initial commit of new layout/consolidated documentation
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
--- /dev/null
+++ b/source/_static/acslogo.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/1000-foot-view.png
Binary files differ
diff --git a/source/_static/images/60recipe.gif b/source/_static/images/60recipe.gif
new file mode 100644
index 0000000..a47a399
--- /dev/null
+++ b/source/_static/images/60recipe.gif
Binary files 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
--- /dev/null
+++ b/source/_static/images/CloudStack-ldap-screen1.png
Binary files differ
diff --git a/source/_static/images/DevCloud-hostonly.png b/source/_static/images/DevCloud-hostonly.png
new file mode 100644
index 0000000..111f93a
--- /dev/null
+++ b/source/_static/images/DevCloud-hostonly.png
Binary files differ
diff --git a/source/_static/images/DevCloud.png b/source/_static/images/DevCloud.png
new file mode 100644
index 0000000..5e83ca9
--- /dev/null
+++ b/source/_static/images/DevCloud.png
Binary files differ
diff --git a/source/_static/images/SnapshotButton.png b/source/_static/images/SnapshotButton.png
new file mode 100644
index 0000000..5217740
--- /dev/null
+++ b/source/_static/images/SnapshotButton.png
Binary files differ
diff --git a/source/_static/images/VMSnapshotButton.png b/source/_static/images/VMSnapshotButton.png
new file mode 100644
index 0000000..5217740
--- /dev/null
+++ b/source/_static/images/VMSnapshotButton.png
Binary files differ
diff --git a/source/_static/images/acslogo.png b/source/_static/images/acslogo.png
new file mode 100644
index 0000000..a938231
--- /dev/null
+++ b/source/_static/images/acslogo.png
Binary files differ
diff --git a/source/_static/images/add-cifs.png b/source/_static/images/add-cifs.png
new file mode 100644
index 0000000..9081f77
--- /dev/null
+++ b/source/_static/images/add-cifs.png
Binary files differ
diff --git a/source/_static/images/add-cluster.png b/source/_static/images/add-cluster.png
new file mode 100644
index 0000000..4b24ec7
--- /dev/null
+++ b/source/_static/images/add-cluster.png
Binary files differ
diff --git a/source/_static/images/add-gateway.png b/source/_static/images/add-gateway.png
new file mode 100644
index 0000000..da8eed9
--- /dev/null
+++ b/source/_static/images/add-gateway.png
Binary files differ
diff --git a/source/_static/images/add-gslb.png b/source/_static/images/add-gslb.png
new file mode 100644
index 0000000..827a913
--- /dev/null
+++ b/source/_static/images/add-gslb.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/add-guest-network.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/add-ip-range.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/add-ldap-configuration-ad.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/add-ldap-configuration-openldap.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/add-new-gateway-vpc.png
Binary files differ
diff --git a/source/_static/images/add-tier.png b/source/_static/images/add-tier.png
new file mode 100644
index 0000000..0994dbd
--- /dev/null
+++ b/source/_static/images/add-tier.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/add-vlan-icon.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/add-vm-vpc.png
Binary files differ
diff --git a/source/_static/images/add-vpc.png b/source/_static/images/add-vpc.png
new file mode 100644
index 0000000..f334862
--- /dev/null
+++ b/source/_static/images/add-vpc.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/add-vpn-customer-gateway.png
Binary files differ
diff --git a/source/_static/images/addAccount-icon.png b/source/_static/images/addAccount-icon.png
new file mode 100644
index 0000000..4743dbe
--- /dev/null
+++ b/source/_static/images/addAccount-icon.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/addvm-tier-sharednw.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/attach-disk-icon.png
Binary files differ
diff --git a/source/_static/images/autoscale-config.png b/source/_static/images/autoscale-config.png
new file mode 100644
index 0000000..735ae96
--- /dev/null
+++ b/source/_static/images/autoscale-config.png
Binary files differ
diff --git a/source/_static/images/basic-deployment.png b/source/_static/images/basic-deployment.png
new file mode 100644
index 0000000..894a053
--- /dev/null
+++ b/source/_static/images/basic-deployment.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/change-admin-password.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/change-affinity-button.png
Binary files differ
diff --git a/source/_static/images/change-password.png b/source/_static/images/change-password.png
new file mode 100644
index 0000000..fbb203a
--- /dev/null
+++ b/source/_static/images/change-password.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/change-service-icon.png
Binary files differ
diff --git a/source/_static/images/cifs-primary.png b/source/_static/images/cifs-primary.png
new file mode 100644
index 0000000..4189980
--- /dev/null
+++ b/source/_static/images/cifs-primary.png
Binary files differ
diff --git a/source/_static/images/cifs-ss.png b/source/_static/images/cifs-ss.png
new file mode 100644
index 0000000..5098095
--- /dev/null
+++ b/source/_static/images/cifs-ss.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/cloudian-s3_ss_cache.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/cloudian-s3_ss_config.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/cloudian-ss_globalopt.png
Binary files differ
diff --git a/source/_static/images/cloudian-tab.png b/source/_static/images/cloudian-tab.png
new file mode 100644
index 0000000..57383e8
--- /dev/null
+++ b/source/_static/images/cloudian-tab.png
Binary files differ
diff --git a/source/_static/images/cluster-overview.png b/source/_static/images/cluster-overview.png
new file mode 100644
index 0000000..18a86c3
--- /dev/null
+++ b/source/_static/images/cluster-overview.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/compute-service-offerings.png
Binary files differ
diff --git a/source/_static/images/console-icon.png b/source/_static/images/console-icon.png
new file mode 100644
index 0000000..bf28886
--- /dev/null
+++ b/source/_static/images/console-icon.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/create-vpn-connection.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/dedicate-resource-button.png
Binary files differ
diff --git a/source/_static/images/del-tier.png b/source/_static/images/del-tier.png
new file mode 100644
index 0000000..aa9846c
--- /dev/null
+++ b/source/_static/images/del-tier.png
Binary files differ
diff --git a/source/_static/images/delete-button.png b/source/_static/images/delete-button.png
new file mode 100644
index 0000000..27145ce
--- /dev/null
+++ b/source/_static/images/delete-button.png
Binary files differ
diff --git a/source/_static/images/destroy-instance.png b/source/_static/images/destroy-instance.png
new file mode 100644
index 0000000..aa9846c
--- /dev/null
+++ b/source/_static/images/destroy-instance.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/detach-disk-icon.png
Binary files differ
diff --git a/source/_static/images/dvswitch-config.png b/source/_static/images/dvswitch-config.png
new file mode 100644
index 0000000..edce6e8
--- /dev/null
+++ b/source/_static/images/dvswitch-config.png
Binary files differ
diff --git a/source/_static/images/dvswitchconfig.png b/source/_static/images/dvswitchconfig.png
new file mode 100644
index 0000000..55b1ef7
--- /dev/null
+++ b/source/_static/images/dvswitchconfig.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/ec2-s3-configuration.png
Binary files differ
diff --git a/source/_static/images/edit-icon.png b/source/_static/images/edit-icon.png
new file mode 100644
index 0000000..42417e2
--- /dev/null
+++ b/source/_static/images/edit-icon.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/edit-traffic-type.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/egress-firewall-rule.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/eip-ns-basiczone.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/enable-disable-autoscale.png
Binary files differ
diff --git a/source/_static/images/enable-disable.png b/source/_static/images/enable-disable.png
new file mode 100644
index 0000000..cab31ae
--- /dev/null
+++ b/source/_static/images/enable-disable.png
Binary files differ
diff --git a/source/_static/images/gslb.png b/source/_static/images/gslb.png
new file mode 100644
index 0000000..f0a04db
--- /dev/null
+++ b/source/_static/images/gslb.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/guest-traffic-setup.png
Binary files differ
diff --git a/source/_static/images/http-access.png b/source/_static/images/http-access.png
new file mode 100644
index 0000000..817f197
--- /dev/null
+++ b/source/_static/images/http-access.png
Binary files differ
diff --git a/source/_static/images/hypervisorcomms-secstorage.png b/source/_static/images/hypervisorcomms-secstorage.png
new file mode 100644
index 0000000..c5c1f8d
--- /dev/null
+++ b/source/_static/images/hypervisorcomms-secstorage.png
Binary files differ
diff --git a/source/_static/images/hypervisorcomms.png b/source/_static/images/hypervisorcomms.png
new file mode 100644
index 0000000..5d4b0ab
--- /dev/null
+++ b/source/_static/images/hypervisorcomms.png
Binary files 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;stroke-dasharray:none"/>
+ <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
--- /dev/null
+++ b/source/_static/images/infrastructure-overview.png
Binary files differ
diff --git a/source/_static/images/installation-complete.png b/source/_static/images/installation-complete.png
new file mode 100644
index 0000000..4626f86
--- /dev/null
+++ b/source/_static/images/installation-complete.png
Binary files differ
diff --git a/source/_static/images/iso-icon.png b/source/_static/images/iso-icon.png
new file mode 100644
index 0000000..8d547fb
--- /dev/null
+++ b/source/_static/images/iso-icon.png
Binary files differ
diff --git a/source/_static/images/jp1.jpg b/source/_static/images/jp1.jpg
new file mode 100644
index 0000000..1778794
--- /dev/null
+++ b/source/_static/images/jp1.jpg
Binary files differ
diff --git a/source/_static/images/jp2.jpg b/source/_static/images/jp2.jpg
new file mode 100644
index 0000000..3cc804a
--- /dev/null
+++ b/source/_static/images/jp2.jpg
Binary files 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
--- /dev/null
+++ b/source/_static/images/large-scale-redundant-setup.png
Binary files differ
diff --git a/source/_static/images/ldap-config.png b/source/_static/images/ldap-config.png
new file mode 100644
index 0000000..28233d9
--- /dev/null
+++ b/source/_static/images/ldap-config.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/mesos-integration-arch.jpg
diff --git a/source/_static/images/metric-view.png b/source/_static/images/metric-view.png
new file mode 100644
index 0000000..bbc6c98
--- /dev/null
+++ b/source/_static/images/metric-view.png
Binary files differ
diff --git a/source/_static/images/migrate-instance.png b/source/_static/images/migrate-instance.png
new file mode 100644
index 0000000..25ff572
--- /dev/null
+++ b/source/_static/images/migrate-instance.png
Binary files differ
diff --git a/source/_static/images/monkey.png b/source/_static/images/monkey.png
new file mode 100644
index 0000000..37928d5
--- /dev/null
+++ b/source/_static/images/monkey.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/multi-node-management-server.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/multi-site-deployment.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/multi-tier-app.png
Binary files differ
diff --git a/source/_static/images/network-acl.png b/source/_static/images/network-acl.png
new file mode 100644
index 0000000..5602827
--- /dev/null
+++ b/source/_static/images/network-acl.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/network-setup-zone.png
Binary files differ
diff --git a/source/_static/images/network-singlepod.png b/source/_static/images/network-singlepod.png
new file mode 100644
index 0000000..e1214ea
--- /dev/null
+++ b/source/_static/images/network-singlepod.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/networking-egress-rule.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/networking-in-a-pod.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/networking-in-a-zone.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/networking-infra-traffic-labels.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/networking-ingress-rule.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/networking-zone-traffic-labels.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nic-bonding-and-multipath-io.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nuage_iso_net_off.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nuage_kvm_traffic_label.jpg
Binary files 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
--- /dev/null
+++ b/source/_static/images/nuage_sha_net_off.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nuage_source_nat_net_off.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nuage_underlay_api_usage.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nuage_vmware_traffic_label.jpg
Binary files 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
--- /dev/null
+++ b/source/_static/images/nuage_vpc_net_off.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nuage_vpc_off.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nuage_vsd_device_add.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nuage_vsp_isolation_method_setting.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nuage_vsp_nsp_enable.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nuage_vsp_nsp_status.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nuage_vsp_vpc_off.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nvp-add-controller.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nvp-enable-provider.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nvp-network-offering.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nvp-physical-network-stt.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/nvp-vpc-offering-edit.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/ovs-network-offering.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/ovs-physical-network-gre-enable.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/ovs-physical-network-gre.png
Binary files differ
diff --git a/source/_static/images/packt.png b/source/_static/images/packt.png
new file mode 100644
index 0000000..53f8a47
--- /dev/null
+++ b/source/_static/images/packt.png
Binary files differ
diff --git a/source/_static/images/parallel-mode.png b/source/_static/images/parallel-mode.png
new file mode 100644
index 0000000..3b67a17
--- /dev/null
+++ b/source/_static/images/parallel-mode.png
Binary files differ
diff --git a/source/_static/images/plugin1.jpg b/source/_static/images/plugin1.jpg
new file mode 100644
index 0000000..970233d
--- /dev/null
+++ b/source/_static/images/plugin1.jpg
Binary files differ
diff --git a/source/_static/images/plugin2.jpg b/source/_static/images/plugin2.jpg
new file mode 100644
index 0000000..9c8a610
--- /dev/null
+++ b/source/_static/images/plugin2.jpg
Binary files differ
diff --git a/source/_static/images/plugin3.jpg b/source/_static/images/plugin3.jpg
new file mode 100644
index 0000000..07fae79
--- /dev/null
+++ b/source/_static/images/plugin3.jpg
Binary files differ
diff --git a/source/_static/images/plugin4.jpg b/source/_static/images/plugin4.jpg
new file mode 100644
index 0000000..2bcec9f
--- /dev/null
+++ b/source/_static/images/plugin4.jpg
Binary files differ
diff --git a/source/_static/images/plugin_intro.jpg b/source/_static/images/plugin_intro.jpg
new file mode 100644
index 0000000..113ffb3
--- /dev/null
+++ b/source/_static/images/plugin_intro.jpg
Binary files differ
diff --git a/source/_static/images/pod-overview.png b/source/_static/images/pod-overview.png
new file mode 100644
index 0000000..c180060
--- /dev/null
+++ b/source/_static/images/pod-overview.png
Binary files differ
diff --git a/source/_static/images/provisioning-overview.png b/source/_static/images/provisioning-overview.png
new file mode 100644
index 0000000..25cc97e
--- /dev/null
+++ b/source/_static/images/provisioning-overview.png
Binary files differ
diff --git a/source/_static/images/region-overview.png b/source/_static/images/region-overview.png
new file mode 100644
index 0000000..528445c
--- /dev/null
+++ b/source/_static/images/region-overview.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/release-ip-icon.png
Binary files differ
diff --git a/source/_static/images/remove-nic.png b/source/_static/images/remove-nic.png
new file mode 100644
index 0000000..27145ce
--- /dev/null
+++ b/source/_static/images/remove-nic.png
Binary files differ
diff --git a/source/_static/images/remove-tier.png b/source/_static/images/remove-tier.png
new file mode 100644
index 0000000..e14d08f
--- /dev/null
+++ b/source/_static/images/remove-tier.png
Binary files differ
diff --git a/source/_static/images/remove-vpc.png b/source/_static/images/remove-vpc.png
new file mode 100644
index 0000000..aa9846c
--- /dev/null
+++ b/source/_static/images/remove-vpc.png
Binary files differ
diff --git a/source/_static/images/remove-vpn.png b/source/_static/images/remove-vpn.png
new file mode 100644
index 0000000..27145ce
--- /dev/null
+++ b/source/_static/images/remove-vpn.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/replace-acl-icon.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/replace-acl-list.png
Binary files differ
diff --git a/source/_static/images/reset-vpn.png b/source/_static/images/reset-vpn.png
new file mode 100644
index 0000000..04655dc
--- /dev/null
+++ b/source/_static/images/reset-vpn.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/resize-volume-icon.png
Binary files differ
diff --git a/source/_static/images/resize-volume.png b/source/_static/images/resize-volume.png
new file mode 100644
index 0000000..6195623
--- /dev/null
+++ b/source/_static/images/resize-volume.png
Binary files differ
diff --git a/source/_static/images/restart-vpc.png b/source/_static/images/restart-vpc.png
new file mode 100644
index 0000000..04655dc
--- /dev/null
+++ b/source/_static/images/restart-vpc.png
Binary files differ
diff --git a/source/_static/images/revert-vm.png b/source/_static/images/revert-vm.png
new file mode 100644
index 0000000..04655dc
--- /dev/null
+++ b/source/_static/images/revert-vm.png
Binary files differ
diff --git a/source/_static/images/s3-ss.png b/source/_static/images/s3-ss.png
new file mode 100644
index 0000000..bd7cdf2
--- /dev/null
+++ b/source/_static/images/s3-ss.png
Binary files differ
diff --git a/source/_static/images/search-button.png b/source/_static/images/search-button.png
new file mode 100644
index 0000000..f329aef
--- /dev/null
+++ b/source/_static/images/search-button.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/select-vm-staticnat-vpc.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/separate-storage-network.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/set-default-nic.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/small-scale-deployment.png
Binary files differ
diff --git a/source/_static/images/software-license.png b/source/_static/images/software-license.png
new file mode 100644
index 0000000..67aa255
--- /dev/null
+++ b/source/_static/images/software-license.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/stop-instance-icon.png
Binary files differ
diff --git a/source/_static/images/subnetting_storage.png b/source/_static/images/subnetting_storage.png
new file mode 100644
index 0000000..a6f47d6
--- /dev/null
+++ b/source/_static/images/subnetting_storage.png
Binary files differ
diff --git a/source/_static/images/suspend-icon.png b/source/_static/images/suspend-icon.png
new file mode 100644
index 0000000..cab31ae
--- /dev/null
+++ b/source/_static/images/suspend-icon.png
Binary files differ
diff --git a/source/_static/images/sysmanager.png b/source/_static/images/sysmanager.png
new file mode 100644
index 0000000..5b9df34
--- /dev/null
+++ b/source/_static/images/sysmanager.png
Binary files differ
diff --git a/source/_static/images/traffic-type.png b/source/_static/images/traffic-type.png
new file mode 100644
index 0000000..10d5ddb
--- /dev/null
+++ b/source/_static/images/traffic-type.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/update-ssl-icon.png
Binary files differ
diff --git a/source/_static/images/update-ssl.png b/source/_static/images/update-ssl.png
new file mode 100644
index 0000000..2f2ee53
--- /dev/null
+++ b/source/_static/images/update-ssl.png
Binary files differ
diff --git a/source/_static/images/vds-name.png b/source/_static/images/vds-name.png
new file mode 100644
index 0000000..bf5b4fc
--- /dev/null
+++ b/source/_static/images/vds-name.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/view-console-button.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/view-systemvm-details.png
Binary files differ
diff --git a/source/_static/images/vm-lifecycle.png b/source/_static/images/vm-lifecycle.png
new file mode 100644
index 0000000..97823fc
--- /dev/null
+++ b/source/_static/images/vm-lifecycle.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/vmware-increase-ports.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/vmware-iscsi-datastore.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/vmware-iscsi-general.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/vmware-iscsi-initiator-properties.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/vmware-iscsi-initiator.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/vmware-iscsi-target-add.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/vmware-mgt-network-properties.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/vmware-nexus-add-cluster.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/vmware-nexus-port-profile.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/vmware-physical-network.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/vmware-vswitch-properties.png
Binary files differ
diff --git a/source/_static/images/vpc-lb.png b/source/_static/images/vpc-lb.png
new file mode 100644
index 0000000..4269e8b
--- /dev/null
+++ b/source/_static/images/vpc-lb.png
Binary files differ
diff --git a/source/_static/images/vpc-setting.png b/source/_static/images/vpc-setting.png
new file mode 100644
index 0000000..782299e
--- /dev/null
+++ b/source/_static/images/vpc-setting.png
Binary files differ
diff --git a/source/_static/images/vpn-icon.png b/source/_static/images/vpn-icon.png
new file mode 100644
index 0000000..2ac12f7
--- /dev/null
+++ b/source/_static/images/vpn-icon.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/vpn/osxvpn_connected.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/vpn/osxvpn_form1.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/vpn/osxvpn_form2.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/vpn/osxvpn_form3.png
Binary files 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
--- /dev/null
+++ b/source/_static/images/vpn/osxvpn_netconf.png
Binary files differ
diff --git a/source/_static/images/vpn/win1.png b/source/_static/images/vpn/win1.png
new file mode 100644
index 0000000..c9bb893
--- /dev/null
+++ b/source/_static/images/vpn/win1.png
Binary files differ
diff --git a/source/_static/images/vpn/win10.png b/source/_static/images/vpn/win10.png
new file mode 100644
index 0000000..2cbe591
--- /dev/null
+++ b/source/_static/images/vpn/win10.png
Binary files differ
diff --git a/source/_static/images/vpn/win11.png b/source/_static/images/vpn/win11.png
new file mode 100644
index 0000000..cf95426
--- /dev/null
+++ b/source/_static/images/vpn/win11.png
Binary files differ
diff --git a/source/_static/images/vpn/win12.png b/source/_static/images/vpn/win12.png
new file mode 100644
index 0000000..61ba08c
--- /dev/null
+++ b/source/_static/images/vpn/win12.png
Binary files differ
diff --git a/source/_static/images/vpn/win13.png b/source/_static/images/vpn/win13.png
new file mode 100644
index 0000000..d5a990f
--- /dev/null
+++ b/source/_static/images/vpn/win13.png
Binary files differ
diff --git a/source/_static/images/vpn/win14.png b/source/_static/images/vpn/win14.png
new file mode 100644
index 0000000..2d6e93c
--- /dev/null
+++ b/source/_static/images/vpn/win14.png
Binary files differ
diff --git a/source/_static/images/vpn/win2.png b/source/_static/images/vpn/win2.png
new file mode 100644
index 0000000..f30ef69
--- /dev/null
+++ b/source/_static/images/vpn/win2.png
Binary files differ
diff --git a/source/_static/images/vpn/win3.png b/source/_static/images/vpn/win3.png
new file mode 100644
index 0000000..bc0dc91
--- /dev/null
+++ b/source/_static/images/vpn/win3.png
Binary files differ
diff --git a/source/_static/images/vpn/win4.png b/source/_static/images/vpn/win4.png
new file mode 100644
index 0000000..1599f58
--- /dev/null
+++ b/source/_static/images/vpn/win4.png
Binary files differ
diff --git a/source/_static/images/vpn/win5.png b/source/_static/images/vpn/win5.png
new file mode 100644
index 0000000..d2d5f7a
--- /dev/null
+++ b/source/_static/images/vpn/win5.png
Binary files differ
diff --git a/source/_static/images/vpn/win6.png b/source/_static/images/vpn/win6.png
new file mode 100644
index 0000000..cb27870
--- /dev/null
+++ b/source/_static/images/vpn/win6.png
Binary files differ
diff --git a/source/_static/images/vpn/win7.png b/source/_static/images/vpn/win7.png
new file mode 100644
index 0000000..e601f15
--- /dev/null
+++ b/source/_static/images/vpn/win7.png
Binary files differ
diff --git a/source/_static/images/vpn/win8.png b/source/_static/images/vpn/win8.png
new file mode 100644
index 0000000..4ab5db5
--- /dev/null
+++ b/source/_static/images/vpn/win8.png
Binary files differ
diff --git a/source/_static/images/vpn/win9.png b/source/_static/images/vpn/win9.png
new file mode 100644
index 0000000..e276f5f
--- /dev/null
+++ b/source/_static/images/vpn/win9.png
Binary files differ
diff --git a/source/_static/images/vr-upgrade.png b/source/_static/images/vr-upgrade.png
new file mode 100644
index 0000000..42417e2
--- /dev/null
+++ b/source/_static/images/vr-upgrade.png
Binary files differ
diff --git a/source/_static/images/vsphere-client.png b/source/_static/images/vsphere-client.png
new file mode 100644
index 0000000..2acc8b8
--- /dev/null
+++ b/source/_static/images/vsphere-client.png
Binary files differ
diff --git a/source/_static/images/vxlan-physicalnetwork.png b/source/_static/images/vxlan-physicalnetwork.png
new file mode 100644
index 0000000..eb06fcd
--- /dev/null
+++ b/source/_static/images/vxlan-physicalnetwork.png
Binary files differ
diff --git a/source/_static/images/vxlan-trafficlabel.png b/source/_static/images/vxlan-trafficlabel.png
new file mode 100644
index 0000000..916e944
--- /dev/null
+++ b/source/_static/images/vxlan-trafficlabel.png
Binary files differ
diff --git a/source/_static/images/vxlan-vniconfig.png b/source/_static/images/vxlan-vniconfig.png
new file mode 100644
index 0000000..c7372a0
--- /dev/null
+++ b/source/_static/images/vxlan-vniconfig.png
Binary files differ
diff --git a/source/_static/images/workloads.png b/source/_static/images/workloads.png
new file mode 100644
index 0000000..a8334d9
--- /dev/null
+++ b/source/_static/images/workloads.png
Binary files differ
diff --git a/source/_static/images/zone-overview.png b/source/_static/images/zone-overview.png
new file mode 100644
index 0000000..24aeecf
--- /dev/null
+++ b/source/_static/images/zone-overview.png
Binary files 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 <EMAIL@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 <EMAIL@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 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."
+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, a host with system VMs or virtual routers can be used for preferred implicit dedication."
+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 starting at a specified base directory and return the distinguished name (DN) and password of the matching user. This information along with the given password is used to authenticate the user.."
+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 is outside the scope of our documentation. The following table shows some examples of search bases to find users in the testing department.."
+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 <EMAIL@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 <EMAIL@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 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."
+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 <EMAIL@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 <EMAIL@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 <EMAIL@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 <EMAIL@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 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.."
+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 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."
+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, action events, usage events) and the additional category of resource state change events, are published on to the events bus."
+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 archived or deleted."
+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 <EMAIL@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 <EMAIL@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 support any system that is not up to date with patches."
+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 the CloudStack placement algorithm decides to place a VM."
+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 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."
+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 the same set of IPs for different customers, each one with their own routers and the guest networks on different physical NICs."
+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 <EMAIL@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 <EMAIL@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 <EMAIL@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 <EMAIL@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 the number of hosts and sockets used for each host type."
+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 <EMAIL@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 <EMAIL@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 a web server farm and require a scalable firewall solution, load balancing solution, and alternate networks for accessing the database backend."
+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 custom system service offerings that have been defined by the CloudStack root administrator."
+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 master virtual router. CloudStack deploys the routers on different hosts to ensure reliability if one host is down."
+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 <EMAIL@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 <EMAIL@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 <EMAIL@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 <EMAIL@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 <EMAIL@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 <EMAIL@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 <EMAIL@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 <EMAIL@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 <EMAIL@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 <EMAIL@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 is down, the IP address can be reassigned to a new VM in your account."
+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 data center goes through the firewall."
+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 and enable static NAT."
+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 <EMAIL@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 <EMAIL@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 device providing EIP/ELB, layer 3 router must have a policy-based routing. A policy-based route must be set up so that all traffic originated from the guest VM's are directed to NetScaler device. This is required to ensure that the outbound traffic from the guest VM's is routed to a public IP by using NAT.For more information on Elastic IP, see `\"About Elastic IP\" <#about-elastic-ip>`_."
+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 objects:"
+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, cookies are used. The cookie generated by the load balancer or application is included in request and response URLs to create persistence. The cookie name can be specified by the administrator or automatically generated. A variety of options are provided to control the exact behavior of cookies, such as how they are generated and whether they are cached."
+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 with a health check configured, the state will be shown as UP or DOWN in the UI depending on the result of the most recent health check."
+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 CPU usage is less than 20 percent for 30 minutes."
+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-server>`_ to configure SNMP on a RHEL machine."
+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 active instance count breaches the Max instance value."
+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 <EMAIL@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 <EMAIL@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 accessing a resource in the event of a failure, or to provide a means of shifting traffic easily to simplify maintenance, or both."
+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 a FQDN DNS name."
+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 balancing or content switching virtual server, the client sends the request to that virtual server's VIP address."
+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 and port."
+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 xyztelco cloud. For that purpose, they launch two instances each in both the zones: VM1 and VM2 in Zone-1 and VM5 and VM6 in Zone-2. Tenant-A acquires a public IP, IP-1 in Zone-1, and configures a load balancer rule to load balance the traffic between VM1 and VM2 instances. CloudStack orchestrates setting up a virtual server on the LB service provider in Zone-1. Virtual server 1 that is set up on the LB service provider in Zone-1 represents a publicly accessible virtual server that client reaches at IP-1. The client traffic to virtual server 1 at IP-1 will be load balanced across VM1 and VM2 instances."
+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 instances. At this point Tenant-A has the service enabled in both the zones, but has no means to set up a disaster recovery plan if one of the zone fails. Additionally, there is no way for Tenant-A to load balance the traffic intelligently to one of the zones based on load, proximity and so on. The cloud administrator of xyztelco provisions a GSLB service provider to both the zones. A GSLB provider is typically an ADC that has the ability to act as an ADNS (Authoritative Domain Name Server) and has the mechanism to monitor health of virtual servers both at local and remote sites. The cloud admin enables GSLB as a service to the tenants that use zones 1 and 2."
+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 start monitoring the health of virtual server 1 and 2 in Zone-1. CloudStack will also orchestrate setting up GSLB virtual server 2 on GSLB service provider at Zone-2. CloudStack will bind virtual server 1 of Zone-1 and virtual server 2 of Zone-2 to GLSB virtual server 2. GSLB virtual server 2 is configured to start monitoring the health of virtual server 1 and 2. CloudStack will bind the domain A.xyztelco.com to both the GSLB virtual server 1 and 2. At this point, Tenant-A service will be globally reachable at A.xyztelco.com. The private DNS server for the domain xyztelcom.com is configured by the admin out-of-band to resolve the domain A.xyztelco.com to the GSLB providers at both the zones, which are configured as ADNS for the domain A.xyztelco.com. A client when sends a DNS request to resolve A.xyztelcom.com, will eventually get DNS delegation to the address of GSLB providers at zone 1 and 2. A client DNS request will be received by the GSLB provider. The GSLB provider, depending on the domain for which it needs to resolve, will pick up the GSLB virtual server associated with the domain. Depending on the health of the virtual servers being load balanced, DNS request for the domain will be resolved to the public IP associated with the selected virtual server."
+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 servers. Finally, bind the domain to the GSLB virtual servers. The GSLB configurations on the two appliances at the two different zones are identical, although each sites load-balancing configuration is specific to that site."
+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 <EMAIL@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 <EMAIL@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 <EMAIL@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 <EMAIL@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 router. Its eth2 interface is assigned a public IP address for public traffic. If multiple public VLAN is used, the router will have multiple public interfaces."
+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 <EMAIL@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 <EMAIL@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 the VMs. In effect, you can segment VMs by means of VLANs into different networks that can host multi-tier applications, such as Web, Application, or Database. Such segmentation by means of VLANs logically separate application VMs for higher security and lower broadcasts, while remaining physically connected to the same device."
+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 <EMAIL@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 <EMAIL@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 rules are removed the default policy, Block, is applied."
+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 <EMAIL@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 <EMAIL@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 <EMAIL@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 <EMAIL@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 called Reserved IP Range. When IP reservation is configured, the administrator can add additional VMs or physical servers that are not part of CloudStack to the same network and assign them the Reserved IP addresses. CloudStack guest VMs cannot acquire IPs from the Reserved IP Range."
+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 <EMAIL@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 <EMAIL@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 users' VMs."
+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 VLAN that is being divided into smaller groups is called Primary, which implies that all VLAN pairs in a private VLAN share the same Primary VLAN. All the secondary VLANs exist only inside the Primary. Each Secondary VLAN has a specific VLAN ID associated to it, which differentiates one sub-domain from another."
+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 communicate among themselves, deploy them in community ports."
+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 <EMAIL@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 <EMAIL@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
+# cb23bf06693941579c5993219c416bb8
+msgid "CIDR (for IPv6)"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:133
+# bce02b8426584ab693112a2a3eaa69a4
+msgid "Removing a Network"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:143
+# ca1c1c7c1c9d4ff8aaca289a38a6f7c0
+msgid "Locate the NIC you want to remove."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:145
+# 85a4e2e7437642f18635fa647891d856
+msgid "Click Remove NIC button. |remove-nic.png|"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:147
+#: ../../networking/multiple_guest_networks.rst:165
+# ffa7cf9f06374be19a3b64261219cdc1
+# 5597778b6dec4d1fac608939422f4a00
+msgid "Click Yes to confirm."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:151
+# 78a6b76d558e43c18b80b80d9ae29567
+msgid "Selecting the Default Network"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:161
+# d548799e04664a74b122217c8b65678f
+msgid "Locate the NIC you want to work with."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:163
+# 43217c75ff3e4ac885b27d575f4c47ee
+msgid "Click the Set default NIC button. |set-default-nic.png|."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:168
+# fea27f4c1e3f45e89b4b9439c9affb16
+msgid "Changing the Network Offering on a Guest Network"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:170
+# 9de4858c24814a74a54559f2494b3a89
+msgid "A user or administrator can change the network offering that is associated with an existing guest network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:175
+# 7c551d2e95a241b48be8ce6603506ab3
+msgid "If you are changing from a network offering that uses the CloudStack virtual router to one that uses external devices as network service providers, you must first stop all the VMs on the network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:181
+# c67df95acd7f48b18f620634af845488
+msgid "Click the name of the network you want to modify."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:183
+# fb679c3a524c4c4a837fe24566e3a12b
+msgid "In the Details tab, click Edit. |edit-icon.png|"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:185
+# 4afa43a2ac5b46f29ad42d421235b01d
+msgid "In Network Offering, choose the new network offering, then click Apply."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:188
+# 6a7280bbaba74bfb8b6622ac7832cf5c
+msgid "A prompt is displayed asking whether you want to keep the existing CIDR. This is to let you know that if you change the network offering, the CIDR will be affected."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:192
+# 42e2f2150b07464bbdf35bc0c30edd91
+msgid "If you upgrade between virtual router as a provider and an external network device as provider, acknowledge the change of CIDR to continue, so choose Yes."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:196
+# 3b240e38bc11456095069b1622cc917f
+msgid "Wait for the update to complete. Don't try to restart VMs until the network change is complete."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:199
+# a6db1505b17b48e1ae1063872635e2bb
+msgid "If you stopped any VMs, restart them."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/multiple_ip_ranges.pot b/source/adminguide/locale/pot/networking/multiple_ip_ranges.pot
new file mode 100644
index 0000000..1c2c968
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/multiple_ip_ranges.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 <EMAIL@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 <EMAIL@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_ip_ranges.rst:18
+# cea4bcb571304273bc04b67f139f0140
+msgid "About Multiple IP Ranges"
+msgstr ""
+
+#: ../../networking/multiple_ip_ranges.rst:20
+# fb1aec1297a645198cd0ecbc09f187eb
+msgid "The feature can only be implemented on IPv4 addresses."
+msgstr ""
+
+#: ../../networking/multiple_ip_ranges.rst:22
+# 3180ea2f13aa4565a8715d959ef1148d
+msgid "CloudStack provides you with the flexibility to add guest IP ranges from different subnets in Basic zones and security groups-enabled Advanced zones. For security groups-enabled Advanced zones, it implies multiple subnets can be added to the same VLAN. With the addition of this feature, you will be able to add IP address ranges from the same subnet or from a different one when IP address are exhausted. This would in turn allows you to employ higher number of subnets and thus reduce the address management overhead. To support this feature, the capability of ``createVlanIpRange`` API is extended to add IP ranges also from a different subnet."
+msgstr ""
+
+#: ../../networking/multiple_ip_ranges.rst:33
+# d1d9636b0fd14b508f2570b3d7f5b7a2
+msgid "Ensure that you manually configure the gateway of the new subnet before adding the IP range. Note that CloudStack supports only one gateway for a subnet; overlapping subnets are not currently supported."
+msgstr ""
+
+#: ../../networking/multiple_ip_ranges.rst:37
+# b1ed3bd81dfa4662bcf9ab17817d99e5
+msgid "Use the ``deleteVlanRange`` API to delete IP ranges. This operation fails if an IP from the remove range is in use. If the remove range contains the IP address on which the DHCP server is running, CloudStack acquires a new IP from the same subnet. If no IP is available in the subnet, the remove operation fails."
+msgstr ""
+
+#: ../../networking/multiple_ip_ranges.rst:43
+# 5c66e6ebd5cc42728bccf16a99764a94
+msgid "This feature is supported on KVM, xenServer, and VMware hypervisors."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/multiple_ips_on_single_nic.pot b/source/adminguide/locale/pot/networking/multiple_ips_on_single_nic.pot
new file mode 100644
index 0000000..7919a5f
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/multiple_ips_on_single_nic.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 <EMAIL@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 <EMAIL@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_ips_on_single_nic.rst:18
+# 80e46ffc92914befa1e1b6bb37ae48e0
+msgid "Configuring Multiple IP Addresses on a Single NIC"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:20
+# e552e4b860e64b83bd63e053002d0187
+msgid "CloudStack provides you the ability to associate multiple private IP addresses per guest VM NIC. In addition to the primary IP, you can assign additional IPs to the guest VM NIC. This feature is supported on all the network configurations: Basic, Advanced, and VPC. Security Groups, Static NAT and Port forwarding services are supported on these additional IPs."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:27
+# 37ec7f1162de4309afcd34ea7bc9af66
+msgid "As always, you can specify an IP from the guest subnet; if not specified, an IP is automatically picked up from the guest VM subnet. You can view the IPs associated with for each guest VM NICs on the UI. You can apply NAT on these additional guest IPs by using network configuration option in the CloudStack UI. You must specify the NIC to which the IP should be associated."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:34
+# 9a035e888c1245098bf6a6b97754c398
+msgid "This feature is supported on XenServer, KVM, and VMware hypervisors. Note that Basic zone security groups are not supported on VMware."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:39
+# e65e3e62dc4a4301b7c488f06bbe696d
+msgid "Use Cases"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:41
+# 11ad1c7201dd4368b51c2686f4f6c436
+msgid "Some of the use cases are described below:"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:43
+# bad26d93f70a454ea65fe8d314c5fb5f
+msgid "Network devices, such as firewalls and load balancers, generally work best when they have access to multiple IP addresses on the network interface."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:47
+# 95be93b5a22541cf8e3a65154ae683cc
+msgid "Moving private IP addresses between interfaces or instances. Applications that are bound to specific IP addresses can be moved between instances."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:51
+# 9ee757e7b88f4aa2a87ccd4771a324d2
+msgid "Hosting multiple SSL Websites on a single instance. You can install multiple SSL certificates on a single instance, each associated with a distinct IP address."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:57
+# 4edd1f589e2e49829a8738af942f1449
+msgid "Guidelines"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:59
+# 54a52619c6484653a0d95be689657a85
+msgid "To prevent IP conflict, configure different subnets when multiple networks are connected to the same VM."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:64
+# 2e55027ec0ce4ce6b87130453ca2ea69
+msgid "Assigning Additional IPs to a VM"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:66
+# 24aaa9f9fd734b1d9b775ad1342d31b2
+msgid "Log in to the CloudStack UI."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:68
+# 51fd921471ee488bb728f102e439c19e
+msgid "In the left navigation bar, click Instances."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:70
+# f0efc1c51c2a471498620eb3d6313aa6
+msgid "Click the name of the instance you want to work with."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:72
+# 17a62e09249f4a3fac5b78b1ee42aa11
+msgid "In the Details tab, click NICs."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:74
+# 815af55e9e6e475ea2139c0ee79838c8
+msgid "Click View Secondary IPs."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:76
+# edd4eb38ff964d91901201733864317e
+msgid "Click Acquire New Secondary IP, and click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:79
+# a243effbef704447bf0f0a2d5bdc0a86
+msgid "You need to configure the IP on the guest VM NIC manually. CloudStack will not automatically configure the acquired IP address on the VM. Ensure that the IP address configuration persist on VM reboot."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:83
+# 92b50e481e5943af8db0036e562bcf45
+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 StaticNAT rules."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:89
+# 8ce45ae597644592be9f68b1b9a50693
+msgid "Port Forwarding and StaticNAT Services Changes"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:91
+# 707c305e2e104709866aebe9741b3891
+msgid "Because multiple IPs can be associated per NIC, you are allowed to select a desired IP for the Port Forwarding and StaticNAT services. The default is the primary IP. To enable this functionality, an extra optional parameter 'vmguestip' is added to the Port forwarding and StaticNAT APIs (enableStaticNat, createIpForwardingRule) to indicate on what IP address NAT need to be configured. If vmguestip is passed, NAT is configured on the specified private IP of the VM. if not passed, NAT is configured on the primary IP of the VM."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/multiple_subnets_in_shared_network.pot b/source/adminguide/locale/pot/networking/multiple_subnets_in_shared_network.pot
new file mode 100644
index 0000000..ca77e68
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/multiple_subnets_in_shared_network.pot
@@ -0,0 +1,158 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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_subnets_in_shared_network.rst:18
+# aaae14dc309846cf90268bd429550032
+msgid "Multiple Subnets in Shared Network"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:20
+# e1e0546c06b44b948781bf1b155376b6
+msgid "CloudStack provides you with the flexibility to add guest IP ranges from different subnets in Basic zones and security groups-enabled Advanced zones. For security groups-enabled Advanced zones, it implies multiple subnets can be added to the same VLAN. With the addition of this feature, you will be able to add IP address ranges from the same subnet or from a different one when IP address are exhausted. This would in turn allows you to employ higher number of subnets and thus reduce the address management overhead. You can delete the IP ranges you have added."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:32
+# d651b6e4b73a4c8897943f492f553be4
+msgid "Prerequisites and Guidelines"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:34
+# 321b92f77c9e47b581323b300949d477
+msgid "This feature can only be implemented:"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:36
+# 693a867b887b40c39f9112ee79a514f3
+msgid "on IPv4 addresses"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:38
+# d4bb9088f4ce439bb4aa86f2d6ca1226
+msgid "if virtual router is the DHCP provider"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:40
+# b4bb01b3421b4a26af052b41ef2e9c74
+msgid "on KVM, xenServer, and VMware hypervisors"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:42
+# 3ce0b6127bed4c878204268e02519b5f
+msgid "Manually configure the gateway of the new subnet before adding the IP range."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:45
+# 92e9da161e084fd09cbd7a34e3a8ea59
+msgid "CloudStack supports only one gateway for a subnet; overlapping subnets are not currently supported"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:50
+# 0ccc8eb511c649519820d407c101fb3f
+msgid "Adding Multiple Subnets to a Shared Network"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:52
+# 402388a40d1c4432adf97dcb94bc7e0a
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:54
+# c062e6ebc0b74be185c8e192c237a3d8
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:56
+# 9d6f09662ceb452bb8bf26c21696a7ff
+msgid "On Zones, click View More, then click the zone to which you want to work with.."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:59
+# 9a6c131e8dee4829a34a534324f96d6a
+msgid "Click Physical Network."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:61
+# 412cf2ea6b7c4fc9a45dcfabca044210
+msgid "In the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:63
+# 20271a4db3304ebd986eefb0dbe2304b
+msgid "Click Networks."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:65
+# d4d67c51b96a441984f094dad7440b53
+msgid "Select the networks you want to work with."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:67
+# dbda223b46514614bc24a96cbd967579
+msgid "Click View IP Ranges."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:69
+# fd40e95e0dcc4b37ac83ea1764ccd1c5
+msgid "Click Add IP Range."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:71
+# e57818339fdd4bea80a587551ff3bb27
+msgid "The Add IP Range dialog is displayed, as follows:"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:73
+# 1adf38c68dd04551aeded2194d8d3bfb
+msgid "|add-ip-range.png|"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:75
+# 8d5c0e4efe1742f7988a60fe55223d66
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:77
+# c5bd70e2ab5748e18b8bc2840088a41e
+msgid "All the fields are mandatory."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:79
+# cefcd378eaf44ae5b0c6aaa2809a4fe4
+msgid "**Gateway**: The gateway for the tier you create. Ensure that the gateway is within the Super CIDR range that you specified while creating the VPC, and is not overlapped with the CIDR of any existing tier within the VPC."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:84
+# d63b707e5f374d5d807b5749f9cc44ad
+msgid "**Netmask**: The netmask for the tier you create."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:86
+# f5d499f2a9fa4a859f8563d9b68b29a3
+msgid "For example, if the VPC CIDR is 10.0.0.0/16 and the network tier CIDR is 10.0.1.0/24, the gateway of the tier is 10.0.1.1, and the netmask of the tier is 255.255.255.0."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:90
+# 4aeabf0b77244ea994e1c9a3587421a7
+msgid "**Start IP/ End IP**: A range of IP addresses that are accessible from the Internet and will be allocated to guest VMs. Enter the first and last IP addresses that define a range that CloudStack can assign to guest VMs ."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:95
+# c54dd19ac3fc4b1abe5c8e2ba6021969
+msgid "Click OK."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/networking_in_pod.pot b/source/adminguide/locale/pot/networking/networking_in_pod.pot
new file mode 100644
index 0000000..47d6094
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/networking_in_pod.pot
@@ -0,0 +1,58 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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/networking_in_pod.rst:18
+# 3d0c16ad63444261b9694623c2402727
+msgid "Networking in a Pod"
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:20
+# 6f94486d31ee45b8a15da0d2a1c080ca
+msgid "The figure below illustrates network setup within a single pod. The hosts are connected to a pod-level switch. At a minimum, the hosts should have one physical uplink to each switch. Bonded NICs are supported as well. The pod-level switch is a pair of redundant gigabit switches with 10 G uplinks."
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:26
+# d14ee305eeed479b95127d50242ce7f9
+msgid "|networksinglepod.png|"
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:28
+# 6c63d1a963fe4751bb6a3efcc28ec07b
+msgid "Servers are connected as follows:"
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:30
+# cab4d0a9b3874148b142ec81b8916ab3
+msgid "Storage devices are connected to only the network that carries management traffic."
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:33
+# a01f83aa00be44768e404b928746539d
+msgid "Hosts are connected to networks for both management traffic and public traffic."
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:36
+# 7cc32b192f154001a6b37b93bf141c79
+msgid "Hosts are also connected to one or more networks carrying guest traffic."
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:39
+# afe45e02d11f436b92bc4752de309aa2
+msgid "We recommend the use of multiple physical Ethernet cards to implement each network interface as well as redundant switch fabric in order to maximize throughput and improve reliability."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/networking_in_zone.pot b/source/adminguide/locale/pot/networking/networking_in_zone.pot
new file mode 100644
index 0000000..377c408
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/networking_in_zone.pot
@@ -0,0 +1,43 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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/networking_in_zone.rst:18
+# 3080bd3d63ce42f7970a7e111d5cc46b
+msgid "Networking in a Zone"
+msgstr ""
+
+#: ../../networking/networking_in_zone.rst:20
+# acc145c9dbbb43d0a4e7bcb5cdb804cb
+msgid "The following figure illustrates the network setup within a single zone."
+msgstr ""
+
+#: ../../networking/networking_in_zone.rst:22
+# a22b23e45435457b927cdcd248830e97
+msgid "|networksetupzone.png|"
+msgstr ""
+
+#: ../../networking/networking_in_zone.rst:24
+# 116d5e262cd547858fe9873be74c59da
+msgid "A firewall for management traffic operates in the NAT mode. The network typically is assigned IP addresses in the 192.168.0.0/16 Class B private address space. Each pod is assigned IP addresses in the 192.168.\\*.0/24 Class C private address space."
+msgstr ""
+
+#: ../../networking/networking_in_zone.rst:29
+# 7a1eee0be4da4ed3aa3c0854ab4c2230
+msgid "Each zone has its own set of public IP addresses. Public IP addresses from different zones do not overlap."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/palo_alto_config.pot b/source/adminguide/locale/pot/networking/palo_alto_config.pot
new file mode 100644
index 0000000..6483dea
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/palo_alto_config.pot
@@ -0,0 +1,781 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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/palo_alto_config.rst:18
+# f3d9b37c09d84940aa4c2fde3f9acd2a
+msgid "Setup a Palo Alto Networks Firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:22
+# bf6ec115893747b1baf4957e9be35ff4
+msgid "Functionality Provided"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:24
+# c1f3ed83f8394089ab4694fe954e0195
+msgid "This implementation enables the orchestration of a Palo Alto Networks Firewall from within CloudStack UI and API."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:27
+# 4b1340d4e6f74cd39095e06ca20ccbdd
+msgid "**The following features are supported**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:29
+# e30f817e0e4d45ff8140a2bf41b86fb3
+msgid "List/Add/Delete Palo Alto Networks service provider"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:31
+# d027f8c0521d4e3c8659c5f89b010dc3
+msgid "List/Add/Delete Palo Alto Networks network service offering"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:33
+# d3c3bd36ca4744d68797f6bda8758efd
+msgid "List/Add/Delete Palo Alto Networks network using the above service offering"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:35
+# d4ba1563cd1a4efb8039895bd0fc4abc
+msgid "Add an instance to a Palo Alto Networks network"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:37
+# 095297003ef84ab4946859b93741650f
+msgid "Source NAT management on network create and delete"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:39
+# 83be5169430e457495da1faa61028b94
+msgid "List/Add/Delete Ingress Firewall rule"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:41
+# 934645096b2041c0892c5827ab0bae62
+msgid "List/Add/Delete Egress Firewall rule (both 'Allow' and 'Deny' default rules supported)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:44
+# b3d40e33e09544e892974a896c1c0f5e
+msgid "List/Add/Delete Port Forwarding rule"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:46
+# 2227e25f9e3e4cf19e34dd0deddbb404
+msgid "List/Add/Delete Static NAT rule"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:48
+# 64c598fbe2d04d368d5f30c35aa7f1d6
+msgid "Apply a Threat Profile to all firewall rules (more details in the Additional Features section)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:51
+# 6843739b321a4d828b6e9b17a9ef0fc8
+msgid "Apply a Log Forwarding profile to all firewall rules (more details in the Additional Features section)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:57
+# 90c46aad0abf4f3c9d84941828556629
+msgid "Initial Palo Alto Networks Firewall Configuration"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:60
+# 3404e87b314644c49c28a53bc5f5e6a0
+msgid "Anatomy of the Palo Alto Networks Firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:62
+# a9c2ce1bfd05437a975c7cb37c0fba62
+msgid "In **'Network > Interfaces'** there is a list of physical interfaces as well as aggregated physical interfaces which are used for managing traffic in and out of the Palo Alto Networks Firewall device."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:66
+# 5ac5b705b6834ded91c030380797cbd2
+msgid "In **'Network > Zones'** there is a list of the different configuration zones. This implementation will use two zones; a public (defaults to 'untrust') and private (defaults to 'trust') zone."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:70
+# eea4177c1fff4e099f0d3ed3d68ddfca
+msgid "In **'Network > Virtual Routers'** there is a list of VRs which handle traffic routing for the Palo Alto Firewall. We only use a single Virtual Router on the firewall and it is used to handle all the routing to the next network hop."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:75
+# abd376e7380441f390cd90564d09d4c5
+msgid "In **'Objects > Security Profile Groups'** there is a list of profiles which can be applied to firewall rules. These profiles are used to better understand the types of traffic that is flowing through your network. Configured when you add the firewall provider to CloudStack."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:80
+# 81bf3163d8e548f9827901650a45fa29
+msgid "In **'Objects > Log Forwarding'** there is a list of profiles which can be applied to firewall rules. These profiles are used to better track the logs generated by the firewall. Configured when you add the firewall provider to CloudStack."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:85
+# 3f1feff617394987a3e0e75b9098bdb8
+msgid "In **'Policies > Security'** there is a list of firewall rules that are currently configured. You will not need to modify this section because it will be completely automated by CloudStack, but you can review the firewall rules which have been created here."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:90
+# 34e8e7a02d1a478d99e352c6a4dd825c
+msgid "In **'Policies > NAT'** there is a list of the different NAT rules. You will not need to modify this section because it will be completely automated by CloudStack, but you can review the different NAT rules that have been created here. Source NAT, Static NAT and Destination NAT (Port Forwarding) rules will show up in this list."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:99
+# 640e9e01bf184821b43d47005542f297
+msgid "Configure the Public / Private Zones on the firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:101
+# dd1583c5eff3465b96b6e0e55da67a78
+msgid "No manual configuration is required to setup these zones because CloudStack will configure them automatically when you add the Palo Alto Networks firewall device to CloudStack as a service provider. This implementation depends on two zones, one for the public side and one for the private side of the firewall."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:107
+# f247dae111a8455598a5509325f99b2d
+msgid "The public zone (defaults to 'untrust') will contain all of the public interfaces and public IPs."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:110
+# 3cc0d8d0cdd949bbae82f501193f7705
+msgid "The private zone (defaults to 'trust') will contain all of the private interfaces and guest network gateways."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:113
+# fffcd92335be420f92a7847a249b200c
+msgid "The NAT and firewall rules will be configured between these zones."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:118
+# 0f85059787c94c61b9cb4b39e5cb52c9
+msgid "Configure the Public / Private Interfaces on the firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:120
+# c8c72310b2744d4caefb5b9575ee6e60
+msgid "This implementation supports standard physical interfaces as well as grouped physical interfaces called aggregated interfaces. Both standard interfaces and aggregated interfaces are treated the same, so they can be used interchangeably. For this document, we will assume that we are using 'ethernet1/1' as the public interface and 'ethernet1/2' as the private interface. If aggregated interfaces where used, you would use something like 'ae1' and 'ae2' as the interfaces."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:128
+# 2831a742f496425ba96db130e37c9fdf
+msgid "This implementation requires that the 'Interface Type' be set to 'Layer3' for both the public and private interfaces. If you want to be able to use the 'Untagged' VLAN tag for public traffic in CloudStack, you will need to enable support for it in the public 'ethernet1/1' interface (details below)."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:133
+# 7c752ebb778a47f5ab20ddd8e7c2c88d
+msgid "**Steps to configure the Public Interface**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:135
+#: ../../networking/palo_alto_config.rst:171
+#: ../../networking/palo_alto_config.rst:228
+# 5700c7ece81b43cb98c6727c752735b2
+# e49c5cac5b754c67a068eb76b8f2b016
+# de7a1d67b1d944d9a9282e1481b27948
+msgid "Log into Palo Alto Networks Firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:137
+#: ../../networking/palo_alto_config.rst:230
+# 084f3f60d58341c1bb8a4c5902758909
+# ef024b35b5944a84b02459069f6213a1
+msgid "Navigate to 'Network > Interfaces'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:139
+# f9c2ae1f0de249878828ead2f5703582
+msgid "Click on 'ethernet1/1' (for aggregated ethernet, it will probably be called 'ae1')"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:142
+#: ../../networking/palo_alto_config.rst:155
+# 04a63a60ad414b7e81b979d479bae1fd
+# 04da4ad3a88d4e6cba3ee5b4668f9ee2
+msgid "Select 'Layer3' from the 'Interface Type' list"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:144
+# ff872b1bbd2945db9cce189792e38246
+msgid "Click 'Advanced'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:146
+# 944d68b812d8463a87b69f9d882e8b28
+msgid "Check the 'Untagged Subinterface' check-box"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:148
+#: ../../networking/palo_alto_config.rst:157
+#: ../../networking/palo_alto_config.rst:193
+#: ../../networking/palo_alto_config.rst:195
+#: ../../networking/palo_alto_config.rst:265
+#: ../../networking/palo_alto_config.rst:339
+#: ../../networking/palo_alto_config.rst:388
+#: ../../networking/palo_alto_config.rst:426
+#: ../../networking/palo_alto_config.rst:455
+# 290ce1b89ac441bcbc6691b3a41534a6
+# ac12e64f14884682ba033e7f2177cc9b
+# 8f94cc2074684065a79e57cf90d6ab9a
+# 8a83b222380740918936aca1feee32b9
+# f18ef2d3aeac41389cdfd198b83c5467
+# 95a5afc210324dab8a21ba2da8e6801c
+# d765a343c5f146639728c4ea3493e250
+# 8b7efac976c241fe9f3fa33963361d5a
+# 8a61018dde394d37b9ca3df99d188ee5
+msgid "Click 'OK'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:150
+# 8b5c88e0cc8242a580db731046cce5d3
+msgid "**Steps to configure the Private Interface**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:152
+# a94612c3076e4722bd18904180a04114
+msgid "Click on 'ethernet1/2' (for aggregated ethernet, it will probably be called 'ae2')"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:162
+# 0beaed2fa39442e887eaca261cae62d7
+msgid "Configure a Virtual Router on the firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:164
+# 22d2fb39f9f44f928787ed03f4aa558c
+msgid "The Virtual Router on the Palo Alto Networks Firewall is not to be confused with the Virtual Routers that CloudStack provisions. For this implementation, the Virtual Router on the Palo Alto Networks Firewall will ONLY handle the upstream routing from the Firewall to the next hop."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:169
+# e11103f99e6d45d0bea4183b1cf60c98
+msgid "**Steps to configure the Virtual Router**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:173
+# d520996f46e84c8c94ce274dd654f3cb
+msgid "Navigate to 'Network > Virtual Routers'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:175
+# e966f3781b904686b55509eef9892346
+msgid "Select the 'default' Virtual Router or Add a new Virtual Router if there are none in the list"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:178
+# 9cbe5a8debc5407fb6918d33d5b71aab
+msgid "If you added a new Virtual Router, you will need to give it a 'Name'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:180
+# b6a107e3fda3444fbcc24365b6ee33ca
+msgid "Navigate to 'Static Routes > IPv4'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:182
+# 6efcbc75fe144976b8a75a2dd888c615
+msgid "'Add' a new static route"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:184
+# ed78234999764665912475eb992e6395
+msgid "**Name**: next_hop (you can name it anything you want)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:186
+# 47efb66b283043aa89a78ad4c6a87339
+msgid "**Destination**: 0.0.0.0/0 (send all traffic to this route)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:188
+# f9dde0e9e0534954bf1da5b6bf535824
+msgid "**Interface**: ethernet1/1 (or whatever you set your public interface as)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:191
+# 1e8a9818e50544a19445ee39589e5215
+msgid "**Next Hop**: (specify the gateway IP for the next hop in your network)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:200
+# f26446d9a67c4620a0f511145ecfde2b
+msgid "Configure the default Public Subinterface"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:202
+# 7225aebfeb604bd7ad6ffa6bd19425c3
+msgid "The current implementation of the Palo Alto Networks firewall integration uses CIDRs in the form of 'w.x.y.z/32' for the public IP addresses that CloudStack provisions. Because no broadcast or gateway IPs are in this single IP range, there is no way for the firewall to route the traffic for these IPs. To route the traffic for these IPs, we create a single subinterface on the public interface with an IP and a CIDR which encapsulates the CloudStack public IP range. This IP will need to be inside the subnet defined by the CloudStack public range netmask, but outside the CloudStack public IP range. The CIDR should reflect the same subnet defined by the CloudStack public range netmask. The name of the subinterface is determined by the VLAN configured for the public range in CloudStack."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:214
+# 3c781eec6bac4e599027b694351c3cd4
+msgid "To clarify this concept, we will use the following example."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:216
+# 9637f4b7396f4c51983c5bf87b43e912
+msgid "**Example CloudStack Public Range Configuration**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:218
+# 8a3070e081974ca68cc0375eca88007b
+msgid "**Gateway**: 172.30.0.1"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:220
+# 9f64613849464823b633f1d16645d42e
+msgid "**Netmask**: 255.255.255.0"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:222
+# 9330fe95cfaf44abbdb0d4f38e739dde
+msgid "**IP Range**: 172.30.0.100 - 172.30.0.199"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:224
+# 435b6fb99438485f877a6756893298bf
+msgid "**VLAN**: Untagged"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:226
+# eb956dfff226492fa1b0806cbbf743dc
+msgid "**Configure the Public Subinterface**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:232
+# 2c3eb0c3c7e642cbb78583a57bc43be3
+msgid "Select the 'ethernet1/1' line (not clicking on the name)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:234
+# 739221cdf0024efc9b93b1d76646825b
+msgid "Click 'Add Subinterface' at the bottom of the window"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:236
+# 6b8490f4a2684ca8ad9814a1461edaaa
+msgid "Enter 'Interface Name': 'ethernet1/1' . '9999'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:238
+# fb030c9c7b044a0185fe843def4a3bb5
+msgid "9999 is used if the CloudStack public range VLAN is 'Untagged'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:240
+# 912e1187e17b414f9493ddb7f368b068
+msgid "If the CloudStack public range VLAN is tagged (eg: 333), then the name will reflect that tag"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:243
+# 4472ddfa3e6f4c878a16d411cc343a7d
+msgid "The 'Tag' is the VLAN tag that the traffic is sent to the next hop with, so set it accordingly. If you are passing 'Untagged' traffic from CloudStack to your next hop, leave it blank. If you want to pass tagged traffic from CloudStack, specify the tag."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:248
+# f1ede2abd59c4fcc914acf233aa4b38c
+msgid "Select 'default' from the 'Config > Virtual Router' drop-down (assuming that is what your virtual router is called)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:251
+# 0d7f8743ae7e405c833390569c1a342c
+msgid "Click the 'IPv4' tab"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:253
+# 93bc9ae7b5f346f99a40644725c2ebc0
+msgid "Select 'Static' from the 'Type' radio options"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:255
+# 661bc9fb00f342d58bfd39624ff5f72a
+msgid "Click 'Add' in the 'IP' section"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:257
+# b3482058794d4e2abb1e0a1f41bee8fa
+msgid "Enter '172.30.0.254/24' in the new line"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:259
+# 02e03b2878504ed9a7ee888b36978cd4
+msgid "The IP can be any IP outside the CloudStack public IP range, but inside the CloudStack public range netmask (it can NOT be the gateway IP)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:262
+# 925fe2a4b10d4cb1ab438e2de318af0a
+msgid "The subnet defined by the CIDR should match the CloudStack public range netmask"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:269
+# 10d6dd9ed3af49ffad4020de805389de
+msgid "Commit configuration on the Palo Alto Networks Firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:271
+# 89ac6f1b3c694a06b75008f8eec59b16
+msgid "In order for all the changes we just made to take effect, we need to commit the changes."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:274
+# 3137cac6d6e14fc9904a5fa154e3905d
+msgid "Click the 'Commit' link in the top right corner of the window"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:276
+# f3aaf9f819ef410fba6edbc621ea6a4d
+msgid "Click 'OK' in the commit window overlay"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:278
+# 3b4acc9911434ddc83362cedcacab668
+msgid "Click 'Close' to the resulting commit status window after the commit finishes"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:284
+# 6bb86113a96547538dbfd01db7c9e7ae
+msgid "Setup the Palo Alto Networks Firewall in CloudStack"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:287
+# b8515e0d94ef4d4a865f64f7bef85482
+msgid "Add the Palo Alto Networks Firewall as a Service Provider"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:289
+# 9b19a32893484d2fac28f3558f2643b5
+msgid "Navigate to 'Infrastructure > Zones > ZONE_NAME > Physical Network > NETWORK_NAME (guest) > Configure; Network Service Providers'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:292
+# 9bdf06473baa43cd9c6b8cb17a6313c3
+msgid "Click on 'Palo Alto' in the list"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:294
+# 8565a2ab22994798a9167083879136f7
+msgid "Click 'View Devices'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:296
+# d10162d1e53c40e6bd448e05bb8a3259
+msgid "Click 'Add Palo Alto Device'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:298
+# c6fcd95bacbf4675951227d95a5737fc
+msgid "Enter your configuration in the overlay. This example will reflect the details previously used in this guide."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:301
+# 1d34f716f84e4296a01fd3f7afde7356
+msgid "**IP Address**: (the IP of the Palo Alto Networks Firewall)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:303
+# add3b3461b6b48d7b74f94961a7b26e1
+msgid "**Username**: (the admin username for the firewall)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:305
+# 708228ac2edb498f9fd079d05a8a7511
+msgid "**Password**: (the admin password for the firewall)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:307
+# b2a6f266de904ebe94805b3176617484
+msgid "**Type**: Palo Alto Firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:309
+# 1cc218519592430f98cc8e009d0c8f2c
+msgid "**Public Interface**: ethernet1/1 (use what you setup earlier as the public interface if it is different from my examples)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:312
+# 5f1c1837d4df4e65a7a8abd05abd43ce
+msgid "**Private Interface**: ethernet1/2 (use what you setup earlier as the private interface if it is different from my examples)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:315
+# dd40b4143070449bb34ede04b3fe467e
+msgid "**Number of Retries**: 2 (the default is fine)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:317
+# 1d8080f41f894087b6e0a8c4c934dfe9
+msgid "**Timeout**: 300 (the default is fine)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:319
+# 876888b0168e496a897f306b246db971
+msgid "**Public Network**: untrust (this is the public zone on the firewall and did not need to be configured)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:322
+# 920274e528a341fb8962b73ff4b77179
+msgid "**Private Network**: trust (this is the private zone on the firewall and did not need to be configured)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:325
+# 2072277d3e14495aa762454838f72995
+msgid "**Virtual Router**: default (this is the name of the Virtual Router we setup on the firewall)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:328
+# 0376444c2cbd4404ad01b614aac5c07f
+msgid "**Palo Alto Threat Profile**: (not required. name of the 'Security Profile Groups' to apply. more details in the 'Additional Features' section)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:332
+# e649ac1802774500b5003c708987fe74
+msgid "**Palo Alto Log Profile**: (not required. name of the 'Log Forwarding' profile to apply. more details in the 'Additional Features' section)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:335
+# 32094fb7d72248d28b8f84e1fd56e988
+msgid "**Capacity**: (not required)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:337
+# 7e33721fb17a48e2ab7aa2d1b1dc460c
+msgid "**Dedicated**: (not required)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:341
+# dbef98d732fc4f7fbbad776d1b61f41e
+msgid "Click on 'Palo Alto' in the breadcrumbs to go back one screen."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:343
+# e499e22a30754ab4acfd6a779b03ea97
+msgid "Click on 'Enable Provider' |EnableDisableFeature.png|"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:347
+# b7b0fa1a4629430b839286b55162f882
+msgid "Add a Network Service Offering to use the new Provider"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:349
+# 1cc4ca671df7479c96ab873e7ae0cc68
+msgid "There are 6 'Supported Services' that need to be configured in the network service offering for this functionality. They are DHCP, DNS, Firewall, Source NAT, Static NAT and Port Forwarding. For the other settings, there are probably additional configurations which will work, but I will just document a common case."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:355
+# f406f98a91684fd1bd4947a0b06ed1a2
+msgid "Navigate to 'Service Offerings'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:357
+# 942ee3b426ba4d88acfbee186446dcaf
+msgid "In the drop-down at the top, select 'Network Offerings'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:359
+# 6d216de0290941758439b72593f8a6c8
+msgid "Click 'Add Network Offering'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:361
+# da673cd57e5d4dadaaa406cb5fa5ec13
+msgid "**Name**: (name it whatever you want)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:363
+# a59e3d821172494d9efb8de1253d352d
+msgid "**Description**: (again, can be whatever you want)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:365
+# bdb32fa4fdf545d2886707aa7ca1156d
+msgid "**Guest Type**: Isolated"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:367
+# ee73168cca234bf08581ec3131ec5bb8
+msgid "**Supported Services**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:369
+# 320e8c3f0b9b49ac8768926d267e94d7
+msgid "**DHCP**: Provided by 'VirtualRouter'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:371
+# 4c6b47d1b7b34586863177a90b865d85
+msgid "**DNS**: Provided by 'VirtualRouter'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:373
+# 56ac8260b8a3496ca38997dfc58dae3f
+msgid "**Firewall**: Provided by 'PaloAlto'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:375
+# fb63dd0553724890988f01e52cc9fb1a
+msgid "**Source NAT**: Provided by 'PaloAlto'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:377
+# 4cdf39f3041d47699f285f61fcf0ac95
+msgid "**Static NAT**: Provided by 'PaloAlto'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:379
+# bfbb888f85ab4e179965cac8c6d8dadb
+msgid "**Port Forwarding**: Provided by 'PaloAlto'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:381
+# 88e886aff4204f32811dff6e4d8ea019
+msgid "**System Offering for Router**: System Offering For Software Router"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:383
+# 8f0e43a7d0f34b9992263fdfdcfcd2d6
+msgid "**Supported Source NAT Type**: Per account (this is the only supported option)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:386
+# e06e5423d74c4f328eae1e741028734b
+msgid "**Default egress policy**: (both 'Allow' and 'Deny' are supported)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:390
+# 59c525fe149a425098205f41b21a9cf1
+msgid "Click on the newly created service offering"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:392
+# 44fc81442fe34d68a2728f0ca0a160dc
+msgid "Click 'Enable network offering' |EnableDisableFeature.png|"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:394
+# 934d3259e9bf44c083323e6b2f2aa9bf
+msgid "When adding networks in CloudStack, select this network offering to use the Palo Alto Networks firewall."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:399
+# fae8d19c649e479f99c6b2edd49434eb
+msgid "Additional Features"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:401
+# 9dc0b83948d74e16b3ad351d1210f5b5
+msgid "In addition to the standard functionality exposed by CloudStack, we have added a couple additional features to this implementation. We did not add any new screens to CloudStack, but we have added a couple fields to the 'Add Palo Alto Service Provider' screen which will add functionality globally for the device."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:408
+# 5af1e576fa7847f7b87eed5fe35e77b8
+msgid "Palo Alto Networks Threat Profile"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:410
+# 9070542c237349599f645efcd8a64128
+msgid "This feature allows you to specify a 'Security Profile Group' to be applied to all of the firewall rules which are created on the Palo Alto Networks firewall device."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:414
+# a4257973d0524640b7102968817ca7e5
+msgid "To create a 'Security Profile Group' on the Palo Alto Networks firewall, do the following:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:417
+#: ../../networking/palo_alto_config.rst:446
+# 77a31bab19cd4e55b4cc13c92cb328bb
+# 92409a68a6f345c89e059f0a26e707ee
+msgid "Log into the Palo Alto Networks firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:419
+# 2b0227f96b854d92bf96e91d9c17435c
+msgid "Navigate to 'Objects > Security Profile Groups'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:421
+# 2405f37aad834c34b4360f784ce6ec69
+msgid "Click 'Add' at the bottom of the page to add a new group"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:423
+# 7e5ffff8c26545c48b07a4921ca76a52
+msgid "Give the group a Name and specify the profiles you would like to include in the group"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:428
+#: ../../networking/palo_alto_config.rst:457
+# 3e3d4bfaa14c46c38499c68ce4f36095
+# 547b08aaaf164fb68c2b8f1b37d09793
+msgid "Click the 'Commit' link in the top right of the screen and follow the on screen instructions"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:431
+# a31ebe4cd3bf4bf9b7e3fe8d35c32f63
+msgid "Once you have created a profile, you can reference it by Name in the 'Palo Alto Threat Profile' field in the 'Add the Palo Alto Networks Firewall as a Service Provider' step."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:437
+# 735566ed2935434ea67f2e2595c3f686
+msgid "Palo Alto Networks Log Forwarding Profile"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:439
+# c229e4bdb0c04fac952295035d8afa6b
+msgid "This feature allows you to specify a 'Log Forwarding' profile to better manage where the firewall logs are sent to. This is helpful for keeping track of issues that can arise on the firewall."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:443
+# 461ea8be12674fcd842217cf72c68f7f
+msgid "To create a 'Log Forwarding' profile on the Palo Alto Networks Firewall, do the following:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:448
+# a61142f77e8941e9b976c01cd1aa9f89
+msgid "Navigate to 'Objects > Log Forwarding'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:450
+# ea14dff9d3c448f0976b6aebe2d119cc
+msgid "Click 'Add' at the bottom of the page to add a new profile"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:452
+# 1352f9adcbd94a24a5429e2ed53caa48
+msgid "Give the profile a Name and specify the details you want for the traffic and threat settings"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:460
+# 6b304cde8312467ebef3f110a46fce1a
+msgid "Once you have created a profile, you can reference it by Name in the 'Palo Alto Log Profile' field in the 'Add the Palo Alto Networks Firewall as a Service Provider' step."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:467
+# 7ba0d11bde5b4c3e97de4830b0aecc15
+msgid "Limitations"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:469
+# 796314d492b54823a652a3f50d430629
+msgid "The implementation currently only supports a single public IP range in CloudStack"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:472
+# c8e8545461454cb9acf0a06bf42b95c0
+msgid "Usage tracking is not yet implemented"
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/persistent_networks.pot b/source/adminguide/locale/pot/networking/persistent_networks.pot
new file mode 100644
index 0000000..5db6bc1
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/persistent_networks.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 <EMAIL@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 <EMAIL@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/persistent_networks.rst:18
+# 4083b4f8962d4ce2add5a637beceaf4d
+msgid "Persistent Networks"
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:20
+# 5157cfe530594f5f954a8a8e1525ce10
+msgid "The network that you can provision without having to deploy any VMs on it is called a persistent network. A persistent network can be part of a VPC or a non-VPC environment."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:24
+# 469fa7c5517f4f82b49e9015b0027b0f
+msgid "When you create other types of network, a network is only a database entry until the first VM is created on that network. When the first VM is created, a VLAN ID is assigned and the network is provisioned. Also, when the last VM is destroyed, the VLAN ID is released and the network is no longer available. With the addition of persistent network, you will have the ability to create a network in CloudStack in which physical devices can be deployed without having to run any VMs. Additionally, you can deploy physical devices on that network."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:33
+# 87f88f46858c41ba96f785b7c3122342
+msgid "One of the advantages of having a persistent network is that you can create a VPC with a tier consisting of only physical devices. For example, you might create a VPC for a three-tier application, deploy VMs for Web and Application tier, and use physical machines for the Database tier. Another use case is that if you are providing services by using physical hardware, you can define the network as persistent and therefore even if all its VMs are destroyed the services will not be discontinued."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:44
+# 68622842a6474e23b5b4ace4928a7f02
+msgid "Persistent Network Considerations"
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:46
+# bd289a0ef0dc4ef1b5a6acb8b9ad0c38
+msgid "Persistent network is designed for isolated networks."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:48
+# 10b2b9266df84efcb8fb9002316e3f11
+msgid "All default network offerings are non-persistent."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:50
+# d9e8d354f6bc4b6f8194156ed112a537
+msgid "A network offering cannot be editable because changing it affects the behavior of the existing networks that were created using this network offering."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:54
+# 80b8615033b54141b06d3d7a311809bf
+msgid "When you create a guest network, the network offering that you select defines the network persistence. This in turn depends on whether persistent network is enabled in the selected network offering."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:58
+# 5e5d6fc784af4dec8e15481000f5125f
+msgid "An existing network can be made persistent by changing its network offering to an offering that has the Persistent option enabled. While setting this property, even if the network has no running VMs, the network is provisioned."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:63
+# 30e1aaa119a34adcb9a57e513d705745
+msgid "An existing network can be made non-persistent by changing its network offering to an offering that has the Persistent option disabled. If the network has no running VMs, during the next network garbage collection run the network is shut down."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:68
+# 1fafa4f8c2e8475e984703fe2e4c29ba
+msgid "When the last VM on a network is destroyed, the network garbage collector checks if the network offering associated with the network is persistent, and shuts down the network only if it is non-persistent."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:75
+# 6302571eba5d408687957bd3759816c3
+msgid "Creating a Persistent Guest Network"
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:77
+# c3876e9bd8d449b489101f5ac1bae458
+msgid "To create a persistent network, perform the following:"
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:79
+# 99fe5f5c722844089e5bdbcdadb22fc0
+msgid "Create a network offering with the Persistent option enabled."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:81
+# 16d2470643ab4777a40f35f26a9de70c
+msgid "See `\"Creating a New Network Offering\" <networking.html#creating-a-new-network-offering>`_."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:84
+# 267c8937d18548498e620897ef0e587e
+msgid "Select Network from the left navigation pane."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:86
+# bc4568a29a4149c797c11839057e9538
+msgid "Select the guest network that you want to offer this network service to."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:89
+# ecdb6f1a35444f46acd9620f3305b060
+msgid "Click the Edit button."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:91
+# 5bda22ffd010416cb80b2848179d18fa
+msgid "From the Network Offering drop-down, select the persistent network offering you have just created."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:94
+# fd7fed942171405cb30c3ea00f4111cb
+msgid "Click OK."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/portable_ips.pot b/source/adminguide/locale/pot/networking/portable_ips.pot
new file mode 100644
index 0000000..d21b851
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/portable_ips.pot
@@ -0,0 +1,210 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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/portable_ips.rst:18
+# 0d718ef9845940f3b45f93fdedd55a80
+msgid "Portable IPs"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:21
+# 7dbdc94b3c7148f3a67dd212137b1b78
+msgid "About Portable IP"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:23
+# a4b9041cb1da4c7c9185978b3bd46328
+msgid "Portable IPs in CloudStack are region-level pool of IPs, which are elastic in nature, that can be transferred across geographically separated zones. As an administrator, you can provision a pool of portable public IPs at region level and are available for user consumption. The users can acquire portable IPs if admin has provisioned portable IPs at the region level they are part of. These IPs can be use for any service within an advanced zone. You can also use portable IPs for EIP services in basic zones."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:32
+# 824ded2676d34d4b8d60fd93b08f58c8
+msgid "The salient features of Portable IP are as follows:"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:34
+# 1f57b59fbbbd426b9b2fd6f4dffaa0d2
+msgid "IP is statically allocated"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:36
+# 1759d65d5ed34db283d80b85d56f486a
+msgid "IP need not be associated with a network"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:38
+# 6826b76a9eea4332a6c068382f8b050c
+msgid "IP association is transferable across networks"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:40
+# ae7460bc9900474fbf94402165b9cb7e
+msgid "IP is transferable across both Basic and Advanced zones"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:42
+# 770563314c044da6acca6641fce5f500
+msgid "IP is transferable across VPC, non-VPC isolated and shared networks"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:44
+# ea55d3113555412f8f8a2bbf4f6b0846
+msgid "Portable IP transfer is available only for static NAT."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:48
+# 2ff5ef4c14bb4585a2e7c5c7458d25fe
+msgid "Guidelines"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:50
+# 662d9610efd3460aae2192eea97c7bd6
+msgid "Before transferring to another network, ensure that no network rules (Firewall, Static NAT, Port Forwarding, and so on) exist on that portable IP."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:56
+# d276865047e64a7f9cdddb63ad28d313
+msgid "Configuring Portable IPs"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:58
+#: ../../networking/portable_ips.rst:90
+# b085a9f5f2ce4744b86603f26196b283
+# a28f4db3b1734d3c9f0aa6cada34dab5
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:60
+# 2f850a50ddab404d9df06aa0338d6479
+msgid "In the left navigation, click Regions."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:62
+# 316a2bbd2c69469597356b663e5135ba
+msgid "Choose the Regions that you want to work with."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:64
+# c66c2dfa7575447e82396eeff33e1315
+msgid "Click View Portable IP."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:66
+# cd5798170b724d0abe4461ee8779eded
+msgid "Click Portable IP Range."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:68
+# 09d0a8e2201a44acbe61f89c2ebdba6b
+msgid "The Add Portable IP Range window is displayed."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:70
+# 9c9681bfaca543f09522720f86b05c3b
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:72
+# 2832d8a453bf4a27a01dfbe6ade2c252
+msgid "**Start IP/ End IP**: A range of IP addresses that are accessible from the Internet and will be allocated to guest VMs. Enter the first and last IP addresses that define a range that CloudStack can assign to guest VMs."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:77
+# ea589b30c39d429c86fd50fe49515dd7
+msgid "**Gateway**: The gateway in use for the Portable IP addresses you are configuring."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:80
+# 9d8360b75a254007b307c9ba1341550d
+msgid "**Netmask**: The netmask associated with the Portable IP range."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:82
+# 60ed534104ce48fdb9586f72c61b379f
+msgid "**VLAN**: The VLAN that will be used for public traffic."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:84
+# 8615e1020e2747f0ba31cd4cb186a010
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:88
+# d88ec64c255243049a67ed2616530031
+msgid "Acquiring a Portable IP"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:92
+# b933b6d78fe94153a35b24d2ccfd8e06
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:94
+# 2f46ac57574a4ff3833cd3af46386463
+msgid "Click the name of the network where you want to work with."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:96
+# a7dc83315ae746af830094d45cfe7c11
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:98
+# 64b8eac8ac21402293c2fff5d435a7eb
+msgid "Click Acquire New IP."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:100
+# 4a739787a6194df09e032797d1fe0911
+msgid "The Acquire New IP window is displayed."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:102
+# c8424da0e97a443f9d01fab04339184f
+msgid "Specify whether you want cross-zone IP or not."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:104
+# 222f964df0914c01bf92a5a5f461d4cc
+msgid "Click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:106
+# 97dbf547785f4b1aaea165efca4b50a9
+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 ""
+
+#: ../../networking/portable_ips.rst:112
+# b84bba5db56047ba9dcd10cad9a14c3a
+msgid "Transferring Portable IP"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:114
+# f9ff7b7ea0d541a2bb6530a633a01f8b
+msgid "An IP can be transferred from one network to another only if Static NAT is enabled. However, when a portable IP is associated with a network, you can use it for any service in the network."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:118
+# 2112dfc5676e4e7fbeb783e1bdbafb8d
+msgid "To transfer a portable IP across the networks, execute the following API:"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:125
+# 794e73bb89214a29bc9257f2fc58c178
+msgid "Replace the UUID with appropriate UUID. For example, if you want to transfer a portable IP to network X and VM Y in a network, execute the following:"
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/public_ips_and_vlans_for_accounts.pot b/source/adminguide/locale/pot/networking/public_ips_and_vlans_for_accounts.pot
new file mode 100644
index 0000000..4d6abc6
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/public_ips_and_vlans_for_accounts.pot
@@ -0,0 +1,261 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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/public_ips_and_vlans_for_accounts.rst:18
+# e16ce84ab27a470389c600bd7f1937e6
+msgid "Reserving Public IP Addresses and VLANs for Accounts"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:20
+# d20bf40a65964aee8e9477cfb99a8d76
+msgid "CloudStack provides you the ability to reserve a set of public IP addresses and VLANs exclusively for an account. During zone creation, you can continue defining a set of VLANs and multiple public IP ranges. This feature extends the functionality to enable you to dedicate a fixed set of VLANs and guest IP addresses for a tenant."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:26
+# e0cd381debc1495fa88b0bed963e8b16
+msgid "Note that if an account has consumed all the VLANs and IPs dedicated to it, the account can acquire two more resources from the system. CloudStack provides the root admin with two configuration parameter to modify this default behavior: use.system.public.ips and use.system.guest.vlans. These global parameters enable the root admin to disallow an account from acquiring public IPs and guest VLANs from the system, if the account has dedicated resources and these dedicated resources have all been consumed. Both these configurations are configurable at the account level."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:36
+# baef2538501f4f729cd5b4f69fbbefaa
+msgid "This feature provides you the following capabilities:"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:38
+# 4e16f6283a6e4f389b44d3af88cc4364
+msgid "Reserve a VLAN range and public IP address range from an Advanced zone and assign it to an account"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:41
+# c67672fcea6c4ae69a5c3c7d8fbd6a33
+msgid "Disassociate a VLAN and public IP address range from an account"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:43
+# 8451f0b840ab420cb1589fcc1572e6c0
+msgid "View the number of public IP addresses allocated to an account"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:45
+# 2a183b234d9c44b8b99fa31594f06e38
+msgid "Check whether the required range is available and is conforms to account limits."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:48
+# be8cff382a7748e4a75c68c3f8aa3dd7
+msgid "The maximum IPs per account limit cannot be superseded."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:52
+# 17f5e888607c4537816aa2f2e8b7c363
+msgid "Dedicating IP Address Ranges to an Account"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:54
+# 5409cfc1bd6f4b41bdd23eee4d6b9396
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:56
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:126
+# b8615267486a44ff8ee964b26529f16d
+# ba51a55851504a869dc0f28d293993ad
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:58
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:128
+# b1c57a90f0c843c4906f95e699dd7d13
+# 2a38ee721dc8442f850ff993fa52de59
+msgid "In Zones, click View All."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:60
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:130
+# defb870416a14ff0a7ea37bf68b8e890
+# 207025dba9b843299213868bf721e0d2
+msgid "Choose the zone you want to work with."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:62
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:132
+# 04eaa49757a64adf830002153cf8db20
+# cea8888967a844ccbb283c973f4b9482
+msgid "Click the Physical Network tab."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:64
+# fd016a6c74fa4aceb46c592a01f82621
+msgid "In the Public node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:66
+# abe4deb76feb40fd9fa6dd1461e1dec3
+msgid "Click the IP Ranges tab."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:68
+# 3686de2bd0e24c578fb64abcd3b86fbc
+msgid "You can either assign an existing IP range to an account, or create a new IP range and assign to an account."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:71
+# 90bc5a3040c541cb95831323867cee7d
+msgid "To assign an existing IP range to an account, perform the following:"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:73
+# 196250a3ddc54abc978d437ea8ba3f96
+msgid "Locate the IP range you want to work with."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:75
+# 0a707d3297ad4ccfa38f80baa7690816
+msgid "Click Add Account |addAccount-icon.png| button."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:77
+# 3aaf2af3bb8f4c9485ae2e0ada7aee73
+msgid "The Add Account dialog is displayed."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:79
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:89
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:107
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:142
+# b99e236f412f4946af47669c8d62396e
+# eedc80b2aa5c4c8696da4d4b51a28179
+# 39b98908344542aeb2e40bdbf9550571
+# f6dc925b4c634b9fa0523254d12380bb
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:81
+# 64e4bf3c9f034ef4adb32087be1bc7aa
+msgid "**Account**: The account to which you want to assign the IP address range."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:84
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:112
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:150
+# d15ca620e8154bf9ad213a256496e6e0
+# 09ac68b8a6f24e84b36a726d6058809b
+# f8da528d9cdd447fb262d7ca5542308f
+msgid "**Domain**: The domain associated with the account."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:86
+# 06d6686b378e4a22a762e94353aee862
+msgid "To create a new IP range and assign an account, perform the following:"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:91
+# dd52a8808d1b44e7ba133f213439d71d
+msgid "**Gateway**"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:93
+# 781ca41349a949cca28101dfea1676d5
+msgid "**Netmask**"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:95
+# 1b745bfb0a6443e1a0f947860308e044
+msgid "**VLAN**"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:97
+# 9526ce220e2941459d408f259d6e9b30
+msgid "**Start IP**"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:99
+# a55c7588b51f4a84afa7fa78fc58ed5e
+msgid "**End IP**"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:101
+# 9282436854274ee485b8c2df6ba7f342
+msgid "**Account**: Perform the following:"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:103
+# 678fa43c9d524b8fbb3ca453d599d6f1
+msgid "Click Account."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:105
+# 58e785cf6c3f4544af852a60e9ff4639
+msgid "The Add Account page is displayed."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:109
+# c1b6c5a339b940b7907cfc3fd14b35d6
+msgid "**Account**: The account to which you want to assign an IP address range."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:115
+# e54b45158ec1469392091a64574cbb55
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:117
+# cbf3d4473399404684b33c48a92e0148
+msgid "Click Add."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:121
+# 8d933442217c4288b95b7ed71f57b95f
+msgid "Dedicating VLAN Ranges to an Account"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:123
+# d7e1ce8c0be24d57b606cd1a7b4ac29e
+msgid "After the CloudStack Management Server is installed, log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:134
+# 68317dc975da4182878b75c19ec73b1e
+msgid "In the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:136
+# de0ffdc9f48d4d068a50a53f85c49cea
+msgid "Select the Dedicated VLAN Ranges tab."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:138
+# d7319cdb148746849dba29b0a020ce01
+msgid "Click Dedicate VLAN Range."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:140
+# 6037b47944d9429aad5df0dd7981dace
+msgid "The Dedicate VLAN Range dialog is displayed."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:144
+# 564cf1e324b54969924910efd7c3f00b
+msgid "**VLAN Range**: The VLAN range that you want to assign to an account."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:147
+# b2c4b566d49c4a3b99b3268f4e867233
+msgid "**Account**: The account to which you want to assign the selected VLAN range."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/releasing_an_ip_address.pot b/source/adminguide/locale/pot/networking/releasing_an_ip_address.pot
new file mode 100644
index 0000000..0a982ef
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/releasing_an_ip_address.pot
@@ -0,0 +1,58 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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/releasing_an_ip_address.rst:18
+# c50d06f60c5d483ba5f4799c50384e9c
+msgid "Releasing an IP Address"
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:20
+# 3a245bdefb444425ad5f7bd6a1ea5de2
+msgid "When the last rule for an IP address is removed, you can release that IP address. The IP address still belongs to the VPC; however, it can be picked up for any guest network again."
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:24
+# 99e24197740148e683aa3ffad5870800
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:26
+# da80f79b21a846878018930987c87ffd
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:28
+# 24863c020eb04ba9808fc2e0f24e0760
+msgid "Click the name of the network where you want to work with."
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:30
+# 1e70144ba5394954a2c92850335b7555
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:32
+# 3f542514484849b1bfde31aa95ec3a25
+msgid "Click the IP address you want to release."
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:34
+# 7851cee0ec9c4ea3a8d5309aa5f84d40
+msgid "Click the Release IP button. |ReleaseIPButton.png|"
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/remote_access_vpn.pot b/source/adminguide/locale/pot/networking/remote_access_vpn.pot
new file mode 100644
index 0000000..b7806e1
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/remote_access_vpn.pot
@@ -0,0 +1,997 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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/remote_access_vpn.rst:18
+# 037fa60a2e2f4601bf22e714a97fe0fd
+msgid "Remote Access VPN"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:20
+# 8202b8f150584992995c6c6f69a2c907
+msgid "CloudStack account owners can create virtual private networks (VPN) to access their virtual machines. If the guest network is instantiated from a network offering that offers the Remote Access VPN service, the virtual router (based on the System VM) is used to provide the service. CloudStack provides a L2TP-over-IPsec-based remote access VPN service to guest virtual networks. Since each network gets its own virtual router, VPNs are not shared across the networks. VPN clients native to Windows, Mac OS X and iOS can be used to connect to the guest networks. The account owner can create and manage users for their VPN. CloudStack does not use its account database for this purpose but uses a separate table. The VPN user database is shared across all the VPNs created by the account owner. All VPN users get access to all VPNs created by the account owner."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:35
+# a8a54e6134ab4ebaae71aeb42d0ad32b
+msgid "Make sure that not all traffic goes through the VPN. That is, the route installed by the VPN should be only for the guest network and not for all traffic."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:39
+# a107bc4ab6624b839681adafc00d60e1
+msgid "**Road Warrior / Remote Access**. Users want to be able to connect securely from a home or office to a private network in the cloud. Typically, the IP address of the connecting client is dynamic and cannot be preconfigured on the VPN server."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:44
+# 7b5e742bfe7f429794320cf1c32ffdfc
+msgid "**Site to Site**. In this scenario, two private subnets are connected over the public Internet with a secure VPN tunnel. The cloud user's subnet (for example, an office network) is connected through a gateway to the network in the cloud. The address of the user's gateway must be preconfigured on the VPN server in the cloud. Note that although L2TP-over-IPsec can be used to set up Site-to-Site VPNs, this is not the primary intent of this feature. For more information, see \":ref:`setting-s2s-vpn-conn`\"."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:55
+# 3411c8387ca84f18bd032795907f4585
+msgid "Configuring Remote Access VPN"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:57
+# b5e1d88079c447ba9d2baa0e3f5cf685
+msgid "To set up VPN for the cloud:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:59
+#: ../../networking/remote_access_vpn.rst:301
+#: ../../networking/remote_access_vpn.rst:411
+#: ../../networking/remote_access_vpn.rst:431
+#: ../../networking/remote_access_vpn.rst:493
+#: ../../networking/remote_access_vpn.rst:624
+# 85153916f2a94aeb80faa2c9f22cfcea
+# e7cff502f3494c00b665a1b732e05fb1
+# 7fd5ac75573d435b8c164435b6b50404
+# ab1f2323529a48e8a071e9baa44284e3
+# 6dfbddbad973426b8d6704da05fb2166
+# ce7c03a477b84c029914728fac5f85d5
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:61
+# ef4d98e4df0149d797b4aebfc0dbdc03
+msgid "In the left navigation, click Global Settings."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:63
+# 6915f23eef3f4ddfaf19ba566058535d
+msgid "Set the following global configuration parameters."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:65
+# b46467b5e34e436389d14380f0094d63
+msgid "remote.access.vpn.client.ip.range - The range of IP addresses to be allocated to remote access VPN clients. The first IP in the range is used by the VPN server."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:69
+# ad4d961d0bf3453ebc21a59b09ad0207
+msgid "remote.access.vpn.psk.length - Length of the IPSec key."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:71
+# a89aef80d75a49a9bf21eed458b3a570
+msgid "remote.access.vpn.user.limit - Maximum number of VPN users per account."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:74
+# 115f9b2e63704bd7b8d0880401243098
+msgid "To enable VPN for a particular network:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:76
+#: ../../networking/remote_access_vpn.rst:101
+# 1cbcce1e10884bc0906f10625b02b967
+# d3065ab6ac634b4ab6d37d5cc5f6b0f8
+msgid "Log in as a user or administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:78
+#: ../../networking/remote_access_vpn.rst:103
+# 911488c63a744096b46e3c6ffffb13be
+# d221bc15811f454fbe75a5f60599eddf
+msgid "In the left navigation, click Network."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:80
+# 6c20446c6a1442f5997a8515ffe0e2b7
+msgid "Click the name of the network you want to work with."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:82
+# a23f38b6e2c8464bb754dcb7965bd45e
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:84
+# ddf12be035374568a290af5640b40e74
+msgid "Click one of the displayed IP address names."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:86
+#: ../../networking/remote_access_vpn.rst:140
+# 41e32709f78944188aa733087e185747
+# 29b34df35b844a28a5c4da345fb4deca
+msgid "Click the Enable VPN button. |vpn-icon.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:88
+# 2721223cf47046fa977985536715b7f7
+msgid "The IPsec key is displayed in a popup window."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:92
+# 4837a25ffda64a66818f80b1160c7cd2
+msgid "Configuring Remote Access VPN in VPC"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:94
+# c157c1f5cdd34780971c2d08fa7c492c
+msgid "On enabling Remote Access VPN on a VPC, any VPN client present outside the VPC can access VMs present in the VPC by using the Remote VPN connection. The VPN client can be present anywhere except inside the VPC on which the user enabled the Remote Access VPN service."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:99
+# 5254f550923d4da39985b04b9a5b5054
+msgid "To enable VPN for a VPC:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:105
+#: ../../networking/remote_access_vpn.rst:435
+#: ../../networking/remote_access_vpn.rst:497
+#: ../../networking/remote_access_vpn.rst:628
+# 12f54511f47d449693acfea97e8d4600
+# 435bbd53f5414d84ba589387bf3fdce6
+# b89124caf1504a709e89424403a433ed
+# 7f0dcc6104d34e828aed248a3d1e5382
+msgid "In the Select view, select VPC."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:107
+#: ../../networking/remote_access_vpn.rst:437
+#: ../../networking/remote_access_vpn.rst:630
+# 7febfd652a0f4a4a9e44f110742bf34a
+# f923f2ca6046405ab0c396e3ca9d07ec
+# 07d5aa607fb94d8b9968b055618eea1c
+msgid "All the VPCs that you have created for the account is listed in the page."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:110
+# 9c932fa1898c4fef97f99b0535e90a08
+msgid "Click the Configure button of the VPC."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:112
+#: ../../networking/remote_access_vpn.rst:446
+#: ../../networking/remote_access_vpn.rst:509
+#: ../../networking/remote_access_vpn.rst:641
+# 83859c50046f48e4b614cd9f79148c16
+# 15f6f70e22df4f90868d62f6c93d09f7
+# 22a5c413786843acb09faad526a6e8e0
+# b4e49b76aea54ad6a1b5116db84dd6d6
+msgid "For each tier, the following options are displayed:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:114
+#: ../../networking/remote_access_vpn.rst:448
+#: ../../networking/remote_access_vpn.rst:511
+#: ../../networking/remote_access_vpn.rst:643
+# f709cfb9270544caa350d3649e206913
+# 1e135a9023a3449996277c5654e0ffe8
+# 36d751e518594344814cd905fce95167
+# 5f29611ae8024e66a507590e86ca1301
+msgid "Internal LB"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:116
+#: ../../networking/remote_access_vpn.rst:450
+#: ../../networking/remote_access_vpn.rst:513
+#: ../../networking/remote_access_vpn.rst:645
+# 38b29ff504c24ecc8d7d54f35ab29998
+# d744448419454b5ba7aae6c638c1f8fd
+# 7e6e21ff676c435d902e75134d2341e5
+# b7dd123eea7d460aa99844bad34e0f91
+msgid "Public LB IP"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:118
+#: ../../networking/remote_access_vpn.rst:452
+#: ../../networking/remote_access_vpn.rst:515
+#: ../../networking/remote_access_vpn.rst:647
+# 74d00e17afdf47d8a79f5c8f0a90a214
+# 404668f335f04d41947db0129e79e65f
+# bee509b27e7c4c9985f5bd7c9169ecaf
+# 7f14717fbb6e471c9e00e2f7622cfa7b
+msgid "Static NAT"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:120
+#: ../../networking/remote_access_vpn.rst:454
+#: ../../networking/remote_access_vpn.rst:517
+#: ../../networking/remote_access_vpn.rst:649
+# 6fd6582e4c7d47019c91a20d69646e3a
+# e333c5792fca4359b9348192f5918984
+# bdf83d752fbc42ef93ab96051cdf7700
+# 30265536e81c46c2879ee0cca63d1297
+msgid "Virtual Machines"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:122
+#: ../../networking/remote_access_vpn.rst:456
+#: ../../networking/remote_access_vpn.rst:519
+#: ../../networking/remote_access_vpn.rst:651
+# 8696dd08ef2d4b6a816ecd0095cdf602
+# f1f39145e71e46b09b4c26ce0175e5b8
+# fe3c8f334ef04b4aa83e3850c9666137
+# 54ff7edf855e482da2b26688c543effe
+msgid "CIDR"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:124
+#: ../../networking/remote_access_vpn.rst:458
+#: ../../networking/remote_access_vpn.rst:521
+#: ../../networking/remote_access_vpn.rst:653
+# 1bd24a8501fd4efd8cd4d0eba492ce37
+# e7a3e4a10b2e484f8b311cdb938a0e47
+# 95e13a760c004dc9a119ddf73d83d0fa
+# 5605be5958c24cb5a0f534dbdecdfa40
+msgid "The following router information is displayed:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:126
+#: ../../networking/remote_access_vpn.rst:460
+#: ../../networking/remote_access_vpn.rst:523
+#: ../../networking/remote_access_vpn.rst:655
+# 8d80f7dd9bcc41f38e801ab022f3fa7d
+# 5c726601395a427e9f541bf544194e40
+# 8b623ab0e8764c58bad6a828685b3cce
+# 71bcceb5de54474b88583e11b88f962e
+msgid "Private Gateways"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:128
+#: ../../networking/remote_access_vpn.rst:462
+#: ../../networking/remote_access_vpn.rst:525
+#: ../../networking/remote_access_vpn.rst:657
+# 0b3d0e7c6eac4b83b9912d3af84c76b3
+# 582728e1b1c043f0bde4a3c35e0ebaba
+# df66b830cc464227ab4da8790a6275bf
+# 4055bdef61d847dc91261a6fc6346d1d
+msgid "Public IP Addresses"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:130
+#: ../../networking/remote_access_vpn.rst:464
+#: ../../networking/remote_access_vpn.rst:527
+#: ../../networking/remote_access_vpn.rst:659
+# 9ce2994577cc43f9bd1f86225e23149e
+# fbf89a2ae9534ea18fb4673230aa75fb
+# 0720a5b1037e49ffbf44a70beacd5c9b
+# 3ade6e74142f446c9bea2329e2828be8
+msgid "Site-to-Site VPNs"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:132
+#: ../../networking/remote_access_vpn.rst:466
+#: ../../networking/remote_access_vpn.rst:529
+#: ../../networking/remote_access_vpn.rst:661
+# 8c10e84bb92143eb918356bda1b0e7e5
+# 376033730f8d4e0b88fc25e1b6fdea80
+# a7e9c55327984532a4460a2b4ba05bb4
+# cd29b4ee7b0c4da0aec784bb04dce7e6
+msgid "Network ACL Lists"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:134
+# c45c88d1e8af4023bd23142b7397edd5
+msgid "In the Router node, select Public IP Addresses."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:136
+# 2334ea7959384b2bbf5138eb8c7aaf78
+msgid "The IP Addresses page is displayed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:138
+# 31440b2a6daa47d2a5ff458a51ca81cc
+msgid "Click Source NAT IP address."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:142
+# 8cf058b60a184e129abe4d2bc8ade840
+msgid "Click OK to confirm. The IPsec key is displayed in a pop-up window."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:144
+# 36c398fbda5b45599ac36f3b5b77e97d
+msgid "Now, you need to add the VPN users."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:146
+# a6d5430b813547dabde217104eba046a
+msgid "Click the Source NAT IP."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:148
+# 88ac91cdca464aa8a924d7cbca73f3df
+msgid "Select the VPN tab."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:150
+# 76a034604e9a4113a46051cde33b0cd8
+msgid "Add the username and the corresponding password of the user you wanted to add."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:153
+# f388fc2f4f0749f5bbb9e062d57f1137
+msgid "Click Add."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:155
+# c491f786e1874564b25032b670c35f98
+msgid "Repeat the same steps to add the VPN users."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:159
+# d3c8df533b2c4e659158e77c8669a813
+msgid "Using Remote Access VPN with Windows"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:161
+# d03485e36a8744758782e81ab88041d1
+msgid "The procedure to use VPN varies by Windows version. Generally, the user must edit the VPN properties and make sure that the default route is not the VPN. The following steps are for Windows L2TP clients on Windows Vista. The commands should be similar for other Windows versions."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:166
+# 98196e5429de407da75adf5f3ce7cf8d
+msgid "Log in to the CloudStack UI and click on the source NAT IP for the account. The VPN tab should display the IPsec preshared key. Make a note of this and the source NAT IP. The UI also lists one or more users and their passwords. Choose one of these users, or, if none exists, add a user and password."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:172
+# 6a896fa8431d479195d161efebf56672
+msgid "On the Windows box, go to Control Panel, then select Network and Sharing center. Click Setup a connection or network."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:175
+# 8e983aa928b444228e689749e8fc0801
+msgid "In the next dialog, select No, create a new connection."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:177
+# 98f484c7652c45d2ae57690d719610ed
+msgid "In the next dialog, select Use my Internet Connection (VPN)."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:179
+# 784c5c041ba94caea475a667add0adcd
+msgid "In the next dialog, enter the source NAT IP from step #1 and give the connection a name. Check Don't connect now."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:183
+# 41d1540c0a7d401a9c549bd5304f18ce
+msgid "In the next dialog, enter the user name and password selected in step #1."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:186
+# 3cbbd674fd8d412c90bfbbeb8f607ea0
+msgid "Click Create."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:188
+# 85a9ef6f201e47f584255229980b3d87
+msgid "Go back to the Control Panel and click Network Connections to see the new connection. The connection is not active yet."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:191
+# 1d169d66dd744654bd8ea7dd62a677a6
+msgid "Right-click the new connection and select Properties. In the Properties dialog, select the Networking tab."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:196
+# a191730de1684f06a3d729e5cde2e487
+msgid "In Type of VPN, choose L2TP IPsec VPN, then click IPsec settings. Select Use preshared key. Enter the preshared key from step #1."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:199
+# 343858b6c3e5498fad0bd34b503e792d
+msgid "The connection is ready for activation. Go back to Control Panel -> Network Connections and double-click the created connection."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:202
+# e60c05ee4aef40d38a3a0b01aade9b5e
+msgid "Enter the user name and password from step #1."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:206
+# d1cfefca174a4554a0c4170ec0c49f9b
+msgid "Using Remote Access VPN with Mac OS X"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:208
+# 728cc61e43c440459c1ad6252a2f6b97
+msgid "First, be sure you've configured the VPN settings in your CloudStack install. This section is only concerned with connecting via Mac OS X to your VPN."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:212
+# b3185af9f4534991ad3e3e5b66f47da2
+msgid "Note, these instructions were written on Mac OS X 10.7.5. They may differ slightly in older or newer releases of Mac OS X."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:215
+# 6f2aaf1e33d6421db0f521c5820d02c8
+msgid "On your Mac, open System Preferences and click Network."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:217
+# 26e7088ea9494f94922f1a8f5e0ad753
+msgid "Make sure Send all traffic over VPN connection is not checked."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:219
+# 8e0600ca2c9546a2b3905659b64a835b
+msgid "If your preferences are locked, you'll need to click the lock in the bottom left-hand corner to make any changes and provide your administrator credentials."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:223
+# da1ba33a066b4415a728d14ab936780c
+msgid "You will need to create a new network entry. Click the plus icon on the bottom left-hand side and you'll see a dialog that says \"Select the interface and enter a name for the new service.\" Select VPN from the Interface drop-down menu, and \"L2TP over IPSec\" for the VPN Type. Enter whatever you like within the \"Service Name\" field."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:229
+# b96bb5f3c9534d3384752b6c652405b5
+msgid "You'll now have a new network interface with the name of whatever you put in the \"Service Name\" field. For the purposes of this example, we'll assume you've named it \"CloudStack.\" Click on that interface and provide the IP address of the interface for your VPN under the Server Address field, and the user name for your VPN under Account Name."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:236
+# db5b3b2b72e449368be600488d32a212
+msgid "Click Authentication Settings, and add the user's password under User Authentication and enter the pre-shared IPSec key in the Shared Secret field under Machine Authentication. Click OK."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:240
+# 79ff11baad9844c9a7bb84f19aac4703
+msgid "You may also want to click the \"Show VPN status in menu bar\" but that's entirely optional."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:243
+# 74b926642e7d49ca925804a4d6d99abc
+msgid "Now click \"Connect\" and you will be connected to the CloudStack VPN."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:249
+# fb0aef197790435d95971b0006f98a9d
+msgid "Setting Up a Site-to-Site VPN Connection"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:251
+# b113a5a8546b4ce8b1a7507f2b860ad7
+msgid "A Site-to-Site VPN connection helps you establish a secure connection from an enterprise datacenter to the cloud infrastructure. This allows users to access the guest VMs by establishing a VPN connection to the virtual router of the account from a device in the datacenter of the enterprise. You can also establish a secure connection between two VPC setups or high availability zones in your environment. Having this facility eliminates the need to establish VPN connections to individual VMs."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:260
+# ec0ce935716740158c031ebf544b7294
+msgid "The difference from Remote VPN is that Site-to-site VPNs connects entire networks to each other, for example, connecting a branch office network to a company headquarters network. In a site-to-site VPN, hosts do not have VPN client software; they send and receive normal TCP/IP traffic through a VPN gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:266
+# 79120b77963b4f77afa51573e6ad1ca7
+msgid "The supported endpoints on the remote datacenters are:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:268
+# 34aba4dd56884ad3871e85272aab2acf
+msgid "Cisco ISR with IOS 12.4 or later"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:270
+# 95978dcfdbf34c2886952ee16cb6e16d
+msgid "Juniper J-Series routers with JunOS 9.5 or later"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:272
+# 272a2a827c494e90a6b2d52dc96b7f0b
+msgid "CloudStack virtual routers"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:275
+# 8c16297c0eab4c72b6a2a29b0f4866d1
+msgid "In addition to the specific Cisco and Juniper devices listed above, the expectation is that any Cisco or Juniper device running on the supported operating systems are able to establish VPN connections."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:279
+# eb701cb20d40405b9ca1d79ce15b681f
+msgid "To set up a Site-to-Site VPN connection, perform the following:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:281
+# b5f397a7a64b47168a74fb1618810e5c
+msgid "Create a Virtual Private Cloud (VPC)."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:283
+# 1d44be641cf042b99841b146bb055956
+msgid "See \":ref:`configuring-vpc`\"."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:285
+# f1ff67e23d7d4eaeb81c1b5686399942
+msgid "Create a VPN Customer Gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:287
+# e3425171b9504f5b958d0802ca1a55ce
+msgid "Create a VPN gateway for the VPC that you created."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:289
+# 6d0964544a6944f39ec8eafdaf587428
+msgid "Create VPN connection from the VPC VPN gateway to the customer VPN gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:294
+# 3d85874020904fbdb261885b5e2f05ce
+msgid "Creating and Updating a VPN Customer Gateway"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:297
+# 9b0857af13544aaebee5984422c93195
+msgid "A VPN customer gateway can be connected to only one VPN gateway at a time."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:299
+# 1a951a0ee8d54164b9b99ff9cd080e58
+msgid "To add a VPN Customer Gateway:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:303
+#: ../../networking/remote_access_vpn.rst:413
+#: ../../networking/remote_access_vpn.rst:433
+#: ../../networking/remote_access_vpn.rst:495
+#: ../../networking/remote_access_vpn.rst:626
+# 6a26e636eb224d1eb75c9782de7c830d
+# affc98b5cd4b401086e5e00f9e69ac90
+# 23c81aa674f64826830390c49839730c
+# 98dc2f6f69d341b0b1867f35102e20ff
+# d4efd83e728b439eaa8408bd783d0c11
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:305
+#: ../../networking/remote_access_vpn.rst:415
+# b0e99af0f0014e1aa156dd7f2644f23a
+# cf4e8a6aa8be4c3e9c92bd5f84e9b571
+msgid "In the Select view, select VPN Customer Gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:307
+# 51d8e12e75dd47e4b2d4a9c52da89be9
+msgid "Click Add VPN Customer Gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:309
+# e72b7822c85649f99f01e845e1418844
+msgid "|addvpncustomergateway.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:311
+# 0810d2cb133043b4858badbc2e4ac704
+msgid "Provide the following information:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:313
+# 372ec8983a514ad3b0927d01bc30fae6
+msgid "**Name**: A unique name for the VPN customer gateway you create."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:315
+# 0cd283ba65a241cf97d90b2c5f04c36f
+msgid "**Gateway**: The IP address for the remote gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:317
+# 0e3f2efe75f7454e9f2ac706604f832d
+msgid "**CIDR list**: The guest CIDR list of the remote subnets. Enter a CIDR or a comma-separated list of CIDRs. Ensure that a guest CIDR list is not overlapped with the VPC's CIDR, or another guest CIDR. The CIDR must be RFC1918-compliant."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:322
+# 929c5f444fae4aee88faa98a926d0f52
+msgid "**IPsec Preshared Key**: Preshared keying is a method where the endpoints of the VPN share a secret key. This key value is used to authenticate the customer gateway and the VPC VPN gateway to each other."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:328
+# 171abb6f27ef471eae87fd0718d714af
+msgid "The IKE peers (VPN end points) authenticate each other by computing and sending a keyed hash of data that includes the Preshared key. If the receiving peer is able to create the same hash independently by using its Preshared key, it knows that both peers must share the same secret, thus authenticating the customer gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:335
+# a4553b53ccb04b358a278545e87eb9bd
+msgid "**IKE Encryption**: The Internet Key Exchange (IKE) policy for phase-1. The supported encryption algorithms are AES128, AES192, AES256, and 3DES. Authentication is accomplished through the Preshared Keys."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:341
+# 3bb40218a4db49e0aa09d5983d57a8fa
+msgid "The phase-1 is the first phase in the IKE process. In this initial negotiation phase, the two VPN endpoints agree on the methods to be used to provide security for the underlying IP traffic. The phase-1 authenticates the two VPN gateways to each other, by confirming that the remote gateway has a matching Preshared Key."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:347
+# a5e3619f28fb487987386ff3359d079b
+msgid "**IKE Hash**: The IKE hash for phase-1. The supported hash algorithms are SHA1 and MD5."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:350
+# 998f798e068147c69b96d5332181acdd
+msgid "**IKE DH**: A public-key cryptography protocol which allows two parties to establish a shared secret over an insecure communications channel. The 1536-bit Diffie-Hellman group is used within IKE to establish session keys. The supported options are None, Group-5 (1536-bit) and Group-2 (1024-bit)."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:356
+# 34c98169c2dd4375a23dff45d764590d
+msgid "**ESP Encryption**: Encapsulating Security Payload (ESP) algorithm within phase-2. The supported encryption algorithms are AES128, AES192, AES256, and 3DES."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:361
+# c61b40cf82de4f9fb6c45b8e0172b4b4
+msgid "The phase-2 is the second phase in the IKE process. The purpose of IKE phase-2 is to negotiate IPSec security associations (SA) to set up the IPSec tunnel. In phase-2, new keying material is extracted from the Diffie-Hellman key exchange in phase-1, to provide session keys to use in protecting the VPN data flow."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:367
+# 71d47a66a42f4a04b2540e69eba4cdd9
+msgid "**ESP Hash**: Encapsulating Security Payload (ESP) hash for phase-2. Supported hash algorithms are SHA1 and MD5."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:370
+# 2378eab3a19b42cda0e954ae2c70bb38
+msgid "**Perfect Forward Secrecy**: Perfect Forward Secrecy (or PFS) is the property that ensures that a session key derived from a set of long-term public and private keys will not be compromised. This property enforces a new Diffie-Hellman key exchange. It provides the keying material that has greater key material life and thereby greater resistance to cryptographic attacks. The available options are None, Group-5 (1536-bit) and Group-2 (1024-bit). The security of the key exchanges increase as the DH groups grow larger, as does the time of the exchanges."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:381
+# de12259eb62f48c294bc324395468d43
+msgid "When PFS is turned on, for every negotiation of a new phase-2 SA the two gateways must generate a new set of phase-1 keys. This adds an extra layer of protection that PFS adds, which ensures if the phase-2 SA's have expired, the keys used for new phase-2 SA's have not been generated from the current phase-1 keying material."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:387
+# c29472e88000476ea8eb3f3165f58da4
+msgid "**IKE Lifetime (seconds)**: The phase-1 lifetime of the security association in seconds. Default is 86400 seconds (1 day). Whenever the time expires, a new phase-1 exchange is performed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:391
+# c05a91d5e2b44d7a9ea842e762a6f4a0
+msgid "**ESP Lifetime (seconds)**: The phase-2 lifetime of the security association in seconds. Default is 3600 seconds (1 hour). Whenever the value is exceeded, a re-key is initiated to provide a new IPsec encryption and authentication session keys."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:396
+# 9afba73f17a3471faa8cff978bb64495
+msgid "**Dead Peer Detection**: A method to detect an unavailable Internet Key Exchange (IKE) peer. Select this option if you want the virtual router to query the liveliness of its IKE peer at regular intervals. It's recommended to have the same configuration of DPD on both side of VPN connection."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:402
+#: ../../networking/remote_access_vpn.rst:425
+# 4d12f59b777c48e98fb18ab2bace355d
+# a65f0ba427b04b6da2bdc39a05acba02
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:406
+# 460983ec4dd64370b650944e21d45b75
+msgid "Updating and Removing a VPN Customer Gateway"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:408
+# 47640086ca6e4122a862027f6e528af6
+msgid "You can update a customer gateway either with no VPN connection, or related VPN connection is in error state."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:417
+# eee4a55897da4f06b44795327c878110
+msgid "Select the VPN customer gateway you want to work with."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:419
+# 9dc617447a9c48df92819b996a8e3b39
+msgid "To modify the required parameters, click the Edit VPN Customer Gateway button |vpn-edit-icon.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:422
+# 0c3c4beedfb2453cb03958649454d3d2
+msgid "To remove the VPN customer gateway, click the Delete VPN Customer Gateway button |delete.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:429
+# ae45fd8564384b9a8682a662011196da
+msgid "Creating a VPN gateway for the VPC"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:440
+#: ../../networking/remote_access_vpn.rst:501
+#: ../../networking/remote_access_vpn.rst:633
+# addf23d2b2b14d9c80370bc70f64ec94
+# 8ab2d3e53e83433ab4cf699e916d89d9
+# 5ece94a59df34ecdb036ac45fc49bd06
+msgid "Click the Configure button of the VPC to which you want to deploy the VMs."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:443
+#: ../../networking/remote_access_vpn.rst:504
+#: ../../networking/remote_access_vpn.rst:636
+# af1a9268a6da4a45922589c847776234
+# 1ccf3bf911414951aeb77508e82aa992
+# 433faedb39a3413c8ce1f220f5e22560
+msgid "The VPC page is displayed where all the tiers you created are listed in a diagram."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:468
+#: ../../networking/remote_access_vpn.rst:531
+#: ../../networking/remote_access_vpn.rst:663
+# 3152bcd237704f96b4a1b897b801f81b
+# 5a72231d602e4625acd0cbd4b0af4f7e
+# 243047505a8c40e1aadfa9dfbc091f0c
+msgid "Select Site-to-Site VPN."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:470
+# 626b08a7444c4baeb387b316fcf8921d
+msgid "If you are creating the VPN gateway for the first time, selecting Site-to-Site VPN prompts you to create a VPN gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:473
+# c46b3f642ec240738664d6765c1d736f
+msgid "In the confirmation dialog, click Yes to confirm."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:475
+# 6dbf5c6dc5984bc896785e8d81f1fa0d
+msgid "Within a few moments, the VPN gateway is created. You will be prompted to view the details of the VPN gateway you have created. Click Yes to confirm."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:479
+# 62c9ff637a9c46beb4a187d9d333e711
+msgid "The following details are displayed in the VPN Gateway page:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:481
+#: ../../networking/remote_access_vpn.rst:561
+# 202a6b9a51f3470d89bb84bb2c9579a8
+# 47435eb81ccf40eab149e9b0abb9213e
+msgid "IP Address"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:483
+# 46f2ea07f3744ac381add8029488f5d3
+msgid "Account"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:485
+# bad02846a1ee4160a278abb51303de1f
+msgid "Domain"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:489
+# b0b08d6daddb48409f581811786b76cf
+msgid "Creating a VPN Connection"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:491
+# 596c1d39f0fe47fa8b05ff9b321ae507
+msgid "CloudStack supports creating up to 8 VPN connections."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:499
+# a61e029b8b514adfa93c97620ffff95f
+msgid "All the VPCs that you create for the account are listed in the page."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:507
+#: ../../networking/remote_access_vpn.rst:639
+# 690702b545754083adec40f20d69acb4
+# 614430ff17c8485fae7ddb094273ef06
+msgid "Click the Settings icon."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:533
+#: ../../networking/remote_access_vpn.rst:665
+# 86dbf74b2c6e4f0aab3f252fafd89f2c
+# fab72af09a284fd2800ff51645f071bf
+msgid "The Site-to-Site VPN page is displayed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:535
+#: ../../networking/remote_access_vpn.rst:667
+# db4dc2719dd6405eb250f62908eef010
+# 207bfc2acd9e434887770513a245873b
+msgid "From the Select View drop-down, ensure that VPN Connection is selected."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:538
+# 950eac49657f4a29a9fba1b973577867
+msgid "Click Create VPN Connection."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:540
+# 916fc10dd39346ada9828e3a2a80ffda
+msgid "The Create VPN Connection dialog is displayed:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:542
+# 87888fff4a5f4664be5c4c03fc2ecf6a
+msgid "|createvpnconnection.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:544
+# 4b6cc407b8bc4a728fb3328f0ce53f3f
+msgid "Select the desired customer gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:546
+# 6776ab8d9fad4c2d8956d78ff11ab998
+msgid "Select Passive if you want to establish a connection between two VPC virtual routers."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:549
+# 513eee2d7f8745a4b338c8ea142fae05
+msgid "If you want to establish a connection between two VPC virtual routers, select Passive only on one of the VPC virtual routers, which waits for the other VPC virtual router to initiate the connection. Do not select Passive on the VPC virtual router that initiates the connection."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:555
+# dd03407d4f064ec99ea68bb066d2289e
+msgid "Click OK to confirm."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:557
+# d4c274e9cecb44bcad1ba67ed65069e4
+msgid "Within a few moments, the VPN Connection is displayed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:559
+# 42dd7918225d458f980e458924b262f3
+msgid "The following information on the VPN connection is displayed:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:563
+# 64fdbdcdfac148dea0883db2615bf0ed
+msgid "Gateway"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:565
+# 8ac547f2f1574131adc8c69d4e3c30ef
+msgid "State"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:567
+# d2a5bd51a6e347e89857750706114fc9
+msgid "IPSec Preshared Key"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:569
+# ccfea0cb9ae34777990aa348b7a9c23f
+msgid "IKE Policy"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:571
+# bc29ecfda06848f78a8cc694b3f6d47b
+msgid "ESP Policy"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:575
+# 57cee5dc2eed4f6a9164c4838ebdc9d6
+msgid "Site-to-Site VPN Connection Between VPC Networks"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:577
+# d8f9f929fafd40e6895122549b022754
+msgid "CloudStack provides you with the ability to establish a site-to-site VPN connection between CloudStack virtual routers. To achieve that, add a passive mode Site-to-Site VPN. With this functionality, users can deploy applications in multiple Availability Zones or VPCs, which can communicate with each other by using a secure Site-to-Site VPN Tunnel."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:583
+# 2fb087843cd04fafa3beba95a3ae2af1
+msgid "This feature is supported on all the hypervisors."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:585
+# 217a4da322cc4f8caa7e04c029779c8b
+msgid "Create two VPCs. For example, VPC A and VPC B."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:587
+# a78d89e3621346c8a11277927e8dc502
+msgid "For more information, see \":ref:`configuring-vpc`\"."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:589
+# 09b752dc4d4e4cd29912fcbe352309fa
+msgid "Create VPN gateways on both the VPCs you created."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:591
+# b9af87b346ef40889104b5a1f40c7702
+msgid "For more information, see `\"Creating a VPN gateway for the VPC\" <#creating-a-vpn-gateway-for-the-vpc>`_."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:594
+# 29d8db01114c458e8d855996c22e0664
+msgid "Create VPN customer gateway for both the VPCs."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:596
+# 1a50b7ef681f4cb48c15d30e08dfd1e7
+msgid "For more information, see `\"Creating and Updating a VPN Customer Gateway\" <#creating-and-updating-a-vpn-customer-gateway>`_."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:599
+# c9013d4ec4c74444a40bf745ae0a5544
+msgid "Enable a VPN connection on VPC A in passive mode."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:601
+# 8fb700491eeb4156a1c7549d81a78346
+msgid "For more information, see `\"Creating a VPN Connection\" <#creating-a-vpn-connection>`_."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:604
+# e8dd1dd51dd34f57ac10161220734be4
+msgid "Ensure that the customer gateway is pointed to VPC B. The VPN connection is shown in the Disconnected state."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:607
+# eca76af9d9304b17982a0bb977a12547
+msgid "Enable a VPN connection on VPC B."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:609
+# 79e9417cc7294b70bd95236d9c2c80ac
+msgid "Ensure that the customer gateway is pointed to VPC A. Because virtual router of VPC A, in this case, is in passive mode and is waiting for the virtual router of VPC B to initiate the connection, VPC B virtual router should not be in passive mode."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:614
+# cf0657024acb43ea8028262bf74a9848
+msgid "The VPN connection is shown in the Disconnected state."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:616
+# 4c18218889914f65b2fe355d4568b407
+msgid "Creating VPN connection on both the VPCs initiates a VPN connection. Wait for few seconds. The default is 30 seconds for both the VPN connections to show the Connected state."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:622
+# 84118e99c0b14f49b14160c3975dad17
+msgid "Restarting and Removing a VPN Connection"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:670
+# 090940869ab44e80b8e9c4ea04fa48ec
+msgid "All the VPN connections you created are displayed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:672
+# b921e72e9ca74e75b9c515a87f105b9a
+msgid "Select the VPN connection you want to work with."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:674
+# 2387d86e243f469f84a0cee989324610
+msgid "The Details tab is displayed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:676
+# 345c5bfe23d84fd09f56e0e34de09e29
+msgid "To remove a VPN connection, click the Delete VPN connection button |remove-vpn.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:679
+# 8d1a3cf378554f51a5702b0710c331f2
+msgid "To restart a VPN connection, click the Reset VPN connection button present in the Details tab. |reset-vpn.png|"
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/security_groups.pot b/source/adminguide/locale/pot/networking/security_groups.pot
new file mode 100644
index 0000000..d52a4a3
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/security_groups.pot
@@ -0,0 +1,265 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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/security_groups.rst:18
+# b67087ae536e4b77ac5668f8f3f73ba8
+msgid "Security Groups"
+msgstr ""
+
+#: ../../networking/security_groups.rst:21
+# 1397d3fadf7d45779a890fb7156cf142
+msgid "About Security Groups"
+msgstr ""
+
+#: ../../networking/security_groups.rst:23
+# 965e0935679141b0bc89e0d82dc1cff8
+msgid "Security groups provide a way to isolate traffic to VMs. 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. Security groups are particularly useful in zones that use basic networking, because there is a single guest network for all guest VMs. In advanced zones, security groups are supported only on the KVM hypervisor."
+msgstr ""
+
+#: ../../networking/security_groups.rst:33
+# 7cc1c024596546c4837b5e09cef7f7db
+msgid "In a zone that uses advanced networking, you can instead define multiple guest networks to isolate traffic to VMs."
+msgstr ""
+
+#: ../../networking/security_groups.rst:36
+# bd8429af9a564cd398104231d1bfc2d9
+msgid "Each CloudStack account comes with a default security group that denies all inbound traffic and allows all outbound traffic. The default security group can be modified so that all new VMs inherit some other desired set of rules."
+msgstr ""
+
+#: ../../networking/security_groups.rst:41
+# 3eb3f0e93cf04d8a9c2a967e8ff3a11c
+msgid "Any CloudStack user can set up any number of additional security groups. When a new VM is launched, it is assigned to the default security group unless another user-defined security group is specified. A VM can be a member of any number of security groups. Once a VM is assigned to a security group, it remains in that group for its entire lifetime; you can not move a running VM from one security group to another."
+msgstr ""
+
+#: ../../networking/security_groups.rst:48
+# 1d91c7babdd54f38b62e9e65788a8a7c
+msgid "You can modify a security group by deleting or adding any number of ingress and egress rules. When you do, the new rules apply to all VMs in the group, whether running or stopped."
+msgstr ""
+
+#: ../../networking/security_groups.rst:52
+# f705f2a195b240f49ffc0cbe9aaa253a
+msgid "If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule."
+msgstr ""
+
+#: ../../networking/security_groups.rst:58
+# 7fa1798aea704a55b545171eb64a16bd
+msgid "Adding a Security Group"
+msgstr ""
+
+#: ../../networking/security_groups.rst:60
+# f7cc763899ad4df99b9e927ef37eabb4
+msgid "A user or administrator can define a new security group."
+msgstr ""
+
+#: ../../networking/security_groups.rst:62
+#: ../../networking/security_groups.rst:124
+# a026f1875e7f4cec8447b013bf2d7a78
+# 27e30ee65cbe485bb8e7370a38b75281
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/security_groups.rst:64
+# 344ee6a79a674e88a4a61b24b0a01b42
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/security_groups.rst:66
+# 07579af87ecd4f1d8bd6e66835cb2958
+msgid "In Select view, choose Security Groups."
+msgstr ""
+
+#: ../../networking/security_groups.rst:68
+# 23507439460f427cb5be523f65e254fb
+msgid "Click Add Security Group."
+msgstr ""
+
+#: ../../networking/security_groups.rst:70
+# a530b7d59d194fb18081a92d396a272a
+msgid "Provide a name and description."
+msgstr ""
+
+#: ../../networking/security_groups.rst:72
+# 237fc184482448589b8a2eb7c3c70e76
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/security_groups.rst:74
+# 34ea82240e9c456ab55ff2f0d5756566
+msgid "The new security group appears in the Security Groups Details tab."
+msgstr ""
+
+#: ../../networking/security_groups.rst:76
+# df20adfc9c2e43b9b56c6f1119a9d73f
+msgid "To make the security group useful, continue to Adding Ingress and Egress Rules to a Security Group."
+msgstr ""
+
+#: ../../networking/security_groups.rst:81
+# 0a506fc7186b4a0c8a15ae463c4793e1
+msgid "Security Groups in Advanced Zones (KVM Only)"
+msgstr ""
+
+#: ../../networking/security_groups.rst:83
+# b2a6fb8be2384189ae73c2430ce94159
+msgid "CloudStack provides the ability to use security groups to provide isolation between guests on a single shared, zone-wide network in an advanced zone where KVM is the hypervisor. Using security groups in advanced zones rather than multiple VLANs allows a greater range of options for setting up guest isolation in a cloud."
+msgstr ""
+
+#: ../../networking/security_groups.rst:91
+# 180782afad3643f1ba9672b7f6da72b3
+msgid "Limitations"
+msgstr ""
+
+#: ../../networking/security_groups.rst:93
+# 133ba38a19484e2e9122631ab38446fa
+msgid "The following are not supported for this feature:"
+msgstr ""
+
+#: ../../networking/security_groups.rst:95
+# 7c46f4b3ab9f405b8ba2b599ffc1985e
+msgid "Two IP ranges with the same VLAN and different gateway or netmask in security group-enabled shared network."
+msgstr ""
+
+#: ../../networking/security_groups.rst:98
+# 25d83dec92f045bda786a85257b3e1d1
+msgid "Two IP ranges with the same VLAN and different gateway or netmask in account-specific shared networks."
+msgstr ""
+
+#: ../../networking/security_groups.rst:101
+# 529f72b64c464f0cbbe8b287e8258f1a
+msgid "Multiple VLAN ranges in security group-enabled shared network."
+msgstr ""
+
+#: ../../networking/security_groups.rst:103
+# c9ffb5f82e6b45778e4e1b83b29ed310
+msgid "Multiple VLAN ranges in account-specific shared networks."
+msgstr ""
+
+#: ../../networking/security_groups.rst:105
+# 8488c958047d450bb250b38d098bc214
+msgid "Security groups must be enabled in the zone in order for this feature to be used."
+msgstr ""
+
+#: ../../networking/security_groups.rst:110
+# 6c5be222e8184b8ab28d3019648e9990
+msgid "Enabling Security Groups"
+msgstr ""
+
+#: ../../networking/security_groups.rst:112
+# b6b2af559254408ba42336e7fddf32e6
+msgid "In order for security groups to function in a zone, the security groups feature must first be enabled for the zone. The administrator can do this when creating a new zone, by selecting a network offering that includes security groups. The procedure is described in Basic Zone Configuration in the Advanced Installation Guide. The administrator can not enable security groups for an existing zone, only when creating a new zone."
+msgstr ""
+
+#: ../../networking/security_groups.rst:122
+# e09d51e1a259488eab79d1fb28954b59
+msgid "Adding Ingress and Egress Rules to a Security Group"
+msgstr ""
+
+#: ../../networking/security_groups.rst:126
+# b24e5ca705b84ea4a6c0511ef2244936
+msgid "In the left navigation, choose Network"
+msgstr ""
+
+#: ../../networking/security_groups.rst:128
+# e6e52ad277a249ebb052f48c14687e98
+msgid "In Select view, choose Security Groups, then click the security group you want."
+msgstr ""
+
+#: ../../networking/security_groups.rst:131
+# 4563cb9609194e7b8bfe401fa3b6219e
+msgid "To add an ingress rule, click the Ingress Rules tab and fill out the following fields to specify what network traffic is allowed into VM instances in this security group. If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule."
+msgstr ""
+
+#: ../../networking/security_groups.rst:137
+# a4934e5b794b41469ff66677df530f64
+msgid "**Add by CIDR/Account**. Indicate whether the source of the traffic will be defined by IP address (CIDR) or an existing security group in a CloudStack account (Account). Choose Account if you want to allow incoming traffic from all VMs in another security group"
+msgstr ""
+
+#: ../../networking/security_groups.rst:143
+# 38c863d52b6c4f3b900f9268d71a3167
+msgid "**Protocol**. The networking protocol that sources will use to send traffic to the security group. TCP and UDP are typically used for data exchange and end-user communications. ICMP is typically used to send error messages or network monitoring data."
+msgstr ""
+
+#: ../../networking/security_groups.rst:148
+# bcb96d430c8649f483335f10c670e649
+msgid "**Start Port, End Port**. (TCP, UDP only) A range of listening ports that are the destination for the incoming traffic. If you are opening a single port, use the same number in both fields."
+msgstr ""
+
+#: ../../networking/security_groups.rst:152
+# 6c1ac4c3fb7e476a8eba891bbf1fa14e
+msgid "**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code that will be accepted."
+msgstr ""
+
+#: ../../networking/security_groups.rst:155
+# 6d982263975e486e8e1b13fe56a83ed0
+msgid "**CIDR**. (Add by CIDR only) To accept only traffic from 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 incoming traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr ""
+
+#: ../../networking/security_groups.rst:161
+# 10e7f63d3cf94152a51416bc737199ed
+msgid "**Account, Security Group**. (Add by Account only) To accept only traffic from another security group, enter the CloudStack account and name of a security group that has already been defined in that account. To allow traffic between VMs within the security group you are editing now, enter the same name you used in step 7."
+msgstr ""
+
+#: ../../networking/security_groups.rst:167
+# 9d70746377c24fdb80bdb73145dda1fe
+msgid "The following example allows inbound HTTP access from anywhere:"
+msgstr ""
+
+#: ../../networking/security_groups.rst:169
+# f1fa895a70e745a182f076db946d9d16
+msgid "|httpaccess.png|"
+msgstr ""
+
+#: ../../networking/security_groups.rst:171
+# 25c1f9eee689482ab0a99049e45c6ceb
+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 security group. If no egress rules are specified, then all traffic will be allowed out. Once egress rules are specified, the following types of traffic are allowed out: traffic specified in egress rules; queries to DNS and DHCP servers; and responses to any traffic that has been allowed in through an ingress rule"
+msgstr ""
+
+#: ../../networking/security_groups.rst:180
+# 83bfb97418d545549c3ea5c0a17c5985
+msgid "**Add by CIDR/Account**. Indicate whether the destination of the traffic will be defined by IP address (CIDR) or an existing security group in a CloudStack account (Account). Choose Account if you want to allow outgoing traffic to all VMs in another security group."
+msgstr ""
+
+#: ../../networking/security_groups.rst:186
+# f175b78e34494795b301760a7fd5168f
+msgid "**Protocol**. The networking protocol that VMs will use to send outgoing traffic. TCP and UDP are typically used for data exchange and end-user communications. ICMP is typically used to send error messages or network monitoring data."
+msgstr ""
+
+#: ../../networking/security_groups.rst:191
+# 31089018bb9f47e4941651c91b2bd90c
+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/security_groups.rst:195
+# 96661f61b9b54d448e5e7be7ba933296
+msgid "**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code that will be sent"
+msgstr ""
+
+#: ../../networking/security_groups.rst:198
+# 7e52dd9e52524ea98f0bcf7ff00116ac
+msgid "**CIDR**. (Add by CIDR only) To send traffic only to 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/security_groups.rst:204
+# 40e0b1515ef948adb1a42642f73f490d
+msgid "**Account, Security Group**. (Add by Account only) To allow traffic to be sent to another security group, enter the CloudStack account and name of a security group that has already been defined in that account. To allow traffic between VMs within the security group you are editing now, enter its name."
+msgstr ""
+
+#: ../../networking/security_groups.rst:210
+# 39febf06883a4d248d1ac5ad19510065
+msgid "Click Add."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/static_nat.pot b/source/adminguide/locale/pot/networking/static_nat.pot
new file mode 100644
index 0000000..20773ee
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/static_nat.pot
@@ -0,0 +1,83 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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/static_nat.rst:18
+# 89295dfc645a421eac4401834f1b5564
+msgid "Static NAT"
+msgstr ""
+
+#: ../../networking/static_nat.rst:20
+# c3b2d053fab944578298ac1adf46e76e
+msgid "A static NAT rule maps a public IP address to the private IP address of a VM in order to allow Internet traffic into the VM. The public IP address always remains the same, which is why it is called static NAT. This section tells how to enable or disable static NAT for a particular IP address."
+msgstr ""
+
+#: ../../networking/static_nat.rst:28
+# ffe605639e6844fa8170c65805372b4c
+msgid "Enabling or Disabling Static NAT"
+msgstr ""
+
+#: ../../networking/static_nat.rst:30
+# 311e1bb870dd43bb98cd7ee6a01f42ca
+msgid "If port forwarding rules are already in effect for an IP address, you cannot enable static NAT to that IP."
+msgstr ""
+
+#: ../../networking/static_nat.rst:33
+# b89fc2e081874b24b0ad50ed843837e9
+msgid "If a guest VM is part of more than one network, static NAT rules will function only if they are defined on the default network."
+msgstr ""
+
+#: ../../networking/static_nat.rst:36
+# e6dabe6070464d23926137799673505a
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/static_nat.rst:38
+# 726614a43cbf4c448770c40822676059
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/static_nat.rst:40
+# 71505d3318714907a3abd5319833b78e
+msgid "Click the name of the network where you want to work with."
+msgstr ""
+
+#: ../../networking/static_nat.rst:42
+# 0898722d18384a89a217a7a8e7cb6fbf
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking/static_nat.rst:44
+# 5e916ccbf7c94237b104827f38f2ca6a
+msgid "Click the IP address you want to work with."
+msgstr ""
+
+#: ../../networking/static_nat.rst:46
+# 4f5018aad8f14212a2d0c17d955b197a
+msgid "Click the Static NAT |enabledisablenat.png| button."
+msgstr ""
+
+#: ../../networking/static_nat.rst:48
+# 001cc2e543c345afb265ff300a5435ca
+msgid "The button toggles between Enable and Disable, depending on whether static NAT is currently enabled for the IP address."
+msgstr ""
+
+#: ../../networking/static_nat.rst:51
+# 91178f93f90f4135b40823266a6ecb4e
+msgid "If you are enabling static NAT, a dialog appears where you can choose the destination VM and click Apply."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking/virtual_private_cloud_config.pot b/source/adminguide/locale/pot/networking/virtual_private_cloud_config.pot
new file mode 100644
index 0000000..e589c54
--- /dev/null
+++ b/source/adminguide/locale/pot/networking/virtual_private_cloud_config.pot
@@ -0,0 +1,2019 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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/virtual_private_cloud_config.rst:20
+# 4425df0b51c64a33802d59f9f7eb5bd8
+msgid "Configuring a Virtual Private Cloud"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:23
+# 60b4e45448554da0a9df907a8e700391
+msgid "About Virtual Private Clouds"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:25
+# 9caa2b864b03431aae6a6f47aa583653
+msgid "CloudStack Virtual Private Cloud is a private, isolated part of CloudStack. A VPC can have its own virtual network topology that resembles a traditional physical network. You can launch VMs in the virtual network that can have private addresses in the range of your choice, for example: 10.0.0.0/16. You can define network tiers within your VPC network range, which in turn enables you to group similar kinds of instances based on IP address range."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:33
+# e8c6a442ed744a6c96df83edc8c28763
+msgid "For example, if a VPC has the private range 10.0.0.0/16, its guest networks can have the network ranges 10.0.1.0/24, 10.0.2.0/24, 10.0.3.0/24, and so on."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:39
+# d7dd703816c14c8ab823fc4ac5ee3c02
+msgid "Major Components of a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:41
+# c50712e0b85b4e8d8a37c525dc8f77d0
+msgid "A VPC is comprised of the following network components:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:43
+# 7805e308c7f14ae4b5bf6813c742fd84
+msgid "**VPC**: A VPC acts as a container for multiple isolated networks that can communicate with each other via its virtual router."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:46
+# 6837ce595efa433cb0a4eeef3c61bd86
+msgid "**Network Tiers**: Each tier acts as an isolated network with its own VLANs and CIDR list, where you can place groups of resources, such as VMs. The tiers are segmented by means of VLANs. The NIC of each tier acts as its gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:51
+# eaa3327f752e430ba437d3048c8cd517
+msgid "**Virtual Router**: A virtual router is automatically created and started when you create a VPC. The virtual router connect the tiers and direct traffic among the public gateway, the VPN gateways, and the NAT instances. For each tier, a corresponding NIC and IP exist in the virtual router. The virtual router provides DNS and DHCP services through its IP."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:58
+# 2922aef73276424d86c458cab53d05d6
+msgid "**Public Gateway**: The traffic to and from the Internet routed to the VPC through the public gateway. In a VPC, the public gateway is not exposed to the end user; therefore, static routes are not support for the public gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:63
+# 417e8d202f044580b6bef8868a97493b
+msgid "**Private Gateway**: All the traffic to and from a private network routed to the VPC through the private gateway. For more information, see \":ref:`adding-priv-gw-vpc`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:67
+# 4776de29b7b1471084bbdc0a5fd8257d
+msgid "**VPN Gateway**: The VPC side of a VPN connection."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:69
+# 208527258e274b0ea77846c710ba8258
+msgid "**Site-to-Site VPN Connection**: A hardware-based VPN connection between your VPC and your datacenter, home network, or co-location facility. For more information, see \":ref:`setting-s2s-vpn-conn`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:73
+# 3b96c83ddcc34269896e5573992e31b5
+msgid "**Customer Gateway**: The customer side of a VPN Connection. For more information, see `\"Creating and Updating a VPN Customer Gateway\" <#creating-and-updating-a-vpn-customer-gateway>`_."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:77
+# bfadc68d3fbe458bb82d6692306f1319
+msgid "**NAT Instance**: An instance that provides Port Address Translation for instances to access the Internet via the public gateway. For more information, see \":ref:`enabling-disabling-static-nat-on-vpc`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:81
+# aa7430e86dde41ea828ef58fdc9a2616
+msgid "**Network ACL**: Network ACL is a group of Network ACL items. Network ACL items are nothing but numbered rules that are evaluated in order, starting with the lowest numbered rule. These rules determine whether traffic is allowed in or out of any tier associated with the network ACL. For more information, see \":ref:`conf-net-acl`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:89
+# 3248944cfc5a49b7a0c47f7fe13a0385
+msgid "Network Architecture in a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:91
+# 5f310f0748274a1a9d0a095aec7c9c2b
+msgid "In a VPC, the following four basic options of network architectures are present:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:94
+# 7cb03da5ae0b478690c6ab442164a344
+msgid "VPC with a public gateway only"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:96
+# ea9f2145319e406e957665bb7b53123c
+msgid "VPC with public and private gateways"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:98
+# 2b4f4b4fbf46434c8e5534d0631bca33
+msgid "VPC with public and private gateways and site-to-site VPN access"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:100
+# 45b4489a9fcc4360a6d5b2719a77dc79
+msgid "VPC with a private gateway only and site-to-site VPN access"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:104
+# b702ceb782244642b4369af267ce81d8
+msgid "Connectivity Options for a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:106
+# 6b1ff95952fe4ccbba871b1f5d84e8d8
+msgid "You can connect your VPC to:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:108
+# 65aa43fb551b4f999e9e48eb5960893d
+msgid "The Internet through the public gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:110
+# 09137011988c4abebde330c2201cbfe4
+msgid "The corporate datacenter by using a site-to-site VPN connection through the VPN gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:113
+# 7a7466064859416c9bf3d5f6fb2828fa
+msgid "Both the Internet and your corporate datacenter by using both the public gateway and a VPN gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:118
+# c4053fc0a35c4c30b312bd50f3cc946e
+msgid "VPC Network Considerations"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:120
+# f884bf37cfa444299fac3dd70425950c
+msgid "Consider the following before you create a VPC:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:122
+# 3d67118ab9e24f4d861c4b78cd07fe86
+msgid "A VPC, by default, is created in the enabled state."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:124
+# 64f62904ffbf4d0998ef58a29ec39785
+msgid "A VPC can be created in Advance zone only, and can't belong to more than one zone at a time."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:127
+# 146628ae783e4af79b8cdd56694e87b3
+msgid "The default number of VPCs an account can create is 20. However, you can change it by using the max.account.vpcs global parameter, which controls the maximum number of VPCs an account is allowed to create."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:131
+# 548f4246178a412ba72c20238355c619
+msgid "The default number of tiers an account can create within a VPC is 3. You can configure this number by using the vpc.max.networks parameter."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:135
+# 8f4ab58bb2db48e7ab28e709ee99c791
+msgid "Each tier should have an unique CIDR in the VPC. Ensure that the tier's CIDR should be within the VPC CIDR range."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:138
+# a3ab5225e8e649a38b583c6dfa85dd0b
+msgid "A tier belongs to only one VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:140
+# cbf79c1dbbb04abeb940ac4a4e63693b
+msgid "All network tiers inside the VPC should belong to the same account."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:142
+# 4697685b3c1c4f75888b23d1f474ad37
+msgid "When a VPC is created, by default, a SourceNAT IP is allocated to it. The Source NAT IP is released only when the VPC is removed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:145
+# f790d826d90d4341885a39022d276efc
+msgid "A public IP can be used for only one purpose at a time. If the IP is a sourceNAT, it cannot be used for StaticNAT or port forwarding."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:148
+# cccc0c77482c4721a48a8e3eee6370e0
+msgid "The instances can only have a private IP address that you provision. To communicate with the Internet, enable NAT to an instance that you launch in your VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:152
+# b833eb4050c145869c7a419c8f37aee9
+msgid "Only new networks can be added to a VPC. The maximum number of networks per VPC is limited by the value you specify in the vpc.max.networks parameter. The default value is three."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:156
+# 1180f413398548729b7198559dc5eb33
+msgid "The load balancing service can be supported by only one tier inside the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:159
+# 1d6388d964364caa8d134f7673bfa2dd
+msgid "If an IP address is assigned to a tier:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:161
+# 92d15597ceda4a5383fd25cb566b47c7
+msgid "That IP can't be used by more than one tier at a time in the VPC. For example, if you have tiers A and B, and a public IP1, you can create a port forwarding rule by using the IP either for A or B, but not for both."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:166
+# a92e77fa9415458b960baded020a27ac
+msgid "That IP can't be used for StaticNAT, load balancing, or port forwarding rules for another guest network inside the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:169
+# e138623610a449e8a6fd5bb3f4a2ab3f
+msgid "Remote access VPN is not supported in VPC networks."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:173
+# 02efff273d294762ad189c6d19730f71
+msgid "Adding a Virtual Private Cloud"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:175
+# d1100a2ab1a54454bece6b2f5a47e4f8
+msgid "When creating the VPC, you simply provide the zone and a set of IP addresses for the VPC network address space. You specify this set of addresses in the form of a Classless Inter-Domain Routing (CIDR) block."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:179
+#: ../../networking/virtual_private_cloud_config.rst:223
+#: ../../networking/virtual_private_cloud_config.rst:331
+#: ../../networking/virtual_private_cloud_config.rst:380
+#: ../../networking/virtual_private_cloud_config.rst:492
+#: ../../networking/virtual_private_cloud_config.rst:662
+#: ../../networking/virtual_private_cloud_config.rst:729
+#: ../../networking/virtual_private_cloud_config.rst:788
+#: ../../networking/virtual_private_cloud_config.rst:848
+#: ../../networking/virtual_private_cloud_config.rst:1014
+#: ../../networking/virtual_private_cloud_config.rst:1227
+#: ../../networking/virtual_private_cloud_config.rst:1282
+#: ../../networking/virtual_private_cloud_config.rst:1360
+#: ../../networking/virtual_private_cloud_config.rst:1388
+# 27c90db3b2d846b58c9abf075735077b
+# 23214314bc4c40d3bc784cf8b99c1273
+# 06da644a106746d9b22320df5442e7eb
+# 8292048a7bd74adeae7e3b6677cc7dc8
+# fb4e97f30b554d92af68a1e9d1886576
+# ceaea70c95b1422597606b789f77fae7
+# c80fe5feb23443ab8e81a05534c38d15
+# 612a8d98561a4b08824d22d8ab9cd815
+# 3d9f5b1f4cf7497ebaa39f40d2b7d3fb
+# 7af40adf2d7f49ee82115cf17558f076
+# 54efcc991da44e5b87cab339063f09cc
+# 98308f9c7c7e4548b3e6ef0828178c9d
+# b16c2e02fd8e42a1aacb687d60b4fb46
+# 1d2a5b77246843818d6d6cc8fd7482ae
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:181
+#: ../../networking/virtual_private_cloud_config.rst:225
+#: ../../networking/virtual_private_cloud_config.rst:333
+#: ../../networking/virtual_private_cloud_config.rst:382
+#: ../../networking/virtual_private_cloud_config.rst:494
+#: ../../networking/virtual_private_cloud_config.rst:664
+#: ../../networking/virtual_private_cloud_config.rst:731
+#: ../../networking/virtual_private_cloud_config.rst:790
+#: ../../networking/virtual_private_cloud_config.rst:850
+#: ../../networking/virtual_private_cloud_config.rst:1016
+#: ../../networking/virtual_private_cloud_config.rst:1229
+#: ../../networking/virtual_private_cloud_config.rst:1284
+#: ../../networking/virtual_private_cloud_config.rst:1362
+#: ../../networking/virtual_private_cloud_config.rst:1390
+# 25aa9d2390434c03a89b6b16c9b69fe9
+# 6e8e81dbb9f447c3aaabac12cbbebc79
+# 7daeed72e5de4f68b5d3fec3deae5a12
+# ad50664f103d4bc3b95d04f0c6891395
+# b462daef366f4f119997d229bdcd4fde
+# cbb8c618e79f4f5bb024ac637c94f155
+# d418a0fbecc7474d89b0c7122cb9f046
+# c1602cd2089a4465bb64a310c84582ae
+# 692a153c672746fa937e636f18024241
+# f2241fbd031643a498b64bc52bc9a3ed
+# 35b9e68484d140e1813335d0a33c68d1
+# bb61fadd006d4624a91bb45665efac73
+# 0cdbc29c89c540c08fa87bd601f4976c
+# 2706338d19fe43d589acd0c274b932c0
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:183
+#: ../../networking/virtual_private_cloud_config.rst:227
+#: ../../networking/virtual_private_cloud_config.rst:335
+#: ../../networking/virtual_private_cloud_config.rst:384
+#: ../../networking/virtual_private_cloud_config.rst:496
+#: ../../networking/virtual_private_cloud_config.rst:666
+#: ../../networking/virtual_private_cloud_config.rst:733
+#: ../../networking/virtual_private_cloud_config.rst:792
+#: ../../networking/virtual_private_cloud_config.rst:852
+#: ../../networking/virtual_private_cloud_config.rst:1018
+#: ../../networking/virtual_private_cloud_config.rst:1231
+#: ../../networking/virtual_private_cloud_config.rst:1286
+#: ../../networking/virtual_private_cloud_config.rst:1364
+#: ../../networking/virtual_private_cloud_config.rst:1392
+# 4a2df6815f134b918345eaf3d39193fa
+# a59b8d1dfb334d948ed4ad0764ce5b84
+# 12b0ac2563474462b71654534aba088a
+# 08995e8ef0484b879f2982b11278720c
+# 0913e0292efb41c284ad04d0d8ec0c1d
+# f66916dd15334247bb50483cd9c296b7
+# d34dad2acbce43aa9f28ce7014089f24
+# 50500a3f8df347e19b005d01525ac7e1
+# c538254df2644b7fb6e4aa16f80f84a6
+# 92649f86d20849b498765a29fd1d7973
+# 9528e3d88e224cacb28e4e204ddab6a7
+# 934c19367f124113b2d3d8f8aabab4a6
+# cd85c04d5e0b4e7c901b189b7ab5e96e
+# 2028f717603c4390944c6c6cb703af37
+msgid "In the Select view, select VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:185
+# 03b833a9bbc14d2f8ccd0561f8bac779
+msgid "Click Add VPC. The Add VPC page is displayed as follows:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:187
+# 007c69b8b7c640d2a9dd08b2b4a86102
+msgid "|add-vpc.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:189
+# 7bd4344fc68d4e6c8939286640c64ff6
+msgid "Provide the following information:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:191
+# fecc1622a73f4e299c4fe16149ef3c1e
+msgid "**Name**: A short name for the VPC that you are creating."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:193
+# 9fe964ec13864d159f7f9fe45e612351
+msgid "**Description**: A brief description of the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:195
+# 75bab09118a641cd94d798e0450bb114
+msgid "**Zone**: Choose the zone where you want the VPC to be available."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:197
+# 38e1b19b64074aebbc448d4398522e6a
+msgid "**Super CIDR for Guest Networks**: Defines the CIDR range for all the tiers (guest networks) within a VPC. When you create a tier, ensure that its CIDR is within the Super CIDR value you enter. The CIDR must be RFC1918 compliant."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:202
+# 2b3cb992f4d9418699ec71ad0d7892b7
+msgid "**DNS domain for Guest Networks**: If you want to assign a special domain name, specify the DNS suffix. This parameter is applied to all the tiers within the VPC. That implies, all the tiers you create in the VPC belong to the same DNS domain. If the parameter is not specified, a DNS domain name is generated automatically."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:208
+# ae282958b5fb4ea594fe92f009ca5f46
+msgid "**Public Load Balancer Provider**: You have two options: VPC Virtual Router and Netscaler."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:211
+#: ../../networking/virtual_private_cloud_config.rst:281
+#: ../../networking/virtual_private_cloud_config.rst:455
+#: ../../networking/virtual_private_cloud_config.rst:479
+# f0a8bdb0febf4b97879a69db489ba8b8
+# a37c6acaf1254a6f818d9f64ae0960aa
+# 677238e0e48a40898578fd007249ecaa
+# 650c882688974599ba5c3660d14f2838
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:215
+# 83d71b83ff1b413187423073f1a1c957
+msgid "Adding Tiers"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:217
+# 8202063e990e4086bb8c476cfa8f2650
+msgid "Tiers are distinct locations within a VPC that act as isolated networks, which do not have access to other tiers by default. Tiers are set up on different VLANs that can communicate with each other by using a virtual router. Tiers provide inexpensive, low latency network connectivity to other tiers within the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:229
+#: ../../networking/virtual_private_cloud_config.rst:1366
+# 6f156f2256294f94a48422c02a2a33f1
+# 91fdfd64076446a1af782ea3021c6911
+msgid "All the VPC that you have created for the account is listed in the page."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:233
+# 98e3757975184289b5414253c54bd6c9
+msgid "The end users can see their own VPCs, while root and domain admin can see any VPC they are authorized to see."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:236
+#: ../../networking/virtual_private_cloud_config.rst:1369
+# 3293738bea7a4e3c97fc6b8cd60f65ba
+# 4c89fd343c734f5cabc8cb26dd48bf94
+msgid "Click the Configure button of the VPC for which you want to set up tiers."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:239
+# a3b02bf28e484233b337b84341a2f39e
+msgid "Click Create network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:241
+# e8b22e1b54b84b1e9945e0c94e3fd069
+msgid "The Add new tier dialog is displayed, as follows:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:243
+# 1f18a2fd76094e94947690c4064b2a75
+msgid "|add-tier.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:245
+# 830f50fe9c8041c9821f1cf9b94f87bd
+msgid "If you have already created tiers, the VPC diagram is displayed. Click Create Tier to add a new tier."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:248
+#: ../../networking/virtual_private_cloud_config.rst:539
+#: ../../networking/virtual_private_cloud_config.rst:1062
+#: ../../networking/virtual_private_cloud_config.rst:1330
+# b372cab6baf04844a5ff7a1611d1d5b6
+# 4bc6b0a5224f4b8383ff3c5322dc34c6
+# 95ebee159c7a49d6a38872dfbba22963
+# 1490eec9177146d0bb7ef70ee1896fb9
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:250
+# 07194bca2d77463fb722f6b3a2d51fd6
+msgid "All the fields are mandatory."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:252
+# 26b1c6c9cd4747a0b399711d03ee9f7f
+msgid "**Name**: A unique name for the tier you create."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:254
+# b4b14e979a074d9fbdd39309629f1524
+msgid "**Network Offering**: The following default network offerings are listed: Internal LB, DefaultIsolatedNetworkOfferingForVpcNetworksNoLB, DefaultIsolatedNetworkOfferingForVpcNetworks"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:259
+# 54126af9bcfb4590a766f2324d72f790
+msgid "In a VPC, only one tier can be created by using LB-enabled network offering."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:262
+# 083df7653efc42938c67b7537bbc4bc3
+msgid "**Gateway**: The gateway for the tier you create. Ensure that the gateway is within the Super CIDR range that you specified while creating the VPC, and is not overlapped with the CIDR of any existing tier within the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:267
+# abb381823abe42c78600368125e95a5a
+msgid "**VLAN**: The VLAN ID for the tier that the root admin creates."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:269
+# e6585788ce994cfba6fa7581d88af8df
+msgid "This option is only visible if the network offering you selected is VLAN-enabled."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:272
+# 383ce12e9bc44d939d3ae386c0ca42aa
+msgid "For more information, see `\"Assigning VLANs to Isolated Networks\" <hosts.html#assigning-vlans-to-isolated-networks>`_."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:275
+# 88877f2edc5f40a9949cf663c7c306a0
+msgid "**Netmask**: The netmask for the tier you create."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:277
+# 25897e33d08b4bedb702059f77e2f09e
+msgid "For example, if the VPC CIDR is 10.0.0.0/16 and the network tier CIDR is 10.0.1.0/24, the gateway of the tier is 10.0.1.1, and the netmask of the tier is 255.255.255.0."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:283
+# 6da01b412d664e3baa5324abd03955b7
+msgid "Continue with configuring access control list for the tier."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:289
+# dc2a5ea9afaf4bb8b1d188b3cadc5fb2
+msgid "Configuring Network Access Control List"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:291
+# 79dbace67e0b4872ba1da3458f8ccb16
+msgid "Define Network Access Control List (ACL) on the VPC virtual router to control incoming (ingress) and outgoing (egress) traffic between the VPC tiers, and the tiers and Internet. By default, all incoming traffic to the guest networks is blocked and all outgoing traffic from guest networks is allowed, once you add an ACL rule for outgoing traffic, then only outgoing traffic specified in this ACL rule is allowed, the rest is blocked. To open the ports, you must create a new network ACL. The network ACLs can be created for the tiers only if the NetworkACL service is supported."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:303
+# c9d908950964474eb10940d7ba15e7ba
+msgid "About Network ACL Lists"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:305
+# c28b7fe0e1f04f65ad1968b74ca91f03
+msgid "In CloudStack terminology, Network ACL is a group of Network ACL items. Network ACL items are nothing but numbered rules that are evaluated in order, starting with the lowest numbered rule. These rules determine whether traffic is allowed in or out of any tier associated with the network ACL. You need to add the Network ACL items to the Network ACL, then associate the Network ACL with a tier. Network ACL is associated with a VPC and can be assigned to multiple VPC tiers within a VPC. A Tier is associated with a Network ACL at all the times. Each tier can be associated with only one ACL."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:315
+# e213818eed1947258f8bcb2896c4b24a
+msgid "The default Network ACL is used when no ACL is associated. Default behavior is all the incoming traffic is blocked and outgoing traffic is allowed from the tiers. Default network ACL cannot be removed or modified. Contents of the default Network ACL is:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:321
+# e7163daf40764297bb4c9256f9b0db76
+msgid "Rule"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:321
+# 8c0f119efb90499885ad10d74e32f699
+msgid "Protocol"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:321
+# 6a4e95a5005949559075e58b104e8b1e
+msgid "Traffic type"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:321
+# db7f138ccd254efda3045d28c44e5ebd
+msgid "Action"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:321
+#: ../../networking/virtual_private_cloud_config.rst:352
+#: ../../networking/virtual_private_cloud_config.rst:519
+#: ../../networking/virtual_private_cloud_config.rst:754
+#: ../../networking/virtual_private_cloud_config.rst:812
+#: ../../networking/virtual_private_cloud_config.rst:873
+#: ../../networking/virtual_private_cloud_config.rst:1039
+#: ../../networking/virtual_private_cloud_config.rst:1307
+# 51c0d62f36c143a5baf332fb86f16b96
+# d597d570fbfc4080b2ea3998fa7d939e
+# eff385663f0941d4b6809c0c182cfaf2
+# 2599fa667bce44d7b2c977f4d835a98e
+# bc9aa77c4f984714a6cead0bf43281ad
+# a2e2cc9d31f448ecab07fc456663f5bd
+# d849de055dcd46a29493cd6942aa2cae
+# 7d80106d48c4421190d8c55e7ddd2f90
+msgid "CIDR"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:323
+# fc484eb64ca04d1b8fed82414583e90a
+msgid "1"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:323
+#: ../../networking/virtual_private_cloud_config.rst:324
+# c40bf7c2103d4006b064570d67b6b324
+# 8f113663532445cbb46226109e68fc87
+msgid "All"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:323
+# cd3fb0b3957f47a7b32acd1b403d5f55
+msgid "Ingress"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:323
+#: ../../networking/virtual_private_cloud_config.rst:324
+# e166cc8cfc04481391575caea5841312
+# d259eeaee8994ad79d0143e92a5fe39a
+msgid "Deny"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:323
+#: ../../networking/virtual_private_cloud_config.rst:324
+# acedcca878414c89b67e3f7e98d67e02
+# c2f3ea9812544c20a6fc02ac9aad34f0
+msgid "0.0.0.0/0"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:324
+# dd6e16cde8494347a2e77ca176fd8a0c
+msgid "2"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:324
+# 23726ba83ae748468e32ef14a54d573b
+msgid "Egress"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:329
+# 464f3ed7f4f24169b73210972956651a
+msgid "Creating ACL Lists"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:337
+#: ../../networking/virtual_private_cloud_config.rst:386
+#: ../../networking/virtual_private_cloud_config.rst:498
+#: ../../networking/virtual_private_cloud_config.rst:668
+#: ../../networking/virtual_private_cloud_config.rst:735
+#: ../../networking/virtual_private_cloud_config.rst:794
+#: ../../networking/virtual_private_cloud_config.rst:854
+#: ../../networking/virtual_private_cloud_config.rst:1020
+#: ../../networking/virtual_private_cloud_config.rst:1233
+#: ../../networking/virtual_private_cloud_config.rst:1288
+#: ../../networking/virtual_private_cloud_config.rst:1394
+# b4c82d1c9112484d92153e98ab6a2d33
+# 473281bb899a4393b7cf08840e8c8fde
+# 96a686680e5647d1b47c4067236c664f
+# a790843b311f4f1a9cd8d8d1ee5257a0
+# 4b114128189141c284315e2473ddc438
+# eee54cf82c9f4083b3ad53bb800a3bb4
+# 5c27b5d189844a82a379bc064c2b337e
+# 24808f02d0764c739d4aad58f9e15037
+# 1b11a2ac4b0e47ee9fc8a3f367edea68
+# 100ab8e1140f431bb36c49295576da40
+# 3ed6090af9fa4e238cf801269c4c072d
+msgid "All the VPCs that you have created for the account is listed in the page."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:340
+#: ../../networking/virtual_private_cloud_config.rst:389
+# 6aa87599a443418889e9db15cc500f7d
+# 0bb74bee4b2d4d6da70d6240c47afe8f
+msgid "Click the Configure button of the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:342
+#: ../../networking/virtual_private_cloud_config.rst:1029
+#: ../../networking/virtual_private_cloud_config.rst:1297
+# a7a5868fc1c545d8b40456b1836b9ddc
+# 62d64d7c737248d3b49d2cfcf91ab9ea
+# a7576a24a2874ab89a29f6d0b1528bac
+msgid "For each tier, the following options are displayed:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:344
+#: ../../networking/virtual_private_cloud_config.rst:511
+#: ../../networking/virtual_private_cloud_config.rst:746
+#: ../../networking/virtual_private_cloud_config.rst:804
+#: ../../networking/virtual_private_cloud_config.rst:865
+#: ../../networking/virtual_private_cloud_config.rst:1031
+#: ../../networking/virtual_private_cloud_config.rst:1299
+# c84c70798b73443ba7f00b174398ed30
+# 2b1209152c06414c809dd9cbe8e873f6
+# 2d40227490424cf0b08f531835947150
+# 5d234a982f1c449bb04697d7e629b3d7
+# b35cbc7845ed400cb02bd71b07eac64e
+# 68ca9e9b2011446da7adcef0d83d05ee
+# edde5a9896f94691829221191ccf24ca
+msgid "Internal LB"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:346
+#: ../../networking/virtual_private_cloud_config.rst:513
+#: ../../networking/virtual_private_cloud_config.rst:748
+#: ../../networking/virtual_private_cloud_config.rst:806
+#: ../../networking/virtual_private_cloud_config.rst:867
+#: ../../networking/virtual_private_cloud_config.rst:1033
+#: ../../networking/virtual_private_cloud_config.rst:1301
+# 840747d13a8548c3a1ed1cfa7aec94d8
+# 2cebf679ea3c44cea4495a0da3fdede4
+# 171baf1d98124ad5a9e0e93348d43959
+# 60793fb25c274674a39f4d6ca1d6f5e8
+# cdafdf21344242e391e50189def8e3f7
+# 22aed14946de415e844a06a396d14413
+# d215b78e0acd4886aaae10e01da3539a
+msgid "Public LB IP"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:348
+#: ../../networking/virtual_private_cloud_config.rst:515
+#: ../../networking/virtual_private_cloud_config.rst:750
+#: ../../networking/virtual_private_cloud_config.rst:808
+#: ../../networking/virtual_private_cloud_config.rst:869
+#: ../../networking/virtual_private_cloud_config.rst:1035
+#: ../../networking/virtual_private_cloud_config.rst:1303
+# 503c7c6831eb4f5ca96c64c2b8328442
+# b565e6a4cff8412f9d1c9032ea24e848
+# 749694902cf440fea4b8315f93dddf91
+# 0b5fb5da84014d7680951915cb26b0a8
+# f8fa3d05ec454df1abf7f6a5079c965b
+# 43f4ab42a09a499783f95aba183bd8a7
+# 88e9603df37e4eacb36619474a076744
+msgid "Static NAT"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:350
+#: ../../networking/virtual_private_cloud_config.rst:517
+#: ../../networking/virtual_private_cloud_config.rst:752
+#: ../../networking/virtual_private_cloud_config.rst:810
+#: ../../networking/virtual_private_cloud_config.rst:871
+#: ../../networking/virtual_private_cloud_config.rst:1037
+#: ../../networking/virtual_private_cloud_config.rst:1305
+# c7d592104fa6447da1b9471822e82ec8
+# 714747328af148798be74203cc3ea72e
+# 86f01795bd5c488fb9cbffd13a3b84a0
+# 1a4d0e4cefc648188e4e0d1e3f5f813f
+# 7df65f6c728842c680faa985c0d2b934
+# 0caa2b61a0d14a3893de13c06290cb7a
+# 8adba6b367094ad4bd769cc0a7ae13a8
+msgid "Virtual Machines"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:354
+#: ../../networking/virtual_private_cloud_config.rst:521
+#: ../../networking/virtual_private_cloud_config.rst:756
+#: ../../networking/virtual_private_cloud_config.rst:814
+#: ../../networking/virtual_private_cloud_config.rst:875
+#: ../../networking/virtual_private_cloud_config.rst:1041
+#: ../../networking/virtual_private_cloud_config.rst:1309
+# 2e579cf3f90345feb4b8edc18f78fd8d
+# 600d551d0f114e47a420f1c86cd445f4
+# 485eb313498a44e2ab1906012a044734
+# 92f01bcc2bcd45919753fcbc87f143c3
+# e6be963a127340ba88d4e76482c44368
+# e48b3a02fdbf4c1aab3e5704df727b54
+# 0a61a781736c436c9379e115fd3df3cb
+msgid "The following router information is displayed:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:356
+#: ../../networking/virtual_private_cloud_config.rst:523
+#: ../../networking/virtual_private_cloud_config.rst:758
+#: ../../networking/virtual_private_cloud_config.rst:816
+#: ../../networking/virtual_private_cloud_config.rst:877
+#: ../../networking/virtual_private_cloud_config.rst:1043
+#: ../../networking/virtual_private_cloud_config.rst:1311
+# 4ed3754e8e014af2a5af0fb4036eeef2
+# 3d5c5cdec63d4e90aee5f9c884e80a5d
+# dcf31b093d01445ebfad5a3769f1a716
+# 4e06d785ce264f838a57f818a5eb51de
+# 33fd1f6f2fe94fbb8fcebb54432f6db5
+# 920576fcde1e43f5a7d673e3fc8c3961
+# 8d9aac57476145b98417e24b78edbee1
+msgid "Private Gateways"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:358
+#: ../../networking/virtual_private_cloud_config.rst:525
+#: ../../networking/virtual_private_cloud_config.rst:760
+#: ../../networking/virtual_private_cloud_config.rst:818
+#: ../../networking/virtual_private_cloud_config.rst:879
+#: ../../networking/virtual_private_cloud_config.rst:1045
+#: ../../networking/virtual_private_cloud_config.rst:1313
+# 0f79101b541d4297ad26fb3125843df6
+# 4e977612c45648cd8858b2f415c8d338
+# 764c6f4d2f214c1f9d33d36fec4bc931
+# 9ed4d3258aec4c01a9d1d7ab9ee6584a
+# 6210247a7c834558b9caf3e695d10eeb
+# b44f415f26cd49dcb58c424bce136a67
+# db0357d3ac9a479698e479d686e8cd9c
+msgid "Public IP Addresses"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:360
+#: ../../networking/virtual_private_cloud_config.rst:527
+#: ../../networking/virtual_private_cloud_config.rst:762
+#: ../../networking/virtual_private_cloud_config.rst:820
+#: ../../networking/virtual_private_cloud_config.rst:881
+#: ../../networking/virtual_private_cloud_config.rst:1047
+#: ../../networking/virtual_private_cloud_config.rst:1315
+# 70abe760545c42d0a794c6ce16a6c288
+# 0c346db4251b43b3a80a084bfd310d80
+# e6e45a6bac434db8b588e5a74c0902b8
+# d682a97cc5f14a0e801c4858edf11f48
+# 29fa45fc941945f891cbf96f6478db82
+# 941bc49890ae411aa05236d0e5102149
+# 3800a9e49a3b4745b17c1769febf9383
+msgid "Site-to-Site VPNs"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:362
+#: ../../networking/virtual_private_cloud_config.rst:529
+#: ../../networking/virtual_private_cloud_config.rst:764
+#: ../../networking/virtual_private_cloud_config.rst:822
+#: ../../networking/virtual_private_cloud_config.rst:883
+#: ../../networking/virtual_private_cloud_config.rst:1049
+#: ../../networking/virtual_private_cloud_config.rst:1317
+# ba528c5024fa489689b4d8ce0c1a0d85
+# 9b993afc4ad845f081de9838ee06ba00
+# 64ec433ac68146178442d14772e8ef45
+# 5a1b96032f234dbc85b6c87e45c31b31
+# c6f194d9a94a415a914fccd54dd4cffa
+# 1148599659df40fc8189b9aaf51587de
+# 5ae9778ec74a46dca0c4191ae03ecbb0
+msgid "Network ACL Lists"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:364
+#: ../../networking/virtual_private_cloud_config.rst:391
+# a3498a3bc728411aa4d5a7313f8d1fca
+# 1fd8c162a2124419bfff5003f1d58fe3
+msgid "Select Network ACL Lists."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:366
+# 9a1064fed3e342afb4b08a5d9e4ba3f9
+msgid "The following default rules are displayed in the Network ACLs page: default\\_allow, default\\_deny."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:369
+# eee1fde55c454e4ba76e51f7c0073681
+msgid "Click Add ACL Lists, and specify the following:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:371
+# 0019e51fcb5d4b609e3dfc8a2f798182
+msgid "**ACL List Name**: A name for the ACL list."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:373
+# 545d7afa82d944fc932e088624630881
+msgid "**Description**: A short description of the ACL list that can be displayed to users."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:378
+# 0eef9c80eb244e469737b6dbfed09ee5
+msgid "Creating an ACL Rule"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:393
+# 9ec1bad501f2492c875359dee57af36c
+msgid "In addition to the custom ACL lists you have created, the following default rules are displayed in the Network ACLs page: default\\_allow, default\\_deny."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:397
+#: ../../networking/virtual_private_cloud_config.rst:477
+# 56fa96725745426090705b3dea696c75
+# a5a846532a7f4d51b3b4ad850b809ffc
+msgid "Select the desired ACL list."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:399
+# 9b8b87a05d164a1e9388a9e96455c916
+msgid "Select the ACL List Rules tab."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:401
+# a35e39faa5504d4a939aa4cbc70ebd47
+msgid "To add an ACL rule, fill in the following fields to specify what kind of network traffic is allowed in the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:404
+# 09875f1f997e40c78467e4afbfd008a0
+msgid "**Rule Number**: The order in which the rules are evaluated."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:406
+# 718a86130cf84374b39ef695d7c0319f
+msgid "**CIDR**: The CIDR acts as the Source CIDR for the Ingress rules, and Destination CIDR for the Egress rules. To accept traffic only from or 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 incoming traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:413
+# 5e7871dde2bc4878b9630e4f89ef78a5
+msgid "**Action**: What action to be taken. Allow traffic or block."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:415
+# 960f6ba511804daf84bb14b0ee7d9fcb
+msgid "**Protocol**: The networking protocol that sources use to send traffic to the tier. 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. All supports all the traffic. Other option is Protocol Number."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:422
+# f8c920b2724240f7bcce7a3ffa539142
+msgid "**Start Port**, **End Port** (TCP, UDP only): A range of listening ports that are the destination for the incoming traffic. If you are opening a single port, use the same number in both fields."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:426
+# 6354d433a9d14d5aac441bc824aa18d8
+msgid "**Protocol Number**: The protocol number associated with IPv4 or IPv6. For more information, see `Protocol Numbers <http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xml>`_."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:430
+# 07c3ccfb6e804b7b9f9c6ee3e97baab6
+msgid "**ICMP Type**, **ICMP Code** (ICMP only): The type of message and error code that will be sent."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:433
+# fcf4685a451c434fa979261a9f4a989a
+msgid "**Traffic Type**: The type of traffic: Incoming or outgoing."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:435
+# 4cb2859d5c494c07a39e4f7f9c8b316d
+msgid "Click Add. The ACL rule is added."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:437
+# 6a1dc858d8f64fc4b59744f3ce271735
+msgid "You can edit the tags assigned to the ACL rules and delete the ACL rules you have created. Click the appropriate button in the Details tab."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:443
+# f116157c2cc3452d9381d88f34e5edcc
+msgid "Creating a Tier with Custom ACL List"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:445
+#: ../../networking/virtual_private_cloud_config.rst:461
+# a6dcc18dbcf14658bbe49913ec9d7258
+# a9d8c9ab4785456fa3b539a958e0a391
+msgid "Create a VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:447
+#: ../../networking/virtual_private_cloud_config.rst:467
+# c46ed610d0de4aabb7a66be1bc38b59c
+# 0eba50fd6c8241ce8c46b4f22adac8ce
+msgid "Create a custom ACL list."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:449
+#: ../../networking/virtual_private_cloud_config.rst:469
+# d641158411d6429aa58b99856ae3aa3e
+# ee2e3bb2bdcf4ae6ac56d960eb5c8414
+msgid "Add ACL rules to the ACL list."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:451
+#: ../../networking/virtual_private_cloud_config.rst:463
+# 1b9144de1d7c42478e9bcc5e58e8ad8b
+# 6416990ed47a46299ea5a399d45a25e5
+msgid "Create a tier in the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:453
+# d7313c7f5dc741be9cab74d4cc465987
+msgid "Select the desired ACL list while creating a tier."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:459
+# a2518e7f8c9347b1b2c5d2a4575170df
+msgid "Assigning a Custom ACL List to a Tier"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:465
+# 67c4657175a040149f04332d949d57bf
+msgid "Associate the tier with the default ACL rule."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:471
+# b83eff10b1ce44d2bcfae9e1e8920b6f
+msgid "Select the tier for which you want to assign the custom ACL."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:473
+# a44330dc8018442bb213f335afaab969
+msgid "Click the Replace ACL List icon. |replace-acl-icon.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:475
+# dd9f88e9651f45199d45d102228e2574
+msgid "The Replace ACL List dialog is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:485
+# 51a9c7e87c8c46bc8c2d01f1c70b1b5e
+msgid "Adding a Private Gateway to a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:487
+# 5bb03fe2db6344479a16781735c33d36
+msgid "A private gateway can be added by the root admin only. The VPC private network has 1:1 relationship with the NIC of the physical network. You can configure multiple private gateways to a single VPC. No gateways with duplicated VLAN and IP are allowed in the same data center."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:501
+# 56d5e3ac03e0437e95ee0073c44b19dd
+msgid "Click the Configure button of the VPC to which you want to configure load balancing rules."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:504
+#: ../../networking/virtual_private_cloud_config.rst:741
+#: ../../networking/virtual_private_cloud_config.rst:799
+#: ../../networking/virtual_private_cloud_config.rst:860
+#: ../../networking/virtual_private_cloud_config.rst:1294
+# 142dc427cda8454c943c18bb8066cbea
+# 508dbf4fb717460bbb35c009061f7564
+# fb95c3660854480db28704507ed4b900
+# 21eb0af33be64ade85d894838188a330
+# 75579da7cb264f9b80565e8bc7ef99b4
+msgid "The VPC page is displayed where all the tiers you created are listed in a diagram."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:507
+# 57a669215b0c459babdfa0f7477512bb
+msgid "Click the Settings icon."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:509
+#: ../../networking/virtual_private_cloud_config.rst:744
+#: ../../networking/virtual_private_cloud_config.rst:802
+# 27df09e575754d0bb04ff268ac13cd85
+# aec57c8f590a41ea9f3c4002d2bb2082
+# c83fad1cd6a74d3ba7da7551441402ad
+msgid "The following options are displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:531
+# c22be90142b04c5483ec525bb576d2c3
+msgid "Select Private Gateways."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:533
+# 2902accc6b5b49a1b204fd3fd16b1f5e
+msgid "The Gateways page is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:535
+# 92c2f2f09846411594265950bf78b9e4
+msgid "Click Add new gateway:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:537
+# 2c2c653d4d9d4521b4a7eb5c0e19f64c
+msgid "|add-new-gateway-vpc.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:541
+# 891ea4ddb15443e5ab8f32c8088c452f
+msgid "**Physical Network**: The physical network you have created in the zone."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:544
+# ca06b3e4deaf4ce3a02322454f78ed68
+msgid "**IP Address**: The IP address associated with the VPC gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:546
+# a5410ac8843e4c719973edf2d9bab4e0
+msgid "**Gateway**: The gateway through which the traffic is routed to and from the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:549
+# 955c1cc8e0f847408e1bd7754afbe13b
+msgid "**Netmask**: The netmask associated with the VPC gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:551
+# 852f638bb7234dc1a27dc43b5e016322
+msgid "**VLAN**: The VLAN associated with the VPC gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:553
+# 6f6c910aeb6d4ee29cfd16a8f169801a
+msgid "**Source NAT**: Select this option to enable the source NAT service on the VPC private gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:556
+# ca50f58a899f498d80e5d3cfaddc4e56
+msgid "See \":ref:`source-nat-priv-gw`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:558
+# 4004b1c124dc41d7afca981bfc6aa29d
+msgid "**ACL**: Controls both ingress and egress traffic on a VPC private gateway. By default, all the traffic is blocked."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:561
+# e0641473896e4fc4abe0e8d8f6500ad5
+msgid "See \":ref:`acl-priv-gw`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:563
+# c748dfb7b8764ed2b63524e27be99156
+msgid "The new gateway appears in the list. You can repeat these steps to add more gateway for this VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:570
+# 67cc2c7079b445b1aa5c3f8d7b0ff2bf
+msgid "Source NAT on Private Gateway"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:572
+# 2a8f60c14ac64d6e8d87dbce76bedb16
+msgid "You might want to deploy multiple VPCs with the same super CIDR and guest tier CIDR. Therefore, multiple guest VMs from different VPCs can have the same IPs to reach a enterprise data center through the private gateway. In such cases, a NAT service need to be configured on the private gateway to avoid IP conflicts. If Source NAT is enabled, the guest VMs in VPC reaches the enterprise network via private gateway IP address by using the NAT service."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:580
+# 13ba311a60ee4d00b7c597fafb945d0b
+msgid "The Source NAT service on a private gateway can be enabled while adding the private gateway. On deletion of a private gateway, source NAT rules specific to the private gateway are deleted."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:584
+# d8e4c7cc999e4730ad5bf6aa6f1b810f
+msgid "To enable source NAT on existing private gateways, delete them and create afresh with source NAT."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:591
+# 8c1553f72c3d4599892c402b65672931
+msgid "ACL on Private Gateway"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:593
+# 7a5729fff5c74521a2455b4e2b885a0f
+msgid "The traffic on the VPC private gateway is controlled by creating both ingress and egress network ACL rules. The ACLs contains both allow and deny rules. As per the rule, all the ingress traffic to the private gateway interface and all the egress traffic out from the private gateway interface are blocked."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:599
+# a7c844a5b9594a8c9090ef0fb4c815ac
+msgid "You can change this default behaviour while creating a private gateway. Alternatively, you can do the following:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:602
+#: ../../networking/virtual_private_cloud_config.rst:633
+# ce82be93f3014dafa0618abed1ddbc56
+# cf4dffd32e4045a0809d358aa5c89b4e
+msgid "In a VPC, identify the Private Gateway you want to work with."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:604
+# d931e9176936499f8a82583a1141f759
+msgid "In the Private Gateway page, do either of the following:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:606
+# df22ccb2fc4a4d4cbc59a8eced7cdd99
+msgid "Use the Quickview. See 3."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:608
+# 2e88948ffe35436398eb3dcc24a068a1
+msgid "Use the Details tab. See 4 through ."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:610
+# a6b863b1326a484080f38c0d2fffe32e
+msgid "In the Quickview of the selected Private Gateway, click Replace ACL, select the ACL rule, then click OK"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:613
+# 393090f44f4e449480ae7b9cd7171e2e
+msgid "Click the IP address of the Private Gateway you want to work with."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:615
+# 175a8bc977814206b1b438e55d487d9d
+msgid "In the Detail tab, click the Replace ACL button. |replace-acl-icon.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:618
+# cb57cf7f56bd4ab7b815980fd401d492
+msgid "The Replace ACL dialog is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:620
+# 52fd814724fc4614a6513bc716822b2e
+msgid "select the ACL rule, then click OK."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:622
+# 0594c5c95e77436b9fba83680438d29f
+msgid "Wait for few seconds. You can see that the new ACL rule is displayed in the Details page."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:627
+# ab277710c8d843ae81e757e3336317d0
+msgid "Creating a Static Route"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:629
+# 941e24b2fbef4bb7a3938f2fc6fb31ba
+msgid "CloudStack enables you to specify routing for the VPN connection you create. You can enter one or CIDR addresses to indicate which traffic is to be routed back to the gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:635
+# 6a994cb0af754d01bd335367a6f9d4f9
+msgid "In the Private Gateway page, click the IP address of the Private Gateway you want to work with."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:638
+# ed8760a26f62434da30f3b3d3094da23
+msgid "Select the Static Routes tab."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:640
+# dc6e78e20d8a49b18b1c7b68fc53d28f
+msgid "Specify the CIDR of destination network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:642
+# a267ec664f35442db0c8d33d273ec07a
+msgid "Click Add."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:644
+# 0b06e4ce11114d68a1d616162a29b46b
+msgid "Wait for few seconds until the new route is created."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:648
+# f66d2b908d63453ba9331658c3105974
+msgid "Blacklisting Routes"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:650
+# 5e262d8f57f94df080de1ebfd57089c5
+msgid "CloudStack enables you to block a list of routes so that they are not assigned to any of the VPC private gateways. Specify the list of routes that you want to blacklist in the ``blacklisted.routes`` global parameter. Note that the parameter update affects only new static route creations. If you block an existing static route, it remains intact and continue functioning. You cannot add a static route if the route is blacklisted for the zone."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:660
+# c95c27354e2b4308b6fe6cd594b07c4b
+msgid "Deploying VMs to the Tier"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:671
+#: ../../networking/virtual_private_cloud_config.rst:738
+#: ../../networking/virtual_private_cloud_config.rst:857
+#: ../../networking/virtual_private_cloud_config.rst:1291
+# d912fb084257494b9ea49a22d2952df6
+# 6a271ec843964a2392c14ea15bebcab2
+# 2db0b4a30faa4d2486de8987dc035b35
+# 42de70c0e3314b3b9312103ccf0318a3
+msgid "Click the Configure button of the VPC to which you want to deploy the VMs."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:674
+# a10f32d36f52426288a9a524c7034bde
+msgid "The VPC page is displayed where all the tiers you have created are listed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:677
+# e8a7f18c2c2443b8afb0ba68b10df211
+msgid "Click Virtual Machines tab of the tier to which you want to add a VM."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:679
+# 2021d183ee7640019cdf5bdbfe5498f3
+msgid "|add-vm-vpc.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:681
+# 2d48018b840946fd8af8d726d139f5d0
+msgid "The Add Instance page is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:683
+# 3090bc6cae14453a973abac600b9c2cf
+msgid "Follow the on-screen instruction to add an instance. For information on adding an instance, see the Installation Guide."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:688
+# dcd8e45c721b400eaba7cde1328bdc81
+msgid "Deploying VMs to VPC Tier and Shared Networks"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:690
+# 17212685c197411da69afebe1fd43553
+msgid "CloudStack allows you deploy VMs on a VPC tier and one or more shared networks. With this feature, VMs deployed in a multi-tier application can receive monitoring services via a shared network provided by a service provider."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:695
+# fc5a14ca00a74032a5a578f32fe13799
+msgid "Log in to the CloudStack UI as an administrator."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:697
+# 32b36a6c72fa45f99cc16fe65842edb4
+msgid "In the left navigation, choose Instances."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:699
+# 2f251266e8f84c3bb1eb88f9cbf3421b
+msgid "Click Add Instance."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:701
+# e9423e60b1d047809ea35f96287dc4cb
+msgid "Select a zone."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:703
+# 270e50111a9d4c328ccfd3e302a1712c
+msgid "Select a template or ISO, then follow the steps in the wizard."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:705
+# b9f9249e068d492a89e876e8d5282100
+msgid "Ensure that the hardware you have allows starting the selected service offering."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:708
+# 646cca07fc3241d9bdcb00578a77e3e3
+msgid "Under Networks, select the desired networks for the VM you are launching."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:711
+# c5f162c06a0641cf8ca1c4ee6f54f651
+msgid "You can deploy a VM to a VPC tier and multiple shared networks."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:713
+# edcfad81a1b04c068848242fac9adfac
+msgid "|addvm-tier-sharednw.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:715
+# efc4e3cc0b2843ccb58ccc673b8f20cd
+msgid "Click Next, review the configuration and click Launch."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:717
+# 34b1022eb48b4dbf92712eb65b1308c8
+msgid "Your VM will be deployed to the selected VPC tier and shared network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:721
+# e75183b01c2e4d9a87561e256f60760d
+msgid "Acquiring a New IP Address for a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:723
+# 8712a3a4537f4038a9703ae12a15da40
+msgid "When you acquire an IP address, all IP addresses are allocated to VPC, not to the guest networks within the VPC. The IPs are associated to the guest network only when the first port-forwarding, load balancing, or Static NAT rule is created for the IP or the network. IP can't be associated to more than one network at a time."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:766
+# f3548df663fd4502b857204d85782486
+msgid "Select IP Addresses."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:768
+# 8b29cfd1cdcd4018ae63dfe1624f5e58
+msgid "The Public IP Addresses page is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:770
+# b571bcf25fd64067a9bc6c684f923ef4
+msgid "Click Acquire New IP, and click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:772
+# 5bc9804e2b3a444c9eca95b480c5247e
+msgid "You are prompted for confirmation because, typically, IP addresses are a limited resource. Within a few moments, the new IP address should appear with the state Allocated. You can now use the IP address in port forwarding, load balancing, and static NAT rules."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:779
+# f14eea7624044595966630cad5fb25a4
+msgid "Releasing an IP Address Alloted to a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:781
+# a32c2ee15c7f41209d11d1460881df99
+msgid "The IP address is a limited resource. If you no longer need a particular IP, you can disassociate it from its VPC and return it to the pool of available addresses. An IP address can be released from its tier, only when all the networking ( port forwarding, load balancing, or StaticNAT ) rules are removed for this IP address. The released IP address will still belongs to the same VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:797
+# cff29ec3366646748c80c78ae0b21df3
+msgid "Click the Configure button of the VPC whose IP you want to release."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:824
+# e61ac663ca83460e902eb75be8323c7b
+msgid "Select Public IP Addresses."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:826
+#: ../../networking/virtual_private_cloud_config.rst:887
+#: ../../networking/virtual_private_cloud_config.rst:1053
+#: ../../networking/virtual_private_cloud_config.rst:1321
+# d6214f88ed8e46abb807a2b8e2f87bf7
+# fee8b392a6654e98b2a92ed46a6a1d09
+# 86b1ba91303847249fe71e091aa53075
+# e80daef3c8c548fe905c71e3888d9d35
+msgid "The IP Addresses page is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:828
+# 7100a75c5b7f4e94af12eba67cc769d7
+msgid "Click the IP you want to release."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:830
+# 5d08cda75ef64158bc169fa0b4d55bfd
+msgid "In the Details tab, click the Release IP button |release-ip-icon.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:836
+# 66b58ca8d7e8481184b5f30fb10aeb3a
+msgid "Enabling or Disabling Static NAT on a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:838
+# 5ffcce98eb5341c4815405feb3f45e3d
+msgid "A static NAT rule maps a public IP address to the private IP address of a VM in a VPC to allow Internet traffic to it. This section tells how to enable or disable static NAT for a particular IP address in a VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:842
+# 3a033892a74543d4a655001ee01f7102
+msgid "If port forwarding rules are already in effect for an IP address, you cannot enable static NAT to that IP."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:845
+# 3ced6dfc6cda40c59a7663608968ae25
+msgid "If a guest VM is part of more than one network, static NAT rules will function only if they are defined on the default network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:863
+# a101d2d938bd44ef8b442c2dd878803b
+msgid "For each tier, the following options are displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:885
+#: ../../networking/virtual_private_cloud_config.rst:1051
+#: ../../networking/virtual_private_cloud_config.rst:1319
+# 2aa87b8efca045199c60a69232f4100c
+# f29854dbe679478497f195c125c70fc3
+# 0ca75518c2c1401bada82a5f5b3953b2
+msgid "In the Router node, select Public IP Addresses."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:889
+# ecb19327446e44f7a44f71eaef9cc73a
+msgid "Click the IP you want to work with."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:891
+# 54b9ba8fad964d51a0442fc5838ba574
+msgid "In the Details tab,click the Static NAT button. |enable-disable.png| The button toggles between Enable and Disable, depending on whether static NAT is currently enabled for the IP address."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:896
+# ee96b8eeef6f44169338cbec4bd552e2
+msgid "If you are enabling static NAT, a dialog appears as follows:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:898
+# 2934b5d934b343aab14d143fb537ce07
+msgid "|select-vmstatic-nat.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:900
+# ba4894eec4ee4f8ab908308bf7f2b682
+msgid "Select the tier and the destination VM, then click Apply."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:904
+# 6bc44c698b784002948ea93ac931ccb3
+msgid "Adding Load Balancing Rules on a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:906
+# d55b224d3d4d427da85774962a911e9b
+msgid "In a VPC, you can configure two types of load balancing: external LB and internal LB. External LB is nothing but a LB rule created to redirect the traffic received at a public IP of the VPC virtual router. The traffic is load balanced within a tier based on your configuration. Citrix NetScaler and VPC virtual router are supported for external LB. When you use internal LB service, traffic received at a tier is load balanced across different VMs within that tier. For example, traffic reached at Web tier is redirected to another VM in that tier. External load balancing devices are not supported for internal LB. The service is provided by a internal LB VM configured on the target tier."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:919
+# 40e935f35e0c40ada19216e535aa1258
+msgid "Load Balancing Within a Tier (External LB)"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:921
+# f415c289521945488fc0ee0094a1dab0
+msgid "A CloudStack user or administrator may create load balancing rules that balance traffic received at a public IP to one or more VMs that belong to a network tier that provides load balancing service in a VPC. A user creates a rule, specifies an algorithm, and assigns the rule to a set of VMs within a tier."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:929
+# 3e4fdfab26c8433f985733abf6b8fab2
+msgid "Enabling NetScaler as the LB Provider on a VPC Tier"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:931
+# f4009b64ee9a4abc935568ba00072b14
+msgid "Add and enable Netscaler VPX in dedicated mode."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:933
+# 11c807f9e62a4acb9f8b3ef0d007c2c9
+msgid "Netscaler can be used in a VPC environment only if it is in dedicated mode."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:936
+# 57a85fbc857449ee89781dd4fce1788c
+msgid "Create a network offering, as given in \":ref:`create-net-offering-ext-lb`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:938
+# 08a0f277fc3f43b694322360de337dfc
+msgid "Create a VPC with Netscaler as the Public LB provider."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:940
+# ecc067da6bf9448587d900d0602ecacd
+msgid "For more information, see `\"Adding a Virtual Private Cloud\" <#adding-a-virtual-private-cloud>`_."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:943
+# aa3b5b48c05343338d0ee08f3382b40d
+msgid "For the VPC, acquire an IP."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:945
+# 7c4c3743af9240d882f3ba1d438b3bd8
+msgid "Create an external load balancing rule and apply, as given in :ref:`create-ext-lb-rule`."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:952
+# 65a1193d54904d989149249c4257b9c1
+msgid "Creating a Network Offering for External LB"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:954
+# e69c20a921124dc7b5ac28a8bc23f254
+msgid "To have external LB support on VPC, create a network offering as follows:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:957
+#: ../../networking/virtual_private_cloud_config.rst:1163
+# 27d475982a384fed8f13220941eded23
+# 2da0ddfe20c0412a9dc8725da9ebfb08
+msgid "Log in to the CloudStack UI as a user or admin."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:959
+#: ../../networking/virtual_private_cloud_config.rst:1165
+# 2e6d402ef3d044488597c6501ca6749d
+# f974a014675745ceae4ebb19113bc49e
+msgid "From the Select Offering drop-down, choose Network Offering."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:961
+#: ../../networking/virtual_private_cloud_config.rst:1167
+# 08107e25d3ae4ed5a4e72a9ef68249af
+# f88397d4525c49d4b10ca8f6d24c5999
+msgid "Click Add Network Offering."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:963
+#: ../../networking/virtual_private_cloud_config.rst:1169
+# 0b77090696474c0a9cab45f79b1c7986
+# e1cffd47fe2e4f3089c2620a68b839a1
+msgid "In the dialog, make the following choices:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:965
+#: ../../networking/virtual_private_cloud_config.rst:1171
+# 60d2abd68eb948dbaba04e1ac5723b86
+# 2e15e5f8b3704612a4d58813e4d32f6b
+msgid "**Name**: Any desired name for the network offering."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:967
+#: ../../networking/virtual_private_cloud_config.rst:1173
+# 3959d6091cd747cb937e8f842088c32e
+# 5f694898705c49328c1a2e142eb14d1f
+msgid "**Description**: A short description of the offering that can be displayed to users."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:970
+#: ../../networking/virtual_private_cloud_config.rst:1176
+# 2e0e45c2f8604206ab9ab52b64e032e0
+# 40a66509e3424c24bb6186610a441bac
+msgid "**Network Rate**: Allowed data transfer rate in MB per second."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:972
+#: ../../networking/virtual_private_cloud_config.rst:1178
+# 33f13b044bc94b5b8696d75ddf4b8bc3
+# a160a569847143f797400c4ff977efdf
+msgid "**Traffic Type**: The type of network traffic that will be carried on the network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:975
+#: ../../networking/virtual_private_cloud_config.rst:1181
+# aaf9ff68483341d98ede19f290845e4d
+# c3356024660a4455a0ceac2dcae5caee
+msgid "**Guest Type**: Choose whether the guest network is isolated or shared."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:978
+#: ../../networking/virtual_private_cloud_config.rst:1184
+# 78da437179454d2e9bb2b2566016b345
+# 8e43b8eb7620486dafe2037f9644fc74
+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."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:982
+#: ../../networking/virtual_private_cloud_config.rst:1188
+# b8efdabd98ae4986a6423993e842848f
+# a09dbae19ba24a44abe4d1e06d94391d
+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\" <#about-virtual-private-clouds>`_."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:988
+#: ../../networking/virtual_private_cloud_config.rst:1195
+# f833921e66e7405e90b64ecab4f06585
+# 60780dc0b1414010b97ef9ee9fdf6896
+msgid "**Specify VLAN**: (Isolated guest networks only) Indicate whether a VLAN should be specified when this offering is used."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:991
+# c39ddc76ab104334a4dc179d2666185f
+msgid "**Supported Services**: Select Load Balancer. Use Netscaler or VpcVirtualRouter."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:994
+# 0f2a2787484945d4893a95c93e013659
+msgid "**Load Balancer Type**: Select Public LB from the drop-down."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:996
+# 012d5de507d14d86a63f00c612267262
+msgid "**LB Isolation**: Select Dedicated if Netscaler is used as the external LB provider."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:999
+#: ../../networking/virtual_private_cloud_config.rst:1203
+# 32714ec60c95462a86fad6f4ea8a389f
+# 6d1b55437586405195f96d4e1901a030
+msgid "**System Offering**: Choose the system service offering that you want virtual routers to use in this network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1002
+#: ../../networking/virtual_private_cloud_config.rst:1206
+# ccddc4e596ac4b9590b1e89143679f4c
+# 5b0c2de816bb4f3489ea6c0aaf56dd92
+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."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1006
+#: ../../networking/virtual_private_cloud_config.rst:1210
+# 64b8ac5900b040949abdbe1be369798e
+# 86eacc968b5642af9d7708d20b05fa0b
+msgid "Click OK and the network offering is created."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1012
+# 7d8aa307714e45a48e2b8a026f88ecd5
+msgid "Creating an External LB Rule"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1023
+# ec858cbb6d054d82b7344347f3d1f80a
+msgid "Click the Configure button of the VPC, for which you want to configure load balancing rules."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1026
+#: ../../networking/virtual_private_cloud_config.rst:1239
+# 24c4acc56c8546b48b0d1ba8225aa2c3
+# 8623ea1fa5f64fc882bc161a00e0de31
+msgid "The VPC page is displayed where all the tiers you created listed in a diagram."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1055
+#: ../../networking/virtual_private_cloud_config.rst:1323
+# faa2aca06f244ec79e1495f403d60fba
+# f6b4d72a1ace463aaeae65e85f5351fe
+msgid "Click the IP address for which you want to create the rule, then click the Configuration tab."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1058
+# 05fb941cda1540a6ae76a68c80d28164
+msgid "In the Load Balancing node of the diagram, click View All."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1060
+#: ../../networking/virtual_private_cloud_config.rst:1328
+# a68bbaad32ad4fb1a32434a21627c7df
+# 513eb1682d554f15af9624073505f185
+msgid "Select the tier to which you want to apply the rule."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1064
+#: ../../networking/virtual_private_cloud_config.rst:1249
+# 48072a5bd67b4fc2b091903b2930ef20
+# 23e879002b734874bb3fb8648d82ec9f
+msgid "**Name**: A name for the load balancer rule."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1066
+# 035ce1c6b7094ddfb03cf84e79fe13fb
+msgid "**Public Port**: The port that receives the incoming traffic to be balanced."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1069
+# 95e57b758d354580b0723b1cf69b1ad9
+msgid "**Private Port**: The port that the VMs will use to receive the traffic."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1072
+#: ../../networking/virtual_private_cloud_config.rst:1268
+# 9401419db1ac40dd8912809bfb47d5fa
+# c29c451e2c474605af3093430f4fe416
+msgid "**Algorithm**. Choose the load balancing algorithm you want CloudStack to use. CloudStack supports the following well-known algorithms:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1076
+#: ../../networking/virtual_private_cloud_config.rst:1272
+# 45872bf350da46e8915a4c200e500d47
+# 2fe10525962546129f438019ddb43570
+msgid "Round-robin"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1078
+#: ../../networking/virtual_private_cloud_config.rst:1274
+# b89b8c35da0e4067aa0e2dfc46507db4
+# 384c8fd5fe8049389138586119a8e392
+msgid "Least connections"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1080
+#: ../../networking/virtual_private_cloud_config.rst:1276
+# 75b481e88cb749ee9744fa2d4153d658
+# a656566824f644a7a9bf0c5aa7f7ce82
+msgid "Source"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1082
+# 156eaabf00d6402fb1a6f26cdc8bdc3a
+msgid "**Stickiness**. (Optional) Click Configure and choose the algorithm for the stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1086
+# 5a609fc01f0c442fbaa6859f3c48de9d
+msgid "**Add VMs**: Click Add VMs, then select two or more VMs that will divide the load of incoming traffic, and click Apply."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1089
+# 227920ab85304ccd9ef2ff2fcc816394
+msgid "The new load balancing rule appears in the list. You can repeat these steps to add more load balancing rules for this IP address."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1094
+# 9e2c252f60374e98b336b982bdb5a807
+msgid "Load Balancing Across Tiers"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1096
+# b0b3d2bc1154428ea7aa2a73ccf65ca9
+msgid "CloudStack supports sharing workload across different tiers within your VPC. Assume that multiple tiers are set up in your environment, such as Web tier and Application tier. Traffic to each tier is balanced on the VPC virtual router on the public side, as explained in `\"Adding Load Balancing Rules on a VPC\" <#adding-load-balancing-rules-on-a-vpc>`_. If you want the traffic coming from the Web tier to the Application tier to be balanced, use the internal load balancing feature offered by CloudStack."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1107
+# fbb2a59a26334767857dae55b7dd76d2
+msgid "How Does Internal LB Work in VPC?"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1109
+# 9f3100aad1e345bb8ac547e9ff36084f
+msgid "In this figure, a public LB rule is created for the public IP 72.52.125.10 with public port 80 and private port 81. The LB rule, created on the VPC virtual router, is applied on the traffic coming from the Internet to the VMs on the Web tier. On the Application tier two internal load balancing rules are created. An internal LB rule for the guest IP 10.10.10.4 with load balancer port 23 and instance port 25 is configured on the VM, InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.4 with load balancer port 45 and instance port 46 is configured on the VM, InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.6, with load balancer port 23 and instance port 25 is configured on the VM, InternalLBVM2."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1121
+# c94baade36ca41029339b5771845f6eb
+msgid "|vpc-lb.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1125
+# 6b5c736fe39c453f9df86d49e415bb0d
+msgid "Guidelines"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1127
+# f48db5cf237f48c1b83470d2b3619c89
+msgid "Internal LB and Public LB are mutually exclusive on a tier. If the tier has LB on the public side, then it can't have the Internal LB."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1130
+# 39c3726d0f1e417ba4856caefdc69c5f
+msgid "Internal LB is supported just on VPC networks in CloudStack 4.2 release."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1133
+# c9b5009bd45949ca9adfe8bad469126e
+msgid "Only Internal LB VM can act as the Internal LB provider in CloudStack 4.2 release."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1136
+# f0db26b4389241deb62e3e62af4ae108
+msgid "Network upgrade is not supported from the network offering with Internal LB to the network offering with Public LB."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1139
+# cdacc61443a24192b33aa89bf454081d
+msgid "Multiple tiers can have internal LB support in a VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1141
+# 08ebb9d7ed624f58a875207bb6be9859
+msgid "Only one tier can have Public LB support in a VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1145
+# 0cf099b085094a858d1b083c8e2f72f6
+msgid "Enabling Internal LB on a VPC Tier"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1147
+# 381918d116bf406189b9d4dd38f04f33
+msgid "Create a network offering, as given in :ref:`creating-net-offering-internal-lb`."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1150
+# f09e6b3612574602ae51429ca4126c05
+msgid "Create an internal load balancing rule and apply, as given in :ref:`create-int-lb-rule`."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1157
+# 25a70af8ca1e41f18f48eb08ef5d850a
+msgid "Creating a Network Offering for Internal LB"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1159
+# 08c27533594e44e582e605b3e9b3df6a
+msgid "To have internal LB support on VPC, either use the default offering, DefaultIsolatedNetworkOfferingForVpcNetworksWithInternalLB, or create a network offering as follows:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1198
+# a41f382608f64d309fbe464cf7137a17
+msgid "**Supported Services**: Select Load Balancer. Select ``InternalLbVM`` from the provider list."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1201
+# 163583059e0b4dc38ec9a9324be12914
+msgid "**Load Balancer Type**: Select Internal LB from the drop-down."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1216
+# c468f85bcd804f59b3e50b6395b59e2a
+msgid "Creating an Internal LB Rule"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1218
+# 97768defcebc48e484aca56eed453215
+msgid "When you create the Internal LB rule and applies to a VM, an Internal LB VM, which is responsible for load balancing, is created."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1221
+# 68b5cb10c6e7463690bbeefba32870fb
+msgid "You can view the created Internal LB VM in the Instances page if you navigate to **Infrastructure** > **Zones** > <zone\\_ name> > <physical\\_network\\_name> > **Network Service Providers** > **Internal LB VM**. You can manage the Internal LB VMs as and when required from the location."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1236
+# 3df2a5995876429facf54c5a8446811d
+msgid "Locate the VPC for which you want to configure internal LB, then click Configure."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1242
+# 6f207d8e5df84a4b8c67c56fd431c1d7
+msgid "Locate the Tier for which you want to configure an internal LB rule, click Internal LB."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1245
+# 3d886b162d3b4cb78187e716d7935265
+msgid "In the Internal LB page, click Add Internal LB."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1247
+# f08b145932924c3caba6b02b3e38b19a
+msgid "In the dialog, specify the following:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1251
+# 551399e510014c7fbc3cf5f1a0110627
+msgid "**Description**: A short description of the rule that can be displayed to users."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1254
+# 6cf0e4a86d4043878ef3a656833ff790
+msgid "**Source IP Address**: (Optional) The source IP from which traffic originates. The IP is acquired from the CIDR of that particular tier on which you want to create the Internal LB rule. If not specified, the IP address is automatically allocated from the network CIDR."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1260
+# 2feac41c2e1b49e48df5d82f1bda3eef
+msgid "For every Source IP, a new Internal LB VM is created for load balancing."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1263
+# 4063dce4a7c94bc19982815512a92efa
+msgid "**Source Port**: The port associated with the source IP. Traffic on this port is load balanced."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1266
+# 7c1698db8e014d99ba6821c2749a280a
+msgid "**Instance Port**: The port of the internal LB VM."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1280
+# 22a6cc81098f4226b86f3e9b82cd4bba
+msgid "Adding a Port Forwarding Rule on a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1326
+# d8e4477eb9414ccbad83f00d2dbb0bcc
+msgid "In the Port Forwarding node of the diagram, click View All."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1332
+# 0dae384f57174980aacd91725f200202
+msgid "**Public Port**: The port to which public traffic will be addressed on the IP address you acquired in the previous step."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1335
+# e58b66b804154984ac2848feded76f18
+msgid "**Private Port**: The port on which the instance is listening for forwarded public traffic."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1338
+# fdf35395971c43d7b03e9bf1a85afd10
+msgid "**Protocol**: The communication protocol in use between the two ports."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1341
+# 3488a82bf48c43dbbcf214cbc6915803
+msgid "TCP"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1343
+# 65fd29db5c09403aad6a2b1688af4414
+msgid "UDP"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1345
+# 3092d0bc5e29456e9c83bf700d0989ed
+msgid "**Add VM**: Click Add VM. Select the name of the instance to which this rule applies, and click Apply."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1348
+# 957a6544516446768dd3e34e10b081d8
+msgid "You can test the rule by opening an SSH session to the instance."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1352
+# fa091c39660d4a79ad8d7663f777f9b0
+msgid "Removing Tiers"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1354
+# 23a5734e02084bdcb2075d5b7ff872ef
+msgid "You can remove a tier from a VPC. A removed tier cannot be revoked. When a tier is removed, only the resources of the tier are expunged. All the network rules (port forwarding, load balancing and staticNAT) and the IP addresses associated to the tier are removed. The IP address still be belonging to the same VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1372
+# 9b3b9eb7db0b4fc3983bc9bd94eb5f2c
+msgid "The Configure VPC page is displayed. Locate the tier you want to work with."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1375
+# b4b3c46f5c7c43d2a38281a25cff0a95
+msgid "Select the tier you want to remove."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1377
+# 1c7ac4dbb28d46be86f3ab4794676d8c
+msgid "In the Network Details tab, click the Delete Network button. |del-tier.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1380
+# b2a09950453549488f1a8233090286dd
+msgid "Click Yes to confirm. Wait for some time for the tier to be removed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1384
+# 4dc06c7515ba4393856799669ecf6a8a
+msgid "Editing, Restarting, and Removing a Virtual Private Cloud"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1386
+# c61c02b8451b4d52bc9e0b8232ce8d73
+msgid "Ensure that all the tiers are removed before you remove a VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1397
+# 7e354bd7277d4569a94e6a022ae111e5
+msgid "Select the VPC you want to work with."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1399
+# 4e23279e59874fcdb4e38c54c1054efa
+msgid "In the Details tab, click the Remove VPC button |remove-vpc.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1401
+# 3227af3c60cb400c8679fd84202d852a
+msgid "You can remove the VPC by also using the remove button in the Quick View."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1404
+# 0e3026db29aa4e3780f95b598c5483fc
+msgid "You can edit the name and description of a VPC. To do that, select the VPC, then click the Edit button. |vpc-edit-icon.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1407
+# 5d731df0a6ca4174a2b9f85dba537a8a
+msgid "To restart a VPC, select the VPC, then click the Restart button. |restart-vpc.png|"
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking2.pot b/source/adminguide/locale/pot/networking2.pot
new file mode 100644
index 0000000..a2f6fbd
--- /dev/null
+++ b/source/adminguide/locale/pot/networking2.pot
@@ -0,0 +1,6796 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:08-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../networking2.rst:18
+# 4c134b7a710148a3ab2766ead2eecc37
+msgid "Managing Networks and Traffic"
+msgstr ""
+
+#: ../../networking2.rst:20
+# 3dea6f52fda445569cf65ce098c1b84c
+msgid "In a CloudStack, guest VMs can communicate with each other using shared infrastructure with the security and user perception that the guests have a private LAN. The CloudStack virtual router is the main component providing networking features for guest traffic."
+msgstr ""
+
+#: ../../networking2.rst:26
+# c845ad86dd2c41e091ae6234539d6672
+msgid "Guest Traffic"
+msgstr ""
+
+#: ../../networking2.rst:28
+# d8fc8ee73a5d4bc5915b1fd2e4eb7108
+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 ""
+
+#: ../../networking2.rst:33
+# e56f7eded9f441659c145763662800d5
+msgid "See a typical guest traffic setup given below:"
+msgstr ""
+
+#: ../../networking2.rst:35
+# 6823c848cad04848a61dbff31215055b
+msgid "|guest-traffic-setup.png|"
+msgstr ""
+
+#: ../../networking2.rst:37
+# 5cc5110f1ee142468aaacae83aca4060
+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 router. Its eth2 interface is assigned a public IP address for public traffic. If multiple public VLAN is used, the router will have multiple public interfaces."
+msgstr ""
+
+#: ../../networking2.rst:48
+# b252663b377641b6a497a33ae549a1c3
+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 ""
+
+#: ../../networking2.rst:53
+# 08366e677b394ff486de117a98b53a1c
+msgid "Source NAT is automatically configured in the virtual router to forward outbound traffic for all guest VMs"
+msgstr ""
+
+#: ../../networking2.rst:57
+# 8db3692749f44d209bc4b6643b4bed42
+msgid "Networking in a Pod"
+msgstr ""
+
+#: ../../networking2.rst:59
+# f92d73cb904740b69bb3044663745ef9
+msgid "The figure below illustrates network setup within a single pod. The hosts are connected to a pod-level switch. At a minimum, the hosts should have one physical uplink to each switch. Bonded NICs are supported as well. The pod-level switch is a pair of redundant gigabit switches with 10 G uplinks."
+msgstr ""
+
+#: ../../networking2.rst:65
+# 3cf0b62b19c942899bbf90f9c3e111be
+msgid "|networksinglepod.png|"
+msgstr ""
+
+#: ../../networking2.rst:67
+# 61fa2a0f3f6046b2a1d038ab3e5ea255
+msgid "Servers are connected as follows:"
+msgstr ""
+
+#: ../../networking2.rst:71
+# 9dd3a988270c471db1794e964c4a56c7
+msgid "Storage devices are connected to only the network that carries management traffic."
+msgstr ""
+
+#: ../../networking2.rst:76
+# 2e2c8c8881fa4cd5be1de3eec14c1d1c
+msgid "Hosts are connected to networks for both management traffic and public traffic."
+msgstr ""
+
+#: ../../networking2.rst:81
+# 3e2f4aed8c924b9e80395bdf1e1c2f73
+msgid "Hosts are also connected to one or more networks carrying guest traffic."
+msgstr ""
+
+#: ../../networking2.rst:84
+# d85f7dccd3784410a2b1d16863f27a73
+msgid "We recommend the use of multiple physical Ethernet cards to implement each network interface as well as redundant switch fabric in order to maximize throughput and improve reliability."
+msgstr ""
+
+#: ../../networking2.rst:89
+# d776e46765c84e1181b3e580c688c626
+msgid "Networking in a Zone"
+msgstr ""
+
+#: ../../networking2.rst:91
+# d239d21a20c649aba205a75b8c13f10d
+msgid "The following figure illustrates the network setup within a single zone."
+msgstr ""
+
+#: ../../networking2.rst:93
+# a576182d84c04ab98566ba031289abb1
+msgid "|networksetupzone.png|"
+msgstr ""
+
+#: ../../networking2.rst:95
+# f9ec1f6b949e428b918524444e4e4c2d
+msgid "A firewall for management traffic operates in the NAT mode. The network typically is assigned IP addresses in the 192.168.0.0/16 Class B private address space. Each pod is assigned IP addresses in the 192.168.\\*.0/24 Class C private address space."
+msgstr ""
+
+#: ../../networking2.rst:100
+# f0acacb8a1ac4f92b32c742e22c0aa30
+msgid "Each zone has its own set of public IP addresses. Public IP addresses from different zones do not overlap."
+msgstr ""
+
+#: ../../networking2.rst:104
+# 48df0d18a8e448909a0b484414468735
+msgid "Basic Zone Physical Network Configuration"
+msgstr ""
+
+#: ../../networking2.rst:106
+# 20494f4a5f604216bed0571fa51a7ddb
+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 ""
+
+#: ../../networking2.rst:112
+# b5ca7152b69d4a2d8fcc434cb9267f7c
+msgid "Advanced Zone Physical Network Configuration"
+msgstr ""
+
+#: ../../networking2.rst:114
+# 954218a2f4204be989c2436ecd73edc1
+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 ""
+
+#: ../../networking2.rst:119
+# b3ba0f73a0df4d36a3cb4f204c4dee2d
+msgid "Configure Guest Traffic in an Advanced Zone"
+msgstr ""
+
+#: ../../networking2.rst:121
+# ecd9d16a0a0c4dff9373a2dbf58e4c09
+msgid "These steps assume you have already logged in to the CloudStack UI. To configure the base guest network:"
+msgstr ""
+
+#: ../../networking2.rst:126
+# 78523deb5f20412383b00c879c3b21aa
+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 ""
+
+#: ../../networking2.rst:131
+#: ../../networking2.rst:215
+#: ../../networking2.rst:1597
+# 6257a61390924cb3bd8aeeac1a071780
+# 991bb1da835442988405cc08b7001c28
+# 61c9a678d28f40d599b72b6c2670f13d
+msgid "Click the Network tab."
+msgstr ""
+
+#: ../../networking2.rst:135
+#: ../../networking2.rst:219
+#: ../../networking2.rst:1601
+# 81ea8b8553864a83843ba71e6bf101af
+# 2d5debf29d7e42428b6c6d0ea25b7b92
+# e156f160e7c64f60a6d9c5bd8b8164a9
+msgid "Click Add guest network."
+msgstr ""
+
+#: ../../networking2.rst:137
+# 7b664064e09a4c25ac5afbc839d6bf94
+msgid "The Add guest network window is displayed:"
+msgstr ""
+
+#: ../../networking2.rst:139
+# 467663954a4745be91a92b1d95b23080
+msgid "|addguestnetwork.png|"
+msgstr ""
+
+#: ../../networking2.rst:143
+#: ../../networking2.rst:4200
+#: ../../networking2.rst:5082
+# a7bd588835354863bf7622de307358f6
+# e19b9c5096354c629c5cb237adbb7845
+# d0d70642a5104df08ab13289bdd0c02b
+msgid "Provide the following information:"
+msgstr ""
+
+#: ../../networking2.rst:147
+# 02150922f26d47f3b7a13ca653f96421
+msgid "**Name**. The name of the network. This will be user-visible"
+msgstr ""
+
+#: ../../networking2.rst:151
+# 71b93ff5fc154455a9e31bb96fc71d72
+msgid "**Display Text**: The description of the network. This will be user-visible"
+msgstr ""
+
+#: ../../networking2.rst:156
+# 3aa2ff94b2f3453caf3cf8a60cf57294
+msgid "**Zone**: The zone in which you are configuring the guest network."
+msgstr ""
+
+#: ../../networking2.rst:160
+# 8020d9a242d94611b622a7fbbf730632
+msgid "**Network offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network"
+msgstr ""
+
+#: ../../networking2.rst:165
+# 409cf198865e4ed4a4ceda18fb9c08f8
+msgid "**Guest Gateway**: The gateway that the guests should use"
+msgstr ""
+
+#: ../../networking2.rst:169
+# 1b24f9a1dc1a468fa60412939100a476
+msgid "**Guest Netmask**: The netmask in use on the subnet the guests will use"
+msgstr ""
+
+#: ../../networking2.rst:174
+#: ../../networking2.rst:870
+#: ../../networking2.rst:1251
+#: ../../networking2.rst:1428
+#: ../../networking2.rst:1755
+#: ../../networking2.rst:3144
+#: ../../networking2.rst:3662
+#: ../../networking2.rst:4319
+#: ../../networking2.rst:4355
+#: ../../networking2.rst:5118
+#: ../../networking2.rst:5211
+#: ../../networking2.rst:5458
+#: ../../networking2.rst:5499
+#: ../../networking2.rst:6953
+# 91173c96c5184ed8a0542f56f340c125
+# 6968c572935348d89aa2cfe9419c00cd
+# 9ee0ac806d854e47bd3f486e9e128034
+# 5d45344f6070463bb25599b8c1ac7145
+# 0527e80fdbfe4508a05ede62a047cd51
+# c6016b8b267942548713429d3c7e74e0
+# 3ccbb578962b42588bd495e0dbd57f76
+# f5954071e2a24961b74b3dcca98a33b1
+# e6ab2eac57564f63bfeea06d1691c574
+# 6d9b635b27544fb3adc30d7e8bc3070b
+# aae381906435443489b7db544138dc66
+# 0218e655795843808690f324bad3bbf9
+# 2c8c3e70a3904e0fb57a195a43305818
+# bc97ad0f132944ffbb337c4649b00a51
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking2.rst:177
+# bb8994cf25ed4d0f9c1738b0a288a66d
+msgid "Configure Public Traffic in an Advanced Zone"
+msgstr ""
+
+#: ../../networking2.rst:179
+# 53d266b50a684d08b2b57469d0ba2117
+msgid "In a zone that uses advanced networking, you need to configure at least one range of IP addresses for Internet traffic."
+msgstr ""
+
+#: ../../networking2.rst:183
+# 173ecef5b8d34d51b8690fdff5bcfc1f
+msgid "Configuring a Shared Guest Network"
+msgstr ""
+
+#: ../../networking2.rst:187
+#: ../../networking2.rst:761
+#: ../../networking2.rst:1569
+# 93a4d181244541b381a3a70d1daea74e
+# 55cf11dd995e463eb0015820a7998825
+# 648d4dddf66542dd975f89802e4efaec
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../networking2.rst:191
+#: ../../networking2.rst:1363
+#: ../../networking2.rst:1573
+# ef46dafa14464c0580eef19b6347e754
+# f88933a8ce404a74b4dbfb012972639e
+# 1a1e2e9b76e842d2ad6653556d716440
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../networking2.rst:195
+#: ../../networking2.rst:1577
+# e6266ec66e47425eaefdebd94b55e3d6
+# 9b6fa85ad73145c2a68b917e13c4dd74
+msgid "On Zones, click View More."
+msgstr ""
+
+#: ../../networking2.rst:199
+#: ../../networking2.rst:1581
+# ae18ac4302694c399605762c754adc89
+# a83fd7a01a4d4702815c49eabf8d6f45
+msgid "Click the zone to which you want to add a guest network."
+msgstr ""
+
+#: ../../networking2.rst:203
+#: ../../networking2.rst:777
+#: ../../networking2.rst:898
+#: ../../networking2.rst:1585
+# 35ace6a71a514813adb835b0e291e59a
+# 92a70044e0a64276aca71c727238658c
+# e7a6054e0cac452abbdf14af1fcf9ab7
+# 1dc7e2ce80f242c792c3eadfdf57d1f8
+msgid "Click the Physical Network tab."
+msgstr ""
+
+#: ../../networking2.rst:207
+#: ../../networking2.rst:1589
+# 7d1c35e3c6fb45268f88743d4f33fc4a
+# 5d24c24102dc463b8df955cea14e8321
+msgid "Click the physical network you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:211
+#: ../../networking2.rst:1593
+# d69f9202aba443119708b15355371054
+# b50eb62ce8e94fdf956d6c49a9d8c539
+msgid "On the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking2.rst:221
+#: ../../networking2.rst:1603
+# 61f94d523e2b4257ac005b54b2300cd1
+# e69e4aa9dc5d4b77b59760f32d4410e5
+msgid "The Add guest network window is displayed."
+msgstr ""
+
+#: ../../networking2.rst:225
+#: ../../networking2.rst:806
+#: ../../networking2.rst:822
+#: ../../networking2.rst:856
+#: ../../networking2.rst:916
+#: ../../networking2.rst:1227
+#: ../../networking2.rst:1400
+#: ../../networking2.rst:1607
+#: ../../networking2.rst:2480
+#: ../../networking2.rst:3177
+#: ../../networking2.rst:5166
+#: ../../networking2.rst:5592
+#: ../../networking2.rst:6347
+#: ../../networking2.rst:6741
+# 4af18c5d61a6456caf73f7a9369e2fee
+# cd3004192b7247d6b3d8df85d071c687
+# cefbbdc700e1418791c24fa0e9ff9991
+# 7d7d79ee61514455a6bd14b72d23c697
+# 9eddccf9e3ed490ba485fed483665910
+# ad7396c2fa194389a72869772975a651
+# ba22f3a686da4d51be0844159353ec45
+# 813ce0c39bee45a6b48988f7b8abcccd
+# 49c644d753054859b04b0040656835a6
+# 6851774e7c7b4a888987619af18e594a
+# 5bb2026725a84546bbf11325cca1e760
+# ca837cbb6534464a8d34b465a79f3b42
+# 1766498324004d1b9d70c399f1671335
+# 3fcb97db48704b65b73bdf48cfc719df
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking2.rst:229
+#: ../../networking2.rst:1611
+# 8779be8d9d6846f085dbce3da3461bc3
+# b0b915aaeb67486684b659dc291d6454
+msgid "**Name**: The name of the network. This will be visible to the user."
+msgstr ""
+
+#: ../../networking2.rst:234
+#: ../../networking2.rst:1616
+# 5074f17c728f4f3a8a7f794e8374c034
+# 0a5db820304048068d1845c134b8df63
+msgid "**Description**: The short description of the network that can be displayed to users."
+msgstr ""
+
+#: ../../networking2.rst:239
+#: ../../networking2.rst:1621
+# 2b82a4bc6aa046f3b00d043934c959d7
+# 41c1edb5305a4945842709a1c5cf1ad6
+msgid "**VLAN ID**: The unique ID of the VLAN."
+msgstr ""
+
+#: ../../networking2.rst:243
+# 418bb2fcab5742fb987163b73807d96b
+msgid "**Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr ""
+
+#: ../../networking2.rst:248
+#: ../../networking2.rst:1633
+# f26b6b49568f43ac84898deb5855609f
+# 969c263588994f74ac62592a499a4b31
+msgid "**Scope**: The available scopes are Domain, Account, Project, and All."
+msgstr ""
+
+#: ../../networking2.rst:253
+#: ../../networking2.rst:1638
+# 178c532fedf44f0fb1a2993bf0f625a0
+# 15faa541a4ce4327913cfce7e0c3f217
+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 ""
+
+#: ../../networking2.rst:261
+#: ../../networking2.rst:1646
+# 91422a2eb500489a88e0a6f4b976e5c8
+# eb7d195938c445079e17b8d4de34c9b0
+msgid "**Account**: The account for which the guest network is being created for. You must specify the domain the account belongs to."
+msgstr ""
+
+#: ../../networking2.rst:267
+#: ../../networking2.rst:1652
+# acbed03163c746f394f0b6065ac5d267
+# b6481103a23442a698dd33a8241fd4a5
+msgid "**Project**: The project for which the guest network is being created for. You must specify the domain the project belongs to."
+msgstr ""
+
+#: ../../networking2.rst:273
+#: ../../networking2.rst:1658
+# 7515546501ea4a229f3d24cb1957114c
+# 14055c49cff34a97af7586b6692b395f
+msgid "**All**: The guest network is available for all the domains, account, projects within the selected zone."
+msgstr ""
+
+#: ../../networking2.rst:278
+#: ../../networking2.rst:1663
+# 9e7d75c438d04916a6c8e41212a5add4
+# d311a00faddf44fb969a7362e8525846
+msgid "**Network Offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network."
+msgstr ""
+
+#: ../../networking2.rst:284
+#: ../../networking2.rst:1669
+# 3b34a00342f74aabb8f06ef47a71928f
+# cec7265b43cc44c985fc19c1aada24ca
+msgid "**Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../networking2.rst:288
+#: ../../networking2.rst:1673
+# e8b1ed0c13f24b28b17097da6a906553
+# e376b4730d514e9cb67f58490f5323da
+msgid "**Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../networking2.rst:292
+#: ../../networking2.rst:1677
+# e95322f93824448f8b5213679edb09a1
+# f9867bf0fe584ea68c8d8697b398a35d
+msgid "**IP Range**: A range of IP addresses that are accessible from the Internet and are assigned to the guest VMs."
+msgstr ""
+
+#: ../../networking2.rst:295
+# e30dfcdbb56b4fdab7ac50d318f8cfee
+msgid "If one NIC is used, these IPs should be in the same CIDR in the case of IPv6."
+msgstr ""
+
+#: ../../networking2.rst:300
+# c999c7758e4644bb960bd36b4934a153
+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 ""
+
+#: ../../networking2.rst:307
+#: ../../networking2.rst:1682
+# 06222d5aca4f4401b3e50b9562eafd93
+# bdec8ee29ad7416da22dd28dfee5836c
+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 ""
+
+#: ../../networking2.rst:313
+#: ../../networking2.rst:1688
+#: ../../networking2.rst:3215
+#: ../../networking2.rst:3256
+#: ../../networking2.rst:4559
+# 6cbf270deb434c49a37109538320e729
+# e3f042ecf42f48179722b1f43ed74365
+# 6a7ddea8dd2248ce9c184a2ecb2a727c
+# 3048777b2bf143b7b0cf2d931ebf1461
+# 007a1927e30b4659b6f5b8dad349a236
+msgid "Click OK to confirm."
+msgstr ""
+
+#: ../../networking2.rst:316
+# 6dae7352ba9441b4ab5afb0eb736de8e
+msgid "Using Multiple Guest Networks"
+msgstr ""
+
+#: ../../networking2.rst:318
+# 2b127f6d5dfd4f3aa7e896c69fa530fc
+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 ""
+
+#: ../../networking2.rst:323
+# 57493d5abb6d42e29119db9cfbd72df0
+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 ""
+
+#: ../../networking2.rst:328
+# df560b1f84f74fa096be5526e9f253c2
+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 ""
+
+#: ../../networking2.rst:334
+# 1b89ed0c211f490d9ab7e3873f785995
+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 ""
+
+#: ../../networking2.rst:342
+# 03479d92c4f3472fbf1c837f78ae38b9
+msgid "Adding an Additional Guest Network"
+msgstr ""
+
+#: ../../networking2.rst:346
+#: ../../networking2.rst:413
+#: ../../networking2.rst:478
+#: ../../networking2.rst:509
+#: ../../networking2.rst:543
+#: ../../networking2.rst:688
+#: ../../networking2.rst:1205
+#: ../../networking2.rst:1258
+#: ../../networking2.rst:1359
+#: ../../networking2.rst:1735
+#: ../../networking2.rst:1815
+#: ../../networking2.rst:2210
+#: ../../networking2.rst:3284
+#: ../../networking2.rst:3327
+#: ../../networking2.rst:3370
+#: ../../networking2.rst:3444
+#: ../../networking2.rst:3548
+#: ../../networking2.rst:3695
+#: ../../networking2.rst:3829
+#: ../../networking2.rst:4184
+#: ../../networking2.rst:4329
+#: ../../networking2.rst:4362
+#: ../../networking2.rst:4459
+#: ../../networking2.rst:4650
+#: ../../networking2.rst:5066
+#: ../../networking2.rst:5131
+#: ../../networking2.rst:5262
+#: ../../networking2.rst:5344
+#: ../../networking2.rst:5513
+#: ../../networking2.rst:5752
+#: ../../networking2.rst:5843
+#: ../../networking2.rst:5931
+#: ../../networking2.rst:6022
+#: ../../networking2.rst:6265
+#: ../../networking2.rst:6575
+#: ../../networking2.rst:6659
+#: ../../networking2.rst:6784
+#: ../../networking2.rst:6823
+# dcc9b20e05d94a90a82df638e638d914
+# bf1857069dbe437da757dd8117d7a8f6
+# b00f09bd670c4e6bb6a9d90b98d3ee27
+# 06d1f9568c404045a154fa7800b17b42
+# 3a1cc0396efd4b8ebd8a6128932f37f3
+# ded02e7a4c5d4431a40e7c763efe892e
+# 2bf9437aec83464ca8aa33fb4d5bc7d2
+# 474cb61b7d6d414bb525496395e11ac0
+# cf958678b40649e395bf748ed3a82341
+# c6386d8cdb7f4830ac34eb0e3d53d353
+# e419b4e20de34ab59ca3fd7119a6a509
+# cb96251ca7834bcfb93698899e36997c
+# c24de51d817f4b8b86aa10d3c56327e6
+# 1970352df0b24327ab0040b0248447d1
+# b69b28bceebf484d9240513871a69e53
+# efd7ff6f49f24baebd8a7054ca0fcb6a
+# 855b8ad33e0942859a9fb87da979bff6
+# b853131f26c84398bd3ab3b28e7c8c10
+# 0415ee973c9e4f138f81c716a5897661
+# a2d18d98840548f1994851b84a11d06b
+# dafb981c4cd44ff284f9609a6d78076f
+# 8b5b3770bbea4a4b91bce618eaa95579
+# 0f348eefc7a140f0bfa10c40ab0de750
+# 20e4bf643dc649a5adf2b96c98aad755
+# 229dd2bf881340558fca0975604b2643
+# 470f52bcfa37419386c12e3c2112f795
+# bbf8e4596d4c4216a94cb7fd144372c1
+# bbeffb28c2c749518103fe11d941e8f3
+# 910d29d282334e13b2f84bdba7e4ae2f
+# d94ff6f14e7643a9832ac593d1c69ffb
+# 534c0a26f9b24f54a399020a1716f7ed
+# e92cc9d2cd1d448e9f9d848b7a0f8851
+# a96d8dddd84c4103b8b7afff0db24cfe
+# e307dc8da8084a23951ba5a0f61c85d4
+# 538a9fc2f7b941d8831cf7952f1eac3f
+# a6c65c894c464e4f928395582357dc97
+# 786b76e0eb6b4cadba166292663da2ea
+# 6530063879054b16a643c0b8d345a236
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking2.rst:350
+#: ../../networking2.rst:553
+#: ../../networking2.rst:692
+#: ../../networking2.rst:1262
+#: ../../networking2.rst:2214
+#: ../../networking2.rst:3288
+#: ../../networking2.rst:3331
+#: ../../networking2.rst:3374
+#: ../../networking2.rst:3448
+#: ../../networking2.rst:3552
+#: ../../networking2.rst:4188
+#: ../../networking2.rst:4333
+#: ../../networking2.rst:4366
+#: ../../networking2.rst:4463
+#: ../../networking2.rst:4654
+#: ../../networking2.rst:5070
+#: ../../networking2.rst:5135
+#: ../../networking2.rst:5266
+#: ../../networking2.rst:5348
+#: ../../networking2.rst:5517
+#: ../../networking2.rst:5756
+#: ../../networking2.rst:5847
+#: ../../networking2.rst:5935
+#: ../../networking2.rst:6026
+#: ../../networking2.rst:6269
+#: ../../networking2.rst:6579
+#: ../../networking2.rst:6663
+#: ../../networking2.rst:6788
+#: ../../networking2.rst:6827
+# c650c895a3ac4ff2851197288859be98
+# 65e8807d38054bd1b0027a7155f8085f
+# 6cbdfa0e6a0e46cdab35e3223f504119
+# 2f9490cb25514f8283f8dec06a79102d
+# 5563fe265c1a429d967cda0edab813f4
+# 54d9e12cb3164286a92aceeba0a664e5
+# 612ff33bd3f84bdd84ef63b9c3cb6cf3
+# 6fc81420daf44701856963aa3d9f4a87
+# 07cefb7f05bc4714bf198cbd879aea33
+# ab72dbc455b843cfb4c72e923297fc4d
+# 2e8cbb1231ef43fb9b387b21b0f97305
+# 9cb098264bbf4fc79077a14d44ff4e4d
+# ceb0f3b90cd2499b89cc614d577384d9
+# f15f55387b954e10a6e5a4417bfa6071
+# c298749dee624dae9ac00c5329f45af3
+# e222d654cbbb4a0a9bfcec6a887925e2
+# aa6ece8cd97543d091148cc4a9db4c04
+# 412366a772fc462991958a94917d88ee
+# e838e4d54a33420fad3f9b5aac4181ea
+# ef4b5d8b2c1f4efcb1dcb0909dd0610b
+# fb954e22b2e247cfbf72c9525d556f10
+# e9064194f98e4db6bb1374bc04afd258
+# da3f29bc5aa344e99d840c524c97ff52
+# 931799f15e4f4ef78f34f77acc6a84a5
+# 0035008431074c10b6f9cdcd88cf746a
+# 7a1970bdf40a45d3acd7f9db64c34c2f
+# f9b9878b284a440380845f18adc4dc02
+# 1108ad1b0aa449c198fc5fbf7b2f6f72
+# cea2011545724bc2b72940d23a00d3d7
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking2.rst:354
+# f6aa7a61ff37420d9f141635bdbce188
+msgid "Click Add guest network. Provide the following information:"
+msgstr ""
+
+#: ../../networking2.rst:358
+# 94e3451e541243a590fc75a1c6838168
+msgid "**Name**: The name of the network. This will be user-visible."
+msgstr ""
+
+#: ../../networking2.rst:362
+# 24a87a4d530b4a8c9af892bd51a53c2b
+msgid "**Display Text**: The description of the network. This will be user-visible."
+msgstr ""
+
+#: ../../networking2.rst:367
+# 4491ce6396264b9f805777eca895a720
+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 ""
+
+#: ../../networking2.rst:374
+# 738c6e4f1dac40f6ae58cfa12e3fafb6
+msgid "**Network offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network."
+msgstr ""
+
+#: ../../networking2.rst:380
+# 4d5b30b8ae754940bd24bf9ce873f62c
+msgid "**Guest Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../networking2.rst:384
+# d2cc46c6e57d4a74b0f41b06645d7905
+msgid "**Guest Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../networking2.rst:389
+#: ../../networking2.rst:4032
+# 0eef322a01b1441c968f5d08a7d1205d
+# 0fd1c8972f504925a86019b475f8cf7a
+msgid "Click Create."
+msgstr ""
+
+#: ../../networking2.rst:392
+# de4eb821eff84801b56973e967b9870e
+msgid "Reconfiguring Networks in VMs"
+msgstr ""
+
+#: ../../networking2.rst:394
+# 0f2fe4ab745e4f7fb65fe812f7d64f1a
+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 ""
+
+#: ../../networking2.rst:400
+# 74ad1316798b4f60a8f0033d2c970d86
+msgid "This feature is supported on XenServer, VMware, and KVM hypervisors."
+msgstr ""
+
+#: ../../networking2.rst:403
+#: ../../networking2.rst:1526
+#: ../../networking2.rst:2416
+# 65c68a2b86274b91a6ec6ed32d0eb511
+# b0f423eb9e1444fa8072955fb8cbe955
+# c9a7dedb4fe74538a84d59bba4b0ea21
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../networking2.rst:405
+# bc2166808aa14a3d84e34f7a073eda9b
+msgid "Ensure that vm-tools are running on guest VMs for adding or removing networks to work on VMware hypervisor."
+msgstr ""
+
+#: ../../networking2.rst:409
+# 5edc5eb13c714fdcb4bc76dfefee938a
+msgid "Adding a Network"
+msgstr ""
+
+#: ../../networking2.rst:417
+#: ../../networking2.rst:482
+#: ../../networking2.rst:513
+# e9c46729b8e44e9b86983fc1d062228c
+# 69e1fa7916874968ad5f68de2af2cbc4
+# 53892275c4d84a16b7aa19e912822afe
+msgid "In the left navigation, click Instances."
+msgstr ""
+
+#: ../../networking2.rst:421
+#: ../../networking2.rst:486
+#: ../../networking2.rst:517
+# 237aa96a8b6047e2abb22526bd4bac7c
+# 2b3f21ea21b24697b7196dc8f6846009
+# 274e34eca30542b289b9dccb8063fa1f
+msgid "Choose the VM that you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:425
+#: ../../networking2.rst:490
+#: ../../networking2.rst:521
+# a616e6054be2484499468033d21dea1c
+# 7df447c421184ebd8362e78e05a81058
+# 57cb30b5f480462abef7c6f73b23f46e
+msgid "Click the NICs tab."
+msgstr ""
+
+#: ../../networking2.rst:429
+# dccdbd5be35b43fda6baf17f2c628af7
+msgid "Click Add network to VM."
+msgstr ""
+
+#: ../../networking2.rst:431
+# 05af00bbbfae48b0869d614090792531
+msgid "The Add network to VM dialog is displayed."
+msgstr ""
+
+#: ../../networking2.rst:435
+# 9d15b4dcf3c8457785334338c368aa26
+msgid "In the drop-down list, select the network that you would like to add this VM to."
+msgstr ""
+
+#: ../../networking2.rst:438
+# 9747107d35eb413e81aa96529adf5506
+msgid "A new NIC is added for this network. You can view the following details in the NICs page:"
+msgstr ""
+
+#: ../../networking2.rst:443
+# 96ffcc74f3da41ee9f7fade2c284e2cc
+msgid "ID"
+msgstr ""
+
+#: ../../networking2.rst:447
+# 0930c07f915e4e8f8321b47ce1b2546c
+msgid "Network Name"
+msgstr ""
+
+#: ../../networking2.rst:451
+# 2166ea3836e64777968d20d97a551782
+msgid "Type"
+msgstr ""
+
+#: ../../networking2.rst:455
+#: ../../networking2.rst:4442
+#: ../../networking2.rst:4567
+# ebba5967ce5b40c6a4b9557338f01ce6
+# 3d4b724e0c8241c1ba31b6395bc04008
+# 5af256fd3dbb4fdd841ef05a4ec9b838
+msgid "IP Address"
+msgstr ""
+
+#: ../../networking2.rst:459
+#: ../../networking2.rst:4571
+# a5e87e2a4b4d4ddd80f323f49ceee587
+# ad200504779f4909905c825a837ecb20
+msgid "Gateway"
+msgstr ""
+
+#: ../../networking2.rst:463
+# b15a081ce5664e48891a6f018aa8f161
+msgid "Netmask"
+msgstr ""
+
+#: ../../networking2.rst:467
+# 297b7172628240e1a2c5b8cabc302f62
+msgid "Is default"
+msgstr ""
+
+#: ../../networking2.rst:471
+# 8a2efed9a7e74c7f9fe0f1d5eb5d090c
+msgid "CIDR (for IPv6)"
+msgstr ""
+
+#: ../../networking2.rst:474
+# 9398952782e64b64b3867a3fe12fd7bc
+msgid "Removing a Network"
+msgstr ""
+
+#: ../../networking2.rst:494
+# a093eadb6ac145cbae36f5faaaa2c9a1
+msgid "Locate the NIC you want to remove."
+msgstr ""
+
+#: ../../networking2.rst:498
+# 5785d874c0944a0caf08db20f4f9e446
+msgid "Click Remove NIC button. |remove-nic.png|"
+msgstr ""
+
+#: ../../networking2.rst:502
+#: ../../networking2.rst:533
+# c2771766c44443d1bb463bd5a0f9ecef
+# ed60114d9fff4ae6871302c0c6b0aed2
+msgid "Click Yes to confirm."
+msgstr ""
+
+#: ../../networking2.rst:505
+# 6b25b8b44f294113afdfb3b97d2eac02
+msgid "Selecting the Default Network"
+msgstr ""
+
+#: ../../networking2.rst:525
+# 86d95a73e3274acc9285a47537212537
+msgid "Locate the NIC you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:529
+# 998ed551fd1a45f4ac897f9f38552afe
+msgid "Click the Set default NIC button. |set-default-nic.png|."
+msgstr ""
+
+#: ../../networking2.rst:536
+# df5fbaabb7364cf599673d6b129dc3a4
+msgid "Changing the Network Offering on a Guest Network"
+msgstr ""
+
+#: ../../networking2.rst:538
+# 7fc2bd82deb7433b8d2b5f310500de46
+msgid "A user or administrator can change the network offering that is associated with an existing guest network."
+msgstr ""
+
+#: ../../networking2.rst:547
+# 9961a724d3c9484ca0b4c1d5978d448c
+msgid "If you are changing from a network offering that uses the CloudStack virtual router to one that uses external devices as network service providers, you must first stop all the VMs on the network."
+msgstr ""
+
+#: ../../networking2.rst:557
+#: ../../networking2.rst:696
+# 449cac531ff847d796c389fb42f64c5c
+# 44aa044295ce4f078b84c89406c09bb3
+msgid "Click the name of the network you want to modify."
+msgstr ""
+
+#: ../../networking2.rst:561
+#: ../../networking2.rst:700
+# 013515a624984a4181813aa619128c01
+# fb4f4c6fee5a4d54a8210453ae8fea0b
+msgid "In the Details tab, click Edit. |edit-icon.png|"
+msgstr ""
+
+#: ../../networking2.rst:565
+# 2af58d6970ae4fa49f1d797131ae88e5
+msgid "In Network Offering, choose the new network offering, then click Apply."
+msgstr ""
+
+#: ../../networking2.rst:568
+# bc3a2c3c3d324782ae47b4da0e17c214
+msgid "A prompt is displayed asking whether you want to keep the existing CIDR. This is to let you know that if you change the network offering, the CIDR will be affected."
+msgstr ""
+
+#: ../../networking2.rst:572
+# 1b6db56bbeec4098851005614591b4f2
+msgid "If you upgrade between virtual router as a provider and an external network device as provider, acknowledge the change of CIDR to continue, so choose Yes."
+msgstr ""
+
+#: ../../networking2.rst:578
+# 146e4502698d4bedb783dec26532e410
+msgid "Wait for the update to complete. Don't try to restart VMs until the network change is complete."
+msgstr ""
+
+#: ../../networking2.rst:583
+# 4ae7ada6f8e841c4bab421568ca6c79c
+msgid "If you stopped any VMs, restart them."
+msgstr ""
+
+#: ../../networking2.rst:586
+# 9725e5abe5b24d5b9b938be30e1e60f9
+msgid "IP Reservation in Isolated Guest Networks"
+msgstr ""
+
+#: ../../networking2.rst:588
+# 2160ad6d081d44638ebbdfb06dbfae1f
+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 ""
+
+#: ../../networking2.rst:596
+# fbba0aa499f74b36b378c6c99ef2ea87
+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 called Reserved IP Range. When IP reservation is configured, the administrator can add additional VMs or physical servers that are not part of CloudStack to the same network and assign them the Reserved IP addresses. CloudStack guest VMs cannot acquire IPs from the Reserved IP Range."
+msgstr ""
+
+#: ../../networking2.rst:610
+# 90bf1a7d2c754ac4902085a1fd1ba748
+msgid "IP Reservation Considerations"
+msgstr ""
+
+#: ../../networking2.rst:612
+# bc5248dcc785447289018e7cdfcbae8a
+msgid "Consider the following before you reserve an IP range for non-CloudStack machines:"
+msgstr ""
+
+#: ../../networking2.rst:617
+# 7c3b4a1806bc46caaec696068e353f33
+msgid "IP Reservation is supported only in Isolated networks."
+msgstr ""
+
+#: ../../networking2.rst:621
+# a58ea815910f4eeebf5310fba2f2b4e6
+msgid "IP Reservation can be applied only when the network is in Implemented state."
+msgstr ""
+
+#: ../../networking2.rst:626
+# b1e7853953d34392be43f635d609444e
+msgid "No IP Reservation is done by default."
+msgstr ""
+
+#: ../../networking2.rst:630
+# c5d1c53bfa0a4acb8b354fa73f021b37
+msgid "Guest VM CIDR you specify must be a subset of the network CIDR."
+msgstr ""
+
+#: ../../networking2.rst:634
+# 71e39d8747064bfa95ff48adddf42e34
+msgid "Specify a valid Guest VM CIDR. IP Reservation is applied only if no active IPs exist outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking2.rst:637
+# 7cd262eb2864435f953ba2f8d9b2e0a0
+msgid "You cannot apply IP Reservation if any VM is alloted with an IP address that is outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking2.rst:642
+# e135731ad79443bcb5dd396201d24cf1
+msgid "To reset an existing IP Reservation, apply IP reservation by specifying the value of network CIDR in the CIDR field."
+msgstr ""
+
+#: ../../networking2.rst:645
+# 3019eee8f787404483287650255b0fe0
+msgid "For example, the following table describes three scenarios of guest network creation:"
+msgstr ""
+
+#: ../../networking2.rst:649
+# 80174dfa477741e8a428588c2de692c5
+msgid "Case"
+msgstr ""
+
+#: ../../networking2.rst:649
+#: ../../networking2.rst:3931
+#: ../../networking2.rst:4403
+#: ../../networking2.rst:4503
+#: ../../networking2.rst:4695
+#: ../../networking2.rst:5251
+#: ../../networking2.rst:5299
+#: ../../networking2.rst:5558
+#: ../../networking2.rst:5884
+#: ../../networking2.rst:5971
+#: ../../networking2.rst:6063
+#: ../../networking2.rst:6306
+#: ../../networking2.rst:6700
+# eef86be3eee44a648412010005fb2333
+# 5f16a478e68c498db89c7157f7a1baf2
+# 60559aa9aec74533a0723a299680c8a8
+# fe93ec4b20274d52a8708a5cf4922fbd
+# a51541e1ff974e5b9cec68fc9bcf7ea7
+# d31c3f23647842caa0554fd1db873ce4
+# 94126de200d245e5a36add083af0c115
+# d3690595a81542b3a1a8daec4b800f9c
+# 7cb858db9ac346838a97c8e7ed8dcd87
+# e2cbdab6f6d04ca3a9579faffa22f221
+# d1254ad4a86545a8ac507083e4787780
+# 7abcfe51770247ca88d17c97fb261b52
+# ab3f6c13fcea4cdf8df4054fc6c55960
+msgid "CIDR"
+msgstr ""
+
+#: ../../networking2.rst:649
+# 7190e9a05c824c698c369f059903140f
+msgid "Network CIDR"
+msgstr ""
+
+#: ../../networking2.rst:649
+# 7b3e79ea891f42948ec144865f44db13
+msgid "Reserved IP Range for Non-CloudStack VMs"
+msgstr ""
+
+#: ../../networking2.rst:649
+# 4c1abc1728ab4017a78ab13faa073d32
+msgid "Description"
+msgstr ""
+
+#: ../../networking2.rst:651
+#: ../../networking2.rst:5253
+# 95c1f9dcea57490f9baba27f6052d7df
+# c7dc34629f4a4f3380ad7fa0415823fe
+msgid "1"
+msgstr ""
+
+#: ../../networking2.rst:651
+#: ../../networking2.rst:652
+#: ../../networking2.rst:655
+# ca251edef20a4a09a96d4439f40e9fcc
+# 47ec19dde3c14d2daf3a5f567a8ab892
+# 96ce4f76ef034c6c8ad91aa5358390ea
+msgid "10.1.1.0/24"
+msgstr ""
+
+#: ../../networking2.rst:651
+#: ../../networking2.rst:651
+#: ../../networking2.rst:655
+#: ../../networking2.rst:655
+# 9553954ea80b4c108951c22f66b1f907
+# 9d8d02ccc8624c42ab63f95c1e6e61d2
+# 1711e6d7b17c49c1bbacdfe2f237bc1c
+# 3fe4ae27728949db852e351bdc3590a0
+msgid "None"
+msgstr ""
+
+#: ../../networking2.rst:651
+# 4cefe96c4cd048d6ab5bba6b2b2b2c1f
+msgid "No IP Reservation."
+msgstr ""
+
+#: ../../networking2.rst:652
+#: ../../networking2.rst:5254
+# 9743a326091e467d9b6bca3cd0e35000
+# 326ceea3093e4ad2bc955dd15a12fcaa
+msgid "2"
+msgstr ""
+
+#: ../../networking2.rst:652
+# 28839e89c7b84228a801613e0c9ed896
+msgid "10.1.1.0/26"
+msgstr ""
+
+#: ../../networking2.rst:652
+# fb5379ee12174589ad3d2da83e61667c
+msgid "10.1.1.64 to 10.1.1.254"
+msgstr ""
+
+#: ../../networking2.rst:652
+# a9558f6e733545849f81f3ae6fc11f08
+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 ""
+
+#: ../../networking2.rst:655
+# b3beece5bd0f4a3d8a0234aa9980a330
+msgid "3"
+msgstr ""
+
+#: ../../networking2.rst:655
+# 79c55aa2874f4650b96805d27acfee4e
+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 ""
+
+#: ../../networking2.rst:661
+#: ../../networking2.rst:1774
+# 69a8f32537914ac6a722239a9dc07582
+# d8ca4fc7bf014daa9437cc4d5c7eb4f6
+msgid "Limitations"
+msgstr ""
+
+#: ../../networking2.rst:665
+# 6d66399f47684bc1940beb29a805e60c
+msgid "The IP Reservation is not supported if active IPs that are found outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking2.rst:670
+# db05ec3e0280485b9f6f8c5d902cbcc7
+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 ""
+
+#: ../../networking2.rst:676
+# 6edc84466bc24a3d85247cab80c0cd80
+msgid "Best Practices"
+msgstr ""
+
+#: ../../networking2.rst:678
+# 4bd0b852d6474b84accb421f128331f4
+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 ""
+
+#: ../../networking2.rst:684
+# e601241fba8a43feb30b4dcde1dc89a6
+msgid "Reserving an IP Range"
+msgstr ""
+
+#: ../../networking2.rst:702
+# dd9d0df809aa420899439632c2e7019f
+msgid "The CIDR field changes to editable one."
+msgstr ""
+
+#: ../../networking2.rst:706
+# 0ffc29b024624ccdb36d0ea407209d7f
+msgid "In CIDR, specify the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking2.rst:710
+# b2b4f195c2e847418d352a7e1ef06061
+msgid "Click Apply."
+msgstr ""
+
+#: ../../networking2.rst:712
+# d33d489b7f234940bc59878574087127
+msgid "Wait for the update to complete. The Network CIDR and the Reserved IP Range are displayed on the Details page."
+msgstr ""
+
+#: ../../networking2.rst:716
+# 06aed4f105fd47d283331f291310c288
+msgid "Reserving Public IP Addresses and VLANs for Accounts"
+msgstr ""
+
+#: ../../networking2.rst:718
+# d29491316baf475184dbf3bd53bb19c3
+msgid "CloudStack provides you the ability to reserve a set of public IP addresses and VLANs exclusively for an account. During zone creation, you can continue defining a set of VLANs and multiple public IP ranges. This feature extends the functionality to enable you to dedicate a fixed set of VLANs and guest IP addresses for a tenant."
+msgstr ""
+
+#: ../../networking2.rst:724
+# 68a3748797434d67bcbfc405a263a065
+msgid "Note that if an account has consumed all the VLANs and IPs dedicated to it, the account can acquire two more resources from the system. CloudStack provides the root admin with two configuration parameter to modify this default behavior: use.system.public.ips and use.system.guest.vlans. These global parameters enable the root admin to disallow an account from acquiring public IPs and guest VLANs from the system, if the account has dedicated resources and these dedicated resources have all been consumed. Both these configurations are configurable at the account level."
+msgstr ""
+
+#: ../../networking2.rst:734
+# 40f4120539264e8fb5dbf5a7064d1fe9
+msgid "This feature provides you the following capabilities:"
+msgstr ""
+
+#: ../../networking2.rst:738
+# 9bf2889fc36847ebabce3e8f9b625163
+msgid "Reserve a VLAN range and public IP address range from an Advanced zone and assign it to an account"
+msgstr ""
+
+#: ../../networking2.rst:743
+# e1e3b63901214e39b4cd5ded0ff47ab6
+msgid "Disassociate a VLAN and public IP address range from an account"
+msgstr ""
+
+#: ../../networking2.rst:747
+# a849c48967014ee4ab4c29e6250ac9bc
+msgid "View the number of public IP addresses allocated to an account"
+msgstr ""
+
+#: ../../networking2.rst:751
+# 4c148c9f929f4394861c0230a52f46ea
+msgid "Check whether the required range is available and is conforms to account limits."
+msgstr ""
+
+#: ../../networking2.rst:754
+# b03cc0c4939e4538b33463b1acfa081f
+msgid "The maximum IPs per account limit cannot be superseded."
+msgstr ""
+
+#: ../../networking2.rst:757
+# 331f9e80ff07451f833ea2f1e6592f48
+msgid "Dedicating IP Address Ranges to an Account"
+msgstr ""
+
+#: ../../networking2.rst:765
+#: ../../networking2.rst:886
+#: ../../networking2.rst:3054
+# cc9f01ca9cd04090b9ef074c6c68eb34
+# af5838600fdc41f68b104a44ea03d81a
+# 6230bfd5086842d69df7366e01ad5977
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../networking2.rst:769
+#: ../../networking2.rst:890
+# 732571fdd87e45b2ba3d0c99d319dada
+# 0a044cf03cd04706a971cfd6747f3972
+msgid "In Zones, click View All."
+msgstr ""
+
+#: ../../networking2.rst:773
+#: ../../networking2.rst:894
+#: ../../networking2.rst:3062
+# 718b87bdd1b24472a05561bc487af593
+# f0113ce9f8584511a94348c59e5098e9
+# 11d188714878411189998fcd7fb05a07
+msgid "Choose the zone you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:781
+# e2c9d117a33a4ca698597ea697c642a8
+msgid "In the Public node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking2.rst:785
+# b587547f92d54da6a66fb328a1f90aa1
+msgid "Click the IP Ranges tab."
+msgstr ""
+
+#: ../../networking2.rst:787
+# 71762e4009804e12af198d32409f6abe
+msgid "You can either assign an existing IP range to an account, or create a new IP range and assign to an account."
+msgstr ""
+
+#: ../../networking2.rst:792
+# 89865009ad614a7caefc9d7e195d1f2c
+msgid "To assign an existing IP range to an account, perform the following:"
+msgstr ""
+
+#: ../../networking2.rst:796
+# 023883e725b743e790c6c7d378fae5d1
+msgid "Locate the IP range you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:800
+# 727f9c60c5a149af95962b79fb673136
+msgid "Click Add Account |addAccount-icon.png| button."
+msgstr ""
+
+#: ../../networking2.rst:802
+# 98609249ea444461a727d851b23bdb4a
+msgid "The Add Account dialog is displayed."
+msgstr ""
+
+#: ../../networking2.rst:810
+# 91a874f4d53548b5a54dd26c7a8070c4
+msgid "**Account**: The account to which you want to assign the IP address range."
+msgstr ""
+
+#: ../../networking2.rst:815
+# d765ebdf04b540e9bb49f050bc9d5d1c
+msgid "**Domain**: The domain associated with the account."
+msgstr ""
+
+#: ../../networking2.rst:817
+# 68e22a0328b543599b5c092cb1be55c8
+msgid "To create a new IP range and assign an account, perform the following:"
+msgstr ""
+
+#: ../../networking2.rst:826
+# a7351c3fc8aa4e6ab6f6de9982df895a
+msgid "**Gateway**"
+msgstr ""
+
+#: ../../networking2.rst:830
+# a8212080596548efb06b7f360af77801
+msgid "**Netmask**"
+msgstr ""
+
+#: ../../networking2.rst:834
+# 2bac81ea68b044c99364b2e06d943f9e
+msgid "**VLAN**"
+msgstr ""
+
+#: ../../networking2.rst:838
+# a4fe8a556467404db7fc7ce462d9d690
+msgid "**Start IP**"
+msgstr ""
+
+#: ../../networking2.rst:842
+# b86850aa7e104d75b25613535bda6ad1
+msgid "**End IP**"
+msgstr ""
+
+#: ../../networking2.rst:846
+# 0cb6e7bb5c24462ca8eba42cba3c2ba0
+msgid "**Account**: Perform the following:"
+msgstr ""
+
+#: ../../networking2.rst:850
+# ba26e0ab36b64d9a9e00350c439eb9ec
+msgid "Click Account."
+msgstr ""
+
+#: ../../networking2.rst:852
+# 7ef94c9e8e0b407d82dc09a915d88b3e
+msgid "The Add Account page is displayed."
+msgstr ""
+
+#: ../../networking2.rst:860
+# 2e18417b732143f89ffa9ab5c5767d1d
+msgid "****Account****: The account to which you want to assign an IP address range."
+msgstr ""
+
+#: ../../networking2.rst:865
+#: ../../networking2.rst:930
+# 24326080425a4f7ba299c24defa8ee63
+# 3360555202854da8a230941d49441cb7
+msgid "****Domain****: The domain associated with the account."
+msgstr ""
+
+#: ../../networking2.rst:874
+#: ../../networking2.rst:1935
+#: ../../networking2.rst:3493
+#: ../../networking2.rst:3595
+#: ../../networking2.rst:3751
+#: ../../networking2.rst:3984
+#: ../../networking2.rst:5732
+# 57dd5ad50af947868ed60fb4f4871b8e
+# fd71c947508a4b19a74d5e8e68ab028a
+# df1c4b86b0574044b3b1e2f59f86e433
+# 911725135046474fbb858f58a060c70c
+# 7f4d32193a8e441ba5d3ba76afdc660d
+# 0d1a59ac450f4913861519bb5690af46
+# 68ec8457b8f6477a877539749238ecd7
+msgid "Click Add."
+msgstr ""
+
+#: ../../networking2.rst:877
+# 6ef67854e5d346c7913e58e20a2b72f4
+msgid "Dedicating VLAN Ranges to an Account"
+msgstr ""
+
+#: ../../networking2.rst:881
+# 37745b0f98834f4b805af70b9546e2d7
+msgid "After the CloudStack Management Server is installed, log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../networking2.rst:902
+#: ../../networking2.rst:1376
+# f8bb5c0c781349a6ad62cac445eb11cc
+# eab05b15433e427aa1bb42cc204ab3e9
+msgid "In the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking2.rst:906
+# 61505cd3d4344e769a534aed469c073d
+msgid "Select the Dedicated VLAN Ranges tab."
+msgstr ""
+
+#: ../../networking2.rst:910
+# 1df8c107f4854732a4f8a3a50c9cec49
+msgid "Click Dedicate VLAN Range."
+msgstr ""
+
+#: ../../networking2.rst:912
+# c02ef1fcb0e642a28e69bd463286ec33
+msgid "The Dedicate VLAN Range dialog is displayed."
+msgstr ""
+
+#: ../../networking2.rst:920
+# acd323fd8ca8468880666db446b5d222
+msgid "****VLAN Range****: The VLAN range that you want to assign to an account."
+msgstr ""
+
+#: ../../networking2.rst:925
+# 1a79b0742f1a4aefa692f541aa4b5892
+msgid "****Account****: The account to which you want to assign the selected VLAN range."
+msgstr ""
+
+#: ../../networking2.rst:933
+# fe1be017fe7644368cd98ae4c68575eb
+msgid "Configuring Multiple IP Addresses on a Single NIC"
+msgstr ""
+
+#: ../../networking2.rst:935
+# c38d77c3c3a04ece8ca7568348264c1c
+msgid "CloudStack provides you the ability to associate multiple private IP addresses per guest VM NIC. In addition to the primary IP, you can assign additional IPs to the guest VM NIC. This feature is supported on all the network configurations: Basic, Advanced, and VPC. Security Groups, Static NAT and Port forwarding services are supported on these additional IPs."
+msgstr ""
+
+#: ../../networking2.rst:942
+# f6ae31a4bdbf477bb30c85f877c5c6b6
+msgid "As always, you can specify an IP from the guest subnet; if not specified, an IP is automatically picked up from the guest VM subnet. You can view the IPs associated with for each guest VM NICs on the UI. You can apply NAT on these additional guest IPs by using network configuration option in the CloudStack UI. You must specify the NIC to which the IP should be associated."
+msgstr ""
+
+#: ../../networking2.rst:949
+# e122667851cc41cbb7ee1643ac94d437
+msgid "This feature is supported on XenServer, KVM, and VMware hypervisors. Note that Basic zone security groups are not supported on VMware."
+msgstr ""
+
+#: ../../networking2.rst:953
+# d244bec96a6742dcba6445489ebe5218
+msgid "Use Cases"
+msgstr ""
+
+#: ../../networking2.rst:955
+# 6bb7477d1acc4f3fbd79cd0dbfc2ca5e
+msgid "Some of the use cases are described below:"
+msgstr ""
+
+#: ../../networking2.rst:959
+# deaccf09c30b469a945f6c92f5b3e9e8
+msgid "Network devices, such as firewalls and load balancers, generally work best when they have access to multiple IP addresses on the network interface."
+msgstr ""
+
+#: ../../networking2.rst:965
+# b3bb1a633fb0431687fc030d4f1135d3
+msgid "Moving private IP addresses between interfaces or instances. Applications that are bound to specific IP addresses can be moved between instances."
+msgstr ""
+
+#: ../../networking2.rst:971
+# 5d372ef180164330a3adddfbf3c1cc0f
+msgid "Hosting multiple SSL Websites on a single instance. You can install multiple SSL certificates on a single instance, each associated with a distinct IP address."
+msgstr ""
+
+#: ../../networking2.rst:976
+#: ../../networking2.rst:1194
+#: ../../networking2.rst:6425
+# 37f9e5af46a34673a930879c2e5cba6f
+# c7db437925a34c6a87c825ef10de2e9a
+# 3f3eba9611d84d6aae271d271019803b
+msgid "Guidelines"
+msgstr ""
+
+#: ../../networking2.rst:978
+# 3e292b09263b4b97bfd6c423204dbc2f
+msgid "To prevent IP conflict, configure different subnets when multiple networks are connected to the same VM."
+msgstr ""
+
+#: ../../networking2.rst:982
+# 95785c3d19f449f78cc05d757ee25d24
+msgid "Assigning Additional IPs to a VM"
+msgstr ""
+
+#: ../../networking2.rst:986
+# 59a152d36896406a8e27bc6d934ee420
+msgid "Log in to the CloudStack UI."
+msgstr ""
+
+#: ../../networking2.rst:990
+# 62ef4fc700f2458282be770129fbe8f3
+msgid "In the left navigation bar, click Instances."
+msgstr ""
+
+#: ../../networking2.rst:994
+# e481a0bf01464ec993e94b0b35787eed
+msgid "Click the name of the instance you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:998
+# 040e0aa0901c4a738201d7f2b345c0f1
+msgid "In the Details tab, click NICs."
+msgstr ""
+
+#: ../../networking2.rst:1002
+# 783db8f186394495ad0ab1546a97951e
+msgid "Click View Secondary IPs."
+msgstr ""
+
+#: ../../networking2.rst:1006
+# 81df8a9f3f814aaa861dd841284985ef
+msgid "Click Acquire New Secondary IP, and click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../networking2.rst:1009
+# 5bee3ae73622433aaf3ff3502d16bfcb
+msgid "You need to configure the IP on the guest VM NIC manually. CloudStack will not automatically configure the acquired IP address on the VM. Ensure that the IP address configuration persist on VM reboot."
+msgstr ""
+
+#: ../../networking2.rst:1013
+# f5aed3f52f76443b9810ed9d0bd1d47c
+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 StaticNAT rules."
+msgstr ""
+
+#: ../../networking2.rst:1018
+# 91390ddfe5794441a909d512aaf69b16
+msgid "Port Forwarding and StaticNAT Services Changes"
+msgstr ""
+
+#: ../../networking2.rst:1020
+# 178e8a8fb2244a73af81938965720ec0
+msgid "Because multiple IPs can be associated per NIC, you are allowed to select a desired IP for the Port Forwarding and StaticNAT services. The default is the primary IP. To enable this functionality, an extra optional parameter 'vmguestip' is added to the Port forwarding and StaticNAT APIs (enableStaticNat, createIpForwardingRule) to indicate on what IP address NAT need to be configured. If vmguestip is passed, NAT is configured on the specified private IP of the VM. if not passed, NAT is configured on the primary IP of the VM."
+msgstr ""
+
+#: ../../networking2.rst:1030
+# 9a799b4a628a476f9d231bc81b470264
+msgid "About Multiple IP Ranges"
+msgstr ""
+
+#: ../../networking2.rst:1032
+# 028ff8cab15f440e877ecf3ac468a1a2
+msgid "The feature can only be implemented on IPv4 addresses."
+msgstr ""
+
+#: ../../networking2.rst:1034
+# e4d2239d0d0c410c8f96922f8da73fd8
+msgid "CloudStack provides you with the flexibility to add guest IP ranges from different subnets in Basic zones and security groups-enabled Advanced zones. For security groups-enabled Advanced zones, it implies multiple subnets can be added to the same VLAN. With the addition of this feature, you will be able to add IP address ranges from the same subnet or from a different one when IP address are exhausted. This would in turn allows you to employ higher number of subnets and thus reduce the address management overhead. To support this feature, the capability of ``createVlanIpRange`` API is extended to add IP ranges also from a different subnet."
+msgstr ""
+
+#: ../../networking2.rst:1045
+# 2881a530808e42f5be3d6298eeb47271
+msgid "Ensure that you manually configure the gateway of the new subnet before adding the IP range. Note that CloudStack supports only one gateway for a subnet; overlapping subnets are not currently supported."
+msgstr ""
+
+#: ../../networking2.rst:1049
+# 003e5d07c0794227bc714b0f29892867
+msgid "Use the ``deleteVlanRange`` API to delete IP ranges. This operation fails if an IP from the remove range is in use. If the remove range contains the IP address on which the DHCP server is running, CloudStack acquires a new IP from the same subnet. If no IP is available in the subnet, the remove operation fails."
+msgstr ""
+
+#: ../../networking2.rst:1055
+# b8a91ec2e02844bd85db4f28846aad2b
+msgid "This feature is supported on KVM, xenServer, and VMware hypervisors."
+msgstr ""
+
+#: ../../networking2.rst:1058
+# ed378b716b614e5ea18ea508d7ecccb8
+msgid "About Elastic IP"
+msgstr ""
+
+#: ../../networking2.rst:1060
+# cb979912025d4652b170b423b3323451
+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 is down, the IP address can be reassigned to a new VM in your account."
+msgstr ""
+
+#: ../../networking2.rst:1069
+# a05811529f014d1aa52b2974f0bba51e
+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 ""
+
+#: ../../networking2.rst:1077
+# d254f6b5f23f4583bf38593e35204bd5
+msgid "|eip-ns-basiczone.png|"
+msgstr ""
+
+#: ../../networking2.rst:1079
+# ec87f8235ad14731b88fa165faf2855f
+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 data center goes through the firewall."
+msgstr ""
+
+#: ../../networking2.rst:1088
+# cccbede2f664419a97a65174be17cfba
+msgid "The EIP work flow is as follows:"
+msgstr ""
+
+#: ../../networking2.rst:1092
+# 748bdba8746d4237862652eeefe51b0c
+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 ""
+
+#: ../../networking2.rst:1098
+# b453f18754a649e5913c58ce4a28993b
+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 ""
+
+#: ../../networking2.rst:1104
+# 6e1a151b2c704623941c8c05d3a90134
+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 ""
+
+#: ../../networking2.rst:1113
+# e64823a0214b46d8a6326da740b47131
+msgid "This default public IP will be released in two cases:"
+msgstr ""
+
+#: ../../networking2.rst:1117
+# ec3de61219d640b2baa722270d509f9b
+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 ""
+
+#: ../../networking2.rst:1123
+# 9429fa004e17414e88ed8a023486ac59
+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 ""
+
+#: ../../networking2.rst:1131
+# 469830a9248b4593a5aac71adbba4340
+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 and enable static NAT."
+msgstr ""
+
+#: ../../networking2.rst:1140
+# 0ecd0ac61194408a98281da0aadd9e1a
+msgid "For more information on the Associate Public IP option, see `\"Creating a New Network Offering\" <networking.html#creating-a-new-network-offering>`_."
+msgstr ""
+
+#: ../../networking2.rst:1144
+# 3cd8dd1307094741b10ebb57dc03d260
+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 ""
+
+#: ../../networking2.rst:1148
+# 3ff9c04d9cd44e088c20dfd89e9b3b8b
+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 ""
+
+#: ../../networking2.rst:1153
+# 16c8dc460b214f4894425176314b9cb3
+msgid "Portable IPs"
+msgstr ""
+
+#: ../../networking2.rst:1156
+# 3a5bf095b28f463397be53d043c810c8
+msgid "About Portable IP"
+msgstr ""
+
+#: ../../networking2.rst:1158
+# 5458a5ed86214e4c93481bcc51808719
+msgid "Portable IPs in CloudStack are region-level pool of IPs, which are elastic in nature, that can be transferred across geographically separated zones. As an administrator, you can provision a pool of portable public IPs at region level and are available for user consumption. The users can acquire portable IPs if admin has provisioned portable IPs at the region level they are part of. These IPs can be use for any service within an advanced zone. You can also use portable IPs for EIP services in basic zones."
+msgstr ""
+
+#: ../../networking2.rst:1167
+# 7315df7ef52e4cf1b934b6af1441d884
+msgid "The salient features of Portable IP are as follows:"
+msgstr ""
+
+#: ../../networking2.rst:1171
+# 891115e5cf6a48ada1f4095573352338
+msgid "IP is statically allocated"
+msgstr ""
+
+#: ../../networking2.rst:1175
+# 4d10cf62b6c743b8b592cc802be6cc92
+msgid "IP need not be associated with a network"
+msgstr ""
+
+#: ../../networking2.rst:1179
+# 24d3e403f0aa4c39ad463d1fa0ae207d
+msgid "IP association is transferable across networks"
+msgstr ""
+
+#: ../../networking2.rst:1183
+# 74cb916a3d374a76b971841f8b2379a5
+msgid "IP is transferable across both Basic and Advanced zones"
+msgstr ""
+
+#: ../../networking2.rst:1187
+# 7d33ab9a52444bbe9b3f7b3128209e6b
+msgid "IP is transferable across VPC, non-VPC isolated and shared networks"
+msgstr ""
+
+#: ../../networking2.rst:1191
+# df1a612ddd7d4098a0ddf9b83ad8a93e
+msgid "Portable IP transfer is available only for static NAT."
+msgstr ""
+
+#: ../../networking2.rst:1196
+# bb4f9954dc894d61abfa568fb2e16957
+msgid "Before transferring to another network, ensure that no network rules (Firewall, Static NAT, Port Forwarding, and so on) exist on that portable IP."
+msgstr ""
+
+#: ../../networking2.rst:1201
+# 6219f205752d4e34a5f1fbf3a5de51cc
+msgid "Configuring Portable IPs"
+msgstr ""
+
+#: ../../networking2.rst:1209
+# d64282ef04d447a599ddece7139055f7
+msgid "In the left navigation, click Regions."
+msgstr ""
+
+#: ../../networking2.rst:1213
+# 8b31c7af9d8541d79d6b98d0ed76d82d
+msgid "Choose the Regions that you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:1217
+# 1938f07ea2c94222a20b08898972dc0c
+msgid "Click View Portable IP."
+msgstr ""
+
+#: ../../networking2.rst:1221
+# 3fd59fc0c5804ab58ed115888d070d9d
+msgid "Click Portable IP Range."
+msgstr ""
+
+#: ../../networking2.rst:1223
+# 289d79706e0d4aac949867e57202c169
+msgid "The Add Portable IP Range window is displayed."
+msgstr ""
+
+#: ../../networking2.rst:1231
+# 6ba39db9be5d430986ffe15997a7b655
+msgid "**Start IP/ End IP**: A range of IP addresses that are accessible from the Internet and will be allocated to guest VMs. Enter the first and last IP addresses that define a range that CloudStack can assign to guest VMs."
+msgstr ""
+
+#: ../../networking2.rst:1238
+# a79eef6844454a7e8d9fe27202723b53
+msgid "**Gateway**: The gateway in use for the Portable IP addresses you are configuring."
+msgstr ""
+
+#: ../../networking2.rst:1243
+# ade2b585b1ff4b51b25c1f72d1f5a03e
+msgid "**Netmask**: The netmask associated with the Portable IP range."
+msgstr ""
+
+#: ../../networking2.rst:1247
+# 2cce53fcfa9e4ebdb7cec25d4dd3f797
+msgid "**VLAN**: The VLAN that will be used for public traffic."
+msgstr ""
+
+#: ../../networking2.rst:1254
+# 5c4576cb4d01410ea44f66b3560eec1c
+msgid "Acquiring a Portable IP"
+msgstr ""
+
+#: ../../networking2.rst:1266
+#: ../../networking2.rst:3292
+#: ../../networking2.rst:3335
+#: ../../networking2.rst:3378
+#: ../../networking2.rst:3452
+# fd1b3a3c5e574a7ebb4e782d04f0746b
+# 3ec5393b7aa8486ca2b52df1597e7a98
+# b4889435dd5a4b8986acad62a13ddd6a
+# bfc4acd9c38f49138744c5671d7deb8b
+# 9eae88f558024bafa1c71d5b5f8f6d94
+msgid "Click the name of the network where you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:1270
+#: ../../networking2.rst:2223
+#: ../../networking2.rst:3296
+#: ../../networking2.rst:3339
+#: ../../networking2.rst:3382
+#: ../../networking2.rst:3456
+#: ../../networking2.rst:3870
+# e986c959252444b99b7c5594762994fb
+# 2809642deff2421db1593ab57615dc68
+# d64bfe77233d4d59b07129a931a574b3
+# 15c8b96721f3464380599d2d5d2f02bc
+# 9751f6d58300447198381c3549bd481e
+# f8c3a0b896d14361b59692083c989410
+# 4bccc75dc7d0449097629003483b3545
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking2.rst:1274
+#: ../../networking2.rst:3300
+# 667a207d51d24ec19784a9167e8565b8
+# 5605f1edaf4a463a84ae99cdd32825a4
+msgid "Click Acquire New IP."
+msgstr ""
+
+#: ../../networking2.rst:1276
+#: ../../networking2.rst:3302
+# 6f484ad19a9e4e70b96bf198ddbcf3f4
+# ac45a6f42e5e42a29e4eb09f827d12a3
+msgid "The Acquire New IP window is displayed."
+msgstr ""
+
+#: ../../networking2.rst:1280
+#: ../../networking2.rst:3306
+# a62089adc7304fe1a0c39b6e337ddca2
+# 9baf10608a674ae292c3dea0a0859da7
+msgid "Specify whether you want cross-zone IP or not."
+msgstr ""
+
+#: ../../networking2.rst:1284
+# 3bb7d4dc99f341248a9c5c892bc12485
+msgid "Click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../networking2.rst:1286
+#: ../../networking2.rst:3314
+# 38c1b6967ebb4ec9852ba01c1f005f98
+# 197a1c50649d486ca45fb94f4900aa2d
+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 ""
+
+#: ../../networking2.rst:1291
+# 524a4bfc4e03495584030002db87273b
+msgid "Transferring Portable IP"
+msgstr ""
+
+#: ../../networking2.rst:1293
+# 68465770f0cb4381ac7ce0eb0b65ecbc
+msgid "An IP can be transferred from one network to another only if Static NAT is enabled. However, when a portable IP is associated with a network, you can use it for any service in the network."
+msgstr ""
+
+#: ../../networking2.rst:1297
+# b51d59c49aad4d2c82dc7ff551a1e515
+msgid "To transfer a portable IP across the networks, execute the following API:"
+msgstr ""
+
+#: ../../networking2.rst:1304
+# baaa47d9664443df8004dbd797ca37f0
+msgid "Replace the UUID with appropriate UUID. For example, if you want to transfer a portable IP to network X and VM Y in a network, execute the following:"
+msgstr ""
+
+#: ../../networking2.rst:1313
+# 2ab16bedc435498fa54a92c12d41873b
+msgid "Multiple Subnets in Shared Network"
+msgstr ""
+
+#: ../../networking2.rst:1315
+# 052e7dd83a5d49f6830d255583296f7d
+msgid "CloudStack provides you with the flexibility to add guest IP ranges from different subnets in Basic zones and security groups-enabled Advanced zones. For security groups-enabled Advanced zones, it implies multiple subnets can be added to the same VLAN. With the addition of this feature, you will be able to add IP address ranges from the same subnet or from a different one when IP address are exhausted. This would in turn allows you to employ higher number of subnets and thus reduce the address management overhead. You can delete the IP ranges you have added."
+msgstr ""
+
+#: ../../networking2.rst:1326
+#: ../../networking2.rst:2963
+#: ../../networking2.rst:3510
+# 39d6185c2a9142778ebfcfaa45d53ea4
+# a87fd7c6cc4d4983be85e89d3f15de49
+# dff9442af85b489c8e6c974a633e5646
+msgid "Prerequisites and Guidelines"
+msgstr ""
+
+#: ../../networking2.rst:1330
+# b12da91685134a71866c8fa74aeaa4de
+msgid "This feature can only be implemented:"
+msgstr ""
+
+#: ../../networking2.rst:1334
+# 1393ad33a993459f81ea3de1149b6a09
+msgid "on IPv4 addresses"
+msgstr ""
+
+#: ../../networking2.rst:1338
+# 4764589edb39403a9fd8558614490a61
+msgid "if virtual router is the DHCP provider"
+msgstr ""
+
+#: ../../networking2.rst:1342
+# b1541de5c3f0486faa35809ad77b0359
+msgid "on KVM, xenServer, and VMware hypervisors"
+msgstr ""
+
+#: ../../networking2.rst:1346
+# 2422d92308cd49628de0caa0efcad9c7
+msgid "Manually configure the gateway of the new subnet before adding the IP range."
+msgstr ""
+
+#: ../../networking2.rst:1351
+# bf5e159cb4c54583a861e417824b26a3
+msgid "CloudStack supports only one gateway for a subnet; overlapping subnets are not currently supported"
+msgstr ""
+
+#: ../../networking2.rst:1355
+# 7e64cd24270240e9bef22bc1491bf837
+msgid "Adding Multiple Subnets to a Shared Network"
+msgstr ""
+
+#: ../../networking2.rst:1367
+# 1f05243395c24667a0f7e9c75bbc190f
+msgid "On Zones, click View More, then click the zone to which you want to work with.."
+msgstr ""
+
+#: ../../networking2.rst:1372
+# 2b58f0a641ae4d80a61839330e31435b
+msgid "Click Physical Network."
+msgstr ""
+
+#: ../../networking2.rst:1380
+# 01147d3437e04c6c93201551e05eec93
+msgid "Click Networks."
+msgstr ""
+
+#: ../../networking2.rst:1384
+# f5611c1c2d6f4bc2935f6fcb462429ac
+msgid "Select the networks you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:1388
+# 8c8af6183f054d4b87cd5369985f279b
+msgid "Click View IP Ranges."
+msgstr ""
+
+#: ../../networking2.rst:1392
+# 27bfee4a94154becadc04d190e2248f0
+msgid "Click Add IP Range."
+msgstr ""
+
+#: ../../networking2.rst:1394
+# 0b8e9d89d4724266b4f358cddb5b5dae
+msgid "The Add IP Range dialog is displayed, as follows:"
+msgstr ""
+
+#: ../../networking2.rst:1396
+# b80689bd7547487da595f615e2462e55
+msgid "|add-ip-range.png|"
+msgstr ""
+
+#: ../../networking2.rst:1402
+#: ../../networking2.rst:5168
+# ecfac85bd0504455b3d64af38c930d89
+# b0284174465747738037a24f289b32cd
+msgid "All the fields are mandatory."
+msgstr ""
+
+#: ../../networking2.rst:1406
+#: ../../networking2.rst:5186
+# 2a42d646d37c4df6add5bdf38ceca64d
+# d96a1cf974414215858b14602328707b
+msgid "**Gateway**: The gateway for the tier you create. Ensure that the gateway is within the Super CIDR range that you specified while creating the VPC, and is not overlapped with the CIDR of any existing tier within the VPC."
+msgstr ""
+
+#: ../../networking2.rst:1413
+#: ../../networking2.rst:5203
+# 135026f2c8ab4d77a877e4d100640178
+# 035c6987b29147ebb036cad74b0ca7e2
+msgid "**Netmask**: The netmask for the tier you create."
+msgstr ""
+
+#: ../../networking2.rst:1415
+#: ../../networking2.rst:5205
+# ff580244e12e4780b2df473d710b2271
+# 8323a108551a443f8e02e4e8bf7cb1cc
+msgid "For example, if the VPC CIDR is 10.0.0.0/16 and the network tier CIDR is 10.0.1.0/24, the gateway of the tier is 10.0.1.1, and the netmask of the tier is 255.255.255.0."
+msgstr ""
+
+#: ../../networking2.rst:1421
+# e68e024d0d01404c95c2dfc37f213a3e
+msgid "**Start IP/ End IP**: A range of IP addresses that are accessible from the Internet and will be allocated to guest VMs. Enter the first and last IP addresses that define a range that CloudStack can assign to guest VMs ."
+msgstr ""
+
+#: ../../networking2.rst:1431
+# 878c548f176b4ef18a4c21be8ace7a7b
+msgid "Isolation in Advanced Zone Using Private VLAN"
+msgstr ""
+
+#: ../../networking2.rst:1433
+# a24c2265540a4aef9c82390bf465ff16
+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 users' VMs."
+msgstr ""
+
+#: ../../networking2.rst:1444
+# 4a22b32ca020436b81dd8f07f34306f4
+msgid "Isolate VMs in a shared networks by using Private VLANs."
+msgstr ""
+
+#: ../../networking2.rst:1448
+# abb78195383c40838e8616f04b87f7f2
+msgid "Supported on KVM, XenServer, and VMware hypervisors"
+msgstr ""
+
+#: ../../networking2.rst:1452
+# 2b02488a70fc420996644982994ac6eb
+msgid "PVLAN-enabled shared network can be a part of multiple networks of a guest VM."
+msgstr ""
+
+#: ../../networking2.rst:1456
+# d86c07b7947d412799db280d59e3f9e5
+msgid "About Private VLAN"
+msgstr ""
+
+#: ../../networking2.rst:1458
+# 892b94b696954a8e9527248d969742c6
+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 VLAN that is being divided into smaller groups is called Primary, which implies that all VLAN pairs in a private VLAN share the same Primary VLAN. All the secondary VLANs exist only inside the Primary. Each Secondary VLAN has a specific VLAN ID associated to it, which differentiates one sub-domain from another."
+msgstr ""
+
+#: ../../networking2.rst:1471
+# 65264ae745f94985b736d5abe4446401
+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 ""
+
+#: ../../networking2.rst:1480
+# 65ce874571f0428cbe807261ef5c91ff
+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 ""
+
+#: ../../networking2.rst:1490
+# 11d7e1e2a07f44da85da53d61de9130b
+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 ""
+
+#: ../../networking2.rst:1498
+# c008cae9b2a74d48a4170c54a17a63d6
+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 communicate among themselves, deploy them in community ports."
+msgstr ""
+
+#: ../../networking2.rst:1508
+# eca73570aa5c496ba46877b3392feba4
+msgid "For further reading:"
+msgstr ""
+
+#: ../../networking2.rst:1512
+# 3fb1a7985e5143939ea6ed3db5517634
+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 ""
+
+#: ../../networking2.rst:1517
+# 413321509f2d47a8b184ec2e8adbfcb5
+msgid "`Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment <http://tools.ietf.org/html/rfc5517>`_"
+msgstr ""
+
+#: ../../networking2.rst:1522
+# d92ce4bc2e25409b903ed61ed410286d
+msgid "`Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview (1010691) <http://kb.vmware.com>`_"
+msgstr ""
+
+#: ../../networking2.rst:1530
+# 7b72e0b764624a06bcaed4e13da2da3d
+msgid "Use a PVLAN supported switch."
+msgstr ""
+
+#: ../../networking2.rst:1532
+# 4c3023eb7cbe49fdbc0af7708061b61c
+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 ""
+
+#: ../../networking2.rst:1538
+# 3d53c6dd5e0c47c98d6a7945385c1baa
+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 ""
+
+#: ../../networking2.rst:1546
+# c0a596996cd541c399ba489470a762f3
+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 ""
+
+#: ../../networking2.rst:1553
+# cc4e6fc0e1f245528985b2117be84d9f
+msgid "Configure private VLAN on your physical switches out-of-band."
+msgstr ""
+
+#: ../../networking2.rst:1557
+# 62074ec8d4834007976930e3c6191196
+msgid "Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS)."
+msgstr ""
+
+#: ../../networking2.rst:1560
+# 801f968d2c41437ab6df2a4e4ba571f9
+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 ""
+
+#: ../../networking2.rst:1565
+# 11c21ce678fe4324bddd45de27ee2be7
+msgid "Creating a PVLAN-Enabled Guest Network"
+msgstr ""
+
+#: ../../networking2.rst:1625
+# 3a96dbbceb574c5fa075e67bf6efd8eb
+msgid "**Secondary Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr ""
+
+#: ../../networking2.rst:1628
+# 7030034cd1d8428a993a53ec2cf81a4b
+msgid "For the description on Secondary Isolated VLAN, see `About Private VLAN\" <#about-private-vlan>`_."
+msgstr ""
+
+#: ../../networking2.rst:1691
+# 3334596753684a6cae9e21d47cf11119
+msgid "Security Groups"
+msgstr ""
+
+#: ../../networking2.rst:1694
+# e6afa18d968443a988f9cda5396370a6
+msgid "About Security Groups"
+msgstr ""
+
+#: ../../networking2.rst:1696
+# 12db6b6e0abb441ca307862c39b2f3a7
+msgid "Security groups provide a way to isolate traffic to VMs. 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. Security groups are particularly useful in zones that use basic networking, because there is a single guest network for all guest VMs. In advanced zones, security groups are supported only on the KVM hypervisor."
+msgstr ""
+
+#: ../../networking2.rst:1706
+# 5e0a423faa66428cb475ef10f065148b
+msgid "In a zone that uses advanced networking, you can instead define multiple guest networks to isolate traffic to VMs."
+msgstr ""
+
+#: ../../networking2.rst:1708
+# d58dc8ccb7ac4d10926fb53edabf176a
+msgid "Each CloudStack account comes with a default security group that denies all inbound traffic and allows all outbound traffic. The default security group can be modified so that all new VMs inherit some other desired set of rules."
+msgstr ""
+
+#: ../../networking2.rst:1713
+# 39f399e25b2f415d8584bd6f5dd19360
+msgid "Any CloudStack user can set up any number of additional security groups. When a new VM is launched, it is assigned to the default security group unless another user-defined security group is specified. A VM can be a member of any number of security groups. Once a VM is assigned to a security group, it remains in that group for its entire lifetime; you can not move a running VM from one security group to another."
+msgstr ""
+
+#: ../../networking2.rst:1720
+# bd1a3a7c766a49568e5d389c615a00fd
+msgid "You can modify a security group by deleting or adding any number of ingress and egress rules. When you do, the new rules apply to all VMs in the group, whether running or stopped."
+msgstr ""
+
+#: ../../networking2.rst:1724
+# a52edc5536e9495bbf1410f462d5932b
+msgid "If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule."
+msgstr ""
+
+#: ../../networking2.rst:1729
+# 7d25ba3d47574104ae0d8c4085970ddc
+msgid "Adding a Security Group"
+msgstr ""
+
+#: ../../networking2.rst:1731
+# 4a52e8eaf7f5498e9cac0ef8d3e753bb
+msgid "A user or administrator can define a new security group."
+msgstr ""
+
+#: ../../networking2.rst:1739
+#: ../../networking2.rst:1819
+# a705e539e74940a78a8983f0585d2556
+# c227631e574645b2b6062f0bf192b879
+msgid "In the left navigation, choose Network"
+msgstr ""
+
+#: ../../networking2.rst:1743
+# 7c3b2c1204ad4116b2771e974c0cf4c2
+msgid "In Select view, choose Security Groups."
+msgstr ""
+
+#: ../../networking2.rst:1747
+# 721d38433467434482cb1c4486f14572
+msgid "Click Add Security Group."
+msgstr ""
+
+#: ../../networking2.rst:1751
+# 02ecffe07c904fc2a4c3fa6a392afd04
+msgid "Provide a name and description."
+msgstr ""
+
+#: ../../networking2.rst:1757
+# 3e0ee4bc42fc4ea2a3189f69cde928db
+msgid "The new security group appears in the Security Groups Details tab."
+msgstr ""
+
+#: ../../networking2.rst:1761
+# 1b1ca02aa0b348c1b8d8e92f7dbe459d
+msgid "To make the security group useful, continue to Adding Ingress and Egress Rules to a Security Group."
+msgstr ""
+
+#: ../../networking2.rst:1765
+# 6d68ff5e482a496ea71d636366da8518
+msgid "Security Groups in Advanced Zones (KVM Only)"
+msgstr ""
+
+#: ../../networking2.rst:1767
+# bf3e0daa32bd4d928334c6593b3da60d
+msgid "CloudStack provides the ability to use security groups to provide isolation between guests on a single shared, zone-wide network in an advanced zone where KVM is the hypervisor. Using security groups in advanced zones rather than multiple VLANs allows a greater range of options for setting up guest isolation in a cloud."
+msgstr ""
+
+#: ../../networking2.rst:1776
+# a13d1f37385b4e7b86996acde4babec4
+msgid "The following are not supported for this feature:"
+msgstr ""
+
+#: ../../networking2.rst:1780
+# 8fc8b70b5cde4f87a62e5b1ca4a75e2a
+msgid "Two IP ranges with the same VLAN and different gateway or netmask in security group-enabled shared network."
+msgstr ""
+
+#: ../../networking2.rst:1785
+# 9afc1351e88841e18eb5fe14fc168913
+msgid "Two IP ranges with the same VLAN and different gateway or netmask in account-specific shared networks."
+msgstr ""
+
+#: ../../networking2.rst:1790
+# 964239c4525b49c48d33e98fa19650e7
+msgid "Multiple VLAN ranges in security group-enabled shared network."
+msgstr ""
+
+#: ../../networking2.rst:1794
+# 0e18491db0744181b7e4947503a5bf06
+msgid "Multiple VLAN ranges in account-specific shared networks."
+msgstr ""
+
+#: ../../networking2.rst:1796
+# 05bc77a1a85b4d40ac91eb83feacc795
+msgid "Security groups must be enabled in the zone in order for this feature to be used."
+msgstr ""
+
+#: ../../networking2.rst:1800
+# e64a176e0d1a4f50992f36b58586ff9e
+msgid "Enabling Security Groups"
+msgstr ""
+
+#: ../../networking2.rst:1802
+# 6ad796b8b65541758fa9ac87509ecbc2
+msgid "In order for security groups to function in a zone, the security groups feature must first be enabled for the zone. The administrator can do this when creating a new zone, by selecting a network offering that includes security groups. The procedure is described in Basic Zone Configuration in the Advanced Installation Guide. The administrator can not enable security groups for an existing zone, only when creating a new zone."
+msgstr ""
+
+#: ../../networking2.rst:1811
+# e2ba36a71c01454c872db51e3f32589d
+msgid "Adding Ingress and Egress Rules to a Security Group"
+msgstr ""
+
+#: ../../networking2.rst:1823
+# a1a516287e0441a7bfff434dc4c25818
+msgid "In Select view, choose Security Groups, then click the security group you want ."
+msgstr ""
+
+#: ../../networking2.rst:1828
+# d6e55c16dfbc4f85a9169f71f66a2804
+msgid "To add an ingress rule, click the Ingress Rules tab and fill out the following fields to specify what network traffic is allowed into VM instances in this security group. If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule."
+msgstr ""
+
+#: ../../networking2.rst:1836
+# 42943b264de7449685e9e46efc6a170c
+msgid "**Add by CIDR/Account**. Indicate whether the source of the traffic will be defined by IP address (CIDR) or an existing security group in a CloudStack account (Account). Choose Account if you want to allow incoming traffic from all VMs in another security group"
+msgstr ""
+
+#: ../../networking2.rst:1844
+# e2cc45d1de64494db50fe0a1c454f1de
+msgid "**Protocol**. The networking protocol that sources will use to send traffic to the security group. TCP and UDP are typically used for data exchange and end-user communications. ICMP is typically used to send error messages or network monitoring data."
+msgstr ""
+
+#: ../../networking2.rst:1851
+# 3830ab6e902f4099a0d5bcd5f94c98f9
+msgid "**Start Port, End Port**. (TCP, UDP only) A range of listening ports that are the destination for the incoming traffic. If you are opening a single port, use the same number in both fields."
+msgstr ""
+
+#: ../../networking2.rst:1857
+# 8964c7df1073444194c59e9ddf9726c6
+msgid "**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code that will be accepted."
+msgstr ""
+
+#: ../../networking2.rst:1862
+# b0cf8f7cc93e4879aab846412508fb1a
+msgid "**CIDR**. (Add by CIDR only) To accept only traffic from 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 incoming traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr ""
+
+#: ../../networking2.rst:1870
+# 76c5ca0cfe334149a512d3956349b0df
+msgid "**Account, Security Group**. (Add by Account only) To accept only traffic from another security group, enter the CloudStack account and name of a security group that has already been defined in that account. To allow traffic between VMs within the security group you are editing now, enter the same name you used in step 7."
+msgstr ""
+
+#: ../../networking2.rst:1876
+# 3903c6ce7d964ff99823291ab66fd97e
+msgid "The following example allows inbound HTTP access from anywhere:"
+msgstr ""
+
+#: ../../networking2.rst:1878
+# 0ca36e66c67f4b0fbc6e9642f98244e2
+msgid "|httpaccess.png|"
+msgstr ""
+
+#: ../../networking2.rst:1882
+# 0e328d3fe5ff4d199d094778ca339694
+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 security group. If no egress rules are specified, then all traffic will be allowed out. Once egress rules are specified, the following types of traffic are allowed out: traffic specified in egress rules; queries to DNS and DHCP servers; and responses to any traffic that has been allowed in through an ingress rule"
+msgstr ""
+
+#: ../../networking2.rst:1893
+# 6345c89e81524779ab6e143c18064dbf
+msgid "**Add by CIDR/Account**. Indicate whether the destination of the traffic will be defined by IP address (CIDR) or an existing security group in a CloudStack account (Account). Choose Account if you want to allow outgoing traffic to all VMs in another security group."
+msgstr ""
+
+#: ../../networking2.rst:1901
+# 3aacbdb631954d769b273926968b7e76
+msgid "**Protocol**. The networking protocol that VMs will use to send outgoing traffic. TCP and UDP are typically used for data exchange and end-user communications. ICMP is typically used to send error messages or network monitoring data."
+msgstr ""
+
+#: ../../networking2.rst:1908
+# bf325442015447ccacf5f769195e3e42
+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 ""
+
+#: ../../networking2.rst:1914
+# 6018cd1041b946a9a0e09343687a2ef2
+msgid "**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code that will be sent"
+msgstr ""
+
+#: ../../networking2.rst:1919
+# dcedb9aa8a5f45fc8708767a08ba30e5
+msgid "**CIDR**. (Add by CIDR only) To send traffic only to 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 ""
+
+#: ../../networking2.rst:1927
+# 7fe28834c4e944fa960b6bc798395bb8
+msgid "**Account, Security Group**. (Add by Account only) To allow traffic to be sent to another security group, enter the CloudStack account and name of a security group that has already been defined in that account. To allow traffic between VMs within the security group you are editing now, enter its name."
+msgstr ""
+
+#: ../../networking2.rst:1938
+# b98f0fffba9942f6b1c8338e399cd238
+msgid "External Firewalls and Load Balancers"
+msgstr ""
+
+#: ../../networking2.rst:1940
+# 538d6ddab6754d2f95ed16d1c8c19a47
+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 ""
+
+#: ../../networking2.rst:1946
+# 5b34eb6058a24e94801076fbb7ad2149
+msgid "About Using a NetScaler Load Balancer"
+msgstr ""
+
+#: ../../networking2.rst:1948
+# a78cf7cfee394628aaab85679c2ff14d
+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 ""
+
+#: ../../networking2.rst:1954
+# b05631eea76f43049dad194f18a6a9b6
+msgid "In a Basic zone, load balancing service is supported only if Elastic IP or Elastic LB services are enabled."
+msgstr ""
+
+#: ../../networking2.rst:1956
+# 705041b2434b4ca483b18e0e974897dc
+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 device providing EIP/ELB, layer 3 router must have a policy-based routing. A policy-based route must be set up so that all traffic originated from the guest VM's are directed to NetScaler device. This is required to ensure that the outbound traffic from the guest VM's is routed to a public IP by using NAT.For more information on Elastic IP, see `\"About Elastic IP\" <#about-elastic-ip>`_."
+msgstr ""
+
+#: ../../networking2.rst:1970
+# 6bfdd4158ad14aa38deebe45fb9cbb9a
+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 ""
+
+#: ../../networking2.rst:1974
+# d0b9fb7fee614995a8c6fa5905fff158
+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 ""
+
+#: ../../networking2.rst:1979
+# 11e9cfee2a764a7fb0b70afb98d31c3b
+msgid "To install and enable an external load balancer for CloudStack management, see External Guest Load Balancer Integration in the Installation Guide."
+msgstr ""
+
+#: ../../networking2.rst:1983
+# 1fb1edcb2b6d4ffaa95d0fbe2737024a
+msgid "The Citrix NetScaler comes in three varieties. The following table summarizes how these variants are treated in CloudStack."
+msgstr ""
+
+#: ../../networking2.rst:1986
+# 12edf1030b1a46dea557408534fb87af
+msgid "NetScaler ADC Type"
+msgstr ""
+
+#: ../../networking2.rst:1988
+# 76d92f88c012490b8f745539f5beff17
+msgid "Description of Capabilities"
+msgstr ""
+
+#: ../../networking2.rst:1990
+# 85070d10ba6a46b6b7e646e0e6e68101
+msgid "CloudStack Supported Features"
+msgstr ""
+
+#: ../../networking2.rst:1992
+# 04cb1b68ff3b48edabc301bf64ccf560
+msgid "MPX"
+msgstr ""
+
+#: ../../networking2.rst:1994
+# 2d07236e0fb24abc935fc25da378dc09
+msgid "Physical appliance. Capable of deep packet inspection. Can act as application firewall and load balancer"
+msgstr ""
+
+#: ../../networking2.rst:1997
+# ec6682993a804b9e9f80b1d00004182e
+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 ""
+
+#: ../../networking2.rst:2001
+# b9ff4330d7774617b6ae9a5e7a8a6f1d
+msgid "VPX"
+msgstr ""
+
+#: ../../networking2.rst:2003
+# 9005b76458ad41a483ee097a591c21db
+msgid "Virtual appliance. Can run as VM on XenServer, ESXi, and Hyper-V hypervisors. Same functionality as MPX"
+msgstr ""
+
+#: ../../networking2.rst:2006
+# 3685fe921180440098631978824bd41e
+msgid "Supported on ESXi and XenServer. Same functional support as for MPX. CloudStack will treat VPX and MPX as the same device type."
+msgstr ""
+
+#: ../../networking2.rst:2009
+# b4d1336da974407c9db6af169f5b24ff
+msgid "SDX"
+msgstr ""
+
+#: ../../networking2.rst:2011
+# 62d3529ceb9a40a5a2112aff3c4ee083
+msgid "Physical appliance. Can create multiple fully isolated VPX instances on a single appliance to support multi-tenant usage"
+msgstr ""
+
+#: ../../networking2.rst:2014
+# 926617dc198f41458aa9112b482a4259
+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 ""
+
+#: ../../networking2.rst:2021
+# 05a9bff4e49b4e6faaeeecdcf5ef0c7e
+msgid "Configuring SNMP Community String on a RHEL Server"
+msgstr ""
+
+#: ../../networking2.rst:2023
+# 75f35b06310648d3a4b6bfddf33bc68e
+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 ""
+
+#: ../../networking2.rst:2029
+# 9c719f6ec799444b9ad1bf98205eabc8
+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 ""
+
+#: ../../networking2.rst:2035
+# bdc592b5c12d4fc9bbfb1cb4bf44b046
+msgid "Ensure that you installed SNMP on RedHat. If not, run the following command:"
+msgstr ""
+
+#: ../../networking2.rst:2044
+# 02cf855a387949f3b83f4bb528cbf1c4
+msgid "Edit the /etc/snmp/snmpd.conf file to allow the SNMP polling from the NetScaler device."
+msgstr ""
+
+#: ../../networking2.rst:2049
+# 1decbe06fdbd45039c5b61ab7d3088d9
+msgid "Map the community name into a security name (local and mynetwork, depending on where the request is coming from):"
+msgstr ""
+
+#: ../../networking2.rst:2053
+# 8a17ab86a6dd4d5787e52b8e4414895f
+msgid "Use a strong password instead of public when you edit the following table."
+msgstr ""
+
+#: ../../networking2.rst:2062
+# 0179988cd69648e98566be83bd2dff14
+msgid "Setting to 0.0.0.0 allows all IPs to poll the NetScaler server."
+msgstr ""
+
+#: ../../networking2.rst:2066
+# 6577e90762254a09835bb6467df5a6ba
+msgid "Map the security names into group names:"
+msgstr ""
+
+#: ../../networking2.rst:2078
+# e25e9e1efba84febaa488370009ea353
+msgid "Create a view to allow the groups to have the permission to:"
+msgstr ""
+
+#: ../../networking2.rst:2086
+# 45d988cd96b04573b080085fbd6ee6cb
+msgid "Grant access with different write permissions to the two groups to the view you created."
+msgstr ""
+
+#: ../../networking2.rst:2097
+# 9fc121277fb04877af683ce49e88b40b
+msgid "Unblock SNMP in iptables."
+msgstr ""
+
+#: ../../networking2.rst:2105
+# ce86c5292fa840f194d550efe25863bf
+msgid "Start the SNMP service:"
+msgstr ""
+
+#: ../../networking2.rst:2113
+# c68c4cc6430e45fb8625e65486ad2c89
+msgid "Ensure that the SNMP service is started automatically during the system startup:"
+msgstr ""
+
+#: ../../networking2.rst:2121
+# 9a86418eaea24d238f86754265515817
+msgid "Initial Setup of External Firewalls and Load Balancers"
+msgstr ""
+
+#: ../../networking2.rst:2123
+# 06a101bd0fb84bd0b26f130d1a867429
+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 ""
+
+#: ../../networking2.rst:2129
+# ab3bbc626f914afe9ac2a1b689262029
+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 ""
+
+#: ../../networking2.rst:2135
+# f006b40c148b48a08def3072e5ad067c
+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 ""
+
+#: ../../networking2.rst:2141
+# cd7a4e14c7984cd284aa60828cf93747
+msgid "A firewall filter counter that measures the number of bytes of outgoing traffic for the account"
+msgstr ""
+
+#: ../../networking2.rst:2144
+# 6863d2e715784256ae2aa22351962b89
+msgid "The following objects are created on the load balancer:"
+msgstr ""
+
+#: ../../networking2.rst:2148
+# 9f6423f23a65442d8e2bda3bb6db462b
+msgid "A new VLAN that matches the account's provisioned Zone VLAN"
+msgstr ""
+
+#: ../../networking2.rst:2152
+# 72187f0b05e848e6967cdb9a555381db
+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 ""
+
+#: ../../networking2.rst:2156
+# ab8a654963914f2baa6cec082bc98b83
+msgid "Ongoing Configuration of External Firewalls and Load Balancers"
+msgstr ""
+
+#: ../../networking2.rst:2158
+# 6cc8786791794c06befa8a17509abd10
+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 objects:"
+msgstr ""
+
+#: ../../networking2.rst:2169
+# 1264629934524065bc84801e9205e4a5
+msgid "A static NAT rule that maps the public IP address to the private IP address of a VM."
+msgstr ""
+
+#: ../../networking2.rst:2174
+# c5fc12f27ace4872a52cb589ca35d678
+msgid "A security policy that allows traffic within the set of protocols and port ranges that are specified."
+msgstr ""
+
+#: ../../networking2.rst:2179
+# 3987c5c775d14d12b88cb87ad208f691
+msgid "A firewall filter counter that measures the number of bytes of incoming traffic to the public IP."
+msgstr ""
+
+#: ../../networking2.rst:2182
+# c5db6b14c530477fbdab470760ab4530
+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 ""
+
+#: ../../networking2.rst:2188
+# ffe7e0e1d6a54f58847e94107290cdea
+msgid "Load Balancer Rules"
+msgstr ""
+
+#: ../../networking2.rst:2190
+# c4c2a4ed95bf4c308ca4f5e48b75081b
+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 ""
+
+#: ../../networking2.rst:2196
+# 5edeb5d8028f43088fd22e105d890c45
+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 ""
+
+#: ../../networking2.rst:2206
+# aee5ead118ba49d2af6fd663749cb21a
+msgid "Adding a Load Balancer Rule"
+msgstr ""
+
+#: ../../networking2.rst:2218
+# ef9ec7e8608f4622a42b9006e67332f1
+msgid "Click the name of the network where you want to load balance the traffic."
+msgstr ""
+
+#: ../../networking2.rst:2227
+#: ../../networking2.rst:6334
+#: ../../networking2.rst:6728
+# d56ea994f5094995b0b1a4f7aa68eca8
+# 7764a67f3ade40b1b3dc2075fac839f4
+# ff64344bfa4d4a28a323dffd869d78cc
+msgid "Click the IP address for which you want to create the rule, then click the Configuration tab."
+msgstr ""
+
+#: ../../networking2.rst:2232
+#: ../../networking2.rst:6339
+# bd1517a9c2da449f8664512b691ebb65
+# 563ad659bddb4945a34373de5161db96
+msgid "In the Load Balancing node of the diagram, click View All."
+msgstr ""
+
+#: ../../networking2.rst:2234
+# 5c4e645be6564d2981406da6582c05fa
+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 ""
+
+#: ../../networking2.rst:2239
+# 19e72807452b47e3a1cc379d4795b3d9
+msgid "To do that, select the name of the network, then click Add Load Balancer tab. Continue with #7."
+msgstr ""
+
+#: ../../networking2.rst:2244
+#: ../../networking2.rst:3732
+# 92a8a5aa771d4722b5156213b1af4fd5
+# 130044af73ab495bab3655cce16db603
+msgid "Fill in the following:"
+msgstr ""
+
+#: ../../networking2.rst:2248
+#: ../../networking2.rst:6351
+#: ../../networking2.rst:6609
+# 96cfbfac34a546b2aabfdd57984816d9
+# 2f3e7f66b6854ce1bf779bd548cb6f12
+# 0e0ff88d07eb4baf9edfced6bfbc8d7b
+msgid "**Name**: A name for the load balancer rule."
+msgstr ""
+
+#: ../../networking2.rst:2252
+# d159c92df5a7480c9ea3390d74166c14
+msgid "**Public Port**: The port receiving incoming traffic to be balanced."
+msgstr ""
+
+#: ../../networking2.rst:2257
+#: ../../networking2.rst:6360
+# b581656e45d34c8d81bf85c2f5e1687d
+# 4bc8d2ff0de548bfac5f09a67456130e
+msgid "**Private Port**: The port that the VMs will use to receive the traffic."
+msgstr ""
+
+#: ../../networking2.rst:2262
+# 2543a97cf11048648e1d03e65b26ff8e
+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 ""
+
+#: ../../networking2.rst:2269
+# 0e85be5a5f044e87a64418a1378234c5
+msgid "**Stickiness**: (Optional) Click Configure and choose the algorithm for the stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr ""
+
+#: ../../networking2.rst:2275
+# d254fa1eae76499aa9dd3674a7ccb16e
+msgid "**AutoScale**: Click Configure and complete the AutoScale configuration as explained in :ref:`conf-autoscale`."
+msgstr ""
+
+#: ../../networking2.rst:2280
+# 80c293bf8b72415daff417f7d1e485c2
+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 ""
+
+#: ../../networking2.rst:2286
+# 7646c6b438bc4f6a95b867bca86d2778
+msgid "**Ping path (Optional)**: Sequence of destinations to which to send health check queries. Default: / (all)."
+msgstr ""
+
+#: ../../networking2.rst:2291
+# f2e4bc38af6b4daf89f145d9739466f4
+msgid "**Response time (Optional)**: How long to wait for a response from the health check (2 - 60 seconds). Default: 5 seconds."
+msgstr ""
+
+#: ../../networking2.rst:2296
+# b56f106902c64b1c8aa0a36c64aec4ac
+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 ""
+
+#: ../../networking2.rst:2303
+# 4295d940156f4b3ba091563f2533eb12
+msgid "**Healthy threshold (Optional)**: Number of consecutive health check successes that are required before declaring an instance healthy. Default: 2."
+msgstr ""
+
+#: ../../networking2.rst:2309
+# 7ac5054f47b24947b246698f28438d57
+msgid "**Unhealthy threshold (Optional)**: Number of consecutive health check failures that are required before declaring an instance unhealthy. Default: 10."
+msgstr ""
+
+#: ../../networking2.rst:2315
+# 7836878559f34b60b1399d767ae28a29
+msgid "Click Add VMs, then select two or more VMs that will divide the load of incoming traffic, and click Apply."
+msgstr ""
+
+#: ../../networking2.rst:2318
+# 6a2803e8da5f48318b4b61fd67bcd43f
+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 ""
+
+#: ../../networking2.rst:2322
+# d24dcf4899a54968b3b3db61c818c67d
+msgid "Sticky Session Policies for Load Balancer Rules"
+msgstr ""
+
+#: ../../networking2.rst:2324
+# 8ab79ec71a4e4b98ad38ad17ec22af5f
+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 ""
+
+#: ../../networking2.rst:2330
+# c3519ee8b4b344cabb8750b51ce2309d
+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, cookies are used. The cookie generated by the load balancer or application is included in request and response URLs to create persistence. The cookie name can be specified by the administrator or automatically generated. A variety of options are provided to control the exact behavior of cookies, such as how they are generated and whether they are cached."
+msgstr ""
+
+#: ../../networking2.rst:2344
+# 79f3c606c002408f917d8fa2d8fdd9eb
+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 ""
+
+#: ../../networking2.rst:2351
+# 3f62bdba5f31457aadd915d45be545a7
+msgid "Health Checks for Load Balancer Rules"
+msgstr ""
+
+#: ../../networking2.rst:2353
+# b083bc41aca34d9b98d86dc1d0206017
+msgid "(NetScaler load balancer only; requires NetScaler version 10.0)"
+msgstr ""
+
+#: ../../networking2.rst:2355
+# 1bf841d08f9947a9a22824b89f8e09d4
+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 ""
+
+#: ../../networking2.rst:2362
+# 85c9feea4e8743198f31cc482695a279
+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 ""
+
+#: ../../networking2.rst:2367
+# 352dde5daf9c433c88293769a6bb0553
+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 with a health check configured, the state will be shown as UP or DOWN in the UI depending on the result of the most recent health check."
+msgstr ""
+
+#: ../../networking2.rst:2377
+# 7487d03bd3954a619c9deab8432eccb5
+msgid "You can delete or modify existing health check policies."
+msgstr ""
+
+#: ../../networking2.rst:2379
+# 9bb908ef254545669272a47771402d19
+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 ""
+
+#: ../../networking2.rst:2384
+# a4a4e4ced2f64992a7090ec99eec5b74
+msgid "For details on how to set a health check policy using the UI, see :ref:`adding-lb-rule`."
+msgstr ""
+
+#: ../../networking2.rst:2390
+# 7583c6f2d7c04c729c049fe5fb20f1d0
+msgid "Configuring AutoScale"
+msgstr ""
+
+#: ../../networking2.rst:2392
+# 110dc69ca3524adf841208bc3b2afa45
+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 ""
+
+#: ../../networking2.rst:2400
+# 6067162c83174a73b67766fe147a1105
+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 CPU usage is less than 20 percent for 30 minutes."
+msgstr ""
+
+#: ../../networking2.rst:2409
+# 4178b892ea11419ca207b4f23416d240
+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 ""
+
+#: ../../networking2.rst:2413
+# 720fc42dfba2445580316d8a7c7b6446
+msgid "AutoScale is supported on NetScaler Release 10 Build 74.4006.e and beyond."
+msgstr ""
+
+#: ../../networking2.rst:2418
+# 25d5a916dcd24f8c93a8a2270ea1dec8
+msgid "Before you configure an AutoScale rule, consider the following:"
+msgstr ""
+
+#: ../../networking2.rst:2422
+# e5e20ba2d3ec4d3492856bcfe74d40f1
+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 ""
+
+#: ../../networking2.rst:2427
+# a3786b1dded84da299934e36c6d9e71a
+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 ""
+
+#: ../../networking2.rst:2433
+# 848edeadae8842dd9b6660533e51cb84
+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 ""
+
+#: ../../networking2.rst:2440
+# 47a8c8b854724128bca574cad390341b
+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 RHEL Server\" <#configuring-snmp-community-string-on-a-rhel-server>`_ to configure SNMP on a RHEL machine."
+msgstr ""
+
+#: ../../networking2.rst:2451
+# c4bb8c60d3214089b1726fe9bea68db1
+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 ""
+
+#: ../../networking2.rst:2459
+# f6027494d923450aa21e243d185af107
+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 ""
+
+#: ../../networking2.rst:2465
+# 30b6a0dcaf8e406d930c2671bee73f49
+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 ""
+
+#: ../../networking2.rst:2472
+# 8e11275ad7bc4f9bbae8488f9270ddb9
+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 ""
+
+#: ../../networking2.rst:2478
+# 2f62ff61696a4b28b1fe7a6e9ed379af
+msgid "Configuration"
+msgstr ""
+
+#: ../../networking2.rst:2482
+# 6ecf74a9baef420b8f4cf0f4a633ee47
+msgid "|autoscaleateconfig.png|"
+msgstr ""
+
+#: ../../networking2.rst:2486
+# f28a8f2eaa864c579595a69d9339a432
+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 ""
+
+#: ../../networking2.rst:2496
+# ab74533b03a84bf99ebf74e5eb9a1f2d
+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 ""
+
+#: ../../networking2.rst:2504
+# e0ca6e4baff64455862f60837590f305
+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 ""
+
+#: ../../networking2.rst:2512
+# 985d35506cb34451b0d15a405feae1a7
+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 active instance count breaches the Max instance value."
+msgstr ""
+
+#: ../../networking2.rst:2524
+# fb0ddc4d1f94403ebeed8e5714b4f617
+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 ""
+
+#: ../../networking2.rst:2529
+# 783c86a84d0f4c1b833db963b51c82af
+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 ""
+
+#: ../../networking2.rst:2535
+# 1a3b1e1b09e04f57993e13c4afcb55e0
+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 ""
+
+#: ../../networking2.rst:2543
+# 6a70933964e74afe83fe5d290058b273
+msgid "Specify the following scale-up and scale-down policies:"
+msgstr ""
+
+#: ../../networking2.rst:2547
+# cf10d74a5d0c41e589755735a7cedc27
+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 ""
+
+#: ../../networking2.rst:2554
+# a57ca091c3bd43c096bfa98631b1cdde
+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 ""
+
+#: ../../networking2.rst:2563
+# a0b4564310ab4971b3f47a61f665d061
+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 ""
+
+#: ../../networking2.rst:2569
+# e0ce29c287f846fab5b519e88ea090ee
+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 ""
+
+#: ../../networking2.rst:2575
+# 6561f9d06cfe4f6d9874575da794592a
+msgid "**Add**: Click Add to add the condition."
+msgstr ""
+
+#: ../../networking2.rst:2577
+# 1497e6bea4e1463b844a038331cb983f
+msgid "Additionally, if you want to configure the advanced settings, click Show advanced settings, and specify the following:"
+msgstr ""
+
+#: ../../networking2.rst:2582
+# eb929ac5f36d4e0685a50c5cc16f0df5
+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 ""
+
+#: ../../networking2.rst:2589
+# 8d0aedaf4e0f45a6beda1b9421388942
+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 ""
+
+#: ../../networking2.rst:2598
+# fdefaeca99e24f218e68b41bfe85e3ce
+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 ""
+
+#: ../../networking2.rst:2606
+# cf6ffe6f0c4c4e1a868a853debfcdbbf
+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 ""
+
+#: ../../networking2.rst:2615
+# c4bd403a66d64d868f4d5b0442abb5f7
+msgid "**Disk Offerings**: A predefined set of disk size for primary data storage."
+msgstr ""
+
+#: ../../networking2.rst:2620
+# 8976b1a845f84354ab47314b3cc692d7
+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 ""
+
+#: ../../networking2.rst:2626
+# cca89ffa679d47ad992fe021145932eb
+msgid "**SNMP Port**: The port number on which the SNMP agent that run on the provisioned VMs is listening. Default port is 161."
+msgstr ""
+
+#: ../../networking2.rst:2631
+# e00f8d3ec41440b5b002e2041a08220f
+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 ""
+
+#: ../../networking2.rst:2638
+# 9b84f1bc76c44c38a35321973e56210c
+msgid "**Apply**: Click Apply to create the AutoScale configuration."
+msgstr ""
+
+#: ../../networking2.rst:2641
+# b547fd51c7ac43f6896f5326d0bc8ba8
+msgid "Disabling and Enabling an AutoScale Configuration"
+msgstr ""
+
+#: ../../networking2.rst:2643
+# 38e5928d47d14bc19e1fab9539b611a0
+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 ""
+
+#: ../../networking2.rst:2649
+# 9e667521e0ed422c97c64cd3cd3a8b27
+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 ""
+
+#: ../../networking2.rst:2658
+# 8c265f29a2494792991abbb3daed1b9e
+msgid "Updating an AutoScale Configuration"
+msgstr ""
+
+#: ../../networking2.rst:2660
+# 280deb0a83064852b5f2ddd3b80809a6
+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 ""
+
+#: ../../networking2.rst:2665
+# e7070f9e778042a7aa68aeb88bde2257
+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 ""
+
+#: ../../networking2.rst:2670
+# e92451dccecb4a40a0c35bcc6e42105a
+msgid "Runtime Considerations"
+msgstr ""
+
+#: ../../networking2.rst:2674
+# 5a7ed98221fc42848a83b71bcc5439f8
+msgid "An administrator should not assign a VM to a load balancing rule which is configured for AutoScale."
+msgstr ""
+
+#: ../../networking2.rst:2679
+# 3afe9927a67b460a9e6faea30ba427fb
+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 ""
+
+#: ../../networking2.rst:2688
+# eee56e4a2e474a04988980cace231253
+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 ""
+
+#: ../../networking2.rst:2695
+# 6da746ba5a56414f91ec2e2db3f82484
+msgid "Global Server Load Balancing Support"
+msgstr ""
+
+#: ../../networking2.rst:2697
+# 81e233e5a8774fe7912bb9d777b02098
+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 ""
+
+#: ../../networking2.rst:2705
+# 182ac54151764429a54597e47be09455
+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 ""
+
+#: ../../networking2.rst:2713
+# 8250959d1c994c618634ca275a2acf89
+msgid "About Global Server Load Balancing"
+msgstr ""
+
+#: ../../networking2.rst:2715
+# 23d6ad0ee7e345bd8b6e5a4ff72f0bde
+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 accessing a resource in the event of a failure, or to provide a means of shifting traffic easily to simplify maintenance, or both."
+msgstr ""
+
+#: ../../networking2.rst:2726
+# 9df73711bf05422aa3ff011e97b010d0
+msgid "Components of GSLB"
+msgstr ""
+
+#: ../../networking2.rst:2728
+# 0dbce0ca6baa46aeaad670109fbc187b
+msgid "A typical GSLB environment is comprised of the following components:"
+msgstr ""
+
+#: ../../networking2.rst:2732
+# be687e83d654431899ed881ba56746a0
+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 ""
+
+#: ../../networking2.rst:2742
+# 1a724093f2854945a12f90a9aac0cdf7
+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 ""
+
+#: ../../networking2.rst:2753
+# 5fa2919887bc460f94bbe24c89b9d442
+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 a FQDN DNS name."
+msgstr ""
+
+#: ../../networking2.rst:2764
+# 20cb61cdbd444e9a9f11f683a1ee4b35
+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 balancing or content switching virtual server, the client sends the request to that virtual server's VIP address."
+msgstr ""
+
+#: ../../networking2.rst:2776
+# a5ecee28e9bb433a8951bf3350e6aa91
+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 ""
+
+#: ../../networking2.rst:2783
+# 4eb2a120e2de43caad10fb89f83d8158
+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 and port."
+msgstr ""
+
+#: ../../networking2.rst:2793
+# cd935874099944bd8bd07f110b11f0c3
+msgid "How Does GSLB Works in CloudStack?"
+msgstr ""
+
+#: ../../networking2.rst:2795
+# a07db76162554695b05812b43a222375
+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 xyztelco cloud. For that purpose, they launch two instances each in both the zones: VM1 and VM2 in Zone-1 and VM5 and VM6 in Zone-2. Tenant-A acquires a public IP, IP-1 in Zone-1, and configures a load balancer rule to load balance the traffic between VM1 and VM2 instances. CloudStack orchestrates setting up a virtual server on the LB service provider in Zone-1. Virtual server 1 that is set up on the LB service provider in Zone-1 represents a publicly accessible virtual server that client reaches at IP-1. The client traffic to virtual server 1 at IP-1 will be load balanced across VM1 and VM2 instances."
+msgstr ""
+
+#: ../../networking2.rst:2812
+# 7522dda4534f412e9114fbef583cdbc4
+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 instances. At this point Tenant-A has the service enabled in both the zones, but has no means to set up a disaster recovery plan if one of the zone fails. Additionally, there is no way for Tenant-A to load balance the traffic intelligently to one of the zones based on load, proximity and so on. The cloud administrator of xyztelco provisions a GSLB service provider to both the zones. A GSLB provider is typically an ADC that has the ability to act as an ADNS (Authoritative Domain Name Server) and has the mechanism to monitor health of virtual servers both at local and remote sites. The cloud admin enables GSLB as a service to the tenants that use zones 1 and 2."
+msgstr ""
+
+#: ../../networking2.rst:2830
+# 89319188219b404eb12377733494db5a
+msgid "|gslb.png|"
+msgstr ""
+
+#: ../../networking2.rst:2832
+# b984591edede4102820e3e91af964094
+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 start monitoring the health of virtual server 1 and 2 in Zone-1. CloudStack will also orchestrate setting up GSLB virtual server 2 on GSLB service provider at Zone-2. CloudStack will bind virtual server 1 of Zone-1 and virtual server 2 of Zone-2 to GLSB virtual server 2. GSLB virtual server 2 is configured to start monitoring the health of virtual server 1 and 2. CloudStack will bind the domain A.xyztelco.com to both the GSLB virtual server 1 and 2. At this point, Tenant-A service will be globally reachable at A.xyztelco.com. The private DNS server for the domain xyztelcom.com is configured by the admin out-of-band to resolve the domain A.xyztelco.com to the GSLB providers at both the zones, which are configured as ADNS for the domain A.xyztelco.com. A client when sends a DNS request to resolve A.xyztelcom.com, will eventually get DNS delegation to the address of GSLB providers at zone 1 and 2. A client DNS request will be received by the GSLB provider. The GSLB provider, depending on the domain for which it needs to resolve, will pick up the GSLB virtual server associated with the domain. Depending on the health of the virtual servers being load balanced, DNS request for the domain will be resolved to the public IP associated with the selected virtual server."
+msgstr ""
+
+#: ../../networking2.rst:2860
+# 8456ab01fb394c3383eeb5029e812dc5
+msgid "Configuring GSLB"
+msgstr ""
+
+#: ../../networking2.rst:2862
+# a2ddfa5eb5c04d4b8969f09f92f69456
+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 servers. Finally, bind the domain to the GSLB virtual servers. The GSLB configurations on the two appliances at the two different zones are identical, although each sites load-balancing configuration is specific to that site."
+msgstr ""
+
+#: ../../networking2.rst:2874
+# 6d13a7e3c72d4d0fbbf094a3a0048b5e
+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 ""
+
+#: ../../networking2.rst:2879
+# 1b13dfc3a4704d5a8fa68973611763ec
+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 ""
+
+#: ../../networking2.rst:2884
+# 24fa8e0bc85a4858bb09168558689b88
+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 ""
+
+#: ../../networking2.rst:2890
+# 4527dca57f1440febc672d19e072283e
+msgid "Configuring a standard load balancing setup."
+msgstr ""
+
+#: ../../networking2.rst:2894
+# 0c91751454f842ed867ba1142e0082af
+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 ""
+
+#: ../../networking2.rst:2900
+# 81d14d2da5084c1491a9261135038ca2
+msgid "Configure a GSLB site with site name formed from the domain name details."
+msgstr ""
+
+#: ../../networking2.rst:2903
+# b8bd9fe16daa4ddab41339b4016d8128
+msgid "Configure a GSLB site with the site name formed from the domain name."
+msgstr ""
+
+#: ../../networking2.rst:2906
+# ec8346bdb6fb4e9b85623f3b7fedc33b
+msgid "As per the example given above, the site names are A.xyztelco.com and B.xyztelco.com."
+msgstr ""
+
+#: ../../networking2.rst:2909
+# 7e764b73be594f529ea85676104ba0d9
+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 ""
+
+#: ../../networking2.rst:2914
+# e8b2b78d2bcc4ead899d033a82688d6a
+msgid "Configure a GSLB virtual server."
+msgstr ""
+
+#: ../../networking2.rst:2916
+# a658718fb49e4176814d60e01d81a6c3
+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 ""
+
+#: ../../networking2.rst:2921
+# 5bc91629e58046eabfa170a8ff9228cd
+msgid "Configure a GSLB service for each virtual server."
+msgstr ""
+
+#: ../../networking2.rst:2923
+# ad990e26ce2c411081c88e66a273cb2c
+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 ""
+
+#: ../../networking2.rst:2928
+# c239f4ef8dcf4da58541d9bb39333eb2
+msgid "Bind the GSLB services to the GSLB virtual server."
+msgstr ""
+
+#: ../../networking2.rst:2930
+# 1e702a12b98043e2bacf01a137ee482e
+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 ""
+
+#: ../../networking2.rst:2935
+# 10e534b7d92e4b40ad06805f6092f802
+msgid "Bind domain name to GSLB virtual server. Domain name is obtained from the domain details."
+msgstr ""
+
+#: ../../networking2.rst:2938
+# 604d20e5aff64a2e9c6634fcbc5268e5
+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 ""
+
+#: ../../networking2.rst:2943
+# 0ac7add23ac4439ca08fc7caba76441e
+msgid "In each zone that are participating in GSLB, add GSLB-enabled NetScaler device."
+msgstr ""
+
+#: ../../networking2.rst:2946
+# 5d9a5dd2235f42579a6118838bb636fa
+msgid "For more information, see :ref:`enabling-gslb-in-ns`."
+msgstr ""
+
+#: ../../networking2.rst:2948
+# ff5093bc021b4c379b8656f628935267
+msgid "As a domain administrator/ user perform the following:"
+msgstr ""
+
+#: ../../networking2.rst:2952
+# 1ef3c0fd004d43e69534e4a5de7f38d8
+msgid "Add a GSLB rule on both the sites."
+msgstr ""
+
+#: ../../networking2.rst:2954
+# 5779d01501a3442eadc72060d6a298e3
+msgid "See \":ref:`adding-gslb-rule`\"."
+msgstr ""
+
+#: ../../networking2.rst:2958
+# cbd719c880074f4d8e40125c6a766be2
+msgid "Assign load balancer rules."
+msgstr ""
+
+#: ../../networking2.rst:2960
+# c9a1fb87306b486dad29aa18bd3d8819
+msgid "See \":ref:`assigning-lb-rule-gslb`\"."
+msgstr ""
+
+#: ../../networking2.rst:2967
+# a1b0865343b54113bc0065aa808ec8cb
+msgid "The GSLB functionality is supported both Basic and Advanced zones."
+msgstr ""
+
+#: ../../networking2.rst:2971
+# da30d8fa37d94effb410d14171ff906b
+msgid "GSLB is added as a new network service."
+msgstr ""
+
+#: ../../networking2.rst:2975
+# 13eb68d1468e4d7c99753052f9b72a15
+msgid "GSLB service provider can be added to a physical network in a zone."
+msgstr ""
+
+#: ../../networking2.rst:2979
+# 6384b810c9a4410c9ae8f67816e13cd9
+msgid "The admin is allowed to enable or disable GSLB functionality at region level."
+msgstr ""
+
+#: ../../networking2.rst:2984
+# dbd35e047b8d4eb89dde586187f3d0eb
+msgid "The admin is allowed to configure a zone as GSLB capable or enabled."
+msgstr ""
+
+#: ../../networking2.rst:2986
+# 58bd5b2c58a9407692791abdff3e6e54
+msgid "A zone shall be considered as GSLB capable only if a GSLB service provider is provisioned in the zone."
+msgstr ""
+
+#: ../../networking2.rst:2991
+# efc18977b5ac4e84a963305554993e11
+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 ""
+
+#: ../../networking2.rst:2997
+# e793a1e1efc84729991ede4558891921
+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 ""
+
+#: ../../networking2.rst:3002
+# 4c4a8f9e84ea44b19390f5fd020277fb
+msgid "The users can load balance traffic across the availability zones in the same region or different regions."
+msgstr ""
+
+#: ../../networking2.rst:3007
+# 4a914f83d04549c29de6013290e3e7f4
+msgid "The admin can configure DNS name for the entire cloud."
+msgstr ""
+
+#: ../../networking2.rst:3011
+# 596f9eade21844dfa16d3d964f7ce03d
+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 ""
+
+#: ../../networking2.rst:3015
+# 6547e809a9f240ed88dd1d5c4a9d325d
+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 ""
+
+#: ../../networking2.rst:3024
+# 954c733062ed4faaae39782c315285fc
+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 ""
+
+#: ../../networking2.rst:3029
+# b7249d54a14f4c3e9ab5f0ef17a864dd
+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 ""
+
+#: ../../networking2.rst:3035
+# d0d2828b22794506bce6cc04c652759f
+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 ""
+
+#: ../../networking2.rst:3039
+# fe2366a38bbf4359aa47d04dbbe9ef53
+msgid "Statistics is collected from each GSLB virtual server."
+msgstr ""
+
+#: ../../networking2.rst:3044
+# 310bede319094d1a81dd13ae031d171e
+msgid "Enabling GSLB in NetScaler"
+msgstr ""
+
+#: ../../networking2.rst:3046
+# 6cf5dc558b0541b38ee30e8b09f0a119
+msgid "In each zone, add GSLB-enabled NetScaler device for load balancing."
+msgstr ""
+
+#: ../../networking2.rst:3050
+# db33d472d3bd4ea6aefc696bbb848e61
+msgid "Log in as administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../networking2.rst:3058
+# 71afbe01841a4e11a0fcc15b17786d36
+msgid "In Zones, click View More."
+msgstr ""
+
+#: ../../networking2.rst:3066
+# e790f063f0054d8fa2f47e81ff50ca59
+msgid "Click the Physical Network tab, then click the name of the physical network."
+msgstr ""
+
+#: ../../networking2.rst:3071
+# 9e1c9696e24a415ca0080414be0196e6
+msgid "In the Network Service Providers node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking2.rst:3074
+# 536e22d770c44b319d5ee4d2ae4b2153
+msgid "You might have to scroll down to see this."
+msgstr ""
+
+#: ../../networking2.rst:3078
+# 21cd237381d44ee58898516d998a4372
+msgid "Click NetScaler."
+msgstr ""
+
+#: ../../networking2.rst:3082
+# 5bca2c9d180b435bb43c10f72d8b4f50
+msgid "Click Add NetScaler device and provide the following:"
+msgstr ""
+
+#: ../../networking2.rst:3084
+# c101c1fb776f45a3b10751c976f19dff
+msgid "For NetScaler:"
+msgstr ""
+
+#: ../../networking2.rst:3088
+# 2ba731212f4e4d97bf33b98b02462f31
+msgid "**IP Address**: The IP address of the SDX."
+msgstr ""
+
+#: ../../networking2.rst:3092
+# f6756edb0b2749a28f89727cedd914de
+msgid "**Username/Password**: The authentication credentials to access the device. CloudStack uses these credentials to access the device."
+msgstr ""
+
+#: ../../networking2.rst:3098
+# c289535d0983447bb28313242c1afcfd
+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 ""
+
+#: ../../networking2.rst:3105
+# fcf8d7c54d854ef6ac2504c8b710bdea
+msgid "**Public interface**: Interface of device that is configured to be part of the public network."
+msgstr ""
+
+#: ../../networking2.rst:3110
+# 770c0db7ca88466d9f7a6723075a9f24
+msgid "**Private interface**: Interface of device that is configured to be part of the private network."
+msgstr ""
+
+#: ../../networking2.rst:3115
+# ea63258ee8704f1d9b63279f814a6194
+msgid "**GSLB service**: Select this option."
+msgstr ""
+
+#: ../../networking2.rst:3119
+# 8b775a110efc48adafc54539a743a373
+msgid "**GSLB service Public IP**: The public IP address of the NAT translator for a GSLB service that is on a private network."
+msgstr ""
+
+#: ../../networking2.rst:3124
+# 721d09d62d574127acbc4eedf582a400
+msgid "**GSLB service Private IP**: The private IP of the GSLB service."
+msgstr ""
+
+#: ../../networking2.rst:3128
+# 58903b1562ff43d3ac2842018f153a1f
+msgid "**Number of Retries**. Number of times to attempt a command on the device before considering the operation failed. Default is 2."
+msgstr ""
+
+#: ../../networking2.rst:3133
+# 8453399635794a5dafd95e6644881b34
+msgid "**Capacity**: The number of networks the device can handle."
+msgstr ""
+
+#: ../../networking2.rst:3137
+# 032a009f433441a7a9ea141a1a37190f
+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 ""
+
+#: ../../networking2.rst:3149
+# 9c1c5bdbb7b04a5081ee5ee1be823231
+msgid "Adding a GSLB Rule"
+msgstr ""
+
+#: ../../networking2.rst:3153
+#: ../../networking2.rst:3224
+# 9886f1b9081c4b2b9f94068c36234301
+# c0bb3b92c34f4bc79ff38db4f1867976
+msgid "Log in to the CloudStack UI as a domain administrator or user."
+msgstr ""
+
+#: ../../networking2.rst:3157
+#: ../../networking2.rst:3228
+# cf94d6818dfd454bb24a0197b45b1c89
+# 1631e25bb98e44a68e0491ede5dc221d
+msgid "In the left navigation pane, click Region."
+msgstr ""
+
+#: ../../networking2.rst:3161
+#: ../../networking2.rst:3232
+# 99089f1571d2400ba327b8e2e914141f
+# d38f849a92654b41b37919edf2efdf78
+msgid "Select the region for which you want to create a GSLB rule."
+msgstr ""
+
+#: ../../networking2.rst:3165
+#: ../../networking2.rst:3236
+# 17cf4f5a1948405ab27b253588ef1352
+# 98821ced62fd453b90d3870422da2536
+msgid "In the Details tab, click View GSLB."
+msgstr ""
+
+#: ../../networking2.rst:3169
+# 6a85608ee29b4baca127e393abe5ad11
+msgid "Click Add GSLB."
+msgstr ""
+
+#: ../../networking2.rst:3171
+# 0ae5d0eae58a463db228c0ee3c3f2d0e
+msgid "The Add GSLB page is displayed as follows:"
+msgstr ""
+
+#: ../../networking2.rst:3173
+# b9b04ceabaa9463d85a4faf511f47d57
+msgid "|gslb-add.png|"
+msgstr ""
+
+#: ../../networking2.rst:3181
+# 3cc1ebf185774545998478f479bffa85
+msgid "**Name**: Name for the GSLB rule."
+msgstr ""
+
+#: ../../networking2.rst:3185
+# c0e402372e814565bdeff0182a1d1779
+msgid "**Description**: (Optional) A short description of the GSLB rule that can be displayed to users."
+msgstr ""
+
+#: ../../networking2.rst:3190
+# 727d582900354d2bb9e4a0301b19cc35
+msgid "**GSLB Domain Name**: A preferred domain name for the service."
+msgstr ""
+
+#: ../../networking2.rst:3194
+# ef12427c38c94561abed938f4a2bbd8c
+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 ""
+
+#: ../../networking2.rst:3200
+# 241c813551f64e92b78dfd290df99cfe
+msgid "**Service Type**: The transport protocol to use for GSLB. The options are TCP and UDP."
+msgstr ""
+
+#: ../../networking2.rst:3205
+# aa4bcbd25cf647e1ab4384586b654409
+msgid "**Domain**: (Optional) The domain for which you want to create the GSLB rule."
+msgstr ""
+
+#: ../../networking2.rst:3210
+# 839afecaeeed4cbbb6ef0bb21bf498f3
+msgid "**Account**: (Optional) The account on which you want to apply the GSLB rule."
+msgstr ""
+
+#: ../../networking2.rst:3220
+# 2ab62b2492a3407ca085e8666b106fa4
+msgid "Assigning Load Balancing Rules to GSLB"
+msgstr ""
+
+#: ../../networking2.rst:3240
+# 7c5601cd6ce640e8b5dc8a45589bad59
+msgid "Select the desired GSLB."
+msgstr ""
+
+#: ../../networking2.rst:3244
+# cf5bad08cdb4408c83d7b139e0c64547
+msgid "Click view assigned load balancing."
+msgstr ""
+
+#: ../../networking2.rst:3248
+# e8ee6a81561b4140a5fc1b69a76cc736
+msgid "Click assign more load balancing."
+msgstr ""
+
+#: ../../networking2.rst:3252
+# 645c7738ea8643bb8dc363416867e170
+msgid "Select the load balancing rule you have created for the zone."
+msgstr ""
+
+#: ../../networking2.rst:3259
+# 607875c969314174b33d5ffe591d6d01
+msgid "Known Limitation"
+msgstr ""
+
+#: ../../networking2.rst:3261
+# 7b4f744d0ba14d0793259da18acaa8e4
+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 ""
+
+#: ../../networking2.rst:3266
+# 07d2c270666b4ce5b27e2329f4a46336
+msgid "Guest IP Ranges"
+msgstr ""
+
+#: ../../networking2.rst:3268
+# 5ba35a4bec1d4cd086d34463a8fd3b26
+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 ""
+
+#: ../../networking2.rst:3273
+# 24793eb079054dad8ef15f9ce2ce53ad
+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 ""
+
+#: ../../networking2.rst:3280
+# 1a16911ddff840da827812b45ff09025
+msgid "Acquiring a New IP Address"
+msgstr ""
+
+#: ../../networking2.rst:3308
+# 2959313cb3534153848362cb02ce12c0
+msgid "If you want Portable IP click Yes in the confirmation dialog. If you want a normal Public IP click No."
+msgstr ""
+
+#: ../../networking2.rst:3311
+# 83e09cc7cc8940f6aa9b890d0011f628
+msgid "For more information on Portable IP, see `\"Portable IPs\" <#portable-ips>`_."
+msgstr ""
+
+#: ../../networking2.rst:3319
+# e238190f4d8f4177ac72494fa5eb1d72
+msgid "Releasing an IP Address"
+msgstr ""
+
+#: ../../networking2.rst:3321
+# 84c5bd1b7c19450b9c9a23243730fa62
+msgid "When the last rule for an IP address is removed, you can release that IP address. The IP address still belongs to the VPC; however, it can be picked up for any guest network again."
+msgstr ""
+
+#: ../../networking2.rst:3343
+# cf51c9fcec0b45fa99f4d7aeeb1b1c06
+msgid "Click the IP address you want to release."
+msgstr ""
+
+#: ../../networking2.rst:3347
+# e09fbcc9c5114e19a679764fe1714c1a
+msgid "Click the Release IP button. |ReleaseIPButton.png|"
+msgstr ""
+
+#: ../../networking2.rst:3351
+#: ../../networking2.rst:3923
+#: ../../networking2.rst:4395
+#: ../../networking2.rst:4495
+#: ../../networking2.rst:4687
+#: ../../networking2.rst:5291
+#: ../../networking2.rst:5550
+#: ../../networking2.rst:5876
+#: ../../networking2.rst:5963
+#: ../../networking2.rst:6055
+#: ../../networking2.rst:6298
+#: ../../networking2.rst:6692
+# a1e27ff808d74a1ca5f49c2d72593b00
+# c329d8910228495faeb8d66b4e61c0b6
+# f699725aeceb41beb4bd661924beb0fe
+# b55b701c8a634f42a9019c46b5f7a204
+# 7c788a2a5d3640c99e8cc0ae99940251
+# 160c7d49caad47f7ae0c0b2f98aff672
+# 37a5880aa697458fb42243e1e26fc671
+# 8980bc62961847a7bb55dc12efac6df7
+# 1918561df94f4fa4bfa406d4ed4cd1a1
+# b5960db5e5104fafa693db42db76ba47
+# 9cd72aa996794ce4bd207159d1fa8742
+# abe42da7383441778d0131125e8ff6c8
+msgid "Static NAT"
+msgstr ""
+
+#: ../../networking2.rst:3353
+# b1f96220fd994b41b5fa5fdebccab0b4
+msgid "A static NAT rule maps a public IP address to the private IP address of a VM in order to allow Internet traffic into the VM. The public IP address always remains the same, which is why it is called “static†NAT. This section tells how to enable or disable static NAT for a particular IP address."
+msgstr ""
+
+#: ../../networking2.rst:3360
+# d98473b1ef2041a7877e6841336bbe2f
+msgid "Enabling or Disabling Static NAT"
+msgstr ""
+
+#: ../../networking2.rst:3362
+#: ../../networking2.rst:6014
+# 66e31a75defd4e2e88802eaa37a23902
+# 507d4788f25d423c84d95132346afd2b
+msgid "If port forwarding rules are already in effect for an IP address, you cannot enable static NAT to that IP."
+msgstr ""
+
+#: ../../networking2.rst:3365
+#: ../../networking2.rst:6017
+# 28d0504840374a70bd1ec4eab3c57295
+# dd68e0b051b34d709557d0f739c568ac
+msgid "If a guest VM is part of more than one network, static NAT rules will function only if they are defined on the default network."
+msgstr ""
+
+#: ../../networking2.rst:3386
+#: ../../networking2.rst:3460
+# 4f6ac41af4434f21b7bbb61428e5bd46
+# 6f85b85b1cd24dbeb7fffdbd01f0afa2
+msgid "Click the IP address you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:3390
+# 326984a3cc3446ed806cf614b48f5841
+msgid "Click the Static NAT |enabledisablenat.png| button."
+msgstr ""
+
+#: ../../networking2.rst:3393
+# a372a7da12b54432889a1a60bab4be8a
+msgid "The button toggles between Enable and Disable, depending on whether static NAT is currently enabled for the IP address."
+msgstr ""
+
+#: ../../networking2.rst:3398
+# 78c5d4edd8db44cf9d448e10f2a89813
+msgid "If you are enabling static NAT, a dialog appears where you can choose the destination VM and click Apply."
+msgstr ""
+
+#: ../../networking2.rst:3402
+# 88e457a0ae3145f49ab4f361af8d4a4a
+msgid "IP Forwarding and Firewalling"
+msgstr ""
+
+#: ../../networking2.rst:3404
+# 9abca0c542c1441f8b116871bcce046d
+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 ""
+
+#: ../../networking2.rst:3407
+# 1dd28301d9264826b4c64d6f13edf77f
+msgid "To allow outgoing traffic, follow the procedure in :ref:`egress-fw-rules`."
+msgstr ""
+
+#: ../../networking2.rst:3409
+# 35f67e1320f941ac85f0fbb87f8fb385
+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 ""
+
+#: ../../networking2.rst:3418
+# 9229b4cb0661463cab6efc5582184abc
+msgid "Firewall Rules"
+msgstr ""
+
+#: ../../networking2.rst:3420
+# d51a292426874329a0951777c1772476
+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 ""
+
+#: ../../networking2.rst:3426
+# 59963a8e5da34833bc437796df5d300c
+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 ""
+
+#: ../../networking2.rst:3431
+# f9d2eb76396f4589896d0f4797e8c77b
+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 ""
+
+#: ../../networking2.rst:3434
+# ee967d9902434ce68b69c49226492070
+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 ""
+
+#: ../../networking2.rst:3440
+# 9ceb40041acc44ed8cb1dbd759ffa528
+msgid "To create a firewall rule:"
+msgstr ""
+
+#: ../../networking2.rst:3464
+# c2c48ea9ba7d4778bc6bc6820adf83f0
+msgid "Click the Configuration tab and fill in the following values."
+msgstr ""
+
+#: ../../networking2.rst:3468
+# f889ae51ce804cde9da76459ef8ca9f6
+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 ""
+
+#: ../../networking2.rst:3475
+# 036b027b27144215b7da6ad75fa7c68e
+msgid "**Protocol**. The communication protocol in use on the opened port(s)."
+msgstr ""
+
+#: ../../networking2.rst:3480
+# d8ab296b3ccd4f159dba1554303104e4
+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 ""
+
+#: ../../networking2.rst:3486
+# 45ba206ce4584c259c3d086badc5d9dc
+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 ""
+
+#: ../../networking2.rst:3498
+# 83c407ae9e1d47c5a3a71b8e00327dee
+msgid "Egress Firewall Rules in an Advanced Zone"
+msgstr ""
+
+#: ../../networking2.rst:3500
+# 5c422781131a4989a954e4495b8e8630
+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 rules are removed the default policy, Block, is applied."
+msgstr ""
+
+#: ../../networking2.rst:3512
+# 9feacce2e10b4e7890c88a3bcc0a75fa
+msgid "Consider the following scenarios to apply egress firewall rules:"
+msgstr ""
+
+#: ../../networking2.rst:3516
+# 2fbbeae49f87458890dd0c859e95d758
+msgid "Egress firewall rules are supported on Juniper SRX and virtual router."
+msgstr ""
+
+#: ../../networking2.rst:3521
+# 4559d85d3913439095bf17b9b34c926e
+msgid "The egress firewall rules are not supported on shared networks."
+msgstr ""
+
+#: ../../networking2.rst:3525
+# 83d00a1385a048c1a78d6ff81e6d2c18
+msgid "Allow the egress traffic from specified source CIDR. The Source CIDR is part of guest network CIDR."
+msgstr ""
+
+#: ../../networking2.rst:3530
+# 958ef1560ca04b98b84aad9240aa503e
+msgid "Allow the egress traffic with protocol TCP,UDP,ICMP, or ALL."
+msgstr ""
+
+#: ../../networking2.rst:3534
+# 07016fef8ef94149b04668cd6107f2a4
+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 ""
+
+#: ../../networking2.rst:3539
+# d4588055cabf49ef8eb1caa7313a181a
+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 ""
+
+#: ../../networking2.rst:3544
+# 73084bef40134e449ffe9d78b00d3ba2
+msgid "Configuring an Egress Firewall Rule"
+msgstr ""
+
+#: ../../networking2.rst:3556
+# eed98622c7604cfa83eec241a54202d7
+msgid "In Select view, choose Guest networks, then click the Guest network you want."
+msgstr ""
+
+#: ../../networking2.rst:3561
+# 8d5d5eaa44ef455786d9d7d6a412826e
+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 ""
+
+#: ../../networking2.rst:3565
+# 615b7e1b5d4a4afba201cbd868ebcae4
+msgid "|egress-firewall-rule.png|"
+msgstr ""
+
+#: ../../networking2.rst:3569
+# 3b0e293e06344c648450ac61d33c6e86
+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 ""
+
+#: ../../networking2.rst:3577
+# a81a39ae46914bcbb4b99900eb016883
+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 ""
+
+#: ../../networking2.rst:3584
+# cf939bab32ca4167afcce4eddff3015e
+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 ""
+
+#: ../../networking2.rst:3590
+# 12c38b633f1f4796af7e5704d6128627
+msgid "**ICMP Type, ICMP Code**: (ICMP only) The type of message and error code that are sent."
+msgstr ""
+
+#: ../../networking2.rst:3598
+# 2cd26bb0b191473db9267cd6ec1492e7
+msgid "Configuring the Default Egress Policy"
+msgstr ""
+
+#: ../../networking2.rst:3600
+# 68762a16d8b94ae298a95f68573272e3
+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 ""
+
+#: ../../networking2.rst:3608
+# 1113d91089884de2966c0431459b50af
+msgid "You have two options: Allow and Deny."
+msgstr ""
+
+#: ../../networking2.rst:3611
+# 675178fcb7144053a9b257ebdc760670
+msgid "Allow"
+msgstr ""
+
+#: ../../networking2.rst:3613
+# db1c618c19734644b9f8f3714393f25c
+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 ""
+
+#: ../../networking2.rst:3620
+#: ../../networking2.rst:5253
+#: ../../networking2.rst:5254
+# cd74f40051e845018f993bc3377272b7
+# ada70d776fb44fff9ae52224ac02290a
+# 6870c74dca5142b0a048f825f2f357dc
+msgid "Deny"
+msgstr ""
+
+#: ../../networking2.rst:3622
+# 8766188244b541e08448f923693d31d9
+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 ""
+
+#: ../../networking2.rst:3629
+# 57f1dde63b4949e5a229d6af14593571
+msgid "This feature is supported only on virtual router and Juniper SRX."
+msgstr ""
+
+#: ../../networking2.rst:3633
+# a711b3baa28c4e3fa0ee4a98adacfcc8
+msgid "Create a network offering with your desirable default egress policy:"
+msgstr ""
+
+#: ../../networking2.rst:3637
+# c311057000004a4bb96e882cffcc28ce
+msgid "Log in with admin privileges to the CloudStack UI."
+msgstr ""
+
+#: ../../networking2.rst:3641
+# 25106537239545dc82409a24f0e06bd6
+msgid "In the left navigation bar, click Service Offerings."
+msgstr ""
+
+#: ../../networking2.rst:3645
+# 9289d78fd54546e3ac890ba5e790db43
+msgid "In Select Offering, choose Network Offering."
+msgstr ""
+
+#: ../../networking2.rst:3649
+#: ../../networking2.rst:6181
+#: ../../networking2.rst:6486
+# 09e3077c1dd044d899bb41898736a9b2
+# f6c2630b089b4f4ab8805c97a1cae4af
+# e7fccdf8282c4f6c8d7a6e5836840c19
+msgid "Click Add Network Offering."
+msgstr ""
+
+#: ../../networking2.rst:3653
+# 9c68f5258ad84445be883d57d0570c1e
+msgid "In the dialog, make necessary choices, including firewall provider."
+msgstr ""
+
+#: ../../networking2.rst:3658
+# cc2848c801fa426abd8304928f336162
+msgid "In the Default egress policy field, specify the behaviour."
+msgstr ""
+
+#: ../../networking2.rst:3666
+# a536099bc33f41dca54d66a4d01bd083
+msgid "Create an isolated network by using this network offering."
+msgstr ""
+
+#: ../../networking2.rst:3668
+# 4d9a8aef2dad4881b4fc8e1396be6aa2
+msgid "Based on your selection, the network will have the egress public traffic blocked or allowed."
+msgstr ""
+
+#: ../../networking2.rst:3672
+# fbdeecae49e641c1b71f8f62cb19d1e8
+msgid "Port Forwarding"
+msgstr ""
+
+#: ../../networking2.rst:3674
+# 242ca59ae1ec44818bf282c05c1a6171
+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 ""
+
+#: ../../networking2.rst:3682
+# 6d1f9b4d8e6d4fe090b4bbf4f93459bd
+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 ""
+
+#: ../../networking2.rst:3687
+# 0986f075d3ae43e980cfa47acdab6ffe
+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 ""
+
+#: ../../networking2.rst:3691
+# 31bccf868e794f2cbdddcca69224bad3
+msgid "To set up port forwarding:"
+msgstr ""
+
+#: ../../networking2.rst:3699
+# 16dcd6a5ef644770900cdcce80794c67
+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 ""
+
+#: ../../networking2.rst:3705
+# 3bd594ec854b43b583f5c33092e99657
+msgid "Add one or more VM instances to CloudStack."
+msgstr ""
+
+#: ../../networking2.rst:3709
+# 67e6520d95a749bca1dfd8ee7d653c61
+msgid "In the left navigation bar, click Network."
+msgstr ""
+
+#: ../../networking2.rst:3713
+# 8ec41137f3064dbf9b135e9131c01078
+msgid "Click the name of the guest network where the VMs are running."
+msgstr ""
+
+#: ../../networking2.rst:3717
+# edc2c92eb5c940938babba424e0ab0a7
+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 ""
+
+#: ../../networking2.rst:3724
+# 94e2eab0e63b4fc3857c9bd41223a42c
+msgid "Click the Configuration tab."
+msgstr ""
+
+#: ../../networking2.rst:3728
+#: ../../networking2.rst:6733
+# 44faf09e38934875bdb4123f711051b7
+# 5bd7a3feb2a74eedb79b444a48452c5d
+msgid "In the Port Forwarding node of the diagram, click View All."
+msgstr ""
+
+#: ../../networking2.rst:3736
+# f513170f116e42d98255397872cd84b2
+msgid "**Public Port**. The port to which public traffic will be addressed on the IP address you acquired in the previous step."
+msgstr ""
+
+#: ../../networking2.rst:3741
+# 1e1f06ab8e7d4b228f0671927b1d37b7
+msgid "**Private Port**. The port on which the instance is listening for forwarded public traffic."
+msgstr ""
+
+#: ../../networking2.rst:3746
+# b96619b413e4435494d46e6c18e985b6
+msgid "**Protocol**. The communication protocol in use between the two ports"
+msgstr ""
+
+#: ../../networking2.rst:3754
+# 189bbad94193454d80e285996b14f052
+msgid "IP Load Balancing"
+msgstr ""
+
+#: ../../networking2.rst:3756
+# 8bb4fc89584047a4979eb7ade38555ac
+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 ""
+
+#: ../../networking2.rst:3762
+#: ../../networking2.rst:6371
+#: ../../networking2.rst:6644
+# 2d62543390a44d9b86be0973a26237e3
+# 71d3f562cf68451d95abf2e2855c938f
+# a91ad3d092144bad9c7c61b4fae3c2e9
+msgid "Round-robin"
+msgstr ""
+
+#: ../../networking2.rst:3766
+# 8fd8ce7230194556b444745abd07c778
+msgid "Least connection"
+msgstr ""
+
+#: ../../networking2.rst:3770
+# 5f1fa380f5a1493cbb22ae41bd77eab0
+msgid "Source IP"
+msgstr ""
+
+#: ../../networking2.rst:3772
+# e337b776e21743439b7207bfb4c76b76
+msgid "This is similar to port forwarding but the destination may be multiple IP addresses."
+msgstr ""
+
+#: ../../networking2.rst:3776
+# 348ae44471844fa39d0776a54c21522c
+msgid "DNS and DHCP"
+msgstr ""
+
+#: ../../networking2.rst:3778
+# e9f3ca6c9e6f429bb4fe851ef31d2037
+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 ""
+
+#: ../../networking2.rst:3783
+# dd8cfae4c4df4db5abe405b9fc23f91c
+msgid "Remote Access VPN"
+msgstr ""
+
+#: ../../networking2.rst:3785
+# 421361e0532246a2b00b1aabc0663fa7
+msgid "CloudStack account owners can create virtual private networks (VPN) to access their virtual machines. If the guest network is instantiated from a network offering that offers the Remote Access VPN service, the virtual router (based on the System VM) is used to provide the service. CloudStack provides a L2TP-over-IPsec-based remote access VPN service to guest virtual networks. Since each network gets its own virtual router, VPNs are not shared across the networks. VPN clients native to Windows, Mac OS X and iOS can be used to connect to the guest networks. The account owner can create and manage users for their VPN. CloudStack does not use its account database for this purpose but uses a separate table. The VPN user database is shared across all the VPNs created by the account owner. All VPN users get access to all VPNs created by the account owner."
+msgstr ""
+
+#: ../../networking2.rst:3800
+# a732cf37468141f3b91c785a8153d60d
+msgid "Make sure that not all traffic goes through the VPN. That is, the route installed by the VPN should be only for the guest network and not for all traffic."
+msgstr ""
+
+#: ../../networking2.rst:3806
+# 4dbb5c3287b64cd5abc3987f02c48b48
+msgid "**Road Warrior / Remote Access**. Users want to be able to connect securely from a home or office to a private network in the cloud. Typically, the IP address of the connecting client is dynamic and cannot be preconfigured on the VPN server."
+msgstr ""
+
+#: ../../networking2.rst:3813
+# eb6134e7170946da9f096bcd062d7aad
+msgid "**Site to Site**. In this scenario, two private subnets are connected over the public Internet with a secure VPN tunnel. The cloud user's subnet (for example, an office network) is connected through a gateway to the network in the cloud. The address of the user's gateway must be preconfigured on the VPN server in the cloud. Note that although L2TP-over-IPsec can be used to set up Site-to-Site VPNs, this is not the primary intent of this feature. For more information, see \":ref:`setting-s2s-vpn-conn`\"."
+msgstr ""
+
+#: ../../networking2.rst:3823
+# 7dd56949a6f74a439a60c07ad67f722a
+msgid "Configuring Remote Access VPN"
+msgstr ""
+
+#: ../../networking2.rst:3825
+# 0061faa9e6cd4ad59954ed3c0856b411
+msgid "To set up VPN for the cloud:"
+msgstr ""
+
+#: ../../networking2.rst:3833
+# 0e3ff971fa3d4442848a972f64282837
+msgid "In the left navigation, click Global Settings."
+msgstr ""
+
+#: ../../networking2.rst:3837
+# c2fc515f4e564cf48108c56364709b7b
+msgid "Set the following global configuration parameters."
+msgstr ""
+
+#: ../../networking2.rst:3841
+# 6e225aa038964885a007931b82b18986
+msgid "remote.access.vpn.client.ip.range - The range of IP addresses to be allocated to remote access VPN clients. The first IP in the range is used by the VPN server."
+msgstr ""
+
+#: ../../networking2.rst:3847
+# 1639d05b22d9481b8b92fc8a707d027a
+msgid "remote.access.vpn.psk.length - Length of the IPSec key."
+msgstr ""
+
+#: ../../networking2.rst:3851
+# d8c75e5dc742435ca19c4a06e2a61ecd
+msgid "remote.access.vpn.user.limit - Maximum number of VPN users per account."
+msgstr ""
+
+#: ../../networking2.rst:3854
+# 3f55599605614d13a5e11b6eb4a74bfa
+msgid "To enable VPN for a particular network:"
+msgstr ""
+
+#: ../../networking2.rst:3858
+#: ../../networking2.rst:3894
+# 37b4e592dd084399a75751ec656055ca
+# f5662606b3e94deaa8d00053c5b1f843
+msgid "Log in as a user or administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../networking2.rst:3862
+#: ../../networking2.rst:3898
+# c949dee3a72b40e1aa492da5a563a3bf
+# b4fa7486bbc9431d8834b563df517c52
+msgid "In the left navigation, click Network."
+msgstr ""
+
+#: ../../networking2.rst:3866
+# 89d5b593db5e47e4b8d8ba9343bb9a81
+msgid "Click the name of the network you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:3874
+# 7f1c96aff09c4aca89166670c00e135b
+msgid "Click one of the displayed IP address names."
+msgstr ""
+
+#: ../../networking2.rst:3878
+#: ../../networking2.rst:3963
+# c037fe41e67e44569c8ef9d9ed2c87de
+# 0b7e6681912942398e9b55f50db5fabb
+msgid "Click the Enable VPN button. |vpn-icon.png|"
+msgstr ""
+
+#: ../../networking2.rst:3880
+# d8ac0fa0cc1f430ab2dabd3976e35a13
+msgid "The IPsec key is displayed in a popup window."
+msgstr ""
+
+#: ../../networking2.rst:3883
+# 3b6c749a19ac411e85a91bebde5620ac
+msgid "Configuring Remote Access VPN in VPC"
+msgstr ""
+
+#: ../../networking2.rst:3885
+# 24849989ce59453cb53461958b872d24
+msgid "On enabling Remote Access VPN on a VPC, any VPN client present outside the VPC can access VMs present in the VPC by using the Remote VPN connection. The VPN client can be present anywhere except inside the VPC on which the user enabled the Remote Access VPN service."
+msgstr ""
+
+#: ../../networking2.rst:3890
+# 9fe0ef310ce946a4b81eb99779e7d6e2
+msgid "To enable VPN for a VPC:"
+msgstr ""
+
+#: ../../networking2.rst:3902
+#: ../../networking2.rst:4370
+#: ../../networking2.rst:4467
+#: ../../networking2.rst:4658
+#: ../../networking2.rst:5074
+#: ../../networking2.rst:5139
+#: ../../networking2.rst:5270
+#: ../../networking2.rst:5352
+#: ../../networking2.rst:5521
+#: ../../networking2.rst:5760
+#: ../../networking2.rst:5851
+#: ../../networking2.rst:5939
+#: ../../networking2.rst:6030
+#: ../../networking2.rst:6273
+#: ../../networking2.rst:6583
+#: ../../networking2.rst:6667
+#: ../../networking2.rst:6792
+#: ../../networking2.rst:6831
+# a35416d0aa534a0786c5008000fd8e43
+# e9f7b5e6165a407b8c8f26dbd4564cea
+# 70b305de6a494311b862c80f66aec1ce
+# 77e179e8fd184282bca07276311f4193
+# c258a12f71d44428b74e9dace4023355
+# e34ba66fcef1410680e2597a9d2a8954
+# 2becfb5ca8464b0486c1fe7c82b5a4e3
+# 0712e1bd6b914f2885daf1e5febb7442
+# 97c2acefafb34f709fcc84b7a4dc40b9
+# b527a3e4798548ab91c07365a835ea9c
+# 3e347e3728d44b79a3475adb8b0600f2
+# b12fa2f420ac47059eb47eb95abebe58
+# 27fcf04f38494625a2efecfad5de2f9c
+# 9f39d7e9da4d40e5be4cbf6b4666758a
+# f624d82ab7e649288e146d0cebab16e0
+# 1895dd237c1341b295430829d5c5950c
+# f40ec8edcf6f46ff93c1db49b2d59307
+# 0eb2cf52b2f144dfb78982d1caa03b35
+msgid "In the Select view, select VPC."
+msgstr ""
+
+#: ../../networking2.rst:3904
+#: ../../networking2.rst:4372
+#: ../../networking2.rst:4660
+#: ../../networking2.rst:5272
+#: ../../networking2.rst:5354
+#: ../../networking2.rst:5523
+#: ../../networking2.rst:5762
+#: ../../networking2.rst:5853
+#: ../../networking2.rst:5941
+#: ../../networking2.rst:6032
+#: ../../networking2.rst:6275
+#: ../../networking2.rst:6585
+#: ../../networking2.rst:6669
+#: ../../networking2.rst:6833
+# ec4a1f9371cd43e39a21d45da9e513e9
+# 903528c98fb6402081d0c518396e4d5a
+# 02c81362a5294fe885a28cc0abe9f5a9
+# 8449bcf110af4969aeb6172fafda2205
+# a213eb463b5c421bbd5a602580f1b51a
+# 32bed119537345e7aa5c1f4d2ec728a5
+# f826c1e8499f44a7b886ac07bbeb0b5f
+# e3d9e5ecc1964bd880bc814a1c8a935b
+# 0d0c7e45230d4a7bb6d548c856fa8f7a
+# f4df1631caf646afad3bba723757c066
+# e30097b3b31c4398bab851342cc05e17
+# f26cae26e34e447e86996448bd94ee59
+# 5e20c449bba64885af814ea48d956e2c
+# ac7881d3dc5743a1baad101ab5045e35
+msgid "All the VPCs that you have created for the account is listed in the page."
+msgstr ""
+
+#: ../../networking2.rst:3909
+#: ../../networking2.rst:5277
+#: ../../networking2.rst:5359
+# 7b4b5acd29144a01a92211053af28180
+# 8993b44d5f7c418aafe0163c0dc2f320
+# 1c850ec226f5448797b19cee4f4bbdda
+msgid "Click the Configure button of the VPC."
+msgstr ""
+
+#: ../../networking2.rst:3911
+#: ../../networking2.rst:4383
+#: ../../networking2.rst:4483
+#: ../../networking2.rst:4675
+#: ../../networking2.rst:5279
+#: ../../networking2.rst:6286
+#: ../../networking2.rst:6680
+# 41f127a431e44ea1af73a4efd93d50dd
+# 4663a4f2b9d749bdaa308b9c71f6625a
+# 6517ef547f114583b55ea471ddfa3e96
+# f95ad4b883994ccab44a025f2b50f7e7
+# 8e35937d2ca84fa6905cf264caabfb6b
+# b7d205c295044f38ad749b9b58a45281
+# c33a19c6331843fca695c025eef65638
+msgid "For each tier, the following options are displayed:"
+msgstr ""
+
+#: ../../networking2.rst:3915
+#: ../../networking2.rst:4387
+#: ../../networking2.rst:4487
+#: ../../networking2.rst:4679
+#: ../../networking2.rst:5283
+#: ../../networking2.rst:5542
+#: ../../networking2.rst:5868
+#: ../../networking2.rst:5955
+#: ../../networking2.rst:6047
+#: ../../networking2.rst:6290
+#: ../../networking2.rst:6684
+# d36b5f8182cf4512aadad3221d7dd83d
+# dc877a54fec94d7cae1f81bdb0023b94
+# 8a8bdc30b2174cacbb572f5ad4c98a7b
+# 1b988edb0d8e4314a7eb8c37c3cfbf77
+# c30de8bbacbe4334a9b05a16ff351461
+# df7817d8060843d69314130c722fe9b6
+# c68c4a643bc0413a811ad7a01bfdc606
+# 0166943624e64d68860eafa9e58ab9bd
+# d21582e266e543afb57737fda85467b5
+# 6fa5c9555c7e46ac9ef191dd4173f8da
+# e6cdbca9e85d47b9b042e1f0310461fe
+msgid "Internal LB"
+msgstr ""
+
+#: ../../networking2.rst:3919
+#: ../../networking2.rst:4391
+#: ../../networking2.rst:4491
+#: ../../networking2.rst:4683
+#: ../../networking2.rst:5287
+#: ../../networking2.rst:5546
+#: ../../networking2.rst:5872
+#: ../../networking2.rst:5959
+#: ../../networking2.rst:6051
+#: ../../networking2.rst:6294
+#: ../../networking2.rst:6688
+# 6fa74bd617c04d698de6f38bf2416158
+# b4ec2750e056403ab30e230857867f11
+# 051be71f2d03468f854f32b5dfdb6439
+# e6dce01524cb4e9392a365a592674ec5
+# 3ac84bc009234f6a8e8a1f1caebe83a1
+# fc8ff98a80744b8a811a5f1c8f805de5
+# 7d23ee0ec36f41ed93929f00828f848d
+# 37dc837b902246d3855ec01eda4c0be2
+# 64590fae08ae4c8bbba1feb231077932
+# e77c1fc68625472b9ecf752fb5790551
+# 00a7eccc5d684130b79b1d1451b6390f
+msgid "Public LB IP"
+msgstr ""
+
+#: ../../networking2.rst:3927
+#: ../../networking2.rst:4399
+#: ../../networking2.rst:4499
+#: ../../networking2.rst:4691
+#: ../../networking2.rst:5295
+#: ../../networking2.rst:5554
+#: ../../networking2.rst:5880
+#: ../../networking2.rst:5967
+#: ../../networking2.rst:6059
+#: ../../networking2.rst:6302
+#: ../../networking2.rst:6696
+# fab3827cfc494ecd8b648f564a195172
+# 19cff60834f84a7b91d3dd25f4eff4f5
+# d38259f3d32d473980ccdef9d1689608
+# 0846fc98b6fc40eabb78391a7641f248
+# 14c417b19bdf4c3f8a22c9302c8edc7f
+# 11a737406efb4d0d987480bda52770e0
+# 65eadb3d777e4e10b89edf86e21a965e
+# d0731ebc92ab457d919264f55f94e1d8
+# ecfaad1840444dc5b5fc9fecfd3a5db8
+# f87032d442244dd9ace6770bd77cc552
+# 53d5237aaea24a448651d13727dcba17
+msgid "Virtual Machines"
+msgstr ""
+
+#: ../../networking2.rst:3933
+#: ../../networking2.rst:4405
+#: ../../networking2.rst:4505
+#: ../../networking2.rst:4697
+#: ../../networking2.rst:5301
+#: ../../networking2.rst:5560
+#: ../../networking2.rst:5886
+#: ../../networking2.rst:5973
+#: ../../networking2.rst:6065
+#: ../../networking2.rst:6308
+#: ../../networking2.rst:6702
+# 55332d391cdd468495ad76f952811577
+# 46bedbc30be240609724ff6eee13c73e
+# 78e5566733024d098b27e7a0ac093950
+# 4ffb5ac895d04c9bb052f07e28e82fa9
+# ba68a5eb30484d1ca76c23fc9bc74a09
+# 3dec4fac4a1446248f59d4ba0fe33666
+# afabe87fc2fc4de1bf89a7643d99ed17
+# 9d72e437059c43b39a0369449b50ce08
+# 58c6f2db6cff4dc49e7412bb20e7a01a
+# 23eee839c1c34752ac8eab15d0029064
+# 498838fb8fe040329abb978aea99f2be
+msgid "The following router information is displayed:"
+msgstr ""
+
+#: ../../networking2.rst:3937
+#: ../../networking2.rst:4409
+#: ../../networking2.rst:4509
+#: ../../networking2.rst:4701
+#: ../../networking2.rst:5305
+#: ../../networking2.rst:5564
+#: ../../networking2.rst:5890
+#: ../../networking2.rst:5977
+#: ../../networking2.rst:6069
+#: ../../networking2.rst:6312
+#: ../../networking2.rst:6706
+# c26c1853bc4f4277b2210032d9fb8c71
+# 0139a8b25d624810bd6bd843f489005e
+# 1a93bacd56834a9a8b5b28a8a7860331
+# 37f0f96d9ff840e2bc3edfce09290220
+# 361aba2c5dde45f78980a4afef525afe
+# c0a4cfa4e5fe4cc5a0ad6e9b742ba56c
+# 77a0686377bb4665b5d5069fb6b3ce35
+# 0a570734113f4de18e33b19bcf20dc8c
+# f55e6f457a684df2b425513b5ebb8f84
+# e04ebd7737dc4c5d905b4a2e898dd1dd
+# dac82df8dc6e4aeb9f668a0fce3839f7
+msgid "Private Gateways"
+msgstr ""
+
+#: ../../networking2.rst:3941
+#: ../../networking2.rst:4413
+#: ../../networking2.rst:4513
+#: ../../networking2.rst:4705
+#: ../../networking2.rst:5309
+#: ../../networking2.rst:5568
+#: ../../networking2.rst:5894
+#: ../../networking2.rst:5981
+#: ../../networking2.rst:6073
+#: ../../networking2.rst:6316
+#: ../../networking2.rst:6710
+# a9e24dfd29a3416d90e3051d7adbfd22
+# f868061634e14c84ad71294278a83859
+# 48ca230e37f745998e82d810cac0601f
+# 7e3d042b215f496eadd246802bc8d222
+# 5ff70875c6a34da991576fa2cb6c9383
+# e3012be55eb74fcf88d4ef4e6b761efd
+# e3050c23e81b4d149d94857d393c88e2
+# ddae1748531d48bbbdd4d197c05796fb
+# efeffe0be53f4e16a0484bfa29446228
+# 0b41ea343fdd486c8076aafd64b39af0
+# f3c278d0a4e1481da2d1684a5128a925
+msgid "Public IP Addresses"
+msgstr ""
+
+#: ../../networking2.rst:3945
+#: ../../networking2.rst:4417
+#: ../../networking2.rst:4517
+#: ../../networking2.rst:4709
+#: ../../networking2.rst:5313
+#: ../../networking2.rst:5572
+#: ../../networking2.rst:5898
+#: ../../networking2.rst:5985
+#: ../../networking2.rst:6077
+#: ../../networking2.rst:6320
+#: ../../networking2.rst:6714
+# 2e72f864a49742349a9ac3443b812ace
+# 34ef012f20b144bd90ebf24e0b12b44a
+# 5913d2bdbb4a4e53a3ac3b0298e92e49
+# 40012c7aa1ee4262bd10d91b96e8a9c9
+# 6f57a5bdf67e4cb58990f4d008083823
+# 853f28cafe0a4fc2891f7fabaae17a63
+# 3e495712a7e54c939d916fc98129d091
+# e3f120e5aaaf463c8ecc396d8abbd9d5
+# 97c98429541c4be592183749d007886c
+# 7a721c1ac43b4854b117cbce3eb74212
+# f91d27b21a40457eafd937a34be8e496
+msgid "Site-to-Site VPNs"
+msgstr ""
+
+#: ../../networking2.rst:3949
+#: ../../networking2.rst:4421
+#: ../../networking2.rst:4521
+#: ../../networking2.rst:4713
+#: ../../networking2.rst:5317
+#: ../../networking2.rst:5576
+#: ../../networking2.rst:5902
+#: ../../networking2.rst:5989
+#: ../../networking2.rst:6081
+#: ../../networking2.rst:6324
+#: ../../networking2.rst:6718
+# 349f95fa06f64797aff0edd3c925735e
+# 38e399fbd60f4bf5bf7ed82ae8ca8e0a
+# 5a4c91418b0a4ff99bb9831c5d46345b
+# 4f3ed50fa2084beab6f50bf893480074
+# 1e5d1d73bc104f34bcd1a3323e0735ef
+# 1191bcc81f424ae0b9582151a69b7c74
+# f62a78e753f344e1a9aa50099eea6317
+# b7b2d9ae13c340259dc2ccd54fd143d4
+# c450b0235bc74c36970ffde3fc943e02
+# 6e50d4714233432ca68b491f4d81721f
+# 86a0e3bd6be54e0a883c965b6aa369c8
+msgid "Network ACL Lists"
+msgstr ""
+
+#: ../../networking2.rst:3953
+#: ../../networking2.rst:6085
+#: ../../networking2.rst:6328
+#: ../../networking2.rst:6722
+# 4ea069860ba74bfdbaa2253dec4c494b
+# 13c12d90b1e84f96ad76cba5a47982c5
+# c218f564b23b41ea9e5193fb707b10fc
+# 82b5209e8daf48ef940f3188b13d1773
+msgid "In the Router node, select Public IP Addresses."
+msgstr ""
+
+#: ../../networking2.rst:3955
+#: ../../networking2.rst:5995
+#: ../../networking2.rst:6087
+#: ../../networking2.rst:6330
+#: ../../networking2.rst:6724
+# ba7c1886ce2f4ee2b912e553ebc3d61b
+# 0bfc7d4f8b8342789c24f18c3050712e
+# 580ba0ab2bca4c888e0a88e20bdbea27
+# d809889924b44274b70abfc5c5e45700
+# 25e20e9a574348cdaa22b580e2eda1e7
+msgid "The IP Addresses page is displayed."
+msgstr ""
+
+#: ../../networking2.rst:3959
+# b79d01255d3242b2bca0f5b82a3f42a7
+msgid "Click Source NAT IP address."
+msgstr ""
+
+#: ../../networking2.rst:3965
+# 124e19bc247541509add9967859dbd05
+msgid "Click OK to confirm. The IPsec key is displayed in a pop-up window."
+msgstr ""
+
+#: ../../networking2.rst:3967
+# d67e0d11d2a84def84932c99310a36fc
+msgid "Now, you need to add the VPN users."
+msgstr ""
+
+#: ../../networking2.rst:3971
+# b4de336c841f4553b07b5e167ffa4d21
+msgid "Click the Source NAT IP."
+msgstr ""
+
+#: ../../networking2.rst:3975
+# 4d3e59a6636142a4b87a1bc3e1114a0b
+msgid "Select the VPN tab."
+msgstr ""
+
+#: ../../networking2.rst:3979
+# 27ab772233bc45b3926b22bfac64318c
+msgid "Add the username and the corresponding password of the user you wanted to add."
+msgstr ""
+
+#: ../../networking2.rst:3988
+# 389210e40ce143f7a96d6c93a81f9f34
+msgid "Repeat the same steps to add the VPN users."
+msgstr ""
+
+#: ../../networking2.rst:3991
+# b3ada11c846b4cd9a7ea6de9608b48ed
+msgid "Using Remote Access VPN with Windows"
+msgstr ""
+
+#: ../../networking2.rst:3993
+# 4dacd242f3fc46b58f15b96d910b2a54
+msgid "The procedure to use VPN varies by Windows version. Generally, the user must edit the VPN properties and make sure that the default route is not the VPN. The following steps are for Windows L2TP clients on Windows Vista. The commands should be similar for other Windows versions."
+msgstr ""
+
+#: ../../networking2.rst:4000
+# e7a57a9061b640579542551d1c1a0a6a
+msgid "Log in to the CloudStack UI and click on the source NAT IP for the account. The VPN tab should display the IPsec preshared key. Make a note of this and the source NAT IP. The UI also lists one or more users and their passwords. Choose one of these users, or, if none exists, add a user and password."
+msgstr ""
+
+#: ../../networking2.rst:4008
+# d1fc77ea9ff74b79be7e81efd85d177a
+msgid "On the Windows box, go to Control Panel, then select Network and Sharing center. Click Setup a connection or network."
+msgstr ""
+
+#: ../../networking2.rst:4013
+# 7e4498aa4e0a4ebdafe3f2dab310a0f6
+msgid "In the next dialog, select No, create a new connection."
+msgstr ""
+
+#: ../../networking2.rst:4017
+# 90e3f9cc2fc740aca1edb2b0edc930f9
+msgid "In the next dialog, select Use my Internet Connection (VPN)."
+msgstr ""
+
+#: ../../networking2.rst:4021
+# 8e80995c739c4114ac013a88f71347e9
+msgid "In the next dialog, enter the source NAT IP from step #1 and give the connection a name. Check Don't connect now."
+msgstr ""
+
+#: ../../networking2.rst:4027
+# 2b3c410c5ec74b4eb6b7d269c04bdfb6
+msgid "In the next dialog, enter the user name and password selected in step #1."
+msgstr ""
+
+#: ../../networking2.rst:4036
+# 56b71e910d734f4b93b857548bcc867d
+msgid "Go back to the Control Panel and click Network Connections to see the new connection. The connection is not active yet."
+msgstr ""
+
+#: ../../networking2.rst:4041
+# 5032581f1fe042c1844ebad881b3d41a
+msgid "Right-click the new connection and select Properties. In the Properties dialog, select the Networking tab."
+msgstr ""
+
+#: ../../networking2.rst:4046
+# 23ee9538e54a49c39f87d22e2a8aae65
+msgid "In Type of VPN, choose L2TP IPsec VPN, then click IPsec settings. Select Use preshared key. Enter the preshared key from step #1."
+msgstr ""
+
+#: ../../networking2.rst:4051
+# e432bdf75f62482ab7522b9a120ab5b1
+msgid "The connection is ready for activation. Go back to Control Panel -> Network Connections and double-click the created connection."
+msgstr ""
+
+#: ../../networking2.rst:4056
+# fd7a739563464507bd2c37c2ad54953c
+msgid "Enter the user name and password from step #1."
+msgstr ""
+
+#: ../../networking2.rst:4059
+# aebae91f3d7c45eb9f3dd5fa89388da5
+msgid "Using Remote Access VPN with Mac OS X"
+msgstr ""
+
+#: ../../networking2.rst:4061
+# 580e45aef47e4d37846427f1b651a7e2
+msgid "First, be sure you've configured the VPN settings in your CloudStack install. This section is only concerned with connecting via Mac OS X to your VPN."
+msgstr ""
+
+#: ../../networking2.rst:4065
+# 093bbd04cdab4e429fd3a568f011382f
+msgid "Note, these instructions were written on Mac OS X 10.7.5. They may differ slightly in older or newer releases of Mac OS X."
+msgstr ""
+
+#: ../../networking2.rst:4070
+# 50d800b2cf72450f8bd890270e0e0ee6
+msgid "On your Mac, open System Preferences and click Network."
+msgstr ""
+
+#: ../../networking2.rst:4074
+# 3a1af061748d4e418eaaf8b5f8877f09
+msgid "Make sure Send all traffic over VPN connection is not checked."
+msgstr ""
+
+#: ../../networking2.rst:4078
+# ef3e10026dbb4d1798d2133b3e9c22dd
+msgid "If your preferences are locked, you'll need to click the lock in the bottom left-hand corner to make any changes and provide your administrator credentials."
+msgstr ""
+
+#: ../../networking2.rst:4084
+# 292ec3cfa46e48a9a541875456694b77
+msgid "You will need to create a new network entry. Click the plus icon on the bottom left-hand side and you'll see a dialog that says \"Select the interface and enter a name for the new service.\" Select VPN from the Interface drop-down menu, and \"L2TP over IPSec\" for the VPN Type. Enter whatever you like within the \"Service Name\" field."
+msgstr ""
+
+#: ../../networking2.rst:4092
+# 164c5574c52f41baabcf85d8a575f7fa
+msgid "You'll now have a new network interface with the name of whatever you put in the \"Service Name\" field. For the purposes of this example, we'll assume you've named it \"CloudStack.\" Click on that interface and provide the IP address of the interface for your VPN under the Server Address field, and the user name for your VPN under Account Name."
+msgstr ""
+
+#: ../../networking2.rst:4101
+# 581debc7245446b48e5e1c54984c711d
+msgid "Click Authentication Settings, and add the user's password under User Authentication and enter the pre-shared IPSec key in the Shared Secret field under Machine Authentication. Click OK."
+msgstr ""
+
+#: ../../networking2.rst:4107
+# 37bca241509a4e3198b5a084939f14e5
+msgid "You may also want to click the \"Show VPN status in menu bar\" but that's entirely optional."
+msgstr ""
+
+#: ../../networking2.rst:4112
+# 0cb9849a0685438b81bdcd0818eb6202
+msgid "Now click \"Connect\" and you will be connected to the CloudStack VPN."
+msgstr ""
+
+#: ../../networking2.rst:4117
+# 3bac353e80464ab9856af6e4cd87363e
+msgid "Setting Up a Site-to-Site VPN Connection"
+msgstr ""
+
+#: ../../networking2.rst:4119
+# 38ff1a3ce4164fa994abfc693aeaffec
+msgid "A Site-to-Site VPN connection helps you establish a secure connection from an enterprise datacenter to the cloud infrastructure. This allows users to access the guest VMs by establishing a VPN connection to the virtual router of the account from a device in the datacenter of the enterprise. You can also establish a secure connection between two VPC setups or high availability zones in your environment. Having this facility eliminates the need to establish VPN connections to individual VMs."
+msgstr ""
+
+#: ../../networking2.rst:4128
+# bcd63d9bd1044fcd99b0164249abc73b
+msgid "The difference from Remote VPN is that Site-to-site VPNs connects entire networks to each other, for example, connecting a branch office network to a company headquarters network. In a site-to-site VPN, hosts do not have VPN client software; they send and receive normal TCP/IP traffic through a VPN gateway."
+msgstr ""
+
+#: ../../networking2.rst:4134
+# 00b0a4bc2c4642a1844c93fbefe3d0d4
+msgid "The supported endpoints on the remote datacenters are:"
+msgstr ""
+
+#: ../../networking2.rst:4138
+# 39b1debdf4a34a63a316d90993e9826d
+msgid "Cisco ISR with IOS 12.4 or later"
+msgstr ""
+
+#: ../../networking2.rst:4142
+# e913039ba6aa428892f596416afe8630
+msgid "Juniper J-Series routers with JunOS 9.5 or later"
+msgstr ""
+
+#: ../../networking2.rst:4146
+# 2e26cd40d2ed445d8929a3a0c02a5751
+msgid "CloudStack virtual routers"
+msgstr ""
+
+#: ../../networking2.rst:4149
+# 049e25279dbc416c937b6fecf03e8e08
+msgid "In addition to the specific Cisco and Juniper devices listed above, the expectation is that any Cisco or Juniper device running on the supported operating systems are able to establish VPN connections."
+msgstr ""
+
+#: ../../networking2.rst:4153
+# e3328079c0ec42049907920ee99daf6e
+msgid "To set up a Site-to-Site VPN connection, perform the following:"
+msgstr ""
+
+#: ../../networking2.rst:4157
+# 29a806dda94c425ab905caa5f7709805
+msgid "Create a Virtual Private Cloud (VPC)."
+msgstr ""
+
+#: ../../networking2.rst:4159
+# 7adc784ea1124f6f8fca7553c17ca916
+msgid "See \":ref:`configuring-vpc`\"."
+msgstr ""
+
+#: ../../networking2.rst:4163
+# 9649c39af37946ccbc1cba0e6b044fda
+msgid "Create a VPN Customer Gateway."
+msgstr ""
+
+#: ../../networking2.rst:4167
+# 27873ddb52d14bef9f93d4c83fc88464
+msgid "Create a VPN gateway for the VPC that you created."
+msgstr ""
+
+#: ../../networking2.rst:4171
+# 43ca7677d7b844209b1c70d588741934
+msgid "Create VPN connection from the VPC VPN gateway to the customer VPN gateway."
+msgstr ""
+
+#: ../../networking2.rst:4175
+# 232821d4f81947f1885a8e8355905d9d
+msgid "Creating and Updating a VPN Customer Gateway"
+msgstr ""
+
+#: ../../networking2.rst:4178
+# e0e6f58531f24a02852eb092cba35ff8
+msgid "A VPN customer gateway can be connected to only one VPN gateway at a time."
+msgstr ""
+
+#: ../../networking2.rst:4180
+# 95d554ca702946bca83b30c6adf6a445
+msgid "To add a VPN Customer Gateway:"
+msgstr ""
+
+#: ../../networking2.rst:4192
+#: ../../networking2.rst:4337
+# 46009b4629e8480591e1052e0a368962
+# d92d044f9c1f417cb5166046b62ef99a
+msgid "In the Select view, select VPN Customer Gateway."
+msgstr ""
+
+#: ../../networking2.rst:4196
+# 5b578ba46d8f4757aaf5620e6f77b1dc
+msgid "Click Add VPN Customer Gateway."
+msgstr ""
+
+#: ../../networking2.rst:4198
+# c3fa00baefd74a0eab971c38b2e19251
+msgid "|addvpncustomergateway.png|"
+msgstr ""
+
+#: ../../networking2.rst:4204
+# fd022a19e85d42918e285828af4c3698
+msgid "**Name**: A unique name for the VPN customer gateway you create."
+msgstr ""
+
+#: ../../networking2.rst:4208
+# 33ddd28d37da46f38c17f701efbd46d1
+msgid "**Gateway**: The IP address for the remote gateway."
+msgstr ""
+
+#: ../../networking2.rst:4212
+# a29af3f7a7934e4d88f2cd38dd8f70a1
+msgid "**CIDR list**: The guest CIDR list of the remote subnets. Enter a CIDR or a comma-separated list of CIDRs. Ensure that a guest CIDR list is not overlapped with the VPC's CIDR, or another guest CIDR. The CIDR must be RFC1918-compliant."
+msgstr ""
+
+#: ../../networking2.rst:4219
+# 4fdaac9ee4004de68ddbea33d37d1e43
+msgid "**IPsec Preshared Key**: Preshared keying is a method where the endpoints of the VPN share a secret key. This key value is used to authenticate the customer gateway and the VPC VPN gateway to each other."
+msgstr ""
+
+#: ../../networking2.rst:4225
+# 05946c6fb7bd4305bb2e20af004a01e3
+msgid "The IKE peers (VPN end points) authenticate each other by computing and sending a keyed hash of data that includes the Preshared key. If the receiving peer is able to create the same hash independently by using its Preshared key, it knows that both peers must share the same secret, thus authenticating the customer gateway."
+msgstr ""
+
+#: ../../networking2.rst:4234
+# b56b82f20e33400d8c4b39ce0b55bab2
+msgid "**IKE Encryption**: The Internet Key Exchange (IKE) policy for phase-1. The supported encryption algorithms are AES128, AES192, AES256, and 3DES. Authentication is accomplished through the Preshared Keys."
+msgstr ""
+
+#: ../../networking2.rst:4240
+# bd7c468509ca4ad5840e115efaa7e1ca
+msgid "The phase-1 is the first phase in the IKE process. In this initial negotiation phase, the two VPN endpoints agree on the methods to be used to provide security for the underlying IP traffic. The phase-1 authenticates the two VPN gateways to each other, by confirming that the remote gateway has a matching Preshared Key."
+msgstr ""
+
+#: ../../networking2.rst:4248
+# 13e9c659a1764d4fba7fc6de838ff8b1
+msgid "**IKE Hash**: The IKE hash for phase-1. The supported hash algorithms are SHA1 and MD5."
+msgstr ""
+
+#: ../../networking2.rst:4253
+# 23efa859bff14bc69f132fda62399cbe
+msgid "**IKE DH**: A public-key cryptography protocol which allows two parties to establish a shared secret over an insecure communications channel. The 1536-bit Diffie-Hellman group is used within IKE to establish session keys. The supported options are None, Group-5 (1536-bit) and Group-2 (1024-bit)."
+msgstr ""
+
+#: ../../networking2.rst:4261
+# 208ddb7be762449e9a6bb569f815f0ed
+msgid "**ESP Encryption**: Encapsulating Security Payload (ESP) algorithm within phase-2. The supported encryption algorithms are AES128, AES192, AES256, and 3DES."
+msgstr ""
+
+#: ../../networking2.rst:4266
+# b5dd17cc99c744d39b800b3df090e674
+msgid "The phase-2 is the second phase in the IKE process. The purpose of IKE phase-2 is to negotiate IPSec security associations (SA) to set up the IPSec tunnel. In phase-2, new keying material is extracted from the Diffie-Hellman key exchange in phase-1, to provide session keys to use in protecting the VPN data flow."
+msgstr ""
+
+#: ../../networking2.rst:4274
+# 0b0d1207149646f7b20a26a97a43f2d2
+msgid "**ESP Hash**: Encapsulating Security Payload (ESP) hash for phase-2. Supported hash algorithms are SHA1 and MD5."
+msgstr ""
+
+#: ../../networking2.rst:4279
+# 24ada2be8386490aafda31663e439f6f
+msgid "**Perfect Forward Secrecy**: Perfect Forward Secrecy (or PFS) is the property that ensures that a session key derived from a set of long-term public and private keys will not be compromised. This property enforces a new Diffie-Hellman key exchange. It provides the keying material that has greater key material life and thereby greater resistance to cryptographic attacks. The available options are None, Group-5 (1536-bit) and Group-2 (1024-bit). The security of the key exchanges increase as the DH groups grow larger, as does the time of the exchanges."
+msgstr ""
+
+#: ../../networking2.rst:4290
+# 7070c64276df4df0bf10b79718192550
+msgid "When PFS is turned on, for every negotiation of a new phase-2 SA the two gateways must generate a new set of phase-1 keys. This adds an extra layer of protection that PFS adds, which ensures if the phase-2 SA's have expired, the keys used for new phase-2 SA's have not been generated from the current phase-1 keying material."
+msgstr ""
+
+#: ../../networking2.rst:4298
+# 2ca89467ccc94df5a7bef6468f566b46
+msgid "**IKE Lifetime (seconds)**: The phase-1 lifetime of the security association in seconds. Default is 86400 seconds (1 day). Whenever the time expires, a new phase-1 exchange is performed."
+msgstr ""
+
+#: ../../networking2.rst:4304
+# 8ca35ecaf59e42cfbef7fe98bfd8f264
+msgid "**ESP Lifetime (seconds)**: The phase-2 lifetime of the security association in seconds. Default is 3600 seconds (1 hour). Whenever the value is exceeded, a re-key is initiated to provide a new IPsec encryption and authentication session keys."
+msgstr ""
+
+#: ../../networking2.rst:4311
+# f5df9d75cd524b5b92d8c85cce626655
+msgid "**Dead Peer Detection**: A method to detect an unavailable Internet Key Exchange (IKE) peer. Select this option if you want the virtual router to query the liveliness of its IKE peer at regular intervals. It's recommended to have the same configuration of DPD on both side of VPN connection."
+msgstr ""
+
+#: ../../networking2.rst:4322
+# d5d1124c4e124407a611667296f6ffac
+msgid "Updating and Removing a VPN Customer Gateway"
+msgstr ""
+
+#: ../../networking2.rst:4324
+# 04bbad214e7c4a6884dbfa7b6367b57d
+msgid "You can update a customer gateway either with no VPN connection, or related VPN connection is in error state."
+msgstr ""
+
+#: ../../networking2.rst:4341
+# 1ab9886431a14731ae0c50e12a2203d6
+msgid "Select the VPN customer gateway you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:4345
+# ba453f5b81544287922dde81efcc590b
+msgid "To modify the required parameters, click the Edit VPN Customer Gateway button |edit-icon.png|"
+msgstr ""
+
+#: ../../networking2.rst:4350
+# 46a97e97cc034e4e91727e4f784cc8b7
+msgid "To remove the VPN customer gateway, click the Delete VPN Customer Gateway button |delete.png|"
+msgstr ""
+
+#: ../../networking2.rst:4358
+# 60adfabe1723470599d91c8c7e4d173a
+msgid "Creating a VPN gateway for the VPC"
+msgstr ""
+
+#: ../../networking2.rst:4377
+#: ../../networking2.rst:4473
+#: ../../networking2.rst:4665
+#: ../../networking2.rst:5767
+#: ../../networking2.rst:5858
+#: ../../networking2.rst:6037
+#: ../../networking2.rst:6674
+# 3500ca75a83147c19f1ed28777444c7d
+# a64efaea89b24d67a8e4d1e4d36d34eb
+# ce5b35fdd4964dd398d49233e31b5fcd
+# 67bc60dd8b6046558a097762240decf1
+# 6c5213a6e5524a83bd5c41c59f290442
+# f25b37649f5d4cd5b04a737641c79d73
+# 5b21b4e1cb1045269d9814e3cc029bd0
+msgid "Click the Configure button of the VPC to which you want to deploy the VMs."
+msgstr ""
+
+#: ../../networking2.rst:4380
+#: ../../networking2.rst:4476
+#: ../../networking2.rst:4668
+#: ../../networking2.rst:5531
+#: ../../networking2.rst:5861
+#: ../../networking2.rst:5948
+#: ../../networking2.rst:6040
+#: ../../networking2.rst:6677
+# e1358ecd8ab54314873c0775c0880f75
+# 19d3fa0227e84261bf1cd4663828636e
+# 4de39a3991db4dfc901c6279c5294ac2
+# 1a2f3ce6a491468ab7a3459fcdfe215a
+# 469af671796348f5b92558710d159c36
+# c11ffe7f7c0949189706c0df2f2ff581
+# 94a0dea0d2b04ba797bfe1f2164cac7b
+# 30b175b156724a81b03bd2d42e85a0a1
+msgid "The VPC page is displayed where all the tiers you created are listed in a diagram."
+msgstr ""
+
+#: ../../networking2.rst:4425
+#: ../../networking2.rst:4525
+#: ../../networking2.rst:4717
+# 795d87a7e4884bc9954978635c4a0ce3
+# bfc77b95ba024e828af5e01a0235044f
+# c412e8677d9f43bd91d874297d2a51b1
+msgid "Select Site-to-Site VPN."
+msgstr ""
+
+#: ../../networking2.rst:4427
+# 8284273706754d38a31bf76d8261f3ed
+msgid "If you are creating the VPN gateway for the first time, selecting Site-to-Site VPN prompts you to create a VPN gateway."
+msgstr ""
+
+#: ../../networking2.rst:4432
+# 9403ca5a182a46bea09047c00af73183
+msgid "In the confirmation dialog, click Yes to confirm."
+msgstr ""
+
+#: ../../networking2.rst:4434
+# e4ae30f09bbb4771b8c6f422926370fd
+msgid "Within a few moments, the VPN gateway is created. You will be prompted to view the details of the VPN gateway you have created. Click Yes to confirm."
+msgstr ""
+
+#: ../../networking2.rst:4438
+# 92509e2b8fd34d06a5026dc84df93572
+msgid "The following details are displayed in the VPN Gateway page:"
+msgstr ""
+
+#: ../../networking2.rst:4446
+# 0d9b83c3c7c14ceb89902aa2acd77eef
+msgid "Account"
+msgstr ""
+
+#: ../../networking2.rst:4450
+# de092a05c0cb4352a757a99ec8ec10cc
+msgid "Domain"
+msgstr ""
+
+#: ../../networking2.rst:4453
+# f9de76d1de924804aada31d4d335a636
+msgid "Creating a VPN Connection"
+msgstr ""
+
+#: ../../networking2.rst:4455
+# 041a061561c240feb48418d06b345f9d
+msgid "CloudStack supports creating up to 8 VPN connections."
+msgstr ""
+
+#: ../../networking2.rst:4469
+# c343d040bbf94652805f9913087df284
+msgid "All the VPCs that you create for the account are listed in the page."
+msgstr ""
+
+#: ../../networking2.rst:4481
+#: ../../networking2.rst:4673
+#: ../../networking2.rst:5536
+# 6ab7b79bc9384d7e80adc871af997847
+# 49acb49a732346378816e6bb92cf285d
+# 02fa5743f59b45619d573323e28ba038
+msgid "Click the Settings icon."
+msgstr ""
+
+#: ../../networking2.rst:4527
+#: ../../networking2.rst:4719
+# fc6f5140f3c942dca23fcfd1ab68c6a7
+# 51c44ccda83c4464a1e80005c54790fc
+msgid "The Site-to-Site VPN page is displayed."
+msgstr ""
+
+#: ../../networking2.rst:4531
+#: ../../networking2.rst:4723
+# 786eac580afe4c91a9f86515ed758789
+# 17b40c7b7853452ea96b30e63059db2c
+msgid "From the Select View drop-down, ensure that VPN Connection is selected."
+msgstr ""
+
+#: ../../networking2.rst:4536
+# 163923e5fc7e45a9b9022496845d5da4
+msgid "Click Create VPN Connection."
+msgstr ""
+
+#: ../../networking2.rst:4538
+# 3755699dc4ef4c60846d045f671bfcee
+msgid "The Create VPN Connection dialog is displayed:"
+msgstr ""
+
+#: ../../networking2.rst:4540
+# 63e805ab6ce6420d97103dc7a20b5506
+msgid "|createvpnconnection.png|"
+msgstr ""
+
+#: ../../networking2.rst:4544
+# e897f05865fe4bf3b6daee5504dcf357
+msgid "Select the desired customer gateway."
+msgstr ""
+
+#: ../../networking2.rst:4548
+# cc72f3e20e344c9f8e3202d92866c9ce
+msgid "Select Passive if you want to establish a connection between two VPC virtual routers."
+msgstr ""
+
+#: ../../networking2.rst:4551
+# b1e77d6e88094abc8f1efc7fc737c62a
+msgid "If you want to establish a connection between two VPC virtual routers, select Passive only on one of the VPC virtual routers, which waits for the other VPC virtual router to initiate the connection. Do not select Passive on the VPC virtual router that initiates the connection."
+msgstr ""
+
+#: ../../networking2.rst:4561
+# e81cf6ee9dbe4cf8a512334ae708d8e0
+msgid "Within a few moments, the VPN Connection is displayed."
+msgstr ""
+
+#: ../../networking2.rst:4563
+# ceccd67800e84c5f86872fc8697f97d5
+msgid "The following information on the VPN connection is displayed:"
+msgstr ""
+
+#: ../../networking2.rst:4575
+# d7d71c18469c485d9cf0c62d4e18ee44
+msgid "State"
+msgstr ""
+
+#: ../../networking2.rst:4579
+# 7e17d8eed6e64a6bb98dfcc6688f7011
+msgid "IPSec Preshared Key"
+msgstr ""
+
+#: ../../networking2.rst:4583
+# 7698868ecfe742709ac2201b3c176a62
+msgid "IKE Policy"
+msgstr ""
+
+#: ../../networking2.rst:4587
+# f8b615756067468c82c8cc29bd97d4f6
+msgid "ESP Policy"
+msgstr ""
+
+#: ../../networking2.rst:4590
+# 2885f5a0b00e4f45bac61fa489576241
+msgid "Site-to-Site VPN Connection Between VPC Networks"
+msgstr ""
+
+#: ../../networking2.rst:4592
+# cffe70c20ec8443a93e09b3c742a055b
+msgid "CloudStack provides you with the ability to establish a site-to-site VPN connection between CloudStack virtual routers. To achieve that, add a passive mode Site-to-Site VPN. With this functionality, users can deploy applications in multiple Availability Zones or VPCs, which can communicate with each other by using a secure Site-to-Site VPN Tunnel."
+msgstr ""
+
+#: ../../networking2.rst:4598
+# 1a50c272367a482fb9fb4939f3e4baa1
+msgid "This feature is supported on all the hypervisors."
+msgstr ""
+
+#: ../../networking2.rst:4602
+# 2f0c1484f8594418b1f21b468680914a
+msgid "Create two VPCs. For example, VPC A and VPC B."
+msgstr ""
+
+#: ../../networking2.rst:4604
+# 2db40aa80b84423f9d304bb0b3745676
+msgid "For more information, see \":ref:`configuring-vpc`\"."
+msgstr ""
+
+#: ../../networking2.rst:4608
+# 8cbc2e0b316a42489765523577ab7e6a
+msgid "Create VPN gateways on both the VPCs you created."
+msgstr ""
+
+#: ../../networking2.rst:4610
+# c68bd6435db949d791a0372688848f1a
+msgid "For more information, see `\"Creating a VPN gateway for the VPC\" <#creating-a-vpn-gateway-for-the-vpc>`_."
+msgstr ""
+
+#: ../../networking2.rst:4615
+# f8b154e601404d4abdd3a9a4e6374500
+msgid "Create VPN customer gateway for both the VPCs."
+msgstr ""
+
+#: ../../networking2.rst:4617
+# 7e4fb977595840019e437c0884f0a8f1
+msgid "For more information, see `\"Creating and Updating a VPN Customer Gateway\" <#creating-and-updating-a-vpn-customer-gateway>`_."
+msgstr ""
+
+#: ../../networking2.rst:4622
+# ade608d3a3ea45829af36e650cd98e47
+msgid "Enable a VPN connection on VPC A in passive mode."
+msgstr ""
+
+#: ../../networking2.rst:4624
+# 7a5159ba5d354f659fa0b9c6291f9413
+msgid "For more information, see `\"Creating a VPN Connection\" <#creating-a-vpn-connection>`_."
+msgstr ""
+
+#: ../../networking2.rst:4627
+# 17674753d913496ea042cb7c2039383f
+msgid "Ensure that the customer gateway is pointed to VPC B. The VPN connection is shown in the Disconnected state."
+msgstr ""
+
+#: ../../networking2.rst:4632
+# d8feab6deab8404a9912bb7ea7882511
+msgid "Enable a VPN connection on VPC B."
+msgstr ""
+
+#: ../../networking2.rst:4634
+# 9234f47ff9fb4a4a86a85bcc6d518287
+msgid "Ensure that the customer gateway is pointed to VPC A. Because virtual router of VPC A, in this case, is in passive mode and is waiting for the virtual router of VPC B to initiate the connection, VPC B virtual router should not be in passive mode."
+msgstr ""
+
+#: ../../networking2.rst:4639
+# 85d2c38cd2d0427a833207d6c3b42087
+msgid "The VPN connection is shown in the Disconnected state."
+msgstr ""
+
+#: ../../networking2.rst:4641
+# 6a7541ea6fa1406eacf4db796e79ef64
+msgid "Creating VPN connection on both the VPCs initiates a VPN connection. Wait for few seconds. The default is 30 seconds for both the VPN connections to show the Connected state."
+msgstr ""
+
+#: ../../networking2.rst:4646
+# 894d44a883c248778d9598ba46e3f27f
+msgid "Restarting and Removing a VPN Connection"
+msgstr ""
+
+#: ../../networking2.rst:4726
+# 83fe3a90f3094225aecb250153297a3d
+msgid "All the VPN connections you created are displayed."
+msgstr ""
+
+#: ../../networking2.rst:4730
+# b94b1fdaf1c844a28ccf4863998d8635
+msgid "Select the VPN connection you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:4732
+# a9f2559596ff44e281d29137f23566ef
+msgid "The Details tab is displayed."
+msgstr ""
+
+#: ../../networking2.rst:4736
+# a233c3b9788d41f38eb802e1f9d989c9
+msgid "To remove a VPN connection, click the Delete VPN connection button |remove-vpn.png|"
+msgstr ""
+
+#: ../../networking2.rst:4739
+# 41b780de0b934756a92a9ca0269e75e5
+msgid "To restart a VPN connection, click the Reset VPN connection button present in the Details tab. |reset-vpn.png|"
+msgstr ""
+
+#: ../../networking2.rst:4743
+# 183bb10ab504444faae13d81f2319f23
+msgid "About Inter-VLAN Routing (nTier Apps)"
+msgstr ""
+
+#: ../../networking2.rst:4745
+# 13ccb675390f4150acd57078694a88dd
+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 the VMs. In effect, you can segment VMs by means of VLANs into different networks that can host multi-tier applications, such as Web, Application, or Database. Such segmentation by means of VLANs logically separate application VMs for higher security and lower broadcasts, while remaining physically connected to the same device."
+msgstr ""
+
+#: ../../networking2.rst:4758
+# 8e00b9f53dfe4448b8fe2664f0725c1e
+msgid "This feature is supported on XenServer, KVM, and VMware hypervisors."
+msgstr ""
+
+#: ../../networking2.rst:4760
+# cf6ee1a9b0f24cf2b239f5c5ee3e1ccb
+msgid "The major advantages are:"
+msgstr ""
+
+#: ../../networking2.rst:4764
+# 9914db80271c45879b3763424ebbbe4e
+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 ""
+
+#: ../../networking2.rst:4770
+# 7c49b6960b3e4fe98267c66963d07a32
+msgid "A VLAN allocated for an account cannot be shared between multiple accounts."
+msgstr ""
+
+#: ../../networking2.rst:4774
+# 079fa9b5868843beb9ef64f20fd14208
+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 ""
+
+#: ../../networking2.rst:4780
+# cdc5e1a97e7347ed92c034645cf61bb8
+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 ""
+
+#: ../../networking2.rst:4786
+# b939e06705db41289dc97594160ccd4b
+msgid "The administrator can create the following gateways to send to or receive traffic from the VMs:"
+msgstr ""
+
+#: ../../networking2.rst:4791
+# 3f3d39b2a9544b7dbe578450c863c442
+msgid "**VPN Gateway**: For more information, see `\"Creating a VPN gateway for the VPC\" <#creating-a-vpn-gateway-for-the-vpc>`_."
+msgstr ""
+
+#: ../../networking2.rst:4796
+# 563958c0c69e44a79fb209179e6f5ef8
+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 ""
+
+#: ../../networking2.rst:4803
+# 1178d5307b4a4df3b4982bb2985004e1
+msgid "**Private Gateway**: For more information, see \":ref:`adding-priv-gw-vpc`\"."
+msgstr ""
+
+#: ../../networking2.rst:4807
+# c652b274f1d44ceebe3ea04ee8beb31c
+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 ""
+
+#: ../../networking2.rst:4811
+# 5d134a3e16ec432a972f90fb955629c9
+msgid "For example:"
+msgstr ""
+
+#: ../../networking2.rst:4815
+# 47a88da418a64634b2908fb3999fec58
+msgid "**VLANs and Public Gateway**: For example, an application is deployed in the cloud, and the Web application VMs communicate with the Internet."
+msgstr ""
+
+#: ../../networking2.rst:4821
+# e5054d8177ff4ecd817c1e9b50370893
+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 ""
+
+#: ../../networking2.rst:4828
+# 9cf8b80f8da6486e8a190779839a52af
+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 ""
+
+#: ../../networking2.rst:4834
+# f03fcc7d11a24d6d9058d56e0690ee72
+msgid "The following figure shows the possible deployment scenarios of a Inter-VLAN setup:"
+msgstr ""
+
+#: ../../networking2.rst:4837
+# 8da1d43a48f54d3cadd9a2ab40446452
+msgid "|mutltier.png|"
+msgstr ""
+
+#: ../../networking2.rst:4839
+# b5b5c31e4e374e9c80fbb2bb5d5178cd
+msgid "To set up a multi-tier Inter-VLAN deployment, see \":ref:`configuring-vpc`\"."
+msgstr ""
+
+#: ../../networking2.rst:4844
+# 019f7c2e7a1c40289e074fc89915b010
+msgid "Configuring a Virtual Private Cloud"
+msgstr ""
+
+#: ../../networking2.rst:4847
+# cf430774172c4664b8c8126dc2f8f2a9
+msgid "About Virtual Private Clouds"
+msgstr ""
+
+#: ../../networking2.rst:4849
+# 06c06ce2f5fe4b2e8a3464b3c4becf6a
+msgid "CloudStack Virtual Private Cloud is a private, isolated part of CloudStack. A VPC can have its own virtual network topology that resembles a traditional physical network. You can launch VMs in the virtual network that can have private addresses in the range of your choice, for example: 10.0.0.0/16. You can define network tiers within your VPC network range, which in turn enables you to group similar kinds of instances based on IP address range."
+msgstr ""
+
+#: ../../networking2.rst:4857
+# 46308016994049eb85cdc73e86db616e
+msgid "For example, if a VPC has the private range 10.0.0.0/16, its guest networks can have the network ranges 10.0.1.0/24, 10.0.2.0/24, 10.0.3.0/24, and so on."
+msgstr ""
+
+#: ../../networking2.rst:4862
+# ef383bc8b7d54a0785f2b4828b5290ee
+msgid "Major Components of a VPC:"
+msgstr ""
+
+#: ../../networking2.rst:4864
+# b90235f5e79947b7a57dee0d5c08e244
+msgid "A VPC is comprised of the following network components:"
+msgstr ""
+
+#: ../../networking2.rst:4868
+# 9a373d73d3ae48309685ddecb2399f89
+msgid "**VPC**: A VPC acts as a container for multiple isolated networks that can communicate with each other via its virtual router."
+msgstr ""
+
+#: ../../networking2.rst:4873
+# 4d1cc64429d44838942ce9d9290d09f6
+msgid "**Network Tiers**: Each tier acts as an isolated network with its own VLANs and CIDR list, where you can place groups of resources, such as VMs. The tiers are segmented by means of VLANs. The NIC of each tier acts as its gateway."
+msgstr ""
+
+#: ../../networking2.rst:4880
+# 4e202e5460e24d838d858dc82fd70fee
+msgid "**Virtual Router**: A virtual router is automatically created and started when you create a VPC. The virtual router connect the tiers and direct traffic among the public gateway, the VPN gateways, and the NAT instances. For each tier, a corresponding NIC and IP exist in the virtual router. The virtual router provides DNS and DHCP services through its IP."
+msgstr ""
+
+#: ../../networking2.rst:4889
+# 5620f9a835ae40ac9f844be5648dafad
+msgid "**Public Gateway**: The traffic to and from the Internet routed to the VPC through the public gateway. In a VPC, the public gateway is not exposed to the end user; therefore, static routes are not support for the public gateway."
+msgstr ""
+
+#: ../../networking2.rst:4896
+# c72e1f296d024bf6a636137059d31752
+msgid "**Private Gateway**: All the traffic to and from a private network routed to the VPC through the private gateway. For more information, see \":ref:`adding-priv-gw-vpc`\"."
+msgstr ""
+
+#: ../../networking2.rst:4902
+# 741b3998454f43bbad3608dd86a74114
+msgid "**VPN Gateway**: The VPC side of a VPN connection."
+msgstr ""
+
+#: ../../networking2.rst:4906
+# 6487d4f72da84801ae40e38bcb8f7458
+msgid "**Site-to-Site VPN Connection**: A hardware-based VPN connection between your VPC and your datacenter, home network, or co-location facility. For more information, see \":ref:`setting-s2s-vpn-conn`\"."
+msgstr ""
+
+#: ../../networking2.rst:4912
+# d4b8df91ae5d4307835174a0c96640f1
+msgid "**Customer Gateway**: The customer side of a VPN Connection. For more information, see `\"Creating and Updating a VPN Customer Gateway\" <#creating-and-updating-a-vpn-customer-gateway>`_."
+msgstr ""
+
+#: ../../networking2.rst:4918
+# f97a3ebbcde34d3a82a37aa401487760
+msgid "**NAT Instance**: An instance that provides Port Address Translation for instances to access the Internet via the public gateway. For more information, see \":ref:`enabling-disabling-static-nat-on-vpc`\"."
+msgstr ""
+
+#: ../../networking2.rst:4924
+# 0e9442c446e34500a845a7dff022554d
+msgid "**Network ACL**: Network ACL is a group of Network ACL items. Network ACL items are nothing but numbered rules that are evaluated in order, starting with the lowest numbered rule. These rules determine whether traffic is allowed in or out of any tier associated with the network ACL. For more information, see \":ref:`conf-net-acl`\"."
+msgstr ""
+
+#: ../../networking2.rst:4931
+# daf38611958e42f7b832673319b348fb
+msgid "Network Architecture in a VPC"
+msgstr ""
+
+#: ../../networking2.rst:4933
+# cc60b077b9ff4de19f842b6afab2e62b
+msgid "In a VPC, the following four basic options of network architectures are present:"
+msgstr ""
+
+#: ../../networking2.rst:4938
+# f1eb7bb1a38f4dc68def9d12e7a3e178
+msgid "VPC with a public gateway only"
+msgstr ""
+
+#: ../../networking2.rst:4942
+# b0e2f221d7b14320bbc1222a776de41f
+msgid "VPC with public and private gateways"
+msgstr ""
+
+#: ../../networking2.rst:4946
+# 0994c597eccb4d299d4dc9b107fb9fa7
+msgid "VPC with public and private gateways and site-to-site VPN access"
+msgstr ""
+
+#: ../../networking2.rst:4950
+# 870f363e446c47b4b668cb236c51be3b
+msgid "VPC with a private gateway only and site-to-site VPN access"
+msgstr ""
+
+#: ../../networking2.rst:4953
+# 0875278053ce4aa7a964657f5ef7ca92
+msgid "Connectivity Options for a VPC"
+msgstr ""
+
+#: ../../networking2.rst:4955
+# 5d9bd85e540b4cd89292060896221da5
+msgid "You can connect your VPC to:"
+msgstr ""
+
+#: ../../networking2.rst:4959
+# d4a48f7eedb24cd0ada3d40f216fd98e
+msgid "The Internet through the public gateway."
+msgstr ""
+
+#: ../../networking2.rst:4963
+# 24471a284e4241e0bd0c5c456168c7a8
+msgid "The corporate datacenter by using a site-to-site VPN connection through the VPN gateway."
+msgstr ""
+
+#: ../../networking2.rst:4968
+# 25fc02e4454849d4a573bd5dd0d7449a
+msgid "Both the Internet and your corporate datacenter by using both the public gateway and a VPN gateway."
+msgstr ""
+
+#: ../../networking2.rst:4972
+# de5ded73de514bd5a57ecb362fc2faff
+msgid "VPC Network Considerations"
+msgstr ""
+
+#: ../../networking2.rst:4974
+# 78994af1e78348c9ba1f4b1565241a38
+msgid "Consider the following before you create a VPC:"
+msgstr ""
+
+#: ../../networking2.rst:4978
+# cb564008696f42c493ba11e1ed4f80dc
+msgid "A VPC, by default, is created in the enabled state."
+msgstr ""
+
+#: ../../networking2.rst:4982
+# 000ae42b46f34e98836dd0ae06ce491f
+msgid "A VPC can be created in Advance zone only, and can't belong to more than one zone at a time."
+msgstr ""
+
+#: ../../networking2.rst:4987
+# 057235f5ffdf462bb0c747d2d3069fe8
+msgid "The default number of VPCs an account can create is 20. However, you can change it by using the max.account.vpcs global parameter, which controls the maximum number of VPCs an account is allowed to create."
+msgstr ""
+
+#: ../../networking2.rst:4993
+# 6356075be5b54a679178f3b08844bb13
+msgid "The default number of tiers an account can create within a VPC is 3. You can configure this number by using the vpc.max.networks parameter."
+msgstr ""
+
+#: ../../networking2.rst:4999
+# 14ee39b30ff7411188721f6d19152415
+msgid "Each tier should have an unique CIDR in the VPC. Ensure that the tier's CIDR should be within the VPC CIDR range."
+msgstr ""
+
+#: ../../networking2.rst:5004
+# 227b4656e25549c3ae49cbd3eadee4da
+msgid "A tier belongs to only one VPC."
+msgstr ""
+
+#: ../../networking2.rst:5008
+# 8c1c0a2daf2f454daf51a743c52d1875
+msgid "All network tiers inside the VPC should belong to the same account."
+msgstr ""
+
+#: ../../networking2.rst:5012
+# 151ef843569c413592482f23408cc0b1
+msgid "When a VPC is created, by default, a SourceNAT IP is allocated to it. The Source NAT IP is released only when the VPC is removed."
+msgstr ""
+
+#: ../../networking2.rst:5017
+# a4dbf6325246473c80fa288a2c05f46f
+msgid "A public IP can be used for only one purpose at a time. If the IP is a sourceNAT, it cannot be used for StaticNAT or port forwarding."
+msgstr ""
+
+#: ../../networking2.rst:5022
+# 66e9af0df38d44acbdfd5b4f7c7f2209
+msgid "The instances can only have a private IP address that you provision. To communicate with the Internet, enable NAT to an instance that you launch in your VPC."
+msgstr ""
+
+#: ../../networking2.rst:5028
+# a7fc2cd6204b4ccdb272b79d22b93120
+msgid "Only new networks can be added to a VPC. The maximum number of networks per VPC is limited by the value you specify in the vpc.max.networks parameter. The default value is three."
+msgstr ""
+
+#: ../../networking2.rst:5034
+# 636571d03b1244af968495ed107bce4f
+msgid "The load balancing service can be supported by only one tier inside the VPC."
+msgstr ""
+
+#: ../../networking2.rst:5039
+# 690bdd20a5e449298f4d89ca8d62c663
+msgid "If an IP address is assigned to a tier:"
+msgstr ""
+
+#: ../../networking2.rst:5043
+# 58b11a4dc63949a7a3052e4aa24933d5
+msgid "That IP can't be used by more than one tier at a time in the VPC. For example, if you have tiers A and B, and a public IP1, you can create a port forwarding rule by using the IP either for A or B, but not for both."
+msgstr ""
+
+#: ../../networking2.rst:5050
+# 856f012d37d643d8804e106bcbfc20f7
+msgid "That IP can't be used for StaticNAT, load balancing, or port forwarding rules for another guest network inside the VPC."
+msgstr ""
+
+#: ../../networking2.rst:5055
+# 4683db25b3ea4e4188deea16746ee8e9
+msgid "Remote access VPN is not supported in VPC networks."
+msgstr ""
+
+#: ../../networking2.rst:5058
+# d6e7cab15dfe4412bd18e44c210098b5
+msgid "Adding a Virtual Private Cloud"
+msgstr ""
+
+#: ../../networking2.rst:5060
+# aebf60ad9d2040f5a4693f4948d8ee9f
+msgid "When creating the VPC, you simply provide the zone and a set of IP addresses for the VPC network address space. You specify this set of addresses in the form of a Classless Inter-Domain Routing (CIDR) block."
+msgstr ""
+
+#: ../../networking2.rst:5078
+# e96c8770c7a94c51a0e5abf05e27349d
+msgid "Click Add VPC. The Add VPC page is displayed as follows:"
+msgstr ""
+
+#: ../../networking2.rst:5080
+# 5c49f3b134ab451fb0baebec74eb6d02
+msgid "|add-vpc.png|"
+msgstr ""
+
+#: ../../networking2.rst:5086
+# fa0553b67cec41e993031eaa2cfdaf13
+msgid "**Name**: A short name for the VPC that you are creating."
+msgstr ""
+
+#: ../../networking2.rst:5090
+# 97f59ddee9cd4c10bc7c6f87d980837a
+msgid "**Description**: A brief description of the VPC."
+msgstr ""
+
+#: ../../networking2.rst:5094
+# fb51bf0a8fcf42bf90044a947eeb19d5
+msgid "**Zone**: Choose the zone where you want the VPC to be available."
+msgstr ""
+
+#: ../../networking2.rst:5098
+# d7698df9efa0453db3df61a65907f84e
+msgid "**Super CIDR for Guest Networks**: Defines the CIDR range for all the tiers (guest networks) within a VPC. When you create a tier, ensure that its CIDR is within the Super CIDR value you enter. The CIDR must be RFC1918 compliant."
+msgstr ""
+
+#: ../../networking2.rst:5105
+# 927e8a069df94b7ab7c15ce7c08682f2
+msgid "**DNS domain for Guest Networks**: If you want to assign a special domain name, specify the DNS suffix. This parameter is applied to all the tiers within the VPC. That implies, all the tiers you create in the VPC belong to the same DNS domain. If the parameter is not specified, a DNS domain name is generated automatically."
+msgstr ""
+
+#: ../../networking2.rst:5113
+# db3617bea0a7437a98e0ceb8acf7525b
+msgid "**Public Load Balancer Provider**: You have two options: VPC Virtual Router and Netscaler."
+msgstr ""
+
+#: ../../networking2.rst:5121
+# 4cfebf8fa1714d45b8ad960ae9f7ab29
+msgid "Adding Tiers"
+msgstr ""
+
+#: ../../networking2.rst:5123
+# c329d2c258cc49dba5536840ef027842
+msgid "Tiers are distinct locations within a VPC that act as isolated networks, which do not have access to other tiers by default. Tiers are set up on different VLANs that can communicate with each other by using a virtual router. Tiers provide inexpensive, low latency network connectivity to other tiers within the VPC."
+msgstr ""
+
+#: ../../networking2.rst:5141
+#: ../../networking2.rst:6794
+# 28ee0841ce014e79a7a281d4bb216ebc
+# c6dc02263cdf449d9a13e9076217f576
+msgid "All the VPC that you have created for the account is listed in the page."
+msgstr ""
+
+#: ../../networking2.rst:5145
+# c99084307ecd4209897fc97c610b02b1
+msgid "The end users can see their own VPCs, while root and domain admin can see any VPC they are authorized to see."
+msgstr ""
+
+#: ../../networking2.rst:5150
+#: ../../networking2.rst:6799
+# 1470c73ac281442a9cd21cee278957a9
+# 7c8420344fe944869eb9ffe03433dc65
+msgid "Click the Configure button of the VPC for which you want to set up tiers."
+msgstr ""
+
+#: ../../networking2.rst:5155
+# c0383203b6324f44bca1f8d64372fd12
+msgid "Click Create network."
+msgstr ""
+
+#: ../../networking2.rst:5157
+# 71dfd71fa8254a17b162b5ecbea81465
+msgid "The Add new tier dialog is displayed, as follows:"
+msgstr ""
+
+#: ../../networking2.rst:5159
+# 74a521a42b084463aec6f5c6b7a135d8
+msgid "|add-tier.png|"
+msgstr ""
+
+#: ../../networking2.rst:5161
+# cd56a1cb2ee5401699918cb0e48192d6
+msgid "If you have already created tiers, the VPC diagram is displayed. Click Create Tier to add a new tier."
+msgstr ""
+
+#: ../../networking2.rst:5172
+# 08999394431847eb807438afe40264eb
+msgid "**Name**: A unique name for the tier you create."
+msgstr ""
+
+#: ../../networking2.rst:5176
+# b1d5cef8af774c368f4db6f7adb35ae4
+msgid "**Network Offering**: The following default network offerings are listed: Internal LB, DefaultIsolatedNetworkOfferingForVpcNetworksNoLB, DefaultIsolatedNetworkOfferingForVpcNetworks"
+msgstr ""
+
+#: ../../networking2.rst:5181
+# a109edde2faf4ec4b1f5de31c2c91472
+msgid "In a VPC, only one tier can be created by using LB-enabled network offering."
+msgstr ""
+
+#: ../../networking2.rst:5193
+# cb1a1e05c80349aba5c29f7eb19fb029
+msgid "**VLAN**: The VLAN ID for the tier that the root admin creates."
+msgstr ""
+
+#: ../../networking2.rst:5195
+# 3a87f69636d34930b6e2382a6c0df8ed
+msgid "This option is only visible if the network offering you selected is VLAN-enabled."
+msgstr ""
+
+#: ../../networking2.rst:5198
+# 94a1b1fbefab4cd88665da31ab04dff5
+msgid "For more information, see `\"Assigning VLANs to Isolated Networks\" <hosts.html#assigning-vlans-to-isolated-networks>`_."
+msgstr ""
+
+#: ../../networking2.rst:5215
+# 2c2c9c5c56b24b02b949731d057ccece
+msgid "Continue with configuring access control list for the tier."
+msgstr ""
+
+#: ../../networking2.rst:5220
+# fe50554812f144079082cb76d478f030
+msgid "Configuring Network Access Control List"
+msgstr ""
+
+#: ../../networking2.rst:5222
+# e6ac09ebbb494a58abe8f4e2b48ab189
+msgid "Define Network Access Control List (ACL) on the VPC virtual router to control incoming (ingress) and outgoing (egress) traffic between the VPC tiers, and the tiers and Internet. By default, all incoming traffic to the guest networks is blocked and all outgoing traffic from guest networks is allowed, once you add an ACL rule for outgoing traffic, then only outgoing traffic specified in this ACL rule is allowed, the rest is blocked. To open the ports, you must create a new network ACL. The network ACLs can be created for the tiers only if the NetworkACL service is supported."
+msgstr ""
+
+#: ../../networking2.rst:5233
+# 98625caa21a9468fa1732748d2a17096
+msgid "About Network ACL Lists"
+msgstr ""
+
+#: ../../networking2.rst:5235
+# 09938c6b069c491ea32225bf40b4c1cb
+msgid "In CloudStack terminology, Network ACL is a group of Network ACL items. Network ACL items are nothing but numbered rules that are evaluated in order, starting with the lowest numbered rule. These rules determine whether traffic is allowed in or out of any tier associated with the network ACL. You need to add the Network ACL items to the Network ACL, then associate the Network ACL with a tier. Network ACL is associated with a VPC and can be assigned to multiple VPC tiers within a VPC. A Tier is associated with a Network ACL at all the times. Each tier can be associated with only one ACL."
+msgstr ""
+
+#: ../../networking2.rst:5245
+# c66744937e154fa482ad3a3e61f312b8
+msgid "The default Network ACL is used when no ACL is associated. Default behavior is all the incoming traffic is blocked and outgoing traffic is allowed from the tiers. Default network ACL cannot be removed or modified. Contents of the default Network ACL is:"
+msgstr ""
+
+#: ../../networking2.rst:5251
+# e83245e0845e43b2974a692e326ac4d0
+msgid "Rule"
+msgstr ""
+
+#: ../../networking2.rst:5251
+# 80ab5b23b00f4d199c8b9abbf436bb6c
+msgid "Protocol"
+msgstr ""
+
+#: ../../networking2.rst:5251
+# fd729c57b4ea4e5eba4b9567d5fb91c0
+msgid "Traffic type"
+msgstr ""
+
+#: ../../networking2.rst:5251
+# c829bf78c58d40288a0ea4fc4372babf
+msgid "Action"
+msgstr ""
+
+#: ../../networking2.rst:5253
+#: ../../networking2.rst:5254
+# 428dd3d46f624c17b6333ea245a479d1
+# 0044bb0439f34285b617e17b26a24c31
+msgid "All"
+msgstr ""
+
+#: ../../networking2.rst:5253
+# fab35c06087d44a7874a0f5bcd4b49a3
+msgid "Ingress"
+msgstr ""
+
+#: ../../networking2.rst:5253
+#: ../../networking2.rst:5254
+# 28a1e4dff1af4530b1bc7247d7231156
+# f074d55a63a84bdd93f4679ef5703083
+msgid "0.0.0.0/0"
+msgstr ""
+
+#: ../../networking2.rst:5254
+# b4f811fade53417f914ba70fdda841eb
+msgid "Egress"
+msgstr ""
+
+#: ../../networking2.rst:5258
+# 8cc5201e9ef74389bf852a8c965d8c58
+msgid "Creating ACL Lists"
+msgstr ""
+
+#: ../../networking2.rst:5321
+#: ../../networking2.rst:5363
+# 1d2d971c7e064b558d73374bc47d82d0
+# 3404c28191eb451a91f3cfa59aefaba4
+msgid "Select Network ACL Lists."
+msgstr ""
+
+#: ../../networking2.rst:5323
+# faf3ffe663364217b1a4616fa0286cf2
+msgid "The following default rules are displayed in the Network ACLs page: default\\_allow, default\\_deny."
+msgstr ""
+
+#: ../../networking2.rst:5328
+# f9e4f48e72cc497a8f9dcdbb42107837
+msgid "Click Add ACL Lists, and specify the following:"
+msgstr ""
+
+#: ../../networking2.rst:5332
+# 90439c9713414c43aa9c2e05eb942726
+msgid "**ACL List Name**: A name for the ACL list."
+msgstr ""
+
+#: ../../networking2.rst:5336
+# d7606f1b49fa42f190dcf0037e7a7f82
+msgid "**Description**: A short description of the ACL list that can be displayed to users."
+msgstr ""
+
+#: ../../networking2.rst:5340
+# 48a4f463117347eb8b319809642e7da8
+msgid "Creating an ACL Rule"
+msgstr ""
+
+#: ../../networking2.rst:5365
+# 2651d622eb634957a6d286e42b35b431
+msgid "In addition to the custom ACL lists you have created, the following default rules are displayed in the Network ACLs page: default\\_allow, default\\_deny."
+msgstr ""
+
+#: ../../networking2.rst:5371
+#: ../../networking2.rst:5495
+# 8589eb86d31d49b0b8b3a066e403dea3
+# 9fe9f83f4eea466b8c268bff18971db7
+msgid "Select the desired ACL list."
+msgstr ""
+
+#: ../../networking2.rst:5375
+# 526f674e5a544241bfcb69fec29f6b30
+msgid "Select the ACL List Rules tab."
+msgstr ""
+
+#: ../../networking2.rst:5377
+# 6b315c7b1ebe42268824f83af55fae75
+msgid "To add an ACL rule, fill in the following fields to specify what kind of network traffic is allowed in the VPC."
+msgstr ""
+
+#: ../../networking2.rst:5382
+# e9fd41991f514decba25f1e0b8bacf9a
+msgid "**Rule Number**: The order in which the rules are evaluated."
+msgstr ""
+
+#: ../../networking2.rst:5386
+# 74e33543194246e9bf723eb7f8579770
+msgid "**CIDR**: The CIDR acts as the Source CIDR for the Ingress rules, and Destination CIDR for the Egress rules. To accept traffic only from or 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 incoming traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr ""
+
+#: ../../networking2.rst:5395
+# 56275e37fc8b4caea8702ef3e16f0361
+msgid "**Action**: What action to be taken. Allow traffic or block."
+msgstr ""
+
+#: ../../networking2.rst:5399
+# 3a81766b5639471dad96fc442722931a
+msgid "**Protocol**: The networking protocol that sources use to send traffic to the tier. 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. All supports all the traffic. Other option is Protocol Number."
+msgstr ""
+
+#: ../../networking2.rst:5408
+# f182719948c24202b52f34f53d6237ca
+msgid "**Start Port**, **End Port** (TCP, UDP only): A range of listening ports that are the destination for the incoming traffic. If you are opening a single port, use the same number in both fields."
+msgstr ""
+
+#: ../../networking2.rst:5414
+# 95cc0c49ceea4d609a66a6f010f464a8
+msgid "**Protocol Number**: The protocol number associated with IPv4 or IPv6. For more information, see `Protocol Numbers <http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xml>`_."
+msgstr ""
+
+#: ../../networking2.rst:5420
+# 9557a03428624acd806829547ae0ca87
+msgid "**ICMP Type**, **ICMP Code** (ICMP only): The type of message and error code that will be sent."
+msgstr ""
+
+#: ../../networking2.rst:5425
+# daa0c660c1ee4f7c86a1abd1282d5aa5
+msgid "**Traffic Type**: The type of traffic: Incoming or outgoing."
+msgstr ""
+
+#: ../../networking2.rst:5429
+# 2a986f306a534501ac5ce1869c4879b2
+msgid "Click Add. The ACL rule is added."
+msgstr ""
+
+#: ../../networking2.rst:5431
+# 1ff7a90c1c8b4226b22c2f267b0cd329
+msgid "You can edit the tags assigned to the ACL rules and delete the ACL rules you have created. Click the appropriate button in the Details tab."
+msgstr ""
+
+#: ../../networking2.rst:5436
+# 497f804bbce846e084e10331e6e0079b
+msgid "Creating a Tier with Custom ACL List"
+msgstr ""
+
+#: ../../networking2.rst:5440
+#: ../../networking2.rst:5465
+# d0c0bf84620447fc8dfa178137f97b16
+# d930dbc632b042b188ba54a843e568f1
+msgid "Create a VPC."
+msgstr ""
+
+#: ../../networking2.rst:5444
+#: ../../networking2.rst:5477
+# 25eee7556d974e60bbeb1f18e85c55df
+# 6ed43363cfac4b8987d1e2d72304c877
+msgid "Create a custom ACL list."
+msgstr ""
+
+#: ../../networking2.rst:5448
+#: ../../networking2.rst:5481
+# 6dcc5bedc2554ba1a3e36b2e2b3645be
+# 5463933959af4e5288a81e194a5e6a58
+msgid "Add ACL rules to the ACL list."
+msgstr ""
+
+#: ../../networking2.rst:5452
+#: ../../networking2.rst:5469
+# 029e9aecbf464779994d37ec61ad7314
+# 0413f59339f64f0b873ba87c7d559a84
+msgid "Create a tier in the VPC."
+msgstr ""
+
+#: ../../networking2.rst:5454
+# d789fdcbc43847f981d99a6c6a203caf
+msgid "Select the desired ACL list while creating a tier."
+msgstr ""
+
+#: ../../networking2.rst:5461
+# d2aee63fb26240c8ab5829112ee254c1
+msgid "Assigning a Custom ACL List to a Tier"
+msgstr ""
+
+#: ../../networking2.rst:5473
+# b0606dffaee64d4994e5e57c20a1c455
+msgid "Associate the tier with the default ACL rule."
+msgstr ""
+
+#: ../../networking2.rst:5485
+# 6113c98ff3804f59808cc2f432c7312e
+msgid "Select the tier for which you want to assign the custom ACL."
+msgstr ""
+
+#: ../../networking2.rst:5489
+# 14772476c28c4746811457f94c763124
+msgid "Click the Replace ACL List icon. |replace-acl-icon.png|"
+msgstr ""
+
+#: ../../networking2.rst:5491
+# c4482d85ed6040e0978d138c1416283a
+msgid "The Replace ACL List dialog is displayed."
+msgstr ""
+
+#: ../../networking2.rst:5504
+# 8abffdce40894b3fafb845f68b82bc74
+msgid "Adding a Private Gateway to a VPC"
+msgstr ""
+
+#: ../../networking2.rst:5506
+# 743a879733de4969814a821843950e18
+msgid "A private gateway can be added by the root admin only. The VPC private network has 1:1 relationship with the NIC of the physical network. You can configure multiple private gateways to a single VPC. No gateways with duplicated VLAN and IP are allowed in the same data center."
+msgstr ""
+
+#: ../../networking2.rst:5528
+# dd777f72c6814da7a4e087c6c8c60cbe
+msgid "Click the Configure button of the VPC to which you want to configure load balancing rules."
+msgstr ""
+
+#: ../../networking2.rst:5538
+#: ../../networking2.rst:5864
+#: ../../networking2.rst:5951
+# 27478e3646e84848b0ead2c5ad0d50f9
+# d08325208f454c9b8c778e4776c4daa3
+# bc97c76d6cd648dc9717c2058744a84e
+msgid "The following options are displayed."
+msgstr ""
+
+#: ../../networking2.rst:5580
+# 394a3dcb6e3741b489d58eb9830c71e9
+msgid "Select Private Gateways."
+msgstr ""
+
+#: ../../networking2.rst:5582
+# e4a0570c1e7a471cb5d358378b06e7fe
+msgid "The Gateways page is displayed."
+msgstr ""
+
+#: ../../networking2.rst:5586
+# 6ca2b7325b9e4244a7785ff0e1ddbfd9
+msgid "Click Add new gateway:"
+msgstr ""
+
+#: ../../networking2.rst:5588
+# 1d19d16a595c4323b72e7afcfa725bee
+msgid "|add-new-gateway-vpc.png|"
+msgstr ""
+
+#: ../../networking2.rst:5596
+# 8413e5ef903842ec837e56605289465f
+msgid "**Physical Network**: The physical network you have created in the zone."
+msgstr ""
+
+#: ../../networking2.rst:5601
+# 0a11f680d5cf4a41a7a387b092f56f28
+msgid "**IP Address**: The IP address associated with the VPC gateway."
+msgstr ""
+
+#: ../../networking2.rst:5605
+# fd907890f582482d8e4cf0dd81960ff5
+msgid "**Gateway**: The gateway through which the traffic is routed to and from the VPC."
+msgstr ""
+
+#: ../../networking2.rst:5610
+# 7487738adef9453d85604bfba671fa3f
+msgid "**Netmask**: The netmask associated with the VPC gateway."
+msgstr ""
+
+#: ../../networking2.rst:5614
+# 16e78548659f4f26a1bda70303cc2316
+msgid "**VLAN**: The VLAN associated with the VPC gateway."
+msgstr ""
+
+#: ../../networking2.rst:5618
+# 4cdaeb9a18454c5a91c6210ae427c1a9
+msgid "**Source NAT**: Select this option to enable the source NAT service on the VPC private gateway."
+msgstr ""
+
+#: ../../networking2.rst:5621
+# c6b56cf49a42479893378e9da36129da
+msgid "See \":ref:`source-nat-priv-gw`\"."
+msgstr ""
+
+#: ../../networking2.rst:5625
+# c362a5b1af954f8c9a1fd9e40fb438db
+msgid "**ACL**: Controls both ingress and egress traffic on a VPC private gateway. By default, all the traffic is blocked."
+msgstr ""
+
+#: ../../networking2.rst:5628
+# a6398dc9bed3442296a3f9cac8a90a34
+msgid "See \":ref:`acl-priv-gw`\"."
+msgstr ""
+
+#: ../../networking2.rst:5630
+# b9e1f64ee58f4a9fa3bdd10dd0cfaa4f
+msgid "The new gateway appears in the list. You can repeat these steps to add more gateway for this VPC."
+msgstr ""
+
+#: ../../networking2.rst:5636
+# f6c87880d85a40cfa41db29b98eb2194
+msgid "Source NAT on Private Gateway"
+msgstr ""
+
+#: ../../networking2.rst:5638
+# 5a7c4b197f044c9bbb56e419cc6153a8
+msgid "You might want to deploy multiple VPCs with the same super CIDR and guest tier CIDR. Therefore, multiple guest VMs from different VPCs can have the same IPs to reach a enterprise data center through the private gateway. In such cases, a NAT service need to be configured on the private gateway to avoid IP conflicts. If Source NAT is enabled, the guest VMs in VPC reaches the enterprise network via private gateway IP address by using the NAT service."
+msgstr ""
+
+#: ../../networking2.rst:5646
+# 5a246caddff54fc8aeda076ee6ad6da2
+msgid "The Source NAT service on a private gateway can be enabled while adding the private gateway. On deletion of a private gateway, source NAT rules specific to the private gateway are deleted."
+msgstr ""
+
+#: ../../networking2.rst:5650
+# 7b68b00b8cae40daa6b6e018b007407f
+msgid "To enable source NAT on existing private gateways, delete them and create afresh with source NAT."
+msgstr ""
+
+#: ../../networking2.rst:5656
+# 5eb31def4dea44a8b45223d8bfba9bc1
+msgid "ACL on Private Gateway"
+msgstr ""
+
+#: ../../networking2.rst:5658
+# 43dd38fb6bcb4da99519465cd2fee79e
+msgid "The traffic on the VPC private gateway is controlled by creating both ingress and egress network ACL rules. The ACLs contains both allow and deny rules. As per the rule, all the ingress traffic to the private gateway interface and all the egress traffic out from the private gateway interface are blocked."
+msgstr ""
+
+#: ../../networking2.rst:5664
+# 968f844cb23249299b07710fbdea8328
+msgid "You can change this default behaviour while creating a private gateway. Alternatively, you can do the following:"
+msgstr ""
+
+#: ../../networking2.rst:5669
+#: ../../networking2.rst:5715
+# c42acc331624417e9e3770047d128c45
+# f426686ca214461286b5b27085ef9e07
+msgid "In a VPC, identify the Private Gateway you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:5673
+# bebf8abea37d4d5da748d4dc7da121e9
+msgid "In the Private Gateway page, do either of the following:"
+msgstr ""
+
+#: ../../networking2.rst:5677
+# 83b961b102be4930990a6f24d2f61788
+msgid "Use the Quickview. See 3."
+msgstr ""
+
+#: ../../networking2.rst:5681
+# af59e46963cc4dfcae44b860b6d546a1
+msgid "Use the Details tab. See 4 through ."
+msgstr ""
+
+#: ../../networking2.rst:5685
+# d774795a1b854c8e9b7b135859f6dc59
+msgid "In the Quickview of the selected Private Gateway, click Replace ACL, select the ACL rule, then click OK"
+msgstr ""
+
+#: ../../networking2.rst:5690
+# 24203d2c129848b3a54d2a2a6f231ce4
+msgid "Click the IP address of the Private Gateway you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:5694
+# 1374de69edfb44449764f2be1dcb29e2
+msgid "In the Detail tab, click the Replace ACL button. |replace-acl-icon.png|"
+msgstr ""
+
+#: ../../networking2.rst:5697
+# 0a1a67c900a645b587377ce0696fcc69
+msgid "The Replace ACL dialog is displayed."
+msgstr ""
+
+#: ../../networking2.rst:5701
+# b054350634fe4a6a93e997e7888de509
+msgid "select the ACL rule, then click OK."
+msgstr ""
+
+#: ../../networking2.rst:5703
+# 89bdf37574754f799764bcd9ea9b8154
+msgid "Wait for few seconds. You can see that the new ACL rule is displayed in the Details page."
+msgstr ""
+
+#: ../../networking2.rst:5707
+# 5156bdb1b2c6423aa03d31c6d234cdbb
+msgid "Creating a Static Route"
+msgstr ""
+
+#: ../../networking2.rst:5709
+# 188c119a7dde4624a113c36b70910b9e
+msgid "CloudStack enables you to specify routing for the VPN connection you create. You can enter one or CIDR addresses to indicate which traffic is to be routed back to the gateway."
+msgstr ""
+
+#: ../../networking2.rst:5719
+# c483d63531ae420796887a1e3a3f5ab3
+msgid "In the Private Gateway page, click the IP address of the Private Gateway you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:5724
+# df50f83dcb434a239f5ce4054573908a
+msgid "Select the Static Routes tab."
+msgstr ""
+
+#: ../../networking2.rst:5728
+# ddbc917d09ae47a1a33bb2e422a41ac8
+msgid "Specify the CIDR of destination network."
+msgstr ""
+
+#: ../../networking2.rst:5734
+# 14be55f3d8354339befda018b8959689
+msgid "Wait for few seconds until the new route is created."
+msgstr ""
+
+#: ../../networking2.rst:5737
+# 4bb61ba3dd1444269d2f517a3d774dac
+msgid "Blacklisting Routes"
+msgstr ""
+
+#: ../../networking2.rst:5739
+# bf15aaf7395c48438bdfb1c5a1b303cd
+msgid "CloudStack enables you to block a list of routes so that they are not assigned to any of the VPC private gateways. Specify the list of routes that you want to blacklist in the ``blacklisted.routes`` global parameter. Note that the parameter update affects only new static route creations. If you block an existing static route, it remains intact and continue functioning. You cannot add a static route if the route is blacklisted for the zone."
+msgstr ""
+
+#: ../../networking2.rst:5748
+# 0331141edca34d0d88619127d2766371
+msgid "Deploying VMs to the Tier"
+msgstr ""
+
+#: ../../networking2.rst:5770
+# 704ce74d41e94806a21f067331377028
+msgid "The VPC page is displayed where all the tiers you have created are listed."
+msgstr ""
+
+#: ../../networking2.rst:5775
+# bb949e6b291d4db5b13cf4fe9834f452
+msgid "Click Virtual Machines tab of the tier to which you want to add a VM."
+msgstr ""
+
+#: ../../networking2.rst:5777
+# 71ad9ca13d4c4362972cdf2637e41c93
+msgid "|add-vm-vpc.png|"
+msgstr ""
+
+#: ../../networking2.rst:5779
+# 2f2516ad2c5942d999843c0a9a68933e
+msgid "The Add Instance page is displayed."
+msgstr ""
+
+#: ../../networking2.rst:5781
+# 1d62201e441d48f788fa541062d4c596
+msgid "Follow the on-screen instruction to add an instance. For information on adding an instance, see the Installation Guide."
+msgstr ""
+
+#: ../../networking2.rst:5785
+# 635c6aa90270428badb026296ec37787
+msgid "Deploying VMs to VPC Tier and Shared Networks"
+msgstr ""
+
+#: ../../networking2.rst:5787
+# dd3534643d7a477c824d8e185d5475e4
+msgid "CloudStack allows you deploy VMs on a VPC tier and one or more shared networks. With this feature, VMs deployed in a multi-tier application can receive monitoring services via a shared network provided by a service provider."
+msgstr ""
+
+#: ../../networking2.rst:5794
+# b14c4ec942684d4d8a32be3cc684ba90
+msgid "Log in to the CloudStack UI as an administrator."
+msgstr ""
+
+#: ../../networking2.rst:5798
+# 47af434606084162a5d43bfca5f9a35c
+msgid "In the left navigation, choose Instances."
+msgstr ""
+
+#: ../../networking2.rst:5802
+# 75908924f9fe449db880b8f340e3e1b9
+msgid "Click Add Instance."
+msgstr ""
+
+#: ../../networking2.rst:5806
+# 1129214998c14deca387e232b2b61a2c
+msgid "Select a zone."
+msgstr ""
+
+#: ../../networking2.rst:5810
+# 447c3075519c4efcb0cce18f747c5fdc
+msgid "Select a template or ISO, then follow the steps in the wizard."
+msgstr ""
+
+#: ../../networking2.rst:5814
+# ac1ff1f49a954b0dbd5cd4e18543ec70
+msgid "Ensure that the hardware you have allows starting the selected service offering."
+msgstr ""
+
+#: ../../networking2.rst:5819
+# 5e9d7d945a51416db45c9d4c136cf660
+msgid "Under Networks, select the desired networks for the VM you are launching."
+msgstr ""
+
+#: ../../networking2.rst:5822
+# 6a193b8ef2e14baab4287c9227dbd94f
+msgid "You can deploy a VM to a VPC tier and multiple shared networks."
+msgstr ""
+
+#: ../../networking2.rst:5824
+# 69378b350f8540138b3659036450b93e
+msgid "|addvm-tier-sharednw.png|"
+msgstr ""
+
+#: ../../networking2.rst:5828
+# c32a2db50b2b44dfa529d303ae7737ca
+msgid "Click Next, review the configuration and click Launch."
+msgstr ""
+
+#: ../../networking2.rst:5830
+# 424cd68b49af4936b7a29172ce8b21c6
+msgid "Your VM will be deployed to the selected VPC tier and shared network."
+msgstr ""
+
+#: ../../networking2.rst:5833
+# a466e870147241b7a6266b24ffb983be
+msgid "Acquiring a New IP Address for a VPC"
+msgstr ""
+
+#: ../../networking2.rst:5835
+# 2469c8b87a5b404695be7cd3d52d8540
+msgid "When you acquire an IP address, all IP addresses are allocated to VPC, not to the guest networks within the VPC. The IPs are associated to the guest network only when the first port-forwarding, load balancing, or Static NAT rule is created for the IP or the network. IP can't be associated to more than one network at a time."
+msgstr ""
+
+#: ../../networking2.rst:5906
+# 20c45cce73544593af8aea069f4556ce
+msgid "Select IP Addresses."
+msgstr ""
+
+#: ../../networking2.rst:5908
+# e00bf099dd75477787b7732cadc10c50
+msgid "The Public IP Addresses page is displayed."
+msgstr ""
+
+#: ../../networking2.rst:5912
+# decf033da44c4b64b64175bbace5e37d
+msgid "Click Acquire New IP, and click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../networking2.rst:5914
+# f9206ddfd2ad4b9ba496b7bcaa139527
+msgid "You are prompted for confirmation because, typically, IP addresses are a limited resource. Within a few moments, the new IP address should appear with the state Allocated. You can now use the IP address in port forwarding, load balancing, and static NAT rules."
+msgstr ""
+
+#: ../../networking2.rst:5920
+# 1b26f54458754874a03b4d4bf65d1776
+msgid "Releasing an IP Address Alloted to a VPC"
+msgstr ""
+
+#: ../../networking2.rst:5922
+# be262f6b7e5d45269e0940307ba4a209
+msgid "The IP address is a limited resource. If you no longer need a particular IP, you can disassociate it from its VPC and return it to the pool of available addresses. An IP address can be released from its tier, only when all the networking ( port forwarding, load balancing, or StaticNAT ) rules are removed for this IP address. The released IP address will still belongs to the same VPC."
+msgstr ""
+
+#: ../../networking2.rst:5946
+# b689860f9d8243e488f59f407397d0f2
+msgid "Click the Configure button of the VPC whose IP you want to release."
+msgstr ""
+
+#: ../../networking2.rst:5993
+# 275b1067e783409fa57673f2c9079c5f
+msgid "Select Public IP Addresses."
+msgstr ""
+
+#: ../../networking2.rst:5999
+# 03719974990f4be2ab4ef5acfece3c8e
+msgid "Click the IP you want to release."
+msgstr ""
+
+#: ../../networking2.rst:6003
+# 0cfc510897374fe28fa93542914d6cf3
+msgid "In the Details tab, click the Release IP button |release-ip-icon.png|"
+msgstr ""
+
+#: ../../networking2.rst:6008
+# be0f2d3e3f7a4e4485e68f2f4eb4339d
+msgid "Enabling or Disabling Static NAT on a VPC"
+msgstr ""
+
+#: ../../networking2.rst:6010
+# b3b3c30b45744238bdaaee1fe21a6ae1
+msgid "A static NAT rule maps a public IP address to the private IP address of a VM in a VPC to allow Internet traffic to it. This section tells how to enable or disable static NAT for a particular IP address in a VPC."
+msgstr ""
+
+#: ../../networking2.rst:6043
+# 8d4539553a8249e59a6c06a65466159f
+msgid "For each tier, the following options are displayed."
+msgstr ""
+
+#: ../../networking2.rst:6091
+# d38f21f4fa594fc99e3fe3eb6bcaac34
+msgid "Click the IP you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:6095
+# 17644423675640bdafb3f481e66d08cd
+msgid "In the Details tab,click the Static NAT button. |enable-disable.png| The button toggles between Enable and Disable, depending on whether static NAT is currently enabled for the IP address."
+msgstr ""
+
+#: ../../networking2.rst:6102
+# d5a0063d431a449b822e840cf68321c0
+msgid "If you are enabling static NAT, a dialog appears as follows:"
+msgstr ""
+
+#: ../../networking2.rst:6104
+# addd4d2aaf5345c486dcddaf20d41069
+msgid "|select-vmstatic-nat.png|"
+msgstr ""
+
+#: ../../networking2.rst:6108
+# e794f8894d7c4c4fb1d144b53ba3eef5
+msgid "Select the tier and the destination VM, then click Apply."
+msgstr ""
+
+#: ../../networking2.rst:6111
+# d7cc633eb7064d0e98b22cf3441dea8f
+msgid "Adding Load Balancing Rules on a VPC"
+msgstr ""
+
+#: ../../networking2.rst:6113
+# 1690cddd7d4544da8afebf41a357f0f6
+msgid "In a VPC, you can configure two types of load balancing: external LB and internal LB. External LB is nothing but a LB rule created to redirect the traffic received at a public IP of the VPC virtual router. The traffic is load balanced within a tier based on your configuration. Citrix NetScaler and VPC virtual router are supported for external LB. When you use internal LB service, traffic received at a tier is load balanced across different VMs within that tier. For example, traffic reached at Web tier is redirected to another VM in that tier. External load balancing devices are not supported for internal LB. The service is provided by a internal LB VM configured on the target tier."
+msgstr ""
+
+#: ../../networking2.rst:6125
+# 5ab48adf63474d97b4570c40a24420bb
+msgid "Load Balancing Within a Tier (External LB)"
+msgstr ""
+
+#: ../../networking2.rst:6127
+# c70e83e371234131bf11479286cdbb1c
+msgid "A CloudStack user or administrator may create load balancing rules that balance traffic received at a public IP to one or more VMs that belong to a network tier that provides load balancing service in a VPC. A user creates a rule, specifies an algorithm, and assigns the rule to a set of VMs within a tier."
+msgstr ""
+
+#: ../../networking2.rst:6134
+# 793b75511a124eb49bc054c366095f7f
+msgid "Enabling NetScaler as the LB Provider on a VPC Tier"
+msgstr ""
+
+#: ../../networking2.rst:6138
+# 2cba8bc745e44ac4a8d2aaeca47e11f7
+msgid "Add and enable Netscaler VPX in dedicated mode."
+msgstr ""
+
+#: ../../networking2.rst:6140
+# 2994a10476d64a719afb3c651265ac88
+msgid "Netscaler can be used in a VPC environment only if it is in dedicated mode."
+msgstr ""
+
+#: ../../networking2.rst:6145
+# d112b0ba00654e278f9b1475857355b0
+msgid "Create a network offering, as given in \":ref:`create-net-offering-ext-lb`\"."
+msgstr ""
+
+#: ../../networking2.rst:6149
+# 909680d1f1b34b728fbb4a720169c60b
+msgid "Create a VPC with Netscaler as the Public LB provider."
+msgstr ""
+
+#: ../../networking2.rst:6151
+# 7ff9cc3865b44322afc77e6c4c063878
+msgid "For more information, see `\"Adding a Virtual Private Cloud\" <#adding-a-virtual-private-cloud>`_."
+msgstr ""
+
+#: ../../networking2.rst:6156
+# 9f9ae62b0b214cba91857447245a18d6
+msgid "For the VPC, acquire an IP."
+msgstr ""
+
+#: ../../networking2.rst:6160
+# c75b7cc4b3234929a881c47cc9eac788
+msgid "Create an external load balancing rule and apply, as given in :ref:`create-ext-lb-rule`."
+msgstr ""
+
+#: ../../networking2.rst:6166
+# d874e75e8da946b99ed923dcdaed1708
+msgid "Creating a Network Offering for External LB"
+msgstr ""
+
+#: ../../networking2.rst:6168
+# 7f3a18897d37416bb87a733cb3943071
+msgid "To have external LB support on VPC, create a network offering as follows:"
+msgstr ""
+
+#: ../../networking2.rst:6173
+#: ../../networking2.rst:6478
+# f8f209ed13a948109fa2bb53a02c1658
+# 2681733d801147e687ba507663618ba4
+msgid "Log in to the CloudStack UI as a user or admin."
+msgstr ""
+
+#: ../../networking2.rst:6177
+#: ../../networking2.rst:6482
+# bfaeb8a949fb4d25a618540dcc365471
+# 6c6e4ac1110442ba9ec325328e96bfb8
+msgid "From the Select Offering drop-down, choose Network Offering."
+msgstr ""
+
+#: ../../networking2.rst:6185
+#: ../../networking2.rst:6490
+# 7d4dc49f6e224caa9bee24da2b622a4c
+# 8e12000ca5ad480ab9dab674135a18a8
+msgid "In the dialog, make the following choices:"
+msgstr ""
+
+#: ../../networking2.rst:6189
+#: ../../networking2.rst:6494
+# 3d9e45006e6b427b94e238e0f793a577
+# 066c1cd8d7414486bd0a821ccffc100b
+msgid "**Name**: Any desired name for the network offering."
+msgstr ""
+
+#: ../../networking2.rst:6193
+#: ../../networking2.rst:6498
+# acbfe1094f0643fea1072cd746f35188
+# f27a5e7e95c64d4b984ce309aaaee266
+msgid "**Description**: A short description of the offering that can be displayed to users."
+msgstr ""
+
+#: ../../networking2.rst:6198
+#: ../../networking2.rst:6503
+# 15f09db814bb43e2832e26ce351b9ae6
+# d6ebc01d2aea41328bd788a943cea913
+msgid "**Network Rate**: Allowed data transfer rate in MB per second."
+msgstr ""
+
+#: ../../networking2.rst:6202
+#: ../../networking2.rst:6507
+# a4945e04912944f89c7073bdac1af7af
+# a9b549ff67de4071aad4f568bc2d7d2b
+msgid "**Traffic Type**: The type of network traffic that will be carried on the network."
+msgstr ""
+
+#: ../../networking2.rst:6207
+#: ../../networking2.rst:6512
+# aefb9c140bc34d2b9b3c2d433d14c685
+# 169e4a6365194916a452f640cf688fb0
+msgid "**Guest Type**: Choose whether the guest network is isolated or shared."
+msgstr ""
+
+#: ../../networking2.rst:6212
+#: ../../networking2.rst:6517
+# bdfc22e5126944f5bca7168232a3f3f5
+# d937940688b44a349057cd0905cd57b2
+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."
+msgstr ""
+
+#: ../../networking2.rst:6218
+#: ../../networking2.rst:6523
+# 24cbc093f168445995bd443ca153e32c
+# b1ee73a6428247b38f74321037409214
+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\" <#about-virtual-private-clouds>`_."
+msgstr ""
+
+#: ../../networking2.rst:6226
+#: ../../networking2.rst:6532
+# 4bf8da8a72a240cd858cf9a55cb035ad
+# 6db873f4ea9f410fb0a58b146ce86962
+msgid "**Specify VLAN**: (Isolated guest networks only) Indicate whether a VLAN should be specified when this offering is used."
+msgstr ""
+
+#: ../../networking2.rst:6231
+# 1d81bbc322a54e489b5b1da1c925266c
+msgid "**Supported Services**: Select Load Balancer. Use Netscaler or VpcVirtualRouter."
+msgstr ""
+
+#: ../../networking2.rst:6236
+# b7b1ce246f71472ebf576db84b53c0e2
+msgid "**Load Balancer Type**: Select Public LB from the drop-down."
+msgstr ""
+
+#: ../../networking2.rst:6240
+# 7b38714001f849eaac70496b3c171131
+msgid "**LB Isolation**: Select Dedicated if Netscaler is used as the external LB provider."
+msgstr ""
+
+#: ../../networking2.rst:6245
+#: ../../networking2.rst:6546
+# f8eb59d83f644c33b8ee256b3cb69be1
+# f03b089f4f1442e99afc923137ed1f0f
+msgid "**System Offering**: Choose the system service offering that you want virtual routers to use in this network."
+msgstr ""
+
+#: ../../networking2.rst:6250
+#: ../../networking2.rst:6551
+# e2ce12394dea4b1abc2c67c40b3f20ce
+# 537aea511f3244d880cd207f11c31028
+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."
+msgstr ""
+
+#: ../../networking2.rst:6256
+#: ../../networking2.rst:6557
+# f89be0d5cb8f47a581ef67c728561fc4
+# 05c7f9a8f2fa439ba289bc25ce6430ab
+msgid "Click OK and the network offering is created."
+msgstr ""
+
+#: ../../networking2.rst:6261
+# 492f96c74e934c4385e58a39f4c1633b
+msgid "Creating an External LB Rule"
+msgstr ""
+
+#: ../../networking2.rst:6280
+# b8dd2aecb6fa4106bfed11ed839c7aca
+msgid "Click the Configure button of the VPC, for which you want to configure load balancing rules."
+msgstr ""
+
+#: ../../networking2.rst:6283
+#: ../../networking2.rst:6593
+# 522435c1f1414cc18a01df702d9f6281
+# bcacf41ce9934ed095e8f719398c45b3
+msgid "The VPC page is displayed where all the tiers you created listed in a diagram."
+msgstr ""
+
+#: ../../networking2.rst:6343
+#: ../../networking2.rst:6737
+# 0ccde3dd807a4f04ac772a7cf191a828
+# c8b1e6fcd7554efd9584f9488b591a1f
+msgid "Select the tier to which you want to apply the rule."
+msgstr ""
+
+#: ../../networking2.rst:6355
+# 1744ccff1ce1472ea311af081db3ec2f
+msgid "**Public Port**: The port that receives the incoming traffic to be balanced."
+msgstr ""
+
+#: ../../networking2.rst:6365
+#: ../../networking2.rst:6638
+# 841c7cfded624598a7091a1eb3f3f894
+# 1342d03c9f7e4b4a879cc635b80b627e
+msgid "**Algorithm**. Choose the load balancing algorithm you want CloudStack to use. CloudStack supports the following well-known algorithms:"
+msgstr ""
+
+#: ../../networking2.rst:6375
+#: ../../networking2.rst:6648
+# ca0b21cbc71045ef9d692689bdf8753b
+# c5c7bc131cb24e8a89af17bc2ee39a95
+msgid "Least connections"
+msgstr ""
+
+#: ../../networking2.rst:6379
+#: ../../networking2.rst:6652
+# 6c473e5828a34e0287d62955ca824812
+# a9615fbf431b46e4b58d02737e405bca
+msgid "Source"
+msgstr ""
+
+#: ../../networking2.rst:6383
+# 1dc54356abfe4ffa8b1fba11d7728393
+msgid "**Stickiness**. (Optional) Click Configure and choose the algorithm for the stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr ""
+
+#: ../../networking2.rst:6389
+# 237d74628ed349cf856380cefedd651f
+msgid "**Add VMs**: Click Add VMs, then select two or more VMs that will divide the load of incoming traffic, and click Apply."
+msgstr ""
+
+#: ../../networking2.rst:6392
+# 71e872c5170d4050b696e3ce82700548
+msgid "The new load balancing rule appears in the list. You can repeat these steps to add more load balancing rules for this IP address."
+msgstr ""
+
+#: ../../networking2.rst:6396
+# 4574a620c8424f90a6c9a8c28f5460a1
+msgid "Load Balancing Across Tiers"
+msgstr ""
+
+#: ../../networking2.rst:6398
+# 843b230d3f9d4a50946db6b4012be2cc
+msgid "CloudStack supports sharing workload across different tiers within your VPC. Assume that multiple tiers are set up in your environment, such as Web tier and Application tier. Traffic to each tier is balanced on the VPC virtual router on the public side, as explained in `\"Adding Load Balancing Rules on a VPC\" <#adding-load-balancing-rules-on-a-vpc>`_. If you want the traffic coming from the Web tier to the Application tier to be balanced, use the internal load balancing feature offered by CloudStack."
+msgstr ""
+
+#: ../../networking2.rst:6408
+# 525cb00286734509a00f17f18c86ced6
+msgid "How Does Internal LB Work in VPC?"
+msgstr ""
+
+#: ../../networking2.rst:6410
+# 4cd2c13cae1c4f91876bc2767c81d9a1
+msgid "In this figure, a public LB rule is created for the public IP 72.52.125.10 with public port 80 and private port 81. The LB rule, created on the VPC virtual router, is applied on the traffic coming from the Internet to the VMs on the Web tier. On the Application tier two internal load balancing rules are created. An internal LB rule for the guest IP 10.10.10.4 with load balancer port 23 and instance port 25 is configured on the VM, InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.4 with load balancer port 45 and instance port 46 is configured on the VM, InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.6, with load balancer port 23 and instance port 25 is configured on the VM, InternalLBVM2."
+msgstr ""
+
+#: ../../networking2.rst:6422
+# b3129b5c753047129a01b1ba3c4fede8
+msgid "|vpc-lb.png|"
+msgstr ""
+
+#: ../../networking2.rst:6429
+# 8b1b1a74897143cb88a7542e79cf51f3
+msgid "Internal LB and Public LB are mutually exclusive on a tier. If the tier has LB on the public side, then it can't have the Internal LB."
+msgstr ""
+
+#: ../../networking2.rst:6434
+# 4388c29d8e264047afa9fe7ff8b116fd
+msgid "Internal LB is supported just on VPC networks in CloudStack 4.2 release."
+msgstr ""
+
+#: ../../networking2.rst:6439
+# f446d0a1aad04939840f2e711a509b3e
+msgid "Only Internal LB VM can act as the Internal LB provider in CloudStack 4.2 release."
+msgstr ""
+
+#: ../../networking2.rst:6444
+# f4b320548bdb4614952985433f8b1177
+msgid "Network upgrade is not supported from the network offering with Internal LB to the network offering with Public LB."
+msgstr ""
+
+#: ../../networking2.rst:6449
+# 264141b663754516b518d1f6d1a96ebf
+msgid "Multiple tiers can have internal LB support in a VPC."
+msgstr ""
+
+#: ../../networking2.rst:6453
+# f09c422386a34597a8def34515b103c9
+msgid "Only one tier can have Public LB support in a VPC."
+msgstr ""
+
+#: ../../networking2.rst:6456
+# 028d12b705c040d4a796b5085738d685
+msgid "Enabling Internal LB on a VPC Tier"
+msgstr ""
+
+#: ../../networking2.rst:6460
+# 7c0d2274b60242a58ed2cf1355a72079
+msgid "Create a network offering, as given in :ref:`creating-net-offering-internal-lb`."
+msgstr ""
+
+#: ../../networking2.rst:6464
+# 6c4da6439e3f4b018afd1c51169ab257
+msgid "Create an internal load balancing rule and apply, as given in :ref:`create-int-lb-rule`."
+msgstr ""
+
+#: ../../networking2.rst:6470
+# 7632bb75de7b4419ab26471d1f3e2cdd
+msgid "Creating a Network Offering for Internal LB"
+msgstr ""
+
+#: ../../networking2.rst:6472
+# bb39964280e14e828cb77bd8faad4389
+msgid "To have internal LB support on VPC, either use the default offering, DefaultIsolatedNetworkOfferingForVpcNetworksWithInternalLB, or create a network offering as follows:"
+msgstr ""
+
+#: ../../networking2.rst:6537
+# 8f9488a3121d483a90d04b721d6d1d67
+msgid "**Supported Services**: Select Load Balancer. Select ``InternalLbVM`` from the provider list."
+msgstr ""
+
+#: ../../networking2.rst:6542
+# 10f1614fb17846fc84ab119ba2e48c82
+msgid "**Load Balancer Type**: Select Internal LB from the drop-down."
+msgstr ""
+
+#: ../../networking2.rst:6562
+# 1554f48553a24d8eb75e184a1a3dcaae
+msgid "Creating an Internal LB Rule"
+msgstr ""
+
+#: ../../networking2.rst:6564
+# 7c93f86fe3d04b018ebc0f755fdd3bd9
+msgid "When you create the Internal LB rule and applies to a VM, an Internal LB VM, which is responsible for load balancing, is created."
+msgstr ""
+
+#: ../../networking2.rst:6567
+# c341cb78685b4d799b920d6abfc1379d
+msgid "You can view the created Internal LB VM in the Instances page if you navigate to **Infrastructure** > **Zones** > <zone\\_ name> > <physical\\_network\\_name> > **Network Service Providers** > **Internal LB VM**. You can manage the Internal LB VMs as and when required from the location."
+msgstr ""
+
+#: ../../networking2.rst:6590
+# bb074ba85b95485ab2000aa11bbf8f33
+msgid "Locate the VPC for which you want to configure internal LB, then click Configure."
+msgstr ""
+
+#: ../../networking2.rst:6598
+# 9f89311df2d04728b293005448c4dc44
+msgid "Locate the Tier for which you want to configure an internal LB rule, click Internal LB."
+msgstr ""
+
+#: ../../networking2.rst:6601
+# a048cf82b55a4a65a79b907eddb27da1
+msgid "In the Internal LB page, click Add Internal LB."
+msgstr ""
+
+#: ../../networking2.rst:6605
+# ec4dcfcce0a24d839230f062df3b4b64
+msgid "In the dialog, specify the following:"
+msgstr ""
+
+#: ../../networking2.rst:6613
+# 74434a3d36fb484a804a01e12ce24764
+msgid "**Description**: A short description of the rule that can be displayed to users."
+msgstr ""
+
+#: ../../networking2.rst:6618
+# daed72af843943e9baccd05bcb786a21
+msgid "**Source IP Address**: (Optional) The source IP from which traffic originates. The IP is acquired from the CIDR of that particular tier on which you want to create the Internal LB rule. If not specified, the IP address is automatically allocated from the network CIDR."
+msgstr ""
+
+#: ../../networking2.rst:6624
+# 15b760898c8e4743b7a45bdb78cc5d29
+msgid "For every Source IP, a new Internal LB VM is created for load balancing."
+msgstr ""
+
+#: ../../networking2.rst:6629
+# 7d4fda85029c411f98060e303e433ebe
+msgid "**Source Port**: The port associated with the source IP. Traffic on this port is load balanced."
+msgstr ""
+
+#: ../../networking2.rst:6634
+# b8760e9c1eb746b98a4deb723cad698b
+msgid "**Instance Port**: The port of the internal LB VM."
+msgstr ""
+
+#: ../../networking2.rst:6655
+# eb41a8a1275d4f319cf708bbc6cbd615
+msgid "Adding a Port Forwarding Rule on a VPC"
+msgstr ""
+
+#: ../../networking2.rst:6745
+# b7b954709aca4ed4b65909249a1445cf
+msgid "**Public Port**: The port to which public traffic will be addressed on the IP address you acquired in the previous step."
+msgstr ""
+
+#: ../../networking2.rst:6750
+# 3457f6b6eb9945b2adb0a5de7deafea8
+msgid "**Private Port**: The port on which the instance is listening for forwarded public traffic."
+msgstr ""
+
+#: ../../networking2.rst:6755
+# 109d7b5b794343e3b14449585d750125
+msgid "**Protocol**: The communication protocol in use between the two ports."
+msgstr ""
+
+#: ../../networking2.rst:6760
+# a52983a3295b440e854b8e8de723ab47
+msgid "TCP"
+msgstr ""
+
+#: ../../networking2.rst:6764
+# a80d548790614268b9a37014436e3b33
+msgid "UDP"
+msgstr ""
+
+#: ../../networking2.rst:6768
+# 3045d1ed30694200ab89150942fe8a6a
+msgid "**Add VM**: Click Add VM. Select the name of the instance to which this rule applies, and click Apply."
+msgstr ""
+
+#: ../../networking2.rst:6771
+# 4b9ed6535e914dd89e1a04c8c2f345d7
+msgid "You can test the rule by opening an SSH session to the instance."
+msgstr ""
+
+#: ../../networking2.rst:6774
+# 4a6c93a072f04111a01f85167fd2755d
+msgid "Removing Tiers"
+msgstr ""
+
+#: ../../networking2.rst:6776
+# 5142d19ad4794b65970714b4e4bbbec5
+msgid "You can remove a tier from a VPC. A removed tier cannot be revoked. When a tier is removed, only the resources of the tier are expunged. All the network rules (port forwarding, load balancing and staticNAT) and the IP addresses associated to the tier are removed. The IP address still be belonging to the same VPC."
+msgstr ""
+
+#: ../../networking2.rst:6802
+# 7c041faaebfa4ddab0237d7749ac57b0
+msgid "The Configure VPC page is displayed. Locate the tier you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:6807
+# df27c86ec4a94161b3370aae61a474f0
+msgid "Select the tier you want to remove."
+msgstr ""
+
+#: ../../networking2.rst:6811
+# 36316512ad134fdd8cf52cee54ea5230
+msgid "In the Network Details tab, click the Delete Network button. |del-tier.png|"
+msgstr ""
+
+#: ../../networking2.rst:6814
+# 50fe8c3d59b048c5b83145acbe8be4e5
+msgid "Click Yes to confirm. Wait for some time for the tier to be removed."
+msgstr ""
+
+#: ../../networking2.rst:6817
+# 2946ed6a189c43f58b6c443a883de36f
+msgid "Editing, Restarting, and Removing a Virtual Private Cloud"
+msgstr ""
+
+#: ../../networking2.rst:6819
+# 41e51cc9e9d14164a66fb7e95f9f8a12
+msgid "Ensure that all the tiers are removed before you remove a VPC."
+msgstr ""
+
+#: ../../networking2.rst:6838
+# 98e5e7fe7bff4cb18c826b8a17fbca71
+msgid "Select the VPC you want to work with."
+msgstr ""
+
+#: ../../networking2.rst:6842
+# fdc4b5db10a245f68c46b4793a5b052e
+msgid "In the Details tab, click the Remove VPC button |remove-vpc.png|"
+msgstr ""
+
+#: ../../networking2.rst:6844
+# 3fabd3a8fb6b4546887df7e7f8c4212c
+msgid "You can remove the VPC by also using the remove button in the Quick View."
+msgstr ""
+
+#: ../../networking2.rst:6847
+# 8f6ce6f0fc7943e8965aeb7c157eef28
+msgid "You can edit the name and description of a VPC. To do that, select the VPC, then click the Edit button. |edit-icon.png|"
+msgstr ""
+
+#: ../../networking2.rst:6850
+# 44868ef425a9478c9a51b13b823cb75d
+msgid "To restart a VPC, select the VPC, then click the Restart button. |restart-vpc.png|"
+msgstr ""
+
+#: ../../networking2.rst:6854
+# f535c4d4c6e542569b645467558a84ba
+msgid "Persistent Networks"
+msgstr ""
+
+#: ../../networking2.rst:6856
+# ac16a1f817024aa4ba3804fcab51f851
+msgid "The network that you can provision without having to deploy any VMs on it is called a persistent network. A persistent network can be part of a VPC or a non-VPC environment."
+msgstr ""
+
+#: ../../networking2.rst:6860
+# 69a29ed2704f4f48b0796699ad7a36eb
+msgid "When you create other types of network, a network is only a database entry until the first VM is created on that network. When the first VM is created, a VLAN ID is assigned and the network is provisioned. Also, when the last VM is destroyed, the VLAN ID is released and the network is no longer available. With the addition of persistent network, you will have the ability to create a network in CloudStack in which physical devices can be deployed without having to run any VMs. Additionally, you can deploy physical devices on that network."
+msgstr ""
+
+#: ../../networking2.rst:6869
+# 58f4be07725f415581616cb03772a7a7
+msgid "One of the advantages of having a persistent network is that you can create a VPC with a tier consisting of only physical devices. For example, you might create a VPC for a three-tier application, deploy VMs for Web and Application tier, and use physical machines for the Database tier. Another use case is that if you are providing services by using physical hardware, you can define the network as persistent and therefore even if all its VMs are destroyed the services will not be discontinued."
+msgstr ""
+
+#: ../../networking2.rst:6879
+# 8ff007bee6954fe199b3c83d78392acf
+msgid "Persistent Network Considerations"
+msgstr ""
+
+#: ../../networking2.rst:6883
+# f6f834bfef49425085d2d0742d6ef874
+msgid "Persistent network is designed for isolated networks."
+msgstr ""
+
+#: ../../networking2.rst:6887
+# 0bb5d0eb31464beaa3c07b2ff9af3aa2
+msgid "All default network offerings are non-persistent."
+msgstr ""
+
+#: ../../networking2.rst:6891
+# 5051557b950f477e8d115a69bf8150d4
+msgid "A network offering cannot be editable because changing it affects the behavior of the existing networks that were created using this network offering."
+msgstr ""
+
+#: ../../networking2.rst:6897
+# 593697221e614fe980bca6c00979e531
+msgid "When you create a guest network, the network offering that you select defines the network persistence. This in turn depends on whether persistent network is enabled in the selected network offering."
+msgstr ""
+
+#: ../../networking2.rst:6903
+# 34302861eff548dd9e9007020f1c927b
+msgid "An existing network can be made persistent by changing its network offering to an offering that has the Persistent option enabled. While setting this property, even if the network has no running VMs, the network is provisioned."
+msgstr ""
+
+#: ../../networking2.rst:6910
+# e3974307d7cd464eb0a6028ee8f57e4b
+msgid "An existing network can be made non-persistent by changing its network offering to an offering that has the Persistent option disabled. If the network has no running VMs, during the next network garbage collection run the network is shut down."
+msgstr ""
+
+#: ../../networking2.rst:6917
+# 1c9032badc034107b57250169a03a890
+msgid "When the last VM on a network is destroyed, the network garbage collector checks if the network offering associated with the network is persistent, and shuts down the network only if it is non-persistent."
+msgstr ""
+
+#: ../../networking2.rst:6923
+# 56e305bc255e4c999e504e5acb010e4f
+msgid "Creating a Persistent Guest Network"
+msgstr ""
+
+#: ../../networking2.rst:6925
+# 8ce284f6e33a44e5860a579e00f4fc80
+msgid "To create a persistent network, perform the following:"
+msgstr ""
+
+#: ../../networking2.rst:6929
+# e3ce54a0de2342309210a549828f25b0
+msgid "Create a network offering with the Persistent option enabled."
+msgstr ""
+
+#: ../../networking2.rst:6931
+# 916c1c8c0ef34df2868a5a38c4dd609a
+msgid "See `\"Creating a New Network Offering\" <networking.html#creating-a-new-network-offering>`_."
+msgstr ""
+
+#: ../../networking2.rst:6935
+# 2fd5e35855fe4fa4bae6d7cc0d53b7d8
+msgid "Select Network from the left navigation pane."
+msgstr ""
+
+#: ../../networking2.rst:6939
+# 37e16c8d0d9044dbb0f2d02677062c8d
+msgid "Select the guest network that you want to offer this network service to."
+msgstr ""
+
+#: ../../networking2.rst:6944
+# 5fbd5c95b15941c29f95b337f8ebade8
+msgid "Click the Edit button."
+msgstr ""
+
+#: ../../networking2.rst:6948
+# 706e3f3239cb45f2a6f669847cf5c0ff
+msgid "From the Network Offering drop-down, select the persistent network offering you have just created."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/networking_and_traffic.pot b/source/adminguide/locale/pot/networking_and_traffic.pot
new file mode 100644
index 0000000..303e0c6
--- /dev/null
+++ b/source/adminguide/locale/pot/networking_and_traffic.pot
@@ -0,0 +1,7535 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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_and_traffic.rst:18
+# 2e88968824744a699d5b9e641bba935c
+msgid "Managing Networks and Traffic"
+msgstr ""
+
+#: ../../networking_and_traffic.rst:20
+# 5f4766ac0c9e42fb808ce551ae256f24
+msgid "In a CloudStack, guest VMs can communicate with each other using shared infrastructure with the security and user perception that the guests have a private LAN. The CloudStack virtual router is the main component providing networking features for guest traffic."
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:18
+# 547c4ea0a4df4369904d3e89102a2ff0
+msgid "Guest Traffic"
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:20
+# 66d2b2ce8a6e4cd2a1129c71097c9ffd
+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
+# d283edc27a994358b1d82be3efe292b3
+msgid "See a typical guest traffic setup given below:"
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:27
+# 585953ea4f7741d289a4d3930fbea7f8
+msgid "|guest-traffic-setup.png|"
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:29
+# 231054f3bb304ca8b569aae0ca379d62
+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 router. Its eth2 interface is assigned a public IP address for public traffic. If multiple public VLAN is used, the router will have multiple public interfaces."
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:40
+# fac52c70fa3c497faa044acd49d26532
+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
+# 60254b35a5ca48dcb79bab826da4a5ab
+msgid "Source NAT is automatically configured in the virtual router to forward outbound traffic for all guest VMs"
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:18
+# ffe1b004a96f43bc974d111d3a433cce
+msgid "Networking in a Pod"
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:20
+# b0f1a12d5e7543ab99e1e3a70c348c57
+msgid "The figure below illustrates network setup within a single pod. The hosts are connected to a pod-level switch. At a minimum, the hosts should have one physical uplink to each switch. Bonded NICs are supported as well. The pod-level switch is a pair of redundant gigabit switches with 10 G uplinks."
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:26
+# fa46cc84fe1b4d539c299613f2ea90f8
+msgid "|networksinglepod.png|"
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:28
+# 0b80653796454fe7b33fc3de812c6200
+msgid "Servers are connected as follows:"
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:30
+# 91c1e31402e44614ac425a77ffd95c12
+msgid "Storage devices are connected to only the network that carries management traffic."
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:33
+# 7c9c0e94df7a4c19b6cd106477d3162b
+msgid "Hosts are connected to networks for both management traffic and public traffic."
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:36
+# ab64d976f00e480885bb92e5d544d3ec
+msgid "Hosts are also connected to one or more networks carrying guest traffic."
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:39
+# 2d032fc9112345a8b2b9c78d5f64a723
+msgid "We recommend the use of multiple physical Ethernet cards to implement each network interface as well as redundant switch fabric in order to maximize throughput and improve reliability."
+msgstr ""
+
+#: ../../networking/networking_in_zone.rst:18
+# 34f26bc9bb954421b5a49ea5148512a1
+msgid "Networking in a Zone"
+msgstr ""
+
+#: ../../networking/networking_in_zone.rst:20
+# 42aa6b7f996f49748a02f70fa69cac5d
+msgid "The following figure illustrates the network setup within a single zone."
+msgstr ""
+
+#: ../../networking/networking_in_zone.rst:22
+# cec13401ef5743db802dc373651f4cee
+msgid "|networksetupzone.png|"
+msgstr ""
+
+#: ../../networking/networking_in_zone.rst:24
+# caf254a7b27b483ab945007e27ab2454
+msgid "A firewall for management traffic operates in the NAT mode. The network typically is assigned IP addresses in the 192.168.0.0/16 Class B private address space. Each pod is assigned IP addresses in the 192.168.\\*.0/24 Class C private address space."
+msgstr ""
+
+#: ../../networking/networking_in_zone.rst:29
+# 0de7f4a8ad2349cc87a373a814392846
+msgid "Each zone has its own set of public IP addresses. Public IP addresses from different zones do not overlap."
+msgstr ""
+
+#: ../../networking/basic_zone_config.rst:19
+# 8133c02743444c1691e584fe82e3dbdb
+msgid "Basic Zone Physical Network Configuration"
+msgstr ""
+
+#: ../../networking/basic_zone_config.rst:21
+# 501779cb0c9441e4a29799acb6518b3e
+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 ""
+
+#: ../../networking/advanced_zone_config.rst:19
+# 309e851c308a4e6eb88d0b9cb9eca1a4
+msgid "Advanced Zone Physical Network Configuration"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:21
+# 5ba22edac905490bac4351986297202e
+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
+# 7433a105cf0f4c4a8b5eb2d1b71b5278
+msgid "Configure Guest Traffic in an Advanced Zone"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:29
+# 0479d8eccf0646bda9f39cac51ca890c
+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
+# 6a02a9096d534a41aa433f728dd55749
+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
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:145
+# 9d184022aba349b2aa9aeb49c5222497
+# e23a8b99ae3d4beb87a9db4e87291025
+# 367ee4d166f843e6b790c71cbbf8f9e3
+msgid "Click the Network tab."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:37
+#: ../../networking/advanced_zone_config.rst:89
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:147
+# 3245c61546fe4a81bc5e6e8a09167804
+# aeb508d106f6462bbdae174ca0a17b83
+# b07a9c22d66f4cd59a846a846778af53
+msgid "Click Add guest network."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:39
+# be8bee6943514afda63cb052034b5613
+msgid "The Add guest network window is displayed:"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:41
+# 1c4523333dc64212b845c2b6912c260c
+msgid "|addguestnetwork.png|"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:43
+#: ../../networking/remote_access_vpn.rst:311
+#: ../../networking/virtual_private_cloud_config.rst:189
+# acadf5b43bd44355836e260ef18944cb
+# 914acc88287948198f6d2e928d524cff
+# 00444541c712470cabb10e4c18d44754
+msgid "Provide the following information:"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:45
+# 3a472c2f7bd74e88894a25b50b2ecc0b
+msgid "**Name**: The name of the network. This will be user-visible"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:47
+# cd0d4d5ebb2843508a34eef3fa3cbf95
+msgid "**Display Text**: The description of the network. This will be user-visible"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:50
+# 458b580931c147f39c8754144178743c
+msgid "**Zone**: The zone in which you are configuring the guest network."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:52
+# 5a598415cdd64826baeb7bf89f1d991e
+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
+# 1bd47cc800e74d299fd0a2f14dc79b82
+msgid "**Guest Gateway**: The gateway that the guests should use"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:57
+# dbd235f763be4ac3bd961dfeab6a4119
+msgid "**Guest Netmask**: The netmask in use on the subnet the guests will use"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:60
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:115
+#: ../../networking/portable_ips.rst:84
+#: ../../networking/multiple_subnets_in_shared_network.rst:95
+#: ../../networking/security_groups.rst:72
+#: ../../networking/global_server_load_balancing.rst:371
+#: ../../networking/ip_forwarding_and_firewalling.rst:215
+#: ../../networking/remote_access_vpn.rst:402
+#: ../../networking/remote_access_vpn.rst:425
+#: ../../networking/virtual_private_cloud_config.rst:211
+#: ../../networking/virtual_private_cloud_config.rst:281
+#: ../../networking/virtual_private_cloud_config.rst:455
+#: ../../networking/virtual_private_cloud_config.rst:479
+#: ../../networking/persistent_networks.rst:94
+# 7a600295ac7141be85b91494277f8bae
+# 1699ac2b1b66466896e3e308100bc131
+# c2b6ddd6457b41cda3df2cbb62cbb901
+# 3929bccca11f489993ac83ea79cc8f48
+# c6b55626cac14e82aa807bfced97b64d
+# 46ab1fed30c44cb386441db1762dd430
+# 4562b7f8a5e64cf78cdd7c58d62866fc
+# 692b7464148b43a49edb927fbd74fd4b
+# 70bd2e1ea0524a7882ca8a0d1d607829
+# a6fb58ce33b74a20894b08e4aeffb48f
+# 3c8f6b6fdfc447fb8ee7f3a409e82bad
+# 7673a522d97348a9bc4533f2c623e3b6
+# e92a6822a63b483d92dfedd0eb104b22
+# d8d73b45f64a4ba0a15a6bf8124841f0
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:64
+# c735b3c2a79d4a97ba3b2798068b9032
+msgid "Configure Public Traffic in an Advanced Zone"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:66
+# b6188c4a11a04e4da53e69931cea7e92
+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
+# 382eb9f366b44454835a00e621aa1743
+msgid "Configuring a Shared Guest Network"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:73
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:54
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:131
+# 017873e7ecfe4402a18cf99f80504c6b
+# a45daa5eec1d4fa68d75831b169fafa5
+# b177d05e7fb54f8ab7429856f854dd16
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:75
+#: ../../networking/multiple_subnets_in_shared_network.rst:54
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:133
+# 84a0ef2ad9f943ad9f91eb6a8abb8ae7
+# 76b78351191646ffa98f8ec8e59fea01
+# ef875cadd3c647089970c4b011189042
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:77
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:135
+# 06247e8726024f7098ba1a2c8ffb7cd9
+# 4d47e34008e44518b3ce4ffc1d522b5e
+msgid "On Zones, click View More."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:79
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:137
+# 11a261c7ce9a4280b2283b3420540729
+# a53663a4596d4418b2447b2f34253c13
+msgid "Click the zone to which you want to add a guest network."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:81
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:62
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:132
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:139
+# ad879d34c24644c6be82095823dd2634
+# f4034b1a820b425bbbd9b51218978bac
+# dda2aaaac56e490da82fb8570abcec7c
+# 7ee99e2d45ac49679a2ffc018fb9bada
+msgid "Click the Physical Network tab."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:83
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:141
+# 8e7c54c3dff94e4c975465a247fdc749
+# 6904ead432c948b1a353d1a14cf24ba3
+msgid "Click the physical network you want to work with."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:85
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:143
+# 5198c123311c4dedb764b0fad9b75511
+# b6b304bb36064d9795035a047d554897
+msgid "On the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:91
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:149
+# 9b0560860e8142b6acacce6dee68f77d
+# f66ffb16e9e34d2fab95288ecddbc072
+msgid "The Add guest network window is displayed."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:93
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:79
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:89
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:107
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:142
+#: ../../networking/portable_ips.rst:70
+#: ../../networking/multiple_subnets_in_shared_network.rst:75
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:151
+#: ../../networking/external_firewalls_and_load_balancers.rst:482
+#: ../../networking/global_server_load_balancing.rst:393
+#: ../../networking/virtual_private_cloud_config.rst:248
+#: ../../networking/virtual_private_cloud_config.rst:539
+#: ../../networking/virtual_private_cloud_config.rst:1062
+#: ../../networking/virtual_private_cloud_config.rst:1330
+# 177f27f031a444b2a8fd7dd381980b4d
+# bf9352536eb942a18db080fc500523d3
+# a08d4b6ba13540ceab3e8058b95f89af
+# bc8ca26c46054b58b949250071678da5
+# 65686255f3e34e33b7c9014b22a1f32c
+# 0d69bb44a42b4273942af07cece87f40
+# 40882d4726394e6eabd4a92f88844717
+# df42ee8c70dc4c80884bb2241dce3ff9
+# 392bb66c4eed477b8f17b7327c094d70
+# 67322aa6283c41329898fae4fcd9d14a
+# f8a7557a036c4c2d9e8a1664f9788eb0
+# 15e16203d42441acbfb55f6d515c2648
+# 7dbdb60b7de340c08a41ac492f5f5f2b
+# c11b631f982340159764b1fc93b73259
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:95
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:153
+# 6554135d72104186ad415b989326d68a
+# f5bee2ab4a8a4cd1bb25c20ef7021f7c
+msgid "**Name**: The name of the network. This will be visible to the user."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:97
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:156
+# b63b119a113e499fb649c6b668452512
+# 53f9619369324f10bbc8f0dfb003c5af
+msgid "**Description**: The short description of the network that can be displayed to users."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:100
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:159
+# 7623ee3426cd4a4b8719ca1027787ee0
+# fa610595c19f43feb0a9916b4c61517e
+msgid "**VLAN ID**: The unique ID of the VLAN."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:102
+# a6a3c73efe124f6690c9949d7466b2cd
+msgid "**Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:105
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:167
+# eb5d4e3b37bb4d94bd1e4ce02cf03368
+# 8401ce13c8b14fc7ba27b4342afc3f7f
+msgid "**Scope**: The available scopes are Domain, Account, Project, and All."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:108
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:170
+# 484bd18b48f64d8190817eb10bf25d94
+# 7991b529beef453ba5728f8ca2b2b220
+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
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:176
+# 252ca851074346a6be3e6f4c74f7834d
+# 621835256ebd4c57a89c9353ef9852f2
+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
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:180
+# 0ab56139ecb94d0e8c9655e557cb946c
+# d4a5c2d9539246839f4dd99383968ef9
+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
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:184
+# 2b9a0513ff7e422db20b3251b2fbe195
+# 0f2a1593be4f484781fdadc2f41437da
+msgid "**All**: The guest network is available for all the domains, account, projects within the selected zone."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:125
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:187
+# ca6ea5abd11c4e1788e84dfe1bff99a2
+# d3110bc74ceb49d3be22fc9aae58619b
+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
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:191
+# f51f569ac91a494caa7f8c799bfdbb9f
+# a9df4480acb64d5bbd3f3ceef50ef146
+msgid "**Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:131
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:193
+# 1a04acb9a38148f68b32c27969c45f73
+# 283222bd73704d83b1a3edb949df0350
+msgid "**Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:133
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:195
+# 615ae59795614770a2544f5a3b35cd87
+# 3564dbe5dcda4549a0101e20522adce2
+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
+# 83b96bd50ac546028d9179711930d8b4
+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
+# e8f7fd43c9964fb39020455720c2ace1
+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
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:198
+# 447ec4231b6249d0a2be7e648cf05a4b
+# 9f34c3ebe1d44cc59d6246b9e1ef1cc6
+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
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:202
+#: ../../networking/global_server_load_balancing.rst:415
+#: ../../networking/global_server_load_balancing.rst:439
+#: ../../networking/remote_access_vpn.rst:555
+# 47c08e953e5a4dc6a1fea963aef82e35
+# eda271a950a6423f91f6019045850a96
+# 6866ffd602874da0a27c9d867eef7121
+# 0d2313e6a2b24e99a9800598ca9f6d0a
+# 210ec4b443e34cedbeb2ac91183bbc9e
+msgid "Click OK to confirm."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:18
+# 62aeac41fec848808050e2e871a2b129
+msgid "Using Multiple Guest Networks"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:20
+# 173b4dafa8a24c8d8ef490a9e5d1a2a3
+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
+# c8b83803c190449586b842e47655e008
+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
+# 71b0ed98702b4b929a15ba55f3aa6352
+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
+# 849cc36464bd447d99a2d270e0b8c0b3
+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
+# a3fc8a922f68476db11bacc83c025d3d
+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
+#: ../../networking/ip_reservation_in_guest_networks.rst:106
+#: ../../networking/portable_ips.rst:58
+#: ../../networking/portable_ips.rst:90
+#: ../../networking/multiple_subnets_in_shared_network.rst:52
+#: ../../networking/security_groups.rst:62
+#: ../../networking/security_groups.rst:124
+#: ../../networking/external_firewalls_and_load_balancers.rst:255
+#: ../../networking/acquiring_an_ip_address.rst:20
+#: ../../networking/releasing_an_ip_address.rst:24
+#: ../../networking/static_nat.rst:36
+#: ../../networking/ip_forwarding_and_firewalling.rst:59
+#: ../../networking/ip_forwarding_and_firewalling.rst:132
+#: ../../networking/ip_forwarding_and_firewalling.rst:245
+#: ../../networking/remote_access_vpn.rst:59
+#: ../../networking/remote_access_vpn.rst:301
+#: ../../networking/remote_access_vpn.rst:411
+#: ../../networking/remote_access_vpn.rst:431
+#: ../../networking/remote_access_vpn.rst:493
+#: ../../networking/remote_access_vpn.rst:624
+#: ../../networking/virtual_private_cloud_config.rst:179
+#: ../../networking/virtual_private_cloud_config.rst:223
+#: ../../networking/virtual_private_cloud_config.rst:331
+#: ../../networking/virtual_private_cloud_config.rst:380
+#: ../../networking/virtual_private_cloud_config.rst:492
+#: ../../networking/virtual_private_cloud_config.rst:662
+#: ../../networking/virtual_private_cloud_config.rst:729
+#: ../../networking/virtual_private_cloud_config.rst:788
+#: ../../networking/virtual_private_cloud_config.rst:848
+#: ../../networking/virtual_private_cloud_config.rst:1014
+#: ../../networking/virtual_private_cloud_config.rst:1227
+#: ../../networking/virtual_private_cloud_config.rst:1282
+#: ../../networking/virtual_private_cloud_config.rst:1360
+#: ../../networking/virtual_private_cloud_config.rst:1388
+# dc6276841e84471ba268d113e94e1fde
+# cbab5080c8724ae6b32d638711c47ad3
+# 48fc29cc7efc4b409a45c98ead6968af
+# ace2e79a21274181a0e6a1418b773520
+# 6befffe2a21747639acd37de4675a94a
+# f5963e2398134322866f292a2ba5637c
+# 551332081c79467bb0b0ae8d270e12fc
+# ecb9ef417cf8480db8b57ca2d9f61454
+# ce46c3a278f44eb5b1e7654fa8161e03
+# 9424276887a84ee99fd0b5822bdcd91a
+# cf03db0555ba4247b9b9cf2b658dc39c
+# 3e08d28b8e2f41d18f75caa20d66f640
+# 16776cbc4ef94f86a8459cd47cf975b6
+# 5d6031b242154874a2eea237547f4e27
+# 4556ff5dc1a74038a41b53936c78f484
+# 671400e41c7c4103bbcba44d13f5f1da
+# 62daba2f10ce4203b9a4ace43acaf3e6
+# 349c3fc0ae0045c091b01248f7139bd9
+# 6488b7ea43c743ea94940e1c1f3f2898
+# 3eb6a0e839144aac93bd3202f87081a4
+# 16a312e861604ecca8b56044c71267a5
+# 6a8b51d9d05c4ac48c274e364f981a83
+# d5aee6dabdd249118c7128383890359b
+# 5c15fdde88e743f4b18aea3fe127d933
+# 7a23456b027045198970bd22c7e8c26d
+# 2e31addff9374029b171be7e6159ce7e
+# 4e46d0a70f45414098f422f177f3ac81
+# 285f7a9fc04f4d6489fda4d6a5f605bb
+# 6803fb7ef5e947a19da33579f371d0fa
+# 989f403b307946939b500439893373fa
+# f3ea7727060d4b25b4a675666aa53047
+# 1c9c88a759cd4868990e4b477dc4a97f
+# 8fac984de8c04571aed052d41660d304
+# 155c85bc6c6c471c8933826c53d412db
+# a87fa80f420b452a9c4e0fb44344cd64
+# de7a6e86366d4763b6ed6974061246e9
+# 8e1be4aa91664f038b1f00940c6fef85
+# a9f7303f7b5c4984a44ef3c6a938123e
+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
+#: ../../networking/ip_reservation_in_guest_networks.rst:108
+#: ../../networking/portable_ips.rst:92
+#: ../../networking/security_groups.rst:64
+#: ../../networking/external_firewalls_and_load_balancers.rst:257
+#: ../../networking/acquiring_an_ip_address.rst:22
+#: ../../networking/releasing_an_ip_address.rst:26
+#: ../../networking/static_nat.rst:38
+#: ../../networking/ip_forwarding_and_firewalling.rst:61
+#: ../../networking/ip_forwarding_and_firewalling.rst:134
+#: ../../networking/remote_access_vpn.rst:303
+#: ../../networking/remote_access_vpn.rst:413
+#: ../../networking/remote_access_vpn.rst:433
+#: ../../networking/remote_access_vpn.rst:495
+#: ../../networking/remote_access_vpn.rst:626
+#: ../../networking/virtual_private_cloud_config.rst:181
+#: ../../networking/virtual_private_cloud_config.rst:225
+#: ../../networking/virtual_private_cloud_config.rst:333
+#: ../../networking/virtual_private_cloud_config.rst:382
+#: ../../networking/virtual_private_cloud_config.rst:494
+#: ../../networking/virtual_private_cloud_config.rst:664
+#: ../../networking/virtual_private_cloud_config.rst:731
+#: ../../networking/virtual_private_cloud_config.rst:790
+#: ../../networking/virtual_private_cloud_config.rst:850
+#: ../../networking/virtual_private_cloud_config.rst:1016
+#: ../../networking/virtual_private_cloud_config.rst:1229
+#: ../../networking/virtual_private_cloud_config.rst:1284
+#: ../../networking/virtual_private_cloud_config.rst:1362
+#: ../../networking/virtual_private_cloud_config.rst:1390
+# 237757a1c35441d4b6a1d0138d51de32
+# 39b4377eadca44f88700dca104d2f2a4
+# 14e144b6e7d84af79103518642863237
+# e38926ea76d24deabf34f94cc6156141
+# 1cafa5021f254ccdb3e66342906cbbe0
+# 76644abeaf9b49d48e5c26fd3863d65d
+# fd119509867a413eb5b071e9da496e8e
+# 957b74b12b1a45c7b9b8114b38f97d77
+# aa4565d6e2ed407b960640041eb584ff
+# 4e76e138c9884ac8beba173f7412d536
+# 44488e4d095a4f2d8266449c8307fc21
+# af7438793b9e44748cabc8348e59fda1
+# 4eb14251b140410c9af761d030914dc5
+# 60c4993c8a9a4e568ee599adb94f496d
+# ac22aded37484d4f98a0e5a40819d801
+# 8cc4478d868544b9848e14dfbd88437c
+# 7c473fc1dc29485bab80620cb5516658
+# 5719d26cc6b34a00b95be2ce35247df4
+# 10dbf0d03759490a8446988e520c079c
+# 92cb7c01ff9f4be098792e0ef2848938
+# fd1c21fdf57f4352984d33f74a0ffe94
+# 10c9ca3bb4e64794961df411c87283c0
+# 9ceabecc68364512ba46aba32daf9204
+# d77f1f6f348745e08a97c31b73820e52
+# f7bed0f61bd84981b3ec3692340f0005
+# 9981e33a734c445c98a725f067fc9940
+# e068bf6b3bc14e1b90f2154ebf50cc7f
+# 37ca9de5ef034ad4a025068c67b7cda8
+# 3f72ad0b7cf24c6cad9063dd0771a6b0
+# 52a95f6853b440feb680fdfbf7854d1e
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:51
+# cb6079f81a4a444c8445b03dfffb3384
+msgid "Click Add guest network. Provide the following information:"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:53
+# a733015f94ce486a85c1b03cddfbc38d
+msgid "**Name**: The name of the network. This will be user-visible."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:55
+# c09b04d766c44686adfb027006335ba6
+msgid "**Display Text**: The description of the network. This will be user-visible."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:58
+# 2c86bf84ff20496e9c0dbae8475b8796
+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
+# afa6888ba15346988e310755527a9c8c
+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
+# 7f1d89fa4b5b43eabe3a6dcd6a33dfeb
+msgid "**Guest Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:69
+# b882e804c5a845c2bb51f84c46f7e4b2
+msgid "**Guest Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:72
+#: ../../networking/remote_access_vpn.rst:186
+# fae38490ef9a46b1849e4b2335cc0fed
+# 78b272d2f17d4c2aa5e3c38757550038
+msgid "Click Create."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:76
+# 89ec799633d344d9a83b6db46a6c828c
+msgid "Reconfiguring Networks in VMs"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:78
+# a88f5c6d61374a3b928e78e6b1ea34aa
+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
+# 2316dff2f40f4d3f86f201bc60758648
+msgid "This feature is supported on XenServer, VMware, and KVM hypervisors."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:88
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:97
+#: ../../networking/external_firewalls_and_load_balancers.rst:428
+# 616dba5e33b041d58b10b5d6e07ee798
+# 537bba5fd9ca4e46a540acdaa254af70
+# cedaba73cb0d47a88420f975227d5918
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:90
+# 96d0ba198631458b9ed9d4fa9ed7a7e8
+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
+# 0329f8bc61c245c990fbec99fc953f92
+msgid "Adding a Network"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:99
+#: ../../networking/multiple_guest_networks.rst:137
+#: ../../networking/multiple_guest_networks.rst:155
+# 97b216f50e31423b9810c721a305ff6a
+# 9a2142ffcdd841c6add827da072540a3
+# 472370d3518e4d43897027152ff4f4a4
+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
+# a42801e9f96a4b12aef748033faea01f
+# 81f21ab3baef4f45b105fc9089d4e0d3
+# 635dc740070544bc8307380af26d34fa
+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
+# 6bac6d526e3d4904baf4586d1d888847
+# fc1fad0459ba46678afe706a5a01d3e2
+# 1975c5cefdba4f0e8aeb59dd9eace947
+msgid "Click the NICs tab."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:105
+# 4fab29c3388c444694883cc767e38d1a
+msgid "Click Add network to VM."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:107
+# 2607dcbcf15f4c8dafde44a5570a2766
+msgid "The Add network to VM dialog is displayed."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:109
+# 078937d5a79043d497e0b24671ff352d
+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
+# 45834b3a55d14caebf167b7bd28ebd2f
+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
+# 2e97354cbec940b796eec8b025dc982e
+msgid "ID"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:117
+# 122b599d9d7d4f8c8fb462bd0c5b5f2e
+msgid "Network Name"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:119
+# 6766a85b557b460c8955aa3fb09bfb8d
+msgid "Type"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:121
+#: ../../networking/remote_access_vpn.rst:481
+#: ../../networking/remote_access_vpn.rst:561
+# 3bd581b01cb243438e2e27273acdbedf
+# 5933f737b419411fa7207a44b3bdea6a
+# 940af38d78dc494ab2ad01f61aafe5d1
+msgid "IP Address"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:123
+#: ../../networking/remote_access_vpn.rst:563
+# daa389d546724738b57068be58e101d3
+# 95d8f0e06cb94200ae5681c2d2a96628
+msgid "Gateway"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:125
+# c39faf6b191042feb2d8ef693d09e473
+msgid "Netmask"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:127
+# 84a7fde285214a59a6105b424d0e3616
+msgid "Is default"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:129
+# 7689a2a82f5c496e89049b4c6c30a8a0
+msgid "CIDR (for IPv6)"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:133
+# 8d0db3320eaf4c88be0ac3e518bfb002
+msgid "Removing a Network"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:143
+# 5aa8d15ef25e4b49b6eebcd1275b2a27
+msgid "Locate the NIC you want to remove."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:145
+# 839f1682ea074a07990190ec500a473f
+msgid "Click Remove NIC button. |remove-nic.png|"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:147
+#: ../../networking/multiple_guest_networks.rst:165
+# 00cc631ddf71493784b992fb54efb226
+# aba902f0e4d940768424cda703f41a00
+msgid "Click Yes to confirm."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:151
+# 4628fde155ff46dab3f60b7acb743a7a
+msgid "Selecting the Default Network"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:161
+# cd2ff5578eb8448fb8960115c581a240
+msgid "Locate the NIC you want to work with."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:163
+# b267fb4c8ea944a896d8494196363127
+msgid "Click the Set default NIC button. |set-default-nic.png|."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:168
+# b1e087e064cd4c8ebe77979cdeb59029
+msgid "Changing the Network Offering on a Guest Network"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:170
+# 98f57e4d0fe143c39ec77fdc7afbbc1a
+msgid "A user or administrator can change the network offering that is associated with an existing guest network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:175
+# 8c3a2eaed1fa46a09bab8a2fb9394033
+msgid "If you are changing from a network offering that uses the CloudStack virtual router to one that uses external devices as network service providers, you must first stop all the VMs on the network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:181
+#: ../../networking/ip_reservation_in_guest_networks.rst:110
+# deb6cb39e0f942ef8537ff0805aee20c
+# d19c0a1a49dd41129e10a67ab3d452dc
+msgid "Click the name of the network you want to modify."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:183
+# ecccedf20bf340e2ba7ead538934109d
+msgid "In the Details tab, click Edit. |edit-icon.png|"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:185
+# edc1fb28dc1b449cacf52a30f5e913b6
+msgid "In Network Offering, choose the new network offering, then click Apply."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:188
+# 19df93b01dc24fd594f644c960aac9d3
+msgid "A prompt is displayed asking whether you want to keep the existing CIDR. This is to let you know that if you change the network offering, the CIDR will be affected."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:192
+# 31721f214c5b41e0902e0192cb732fd2
+msgid "If you upgrade between virtual router as a provider and an external network device as provider, acknowledge the change of CIDR to continue, so choose Yes."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:196
+# 3bd6b923a2f64dfe984b12e9d7a9989a
+msgid "Wait for the update to complete. Don't try to restart VMs until the network change is complete."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:199
+# 33336e86a2f748f6a87662d9f20dc804
+msgid "If you stopped any VMs, restart them."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:18
+# 685effa0d8104882b0a30dc6b824029a
+msgid "IP Reservation in Isolated Guest Networks"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:20
+# 359e7f6b58f44d209b72518d79eaa4a1
+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
+# e20dc9218ab14a249b1976460b6ff50e
+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 called Reserved IP Range. When IP reservation is configured, the administrator can add additional VMs or physical servers that are not part of CloudStack to the same network and assign them the Reserved IP addresses. CloudStack guest VMs cannot acquire IPs from the Reserved IP Range."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:43
+# aa0353a0869b430a9e00cc950d697674
+msgid "IP Reservation Considerations"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:45
+# 22d783b25a1a4a81835a9f474578360d
+msgid "Consider the following before you reserve an IP range for non-CloudStack machines:"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:48
+# 0b76d0acbe274475b3d5501612754809
+msgid "IP Reservation is supported only in Isolated networks."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:50
+# 5bc6f26160614e04a5e091d9ce7f7b41
+msgid "IP Reservation can be applied only when the network is in Implemented state."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:53
+# ab5412a6ce1d4c0cb3eef49dfab3e255
+msgid "No IP Reservation is done by default."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:55
+# 428a3fe4ee25419a968877cb3d6e16e8
+msgid "Guest VM CIDR you specify must be a subset of the network CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:57
+# 172c915bb06f46d498d3fc10f4f49011
+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
+# 0e5b7bff020d494b9f4e85c641380036
+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
+# dd5d34dcc85b438e9f317da8db24673b
+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
+# 56f3f34b92224637b58c7c86bb310fd1
+msgid "For example, the following table describes three scenarios of guest network creation:"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# 96cbc8ccee6044a3a4e224d82dda12dd
+msgid "Case"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+#: ../../networking/remote_access_vpn.rst:122
+#: ../../networking/remote_access_vpn.rst:456
+#: ../../networking/remote_access_vpn.rst:519
+#: ../../networking/remote_access_vpn.rst:651
+#: ../../networking/virtual_private_cloud_config.rst:321
+#: ../../networking/virtual_private_cloud_config.rst:352
+#: ../../networking/virtual_private_cloud_config.rst:519
+#: ../../networking/virtual_private_cloud_config.rst:754
+#: ../../networking/virtual_private_cloud_config.rst:812
+#: ../../networking/virtual_private_cloud_config.rst:873
+#: ../../networking/virtual_private_cloud_config.rst:1039
+#: ../../networking/virtual_private_cloud_config.rst:1307
+# 2982ca1c12bf49f2866744193ff6f578
+# f16720ba82ad472da40e8ad034254fe4
+# 24dfa509e12d4af98062dd3ae0b48f52
+# 8e4bbd56239d4c71954370d8ef6e8cbe
+# 1f15602058a04c8ebef82e324bb336e6
+# 9ba99b464c2a41bdbe57d55fafae2ccb
+# ebb32770ece6425e9748b0b6a9e2f681
+# ddc08af8ce4f4978a487c0467816270a
+# 642e10bd685b467ead08d1a5a1df5a5f
+# 4060fb167ecd47c882155784f918a887
+# 4c47fa58c98943ec8448eb44ecf621c2
+# 2bf6e84c5f66458f9ed8b4566d751075
+# 606de62e4a0643e89e7cc0809decf0d1
+msgid "CIDR"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# d4529e4573f1422e89f8705d72b14fa6
+msgid "Network CIDR"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# 8717091b7d574910ae7f7db398dec4df
+msgid "Reserved IP Range for Non-CloudStack VMs"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# f596416e0a6849629c21a6b74715913c
+msgid "Description"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+#: ../../networking/virtual_private_cloud_config.rst:323
+# 3982ebcb186c4a28bf3ffa4552438c72
+# 15b7293e51984eb1be8bb66b8d99d6e1
+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
+# f627b7351048414296987b276f691d64
+# 696d3ab791fa4146be4d6793d9894204
+# df688c92b303499f87d27d2a6fda5fc3
+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
+# a5a742b38ae847cb99bd9339c2d47e94
+# 332c38a7b5df4f1ca82b88c659c623bd
+# 8adf0d6c1d72460eb7310b93522b0346
+# d4268a954eb94931af19f1c48598c309
+msgid "None"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+# f2eddeac640e48e5b16991ce8b7bfa93
+msgid "No IP Reservation."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+#: ../../networking/virtual_private_cloud_config.rst:324
+# 5bb07f152b264e86ae6eda03cc31e1c1
+# f5f2048cf9714b9ea68d2049570c4f6c
+msgid "2"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+# 01110998a1c74b3c80ef1a4dc83268a1
+msgid "10.1.1.0/26"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+# e5cce0b4eb08472589cd816030a3de7d
+msgid "10.1.1.64 to 10.1.1.254"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+# 9e5926a76629431e9e75a9c27ec25211
+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
+# a1279f60da4448408c8b4ef94ae25031
+msgid "3"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+# 24e829a2afac40eaa86a07045b551c40
+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
+#: ../../networking/security_groups.rst:91
+#: ../../networking/palo_alto_config.rst:467
+# d2dda38687714f138add9a3210ce94ec
+# 46aafdafc5b941cc973bf413019aea2d
+# 72b66fa9b2694682919a62c46d2a7506
+msgid "Limitations"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:85
+# 6c3ae7eb716447539cf6ce3a087485f8
+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
+# 2b40b03295c04e3384d785ee53b756e2
+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
+# 583ca0216ee74e1581158dc7533c07d0
+msgid "Best Practices"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:97
+# 388bdfcc95f147538a75b7767724cbda
+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
+# a3c4555e018a445ca599010a280d64a5
+msgid "Reserving an IP Range"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:112
+# 6242f71ba63246c7a5080997cf22f7c6
+msgid "In the Details tab, click Edit. |ip-edit-icon.png|"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:114
+# df98c1294588410ca38bdcafe1f1a634
+msgid "The CIDR field changes to editable one."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:116
+# e18e130a65f64f129965e464668821cc
+msgid "In CIDR, specify the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:118
+# e1926c61c2e24ac9bb3568b5425e6640
+msgid "Click Apply."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:120
+# 8e47676d285f403ab1c11aacbe5ad256
+msgid "Wait for the update to complete. The Network CIDR and the Reserved IP Range are displayed on the Details page."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:18
+# b15f7528cec041d084db2225a51abbd1
+msgid "Reserving Public IP Addresses and VLANs for Accounts"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:20
+# 1237af30bb46480aa12ce39cfe5e593c
+msgid "CloudStack provides you the ability to reserve a set of public IP addresses and VLANs exclusively for an account. During zone creation, you can continue defining a set of VLANs and multiple public IP ranges. This feature extends the functionality to enable you to dedicate a fixed set of VLANs and guest IP addresses for a tenant."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:26
+# 17369f839a29414b986f6bea29ed68ba
+msgid "Note that if an account has consumed all the VLANs and IPs dedicated to it, the account can acquire two more resources from the system. CloudStack provides the root admin with two configuration parameter to modify this default behavior: use.system.public.ips and use.system.guest.vlans. These global parameters enable the root admin to disallow an account from acquiring public IPs and guest VLANs from the system, if the account has dedicated resources and these dedicated resources have all been consumed. Both these configurations are configurable at the account level."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:36
+# eb7adb4a348943f4a8a202f85e7fb8d5
+msgid "This feature provides you the following capabilities:"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:38
+# 358e7d880b0749daa4dc8a226925c073
+msgid "Reserve a VLAN range and public IP address range from an Advanced zone and assign it to an account"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:41
+# 6e0eb4612e474dc984111d18bb95fc83
+msgid "Disassociate a VLAN and public IP address range from an account"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:43
+# bab06e5f1a2f454aa3b08743ba57c793
+msgid "View the number of public IP addresses allocated to an account"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:45
+# a6866fc5db5347209e221b84742c3365
+msgid "Check whether the required range is available and is conforms to account limits."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:48
+# 1620986a4ae94f2485a54cd91ccaac56
+msgid "The maximum IPs per account limit cannot be superseded."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:52
+# 22120243221443aebd306ac3563d496f
+msgid "Dedicating IP Address Ranges to an Account"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:56
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:126
+#: ../../networking/global_server_load_balancing.rst:317
+# 41eada43c00c47d3af3049e17e3a5ed4
+# 3a4fc14485e04b878d42c2f16d2c1874
+# 3b0a5efffc524d5a89c218f531388b51
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:58
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:128
+# afa72273b7894980af0176c1cbb8d600
+# 1b7787454ba64ef5bde4f8dc55076690
+msgid "In Zones, click View All."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:60
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:130
+#: ../../networking/global_server_load_balancing.rst:321
+# 3538cd7eca744d5dbedb17d4d1df1490
+# 737bb1531046470f96395e869b9b3d0d
+# 1c6a07051f2f4a1eb71d9cb9a6cbb984
+msgid "Choose the zone you want to work with."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:64
+# 2afee3aa9d964227ad8abeec4cff164d
+msgid "In the Public node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:66
+# 31af885ac08540b1a345a76ed1c81e3a
+msgid "Click the IP Ranges tab."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:68
+# d99c704f2b3e4e829337b91b0e1af56a
+msgid "You can either assign an existing IP range to an account, or create a new IP range and assign to an account."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:71
+# 781bb561940748e88798ab180120b3e8
+msgid "To assign an existing IP range to an account, perform the following:"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:73
+# 64caee3705894ae5b7eb188e82c8d260
+msgid "Locate the IP range you want to work with."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:75
+# 9e0730ca65ac4442a517f39c9056cee8
+msgid "Click Add Account |addAccount-icon.png| button."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:77
+# 6c4ee6b7080e4fd7a90d8edddfda5845
+msgid "The Add Account dialog is displayed."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:81
+# 2c50704135d54e319c54ab3e0aade306
+msgid "**Account**: The account to which you want to assign the IP address range."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:84
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:112
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:150
+# ee19ac37f89e4403997fdca99142dad5
+# 2ba3bff62178453c93570a1e85aa2879
+# 265ed744d98042a9bbcb2c139f70e7fb
+msgid "**Domain**: The domain associated with the account."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:86
+# 8fbac9b35cdb43ea90d07e27edb5a231
+msgid "To create a new IP range and assign an account, perform the following:"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:91
+# 16602be853314d1ca41010b8d9c70203
+msgid "**Gateway**"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:93
+# 2b07551df7d347b2877a717602b072a0
+msgid "**Netmask**"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:95
+# 8302fe6345ff497088145a583593bea1
+msgid "**VLAN**"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:97
+# 34b38799ec734aa89366e4c3f651a3e4
+msgid "**Start IP**"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:99
+# 70bab7c8bc9a44b8b72a460686975a2a
+msgid "**End IP**"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:101
+# 02aaa72ff90843289ad5aeb650f65a9d
+msgid "**Account**: Perform the following:"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:103
+# 9a58082c89c9466fba38134f240e1b52
+msgid "Click Account."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:105
+# dcb5729930024223b016b7cbdb424ba1
+msgid "The Add Account page is displayed."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:109
+# 5c2df9219e7346a6bfc5ecb3bf074542
+msgid "**Account**: The account to which you want to assign an IP address range."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:117
+#: ../../networking/security_groups.rst:210
+#: ../../networking/ip_forwarding_and_firewalling.rst:88
+#: ../../networking/ip_forwarding_and_firewalling.rst:163
+#: ../../networking/ip_forwarding_and_firewalling.rst:276
+#: ../../networking/remote_access_vpn.rst:153
+#: ../../networking/virtual_private_cloud_config.rst:642
+# f149473b61b340ca9e017c5f4aad3762
+# 2ddbd5f2481d4b119ddad24b954900cc
+# b48da4e586f54f578325e5a80b7d9f43
+# 5b0f318024d544438e606644459f750b
+# 065cefba75724c0a8d56d7931eea5c3d
+# 589f4a9092e34b8f8382b017ebf0259f
+# b103ac8cfde9495fb1cd24a491540360
+msgid "Click Add."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:121
+# 6f051411c8144bdc9db1c5f418ca9e6b
+msgid "Dedicating VLAN Ranges to an Account"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:123
+# 0624b2939c5d4e5f9f0769c68abba80a
+msgid "After the CloudStack Management Server is installed, log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:134
+#: ../../networking/multiple_subnets_in_shared_network.rst:61
+# 40248bd661704cdb80e80629fe09d500
+# f99a23ecda8047cfa0314a138db2515e
+msgid "In the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:136
+# 092aa112394946a6a4808b597cc9d85d
+msgid "Select the Dedicated VLAN Ranges tab."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:138
+# 1fdecb917bc84f50afd745175be5d7e7
+msgid "Click Dedicate VLAN Range."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:140
+# b67fd2523d364441a6c82f24bc357ab5
+msgid "The Dedicate VLAN Range dialog is displayed."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:144
+# 542f999a29c64479b5f5d452895813bd
+msgid "**VLAN Range**: The VLAN range that you want to assign to an account."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:147
+# 55217660cfb0479ebc430fe86772c808
+msgid "**Account**: The account to which you want to assign the selected VLAN range."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:18
+# 4b6378bc482446339fca13029388310a
+msgid "Configuring Multiple IP Addresses on a Single NIC"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:20
+# 3cb13c102ebb495b944a5ea2571c0ea6
+msgid "CloudStack provides you the ability to associate multiple private IP addresses per guest VM NIC. In addition to the primary IP, you can assign additional IPs to the guest VM NIC. This feature is supported on all the network configurations: Basic, Advanced, and VPC. Security Groups, Static NAT and Port forwarding services are supported on these additional IPs."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:27
+# cda7fad448d845659243893d3485d00f
+msgid "As always, you can specify an IP from the guest subnet; if not specified, an IP is automatically picked up from the guest VM subnet. You can view the IPs associated with for each guest VM NICs on the UI. You can apply NAT on these additional guest IPs by using network configuration option in the CloudStack UI. You must specify the NIC to which the IP should be associated."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:34
+# de43d093c3fa4819badd7e95a605662c
+msgid "This feature is supported on XenServer, KVM, and VMware hypervisors. Note that Basic zone security groups are not supported on VMware."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:39
+# b0dc091ada714fc080fbb52f2ea8f427
+msgid "Use Cases"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:41
+# f716fd8c0f43409d9b85a31bfd022770
+msgid "Some of the use cases are described below:"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:43
+# 39e24f20af4e4a389da098c9fb80f1f5
+msgid "Network devices, such as firewalls and load balancers, generally work best when they have access to multiple IP addresses on the network interface."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:47
+# 75801965b1464997a865772f1ea040ef
+msgid "Moving private IP addresses between interfaces or instances. Applications that are bound to specific IP addresses can be moved between instances."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:51
+# 1f4805e6057f4a5f97735f57cc71033c
+msgid "Hosting multiple SSL Websites on a single instance. You can install multiple SSL certificates on a single instance, each associated with a distinct IP address."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:57
+#: ../../networking/portable_ips.rst:48
+#: ../../networking/virtual_private_cloud_config.rst:1125
+# c0033b8d9992490791fbd0dc7f89fa6f
+# 4c7d965ae98540498820d6359998db6c
+# 924fe16b17a346a1b175d02a5701f4db
+msgid "Guidelines"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:59
+# ab36c55d792048e78529f118b75f7169
+msgid "To prevent IP conflict, configure different subnets when multiple networks are connected to the same VM."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:64
+# a16d7477fb8d418abbe4a25970ed93ac
+msgid "Assigning Additional IPs to a VM"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:66
+# 8913586016c847b1b942015f371fff55
+msgid "Log in to the CloudStack UI."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:68
+# 93115e86c11446058862e5525c9fcc6d
+msgid "In the left navigation bar, click Instances."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:70
+# 197ab17d29454cdc8de866d1f2c0be83
+msgid "Click the name of the instance you want to work with."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:72
+# c7863b679faf4fb6ac1f9e48e70ba5d4
+msgid "In the Details tab, click NICs."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:74
+# 9dfa60a220ed42018f74c7bd78e6d7cd
+msgid "Click View Secondary IPs."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:76
+# e783f44753f8491689c78956994376bd
+msgid "Click Acquire New Secondary IP, and click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:79
+# ae7779933a044ea395e2bfa5e67ca484
+msgid "You need to configure the IP on the guest VM NIC manually. CloudStack will not automatically configure the acquired IP address on the VM. Ensure that the IP address configuration persist on VM reboot."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:83
+# e08145cc27e24301982a9f2f45bd93d8
+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 StaticNAT rules."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:89
+# 1aa79a21e0f24d109fbf1a380be58b37
+msgid "Port Forwarding and StaticNAT Services Changes"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:91
+# ffac07bcb64d47f7bcb39e02c46e43b5
+msgid "Because multiple IPs can be associated per NIC, you are allowed to select a desired IP for the Port Forwarding and StaticNAT services. The default is the primary IP. To enable this functionality, an extra optional parameter 'vmguestip' is added to the Port forwarding and StaticNAT APIs (enableStaticNat, createIpForwardingRule) to indicate on what IP address NAT need to be configured. If vmguestip is passed, NAT is configured on the specified private IP of the VM. if not passed, NAT is configured on the primary IP of the VM."
+msgstr ""
+
+#: ../../networking/multiple_ip_ranges.rst:18
+# 0e8ade71092049f9bae900723c45e41a
+msgid "About Multiple IP Ranges"
+msgstr ""
+
+#: ../../networking/multiple_ip_ranges.rst:20
+# e46b13dd887941a78dd4dde1a9c91f7b
+msgid "The feature can only be implemented on IPv4 addresses."
+msgstr ""
+
+#: ../../networking/multiple_ip_ranges.rst:22
+# 6bd2d25649fc4326b60a07cefee0f204
+msgid "CloudStack provides you with the flexibility to add guest IP ranges from different subnets in Basic zones and security groups-enabled Advanced zones. For security groups-enabled Advanced zones, it implies multiple subnets can be added to the same VLAN. With the addition of this feature, you will be able to add IP address ranges from the same subnet or from a different one when IP address are exhausted. This would in turn allows you to employ higher number of subnets and thus reduce the address management overhead. To support this feature, the capability of ``createVlanIpRange`` API is extended to add IP ranges also from a different subnet."
+msgstr ""
+
+#: ../../networking/multiple_ip_ranges.rst:33
+# 3ba0c789bb3449fe86585f4c8c841997
+msgid "Ensure that you manually configure the gateway of the new subnet before adding the IP range. Note that CloudStack supports only one gateway for a subnet; overlapping subnets are not currently supported."
+msgstr ""
+
+#: ../../networking/multiple_ip_ranges.rst:37
+# e5e487ee073f4d56be1f4666a45f4dfe
+msgid "Use the ``deleteVlanRange`` API to delete IP ranges. This operation fails if an IP from the remove range is in use. If the remove range contains the IP address on which the DHCP server is running, CloudStack acquires a new IP from the same subnet. If no IP is available in the subnet, the remove operation fails."
+msgstr ""
+
+#: ../../networking/multiple_ip_ranges.rst:43
+# bc188db60e2742989c16aedac841809e
+msgid "This feature is supported on KVM, xenServer, and VMware hypervisors."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:18
+# 866f7bd8690f4e378e4a55a7c80d196c
+msgid "About Elastic IPs"
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:20
+# 53c01f3c606045ad9beed865c2233d50
+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 is down, the IP address can be reassigned to a new VM in your account."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:29
+# eeb2c5db0229477692e9e379117ad90e
+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
+# c188c126629840a7a54f6b8956cb2c76
+msgid "|eip-ns-basiczone.png|"
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:39
+# 51020097041145ddb6805633c7eb819c
+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 data center goes through the firewall."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:48
+# 3f2630ad1d0343c68eb8a2303ccb4c9c
+msgid "The EIP work flow is as follows:"
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:50
+# d20e19311068491ba44b06500472b710
+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
+# d15702d110a942848fa6cef69cece507
+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
+# ff6cb27225094523ba3a17d305016521
+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
+# e9dde6b9e99a42a4b1141fa7cde9549e
+msgid "This default public IP will be released in two cases:"
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:69
+# bb3ef5bc34c24d44980be5d6f69e0c5c
+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
+# 571a9e4939ea4287a8aa0ddf426417b4
+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
+# aaf805319e4341d8a268392acb2bda8e
+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 and enable static NAT."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:90
+# 31babd6d6dfd4d079192f8d6984817ee
+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
+# dbb9cddd535f4a438059357783272fe3
+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
+# d898deec360a48b1851e6a597385713b
+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 ""
+
+#: ../../networking/portable_ips.rst:18
+# 0f08f4f232ba497eb9cd9c3e04f96afc
+msgid "Portable IPs"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:21
+# 7ac92bb50f6449d988fcc630639a18fc
+msgid "About Portable IP"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:23
+# 6ae5874856114307829101c5c704d620
+msgid "Portable IPs in CloudStack are region-level pool of IPs, which are elastic in nature, that can be transferred across geographically separated zones. As an administrator, you can provision a pool of portable public IPs at region level and are available for user consumption. The users can acquire portable IPs if admin has provisioned portable IPs at the region level they are part of. These IPs can be use for any service within an advanced zone. You can also use portable IPs for EIP services in basic zones."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:32
+# 742f98931c1a44baa38129e2d9707866
+msgid "The salient features of Portable IP are as follows:"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:34
+# a4472d2004c943f1ad88325b36b6a440
+msgid "IP is statically allocated"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:36
+# fcd6dca4d30d4a1f92bb64c7635abeb1
+msgid "IP need not be associated with a network"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:38
+# 7409719b9ce74f6c8d91b07f9079a6ef
+msgid "IP association is transferable across networks"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:40
+# 5aeff85fa3704f3ab93dbbba900c80f2
+msgid "IP is transferable across both Basic and Advanced zones"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:42
+# 96ffa5d02ec9464e8866c8d272aad9c1
+msgid "IP is transferable across VPC, non-VPC isolated and shared networks"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:44
+# 6207a2e79e024acc8ef256c36daec0ff
+msgid "Portable IP transfer is available only for static NAT."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:50
+# c3d0138ce57f44a9becb32df52ca0fb9
+msgid "Before transferring to another network, ensure that no network rules (Firewall, Static NAT, Port Forwarding, and so on) exist on that portable IP."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:56
+# 18cc0645453a43eebf52beaa73a9a6a6
+msgid "Configuring Portable IPs"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:60
+# 740ad8e23fac49f8950f5161989c18e9
+msgid "In the left navigation, click Regions."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:62
+# 40704d729f114cbcb667118f671238ef
+msgid "Choose the Regions that you want to work with."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:64
+# 03bf5d8664204ec084df0a9d5940644a
+msgid "Click View Portable IP."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:66
+# ddc000619eb94419951b60265902d979
+msgid "Click Portable IP Range."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:68
+# c8a67f00327e4e37bfae6b2882e40fa0
+msgid "The Add Portable IP Range window is displayed."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:72
+# 873cae2265344ab384d2b0f8956b8cbe
+msgid "**Start IP/ End IP**: A range of IP addresses that are accessible from the Internet and will be allocated to guest VMs. Enter the first and last IP addresses that define a range that CloudStack can assign to guest VMs."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:77
+# 47a17aedcd9a46d4aa9426bc133f7593
+msgid "**Gateway**: The gateway in use for the Portable IP addresses you are configuring."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:80
+# 7979e6a1cf8a4b2d8e8673ed132db41e
+msgid "**Netmask**: The netmask associated with the Portable IP range."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:82
+# 63cb5224252e403480ba1ddc53337de8
+msgid "**VLAN**: The VLAN that will be used for public traffic."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:88
+# 124023448c074dcea01be7eddc177170
+msgid "Acquiring a Portable IP"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:94
+#: ../../networking/acquiring_an_ip_address.rst:24
+#: ../../networking/releasing_an_ip_address.rst:28
+#: ../../networking/static_nat.rst:40
+#: ../../networking/ip_forwarding_and_firewalling.rst:63
+# ac222ffaf3d1404a885f643c228d2c83
+# baf678baec6247bb94c9eab6b3b1e84e
+# ffdddf1fe28240469a8090a522b32151
+# 663ad172db854afdadd95fc1d3db1f64
+# 2bf3f81e7dbb4b2cb34d627506ee9889
+msgid "Click the name of the network where you want to work with."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:96
+#: ../../networking/external_firewalls_and_load_balancers.rst:262
+#: ../../networking/acquiring_an_ip_address.rst:26
+#: ../../networking/releasing_an_ip_address.rst:30
+#: ../../networking/static_nat.rst:42
+#: ../../networking/ip_forwarding_and_firewalling.rst:65
+#: ../../networking/remote_access_vpn.rst:82
+# 442ce3999e8d427da57daa610533fb7c
+# 9cc585cd1a5740acba75c898195b0eab
+# 4c9d3404671a4e4d99d3323175204d8e
+# e8c449dffe3c49e8938437a96cef0ca6
+# d605e8bf3fb74b278bf0d265f1db6084
+# 5f4eacd3a2ba48349a41f04f8756ee37
+# ba3dfb6ca3af4d51a17fa31861d95379
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:98
+#: ../../networking/acquiring_an_ip_address.rst:28
+# fbc9c26eb4f041618e668c4addb7f051
+# eab860b6d87641698d96cf5e11803339
+msgid "Click Acquire New IP."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:100
+#: ../../networking/acquiring_an_ip_address.rst:30
+# 294bab6d3d9f43aa8d85acabb8fdbdf5
+# 5ebf3c5ce9154b57bf3cf2ef8e449b4b
+msgid "The Acquire New IP window is displayed."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:102
+#: ../../networking/acquiring_an_ip_address.rst:32
+# 54c07b2049174cceae5d75abcd11939f
+# d82eff4f2d2d4e8cb8c9fe694607832a
+msgid "Specify whether you want cross-zone IP or not."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:104
+# 3c0460b1928b474e8347baf870d93061
+msgid "Click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:106
+#: ../../networking/acquiring_an_ip_address.rst:40
+# c6d079ae16bb440d9430701ba56f68a1
+# 5c09ad0de69f460bbc10914cf114f514
+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 ""
+
+#: ../../networking/portable_ips.rst:112
+# 8f37986b8a4e47ba93264a3bb9af1a18
+msgid "Transferring Portable IP"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:114
+# 8a4e3d4a96ea471794ae2d68687fa797
+msgid "An IP can be transferred from one network to another only if Static NAT is enabled. However, when a portable IP is associated with a network, you can use it for any service in the network."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:118
+# 680b04281ce240339902b0a08da4ecd8
+msgid "To transfer a portable IP across the networks, execute the following API:"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:125
+# 8a701f169d1449e7b4cc16e3e4ae8b8f
+msgid "Replace the UUID with appropriate UUID. For example, if you want to transfer a portable IP to network X and VM Y in a network, execute the following:"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:18
+# 7089d5ba1bd84cd788dd5c22ca2b1bd2
+msgid "Multiple Subnets in Shared Network"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:20
+# 0477f56fce2e483d8971ed6598538bac
+msgid "CloudStack provides you with the flexibility to add guest IP ranges from different subnets in Basic zones and security groups-enabled Advanced zones. For security groups-enabled Advanced zones, it implies multiple subnets can be added to the same VLAN. With the addition of this feature, you will be able to add IP address ranges from the same subnet or from a different one when IP address are exhausted. This would in turn allows you to employ higher number of subnets and thus reduce the address management overhead. You can delete the IP ranges you have added."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:32
+#: ../../networking/global_server_load_balancing.rst:255
+#: ../../networking/ip_forwarding_and_firewalling.rst:107
+# 2ad5b5d4ac7c4c81bb8f93f0bc9ec255
+# 788fe7caacfd434d9974e747cc5b6975
+# 6a8d2ba526f244f0867dd3ba399837cc
+msgid "Prerequisites and Guidelines"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:34
+# 6ba395678a3b488d83285fef91d03eb8
+msgid "This feature can only be implemented:"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:36
+# d0797766d8c8418a944d9351c7a7d5f2
+msgid "on IPv4 addresses"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:38
+# dfbc41f238524d26b2412643554b3dda
+msgid "if virtual router is the DHCP provider"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:40
+# b16927d0778c489d8684d17d6d5080a5
+msgid "on KVM, xenServer, and VMware hypervisors"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:42
+# da5c39ee692344d9ad7e4baa53792f99
+msgid "Manually configure the gateway of the new subnet before adding the IP range."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:45
+# 12c49c34743945559bdac3337e94b72b
+msgid "CloudStack supports only one gateway for a subnet; overlapping subnets are not currently supported"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:50
+# 5e0122bb568b4cb89567b4d417ff860d
+msgid "Adding Multiple Subnets to a Shared Network"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:56
+# 5dead61f678f4f708dc471eb41eb51d7
+msgid "On Zones, click View More, then click the zone to which you want to work with.."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:59
+# 113bdf0910ef4fa181ae7e1dd6b4965a
+msgid "Click Physical Network."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:63
+# 93cb70825bb2406bb280993bb96c1423
+msgid "Click Networks."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:65
+# a8776092b5274a8f85bb80eea30fc74e
+msgid "Select the networks you want to work with."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:67
+# 1bee5ce455ca48a99e79744a7d62e425
+msgid "Click View IP Ranges."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:69
+# bda3572323594aa4b29c6a6b5757d2b3
+msgid "Click Add IP Range."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:71
+# 9f735ab5dccd454ba2337ef570347dd5
+msgid "The Add IP Range dialog is displayed, as follows:"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:73
+# 83f6544a7bc44bc09cf19bfaf591db11
+msgid "|add-ip-range.png|"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:77
+#: ../../networking/virtual_private_cloud_config.rst:250
+# d555abc08eb3476c9e5aa15b14cb5ecb
+# fbc89fdbac934907bce2121e6b919e02
+msgid "All the fields are mandatory."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:79
+#: ../../networking/virtual_private_cloud_config.rst:262
+# a0f1b8e275a849a79eefa4a842795497
+# da34b3884ae5434b9e9aa6bcf68fd955
+msgid "**Gateway**: The gateway for the tier you create. Ensure that the gateway is within the Super CIDR range that you specified while creating the VPC, and is not overlapped with the CIDR of any existing tier within the VPC."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:84
+#: ../../networking/virtual_private_cloud_config.rst:275
+# 9a478560b45f4c7fa3a7749ae1781e2f
+# 625aa7b3683d4ab686623285a759d03e
+msgid "**Netmask**: The netmask for the tier you create."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:86
+#: ../../networking/virtual_private_cloud_config.rst:277
+# bc0ecfa80a4b43e4881c58b85f681266
+# c8ffd6a926fe4eefbdc0e84ebc7dd348
+msgid "For example, if the VPC CIDR is 10.0.0.0/16 and the network tier CIDR is 10.0.1.0/24, the gateway of the tier is 10.0.1.1, and the netmask of the tier is 255.255.255.0."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:90
+# b48ff10b434e49e5abe6714cfb3452d9
+msgid "**Start IP/ End IP**: A range of IP addresses that are accessible from the Internet and will be allocated to guest VMs. Enter the first and last IP addresses that define a range that CloudStack can assign to guest VMs ."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:18
+# cc7a99018f204eb3b14ae4407e439d52
+msgid "Isolation in Advanced Zone Using Private VLAN"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:20
+# d4c63a56d1c541179877426fec001db5
+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 users' VMs."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:29
+# 662c4fdd4bd34b7b9c55b5525c739c11
+msgid "Isolate VMs in a shared networks by using Private VLANs."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:31
+# 1a255e04a5154ff0be5f76264b93453e
+msgid "Supported on KVM, XenServer, and VMware hypervisors"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:33
+# 8f8a37c238cc4670b3152c2a622787c7
+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
+# 8be0c81861ea4d4f9f8a9e2403e11250
+msgid "About Private VLAN"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:40
+# 19221ad3a5f64011b70c802da07bee31
+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 VLAN that is being divided into smaller groups is called Primary, which implies that all VLAN pairs in a private VLAN share the same Primary VLAN. All the secondary VLANs exist only inside the Primary. Each Secondary VLAN has a specific VLAN ID associated to it, which differentiates one sub-domain from another."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:53
+# c46e1be64b4e467aaa0a2109cb87bc24
+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
+# 8773791ad68744dbbef479a5a63348f1
+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
+# 91c780247f2c4db2a19e098d51fb2a1f
+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
+# 4e94602bf9fa44c6b94244cf55cb1aeb
+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 communicate among themselves, deploy them in community ports."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:84
+# 362d4b4e5dd242628fe508d3abbe3361
+msgid "For further reading:"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:86
+# 9dc2e8a81d2e4418ae9f6222887a9bd3
+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
+# 7e9fd9cf1c9b469ebd5bd961175982df
+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
+# 7cd6254dad1c4523b2c2be1867cca7cb
+msgid "`Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview (1010691) <http://kb.vmware.com>`_"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:99
+# e7159581e2aa4e7f82fcc3e3e5b8e9b2
+msgid "Use a PVLAN supported switch."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:101
+# 558f121cf82b419cbacce6914151513e
+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
+# bc44ba94ec284076984bcf8bd7345e42
+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
+# 71abf1e9b2ae4a149e565ca17b45f51c
+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
+# 6b7feb8b8f8646848e0fc9321c60bb0f
+msgid "Configure private VLAN on your physical switches out-of-band."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:120
+# 06b27f4c4355406886e4aa1e037d9467
+msgid "Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS)."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:123
+# d9b9a5e0ce044d7b94cc7f36f40dac75
+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
+# 579764808b8b4cee81634b52e650e7f4
+msgid "Creating a PVLAN-Enabled Guest Network"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:161
+# 5fd76d10b7a245ca92d599f5d84b04aa
+msgid "**Secondary Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:164
+# ba80bf59655f4806845c6b592500c85a
+msgid "For the description on Secondary Isolated VLAN, see `About Private VLAN\" <#about-private-vlan>`_."
+msgstr ""
+
+#: ../../networking/security_groups.rst:18
+# cb6cc7de1ccf43ceb4fee732f2374d3a
+msgid "Security Groups"
+msgstr ""
+
+#: ../../networking/security_groups.rst:21
+# d27a88932a2a40c580ff31cd04f7c5b1
+msgid "About Security Groups"
+msgstr ""
+
+#: ../../networking/security_groups.rst:23
+# f5ba715a47234ff3a2bb8f9c56d490ab
+msgid "Security groups provide a way to isolate traffic to VMs. 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. Security groups are particularly useful in zones that use basic networking, because there is a single guest network for all guest VMs. In advanced zones, security groups are supported only on the KVM hypervisor."
+msgstr ""
+
+#: ../../networking/security_groups.rst:33
+# 29c17e93f2554fe99e042dbc72b337d9
+msgid "In a zone that uses advanced networking, you can instead define multiple guest networks to isolate traffic to VMs."
+msgstr ""
+
+#: ../../networking/security_groups.rst:36
+# b0e658a849c44ade96fd212d6c6b2589
+msgid "Each CloudStack account comes with a default security group that denies all inbound traffic and allows all outbound traffic. The default security group can be modified so that all new VMs inherit some other desired set of rules."
+msgstr ""
+
+#: ../../networking/security_groups.rst:41
+# 03c3350e08fe420da4f2f221c5773dba
+msgid "Any CloudStack user can set up any number of additional security groups. When a new VM is launched, it is assigned to the default security group unless another user-defined security group is specified. A VM can be a member of any number of security groups. Once a VM is assigned to a security group, it remains in that group for its entire lifetime; you can not move a running VM from one security group to another."
+msgstr ""
+
+#: ../../networking/security_groups.rst:48
+# 4b6f67cf254b46589e9ddd94ff94b1bc
+msgid "You can modify a security group by deleting or adding any number of ingress and egress rules. When you do, the new rules apply to all VMs in the group, whether running or stopped."
+msgstr ""
+
+#: ../../networking/security_groups.rst:52
+# d23292c15bd3444c9ce839ff69392d35
+msgid "If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule."
+msgstr ""
+
+#: ../../networking/security_groups.rst:58
+# c22e98199bb447fd9a71ddcec88a9deb
+msgid "Adding a Security Group"
+msgstr ""
+
+#: ../../networking/security_groups.rst:60
+# 8a6a28fa1d434e4fbe428253b48eb3b8
+msgid "A user or administrator can define a new security group."
+msgstr ""
+
+#: ../../networking/security_groups.rst:66
+# 1ed905affb2a472aa04efaf4868c54d6
+msgid "In Select view, choose Security Groups."
+msgstr ""
+
+#: ../../networking/security_groups.rst:68
+# b052c553469c485a8ff0422d5b0abf73
+msgid "Click Add Security Group."
+msgstr ""
+
+#: ../../networking/security_groups.rst:70
+# 3db27ac74dd94357a381d19d64f5759e
+msgid "Provide a name and description."
+msgstr ""
+
+#: ../../networking/security_groups.rst:74
+# 5715f7737e534f99853d1f7ef2ff13f0
+msgid "The new security group appears in the Security Groups Details tab."
+msgstr ""
+
+#: ../../networking/security_groups.rst:76
+# 581f75deea1c4ce98b419a71f864130e
+msgid "To make the security group useful, continue to Adding Ingress and Egress Rules to a Security Group."
+msgstr ""
+
+#: ../../networking/security_groups.rst:81
+# f35cc6563a5e4857b8feee6cf88f29a3
+msgid "Security Groups in Advanced Zones (KVM Only)"
+msgstr ""
+
+#: ../../networking/security_groups.rst:83
+# fe26402e50fd46458f4ad511d322ba21
+msgid "CloudStack provides the ability to use security groups to provide isolation between guests on a single shared, zone-wide network in an advanced zone where KVM is the hypervisor. Using security groups in advanced zones rather than multiple VLANs allows a greater range of options for setting up guest isolation in a cloud."
+msgstr ""
+
+#: ../../networking/security_groups.rst:93
+# 6199b2fe0a1346459e8db63371e35db5
+msgid "The following are not supported for this feature:"
+msgstr ""
+
+#: ../../networking/security_groups.rst:95
+# 68ca4f1c51804347a9af6d0fd227f701
+msgid "Two IP ranges with the same VLAN and different gateway or netmask in security group-enabled shared network."
+msgstr ""
+
+#: ../../networking/security_groups.rst:98
+# 6d6ded6fa4fe4853b91bbaea875c3db7
+msgid "Two IP ranges with the same VLAN and different gateway or netmask in account-specific shared networks."
+msgstr ""
+
+#: ../../networking/security_groups.rst:101
+# fb280b17f22e4093b26c6e9d1891f60c
+msgid "Multiple VLAN ranges in security group-enabled shared network."
+msgstr ""
+
+#: ../../networking/security_groups.rst:103
+# 465a90dfe47647f28f1d23f859ff2f8a
+msgid "Multiple VLAN ranges in account-specific shared networks."
+msgstr ""
+
+#: ../../networking/security_groups.rst:105
+# d5d9f22d58634efcbbd25a21f05d9ddf
+msgid "Security groups must be enabled in the zone in order for this feature to be used."
+msgstr ""
+
+#: ../../networking/security_groups.rst:110
+# 4f0382c2c0e349d0b3df1e3c6f9ae199
+msgid "Enabling Security Groups"
+msgstr ""
+
+#: ../../networking/security_groups.rst:112
+# 5b48cea9b0254d6b92404b64173b5f9f
+msgid "In order for security groups to function in a zone, the security groups feature must first be enabled for the zone. The administrator can do this when creating a new zone, by selecting a network offering that includes security groups. The procedure is described in Basic Zone Configuration in the Advanced Installation Guide. The administrator can not enable security groups for an existing zone, only when creating a new zone."
+msgstr ""
+
+#: ../../networking/security_groups.rst:122
+# f31414cc005f439194236fdcf63adaba
+msgid "Adding Ingress and Egress Rules to a Security Group"
+msgstr ""
+
+#: ../../networking/security_groups.rst:126
+# 13f6fe7914834d94be54eccfd3a6571e
+msgid "In the left navigation, choose Network"
+msgstr ""
+
+#: ../../networking/security_groups.rst:128
+# 012c6f8bd96840d5b500950bbb99d37a
+msgid "In Select view, choose Security Groups, then click the security group you want."
+msgstr ""
+
+#: ../../networking/security_groups.rst:131
+# c5c93da9ab4542f288c0ea7dacc7015d
+msgid "To add an ingress rule, click the Ingress Rules tab and fill out the following fields to specify what network traffic is allowed into VM instances in this security group. If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule."
+msgstr ""
+
+#: ../../networking/security_groups.rst:137
+# a2545fd9c6a14c158863af3aca3b3a6d
+msgid "**Add by CIDR/Account**. Indicate whether the source of the traffic will be defined by IP address (CIDR) or an existing security group in a CloudStack account (Account). Choose Account if you want to allow incoming traffic from all VMs in another security group"
+msgstr ""
+
+#: ../../networking/security_groups.rst:143
+# b0594fd78a124efd8984037ef17e6b89
+msgid "**Protocol**. The networking protocol that sources will use to send traffic to the security group. TCP and UDP are typically used for data exchange and end-user communications. ICMP is typically used to send error messages or network monitoring data."
+msgstr ""
+
+#: ../../networking/security_groups.rst:148
+# 3af9a8d515614eccafed5e09672a8f15
+msgid "**Start Port, End Port**. (TCP, UDP only) A range of listening ports that are the destination for the incoming traffic. If you are opening a single port, use the same number in both fields."
+msgstr ""
+
+#: ../../networking/security_groups.rst:152
+# 27a7bc38a030400e9d8f1dedb608659e
+msgid "**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code that will be accepted."
+msgstr ""
+
+#: ../../networking/security_groups.rst:155
+# 0ce4ad2050184376bdd26ed654e59599
+msgid "**CIDR**. (Add by CIDR only) To accept only traffic from 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 incoming traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr ""
+
+#: ../../networking/security_groups.rst:161
+# 91ef8eb9529941acbded2108e7c153e0
+msgid "**Account, Security Group**. (Add by Account only) To accept only traffic from another security group, enter the CloudStack account and name of a security group that has already been defined in that account. To allow traffic between VMs within the security group you are editing now, enter the same name you used in step 7."
+msgstr ""
+
+#: ../../networking/security_groups.rst:167
+# 813409a701e84482ab284821eb359fe2
+msgid "The following example allows inbound HTTP access from anywhere:"
+msgstr ""
+
+#: ../../networking/security_groups.rst:169
+# 7ac1c499669b4a3cafd27ef10695d298
+msgid "|httpaccess.png|"
+msgstr ""
+
+#: ../../networking/security_groups.rst:171
+# e1083636f84c412fab7099c64bed463a
+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 security group. If no egress rules are specified, then all traffic will be allowed out. Once egress rules are specified, the following types of traffic are allowed out: traffic specified in egress rules; queries to DNS and DHCP servers; and responses to any traffic that has been allowed in through an ingress rule"
+msgstr ""
+
+#: ../../networking/security_groups.rst:180
+# 69e5e83165db4e4ea9fd33a5bd1b0fff
+msgid "**Add by CIDR/Account**. Indicate whether the destination of the traffic will be defined by IP address (CIDR) or an existing security group in a CloudStack account (Account). Choose Account if you want to allow outgoing traffic to all VMs in another security group."
+msgstr ""
+
+#: ../../networking/security_groups.rst:186
+# 63fc0c9e030d4dc193c101bcb0e4b3fb
+msgid "**Protocol**. The networking protocol that VMs will use to send outgoing traffic. TCP and UDP are typically used for data exchange and end-user communications. ICMP is typically used to send error messages or network monitoring data."
+msgstr ""
+
+#: ../../networking/security_groups.rst:191
+# 0aa4b36b063a4f05a08b6a2ebb65d1f7
+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/security_groups.rst:195
+# c2b03378b50f4e2b8ad15946702ddb5c
+msgid "**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code that will be sent"
+msgstr ""
+
+#: ../../networking/security_groups.rst:198
+# f8d9e0334b9a4b1faa27a9fa5f918dae
+msgid "**CIDR**. (Add by CIDR only) To send traffic only to 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/security_groups.rst:204
+# 748c734315774d6ea521e50471bbadab
+msgid "**Account, Security Group**. (Add by Account only) To allow traffic to be sent to another security group, enter the CloudStack account and name of a security group that has already been defined in that account. To allow traffic between VMs within the security group you are editing now, enter its name."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:18
+# 121a5a4d0fdf4adbadf0e9018abbb3f2
+msgid "External Firewalls and Load Balancers"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:20
+# da0033de7a88452b92b35dc42a5409ca
+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
+# 1758f3bbc4ec49b6a87df151d32c7822
+msgid "About Using a NetScaler Load Balancer"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:29
+# edf025a8432d4d2e916b9e1e4506292b
+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
+# e6c1fa94b4a44fe9af51313b701a4c0a
+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
+# 919e3b6335ec43cbb41cd06193a91872
+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 device providing EIP/ELB, layer 3 router must have a policy-based routing. A policy-based route must be set up so that all traffic originated from the guest VM's are directed to NetScaler device. This is required to ensure that the outbound traffic from the guest VM's is routed to a public IP by using NAT.For more information on Elastic IP, see `\"About Elastic IP\" <#about-elastic-ip>`_."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:52
+# e8f3e9f2b1bd412a99284612b6c7e030
+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
+# 523f98e01f234306b388d42100392a01
+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
+# 9526107823ab4b9bbdf3aeabea512cbd
+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
+# b606dd0a26944ae7abe244a91ae68dce
+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
+# 4d4acf453ee34b99bcd9422624a29d4f
+msgid "**MPX**"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:70
+# 31bf9c295f6f41ceba97d553ee88a09e
+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
+# 9393642591e14352a7b452e06213da83
+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
+# b9313747ed1d4f2bb9ceb37cc651ef0e
+msgid "**VPX**"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:79
+# 726835d9e8994018bac41442046eebab
+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
+# c85737d038fa4926a9e5e9ea965a24ce
+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
+# 6aa4be1b809449b48793dde65f3fee9c
+msgid "**SDX**"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:87
+# ffe20a22c29347ff81fd3ac28699bc4c
+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
+# 363ff0dd6af349ae9fb5dfe4b0264655
+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
+# 48be3cf5cf894ea3be2012a3fd52b693
+msgid "Configuring SNMP Community String on a RHEL Server"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:100
+# 124686b380a8434fbe22ff4861dcf466
+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
+# db1b06466d9042489699add305179ed0
+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
+# 86bf1082cfba4dd0ab1ae1cd1fc55280
+msgid "Ensure that you installed SNMP on RedHat. If not, run the following command:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:117
+# b57fd1f457bb47559202771c0c0e81b9
+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
+# 7cc4f86ef08341519c58b04122531955
+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
+# 96e1da8de4da414f8ba5659fc97790f5
+msgid "Use a strong password instead of public when you edit the following table."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:133
+# e0dfb13b632f40ee91f2522b6545638c
+msgid "Setting to 0.0.0.0 allows all IPs to poll the NetScaler server."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:135
+# 8bbf09e13cf4449eab6802c2e431d166
+msgid "Map the security names into group names:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:145
+# 28f26a19a75e4d38b8cbe455da453945
+msgid "Create a view to allow the groups to have the permission to:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:151
+# cbb139269f8f422ea3ced1eb9e1f20d4
+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
+# 4b8fa0c0c42b41e585535c6e0a66012c
+msgid "Unblock SNMP in iptables."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:166
+# 62e7b099d03c4a73bfcac8ea208630d3
+msgid "Start the SNMP service:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:172
+# 54522a637adb4007a9a82f11819c2c59
+msgid "Ensure that the SNMP service is started automatically during the system startup:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:181
+# 5949212234ed48b6adc372a7c7ce1637
+msgid "Initial Setup of External Firewalls and Load Balancers"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:183
+# 4cac2b9077964674844de4e3e3a93a0b
+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
+# 4bf4042c7f4f4def95f95bb7a9c4c3ec
+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
+# 0691cec2a7cf4c178b39117f7d1ae324
+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
+# 493986833b5c4b068a45f8c644330cc3
+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
+# d94c05bebe7142f69087aa01f32a8dd2
+msgid "The following objects are created on the load balancer:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:200
+# 3038b6bbaf9a40e4bf717fc65b7b5f7a
+msgid "A new VLAN that matches the account's provisioned Zone VLAN"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:202
+# 6babff57f8864990afeabf3aa8702676
+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
+# c78efbcb1b344675a63143a5fa305c80
+msgid "Ongoing Configuration of External Firewalls and Load Balancers"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:209
+# 778d4134b7bd4fec9bc3c731d1dd006f
+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 objects:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:218
+# 98d20f26e4be4a6693dbe1d69cbd1dc6
+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
+# 21bcfd0a7295477cb6daae191a4b5300
+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
+# d57954e8fd754ec291d98eda142d626c
+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
+# fe43a5a0e7e9497595d1e43626bc76de
+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
+# 6db8db0667bd4e58b757a87adabda6bc
+msgid "Load Balancer Rules"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:236
+# 146c1ce3466a4755a2e0733761dc4ed0
+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
+# c95ce127b66547f6922052b2dd046529
+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
+# 1cb0607405a54290aac63427224142d3
+msgid "Adding a Load Balancer Rule"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:259
+# e9125f99985c4930b8ca325f3fcf515a
+msgid "Click the name of the network where you want to load balance the traffic."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:264
+#: ../../networking/virtual_private_cloud_config.rst:1055
+#: ../../networking/virtual_private_cloud_config.rst:1323
+# e2976048502c4d5a9d5bee635ce5ee1b
+# 5b388625f3784583b0752e36f9353e8a
+# aa8c8d52101742e9a804ccc41cbcfbb3
+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
+#: ../../networking/virtual_private_cloud_config.rst:1058
+# d0100e755da442c3a5f073f8219b5816
+# bc3f9224355b4e66b73a49411a2326b8
+msgid "In the Load Balancing node of the diagram, click View All."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:269
+# aed2916e2f794074898738f6a54fd470
+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
+# cdcdffd84542448691328bee08d8de97
+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
+#: ../../networking/ip_forwarding_and_firewalling.rst:265
+# c90d375729ae4857b6cbfad14e955c25
+# 899cdfae1e1b423fa4228db904e74d4c
+msgid "Fill in the following:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:279
+#: ../../networking/virtual_private_cloud_config.rst:1064
+#: ../../networking/virtual_private_cloud_config.rst:1249
+# ee36f3f0257549b5a157b2c373cc595f
+# 03c1b13d01dd4d93abf1db0df4d270c3
+# 35a1954cf7ed4135a2a506e65626b63b
+msgid "**Name**: A name for the load balancer rule."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:281
+# 13aa4f60513144f581eaaea2a25fc259
+msgid "**Public Port**: The port receiving incoming traffic to be balanced."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:284
+#: ../../networking/virtual_private_cloud_config.rst:1069
+# 94a4f9710f0548e9b5efb1ced085ee7c
+# 43dd6392f9004b9ea68310e1bda21332
+msgid "**Private Port**: The port that the VMs will use to receive the traffic."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:287
+# 6dadc08ee20e449882fb626362f7af7f
+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
+# b7ba39ce29984655a3fee83759341968
+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
+# a79ee74d2a374432bae88b284375af8d
+msgid "**AutoScale**: Click Configure and complete the AutoScale configuration as explained in :ref:`conf-autoscale`."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:299
+# 748f88b5e1234460b650bb46124ebf32
+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
+# 57115cc9cda44c37ab09f3b0a846ddb6
+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
+# 4f4a56c64b114bfbbc4a00ffe27666f1
+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
+# 5d063fd6cf084d458e9bb553fdcaa398
+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
+# 6550d0fabfa042e698d1e24bab46eae8
+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
+# d30d4c6e04f84624988f359219dfe504
+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
+# 427464c4195c4474982b88b06a60bd2b
+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
+# b57e6480829e4e1ea39a935dfae60828
+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
+# 5b7fc7b5ea6d40a5bc3f415a80425764
+msgid "Sticky Session Policies for Load Balancer Rules"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:332
+# b9827a93606d4bd78ba8176109a6543b
+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
+# a0e599620e7d421795bf10da5e68221f
+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, cookies are used. The cookie generated by the load balancer or application is included in request and response URLs to create persistence. The cookie name can be specified by the administrator or automatically generated. A variety of options are provided to control the exact behavior of cookies, such as how they are generated and whether they are cached."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:352
+# 788d44c8346c41e88c23f175e62c939b
+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
+# 44e5efde27ff453a945b83ed79f8935b
+msgid "Health Checks for Load Balancer Rules"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:362
+# e0222e643eba40e5b2a9d97fbebef725
+msgid "(NetScaler load balancer only; requires NetScaler version 10.0)"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:364
+# cdf4e72bdd1842b38d1c7c61809209b5
+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
+# 3186740a23ed4c6ba61108544d0a4aec
+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
+# ec37f719769d4b7386f0b940981fed70
+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 with a health check configured, the state will be shown as UP or DOWN in the UI depending on the result of the most recent health check."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:386
+# e7b935bafd4a47d68590f912c335e640
+msgid "You can delete or modify existing health check policies."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:388
+# c111733988ec45f6bcd2979e368c5226
+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
+# 4c9ae4abb3c04ebda936ddf28d4b1250
+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
+# 3d3b622fa6c24a71a43dfb7d262e68ff
+msgid "Configuring AutoScale"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:402
+# 5b23f0c9a3884ba4a454fd703688166f
+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
+# 5141d63f3ea14b7cb903e6c53d86085f
+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 CPU usage is less than 20 percent for 30 minutes."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:419
+# f32191641b9644909945358cb69ebe4d
+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
+# 56002db08e75494cac10bdd7f2b5c707
+msgid "AutoScale is supported on NetScaler Release 10 Build 74.4006.e and beyond."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:430
+# 45a1a6402e1e40a0a91763809e1b7729
+msgid "Before you configure an AutoScale rule, consider the following:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:432
+# 0a687417e2094c359d8a604e95095fc5
+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
+# 7d9b17872f514d4c88eedbe080005a94
+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
+# c72572ced880471fa607c51156f11bda
+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
+# ff134327842d420886adb98a42f2723a
+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-server>`_ to configure SNMP on a RHEL machine."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:456
+# d8cef4ea8860477489a80f3a715fbd90
+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
+# 1cd70adcb30d47abbcc3dc69e3707036
+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
+# 55df6ae7033b4ca3a3f52dd90fd74501
+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
+# f6552bde1aaf4055b316eb9c17b5f64a
+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
+# a79a1b3a477d4397abe465f3b5ba2c56
+msgid "Configuration"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:484
+# 7d9d1fe996094830bd4e91ea3b3632e7
+msgid "|autoscaleateconfig.png|"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:486
+# 4fc1aed8f2864acba56525d8509dfc38
+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
+# 15493a90f6c04d51a80a4caaa5a833c5
+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
+# 55397884cbb84b2cb778668b2f01bb7e
+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
+# c33b18f0b309446eb974ca219945f004
+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 active instance count breaches the Max instance value."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:518
+# f040e7755d074bee8817ada9261b421b
+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
+# 2115dadd36d541558713322993492848
+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
+# 40a5c798ef9d4d7584efa6400c0edfac
+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
+# 19812fc19c6a4a7d9ebc51b8e0ecb75b
+msgid "Specify the following scale-up and scale-down policies:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:539
+# 74891b0d3cfd491f863a6557f788d493
+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
+# 436acb44653a45cc9c54ff9c950b7a56
+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
+# 2137176110684b2db672902ab582654c
+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
+# fce26387204d4e949d43cee1c917b9c0
+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
+# f9e47cc9e3ad4739a2e6ef1470a50570
+msgid "**Add**: Click Add to add the condition."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:561
+# 3ea8d8738fdd408fb23e11b899d7b418
+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
+# 9fafd8d4c0614661af2bc64d9c06879e
+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
+# c719d597315640dc81a33fab44ae0a0e
+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
+# 98b814f48ff24f0c9ed3bca9f2dd1619
+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
+# bcae2f20091343669f94311a955eb918
+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
+# 24e7476382c24a7a8bdb85ceef987fcb
+msgid "**Disk Offerings**: A predefined set of disk size for primary data storage."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:592
+# 8b28accd4fce47b6afc47f2341e26d5d
+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
+# e01443d94f864a8e80ec211f1a96c910
+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
+# 64c6d2f9ae6f4ac3b09f31d6fb0e360c
+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
+# 062c87f44c6f4c92916dae1a85b891cc
+msgid "**Apply**: Click Apply to create the AutoScale configuration."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:608
+# 6563ec698c3d499ab5e8e86cb3073ff0
+msgid "Disabling and Enabling an AutoScale Configuration"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:610
+# e1b4da3ad2534f6c8fba4e5ec4616af2
+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
+# eb31769bc729463bbdd6b8d9bd472847
+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
+# 800c645e10c34f3b96d364a7e7b44570
+msgid "Updating an AutoScale Configuration"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:628
+# 35012a4fdbe84c63a612c99f0ba31d1b
+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
+# b87ea7a2a6c5474392ec23163db4cadb
+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
+# 4b66b8ccf0284d27afeafec62196c28b
+msgid "Runtime Considerations"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:641
+# c38f40d156554c08a840a51d5bc01d89
+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
+# dee362b009924ebea8ca92bdd9f61f8d
+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
+# 68fd9fba22874c88aeee1a1e17da457f
+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 ""
+
+#: ../../networking/global_server_load_balancing.rst:18
+# 25734f8479cd4aeaa96bc94c9e97b3f0
+msgid "Global Server Load Balancing Support"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:20
+# 4281e272ec6741e89ba2c668c2b466e9
+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
+# 6945e2d89c9d4d758cba8b0168f0b818
+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
+# e5df28b9850c419293fdae6e4e253ab5
+msgid "About Global Server Load Balancing"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:39
+# 0b8dcd5aa2ba4b9984c94850cd1c44a9
+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 accessing a resource in the event of a failure, or to provide a means of shifting traffic easily to simplify maintenance, or both."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:51
+# ab0467a3e9d24e78b8e9e16d225ce4b3
+msgid "Components of GSLB"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:53
+# f131bfe486894f13961e91b6409ae286
+msgid "A typical GSLB environment is comprised of the following components:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:55
+# 6bc81bb78e4c4bd9974edba31c58d4cf
+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
+# ed55296b3210425390ee6cb680b0f347
+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
+# f00eb1ec7b75437699e4603066de4f63
+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 a FQDN DNS name."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:81
+# ca80f04e2c8542269d92af6e7de92d03
+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 balancing or content switching virtual server, the client sends the request to that virtual server's VIP address."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:91
+# d008156342444851b79a1c914ff2dbcb
+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
+# 71d33e18670d4b49a2881ebc9a6de115
+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 and port."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:107
+# 0a4b19e96b7140af83a35ab77bc744af
+msgid "How Does GSLB Works in CloudStack?"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:109
+# 3fcf9c5675d647d09f1b6df17ad60cc1
+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 xyztelco cloud. For that purpose, they launch two instances each in both the zones: VM1 and VM2 in Zone-1 and VM5 and VM6 in Zone-2. Tenant-A acquires a public IP, IP-1 in Zone-1, and configures a load balancer rule to load balance the traffic between VM1 and VM2 instances. CloudStack orchestrates setting up a virtual server on the LB service provider in Zone-1. Virtual server 1 that is set up on the LB service provider in Zone-1 represents a publicly accessible virtual server that client reaches at IP-1. The client traffic to virtual server 1 at IP-1 will be load balanced across VM1 and VM2 instances."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:126
+# 16209a7b07e746f19adc6902ea420f50
+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 instances. At this point Tenant-A has the service enabled in both the zones, but has no means to set up a disaster recovery plan if one of the zone fails. Additionally, there is no way for Tenant-A to load balance the traffic intelligently to one of the zones based on load, proximity and so on. The cloud administrator of xyztelco provisions a GSLB service provider to both the zones. A GSLB provider is typically an ADC that has the ability to act as an ADNS (Authoritative Domain Name Server) and has the mechanism to monitor health of virtual servers both at local and remote sites. The cloud admin enables GSLB as a service to the tenants that use zones 1 and 2."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:144
+# d073e26f378940f9b2b7bacfdc8d7e0a
+msgid "|gslb.png|"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:146
+# 78fe59c21fad44febb867459cdd3c4fc
+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 start monitoring the health of virtual server 1 and 2 in Zone-1. CloudStack will also orchestrate setting up GSLB virtual server 2 on GSLB service provider at Zone-2. CloudStack will bind virtual server 1 of Zone-1 and virtual server 2 of Zone-2 to GLSB virtual server 2. GSLB virtual server 2 is configured to start monitoring the health of virtual server 1 and 2. CloudStack will bind the domain A.xyztelco.com to both the GSLB virtual server 1 and 2. At this point, Tenant-A service will be globally reachable at A.xyztelco.com. The private DNS server for the domain xyztelcom.com is configured by the admin out-of-band to resolve the domain A.xyztelco.com to the GSLB providers at both the zones, which are configured as ADNS for the domain A.xyztelco.com. A client when sends a DNS request to resolve A.xyztelcom.com, will eventually get DNS delegation to the address of GSLB providers at zone 1 and 2. A client DNS request will be received by the GSLB provider. The GSLB provider, depending on the domain for which it needs to resolve, will pick up the GSLB virtual server associated with the domain. Depending on the health of the virtual servers being load balanced, DNS request for the domain will be resolved to the public IP associated with the selected virtual server."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:175
+# ec2c5b7b09154785b795d77e01eadd4d
+msgid "Configuring GSLB"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:177
+# 9df6a592e23d49148060b5c6ca5e52ac
+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 servers. Finally, bind the domain to the GSLB virtual servers. The GSLB configurations on the two appliances at the two different zones are identical, although each sites load-balancing configuration is specific to that site."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:189
+# ea099698d96f40f7adcc38a2fc9c997d
+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
+# ac5abddeadb048d794cccae84c2689cb
+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
+# 628b54626394479caf7ea8d6fd8d3210
+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
+# 4ae673b1b0a741d4a8ae715022d39bfc
+msgid "Configuring a standard load balancing setup."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:201
+# a3e3a1d93b6a48128aea3a0dee30c2ce
+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
+# 1bbbaf3fabe54fa8bd1f12d3cf85553d
+msgid "Configure a GSLB site with site name formed from the domain name details."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:208
+# 9bbfadb6046f4a089e701c8968231bf1
+msgid "Configure a GSLB site with the site name formed from the domain name."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:211
+# 5c91f57c9b0a4c1b81467b113da3b368
+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
+# cf4285866ee549228e56d7a5b5423e75
+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
+# 665433a1ecba490ca6d1a6f594d8d15d
+msgid "Configure a GSLB virtual server."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:219
+# 62a5af1b8ba947619f77fffcc044737e
+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
+# b5348156d5684555bf4a16f7b0aed2e1
+msgid "Configure a GSLB service for each virtual server."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:224
+# 1be7e75accb342118f2db621053cd0ca
+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
+# a057f57840c249baa28d0ea92fb18a4d
+msgid "Bind the GSLB services to the GSLB virtual server."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:229
+# 54fde0c1b28d4b218b1b38fd69512fc7
+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
+# b238ffa658954d6bb8950514feb4309e
+msgid "Bind domain name to GSLB virtual server. Domain name is obtained from the domain details."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:235
+# ddb89d80e86542fca93e99d812871a42
+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
+# 994ecce5579142d68bbcabc7fbbcee66
+msgid "In each zone that are participating in GSLB, add GSLB-enabled NetScaler device."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:241
+# 77a9ecb28f3c42fa871ca4293f5fb3c2
+msgid "For more information, see :ref:`enabling-gslb-in-ns`."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:243
+# 9d1700ef75be4986a54fd1e51b7daf09
+msgid "As a domain administrator/ user perform the following:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:245
+# 1b28e385ddd9459f934219e64252f08a
+msgid "Add a GSLB rule on both the sites."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:247
+# b3f6d2228fdd4f249692765a44df3257
+msgid "See \":ref:`adding-gslb-rule`\"."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:249
+# d4539ca63ba143f5a57e95a7cc50c138
+msgid "Assign load balancer rules."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:251
+# 5e832683ca534485b0fbd672a249e511
+msgid "See \":ref:`assigning-lb-rule-gslb`\"."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:257
+# 9fd9a67186904ceda46fa7d9e61e6dce
+msgid "The GSLB functionality is supported both Basic and Advanced zones."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:259
+# 155a1b915c7840afae25327ef3a7f6bb
+msgid "GSLB is added as a new network service."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:261
+# b5681032556f4430a86b311f53d393c5
+msgid "GSLB service provider can be added to a physical network in a zone."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:263
+# ba83a0e977bc4a3abc65c3f30c4684d4
+msgid "The admin is allowed to enable or disable GSLB functionality at region level."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:266
+# 682239c65afe4c2fa7312feeac21e9bf
+msgid "The admin is allowed to configure a zone as GSLB capable or enabled."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:268
+# 16c808c16f1e4f22a5294f1060dfe2c3
+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
+# 54c1b30001084a9d88eb89799461dc9f
+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
+# 04c2a492332c437daed8f4ef774ba016
+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
+# 1f9b8a3555524eaea6e144288b6f74a6
+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
+# 56f19e5d46de43f5b7e3ac6674a8084b
+msgid "The admin can configure DNS name for the entire cloud."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:283
+# 5d62e65b44ab487688e71984b4665f2b
+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
+# ed7a5577959a4271b7b98ac369d63874
+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
+# 8cac76f1529943b5a001cc5e9e8978ac
+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
+# d53da99edf45482fae37a6beabd277e0
+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
+# 7a49a6392b3841eea149e6bda34bf00a
+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
+# bb4138b786e9474fb0ed35738608df60
+msgid "Statistics is collected from each GSLB virtual server."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:311
+# 47055f92a29342529bfcdc61d569e7e5
+msgid "Enabling GSLB in NetScaler"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:313
+# 993ee7e5933440be90a5d733c261dbfa
+msgid "In each zone, add GSLB-enabled NetScaler device for load balancing."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:315
+# 1ccc47562da1485ebadaf564a75a1e8f
+msgid "Log in as administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:319
+# 50c53a288e5c4ba8a5873ae93ce2ebc1
+msgid "In Zones, click View More."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:323
+# 426b0fac04b243adae39f7591362417b
+msgid "Click the Physical Network tab, then click the name of the physical network."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:326
+# fafed439faa145cfbd6e0660489f0c23
+msgid "In the Network Service Providers node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:329
+# fd8f072b359a4f04ad326eb3d908940d
+msgid "You might have to scroll down to see this."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:331
+# 4cb81ecc1e2041ac85015a942c236caf
+msgid "Click NetScaler."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:333
+# fd9c663d6f344362bc282938fa9a7568
+msgid "Click Add NetScaler device and provide the following:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:335
+# 482e597c23cc41b798a1610afce4cdeb
+msgid "For NetScaler:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:337
+# 3294458f8c544dd2b784f2fa14c2aa67
+msgid "**IP Address**: The IP address of the SDX."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:339
+# b70b5b91f59c409c9dd3966293451a99
+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
+# 8ef3b665ac154e6287ad6ea81148049c
+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
+# 2e237e04e2dc44aa9a63e9b610481683
+msgid "**Public interface**: Interface of device that is configured to be part of the public network."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:351
+# 1768efdd0e38457882de8c3f6a4bc7ac
+msgid "**Private interface**: Interface of device that is configured to be part of the private network."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:354
+# d7a97e5326bf493ea8de67360056032f
+msgid "**GSLB service**: Select this option."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:356
+# 3169f742f2b541cf9ba5e47685b71979
+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
+# 8aea303aff5746d887377f892f81bedb
+msgid "**GSLB service Private IP**: The private IP of the GSLB service."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:361
+# 12ef6d7387b1493fbb70926187f28853
+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
+# 66bbb327d60548f78a85f6f748811885
+msgid "**Capacity**: The number of networks the device can handle."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:366
+# d60d1dd86fb4433b99b28a0c96f1576a
+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:377
+# 69bd10926c1b4f639cc360e4c6418c3e
+msgid "Adding a GSLB Rule"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:379
+#: ../../networking/global_server_load_balancing.rst:423
+# d8d474dabeab4c1f8f00fa162277cd18
+# 2533afdf8c2f4af0ae6a8c0a349218af
+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
+# 7550ed528a27426c853c744100fd4ae1
+# a6856d0d96014ad4bcf0169664b844e3
+msgid "In the left navigation pane, click Region."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:383
+#: ../../networking/global_server_load_balancing.rst:427
+# 5a1ef80e398e476bb8d0a513004669b9
+# 8f5b19bc2a244501b359c7b31af3d903
+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
+# de6f8ae256d04834b07c2f957c2d329f
+# 14610babee3a4c4f98ccda032d8a1a24
+msgid "In the Details tab, click View GSLB."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:387
+# 9c265b9b1d6f450fbb90a2dab4a3dd4d
+msgid "Click Add GSLB."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:389
+# 7b20c6e1ba68451d9c097b40cf182ed5
+msgid "The Add GSLB page is displayed as follows:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:391
+# 156298ad77934768a3936c310cb506c7
+msgid "|gslb-add.png|"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:395
+# 94ceaa226a6348128cee4e536b67def7
+msgid "**Name**: Name for the GSLB rule."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:397
+# 1bedbf6a59124f5ab5ad9ae9d676f428
+msgid "**Description**: (Optional) A short description of the GSLB rule that can be displayed to users."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:400
+# 760fed68b0f1425d813d3da44e010ef0
+msgid "**GSLB Domain Name**: A preferred domain name for the service."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:402
+# f10e909d63a847f2ac92ce505fbe7453
+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
+# 5bd10eaef9ea49fdafb1aaf2a6d04f89
+msgid "**Service Type**: The transport protocol to use for GSLB. The options are TCP and UDP."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:409
+# 5a07001702fd46899b6363fe3e335dda
+msgid "**Domain**: (Optional) The domain for which you want to create the GSLB rule."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:412
+# f95e0967cf5b4586af07b8c278fa7f2c
+msgid "**Account**: (Optional) The account on which you want to apply the GSLB rule."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:421
+# 8e6fff3aabfc4338a6d75cc7a0817e74
+msgid "Assigning Load Balancing Rules to GSLB"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:431
+# c1a5b66d72da4e03acd469f7c6097117
+msgid "Select the desired GSLB."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:433
+# 1a740350bc534faaaa40f53959d4fee9
+msgid "Click view assigned load balancing."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:435
+# daff37ebdd2349a497dab10e0d234426
+msgid "Click assign more load balancing."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:437
+# d63a5166197e4a17b6bd9ab1cd618814
+msgid "Select the load balancing rule you have created for the zone."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:443
+# 35f5b11c84c142c58580b76bb4ddadfd
+msgid "Known Limitation"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:445
+# 89c2b07fa33e40838e9c4de58e3296be
+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 ""
+
+#: ../../networking/guest_ip_ranges.rst:18
+# 43426b72e0e24e35a5898286a3dd3dc2
+msgid "Guest IP Ranges"
+msgstr ""
+
+#: ../../networking/guest_ip_ranges.rst:20
+# 8ad2743b8f6d4eb1bf10b5afb1c89f54
+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
+# dc1be0f75ec04a468b17af4d2750b1ca
+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 ""
+
+#: ../../networking/acquiring_an_ip_address.rst:18
+# 5daf1c058a0c43718015e5812d9c0836
+msgid "Acquiring a New IP Address"
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:34
+# 32dbea4bf3a6422da3941f2407b12a71
+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
+# b8ffa6eff3794134bf11db68c7c32099
+msgid "For more information on Portable IP, see `\"Portable IPs\" <#portable-ips>`_."
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:18
+# d5be22795b3d4926be02f94cc069db79
+msgid "Releasing an IP Address"
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:20
+# d608beb5fbb544afaaad161b9661dcb0
+msgid "When the last rule for an IP address is removed, you can release that IP address. The IP address still belongs to the VPC; however, it can be picked up for any guest network again."
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:32
+# cbede7f4af98499c97ff53a446ca173d
+msgid "Click the IP address you want to release."
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:34
+# b5f7d64cc75b4ee18855fa6ad6f1438d
+msgid "Click the Release IP button. |ReleaseIPButton.png|"
+msgstr ""
+
+#: ../../networking/static_nat.rst:18
+#: ../../networking/remote_access_vpn.rst:118
+#: ../../networking/remote_access_vpn.rst:452
+#: ../../networking/remote_access_vpn.rst:515
+#: ../../networking/remote_access_vpn.rst:647
+#: ../../networking/virtual_private_cloud_config.rst:348
+#: ../../networking/virtual_private_cloud_config.rst:515
+#: ../../networking/virtual_private_cloud_config.rst:750
+#: ../../networking/virtual_private_cloud_config.rst:808
+#: ../../networking/virtual_private_cloud_config.rst:869
+#: ../../networking/virtual_private_cloud_config.rst:1035
+#: ../../networking/virtual_private_cloud_config.rst:1303
+# 6d82408293c1416ca310c302379aa09a
+# 2fb7e2316ee54739935361a2c3eaeeb3
+# e63c1fef73664de395b24f2fd3232139
+# a499d21cfffe4303bb3b23988d32ed53
+# 692e4e5ab7df4a7cbc791aa7fa428661
+# bd6701c2c7bb43c3b81bd5a810215d73
+# e357c811590c493c8341f10d87e99492
+# ad2e62635b524cfd95d4640c69979c8e
+# ba9cd4d358194f5bb69c7779b84c8c27
+# 24720c3dbfa6455a9c417b49062ebfd7
+# c7886284bd2c4db990aecc9f5d015a0c
+# b1144b4196da4257868a1599fb14431d
+msgid "Static NAT"
+msgstr ""
+
+#: ../../networking/static_nat.rst:20
+# 894073bd52434748977055e7ee9a6604
+msgid "A static NAT rule maps a public IP address to the private IP address of a VM in order to allow Internet traffic into the VM. The public IP address always remains the same, which is why it is called static NAT. This section tells how to enable or disable static NAT for a particular IP address."
+msgstr ""
+
+#: ../../networking/static_nat.rst:28
+# 3ce1cecac4bf48f6bc8b81b403d9e42b
+msgid "Enabling or Disabling Static NAT"
+msgstr ""
+
+#: ../../networking/static_nat.rst:30
+#: ../../networking/virtual_private_cloud_config.rst:842
+# ca8d159797c4416288520787181cb2f5
+# 7732dac53f9c44c3884d468654271191
+msgid "If port forwarding rules are already in effect for an IP address, you cannot enable static NAT to that IP."
+msgstr ""
+
+#: ../../networking/static_nat.rst:33
+#: ../../networking/virtual_private_cloud_config.rst:845
+# a931121d677f4d04b656aca83f043d26
+# c2bb747e18d64159bd3605ffa4f2f044
+msgid "If a guest VM is part of more than one network, static NAT rules will function only if they are defined on the default network."
+msgstr ""
+
+#: ../../networking/static_nat.rst:44
+#: ../../networking/ip_forwarding_and_firewalling.rst:67
+# 33a01340d067438a8dfaf19d33406d95
+# 39954d50f8bc407f84931182c3e7dd86
+msgid "Click the IP address you want to work with."
+msgstr ""
+
+#: ../../networking/static_nat.rst:46
+# a33212ef265c4bc68a9ed53a9c693df0
+msgid "Click the Static NAT |enabledisablenat.png| button."
+msgstr ""
+
+#: ../../networking/static_nat.rst:48
+# c6c4c974f1b44a05823bc42e28095e76
+msgid "The button toggles between Enable and Disable, depending on whether static NAT is currently enabled for the IP address."
+msgstr ""
+
+#: ../../networking/static_nat.rst:51
+# 0e003c10fb6b4b86a1c8fb0d260fb702
+msgid "If you are enabling static NAT, a dialog appears where you can choose the destination VM and click Apply."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:18
+# ab5d3e20a35044a490aa5251c4b85f4d
+msgid "IP Forwarding and Firewalling"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:20
+# aee28d66b74c499597d47124ee883143
+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
+# 387c2271d56a4e12beb6624f511851c8
+msgid "To allow outgoing traffic, follow the procedure in :ref:`egress-fw-rules`."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:25
+# 2e337162d6dd4714a9a6a2542e8a146e
+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
+# 3b46ec3be763405b94a219d0c00a44d9
+msgid "Firewall Rules"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:37
+# 289b2b9b80b942a7bd122ec6a45830a1
+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
+# aebb1c0165554e0eaf7198fa58bb0243
+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
+# a63a51dddfbc4821b71342f76ea15396
+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
+# 9cdd6b4c846447d8bf19cfb8b5b22829
+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
+# 109ed3b0aad347d99e3cff3240722f30
+msgid "To create a firewall rule:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:69
+# ec5934105a19458782c675dd18684173
+msgid "Click the Configuration tab and fill in the following values."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:71
+# 61cd332681ea4fccb7a69d35effdfbe0
+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
+# fbecf77ee36345b38502a02307d58865
+msgid "**Protocol**: The communication protocol in use on the opened port(s)."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:79
+# 87689392abf14a949afbc25ee0410466
+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
+# 9e4666af35d043358c3246ec14509b78
+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:94
+# c0ae5406014e43d4a50a05ed74aa8dc8
+msgid "Egress Firewall Rules in an Advanced Zone"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:96
+# bf3e32d6e33f4bb199a83e9ee2a6d307
+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 rules are removed the default policy, Block, is applied."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:109
+# bedc63fb7a3b4ba2ad3a4f4c4992b742
+msgid "Consider the following scenarios to apply egress firewall rules:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:111
+# 20406d7e04b74d6d9adb04b039195d77
+msgid "Egress firewall rules are supported on Juniper SRX and virtual router."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:114
+# 97a42a58db4c4505919b767f168001e8
+msgid "The egress firewall rules are not supported on shared networks."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:116
+# 1bd785cd4def48be9265615471d02ced
+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
+# ff0740d14f3f454395f0342767084065
+msgid "Allow the egress traffic with protocol TCP,UDP,ICMP, or ALL."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:121
+# 3da424158d4a46fb955bad940049cfaf
+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
+# bfec00d70b32484abdd2be7a7067fb12
+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
+# 77a21030af6444aaac365dc1d6c1a40e
+msgid "Configuring an Egress Firewall Rule"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:136
+# d7e0415b36d0404bb5d71baf38d49af2
+msgid "In Select view, choose Guest networks, then click the Guest network you want."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:139
+# acbfbe60bbfa423ab99d7faeea324dac
+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
+# 93d9dbdbdf68488fb08f2c93714eb381
+msgid "|egress-firewall-rule.png|"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:145
+# 71041bfd382d4c2ea6e0339c055e8e66
+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
+# 136a4ea4a1424e4fb3a4e36f7ba438c7
+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
+# a710752f5a514f3e92ca3474b03d66b0
+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
+# 273049a1dabe4b00aab163a686500120
+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
+# 0ba1bc60e7114766b5562aa9f590799d
+msgid "Configuring the Default Egress Policy"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:169
+# 8b256b4cb62e43fe879f448d1cb5c940
+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
+# b03f1cb4957b4a18b437e26cca194176
+msgid "You have two options: Allow and Deny."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:180
+# faccf3355885414e87bbb03070f6a7c0
+msgid "Allow"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:182
+# a7d3b32fbf8448c5ab02390ca3e1cc21
+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
+#: ../../networking/virtual_private_cloud_config.rst:323
+#: ../../networking/virtual_private_cloud_config.rst:324
+# 17b36c3415d3468896d8b48ae47ca8a8
+# 6cccf344439e4750904131cef8ef2b39
+# 1208ff713d13448f8bb67189a2a733dd
+msgid "Deny"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:191
+# 933662ed493243f599791cfc52e41965
+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
+# 0f97837bd48b43808e4499c3bca32f0a
+msgid "This feature is supported only on virtual router and Juniper SRX."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:200
+# 12362b3472604a26858c49a699414934
+msgid "Create a network offering with your desirable default egress policy:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:202
+# e3686a1cbaa54de4adb23df170fdbb9a
+msgid "Log in with admin privileges to the CloudStack UI."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:204
+# 2b34103f06b74a83956a2e4aa4c43e89
+msgid "In the left navigation bar, click Service Offerings."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:206
+# be40a0ea880c4159a9d420c70881eeba
+msgid "In Select Offering, choose Network Offering."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:208
+#: ../../networking/virtual_private_cloud_config.rst:961
+#: ../../networking/virtual_private_cloud_config.rst:1167
+# 3b005d62ac404f7a971817f2e813a88a
+# 42bbce384f5b43a39000860f820fe3a0
+# 80979f7b880b45f0864683361aa46fd3
+msgid "Click Add Network Offering."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:210
+# d3e708006ce243298b2fdbfef4a94a28
+msgid "In the dialog, make necessary choices, including firewall provider."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:213
+# a6aaeba01e87402cab4799e384a7e8b7
+msgid "In the Default egress policy field, specify the behaviour."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:217
+# dfeed74eee834f7aa70dc9a0ebca0b5d
+msgid "Create an isolated network by using this network offering."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:219
+# d4f2f0db67ad4becad9ecf217e63fc08
+msgid "Based on your selection, the network will have the egress public traffic blocked or allowed."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:224
+# 49dbcf0869cc408aac40d8ace99c793b
+msgid "Port Forwarding"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:226
+# d63e7dc020174931a136b5f851d10342
+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
+# 28ad8f3213ac41ed9debe3407c4cf783
+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
+# acee955e81034850834c7f10a308dd65
+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
+# 456211f25f094d9090dc8de808d1c666
+msgid "To set up port forwarding:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:247
+# d0f998d8aa0a48f9a3f19ea0d36f07d2
+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
+# 10d08ed8092843f18456b1a0752ba168
+msgid "Add one or more VM instances to CloudStack."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:253
+# bdd495a8008d4823b8bd78a763cca275
+msgid "In the left navigation bar, click Network."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:255
+# 73ad1f9cd260427bb05aeb2d4ca2f056
+msgid "Click the name of the guest network where the VMs are running."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:257
+# 89c3b56ae71346e9b89fa5e446f3f43d
+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
+# 2c19d7e25d8845cbba9fd2d132c04fb7
+msgid "Click the Configuration tab."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:263
+#: ../../networking/virtual_private_cloud_config.rst:1326
+# a9244a779ecb4355bbabd6689495a9ae
+# 35dbd54b25cb438f97ccf2f32ff9370e
+msgid "In the Port Forwarding node of the diagram, click View All."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:267
+#: ../../networking/virtual_private_cloud_config.rst:1332
+# a51ed2228b8a437386ad9ff99ee96a04
+# e6d29f52eea44172bfaa95b47d20d5b9
+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
+#: ../../networking/virtual_private_cloud_config.rst:1335
+# 994ccfa7425f4863ade7a74a14b9e011
+# 5fbd968022954bba912d0dfdbe504ad9
+msgid "**Private Port**: The port on which the instance is listening for forwarded public traffic."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:273
+# 98023e5bfedb4649a79fadc67850521f
+msgid "**Protocol**: The communication protocol in use between the two ports"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:18
+# b71d2a4a35644691974638b71dbe56b1
+msgid "IP Load Balancing"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:20
+# 982a5f5a6b7f481dbf623c4ae30c9ef1
+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
+#: ../../networking/virtual_private_cloud_config.rst:1076
+#: ../../networking/virtual_private_cloud_config.rst:1272
+# a01b6fefc32a4fce911ca69c16c670d9
+# 28c60cdb8d574461b463ea6e8e14675c
+# b09a939f044f421d83e16513b3a9dc7b
+msgid "Round-robin"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:26
+# e8cdafa2b1f645e99d3133d52f0a355a
+msgid "Least connection"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:28
+# 803259d2ae8f446a9c4ec7c8ed71a28b
+msgid "Source IP"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:30
+# 6ba67a79525947f49fd89a4630112c11
+msgid "This is similar to port forwarding but the destination may be multiple IP addresses."
+msgstr ""
+
+#: ../../networking/dns_and_dhcp.rst:18
+# f64b9bee4c5c4f5b8edb7227f447c380
+msgid "DNS and DHCP"
+msgstr ""
+
+#: ../../networking/dns_and_dhcp.rst:20
+# b1490bbc343240eba492e29dd3431440
+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 ""
+
+#: ../../networking/remote_access_vpn.rst:18
+# 380298c917b144379af6fe612e2d842a
+msgid "Remote Access VPN"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:20
+# 6e90c60bc41e4969b0281b09531745b8
+msgid "CloudStack account owners can create virtual private networks (VPN) to access their virtual machines. If the guest network is instantiated from a network offering that offers the Remote Access VPN service, the virtual router (based on the System VM) is used to provide the service. CloudStack provides a L2TP-over-IPsec-based remote access VPN service to guest virtual networks. Since each network gets its own virtual router, VPNs are not shared across the networks. VPN clients native to Windows, Mac OS X and iOS can be used to connect to the guest networks. The account owner can create and manage users for their VPN. CloudStack does not use its account database for this purpose but uses a separate table. The VPN user database is shared across all the VPNs created by the account owner. All VPN users get access to all VPNs created by the account owner."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:35
+# c670185e66c148958a214fecee43aff5
+msgid "Make sure that not all traffic goes through the VPN. That is, the route installed by the VPN should be only for the guest network and not for all traffic."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:39
+# dba6da095c764124a25c5a98d801496e
+msgid "**Road Warrior / Remote Access**. Users want to be able to connect securely from a home or office to a private network in the cloud. Typically, the IP address of the connecting client is dynamic and cannot be preconfigured on the VPN server."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:44
+# 8793d40a1a80441398907f711e568b99
+msgid "**Site to Site**. In this scenario, two private subnets are connected over the public Internet with a secure VPN tunnel. The cloud user's subnet (for example, an office network) is connected through a gateway to the network in the cloud. The address of the user's gateway must be preconfigured on the VPN server in the cloud. Note that although L2TP-over-IPsec can be used to set up Site-to-Site VPNs, this is not the primary intent of this feature. For more information, see \":ref:`setting-s2s-vpn-conn`\"."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:55
+# 8c8d8279293b421c868d44267f2291d1
+msgid "Configuring Remote Access VPN"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:57
+# 90ad6dccf00c4430ac2951fce79496d6
+msgid "To set up VPN for the cloud:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:61
+# e37d36e8639e48b5a1043c2e57008523
+msgid "In the left navigation, click Global Settings."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:63
+# 505b3a7726bc48fda8c03560c7bf88b1
+msgid "Set the following global configuration parameters."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:65
+# 53ec16f914374f86a2beb90e7af26ece
+msgid "remote.access.vpn.client.ip.range - The range of IP addresses to be allocated to remote access VPN clients. The first IP in the range is used by the VPN server."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:69
+# f4300671c2a149c284a642b6f79ef00e
+msgid "remote.access.vpn.psk.length - Length of the IPSec key."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:71
+# 231df586fa3c4ed1970d5b7575cc5b83
+msgid "remote.access.vpn.user.limit - Maximum number of VPN users per account."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:74
+# 76cfe55cf6cf458e93e7c31c53fd06c7
+msgid "To enable VPN for a particular network:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:76
+#: ../../networking/remote_access_vpn.rst:101
+# 7c4372020568480ea2a617b164d7fde7
+# 84de4841949448d09c061ed72abcd263
+msgid "Log in as a user or administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:78
+#: ../../networking/remote_access_vpn.rst:103
+# 1b8df6da450a4c73b2f16aa4eaca745f
+# 5be9a0df2c9b497c95947824049942f6
+msgid "In the left navigation, click Network."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:80
+# 4a0bb2f81c4f4829853bbbb9f5fdcdea
+msgid "Click the name of the network you want to work with."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:84
+# dcdbca37932e4934822095b46a7460fd
+msgid "Click one of the displayed IP address names."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:86
+#: ../../networking/remote_access_vpn.rst:140
+# c58b358559ab46a8b37d20c157cabb78
+# 3d371180587a4467995d29840af82de7
+msgid "Click the Enable VPN button. |vpn-icon.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:88
+# d3fc3632ae204d92945354ecf5b17a1c
+msgid "The IPsec key is displayed in a popup window."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:92
+# 866b778ea915477a8513f360a7923a9f
+msgid "Configuring Remote Access VPN in VPC"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:94
+# 4f7b18dfcf584e5c90d57d8e8a471744
+msgid "On enabling Remote Access VPN on a VPC, any VPN client present outside the VPC can access VMs present in the VPC by using the Remote VPN connection. The VPN client can be present anywhere except inside the VPC on which the user enabled the Remote Access VPN service."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:99
+# cf87d57665af4942874e753a98b32768
+msgid "To enable VPN for a VPC:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:105
+#: ../../networking/remote_access_vpn.rst:435
+#: ../../networking/remote_access_vpn.rst:497
+#: ../../networking/remote_access_vpn.rst:628
+#: ../../networking/virtual_private_cloud_config.rst:183
+#: ../../networking/virtual_private_cloud_config.rst:227
+#: ../../networking/virtual_private_cloud_config.rst:335
+#: ../../networking/virtual_private_cloud_config.rst:384
+#: ../../networking/virtual_private_cloud_config.rst:496
+#: ../../networking/virtual_private_cloud_config.rst:666
+#: ../../networking/virtual_private_cloud_config.rst:733
+#: ../../networking/virtual_private_cloud_config.rst:792
+#: ../../networking/virtual_private_cloud_config.rst:852
+#: ../../networking/virtual_private_cloud_config.rst:1018
+#: ../../networking/virtual_private_cloud_config.rst:1231
+#: ../../networking/virtual_private_cloud_config.rst:1286
+#: ../../networking/virtual_private_cloud_config.rst:1364
+#: ../../networking/virtual_private_cloud_config.rst:1392
+# a851855e564c4ad2abb7f191c35fc2e8
+# 7696ccb576dc417482a5c054ceca9b60
+# e018f229d0304c21bc251e3bcaf4174e
+# 853e8a12190242e1922b7e3eceeacd90
+# 858d04db9e0d49328574f666ca08832b
+# 7e353532572644f29c0956717585ae5d
+# 3788df11cb0b4d9f99e69906815734a3
+# 2bb59ff5316a4315ad133017bc7aaa7b
+# 19560e560096444384f47cc8bcc957a9
+# 92e2187aa49046a4a1c1d8e8b50caeda
+# 74ff9845b2fc4a28a4f6e5c10d5b5e41
+# 3f4c3248f6b74195aadf920c9d064ea0
+# 37596bbfca114dd292c20a4d712a56d4
+# 474cd3b9ddcf45209e8b7f7c20094087
+# f011af1bc62c416bb2cc09b3e6d1da82
+# 51106dd7db2e450480c1b806d5f8c575
+# 20cb483c8c1a457d88d907105a2df0b6
+# 20037f12721b44a5b069106ec01c9037
+msgid "In the Select view, select VPC."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:107
+#: ../../networking/remote_access_vpn.rst:437
+#: ../../networking/remote_access_vpn.rst:630
+#: ../../networking/virtual_private_cloud_config.rst:337
+#: ../../networking/virtual_private_cloud_config.rst:386
+#: ../../networking/virtual_private_cloud_config.rst:498
+#: ../../networking/virtual_private_cloud_config.rst:668
+#: ../../networking/virtual_private_cloud_config.rst:735
+#: ../../networking/virtual_private_cloud_config.rst:794
+#: ../../networking/virtual_private_cloud_config.rst:854
+#: ../../networking/virtual_private_cloud_config.rst:1020
+#: ../../networking/virtual_private_cloud_config.rst:1233
+#: ../../networking/virtual_private_cloud_config.rst:1288
+#: ../../networking/virtual_private_cloud_config.rst:1394
+# 433a058aaf2c4f7abcac16a4a89c0cb0
+# 253f99defd504664bca4c20805fad8d8
+# b03f74003e0f49f7b107d129dc8378f5
+# 0c712fdfecf145558f1363a547a5be30
+# 73d10dfbf9fe4ada98571d825e6a514f
+# df3ab8626fa64f6aac0e4c7b4baba5f6
+# 7d49d58694804462b40ebf7853c9f722
+# b343232e12944a0fa7e090d98eb63cdd
+# 01f2e1ef8d4a4fdd977b417d2e5a263f
+# 93c2804d558a4e9d838e266756a2a563
+# d561a8755b42408f897f89f7078867ec
+# c51038c5a8a44985867d6ba9c27b9d9d
+# fbee3b23e526460b81062dca124f6118
+# 0e98fee7920f4d06bebf81cf58e4cc47
+msgid "All the VPCs that you have created for the account is listed in the page."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:110
+#: ../../networking/virtual_private_cloud_config.rst:340
+#: ../../networking/virtual_private_cloud_config.rst:389
+# 9be1f95a9d58404cbd6e4417d049f493
+# 101241fe7ad147dd849d0b52d7648247
+# 1448cfd34b3f43a480717b41c5eebb77
+msgid "Click the Configure button of the VPC."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:112
+#: ../../networking/remote_access_vpn.rst:446
+#: ../../networking/remote_access_vpn.rst:509
+#: ../../networking/remote_access_vpn.rst:641
+#: ../../networking/virtual_private_cloud_config.rst:342
+#: ../../networking/virtual_private_cloud_config.rst:1029
+#: ../../networking/virtual_private_cloud_config.rst:1297
+# c95b38d3084f49a79782733848b3ecca
+# ab89f03b01054efcbdc4b304e895e95b
+# e9dc8a6495354766a07447565741a528
+# 985ac077ba8248a7a48dfa8c5c506d16
+# 9bc1baaed7ec4515ad2c3b5c6ce0451e
+# 801d602110c041cabcf0cc684584957a
+# be7596ebba2542159b95b5abc0607142
+msgid "For each tier, the following options are displayed:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:114
+#: ../../networking/remote_access_vpn.rst:448
+#: ../../networking/remote_access_vpn.rst:511
+#: ../../networking/remote_access_vpn.rst:643
+#: ../../networking/virtual_private_cloud_config.rst:344
+#: ../../networking/virtual_private_cloud_config.rst:511
+#: ../../networking/virtual_private_cloud_config.rst:746
+#: ../../networking/virtual_private_cloud_config.rst:804
+#: ../../networking/virtual_private_cloud_config.rst:865
+#: ../../networking/virtual_private_cloud_config.rst:1031
+#: ../../networking/virtual_private_cloud_config.rst:1299
+# 0d83a023e9014f9aade55353c79e3170
+# 401ffa05eaf246a28e37840ebe9292cc
+# 067e314f365a480ca4a21f8e163015f1
+# f9a89e98ace24da0b17c3378764628ec
+# df1588b26c554c8ebb2120108c70f35d
+# 14d477e028374bc7ba1a23e02c9a1b4c
+# 3961aede6bf54c31b9c546f46b4e6aa5
+# 8f1f5dfc2d674fc194d70276d8d18468
+# 0a8f19a5e8734bcab55acd9fca629358
+# 445b7ca76fea45e8a3439159d1faa90e
+# 1487ab642c08402ca5ba42c3837ea69a
+msgid "Internal LB"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:116
+#: ../../networking/remote_access_vpn.rst:450
+#: ../../networking/remote_access_vpn.rst:513
+#: ../../networking/remote_access_vpn.rst:645
+#: ../../networking/virtual_private_cloud_config.rst:346
+#: ../../networking/virtual_private_cloud_config.rst:513
+#: ../../networking/virtual_private_cloud_config.rst:748
+#: ../../networking/virtual_private_cloud_config.rst:806
+#: ../../networking/virtual_private_cloud_config.rst:867
+#: ../../networking/virtual_private_cloud_config.rst:1033
+#: ../../networking/virtual_private_cloud_config.rst:1301
+# 31d49abe67634960a557928d198a117b
+# d9f6c55773f44decab0c8f7c54706ab1
+# 77bc18fed48f46e4ac2df77187e262df
+# 2261a78bcdfd4e6da5136e979c35bb88
+# cbbd2dca656549c884e00639b9ae2035
+# e61e6beeae9c412bbe90181105cf2ae1
+# 909e61b8202a4b838f82ea576f748d63
+# 44b5133723344f3bbd1c7783e59642ed
+# b4286c8c1b954ab2bf7fe43800649c15
+# 0c9f5baff8f847a8871c2dc07441e145
+# 39db39923d924abba04f7eb190b0c065
+msgid "Public LB IP"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:120
+#: ../../networking/remote_access_vpn.rst:454
+#: ../../networking/remote_access_vpn.rst:517
+#: ../../networking/remote_access_vpn.rst:649
+#: ../../networking/virtual_private_cloud_config.rst:350
+#: ../../networking/virtual_private_cloud_config.rst:517
+#: ../../networking/virtual_private_cloud_config.rst:752
+#: ../../networking/virtual_private_cloud_config.rst:810
+#: ../../networking/virtual_private_cloud_config.rst:871
+#: ../../networking/virtual_private_cloud_config.rst:1037
+#: ../../networking/virtual_private_cloud_config.rst:1305
+# 5eaac9ad38594847b17964661cf9236c
+# 92df7a88e8e04a3483d10de7d9e73800
+# 5a76cc0a9455476cbc8b2c81878d7f05
+# 89f6fcd63e4f4cd1a5c2ae9d98d431d3
+# 3848ce6d7b224573a45a3daa5e369d11
+# ef82afc618e2465d879fb6566335f979
+# 4270f6ecdc324f22951c5acb77c4ee23
+# 39a7d2038d76415498e328d304159562
+# 593c2b74c4fc46a68613d48864ea1ea1
+# 442f49fa53564d63ac1c056170b5b4a8
+# 1679c7f2f3d74f87941189cd7a8eadf1
+msgid "Virtual Machines"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:124
+#: ../../networking/remote_access_vpn.rst:458
+#: ../../networking/remote_access_vpn.rst:521
+#: ../../networking/remote_access_vpn.rst:653
+#: ../../networking/virtual_private_cloud_config.rst:354
+#: ../../networking/virtual_private_cloud_config.rst:521
+#: ../../networking/virtual_private_cloud_config.rst:756
+#: ../../networking/virtual_private_cloud_config.rst:814
+#: ../../networking/virtual_private_cloud_config.rst:875
+#: ../../networking/virtual_private_cloud_config.rst:1041
+#: ../../networking/virtual_private_cloud_config.rst:1309
+# f5bae5ffb2f542f1a50da6263d5830fc
+# 1353046d5778408f926e87efdf7cfff4
+# 86105ce7fed24f5cb1731b0445e71c58
+# d0a50513766f4193a8ae3ce206f4f27f
+# 9494e63e7f1345eab39614b094d5418c
+# e840260e3fbe4d8e9ee76819e55c2271
+# 6e3d9062bdbb4bba84da4f570fd7c7fb
+# b76b5756109d44ddb7bcf3eee9b52377
+# ad03548aa7c148f1b0bb6d6489c1b169
+# 2eeb832b8f2744ff994afa7f34a8d110
+# fef8407d652246f9b64d3af9fab77e4c
+msgid "The following router information is displayed:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:126
+#: ../../networking/remote_access_vpn.rst:460
+#: ../../networking/remote_access_vpn.rst:523
+#: ../../networking/remote_access_vpn.rst:655
+#: ../../networking/virtual_private_cloud_config.rst:356
+#: ../../networking/virtual_private_cloud_config.rst:523
+#: ../../networking/virtual_private_cloud_config.rst:758
+#: ../../networking/virtual_private_cloud_config.rst:816
+#: ../../networking/virtual_private_cloud_config.rst:877
+#: ../../networking/virtual_private_cloud_config.rst:1043
+#: ../../networking/virtual_private_cloud_config.rst:1311
+# daf0d5dc2d9040e19b1366f58af4b3c6
+# a4596fec8cdb45bba1c99bc713b0d10c
+# 8da0cfd9fed2460cb97816a778997f9d
+# 056a09262bfc4d6482a20801b8acaaf5
+# 777bc6a7065949dbb37c74c841759e3c
+# b2c193538ac94be38e2a27ee2bf943d0
+# 0f492f18d1ae4cee885b69b82980784f
+# 5afe0c98d94b4a129c170577873b4208
+# d371bf7bd366484abd327ba22b4906d8
+# 7cf1fde7dabe40ecb52db6750a1508f7
+# 0369ed96499e48b3a23519de10fa02a8
+msgid "Private Gateways"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:128
+#: ../../networking/remote_access_vpn.rst:462
+#: ../../networking/remote_access_vpn.rst:525
+#: ../../networking/remote_access_vpn.rst:657
+#: ../../networking/virtual_private_cloud_config.rst:358
+#: ../../networking/virtual_private_cloud_config.rst:525
+#: ../../networking/virtual_private_cloud_config.rst:760
+#: ../../networking/virtual_private_cloud_config.rst:818
+#: ../../networking/virtual_private_cloud_config.rst:879
+#: ../../networking/virtual_private_cloud_config.rst:1045
+#: ../../networking/virtual_private_cloud_config.rst:1313
+# 5f0457bd87ee495a8d5bfe9c4e4140b9
+# be6d3ce6cbaf4b5784187f736898bbb4
+# 137340b6a07047f5b4105b550bd2dea5
+# 16a448bd22a34fd59b341f0be0cfad13
+# 98dd6a7c42284bd7ab5a086176692d74
+# 77e662d10339479c93999acb83f50aab
+# f87b9d1bf7c8489d824e4bc2c1edb94a
+# 4627c69d41294c8fab4d9898db33c83f
+# 0c430ab6225a479a8e58afe0436292db
+# f224a8b6cbea436aaea2ce0b6c58b5a5
+# 50ff9ec30a43472aaaea14d658f3ede1
+msgid "Public IP Addresses"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:130
+#: ../../networking/remote_access_vpn.rst:464
+#: ../../networking/remote_access_vpn.rst:527
+#: ../../networking/remote_access_vpn.rst:659
+#: ../../networking/virtual_private_cloud_config.rst:360
+#: ../../networking/virtual_private_cloud_config.rst:527
+#: ../../networking/virtual_private_cloud_config.rst:762
+#: ../../networking/virtual_private_cloud_config.rst:820
+#: ../../networking/virtual_private_cloud_config.rst:881
+#: ../../networking/virtual_private_cloud_config.rst:1047
+#: ../../networking/virtual_private_cloud_config.rst:1315
+# 2a01498545a9403e8315ab2b9dc8d3ff
+# 5c6c556abdb042cd95b91af10067d5b6
+# 863fdc1a436149ec81d2a240d4d22a2f
+# 79192eb67b614bd58e10729375bddf8c
+# d36fe14908f246bf83e43933e55ef3b4
+# 65e2c761e70f4440ad714dd09cd91349
+# 5aeddf583b6743bb889616c075b0793a
+# 147238d0cb65480c9d78837c05e43bd9
+# 1b2e46ec5bea49d09a0c7c272595d111
+# 26fcc9420a3f49edb4de8b1efbb457bc
+# 63efa7ad47a34105874929f9bbd9427f
+msgid "Site-to-Site VPNs"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:132
+#: ../../networking/remote_access_vpn.rst:466
+#: ../../networking/remote_access_vpn.rst:529
+#: ../../networking/remote_access_vpn.rst:661
+#: ../../networking/virtual_private_cloud_config.rst:362
+#: ../../networking/virtual_private_cloud_config.rst:529
+#: ../../networking/virtual_private_cloud_config.rst:764
+#: ../../networking/virtual_private_cloud_config.rst:822
+#: ../../networking/virtual_private_cloud_config.rst:883
+#: ../../networking/virtual_private_cloud_config.rst:1049
+#: ../../networking/virtual_private_cloud_config.rst:1317
+# b27df81c137d4ada8a78b99a42ce9318
+# ce6512f959b543ed84a43badeb5efb3c
+# b81bad1751644d18810aa0953be2bea5
+# 9f3e88679a5d4387855b32022dbff52c
+# 0e0ee230ef824ba0a10c19e3b311b598
+# 78ef6f691db5444eb53d8f8e2876e4e9
+# 3a98e8ef4c754c41ab1345025b5cc625
+# 0e6c5b8161104349a11cb3207b8b813a
+# 383a9b461f6b4113acb24f60ec71b1fc
+# cc1ad8b9d34945a9baa02216efbc2555
+# 299782736e884755a67a9ff9eae837dd
+msgid "Network ACL Lists"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:134
+#: ../../networking/virtual_private_cloud_config.rst:885
+#: ../../networking/virtual_private_cloud_config.rst:1051
+#: ../../networking/virtual_private_cloud_config.rst:1319
+# c6c2c79f850f4077829c5505885e62f5
+# 1062ef9c7f464e158c482bea53e6ea61
+# e6718162b3284e44a60f542408ae32fc
+# 6a480049441d4ccc8a31e3f11799dd7b
+msgid "In the Router node, select Public IP Addresses."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:136
+#: ../../networking/virtual_private_cloud_config.rst:826
+#: ../../networking/virtual_private_cloud_config.rst:887
+#: ../../networking/virtual_private_cloud_config.rst:1053
+#: ../../networking/virtual_private_cloud_config.rst:1321
+# 7d553b7fbdc6413d8c633ce8dfb4868c
+# 2b2b55ab8a624bb78e95913869ab2a05
+# 0de20186cc34473cb61133c9b865f960
+# 3e9dafbca1bc4a50b60617d6c81f170f
+# 9abe20eba64240cd90a18743af0e00c2
+msgid "The IP Addresses page is displayed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:138
+# f1ce2b4d26b145d49d98a4cecca586e8
+msgid "Click Source NAT IP address."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:142
+# e83452437c9449d7b1f7508735d5e35a
+msgid "Click OK to confirm. The IPsec key is displayed in a pop-up window."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:144
+# d9c262cf3fdb476ea6a3500b5c9e3102
+msgid "Now, you need to add the VPN users."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:146
+# 93e980a2795646be9a5fbc975be42289
+msgid "Click the Source NAT IP."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:148
+# 15e0e443545942579a324fda601e2686
+msgid "Select the VPN tab."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:150
+# 400f2955d75b4fe29ece4d0b82cdadf3
+msgid "Add the username and the corresponding password of the user you wanted to add."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:155
+# 13bbf1c44ce8451e9fda9df0a55488d9
+msgid "Repeat the same steps to add the VPN users."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:159
+# f882d1b965574377abb5c47c46d2017d
+msgid "Using Remote Access VPN with Windows"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:161
+# 7dac5068f0b244e1a144a09d45c39932
+msgid "The procedure to use VPN varies by Windows version. Generally, the user must edit the VPN properties and make sure that the default route is not the VPN. The following steps are for Windows L2TP clients on Windows Vista. The commands should be similar for other Windows versions."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:166
+# 9863de47db9f4572ad58ea772de9f36d
+msgid "Log in to the CloudStack UI and click on the source NAT IP for the account. The VPN tab should display the IPsec preshared key. Make a note of this and the source NAT IP. The UI also lists one or more users and their passwords. Choose one of these users, or, if none exists, add a user and password."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:172
+# 7fda5d36b51847d49837befe10623588
+msgid "On the Windows box, go to Control Panel, then select Network and Sharing center. Click Setup a connection or network."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:175
+# da78d151c9234aed8997f0bc85337cf6
+msgid "In the next dialog, select No, create a new connection."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:177
+# 43e868088a2941f2b050d28f6420c815
+msgid "In the next dialog, select Use my Internet Connection (VPN)."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:179
+# 239288f41e5547d280e2293ec8da8206
+msgid "In the next dialog, enter the source NAT IP from step #1 and give the connection a name. Check Don't connect now."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:183
+# 38f025d6b59c4032a92973f1c1a27c07
+msgid "In the next dialog, enter the user name and password selected in step #1."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:188
+# 65891d17f3074ed9b484f59841022124
+msgid "Go back to the Control Panel and click Network Connections to see the new connection. The connection is not active yet."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:191
+# 90aee2a731374796ae19cb91e6c4eaca
+msgid "Right-click the new connection and select Properties. In the Properties dialog, select the Networking tab."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:196
+# 785904429cc24b31a7cf663347b72344
+msgid "In Type of VPN, choose L2TP IPsec VPN, then click IPsec settings. Select Use preshared key. Enter the preshared key from step #1."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:199
+# 3e29d7f5cd6b43428b98157632b35cfe
+msgid "The connection is ready for activation. Go back to Control Panel -> Network Connections and double-click the created connection."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:202
+# 658b86e57b2145119bff660e836d339d
+msgid "Enter the user name and password from step #1."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:206
+# f28b68b93a984f618a8681036210e3b9
+msgid "Using Remote Access VPN with Mac OS X"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:208
+# 8b76f5b992cc490bad145d28495ce704
+msgid "First, be sure you've configured the VPN settings in your CloudStack install. This section is only concerned with connecting via Mac OS X to your VPN."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:212
+# 7da87b538a3b4bd98149a9dc28b99cb5
+msgid "Note, these instructions were written on Mac OS X 10.7.5. They may differ slightly in older or newer releases of Mac OS X."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:215
+# 99afa11cb02448889b90260c46e6daf2
+msgid "On your Mac, open System Preferences and click Network."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:217
+# 1b60714f0b664945b51a0b61be0399a5
+msgid "Make sure Send all traffic over VPN connection is not checked."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:219
+# bcd319828ca0418fb3c241dfe5096e41
+msgid "If your preferences are locked, you'll need to click the lock in the bottom left-hand corner to make any changes and provide your administrator credentials."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:223
+# 4300ee6f178548d5a9905a6bbe2d9860
+msgid "You will need to create a new network entry. Click the plus icon on the bottom left-hand side and you'll see a dialog that says \"Select the interface and enter a name for the new service.\" Select VPN from the Interface drop-down menu, and \"L2TP over IPSec\" for the VPN Type. Enter whatever you like within the \"Service Name\" field."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:229
+# 23650c313b074382a57881042b50304e
+msgid "You'll now have a new network interface with the name of whatever you put in the \"Service Name\" field. For the purposes of this example, we'll assume you've named it \"CloudStack.\" Click on that interface and provide the IP address of the interface for your VPN under the Server Address field, and the user name for your VPN under Account Name."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:236
+# 6b61feadee8d476583c5ac8024ecf9dc
+msgid "Click Authentication Settings, and add the user's password under User Authentication and enter the pre-shared IPSec key in the Shared Secret field under Machine Authentication. Click OK."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:240
+# 82160d6db5874a5fb691804a0f4064ee
+msgid "You may also want to click the \"Show VPN status in menu bar\" but that's entirely optional."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:243
+# 7888991db08f4692af070e20a8f548e4
+msgid "Now click \"Connect\" and you will be connected to the CloudStack VPN."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:249
+# b8fcb8654d4045cabab65cc607473fa0
+msgid "Setting Up a Site-to-Site VPN Connection"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:251
+# bf33833486e34298bbd54de0d5e5c883
+msgid "A Site-to-Site VPN connection helps you establish a secure connection from an enterprise datacenter to the cloud infrastructure. This allows users to access the guest VMs by establishing a VPN connection to the virtual router of the account from a device in the datacenter of the enterprise. You can also establish a secure connection between two VPC setups or high availability zones in your environment. Having this facility eliminates the need to establish VPN connections to individual VMs."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:260
+# 4bf27ce4183e47dda88b6603d61b46b8
+msgid "The difference from Remote VPN is that Site-to-site VPNs connects entire networks to each other, for example, connecting a branch office network to a company headquarters network. In a site-to-site VPN, hosts do not have VPN client software; they send and receive normal TCP/IP traffic through a VPN gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:266
+# 153b937b1c0e4de69b3b94451840a13f
+msgid "The supported endpoints on the remote datacenters are:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:268
+# 5ebb68947e8846959fdb844894eba6eb
+msgid "Cisco ISR with IOS 12.4 or later"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:270
+# e3a55a3999da49baa81621a7f7ffb70a
+msgid "Juniper J-Series routers with JunOS 9.5 or later"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:272
+# ffc402a2243c4da9bcd196372f78bf94
+msgid "CloudStack virtual routers"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:275
+# af60329a6d1b421db96e66d969e7148a
+msgid "In addition to the specific Cisco and Juniper devices listed above, the expectation is that any Cisco or Juniper device running on the supported operating systems are able to establish VPN connections."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:279
+# 4e099c5b2d15403d841fca6ab971b147
+msgid "To set up a Site-to-Site VPN connection, perform the following:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:281
+# 9f0c55b7e3d1405ea91d412d82570573
+msgid "Create a Virtual Private Cloud (VPC)."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:283
+# 1cc41acb25564437bf47069632c1e47f
+msgid "See \":ref:`configuring-vpc`\"."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:285
+# 0350dab55c154adb8bfb5fc2329bc99b
+msgid "Create a VPN Customer Gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:287
+# 9e0ade3afda44783837277f292aac18e
+msgid "Create a VPN gateway for the VPC that you created."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:289
+# bd574fc0e611460eb6f1cf836570d65a
+msgid "Create VPN connection from the VPC VPN gateway to the customer VPN gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:294
+# 94a11afb4f284c39876ab9e7ad9b4203
+msgid "Creating and Updating a VPN Customer Gateway"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:297
+# d7741a7964f14270836f90faa50dee5e
+msgid "A VPN customer gateway can be connected to only one VPN gateway at a time."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:299
+# b0237b80ce7945038ccf7e43814bc271
+msgid "To add a VPN Customer Gateway:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:305
+#: ../../networking/remote_access_vpn.rst:415
+# 101bb0d15ff04d2b833841a38622b5a3
+# 2b4e8de7b2b8461685571e9bd8677151
+msgid "In the Select view, select VPN Customer Gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:307
+# 7731e51aab804267b5d9a1b77c2a563f
+msgid "Click Add VPN Customer Gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:309
+# a28ae413767b455ba902116cbfb65b62
+msgid "|addvpncustomergateway.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:313
+# 4b1ee71a183a40f08f2c0f6153980745
+msgid "**Name**: A unique name for the VPN customer gateway you create."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:315
+# 4a55d6fffb10456eb7eedd3b877f3290
+msgid "**Gateway**: The IP address for the remote gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:317
+# a1719efbdbf3445e88fe8b57058e647d
+msgid "**CIDR list**: The guest CIDR list of the remote subnets. Enter a CIDR or a comma-separated list of CIDRs. Ensure that a guest CIDR list is not overlapped with the VPC's CIDR, or another guest CIDR. The CIDR must be RFC1918-compliant."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:322
+# 45e753e1aca84d72a27705c47e7359fe
+msgid "**IPsec Preshared Key**: Preshared keying is a method where the endpoints of the VPN share a secret key. This key value is used to authenticate the customer gateway and the VPC VPN gateway to each other."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:328
+# 685253a274ff4f8ab93ec131da0a8e17
+msgid "The IKE peers (VPN end points) authenticate each other by computing and sending a keyed hash of data that includes the Preshared key. If the receiving peer is able to create the same hash independently by using its Preshared key, it knows that both peers must share the same secret, thus authenticating the customer gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:335
+# 99c6b3d0d9b644ac963db1bbbec803aa
+msgid "**IKE Encryption**: The Internet Key Exchange (IKE) policy for phase-1. The supported encryption algorithms are AES128, AES192, AES256, and 3DES. Authentication is accomplished through the Preshared Keys."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:341
+# 5fc1a26b6376451e99e9e5edb6e43b8c
+msgid "The phase-1 is the first phase in the IKE process. In this initial negotiation phase, the two VPN endpoints agree on the methods to be used to provide security for the underlying IP traffic. The phase-1 authenticates the two VPN gateways to each other, by confirming that the remote gateway has a matching Preshared Key."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:347
+# 4a50daea38b94c4c8f566640f9423d59
+msgid "**IKE Hash**: The IKE hash for phase-1. The supported hash algorithms are SHA1 and MD5."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:350
+# 164ad3cc6c1d4be09637856b2caebc73
+msgid "**IKE DH**: A public-key cryptography protocol which allows two parties to establish a shared secret over an insecure communications channel. The 1536-bit Diffie-Hellman group is used within IKE to establish session keys. The supported options are None, Group-5 (1536-bit) and Group-2 (1024-bit)."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:356
+# 7f48a32285424744aed43ca25afe1013
+msgid "**ESP Encryption**: Encapsulating Security Payload (ESP) algorithm within phase-2. The supported encryption algorithms are AES128, AES192, AES256, and 3DES."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:361
+# b406299f4fea47069d76bb649b8708f9
+msgid "The phase-2 is the second phase in the IKE process. The purpose of IKE phase-2 is to negotiate IPSec security associations (SA) to set up the IPSec tunnel. In phase-2, new keying material is extracted from the Diffie-Hellman key exchange in phase-1, to provide session keys to use in protecting the VPN data flow."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:367
+# a27571240d7c4f3c9acf4a0a4aa3b628
+msgid "**ESP Hash**: Encapsulating Security Payload (ESP) hash for phase-2. Supported hash algorithms are SHA1 and MD5."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:370
+# 4b7ceba042f249029e0dbf978aa690d3
+msgid "**Perfect Forward Secrecy**: Perfect Forward Secrecy (or PFS) is the property that ensures that a session key derived from a set of long-term public and private keys will not be compromised. This property enforces a new Diffie-Hellman key exchange. It provides the keying material that has greater key material life and thereby greater resistance to cryptographic attacks. The available options are None, Group-5 (1536-bit) and Group-2 (1024-bit). The security of the key exchanges increase as the DH groups grow larger, as does the time of the exchanges."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:381
+# 31cd21a987c94c2593fa18b480d5655a
+msgid "When PFS is turned on, for every negotiation of a new phase-2 SA the two gateways must generate a new set of phase-1 keys. This adds an extra layer of protection that PFS adds, which ensures if the phase-2 SA's have expired, the keys used for new phase-2 SA's have not been generated from the current phase-1 keying material."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:387
+# c4fac70acb7546528e8f03a69aec87d6
+msgid "**IKE Lifetime (seconds)**: The phase-1 lifetime of the security association in seconds. Default is 86400 seconds (1 day). Whenever the time expires, a new phase-1 exchange is performed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:391
+# 253e1c3775154909922b7f978944cd3e
+msgid "**ESP Lifetime (seconds)**: The phase-2 lifetime of the security association in seconds. Default is 3600 seconds (1 hour). Whenever the value is exceeded, a re-key is initiated to provide a new IPsec encryption and authentication session keys."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:396
+# c0c484db7f344e408d168f25bb654809
+msgid "**Dead Peer Detection**: A method to detect an unavailable Internet Key Exchange (IKE) peer. Select this option if you want the virtual router to query the liveliness of its IKE peer at regular intervals. It's recommended to have the same configuration of DPD on both side of VPN connection."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:406
+# bbbaed88ff1d435c8172e82d1ba38621
+msgid "Updating and Removing a VPN Customer Gateway"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:408
+# dce2c8dc1af941d3995eccd689185d2f
+msgid "You can update a customer gateway either with no VPN connection, or related VPN connection is in error state."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:417
+# a2663d4c4c664967b66aed432bc15feb
+msgid "Select the VPN customer gateway you want to work with."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:419
+# a7ded8e5a4764341a0616505650a00e8
+msgid "To modify the required parameters, click the Edit VPN Customer Gateway button |vpn-edit-icon.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:422
+# 756841a8fa024fd8a5c97c8f30e876d3
+msgid "To remove the VPN customer gateway, click the Delete VPN Customer Gateway button |delete.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:429
+# b8b2a50b82054314966bddcea5e58624
+msgid "Creating a VPN gateway for the VPC"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:440
+#: ../../networking/remote_access_vpn.rst:501
+#: ../../networking/remote_access_vpn.rst:633
+#: ../../networking/virtual_private_cloud_config.rst:671
+#: ../../networking/virtual_private_cloud_config.rst:738
+#: ../../networking/virtual_private_cloud_config.rst:857
+#: ../../networking/virtual_private_cloud_config.rst:1291
+# 55ffd9d38baf4689915216b245eb0345
+# 9dffc7abb0334653a04e9da28c3986eb
+# cafe1c918b254231856621d595a969ea
+# 629408b6b4d44c488f179e9d12c9d1c8
+# 12f2c2ca637145198bd85e6aefc78803
+# 322ff7890b6647d89fc773f95de5ca97
+# b5eb13586b2d401b9224cc304d4d596e
+msgid "Click the Configure button of the VPC to which you want to deploy the VMs."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:443
+#: ../../networking/remote_access_vpn.rst:504
+#: ../../networking/remote_access_vpn.rst:636
+#: ../../networking/virtual_private_cloud_config.rst:504
+#: ../../networking/virtual_private_cloud_config.rst:741
+#: ../../networking/virtual_private_cloud_config.rst:799
+#: ../../networking/virtual_private_cloud_config.rst:860
+#: ../../networking/virtual_private_cloud_config.rst:1294
+# 3ede94e26b2243618297004100dde13e
+# 2f52e248552b455a87f010302f709dad
+# 053eb6822dcf4582b9bba73ede381afb
+# d368f1f8019d471eb6596301beba362c
+# dfea3c0fff89489eac70a967cc49c5aa
+# 73059e34302c43d1a5a4c816f43b9382
+# fb07c649ea2b4a768d6e5716e8030063
+# 28f7d7ee821449b29c5cd912fde10a27
+msgid "The VPC page is displayed where all the tiers you created are listed in a diagram."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:468
+#: ../../networking/remote_access_vpn.rst:531
+#: ../../networking/remote_access_vpn.rst:663
+# bb47b6a4c9894b0ba98c007547e23a7b
+# 5f44ee9703334af187a5f781a5bdd3ca
+# 90eeedf47dda43f69ca4cd79e42918d7
+msgid "Select Site-to-Site VPN."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:470
+# 3904e2f97d404bd0ac8c9e9461127c9c
+msgid "If you are creating the VPN gateway for the first time, selecting Site-to-Site VPN prompts you to create a VPN gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:473
+# 58e6c2a9a3ca472c8470f2da068490b4
+msgid "In the confirmation dialog, click Yes to confirm."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:475
+# 0dcce7d9ba7e44fea93fd343b6eb8ccd
+msgid "Within a few moments, the VPN gateway is created. You will be prompted to view the details of the VPN gateway you have created. Click Yes to confirm."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:479
+# 08c91c396238462eb6a6a86c3bc34356
+msgid "The following details are displayed in the VPN Gateway page:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:483
+# a77fc54a7c8146a3ac276762ce040121
+msgid "Account"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:485
+# 7d5a08b580ca444fa94ea41cf933bbed
+msgid "Domain"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:489
+# a9bedddab6d94613aa7949d22530c563
+msgid "Creating a VPN Connection"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:491
+# eb9ff504d03f4098abe385052da3a163
+msgid "CloudStack supports creating up to 8 VPN connections."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:499
+# 4106c6c68d6d468fa69e8066df52a37d
+msgid "All the VPCs that you create for the account are listed in the page."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:507
+#: ../../networking/remote_access_vpn.rst:639
+#: ../../networking/virtual_private_cloud_config.rst:507
+# 30ef75902e6a416e943de29ba0ae78f2
+# 2ea0f0278379492ba4ae3fe6df1acc1e
+# 9120ca60dcc143a28655716ade74dd8d
+msgid "Click the Settings icon."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:533
+#: ../../networking/remote_access_vpn.rst:665
+# c17fddae85054e48acc62417d618005b
+# d51c787e2c3641bda74032c8dda674a2
+msgid "The Site-to-Site VPN page is displayed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:535
+#: ../../networking/remote_access_vpn.rst:667
+# d20933656e614d3c90bbeca3c9dfa1e8
+# ae7c48ded27f46fba258b7713abe8020
+msgid "From the Select View drop-down, ensure that VPN Connection is selected."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:538
+# e805d37fb5de4010a4e653ecc10fe88f
+msgid "Click Create VPN Connection."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:540
+# 6461a9409d0d43af95085f7592764ec5
+msgid "The Create VPN Connection dialog is displayed:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:542
+# 302fc42f8855480ea855ba83253ae510
+msgid "|createvpnconnection.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:544
+# 256fd2eeb83d4c8ca42223952cda2eaa
+msgid "Select the desired customer gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:546
+# 1216cafe939448ce89002732610150f9
+msgid "Select Passive if you want to establish a connection between two VPC virtual routers."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:549
+# 31801a53933d4e8e98ac8b775c9547ad
+msgid "If you want to establish a connection between two VPC virtual routers, select Passive only on one of the VPC virtual routers, which waits for the other VPC virtual router to initiate the connection. Do not select Passive on the VPC virtual router that initiates the connection."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:557
+# 06301a1ae56d4aa0829075cea0e779b2
+msgid "Within a few moments, the VPN Connection is displayed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:559
+# aa7133cb7a2f415180d09d0a134d39b2
+msgid "The following information on the VPN connection is displayed:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:565
+# 0c0a058f5bba400ba3f349f62ea660f1
+msgid "State"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:567
+# c7cdf1f2c13b4df7852fb798ffb852f1
+msgid "IPSec Preshared Key"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:569
+# 97c84bf1a75c4e84a20bda2e28f8dd99
+msgid "IKE Policy"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:571
+# 7d9d2e44ca2e45118dd87874aab3660c
+msgid "ESP Policy"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:575
+# 53ad2d1f828e40a5a6e793ae3c464cf6
+msgid "Site-to-Site VPN Connection Between VPC Networks"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:577
+# bfe3ddb6f0054692ade09235d6409226
+msgid "CloudStack provides you with the ability to establish a site-to-site VPN connection between CloudStack virtual routers. To achieve that, add a passive mode Site-to-Site VPN. With this functionality, users can deploy applications in multiple Availability Zones or VPCs, which can communicate with each other by using a secure Site-to-Site VPN Tunnel."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:583
+# 4d7b48c89729493fab30a6c8fa3e3d8a
+msgid "This feature is supported on all the hypervisors."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:585
+# 63d33594095642d6bd759d685c327728
+msgid "Create two VPCs. For example, VPC A and VPC B."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:587
+# f38ada5b2bf347699a13c440cdbb6d6d
+msgid "For more information, see \":ref:`configuring-vpc`\"."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:589
+# 9725f2c0a7804cd08dabeb07ccced69e
+msgid "Create VPN gateways on both the VPCs you created."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:591
+# 863b39380dc440b39636aefc3f305286
+msgid "For more information, see `\"Creating a VPN gateway for the VPC\" <#creating-a-vpn-gateway-for-the-vpc>`_."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:594
+# 80e6cc23902e4983926d330301305245
+msgid "Create VPN customer gateway for both the VPCs."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:596
+# 8b053f18f0cf45d7a54c9a55525e51d5
+msgid "For more information, see `\"Creating and Updating a VPN Customer Gateway\" <#creating-and-updating-a-vpn-customer-gateway>`_."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:599
+# e62bfd0cb16b4506af656ac300d2b9d6
+msgid "Enable a VPN connection on VPC A in passive mode."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:601
+# e9a973fc175a4c358a0961c603185a9b
+msgid "For more information, see `\"Creating a VPN Connection\" <#creating-a-vpn-connection>`_."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:604
+# 077205cc874949ebb23a94463f757867
+msgid "Ensure that the customer gateway is pointed to VPC B. The VPN connection is shown in the Disconnected state."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:607
+# a1f2ec5982ca4ee88e0e1b6d64a341e4
+msgid "Enable a VPN connection on VPC B."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:609
+# 9b111a2dd2fb47d384d121a954fb00d0
+msgid "Ensure that the customer gateway is pointed to VPC A. Because virtual router of VPC A, in this case, is in passive mode and is waiting for the virtual router of VPC B to initiate the connection, VPC B virtual router should not be in passive mode."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:614
+# 6f48c7f01a334934959f0048f9a19913
+msgid "The VPN connection is shown in the Disconnected state."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:616
+# f9289b1f358541dcbbea60dd60547408
+msgid "Creating VPN connection on both the VPCs initiates a VPN connection. Wait for few seconds. The default is 30 seconds for both the VPN connections to show the Connected state."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:622
+# 9fe12894f28c427a9daba08709f4326d
+msgid "Restarting and Removing a VPN Connection"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:670
+# 4f1aa09db210412ca829b0fadcbc3175
+msgid "All the VPN connections you created are displayed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:672
+# 17e6855dfa4241a58cce788d5d96a057
+msgid "Select the VPN connection you want to work with."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:674
+# bc52370e920b4f288050d7fcf2c623f4
+msgid "The Details tab is displayed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:676
+# dd3715695c204665987222ab000106cd
+msgid "To remove a VPN connection, click the Delete VPN connection button |remove-vpn.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:679
+# 4b987b9761934af19b5d8a4be76875a5
+msgid "To restart a VPN connection, click the Reset VPN connection button present in the Details tab. |reset-vpn.png|"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:18
+# 1280b685b60c4cd9b6c84035e7c3ff2a
+msgid "About Inter-VLAN Routing (nTier Apps)"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:20
+# be2045156b3041218bc42ecd27d7d6f0
+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 the VMs. In effect, you can segment VMs by means of VLANs into different networks that can host multi-tier applications, such as Web, Application, or Database. Such segmentation by means of VLANs logically separate application VMs for higher security and lower broadcasts, while remaining physically connected to the same device."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:33
+# ee648742bfb3421f8a3889c2349f279b
+msgid "This feature is supported on XenServer, KVM, and VMware hypervisors."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:35
+# ef162a16526641098e51a139989ae97e
+msgid "The major advantages are:"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:37
+# 3e6de8dbeba5419abdb2b03019116141
+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
+# bc8ba74b90594f12a5fd5677cc9ff6d1
+msgid "A VLAN allocated for an account cannot be shared between multiple accounts."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:45
+# 1ab1ca8e96254434870948d662709b43
+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
+# a3116bd8472e48a7aa7cda71b97e27cc
+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
+# 6fd43509fad74559adbc29b02d394dc9
+msgid "The administrator can create the following gateways to send to or receive traffic from the VMs:"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:56
+# 8ddc983de3d241f09f98b725eb5816b9
+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
+# 61e9f85faff44050a4964c4318e14c71
+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
+# b56703bb9e304d9eb985cf50d8467b88
+msgid "**Private Gateway**: For more information, see \":ref:`adding-priv-gw-vpc`\"."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:66
+# 971a020719584df99604941837f413e9
+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
+# a959d3a87f854875b155e4dd0378bc58
+msgid "For example:"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:72
+# c8562933cf3a49dabea40ebda77c173e
+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
+# 9a0414207cf1455fa28030b70576f628
+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
+# 8534c0f613cb4afd87cee4abbbeb1864
+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
+# dbc5184ebe294b3c978a2597145d1afc
+msgid "The following figure shows the possible deployment scenarios of a Inter-VLAN setup:"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:90
+# 7b6b27d712ab4049bb9e18da1df3f10f
+msgid "|mutltier.png|"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:92
+# a73c0ccfe9e242bbafc920ed4db89f8c
+msgid "To set up a multi-tier Inter-VLAN deployment, see \":ref:`configuring-vpc`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:20
+# 68230541a8c04698a2cd4782fa199025
+msgid "Configuring a Virtual Private Cloud"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:23
+# c96dce204b9449f096ddff43e7c501e4
+msgid "About Virtual Private Clouds"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:25
+# 39a15c9ebdbf402189072d4ad538b511
+msgid "CloudStack Virtual Private Cloud is a private, isolated part of CloudStack. A VPC can have its own virtual network topology that resembles a traditional physical network. You can launch VMs in the virtual network that can have private addresses in the range of your choice, for example: 10.0.0.0/16. You can define network tiers within your VPC network range, which in turn enables you to group similar kinds of instances based on IP address range."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:33
+# 52f1ec4df5f14d00acc410893a48cd12
+msgid "For example, if a VPC has the private range 10.0.0.0/16, its guest networks can have the network ranges 10.0.1.0/24, 10.0.2.0/24, 10.0.3.0/24, and so on."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:39
+# c427f4f401964436adf6600e085f1c73
+msgid "Major Components of a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:41
+# aa65d02ab49c4593ab9a6304e97b0499
+msgid "A VPC is comprised of the following network components:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:43
+# 6ce250346a5b4839af2f807498d27a93
+msgid "**VPC**: A VPC acts as a container for multiple isolated networks that can communicate with each other via its virtual router."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:46
+# bf8dcbee37f94f398e40dcc29aa1b1f2
+msgid "**Network Tiers**: Each tier acts as an isolated network with its own VLANs and CIDR list, where you can place groups of resources, such as VMs. The tiers are segmented by means of VLANs. The NIC of each tier acts as its gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:51
+# 85c01a3feddd4eefa12e8569dc29abdb
+msgid "**Virtual Router**: A virtual router is automatically created and started when you create a VPC. The virtual router connect the tiers and direct traffic among the public gateway, the VPN gateways, and the NAT instances. For each tier, a corresponding NIC and IP exist in the virtual router. The virtual router provides DNS and DHCP services through its IP."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:58
+# 084d9e9386154de29f7c85e78edcbddf
+msgid "**Public Gateway**: The traffic to and from the Internet routed to the VPC through the public gateway. In a VPC, the public gateway is not exposed to the end user; therefore, static routes are not support for the public gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:63
+# 0a67aeaa8469476786141e2d15792113
+msgid "**Private Gateway**: All the traffic to and from a private network routed to the VPC through the private gateway. For more information, see \":ref:`adding-priv-gw-vpc`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:67
+# 7f1df774c21345d183d04571db70c24d
+msgid "**VPN Gateway**: The VPC side of a VPN connection."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:69
+# d4f1eced716140b2ba2e5c4a4bb94733
+msgid "**Site-to-Site VPN Connection**: A hardware-based VPN connection between your VPC and your datacenter, home network, or co-location facility. For more information, see \":ref:`setting-s2s-vpn-conn`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:73
+# d96c6c8f7e914115913908328dafe225
+msgid "**Customer Gateway**: The customer side of a VPN Connection. For more information, see `\"Creating and Updating a VPN Customer Gateway\" <#creating-and-updating-a-vpn-customer-gateway>`_."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:77
+# 4a709f7fe7a644bcbf353a4841f01b9d
+msgid "**NAT Instance**: An instance that provides Port Address Translation for instances to access the Internet via the public gateway. For more information, see \":ref:`enabling-disabling-static-nat-on-vpc`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:81
+# d3585dd79a1e4e7e89912c04813bb102
+msgid "**Network ACL**: Network ACL is a group of Network ACL items. Network ACL items are nothing but numbered rules that are evaluated in order, starting with the lowest numbered rule. These rules determine whether traffic is allowed in or out of any tier associated with the network ACL. For more information, see \":ref:`conf-net-acl`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:89
+# d9a20cb6323241afa91a6c2cbc307ff9
+msgid "Network Architecture in a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:91
+# 7ee1153de76a4c929d0b1fa6a71fd31d
+msgid "In a VPC, the following four basic options of network architectures are present:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:94
+# 1451c0ec747146d4b4c7cef8cb2721de
+msgid "VPC with a public gateway only"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:96
+# 10f537ebc4544eb487ff69cb3d4925f7
+msgid "VPC with public and private gateways"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:98
+# 6df0df8e0b47452e978347b896d0550a
+msgid "VPC with public and private gateways and site-to-site VPN access"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:100
+# 7210a6e941a1458299c8b7853414ea18
+msgid "VPC with a private gateway only and site-to-site VPN access"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:104
+# 41f1471fc8d144d4a2ae08eaa26079e5
+msgid "Connectivity Options for a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:106
+# 7939a1a9ae10427e945a7598b60a6acb
+msgid "You can connect your VPC to:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:108
+# 92785d31fb8449578b7a7d78f8d59eb4
+msgid "The Internet through the public gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:110
+# 013122ffc01c46aabad011737399bc1b
+msgid "The corporate datacenter by using a site-to-site VPN connection through the VPN gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:113
+# 3199327142444fe1bd185a5b40149130
+msgid "Both the Internet and your corporate datacenter by using both the public gateway and a VPN gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:118
+# 2a91b9eca4284fbcb69ab5478b249d29
+msgid "VPC Network Considerations"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:120
+# 8e8bd043a0c34c77885f6c613181a421
+msgid "Consider the following before you create a VPC:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:122
+# f39001cdf8054dcfbd61db983190b41f
+msgid "A VPC, by default, is created in the enabled state."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:124
+# 82792dd3f27546d2a3c42b67ba5b29f4
+msgid "A VPC can be created in Advance zone only, and can't belong to more than one zone at a time."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:127
+# 8a09712594af4741822a39824fdef070
+msgid "The default number of VPCs an account can create is 20. However, you can change it by using the max.account.vpcs global parameter, which controls the maximum number of VPCs an account is allowed to create."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:131
+# 261cae4270494826bf83e0dcae8af848
+msgid "The default number of tiers an account can create within a VPC is 3. You can configure this number by using the vpc.max.networks parameter."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:135
+# 62fc1185526b4470b7cc2d5eebfcbdfd
+msgid "Each tier should have an unique CIDR in the VPC. Ensure that the tier's CIDR should be within the VPC CIDR range."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:138
+# 96300f5d5fe44005a32e9cf1f40b4ea4
+msgid "A tier belongs to only one VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:140
+# 3fa6bb2bbfc54d1da2bab5ebfe5b22b2
+msgid "All network tiers inside the VPC should belong to the same account."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:142
+# abd18af86f4e44958067a2f7dc82012f
+msgid "When a VPC is created, by default, a SourceNAT IP is allocated to it. The Source NAT IP is released only when the VPC is removed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:145
+# 14ebd559d22240e29e435b14253ef654
+msgid "A public IP can be used for only one purpose at a time. If the IP is a sourceNAT, it cannot be used for StaticNAT or port forwarding."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:148
+# c29d747872084beb8924548c54211fae
+msgid "The instances can only have a private IP address that you provision. To communicate with the Internet, enable NAT to an instance that you launch in your VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:152
+# 8d3468d50b334a3389cb81da8b464dea
+msgid "Only new networks can be added to a VPC. The maximum number of networks per VPC is limited by the value you specify in the vpc.max.networks parameter. The default value is three."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:156
+# af8282a7c19c4580a62b69371106d6f2
+msgid "The load balancing service can be supported by only one tier inside the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:159
+# 39cb5b3dc8fe40988ffba7f5ede4490d
+msgid "If an IP address is assigned to a tier:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:161
+# 176c27ebe07048b3a7836a228d011441
+msgid "That IP can't be used by more than one tier at a time in the VPC. For example, if you have tiers A and B, and a public IP1, you can create a port forwarding rule by using the IP either for A or B, but not for both."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:166
+# f43348e85da24485a1d92b63da2366ac
+msgid "That IP can't be used for StaticNAT, load balancing, or port forwarding rules for another guest network inside the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:169
+# fee8e4c6c5954adeb9005bf1d5ce023e
+msgid "Remote access VPN is not supported in VPC networks."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:173
+# 96fc9927ad5141bba2d657b1963d9d87
+msgid "Adding a Virtual Private Cloud"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:175
+# 5f129175d6144d298c7ede91ac9ec513
+msgid "When creating the VPC, you simply provide the zone and a set of IP addresses for the VPC network address space. You specify this set of addresses in the form of a Classless Inter-Domain Routing (CIDR) block."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:185
+# c91fb511977940b7b6f4adbffe2da030
+msgid "Click Add VPC. The Add VPC page is displayed as follows:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:187
+# 7632a958cf894fb9a2bfac92d1f5600d
+msgid "|add-vpc.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:191
+# 8ecd10dee5dc44baa12a0ec575b6f501
+msgid "**Name**: A short name for the VPC that you are creating."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:193
+# 27ae714de91a400780ba0479927daaf5
+msgid "**Description**: A brief description of the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:195
+# 1824e109bd6c46ac8a5a0c0f2057b2fa
+msgid "**Zone**: Choose the zone where you want the VPC to be available."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:197
+# e936203c2e05451299d2de67f4f47ebc
+msgid "**Super CIDR for Guest Networks**: Defines the CIDR range for all the tiers (guest networks) within a VPC. When you create a tier, ensure that its CIDR is within the Super CIDR value you enter. The CIDR must be RFC1918 compliant."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:202
+# 6ca68d15f75048b0b195f40134796a2c
+msgid "**DNS domain for Guest Networks**: If you want to assign a special domain name, specify the DNS suffix. This parameter is applied to all the tiers within the VPC. That implies, all the tiers you create in the VPC belong to the same DNS domain. If the parameter is not specified, a DNS domain name is generated automatically."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:208
+# 71b34c1e720143dfa39c979df560f4ca
+msgid "**Public Load Balancer Provider**: You have two options: VPC Virtual Router and Netscaler."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:215
+# 8798d1945a1c4084a1b2a0614ec9db32
+msgid "Adding Tiers"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:217
+# 98d4e1b6db094ef3be8c292cd0efa54b
+msgid "Tiers are distinct locations within a VPC that act as isolated networks, which do not have access to other tiers by default. Tiers are set up on different VLANs that can communicate with each other by using a virtual router. Tiers provide inexpensive, low latency network connectivity to other tiers within the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:229
+#: ../../networking/virtual_private_cloud_config.rst:1366
+# 3314f3a5a14a4b969d7ee70acab97a4a
+# f747c26b980441cc9b6ecb7baf8f8557
+msgid "All the VPC that you have created for the account is listed in the page."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:233
+# 8844e1d7896046a7881fdb53a34d3dce
+msgid "The end users can see their own VPCs, while root and domain admin can see any VPC they are authorized to see."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:236
+#: ../../networking/virtual_private_cloud_config.rst:1369
+# 9771fbcf9e3e4bc7adeceaeb5db1a8ff
+# 19ef7e315e30411398c644e4ee829252
+msgid "Click the Configure button of the VPC for which you want to set up tiers."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:239
+# c78aa8064f6342b481fd5870fce87c54
+msgid "Click Create network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:241
+# c405f8d748a04cbe8c19e538c402ff7e
+msgid "The Add new tier dialog is displayed, as follows:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:243
+# 34e2e606b003480ab786bf798340707f
+msgid "|add-tier.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:245
+# e176f3eb0eff46849004f861f27d70ba
+msgid "If you have already created tiers, the VPC diagram is displayed. Click Create Tier to add a new tier."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:252
+# 6da7a219b10c4cd393a25728f68792f6
+msgid "**Name**: A unique name for the tier you create."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:254
+# 1b4af9e2df5d4c45a8fe0846d9421847
+msgid "**Network Offering**: The following default network offerings are listed: Internal LB, DefaultIsolatedNetworkOfferingForVpcNetworksNoLB, DefaultIsolatedNetworkOfferingForVpcNetworks"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:259
+# ee49520ec77a4c7097618acebca06e0a
+msgid "In a VPC, only one tier can be created by using LB-enabled network offering."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:267
+# fe3e7690b8434d17bee25931f77b4060
+msgid "**VLAN**: The VLAN ID for the tier that the root admin creates."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:269
+# ac4187501eb24391a8fe48b9eaea78db
+msgid "This option is only visible if the network offering you selected is VLAN-enabled."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:272
+# 4f0b4d89f6904969ae3ee5e09664a312
+msgid "For more information, see `\"Assigning VLANs to Isolated Networks\" <hosts.html#assigning-vlans-to-isolated-networks>`_."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:283
+# 9d2a27efdd3340729e2b4d326a7ae82f
+msgid "Continue with configuring access control list for the tier."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:289
+# cfc11ab12602462ea15568f2ee59a571
+msgid "Configuring Network Access Control List"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:291
+# 80d05b449ec74dcf9676a890310dd627
+msgid "Define Network Access Control List (ACL) on the VPC virtual router to control incoming (ingress) and outgoing (egress) traffic between the VPC tiers, and the tiers and Internet. By default, all incoming traffic to the guest networks is blocked and all outgoing traffic from guest networks is allowed, once you add an ACL rule for outgoing traffic, then only outgoing traffic specified in this ACL rule is allowed, the rest is blocked. To open the ports, you must create a new network ACL. The network ACLs can be created for the tiers only if the NetworkACL service is supported."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:303
+# aa42198a93034f1c84348ea431669aa6
+msgid "About Network ACL Lists"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:305
+# b8c70fbf1bc54242a435cb7f6a8bcfff
+msgid "In CloudStack terminology, Network ACL is a group of Network ACL items. Network ACL items are nothing but numbered rules that are evaluated in order, starting with the lowest numbered rule. These rules determine whether traffic is allowed in or out of any tier associated with the network ACL. You need to add the Network ACL items to the Network ACL, then associate the Network ACL with a tier. Network ACL is associated with a VPC and can be assigned to multiple VPC tiers within a VPC. A Tier is associated with a Network ACL at all the times. Each tier can be associated with only one ACL."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:315
+# 2b2f7cf9c53546368b42fa70f544bd0a
+msgid "The default Network ACL is used when no ACL is associated. Default behavior is all the incoming traffic is blocked and outgoing traffic is allowed from the tiers. Default network ACL cannot be removed or modified. Contents of the default Network ACL is:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:321
+# 94ec3c0bd9ad4d2694658ae87c05a6dc
+msgid "Rule"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:321
+# cdf1ee2618b8425fa236a5ba71e879f8
+msgid "Protocol"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:321
+# 71beb1131ecc4bf79f519067b0cc0421
+msgid "Traffic type"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:321
+# 02feb18dc4204c6d816848bece6753f2
+msgid "Action"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:323
+#: ../../networking/virtual_private_cloud_config.rst:324
+# 7b039a75bc4e40b0998ee720fc9be7af
+# b4c3a2a2f8274af8b1e3a9590128b37e
+msgid "All"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:323
+# 29b1464ed65441e9aef0eac71c0aee88
+msgid "Ingress"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:323
+#: ../../networking/virtual_private_cloud_config.rst:324
+# 0f25a9ce81214a8db99b2c15ca68ecaf
+# 1f7b00eb40c84e49afad68ec636cf017
+msgid "0.0.0.0/0"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:324
+# 2a938982deaf4bee91999a560045df0f
+msgid "Egress"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:329
+# a89760a050314e7687a774e021984e36
+msgid "Creating ACL Lists"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:364
+#: ../../networking/virtual_private_cloud_config.rst:391
+# 3eda1f1ad1e84a5fa0abdd0d63298377
+# c9c0ef8b2d724a88af647c817e2e60b3
+msgid "Select Network ACL Lists."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:366
+# d948b72948e443708b6aa2c594cbf48c
+msgid "The following default rules are displayed in the Network ACLs page: default\\_allow, default\\_deny."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:369
+# a06453197ea54b78a1671d85bf9e73d7
+msgid "Click Add ACL Lists, and specify the following:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:371
+# 936eba7c1c614d71b4d81a9836930774
+msgid "**ACL List Name**: A name for the ACL list."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:373
+# 33929738488f4ea9919dcf6a7e3fe2f5
+msgid "**Description**: A short description of the ACL list that can be displayed to users."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:378
+# 7c8c60eca2c549f5b45770647d1aa00c
+msgid "Creating an ACL Rule"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:393
+# 9dd4e8a5913f4029b9009edcec1a873e
+msgid "In addition to the custom ACL lists you have created, the following default rules are displayed in the Network ACLs page: default\\_allow, default\\_deny."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:397
+#: ../../networking/virtual_private_cloud_config.rst:477
+# a6f4bd8cfb1b4f6fad84ffaa0cb8be7d
+# 8f83289dee8e4333b67e394e3c8d0f0d
+msgid "Select the desired ACL list."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:399
+# 92b66b5dafcf4032a201494a372c5a09
+msgid "Select the ACL List Rules tab."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:401
+# dfaf3ab49c4a4d8c89f6e9f968c769ac
+msgid "To add an ACL rule, fill in the following fields to specify what kind of network traffic is allowed in the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:404
+# 51c1de77519e4d1dbd873ec733e2ba75
+msgid "**Rule Number**: The order in which the rules are evaluated."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:406
+# 86a9b66780f94ece927187a782db5a7b
+msgid "**CIDR**: The CIDR acts as the Source CIDR for the Ingress rules, and Destination CIDR for the Egress rules. To accept traffic only from or 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 incoming traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:413
+# 8330289162464c20a853e935c0a8994c
+msgid "**Action**: What action to be taken. Allow traffic or block."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:415
+# 498ccf8b2f69422382f0f84e1ca4539c
+msgid "**Protocol**: The networking protocol that sources use to send traffic to the tier. 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. All supports all the traffic. Other option is Protocol Number."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:422
+# e63c6c1906af4a6b8ed6d87b9c73ed40
+msgid "**Start Port**, **End Port** (TCP, UDP only): A range of listening ports that are the destination for the incoming traffic. If you are opening a single port, use the same number in both fields."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:426
+# 7c79246e902c4bbc8186dda26670b328
+msgid "**Protocol Number**: The protocol number associated with IPv4 or IPv6. For more information, see `Protocol Numbers <http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xml>`_."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:430
+# f108c8672b5549f0b7bccead5633f71e
+msgid "**ICMP Type**, **ICMP Code** (ICMP only): The type of message and error code that will be sent."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:433
+# aea6fa8baba04251bd617d19ec0fac50
+msgid "**Traffic Type**: The type of traffic: Incoming or outgoing."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:435
+# 8837fecc5cbe4deb9b9b32eb1e7a22bb
+msgid "Click Add. The ACL rule is added."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:437
+# ff24506a3edf4b368b6851738d3cd4a6
+msgid "You can edit the tags assigned to the ACL rules and delete the ACL rules you have created. Click the appropriate button in the Details tab."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:443
+# 686d25e2eb934b228756cffad503dc14
+msgid "Creating a Tier with Custom ACL List"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:445
+#: ../../networking/virtual_private_cloud_config.rst:461
+# 12b4daba446b406188c175ab28efa5c1
+# e044ead1ada14ab5b3ec8b3e711b655c
+msgid "Create a VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:447
+#: ../../networking/virtual_private_cloud_config.rst:467
+# 5f8cae5888424f2a90e4e67bb1174768
+# 1a83d09401c84e96a549f864c6695017
+msgid "Create a custom ACL list."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:449
+#: ../../networking/virtual_private_cloud_config.rst:469
+# a0a748dbf9a14a6292e606e617c28d64
+# b359fbe706df412e8209f49644e377e0
+msgid "Add ACL rules to the ACL list."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:451
+#: ../../networking/virtual_private_cloud_config.rst:463
+# 3c202066013d4bc0adfd54fbb57b6a40
+# c1084edbb18d4e88a8862f51a676882d
+msgid "Create a tier in the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:453
+# 2693d2f98f2144d2bd046d2a6ee9edc4
+msgid "Select the desired ACL list while creating a tier."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:459
+# 8d75f722483847bfbaf121d50683108f
+msgid "Assigning a Custom ACL List to a Tier"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:465
+# fb8e5f4022c7464683a31b78f61d773e
+msgid "Associate the tier with the default ACL rule."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:471
+# 39e12cdf7861405b9cb6e499e2a43a69
+msgid "Select the tier for which you want to assign the custom ACL."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:473
+# 948fcbc5ab17415abed167dfec847398
+msgid "Click the Replace ACL List icon. |replace-acl-icon.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:475
+# 1e59b7c5187d410c84f77a2de169bfd2
+msgid "The Replace ACL List dialog is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:485
+# 6a8102624df0467d816ba212863e0f4a
+msgid "Adding a Private Gateway to a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:487
+# d90a68b590214ef5a6ef4f86afbf6fd5
+msgid "A private gateway can be added by the root admin only. The VPC private network has 1:1 relationship with the NIC of the physical network. You can configure multiple private gateways to a single VPC. No gateways with duplicated VLAN and IP are allowed in the same data center."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:501
+# 8834cea2024a427e8ed0a565fd66bd19
+msgid "Click the Configure button of the VPC to which you want to configure load balancing rules."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:509
+#: ../../networking/virtual_private_cloud_config.rst:744
+#: ../../networking/virtual_private_cloud_config.rst:802
+# b947ba8a391e4148ae31611b4dd8a083
+# 97f4415d522c4cd0bcb3fccbe14ce6bb
+# 3ee1ffc35ae4421ab543c330faa61f59
+msgid "The following options are displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:531
+# 0486f473e9e3414bb92b039e48b87494
+msgid "Select Private Gateways."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:533
+# a70922624b2b4f53abab8e82e8145edb
+msgid "The Gateways page is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:535
+# 997a7c9466244a49a73f4b7b36f80498
+msgid "Click Add new gateway:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:537
+# 46ae796875074a9bb87aa12a389ff481
+msgid "|add-new-gateway-vpc.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:541
+# 2bdb16a51b0c4b0ebc5ecc1fe2301931
+msgid "**Physical Network**: The physical network you have created in the zone."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:544
+# 40e19742c3d6491ba0358d3376dca15c
+msgid "**IP Address**: The IP address associated with the VPC gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:546
+# b992f8b2e26749a7b8eb0483fbe18516
+msgid "**Gateway**: The gateway through which the traffic is routed to and from the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:549
+# 08b7e18cfef146d5aac5e3a932b9ceee
+msgid "**Netmask**: The netmask associated with the VPC gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:551
+# 17bf2c0bfeb849c286ef214c11472b88
+msgid "**VLAN**: The VLAN associated with the VPC gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:553
+# 7c787d4d6da0489494c04559abeb12bb
+msgid "**Source NAT**: Select this option to enable the source NAT service on the VPC private gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:556
+# d3c83ba870aa46f481f5b326130c542f
+msgid "See \":ref:`source-nat-priv-gw`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:558
+# d19b3a39546842e5a175f1e7e7819cef
+msgid "**ACL**: Controls both ingress and egress traffic on a VPC private gateway. By default, all the traffic is blocked."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:561
+# eb9e7232fbad4dc5b0bae719d0592256
+msgid "See \":ref:`acl-priv-gw`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:563
+# 7aa9fc8200334aa4901dc0974c908c27
+msgid "The new gateway appears in the list. You can repeat these steps to add more gateway for this VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:570
+# 2b0ce92e7bed418b936208b7bad7d5b7
+msgid "Source NAT on Private Gateway"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:572
+# fe7ed22a9393446c9cc5ad4d4cd5edc3
+msgid "You might want to deploy multiple VPCs with the same super CIDR and guest tier CIDR. Therefore, multiple guest VMs from different VPCs can have the same IPs to reach a enterprise data center through the private gateway. In such cases, a NAT service need to be configured on the private gateway to avoid IP conflicts. If Source NAT is enabled, the guest VMs in VPC reaches the enterprise network via private gateway IP address by using the NAT service."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:580
+# 5a711a13a70c4237b78e207150d2aa6b
+msgid "The Source NAT service on a private gateway can be enabled while adding the private gateway. On deletion of a private gateway, source NAT rules specific to the private gateway are deleted."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:584
+# 63952cd0c2df4a2ba370e8e3f499ebb3
+msgid "To enable source NAT on existing private gateways, delete them and create afresh with source NAT."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:591
+# ca4ce702729d44de9545633f08b8e2c0
+msgid "ACL on Private Gateway"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:593
+# f6b347934c2d421d9b87c66c8944a8b9
+msgid "The traffic on the VPC private gateway is controlled by creating both ingress and egress network ACL rules. The ACLs contains both allow and deny rules. As per the rule, all the ingress traffic to the private gateway interface and all the egress traffic out from the private gateway interface are blocked."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:599
+# 6f1f3b0dd74f4ce594dbb45f33ef48e9
+msgid "You can change this default behaviour while creating a private gateway. Alternatively, you can do the following:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:602
+#: ../../networking/virtual_private_cloud_config.rst:633
+# 8238d9adc04246d9a930b0b546fc0dc4
+# b52342a1c90a4d8588ad601a3cb95384
+msgid "In a VPC, identify the Private Gateway you want to work with."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:604
+# d0331cbe6cb343e9baeed7ebabf6898b
+msgid "In the Private Gateway page, do either of the following:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:606
+# d004af9551994806b983a6b59283779b
+msgid "Use the Quickview. See 3."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:608
+# 40cc4d8cf410478e812d5cb50a621341
+msgid "Use the Details tab. See 4 through ."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:610
+# 6d609b2091244d7ca3405dc4269efe6f
+msgid "In the Quickview of the selected Private Gateway, click Replace ACL, select the ACL rule, then click OK"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:613
+# 83b99b7439014125a36b48a6b0a7f80e
+msgid "Click the IP address of the Private Gateway you want to work with."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:615
+# 14187251994f4a8c8ccffac034d839d3
+msgid "In the Detail tab, click the Replace ACL button. |replace-acl-icon.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:618
+# 9dbebf0df0394108a99bc5c305a172cb
+msgid "The Replace ACL dialog is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:620
+# ec9140575d1943d0b76f6536f0862e43
+msgid "select the ACL rule, then click OK."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:622
+# a324b1ff2ee443c885f67b4510b32b3e
+msgid "Wait for few seconds. You can see that the new ACL rule is displayed in the Details page."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:627
+# 9a47b3e0d1cf4da0990cb87352ca3de5
+msgid "Creating a Static Route"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:629
+# e189527e17704f7cab4e4e21f6b2549f
+msgid "CloudStack enables you to specify routing for the VPN connection you create. You can enter one or CIDR addresses to indicate which traffic is to be routed back to the gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:635
+# b95c782aec15430ab351080cb9dc47ba
+msgid "In the Private Gateway page, click the IP address of the Private Gateway you want to work with."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:638
+# f62c207d59b144dd8e5724167fb00821
+msgid "Select the Static Routes tab."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:640
+# 98e5544022bb4cf39452861c830d9665
+msgid "Specify the CIDR of destination network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:644
+# 35f9f527d4364d4db2faefcd92d3a394
+msgid "Wait for few seconds until the new route is created."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:648
+# f5f80f387b5246caa603111d30dcfab7
+msgid "Blacklisting Routes"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:650
+# 8515025cd30a4b30b46f527ea9be5b2b
+msgid "CloudStack enables you to block a list of routes so that they are not assigned to any of the VPC private gateways. Specify the list of routes that you want to blacklist in the ``blacklisted.routes`` global parameter. Note that the parameter update affects only new static route creations. If you block an existing static route, it remains intact and continue functioning. You cannot add a static route if the route is blacklisted for the zone."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:660
+# 0a8f5a5461c9432188d46d5dc80a91a0
+msgid "Deploying VMs to the Tier"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:674
+# ad6ac67751dc4a668c90b3901921cecf
+msgid "The VPC page is displayed where all the tiers you have created are listed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:677
+# 8da453ba01704444966e4877573b0073
+msgid "Click Virtual Machines tab of the tier to which you want to add a VM."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:679
+# 7564a13e0be543f29abd89bd7ef0c987
+msgid "|add-vm-vpc.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:681
+# ceb06d16d0d545d79a24d120e0cc1557
+msgid "The Add Instance page is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:683
+# e0c2b5aaefda4e768eca34fdf762257c
+msgid "Follow the on-screen instruction to add an instance. For information on adding an instance, see the Installation Guide."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:688
+# 23b31383376b429ab397c708f57a73bb
+msgid "Deploying VMs to VPC Tier and Shared Networks"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:690
+# 2bac09bc2c4a4906abd70bb5d83a5111
+msgid "CloudStack allows you deploy VMs on a VPC tier and one or more shared networks. With this feature, VMs deployed in a multi-tier application can receive monitoring services via a shared network provided by a service provider."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:695
+# e86ba5c678024942ba0da9ff54dd94ae
+msgid "Log in to the CloudStack UI as an administrator."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:697
+# 50b2ea4e91a94d79b91efe6ba058dadd
+msgid "In the left navigation, choose Instances."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:699
+# 0f4af44df518497191f2b3af865061d2
+msgid "Click Add Instance."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:701
+# a5a3bb272f26416fa231be8972453e35
+msgid "Select a zone."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:703
+# 51a5385be8d5470b859a693b22b5c52b
+msgid "Select a template or ISO, then follow the steps in the wizard."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:705
+# bb1283c54a10494a96923abd8273c452
+msgid "Ensure that the hardware you have allows starting the selected service offering."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:708
+# afcf609fa1fb4cc5a296c5eb20e7c9f5
+msgid "Under Networks, select the desired networks for the VM you are launching."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:711
+# f749aa3668cd4b44bb2ebeff764f56dd
+msgid "You can deploy a VM to a VPC tier and multiple shared networks."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:713
+# b0aa4f80622f4438a373dce39b0c6537
+msgid "|addvm-tier-sharednw.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:715
+# d3d95e78e214447ab42817d669d4fb61
+msgid "Click Next, review the configuration and click Launch."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:717
+# 2f1d867de64e4eef8f377943f7f76f2b
+msgid "Your VM will be deployed to the selected VPC tier and shared network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:721
+# 5dfeffe5b39b420b8932120cf5a86f75
+msgid "Acquiring a New IP Address for a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:723
+# 31693458308e43659d6be92a4f78c332
+msgid "When you acquire an IP address, all IP addresses are allocated to VPC, not to the guest networks within the VPC. The IPs are associated to the guest network only when the first port-forwarding, load balancing, or Static NAT rule is created for the IP or the network. IP can't be associated to more than one network at a time."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:766
+# 075db32f8684487ebf86e97f17da3fb0
+msgid "Select IP Addresses."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:768
+# ca26d66e3c0644258b7e33c973c87793
+msgid "The Public IP Addresses page is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:770
+# 501fe4755a8a4045952f5337c4e34ad3
+msgid "Click Acquire New IP, and click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:772
+# 6654947db0c74b30bedc7c3644dad688
+msgid "You are prompted for confirmation because, typically, IP addresses are a limited resource. Within a few moments, the new IP address should appear with the state Allocated. You can now use the IP address in port forwarding, load balancing, and static NAT rules."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:779
+# 8c7d4d3811bd4e5a9cdc8fd5b9fc07a4
+msgid "Releasing an IP Address Alloted to a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:781
+# fa1d68cb193b4e8186bc44093bb34441
+msgid "The IP address is a limited resource. If you no longer need a particular IP, you can disassociate it from its VPC and return it to the pool of available addresses. An IP address can be released from its tier, only when all the networking ( port forwarding, load balancing, or StaticNAT ) rules are removed for this IP address. The released IP address will still belongs to the same VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:797
+# 2ce137b1395747dc8e893c80bcda0e22
+msgid "Click the Configure button of the VPC whose IP you want to release."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:824
+# 9fd161045cbe45a281c9d8e874926856
+msgid "Select Public IP Addresses."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:828
+# 5efdb9a8c3284fe195862d5624cd2ad7
+msgid "Click the IP you want to release."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:830
+# 2a495a61f8ae472bb5500bb1d609c595
+msgid "In the Details tab, click the Release IP button |release-ip-icon.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:836
+# 0d6369bc16a24d93ab131097fa1c26d0
+msgid "Enabling or Disabling Static NAT on a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:838
+# ca62a217246f4a06a8d12965cdfa849c
+msgid "A static NAT rule maps a public IP address to the private IP address of a VM in a VPC to allow Internet traffic to it. This section tells how to enable or disable static NAT for a particular IP address in a VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:863
+# 2b8f37a180cf44aabf4c1102171a0a0f
+msgid "For each tier, the following options are displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:889
+# 27a3e8f27ef74f348d38e0a750d4b22d
+msgid "Click the IP you want to work with."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:891
+# cdf3e4bc65504a1ba280c33c311c5ff3
+msgid "In the Details tab,click the Static NAT button. |enable-disable.png| The button toggles between Enable and Disable, depending on whether static NAT is currently enabled for the IP address."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:896
+# 5d57c9b6170d475cb726d63bd8a7d4b4
+msgid "If you are enabling static NAT, a dialog appears as follows:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:898
+# 8652f2ad4f894964b5749224fa457264
+msgid "|select-vmstatic-nat.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:900
+# 8642184696854f59a8be93ce090ef2fb
+msgid "Select the tier and the destination VM, then click Apply."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:904
+# 3f81050b54e046ce8e1509efface1df4
+msgid "Adding Load Balancing Rules on a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:906
+# 64775e05d52c4fd68cdf87d2e24c802f
+msgid "In a VPC, you can configure two types of load balancing: external LB and internal LB. External LB is nothing but a LB rule created to redirect the traffic received at a public IP of the VPC virtual router. The traffic is load balanced within a tier based on your configuration. Citrix NetScaler and VPC virtual router are supported for external LB. When you use internal LB service, traffic received at a tier is load balanced across different VMs within that tier. For example, traffic reached at Web tier is redirected to another VM in that tier. External load balancing devices are not supported for internal LB. The service is provided by a internal LB VM configured on the target tier."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:919
+# 5f34d7b800174adea102238371bbf537
+msgid "Load Balancing Within a Tier (External LB)"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:921
+# 060c73cf4ee8497d961587b4e5e88f8e
+msgid "A CloudStack user or administrator may create load balancing rules that balance traffic received at a public IP to one or more VMs that belong to a network tier that provides load balancing service in a VPC. A user creates a rule, specifies an algorithm, and assigns the rule to a set of VMs within a tier."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:929
+# e988811e64294d9690e628d0a32d6f6e
+msgid "Enabling NetScaler as the LB Provider on a VPC Tier"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:931
+# 1a47a4579a094d95b8a0de664ef21a91
+msgid "Add and enable Netscaler VPX in dedicated mode."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:933
+# 9cd82ffd68b24939ae095006b094d212
+msgid "Netscaler can be used in a VPC environment only if it is in dedicated mode."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:936
+# b3484bb76994414e9ea417121e40d040
+msgid "Create a network offering, as given in \":ref:`create-net-offering-ext-lb`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:938
+# 121f69be457f40c5a9230d5ea3592bfb
+msgid "Create a VPC with Netscaler as the Public LB provider."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:940
+# e3da4dec088145cdab1337246f694c25
+msgid "For more information, see `\"Adding a Virtual Private Cloud\" <#adding-a-virtual-private-cloud>`_."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:943
+# a9a66b4ea7f240caa72b7230eb594dca
+msgid "For the VPC, acquire an IP."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:945
+# 41f7df1af1ff4bd8b55750efc9e38211
+msgid "Create an external load balancing rule and apply, as given in :ref:`create-ext-lb-rule`."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:952
+# 6f16d85076c347eb9f22335560475ef4
+msgid "Creating a Network Offering for External LB"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:954
+# 709e2fd0e27745f68f26028a48c613a5
+msgid "To have external LB support on VPC, create a network offering as follows:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:957
+#: ../../networking/virtual_private_cloud_config.rst:1163
+# 76d5fee0b6ef4598b2f4f80ee690c974
+# 80171134c89b4246b8e6d948ddf36a21
+msgid "Log in to the CloudStack UI as a user or admin."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:959
+#: ../../networking/virtual_private_cloud_config.rst:1165
+# d6358f1cb80b45c6becf012d6670f0ff
+# 19877c93762c4d95b38bfafc90fc110c
+msgid "From the Select Offering drop-down, choose Network Offering."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:963
+#: ../../networking/virtual_private_cloud_config.rst:1169
+# 34b1dc57da234cfcbef32cbb10126c3c
+# 1bba2b0d34da443ea11b5a194c8a3b59
+msgid "In the dialog, make the following choices:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:965
+#: ../../networking/virtual_private_cloud_config.rst:1171
+# 86e34c74e6134c7bb7c04554bfed9df0
+# 4e3f1479665d42f78ead497e7f965f00
+msgid "**Name**: Any desired name for the network offering."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:967
+#: ../../networking/virtual_private_cloud_config.rst:1173
+# c960eb115c114434af67b0fbc25be487
+# bc5490caeeff4328865c3f318b98cfee
+msgid "**Description**: A short description of the offering that can be displayed to users."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:970
+#: ../../networking/virtual_private_cloud_config.rst:1176
+# 84e47db19f574c3ba5d0b2f1154fbc45
+# 93388787993544a4901e262399be3022
+msgid "**Network Rate**: Allowed data transfer rate in MB per second."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:972
+#: ../../networking/virtual_private_cloud_config.rst:1178
+# 816b6192dc2f4e3ca02aeb6804edb355
+# 27411d0400294e9ba1bfb67609002343
+msgid "**Traffic Type**: The type of network traffic that will be carried on the network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:975
+#: ../../networking/virtual_private_cloud_config.rst:1181
+# c74a767bceed4a628199500712d7c8c7
+# eb0786cb716a4706a211b3b6088bb4b9
+msgid "**Guest Type**: Choose whether the guest network is isolated or shared."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:978
+#: ../../networking/virtual_private_cloud_config.rst:1184
+# c522088c1c6e47d79f06f5fe842e40ee
+# 0aea3f7e943e49b291046f8fc45d6484
+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."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:982
+#: ../../networking/virtual_private_cloud_config.rst:1188
+# b84887ec1f6c4513aa057f3a630484a1
+# 930505e9acaa4d9193047e12ab7c3a3e
+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\" <#about-virtual-private-clouds>`_."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:988
+#: ../../networking/virtual_private_cloud_config.rst:1195
+# ed834a8fdce7467eb36d015cba5a8227
+# dbc9e89b121148e296344a7619ca01db
+msgid "**Specify VLAN**: (Isolated guest networks only) Indicate whether a VLAN should be specified when this offering is used."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:991
+# 6e7a1944576040bbb72e01310aa2b99d
+msgid "**Supported Services**: Select Load Balancer. Use Netscaler or VpcVirtualRouter."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:994
+# 89f5557a4a6546158f9fdc778ad029c1
+msgid "**Load Balancer Type**: Select Public LB from the drop-down."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:996
+# 7a932d710a9843c0af0b0cf4522a5284
+msgid "**LB Isolation**: Select Dedicated if Netscaler is used as the external LB provider."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:999
+#: ../../networking/virtual_private_cloud_config.rst:1203
+# 4ac8eb66ecab474195206ca9dd076d42
+# fe97ea397c194e4284760800bee72bea
+msgid "**System Offering**: Choose the system service offering that you want virtual routers to use in this network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1002
+#: ../../networking/virtual_private_cloud_config.rst:1206
+# fdf046b7980844e19139feacede80d66
+# 6f5f9241b8e1492a846b95d1bf8c9fe1
+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."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1006
+#: ../../networking/virtual_private_cloud_config.rst:1210
+# d3ed6db3fe1745b78b2b927bc7d01a53
+# c9781285467f4ad1b249ead320965229
+msgid "Click OK and the network offering is created."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1012
+# 88f68116cf4240d1b534cf9122dca89d
+msgid "Creating an External LB Rule"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1023
+# 08a7150e85df4a9f8efd234f87de819b
+msgid "Click the Configure button of the VPC, for which you want to configure load balancing rules."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1026
+#: ../../networking/virtual_private_cloud_config.rst:1239
+# ea4d0a7fdac64d889620ae55b699113e
+# 0d81aa1b316a4977838e69024fa1072a
+msgid "The VPC page is displayed where all the tiers you created listed in a diagram."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1060
+#: ../../networking/virtual_private_cloud_config.rst:1328
+# a5ab0f5fbd054d0790aeb9802997b2d0
+# 5ff05892aa8e4255bd7bc42730f2c699
+msgid "Select the tier to which you want to apply the rule."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1066
+# ef5c662d47e24cd2bd98a84a97bf37cd
+msgid "**Public Port**: The port that receives the incoming traffic to be balanced."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1072
+#: ../../networking/virtual_private_cloud_config.rst:1268
+# 36f023f1ff9f4854a6413a29e48a1be5
+# 4842c5ef77d840658853291a3ee85181
+msgid "**Algorithm**. Choose the load balancing algorithm you want CloudStack to use. CloudStack supports the following well-known algorithms:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1078
+#: ../../networking/virtual_private_cloud_config.rst:1274
+# 70c9123d5f194ebf9c345f9ad993cdc0
+# 7ac4ebb233324a8eb27698cc7a04a5be
+msgid "Least connections"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1080
+#: ../../networking/virtual_private_cloud_config.rst:1276
+# 23d0139cefac4b7a805b0d7e4a1a43e5
+# 7eeb60a40f294f1dacce7d723e8e193c
+msgid "Source"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1082
+# 75a5279c04344957bc0a080be77c8274
+msgid "**Stickiness**. (Optional) Click Configure and choose the algorithm for the stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1086
+# 43d9888e2f9440e984b9541afc588eea
+msgid "**Add VMs**: Click Add VMs, then select two or more VMs that will divide the load of incoming traffic, and click Apply."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1089
+# 59f6f69006154b2f8ce3eb5d9e9e5351
+msgid "The new load balancing rule appears in the list. You can repeat these steps to add more load balancing rules for this IP address."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1094
+# b829d10e71d44f6eae3ea7663c35f418
+msgid "Load Balancing Across Tiers"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1096
+# ee38327ce5984aab9e56b1a4096f683f
+msgid "CloudStack supports sharing workload across different tiers within your VPC. Assume that multiple tiers are set up in your environment, such as Web tier and Application tier. Traffic to each tier is balanced on the VPC virtual router on the public side, as explained in `\"Adding Load Balancing Rules on a VPC\" <#adding-load-balancing-rules-on-a-vpc>`_. If you want the traffic coming from the Web tier to the Application tier to be balanced, use the internal load balancing feature offered by CloudStack."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1107
+# d83d8db5511d4aba8c9c4efd61e0f5e6
+msgid "How Does Internal LB Work in VPC?"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1109
+# c710a43f15e34b5ab71f20ea2709e950
+msgid "In this figure, a public LB rule is created for the public IP 72.52.125.10 with public port 80 and private port 81. The LB rule, created on the VPC virtual router, is applied on the traffic coming from the Internet to the VMs on the Web tier. On the Application tier two internal load balancing rules are created. An internal LB rule for the guest IP 10.10.10.4 with load balancer port 23 and instance port 25 is configured on the VM, InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.4 with load balancer port 45 and instance port 46 is configured on the VM, InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.6, with load balancer port 23 and instance port 25 is configured on the VM, InternalLBVM2."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1121
+# 37cf27e0f1d34d6eb0aed4b83bbd2b4c
+msgid "|vpc-lb.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1127
+# 2ebee5edba904c0a9de6b022c5d1e3d8
+msgid "Internal LB and Public LB are mutually exclusive on a tier. If the tier has LB on the public side, then it can't have the Internal LB."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1130
+# 82754be2930f483c83607cde35e73470
+msgid "Internal LB is supported just on VPC networks in CloudStack 4.2 release."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1133
+# a8769b5a4a9e48caab6c9ecc82e77234
+msgid "Only Internal LB VM can act as the Internal LB provider in CloudStack 4.2 release."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1136
+# b076139f831c4e3ba6417259ac863de8
+msgid "Network upgrade is not supported from the network offering with Internal LB to the network offering with Public LB."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1139
+# 969d6f5939874bca859151e7d0d68447
+msgid "Multiple tiers can have internal LB support in a VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1141
+# 67372cabb36b437a8232a78a78f08515
+msgid "Only one tier can have Public LB support in a VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1145
+# 69768caec218466dafc06876ae8e797f
+msgid "Enabling Internal LB on a VPC Tier"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1147
+# daf581a704674dc287b6516c737b20e9
+msgid "Create a network offering, as given in :ref:`creating-net-offering-internal-lb`."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1150
+# a3b6f09db9e44bc597c6dd364de8f2ec
+msgid "Create an internal load balancing rule and apply, as given in :ref:`create-int-lb-rule`."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1157
+# e6d4695c11f545a09e177701ad41e3c4
+msgid "Creating a Network Offering for Internal LB"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1159
+# b711b583939045f2b881dd3d65a60666
+msgid "To have internal LB support on VPC, either use the default offering, DefaultIsolatedNetworkOfferingForVpcNetworksWithInternalLB, or create a network offering as follows:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1198
+# 3248edb0427641c389adc91e927709f9
+msgid "**Supported Services**: Select Load Balancer. Select ``InternalLbVM`` from the provider list."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1201
+# e7e35dcafc134423bff098fbd63e22e9
+msgid "**Load Balancer Type**: Select Internal LB from the drop-down."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1216
+# 56e0a94386164762912004a783f992e4
+msgid "Creating an Internal LB Rule"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1218
+# 89853887164549829b5d2bf60bd1820d
+msgid "When you create the Internal LB rule and applies to a VM, an Internal LB VM, which is responsible for load balancing, is created."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1221
+# 353f381499f141628587960d6e26f5b0
+msgid "You can view the created Internal LB VM in the Instances page if you navigate to **Infrastructure** > **Zones** > <zone\\_ name> > <physical\\_network\\_name> > **Network Service Providers** > **Internal LB VM**. You can manage the Internal LB VMs as and when required from the location."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1236
+# 695b01da42ba4aafa25052faf19cfb61
+msgid "Locate the VPC for which you want to configure internal LB, then click Configure."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1242
+# 353f4dce86ad490c9f02ffb55550faf1
+msgid "Locate the Tier for which you want to configure an internal LB rule, click Internal LB."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1245
+# 2950ef7334d8445db81781a662805752
+msgid "In the Internal LB page, click Add Internal LB."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1247
+# c7bb9deb227d41a08b2d4a17f0c56272
+msgid "In the dialog, specify the following:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1251
+# acee91ffe73343149992e4445c25639d
+msgid "**Description**: A short description of the rule that can be displayed to users."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1254
+# 21c16720a2424baba66dd99f17596511
+msgid "**Source IP Address**: (Optional) The source IP from which traffic originates. The IP is acquired from the CIDR of that particular tier on which you want to create the Internal LB rule. If not specified, the IP address is automatically allocated from the network CIDR."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1260
+# 09ee6ad213fe4332930cd10d34913eba
+msgid "For every Source IP, a new Internal LB VM is created for load balancing."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1263
+# d79a0aa56c2d43a99118d61cdee35de5
+msgid "**Source Port**: The port associated with the source IP. Traffic on this port is load balanced."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1266
+# 2aa21466b141411194bccbfbce825ad3
+msgid "**Instance Port**: The port of the internal LB VM."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1280
+# 519302d094284d71b5c6fb38328a1324
+msgid "Adding a Port Forwarding Rule on a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1338
+# 8637eb165f5a4accba725d09dc0f0a2b
+msgid "**Protocol**: The communication protocol in use between the two ports."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1341
+# 6acdc3f1bfe647e8bc3f77d1c6ebe7cc
+msgid "TCP"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1343
+# a94613fd8a23416cbcd8dddc6013a988
+msgid "UDP"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1345
+# 10549636e52849679931a001d1d335eb
+msgid "**Add VM**: Click Add VM. Select the name of the instance to which this rule applies, and click Apply."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1348
+# 5be772f552314f2d8e9cee0ff65bf489
+msgid "You can test the rule by opening an SSH session to the instance."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1352
+# e0d8c785784b42e5b872d0d1e0e01fc8
+msgid "Removing Tiers"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1354
+# 7568184600d04040b5e2be7097d75720
+msgid "You can remove a tier from a VPC. A removed tier cannot be revoked. When a tier is removed, only the resources of the tier are expunged. All the network rules (port forwarding, load balancing and staticNAT) and the IP addresses associated to the tier are removed. The IP address still be belonging to the same VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1372
+# f487d939ba954e449d7080e7517574a6
+msgid "The Configure VPC page is displayed. Locate the tier you want to work with."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1375
+# c7fbdf1d685a4919a2ea4a0624d9d045
+msgid "Select the tier you want to remove."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1377
+# f5493869c62248649482971d798e37ca
+msgid "In the Network Details tab, click the Delete Network button. |del-tier.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1380
+# aa755672baae4d7697f96b16039da071
+msgid "Click Yes to confirm. Wait for some time for the tier to be removed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1384
+# 9b44d6e7259c4c4d88ddd3fbec0511de
+msgid "Editing, Restarting, and Removing a Virtual Private Cloud"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1386
+# a72ab3649f44452fad64ca5e5c27699f
+msgid "Ensure that all the tiers are removed before you remove a VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1397
+# 528e37d6eed24e24a482eda24bba84b4
+msgid "Select the VPC you want to work with."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1399
+# 85aecab9e0aa42e285e0946a9b7fc270
+msgid "In the Details tab, click the Remove VPC button |remove-vpc.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1401
+# d499762e52f543f7a82c853e728a5516
+msgid "You can remove the VPC by also using the remove button in the Quick View."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1404
+# db5c63c401ed457d8296666c3e708e2b
+msgid "You can edit the name and description of a VPC. To do that, select the VPC, then click the Edit button. |vpc-edit-icon.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1407
+# 85223757733c41afac7e59be10812ad4
+msgid "To restart a VPC, select the VPC, then click the Restart button. |restart-vpc.png|"
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:18
+# c73707abeeee4762af99c2fe10074730
+msgid "Persistent Networks"
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:20
+# f57736d14d734e409d67507b6128fbec
+msgid "The network that you can provision without having to deploy any VMs on it is called a persistent network. A persistent network can be part of a VPC or a non-VPC environment."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:24
+# ce6fd8a3ec00423d86e7ba4f4cba6189
+msgid "When you create other types of network, a network is only a database entry until the first VM is created on that network. When the first VM is created, a VLAN ID is assigned and the network is provisioned. Also, when the last VM is destroyed, the VLAN ID is released and the network is no longer available. With the addition of persistent network, you will have the ability to create a network in CloudStack in which physical devices can be deployed without having to run any VMs. Additionally, you can deploy physical devices on that network."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:33
+# 6fcce92beeff40cb864882157e6e38eb
+msgid "One of the advantages of having a persistent network is that you can create a VPC with a tier consisting of only physical devices. For example, you might create a VPC for a three-tier application, deploy VMs for Web and Application tier, and use physical machines for the Database tier. Another use case is that if you are providing services by using physical hardware, you can define the network as persistent and therefore even if all its VMs are destroyed the services will not be discontinued."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:44
+# 2967de4df3df472abd55988c65ca1c07
+msgid "Persistent Network Considerations"
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:46
+# 4091d1efe69a4148864ddea8b1361e5f
+msgid "Persistent network is designed for isolated networks."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:48
+# 153b60917c5c49d3982f1098e01b59b7
+msgid "All default network offerings are non-persistent."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:50
+# 77c3328fec084f13967871c9b7123076
+msgid "A network offering cannot be editable because changing it affects the behavior of the existing networks that were created using this network offering."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:54
+# 06bccf901e8a4ee8be58f15bfd579e68
+msgid "When you create a guest network, the network offering that you select defines the network persistence. This in turn depends on whether persistent network is enabled in the selected network offering."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:58
+# d92b9c95102f488ba671717466ac055f
+msgid "An existing network can be made persistent by changing its network offering to an offering that has the Persistent option enabled. While setting this property, even if the network has no running VMs, the network is provisioned."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:63
+# ef669f1e80be470eb1e8a8db355b2d4a
+msgid "An existing network can be made non-persistent by changing its network offering to an offering that has the Persistent option disabled. If the network has no running VMs, during the next network garbage collection run the network is shut down."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:68
+# 007f1cc1aa7c42f8a66e3fb305143475
+msgid "When the last VM on a network is destroyed, the network garbage collector checks if the network offering associated with the network is persistent, and shuts down the network only if it is non-persistent."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:75
+# 4d27044c9aad4e059509066b13f9dc3a
+msgid "Creating a Persistent Guest Network"
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:77
+# 30f307ec95db44a0b8c70317f2a9c100
+msgid "To create a persistent network, perform the following:"
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:79
+# f479c47b1f454044bc8c2e67d6f14f0a
+msgid "Create a network offering with the Persistent option enabled."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:81
+# 08ed25ddd4a8403e98bddb19816af5cf
+msgid "See `\"Creating a New Network Offering\" <networking.html#creating-a-new-network-offering>`_."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:84
+# fd6c23139519494b901a461ef6fd445e
+msgid "Select Network from the left navigation pane."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:86
+# 92c525d55a6643c6a9f89f6b1ee2ff2e
+msgid "Select the guest network that you want to offer this network service to."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:89
+# 7c5a5842cf864317a92199d463521c9f
+msgid "Click the Edit button."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:91
+# 552f67c193a3437586fc226221b340e3
+msgid "From the Network Offering drop-down, select the persistent network offering you have just created."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:18
+# 4cd6d99517e445589fe0847cd2035e84
+msgid "Setup a Palo Alto Networks Firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:22
+# a25de960bb5944a9a2ffe54913707ab8
+msgid "Functionality Provided"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:24
+# c9b058343ea14748825cfcc53a551dcf
+msgid "This implementation enables the orchestration of a Palo Alto Networks Firewall from within CloudStack UI and API."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:27
+# 0f204dd9374d4ca281f9fa055813bcb0
+msgid "**The following features are supported**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:29
+# 0a04c861f9c64663836468cf37783f6d
+msgid "List/Add/Delete Palo Alto Networks service provider"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:31
+# f032d6431c414cb3bbb06b959df9a121
+msgid "List/Add/Delete Palo Alto Networks network service offering"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:33
+# c1ad64a629ce42868368c8787dd4f3b8
+msgid "List/Add/Delete Palo Alto Networks network using the above service offering"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:35
+# 983ec08ac8f442c580217a2a2fb8a596
+msgid "Add an instance to a Palo Alto Networks network"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:37
+# 3ad3b15459c64a6eae255957c08316de
+msgid "Source NAT management on network create and delete"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:39
+# 452d433b69644504b60597d2c0abd868
+msgid "List/Add/Delete Ingress Firewall rule"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:41
+# 0a537c6e22f5405a970698d492049bda
+msgid "List/Add/Delete Egress Firewall rule (both 'Allow' and 'Deny' default rules supported)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:44
+# 6df7942d9fdd4433a02767a4b6bbd97a
+msgid "List/Add/Delete Port Forwarding rule"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:46
+# 5adfa913867943e9a5334e717ba621b6
+msgid "List/Add/Delete Static NAT rule"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:48
+# 9073fd9f1c574f99830d3323ff81b059
+msgid "Apply a Threat Profile to all firewall rules (more details in the Additional Features section)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:51
+# de1483044bfa4bb6a8d75e7825ab54af
+msgid "Apply a Log Forwarding profile to all firewall rules (more details in the Additional Features section)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:57
+# bb979ee8007748adb71a5a35c819303f
+msgid "Initial Palo Alto Networks Firewall Configuration"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:60
+# 933f635eb00e45d291ea9b284dde50c8
+msgid "Anatomy of the Palo Alto Networks Firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:62
+# 6c130d9bd83d4265aa57e471d8849d87
+msgid "In **'Network > Interfaces'** there is a list of physical interfaces as well as aggregated physical interfaces which are used for managing traffic in and out of the Palo Alto Networks Firewall device."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:66
+# f3ed9b3a42c94267a7aa3c8799d6f2d4
+msgid "In **'Network > Zones'** there is a list of the different configuration zones. This implementation will use two zones; a public (defaults to 'untrust') and private (defaults to 'trust') zone."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:70
+# 702c5d78734a4fb8ad9bdde0f6fe0fa8
+msgid "In **'Network > Virtual Routers'** there is a list of VRs which handle traffic routing for the Palo Alto Firewall. We only use a single Virtual Router on the firewall and it is used to handle all the routing to the next network hop."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:75
+# fa5e01b476f8473cb2cd6dba3c93b26d
+msgid "In **'Objects > Security Profile Groups'** there is a list of profiles which can be applied to firewall rules. These profiles are used to better understand the types of traffic that is flowing through your network. Configured when you add the firewall provider to CloudStack."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:80
+# 6ec861ebd15247b2a9d647243d07b9dc
+msgid "In **'Objects > Log Forwarding'** there is a list of profiles which can be applied to firewall rules. These profiles are used to better track the logs generated by the firewall. Configured when you add the firewall provider to CloudStack."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:85
+# 10bd8a298e9b4499a4e2b8158b2781ec
+msgid "In **'Policies > Security'** there is a list of firewall rules that are currently configured. You will not need to modify this section because it will be completely automated by CloudStack, but you can review the firewall rules which have been created here."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:90
+# 5deafeaa993b405cafa909f5c07398af
+msgid "In **'Policies > NAT'** there is a list of the different NAT rules. You will not need to modify this section because it will be completely automated by CloudStack, but you can review the different NAT rules that have been created here. Source NAT, Static NAT and Destination NAT (Port Forwarding) rules will show up in this list."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:99
+# 97d928354c784496b323810668db7981
+msgid "Configure the Public / Private Zones on the firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:101
+# fc57f3d20fc6497093dfee06aed841b5
+msgid "No manual configuration is required to setup these zones because CloudStack will configure them automatically when you add the Palo Alto Networks firewall device to CloudStack as a service provider. This implementation depends on two zones, one for the public side and one for the private side of the firewall."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:107
+# 5dc660fae9f340ae9d54c5ba27bccdc1
+msgid "The public zone (defaults to 'untrust') will contain all of the public interfaces and public IPs."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:110
+# af5503e4adbb4dff94c7db0cbfeda2b0
+msgid "The private zone (defaults to 'trust') will contain all of the private interfaces and guest network gateways."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:113
+# 0c1f328f71d949568997a16e0ee29ebb
+msgid "The NAT and firewall rules will be configured between these zones."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:118
+# 4edccd68911e4eb8ad8d16aae69c40c7
+msgid "Configure the Public / Private Interfaces on the firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:120
+# 7b5d71324ae94b4eb1345496cb5fc980
+msgid "This implementation supports standard physical interfaces as well as grouped physical interfaces called aggregated interfaces. Both standard interfaces and aggregated interfaces are treated the same, so they can be used interchangeably. For this document, we will assume that we are using 'ethernet1/1' as the public interface and 'ethernet1/2' as the private interface. If aggregated interfaces where used, you would use something like 'ae1' and 'ae2' as the interfaces."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:128
+# ce56405d9b404dd8abcbd2b47dbd6002
+msgid "This implementation requires that the 'Interface Type' be set to 'Layer3' for both the public and private interfaces. If you want to be able to use the 'Untagged' VLAN tag for public traffic in CloudStack, you will need to enable support for it in the public 'ethernet1/1' interface (details below)."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:133
+# e655877c1c3c4268b51d1f17b4d569e1
+msgid "**Steps to configure the Public Interface**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:135
+#: ../../networking/palo_alto_config.rst:171
+#: ../../networking/palo_alto_config.rst:228
+# e8057bd4216c433a90d5747562875a83
+# e308adb3c6de47c3998377447d260f7e
+# 25d30e44808748d2bb2915a15019e45e
+msgid "Log into Palo Alto Networks Firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:137
+#: ../../networking/palo_alto_config.rst:230
+# 86c58907aa3c4905ac84366e69565cd9
+# 9e1f9a8ecebd488e8489f498bfc9409a
+msgid "Navigate to 'Network > Interfaces'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:139
+# d130fc55cd9d49c5a73893a0c995e367
+msgid "Click on 'ethernet1/1' (for aggregated ethernet, it will probably be called 'ae1')"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:142
+#: ../../networking/palo_alto_config.rst:155
+# 33208ee8235747389e981e3758d7dc4e
+# 39345e835bac41baa611bcf824968ff2
+msgid "Select 'Layer3' from the 'Interface Type' list"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:144
+# b0867e0d6cb34b75b442b55cfa026322
+msgid "Click 'Advanced'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:146
+# 0c56d4c03cf243f6a1a87f9d8ca7e880
+msgid "Check the 'Untagged Subinterface' check-box"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:148
+#: ../../networking/palo_alto_config.rst:157
+#: ../../networking/palo_alto_config.rst:193
+#: ../../networking/palo_alto_config.rst:195
+#: ../../networking/palo_alto_config.rst:265
+#: ../../networking/palo_alto_config.rst:339
+#: ../../networking/palo_alto_config.rst:388
+#: ../../networking/palo_alto_config.rst:426
+#: ../../networking/palo_alto_config.rst:455
+# 9166a2200b574af9b0ffe071ed3f4b87
+# 00c33fde208a445a9be7a319592575fc
+# 987a5a8988304ce2896e1879196846a5
+# 065cd5ad2daf471ea266f1b0d2fda873
+# c3f6ec8691624d8ab74249c07e266983
+# 91645da523df4c5ab7b8492737d911f5
+# 4240529e3bd14c3ca9c9d3376612f6f7
+# d3d09b3543e544f3bddba24c6963e421
+# 380b2d7379934a6da1b399eab4d37c07
+msgid "Click 'OK'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:150
+# a53d6716c3174e058cf5ad15298f16e9
+msgid "**Steps to configure the Private Interface**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:152
+# 3aa72dc4f76541deb400a07b2b6b6787
+msgid "Click on 'ethernet1/2' (for aggregated ethernet, it will probably be called 'ae2')"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:162
+# 9be091f2707545c88df4139ff618a457
+msgid "Configure a Virtual Router on the firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:164
+# 84d511674355441bbe7dbe76d66c768f
+msgid "The Virtual Router on the Palo Alto Networks Firewall is not to be confused with the Virtual Routers that CloudStack provisions. For this implementation, the Virtual Router on the Palo Alto Networks Firewall will ONLY handle the upstream routing from the Firewall to the next hop."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:169
+# e82ded6aea36475f968637969a284573
+msgid "**Steps to configure the Virtual Router**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:173
+# 579fa3c360f448d08cbcf3ed1ac4c275
+msgid "Navigate to 'Network > Virtual Routers'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:175
+# c0ff1f9d1a7247718698f44028af33b5
+msgid "Select the 'default' Virtual Router or Add a new Virtual Router if there are none in the list"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:178
+# 9d99adc7f2b74c30b6053032d36fabb3
+msgid "If you added a new Virtual Router, you will need to give it a 'Name'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:180
+# feab30a949cd4a22885bd65920931c99
+msgid "Navigate to 'Static Routes > IPv4'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:182
+# ac625a8780de43ed897656d4cfb74bcd
+msgid "'Add' a new static route"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:184
+# 472da2053fed453e96fb4acb49fd7e62
+msgid "**Name**: next_hop (you can name it anything you want)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:186
+# cbfb1fb365b04c96b7df8ee388ae85d7
+msgid "**Destination**: 0.0.0.0/0 (send all traffic to this route)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:188
+# cda878dca5164d2f8e01aa0ff2848a96
+msgid "**Interface**: ethernet1/1 (or whatever you set your public interface as)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:191
+# a8dff252ac8841e1b30d1b61396e2f83
+msgid "**Next Hop**: (specify the gateway IP for the next hop in your network)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:200
+# 903e21b9a4a14125bacefde84d94aff4
+msgid "Configure the default Public Subinterface"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:202
+# 2bd085187cbc476bbd72de056c01f9b1
+msgid "The current implementation of the Palo Alto Networks firewall integration uses CIDRs in the form of 'w.x.y.z/32' for the public IP addresses that CloudStack provisions. Because no broadcast or gateway IPs are in this single IP range, there is no way for the firewall to route the traffic for these IPs. To route the traffic for these IPs, we create a single subinterface on the public interface with an IP and a CIDR which encapsulates the CloudStack public IP range. This IP will need to be inside the subnet defined by the CloudStack public range netmask, but outside the CloudStack public IP range. The CIDR should reflect the same subnet defined by the CloudStack public range netmask. The name of the subinterface is determined by the VLAN configured for the public range in CloudStack."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:214
+# 1027972bdb804444a04abfcb173c3213
+msgid "To clarify this concept, we will use the following example."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:216
+# a217cfb35c1942b49aad39cf26323af1
+msgid "**Example CloudStack Public Range Configuration**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:218
+# 0d8df54c42af461d957cae7fb26c8b0f
+msgid "**Gateway**: 172.30.0.1"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:220
+# 203a1dcc624243cebe5260b914ca588d
+msgid "**Netmask**: 255.255.255.0"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:222
+# fe0cf8e78a914ef6a9d994d84e33f273
+msgid "**IP Range**: 172.30.0.100 - 172.30.0.199"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:224
+# 763cbf33799e4a66ba4ebba67deedea8
+msgid "**VLAN**: Untagged"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:226
+# ef7b22d901134531a4ddc52d109f3884
+msgid "**Configure the Public Subinterface**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:232
+# ce16b404e8fa422cb8d798d367d8ef89
+msgid "Select the 'ethernet1/1' line (not clicking on the name)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:234
+# 032bbee32d6343328a3ad9989c008a6d
+msgid "Click 'Add Subinterface' at the bottom of the window"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:236
+# 6359f5f7ec124236b0f34c9d7e6c3635
+msgid "Enter 'Interface Name': 'ethernet1/1' . '9999'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:238
+# ed56cd87d56b41ed87efb9d1bf1c66f8
+msgid "9999 is used if the CloudStack public range VLAN is 'Untagged'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:240
+# 57a09d78c0084f9d839011aec1eed2eb
+msgid "If the CloudStack public range VLAN is tagged (eg: 333), then the name will reflect that tag"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:243
+# bcde49681f784127a31d97e7b792eed0
+msgid "The 'Tag' is the VLAN tag that the traffic is sent to the next hop with, so set it accordingly. If you are passing 'Untagged' traffic from CloudStack to your next hop, leave it blank. If you want to pass tagged traffic from CloudStack, specify the tag."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:248
+# 579804e4cdd9464eb30e3ff2621fb8a1
+msgid "Select 'default' from the 'Config > Virtual Router' drop-down (assuming that is what your virtual router is called)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:251
+# 3a5160b4f5c042c6b940642fa2b05b2c
+msgid "Click the 'IPv4' tab"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:253
+# 84bf732b36934a829114ed49a2742f17
+msgid "Select 'Static' from the 'Type' radio options"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:255
+# 5870dee962e9418d9d87eeacec3d35ad
+msgid "Click 'Add' in the 'IP' section"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:257
+# 5b9f289d72b14be9b4cfa38ef1728f76
+msgid "Enter '172.30.0.254/24' in the new line"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:259
+# a57d0d5ce83540e0a1b3d855b376e6b8
+msgid "The IP can be any IP outside the CloudStack public IP range, but inside the CloudStack public range netmask (it can NOT be the gateway IP)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:262
+# 359215f62863484ba745f8d2e03ce161
+msgid "The subnet defined by the CIDR should match the CloudStack public range netmask"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:269
+# c46252e83d114010880044c824b7e57b
+msgid "Commit configuration on the Palo Alto Networks Firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:271
+# 365f937b3fec42aea6aea597efca79fd
+msgid "In order for all the changes we just made to take effect, we need to commit the changes."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:274
+# e5f848bca30e4beba84d97eb6c369c28
+msgid "Click the 'Commit' link in the top right corner of the window"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:276
+# 506c144a4d5e4583b1ac84b1eead3373
+msgid "Click 'OK' in the commit window overlay"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:278
+# c6025e0b37e240a4bbb98c10672afae7
+msgid "Click 'Close' to the resulting commit status window after the commit finishes"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:284
+# 37fa8b13701846cc9138c340b9c5c1c9
+msgid "Setup the Palo Alto Networks Firewall in CloudStack"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:287
+# bf172f38242047e6a97f2181882e672f
+msgid "Add the Palo Alto Networks Firewall as a Service Provider"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:289
+# 937455f6c6d4494680d9216fc506771b
+msgid "Navigate to 'Infrastructure > Zones > ZONE_NAME > Physical Network > NETWORK_NAME (guest) > Configure; Network Service Providers'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:292
+# cf68cff820a249ceb84fe458347aa12b
+msgid "Click on 'Palo Alto' in the list"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:294
+# 46ab280934294383a25c46ec2f79b443
+msgid "Click 'View Devices'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:296
+# 7560d69ce9b843b6bf611c931c0675bb
+msgid "Click 'Add Palo Alto Device'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:298
+# 8956b2ff67f7426190554aae0701fcfa
+msgid "Enter your configuration in the overlay. This example will reflect the details previously used in this guide."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:301
+# 30d5213a36ba4d038e33bd011c545565
+msgid "**IP Address**: (the IP of the Palo Alto Networks Firewall)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:303
+# 521f94e44aa74f7d80c7fa7e161c899e
+msgid "**Username**: (the admin username for the firewall)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:305
+# 8e9ee920bf3e4af9ac7f6b3577fa353d
+msgid "**Password**: (the admin password for the firewall)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:307
+# bb1105db236c4fe2a3565df1a58ce8f1
+msgid "**Type**: Palo Alto Firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:309
+# dc49c3aae7c3461cbd16d505f7fd294b
+msgid "**Public Interface**: ethernet1/1 (use what you setup earlier as the public interface if it is different from my examples)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:312
+# 752d21019c2944548bded6ff17d05189
+msgid "**Private Interface**: ethernet1/2 (use what you setup earlier as the private interface if it is different from my examples)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:315
+# d71bcfebd9824cd59280dfb23f87fc94
+msgid "**Number of Retries**: 2 (the default is fine)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:317
+# 8f1e92bb49df4bf69a4983820930b5b6
+msgid "**Timeout**: 300 (the default is fine)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:319
+# ac1090afc1b14b8a9dd41ebfe6fd059e
+msgid "**Public Network**: untrust (this is the public zone on the firewall and did not need to be configured)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:322
+# 81323dc3b1b5477a84f1f9a0aca02f1d
+msgid "**Private Network**: trust (this is the private zone on the firewall and did not need to be configured)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:325
+# 0587f506923242dba7d30acfa5f444bc
+msgid "**Virtual Router**: default (this is the name of the Virtual Router we setup on the firewall)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:328
+# 64503dfbfc6a4a52a027fb5580d77e45
+msgid "**Palo Alto Threat Profile**: (not required. name of the 'Security Profile Groups' to apply. more details in the 'Additional Features' section)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:332
+# 6a825e2b4acf42e89c8918ec303b4857
+msgid "**Palo Alto Log Profile**: (not required. name of the 'Log Forwarding' profile to apply. more details in the 'Additional Features' section)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:335
+# 096b8832d07e48e49b72747a73f81495
+msgid "**Capacity**: (not required)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:337
+# f58dd37d12ff463a8cf1cf7fd24c6249
+msgid "**Dedicated**: (not required)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:341
+# fffae74d8e664c85be11eaef42463e99
+msgid "Click on 'Palo Alto' in the breadcrumbs to go back one screen."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:343
+# 3eb2449be08d4f88b8175a9fbd1e399a
+msgid "Click on 'Enable Provider' |EnableDisableFeature.png|"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:347
+# f471b4d3e1334984931fdfba6c1e3630
+msgid "Add a Network Service Offering to use the new Provider"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:349
+# 4e9125d7228d4e1d82ac0e317b41a5db
+msgid "There are 6 'Supported Services' that need to be configured in the network service offering for this functionality. They are DHCP, DNS, Firewall, Source NAT, Static NAT and Port Forwarding. For the other settings, there are probably additional configurations which will work, but I will just document a common case."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:355
+# b591b1d771584a438ede97f7071cd655
+msgid "Navigate to 'Service Offerings'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:357
+# 14059062e0634e599485931cf2e0733b
+msgid "In the drop-down at the top, select 'Network Offerings'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:359
+# 2b3a92a7cce44d9792ac52aea4305a79
+msgid "Click 'Add Network Offering'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:361
+# 6b9a36687b1c429aa2bedbe8afb2a16c
+msgid "**Name**: (name it whatever you want)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:363
+# 3dd061afb48b49d5828e2ffafa973281
+msgid "**Description**: (again, can be whatever you want)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:365
+# 49f121a90bb6407484225354829e4f76
+msgid "**Guest Type**: Isolated"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:367
+# 3ac932b614024736adfe4404b0994b15
+msgid "**Supported Services**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:369
+# 5326f2fa7c3046859d71e526cbb378d3
+msgid "**DHCP**: Provided by 'VirtualRouter'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:371
+# 8380eb62feed49cf9defb0c46d0d965a
+msgid "**DNS**: Provided by 'VirtualRouter'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:373
+# c1a7cc369b54411b886e9cf936f96da2
+msgid "**Firewall**: Provided by 'PaloAlto'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:375
+# 2c93d4effcc3444b8ab2c3da1933602d
+msgid "**Source NAT**: Provided by 'PaloAlto'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:377
+# 4279d687aefd4657a9a25f5a81681496
+msgid "**Static NAT**: Provided by 'PaloAlto'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:379
+# 629dfab5c1dc40cc99930ae86c10df50
+msgid "**Port Forwarding**: Provided by 'PaloAlto'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:381
+# 7d48d89ad530444db29511d673a7df5e
+msgid "**System Offering for Router**: System Offering For Software Router"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:383
+# 5ea8ba9b5eab4284ae26af32a837796e
+msgid "**Supported Source NAT Type**: Per account (this is the only supported option)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:386
+# c1ce203c827e446d855abb79dc033d31
+msgid "**Default egress policy**: (both 'Allow' and 'Deny' are supported)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:390
+# 1e2fa21b7c18491d943e71b38a893339
+msgid "Click on the newly created service offering"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:392
+# ded26656c3714a89969c20ed0145aeca
+msgid "Click 'Enable network offering' |EnableDisableFeature.png|"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:394
+# 961c14735e81493e85f84b384a2cf059
+msgid "When adding networks in CloudStack, select this network offering to use the Palo Alto Networks firewall."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:399
+# 625a28d178864aeba73bb243f68af405
+msgid "Additional Features"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:401
+# 966abd9906d540eeb3992080bfa4e79b
+msgid "In addition to the standard functionality exposed by CloudStack, we have added a couple additional features to this implementation. We did not add any new screens to CloudStack, but we have added a couple fields to the 'Add Palo Alto Service Provider' screen which will add functionality globally for the device."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:408
+# a0955c0b218e4ead9953db5f3e933ebc
+msgid "Palo Alto Networks Threat Profile"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:410
+# b56617dd1b7a49439204d45bd3ddc540
+msgid "This feature allows you to specify a 'Security Profile Group' to be applied to all of the firewall rules which are created on the Palo Alto Networks firewall device."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:414
+# ddf43faad14a41deb2f807650433579e
+msgid "To create a 'Security Profile Group' on the Palo Alto Networks firewall, do the following:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:417
+#: ../../networking/palo_alto_config.rst:446
+# a77eb7c4a55b45db96ba922310c92a31
+# 401e0ddfb24441f3a01f0406fed5ea8c
+msgid "Log into the Palo Alto Networks firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:419
+# d1cffa0eb5b84c4fac78345a6a1eac14
+msgid "Navigate to 'Objects > Security Profile Groups'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:421
+# d8a2cff026f443e48ddc23e758c6b433
+msgid "Click 'Add' at the bottom of the page to add a new group"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:423
+# 2260b8c3d00f4fb48409751005878ea3
+msgid "Give the group a Name and specify the profiles you would like to include in the group"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:428
+#: ../../networking/palo_alto_config.rst:457
+# 71409d6bba4e4cefb293a3a2adb62a58
+# b0ff6a165cf648f59bb775cb80b7bae8
+msgid "Click the 'Commit' link in the top right of the screen and follow the on screen instructions"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:431
+# 39f6f68e96514eb687aee18212a17720
+msgid "Once you have created a profile, you can reference it by Name in the 'Palo Alto Threat Profile' field in the 'Add the Palo Alto Networks Firewall as a Service Provider' step."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:437
+# 19e3020b2cb741dcbeaf2757b1c46b0e
+msgid "Palo Alto Networks Log Forwarding Profile"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:439
+# 8e702ba47eb14d06953df77990976d35
+msgid "This feature allows you to specify a 'Log Forwarding' profile to better manage where the firewall logs are sent to. This is helpful for keeping track of issues that can arise on the firewall."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:443
+# a924dcc217f44a8d9ea1bf038038cc48
+msgid "To create a 'Log Forwarding' profile on the Palo Alto Networks Firewall, do the following:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:448
+# ae0e76d3eff94c3aae3e4b2c7d55b745
+msgid "Navigate to 'Objects > Log Forwarding'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:450
+# 2568e7109c7a4034872602eaf73fc171
+msgid "Click 'Add' at the bottom of the page to add a new profile"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:452
+# b3e2a50453874aa591e0592eea54a974
+msgid "Give the profile a Name and specify the details you want for the traffic and threat settings"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:460
+# 15fa6db47be1443fa69fb555db7583b7
+msgid "Once you have created a profile, you can reference it by Name in the 'Palo Alto Log Profile' field in the 'Add the Palo Alto Networks Firewall as a Service Provider' step."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:469
+# 5d10eda1d77e4cdcaef70d1cded35c75
+msgid "The implementation currently only supports a single public IP range in CloudStack"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:472
+# 01f1108e82134be5bf3daf49f3d331ea
+msgid "Usage tracking is not yet implemented"
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/projects.pot b/source/adminguide/locale/pot/projects.pot
new file mode 100644
index 0000000..e29ee05
--- /dev/null
+++ b/source/adminguide/locale/pot/projects.pot
@@ -0,0 +1,600 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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"
+
+#: ../../projects.rst:18
+# 4b4ac9e9d63047e88707cfbcf936a425
+msgid "Using Projects to Organize Users and Resources"
+msgstr ""
+
+#: ../../projects.rst:21
+# dd53e71c97984e29944fd5f92845fc70
+msgid "Overview of Projects"
+msgstr ""
+
+#: ../../projects.rst:23
+# 9ad708c803064abcbaa0ba5c9d5efe55
+msgid "Projects are used to organize people and resources. CloudStack users within a single domain can group themselves into project teams so they can collaborate and share virtual resources such as VMs, snapshots, templates, data disks, and IP addresses. CloudStack tracks resource usage per project as well as per user, so the usage can be billed to either a user account or a project. For example, a private cloud within a software company might have all members of the QA department assigned to one project, so the company can track the resources used in testing while the project members can more easily isolate their efforts from other users of the same cloud"
+msgstr ""
+
+#: ../../projects.rst:34
+# df157ec524304800a9ced5d428bd234c
+msgid "You can configure CloudStack to allow any user to create a new project, or you can restrict that ability to just CloudStack administrators. Once you have created a project, you become that project’s administrator, and you can add others within your domain to the project. CloudStack can be set up either so that you can add people directly to a project, or so that you have to send an invitation which the recipient must accept. Project members can view and manage all virtual resources created by anyone in the project (for example, share VMs). A user can be a member of any number of projects and can switch views in the CloudStack UI to show only project-related information, such as project VMs, fellow project members, project-related alerts, and so on."
+msgstr ""
+
+#: ../../projects.rst:46
+# d29f7ae31802463281f05dac9610d8d2
+msgid "The project administrator can pass on the role to another project member. The project administrator can also add more members, remove members from the project, set new resource limits (as long as they are below the global defaults set by the CloudStack administrator), and delete the project. When the administrator removes a member from the project, resources created by that user, such as VM instances, remain with the project. This brings us to the subject of resource ownership and which resources can be used by a project."
+msgstr ""
+
+#: ../../projects.rst:55
+# dde002b5830f493b94778605a4014583
+msgid "Resources created within a project are owned by the project, not by any particular CloudStack account, and they can be used only within the project. A user who belongs to one or more projects can still create resources outside of those projects, and those resources belong to the user’s account; they will not be counted against the project’s usage or resource limits. You can create project-level networks to isolate traffic within the project and provide network services such as port forwarding, load balancing, VPN, and static NAT. A project can also make use of certain types of resources from outside the project, if those resources are shared. For example, a shared network or public template is available to any project in the domain. A project can get access to a private template if the template’s owner will grant permission. A project can use any service offering or disk offering available in its domain; however, you can not create private service and disk offerings at the project level.."
+msgstr ""
+
+#: ../../projects.rst:73
+# 847217dcf84349fc9c5c719bfde3ec7f
+msgid "Configuring Projects"
+msgstr ""
+
+#: ../../projects.rst:75
+# 8a115b7683d3463087791eaed5a40d85
+msgid "Before CloudStack users start using projects, the CloudStack administrator must set up various systems to support them, including membership invitations, limits on project resources, and controls on who can create projects."
+msgstr ""
+
+#: ../../projects.rst:82
+# 327e0569d0c44de5b93b9f7e446920cc
+msgid "Setting Up Invitations"
+msgstr ""
+
+#: ../../projects.rst:84
+# 3e242eb556ee478cb2f58ad9f6d5ce85
+msgid "CloudStack can be set up either so that project administrators can add people directly to a project, or so that it is necessary to send an invitation which the recipient must accept. The invitation can be sent by email or through the user’s CloudStack account. If you want administrators to use invitations to add members to projects, turn on and set up the invitations feature in CloudStack."
+msgstr ""
+
+#: ../../projects.rst:91
+#: ../../projects.rst:158
+#: ../../projects.rst:177
+#: ../../projects.rst:214
+#: ../../projects.rst:242
+# 8e48e6338f444e73898549bf0932c731
+# 2309d4b19c6d404181b591f4f6d205fc
+# 2e84d8cc479e4cf0af43cd20e4fa190b
+# ccfea269215f463d9fe35998c9494c53
+# 8c0130530bbe4c28b429436a6d8e61c9
+msgid "Log in as administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../projects.rst:93
+#: ../../projects.rst:179
+#: ../../projects.rst:216
+# e539c47bc6254e2c8a1382c03574a8c0
+# c7df097745ac41e1ab3b12f5ede84582
+# 989f33da3208451a8bcb145c25a7d1c9
+msgid "In the left navigation, click Global Settings."
+msgstr ""
+
+#: ../../projects.rst:95
+# 37e43d6f62be443998cb185f24333cdf
+msgid "In the search box, type project and click the search button. |Searches projects|"
+msgstr ""
+
+#: ../../projects.rst:98
+# e42abfd82e134939b6d5b7d2fed2f4cc
+msgid "In the search results, you can see a few other parameters you need to set to control how invitations behave. The table below shows global configuration parameters related to project invitations. Click the edit button to set each parameter."
+msgstr ""
+
+#: ../../projects.rst:104
+# 9a803ec0fbce49a1bfcbdcb1961d9fe9
+msgid "Configuration Parameters"
+msgstr ""
+
+#: ../../projects.rst:104
+# 2eb9f6fe8d7148b99a39f5ba5c0b8acf
+msgid "Description"
+msgstr ""
+
+#: ../../projects.rst:106
+# 8f015394c22643a89189371d0708f414
+msgid "project.invite.required"
+msgstr ""
+
+#: ../../projects.rst:106
+# 3f3e2860eff34ffaad4d84f57b53f46d
+msgid "Set to true to turn on the invitations feature."
+msgstr ""
+
+#: ../../projects.rst:108
+# c3dd124564eb4178a6f272ed89393757
+msgid "project.email.sender"
+msgstr ""
+
+#: ../../projects.rst:108
+# 1c83afe8caa5414181a01e7c8e31627f
+msgid "The email address to show in the From field of invitation emails."
+msgstr ""
+
+#: ../../projects.rst:110
+# 31cb407a37cc40c79b6cdb1c8171c153
+msgid "project.invite.timeout"
+msgstr ""
+
+#: ../../projects.rst:110
+# 1ff23ba5f3174049a1f067acd434fa47
+msgid "Amount of time to allow for a new member to respond to the invitation."
+msgstr ""
+
+#: ../../projects.rst:112
+# 9daf130db7394b60aae7266b51a04ff6
+msgid "project.smtp.host"
+msgstr ""
+
+#: ../../projects.rst:112
+# dd464c374e9049c4995f6ea455014f6a
+msgid "Name of the host that acts as an email server to handle invitations."
+msgstr ""
+
+#: ../../projects.rst:114
+# 89967c84b58c4a69af3b1718861da2b1
+msgid "project.smtp.password"
+msgstr ""
+
+#: ../../projects.rst:114
+# 1815f51cddd147efb8c9cd0bf2fb66dd
+msgid "(Optional) Password required by the SMTP server. You must also set project.smtp.username and set project.smtp.useAuth to true."
+msgstr ""
+
+#: ../../projects.rst:116
+# bb3f4cd97d8c4c5881aaded19029f405
+msgid "project.smtp.port"
+msgstr ""
+
+#: ../../projects.rst:116
+# 30ad11730ae14fc5a8a26e34a244704d
+msgid "SMTP server’s listening port."
+msgstr ""
+
+#: ../../projects.rst:118
+# 1e41abde08fb4385ad49ccdd91e5d856
+msgid "project.smtp.useAuth"
+msgstr ""
+
+#: ../../projects.rst:118
+# 41fc2bf9b98d4dd7af52e18e21334a4a
+msgid "Set to true if the SMTP server requires a username and password."
+msgstr ""
+
+#: ../../projects.rst:120
+# d22498c945d14f65bd0892d1a3bbb4ab
+msgid "project.smtp.username"
+msgstr ""
+
+#: ../../projects.rst:120
+# a025e0ccc7b641c8b1c1c18d0884a7e8
+msgid "(Optional) User name required by the SMTP server for authentication. You must also set project.smtp.password and set project.smtp.useAuth to true.."
+msgstr ""
+
+#: ../../projects.rst:123
+# 5a399b5498814feb8d1d90ac249c0f06
+msgid "Restart the Management Server:"
+msgstr ""
+
+#: ../../projects.rst:130
+# cc25b73903da4b3eb00ef5dca983a9b6
+msgid "Setting Resource Limits for Projects"
+msgstr ""
+
+#: ../../projects.rst:132
+# 4554a70f1086483a8feea5f0c15eafd0
+msgid "The CloudStack administrator can set global default limits to control the amount of resources that can be owned by each project in the cloud. This serves to prevent uncontrolled usage of resources such as snapshots, IP addresses, and virtual machine instances. Domain administrators can override these resource limits for individual projects with their domains, as long as the new limits are below the global defaults set by the CloudStack root administrator. The root administrator can also set lower resource limits for any project in the cloud"
+msgstr ""
+
+#: ../../projects.rst:143
+# 87c2e78e1e344c2fa0e550443ff641e3
+msgid "Setting Per-Project Resource Limits"
+msgstr ""
+
+#: ../../projects.rst:145
+# 7e81041e8a9147bd84fde49f3f569465
+msgid "The CloudStack root administrator or the domain administrator of the domain where the project resides can set new resource limits for an individual project. The project owner can set resource limits only if the owner is also a domain or root administrator."
+msgstr ""
+
+#: ../../projects.rst:150
+# 47029644eddd41d1b4647b5332d9c061
+msgid "The new limits must be below the global default limits set by the CloudStack administrator (as described in `“Setting Resource Limits for Projects” <#setting-resource-limits-for-projects>`_). If the project already owns more of a given type of resource than the new maximum, the resources are not affected; however, the project can not add any new resources of that type until the total drops below the new limit."
+msgstr ""
+
+#: ../../projects.rst:160
+#: ../../projects.rst:244
+#: ../../projects.rst:284
+#: ../../projects.rst:328
+#: ../../projects.rst:350
+#: ../../projects.rst:380
+# f22a47ab0c5948e6b1e37d8a2ea696c9
+# e197ae8d631c487694852e4f6de2552f
+# befd6ea180404a3bb8cc85b535ec7a84
+# c2260b29d8b94395b2be966c4a99333d
+# 322b7293e93f44dcb5b9d2b201132963
+# 9f3d412110854b50a846dbdbcf15d67a
+msgid "In the left navigation, click Projects."
+msgstr ""
+
+#: ../../projects.rst:162
+#: ../../projects.rst:286
+#: ../../projects.rst:330
+#: ../../projects.rst:382
+# 028c250e7e6144e2a78bcb28aeb20c20
+# 2eb7b64a81f44d6381ff74cb4876454f
+# ced1ffd77bfc4a769d87a1e02b4f605b
+# c52047f8f2064bb2a2e81d5aa52a4c86
+msgid "In Select View, choose Projects."
+msgstr ""
+
+#: ../../projects.rst:164
+#: ../../projects.rst:288
+#: ../../projects.rst:332
+# af4be7e8b89f4da08c1391967263e362
+# dc1fc36ced6d4c48984c0a599e2893ba
+# 79ab804df9234bd0af6b4f89d1b545b5
+msgid "Click the name of the project you want to work with."
+msgstr ""
+
+#: ../../projects.rst:166
+# 5e274b4f574149edaa1899709a04a1d3
+msgid "Click the Resources tab. This tab lists the current maximum amount that the project is allowed to own for each type of resource."
+msgstr ""
+
+#: ../../projects.rst:169
+# b0861fc478514256ad0ca41e6184ba3a
+msgid "Type new values for one or more resources."
+msgstr ""
+
+#: ../../projects.rst:171
+# 363f4b7e52b04d4ba5bf081c3c51dc8a
+msgid "Click Apply."
+msgstr ""
+
+#: ../../projects.rst:175
+# 7263280c84454f05be8680c02efbd4c3
+msgid "Setting the Global Project Resource Limits"
+msgstr ""
+
+#: ../../projects.rst:181
+# 81a908897f4d4aacb979288d14e8f4ad
+msgid "In the search box, type max.projects and click the search button."
+msgstr ""
+
+#: ../../projects.rst:183
+# 7a132176784548a1bb80edb054b486b9
+msgid "In the search results, you will see the parameters you can use to set per-project maximum resource amounts that apply to all projects in the cloud. No project can have more resources, but an individual project can have lower limits. Click the edit button to set each parameter. |Edits parameters|"
+msgstr ""
+
+#: ../../projects.rst:190
+# 241b29e357a047dc890813c8021b8bfa
+msgid "max.project.public.ips"
+msgstr ""
+
+#: ../../projects.rst:190
+# ca118c2a5e6d41b0ae029c8780d99883
+msgid "Maximum number of public IP addresses that can be owned by any project in the cloud. See About Public IP Addresses."
+msgstr ""
+
+#: ../../projects.rst:192
+# 2c1e0ade7edc46ff97ef948312221adb
+msgid "max.project.snapshots"
+msgstr ""
+
+#: ../../projects.rst:192
+# a809d74e8e264f2f8544e96dacf33d1a
+msgid "Maximum number of snapshots that can be owned by any project in the cloud. See Working with Snapshots."
+msgstr ""
+
+#: ../../projects.rst:194
+# 977134a911f844f98a39206991e01c12
+msgid "max.project.templates"
+msgstr ""
+
+#: ../../projects.rst:194
+# 44dcf66c930a42869b7601e0250466ac
+msgid "Maximum number of templates that can be owned by any project in the cloud. See Working with Templates."
+msgstr ""
+
+#: ../../projects.rst:196
+# 9007c476909543678660480c9c5cca8e
+msgid "max.project.uservms"
+msgstr ""
+
+#: ../../projects.rst:196
+# fa7756a39a51499aa79542f6a9aebd0a
+msgid "Maximum number of guest virtual machines that can be owned by any project in the cloud. See Working With Virtual Machines."
+msgstr ""
+
+#: ../../projects.rst:198
+# 4bd44963b3c84bd09612d0c16cb2b21f
+msgid "max.project.volumes"
+msgstr ""
+
+#: ../../projects.rst:198
+# b684120b36d54144b7d6bfd1b9cb26fd
+msgid "Maximum number of data volumes that can be owned by any project in the cloud. See Working with Volumes."
+msgstr ""
+
+#: ../../projects.rst:202
+#: ../../projects.rst:228
+# 0a08e573ccff40ed964877c1e0a25422
+# 30bf816d7d164ebc9a3527bb06dcd0f5
+msgid "Restart the Management Server."
+msgstr ""
+
+#: ../../projects.rst:209
+# 7a9e7b11d9204da7b5e4ae5b0cad6e15
+msgid "Setting Project Creator Permissions"
+msgstr ""
+
+#: ../../projects.rst:211
+# c9583a67341f459c94f3aa76485a5fd8
+msgid "You can configure CloudStack to allow any user to create a new project, or you can restrict that ability to just CloudStack administrators."
+msgstr ""
+
+#: ../../projects.rst:218
+# 0c5d1047bef445548c0c40109d391eca
+msgid "In the search box, type allow.user.create.projects."
+msgstr ""
+
+#: ../../projects.rst:220
+# 44b11d9aac27438eb4bfa70d31759c86
+msgid "Click the edit button to set the parameter. |Edits parameters|"
+msgstr ""
+
+#: ../../projects.rst:222
+# fb277fa119e0496885f889a3ae48d1e7
+msgid "``allow.user.create.projects``"
+msgstr ""
+
+#: ../../projects.rst:224
+# 9cdac884b4f1482599019f9178759604
+msgid "Set to true to allow end users to create projects. Set to false if you want only the CloudStack root administrator and domain administrators to create projects."
+msgstr ""
+
+#: ../../projects.rst:236
+# c36ba31002c74ec98d2dcdec7bd9374e
+msgid "Creating a New Project"
+msgstr ""
+
+#: ../../projects.rst:238
+# 6b62d8460a034f809371e1886bd34e80
+msgid "CloudStack administrators and domain administrators can create projects. If the global configuration parameter allow.user.create.projects is set to true, end users can also create projects."
+msgstr ""
+
+#: ../../projects.rst:246
+# 4a302cfc6cb34ba5baf6615abcae28ec
+msgid "In Select view, click Projects."
+msgstr ""
+
+#: ../../projects.rst:248
+# 520e75eebfb24c338a07edbd8119b8b8
+msgid "Click New Project."
+msgstr ""
+
+#: ../../projects.rst:250
+# 42a42b0b1bb24125b530a8fb28a3b31a
+msgid "Give the project a name and description for display to users, then click Create Project."
+msgstr ""
+
+#: ../../projects.rst:253
+# 2c2486f0447d4f138b5e1c0e8ceace41
+msgid "A screen appears where you can immediately add more members to the project. This is optional. Click Next when you are ready to move on."
+msgstr ""
+
+#: ../../projects.rst:256
+# 2bc3c862668e44e78c5ec777dc974839
+msgid "Click Save."
+msgstr ""
+
+#: ../../projects.rst:260
+# 986f0cb8853a42738eabaab830e43267
+msgid "Adding Members to a Project"
+msgstr ""
+
+#: ../../projects.rst:262
+# 50647c0e69974fbba211aabef3bcda09
+msgid "New members can be added to a project by the project’s administrator, the domain administrator of the domain where the project resides or any parent domain, or the CloudStack root administrator. There are two ways to add members in CloudStack, but only one way is enabled at a time:"
+msgstr ""
+
+#: ../../projects.rst:267
+# ef81123f6c0e4fc3b1c2521f4324fc93
+msgid "If invitations have been enabled, you can send invitations to new members."
+msgstr ""
+
+#: ../../projects.rst:270
+# f7125c407042411f8a4f35feff955784
+msgid "If invitations are not enabled, you can add members directly through the UI."
+msgstr ""
+
+#: ../../projects.rst:275
+# a4433f30587f4374807fa615b7d326cb
+msgid "Sending Project Membership Invitations"
+msgstr ""
+
+#: ../../projects.rst:277
+# 4417ea897e4e418caf7f9050b019b36e
+msgid "Use these steps to add a new member to a project if the invitations feature is enabled in the cloud as described in `“Setting Up Invitations” <#setting-up-invitations>`_. If the invitations feature is not turned on, use the procedure in Adding Project Members From the UI."
+msgstr ""
+
+#: ../../projects.rst:282
+#: ../../projects.rst:326
+#: ../../projects.rst:348
+#: ../../projects.rst:378
+#: ../../projects.rst:402
+# b67c9d2fbb734979be7d9a0b06c83e07
+# 09c3e88bd9394c8ebecf83e40f6dfef9
+# 2b65ac18e6e14d988ed9d105965093b3
+# 0f9433a953604a24aaa3936b6304ff37
+# aaabf61386aa4e90a83121dd76c55ca6
+msgid "Log in to the CloudStack UI."
+msgstr ""
+
+#: ../../projects.rst:290
+# 6848798224324e658909d941615e3c71
+msgid "Click the Invitations tab."
+msgstr ""
+
+#: ../../projects.rst:292
+# 49786f4671bb4afbb13144fb5cdb22de
+msgid "In Add by, select one of the following:"
+msgstr ""
+
+#: ../../projects.rst:294
+# 00420a7de6a943b5bea54e2930363c7b
+msgid "Account – The invitation will appear in the user’s Invitations tab in the Project View. See Using the Project View."
+msgstr ""
+
+#: ../../projects.rst:297
+# 23674aa094d8476181833f1077c82ce9
+msgid "Email – The invitation will be sent to the user’s email address. Each emailed invitation includes a unique code called a token which the recipient will provide back to CloudStack when accepting the invitation. Email invitations will work only if the global parameters related to the SMTP server have been set. See `“Setting Up Invitations” <#setting-up-invitations>`_."
+msgstr ""
+
+#: ../../projects.rst:304
+# 98b4ad1148b94b9ba8e815a3ce4214a8
+msgid "Type the user name or email address of the new member you want to add, and click Invite. Type the CloudStack user name if you chose Account in the previous step. If you chose Email, type the email address. You can invite only people who have an account in this cloud within the same domain as the project. However, you can send the invitation to any email address."
+msgstr ""
+
+#: ../../projects.rst:311
+# 9a6d6ea948754921bbc259b87b29ba60
+msgid "To view and manage the invitations you have sent, return to this tab. When an invitation is accepted, the new member will appear in the project’s Accounts tab."
+msgstr ""
+
+#: ../../projects.rst:317
+# 2cf29d018a2c48a79262e2f02cd30162
+msgid "Adding Project Members From the UI"
+msgstr ""
+
+#: ../../projects.rst:319
+# fdbf78a90732473689bcedc64864415d
+msgid "The steps below tell how to add a new member to a project if the invitations feature is not enabled in the cloud. If the invitations feature is enabled cloud,as described in `“Setting Up Invitations” <#setting-up-invitations>`_, use the procedure in `“Sending Project Membership Invitations” <#sending-project-membership-invitations>`_."
+msgstr ""
+
+#: ../../projects.rst:334
+# 069a956c95384174a82d2d0302f3dfd7
+msgid "Click the Accounts tab. The current members of the project are listed."
+msgstr ""
+
+#: ../../projects.rst:337
+# 7654413243e545579270bc7c8b813727
+msgid "Type the account name of the new member you want to add, and click Add Account. You can add only people who have an account in this cloud and within the same domain as the project."
+msgstr ""
+
+#: ../../projects.rst:343
+# 774bd03942ea4a3ab9023bb4f72b627b
+msgid "Accepting a Membership Invitation"
+msgstr ""
+
+#: ../../projects.rst:345
+# 462eace7144340bc8bc65c06d8056b5d
+msgid "If you have received an invitation to join a CloudStack project, and you want to accept the invitation, follow these steps:"
+msgstr ""
+
+#: ../../projects.rst:352
+# 0196721635cc470094d28372774afeac
+msgid "In Select View, choose Invitations."
+msgstr ""
+
+#: ../../projects.rst:354
+# f5c8ed37ac54486f8d3f20f9129936a9
+msgid "If you see the invitation listed onscreen, click the Accept button."
+msgstr ""
+
+#: ../../projects.rst:356
+# f33506966c894c8eb0f91c35c2d506ee
+msgid "Invitations listed on screen were sent to you using your CloudStack account name."
+msgstr ""
+
+#: ../../projects.rst:359
+# 67733042a89a4b969d73efc5f2fa6e94
+msgid "If you received an email invitation, click the Enter Token button, and provide the project ID and unique ID code (token) from the email."
+msgstr ""
+
+#: ../../projects.rst:364
+# c33bd4e1071f4d9dab4b1d9a3be3f052
+msgid "Suspending or Deleting a Project"
+msgstr ""
+
+#: ../../projects.rst:366
+# b401169d94da465097ecd686cf60ced2
+msgid "When a project is suspended, it retains the resources it owns, but they can no longer be used. No new resources or members can be added to a suspended project."
+msgstr ""
+
+#: ../../projects.rst:370
+# d08b758fd1754360a7334fa51c6067cf
+msgid "When a project is deleted, its resources are destroyed, and member accounts are removed from the project. The project’s status is shown as Disabled pending final deletion."
+msgstr ""
+
+#: ../../projects.rst:374
+# 400db324f49c472881028c92fb1082c8
+msgid "A project can be suspended or deleted by the project administrator, the domain administrator of the domain the project belongs to or of its parent domain, or the CloudStack root administrator."
+msgstr ""
+
+#: ../../projects.rst:384
+# d8a96b11443d49109477879ebdf4e6c1
+msgid "Click the name of the project."
+msgstr ""
+
+#: ../../projects.rst:386
+# 6c5f88a0ad7443cdb4f778b9d3d8da58
+msgid "Click one of the buttons:"
+msgstr ""
+
+#: ../../projects.rst:388
+# 29804834398d400d9518f86f6aadc9ca
+msgid "To delete, use |Removes a project|"
+msgstr ""
+
+#: ../../projects.rst:390
+# 41920e56886b48dbb25f86128a21a0c2
+msgid "To suspend, use |Suspends a project|"
+msgstr ""
+
+#: ../../projects.rst:394
+# fe947634ec70449bb7e58adb8700e805
+msgid "Using the Project View"
+msgstr ""
+
+#: ../../projects.rst:396
+# b2b759558262491e98fb0636eae9bd35
+msgid "If you are a member of a project, you can use CloudStack’s project view to see project members, resources consumed, and more. The project view shows only information related to one project. It is a useful way to filter out other information so you can concentrate on a project status and resources."
+msgstr ""
+
+#: ../../projects.rst:404
+# b2d475dcc43b441da5592c11733cec95
+msgid "Click Project View."
+msgstr ""
+
+#: ../../projects.rst:406
+# 697e02ba1d754fab8d93b30aa2692085
+msgid "The project dashboard appears, showing the project’s VMs, volumes, users, events, network settings, and more. From the dashboard, you can:"
+msgstr ""
+
+#: ../../projects.rst:410
+# 0439e9369d664d92be0b7b1fdb1ca88f
+msgid "Click the Accounts tab to view and manage project members. If you are the project administrator, you can add new members, remove members, or change the role of a member from user to admin. Only one member at a time can have the admin role, so if you set another user’s role to admin, your role will change to regular user."
+msgstr ""
+
+#: ../../projects.rst:417
+# cfe2dfd46e014224a3ec791add73746c
+msgid "(If invitations are enabled) Click the Invitations tab to view and manage invitations that have been sent to new project members but not yet accepted. Pending invitations will remain in this list until the new member accepts, the invitation timeout is reached, or you cancel the invitation."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/reliability.pot b/source/adminguide/locale/pot/reliability.pot
new file mode 100644
index 0000000..74a2341
--- /dev/null
+++ b/source/adminguide/locale/pot/reliability.pot
@@ -0,0 +1,368 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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"
+
+#: ../../reliability.rst:18
+# 87e0763c1e254b4d865a6575d53cd476
+msgid "System Reliability and High Availability"
+msgstr ""
+
+#: ../../reliability.rst:21
+# c2cb2128aadc481d823ace426cd60607
+msgid "HA for Management Server"
+msgstr ""
+
+#: ../../reliability.rst:23
+# 2cf0c6cbde074e988216174d32a34366
+msgid "The CloudStack Management Server should be deployed in a multi-node configuration such that it is not susceptible to individual server failures. The Management Server itself (as distinct from the MySQL database) is stateless and may be placed behind a load balancer."
+msgstr ""
+
+#: ../../reliability.rst:28
+# 0fa3d9ec6d144621b71b2a0077137930
+msgid "Normal operation of Hosts is not impacted by an outage of all Management Serves. All guest VMs will continue to work."
+msgstr ""
+
+#: ../../reliability.rst:31
+# 161abac9b6d7470bbf7a984e225c9a6d
+msgid "When the Management Server is down, no new VMs can be created, and the end user and admin UI, API, dynamic load distribution, and HA will cease to work."
+msgstr ""
+
+#: ../../reliability.rst:37
+# c2abacc0b20149d5b7a4683aedfe4f32
+msgid "Management Server Load Balancing"
+msgstr ""
+
+#: ../../reliability.rst:39
+# 0dc6eb435a354cf3b4279772461cbf7f
+msgid "CloudStack can use a load balancer to provide a virtual IP for multiple Management Servers. The administrator is responsible for creating the load balancer rules for the Management Servers. The application requires persistence or stickiness across multiple sessions. The following chart lists the ports that should be load balanced and whether or not persistence is required."
+msgstr ""
+
+#: ../../reliability.rst:46
+# c998c6decbb94666aa6b7c6191a0f4ce
+msgid "Even if persistence is not required, enabling it is permitted."
+msgstr ""
+
+#: ../../reliability.rst:49
+# fa7858c33d194002ade885780b974057
+msgid "Source Port"
+msgstr ""
+
+#: ../../reliability.rst:49
+# 8e4749c413de4b28a281ada8d2d64112
+msgid "Destination Port"
+msgstr ""
+
+#: ../../reliability.rst:49
+# 044f0a55ef9143028e6a1442c2d75ee4
+msgid "Protocol"
+msgstr ""
+
+#: ../../reliability.rst:49
+# 50fdab6c4d254b51be652286846ebac8
+msgid "Persistence Required?"
+msgstr ""
+
+#: ../../reliability.rst:51
+# f5fcf842916f48bba5a1ef7630fe9998
+msgid "80 or 443"
+msgstr ""
+
+#: ../../reliability.rst:51
+# 3a276b78a619418392895c04f2b8e5f0
+msgid "8080 (or 20400 with AJP)"
+msgstr ""
+
+#: ../../reliability.rst:51
+# d09ff40864724d449227f282f2c255b4
+msgid "HTTP (or AJP)"
+msgstr ""
+
+#: ../../reliability.rst:51
+#: ../../reliability.rst:52
+# 10b0e96112a54a5b92b53ee2ad9bf186
+# fb100cffa01e43e2b2b5880237a41528
+msgid "Yes"
+msgstr ""
+
+#: ../../reliability.rst:52
+#: ../../reliability.rst:52
+# f3007601ae444c0796d25c5e58d09d7a
+# 1393fb040df84ca781d1000f40e4794a
+msgid "8250"
+msgstr ""
+
+#: ../../reliability.rst:52
+# 6443f2a5e1d840699fd47b726ff379f9
+msgid "TCP"
+msgstr ""
+
+#: ../../reliability.rst:53
+#: ../../reliability.rst:53
+# 1e51ee3a6cd14a0a954cce617a60c19d
+# a50ea41d89cf476eadb2a4ad960c9c6a
+msgid "8096"
+msgstr ""
+
+#: ../../reliability.rst:53
+# c2b280074d6f40d685182ce0770b0146
+msgid "HTTP"
+msgstr ""
+
+#: ../../reliability.rst:53
+# 759f4cdc678a4b149c52cf0e39205f9c
+msgid "No"
+msgstr ""
+
+#: ../../reliability.rst:56
+# a6f72463a9f44a83992ea95a6ca2d121
+msgid "In addition to above settings, the administrator is responsible for setting the 'host' global config value from the management server IP to load balancer virtual IP address. If the 'host' value is not set to the VIP for Port 8250 and one of your management servers crashes, the UI is still available but the system VMs will not be able to contact the management server."
+msgstr ""
+
+#: ../../reliability.rst:65
+# 4ea4aac15f0649b9a4ec0335de47dde1
+msgid "HA-Enabled Virtual Machines"
+msgstr ""
+
+#: ../../reliability.rst:67
+#: ../../reliability.rst:84
+# c3b807bd9019482093758c219005a8af
+# 15a6c6ff487d4b4ab6f7088de5c25301
+msgid "The user can specify a virtual machine as HA-enabled. By default, all virtual router VMs and Elastic Load Balancing VMs are automatically configured as HA-enabled. When an HA-enabled VM crashes, CloudStack detects the crash and restarts the VM automatically within the same Availability Zone. HA is never performed across different Availability Zones. CloudStack has a conservative policy towards restarting VMs and ensures that there will never be two instances of the same VM running at the same time. The Management Server attempts to start the VM on another Host in the same cluster."
+msgstr ""
+
+#: ../../reliability.rst:77
+#: ../../reliability.rst:94
+# 07861c848b9c4db19a1648e1e80cfabd
+# 69462f0a341c4b64a73b9f2e6a9dbb2d
+msgid "HA features work with iSCSI or NFS primary storage. HA with local storage is not supported."
+msgstr ""
+
+#: ../../reliability.rst:82
+# d6b616e863194085b6c28e537822b4b0
+msgid "HA for Hosts"
+msgstr ""
+
+#: ../../reliability.rst:99
+# 00c672182ced409dbf9628273c7e72cc
+msgid "Dedicated HA Hosts"
+msgstr ""
+
+#: ../../reliability.rst:101
+# d615a157c03a46f8a4185819e7d53f6a
+msgid "One or more hosts can be designated for use only by HA-enabled VMs that are restarting due to a host failure. Setting up a pool of such dedicated HA hosts as the recovery destination for all HA-enabled VMs is useful to:"
+msgstr ""
+
+#: ../../reliability.rst:106
+# 3b2ac4cb2fd24384adc49f8f6de78d12
+msgid "Make it easier to determine which VMs have been restarted as part of the CloudStack high-availability function. If a VM is running on a dedicated HA host, then it must be an HA-enabled VM whose original host failed. (With one exception: It is possible for an administrator to manually migrate any VM to a dedicated HA host.)."
+msgstr ""
+
+#: ../../reliability.rst:112
+# 2814f71a4772417494be794e95ed6189
+msgid "Keep HA-enabled VMs from restarting on hosts which may be reserved for other purposes."
+msgstr ""
+
+#: ../../reliability.rst:115
+# f29ad59410ba484d81a40d3ab33cfb75
+msgid "The dedicated HA option is set through a special host tag when the host is created. To allow the administrator to dedicate hosts to only HA-enabled VMs, set the global configuration variable ha.tag to the desired tag (for example, \"ha\\_host\"), and restart the Management Server. Enter the value in the Host Tags field when adding the host(s) that you want to dedicate to HA-enabled VMs."
+msgstr ""
+
+#: ../../reliability.rst:123
+# d5444df1dd2240bea9615234f1703727
+msgid "If you set ha.tag, be sure to actually use that tag on at least one host in your cloud. If the tag specified in ha.tag is not set for any host in the cloud, the HA-enabled VMs will fail to restart after a crash."
+msgstr ""
+
+#: ../../reliability.rst:130
+# 41dd6b225a02456f873c956ecc4e6018
+msgid "Primary Storage Outage and Data Loss"
+msgstr ""
+
+#: ../../reliability.rst:132
+# 982e58c7dfd644a9a8e0eaf38fbf516a
+msgid "When a primary storage outage occurs the hypervisor immediately stops all VMs stored on that storage device. Guests that are marked for HA will be restarted as soon as practical when the primary storage comes back on line. With NFS, the hypervisor may allow the virtual machines to continue running depending on the nature of the issue. For example, an NFS hang will cause the guest VMs to be suspended until storage connectivity is restored.Primary storage is not designed to be backed up. Individual volumes in primary storage can be backed up using snapshots."
+msgstr ""
+
+#: ../../reliability.rst:144
+# 2d193df58d2c4fcb867416d740fd9657
+msgid "Secondary Storage Outage and Data Loss"
+msgstr ""
+
+#: ../../reliability.rst:146
+# 2d7b3415392e4e8ba762191a40dafa04
+msgid "For a Zone that has only one secondary storage server, a secondary storage outage will have feature level impact to the system but will not impact running guest VMs. It may become impossible to create a VM with the selected template for a user. A user may also not be able to save snapshots or examine/restore saved snapshots. These features will automatically be available when the secondary storage comes back online."
+msgstr ""
+
+#: ../../reliability.rst:153
+# 8cda194548a545c0864b2334b52ac6c1
+msgid "Secondary storage data loss will impact recently added user data including templates, snapshots, and ISO images. Secondary storage should be backed up periodically. Multiple secondary storage servers can be provisioned within each zone to increase the scalability of the system."
+msgstr ""
+
+#: ../../reliability.rst:160
+# 5d6dd861732344e1a4563e92beaf4b89
+msgid "Database High Availability"
+msgstr ""
+
+#: ../../reliability.rst:162
+# 2ab1e8b94c5447719fe99d7a1f876d22
+msgid "To help ensure high availability of the databases that store the internal data for CloudStack, you can set up database replication. This covers both the main CloudStack database and the Usage database. Replication is achieved using the MySQL connector parameters and two-way replication. Tested with MySQL 5.1 and 5.5."
+msgstr ""
+
+#: ../../reliability.rst:170
+# 2f86c6796ebc476ba0a054b55ec4199d
+msgid "How to Set Up Database Replication"
+msgstr ""
+
+#: ../../reliability.rst:172
+# 9c0172a3e34d439ca93117a4c922b4cf
+msgid "Database replication in CloudStack is provided using the MySQL replication capabilities. The steps to set up replication can be found in the MySQL documentation (links are provided below). It is suggested that you set up two-way replication, which involves two database nodes. In this case, for example, you might have node1 and node2."
+msgstr ""
+
+#: ../../reliability.rst:178
+# c0c448bf2d294f1f99d5a0715263bf84
+msgid "You can also set up chain replication, which involves more than two nodes. In this case, you would first set up two-way replication with node1 and node2. Next, set up one-way replication from node2 to node3. Then set up one-way replication from node3 to node4, and so on for all the additional nodes."
+msgstr ""
+
+#: ../../reliability.rst:184
+# 946a91ee699241e981ff92c48293ebe9
+msgid "References:"
+msgstr ""
+
+#: ../../reliability.rst:186
+# 0e89f25f5f474fa8a51de012dc293160
+msgid "`http://dev.mysql.com/doc/refman/5.0/en/replication-howto.html <http://dev.mysql.com/doc/refman/5.0/en/replication-howto.html>`_"
+msgstr ""
+
+#: ../../reliability.rst:188
+# 4b174fc7f8484911b245607384172cae
+msgid "`https://wikis.oracle.com/display/CommSuite/MySQL+High+Availability+and+Replication+Information+For+Calendar+Server <https://wikis.oracle.com/display/CommSuite/MySQL+High+Availability+and+Replication+Information+For+Calendar+Server>`_"
+msgstr ""
+
+#: ../../reliability.rst:192
+# 4fe437de91df4ffa8fe0925f0acdbfc5
+msgid "Configuring Database High Availability"
+msgstr ""
+
+#: ../../reliability.rst:194
+# f284eab37564471292cd2af70ef18ae5
+msgid "To control the database high availability behavior, use the following configuration settings in the file /etc/cloudstack/management/db.properties."
+msgstr ""
+
+#: ../../reliability.rst:198
+# f79c8f4273854ceb83977ca0474e9594
+msgid "**Required Settings**"
+msgstr ""
+
+#: ../../reliability.rst:200
+# 239ea1c4ea2a4c428cbfdd0ae1d3c2a3
+msgid "Be sure you have set the following in db.properties:"
+msgstr ""
+
+#: ../../reliability.rst:202
+# e03d864abdca47daa90be6c6c5eccecc
+msgid "``db.ha.enabled``: set to true if you want to use the replication feature."
+msgstr ""
+
+#: ../../reliability.rst:205
+# affe10ff738642c4b25a6cbfc26c498e
+msgid "Example: ``db.ha.enabled=true``"
+msgstr ""
+
+#: ../../reliability.rst:207
+# 147ac9efb2314312b6e97323a267fd7c
+msgid "``db.cloud.slaves``: set to a comma-delimited set of slave hosts for the cloud database. This is the list of nodes set up with replication. The master node is not in the list, since it is already mentioned elsewhere in the properties file."
+msgstr ""
+
+#: ../../reliability.rst:212
+# aa38f185ca8b4c1b86e19da970eb3901
+msgid "Example: ``db.cloud.slaves=node2,node3,node4``"
+msgstr ""
+
+#: ../../reliability.rst:214
+# 1783ef0808884e28ab22f6b3172dba41
+msgid "``db.usage.slaves``: set to a comma-delimited set of slave hosts for the usage database. This is the list of nodes set up with replication. The master node is not in the list, since it is already mentioned elsewhere in the properties file."
+msgstr ""
+
+#: ../../reliability.rst:219
+# 573fb04445dd4b0ba4f5b9a5f8517c75
+msgid "Example: ``db.usage.slaves=node2,node3,node4``"
+msgstr ""
+
+#: ../../reliability.rst:221
+# 739f9df2617d4e24aaa9adb209c65969
+msgid "**Optional Settings**"
+msgstr ""
+
+#: ../../reliability.rst:223
+# 21e38ceba8e84d3f8b520026cae7d1b7
+msgid "The following settings must be present in db.properties, but you are not required to change the default values unless you wish to do so for tuning purposes:"
+msgstr ""
+
+#: ../../reliability.rst:227
+# bcfa8dcb331c4185bab0cbdfbb3624ca
+msgid "``db.cloud.secondsBeforeRetryMaster``: The number of seconds the MySQL connector should wait before trying again to connect to the master after the master went down. Default is 1 hour. The retry might happen sooner if db.cloud.queriesBeforeRetryMaster is reached first."
+msgstr ""
+
+#: ../../reliability.rst:232
+# 55d7217f8ea6408e8389bd39dbbfc3fc
+msgid "Example: ``db.cloud.secondsBeforeRetryMaster=3600``"
+msgstr ""
+
+#: ../../reliability.rst:234
+# d8cfb3b10706434d8ad7c63b231e7ee9
+msgid "``db.cloud.queriesBeforeRetryMaster``: The minimum number of queries to be sent to the database before trying again to connect to the master after the master went down. Default is 5000. The retry might happen sooner if db.cloud.secondsBeforeRetryMaster is reached first."
+msgstr ""
+
+#: ../../reliability.rst:239
+# f7b672a867c64854accef70177a0dd73
+msgid "Example: ``db.cloud.queriesBeforeRetryMaster=5000``"
+msgstr ""
+
+#: ../../reliability.rst:241
+# 2283aca3081443c585804a3c9d63a45d
+msgid "``db.cloud.initialTimeout``: Initial time the MySQL connector should wait before trying again to connect to the master. Default is 3600."
+msgstr ""
+
+#: ../../reliability.rst:244
+# bae95908743e448b967b6992b4e88816
+msgid "Example: ``db.cloud.initialTimeout=3600``"
+msgstr ""
+
+#: ../../reliability.rst:248
+# 6b17824c97504228abd0de9726eb598e
+msgid "Limitations on Database High Availability"
+msgstr ""
+
+#: ../../reliability.rst:250
+# 5df2f93aff944e03bd3c9f9e21c95cb6
+msgid "The following limitations exist in the current implementation of this feature."
+msgstr ""
+
+#: ../../reliability.rst:253
+# 7c4a38ab45c943a489f2e7ae8f3ab0e2
+msgid "Slave hosts can not be monitored through CloudStack. You will need to have a separate means of monitoring."
+msgstr ""
+
+#: ../../reliability.rst:256
+# 5270e63b8008415bbe847a54002660bc
+msgid "Events from the database side are not integrated with the CloudStack Management Server events system."
+msgstr ""
+
+#: ../../reliability.rst:259
+# 1bef8f38060a49e7ba30b234ad377f32
+msgid "You must periodically perform manual clean-up of bin log files generated by replication on database nodes. If you do not clean up the log files, the disk can become full."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/service_offerings.pot b/source/adminguide/locale/pot/service_offerings.pot
new file mode 100644
index 0000000..6edb5a3
--- /dev/null
+++ b/source/adminguide/locale/pot/service_offerings.pot
@@ -0,0 +1,809 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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"
+
+#: ../../service_offerings.rst:18
+# 003ddcd4027d44e1bae1560113612be3
+msgid "Service Offerings"
+msgstr ""
+
+#: ../../service_offerings.rst:20
+# db77c1944ac947e79b5c76bac2c1cc4d
+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 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."
+msgstr ""
+
+#: ../../service_offerings.rst:34
+# eac4f2f6a6f346d991640acd102c8d0f
+msgid "Service Offerings, Disk Offerings, Network Offerings, and Templates"
+msgstr ""
+
+#: ../../service_offerings.rst:36
+# f620092a7ebb41d79ed21c4a5c81d56c
+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 ""
+
+#: ../../service_offerings.rst:40
+# ab361873de2144c095169458d8a25cb1
+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 ""
+
+#: ../../service_offerings.rst:44
+# 1044e18059f346f9ac414afad0f176ff
+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 ""
+
+#: ../../service_offerings.rst:48
+# 8fa5935f6811416784633a016e64dff9
+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 ""
+
+#: ../../service_offerings.rst:53
+# 0e8bd7f2f14a4d698ef10eb8f7bd3059
+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 ""
+
+#: ../../service_offerings.rst:58
+# 52afe58166814f258c3426dd55249f7d
+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 ""
+
+#: ../../service_offerings.rst:66
+# b05b989a07394a3eafabebb48aeaa29b
+msgid "Compute and Disk Service Offerings"
+msgstr ""
+
+#: ../../service_offerings.rst:68
+# 494d86b3d06340ab855b7df7a298410a
+msgid "A service offering is a set of virtual hardware features such as CPU core count and speed, memory, and disk size. The CloudStack administrator can set up various offerings, and then end users choose from the available offerings when they create a new VM. Based on the user’s selected offering, CloudStack emits usage records that can be integrated with billing systems."
+msgstr ""
+
+#: ../../service_offerings.rst:75
+# d5a6cbcc11594496b3347a195f561c03
+msgid "Some characteristics of service offerings must be defined by the CloudStack administrator, and others can be left undefined so that the end-user can enter their own desired values. This is useful to reduce the number of offerings the CloudStack administrator has to define. Instead of defining a compute offering for every imaginable combination of values that a user might want, the administrator can define offerings that provide some flexibility to the users and can serve as the basis for several different VM configurations."
+msgstr ""
+
+#: ../../service_offerings.rst:84
+# 57a11b0d87cd4cb6bd64aa2c1b61db19
+msgid "A service offering includes the following elements:"
+msgstr ""
+
+#: ../../service_offerings.rst:86
+# 314c7c80394a45fe9bd7869f420d84b0
+msgid "CPU, memory, and network resource guarantees"
+msgstr ""
+
+#: ../../service_offerings.rst:88
+# b88f65b187394191a414ccf797fb3c8a
+msgid "How resources are metered"
+msgstr ""
+
+#: ../../service_offerings.rst:90
+# 0f00c0ffe83246cdbebaae3ad3295fb6
+msgid "How the resource usage is charged"
+msgstr ""
+
+#: ../../service_offerings.rst:92
+# 168105b5e4554db0b0cb46f61c6763c3
+msgid "How often the charges are generated"
+msgstr ""
+
+#: ../../service_offerings.rst:94
+# 4ed86a2b44c647c4991679260cf019f9
+msgid "For example, one service offering might allow users to create a virtual machine instance that is equivalent to a 1 GHz Intel® Core™ 2 CPU, with 1 GB memory at $0.20/hour, with network traffic metered at $0.10/GB."
+msgstr ""
+
+#: ../../service_offerings.rst:98
+# c41f30feb0b442d4b39c95168d4ea2cc
+msgid "CloudStack separates service offerings into compute offerings and disk offerings. The compute service offering specifies:"
+msgstr ""
+
+#: ../../service_offerings.rst:101
+# 03b79e1695f6418596fbf3dfdae6fdf5
+msgid "Guest CPU (optional). If not defined by the CloudStack administrator, users can pick the CPU attributes."
+msgstr ""
+
+#: ../../service_offerings.rst:104
+# a9484632eacc49aaaa151b0462236017
+msgid "Guest RAM (optional). If not defined by the CloudStack administrator, users can pick the RAM."
+msgstr ""
+
+#: ../../service_offerings.rst:107
+# 8566fe8312914c68bedcb2c81b3c0c7b
+msgid "Guest Networking type (virtual or direct)"
+msgstr ""
+
+#: ../../service_offerings.rst:109
+# 083cf96ec0c24344baef88ec1b1b562b
+msgid "Tags on the root disk"
+msgstr ""
+
+#: ../../service_offerings.rst:111
+# 49478998f1fc4c37a9278a56f4e95eac
+msgid "The disk offering specifies:"
+msgstr ""
+
+#: ../../service_offerings.rst:113
+# e819601d04c3430f97d349bc00ef953b
+msgid "Disk size (optional). If not defined by the CloudStack administrator, users can pick the disk size."
+msgstr ""
+
+#: ../../service_offerings.rst:116
+# a4d4936154c4482d889d800ccf8426ef
+msgid "Tags on the data disk"
+msgstr ""
+
+#: ../../service_offerings.rst:120
+# a561332470b74e3e90cdf9bcabe2317e
+msgid "Custom Compute Offering"
+msgstr ""
+
+#: ../../service_offerings.rst:122
+# 55f34a846c444887ad4349ad37fe65f8
+msgid "CloudStack provides you the flexibility to specify the desired values for the number of CPU, CPU speed, and memory while deploying a VM. As an admin, you create a Compute Offering by marking it as custom, and the users will be able to customize this dynamic Compute Offering by specifying the memory, and CPU at the time of VM creation or upgrade. Custom Compute Offering is same as the normal Compute Offering except that the values of the dynamic parameters will be set to zeros in the given set of templates. Use this offering to deploy VM by specifying custom values for the dynamic parameters. Memory, CPU and number of CPUs are considered as dynamic parameters."
+msgstr ""
+
+#: ../../service_offerings.rst:133
+# 50cd9056418842c08eb28fdce54e3deb
+msgid "Dynamic Compute Offerings can be used in following cases: deploying a VM, changing the compute offering of a stopped VM and running VMs, which is nothing but scaling up. To support this feature a new field, Custom, has been added to the Create Compute Offering page. If the Custom field is checked, the user will be able to create a custom Compute Offering by filling in the desired values for number of CPU, CPU speed, and memory. See ? for more information on this."
+msgstr ""
+
+#: ../../service_offerings.rst:141
+# efbe01f182224e6a96c59f3165e87c47
+msgid "*Recording Usage Events for Dynamically Assigned Resources*."
+msgstr ""
+
+#: ../../service_offerings.rst:143
+# b098284613414134b2cd3e2527db633b
+msgid "To support this feature, usage events has been enhanced to register events for dynamically assigned resources. Usage events are registered when a VM is created from a custom compute offering, and upon changing the compute offering of a stopped or running VM. The values of the parameters, such as CPU, speed, RAM are recorded."
+msgstr ""
+
+#: ../../service_offerings.rst:151
+# 64a1b09cdfbd4e95b1fcdf2ba0db010b
+msgid "Creating a New Compute Offering"
+msgstr ""
+
+#: ../../service_offerings.rst:153
+# a989d37873d84df993d59a7d089d7cdd
+msgid "To create a new compute offering:"
+msgstr ""
+
+#: ../../service_offerings.rst:155
+#: ../../service_offerings.rst:276
+#: ../../service_offerings.rst:375
+# cd40916e685345c99849ac58022fd684
+# 3f783f61450b417ea824bafee21771db
+# a464ec4a658b4d9884f389505fe3ad18
+msgid "Log in with admin privileges to the CloudStack UI."
+msgstr ""
+
+#: ../../service_offerings.rst:157
+#: ../../service_offerings.rst:278
+#: ../../service_offerings.rst:377
+# 430fa2ee248b407f9d4085fb63dd7d77
+# 999d0aeef65e43539cf25bcb3f791342
+# b51af425528d45d6b50797a303b9badc
+msgid "In the left navigation bar, click Service Offerings."
+msgstr ""
+
+#: ../../service_offerings.rst:159
+# 9d93f2c8859741418b99ea21160f5717
+msgid "In Select Offering, choose Compute Offering."
+msgstr ""
+
+#: ../../service_offerings.rst:161
+# 7167eb3ab24d4bba83156b7b67a2474a
+msgid "Click Add Compute Offering."
+msgstr ""
+
+#: ../../service_offerings.rst:163
+#: ../../service_offerings.rst:284
+#: ../../service_offerings.rst:383
+# d66b1055632049b3be191768ce8d3f6f
+# 8282a7241f674568b997c0dcd2b08b88
+# 22f14b2d47e140ae9fa9f96c736f51f5
+msgid "In the dialog, make the following choices:"
+msgstr ""
+
+#: ../../service_offerings.rst:165
+# 248a64cf597a40f29490a97743581cae
+msgid "**Name**: Any desired name for the service offering."
+msgstr ""
+
+#: ../../service_offerings.rst:167
+# 16069fbe3c51423eba16ddfb98cd4dd2
+msgid "**Description**: A short description of the offering that can be displayed to users"
+msgstr ""
+
+#: ../../service_offerings.rst:170
+# 347237d86b124a00be0d69850897539d
+msgid "**Storage type**: The type of disk that should be allocated. Local allocates from storage attached directly to the host where the system VM is running. Shared allocates from storage accessible via NFS."
+msgstr ""
+
+#: ../../service_offerings.rst:175
+# 2740734abb894968ad28ec481f8be6f8
+msgid "**Custom**: Custom compute offerings can be used in following cases: deploying a VM, changing the compute offering of a stopped VM and running VMs, which is nothing but scaling up."
+msgstr ""
+
+#: ../../service_offerings.rst:179
+# ca83dc70a28544378533fd9391d96e06
+msgid "If the Custom field is checked, the end-user must fill in the desired values for number of CPU, CPU speed, and RAM Memory when using a custom compute offering. When you check this box, those three input fields are hidden in the dialog box."
+msgstr ""
+
+#: ../../service_offerings.rst:184
+# 8ca7932a8f254ece814179f9c5690c71
+msgid "**# of CPU cores**: The number of cores which should be allocated to a system VM with this offering. If Custom is checked, this field does not appear."
+msgstr ""
+
+#: ../../service_offerings.rst:188
+# 179de46f279a47c38263160519e05bc8
+msgid "**CPU (in MHz)**: The CPU speed of the cores that the system VM is allocated. For example, “2000” would provide for a 2 GHz clock. If Custom is checked, this field does not appear."
+msgstr ""
+
+#: ../../service_offerings.rst:192
+# b4862e3476024139a5791b56f164bf54
+msgid "**Memory (in MB)**: The amount of memory in megabytes that the system VM should be allocated. For example, “2048” would provide for a 2 GB RAM allocation. If Custom is checked, this field does not appear."
+msgstr ""
+
+#: ../../service_offerings.rst:197
+# 75b2531b57c743c1b6077813a925c97c
+msgid "**Network Rate**: Allowed data transfer rate in MB per second."
+msgstr ""
+
+#: ../../service_offerings.rst:199
+# d8427006117040188afa00c409a53e9c
+msgid "**Disk Read Rate**: Allowed disk read rate in bits per second."
+msgstr ""
+
+#: ../../service_offerings.rst:201
+# d7c08f798b324b0fa241b2bc293d9fe1
+msgid "**Disk Write Rate**: Allowed disk write rate in bits per second."
+msgstr ""
+
+#: ../../service_offerings.rst:203
+# 657abd8d993d47f98da0e15c0842aadd
+msgid "**Disk Read Rate**: Allowed disk read rate in IOPS (input/output operations per second)."
+msgstr ""
+
+#: ../../service_offerings.rst:206
+# 41c2fbc1baef42c6b5df3e05a520019a
+msgid "**Disk Write Rate**: Allowed disk write rate in IOPS (input/output operations per second)."
+msgstr ""
+
+#: ../../service_offerings.rst:209
+# 1ec28ce24ead4f2486f7368ade10a4e8
+msgid "**Offer HA**: If yes, the administrator can choose to have the system VM be monitored and as highly available as possible."
+msgstr ""
+
+#: ../../service_offerings.rst:212
+# 6d4c0c7c0d8548e3825edabb5d73d731
+msgid "**Storage Tags**: The tags that should be associated with the primary storage used by the system VM."
+msgstr ""
+
+#: ../../service_offerings.rst:215
+# b730850e604446d89aba06366e8302be
+msgid "**Host Tags**: (Optional) Any tags that you use to organize your hosts"
+msgstr ""
+
+#: ../../service_offerings.rst:218
+# 6fb3e5e926cc49038912a81d7d3c1a1c
+msgid "**CPU cap**: Whether to limit the level of CPU usage even if spare capacity is available."
+msgstr ""
+
+#: ../../service_offerings.rst:221
+# 5eff635b882c422680849b6f7d511fdb
+msgid "**Public**: Indicate whether the service offering should be available all domains or only some domains. Choose Yes to make it available to all domains. Choose No to limit the scope to a subdomain; CloudStack will then prompt for the subdomain's name."
+msgstr ""
+
+#: ../../service_offerings.rst:226
+# d401f5f62aaa4778bce3429d100a06de
+msgid "**isVolatile**: If checked, VMs created from this service offering will have their root disks reset upon reboot. This is useful for secure environments that need a fresh start on every boot and for desktops that should not retain state."
+msgstr ""
+
+#: ../../service_offerings.rst:231
+# 7ea10a7203db4d629ba1fc7dfd120b28
+msgid "**Deployment Planner**: Choose the technique that you would like CloudStack to use when deploying VMs based on this service offering."
+msgstr ""
+
+#: ../../service_offerings.rst:235
+# 09d1468dffad438fa4266aa82987ce0e
+msgid "First Fit places new VMs on the first host that is found having sufficient capacity to support the VM's requirements."
+msgstr ""
+
+#: ../../service_offerings.rst:238
+# 9a877ddb3dab4ad69db6b5c7627dd22c
+msgid "User Dispersing makes the best effort to evenly distribute VMs belonging to the same account on different clusters or pods."
+msgstr ""
+
+#: ../../service_offerings.rst:241
+# e2716f72710c4569899cebc9a22840ab
+msgid "User Concentrated prefers to deploy VMs belonging to the same account within a single pod."
+msgstr ""
+
+#: ../../service_offerings.rst:244
+# 5e285b8b246b49bbb76fdf939e1dc838
+msgid "Implicit Dedication will deploy VMs on private infrastructure that is dedicated to a specific domain or account. If you choose this planner, then you must also pick a value for Planner Mode. See `“Dedicating Resources to Accounts and Domains” <accounts.html#dedicating-resources-to-accounts-and-domains>`_."
+msgstr ""
+
+#: ../../service_offerings.rst:250
+# 6e9b2cfece7840a3a281d17fbf4d19cd
+msgid "Bare Metal is used with bare metal hosts. See Bare Metal Installation in the Installation Guide."
+msgstr ""
+
+#: ../../service_offerings.rst:253
+# 3a40b2888d8b4d0bb06501a2d726411d
+msgid "**Planner Mode**: Used when ImplicitDedicationPlanner is selected in the previous field. The planner mode determines how VMs will be deployed on private infrastructure that is dedicated to a single domain or account."
+msgstr ""
+
+#: ../../service_offerings.rst:258
+# 8c6a6d1601d5409f9cf07e89162fe229
+msgid "Strict: 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 ""
+
+#: ../../service_offerings.rst:264
+# 36d35c740f134708ade301fc640503d9
+msgid "Preferred: The VM will be deployed in dedicated infrastructure if possible. Otherwise, the VM can be deployed in shared infrastructure."
+msgstr ""
+
+#: ../../service_offerings.rst:268
+#: ../../service_offerings.rst:333
+#: ../../service_offerings.rst:426
+# 094aad8be1574fa385667bebf06ed3b6
+# 857fa2723e0b4bf4916f435ba0604892
+# ac56513abaae4c1895b390a2f0333ab0
+msgid "Click Add."
+msgstr ""
+
+#: ../../service_offerings.rst:272
+# 1a46fadd2f3a42c68b8cdeef05745eca
+msgid "Creating a New Disk Offering"
+msgstr ""
+
+#: ../../service_offerings.rst:274
+# 06fce5a6dad94dfa84eed86ae00ec617
+msgid "To create a new disk offering:"
+msgstr ""
+
+#: ../../service_offerings.rst:280
+# d3eb3c404772407da39449916e1953ca
+msgid "In Select Offering, choose Disk Offering."
+msgstr ""
+
+#: ../../service_offerings.rst:282
+# da2d57c6d441495685b440392d59c162
+msgid "Click Add Disk Offering."
+msgstr ""
+
+#: ../../service_offerings.rst:286
+# d178f97b76c84de0bfd097ef93c110d3
+msgid "Name. Any desired name for the disk offering."
+msgstr ""
+
+#: ../../service_offerings.rst:288
+#: ../../service_offerings.rst:387
+# efaecce14927441aa329961c4d485567
+# e7bfb9a5943b405a8cae32d04743b528
+msgid "Description. A short description of the offering that can be displayed to users"
+msgstr ""
+
+#: ../../service_offerings.rst:291
+# 4f1a836b18b74aaf94d4ad7e5b83152c
+msgid "Custom Disk Size. If checked, the user can set their own disk size. If not checked, the root administrator must define a value in Disk Size."
+msgstr ""
+
+#: ../../service_offerings.rst:295
+# 5663fa2cb649450db44f795449d5dd9f
+msgid "Disk Size. Appears only if Custom Disk Size is not selected. Define the volume size in GB."
+msgstr ""
+
+#: ../../service_offerings.rst:298
+# d06aab69bbd44359a42d1eaebcb4ca5a
+msgid "QoS Type. Three options: Empty (no Quality of Service), hypervisor (rate limiting enforced on the hypervisor side), and storage (guaranteed minimum and maximum IOPS enforced on the storage side). If leveraging QoS, make sure that the hypervisor or storage system supports this feature."
+msgstr ""
+
+#: ../../service_offerings.rst:304
+# 665e3b5c270e42979195e2837591595b
+msgid "Custom IOPS. If checked, the user can set their own IOPS. If not checked, the root administrator can define values. If the root admin does not set values when using storage QoS, default values are used (the defauls can be overridden if the proper parameters are passed into CloudStack when creating the primary storage in question)."
+msgstr ""
+
+#: ../../service_offerings.rst:311
+# 3fdd090110144e8fae3a8a6d77e6e426
+msgid "Min IOPS. Appears only if storage QoS is to be used. Set a guaranteed minimum number of IOPS to be enforced on the storage side."
+msgstr ""
+
+#: ../../service_offerings.rst:315
+# 5f904e8920db455192f6af78633b6f22
+msgid "Max IOPS. Appears only if storage QoS is to be used. Set a maximum number of IOPS to be enforced on the storage side (the system may go above this limit in certain circumstances for short intervals)."
+msgstr ""
+
+#: ../../service_offerings.rst:319
+# ea14b97cc586470c8be3da25ef0a3ae1
+msgid "(Optional)Storage Tags. The tags that should be associated with the primary storage for this disk. Tags are a comma separated list of attributes of the storage. For example \"ssd,blue\". Tags are also added on Primary Storage. CloudStack matches tags on a disk offering to tags on the storage. If a tag is present on a disk offering that tag (or tags) must also be present on Primary Storage for the volume to be provisioned. If no such primary storage exists, allocation from the disk offering will fail.."
+msgstr ""
+
+#: ../../service_offerings.rst:328
+#: ../../service_offerings.rst:421
+# dda851b25a4c44ae92e6890fb2542e04
+# 5034af57e1514329ba054bf08be12e5a
+msgid "Public. Indicate whether the service offering should be available all domains or only some domains. Choose Yes to make it available to all domains. Choose No to limit the scope to a subdomain; CloudStack will then prompt for the subdomain's name."
+msgstr ""
+
+#: ../../service_offerings.rst:337
+# 5c44a4ba4c074c4caf886309d1aba4f1
+msgid "Modifying or Deleting a Service Offering"
+msgstr ""
+
+#: ../../service_offerings.rst:339
+# 5aab86d5c8e443609a4613d0073f7314
+msgid "Service offerings cannot be changed once created. This applies to both compute offerings and disk offerings."
+msgstr ""
+
+#: ../../service_offerings.rst:342
+# 1bab2fd909c74ac299118dcd6c9848b4
+msgid "A service offering can be deleted. If it is no longer in use, it is deleted immediately and permanently. If the service offering is still in use, it will remain in the database until all the virtual machines referencing it have been deleted. After deletion by the administrator, a service offering will not be available to end users that are creating new instances."
+msgstr ""
+
+#: ../../service_offerings.rst:351
+# 0f1e4fe248f24ff6b4e4f47ef4a4ef55
+msgid "System Service Offerings"
+msgstr ""
+
+#: ../../service_offerings.rst:353
+# 007749e74de54391b1664b4166e80259
+msgid "System service offerings provide a choice of CPU speed, number of CPUs, tags, and RAM size, just as other service offerings do. But rather than being used for virtual machine instances and exposed to users, system service offerings are used to change the default properties of virtual routers, console proxies, and other system VMs. System service offerings are visible only to the CloudStack root administrator. CloudStack provides default system service offerings. The CloudStack root administrator can create additional custom system service offerings."
+msgstr ""
+
+#: ../../service_offerings.rst:362
+# 4201666336094c93ae198477756df881
+msgid "When CloudStack creates a virtual router for a guest network, it uses default settings which are defined in the system service offering associated with the network offering. You can upgrade the capabilities of the virtual router by applying a new network offering that contains a different system service offering. All virtual routers in that network will begin using the settings from the new service offering."
+msgstr ""
+
+#: ../../service_offerings.rst:371
+# f91e393f388b4e6481cd8a71e7f79278
+msgid "Creating a New System Service Offering"
+msgstr ""
+
+#: ../../service_offerings.rst:373
+# 0d2bc72cb0364a098544d79a257c89d8
+msgid "To create a system service offering:"
+msgstr ""
+
+#: ../../service_offerings.rst:379
+# 6e5e507b5bf94c149b3113e07ca5ce03
+msgid "In Select Offering, choose System Offering."
+msgstr ""
+
+#: ../../service_offerings.rst:381
+# 42a35e0d5b5e434f8fa210dfa25c0edf
+msgid "Click Add System Service Offering."
+msgstr ""
+
+#: ../../service_offerings.rst:385
+# c20bf047c83a44d89017825a2228c46d
+msgid "Name. Any desired name for the system offering."
+msgstr ""
+
+#: ../../service_offerings.rst:390
+# 1d970335d51e46ac9bda9c706759ba65
+msgid "System VM Type. Select the type of system virtual machine that this offering is intended to support."
+msgstr ""
+
+#: ../../service_offerings.rst:393
+# 8086a4f1336049c19479206b751d04ea
+msgid "Storage type. The type of disk that should be allocated. Local allocates from storage attached directly to the host where the system VM is running. Shared allocates from storage accessible via NFS."
+msgstr ""
+
+#: ../../service_offerings.rst:398
+# 913ba08b0770492cba53d3d247655710
+msgid "# of CPU cores. The number of cores which should be allocated to a system VM with this offering"
+msgstr ""
+
+#: ../../service_offerings.rst:401
+# fb5a2f7abf0a4e18b7847db64d898bc2
+msgid "CPU (in MHz). The CPU speed of the cores that the system VM is allocated. For example, \"2000\" would provide for a 2 GHz clock."
+msgstr ""
+
+#: ../../service_offerings.rst:404
+# de2eaf45f59b471b9d37d34ab02ce6e2
+msgid "Memory (in MB). The amount of memory in megabytes that the system VM should be allocated. For example, \"2048\" would provide for a 2 GB RAM allocation."
+msgstr ""
+
+#: ../../service_offerings.rst:408
+# c1d2470c7b62430481a4de61c2356410
+msgid "Network Rate. Allowed data transfer rate in MB per second."
+msgstr ""
+
+#: ../../service_offerings.rst:410
+# a7d7af4efcf94e478441f58eb4ab9ec1
+msgid "Offer HA. If yes, the administrator can choose to have the system VM be monitored and as highly available as possible."
+msgstr ""
+
+#: ../../service_offerings.rst:413
+# 41c4d5f0752e44e98e557a65b65a14c0
+msgid "Storage Tags. The tags that should be associated with the primary storage used by the system VM."
+msgstr ""
+
+#: ../../service_offerings.rst:416
+# 22cd45b0933841f3bf3106245a42af05
+msgid "Host Tags. (Optional) Any tags that you use to organize your hosts"
+msgstr ""
+
+#: ../../service_offerings.rst:418
+# c8df696c132647959ca16dcad278053e
+msgid "CPU cap. Whether to limit the level of CPU usage even if spare capacity is available."
+msgstr ""
+
+#: ../../service_offerings.rst:430
+# 53c64783d59d4debb2c9c1ebe4a0bb7d
+msgid "Network Throttling"
+msgstr ""
+
+#: ../../service_offerings.rst:432
+# 26cf64df6529406f922adcedb9234f9f
+msgid "Network throttling is the process of controlling the network access and bandwidth usage based on certain rules. CloudStack controls this behaviour of the guest networks in the cloud by using the network rate parameter. This parameter is defined as the default data transfer rate in Mbps (Megabits Per Second) allowed in a guest network. It defines the upper limits for network utilization. If the current utilization is below the allowed upper limits, access is granted, else revoked."
+msgstr ""
+
+#: ../../service_offerings.rst:440
+# 27806198975d424082e8dab6ce49f0b4
+msgid "You can throttle the network bandwidth either to control the usage above a certain limit for some accounts, or to control network congestion in a large cloud environment. The network rate for your cloud can be configured on the following:"
+msgstr ""
+
+#: ../../service_offerings.rst:445
+# 7432018ff67f4894a723bdca6bff087b
+msgid "Network Offering"
+msgstr ""
+
+#: ../../service_offerings.rst:447
+# 506188e4ff414063a2491e10c81e51c9
+msgid "Service Offering"
+msgstr ""
+
+#: ../../service_offerings.rst:449
+# 320ac2d073ce4bf5af25029badc0cdb4
+msgid "Global parameter"
+msgstr ""
+
+#: ../../service_offerings.rst:451
+# 9c2fc1907fa34cf7b21cefc002bff096
+msgid "If network rate is set to NULL in service offering, the value provided in the vm.network.throttling.rate global parameter is applied. If the value is set to NULL for network offering, the value provided in the network.throttling.rate global parameter is considered."
+msgstr ""
+
+#: ../../service_offerings.rst:456
+# 70d2185fb70847edb5c332fb612484e7
+msgid "For the default public, storage, and management networks, network rate is set to 0. This implies that the public, storage, and management networks will have unlimited bandwidth by default. For default guest networks, network rate is set to NULL. In this case, network rate is defaulted to the global parameter value."
+msgstr ""
+
+#: ../../service_offerings.rst:462
+# 88f665be2f3e4cfd87c6d89ae2b118ef
+msgid "The following table gives you an overview of how network rate is applied on different types of networks in CloudStack."
+msgstr ""
+
+#: ../../service_offerings.rst:466
+# 2df7571b44394db29aa0803e1bd515ae
+msgid "Networks"
+msgstr ""
+
+#: ../../service_offerings.rst:466
+# 30beee005ab04cb3947aa3a093695d15
+msgid "Network Rate Is Taken from"
+msgstr ""
+
+#: ../../service_offerings.rst:468
+# 2d1b0256284f4e9196bed7491709337e
+msgid "Guest network of Virtual Router"
+msgstr ""
+
+#: ../../service_offerings.rst:468
+#: ../../service_offerings.rst:469
+# 710cff98d40d47b1b4691f4ef4cc0ed7
+# 7301bab7c1654ab09e4495741b32f409
+msgid "Guest Network Offering"
+msgstr ""
+
+#: ../../service_offerings.rst:469
+# b9550d4e593644f7997ae2b59833d30e
+msgid "Public network of Virtual Router"
+msgstr ""
+
+#: ../../service_offerings.rst:470
+# 5fbb2616fe4146139b5adddf90e140c5
+msgid "Storage network of Secondary Storage VM"
+msgstr ""
+
+#: ../../service_offerings.rst:470
+#: ../../service_offerings.rst:471
+#: ../../service_offerings.rst:472
+#: ../../service_offerings.rst:473
+#: ../../service_offerings.rst:474
+#: ../../service_offerings.rst:475
+#: ../../service_offerings.rst:476
+#: ../../service_offerings.rst:477
+# 149bbe361c7b4f85bc046a55d9a0147e
+# f68c6d576d58455194ee074721af9ab1
+# 6767654cd1d74942a8dc4a4a997c0e62
+# 9784131010fd47ce8cbdf1d9b322bdd6
+# fcb50bbb01464259bf0060a49547950f
+# 3499985b0b95428c8cf13bdceeacae5c
+# 9eb605f5c4204f7a93451b0af6b0ac63
+# a5eff8a6947548b99a5e9c63a24f4890
+msgid "System Network Offering"
+msgstr ""
+
+#: ../../service_offerings.rst:471
+# d0e8015a02d74f79a085327db997c47a
+msgid "Management network of Secondary Storage VM"
+msgstr ""
+
+#: ../../service_offerings.rst:472
+# 5ec6da9e6d934d9fad3bede5813f70f9
+msgid "Storage network of Console Proxy VM"
+msgstr ""
+
+#: ../../service_offerings.rst:473
+# 4cf8b23c38354b708cd82d9c7e31ff03
+msgid "Management network of Console Proxy VM"
+msgstr ""
+
+#: ../../service_offerings.rst:474
+# 2ff0726b224449c08b32d13597df71a7
+msgid "Storage network of Virtual Router"
+msgstr ""
+
+#: ../../service_offerings.rst:475
+# 91083f647e9345d4a21912156d7990dd
+msgid "Management network of Virtual Router"
+msgstr ""
+
+#: ../../service_offerings.rst:476
+# 20a8e9d21dda41208554a4065467ea8e
+msgid "Public network of Secondary Storage VM"
+msgstr ""
+
+#: ../../service_offerings.rst:477
+# 801f07af30a34b239adb18ef1edcd47c
+msgid "Public network of Console Proxy VM"
+msgstr ""
+
+#: ../../service_offerings.rst:478
+# 860138dcf0344072bed2a8184a5336c7
+msgid "Default network of a guest VM"
+msgstr ""
+
+#: ../../service_offerings.rst:478
+# a6f07fe2acf94351951e197227848984
+msgid "Compute Offering"
+msgstr ""
+
+#: ../../service_offerings.rst:479
+# bb5e6134192f48038cbdfcc8141882da
+msgid "Additional networks of a guest VM"
+msgstr ""
+
+#: ../../service_offerings.rst:479
+# 9cdc4ff5ef2e42b39986c9157d856fc7
+msgid "Corresponding Network Offerings"
+msgstr ""
+
+#: ../../service_offerings.rst:482
+# 82ee01b4006f4ba48baf48b75381dac7
+msgid "A guest VM must have a default network, and can also have many additional networks. Depending on various parameters, such as the host and virtual switch used, you can observe a difference in the network rate in your cloud. For example, on a VMware host the actual network rate varies based on where they are configured (compute offering, network offering, or both); the network type (shared or isolated); and traffic direction (ingress or egress)."
+msgstr ""
+
+#: ../../service_offerings.rst:490
+# a3a45b2e646846f984140407ef18cd47
+msgid "The network rate set for a network offering used by a particular network in CloudStack is used for the traffic shaping policy of a port group, for example: port group A, for that network: a particular subnet or VLAN on the actual network. The virtual routers for that network connects to the port group A, and by default instances in that network connects to this port group. However, if an instance is deployed with a compute offering with the network rate set, and if this rate is used for the traffic shaping policy of another port group for the network, for example port group B, then instances using this compute offering are connected to the port group B, instead of connecting to port group A."
+msgstr ""
+
+#: ../../service_offerings.rst:501
+# 439cfd7a4cdd405c9eb7e554009d476e
+msgid "The traffic shaping policy on standard port groups in VMware only applies to the egress traffic, and the net effect depends on the type of network used in CloudStack. In shared networks, ingress traffic is unlimited for CloudStack, and egress traffic is limited to the rate that applies to the port group used by the instance if any. If the compute offering has a network rate configured, this rate applies to the egress traffic, otherwise the network rate set for the network offering applies. For isolated networks, the network rate set for the network offering, if any, effectively applies to the ingress traffic. This is mainly because the network rate set for the network offering applies to the egress traffic from the virtual router to the instance. The egress traffic is limited by the rate that applies to the port group used by the instance if any, similar to shared networks."
+msgstr ""
+
+#: ../../service_offerings.rst:515
+# 1a67086f74d24fdca3d3c8ddc160b6a1
+msgid "For example:"
+msgstr ""
+
+#: ../../service_offerings.rst:517
+# 1ef70fcdcb7742dd9f1e68d72b62bab8
+msgid "Network rate of network offering = 10 Mbps"
+msgstr ""
+
+#: ../../service_offerings.rst:519
+# 4aed36fd4b1e47b994e240a5180902f7
+msgid "Network rate of compute offering = 200 Mbps"
+msgstr ""
+
+#: ../../service_offerings.rst:521
+# 728d67e125214dc69bcb42e87a0bd8ae
+msgid "In shared networks, ingress traffic will not be limited for CloudStack, while egress traffic will be limited to 200 Mbps. In an isolated network, ingress traffic will be limited to 10 Mbps and egress to 200 Mbps."
+msgstr ""
+
+#: ../../service_offerings.rst:528
+# c18fc63ba86d45f6a4a69c240bcbd863
+msgid "Changing the Default System Offering for System VMs"
+msgstr ""
+
+#: ../../service_offerings.rst:530
+# dce8139f2a074eda9f35ccab7be40838
+msgid "You can manually change the system offering for a particular System VM. Additionally, as a CloudStack administrator, you can also change the default system offering used for System VMs."
+msgstr ""
+
+#: ../../service_offerings.rst:534
+# d7758b140e8f4c8ea68093fe1bd87309
+msgid "Create a new system offering."
+msgstr ""
+
+#: ../../service_offerings.rst:536
+# 60b70b45018c4c8398470022264172b3
+msgid "For more information, see Creating a New System Service Offering."
+msgstr ""
+
+#: ../../service_offerings.rst:538
+# c8a9263bb9974a9fb39e3ce36805a635
+msgid "Back up the database:"
+msgstr ""
+
+#: ../../service_offerings.rst:544
+# 7a52c92add7a4ae696f4727651be9ba4
+msgid "Open an MySQL prompt:"
+msgstr ""
+
+#: ../../service_offerings.rst:550
+# 51c46ec1b2844020aea4f791b5a5950e
+msgid "Run the following queries on the cloud database."
+msgstr ""
+
+#: ../../service_offerings.rst:552
+# 6ee5a9e0f1d249749376ed26cf656f31
+msgid "In the disk\\_offering table, identify the original default offering and the new offering you want to use by default."
+msgstr ""
+
+#: ../../service_offerings.rst:555
+# 2611865e94844c71b289c6243b7a2e4c
+msgid "Take a note of the ID of the new offering."
+msgstr ""
+
+#: ../../service_offerings.rst:561
+# 31118e91861d48389cbab25fa138f75e
+msgid "For the original default offering, set the value of unique\\_name to NULL."
+msgstr ""
+
+#: ../../service_offerings.rst:568
+# 04fa9b26725d4ca09b7fd864838698ac
+msgid "Ensure that you use the correct value for the ID."
+msgstr ""
+
+#: ../../service_offerings.rst:570
+# 8884980ed2d74f3ab78d5bfec97e5861
+msgid "For the new offering that you want to use by default, set the value of unique\\_name as follows:"
+msgstr ""
+
+#: ../../service_offerings.rst:573
+# bc246e06f82a4bc2a0d1c4ba3aad6618
+msgid "For the default Console Proxy VM (CPVM) offering,set unique\\_name to 'Cloud.com-ConsoleProxy'. For the default Secondary Storage VM (SSVM) offering, set unique\\_name to 'Cloud.com-SecondaryStorage'. For example:"
+msgstr ""
+
+#: ../../service_offerings.rst:582
+# aebfd61c6ee344829f0ec8db45c37d75
+msgid "Restart CloudStack Management Server. Restarting is required because the default offerings are loaded into the memory at startup."
+msgstr ""
+
+#: ../../service_offerings.rst:589
+# 9f700ce4ec00451991c06d4850686fa9
+msgid "Destroy the existing CPVM or SSVM offerings and wait for them to be recreated. The new CPVM or SSVM are configured with the new offering."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/storage.pot b/source/adminguide/locale/pot/storage.pot
new file mode 100644
index 0000000..e6cdb16
--- /dev/null
+++ b/source/adminguide/locale/pot/storage.pot
@@ -0,0 +1,1106 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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"
+
+#: ../../storage.rst:18
+# 32b44221e38d43c08f57ce3a72c53f03
+msgid "Working with Storage"
+msgstr ""
+
+#: ../../storage.rst:21
+# 10d8b20690d442af8af5376748e600e0
+msgid "Storage Overview"
+msgstr ""
+
+#: ../../storage.rst:23
+# 59f0d86b537245ecb2688c84730ca29a
+msgid "CloudStack defines two types of storage: primary and secondary. Primary storage can be accessed by either iSCSI or NFS. Additionally, direct attached storage may be used for primary storage. Secondary storage is always accessed using NFS."
+msgstr ""
+
+#: ../../storage.rst:28
+# 20876e254ad044ddaa6b6090751c79d2
+msgid "There is no ephemeral storage in CloudStack. All volumes on all nodes are persistent."
+msgstr ""
+
+#: ../../storage.rst:33
+# bf8fb32949b941d98036a5312e70d5a4
+msgid "Primary Storage"
+msgstr ""
+
+#: ../../storage.rst:35
+# d56fc829e85b469dae70016a093f1050
+msgid "This section gives concepts and technical details about CloudStack primary storage. For information about how to install and configure primary storage through the CloudStack UI, see the Installation Guide."
+msgstr ""
+
+#: ../../storage.rst:39
+# 950476049a7645b887c0f50e0a4d1f27
+msgid "`“About Primary Storage” <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-primary-storage>`_"
+msgstr ""
+
+#: ../../storage.rst:43
+# c26af650001f4c28b6d9803b7efde40e
+msgid "Best Practices for Primary Storage"
+msgstr ""
+
+#: ../../storage.rst:45
+# 6f52e89385424e26a23b25f5784a3491
+msgid "The speed of primary storage will impact guest performance. If possible, choose smaller, higher RPM drives or SSDs for primary storage."
+msgstr ""
+
+#: ../../storage.rst:49
+# f8f87fc7d7e4415b831b34939cbe9b12
+msgid "There are two ways CloudStack can leverage primary storage:"
+msgstr ""
+
+#: ../../storage.rst:51
+# 52ac4abe89dd4b3586b61386e9b5b0e5
+msgid "Static: This is CloudStack's traditional way of handling storage. In this model, a preallocated amount of storage (ex. a volume from a SAN) is given to CloudStack. CloudStack then permits many of its volumes to be created on this storage (can be root and/or data disks). If using this technique, ensure that nothing is stored on the storage. Adding the storage to CloudStack will destroy any existing data."
+msgstr ""
+
+#: ../../storage.rst:59
+# 813a87ee26ba4259a5c3ef52a1b0ef5a
+msgid "Dynamic: This is a newer way for CloudStack to manage storage. In this model, a storage system (rather than a preallocated amount of storage) is given to CloudStack. CloudStack, working in concert with a storage plug-in, dynamically creates volumes on the storage system and each volume on the storage system maps to a single CloudStack volume. This is highly useful for features such as storage Quality of Service. Currently this feature is supported for data disks (Disk Offerings)."
+msgstr ""
+
+#: ../../storage.rst:70
+# f97cbc96312f49aba2a6bab0d1e1b2a4
+msgid "Runtime Behavior of Primary Storage"
+msgstr ""
+
+#: ../../storage.rst:72
+# 5bf02a65cf3a40df9e7e165fd9ecd864
+msgid "Root volumes are created automatically when a virtual machine is created. Root volumes are deleted when the VM is destroyed. Data volumes can be created and dynamically attached to VMs. Data volumes are not deleted when VMs are destroyed."
+msgstr ""
+
+#: ../../storage.rst:77
+# 80ad3630b276444cac7f5324ecf5a326
+msgid "Administrators should monitor the capacity of primary storage devices and add additional primary storage as needed. See the Advanced Installation Guide."
+msgstr ""
+
+#: ../../storage.rst:81
+# 073d4376c5e04c77bbfdba19e134418c
+msgid "Administrators add primary storage to the system by creating a CloudStack storage pool. Each storage pool is associated with a cluster or a zone."
+msgstr ""
+
+#: ../../storage.rst:85
+# 79ff1a8b27224fff8510e3a5ce37a304
+msgid "With regards to data disks, when a user executes a Disk Offering to create a data disk, the information is initially written to the CloudStack database only. Upon the first request that the data disk be attached to a VM, CloudStack determines what storage to place the volume on and space is taken from that storage (either from preallocated storage or from a storage system (ex. a SAN), depending on how the primary storage was added to CloudStack)."
+msgstr ""
+
+#: ../../storage.rst:95
+# 03d9238ac1b44704b10a3c6cbc9a194c
+msgid "Hypervisor Support for Primary Storage"
+msgstr ""
+
+#: ../../storage.rst:97
+# f9043e1c7c614dcab5cc48b83c777751
+msgid "The following table shows storage options and parameters for different hypervisors."
+msgstr ""
+
+#: ../../storage.rst:101
+# df81aa4abfe0426f8ea7b5d76689b532
+msgid "Storage media \\\\ hypervisor"
+msgstr ""
+
+#: ../../storage.rst:101
+#: ../../storage.rst:709
+# 21dd8b1cdc0d40dc8559cbcf4fbfab3d
+# 6e7b702add314a16a42c7e999147c3c9
+msgid "VMware vSphere"
+msgstr ""
+
+#: ../../storage.rst:101
+#: ../../storage.rst:709
+# 95085080f31c48d7a3c6eeb26d596976
+# fd649d92db414b198a27e37febfdfe07
+msgid "Citrix XenServer"
+msgstr ""
+
+#: ../../storage.rst:101
+#: ../../storage.rst:332
+#: ../../storage.rst:709
+# 94199ee2b07049529bc3e9c2b7eb8707
+# 7b0dbf552cc34bb0ac898f31180f3a83
+# 3f78f67d3c14490da80f847d2a00fc5d
+msgid "KVM"
+msgstr ""
+
+#: ../../storage.rst:101
+# b63b5cf8a70b492f82138dc7fd0b3d4f
+msgid "Hyper-V"
+msgstr ""
+
+#: ../../storage.rst:103
+# 6b911e3d65954475be2786623c89bfee
+msgid "**Format for Disks, Templates, and Snapshots**"
+msgstr ""
+
+#: ../../storage.rst:103
+# 597a7a22248749eab119febe7cad0654
+msgid "VMDK"
+msgstr ""
+
+#: ../../storage.rst:103
+#: ../../storage.rst:330
+# dcb226ea6af24150b270ebd0e57ce0d6
+# 06b1f702f7ae492c9259258d6cdb9bba
+msgid "VHD"
+msgstr ""
+
+#: ../../storage.rst:103
+#: ../../storage.rst:332
+# 3c8131f767e745659f09e7635e52de1d
+# 891d2deb650249bdaaa476d91cedea41
+msgid "QCOW2"
+msgstr ""
+
+#: ../../storage.rst:103
+# 0ef733d6419b49ddb03a35218b141dad
+msgid "VHD Snapshots are not supported."
+msgstr ""
+
+#: ../../storage.rst:105
+# 366c31ae3c524e20bcbff9f5b0f33865
+msgid "**iSCSI support**"
+msgstr ""
+
+#: ../../storage.rst:105
+#: ../../storage.rst:106
+# 169329b4d94f4d5a9a71e806fc6493ee
+# eb8734785e1e4253ae29efadaea66c18
+msgid "VMFS"
+msgstr ""
+
+#: ../../storage.rst:105
+# 439fbab809dc46b291a52de0067fb0f5
+msgid "Clustered LVM"
+msgstr ""
+
+#: ../../storage.rst:105
+#: ../../storage.rst:106
+# 7166fec7c32746bea34118f3db301ae6
+# aa36e5087ca64a9590ad2b643c91d5f7
+msgid "Yes, via Shared Mountpoint"
+msgstr ""
+
+#: ../../storage.rst:105
+#: ../../storage.rst:106
+#: ../../storage.rst:107
+#: ../../storage.rst:109
+#: ../../storage.rst:110
+#: ../../storage.rst:110
+#: ../../storage.rst:110
+#: ../../storage.rst:711
+#: ../../storage.rst:711
+# 03d269fc73bc48348ab1896256774ae1
+# ce5af21795294bc697ba5aa4474636da
+# 785a027864c94241bdfc6686ade2836e
+# 3099d25cace04a4788cd2531e69b4710
+# 2e285148115d4a2da6cae3f373aba27f
+# 895e4b1ff76840cc94de98328f387f6f
+# 8353d798b3004fb5bbd003df12fac8a2
+# 9695a4455edd45c899785834ba6fef74
+# 7857cd4194be451faa95e02696061cf8
+msgid "No"
+msgstr ""
+
+#: ../../storage.rst:106
+# b70b0d5267be474c85b0240f24b6a2b9
+msgid "**Fiber Channel support**"
+msgstr ""
+
+#: ../../storage.rst:106
+# 443c6e664d6b46a9a0f879410a6e1aa7
+msgid "Yes, via Existing SR"
+msgstr ""
+
+#: ../../storage.rst:107
+# b46dc3d64ece43109c0051e5fc0d66e5
+msgid "**NFS support**"
+msgstr ""
+
+#: ../../storage.rst:107
+#: ../../storage.rst:107
+#: ../../storage.rst:107
+#: ../../storage.rst:108
+#: ../../storage.rst:108
+#: ../../storage.rst:108
+#: ../../storage.rst:108
+#: ../../storage.rst:110
+#: ../../storage.rst:711
+# ac7f31ad38674dd5bd5040d072b67e09
+# de71afbac6cb457caff9416ed30e2d9c
+# 12e7d7ffb19d4610a624484aaffeebf2
+# 10601f00b2d54ae1833a5b8cf47428ea
+# cfade3e6b2824c0b8ae1ddfc34d36e9a
+# 4b311bb6db4b41779b0c525c589c00a7
+# 6ab3b70adba24666a78774746ccfabad
+# bed48ae68b8e4818aad52abb69bbc24b
+# 11121f7bcfdc45db85459a8f12982e26
+msgid "Yes"
+msgstr ""
+
+#: ../../storage.rst:108
+# 8c9b266cc80241eda65595fd19a54dc7
+msgid "**Local storage support**"
+msgstr ""
+
+#: ../../storage.rst:109
+# 1b48c07eb50544109f66a49c39c5d38c
+msgid "**Storage over-provisioning**"
+msgstr ""
+
+#: ../../storage.rst:109
+# 36ee1094090c495d95a6a7650892ffae
+msgid "NFS and iSCSI"
+msgstr ""
+
+#: ../../storage.rst:109
+#: ../../storage.rst:109
+# 565842e982394810bcd8454836b9b271
+# bb172a9d571244538e501ba593025cd6
+msgid "NFS"
+msgstr ""
+
+#: ../../storage.rst:110
+# a5915b6a85a64a268e5a1e41080fa835
+msgid "**SMB/CIFS**"
+msgstr ""
+
+#: ../../storage.rst:113
+# 8f37dda63c1a49f084a39311ad775fd6
+msgid "XenServer uses a clustered LVM system to store VM images on iSCSI and Fiber Channel volumes and does not support over-provisioning in the hypervisor. The storage server itself, however, can support thin-provisioning. As a result the CloudStack can still support storage over-provisioning by running on thin-provisioned storage volumes."
+msgstr ""
+
+#: ../../storage.rst:119
+# d8bfde747fd541bcb2d1f62d1d2ddd9c
+msgid "KVM supports \"Shared Mountpoint\" storage. A shared mountpoint is a file system path local to each server in a given cluster. The path must be the same across all Hosts in the cluster, for example /mnt/primary1. This shared mountpoint is assumed to be a clustered filesystem such as OCFS2. In this case the CloudStack does not attempt to mount or unmount the storage as is done with NFS. The CloudStack requires that the administrator insure that the storage is available"
+msgstr ""
+
+#: ../../storage.rst:127
+# 80ebb012a77045e9b3a5a47d82cef42c
+msgid "With NFS storage, CloudStack manages the overprovisioning. In this case the global configuration parameter storage.overprovisioning.factor controls the degree of overprovisioning. This is independent of hypervisor type."
+msgstr ""
+
+#: ../../storage.rst:132
+# 46f7d4fdff4d4ea996d136375ac93805
+msgid "Local storage is an option for primary storage for vSphere, XenServer, and KVM. When the local disk option is enabled, a local disk storage pool is automatically created on each host. To use local storage for the System Virtual Machines (such as the Virtual Router), set system.vm.use.local.storage to true in global configuration."
+msgstr ""
+
+#: ../../storage.rst:138
+# 84339fc995ab461cb30e853b024629a4
+msgid "CloudStack supports multiple primary storage pools in a Cluster. For example, you could provision 2 NFS servers in primary storage. Or you could provision 1 iSCSI LUN initially and then add a second iSCSI LUN when the first approaches capacity."
+msgstr ""
+
+#: ../../storage.rst:145
+# 16767f52da5e4a3ea351cb7c2208207a
+msgid "Storage Tags"
+msgstr ""
+
+#: ../../storage.rst:147
+# d0ffba1bad5942adaca099b572104c63
+msgid "Storage may be \"tagged\". A tag is a text string attribute associated with primary storage, a Disk Offering, or a Service Offering. Tags allow administrators to provide additional information about the storage. For example, that is a \"SSD\" or it is \"slow\". Tags are not interpreted by CloudStack. They are matched against tags placed on service and disk offerings. CloudStack requires all tags on service and disk offerings to exist on the primary storage before it allocates root or data disks on the primary storage. Service and disk offering tags are used to identify the requirements of the storage that those offerings have. For example, the high end service offering may require \"fast\" for its root disk volume."
+msgstr ""
+
+#: ../../storage.rst:159
+# 81b0523239f34456bfe222f88c9520e0
+msgid "The interaction between tags, allocation, and volume copying across clusters and pods can be complex. To simplify the situation, use the same set of tags on the primary storage for all clusters in a pod. Even if different devices are used to present those tags, the set of exposed tags can be the same."
+msgstr ""
+
+#: ../../storage.rst:167
+# b85907f2a2a546ae9312b9c9d9a443e3
+msgid "Maintenance Mode for Primary Storage"
+msgstr ""
+
+#: ../../storage.rst:169
+# 0e84968be86b4971b80b0b9f4f141840
+msgid "Primary storage may be placed into maintenance mode. This is useful, for example, to replace faulty RAM in a storage device. Maintenance mode for a storage device will first stop any new guests from being provisioned on the storage device. Then it will stop all guests that have any volume on that storage device. When all such guests are stopped the storage device is in maintenance mode and may be shut down. When the storage device is online again you may cancel maintenance mode for the device. The CloudStack will bring the device back online and attempt to start all guests that were running at the time of the entry into maintenance mode."
+msgstr ""
+
+#: ../../storage.rst:182
+# 67a803ad730347ec9a5e5667d7ceadfa
+msgid "Secondary Storage"
+msgstr ""
+
+#: ../../storage.rst:184
+# d48d908ab2384420a19689dfc1957c12
+msgid "This section gives concepts and technical details about CloudStack secondary storage. For information about how to install and configure secondary storage through the CloudStack UI, see the Advanced Installation Guide."
+msgstr ""
+
+#: ../../storage.rst:189
+# 4c9b91f3c5dd4d8a83a8c2706ac95f41
+msgid "`“About Secondary Storage” <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-secondary-storage>`_"
+msgstr ""
+
+#: ../../storage.rst:193
+# 6ca82acb4184482298cdd589b41fdd16
+msgid "Working With Volumes"
+msgstr ""
+
+#: ../../storage.rst:195
+# d8b653a972c54421a4405a011c4ca3e7
+msgid "A volume provides storage to a guest VM. The volume can provide for a root disk or an additional data disk. CloudStack supports additional volumes for guest VMs."
+msgstr ""
+
+#: ../../storage.rst:199
+# 2197b194989d434ca7e999eb0f6cfaa9
+msgid "Volumes are created for a specific hypervisor type. A volume that has been attached to guest using one hypervisor type (e.g, XenServer) may not be attached to a guest that is using another hypervisor type, for example:vSphere, KVM. This is because the different hypervisors use different disk image formats."
+msgstr ""
+
+#: ../../storage.rst:205
+# 6d23b58657fd41c2aba08ac7ae7eaabe
+msgid "CloudStack defines a volume as a unit of storage available to a guest VM. Volumes are either root disks or data disks. The root disk has \"/\" in the file system and is usually the boot device. Data disks provide for additional storage, for example: \"/opt\" or \"D:\". Every guest VM has a root disk, and VMs can also optionally have a data disk. End users can mount multiple data disks to guest VMs. Users choose data disks from the disk offerings created by administrators. The user can create a template from a volume as well; this is the standard procedure for private template creation. Volumes are hypervisor-specific: a volume from one hypervisor type may not be used on a guest of another hypervisor type."
+msgstr ""
+
+#: ../../storage.rst:217
+# 0dfd84618eba4890bd79fdde4a5681c2
+msgid "CloudStack supports attaching up to 13 data disks to a VM on XenServer hypervisor versions 6.0 and above. For the VMs on other hypervisor types, the data disk limit is 6."
+msgstr ""
+
+#: ../../storage.rst:223
+# f423c15d3d884dd295629f532792322b
+msgid "Creating a New Volume"
+msgstr ""
+
+#: ../../storage.rst:225
+# 288ba1fb3a644f05a3cd4b08e05b1524
+msgid "You can add more data disk volumes to a guest VM at any time, up to the limits of your storage capacity. Both CloudStack administrators and users can add volumes to VM instances. When you create a new volume, it is stored as an entity in CloudStack, but the actual storage resources are not allocated on the physical storage device until you attach the volume. This optimization allows the CloudStack to provision the volume nearest to the guest that will use it when the first attachment is made."
+msgstr ""
+
+#: ../../storage.rst:235
+# 09420f12f6d84b9ebe5882b8a922b802
+msgid "Using Local Storage for Data Volumes"
+msgstr ""
+
+#: ../../storage.rst:237
+# 87d84c3ad80f4c65ae01116db8e49f5b
+msgid "You can create data volumes on local storage (supported with XenServer, KVM, and VMware). The data volume is placed on the same host as the VM instance that is attached to the data volume. These local data volumes can be attached to virtual machines, detached, re-attached, and deleted just as with the other types of data volume."
+msgstr ""
+
+#: ../../storage.rst:243
+# 2092c3e84a0040c88df79f6600d12b26
+msgid "Local storage is ideal for scenarios where persistence of data volumes and HA is not required. Some of the benefits include reduced disk I/O latency and cost reduction from using inexpensive local disks."
+msgstr ""
+
+#: ../../storage.rst:247
+# 24091baabed046c79bbde0f55cc59de6
+msgid "In order for local volumes to be used, the feature must be enabled for the zone."
+msgstr ""
+
+#: ../../storage.rst:250
+# a3fc0fa189a444759468f8645397fc0a
+msgid "You can create a data disk offering for local storage. When a user creates a new VM, they can select this disk offering in order to cause the data disk volume to be placed in local storage."
+msgstr ""
+
+#: ../../storage.rst:254
+# 2884a62219544ddea52e40fbabdfc590
+msgid "You can not migrate a VM that has a volume in local storage to a different host, nor migrate the volume itself away to a different host. If you want to put a host into maintenance mode, you must first stop any VMs with local data volumes on that host."
+msgstr ""
+
+#: ../../storage.rst:261
+# 427238ca555946cc8792695ca92136df
+msgid "To Create a New Volume"
+msgstr ""
+
+#: ../../storage.rst:263
+#: ../../storage.rst:357
+#: ../../storage.rst:390
+#: ../../storage.rst:456
+#: ../../storage.rst:477
+#: ../../storage.rst:506
+#: ../../storage.rst:562
+# 70f2f0de47b04a1cbb185fe77792e139
+# 629422b536114a33be189acc56c6cc01
+# 541ad7fafe48443d97a67692a359748c
+# b61f2bef29ea454bb44952aebc53c22c
+# 0e5cea32ef9848a0a96a9ede62313c86
+# 8e3b1d8db33d44fabb0894f24d17d358
+# e35965b604404bef9f199b32675ad907
+msgid "Log in to the CloudStack UI as a user or admin."
+msgstr ""
+
+#: ../../storage.rst:265
+#: ../../storage.rst:312
+#: ../../storage.rst:564
+#: ../../storage.rst:664
+# 146d31151f5e442c8b76e9ef512eac29
+# 11db8955c3494f43b8d2e1bc13a914df
+# 54c24ff429df4622aa1ce17ff0817663
+# f9babc8c9c9941049be79d67a3c60c82
+msgid "In the left navigation bar, click Storage."
+msgstr ""
+
+#: ../../storage.rst:267
+#: ../../storage.rst:361
+#: ../../storage.rst:566
+# 9df84607b2a94838bb6739342d1e0bd7
+# 1f30687ee1374b74bb647174e701cc9b
+# 47fcd7e70cc34717b426f9bf08a626c8
+msgid "In Select View, choose Volumes."
+msgstr ""
+
+#: ../../storage.rst:269
+# d9affc0389314e7cadbe9e0340e6bddd
+msgid "To create a new volume, click Add Volume, provide the following details, and click OK."
+msgstr ""
+
+#: ../../storage.rst:272
+# 8aa967b67394416b9971e9986853fc0e
+msgid "Name. Give the volume a unique name so you can find it later."
+msgstr ""
+
+#: ../../storage.rst:274
+# b95f18a10ac946d8bb6e4424522125a5
+msgid "Availability Zone. Where do you want the storage to reside? This should be close to the VM that will use the volume."
+msgstr ""
+
+#: ../../storage.rst:277
+# 55b275ed6b1b4c7e965e8d9c3fc64d99
+msgid "Disk Offering. Choose the characteristics of the storage."
+msgstr ""
+
+#: ../../storage.rst:279
+# 75cbb5f7984642d8a86bb71c3f274c52
+msgid "The new volume appears in the list of volumes with the state “Allocated.” The volume data is stored in CloudStack, but the volume is not yet ready for use"
+msgstr ""
+
+#: ../../storage.rst:283
+# 97a7e13d891c4ab78df0cd8ebcafdfc7
+msgid "To start using the volume, continue to Attaching a Volume"
+msgstr ""
+
+#: ../../storage.rst:287
+# 890dc04ff24f497186a44bb7d537412d
+msgid "Uploading an Existing Volume to a Virtual Machine"
+msgstr ""
+
+#: ../../storage.rst:289
+# 17f14f4d6eec4e609b6e183abaa18556
+msgid "Existing data can be made accessible to a virtual machine. This is called uploading a volume to the VM. For example, this is useful to upload data from a local file system and attach it to a VM. Root administrators, domain administrators, and end users can all upload existing volumes to VMs."
+msgstr ""
+
+#: ../../storage.rst:295
+# f18a289b1dae403cb4a540ec6280499b
+msgid "The upload is performed using HTTP. The uploaded volume is placed in the zone's secondary storage"
+msgstr ""
+
+#: ../../storage.rst:298
+# e22b07fc396b4455bf886c103b353298
+msgid "You cannot upload a volume if the preconfigured volume limit has already been reached. The default limit for the cloud is set in the global configuration parameter max.account.volumes, but administrators can also set per-domain limits that are different from the global default. See Setting Usage Limits"
+msgstr ""
+
+#: ../../storage.rst:304
+# e8b13fa3aadd48cca116ddff3d8ac16a
+msgid "To upload a volume:"
+msgstr ""
+
+#: ../../storage.rst:306
+# 2032475f0e514f0d87b48fde37cfda03
+msgid "(Optional) Create an MD5 hash (checksum) of the disk image file that you are going to upload. After uploading the data disk, CloudStack will use this value to verify that no data corruption has occurred."
+msgstr ""
+
+#: ../../storage.rst:310
+# 0fc87857d60e4b6e8d2d80130b6dd64d
+msgid "Log in to the CloudStack UI as an administrator or user"
+msgstr ""
+
+#: ../../storage.rst:314
+# cfa804b4dc5e4b539613e1693f19c041
+msgid "Click Upload Volume."
+msgstr ""
+
+#: ../../storage.rst:316
+# b664bc425cd54ca4917358c8830843e7
+msgid "Provide the following:"
+msgstr ""
+
+#: ../../storage.rst:318
+# 33a6b2a32f3646e98a44862cba5bea26
+msgid "Name and Description. Any desired name and a brief description that can be shown in the UI."
+msgstr ""
+
+#: ../../storage.rst:321
+# 1c773983c9a14bda81f657b9831390d5
+msgid "Availability Zone. Choose the zone where you want to store the volume. VMs running on hosts in this zone can attach the volume."
+msgstr ""
+
+#: ../../storage.rst:324
+# d0263e16ccf649a88f3265f9cbd34b80
+msgid "Format. Choose one of the following to indicate the disk image format of the volume."
+msgstr ""
+
+#: ../../storage.rst:328
+# 9e62f8681cf6466c87525f623ab74761
+msgid "Hypervisor"
+msgstr ""
+
+#: ../../storage.rst:328
+# 18fa4b974ece4a8fae34fccd9062dc6a
+msgid "Disk Image Format"
+msgstr ""
+
+#: ../../storage.rst:330
+# fd430608386e4e7db755bcbf9a932e8a
+msgid "XenServer"
+msgstr ""
+
+#: ../../storage.rst:331
+# 6e5d75ea06c7464cb4ec871161a4a108
+msgid "VMware"
+msgstr ""
+
+#: ../../storage.rst:331
+# 01efef53521d4f8189c939afdd9c1cbb
+msgid "OVA"
+msgstr ""
+
+#: ../../storage.rst:335
+# 9e300c5607d34ce6837b1817e414992a
+msgid "URL. The secure HTTP or HTTPS URL that CloudStack can use to access your disk. The type of file at the URL must match the value chosen in Format. For example, if Format is VHD, the URL might look like the following:"
+msgstr ""
+
+#: ../../storage.rst:340
+# 82d85bc5e5704af5a3256a92d5c02114
+msgid "``http://yourFileServerIP/userdata/myDataDisk.vhd``"
+msgstr ""
+
+#: ../../storage.rst:342
+# 2a1e40703cff43efba2d4349b3a16219
+msgid "MD5 checksum. (Optional) Use the hash that you created in step 1."
+msgstr ""
+
+#: ../../storage.rst:344
+# c13069ba6499470eb80792d35b8177e5
+msgid "Wait until the status of the volume shows that the upload is complete. Click Instances - Volumes, find the name you specified in step 5, and make sure the status is Uploaded."
+msgstr ""
+
+#: ../../storage.rst:350
+# 0fd449f8d801478d84a4b2700da5e8b6
+msgid "Attaching a Volume"
+msgstr ""
+
+#: ../../storage.rst:352
+# da2f32e627974c378217daaed2a05282
+msgid "You can attach a volume to a guest VM to provide extra disk storage. Attach a volume when you first create a new volume, when you are moving an existing volume from one VM to another, or after you have migrated a volume from one storage pool to another."
+msgstr ""
+
+#: ../../storage.rst:359
+# e98f959945e047bc950d507b756c28e7
+msgid "In the left navigation, click Storage."
+msgstr ""
+
+#: ../../storage.rst:363
+# 4334745af8f24f039eba4f0736befe7f
+msgid "Click the volume name in the Volumes list, then click the Attach Disk button |AttachDiskButton.png|"
+msgstr ""
+
+#: ../../storage.rst:366
+# 0840d7b567f84dbcbf9820547c2e68b2
+msgid "In the Instance popup, choose the VM to which you want to attach the volume. You will only see instances to which you are allowed to attach volumes; for example, a user will see only instances created by that user, but the administrator will have more choices."
+msgstr ""
+
+#: ../../storage.rst:371
+# 6e680f84bdb84267a7d2d60e4e7fcdf9
+msgid "When the volume has been attached, you should be able to see it by clicking Instances, the instance name, and View Volumes."
+msgstr ""
+
+#: ../../storage.rst:376
+# dc8f48c99c24477fa1924ef7a1fb28dc
+msgid "Detaching and Moving Volumes"
+msgstr ""
+
+#: ../../storage.rst:379
+# 988a57d9e81b49e6be5b37db8f4970c2
+msgid "This procedure is different from moving volumes from one storage pool to another as described in `“VM Storage Migration” <#vm-storage-migration>`_."
+msgstr ""
+
+#: ../../storage.rst:383
+# 87a675231744495a92d09e12337edda0
+msgid "A volume can be detached from a guest VM and attached to another guest. Both CloudStack administrators and users can detach volumes from VMs and move them to other VMs."
+msgstr ""
+
+#: ../../storage.rst:387
+# f3a14cfb3fe242fd95952025a2f91323
+msgid "If the two VMs are in different clusters, and the volume is large, it may take several minutes for the volume to be moved to the new VM."
+msgstr ""
+
+#: ../../storage.rst:392
+# 8c279d5d59154e34b12465e6c1b2088a
+msgid "In the left navigation bar, click Storage, and choose Volumes in Select View. Alternatively, if you know which VM the volume is attached to, you can click Instances, click the VM name, and click View Volumes."
+msgstr ""
+
+#: ../../storage.rst:397
+# 02ba88b018e140248a056d426fd7c9ea
+msgid "Click the name of the volume you want to detach, then click the Detach Disk button. |DetachDiskButton.png|"
+msgstr ""
+
+#: ../../storage.rst:400
+# 2ef3b0f777434eb58770702236698b0d
+msgid "To move the volume to another VM, follow the steps in `“Attaching a Volume” <#attaching-a-volume>`_."
+msgstr ""
+
+#: ../../storage.rst:405
+# 7bce94ec5cda4cfd9031d62fa230127d
+msgid "VM Storage Migration"
+msgstr ""
+
+#: ../../storage.rst:407
+# 1bc602fbceb14e5ab29eb5e9189ae80d
+msgid "Supported in XenServer, KVM, and VMware."
+msgstr ""
+
+#: ../../storage.rst:410
+# 8183ae7d15c748109dabfa42d80894c4
+msgid "This procedure is different from moving disk volumes from one VM to another as described in `“Detaching and Moving Volumes” <#detaching-and-moving-volumes>`_."
+msgstr ""
+
+#: ../../storage.rst:414
+# 1124cbad549d456f858d2dd00e5689b4
+msgid "You can migrate a virtual machine’s root disk volume or any additional data disk volume from one storage pool to another in the same zone."
+msgstr ""
+
+#: ../../storage.rst:417
+# cb9592a82bf84a7c8393f53e9e18ef77
+msgid "You can use the storage migration feature to achieve some commonly desired administration goals, such as balancing the load on storage pools and increasing the reliability of virtual machines by moving them away from any storage pool that is experiencing issues."
+msgstr ""
+
+#: ../../storage.rst:422
+# a2bcc01e8bd8426dba63dd8846123778
+msgid "On XenServer and VMware, live migration of VM storage is enabled through CloudStack support for XenMotion and vMotion. Live storage migration allows VMs to be moved from one host to another, where the VMs are not located on storage shared between the two hosts. It provides the option to live migrate a VM’s disks along with the VM itself. It is possible to migrate a VM from one XenServer resource pool / VMware cluster to another, or to migrate a VM whose disks are on local storage, or even to migrate a VM’s disks from one storage repository to another, all while the VM is running."
+msgstr ""
+
+#: ../../storage.rst:433
+# ebbd4f4ab1654020b6c6bd65f6c8bf34
+msgid "Because of a limitation in VMware, live migration of storage for a VM is allowed only if the source and target storage pool are accessible to the source host; that is, the host where the VM is running when the live migration operation is requested."
+msgstr ""
+
+#: ../../storage.rst:440
+# ebbe88108b474e6fbcb0bf7db34d5473
+msgid "Migrating a Data Volume to a New Storage Pool"
+msgstr ""
+
+#: ../../storage.rst:442
+# c5d71980858c4c34a0fa4c90024e9f49
+msgid "There are two situations when you might want to migrate a disk:"
+msgstr ""
+
+#: ../../storage.rst:444
+# 787fcb424e3a474794856b6e4c36294a
+msgid "Move the disk to new storage, but leave it attached to the same running VM."
+msgstr ""
+
+#: ../../storage.rst:447
+# d3a83f9da3984d7285731f35b1577f61
+msgid "Detach the disk from its current VM, move it to new storage, and attach it to a new VM."
+msgstr ""
+
+#: ../../storage.rst:452
+# 47132cdecc7e40bdbe0b73b197292474
+msgid "Migrating Storage For a Running VM"
+msgstr ""
+
+#: ../../storage.rst:454
+# 49fb8bbee6ed48a0a77ef96befb12bde
+msgid "(Supported on XenServer and VMware)"
+msgstr ""
+
+#: ../../storage.rst:458
+# 22e57c1b2aa74b2681ccf49f19103618
+msgid "In the left navigation bar, click Instances, click the VM name, and click View Volumes."
+msgstr ""
+
+#: ../../storage.rst:461
+# afc084613de9415cb23e3125751a0dbe
+msgid "Click the volume you want to migrate."
+msgstr ""
+
+#: ../../storage.rst:463
+#: ../../storage.rst:479
+# 162037fc56d042c085a994af770ebe2c
+# 35b4f135a003412db306d5c378f6f2b8
+msgid "Detach the disk from the VM. See `“Detaching and Moving Volumes” <#detaching-and-moving-volumes>`_ but skip the “reattach” step at the end. You will do that after migrating to new storage."
+msgstr ""
+
+#: ../../storage.rst:467
+#: ../../storage.rst:483
+# bc76fcc2fe05464dbd69894e5d2d4746
+# d3951fd18db542b9b7fa617306a1f07c
+msgid "Click the Migrate Volume button |Migrateinstance.png| and choose the destination from the dropdown list."
+msgstr ""
+
+#: ../../storage.rst:470
+# 98ce5d9b63084686a8b2a0c0ad1bf658
+msgid "Watch for the volume status to change to Migrating, then back to Ready."
+msgstr ""
+
+#: ../../storage.rst:475
+# f5d81aecca72450bac7269a86bf20b26
+msgid "Migrating Storage and Attaching to a Different VM"
+msgstr ""
+
+#: ../../storage.rst:486
+# 614797ab3f9a44f08c275e1f6ed61f13
+msgid "Watch for the volume status to change to Migrating, then back to Ready. You can find the volume by clicking Storage in the left navigation bar. Make sure that Volumes is displayed at the top of the window, in the Select View dropdown."
+msgstr ""
+
+#: ../../storage.rst:491
+# 5dafaedc6390428eb94978091d3808ad
+msgid "Attach the volume to any desired VM running in the same cluster as the new storage server. See `“Attaching a Volume” <#attaching-a-volume>`_"
+msgstr ""
+
+#: ../../storage.rst:497
+# 2b29f819fd9f4a61b39cd73dbc205e65
+msgid "Migrating a VM Root Volume to a New Storage Pool"
+msgstr ""
+
+#: ../../storage.rst:499
+# 2fdc3aca153f473fac5ef5e7ba874b2a
+msgid "(XenServer, VMware) You can live migrate a VM's root disk from one storage pool to another, without stopping the VM first."
+msgstr ""
+
+#: ../../storage.rst:502
+# f6a2cc4f4e2c40ce85564e77487a6051
+msgid "(KVM) When migrating the root disk volume, the VM must first be stopped, and users can not access the VM. After migration is complete, the VM can be restarted."
+msgstr ""
+
+#: ../../storage.rst:508
+# 99e0360f9cff4f3595658d757416655e
+msgid "In the left navigation bar, click Instances, and click the VM name."
+msgstr ""
+
+#: ../../storage.rst:510
+# 40a52b70ece74eeb83347bcca88c58c0
+msgid "(KVM only) Stop the VM."
+msgstr ""
+
+#: ../../storage.rst:512
+# 918eb301d15e4e369656d3ab9c3eb850
+msgid "Click the Migrate button |Migrateinstance.png| and choose the destination from the dropdown list."
+msgstr ""
+
+#: ../../storage.rst:516
+# d43200e809304acdad782782547fe7b0
+msgid "If the VM's storage has to be migrated along with the VM, this will be noted in the host list. CloudStack will take care of the storage migration for you."
+msgstr ""
+
+#: ../../storage.rst:520
+# 7e0343377d674714bb987eed30d9687e
+msgid "Watch for the volume status to change to Migrating, then back to Running (or Stopped, in the case of KVM). This can take some time."
+msgstr ""
+
+#: ../../storage.rst:523
+# cf995ac6b00e4ede877a0a869d35d0c3
+msgid "(KVM only) Restart the VM."
+msgstr ""
+
+#: ../../storage.rst:527
+# fe6a0aed97e24cd7a80e1e10b113296f
+msgid "Resizing Volumes"
+msgstr ""
+
+#: ../../storage.rst:529
+# d5de1d251de94750aef7188031910714
+msgid "CloudStack provides the ability to resize data disks; CloudStack controls volume size by using disk offerings. This provides CloudStack administrators with the flexibility to choose how much space they want to make available to the end users. Volumes within the disk offerings with the same storage tag can be resized. For example, if you only want to offer 10, 50, and 100 GB offerings, the allowed resize should stay within those limits. That implies if you define a 10 GB, a 50 GB and a 100 GB disk offerings, a user can upgrade from 10 GB to 50 GB, or 50 GB to 100 GB. If you create a custom-sized disk offering, then you have the option to resize the volume by specifying a new, larger size."
+msgstr ""
+
+#: ../../storage.rst:540
+# 6111e137df7f47a99f428cab9e407bda
+msgid "Additionally, using the resizeVolume API, a data volume can be moved from a static disk offering to a custom disk offering with the size specified. This functionality allows those who might be billing by certain volume sizes or disk offerings to stick to that model, while providing the flexibility to migrate to whatever custom size necessary."
+msgstr ""
+
+#: ../../storage.rst:546
+# c25a67ebb3344e2c951583bec9826b9e
+msgid "This feature is supported on KVM, XenServer, and VMware hosts. However, shrinking volumes is not supported on VMware hosts."
+msgstr ""
+
+#: ../../storage.rst:549
+# f3d3d1c66a9a46a49a97000ce2d104ee
+msgid "Before you try to resize a volume, consider the following:"
+msgstr ""
+
+#: ../../storage.rst:551
+# 1c0434424baf4f79a95622559c9119b2
+msgid "The VMs associated with the volume are stopped."
+msgstr ""
+
+#: ../../storage.rst:553
+# bb545d0a9cf34f5e864a5b016d15775d
+msgid "The data disks associated with the volume are removed."
+msgstr ""
+
+#: ../../storage.rst:555
+# 157e4971d3784646a5df1fc2c27026fa
+msgid "When a volume is shrunk, the disk associated with it is simply truncated, and doing so would put its content at risk of data loss. Therefore, resize any partitions or file systems before you shrink a data disk so that all the data is moved off from that disk."
+msgstr ""
+
+#: ../../storage.rst:560
+# ea92d28ccffe4acbb40da15110829f69
+msgid "To resize a volume:"
+msgstr ""
+
+#: ../../storage.rst:568
+# 4bcbe35ab7f749c49a97fc0b69386143
+msgid "Select the volume name in the Volumes list, then click the Resize Volume button |resize-volume-icon.png|"
+msgstr ""
+
+#: ../../storage.rst:571
+# 7e6057281d384902b45704d88725b3b2
+msgid "In the Resize Volume pop-up, choose desired characteristics for the storage."
+msgstr ""
+
+#: ../../storage.rst:574
+# 837580ae5e7d422eb6d54ca24b547f32
+msgid "|resize-volume.png|"
+msgstr ""
+
+#: ../../storage.rst:576
+# 2a4fef4505014a8c9cee37ce70dc08a3
+msgid "If you select Custom Disk, specify a custom size."
+msgstr ""
+
+#: ../../storage.rst:578
+# 0f0109182c0345099ae713929c4c1f4d
+msgid "Click Shrink OK to confirm that you are reducing the size of a volume."
+msgstr ""
+
+#: ../../storage.rst:581
+# 86a5314fba614528805c75a1ce993c5b
+msgid "This parameter protects against inadvertent shrinking of a disk, which might lead to the risk of data loss. You must sign off that you know what you are doing."
+msgstr ""
+
+#: ../../storage.rst:585
+# fa1e5898785847d0acd130136d2b3e4b
+msgid "Click OK."
+msgstr ""
+
+#: ../../storage.rst:589
+# 7416d78fc57b4a21a1c5a748c35efa62
+msgid "Reset VM to New Root Disk on Reboot"
+msgstr ""
+
+#: ../../storage.rst:591
+# aa266ce7558249a58dc21c85bbe527c1
+msgid "You can specify that you want to discard the root disk and create a new one whenever a given VM is rebooted. This is useful for secure environments that need a fresh start on every boot and for desktops that should not retain state. The IP address of the VM will not change due to this operation."
+msgstr ""
+
+#: ../../storage.rst:597
+# f4a034b658174e23b49d8a0dae7faf9d
+msgid "**To enable root disk reset on VM reboot:**"
+msgstr ""
+
+#: ../../storage.rst:599
+# 0d8e7c9c2b4b461bb00b40c89b19ca07
+msgid "When creating a new service offering, set the parameter isVolatile to True. VMs created from this service offering will have their disks reset upon reboot. See `“Creating a New Compute Offering” <service_offerings.html#creating-a-new-compute-offering>`_."
+msgstr ""
+
+#: ../../storage.rst:606
+# 80b7517a265a468a91758a97f1049265
+msgid "Volume Deletion and Garbage Collection"
+msgstr ""
+
+#: ../../storage.rst:608
+# 97ddeaa6235d4294ace130e1f8fd97c0
+msgid "The deletion of a volume does not delete the snapshots that have been created from the volume"
+msgstr ""
+
+#: ../../storage.rst:611
+# 0050f5041dd04b1dbeff8201bd20e44e
+msgid "When a VM is destroyed, data disk volumes that are attached to the VM are not deleted."
+msgstr ""
+
+#: ../../storage.rst:614
+# f3a035c41fca41908db4d1f0f724f360
+msgid "Volumes are permanently destroyed using a garbage collection process. The global configuration variables expunge.delay and expunge.interval determine when the physical deletion of volumes will occur."
+msgstr ""
+
+#: ../../storage.rst:618
+# e4eb84092e8b4ea9a1a97fecac24acbb
+msgid "`expunge.delay`: determines how old the volume must be before it is destroyed, in seconds"
+msgstr ""
+
+#: ../../storage.rst:621
+# 7564390647064858ac8aa5f26279afe5
+msgid "`expunge.interval`: determines how often to run the garbage collection check"
+msgstr ""
+
+#: ../../storage.rst:624
+# 000948d93f8f4cdba6f8fbab90adf234
+msgid "Administrators should adjust these values depending on site policies around data retention."
+msgstr ""
+
+#: ../../storage.rst:629
+# a8d6b53bbfe04f9198da340f624d7b85
+msgid "Working with Volume Snapshots"
+msgstr ""
+
+#: ../../storage.rst:631
+#: ../../storage.rst:676
+# 86801042196e4703adde0a0f8f421cc2
+# ecd40cf685aa497094053129489ffa6d
+msgid "(Supported for the following hypervisors: **XenServer**, **VMware vSphere**, and **KVM**)"
+msgstr ""
+
+#: ../../storage.rst:634
+# 084599a159574408809d1cfaa15f2160
+msgid "CloudStack supports snapshots of disk volumes. Snapshots are a point-in-time capture of virtual machine disks. Memory and CPU states are not captured. If you are using the Oracle VM hypervisor, you can not take snapshots, since OVM does not support them."
+msgstr ""
+
+#: ../../storage.rst:639
+# bd4b18a4d2374e20ae0af95dad8d53e5
+msgid "Snapshots may be taken for volumes, including both root and data disks (except when the Oracle VM hypervisor is used, which does not support snapshots). The administrator places a limit on the number of stored snapshots per user. Users can create new volumes from the snapshot for recovery of particular files and they can create templates from snapshots to boot from a restored disk."
+msgstr ""
+
+#: ../../storage.rst:646
+# 61d7db60070b43a4a6a950e12598da22
+msgid "Users can create snapshots manually or by setting up automatic recurring snapshot policies. Users can also create disk volumes from snapshots, which may be attached to a VM like any other disk volume. Snapshots of both root disks and data disks are supported. However, CloudStack does not currently support booting a VM from a recovered root disk. A disk recovered from snapshot of a root disk is treated as a regular data disk; the data on recovered disk can be accessed by attaching the disk to a VM."
+msgstr ""
+
+#: ../../storage.rst:655
+# 42324227e8644e9dae9c6866285da289
+msgid "A completed snapshot is copied from primary storage to secondary storage, where it is stored until deleted or purged by newer snapshot."
+msgstr ""
+
+#: ../../storage.rst:660
+# 6d4012e38675491e950c4095403168d4
+msgid "How to Snapshot a Volume"
+msgstr ""
+
+#: ../../storage.rst:662
+# c8a3e39ed65148c1b2db5692449e3ec0
+msgid "Log in to the CloudStack UI as a user or administrator."
+msgstr ""
+
+#: ../../storage.rst:666
+# ee26042497e54259b376064aafe9cebf
+msgid "In Select View, be sure Volumes is selected."
+msgstr ""
+
+#: ../../storage.rst:668
+# 2f05b064d8b245a99e010a0f45f944e2
+msgid "Click the name of the volume you want to snapshot."
+msgstr ""
+
+#: ../../storage.rst:670
+# b4d7d4eaa5a149f0812cdddc1fd45a61
+msgid "Click the Snapshot button. |SnapshotButton.png|"
+msgstr ""
+
+#: ../../storage.rst:674
+# 6daa1fb5225e4efe8672fc86408e7055
+msgid "Automatic Snapshot Creation and Retention"
+msgstr ""
+
+#: ../../storage.rst:679
+# 01044207c30b40148eedee96353f6ad9
+msgid "Users can set up a recurring snapshot policy to automatically create multiple snapshots of a disk at regular intervals. Snapshots can be created on an hourly, daily, weekly, or monthly interval. One snapshot policy can be set up per disk volume. For example, a user can set up a daily snapshot at 02:30."
+msgstr ""
+
+#: ../../storage.rst:685
+# bc81c587ad8b4032b27d61690390e258
+msgid "With each snapshot schedule, users can also specify the number of scheduled snapshots to be retained. Older snapshots that exceed the retention limit are automatically deleted. This user-defined limit must be equal to or lower than the global limit set by the CloudStack administrator. See `“Globally Configured Limits” <usage.html#globally-configured-limits>`_. The limit applies only to those snapshots that are taken as part of an automatic recurring snapshot policy. Additional manual snapshots can be created and retained."
+msgstr ""
+
+#: ../../storage.rst:697
+# 4d944a9ae89444379355fd0f48bd592a
+msgid "Incremental Snapshots and Backup"
+msgstr ""
+
+#: ../../storage.rst:699
+# d0114a6db3e54775a44f58bd333b2916
+msgid "Snapshots are created on primary storage where a disk resides. After a snapshot is created, it is immediately backed up to secondary storage and removed from primary storage for optimal utilization of space on primary storage."
+msgstr ""
+
+#: ../../storage.rst:704
+# 1c3dce8473ed47388f4d6175b8e34c81
+msgid "CloudStack does incremental backups for some hypervisors. When incremental backups are supported, every N backup is a full backup."
+msgstr ""
+
+#: ../../storage.rst:711
+# 4559fc5082f543d6b1cdacaa46ed5a23
+msgid "Support incremental backup"
+msgstr ""
+
+#: ../../storage.rst:716
+# 1c981e7b2c7b445a9061e36444287afb
+msgid "Volume Status"
+msgstr ""
+
+#: ../../storage.rst:718
+# b7db2aabc187479797c7424c5a1bb1f8
+msgid "When a snapshot operation is triggered by means of a recurring snapshot policy, a snapshot is skipped if a volume has remained inactive since its last snapshot was taken. A volume is considered to be inactive if it is either detached or attached to a VM that is not running. CloudStack ensures that at least one snapshot is taken since the volume last became inactive."
+msgstr ""
+
+#: ../../storage.rst:725
+# b5a7b1b8f3fe4e47a40bc594491a0643
+msgid "When a snapshot is taken manually, a snapshot is always created regardless of whether a volume has been active or not."
+msgstr ""
+
+#: ../../storage.rst:730
+# e8778a84f2d142489ea29fa0793066b1
+msgid "Snapshot Restore"
+msgstr ""
+
+#: ../../storage.rst:732
+# 4bcf574b0e484b7ebf81324e87069f67
+msgid "There are two paths to restoring snapshots. Users can create a volume from the snapshot. The volume can then be mounted to a VM and files recovered as needed. Alternatively, a template may be created from the snapshot of a root disk. The user can then boot a VM from this template to effect recovery of the root disk."
+msgstr ""
+
+#: ../../storage.rst:740
+# cf46f177e13341079bac27a54806636b
+msgid "Snapshot Job Throttling"
+msgstr ""
+
+#: ../../storage.rst:742
+# 6ba670f617a541788c30476794cde2c6
+msgid "When a snapshot of a virtual machine is requested, the snapshot job runs on the same host where the VM is running or, in the case of a stopped VM, the host where it ran last. If many snapshots are requested for VMs on a single host, this can lead to problems with too many snapshot jobs overwhelming the resources of the host."
+msgstr ""
+
+#: ../../storage.rst:748
+# aedc3df480554bd59de19f4c4ba17dff
+msgid "To address this situation, the cloud's root administrator can throttle how many snapshot jobs are executed simultaneously on the hosts in the cloud by using the global configuration setting concurrent.snapshots.threshold.perhost. By using this setting, the administrator can better ensure that snapshot jobs do not time out and hypervisor hosts do not experience performance issues due to hosts being overloaded with too many snapshot requests."
+msgstr ""
+
+#: ../../storage.rst:756
+# 9a43b07f0da64addaa4eb478d80b82a2
+msgid "Set concurrent.snapshots.threshold.perhost to a value that represents a best guess about how many snapshot jobs the hypervisor hosts can execute at one time, given the current resources of the hosts and the number of VMs running on the hosts. If a given host has more snapshot requests, the additional requests are placed in a waiting queue. No new snapshot jobs will start until the number of currently executing snapshot jobs falls below the configured limit."
+msgstr ""
+
+#: ../../storage.rst:764
+# 2fd65be78bf841d9911d51c1de67cd86
+msgid "The admin can also set job.expire.minutes to place a maximum on how long a snapshot request will wait in the queue. If this limit is reached, the snapshot request fails and returns an error message."
+msgstr ""
+
+#: ../../storage.rst:770
+# 45b8545120ba486ca2cbee08b18502d3
+msgid "VMware Volume Snapshot Performance"
+msgstr ""
+
+#: ../../storage.rst:772
+# aa81997f26a64d1399b138ae79ae8ab7
+msgid "When you take a snapshot of a data or root volume on VMware, CloudStack uses an efficient storage technique to improve performance."
+msgstr ""
+
+#: ../../storage.rst:775
+# edf5b2aae9f54e098d3b6627c10fe21d
+msgid "A snapshot is not immediately exported from vCenter to a mounted NFS share and packaged into an OVA file format. This operation would consume time and resources. Instead, the original file formats (e.g., VMDK) provided by vCenter are retained. An OVA file will only be created as needed, on demand. To generate the OVA, CloudStack uses information in a properties file (\\*.ova.meta) which it stored along with the original snapshot data."
+msgstr ""
+
+#: ../../storage.rst:784
+# c2bf4f95ccfe40aea4c948e5145c1e45
+msgid "For upgrading customers: This process applies only to newly created snapshots after upgrade to CloudStack 4.2. Snapshots that have already been taken and stored in OVA format will continue to exist in that format, and will continue to work as expected."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/systemvm.pot b/source/adminguide/locale/pot/systemvm.pot
new file mode 100644
index 0000000..63cea3f
--- /dev/null
+++ b/source/adminguide/locale/pot/systemvm.pot
@@ -0,0 +1,740 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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"
+
+#: ../../systemvm.rst:18
+# a1ba7b5ddeaa4674a16ca755b4399374
+msgid "Working with System Virtual Machines"
+msgstr ""
+
+#: ../../systemvm.rst:20
+# 8adf74bd899541a180455ab6582554ec
+msgid "CloudStack uses several types of system virtual machines to perform tasks in the cloud. In general CloudStack manages these system VMs and creates, starts, and stops them as needed based on scale and immediate needs. However, the administrator should be aware of them and their roles to assist in debugging issues."
+msgstr ""
+
+#: ../../systemvm.rst:28
+# 9309f035653a42c2a2abfdaced6acabe
+msgid "The System VM Template"
+msgstr ""
+
+#: ../../systemvm.rst:30
+# c845974251da4739b29ae9338d9f85f0
+msgid "The System VMs come from a single template. The System VM has the following characteristics:"
+msgstr ""
+
+#: ../../systemvm.rst:33
+# 6ce60c193c5547e38390bda23ad9acff
+msgid "Debian 6.0 (\"Squeeze\"), 2.6.32 kernel with the latest security patches from the Debian security APT repository"
+msgstr ""
+
+#: ../../systemvm.rst:36
+# 7ba8f1dd850e4472b93271c07b12e27e
+msgid "Has a minimal set of packages installed thereby reducing the attack surface"
+msgstr ""
+
+#: ../../systemvm.rst:39
+# 157f5d425def480e9b24095a62b2f059
+msgid "32-bit for enhanced performance on Xen/VMWare"
+msgstr ""
+
+#: ../../systemvm.rst:41
+# 7a44b4350ff6457cab519a552bd9afca
+msgid "pvops kernel with Xen PV drivers, KVM virtio drivers, and VMware tools for optimum performance on all hypervisors"
+msgstr ""
+
+#: ../../systemvm.rst:44
+# 3e0764891a5141e2b34368e7bb8aeb84
+msgid "Xen tools inclusion allows performance monitoring"
+msgstr ""
+
+#: ../../systemvm.rst:46
+# 60aeed2365974b86a64bdf02460e8ef7
+msgid "Latest versions of HAProxy, iptables, IPsec, and Apache from debian repository ensures improved security and speed"
+msgstr ""
+
+#: ../../systemvm.rst:49
+# 5dab0ffe88944ef3ad1ceb02e640ed9d
+msgid "Latest version of JRE from Sun/Oracle ensures improved security and speed"
+msgstr ""
+
+#: ../../systemvm.rst:54
+# 9f806f6735e64fb786b5ab22d695493f
+msgid "Changing the Default System VM Template"
+msgstr ""
+
+#: ../../systemvm.rst:56
+# 88cf932e61dd41a8bc1c583aa0bd38b7
+msgid "CloudStack allows you to change the default 32-bit System VM template to 64-bit one. Using the 64-bit template, upgrade the virtual router to manage larger number of connection in your network."
+msgstr ""
+
+#: ../../systemvm.rst:60
+# a4f753c8b20b411495b4077d429fadda
+msgid "Based on the hypervisor you use, download the 64-bit template from the following location:"
+msgstr ""
+
+#: ../../systemvm.rst:64
+# 0c56be6861554fe2b5519acffca4bbbf
+msgid "Hypervisor"
+msgstr ""
+
+#: ../../systemvm.rst:64
+# 2d2c7eabf8364232911d6ea74c1ebce2
+msgid "Download Location"
+msgstr ""
+
+#: ../../systemvm.rst:66
+# 18c32afddeff4951a466847a983335fe
+msgid "XenServer"
+msgstr ""
+
+#: ../../systemvm.rst:66
+# 6ea0f846b0a34711b7c0090cb48d8c32
+msgid "http://download.cloud.com/templates/4.2/64bit/systemvmtemplate64-2013-07-15-master-xen.vhd.bz2"
+msgstr ""
+
+#: ../../systemvm.rst:67
+# e8a51da6f6614114a91e4006eedfc912
+msgid "KVM"
+msgstr ""
+
+#: ../../systemvm.rst:67
+# fe251bca2b854129890cba8e7ac9bbbf
+msgid "http://download.cloud.com/templates/4.2/64bit/systemvmtemplate64-2013-07-15-master-kvm.qcow2.bz2"
+msgstr ""
+
+#: ../../systemvm.rst:70
+# 2d498240d20c4683ab11ac2232135a16
+msgid "As an administrator, log in to the CloudStack UI"
+msgstr ""
+
+#: ../../systemvm.rst:72
+# cb836b9320584dfe917198280919b2a8
+msgid "Register the 64 bit template."
+msgstr ""
+
+#: ../../systemvm.rst:74
+# c8cab1a649c94d0ba1393b80e7bf411b
+msgid "For example: KVM64bitTemplate"
+msgstr ""
+
+#: ../../systemvm.rst:76
+# d88c6f133f114456914ec8807ccef386
+msgid "While registering the template, select Routing."
+msgstr ""
+
+#: ../../systemvm.rst:78
+# b7e2b731ae7e4c789be6af9ed2d185af
+msgid "Navigate to Infrastructure > Zone > Settings."
+msgstr ""
+
+#: ../../systemvm.rst:80
+# b58d5557ddeb454fbae55b570e2c68f0
+msgid "Set the name of the 64-bit template, KVM64bitTemplate, in the *``router.template.kvm``* global parameter."
+msgstr ""
+
+#: ../../systemvm.rst:83
+# 951cf2ccd5d34614a87679078d22599c
+msgid "If you are using a XenServer 64-bit template, set the name in the *``router.template.xen``* global parameter."
+msgstr ""
+
+#: ../../systemvm.rst:86
+# 534ac4d13b2a4560aa420c9aa2fb9e57
+msgid "Any new virtual router created in this Zone automatically picks up this template."
+msgstr ""
+
+#: ../../systemvm.rst:89
+# be4168abcbfd4eed8d7d73b2284d3ac4
+msgid "Restart the Management Server."
+msgstr ""
+
+#: ../../systemvm.rst:93
+# 266b4692ed0b4fb4bae8eb4d1ce9af1f
+msgid "Multiple System VM Support for VMware"
+msgstr ""
+
+#: ../../systemvm.rst:95
+# 2e1e78598bc94637b2c8fdfb6387a908
+msgid "Every CloudStack zone has single System VM for template processing tasks such as downloading templates, uploading templates, and uploading ISOs. In a zone where VMware is being used, additional System VMs can be launched to process VMware-specific tasks such as taking snapshots and creating private templates. The CloudStack management server launches additional System VMs for VMware-specific tasks as the load increases. The management server monitors and weights all commands sent to these System VMs and performs dynamic load balancing and scaling-up of more System VMs."
+msgstr ""
+
+#: ../../systemvm.rst:107
+# 37fb441bcdb34d6fb7432fa98ef8886b
+msgid "Console Proxy"
+msgstr ""
+
+#: ../../systemvm.rst:109
+# 9217568c55be47b7bd405187d23f7777
+msgid "The Console Proxy is a type of System Virtual Machine that has a role in presenting a console view via the web UI. It connects the user’s browser to the VNC port made available via the hypervisor for the console of the guest. Both the administrator and end user web UIs offer a console connection."
+msgstr ""
+
+#: ../../systemvm.rst:115
+# f0a0de282eec4d69a9f65b3ff7114cf8
+msgid "Clicking a console icon brings up a new window. The AJAX code downloaded into that window refers to the public IP address of a console proxy VM. There is exactly one public IP address allocated per console proxy VM. The AJAX application connects to this IP. The console proxy then proxies the connection to the VNC port for the requested VM on the Host hosting the guest."
+msgstr ""
+
+#: ../../systemvm.rst:123
+# b8ee3c97a12f494fadd3971c927e4f87
+msgid "The hypervisors will have many ports assigned to VNC usage so that multiple VNC sessions can occur simultaneously."
+msgstr ""
+
+#: ../../systemvm.rst:126
+# 04dcecfe7e024822a311ba18520f6cce
+msgid "There is never any traffic to the guest virtual IP, and there is no need to enable VNC within the guest."
+msgstr ""
+
+#: ../../systemvm.rst:129
+# 15e8724d26714949a10f88914e7038db
+msgid "The console proxy VM will periodically report its active session count to the Management Server. The default reporting interval is five seconds. This can be changed through standard Management Server configuration with the parameter consoleproxy.loadscan.interval."
+msgstr ""
+
+#: ../../systemvm.rst:134
+# 67b327e6f92f4c69a649679cf88b933c
+msgid "Assignment of guest VM to console proxy is determined by first determining if the guest VM has a previous session associated with a console proxy. If it does, the Management Server will assign the guest VM to the target Console Proxy VM regardless of the load on the proxy VM. Failing that, the first available running Console Proxy VM that has the capacity to handle new sessions is used."
+msgstr ""
+
+#: ../../systemvm.rst:141
+# 0fcca189c0b0490fb490988079cca591
+msgid "Console proxies can be restarted by administrators but this will interrupt existing console sessions for users."
+msgstr ""
+
+#: ../../systemvm.rst:146
+# 9c3b4c70f4cf47379b07b5f24863023b
+msgid "Using a SSL Certificate for the Console Proxy"
+msgstr ""
+
+#: ../../systemvm.rst:149
+# 7be31349d45949dfa61f79105ade746f
+msgid "In the past CloudStack used the ``realhostip.com`` dynamic DNS resolution service. As this service will be shut down as of June 30th, 2014, CloudStack has stopped using the service as of version 4.3."
+msgstr ""
+
+#: ../../systemvm.rst:154
+# ff149d60a5d74070bb252689b6e724ab
+msgid "By default, the console viewing functionality uses plaintext HTTP. In any production environment, the console proxy connection should be encrypted via SSL at the mininum."
+msgstr ""
+
+#: ../../systemvm.rst:158
+# 471907f542334e94b211495c26beacff
+msgid "A CloudStack administrator has 2 ways to secure the console proxy communication with SSL:"
+msgstr ""
+
+#: ../../systemvm.rst:161
+# bd5c72a779c74100ada4a4e0ebd65633
+msgid "Set up a SSL wild-card certificate and domain name resolution"
+msgstr ""
+
+#: ../../systemvm.rst:163
+# 9d2106a856664feba8d3ed31ffef47b3
+msgid "Set up SSL certificate for specific FQDN and configure load-balancer"
+msgstr ""
+
+#: ../../systemvm.rst:167
+# fbea784e67f546259f790571d5c68d02
+msgid "Changing the Console Proxy SSL Certificate and Domain"
+msgstr ""
+
+#: ../../systemvm.rst:169
+# 0ef9de23136a444a802cb1fb49929072
+msgid "The administrator can configure SSL encryption by selecting a domain and uploading a new SSL certificate and private key. The domain must run a DNS service that is capable of resolving queries for addresses of the form aaa-bbb-ccc-ddd.your.domain to an IPv4 IP address in the form aaa.bbb.ccc.ddd, for example, 202.8.44.1. To change the console proxy domain, SSL certificate, and private key:"
+msgstr ""
+
+#: ../../systemvm.rst:176
+# 21ed531476934988b073b6db592f8ded
+msgid "Set up dynamic name resolution or populate all possible DNS names in your public IP range into your existing DNS server with the format aaa-bbb-ccc-ddd.consoleproxy.company.com -> aaa.bbb.ccc.ddd."
+msgstr ""
+
+#: ../../systemvm.rst:181
+# 8e0e99fee7274b59a2f75b2439a28528
+msgid "In these steps you will notice *consoleproxy.company.com* -For security best practices, we recommend creating a wildcard SSL certificate on a separate subdomain so in the event that the certificate is compromised, a malicious user cannot impersonate a company.com domain."
+msgstr ""
+
+#: ../../systemvm.rst:187
+# 8840c66ff2704cbca38c9c9f5daddc09
+msgid "Generate the private key and certificate signing request (CSR). When you are using openssl to generate private/public key pairs and CSRs, for the private key that you are going to paste into the CloudStack UI, be sure to convert it into PKCS#8 format."
+msgstr ""
+
+#: ../../systemvm.rst:192
+# efd9b8a8ee594499800d89e3257cef8c
+msgid "Generate a new 2048-bit private key"
+msgstr ""
+
+#: ../../systemvm.rst:198
+# 95cd5c1544fd480784d73f497d0474a9
+msgid "Generate a new certificate CSR. Ensure the creation of a wildcard certificate, eg ``*.consoleproxy.company.com``"
+msgstr ""
+
+#: ../../systemvm.rst:205
+# 8501f0bd21d3496f9a95f55217ad5715
+msgid "Head to the website of your favorite trusted Certificate Authority, purchase an SSL certificate, and submit the CSR. You should receive a valid certificate in return"
+msgstr ""
+
+#: ../../systemvm.rst:209
+# c5e0a99a8e5548a7b30a82aad6008419
+msgid "Convert your private key format into PKCS#8 encrypted format."
+msgstr ""
+
+#: ../../systemvm.rst:215
+# 21138c806f2e48abab8f0748512628e2
+msgid "Convert your PKCS#8 encrypted private key into the PKCS#8 format that is compliant with CloudStack"
+msgstr ""
+
+#: ../../systemvm.rst:222
+# 021b9614a4c740eb995d66bb07551c5d
+msgid "In the Update SSL Certificate screen of the CloudStack UI, paste the following:"
+msgstr ""
+
+#: ../../systemvm.rst:225
+# 93d3977b1fbf4bdcaa3cb7c106025be0
+msgid "The certificate you've just generated."
+msgstr ""
+
+#: ../../systemvm.rst:227
+# f8f025d190ce4094a3dd63915b29267f
+msgid "The private key you've just generated."
+msgstr ""
+
+#: ../../systemvm.rst:229
+# a44d63f6a2084e029bf84c965e10cae2
+msgid "The desired domain name, prefixed with ``*.``; for example, ``*.consoleproxy.company.com``"
+msgstr ""
+
+#: ../../systemvm.rst:231
+# d69ea42c636247548be90fe1cb7c5f51
+msgid "|update-ssl.png|"
+msgstr ""
+
+#: ../../systemvm.rst:233
+# b0dd0973913649e1876bac396552c02e
+msgid "This stops all currently running console proxy VMs, then restarts them with the new certificate and key. Users might notice a brief interruption in console availability."
+msgstr ""
+
+#: ../../systemvm.rst:237
+# 88d8a0760f5641a6a3d5dac7f7ecb8e2
+msgid "The Management Server generates URLs of the form \"aaa-bbb-ccc-ddd.consoleproxy.company.com\" after this change is made. The new console requests will be served with the new DNS domain name, certificate, and key."
+msgstr ""
+
+#: ../../systemvm.rst:244
+# d9ae75c0be0d474f8707a09850ff25db
+msgid "Load-balancing Console Proxies"
+msgstr ""
+
+#: ../../systemvm.rst:245
+# baf2bcf57fed4f82aa193fd45f2f2140
+msgid "An alternative to using dynamic DNS or creating a range of DNS entries as described in the last section would be to create a SSL certificate for a specific domain name, configure CloudStack to use that particular FQDN, and then configure a load balancer to load balance the console proxy's IP address behind the FQDN. As the functionality for this is still new, please see https://cwiki.apache.org/confluence/display/CLOUDSTACK/Realhost+IP+changes for more details."
+msgstr ""
+
+#: ../../systemvm.rst:256
+# f8bc0488fcae4eed874f0719dcbd03dc
+msgid "Virtual Router"
+msgstr ""
+
+#: ../../systemvm.rst:258
+# 5aa09837be9b4cbbb6e84ebaabca6559
+msgid "The virtual router is a type of System Virtual Machine. The virtual router is one of the most frequently used service providers in CloudStack. The end user has no direct access to the virtual router. Users can ping the virtual router and take actions that affect it (such as setting up port forwarding), but users do not have SSH access into the virtual router."
+msgstr ""
+
+#: ../../systemvm.rst:265
+# b1afb70840d04ed6917b9fd0e68a312b
+msgid "There is no mechanism for the administrator to log in to the virtual router. Virtual routers can be restarted by administrators, but this will interrupt public network access and other services for end users. A basic test in debugging networking issues is to attempt to ping the virtual router from a guest VM. Some of the characteristics of the virtual router are determined by its associated system service offering."
+msgstr ""
+
+#: ../../systemvm.rst:274
+# a07561d1be02426f9c20ec39d37ebfda
+msgid "Configuring the Virtual Router"
+msgstr ""
+
+#: ../../systemvm.rst:276
+# 33b921e943764375b7e2833cd80501f1
+msgid "You can set the following:"
+msgstr ""
+
+#: ../../systemvm.rst:278
+# f4bf9f0a9f5341ce9751734831cb4100
+msgid "IP range"
+msgstr ""
+
+#: ../../systemvm.rst:280
+# 63e37af44a1644428067b31b62f0c6b2
+msgid "Supported network services"
+msgstr ""
+
+#: ../../systemvm.rst:282
+# e1a2e37b67a14415b27cdce549422c45
+msgid "Default domain name for the network serviced by the virtual router"
+msgstr ""
+
+#: ../../systemvm.rst:284
+# a78c71c42d6b400e8c6a037d8be60b00
+msgid "Gateway IP address"
+msgstr ""
+
+#: ../../systemvm.rst:286
+# c17203f5ab7c4339ab3bf6d4b276357c
+msgid "How often CloudStack fetches network usage statistics from CloudStack virtual routers. If you want to collect traffic metering data from the virtual router, set the global configuration parameter router.stats.interval. If you are not using the virtual router to gather network usage statistics, set it to 0."
+msgstr ""
+
+#: ../../systemvm.rst:294
+# db1198a11ec947f18c4cf2244c33eb08
+msgid "Upgrading a Virtual Router with System Service Offerings"
+msgstr ""
+
+#: ../../systemvm.rst:296
+# 35a9d4cee92b4a9fb1654d44110881fa
+msgid "When CloudStack creates a virtual router, it uses default settings which are defined in a default system service offering. See `“System Service Offerings” <#system-service-offerings>`_. All the virtual routers in a single guest network use the same system service offering. You can upgrade the capabilities of the virtual router by creating and applying a custom system service offering."
+msgstr ""
+
+#: ../../systemvm.rst:303
+# cd27cfafbeca4a8dbe03d9b84184a373
+msgid "Define your custom system service offering. See `“Creating a New System Service Offering” <#creating-a-new-system-service-offering>`_. In System VM Type, choose Domain Router."
+msgstr ""
+
+#: ../../systemvm.rst:308
+# 59d868f989f44a7daf1bfbc0e292db28
+msgid "Associate the system service offering with a network offering. See `“Creating a New Network Offering” <networking.html#creating-a-new-network-offering>`_."
+msgstr ""
+
+#: ../../systemvm.rst:312
+# dfa56664a39341bcbf503aa23d46f1d4
+msgid "Apply the network offering to the network where you want the virtual routers to use the new system service offering. If this is a new network, follow the steps in Adding an Additional Guest Network on page 66. To change the service offering for existing virtual routers, follow the steps in `“Changing the Network Offering on a Guest Network” <networking2.html#changing-the-network-offering-on-a-guest-network>`_."
+msgstr ""
+
+#: ../../systemvm.rst:321
+# 24d02637553648a99ee527214679997f
+msgid "Best Practices for Virtual Routers"
+msgstr ""
+
+#: ../../systemvm.rst:323
+# 9264d919f1d24e30b3ff39600891fd32
+msgid "WARNING: Restarting a virtual router from a hypervisor console deletes all the iptables rules. To work around this issue, stop the virtual router and start it from the CloudStack UI."
+msgstr ""
+
+#: ../../systemvm.rst:328
+# f0a98ab823014588ba7a79e496358417
+msgid "Do not use the destroyRouter API when only one router is available in the network, because restartNetwork API with the cleanup=false parameter can't recreate it later. If you want to destroy and recreate the single router available in the network, use the restartNetwork API with the cleanup=true parameter."
+msgstr ""
+
+#: ../../systemvm.rst:336
+# c9fe7a0ac42f4b8ba7e912ff1ccd88a6
+msgid "Service Monitoring Tool for Virtual Router"
+msgstr ""
+
+#: ../../systemvm.rst:338
+# 8c7761b870df47549d73c8e0a8e21ec0
+msgid "Various services running on the CloudStack virtual routers can be monitored by using a Service Monitoring tool. The tool ensures that services are successfully running until CloudStack deliberately disables them. If a service goes down, the tool automatically restarts the service, and if that does not help bringing up the service, an alert as well as an event is generated indicating the failure. A new global parameter, ``network.router.enableservicemonitoring``, has been introduced to control this feature. The default value is false, implies, monitoring is disabled. When you enable, ensure that the Management Server and the router are restarted."
+msgstr ""
+
+#: ../../systemvm.rst:349
+# eb435554762a44ae9561f7c121329709
+msgid "Monitoring tool can help to start a VR service, which is crashed due to an unexpected reason. For example:"
+msgstr ""
+
+#: ../../systemvm.rst:352
+# c64d62fa24064373919f92f8bb26dab6
+msgid "The services crashed due to defects in the source code."
+msgstr ""
+
+#: ../../systemvm.rst:354
+# 19f8982ead484814b9812242f98822cf
+msgid "The services that are terminated by the OS when memory or CPU is not sufficiently available for the service."
+msgstr ""
+
+#: ../../systemvm.rst:358
+# 88522e16c4ad4587887f207c3cb1de9f
+msgid "Only those services with daemons are monitored. The services that are failed due to errors in the service/daemon configuration file cannot be restarted by the Monitoring tool. VPC networks are not supported."
+msgstr ""
+
+#: ../../systemvm.rst:362
+# d6dde7af5158444683442aab05bf244e
+msgid "The following services are monitored in a VR:"
+msgstr ""
+
+#: ../../systemvm.rst:364
+#: ../../systemvm.rst:424
+# 919f0a593e4c494588e1859a5fccfae0
+# b9653f8b1d8744999883790ea0990b01
+msgid "DNS"
+msgstr ""
+
+#: ../../systemvm.rst:366
+# c8fa5957a2504e62afaf2aef337a064b
+msgid "HA Proxy"
+msgstr ""
+
+#: ../../systemvm.rst:368
+# d5ed20a1e7744cb0b70dcfa442d18ee0
+msgid "SSH"
+msgstr ""
+
+#: ../../systemvm.rst:370
+# 9a5f6db0ba8441d4ad47c0946c9230bb
+msgid "Apache Web Server"
+msgstr ""
+
+#: ../../systemvm.rst:372
+# 6f2ae7c39bfd4fd3b950701b42e2f0fa
+msgid "The following networks are supported:"
+msgstr ""
+
+#: ../../systemvm.rst:374
+# 6ed18a5a0c7f48feacc05607c212daf6
+msgid "Isolated Networks"
+msgstr ""
+
+#: ../../systemvm.rst:376
+# fd2ab5e43ac34e0fa5bade7bde71c5cf
+msgid "Shared Networks in both Advanced and Basic zone"
+msgstr ""
+
+#: ../../systemvm.rst:378
+# fb5714c33d284b61af774529226b1346
+msgid "VPC networks are not supported"
+msgstr ""
+
+#: ../../systemvm.rst:380
+# d22c1884f61f4ed5b1e3c6c1b2b8b218
+msgid "This feature is supported on the following hypervisors: XenServer, VMware, and KVM."
+msgstr ""
+
+#: ../../systemvm.rst:385
+# 209b4c2a4ff24293988606ece94dcc3d
+msgid "Enhanced Upgrade for Virtual Routers"
+msgstr ""
+
+#: ../../systemvm.rst:387
+# fe5f961e7475463681b5ffacfc66cadd
+msgid "Upgrading VR is made flexible. The CloudStack administrators will be able to control the sequence of the VR upgrades. The sequencing is based on Infrastructure hierarchy, such as by Cluster, Pod, or Zone, and Administrative (Account) hierarchy, such as by Tenant or Domain. As an administrator, you can also determine when a particular customer service, such as VR, is upgraded within a specified upgrade interval. Upgrade operation is enhanced to increase the upgrade speed by allowing as many upgrade operations in parallel as possible."
+msgstr ""
+
+#: ../../systemvm.rst:396
+# 0a2326eddab447b690fd8118e9f41940
+msgid "During the entire duration of the upgrade, users cannot launch new services or make changes to an existing service."
+msgstr ""
+
+#: ../../systemvm.rst:399
+# 4fb42cca852e4f548c30cb9034654413
+msgid "Additionally, using multiple versions of VRs in a single instance is supported. In the Details tab of a VR, you can view the version and whether it requires upgrade. During the Management Server upgrade, CloudStack checks whether VR is at the latest version before performing any operation on the VR. To support this, a new global parameter, *``router.version.check``*, has been added. This parameter is set to true by default, which implies minimum required version is checked before performing any operation. No operation is performed if the VR is not at the required version. Services of the older version VR continue to be available, but no further operations can be performed on the VR until it is upgraded to the latest version. This will be a transient state until the VR is upgraded. This will ensure that the availability of VR services and VR state is not impacted due to the Management Server upgrade."
+msgstr ""
+
+#: ../../systemvm.rst:414
+# 0567e75c33134bcea3a1caa72a5aaa00
+msgid "The following service will be available even if the VR is not upgraded. However, no changes for any of the services can be sent to the VR, until it is upgraded:"
+msgstr ""
+
+#: ../../systemvm.rst:418
+# 48fcfc3f076b494e942f868e0372e0b9
+msgid "SecurityGroup"
+msgstr ""
+
+#: ../../systemvm.rst:420
+# 1bee20546a154520ba2788c22c1f3486
+msgid "UserData"
+msgstr ""
+
+#: ../../systemvm.rst:422
+# 60d206f07ef3446fa4fb2747aa88893b
+msgid "DHCP"
+msgstr ""
+
+#: ../../systemvm.rst:426
+# ace288f1a1044792b92215d6a79af5d1
+msgid "LB"
+msgstr ""
+
+#: ../../systemvm.rst:428
+# 4ccc43be9ec44655b59657daed06a562
+msgid "Port Forwarding"
+msgstr ""
+
+#: ../../systemvm.rst:430
+# 1ffbebe241a745ebaaea80aa5ff7e00e
+msgid "VPN"
+msgstr ""
+
+#: ../../systemvm.rst:432
+# 9bfb5e6221b142eab579bea52cded3a4
+msgid "Static NAT"
+msgstr ""
+
+#: ../../systemvm.rst:434
+# 2b905be150d94c69b81d0dfbcf8e70ec
+msgid "Source NAT"
+msgstr ""
+
+#: ../../systemvm.rst:436
+# 952471d71a404a99b736c2438fd03018
+msgid "Firewall"
+msgstr ""
+
+#: ../../systemvm.rst:438
+# 4051d26b7c91408999d41f021c3ca178
+msgid "Gateway"
+msgstr ""
+
+#: ../../systemvm.rst:440
+# 69c89cdcc4844f728351fe01740e32ef
+msgid "NetworkACL"
+msgstr ""
+
+#: ../../systemvm.rst:444
+# 769b3ed7ed5c4ccf85d9386e5aea8b3f
+msgid "Supported Virtual Routers"
+msgstr ""
+
+#: ../../systemvm.rst:446
+# b3bd3d522cca4802afae131818e0df27
+msgid "VR"
+msgstr ""
+
+#: ../../systemvm.rst:448
+# 6378fb7b02b248cb8e34872a3d19b51d
+msgid "VPC VR"
+msgstr ""
+
+#: ../../systemvm.rst:450
+# dd5c03dc42ae4454a713ff50a2be91e9
+msgid "Redundant VR"
+msgstr ""
+
+#: ../../systemvm.rst:454
+# d9325031af0f4d1597f136b4d9f0e3e3
+msgid "Upgrading Virtual Routers"
+msgstr ""
+
+#: ../../systemvm.rst:456
+# 975d8f6d95014399909cc0cd8a2b16c6
+msgid "Download the latest System VM template."
+msgstr ""
+
+#: ../../systemvm.rst:458
+# c25708086d324a38b701d238b7463924
+msgid "Download the latest System VM to all the primary storage pools."
+msgstr ""
+
+#: ../../systemvm.rst:460
+# c9378adb82f140be8f8663c096c895c5
+msgid "Upgrade the Management Server."
+msgstr ""
+
+#: ../../systemvm.rst:462
+# 40387558057548f98875005c7ceabeb7
+msgid "Upgrade CPVM and SSVM either from the UI or by using the following script:"
+msgstr ""
+
+#: ../../systemvm.rst:469
+# d28d9ad5f0a0451bbff0baf5b102d9dd
+msgid "Even when the VRs are still on older versions, existing services will continue to be available to the VMs. The Management Server cannot perform any operations on the VRs until they are upgraded."
+msgstr ""
+
+#: ../../systemvm.rst:473
+# 2a8027346ddf4f988d4554184bcdb544
+msgid "Selectively upgrade the VRs:"
+msgstr ""
+
+#: ../../systemvm.rst:475
+# 6e59012980ce40deba2b51593d9d8901
+msgid "Log in to the CloudStack UI as the root administrator."
+msgstr ""
+
+#: ../../systemvm.rst:477
+# 728ae8ec4eb74571819bf5ec86b38073
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../systemvm.rst:479
+# 2d56351b1a1644bda4f342dce58b51d7
+msgid "On Virtual Routers, click View More."
+msgstr ""
+
+#: ../../systemvm.rst:481
+# 9af9b62d86b14af2a745e1a359d1c940
+msgid "All the VRs are listed in the Virtual Routers page."
+msgstr ""
+
+#: ../../systemvm.rst:483
+# f19642bbaf564ca0a26f3e8dff683a65
+msgid "In Select View drop-down, select desired grouping based on your requirement."
+msgstr ""
+
+#: ../../systemvm.rst:486
+# a76c013f7da8482eb097248fb3757989
+msgid "You can use either of the following:"
+msgstr ""
+
+#: ../../systemvm.rst:488
+# 0b60f1059d8e4b1faadac9b7a3113d8b
+msgid "Group by zone"
+msgstr ""
+
+#: ../../systemvm.rst:490
+# 5a12e32c9b0c4862a582cca80cd74030
+msgid "Group by pod"
+msgstr ""
+
+#: ../../systemvm.rst:492
+# a83f4a59498e44e09b79b5eb014f9d4f
+msgid "Group by cluster"
+msgstr ""
+
+#: ../../systemvm.rst:494
+# a1c022abb009480bb49288cdad2b5210
+msgid "Group by account"
+msgstr ""
+
+#: ../../systemvm.rst:496
+# 87a6b85df243430293aa4d5a55e00c4a
+msgid "Click the group which has the VRs to be upgraded."
+msgstr ""
+
+#: ../../systemvm.rst:498
+# 9e519d5a83be4513a0a20c665777a298
+msgid "For example, if you have selected Group by zone, select the name of the desired zone."
+msgstr ""
+
+#: ../../systemvm.rst:501
+# bd6d3d8bf8954923909c8147a4718053
+msgid "Click the Upgrade button to upgrade all the VRs. |vr-upgrade.png|"
+msgstr ""
+
+#: ../../systemvm.rst:503
+# 56d36b4fbb234438a6e0fce7d66a0ac1
+msgid "Click OK to confirm."
+msgstr ""
+
+#: ../../systemvm.rst:507
+# 2b7574a9be0e46a9bd04bff25c748a13
+msgid "Secondary Storage VM"
+msgstr ""
+
+#: ../../systemvm.rst:509
+# e941ae432ef24ea2a8b4987accf91257
+msgid "In addition to the hosts, CloudStack’s Secondary Storage VM mounts and writes to secondary storage."
+msgstr ""
+
+#: ../../systemvm.rst:512
+# f062d628750b4d5bbf97ac967cf17788
+msgid "Submissions to secondary storage go through the Secondary Storage VM. The Secondary Storage VM can retrieve templates and ISO images from URLs using a variety of protocols."
+msgstr ""
+
+#: ../../systemvm.rst:516
+# cedfcfe3cd38411ca2633b120ab0d034
+msgid "The secondary storage VM provides a background task that takes care of a variety of secondary storage activities: downloading a new template to a Zone, copying templates between Zones, and snapshot backups."
+msgstr ""
+
+#: ../../systemvm.rst:520
+# c2a68c523bf14634b2f881ce767633cc
+msgid "The administrator can log in to the secondary storage VM if needed."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/templates.pot b/source/adminguide/locale/pot/templates.pot
new file mode 100644
index 0000000..5491370
--- /dev/null
+++ b/source/adminguide/locale/pot/templates.pot
@@ -0,0 +1,1215 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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"
+
+#: ../../templates.rst:18
+# cf61f319f9464e6a8d50baac31e9b5ec
+msgid "Working with Templates"
+msgstr ""
+
+#: ../../templates.rst:20
+# 9fd79a40a20d4709abcae61ed6a93dfd
+msgid "A template is a reusable configuration for virtual machines. When users launch VMs, they can choose from a list of templates in CloudStack."
+msgstr ""
+
+#: ../../templates.rst:23
+# 882ddad869e440869d4f74c92ab41271
+msgid "Specifically, a template is a virtual disk image that includes one of a variety of operating systems, optional additional software such as office applications, and settings such as access control to determine who can use the template. Each template is associated with a particular type of hypervisor, which is specified when the template is added to CloudStack."
+msgstr ""
+
+#: ../../templates.rst:30
+# 100cd7a983eb4961b368c8ba7734c42d
+msgid "CloudStack ships with a default template. In order to present more choices to users, CloudStack administrators and users can create templates and add them to CloudStack."
+msgstr ""
+
+#: ../../templates.rst:36
+# 18309d4f55464acabeff92b1bab9055f
+msgid "Creating Templates: Overview"
+msgstr ""
+
+#: ../../templates.rst:38
+# 51d039ce8ec945faabf8f8999b3d3c0f
+msgid "CloudStack ships with a default template for the CentOS operating system. There are a variety of ways to add more templates. Administrators and end users can add templates. The typical sequence of events is:"
+msgstr ""
+
+#: ../../templates.rst:43
+# 06dcc3e2b2554e33bbfdf892226179bd
+msgid "Launch a VM instance that has the operating system you want. Make any other desired configuration changes to the VM."
+msgstr ""
+
+#: ../../templates.rst:46
+# 991daad714364dbdb6c7429365bfb041
+msgid "Stop the VM."
+msgstr ""
+
+#: ../../templates.rst:48
+# 284657ff1abc49e09a72598a4a379a00
+msgid "Convert the volume into a template."
+msgstr ""
+
+#: ../../templates.rst:50
+# ee2b8742854b46679adc6fced33914ab
+msgid "There are other ways to add templates to CloudStack. For example, you can take a snapshot of the VM's volume and create a template from the snapshot, or import a VHD from another system into CloudStack."
+msgstr ""
+
+#: ../../templates.rst:54
+# 7dee2cf1359f4fcdb0bc7f03150b7582
+msgid "The various techniques for creating templates are described in the next few sections."
+msgstr ""
+
+#: ../../templates.rst:59
+# 9fa8a8480b0345fd8fa7ccd71dcf1b0c
+msgid "Requirements for Templates"
+msgstr ""
+
+#: ../../templates.rst:61
+# cb14c5b032c24423959c7044dc64c47f
+msgid "For XenServer, install PV drivers / Xen tools on each template that you create. This will enable live migration and clean guest shutdown."
+msgstr ""
+
+#: ../../templates.rst:64
+# f69f5344e03e49e78a793d4ca605d703
+msgid "For vSphere, install VMware Tools on each template that you create. This will enable console view to work properly."
+msgstr ""
+
+#: ../../templates.rst:69
+# edd05ad541bd4f498f39bb0645713513
+msgid "Best Practices for Templates"
+msgstr ""
+
+#: ../../templates.rst:71
+# fd430ee9ee634ec9bf53dfcec6786ee3
+msgid "If you plan to use large templates (100 GB or larger), be sure you have a 10-gigabit network to support the large templates. A slower network can lead to timeouts and other errors when large templates are used."
+msgstr ""
+
+#: ../../templates.rst:77
+# 4405e8f642174cb3afc031cd7fdb4dd4
+msgid "The Default Template"
+msgstr ""
+
+#: ../../templates.rst:79
+# 1f4b4121eca94788a949ff8bbb9b6377
+msgid "CloudStack includes a CentOS template. This template is downloaded by the Secondary Storage VM after the primary and secondary storage are configured. You can use this template in your production deployment or you can delete it and use custom templates."
+msgstr ""
+
+#: ../../templates.rst:84
+# a5936c6c63214301b0a732ab8a848614
+msgid "The root password for the default template is \"password\"."
+msgstr ""
+
+#: ../../templates.rst:86
+# 56f17d0ded4f4175b6a8c78f5e04b44f
+msgid "A default template is provided for each of XenServer, KVM, and vSphere. The templates that are downloaded depend on the hypervisor type that is available in your cloud. Each template is approximately 2.5 GB physical size."
+msgstr ""
+
+#: ../../templates.rst:91
+# 5c9065097a2b42dbb7b454a66807e888
+msgid "The default template includes the standard iptables rules, which will block most access to the template excluding ssh."
+msgstr ""
+
+#: ../../templates.rst:123
+# 466a67f6a17249d19212da0a1d4ae915
+msgid "Private and Public Templates"
+msgstr ""
+
+#: ../../templates.rst:125
+# 9c4cef26750347d693d5d9d2abc33ab3
+msgid "When a user creates a template, it can be designated private or public."
+msgstr ""
+
+#: ../../templates.rst:127
+# 0a5c2d13d7de4c8696c17de766c7ff8e
+msgid "Private templates are only available to the user who created them. By default, an uploaded template is private."
+msgstr ""
+
+#: ../../templates.rst:130
+# 28c6ea956b7145bf87d5c591a262ed56
+msgid "When a user marks a template as “public,” the template becomes available to all users in all accounts in the user's domain, as well as users in any other domains that have access to the Zone where the template is stored. This depends on whether the Zone, in turn, was defined as private or public. A private Zone is assigned to a single domain, and a public Zone is accessible to any domain. If a public template is created in a private Zone, it is available only to users in the domain assigned to that Zone. If a public template is created in a public Zone, it is available to all users in all domains."
+msgstr ""
+
+#: ../../templates.rst:142
+# 8cc9490673de43a29b0fa3b899a796c0
+msgid "Creating a Template from an Existing Virtual Machine"
+msgstr ""
+
+#: ../../templates.rst:144
+# 0cd7674a6e674324a8b36a9eef61b924
+msgid "Once you have at least one VM set up in the way you want, you can use it as the prototype for other VMs."
+msgstr ""
+
+#: ../../templates.rst:147
+# e16345095f804e34ba10cdf1772864c5
+msgid "Create and start a virtual machine using any of the techniques given in `“Creating VMs” <virtual_machines.html#creating-vms>`_."
+msgstr ""
+
+#: ../../templates.rst:150
+# 9ecb6312deb04964a10192717ca021b5
+msgid "Make any desired configuration changes on the running VM, then click Stop."
+msgstr ""
+
+#: ../../templates.rst:153
+# 3bf1cf52e2f44c9bb0cc976b5b3217d4
+msgid "Wait for the VM to stop. When the status shows Stopped, go to the next step."
+msgstr ""
+
+#: ../../templates.rst:156
+# 51cee376de054012b33542272d214e67
+msgid "Click Create Template and provide the following:"
+msgstr ""
+
+#: ../../templates.rst:158
+# 3dc70b806977409392d741e01a49337b
+msgid "**Name and Display Text**. These will be shown in the UI, so choose something descriptive."
+msgstr ""
+
+#: ../../templates.rst:161
+# b7cb11e24ec1424abcb2fd299d27e6f8
+msgid "**OS Type**. This helps CloudStack and the hypervisor perform certain operations and make assumptions that improve the performance of the guest. Select one of the following."
+msgstr ""
+
+#: ../../templates.rst:165
+#: ../../templates.rst:242
+# b79a71e908b643308ec4fe326a113d06
+# 3a9638381a74458e8dc78d91fcd5d121
+msgid "If the operating system of the stopped VM is listed, choose it."
+msgstr ""
+
+#: ../../templates.rst:167
+#: ../../templates.rst:244
+# c2046860ca7a420282727c68e7e0bd8d
+# 612b47eacf5a4564b7557383ab6085ff
+msgid "If the OS type of the stopped VM is not listed, choose Other."
+msgstr ""
+
+#: ../../templates.rst:169
+# a132a4db61c047f6843764cb4ad468c3
+msgid "If you want to boot from this template in PV mode, choose Other PV (32-bit) or Other PV (64-bit). This choice is available only for XenServere:"
+msgstr ""
+
+#: ../../templates.rst:174
+# 400f23d7aa30429cadbbcf6d927ea291
+msgid "Generally you should not choose an older version of the OS than the version in the image. For example, choosing CentOS 5.4 to support a CentOS 6.2 image will in general not work. In those cases you should choose Other."
+msgstr ""
+
+#: ../../templates.rst:179
+#: ../../templates.rst:266
+# a74d603504464359801664a22644ecf1
+# f36349a0b7934f51bc4238b6ce12d3bd
+msgid "**Public**. Choose Yes to make this template accessible to all users of this CloudStack installation. The template will appear in the Community Templates list. See `“Private and Public Templates” <#private-and-public-templates>`_."
+msgstr ""
+
+#: ../../templates.rst:184
+#: ../../templates.rst:258
+# cad391d15484479f99460980862c7571
+# f596589a997f4443a0ac19eee063c09f
+msgid "**Password Enabled**. Choose Yes if your template has the CloudStack password change script installed. See :ref:`adding-password-management-to-templates`."
+msgstr ""
+
+#: ../../templates.rst:188
+# 0ad3f0f48f50458e8c753d6a087e4736
+msgid "Click Add."
+msgstr ""
+
+#: ../../templates.rst:190
+# 7560e86cb7f64b25a24a8adffa210672
+msgid "The new template will be visible in the Templates section when the template creation process has been completed. The template is then available when creating a new VM."
+msgstr ""
+
+#: ../../templates.rst:196
+# f25db73d631a4cf2b1a90ddbc720ebea
+msgid "Creating a Template from a Snapshot"
+msgstr ""
+
+#: ../../templates.rst:198
+# 37c2eb36164e46d982140684d23eccc7
+msgid "If you do not want to stop the VM in order to use the Create Template menu item (as described in `“Creating a Template from an Existing Virtual Machine” <#creating-a-template-from-an-existing-virtual-machine>`_), you can create a template directly from any snapshot through the CloudStack UI."
+msgstr ""
+
+#: ../../templates.rst:206
+# 1fddfc6f75c745558d997e2c6af314cf
+msgid "Uploading Templates"
+msgstr ""
+
+#: ../../templates.rst:210
+# f50af047d15042849fd3b9d1ea923270
+msgid "vSphere Templates and ISOs"
+msgstr ""
+
+#: ../../templates.rst:212
+# 942a210bb20f467b98414c592d71af20
+msgid "If you are uploading a template that was created using vSphere Client, be sure the OVA file does not contain an ISO. If it does, the deployment of VMs from the template will fail."
+msgstr ""
+
+#: ../../templates.rst:216
+# 6b6237e29230422f8b97fbbbc07dffd7
+msgid "Templates are uploaded based on a URL. HTTP is the supported access protocol. Templates are frequently large files. You can optionally gzip them to decrease upload times."
+msgstr ""
+
+#: ../../templates.rst:220
+# 40368082877e412c87f9a15e9b28e64a
+msgid "To upload a template:"
+msgstr ""
+
+#: ../../templates.rst:222
+# b954f933d2b84ec6bdc9dcf119fd3657
+msgid "In the left navigation bar, click Templates."
+msgstr ""
+
+#: ../../templates.rst:224
+# 8d360dd921b54190850f9eb8bcfd5832
+msgid "Click Register Template."
+msgstr ""
+
+#: ../../templates.rst:226
+# 641dd9e5a6d24e33ba70513e4c194dde
+msgid "Provide the following:"
+msgstr ""
+
+#: ../../templates.rst:228
+# ee2439f863e4425a9b1d3eed40b451cb
+msgid "**Name and Description**. These will be shown in the UI, so choose something descriptive."
+msgstr ""
+
+#: ../../templates.rst:231
+# c521e0a0730348a88e0393d8c53e0fd8
+msgid "**URL**. The Management Server will download the file from the specified URL, such as ``http://my.web.server/filename.vhd.gz``."
+msgstr ""
+
+#: ../../templates.rst:234
+# 935dbff52fbc49e2bc3effdfe8343c7f
+msgid "**Zone**. Choose the zone where you want the template to be available, or All Zones to make it available throughout CloudStack."
+msgstr ""
+
+#: ../../templates.rst:238
+# ef7a5cbcab564351b11799afe2f3221f
+msgid "**OS Type**: This helps CloudStack and the hypervisor perform certain operations and make assumptions that improve the performance of the guest. Select one of the following:"
+msgstr ""
+
+#: ../../templates.rst:247
+# e179d642fb334f9fa4073821044a5116
+msgid "You should not choose an older version of the OS than the version in the image. For example, choosing CentOS 5.4 to support a CentOS 6.2 image will in general not work. In those cases you should choose Other."
+msgstr ""
+
+#: ../../templates.rst:252
+# 558b914220d948188698827bc674fa3a
+msgid "**Hypervisor**: The supported hypervisors are listed. Select the desired one."
+msgstr ""
+
+#: ../../templates.rst:255
+# 362c6490da7e426ead7c28ef7bca2f3d
+msgid "**Format**. The format of the template upload file, such as VHD or OVA."
+msgstr ""
+
+#: ../../templates.rst:262
+# 475796efd2dd4d64a7897d80ccf02191
+msgid "**Extractable**. Choose Yes if the template is available for extraction. If this option is selected, end users can download a full image of a template."
+msgstr ""
+
+#: ../../templates.rst:271
+# 7f676cb6f6844001ac5af17d480dd595
+msgid "**Featured**. Choose Yes if you would like this template to be more prominent for users to select. The template will appear in the Featured Templates list. Only an administrator can make a template Featured."
+msgstr ""
+
+#: ../../templates.rst:278
+# 4f1b071c71184d61b1e20db9a1408381
+msgid "Exporting Templates"
+msgstr ""
+
+#: ../../templates.rst:280
+# 07e8cf807f6341c981fd8028383cae01
+msgid "End users and Administrators may export templates from the CloudStack. Navigate to the template in the UI and choose the Download function from the Actions menu."
+msgstr ""
+
+#: ../../templates.rst:286
+# ff3b2f1a01194b86a94ca7406e2c9e4c
+msgid "Creating a Linux Template"
+msgstr ""
+
+#: ../../templates.rst:288
+# 942a09f060a248499ad52006fb12910b
+msgid "Linux templates should be prepared using this documentation in order to prepare your linux VMs for template deployment. For ease of documentation, the VM which you are configuring the template on will be referred to as \"Template Master\". This guide currently covers legacy setups which do not take advantage of UserData and cloud-init and assumes openssh-server is installed during installation."
+msgstr ""
+
+#: ../../templates.rst:295
+# c110f6248b3b4a56a32c3a3c42a213b0
+msgid "An overview of the procedure is as follow:"
+msgstr ""
+
+#: ../../templates.rst:297
+# fccf60393f704035b1c6fceaae12ea12
+msgid "Upload your Linux ISO."
+msgstr ""
+
+#: ../../templates.rst:299
+#: ../../templates.rst:549
+# 0a498b0d37ad4ca29ed96268e032ca4f
+# a70aa21eac0643d2908840edc2bf61b8
+msgid "For more information, see `“Adding an ISO” <virtual_machines.html#adding-an-iso>`_."
+msgstr ""
+
+#: ../../templates.rst:302
+#: ../../templates.rst:552
+# a2c6ef939b3644e5a63b94756a7ef72e
+# 949a4ba056404bb29cc67697a1f50b33
+msgid "Create a VM Instance with this ISO."
+msgstr ""
+
+#: ../../templates.rst:304
+#: ../../templates.rst:554
+# eb1605dc63014381b489c931a38377e3
+# 6cf1e105b8a542adb4ea1daf3718eb15
+msgid "For more information, see `“Creating VMs” <virtual_machines.html#creating-vms>`_."
+msgstr ""
+
+#: ../../templates.rst:307
+# 6e61739ba7024680bdf5d1c3a4fb8ddc
+msgid "Prepare the Linux VM"
+msgstr ""
+
+#: ../../templates.rst:309
+# 86ecdc3984a446e69db7d31db4b0f355
+msgid "Create a template from the VM."
+msgstr ""
+
+#: ../../templates.rst:311
+# e865dcc3232e4f51972fe0f554d58eeb
+msgid "For more information, see `“Creating a Template from an Existing Virtual Machine” <#creating-a-template-from-an-existing-virtual-machine>`_."
+msgstr ""
+
+#: ../../templates.rst:316
+# dce1b0c69ea14188bf5d99e9aa364a4d
+msgid "System preparation for Linux"
+msgstr ""
+
+#: ../../templates.rst:318
+# 9d4c8a98ec1c466da2893fd12538e3ba
+msgid "The following steps will prepare a basic Linux installation for templating."
+msgstr ""
+
+#: ../../templates.rst:321
+# 3de223a77c284109956a2eef988638db
+msgid "**Installation**"
+msgstr ""
+
+#: ../../templates.rst:323
+# 4f6808052a554f3cbb8697209cafc2de
+msgid "It is good practice to name your VM something generic during installation, this will ensure components such as LVM do not appear unique to a machine. It is recommended that the name of \"localhost\" is used for installation."
+msgstr ""
+
+#: ../../templates.rst:329
+# ff8376cf4b4b40899df3911a0216a3f8
+msgid "For CentOS, it is necessary to take unique identification out of the interface configuration file, for this edit /etc/sysconfig/network-scripts/ifcfg-eth0 and change the content to the following."
+msgstr ""
+
+#: ../../templates.rst:341
+# f68b6e4efb764f92a1e56ad9ea54f90c
+msgid "The next steps updates the packages on the Template Master."
+msgstr ""
+
+#: ../../templates.rst:343
+#: ../../templates.rst:390
+#: ../../templates.rst:446
+# 143c241d86a44e32b496b66a9934ec6a
+# 4de01ffab6a44664b87eb62c32e550a4
+# 141d36e8817e444e94e29f6c889f76d9
+msgid "Ubuntu"
+msgstr ""
+
+#: ../../templates.rst:353
+#: ../../templates.rst:453
+# 7b51d3bdb3c2417486c37949b1978dab
+# a37b78dad81f45429074776c11add237
+msgid "CentOS"
+msgstr ""
+
+#: ../../templates.rst:361
+# b6d69c72e22e4f40bd0d7d7bdaa1be7e
+msgid "**Password management**"
+msgstr ""
+
+#: ../../templates.rst:364
+# f71ab72462f5424fbc900751e054d736
+msgid "If preferred, custom users (such as ones created during the Ubuntu installation) should be removed. First ensure the root user account is enabled by giving it a password and then login as root to continue."
+msgstr ""
+
+#: ../../templates.rst:373
+# ef5341894f7e40a4a9c300485f9f1367
+msgid "As root, remove any custom user accounts created during the installation process."
+msgstr ""
+
+#: ../../templates.rst:380
+# a81798014288476da8e256abdea8526b
+msgid "See :ref:`adding-password-management-to-templates` for instructions to setup the password management script, this will allow CloudStack to change your root password from the web interface."
+msgstr ""
+
+#: ../../templates.rst:384
+# 9d00097815b24c0ca4034a304afee047
+msgid "**Hostname Management**"
+msgstr ""
+
+#: ../../templates.rst:386
+# c41219c74c2b4b138cdfd88c986a2a02
+msgid "CentOS configures the hostname by default on boot. Unfortunately Ubuntu does not have this functionality, for Ubuntu installations use the following steps."
+msgstr ""
+
+#: ../../templates.rst:392
+# ad9bf73797c24558b7e106dc2ce8510b
+msgid "The hostname of a Templated VM is set by a custom script in `/etc/dhcp/dhclient-exit-hooks.d`, this script first checks if the current hostname is localhost, if true, it will get the host-name, domain-name and fixed-ip from the DHCP lease file and use those values to set the hostname and append the `/etc/hosts` file for local hostname resolution. Once this script, or a user has changed the hostname from localhost, it will no longer adjust system files regardless of it's new hostname. The script also recreates openssh-server keys, which should have been deleted before templating (shown below). Save the following script to `/etc/dhcp/dhclient-exit-hooks.d/sethostname`, and adjust the permissions."
+msgstr ""
+
+#: ../../templates.rst:434
+# 1f68693847f1433bb6541b70f1abedd5
+msgid "The following steps should be run when you are ready to template your Template Master. If the Template Master is rebooted during these steps you will have to run all the steps again. At the end of this process the Template Master should be shutdown and the template created in order to create and deploy the final template."
+msgstr ""
+
+#: ../../templates.rst:440
+# 79b32100447b4464a62f56cf91492a6c
+msgid "**Remove the udev persistent device rules**"
+msgstr ""
+
+#: ../../templates.rst:442
+# 7a1b5554792c4cb1aa676f8e73a843b8
+msgid "This step removes information unique to your Template Master such as network MAC addresses, lease files and CD block devices, the files are automatically generated on next boot."
+msgstr ""
+
+#: ../../templates.rst:460
+# 381e458992444a499e21908b7bf88a68
+msgid "**Remove SSH Keys**"
+msgstr ""
+
+#: ../../templates.rst:462
+# 9badfc5f4bfa454e8ca0d64a71a11c24
+msgid "This step is to ensure all your Templated VMs do not have the same SSH keys, which would decrease the security of the machines dramatically."
+msgstr ""
+
+#: ../../templates.rst:470
+# 0d2aa14e20f04c3bb2bad70954a1291a
+msgid "**Cleaning log files**"
+msgstr ""
+
+#: ../../templates.rst:472
+# af913fb8f91b484bb83ac0737e1b1d10
+msgid "It is good practice to remove old logs from the Template Master."
+msgstr ""
+
+#: ../../templates.rst:481
+# db125d8aa6cc45c8bdf9340dde1d3d45
+msgid "**Setting hostname**"
+msgstr ""
+
+#: ../../templates.rst:483
+# 5a2162138fca40088196712b5650f551
+msgid "In order for the Ubuntu DHCP script to function and the CentOS dhclient to set the VM hostname they both require the Template Master's hostname to be \"localhost\", run the following commands to change the hostname."
+msgstr ""
+
+#: ../../templates.rst:493
+# 3ed2b72c9128441ab39130f547642191
+msgid "**Set user password to expire**"
+msgstr ""
+
+#: ../../templates.rst:495
+# 10db50989ebe48c4a10ebdefa260c489
+msgid "This step forces the user to change the password of the VM after the template has been deployed."
+msgstr ""
+
+#: ../../templates.rst:502
+# abe301956bd54c1c86c35fca1411ece6
+msgid "**Clearing User History**"
+msgstr ""
+
+#: ../../templates.rst:504
+# 9b6183972b934b91be6da40e93a1c12a
+msgid "The next step clears the bash commands you have just run."
+msgstr ""
+
+#: ../../templates.rst:511
+# b8a76342290b46209f3bf8c468dc5cee
+msgid "**Shutdown the VM**"
+msgstr ""
+
+#: ../../templates.rst:513
+# f92b1a930b3e4d859616309b9db518e1
+msgid "Your now ready to shutdown your Template Master and create a template!"
+msgstr ""
+
+#: ../../templates.rst:520
+# 43e271d15b2742238d231b3f7fe85ed1
+msgid "**Create the template!**"
+msgstr ""
+
+#: ../../templates.rst:522
+# 1db89306e7ae4b99b486fb9d7c783da4
+msgid "You are now ready to create the template, for more information see `“Creating a Template from an Existing Virtual Machine” <#creating-a-template-from-an-existing-virtual-machine>`_."
+msgstr ""
+
+#: ../../templates.rst:527
+# 43f673483bbc490ca475ad5e0e1f1736
+msgid "Templated VMs for both Ubuntu and CentOS may require a reboot after provisioning in order to pickup the hostname."
+msgstr ""
+
+#: ../../templates.rst:532
+# 96fe0ca1217f4c6789bb7ef7bf304036
+msgid "Creating a Windows Template"
+msgstr ""
+
+#: ../../templates.rst:534
+# dc56a5c13129464f9d23300535eedbcc
+msgid "Windows templates must be prepared with Sysprep before they can be provisioned on multiple machines. Sysprep allows you to create a generic Windows template and avoid any possible SID conflicts."
+msgstr ""
+
+#: ../../templates.rst:539
+# fcbe31f9497c46618be1ae04f1c300d2
+msgid "(XenServer) Windows VMs running on XenServer require PV drivers, which may be provided in the template or added after the VM is created. The PV drivers are necessary for essential management functions such as mounting additional volumes and ISO images, live migration, and graceful shutdown."
+msgstr ""
+
+#: ../../templates.rst:545
+# 6918a5f84f9e483484479aa24d4ec044
+msgid "An overview of the procedure is as follows:"
+msgstr ""
+
+#: ../../templates.rst:547
+# c48d96b9ff9d430780c7eefe88c19a2d
+msgid "Upload your Windows ISO."
+msgstr ""
+
+#: ../../templates.rst:557
+# c29e3a4c4aec4418a525b07f70e30657
+msgid "Follow the steps in Sysprep for Windows Server 2008 R2 (below) or Sysprep for Windows Server 2003 R2, depending on your version of Windows Server"
+msgstr ""
+
+#: ../../templates.rst:561
+# d526a7794b20490094eb4688b02c0a58
+msgid "The preparation steps are complete. Now you can actually create the template as described in Creating the Windows Template."
+msgstr ""
+
+#: ../../templates.rst:566
+# 9e309b24a2eb479e878115e7e5af8cd0
+msgid "System Preparation for Windows Server 2008 R2"
+msgstr ""
+
+#: ../../templates.rst:568
+# a195817082c4472ea5bb4e287b2b8718
+msgid "For Windows 2008 R2, you run Windows System Image Manager to create a custom sysprep response XML file. Windows System Image Manager is installed as part of the Windows Automated Installation Kit (AIK). Windows AIK can be downloaded from `Microsoft Download Center <http://www.microsoft.com/en-us/download/details.aspx?id=9085>`_."
+msgstr ""
+
+#: ../../templates.rst:574
+# 8add2ef3ee0741feb9b1575421ee590d
+msgid "Use the following steps to run sysprep for Windows 2008 R2:"
+msgstr ""
+
+#: ../../templates.rst:577
+# 0e82209c29214738a91cd3233c54314c
+msgid "The steps outlined here are derived from the excellent guide by Charity Shelbourne, originally published at `Windows Server 2008 Sysprep Mini-Setup. <http://blogs.technet.com/askcore/archive/2008/10/31/automating-the-oobe-process-during-windows-server-2008-sysprep-mini-setup.aspx>`_"
+msgstr ""
+
+#: ../../templates.rst:582
+# 9392d5c10c02447f82b7413a71b09128
+msgid "Download and install the Windows AIK"
+msgstr ""
+
+#: ../../templates.rst:585
+# a4389660d8ad4d1b8c036e5a312acf49
+msgid "Windows AIK should not be installed on the Windows 2008 R2 VM you just created. Windows AIK should not be part of the template you create. It is only used to create the sysprep answer file."
+msgstr ""
+
+#: ../../templates.rst:589
+# b6b2049c23774943958f7539fc0624db
+msgid "Copy the install.wim file in the \\\\sources directory of the Windows 2008 R2 installation DVD to the hard disk. This is a very large file and may take a long time to copy. Windows AIK requires the WIM file to be writable."
+msgstr ""
+
+#: ../../templates.rst:594
+# 6a1367c35ec54816823cc2f821fb42c3
+msgid "Start the Windows System Image Manager, which is part of the Windows AIK."
+msgstr ""
+
+#: ../../templates.rst:597
+# 210d191e2b2540c6986358e0c0b9c87d
+msgid "In the Windows Image pane, right click the Select a Windows image or catalog file option to load the install.wim file you just copied."
+msgstr ""
+
+#: ../../templates.rst:600
+# 2ae1354725354401b1c6774b56210b30
+msgid "Select the Windows 2008 R2 Edition."
+msgstr ""
+
+#: ../../templates.rst:602
+# a4139f632731431fa6c278ed49a402a3
+msgid "You may be prompted with a warning that the catalog file cannot be opened. Click Yes to create a new catalog file."
+msgstr ""
+
+#: ../../templates.rst:605
+# 6daadc2945704fdbae1a77fab0ef5843
+msgid "In the Answer File pane, right click to create a new answer file."
+msgstr ""
+
+#: ../../templates.rst:607
+# 0d84d28c59424fc39b5a2f36f3dd6bfd
+msgid "Generate the answer file from the Windows System Image Manager using the following steps:"
+msgstr ""
+
+#: ../../templates.rst:610
+# fed0398c42684441a6958c5be21f5c07
+msgid "The first page you need to automate is the Language and Country or Region Selection page. To automate this, expand Components in your Windows Image pane, right-click and add the Microsoft-Windows-International-Core setting to Pass 7 oobeSystem. In your Answer File pane, configure the InputLocale, SystemLocale, UILanguage, and UserLocale with the appropriate settings for your language and country or region. Should you have a question about any of these settings, you can right-click on the specific setting and select Help. This will open the appropriate CHM help file with more information, including examples on the setting you are attempting to configure."
+msgstr ""
+
+#: ../../templates.rst:622
+# e1b641ce1c5d42e0bc8e530c840f89c0
+msgid "|sysmanager.png|"
+msgstr ""
+
+#: ../../templates.rst:624
+# fd41b3e0931141e5971248dfb811dc0a
+msgid "You need to automate the Software License Terms Selection page, otherwise known as the End-User License Agreement (EULA). To do this, expand the Microsoft-Windows-Shell-Setup component. High-light the OOBE setting, and add the setting to the Pass 7 oobeSystem. In Settings, set HideEULAPage true."
+msgstr ""
+
+#: ../../templates.rst:630
+# 72f9459967ad49cdaebc5ac0cf7e0940
+msgid "|software-license.png|"
+msgstr ""
+
+#: ../../templates.rst:632
+# d818473f321c4c2594fbc0d903e86837
+msgid "Make sure the license key is properly set. If you use MAK key, you can just enter the MAK key on the Windows 2008 R2 VM. You need not input the MAK into the Windows System Image Manager. If you use KMS host for activation you need not enter the Product Key. Details of Windows Volume Activation can be found at `http://technet.microsoft.com/en-us/library/bb892849.aspx <http://technet.microsoft.com/en-us/library/bb892849.aspx>`_"
+msgstr ""
+
+#: ../../templates.rst:640
+# 0941ea38dbb84c5ab3a37e64ff29e6d1
+msgid "You need to automate is the Change Administrator Password page. Expand the Microsoft-Windows-Shell-Setup component (if it is not still expanded), expand UserAccounts, right-click on AdministratorPassword, and add the setting to the Pass 7 oobeSystem configuration pass of your answer file. Under Settings, specify a password next to Value."
+msgstr ""
+
+#: ../../templates.rst:647
+# 8092f90cf8784fc0bc8408b84b547e18
+msgid "|change-admin-password.png|"
+msgstr ""
+
+#: ../../templates.rst:649
+# e7e1281b1ae04398b43ab9c70d0f8370
+msgid "You may read the AIK documentation and set many more options that suit your deployment. The steps above are the minimum needed to make Windows unattended setup work."
+msgstr ""
+
+#: ../../templates.rst:653
+# 9461bfba70d24cebb27c1d65ea4bdcfa
+msgid "Save the answer file as unattend.xml. You can ignore the warning messages that appear in the validation window."
+msgstr ""
+
+#: ../../templates.rst:656
+# e03af6631f444bac834875feb1551d93
+msgid "Copy the unattend.xml file into the c:\\\\windows\\\\system32\\\\sysprep directory of the Windows 2008 R2 Virtual Machine"
+msgstr ""
+
+#: ../../templates.rst:659
+# f25b60a2d1c64b00ab525ccb2ca1488e
+msgid "Once you place the unattend.xml file in c:\\\\windows\\\\system32\\\\sysprep directory, you run the sysprep tool as follows:"
+msgstr ""
+
+#: ../../templates.rst:668
+# c8ba22aeffd14733b20fd2ddadb189dd
+msgid "The Windows 2008 R2 VM will automatically shut down after sysprep is complete."
+msgstr ""
+
+#: ../../templates.rst:673
+# 8d4d691768fd4d2a9d131f80a0af05cc
+msgid "System Preparation for Windows Server 2003 R2"
+msgstr ""
+
+#: ../../templates.rst:675
+# 25fcbd475b3842f69219e1db506c148d
+msgid "Earlier versions of Windows have a different sysprep tool. Follow these steps for Windows Server 2003 R2."
+msgstr ""
+
+#: ../../templates.rst:678
+# e4b387caeb524e64b8e43a7256ad002b
+msgid "Extract the content of \\\\support\\\\tools\\\\deploy.cab on the Windows installation CD into a directory called c:\\\\sysprep on the Windows 2003 R2 VM."
+msgstr ""
+
+#: ../../templates.rst:682
+# 678e1857aae14091ad3954e190199112
+msgid "Run c:\\\\sysprep\\\\setupmgr.exe to create the sysprep.inf file."
+msgstr ""
+
+#: ../../templates.rst:684
+# eaaddf71b1e144ba9354ecdc3e61237f
+msgid "Select Create New to create a new Answer File."
+msgstr ""
+
+#: ../../templates.rst:686
+# 3a59447b097e4d6a8bbef6303be9c428
+msgid "Enter “Sysprep setup” for the Type of Setup."
+msgstr ""
+
+#: ../../templates.rst:688
+# 511f5fa4a9e04084a2344c13153944c3
+msgid "Select the appropriate OS version and edition."
+msgstr ""
+
+#: ../../templates.rst:690
+# c36d76222fa14fe39dfdd33baf171555
+msgid "On the License Agreement screen, select “Yes fully automate the installation”."
+msgstr ""
+
+#: ../../templates.rst:693
+# 42eac0aa963c4b138bba5785ecc4a9ab
+msgid "Provide your name and organization."
+msgstr ""
+
+#: ../../templates.rst:695
+# 923d7a62003b4bb28c6fdcec04988da5
+msgid "Leave display settings at default."
+msgstr ""
+
+#: ../../templates.rst:697
+# 28ff1531e0574780b26bbcdab535f18d
+msgid "Set the appropriate time zone."
+msgstr ""
+
+#: ../../templates.rst:699
+# c166a631d91d4ec5ba1fe55fb27e9071
+msgid "Provide your product key."
+msgstr ""
+
+#: ../../templates.rst:701
+# bb448a5c8bad409b910a983aafc7e7e5
+msgid "Select an appropriate license mode for your deployment"
+msgstr ""
+
+#: ../../templates.rst:703
+# 5961b7acd3964ece89961a88ac1c9e49
+msgid "Select “Automatically generate computer name”."
+msgstr ""
+
+#: ../../templates.rst:705
+# ee71045d980c48c3b4229992144775db
+msgid "Type a default administrator password. If you enable the password reset feature, the users will not actually use this password. This password will be reset by the instance manager after the guest boots up."
+msgstr ""
+
+#: ../../templates.rst:710
+# 662f974f66a84b258158cc6d888d31ff
+msgid "Leave Network Components at “Typical Settings”."
+msgstr ""
+
+#: ../../templates.rst:712
+# b382f00fffc54d2092dea46275ce07e0
+msgid "Select the “WORKGROUP” option."
+msgstr ""
+
+#: ../../templates.rst:714
+# 864a8297271a4b9c9310a8e580d93f85
+msgid "Leave Telephony options at default."
+msgstr ""
+
+#: ../../templates.rst:716
+# f9104d77ee794b999a52c430bde6f5e0
+msgid "Select appropriate Regional Settings."
+msgstr ""
+
+#: ../../templates.rst:718
+# 7a038c948aee40caad5fdbd408680a4e
+msgid "Select appropriate language settings."
+msgstr ""
+
+#: ../../templates.rst:720
+# 8fe7a793a4b149fc8b2c04b222bb95ff
+msgid "Do not install printers."
+msgstr ""
+
+#: ../../templates.rst:722
+# 0bd5cf14d63149e8a68370eb7b35c1b5
+msgid "Do not specify “Run Once commands”."
+msgstr ""
+
+#: ../../templates.rst:724
+# 05694b63059140748f90c4a339c83a2e
+msgid "You need not specify an identification string."
+msgstr ""
+
+#: ../../templates.rst:726
+# a48d1b90a9bc405daa8af11e577a21dc
+msgid "Save the Answer File as c:\\\\sysprep\\\\sysprep.inf."
+msgstr ""
+
+#: ../../templates.rst:728
+# a2f33c40df224c318576f392e89a029e
+msgid "Run the following command to sysprep the image:"
+msgstr ""
+
+#: ../../templates.rst:734
+# 47370d15208e44779af8dc395473c3ab
+msgid "After this step the machine will automatically shut down"
+msgstr ""
+
+#: ../../templates.rst:738
+# 6a05bb80ea29400084b33d565fcc1600
+msgid "Importing Amazon Machine Images"
+msgstr ""
+
+#: ../../templates.rst:740
+# eaa1897518c8471ca61593a7b64fd3e2
+msgid "The following procedures describe how to import an Amazon Machine Image (AMI) into CloudStack when using the XenServer hypervisor."
+msgstr ""
+
+#: ../../templates.rst:743
+# f83727180aee4a54aa1735df061a32d3
+msgid "Assume you have an AMI file and this file is called CentOS\\_6.2\\_x64. Assume further that you are working on a CentOS host. If the AMI is a Fedora image, you need to be working on a Fedora host initially."
+msgstr ""
+
+#: ../../templates.rst:747
+# d52c5657eb014680ba5dcb4cd793964b
+msgid "You need to have a XenServer host with a file-based storage repository (either a local ext3 SR or an NFS SR) to convert to a VHD once the image file has been customized on the Centos/Fedora host."
+msgstr ""
+
+#: ../../templates.rst:752
+# c6369502d5ec442bba824ba9ebd3399f
+msgid "When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text."
+msgstr ""
+
+#: ../../templates.rst:756
+# b12f0319181043b6ace0737e16ca933e
+msgid "To import an AMI:"
+msgstr ""
+
+#: ../../templates.rst:758
+# 516bca51c4054cb9a0a7c70f455cfb50
+msgid "Set up loopback on image file:"
+msgstr ""
+
+#: ../../templates.rst:765
+# c40cb6ea1f3a41dbbdfca02adc87b77a
+msgid "Install the kernel-xen package into the image. This downloads the PV kernel and ramdisk to the image."
+msgstr ""
+
+#: ../../templates.rst:772
+# 0cf205e0b1214bfd85b81840483a7e11
+msgid "Create a grub entry in /boot/grub/grub.conf."
+msgstr ""
+
+#: ../../templates.rst:780
+# ea05e45228434e6eb41f8d92afdcb402
+msgid "Determine the name of the PV kernel that has been installed into the image."
+msgstr ""
+
+#: ../../templates.rst:793
+# 3395c5bd2c424bf08e6b7c6e789b89b8
+msgid "Xen kernels/ramdisk always end with \"xen\". For the kernel version you choose, there has to be an entry for that version under lib/modules, there has to be an initrd and vmlinuz corresponding to that. Above, the only kernel that satisfies this condition is 2.6.18-164.15.1.el5xen."
+msgstr ""
+
+#: ../../templates.rst:799
+# cd3138f8605141a1a0ef5f9ae345c8cc
+msgid "Based on your findings, create an entry in the grub.conf file. Below is an example entry."
+msgstr ""
+
+#: ../../templates.rst:812
+# 82b126faf726428faa043e59b48fab5c
+msgid "Edit etc/fstab, changing “sda1” to “xvda” and changing “sdb” to “xvdb”."
+msgstr ""
+
+#: ../../templates.rst:824
+# 158d080ac2c845c089c610cf10e51f6e
+msgid "Enable login via the console. The default console device in a XenServer system is xvc0. Ensure that etc/inittab and etc/securetty have the following lines respectively:"
+msgstr ""
+
+#: ../../templates.rst:835
+# 78c0483458064433a5dcf14ba528eb3e
+msgid "Ensure the ramdisk supports PV disk and PV network. Customize this for the kernel version you have determined above."
+msgstr ""
+
+#: ../../templates.rst:845
+# c5985961045c4177b2d3d8f684fbd61b
+msgid "Change the password."
+msgstr ""
+
+#: ../../templates.rst:855
+# a26809b7f44741e898c17da609bbd7fd
+msgid "Exit out of chroot."
+msgstr ""
+
+#: ../../templates.rst:861
+# 3fc6a7c5bbaf414da8d8a91f9f2e1056
+msgid "Check `etc/ssh/sshd_config` for lines allowing ssh login using a password."
+msgstr ""
+
+#: ../../templates.rst:870
+# 664c645f17104a9689c80c1722a33864
+msgid "If you need the template to be enabled to reset passwords from the CloudStack UI or API, install the password change script into the image at this point. See :ref:`adding-password-management-to-templates`."
+msgstr ""
+
+#: ../../templates.rst:874
+# a4f18c75d1074dd2b110ac78ffe5265f
+msgid "Unmount and delete loopback mount."
+msgstr ""
+
+#: ../../templates.rst:881
+# 8edfb6c75d614771b3b350cbc348a938
+msgid "Copy the image file to your XenServer host's file-based storage repository. In the example below, the Xenserver is \"xenhost\". This XenServer has an NFS repository whose uuid is a9c5b8c8-536b-a193-a6dc-51af3e5ff799."
+msgstr ""
+
+#: ../../templates.rst:890
+# 0dc1d9510e784714bcdec1384e8755f1
+msgid "Log in to the Xenserver and create a VDI the same size as the image."
+msgstr ""
+
+#: ../../templates.rst:900
+# 4e8f8e659e434bc5a3f36dc2fd9f822d
+msgid "Import the image file into the VDI. This may take 10–20 minutes."
+msgstr ""
+
+#: ../../templates.rst:906
+# 0b58122603704ebda3d2342ee6515ff7
+msgid "Locate a the VHD file. This is the file with the VDI’s UUID as its name. Compress it and upload it to your web server."
+msgstr ""
+
+#: ../../templates.rst:916
+# 7691e9d11b8b49d29aec196fe6cb380c
+msgid "Converting a Hyper-V VM to a Template"
+msgstr ""
+
+#: ../../templates.rst:918
+# 3edfac90ab644da58894eab904cc447c
+msgid "To convert a Hyper-V VM to a XenServer-compatible CloudStack template, you will need a standalone XenServer host with an attached NFS VHD SR. Use whatever XenServer version you are using with CloudStack, but use XenCenter 5.6 FP1 or SP2 (it is backwards compatible to 5.6). Additionally, it may help to have an attached NFS ISO SR."
+msgstr ""
+
+#: ../../templates.rst:924
+# b65f920f7aa24af9b850a9b006b20069
+msgid "For Linux VMs, you may need to do some preparation in Hyper-V before trying to get the VM to work in XenServer. Clone the VM and work on the clone if you still want to use the VM in Hyper-V. Uninstall Hyper-V Integration Components and check for any references to device names in /etc/fstab:"
+msgstr ""
+
+#: ../../templates.rst:930
+# 163cf95a7ec7444d8308e6f3915b94f7
+msgid "From the linux\\_ic/drivers/dist directory, run make uninstall (where \"linux\\_ic\" is the path to the copied Hyper-V Integration Components files)."
+msgstr ""
+
+#: ../../templates.rst:934
+# 32eb47eefa0b4af493237f82dd0f08e1
+msgid "Restore the original initrd from backup in /boot/ (the backup is named \\*.backup0)."
+msgstr ""
+
+#: ../../templates.rst:937
+# b7363d0658ff4efcb9bdf4657296d185
+msgid "Remove the \"hdX=noprobe\" entries from /boot/grub/menu.lst."
+msgstr ""
+
+#: ../../templates.rst:939
+# f8878c3d06ea47b0b8c1cfaf1721f34b
+msgid "Check /etc/fstab for any partitions mounted by device name. Change those entries (if any) to mount by LABEL or UUID. You can get that information with the blkid command."
+msgstr ""
+
+#: ../../templates.rst:943
+# 685ac8156ffb427f853074d04df8be85
+msgid "The next step is make sure the VM is not running in Hyper-V, then get the VHD into XenServer. There are two options for doing this."
+msgstr ""
+
+#: ../../templates.rst:946
+# 2a0e0f2e121b4d30bb10710db99fd9cb
+msgid "Option one:"
+msgstr ""
+
+#: ../../templates.rst:948
+# 7006009b5d4d452d9a3936d365133d47
+msgid "Import the VHD using XenCenter. In XenCenter, go to Tools>Virtual Appliance Tools>Disk Image Import."
+msgstr ""
+
+#: ../../templates.rst:951
+#: ../../templates.rst:963
+# 0b382531327d4323aa4983bacc4ed07f
+# d535d0d741a64664bf63603df9967f1f
+msgid "Choose the VHD, then click Next."
+msgstr ""
+
+#: ../../templates.rst:953
+# 2a052e079f674601944c0ba73a344456
+msgid "Name the VM, choose the NFS VHD SR under Storage, enable \"Run Operating System Fixups\" and choose the NFS ISO SR."
+msgstr ""
+
+#: ../../templates.rst:956
+# cc2978604a5d4e41bc9bf810c2d56de3
+msgid "Click Next, then Finish. A VM should be created."
+msgstr ""
+
+#: ../../templates.rst:958
+# 67a0e0a79a8a4361a4a7a54ce0f7d4bb
+msgid "Option two:"
+msgstr ""
+
+#: ../../templates.rst:960
+# 30a1d3fd83154d909f816cbdb7f05e1e
+msgid "Run XenConvert, under From choose VHD, under To choose XenServer. Click Next."
+msgstr ""
+
+#: ../../templates.rst:965
+# a00bf9e6d260466fbec3fa0226669cdb
+msgid "Input the XenServer host info, then click Next."
+msgstr ""
+
+#: ../../templates.rst:967
+# 44711d8c01324ee79a30d8ce8b327a78
+msgid "Name the VM, then click Next, then Convert. A VM should be created."
+msgstr ""
+
+#: ../../templates.rst:969
+# 92901943e7874fb1a3d951cd238e0711
+msgid "Once you have a VM created from the Hyper-V VHD, prepare it using the following steps:"
+msgstr ""
+
+#: ../../templates.rst:972
+# 86356c840f4d4588a591dc27d244bfca
+msgid "Boot the VM, uninstall Hyper-V Integration Services, and reboot."
+msgstr ""
+
+#: ../../templates.rst:974
+# b7695ac5e06a43afb682c51148ea61a2
+msgid "Install XenServer Tools, then reboot."
+msgstr ""
+
+#: ../../templates.rst:976
+# 35c3a56ed699450c91f45bdba9627f4c
+msgid "Prepare the VM as desired. For example, run sysprep on Windows VMs. See `“Creating a Windows Template” <#creating-a-windows-template>`_."
+msgstr ""
+
+#: ../../templates.rst:980
+# 35897d5ecf6144a88204cb836ee76084
+msgid "Either option above will create a VM in HVM mode. This is fine for Windows VMs, but Linux VMs may not perform optimally. Converting a Linux VM to PV mode will require additional steps and will vary by distribution."
+msgstr ""
+
+#: ../../templates.rst:985
+# e4c0e0e192034e3b9e9439d79eae9bb3
+msgid "Shut down the VM and copy the VHD from the NFS storage to a web server; for example, mount the NFS share on the web server and copy it, or from the XenServer host use sftp or scp to upload it to the web server."
+msgstr ""
+
+#: ../../templates.rst:990
+# 96fa0ff0b9e842af9381d561f9534955
+msgid "In CloudStack, create a new template using the following values:"
+msgstr ""
+
+#: ../../templates.rst:992
+# 713fe06958f947ecb69e69b7d6b4d85e
+msgid "URL. Give the URL for the VHD"
+msgstr ""
+
+#: ../../templates.rst:994
+# 4af6eb652e6744cca4ac135718ee31e2
+msgid "OS Type. Use the appropriate OS. For PV mode on CentOS, choose Other PV (32-bit) or Other PV (64-bit). This choice is available only for XenServer."
+msgstr ""
+
+#: ../../templates.rst:998
+# 2d17699c6d72457e94c849e9369be071
+msgid "Hypervisor. XenServer"
+msgstr ""
+
+#: ../../templates.rst:1000
+# 0fe80c0299054980a5b04cae8c3a89c4
+msgid "Format. VHD"
+msgstr ""
+
+#: ../../templates.rst:1002
+# 0a2022d596764dda94ee0b8c61a7b8f6
+msgid "The template will be created, and you can create instances from it."
+msgstr ""
+
+#: ../../templates.rst:1008
+# 4a48b7a200f84177bc4c2935b3cb7020
+msgid "Adding Password Management to Your Templates"
+msgstr ""
+
+#: ../../templates.rst:1010
+# c24c604a1aa648859c9853bd23207c13
+msgid "CloudStack provides an optional password reset feature that allows users to set a temporary admin or root password as well as reset the existing admin or root password from the CloudStack UI."
+msgstr ""
+
+#: ../../templates.rst:1014
+# 217ddf1185f5412999996969e470b02e
+msgid "To enable the Reset Password feature, you will need to download an additional script to patch your template. When you later upload the template into CloudStack, you can specify whether reset admin/root password feature should be enabled for this template."
+msgstr ""
+
+#: ../../templates.rst:1019
+# bed2001bd6fd4768808ffe617fb80007
+msgid "The password management feature works always resets the account password on instance boot. The script does an HTTP call to the virtual router to retrieve the account password that should be set. As long as the virtual router is accessible the guest will have access to the account password that should be used. When the user requests a password reset the management server generates and sends a new password to the virtual router for the account. Thus an instance reboot is necessary to effect any password changes."
+msgstr ""
+
+#: ../../templates.rst:1028
+# 6294578d1b274e62ad53e3b5b90dba5e
+msgid "If the script is unable to contact the virtual router during instance boot it will not set the password but boot will continue normally."
+msgstr ""
+
+#: ../../templates.rst:1033
+# 19d468fa67b84dc4ad8a85a6c367545c
+msgid "Linux OS Installation"
+msgstr ""
+
+#: ../../templates.rst:1035
+# 8dafc3143daa4624ac256c0d1deebdb3
+msgid "Use the following steps to begin the Linux OS installation:"
+msgstr ""
+
+#: ../../templates.rst:1037
+# 4cc0194e2b4049d186735606a395ff0c
+msgid "Download the script file cloud-set-guest-password:"
+msgstr ""
+
+#: ../../templates.rst:1039
+# 7dfc38f9a99c4d0bbb5007329350693e
+msgid "`http://download.cloud.com/templates/4.2/bindir/cloud-set-guest-password.in <http://download.cloud.com/templates/4.2/bindir/cloud-set-guest-password.in>`_"
+msgstr ""
+
+#: ../../templates.rst:1042
+# 6eead5e6602446c78f65d37e092b049f
+msgid "Copy this file to /etc/init.d."
+msgstr ""
+
+#: ../../templates.rst:1044
+# 2819cf0c972f4042931c612b737e8f1d
+msgid "On some Linux distributions, copy the file to ``/etc/rc.d/init.d``."
+msgstr ""
+
+#: ../../templates.rst:1046
+# f914b404aef44aa1a7fbc43160c833b3
+msgid "Run the following command to make the script executable:"
+msgstr ""
+
+#: ../../templates.rst:1052
+# ae8119d7538749fb95c1ce6ac6541c59
+msgid "Depending on the Linux distribution, continue with the appropriate step."
+msgstr ""
+
+#: ../../templates.rst:1055
+# c85e239054a542e88bb0030af7cb7a19
+msgid "On Fedora, CentOS/RHEL, and Debian, run:"
+msgstr ""
+
+#: ../../templates.rst:1063
+# e83101bd5fd3442f817ec22d010edc3e
+msgid "Windows OS Installation"
+msgstr ""
+
+#: ../../templates.rst:1065
+# c40beb0a6d5c466c994729dba2d4b12e
+msgid "Download the installer, CloudInstanceManager.msi, from the `Download page <http://sourceforge.net/projects/cloudstack/files/Password%20Management%20Scripts/CloudInstanceManager.msi/download>`_ and run the installer in the newly created Windows VM."
+msgstr ""
+
+#: ../../templates.rst:1071
+# 56df3bfa3de0447b9f0a0b4f02a1fb4c
+msgid "Deleting Templates"
+msgstr ""
+
+#: ../../templates.rst:1073
+# 2d005d50f15746f793e20a2343fe6e29
+msgid "Templates may be deleted. In general, when a template spans multiple Zones, only the copy that is selected for deletion will be deleted; the same template in other Zones will not be deleted. The provided CentOS template is an exception to this. If the provided CentOS template is deleted, it will be deleted from all Zones."
+msgstr ""
+
+#: ../../templates.rst:1079
+# 4ddffe7d5d2b4f14814054eea2d8fd47
+msgid "When templates are deleted, the VMs instantiated from them will continue to run. However, new VMs cannot be created based on the deleted template."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/troubleshooting.pot b/source/adminguide/locale/pot/troubleshooting.pot
new file mode 100644
index 0000000..c9164fa
--- /dev/null
+++ b/source/adminguide/locale/pot/troubleshooting.pot
@@ -0,0 +1,383 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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"
+
+#: ../../troubleshooting.rst:18
+# 453abc0964244620ab303e8bbdd16340
+msgid "TroubleShooting"
+msgstr ""
+
+#: ../../troubleshooting.rst:21
+# b90eea0457d64f3cb90be7deabcaa0c3
+msgid "Working with Server Logs"
+msgstr ""
+
+#: ../../troubleshooting.rst:23
+# 9d89b655688d4af2bfc8302c8a0c9134
+msgid "The CloudStack Management Server logs all web site, middle tier, and database activities for diagnostics purposes in `/var/log/cloudstack/management/`. The CloudStack logs a variety of error messages. We recommend this command to find the problematic output in the Management Server log:."
+msgstr ""
+
+#: ../../troubleshooting.rst:30
+# 3fc8e92bb3a741c3bd3a67d67cf0e9a3
+msgid "When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text."
+msgstr ""
+
+#: ../../troubleshooting.rst:38
+# 845cfc971cf84bbca9edce162a942ad2
+msgid "The CloudStack processes requests with a Job ID. If you find an error in the logs and you are interested in debugging the issue you can grep for this job ID in the management server log. For example, suppose that you find the following ERROR message:"
+msgstr ""
+
+#: ../../troubleshooting.rst:47
+# f7529d9ff27a4e27bdad7d8a6435087a
+msgid "Note that the job ID is 1076. You can track back the events relating to job 1076 with the following grep:"
+msgstr ""
+
+#: ../../troubleshooting.rst:54
+# 4da5450950cc43b79b6d4391e28f4f41
+msgid "The CloudStack Agent Server logs its activities in `/var/log/cloudstack/agent/`."
+msgstr ""
+
+#: ../../troubleshooting.rst:58
+# ba4670a0c5444406a2eb230cb99333d5
+msgid "Data Loss on Exported Primary Storage"
+msgstr ""
+
+#: ../../troubleshooting.rst:61
+#: ../../troubleshooting.rst:99
+#: ../../troubleshooting.rst:140
+#: ../../troubleshooting.rst:162
+#: ../../troubleshooting.rst:185
+#: ../../troubleshooting.rst:219
+# b0ef204b69a54f32bd49070c4b9b6a91
+# 96d811275eea4240af38ec923db3c739
+# 03085fe48e6f4b379bcb1b827fff32d4
+# 83a83346af6342ae960e60c796e896d3
+# dc69c8f4922e4f69a378d3a16a609df7
+# 3970143e5afb4c03a4b3aed0f9e50fc7
+msgid "Symptom"
+msgstr ""
+
+#: ../../troubleshooting.rst:63
+# a5727b8982354aaeb9aaa3eaccf41ef9
+msgid "Loss of existing data on primary storage which has been exposed as a Linux NFS server export on an iSCSI volume."
+msgstr ""
+
+#: ../../troubleshooting.rst:68
+#: ../../troubleshooting.rst:106
+#: ../../troubleshooting.rst:146
+#: ../../troubleshooting.rst:168
+#: ../../troubleshooting.rst:197
+#: ../../troubleshooting.rst:226
+# 77646ea81e804cb9ada6c17c6289cbbe
+# e5b68ba31d5948388069cf4e01357332
+# 48d47c0902414b5194a1d38398971eb6
+# 8c13e9a8446c49ef90ae29a314ee0d33
+# 8a80e812487d4bf6b38f6cdc6feddae0
+# 350e1aaa22b5432f8065bdf94cc27e02
+msgid "Cause"
+msgstr ""
+
+#: ../../troubleshooting.rst:70
+# 8ca868ba6d9349e6b0d83564a152f19e
+msgid "It is possible that a client from outside the intended pool has mounted the storage. When this occurs, the LVM is wiped and all data in the volume is lost"
+msgstr ""
+
+#: ../../troubleshooting.rst:76
+#: ../../troubleshooting.rst:112
+#: ../../troubleshooting.rst:153
+#: ../../troubleshooting.rst:176
+#: ../../troubleshooting.rst:207
+#: ../../troubleshooting.rst:235
+# 4934510ae4ce4c79a0ed5d6ee26fea0a
+# df9bd94f2f95481f93b741b643baedfb
+# 5d33b8b45f404f25abcb9d3fbfeafb70
+# 044a6cc8e613432ab218a02d3bbde2a1
+# 4445e221c952428fb2585060c4540dee
+# 7c3b4d63c42d4990999e96195fe72cca
+msgid "Solution"
+msgstr ""
+
+#: ../../troubleshooting.rst:78
+# 990ebb2f5e854a479d94d06df1280a15
+msgid "When setting up LUN exports, restrict the range of IP addresses that are allowed access by specifying a subnet mask. For example:"
+msgstr ""
+
+#: ../../troubleshooting.rst:85
+# 17f9dff87a0b4b848b2938ad46c42bfc
+msgid "Adjust the above command to suit your deployment needs."
+msgstr ""
+
+#: ../../troubleshooting.rst:89
+# 9dd74bb044b640dcb1b4e410db1a44e2
+msgid "More Information"
+msgstr ""
+
+#: ../../troubleshooting.rst:91
+# 6c10365641b54f549e84579ccb8d4fe2
+msgid "See the export procedure in the \"Secondary Storage\" section of the CloudStack Installation Guide"
+msgstr ""
+
+#: ../../troubleshooting.rst:96
+# 08ecc200c09045599e0c1f960186fdc4
+msgid "Recovering a Lost Virtual Router"
+msgstr ""
+
+#: ../../troubleshooting.rst:101
+# db28bc81f196417980c31fd2d4b63f29
+msgid "A virtual router is running, but the host is disconnected. A virtual router no longer functions as expected."
+msgstr ""
+
+#: ../../troubleshooting.rst:108
+# a6ac53ae9be44b4e8b3602647222e9ac
+msgid "The Virtual router is lost or down."
+msgstr ""
+
+#: ../../troubleshooting.rst:114
+# 1bd58bc5e2314d0cbf2e0059b096bf0a
+msgid "If you are sure that a virtual router is down forever, or no longer functions as expected, destroy it. You must create one afresh while keeping the backup router up and running (it is assumed this is in a redundant router setup):"
+msgstr ""
+
+#: ../../troubleshooting.rst:119
+# 19e8516bc79a4b7faeb2645670f3a6a1
+msgid "Force stop the router. Use the stopRouter API with forced=true parameter to do so."
+msgstr ""
+
+#: ../../troubleshooting.rst:122
+# 340f24e153484784bc1cf3b493c32ea3
+msgid "Before you continue with destroying this router, ensure that the backup router is running. Otherwise the network connection will be lost."
+msgstr ""
+
+#: ../../troubleshooting.rst:126
+# c2db1e8bd10547bfacb3e2d044ca6d06
+msgid "Destroy the router by using the destroyRouter API."
+msgstr ""
+
+#: ../../troubleshooting.rst:128
+# af3e07ca34034b49b6dba68eb7da16f3
+msgid "Recreate the missing router by using the restartNetwork API with cleanup=false parameter. For more information about redundant router setup, see Creating a New Network Offering."
+msgstr ""
+
+#: ../../troubleshooting.rst:132
+# 25bdb5c7a6a7454ea25d62c3f0a02c57
+msgid "For more information about the API syntax, see the API Reference at `http://cloudstack.apache.org/docs/api/ <http://cloudstack.apache.org/docs/api/>`_."
+msgstr ""
+
+#: ../../troubleshooting.rst:137
+# d1a32a2023024c72907911b8c7757cae
+msgid "Maintenance mode not working on vCenter"
+msgstr ""
+
+#: ../../troubleshooting.rst:142
+# bd6813f30ddc4a0da8cf13b7725c9748
+msgid "Host was placed in maintenance mode, but still appears live in vCenter."
+msgstr ""
+
+#: ../../troubleshooting.rst:148
+# 7241c889dd0842189f0c38eda241d14b
+msgid "The CloudStack administrator UI was used to place the host in scheduled maintenance mode. This mode is separate from vCenter's maintenance mode."
+msgstr ""
+
+#: ../../troubleshooting.rst:155
+# a959d82ede064a89ad631ce910f8f7df
+msgid "Use vCenter to place the host in maintenance mode."
+msgstr ""
+
+#: ../../troubleshooting.rst:159
+# f3c4a03f0b5042009b2e858d5b259496
+msgid "Unable to deploy VMs from uploaded vSphere template"
+msgstr ""
+
+#: ../../troubleshooting.rst:164
+# f0d6310e9be647eda1506c7161d33a8b
+msgid "When attempting to create a VM, the VM will not deploy."
+msgstr ""
+
+#: ../../troubleshooting.rst:170
+# 82efe5f025f8468c99e720b0e00c067e
+msgid "If the template was created by uploading an OVA file that was created using vSphere Client, it is possible the OVA contained an ISO image. If it does, the deployment of VMs from the template will fail."
+msgstr ""
+
+#: ../../troubleshooting.rst:178
+# c61b5fec4b5d4b75afac37386a78b766
+msgid "Remove the ISO and re-upload the template."
+msgstr ""
+
+#: ../../troubleshooting.rst:182
+# 7d4b56be6f504129860c6d5c12fd73d5
+msgid "Unable to power on virtual machine on VMware"
+msgstr ""
+
+#: ../../troubleshooting.rst:187
+# bb0c46e2f09647f9a260c9e676f72afb
+msgid "Virtual machine does not power on. You might see errors like:"
+msgstr ""
+
+#: ../../troubleshooting.rst:189
+# 92c768be206b4267bb993ce6b1b74d77
+msgid "Unable to open Swap File"
+msgstr ""
+
+#: ../../troubleshooting.rst:191
+# a63cf9eda829479b835aff2d3b017460
+msgid "Unable to access a file since it is locked"
+msgstr ""
+
+#: ../../troubleshooting.rst:193
+# 0deea4202b4b41d9a4fab5ae3dad09bf
+msgid "Unable to access Virtual machine configuration"
+msgstr ""
+
+#: ../../troubleshooting.rst:199
+# 0605d083a0fa4569ad92e3ea1cfe6634
+msgid "A known issue on VMware machines. ESX hosts lock certain critical virtual machine files and file systems to prevent concurrent changes. Sometimes the files are not unlocked when the virtual machine is powered off. When a virtual machine attempts to power on, it can not access these critical files, and the virtual machine is unable to power on."
+msgstr ""
+
+#: ../../troubleshooting.rst:209
+# 177329a9571d49b5bce7dc8d84731724
+msgid "See the following:"
+msgstr ""
+
+#: ../../troubleshooting.rst:211
+# 344210667a0d414a89c35ba8bce56ca0
+msgid "`VMware Knowledge Base Article <http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=10051/>`_"
+msgstr ""
+
+#: ../../troubleshooting.rst:216
+# 7e82b8b3093b42cfb1088af2632abacf
+msgid "Load balancer rules fail after changing network offering"
+msgstr ""
+
+#: ../../troubleshooting.rst:221
+# 8feb8c6245fb490d835881b4996a3504
+msgid "After changing the network offering on a network, load balancer rules stop working."
+msgstr ""
+
+#: ../../troubleshooting.rst:228
+# dea9609b31dc4131b77505535e3aca09
+msgid "Load balancing rules were created while using a network service offering that includes an external load balancer device such as NetScaler, and later the network service offering changed to one that uses the CloudStack virtual router."
+msgstr ""
+
+#: ../../troubleshooting.rst:237
+# e344e7e16a5145ee9dfeb6c9057e6cb6
+msgid "Create a firewall rule on the virtual router for each of your existing load balancing rules so that they continue to function."
+msgstr ""
+
+#: ../../troubleshooting.rst:242
+# 8bc5100986b347c1a08bbeb52b64f7f7
+msgid "Troubleshooting Internet Traffic"
+msgstr ""
+
+#: ../../troubleshooting.rst:244
+# 5f383b9190f34ebcbdd6bb92b713ee21
+msgid "Below are a few troubleshooting steps to check whats going wrong with your network..."
+msgstr ""
+
+#: ../../troubleshooting.rst:249
+# 07599df9fe734016810667b0edbc9a49
+msgid "Trouble Shooting Steps"
+msgstr ""
+
+#: ../../troubleshooting.rst:251
+# 1a82d41b488b46c2bef892a561b3756c
+msgid "The switches have to be configured correctly to pass VLAN traffic. You can verify if VLAN traffic is working by bringing up a tagged interface on the hosts and pinging between them as below..."
+msgstr ""
+
+#: ../../troubleshooting.rst:255
+# 6b44f2f662ed49199d66820be6f6de02
+msgid "On *host1 (kvm1)*"
+msgstr ""
+
+#: ../../troubleshooting.rst:263
+# 5120295551574a56817a504f54bfe602
+msgid "On *host2 (kvm2)*"
+msgstr ""
+
+#: ../../troubleshooting.rst:271
+# 417a511656394e62ab6533726322a54e
+msgid "If the pings dont work, run *tcpdump(8)* all over the place to check who is gobbling up the packets. Ultimately, if the switches are not configured correctly, CloudStack networking wont work so fix the physical networking issues before you proceed to the next steps"
+msgstr ""
+
+#: ../../troubleshooting.rst:276
+# 63be4a452fb043e1ad03834e2b6afc37
+msgid "Ensure `Traffic Labels <http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/about-physical-networks.html>`_ are set for the Zone."
+msgstr ""
+
+#: ../../troubleshooting.rst:278
+# 997b8cf202374996adfbc66cf272e85d
+msgid "Traffic labels need to be set for all hypervisors including XenServer, KVM and VMware types. You can configure traffic labels when you creating a new zone from the *Add Zone Wizard*."
+msgstr ""
+
+#: ../../troubleshooting.rst:284
+# 7f2757fe05a54b7890d5b634724bd166
+msgid "On an existing zone, you can modify the traffic labels by going to *Infrastructure, Zones, Physical Network* tab."
+msgstr ""
+
+#: ../../troubleshooting.rst:289
+# de6b7290f1874731bab19679f2b1c123
+msgid "List labels using *CloudMonkey*"
+msgstr ""
+
+#: ../../troubleshooting.rst:321
+# d7be5d89abc2416a81c2e11ae80e5c5e
+msgid "KVM traffic labels require to be named as *\"cloudbr0\"*, *\"cloudbr2\"*, *\"cloudbrN\"* etc and the corresponding bridge must exist on the KVM hosts. If you create labels/bridges with any other names, CloudStack (atleast earlier versions did) seems to ignore them. CloudStack does not create the physical bridges on the KVM hosts, you need to create them **before** before adding the host to Cloudstack."
+msgstr ""
+
+#: ../../troubleshooting.rst:340
+# 4d5d185d16bb4379b29d90b15b9e9855
+msgid "The Virtual Router, SSVM, CPVM *public* interface would be bridged to a physical interface on the host. In the example below, *cloudbr0* is the public interface and CloudStack has correctly created the virtual interfaces bridge. This virtual interface to physical interface mapping is done automatically by CloudStack using the traffic label settings for the Zone. If you have provided correct settings and still dont have a working working Internet, check the switching layer before you debug any further. You can verify traffic using tcpdump on the virtual, physical and bridge interfaces."
+msgstr ""
+
+#: ../../troubleshooting.rst:372
+# f261f43d727440edbeaf4c36ca611f7c
+msgid "Pre-create labels on the XenServer Hosts. Similar to KVM bridge setup, traffic labels must also be pre-created on the XenServer hosts before adding them to CloudStack."
+msgstr ""
+
+#: ../../troubleshooting.rst:385
+# e75bf706d6a745c9a94ee34516e86d1f
+msgid "The Internet would be accessible from both the SSVM and CPVM instances by default. Their public IPs will also be directly pingable from the Internet. Please note that these test would work only if your switches and traffic labels are configured correctly for your environment. If your SSVM/CPVM cant reach the Internet, its very unlikely that the Virtual Router (VR) can also the reach the Internet suggesting that its either a switching issue or incorrectly assigned traffic labels. Fix the SSVM/CPVM issues before you debug VR issues."
+msgstr ""
+
+#: ../../troubleshooting.rst:417
+# c1f11bc2b9ea470382b5f863e8d1a146
+msgid "The Virtual Router (VR) should also be able to reach the Internet without having any Egress rules. The Egress rules only control forwarded traffic and not traffic that originates on the VR itself."
+msgstr ""
+
+#: ../../troubleshooting.rst:432
+# fd961e75e43d4c48a4b779ef136e1d12
+msgid "However, the Virtual Router's (VR) Source NAT Public IP address **WONT** be reachable until appropriate Ingress rules are in place. You can add *Ingress* rules under *Network, Guest Network, IP Address, Firewall* setting page."
+msgstr ""
+
+#: ../../troubleshooting.rst:439
+# 7a1ba3d03cd64a0cb60486d361453ebd
+msgid "The VM Instances by default wont be able to access the Internet. Add Egress rules to permit traffic."
+msgstr ""
+
+#: ../../troubleshooting.rst:444
+# 2d798a14dcd149af8197080268c1b12b
+msgid "Some users have reported that flushing IPTables rules (or changing routes) on the SSVM, CPVM or the Virtual Router makes the Internet work. This is not expected behaviour and suggests that your networking settings are incorrect. No IPtables/route changes are required on the SSVM, CPVM or the VR. Go back and double check all your settings."
+msgstr ""
+
+#: ../../troubleshooting.rst:451
+# e14dab36e181467a9fd09fb6d0283176
+msgid "In a vast majority of the cases, the problem has turned out to be at the switching layer where the L3 switches were configured incorrectly."
+msgstr ""
+
+#: ../../troubleshooting.rst:454
+# 5fff1dc7083a4412a9e4051f2e239180
+msgid "This section was contibuted by Shanker Balan and was originally published on `Shapeblue's blog <http://shankerbalan.net/blog/internet-not-working-on-cloudstack-vms/>`_"
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/tuning.pot b/source/adminguide/locale/pot/tuning.pot
new file mode 100644
index 0000000..d13b8e8
--- /dev/null
+++ b/source/adminguide/locale/pot/tuning.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 <EMAIL@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 <EMAIL@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"
+
+#: ../../tuning.rst:18
+# 0c7c82c60c1c4ce4b2ec9838cc883b84
+msgid "Tuning"
+msgstr ""
+
+#: ../../tuning.rst:20
+# 9a2a025467014e929276cfa1e9e73e71
+msgid "This section provides tips on how to improve the performance of your cloud."
+msgstr ""
+
+#: ../../tuning.rst:25
+# 9b00143dbb7b4b4b97baab2aa95815aa
+msgid "Performance Monitoring"
+msgstr ""
+
+#: ../../tuning.rst:27
+# 43c6615bb7084bc58dbf0561984e39f3
+msgid "Host and guest performance monitoring is available to end users and administrators. This allows the user to monitor their utilization of resources and determine when it is appropriate to choose a more powerful service offering or larger disk."
+msgstr ""
+
+#: ../../tuning.rst:34
+# 470932b76e664973b7568b285a10a77d
+msgid "Increase Management Server Maximum Memory"
+msgstr ""
+
+#: ../../tuning.rst:36
+# 82b1560c6fbf421b952de1c8424aa4a2
+msgid "If the Management Server is subject to high demand, the default maximum JVM memory allocation can be insufficient. To increase the memory:"
+msgstr ""
+
+#: ../../tuning.rst:39
+# 1b69cb03d370442f913397dde140c37c
+msgid "Edit the Tomcat configuration file:"
+msgstr ""
+
+#: ../../tuning.rst:45
+# d9a022a48b8a4076872b335db29f658c
+msgid "Change the command-line parameter -XmxNNNm to a higher value of N."
+msgstr ""
+
+#: ../../tuning.rst:47
+# bf5935dc78264c1baf8cd4984a631b98
+msgid "For example, if the current value is -Xmx128m, change it to -Xmx1024m or higher."
+msgstr ""
+
+#: ../../tuning.rst:50
+# e4dda8bcace04b10a404493586f871a1
+msgid "To put the new setting into effect, restart the Management Server."
+msgstr ""
+
+#: ../../tuning.rst:56
+# 4b11c5fd61d0469480f110a7ebe528d0
+msgid "For more information about memory issues, see \"FAQ: Memory\" at `Tomcat Wiki. <http://wiki.apache.org/tomcat/FAQ/Memory>`_"
+msgstr ""
+
+#: ../../tuning.rst:61
+# 588f5981eb3843ac91a1041e9f3bb832
+msgid "Set Database Buffer Pool Size"
+msgstr ""
+
+#: ../../tuning.rst:63
+# 2a1e327a1aa04838bfefce6674d9ec3e
+msgid "It is important to provide enough memory space for the MySQL database to cache data and indexes:"
+msgstr ""
+
+#: ../../tuning.rst:66
+# 55bafed06cb5401fba6713f86660fe74
+msgid "Edit the MySQL configuration file:"
+msgstr ""
+
+#: ../../tuning.rst:72
+# a2719920b1ad4f2388c10ed8f19e5437
+msgid "Insert the following line in the [mysqld] section, below the datadir line. Use a value that is appropriate for your situation. We recommend setting the buffer pool at 40% of RAM if MySQL is on the same server as the management server or 70% of RAM if MySQL has a dedicated server. The following example assumes a dedicated server with 1024M of RAM."
+msgstr ""
+
+#: ../../tuning.rst:83
+# 30d79aae5ff745b789f7e402c61d4164
+msgid "Restart the MySQL service."
+msgstr ""
+
+#: ../../tuning.rst:89
+# b12c7032e74b411d9d9c7bc32a92a3ab
+msgid "For more information about the buffer pool, see \"The InnoDB Buffer Pool\" at `MySQL Reference Manual <http://dev.mysql.com/doc/refman/5.5/en/innodb-buffer-pool.html>`_."
+msgstr ""
+
+#: ../../tuning.rst:95
+# 1cbfe60313d445848eb5e90f708b55a1
+msgid "Set and Monitor Total VM Limits per Host"
+msgstr ""
+
+#: ../../tuning.rst:97
+# 36520c7bbf2b4888813341615ca176fa
+msgid "The CloudStack administrator should monitor the total number of VM instances in each cluster, and disable allocation to the cluster if the total is approaching the maximum that the hypervisor can handle. Be sure to leave a safety margin to allow for the possibility of one or more hosts failing, which would increase the VM load on the other hosts as the VMs are automatically redeployed. Consult the documentation for your chosen hypervisor to find the maximum permitted number of VMs per host, then use CloudStack global configuration settings to set this as the default limit. Monitor the VM activity in each cluster at all times. Keep the total number of VMs below a safe level that allows for the occasional host failure. For example, if there are N hosts in the cluster, and you want to allow for one host in the cluster to be down at any given time, the total number of VM instances you can permit in the cluster is at most (N-1) \\* (per-host-limit). Once a cluster reaches this number of VMs, use the CloudStack UI to disable allocation of more VMs to the cluster."
+msgstr ""
+
+#: ../../tuning.rst:116
+# 87fad0d347f845e4b589cf1b70bfaad0
+msgid "Configure XenServer dom0 Memory"
+msgstr ""
+
+#: ../../tuning.rst:118
+# e6d8fead31da4d2880407fe308a0c13a
+msgid "Configure the XenServer dom0 settings to allocate more memory to dom0. This can enable XenServer to handle larger numbers of virtual machines. We recommend 2940 MB of RAM for XenServer dom0. For instructions on how to do this, see `Citrix Knowledgebase Article <http://support.citrix.com/article/CTX126531>`_.The article refers to XenServer 5.6, but the same information applies to XenServer 6"
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/ui.pot b/source/adminguide/locale/pot/ui.pot
new file mode 100644
index 0000000..5830e1d
--- /dev/null
+++ b/source/adminguide/locale/pot/ui.pot
@@ -0,0 +1,190 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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"
+
+#: ../../ui.rst:18
+# 823af79fce60474780309ce761b8cbb3
+msgid "User Interface"
+msgstr ""
+
+#: ../../ui.rst:21
+# a41f3714ea474cafa002318580d95e84
+msgid "Log In to the UI"
+msgstr ""
+
+#: ../../ui.rst:23
+# aab161d8e0fa441c97c979ad5befdaf2
+msgid "CloudStack provides a web-based UI that can be used by both administrators and end users. The appropriate version of the UI is displayed depending on the credentials used to log in. The UI is available in popular browsers including IE7, IE8, IE9, Firefox 3.5+, Firefox 4, Safari 4, and Safari 5. The URL is: (substitute your own management server IP address)"
+msgstr ""
+
+#: ../../ui.rst:34
+# 5757c519124e45b4b91631b922360a4c
+msgid "On a fresh Management Server installation, a guided tour splash screen appears. On later visits, you’ll see a login screen where you specify the following to proceed to your Dashboard:"
+msgstr ""
+
+#: ../../ui.rst:38
+# 192d35e05058441db921256f04a28daf
+msgid "Username -> The user ID of your account. The default username is admin."
+msgstr ""
+
+#: ../../ui.rst:40
+# 7ca04676225345a3a4d7e9f05fa900b9
+msgid "Password -> The password associated with the user ID. The password for the default username is password."
+msgstr ""
+
+#: ../../ui.rst:43
+# fff9c234e7724e1aa8a5ca63b9cbc714
+msgid "Domain -> If you are a root user, leave this field blank."
+msgstr ""
+
+#: ../../ui.rst:45
+# f7cc367a3acb49149809ad5212740659
+msgid "If you are a user in the sub-domains, enter the full path to the domain, excluding the root domain."
+msgstr ""
+
+#: ../../ui.rst:48
+# 2716e01ce2b446be9cf2b3c098897945
+msgid "For example, suppose multiple levels are created under the root domain, such as Comp1/hr. The users in the Comp1 domain should enter Comp1 in the Domain field, whereas the users in the Comp1/sales domain should enter Comp1/sales."
+msgstr ""
+
+#: ../../ui.rst:53
+# dab31f7d62b846799291e80598d3534d
+msgid "For more guidance about the choices that appear when you log in to this UI, see Logging In as the Root Administrator."
+msgstr ""
+
+#: ../../ui.rst:58
+# f89e19a4f46d49d3899770c2d8d858ae
+msgid "End User's UI Overview"
+msgstr ""
+
+#: ../../ui.rst:60
+# fab0b6e0d255493e9c1a1800bffbd107
+msgid "The CloudStack UI helps users of cloud infrastructure to view and use their cloud resources, including virtual machines, templates and ISOs, data volumes and snapshots, guest networks, and IP addresses. If the user is a member or administrator of one or more CloudStack projects, the UI can provide a project-oriented view."
+msgstr ""
+
+#: ../../ui.rst:68
+# 03bffb509d6342f09a88c6c18b4a0041
+msgid "Root Administrator's UI Overview"
+msgstr ""
+
+#: ../../ui.rst:70
+# f46ea02636f0416ab79e48c05c194422
+msgid "The CloudStack UI helps the CloudStack administrator provision, view, and manage the cloud infrastructure, domains, user accounts, projects, and configuration settings. The first time you start the UI after a fresh Management Server installation, you can choose to follow a guided tour to provision your cloud infrastructure. On subsequent logins, the dashboard of the logged-in user appears. The various links in this screen and the navigation bar on the left provide access to a variety of administrative functions. The root administrator can also use the UI to perform all the same tasks that are present in the end-user’s UI."
+msgstr ""
+
+#: ../../ui.rst:82
+# 2010e004d6354a46899b6e0a6177a36a
+msgid "Logging In as the Root Administrator"
+msgstr ""
+
+#: ../../ui.rst:84
+# beb82ae526444b67b6c2baff8c7901a7
+msgid "After the Management Server software is installed and running, you can run the CloudStack user interface. This UI is there to help you provision, view, and manage your cloud infrastructure."
+msgstr ""
+
+#: ../../ui.rst:88
+#: ../../ui.rst:151
+# 6beabdba74e7408e8fcc8ffa226a704e
+# 8c7e2423aea64ae6b5b2f13c8c000895
+msgid "Open your favorite Web browser and go to this URL. Substitute the IP address of your own Management Server:"
+msgstr ""
+
+#: ../../ui.rst:95
+# 5afc8c800bcb4248a79f7b7dc8ea6173
+msgid "After logging into a fresh Management Server installation, a guided tour splash screen appears. On later visits, you’ll be taken directly into the Dashboard."
+msgstr ""
+
+#: ../../ui.rst:99
+# a27fd5db6a0d41dbb4d17954889871c7
+msgid "If you see the first-time splash screen, choose one of the following."
+msgstr ""
+
+#: ../../ui.rst:101
+# f9579429faa6431a9cc007c91af49e61
+msgid "**Continue with basic setup.** Choose this if you're just trying CloudStack, and you want a guided walkthrough of the simplest possible configuration so that you can get started right away. We'll help you set up a cloud with the following features: a single machine that runs CloudStack software and uses NFS to provide storage; a single machine running VMs under the XenServer or KVM hypervisor; and a shared public network."
+msgstr ""
+
+#: ../../ui.rst:109
+# 8a24a6a0c06f440087e093cad917bffb
+msgid "The prompts in this guided tour should give you all the information you need, but if you want just a bit more detail, you can follow along in the Trial Installation Guide."
+msgstr ""
+
+#: ../../ui.rst:113
+# 81d70c27e4d842afbbdc4f74e0c19acb
+msgid "**I have used CloudStack before.** Choose this if you have already gone through a design phase and planned a more sophisticated deployment, or you are ready to start scaling up a trial cloud that you set up earlier with the basic setup screens. In the Administrator UI, you can start using the more powerful features of CloudStack, such as advanced VLAN networking, high availability, additional network elements such as load balancers and firewalls, and support for multiple hypervisors including Citrix XenServer, KVM, and VMware vSphere."
+msgstr ""
+
+#: ../../ui.rst:123
+# 031ecbafb6b14054869c6a4202b5c1fd
+msgid "The root administrator Dashboard appears."
+msgstr ""
+
+#: ../../ui.rst:125
+# 7d9e4e036dec429db9386110482d17fa
+msgid "You should set a new root administrator password. If you chose basic setup, you’ll be prompted to create a new password right away. If you chose experienced user, use the steps in :ref:`changing-root-password`."
+msgstr ""
+
+#: ../../ui.rst:130
+# 812d903dc8bc4cf5a98f694baeb328a0
+msgid "You are logging in as the root administrator. This account manages the CloudStack deployment, including physical infrastructure. The root administrator can modify configuration settings to change basic functionality, create or delete user accounts, and take many actions that should be performed only by an authorized person. Please change the default password to a new, unique password."
+msgstr ""
+
+#: ../../ui.rst:140
+# b350994b6904403db6d30d524f0eed32
+msgid "Changing the Root Password"
+msgstr ""
+
+#: ../../ui.rst:142
+# 3a06c8a9892b4cbeaac7e2dec367ddd7
+msgid "During installation and ongoing cloud administration, you will need to log in to the UI as the root administrator. The root administrator account manages the CloudStack deployment, including physical infrastructure. The root administrator can modify configuration settings to change basic functionality, create or delete user accounts, and take many actions that should be performed only by an authorized person. When first installing CloudStack, be sure to change the default password to a new, unique value."
+msgstr ""
+
+#: ../../ui.rst:158
+# 7057f98c0cb94bceb1dc66c14a0b5802
+msgid "Log in to the UI using the current root user ID and password. The default is admin, password."
+msgstr ""
+
+#: ../../ui.rst:161
+# fdf104279af341739d24347f0e1fce4e
+msgid "Click Accounts."
+msgstr ""
+
+#: ../../ui.rst:163
+# c12c934bf488453e9c209dcf140e5b22
+msgid "Click the admin account name."
+msgstr ""
+
+#: ../../ui.rst:165
+# 9941a672247948c09ee39a2119dcbb22
+msgid "Click View Users."
+msgstr ""
+
+#: ../../ui.rst:167
+# 482e7c8a3e904702a4089d4643cdae41
+msgid "Click the admin user name."
+msgstr ""
+
+#: ../../ui.rst:169
+# ae46b97a741b49e4b1c2422f074135e9
+msgid "Click the Change Password button. |change-password.png|"
+msgstr ""
+
+#: ../../ui.rst:171
+# 9ba47399deaa4e378669ad789c0a47c0
+msgid "Type the new password, and click OK."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/usage.pot b/source/adminguide/locale/pot/usage.pot
new file mode 100644
index 0000000..b8b14ac
--- /dev/null
+++ b/source/adminguide/locale/pot/usage.pot
@@ -0,0 +1,1497 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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"
+
+#: ../../usage.rst:18
+# f960d1bdf1ff4edcab85c8de14d937d9
+msgid "Working with Usage"
+msgstr ""
+
+#: ../../usage.rst:20
+# 15ed9c55a30744308390d710f71e001e
+msgid "The Usage Server is an optional, separately-installed part of CloudStack that provides aggregated usage records which you can use to create billing integration for CloudStack. The Usage Server works by taking data from the events log and creating summary usage records that you can access using the listUsageRecords API call."
+msgstr ""
+
+#: ../../usage.rst:26
+# 96a54f49657f4ecb814c7babc3d12cd5
+msgid "The usage records show the amount of resources, such as VM run time or template storage space, consumed by guest instances."
+msgstr ""
+
+#: ../../usage.rst:29
+# 55c9c7dee78b4ff284f8a3775ee15d80
+msgid "The Usage Server runs at least once per day. It can be configured to run multiple times per day."
+msgstr ""
+
+#: ../../usage.rst:34
+# e3e786135adc456da195d8c62094e4cf
+msgid "Configuring the Usage Server"
+msgstr ""
+
+#: ../../usage.rst:36
+# 6fb60ef9e16e4db0878d21a3d8ae162b
+msgid "To configure the usage server:"
+msgstr ""
+
+#: ../../usage.rst:38
+# 5adc62eff1f640a094ea087767a99266
+msgid "Be sure the Usage Server has been installed. This requires extra steps beyond just installing the CloudStack software. See Installing the Usage Server (Optional) in the Advanced Installation Guide."
+msgstr ""
+
+#: ../../usage.rst:42
+# 79b6062dbd284c60a7d174315e5ddf4f
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../usage.rst:44
+# 19a9f5fbef3041d9b13807ca7c2cb8b9
+msgid "Click Global Settings."
+msgstr ""
+
+#: ../../usage.rst:46
+# 667e5b8b21924fb69b4fa8afbf76896b
+msgid "In Search, type usage. Find the configuration parameter that controls the behavior you want to set. See the table below for a description of the available parameters."
+msgstr ""
+
+#: ../../usage.rst:50
+# 8fa5855d775b43958fe08525d0e94aae
+msgid "In Actions, click the Edit icon."
+msgstr ""
+
+#: ../../usage.rst:52
+# 63178267fdd94998ab92da5146692648
+msgid "Type the desired value and click the Save icon."
+msgstr ""
+
+#: ../../usage.rst:54
+# 5d851f4543c0408f8e57dce0857766a3
+msgid "Restart the Management Server (as usual with any global configuration change) and also the Usage Server:"
+msgstr ""
+
+#: ../../usage.rst:62
+# b91f29141e0f4cdaaa81be318e86c10e
+msgid "The following table shows the global configuration settings that control the behavior of the Usage Server."
+msgstr ""
+
+#: ../../usage.rst:65
+# 1e76426d14bf4fc6915a0e1c79ef2b9a
+msgid "Parameter Name Description"
+msgstr ""
+
+#: ../../usage.rst:67
+# 668e6317ce104d72ab45c55b9411ea8e
+msgid "enable.usage.server Whether the Usage Server is active."
+msgstr ""
+
+#: ../../usage.rst:69
+# 1fcaf07a4ddb4e8c958cd1b6ef8cfe91
+msgid "usage.aggregation.timezone"
+msgstr ""
+
+#: ../../usage.rst:71
+# fb381c2892df4ea7b1c44440f03ba556
+msgid "Time zone of usage records. Set this if the usage records and daily job execution are in different time zones. For example, with the following settings, the usage job will run at PST 00:15 and generate usage records for the 24 hours from 00:00:00 GMT to 23:59:59 GMT:"
+msgstr ""
+
+#: ../../usage.rst:82
+# 509f3bce303a4ab7a526dcc19e3c3e50
+msgid "Valid values for the time zone are specified in `Appendix A, *Time Zones* <http://docs.cloudstack.apache.org/en/latest/dev.html?highlight=time%20zones#time-zones>`_"
+msgstr ""
+
+#: ../../usage.rst:85
+# 3133231b20dd4c9da1fe9fd7d09136a3
+msgid "Default: GMT"
+msgstr ""
+
+#: ../../usage.rst:87
+# 22dabfab93eb4361b26eb9088cad5134
+msgid "usage.execution.timezone"
+msgstr ""
+
+#: ../../usage.rst:89
+# a27f0dcfc71847ee846e80cb1b5c6e66
+msgid "The time zone of usage.stats.job.exec.time. Valid values for the time zone are specified in `Appendix A, *Time Zones* <http://docs.cloudstack.apache.org/en/latest/dev.html?highlight=time%20zones#time-zones>`_"
+msgstr ""
+
+#: ../../usage.rst:93
+# 101b64630291428aa4dce0f295b51f96
+msgid "Default: The time zone of the management server."
+msgstr ""
+
+#: ../../usage.rst:95
+# e5296f4116c949e282dda12b62a2e31b
+msgid "usage.sanity.check.interval"
+msgstr ""
+
+#: ../../usage.rst:97
+# 12e3d1486808475ba2d50b4b1f480b20
+msgid "The number of days between sanity checks. Set this in order to periodically search for records with erroneous data before issuing customer invoices. For example, this checks for VM usage records created after the VM was destroyed, and similar checks for templates, volumes, and so on. It also checks for usage times longer than the aggregation range. If any issue is found, the alert ALERT\\_TYPE\\_USAGE\\_SANITY\\_RESULT = 21 is sent."
+msgstr ""
+
+#: ../../usage.rst:105
+# d6a51defdc9b4ca1900dca6ee38d488b
+msgid "usage.stats.job.aggregation.range"
+msgstr ""
+
+#: ../../usage.rst:107
+# f200ecf1491a41c58c58d607a2030621
+msgid "The time period in minutes between Usage Server processing jobs. For example, if you set it to 1440, the Usage Server will run once per day. If you set it to 600, it will run every ten hours. In general, when a Usage Server job runs, it processes all events generated since usage was last run."
+msgstr ""
+
+#: ../../usage.rst:113
+# 3fb2ba9c61a64f54bb226a97eff0e59f
+msgid "There is special handling for the case of 1440 (once per day). In this case the Usage Server does not necessarily process all records since Usage was last run. CloudStack assumes that you require processing once per day for the previous, complete day’s records. For example, if the current day is October 7, then it is assumed you would like to process records for October 6, from midnight to midnight. CloudStack assumes this “midnight to midnight” is relative to the usage.execution.timezone."
+msgstr ""
+
+#: ../../usage.rst:121
+# 657e01fff8404e7086e1a5cd318ed5b9
+msgid "Default: 1440"
+msgstr ""
+
+#: ../../usage.rst:123
+# 8e231a3dfe9b4ac494f5ae8dc3e03001
+msgid "usage.stats.job.exec.time"
+msgstr ""
+
+#: ../../usage.rst:125
+# 05f6de4a7dd947ceba3246443c6e2ace
+msgid "The time when the Usage Server processing will start. It is specified in 24-hour format (HH:MM) in the time zone of the server, which should be GMT. For example, to start the Usage job at 10:30 GMT, enter “10:30”."
+msgstr ""
+
+#: ../../usage.rst:129
+# 54677f1477574ba58b744ade5f531ddd
+msgid "If usage.stats.job.aggregation.range is also set, and its value is not 1440, then its value will be added to usage.stats.job.exec.time to get the time to run the Usage Server job again. This is repeated until 24 hours have elapsed, and the next day's processing begins again at usage.stats.job.exec.time."
+msgstr ""
+
+#: ../../usage.rst:135
+# 870bef8e0dc54e1a87ab39acc1c59e7b
+msgid "Default: 00:15."
+msgstr ""
+
+#: ../../usage.rst:137
+# 3c30b2b9e20f485c8ac878c1c8b62ef5
+msgid "For example, suppose that your server is in GMT, your user population is predominantly in the East Coast of the United States, and you would like to process usage records every night at 2 AM local (EST) time. Choose these settings:"
+msgstr ""
+
+#: ../../usage.rst:142
+# 910e4a77b6c34e64ad844e417ab623d5
+msgid "enable.usage.server = true"
+msgstr ""
+
+#: ../../usage.rst:144
+# 078da3cc8569439c9002cbbb7337d936
+msgid "usage.execution.timezone = America/New\\_York"
+msgstr ""
+
+#: ../../usage.rst:146
+# 42e66162ae97481083688b89c626c8cc
+msgid "usage.stats.job.exec.time = 07:00. This will run the Usage job at 2:00 AM EST. Note that this will shift by an hour as the East Coast of the U.S. enters and exits Daylight Savings Time."
+msgstr ""
+
+#: ../../usage.rst:150
+# 5ba2fd5fa7004081a393783418655cdd
+msgid "usage.stats.job.aggregation.range = 1440"
+msgstr ""
+
+#: ../../usage.rst:152
+# 1c9ce06adfa54705878ac2e20fcc8462
+msgid "With this configuration, the Usage job will run every night at 2 AM EST and will process records for the previous day’s midnight-midnight as defined by the EST (America/New\\_York) time zone."
+msgstr ""
+
+#: ../../usage.rst:157
+# 1e914c7e818e47d8b13676d7f92bbe0b
+msgid "Because the special value 1440 has been used for usage.stats.job.aggregation.range, the Usage Server will ignore the data between midnight and 2 AM. That data will be included in the next day's run."
+msgstr ""
+
+#: ../../usage.rst:164
+# 40d99d806e4949158aa5ab2e841cfa2a
+msgid "Setting Usage Limits"
+msgstr ""
+
+#: ../../usage.rst:166
+# 579aaca84d1548508b091885f6e9e9da
+msgid "CloudStack provides several administrator control points for capping resource usage by users. Some of these limits are global configuration parameters. Others are applied at the ROOT domain and may be overridden on a per-account basis."
+msgstr ""
+
+#: ../../usage.rst:173
+# 229ad89efb9c4cb0ab03a6ce99f44f23
+msgid "Globally Configured Limits"
+msgstr ""
+
+#: ../../usage.rst:175
+# e2b6313d1a4d4917a2544b4440379415
+msgid "In a zone, the guest virtual network has a 24 bit CIDR by default. This limits the guest virtual network to 254 running instances. It can be adjusted as needed, but this must be done before any instances are created in the zone. For example, 10.1.1.0/22 would provide for ~1000 addresses."
+msgstr ""
+
+#: ../../usage.rst:181
+# 84670b12426b4429831f536c401fc323
+msgid "The following table lists limits set in the Global Configuration:"
+msgstr ""
+
+#: ../../usage.rst:184
+#: ../../usage.rst:239
+#: ../../usage.rst:343
+#: ../../usage.rst:414
+# 7da9c9f6c4464762b975b5c84e4ebf9c
+# 146d490544914790b152209b009cacb9
+# 1bb822fa0c3e4b7db77988b5cf5efdbd
+# c79e2332c1ba4ad5883126f553ad5388
+msgid "Parameter Name"
+msgstr ""
+
+#: ../../usage.rst:184
+# 69e6a02d3513471b89dca9419976e56b
+msgid "Definition"
+msgstr ""
+
+#: ../../usage.rst:186
+# 8f803160c7ef4b258545cf19783a2cb2
+msgid "max.account.public.ips"
+msgstr ""
+
+#: ../../usage.rst:186
+# 33a9e7f75edb450eb385f759769e8a27
+msgid "Number of public IP addresses that can be owned by an account"
+msgstr ""
+
+#: ../../usage.rst:188
+# 9d54d7043dfa4cfdba9892d7b4987d27
+msgid "max.account.snapshots"
+msgstr ""
+
+#: ../../usage.rst:188
+# 53e9c6336fc343f58d5d0f0c982ecd16
+msgid "Number of snapshots that can exist for an account"
+msgstr ""
+
+#: ../../usage.rst:190
+# 6979458b8f824d9ea8eb1a932cb3700a
+msgid "max.account.templates"
+msgstr ""
+
+#: ../../usage.rst:190
+# a450954b78c549129d90f452f3261c83
+msgid "Number of templates that can exist for an account"
+msgstr ""
+
+#: ../../usage.rst:192
+# e090c2956d874c139e10f94be47e21bd
+msgid "max.account.user.vms"
+msgstr ""
+
+#: ../../usage.rst:192
+# d30280c4822b48cf86341f0c6f0e9f40
+msgid "Number of virtual machine instances that can exist for an account"
+msgstr ""
+
+#: ../../usage.rst:194
+# ecaf59ece9264e429a9664b72c83c9d5
+msgid "max.account.volumes"
+msgstr ""
+
+#: ../../usage.rst:194
+# 352d53dede964c53adaba408485377bb
+msgid "Number of disk volumes that can exist for an account"
+msgstr ""
+
+#: ../../usage.rst:196
+# 4855308d9e7f453ca68c4f73a23b7da2
+msgid "max.template.iso.size"
+msgstr ""
+
+#: ../../usage.rst:196
+# c3cf19fabb7b41c6bfeda6bfcb0d40c6
+msgid "Maximum size for a downloaded template or ISO in GB"
+msgstr ""
+
+#: ../../usage.rst:198
+# e2bd816e02a74341ac3b504ef37abf9b
+msgid "max.volume.size.gb"
+msgstr ""
+
+#: ../../usage.rst:198
+# ac589029cbaa451fb486f219b27caf43
+msgid "Maximum size for a volume in GB"
+msgstr ""
+
+#: ../../usage.rst:200
+# 3b152b7effc14a2098e6b2f885125e11
+msgid "network.throttling.rate"
+msgstr ""
+
+#: ../../usage.rst:200
+# d66b6e2b68304b4d97dae0d72709be2f
+msgid "Default data transfer rate in megabits per second allowed per user (supported on XenServer)"
+msgstr ""
+
+#: ../../usage.rst:202
+# e01d028d0d5643a3a283f12888581998
+msgid "snapshot.max.hourly"
+msgstr ""
+
+#: ../../usage.rst:202
+# 305a224a1c5946ab949570233597705b
+msgid "Maximum recurring hourly snapshots to be retained for a volume. If the limit is reached, early snapshots from the start of the hour are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring hourly snapshots can not be scheduled"
+msgstr ""
+
+#: ../../usage.rst:204
+# 7734cc014872464a8d8672c1190ff731
+msgid "snapshot.max.daily"
+msgstr ""
+
+#: ../../usage.rst:204
+# ddca821bebdf4a12a2b4fb3d9e089efe
+msgid "Maximum recurring daily snapshots to be retained for a volume. If the limit is reached, snapshots from the start of the day are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring daily snapshots can not be scheduled"
+msgstr ""
+
+#: ../../usage.rst:206
+# 90b70954860841d5a31b17b85cc10f84
+msgid "snapshot.max.weekly"
+msgstr ""
+
+#: ../../usage.rst:206
+# 8ee51877c42a40da9039bdc877f388c5
+msgid "Maximum recurring weekly snapshots to be retained for a volume. If the limit is reached, snapshots from the beginning of the week are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring weekly snapshots can not be scheduled"
+msgstr ""
+
+#: ../../usage.rst:208
+# 65aa1a30aab34f218756e423bac8f482
+msgid "snapshot.max.monthly"
+msgstr ""
+
+#: ../../usage.rst:208
+# 631eba2a40fe48f3b4f179dfe6e9fdc7
+msgid "Maximum recurring monthly snapshots to be retained for a volume. If the limit is reached, snapshots from the beginning of the month are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring monthly snapshots can not be scheduled."
+msgstr ""
+
+#: ../../usage.rst:211
+# dce0ccf760cb481290483d2e6c7439e4
+msgid "To modify global configuration parameters, use the global configuration screen in the CloudStack UI. See Setting Global Configuration Parameters"
+msgstr ""
+
+#: ../../usage.rst:216
+# adacfb1bcc74482cbac23e9a14c1803c
+msgid "Limiting Resource Usage"
+msgstr ""
+
+#: ../../usage.rst:218
+# 354d5dde0afe47a982710d8800da3315
+msgid "CloudStack allows you to control resource usage based on the types of resources, such as CPU, RAM, Primary storage, and Secondary storage. A new set of resource types has been added to the existing pool of resources to support the new customization model—need-basis usage, such as large VM or small VM. The new resource types are now broadly classified as CPU, RAM, Primary storage, and Secondary storage. The root administrator is able to impose resource usage limit by the following resource types for Domain, Project, and Accounts."
+msgstr ""
+
+#: ../../usage.rst:227
+# b80deb66aa1244279f48b9e17db7f7a0
+msgid "CPUs"
+msgstr ""
+
+#: ../../usage.rst:229
+# a7c54e874cae4016b7a1d2a17c5a7a89
+msgid "Memory (RAM)"
+msgstr ""
+
+#: ../../usage.rst:231
+# 3db51597d1dd4f328899070b88325384
+msgid "Primary Storage (Volumes)"
+msgstr ""
+
+#: ../../usage.rst:233
+# 6de9a84059e7408e85e9fdb47dbb341d
+msgid "Secondary Storage (Snapshots, Templates, ISOs)"
+msgstr ""
+
+#: ../../usage.rst:235
+# 36f9c552269b44e49eb2f86fa2bd98c8
+msgid "To control the behaviour of this feature, the following configuration parameters have been added:"
+msgstr ""
+
+#: ../../usage.rst:239
+#: ../../usage.rst:345
+#: ../../usage.rst:416
+#: ../../usage.rst:750
+# fc46eaac2efd4bf289bbd9025fd78502
+# 160c8719552a4684880d4f4a8ada714c
+# 947dba25316d4d74959935b65c8c5a33
+# 161ab30e9a60413d90729511c5fe9ec1
+msgid "Description"
+msgstr ""
+
+#: ../../usage.rst:241
+# 23d6c966c2c94a1f986282a729352f38
+msgid "max.account.cpus"
+msgstr ""
+
+#: ../../usage.rst:241
+#: ../../usage.rst:249
+# cdd19d9379ec43648cd224ba64a960dd
+# 2ca1b2c4fdc44e0e940da7f75cb5788b
+msgid "Maximum number of CPU cores that can be used for an account. Default is 40."
+msgstr ""
+
+#: ../../usage.rst:243
+# 4979d3f2676e4809a49cc696c48d2f8d
+msgid "max.account.ram (MB)"
+msgstr ""
+
+#: ../../usage.rst:243
+#: ../../usage.rst:251
+# f3c0b37fc2ea4617b811cef9791eda3b
+# 00fb0cdbac5b4ad291bc50a5e1219a47
+msgid "Maximum RAM that can be used for an account. Default is 40960."
+msgstr ""
+
+#: ../../usage.rst:245
+# 45df7928f7174808a2083dd11add33c0
+msgid "max.account.primary.storage (GB)"
+msgstr ""
+
+#: ../../usage.rst:245
+#: ../../usage.rst:253
+# 1ee6c5009abd4668a5dd0a640a18c8ea
+# 254b02916fc34ad6a649c8c990d4f41a
+msgid "Maximum primary storage space that can be used for an account. Default is 200."
+msgstr ""
+
+#: ../../usage.rst:247
+# cdeb23ce821d4c3196c6ea784f4367b6
+msgid "max.account.secondary.storage (GB)"
+msgstr ""
+
+#: ../../usage.rst:247
+#: ../../usage.rst:255
+# c51c46bd539f4093a4393f2d6d4e9b79
+# 982aa6e78c6f4ecda0f24acd5f6564d3
+msgid "Maximum secondary storage space that can be used for an account. Default is 400."
+msgstr ""
+
+#: ../../usage.rst:249
+# 01081c6a660a44f5851d914915a1281b
+msgid "max.project.cpus"
+msgstr ""
+
+#: ../../usage.rst:251
+# b7aede866d8a41298cf2c284450aea39
+msgid "max.project.ram (MB)"
+msgstr ""
+
+#: ../../usage.rst:253
+# 6a66f463c8a14145b745751a99ff5412
+msgid "max.project.primary.storage (GB)"
+msgstr ""
+
+#: ../../usage.rst:255
+# 86d804726f994f5ea14d1a29e97eb968
+msgid "max.project.secondary.storage (GB)"
+msgstr ""
+
+#: ../../usage.rst:261
+# 8ea9def42949482d99838f5ebe00a5e2
+msgid "User Permission"
+msgstr ""
+
+#: ../../usage.rst:263
+# 31b6a320c933489c96b4ce8db09ee012
+msgid "The root administrator, domain administrators and users are able to list resources. Ensure that proper logs are maintained in the ``vmops.log`` and ``api.log`` files."
+msgstr ""
+
+#: ../../usage.rst:267
+# 41b569e3765441d69d540fed030e34e2
+msgid "The root admin will have the privilege to list and update resource limits."
+msgstr ""
+
+#: ../../usage.rst:270
+# 9f791a84c2014d73b5f8b74f287ad010
+msgid "The domain administrators are allowed to list and change these resource limits only for the sub-domains and accounts under their own domain or the sub-domains."
+msgstr ""
+
+#: ../../usage.rst:274
+# df23a35291874e2d9f7af5d93db4dae4
+msgid "The end users will the privilege to list resource limits. Use the listResourceLimits API."
+msgstr ""
+
+#: ../../usage.rst:279
+# 474425750935446e84565dc2a2f561b6
+msgid "Limit Usage Considerations"
+msgstr ""
+
+#: ../../usage.rst:281
+# c96935ecfc1545448c6a31bf7e9bcefa
+msgid "Primary or Secondary storage space refers to the stated size of the volume and not the physical size— the actual consumed size on disk in case of thin provisioning."
+msgstr ""
+
+#: ../../usage.rst:285
+# 003d62e3a41b4ec0838c1ad1e22ab0c8
+msgid "If the admin reduces the resource limit for an account and set it to less than the resources that are currently being consumed, the existing VMs/templates/volumes are not destroyed. Limits are imposed only if the user under that account tries to execute a new operation using any of these resources. For example, the existing behavior in the case of a VM are:"
+msgstr ""
+
+#: ../../usage.rst:292
+# 61f14d0421dc4f27885ac8f93946dbe6
+msgid "migrateVirtualMachine: The users under that account will be able to migrate the running VM into any other host without facing any limit issue."
+msgstr ""
+
+#: ../../usage.rst:296
+# 287edb83794948b4b1509e7c1ed82b17
+msgid "recoverVirtualMachine: Destroyed VMs cannot be recovered."
+msgstr ""
+
+#: ../../usage.rst:298
+# 2b57273cf486489e856ef1a97146d73a
+msgid "For any resource type, if a domain has limit X, sub-domains or accounts under that domain can have there own limits. However, the sum of resource allocated to a sub-domain or accounts under the domain at any point of time should not exceed the value X."
+msgstr ""
+
+#: ../../usage.rst:303
+# 9f35315b3f6b4560abe71837984f2ed7
+msgid "For example, if a domain has the CPU limit of 40 and the sub-domain D1 and account A1 can have limits of 30 each, but at any point of time the resource allocated to D1 and A1 should not exceed the limit of 40."
+msgstr ""
+
+#: ../../usage.rst:308
+# cfc912fe9e294238a5a41841f8636ecf
+msgid "If any operation needs to pass through two of more resource limit check, then the lower of 2 limits will be enforced, For example: if an account has the VM limit of 10 and CPU limit of 20, and a user under that account requests 5 VMs of 4 CPUs each. The user can deploy 5 more VMs because VM limit is 10. However, the user cannot deploy any more instances because the CPU limit has been exhausted."
+msgstr ""
+
+#: ../../usage.rst:317
+# fd7e43ba4fc2492cb1117d9f171cb475
+msgid "Limiting Resource Usage in a Domain"
+msgstr ""
+
+#: ../../usage.rst:319
+# d7bae8b0c64640aaab9b686ccb641ca1
+msgid "CloudStack allows the configuration of limits on a domain basis. With a domain limit in place, all users still have their account limits. They are additionally limited, as a group, to not exceed the resource limits set on their domain. Domain limits aggregate the usage of all accounts in the domain as well as all the accounts in all the sub-domains of that domain. Limits set at the root domain level apply to the sum of resource usage by the accounts in all the domains and sub-domains below that root domain."
+msgstr ""
+
+#: ../../usage.rst:328
+# 42cc77754b864082aff2b2d5e091fa0f
+msgid "To set a domain limit:"
+msgstr ""
+
+#: ../../usage.rst:330
+#: ../../usage.rst:401
+# bb5fc3b2710e4ea59810c1d28209dfc2
+# b83cbc0f83d7410e8b117351958fc591
+msgid "Log in to the CloudStack UI."
+msgstr ""
+
+#: ../../usage.rst:332
+# 530247f4ca1a4475ae86e656ceff6abb
+msgid "In the left navigation tree, click Domains."
+msgstr ""
+
+#: ../../usage.rst:334
+# a9bff41fd28c435cbb09170c5b103277
+msgid "Select the domain you want to modify. The current domain limits are displayed."
+msgstr ""
+
+#: ../../usage.rst:337
+#: ../../usage.rst:408
+# 519c174598aa4e55b86e899664c75018
+# 182d21886ebb4a09aebb0ef93e1fba63
+msgid "A value of -1 shows that there is no limit in place."
+msgstr ""
+
+#: ../../usage.rst:339
+# b83647ec9f344cccbf360b1f8b85c119
+msgid "Click the Edit button |editbutton.png|"
+msgstr ""
+
+#: ../../usage.rst:341
+#: ../../usage.rst:412
+# c209d72330bd40f887995563563a6337
+# 99aa0e22f71d481eb51b72047c456f3a
+msgid "Edit the following as per your requirement:"
+msgstr ""
+
+#: ../../usage.rst:347
+#: ../../usage.rst:418
+# cd271c3e43ea4c79a12f3f84924b6307
+# f889d8a628fd4b0ba7972855f0dbdc45
+msgid "Instance Limits"
+msgstr ""
+
+#: ../../usage.rst:349
+# 5ef71e88c22848aeb261dfceed3f0ad3
+msgid "The number of instances that can be used in a domain."
+msgstr ""
+
+#: ../../usage.rst:351
+#: ../../usage.rst:424
+# 8eb91b3c4b884b1886b84388b430c4b5
+# 50f79b10ffa84d4e8d63df31d54a18bc
+msgid "Public IP Limits"
+msgstr ""
+
+#: ../../usage.rst:353
+# 9c123828b8bd44759ea889e13f4ab4bb
+msgid "The number of public IP addresses that can be used in a domain."
+msgstr ""
+
+#: ../../usage.rst:355
+#: ../../usage.rst:430
+# 682adde29cb64e42b391dcb5e5cdc9ad
+# f9ffeebe6c1a4111ab27c1b8d080143f
+msgid "Volume Limits"
+msgstr ""
+
+#: ../../usage.rst:357
+# 57ca197f678f416c961a36d6a71f9bf5
+msgid "The number of disk volumes that can be created in a domain."
+msgstr ""
+
+#: ../../usage.rst:359
+#: ../../usage.rst:436
+# 014dffd5f65443088674d2ee9df38979
+# ae967a3a9a714ab2892d18c80a55f652
+msgid "Snapshot Limits"
+msgstr ""
+
+#: ../../usage.rst:361
+# 11f338d7f95041eaa7b84b9960a9f12f
+msgid "The number of snapshots that can be created in a domain."
+msgstr ""
+
+#: ../../usage.rst:363
+#: ../../usage.rst:442
+# 07a01397e2404e18a667da23df9e7bf3
+# 6ba3ca1a17df418cac4387d71ddd7656
+msgid "Template Limits"
+msgstr ""
+
+#: ../../usage.rst:365
+# 6dc70a7ce5ec48f3bcf254b4a20b4145
+msgid "The number of templates that can be registered in a domain."
+msgstr ""
+
+#: ../../usage.rst:367
+#: ../../usage.rst:448
+# 3bf5c725f231453cb6152f1bade12d17
+# 0b2a474b089d426d850f25818db1d152
+msgid "VPC limits"
+msgstr ""
+
+#: ../../usage.rst:369
+# 6041d380cc8b460e838d34d542c0fe6f
+msgid "The number of VPCs that can be created in a domain."
+msgstr ""
+
+#: ../../usage.rst:371
+#: ../../usage.rst:454
+# 6167d0a236e346cdac41980cca4b61a1
+# efac374c510144af805a206947596f0d
+msgid "CPU limits"
+msgstr ""
+
+#: ../../usage.rst:373
+# c3bb1f4173a04335bd9f9a2aa60ffb7f
+msgid "The number of CPU cores that can be used for a domain."
+msgstr ""
+
+#: ../../usage.rst:375
+#: ../../usage.rst:460
+# 5b77e8eb1eed4b89a6add832c6efa78d
+# 0f97c6c6f6bd48d49582e4a5773420a0
+msgid "Memory limits (MB)"
+msgstr ""
+
+#: ../../usage.rst:377
+# 46ff0275d44b492790fbf06cfcc202f9
+msgid "The number of RAM that can be used for a domain."
+msgstr ""
+
+#: ../../usage.rst:379
+#: ../../usage.rst:466
+# cfada3bdc3304c91b6093699cc7aba26
+# e09ca8ab179747818fc4be09918773c3
+msgid "Primary Storage limits (GB)"
+msgstr ""
+
+#: ../../usage.rst:381
+# fadd0e1341ce4a40a364f8e7e5cbd720
+msgid "The primary storage space that can be used for a domain."
+msgstr ""
+
+#: ../../usage.rst:383
+#: ../../usage.rst:472
+# 94e6ad3512c64a968eba503aae4228e9
+# 88b20b1a22f5450abfd0371827b8a662
+msgid "Secondary Storage limits (GB)"
+msgstr ""
+
+#: ../../usage.rst:385
+# af7bbd32f2d744bbb6bc8bc38f2a6fff
+msgid "The secondary storage space that can be used for a domain."
+msgstr ""
+
+#: ../../usage.rst:387
+#: ../../usage.rst:478
+# 9c4e390eeaf74125aff2fabb290d7508
+# 8554c878b3db4319b1e9ff271f3f2e16
+msgid "Click Apply."
+msgstr ""
+
+#: ../../usage.rst:391
+# 0aea17dfad1c43818257b74482bdc4ec
+msgid "Default Account Resource Limits"
+msgstr ""
+
+#: ../../usage.rst:393
+# 5aec04d06e414d8c85567ee7ad5fa5a2
+msgid "You can limit resource use by accounts. The default limits are set by using Global configuration parameters, and they affect all accounts within a cloud. The relevant parameters are those beginning with max.account, for example: max.account.snapshots."
+msgstr ""
+
+#: ../../usage.rst:398
+# 49c964b0ef8840ef953d87ef3115cf7f
+msgid "To override a default limit for a particular account, set a per-account resource limit."
+msgstr ""
+
+#: ../../usage.rst:403
+# 7954a55684b74afbb3e48736fb619dfe
+msgid "In the left navigation tree, click Accounts."
+msgstr ""
+
+#: ../../usage.rst:405
+# 30a0c7b93a044a24b1bbcab3362c9130
+msgid "Select the account you want to modify. The current limits are displayed."
+msgstr ""
+
+#: ../../usage.rst:410
+# 247dcfe79c914ac0a42c2bb5f617c3b2
+msgid "Click the Edit button. |editbutton.png|"
+msgstr ""
+
+#: ../../usage.rst:420
+# a5b53a96d84f4cb993b2539562072ba0
+msgid "The number of instances that can be used in an account."
+msgstr ""
+
+#: ../../usage.rst:422
+#: ../../usage.rst:428
+#: ../../usage.rst:434
+#: ../../usage.rst:440
+#: ../../usage.rst:446
+#: ../../usage.rst:452
+# 4f148fb22eeb4cd5867de40af5d6957d
+# f6aef839dc7e4814a93524ac42691632
+# c8a80cc9dabc47b7908b2be9906b47e6
+# b1fc64706b924e37bcdf44b959b1a10b
+# a4c96e4f6931454c803ad5d310dd832a
+# 37ebe0cf9b3644a59962fb5255cd1e7c
+msgid "The default is 20."
+msgstr ""
+
+#: ../../usage.rst:426
+# b71498e20d9c45f5b4e6246502846b7a
+msgid "The number of public IP addresses that can be used in an account."
+msgstr ""
+
+#: ../../usage.rst:432
+# a7a78f1d32244bd7ae3f36a8706565ec
+msgid "The number of disk volumes that can be created in an account."
+msgstr ""
+
+#: ../../usage.rst:438
+# f22d973606cc4fe68cdf2ef0d22fb7b9
+msgid "The number of snapshots that can be created in an account."
+msgstr ""
+
+#: ../../usage.rst:444
+# 78aa50a7ed74400c8d0a3bcc278ed06b
+msgid "The number of templates that can be registered in an account."
+msgstr ""
+
+#: ../../usage.rst:450
+# 17544e59335b42c2b1dcb5439be274a4
+msgid "The number of VPCs that can be created in an account."
+msgstr ""
+
+#: ../../usage.rst:456
+# dab1fd7da66d424fa313f0a8da2fd672
+msgid "The number of CPU cores that can be used for an account."
+msgstr ""
+
+#: ../../usage.rst:458
+# f8813118e7014ec4b09e2ce57e9826a0
+msgid "The default is 40."
+msgstr ""
+
+#: ../../usage.rst:462
+# 5ee54380b1c7418aa85f1b4aa3d18f5c
+msgid "The number of RAM that can be used for an account."
+msgstr ""
+
+#: ../../usage.rst:464
+# 463fe26a18c747bdba2e4c943174df89
+msgid "The default is 40960."
+msgstr ""
+
+#: ../../usage.rst:468
+# 483d95c867804bd7a67bd7c5db5d7250
+msgid "The primary storage space that can be used for an account."
+msgstr ""
+
+#: ../../usage.rst:470
+# b5792f85ad5748629247339cddc34442
+msgid "The default is 200."
+msgstr ""
+
+#: ../../usage.rst:474
+# cf2794b976cb4597a1c7c46023d92939
+msgid "The secondary storage space that can be used for an account."
+msgstr ""
+
+#: ../../usage.rst:476
+# e31012695d1342b893a7afc797d9efc8
+msgid "The default is 400."
+msgstr ""
+
+#: ../../usage.rst:482
+# 58fd1b50da564cbfbe626a0c715242a2
+msgid "Usage Record Format"
+msgstr ""
+
+#: ../../usage.rst:485
+# bd6e6ad5dd4441038efbfa8256d54fbb
+msgid "Virtual Machine Usage Record Format"
+msgstr ""
+
+#: ../../usage.rst:487
+# f4090312493645f999618d3518704fe4
+msgid "For running and allocated virtual machine usage, the following fields exist in a usage record:"
+msgstr ""
+
+#: ../../usage.rst:490
+#: ../../usage.rst:531
+#: ../../usage.rst:590
+#: ../../usage.rst:624
+#: ../../usage.rst:685
+#: ../../usage.rst:719
+# 1ea8ad4e82f849199566823e669d2e60
+# cb746968f7ea4c6eaeae3a8696c37487
+# 800271ae9863449db8b5d5a7a20f41be
+# 40d84f3b7c0243a2b680c8c5ee6fe699
+# b060e5d0dfc94db5a3dc884d3afc9829
+# 34a867e377074d8b8b7a9d16f17250f8
+msgid "account – name of the account"
+msgstr ""
+
+#: ../../usage.rst:492
+#: ../../usage.rst:533
+#: ../../usage.rst:592
+#: ../../usage.rst:626
+#: ../../usage.rst:687
+#: ../../usage.rst:721
+# 0c884e63b3b6479d8ee0a652be74d5d4
+# 374676d104da4bb795381a260c95ddf1
+# cdf46e85f5ce46b6b29adc8183f20bc5
+# 0afdb6434c584c61acb197cf1a10f04c
+# 871a1002f0e34f38a9d8b6511ac9c04e
+# e13b8b9c705048e583810469fcd0a485
+msgid "accountid – ID of the account"
+msgstr ""
+
+#: ../../usage.rst:494
+#: ../../usage.rst:535
+#: ../../usage.rst:594
+#: ../../usage.rst:628
+#: ../../usage.rst:689
+#: ../../usage.rst:723
+# 422137b0ab2b4696a321d367b6d26f6d
+# 86455aead7614969ab37a2e295a26530
+# 0c7934f2579a497cb68757e53895fe18
+# cd40f5f568ed41969adeb774e54813da
+# bdd3a9da32134e1e8ca88e1d720abcef
+# e797f39fdbc04ecbbbe2bdc559a0b118
+msgid "domainid – ID of the domain in which this account resides"
+msgstr ""
+
+#: ../../usage.rst:496
+#: ../../usage.rst:537
+#: ../../usage.rst:596
+#: ../../usage.rst:630
+#: ../../usage.rst:691
+#: ../../usage.rst:725
+# d938ef5bbcc140c3a43fe372485e16af
+# 0e8bcce04fb34321a8e64ed6f0511dc6
+# 989ad97f092f4ef38b22b0112e749925
+# a74af98e8b4f4970805d2c13cdf90c37
+# 07ebb7ef423743fa8f659f3ab930b615
+# 7f6481f066a049c68b8df922020b9f23
+msgid "zoneid – Zone where the usage occurred"
+msgstr ""
+
+#: ../../usage.rst:498
+#: ../../usage.rst:539
+#: ../../usage.rst:598
+#: ../../usage.rst:632
+#: ../../usage.rst:693
+#: ../../usage.rst:727
+# 603607ff4edb47e9a79f7310b5606576
+# 54a63f2835ce4ebcab6a5e8f61822468
+# 6c1cd88b31ef47699a96c86e2dc2fd57
+# a97e62aec444404ba90732a66e38ba16
+# 851e49d28b7748bc84040d925da26fc0
+# cdf33c6ee5c24ddd843c0c573f0236c9
+msgid "description – A string describing what the usage record is tracking"
+msgstr ""
+
+#: ../../usage.rst:500
+# 18c681fd6a6d4db7ac9c8d0c14546df8
+msgid "usage – String representation of the usage, including the units of usage (e.g. 'Hrs' for VM running time)"
+msgstr ""
+
+#: ../../usage.rst:503
+#: ../../usage.rst:541
+#: ../../usage.rst:603
+#: ../../usage.rst:637
+#: ../../usage.rst:698
+#: ../../usage.rst:704
+#: ../../usage.rst:732
+#: ../../usage.rst:738
+# b56f48c2ce7e4ef8a421781cd8ac72d9
+# 367c8fbc6c3040e1b454649a311e5f24
+# 7a9a014a24af4f13afdf4091e920b2c7
+# 5ea8dfa3838546fea2bc64e05c8c673a
+# 3d7a93e77f944490999348ecfa138347
+# 65753a35c9384d9488a6ba39494069d9
+# 72b65cd48a914780a818c78d2b39df45
+# defb130ed24d43fcbdd05f28d6551b33
+msgid "usagetype – A number representing the usage type (see Usage Types)"
+msgstr ""
+
+#: ../../usage.rst:505
+#: ../../usage.rst:543
+#: ../../usage.rst:605
+#: ../../usage.rst:639
+#: ../../usage.rst:700
+#: ../../usage.rst:734
+# dead7906f5ff49c88d8e41f0a3140bd3
+# 8ee236cbfec44c23a571ce1209509110
+# 51b806027dda42548e0b46c7e5f0c468
+# 2b60dfbda65048239a38cba051b05cd8
+# da840cc63b26444a8154da21e65d5f6b
+# 0f380999106d476eae77a3f78ab9bd69
+msgid "rawusage – A number representing the actual usage in hours"
+msgstr ""
+
+#: ../../usage.rst:507
+#: ../../usage.rst:708
+#: ../../usage.rst:710
+# e398aeba3cd0401992be1f2f12e5fc91
+# e9e71b3111f84185baca323877a352fd
+# 28490f43f8cd44f4bf26a2abb77429ed
+msgid "virtualMachineId – The ID of the virtual machine"
+msgstr ""
+
+#: ../../usage.rst:509
+# adce21eabe0243be8c394e06dd5f7790
+msgid "name – The name of the virtual machine"
+msgstr ""
+
+#: ../../usage.rst:511
+# 6b520c414595424cad27b0ae57527c1f
+msgid "offeringid – The ID of the service offering"
+msgstr ""
+
+#: ../../usage.rst:513
+# 9329a1f52e57454a9b515f46ce1e110c
+msgid "templateid – The ID of the template or the ID of the parent template. The parent template value is present when the current template was created from a volume."
+msgstr ""
+
+#: ../../usage.rst:517
+# d061eac093024ebb867ea323cb34bbc0
+msgid "usageid – Virtual machine"
+msgstr ""
+
+#: ../../usage.rst:519
+#: ../../usage.rst:611
+# 047ce224b91448ba964e79cc572efd1e
+# db530f7238e94cb295d4cf30edceb4bc
+msgid "type – Hypervisor"
+msgstr ""
+
+#: ../../usage.rst:521
+#: ../../usage.rst:549
+#: ../../usage.rst:617
+#: ../../usage.rst:650
+#: ../../usage.rst:712
+#: ../../usage.rst:740
+# 13784faf965d4cae937aa6cdbbb601b3
+# f723716e1445424cbc729bcae6910bae
+# 193cb9ce321c4844bfc67c7421b46b78
+# 3362120577564331af89079c96e60819
+# 48e9160ce71b475d961c452d6984a6fc
+# ed62c302bb274df094275fbf56674a91
+msgid "startdate, enddate – The range of time for which the usage is aggregated; see Dates in the Usage Record"
+msgstr ""
+
+#: ../../usage.rst:526
+# eedaa3906dfd445e8bccefccc0c58cf6
+msgid "Network Usage Record Format"
+msgstr ""
+
+#: ../../usage.rst:528
+# a62195cc17e14143a58822cf0c485c0e
+msgid "For network usage (bytes sent/received), the following fields exist in a usage record."
+msgstr ""
+
+#: ../../usage.rst:545
+# e2aa41ae9fda438280903d7de43e9fa7
+msgid "usageid – Device ID (virtual router ID or external device ID)"
+msgstr ""
+
+#: ../../usage.rst:547
+# cba1335aecd94359b17f04495d757350
+msgid "type – Device type (domain router, external load balancer, etc.)"
+msgstr ""
+
+#: ../../usage.rst:554
+# f60aa591df79401691c6f36e9a9372cd
+msgid "IP Address Usage Record Format"
+msgstr ""
+
+#: ../../usage.rst:556
+# 8c83a518ebf94bda95be14bed415fbdd
+msgid "For IP address usage the following fields exist in a usage record."
+msgstr ""
+
+#: ../../usage.rst:558
+#: ../../usage.rst:657
+# 872facde9d324938a2dc358b6f91d3d6
+# a38435a4207846d386ed6690dbeb757c
+msgid "account - name of the account"
+msgstr ""
+
+#: ../../usage.rst:560
+#: ../../usage.rst:659
+# c2361416c29c4fbd838cca88df7fce39
+# bc06c74f16144181bca49330654a8470
+msgid "accountid - ID of the account"
+msgstr ""
+
+#: ../../usage.rst:562
+#: ../../usage.rst:661
+# 7ad667e8f90242c5b4cacb1421dc53a2
+# e6e2d964ef1a4c8b94bc42f08beea530
+msgid "domainid - ID of the domain in which this account resides"
+msgstr ""
+
+#: ../../usage.rst:564
+#: ../../usage.rst:663
+# c05809fe04764a479c42fe337b8f32a7
+# 051704b34aa84fecb879697aa4461b9c
+msgid "zoneid - Zone where the usage occurred"
+msgstr ""
+
+#: ../../usage.rst:566
+#: ../../usage.rst:665
+# ef2388373bf042c79862477f5068f84f
+# ac7162ddbf9b4f07a70378f7cb4f1376
+msgid "description - A string describing what the usage record is tracking"
+msgstr ""
+
+#: ../../usage.rst:568
+# 680a2939f1ab4cd0b4c7d7ba19346be0
+msgid "usage - String representation of the usage, including the units of usage"
+msgstr ""
+
+#: ../../usage.rst:571
+#: ../../usage.rst:670
+#: ../../usage.rst:676
+# 552772e8c5f745518dc6484ef776e37b
+# 8b658740424143e0804a450732cc90d5
+# 79adc7a2a02248f8a0ee7771272a5624
+msgid "usagetype - A number representing the usage type (see Usage Types)"
+msgstr ""
+
+#: ../../usage.rst:573
+#: ../../usage.rst:672
+# 565c646fcbed4427bf835e888529e76c
+# af9345ffb0554f0eb0ad166c00406ea8
+msgid "rawusage - A number representing the actual usage in hours"
+msgstr ""
+
+#: ../../usage.rst:575
+# 1ce3b40124484eefb27601e1907f939a
+msgid "usageid - IP address ID"
+msgstr ""
+
+#: ../../usage.rst:577
+#: ../../usage.rst:678
+# abfd139b052e4864afc695aba432783c
+# a5cbc24cefb54a2996cf860cf2b1e75c
+msgid "startdate, enddate - The range of time for which the usage is aggregated; see Dates in the Usage Record"
+msgstr ""
+
+#: ../../usage.rst:580
+# 7631780188e9474f8a1041b55d0ac20b
+msgid "issourcenat - Whether source NAT is enabled for the IP address"
+msgstr ""
+
+#: ../../usage.rst:582
+# 85f7d46f4fd5425cad1b87a37ec9ecf7
+msgid "iselastic - True if the IP address is elastic."
+msgstr ""
+
+#: ../../usage.rst:586
+# fd56a0a694804aa884be5fdefcfd3320
+msgid "Disk Volume Usage Record Format"
+msgstr ""
+
+#: ../../usage.rst:588
+# dc66789696474008bbbc81eb24bec679
+msgid "For disk volumes, the following fields exist in a usage record."
+msgstr ""
+
+#: ../../usage.rst:600
+#: ../../usage.rst:634
+#: ../../usage.rst:695
+#: ../../usage.rst:729
+# 4a12e3d8b23f40078657c836a946af1e
+# d33548fd1fe240509c2c86f75c6bd701
+# 38cb41b0bdc94d2e94ee5c3a6492e281
+# 95202bd84a0e4a61991829c07c2c0720
+msgid "usage – String representation of the usage, including the units of usage (e.g. 'Hrs' for hours)"
+msgstr ""
+
+#: ../../usage.rst:607
+# c2f1554e72084e81892a0b538a19c7f8
+msgid "usageid – The volume ID"
+msgstr ""
+
+#: ../../usage.rst:609
+#: ../../usage.rst:643
+# b7525535c67b49b98b4d922f07293bcb
+# c781024621454a418e050f006e91921c
+msgid "offeringid – The ID of the disk offering"
+msgstr ""
+
+#: ../../usage.rst:613
+# 543db09e00804cd787e00be0867a5c6e
+msgid "templateid – ROOT template ID"
+msgstr ""
+
+#: ../../usage.rst:615
+# f2ab3e39617449bf8a68f1fbc0eb4fbe
+msgid "size – The amount of storage allocated"
+msgstr ""
+
+#: ../../usage.rst:622
+# e54797d2c60c4441ac584d3abb0f9c77
+msgid "Template, ISO, and Snapshot Usage Record Format"
+msgstr ""
+
+#: ../../usage.rst:641
+# 60eda22a3c7d4756847f64ff53b961e2
+msgid "usageid – The ID of the the template, ISO, or snapshot"
+msgstr ""
+
+#: ../../usage.rst:645
+# 3562063eefc04af28187703974e45228
+msgid "templateid – – Included only for templates (usage type 7). Source template ID."
+msgstr ""
+
+#: ../../usage.rst:648
+# 9fbfbc974f184b2983595a2d4fed5cdb
+msgid "size – Size of the template, ISO, or snapshot"
+msgstr ""
+
+#: ../../usage.rst:655
+# aa26900876304f758262788c79483c44
+msgid "Load Balancer Policy or Port Forwarding Rule Usage Record Format"
+msgstr ""
+
+#: ../../usage.rst:667
+# f493ad9446bd4b0d84e50c9937d2b21c
+msgid "usage - String representation of the usage, including the units of usage (e.g. 'Hrs' for hours)"
+msgstr ""
+
+#: ../../usage.rst:674
+# 03d262a193f246749d1ed6f6df6d3930
+msgid "usageid - ID of the load balancer policy or port forwarding rule"
+msgstr ""
+
+#: ../../usage.rst:683
+# b01513d3fd8e466ba943f21dd926c03a
+msgid "Network Offering Usage Record Format"
+msgstr ""
+
+#: ../../usage.rst:702
+# d5c5360548e6437882e13f383f854c51
+msgid "usageid – ID of the network offering"
+msgstr ""
+
+#: ../../usage.rst:706
+# 1dd0260b113b4149979baeec2b430e69
+msgid "offeringid – Network offering ID"
+msgstr ""
+
+#: ../../usage.rst:717
+# 2e3b410e70064b95997310d4b2f2d6bb
+msgid "VPN User Usage Record Format"
+msgstr ""
+
+#: ../../usage.rst:736
+# 78984789b8f74fcb9ae0dc8712b092fa
+msgid "usageid – VPN user ID"
+msgstr ""
+
+#: ../../usage.rst:745
+# 371ab2afddac4c8ebe7b59df3a7e3150
+msgid "Usage Types"
+msgstr ""
+
+#: ../../usage.rst:747
+# bb807347fed448728c3e17662b8b1ebc
+msgid "The following table shows all usage types."
+msgstr ""
+
+#: ../../usage.rst:750
+# 9d81d10d8b5343f19edc1316cfbf4854
+msgid "Type ID"
+msgstr ""
+
+#: ../../usage.rst:750
+# e5f69db4f5e44d94804a6a1fa96b3da8
+msgid "Type Name"
+msgstr ""
+
+#: ../../usage.rst:752
+# 78ead0d9336c42648a3ca740bc0c71c3
+msgid "1"
+msgstr ""
+
+#: ../../usage.rst:752
+# e747e335348c4f96b8157b30a1f87074
+msgid "RUNNING\\_VM"
+msgstr ""
+
+#: ../../usage.rst:752
+# 477ac63f7f36460ea08116c949753044
+msgid "Tracks the total running time of a VM per usage record period. If the VM is upgraded during the usage period, you will get a separate Usage Record for the new upgraded VM."
+msgstr ""
+
+#: ../../usage.rst:762
+# 64af61ae9a154740bc59c51cf93b8e50
+msgid "2"
+msgstr ""
+
+#: ../../usage.rst:762
+# 7e1e8fb7beaf45439e7683227a55abb7
+msgid "ALLOCATED\\_VM"
+msgstr ""
+
+#: ../../usage.rst:762
+# 12dcdffa3a2f4d5faaece0b8ee808625
+msgid "Tracks the total time the VM has been created to the time when it has been destroyed. This usage type is also useful in determining usage for specific templates such as Windows-based templates."
+msgstr ""
+
+#: ../../usage.rst:774
+# 56a5110004de419981e5f220ae4e8552
+msgid "3"
+msgstr ""
+
+#: ../../usage.rst:774
+# 9300fc0a0c054c8cb8cf1c50a798ccfe
+msgid "IP\\_ADDRESS"
+msgstr ""
+
+#: ../../usage.rst:774
+# bdd7930fce7d439cac6b82c99e189623
+msgid "Tracks the public IP address owned by the account."
+msgstr ""
+
+#: ../../usage.rst:778
+# 8f41c0480a214679a34ebff91433884a
+msgid "4"
+msgstr ""
+
+#: ../../usage.rst:778
+# 3468bfe1926344ed8b778f78f298e356
+msgid "NETWORK\\_BYTES\\_SENT"
+msgstr ""
+
+#: ../../usage.rst:778
+# 4fc69e9acd00430db5d7bdd162d53a88
+msgid "Tracks the total number of bytes sent by all the VMs for an account. Cloud.com does not currently track network traffic per VM."
+msgstr ""
+
+#: ../../usage.rst:786
+# 9c0a0d79a0ee491b99fc2f18847a9c29
+msgid "5"
+msgstr ""
+
+#: ../../usage.rst:786
+# 8053534caf9a43cfbe6f344918e90568
+msgid "NETWORK\\_BYTES\\_RECEIVED"
+msgstr ""
+
+#: ../../usage.rst:786
+# a09f77e6b1d540fdb4c9e398f8042f22
+msgid "Tracks the total number of bytes received by all the VMs for an account. Cloud.com does not currently track network traffic per VM."
+msgstr ""
+
+#: ../../usage.rst:795
+# 5d8944a3cb7d444aa82efaa09053af2d
+msgid "6"
+msgstr ""
+
+#: ../../usage.rst:795
+# bd9f4acea1a34fb5ada48e39c65e7781
+msgid "VOLUME"
+msgstr ""
+
+#: ../../usage.rst:795
+# e39b0cb9d477433db943c1dfbeb90bb5
+msgid "Tracks the total time a disk volume has been created to the time when it has been destroyed."
+msgstr ""
+
+#: ../../usage.rst:801
+# fb74bed3e64f40f4b1b99833cdfb858b
+msgid "7"
+msgstr ""
+
+#: ../../usage.rst:801
+# 8dbe0a482b8740bcaba3e70100493143
+msgid "TEMPLATE"
+msgstr ""
+
+#: ../../usage.rst:801
+# e01ba5c82149495a87253a75e8f1ee5c
+msgid "Tracks the total time a template (either created from a snapshot or uploaded to the cloud) has been created to the time it has been destroyed. The size of the template is also returned."
+msgstr ""
+
+#: ../../usage.rst:812
+# ea46b251003a4703b4db0e8e9ca83a4a
+msgid "8"
+msgstr ""
+
+#: ../../usage.rst:812
+# f349c4660c004c8f81133723f6ac350c
+msgid "ISO"
+msgstr ""
+
+#: ../../usage.rst:812
+# 7c32db79c4a944e294459472e67ef9a5
+msgid "Tracks the total time an ISO has been uploaded to the time it has been removed from the cloud. The size of the ISO is also returned."
+msgstr ""
+
+#: ../../usage.rst:820
+# b0dacdf41a1c4d989f2f39ef17257ecc
+msgid "9"
+msgstr ""
+
+#: ../../usage.rst:820
+# 1405b90e80e34b8381a814756e95d768
+msgid "SNAPSHOT"
+msgstr ""
+
+#: ../../usage.rst:820
+# e5fa93c081164375acc3fd52345b1187
+msgid "Tracks the total time from when a snapshot has been created to the time it have been destroyed."
+msgstr ""
+
+#: ../../usage.rst:826
+# 4f2594d3f1f24d2c9169fcfc149a62e9
+msgid "11"
+msgstr ""
+
+#: ../../usage.rst:826
+# d37ae3d5c27447e4a1078346d90a373f
+msgid "LOAD\\_BALANCER\\_POLICY"
+msgstr ""
+
+#: ../../usage.rst:826
+# 024b703ada76417194235a1d10290b53
+msgid "Tracks the total time a load balancer policy has been created to the time it has been removed. Cloud.com does not track whether a VM has been assigned to a policy."
+msgstr ""
+
+#: ../../usage.rst:836
+# 6ebb8ff8421347ba8d0f37e13f9738a1
+msgid "12"
+msgstr ""
+
+#: ../../usage.rst:836
+# 4f5ff172a156494c910377d3273476ca
+msgid "PORT\\_FORWARDING\\_RULE"
+msgstr ""
+
+#: ../../usage.rst:836
+# 00141f10a4c040fd9c1981d4c44a5d6b
+msgid "Tracks the time from when a port forwarding rule was created until the time it was removed."
+msgstr ""
+
+#: ../../usage.rst:842
+# bc4b98fcdabc461a8ede71b5285838b0
+msgid "13"
+msgstr ""
+
+#: ../../usage.rst:842
+# 6123d10ab7004c9b943a532e894e2e20
+msgid "NETWORK\\_OFFERING"
+msgstr ""
+
+#: ../../usage.rst:842
+# ec1c84a50ae5471ba6539ff923b81caa
+msgid "The time from when a network offering was assigned to a VM until it is removed."
+msgstr ""
+
+#: ../../usage.rst:847
+# 04d219bbd49540e7a4d433b51cb42d2b
+msgid "14"
+msgstr ""
+
+#: ../../usage.rst:847
+# d70576ee50674251a6ee58e7a072795a
+msgid "VPN\\_USERS"
+msgstr ""
+
+#: ../../usage.rst:847
+# 7031f45ce0894436b7ab77616de3681f
+msgid "The time from when a VPN user is created until it is removed."
+msgstr ""
+
+#: ../../usage.rst:854
+# da745a0b82b6445e998e6d31a0f107b7
+msgid "Example response from listUsageRecords"
+msgstr ""
+
+#: ../../usage.rst:856
+# 73da4de663384d6ba278d517dc44eeef
+msgid "All CloudStack API requests are submitted in the form of a HTTP GET/POST with an associated command and any parameters. A request is composed of the following whether in HTTP or HTTPS:"
+msgstr ""
+
+#: ../../usage.rst:888
+# b1267ab3f74744b8966d6c8dce38d38a
+msgid "Dates in the Usage Record"
+msgstr ""
+
+#: ../../usage.rst:890
+# f9638c3a7a0c4939922d9b03330f3a5a
+msgid "Usage records include a start date and an end date. These dates define the period of time for which the raw usage number was calculated. If daily aggregation is used, the start date is midnight on the day in question and the end date is 23:59:59 on the day in question (with one exception; see below). A virtual machine could have been deployed at noon on that day, stopped at 6pm on that day, then started up again at 11pm. When usage is calculated on that day, there will be 7 hours of running VM usage (usage type 1) and 12 hours of allocated VM usage (usage type 2). If the same virtual machine runs for the entire next day, there will 24 hours of both running VM usage (type 1) and allocated VM usage (type 2)."
+msgstr ""
+
+#: ../../usage.rst:902
+# aa505995145d4de796ce7a54c69e8c04
+msgid "Note: The start date is not the time a virtual machine was started, and the end date is not the time when a virtual machine was stopped. The start and end dates give the time range within which usage was calculated."
+msgstr ""
+
+#: ../../usage.rst:907
+# ffee51b332cd4e589de90c6abf2b8476
+msgid "For network usage, the start date and end date again define the range in which the number of bytes transferred was calculated. If a user downloads 10 MB and uploads 1 MB in one day, there will be two records, one showing the 10 megabytes received and one showing the 1 megabyte sent."
+msgstr ""
+
+#: ../../usage.rst:913
+# de58fb769cc74ed3a62616b4158bd9e8
+msgid "There is one case where the start date and end date do not correspond to midnight and 11:59:59pm when daily aggregation is used. This occurs only for network usage records. When the usage server has more than one day's worth of unprocessed data, the old data will be included in the aggregation period. The start date in the usage record will show the date and time of the earliest event. For other types of usage, such as IP addresses and VMs, the old unprocessed data is not included in daily aggregation."
+msgstr ""
+
diff --git a/source/adminguide/locale/pot/virtual_machines.pot b/source/adminguide/locale/pot/virtual_machines.pot
new file mode 100644
index 0000000..32a1751
--- /dev/null
+++ b/source/adminguide/locale/pot/virtual_machines.pot
@@ -0,0 +1,1611 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@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 <EMAIL@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"
+
+#: ../../virtual_machines.rst:18
+# 825181279d9643c3ae9e1a485765f79a
+msgid "Working with Virtual Machines"
+msgstr ""
+
+#: ../../virtual_machines.rst:21
+# 8ef9955cc01742fb833f6f4cb20ddc40
+msgid "About Working with Virtual Machines"
+msgstr ""
+
+#: ../../virtual_machines.rst:23
+# 5dfc79c076ae4bcf9b78cbc7e7998fb1
+msgid "CloudStack provides administrators with complete control over the lifecycle of all guest VMs executing in the cloud. CloudStack provides several guest management operations for end users and administrators. VMs may be stopped, started, rebooted, and destroyed."
+msgstr ""
+
+#: ../../virtual_machines.rst:28
+# a74753cd5a1e4e87b2b25bb214d76583
+msgid "Guest VMs have a name and group. VM names and groups are opaque to CloudStack and are available for end users to organize their VMs. Each VM can have three names for use in different contexts. Only two of these names can be controlled by the user:"
+msgstr ""
+
+#: ../../virtual_machines.rst:33
+# 33b7dd1035fe468788852c131410d355
+msgid "Instance name – a unique, immutable ID that is generated by CloudStack and can not be modified by the user. This name conforms to the requirements in IETF RFC 1123."
+msgstr ""
+
+#: ../../virtual_machines.rst:37
+# f1b72ed931524f89a7d072ed361a635e
+msgid "Display name – the name displayed in the CloudStack web UI. Can be set by the user. Defaults to instance name."
+msgstr ""
+
+#: ../../virtual_machines.rst:40
+# adc0efb3ff154603a38bf9294009ac65
+msgid "Name – host name that the DHCP server assigns to the VM. Can be set by the user. Defaults to instance name"
+msgstr ""
+
+#: ../../virtual_machines.rst:44
+# 14d2256532ea4ba9ab19bed35890856a
+msgid "You can append the display name of a guest VM to its internal name. For more information, see `“Appending a Display Name to the Guest VM’s Internal Name” <#appending-a-display-name-to-the-guest-vms-internal-name>`_."
+msgstr ""
+
+#: ../../virtual_machines.rst:48
+# a8d661456c4f45b28ad427c44e9b6325
+msgid "Guest VMs can be configured to be Highly Available (HA). An HA-enabled VM is monitored by the system. If the system detects that the VM is down, it will attempt to restart the VM, possibly on a different host. For more information, see HA-Enabled Virtual Machines on"
+msgstr ""
+
+#: ../../virtual_machines.rst:53
+# 5305c3fec9d94b62aa5980618331557e
+msgid "Each new VM is allocated one public IP address. When the VM is started, CloudStack automatically creates a static NAT between this public IP address and the private IP address of the VM."
+msgstr ""
+
+#: ../../virtual_machines.rst:57
+# 587dd3d141fc46bca48b617989e96f59
+msgid "If elastic IP is in use (with the NetScaler load balancer), the IP address initially allocated to the new VM is not marked as elastic. The user must replace the automatically configured IP with a specifically acquired elastic IP, and set up the static NAT mapping between this new IP and the guest VM’s private IP. The VM’s original IP address is then released and returned to the pool of available public IPs. Optionally, you can also decide not to allocate a public IP to a VM in an EIP-enabled Basic zone. For more information on Elastic IP, see `“About Elastic IP” <networking2.html#about-elastic-ip>`_."
+msgstr ""
+
+#: ../../virtual_machines.rst:67
+# 6fbeb0da9ef448f98d0a7a11b1032be6
+msgid "CloudStack cannot distinguish a guest VM that was shut down by the user (such as with the “shutdown” command in Linux) from a VM that shut down unexpectedly. If an HA-enabled VM is shut down from inside the VM, CloudStack will restart it. To shut down an HA-enabled VM, you must go through the CloudStack UI or API."
+msgstr ""
+
+#: ../../virtual_machines.rst:75
+# 9787aabb3dc94e8db7a5de0c51ea7443
+msgid "Best Practices for Virtual Machines"
+msgstr ""
+
+#: ../../virtual_machines.rst:77
+# 6372fe37d9ed4beeb1424ae97b03ad24
+msgid "For VMs to work as expected and provide excellent service, follow these guidelines."
+msgstr ""
+
+#: ../../virtual_machines.rst:82
+# d2a792bb33c2418bba1e90839b5208d4
+msgid "Monitor VMs for Max Capacity"
+msgstr ""
+
+#: ../../virtual_machines.rst:84
+# aaa155f7b055496592fb19179ed93f73
+msgid "The CloudStack administrator should monitor the total number of VM instances in each cluster, and disable allocation to the cluster if the total is approaching the maximum that the hypervisor can handle. Be sure to leave a safety margin to allow for the possibility of one or more hosts failing, which would increase the VM load on the other hosts as the VMs are automatically redeployed. Consult the documentation for your chosen hypervisor to find the maximum permitted number of VMs per host, then use CloudStack global configuration settings to set this as the default limit. Monitor the VM activity in each cluster at all times. Keep the total number of VMs below a safe level that allows for the occasional host failure. For example, if there are N hosts in the cluster, and you want to allow for one host in the cluster to be down at any given time, the total number of VM instances you can permit in the cluster is at most (N-1) \\* (per-host-limit). Once a cluster reaches this number of VMs, use the CloudStack UI to disable allocation of more VMs to the cluster."
+msgstr ""
+
+#: ../../virtual_machines.rst:103
+# e6554027f7f9466a8a5ab12bbbf30fb9
+msgid "Install Required Tools and Drivers"
+msgstr ""
+
+#: ../../virtual_machines.rst:105
+# 6b07dcd845a944ea872a6ace009f7f24
+msgid "Be sure the following are installed on each VM:"
+msgstr ""
+
+#: ../../virtual_machines.rst:107
+# 31fe2e3e61ec4b15865970eafecc35df
+msgid "For XenServer, install PV drivers and Xen tools on each VM. This will enable live migration and clean guest shutdown. Xen tools are required in order for dynamic CPU and RAM scaling to work."
+msgstr ""
+
+#: ../../virtual_machines.rst:111
+# 59c6618b482a4e8590293c7da8aaf7ef
+msgid "For vSphere, install VMware Tools on each VM. This will enable console view to work properly. VMware Tools are required in order for dynamic CPU and RAM scaling to work."
+msgstr ""
+
+#: ../../virtual_machines.rst:115
+# 0054a653c9ee4d008cb5fff30bcb3de8
+msgid "To be sure that Xen tools or VMware Tools is installed, use one of the following techniques:"
+msgstr ""
+
+#: ../../virtual_machines.rst:118
+# 183593c0142745a49f4f2a3791981e31
+msgid "Create each VM from a template that already has the tools installed; or,"
+msgstr ""
+
+#: ../../virtual_machines.rst:121
+# 4ad9dec1226046d48a5dba3598abbf0a
+msgid "When registering a new template, the administrator or user can indicate whether tools are installed on the template. This can be done through the UI or using the updateTemplate API; or,"
+msgstr ""
+
+#: ../../virtual_machines.rst:125
+# 3a12a213c40345018c066a0ec37e65a9
+msgid "If a user deploys a virtual machine with a template that does not have Xen tools or VMware Tools, and later installs the tools on the VM, then the user can inform CloudStack using the updateVirtualMachine API. After installing the tools and updating the virtual machine, stop and start the VM."
+msgstr ""
+
+#: ../../virtual_machines.rst:133
+# b7a0169d017a496787e38b9e50311a88
+msgid "VM Lifecycle"
+msgstr ""
+
+#: ../../virtual_machines.rst:135
+# 0af797cf30df4ac984c7b8d11ede977e
+msgid "Virtual machines can be in the following states:"
+msgstr ""
+
+#: ../../virtual_machines.rst:137
+# f5d2991885b4440f8c7062a60633f065
+msgid "|basic-deployment.png|"
+msgstr ""
+
+#: ../../virtual_machines.rst:139
+# 4c2d3ebcce3744b481035492578b6e3c
+msgid "Once a virtual machine is destroyed, it cannot be recovered. All the resources used by the virtual machine will be reclaimed by the system. This includes the virtual machine’s IP address."
+msgstr ""
+
+#: ../../virtual_machines.rst:143
+# 08c95a701e5348e789bd295aa7819d86
+msgid "A stop will attempt to gracefully shut down the operating system, which typically involves terminating all the running applications. If the operation system cannot be stopped, it will be forcefully terminated. This has the same effect as pulling the power cord to a physical machine."
+msgstr ""
+
+#: ../../virtual_machines.rst:149
+# 6d5fb2afbc1e44ad842f052187cc201f
+msgid "A reboot is a stop followed by a start."
+msgstr ""
+
+#: ../../virtual_machines.rst:151
+# eb78f755807e4fe59ff45bc534fa6dc5
+msgid "CloudStack preserves the state of the virtual machine hard disk until the machine is destroyed."
+msgstr ""
+
+#: ../../virtual_machines.rst:154
+# e18941c1f49b40d4ae53034763c41e57
+msgid "A running virtual machine may fail because of hardware or network issues. A failed virtual machine is in the down state."
+msgstr ""
+
+#: ../../virtual_machines.rst:157
+# 73bd5337e5854464a320f36cca3d4964
+msgid "The system places the virtual machine into the down state if it does not receive the heartbeat from the hypervisor for three minutes."
+msgstr ""
+
+#: ../../virtual_machines.rst:160
+# a45ff69a534b47189b4457ff2d058d8c
+msgid "The user can manually restart the virtual machine from the down state."
+msgstr ""
+
+#: ../../virtual_machines.rst:162
+# 42d0a445aab2404abad8ce54e6ff5947
+msgid "The system will start the virtual machine from the down state automatically if the virtual machine is marked as HA-enabled."
+msgstr ""
+
+#: ../../virtual_machines.rst:167
+# fdeb58579e7749fe88bdf405f79049e5
+msgid "Creating VMs"
+msgstr ""
+
+#: ../../virtual_machines.rst:169
+# 7453d7d0a14e4a9dab16d5580766c5d5
+msgid "Virtual machines are usually created from a template. Users can also create blank virtual machines. A blank virtual machine is a virtual machine without an OS template. Users can attach an ISO file and install the OS from the CD/DVD-ROM."
+msgstr ""
+
+#: ../../virtual_machines.rst:175
+# 3edf15d4b2054f90ae481e9bde143346
+msgid "You can create a VM without starting it. You can determine whether the VM needs to be started as part of the VM deployment. A request parameter, startVM, in the deployVm API provides this feature. For more information, see the Developer's Guide."
+msgstr ""
+
+#: ../../virtual_machines.rst:180
+# e3cf740a72c247ea8cdb5ff298a2e7b3
+msgid "To create a VM from a template:"
+msgstr ""
+
+#: ../../virtual_machines.rst:182
+#: ../../virtual_machines.rst:212
+#: ../../virtual_machines.rst:330
+#: ../../virtual_machines.rst:366
+# 6b4fb12f7826449389052e48b175bf9a
+# 1c346e18dafd4ac7977a7dc98d85926c
+# 4d63920f853642a68b92f2632d3a1ba1
+# d667b7df24994fc4ac857e47436efd5d
+msgid "Log in to the CloudStack UI as an administrator or user."
+msgstr ""
+
+#: ../../virtual_machines.rst:184
+#: ../../virtual_machines.rst:214
+#: ../../virtual_machines.rst:368
+# 243b4d8b914d49d19dd68312aae2042a
+# fbbc9105a1f14883918e0460b902a681
+# 74fc4567c9104ff0ae51ec0d88dc5006
+msgid "In the left navigation bar, click Instances."
+msgstr ""
+
+#: ../../virtual_machines.rst:186
+#: ../../virtual_machines.rst:216
+# be1be45993694cb6ab943a5c229ac71e
+# 7d1b7b4f15c349c68567df62e225bc34
+msgid "Click Add Instance."
+msgstr ""
+
+#: ../../virtual_machines.rst:188
+#: ../../virtual_machines.rst:218
+# 64202b2c542d459596118bf9dd4ad508
+# 7f1cbee620c946a88f43e9b6c8f1e9bf
+msgid "Select a zone."
+msgstr ""
+
+#: ../../virtual_machines.rst:190
+# a0aa0f810b974edcb1d8f305c1b24a5d
+msgid "Select a template, then follow the steps in the wizard. For more information about how the templates came to be in this list, see `*Working with Templates* <templates.html>`_."
+msgstr ""
+
+#: ../../virtual_machines.rst:194
+# 33bbf5e131484a929c10053278adddde
+msgid "Be sure that the hardware you have allows starting the selected service offering."
+msgstr ""
+
+#: ../../virtual_machines.rst:197
+#: ../../virtual_machines.rst:222
+# 9a01eecf26a748e198056df4f7e9b825
+# 82109b204e5841308ff5e74b12cf24a4
+msgid "Click Submit and your VM will be created and started."
+msgstr ""
+
+#: ../../virtual_machines.rst:200
+# 7a2965e6d5004b7088a5e5bc18da649c
+msgid "For security reason, the internal name of the VM is visible only to the root admin."
+msgstr ""
+
+#: ../../virtual_machines.rst:203
+# c19e66233eaa4d00b5b615550ebc0c11
+msgid "To create a VM from an ISO:"
+msgstr ""
+
+#: ../../virtual_machines.rst:206
+# ff3d83c8dc1b40baab04b8c1bcfe3619
+msgid "(XenServer) Windows VMs running on XenServer require PV drivers, which may be provided in the template or added after the VM is created. The PV drivers are necessary for essential management functions such as mounting additional volumes and ISO images, live migration, and graceful shutdown."
+msgstr ""
+
+#: ../../virtual_machines.rst:220
+# aceacbbcfec4422e939ff1ed89aa25c5
+msgid "Select ISO Boot, and follow the steps in the wizard."
+msgstr ""
+
+#: ../../virtual_machines.rst:226
+# a843dc7f749c44d89ba116d3c6af89f8
+msgid "Accessing VMs"
+msgstr ""
+
+#: ../../virtual_machines.rst:228
+# 0bf035db01dd401abc60fc76e71330ba
+msgid "Any user can access their own virtual machines. The administrator can access all VMs running in the cloud."
+msgstr ""
+
+#: ../../virtual_machines.rst:231
+#: ../../virtual_machines.rst:555
+# ff40a54bdc2e4f3f8b310d37998c096b
+# b719e6aa6218441b864dbd9dbb664b20
+msgid "To access a VM through the CloudStack UI:"
+msgstr ""
+
+#: ../../virtual_machines.rst:233
+#: ../../virtual_machines.rst:557
+#: ../../virtual_machines.rst:618
+#: ../../virtual_machines.rst:792
+#: ../../virtual_machines.rst:820
+# 72fdf34366e84d53a902f30170e96826
+# 3b5b89a3e29346439a79e6c9625ab11a
+# 5d3ec5e17ef1449a85064c70381209dc
+# 151cdfe9cd414184908d5b1c15cc7de9
+# 995bd5571b2446418ec4a6f27a17fe5f
+msgid "Log in to the CloudStack UI as a user or admin."
+msgstr ""
+
+#: ../../virtual_machines.rst:235
+# c09833ddb4424c4e82d2b49397dbf82e
+msgid "Click Instances, then click the name of a running VM."
+msgstr ""
+
+#: ../../virtual_machines.rst:237
+# 7276130f1e014d969cbd9246b1310121
+msgid "Click the View Console button |console-icon.png|."
+msgstr ""
+
+#: ../../virtual_machines.rst:239
+# c06df9b367c1493a908523e863cade69
+msgid "To access a VM directly over the network:"
+msgstr ""
+
+#: ../../virtual_machines.rst:241
+# 3a9997d1c0444c66b00f908de1b14f74
+msgid "The VM must have some port open to incoming traffic. For example, in a basic zone, a new VM might be assigned to a security group which allows incoming traffic. This depends on what security group you picked when creating the VM. In other cases, you can open a port by setting up a port forwarding policy. See `“IP Forwarding and Firewalling” <networking2.html#ip-forwarding-and-firewalling>`_."
+msgstr ""
+
+#: ../../virtual_machines.rst:248
+# aa1d9ea00c0f47d58155e9aa67793a80
+msgid "If a port is open but you can not access the VM using ssh, it’s possible that ssh is not already enabled on the VM. This will depend on whether ssh is enabled in the template you picked when creating the VM. Access the VM through the CloudStack UI and enable ssh on the machine using the commands for the VM’s operating system."
+msgstr ""
+
+#: ../../virtual_machines.rst:254
+# af42226ae2f845c4ae39472cd44d62cf
+msgid "If the network has an external firewall device, you will need to create a firewall rule to allow access. See `“IP Forwarding and Firewalling” <networking2.html#ip-forwarding-and-firewalling>`_."
+msgstr ""
+
+#: ../../virtual_machines.rst:260
+# 334cb66ea0fd46fab55d62d6c94401cc
+msgid "Stopping and Starting VMs"
+msgstr ""
+
+#: ../../virtual_machines.rst:262
+# 194b6682b53b4c028e9387e57f318392
+msgid "Once a VM instance is created, you can stop, restart, or delete it as needed. In the CloudStack UI, click Instances, select the VM, and use the Stop, Start, Reboot, and Destroy buttons."
+msgstr ""
+
+#: ../../virtual_machines.rst:268
+# 3475020a222a4190b9e4e184a4be143c
+msgid "Assigning VMs to Hosts"
+msgstr ""
+
+#: ../../virtual_machines.rst:270
+# ab04e4134ad1499abbfb64970cd8d83b
+msgid "At any point in time, each virtual machine instance is running on a single host. How does CloudStack determine which host to place a VM on? There are several ways:"
+msgstr ""
+
+#: ../../virtual_machines.rst:274
+# c9fcda8e47454c1b9ccdd115dc618ffb
+msgid "Automatic default host allocation. CloudStack can automatically pick the most appropriate host to run each virtual machine."
+msgstr ""
+
+#: ../../virtual_machines.rst:277
+# 13722d82fe934c8fbe47baadf772e4b3
+msgid "Instance type preferences. CloudStack administrators can specify that certain hosts should have a preference for particular types of guest instances. For example, an administrator could state that a host should have a preference to run Windows guests. The default host allocator will attempt to place guests of that OS type on such hosts first. If no such host is available, the allocator will place the instance wherever there is sufficient physical capacity."
+msgstr ""
+
+#: ../../virtual_machines.rst:285
+# a32cedb1c3d54276bafa87b47914776e
+msgid "Vertical and horizontal allocation. Vertical allocation consumes all the resources of a given host before allocating any guests on a second host. This reduces power consumption in the cloud. Horizontal allocation places a guest on each host in a round-robin fashion. This may yield better performance to the guests in some cases."
+msgstr ""
+
+#: ../../virtual_machines.rst:291
+# cc5699db1af34f3a9b499307c558a058
+msgid "End user preferences. Users can not control exactly which host will run a given VM instance, but they can specify a zone for the VM. CloudStack is then restricted to allocating the VM only to one of the hosts in that zone."
+msgstr ""
+
+#: ../../virtual_machines.rst:296
+# 0411284295194622b05a0cb1879eeb76
+msgid "Host tags. The administrator can assign tags to hosts. These tags can be used to specify which host a VM should use. The CloudStack administrator decides whether to define host tags, then create a service offering using those tags and offer it to the user."
+msgstr ""
+
+#: ../../virtual_machines.rst:301
+# ead4cb40fadd4eefa3f8eeddf36bea8e
+msgid "Affinity groups. By defining affinity groups and assigning VMs to them, the user or administrator can influence (but not dictate) which VMs should run on separate hosts. This feature is to let users specify that certain VMs won't be on the same host."
+msgstr ""
+
+#: ../../virtual_machines.rst:306
+# 475f207be88542b496285e35e6edb937
+msgid "CloudStack also provides a pluggable interface for adding new allocators. These custom allocators can provide any policy the administrator desires."
+msgstr ""
+
+#: ../../virtual_machines.rst:312
+# 838c2813c99f4ea89cb67e8b2ff25abd
+msgid "Affinity Groups"
+msgstr ""
+
+#: ../../virtual_machines.rst:314
+# d72b6ebfff7246118fbc4df220e6f966
+msgid "By defining affinity groups and assigning VMs to them, the user or administrator can influence (but not dictate) which VMs should run on separate hosts. This feature is to let users specify that VMs with the same “host anti-affinity” type won’t be on the same host. This serves to increase fault tolerance. If a host fails, another VM offering the same service (for example, hosting the user's website) is still up and running on another host."
+msgstr ""
+
+#: ../../virtual_machines.rst:322
+# 7dad3924b6fe49e9b9e6ed13a6316bbf
+msgid "The scope of an affinity group is per user account."
+msgstr ""
+
+#: ../../virtual_machines.rst:326
+# 537f3770162d4c7db20724e2cd3a6d25
+msgid "Creating a New Affinity Group"
+msgstr ""
+
+#: ../../virtual_machines.rst:328
+# 89ec84e3b1004702a136fe33ae40a620
+msgid "To add an affinity group:"
+msgstr ""
+
+#: ../../virtual_machines.rst:332
+#: ../../virtual_machines.rst:382
+#: ../../virtual_machines.rst:397
+# 2e4c181542d24eceadbedafacef6a048
+# 129e5d65a94748d49cc72d49901d7982
+# bfe6c54e9b1d4b95b230d06a783465c2
+msgid "In the left navigation bar, click Affinity Groups."
+msgstr ""
+
+#: ../../virtual_machines.rst:334
+# 2d49709c41b24dcfa6cbec72f9655ecb
+msgid "Click Add affinity group. In the dialog box, fill in the following fields:"
+msgstr ""
+
+#: ../../virtual_machines.rst:337
+# 8f2541aa578d480ab600f234860b710f
+msgid "Name. Give the group a name."
+msgstr ""
+
+#: ../../virtual_machines.rst:339
+# 283fc43838584136ada4a8670741a62f
+msgid "Description. Any desired text to tell more about the purpose of the group."
+msgstr ""
+
+#: ../../virtual_machines.rst:342
+# 6ad15d35202c4aa3829229be0b4dc5a3
+msgid "Type. The only supported type shipped with CloudStack is Host Anti-Affinity. This indicates that the VMs in this group should avoid being placed on the same host with each other. If you see other types in this list, it means that your installation of CloudStack has been extended with customized affinity group plugins."
+msgstr ""
+
+#: ../../virtual_machines.rst:351
+# 9dd18a72cf94423295b7f4e16ebdd474
+msgid "Assign a New VM to an Affinity Group"
+msgstr ""
+
+#: ../../virtual_machines.rst:353
+# f986290eacc04fcd88cddb44e54dd110
+msgid "To assign a new VM to an affinity group:"
+msgstr ""
+
+#: ../../virtual_machines.rst:355
+# b7ecd6311df24770b2f5ff16290be095
+msgid "Create the VM as usual, as described in `“Creating VMs” <virtual_machines.html#creating-vms>`_. In the Add Instance wizard, there is a new Affinity tab where you can select the affinity group."
+msgstr ""
+
+#: ../../virtual_machines.rst:362
+# d887ac9c84494254beaf5d7c2d1d8b17
+msgid "Change Affinity Group for an Existing VM"
+msgstr ""
+
+#: ../../virtual_machines.rst:364
+# ac05d8cab3d84c0fb5fecc7ff5be7a41
+msgid "To assign an existing VM to an affinity group:"
+msgstr ""
+
+#: ../../virtual_machines.rst:370
+# 406004d08a994c7e83f19eb8d3d5ccb4
+msgid "Click the name of the VM you want to work with."
+msgstr ""
+
+#: ../../virtual_machines.rst:372
+# 5198d04fabab4aba81bb176cafd9cd5f
+msgid "Stop the VM by clicking the Stop button."
+msgstr ""
+
+#: ../../virtual_machines.rst:374
+# d7c213c32fa64651beb6d71b29a2f881
+msgid "Click the Change Affinity button. |change-affinity-button.png|"
+msgstr ""
+
+#: ../../virtual_machines.rst:378
+# 7964ffac44554385887c85ac33410324
+msgid "View Members of an Affinity Group"
+msgstr ""
+
+#: ../../virtual_machines.rst:380
+# 60958f4621bd45d68c4c4e5ff8e6166b
+msgid "To see which VMs are currently assigned to a particular affinity group:"
+msgstr ""
+
+#: ../../virtual_machines.rst:384
+#: ../../virtual_machines.rst:399
+# 44277c6e70cc49f5a0262172b42602cd
+# 84c34fd8f1024bc3b3b89c6074d25602
+msgid "Click the name of the group you are interested in."
+msgstr ""
+
+#: ../../virtual_machines.rst:386
+# d621ae0b24c54f108a31c5dc8cf05476
+msgid "Click View Instances. The members of the group are listed."
+msgstr ""
+
+#: ../../virtual_machines.rst:388
+# 43f372265bc14aa89389bbc7b9584816
+msgid "From here, you can click the name of any VM in the list to access all its details and controls."
+msgstr ""
+
+#: ../../virtual_machines.rst:393
+# c126741a86364834b153814dff481a58
+msgid "Delete an Affinity Group"
+msgstr ""
+
+#: ../../virtual_machines.rst:395
+# 41b2a9676116417a9cc26ddecd8e35c0
+msgid "To delete an affinity group:"
+msgstr ""
+
+#: ../../virtual_machines.rst:401
+# 97c32e0a3b4d4a039f0167b916626e38
+msgid "Click Delete."
+msgstr ""
+
+#: ../../virtual_machines.rst:403
+# 2f1e052c0a0441988e9ccb2459b64996
+msgid "Any VM that is a member of the affinity group will be disassociated from the group. The former group members will continue to run normally on the current hosts, but if the VM is restarted, it will no longer follow the host allocation rules from its former affinity group."
+msgstr ""
+
+#: ../../virtual_machines.rst:411
+# 1500b2cdf2f8433f9dc55740099c7554
+msgid "Virtual Machine Snapshots"
+msgstr ""
+
+#: ../../virtual_machines.rst:413
+#: ../../virtual_machines.rst:643
+# 352168175d0f45c7944fb134e5e1ccb0
+# f1ff6b7e77974160b7eb0e268b6c8adf
+msgid "(Supported on VMware and XenServer)"
+msgstr ""
+
+#: ../../virtual_machines.rst:415
+# 4b76741f3c964e48b09015a19ac9ffe6
+msgid "In addition to the existing CloudStack ability to snapshot individual VM volumes, you can take a VM snapshot to preserve all the VM's data volumes as well as (optionally) its CPU/memory state. This is useful for quick restore of a VM. For example, you can snapshot a VM, then make changes such as software upgrades. If anything goes wrong, simply restore the VM to its previous state using the previously saved VM snapshot."
+msgstr ""
+
+#: ../../virtual_machines.rst:423
+# 9ea94fa6d9804e22af343c5c65a0362d
+msgid "The snapshot is created using the hypervisor's native snapshot facility. The VM snapshot includes not only the data volumes, but optionally also whether the VM is running or turned off (CPU state) and the memory contents. The snapshot is stored in CloudStack's primary storage."
+msgstr ""
+
+#: ../../virtual_machines.rst:428
+# b710a2e6c248420bb55ebfa8f0f376dc
+msgid "VM snapshots can have a parent/child relationship. Each successive snapshot of the same VM is the child of the snapshot that came before it. Each time you take an additional snapshot of the same VM, it saves only the differences between the current state of the VM and the state stored in the most recent previous snapshot. The previous snapshot becomes a parent, and the new snapshot is its child. It is possible to create a long chain of these parent/child snapshots, which amount to a \"redo\" record leading from the current state of the VM back to the original."
+msgstr ""
+
+#: ../../virtual_machines.rst:438
+# efe6658a42c34ba1badb3bb03008f9f0
+msgid "If you need more information about VM snapshots on VMware, check out the VMware documentation and the VMware Knowledge Base, especially `Understanding virtual machine snapshots <http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1015180>`_."
+msgstr ""
+
+#: ../../virtual_machines.rst:445
+# 8fb9c61d831b4840801c19c568c3e2f7
+msgid "Limitations on VM Snapshots"
+msgstr ""
+
+#: ../../virtual_machines.rst:447
+# b40a26e614ff482b83dd6fe7ca66a097
+msgid "If a VM has some stored snapshots, you can't attach new volume to the VM or delete any existing volumes. If you change the volumes on the VM, it would become impossible to restore the VM snapshot which was created with the previous volume structure. If you want to attach a volume to such a VM, first delete its snapshots."
+msgstr ""
+
+#: ../../virtual_machines.rst:453
+# 137adaa8ad304bad8e6a62a539a5b277
+msgid "VM snapshots which include both data volumes and memory can't be kept if you change the VM's service offering. Any existing VM snapshots of this type will be discarded."
+msgstr ""
+
+#: ../../virtual_machines.rst:457
+# 9890e43dc8174a959a93587c2843f753
+msgid "You can't make a VM snapshot at the same time as you are taking a volume snapshot."
+msgstr ""
+
+#: ../../virtual_machines.rst:460
+# 0ffbf8b4539648a4884ee457c3ab1cb1
+msgid "You should use only CloudStack to create VM snapshots on hosts managed by CloudStack. Any snapshots that you make directly on the hypervisor will not be tracked in CloudStack."
+msgstr ""
+
+#: ../../virtual_machines.rst:466
+# 77f6cb8f4c0f41fcb04fe4aa2c2f5268
+msgid "Configuring VM Snapshots"
+msgstr ""
+
+#: ../../virtual_machines.rst:468
+# 8582f7496ba340e7b18f0ec535fc74c1
+msgid "The cloud administrator can use global configuration variables to control the behavior of VM snapshots. To set these variables, go through the Global Settings area of the CloudStack UI."
+msgstr ""
+
+#: ../../virtual_machines.rst:472
+# f9f9fa5a5bf040cf942989a479a5e690
+msgid "Configuration Setting Name"
+msgstr ""
+
+#: ../../virtual_machines.rst:474
+# 68ee9c1c4d5a4d0b85ee63309d7b1db0
+msgid "Description"
+msgstr ""
+
+#: ../../virtual_machines.rst:476
+# 85763ceb28de4f0eaca494db0a967117
+msgid "vmsnapshots.max"
+msgstr ""
+
+#: ../../virtual_machines.rst:478
+# 7466c6685f504780a8c5d77c5d580374
+msgid "The maximum number of VM snapshots that can be saved for any given virtual machine in the cloud. The total possible number of VM snapshots in the cloud is (number of VMs) \\* vmsnapshots.max. If the number of snapshots for any VM ever hits the maximum, the older ones are removed by the snapshot expunge job."
+msgstr ""
+
+#: ../../virtual_machines.rst:484
+# 2fd939410c2b4b3aa8b3003ab8a3b968
+msgid "vmsnapshot.create.wait"
+msgstr ""
+
+#: ../../virtual_machines.rst:486
+# 375a0959e9c94eb1a423b278ae046b5b
+msgid "Number of seconds to wait for a snapshot job to succeed before declaring failure and issuing an error."
+msgstr ""
+
+#: ../../virtual_machines.rst:491
+# 2b92af396f6c475a81e3dd289b5b2058
+msgid "Using VM Snapshots"
+msgstr ""
+
+#: ../../virtual_machines.rst:493
+# 936e0bc234f649d98911b973d2a89f24
+msgid "To create a VM snapshot using the CloudStack UI:"
+msgstr ""
+
+#: ../../virtual_machines.rst:495
+# 7cd076f83efb4c1bbf3fd895f87582e8
+msgid "Log in to the CloudStack UI as a user or administrator."
+msgstr ""
+
+#: ../../virtual_machines.rst:497
+# 79e76d457cf54a80bf3e15e93c930b60
+msgid "Click Instances."
+msgstr ""
+
+#: ../../virtual_machines.rst:499
+# 271888c8e7844949b68a79c940659c7b
+msgid "Click the name of the VM you want to snapshot."
+msgstr ""
+
+#: ../../virtual_machines.rst:501
+# e60b0597ab2c4b37b9c1b6e585208f39
+msgid "Click the Take VM Snapshot button. |VMSnapshotButton.png|"
+msgstr ""
+
+#: ../../virtual_machines.rst:504
+# 516b8188c37544fe9289100fa8fd6f81
+msgid "If a snapshot is already in progress, then clicking this button will have no effect."
+msgstr ""
+
+#: ../../virtual_machines.rst:507
+# 3af8f23237d44f6a82ff3805d8748f9b
+msgid "Provide a name and description. These will be displayed in the VM Snapshots list."
+msgstr ""
+
+#: ../../virtual_machines.rst:510
+# 213a0335d6b44dc3a98d11a064dc6168
+msgid "(For running VMs only) If you want to include the VM's memory in the snapshot, click the Memory checkbox. This saves the CPU and memory state of the virtual machine. If you don't check this box, then only the current state of the VM disk is saved. Checking this box makes the snapshot take longer."
+msgstr ""
+
+#: ../../virtual_machines.rst:516
+# d45f3edd0bc741a7a60bc61f1687caae
+msgid "Quiesce VM: check this box if you want to quiesce the file system on the VM before taking the snapshot. Not supported on XenServer when used with CloudStack-provided primary storage."
+msgstr ""
+
+#: ../../virtual_machines.rst:520
+# fe21f13b62b746c7a13b2f7f85a6eaa9
+msgid "When this option is used with CloudStack-provided primary storage, the quiesce operation is performed by the underlying hypervisor (VMware is supported). When used with another primary storage vendor's plugin, the quiesce operation is provided according to the vendor's implementation."
+msgstr ""
+
+#: ../../virtual_machines.rst:526
+#: ../../virtual_machines.rst:635
+#: ../../virtual_machines.rst:808
+#: ../../virtual_machines.rst:951
+#: ../../virtual_machines.rst:975
+# 2a6c32cefec74407bd7fbe5e305ad9fc
+# a8e7b2f2b1c94ee9ab5aacd3929d2b84
+# cd457f5e102e42109f716c58cae05fee
+# 2226bef2616a496e93a295e437d134ec
+# 48260fa4b2a8429582628ee0a4834f18
+msgid "Click OK."
+msgstr ""
+
+#: ../../virtual_machines.rst:528
+# f4d9b9197aca4868ab4d46cfeaeeeb8d
+msgid "To delete a snapshot or restore a VM to the state saved in a particular snapshot:"
+msgstr ""
+
+#: ../../virtual_machines.rst:531
+# 36f6cf98d55c41459202b6750b7eb7f4
+msgid "Navigate to the VM as described in the earlier steps."
+msgstr ""
+
+#: ../../virtual_machines.rst:533
+# bf91c94f8979476a930e9dbf513be4d4
+msgid "Click View VM Snapshots."
+msgstr ""
+
+#: ../../virtual_machines.rst:535
+# e7ccaab839314560b552b6071fc14e64
+msgid "In the list of snapshots, click the name of the snapshot you want to work with."
+msgstr ""
+
+#: ../../virtual_machines.rst:538
+# 8e39335e75044ff99ab9e0def4fdc7d3
+msgid "Depending on what you want to do:"
+msgstr ""
+
+#: ../../virtual_machines.rst:540
+# 1992a3d840bc470fabd250937c4de81e
+msgid "To delete the snapshot, click the Delete button. |delete-button.png|"
+msgstr ""
+
+#: ../../virtual_machines.rst:542
+# 00f5fcea682d428c9a9e195edb1178e9
+msgid "To revert to the snapshot, click the Revert button. |revert-vm.png|"
+msgstr ""
+
+#: ../../virtual_machines.rst:545
+# d31395bcdf554ce6a1057725cfec443b
+msgid "VM snapshots are deleted automatically when a VM is destroyed. You don't have to manually delete the snapshots in this case."
+msgstr ""
+
+#: ../../virtual_machines.rst:550
+# b68606a2ccc14896810536c55cfc1b43
+msgid "Changing the VM Name, OS, or Group"
+msgstr ""
+
+#: ../../virtual_machines.rst:552
+# c3a4b62362fc4863a6506f6a5e3187de
+msgid "After a VM is created, you can modify the display name, operating system, and the group it belongs to."
+msgstr ""
+
+#: ../../virtual_machines.rst:559
+#: ../../virtual_machines.rst:620
+#: ../../virtual_machines.rst:794
+#: ../../virtual_machines.rst:822
+#: ../../virtual_machines.rst:967
+# 72447d94968d48569debc5b7e37e4e80
+# 635b0652817c46e8929098fb5425c79b
+# edcc32c2db4948f7b0702e1fec2c46dd
+# af3dab76cece4fbfa032b786f5efe55f
+# 19861b8d6dbc4928b12763a78bf07383
+msgid "In the left navigation, click Instances."
+msgstr ""
+
+#: ../../virtual_machines.rst:561
+# b339e4730d0445bebdcb106a5c75c2f4
+msgid "Select the VM that you want to modify."
+msgstr ""
+
+#: ../../virtual_machines.rst:563
+#: ../../virtual_machines.rst:627
+# 304e46f42670493198568fd5f0ff4ee9
+# 7fdd96b1f7e0497fb108cb28b45a1d3c
+msgid "Click the Stop button to stop the VM. |StopButton.png|"
+msgstr ""
+
+#: ../../virtual_machines.rst:565
+# 8b84a60389bf4387933672f32d30340e
+msgid "Click Edit. |EditButton.png|"
+msgstr ""
+
+#: ../../virtual_machines.rst:567
+# f5ce6fcba1ca478e9bd1598907c1a601
+msgid "Make the desired changes to the following:"
+msgstr ""
+
+#: ../../virtual_machines.rst:569
+# 96da85f1c1db4d90b6131a4e7bbe1267
+msgid "**Display name**: Enter a new display name if you want to change the name of the VM."
+msgstr ""
+
+#: ../../virtual_machines.rst:572
+# b2eb919b8d15426a86942e811b6b785a
+msgid "**OS Type**: Select the desired operating system."
+msgstr ""
+
+#: ../../virtual_machines.rst:574
+# 963531001c6f471fae769294df407de4
+msgid "**Group**: Enter the group name for the VM."
+msgstr ""
+
+#: ../../virtual_machines.rst:576
+#: ../../virtual_machines.rst:691
+# 1f8f9ed119ca43b291afa2ae2b572532
+# acdd7ec88c4b4a27a7b9ade935e17aad
+msgid "Click Apply."
+msgstr ""
+
+#: ../../virtual_machines.rst:580
+# 35efc08bc7314a2a83b202b6bfd078c6
+msgid "Appending a Display Name to the Guest VM’s Internal Name"
+msgstr ""
+
+#: ../../virtual_machines.rst:582
+# 090483f924564a9d8180f7df880f4066
+msgid "Every guest VM has an internal name. The host uses the internal name to identify the guest VMs. CloudStack gives you an option to provide a guest VM with a display name. You can set this display name as the internal name so that the vCenter can use it to identify the guest VM. A new global parameter, vm.instancename.flag, has now been added to achieve this functionality."
+msgstr ""
+
+#: ../../virtual_machines.rst:589
+# f1544ed6d7c34d8ebadbc2726fd7edb9
+msgid "The default format of the internal name is i-<user\\_id>-<vm\\_id>-<instance.name>, where instance.name is a global parameter. However, If vm.instancename.flag is set to true, and if a display name is provided during the creation of a guest VM, the display name is appended to the internal name of the guest VM on the host. This makes the internal name format as i-<user\\_id>-<vm\\_id>-<displayName>. The default value of vm.instancename.flag is set to false. This feature is intended to make the correlation between instance names and internal names easier in large data center deployments."
+msgstr ""
+
+#: ../../virtual_machines.rst:599
+# fa48ed23ffd24df4a02ee5f2167670e9
+msgid "The following table explains how a VM name is displayed in different scenarios."
+msgstr ""
+
+#: ../../virtual_machines.rst:603
+# 76ff8c667a8c480fb21958db7dd65d12
+msgid "User-Provided Display Name"
+msgstr ""
+
+#: ../../virtual_machines.rst:603
+# 77b3d04a25244f7b88843f76b0269874
+msgid "vm.instancename.flag"
+msgstr ""
+
+#: ../../virtual_machines.rst:603
+# eb539380b01a4ba7abe6fab6cbef8d37
+msgid "Hostname on the VM"
+msgstr ""
+
+#: ../../virtual_machines.rst:603
+# 44a68176f9334f3d893063ea88a1880e
+msgid "Name on vCenter"
+msgstr ""
+
+#: ../../virtual_machines.rst:603
+# 09d5fe54336843e99505c1bd9d7c24c9
+msgid "Internal Name"
+msgstr ""
+
+#: ../../virtual_machines.rst:605
+#: ../../virtual_machines.rst:607
+# 8a2a30cd89b8470ab636c82eea18e3a4
+# 8c02dc549daa4804be4ee3b3bf8216a7
+msgid "Yes"
+msgstr ""
+
+#: ../../virtual_machines.rst:605
+#: ../../virtual_machines.rst:606
+# 854c972116cd4ffea1dd8e5be0d72b55
+# 2d6b531677a8463b806c81b61c640ad8
+msgid "True"
+msgstr ""
+
+#: ../../virtual_machines.rst:605
+#: ../../virtual_machines.rst:607
+# e24020ac7abe425a8fc5ae02e4464a87
+# 1eaa0ac4785f44bf90d042a044d9500f
+msgid "Display name"
+msgstr ""
+
+#: ../../virtual_machines.rst:605
+#: ../../virtual_machines.rst:605
+# da8b1b08fbf24753a7ad71dc4c6e910a
+# b909f46baf824afb95db14b2c7a3628a
+msgid "i-<user\\_id>-<vm\\_id>-displayName"
+msgstr ""
+
+#: ../../virtual_machines.rst:606
+#: ../../virtual_machines.rst:608
+# fe84676df63e465ab7918b5f44790a34
+# 799a550bf2024c8db25a267cd0eac622
+msgid "No"
+msgstr ""
+
+#: ../../virtual_machines.rst:606
+#: ../../virtual_machines.rst:608
+# 2f6abcbb57e24820b71d94a8d721a901
+# 05c2b0965dab4221a022ca3f4d1fb71e
+msgid "UUID"
+msgstr ""
+
+#: ../../virtual_machines.rst:606
+#: ../../virtual_machines.rst:606
+#: ../../virtual_machines.rst:607
+#: ../../virtual_machines.rst:607
+#: ../../virtual_machines.rst:608
+#: ../../virtual_machines.rst:608
+# 5179011192fa4530bf1aa6561ba03e80
+# 0e4881cabf544619b6ed3f98b666fa4d
+# 923b87aaf25d404cb843c35fde7e8abf
+# 14cf566f26974c38b4ceaa39a9c10a2b
+# 5351204fc9aa4a09ac443444dcb12cf5
+# 1b26f9393c914e4bbc0f6099ee278a0e
+msgid "i-<user\\_id>-<vm\\_id>-<instance.name>"
+msgstr ""
+
+#: ../../virtual_machines.rst:607
+#: ../../virtual_machines.rst:608
+# 882c61362e02473eb3d26c71fc8a1d93
+# 2e62c668c7b74882a7c5518dd4e345b7
+msgid "False"
+msgstr ""
+
+#: ../../virtual_machines.rst:613
+# c1aad1317c774f3cb8be7a171d4c7615
+msgid "Changing the Service Offering for a VM"
+msgstr ""
+
+#: ../../virtual_machines.rst:615
+# aa826a1e593e4934b4bd9a30bd004c64
+msgid "To upgrade or downgrade the level of compute resources available to a virtual machine, you can change the VM's compute offering."
+msgstr ""
+
+#: ../../virtual_machines.rst:622
+# 8c522d8ff0c341f08389ff47a300b9be
+msgid "Choose the VM that you want to work with."
+msgstr ""
+
+#: ../../virtual_machines.rst:624
+# 0efe6503c5934cb0b193cabcb06131e0
+msgid "(Skip this step if you have enabled dynamic VM scaling; see :ref:`cpu-and-memory-scaling`.)"
+msgstr ""
+
+#: ../../virtual_machines.rst:629
+# 8a714661de844774afa81e0071868b59
+msgid "Click the Change Service button. |ChangeServiceButton.png|"
+msgstr ""
+
+#: ../../virtual_machines.rst:631
+# 83f39b159c464727b6fccf6e6b055c0e
+msgid "The Change service dialog box is displayed."
+msgstr ""
+
+#: ../../virtual_machines.rst:633
+# c981bd6e1e7f49bab3deb9b83f0477f6
+msgid "Select the offering you want to apply to the selected VM."
+msgstr ""
+
+#: ../../virtual_machines.rst:641
+# a01d7307691b4520a87be0d9d9b9da2d
+msgid "CPU and Memory Scaling for Running VMs"
+msgstr ""
+
+#: ../../virtual_machines.rst:645
+# ab0e9786b026430a9847f2f68311aeb3
+msgid "It is not always possible to accurately predict the CPU and RAM requirements when you first deploy a VM. You might need to increase these resources at any time during the life of a VM. You can dynamically modify CPU and RAM levels to scale up these resources for a running VM without incurring any downtime."
+msgstr ""
+
+#: ../../virtual_machines.rst:651
+# 115161eb80b3499bacb45dfdfebee485
+msgid "Dynamic CPU and RAM scaling can be used in the following cases:"
+msgstr ""
+
+#: ../../virtual_machines.rst:653
+# 30297090e50d4dde9f897f9a136fe4f6
+msgid "User VMs on hosts running VMware and XenServer."
+msgstr ""
+
+#: ../../virtual_machines.rst:655
+# 6232185457af46168206dcb77fbe3d5a
+msgid "System VMs on VMware."
+msgstr ""
+
+#: ../../virtual_machines.rst:657
+# f6a39632a5fc44fc95fe18b95ec76dca
+msgid "VMware Tools or XenServer Tools must be installed on the virtual machine."
+msgstr ""
+
+#: ../../virtual_machines.rst:660
+# 3a9ff2ea379947d1a7d14452ee5a9f23
+msgid "The new requested CPU and RAM values must be within the constraints allowed by the hypervisor and the VM operating system."
+msgstr ""
+
+#: ../../virtual_machines.rst:663
+# 5110926c89cb47f6b2f174d9b7fd2074
+msgid "New VMs that are created after the installation of CloudStack 4.2 can use the dynamic scaling feature. If you are upgrading from a previous version of CloudStack, your existing VMs created with previous versions will not have the dynamic scaling capability unless you update them using the following procedure."
+msgstr ""
+
+#: ../../virtual_machines.rst:671
+# 1ad181d6d7c7496e95ae7d8940fdae5e
+msgid "Updating Existing VMs"
+msgstr ""
+
+#: ../../virtual_machines.rst:673
+# 869cd5d508b846d8bac2af633484f301
+msgid "If you are upgrading from a previous version of CloudStack, and you want your existing VMs created with previous versions to have the dynamic scaling capability, update the VMs using the following steps:"
+msgstr ""
+
+#: ../../virtual_machines.rst:677
+# 11e41c992a6545bca58c3d47b712fc40
+msgid "Make sure the zone-level setting enable.dynamic.scale.vm is set to true. In the left navigation bar of the CloudStack UI, click Infrastructure, then click Zones, click the zone you want, and click the Settings tab."
+msgstr ""
+
+#: ../../virtual_machines.rst:682
+# 62c28d859ce4495393ca05ebe80feab9
+msgid "Install Xen tools (for XenServer hosts) or VMware Tools (for VMware hosts) on each VM if they are not already installed."
+msgstr ""
+
+#: ../../virtual_machines.rst:685
+# d20322e380d44022b1ff5c61fdb66462
+msgid "Stop the VM."
+msgstr ""
+
+#: ../../virtual_machines.rst:687
+# 7fb4a5e90f7240faa3517081515db067
+msgid "Click the Edit button."
+msgstr ""
+
+#: ../../virtual_machines.rst:689
+# e27c8efe5a804069964feebad14fc869
+msgid "Click the Dynamically Scalable checkbox."
+msgstr ""
+
+#: ../../virtual_machines.rst:693
+# cfbb1778b1b04d149bb2c2bb69c274d3
+msgid "Restart the VM."
+msgstr ""
+
+#: ../../virtual_machines.rst:697
+# f11c788c7fd447179dd19538674fb81c
+msgid "Configuring Dynamic CPU and RAM Scaling"
+msgstr ""
+
+#: ../../virtual_machines.rst:699
+# 30af79a24d8f48a1b834110d8374abbc
+msgid "To configure this feature, use the following new global configuration variables:"
+msgstr ""
+
+#: ../../virtual_machines.rst:702
+# 5a2816315adb4870943cb43b6d0cf99c
+msgid "enable.dynamic.scale.vm: Set to True to enable the feature. By default, the feature is turned off."
+msgstr ""
+
+#: ../../virtual_machines.rst:705
+# cdeb9f1cb4df4b029610a510842cc284
+msgid "scale.retry: How many times to attempt the scaling operation. Default = 2."
+msgstr ""
+
+#: ../../virtual_machines.rst:710
+# 07decccd4eb04199817b30945867ed27
+msgid "How to Dynamically Scale CPU and RAM"
+msgstr ""
+
+#: ../../virtual_machines.rst:712
+# ae889fadf36342a6a037fb765a54fd59
+msgid "To modify the CPU and/or RAM capacity of a virtual machine, you need to change the compute offering of the VM to a new compute offering that has the desired CPU and RAM values. You can use the same steps described above in `“Changing the Service Offering for a VM” <#changing-the-service-offering-for-a-vm>`_, but skip the step where you stop the virtual machine. Of course, you might have to create a new compute offering first."
+msgstr ""
+
+#: ../../virtual_machines.rst:720
+# 4ad82ed62390433a83075a6fe291e6c6
+msgid "When you submit a dynamic scaling request, the resources will be scaled up on the current host if possible. If the host does not have enough resources, the VM will be live migrated to another host in the same cluster. If there is no host in the cluster that can fulfill the requested level of CPU and RAM, the scaling operation will fail. The VM will continue to run as it was before."
+msgstr ""
+
+#: ../../virtual_machines.rst:729
+# 04a78ffb0e8a4995a6fbbf8870ef3c01
+msgid "Limitations"
+msgstr ""
+
+#: ../../virtual_machines.rst:731
+# 4d4543f814604671a8582fd47d1298ca
+msgid "You can not do dynamic scaling for system VMs on XenServer."
+msgstr ""
+
+#: ../../virtual_machines.rst:733
+# 0c3b91b5ecc54cb1b79f79eea7129458
+msgid "CloudStack will not check to be sure that the new CPU and RAM levels are compatible with the OS running on the VM."
+msgstr ""
+
+#: ../../virtual_machines.rst:736
+# c8b490e8cfa64c6c992a761349ffcec9
+msgid "When scaling memory or CPU for a Linux VM on VMware, you might need to run scripts in addition to the other steps mentioned above. For more information, see `Hot adding memory in Linux (1012764) <http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012764>`_ in the VMware Knowledge Base."
+msgstr ""
+
+#: ../../virtual_machines.rst:742
+# 4e112807f7f146ccb7683bafe9845553
+msgid "(VMware) If resources are not available on the current host, scaling up will fail on VMware because of a known issue where CloudStack and vCenter calculate the available capacity differently. For more information, see `https://issues.apache.org/jira/browse/CLOUDSTACK-1809 <https://issues.apache.org/jira/browse/CLOUDSTACK-1809>`_."
+msgstr ""
+
+#: ../../virtual_machines.rst:748
+# eed3ea4ba4134de1b4cb819e07cb8326
+msgid "On VMs running Linux 64-bit and Windows 7 32-bit operating systems, if the VM is initially assigned a RAM of less than 3 GB, it can be dynamically scaled up to 3 GB, but not more. This is due to a known issue with these operating systems, which will freeze if an attempt is made to dynamically scale from less than 3 GB to more than 3 GB."
+msgstr ""
+
+#: ../../virtual_machines.rst:756
+# 0f66f02496244365a1fc127038eafca0
+msgid "Resetting the Virtual Machine Root Volume on Reboot"
+msgstr ""
+
+#: ../../virtual_machines.rst:758
+# 63185701fdb845c78448a80722e1e1f9
+msgid "For secure environments, and to ensure that VM state is not persisted across reboots, you can reset the root disk. For more information, see `“Reset VM to New Root Disk on Reboot” <storage.html#reset-vm-to-new-root-disk-on-reboot>`_."
+msgstr ""
+
+#: ../../virtual_machines.rst:765
+# 66018bd4d29d47f5b9921b2b638bd9e5
+msgid "Moving VMs Between Hosts (Manual Live Migration)"
+msgstr ""
+
+#: ../../virtual_machines.rst:767
+# 4a11ec0f0f7849af900329d21eb5021a
+msgid "The CloudStack administrator can move a running VM from one host to another without interrupting service to users or going into maintenance mode. This is called manual live migration, and can be done under the following conditions:"
+msgstr ""
+
+#: ../../virtual_machines.rst:772
+# f7d30be3c9c04c2890163879415fbec7
+msgid "The root administrator is logged in. Domain admins and users can not perform manual live migration of VMs."
+msgstr ""
+
+#: ../../virtual_machines.rst:775
+# 17e5f9d4b5d849c395dc3660e836ea8c
+msgid "The VM is running. Stopped VMs can not be live migrated."
+msgstr ""
+
+#: ../../virtual_machines.rst:777
+# 948845ad74164fee9ba6899a995747ff
+msgid "The destination host must have enough available capacity. If not, the VM will remain in the \"migrating\" state until memory becomes available."
+msgstr ""
+
+#: ../../virtual_machines.rst:781
+# 926ce179048d440ba2bea6731af74b85
+msgid "(KVM) The VM must not be using local disk storage. (On XenServer and VMware, VM live migration with local disk is enabled by CloudStack support for XenMotion and vMotion.)"
+msgstr ""
+
+#: ../../virtual_machines.rst:785
+# 7afc45cd0fd64406bf6773ae8ca01061
+msgid "(KVM) The destination host must be in the same cluster as the original host. (On XenServer and VMware, VM live migration from one cluster to another is enabled by CloudStack support for XenMotion and vMotion.)"
+msgstr ""
+
+#: ../../virtual_machines.rst:790
+# 5b314d24029f4c3b8005118729a96b8a
+msgid "To manually live migrate a virtual machine"
+msgstr ""
+
+#: ../../virtual_machines.rst:796
+# 1e1e47dac41d499993b564e4a93cb2d3
+msgid "Choose the VM that you want to migrate."
+msgstr ""
+
+#: ../../virtual_machines.rst:798
+# 761a3094e3774e94a810eb219c96c394
+msgid "Click the Migrate Instance button. |Migrateinstance.png|"
+msgstr ""
+
+#: ../../virtual_machines.rst:800
+# fd690eecd191485bb7d1b4908411a5cc
+msgid "From the list of suitable hosts, choose the one to which you want to move the VM."
+msgstr ""
+
+#: ../../virtual_machines.rst:804
+# 726aae3ee8924808ba550a28342fc0e5
+msgid "If the VM's storage has to be migrated along with the VM, this will be noted in the host list. CloudStack will take care of the storage migration for you."
+msgstr ""
+
+#: ../../virtual_machines.rst:812
+# 8f08330a7d1e42caaf5ef765aa58882a
+msgid "Deleting VMs"
+msgstr ""
+
+#: ../../virtual_machines.rst:814
+# c3d724719a8246f193d97c4f0d121699
+msgid "Users can delete their own virtual machines. A running virtual machine will be abruptly stopped before it is deleted. Administrators can delete any virtual machines."
+msgstr ""
+
+#: ../../virtual_machines.rst:818
+# 7ce9ae8ec54a41f9a717fdf87bd9c144
+msgid "To delete a virtual machine:"
+msgstr ""
+
+#: ../../virtual_machines.rst:824
+# e404b64388f74a71bbfc6af41ccd3ff1
+msgid "Choose the VM that you want to delete."
+msgstr ""
+
+#: ../../virtual_machines.rst:826
+# 2d8231a2d7c149b796ed88861d1bb909
+msgid "Click the Destroy Instance button. |Destroyinstance.png|"
+msgstr ""
+
+#: ../../virtual_machines.rst:830
+# e060074ca29143089e33cdd841b6e53c
+msgid "Working with ISOs"
+msgstr ""
+
+#: ../../virtual_machines.rst:832
+# 49e588f8f3d3457396167bfe47840a9c
+msgid "CloudStack supports ISOs and their attachment to guest VMs. An ISO is a read-only file that has an ISO/CD-ROM style file system. Users can upload their own ISOs and mount them on their guest VMs."
+msgstr ""
+
+#: ../../virtual_machines.rst:836
+# 43da1c69da0e4ff3ba3867e9061ad9c4
+msgid "ISOs are uploaded based on a URL. HTTP is the supported protocol. Once the ISO is available via HTTP specify an upload URL such as http://my.web.server/filename.iso."
+msgstr ""
+
+#: ../../virtual_machines.rst:840
+# 646b8bd2384245229f23171a7a8d7712
+msgid "ISOs may be public or private, like templates.ISOs are not hypervisor-specific. That is, a guest on vSphere can mount the exact same image that a guest on KVM can mount."
+msgstr ""
+
+#: ../../virtual_machines.rst:844
+# 3d98a7d5d5ef47d5b8a0ccafaa66e0e7
+msgid "ISO images may be stored in the system and made available with a privacy level similar to templates. ISO images are classified as either bootable or not bootable. A bootable ISO image is one that contains an OS image. CloudStack allows a user to boot a guest VM off of an ISO image. Users can also attach ISO images to guest VMs. For example, this enables installing PV drivers into Windows. ISO images are not hypervisor-specific."
+msgstr ""
+
+#: ../../virtual_machines.rst:854
+# 8d9568801830478a848ccdac420a263f
+msgid "Adding an ISO"
+msgstr ""
+
+#: ../../virtual_machines.rst:856
+# ba8d1a29acc24d7ca0da86abbc13d3d2
+msgid "To make additional operating system or other software available for use with guest VMs, you can add an ISO. The ISO is typically thought of as an operating system image, but you can also add ISOs for other types of software, such as desktop applications that you want to be installed as part of a template."
+msgstr ""
+
+#: ../../virtual_machines.rst:862
+# 79227c9ef0904022a147fb56ff1f7530
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../virtual_machines.rst:864
+# 0241367a6d3f4783a3b774447b3e7ba8
+msgid "In the left navigation bar, click Templates."
+msgstr ""
+
+#: ../../virtual_machines.rst:866
+# 0f973ef8ca224955a380e55e4cb178f7
+msgid "In Select View, choose ISOs."
+msgstr ""
+
+#: ../../virtual_machines.rst:868
+# 7fa77a1f7f2c433b9a91a2674c905e0f
+msgid "Click Add ISO."
+msgstr ""
+
+#: ../../virtual_machines.rst:870
+# d823b6abfa4f4f90a537b89a3028cbf8
+msgid "In the Add ISO screen, provide the following:"
+msgstr ""
+
+#: ../../virtual_machines.rst:872
+# 3685d0bb311b4ed380fda725b7cd9278
+msgid "**Name**: Short name for the ISO image. For example, CentOS 6.2 64-bit."
+msgstr ""
+
+#: ../../virtual_machines.rst:875
+# 2b4eed14408848cdba835ad59d43680e
+msgid "**Description**: Display test for the ISO image. For example, CentOS 6.2 64-bit."
+msgstr ""
+
+#: ../../virtual_machines.rst:878
+# f186dace19cc4fb78d4e957564d8542e
+msgid "**URL**: The URL that hosts the ISO image. The Management Server must be able to access this location via HTTP. If needed you can place the ISO image directly on the Management Server"
+msgstr ""
+
+#: ../../virtual_machines.rst:882
+# 425e7404b8194bb5931d02792793408e
+msgid "**Zone**: Choose the zone where you want the ISO to be available, or All Zones to make it available throughout CloudStack."
+msgstr ""
+
+#: ../../virtual_machines.rst:885
+# aa204bdaf6d9433bb4412c757dc5d44b
+msgid "**Bootable**: Whether or not a guest could boot off this ISO image. For example, a CentOS ISO is bootable, a Microsoft Office ISO is not bootable."
+msgstr ""
+
+#: ../../virtual_machines.rst:889
+# 8b59d99740ca42ecbb70e61c148a6cea
+msgid "**OS Type**: This helps CloudStack and the hypervisor perform certain operations and make assumptions that improve the performance of the guest. Select one of the following."
+msgstr ""
+
+#: ../../virtual_machines.rst:893
+# 55d339b4332b4f8d90ab0c41ac4064b8
+msgid "If the operating system of your desired ISO image is listed, choose it."
+msgstr ""
+
+#: ../../virtual_machines.rst:896
+# 7181c3bfc6ea45d29f5de6686bdbc0c8
+msgid "If the OS Type of the ISO is not listed or if the ISO is not bootable, choose Other."
+msgstr ""
+
+#: ../../virtual_machines.rst:899
+# 121ed273b9d942f0bcab107605fbc155
+msgid "(XenServer only) If you want to boot from this ISO in PV mode, choose Other PV (32-bit) or Other PV (64-bit)"
+msgstr ""
+
+#: ../../virtual_machines.rst:902
+# 4630b5213f5447b692ec7949d9d2d0b8
+msgid "(KVM only) If you choose an OS that is PV-enabled, the VMs created from this ISO will have a SCSI (virtio) root disk. If the OS is not PV-enabled, the VMs will have an IDE root disk. The PV-enabled types are:"
+msgstr ""
+
+#: ../../virtual_machines.rst:907
+# 635be29dfcf3483a8f0a22d1a6baccd9
+msgid "Fedora 13"
+msgstr ""
+
+#: ../../virtual_machines.rst:909
+# 93e9c1d5a6a3487d8c2c3fa739eaf98d
+msgid "Fedora 12"
+msgstr ""
+
+#: ../../virtual_machines.rst:911
+# 2a8eeb99d2ea4a3bac651072df26da55
+msgid "Fedora 11"
+msgstr ""
+
+#: ../../virtual_machines.rst:913
+# c31cbc941bb44094846e2e60cddb38b8
+msgid "Fedora 10"
+msgstr ""
+
+#: ../../virtual_machines.rst:915
+# 46d96452f5e645899cdbeed2f1d8dd64
+msgid "Fedora 9"
+msgstr ""
+
+#: ../../virtual_machines.rst:917
+# 4b44f056e016456b86e5d94d780f5c70
+msgid "Other PV"
+msgstr ""
+
+#: ../../virtual_machines.rst:919
+# 1f0bbb7dcde34e43a90ab458542c9245
+msgid "Debian GNU/Linux"
+msgstr ""
+
+#: ../../virtual_machines.rst:921
+# fa0ff295703648b6a27c3051e80cc1a7
+msgid "CentOS 5.3"
+msgstr ""
+
+#: ../../virtual_machines.rst:923
+# 10c5d0e4740249ef938a3af66c83cbd4
+msgid "CentOS 5.4"
+msgstr ""
+
+#: ../../virtual_machines.rst:925
+# 3abebb97eac94950b3928ed76316c4fb
+msgid "CentOS 5.5"
+msgstr ""
+
+#: ../../virtual_machines.rst:927
+# 6e43cd1649cc453eb9ddd4fd035c80cc
+msgid "Red Hat Enterprise Linux 5.3"
+msgstr ""
+
+#: ../../virtual_machines.rst:929
+# 460371604538459f9aaab9dbec447cdd
+msgid "Red Hat Enterprise Linux 5.4"
+msgstr ""
+
+#: ../../virtual_machines.rst:931
+# 7d68f48aeac44031b6cd313d5fc799a1
+msgid "Red Hat Enterprise Linux 5.5"
+msgstr ""
+
+#: ../../virtual_machines.rst:933
+# a2764fbb27c34b978dae6142215c6850
+msgid "Red Hat Enterprise Linux 6"
+msgstr ""
+
+#: ../../virtual_machines.rst:936
+# 94dfebd340a74c8b88a2994cc95f58ec
+msgid "It is not recommended to choose an older version of the OS than the version in the image. For example, choosing CentOS 5.4 to support a CentOS 6.2 image will usually not work. In these cases, choose Other."
+msgstr ""
+
+#: ../../virtual_machines.rst:941
+# f097cba5535645278ee6719b4a03072a
+msgid "**Extractable**: Choose Yes if the ISO should be available for extraction."
+msgstr ""
+
+#: ../../virtual_machines.rst:944
+# 7d047a068b0a49599ef129b9c79a6666
+msgid "**Public**: Choose Yes if this ISO should be available to other users."
+msgstr ""
+
+#: ../../virtual_machines.rst:947
+# cc70871cc63f4a778f5a762c96814820
+msgid "**Featured**: Choose Yes if you would like this ISO to be more prominent for users to select. The ISO will appear in the Featured ISOs list. Only an administrator can make an ISO Featured."
+msgstr ""
+
+#: ../../virtual_machines.rst:953
+# 0ada7b2845314dff81bc2025971a349d
+msgid "The Management Server will download the ISO. Depending on the size of the ISO, this may take a long time. The ISO status column will display Ready once it has been successfully downloaded into secondary storage. Clicking Refresh updates the download percentage."
+msgstr ""
+
+#: ../../virtual_machines.rst:958
+# 6918d4062b5b40fe9ec994fe73602e85
+msgid "**Important**: Wait for the ISO to finish downloading. If you move on to the next task and try to use the ISO right away, it will appear to fail. The entire ISO must be available before CloudStack can work with it."
+msgstr ""
+
+#: ../../virtual_machines.rst:965
+# b14f8c054f394494acb88245da8ba860
+msgid "Attaching an ISO to a VM"
+msgstr ""
+
+#: ../../virtual_machines.rst:969
+# b5dd3e88e7fd4e289eaba6d0a5144d12
+msgid "Choose the virtual machine you want to work with."
+msgstr ""
+
+#: ../../virtual_machines.rst:971
+# 7dc31f79f1d14b79a420d462bfee1c59
+msgid "Click the Attach ISO button. |iso.png|"
+msgstr ""
+
+#: ../../virtual_machines.rst:973
+# c8a3faf4703b4ccd9b1e8108195cc959
+msgid "In the Attach ISO dialog box, select the desired ISO."
+msgstr ""
+
+#: ../../virtual_machines.rst:979
+# 549b92307c7f47f98184d3f1124fa408
+msgid "Changing a VM's Base Image"
+msgstr ""
+
+#: ../../virtual_machines.rst:981
+# 13e3fdc48e0047a987a24ca40e0e1a87
+msgid "Every VM is created from a base image, which is a template or ISO which has been created and stored in CloudStack. Both cloud administrators and end users can create and modify templates, ISOs, and VMs."
+msgstr ""
+
+#: ../../virtual_machines.rst:985
+# f5fa30e2adb14813a20639e4efb5b685
+msgid "In CloudStack, you can change an existing VM's base image from one template to another, or from one ISO to another. (You can not change from an ISO to a template, or from a template to an ISO)."
+msgstr ""
+
+#: ../../virtual_machines.rst:989
+# 950431c149ec42938db84b6db95abf20
+msgid "For example, suppose there is a template based on a particular operating system, and the OS vendor releases a software patch. The administrator or user naturally wants to apply the patch and then make sure existing VMs start using it. Whether a software update is involved or not, it's also possible to simply switch a VM from its current template to any other desired template."
+msgstr ""
+
+#: ../../virtual_machines.rst:996
+# fee5003ddd3f4dbbaba68ad0e14fe0d0
+msgid "To change a VM's base image, call the restoreVirtualMachine API command and pass in the virtual machine ID and a new template ID. The template ID parameter may refer to either a template or an ISO, depending on which type of base image the VM was already using (it must match the previous type of image). When this call occurs, the VM's root disk is first destroyed, then a new root disk is created from the source designated in the template ID parameter. The new root disk is attached to the VM, and now the VM is based on the new template."
+msgstr ""
+
+#: ../../virtual_machines.rst:1005
+# 0b104b6b42e9463c92201dd3799d82d6
+msgid "You can also omit the template ID parameter from the restoreVirtualMachine call. In this case, the VM's root disk is destroyed and recreated, but from the same template or ISO that was already in use by the VM."
+msgstr ""
+
+#: ../../virtual_machines.rst:1012
+# e0d3653b842a43b7bd3f9cba8bfb4397
+msgid "Using SSH Keys for Authentication"
+msgstr ""
+
+#: ../../virtual_machines.rst:1014
+# f04e7ecfb1314f84ab38410cef835634
+msgid "In addition to the username and password authentication, CloudStack supports using SSH keys to log in to the cloud infrastructure for additional security. You can use the createSSHKeyPair API to generate the SSH keys."
+msgstr ""
+
+#: ../../virtual_machines.rst:1019
+# 007515e3abea40618c568f35513e1571
+msgid "Because each cloud user has their own SSH key, one cloud user cannot log in to another cloud user's instances unless they share their SSH key files. Using a single SSH key pair, you can manage multiple instances."
+msgstr ""
+
+#: ../../virtual_machines.rst:1025
+# 0edd947ce47c438daad162beb19d2fd7
+msgid "Creating an Instance Template that Supports SSH Keys"
+msgstr ""
+
+#: ../../virtual_machines.rst:1027
+# f2ce122e2dcf433a8945e8c2d923e2b6
+msgid "Create an instance template that supports SSH Keys."
+msgstr ""
+
+#: ../../virtual_machines.rst:1029
+# c683112d085244fabffdc696c868fdf2
+msgid "Create a new instance by using the template provided by cloudstack."
+msgstr ""
+
+#: ../../virtual_machines.rst:1031
+# 0409d2f2d7964ac28bfeb8bed3f58e12
+msgid "For more information on creating a new instance, see"
+msgstr ""
+
+#: ../../virtual_machines.rst:1033
+# 497da833fd9642c39f7ca84fadb0ce84
+msgid "Download the cloudstack script from `The SSH Key Gen Script <http://sourceforge.net/projects/cloudstack/files/SSH%20Key%20Gen%20Script/>`_ to the instance you have created."
+msgstr ""
+
+#: ../../virtual_machines.rst:1041
+# 339a3d87be144308915639d37c89ea1d
+msgid "Copy the file to /etc/init.d."
+msgstr ""
+
+#: ../../virtual_machines.rst:1047
+# f601fce5097849559dc10a71eeb440a9
+msgid "Give the necessary permissions on the script:"
+msgstr ""
+
+#: ../../virtual_machines.rst:1053
+# a5a38d6cf81845aa81cbb049a6c03108
+msgid "Run the script while starting up the operating system:"
+msgstr ""
+
+#: ../../virtual_machines.rst:1059
+# 733b18c1fccb453396b69626f1da7452
+msgid "Stop the instance."
+msgstr ""
+
+#: ../../virtual_machines.rst:1063
+# 580da0c9298f41699deb34011b0310e6
+msgid "Creating the SSH Keypair"
+msgstr ""
+
+#: ../../virtual_machines.rst:1065
+# c5ac52360d7941528588398acbb420e8
+msgid "You must make a call to the createSSHKeyPair api method. You can either use the CloudStack Python API library or the curl commands to make the call to the cloudstack api."
+msgstr ""
+
+#: ../../virtual_machines.rst:1069
+# 89cec2df86664c26bafeddd6fd2aa054
+msgid "For example, make a call from the cloudstack server to create a SSH keypair called \"keypair-doc\" for the admin account in the root domain:"
+msgstr ""
+
+#: ../../virtual_machines.rst:1073
+# c57fbd36512446559d91c1b7eeff7cea
+msgid "Ensure that you adjust these values to meet your needs. If you are making the API call from a different server, your URL/PORT will be different, and you will need to use the API keys."
+msgstr ""
+
+#: ../../virtual_machines.rst:1077
+# 6d651f1b57ef4e81ade3cdafcc642e4b
+msgid "Run the following curl command:"
+msgstr ""
+
+#: ../../virtual_machines.rst:1083
+# 665246c92ab74234b1790979863082a7
+msgid "The output is something similar to what is given below:"
+msgstr ""
+
+#: ../../virtual_machines.rst:1101
+# 64c5993f04f043b5a0e5925aef2db171
+msgid "Copy the key data into a file. The file looks like this:"
+msgstr ""
+
+#: ../../virtual_machines.rst:1118
+# cf75a310b6854564b8053aa63328f6ce
+msgid "Save the file."
+msgstr ""
+
+#: ../../virtual_machines.rst:1122
+# 87cc3ec398db47f09bc21e1a66c8720f
+msgid "Creating an Instance"
+msgstr ""
+
+#: ../../virtual_machines.rst:1124
+# e115c665e72345fcab3fc94458caa818
+msgid "After you save the SSH keypair file, you must create an instance by using the template that you created at `Section 5.2.1, “ Creating an Instance Template that Supports SSH Keys” <#create-ssh-template>`__. Ensure that you use the same SSH key name that you created at `Section 5.2.2, “Creating the SSH Keypair” <#create-ssh-keypair>`__."
+msgstr ""
+
+#: ../../virtual_machines.rst:1131
+# 8e5a7943aaf741989b2f9aa7c92fa061
+msgid "You cannot create the instance by using the GUI at this time and associate the instance with the newly created SSH keypair."
+msgstr ""
+
+#: ../../virtual_machines.rst:1134
+# bb36e5f1a5cc497bb95f96481cd3c232
+msgid "A sample curl command to create a new instance is:"
+msgstr ""
+
+#: ../../virtual_machines.rst:1140
+# 9a98f03016ba40f1b8eb932e8e15a75c
+msgid "Substitute the template, service offering and security group IDs (if you are using the security group feature) that are in your cloud environment."
+msgstr ""
+
+#: ../../virtual_machines.rst:1146
+# 9c448726db0b469bb32323df48aeba12
+msgid "Logging In Using the SSH Keypair"
+msgstr ""
+
+#: ../../virtual_machines.rst:1148
+# 5276ff9c384b4372bc6814b7f7461ae2
+msgid "To test your SSH key generation is successful, check whether you can log in to the cloud setup."
+msgstr ""
+
+#: ../../virtual_machines.rst:1151
+# 632b48d2ebaf4620be47c9bc1b6e1d39
+msgid "For example, from a Linux OS, run:"
+msgstr ""
+
+#: ../../virtual_machines.rst:1157
+# b597ba33b4154d5c95931e7a30a1aa41
+msgid "The -i parameter tells the ssh client to use a ssh key found at ~/.ssh/keypair-doc."
+msgstr ""
+
+#: ../../virtual_machines.rst:1162
+# 0ebe651140d94e709efff80066e042b7
+msgid "Resetting SSH Keys"
+msgstr ""
+
+#: ../../virtual_machines.rst:1164
+# 1367090489eb4ad68179bce4ba266e37
+msgid "With the API command resetSSHKeyForVirtualMachine, a user can set or reset the SSH keypair assigned to a virtual machine. A lost or compromised SSH keypair can be changed, and the user can access the VM by using the new keypair. Just create or register a new keypair, then call resetSSHKeyForVirtualMachine."
+msgstr ""
+
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/accounts.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/accounts.mo
new file mode 100644
index 0000000..cc88167
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/accounts.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/accounts.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/accounts.po
new file mode 100644
index 0000000..2d96d83
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/accounts.po
@@ -0,0 +1,550 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:03+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# bdc151e73be141a8ad0b4190c3102939
+#: ../../accounts.rst:18
+msgid "Managing Accounts, Users and Domains"
+msgstr "管理账户，用户和域"
+
+# a49422e951994e72894009f0fc5cc963
+#: ../../accounts.rst:21
+msgid "Accounts, Users, and Domains"
+msgstr "账户，用户，域"
+
+# 7316ca3f637249cbbf2f29bd75791600
+#: ../../accounts.rst:24
+msgid "Accounts"
+msgstr "账户"
+
+# 7544ce31af194b279c9dcfb7ae37d3cc
+#: ../../accounts.rst:26
+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 "一个账户通常代表一个客户的服务提供者或一个大组织中的一个部门。一个账户可存在多个用户。"
+
+# e758840629a8483ba31892ff437911e1
+#: ../../accounts.rst:32
+msgid "Domains"
+msgstr "域"
+
+# 3e28d2a36b0642c08a698f6a4426e72c
+#: ../../accounts.rst:34
+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 "帐户通常按域进行分组。域中经常包含多个账户，这些账户间存在一些逻辑上关系和一系列该域和其子域下的委派的管理员（这段的意思就是说在逻辑上域下可以有管理员，子域下也可以有管理员）。比如，一个服务提供商可有多个分销商这样的服务提供商就能为每一个分销商创建一个域"
+
+# 79060520f2e046868f58925f3f2efc01
+#: ../../accounts.rst:40
+msgid ""
+"For each account created, the Cloud installation creates three different "
+"types of user accounts: root administrator, domain administrator, and user."
+msgstr "对于每个账户的创建,Cloud的安装过程中创建了三种不同类型的用户账户：根管理员，域管理员，普通用户。"
+
+# 341bf7792d884c2d8180600a07351f62
+#: ../../accounts.rst:46
+msgid "Users"
+msgstr "普通用户"
+
+# 8efee3ca63e44a4098ff5086e58f1249
+#: ../../accounts.rst:48
+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 "用户就像是账户的别名。在同一账户下的用户彼此之间并非隔离的。但是他们与不同账户下的用户是相互隔离的。大多数安装不需要用户的表面概念；他们只是每一个帐户的用户。同一用户不能属于多个帐户。"
+
+# 67a573904306470f87a1f3f6ad52a15f
+#: ../../accounts.rst:54
+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 "多个账户中的用户名在域中应该是唯一的。相同的用户名能在其他的域中存在，包括子域。域名只有在全路径名唯一的时候才能重复。比如，你能创建一个root/d1，也可以创建root/foo/d1和root/sales/d1。"
+
+# af85977a7aeb4aff9010bde059e08b23
+#: ../../accounts.rst:59
+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 "管理员在系统中是拥有特权的账户。可能有多个管理员在系统中，管理员能创建删除其他管理员，并且修改系统中任意用户的密码。"
+
+# 8613eb42958647fba87ae1b922d58740
+#: ../../accounts.rst:66
+msgid "Domain Administrators"
+msgstr "域管理员"
+
+# 901efdb2c8554033b865587a48a319f9
+#: ../../accounts.rst:68
+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 "域管理员可以对属于该域的用户进行管理操作。域管理员在物理服务器或其他域中不可见。"
+
+# 5922a532b5814e479301a7d697eb8854
+#: ../../accounts.rst:74
+msgid "Root Administrator"
+msgstr "根管理员"
+
+# 20be104d0a134bab92309e774b538dd4
+#: ../../accounts.rst:76
+msgid ""
+"Root administrators have complete access to the system, including managing "
+"templates, service offerings, customer care administrators, and domains"
+msgstr "根管理员拥有系统完全访问权限，包括管理模板，服务方案，客户服务管理员和域。"
+
+# 7f9e7eaa9c5b4eaba5575b81514d4040
+#: ../../accounts.rst:82
+msgid "Resource Ownership"
+msgstr "资源所有权"
+
+# 3fad6f5edfb34464b707419ce6b7b4a6
+#: ../../accounts.rst:84
+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 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."
+msgstr "资源属于帐户，而不是帐户中的单个用户。例如，账单、资源限制等由帐户维护，而不是用户维护。用户有权限操作任何在帐户中提供的资源。权限有角色决定。根管理员通过使用assignVirtualMachine API可以将任何虚拟机的所有权从一个帐户调整到另一个帐户。域或子域管理员可以对域中的VMs做同样的操作，包括子域。"
+
+# f25ec45041cd435d83eaf32720407dd4
+#: ../../accounts.rst:96
+msgid "Dedicating Resources to Accounts and Domains"
+msgstr "给帐户和域分配专用资源"
+
+# 8a6427fc034647e681a14ca03224406c
+#: ../../accounts.rst:98
+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 "根管理员可以将资源分配给指定的域或为了保证额外的安全或性能从而需要单独基础架构帐户。为了一个指定的域或账号，区域、机架、群集或者主机可以被根管理员保留。只有域或它的子域中的用户可以使用这个基础架构。比如，只有域中的用户可以在其中的区域中创建来宾虚机。"
+
+# 13b20e92d1144d5da1089384a9ce4e59
+#: ../../accounts.rst:106
+msgid "There are several types of dedication available:"
+msgstr "这里有几种有效的分配方式："
+
+# a62e7433baeb444386932b41fe5601fa
+#: ../../accounts.rst:108
+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 "明确的专用。根管理员在初始部署和配置期间给一个帐户或者域分配了一个区域、机架、群集或者主机。"
+
+# 29fbffa86cfd49b4aa29ea7d373eaa03
+#: ../../accounts.rst:112
+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 "严格的潜在专用：一个主机禁止通过多个账号共享。例如，严格私自共享对于部署的某些应用是有用处的，像没有软件授权主机不能在不同账号间进行桌面共享。"
+
+# a821acd0f71541708e12788d2fbc5d75
+#: ../../accounts.rst:118
+msgid ""
+"Preferred implicit dedication. The VM will be deployed in dedicated "
+"infrastructure if possible. Otherwise, the VM can be deployed in shared "
+"infrastructure."
+msgstr "优先的潜在专用。如果可以的话，VM会被部署在专用的基础架构中。否则，VM可被部署在共享基础架构中。"
+
+# b498c9fe36a94f2588d7a9e4494a761d
+#: ../../accounts.rst:124
+msgid "How to Dedicate a Zone, Cluster, Pod, or Host to an Account or Domain"
+msgstr "如何给帐户或者域指定一个区域、群集、机架或者主机"
+
+# 62ce22c4d6f346b79218ff7a937ee3e2
+#: ../../accounts.rst:126
+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 "对于明确的专用：当部署一个新的区域、机架、群集或者主机的时候，根管理员可以点击Dedicated选框，然后选择域或者帐户来拥有这些资源。"
+
+# 9dfe3b7a9e87411d9694c32c5e4f891e
+#: ../../accounts.rst:130
+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 "对于明确的专用一个已存在的区域、机架、群集或者主机：使用根管理员登录，在UI中找到资源，然后点击Dedicate按钮。|button to dedicate a zone, pod,cluster, or host|"
+
+# 90707af3ed2b4e6fa7875e9bdd890252
+#: ../../accounts.rst:134
+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 "对于隐式的专用：管理员创建的计算服务方案和在部署规划区域选择ImplicitDedicationPlanner。然后在规划模型中，管理员按照是否允许一些人当没有专用资源可用的时候使用共享资源来选择严格的或者优先的。无论何时，用户基于这个服务方案创建的VM都会位于专用主机。"
+
+# fda3697ce3a4454da72edbe9f02b3564
+#: ../../accounts.rst:144
+msgid "How to Use Dedicated Hosts"
+msgstr "如何使用专用主机"
+
+# cfd0e245a5a2498b9fa7c89160957ffe
+#: ../../accounts.rst:146
+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 "要使用明确专用主机，在关联组 (参阅 `“关联组” <virtual_machines.html#affinity-groups>`_)中选择explicit-dedicated 类型。比如，当创建新VM的时候，终端用户可以选择将其运行在专用基础架构上。如果一些基础架构已经被分配给专用的用户帐号或域，那么这个操作才能成功。"
+
+# 86abbd3940f34e96a1ad71a01dc6339d
+#: ../../accounts.rst:155
+msgid "Behavior of Dedicated Hosts, Clusters, Pods, and Zones"
+msgstr "专用主机、群集、机架和区域的行为"
+
+# a9963e63da4e48f2a2b7b7fdad96ba29
+#: ../../accounts.rst:157
+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 "管理员可以将VMs从专用主机上迁移到任何想要的地方，不管目标主机是不同帐号/域专用的还是共享的主机(不对任何特殊帐号或域专用)。CloudStack将生成一个警告，不过操作还是允许的。"
+
+# a9a8992734b0490aac5bd5e5efa45483
+#: ../../accounts.rst:163
+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 "专用主机可用主机标签连接。如果同时需要主机标签和专用，那么VM将只会在匹配所有需求的主机上运行。如果没有专用资源可用于这类用户，那么VM就不会被不部署。"
+
+# 694b1842b07049c094a79e240c2db934
+#: ../../accounts.rst:169
+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 "如果你删除了一个指定了专用资源的帐号或者域，那么其中的任何主机、群集、机架和区域就会被释放。它们会变成可被任何帐户或者域共享，或者管理员可选择重新把它们指定给不同的帐号或域。"
+
+# 9676e7d49a4247c0bd41a3d53e7482a1
+#: ../../accounts.rst:174
+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, a host with system VMs or "
+"virtual routers can be used for preferred implicit dedication."
+msgstr "系统VMs和虚拟路由器影响专用主机的行为。系统VMs和虚拟路由器由CloudStack系统账号拥有，并且它们可在任何主机上部署。它们不会伴随着明确专用主机。主机上的系统虚机和虚拟路由器使其不再适合作为严格的潜在专用主机。主机之所以不能用于严格的潜在专用主机，是因为主机已经有针对帐号(默认系统账号)的VMs。尽管如此，运行着系统VMs或虚拟路由器的主机可以被用于优先的潜在专用。"
+
+# c3ac9b9cb46f4fa7b6ea8d96adc7111e
+#: ../../accounts.rst:186
+msgid "Using an LDAP Server for User Authentication"
+msgstr "使用LDAP服务器用于用户验证"
+
+# 4c358cdbd0ef4ea8bae9aa240f1b4e4a
+#: ../../accounts.rst:188
+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 starting at a specified base "
+"directory and return the distinguished name (DN) and password of the "
+"matching user. This information along with the given password is used to "
+"authenticate the user.."
+msgstr "你可以使用一个外部LDAP服务器，例如微软活动目录或ApacheDS进行CloudStack的终端用户验证。仅仅使用查询过滤器映射CloudStack账户与对应的LDAP帐户。查询过滤器是使用查询语法写的特别的LDAP服务器，可以包括用CloudStack提供的特殊通配符匹配通用的像用户的电子邮件地址和名称这种值。CloudStack将在外部LDAP目录树中从一个指定的基目搜索录并返回专有名称(DN)和密码匹配用户。这个信息以及给定的密码是用于验证用户。。"
+
+# 14c749c7da61408588c8e8cdaa11796c
+#: ../../accounts.rst:199
+msgid ""
+"To set up LDAP authentication in CloudStack, call the CloudStack API command"
+" ldapConfig and provide the following:"
+msgstr "在CloudStack中设置LDAP验证，调用CloudStack API指令ldapConfig，并提供如下："
+
+# c4708aa56b75423080f17f84ec2a37a4
+#: ../../accounts.rst:202
+msgid "Hostname or IP address and listening port of the LDAP server"
+msgstr "LDAP服务器的主机名或IP地址和监听端口"
+
+# ff4d11fcc40f4d5c86ce032c3d6e6a76
+#: ../../accounts.rst:204
+msgid "Base directory and query filter"
+msgstr "基本目录和查询过滤器"
+
+# 0b5fce75930e49b19cf1d00062c78539
+#: ../../accounts.rst:206
+msgid ""
+"Search user DN credentials, which give CloudStack permission to search on "
+"the LDAP server"
+msgstr "搜索用户DN 凭证，这个凭证是授予CloudStack允许搜索LDAP服务器上的凭证"
+
+# c3d66516470141c3af861a4b24f45150
+#: ../../accounts.rst:209
+msgid "SSL keystore and password, if SSL is used"
+msgstr "SSL密钥库和密码，如果使用了SSL"
+
+# 6e565fd7b02d4a97b86b380e839f129f
+#: ../../accounts.rst:213
+msgid "Example LDAP Configuration Commands"
+msgstr "LDAP配置命令示例"
+
+# ee72e29a6b33456684ebcbfd012c075a
+#: ../../accounts.rst:215
+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 "为了明白本章节的示例， 你需要知道调用CloudStack API的基本概念，这在开发者文档中有讲解。"
+
+# 065e58a0d0f74c8d84670251cf00c487
+#: ../../accounts.rst:219
+msgid ""
+"The following shows an example invocation of ldapConfig with an ApacheDS "
+"LDAP server"
+msgstr "以下展示了通过ApacheDS LDAP服务器调用 ldapConfig命令的示例"
+
+# 31d88144f8004adf8efd11cf7f9db7bd
+#: ../../accounts.rst:226
+msgid ""
+"The command must be URL-encoded. Here is the same example without the URL "
+"encoding:"
+msgstr "命令调用的URL必须进行编码. 这里是一个没有进行URL编码的示例："
+
+# 884cde7f5dbd499ba1c28ff09380c692
+#: ../../accounts.rst:244
+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 "以下展示了与活动目录类似的命令。这里，搜索是基于一个公司的测试组，用户是根据邮件地址进行查找。"
+
+# d2675a267aa34f4ea3fe2bba2300b61c
+#: ../../accounts.rst:252
+msgid ""
+"The next few sections explain some of the concepts you will need to know "
+"when filling out the ldapConfig parameters."
+msgstr "接下来的几个章节解释了当填写ldapConfig参数时你需要知道的一些概念。"
+
+# befdce0cfd624549844139c917a82bb4
+#: ../../accounts.rst:257
+msgid "Search Base"
+msgstr "搜索基础目录"
+
+# 1522f19d5a2a4e35a8bedc5d147a1af1
+#: ../../accounts.rst:259
+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 is outside the scope of our documentation."
+" The following table shows some examples of search bases to find users in "
+"the testing department.."
+msgstr "LDAP查询与一个LDAP目录树中的节点有关，称之为做搜索基础目录。搜索基础目录是目录库中的一级的distinguished name(DN)，在这里能找到所有用户。用户可以直属于根目录或者一些子目录。搜索基础目录可能是组织、组或者域用户名。用于写DN变量的语法取决于你所使用的LDAP服务。再深入全面的讨论distinguished names超出了我们文档的范围。以下表格中展示了一些在搜索基础目录中查找测试部门中用户的示例。"
+
+# 3649e87915d24059beec30463e0abd10
+# eb0f32160dd24b21991c2f454df60742
+#: ../../accounts.rst:270 ../../accounts.rst:328
+msgid "LDAP Server"
+msgstr "LDAP服务器"
+
+# d8fb5f498afb4ee1aa6669b39f1e34be
+#: ../../accounts.rst:270
+msgid "Example Search Base DN"
+msgstr "搜索基本DN示例"
+
+# 2e421fc0d49d4a819b31999dc3cae2e0
+# a0327a00878d45dab6dc0bc777814674
+#: ../../accounts.rst:272 ../../accounts.rst:330
+msgid "ApacheDS"
+msgstr "ApacheDS"
+
+# 6c854d5e6cdd4e3aadda7dd9be769a53
+#: ../../accounts.rst:272
+msgid "OU=testing, O=project"
+msgstr "OU=testing, O=project"
+
+# a1fbaf989c584a248386911c51fd2fba
+# c776e850eb3e4d64b262a32a9d302bfb
+#: ../../accounts.rst:273 ../../accounts.rst:331
+msgid "Active Directory"
+msgstr "Active Directory"
+
+# 5d0095ff2d7044e7b60bc1754210dd3c
+#: ../../accounts.rst:273
+msgid "OU=testing, DC=company"
+msgstr "OU=testing, DC=company"
+
+# 8309dae488944f0aae3e84a8e1a97ac3
+#: ../../accounts.rst:278
+msgid "Query Filter"
+msgstr "查询过滤"
+
+# c523dbbf5dd94c62a2e3927a8f3123dc
+#: ../../accounts.rst:280
+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 "查询过滤器用于在外部LDAP服务器中查找一个映射的用户。为实现有效认证，查询过滤器应该将CloudStack的用户唯一映射到LDAP用户。关于查询过滤器的语法，请参考您使用的LDAP服务器文档。"
+
+# f4f9c13ceefa4163962bd3cfab257852
+#: ../../accounts.rst:285
+msgid "The CloudStack query filter wildcards are:"
+msgstr "CloudStack查询过滤的通配符有:"
+
+# bab683973b9045339c8df3488bc5dd1c
+#: ../../accounts.rst:288
+msgid "Query Filter Wildcard"
+msgstr "查询过滤通配符"
+
+# a94af335cc864d9a962f1fb9b7b5f72c
+#: ../../accounts.rst:288
+msgid "Description"
+msgstr "描述"
+
+# 334393ba6786415e91a2ed1a22d26adb
+#: ../../accounts.rst:290
+msgid "%u"
+msgstr "%u"
+
+# 151cd28e952d4ff98ff9d1544698ccb8
+#: ../../accounts.rst:290
+msgid "User name"
+msgstr "用户名"
+
+# f1f86cbcf39e412fb298da7653a123d3
+#: ../../accounts.rst:291
+msgid "%e"
+msgstr "%e"
+
+# fdf52531788c41fabb814f45f07b178a
+#: ../../accounts.rst:291
+msgid "Email address"
+msgstr "邮件地址"
+
+# 6e5b529e3da248ee85f1e20f81bd8e1c
+#: ../../accounts.rst:292
+msgid "%n"
+msgstr "%n"
+
+# 4704eb3b3e494ad3bc2105d98a3c84a9
+#: ../../accounts.rst:292
+msgid "First and last name"
+msgstr "姓名"
+
+# 51612c6475e246f7b7d8a156605a2323
+#: ../../accounts.rst:295
+msgid ""
+"The following examples assume you are using Active Directory, and refer to "
+"user attributes from the Active Directory schema."
+msgstr "下面的示例假设你使用活动目录, 并从活动目录架构中获得用户属性."
+
+# d853815e3f894dcdbb92be883305dc5b
+#: ../../accounts.rst:298
+msgid "If the CloudStack user name is the same as the LDAP user ID:"
+msgstr "如果 CloudStack 的用户名与LDAP中的用户ID一致:"
+
+# d0bb623240d0410eb8d70ed22ba5a2f8
+#: ../../accounts.rst:304
+msgid "If the CloudStack user name is the LDAP display name:"
+msgstr "如果CloudStack的用户名是LDAP中的显示名字："
+
+# 0a96c3c2516946c1b4260fd4d4d6ffb7
+#: ../../accounts.rst:310
+msgid "To find a user by email address:"
+msgstr "使用邮件地址查找用户:"
+
+# 5b63c901fb5a4d208df8e362234d1cba
+#: ../../accounts.rst:318
+msgid "Search User Bind DN"
+msgstr "搜索用户绑定的DN"
+
+# 92769f4cb5be444cab0bcb685ebe1cc4
+#: ../../accounts.rst:320
+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 "bind DN是位于外部被允许在定义的搜索基础目录中搜索LDAP目录的LDAP服务器上的用户。当DN返回值的时候，DN和通过的密码就与LDAPbind一起被用于验证CloudStack 用户。再深入完全的讨论bind DNs超出了文档的范围。下面的表格展示了一些bind DNs的实例。"
+
+# 7fcc45a0be9241b09a01d2287541d652
+#: ../../accounts.rst:328
+msgid "Example Bind DN"
+msgstr "绑定DN示例"
+
+# b4c0b2f84be54e32820cac392b6c9c75
+#: ../../accounts.rst:330
+msgid "CN=Administrator,DC=testing,OU=project,OU=org"
+msgstr "CN=Administrator,DC=testing,OU=project,OU=org"
+
+# 46e145ddbc9f47e08b21fa2631ed9fa7
+#: ../../accounts.rst:331
+msgid "CN=Administrator, OU=testing, DC=company, DC=com"
+msgstr "CN=Administrator, OU=testing, DC=company, DC=com"
+
+# cbaaf7054abf480eb88b336ba62a097b
+#: ../../accounts.rst:336
+msgid "SSL Keystore Path and Password"
+msgstr "SSL 密钥库路径和密码"
+
+# 8a6a84c57cc144edb9a20e63c71ddedc
+#: ../../accounts.rst:338
+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 "如果LDAP 服务器要求SSL， 你需要在ldapConfig命令中通过设置参数ssl, truststore和truststorepass使其生效。在使SSL 对ldapConfig 生效之前，你需要得到LDAP服务器在使用的证书并把它加到被信任的密钥库中。你将需要知道到密钥库和密码的路径。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/administration.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/administration.mo
new file mode 100644
index 0000000..e93c94b
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/administration.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/administration.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/administration.po
new file mode 100644
index 0000000..53c02d6
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/administration.po
@@ -0,0 +1,95 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:04+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 29cfff43a2514946ad4c3499ebefbed6
+#: ../../administration.rst:18
+msgid "User Services"
+msgstr "用户服务"
+
+# d7001feee3bd4b298a4c17869c0c45dc
+#: ../../administration.rst:20
+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 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."
+msgstr "除了云中的物理和逻辑基础设施以及 CloudStack 软件和服务器，你还需要一个用户服务层以便让人们能够真正利用云。这不仅仅意味这一个用户界面，而是一组用户可选择的选项和资源，如通过模版创建虚拟机，磁盘存储等等。如果您正在运行一个商业服务，您将可以跟踪服务和用户资源的使用以及使用计费情况。即使你不对使用云的人收费，-比如说，用户是你的内部组织，或只是你的朋友共享你的云 - 你仍然可以跟踪他们所使用的服务以及有多少人。"
+
+# 8691c3078d2741dabb85f469a7b58373
+#: ../../administration.rst:34
+msgid "Service Offerings, Disk Offerings, Network Offerings, and Templates"
+msgstr "服务方案，磁盘方案，网络方案和模版"
+
+# 82a1a03c5a234653b024700134d18169
+#: ../../administration.rst:36
+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 "用户可以根据不同的功能和特性来创建新的实例，CloudStack提供了几种方法供用户选择以便创建一个新的实例:"
+
+# 5b79acf1c4034cf09e56634938cbfd33
+#: ../../administration.rst:40
+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 "服务方案，由CloudStack管理员定义，提供了CPU速率，CPU核数，内存大小，根磁盘标签等多种选项供选择。可参阅创建新的计算方案。"
+
+# d71f7d3d0dda4061838347d6fc7e35fc
+#: ../../administration.rst:44
+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 "磁盘方案，由CloudStack管理员定义，针对主数据存储提供磁盘大小和IOPS(QOS)等选项供选择。可参阅创建新的磁盘方案。"
+
+# c00720676a8a4c4a9d423dd5f5743f4c
+#: ../../administration.rst:48
+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 "网络方案，由 CloudStack 管理员定义，约定来宾网络中虚拟路由器或外部网络设备提供给终端用户可用的功能描述集。"
+
+# 169ad751a60e44929103a91c102ac2a2
+#: ../../administration.rst:53
+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 "模版，由CloudStack管理员或其他CloudStack用户定义，用户创建新的实例时可选择的基本操作系统镜像。例如，CloudStack中包含的CentOS模版。可参阅使用模版。"
+
+# 81b027ebc2094409b6f28288660792c7
+#: ../../administration.rst:58
+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 "除了给用户提供了这些选择，还有另一种类型的服务方案只提供给CloudStack管理员，用于配置虚拟基础设施资源。欲了解更多信息，请参阅使用系统服务方案升级虚拟路由器。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/api.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/api.mo
new file mode 100644
index 0000000..c4abbf3
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/api.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/api.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/api.po
new file mode 100644
index 0000000..8140b94
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/api.po
@@ -0,0 +1,154 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:04+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 7499b008b97e41b59d4cdc3835758f36
+#: ../../api.rst:18
+msgid "CloudStack API"
+msgstr "CloudStack API"
+
+# 7a40beffc6484f108ad5202cb2a4e7c3
+#: ../../api.rst:20
+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 "CloudStack API 是可以被用来实现CloudStack Web UI的底层API。这是良好的基础使其提供比如EC2和S3和新兴的DMTF标准等受欢迎的API。"
+
+# 0e4247f81b8a4a83afa84f323d2697b9
+#: ../../api.rst:24
+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 "大多CloudStack的API调用都是异步的. 在调用时它们将立即返回一个任务ID。这个任务ID稍后可以用于查询任务状态。此外，状态调用会在资源受影响时提供一些状态指示。"
+
+# dc0b3fef72b74085a24d7e0c15cb227d
+#: ../../api.rst:29
+msgid ""
+"The API has a REST-like query basis and returns results in XML or JSON."
+msgstr "API基于类似REST的查询, 可以返回XML或JSON格式."
+
+# 1f57015e966c480795b141ba3f87b86a
+#: ../../api.rst:31
+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 "参阅 `开发指南 <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Development+101>`_ 和 `参考API <http://cloudstack.apache.org/docs/api/>`_."
+
+# de3d35bb699f45f495251ceb69a2c238
+#: ../../api.rst:36
+msgid "Provisioning and Authentication API"
+msgstr "配置和认证API"
+
+# c8eb593d2c654d8db8d5ce7791bedd07
+#: ../../api.rst:38
+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 "CloudStack期望客户都会有自己的用户提供基础设施。它提供的API可与这些现有系统集成，通过外部调用CloudStack添加/删除用户。"
+
+# f37cbbabb4af4c76977b51277f5cefa3
+#: ../../api.rst:42
+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 "CloudStack支持插件类型的身份验证. 默认情况下, CloudStack假定自身提供用户密码，作为本地的验证方式. 但也可以使用外部验证。 例如, 参阅使用LDAP服务器进行用户验证。"
+
+# a1cd31f63e9a4fe6869e80cdd8f2274f
+#: ../../api.rst:50
+msgid "User Data and Meta Data"
+msgstr "用户数据和元数据"
+
+# 8adea5c3508040cfb6f8475bc1f2f96c
+#: ../../api.rst:52
+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 "CloudStack提供的API访问在部署VM时可附加多达32KB的用户数据。部署虚拟机也可以通过虚拟路由器访问实例的元数据。"
+
+# 11a9a59d3f23401d8c639b7767af0a94
+#: ../../api.rst:56
+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 "一旦得知虚拟路由的IP便可以访问用户数据。得到IP地址后使用如下步骤访问用户数据："
+
+# 0b14bfd2cf6c41a98f39a406fdb83868
+#: ../../api.rst:60
+msgid "Run the following command to find the virtual router."
+msgstr "执行如下命令查找虚拟路由器。"
+
+# e0144a29051543d1aba1d5b18d18e033
+#: ../../api.rst:66
+msgid ""
+"Access user data by running the following command using the result of the "
+"above command"
+msgstr "通过上述命令的结果运行如下命令访问用户数据"
+
+# 8ebc1946ef8840c4b4c99d6194576997
+#: ../../api.rst:73
+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 "元数据同样可以被访问，使用URL表单 http://10.1.1.1/latest/meta-data/{元数据类型} 。 (为了向后兼容，之前的URL也同样支持 http://10.1.1.1/latest/{元数据类型} 。) 关于元数据类型，请使用以下方法之一："
+
+# bed0120874a643b1b9d59bd6a4e9e404
+#: ../../api.rst:78
+msgid "service-offering. A description of the VMs service offering"
+msgstr "service-offering。VM服务方案的描述。"
+
+# 71b8d766955140c3b512c2a9318fa115
+#: ../../api.rst:80
+msgid "availability-zone. The Zone name"
+msgstr "availability-zone。区域名称"
+
+# 2a80730691bb49e0b69de28d14feea03
+#: ../../api.rst:82
+msgid "local-ipv4. The guest IP of the VM"
+msgstr "local-ipv4。VM的来宾地址"
+
+# 6f5c73e35f714f0f83b7c799a46c499f
+#: ../../api.rst:84
+msgid "local-hostname. The hostname of the VM"
+msgstr "local-hostname。VM的主机名"
+
+# ad4c5b53b2844aa9b7518ea0165e3c5a
+#: ../../api.rst:86
+msgid ""
+"public-ipv4. The first public IP for the router. (E.g. the first IP of eth2)"
+msgstr "public-ipv4。第一个IP为路由器的IP。 (E.g. eth2为第一个IP)"
+
+# 53db659838e1499c86e3674db658bbdb
+#: ../../api.rst:89
+msgid "public-hostname. This is the same as public-ipv4"
+msgstr "public-hostname。与public-ipv4相同"
+
+# 760946f739514ea5be9f4c114716b1ba
+#: ../../api.rst:91
+msgid "instance-id. The instance name of the VM"
+msgstr "instance-id。VM实例的名称"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/events.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/events.mo
new file mode 100644
index 0000000..76198e6
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/events.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/events.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/events.po
new file mode 100644
index 0000000..26aa1ff
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/events.po
@@ -0,0 +1,411 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:04+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 0defb3a9608c4824b34ed35d916fd0c4
+#: ../../events.rst:18
+msgid "Event Notification"
+msgstr "事件通知"
+
+# 37ebc4e9b0b148daaab42c65d71cc834
+#: ../../events.rst:20
+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 "事件本质上是与云环境相关的虚拟和物理资源的状态显著或有意义的变化。事件用于监控系统，使用率和计费系统，或者是用于辨别模式和做出正确商业决定的其他任何事件驱动工作流系统。在 CloudStack 中的事件可以是虚拟或物理资源的状态变化，用户（操作事件）执行的操作，或基于策略的事件（警告）。"
+
+# 82bc7c30085140f89344da554ad386a3
+#: ../../events.rst:30
+msgid "Event Logs"
+msgstr "事件日志"
+
+# c1d54e6d1a2d4cd6888ad99bf943ed83
+#: ../../events.rst:32
+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 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.."
+msgstr "这里有两种类型的事件记录在&PRODUCT;事件日志。标准事件记录一个事件的成功或失败，并且可以用于鉴别哪些是已经失败的任务或进程。这里也记录长时间运行任务事件。异步任务的制定，启动，完成这些事件都被记录。长时间运行的同步和异步事件日志可用于获取挂起任务更多的状态信息，也可以用来识别任务是被挂起或还未开始。以下各节提供有关这些事件的详细信息。"
+
+# 127295678f0c4cf084cf737444f11087
+#: ../../events.rst:45
+msgid "Notification"
+msgstr "通知"
+
+# a669e3079b7e41d1a82dd149bf00b011
+#: ../../events.rst:47
+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 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."
+msgstr "事件通知框架提供一种手段来管理管理服务器组件来发布和订阅 CloudStack 中的事件。事件通知是通过实现事件总线抽象的管理服务器的概念来实现。事件总线的管理服务器，允许 CloudStack 中的组件和扩展插件通过使用高级消息队列协议（AMQP）客户端订阅事件的介绍。在 CloudStack 中，事件总线默认通过一个使用Rabbit MQAMQP 客户端 的插件实现。AMQP 客户端推送发布事件到兼容 AMQP 服务器。因此，所有的 CloudStack 中的事件发布到 AMQP 服务器中交换 。"
+
+# e41f3e4f6450467da27fc6dc4ebb2788
+#: ../../events.rst:59
+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, action events, usage events) and the "
+"additional category of resource state change events, are published on to the"
+" events bus."
+msgstr "状态变化，资源状态变化的新事件作为事件通知架构的一部分被引入。每个资源，例如用户VM，卷VM，网卡，网络，公共IP，快照以及模板，使用机器状态和常规事件被关联起来作为状态变化的一部分。这意味着，一个资源状态的变化产生了一个状态变化事件，并且该事件被公布到相应的状态事件总线。所有的 CloudStack 事件（报警，动作事件，使用事件）和 资源状态变化事件的附加条目将被公布到事件总线。"
+
+# 4aaf02080d184ab387923b45f39d5762
+#: ../../events.rst:71
+msgid "Use Cases"
+msgstr "使用案例"
+
+# f7b5a1de0f014d2eabfe925d0c5c4e95
+#: ../../events.rst:73
+msgid "The following are some of the use cases:"
+msgstr "以下是一些使用场景："
+
+# 9be82bc2fe244fef9851d9adb481fdaf
+#: ../../events.rst:75
+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 "使用率或计费引擎：第三方云使用的解决方案可以实现一个插件，它可以连接到 CloudStack 中订阅 CloudStack 中的事件并产生使用率数据。使用率数据是它们的使用的软件消耗。"
+
+# 2585685666874f3f8795c70fe2671356
+#: ../../events.rst:80
+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 "AMQP的插件可以存放消息队列中的所有事件，然后一个AMQP消息代理可以提供基于主题的通知订阅者。"
+
+# ff10e0227bc04e2f86f15c3c534b7c47
+#: ../../events.rst:84
+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 "AMQP的插件可以存放所有事件在一个消息队列中，然后AMQP打乱的\n发布和订阅通知服务可以作为一个可插拔的服务，在CloudStack中该服务可以为事件通知提供丰富的API集，如主题为标题的主题和通知。此外，可插拔服务可以处理多租户，认证，授权issues.age代理，并提供基于主题的订阅通知。"
+
+# bdc9ac2f935c456fbd3778ddef6c91cf
+#: ../../events.rst:92
+msgid "Configuration"
+msgstr "配置"
+
+# c2514aa04f964044bd2bd630f31b4d3f
+#: ../../events.rst:94
+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 "作为一个 CloudStack 管理员，执行下列一次性配置启用事件通知框架。在运行时不能修改控件行为。"
+
+# e94d4200515d4f15adbc52ca3bbf8c54
+#: ../../events.rst:98
+msgid "Open ``'componentContext.xml``."
+msgstr "打开 `` componentContext.xml ``."
+
+# e2bbf37abe854d6cb8384bdd3c9d72b9
+#: ../../events.rst:100
+msgid "Define a bean named ``eventNotificationBus`` as follows:"
+msgstr "按照以下实例顶一个叫做 “ eventNotificationBus ” 的实体： "
+
+# 47bce54d52714df7bafac2b6d04dd816
+#: ../../events.rst:102
+msgid "name : Specify a name for the bean."
+msgstr "名字：为实体指定一个名字。"
+
+# 4317cb3aa0fd4c7fa3f0e637f6cfea48
+#: ../../events.rst:104
+msgid "server : The name or the IP address of the RabbitMQ AMQP server."
+msgstr "服务器： RabbitMQ AMQP 的名字或IP地址"
+
+# 0f6561172d38446db99181316f50e667
+#: ../../events.rst:106
+msgid "port : The port on which RabbitMQ server is running."
+msgstr "端口 : RabbitMQ服务器运行端口."
+
+# 7ff0aa3ff7af48fbbf4651a2d8e5f34d
+#: ../../events.rst:108
+msgid ""
+"username : The username associated with the account to access the RabbitMQ "
+"server."
+msgstr "用户名： 用户名关联访问 RabbitMQ 服务器的账号。"
+
+# 7193c434eaab44eda2d7d9b2b86c675d
+#: ../../events.rst:111
+msgid ""
+"password : The password associated with the username of the account to "
+"access the RabbitMQ server."
+msgstr "密码： 密码关联访问 RabbitMQ 服务器账号的用户名。"
+
+# f765ea7d69504610a98a95fdb802fe32
+#: ../../events.rst:114
+msgid ""
+"exchange : The exchange name on the RabbitMQ server where CloudStack events "
+"are published."
+msgstr "交流：其中 CloudStack 中事件发布的 RabbitMQ 的服务器上的交流名称。"
+
+# 7ba933b1d4ec41c1a20f2cdca4275405
+#: ../../events.rst:117
+msgid "A sample bean is given below:"
+msgstr "下面给出一个实体实例："
+
+# 07a04a0f79804e938092a93f3180770a
+#: ../../events.rst:130
+msgid ""
+"The ``eventNotificationBus`` bean represents the "
+"``org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus`` class."
+msgstr " `` eventNotificationBus `` 表示 ` `org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus `` 类"
+
+# 83cdf82ae8c34a238d181c5bbaef30dd
+#: ../../events.rst:133
+msgid "Restart the Management Server."
+msgstr "重启管理服务器。"
+
+# 573b41c4def247f6981e828da7f54f82
+#: ../../events.rst:137
+msgid "Standard Events"
+msgstr "标准事件"
+
+# f503981d0a764de49d4acc01c70d6126
+# 9212f9cd71b542899ac8256d4a51026d
+#: ../../events.rst:139 ../../events.rst:161
+msgid "The events log records three types of standard events."
+msgstr "事件日志记录三种类型的标准事件"
+
+# fab87560ba674752808dacaf3abfc44a
+# 94b40a1c0c98456399293f6a38102385
+#: ../../events.rst:141 ../../events.rst:163
+msgid ""
+"INFO. This event is generated when an operation has been successfully "
+"performed."
+msgstr "通知：当一个操作被成功执行产生事件。"
+
+# 49450fc963104f569e80611ac7179829
+# 13438410decf4526b0381dc44062ba76
+#: ../../events.rst:144 ../../events.rst:166
+msgid "WARN. This event is generated in the following circumstances."
+msgstr "警告：以下状况产生该事件。"
+
+# c6197efc809f4a67baf05aa139cb10f5
+# a16599807269441f8f1799ae29968e11
+#: ../../events.rst:146 ../../events.rst:168
+msgid "When a network is disconnected while monitoring a template download."
+msgstr "监控模板下载的同时网络被断开"
+
+# 0e060afef9e84640b3c2da38436691e2
+# 019e604962174d4492cca7be02ad2647
+#: ../../events.rst:149 ../../events.rst:171
+msgid "When a template download is abandoned."
+msgstr "模板下载被放弃"
+
+# 8b3eabd5fcc0406bb83abe3863261df9
+# 19ccb6eebbc1446a8cb47056d2ad0274
+#: ../../events.rst:151 ../../events.rst:173
+msgid ""
+"When an issue on the storage server causes the volumes to fail over to the "
+"mirror storage server."
+msgstr "当存储服务器上的问题会导致卷故障转移到镜像存储服务器。"
+
+# 96793fba6d294c98bd8dcde72d0d9f49
+# 0b487b0c814145438366a847c93c52d8
+#: ../../events.rst:154 ../../events.rst:176
+msgid ""
+"ERROR. This event is generated when an operation has not been successfully "
+"performed"
+msgstr "错误：当操作没有成功执行产生该事件"
+
+# b1c1824ddd304288bd0803e80d482bb9
+#: ../../events.rst:159
+msgid "Long Running Job Events"
+msgstr "长事件运行任务事件"
+
+# ffb5ee0896674a62a567e634fc725510
+#: ../../events.rst:181
+msgid "Event Log Queries"
+msgstr "事件记录查询"
+
+# 0c75a642e72943e0bb28642902590c9b
+#: ../../events.rst:183
+msgid ""
+"Database logs can be queried from the user interface. The list of events "
+"captured by the system includes:"
+msgstr "可以通过用户接口查询数据库日志。系统收集了以下列表事件："
+
+# fe735d1b0444472aa47e381cd00eec61
+#: ../../events.rst:186
+msgid "Virtual machine creation, deletion, and on-going management operations"
+msgstr "虚拟机创建，删除，以及持续管理操作"
+
+# e331126149b64023bf0e7655bbcb2991
+#: ../../events.rst:189
+msgid "Virtual router creation, deletion, and on-going management operations"
+msgstr "虚拟路由器创建，删除，以及持续管理操作"
+
+# 33b99484fca246c48ceff95aac8b52d2
+#: ../../events.rst:191
+msgid "Template creation and deletion"
+msgstr "模板创建和删除"
+
+# 7969071933104816945f05e9f3a597e3
+#: ../../events.rst:193
+msgid "Network/load balancer rules creation and deletion"
+msgstr "网络/压力 负载规则创建和删除"
+
+# 91ecfa5192134ffeafe5043cff29432a
+#: ../../events.rst:195
+msgid "Storage volume creation and deletion"
+msgstr "存储卷创建和和删除"
+
+# b0c0672f35af4003870943a16b461337
+#: ../../events.rst:197
+msgid "User login and logout"
+msgstr "用户登录注销"
+
+# 57cfb09e85c842b581f3a0f38609a9c4
+#: ../../events.rst:201
+msgid "Deleting and Archiving Events and Alerts"
+msgstr "删除和归档事件警告"
+
+# b4160055fbd946979df299cf40a75777
+#: ../../events.rst:203
+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 "CloudStack 提供你删除或归档那些再也不使用的现存警告和事件的能力。您可以定期删除或存档的任何那些您不能或不想从数据库来解决的警报或事件，"
+
+# 7bdab572982c4739808182e94b589c7e
+#: ../../events.rst:208
+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 archived or deleted."
+msgstr "您可以通过快速查看或详情页面直接删除或归档个别警报或事件。如果你想同时删除多个警报或事件，您可以分别使用相应的快捷菜单。您可以按类别删除某个时期的警报或事件。例如，您可以选择诸如 ** USER.LOGOUT**，** VM.DESTROY**，** VM.AG.UPDATE**，** CONFIGURATION.VALUE.EDI** 等类别，依此类推。您还可以查看事件和警报归档或删除的数量。"
+
+# cf46cdd4536a4a93912df2f4e88af8a1
+#: ../../events.rst:217
+msgid ""
+"In order to support the delete or archive alerts, the following global "
+"parameters have been added:"
+msgstr "为了支持删除或归档报警，增加了以下全局参数："
+
+# 19ff2e090cf24d30aeacde33ec972af1
+#: ../../events.rst:220
+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 " **alert.purge.delay** : 指定报警大于多少天被销毁。设置值为0将永不自动销毁"
+
+# e3ccfdc51da14488bc9e44623c64d707
+#: ../../events.rst:223
+msgid ""
+"**alert.purge.interval**: The interval in seconds to wait before running the"
+" alert purge thread. The default is 86400 seconds (one day)."
+msgstr " **alert.purge.interval** : 执行销毁线程后等待间隔秒数. 默认值是86400秒 ( 1天 )."
+
+# a6eda71ad15940c2b58724ff74f97e26
+#: ../../events.rst:228
+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 "不能同通过UI 或 API 来归档报警或者事件。它们都存放在数据库中用于升级或其他目的。"
+
+# 7c40293965f24130896768ea8223a152
+#: ../../events.rst:234
+msgid "Permissions"
+msgstr "许可"
+
+# e43e679e6a304ae1b78e11f56bed12b2
+#: ../../events.rst:236
+msgid "Consider the following:"
+msgstr "参考以下几点："
+
+# c5bd820d9a5e487b9440609da1e22551
+#: ../../events.rst:238
+msgid "The root admin can delete or archive one or multiple alerts or events."
+msgstr "root 管理 可以删除或归档一个或多个警告事件"
+
+# 51b4fa6e53064c7088052c69d7a1b4fe
+#: ../../events.rst:241
+msgid ""
+"The domain admin or end user can delete or archive one or multiple events."
+msgstr "域关乎或终端用户可以删除或归档一个或多个警告事件"
+
+# bea2b3dcb4bb41468a31793133ffeb06
+#: ../../events.rst:246
+msgid "Procedure"
+msgstr "步骤"
+
+# aa16543921984837a7f59142ad2df67d
+#: ../../events.rst:248
+msgid "Log in as administrator to the CloudStack UI."
+msgstr "使用管理员登录到CloudStack管理界面。"
+
+# f8b2ec5bdbf749d2bf704ff20c063c89
+#: ../../events.rst:250
+msgid "In the left navigation, click Events."
+msgstr "在左侧导航栏中，点击事件。"
+
+# 5519a86ae5b04a68b972ee88e37deffe
+#: ../../events.rst:252
+msgid "Perform either of the following:"
+msgstr "请执行下列操作之一： "
+
+# fd1193e3ff83466aa226d4834dea269d
+#: ../../events.rst:254
+msgid ""
+"To archive events, click Archive Events, and specify event type and date."
+msgstr "归档事件，点击 归档事件，并指定事件类型和日期。"
+
+# abfda9e22c7f42f3a4ff488ff755e59e
+#: ../../events.rst:257
+msgid ""
+"To archive events, click Delete Events, and specify event type and date."
+msgstr "归档事件，点击 删除事件，并指定事件类型和日期。"
+
+# 58b630d17160410ab6757d134aa17a62
+#: ../../events.rst:260
+msgid "Click OK."
+msgstr "点击确定。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/hosts.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/hosts.mo
new file mode 100644
index 0000000..f9a0168
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/hosts.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/hosts.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/hosts.po
new file mode 100644
index 0000000..254e584
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/hosts.po
@@ -0,0 +1,1058 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:04+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# d162d1d06fd7403885aaa50b51be64cf
+#: ../../hosts.rst:18
+msgid "Working with Hosts"
+msgstr "使用主机"
+
+# 6c9e070451664a89a2bab7d9dcb4892e
+#: ../../hosts.rst:21
+msgid "Adding Hosts"
+msgstr "添加主机"
+
+# 0fea464db7a843f6930b135daf0f6eef
+#: ../../hosts.rst:23
+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 "添加主机能为来宾VMs提供更多的性能。更多需求与说明请参阅 `“添加主机” <http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/configuration.html#adding-a-host>`_。"
+
+# 8d309023c45240b78a9ddce49978e18c
+#: ../../hosts.rst:29
+msgid "Scheduled Maintenance and Maintenance Mode for Hosts"
+msgstr "主机的维护计划与维护模式"
+
+# 7a2b019ac10a47c39de133fdc1a06f3d
+#: ../../hosts.rst:31
+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 "你可以使一台主机进入维护模式。当激活维护模式时，这台主机将不会接纳新的来宾VMs，同时上面的VMs会无缝地迁移到其他非维护模式的主机上。这个迁移使用在线迁移技术并且不会中断用户的操作。"
+
+# af2fbe9bb8ff4ab29c19fbb7dc7d6a2b
+#: ../../hosts.rst:39
+msgid "vCenter and Maintenance Mode"
+msgstr "vCenter与维护模式"
+
+# d2d9b481634d47499c874f1781439746
+#: ../../hosts.rst:41
+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 "要使vCenter主机进入维护模式，vCenter和CloudStack上都必须进行此操作。CloudStack和vCenter有各自的维护模式，他们需要紧密合作。"
+
+# 1757e266dc494d81be5c3b51608b8507
+#: ../../hosts.rst:45
+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 "在CloudStack中，将主机进入\"维护计划\"模式。这个操作不会调用vCenter的维护模式，但是会将VMs迁离该主机。"
+
+# d96d3c3231d445ffbe5379d2f572a864
+#: ../../hosts.rst:49
+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 "当CloudStack维护模式启用后，主机首先会进入准备维护状态。在这个阶段它不能运行新的来宾VMs。然后所有的VMs将会被迁离该主机。主机使用在线迁移来迁移VMs。这种方式能够使来宾VMs在迁移到其他主机的过程中不会中断用户的操作。"
+
+# a0302fba3abb4768b9ea6456150d1e34
+#: ../../hosts.rst:57
+msgid "Wait for the \"Ready for Maintenance\" indicator to appear in the UI."
+msgstr "等\"准备好维护\"指示灯出现在UI中。"
+
+# bb2fe5471107450db78672f18f6c459b
+#: ../../hosts.rst:59
+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 "现在使用vCenter通过必要的步骤将主机进入维护模式。在此期间，主机不会运行新的VM。"
+
+# 465e081898184a07a0da7751a1b9540b
+#: ../../hosts.rst:63
+msgid ""
+"When the maintenance tasks are complete, take the host out of maintenance "
+"mode as follows:"
+msgstr "当维护任务完成之后，按以下操作将主机退出维护模式："
+
+# d513b1610d3f4e3c94c36672598225ef
+#: ../../hosts.rst:66
+msgid "First use vCenter to exit the vCenter maintenance mode."
+msgstr "首先通过vCenter退出vCenter维护模式。"
+
+# 20604374352a49e78c96fc359907798b
+#: ../../hosts.rst:68
+msgid "This makes the host ready for CloudStack to reactivate it."
+msgstr "这么做是为了主机能够准备好以便CloudStack恢复它。"
+
+# 268a4bfa21584498b9c29213e959d532
+#: ../../hosts.rst:70
+msgid ""
+"Then use CloudStack's administrator UI to cancel the CloudStack maintenance "
+"mode"
+msgstr "然后通过CloudStack的管理员UI来取消CloudStack维护模式"
+
+# 473e00df4c58462d9df612fdba5c4996
+#: ../../hosts.rst:73
+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 "当主机恢复正常，被迁移走的VMs可能需要手工迁移回来并且也能在主机上添加新的VMs了。"
+
+# 8026febd757948bdb38b4f85cbd4c425
+#: ../../hosts.rst:78
+msgid "XenServer and Maintenance Mode"
+msgstr "XenServer和维护模式"
+
+# 38555be75efd4fed91c3479a883493d1
+#: ../../hosts.rst:80
+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 "对于XenServer，你能够通过使用XenCenter中的维护模式功能将一台服务器临时的离线。当你使一台服务器进入维护模式，所有运行的VMs都会自动的迁移到同一个池中的其他主机上。如果此服务器是池master主机，那么此池会选举一个新的master主机。当一台服务器在维护模式下时，你不能在上面创建或启动任何VMs。"
+
+# 456e5e6e17bf41909c0b487227d097cd
+#: ../../hosts.rst:87
+msgid "**To place a server in Maintenance Mode:**"
+msgstr "**使一台服务器进入维护模式：**"
+
+# 5de27d0060754518bf21cd3ed27ed05a
+# 568c45e59b4f4b2294d24752311a5022
+#: ../../hosts.rst:89 ../../hosts.rst:104
+msgid ""
+"In the Resources pane, select the server, then do one of the following:"
+msgstr "在资源面板，选择服务器，然后按下列步骤进行操作："
+
+# a31b8242b89b4b24a48e8d242ed46718
+#: ../../hosts.rst:92
+msgid "Right-click, then click Enter Maintenance Mode on the shortcut menu."
+msgstr "右击，然后在弹出的快捷菜单中点击进入维护模式。"
+
+# 1e90893580c44442be56fd686ba4aab4
+#: ../../hosts.rst:95
+msgid "On the Server menu, click Enter Maintenance Mode."
+msgstr "在服务器菜单，点击进入维护模式。"
+
+# 95cf013b55004f2486b693b9a9bdb52d
+#: ../../hosts.rst:97
+msgid "Click Enter Maintenance Mode."
+msgstr "点击进入维护模式。"
+
+# e9120c5408d94ba89b65157b49de36ae
+#: ../../hosts.rst:99
+msgid ""
+"The server's status in the Resources pane shows when all running VMs have "
+"been successfully migrated off the server."
+msgstr "当所有运行当中的VMs成功的迁离该主机后，在资源面板中会显示服务器的状态。"
+
+# c8ae2b6b96814aa8a04dc2ceebbacabb
+#: ../../hosts.rst:102
+msgid "**To take a server out of Maintenance Mode:**"
+msgstr "**使服务器退出维护模式：**"
+
+# ae539b7f53ce42e8b161a38c897302a8
+#: ../../hosts.rst:107
+msgid "Right-click, then click Exit Maintenance Mode on the shortcut menu."
+msgstr "右击，然后在弹出的快捷菜单中点击退出维护模式。"
+
+# ee115cfaf80446f49c0e9fae828c783e
+#: ../../hosts.rst:110
+msgid "On the Server menu, click Exit Maintenance Mode."
+msgstr "在服务器菜单，点击提出维护模式。"
+
+# 7edbfea17cdb4c4a85766a3d46ccf8da
+#: ../../hosts.rst:112
+msgid "Click Exit Maintenance Mode."
+msgstr "点击退出维护模式。"
+
+# e6edc76480294c5faf6518aaf5f6aacb
+#: ../../hosts.rst:116
+msgid "Disabling and Enabling Zones, Pods, and Clusters"
+msgstr "禁用和启用Zones，Pods和Clusters"
+
+# 144624e6273f4b5c94ed3f88c8fc95e3
+#: ../../hosts.rst:118
+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 "你可以启用或禁用一个zone，pod或者cluster而不用永久的从云中移除他们。这对于维护或者当云中一部分架构的可靠性有问题的时候很有用。禁用状态下的zone，pod或cluster不会接受新的分配，除非其状态变为启用。当一个zone，pod或cluster是初次添加到云中的，默认的情况下它是禁用的。"
+
+# 9fbfab10c6be45a3bd2f6c231c6737bb
+#: ../../hosts.rst:125
+msgid "To disable and enable a zone, pod, or cluster:"
+msgstr "要禁用和启用一个zone，pod或者cluster："
+
+# 71e22a46ce644865b910006aaa048a8d
+#: ../../hosts.rst:127
+msgid "Log in to the CloudStack UI as administrator"
+msgstr "使用管理员权限的账号登录到CloudStack"
+
+# 50c0cd124fa643fdbbc561152e0dbabf
+# e16a19456eb441b4ab3cf57ec846a391
+#: ../../hosts.rst:129 ../../hosts.rst:404
+msgid "In the left navigation bar, click Infrastructure."
+msgstr "在左侧导航栏中，点击基础架构"
+
+# 11fd25d319484ab2b87f09c842be5134
+#: ../../hosts.rst:131
+msgid "In Zones, click View More."
+msgstr "点击区域中的查看更多。"
+
+# c9caf60acf104601bc0f0f946d22b0c5
+#: ../../hosts.rst:133
+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 "如果你要禁用或启用一个zone，请在列表里找到zone的名称，然后点击启用/禁用按钮。|enable-disable.png|"
+
+# 222f496a2d1e456589a79442f4ed34a5
+#: ../../hosts.rst:136
+msgid ""
+"If you are disabling or enabling a pod or cluster, click the name of the "
+"zone that contains the pod or cluster."
+msgstr "如果你要禁用或启用一个pod或者cluster，点击包含该pod或cluster的zone名称。"
+
+# 8de91492f6c848dca361c3822956148a
+#: ../../hosts.rst:139
+msgid "Click the Compute tab."
+msgstr "点击计算这个标签。"
+
+# 260854995dc747e8b0224b78525f9646
+#: ../../hosts.rst:141
+msgid "In the Pods or Clusters node of the diagram, click View All."
+msgstr "在示意图中的Pods或者Clusters节点，点击查看所有。"
+
+# 5496ff56c1c74d689c2d2453c38b4708
+#: ../../hosts.rst:143
+msgid "Click the pod or cluster name in the list."
+msgstr "点击列表中的pod或者cluster名称。"
+
+# 893e62d5abbf47a38a0dd2c1a53d6a5a
+#: ../../hosts.rst:145
+msgid "Click the Enable/Disable button. |enable-disable.png|"
+msgstr "点击启用/禁用按钮。|enable-disable.png|"
+
+# 8f3d3ce8e0c64e67aea7a02d485fb245
+#: ../../hosts.rst:149
+msgid "Removing Hosts"
+msgstr "移除主机"
+
+# 984b62f5ee574b5fa2921a9c51086739
+#: ../../hosts.rst:151
+msgid ""
+"Hosts can be removed from the cloud as needed. The procedure to remove a "
+"host depends on the hypervisor type."
+msgstr "主机在需要的时候可以被移除。这个过程取决于主机所使用的hypervisor类型。"
+
+# 65240cc22f554f09bdc03200b95bd05d
+#: ../../hosts.rst:156
+msgid "Removing XenServer and KVM Hosts"
+msgstr "移除XenServer和KVM主机"
+
+# 879cec7da3564798aa9e0d864809678d
+#: ../../hosts.rst:158
+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 "cluster中的主机只有进入维护模式才能被移除。这么做是为了确保其上所有的VMs被迁移至其他主机。要从云中移除一个主机："
+
+# 7b965bf8884a4bcba98b12aab945722c
+#: ../../hosts.rst:162
+msgid "Place the node in maintenance mode."
+msgstr "将主机进入维护模式。"
+
+# 1301a77070374e238eb438818854da08
+#: ../../hosts.rst:164
+msgid ""
+"See `“Scheduled Maintenance and Maintenance Mode for Hosts” <#scheduled-"
+"maintenance-and-maintenance-mode-for-hosts>`_."
+msgstr "请参考`“主机的维护计划与维护模式” <#scheduled-maintenance-and-maintenance-mode-for-hosts>`_."
+
+# 6cb63d9356e643f1b3e032a8056a89ee
+#: ../../hosts.rst:167
+msgid "For KVM, stop the cloud-agent service."
+msgstr "对于KVM，停止cloud-agent服务。"
+
+# 3a90c7e2a9224f36b01d73a1df4cd39c
+#: ../../hosts.rst:169
+msgid "Use the UI option to remove the node."
+msgstr "使用UI选项来移除主机。"
+
+# 400a182ceace4cef87ffe6c731ea45cd
+#: ../../hosts.rst:171
+msgid ""
+"Then you may power down the Host, re-use its IP address, re-install it, etc"
+msgstr "然后你可以关掉主机，重用它的IP地址，重新安装系统，等等。"
+
+# b9297a05564a41f8aa6995f8f1e2265a
+#: ../../hosts.rst:176
+msgid "Removing vSphere Hosts"
+msgstr "移除vSphere主机"
+
+# c32ebbedc8304707ab76b57248d80fee
+#: ../../hosts.rst:178
+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 "要移除此类型的主机，首先按照 `“主机的维护计划与维护模式” <#scheduled-maintenance-and-maintenance-mode-for-hosts>`_中的描述将其进入维护模式。然后使用CloudStack来移除主机。使用CloudStack移除主机时，CloudStack不会直接操作主机。但是，主机可能仍然存留在vCenter群集中。"
+
+# dd4d1c612fb44dc195061dd566beec5e
+#: ../../hosts.rst:187
+msgid "Re-Installing Hosts"
+msgstr "重新安装主机"
+
+# 0ee9288a566b4631b2e8f680cfbe5b47
+#: ../../hosts.rst:189
+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 "你可以在将主机进入维护模式并移除它之后重新安装系统。如果主机是宕机状态而不能进入维护模式，在重装它之前仍然能被移除。"
+
+# c85fb73c99e34c10b3289143d58b305b
+#: ../../hosts.rst:195
+msgid "Maintaining Hypervisors on Hosts"
+msgstr "在主机上维护Hypervisors"
+
+# af548f5aa95e4755a881574a77d625fd
+#: ../../hosts.rst:197
+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 support any system that is not up "
+"to date with patches."
+msgstr "当主机上运行了hypervisor软件，请确保安装了供应商提供的所有修补程序。请通过供应商跟踪虚拟化平台的补丁发布情况，一旦发布，请尽快打上补丁。CloudStack不会跟踪或通知您所需要的虚拟化平台补丁。您的主机及时打上最新虚拟化平台补丁是非常重要的。虚拟化平台厂商很可能会拒绝支持未打最新补丁的系统。"
+
+# fb13ff2e1e1c478e8ee99dbb7a71c69d
+#: ../../hosts.rst:207
+msgid ""
+"The lack of up-do-date hotfixes can lead to data corruption and lost VMs."
+msgstr "缺乏最新补丁更新可能会导致数据和虚拟机丢失。"
+
+# 0132d3f953a446e7af2712c1f7f204d9
+#: ../../hosts.rst:209
+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 "（XenServer）更多信息，请参考`CloudStack知识库中高度推荐的XenServer修补程序 <http://docs.cloudstack.org/Knowledge_Base/Possible_VM_corruption_if_XenServer_Hotfix_is_not_Applied/Highly_Recommended_Hotfixes_for_XenServer_5.6_SP2>`_."
+
+# a2b8576f632f48e8b6556fe7958a2b4e
+#: ../../hosts.rst:215
+msgid "Changing Host Password"
+msgstr "更改主机密码"
+
+# 026b9758a8234d5d82e1fd3c20d9f9d6
+#: ../../hosts.rst:217
+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 "数据库中的XenServer主机，KVM主机或者vShpere主机密码可能会被变更。注意群集中的所有节点密码必须一致。"
+
+# d662651348254d968559ee61ec677c9d
+#: ../../hosts.rst:221
+msgid "To change a Node's password:"
+msgstr "用户名和密码要更改一台主机的密码："
+
+# eac8c72d0110440e8d47f458d4dfa691
+#: ../../hosts.rst:223
+msgid "Identify all hosts in the cluster."
+msgstr "让群集中所有的主机状态保持一致。"
+
+# 6c429aa99fc44f4e85ed4eda61090335
+#: ../../hosts.rst:225
+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 "更改群集中所有主机的密码。此刻主机上的密码与CloudStack已知的密码不一致。两个密码不一致的话会导致群集上的操作失败。"
+
+# bd29f4605f0b40a9822294fd0cba68e4
+#: ../../hosts.rst:229
+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 "获取群集中你更改了密码的主机ID列表。你必须访问数据库来获取这些ID。为每个你要更改密码的主机名（或者vSphere群集） \"h\"，执行："
+
+# ae93d4bde54f48ef9b96126a36220883
+#: ../../hosts.rst:238
+msgid ""
+"This should return a single ID. Record the set of such IDs for these hosts."
+msgstr "这条命令将会返回一个ID。记录这些主机的ID。"
+
+# 6e33a985c6204813a3beec13959e029a
+#: ../../hosts.rst:241
+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 "在数据库中为这些主机更新密码。在这个例子中，我们将主机ID为5,10和12的密码更改为\"password\"。"
+
+# 36d8dc7ed9b3447a819222bfb445bd10
+#: ../../hosts.rst:251
+msgid "Over-Provisioning and Service Offering Limits"
+msgstr "超配和服务方案限制"
+
+# 3e5ec1fcb0cf49fda1383c022d23de87
+#: ../../hosts.rst:253
+msgid "(Supported for XenServer, KVM, and VMware)"
+msgstr "（支持XenServer、KVM和VMware）"
+
+# 3633dc63fade45ad8b1bc222bb9ad425
+#: ../../hosts.rst:255
+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 "CPU和内存（RAM）超配直接影响每个群集中主机上可以运行的VMs数量。这样可以帮助优化资源的使用。依靠增加超配比率，能使使资源更充分的被利用。如果比率设为1，那么表示没有使用超配。"
+
+# 43467fc7868049cab2d4374ff0094af1
+#: ../../hosts.rst:261
+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 "管理员也可以在cpu.overprovisioning.factor和mem.overprovisioning.factor这两个全局配置变量中设置全局默认超配比率。默认的值是1：默认情况下超配是关闭的。"
+
+# 253e39db71ed47619ec617fb7a5397ac
+#: ../../hosts.rst:266
+msgid ""
+"Over-provisioning ratios are dynamically substituted in CloudStack's "
+"capacity calculations. For example:"
+msgstr "超配比率是由CloudStack的容量计算器动态调整的。比如："
+
+# 48cbfebf2e804785ba7f9631cb010778
+#: ../../hosts.rst:269
+msgid ""
+"Capacity = 2 GB Over-provisioning factor = 2 Capacity after over-"
+"provisioning = 4 GB"
+msgstr "容量=2GB 超配系数=2 超配后容量=4GB"
+
+# af111e47b7cc4e53825770d523defc61
+#: ../../hosts.rst:273
+msgid "With this configuration, suppose you deploy 3 VMs of 1 GB each:"
+msgstr "按照这个配置，假设你部署了3个VMs，每个VM 1GB："
+
+# 851386252faa45d69618b89e2ff7ba8e
+#: ../../hosts.rst:275
+msgid "Used = 3 GB Free = 1 GB"
+msgstr "已使用=3GB 空闲=1GB"
+
+# fdd299fb9bed44d696ed49d97cd8779d
+#: ../../hosts.rst:278
+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 "管理员可以在每个群集中指定一个内存超配比率，也可以同时指定CPU和内存超配比率。"
+
+# 13239c1da0164d2e88a9275d8083e8aa
+#: ../../hosts.rst:282
+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 the CloudStack placement "
+"algorithm decides to place a VM."
+msgstr "在任何已有的云中，hypervisor、存储和硬件配置影响每个主机上VMs最佳数量。同一个云中的每个群集的这些配置可能都不同。单一的全局超配设置不能为云中所有的群集提供最佳效果。它只能作为一个基线。无论CloudStack使用哪种算法来放置一个VM，每个群集都提供了细颗粒度的设置以提供更好的资源效果。"
+
+# 14bb9814011f4bb6972aeb18939b2e6c
+#: ../../hosts.rst:291
+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 "超配设置和专用资源（对一个账号分配一个特定的群集）一起使用时能对不同用户有效的提供的不同服务级别。比如，一个账号购买了比较高级别的服务，那么分配给他一个超配比率为1的专用群集，购买低级别服务的账号分配一个比率为2的群集。"
+
+# a04ae50db280409bacc1c0752456eb1b
+#: ../../hosts.rst:298
+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 "当一个新主机被添加到群集中，CloudStack假设配置了超配的群集中的主机能够提供CPU和RAM的超配能力。这个要靠管理员来决定主机是否真的能够提供设置的超配级别。"
+
+# bc9d355b0e014b5ab9fd367c9e80ab24
+#: ../../hosts.rst:306
+msgid "Limitations on Over-Provisioning in XenServer and KVM"
+msgstr "XenServer和KVM中超配的局限性"
+
+# c556b8018bbd4fee9f244adf40b4f51d
+# 536dc98cafb74355b90a4bea9be01f99
+#: ../../hosts.rst:308 ../../hosts.rst:416
+msgid ""
+"In XenServer, due to a constraint of this hypervisor, you can not use an "
+"over-provisioning factor greater than 4."
+msgstr "在XenServer中，由于这个hypervisor的限制，超配系数不能超过4。"
+
+# a9dd662370ca407596ca9fa0b313a3af
+#: ../../hosts.rst:311
+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 "KVM hypervisor不能动态的管理分配给VMs的内存。CloudStack设置VM能够使用的内存最小和最大量。Hypervisor基于存储器争用技术在设定范围内调整内存。"
+
+# 4eb1b9a8ad484a8fa8cb381ce6b52eb2
+#: ../../hosts.rst:318
+msgid "Requirements for Over-Provisioning"
+msgstr "存储超配的要求"
+
+# b5394f77c74e479980f2f996e9f81251
+#: ../../hosts.rst:320
+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 "为了让超配能够正常工作需要几个前提条件。此特性取决于OS类型，hypervisor功能和特定的脚本。管理员负责确认这些条件都符合。"
+
+# 4fc500a083b4403998ada5877b9d0de0
+#: ../../hosts.rst:327
+msgid "Balloon Driver"
+msgstr "Balloon驱动"
+
+# 9e1eb0f5b30a4a9cbebcf773c16bf440
+#: ../../hosts.rst:329
+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 "所有VMs中都安装了balloon驱动。Hypervisor靠balloon驱动与VM通讯以释放内存和让内存变得可用。"
+
+# 588dfd76655d44b999fcc554493271ee
+# 876a75ef59a549349b25f46f2f3fc8bf
+#: ../../hosts.rst:335 ../../hosts.rst:365
+msgid "XenServer"
+msgstr "XenServer"
+
+# cc2308bc95464b93a3dc5631c6edb411
+#: ../../hosts.rst:337
+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 "Balloon驱动是Xen pv或者PVHVM驱动的一部分。Linux kernels 2.6.36和以上版本中包含了Xen pvhvm驱动。"
+
+# db7f94775ac3401c8e7da496601ce4d7
+#: ../../hosts.rst:342
+msgid "VMware"
+msgstr "VMware"
+
+# db5f8890af6c435aa86e4c6106f0d83e
+#: ../../hosts.rst:344
+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 "Balloon驱动是VMware tools的一部分。在一台超配群集中部署的所有的VMs都应该安装VMware tools。"
+
+# e051f09fe032421881651a264ec5562c
+#: ../../hosts.rst:350
+msgid "KVM"
+msgstr "KVM"
+
+# 9c51a6068b774e919cd552b525963bef
+#: ../../hosts.rst:352
+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 "所有VMs都需要支持virtio驱动。Linux kernel versions 2.6.25和更高版本中已经安装了这些驱动。管理员必须在virtio的配置文件中配置CONFIG\\_VIRTIO\\_BALLOON=y。"
+
+# c8150c4e5af743bd8897bbd116c538d7
+#: ../../hosts.rst:359
+msgid "Hypervisor capabilities"
+msgstr "Hypervisor功能"
+
+# efc1f0769cdf44d0aee285aed27c7e0f
+#: ../../hosts.rst:361
+msgid "The hypervisor must be capable of using the memory ballooning."
+msgstr "Hypervisor必须能够使用内存ballooning。"
+
+# 8b282cb5f7914088be3b38b87b604492
+#: ../../hosts.rst:367
+msgid ""
+"The DMC (Dynamic Memory Control) capability of the hypervisor should be "
+"enabled. Only XenServer Advanced and above versions have this feature."
+msgstr "Hypervisor必须启用了DMC（动态内存控制）功能。只有XenServer高级版以及更高版本拥有这个功能。"
+
+# 11e7b221209c4b97ab044dbbb6c53b0e
+#: ../../hosts.rst:372
+msgid "VMware, KVM"
+msgstr "VMware、KVM"
+
+# c289bebec04c474c9497ce81216e04f1
+#: ../../hosts.rst:374
+msgid "Memory ballooning is supported by default."
+msgstr "默认支持内存ballooning。"
+
+# fd73c49bd922450fb7a771ebb8586d6d
+#: ../../hosts.rst:378
+msgid "Setting Over-Provisioning Ratios"
+msgstr "设置存储超配系数"
+
+# 7d8bbd43174f499a98270e1aad9301bd
+#: ../../hosts.rst:380
+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 "管理员有两种方法来设置CPU和RAM超配系数。第一，当新的群集被创建完成的时候全局配置中的cpu.overprovisioning.factor和mem.overprovisioning.factor将生效。第二，对于已存在的群集可以直接修改系数。 "
+
+# 6930197d999a4c1bb3e8bca13bb10c00
+#: ../../hosts.rst:386
+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 "只有在变更之后部署VMs，设置才会生效。如果想让变更之前部署的VMs也能继承新的超配比率，你必须重启VMs。当此操作完成之后，CloudStack会重新计算或者调整已使用的资源，并且基于新的超配比率预留出容量，以保证CloudStack正确的掌握了剩余容量的情况。"
+
+# fe4660151e234650980661b9975d4c77
+#: ../../hosts.rst:394
+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 "如果新的可用容量不足以满足新的VMs需求，那么当重新计算容量的过程中不去部署新的VMs是比较安全的。等新的已用/可用容量完全可用时，确认这空间对于你想创建的VMs足够用。"
+
+# 443b0ee66d0b40bdad6e11ac6c4eb123
+#: ../../hosts.rst:400
+msgid "To change the over-provisioning ratios for an existing cluster:"
+msgstr "在已存在的群集中更改超配系数："
+
+# b796b807352f4f8285fca177e9417577
+#: ../../hosts.rst:402
+msgid "Log in as administrator to the CloudStack UI."
+msgstr "使用管理员登录到CloudStack管理界面。"
+
+# 450e03bbb9974112bec16a0dca62c829
+#: ../../hosts.rst:406
+msgid "Under Clusters, click View All."
+msgstr "在群集页面，点击查看所有。"
+
+# dc9598fec6f74c74a82c2311ff962b5d
+#: ../../hosts.rst:408
+msgid "Select the cluster you want to work with, and click the Edit button."
+msgstr "选择你要操作的群集，点击编辑按钮。"
+
+# 4574765089c64df0a53ffd4b0d9052a0
+#: ../../hosts.rst:410
+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 "在CPU overcommit ratio和RAM overcommit ratio区域里填入你希望的超配系数。这里的初始值是从全局配置设置里继承而来的。"
+
+# 2652eabbfcd64f92bab0644f7cddd8d6
+#: ../../hosts.rst:421
+msgid "Service Offering Limits and Over-Provisioning"
+msgstr "服务方案限制和超配"
+
+# d88ad9813f6448ec9277039383ab3f86
+#: ../../hosts.rst:423
+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 "服务方案限制（比如1GHz，1 core）是受到core数严格限制的。比如，一个使用1 core服务方案的用户只能用 1core，无论这个主机多空闲。"
+
+# 0a5fa05e882e493f8d41201840eb0cd9
+#: ../../hosts.rst:428
+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 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."
+msgstr "GHz的服务方案限制只存在于CPU资源的争用中。比如，假设用户在一个有2GHz core的主机上创建了一个1 GHz的服务方案，并且该用户是这个主机上唯一一个用户。那么该用户有2 GHz可用性能。当多个用户尝试使用CPU，则由权重系数来调度CPU资源。这个权重基于服务方案中的时钟速度。用户分配到的CPU GHz与服务方案中一致。比如，用户从一个2GHz服务方案中创建的VM分配到的CPU是从1 GHz方案中分配到的2倍。CloudStack不能提供内存的超配。"
+
+# 86b75c2fbf034662ac3133fe63acefea
+#: ../../hosts.rst:442
+msgid "VLAN Provisioning"
+msgstr "VLAN供应"
+
+# 9d66a1eb7d4d4d88818d5d5d00bb285a
+#: ../../hosts.rst:444
+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 "CloudStack能在主机上自动创建和销毁桥接至VLAN的网络接口。一般来说，管理员不需要介入此处理过程。"
+
+# 7cfe38c7368a44d1b920f68fbb7e2b5e
+#: ../../hosts.rst:448
+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 "CloudStack根据hypervisor类型的不同，管理VLANs的方式也不同。对于XenServer或者KVM来说，只在使用VLANs的主机上创建VLANs，并且当所有使用VLANs的来宾虚机被销毁或者移动至其他主机的时候，这些VLANs就会被销毁。"
+
+# a681bdc643fc41a49688c3a833dce9ac
+#: ../../hosts.rst:453
+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 "vSphere上的VLANs是在群集中的所有主机上配置的，不管主机上有没有使用VLAN的来宾虚机在运行。这样允许管理员在vCenter中不需在目标主机上创建VLAN就可以执行在线迁移和其他功能。此外，当主机不再需要的时候VLANs也不会被移除。"
+
+# 162b7ae68b2d41db83c3bc6d32e86e6b
+#: ../../hosts.rst:460
+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 the same set of "
+"IPs for different customers, each one with their own routers and the guest "
+"networks on different physical NICs."
+msgstr "你能够使用由不同的拥有二层网络结构的物理网络提供同样的VLANs，比如交换机。比如，在对高级zone中部署物理网络A和B的时候，你可以指定VLAN范围为500-1000。如果你的VLANs用尽了，这个功能允许你在不同的物理网卡上设置追加一个二层物理网络并且使用同样的VLANs设置。另一个优点是你可以在不同的物理网卡上为不同的客户使用同样的IPs设置，每个都有自己的路由器和来宾网络。"
+
+# d4316f84d139424ab25c6fb9292b2840
+#: ../../hosts.rst:472
+msgid "VLAN Allocation Example"
+msgstr "VLAN分配示例"
+
+# ea6edc6b827c4791a53ea10997662dae
+#: ../../hosts.rst:474
+msgid ""
+"VLANs are required for public and guest traffic. The following is an example"
+" of a VLAN allocation scheme:"
+msgstr "公共和来宾流量要求使用VLAN，下面是一个VLAN分配的示例："
+
+# 558c3d372c85421390186a570da26dee
+#: ../../hosts.rst:478
+msgid "VLAN IDs"
+msgstr "VLAN IDs"
+
+# b6c7ef27f668454dbb5adb9a9c190c98
+#: ../../hosts.rst:478
+msgid "Traffic type"
+msgstr "流量类型"
+
+# 2dc30077851f4826beeaeb3c808e6452
+#: ../../hosts.rst:478
+msgid "Scope"
+msgstr "范围"
+
+# 46e966a312a047cfa77c7292aaba1fdb
+#: ../../hosts.rst:480
+msgid "less than 500"
+msgstr "小于500"
+
+# c6ffd280911a498f99904379cc538935
+#: ../../hosts.rst:480
+msgid "Management traffic."
+msgstr "管理流量。"
+
+# bb76ee312d884069ac0a101cfc2680d2
+#: ../../hosts.rst:480
+msgid ""
+"Reserved for administrative purposes. CloudStack software can access this, "
+"hypervisors, system VMs."
+msgstr "出于管理目的而预留的。CloudStack，hypervisors和系统虚机能访问它。"
+
+# 1307c25d94c447a08ebf7b1f47d76fa7
+#: ../../hosts.rst:481
+msgid "500-599"
+msgstr "500-599"
+
+# fb79eefe00ad444eaf660e4c6c7571b7
+#: ../../hosts.rst:481
+msgid "VLAN carrying public traffic."
+msgstr "承载公共流量。"
+
+# 0c7d0d0d68c94f5f889f1e32dcb564cb
+#: ../../hosts.rst:481
+msgid "CloudStack accounts."
+msgstr "CloudStack账户。"
+
+# 9ab975c827154ebd84ab2f50936736b8
+#: ../../hosts.rst:482
+msgid "600-799"
+msgstr "600-799"
+
+# e33f1854a40043ed9d323fa1f1a3519d
+# 1dfa7469eec44ea6b03b34b9c6f7504e
+#: ../../hosts.rst:482 ../../hosts.rst:483
+msgid "VLANs carrying guest traffic."
+msgstr "承载来宾流量"
+
+# e10058e68df14ced9dda12d02876f4c4
+#: ../../hosts.rst:482
+msgid "CloudStack accounts. Account-specific VLAN is chosen from this pool."
+msgstr "CloudStack 账户。 从这个池中选择账户特定的VLAN。"
+
+# 26028e0cc17c46ceae4008c85730b970
+#: ../../hosts.rst:483
+msgid "800-899"
+msgstr "800-899"
+
+# a894ab0d32654721aa09284c57bbabc4
+#: ../../hosts.rst:483
+msgid ""
+"CloudStack accounts. Account-specific VLAN chosen by CloudStack admin to "
+"assign to that account."
+msgstr "CloudStack 账户。CloudStack管理员为账户指定特定的VLAN。"
+
+# 4a297ddc517048fab79c4a44c5ad0b99
+#: ../../hosts.rst:484
+msgid "900-999"
+msgstr "900-999"
+
+# 404678aaa64349f8924466d04c12db32
+#: ../../hosts.rst:484
+msgid "VLAN carrying guest traffic"
+msgstr "承载来宾流量"
+
+# 185277c2c47d409cb9ec68e3f03ceddc
+#: ../../hosts.rst:484
+msgid ""
+"CloudStack accounts. Can be scoped by project, domain, or all accounts."
+msgstr "CloudStack 账户。可作为项目、域或所有账户的作用域。"
+
+# 5032da4e90be448f905a4ee48df7d8ed
+#: ../../hosts.rst:485
+msgid "greater than 1000"
+msgstr "大于1000"
+
+# af16d28d60df4d84b3951c37a78f02bc
+#: ../../hosts.rst:485
+msgid "Reserved for future use"
+msgstr "保留为将来使用"
+
+# ef44b9e8dc084564a01254fc196c3b9e
+#: ../../hosts.rst:490
+msgid "Adding Non Contiguous VLAN Ranges"
+msgstr "添加不连续的VLAN范围"
+
+# 5b73c96b899144be9a84d12c7ed11d55
+#: ../../hosts.rst:492
+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 "CloudStack能让你灵活的给你的网络添加不连续的VLAN范围。在创建一个zone的时候，管理员要么更新一个已存在的VLAN范围，要么添加多个不连续的VLAN范围。你同样可以使用UpdatephysicalNetwork API来扩展VLAN范围。"
+
+# 957172517a6845a3915b26e7b95812d0
+#: ../../hosts.rst:498
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# cb713605543d4f8eb0ffd5bec494839d
+#: ../../hosts.rst:500
+msgid "Ensure that the VLAN range does not already exist."
+msgstr "确保VLAN范围没有被使用。"
+
+# 6543749bf38741be83173b69828b1f49
+#: ../../hosts.rst:502
+msgid "In the left navigation, choose Infrastructure."
+msgstr "在左边的导航，选择基础架构。"
+
+# 7bd96bd6e7fd4c94bd7be28295bd46de
+#: ../../hosts.rst:504
+msgid ""
+"On Zones, click View More, then click the zone to which you want to work "
+"with."
+msgstr "在Zones上，点击查看更多，然后点击你要进行操作的zone。"
+
+# 29ea322032104b06880f1204aa29a145
+#: ../../hosts.rst:507
+msgid "Click Physical Network."
+msgstr "点击物理网络。"
+
+# a6e5a25d6929406594577a6b3f074454
+#: ../../hosts.rst:509
+msgid "In the Guest node of the diagram, click Configure."
+msgstr "在图中的来宾节点上，点击配置"
+
+# b85881c793b045978846d5eb97408757
+#: ../../hosts.rst:511
+msgid "Click Edit |edit-icon.png|."
+msgstr "点击编辑|edit-icon.png|。"
+
+# 061af0a695ad4e1abcd195287ee6e0ef
+#: ../../hosts.rst:513
+msgid "The VLAN Ranges field now is editable."
+msgstr "现在VLAN范围区域是可编辑的了。"
+
+# 131fadb281474dc597e34d3fe0d6d444
+#: ../../hosts.rst:515
+msgid "Specify the start and end of the VLAN range in comma-separated list."
+msgstr "指定VLAN范围的起始和结束用逗号隔开。"
+
+# aaf0146792d5487297eff314b521c053
+#: ../../hosts.rst:517
+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 "指定所有你想使用的VLANs，如果你添加新的范围到已有列表里，那么没有指定的VLANs将被移除。"
+
+# d7cd1af070644a71ae33b79fbc724b87
+#: ../../hosts.rst:520
+msgid "Click Apply."
+msgstr "点击应用"
+
+# 9685350eac754d8c889dc8da19292529
+#: ../../hosts.rst:524
+msgid "Assigning VLANs to Isolated Networks"
+msgstr "给隔离的网络指定VLAN。"
+
+# 31001908f2bd40018f7b77a9001e50c7
+#: ../../hosts.rst:526
+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 "CloudStack能够让你控制VLAN分配至隔离网络。作为一个Root管理员，当一个网络被创建后，你能为其分配一个VLAN ID，这个网络只能是共享网络。"
+
+# 47af367fd0e74e9c98c07d5fd93d9a6a
+#: ../../hosts.rst:530
+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 "同样被支持—当网络转换为运行状态是，VLAN是随机地通过物理网络的VNET范围分配给网络。当网络作为网络垃圾回收过程的一部分而关闭时，VLAN会被回收到VNET池。当网络再次启用的时候VLAN还能被其重用，或者其他网络使用。在每个新启用的网络中，都有一个新的VLAN被分配。"
+
+# 1ba6d80370024ab596ffd9d4ae6294cc
+#: ../../hosts.rst:538
+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 "只有Root管理员能够分配VLANs，因为常规的用户和域管理员并不清楚物理网络拓扑。他们也不能查看哪个VLAN被分配给网络。"
+
+# f8d82f2f80da4f4fbdef3b4308538511
+#: ../../hosts.rst:542
+msgid "To enable you to assign VLANs to Isolated networks,"
+msgstr "要把VLANs分配给隔离的网络，"
+
+# 51e781fd8ac2474f896774fe185ff585
+#: ../../hosts.rst:544
+msgid "Create a network offering by specifying the following:"
+msgstr "使用下列指定的步骤创建一个网络方案："
+
+# 38ae271a7f7f4855a4353c109d01d761
+#: ../../hosts.rst:546
+msgid "**Guest Type**: Select Isolated."
+msgstr "**来宾网络类型**：选择隔离的。"
+
+# 136f37de7a6f4b1ead01c213603a4a47
+#: ../../hosts.rst:548
+msgid "**Specify VLAN**: Select the option."
+msgstr "**指定VLAN**：选择一个选项。"
+
+# ba4c14a8b3d94e1fbeccb6afd28ec4ad
+#: ../../hosts.rst:550
+msgid "For more information, see the CloudStack Installation Guide."
+msgstr "更多信息，请参考CloudStack安装指导。"
+
+# 42fbeadc772741cdb88549a149bef4c4
+#: ../../hosts.rst:552
+msgid "Using this network offering, create a network."
+msgstr "使用这个网络方案，创建一个网络。"
+
+# b08c9effb9bf43ecb0e42699daf88922
+#: ../../hosts.rst:554
+msgid "You can create a VPC tier or an Isolated network."
+msgstr "你可以创建一个VPC层或者一个隔离网络。"
+
+# d1ae253e49f3473a9ee2ed29b8447270
+#: ../../hosts.rst:556
+msgid "Specify the VLAN when you create the network."
+msgstr "当你创建网络的时候指定VLAN。"
+
+# d4c5557c8994473ba6ca182dc7149c44
+#: ../../hosts.rst:558
+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 "当VLAN被指定后，CIDR和网关就被分配给这个网络了，并且它的状态也变成Setup了。在这个状态下，网络不会被回收。"
+
+# 89369b26917b4d54ad28290b37c59b53
+#: ../../hosts.rst:563
+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 "一旦VLAN被分配给一个网络的话，你就不能更改它。VLAN将伴随着网络的整个生命周期。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/index.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/index.mo
new file mode 100644
index 0000000..2812473
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/index.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/index.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/index.po
new file mode 100644
index 0000000..ec9c85d
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/index.po
@@ -0,0 +1,138 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:04+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 84926a62ef4145eb8258fb18cc990020
+#: ../../index.rst:23
+msgid "Welcome to CloudStack Administration Documentation"
+msgstr "欢迎阅读CloudStack管理文档"
+
+# 17401d6f4fa445e288e17f050447db52
+#: ../../index.rst:29
+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 ""
+
+# 3ed721b0cbc84d29b41f1f88c145794b
+#: ../../index.rst:32
+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 ""
+
+# 6bdec416d5864e24a626b2a1672d12fc
+#: ../../index.rst:36
+msgid "`Documentation Start <http://docs.cloudstack.apache.org>`_"
+msgstr ""
+
+# 59647f13b4c6495bb231941872f8615c
+#: ../../index.rst:38
+msgid ""
+"`Installation Guide <http://docs.cloudstack.apache.org/projects/cloudstack-"
+"installation>`_"
+msgstr ""
+
+# 3cb4b38db39a4954baa74c5207e46806
+#: ../../index.rst:40
+msgid ""
+"`Release Notes <http://docs.cloudstack.apache.org/projects/cloudstack-"
+"release-notes>`_"
+msgstr "`发行说明 <http://docs.cloudstack.apache.org/projects/cloudstack-release-notes>`_"
+
+# 62705a3d035f4c9894e165081f5341b0
+#: ../../index.rst:44
+msgid "User Interface"
+msgstr "用户界面"
+
+# 253ae3a9066e4b22aa50e77c73b69357
+#: ../../index.rst:53
+msgid "Managing Accounts, Users and Domains"
+msgstr "管理账户，用户和域"
+
+# bb51dd2b7b6d4b6287d5b832dd1ef9f3
+#: ../../index.rst:62
+msgid "Using Projects to Organize User Resources"
+msgstr "使用项目来组织用户资源"
+
+# fcbcd54779cb4d14b7c28ea8e525c2ff
+#: ../../index.rst:70
+msgid "Service Offerings"
+msgstr "服务方案"
+
+# 2fed4745955e4e73b1b3bd6c4664a015
+#: ../../index.rst:79
+msgid "Setting up Networking for Users"
+msgstr "用户网络设置"
+
+# 37cb22ac86ef4acb9c046bc1dc7f7de4
+#: ../../index.rst:88
+msgid "Working with Virtual Machines"
+msgstr "使用虚拟机"
+
+# 625c8add441e4edeac86a1ec4f792cec
+#: ../../index.rst:97
+msgid "Working with Templates"
+msgstr "使用模板"
+
+# 7ad29a9c67c74560b24731372d219e23
+#: ../../index.rst:106
+msgid "Working with Hosts"
+msgstr "使用主机"
+
+# a3332c4666934361ad83c88e6946f7f7
+#: ../../index.rst:115
+msgid "Working with Storage"
+msgstr "使用存储"
+
+# f2f20fd23af44019b1f0578d399c9ecc
+#: ../../index.rst:124
+msgid "Working with System Virtual Machines"
+msgstr "使用系统虚拟机"
+
+# 73fe247fe2a14cf08be624ae4f8d5926
+#: ../../index.rst:133
+msgid "Working with Usage"
+msgstr "使用服务"
+
+# 5d20c3a9b5124254a155ba5a519c85ca
+#: ../../index.rst:142
+msgid "Managing Networks and Traffic"
+msgstr "网络和流量管理"
+
+# c591434a39994a6fa8546f4b1115eb07
+#: ../../index.rst:151
+msgid "Managing the Cloud"
+msgstr "管理云"
+
+# 1ffdcf555b9a45d58d6a0e3b4d670037
+#: ../../index.rst:160
+msgid "System Reliability and Availability"
+msgstr "系统可靠性和可用性"
+
+# 8422886b2cfe4b9c9d2adf3afd86f37f
+#: ../../index.rst:169
+msgid "Tuning"
+msgstr "调优"
+
+# c05956039d98457abe5c11b6f7661b23
+#: ../../index.rst:178
+msgid "Events and Troubleshooting"
+msgstr "事件和故障排查"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/management.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/management.mo
new file mode 100644
index 0000000..bfdfc68
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/management.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/management.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/management.po
new file mode 100644
index 0000000..5374345
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/management.po
@@ -0,0 +1,602 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:04+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 36cc316d379647279da05d191cf9e9b5
+#: ../../management.rst:18
+msgid "Managing the Cloud"
+msgstr "管理云"
+
+# 0dc09dfbe9e34a9cb51831005d8fc025
+#: ../../management.rst:21
+msgid "Using Tags to Organize Resources in the Cloud"
+msgstr "在云中使用Tags来组织资源。"
+
+# 3ead5d7ddceb4d98a278abeeed0683c2
+#: ../../management.rst:23
+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 "标签是一类存储云中资源元数据的键值对。其主要用来分类资源，例如，可以将一个用户的虚拟机打上标签，以表明用户所在的城市。在这个例子中，键就是城市，而值可能是Toronto或是Tokyo。可以让cloudstack发现所有打上标签的资源。例如，发现指定城市里用户的虚拟机。"
+
+# 6388318fab6c44f58fd92b854f510717
+#: ../../management.rst:30
+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 "可以给用户虚拟机，磁盘卷，快照，来宾网络，模板，ISO镜像，防火墙规则，端口转发规则，公共IP地址，安全组，负载均衡规则，项目，VPC，网络访问列表或者静态路由器等等，都打上标签。但不能给远程登录VPN打上标签。"
+
+# 87e95cabe82f4b7f86c2cd1cc303b912
+#: ../../management.rst:35
+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 "可以通过CloudStack的界面或者API来创建标签，删除标签或者列出标签。也可以为每一个资源定义多个标签。没有数量的限制。并且，每个标签可以达到255个字符的长度。用户可以定义自己拥有的资源的标签，而管理员可以定义云中所有资源的标签。"
+
+# c2db56ab546245ec9d37ccf72573c16c
+#: ../../management.rst:42
+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 "一个可选的输入参数，标签，存在于多个API中。下面的例子展示了如何应用这个新参数来查找带有 地域=加拿大或城市=多伦多 标签的所有磁盘卷。"
+
+# 0d735394ca9f48f8a4ef3c5d0a25741d
+#: ../../management.rst:55
+msgid "The following API commands have the \"tags\" input parameter:"
+msgstr "下面的API命令具有以下输入参数："
+
+# 6d986331aa5d4971bab13111a8471d36
+#: ../../management.rst:57
+msgid "listVirtualMachines"
+msgstr "listVirtualMachines"
+
+# b0e2702f6aed49a8831ae5c2983a18c9
+#: ../../management.rst:59
+msgid "listVolumes"
+msgstr "listVolumes"
+
+# 97c53594680a4cecb64e3f1a5ea2a2f3
+#: ../../management.rst:61
+msgid "listSnapshots"
+msgstr "listSnapshots"
+
+# 0217180a24604d579084142d07f11299
+#: ../../management.rst:63
+msgid "listNetworks"
+msgstr "listNetworks"
+
+# dcf958a652304820818033fc441226e7
+#: ../../management.rst:65
+msgid "listTemplates"
+msgstr "listTemplates"
+
+# 296660956a3b4ce5b02c4c7f1272e889
+#: ../../management.rst:67
+msgid "listIsos"
+msgstr "listIsos"
+
+# 69e88bee17394199a778180f3304fbf0
+#: ../../management.rst:69
+msgid "listFirewallRules"
+msgstr "listFirewallRules"
+
+# 7954e7afc0334bc7bfcf16492195bb49
+#: ../../management.rst:71
+msgid "listPortForwardingRules"
+msgstr "listPortForwardingRules"
+
+# d273e10141d84eecbdc74ec901700d11
+#: ../../management.rst:73
+msgid "listPublicIpAddresses"
+msgstr "listPublicIpAddresses"
+
+# b3e40262a34d4590bed84b8d5fc62798
+#: ../../management.rst:75
+msgid "listSecurityGroups"
+msgstr "listSecurityGroups"
+
+# e8f6e365e1da4b499d6b852d6c3e1162
+#: ../../management.rst:77
+msgid "listLoadBalancerRules"
+msgstr "listLoadBalancerRules"
+
+# 3c8faeeede5147fb911f022fd5858210
+#: ../../management.rst:79
+msgid "listProjects"
+msgstr "listProjects"
+
+# a9805315805e4d75b977c3428bcde48a
+#: ../../management.rst:81
+msgid "listVPCs"
+msgstr "listVPCs"
+
+# bfab0c32d8364cd9a3e762e7992888f1
+#: ../../management.rst:83
+msgid "listNetworkACLs"
+msgstr "listNetworkACLs"
+
+# 46fab81fefa1469eb87698342b0f045e
+#: ../../management.rst:85
+msgid "listStaticRoutes"
+msgstr "listStaticRoutes"
+
+# 489808dcb1c9407cbe2bd271c02ce89a
+#: ../../management.rst:89
+msgid "Reporting CPU Sockets"
+msgstr "CPU Sockets报表"
+
+# 7d8f4e987714451e9db1c9e749f8b1ca
+#: ../../management.rst:91
+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 the number of hosts and"
+" sockets used for each host type."
+msgstr "生产环境管理着包含一个多个物理CPU端口的不同类型的主机。CPU端口可以看作是一个测量单元，用来授权或制定云架构。生产环境提供UI和API支持来收集CPU端口统计，供订单使用。在架构选项中，有一个新的CPU端口项。可以查看生产环境管理的CPU端口统计数据，这些数据能够反映云的大小。CPU端口页会展示每一主机类型的主机数量及端口数。"
+
+# dec087784ccd48c49189c3f0ed1811a9
+#: ../../management.rst:100
+msgid "Log in to the PRODUCT UI."
+msgstr "登录到CloudStack用户界面。"
+
+# 012d9d141d8745a48fd182b1cab1f8f1
+#: ../../management.rst:102
+msgid "In the left navigation bar, click Infrastructure."
+msgstr "在左侧导航栏中，点击基础架构"
+
+# 991d040f4ccc467f87019591608beea8
+#: ../../management.rst:104
+msgid "On CPU Sockets, click View all."
+msgstr "在CPU Sockets中，点击查看全部。"
+
+# 1f3a30df3d8746f291bc00e761d59f3e
+#: ../../management.rst:106
+msgid ""
+"The CPU Socket page is displayed. The page shows the number of hosts and CPU"
+" sockets based on hypervisor types."
+msgstr "显示CPU插槽页。此页会显示主机数量以及基于虚拟机类型的CPU插槽数量。"
+
+# 3d662bf06abc42bd951d16844faada76
+#: ../../management.rst:111
+msgid "Changing the Database Configuration"
+msgstr "更改数据库配置"
+
+# 638ca3cbc00844789edafb4eb0e60df5
+#: ../../management.rst:113
+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 "CloudStack管理服务器存储了数据库配置信息（如主机名，端口，凭证），这些信息在/etc/cloudstack/management/db.properties文件中，为使更改生效，编辑每个管理服务器上的此文件，然后重启管理服务器"
+
+# a0530bddfe5a47a69ac27ef0a2c38a2e
+#: ../../management.rst:119
+msgid "Changing the Database Password"
+msgstr "更改数据库密码"
+
+# 6ede044a32ac422baed2cd80afc2e114
+#: ../../management.rst:121
+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 "可能会需要更改CloudStack使用的mysql账户密码。如果要更改，需要在MySQL中更改密码，同时要将加密的密码加入到/etc/cloudstack/management/db.properties文件中。"
+
+# 803fea7347b74457808913e8d34560e4
+#: ../../management.rst:126
+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 "在更改密码之前，需要停止CloudStack管理服务器，如果部署了使用引擎，也需要关闭使用引擎。"
+
+# 83b051e006ce4a898817788447a54253
+#: ../../management.rst:135
+msgid ""
+"Next, you'll update the password for the CloudStack user on the MySQL "
+"server."
+msgstr "接下来，你将在MySQL服务器上更新CloudStack的用户密码。"
+
+# a6ed0f9a1e5f41d9883e8ab8e6ed7157
+#: ../../management.rst:142
+msgid "At the MySQL shell, you'll change the password and flush privileges:"
+msgstr "在MySQL命令行下，你将更改密码并且刷新权限："
+
+# 5042ed8fa23b4aa6bf244fb7e8d21d0b
+#: ../../management.rst:150
+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 "下一步是加密密码然后拷贝加密后的密码到CloudStack的数据库配置中(``/etc/cloudstack/management/db.properties``)。"
+
+# 08fe5ba4a2844019b7c34948af80d3e9
+#: ../../management.rst:160
+msgid "File encryption type"
+msgstr "文件加密类型"
+
+# a985e48a20754561ae6daee44e6d79a8
+#: ../../management.rst:162
+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 "请注意这是给文件加密类型准备的。如果你使用web加密类型，那么你要使用password=\"management\\_server\\_secret\\_key\""
+
+# 41348185b9bc4aa59d47266350f37bea
+#: ../../management.rst:166
+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 "现在，你会在 ``/etc/cloudstack/management/db.properties`` 中更新心的密文。使用文本编辑器打开``/etc/cloudstack/management/db.properties`` ，然后更新这些参数："
+
+# 3224048da0604d5e8ff7b22550451ce5
+#: ../../management.rst:175
+msgid ""
+"After copying the new password over, you can now start CloudStack (and the "
+"usage engine, if necessary)."
+msgstr "在复制新的密码过去之后，你可以启动CloudStack了(如果需要的话，还有用量引擎)。"
+
+# b42158e718f44c4ab881833d2dbc0929
+#: ../../management.rst:185
+msgid "Administrator Alerts"
+msgstr "管理员告警信息"
+
+# f35a6a1c63244c84b73055d401027bf8
+#: ../../management.rst:187
+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 "系统提供告警和事件用以帮助云的管理。告警通知管理员，一般用邮件发送，提醒管理员云中有错误发生。告警的行为可以进行配置。"
+
+# ff3195bd128540cca761c8b00697d461
+#: ../../management.rst:192
+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 "事件会追踪云中所有用户和管理员的操作事件。比如，每个客户虚拟机的启动会建立一个对应的事件。每个时间都存储在管理节点的数据库中。"
+
+# 6b6c7d267ebc4ecdba5787f75ed95d52
+#: ../../management.rst:196
+msgid ""
+"Emails will be sent to administrators under the following circumstances:"
+msgstr "在以下情况，系统会发送邮件给管理员："
+
+# 239b319d590244788e6be621087e695a
+#: ../../management.rst:198
+msgid ""
+"The Management Server cluster runs low on CPU, memory, or storage resources"
+msgstr "管理节点集群中CPU，内存或者存储资源的可用量低。"
+
+# 11bbb0a3f5de4024ac7e944c1603e026
+#: ../../management.rst:201
+msgid ""
+"The Management Server loses heartbeat from a Host for more than 3 minutes"
+msgstr "管理节点和主机之间的心跳检查丢失超过3分钟。"
+
+# f6a69a83f8bb45a193d273cbd63ac7bd
+#: ../../management.rst:204
+msgid "The Host cluster runs low on CPU, memory, or storage resources"
+msgstr "主机集群中CPU，内存或者存储资源的可用量低。"
+
+# 267b4ae8b12e42d69f646aa22992388d
+#: ../../management.rst:208
+msgid "Sending Alerts to External SNMP and Syslog Managers"
+msgstr "将警告发送给外部的SNMP和Syslog管理器"
+
+# 030acb1fc907414196ead65866a918b0
+#: ../../management.rst:210
+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 "除了在CloudStack UI中的仪表板上给管理员显示警告和发送电子邮件之外，CloudStack还可以发送同样的警告给外部的SNMP或者Syslog管理软件。如果你更愿意使用SNMP或者Syslog管理器来监视你的云的话，那这么做很有用。"
+
+# ae64dcb892834822b7480195c2882a8c
+#: ../../management.rst:216
+msgid "The alerts which can be sent are:"
+msgstr "可以发送的警告有："
+
+# 814ff89fb6f444fc96a8b87a532bc28f
+#: ../../management.rst:218
+msgid ""
+"The following is the list of alert type numbers. The current alerts can be "
+"found by calling listAlerts."
+msgstr "以下是告警类型的列表。当前告警可以通过调用listAlerts得知。"
+
+# cac2d1c9d3a34cb29f25fc81630f96dc
+#: ../../management.rst:330
+msgid ""
+"You can also display the most up to date list by calling the API command "
+"``listAlerts``."
+msgstr "通过调用API命令 ``listAlerts``，你还可以显示最新的列表。"
+
+# 0ead10e6a3664baf84b6199d70dfb243
+#: ../../management.rst:334
+msgid "SNMP Alert Details"
+msgstr "SNMP警告详情"
+
+# 77c8d073d21f41859f495f2b0120f7ef
+#: ../../management.rst:336
+msgid "The supported protocol is SNMP version 2."
+msgstr "支持SNMP v2。"
+
+# 164535e01fe54071916fc21626d662af
+#: ../../management.rst:338
+msgid ""
+"Each SNMP trap contains the following information: message, podId, "
+"dataCenterId, clusterId, and generationTime."
+msgstr "每个SNMP陷阱报错以下信息：message、podId、dataCenterId、clusterId和generationTime。"
+
+# be99b465676b4d13ae21a9bd33ff94ef
+#: ../../management.rst:343
+msgid "Syslog Alert Details"
+msgstr "Syslog警报详情"
+
+# 653fb8fc18ea4f17ab01fe630ed6783b
+#: ../../management.rst:345
+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 "CloudStack为每个警告生成一个syslog信息。每个syslog信息包含下列格式的字段alertType、message、podId、dataCenterId和clusterId。如果任何字段没有有效值的话，它将不会包含在内。"
+
+# 7c74aa344fe948a39e5bff24928b78fa
+#: ../../management.rst:354
+msgid "For example:"
+msgstr "例如："
+
+# b3bcf49651e44cc189085099c9309174
+#: ../../management.rst:361
+msgid "Configuring SNMP and Syslog Managers"
+msgstr "配置SNMP和Syslog日志管理"
+
+# b5638ebd1bd5442ab77995897186ed0c
+#: ../../management.rst:363
+msgid ""
+"To configure one or more SNMP managers or Syslog managers to receive alerts "
+"from CloudStack:"
+msgstr "要配置一个或多个SNMP管理器或者Syslog管理器来接收来自CloudStack 的警告："
+
+# 377884390b154436a6ce3913008b664c
+#: ../../management.rst:366
+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 "对于SNMP管理器，一个安装在你的SNMP管理系统上安装的CloudStack MIB文件。它映射SNMP OIDs到陷阱类型，目的让用户更容易阅读。这个文件必须是公开的。关于如何安装这个文件的更多信息，参阅SNMP管理器提供的文档。"
+
+# a32632406531434cbf5c4c261b1f69b6
+#: ../../management.rst:372
+msgid "Edit the file /etc/cloudstack/management/log4j-cloud.xml."
+msgstr "编辑 /etc/cloudstack/management/log4j-cloud.xml文件。"
+
+# 8ba1745b7c924d888e2595a379d2db32
+#: ../../management.rst:378
+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 "使用下面给出的语法添加一个条目。选择你是要添加一个SNMP管理器还是一个Syslog管理器，然后按照适当的示例操作。要指定多个外部管理器，使用逗号(,)将IP地址和其他配置值隔开。"
+
+# 6cd8468c57974817b400436e8e445394
+#: ../../management.rst:384
+msgid ""
+"The recommended maximum number of SNMP or Syslog managers is 20 for each."
+msgstr "SNMP或Syslog管理器推荐的最大值是20。"
+
+# d399f22c73ea4836a3776bd53493aaf9
+#: ../../management.rst:387
+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 "下面的例子展示了如果配置两个IP分别为10.1.1.1和10.1.1.2的SNMP管理器。在实际使用中请替换成你的IP、ports和communities。不要改变其他值(name、threshold、class和layout值)。"
+
+# 57b464a769fd4128a163f5613f5f1c96
+#: ../../management.rst:405
+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 "下面的例子展示了如果配置两个IP分别为10.1.1.1和10.1.1.2的Syslog管理器。在实际是使用中请替换成你的IP。你可以设置Facility为任何syslog-defined的值，如 LOCAL0 - LOCAL7。不要改变其他的值。"
+
+# 9ac4b5f945144653a9fb6df9185afba4
+#: ../../management.rst:421
+msgid ""
+"If your cloud has multiple Management Server nodes, repeat these steps to "
+"edit log4j-cloud.xml on every instance."
+msgstr "如果你的云有多个管理服务器节点，在编辑每个节点中log4j-cloud.xml的时候，重复这些步骤。"
+
+# d82882ad1f8e447fb1ddbf2141ca0f1e
+#: ../../management.rst:424
+msgid ""
+"If you have made these changes while the Management Server is running, wait "
+"a few minutes for the change to take effect."
+msgstr "当管理服务器正在运行的时候，你做了这些变更，等待一会让变更生效。"
+
+# c74a110e35d5496db9637e208ca69f0c
+#: ../../management.rst:427
+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 "**排错：**如果一段之后，在配置的SNMP或者Syslog管理器中没有警告出现，那么log4j-cloud.xml中<appender>的语法可能有错误。检查并确定格式和设置都是正确的。"
+
+# 6e66a0c8054b4278923a1680c1d13f92
+#: ../../management.rst:435
+msgid "Deleting an SNMP or Syslog Manager"
+msgstr "删除SNMP或Syslog日志管理"
+
+# daed36b7b2304574be3a327f0fdaae34
+#: ../../management.rst:437
+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 "要移除一个外部SNMP管理器或者Syslog管理器以便它不再接收来自CloudStack 的警告，请删除``/etc/cloudstack/management/log4j-cloud.xml``文件中对应的条目。"
+
+# 13024d28ec5a4e0d9d54dc264f048c4c
+#: ../../management.rst:443
+msgid "Customizing the Network Domain Name"
+msgstr "自定义网络域名"
+
+# 47fe94d226e941e8971730847123ac7e
+#: ../../management.rst:445
+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 "根管理员在网络, 帐户，域， 资源域以及整个CloudStack级别可选择设置DNS后缀，域管理员可以在自己的域做这样的设置。要自定义域名并使其有效, 请按照下面的步骤操作。"
+
+# 12a0d889b85a42dfb2f7a37556be8592
+#: ../../management.rst:451
+msgid "Set the DNS suffix at the desired scope"
+msgstr "在所需的范围内设置DNS后缀"
+
+# 8f9f57e29f9c404d9930091f8630a427
+#: ../../management.rst:453
+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 "在网络级别中, DNS后缀可以通过UI在创建新的网络时设置, 这些在 `“添加额外的来宾网络” <networking2#adding-an-additional-guest-network>`_ 或CloudStack API的updateNetwork命令中都有描述."
+
+# c091289d2eee46e89ea79afc752a76bf
+#: ../../management.rst:459
+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 "在帐户、域或者区域级别，DNS后缀可以由以下CloudStack API命令：createAccount、editAccount、createDomain、editDomain、createZone或editZone指定。"
+
+# 3aa8bfbb66e6499eaf26bd3d496d6bf8
+#: ../../management.rst:464
+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 "在全局级别中，使用配置参数guest.domain.suffix。你也可以使用CloudStack API命令updateConfiguration。当更改了这个全局配置后，重启管理服务器的服务以便新的设置有效。"
+
+# ea55aed82e8440d191210e6219afd4b4
+#: ../../management.rst:469
+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 "为了使你的新DNS后缀对已经存在的网络有效，你需要调用CloudStack API命令updateNetwork。对于DNS后缀已经更改后新建的网络这一步不是必需的。"
+
+# c4c8780f62264aef9166fb7abb03b23d
+#: ../../management.rst:473
+msgid ""
+"The source of the network domain that is used depends on the following "
+"rules."
+msgstr "你使用的网络域的源取决于下面的一些规则。"
+
+# ed54e22f6c384a979fdd24525a23d6f4
+#: ../../management.rst:476
+msgid ""
+"For all networks, if a network domain is specified as part of a network's "
+"own configuration, that value is used."
+msgstr "对于所有的网络，如果网络域作为这个网络自己配置的一部分，那这个网络域的值会被使用。"
+
+# b62736506f044912b7508f5bcfca6b0b
+#: ../../management.rst:479
+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 "对于账户指定的网络，为这个账户指定的网域会被使用。如果没有指定，系统会按照域，区域和全局配置的顺序查找网域的值。"
+
+# e4424d33ec9549389255552629bbdd2a
+#: ../../management.rst:483
+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 "对于域指定的网络, 为这个域指定的网络域名会被使用. 如果没有指定, 系统会区域和全局配置中按顺序查找网络域名的值."
+
+# 3d1ebf272ba647ef8f54fcd126b4806c
+#: ../../management.rst:487
+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 "对于区域指定的网络, 为这个域指定的网络域名会被使用. 如果没有指定, 系统会在全局配置里查找网络域名的值."
+
+# b6795b367f9a4a56bd542d1303ef6706
+#: ../../management.rst:493
+msgid "Stopping and Restarting the Management Server"
+msgstr "停止和重启管理服务"
+
+# bbd28a885afc4bd6918951b631b80c85
+#: ../../management.rst:495
+msgid ""
+"The root administrator will need to stop and restart the Management Server "
+"from time to time."
+msgstr "超级管理员需要经常性的关闭和重启管理服务。"
+
+# 0d670244a1804343a1935015f8eaa6fb
+#: ../../management.rst:498
+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 "例如，修改全局配置参数之后，要求重启管理服务器。如果您有多个管理服务器节点，请全部重启，以便使新参数值在整个云中生效。"
+
+# 180fc3fdda44467f97b04959693747c5
+#: ../../management.rst:503
+msgid ""
+"To stop the Management Server, issue the following command at the operating "
+"system prompt on the Management Server node:"
+msgstr "要停止管理服务，在管理服务节点所在的操作系统中运行如下命令："
+
+# 02d90290579d496098aed77584f7a2d3
+#: ../../management.rst:510
+msgid "To start the Management Server:"
+msgstr "启动管理服务："
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking.mo
new file mode 100644
index 0000000..53f4100
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking.po
new file mode 100644
index 0000000..0d95a6e
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking.po
@@ -0,0 +1,900 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:04+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# e178ac0be7b0492e8a2edc6ed9be7a7b
+#: ../../networking.rst:18
+msgid "Setting Up Networking for Users"
+msgstr "用户网络设置"
+
+# 04f3cd2def1648f2a118dc72cdd5a592
+#: ../../networking.rst:21
+msgid "Overview of Setting Up Networking for Users"
+msgstr "用户网络设置概览"
+
+# 60188130ecb74037bd537749bcaf4750
+#: ../../networking.rst:23
+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 "当涉及到云计算所提供的网络服务, 使用云基础设施的人都有各自不同的需求和喜好. 作为CloudStack管理员, 你可以为你的用户做下面的事情来设置网络:"
+
+# fb8952bb97144229abe5a477941ae76a
+#: ../../networking.rst:28
+msgid "Set up physical networks in zones"
+msgstr "在资源域里设置物理网络"
+
+# 8dd6941ef2c54c6bbabf956d9eb0680a
+#: ../../networking.rst:30
+msgid ""
+"Set up several different providers for the same service on a single physical"
+" network (for example, both Cisco and Juniper firewalls)"
+msgstr "在单个物理网卡上为同一服务设置不同的服务提供者(例如, 同时设置Cisco和Juniper的防火墙)"
+
+# d4c8d144d71e47c7b10f71c182941308
+#: ../../networking.rst:33
+msgid ""
+"Bundle different types of network services into network offerings, so users "
+"can choose the desired network services for any given virtual machine"
+msgstr "绑定不同类型的网络服务到网络方案中, 这样用户可以在给定的虚机中使用期望的网络服务."
+
+# f5309ffd41a14f77a9dd77113c106332
+#: ../../networking.rst:37
+msgid ""
+"Add new network offerings as time goes on so end users can upgrade to a "
+"better class of service on their network"
+msgstr "随着时间的推移, 添加新的网络方案以便是最终用户升级他们的网络服务."
+
+# 13b07adc896a416793148e27ab919b13
+#: ../../networking.rst:40
+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 "提供更多的途径让一个用户访问一个网络, 比如通过用户所在的一个项目"
+
+# 75c4f2f501724f68be26715201e81f13
+#: ../../networking.rst:45
+msgid "About Virtual Networks"
+msgstr "关于虚拟网络"
+
+# 6e8b5c92233f49618f96673822e130e6
+#: ../../networking.rst:47
+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 "虚拟网络是使多租户在一个物理网络中的逻辑结构。在CloudStack中，虚拟网络可以被共享或隔离。"
+
+# e96b2f098a274b148edc9883c7424a27
+#: ../../networking.rst:53
+msgid "Isolated Networks"
+msgstr "独立的网络"
+
+# 3358619f0382468a9d2f2aea99522408
+#: ../../networking.rst:55
+msgid ""
+"An isolated network can be accessed only by virtual machines of a single "
+"account. Isolated networks have the following properties."
+msgstr "一个隔离的网络可以访问虚拟机的单一账户。隔离的网络具有下列性质。"
+
+# c84b0ce76be64977bad2361a036a55cf
+#: ../../networking.rst:58
+msgid "Resources such as VLAN are allocated and garbage collected dynamically"
+msgstr "如VLAN等资源被动态分配和垃圾收集"
+
+# 3eb29ededba94d0dbcb168491b1acda6
+#: ../../networking.rst:61
+msgid "There is one network offering for the entire network"
+msgstr "有一个用于整个网络的网络方案"
+
+# ff059c44a53e4765b488337444f9fd70
+#: ../../networking.rst:63
+msgid ""
+"The network offering can be upgraded or downgraded but it is for the entire "
+"network"
+msgstr "网络提供可升级或降级，但它是用于整个网络的"
+
+# d147367777724c05a61626c7756aae05
+#: ../../networking.rst:66
+msgid ""
+"For more information, see `“Configure Guest Traffic in an Advanced Zone” "
+"<networking2.html#configure-guest-traffic-in-an-advanced-zone>`_."
+msgstr "更多信息，参考`“在高级区域中配置来宾流量” <networking2.html#configure-guest-traffic-in-an-advanced-zone>`_."
+
+# 9cb58dfba63248058b6e4c2370250e1f
+#: ../../networking.rst:71
+msgid "Shared Networks"
+msgstr "共享网络"
+
+# 4b159336d5054af78283deb65966e56d
+#: ../../networking.rst:73
+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 "共享网络可以被属于不同客户的虚拟机访问。共享网络中的网络隔离通过安全组实现（仅在CloudStack 3.0.3及以后的基本区域中支持）"
+
+# 0eed59cfbc8447e98bc84e58489e3ae7
+#: ../../networking.rst:78
+msgid "Shared Networks are created by the administrator"
+msgstr "管理员创建的共享网络"
+
+# b29eadf838f449549e16a2e745f711af
+#: ../../networking.rst:80
+msgid "Shared Networks can be designated to a certain domain"
+msgstr "在一个确定的哉中设计共享网络"
+
+# 956864b9c95e4fb98178b4a0ad4918d3
+#: ../../networking.rst:82
+msgid ""
+"Shared Network resources such as VLAN and physical network that it maps to "
+"are designated by the administrator"
+msgstr "共享网络资源如VLAN和物理网络，它映射到指定的管理员"
+
+# a9b84145482e4171bdf228084a5d51f4
+#: ../../networking.rst:85
+msgid "Shared Networks can be isolated by security groups"
+msgstr "共享网络通过安全组实现隔离"
+
+# 345abc742c6749aeb975b3453c70c387
+#: ../../networking.rst:87
+msgid "Public Network is a shared network that is not shown to the end users"
+msgstr "公网网络作为一个共享网络不会展示给终端用户"
+
+# 743e27f0ef1d415180cce8da2bb79724
+#: ../../networking.rst:89
+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 "当共享网络是由虚拟路由提供的服务，则每个区域是不支持Source NAT功能的。然而，每个帐户是支持Source NAT功能的。更多信息，参考`“配置共享来宾网络” <networking2.html#configuring-a-shared-guest-network>`_."
+
+# dfed0497ec374d71927a32da736f6b28
+#: ../../networking.rst:96
+msgid "Runtime Allocation of Virtual Network Resources"
+msgstr "虚拟网络资源的运行时分配"
+
+# 33c1cc37caa3449d8a22888ee5706153
+#: ../../networking.rst:98
+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 "当你定义一个新的虚拟网络，该网络的所有的设置都存储在CloudStack中。只有当第一台虚拟机在该网络中启动时，实际的网络资源才会被激活。当所有的虚拟机都离开了虚拟网络，系统进行网络资源垃圾收集，使它们能够重新分配。这有助于节约网络资源。"
+
+# c7699333b3c747f09b34f3a541caa725
+#: ../../networking.rst:107
+msgid "Network Service Providers"
+msgstr "网络服务提供者"
+
+# 90bd799fd2444d978136f72070afd1ca
+#: ../../networking.rst:110
+msgid ""
+"For the most up-to-date list of supported network service providers, see the"
+" CloudStack UI or call `listNetworkServiceProviders`."
+msgstr "查看最新的网络服务提供者支持列表请见CloudStack用户界面或者调用listNetworkServiceProviders`.。"
+
+# 3f97bb088f7240d99034a78ca6adf65f
+#: ../../networking.rst:113
+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 "服务提供者(也称为网络元件)是指通过硬件或虚拟应用来实现网络应用。比如，防火墙应用可以安装在云端来提供防火墙服务。在独立网络中多个提供者能提供相同的网络服务。比如，可以通过思科或者Juniper的设备在同一个物理网络中提供防火墙服务。"
+
+# e52ed5139a664c31acccd845de73897d
+#: ../../networking.rst:120
+msgid ""
+"You can have multiple instances of the same service provider in a network "
+"(say, more than one Juniper SRX device)."
+msgstr "在一个网络中你可以多个实例使用相同的服务提供者(也可以使用多个Juniper SRX设备)"
+
+# 013a36e42a254aaa98b7e3ad9ea97db8
+#: ../../networking.rst:123
+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 "如果不同提供者被设置在网络中提供相同服务，管理员可以通过创建网络提供方案，因此用户能够自己制定使用哪个物理网络提供者(要遵从网络提供方案中的其他选项)。否则CloudStack会在服务被需求的时候选择使用哪个提供者。"
+
+# eb5e7f69942b448f906dc822400a348c
+#: ../../networking.rst:129
+msgid "*Supported Network Service Providers*"
+msgstr "*支持的网络服务提供者*"
+
+# d43ecfbdacb84dac9d6ffe5229f277a3
+#: ../../networking.rst:131
+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 "CloudStack已经预置了一些内置的服务提供者支持列表。你能在创建网络提供方案的时候你能从这列表中选择。"
+
+# 5dd3d24c6aa149cd8be77c9e90e924fa
+#: ../../networking.rst:136
+msgid "Virtual Router"
+msgstr "虚拟路由"
+
+# 8f9be66568214ef19761bdd0b1e87a0a
+#: ../../networking.rst:136
+msgid "Citrix NetScaler"
+msgstr "Citrix NetScaler"
+
+# dccb0ff066124e7ca8f1f4b1df9b566a
+#: ../../networking.rst:136
+msgid "Juniper SRX"
+msgstr "Juniper SRX"
+
+# b6c9b2cf119641999eeded8e8069824f
+#: ../../networking.rst:136
+msgid "F5 BigIP"
+msgstr "F5 BigIP"
+
+# 4eec0320581e47cea2b8b9a6eb5c5b70
+#: ../../networking.rst:136
+msgid "Host based (KVM/Xen)"
+msgstr "Host based (KVM/Xen)"
+
+# 2c2f1239e908471a929feb91a02e08dd
+#: ../../networking.rst:139
+msgid "Remote Access VPN"
+msgstr "远程访问VPN"
+
+# 3ae9d08f24164c359e5553b13dd96db0
+# 0c7c9adabf9449babcb4553e3a59b52b
+# 411fef44341e42758013621c4a23b6b6
+# 6c934e881e7849368f5400433ea69f81
+# 1fc336068db6481183d8a01c5746f5e0
+# 8a397af8cc344e41b52173b2d9bce329
+# 8a7faf6012614a33a03fce7b63e06032
+# f4b01e6ad27f435bbe4aa4b14adc6cd9
+# 60fc90d0645a4e70a2b43c269d7d92ab
+# 72abbb0d60bb43e7ac7ca73f206aa8dd
+# 3f6508ced2f04ac2adcd337ac022d6b0
+# 5492ba67a1304fdb9b75910ef384ac85
+# 1b2c1c6af0814e59bd1d64623dec20d6
+# 76efa1585e2241eaaae3e5a45da37007
+# 933c860bae084ab4846ad9f7270712aa
+# c38c824dc105481f82f564a1071efb74
+#: ../../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
+msgid "Yes"
+msgstr "是"
+
+# 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
+#: ../../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
+msgid "No"
+msgstr "否"
+
+# ab9d28c06dcf43d6b43310410d730272
+#: ../../networking.rst:141
+msgid "DNS/DHCP/User Data"
+msgstr "DNS/DHCP/User Data"
+
+# ec9a836945d54daa80b2790549b0e124
+# 98b80ddeb60c417e839a5e695b989f52
+# 155333ae90b64d45959ef29649a45d44
+#: ../../networking.rst:143 ../../networking.rst:180 ../../networking.rst:288
+msgid "Firewall"
+msgstr "防火墙"
+
+# ec3524d24a7c47479fbc5f696c94c8ba
+# 5d871878b8f6400babacd35334ff571b
+#: ../../networking.rst:145 ../../networking.rst:178
+msgid "Load Balancing"
+msgstr "负载均衡"
+
+# e9f00e30da4347368893885b9ebf0951
+#: ../../networking.rst:147
+msgid "Elastic IP"
+msgstr "弹性IP"
+
+# 2665ea2a6b90470e81ee706892bc8f12
+#: ../../networking.rst:149
+msgid "Elastic LB"
+msgstr "弹性负载均衡"
+
+# b07356b446e34c669846ad2c208ed183
+# 522b28c564644bf68213f95712c5b120
+# 2177095ff4a24da29d588bb4cd3c2f4a
+#: ../../networking.rst:151 ../../networking.rst:172 ../../networking.rst:289
+msgid "Source NAT"
+msgstr "Source NAT"
+
+# eea6bbfe102d498e8fed5cb73cc69b0d
+# c02a1aa3d43f4cde9668b0c049f5ca68
+# fdd23b4cdd3f4aa4a540bf84253e6a5b
+#: ../../networking.rst:153 ../../networking.rst:174 ../../networking.rst:292
+msgid "Static NAT"
+msgstr "静态 NAT"
+
+# b4c037f8d0f1486a8b571d432c94dfc2
+# 218d3d03262e42b2aff11ea6d99f0a49
+# 3ec6fc2e436743f7bf4b9704948e4af3
+#: ../../networking.rst:155 ../../networking.rst:176 ../../networking.rst:295
+msgid "Port Forwarding"
+msgstr "端口转发"
+
+# 479f4b962b404a428355bb406c787cd9
+#: ../../networking.rst:160
+msgid "Network Offerings"
+msgstr "网络方案"
+
+# 25cda5fdd680428d82d9dc0b90b9da3f
+#: ../../networking.rst:163
+msgid ""
+"For the most up-to-date list of supported network services, see the "
+"CloudStack UI or call listNetworkServices."
+msgstr "要查看最新的网络服务支持列表，请参见 CloudStack用户界面或者调用API listNetworkServices。"
+
+# 746c329fee3d40298682a774fc0e1ce0
+#: ../../networking.rst:166
+msgid "A network offering is a named set of network services, such as:"
+msgstr "网络方案是带名称的一套网络服务，例如："
+
+# 1f84716ebc364d34a628de273bfae124
+# 50ebc53bb5124166b60910b97ac86bc4
+#: ../../networking.rst:168 ../../networking.rst:283
+msgid "DHCP"
+msgstr "DHCP"
+
+# 883e0ebe77d94552b3e24415615a7bd9
+# 206e31a90b27475a957f3a6347b7e15d
+#: ../../networking.rst:170 ../../networking.rst:284
+msgid "DNS"
+msgstr "DNS"
+
+# c7ba4a3ce199420a8e1ffa59b6b5aa77
+# e018337607ad4a9d90fe4ef3ab26189e
+#: ../../networking.rst:182 ../../networking.rst:298
+msgid "VPN"
+msgstr "VPN"
+
+# 0c8566ee7245401e89972f62635febae
+#: ../../networking.rst:184
+msgid ""
+"(Optional) Name one of several available providers to use for a given "
+"service, such as Juniper for the firewall"
+msgstr "(可选)在服务的多个可选提供者中指定其一，例如Juniper作为防火墙服务"
+
+# 010067ad73c94e95ad457ead1a816c4e
+#: ../../networking.rst:187
+msgid "(Optional) Network tag to specify which physical network to use"
+msgstr "(可选)用于指定使用哪个物理网络的网络标签"
+
+# 27fc0e1384a041e280aad1d5c6497be1
+#: ../../networking.rst:189
+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 "用户创建虚机时，需要选择一种可用的网络方案。该网络方案确定了虚机可使用的网络服务。"
+
+# f0629abea4a3489ab43c6616754295d7
+#: ../../networking.rst:192
+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 a web server farm and "
+"require a scalable firewall solution, load balancing solution, and alternate"
+" networks for accessing the database backend."
+msgstr "CloudStack ;提供了默认的网络方案，在此之外，系统管理员可以添加任意数量的自定义网络方案。通过创建多种自定义网络方案，您可以在一个多租户的物理网络基础上提供不同级别的网络服务。例如，尽管两个租户的底层物理网络是一个，租户A可能仅需要用防火墙保护他们的网站，而租户B可能运行一个Web服务器集群，要求一个可扩展的防火墙方案、负载均衡方案、和用于访问后台数据库的可替代的网络。"
+
+# f84d6b9ac9d44d159518d14cc74cef39
+#: ../../networking.rst:204
+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 "如果你创建了一个负载均衡规则且使用包括外部负载均衡设备的网络服务方案，如包括NetScaler，但随后将网络方案改成使用CloudStack的虚拟路由器，则你必须在虚拟路由器上创建一个防火墙规则，这些防火墙规则与已经设置的负载均衡规则一一对应，只有这样，才能使那些负载均衡规则继续起作用。"
+
+# 6a193ad193634184b47093dfab78d48b
+#: ../../networking.rst:211
+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 "创建新虚拟网络时，CloudStack 管理服务器可选择该网络使用的网络方案。每个虚拟网络都关联一个网络方案。虚拟网络可以通过改变关联的网络方案来升级或降级。如果您要这样做，请确保调整物理网络以匹配网络方案。"
+
+# 514547d261a44dbba069882e1163a863
+#: ../../networking.rst:217
+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 "CloudStack 中有给系统虚机使用的内部网络方案。内部网络方案对最终用户是不可见的，但系统管理员可以对其修改。"
+
+# 9eab025e1e0b4102aabc5ed825ad3513
+#: ../../networking.rst:223
+msgid "Creating a New Network Offering"
+msgstr "创建一个新的网络方案"
+
+# 101c5c58b3164f2d91d7c068fa2ddc13
+#: ../../networking.rst:225
+msgid "To create a network offering:"
+msgstr "创建一个新的网络方案"
+
+# ad144ea208224f0ba8bfd3d268ebaa1a
+#: ../../networking.rst:227
+msgid "Log in with admin privileges to the CloudStack UI."
+msgstr "以管理员权限登录CloudStack用户界面。"
+
+# 7183c1c87f1e4a549609755e3b609e22
+#: ../../networking.rst:229
+msgid "In the left navigation bar, click Service Offerings."
+msgstr "在左侧导航栏中，点击 服务方案。"
+
+# 22b7bae2bee145399e00d289bccc7917
+#: ../../networking.rst:231
+msgid "In Select Offering, choose Network Offering."
+msgstr "在选择方案中，选择网络方案。"
+
+# ef1169d122904044a6c0246757cbbb46
+#: ../../networking.rst:233
+msgid "Click Add Network Offering."
+msgstr "点击添加网络方案。"
+
+# 3479c8e9a5ef4f458aa9a86725ea9a15
+#: ../../networking.rst:235
+msgid "In the dialog, make the following choices:"
+msgstr "在对话框中，选择如下操作："
+
+# b9faa7d006ed43108fcd33897fea3a5f
+#: ../../networking.rst:237
+msgid "**Name**. Any desired name for the network offering."
+msgstr "**名称**: 任何网络方案的名称。"
+
+# 28d48401d7c74f61a6251f06e8e33ea5
+#: ../../networking.rst:239
+msgid ""
+"**Description**. A short description of the offering that can be displayed "
+"to users."
+msgstr "**描述**: 提供一个简短的方案描述。 "
+
+# a81d203163fd41108b4ed24231b5c84d
+#: ../../networking.rst:242
+msgid "**Network Rate**. Allowed data transfer rate in MB per second."
+msgstr "**网络速度**: 允许的数据传输速度（MB/秒）。"
+
+# bf34e4c1410c487c81e21d82564c0ceb
+#: ../../networking.rst:244
+msgid ""
+"**Guest Type**. Choose whether the guest network is isolated or shared."
+msgstr "**来宾类型**: 选择来宾网络为隔离或共享网络。"
+
+# 636bbcf4e8ff4e89bc5a3263fa3152fd
+#: ../../networking.rst:247
+msgid ""
+"For a description of this term, see `“About Virtual Networks” <#about-"
+"virtual-networks>`_."
+msgstr "关于此组的描述，参考 see `“关于虚拟网络” <#about-virtual-networks>`_."
+
+# d9e50bd69812476c975c4eb28509a054
+#: ../../networking.rst:250
+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 "**持续性**: 表明来宾网络是否支持持续性。无需提供任何VM部署的网络，称之为持续性网络。更多信息，参考 `“持久性网络” <networking2.html#persistent-networks>`_."
+
+# a78fcf61c20941b4a0074b52d456b4fb
+#: ../../networking.rst:256
+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 "**指定VLAN**.(只针对隔离来宾网络)这表明无论使用这个方案时是否指定了VLAN，如果你选中了这个选项，并且当你创建VPC层或隔离网络时使用了这个网络方案，那么，你都可以为你创建的网络拽定一个VLAN ID。"
+
+# 0c356efbc6b1453083e1df0e795cfc3f
+#: ../../networking.rst:262
+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 "**VPC**: 此选项表明是否在来宾网络中启用VPC。 CloudStack中的虚拟专用云(VPC)是专用、隔离的。 一个VPC可以有一个类似于传统物理网络的虚拟网络拓扑结构。有关的VPC的详细信息，请参考 see `“关于VPC” <networking2.html#about-virtual-private-clouds>`_."
+
+# 99699a8ca7b8442b9273331bf3721599
+#: ../../networking.rst:269
+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 "**支持的服务**.选择一个或多个可能的网络服务。对于有一个服务，你还必须同时选择服务的提供者。比如，如果你选择了负载均衡服务，那你可以CLOUDSTACK虚拟路由或是云环境中其它配置了此功能的服务者。取决于你选择服务的不同，额外的选项或是对话框的填写项也会相应不同。"
+
+# 92f1a16c1ffe4ceb84808c9ba972cbd4
+#: ../../networking.rst:277
+msgid ""
+"Based on the guest network type selected, you can see the following "
+"supported services:"
+msgstr "基于你选择的来宾网络类型，可以看到如何支持的服务。"
+
+# 88a57a6470eb454ba571d8fde5632a82
+#: ../../networking.rst:281
+msgid "Supported Services"
+msgstr "支持的服务"
+
+# d4aa55848ef645639458f908896ac697
+#: ../../networking.rst:281
+msgid "Description"
+msgstr "描述"
+
+# f8724e6bbae14251ae83b23169d9420f
+#: ../../networking.rst:281
+msgid "Isolated"
+msgstr "隔离"
+
+# 23bd72f8680a493682d6741602166846
+#: ../../networking.rst:281
+msgid "Shared"
+msgstr "共享"
+
+# b488c5b17c004a7b88b330efbc3bc05f
+# 9817c5466dbe4abf99c2de124120bbed
+#: ../../networking.rst:283 ../../networking.rst:284
+msgid ""
+"For more information, see `“DNS and DHCP” <networking2.html#dns-and-dhcp>`_."
+msgstr "更多信息，请参考 `“DNS and DHCP” <networking2.html#dns-and-dhcp>`_."
+
+# c4875cd1ba3341f0801c282d362f1d24
+# d065a3aee4944733bff2d01f26b75c7f
+# 9f736e032cce456ebb4f77be38b5e58f
+# 7df1ac5d383948bd84380b75c4e098af
+# 3ba5059895ef4d1c85924407662447ee
+# 3e841c3844b94853b7a8aaaed25cd4ad
+# c77eeef8c5314be099fb3716d3445a66
+# 25f106d12a764b078bb2b6524ad18215
+# f63379e1fe44403bb4b003d91fc04f93
+# 4f4951219e654f71ba852ba5238e8851
+# 15ddd915917341cb80019e9b900a4731
+# 8dacf6aaa0704e9db73a0126c94e16e5
+# 50e87369ed7e48e29d7cb426767a5ed8
+# c1b167740f9e43c2a17a96fbf65930bf
+# 22a23c6ed73740b8a269adc46484bd2a
+# bb47b4ce2443499aa4f5308fec5ed187
+# 8754a866d8d14c92a6556744cf012422
+#: ../../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
+msgid "Supported"
+msgstr "支持"
+
+# 50819151ad5442aeb2570677b2632a46
+#: ../../networking.rst:285
+msgid "Load Balancer"
+msgstr "负载均衡"
+
+# b9edc8827ba44d2db0f62206a215e670
+#: ../../networking.rst:285
+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 "如果选择了负载均衡功能，你就可以选择CLOUDSTACK虚拟路由或是云环境中其它配置了此服务的提供者。"
+
+# 2e489054cb1e4a35ac3e90f70c1f1255
+#: ../../networking.rst:288
+msgid "For more information, see the Administration Guide."
+msgstr "更多信息，请参考管理指南"
+
+# 8e117eda9d13423c93e568f0818cc4d9
+#: ../../networking.rst:289
+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 "如果选择了 Source NAT功能，你就可以选择CLOUDSTACK虚拟路由或是云环境中其它配置了此服务的提供者。 "
+
+# aba8109b051a46d89785cb597e382503
+#: ../../networking.rst:292
+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 "如果选择了Static NAT功能，你就可以选择CLOUDSTACK虚拟路由或是云环境中其它配置了此服务的提供者。"
+
+# d932fb3f0c49487e8fb03f47c8ec3137
+#: ../../networking.rst:295
+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 "如果选择了端口转发功能，你就可以选择CLOUDSTACK虚拟路由或是云环境中其它配置了此服务的提供者。"
+
+# ba3080b2df494a6194c5a4ec14bd1410
+# 5c07262385d1478c927953b93692e644
+# 23f57ac958b34548a1c2d23a776e1da8
+# c3490a0f19134b8b886f204a4794c427
+# 111a4f3a414c443cb13dcb958326620f
+#: ../../networking.rst:295 ../../networking.rst:298 ../../networking.rst:300
+#: ../../networking.rst:302 ../../networking.rst:304
+msgid "Not Supported"
+msgstr "不支持"
+
+# ab512b24e90a4f0fbeff2872914232bf
+#: ../../networking.rst:298
+msgid ""
+"For more information, see `“Remote Access VPN” <networking2.html#remote-"
+"access-vpn>`_."
+msgstr "更多信息，请参考`“Remote Access VPN” <networking2.html#remote-access-vpn>`_."
+
+# bc836dbec7dd41098535b7062953abf7
+#: ../../networking.rst:300
+msgid "User Data"
+msgstr "用户数据"
+
+# 2ee92986a8924dd1a8704e477e3ce1a6
+#: ../../networking.rst:300
+msgid ""
+"For more information, see `“User Data and Meta Data” <api.html#user-data-"
+"and-meta-data>`_."
+msgstr "更多信息，请参考 `“用户数据和元数据” <api.html#user-data-and-meta-data>`_."
+
+# c84e2a3c0cb2440f96442843325bf941
+#: ../../networking.rst:302
+msgid "Network ACL"
+msgstr "网络 ACL"
+
+# 1a00657b608e45b9b31d17dedf1209d9
+#: ../../networking.rst:302
+msgid ""
+"For more information, see `“Configuring Network Access Control List” "
+"<networking2.html#configuring-network-access-control-list>`_."
+msgstr "更多信息，参考 `“配置网络ACL” <networking2.html#configuring-network-access-control-list>`_."
+
+# 72b47ce7c25a4820af0c52549a594235
+#: ../../networking.rst:304
+msgid "Security Groups"
+msgstr "安全组"
+
+# 08f3a340905b433990695bcc9c4fdd28
+#: ../../networking.rst:304
+msgid ""
+"For more information, see `“Adding a Security Group” "
+"<networking2.html#adding-a-security-group>`_."
+msgstr "更多信息，请参考 `“添加一个安全组” <networking2.html#adding-a-security-group>`_."
+
+# e235b3337dbb400c90ecee3f5837fde2
+#: ../../networking.rst:309
+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 custom system service "
+"offerings that have been defined by the CloudStack root administrator."
+msgstr "**系统方案**.如果你在任务服务提供者中选择了虚拟路由，那就会出现系统方案的填写项。选择你希望虚拟路由在此网络中提供的服务。比如，如果你选择了虚拟路由提供负载均衡服务，系统方案填写项就会出现，你可以选择CLOUDSTACK管理员定义的所有系统服务及默认服务。 "
+
+# 34b519afb51c4d1f9b1718b0f32cb527
+#: ../../networking.rst:319
+msgid ""
+"For more information, see `“System Service Offerings” "
+"<service_offerings.html#system-service-offerings>`_."
+msgstr "更多信息，参考 `“系统服务方案” <service_offerings.html#system-service-offerings>`_."
+
+# 66fb3b1df7164cd6bc37c61a61367d73
+#: ../../networking.rst:322
+msgid ""
+"**LB Isolation**: Specify what type of load balancer isolation you want for "
+"the network: Shared or Dedicated."
+msgstr "**负载均衡隔离**:指定一种你希望的网络里的负载均衡隔离类型：共享的或单独的。"
+
+# a07b6242746142e18198a5bf7356254f
+#: ../../networking.rst:325
+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 "**单独的**:如果你选择了单独的负载均衡隔离类型，这个区域内的单独负载均衡设备资源池里就会分出一个设备来供使用。如果没有足够的设备，网络创建就会失败。如果要在高流量环境充分利用设备，单独的负载均衡设备是一个很好的选择。"
+
+# 1481728f6860436790f1bbdf1de1b4d0
+#: ../../networking.rst:333
+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 "**共享的**:如果你选择了共享的负载均衡设备， 这个区域内的共享负载均衡设备资源池里就会分出一个设备来供使用。CloudStack会将共享设备分配给不少于一定量的帐号共用，如果共享设备到达了最大数量，则这个设备不会再分配给新的帐号使用。"
+
+# 232eced6797144d7b6cb941627e8d2e6
+#: ../../networking.rst:341
+msgid "**Mode**: You can select either Inline mode or Side by Side mode:"
+msgstr "**模式**: 你可以选择 Inline mode 或 Side by Side 模式:"
+
+# 7684aca0c54c44fb9871f784de706a13
+#: ../../networking.rst:343
+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 "**Inline mode**: 这种模式只被Juniper SRX 和BigF5负载均衡设备支持。在Inline mode模式下，防火墙设备放在负载均衡设置的前端，这个防火墙作为进入流量的网关，所有的流量会被转发到后端的负载均衡设备上。在这种情况下，负载均衡不是直接连接到公网网络的。"
+
+# a5a609bdc196450fb249b0fed2b62618
+#: ../../networking.rst:351
+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 "*Side by Side**:在Side by Side模式下，防火墙设备和负载均衡设备是并列的。所以所有的流量都是直接到负载均衡设备而不经过防火墙。因此，负载均衡设备是直接暴露在公网中的。"
+
+# fddae68fcb5145e68976043eb707eed5
+#: ../../networking.rst:356
+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 "**关联的公网IP**:如果你想给来宾网络中的虚拟机直接分配公网IP，选择这个选项。这个选择只有在以下情况都满足时才有效："
+
+# b6cedd774fb4418b8c7f09c30e492ac5
+#: ../../networking.rst:360
+msgid "Guest network is shared."
+msgstr "来宾网络被共享"
+
+# c011835f1c314df2afcb840630a7ff99
+#: ../../networking.rst:362
+msgid "StaticNAT is enabled."
+msgstr "启用StaticNAT "
+
+# fcd9521a7c684aaaaacf045798eaaf33
+#: ../../networking.rst:364
+msgid "Elastic IP is enabled."
+msgstr "启用弹性IP"
+
+# 9818049dc1484f41b94a2c0c3904838d
+#: ../../networking.rst:366
+msgid ""
+"For information on Elastic IP, see `“About Elastic IP” <networking2.html"
+"#about-elastic-ip>`_."
+msgstr "更多信息，参考`“关于弹性IP” <networking2.html#about-elastic-ip>`_."
+
+# 6c9c68a68ab14d30a00460dd3b13f8a6
+#: ../../networking.rst:369
+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 master virtual router. "
+"CloudStack deploys the routers on different hosts to ensure reliability if "
+"one host is down."
+msgstr "**冗余路由性能**:这个选项只有在虚拟路由作为Source NAT提供者时才是可选的。如果你希望提供不间断的网络连接，选中这个选项，则系统会提供两个虚拟路由：一个主的，一个辅的。主虚拟路由负载收发用户虚拟机器的相关请深圳市。如主的路由DOWN掉时，由辅助路由升级为主路由接替工作。CloudStack 会将两个邪气路由分别部署在不同的主机上，以保证可用性。"
+
+# e5994ec5233c4a979624fa1fc8593822
+#: ../../networking.rst:380
+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 "**Conserve mode**: 这个选项表明是滞要使用Conserve模式。在这种模式下，网络资源只会分配给网络里第一个启动的虚拟机。当Conserve模式被关闭时，公网IP只能用于一个设备。比如，一个用于端口转发规则的公网IP不会被用于其它StaticNAT或是负载均衡服务。当Conserve模式启用时，你可以在同一个公网IP上定义多个服务。"
+
+# 6a2faa335b6b42588d747ac83fc4770b
+#: ../../networking.rst:390
+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 "如果StaticNAT启用后，不考虑conseve模式的状态，则此IP不会创建端口转发或是负载均衡规则。然而，你可以通过 createFirewallRule命令添加防火墙规则。"
+
+# 029a76d3e8444e15981d3fda29b8982e
+#: ../../networking.rst:395
+msgid "**Tags**: Network tag to specify which physical network to use."
+msgstr "**标签**:网络标签用于指定所要使用的物理网络。 "
+
+# e0d7d2460dba47d29922d3dcf0d16dc5
+#: ../../networking.rst:397
+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 "**默认外出策略**: 为防火墙配置默认的外出流量规则。选项有阻止和允许。如果没有特别制定策略的话，所有外出流量都是允许的。这表明，从这个方案创建的客户网络是允许所有外出流量的。"
+
+# 6cf9fba73dda48b8801d8608ce2f52a4
+#: ../../networking.rst:403
+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 "为了阻止客户网络的外出流量，选择阻止选项。在这种情况下，当你从一个隔离的客户网络配置一个外出规则时，添加一些特殊的规则以允许外出流量。"
+
+# fcfc7b9313f94bbda5ac1afbd8168f7c
+#: ../../networking.rst:407
+msgid "Click Add."
+msgstr "点击 添加"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/acquiring_an_ip_address.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/acquiring_an_ip_address.mo
new file mode 100644
index 0000000..7d9afb2
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/acquiring_an_ip_address.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/acquiring_an_ip_address.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/acquiring_an_ip_address.po
new file mode 100644
index 0000000..ad1020f
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/acquiring_an_ip_address.po
@@ -0,0 +1,80 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:05+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# aec0c098f53f452cb8665fc7b69cd182
+#: ../../networking/acquiring_an_ip_address.rst:18
+msgid "Acquiring a New IP Address"
+msgstr "获得一个新的IP地址"
+
+# 6113064b39bc4682869acf44286131ad
+#: ../../networking/acquiring_an_ip_address.rst:20
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# ccc7a493b9b940c2b706c15e852b3e93
+#: ../../networking/acquiring_an_ip_address.rst:22
+msgid "In the left navigation, choose Network."
+msgstr "在左侧的导航栏，选择网络。"
+
+# 9a6973f9449e4414a4643a6da352263e
+#: ../../networking/acquiring_an_ip_address.rst:24
+msgid "Click the name of the network where you want to work with."
+msgstr "点击拟修改的网络名称。"
+
+# beaa083fcce64bb48e44a47c9b4ab745
+#: ../../networking/acquiring_an_ip_address.rst:26
+msgid "Click View IP Addresses."
+msgstr "点击查看IP地址。"
+
+# 76867ce630364509a651c09137cab94e
+#: ../../networking/acquiring_an_ip_address.rst:28
+msgid "Click Acquire New IP."
+msgstr "点击获取新IP。"
+
+# 35698ea68aa24ff79ce9dc09c1d12caf
+#: ../../networking/acquiring_an_ip_address.rst:30
+msgid "The Acquire New IP window is displayed."
+msgstr "获取新IP的窗口会出现。"
+
+# 4819ef07622d41fd818aef83d9752ac2
+#: ../../networking/acquiring_an_ip_address.rst:32
+msgid "Specify whether you want cross-zone IP or not."
+msgstr "说明是否需要IP跨区。"
+
+# 342295d34e8e4252b2850d040aca7909
+#: ../../networking/acquiring_an_ip_address.rst:34
+msgid ""
+"If you want Portable IP click Yes in the confirmation dialog. If you want a "
+"normal Public IP click No."
+msgstr "如果你想作为 Portable IP则在确认窗口中点击Yes，如果你想作为正常的公共IP则点击No。"
+
+# 9a4837aaa4c940b78c8aa311245b748a
+#: ../../networking/acquiring_an_ip_address.rst:37
+msgid ""
+"For more information on Portable IP, see `\"Portable IPs\" <#portable-"
+"ips>`_."
+msgstr "关于便携式IP的更多信息，查看 `\"便携式IP\" <#portable-ips>`_."
+
+# 2ee8ad57fe20463893a86f3fe6eb669f
+#: ../../networking/acquiring_an_ip_address.rst:40
+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 "稍等一会，新的IP地址会出现，状态栏为会显示为分配。现在可以在端口转发或静态NAT规则中使用此IP地址了。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/advanced_zone_config.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/advanced_zone_config.mo
new file mode 100644
index 0000000..4b88509
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/advanced_zone_config.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/advanced_zone_config.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/advanced_zone_config.po
new file mode 100644
index 0000000..532e751
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/advanced_zone_config.po
@@ -0,0 +1,290 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:05+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# bcc6293e20c4470c938be75c5f17196e
+#: ../../networking/advanced_zone_config.rst:19
+msgid "Advanced Zone Physical Network Configuration"
+msgstr "高级区域物理网络的配置"
+
+# 65ad7a2b34f848cd9f21c2d2d51f06f6
+#: ../../networking/advanced_zone_config.rst:21
+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 "在使用复杂网络的区域中，你需要告知管理服务器，为了实现隔离不同类型的通讯，物理网络是如何设置的。"
+
+# 360066243e5b4ffc894a816b7e903923
+#: ../../networking/advanced_zone_config.rst:27
+msgid "Configure Guest Traffic in an Advanced Zone"
+msgstr "在高级域中设置客户通信"
+
+# ed393c6319d54e98ba44a7577315044b
+#: ../../networking/advanced_zone_config.rst:29
+msgid ""
+"These steps assume you have already logged in to the CloudStack UI. To "
+"configure the base guest network:"
+msgstr "下面的步骤假定你已经登录进入 CloudStack 的界面。设置基本的客户网络："
+
+# e3081f9e98e446d6855a2e72cba9849d
+#: ../../networking/advanced_zone_config.rst:32
+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 "在左边的导航栏，选择基础架构。在区域界面点击查看全部，然后点击你要添加网络的区域。"
+
+# 7e76a728cc8a43778d79ff577c30b3f2
+# 22748233c6cf4d06b5ba94259fe1e6e9
+#: ../../networking/advanced_zone_config.rst:35
+#: ../../networking/advanced_zone_config.rst:87
+msgid "Click the Network tab."
+msgstr "点击网络选项卡。"
+
+# 1c9241340a4d47a58af0ae3e10893ea1
+# 2c90664c2e9647c59a36e2a8f25d1a87
+#: ../../networking/advanced_zone_config.rst:37
+#: ../../networking/advanced_zone_config.rst:89
+msgid "Click Add guest network."
+msgstr "点击 添加来宾网络。"
+
+# cbb8ccbe13b34ed88593d4cf688451a1
+#: ../../networking/advanced_zone_config.rst:39
+msgid "The Add guest network window is displayed:"
+msgstr "添加来宾网络窗口显示："
+
+# ef5079e0fa7f4e5c8bac3410c02fa00f
+#: ../../networking/advanced_zone_config.rst:41
+msgid "|addguestnetwork.png|"
+msgstr "|addguestnetwork.png|"
+
+# ec8bb470f4924bd0af5b256494fbf0f5
+#: ../../networking/advanced_zone_config.rst:43
+msgid "Provide the following information:"
+msgstr "填写以下内容："
+
+# fa32f98dfeb04b68b79b01e6ef0e1fcf
+#: ../../networking/advanced_zone_config.rst:45
+msgid "**Name**: The name of the network. This will be user-visible"
+msgstr ""
+
+# f38e902b2f2c4fe78960c5d37c4a3609
+#: ../../networking/advanced_zone_config.rst:47
+msgid ""
+"**Display Text**: The description of the network. This will be user-visible"
+msgstr "**Display Text**：网络的描述。用户可见"
+
+# c1e74ac05b5a4eacb568d9201d733f74
+#: ../../networking/advanced_zone_config.rst:50
+msgid "**Zone**: The zone in which you are configuring the guest network."
+msgstr "**Zone**: 这里的区域是指你要配置客户网络的区域。"
+
+# 1bb07d209bd44e82b5f43507bb058db9
+#: ../../networking/advanced_zone_config.rst:52
+msgid ""
+"**Network offering**: If the administrator has configured multiple network "
+"offerings, select the one you want to use for this network"
+msgstr "**网络提议**: 如果管理员已经配置了多个网络方案，可以选择你需要的那个"
+
+# a33441c2621f415eb45dbc077a63e7bb
+#: ../../networking/advanced_zone_config.rst:55
+msgid "**Guest Gateway**: The gateway that the guests should use"
+msgstr "**Guest gateway**：虚拟机需要使用的网关"
+
+# 7f50db013a5941939cff931a256abb58
+#: ../../networking/advanced_zone_config.rst:57
+msgid ""
+"**Guest Netmask**: The netmask in use on the subnet the guests will use"
+msgstr "**Guest Netmask**：客户虚拟机会使用的子网掩码"
+
+# 186fd6f7a8de48fea845645978a6b332
+#: ../../networking/advanced_zone_config.rst:60
+msgid "Click OK."
+msgstr "点击确定。"
+
+# 6c2ac4e12f5f4a8c8788df54295b6e31
+#: ../../networking/advanced_zone_config.rst:64
+msgid "Configure Public Traffic in an Advanced Zone"
+msgstr "在高级区域中配置公共通信"
+
+# 7e91e673073d49e69f1ec92976a0d118
+#: ../../networking/advanced_zone_config.rst:66
+msgid ""
+"In a zone that uses advanced networking, you need to configure at least one "
+"range of IP addresses for Internet traffic."
+msgstr "在一个使用高级网络配置的区域中，你需要配置至少一个用于Internet通信的IP地址范围。"
+
+# c4aa53c641a347da9da814dfc32940a5
+#: ../../networking/advanced_zone_config.rst:71
+msgid "Configuring a Shared Guest Network"
+msgstr "配置共享的客户网络"
+
+# d5ac14718de945a5ae1eda9e0574d9cf
+#: ../../networking/advanced_zone_config.rst:73
+msgid "Log in to the CloudStack UI as administrator."
+msgstr "作为管理员登录到CloudStack用户界面。"
+
+# 9a3fd0f929374352a6cf52cc9790dfb1
+#: ../../networking/advanced_zone_config.rst:75
+msgid "In the left navigation, choose Infrastructure."
+msgstr "在左边的导航，选择基础架构。"
+
+# dbfd04e800154df197a15cb258be6d3f
+#: ../../networking/advanced_zone_config.rst:77
+msgid "On Zones, click View More."
+msgstr "在区域页面，点击查看全部。"
+
+# 7f633e5cc4504dfdaa399fcb8ab6c22e
+#: ../../networking/advanced_zone_config.rst:79
+msgid "Click the zone to which you want to add a guest network."
+msgstr "选择要添加客户网络的那个区域。"
+
+# 173dd051e7a1433d90061cca03962fc4
+#: ../../networking/advanced_zone_config.rst:81
+msgid "Click the Physical Network tab."
+msgstr "点击物理网络标签卡。"
+
+# e48da344ca7241429e6404ab7b137b39
+#: ../../networking/advanced_zone_config.rst:83
+msgid "Click the physical network you want to work with."
+msgstr "选择您要操作的物理网络。"
+
+# 0e03928f490a4bf5acd9028fed3fd8d8
+#: ../../networking/advanced_zone_config.rst:85
+msgid "On the Guest node of the diagram, click Configure."
+msgstr "在客户节点界面，点击配置。"
+
+# 9272a3e9c02b4d3fb7e88cd90f63e56f
+#: ../../networking/advanced_zone_config.rst:91
+msgid "The Add guest network window is displayed."
+msgstr "现实添加客户网络窗口。"
+
+# 271290c4c54643a9a8cc203840b4bb3b
+#: ../../networking/advanced_zone_config.rst:93
+msgid "Specify the following:"
+msgstr "指定以下信息："
+
+# a69cf77fdc48441b9a0e41233bf3d4db
+#: ../../networking/advanced_zone_config.rst:95
+msgid "**Name**: The name of the network. This will be visible to the user."
+msgstr "**Name**: 要建立的网络的名字。这个是用户可见的"
+
+# 924d5df6b0f643c3ad34cdfa02548391
+#: ../../networking/advanced_zone_config.rst:97
+msgid ""
+"**Description**: The short description of the network that can be displayed "
+"to users."
+msgstr "**描述**: 提供一个简短的方案描述。 "
+
+# 8c68c64196cb4b548290e4a3e9851553
+#: ../../networking/advanced_zone_config.rst:100
+msgid "**VLAN ID**: The unique ID of the VLAN."
+msgstr "**VLAN ID**: VLAN 的ID。"
+
+# 0711300a6023445c91c8a4d7926a8e04
+#: ../../networking/advanced_zone_config.rst:102
+msgid "**Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr "**Isolated VLAN ID**: 二级独立 VLAN 的 ID。"
+
+# dbbc4b85106a407f9bb4532a5c1a40a2
+#: ../../networking/advanced_zone_config.rst:105
+msgid "**Scope**: The available scopes are Domain, Account, Project, and All."
+msgstr "**Scope**: 可用的范围，包括域，帐户，项目和其他所以。"
+
+# 46fd996ba0b241efa0f21c9f22c7c77d
+#: ../../networking/advanced_zone_config.rst:108
+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 "**Domain**: 域，指定客户网络范围的域。指定域中的网络相对其他域是隔离不可见的。如果指定子域访问，域中的客户网络将在所有的子域中可用。"
+
+# 79bd2bf86f74472db3b4cba26ef143dd
+#: ../../networking/advanced_zone_config.rst:114
+msgid ""
+"**Account**: The account for which the guest network is being created for. "
+"You must specify the domain the account belongs to."
+msgstr "**Account**: 这里的帐户是为建立客户网络所指定的。必须指定域中所属的帐户。"
+
+# f3de2d8830134ab195b04b7e4b74b215
+#: ../../networking/advanced_zone_config.rst:118
+msgid ""
+"**Project**: The project for which the guest network is being created for. "
+"You must specify the domain the project belongs to."
+msgstr "**Project**: 项目是客户网络所建立的项目。必须为这个项目指定域。"
+
+# e03c5c4ff8d646cdb1a4029a794765e5
+#: ../../networking/advanced_zone_config.rst:122
+msgid ""
+"**All**: The guest network is available for all the domains, account, "
+"projects within the selected zone."
+msgstr "**All**: 选择它，会让客户网络对这个区域（Zone）中的所有域，帐户和项目都可用。"
+
+# 74217dea4b9c4d8faa89e1ea6b2c754e
+#: ../../networking/advanced_zone_config.rst:125
+msgid ""
+"**Network Offering**: If the administrator has configured multiple network "
+"offerings, select the one you want to use for this network."
+msgstr "**网络提议**: 如果管理员已经配置了多个网络方案，可以选择你需要的那个。"
+
+# 587275eb7b1249e590763c8b0fb81d41
+#: ../../networking/advanced_zone_config.rst:129
+msgid "**Gateway**: The gateway that the guests should use."
+msgstr "**Guest gateway**: 虚拟机需要使用的网关。"
+
+# 8123de4fbb1d4a1cba01cb099365b448
+#: ../../networking/advanced_zone_config.rst:131
+msgid "**Netmask**: The netmask in use on the subnet the guests will use."
+msgstr "**Netmask**: 虚拟机子网要使用的网络掩码。"
+
+# 129d7c2b8ec442cb802ec894eb871959
+#: ../../networking/advanced_zone_config.rst:133
+msgid ""
+"**IP Range**: A range of IP addresses that are accessible from the Internet "
+"and are assigned to the guest VMs."
+msgstr "**IP Range**: 定义公网IP范围，这些IP用来访问公网或是从公网访问客户虚拟机。"
+
+# 8ea844eb28e94825bdefeba5cc1e143c
+#: ../../networking/advanced_zone_config.rst:136
+msgid ""
+"If one NIC is used, these IPs should be in the same CIDR in the case of "
+"IPv6."
+msgstr "如果使用了网卡，这些IP应该在相同的IPv6的CIDR中。"
+
+# 1a2dacdd2a984c978ad1455bdb6c04b8
+#: ../../networking/advanced_zone_config.rst:139
+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 "**IPv6 CIDR**: 用于定义网络子网的网络前缀。"
+
+# d17e32d82ae849139dda243c9ddc9676
+#: ../../networking/advanced_zone_config.rst:144
+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 "**网络域**: 如果你想为客户虚机网络定义一个域名，在此处输入后缀名。"
+
+# e200da9c829a41109b13173bce7f11ca
+#: ../../networking/advanced_zone_config.rst:148
+msgid "Click OK to confirm."
+msgstr "点击确定。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/basic_zone_config.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/basic_zone_config.mo
new file mode 100644
index 0000000..776cd39
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/basic_zone_config.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/basic_zone_config.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/basic_zone_config.po
new file mode 100644
index 0000000..aefa328
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/basic_zone_config.po
@@ -0,0 +1,32 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:05+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# bf16fca54893437db5aad5aa3f2e6e2c
+#: ../../networking/basic_zone_config.rst:19
+msgid "Basic Zone Physical Network Configuration"
+msgstr "基本区域物理网络配置"
+
+# 153ba46cfcf14ac28f2db2730d2e43af
+#: ../../networking/basic_zone_config.rst:21
+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 "在一个基本的网络中，物理网络的配置非常直接明了。你只需要配置一个客户网络（虚拟）以承载由客户虚拟机产生的流量。当你首次增加一个区域（Zone）到 CloudStack 中，你通过添加域（Add Zone）页面来设置客户网络（虚拟）。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/dns_and_dhcp.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/dns_and_dhcp.mo
new file mode 100644
index 0000000..0b3362f
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/dns_and_dhcp.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/dns_and_dhcp.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/dns_and_dhcp.po
new file mode 100644
index 0000000..fdd4239
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/dns_and_dhcp.po
@@ -0,0 +1,30 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:05+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 727de7b64d0e4c34bddda54359ed846d
+#: ../../networking/dns_and_dhcp.rst:18
+msgid "DNS and DHCP"
+msgstr "DNS和DHCP"
+
+# f58ccb2c24bb47c0872a16c74d47f121
+#: ../../networking/dns_and_dhcp.rst:20
+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 "虚拟路由器为来宾提供DNS和DHCP服务。它将DNS请求代理到在可用区域中配置的DNS服务器。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/elastic_ips.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/elastic_ips.mo
new file mode 100644
index 0000000..35dc00b
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/elastic_ips.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/elastic_ips.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/elastic_ips.po
new file mode 100644
index 0000000..e8d264e
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/elastic_ips.po
@@ -0,0 +1,157 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:05+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 68f25b7a2e514065b563d7ccdd72f355
+#: ../../networking/elastic_ips.rst:18
+msgid "About Elastic IPs"
+msgstr ""
+
+# bf34049aef4a4cddb2aa0169d49b5281
+#: ../../networking/elastic_ips.rst:20
+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 is down, the IP address can be "
+"reassigned to a new VM in your account."
+msgstr "弹性IP（EIP）地址是指与帐户关联的IP地址，能起到静态IP地址的作用。帐户所有者能完全控制隶属于此账户的弹性IP。作为帐户拥有者，你可以从你帐户的EIP池中选择一个IP分配给虚拟机。如果后续需要，你可以继续分配此IP地址给另一个虚拟机。在VM宕机时，此功能特别有用。此IP地址可以重新指定给一个新的虚拟机，而不是取代已经宕机的虚拟机。"
+
+# 8b249afbc2664b01a564524559d5c5fd
+#: ../../networking/elastic_ips.rst:29
+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 "与公共IP地址一样，弹性IP地址通过使用静态NAT关联至与之相关的私有IP地址。在起用了EIP的基础域中，EIP的服务与静态NAT的服务一一对应。默认的网络方案，默认共享EIP与负载均衡网络方案，在区域部署了NetScaler设备的前提下，能够提供EIP以及ELB网络服务。参见以下更详细的说明。"
+
+# deef19d6b1414dbb967743f1b7cef2df
+#: ../../networking/elastic_ips.rst:37
+msgid "|eip-ns-basiczone.png|"
+msgstr "|eip-ns-basiczone.png|"
+
+# a1f02d4922ed4bbb8941ccc048f0b0b4
+#: ../../networking/elastic_ips.rst:39
+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 data center goes through the firewall."
+msgstr "在图中，NetScaler设备对CloudStack的实例而言是一个默认的入口或出口，防火墙是剩余数据中心的出口或入口。Netscaler对来宾网络提供负载均衡以及静态NAT的服务。在机架和管理服务器上，来宾流量是不同的子网或VLAN。在数据中心的核心交换机的基础路由策略是通过NetScaler转发公共流量，其他数据中心的流量则通过防火墙。"
+
+# 28c78bf967714b33884e97cfa4ca307b
+#: ../../networking/elastic_ips.rst:48
+msgid "The EIP work flow is as follows:"
+msgstr "EIP的工作流如下："
+
+# 773cd4ac9b6d4973832aafd2d0cf2f9e
+#: ../../networking/elastic_ips.rst:50
+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 "当部署一个用户虚拟机时，会从区域配置的IP中自动获得一个公共IP。这个IP为虚拟机帐户所拥有。"
+
+# 23a70289953d415c81e8dd6ebc86423c
+#: ../../networking/elastic_ips.rst:54
+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 "每一个虚拟机都有自己的私有IP。当来客户虚拟机启动时，通过使用在公共IP和私有IP之间的入口网络地址转换（INAT）以及预留地址转换（RNAT），NetScaler设备可以提供静态NAT"
+
+# bfa50768ea9b496599aa1804e3437f25
+#: ../../networking/elastic_ips.rst:60
+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 "入口网络地址转换（INAT）是NetScaler支持的一类NAT类型，在此类型中，来自公共网络（如Internet)的数据包中的目标IP地址被私有网络中虚拟机的私有地址取代。预留地址转换（RNAT）也是NetScaler支持的一类NAT类型，私有网络中虚拟机产生的数据包中的源IP地址被公共IP地址取代。"
+
+# cef50f723bd34b298098fab0ed2c2328
+#: ../../networking/elastic_ips.rst:67
+msgid "This default public IP will be released in two cases:"
+msgstr "默认的公共IP在两种情况下会被释放："
+
+# 954fad75b2bd41d1b16f50f819a7e300
+#: ../../networking/elastic_ips.rst:69
+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 "当虚拟机停止时。当虚拟机启动时，可以重新获取一个新的公共IP，并不必须是从公共IP地址池中最初分配的那一个。"
+
+# a5713ccdbc7f41dea9e1fb5bd2a81337
+#: ../../networking/elastic_ips.rst:73
+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 "当用户获取公共IP（弹性IP）时。这些公共IP与帐户相关联，但不与任何私有IP相关。然而，用户可以开启静态NAT将帐户中虚拟机的私有IP与之关联。对应公共IP的静态NAT规则可随时取消。当静态NAT关闭时，会从地址池中分配的一个新的公共IP，并不必须是最初分配的那一个。"
+
+# a8f5524c22bd4ddf82fd8d2d6240b94f
+#: ../../networking/elastic_ips.rst:81
+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 and enable static NAT."
+msgstr "对部署而言，公共IP会受限于资源，可以灵活的选择默认不分配公共IP。可以在开启了EIP的基础区域中，通过关联公共IP选项来打开或关闭自动公共IP指定。如果在创建网络方案时，你关闭了自动公共IP指定，则在使用此网络方案部署时，仅会分配一个私有IP给虚拟机。此后，用户虚拟机可以获取一个IP，并可以开启静态NAT。"
+
+# 89cea0807df84e08bd3c61dbf7579d80
+#: ../../networking/elastic_ips.rst:90
+msgid ""
+"For more information on the Associate Public IP option, see `\"Creating a "
+"New Network Offering\" <networking.html#creating-a-new-network-offering>`_."
+msgstr "要了解更多关于关联公共IP的选项，请参考`\"创建一个新的网络方案\" <networking.html#creating-a-new-network-offering>`_."
+
+# e8e0a7038ebb4ea181ba58c3f4cdc0ed
+#: ../../networking/elastic_ips.rst:94
+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 "设计关联公共IP的功能，仅是为使用用户虚拟机。系统虚拟机仍然默认会获取公共IP和私有IP，与网络配置并不相关。"
+
+# 116e2d3d7abc4e4b89e08770c938b985
+#: ../../networking/elastic_ips.rst:98
+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 "在基础区域中，使用默认具有EIP和ELB服务的网络方案来创建共享网络时，仍然会给每一个用户虚拟机分配公共IP。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/external_firewalls_and_load_balancers.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/external_firewalls_and_load_balancers.mo
new file mode 100644
index 0000000..c9837aa
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/external_firewalls_and_load_balancers.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/external_firewalls_and_load_balancers.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/external_firewalls_and_load_balancers.po
new file mode 100644
index 0000000..384282a
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/external_firewalls_and_load_balancers.po
@@ -0,0 +1,1056 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:05+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 9b2c57c96864404ab39ea18532184a3c
+#: ../../networking/external_firewalls_and_load_balancers.rst:18
+msgid "External Firewalls and Load Balancers"
+msgstr "外部防火墙及负载均衡"
+
+# 406fa3a599d74b6fb0f6a893d839784a
+#: ../../networking/external_firewalls_and_load_balancers.rst:20
+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 "CloudStack允许通过外部的Jniper SRX 设备和外部NetScaler设备或网关负载均衡设备和负载均衡服务。在此情形下，虚拟机使用SRX作为网关。"
+
+# e50bcd9fe60e430d85efc883354624a5
+#: ../../networking/external_firewalls_and_load_balancers.rst:27
+msgid "About Using a NetScaler Load Balancer"
+msgstr "关于使用NetScaler负载均衡器"
+
+# 1cf32061da5449a2a6dc5887c27b0d72
+#: ../../networking/external_firewalls_and_load_balancers.rst:29
+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 "在区域中，或高级区域使用隔离网络时，CloudStack支持思杰的NetScaler作为外部网络设备元素作为负责均衡。拟通过其他方案提供负载均衡而不是CloudStack的虚拟路由器时，就可以建立一个外部负载均衡器"
+
+# 188f8456b75c41ffadbc92d637327f54
+#: ../../networking/external_firewalls_and_load_balancers.rst:35
+msgid ""
+"In a Basic zone, load balancing service is supported only if Elastic IP or "
+"Elastic LB services are enabled."
+msgstr "在基础区域中，仅在弹性IP或弹性负载均衡服务开启时，才支持负载均衡服务"
+
+# 7189603a0b934b4b8f4de77ccc774586
+#: ../../networking/external_firewalls_and_load_balancers.rst:38
+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 device providing "
+"EIP/ELB, layer 3 router must have a policy-based routing. A policy-based "
+"route must be set up so that all traffic originated from the guest VM's are "
+"directed to NetScaler device. This is required to ensure that the outbound "
+"traffic from the guest VM's is routed to a public IP by using NAT.For more "
+"information on Elastic IP, see `\"About Elastic IP\" <#about-elastic-ip>`_."
+msgstr "在基础域中使用NetScaler负载均衡提供EIP或ELB服务时，确保所有的客户虚拟机流量必须通过NetScaler设备进出。当入流量通过NetScaler设备时流量通过使用NAT协议被路由，此NAT协议依赖于公共IP到私有IP的配置。来自客户虚拟机的流量通常要经过3层路由器，为确保出流量通过提供EIP/ELB的NetScaler设备，3层路由器，必须具有基础策略。必有设立一个具有基础策略的路由器可保证所有客户机的流量都能转向NetScaler设备。这也需要确保客户虚拟机的出流量通过使用NAT被路由到公共IP。关于EIP的更多信息，参看`\"关于EIP\" <#about-elastic-ip>`_."
+
+# baddaa181f054bb5b0b41e5dcce1387e
+#: ../../networking/external_firewalls_and_load_balancers.rst:52
+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 "NetScaler可以设置成直通模式。它必须在区域中部署客户虚拟机负载均衡规则之前加入。"
+
+# 263c8a9eb9d147ad91ae71970d65bd41
+#: ../../networking/external_firewalls_and_load_balancers.rst:56
+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 "CloudStack中NetScaler的功能作用与CloudStack文档中说明的使用F5 外部负载均衡器的功能作用相同。一点差别就是，F5支持路由域名，而NetScaler无此功能。NetScaler也不可以用作防火墙。"
+
+# 79187d2fbfa743c39e8c524304235dc2
+#: ../../networking/external_firewalls_and_load_balancers.rst:61
+msgid ""
+"To install and enable an external load balancer for CloudStack management, "
+"see External Guest Load Balancer Integration in the Installation Guide."
+msgstr "为CLOUDSTACK管理端安装和启用外部负载均衡功能，参阅安装文档里的外部客户负载均衡。"
+
+# d3c851ee525b49599c01646d4d1e2dd5
+#: ../../networking/external_firewalls_and_load_balancers.rst:65
+msgid ""
+"The Citrix NetScaler comes in three varieties. The following summarizes how "
+"these variants are treated in CloudStack."
+msgstr ""
+
+# 64aec7c1c44049498dcf6c10b4fa5605
+#: ../../networking/external_firewalls_and_load_balancers.rst:68
+msgid "**MPX**"
+msgstr ""
+
+# b8df1ce8dfa14d8c8ecc441c6f71748f
+#: ../../networking/external_firewalls_and_load_balancers.rst:70
+msgid ""
+"Physical appliance. Capable of deep packet inspection. Can act as "
+"application firewall and load balancer"
+msgstr "物理应用。能够进行深度数据包检测。可作为防火墙和负载均衡应用。"
+
+# 3a1ec0e897e34118a0fbeb78f64a544a
+#: ../../networking/external_firewalls_and_load_balancers.rst:73
+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 "在高级区域中，完全支持负载均衡功能，没有限制。在基础区域中，也提供静态NAT，EIP，ELB功能。"
+
+# 68d5e27c550d40cd921b14324d33692a
+#: ../../networking/external_firewalls_and_load_balancers.rst:77
+msgid "**VPX**"
+msgstr ""
+
+# 886b66d79fd049739f35d53684946f35
+#: ../../networking/external_firewalls_and_load_balancers.rst:79
+msgid ""
+"Virtual appliance. Can run as VM on XenServer, ESXi, and Hyper-V "
+"hypervisors. Same functionality as MPX"
+msgstr "虚拟应用，可以运行在XenServer，ESXi以及Hyper-V上虚拟机上。与MPX功能相同。"
+
+# acdf8d15b2b740579349caa99d8ff14f
+#: ../../networking/external_firewalls_and_load_balancers.rst:82
+msgid ""
+"Supported on ESXi and XenServer. Same functional support as for MPX. "
+"CloudStack will treat VPX and MPX as the same device type."
+msgstr "在ESXi和XenServer上支持。对MPX也支持一些功能。CloudStack将VPX和MPX作为同一类型的设备看待。"
+
+# 632775a416fd40bfb11895ae39b883e9
+#: ../../networking/external_firewalls_and_load_balancers.rst:85
+msgid "**SDX**"
+msgstr ""
+
+# 94896445c73d42c7a8a8b30da3d762a9
+#: ../../networking/external_firewalls_and_load_balancers.rst:87
+msgid ""
+"Physical appliance. Can create multiple fully isolated VPX instances on a "
+"single appliance to support multi-tenant usage"
+msgstr "物理应用。可以在单个应用上创建多个完全隔离的VPX实例，以支持多客户使用。"
+
+# 7272ab89523e416fba357a4ceb24b459
+#: ../../networking/external_firewalls_and_load_balancers.rst:90
+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 "CloudStack会动态分配，配置，管理在SDX上的虚拟机实例的生命周期。分配的实例会自动加入到CloudStack，不需要管理员进行手动配置。一旦一个VPX实例加入到CloudStack，将会认为是ESXi主机上的一个VPX。"
+
+# e712ff0906b7463083ac7a8f9b19847c
+#: ../../networking/external_firewalls_and_load_balancers.rst:98
+msgid "Configuring SNMP Community String on a RHEL Server"
+msgstr "在RHEL服务器上配置SNMP社区字符串"
+
+# a0e11ba7efae4e63a0cd9eb015162722
+#: ../../networking/external_firewalls_and_load_balancers.rst:100
+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 "SNMP社区字符串类似于用户ID或用户密码，用来登录网络设备，如路由器。这类字符串随着所有的SNMP请求发送。如果社区字符串正确，设备将反馈相应的字符串若不正确，设备将丢弃请求，不进行处理。"
+
+# d9a8fc53fc4949bda74cb44fbcb04146
+#: ../../networking/external_firewalls_and_load_balancers.rst:106
+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 "NetScaler设备使用SNMP与虚拟机进行通讯。为保证NetScaler设备与RHEL机器之间安全的通讯，必须安装并配置社区字符串。"
+
+# 9f7d96642a9b435ab7687ecf88e6f6de
+#: ../../networking/external_firewalls_and_load_balancers.rst:110
+msgid ""
+"Ensure that you installed SNMP on RedHat. If not, run the following command:"
+msgstr "确保在RedHat上安装了SNMP，如果没有，执行以下命令:"
+
+# 657a8fba85b14585be4a9165ba95128b
+#: ../../networking/external_firewalls_and_load_balancers.rst:117
+msgid ""
+"Edit the /etc/snmp/snmpd.conf file to allow the SNMP polling from the "
+"NetScaler device."
+msgstr "编辑/etc/snmp/snmpd.conf 文件，以允许来自NetScaler设备的SNMP查询"
+
+# 752d34a607b64dbea0348f5551d5cebc
+#: ../../networking/external_firewalls_and_load_balancers.rst:120
+msgid ""
+"Map the community name into a security name (local and mynetwork, depending "
+"on where the request is coming from):"
+msgstr "映射社区名到一个安全的名字（本地，我的网络，依赖于其来源）"
+
+# 07b1fa6ac91c4aa186c434d633b0384e
+#: ../../networking/external_firewalls_and_load_balancers.rst:124
+msgid ""
+"Use a strong password instead of public when you edit the following table."
+msgstr "编辑下表时，使用一个强密码"
+
+# f8acb0abc31c4fd0ab9300c705ba1f72
+#: ../../networking/external_firewalls_and_load_balancers.rst:133
+msgid "Setting to 0.0.0.0 allows all IPs to poll the NetScaler server."
+msgstr "设置0.0.0.0以允许所有的IP都可以查询NetScaler设备"
+
+# 327a4b1c1e4d429c83dc1e1628f8376a
+#: ../../networking/external_firewalls_and_load_balancers.rst:135
+msgid "Map the security names into group names:"
+msgstr "映射一个安全名到组名"
+
+# 193cbe00950147958924521840ba4405
+#: ../../networking/external_firewalls_and_load_balancers.rst:145
+msgid "Create a view to allow the groups to have the permission to:"
+msgstr "创建一个视图，以允许组有权限执行："
+
+# 39191ba80aa24e32898e8a79892fb7cf
+#: ../../networking/external_firewalls_and_load_balancers.rst:151
+msgid ""
+"Grant access with different write permissions to the two groups to the view "
+"you created."
+msgstr "授权不同的写权限给二个组及你创建的视图"
+
+# ca08ac1ab89442c9a42c7d59efa70e6b
+#: ../../networking/external_firewalls_and_load_balancers.rst:160
+msgid "Unblock SNMP in iptables."
+msgstr "在iptalbes中解除对SNMP的锁定。"
+
+# f161affb624f4139be0750f3dc19f505
+#: ../../networking/external_firewalls_and_load_balancers.rst:166
+msgid "Start the SNMP service:"
+msgstr "开启SNMP服务："
+
+# 60eb8801ebf44b97b3b4cc63348013b6
+#: ../../networking/external_firewalls_and_load_balancers.rst:172
+msgid ""
+"Ensure that the SNMP service is started automatically during the system "
+"startup:"
+msgstr "确保在系统启动时，SNMP服务能够自动启动。"
+
+# 8893688efc574dbfba90b00df9f467bd
+#: ../../networking/external_firewalls_and_load_balancers.rst:181
+msgid "Initial Setup of External Firewalls and Load Balancers"
+msgstr "初始化安装外部防火墙和负载均衡"
+
+# 2149019287d549649f77e49102f3a8e2
+#: ../../networking/external_firewalls_and_load_balancers.rst:183
+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 "当为一个新帐户创建一个虚拟机时，CloudStack会设置程序以让外部防火墙和负载均衡与虚拟机共同工作。会在防火墙上创建以下对象："
+
+# 7bec0089c55040c9bcc3b75a4ce9ae0b
+#: ../../networking/external_firewalls_and_load_balancers.rst:187
+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 "一个新的逻辑接口，用以连接帐户的私有VLAN。接口的IP通常是私有帐户私有子网的第一个IP。"
+
+# 5d690ff5c70b4951a41d9ccf663e1e5d
+#: ../../networking/external_firewalls_and_load_balancers.rst:191
+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 "一个源NAT规则转发帐户从私有VLAN到公共网络的的出口流量，使用帐户的公共IP地址作为源地址。"
+
+# a8b478c2d3334a0aa56507a774978095
+#: ../../networking/external_firewalls_and_load_balancers.rst:195
+msgid ""
+"A firewall filter counter that measures the number of bytes of outgoing "
+"traffic for the account"
+msgstr "防火墙过滤计数器计量帐户出口流量的字节数"
+
+# 438d673ffaa3412c98761796e1c9043c
+#: ../../networking/external_firewalls_and_load_balancers.rst:198
+msgid "The following objects are created on the load balancer:"
+msgstr "以下对象会在负载均衡上创建："
+
+# 07491865d4a3476293c53ae24c343c78
+#: ../../networking/external_firewalls_and_load_balancers.rst:200
+msgid "A new VLAN that matches the account's provisioned Zone VLAN"
+msgstr "匹配帐户区域VLAN的私有VLAN。"
+
+# 3691e62805b34e95acd2ff232154ca0d
+#: ../../networking/external_firewalls_and_load_balancers.rst:202
+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 "一个VLAN的自有IP。经常是帐户私有子网的第二个IP。"
+
+# 1e387fca9feb4a08825eb2dfe3547fb0
+#: ../../networking/external_firewalls_and_load_balancers.rst:207
+msgid "Ongoing Configuration of External Firewalls and Load Balancers"
+msgstr "继续配置外部防火墙和负载均衡"
+
+# 133336c3018e4957ba148ad3a8f85ed4
+#: ../../networking/external_firewalls_and_load_balancers.rst:209
+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 objects:"
+msgstr "增加的用户行为(如设置端口转发)会引起防火墙和负载均衡的程序化。一个用户可以请求增加公共IP地址以及转发使用此公共IP地址的虚拟机接受到的流量。这是通过静态NAT功能完成的，静态NAT将一个公共IP地址映射给一个虚拟机，并指定一组特定协议，开放一组特定端口。当静态NAT建立好之后，CLOUDSTACK会在区域的外部防火墙上通过程序定制如下对象："
+
+# cfcd0d08f25142019221555a1a499683
+#: ../../networking/external_firewalls_and_load_balancers.rst:218
+msgid ""
+"A static NAT rule that maps the public IP address to the private IP address "
+"of a VM."
+msgstr "一条静态NAT规则将虚拟机的私有IP地址映射到公共IP地址。"
+
+# 76e196b931384143a2f1b65467f003dd
+#: ../../networking/external_firewalls_and_load_balancers.rst:221
+msgid ""
+"A security policy that allows traffic within the set of protocols and port "
+"ranges that are specified."
+msgstr "一个安全策略可以允许说明的协议和端口范围内的流量通过。"
+
+# b6b755f7fb5a4d4d9495bfe3b0eac10e
+#: ../../networking/external_firewalls_and_load_balancers.rst:224
+msgid ""
+"A firewall filter counter that measures the number of bytes of incoming "
+"traffic to the public IP."
+msgstr "防火墙过滤计数器计量到达此公共IP的流量"
+
+# 077fa026b5954737b4af75e98a4dd1e8
+#: ../../networking/external_firewalls_and_load_balancers.rst:227
+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 "通过源NAT，静态NAT以及负载均衡规则进出的字节数均被计量并保存在每一个外部设备中。按一定的规则对这些数据进行收集，并将其存储在CloudStack的数据库中。"
+
+# a882754de1c64a389513a78637f3325d
+#: ../../networking/external_firewalls_and_load_balancers.rst:234
+msgid "Load Balancer Rules"
+msgstr "负载均衡规则"
+
+# 9b95ee51dc6e4026905b950584948d63
+#: ../../networking/external_firewalls_and_load_balancers.rst:236
+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 "一个CloudStack的用户或管理员可以创建负载均衡规则以平衡一个公共IP地址收到的针对一个或多个虚拟机的外部流量。一个用户可以创建一条规则，说明一个算法，并将其指定给一部分虚拟机。"
+
+# 7ac5de99c5694e0b89ceb6d4c39e0dfb
+#: ../../networking/external_firewalls_and_load_balancers.rst:242
+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 "如果你创建了一个负载均衡规则且使用包括外部负载均衡设备的网络服务方案，如包括NetScaler，但随后将网络方案改成使用CloudStack的虚拟路由器，则你必须在虚拟路由器上创建一个防火墙规则，这些防火墙规则与已经设置的负载均衡规则一一对应，只有这样，才能使那些负载均衡规则继续起作用。"
+
+# b09aa6c58aa84b8f89b3293a64ca17fd
+#: ../../networking/external_firewalls_and_load_balancers.rst:253
+msgid "Adding a Load Balancer Rule"
+msgstr "增加一条负载均衡规则"
+
+# 1bc40a00c2f341118db65e97bbbcf986
+#: ../../networking/external_firewalls_and_load_balancers.rst:255
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# 57f7d8a61234427abc813c4208e84192
+#: ../../networking/external_firewalls_and_load_balancers.rst:257
+msgid "In the left navigation, choose Network."
+msgstr "在左侧的导航栏，选择网络。"
+
+# d947318aba7746718816eb5c7e29e9b1
+#: ../../networking/external_firewalls_and_load_balancers.rst:259
+msgid ""
+"Click the name of the network where you want to load balance the traffic."
+msgstr "点击拟进行负载均衡的网络名称"
+
+# 20fc7dedf2cf482d94d8977ac64c6b0d
+#: ../../networking/external_firewalls_and_load_balancers.rst:262
+msgid "Click View IP Addresses."
+msgstr "点击查看IP地址。"
+
+# aff4544b414847af82ceceb0bd4e3b55
+#: ../../networking/external_firewalls_and_load_balancers.rst:264
+msgid ""
+"Click the IP address for which you want to create the rule, then click the "
+"Configuration tab."
+msgstr "点击你希望创建规则的IP地址，然后点击配置"
+
+# a84c70dc6b4f4d7c8f5a2d1f82b59355
+#: ../../networking/external_firewalls_and_load_balancers.rst:267
+msgid "In the Load Balancing node of the diagram, click View All."
+msgstr "在图的负载均衡节点点上，点击 查看全部。"
+
+# 698c929938644fa88bcaa781f68ea4e7
+#: ../../networking/external_firewalls_and_load_balancers.rst:269
+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 "在基础区域中，在不需要或不选择IP的条件下，你可以创建一条负载均衡规则。当你创建负载均衡规则时，CloudStack会内部指定一个IP地址。当规则创建完成时，IP地址会在IP地址页列出来。"
+
+# 2991ed0062324ee88859d10be3c6d280
+#: ../../networking/external_firewalls_and_load_balancers.rst:274
+msgid ""
+"To do that, select the name of the network, then click Add Load Balancer "
+"tab. Continue with #7."
+msgstr "为此，选择网络名称，点击 增加负载均衡。按#7继续进行配置。"
+
+# f62541afe2764660ba42de5ab1903be0
+#: ../../networking/external_firewalls_and_load_balancers.rst:277
+msgid "Fill in the following:"
+msgstr "填写以下内容："
+
+# 9d106d6a229045acbfc2622c0c395bd9
+#: ../../networking/external_firewalls_and_load_balancers.rst:279
+msgid "**Name**: A name for the load balancer rule."
+msgstr "**名称**: 负载均衡规则的名称。"
+
+# 75090eb93c0c438fbb12cc3c26d20ef9
+#: ../../networking/external_firewalls_and_load_balancers.rst:281
+msgid "**Public Port**: The port receiving incoming traffic to be balanced."
+msgstr "**公共端口**: 这个端口接受到负载均衡的进入流量。"
+
+# 61dc53b8703148608a98d96de9b2f3f7
+#: ../../networking/external_firewalls_and_load_balancers.rst:284
+msgid ""
+"**Private Port**: The port that the VMs will use to receive the traffic."
+msgstr "**私有端口**: 虚拟机会使用此端口接收流量。"
+
+# 9e98c799101c44728527da77d95553ee
+#: ../../networking/external_firewalls_and_load_balancers.rst:287
+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 "**算法**: 选择让CloudStack使用的负载均衡算法。CloudStack各类已知的算法，如果不熟悉那些选项，通过goole搜索会发现大量信息。"
+
+# 1fc198ccbf4e4718beba8aaec97b2a38
+#: ../../networking/external_firewalls_and_load_balancers.rst:292
+msgid ""
+"**Stickiness**: (Optional) Click Configure and choose the algorithm for the "
+"stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr "**粘性**: (可选) 点击配置，为粘性策略选择一个算法。可参见为负载均衡规则制定的粘性会话策略。"
+
+# 8d672e758cc24f2da82cbdd82c83ea21
+#: ../../networking/external_firewalls_and_load_balancers.rst:296
+msgid ""
+"**AutoScale**: Click Configure and complete the AutoScale configuration as "
+"explained in :ref:`conf-autoscale`."
+msgstr "**自动缩放**：点击配置完成自动缩放配置，在 :ref:`conf-autoscale`中有介绍。"
+
+# 33ab79892f344fde975f3d6c32cd9b12
+#: ../../networking/external_firewalls_and_load_balancers.rst:299
+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 "**健康检查**：(可选，只针对NetScaler的负载均衡设备)点击配置并填写健康检查特性，参见15.16.5.3 负载均衡规则的健康检查。参见 :ref:`health-check`."
+
+# d643db9463b745c7ac1f19daad8358dd
+#: ../../networking/external_firewalls_and_load_balancers.rst:303
+msgid ""
+"**Ping path (Optional)**: Sequence of destinations to which to send health "
+"check queries. Default: / (all)."
+msgstr "**ping 路径(可选)**: 需要发送健康检查的目的地顺序。默认：/ (all)。"
+
+# b33a72d1050241329dd52806584f0b49
+#: ../../networking/external_firewalls_and_load_balancers.rst:306
+msgid ""
+"**Response time (Optional)**: How long to wait for a response from the "
+"health check (2 - 60 seconds). Default: 5 seconds."
+msgstr "**响应时间(可选)**: 从健康检查返回的响应时间(2-60秒)，默认为5秒。"
+
+# 885f1763ea71493ea93ba841259240b3
+#: ../../networking/external_firewalls_and_load_balancers.rst:309
+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 "**间隔时间(可选)**: 健康检查的间隔时间(1秒-5分)）。默认值在全局参数 lbrule\\_health check\\_time\\_interval"
+
+# 82dd529deb534e00b11b709fad1a829f
+#: ../../networking/external_firewalls_and_load_balancers.rst:314
+msgid ""
+"**Healthy threshold (Optional)**: Number of consecutive health check "
+"successes that are required before declaring an instance healthy. Default: "
+"2."
+msgstr "**健康阀值(可选)**: 在声明一个实例健康之前，连续健康检查成功的次数。默认为2."
+
+# 8c946ad8aa9b402ba1d7808681a90216
+#: ../../networking/external_firewalls_and_load_balancers.rst:318
+msgid ""
+"**Unhealthy threshold (Optional)**: Number of consecutive health check "
+"failures that are required before declaring an instance unhealthy. Default: "
+"10."
+msgstr "**不健康阀值(可选)**: 在声音一个实例不健康之前连续健康检查失败的次数。默认为10。"
+
+# 8bd4120f80ff41368605d05b647ee837
+#: ../../networking/external_firewalls_and_load_balancers.rst:322
+msgid ""
+"Click Add VMs, then select two or more VMs that will divide the load of "
+"incoming traffic, and click Apply."
+msgstr "点击添加虚拟机，选择拟分散进入流量的二个或多个虚拟机，点击应用。"
+
+# 9720f8ded014448394288000a5c40217
+#: ../../networking/external_firewalls_and_load_balancers.rst:325
+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 "在列表中会出现新加的负载均衡规则。可以重复以上步骤以对此IP增加更多的负载均衡规则。"
+
+# 3ccedfb3a9324eb1860d1924ac909e3a
+#: ../../networking/external_firewalls_and_load_balancers.rst:330
+msgid "Sticky Session Policies for Load Balancer Rules"
+msgstr "为负载均衡规则制定的粘性会话策略。"
+
+# b33d98749eb5488a8a02cad61861c752
+#: ../../networking/external_firewalls_and_load_balancers.rst:332
+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 "粘性会话应用于基于网页的应用中，以确保在用户的会话中，对用户的多种请求持续提供信息。例如，购物者正在向购物车中增加东西，则需要记住到目前为止已买的东西。粘性的概念也指持久发现或维护状态。"
+
+# 68678f9c4f934ed796779a0d4121e91a
+#: ../../networking/external_firewalls_and_load_balancers.rst:338
+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, cookies are used. The cookie "
+"generated by the load balancer or application is included in request and "
+"response URLs to create persistence. The cookie name can be specified by the"
+" administrator or automatically generated. A variety of options are provided"
+" to control the exact behavior of cookies, such as how they are generated "
+"and whether they are cached."
+msgstr "在CloudStack中定义的任何负载均衡规则，都可以具有粘性策略。策略有名字，粘性方法以及参数组成。参数是成对的值-名或标志，这些由负载均衡提供商进行定义。粘发现方法可以加载负载均衡设备产生的cookie，应用生产的cookie，或基于源产生的cookie。在基于源的方法中，源IP地址被用来区分用户和定位用户存储的数据。在其他方法中，则使用cookie。由负载均衡或应用产生的cookie，包含在请求或响应的url中，以产生持久性。cookie的名称可以有管理员指定或自动产生。提供了多种选择来准确控制cookie行为。诸如如何产生的以及是否进行缓存。"
+
+# bb05b34273814acfb053cac6ffdfe917
+#: ../../networking/external_firewalls_and_load_balancers.rst:352
+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 "对于多数粘性方法变量列表，可以参看CloudStack UI或者调用网络列表，并检查粘性方法支持能力。"
+
+# 35aba1c4298e4ecdaaa750f3375b4be2
+#: ../../networking/external_firewalls_and_load_balancers.rst:360
+msgid "Health Checks for Load Balancer Rules"
+msgstr "负载均衡规则的健康检查。"
+
+# d9cc398640dc410ea5c44e614e8d82cd
+#: ../../networking/external_firewalls_and_load_balancers.rst:362
+msgid "(NetScaler load balancer only; requires NetScaler version 10.0)"
+msgstr "（仅对NetScaler负载均衡设备，需要NetScaler版本10.0以上。）"
+
+# 13a5a45067f34a0b8387527dfaa9d0ce
+#: ../../networking/external_firewalls_and_load_balancers.rst:364
+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 "负载均衡应用中的健康检查，能够确保转发需求运行，服务可用。当创建一个负载均衡规则里，你可以指定一个健康检查策略。这是对粘性策略，算法，其他负载均衡设备规则的附加说明。可以为每一条负载均衡设备进行配置。"
+
+# 507b3dcc2fbd48a18c5ae46dcb37b341
+#: ../../networking/external_firewalls_and_load_balancers.rst:371
+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 "在CloudStackk中的NetScaler负载均衡设备定义的任一负载均衡规则都可以有一条健康检查策略。该策略有ping路径，定义健康或非健康状态的阀值，健康检查频率以及等待超时间隔。"
+
+# 35f78e270b3e47749e7a677486944ac1
+#: ../../networking/external_firewalls_and_load_balancers.rst:376
+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 with a health check "
+"configured, the state will be shown as UP or DOWN in the UI depending on the"
+" result of the most recent health check."
+msgstr "当健康检查策略生效时，负载均衡被发现处于非健康状态时，会停止转发到源的任何请求。如果随后资源变为可用，周期性进行的健康检查就会发现，此资源就会再一次被添加至从负载均衡器收到的请求资源池里。任一时刻，最近的健康检查结果会显示在UI中。对绑定了负载均衡规则的虚拟机，且此规则配置了健康检查，依据最近的检查，状态会显示为正常或失败。"
+
+# bdff04e42c3943e38c182443f757f743
+#: ../../networking/external_firewalls_and_load_balancers.rst:386
+msgid "You can delete or modify existing health check policies."
+msgstr "可以删除或修改存在的健康检查策略。"
+
+# eef49f2114c344a58739dcf8f68aac70
+#: ../../networking/external_firewalls_and_load_balancers.rst:388
+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 "为配置默认的健康检查执行频率，通过全局配置参数 healthcheck.update.interval进行设备，默认值是600秒。可以根据需要进行设置此值。"
+
+# 6f13b2ca1fd74ad2a09363a9de9dfa54
+#: ../../networking/external_firewalls_and_load_balancers.rst:393
+msgid ""
+"For details on how to set a health check policy using the UI, see :ref"
+":`adding-lb-rule`."
+msgstr "如何通过UI进行健康检查策略的设置，可参看 :ref:`adding-lb-rule`。"
+
+# 6f66a1def18847c0ba2eec5214f58bc4
+#: ../../networking/external_firewalls_and_load_balancers.rst:400
+msgid "Configuring AutoScale"
+msgstr "配置自缩放"
+
+# 1d10105f71d4436ca70e813d83aa587d
+#: ../../networking/external_firewalls_and_load_balancers.rst:402
+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 "自缩放允许你能够根据定义的条件进行无缝且自动的增加或减少后端服务或应用虚拟机。当开启自缩放时，可以确保在需求增加时，无缝的增加正在使用虚拟机的数量。因此他会通过关闭未使用的虚拟机或者需要时开启新的虚拟机，从而节省你的计算成本。这些操作，都不需要手动干预。"
+
+# f916e1ba803d4d5f93f20a1fc650704f
+#: ../../networking/external_firewalls_and_load_balancers.rst:410
+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 CPU usage is less than 20 "
+"percent for 30 minutes."
+msgstr "NetScaler的自缩放定义为基于用户定义的条件，无缝的开启或关闭虚拟机。触发扩大或缩小行为的条件从监控服务器cpu的使用率的单一用例到监控服务器响应及cpu使用率的组合用例，各不相同。例如，你可以一个自缩放，能够在CPU使用超过80%持续15分钟时启动一个新的虚拟机，或CPU使用率低于20%持续30分钟时，移除一个虚拟机。"
+
+# fa4167d0761945e6b5552ddc195aa1cb
+#: ../../networking/external_firewalls_and_load_balancers.rst:419
+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 "CloudStack使用NetScaler负载均衡器来监控系统健康的各方面，并与CloudStack共同工作以初始化扩大或缩小的行为。"
+
+# 25cc6eeee03544bead38d29ffde91c33
+#: ../../networking/external_firewalls_and_load_balancers.rst:424
+msgid ""
+"AutoScale is supported on NetScaler Release 10 Build 74.4006.e and beyond."
+msgstr "自缩放在NetScaler发布的10版本以上适用。（Build 74.4006.e 及以上）"
+
+# f97b092a261142629f674c1cf40ee949
+#: ../../networking/external_firewalls_and_load_balancers.rst:428
+msgid "Prerequisites"
+msgstr "先决条件"
+
+# 0c697f756785488aaa591aa8b9a921cc
+#: ../../networking/external_firewalls_and_load_balancers.rst:430
+msgid "Before you configure an AutoScale rule, consider the following:"
+msgstr "在配置自缩放前，需要考虑以下几点："
+
+# 8229cf3ea2d24a22bc9707f8f142ca5e
+#: ../../networking/external_firewalls_and_load_balancers.rst:432
+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 "确保在配置自缩放时有必需的模板。当使用模板部署虚拟机并使虚拟机启动时，应用能够起动并运行。"
+
+# a3b170baceb44749ba1bc8c05a2d5b1c
+#: ../../networking/external_firewalls_and_load_balancers.rst:437
+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 "如果应用没有运行，NetScaler设备会认为虚拟机无效并持续无条件的创建虚拟机，直到资源耗尽。"
+
+# df32d04c33ca462ea54e7d716b2d8ffe
+#: ../../networking/external_firewalls_and_load_balancers.rst:441
+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 "部署准备好的模板。确保应用在第一次启动时能够开启并准备好接管流量。观察部署模板需要的时间。在配置自缩放时，要考虑这段时间。"
+
+# e416b95063a0497fa2b7ca6430c0957c
+#: ../../networking/external_firewalls_and_load_balancers.rst:446
+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-server>`_ to configure SNMP on"
+" a RHEL machine."
+msgstr ""
+
+# 0ac0707e74464bd0840f60e335716a25
+#: ../../networking/external_firewalls_and_load_balancers.rst:456
+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 "确保在全局配置中的结束点地址参数已设置为管理服务器的API地址。例如：``http://10.102.102.22:8080/client/api``。 在多管理节点的部署中，使用配置在负载均衡器上的虚拟IP地址作为管理服务器集群的IP地址。此外，确保NetScaler设备有读取为提供自缩放而配置的IP地址的权限。"
+
+# f8d93cd584a54fd8b2a72143d4107323
+#: ../../networking/external_firewalls_and_load_balancers.rst:464
+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 "如果更新了endpointe.url，在系统自动负载均衡器规则里，先关闭自缩放功能随后再开启，以应用此更新。。更多信息，参见 :ref:`update-autoscale`。"
+
+# f4e671d2a1814ee7936944319291f882
+#: ../../networking/external_firewalls_and_load_balancers.rst:468
+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 "如果为自缩放用户生成了API值和秘钥，确保用户参与的负载均衡器的自缩放功能先关闭，再开启，以应用NetScaler配置的变化。"
+
+# 1def24ca3fcf4a9984043a4339307137
+#: ../../networking/external_firewalls_and_load_balancers.rst:473
+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 "在高级区域中，在配置带自缩放的负载均衡规则时，确保至少要有一个虚拟机。在网络中存在一个虚拟机，可保证在配置自缩放时，网络处于使用状态。"
+
+# d722fd21fbb64e1f8fe5c04b72d39a29
+#: ../../networking/external_firewalls_and_load_balancers.rst:480
+msgid "Configuration"
+msgstr "配置"
+
+# aa34165bbbed4360bb6cebfc7b978d91
+#: ../../networking/external_firewalls_and_load_balancers.rst:482
+msgid "Specify the following:"
+msgstr "指定以下信息："
+
+# 306046475ddb4e789bc88bc1633cdc73
+#: ../../networking/external_firewalls_and_load_balancers.rst:484
+msgid "|autoscaleateconfig.png|"
+msgstr "|autoscaleateconfig.png|"
+
+# 951132877c0f4870b67560ae8035c8eb
+#: ../../networking/external_firewalls_and_load_balancers.rst:486
+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 "**模板**: 模板由基本的操作系统镜像和应用组成。在自缩放动作中，模板用来提供一个应用的新的实例。当从模板部署虚拟机时，虚拟机在管理员不干预的情形下开始从负载均衡器那里接管流量。例如，如果虚拟机部署为WEB服务应用，则虚拟机上的WEB服务器应该在运行，并且连接了数据库，等等。"
+
+# 313bdbb8a05e46239d80664ae76a92cf
+#: ../../networking/external_firewalls_and_load_balancers.rst:494
+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 "**计算方案**: 一个预定义的虚拟硬件资源集，包括CPU速度，CPU数量，RAM，用户在创建虚拟时可以选择这些。选择一个计算方案作为提供虚拟机实例中自缩放行为的一部分。"
+
+# cd0d1d8ce17d439eb9c360d182e61bc0
+#: ../../networking/external_firewalls_and_load_balancers.rst:500
+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 "**最小实例**: 指定给负载均衡规则活动的虚拟机实例的最小数量，活动的虚拟机实例是开启的应用实例，并服务于流量和负载均衡。这个参数确保负载均衡规则拥有至少一个配置的活动虚拟机实例，并且能够服务于流量。"
+
+# b883f060ac0a4b669952542845307113
+#: ../../networking/external_firewalls_and_load_balancers.rst:508
+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 active instance count breaches the Max"
+" instance value."
+msgstr "如果一个应用程序，比如SAP，它运行在一个VM实例上，但是VM因为某些原因宕机了，那么这个VM没有被算成是Min实例的一部分，并且如果这些活动的VM实例是下面配置的数值，那么自动扩展功能启动一个扩展的动作。同样的，当应用程序实例从宕机的状态恢复了以后，这个应用程序实例会被算为活动实例计数的一部分，并且当活动实例计数超出Max实例数值的时候，自动扩展启动一个缩减动作。"
+
+# 1062b529c80542fe9f49822dc8e1226b
+#: ../../networking/external_firewalls_and_load_balancers.rst:518
+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 "**最大实例数**：最大数量的**应该被指派到**\\ 一条负载均衡策略的活动VM实例。这个参数定义了能被指派到一条负载均衡策略的活动VM实例的上限。"
+
+# 2f6f81ae0f294d00be1d4501c00d3ef4
+#: ../../networking/external_firewalls_and_load_balancers.rst:523
+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 "给最大量实例参数指定一个大的值可能引发大量VM实例的分发，这个过程会导致一个负载均衡策略耗尽账户或者域级别下VM实例指定的限制。"
+
+# 80e14b2eba9f4b31bf0f73a8fb4665ac
+#: ../../networking/external_firewalls_and_load_balancers.rst:529
+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 "如果一个应用程序，比如SAP，它运行在一个VM实例上，但是VM因为某些原因宕机了，那么这个VM没有被算成是Max实例的一部分。所以这个情况中为扩展动作分发的VMs数量可能会超过配置的MAX实例数值。一旦这个VMs中的应用程序实例从先前的宕机中恢复的时候，自动扩展功能就会校正Max实例的数值。"
+
+# c05f5503e8994d1bbe38126fc1652574
+#: ../../networking/external_firewalls_and_load_balancers.rst:537
+msgid "Specify the following scale-up and scale-down policies:"
+msgstr "指定下列扩展和缩减的策略："
+
+# 8b8ee965cf5f45e4a993ef5a61584ee7
+#: ../../networking/external_firewalls_and_load_balancers.rst:539
+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 "**持续**：持续，以秒为单位，你必须指定条件为true以触发一个扩展动作。这个条件定义的是为了触发一个自动扩展动作，你指定的全部持续值应保持为true。"
+
+# aef0e1b396cc4f4aa88ea919926bc457
+#: ../../networking/external_firewalls_and_load_balancers.rst:544
+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 "**计数器**：性能计数器直接体现了被监视实例的状态。默认情况下，CloudStack提供了4个性能计数器：3个SNMP计数器和1个NetScaler计数器。SNMP计数器是Linux User CPU、Linux System CPU和Linux CPU Idle。NetScaler计数器是ResponseTime。root管理员能够使用CloudStack API给CloudStack添加额外的计数器。"
+
+# e13329c9be684765967ad40f1ed75b4e
+#: ../../networking/external_firewalls_and_load_balancers.rst:551
+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 "**运算符**：自动扩展功能支持下列5种关系型运算符：大于、小于、小于或等于、大于或等于和等于。"
+
+# 736606eaa3ac4622b52ed0ab0545ba37
+#: ../../networking/external_firewalls_and_load_balancers.rst:555
+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 "**阈值**：阈值用于计数器。一旦上面计数器中定义的值超出阈值，自动扩展功能会启动扩展或者缩减动作。"
+
+# e74122a065ed4373a7c1291eb1291e64
+#: ../../networking/external_firewalls_and_load_balancers.rst:559
+msgid "**Add**: Click Add to add the condition."
+msgstr "**添加**:：点击添加来添加条件。"
+
+# 7d05f0a9ea384a5790999dfcd7fd3647
+#: ../../networking/external_firewalls_and_load_balancers.rst:561
+msgid ""
+"Additionally, if you want to configure the advanced settings, click Show "
+"advanced settings, and specify the following:"
+msgstr "另外，如果你想配置高级设置，点击显示高级设置，接着指定下列参数："
+
+# 9e8ccf2af53541eea6450c116ba10b0a
+#: ../../networking/external_firewalls_and_load_balancers.rst:564
+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 "**轮询间隔**：组合计数器，运算和阈值这几个条件的频率在触发扩展和缩减动作之前都要被评估。默认的轮询间隔是30秒。"
+
+# 9a0a8077043d427ba02f39207e648c16
+#: ../../networking/external_firewalls_and_load_balancers.rst:569
+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 "**平静期**：这是自动扩展动作被触发之后的冷静期。这个时间包括完成从模板分发一个VM实例的时间和一个应用程序准备好提供服务的时间。平静期允许机群在发生任何动作之前进入稳定状态。默认值是300秒。"
+
+# d562af8950534ba78cfad860812c91af
+#: ../../networking/external_firewalls_and_load_balancers.rst:576
+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 "**VM销毁宽限期**：此宽限期以秒计算，在一个缩减动作运行之后，在VMs被视为缩减动作的一部分从而销毁之前的等待时间。它保证了能够彻底关闭任何服务于被标记为销毁的VM的挂起中的进程或者事务。默认值是120秒。"
+
+# b74500ed7cdc4d5e984c9d01a17d6cae
+#: ../../networking/external_firewalls_and_load_balancers.rst:582
+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 "**安全组**：安全组提供一种方法来隔离VMs流量。一个安全组是一组依照设置名为入口规则和出口规则来过滤他们进出流量的VMs，这些规则依靠与VM通讯的IP地址来过滤网络流量。"
+
+# 6e921b5c683943bf8e306cb4cd731b76
+#: ../../networking/external_firewalls_and_load_balancers.rst:589
+msgid ""
+"**Disk Offerings**: A predefined set of disk size for primary data storage."
+msgstr "**磁盘方案**：一组预定义的主数据存储磁盘大小。"
+
+# 8eeeb8c4bf1749e6b405081fce9318ca
+#: ../../networking/external_firewalls_and_load_balancers.rst:592
+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 "**SNMP 联系**：SNMP 联系字符串被用于NetScaler设备从分发的VM实例中查询已配置的计数器的值。默认是public。"
+
+# 63d93ca18c5245e3aa630d743d5b1fff
+#: ../../networking/external_firewalls_and_load_balancers.rst:596
+msgid ""
+"**SNMP Port**: The port number on which the SNMP agent that run on the "
+"provisioned VMs is listening. Default port is 161."
+msgstr "**SNMP端口**：运行在已分发的VMs上的SNMP代理端口号。默认的端口是161."
+
+# 8e4ead8319ea470ba2e3a6183acf7ce2
+#: ../../networking/external_firewalls_and_load_balancers.rst:599
+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 "**用户**：在云中NetScaler设备中用于发起扩展和缩减API调用的用户。如果没有指定选项，那么该用户被配置为自动扩展。指定其他用户名可以覆盖此配置。"
+
+# c5ab8b8578de4f5b8e2aa37c414525aa
+#: ../../networking/external_firewalls_and_load_balancers.rst:604
+msgid "**Apply**: Click Apply to create the AutoScale configuration."
+msgstr "**应用**：点击应用创建自动扩展配置。"
+
+# 3d6ec42e045a4082a8798bec5791982a
+#: ../../networking/external_firewalls_and_load_balancers.rst:608
+msgid "Disabling and Enabling an AutoScale Configuration"
+msgstr "禁止和启用自动扩展配置"
+
+# ec5c758cc62a40e587a4b6c4fddb434f
+#: ../../networking/external_firewalls_and_load_balancers.rst:610
+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 "如果你想对一个自动扩展VM实例执行任何维护操作，请禁用自动扩展配置。当自动扩展配置被禁用，扩展和缩减动作不会执行。你可以利用停机时间进行维护活动。要禁用自动扩展配置，点击禁用自动扩展按钮 |EnableDisable.png|。"
+
+# 0a60f936b205455c98dceed77b11df3c
+#: ../../networking/external_firewalls_and_load_balancers.rst:616
+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 "这个按钮是启用和禁止的切换开关，取决于当前是否启用了自动扩展。在执行完维护操作以后，你可以启用回自动扩展配置。要启用，请再次打开自动扩展配置页面，然后点击启用自动扩展按钮|EnableDisable.png|。"
+
+# f4bb71e85bd344b89fdcb3239a0f51f8
+#: ../../networking/external_firewalls_and_load_balancers.rst:626
+msgid "Updating an AutoScale Configuration"
+msgstr "更新自动扩展配置"
+
+# 3bf60f14a73d43869794736b33b5aa5b
+#: ../../networking/external_firewalls_and_load_balancers.rst:628
+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 "你可以更新各种参数和添加或者删除扩展或缩减策略中的条件。在你更新自动扩展配置之前，请确保你已经通过点击禁止自动扩展按钮禁止了自动扩展负载均衡策略。"
+
+# f9665a6811b3410ba434ca755c6451f6
+#: ../../networking/external_firewalls_and_load_balancers.rst:633
+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 "在你修改了所需的自动扩展参数之后，点击应用。要应新的自动扩展策略，再次打开自动扩展配置页面，然后点击启用自动扩展按钮。"
+
+# debb34a5766f45ca8759a81e6401dc05
+#: ../../networking/external_firewalls_and_load_balancers.rst:639
+msgid "Runtime Considerations"
+msgstr "运行时注意事项"
+
+# 57af5a07b00746d1b071d2eb6e80fea1
+#: ../../networking/external_firewalls_and_load_balancers.rst:641
+msgid ""
+"An administrator should not assign a VM to a load balancing rule which is "
+"configured for AutoScale."
+msgstr "管理员不应该分配VM到配置为AutoScale的负载均衡规则中。"
+
+# 7df6035fc7ca442bbbb5d7bd0ea0428b
+#: ../../networking/external_firewalls_and_load_balancers.rst:644
+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 "在分配虚拟机到一个负载均衡的规则配置完成前如果NetScaler被关闭或重启，则配置的虚拟机不能成为负载均衡规则的一部分。要解决此问题，重命名基于AutoScale配置的虚拟机名称或ID，以便在任何时间点负载平衡规则可以调节该虚拟机。"
+
+# 0eca9ec603bb4fc28eaabd868afa3e27
+#: ../../networking/external_firewalls_and_load_balancers.rst:651
+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 "在自动扩展上下文之外使用API调用，如destroyVM，那么自动扩展下的VM会处于负载均衡配置冲突状态中。虽然VM被负载均衡策略所销毁，但NetScaler仍然会把VM作为一个设备分配一条策略。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/global_server_load_balancing.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/global_server_load_balancing.mo
new file mode 100644
index 0000000..6f27f46
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/global_server_load_balancing.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/global_server_load_balancing.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/global_server_load_balancing.po
new file mode 100644
index 0000000..2778969
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/global_server_load_balancing.po
@@ -0,0 +1,789 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:05+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# dcd5b9f2eedc4d1682f64e174cd2cef7
+#: ../../networking/global_server_load_balancing.rst:18
+msgid "Global Server Load Balancing Support"
+msgstr "全局服务器负载均衡 支持"
+
+# 6cf6d74b4dde4e5fb05f41ae52822a4a
+#: ../../networking/global_server_load_balancing.rst:20
+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 "CLOUDSTACK支持全局服务器负载均衡 (GSLB) 功能以提供可持续的商业运营。GSLB可以在CLOUDSTACK环境中实现资源的无缝迁移。CLOUDSTACK通过集成NetScaler应用交付控制器 (ADC)来提供GSLB功能，ADC可以提供各种各样的GSLB能力，比如灾难恢复，负载均衡。CLOUDSTACK在实现GSLB功能进，使用了DNS重定向技术。"
+
+# 7396fe0f91a94dcf8d73474623b3c975
+#: ../../networking/global_server_load_balancing.rst:28
+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 "为了支持这个功能，引进了地域级别的服务和服务提供者。引进了一项新服务“GSLB”作为地域级别的服务。该GSLB服务提供者介绍将提供GSLB服务。目前，CloudStack中NetScaler可作为GSLB提供者。 GSLB功能工作在Active-Active数据中心环境。"
+
+# c1b8feb53b76438681b08acf77c25440
+#: ../../networking/global_server_load_balancing.rst:37
+msgid "About Global Server Load Balancing"
+msgstr "关于全局服务器负载均衡"
+
+# e03a6a1a69b640308c22260d5737533b
+#: ../../networking/global_server_load_balancing.rst:39
+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 accessing a resource in the event of a "
+"failure, or to provide a means of shifting traffic easily to simplify "
+"maintenance, or both."
+msgstr "全局服务器负载均衡(GSLB)是负载均衡功能的扩展，为了高效的避免停机时间。基于部署的性质，GSLB代表一组技术的集合，用于各种用途，如负载均衡，灾难恢复，性能，和法定义务。使用GSLB，工作负载可以分布在位于不同地理位置的多个数据中心。 GSLB也可以用于在发生故障时访问资源的另一个备用位置，或对流量提供了简易的维护方式，或两者兼得。"
+
+# ba32175058a043b081e7045d04a34334
+#: ../../networking/global_server_load_balancing.rst:51
+msgid "Components of GSLB"
+msgstr "GSLB服务组件"
+
+# 8282609b9ff24cd980a31ea858744fba
+#: ../../networking/global_server_load_balancing.rst:53
+msgid "A typical GSLB environment is comprised of the following components:"
+msgstr "一个典型的GSLB环境由以下服务组件组成："
+
+# 0c4b0b08a37346789443744bef960c26
+#: ../../networking/global_server_load_balancing.rst:55
+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 "**GSLB站点**：在CloudStack专业术语中，GSLB站点表现为映射至数据中心的zones，每个GSLB有多个网络设备。每个GSLB站点由一个位于站点中的NetScaler设备管理。每个NetScaler设备将他管理的站点视为本地站点，并且由其他NetScaler设备管理的站点视为远程站点。在GSLB部署中它是一个中央实体，具体表现为一个名称和一个IP地址。"
+
+# e6f8317f00944a5faf27bf059374e211
+#: ../../networking/global_server_load_balancing.rst:63
+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 "**GSLB服务**：GSLB服务表现为典型的负载均衡或者内容交换虚拟服务器。在一个GSLB环境中，你可以有本地及远程GSLB服务。本地GSLB服务表现为一个本地负载均衡或者内容交换虚拟服务器。远程GSLB服务是配置在GSLB设置中的其他站点。在每个站点中的GSLB设置里，你可以创建一个本地GSLB服务和任意数量的远程GSLB服务。"
+
+# 0d6074d67e874afaafcced32aa2dcad8
+#: ../../networking/global_server_load_balancing.rst:72
+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 a FQDN DNS name."
+msgstr "**GSLB虚拟服务器**：GSLB虚拟服务器指的是一个或多个GSLB服务和平衡跨越多个使用CloudStack功能的zones之间VMs的流量。它通过评估配置的GSLB方法或者算法来选择一个GSLB服务发送客户端请求。来自不同zone的一个或多个虚拟服务器被绑定到GSLB虚拟服务器上。GSLB虚拟服务器没有对应的公共IP，只有一个FQDN DNS名称。"
+
+# 25269a15ffaf4c48880b969ed8e8ff0b
+#: ../../networking/global_server_load_balancing.rst:81
+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 balancing or content switching virtual "
+"server, the client sends the request to that virtual server's VIP address."
+msgstr "**负载均衡或内容交换虚拟服务器**：依照Citrix NetScaler的专业术语，一个负载均衡或者内容交换虚拟服务器表现为本地网络上的一个或多个服务器。客户端发送他们的请求至负载均衡或内容交换虚拟服务器IP(VIP)地址，并且由虚拟服务器平衡本地服务器之间的负载。在GSLB虚拟服务器选择了一个基于本地或者远程负载均衡或者内容交换虚拟服务器的GSLB服务之后，客户端发送请求至虚拟服务器的VIP地址。"
+
+# a4ae12735c574a18995202afba84a585
+#: ../../networking/global_server_load_balancing.rst:91
+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 "**DNS VIPs**：DNS虚拟IP是一个在GSLB服务供应者上的DNS负载均衡虚拟服务器。在有GSLB服务提供者的域中的DNS请求会被发送至一个DNS VIP。"
+
+# 18dae232ea054aad8beb56723f2e9d6d
+#: ../../networking/global_server_load_balancing.rst:96
+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 and port."
+msgstr "**权威DNS**：ADNS(权威域名称服务器)是一个为DNS请求提供真实响应的服务，比如web站点IP地址。在GSLB环境中，一个ADNS服务只响应权威的GSLB服务提供者所在域的DNS请求。当配置了一个ADNS服务，该服务的提供者即拥有该服务IP并且广播它。当你创建一个ADNS服务的时候，NetScaler通过配置的ADNS服务IP和端口响应DNS请求。"
+
+# 9efb5a6ae20d45eab31e7fe7ffc87eab
+#: ../../networking/global_server_load_balancing.rst:107
+msgid "How Does GSLB Works in CloudStack?"
+msgstr "在CloudStack中，GSLB的工作原理是什么？"
+
+# daac6a57d97c4caebd3fa5d2f5f27324
+#: ../../networking/global_server_load_balancing.rst:109
+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 xyztelco cloud. For that purpose, they "
+"launch two instances each in both the zones: VM1 and VM2 in Zone-1 and VM5 "
+"and VM6 in Zone-2. Tenant-A acquires a public IP, IP-1 in Zone-1, and "
+"configures a load balancer rule to load balance the traffic between VM1 and "
+"VM2 instances. CloudStack orchestrates setting up a virtual server on the LB"
+" service provider in Zone-1. Virtual server 1 that is set up on the LB "
+"service provider in Zone-1 represents a publicly accessible virtual server "
+"that client reaches at IP-1. The client traffic to virtual server 1 at IP-1 "
+"will be load balanced across VM1 and VM2 instances."
+msgstr "全局服务器负载均衡-GSLB-用于在不同地域的不同独立区域之间管理WEB服务器的访问流量。以下是CLOUDSTACK中提供的GSLB功能图示：EXZTELCO这个组织用CLOUDSTACK在不同的数据中心部署一个公有云，此云环境包括两个区域，Zone-1 和Zone-2。XYZTELCO里有租户A需要部署一个高可用方案。为了达到此目标，他们分别在两个区域里部署了两个虚拟机实例：Zone-1中有VM1和VM2，Zone-2中有VM5和VM6。租户A在Zone-1中得到一个公网IP-IP-1，并且在VM1和VM2之间配置了负载均衡规则。CLOUDSTACK 编排系统在 Zone-1中LB服务上设置了一个虚拟服务器-Virtual server 1 。客户端对-IP-1的访问会到达Virtual server 1，此虚拟服务器再将流量转发到VM1和VM2上进行流量负载均衡。"
+
+# ab85065c7a794a62bb64bb4d17ff62c9
+#: ../../networking/global_server_load_balancing.rst:126
+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 instances. At this point Tenant-A "
+"has the service enabled in both the zones, but has no means to set up a "
+"disaster recovery plan if one of the zone fails. Additionally, there is no "
+"way for Tenant-A to load balance the traffic intelligently to one of the "
+"zones based on load, proximity and so on. The cloud administrator of "
+"xyztelco provisions a GSLB service provider to both the zones. A GSLB "
+"provider is typically an ADC that has the ability to act as an ADNS "
+"(Authoritative Domain Name Server) and has the mechanism to monitor health "
+"of virtual servers both at local and remote sites. The cloud admin enables "
+"GSLB as a service to the tenants that use zones 1 and 2."
+msgstr "租户A在Zone-2中得到一个公网IP-IP-2，并且在VM5和VM6之间配置了负载均衡规则。CLOUDSTACK 编排系统在 Zone-2中LB服务上设置了一个虚拟服务器-Virtual server 2 。客户端对-IP-2的访问会到达Virtual server 2，此虚拟服务器再将流量转发到VM5和VM6上进行流量负载均衡。此时，租户A在两个区域里都启用了服务，但是，无法在这种环境下部署灾难恢复计划，也无法更智能在区域内使用负载均衡。要解决这些问题，XYZTELCO云管理员可以在两个区域内启用GSLB服务，一个GSLB服务通常是一个具有ADNS(认证域名服务器)能力的ADC，并且具有监测本地和远程站点健康状况的手段。云管理员可以在ZONE 1和2中为租户启用GSLB服务。"
+
+# 16e02bcf2da14fd48ec4af740ccfc445
+#: ../../networking/global_server_load_balancing.rst:144
+msgid "|gslb.png|"
+msgstr "|gslb.png|"
+
+# 7f93cb0f9f2e4bc58cfc7f308c019bda
+#: ../../networking/global_server_load_balancing.rst:146
+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 start monitoring the health of "
+"virtual server 1 and 2 in Zone-1. CloudStack will also orchestrate setting "
+"up GSLB virtual server 2 on GSLB service provider at Zone-2. CloudStack will"
+" bind virtual server 1 of Zone-1 and virtual server 2 of Zone-2 to GLSB "
+"virtual server 2. GSLB virtual server 2 is configured to start monitoring "
+"the health of virtual server 1 and 2. CloudStack will bind the domain "
+"A.xyztelco.com to both the GSLB virtual server 1 and 2. At this point, "
+"Tenant-A service will be globally reachable at A.xyztelco.com. The private "
+"DNS server for the domain xyztelcom.com is configured by the admin out-of-"
+"band to resolve the domain A.xyztelco.com to the GSLB providers at both the "
+"zones, which are configured as ADNS for the domain A.xyztelco.com. A client "
+"when sends a DNS request to resolve A.xyztelcom.com, will eventually get DNS"
+" delegation to the address of GSLB providers at zone 1 and 2. A client DNS "
+"request will be received by the GSLB provider. The GSLB provider, depending "
+"on the domain for which it needs to resolve, will pick up the GSLB virtual "
+"server associated with the domain. Depending on the health of the virtual "
+"servers being load balanced, DNS request for the domain will be resolved to "
+"the public IP associated with the selected virtual server."
+msgstr "租户- A希望利用由xyztelco cloud提供的GSLB服务。租户-A配置了一个GSLB规则对Zone-1中的虚拟服务器1和Zone-2中的虚拟服务器2提供流量负载均衡。假设域名是A.xyztelco.com 。CloudStack中协调设置GSLB服务提供者Zone-1中的GSLB虚拟服务器1。 CloudStack绑定Zone-1中的虚拟服务器1和Zone-2中的虚拟服务器2到GSLB虚拟服务器1。CloudStack也将协调设置GSLB服务提供者Zone-2中的GSLB虚拟服务器2.CloudStack绑定Zone-1中的虚拟服务器1和Zone-2中的虚拟服务器2到GSLB虚拟服务器2.GSLB虚拟服务器2配置为开始监视虚拟服务器1和2的健康。CloudStack中会绑定域名A.xyztelco.com到GSLB虚拟服务器1和2。在这一点上，租户-A的服务将在全球范围内可达于A.xyztelco.com。域名xyztelcom.com的专用DNS服务器，被管理员配置为外带管理，由两个区域的GSLB提供者对域名A.xyztelco.com提供解析。它将被配置为域名A.xyztelco.com的ADNS。当客户端请求解析A.xyztelcom.com域名时，将最终由DNS指派到GSLB提供者Zone 1 和Zone2。客户DNS请求将被GSLB提供者接获。GSLB提供者，根据需要解析的域名，将获得与域名关联的GSLB虚拟服务器。根据用于负载均衡的虚拟服务器的运行健康状况，域名DNS请求将被解析到所选择关联的虚拟服务器中。"
+
+# dcd79b8e29a442d098cb8090a4527144
+#: ../../networking/global_server_load_balancing.rst:175
+msgid "Configuring GSLB"
+msgstr "配置GSLB"
+
+# af3fb04e787447d9976ebb989e847e3d
+#: ../../networking/global_server_load_balancing.rst:177
+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 servers. Finally, bind the domain to "
+"the GSLB virtual servers. The GSLB configurations on the two appliances at "
+"the two different zones are identical, although each sites load-balancing "
+"configuration is specific to that site."
+msgstr "要配置GSLB的部署，您必须首先为每个区域配置一个标准的负载平衡设置。这使您能够在该地域中每个区域的不同服务器之间进行负载均衡。然后在NetScaler方面，配置您计划添加到每个区域作为权威DNS(ADNS)服务器的两个NetScaler应用。接下来，为每个区域创建GSLB站点、配置GSLB虚拟服务器、创建GSLB服务并绑定GSLB服务到GSLB虚拟服务器中。最后，绑定该域到GSLB虚拟服务器。两个应用的GSLB配置在两个不同区域中是完全相同的，尽管每个网站的负载均衡配置特定于该网站。"
+
+# f12e3e8dd3114cc6ab5febf7d770620a
+#: ../../networking/global_server_load_balancing.rst:189
+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 "作为云管理员执行以下操作。按照上面给出的例子中，由管理员xyztelco设置GSLB："
+
+# 9579cd3756414bb59e03052c3c4807de
+#: ../../networking/global_server_load_balancing.rst:192
+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 "在全局变量 cloud.dns.name中，为您租户云定义DNS名称并供GSLB服务使用。"
+
+# e675df400e4c40079a4b8ac2c3a3a007
+#: ../../networking/global_server_load_balancing.rst:195
+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 "在NetScaler方面，给出GSLB配置 `配置全局服务器负载均衡 (GSLB)<http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-con.html>`_:"
+
+# 8366d0a33b5d4328b32668eee7db43a7
+#: ../../networking/global_server_load_balancing.rst:199
+msgid "Configuring a standard load balancing setup."
+msgstr "配置一个标准的负载均衡设置。"
+
+# 652a6e0d3f25435bad8a3a37ff14f6de
+#: ../../networking/global_server_load_balancing.rst:201
+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 "配置权威DNS，如下解释 `配置权威的DNS服务 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-adns-svc-tsk.html>`__."
+
+# eb1be7170a664c05818eea4cebcd652c
+#: ../../networking/global_server_load_balancing.rst:205
+msgid ""
+"Configure a GSLB site with site name formed from the domain name details."
+msgstr "由域名详细信息配置一个GSLB站点和站点名称。"
+
+# af0e9c7b27f545b9a2532edf6109ddf3
+#: ../../networking/global_server_load_balancing.rst:208
+msgid "Configure a GSLB site with the site name formed from the domain name."
+msgstr "由域名配置一个GSLB站点和站点名称。"
+
+# 6c3c9b0f00314c219b51b9ea4a817b37
+#: ../../networking/global_server_load_balancing.rst:211
+msgid ""
+"As per the example given above, the site names are A.xyztelco.com and "
+"B.xyztelco.com."
+msgstr "按照上面给出的例子，站点名称为 A.xyztelco.com 和 B.xyztelco.com"
+
+# 8bc45e9126194d24824f0e0e2d92ca1b
+#: ../../networking/global_server_load_balancing.rst:214
+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 "更多信息，请参阅 `配置基本的GSLB站点 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-basic-site-tsk.html>`__."
+
+# 7276993a8c1f4f089886c5bfce5f4f6e
+#: ../../networking/global_server_load_balancing.rst:217
+msgid "Configure a GSLB virtual server."
+msgstr "配置GSLB虚拟服务器。"
+
+# 8d0c82c139184d3992209af4d2e54a6c
+#: ../../networking/global_server_load_balancing.rst:219
+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 "更多信息，请参阅 `配置GSLB虚拟服务器 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-vsvr-tsk.html>`__."
+
+# 7db75bd72fa44709ab7adb82ba26f318
+#: ../../networking/global_server_load_balancing.rst:222
+msgid "Configure a GSLB service for each virtual server."
+msgstr "为每个虚拟服务器配置GSLB服务。"
+
+# 7dd4d9aa1c394ed6859a00b0331f3e5b
+#: ../../networking/global_server_load_balancing.rst:224
+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 "更多信息，请参阅 `配置GSLB服务 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-svc-tsk.html>`__."
+
+# 30745365545f4cbca1a5ff6fa73a495f
+#: ../../networking/global_server_load_balancing.rst:227
+msgid "Bind the GSLB services to the GSLB virtual server."
+msgstr "绑定GSLB服务到GSLB虚拟服务器。"
+
+# f5c32c764b0c44cc9b430cd2c74f5a0b
+#: ../../networking/global_server_load_balancing.rst:229
+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 "更多信息，请参阅 `绑定GSLB服务到GSLB虚拟服务器 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-bind-svc-vsvr-tsk.html>`__."
+
+# 74f55b2693404f1d8b46b1960f0987db
+#: ../../networking/global_server_load_balancing.rst:232
+msgid ""
+"Bind domain name to GSLB virtual server. Domain name is obtained from the "
+"domain details."
+msgstr "绑定GSLB域名到GSLB虚拟服务器。从域的详细信息中获得域名。"
+
+# 012a1ab7ff7b422995e21b6709b4c6b3
+#: ../../networking/global_server_load_balancing.rst:235
+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 "更多信息，请参阅 `绑定GSLB域名到GSLB虚拟服务器 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-bind-dom-vsvr-tsk.html>`__."
+
+# efe8d44a7dc84347bdc932507e0cf417
+#: ../../networking/global_server_load_balancing.rst:238
+msgid ""
+"In each zone that are participating in GSLB, add GSLB-enabled NetScaler "
+"device."
+msgstr "在每个参与GSLB的区域内，添加启用GSLB功能的NetScaler设备。"
+
+# b4176a11b248487686fbfb80d484f72d
+#: ../../networking/global_server_load_balancing.rst:241
+msgid "For more information, see :ref:`enabling-gslb-in-ns`."
+msgstr "更多信息请参考 :ref:`enabling-gslb-in-ns`."
+
+# 8fc3da50593741b9863599aee89587e8
+#: ../../networking/global_server_load_balancing.rst:243
+msgid "As a domain administrator/ user perform the following:"
+msgstr "以域管理员/用户执行以下操作："
+
+# 8c1293eb2d3746e8abb219c5c4cb7290
+#: ../../networking/global_server_load_balancing.rst:245
+msgid "Add a GSLB rule on both the sites."
+msgstr "在两个站点中添加GSLB规则。"
+
+# a78f47a38a364e859b24e482f8eab174
+#: ../../networking/global_server_load_balancing.rst:247
+msgid "See \":ref:`adding-gslb-rule`\"."
+msgstr "参考\":ref:`adding-gslb-rule`\"."
+
+# 17e3b59ea95e4eb39b1290cea67e4801
+#: ../../networking/global_server_load_balancing.rst:249
+msgid "Assign load balancer rules."
+msgstr "分配负载均衡规则。"
+
+# d37f5840c4d34fa9aa990a0bb0610af9
+#: ../../networking/global_server_load_balancing.rst:251
+msgid "See \":ref:`assigning-lb-rule-gslb`\"."
+msgstr "参考\":ref:`assigning-lb-rule-gslb`\"."
+
+# 2553447c986746b582a9f8b495396c3b
+#: ../../networking/global_server_load_balancing.rst:255
+msgid "Prerequisites and Guidelines"
+msgstr "先决条件和指南"
+
+# 8627b5c519f04c4bb75b82af96f25418
+#: ../../networking/global_server_load_balancing.rst:257
+msgid "The GSLB functionality is supported both Basic and Advanced zones."
+msgstr "GSLB功能支持基本和高级区域。"
+
+# c2b5f208b13f4b07b6755c0a53fa1104
+#: ../../networking/global_server_load_balancing.rst:259
+msgid "GSLB is added as a new network service."
+msgstr "GSLB是新添加的网络服务。"
+
+# 3c6e0da5ecd148d599a35191c7e92678
+#: ../../networking/global_server_load_balancing.rst:261
+msgid "GSLB service provider can be added to a physical network in a zone."
+msgstr "GSLB服务提供者可以被添加至区域中的物理网络。"
+
+# 6c159f1bc2224bb2b35dd03ec51bc6b1
+#: ../../networking/global_server_load_balancing.rst:263
+msgid ""
+"The admin is allowed to enable or disable GSLB functionality at region "
+"level."
+msgstr "管理员允许开启或禁用地域级别的GSLB功能。"
+
+# 6367e49f50d0418c92b7b6fc7cc91a39
+#: ../../networking/global_server_load_balancing.rst:266
+msgid "The admin is allowed to configure a zone as GSLB capable or enabled."
+msgstr "管理员具有启用或配置区域为GSLB的能力"
+
+# a66b5c6d51534ab492d244d518221776
+#: ../../networking/global_server_load_balancing.rst:268
+msgid ""
+"A zone shall be considered as GSLB capable only if a GSLB service provider "
+"is provisioned in the zone."
+msgstr "只有在GSLB服务提供者提供的区域中，该区域才被视为有GSLB能力。"
+
+# 0ea762e8718b465eaacf40a6118c8f7f
+#: ../../networking/global_server_load_balancing.rst:271
+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 "当用户的VMs部署在启用GSLB功能的多个可用区域中时，他们可以使用GSLB功能在多个区域中将VM的流量进行负载均衡。"
+
+# ed2130b4027e41e3833699a89ff82708
+#: ../../networking/global_server_load_balancing.rst:275
+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 "如果管理员在地域中启用了GSLB，用户可以使用GSLB对地狱中的所有区域的VMs进行负载均衡。"
+
+# 1b374fea614b459eb39cfbe4f20478c9
+#: ../../networking/global_server_load_balancing.rst:278
+msgid ""
+"The users can load balance traffic across the availability zones in the same"
+" region or different regions."
+msgstr "用户可以为同一个区域或不同地域间可用的区域流量进行负载均衡。"
+
+# 62da6f878356420f9becc6fffbe1ae6d
+#: ../../networking/global_server_load_balancing.rst:281
+msgid "The admin can configure DNS name for the entire cloud."
+msgstr "管理员可以为整个云配置DNS名称。"
+
+# 799fe9490296493e9d86d0ea8cdc9297
+#: ../../networking/global_server_load_balancing.rst:283
+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 "用户可以为云中的全局负载均衡服务指定一个唯一的名称。所提供名称的域名相当于云的DNS名称。"
+
+# 1d6c20de63954971a720227985a74433
+#: ../../networking/global_server_load_balancing.rst:287
+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 "用户提供的名称与管理员提供的DNS名称一起为用户的全局负载均衡服务产生一个全局解析的FQDN。例如，如果管理员已经配置xyztelco.com为云中的DNS名称，以及用户为GSLB虚拟服务器指定的名称为'foo'，那么GSLB虚拟服务器的FQDN名称是foo.xyztelco.com。"
+
+# a7817e36fe2c4ea58737d1a5ae3db30b
+#: ../../networking/global_server_load_balancing.rst:294
+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 "设置GSLB时，用户可以为GSLB跨区域的一部分选择负载均衡方式，例如 round robin。"
+
+# 971bcd7f3cf24bbbb424a020cc7c06a4
+#: ../../networking/global_server_load_balancing.rst:297
+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 "用户应能设置区域级虚拟服务器的权重。负载均衡在分配流量时会考虑该权重。"
+
+# 6f3d31dca71d4b608fa90d1eb73ecee2
+#: ../../networking/global_server_load_balancing.rst:301
+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 "该GSLB功能必须支持会话持久性，特定域名的一系列客户端请求被发送到同一个区域中的虚拟服务器上。"
+
+# bfaf6196eae343259864ac2443ff5746
+#: ../../networking/global_server_load_balancing.rst:305
+msgid "Statistics is collected from each GSLB virtual server."
+msgstr "从每个GSLB虚拟服务器中收集统计数据。"
+
+# d2f3468cd4ac44d58c53e731e50e35dd
+#: ../../networking/global_server_load_balancing.rst:311
+msgid "Enabling GSLB in NetScaler"
+msgstr "开启NetScaler的GSLB"
+
+# d51d618416764b5c843fc13bfd2dfa6d
+#: ../../networking/global_server_load_balancing.rst:313
+msgid "In each zone, add GSLB-enabled NetScaler device for load balancing."
+msgstr "在每个区域中，添加启用GSLB的NetScaler设备提供负载均衡。"
+
+# 91d1d3b496c34b179f0b865500b6bf93
+#: ../../networking/global_server_load_balancing.rst:315
+msgid "Log in as administrator to the CloudStack UI."
+msgstr "使用管理员登录到CloudStack管理界面。"
+
+# cc1ae38bffd84c058812510e8495b73f
+#: ../../networking/global_server_load_balancing.rst:317
+msgid "In the left navigation bar, click Infrastructure."
+msgstr "在左侧导航栏中，点击基础架构"
+
+# 46ba7c7f81d04aa78f0c04d3d045bc8a
+#: ../../networking/global_server_load_balancing.rst:319
+msgid "In Zones, click View More."
+msgstr "点击区域中的查看更多。"
+
+# 1feb8d2e09014d9989264c48ece8fc81
+#: ../../networking/global_server_load_balancing.rst:321
+msgid "Choose the zone you want to work with."
+msgstr "选择你要设置的区域。"
+
+# 82a50383b1124be48db8d0c5721e9f13
+#: ../../networking/global_server_load_balancing.rst:323
+msgid ""
+"Click the Physical Network tab, then click the name of the physical network."
+msgstr "点击物理网络选项卡，然后点击物理网络的名称。"
+
+# 75224089389e4bee8e89a1caf1dc5880
+#: ../../networking/global_server_load_balancing.rst:326
+msgid "In the Network Service Providers node of the diagram, click Configure."
+msgstr "点击示意图'网络服务提供程序'中的配置"
+
+# 410a9b626bf9412a9f482c2df1aac784
+#: ../../networking/global_server_load_balancing.rst:329
+msgid "You might have to scroll down to see this."
+msgstr "你可能需要向下滚动才能看到。"
+
+# 1d32a851fb92436c8e045ccc828641f4
+#: ../../networking/global_server_load_balancing.rst:331
+msgid "Click NetScaler."
+msgstr "点击NetScaler."
+
+# af72e8614fc44c60af3004624dba03b1
+#: ../../networking/global_server_load_balancing.rst:333
+msgid "Click Add NetScaler device and provide the following:"
+msgstr "点击添加NetScaler设备并提供如下信息："
+
+# 6290f4f42d054ac28661b16c5366b62f
+#: ../../networking/global_server_load_balancing.rst:335
+msgid "For NetScaler:"
+msgstr "对于NetScaler:"
+
+# 8e09b55d68a849d089029f2c893e3e97
+#: ../../networking/global_server_load_balancing.rst:337
+msgid "**IP Address**: The IP address of the SDX."
+msgstr "**IP地址**: SDX的IP地址。"
+
+# 9b9b4165d2ee4e64b3b0b04390702686
+#: ../../networking/global_server_load_balancing.rst:339
+msgid ""
+"**Username/Password**: The authentication credentials to access the device. "
+"CloudStack uses these credentials to access the device."
+msgstr "**用户名/密码.** 访问此设备的认证许可。CloudStack使用这些认证信息访问此设备。"
+
+# 212ab71ac16a49309da99e2870717faa
+#: ../../networking/global_server_load_balancing.rst:343
+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 "**类型**：添加设备的类型。可以是F5 BigIP负载均衡器、NetScaler VPX、NetScaler MPX或 NetScaler SDX等设备。关于NetScaler的类型比较，请参阅CloudStack管理指南。"
+
+# 3d72c6cb5cbb49418002a5e3acf1617c
+#: ../../networking/global_server_load_balancing.rst:348
+msgid ""
+"**Public interface**: Interface of device that is configured to be part of "
+"the public network."
+msgstr "**公共接口**: 配置为公共网络部分的设备接口。"
+
+# 5bbed919dc2c45008af4312d028cfbd7
+#: ../../networking/global_server_load_balancing.rst:351
+msgid ""
+"**Private interface**: Interface of device that is configured to be part of "
+"the private network."
+msgstr "**专用接口**: 配置为专用网络部分的设备接口。"
+
+# fb82ba2e06e34aaf9ab8e8fa8362b43d
+#: ../../networking/global_server_load_balancing.rst:354
+msgid "**GSLB service**: Select this option."
+msgstr "**GSLB 服务**:选择该选项。"
+
+# 8a1e3ad262934da086878740aefca5fc
+#: ../../networking/global_server_load_balancing.rst:356
+msgid ""
+"**GSLB service Public IP**: The public IP address of the NAT translator for "
+"a GSLB service that is on a private network."
+msgstr "**GSLB 服务公共IP**:在专用网络中，为GSLB服务提供NAT转换的公共IP地址。"
+
+# 5ca3fc19dd8e4706872b9e3af0652c2f
+#: ../../networking/global_server_load_balancing.rst:359
+msgid "**GSLB service Private IP**: The private IP of the GSLB service."
+msgstr "**GSLB 服务专用IP**: GSLB服务的专用IP地址。"
+
+# 8f1a8fd9ec814e02970f7edf85c8fad1
+#: ../../networking/global_server_load_balancing.rst:361
+msgid ""
+"**Number of Retries**. Number of times to attempt a command on the device "
+"before considering the operation failed. Default is 2."
+msgstr "**重试次数** 尝试控制设备失败时重试的次数，默认为2次。"
+
+# 2416b7a9e5fa43fdb27834cb7e46253b
+#: ../../networking/global_server_load_balancing.rst:364
+msgid "**Capacity**: The number of networks the device can handle."
+msgstr "**容量**：该设备能处理的网络数量。"
+
+# c9166740fb2747a7abd4ae6c0851aabc
+#: ../../networking/global_server_load_balancing.rst:366
+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 "**专用**: 当标记为专用后，这个设备只对单个帐号专用。该选项被勾选后，容量选项就没有了实际意义且值会被置为1。"
+
+# e7f874eb36ba4cd380f7a50d5bff8909
+#: ../../networking/global_server_load_balancing.rst:371
+msgid "Click OK."
+msgstr "点击确定。"
+
+# d1556618bd5d4d18862c048d52694dd4
+#: ../../networking/global_server_load_balancing.rst:377
+msgid "Adding a GSLB Rule"
+msgstr "添加 GSLB规则"
+
+# c06bbbd0cb824ecc8ef3d7956571f739
+# 2b618c03ffb14afb99d7e63813820288
+#: ../../networking/global_server_load_balancing.rst:379
+#: ../../networking/global_server_load_balancing.rst:423
+msgid "Log in to the CloudStack UI as a domain administrator or user."
+msgstr "使用管理员或者用户账号登录CloudStack UI。"
+
+# 3b04d23a46774662bbca98318323a71e
+# 62eb7d6a5d9b4256bde0fcafb9f42b7f
+#: ../../networking/global_server_load_balancing.rst:381
+#: ../../networking/global_server_load_balancing.rst:425
+msgid "In the left navigation pane, click Region."
+msgstr "在左边的导航栏里，点击区域（为文档翻译中地域的概念，英文为region，下同）"
+
+# 940f5610d0484910bf9e9ba31728be30
+# 581952b854514ed78884cc712ee4ec94
+#: ../../networking/global_server_load_balancing.rst:383
+#: ../../networking/global_server_load_balancing.rst:427
+msgid "Select the region for which you want to create a GSLB rule."
+msgstr "选择你想创建GSLB规则的地域。"
+
+# fc1d362cc95a4668b2a24c7c0f488348
+# 8519e9d4ad6d46989865460e20b186b6
+#: ../../networking/global_server_load_balancing.rst:385
+#: ../../networking/global_server_load_balancing.rst:429
+msgid "In the Details tab, click View GSLB."
+msgstr "在详细选项卡中，点击查看GSLB。"
+
+# f59a742f9f1b4f37b6f0bc0b062028d6
+#: ../../networking/global_server_load_balancing.rst:387
+msgid "Click Add GSLB."
+msgstr "点击添加GSLB。"
+
+# ca546577015a45af8ddcdc3d2ad22f3a
+#: ../../networking/global_server_load_balancing.rst:389
+msgid "The Add GSLB page is displayed as follows:"
+msgstr "添加GSLB页面显示如下："
+
+# b0b6437c269342ff9099b6da9a6d5b9f
+#: ../../networking/global_server_load_balancing.rst:391
+msgid "|gslb-add.png|"
+msgstr "|gslb-add.png|"
+
+# 767ce39d9a094fda85465381d3a93bad
+#: ../../networking/global_server_load_balancing.rst:393
+msgid "Specify the following:"
+msgstr "指定以下信息："
+
+# affa9e59440b4f4e9e6428e887d12582
+#: ../../networking/global_server_load_balancing.rst:395
+msgid "**Name**: Name for the GSLB rule."
+msgstr "**名称**: GSLB规则的名称。"
+
+# 82b72cbf0f8949fdab2de931138620c5
+#: ../../networking/global_server_load_balancing.rst:397
+msgid ""
+"**Description**: (Optional) A short description of the GSLB rule that can be"
+" displayed to users."
+msgstr "**描述**: (可选)为用户提供一个简短的GSLB规则描述。 "
+
+# 8a6b82bfcd3a469c838315b17f4cd014
+#: ../../networking/global_server_load_balancing.rst:400
+msgid "**GSLB Domain Name**: A preferred domain name for the service."
+msgstr "**GSLB 域名**: 首选的域名服务。"
+
+# ff5539d5f09f48bc80c0cf9dc83dcca0
+#: ../../networking/global_server_load_balancing.rst:402
+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 "**算法**: (可选) 用于跨区域流量负载均衡的算法。可选项为 Round Robin, Least Connection, 和Proximity."
+
+# b07f4dffc105427389bb8e089a71f9f0
+#: ../../networking/global_server_load_balancing.rst:406
+msgid ""
+"**Service Type**: The transport protocol to use for GSLB. The options are "
+"TCP and UDP."
+msgstr "**服务类型**: GSLB使用的传输协议。可选项为TCP和UDP。"
+
+# 03ffe3890f5c4ea79836cfa0cc96986f
+#: ../../networking/global_server_load_balancing.rst:409
+msgid ""
+"**Domain**: (Optional) The domain for which you want to create the GSLB "
+"rule."
+msgstr "**域**: (可选) 你想要创建GSLB规则的域。"
+
+# 5d0367f6567241968e5d6cac6f8ab34b
+#: ../../networking/global_server_load_balancing.rst:412
+msgid ""
+"**Account**: (Optional) The account on which you want to apply the GSLB "
+"rule."
+msgstr "**账户**: (可选) 应用GSLB规则的账户。"
+
+# 0161504934d746e39b05e6b50e264faf
+# 8c377e12f8494a009d5eed7e06824fe3
+#: ../../networking/global_server_load_balancing.rst:415
+#: ../../networking/global_server_load_balancing.rst:439
+msgid "Click OK to confirm."
+msgstr "点击确定。"
+
+# f61c6b78ef4940129243771e21d78f4c
+#: ../../networking/global_server_load_balancing.rst:421
+msgid "Assigning Load Balancing Rules to GSLB"
+msgstr "为GSLB分配负载均衡规则"
+
+# 54cc7b916ceb420584020f5ff230b79c
+#: ../../networking/global_server_load_balancing.rst:431
+msgid "Select the desired GSLB."
+msgstr "选择所需的GSLB。"
+
+# 5e2a1bf3adfc41bab4bea1a489f9bda1
+#: ../../networking/global_server_load_balancing.rst:433
+msgid "Click view assigned load balancing."
+msgstr "点击已分配的负载均衡视图。"
+
+# 269db9ca8770495f9c5bc08491e61bc6
+#: ../../networking/global_server_load_balancing.rst:435
+msgid "Click assign more load balancing."
+msgstr "点击分配更多负载平衡"
+
+# eceeb5fccdfa4cac904ef8fb945242c9
+#: ../../networking/global_server_load_balancing.rst:437
+msgid "Select the load balancing rule you have created for the zone."
+msgstr "选择你将为区域创建的负载均衡规则。"
+
+# d8792daad4a94b4589452d5b61f75cd9
+#: ../../networking/global_server_load_balancing.rst:443
+msgid "Known Limitation"
+msgstr "已知的局限性"
+
+# 7424fdf000e3479c910e72fbbaaa0169
+#: ../../networking/global_server_load_balancing.rst:445
+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 "目前，CloudStack并不支持跨区域的服务编排。将引入服务的概念和地域服务提供者。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/guest_ip_ranges.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/guest_ip_ranges.mo
new file mode 100644
index 0000000..7eff618
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/guest_ip_ranges.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/guest_ip_ranges.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/guest_ip_ranges.po
new file mode 100644
index 0000000..b793339
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/guest_ip_ranges.po
@@ -0,0 +1,41 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:05+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# c4f6e8eb1ed7428a8132309d84e4b1bf
+#: ../../networking/guest_ip_ranges.rst:18
+msgid "Guest IP Ranges"
+msgstr "来宾IP范围"
+
+# ef6d3891253c4ed58a8a51c2f86b51dc
+#: ../../networking/guest_ip_ranges.rst:20
+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 "宾客网络流量的IP是由用户以帐号为基础设置的。这允许用户以在他们的宾客网络和他们的客户端之间开通VPN连接的方式配置他们的网络。"
+
+# 943864c06f494d7ca4f4310246ba996a
+#: ../../networking/guest_ip_ranges.rst:25
+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 "存在基本网络和启用安全组的高级网络中的共享网络，你可以灵活的在不同子网中添加多个来宾IP范围。你可以同时添加或移除IP范围。更多信息，请参阅 `章节 15.10, “关于多IP范围”<#about-multiple-ip-ranges>`_."
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/guest_traffic.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/guest_traffic.mo
new file mode 100644
index 0000000..38b1cb6
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/guest_traffic.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/guest_traffic.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/guest_traffic.po
new file mode 100644
index 0000000..6124193
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/guest_traffic.po
@@ -0,0 +1,71 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:05+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 6a1d02b308ae4f228e4104aa95e39ee3
+#: ../../networking/guest_traffic.rst:18
+msgid "Guest Traffic"
+msgstr "来宾流量"
+
+# 77e0128afe644aa9a04259e24cb22595
+#: ../../networking/guest_traffic.rst:20
+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 "在同一个区域内，客户虚拟机之间可以互访，但在不同的区域内，客户虚拟机之间不可以通过（内网）IP地址互访，而只能通过公网IP路由才可以互连。"
+
+# 79cb326a48f942949bf3dfe341a3664f
+#: ../../networking/guest_traffic.rst:25
+msgid "See a typical guest traffic setup given below:"
+msgstr "下图是一个典型的来宾流量设置："
+
+# e0ac4742331840b89eef72912ffd2138
+#: ../../networking/guest_traffic.rst:27
+msgid "|guest-traffic-setup.png|"
+msgstr "|guest-traffic-setup.png|"
+
+# 685689cd44444e13aefa015c58761ebb
+#: ../../networking/guest_traffic.rst:29
+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 router. Its eth2 interface is assigned a"
+" public IP address for public traffic. If multiple public VLAN is used, the "
+"router will have multiple public interfaces."
+msgstr "通常，管理服务会自动为每一个网络建立一个虚拟路由。一个虚拟路由实际上就是运行在物理主机上的一台特殊的虚拟机。每一台在一个独立网络中的虚拟路由有3个网口。如果使用多个公共 VLAN，相应的这台路由器就有多个公共的网口。 它的 eth0 网口是提供客户机通信的网关服务的，它的IP地址是 10.1.1.1。eth1 网口是为系统来配置这个虚拟路由而提供的。eth2 网口被赋予一个公共 IP 地址用来实现外部的公共通信。 同样如果使用了多个公共 VLAN 接入，这台路由器将会拥有多个公共的网口。"
+
+# c07d5440a8e64d5b912e6e98e6f9d078
+#: ../../networking/guest_traffic.rst:40
+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 "虚拟路由器提供DHCP功能，能自动的为每一个客户虚拟机在预先定义好的IP范围之内分配IP地址。用户也可以为虚拟机手工配置不同的IP地址。"
+
+# 360d9d124254479e85292973d6d8e7f9
+#: ../../networking/guest_traffic.rst:45
+msgid ""
+"Source NAT is automatically configured in the virtual router to forward "
+"outbound traffic for all guest VMs"
+msgstr "Source NAT功能是在虚拟路由里自动配置好的，它可以转发所有来宾虚拟机的外出流量。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/inter_vlan_routing.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/inter_vlan_routing.mo
new file mode 100644
index 0000000..547708f
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/inter_vlan_routing.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/inter_vlan_routing.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/inter_vlan_routing.po
new file mode 100644
index 0000000..c2517b7
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/inter_vlan_routing.po
@@ -0,0 +1,167 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:05+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 536a6b6a19a04686832c0c8f3202472a
+#: ../../networking/inter_vlan_routing.rst:18
+msgid "About Inter-VLAN Routing (nTier Apps)"
+msgstr "关于vlan间路由(多层应用)"
+
+# 01903cae08524fb18fb51475e29cccc5
+#: ../../networking/inter_vlan_routing.rst:20
+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 the VMs. In effect, "
+"you can segment VMs by means of VLANs into different networks that can host "
+"multi-tier applications, such as Web, Application, or Database. Such "
+"segmentation by means of VLANs logically separate application VMs for higher"
+" security and lower broadcasts, while remaining physically connected to the "
+"same device."
+msgstr "vlan间路由(多层应用)提供了在vlan间通过流量路由的功能。这个特性使你能够j建立私有云(vpc)，独立分割的云，可容纳多层应用程序。这些层被部署在不同的VLAN，可以互相沟通。您提供的VLAN层的创建和部署虚拟机可以在不同的层上。VLAN连接到一个虚拟路由器，这有利于虚拟机之间的通信。实际上，你可以通过不同定义的vlan来分割你的虚拟机到不同网络，以便承担多层应用，如Web，应用程序或数据库的虚拟机。通过VLAN的逻辑上独立的应用程序的虚拟具有较高的安全性和较低的广播，同时任然物理连接到同一设备。"
+
+# d835d5a69985471085a5688b045c4e38
+#: ../../networking/inter_vlan_routing.rst:33
+msgid "This feature is supported on XenServer, KVM, and VMware hypervisors."
+msgstr "在 XenServer ,KVM和 VMware hypervisors支持这个特性"
+
+# 7aecd1ac66b84f9cb92b03fea7d5edde
+#: ../../networking/inter_vlan_routing.rst:35
+msgid "The major advantages are:"
+msgstr "主要的优势为："
+
+# dca4c4be393c4d7bbcda75f49ffc8efc
+#: ../../networking/inter_vlan_routing.rst:37
+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 "管理可以部署一个vlans集，同时运行用户部署虚拟机在这些vlan上。从预先指定的vlan集中随机的为租户分配一个来宾vlan.租户处于同一层的所有vm处于分配给这个租户的来宾vlan."
+
+# d5d8b41e126e4b38913d0cf7de1ec29d
+#: ../../networking/inter_vlan_routing.rst:43
+msgid ""
+"A VLAN allocated for an account cannot be shared between multiple accounts."
+msgstr "一个租户分配到的vlan不能被多个租户共享"
+
+# 4e04be2a6cef4fa8973d317232221018
+#: ../../networking/inter_vlan_routing.rst:45
+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 "管理员允许所有用户创建自己的vpc,并部署应用。这个场景中，租户的虚拟机被部署到改租户的分配到的vlan中"
+
+# 48018251e76046c4a606035de8d1b4d5
+#: ../../networking/inter_vlan_routing.rst:49
+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 "管理员和用户都可以创建多个vpcs.当第一个虚拟机被部署到该层时候，一个来宾网络nic插入到这个vpc虚拟路由器上"
+
+# cc50778ecfab43c38af3373511f47072
+#: ../../networking/inter_vlan_routing.rst:53
+msgid ""
+"The administrator can create the following gateways to send to or receive "
+"traffic from the VMs:"
+msgstr "管理员创建网关用接受和发送来自vm的流量："
+
+# 5d91169a83a5400b8408b6ce4ccb84f5
+#: ../../networking/inter_vlan_routing.rst:56
+msgid ""
+"**VPN Gateway**: For more information, see `\"Creating a VPN gateway for the"
+" VPC\" <#creating-a-vpn-gateway-for-the-vpc>`_."
+msgstr "**VPN网关**:更多信息，参考 `\"为VPC创建VPN网关\" <#creating-a-vpn-gateway-for-the-vpc>`_."
+
+# 1f0ed1ecf964455ab40301bdf5ab2dc2
+#: ../../networking/inter_vlan_routing.rst:59
+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 "**公网网关**：当为vpc创建一个虚拟路由器时，这个vpc的公共网关就添加到虚拟路由器当中。公共网关还没有暴露到最终用户。你不允许其列出，也不允许建立任何静态路由。"
+
+# b843201a793749bb924d48f21be04e09
+#: ../../networking/inter_vlan_routing.rst:64
+msgid ""
+"**Private Gateway**: For more information, see \":ref:`adding-priv-gw-"
+"vpc`\"."
+msgstr "**私有网关**: 更多信息，参考 \":ref:`adding-priv-gw-vpc`\"."
+
+# a4ac63d4b99a4edd968087d0f622647a
+#: ../../networking/inter_vlan_routing.rst:66
+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 "管理员和用户可以创建各种可能的目的地的网关组合。但是，在部署中每种类型只能有一个网关。"
+
+# 50735b7154a64b7880f5543c4792b1c0
+#: ../../networking/inter_vlan_routing.rst:70
+msgid "For example:"
+msgstr "例如："
+
+# bdd41dc64438436aac12d9f1c8d5a8bc
+#: ../../networking/inter_vlan_routing.rst:72
+msgid ""
+"**VLANs and Public Gateway**: For example, an application is deployed in the"
+" cloud, and the Web application VMs communicate with the Internet."
+msgstr "**VLAN和公网网关**: 比如，在云中部署了一个应用，并且这个web应用所在的虚拟机要和因特网通信。"
+
+# f2c3b70246534d5aabdd3954a25ba1eb
+#: ../../networking/inter_vlan_routing.rst:76
+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 "**VLANs, VPN网关和公网网关**: 比如, 云中部署了一个应用;部署这个web应用的虚拟机要和因特网通信; 并且数据库虚拟要个先前提到的设备通信"
+
+# 7fb2fe01c3484b80a30d4c6edb0b5782
+#: ../../networking/inter_vlan_routing.rst:81
+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 "管理员可以在虚拟路由器定义一个访问控制列表(ACL)用于过滤vlan或者因特网和vlan直接的流量。你可定义基于CIDR,端口范围，协议，类型代码(如果选用ICPM协议)和进出流量的acl"
+
+# 95cd03acfa2948c682ec51eaf24346be
+#: ../../networking/inter_vlan_routing.rst:87
+msgid ""
+"The following figure shows the possible deployment scenarios of a Inter-VLAN"
+" setup:"
+msgstr "下图显示了可能的部署一个VLAN间的场景设置的："
+
+# a9f3216208ba417681d8885848d2a414
+#: ../../networking/inter_vlan_routing.rst:90
+msgid "|mutltier.png|"
+msgstr "|mutltier.png|"
+
+# 785b1c5286424a3680f6ffa4fa40de5a
+#: ../../networking/inter_vlan_routing.rst:92
+msgid ""
+"To set up a multi-tier Inter-VLAN deployment, see \":ref:`configuring-"
+"vpc`\"."
+msgstr "要建立一个多层次的跨VLAN部署，请参考\":ref:`configuring-vpc`\"."
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_forwarding_and_firewalling.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_forwarding_and_firewalling.mo
new file mode 100644
index 0000000..0c896ca
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_forwarding_and_firewalling.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_forwarding_and_firewalling.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_forwarding_and_firewalling.po
new file mode 100644
index 0000000..f4ebdc3
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_forwarding_and_firewalling.po
@@ -0,0 +1,499 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:05+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 3ec46c2d67cb4acc87705b3f0985e5c8
+#: ../../networking/ip_forwarding_and_firewalling.rst:18
+msgid "IP Forwarding and Firewalling"
+msgstr "IP转发及防火墙"
+
+# 5bb709bf233742ce8f3a83dc5ce7cf26
+#: ../../networking/ip_forwarding_and_firewalling.rst:20
+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 "默认情况下, 所有从公共IP进来的流量都会被拒绝. 所有在来宾网络出去的流量默认也被阻挡。"
+
+# 83f985061e4e4301aa5ce50049ea4565
+#: ../../networking/ip_forwarding_and_firewalling.rst:23
+msgid ""
+"To allow outgoing traffic, follow the procedure in :ref:`egress-fw-rules`."
+msgstr "为了允许外出的流量，遵循:ref:`egress-fw-rules`中的操作步骤。"
+
+# 1328a8040ae7487b8f7ed1dcaaf5a596
+#: ../../networking/ip_forwarding_and_firewalling.rst:25
+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 "为了允许接收到的流量, 用户可以设置一些防火墙规则和/或端口转发规则. 例如, 你可以在公共IP地址上设定防火墙规则来打开一个端口范围, 比如从33到44端口. 然后使用端口转发将流量从这个特定的范围内的端口直接送到指定的用户虚机端口. 例如, 一个端口转发的规则可以将接收的流量从公共IP的33端口到用户虚机私有IP的100端口."
+
+# 88ee727310bb4a5789291e8e48578dab
+#: ../../networking/ip_forwarding_and_firewalling.rst:35
+msgid "Firewall Rules"
+msgstr "防火墙规则"
+
+# 073cb21345c44ce2a3f2ce3446d4ad3a
+#: ../../networking/ip_forwarding_and_firewalling.rst:37
+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 "默认情况下，防火墙拒绝所有流入公共IP的流量。要允许外部流量，你需要制定防火墙规则打开防火墙端口。你可以选择性的制定一个或多个CIDR来过滤来源IP。这在当你只需要允许特定IP请求时会很有用。"
+
+# b43e4fc4f43841c9aebd342bbd60b33d
+#: ../../networking/ip_forwarding_and_firewalling.rst:43
+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 "你不能使用防火墙规则打开弹性IP的端口。当弹性IP处在使用状态时，外部的通过请求将被安全组管理。参阅 `\"添加安全组\" <#adding-a-security-group>`_."
+
+# 36b1e8acd3ef4b1cb7a7ffd1f60599c5
+#: ../../networking/ip_forwarding_and_firewalling.rst:48
+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 "在高级Zone中，您也可以用虚拟路由器来创建流出的防火墙规则。更多信息，请查阅\":ref:`egress-fw-rules`\"。"
+
+# 2aeb084c075b4451b0911c2a6baf0f84
+#: ../../networking/ip_forwarding_and_firewalling.rst:51
+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 "防火墙规则能在管理服务器的UI中防火墙选项卡里创建，CloudStac安装好以后，这个规则选项卡默认不显示，你需要以管理员身份修改全局变量 firewall.rule.ui.enabled为 \"true\"才能显示。"
+
+# e1408eeb730f4709bbba8852f79807fd
+#: ../../networking/ip_forwarding_and_firewalling.rst:57
+msgid "To create a firewall rule:"
+msgstr "创建防火墙规则："
+
+# 098b22043ec643559c039b39aa24d618
+# f62479b013c241a791c42b8843bd140d
+# c384f1b44804485fba23fe018c16683e
+#: ../../networking/ip_forwarding_and_firewalling.rst:59
+#: ../../networking/ip_forwarding_and_firewalling.rst:132
+#: ../../networking/ip_forwarding_and_firewalling.rst:245
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# a633160d3ee343639365b9067af58eb1
+# c6c7495d464a4262ace3361c7cce9b5b
+#: ../../networking/ip_forwarding_and_firewalling.rst:61
+#: ../../networking/ip_forwarding_and_firewalling.rst:134
+msgid "In the left navigation, choose Network."
+msgstr "在左侧的导航栏，选择网络。"
+
+# ff56e69810c34ee4a08280a7ef06cfbb
+#: ../../networking/ip_forwarding_and_firewalling.rst:63
+msgid "Click the name of the network where you want to work with."
+msgstr "点击拟修改的网络名称。"
+
+# d546be88025a4254b8eecf1f0b16bdf0
+#: ../../networking/ip_forwarding_and_firewalling.rst:65
+msgid "Click View IP Addresses."
+msgstr "点击查看IP地址。"
+
+# 0c60a7fde5644f9188c0bf190c166890
+#: ../../networking/ip_forwarding_and_firewalling.rst:67
+msgid "Click the IP address you want to work with."
+msgstr "点击你要修改的IP地址"
+
+# 0e0775a902554fa68fc54157ed73ed0a
+#: ../../networking/ip_forwarding_and_firewalling.rst:69
+msgid "Click the Configuration tab and fill in the following values."
+msgstr "点击设置选项卡 填入以下值："
+
+# 8bb21f2deca7442683f782de4a83935f
+#: ../../networking/ip_forwarding_and_firewalling.rst:71
+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 ""
+
+# 4cb05fbe28ae408a8df34014da711575
+#: ../../networking/ip_forwarding_and_firewalling.rst:76
+msgid "**Protocol**: The communication protocol in use on the opened port(s)."
+msgstr ""
+
+# e59d4d2a187f4510a91409fac5cfb51c
+#: ../../networking/ip_forwarding_and_firewalling.rst:79
+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 ""
+
+# 3274875afce44bbe9d7017bb4e2fc2b2
+#: ../../networking/ip_forwarding_and_firewalling.rst:83
+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 ""
+
+# 41821a610d844daf8255026b71299059
+# 1d39fcb3a5e34d769f89885db9866836
+# 2319658c89b74a0294ce8f0a253a4d53
+#: ../../networking/ip_forwarding_and_firewalling.rst:88
+#: ../../networking/ip_forwarding_and_firewalling.rst:163
+#: ../../networking/ip_forwarding_and_firewalling.rst:276
+msgid "Click Add."
+msgstr "点击 添加"
+
+# eec2e0a57feb4eca85c58ac1b58b228b
+#: ../../networking/ip_forwarding_and_firewalling.rst:94
+msgid "Egress Firewall Rules in an Advanced Zone"
+msgstr "高级区域中的出口防火墙规则"
+
+# 3bae6d1e0fb543beaeb466c40aeddfc3
+#: ../../networking/ip_forwarding_and_firewalling.rst:96
+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 rules are removed the default "
+"policy, Block, is applied."
+msgstr "出口流量起源于从专用网络访问公共网络，例如Internet。默认情况下，在默认网络方案中，出口流量被拒绝，所以没有从来宾网络到Internet的出口流量被允许。不过，你可以通过创建出口防火墙规则来控制高级网络中的出口流量。当出口防火墙规则被应用时，规则指定的流量被允许，其余的流量被阻止。当所有的防火墙规则从默认策略中移除，阻止策略再次被应用。"
+
+# 80fbdba2a681463894376f620458c160
+#: ../../networking/ip_forwarding_and_firewalling.rst:107
+msgid "Prerequisites and Guidelines"
+msgstr "先决条件和指南"
+
+# 998ae537c5664319b836e769ab967fc3
+#: ../../networking/ip_forwarding_and_firewalling.rst:109
+msgid "Consider the following scenarios to apply egress firewall rules:"
+msgstr "应用出口防火墙规则时请思考如下方案："
+
+# 18a68e97f28f4f7898b92513d34e5e26
+#: ../../networking/ip_forwarding_and_firewalling.rst:111
+msgid "Egress firewall rules are supported on Juniper SRX and virtual router."
+msgstr "出口防火墙规则在Jniper SRX和虚拟路由器中均支持。"
+
+# a4eaae6cb4474e5a8182092404f48116
+#: ../../networking/ip_forwarding_and_firewalling.rst:114
+msgid "The egress firewall rules are not supported on shared networks."
+msgstr "共享网络中不支持出口防火墙规则。"
+
+# 85bdd2e7a708485bae147bfa93cdcb1b
+#: ../../networking/ip_forwarding_and_firewalling.rst:116
+msgid ""
+"Allow the egress traffic from specified source CIDR. The Source CIDR is part"
+" of guest network CIDR."
+msgstr "允许特定源CIDR的出口流量。源CIDR是来宾网络CIDR的一部分。"
+
+# d9af348ce95e47a0bae91a55488b1155
+#: ../../networking/ip_forwarding_and_firewalling.rst:119
+msgid "Allow the egress traffic with protocol TCP,UDP,ICMP, or ALL."
+msgstr "允许出口流量的协议为TCP，UDP,ICMP或ALL。"
+
+# 786d85af2e334cf5a8a25fc59dde7cb5
+#: ../../networking/ip_forwarding_and_firewalling.rst:121
+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 "允许出口流量协议和目标端口范围。端口范围需要指定TCP，UDP或ICMP类型和代码。"
+
+# 8d9e5fa49cb648a6ad0b917f06176014
+#: ../../networking/ip_forwarding_and_firewalling.rst:124
+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 "新网络方案的默认策略是允许的，然而升级现有的网络方案后，防火墙服务提供商的出口策略默认将是拒绝。"
+
+# ee1ee0417255469abce66dbfd40f9611
+#: ../../networking/ip_forwarding_and_firewalling.rst:130
+msgid "Configuring an Egress Firewall Rule"
+msgstr "配置出口防火墙规则"
+
+# 4d43b047c25a4605acc888b025d376aa
+#: ../../networking/ip_forwarding_and_firewalling.rst:136
+msgid ""
+"In Select view, choose Guest networks, then click the Guest network you "
+"want."
+msgstr "在选择视图中，选择来宾网络，然后点击需要的来宾网络。"
+
+# 4c11dfc739f94ce0995b7c7bdf566e5d
+#: ../../networking/ip_forwarding_and_firewalling.rst:139
+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 "要添加出口策略，点击出口策略选项卡并填写以下字段指定哪种类型的流量在来宾网络中是被允许从VM中实例发送出的。"
+
+# a476fe8da41b43168b89c7b558afcb48
+#: ../../networking/ip_forwarding_and_firewalling.rst:143
+msgid "|egress-firewall-rule.png|"
+msgstr "|egress-firewall-rule.png|"
+
+# d56527f1ac864c5c9d47df9e55c225cf
+#: ../../networking/ip_forwarding_and_firewalling.rst:145
+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 "**CIDR**:(仅通过CIDR添加)为接受来来自特殊地址块的流量，输入一个CIDR，多个时用逗号隔开。CIDR是进入流量的基础IP地址。例如：192.168.0.0/22，为允许所有CIDR，请设为0.0.0.0/0"
+
+# c1e8fac9fa8046d8a9315511c011542e
+#: ../../networking/ip_forwarding_and_firewalling.rst:151
+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 "**协议**: 虚拟机发送流量所使用的网络协议。TCP和UDP通常用于数据交换和用户通讯。ICMP通常用于发送出错信息和网络监控数据。"
+
+# 6b9d46d4c88d48c98d3fa4fcceb60e29
+#: ../../networking/ip_forwarding_and_firewalling.rst:156
+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 "**开始端口，结束端口**: (仅对TCP，UDP)。目的地为进入流量而设的监听端口范围。如果仅开放了单个端口，则在两者的区域中用同一端口。"
+
+# 17c266c56f194132a6fc948f3142e4bc
+#: ../../networking/ip_forwarding_and_firewalling.rst:160
+msgid ""
+"**ICMP Type, ICMP Code**: (ICMP only) The type of message and error code "
+"that are sent."
+msgstr "**ICMP类型**, **ICMP代码** (ICMP only): 信息类型及发送错误的代码。"
+
+# f0100304289f4a67b01e8f6c52976a10
+#: ../../networking/ip_forwarding_and_firewalling.rst:167
+msgid "Configuring the Default Egress Policy"
+msgstr "配置默认出口策略"
+
+# a802326f92404392beacd9675985c106
+#: ../../networking/ip_forwarding_and_firewalling.rst:169
+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 "通过网络方案配置隔离来宾网络的默认出口策略。通过创建网络方案选项决定来宾网络到公共网络的所有流量在默认策略中是允许或者拒绝。使用该网络方案创建网络。如果没有指定策略，你创建的来宾网络中的所有流量将被允许。"
+
+# 9b5e480b6757449ab8272d3e7a691110
+#: ../../networking/ip_forwarding_and_firewalling.rst:177
+msgid "You have two options: Allow and Deny."
+msgstr "你有两个选择：允许和拒绝。"
+
+# 9b8d4463d6024d8589cc801658fa7bab
+#: ../../networking/ip_forwarding_and_firewalling.rst:180
+msgid "Allow"
+msgstr "允许"
+
+# 01d29e0665f84d548d9f41399d9258d8
+#: ../../networking/ip_forwarding_and_firewalling.rst:182
+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 "如果你选择网络方案为允许，则默认出口流量被允许。无论如何，当配置了来宾网络的出口规则，规则被应用于阻止特定的流量和允许其他的 。如果网络中没有配置出口规则，则出口流量会被放行。"
+
+# 63816b9551f04933aa99e27cc3dc34f1
+#: ../../networking/ip_forwarding_and_firewalling.rst:189
+msgid "Deny"
+msgstr "拒绝"
+
+# 1952d7735fb746a6834bbdeed4c1eaa9
+#: ../../networking/ip_forwarding_and_firewalling.rst:191
+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 "如果你选择网络方案为拒绝，则来宾网络中的默认出口流量将被阻挡。无论如何，当配置了来宾网络的出口规则，规则被应用于允许特定的流量。当实施来宾网络时，CloudStack为来宾网络添加防火墙出口规则指定默认的出口策略。"
+
+# 238db98415e74782937deddd3970b285
+#: ../../networking/ip_forwarding_and_firewalling.rst:198
+msgid "This feature is supported only on virtual router and Juniper SRX."
+msgstr "该特定只支持虚拟路由器和Juniper SRX。"
+
+# e460df960d61405db56e64d21a8c43d7
+#: ../../networking/ip_forwarding_and_firewalling.rst:200
+msgid "Create a network offering with your desirable default egress policy:"
+msgstr "为合适的默认出口策略创建一个网络方案："
+
+# 5271ad0a1d4a4a27aa5597b044b42acf
+#: ../../networking/ip_forwarding_and_firewalling.rst:202
+msgid "Log in with admin privileges to the CloudStack UI."
+msgstr "以管理员权限登录CloudStack用户界面。"
+
+# fd49a59627284ffda66fef7096eaa709
+#: ../../networking/ip_forwarding_and_firewalling.rst:204
+msgid "In the left navigation bar, click Service Offerings."
+msgstr "在左侧导航栏中，点击 服务方案。"
+
+# 7fce8b96f6e64727bb6063766c828bdd
+#: ../../networking/ip_forwarding_and_firewalling.rst:206
+msgid "In Select Offering, choose Network Offering."
+msgstr "在选择方案中，选择网络方案。"
+
+# ef8895c197ff4343b04aecc73b5a9294
+#: ../../networking/ip_forwarding_and_firewalling.rst:208
+msgid "Click Add Network Offering."
+msgstr "点击添加网络方案。"
+
+# abb73d0d766d4d32a4bbe32137193cad
+#: ../../networking/ip_forwarding_and_firewalling.rst:210
+msgid "In the dialog, make necessary choices, including firewall provider."
+msgstr "在对话框中，填写必选项，包括防火墙提供者。"
+
+# 932c30480a1f4e3ea92f06ba4296ae45
+#: ../../networking/ip_forwarding_and_firewalling.rst:213
+msgid "In the Default egress policy field, specify the behaviour."
+msgstr "在默认出口策略选项中，指定行为。"
+
+# 41d012a83e774bdeaeac42e5b44d851c
+#: ../../networking/ip_forwarding_and_firewalling.rst:215
+msgid "Click OK."
+msgstr "点击确定。"
+
+# 5a1192bc5c8a4c3c930879e56c5d58bb
+#: ../../networking/ip_forwarding_and_firewalling.rst:217
+msgid "Create an isolated network by using this network offering."
+msgstr "使用网络方案创建隔离网络。"
+
+# 3918ff66d4914376a4707b9db470a027
+#: ../../networking/ip_forwarding_and_firewalling.rst:219
+msgid ""
+"Based on your selection, the network will have the egress public traffic "
+"blocked or allowed."
+msgstr "根据你的选择，网络的出口公共流量将被拒绝或允许。"
+
+# 29ffedbd547e431f95d82b075df5ea66
+#: ../../networking/ip_forwarding_and_firewalling.rst:224
+msgid "Port Forwarding"
+msgstr "端口转发"
+
+# d9efd9df178e4f7c8d81b2ba24a9fdbb
+#: ../../networking/ip_forwarding_and_firewalling.rst:226
+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 "一个端口转发服务是一系列转发转发规则的集合。一个端口转发服务随后可以应用于一个或多个来宾虚拟机。来宾虚拟机会根据端口转发规则作相关进入端口的管理。你可以定义一个或多个CIDR来过滤源IP地址。当你只希望特定的IP流量进入时是相当有用的。"
+
+# ae4f5d3e4bc24f8584c17c3057688144
+#: ../../networking/ip_forwarding_and_firewalling.rst:234
+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 "一个客户VM可以在任意数量的端口转发服务中。端口转发服务可以不包含客户VM。如果客户VM在多个网络中，则端口转发仅在默认网络中定义时才生效。"
+
+# 89ce910349884d8ea8a7b4f6aee10613
+#: ../../networking/ip_forwarding_and_firewalling.rst:239
+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 "您不能使用端口转发打开弹性IP地址的端口。当使用弹性IP时，外部访问是由安全组控制的。参见安全组。"
+
+# 263627f6e1de45999d0e9ab68c8a1a2d
+#: ../../networking/ip_forwarding_and_firewalling.rst:243
+msgid "To set up port forwarding:"
+msgstr "设置端口转发："
+
+# 41c9b9f2473e4b5aa0d8ea3c54e45b1b
+#: ../../networking/ip_forwarding_and_firewalling.rst:247
+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 "如果还没有，请在 CloudStack中为Zone添加公网IP段。参阅 安装指南中的添加Zone和Pod。"
+
+# 2c98fbd961df4ef28a276b3ccf1d53c0
+#: ../../networking/ip_forwarding_and_firewalling.rst:251
+msgid "Add one or more VM instances to CloudStack."
+msgstr "在 CloudStack中创建1台或更多VM。"
+
+# 17a544cc6c8a42cbaef47575f1029173
+#: ../../networking/ip_forwarding_and_firewalling.rst:253
+msgid "In the left navigation bar, click Network."
+msgstr "在左边导航栏，点击网络。"
+
+# ade84b4f63694fadbe6c835b52ba796f
+#: ../../networking/ip_forwarding_and_firewalling.rst:255
+msgid "Click the name of the guest network where the VMs are running."
+msgstr "点击需要操作VM所在的网络名称。"
+
+# 48ab8bf9d7e04ca7a13eaf58eeead278
+#: ../../networking/ip_forwarding_and_firewalling.rst:257
+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 "选择一个已有的IP或者获取一个新的IP地址。参阅 `\"获取一个新的IP\" <#acquiring-a-new-ip-address>`_.。 点击列表中IP地址的名称。"
+
+# da392889cd304ce8973c2b4b8341665b
+#: ../../networking/ip_forwarding_and_firewalling.rst:261
+msgid "Click the Configuration tab."
+msgstr "点击配置选项卡。"
+
+# 4d02af0497b544d89616ff1ddf286767
+#: ../../networking/ip_forwarding_and_firewalling.rst:263
+msgid "In the Port Forwarding node of the diagram, click View All."
+msgstr "在图表的端口转发节点，点击查看所有。"
+
+# ee9101e2c97447d4b23f89177c60e7ab
+#: ../../networking/ip_forwarding_and_firewalling.rst:265
+msgid "Fill in the following:"
+msgstr "填写以下内容："
+
+# e9d9402255ae405781f85b32409d3654
+#: ../../networking/ip_forwarding_and_firewalling.rst:267
+msgid ""
+"**Public Port**: The port to which public traffic will be addressed on the "
+"IP address you acquired in the previous step."
+msgstr "**公用端口**: 你在前面操作所获取的供公共流量使用的公用IP地址的端口。 "
+
+# bf8d351e8ca649ca9931311f402ea7bc
+#: ../../networking/ip_forwarding_and_firewalling.rst:270
+msgid ""
+"**Private Port**: The port on which the instance is listening for forwarded "
+"public traffic."
+msgstr "**私有端口**: 虚拟机实例将被转发到公共流量的监听端口。"
+
+# 5140efc173fd46e194d6c4827a8a67fc
+#: ../../networking/ip_forwarding_and_firewalling.rst:273
+msgid "**Protocol**: The communication protocol in use between the two ports"
+msgstr ""
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_load_balancing.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_load_balancing.mo
new file mode 100644
index 0000000..44f1e59
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_load_balancing.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_load_balancing.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_load_balancing.po
new file mode 100644
index 0000000..861a833
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_load_balancing.po
@@ -0,0 +1,52 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 974ac2a4e2dd4641920f5361833b3e12
+#: ../../networking/ip_load_balancing.rst:18
+msgid "IP Load Balancing"
+msgstr "IP负载均衡"
+
+# 7eaede5161a04e0cbb6a4b15fc2de3b2
+#: ../../networking/ip_load_balancing.rst:20
+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 "用户可以选择关联同一个公网IP到多个虚拟机。 CloudStack实现了TCP级别的负载平衡器，有以下策略。"
+
+# 8c044fa0f1714d63815a08d7a658b08d
+#: ../../networking/ip_load_balancing.rst:24
+msgid "Round-robin"
+msgstr "轮询"
+
+# 6732c79a9ecf4eec91f6ddea4d55833a
+#: ../../networking/ip_load_balancing.rst:26
+msgid "Least connection"
+msgstr "最少连接数"
+
+# 28c3b6fa228545e382ed84cceaf1666a
+#: ../../networking/ip_load_balancing.rst:28
+msgid "Source IP"
+msgstr "源IP"
+
+# 0eac6f2afde349909f9ee8d0148a99b6
+#: ../../networking/ip_load_balancing.rst:30
+msgid ""
+"This is similar to port forwarding but the destination may be multiple IP "
+"addresses."
+msgstr "这类似于端口转发，但目标可能会有多个IP地址。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_reservation_in_guest_networks.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_reservation_in_guest_networks.mo
new file mode 100644
index 0000000..e6dd143
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_reservation_in_guest_networks.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_reservation_in_guest_networks.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_reservation_in_guest_networks.po
new file mode 100644
index 0000000..2b2be7d
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/ip_reservation_in_guest_networks.po
@@ -0,0 +1,282 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 25e21d9bd50e4db29764c09ec3255ea1
+#: ../../networking/ip_reservation_in_guest_networks.rst:18
+msgid "IP Reservation in Isolated Guest Networks"
+msgstr "隔离的来宾网络中的预留IP"
+
+# f043acb1e27b49aebecf48876dca90d4
+#: ../../networking/ip_reservation_in_guest_networks.rst:20
+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 "在隔离的来宾网络中，来宾IP地址空间中的一部分可以被保留下来以供非CloudStack VMs或者物理服务器使用。要真么做，你应该在来宾网络应用状态时依靠指定CIDR来配置一个预留IP地址范围。如果你的客户希望在同一个网络中有非CloudStack控制的VMs或者物理服务器，它们可以共享一部分主要为来宾网络提供的IP地址空间。"
+
+# fe77cb19c33a475f9389f57e62e466e0
+#: ../../networking/ip_reservation_in_guest_networks.rst:28
+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 called Reserved IP Range. When IP "
+"reservation is configured, the administrator can add additional VMs or "
+"physical servers that are not part of CloudStack to the same network and "
+"assign them the Reserved IP addresses. CloudStack guest VMs cannot acquire "
+"IPs from the Reserved IP Range."
+msgstr "在高级域中，定义一个网络时要给其赋予一个IP地址范围或CIDR。CloudStack虚拟路由器起着DHCP的作用，并通过CIDR来给客户虚拟机分配IP地址。如果为了预留CIDR不用于cloudstack，应当进行说明，即部分IP地址范围或CIDR仅能被DHCP服务分配给在cloudstack中创建的虚拟机。剩下的IP地址被称作预留IP地址范围。当预留的IP被配置时，管理员可以增加额外的虚拟机或并不属于cloudstack的物理服务器到同一个网络，可以将预留的IP地址指定给他们。cloudstack的客户虚拟机不能够从预留的IP地址中获得地址。"
+
+# 9428ab05bfce48cb9dce92078998854c
+#: ../../networking/ip_reservation_in_guest_networks.rst:43
+msgid "IP Reservation Considerations"
+msgstr "IP预留事项"
+
+# 5780d0b48e6f44cbb972018a31489ebb
+#: ../../networking/ip_reservation_in_guest_networks.rst:45
+msgid ""
+"Consider the following before you reserve an IP range for non-CloudStack "
+"machines:"
+msgstr "在给非cloudstack内的机器预留IP地址时，要考虑以下几个方面："
+
+# cc50e370af0c450588c711e282c0ac93
+#: ../../networking/ip_reservation_in_guest_networks.rst:48
+msgid "IP Reservation is supported only in Isolated networks."
+msgstr "IP预留仅在隔离网络内支持"
+
+# 9543f099f9de4fc3a8a815cd3cb04f40
+#: ../../networking/ip_reservation_in_guest_networks.rst:50
+msgid ""
+"IP Reservation can be applied only when the network is in Implemented state."
+msgstr "仅当网络在实施状态时，IP预留才能被应用。"
+
+# c7bc13975b37474299e4a7a65c56ed75
+#: ../../networking/ip_reservation_in_guest_networks.rst:53
+msgid "No IP Reservation is done by default."
+msgstr "默认不做IP预留。"
+
+# f7a970b25ef94f48bc75a5c8a5fd0a0c
+#: ../../networking/ip_reservation_in_guest_networks.rst:55
+msgid "Guest VM CIDR you specify must be a subset of the network CIDR."
+msgstr "指定客户的CIDR必须是网络CIDR的子网。"
+
+# a96a64591c4d498ca7c95b1458def6f3
+#: ../../networking/ip_reservation_in_guest_networks.rst:57
+msgid ""
+"Specify a valid Guest VM CIDR. IP Reservation is applied only if no active "
+"IPs exist outside the Guest VM CIDR."
+msgstr "指定一个有效的客户虚拟机CIDR。只有不活动的IP在客户虚拟机CIDR存在时，IP预留才能被应用。"
+
+# 0710411bb18c4764970dffcc49fe5dab
+#: ../../networking/ip_reservation_in_guest_networks.rst:60
+msgid ""
+"You cannot apply IP Reservation if any VM is alloted with an IP address that"
+" is outside the Guest VM CIDR."
+msgstr "如果任一虚拟机被分配了客户虚拟机CIDR之外的IP地址时，IP预留将不能应用。"
+
+# ba005fe1c84e4e5d8d8b2f2cbd904deb
+#: ../../networking/ip_reservation_in_guest_networks.rst:63
+msgid ""
+"To reset an existing IP Reservation, apply IP reservation by specifying the "
+"value of network CIDR in the CIDR field."
+msgstr "为重置一个已存在的IP预留，通过在CIDR框指定CIDR值就可应用IP预留。"
+
+# 23bef4e190a54c2298a52b3acb439c57
+#: ../../networking/ip_reservation_in_guest_networks.rst:66
+msgid ""
+"For example, the following table describes three scenarios of guest network "
+"creation:"
+msgstr "例如，下表描述了客户网络创建的三种情形："
+
+# fd80ccd9ee7947c6a41f35a77766ba87
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+msgid "Case"
+msgstr "案例"
+
+# 1b0d9124efce41c8bf2ff9c04f471053
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+msgid "CIDR"
+msgstr "CIDR"
+
+# 340cf6747d6449b09015c49437828468
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+msgid "Network CIDR"
+msgstr "网络CIDR"
+
+# ca9e89e3707343c6a6bb2e2c52dc4acd
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+msgid "Reserved IP Range for Non-CloudStack VMs"
+msgstr "非cloudstack虚拟机的IP预留范围"
+
+# e1395f7f735643f98e49f71acb302533
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+msgid "Description"
+msgstr "描述"
+
+# bfc721eb783042dbbd4049d97eeae50c
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+msgid "1"
+msgstr "1"
+
+# 07110191079642298d8d53f83f4a6fe7
+# a0e61e48b84a4bb297fead377ce043cf
+# d64231917df74c5189732a5fedd1d141
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+msgid "10.1.1.0/24"
+msgstr "10.1.1.0/24"
+
+# 865ea8d88306424bab506a500520c22e
+# 184b1eac870b483f910546a5d5b37906
+# 70f4868471d54ac882b8093eb1db9f74
+# 3c040050888741f09b3cee5a8482aca4
+#: ../../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
+msgid "None"
+msgstr "无"
+
+# 24e526351c7b4686b16e030bc869d399
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+msgid "No IP Reservation."
+msgstr "无"
+
+# 81f560cf3b4c47bbb2b781add102de88
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+msgid "2"
+msgstr "2"
+
+# 725f92aed0d44be3bb5865f246acc29d
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+msgid "10.1.1.0/26"
+msgstr "10.1.1.0/26"
+
+# 02e4012c8ce94d95a0c5e4d5088637fd
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+msgid "10.1.1.64 to 10.1.1.254"
+msgstr "10.1.1.64-10.1.1.254"
+
+# 8fe36bed92d2475bbdd0fa903eb8c54b
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+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 "在界面的CIDR框内输入10.1.1.0/26或通过UpdateNetwork的API配置为guestvmcidr=10.1.1.0/26，进行IP预留配置"
+
+# e2c363737b654228a0ac0581ba4c55c8
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+msgid "3"
+msgstr "3"
+
+# 139e9ad2489d40738198ebfac4b14c45
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+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 "在界面的CIDR框内输入10.1.1.0/24或通过UpdateNetwork API配置为guestvmcidr=10.1.1.0/24，进行IP预留清除"
+
+# 43bbd9a15792420cb8b1e694ad792cf2
+#: ../../networking/ip_reservation_in_guest_networks.rst:83
+msgid "Limitations"
+msgstr "局限性"
+
+# 1ed6f796d3f04ed0b5c96512bc673c25
+#: ../../networking/ip_reservation_in_guest_networks.rst:85
+msgid ""
+"The IP Reservation is not supported if active IPs that are found outside the"
+" Guest VM CIDR."
+msgstr "如果在客户虚拟机CIDR外发现活动的IP地址，IP预留将不被支持。"
+
+# 28ed30440a3543f6b7744261f3f5c2e0
+#: ../../networking/ip_reservation_in_guest_networks.rst:88
+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 "在IP预留中，引起CIDR变化的网络升级方案都将无效，如将无外部设备的方案升级到带有外部设备的方案。在新实施的网络中，要重新配置IP预留。"
+
+# f9aacfd3f1a94c7c8d3ca0910da962a9
+#: ../../networking/ip_reservation_in_guest_networks.rst:95
+msgid "Best Practices"
+msgstr "最佳实践"
+
+# c5d0950bef8a49ce9b373d64fcf22b86
+#: ../../networking/ip_reservation_in_guest_networks.rst:97
+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 "一旦网络状态变为实施，应尽快应用IP预留到客户网络。如果在第一台客户虚拟机部署后应用IP预留，则会在应用IP会有较少的冲突发生。"
+
+# 636d85b86d5a460788a233fd1cb49014
+#: ../../networking/ip_reservation_in_guest_networks.rst:104
+msgid "Reserving an IP Range"
+msgstr "预留一个IP范围"
+
+# 34eb58849cb141e9898291a434cc05ba
+#: ../../networking/ip_reservation_in_guest_networks.rst:106
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# 3dc484e1bd5145259125fe0fcf8ccf8c
+#: ../../networking/ip_reservation_in_guest_networks.rst:108
+msgid "In the left navigation, choose Network."
+msgstr "在左侧的导航栏，选择网络。"
+
+# e4559a4e7ddf4812890314b955dae344
+#: ../../networking/ip_reservation_in_guest_networks.rst:110
+msgid "Click the name of the network you want to modify."
+msgstr "点击你要修改的网络名称。"
+
+# 9119b8d7ea884da4b996f8a191d30e0b
+#: ../../networking/ip_reservation_in_guest_networks.rst:112
+msgid "In the Details tab, click Edit. |ip-edit-icon.png|"
+msgstr ""
+
+# 31eaf6bfc27e465e950da4b920fbad80
+#: ../../networking/ip_reservation_in_guest_networks.rst:114
+msgid "The CIDR field changes to editable one."
+msgstr "CIDR框将变为可编辑状态"
+
+# f29831c8666d45218af0ae6769e46fff
+#: ../../networking/ip_reservation_in_guest_networks.rst:116
+msgid "In CIDR, specify the Guest VM CIDR."
+msgstr "在CIDR框，说明客户虚拟机的CIDR"
+
+# 41acec1236df4ddbad427f23127244b1
+#: ../../networking/ip_reservation_in_guest_networks.rst:118
+msgid "Click Apply."
+msgstr "点击应用"
+
+# 8213a6fd8f414bd2b710a4ee77b167ae
+#: ../../networking/ip_reservation_in_guest_networks.rst:120
+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/zh_CN/LC_MESSAGES/networking/isolation_in_advanced_zone_with_vlan.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/isolation_in_advanced_zone_with_vlan.mo
new file mode 100644
index 0000000..b96b0ae
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/isolation_in_advanced_zone_with_vlan.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/isolation_in_advanced_zone_with_vlan.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/isolation_in_advanced_zone_with_vlan.po
new file mode 100644
index 0000000..f7ca60e
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/isolation_in_advanced_zone_with_vlan.po
@@ -0,0 +1,363 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 2ce5e59640934ab387652df180ce1583
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:18
+msgid "Isolation in Advanced Zone Using Private VLAN"
+msgstr "使用Private VLAN隔离高级Zone中的网络"
+
+# 813ada1771994469abac6b243cbc4ed6
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:20
+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 users' VMs."
+msgstr "在共享网络中的隔离来宾流量能被Private VLAN（PVLAN）获取。PVLANs提供同一个VLAN里端口间的2层网络隔离。在启用了PVLAN的共享网络，一个用户VM不能到达其他用户VM，但是他们能与DHCP服务器和网关通讯，反过来这样能允许用户去控制网络内部的流量，并且帮助他们像阻止与其他用户VMs通讯一样的去部署无需通讯的多个应用程序。"
+
+# 1f6fb3f08ede4dbcbd7c9017afd047dd
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:29
+msgid "Isolate VMs in a shared networks by using Private VLANs."
+msgstr "使用PVLAN在共享网络中隔离VMs。"
+
+# c578b86e668046b18652e81289fd1811
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:31
+msgid "Supported on KVM, XenServer, and VMware hypervisors"
+msgstr "在KVM，XenServer和VMware hypervisors中支持"
+
+# f410d2d58c4b4e91b95fec05d57cf0b8
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:33
+msgid ""
+"PVLAN-enabled shared network can be a part of multiple networks of a guest "
+"VM."
+msgstr "启用了PVLAN的共享网络可以是来宾VM的多个网络的一部分。"
+
+# 23d9d81e853644d8a8e311853c02a801
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:38
+msgid "About Private VLAN"
+msgstr "关于Private VLAN"
+
+# a83e1c8b0ee2433b8776507d78fdd2b4
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:40
+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 VLAN that is being divided "
+"into smaller groups is called Primary, which implies that all VLAN pairs in "
+"a private VLAN share the same Primary VLAN. All the secondary VLANs exist "
+"only inside the Primary. Each Secondary VLAN has a specific VLAN ID "
+"associated to it, which differentiates one sub-domain from another."
+msgstr "在以太网交换机中，VLAN是二层网络中的一个主机之间主机能建立直接通讯的广播域 。Private VLAN被设计成一个标准的VLAN的延伸，为了进一步细分逻辑广播域。一个规则的VLAN是单一广播域，但是一个 private VLAN将一个较大的VLAN广播域划分为较小的多个子域。子域表现为一对VLANs：一个主VLAN和一个辅助VLAN。被划分为较小组的原始VLAN叫主，这意味着所有的在private VLAN中的VLAN对共享着同一个主VLAN。所有的辅助VLANs存在与主VLAN中。每个辅助VLAN有一个特定的区别于其他子域VLAN ID。"
+
+# 4b8abf8fe1534c228333ad081037a150
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:53
+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 "在private VLAN中有三种端口类型，它们实质上决定了所包含的主机的流量走势。每组端口都有自己唯一的策略，它能控制配置同一个private VLAN域中连接到端口的主机与其他已连接主机的通讯。使用下面三种端口定义中的一种来配置每个PVLAN对中的主机："
+
+# d369217099d04739b0c778e20ac02897
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:60
+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 "**混杂模式（Promiscuous）**：混杂模式的端口能与所有的接口通讯，包括可通讯与隔离属于辅助VLANs的主机端口。在混杂模式中，主机被连接到混在模式端口并且能够直接与主VLAN和辅助VLAN中的资源。典型的连接到混杂模式端口的是路由器，DHCP服务器和其他受信任的设备。"
+
+# 1e0c762b123d404eaedebd33003ad75b
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:68
+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 "**隔离(Isolated)VLANs**: 隔离模式VLAN中的端口不能与其他二层网络中的端口通讯。连接隔离模式端口上的主机只能直接与混杂模式下的资源通讯。如果你的客户设备只访问网关路由器，请将其附加至隔离端口。"
+
+# 15e3128ebacd47afb6aa943d0f2a5df1
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:74
+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 communicate among themselves, deploy them in "
+"community ports."
+msgstr "**Community VLANs**：中的端口能与其他端口和混杂模式下的端口通讯，但是他们不能与二层网络中的其他community VLAN中的端口通讯。在Community模式下，主机能与同一community中的主机和连接到混杂模式中的主VLAN的主机可以通讯。如果你的客户有两个设备需要与其他客户的设备隔离，但是他们之间又要通讯，请将他们部署至 community 端口。"
+
+# 6a977183f6864375ada79a287e63bab3
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:84
+msgid "For further reading:"
+msgstr "延伸阅读："
+
+# ca791914bab54854b0b9c5cfdbb20be8
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:86
+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 "`理解 Private VLANs <http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_25_see/configuration/guide/swpvlan.html#wp1038379>`_"
+
+# e676f05feb9a46d6974a4ed7048edad2
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:89
+msgid ""
+"`Cisco Systems' Private VLANs: Scalable Security in a Multi-Client "
+"Environment <http://tools.ietf.org/html/rfc5517>`_"
+msgstr "`Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment <http://tools.ietf.org/html/rfc5517>`_"
+
+# d5429c82db8a47aa82c6bf7602605f93
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:92
+msgid ""
+"`Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview "
+"(1010691) <http://kb.vmware.com>`_"
+msgstr "`Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview (1010691) <http://kb.vmware.com>`_"
+
+# ad67b66852ee445b847bec89936c0d02
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:97
+msgid "Prerequisites"
+msgstr "先决条件"
+
+# 1f2367cd590b456b9590a9b2616c8ad5
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:99
+msgid "Use a PVLAN supported switch."
+msgstr "在支持的交换机上使用PVLAN。"
+
+# f2c1161babac465c93d8ff531d97174d
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:101
+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 "更多信息，请参考 `Private VLAN Catalyst Switch Support Matrix <http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a0080094830.shtml>`_ "
+
+# d6805374b5244b3da5f5a39bbb521739
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:105
+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 "将所有能识别PVLAN的二层交换机之间互连，并且其中一个要连至一个路由器。主机连接到的所有端口需配置为trunk模式。打开VLAN管理，主VLAN（公共网络）和隔离的辅助VLAN端口。配置交换机连接到路由器的端口为PVLAN混杂trunk，这样可以为不识别PVLAN的路由器转换一个隔离的VLAN到主VLAN。"
+
+# 3afd52bf2fa3442b8f0721d8bca53715
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:113
+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 "注意只有Cisco Catalyst 4500有PVLAN混杂trunk模式，可以连接所有普通VLAN和PVLAN到不能识别PVLAN的交换机。其他支持PVLAN的Catalyst交换机，在PVALN对中的每个交换机上使用级联线连接到上联交换机。"
+
+# 5ce2b463414844099564cd171152b994
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:118
+msgid "Configure private VLAN on your physical switches out-of-band."
+msgstr "在你的物理交换机上使用带外管理配置private VLAN。"
+
+# 2cd1aebdb79742a3ab786e439ef69d89
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:120
+msgid "Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS)."
+msgstr "在XenServer和KVM上使用PVALN之前，请启用Open vSwitch (OVS)。"
+
+# 23029ff5d87847c3b9a551d1755aae1a
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:123
+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 "XenServer和KVM中的OVS不支持原生的PVLAN。因此，靠修改flow table，CloudStack为XenServer和KVM模拟OVS中的PVLAN。"
+
+# 1ab529fe7a53485da31a8085c5fc8181
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:129
+msgid "Creating a PVLAN-Enabled Guest Network"
+msgstr "配置一个启用了PVLAN的来宾网络"
+
+# 73811e0470e04b63a31d32549a8c882b
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:131
+msgid "Log in to the CloudStack UI as administrator."
+msgstr "作为管理员登录到CloudStack用户界面。"
+
+# f987d4525be34ae986962e374a48197f
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:133
+msgid "In the left navigation, choose Infrastructure."
+msgstr "在左边的导航，选择基础架构。"
+
+# 81a7cad61d0c43e3989e9742e6efb902
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:135
+msgid "On Zones, click View More."
+msgstr "在区域页面，点击查看全部。"
+
+# 62eb1c2209d34440987b38dc999dad75
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:137
+msgid "Click the zone to which you want to add a guest network."
+msgstr "选择要添加客户网络的那个区域。"
+
+# aeaece1bb557450383b2b0c0930b8d39
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:139
+msgid "Click the Physical Network tab."
+msgstr "点击物理网络标签卡。"
+
+# bdccf5bb73ce4a58b074c7db9f09db19
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:141
+msgid "Click the physical network you want to work with."
+msgstr "选择您要操作的物理网络。"
+
+# d325d3d79e0e41fd9ce93131ae2ea76a
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:143
+msgid "On the Guest node of the diagram, click Configure."
+msgstr "在客户节点界面，点击配置。"
+
+# 3254ff32eecc4e9b9ac57fc4f2219acd
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:145
+msgid "Click the Network tab."
+msgstr "点击网络选项卡。"
+
+# fdd056f25bee447e98028c9301071fd7
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:147
+msgid "Click Add guest network."
+msgstr "点击 添加来宾网络。"
+
+# f58f17bd25284897abbe7df71fc2c3fb
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:149
+msgid "The Add guest network window is displayed."
+msgstr "现实添加客户网络窗口。"
+
+# 5e421fb492504766a709b728f4fc51e5
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:151
+msgid "Specify the following:"
+msgstr "指定以下信息："
+
+# 606686347ca84fbc9a83c5f46c31d8ea
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:153
+msgid "**Name**: The name of the network. This will be visible to the user."
+msgstr "**Name**: 要建立的网络的名字。这个是用户可见的"
+
+# 73bbe5e4075e43f39b388b8b267c5401
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:156
+msgid ""
+"**Description**: The short description of the network that can be displayed "
+"to users."
+msgstr "**描述**: 提供一个简短的方案描述。 "
+
+# 17a0fe7f48cc4af3bbe7b8e52b6f6d1b
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:159
+msgid "**VLAN ID**: The unique ID of the VLAN."
+msgstr "**VLAN ID**: VLAN 的ID。"
+
+# 1656d47de54d42a788bc34e0a0c5f2e4
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:161
+msgid ""
+"**Secondary Isolated VLAN ID**: The unique ID of the Secondary Isolated "
+"VLAN."
+msgstr "**辅助隔离VLAN ID**：辅助隔离VLAN的唯一ID。"
+
+# 22e09670bce14054b1c11ce5ff049ba5
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:164
+msgid ""
+"For the description on Secondary Isolated VLAN, see `About Private VLAN\" "
+"<#about-private-vlan>`_."
+msgstr "更多关于辅助隔离VLAN的描述，请参考see `关于 Private VLAN\" <#about-private-vlan>`_."
+
+# 38765c8ae24048dba72826d07d096afe
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:167
+msgid "**Scope**: The available scopes are Domain, Account, Project, and All."
+msgstr "**Scope**: 可用的范围，包括域，帐户，项目和其他所以。"
+
+# 90706772c0084832b86742ce99f99d6e
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:170
+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 "**Domain**: 域，指定客户网络范围的域。指定域中的网络相对其他域是隔离不可见的。如果指定子域访问，域中的客户网络将在所有的子域中可用。"
+
+# 7e174e9b956f4f2784d5196f1a30439f
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:176
+msgid ""
+"**Account**: The account for which the guest network is being created for. "
+"You must specify the domain the account belongs to."
+msgstr "**Account**: 这里的帐户是为建立客户网络所指定的。必须指定域中所属的帐户。"
+
+# d8216708afb2490c97e3cca13b2752dd
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:180
+msgid ""
+"**Project**: The project for which the guest network is being created for. "
+"You must specify the domain the project belongs to."
+msgstr "**Project**: 项目是客户网络所建立的项目。必须为这个项目指定域。"
+
+# 3aa0f96be4f84d1bae1f1744b108dff8
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:184
+msgid ""
+"**All**: The guest network is available for all the domains, account, "
+"projects within the selected zone."
+msgstr "**All**: 选择它，会让客户网络对这个区域（Zone）中的所有域，帐户和项目都可用。"
+
+# 339b47c6f0f94ca4a221c0f592e92d5b
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:187
+msgid ""
+"**Network Offering**: If the administrator has configured multiple network "
+"offerings, select the one you want to use for this network."
+msgstr "**网络提议**: 如果管理员已经配置了多个网络方案，可以选择你需要的那个。"
+
+# ae2111debd664f179fe8eb3b251587ff
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:191
+msgid "**Gateway**: The gateway that the guests should use."
+msgstr "**Guest gateway**: 虚拟机需要使用的网关。"
+
+# df6c332c5f7e427d867dcef1784c0731
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:193
+msgid "**Netmask**: The netmask in use on the subnet the guests will use."
+msgstr "**Netmask**: 虚拟机子网要使用的网络掩码。"
+
+# 5331fd382d74450c957ad9e5fa46a095
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:195
+msgid ""
+"**IP Range**: A range of IP addresses that are accessible from the Internet "
+"and are assigned to the guest VMs."
+msgstr "**IP Range**: 定义公网IP范围，这些IP用来访问公网或是从公网访问客户虚拟机。"
+
+# 6be7da6ede894331ad2082717f19c89d
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:198
+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 "**网络域**: 如果你想为客户虚机网络定义一个域名，在此处输入后缀名。"
+
+# 0f106d1db97249348138b9cf76182524
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:202
+msgid "Click OK to confirm."
+msgstr "点击确定。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_guest_networks.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_guest_networks.mo
new file mode 100644
index 0000000..bde4667
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_guest_networks.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_guest_networks.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_guest_networks.po
new file mode 100644
index 0000000..679e057
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_guest_networks.po
@@ -0,0 +1,362 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# cbc2c710bdfe4a52822f6acf8381d1dd
+#: ../../networking/multiple_guest_networks.rst:18
+msgid "Using Multiple Guest Networks"
+msgstr "使用多个来宾网络"
+
+# 43824860271641cabc92b4e2fea91b0d
+#: ../../networking/multiple_guest_networks.rst:20
+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 "在使用高级网络的资源域里, 额外的来宾网络可以在初始安装后任何时间添加. 你还可以通过指定DNS后缀为每个网络自定义关联的域名."
+
+# e7a7a8ebce174e439d282d7c86c23ffc
+#: ../../networking/multiple_guest_networks.rst:25
+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 "一个虚机的网络在其创建时定义. 当一个虚机创建以后, 就不能对其网络添加删除, 即便用户可以进入客户虚机删除指定网卡的IP地址."
+
+# c1facfd27f164a849bd7151e92129d58
+#: ../../networking/multiple_guest_networks.rst:30
+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 "每一个虚机只有一个默认的网络. 在这个默认网络里, 虚拟路由器的DHCP响应将设置客户的默认网关. 除了单一,必须的默认网络, 多个非默认的网络也可以添加到客户虚机里. 管理员可以控制哪个网络作为默认的网络."
+
+# 008bbd9e609541888208d792dda845fd
+#: ../../networking/multiple_guest_networks.rst:36
+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 "附加的网络可以给所有账户使用或者分配给特定的账户. 对所有账户都可用的网络在整个资源域有效. 任何可以访问这个资源域的用户都可以使用这个网络创建虚机. 这些资源域一级的网络基本不提供客户之间的隔离. 分配给特定帐户的网络提供强制隔离的功能."
+
+# e8b12ba98b314fcca6f8659fdffe0e5a
+#: ../../networking/multiple_guest_networks.rst:45
+msgid "Adding an Additional Guest Network"
+msgstr "增添一个虚拟机的网络"
+
+# fc94885acfb44c089b5b955040cda635
+# e90f66fa32fb4ac0bdd48def8833e52d
+# 443695bf438a4240b9c354d9c66f2292
+# dc150422f8d8498e81ccfa11cc7daf5f
+# f4162f2a3af54aee90b80a9efec6523f
+#: ../../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
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# e9d2f3becfba421592c540e757fe27e8
+# 1e2cad5b28aa4f56bfee80c03c969d5c
+#: ../../networking/multiple_guest_networks.rst:49
+#: ../../networking/multiple_guest_networks.rst:179
+msgid "In the left navigation, choose Network."
+msgstr "在左侧的导航栏，选择网络。"
+
+# 4e88ac1dcf2144278c13cac5cf518978
+#: ../../networking/multiple_guest_networks.rst:51
+msgid "Click Add guest network. Provide the following information:"
+msgstr "地阿基添加来宾网络。提供以下信息："
+
+# 752dce8be6894794b7f10719d33214c9
+#: ../../networking/multiple_guest_networks.rst:53
+msgid "**Name**: The name of the network. This will be user-visible."
+msgstr "**Name**：网络的名称。对于最终用户可见。"
+
+# 68d2d60b814f4b48805d73f511a0c3f4
+#: ../../networking/multiple_guest_networks.rst:55
+msgid ""
+"**Display Text**: The description of the network. This will be user-visible."
+msgstr "**Display Text**:网络的描述信息。对于最终用户可见。"
+
+# 2e28d86b3670448ea924597e1a6eafbb
+#: ../../networking/multiple_guest_networks.rst:58
+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 "**Zone**：此网络所应用到zone的名称。每个zone都是一个广播域，因此每个zone中的来宾网络都有不同的IP范围。管理员必须为每个zone配置IP范围。"
+
+# 783fa5ad4bb94a898e27fb2fb400ce30
+#: ../../networking/multiple_guest_networks.rst:63
+msgid ""
+"**Network offering**: If the administrator has configured multiple network "
+"offerings, select the one you want to use for this network."
+msgstr "**Network offering**: 如果管理员已经配置了多个网络，选择一个你想使用的。"
+
+# e6d0251f520945198846d9589071d11c
+#: ../../networking/multiple_guest_networks.rst:67
+msgid "**Guest Gateway**: The gateway that the guests should use."
+msgstr "**Guest Gateway**: 来宾网络的网关。"
+
+# 82e7d212928549ba947dfe5e04919372
+#: ../../networking/multiple_guest_networks.rst:69
+msgid ""
+"**Guest Netmask**: The netmask in use on the subnet the guests will use."
+msgstr "**Guest Netmask**: 来宾网络的子网掩码。"
+
+# 333d9595d92b4dbc9842d746d1dd8448
+#: ../../networking/multiple_guest_networks.rst:72
+msgid "Click Create."
+msgstr "点击创建。"
+
+# cadd27c83ef84c9e9ce49c9ce9e5d8ca
+#: ../../networking/multiple_guest_networks.rst:76
+msgid "Reconfiguring Networks in VMs"
+msgstr "在VMs中重新配置网络"
+
+# 38552d30397849ea975e0b5d28fd31a0
+#: ../../networking/multiple_guest_networks.rst:78
+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 "CloudStack能让你在不同网络间移动VMs和重新配置VM的网络。你可以从一个网络中移除一个VM，再将其移动到另一个网络。你同样可以修改虚拟机的默认我拿过来，使用这个功能，混合和传统的服务器负载可以被轻松缓解。"
+
+# 205bea0ed92e4de594873aa8e5ad9d45
+#: ../../networking/multiple_guest_networks.rst:84
+msgid "This feature is supported on XenServer, VMware, and KVM hypervisors."
+msgstr "XenServer、VMware和KVM hypervisors支持这个特性。"
+
+# 7d8b8d41cfa04ea0b337a64b1206ae92
+#: ../../networking/multiple_guest_networks.rst:88
+msgid "Prerequisites"
+msgstr "先决条件"
+
+# bd4145a5e8ae4ca29cd7bdd5b1aab637
+#: ../../networking/multiple_guest_networks.rst:90
+msgid ""
+"Ensure that vm-tools are running on guest VMs for adding or removing "
+"networks to work on VMware hypervisor."
+msgstr "确保虚拟机上安装了vm-tools以便通过VMware hypervisor添加或移除网络。"
+
+# 42b8d9502ed54485bde4210b8fdbb499
+#: ../../networking/multiple_guest_networks.rst:95
+msgid "Adding a Network"
+msgstr "添加网络"
+
+# c398a820cb1648bc8799135cbaa74b1b
+# d48f631728b44c90be3cb811c9cd0505
+# 37c98038af7f4dc6a120b05e4e13c555
+#: ../../networking/multiple_guest_networks.rst:99
+#: ../../networking/multiple_guest_networks.rst:137
+#: ../../networking/multiple_guest_networks.rst:155
+msgid "In the left navigation, click Instances."
+msgstr "在左侧的导航菜单中，点击实例。"
+
+# b25bff80ed07457f9b1f926c0a58cc6c
+# 39876863e78d47378acdd305a1e22606
+# 2f4e1895d207479597c89b7b137794df
+#: ../../networking/multiple_guest_networks.rst:101
+#: ../../networking/multiple_guest_networks.rst:139
+#: ../../networking/multiple_guest_networks.rst:157
+msgid "Choose the VM that you want to work with."
+msgstr "选择你要处理的VM。"
+
+# 00b5baacd9084cd580b5fc02a2eb93fb
+# cd7d2fceff8d47d5b392be059b471ab9
+# 3f13993fdab542d6b8318cc2fe353acb
+#: ../../networking/multiple_guest_networks.rst:103
+#: ../../networking/multiple_guest_networks.rst:141
+#: ../../networking/multiple_guest_networks.rst:159
+msgid "Click the NICs tab."
+msgstr "点击网络适配器标签。"
+
+# 47b1307c53ed41dfbe754e5141219451
+#: ../../networking/multiple_guest_networks.rst:105
+msgid "Click Add network to VM."
+msgstr "将网络添加到 VM"
+
+# ebd8002977894bed935a5229f868dc66
+#: ../../networking/multiple_guest_networks.rst:107
+msgid "The Add network to VM dialog is displayed."
+msgstr "显示添加网络对话框。"
+
+# fa83b310f8904d8587c3dfdc52cacbad
+#: ../../networking/multiple_guest_networks.rst:109
+msgid ""
+"In the drop-down list, select the network that you would like to add this VM"
+" to."
+msgstr "在下拉列表里选择你要添加给VM的网络。"
+
+# dd48bfa27d7345aa87c6b7e63a358160
+#: ../../networking/multiple_guest_networks.rst:112
+msgid ""
+"A new NIC is added for this network. You can view the following details in "
+"the NICs page:"
+msgstr "这样就为这个网络添加了一个新网卡。你可以在网卡页面查看下列信息："
+
+# 6463c065bc1943008470d1edad582974
+#: ../../networking/multiple_guest_networks.rst:115
+msgid "ID"
+msgstr "ID"
+
+# 9420ad95bce443da9b81765885249155
+#: ../../networking/multiple_guest_networks.rst:117
+msgid "Network Name"
+msgstr "网络名称"
+
+# f846a9f3d938451198081772cc74cb85
+#: ../../networking/multiple_guest_networks.rst:119
+msgid "Type"
+msgstr "类型"
+
+# 8592916e5acf4e70bafbdbda7c00c614
+#: ../../networking/multiple_guest_networks.rst:121
+msgid "IP Address"
+msgstr "IP地址"
+
+# c75427419ce04483b71df9bd261c2fbd
+#: ../../networking/multiple_guest_networks.rst:123
+msgid "Gateway"
+msgstr "网关"
+
+# d008ddbc8a054a27ae521d3e3b8a4013
+#: ../../networking/multiple_guest_networks.rst:125
+msgid "Netmask"
+msgstr "子网掩码"
+
+# 41cff6439a0b42b5abab39913bc773bb
+#: ../../networking/multiple_guest_networks.rst:127
+msgid "Is default"
+msgstr "默认的"
+
+# cb23bf06693941579c5993219c416bb8
+#: ../../networking/multiple_guest_networks.rst:129
+msgid "CIDR (for IPv6)"
+msgstr "CIDR（IPv6）"
+
+# bce02b8426584ab693112a2a3eaa69a4
+#: ../../networking/multiple_guest_networks.rst:133
+msgid "Removing a Network"
+msgstr "移除网络"
+
+# ca1c1c7c1c9d4ff8aaca289a38a6f7c0
+#: ../../networking/multiple_guest_networks.rst:143
+msgid "Locate the NIC you want to remove."
+msgstr "找到你要移除的网卡上。"
+
+# 85a4e2e7437642f18635fa647891d856
+#: ../../networking/multiple_guest_networks.rst:145
+msgid "Click Remove NIC button. |remove-nic.png|"
+msgstr "点击移除网卡按钮。|remove-nic.png|"
+
+# ffa7cf9f06374be19a3b64261219cdc1
+# 5597778b6dec4d1fac608939422f4a00
+#: ../../networking/multiple_guest_networks.rst:147
+#: ../../networking/multiple_guest_networks.rst:165
+msgid "Click Yes to confirm."
+msgstr "点击Yes确认。"
+
+# 78a6b76d558e43c18b80b80d9ae29567
+#: ../../networking/multiple_guest_networks.rst:151
+msgid "Selecting the Default Network"
+msgstr "选择默认网络"
+
+# d548799e04664a74b122217c8b65678f
+#: ../../networking/multiple_guest_networks.rst:161
+msgid "Locate the NIC you want to work with."
+msgstr "找到你想要的网卡。"
+
+# 43217c75ff3e4ac885b27d575f4c47ee
+#: ../../networking/multiple_guest_networks.rst:163
+msgid "Click the Set default NIC button. |set-default-nic.png|."
+msgstr "点击设置为默认网卡按钮。 |set-default-nic.png|."
+
+# fea27f4c1e3f45e89b4b9439c9affb16
+#: ../../networking/multiple_guest_networks.rst:168
+msgid "Changing the Network Offering on a Guest Network"
+msgstr "在来宾网络上更改网络方案"
+
+# 9de4858c24814a74a54559f2494b3a89
+#: ../../networking/multiple_guest_networks.rst:170
+msgid ""
+"A user or administrator can change the network offering that is associated "
+"with an existing guest network."
+msgstr "用户或者管理员可以更改与之相关的来宾网络的网络方案。"
+
+# 7c551d2e95a241b48be8ce6603506ab3
+#: ../../networking/multiple_guest_networks.rst:175
+msgid ""
+"If you are changing from a network offering that uses the CloudStack virtual"
+" router to one that uses external devices as network service providers, you "
+"must first stop all the VMs on the network."
+msgstr "如果你将使用CloudStack虚拟路由的一个网络方案改成使用公共网络设备作为网络服务商，那么你必须先关掉该网络中的所有虚机。"
+
+# c67df95acd7f48b18f620634af845488
+#: ../../networking/multiple_guest_networks.rst:181
+msgid "Click the name of the network you want to modify."
+msgstr "点击你要修改的网络名称。"
+
+# fb679c3a524c4c4a837fe24566e3a12b
+#: ../../networking/multiple_guest_networks.rst:183
+msgid "In the Details tab, click Edit. |edit-icon.png|"
+msgstr "在 详细 页签，点击 编辑按钮。|edit-icon.png|"
+
+# 4afa43a2ac5b46f29ad42d421235b01d
+#: ../../networking/multiple_guest_networks.rst:185
+msgid ""
+"In Network Offering, choose the new network offering, then click Apply."
+msgstr "在网络方案中，选择新的网络方案，然后点击应用。"
+
+# 6a7280bbaba74bfb8b6622ac7832cf5c
+#: ../../networking/multiple_guest_networks.rst:188
+msgid ""
+"A prompt is displayed asking whether you want to keep the existing CIDR. "
+"This is to let you know that if you change the network offering, the CIDR "
+"will be affected."
+msgstr "这时会有一个提示问你是否保持已存在的CIDR不变。这是让你了解如果你改变网络了方案，那么CIDR会受到影响。"
+
+# 42e2f2150b07464bbdf35bc0c30edd91
+#: ../../networking/multiple_guest_networks.rst:192
+msgid ""
+"If you upgrade between virtual router as a provider and an external network "
+"device as provider, acknowledge the change of CIDR to continue, so choose "
+"Yes."
+msgstr "如果你将虚拟路由升级到外网设备，在看到变更CIDR以继续时，请选择Yes。"
+
+# 3b240e38bc11456095069b1622cc917f
+#: ../../networking/multiple_guest_networks.rst:196
+msgid ""
+"Wait for the update to complete. Don't try to restart VMs until the network "
+"change is complete."
+msgstr "等待更新完成。在网络变更完成之前不要试图重启虚拟机。"
+
+# a6db1505b17b48e1ae1063872635e2bb
+#: ../../networking/multiple_guest_networks.rst:199
+msgid "If you stopped any VMs, restart them."
+msgstr "如果你停止了任何VMs，请重启他们。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_ip_ranges.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_ip_ranges.mo
new file mode 100644
index 0000000..81f9e91
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_ip_ranges.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_ip_ranges.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_ip_ranges.po
new file mode 100644
index 0000000..a6a0a68
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_ip_ranges.po
@@ -0,0 +1,65 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# cea4bcb571304273bc04b67f139f0140
+#: ../../networking/multiple_ip_ranges.rst:18
+msgid "About Multiple IP Ranges"
+msgstr "关于多IP范围"
+
+# fb1aec1297a645198cd0ecbc09f187eb
+#: ../../networking/multiple_ip_ranges.rst:20
+msgid "The feature can only be implemented on IPv4 addresses."
+msgstr "这些功能仅能在IPV4的地址是实现。"
+
+# 3180ea2f13aa4565a8715d959ef1148d
+#: ../../networking/multiple_ip_ranges.rst:22
+msgid ""
+"CloudStack provides you with the flexibility to add guest IP ranges from "
+"different subnets in Basic zones and security groups-enabled Advanced zones."
+" For security groups-enabled Advanced zones, it implies multiple subnets can"
+" be added to the same VLAN. With the addition of this feature, you will be "
+"able to add IP address ranges from the same subnet or from a different one "
+"when IP address are exhausted. This would in turn allows you to employ "
+"higher number of subnets and thus reduce the address management overhead. To"
+" support this feature, the capability of ``createVlanIpRange`` API is "
+"extended to add IP ranges also from a different subnet."
+msgstr "在基础区域以及高级区域的开启安全组，CloudStack能够让你从不同的子网添加来宾IP范围。对于高级区域的开启安全组，多个子网可被加至同一个VLAN。随着此功能的增加，当IP地址耗尽时，你能够从同一个子网或从不同的子网添加IP范围。这会允许你添加更多的子网，因此减少了了地址管理的问题。为支持这一特性，创建VLANIP范围的API被加以扩展，这样就能从不同的子网添加IP范围"
+
+# d1d9636b0fd14b508f2570b3d7f5b7a2
+#: ../../networking/multiple_ip_ranges.rst:33
+msgid ""
+"Ensure that you manually configure the gateway of the new subnet before "
+"adding the IP range. Note that CloudStack supports only one gateway for a "
+"subnet; overlapping subnets are not currently supported."
+msgstr "确实在添加IP范围前，手动配置了子网的网关。注意，CloudStack仅支持一个子网有一个网关。不支持重叠的子网。"
+
+# b1ed3bd81dfa4662bcf9ab17817d99e5
+#: ../../networking/multiple_ip_ranges.rst:37
+msgid ""
+"Use the ``deleteVlanRange`` API to delete IP ranges. This operation fails if"
+" an IP from the remove range is in use. If the remove range contains the IP "
+"address on which the DHCP server is running, CloudStack acquires a new IP "
+"from the same subnet. If no IP is available in the subnet, the remove "
+"operation fails."
+msgstr "使用删除VLAN范围的API删除IP范围。如果拟删除的IP在被使用时，此操作会失败。如果删除的范围包含DHCP服务器拟分配的IP地址CloudStack会从同一个子网下获取新的IP。如果在子网内没有可供利用的IP时，删除操作会失败。"
+
+# 5c66e6ebd5cc42728bccf16a99764a94
+#: ../../networking/multiple_ip_ranges.rst:43
+msgid "This feature is supported on KVM, xenServer, and VMware hypervisors."
+msgstr "在KVM, xenServer以及VMware虚拟机中，都支持这项功能。 "
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_ips_on_single_nic.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_ips_on_single_nic.mo
new file mode 100644
index 0000000..6780d82
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_ips_on_single_nic.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_ips_on_single_nic.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_ips_on_single_nic.po
new file mode 100644
index 0000000..ca4693f
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_ips_on_single_nic.po
@@ -0,0 +1,165 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 80e46ffc92914befa1e1b6bb37ae48e0
+#: ../../networking/multiple_ips_on_single_nic.rst:18
+msgid "Configuring Multiple IP Addresses on a Single NIC"
+msgstr "在单网卡配置多个IP地址"
+
+# e552e4b860e64b83bd63e053002d0187
+#: ../../networking/multiple_ips_on_single_nic.rst:20
+msgid ""
+"CloudStack provides you the ability to associate multiple private IP "
+"addresses per guest VM NIC. In addition to the primary IP, you can assign "
+"additional IPs to the guest VM NIC. This feature is supported on all the "
+"network configurations: Basic, Advanced, and VPC. Security Groups, Static "
+"NAT and Port forwarding services are supported on these additional IPs."
+msgstr "CloudStack能够让你给每个客户虚拟机网卡配置多个私有IP地址，除主IP地址外，你可以指定额外的IP地址到客户虚拟机网卡。在所有的网络配置中，如基础配置，高级配置，VPC，均支持这一功能。安全组，静态NAT及端口转发服务在额外的IP地址上也都被支持。"
+
+# 37ec7f1162de4309afcd34ea7bc9af66
+#: ../../networking/multiple_ips_on_single_nic.rst:27
+msgid ""
+"As always, you can specify an IP from the guest subnet; if not specified, an"
+" IP is automatically picked up from the guest VM subnet. You can view the "
+"IPs associated with for each guest VM NICs on the UI. You can apply NAT on "
+"these additional guest IPs by using network configuration option in the "
+"CloudStack UI. You must specify the NIC to which the IP should be "
+"associated."
+msgstr "当然，你也可以从来宾子网中指定一个IP，如果没有指定，将会从来宾虚拟机子网中自动选择一个。可以从UI中查看每一个与来宾虚拟机网卡关联的IP地址。也可以在CloudStack界面中通过网络配置选项在那些额外的来宾虚拟机上应用NAT。但必须指明网卡与哪一个IP关联。"
+
+# 9a035e888c1245098bf6a6b97754c398
+#: ../../networking/multiple_ips_on_single_nic.rst:34
+msgid ""
+"This feature is supported on XenServer, KVM, and VMware hypervisors. Note "
+"that Basic zone security groups are not supported on VMware."
+msgstr "在XenServer，KVM和VMware虚拟机中，都支持这些功能。注意，VMware不支持基础区域的安全组。"
+
+# e65e3e62dc4a4301b7c488f06bbe696d
+#: ../../networking/multiple_ips_on_single_nic.rst:39
+msgid "Use Cases"
+msgstr "使用案例"
+
+# 11ad1c7201dd4368b51c2686f4f6c436
+#: ../../networking/multiple_ips_on_single_nic.rst:41
+msgid "Some of the use cases are described below:"
+msgstr "一些使用案例见以下描述"
+
+# bad26d93f70a454ea65fe8d314c5fb5f
+#: ../../networking/multiple_ips_on_single_nic.rst:43
+msgid ""
+"Network devices, such as firewalls and load balancers, generally work best "
+"when they have access to multiple IP addresses on the network interface."
+msgstr "网络设备，如防火墙或负责均衡设备，一般来讲，当他们在网络接口上接入更多的IP地址时，他们能够更好的工作。"
+
+# 95be93b5a22541cf8e3a65154ae683cc
+#: ../../networking/multiple_ips_on_single_nic.rst:47
+msgid ""
+"Moving private IP addresses between interfaces or instances. Applications "
+"that are bound to specific IP addresses can be moved between instances."
+msgstr "在接口和实例中迁移IP地址。绑定到特定IP地址的应用可以在实例中迁移。"
+
+# 9ee757e7b88f4aa2a87ccd4771a324d2
+#: ../../networking/multiple_ips_on_single_nic.rst:51
+msgid ""
+"Hosting multiple SSL Websites on a single instance. You can install multiple"
+" SSL certificates on a single instance, each associated with a distinct IP "
+"address."
+msgstr "在单个实例上开启多个SSL网站。可以在单个实例上安装多个SSL认证，每一个认证都关联一个单独的IP地址。"
+
+# 4edd1f589e2e49829a8738af942f1449
+#: ../../networking/multiple_ips_on_single_nic.rst:57
+msgid "Guidelines"
+msgstr "指南"
+
+# 54a52619c6484653a0d95be689657a85
+#: ../../networking/multiple_ips_on_single_nic.rst:59
+msgid ""
+"To prevent IP conflict, configure different subnets when multiple networks "
+"are connected to the same VM."
+msgstr "为防止IP冲突，当多个网络连接至同一个虚拟机时，要配置不同的子网。"
+
+# 2e55027ec0ce4ce6b87130453ca2ea69
+#: ../../networking/multiple_ips_on_single_nic.rst:64
+msgid "Assigning Additional IPs to a VM"
+msgstr "指定额外的IP给虚拟机"
+
+# 24aaa9f9fd734b1d9b775ad1342d31b2
+#: ../../networking/multiple_ips_on_single_nic.rst:66
+msgid "Log in to the CloudStack UI."
+msgstr "登录到CloudStack的界面"
+
+# 51fd921471ee488bb728f102e439c19e
+#: ../../networking/multiple_ips_on_single_nic.rst:68
+msgid "In the left navigation bar, click Instances."
+msgstr "在左侧导航栏，点击实例"
+
+# f0efc1c51c2a471498620eb3d6313aa6
+#: ../../networking/multiple_ips_on_single_nic.rst:70
+msgid "Click the name of the instance you want to work with."
+msgstr "点击拟配置的实例"
+
+# 17a62e09249f4a3fac5b78b1ee42aa11
+#: ../../networking/multiple_ips_on_single_nic.rst:72
+msgid "In the Details tab, click NICs."
+msgstr "在详细 页签，点击网卡"
+
+# 815af55e9e6e475ea2139c0ee79838c8
+#: ../../networking/multiple_ips_on_single_nic.rst:74
+msgid "Click View Secondary IPs."
+msgstr "点击查看二级地址"
+
+# edd4eb38ff964d91901201733864317e
+#: ../../networking/multiple_ips_on_single_nic.rst:76
+msgid ""
+"Click Acquire New Secondary IP, and click Yes in the confirmation dialog."
+msgstr "点击获取新二级IP，在确认对话框点击确定。"
+
+# a243effbef704447bf0f0a2d5bdc0a86
+#: ../../networking/multiple_ips_on_single_nic.rst:79
+msgid ""
+"You need to configure the IP on the guest VM NIC manually. CloudStack will "
+"not automatically configure the acquired IP address on the VM. Ensure that "
+"the IP address configuration persist on VM reboot."
+msgstr "需要手动配置来宾虚拟机的网卡。在虚拟机上，CloudStack不会自动配置获取IP。确保在虚拟机重启IP地址配置仍有效。"
+
+# 92b50e481e5943af8db0036e562bcf45
+#: ../../networking/multiple_ips_on_single_nic.rst:83
+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 StaticNAT "
+"rules."
+msgstr "稍等一会，新的IP地址会出现，状态栏为会显示为分配。现在可以在端口转发或静态NAT规则中使用此IP地址了。"
+
+# 8ce45ae597644592be9f68b1b9a50693
+#: ../../networking/multiple_ips_on_single_nic.rst:89
+msgid "Port Forwarding and StaticNAT Services Changes"
+msgstr "更改端口转发和静态NAT服务"
+
+# 707c305e2e104709866aebe9741b3891
+#: ../../networking/multiple_ips_on_single_nic.rst:91
+msgid ""
+"Because multiple IPs can be associated per NIC, you are allowed to select a "
+"desired IP for the Port Forwarding and StaticNAT services. The default is "
+"the primary IP. To enable this functionality, an extra optional parameter "
+"'vmguestip' is added to the Port forwarding and StaticNAT APIs "
+"(enableStaticNat, createIpForwardingRule) to indicate on what IP address NAT"
+" need to be configured. If vmguestip is passed, NAT is configured on the "
+"specified private IP of the VM. if not passed, NAT is configured on the "
+"primary IP of the VM."
+msgstr "因为每一个网卡都可关联至多IP，CloudStack可以允许为端口转发及静态NAT服务选择一个目标IP。默认为主IP。为开启此功能，另一个可选的配置参数 虚拟机来宾IP 需要被加至端口转发及静态NAT 的API中去（开启静态NAT，创建IP端口转发），以示IP地址NAT需要配置。如果虚拟机来宾IP 没有设置，NAT会配置在虚拟机的私有IP上，如果设置了，NAT会配置在虚拟机的主IP上。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_subnets_in_shared_network.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_subnets_in_shared_network.mo
new file mode 100644
index 0000000..11dc294
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_subnets_in_shared_network.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_subnets_in_shared_network.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_subnets_in_shared_network.po
new file mode 100644
index 0000000..f919ffc
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/multiple_subnets_in_shared_network.po
@@ -0,0 +1,180 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# aaae14dc309846cf90268bd429550032
+#: ../../networking/multiple_subnets_in_shared_network.rst:18
+msgid "Multiple Subnets in Shared Network"
+msgstr "共享网络中的多子网"
+
+# e1e0546c06b44b948781bf1b155376b6
+#: ../../networking/multiple_subnets_in_shared_network.rst:20
+msgid ""
+"CloudStack provides you with the flexibility to add guest IP ranges from "
+"different subnets in Basic zones and security groups-enabled Advanced zones."
+" For security groups-enabled Advanced zones, it implies multiple subnets can"
+" be added to the same VLAN. With the addition of this feature, you will be "
+"able to add IP address ranges from the same subnet or from a different one "
+"when IP address are exhausted. This would in turn allows you to employ "
+"higher number of subnets and thus reduce the address management overhead. "
+"You can delete the IP ranges you have added."
+msgstr "CloudStack为你提供了在基本zones和启用了安全组的高级zones不同的子网中灵活的添加来宾IP段功能 。在启用了安全组的高级zones中，这意味着多子网可以被添加到同一个VLAN。这个特性还意味着，当IP地址用尽的时候，你可以从同一个子网或从不同的子网添加IP地址范围。这将允许你使用更多的子网，降低地址管理工作量。你也可以删除已经添加的IP地址范围。"
+
+# d651b6e4b73a4c8897943f492f553be4
+#: ../../networking/multiple_subnets_in_shared_network.rst:32
+msgid "Prerequisites and Guidelines"
+msgstr "先决条件和指南"
+
+# 321b92f77c9e47b581323b300949d477
+#: ../../networking/multiple_subnets_in_shared_network.rst:34
+msgid "This feature can only be implemented:"
+msgstr "这个特性只能被实现在："
+
+# 693a867b887b40c39f9112ee79a514f3
+#: ../../networking/multiple_subnets_in_shared_network.rst:36
+msgid "on IPv4 addresses"
+msgstr "IPv4地址"
+
+# d4bb9088f4ce439bb4aa86f2d6ca1226
+#: ../../networking/multiple_subnets_in_shared_network.rst:38
+msgid "if virtual router is the DHCP provider"
+msgstr "如果虚拟路由是由DHCP提供的"
+
+# b4bb01b3421b4a26af052b41ef2e9c74
+#: ../../networking/multiple_subnets_in_shared_network.rst:40
+msgid "on KVM, xenServer, and VMware hypervisors"
+msgstr "在KVM，XenServer和VMware hypervisors"
+
+# 3ce0b6127bed4c878204268e02519b5f
+#: ../../networking/multiple_subnets_in_shared_network.rst:42
+msgid ""
+"Manually configure the gateway of the new subnet before adding the IP range."
+msgstr "在添加IP范围之前，手动配置新子网的网关。"
+
+# 92e9da161e084fd09cbd7a34e3a8ea59
+#: ../../networking/multiple_subnets_in_shared_network.rst:45
+msgid ""
+"CloudStack supports only one gateway for a subnet; overlapping subnets are "
+"not currently supported"
+msgstr "CloudStack只支持一个子网对应一个网关；交叉子网目前不支持。"
+
+# 0ccc8eb511c649519820d407c101fb3f
+#: ../../networking/multiple_subnets_in_shared_network.rst:50
+msgid "Adding Multiple Subnets to a Shared Network"
+msgstr "给共享网络添加多子网"
+
+# 402388a40d1c4432adf97dcb94bc7e0a
+#: ../../networking/multiple_subnets_in_shared_network.rst:52
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# c062e6ebc0b74be185c8e192c237a3d8
+#: ../../networking/multiple_subnets_in_shared_network.rst:54
+msgid "In the left navigation, choose Infrastructure."
+msgstr "在左边的导航，选择基础架构。"
+
+# 9d6f09662ceb452bb8bf26c21696a7ff
+#: ../../networking/multiple_subnets_in_shared_network.rst:56
+msgid ""
+"On Zones, click View More, then click the zone to which you want to work "
+"with.."
+msgstr "在Zones上，点击查看更多，然后点击你要进行操作的zone.."
+
+# 9a6c131e8dee4829a34a534324f96d6a
+#: ../../networking/multiple_subnets_in_shared_network.rst:59
+msgid "Click Physical Network."
+msgstr "点击物理网络。"
+
+# 412cf2ea6b7c4fc9a45dcfabca044210
+#: ../../networking/multiple_subnets_in_shared_network.rst:61
+msgid "In the Guest node of the diagram, click Configure."
+msgstr "在图中的来宾节点上，点击配置"
+
+# 20271a4db3304ebd986eefb0dbe2304b
+#: ../../networking/multiple_subnets_in_shared_network.rst:63
+msgid "Click Networks."
+msgstr "点击网络。"
+
+# d4d67c51b96a441984f094dad7440b53
+#: ../../networking/multiple_subnets_in_shared_network.rst:65
+msgid "Select the networks you want to work with."
+msgstr "选择你想要操作的网络。"
+
+# dbda223b46514614bc24a96cbd967579
+#: ../../networking/multiple_subnets_in_shared_network.rst:67
+msgid "Click View IP Ranges."
+msgstr "点击查看IP范围。"
+
+# fd40e95e0dcc4b37ac83ea1764ccd1c5
+#: ../../networking/multiple_subnets_in_shared_network.rst:69
+msgid "Click Add IP Range."
+msgstr "点击添加IP范围。"
+
+# e57818339fdd4bea80a587551ff3bb27
+#: ../../networking/multiple_subnets_in_shared_network.rst:71
+msgid "The Add IP Range dialog is displayed, as follows:"
+msgstr "显示的添加IP范围对话框如下："
+
+# 1adf38c68dd04551aeded2194d8d3bfb
+#: ../../networking/multiple_subnets_in_shared_network.rst:73
+msgid "|add-ip-range.png|"
+msgstr "|add-ip-range.png|"
+
+# 8d5c0e4efe1742f7988a60fe55223d66
+#: ../../networking/multiple_subnets_in_shared_network.rst:75
+msgid "Specify the following:"
+msgstr "指定以下信息："
+
+# c5bd70e2ab5748e18b8bc2840088a41e
+#: ../../networking/multiple_subnets_in_shared_network.rst:77
+msgid "All the fields are mandatory."
+msgstr "所有的区域必须填写的。"
+
+# cefcd378eaf44ae5b0c6aaa2809a4fe4
+#: ../../networking/multiple_subnets_in_shared_network.rst:79
+msgid ""
+"**Gateway**: The gateway for the tier you create. Ensure that the gateway is"
+" within the Super CIDR range that you specified while creating the VPC, and "
+"is not overlapped with the CIDR of any existing tier within the VPC."
+msgstr "**网关**：你创建网络层的网关。确保网关在你创建VPC时指定的超级CIDR范围内，并且不能与已存在VPC的任何网络层的CIDR重叠。"
+
+# d63b707e5f374d5d807b5749f9cc44ad
+#: ../../networking/multiple_subnets_in_shared_network.rst:84
+msgid "**Netmask**: The netmask for the tier you create."
+msgstr "**子网掩码**：你创建的网络层的子网掩码。"
+
+# f5d499f2a9fa4a859f8563d9b68b29a3
+#: ../../networking/multiple_subnets_in_shared_network.rst:86
+msgid ""
+"For example, if the VPC CIDR is 10.0.0.0/16 and the network tier CIDR is "
+"10.0.1.0/24, the gateway of the tier is 10.0.1.1, and the netmask of the "
+"tier is 255.255.255.0."
+msgstr "比如，如果VPC CIDR是10.0.0.0/16并且该网络层CIDR是10.0.1.0/24，那么这个网络层的网关是10.0.1.1，子网掩码是255.255.255.0."
+
+# 4aeabf0b77244ea994e1c9a3587421a7
+#: ../../networking/multiple_subnets_in_shared_network.rst:90
+msgid ""
+"**Start IP/ End IP**: A range of IP addresses that are accessible from the "
+"Internet and will be allocated to guest VMs. Enter the first and last IP "
+"addresses that define a range that CloudStack can assign to guest VMs ."
+msgstr "**起始/结束IP**：从互联网获得的和将被分配给来宾VMsIP地址范围。输入第一个和最后一个IP地址，该地址范围定义的是CloudStack能分配给来宾VMs的范围。"
+
+# c54dd19ac3fc4b1abe5c8e2ba6021969
+#: ../../networking/multiple_subnets_in_shared_network.rst:95
+msgid "Click OK."
+msgstr "点击确定。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/networking_in_pod.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/networking_in_pod.mo
new file mode 100644
index 0000000..b49b2f5
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/networking_in_pod.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/networking_in_pod.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/networking_in_pod.po
new file mode 100644
index 0000000..067e7e1
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/networking_in_pod.po
@@ -0,0 +1,70 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 3d0c16ad63444261b9694623c2402727
+#: ../../networking/networking_in_pod.rst:18
+msgid "Networking in a Pod"
+msgstr "一个提供点里的网络"
+
+# 6f94486d31ee45b8a15da0d2a1c080ca
+#: ../../networking/networking_in_pod.rst:20
+msgid ""
+"The figure below illustrates network setup within a single pod. The hosts "
+"are connected to a pod-level switch. At a minimum, the hosts should have one"
+" physical uplink to each switch. Bonded NICs are supported as well. The pod-"
+"level switch is a pair of redundant gigabit switches with 10 G uplinks."
+msgstr "下图演示了一个单提供点的网络配置。主机均连接到提供点层级的交换机。每一个主机至少有一个物理网卡连接到交换机。当然，这种环境也支持网卡绑定。提供点层级的交换机由两个1000M冗余组成，它们通过10G线路上联。"
+
+# d14ee305eeed479b95127d50242ce7f9
+#: ../../networking/networking_in_pod.rst:26
+msgid "|networksinglepod.png|"
+msgstr "|networksinglepod.png|"
+
+# 6c63d1a963fe4751bb6a3efcc28ec07b
+#: ../../networking/networking_in_pod.rst:28
+msgid "Servers are connected as follows:"
+msgstr "服务器以如下形式连接："
+
+# cab4d0a9b3874148b142ec81b8916ab3
+#: ../../networking/networking_in_pod.rst:30
+msgid ""
+"Storage devices are connected to only the network that carries management "
+"traffic."
+msgstr "存储设备只与管理网络连接。"
+
+# a01f83aa00be44768e404b928746539d
+#: ../../networking/networking_in_pod.rst:33
+msgid ""
+"Hosts are connected to networks for both management traffic and public "
+"traffic."
+msgstr "主机同时与管理网络和公共网络连接。"
+
+# 7cc32b192f154001a6b37b93bf141c79
+#: ../../networking/networking_in_pod.rst:36
+msgid ""
+"Hosts are also connected to one or more networks carrying guest traffic."
+msgstr "主机也与一个或多个来宾网络连接。"
+
+# afe45e02d11f436b92bc4752de309aa2
+#: ../../networking/networking_in_pod.rst:39
+msgid ""
+"We recommend the use of multiple physical Ethernet cards to implement each "
+"network interface as well as redundant switch fabric in order to maximize "
+"throughput and improve reliability."
+msgstr "我们推荐用多个物理网卡以改进性能，也推荐用冗余的光纤交换机以改进网络可靠性。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/networking_in_zone.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/networking_in_zone.mo
new file mode 100644
index 0000000..e2d984f
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/networking_in_zone.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/networking_in_zone.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/networking_in_zone.po
new file mode 100644
index 0000000..0637569
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/networking_in_zone.po
@@ -0,0 +1,50 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 3080bd3d63ce42f7970a7e111d5cc46b
+#: ../../networking/networking_in_zone.rst:18
+msgid "Networking in a Zone"
+msgstr "一个区域里的网络"
+
+# acc145c9dbbb43d0a4e7bcb5cdb804cb
+#: ../../networking/networking_in_zone.rst:20
+msgid ""
+"The following figure illustrates the network setup within a single zone."
+msgstr "下图说明了一个单一区域内的网络设置。"
+
+# a22b23e45435457b927cdcd248830e97
+#: ../../networking/networking_in_zone.rst:22
+msgid "|networksetupzone.png|"
+msgstr "|networksetupzone.png|"
+
+# 116d5e262cd547858fe9873be74c59da
+#: ../../networking/networking_in_zone.rst:24
+msgid ""
+"A firewall for management traffic operates in the NAT mode. The network "
+"typically is assigned IP addresses in the 192.168.0.0/16 Class B private "
+"address space. Each pod is assigned IP addresses in the 192.168.\\*.0/24 "
+"Class C private address space."
+msgstr "用于管理通信的防火墙工作在NAT模式。通常是分配给网络中的IP地址192.168.0.0/16 B类私有地址空间。每个机柜（POD）分配的IP地址是192.168.*.0/24 C类私有地址空间。"
+
+# 7a1eee0be4da4ed3aa3c0854ab4c2230
+#: ../../networking/networking_in_zone.rst:29
+msgid ""
+"Each zone has its own set of public IP addresses. Public IP addresses from "
+"different zones do not overlap."
+msgstr "每个区域都有自己的一套公网IP地址。来自不同区域的公网IP地址不重叠。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/palo_alto_config.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/palo_alto_config.mo
new file mode 100644
index 0000000..60e47c8
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/palo_alto_config.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/palo_alto_config.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/palo_alto_config.po
new file mode 100644
index 0000000..284a313
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/palo_alto_config.po
@@ -0,0 +1,932 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# f3d9b37c09d84940aa4c2fde3f9acd2a
+#: ../../networking/palo_alto_config.rst:18
+msgid "Setup a Palo Alto Networks Firewall"
+msgstr ""
+
+# bf6ec115893747b1baf4957e9be35ff4
+#: ../../networking/palo_alto_config.rst:22
+msgid "Functionality Provided"
+msgstr ""
+
+# c1f3ed83f8394089ab4694fe954e0195
+#: ../../networking/palo_alto_config.rst:24
+msgid ""
+"This implementation enables the orchestration of a Palo Alto Networks "
+"Firewall from within CloudStack UI and API."
+msgstr ""
+
+# 4b1340d4e6f74cd39095e06ca20ccbdd
+#: ../../networking/palo_alto_config.rst:27
+msgid "**The following features are supported**:"
+msgstr ""
+
+# e30f817e0e4d45ff8140a2bf41b86fb3
+#: ../../networking/palo_alto_config.rst:29
+msgid "List/Add/Delete Palo Alto Networks service provider"
+msgstr ""
+
+# d027f8c0521d4e3c8659c5f89b010dc3
+#: ../../networking/palo_alto_config.rst:31
+msgid "List/Add/Delete Palo Alto Networks network service offering"
+msgstr ""
+
+# d3c3bd36ca4744d68797f6bda8758efd
+#: ../../networking/palo_alto_config.rst:33
+msgid ""
+"List/Add/Delete Palo Alto Networks network using the above service offering"
+msgstr ""
+
+# d4ba1563cd1a4efb8039895bd0fc4abc
+#: ../../networking/palo_alto_config.rst:35
+msgid "Add an instance to a Palo Alto Networks network"
+msgstr ""
+
+# 095297003ef84ab4946859b93741650f
+#: ../../networking/palo_alto_config.rst:37
+msgid "Source NAT management on network create and delete"
+msgstr ""
+
+# 83be5169430e457495da1faa61028b94
+#: ../../networking/palo_alto_config.rst:39
+msgid "List/Add/Delete Ingress Firewall rule"
+msgstr ""
+
+# 934645096b2041c0892c5827ab0bae62
+#: ../../networking/palo_alto_config.rst:41
+msgid ""
+"List/Add/Delete Egress Firewall rule (both 'Allow' and 'Deny' default rules "
+"supported)"
+msgstr ""
+
+# b3d40e33e09544e892974a896c1c0f5e
+#: ../../networking/palo_alto_config.rst:44
+msgid "List/Add/Delete Port Forwarding rule"
+msgstr ""
+
+# 2227e25f9e3e4cf19e34dd0deddbb404
+#: ../../networking/palo_alto_config.rst:46
+msgid "List/Add/Delete Static NAT rule"
+msgstr ""
+
+# 64c598fbe2d04d368d5f30c35aa7f1d6
+#: ../../networking/palo_alto_config.rst:48
+msgid ""
+"Apply a Threat Profile to all firewall rules (more details in the Additional"
+" Features section)"
+msgstr ""
+
+# 6843739b321a4d828b6e9b17a9ef0fc8
+#: ../../networking/palo_alto_config.rst:51
+msgid ""
+"Apply a Log Forwarding profile to all firewall rules (more details in the "
+"Additional Features section)"
+msgstr ""
+
+# 90c46aad0abf4f3c9d84941828556629
+#: ../../networking/palo_alto_config.rst:57
+msgid "Initial Palo Alto Networks Firewall Configuration"
+msgstr ""
+
+# 3404e87b314644c49c28a53bc5f5e6a0
+#: ../../networking/palo_alto_config.rst:60
+msgid "Anatomy of the Palo Alto Networks Firewall"
+msgstr ""
+
+# a9c2ce1bfd05437a975c7cb37c0fba62
+#: ../../networking/palo_alto_config.rst:62
+msgid ""
+"In **'Network > Interfaces'** there is a list of physical interfaces as well"
+" as aggregated physical interfaces which are used for managing traffic in "
+"and out of the Palo Alto Networks Firewall device."
+msgstr ""
+
+# 5ac5b705b6834ded91c030380797cbd2
+#: ../../networking/palo_alto_config.rst:66
+msgid ""
+"In **'Network > Zones'** there is a list of the different configuration "
+"zones. This implementation will use two zones; a public (defaults to "
+"'untrust') and private (defaults to 'trust') zone."
+msgstr ""
+
+# eea4177c1fff4e099f0d3ed3d68ddfca
+#: ../../networking/palo_alto_config.rst:70
+msgid ""
+"In **'Network > Virtual Routers'** there is a list of VRs which handle "
+"traffic routing for the Palo Alto Firewall. We only use a single Virtual "
+"Router on the firewall and it is used to handle all the routing to the next "
+"network hop."
+msgstr ""
+
+# abd376e7380441f390cd90564d09d4c5
+#: ../../networking/palo_alto_config.rst:75
+msgid ""
+"In **'Objects > Security Profile Groups'** there is a list of profiles which"
+" can be applied to firewall rules. These profiles are used to better "
+"understand the types of traffic that is flowing through your network. "
+"Configured when you add the firewall provider to CloudStack."
+msgstr ""
+
+# 81bf3163d8e548f9827901650a45fa29
+#: ../../networking/palo_alto_config.rst:80
+msgid ""
+"In **'Objects > Log Forwarding'** there is a list of profiles which can be "
+"applied to firewall rules. These profiles are used to better track the logs"
+" generated by the firewall. Configured when you add the firewall provider "
+"to CloudStack."
+msgstr ""
+
+# 3f1feff617394987a3e0e75b9098bdb8
+#: ../../networking/palo_alto_config.rst:85
+msgid ""
+"In **'Policies > Security'** there is a list of firewall rules that are "
+"currently configured. You will not need to modify this section because it "
+"will be completely automated by CloudStack, but you can review the firewall "
+"rules which have been created here."
+msgstr ""
+
+# 34e8e7a02d1a478d99e352c6a4dd825c
+#: ../../networking/palo_alto_config.rst:90
+msgid ""
+"In **'Policies > NAT'** there is a list of the different NAT rules. You "
+"will not need to modify this section because it will be completely automated"
+" by CloudStack, but you can review the different NAT rules that have been "
+"created here. Source NAT, Static NAT and Destination NAT (Port Forwarding) "
+"rules will show up in this list."
+msgstr ""
+
+# 640e9e01bf184821b43d47005542f297
+#: ../../networking/palo_alto_config.rst:99
+msgid "Configure the Public / Private Zones on the firewall"
+msgstr ""
+
+# dd1583c5eff3465b96b6e0e55da67a78
+#: ../../networking/palo_alto_config.rst:101
+msgid ""
+"No manual configuration is required to setup these zones because CloudStack "
+"will configure them automatically when you add the Palo Alto Networks "
+"firewall device to CloudStack as a service provider. This implementation "
+"depends on two zones, one for the public side and one for the private side "
+"of the firewall."
+msgstr ""
+
+# f247dae111a8455598a5509325f99b2d
+#: ../../networking/palo_alto_config.rst:107
+msgid ""
+"The public zone (defaults to 'untrust') will contain all of the public "
+"interfaces and public IPs."
+msgstr ""
+
+# 3cc0d8d0cdd949bbae82f501193f7705
+#: ../../networking/palo_alto_config.rst:110
+msgid ""
+"The private zone (defaults to 'trust') will contain all of the private "
+"interfaces and guest network gateways."
+msgstr ""
+
+# fffcd92335be420f92a7847a249b200c
+#: ../../networking/palo_alto_config.rst:113
+msgid "The NAT and firewall rules will be configured between these zones."
+msgstr ""
+
+# 0f85059787c94c61b9cb4b39e5cb52c9
+#: ../../networking/palo_alto_config.rst:118
+msgid "Configure the Public / Private Interfaces on the firewall"
+msgstr ""
+
+# c8c72310b2744d4caefb5b9575ee6e60
+#: ../../networking/palo_alto_config.rst:120
+msgid ""
+"This implementation supports standard physical interfaces as well as grouped"
+" physical interfaces called aggregated interfaces. Both standard interfaces"
+" and aggregated interfaces are treated the same, so they can be used "
+"interchangeably. For this document, we will assume that we are using "
+"'ethernet1/1' as the public interface and 'ethernet1/2' as the private "
+"interface. If aggregated interfaces where used, you would use something "
+"like 'ae1' and 'ae2' as the interfaces."
+msgstr ""
+
+# 2831a742f496425ba96db130e37c9fdf
+#: ../../networking/palo_alto_config.rst:128
+msgid ""
+"This implementation requires that the 'Interface Type' be set to 'Layer3' "
+"for both the public and private interfaces. If you want to be able to use "
+"the 'Untagged' VLAN tag for public traffic in CloudStack, you will need to "
+"enable support for it in the public 'ethernet1/1' interface (details below)."
+msgstr ""
+
+# 7c752ebb778a47f5ab20ddd8e7c2c88d
+#: ../../networking/palo_alto_config.rst:133
+msgid "**Steps to configure the Public Interface**:"
+msgstr ""
+
+# 5700c7ece81b43cb98c6727c752735b2
+# e49c5cac5b754c67a068eb76b8f2b016
+# de7a1d67b1d944d9a9282e1481b27948
+#: ../../networking/palo_alto_config.rst:135
+#: ../../networking/palo_alto_config.rst:171
+#: ../../networking/palo_alto_config.rst:228
+msgid "Log into Palo Alto Networks Firewall"
+msgstr ""
+
+# 084f3f60d58341c1bb8a4c5902758909
+# ef024b35b5944a84b02459069f6213a1
+#: ../../networking/palo_alto_config.rst:137
+#: ../../networking/palo_alto_config.rst:230
+msgid "Navigate to 'Network > Interfaces'"
+msgstr ""
+
+# f9c2ae1f0de249878828ead2f5703582
+#: ../../networking/palo_alto_config.rst:139
+msgid ""
+"Click on 'ethernet1/1' (for aggregated ethernet, it will probably be called "
+"'ae1')"
+msgstr ""
+
+# 04a63a60ad414b7e81b979d479bae1fd
+# 04da4ad3a88d4e6cba3ee5b4668f9ee2
+#: ../../networking/palo_alto_config.rst:142
+#: ../../networking/palo_alto_config.rst:155
+msgid "Select 'Layer3' from the 'Interface Type' list"
+msgstr ""
+
+# ff872b1bbd2945db9cce189792e38246
+#: ../../networking/palo_alto_config.rst:144
+msgid "Click 'Advanced'"
+msgstr ""
+
+# 944d68b812d8463a87b69f9d882e8b28
+#: ../../networking/palo_alto_config.rst:146
+msgid "Check the 'Untagged Subinterface' check-box"
+msgstr ""
+
+# 290ce1b89ac441bcbc6691b3a41534a6
+# ac12e64f14884682ba033e7f2177cc9b
+# 8f94cc2074684065a79e57cf90d6ab9a
+# 8a83b222380740918936aca1feee32b9
+# f18ef2d3aeac41389cdfd198b83c5467
+# 95a5afc210324dab8a21ba2da8e6801c
+# d765a343c5f146639728c4ea3493e250
+# 8b7efac976c241fe9f3fa33963361d5a
+# 8a61018dde394d37b9ca3df99d188ee5
+#: ../../networking/palo_alto_config.rst:148
+#: ../../networking/palo_alto_config.rst:157
+#: ../../networking/palo_alto_config.rst:193
+#: ../../networking/palo_alto_config.rst:195
+#: ../../networking/palo_alto_config.rst:265
+#: ../../networking/palo_alto_config.rst:339
+#: ../../networking/palo_alto_config.rst:388
+#: ../../networking/palo_alto_config.rst:426
+#: ../../networking/palo_alto_config.rst:455
+msgid "Click 'OK'"
+msgstr ""
+
+# 8b5c88e0cc8242a580db731046cce5d3
+#: ../../networking/palo_alto_config.rst:150
+msgid "**Steps to configure the Private Interface**:"
+msgstr ""
+
+# a94612c3076e4722bd18904180a04114
+#: ../../networking/palo_alto_config.rst:152
+msgid ""
+"Click on 'ethernet1/2' (for aggregated ethernet, it will probably be called "
+"'ae2')"
+msgstr ""
+
+# 0beaed2fa39442e887eaca261cae62d7
+#: ../../networking/palo_alto_config.rst:162
+msgid "Configure a Virtual Router on the firewall"
+msgstr ""
+
+# 22d2fb39f9f44f928787ed03f4aa558c
+#: ../../networking/palo_alto_config.rst:164
+msgid ""
+"The Virtual Router on the Palo Alto Networks Firewall is not to be confused "
+"with the Virtual Routers that CloudStack provisions. For this "
+"implementation, the Virtual Router on the Palo Alto Networks Firewall will "
+"ONLY handle the upstream routing from the Firewall to the next hop."
+msgstr ""
+
+# e11103f99e6d45d0bea4183b1cf60c98
+#: ../../networking/palo_alto_config.rst:169
+msgid "**Steps to configure the Virtual Router**:"
+msgstr ""
+
+# d520996f46e84c8c94ce274dd654f3cb
+#: ../../networking/palo_alto_config.rst:173
+msgid "Navigate to 'Network > Virtual Routers'"
+msgstr ""
+
+# e966f3781b904686b55509eef9892346
+#: ../../networking/palo_alto_config.rst:175
+msgid ""
+"Select the 'default' Virtual Router or Add a new Virtual Router if there are"
+" none in the list"
+msgstr ""
+
+# 9cbe5a8debc5407fb6918d33d5b71aab
+#: ../../networking/palo_alto_config.rst:178
+msgid "If you added a new Virtual Router, you will need to give it a 'Name'"
+msgstr ""
+
+# b6a107e3fda3444fbcc24365b6ee33ca
+#: ../../networking/palo_alto_config.rst:180
+msgid "Navigate to 'Static Routes > IPv4'"
+msgstr ""
+
+# 6efcbc75fe144976b8a75a2dd888c615
+#: ../../networking/palo_alto_config.rst:182
+msgid "'Add' a new static route"
+msgstr ""
+
+# ed78234999764665912475eb992e6395
+#: ../../networking/palo_alto_config.rst:184
+msgid "**Name**: next_hop (you can name it anything you want)"
+msgstr ""
+
+# 47efb66b283043aa89a78ad4c6a87339
+#: ../../networking/palo_alto_config.rst:186
+msgid "**Destination**: 0.0.0.0/0 (send all traffic to this route)"
+msgstr ""
+
+# f9dde0e9e0534954bf1da5b6bf535824
+#: ../../networking/palo_alto_config.rst:188
+msgid ""
+"**Interface**: ethernet1/1 (or whatever you set your public interface as)"
+msgstr ""
+
+# 1e8a9818e50544a19445ee39589e5215
+#: ../../networking/palo_alto_config.rst:191
+msgid ""
+"**Next Hop**: (specify the gateway IP for the next hop in your network)"
+msgstr ""
+
+# f26446d9a67c4620a0f511145ecfde2b
+#: ../../networking/palo_alto_config.rst:200
+msgid "Configure the default Public Subinterface"
+msgstr ""
+
+# 7225aebfeb604bd7ad6ffa6bd19425c3
+#: ../../networking/palo_alto_config.rst:202
+msgid ""
+"The current implementation of the Palo Alto Networks firewall integration "
+"uses CIDRs in the form of 'w.x.y.z/32' for the public IP addresses that "
+"CloudStack provisions. Because no broadcast or gateway IPs are in this "
+"single IP range, there is no way for the firewall to route the traffic for "
+"these IPs. To route the traffic for these IPs, we create a single "
+"subinterface on the public interface with an IP and a CIDR which "
+"encapsulates the CloudStack public IP range. This IP will need to be inside"
+" the subnet defined by the CloudStack public range netmask, but outside the "
+"CloudStack public IP range. The CIDR should reflect the same subnet defined"
+" by the CloudStack public range netmask. The name of the subinterface is "
+"determined by the VLAN configured for the public range in CloudStack."
+msgstr ""
+
+# 3c781eec6bac4e599027b694351c3cd4
+#: ../../networking/palo_alto_config.rst:214
+msgid "To clarify this concept, we will use the following example."
+msgstr ""
+
+# 9637f4b7396f4c51983c5bf87b43e912
+#: ../../networking/palo_alto_config.rst:216
+msgid "**Example CloudStack Public Range Configuration**:"
+msgstr ""
+
+# 8a3070e081974ca68cc0375eca88007b
+#: ../../networking/palo_alto_config.rst:218
+msgid "**Gateway**: 172.30.0.1"
+msgstr ""
+
+# 9f64613849464823b633f1d16645d42e
+#: ../../networking/palo_alto_config.rst:220
+msgid "**Netmask**: 255.255.255.0"
+msgstr ""
+
+# 9330fe95cfaf44abbdb0d4f38e739dde
+#: ../../networking/palo_alto_config.rst:222
+msgid "**IP Range**: 172.30.0.100 - 172.30.0.199"
+msgstr ""
+
+# 435b6fb99438485f877a6756893298bf
+#: ../../networking/palo_alto_config.rst:224
+msgid "**VLAN**: Untagged"
+msgstr ""
+
+# eb956dfff226492fa1b0806cbbf743dc
+#: ../../networking/palo_alto_config.rst:226
+msgid "**Configure the Public Subinterface**:"
+msgstr ""
+
+# 2c3eb0c3c7e642cbb78583a57bc43be3
+#: ../../networking/palo_alto_config.rst:232
+msgid "Select the 'ethernet1/1' line (not clicking on the name)"
+msgstr ""
+
+# 739221cdf0024efc9b93b1d76646825b
+#: ../../networking/palo_alto_config.rst:234
+msgid "Click 'Add Subinterface' at the bottom of the window"
+msgstr ""
+
+# 6b8490f4a2684ca8ad9814a1461edaaa
+#: ../../networking/palo_alto_config.rst:236
+msgid "Enter 'Interface Name': 'ethernet1/1' . '9999'"
+msgstr ""
+
+# fb030c9c7b044a0185fe843def4a3bb5
+#: ../../networking/palo_alto_config.rst:238
+msgid "9999 is used if the CloudStack public range VLAN is 'Untagged'"
+msgstr ""
+
+# 912e1187e17b414f9493ddb7f368b068
+#: ../../networking/palo_alto_config.rst:240
+msgid ""
+"If the CloudStack public range VLAN is tagged (eg: 333), then the name will "
+"reflect that tag"
+msgstr ""
+
+# 4472ddfa3e6f4c878a16d411cc343a7d
+#: ../../networking/palo_alto_config.rst:243
+msgid ""
+"The 'Tag' is the VLAN tag that the traffic is sent to the next hop with, so "
+"set it accordingly. If you are passing 'Untagged' traffic from CloudStack "
+"to your next hop, leave it blank. If you want to pass tagged traffic from "
+"CloudStack, specify the tag."
+msgstr ""
+
+# f1ede2abd59c4fcc914acf233aa4b38c
+#: ../../networking/palo_alto_config.rst:248
+msgid ""
+"Select 'default' from the 'Config > Virtual Router' drop-down (assuming that"
+" is what your virtual router is called)"
+msgstr ""
+
+# 0d7f8743ae7e405c833390569c1a342c
+#: ../../networking/palo_alto_config.rst:251
+msgid "Click the 'IPv4' tab"
+msgstr ""
+
+# 93bc9ae7b5f346f99a40644725c2ebc0
+#: ../../networking/palo_alto_config.rst:253
+msgid "Select 'Static' from the 'Type' radio options"
+msgstr ""
+
+# 661bc9fb00f342d58bfd39624ff5f72a
+#: ../../networking/palo_alto_config.rst:255
+msgid "Click 'Add' in the 'IP' section"
+msgstr ""
+
+# b3482058794d4e2abb1e0a1f41bee8fa
+#: ../../networking/palo_alto_config.rst:257
+msgid "Enter '172.30.0.254/24' in the new line"
+msgstr ""
+
+# 02e03b2878504ed9a7ee888b36978cd4
+#: ../../networking/palo_alto_config.rst:259
+msgid ""
+"The IP can be any IP outside the CloudStack public IP range, but inside the "
+"CloudStack public range netmask (it can NOT be the gateway IP)"
+msgstr ""
+
+# 925fe2a4b10d4cb1ab438e2de318af0a
+#: ../../networking/palo_alto_config.rst:262
+msgid ""
+"The subnet defined by the CIDR should match the CloudStack public range "
+"netmask"
+msgstr ""
+
+# 10d6dd9ed3af49ffad4020de805389de
+#: ../../networking/palo_alto_config.rst:269
+msgid "Commit configuration on the Palo Alto Networks Firewall"
+msgstr ""
+
+# 89ac6f1b3c694a06b75008f8eec59b16
+#: ../../networking/palo_alto_config.rst:271
+msgid ""
+"In order for all the changes we just made to take effect, we need to commit "
+"the changes."
+msgstr ""
+
+# 3137cac6d6e14fc9904a5fa154e3905d
+#: ../../networking/palo_alto_config.rst:274
+msgid "Click the 'Commit' link in the top right corner of the window"
+msgstr ""
+
+# f3aaf9f819ef410fba6edbc621ea6a4d
+#: ../../networking/palo_alto_config.rst:276
+msgid "Click 'OK' in the commit window overlay"
+msgstr ""
+
+# 3b4acc9911434ddc83362cedcacab668
+#: ../../networking/palo_alto_config.rst:278
+msgid ""
+"Click 'Close' to the resulting commit status window after the commit "
+"finishes"
+msgstr ""
+
+# 6bb86113a96547538dbfd01db7c9e7ae
+#: ../../networking/palo_alto_config.rst:284
+msgid "Setup the Palo Alto Networks Firewall in CloudStack"
+msgstr ""
+
+# b8515e0d94ef4d4a865f64f7bef85482
+#: ../../networking/palo_alto_config.rst:287
+msgid "Add the Palo Alto Networks Firewall as a Service Provider"
+msgstr ""
+
+# 9b19a32893484d2fac28f3558f2643b5
+#: ../../networking/palo_alto_config.rst:289
+msgid ""
+"Navigate to 'Infrastructure > Zones > ZONE_NAME > Physical Network > "
+"NETWORK_NAME (guest) > Configure; Network Service Providers'"
+msgstr ""
+
+# 9bdf06473baa43cd9c6b8cb17a6313c3
+#: ../../networking/palo_alto_config.rst:292
+msgid "Click on 'Palo Alto' in the list"
+msgstr ""
+
+# 8565a2ab22994798a9167083879136f7
+#: ../../networking/palo_alto_config.rst:294
+msgid "Click 'View Devices'"
+msgstr ""
+
+# d10162d1e53c40e6bd448e05bb8a3259
+#: ../../networking/palo_alto_config.rst:296
+msgid "Click 'Add Palo Alto Device'"
+msgstr ""
+
+# c6fcd95bacbf4675951227d95a5737fc
+#: ../../networking/palo_alto_config.rst:298
+msgid ""
+"Enter your configuration in the overlay. This example will reflect the "
+"details previously used in this guide."
+msgstr ""
+
+# 1d34f716f84e4296a01fd3f7afde7356
+#: ../../networking/palo_alto_config.rst:301
+msgid "**IP Address**: (the IP of the Palo Alto Networks Firewall)"
+msgstr ""
+
+# add3b3461b6b48d7b74f94961a7b26e1
+#: ../../networking/palo_alto_config.rst:303
+msgid "**Username**: (the admin username for the firewall)"
+msgstr ""
+
+# 708228ac2edb498f9fd079d05a8a7511
+#: ../../networking/palo_alto_config.rst:305
+msgid "**Password**: (the admin password for the firewall)"
+msgstr ""
+
+# b2a6f266de904ebe94805b3176617484
+#: ../../networking/palo_alto_config.rst:307
+msgid "**Type**: Palo Alto Firewall"
+msgstr ""
+
+# 1cc218519592430f98cc8e009d0c8f2c
+#: ../../networking/palo_alto_config.rst:309
+msgid ""
+"**Public Interface**: ethernet1/1 (use what you setup earlier as the public "
+"interface if it is different from my examples)"
+msgstr ""
+
+# 5f1c1837d4df4e65a7a8abd05abd43ce
+#: ../../networking/palo_alto_config.rst:312
+msgid ""
+"**Private Interface**: ethernet1/2 (use what you setup earlier as the "
+"private interface if it is different from my examples)"
+msgstr ""
+
+# dd40b4143070449bb34ede04b3fe467e
+#: ../../networking/palo_alto_config.rst:315
+msgid "**Number of Retries**: 2 (the default is fine)"
+msgstr ""
+
+# 1d8080f41f894087b6e0a8c4c934dfe9
+#: ../../networking/palo_alto_config.rst:317
+msgid "**Timeout**: 300 (the default is fine)"
+msgstr ""
+
+# 876888b0168e496a897f306b246db971
+#: ../../networking/palo_alto_config.rst:319
+msgid ""
+"**Public Network**: untrust (this is the public zone on the firewall and did"
+" not need to be configured)"
+msgstr ""
+
+# 920274e528a341fb8962b73ff4b77179
+#: ../../networking/palo_alto_config.rst:322
+msgid ""
+"**Private Network**: trust (this is the private zone on the firewall and did"
+" not need to be configured)"
+msgstr ""
+
+# 2072277d3e14495aa762454838f72995
+#: ../../networking/palo_alto_config.rst:325
+msgid ""
+"**Virtual Router**: default (this is the name of the Virtual Router we setup"
+" on the firewall)"
+msgstr ""
+
+# 0376444c2cbd4404ad01b614aac5c07f
+#: ../../networking/palo_alto_config.rst:328
+msgid ""
+"**Palo Alto Threat Profile**: (not required. name of the 'Security Profile "
+"Groups' to apply. more details in the 'Additional Features' section)"
+msgstr ""
+
+# e649ac1802774500b5003c708987fe74
+#: ../../networking/palo_alto_config.rst:332
+msgid ""
+"**Palo Alto Log Profile**: (not required. name of the 'Log Forwarding' "
+"profile to apply. more details in the 'Additional Features' section)"
+msgstr ""
+
+# 32094fb7d72248d28b8f84e1fd56e988
+#: ../../networking/palo_alto_config.rst:335
+msgid "**Capacity**: (not required)"
+msgstr ""
+
+# 7e33721fb17a48e2ab7aa2d1b1dc460c
+#: ../../networking/palo_alto_config.rst:337
+msgid "**Dedicated**: (not required)"
+msgstr ""
+
+# dbef98d732fc4f7fbbad776d1b61f41e
+#: ../../networking/palo_alto_config.rst:341
+msgid "Click on 'Palo Alto' in the breadcrumbs to go back one screen."
+msgstr ""
+
+# e499e22a30754ab4acfd6a779b03ea97
+#: ../../networking/palo_alto_config.rst:343
+msgid "Click on 'Enable Provider' |EnableDisableFeature.png|"
+msgstr ""
+
+# b7b0fa1a4629430b839286b55162f882
+#: ../../networking/palo_alto_config.rst:347
+msgid "Add a Network Service Offering to use the new Provider"
+msgstr ""
+
+# 1cc4ca671df7479c96ab873e7ae0cc68
+#: ../../networking/palo_alto_config.rst:349
+msgid ""
+"There are 6 'Supported Services' that need to be configured in the network "
+"service offering for this functionality. They are DHCP, DNS, Firewall, "
+"Source NAT, Static NAT and Port Forwarding. For the other settings, there "
+"are probably additional configurations which will work, but I will just "
+"document a common case."
+msgstr ""
+
+# f406f98a91684fd1bd4947a0b06ed1a2
+#: ../../networking/palo_alto_config.rst:355
+msgid "Navigate to 'Service Offerings'"
+msgstr ""
+
+# 942ee3b426ba4d88acfbee186446dcaf
+#: ../../networking/palo_alto_config.rst:357
+msgid "In the drop-down at the top, select 'Network Offerings'"
+msgstr ""
+
+# 6d216de0290941758439b72593f8a6c8
+#: ../../networking/palo_alto_config.rst:359
+msgid "Click 'Add Network Offering'"
+msgstr ""
+
+# da673cd57e5d4dadaaa406cb5fa5ec13
+#: ../../networking/palo_alto_config.rst:361
+msgid "**Name**: (name it whatever you want)"
+msgstr ""
+
+# a59e3d821172494d9efb8de1253d352d
+#: ../../networking/palo_alto_config.rst:363
+msgid "**Description**: (again, can be whatever you want)"
+msgstr ""
+
+# bdb32fa4fdf545d2886707aa7ca1156d
+#: ../../networking/palo_alto_config.rst:365
+msgid "**Guest Type**: Isolated"
+msgstr ""
+
+# ee73168cca234bf08581ec3131ec5bb8
+#: ../../networking/palo_alto_config.rst:367
+msgid "**Supported Services**:"
+msgstr ""
+
+# 320e8c3f0b9b49ac8768926d267e94d7
+#: ../../networking/palo_alto_config.rst:369
+msgid "**DHCP**: Provided by 'VirtualRouter'"
+msgstr ""
+
+# 4c6b47d1b7b34586863177a90b865d85
+#: ../../networking/palo_alto_config.rst:371
+msgid "**DNS**: Provided by 'VirtualRouter'"
+msgstr ""
+
+# 56ac8260b8a3496ca38997dfc58dae3f
+#: ../../networking/palo_alto_config.rst:373
+msgid "**Firewall**: Provided by 'PaloAlto'"
+msgstr ""
+
+# fb63dd0553724890988f01e52cc9fb1a
+#: ../../networking/palo_alto_config.rst:375
+msgid "**Source NAT**: Provided by 'PaloAlto'"
+msgstr ""
+
+# 4cdf39f3041d47699f285f61fcf0ac95
+#: ../../networking/palo_alto_config.rst:377
+msgid "**Static NAT**: Provided by 'PaloAlto'"
+msgstr ""
+
+# bfbb888f85ab4e179965cac8c6d8dadb
+#: ../../networking/palo_alto_config.rst:379
+msgid "**Port Forwarding**: Provided by 'PaloAlto'"
+msgstr ""
+
+# 88e886aff4204f32811dff6e4d8ea019
+#: ../../networking/palo_alto_config.rst:381
+msgid "**System Offering for Router**: System Offering For Software Router"
+msgstr ""
+
+# 8f0e43a7d0f34b9992263fdfdcfcd2d6
+#: ../../networking/palo_alto_config.rst:383
+msgid ""
+"**Supported Source NAT Type**: Per account (this is the only supported "
+"option)"
+msgstr ""
+
+# e06e5423d74c4f328eae1e741028734b
+#: ../../networking/palo_alto_config.rst:386
+msgid "**Default egress policy**: (both 'Allow' and 'Deny' are supported)"
+msgstr ""
+
+# 59c525fe149a425098205f41b21a9cf1
+#: ../../networking/palo_alto_config.rst:390
+msgid "Click on the newly created service offering"
+msgstr ""
+
+# 44fc81442fe34d68a2728f0ca0a160dc
+#: ../../networking/palo_alto_config.rst:392
+msgid "Click 'Enable network offering' |EnableDisableFeature.png|"
+msgstr ""
+
+# 934d3259e9bf44c083323e6b2f2aa9bf
+#: ../../networking/palo_alto_config.rst:394
+msgid ""
+"When adding networks in CloudStack, select this network offering to use the "
+"Palo Alto Networks firewall."
+msgstr ""
+
+# fae8d19c649e479f99c6b2edd49434eb
+#: ../../networking/palo_alto_config.rst:399
+msgid "Additional Features"
+msgstr ""
+
+# 9dc0b83948d74e16b3ad351d1210f5b5
+#: ../../networking/palo_alto_config.rst:401
+msgid ""
+"In addition to the standard functionality exposed by CloudStack, we have "
+"added a couple additional features to this implementation. We did not add "
+"any new screens to CloudStack, but we have added a couple fields to the 'Add"
+" Palo Alto Service Provider' screen which will add functionality globally "
+"for the device."
+msgstr ""
+
+# 5af1e576fa7847f7b87eed5fe35e77b8
+#: ../../networking/palo_alto_config.rst:408
+msgid "Palo Alto Networks Threat Profile"
+msgstr ""
+
+# 9070542c237349599f645efcd8a64128
+#: ../../networking/palo_alto_config.rst:410
+msgid ""
+"This feature allows you to specify a 'Security Profile Group' to be applied "
+"to all of the firewall rules which are created on the Palo Alto Networks "
+"firewall device."
+msgstr ""
+
+# a4257973d0524640b7102968817ca7e5
+#: ../../networking/palo_alto_config.rst:414
+msgid ""
+"To create a 'Security Profile Group' on the Palo Alto Networks firewall, do "
+"the following:"
+msgstr ""
+
+# 77a31bab19cd4e55b4cc13c92cb328bb
+# 92409a68a6f345c89e059f0a26e707ee
+#: ../../networking/palo_alto_config.rst:417
+#: ../../networking/palo_alto_config.rst:446
+msgid "Log into the Palo Alto Networks firewall"
+msgstr ""
+
+# 2b0227f96b854d92bf96e91d9c17435c
+#: ../../networking/palo_alto_config.rst:419
+msgid "Navigate to 'Objects > Security Profile Groups'"
+msgstr ""
+
+# 2405f37aad834c34b4360f784ce6ec69
+#: ../../networking/palo_alto_config.rst:421
+msgid "Click 'Add' at the bottom of the page to add a new group"
+msgstr ""
+
+# 7e5ffff8c26545c48b07a4921ca76a52
+#: ../../networking/palo_alto_config.rst:423
+msgid ""
+"Give the group a Name and specify the profiles you would like to include in "
+"the group"
+msgstr ""
+
+# 3e3d4bfaa14c46c38499c68ce4f36095
+# 547b08aaaf164fb68c2b8f1b37d09793
+#: ../../networking/palo_alto_config.rst:428
+#: ../../networking/palo_alto_config.rst:457
+msgid ""
+"Click the 'Commit' link in the top right of the screen and follow the on "
+"screen instructions"
+msgstr ""
+
+# a31ebe4cd3bf4bf9b7e3fe8d35c32f63
+#: ../../networking/palo_alto_config.rst:431
+msgid ""
+"Once you have created a profile, you can reference it by Name in the 'Palo "
+"Alto Threat Profile' field in the 'Add the Palo Alto Networks Firewall as a "
+"Service Provider' step."
+msgstr ""
+
+# 735566ed2935434ea67f2e2595c3f686
+#: ../../networking/palo_alto_config.rst:437
+msgid "Palo Alto Networks Log Forwarding Profile"
+msgstr ""
+
+# c229e4bdb0c04fac952295035d8afa6b
+#: ../../networking/palo_alto_config.rst:439
+msgid ""
+"This feature allows you to specify a 'Log Forwarding' profile to better "
+"manage where the firewall logs are sent to. This is helpful for keeping "
+"track of issues that can arise on the firewall."
+msgstr ""
+
+# 461ea8be12674fcd842217cf72c68f7f
+#: ../../networking/palo_alto_config.rst:443
+msgid ""
+"To create a 'Log Forwarding' profile on the Palo Alto Networks Firewall, do "
+"the following:"
+msgstr ""
+
+# a61142f77e8941e9b976c01cd1aa9f89
+#: ../../networking/palo_alto_config.rst:448
+msgid "Navigate to 'Objects > Log Forwarding'"
+msgstr ""
+
+# ea14dff9d3c448f0976b6aebe2d119cc
+#: ../../networking/palo_alto_config.rst:450
+msgid "Click 'Add' at the bottom of the page to add a new profile"
+msgstr ""
+
+# 1352f9adcbd94a24a5429e2ed53caa48
+#: ../../networking/palo_alto_config.rst:452
+msgid ""
+"Give the profile a Name and specify the details you want for the traffic and"
+" threat settings"
+msgstr ""
+
+# 6b304cde8312467ebef3f110a46fce1a
+#: ../../networking/palo_alto_config.rst:460
+msgid ""
+"Once you have created a profile, you can reference it by Name in the 'Palo "
+"Alto Log Profile' field in the 'Add the Palo Alto Networks Firewall as a "
+"Service Provider' step."
+msgstr ""
+
+# 7ba0d11bde5b4c3e97de4830b0aecc15
+#: ../../networking/palo_alto_config.rst:467
+msgid "Limitations"
+msgstr "局限性"
+
+# 796314d492b54823a652a3f50d430629
+#: ../../networking/palo_alto_config.rst:469
+msgid ""
+"The implementation currently only supports a single public IP range in "
+"CloudStack"
+msgstr ""
+
+# c8e8545461454cb9acf0a06bf42b95c0
+#: ../../networking/palo_alto_config.rst:472
+msgid "Usage tracking is not yet implemented"
+msgstr ""
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/persistent_networks.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/persistent_networks.mo
new file mode 100644
index 0000000..37f083f
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/persistent_networks.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/persistent_networks.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/persistent_networks.po
new file mode 100644
index 0000000..89352a5
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/persistent_networks.po
@@ -0,0 +1,163 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 4083b4f8962d4ce2add5a637beceaf4d
+#: ../../networking/persistent_networks.rst:18
+msgid "Persistent Networks"
+msgstr "持久化网络"
+
+# 5157cfe530594f5f954a8a8e1525ce10
+#: ../../networking/persistent_networks.rst:20
+msgid ""
+"The network that you can provision without having to deploy any VMs on it is"
+" called a persistent network. A persistent network can be part of a VPC or a"
+" non-VPC environment."
+msgstr "在不部署任何VM的情况下就初始化好的网络称为持久化网络。持久化网络可以是VPC的一部分，也可以不是。"
+
+# 469fa7c5517f4f82b49e9015b0027b0f
+#: ../../networking/persistent_networks.rst:24
+msgid ""
+"When you create other types of network, a network is only a database entry "
+"until the first VM is created on that network. When the first VM is created,"
+" a VLAN ID is assigned and the network is provisioned. Also, when the last "
+"VM is destroyed, the VLAN ID is released and the network is no longer "
+"available. With the addition of persistent network, you will have the "
+"ability to create a network in CloudStack in which physical devices can be "
+"deployed without having to run any VMs. Additionally, you can deploy "
+"physical devices on that network."
+msgstr "在您创建其它类型的网络时，在网络中第一台VM创建之前，该网络仅是数据库的一条记录。当第一个VM创建时，网络会指定一个VLAN ID并初始化。同样，当网络中最后一个VM销毁后，VLAN ID会被释放，这样该网络就不再可用。通过使用持久化网络，您就有能力在不部署VM的情况下在&PRODUCT;中创建一个网络用来部署物理设备。而且，您可以在该网络中部署物理设备。"
+
+# 87f88f46858c41ba96f785b7c3122342
+#: ../../networking/persistent_networks.rst:33
+msgid ""
+"One of the advantages of having a persistent network is that you can create "
+"a VPC with a tier consisting of only physical devices. For example, you "
+"might create a VPC for a three-tier application, deploy VMs for Web and "
+"Application tier, and use physical machines for the Database tier. Another "
+"use case is that if you are providing services by using physical hardware, "
+"you can define the network as persistent and therefore even if all its VMs "
+"are destroyed the services will not be discontinued."
+msgstr "使用持久化网络的一个优点是您可以创建具有一个只包含物理设备的层的VPC。例如，您可以为一个三层应用创建一个VPC，在Web层和应用层部署VM，在数据库层使用物理机器。另一个使用场景为如果您使用物理硬件提供网络服务，您可以定义网络为持久化的。这样即便网络中所有VM都销毁了，服务还可以继续提供。"
+
+# 68622842a6474e23b5b4ace4928a7f02
+#: ../../networking/persistent_networks.rst:44
+msgid "Persistent Network Considerations"
+msgstr "持久化网络的考虑事项"
+
+# bd289a0ef0dc4ef1b5a6acb8b9ad0c38
+#: ../../networking/persistent_networks.rst:46
+msgid "Persistent network is designed for isolated networks."
+msgstr "Persistent网络是为隔离网络而设计的。"
+
+# 10b2b9266df84efcb8fb9002316e3f11
+#: ../../networking/persistent_networks.rst:48
+msgid "All default network offerings are non-persistent."
+msgstr "所有默认网络方案都不是持久化的。"
+
+# d9e8d354f6bc4b6f8194156ed112a537
+#: ../../networking/persistent_networks.rst:50
+msgid ""
+"A network offering cannot be editable because changing it affects the "
+"behavior of the existing networks that were created using this network "
+"offering."
+msgstr "网络方案的持久化选项不可编辑。因为修改该选项会影响使用该网络方案创建的已有网络的行为。"
+
+# 80b8615033b54141b06d3d7a311809bf
+#: ../../networking/persistent_networks.rst:54
+msgid ""
+"When you create a guest network, the network offering that you select "
+"defines the network persistence. This in turn depends on whether persistent "
+"network is enabled in the selected network offering."
+msgstr "当您创建客户网络时，您选择的网络方案定义了该网络的持久化。反过来，这依赖于选择的网络方案是否启用持久化网络。"
+
+# 5e5d6fc784af4dec8e15481000f5125f
+#: ../../networking/persistent_networks.rst:58
+msgid ""
+"An existing network can be made persistent by changing its network offering "
+"to an offering that has the Persistent option enabled. While setting this "
+"property, even if the network has no running VMs, the network is "
+"provisioned."
+msgstr "通过修改使用的网络方案为启用持久化的方案，现有网络可以变为持久化。在设置该属性时，即便网络中没有运行的VM，该网络也会初始化。"
+
+# 30e1aaa119a34adcb9a57e513d705745
+#: ../../networking/persistent_networks.rst:63
+msgid ""
+"An existing network can be made non-persistent by changing its network "
+"offering to an offering that has the Persistent option disabled. If the "
+"network has no running VMs, during the next network garbage collection run "
+"the network is shut down."
+msgstr "通过修改使用的网络方案为禁用持久化的方案，现有网络可以变为非持久化。如果网络中没有运行的VM，在下次网络垃圾回收运行时，该网络会被关闭。"
+
+# 1fafa4f8c2e8475e984703fe2e4c29ba
+#: ../../networking/persistent_networks.rst:68
+msgid ""
+"When the last VM on a network is destroyed, the network garbage collector "
+"checks if the network offering associated with the network is persistent, "
+"and shuts down the network only if it is non-persistent."
+msgstr "当网络中最后一台VM销毁时，网络垃圾回收器会检查该网络的网络方案是否为持久化，若不是持久化，则会关闭网络。"
+
+# 6302571eba5d408687957bd3759816c3
+#: ../../networking/persistent_networks.rst:75
+msgid "Creating a Persistent Guest Network"
+msgstr "创建一个Persistent客户网络"
+
+# c3876e9bd8d449b489101f5ac1bae458
+#: ../../networking/persistent_networks.rst:77
+msgid "To create a persistent network, perform the following:"
+msgstr "要创建一个Persistent网络，请按如下操作："
+
+# 99fe5f5c722844089e5bdbcdadb22fc0
+#: ../../networking/persistent_networks.rst:79
+msgid "Create a network offering with the Persistent option enabled."
+msgstr "创建一个Persistent选项启用的网络方案。"
+
+# 16d2470643ab4777a40f35f26a9de70c
+#: ../../networking/persistent_networks.rst:81
+msgid ""
+"See `\"Creating a New Network Offering\" <networking.html#creating-a-new-"
+"network-offering>`_."
+msgstr "请参考`\"创建一个新的网络方案\" <networking.html#creating-a-new-network-offering>`_."
+
+# 267c8937d18548498e620897ef0e587e
+#: ../../networking/persistent_networks.rst:84
+msgid "Select Network from the left navigation pane."
+msgstr "从左边的导航栏里选择网络。"
+
+# bc4568a29a4149c797c11839057e9538
+#: ../../networking/persistent_networks.rst:86
+msgid ""
+"Select the guest network that you want to offer this network service to."
+msgstr "选择你希望提供此网络方案服务的客户网络。"
+
+# ecdb6f1a35444f46acd9620f3305b060
+#: ../../networking/persistent_networks.rst:89
+msgid "Click the Edit button."
+msgstr "点击编辑按钮。"
+
+# 5bda22ffd010416cb80b2848179d18fa
+#: ../../networking/persistent_networks.rst:91
+msgid ""
+"From the Network Offering drop-down, select the persistent network offering "
+"you have just created."
+msgstr "在网络方案下拉列表里，选择你刚才创建的persistent网络方案。"
+
+# fd7fed942171405cb30c3ea00f4111cb
+#: ../../networking/persistent_networks.rst:94
+msgid "Click OK."
+msgstr "点击确定。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/portable_ips.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/portable_ips.mo
new file mode 100644
index 0000000..e09889b
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/portable_ips.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/portable_ips.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/portable_ips.po
new file mode 100644
index 0000000..33859a2
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/portable_ips.po
@@ -0,0 +1,233 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 0d718ef9845940f3b45f93fdedd55a80
+#: ../../networking/portable_ips.rst:18
+msgid "Portable IPs"
+msgstr "端口IP"
+
+# 7dbdc94b3c7148f3a67dd212137b1b78
+#: ../../networking/portable_ips.rst:21
+msgid "About Portable IP"
+msgstr "关于端口IP"
+
+# a4b9041cb1da4c7c9185978b3bd46328
+#: ../../networking/portable_ips.rst:23
+msgid ""
+"Portable IPs in CloudStack are region-level pool of IPs, which are elastic "
+"in nature, that can be transferred across geographically separated zones. As"
+" an administrator, you can provision a pool of portable public IPs at region"
+" level and are available for user consumption. The users can acquire "
+"portable IPs if admin has provisioned portable IPs at the region level they "
+"are part of. These IPs can be use for any service within an advanced zone. "
+"You can also use portable IPs for EIP services in basic zones."
+msgstr "在CloudStack中，端口IP是地域级的IP地址池，其天然具有弹性，亦即可以在地理隔离的区域中进行转发。作为管理员,可以在地域级提供IP地址池供用户使用。如果在用户所属的地域，其管理员提供了端口IP，用户就可以获取此类IP。在高级区域内，这些IP可用于任一服务。也可以在基础区域中为EIP服务使用端口IP。"
+
+# 824ded2676d34d4b8d60fd93b08f58c8
+#: ../../networking/portable_ips.rst:32
+msgid "The salient features of Portable IP are as follows:"
+msgstr "端口IP的主要功能如下："
+
+# 1f57b59fbbbd426b9b2fd6f4dffaa0d2
+#: ../../networking/portable_ips.rst:34
+msgid "IP is statically allocated"
+msgstr "IP是静态分配的。"
+
+# 1759d65d5ed34db283d80b85d56f486a
+#: ../../networking/portable_ips.rst:36
+msgid "IP need not be associated with a network"
+msgstr "IP与网络无关。"
+
+# 6826b76a9eea4332a6c068382f8b050c
+#: ../../networking/portable_ips.rst:38
+msgid "IP association is transferable across networks"
+msgstr "IP关联是可以通过网络转发的。"
+
+# ae7460bc9900474fbf94402165b9cb7e
+#: ../../networking/portable_ips.rst:40
+msgid "IP is transferable across both Basic and Advanced zones"
+msgstr "IP可以在基础区域和高级区域中转发。"
+
+# 770563314c044da6acca6641fce5f500
+#: ../../networking/portable_ips.rst:42
+msgid "IP is transferable across VPC, non-VPC isolated and shared networks"
+msgstr "IP可通过VPC，非VPC隔离和共享网络进行转发。"
+
+# ea55d3113555412f8f8a2bbf4f6b0846
+#: ../../networking/portable_ips.rst:44
+msgid "Portable IP transfer is available only for static NAT."
+msgstr "端口IP转发仅对静态NAT可用。"
+
+# 2ff5ef4c14bb4585a2e7c5c7458d25fe
+#: ../../networking/portable_ips.rst:48
+msgid "Guidelines"
+msgstr "指南"
+
+# 662d9610efd3460aae2192eea97c7bd6
+#: ../../networking/portable_ips.rst:50
+msgid ""
+"Before transferring to another network, ensure that no network rules "
+"(Firewall, Static NAT, Port Forwarding, and so on) exist on that portable "
+"IP."
+msgstr "在转发至另一网络前，确保没有网络规则（如防火墙，静态NAT，端口转发等等）不存在于端口IP。"
+
+# d276865047e64a7f9cdddb63ad28d313
+#: ../../networking/portable_ips.rst:56
+msgid "Configuring Portable IPs"
+msgstr "配置端口IP"
+
+# b085a9f5f2ce4744b86603f26196b283
+# a28f4db3b1734d3c9f0aa6cada34dab5
+#: ../../networking/portable_ips.rst:58 ../../networking/portable_ips.rst:90
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# 2f850a50ddab404d9df06aa0338d6479
+#: ../../networking/portable_ips.rst:60
+msgid "In the left navigation, click Regions."
+msgstr "在左侧导航栏中，点击地域"
+
+# 316a2bbd2c69469597356b663e5135ba
+#: ../../networking/portable_ips.rst:62
+msgid "Choose the Regions that you want to work with."
+msgstr "选择拟修改的地域。"
+
+# c66c2dfa7575447e82396eeff33e1315
+#: ../../networking/portable_ips.rst:64
+msgid "Click View Portable IP."
+msgstr "点击查看端口IP"
+
+# cd5798170b724d0abe4461ee8779eded
+#: ../../networking/portable_ips.rst:66
+msgid "Click Portable IP Range."
+msgstr "点击端口IP范围"
+
+# 09d0a8e2201a44acbe61f89c2ebdba6b
+#: ../../networking/portable_ips.rst:68
+msgid "The Add Portable IP Range window is displayed."
+msgstr "会出现 添加端口IP范围的窗口"
+
+# 9c9681bfaca543f09522720f86b05c3b
+#: ../../networking/portable_ips.rst:70
+msgid "Specify the following:"
+msgstr "指定以下信息："
+
+# 2832d8a453bf4a27a01dfbe6ade2c252
+#: ../../networking/portable_ips.rst:72
+msgid ""
+"**Start IP/ End IP**: A range of IP addresses that are accessible from the "
+"Internet and will be allocated to guest VMs. Enter the first and last IP "
+"addresses that define a range that CloudStack can assign to guest VMs."
+msgstr "**起始IP/结束IP**: 从Internet可以访问的一个IP地址范围，将会分配给客户虚拟机。输入起始IP以及结束IP，定义CloudStack指定给客户虚拟机的IP范围。"
+
+# ea589b30c39d429c86fd50fe49515dd7
+#: ../../networking/portable_ips.rst:77
+msgid ""
+"**Gateway**: The gateway in use for the Portable IP addresses you are "
+"configuring."
+msgstr "**网关**: 配置端口IP地址所使用的网关。"
+
+# 9d8360b75a254007b307c9ba1341550d
+#: ../../networking/portable_ips.rst:80
+msgid "**Netmask**: The netmask associated with the Portable IP range."
+msgstr "**掩码**: 与端口IP范围关联的掩码。"
+
+# 60ed534104ce48fdb9586f72c61b379f
+#: ../../networking/portable_ips.rst:82
+msgid "**VLAN**: The VLAN that will be used for public traffic."
+msgstr "**VLAN**: 公共流量拟使用的VLAN。"
+
+# 8615e1020e2747f0ba31cd4cb186a010
+#: ../../networking/portable_ips.rst:84
+msgid "Click OK."
+msgstr "点击确定。"
+
+# d88ec64c255243049a67ed2616530031
+#: ../../networking/portable_ips.rst:88
+msgid "Acquiring a Portable IP"
+msgstr "获取端口IP。"
+
+# b933b6d78fe94153a35b24d2ccfd8e06
+#: ../../networking/portable_ips.rst:92
+msgid "In the left navigation, choose Network."
+msgstr "在左侧的导航栏，选择网络。"
+
+# 2f46ac57574a4ff3833cd3af46386463
+#: ../../networking/portable_ips.rst:94
+msgid "Click the name of the network where you want to work with."
+msgstr "点击拟修改的网络名称。"
+
+# a7dc83315ae746af830094d45cfe7c11
+#: ../../networking/portable_ips.rst:96
+msgid "Click View IP Addresses."
+msgstr "点击查看IP地址。"
+
+# 64b8eac8ac21402293c2fff5d435a7eb
+#: ../../networking/portable_ips.rst:98
+msgid "Click Acquire New IP."
+msgstr "点击获取新IP。"
+
+# 4a739787a6194df09e032797d1fe0911
+#: ../../networking/portable_ips.rst:100
+msgid "The Acquire New IP window is displayed."
+msgstr "获取新IP的窗口会出现。"
+
+# c8424da0e97a443f9d01fab04339184f
+#: ../../networking/portable_ips.rst:102
+msgid "Specify whether you want cross-zone IP or not."
+msgstr "说明是否需要IP跨区。"
+
+# 222f964df0914c01bf92a5a5f461d4cc
+#: ../../networking/portable_ips.rst:104
+msgid "Click Yes in the confirmation dialog."
+msgstr "在确认对话框中点击确定。"
+
+# 97dbf547785f4b1aaea165efca4b50a9
+#: ../../networking/portable_ips.rst:106
+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 "稍等一会，新的IP地址会出现，状态栏为会显示为分配。现在可以在端口转发或静态NAT规则中使用此IP地址了。"
+
+# b84bba5db56047ba9dcd10cad9a14c3a
+#: ../../networking/portable_ips.rst:112
+msgid "Transferring Portable IP"
+msgstr "便携式IP"
+
+# f9ff7b7ea0d541a2bb6530a633a01f8b
+#: ../../networking/portable_ips.rst:114
+msgid ""
+"An IP can be transferred from one network to another only if Static NAT is "
+"enabled. However, when a portable IP is associated with a network, you can "
+"use it for any service in the network."
+msgstr "IP要从一个网络转换至另一网络的话，只需启用静态NAT。但是，当一个portable IP对应一个网络的时候，你可以在网络中为任何服务使用它 。"
+
+# 2112dfc5676e4e7fbeb783e1bdbafb8d
+#: ../../networking/portable_ips.rst:118
+msgid ""
+"To transfer a portable IP across the networks, execute the following API:"
+msgstr "要跨网络转换一个portable IP，执行下列API："
+
+# 794e73bb89214a29bc9257f2fc58c178
+#: ../../networking/portable_ips.rst:125
+msgid ""
+"Replace the UUID with appropriate UUID. For example, if you want to transfer"
+" a portable IP to network X and VM Y in a network, execute the following:"
+msgstr "用正确的UUID替换此处的UUID。比如，如果你想转换一个portable IP至X网络和一个网络中的VM Y，请执行下列操作："
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/public_ips_and_vlans_for_accounts.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/public_ips_and_vlans_for_accounts.mo
new file mode 100644
index 0000000..5f1ad7a
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/public_ips_and_vlans_for_accounts.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/public_ips_and_vlans_for_accounts.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/public_ips_and_vlans_for_accounts.po
new file mode 100644
index 0000000..c6e15c6
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/public_ips_and_vlans_for_accounts.po
@@ -0,0 +1,286 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# e16ce84ab27a470389c600bd7f1937e6
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:18
+msgid "Reserving Public IP Addresses and VLANs for Accounts"
+msgstr "为账户预留公共IP地址及VLANS"
+
+# d20bf40a65964aee8e9477cfb99a8d76
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:20
+msgid ""
+"CloudStack provides you the ability to reserve a set of public IP addresses "
+"and VLANs exclusively for an account. During zone creation, you can continue"
+" defining a set of VLANs and multiple public IP ranges. This feature extends"
+" the functionality to enable you to dedicate a fixed set of VLANs and guest "
+"IP addresses for a tenant."
+msgstr "CloudStack可以让你能够独立的为账户预留一部分公共IP地址和VLANS。在创建区域阶段，你可以继续定义一部分VLANS以及多个公共IP范围。这种功能扩展特性可以让你能够为客户预留固定的一部分VLAN和客户IP地址"
+
+# e0cd381debc1495fa88b0bed963e8b16
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:26
+msgid ""
+"Note that if an account has consumed all the VLANs and IPs dedicated to it, "
+"the account can acquire two more resources from the system. CloudStack "
+"provides the root admin with two configuration parameter to modify this "
+"default behavior: use.system.public.ips and use.system.guest.vlans. These "
+"global parameters enable the root admin to disallow an account from "
+"acquiring public IPs and guest VLANs from the system, if the account has "
+"dedicated resources and these dedicated resources have all been consumed. "
+"Both these configurations are configurable at the account level."
+msgstr "注意，如果一个账户使用了所有分配给他的VLAN和IP，这个账户可以从系统获得二个以上的资源。CloudStack为根管理员提供了二个参数可以进行控制，分别是use.system.public.ips和use.system.guest.vlans。当一个账户分配了资源并且这些资源已经被消耗掉时，这二个全局参数可以使根管理员拒绝此账户从公共IP和来宾VLAN获取资源。二个配置都能在帐户级别进行配置。"
+
+# baef2538501f4f729cd5b4f69fbbefaa
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:36
+msgid "This feature provides you the following capabilities:"
+msgstr "这些特性可提供以下的功能："
+
+# 4e16f6283a6e4f389b44d3af88cc4364
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:38
+msgid ""
+"Reserve a VLAN range and public IP address range from an Advanced zone and "
+"assign it to an account"
+msgstr "从一个高级区域中预留一个VLAN范围和公共IP地址，并可以将其指定给一个账户。"
+
+# c67672fcea6c4ae69a5c3c7d8fbd6a33
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:41
+msgid "Disassociate a VLAN and public IP address range from an account"
+msgstr "将一个VLAN和IP地址从一个账户解除联系。"
+
+# 8451f0b840ab420cb1589fcc1572e6c0
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:43
+msgid "View the number of public IP addresses allocated to an account"
+msgstr "查看分配给帐户的公共IP地址。"
+
+# 2a183b234d9c44b8b99fa31594f06e38
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:45
+msgid ""
+"Check whether the required range is available and is conforms to account "
+"limits."
+msgstr "检查需要的范围是否可用并且要符合帐户限制。"
+
+# be8cff382a7748e4a75c68c3f8aa3dd7
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:48
+msgid "The maximum IPs per account limit cannot be superseded."
+msgstr "不能超过每个账户最大的IP限制数。"
+
+# 17f5e888607c4537816aa2f2e8b7c363
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:52
+msgid "Dedicating IP Address Ranges to an Account"
+msgstr "分配IP地址给一个账户"
+
+# 5409cfc1bd6f4b41bdd23eee4d6b9396
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:54
+msgid "Log in to the CloudStack UI as administrator."
+msgstr "作为管理员登录到CloudStack用户界面。"
+
+# b8615267486a44ff8ee964b26529f16d
+# ba51a55851504a869dc0f28d293993ad
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:56
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:126
+msgid "In the left navigation bar, click Infrastructure."
+msgstr "在左侧导航栏中，点击基础架构"
+
+# b1c57a90f0c843c4906f95e699dd7d13
+# 2a38ee721dc8442f850ff993fa52de59
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:58
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:128
+msgid "In Zones, click View All."
+msgstr "在区域中，点击查看全部"
+
+# defb870416a14ff0a7ea37bf68b8e890
+# 207025dba9b843299213868bf721e0d2
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:60
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:130
+msgid "Choose the zone you want to work with."
+msgstr "选择你要设置的区域。"
+
+# 04eaa49757a64adf830002153cf8db20
+# cea8888967a844ccbb283c973f4b9482
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:62
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:132
+msgid "Click the Physical Network tab."
+msgstr "点击物理网络标签卡。"
+
+# fd016a6c74fa4aceb46c592a01f82621
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:64
+msgid "In the Public node of the diagram, click Configure."
+msgstr "在图的公共节点上，点击配置。"
+
+# abe4deb76feb40fd9fa6dd1461e1dec3
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:66
+msgid "Click the IP Ranges tab."
+msgstr "点击IP范围页签。"
+
+# 3686de2bd0e24c578fb64abcd3b86fbc
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:68
+msgid ""
+"You can either assign an existing IP range to an account, or create a new IP"
+" range and assign to an account."
+msgstr "或者指定一个已经的IP范围给帐户，或创建一个新的IP范围并指定给一个帐户。"
+
+# 90bc5a3040c541cb95831323867cee7d
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:71
+msgid "To assign an existing IP range to an account, perform the following:"
+msgstr "要指定一个已有IP范围给帐户，按以下操作进行"
+
+# 196250a3ddc54abc978d437ea8ba3f96
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:73
+msgid "Locate the IP range you want to work with."
+msgstr "确定需要分配的IP范围"
+
+# 0a707d3297ad4ccfa38f80baa7690816
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:75
+msgid "Click Add Account |addAccount-icon.png| button."
+msgstr "点击添加帐户按钮。|addAccount-icon.png| "
+
+# 3aaf2af3bb8f4c9485ae2e0ada7aee73
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:77
+msgid "The Add Account dialog is displayed."
+msgstr "会弹出添加帐户对话框。"
+
+# b99e236f412f4946af47669c8d62396e
+# eedc80b2aa5c4c8696da4d4b51a28179
+# 39b98908344542aeb2e40bdbf9550571
+# f6dc925b4c634b9fa0523254d12380bb
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:79
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:89
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:107
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:142
+msgid "Specify the following:"
+msgstr "指定以下信息："
+
+# 64e4bf3c9f034ef4adb32087be1bc7aa
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:81
+msgid ""
+"**Account**: The account to which you want to assign the IP address range."
+msgstr "**帐户**: 即需要指定IP地址范围的帐户"
+
+# d15ca620e8154bf9ad213a256496e6e0
+# 09ac68b8a6f24e84b36a726d6058809b
+# f8da528d9cdd447fb262d7ca5542308f
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:84
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:112
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:150
+msgid "**Domain**: The domain associated with the account."
+msgstr "**域**: 与帐户关联的域名"
+
+# 06d6686b378e4a22a762e94353aee862
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:86
+msgid "To create a new IP range and assign an account, perform the following:"
+msgstr "要指定一个新的IP范围给帐户，按以下操作进行"
+
+# dd52a8808d1b44e7ba133f213439d71d
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:91
+msgid "**Gateway**"
+msgstr "**网关**"
+
+# 781ca41349a949cca28101dfea1676d5
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:93
+msgid "**Netmask**"
+msgstr "**掩码**"
+
+# 1b745bfb0a6443e1a0f947860308e044
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:95
+msgid "**VLAN**"
+msgstr "**VLAN**"
+
+# 9526ce220e2941459d408f259d6e9b30
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:97
+msgid "**Start IP**"
+msgstr "**起始IP**"
+
+# a55c7588b51f4a84afa7fa78fc58ed5e
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:99
+msgid "**End IP**"
+msgstr "**结束IP**"
+
+# 9282436854274ee485b8c2df6ba7f342
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:101
+msgid "**Account**: Perform the following:"
+msgstr "**帐户**: 按以下操作进行："
+
+# 678fa43c9d524b8fbb3ca453d599d6f1
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:103
+msgid "Click Account."
+msgstr "点击帐户"
+
+# 58e785cf6c3f4544af852a60e9ff4639
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:105
+msgid "The Add Account page is displayed."
+msgstr "会显示添加帐户页"
+
+# c1b6c5a339b940b7907cfc3fd14b35d6
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:109
+msgid ""
+"**Account**: The account to which you want to assign an IP address range."
+msgstr ""
+
+# e54b45158ec1469392091a64574cbb55
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:115
+msgid "Click OK."
+msgstr "点击确定。"
+
+# cbf3d4473399404684b33c48a92e0148
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:117
+msgid "Click Add."
+msgstr "点击 添加"
+
+# 8d933442217c4288b95b7ed71f57b95f
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:121
+msgid "Dedicating VLAN Ranges to an Account"
+msgstr "确定需要分配的IP范围"
+
+# d7e1ce8c0be24d57b606cd1a7b4ac29e
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:123
+msgid ""
+"After the CloudStack Management Server is installed, log in to the "
+"CloudStack UI as administrator."
+msgstr "安装好CloudStack管理端后，使用管理员帐号登录CloudStack用户界面。"
+
+# 68317dc975da4182878b75c19ec73b1e
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:134
+msgid "In the Guest node of the diagram, click Configure."
+msgstr "在图中的来宾节点上，点击配置"
+
+# de0ffdc9f48d4d068a50a53f85c49cea
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:136
+msgid "Select the Dedicated VLAN Ranges tab."
+msgstr "选择分配VLAN范围页签"
+
+# d7319cdb148746849dba29b0a020ce01
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:138
+msgid "Click Dedicate VLAN Range."
+msgstr "点击分配VLAN范围"
+
+# 6037b47944d9429aad5df0dd7981dace
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:140
+msgid "The Dedicate VLAN Range dialog is displayed."
+msgstr "会弹出分配VLAN对话框。"
+
+# 564cf1e324b54969924910efd7c3f00b
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:144
+msgid "**VLAN Range**: The VLAN range that you want to assign to an account."
+msgstr ""
+
+# b2c4b566d49c4a3b99b3268f4e867233
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:147
+msgid ""
+"**Account**: The account to which you want to assign the selected VLAN "
+"range."
+msgstr ""
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/releasing_an_ip_address.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/releasing_an_ip_address.mo
new file mode 100644
index 0000000..7de1d1f
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/releasing_an_ip_address.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/releasing_an_ip_address.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/releasing_an_ip_address.po
new file mode 100644
index 0000000..c0ee7f3
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/releasing_an_ip_address.po
@@ -0,0 +1,61 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# c50d06f60c5d483ba5f4799c50384e9c
+#: ../../networking/releasing_an_ip_address.rst:18
+msgid "Releasing an IP Address"
+msgstr "释放IP地址"
+
+# 3a245bdefb444425ad5f7bd6a1ea5de2
+#: ../../networking/releasing_an_ip_address.rst:20
+msgid ""
+"When the last rule for an IP address is removed, you can release that IP "
+"address. The IP address still belongs to the VPC; however, it can be picked "
+"up for any guest network again."
+msgstr "当IP的最后一条规则删除后，您就能够释放该IP。然而，该IP仍属于VPC，无论如何，该IP可以再次被VPC中的来宾网络再次获取。"
+
+# 99e24197740148e683aa3ffad5870800
+#: ../../networking/releasing_an_ip_address.rst:24
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# da80f79b21a846878018930987c87ffd
+#: ../../networking/releasing_an_ip_address.rst:26
+msgid "In the left navigation, choose Network."
+msgstr "在左侧的导航栏，选择网络。"
+
+# 24863c020eb04ba9808fc2e0f24e0760
+#: ../../networking/releasing_an_ip_address.rst:28
+msgid "Click the name of the network where you want to work with."
+msgstr "点击拟修改的网络名称。"
+
+# 1e70144ba5394954a2c92850335b7555
+#: ../../networking/releasing_an_ip_address.rst:30
+msgid "Click View IP Addresses."
+msgstr "点击查看IP地址。"
+
+# 3f542514484849b1bfde31aa95ec3a25
+#: ../../networking/releasing_an_ip_address.rst:32
+msgid "Click the IP address you want to release."
+msgstr "点击要释放的IP地址。"
+
+# 7851cee0ec9c4ea3a8d5309aa5f84d40
+#: ../../networking/releasing_an_ip_address.rst:34
+msgid "Click the Release IP button. |ReleaseIPButton.png|"
+msgstr "Click the Release IP button. |ReleaseIPButton.png|"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/remote_access_vpn.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/remote_access_vpn.mo
new file mode 100644
index 0000000..f16bc24
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/remote_access_vpn.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/remote_access_vpn.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/remote_access_vpn.po
new file mode 100644
index 0000000..d6fc91e
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/remote_access_vpn.po
@@ -0,0 +1,1199 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 037fa60a2e2f4601bf22e714a97fe0fd
+#: ../../networking/remote_access_vpn.rst:18
+msgid "Remote Access VPN"
+msgstr "远程访问VPN"
+
+# 8202b8f150584992995c6c6f69a2c907
+#: ../../networking/remote_access_vpn.rst:20
+msgid ""
+"CloudStack account owners can create virtual private networks (VPN) to "
+"access their virtual machines. If the guest network is instantiated from a "
+"network offering that offers the Remote Access VPN service, the virtual "
+"router (based on the System VM) is used to provide the service. CloudStack "
+"provides a L2TP-over-IPsec-based remote access VPN service to guest virtual "
+"networks. Since each network gets its own virtual router, VPNs are not "
+"shared across the networks. VPN clients native to Windows, Mac OS X and iOS "
+"can be used to connect to the guest networks. The account owner can create "
+"and manage users for their VPN. CloudStack does not use its account database"
+" for this purpose but uses a separate table. The VPN user database is shared"
+" across all the VPNs created by the account owner. All VPN users get access "
+"to all VPNs created by the account owner."
+msgstr "CloudStack中的账户拥有者可以建立虚拟专用网(VPN)以便访问他们的虚拟机。如果通过网络方案对来宾网络提供远程VPN访问服务的实例化，虚拟路由(基于System VM)将被用于提供服务。CloudStack为来宾虚拟网络提供了一个基于L2TP-over-IPsec-based协议的远程VPN访问服务。因为每个网络有它自己的虚拟路由器，VPNs不能跨网络共享。Windows, Mac OS X和iOS自带的VPN客户端可以用于访问来宾网络。账户拥有者可以建立并管理他们的VPN用户。CloudStack并不为此使用自己的账户数据库，而是使用一个独立的表。VPN用户数据库在同一个账户拥有者建立的VPN网络中被共享。 也就是说，同一个账户拥有者创建的所有VPN可以被它的所有VPN用户访问。"
+
+# a8a54e6134ab4ebaae71aeb42d0ad32b
+#: ../../networking/remote_access_vpn.rst:35
+msgid ""
+"Make sure that not all traffic goes through the VPN. That is, the route "
+"installed by the VPN should be only for the guest network and not for all "
+"traffic."
+msgstr "确保不是所有的网络流量走VPN。也就是说，用于配置VPN的route不是唯一用于该guest network，也不承担全部的网络流量。"
+
+# a107bc4ab6624b839681adafc00d60e1
+#: ../../networking/remote_access_vpn.rst:39
+msgid ""
+"**Road Warrior / Remote Access**. Users want to be able to connect securely "
+"from a home or office to a private network in the cloud. Typically, the IP "
+"address of the connecting client is dynamic and cannot be preconfigured on "
+"the VPN server."
+msgstr "**公路勇士/远程访问**. .用户希望可以安全地从家里或者办公室连接到云里的一个 私有网络。特别是连接的客户端的IP地址是动态决定的，不能预先配置到VPN 服务器上。"
+
+# 7b5e742bfe7f429794320cf1c32ffdfc
+#: ../../networking/remote_access_vpn.rst:44
+msgid ""
+"**Site to Site**. In this scenario, two private subnets are connected over "
+"the public Internet with a secure VPN tunnel. The cloud user's subnet (for "
+"example, an office network) is connected through a gateway to the network in"
+" the cloud. The address of the user's gateway must be preconfigured on the "
+"VPN server in the cloud. Note that although L2TP-over-IPsec can be used to "
+"set up Site-to-Site VPNs, this is not the primary intent of this feature. "
+"For more information, see \":ref:`setting-s2s-vpn-conn`\"."
+msgstr "**Site to Site 站点到站点**。在这个场景中，两个私有子网通过公共互联网上的一个安全VPN隧道互联。云用户的子网 （例如：办公室的网络）通过一个网关连接到云中的网络。用户的网关地址必须被预先配置到云的VPN服务器上。注意：通过 L2TP-over-IPsec 协议可以用来配置站点到站点的 VPN，虽然这不是该特性的最初目标。更多信息，参考\":ref:`setting-s2s-vpn-conn`\"。"
+
+# 3411c8387ca84f18bd032795907f4585
+#: ../../networking/remote_access_vpn.rst:55
+msgid "Configuring Remote Access VPN"
+msgstr "配置远程访问VPN"
+
+# b5e1d88079c447ba9d2baa0e3f5cf685
+#: ../../networking/remote_access_vpn.rst:57
+msgid "To set up VPN for the cloud:"
+msgstr "为云设置VPN："
+
+# 85153916f2a94aeb80faa2c9f22cfcea
+# e7cff502f3494c00b665a1b732e05fb1
+# 7fd5ac75573d435b8c164435b6b50404
+# ab1f2323529a48e8a071e9baa44284e3
+# 6dfbddbad973426b8d6704da05fb2166
+# ce7c03a477b84c029914728fac5f85d5
+#: ../../networking/remote_access_vpn.rst:59
+#: ../../networking/remote_access_vpn.rst:301
+#: ../../networking/remote_access_vpn.rst:411
+#: ../../networking/remote_access_vpn.rst:431
+#: ../../networking/remote_access_vpn.rst:493
+#: ../../networking/remote_access_vpn.rst:624
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# ef4d98e4df0149d797b4aebfc0dbdc03
+#: ../../networking/remote_access_vpn.rst:61
+msgid "In the left navigation, click Global Settings."
+msgstr "在左侧导航栏，点击 全局设置"
+
+# 6915f23eef3f4ddfaf19ba566058535d
+#: ../../networking/remote_access_vpn.rst:63
+msgid "Set the following global configuration parameters."
+msgstr "设置以下全局配置参数。"
+
+# b46467b5e34e436389d14380f0094d63
+#: ../../networking/remote_access_vpn.rst:65
+msgid ""
+"remote.access.vpn.client.ip.range - The range of IP addresses to be "
+"allocated to remote access VPN clients. The first IP in the range is used by"
+" the VPN server."
+msgstr "remote.access.vpn.client.ip.range – 分配给远程访问VPN客户端的IP地址范围。第一个IP被VPN服务器使用。"
+
+# ad4d961d0bf3453ebc21a59b09ad0207
+#: ../../networking/remote_access_vpn.rst:69
+msgid "remote.access.vpn.psk.length - Length of the IPSec key."
+msgstr "remote.access.vpn.psk.length – IPsec密钥长度。"
+
+# a89aef80d75a49a9bf21eed458b3a570
+#: ../../networking/remote_access_vpn.rst:71
+msgid ""
+"remote.access.vpn.user.limit - Maximum number of VPN users per account."
+msgstr "remote.access.vpn.user.limit – 单个账户的最大VPN用户数量。"
+
+# 115f9b2e63704bd7b8d0880401243098
+#: ../../networking/remote_access_vpn.rst:74
+msgid "To enable VPN for a particular network:"
+msgstr "为特定的网络启用VPN："
+
+# 1cbcce1e10884bc0906f10625b02b967
+# d3065ab6ac634b4ab6d37d5cc5f6b0f8
+#: ../../networking/remote_access_vpn.rst:76
+#: ../../networking/remote_access_vpn.rst:101
+msgid "Log in as a user or administrator to the CloudStack UI."
+msgstr "使用用户或管理员身份登录到CloudStack用户界面。"
+
+# 911488c63a744096b46e3c6ffffb13be
+# d221bc15811f454fbe75a5f60599eddf
+#: ../../networking/remote_access_vpn.rst:78
+#: ../../networking/remote_access_vpn.rst:103
+msgid "In the left navigation, click Network."
+msgstr "在左边导航栏，点击网络。"
+
+# 6c20446c6a1442f5997a8515ffe0e2b7
+#: ../../networking/remote_access_vpn.rst:80
+msgid "Click the name of the network you want to work with."
+msgstr "选择你要操作的网络名称"
+
+# a23f38b6e2c8464bb754dcb7965bd45e
+#: ../../networking/remote_access_vpn.rst:82
+msgid "Click View IP Addresses."
+msgstr "点击查看IP地址。"
+
+# ddf12be035374568a290af5640b40e74
+#: ../../networking/remote_access_vpn.rst:84
+msgid "Click one of the displayed IP address names."
+msgstr "点击一个显示的IP地址名称。"
+
+# 41e32709f78944188aa733087e185747
+# 29b34df35b844a28a5c4da345fb4deca
+#: ../../networking/remote_access_vpn.rst:86
+#: ../../networking/remote_access_vpn.rst:140
+msgid "Click the Enable VPN button. |vpn-icon.png|"
+msgstr "点击启用VPN按钮。|vpn-icon.png|"
+
+# 2721223cf47046fa977985536715b7f7
+#: ../../networking/remote_access_vpn.rst:88
+msgid "The IPsec key is displayed in a popup window."
+msgstr "IPsec密钥将显示在弹出的窗口中。"
+
+# 4837a25ffda64a66818f80b1160c7cd2
+#: ../../networking/remote_access_vpn.rst:92
+msgid "Configuring Remote Access VPN in VPC"
+msgstr "为VPC配置远程访问VPN"
+
+# c157c1f5cdd34780971c2d08fa7c492c
+#: ../../networking/remote_access_vpn.rst:94
+msgid ""
+"On enabling Remote Access VPN on a VPC, any VPN client present outside the "
+"VPC can access VMs present in the VPC by using the Remote VPN connection. "
+"The VPN client can be present anywhere except inside the VPC on which the "
+"user enabled the Remote Access VPN service."
+msgstr "在VPC中启用远程访问VPN，任何VPC以外的VPN客户端都可以使用远程VPN连接访问VPC中的VM。VPN客户端可以在除了用户启用了远程访问VPN服务的VPC中的任何位置。"
+
+# 5254f550923d4da39985b04b9a5b5054
+#: ../../networking/remote_access_vpn.rst:99
+msgid "To enable VPN for a VPC:"
+msgstr "为VPC开启VPN："
+
+# 12f54511f47d449693acfea97e8d4600
+# 435bbd53f5414d84ba589387bf3fdce6
+# b89124caf1504a709e89424403a433ed
+# 7f0dcc6104d34e828aed248a3d1e5382
+#: ../../networking/remote_access_vpn.rst:105
+#: ../../networking/remote_access_vpn.rst:435
+#: ../../networking/remote_access_vpn.rst:497
+#: ../../networking/remote_access_vpn.rst:628
+msgid "In the Select view, select VPC."
+msgstr "在选择视图中，选择VPC。"
+
+# 7febfd652a0f4a4a9e44f110742bf34a
+# f923f2ca6046405ab0c396e3ca9d07ec
+# 07d5aa607fb94d8b9968b055618eea1c
+#: ../../networking/remote_access_vpn.rst:107
+#: ../../networking/remote_access_vpn.rst:437
+#: ../../networking/remote_access_vpn.rst:630
+msgid ""
+"All the VPCs that you have created for the account is listed in the page."
+msgstr "此帐号创建的所有VPC将显示在页面中。"
+
+# 9c932fa1898c4fef97f99b0535e90a08
+#: ../../networking/remote_access_vpn.rst:110
+msgid "Click the Configure button of the VPC."
+msgstr "点击VPC的配置按钮。"
+
+# 83859c50046f48e4b614cd9f79148c16
+# 15f6f70e22df4f90868d62f6c93d09f7
+# 22a5c413786843acb09faad526a6e8e0
+# b4e49b76aea54ad6a1b5116db84dd6d6
+#: ../../networking/remote_access_vpn.rst:112
+#: ../../networking/remote_access_vpn.rst:446
+#: ../../networking/remote_access_vpn.rst:509
+#: ../../networking/remote_access_vpn.rst:641
+msgid "For each tier, the following options are displayed:"
+msgstr "对于每一个层，会显示以下选项。"
+
+# f709cfb9270544caa350d3649e206913
+# 1e135a9023a3449996277c5654e0ffe8
+# 36d751e518594344814cd905fce95167
+# 5f29611ae8024e66a507590e86ca1301
+#: ../../networking/remote_access_vpn.rst:114
+#: ../../networking/remote_access_vpn.rst:448
+#: ../../networking/remote_access_vpn.rst:511
+#: ../../networking/remote_access_vpn.rst:643
+msgid "Internal LB"
+msgstr "内部LB"
+
+# 38b29ff504c24ecc8d7d54f35ab29998
+# d744448419454b5ba7aae6c638c1f8fd
+# 7e6e21ff676c435d902e75134d2341e5
+# b7dd123eea7d460aa99844bad34e0f91
+#: ../../networking/remote_access_vpn.rst:116
+#: ../../networking/remote_access_vpn.rst:450
+#: ../../networking/remote_access_vpn.rst:513
+#: ../../networking/remote_access_vpn.rst:645
+msgid "Public LB IP"
+msgstr "公共LB IP"
+
+# 74d00e17afdf47d8a79f5c8f0a90a214
+# 404668f335f04d41947db0129e79e65f
+# bee509b27e7c4c9985f5bd7c9169ecaf
+# 7f14717fbb6e471c9e00e2f7622cfa7b
+#: ../../networking/remote_access_vpn.rst:118
+#: ../../networking/remote_access_vpn.rst:452
+#: ../../networking/remote_access_vpn.rst:515
+#: ../../networking/remote_access_vpn.rst:647
+msgid "Static NAT"
+msgstr "静态 NAT"
+
+# 6fd6582e4c7d47019c91a20d69646e3a
+# e333c5792fca4359b9348192f5918984
+# bdf83d752fbc42ef93ab96051cdf7700
+# 30265536e81c46c2879ee0cca63d1297
+#: ../../networking/remote_access_vpn.rst:120
+#: ../../networking/remote_access_vpn.rst:454
+#: ../../networking/remote_access_vpn.rst:517
+#: ../../networking/remote_access_vpn.rst:649
+msgid "Virtual Machines"
+msgstr "虚拟机"
+
+# 8696dd08ef2d4b6a816ecd0095cdf602
+# f1f39145e71e46b09b4c26ce0175e5b8
+# fe3c8f334ef04b4aa83e3850c9666137
+# 54ff7edf855e482da2b26688c543effe
+#: ../../networking/remote_access_vpn.rst:122
+#: ../../networking/remote_access_vpn.rst:456
+#: ../../networking/remote_access_vpn.rst:519
+#: ../../networking/remote_access_vpn.rst:651
+msgid "CIDR"
+msgstr "CIDR"
+
+# 1bd24a8501fd4efd8cd4d0eba492ce37
+# e7a3e4a10b2e484f8b311cdb938a0e47
+# 95e13a760c004dc9a119ddf73d83d0fa
+# 5605be5958c24cb5a0f534dbdecdfa40
+#: ../../networking/remote_access_vpn.rst:124
+#: ../../networking/remote_access_vpn.rst:458
+#: ../../networking/remote_access_vpn.rst:521
+#: ../../networking/remote_access_vpn.rst:653
+msgid "The following router information is displayed:"
+msgstr "显示以下路由器信息："
+
+# 8d80f7dd9bcc41f38e801ab022f3fa7d
+# 5c726601395a427e9f541bf544194e40
+# 8b623ab0e8764c58bad6a828685b3cce
+# 71bcceb5de54474b88583e11b88f962e
+#: ../../networking/remote_access_vpn.rst:126
+#: ../../networking/remote_access_vpn.rst:460
+#: ../../networking/remote_access_vpn.rst:523
+#: ../../networking/remote_access_vpn.rst:655
+msgid "Private Gateways"
+msgstr "专用网关"
+
+# 0b3d0e7c6eac4b83b9912d3af84c76b3
+# 582728e1b1c043f0bde4a3c35e0ebaba
+# df66b830cc464227ab4da8790a6275bf
+# 4055bdef61d847dc91261a6fc6346d1d
+#: ../../networking/remote_access_vpn.rst:128
+#: ../../networking/remote_access_vpn.rst:462
+#: ../../networking/remote_access_vpn.rst:525
+#: ../../networking/remote_access_vpn.rst:657
+msgid "Public IP Addresses"
+msgstr "公共IP地址"
+
+# 9ce2994577cc43f9bd1f86225e23149e
+# fbf89a2ae9534ea18fb4673230aa75fb
+# 0720a5b1037e49ffbf44a70beacd5c9b
+# 3ade6e74142f446c9bea2329e2828be8
+#: ../../networking/remote_access_vpn.rst:130
+#: ../../networking/remote_access_vpn.rst:464
+#: ../../networking/remote_access_vpn.rst:527
+#: ../../networking/remote_access_vpn.rst:659
+msgid "Site-to-Site VPNs"
+msgstr "站点到站点 VPN"
+
+# 8c10e84bb92143eb918356bda1b0e7e5
+# 376033730f8d4e0b88fc25e1b6fdea80
+# a7e9c55327984532a4460a2b4ba05bb4
+# cd29b4ee7b0c4da0aec784bb04dce7e6
+#: ../../networking/remote_access_vpn.rst:132
+#: ../../networking/remote_access_vpn.rst:466
+#: ../../networking/remote_access_vpn.rst:529
+#: ../../networking/remote_access_vpn.rst:661
+msgid "Network ACL Lists"
+msgstr "网络 ACL列表"
+
+# c45c88d1e8af4023bd23142b7397edd5
+#: ../../networking/remote_access_vpn.rst:134
+msgid "In the Router node, select Public IP Addresses."
+msgstr "在路由器节点中，选择公共IP地址。"
+
+# 2334ea7959384b2bbf5138eb8c7aaf78
+#: ../../networking/remote_access_vpn.rst:136
+msgid "The IP Addresses page is displayed."
+msgstr "系统显示IP地址页面。"
+
+# 31440b2a6daa47d2a5ff458a51ca81cc
+#: ../../networking/remote_access_vpn.rst:138
+msgid "Click Source NAT IP address."
+msgstr "点击源NAT IP地址。"
+
+# 8cf058b60a184e129abe4d2bc8ade840
+#: ../../networking/remote_access_vpn.rst:142
+msgid "Click OK to confirm. The IPsec key is displayed in a pop-up window."
+msgstr "点击OK确认。IPsec密钥将显示在弹出的窗口中。"
+
+# 36c398fbda5b45599ac36f3b5b77e97d
+#: ../../networking/remote_access_vpn.rst:144
+msgid "Now, you need to add the VPN users."
+msgstr "现在，需要添加VPN用户。"
+
+# a6d5430b813547dabde217104eba046a
+#: ../../networking/remote_access_vpn.rst:146
+msgid "Click the Source NAT IP."
+msgstr "点击源NAT IP。"
+
+# 88ac91cdca464aa8a924d7cbca73f3df
+#: ../../networking/remote_access_vpn.rst:148
+msgid "Select the VPN tab."
+msgstr "选择VPN选项卡。"
+
+# 76a034604e9a4113a46051cde33b0cd8
+#: ../../networking/remote_access_vpn.rst:150
+msgid ""
+"Add the username and the corresponding password of the user you wanted to "
+"add."
+msgstr "为你要创建的用户添加用户名和对应的密码。"
+
+# f388fc2f4f0749f5bbb9e062d57f1137
+#: ../../networking/remote_access_vpn.rst:153
+msgid "Click Add."
+msgstr "点击 添加"
+
+# c491f786e1874564b25032b670c35f98
+#: ../../networking/remote_access_vpn.rst:155
+msgid "Repeat the same steps to add the VPN users."
+msgstr "重复相同的步骤添加VPN用户。"
+
+# d3c8df533b2c4e659158e77c8669a813
+#: ../../networking/remote_access_vpn.rst:159
+msgid "Using Remote Access VPN with Windows"
+msgstr "在Windows系统中使用远程访问VPN"
+
+# d03485e36a8744758782e81ab88041d1
+#: ../../networking/remote_access_vpn.rst:161
+msgid ""
+"The procedure to use VPN varies by Windows version. Generally, the user must"
+" edit the VPN properties and make sure that the default route is not the "
+"VPN. The following steps are for Windows L2TP clients on Windows Vista. The "
+"commands should be similar for other Windows versions."
+msgstr "程序使用不同Windows版本的VPN。通常用户必须编辑VPN属性并确保不使用VPN的默认路由。以下步骤使用基于Windows Vista的Windows L2TP客户端。命令应该类似于其他版本的Windows。"
+
+# 98196e5429de407da75adf5f3ce7cf8d
+#: ../../networking/remote_access_vpn.rst:166
+msgid ""
+"Log in to the CloudStack UI and click on the source NAT IP for the account. "
+"The VPN tab should display the IPsec preshared key. Make a note of this and "
+"the source NAT IP. The UI also lists one or more users and their passwords. "
+"Choose one of these users, or, if none exists, add a user and password."
+msgstr "登录到CloudStack用户界面并点击账户下的源NAT IP。VPN选项卡应该会显示IPsec预共享密钥。记录该密钥和源NAT IP。用户界面同样也列出了一个多或多个用户他们的密码。选择一个用户，或者如果不存在任何用户，则创建一个用户。"
+
+# 6a896fa8431d479195d161efebf56672
+#: ../../networking/remote_access_vpn.rst:172
+msgid ""
+"On the Windows box, go to Control Panel, then select Network and Sharing "
+"center. Click Setup a connection or network."
+msgstr "在Windows中，进入控制面板，然后选择网络和共享中心，点击设置一个网络连接。"
+
+# 8e983aa928b444228e689749e8fc0801
+#: ../../networking/remote_access_vpn.rst:175
+msgid "In the next dialog, select No, create a new connection."
+msgstr "在下一个对话框中，选择否，创建一个新的连接。"
+
+# 98f484c7652c45d2ae57690d719610ed
+#: ../../networking/remote_access_vpn.rst:177
+msgid "In the next dialog, select Use my Internet Connection (VPN)."
+msgstr "在下一个对话框中，选择使用我的Internet连接(VPN)."
+
+# 784c5c041ba94caea475a667add0adcd
+#: ../../networking/remote_access_vpn.rst:179
+msgid ""
+"In the next dialog, enter the source NAT IP from step #1 and give the "
+"connection a name. Check Don't connect now."
+msgstr "在下一个对话框中，输入此步骤#1中的源NAT IP地址并填写连接名称。勾选现在不连接。"
+
+# 41d1540c0a7d401a9c549bd5304f18ce
+#: ../../networking/remote_access_vpn.rst:183
+msgid ""
+"In the next dialog, enter the user name and password selected in step #1."
+msgstr "在下一个对话框中，输入此步骤#1中的用户名和密码。"
+
+# 3cbbd674fd8d412c90bfbbeb8f607ea0
+#: ../../networking/remote_access_vpn.rst:186
+msgid "Click Create."
+msgstr "点击创建。"
+
+# 85a9ef6f201e47f584255229980b3d87
+#: ../../networking/remote_access_vpn.rst:188
+msgid ""
+"Go back to the Control Panel and click Network Connections to see the new "
+"connection. The connection is not active yet."
+msgstr "返回控制面板并点击网络连接查看这个新的连接。但当前连接并不是活动状态。"
+
+# 1d169d66dd744654bd8ea7dd62a677a6
+#: ../../networking/remote_access_vpn.rst:191
+msgid ""
+"Right-click the new connection and select Properties. In the Properties "
+"dialog, select the Networking tab."
+msgstr "在新创建的连接上点击右键并选择属性。在属性对话框中，选择网络选项卡。"
+
+# a191730de1684f06a3d729e5cde2e487
+#: ../../networking/remote_access_vpn.rst:196
+msgid ""
+"In Type of VPN, choose L2TP IPsec VPN, then click IPsec settings. Select Use"
+" preshared key. Enter the preshared key from step #1."
+msgstr "在VPN类型中，选择L2TP IPsec VPN,然后点击IPsec设置，选择用户预共享密钥。并输入此步骤#1中提供的密钥。"
+
+# 343858b6c3e5498fad0bd34b503e792d
+#: ../../networking/remote_access_vpn.rst:199
+msgid ""
+"The connection is ready for activation. Go back to Control Panel -> Network "
+"Connections and double-click the created connection."
+msgstr "该连接已经准备好被激活。返回到控制面板 -> 网络连接，双击创建连接。"
+
+# e60c05ee4aef40d38a3a0b01aade9b5e
+#: ../../networking/remote_access_vpn.rst:202
+msgid "Enter the user name and password from step #1."
+msgstr "输入此步骤 #1中提供的用户名和密码。"
+
+# d1cfefca174a4554a0c4170ec0c49f9b
+#: ../../networking/remote_access_vpn.rst:206
+msgid "Using Remote Access VPN with Mac OS X"
+msgstr "在Mac OS X 中使用远程访问VPN"
+
+# 728cc61e43c440459c1ad6252a2f6b97
+#: ../../networking/remote_access_vpn.rst:208
+msgid ""
+"First, be sure you've configured the VPN settings in your CloudStack "
+"install. This section is only concerned with connecting via Mac OS X to your"
+" VPN."
+msgstr "首先，确保在你的CloudStack中已经设置好VPN。本章节仅涉及通过Mac OS X 连接至VPN。"
+
+# b3185af9f4534991ad3e3e5b66f47da2
+#: ../../networking/remote_access_vpn.rst:212
+msgid ""
+"Note, these instructions were written on Mac OS X 10.7.5. They may differ "
+"slightly in older or newer releases of Mac OS X."
+msgstr "请注意，此指南只基于Mac OS X 10.7.5 。在旧版或新版本的Mac OS X中可能会略有不同。"
+
+# 6f2aaf1e33d6421db0f521c5820d02c8
+#: ../../networking/remote_access_vpn.rst:215
+msgid "On your Mac, open System Preferences and click Network."
+msgstr "在Mac中，打开系统偏好设置然后点击网络。"
+
+# 26e7088ea9494f94922f1a8f5e0ad753
+#: ../../networking/remote_access_vpn.rst:217
+msgid "Make sure Send all traffic over VPN connection is not checked."
+msgstr "确保Send all traffic over VPN connection没有被选定。"
+
+# 8e0600ca2c9546a2b3905659b64a835b
+#: ../../networking/remote_access_vpn.rst:219
+msgid ""
+"If your preferences are locked, you'll need to click the lock in the bottom "
+"left-hand corner to make any changes and provide your administrator "
+"credentials."
+msgstr "如果你的首选项框被锁住，你如果要做些改动需要点击底部左侧的锁按钮，并提供管理员认证。"
+
+# da1ba33a066b4415a728d14ab936780c
+#: ../../networking/remote_access_vpn.rst:223
+msgid ""
+"You will need to create a new network entry. Click the plus icon on the "
+"bottom left-hand side and you'll see a dialog that says \"Select the "
+"interface and enter a name for the new service.\" Select VPN from the "
+"Interface drop-down menu, and \"L2TP over IPSec\" for the VPN Type. Enter "
+"whatever you like within the \"Service Name\" field."
+msgstr "您将需要创建一个新的网络入口。点击底部左侧的加号图标，你会看到一个对话框，写着“选择接口并输入新服务的名称”。在接口下拉菜单中选择VPN，VPN类型为“基于IPSec的L2TP”。在“服务名称”中输入任何你喜欢的字段。"
+
+# b96bb5f3c9534d3384752b6c652405b5
+#: ../../networking/remote_access_vpn.rst:229
+msgid ""
+"You'll now have a new network interface with the name of whatever you put in"
+" the \"Service Name\" field. For the purposes of this example, we'll assume "
+"you've named it \"CloudStack.\" Click on that interface and provide the IP "
+"address of the interface for your VPN under the Server Address field, and "
+"the user name for your VPN under Account Name."
+msgstr "现在你需要在\"Service Name\" 中填入新的网络接口的名称。对于这个例子，我们假设你已经把它命名为“CloudStack”。点击该接口，并在服务器地址字段中填入提供的VPN IP地址，并在账户名称中填入您的VPN用户名。"
+
+# db5b3b2b72e449368be600488d32a212
+#: ../../networking/remote_access_vpn.rst:236
+msgid ""
+"Click Authentication Settings, and add the user's password under User "
+"Authentication and enter the pre-shared IPSec key in the Shared Secret field"
+" under Machine Authentication. Click OK."
+msgstr "点击身份验证设置，在机器验证中，用户身份验证下输入用户名和密码，在共享密钥下输入预共享IPsec密钥。点击OK。"
+
+# 79ff11baad9844c9a7bb84f19aac4703
+#: ../../networking/remote_access_vpn.rst:240
+msgid ""
+"You may also want to click the \"Show VPN status in menu bar\" but that's "
+"entirely optional."
+msgstr "你也可以点击\"在菜单栏中查看VPN状态\",这完全是可选的操作。"
+
+# 74b926642e7d49ca925804a4d6d99abc
+#: ../../networking/remote_access_vpn.rst:243
+msgid "Now click \"Connect\" and you will be connected to the CloudStack VPN."
+msgstr "现在点击\"连接\" 你将会连接到CloudStack VPN。"
+
+# fb0aef197790435d95971b0006f98a9d
+#: ../../networking/remote_access_vpn.rst:249
+msgid "Setting Up a Site-to-Site VPN Connection"
+msgstr "配置站点到站点的VPN连接"
+
+# b113a5a8546b4ce8b1a7507f2b860ad7
+#: ../../networking/remote_access_vpn.rst:251
+msgid ""
+"A Site-to-Site VPN connection helps you establish a secure connection from "
+"an enterprise datacenter to the cloud infrastructure. This allows users to "
+"access the guest VMs by establishing a VPN connection to the virtual router "
+"of the account from a device in the datacenter of the enterprise. You can "
+"also establish a secure connection between two VPC setups or high "
+"availability zones in your environment. Having this facility eliminates the "
+"need to establish VPN connections to individual VMs."
+msgstr "一个站点到站点的VPN连接可以帮助你建立从云基础架构到企业内部数据中心的安全连接.这就允许一个账户从企业内部数据中心的设备连接到此账户启用VPN连接的虚拟路由器上, 从而通过VPN连接到该账户的虚拟机.你也可以在两个VPC之间或是高可用区域之间建立VPC以加强安全。这样一来，就不需要在虚拟机之间建立VPN连接的必要了。"
+
+# ec0ce935716740158c031ebf544b7294
+#: ../../networking/remote_access_vpn.rst:260
+msgid ""
+"The difference from Remote VPN is that Site-to-site VPNs connects entire "
+"networks to each other, for example, connecting a branch office network to a"
+" company headquarters network. In a site-to-site VPN, hosts do not have VPN "
+"client software; they send and receive normal TCP/IP traffic through a VPN "
+"gateway."
+msgstr "与Remote VPN不同，Site-to-site VPNs是将两个网络相互连接。比如，将一个分支办公室的网络与总公司网络互联，Site-to-site VPN的两个主机不需要VPN客户端软件，它们通过VPN网关收发普通的TCP/IP数据包流量 。"
+
+# 79120b77963b4f77afa51573e6ad1ca7
+#: ../../networking/remote_access_vpn.rst:266
+msgid "The supported endpoints on the remote datacenters are:"
+msgstr "目前支持的数据中心的终端设备是:"
+
+# 34aba4dd56884ad3871e85272aab2acf
+#: ../../networking/remote_access_vpn.rst:268
+msgid "Cisco ISR with IOS 12.4 or later"
+msgstr "Cisco ISR IOS 12.4或更新"
+
+# 95978dcfdbf34c2886952ee16cb6e16d
+#: ../../networking/remote_access_vpn.rst:270
+msgid "Juniper J-Series routers with JunOS 9.5 or later"
+msgstr "Juniper J-系统 路由器 JunOS 9.5 或更新版本"
+
+# 272a2a827c494e90a6b2d52dc96b7f0b
+#: ../../networking/remote_access_vpn.rst:272
+msgid "CloudStack virtual routers"
+msgstr "CloudStack虚拟路由器。"
+
+# 8c16297c0eab4c72b6a2a29b0f4866d1
+#: ../../networking/remote_access_vpn.rst:275
+msgid ""
+"In addition to the specific Cisco and Juniper devices listed above, the "
+"expectation is that any Cisco or Juniper device running on the supported "
+"operating systems are able to establish VPN connections."
+msgstr "除了上述指定的Cisco和Juniper设备, 所期望的是任何Cisco或Juniper的设备在支持的操作系统上都可以建立VPN连接."
+
+# eb701cb20d40405b9ca1d79ce15b681f
+#: ../../networking/remote_access_vpn.rst:279
+msgid "To set up a Site-to-Site VPN connection, perform the following:"
+msgstr "为了建立站点到站点的VPN连接, 需要执行以下步骤:"
+
+# b5f397a7a64b47168a74fb1618810e5c
+#: ../../networking/remote_access_vpn.rst:281
+msgid "Create a Virtual Private Cloud (VPC)."
+msgstr "创建一个虚拟私有云(VPC)."
+
+# 1d44be641cf042b99841b146bb055956
+#: ../../networking/remote_access_vpn.rst:283
+msgid "See \":ref:`configuring-vpc`\"."
+msgstr "参考\":ref:`configuring-vpc`\"."
+
+# f1ff67e23d7d4eaeb81c1b5686399942
+#: ../../networking/remote_access_vpn.rst:285
+msgid "Create a VPN Customer Gateway."
+msgstr "创建一个VPN客户网关."
+
+# e3425171b9504f5b958d0802ca1a55ce
+#: ../../networking/remote_access_vpn.rst:287
+msgid "Create a VPN gateway for the VPC that you created."
+msgstr "为你创建的VPC设定一个VPN网关."
+
+# 6d0964544a6944f39ec8eafdaf587428
+#: ../../networking/remote_access_vpn.rst:289
+msgid ""
+"Create VPN connection from the VPC VPN gateway to the customer VPN gateway."
+msgstr "从VPC的VPN网关到客户的VPN网关建立VPN连接."
+
+# 3d85874020904fbdb261885b5e2f05ce
+#: ../../networking/remote_access_vpn.rst:294
+msgid "Creating and Updating a VPN Customer Gateway"
+msgstr "创建和更新一个VPN客户网关."
+
+# 9b0857af13544aaebee5984422c93195
+#: ../../networking/remote_access_vpn.rst:297
+msgid ""
+"A VPN customer gateway can be connected to only one VPN gateway at a time."
+msgstr "一个VPN客户网关在同一时间只能连接一个VPN网关。"
+
+# 1a951a0ee8d54164b9b99ff9cd080e58
+#: ../../networking/remote_access_vpn.rst:299
+msgid "To add a VPN Customer Gateway:"
+msgstr "添加 VPN 客户网关"
+
+# 6a26e636eb224d1eb75c9782de7c830d
+# affc98b5cd4b401086e5e00f9e69ac90
+# 23c81aa674f64826830390c49839730c
+# 98dc2f6f69d341b0b1867f35102e20ff
+# d4efd83e728b439eaa8408bd783d0c11
+#: ../../networking/remote_access_vpn.rst:303
+#: ../../networking/remote_access_vpn.rst:413
+#: ../../networking/remote_access_vpn.rst:433
+#: ../../networking/remote_access_vpn.rst:495
+#: ../../networking/remote_access_vpn.rst:626
+msgid "In the left navigation, choose Network."
+msgstr "在左侧的导航栏，选择网络。"
+
+# b0e99af0f0014e1aa156dd7f2644f23a
+# cf4e8a6aa8be4c3e9c92bd5f84e9b571
+#: ../../networking/remote_access_vpn.rst:305
+#: ../../networking/remote_access_vpn.rst:415
+msgid "In the Select view, select VPN Customer Gateway."
+msgstr "在选择视图里，选择VPN客户网关。"
+
+# 51d8e12e75dd47e4b2d4a9c52da89be9
+#: ../../networking/remote_access_vpn.rst:307
+msgid "Click Add VPN Customer Gateway."
+msgstr "点击添加 VPN 客户网关。"
+
+# e72b7822c85649f99f01e845e1418844
+#: ../../networking/remote_access_vpn.rst:309
+msgid "|addvpncustomergateway.png|"
+msgstr "|addvpncustomergateway.png|"
+
+# 0810d2cb133043b4858badbc2e4ac704
+#: ../../networking/remote_access_vpn.rst:311
+msgid "Provide the following information:"
+msgstr "填写以下内容："
+
+# 372ec8983a514ad3b0927d01bc30fae6
+#: ../../networking/remote_access_vpn.rst:313
+msgid "**Name**: A unique name for the VPN customer gateway you create."
+msgstr "**名称**: 你添加的VPN客户网关的一个唯一的名称。"
+
+# 0cd283ba65a241cf97d90b2c5f04c36f
+#: ../../networking/remote_access_vpn.rst:315
+msgid "**Gateway**: The IP address for the remote gateway."
+msgstr "**IP地址**: 远端网关的IP地址。"
+
+# 0e3f2efe75f7454e9f2ac706604f832d
+#: ../../networking/remote_access_vpn.rst:317
+msgid ""
+"**CIDR list**: The guest CIDR list of the remote subnets. Enter a CIDR or a "
+"comma-separated list of CIDRs. Ensure that a guest CIDR list is not "
+"overlapped with the VPC's CIDR, or another guest CIDR. The CIDR must be "
+"RFC1918-compliant."
+msgstr "**CIDR列表**: 远端客户子网的CIDR。输入一个CIDR或是以逗号分隔的多个CIDR。在确认客户的CIDR和VPC的CIDR或是另一个客户的CIDR不重叠冲突。CIDR的格式必须符合 RFC1918标准。"
+
+# 929c5f444fae4aee88faa98a926d0f52
+#: ../../networking/remote_access_vpn.rst:322
+msgid ""
+"**IPsec Preshared Key**: Preshared keying is a method where the endpoints of"
+" the VPN share a secret key. This key value is used to authenticate the "
+"customer gateway and the VPC VPN gateway to each other."
+msgstr "**IPsec预共享密钥**: 预共享密钥在两个端点之间共享同一个密钥。这个密钥用来在客户网关和VPN的VPN网关之间相互认证。"
+
+# 171abb6f27ef471eae87fd0718d714af
+#: ../../networking/remote_access_vpn.rst:328
+msgid ""
+"The IKE peers (VPN end points) authenticate each other by computing and "
+"sending a keyed hash of data that includes the Preshared key. If the "
+"receiving peer is able to create the same hash independently by using its "
+"Preshared key, it knows that both peers must share the same secret, thus "
+"authenticating the customer gateway."
+msgstr "Internet密钥交换协议（IKE）匹配点 ( VPN 端点 ) 通过计算并发送包含预共享密钥的哈希键值来进行相互验证。如果收接点通过自己的预共享密钥算出同一个键值的话，这就说明两个点是用的同一个密钥，相互之间认证通过，形成匹配。"
+
+# a4553b53ccb04b358a278545e87eb9bd
+#: ../../networking/remote_access_vpn.rst:335
+msgid ""
+"**IKE Encryption**: The Internet Key Exchange (IKE) policy for phase-1. The "
+"supported encryption algorithms are AES128, AES192, AES256, and 3DES. "
+"Authentication is accomplished through the Preshared Keys."
+msgstr "**IKE 加密**: Internet密钥交换协议(IKE)第一阶段（phase-1）策略。支持的加密算法包括 AES128, AES192, AES256和3DES.。认证通过预共享密钥完成。"
+
+# 3bb40218a4db49e0aa09d5983d57a8fa
+#: ../../networking/remote_access_vpn.rst:341
+msgid ""
+"The phase-1 is the first phase in the IKE process. In this initial "
+"negotiation phase, the two VPN endpoints agree on the methods to be used to "
+"provide security for the underlying IP traffic. The phase-1 authenticates "
+"the two VPN gateways to each other, by confirming that the remote gateway "
+"has a matching Preshared Key."
+msgstr "phase-1是IKE过程的第一阶段。在这个开始的协商阶段，两个VPN端点在将底层IP流量加密安全的方法上取得一致。第一阶段认证通过的条件是：两个VPN网关之间使用的是同一个预定义密钥。"
+
+# a5e3619f28fb487987386ff3359d079b
+#: ../../networking/remote_access_vpn.rst:347
+msgid ""
+"**IKE Hash**: The IKE hash for phase-1. The supported hash algorithms are "
+"SHA1 and MD5."
+msgstr "**IKE 哈希**: IKE第一阶段（ phase-1）哈希散列使用的算法。支持SHA1 和 MD5."
+
+# 998f798e068147c69b96d5332181acdd
+#: ../../networking/remote_access_vpn.rst:350
+msgid ""
+"**IKE DH**: A public-key cryptography protocol which allows two parties to "
+"establish a shared secret over an insecure communications channel. The "
+"1536-bit Diffie-Hellman group is used within IKE to establish session keys. "
+"The supported options are None, Group-5 (1536-bit) and Group-2 (1024-bit)."
+msgstr "**IKE DH（Diffie-Hellman组）**: IKE的DH加密协议，可以在不安全的连接上确保共享KEY的安全。1536位的DH组用在IKE中用来建立会话KEYS。在这里，支持的选项是 None, Group-5 (1536-bit) 和 Group-2 (1024-bit)."
+
+# 34c98169c2dd4375a23dff45d764590d
+#: ../../networking/remote_access_vpn.rst:356
+msgid ""
+"**ESP Encryption**: Encapsulating Security Payload (ESP) algorithm within "
+"phase-2. The supported encryption algorithms are AES128, AES192, AES256, and"
+" 3DES."
+msgstr "**ESP 加密**: 封装安全有效负荷（Encapsulating Security Payload,ESP）算法是发生在第二阶段(phase-2)。其支持的加密算法包括 AES128, AES192, AES256, 和 3DES。"
+
+# c61b40cf82de4f9fb6c45b8e0172b4b4
+#: ../../networking/remote_access_vpn.rst:361
+msgid ""
+"The phase-2 is the second phase in the IKE process. The purpose of IKE "
+"phase-2 is to negotiate IPSec security associations (SA) to set up the IPSec"
+" tunnel. In phase-2, new keying material is extracted from the Diffie-"
+"Hellman key exchange in phase-1, to provide session keys to use in "
+"protecting the VPN data flow."
+msgstr "phase-2是IKE过程的第二阶段，其目标是协助IPSec安全关联 (SA) 以建立IPSec通道。在 phase-2阶段，会利用 phase-1阶段建立好的DH安全协议方法来交换新的密钥。"
+
+# 71d47a66a42f4a04b2540e69eba4cdd9
+#: ../../networking/remote_access_vpn.rst:367
+msgid ""
+"**ESP Hash**: Encapsulating Security Payload (ESP) hash for phase-2. "
+"Supported hash algorithms are SHA1 and MD5."
+msgstr "**ESP哈希散列**:phase-2支持的封装安全有效负荷(Encapsulating Security Payload,ESP)哈希算法包括：SHA1 和MD5."
+
+# 2378eab3a19b42cda0e954ae2c70bb38
+#: ../../networking/remote_access_vpn.rst:370
+msgid ""
+"**Perfect Forward Secrecy**: Perfect Forward Secrecy (or PFS) is the "
+"property that ensures that a session key derived from a set of long-term "
+"public and private keys will not be compromised. This property enforces a "
+"new Diffie-Hellman key exchange. It provides the keying material that has "
+"greater key material life and thereby greater resistance to cryptographic "
+"attacks. The available options are None, Group-5 (1536-bit) and Group-2 "
+"(1024-bit). The security of the key exchanges increase as the DH groups grow"
+" larger, as does the time of the exchanges."
+msgstr "**Perfect forward secrecy(完全正向保密,PFS) **: PFS的性质是确保来自一组的长期的公共密钥和私人密钥之间的会话密钥不会妥协失效。PFS会促使一组新的DH KEY发生交换。这组新KEY具有更长的生命周期因此可以抵制更强大的功击。DH的可用选项是 None, Group-5 (1536-bit)和 Group-2 (1024-bit). 当新KEY交换之后，DH组会变得更大。"
+
+# de12259eb62f48c294bc324395468d43
+#: ../../networking/remote_access_vpn.rst:381
+msgid ""
+"When PFS is turned on, for every negotiation of a new phase-2 SA the two "
+"gateways must generate a new set of phase-1 keys. This adds an extra layer "
+"of protection that PFS adds, which ensures if the phase-2 SA's have expired,"
+" the keys used for new phase-2 SA's have not been generated from the current"
+" phase-1 keying material."
+msgstr "当PFS打开后，两个网关之间的新的phase-2 SA协商都会产生新的phase-1的一组KEY，这就会导致增加一个额外的层。这个层的作用是保证即使phase-2 SA失效过期，其KEY也不会由phase-1生成。"
+
+# c29472e88000476ea8eb3f3165f58da4
+#: ../../networking/remote_access_vpn.rst:387
+msgid ""
+"**IKE Lifetime (seconds)**: The phase-1 lifetime of the security association"
+" in seconds. Default is 86400 seconds (1 day). Whenever the time expires, a "
+"new phase-1 exchange is performed."
+msgstr "**IKE 存活期(秒)**: SA的phase-1的存活期。默认是86400 秒 (1 天).当这个时间过了之后，会发生一次新的 phase-1 KEY交换。"
+
+# c05a91d5e2b44d7a9ea842e762a6f4a0
+#: ../../networking/remote_access_vpn.rst:391
+msgid ""
+"**ESP Lifetime (seconds)**: The phase-2 lifetime of the security association"
+" in seconds. Default is 3600 seconds (1 hour). Whenever the value is "
+"exceeded, a re-key is initiated to provide a new IPsec encryption and "
+"authentication session keys."
+msgstr "**ESP存活期 (秒)**:SA的 phase-2存活期。默认为 3600 秒(1 小时). 当过了这个时间之后，会有一个新的KEY初始化，用来加密和认证 IPsec的会话KEY。"
+
+# 9afba73f17a3471faa8cff978bb64495
+#: ../../networking/remote_access_vpn.rst:396
+msgid ""
+"**Dead Peer Detection**: A method to detect an unavailable Internet Key "
+"Exchange (IKE) peer. Select this option if you want the virtual router to "
+"query the liveliness of its IKE peer at regular intervals. It's recommended "
+"to have the same configuration of DPD on both side of VPN connection."
+msgstr "**死亡匹配点检测**:这是一种检测不可用IKE节点的方法。如果你希望虚拟路由器随时测试IKE节点的存活情况，选择了这个选项。 一般来说，最好在VPN连接的两端都同时配置DPD(Dead Peer Detectio)."
+
+# 4d12f59b777c48e98fb18ab2bace355d
+# a65f0ba427b04b6da2bdc39a05acba02
+#: ../../networking/remote_access_vpn.rst:402
+#: ../../networking/remote_access_vpn.rst:425
+msgid "Click OK."
+msgstr "点击确定。"
+
+# 460983ec4dd64370b650944e21d45b75
+#: ../../networking/remote_access_vpn.rst:406
+msgid "Updating and Removing a VPN Customer Gateway"
+msgstr "更新和删除一个VPN客户网关."
+
+# 47640086ca6e4122a862027f6e528af6
+#: ../../networking/remote_access_vpn.rst:408
+msgid ""
+"You can update a customer gateway either with no VPN connection, or related "
+"VPN connection is in error state."
+msgstr "你可以更新一个客户网关：即可以从无到有新建一个VPN，或是将有错误提示的VPN改正。"
+
+# eee4a55897da4f06b44795327c878110
+#: ../../networking/remote_access_vpn.rst:417
+msgid "Select the VPN customer gateway you want to work with."
+msgstr "选择您要操作的客户VPN连接。"
+
+# 9dc617447a9c48df92819b996a8e3b39
+#: ../../networking/remote_access_vpn.rst:419
+msgid ""
+"To modify the required parameters, click the Edit VPN Customer Gateway "
+"button |vpn-edit-icon.png|"
+msgstr ""
+
+# 0c3c4beedfb2453cb03958649454d3d2
+#: ../../networking/remote_access_vpn.rst:422
+msgid ""
+"To remove the VPN customer gateway, click the Delete VPN Customer Gateway "
+"button |delete.png|"
+msgstr "删除一个客户VPN网关，点击删除客户VPN网关按钮。 |delete.png|"
+
+# ae45fd8564384b9a8682a662011196da
+#: ../../networking/remote_access_vpn.rst:429
+msgid "Creating a VPN gateway for the VPC"
+msgstr "为VPC创建一个VPN网关"
+
+# addf23d2b2b14d9c80370bc70f64ec94
+# 8ab2d3e53e83433ab4cf699e916d89d9
+# 5ece94a59df34ecdb036ac45fc49bd06
+#: ../../networking/remote_access_vpn.rst:440
+#: ../../networking/remote_access_vpn.rst:501
+#: ../../networking/remote_access_vpn.rst:633
+msgid ""
+"Click the Configure button of the VPC to which you want to deploy the VMs."
+msgstr "点击要部署虚机的VPC的配置按钮。"
+
+# af1a9268a6da4a45922589c847776234
+# 1ccf3bf911414951aeb77508e82aa992
+# 433faedb39a3413c8ce1f220f5e22560
+#: ../../networking/remote_access_vpn.rst:443
+#: ../../networking/remote_access_vpn.rst:504
+#: ../../networking/remote_access_vpn.rst:636
+msgid ""
+"The VPC page is displayed where all the tiers you created are listed in a "
+"diagram."
+msgstr "系统会显示VPC页面，您创建的所有层都列在图中。"
+
+# 3152bcd237704f96b4a1b897b801f81b
+# 5a72231d602e4625acd0cbd4b0af4f7e
+# 243047505a8c40e1aadfa9dfbc091f0c
+#: ../../networking/remote_access_vpn.rst:468
+#: ../../networking/remote_access_vpn.rst:531
+#: ../../networking/remote_access_vpn.rst:663
+msgid "Select Site-to-Site VPN."
+msgstr "选择点对点VPN"
+
+# 626b08a7444c4baeb387b316fcf8921d
+#: ../../networking/remote_access_vpn.rst:470
+msgid ""
+"If you are creating the VPN gateway for the first time, selecting Site-to-"
+"Site VPN prompts you to create a VPN gateway."
+msgstr "如果您是第一次创建VPN网关，选择点对点VPN会提示您创建一个VPN网关。"
+
+# c46b3f642ec240738664d6765c1d736f
+#: ../../networking/remote_access_vpn.rst:473
+msgid "In the confirmation dialog, click Yes to confirm."
+msgstr "在信息确认对话框，点击“是”。"
+
+# 6dbf5c6dc5984bc896785e8d81f1fa0d
+#: ../../networking/remote_access_vpn.rst:475
+msgid ""
+"Within a few moments, the VPN gateway is created. You will be prompted to "
+"view the details of the VPN gateway you have created. Click Yes to confirm."
+msgstr "过一会儿，VPN网关就创建出来了。系统会提示您查看VPN网关的详细信息，请点击“是”。"
+
+# 62c9ff637a9c46beb4a187d9d333e711
+#: ../../networking/remote_access_vpn.rst:479
+msgid "The following details are displayed in the VPN Gateway page:"
+msgstr "VPN网关页面会显示以下详细信息："
+
+# 202a6b9a51f3470d89bb84bb2c9579a8
+# 47435eb81ccf40eab149e9b0abb9213e
+#: ../../networking/remote_access_vpn.rst:481
+#: ../../networking/remote_access_vpn.rst:561
+msgid "IP Address"
+msgstr "IP地址"
+
+# 46f2ea07f3744ac381add8029488f5d3
+#: ../../networking/remote_access_vpn.rst:483
+msgid "Account"
+msgstr "帐号"
+
+# bad02846a1ee4160a278abb51303de1f
+#: ../../networking/remote_access_vpn.rst:485
+msgid "Domain"
+msgstr "域名"
+
+# b0b08d6daddb48409f581811786b76cf
+#: ../../networking/remote_access_vpn.rst:489
+msgid "Creating a VPN Connection"
+msgstr "新建vpn连接"
+
+# 596c1d39f0fe47fa8b05ff9b321ae507
+#: ../../networking/remote_access_vpn.rst:491
+msgid "CloudStack supports creating up to 8 VPN connections."
+msgstr "CloudStack最多支持建立8个VPN连接。"
+
+# a61e029b8b514adfa93c97620ffff95f
+#: ../../networking/remote_access_vpn.rst:499
+msgid "All the VPCs that you create for the account are listed in the page."
+msgstr "页面上列出了该账号下所有的VPC。"
+
+# 690702b545754083adec40f20d69acb4
+# 614430ff17c8485fae7ddb094273ef06
+#: ../../networking/remote_access_vpn.rst:507
+#: ../../networking/remote_access_vpn.rst:639
+msgid "Click the Settings icon."
+msgstr "点击设置图标。"
+
+# 86dbf74b2c6e4f0aab3f252fafd89f2c
+# fab72af09a284fd2800ff51645f071bf
+#: ../../networking/remote_access_vpn.rst:533
+#: ../../networking/remote_access_vpn.rst:665
+msgid "The Site-to-Site VPN page is displayed."
+msgstr "系统会显示点对点VPN页面。"
+
+# db4dc2719dd6405eb250f62908eef010
+# 207bfc2acd9e434887770513a245873b
+#: ../../networking/remote_access_vpn.rst:535
+#: ../../networking/remote_access_vpn.rst:667
+msgid ""
+"From the Select View drop-down, ensure that VPN Connection is selected."
+msgstr "在选择视图下拉框，请确保选择VPN连接。"
+
+# 950eac49657f4a29a9fba1b973577867
+#: ../../networking/remote_access_vpn.rst:538
+msgid "Click Create VPN Connection."
+msgstr "选择创建vpn连接按钮"
+
+# 916fc10dd39346ada9828e3a2a80ffda
+#: ../../networking/remote_access_vpn.rst:540
+msgid "The Create VPN Connection dialog is displayed:"
+msgstr "系统会显示创建VPN连接对话框："
+
+# 87888fff4a5f4664be5c4c03fc2ecf6a
+#: ../../networking/remote_access_vpn.rst:542
+msgid "|createvpnconnection.png|"
+msgstr "|createvpnconnection.png|"
+
+# 4b6cc407b8bc4a728fb3328f0ce53f3f
+#: ../../networking/remote_access_vpn.rst:544
+msgid "Select the desired customer gateway."
+msgstr "选择想要的用户网关。"
+
+# 6776ab8d9fad4c2d8956d78ff11ab998
+#: ../../networking/remote_access_vpn.rst:546
+msgid ""
+"Select Passive if you want to establish a connection between two VPC virtual"
+" routers."
+msgstr "如果你希望在两个VPC虚拟路由器之间建立连接，选择被动模式。"
+
+# 513eee2d7f8745a4b338c8ea142fae05
+#: ../../networking/remote_access_vpn.rst:549
+msgid ""
+"If you want to establish a connection between two VPC virtual routers, "
+"select Passive only on one of the VPC virtual routers, which waits for the "
+"other VPC virtual router to initiate the connection. Do not select Passive "
+"on the VPC virtual router that initiates the connection."
+msgstr "如果你希望在两个VPC虚拟路由器之间建立连接，需要等待另一个虚拟路由器来初始化连接，则只有其中一个虚拟器上选择被动模式。在这种情况下，不要在初始化连接的虚拟路由器上选择被动模式。"
+
+# dd03407d4f064ec99ea68bb066d2289e
+#: ../../networking/remote_access_vpn.rst:555
+msgid "Click OK to confirm."
+msgstr "点击确定。"
+
+# d4c274e9cecb44bcad1ba67ed65069e4
+#: ../../networking/remote_access_vpn.rst:557
+msgid "Within a few moments, the VPN Connection is displayed."
+msgstr "过一会儿，系统会显示该VPN连接。"
+
+# 42dd7918225d458f980e458924b262f3
+#: ../../networking/remote_access_vpn.rst:559
+msgid "The following information on the VPN connection is displayed:"
+msgstr "VPN连接信息"
+
+# 64fdbdcdfac148dea0883db2615bf0ed
+#: ../../networking/remote_access_vpn.rst:563
+msgid "Gateway"
+msgstr "网关"
+
+# 8ac547f2f1574131adc8c69d4e3c30ef
+#: ../../networking/remote_access_vpn.rst:565
+msgid "State"
+msgstr "状态 "
+
+# d2a5bd51a6e347e89857750706114fc9
+#: ../../networking/remote_access_vpn.rst:567
+msgid "IPSec Preshared Key"
+msgstr "IPSec 预共享密钥"
+
+# ccfea0cb9ae34777990aa348b7a9c23f
+#: ../../networking/remote_access_vpn.rst:569
+msgid "IKE Policy"
+msgstr "IKE策略"
+
+# bc29ecfda06848f78a8cc694b3f6d47b
+#: ../../networking/remote_access_vpn.rst:571
+msgid "ESP Policy"
+msgstr "ESP策略"
+
+# 57cee5dc2eed4f6a9164c4838ebdc9d6
+#: ../../networking/remote_access_vpn.rst:575
+msgid "Site-to-Site VPN Connection Between VPC Networks"
+msgstr "在VPC网络之间的站点的VPN连接"
+
+# d8f9f929fafd40e6895122549b022754
+#: ../../networking/remote_access_vpn.rst:577
+msgid ""
+"CloudStack provides you with the ability to establish a site-to-site VPN "
+"connection between CloudStack virtual routers. To achieve that, add a "
+"passive mode Site-to-Site VPN. With this functionality, users can deploy "
+"applications in multiple Availability Zones or VPCs, which can communicate "
+"with each other by using a secure Site-to-Site VPN Tunnel."
+msgstr "CloudStack可以在虚拟路由器之间部署站点到站点的VPN连接，这需要添加一个被动模式的站点到站点VPN。有了这个功能之后，用户就可以在多个区域或VPC之间通过安全的VPN通道互联。"
+
+# 2fb087843cd04fafa3beba95a3ae2af1
+#: ../../networking/remote_access_vpn.rst:583
+msgid "This feature is supported on all the hypervisors."
+msgstr "这个特性支持所有类型的HYPERVISOR."
+
+# 217a4da322cc4f8caa7e04c029779c8b
+#: ../../networking/remote_access_vpn.rst:585
+msgid "Create two VPCs. For example, VPC A and VPC B."
+msgstr "创建两个VPC。比如，VPC A和VPC B。"
+
+# a78d89e3621346c8a11277927e8dc502
+#: ../../networking/remote_access_vpn.rst:587
+msgid "For more information, see \":ref:`configuring-vpc`\"."
+msgstr "更多信息，参考\":ref:`configuring-vpc`\"."
+
+# 09b752dc4d4e4cd29912fcbe352309fa
+#: ../../networking/remote_access_vpn.rst:589
+msgid "Create VPN gateways on both the VPCs you created."
+msgstr "在创建的VPC两边都添加VPN网关。"
+
+# b9af87b346ef40889104b5a1f40c7702
+#: ../../networking/remote_access_vpn.rst:591
+msgid ""
+"For more information, see `\"Creating a VPN gateway for the VPC\" "
+"<#creating-a-vpn-gateway-for-the-vpc>`_."
+msgstr "更多信息，参考 `\"为VPC创建VPN网关\" <#creating-a-vpn-gateway-for-the-vpc>`_."
+
+# 29d8db01114c458e8d855996c22e0664
+#: ../../networking/remote_access_vpn.rst:594
+msgid "Create VPN customer gateway for both the VPCs."
+msgstr "在VPC两边都创建VPN客户网关。"
+
+# 1a50b7ef681f4cb48c15d30e08dfd1e7
+#: ../../networking/remote_access_vpn.rst:596
+msgid ""
+"For more information, see `\"Creating and Updating a VPN Customer Gateway\" "
+"<#creating-and-updating-a-vpn-customer-gateway>`_."
+msgstr "更多信息，参考`\"创建和更新VPN客户网关\" <#creating-and-updating-a-vpn-customer-gateway>`_."
+
+# c9013d4ec4c74444a40bf745ae0a5544
+#: ../../networking/remote_access_vpn.rst:599
+msgid "Enable a VPN connection on VPC A in passive mode."
+msgstr "在VPC A这边启用VPN的被动连接模式。"
+
+# 8fb700491eeb4156a1c7549d81a78346
+#: ../../networking/remote_access_vpn.rst:601
+msgid ""
+"For more information, see `\"Creating a VPN Connection\" <#creating-a-vpn-"
+"connection>`_."
+msgstr "更多信息，请参阅 `\"创建VPN连接\" <#creating-a-vpn-connection>`_。"
+
+# e8dd1dd51dd34f57ac10161220734be4
+#: ../../networking/remote_access_vpn.rst:604
+msgid ""
+"Ensure that the customer gateway is pointed to VPC B. The VPN connection is "
+"shown in the Disconnected state."
+msgstr "确保客户网关指向VPC B。这个VPN当前显示的是未连接状态。"
+
+# eca76af9d9304b17982a0bb977a12547
+#: ../../networking/remote_access_vpn.rst:607
+msgid "Enable a VPN connection on VPC B."
+msgstr "在VPC B上启用VPN连接。"
+
+# 79e9417cc7294b70bd95236d9c2c80ac
+#: ../../networking/remote_access_vpn.rst:609
+msgid ""
+"Ensure that the customer gateway is pointed to VPC A. Because virtual router"
+" of VPC A, in this case, is in passive mode and is waiting for the virtual "
+"router of VPC B to initiate the connection, VPC B virtual router should not "
+"be in passive mode."
+msgstr "确保客户网关指向VPC A。在这个示例里，因为VPC A的虚拟路由器是处于被动模式且等待着VPC B进行初始化连接，所以VPC B的虚拟路由器不要设置为被动模式。"
+
+# cf0657024acb43ea8028262bf74a9848
+#: ../../networking/remote_access_vpn.rst:614
+msgid "The VPN connection is shown in the Disconnected state."
+msgstr "VPN连接当前显示为未连接状态。"
+
+# 4c18218889914f65b2fe355d4568b407
+#: ../../networking/remote_access_vpn.rst:616
+msgid ""
+"Creating VPN connection on both the VPCs initiates a VPN connection. Wait "
+"for few seconds. The default is 30 seconds for both the VPN connections to "
+"show the Connected state."
+msgstr "VPC两边的VPN会进行初始化连接。默认为30秒之后，两边VPN都会显示为已连接状态。"
+
+# 84118e99c0b14f49b14160c3975dad17
+#: ../../networking/remote_access_vpn.rst:622
+msgid "Restarting and Removing a VPN Connection"
+msgstr "VPN连接的重启和删除"
+
+# 090940869ab44e80b8e9c4ea04fa48ec
+#: ../../networking/remote_access_vpn.rst:670
+msgid "All the VPN connections you created are displayed."
+msgstr "系统会显示创建VPN连接对话框："
+
+# b921e72e9ca74e75b9c515a87f105b9a
+#: ../../networking/remote_access_vpn.rst:672
+msgid "Select the VPN connection you want to work with."
+msgstr "选择您要操作的VPN连接。"
+
+# 2387d86e243f469f84a0cee989324610
+#: ../../networking/remote_access_vpn.rst:674
+msgid "The Details tab is displayed."
+msgstr "系统显示详细信息页。"
+
+# 345c5bfe23d84fd09f56e0e34de09e29
+#: ../../networking/remote_access_vpn.rst:676
+msgid ""
+"To remove a VPN connection, click the Delete VPN connection button |remove-"
+"vpn.png|"
+msgstr "删除一个VPN连接，点击删除VPN连接按钮。 |remove-vpn.png|"
+
+# 8d1a3cf378554f51a5702b0710c331f2
+#: ../../networking/remote_access_vpn.rst:679
+msgid ""
+"To restart a VPN connection, click the Reset VPN connection button present "
+"in the Details tab. |reset-vpn.png|"
+msgstr "要重启VPN连接，请点击详细信息页的重置VPN连接按钮。 |reset-vpn.png|"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/security_groups.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/security_groups.mo
new file mode 100644
index 0000000..fc17470
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/security_groups.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/security_groups.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/security_groups.po
new file mode 100644
index 0000000..3105cce
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/security_groups.po
@@ -0,0 +1,366 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# b67087ae536e4b77ac5668f8f3f73ba8
+#: ../../networking/security_groups.rst:18
+msgid "Security Groups"
+msgstr "安全组"
+
+# 1397d3fadf7d45779a890fb7156cf142
+#: ../../networking/security_groups.rst:21
+msgid "About Security Groups"
+msgstr "关于安全组"
+
+# 965e0935679141b0bc89e0d82dc1cff8
+#: ../../networking/security_groups.rst:23
+msgid ""
+"Security groups provide a way to isolate traffic to VMs. 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. Security groups are particularly useful in zones that use basic "
+"networking, because there is a single guest network for all guest VMs. In "
+"advanced zones, security groups are supported only on the KVM hypervisor."
+msgstr "安全组提供一种方法来隔离VMs流量。一个安全组是一组依照设置名为入口规则和出口规则来过滤他们进出流量的VMs，这些规则依靠与VM通讯的IP地址来过滤网络流量。安全组在使用基础网络的zones中尤为重要，因为这里只有一个来宾网络。在高级zones中，只有KVM hypervisor支持安全组。"
+
+# 7cc1c024596546c4837b5e09cef7f7db
+#: ../../networking/security_groups.rst:33
+msgid ""
+"In a zone that uses advanced networking, you can instead define multiple "
+"guest networks to isolate traffic to VMs."
+msgstr "在一个使用高级网络的zone中，你可以改为定义多个来宾网络隔离流量至VMs。"
+
+# bd8429af9a564cd398104231d1bfc2d9
+#: ../../networking/security_groups.rst:36
+msgid ""
+"Each CloudStack account comes with a default security group that denies all "
+"inbound traffic and allows all outbound traffic. The default security group "
+"can be modified so that all new VMs inherit some other desired set of rules."
+msgstr "每个CloudStack账号匹配一个拒绝所有入站流量和允许所有出口流量的默认安全组 。可以编辑默认的安全组以便所有新VMs的策略继承一些的想要的设置。"
+
+# 3eb3f0e93cf04d8a9c2a967e8ff3a11c
+#: ../../networking/security_groups.rst:41
+msgid ""
+"Any CloudStack user can set up any number of additional security groups. "
+"When a new VM is launched, it is assigned to the default security group "
+"unless another user-defined security group is specified. A VM can be a "
+"member of any number of security groups. Once a VM is assigned to a security"
+" group, it remains in that group for its entire lifetime; you can not move a"
+" running VM from one security group to another."
+msgstr "任何CloudStack用户可以增加任意数量的安全组。当一个新的VM运行起来的时候，它会被添加到默认安全组除非其他用户指定了其他安全组。一个VM可以是任何安全组的成员。一旦VM被添加到一个安全组，它会继承这个组的生命周期；你不能移动一台正在运行的VM到其他安全组。"
+
+# 1d91c7babdd54f38b62e9e65788a8a7c
+#: ../../networking/security_groups.rst:48
+msgid ""
+"You can modify a security group by deleting or adding any number of ingress "
+"and egress rules. When you do, the new rules apply to all VMs in the group, "
+"whether running or stopped."
+msgstr "你可以通过删除或添加任意的入口和出口策略来修改一个安全组。当你这么做的时候，新的策略会应用到组中的所有VMs，无论是运行的还是关机的。"
+
+# f705f2a195b240f49ffc0cbe9aaa253a
+#: ../../networking/security_groups.rst:52
+msgid ""
+"If no ingress rules are specified, then no traffic will be allowed in, "
+"except for responses to any traffic that has been allowed out through an "
+"egress rule."
+msgstr "如果没有指定入口规则，那么流量会被禁止，除了已经允许通过一个出口规则响应任何流量 。"
+
+# 7fa1798aea704a55b545171eb64a16bd
+#: ../../networking/security_groups.rst:58
+msgid "Adding a Security Group"
+msgstr "添加一个安全组"
+
+# f7cc763899ad4df99b9e927ef37eabb4
+#: ../../networking/security_groups.rst:60
+msgid "A user or administrator can define a new security group."
+msgstr "一个用户或者管理员能定义一个新的安全组。"
+
+# a026f1875e7f4cec8447b013bf2d7a78
+# 27e30ee65cbe485bb8e7370a38b75281
+#: ../../networking/security_groups.rst:62
+#: ../../networking/security_groups.rst:124
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# 344ee6a79a674e88a4a61b24b0a01b42
+#: ../../networking/security_groups.rst:64
+msgid "In the left navigation, choose Network."
+msgstr "在左侧的导航栏，选择网络。"
+
+# 07579af87ecd4f1d8bd6e66835cb2958
+#: ../../networking/security_groups.rst:66
+msgid "In Select view, choose Security Groups."
+msgstr "在选择视图中，选择安全组。"
+
+# 23507439460f427cb5be523f65e254fb
+#: ../../networking/security_groups.rst:68
+msgid "Click Add Security Group."
+msgstr "点击添加安全组。"
+
+# a530b7d59d194fb18081a92d396a272a
+#: ../../networking/security_groups.rst:70
+msgid "Provide a name and description."
+msgstr "提供一个名称和描述。"
+
+# 237fc184482448589b8a2eb7c3c70e76
+#: ../../networking/security_groups.rst:72
+msgid "Click OK."
+msgstr "点击确定。"
+
+# 34ea82240e9c456ab55ff2f0d5756566
+#: ../../networking/security_groups.rst:74
+msgid "The new security group appears in the Security Groups Details tab."
+msgstr "新的安全组出现在安全组详细信息标签中。"
+
+# df20adfc9c2e43b9b56c6f1119a9d73f
+#: ../../networking/security_groups.rst:76
+msgid ""
+"To make the security group useful, continue to Adding Ingress and Egress "
+"Rules to a Security Group."
+msgstr "要使安全组生效，继续给这个安全组添加入口和出口策略。"
+
+# 0a506fc7186b4a0c8a15ae463c4793e1
+#: ../../networking/security_groups.rst:81
+msgid "Security Groups in Advanced Zones (KVM Only)"
+msgstr "高级区域中的安全组（只针对KVM）"
+
+# b2a6fb8be2384189ae73c2430ce94159
+#: ../../networking/security_groups.rst:83
+msgid ""
+"CloudStack provides the ability to use security groups to provide isolation "
+"between guests on a single shared, zone-wide network in an advanced zone "
+"where KVM is the hypervisor. Using security groups in advanced zones rather "
+"than multiple VLANs allows a greater range of options for setting up guest "
+"isolation in a cloud."
+msgstr "以KVM作为虚拟机时，在单共享广域的网络内，CloudStack可以通过安全组来隔离客户。通过使用安全组而不是多VLAN，可以在云中隔离客户时具有更高的灵活性"
+
+# 180782afad3643f1ba9672b7f6da72b3
+#: ../../networking/security_groups.rst:91
+msgid "Limitations"
+msgstr "局限性"
+
+# 133ba38a19484e2e9122631ab38446fa
+#: ../../networking/security_groups.rst:93
+msgid "The following are not supported for this feature:"
+msgstr "下列不支持此功能："
+
+# 7c46f4b3ab9f405b8ba2b599ffc1985e
+#: ../../networking/security_groups.rst:95
+msgid ""
+"Two IP ranges with the same VLAN and different gateway or netmask in "
+"security group-enabled shared network."
+msgstr "在开启了安全组的共享网络内，同一VLAN内具有不同网关或掩码的二个IP范围，"
+
+# 25d83dec92f045bda786a85257b3e1d1
+#: ../../networking/security_groups.rst:98
+msgid ""
+"Two IP ranges with the same VLAN and different gateway or netmask in "
+"account-specific shared networks."
+msgstr "在共享网络的特殊帐户内，同一VLAN内具有不同网关或掩码的二个IP范围"
+
+# 529f72b64c464f0cbbe8b287e8258f1a
+#: ../../networking/security_groups.rst:101
+msgid "Multiple VLAN ranges in security group-enabled shared network."
+msgstr "在开启了安全组共享网络的多VLAN范围"
+
+# c9ffb5f82e6b45778e4e1b83b29ed310
+#: ../../networking/security_groups.rst:103
+msgid "Multiple VLAN ranges in account-specific shared networks."
+msgstr "在共享网络的特殊帐户内，多个VLAN范围"
+
+# 8488c958047d450bb250b38d098bc214
+#: ../../networking/security_groups.rst:105
+msgid ""
+"Security groups must be enabled in the zone in order for this feature to be "
+"used."
+msgstr "为使用此特性，在区域内必须开启安全组"
+
+# 6c5be222e8184b8ab28d3019648e9990
+#: ../../networking/security_groups.rst:110
+msgid "Enabling Security Groups"
+msgstr "开启安全组"
+
+# b6b2af559254408ba42336e7fddf32e6
+#: ../../networking/security_groups.rst:112
+msgid ""
+"In order for security groups to function in a zone, the security groups "
+"feature must first be enabled for the zone. The administrator can do this "
+"when creating a new zone, by selecting a network offering that includes "
+"security groups. The procedure is described in Basic Zone Configuration in "
+"the Advanced Installation Guide. The administrator can not enable security "
+"groups for an existing zone, only when creating a new zone."
+msgstr "使用安全组功能之前，必须先在Zone中启用安全组功能。系统管理员可以在创建一个新的Zone时，通过选择带‘安全组’功能的网络方案进行启用。在高级安装指南的基本Zone配置中有该过程的详细描述。系统管理员不能对现有Zone启用安全组，只能在新建Zone时启用。"
+
+# e09d51e1a259488eab79d1fb28954b59
+#: ../../networking/security_groups.rst:122
+msgid "Adding Ingress and Egress Rules to a Security Group"
+msgstr "对安全组添加入口出口规则"
+
+# b24e5ca705b84ea4a6c0511ef2244936
+#: ../../networking/security_groups.rst:126
+msgid "In the left navigation, choose Network"
+msgstr "在左侧的导航栏，选择网络"
+
+# e6e52ad277a249ebb052f48c14687e98
+#: ../../networking/security_groups.rst:128
+msgid ""
+"In Select view, choose Security Groups, then click the security group you "
+"want."
+msgstr ""
+
+# 4563cb9609194e7b8bfe401fa3b6219e
+#: ../../networking/security_groups.rst:131
+msgid ""
+"To add an ingress rule, click the Ingress Rules tab and fill out the "
+"following fields to specify what network traffic is allowed into VM "
+"instances in this security group. If no ingress rules are specified, then no"
+" traffic will be allowed in, except for responses to any traffic that has "
+"been allowed out through an egress rule."
+msgstr "为增加入口规则，点击入口规则并填写相应内容，以说明在此安全组内何种网络流量可以到达虚拟机实例。如果没有说明入口规则，则不会允许流量进入。也就只有出口规允许的流量了。"
+
+# a4934e5b794b41469ff66677df530f64
+#: ../../networking/security_groups.rst:137
+msgid ""
+"**Add by CIDR/Account**. Indicate whether the source of the traffic will be "
+"defined by IP address (CIDR) or an existing security group in a CloudStack "
+"account (Account). Choose Account if you want to allow incoming traffic from"
+" all VMs in another security group"
+msgstr "**通过CIDR帐户添加**. 表明在CloudStack帐户中是否有CIDR定义的流量来源或是已存在的安全组。如果允许来自另一安全组的所有虚拟机的流量进入，则添加此帐户。"
+
+# 38c863d52b6c4f3b900f9268d71a3167
+#: ../../networking/security_groups.rst:143
+msgid ""
+"**Protocol**. The networking protocol that sources will use to send traffic "
+"to the security group. TCP and UDP are typically used for data exchange and "
+"end-user communications. ICMP is typically used to send error messages or "
+"network monitoring data."
+msgstr "**协议**. 发送源会使用网络协议来发送流量到安全组。TCP和UDP是典型的二种用来数据交换和终端用户交流的协议。ICMP则用来发送错误信息或网络监控数据"
+
+# bcb96d430c8649f483335f10c670e649
+#: ../../networking/security_groups.rst:148
+msgid ""
+"**Start Port, End Port**. (TCP, UDP only) A range of listening ports that "
+"are the destination for the incoming traffic. If you are opening a single "
+"port, use the same number in both fields."
+msgstr "**开始端口，结束端口**. (仅对TCP，UDP)。目的地为进入流量而设的监听端口范围。如果仅开放了单个端口，则在两者的区域中用同一端口。"
+
+# 6c1ac4c3fb7e476a8eba891bbf1fa14e
+#: ../../networking/security_groups.rst:152
+msgid ""
+"**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code "
+"that will be accepted."
+msgstr "**ICMP类型，ICMP编码**. (仅对ICMP)。接受的信息及错误码的类型。"
+
+# 6d982263975e486e8e1b13fe56a83ed0
+#: ../../networking/security_groups.rst:155
+msgid ""
+"**CIDR**. (Add by CIDR only) To accept only traffic from 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 incoming traffic. For example,"
+" 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr "**CIDR**. (仅通过CIDR添加)。为接受来来自特殊地址块的流量，输入一个CIDR，多个时用逗号隔开。CIDR是进入流量的基础IP地址。例如：192.168.0.0/22，为允许所有CIDR，请设为0.0.0.0/0"
+
+# 10e7f63d3cf94152a51416bc737199ed
+#: ../../networking/security_groups.rst:161
+msgid ""
+"**Account, Security Group**. (Add by Account only) To accept only traffic "
+"from another security group, enter the CloudStack account and name of a "
+"security group that has already been defined in that account. To allow "
+"traffic between VMs within the security group you are editing now, enter the"
+" same name you used in step 7."
+msgstr "**帐户，安全组**. (仅通过帐户添加)。为接受来自另一安全组的流量，输入一个CloudStack帐户和在此帐户中已经定义的安全组的名字。为允许你正在编辑的安全组内虚拟机之间的流量，输入你在第7步使用的相同的名字。"
+
+# 9d70746377c24fdb80bdb73145dda1fe
+#: ../../networking/security_groups.rst:167
+msgid "The following example allows inbound HTTP access from anywhere:"
+msgstr "下面这个例子允许内部任何地方的HTTP访问"
+
+# f1fa895a70e745a182f076db946d9d16
+#: ../../networking/security_groups.rst:169
+msgid "|httpaccess.png|"
+msgstr "|httpaccess.png|"
+
+# 25c1f9eee689482ab0a99049e45c6ceb
+#: ../../networking/security_groups.rst:171
+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 security group. If no egress rules are specified, then all"
+" traffic will be allowed out. Once egress rules are specified, the following"
+" types of traffic are allowed out: traffic specified in egress rules; "
+"queries to DNS and DHCP servers; and responses to any traffic that has been "
+"allowed in through an ingress rule"
+msgstr "为添加一个出口规则，点击出口规则并填写以下内容，以说明在此安全组内的虚拟机，被允许哪一类型的流量送出。如果出口规则没有说明，所以的流量都被允许出去一旦进行了说明，则以下流量可以允许出去：在出口规则中进行说明的，查询DNS和DHCP服务器的，响应来自入口规则允许进入的流量的"
+
+# 83bfb97418d545549c3ea5c0a17c5985
+#: ../../networking/security_groups.rst:180
+msgid ""
+"**Add by CIDR/Account**. Indicate whether the destination of the traffic "
+"will be defined by IP address (CIDR) or an existing security group in a "
+"CloudStack account (Account). Choose Account if you want to allow outgoing "
+"traffic to all VMs in another security group."
+msgstr "**通过CIDR帐户添加**. 表明流量目的地是否已通过IP地址(CIDR)定义或是CloudStack帐户(Account)内存在的安全组。选择帐户，以允许流量到其安全组内所有虚拟机"
+
+# f175b78e34494795b301760a7fd5168f
+#: ../../networking/security_groups.rst:186
+msgid ""
+"**Protocol**. The networking protocol that VMs will use to send outgoing "
+"traffic. TCP and UDP are typically used for data exchange and end-user "
+"communications. ICMP is typically used to send error messages or network "
+"monitoring data."
+msgstr "**协议**. 虚拟机发送流量需要的协议。TCP和UDP是典型的二种用来数据交换和终端用户交流的协议。ICMP则用来发送错误信息或网络监控数据"
+
+# 31089018bb9f47e4941651c91b2bd90c
+#: ../../networking/security_groups.rst:191
+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 "**开始端口，结束端口**. (仅对TCP，UDP) 。目的地为进入流量而设的监听端口范围。如果仅开放了单个端口，则在两者的区域中用同一端口。"
+
+# 96661f61b9b54d448e5e7be7ba933296
+#: ../../networking/security_groups.rst:195
+msgid ""
+"**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code "
+"that will be sent"
+msgstr "**ICMP类型，ICMP编码**. (仅对ICMP) 。信息及错误码的类型。"
+
+# 7e52dd9e52524ea98f0bcf7ff00116ac
+#: ../../networking/security_groups.rst:198
+msgid ""
+"**CIDR**. (Add by CIDR only) To send traffic only to 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 "**CIDR**. (仅通过CIDR添加) 。为接受来来自特殊地址块的流量，输入一个CIDR，多个时用逗号隔开。CIDR是进入流量的基础IP地址。例如：192.168.0.0/22，为允许所有CIDR，请设为0.0.0.0/0"
+
+# 40e0b1515ef948adb1a42642f73f490d
+#: ../../networking/security_groups.rst:204
+msgid ""
+"**Account, Security Group**. (Add by Account only) To allow traffic to be "
+"sent to another security group, enter the CloudStack account and name of a "
+"security group that has already been defined in that account. To allow "
+"traffic between VMs within the security group you are editing now, enter its"
+" name."
+msgstr "**帐户，安全组**. (仅通过帐户添加) 。为接受来自另一安全组的流量，输入一个CloudStack帐户和在此帐户中已经定义的安全组的名字。为允许你正在编辑的安全组内虚拟机之间的流量，输入名字。"
+
+# 39febf06883a4d248d1ac5ad19510065
+#: ../../networking/security_groups.rst:210
+msgid "Click Add."
+msgstr "点击 添加"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/static_nat.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/static_nat.mo
new file mode 100644
index 0000000..d175f14
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/static_nat.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/static_nat.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/static_nat.po
new file mode 100644
index 0000000..4407395
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/static_nat.po
@@ -0,0 +1,95 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 89295dfc645a421eac4401834f1b5564
+#: ../../networking/static_nat.rst:18
+msgid "Static NAT"
+msgstr "静态 NAT"
+
+# c3b2d053fab944578298ac1adf46e76e
+#: ../../networking/static_nat.rst:20
+msgid ""
+"A static NAT rule maps a public IP address to the private IP address of a VM"
+" in order to allow Internet traffic into the VM. The public IP address "
+"always remains the same, which is why it is called static NAT. This section "
+"tells how to enable or disable static NAT for a particular IP address."
+msgstr ""
+
+# ffe605639e6844fa8170c65805372b4c
+#: ../../networking/static_nat.rst:28
+msgid "Enabling or Disabling Static NAT"
+msgstr "启用或禁用静态NAT"
+
+# 311e1bb870dd43bb98cd7ee6a01f42ca
+#: ../../networking/static_nat.rst:30
+msgid ""
+"If port forwarding rules are already in effect for an IP address, you cannot"
+" enable static NAT to that IP."
+msgstr "如果该公网IP上已经有端口转发规则，则不允许再启用静态NAT。"
+
+# b89fc2e081874b24b0ad50ed843837e9
+#: ../../networking/static_nat.rst:33
+msgid ""
+"If a guest VM is part of more than one network, static NAT rules will "
+"function only if they are defined on the default network."
+msgstr "如果用户VM存在多个网络，则静态NAT规则仅在默认网络上定义时生效。"
+
+# e6dabe6070464d23926137799673505a
+#: ../../networking/static_nat.rst:36
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# 726614a43cbf4c448770c40822676059
+#: ../../networking/static_nat.rst:38
+msgid "In the left navigation, choose Network."
+msgstr "在左侧的导航栏，选择网络。"
+
+# 71505d3318714907a3abd5319833b78e
+#: ../../networking/static_nat.rst:40
+msgid "Click the name of the network where you want to work with."
+msgstr "点击拟修改的网络名称。"
+
+# 0898722d18384a89a217a7a8e7cb6fbf
+#: ../../networking/static_nat.rst:42
+msgid "Click View IP Addresses."
+msgstr "点击查看IP地址。"
+
+# 5e916ccbf7c94237b104827f38f2ca6a
+#: ../../networking/static_nat.rst:44
+msgid "Click the IP address you want to work with."
+msgstr "点击你要修改的IP地址"
+
+# 4f5018aad8f14212a2d0c17d955b197a
+#: ../../networking/static_nat.rst:46
+msgid "Click the Static NAT |enabledisablenat.png| button."
+msgstr "点击静态NAT按钮。 |enabledisablenat.png| "
+
+# 001cc2e543c345afb265ff300a5435ca
+#: ../../networking/static_nat.rst:48
+msgid ""
+"The button toggles between Enable and Disable, depending on whether static "
+"NAT is currently enabled for the IP address."
+msgstr "该按钮在启用和禁用之间切换，这取决于IP地址是否已经启用了静态NAT。"
+
+# 91178f93f90f4135b40823266a6ecb4e
+#: ../../networking/static_nat.rst:51
+msgid ""
+"If you are enabling static NAT, a dialog appears where you can choose the "
+"destination VM and click Apply."
+msgstr "如果是启用静态NAT，会出现一个对话框让您选择目标VM然后点击应用。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/virtual_private_cloud_config.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/virtual_private_cloud_config.mo
new file mode 100644
index 0000000..e4430eb
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/virtual_private_cloud_config.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/virtual_private_cloud_config.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/virtual_private_cloud_config.po
new file mode 100644
index 0000000..163e960
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking/virtual_private_cloud_config.po
@@ -0,0 +1,2403 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:06+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 4425df0b51c64a33802d59f9f7eb5bd8
+#: ../../networking/virtual_private_cloud_config.rst:20
+msgid "Configuring a Virtual Private Cloud"
+msgstr "配置一个虚拟私有云（VPC）"
+
+# 60b4e45448554da0a9df907a8e700391
+#: ../../networking/virtual_private_cloud_config.rst:23
+msgid "About Virtual Private Clouds"
+msgstr "关于虚拟私有云（VPC）"
+
+# 9caa2b864b03431aae6a6f47aa583653
+#: ../../networking/virtual_private_cloud_config.rst:25
+msgid ""
+"CloudStack Virtual Private Cloud is a private, isolated part of CloudStack. "
+"A VPC can have its own virtual network topology that resembles a traditional"
+" physical network. You can launch VMs in the virtual network that can have "
+"private addresses in the range of your choice, for example: 10.0.0.0/16. You"
+" can define network tiers within your VPC network range, which in turn "
+"enables you to group similar kinds of instances based on IP address range."
+msgstr "CloudStackVPC是CloudStack云中私有并隔离的部分。一个VPC可以使用自己的虚拟网络拓扑来组建传统物理网络。在这个虚拟网络中，您创建的虚机的私网地址可以由您自主选择IP范围，例如10.0.0.0/16。您可以在VPC网络范围内定义多个网络层，这些层可以让你将类似的虚机按IP地址范围分组。"
+
+# e8c6a442ed744a6c96df83edc8c28763
+#: ../../networking/virtual_private_cloud_config.rst:33
+msgid ""
+"For example, if a VPC has the private range 10.0.0.0/16, its guest networks "
+"can have the network ranges 10.0.1.0/24, 10.0.2.0/24, 10.0.3.0/24, and so "
+"on."
+msgstr "例如：一个VPC的私有地址范围是10.0.0.0/16，其中的用户网络的地址范围可以分别是10.0.1.0/24、10.0.2.0/24、10.0.3.0/24等等。"
+
+# d7dd703816c14c8ab823fc4ac5ee3c02
+#: ../../networking/virtual_private_cloud_config.rst:39
+msgid "Major Components of a VPC"
+msgstr ""
+
+# c50712e0b85b4e8d8a37c525dc8f77d0
+#: ../../networking/virtual_private_cloud_config.rst:41
+msgid "A VPC is comprised of the following network components:"
+msgstr "VPC主要由以下网络组件构成："
+
+# 7805e308c7f14ae4b5bf6813c742fd84
+#: ../../networking/virtual_private_cloud_config.rst:43
+msgid ""
+"**VPC**: A VPC acts as a container for multiple isolated networks that can "
+"communicate with each other via its virtual router."
+msgstr "**VPC**：一个VPC是多个隔离网络的容器，隔离网络间可以通过VPC的虚拟路由器互通。"
+
+# 6837ce595efa433cb0a4eeef3c61bd86
+#: ../../networking/virtual_private_cloud_config.rst:46
+msgid ""
+"**Network Tiers**: Each tier acts as an isolated network with its own VLANs "
+"and CIDR list, where you can place groups of resources, such as VMs. The "
+"tiers are segmented by means of VLANs. The NIC of each tier acts as its "
+"gateway."
+msgstr "**网络层**：每个层是一个拥有各自VLAN和CIDR的隔离网络。您可以在层内放置VM等各种资源组。层与层之间通过VLAN方式隔离。VPC虚拟路由器在每个层中的网卡是该层的网关。"
+
+# eaa3327f752e430ba437d3048c8cd517
+#: ../../networking/virtual_private_cloud_config.rst:51
+msgid ""
+"**Virtual Router**: A virtual router is automatically created and started "
+"when you create a VPC. The virtual router connect the tiers and direct "
+"traffic among the public gateway, the VPN gateways, and the NAT instances. "
+"For each tier, a corresponding NIC and IP exist in the virtual router. The "
+"virtual router provides DNS and DHCP services through its IP."
+msgstr "**虚拟路由器**：创建VPC时会自动创建并启动一个虚拟路由器。该虚拟路由器连接了各层，并负责各层与公网网关、VPN网关和NAT实例间的网络流量。对于每个层，该虚拟路由器都会有对应的网卡和IP，并通过该IP提供DNS和DHCP服务。"
+
+# 2922aef73276424d86c458cab53d05d6
+#: ../../networking/virtual_private_cloud_config.rst:58
+msgid ""
+"**Public Gateway**: The traffic to and from the Internet routed to the VPC "
+"through the public gateway. In a VPC, the public gateway is not exposed to "
+"the end user; therefore, static routes are not support for the public "
+"gateway."
+msgstr "**公网网关**：VPC进出互联网的流量会走公网网关。VPC中的公网网关不暴露给最终用户，因此公网网关上不支持静态路由。"
+
+# 417e8d202f044580b6bef8868a97493b
+#: ../../networking/virtual_private_cloud_config.rst:63
+msgid ""
+"**Private Gateway**: All the traffic to and from a private network routed to"
+" the VPC through the private gateway. For more information, see \":ref"
+":`adding-priv-gw-vpc`\"."
+msgstr "**私有网关**：VPC进出某个私有网络的流量通过私有网关。更多信息，请查阅 \":ref:`adding-priv-gw-vpc`\"."
+
+# 4776de29b7b1471084bbdc0a5fd8257d
+#: ../../networking/virtual_private_cloud_config.rst:67
+msgid "**VPN Gateway**: The VPC side of a VPN connection."
+msgstr "**VPN 网关**：VPN连接的VPC端。"
+
+# 208527258e274b0ea77846c710ba8258
+#: ../../networking/virtual_private_cloud_config.rst:69
+msgid ""
+"**Site-to-Site VPN Connection**: A hardware-based VPN connection between "
+"your VPC and your datacenter, home network, or co-location facility. For "
+"more information, see \":ref:`setting-s2s-vpn-conn`\"."
+msgstr "**点对点VPN连接**：您的VPC和您的数据中心、家庭网络、主机托管设施之间基于硬件的VPN连接。更多信息，请参考\":ref:`setting-s2s-vpn-conn`\"."
+
+# 3b96c83ddcc34269896e5573992e31b5
+#: ../../networking/virtual_private_cloud_config.rst:73
+msgid ""
+"**Customer Gateway**: The customer side of a VPN Connection. For more "
+"information, see `\"Creating and Updating a VPN Customer Gateway\" "
+"<#creating-and-updating-a-vpn-customer-gateway>`_."
+msgstr "**客户网关**:客户这边的VPN连接。更多信息，请参考 `\"创建和更新VPN客户网关\" <#creating-and-updating-a-vpn-customer-gateway>`_."
+
+# bfadc68d3fbe458bb82d6692306f1319
+#: ../../networking/virtual_private_cloud_config.rst:77
+msgid ""
+"**NAT Instance**: An instance that provides Port Address Translation for "
+"instances to access the Internet via the public gateway. For more "
+"information, see \":ref:`enabling-disabling-static-nat-on-vpc`\"."
+msgstr "**NAT实例**:在用户虚机通过公网网关访问公网时，提供端口地址转换的实例。关于更多信息，请参考 \":ref:`enabling-disabling-static-nat-on-vpc`\"."
+
+# aa7430e86dde41ea828ef58fdc9a2616
+#: ../../networking/virtual_private_cloud_config.rst:81
+msgid ""
+"**Network ACL**: Network ACL is a group of Network ACL items. Network ACL "
+"items are nothing but numbered rules that are evaluated in order, starting "
+"with the lowest numbered rule. These rules determine whether traffic is "
+"allowed in or out of any tier associated with the network ACL. For more "
+"information, see \":ref:`conf-net-acl`\"."
+msgstr "**网络ACL**: 网络ACL是一组网络访问控制列表。这些列表就是一个按顺序编号的规则，执行的时候，从最小的编号开始。这些规则决定了与此ACL关联的各个层的进出流量会被允许或阻止。更多信息，请参考 \":ref:`conf-net-acl`\"."
+
+# 3248944cfc5a49b7a0c47f7fe13a0385
+#: ../../networking/virtual_private_cloud_config.rst:89
+msgid "Network Architecture in a VPC"
+msgstr "VPC的网络架构"
+
+# 5f310f0748274a1a9d0a095aec7c9c2b
+#: ../../networking/virtual_private_cloud_config.rst:91
+msgid ""
+"In a VPC, the following four basic options of network architectures are "
+"present:"
+msgstr "VPC有以下四个基本的网络架构："
+
+# 7cb03da5ae0b478690c6ab442164a344
+#: ../../networking/virtual_private_cloud_config.rst:94
+msgid "VPC with a public gateway only"
+msgstr "只有一个公网网关的VPC"
+
+# ea9f2145319e406e957665bb7b53123c
+#: ../../networking/virtual_private_cloud_config.rst:96
+msgid "VPC with public and private gateways"
+msgstr "VPC的公有和私有网关"
+
+# 2b4f4b4fbf46434c8e5534d0631bca33
+#: ../../networking/virtual_private_cloud_config.rst:98
+msgid "VPC with public and private gateways and site-to-site VPN access"
+msgstr "VPC的公有和私有网关以及site-to-site VPN访问"
+
+# 45b4489a9fcc4360a6d5b2719a77dc79
+#: ../../networking/virtual_private_cloud_config.rst:100
+msgid "VPC with a private gateway only and site-to-site VPN access"
+msgstr "只有私有网关的VPC以及site-to-site VPN访问"
+
+# b702ceb782244642b4369af267ce81d8
+#: ../../networking/virtual_private_cloud_config.rst:104
+msgid "Connectivity Options for a VPC"
+msgstr "VPC的连接选择"
+
+# 6b1ff95952fe4ccbba871b1f5d84e8d8
+#: ../../networking/virtual_private_cloud_config.rst:106
+msgid "You can connect your VPC to:"
+msgstr "你可以连接你的VPC："
+
+# 65aa43fb551b4f999e9e48eb5960893d
+#: ../../networking/virtual_private_cloud_config.rst:108
+msgid "The Internet through the public gateway."
+msgstr "通过公有网关连接到Internet."
+
+# 09137011988c4abebde330c2201cbfe4
+#: ../../networking/virtual_private_cloud_config.rst:110
+msgid ""
+"The corporate datacenter by using a site-to-site VPN connection through the "
+"VPN gateway."
+msgstr "通过site-to-siteVPN网关连接到相邻数据中心。"
+
+# 7a7466064859416c9bf3d5f6fb2828fa
+#: ../../networking/virtual_private_cloud_config.rst:113
+msgid ""
+"Both the Internet and your corporate datacenter by using both the public "
+"gateway and a VPN gateway."
+msgstr "通过公有和私有VPN网关同时连接到Internet和相邻数据中心。"
+
+# c4053fc0a35c4c30b312bd50f3cc946e
+#: ../../networking/virtual_private_cloud_config.rst:118
+msgid "VPC Network Considerations"
+msgstr "VPC网络的考虑事项"
+
+# f884bf37cfa444299fac3dd70425950c
+#: ../../networking/virtual_private_cloud_config.rst:120
+msgid "Consider the following before you create a VPC:"
+msgstr "在创建VPC之前，确认以下事项："
+
+# 3d67118ab9e24f4d861c4b78cd07fe86
+#: ../../networking/virtual_private_cloud_config.rst:122
+msgid "A VPC, by default, is created in the enabled state."
+msgstr "在创建好VPC之后，其默认处于启用状态。"
+
+# 64f62904ffbf4d0998ef58a29ec39785
+#: ../../networking/virtual_private_cloud_config.rst:124
+msgid ""
+"A VPC can be created in Advance zone only, and can't belong to more than one"
+" zone at a time."
+msgstr "只能在高级区域中创建VPC，并且VPC只能属于一个区域。"
+
+# 146628ae783e4af79b8cdd56694e87b3
+#: ../../networking/virtual_private_cloud_config.rst:127
+msgid ""
+"The default number of VPCs an account can create is 20. However, you can "
+"change it by using the max.account.vpcs global parameter, which controls the"
+" maximum number of VPCs an account is allowed to create."
+msgstr "默认VPC的数量是20个。如果你需要更多的VPC的话，可以通过修改max.account.vpcs这个全局参数。这个参数是控制创建VPC的最大数量的。"
+
+# 548f4246178a412ba72c20238355c619
+#: ../../networking/virtual_private_cloud_config.rst:131
+msgid ""
+"The default number of tiers an account can create within a VPC is 3. You can"
+" configure this number by using the vpc.max.networks parameter."
+msgstr "默认一个用户能创建VPC的层数是三层。也可以通过vpc.max.networks这个参数修改。"
+
+# 8f4ab58bb2db48e7ab28e709ee99c791
+#: ../../networking/virtual_private_cloud_config.rst:135
+msgid ""
+"Each tier should have an unique CIDR in the VPC. Ensure that the tier's CIDR"
+" should be within the VPC CIDR range."
+msgstr "VPC中每一层都需要是唯一的CIDR，并且这个CIDR是在VPC的CIDR的范围之内。"
+
+# a3ab5225e8e649a38b583c6dfa85dd0b
+#: ../../networking/virtual_private_cloud_config.rst:138
+msgid "A tier belongs to only one VPC."
+msgstr "每一层只能属于一个VPC。"
+
+# cbf79c1dbbb04abeb940ac4a4e63693b
+#: ../../networking/virtual_private_cloud_config.rst:140
+msgid "All network tiers inside the VPC should belong to the same account."
+msgstr "VPC中所有网络层都应属于同一个帐号。"
+
+# 4697685b3c1c4f75888b23d1f474ad37
+#: ../../networking/virtual_private_cloud_config.rst:142
+msgid ""
+"When a VPC is created, by default, a SourceNAT IP is allocated to it. The "
+"Source NAT IP is released only when the VPC is removed."
+msgstr "当VPC创建好之后，默认会分配好SourceNAT IP。当此VPC删除之后，SourceNAT IP也会被释放。"
+
+# f790d826d90d4341885a39022d276efc
+#: ../../networking/virtual_private_cloud_config.rst:145
+msgid ""
+"A public IP can be used for only one purpose at a time. If the IP is a "
+"sourceNAT, it cannot be used for StaticNAT or port forwarding."
+msgstr "一个公网IP只能用一个用途。如果此IP用于SourceNAT作用的话，就不能同时再用作StaticNAT 或端口转发。"
+
+# cccc0c77482c4721a48a8e3eee6370e0
+#: ../../networking/virtual_private_cloud_config.rst:148
+msgid ""
+"The instances can only have a private IP address that you provision. To "
+"communicate with the Internet, enable NAT to an instance that you launch in "
+"your VPC."
+msgstr "一个实例只能有一个私有IP地址，为了访问Internet,你可以为VPC里的此实例启用NAT功能。"
+
+# b833eb4050c145869c7a419c8f37aee9
+#: ../../networking/virtual_private_cloud_config.rst:152
+msgid ""
+"Only new networks can be added to a VPC. The maximum number of networks per "
+"VPC is limited by the value you specify in the vpc.max.networks parameter. "
+"The default value is three."
+msgstr "只有新的网络才能加入VPC。每一个VPC的最大网络数量由参数vpc.max.networks指定。其默认值为3."
+
+# 1180f413398548729b7198559dc5eb33
+#: ../../networking/virtual_private_cloud_config.rst:156
+msgid ""
+"The load balancing service can be supported by only one tier inside the VPC."
+msgstr "VPC中只有一层支持负载均衡服务。"
+
+# 1d6388d964364caa8d134f7673bfa2dd
+#: ../../networking/virtual_private_cloud_config.rst:159
+msgid "If an IP address is assigned to a tier:"
+msgstr "如果一个IP地址被赋予一个网络层："
+
+# 92d15597ceda4a5383fd25cb566b47c7
+#: ../../networking/virtual_private_cloud_config.rst:161
+msgid ""
+"That IP can't be used by more than one tier at a time in the VPC. For "
+"example, if you have tiers A and B, and a public IP1, you can create a port "
+"forwarding rule by using the IP either for A or B, but not for both."
+msgstr "那么这个IP就不能在VPC里被另外的层所使用。比如：如果你有A层和B层以及一个公网IP地址，则你可以为A或B创建一个端口转发规则，但不能同时在A和B上创建。"
+
+# a92e77fa9415458b960baded020a27ac
+#: ../../networking/virtual_private_cloud_config.rst:166
+msgid ""
+"That IP can't be used for StaticNAT, load balancing, or port forwarding "
+"rules for another guest network inside the VPC."
+msgstr "那个IP也不能在VPC的其它的客户网络里用作StaticNAT,负载均衡，端口转发规则。"
+
+# e138623610a449e8a6fd5bb3f4a2ab3f
+#: ../../networking/virtual_private_cloud_config.rst:169
+msgid "Remote access VPN is not supported in VPC networks."
+msgstr "VPC网络不支持Remote access VPN。"
+
+# 02efff273d294762ad189c6d19730f71
+#: ../../networking/virtual_private_cloud_config.rst:173
+msgid "Adding a Virtual Private Cloud"
+msgstr "添加一个VPC"
+
+# d1100a2ab1a54454bece6b2f5a47e4f8
+#: ../../networking/virtual_private_cloud_config.rst:175
+msgid ""
+"When creating the VPC, you simply provide the zone and a set of IP addresses"
+" for the VPC network address space. You specify this set of addresses in the"
+" form of a Classless Inter-Domain Routing (CIDR) block."
+msgstr "当创建VPC时，你只需要提供区域名和VPC要使用的一组IP地址。这组IP地址是以CIDR块的形式提供。"
+
+# 27c90db3b2d846b58c9abf075735077b
+# 23214314bc4c40d3bc784cf8b99c1273
+# 06da644a106746d9b22320df5442e7eb
+# 8292048a7bd74adeae7e3b6677cc7dc8
+# fb4e97f30b554d92af68a1e9d1886576
+# ceaea70c95b1422597606b789f77fae7
+# c80fe5feb23443ab8e81a05534c38d15
+# 612a8d98561a4b08824d22d8ab9cd815
+# 3d9f5b1f4cf7497ebaa39f40d2b7d3fb
+# 7af40adf2d7f49ee82115cf17558f076
+# 54efcc991da44e5b87cab339063f09cc
+# 98308f9c7c7e4548b3e6ef0828178c9d
+# b16c2e02fd8e42a1aacb687d60b4fb46
+# 1d2a5b77246843818d6d6cc8fd7482ae
+#: ../../networking/virtual_private_cloud_config.rst:179
+#: ../../networking/virtual_private_cloud_config.rst:223
+#: ../../networking/virtual_private_cloud_config.rst:331
+#: ../../networking/virtual_private_cloud_config.rst:380
+#: ../../networking/virtual_private_cloud_config.rst:492
+#: ../../networking/virtual_private_cloud_config.rst:662
+#: ../../networking/virtual_private_cloud_config.rst:729
+#: ../../networking/virtual_private_cloud_config.rst:788
+#: ../../networking/virtual_private_cloud_config.rst:848
+#: ../../networking/virtual_private_cloud_config.rst:1014
+#: ../../networking/virtual_private_cloud_config.rst:1227
+#: ../../networking/virtual_private_cloud_config.rst:1282
+#: ../../networking/virtual_private_cloud_config.rst:1360
+#: ../../networking/virtual_private_cloud_config.rst:1388
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# 25aa9d2390434c03a89b6b16c9b69fe9
+# 6e8e81dbb9f447c3aaabac12cbbebc79
+# 7daeed72e5de4f68b5d3fec3deae5a12
+# ad50664f103d4bc3b95d04f0c6891395
+# b462daef366f4f119997d229bdcd4fde
+# cbb8c618e79f4f5bb024ac637c94f155
+# d418a0fbecc7474d89b0c7122cb9f046
+# c1602cd2089a4465bb64a310c84582ae
+# 692a153c672746fa937e636f18024241
+# f2241fbd031643a498b64bc52bc9a3ed
+# 35b9e68484d140e1813335d0a33c68d1
+# bb61fadd006d4624a91bb45665efac73
+# 0cdbc29c89c540c08fa87bd601f4976c
+# 2706338d19fe43d589acd0c274b932c0
+#: ../../networking/virtual_private_cloud_config.rst:181
+#: ../../networking/virtual_private_cloud_config.rst:225
+#: ../../networking/virtual_private_cloud_config.rst:333
+#: ../../networking/virtual_private_cloud_config.rst:382
+#: ../../networking/virtual_private_cloud_config.rst:494
+#: ../../networking/virtual_private_cloud_config.rst:664
+#: ../../networking/virtual_private_cloud_config.rst:731
+#: ../../networking/virtual_private_cloud_config.rst:790
+#: ../../networking/virtual_private_cloud_config.rst:850
+#: ../../networking/virtual_private_cloud_config.rst:1016
+#: ../../networking/virtual_private_cloud_config.rst:1229
+#: ../../networking/virtual_private_cloud_config.rst:1284
+#: ../../networking/virtual_private_cloud_config.rst:1362
+#: ../../networking/virtual_private_cloud_config.rst:1390
+msgid "In the left navigation, choose Network."
+msgstr "在左侧的导航栏，选择网络。"
+
+# 4a2df6815f134b918345eaf3d39193fa
+# a59b8d1dfb334d948ed4ad0764ce5b84
+# 12b0ac2563474462b71654534aba088a
+# 08995e8ef0484b879f2982b11278720c
+# 0913e0292efb41c284ad04d0d8ec0c1d
+# f66916dd15334247bb50483cd9c296b7
+# d34dad2acbce43aa9f28ce7014089f24
+# 50500a3f8df347e19b005d01525ac7e1
+# c538254df2644b7fb6e4aa16f80f84a6
+# 92649f86d20849b498765a29fd1d7973
+# 9528e3d88e224cacb28e4e204ddab6a7
+# 934c19367f124113b2d3d8f8aabab4a6
+# cd85c04d5e0b4e7c901b189b7ab5e96e
+# 2028f717603c4390944c6c6cb703af37
+#: ../../networking/virtual_private_cloud_config.rst:183
+#: ../../networking/virtual_private_cloud_config.rst:227
+#: ../../networking/virtual_private_cloud_config.rst:335
+#: ../../networking/virtual_private_cloud_config.rst:384
+#: ../../networking/virtual_private_cloud_config.rst:496
+#: ../../networking/virtual_private_cloud_config.rst:666
+#: ../../networking/virtual_private_cloud_config.rst:733
+#: ../../networking/virtual_private_cloud_config.rst:792
+#: ../../networking/virtual_private_cloud_config.rst:852
+#: ../../networking/virtual_private_cloud_config.rst:1018
+#: ../../networking/virtual_private_cloud_config.rst:1231
+#: ../../networking/virtual_private_cloud_config.rst:1286
+#: ../../networking/virtual_private_cloud_config.rst:1364
+#: ../../networking/virtual_private_cloud_config.rst:1392
+msgid "In the Select view, select VPC."
+msgstr "在选择视图中，选择VPC。"
+
+# 03b833a9bbc14d2f8ccd0561f8bac779
+#: ../../networking/virtual_private_cloud_config.rst:185
+msgid "Click Add VPC. The Add VPC page is displayed as follows:"
+msgstr "点击添加VPC按钮。页面呈现以下："
+
+# 007c69b8b7c640d2a9dd08b2b4a86102
+#: ../../networking/virtual_private_cloud_config.rst:187
+msgid "|add-vpc.png|"
+msgstr "|add-vpc.png|"
+
+# 7bd4344fc68d4e6c8939286640c64ff6
+#: ../../networking/virtual_private_cloud_config.rst:189
+msgid "Provide the following information:"
+msgstr "填写以下内容："
+
+# fecc1622a73f4e299c4fe16149ef3c1e
+#: ../../networking/virtual_private_cloud_config.rst:191
+msgid "**Name**: A short name for the VPC that you are creating."
+msgstr "**名称**: 要创建的VPC的名称。"
+
+# 9fe964ec13864d159f7f9fe45e612351
+#: ../../networking/virtual_private_cloud_config.rst:193
+msgid "**Description**: A brief description of the VPC."
+msgstr "**描述**: 关于此VPC的简短描述."
+
+# 75bab09118a641cd94d798e0450bb114
+#: ../../networking/virtual_private_cloud_config.rst:195
+msgid "**Zone**: Choose the zone where you want the VPC to be available."
+msgstr "**区域**: 你希望将此VPN应用在哪个区域中。"
+
+# 38e1b19b64074aebbc448d4398522e6a
+#: ../../networking/virtual_private_cloud_config.rst:197
+msgid ""
+"**Super CIDR for Guest Networks**: Defines the CIDR range for all the tiers "
+"(guest networks) within a VPC. When you create a tier, ensure that its CIDR "
+"is within the Super CIDR value you enter. The CIDR must be RFC1918 "
+"compliant."
+msgstr "**客户网络超级CIDR**: 定义一个VPC内所有层（客户网络）的CIDR范围。当你新创建一个层时，这个层的CIDR必须在这个超级CIDR范围之内。CIDR的格式定义必须符合RFC1918。"
+
+# 2b3cb992f4d9418699ec71ad0d7892b7
+#: ../../networking/virtual_private_cloud_config.rst:202
+msgid ""
+"**DNS domain for Guest Networks**: If you want to assign a special domain "
+"name, specify the DNS suffix. This parameter is applied to all the tiers "
+"within the VPC. That implies, all the tiers you create in the VPC belong to "
+"the same DNS domain. If the parameter is not specified, a DNS domain name is"
+" generated automatically."
+msgstr "**客户网络的DNS域名**: 如果你需要一个域名，则需要在此指定域名后缀。这个参数会应用到VPC中所有的层中。这表示，VPC中所有的层都属于同一个域。如果没有指定域名，则域名会由系统随机产生。"
+
+# ae282958b5fb4ea594fe92f009ca5f46
+#: ../../networking/virtual_private_cloud_config.rst:208
+msgid ""
+"**Public Load Balancer Provider**: You have two options: VPC Virtual Router "
+"and Netscaler."
+msgstr "**公共负载均衡提供者**: 有两个选项：VPC虚拟路由器和 Netscaler。"
+
+# f0a8bdb0febf4b97879a69db489ba8b8
+# a37c6acaf1254a6f818d9f64ae0960aa
+# 677238e0e48a40898578fd007249ecaa
+# 650c882688974599ba5c3660d14f2838
+#: ../../networking/virtual_private_cloud_config.rst:211
+#: ../../networking/virtual_private_cloud_config.rst:281
+#: ../../networking/virtual_private_cloud_config.rst:455
+#: ../../networking/virtual_private_cloud_config.rst:479
+msgid "Click OK."
+msgstr "点击确定。"
+
+# 83d71b83ff1b413187423073f1a1c957
+#: ../../networking/virtual_private_cloud_config.rst:215
+msgid "Adding Tiers"
+msgstr "添加层"
+
+# 8202063e990e4086bb8c476cfa8f2650
+#: ../../networking/virtual_private_cloud_config.rst:217
+msgid ""
+"Tiers are distinct locations within a VPC that act as isolated networks, "
+"which do not have access to other tiers by default. Tiers are set up on "
+"different VLANs that can communicate with each other by using a virtual "
+"router. Tiers provide inexpensive, low latency network connectivity to other"
+" tiers within the VPC."
+msgstr "层在VPC里起来隔离网络的作用，默认规则是层之间不能互访。不同VLAN之间的层可以通过虚拟机实现连接。层在VPC内部提供一种廉价，低延迟的网络连接。"
+
+# 6f156f2256294f94a48422c02a2a33f1
+# 91fdfd64076446a1af782ea3021c6911
+#: ../../networking/virtual_private_cloud_config.rst:229
+#: ../../networking/virtual_private_cloud_config.rst:1366
+msgid ""
+"All the VPC that you have created for the account is listed in the page."
+msgstr "此帐号创建的所有VPC将显示在页面中。"
+
+# 98e3757975184289b5414253c54bd6c9
+#: ../../networking/virtual_private_cloud_config.rst:233
+msgid ""
+"The end users can see their own VPCs, while root and domain admin can see "
+"any VPC they are authorized to see."
+msgstr "最终用户能看到他们自己的VPC，系统管理用户和域管理员可以看到所有被授权查看的VPC。"
+
+# 3293738bea7a4e3c97fc6b8cd60f65ba
+# 4c89fd343c734f5cabc8cb26dd48bf94
+#: ../../networking/virtual_private_cloud_config.rst:236
+#: ../../networking/virtual_private_cloud_config.rst:1369
+msgid ""
+"Click the Configure button of the VPC for which you want to set up tiers."
+msgstr "在你希望设置层的VPC里，点击配置按钮。"
+
+# a3b02bf28e484233b337b84341a2f39e
+#: ../../networking/virtual_private_cloud_config.rst:239
+msgid "Click Create network."
+msgstr "点击新建网络。"
+
+# e8b22e1b54b84b1e9945e0c94e3fd069
+#: ../../networking/virtual_private_cloud_config.rst:241
+msgid "The Add new tier dialog is displayed, as follows:"
+msgstr "然后，添加层的对话界面就会出现。如下："
+
+# 1f18a2fd76094e94947690c4064b2a75
+#: ../../networking/virtual_private_cloud_config.rst:243
+msgid "|add-tier.png|"
+msgstr "|add-tier.png|"
+
+# 830f50fe9c8041c9821f1cf9b94f87bd
+#: ../../networking/virtual_private_cloud_config.rst:245
+msgid ""
+"If you have already created tiers, the VPC diagram is displayed. Click "
+"Create Tier to add a new tier."
+msgstr "如果你已添加层，VPC界面就会出现。点击添加层可以增加一个新的层。"
+
+# b372cab6baf04844a5ff7a1611d1d5b6
+# 4bc6b0a5224f4b8383ff3c5322dc34c6
+# 95ebee159c7a49d6a38872dfbba22963
+# 1490eec9177146d0bb7ef70ee1896fb9
+#: ../../networking/virtual_private_cloud_config.rst:248
+#: ../../networking/virtual_private_cloud_config.rst:539
+#: ../../networking/virtual_private_cloud_config.rst:1062
+#: ../../networking/virtual_private_cloud_config.rst:1330
+msgid "Specify the following:"
+msgstr "指定以下信息："
+
+# 07194bca2d77463fb722f6b3a2d51fd6
+#: ../../networking/virtual_private_cloud_config.rst:250
+msgid "All the fields are mandatory."
+msgstr "所有的区域必须填写的。"
+
+# 26b1c6c9cd4747a0b399711d03ee9f7f
+#: ../../networking/virtual_private_cloud_config.rst:252
+msgid "**Name**: A unique name for the tier you create."
+msgstr "**名称**: 你添加的层的一个唯一的层名。"
+
+# b4b14e979a074d9fbdd39309629f1524
+#: ../../networking/virtual_private_cloud_config.rst:254
+msgid ""
+"**Network Offering**: The following default network offerings are listed: "
+"Internal LB, DefaultIsolatedNetworkOfferingForVpcNetworksNoLB, "
+"DefaultIsolatedNetworkOfferingForVpcNetworks"
+msgstr "**网络方案**: 默认有以下几种网络方案: Internal LB, DefaultIsolatedNetworkOfferingForVpcNetworksNoLB, DefaultIsolatedNetworkOfferingForVpcNetworks"
+
+# 54126af9bcfb4590a766f2324d72f790
+#: ../../networking/virtual_private_cloud_config.rst:259
+msgid ""
+"In a VPC, only one tier can be created by using LB-enabled network offering."
+msgstr "在一个VPC中，用LB-enabled network offering只能创建一个层。"
+
+# 083df7653efc42938c67b7537bbc4bc3
+#: ../../networking/virtual_private_cloud_config.rst:262
+msgid ""
+"**Gateway**: The gateway for the tier you create. Ensure that the gateway is"
+" within the Super CIDR range that you specified while creating the VPC, and "
+"is not overlapped with the CIDR of any existing tier within the VPC."
+msgstr "**网关**：你创建网络层的网关。确保网关在你创建VPC时指定的超级CIDR范围内，并且不能与已存在VPC的任何网络层的CIDR重叠。"
+
+# abb381823abe42c78600368125e95a5a
+#: ../../networking/virtual_private_cloud_config.rst:267
+msgid "**VLAN**: The VLAN ID for the tier that the root admin creates."
+msgstr "**VLAN**: 指定系统管理员创建的层的VLAN ID号。"
+
+# e6585788ce994cfba6fa7581d88af8df
+#: ../../networking/virtual_private_cloud_config.rst:269
+msgid ""
+"This option is only visible if the network offering you selected is VLAN-"
+"enabled."
+msgstr "这个选项只在你选择的方案在VLAN-enabled的情况下才会显示出来。"
+
+# 383ce12e9bc44d939d3ae386c0ca42aa
+#: ../../networking/virtual_private_cloud_config.rst:272
+msgid ""
+"For more information, see `\"Assigning VLANs to Isolated Networks\" "
+"<hosts.html#assigning-vlans-to-isolated-networks>`_."
+msgstr "如需要更多信息，请参考\"为隔离网络分配VLAN\" <hosts.html#assigning-vlans-to-isolated-networks>`_.节。"
+
+# 88877f2edc5f40a9949cf663c7c306a0
+#: ../../networking/virtual_private_cloud_config.rst:275
+msgid "**Netmask**: The netmask for the tier you create."
+msgstr "**子网掩码**：你创建的网络层的子网掩码。"
+
+# 25897e33d08b4bedb702059f77e2f09e
+#: ../../networking/virtual_private_cloud_config.rst:277
+msgid ""
+"For example, if the VPC CIDR is 10.0.0.0/16 and the network tier CIDR is "
+"10.0.1.0/24, the gateway of the tier is 10.0.1.1, and the netmask of the "
+"tier is 255.255.255.0."
+msgstr "比如，如果VPC CIDR是10.0.0.0/16并且该网络层CIDR是10.0.1.0/24，那么这个网络层的网关是10.0.1.1，子网掩码是255.255.255.0."
+
+# 6da01b412d664e3baa5324abd03955b7
+#: ../../networking/virtual_private_cloud_config.rst:283
+msgid "Continue with configuring access control list for the tier."
+msgstr "继续为层配置访问控制列表。"
+
+# dc2a5ea9afaf4bb8b1d188b3cadc5fb2
+#: ../../networking/virtual_private_cloud_config.rst:289
+msgid "Configuring Network Access Control List"
+msgstr "配置网络访问控制列表"
+
+# 79dbace67e0b4872ba1da3458f8ccb16
+#: ../../networking/virtual_private_cloud_config.rst:291
+msgid ""
+"Define Network Access Control List (ACL) on the VPC virtual router to "
+"control incoming (ingress) and outgoing (egress) traffic between the VPC "
+"tiers, and the tiers and Internet. By default, all incoming traffic to the "
+"guest networks is blocked and all outgoing traffic from guest networks is "
+"allowed, once you add an ACL rule for outgoing traffic, then only outgoing "
+"traffic specified in this ACL rule is allowed, the rest is blocked. To open "
+"the ports, you must create a new network ACL. The network ACLs can be "
+"created for the tiers only if the NetworkACL service is supported."
+msgstr "定义网络访问控制列表（ACL），用以在VPC的层之间，或是层与互联网之间控制进出流量。默认情况下，客户网络的所有进入流量被阻止，所有外出流量被允许。一旦在外出流量方向添加了ACL，则只有ACL规则允许的流量可以被允许，其余的外出流量会被阻止。如果要开放其它端口，则需要在新的ACL中明确定义。只有在支持NetworkACL服务的条件下，只能创建层的ACL。"
+
+# c9d908950964474eb10940d7ba15e7ba
+#: ../../networking/virtual_private_cloud_config.rst:303
+msgid "About Network ACL Lists"
+msgstr "关于ACL列表"
+
+# c28b7fe0e1f04f65ad1968b74ca91f03
+#: ../../networking/virtual_private_cloud_config.rst:305
+msgid ""
+"In CloudStack terminology, Network ACL is a group of Network ACL items. "
+"Network ACL items are nothing but numbered rules that are evaluated in "
+"order, starting with the lowest numbered rule. These rules determine whether"
+" traffic is allowed in or out of any tier associated with the network ACL. "
+"You need to add the Network ACL items to the Network ACL, then associate the"
+" Network ACL with a tier. Network ACL is associated with a VPC and can be "
+"assigned to multiple VPC tiers within a VPC. A Tier is associated with a "
+"Network ACL at all the times. Each tier can be associated with only one ACL."
+msgstr "在CloudStack术语中，ACL指的是一组针对网络条目。其按条目规则顺序执行，从最小值开始。这些规则决定了与此ACL关联的层的进出流量是被允许还是阻止。操作的方法是添加一个ACL，然后将这个ACL与层关联。ACL在整个VPC中使用，它可以被关系到一个VPC当中多个层中。一个层能及只能关联到一个ACL中。"
+
+# e213818eed1947258f8bcb2896c4b24a
+#: ../../networking/virtual_private_cloud_config.rst:315
+msgid ""
+"The default Network ACL is used when no ACL is associated. Default behavior "
+"is all the incoming traffic is blocked and outgoing traffic is allowed from "
+"the tiers. Default network ACL cannot be removed or modified. Contents of "
+"the default Network ACL is:"
+msgstr "当没有ACL明确关联时，会有一个默认的ACL起作用。默认规则是层中所有进入流量被阻止，所有外出流量被允许默认的ACL不能被删除或修改。默认ACL的内容如下："
+
+# e7163daf40764297bb4c9256f9b0db76
+#: ../../networking/virtual_private_cloud_config.rst:321
+msgid "Rule"
+msgstr "规则"
+
+# 8c0f119efb90499885ad10d74e32f699
+#: ../../networking/virtual_private_cloud_config.rst:321
+msgid "Protocol"
+msgstr "协议"
+
+# 6a4e95a5005949559075e58b104e8b1e
+#: ../../networking/virtual_private_cloud_config.rst:321
+msgid "Traffic type"
+msgstr "流量类型"
+
+# db7f138ccd254efda3045d28c44e5ebd
+#: ../../networking/virtual_private_cloud_config.rst:321
+msgid "Action"
+msgstr "动作"
+
+# 51c0d62f36c143a5baf332fb86f16b96
+# d597d570fbfc4080b2ea3998fa7d939e
+# eff385663f0941d4b6809c0c182cfaf2
+# 2599fa667bce44d7b2c977f4d835a98e
+# bc9aa77c4f984714a6cead0bf43281ad
+# a2e2cc9d31f448ecab07fc456663f5bd
+# d849de055dcd46a29493cd6942aa2cae
+# 7d80106d48c4421190d8c55e7ddd2f90
+#: ../../networking/virtual_private_cloud_config.rst:321
+#: ../../networking/virtual_private_cloud_config.rst:352
+#: ../../networking/virtual_private_cloud_config.rst:519
+#: ../../networking/virtual_private_cloud_config.rst:754
+#: ../../networking/virtual_private_cloud_config.rst:812
+#: ../../networking/virtual_private_cloud_config.rst:873
+#: ../../networking/virtual_private_cloud_config.rst:1039
+#: ../../networking/virtual_private_cloud_config.rst:1307
+msgid "CIDR"
+msgstr "CIDR"
+
+# fc484eb64ca04d1b8fed82414583e90a
+#: ../../networking/virtual_private_cloud_config.rst:323
+msgid "1"
+msgstr "1"
+
+# c40bf7c2103d4006b064570d67b6b324
+# 8f113663532445cbb46226109e68fc87
+#: ../../networking/virtual_private_cloud_config.rst:323
+#: ../../networking/virtual_private_cloud_config.rst:324
+msgid "All"
+msgstr "所有"
+
+# cd3fb0b3957f47a7b32acd1b403d5f55
+#: ../../networking/virtual_private_cloud_config.rst:323
+msgid "Ingress"
+msgstr "进入流量"
+
+# e166cc8cfc04481391575caea5841312
+# d259eeaee8994ad79d0143e92a5fe39a
+#: ../../networking/virtual_private_cloud_config.rst:323
+#: ../../networking/virtual_private_cloud_config.rst:324
+msgid "Deny"
+msgstr "拒绝"
+
+# acedcca878414c89b67e3f7e98d67e02
+# c2f3ea9812544c20a6fc02ac9aad34f0
+#: ../../networking/virtual_private_cloud_config.rst:323
+#: ../../networking/virtual_private_cloud_config.rst:324
+msgid "0.0.0.0/0"
+msgstr "0.0.0.0/0"
+
+# dd6e16cde8494347a2e77ca176fd8a0c
+#: ../../networking/virtual_private_cloud_config.rst:324
+msgid "2"
+msgstr "2"
+
+# 23726ba83ae748468e32ef14a54d573b
+#: ../../networking/virtual_private_cloud_config.rst:324
+msgid "Egress"
+msgstr "外出流量"
+
+# 464f3ed7f4f24169b73210972956651a
+#: ../../networking/virtual_private_cloud_config.rst:329
+msgid "Creating ACL Lists"
+msgstr "创建ACL列表"
+
+# b4c82d1c9112484d92153e98ab6a2d33
+# 473281bb899a4393b7cf08840e8c8fde
+# 96a686680e5647d1b47c4067236c664f
+# a790843b311f4f1a9cd8d8d1ee5257a0
+# 4b114128189141c284315e2473ddc438
+# eee54cf82c9f4083b3ad53bb800a3bb4
+# 5c27b5d189844a82a379bc064c2b337e
+# 24808f02d0764c739d4aad58f9e15037
+# 1b11a2ac4b0e47ee9fc8a3f367edea68
+# 100ab8e1140f431bb36c49295576da40
+# 3ed6090af9fa4e238cf801269c4c072d
+#: ../../networking/virtual_private_cloud_config.rst:337
+#: ../../networking/virtual_private_cloud_config.rst:386
+#: ../../networking/virtual_private_cloud_config.rst:498
+#: ../../networking/virtual_private_cloud_config.rst:668
+#: ../../networking/virtual_private_cloud_config.rst:735
+#: ../../networking/virtual_private_cloud_config.rst:794
+#: ../../networking/virtual_private_cloud_config.rst:854
+#: ../../networking/virtual_private_cloud_config.rst:1020
+#: ../../networking/virtual_private_cloud_config.rst:1233
+#: ../../networking/virtual_private_cloud_config.rst:1288
+#: ../../networking/virtual_private_cloud_config.rst:1394
+msgid ""
+"All the VPCs that you have created for the account is listed in the page."
+msgstr "此帐号创建的所有VPC将显示在页面中。"
+
+# 6aa87599a443418889e9db15cc500f7d
+# 0bb74bee4b2d4d6da70d6240c47afe8f
+#: ../../networking/virtual_private_cloud_config.rst:340
+#: ../../networking/virtual_private_cloud_config.rst:389
+msgid "Click the Configure button of the VPC."
+msgstr "点击VPC的配置按钮。"
+
+# a7a5868fc1c545d8b40456b1836b9ddc
+# 62d64d7c737248d3b49d2cfcf91ab9ea
+# a7576a24a2874ab89a29f6d0b1528bac
+#: ../../networking/virtual_private_cloud_config.rst:342
+#: ../../networking/virtual_private_cloud_config.rst:1029
+#: ../../networking/virtual_private_cloud_config.rst:1297
+msgid "For each tier, the following options are displayed:"
+msgstr "对于每一个层，会显示以下选项。"
+
+# c84c70798b73443ba7f00b174398ed30
+# 2b1209152c06414c809dd9cbe8e873f6
+# 2d40227490424cf0b08f531835947150
+# 5d234a982f1c449bb04697d7e629b3d7
+# b35cbc7845ed400cb02bd71b07eac64e
+# 68ca9e9b2011446da7adcef0d83d05ee
+# edde5a9896f94691829221191ccf24ca
+#: ../../networking/virtual_private_cloud_config.rst:344
+#: ../../networking/virtual_private_cloud_config.rst:511
+#: ../../networking/virtual_private_cloud_config.rst:746
+#: ../../networking/virtual_private_cloud_config.rst:804
+#: ../../networking/virtual_private_cloud_config.rst:865
+#: ../../networking/virtual_private_cloud_config.rst:1031
+#: ../../networking/virtual_private_cloud_config.rst:1299
+msgid "Internal LB"
+msgstr "内部LB"
+
+# 840747d13a8548c3a1ed1cfa7aec94d8
+# 2cebf679ea3c44cea4495a0da3fdede4
+# 171baf1d98124ad5a9e0e93348d43959
+# 60793fb25c274674a39f4d6ca1d6f5e8
+# cdafdf21344242e391e50189def8e3f7
+# 22aed14946de415e844a06a396d14413
+# d215b78e0acd4886aaae10e01da3539a
+#: ../../networking/virtual_private_cloud_config.rst:346
+#: ../../networking/virtual_private_cloud_config.rst:513
+#: ../../networking/virtual_private_cloud_config.rst:748
+#: ../../networking/virtual_private_cloud_config.rst:806
+#: ../../networking/virtual_private_cloud_config.rst:867
+#: ../../networking/virtual_private_cloud_config.rst:1033
+#: ../../networking/virtual_private_cloud_config.rst:1301
+msgid "Public LB IP"
+msgstr "公共LB IP"
+
+# 503c7c6831eb4f5ca96c64c2b8328442
+# b565e6a4cff8412f9d1c9032ea24e848
+# 749694902cf440fea4b8315f93dddf91
+# 0b5fb5da84014d7680951915cb26b0a8
+# f8fa3d05ec454df1abf7f6a5079c965b
+# 43f4ab42a09a499783f95aba183bd8a7
+# 88e9603df37e4eacb36619474a076744
+#: ../../networking/virtual_private_cloud_config.rst:348
+#: ../../networking/virtual_private_cloud_config.rst:515
+#: ../../networking/virtual_private_cloud_config.rst:750
+#: ../../networking/virtual_private_cloud_config.rst:808
+#: ../../networking/virtual_private_cloud_config.rst:869
+#: ../../networking/virtual_private_cloud_config.rst:1035
+#: ../../networking/virtual_private_cloud_config.rst:1303
+msgid "Static NAT"
+msgstr "静态 NAT"
+
+# c7d592104fa6447da1b9471822e82ec8
+# 714747328af148798be74203cc3ea72e
+# 86f01795bd5c488fb9cbffd13a3b84a0
+# 1a4d0e4cefc648188e4e0d1e3f5f813f
+# 7df65f6c728842c680faa985c0d2b934
+# 0caa2b61a0d14a3893de13c06290cb7a
+# 8adba6b367094ad4bd769cc0a7ae13a8
+#: ../../networking/virtual_private_cloud_config.rst:350
+#: ../../networking/virtual_private_cloud_config.rst:517
+#: ../../networking/virtual_private_cloud_config.rst:752
+#: ../../networking/virtual_private_cloud_config.rst:810
+#: ../../networking/virtual_private_cloud_config.rst:871
+#: ../../networking/virtual_private_cloud_config.rst:1037
+#: ../../networking/virtual_private_cloud_config.rst:1305
+msgid "Virtual Machines"
+msgstr "虚拟机"
+
+# 2e579cf3f90345feb4b8edc18f78fd8d
+# 600d551d0f114e47a420f1c86cd445f4
+# 485eb313498a44e2ab1906012a044734
+# 92f01bcc2bcd45919753fcbc87f143c3
+# e6be963a127340ba88d4e76482c44368
+# e48b3a02fdbf4c1aab3e5704df727b54
+# 0a61a781736c436c9379e115fd3df3cb
+#: ../../networking/virtual_private_cloud_config.rst:354
+#: ../../networking/virtual_private_cloud_config.rst:521
+#: ../../networking/virtual_private_cloud_config.rst:756
+#: ../../networking/virtual_private_cloud_config.rst:814
+#: ../../networking/virtual_private_cloud_config.rst:875
+#: ../../networking/virtual_private_cloud_config.rst:1041
+#: ../../networking/virtual_private_cloud_config.rst:1309
+msgid "The following router information is displayed:"
+msgstr "显示以下路由器信息："
+
+# 4ed3754e8e014af2a5af0fb4036eeef2
+# 3d5c5cdec63d4e90aee5f9c884e80a5d
+# dcf31b093d01445ebfad5a3769f1a716
+# 4e06d785ce264f838a57f818a5eb51de
+# 33fd1f6f2fe94fbb8fcebb54432f6db5
+# 920576fcde1e43f5a7d673e3fc8c3961
+# 8d9aac57476145b98417e24b78edbee1
+#: ../../networking/virtual_private_cloud_config.rst:356
+#: ../../networking/virtual_private_cloud_config.rst:523
+#: ../../networking/virtual_private_cloud_config.rst:758
+#: ../../networking/virtual_private_cloud_config.rst:816
+#: ../../networking/virtual_private_cloud_config.rst:877
+#: ../../networking/virtual_private_cloud_config.rst:1043
+#: ../../networking/virtual_private_cloud_config.rst:1311
+msgid "Private Gateways"
+msgstr "专用网关"
+
+# 0f79101b541d4297ad26fb3125843df6
+# 4e977612c45648cd8858b2f415c8d338
+# 764c6f4d2f214c1f9d33d36fec4bc931
+# 9ed4d3258aec4c01a9d1d7ab9ee6584a
+# 6210247a7c834558b9caf3e695d10eeb
+# b44f415f26cd49dcb58c424bce136a67
+# db0357d3ac9a479698e479d686e8cd9c
+#: ../../networking/virtual_private_cloud_config.rst:358
+#: ../../networking/virtual_private_cloud_config.rst:525
+#: ../../networking/virtual_private_cloud_config.rst:760
+#: ../../networking/virtual_private_cloud_config.rst:818
+#: ../../networking/virtual_private_cloud_config.rst:879
+#: ../../networking/virtual_private_cloud_config.rst:1045
+#: ../../networking/virtual_private_cloud_config.rst:1313
+msgid "Public IP Addresses"
+msgstr "公共IP地址"
+
+# 70abe760545c42d0a794c6ce16a6c288
+# 0c346db4251b43b3a80a084bfd310d80
+# e6e45a6bac434db8b588e5a74c0902b8
+# d682a97cc5f14a0e801c4858edf11f48
+# 29fa45fc941945f891cbf96f6478db82
+# 941bc49890ae411aa05236d0e5102149
+# 3800a9e49a3b4745b17c1769febf9383
+#: ../../networking/virtual_private_cloud_config.rst:360
+#: ../../networking/virtual_private_cloud_config.rst:527
+#: ../../networking/virtual_private_cloud_config.rst:762
+#: ../../networking/virtual_private_cloud_config.rst:820
+#: ../../networking/virtual_private_cloud_config.rst:881
+#: ../../networking/virtual_private_cloud_config.rst:1047
+#: ../../networking/virtual_private_cloud_config.rst:1315
+msgid "Site-to-Site VPNs"
+msgstr "站点到站点 VPN"
+
+# ba528c5024fa489689b4d8ce0c1a0d85
+# 9b993afc4ad845f081de9838ee06ba00
+# 64ec433ac68146178442d14772e8ef45
+# 5a1b96032f234dbc85b6c87e45c31b31
+# c6f194d9a94a415a914fccd54dd4cffa
+# 1148599659df40fc8189b9aaf51587de
+# 5ae9778ec74a46dca0c4191ae03ecbb0
+#: ../../networking/virtual_private_cloud_config.rst:362
+#: ../../networking/virtual_private_cloud_config.rst:529
+#: ../../networking/virtual_private_cloud_config.rst:764
+#: ../../networking/virtual_private_cloud_config.rst:822
+#: ../../networking/virtual_private_cloud_config.rst:883
+#: ../../networking/virtual_private_cloud_config.rst:1049
+#: ../../networking/virtual_private_cloud_config.rst:1317
+msgid "Network ACL Lists"
+msgstr "网络 ACL列表"
+
+# a3498a3bc728411aa4d5a7313f8d1fca
+# 1fd8c162a2124419bfff5003f1d58fe3
+#: ../../networking/virtual_private_cloud_config.rst:364
+#: ../../networking/virtual_private_cloud_config.rst:391
+msgid "Select Network ACL Lists."
+msgstr "选择网络ACL列表。"
+
+# 9a1064fed3e342afb4b08a5d9e4ba3f9
+#: ../../networking/virtual_private_cloud_config.rst:366
+msgid ""
+"The following default rules are displayed in the Network ACLs page: "
+"default\\_allow, default\\_deny."
+msgstr "在ACL页面，下面默认规则将会显示出来：default\\_allow, default\\_deny."
+
+# eee1fde55c454e4ba76e51f7c0073681
+#: ../../networking/virtual_private_cloud_config.rst:369
+msgid "Click Add ACL Lists, and specify the following:"
+msgstr "点击添加ACL列表，指定以下配置："
+
+# 0019e51fcb5d4b609e3dfc8a2f798182
+#: ../../networking/virtual_private_cloud_config.rst:371
+msgid "**ACL List Name**: A name for the ACL list."
+msgstr "**ACL列表名称**: 为ACL列表命名。"
+
+# 545d7afa82d944fc932e088624630881
+#: ../../networking/virtual_private_cloud_config.rst:373
+msgid ""
+"**Description**: A short description of the ACL list that can be displayed "
+"to users."
+msgstr "**描述**: ACL列表的简短描述。"
+
+# 0eef9c80eb244e469737b6dbfed09ee5
+#: ../../networking/virtual_private_cloud_config.rst:378
+msgid "Creating an ACL Rule"
+msgstr "创建一个ACL规则"
+
+# 9ec1bad501f2492c875359dee57af36c
+#: ../../networking/virtual_private_cloud_config.rst:393
+msgid ""
+"In addition to the custom ACL lists you have created, the following default "
+"rules are displayed in the Network ACLs page: default\\_allow, "
+"default\\_deny."
+msgstr "除了创建的你自定义的ACL列表之后，以下默认ACL规则也会显示在页面中：default\\_allow, default\\_deny."
+
+# 56fa96725745426090705b3dea696c75
+# a5a846532a7f4d51b3b4ad850b809ffc
+#: ../../networking/virtual_private_cloud_config.rst:397
+#: ../../networking/virtual_private_cloud_config.rst:477
+msgid "Select the desired ACL list."
+msgstr "选择需要的ACL列表。"
+
+# 9b8b87a05d164a1e9388a9e96455c916
+#: ../../networking/virtual_private_cloud_config.rst:399
+msgid "Select the ACL List Rules tab."
+msgstr "选择ACL规则栏"
+
+# a35e39faa5504d4a939aa4cbc70ebd47
+#: ../../networking/virtual_private_cloud_config.rst:401
+msgid ""
+"To add an ACL rule, fill in the following fields to specify what kind of "
+"network traffic is allowed in the VPC."
+msgstr "为了创建ACL规则，需要在VPC中定义下面哪些网络流量是允许的。"
+
+# 09875f1f997e40c78467e4afbfd008a0
+#: ../../networking/virtual_private_cloud_config.rst:404
+msgid "**Rule Number**: The order in which the rules are evaluated."
+msgstr "**规则序号**: 规则被执行的顺序。"
+
+# 718a86130cf84374b39ef695d7c0319f
+#: ../../networking/virtual_private_cloud_config.rst:406
+msgid ""
+"**CIDR**: The CIDR acts as the Source CIDR for the Ingress rules, and "
+"Destination CIDR for the Egress rules. To accept traffic only from or 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 incoming "
+"traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr "**CIDR**: 对于进入的规则，CIDR对源地址起作用，对于外出的规则，CIDR对目标地址起作用。如果要定义多个可接受进出流量的特定地址段，需要以逗号分隔各个CIDR。CIDR是进入流量的基IP地址。比如， 192.168.0.0/22. 如要对所有CIDR允许流量, 设置为 0.0.0.0/0."
+
+# 5e7871dde2bc4878b9630e4f89ef78a5
+#: ../../networking/virtual_private_cloud_config.rst:413
+msgid "**Action**: What action to be taken. Allow traffic or block."
+msgstr "**操作**: 定义要进行的操作，允许或阻止。"
+
+# 960f6ba511804daf84bb14b0ee7d9fcb
+#: ../../networking/virtual_private_cloud_config.rst:415
+msgid ""
+"**Protocol**: The networking protocol that sources use to send traffic to "
+"the tier. 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. All supports all the traffic. Other "
+"option is Protocol Number."
+msgstr "**协议**: 发送到层的源地址的网络协议。最终用户的访问和数据交换通常是用TCP和UDP协议。ICMP协议通常用来发送错误信息或网络监控。ALL表示支持所有协议流量，其它选项是协议编号。"
+
+# f8c920b2724240f7bcce7a3ffa539142
+#: ../../networking/virtual_private_cloud_config.rst:422
+msgid ""
+"**Start Port**, **End Port** (TCP, UDP only): A range of listening ports "
+"that are the destination for the incoming traffic. If you are opening a "
+"single port, use the same number in both fields."
+msgstr "**起始端口**, **结束端口** (TCP, UDP only):对进入流量，这些端口是指需要监听的目标地址的端口范围。如果你只开放一个端口，则在起始和结束端口里填写同一个端口。"
+
+# 6354d433a9d14d5aac441bc824aa18d8
+#: ../../networking/virtual_private_cloud_config.rst:426
+msgid ""
+"**Protocol Number**: The protocol number associated with IPv4 or IPv6. For "
+"more information, see `Protocol Numbers <http://www.iana.org/assignments"
+"/protocol-numbers/protocol-numbers.xml>`_."
+msgstr "**协议编号**: 协议编号是与IPV4或IPV6相关联的。更多信息，请参考 `协议号 <http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xml>`_."
+
+# 07c3ccfb6e804b7b9f9c6ee3e97baab6
+#: ../../networking/virtual_private_cloud_config.rst:430
+msgid ""
+"**ICMP Type**, **ICMP Code** (ICMP only): The type of message and error code"
+" that will be sent."
+msgstr "**ICMP类型**, **ICMP代码** (ICMP only): 信息类型及发送错误的代码。"
+
+# fcf4685a451c434fa979261a9f4a989a
+#: ../../networking/virtual_private_cloud_config.rst:433
+msgid "**Traffic Type**: The type of traffic: Incoming or outgoing."
+msgstr "**流量类型**: 进出流量的类型。"
+
+# 4cb2859d5c494c07a39e4f7f9c8b316d
+#: ../../networking/virtual_private_cloud_config.rst:435
+msgid "Click Add. The ACL rule is added."
+msgstr "点击添加。这个ACL规则就添加好了。"
+
+# 6a1dc858d8f64fc4b59744f3ce271735
+#: ../../networking/virtual_private_cloud_config.rst:437
+msgid ""
+"You can edit the tags assigned to the ACL rules and delete the ACL rules you"
+" have created. Click the appropriate button in the Details tab."
+msgstr "你可以重新编辑ACL标签，或是删除ACL。点击详细信息里的appropriate按钮。"
+
+# f116157c2cc3452d9381d88f34e5edcc
+#: ../../networking/virtual_private_cloud_config.rst:443
+msgid "Creating a Tier with Custom ACL List"
+msgstr "创建一个具有自定义ACL列表的层。"
+
+# a6dcc18dbcf14658bbe49913ec9d7258
+# a9d8c9ab4785456fa3b539a958e0a391
+#: ../../networking/virtual_private_cloud_config.rst:445
+#: ../../networking/virtual_private_cloud_config.rst:461
+msgid "Create a VPC."
+msgstr "创建一个VPC。"
+
+# c46ed610d0de4aabb7a66be1bc38b59c
+# 0eba50fd6c8241ce8c46b4f22adac8ce
+#: ../../networking/virtual_private_cloud_config.rst:447
+#: ../../networking/virtual_private_cloud_config.rst:467
+msgid "Create a custom ACL list."
+msgstr "创建一个自定义ACL列表。"
+
+# d641158411d6429aa58b99856ae3aa3e
+# ee2e3bb2bdcf4ae6ac56d960eb5c8414
+#: ../../networking/virtual_private_cloud_config.rst:449
+#: ../../networking/virtual_private_cloud_config.rst:469
+msgid "Add ACL rules to the ACL list."
+msgstr "将ACL规则加入ACL列表。"
+
+# 1b9144de1d7c42478e9bcc5e58e8ad8b
+# 6416990ed47a46299ea5a399d45a25e5
+#: ../../networking/virtual_private_cloud_config.rst:451
+#: ../../networking/virtual_private_cloud_config.rst:463
+msgid "Create a tier in the VPC."
+msgstr "在VPC里创建一个层。"
+
+# d7313c7f5dc741be9cab74d4cc465987
+#: ../../networking/virtual_private_cloud_config.rst:453
+msgid "Select the desired ACL list while creating a tier."
+msgstr "在创建层的过程中选择需要的ACL列表。"
+
+# a2518e7f8c9347b1b2c5d2a4575170df
+#: ../../networking/virtual_private_cloud_config.rst:459
+msgid "Assigning a Custom ACL List to a Tier"
+msgstr "将一个自定义的ACL关联到一个层。"
+
+# 67c4657175a040149f04332d949d57bf
+#: ../../networking/virtual_private_cloud_config.rst:465
+msgid "Associate the tier with the default ACL rule."
+msgstr "将默认的ACL规则关联到层。"
+
+# b83eff10b1ce44d2bcfae9e1e8920b6f
+#: ../../networking/virtual_private_cloud_config.rst:471
+msgid "Select the tier for which you want to assign the custom ACL."
+msgstr "选中你希望赋予自定义ACL的层。"
+
+# a44330dc8018442bb213f335afaab969
+#: ../../networking/virtual_private_cloud_config.rst:473
+msgid "Click the Replace ACL List icon. |replace-acl-icon.png|"
+msgstr "点击替换ACL图标。|replace-acl-icon.png|"
+
+# dd9f88e9651f45199d45d102228e2574
+#: ../../networking/virtual_private_cloud_config.rst:475
+msgid "The Replace ACL List dialog is displayed."
+msgstr "替换ACL的对话界面将会弹出来。"
+
+# 51a9c7e87c8c46bc8c2d01f1c70b1b5e
+#: ../../networking/virtual_private_cloud_config.rst:485
+msgid "Adding a Private Gateway to a VPC"
+msgstr "在一个VPC里加入私有网关。"
+
+# 5bb03fe2db6344479a16781735c33d36
+#: ../../networking/virtual_private_cloud_config.rst:487
+msgid ""
+"A private gateway can be added by the root admin only. The VPC private "
+"network has 1:1 relationship with the NIC of the physical network. You can "
+"configure multiple private gateways to a single VPC. No gateways with "
+"duplicated VLAN and IP are allowed in the same data center."
+msgstr "私有网关只能被系统管理员添加。VPC私有网络和物理网络之间是1：1的对应关系。你可以在一个VPC里定义多个私有网关。在同一个数据中心，不允许复制VLAN和IP的网关。"
+
+# 56d5e3ac03e0437e95ee0073c44b19dd
+#: ../../networking/virtual_private_cloud_config.rst:501
+msgid ""
+"Click the Configure button of the VPC to which you want to configure load "
+"balancing rules."
+msgstr "在你想配置负载均衡的VPC上点击配置按钮。"
+
+# 142dc427cda8454c943c18bb8066cbea
+# 508dbf4fb717460bbb35c009061f7564
+# fb95c3660854480db28704507ed4b900
+# 21eb0af33be64ade85d894838188a330
+# 75579da7cb264f9b80565e8bc7ef99b4
+#: ../../networking/virtual_private_cloud_config.rst:504
+#: ../../networking/virtual_private_cloud_config.rst:741
+#: ../../networking/virtual_private_cloud_config.rst:799
+#: ../../networking/virtual_private_cloud_config.rst:860
+#: ../../networking/virtual_private_cloud_config.rst:1294
+msgid ""
+"The VPC page is displayed where all the tiers you created are listed in a "
+"diagram."
+msgstr "系统会显示VPC页面，您创建的所有层都列在图中。"
+
+# 57a669215b0c459babdfa0f7477512bb
+#: ../../networking/virtual_private_cloud_config.rst:507
+msgid "Click the Settings icon."
+msgstr "点击设置图标。"
+
+# 27df09e575754d0bb04ff268ac13cd85
+# aec57c8f590a41ea9f3c4002d2bb2082
+# c83fad1cd6a74d3ba7da7551441402ad
+#: ../../networking/virtual_private_cloud_config.rst:509
+#: ../../networking/virtual_private_cloud_config.rst:744
+#: ../../networking/virtual_private_cloud_config.rst:802
+msgid "The following options are displayed."
+msgstr "下面这些选项就会出现。"
+
+# c22be90142b04c5483ec525bb576d2c3
+#: ../../networking/virtual_private_cloud_config.rst:531
+msgid "Select Private Gateways."
+msgstr "选择私有网关。"
+
+# 2902accc6b5b49a1b204fd3fd16b1f5e
+#: ../../networking/virtual_private_cloud_config.rst:533
+msgid "The Gateways page is displayed."
+msgstr "网关对话框就会显示出来。"
+
+# 92c2f2f09846411594265950bf78b9e4
+#: ../../networking/virtual_private_cloud_config.rst:535
+msgid "Click Add new gateway:"
+msgstr "点击添加新网关："
+
+# 2c2c653d4d9d4521b4a7eb5c0e19f64c
+#: ../../networking/virtual_private_cloud_config.rst:537
+msgid "|add-new-gateway-vpc.png|"
+msgstr "|add-new-gateway-vpc.png|"
+
+# 891ea4ddb15443e5ab8f32c8088c452f
+#: ../../networking/virtual_private_cloud_config.rst:541
+msgid ""
+"**Physical Network**: The physical network you have created in the zone."
+msgstr "**物理网络**: 此处为你已在区域内建好的物理网络。"
+
+# ca06b3e4deaf4ce3a02322454f78ed68
+#: ../../networking/virtual_private_cloud_config.rst:544
+msgid "**IP Address**: The IP address associated with the VPC gateway."
+msgstr "**IP地址**: 关联VPC网关的IP地址。"
+
+# a5410ac8843e4c719973edf2d9bab4e0
+#: ../../networking/virtual_private_cloud_config.rst:546
+msgid ""
+"**Gateway**: The gateway through which the traffic is routed to and from the"
+" VPC."
+msgstr "**网关**: 定义进出VPC流量的网关。"
+
+# 955c1cc8e0f847408e1bd7754afbe13b
+#: ../../networking/virtual_private_cloud_config.rst:549
+msgid "**Netmask**: The netmask associated with the VPC gateway."
+msgstr "**Netmask**: VPC网关的子网掩码。"
+
+# 852f638bb7234dc1a27dc43b5e016322
+#: ../../networking/virtual_private_cloud_config.rst:551
+msgid "**VLAN**: The VLAN associated with the VPC gateway."
+msgstr "**VLAN**: VPC网关的VLAN。"
+
+# 6f6c910aeb6d4ee29cfd16a8f169801a
+#: ../../networking/virtual_private_cloud_config.rst:553
+msgid ""
+"**Source NAT**: Select this option to enable the source NAT service on the "
+"VPC private gateway."
+msgstr "**Source NAT**: 这个选项会启用VPC私有网关的source NAT服务。"
+
+# ca50f58a899f498d80e5d3cfaddc4e56
+#: ../../networking/virtual_private_cloud_config.rst:556
+msgid "See \":ref:`source-nat-priv-gw`\"."
+msgstr "参考\":ref:`source-nat-priv-gw`\"."
+
+# 4004b1c124dc41d7afca981bfc6aa29d
+#: ../../networking/virtual_private_cloud_config.rst:558
+msgid ""
+"**ACL**: Controls both ingress and egress traffic on a VPC private gateway. "
+"By default, all the traffic is blocked."
+msgstr "**ACL**: 控制VPC私有网关的进出流量，默认情况下，所有流量被阻止。"
+
+# e0641473896e4fc4abe0e8d8f6500ad5
+#: ../../networking/virtual_private_cloud_config.rst:561
+msgid "See \":ref:`acl-priv-gw`\"."
+msgstr "参考\":ref:`acl-priv-gw`\"."
+
+# c748dfb7b8764ed2b63524e27be99156
+#: ../../networking/virtual_private_cloud_config.rst:563
+msgid ""
+"The new gateway appears in the list. You can repeat these steps to add more "
+"gateway for this VPC."
+msgstr "新的网关就会出现在列表中。你可以重复这些步骤为VPC增加更多的网关。"
+
+# 67cc2c7079b445b1aa5c3f8d7b0ff2bf
+#: ../../networking/virtual_private_cloud_config.rst:570
+msgid "Source NAT on Private Gateway"
+msgstr "私有网关的Source NAT"
+
+# 2a8f60c14ac64d6e8d87dbce76bedb16
+#: ../../networking/virtual_private_cloud_config.rst:572
+msgid ""
+"You might want to deploy multiple VPCs with the same super CIDR and guest "
+"tier CIDR. Therefore, multiple guest VMs from different VPCs can have the "
+"same IPs to reach a enterprise data center through the private gateway. In "
+"such cases, a NAT service need to be configured on the private gateway to "
+"avoid IP conflicts. If Source NAT is enabled, the guest VMs in VPC reaches "
+"the enterprise network via private gateway IP address by using the NAT "
+"service."
+msgstr "你可能希望在同一个超级CIDR和客户层CIDR中部署多个VPC。因此，在一个数据中心，不同VPC中的虚拟机通过私有网络可以拥有相同的IP地址。在这种情况下，就需要在私有网关里配置Source NAT服务以避免IP冲突。如果Source NAT服务启用，VPC中的客户虚拟机使用私有网关IP地址与数据中心其它机器交流。"
+
+# 13ba311a60ee4d00b7c597fafb945d0b
+#: ../../networking/virtual_private_cloud_config.rst:580
+msgid ""
+"The Source NAT service on a private gateway can be enabled while adding the "
+"private gateway. On deletion of a private gateway, source NAT rules specific"
+" to the private gateway are deleted."
+msgstr "Source NAT服务是添加私有网关时启用。如果删除了私有网关，关联到此私有网关的Source NAT规则也会被删除。"
+
+# d8e4c7cc999e4730ad5bf6aa6f1b810f
+#: ../../networking/virtual_private_cloud_config.rst:584
+msgid ""
+"To enable source NAT on existing private gateways, delete them and create "
+"afresh with source NAT."
+msgstr "如要有已有私有网关中启用Source NAT，需要先删除（私有网关），然后再建一个启用Source NAT的私有网关。"
+
+# 8c1553f72c3d4599892c402b65672931
+#: ../../networking/virtual_private_cloud_config.rst:591
+msgid "ACL on Private Gateway"
+msgstr "私有网关的ACL"
+
+# 7a5729fff5c74521a2455b4e2b885a0f
+#: ../../networking/virtual_private_cloud_config.rst:593
+msgid ""
+"The traffic on the VPC private gateway is controlled by creating both "
+"ingress and egress network ACL rules. The ACLs contains both allow and deny "
+"rules. As per the rule, all the ingress traffic to the private gateway "
+"interface and all the egress traffic out from the private gateway interface "
+"are blocked."
+msgstr "VPC私有网关的进出流量是被ACL规则控制的。ACL均包含允许和阻止的规则。在每一条规则中，所有进出私有网关接口的流量是被阻止的。"
+
+# a7c844a5b9594a8c9090ef0fb4c815ac
+#: ../../networking/virtual_private_cloud_config.rst:599
+msgid ""
+"You can change this default behaviour while creating a private gateway. "
+"Alternatively, you can do the following:"
+msgstr "你可以在创建私有网关时，改变这个默认的行为。或者，你也可以按如下方式操作："
+
+# ce82be93f3014dafa0618abed1ddbc56
+# cf4dffd32e4045a0809d358aa5c89b4e
+#: ../../networking/virtual_private_cloud_config.rst:602
+#: ../../networking/virtual_private_cloud_config.rst:633
+msgid "In a VPC, identify the Private Gateway you want to work with."
+msgstr "在VPC中，验证你想操作的私有网关。"
+
+# d931e9176936499f8a82583a1141f759
+#: ../../networking/virtual_private_cloud_config.rst:604
+msgid "In the Private Gateway page, do either of the following:"
+msgstr "在私有网关页面，按如下步骤操作："
+
+# df22ccb2fc4a4d4cbc59a8eced7cdd99
+#: ../../networking/virtual_private_cloud_config.rst:606
+msgid "Use the Quickview. See 3."
+msgstr "使用快速查看视图，参考3."
+
+# 2e88948ffe35436398eb3dcc24a068a1
+#: ../../networking/virtual_private_cloud_config.rst:608
+msgid "Use the Details tab. See 4 through ."
+msgstr "使用详细查看栏。参考4。"
+
+# a6b863b1326a484080f38c0d2fffe32e
+#: ../../networking/virtual_private_cloud_config.rst:610
+msgid ""
+"In the Quickview of the selected Private Gateway, click Replace ACL, select "
+"the ACL rule, then click OK"
+msgstr "在所选择的私有网关的快速查看视图里，点击替换ACL，选中ACL规则，然后点击OK按钮。"
+
+# 393090f44f4e449480ae7b9cd7171e2e
+#: ../../networking/virtual_private_cloud_config.rst:613
+msgid "Click the IP address of the Private Gateway you want to work with."
+msgstr "点击你需要操作的私有网关的IP地址。"
+
+# 175a8bc977814206b1b438e55d487d9d
+#: ../../networking/virtual_private_cloud_config.rst:615
+msgid ""
+"In the Detail tab, click the Replace ACL button. |replace-acl-icon.png|"
+msgstr "在详细查看栏。点击替换ACL按钮。|replace-acl-icon.png|"
+
+# cb57cf7f56bd4ab7b815980fd401d492
+#: ../../networking/virtual_private_cloud_config.rst:618
+msgid "The Replace ACL dialog is displayed."
+msgstr "替换ACL的对话框就会出现。"
+
+# 52fd814724fc4614a6513bc716822b2e
+#: ../../networking/virtual_private_cloud_config.rst:620
+msgid "select the ACL rule, then click OK."
+msgstr "选择ACL规则，然后点击OK按钮。"
+
+# 0594c5c95e77436b9fba83680438d29f
+#: ../../networking/virtual_private_cloud_config.rst:622
+msgid ""
+"Wait for few seconds. You can see that the new ACL rule is displayed in the "
+"Details page."
+msgstr "稍等片刻。你就会看到新的ACL规则出现在详细页面里了。"
+
+# ab277710c8d843ae81e757e3336317d0
+#: ../../networking/virtual_private_cloud_config.rst:627
+msgid "Creating a Static Route"
+msgstr "创建一个静态静由。"
+
+# 941e24b2fbef4bb7a3938f2fc6fb31ba
+#: ../../networking/virtual_private_cloud_config.rst:629
+msgid ""
+"CloudStack enables you to specify routing for the VPN connection you create."
+" You can enter one or CIDR addresses to indicate which traffic is to be "
+"routed back to the gateway."
+msgstr "CloudStack可以让你指定你创建的VPN链接的路由。你可以输入一个或CIDR地址来指定路由返回到网关的具体流量。"
+
+# 6a994cb0af754d01bd335367a6f9d4f9
+#: ../../networking/virtual_private_cloud_config.rst:635
+msgid ""
+"In the Private Gateway page, click the IP address of the Private Gateway you"
+" want to work with."
+msgstr "在私有网关页面，点击你需要的私有网关的IP地址。"
+
+# ed8760a26f62434da30f3b3d3094da23
+#: ../../networking/virtual_private_cloud_config.rst:638
+msgid "Select the Static Routes tab."
+msgstr "选择静态路由栏。"
+
+# dc6e78e20d8a49b18b1c7b68fc53d28f
+#: ../../networking/virtual_private_cloud_config.rst:640
+msgid "Specify the CIDR of destination network."
+msgstr "指定目标网络的CIDR。"
+
+# a267ec664f35442db0c8d33d273ec07a
+#: ../../networking/virtual_private_cloud_config.rst:642
+msgid "Click Add."
+msgstr "点击 添加"
+
+# 0b06e4ce11114d68a1d616162a29b46b
+#: ../../networking/virtual_private_cloud_config.rst:644
+msgid "Wait for few seconds until the new route is created."
+msgstr "稍等片刻，新的路由就创建好了。"
+
+# f66d2b908d63453ba9331658c3105974
+#: ../../networking/virtual_private_cloud_config.rst:648
+msgid "Blacklisting Routes"
+msgstr "路由黑名单"
+
+# 5e262d8f57f94df080de1ebfd57089c5
+#: ../../networking/virtual_private_cloud_config.rst:650
+msgid ""
+"CloudStack enables you to block a list of routes so that they are not "
+"assigned to any of the VPC private gateways. Specify the list of routes that"
+" you want to blacklist in the ``blacklisted.routes`` global parameter. Note "
+"that the parameter update affects only new static route creations. If you "
+"block an existing static route, it remains intact and continue functioning. "
+"You cannot add a static route if the route is blacklisted for the zone."
+msgstr "CloudStack允许你定义一个路由黑名单，这样它们就不能关联到任何VPC私有网关。你需要在全局参数blacklisted.routes里定义。要注意，此参数只在新路由创建时才会生效。如果你在黑名单里加入了已存在的静态路由，则此静态路由还是会继续起作用。你不能把在路由黑名单里的路由加入到静态路由当中去。"
+
+# c95c27354e2b4308b6fe6cd594b07c4b
+#: ../../networking/virtual_private_cloud_config.rst:660
+msgid "Deploying VMs to the Tier"
+msgstr "将虚拟机部署到层。"
+
+# d912fb084257494b9ea49a22d2952df6
+# 6a271ec843964a2392c14ea15bebcab2
+# 2db0b4a30faa4d2486de8987dc035b35
+# 42de70c0e3314b3b9312103ccf0318a3
+#: ../../networking/virtual_private_cloud_config.rst:671
+#: ../../networking/virtual_private_cloud_config.rst:738
+#: ../../networking/virtual_private_cloud_config.rst:857
+#: ../../networking/virtual_private_cloud_config.rst:1291
+msgid ""
+"Click the Configure button of the VPC to which you want to deploy the VMs."
+msgstr "点击要部署虚机的VPC的配置按钮。"
+
+# a10f32d36f52426288a9a524c7034bde
+#: ../../networking/virtual_private_cloud_config.rst:674
+msgid ""
+"The VPC page is displayed where all the tiers you have created are listed."
+msgstr "所有创建好的层都会有VPC页面里列出来。"
+
+# e8a7f18c2c2443b8afb0ba68b10df211
+#: ../../networking/virtual_private_cloud_config.rst:677
+msgid "Click Virtual Machines tab of the tier to which you want to add a VM."
+msgstr "指向你想添加虚拟机的层，点击虚拟机栏。"
+
+# 2021d183ee7640019cdf5bdbfe5498f3
+#: ../../networking/virtual_private_cloud_config.rst:679
+msgid "|add-vm-vpc.png|"
+msgstr "|add-vm-vpc.png|"
+
+# 2d48018b840946fd8af8d726d139f5d0
+#: ../../networking/virtual_private_cloud_config.rst:681
+msgid "The Add Instance page is displayed."
+msgstr "添加实例的页面就会出现。"
+
+# 3090bc6cae14453a973abac600b9c2cf
+#: ../../networking/virtual_private_cloud_config.rst:683
+msgid ""
+"Follow the on-screen instruction to add an instance. For information on "
+"adding an instance, see the Installation Guide."
+msgstr "按照屏幕所指示的操作加入实例。至于如何添加实例，参照安装指南文档。"
+
+# dcd8e45c721b400eaba7cde1328bdc81
+#: ../../networking/virtual_private_cloud_config.rst:688
+msgid "Deploying VMs to VPC Tier and Shared Networks"
+msgstr "在VPC层中部署虚拟，共享网络。"
+
+# 17212685c197411da69afebe1fd43553
+#: ../../networking/virtual_private_cloud_config.rst:690
+msgid ""
+"CloudStack allows you deploy VMs on a VPC tier and one or more shared "
+"networks. With this feature, VMs deployed in a multi-tier application can "
+"receive monitoring services via a shared network provided by a service "
+"provider."
+msgstr "CloudStack允许你在VPC层中部署虚拟机和共享网络。有了这个功能，分布在多层当中的虚拟机可以通过共享网络接收到监控服务。"
+
+# fc5a14ca00a74032a5a578f32fe13799
+#: ../../networking/virtual_private_cloud_config.rst:695
+msgid "Log in to the CloudStack UI as an administrator."
+msgstr "用系统管理员登陆到CloudStack UI界面。"
+
+# 32b36a6c72fa45f99cc16fe65842edb4
+#: ../../networking/virtual_private_cloud_config.rst:697
+msgid "In the left navigation, choose Instances."
+msgstr "在左边的导航栏里，选择实例。"
+
+# 2f251266e8f84c3bb1eb88f9cbf3421b
+#: ../../networking/virtual_private_cloud_config.rst:699
+msgid "Click Add Instance."
+msgstr "点击添加实例。"
+
+# e9423e60b1d047809ea35f96287dc4cb
+#: ../../networking/virtual_private_cloud_config.rst:701
+msgid "Select a zone."
+msgstr "选择一个区域。"
+
+# 270e50111a9d4c328ccfd3e302a1712c
+#: ../../networking/virtual_private_cloud_config.rst:703
+msgid "Select a template or ISO, then follow the steps in the wizard."
+msgstr "选择一个模板或ISO，按向导步骤操作。 "
+
+# b9f9249e068d492a89e876e8d5282100
+#: ../../networking/virtual_private_cloud_config.rst:705
+msgid ""
+"Ensure that the hardware you have allows starting the selected service "
+"offering."
+msgstr "请确认你的硬件支持所选择的服务方案。"
+
+# 646cca07fc3241d9bdcb00578a77e3e3
+#: ../../networking/virtual_private_cloud_config.rst:708
+msgid ""
+"Under Networks, select the desired networks for the VM you are launching."
+msgstr "在网络导航栏，选择你希望虚拟机所在的网络。"
+
+# c5f162c06a0641cf8ca1c4ee6f54f651
+#: ../../networking/virtual_private_cloud_config.rst:711
+msgid "You can deploy a VM to a VPC tier and multiple shared networks."
+msgstr "你可以将虚拟机部署在一个拥有多个共享网络的VPC层中。"
+
+# edcfad81a1b04c068848242fac9adfac
+#: ../../networking/virtual_private_cloud_config.rst:713
+msgid "|addvm-tier-sharednw.png|"
+msgstr "|addvm-tier-sharednw.png|"
+
+# efc4e3cc0b2843ccb58ccc673b8f20cd
+#: ../../networking/virtual_private_cloud_config.rst:715
+msgid "Click Next, review the configuration and click Launch."
+msgstr "点击下一步，审看已配置信息，然后点击启动。"
+
+# 34b1022eb48b4dbf92712eb65b1308c8
+#: ../../networking/virtual_private_cloud_config.rst:717
+msgid "Your VM will be deployed to the selected VPC tier and shared network."
+msgstr "你的这个虚拟机就已被部署到所选择的VPC层和共享网络中。"
+
+# e75183b01c2e4d9a87561e256f60760d
+#: ../../networking/virtual_private_cloud_config.rst:721
+msgid "Acquiring a New IP Address for a VPC"
+msgstr "VPC获取新的IP地址。"
+
+# 8712a3a4537f4038a9703ae12a15da40
+#: ../../networking/virtual_private_cloud_config.rst:723
+msgid ""
+"When you acquire an IP address, all IP addresses are allocated to VPC, not "
+"to the guest networks within the VPC. The IPs are associated to the guest "
+"network only when the first port-forwarding, load balancing, or Static NAT "
+"rule is created for the IP or the network. IP can't be associated to more "
+"than one network at a time."
+msgstr "当获取IP地址时，所有的IP地址会被分配到该VPC，而不是VPC中的用户网络。只有当在IP或用户网络上创建第一个网络规则（端口映射、负载均衡、静态NAT）时，该IP才会关联到用户网络。一个IP不能同时关联一个以上的网络。"
+
+# f3548df663fd4502b857204d85782486
+#: ../../networking/virtual_private_cloud_config.rst:766
+msgid "Select IP Addresses."
+msgstr "选择IP地址。"
+
+# 8b29cfd1cdcd4018ae63dfe1624f5e58
+#: ../../networking/virtual_private_cloud_config.rst:768
+msgid "The Public IP Addresses page is displayed."
+msgstr "公网IP地址页面就显示出来。"
+
+# b571bcf25fd64067a9bc6c684f923ef4
+#: ../../networking/virtual_private_cloud_config.rst:770
+msgid "Click Acquire New IP, and click Yes in the confirmation dialog."
+msgstr "点击获得一个新IP, 并且在确认的对话框中点击确定."
+
+# 5bc9804e2b3a444c9eca95b480c5247e
+#: ../../networking/virtual_private_cloud_config.rst:772
+msgid ""
+"You are prompted for confirmation because, typically, IP addresses are a "
+"limited resource. Within a few moments, the new IP address should appear "
+"with the state Allocated. You can now use the IP address in port forwarding,"
+" load balancing, and static NAT rules."
+msgstr "因为通常IP地址是有限资源，系统会提示您确认。 在稍等片刻之后，新的IP地址将会出现并且状态是已分配。现在您就可以使用这个IP地址做端口转发、负载均衡或静态NAT。"
+
+# f14eea7624044595966630cad5fb25a4
+#: ../../networking/virtual_private_cloud_config.rst:779
+msgid "Releasing an IP Address Alloted to a VPC"
+msgstr "释放VPC分配的IP地址"
+
+# a32c2ee15c7f41209d11d1460881df99
+#: ../../networking/virtual_private_cloud_config.rst:781
+msgid ""
+"The IP address is a limited resource. If you no longer need a particular IP,"
+" you can disassociate it from its VPC and return it to the pool of available"
+" addresses. An IP address can be released from its tier, only when all the "
+"networking ( port forwarding, load balancing, or StaticNAT ) rules are "
+"removed for this IP address. The released IP address will still belongs to "
+"the same VPC."
+msgstr "IP地址是有限资源。如果您不再需要某个IP，请解除该IP和VPC的关联，使其返回到可用地址池中。只有当IP上所有的网络规则(端口映射、负载均衡、静态NAT)都删除后，该IP才能从所属层释放。释放的IP仍属于该VPC。"
+
+# cff29ec3366646748c80c78ae0b21df3
+#: ../../networking/virtual_private_cloud_config.rst:797
+msgid "Click the Configure button of the VPC whose IP you want to release."
+msgstr "点击要释放IP的VPC的配置按钮。"
+
+# e61ac663ca83460e902eb75be8323c7b
+#: ../../networking/virtual_private_cloud_config.rst:824
+msgid "Select Public IP Addresses."
+msgstr "选择公网IP地址。"
+
+# d6214f88ed8e46abb807a2b8e2f87bf7
+# fee8b392a6654e98b2a92ed46a6a1d09
+# 86b1ba91303847249fe71e091aa53075
+# e80daef3c8c548fe905c71e3888d9d35
+#: ../../networking/virtual_private_cloud_config.rst:826
+#: ../../networking/virtual_private_cloud_config.rst:887
+#: ../../networking/virtual_private_cloud_config.rst:1053
+#: ../../networking/virtual_private_cloud_config.rst:1321
+msgid "The IP Addresses page is displayed."
+msgstr "系统显示IP地址页面。"
+
+# 7100a75c5b7f4e94af12eba67cc769d7
+#: ../../networking/virtual_private_cloud_config.rst:828
+msgid "Click the IP you want to release."
+msgstr "点击要释放的IP地址。"
+
+# 5d08cda75ef64158bc169fa0b4d55bfd
+#: ../../networking/virtual_private_cloud_config.rst:830
+msgid "In the Details tab, click the Release IP button |release-ip-icon.png|"
+msgstr "在详细查看栏，点击释放IP按钮。 |release-ip-icon.png|"
+
+# 66b58ca8d7e8481184b5f30fb10aeb3a
+#: ../../networking/virtual_private_cloud_config.rst:836
+msgid "Enabling or Disabling Static NAT on a VPC"
+msgstr "VPC中启用或禁用静态NAT"
+
+# 5ffcce98eb5341c4815405feb3f45e3d
+#: ../../networking/virtual_private_cloud_config.rst:838
+msgid ""
+"A static NAT rule maps a public IP address to the private IP address of a VM"
+" in a VPC to allow Internet traffic to it. This section tells how to enable "
+"or disable static NAT for a particular IP address in a VPC."
+msgstr "静态NAT规则是将公网IP映射到VPC中虚机的私网IP，以便允许互联网流量访问该虚机。本节描述如何在VPC中启用或禁用某个公网IP地址的静态NAT。"
+
+# 3a033892a74543d4a655001ee01f7102
+#: ../../networking/virtual_private_cloud_config.rst:842
+msgid ""
+"If port forwarding rules are already in effect for an IP address, you cannot"
+" enable static NAT to that IP."
+msgstr "如果该公网IP上已经有端口转发规则，则不允许再启用静态NAT。"
+
+# 3ced6dfc6cda40c59a7663608968ae25
+#: ../../networking/virtual_private_cloud_config.rst:845
+msgid ""
+"If a guest VM is part of more than one network, static NAT rules will "
+"function only if they are defined on the default network."
+msgstr "如果用户VM存在多个网络，则静态NAT规则仅在默认网络上定义时生效。"
+
+# a101d2d938bd44ef8b442c2dd878803b
+#: ../../networking/virtual_private_cloud_config.rst:863
+msgid "For each tier, the following options are displayed."
+msgstr "对于每一个层，会显示以下选项。"
+
+# 2aa87b8efca045199c60a69232f4100c
+# f29854dbe679478497f195c125c70fc3
+# 0ca75518c2c1401bada82a5f5b3953b2
+#: ../../networking/virtual_private_cloud_config.rst:885
+#: ../../networking/virtual_private_cloud_config.rst:1051
+#: ../../networking/virtual_private_cloud_config.rst:1319
+msgid "In the Router node, select Public IP Addresses."
+msgstr "在路由器节点中，选择公共IP地址。"
+
+# ecb19327446e44f7a44f71eaef9cc73a
+#: ../../networking/virtual_private_cloud_config.rst:889
+msgid "Click the IP you want to work with."
+msgstr "点击您要操作的IP。"
+
+# 54b9ba8fad964d51a0442fc5838ba574
+#: ../../networking/virtual_private_cloud_config.rst:891
+msgid ""
+"In the Details tab,click the Static NAT button. |enable-disable.png| The "
+"button toggles between Enable and Disable, depending on whether static NAT "
+"is currently enabled for the IP address."
+msgstr "在“详细信息”页，点击静态NAT按钮|enable-disable.png| 。该按钮会根据公网IP的静态NAT当前状态，在启用和禁用间切换。"
+
+# ee96b8eeef6f44169338cbec4bd552e2
+#: ../../networking/virtual_private_cloud_config.rst:896
+msgid "If you are enabling static NAT, a dialog appears as follows:"
+msgstr "如果是启用静态NAT，会显示如下对话框："
+
+# 2934b5d934b343aab14d143fb537ce07
+#: ../../networking/virtual_private_cloud_config.rst:898
+msgid "|select-vmstatic-nat.png|"
+msgstr "|select-vmstatic-nat.png|"
+
+# ba4894eec4ee4f8ab908308bf7f2b682
+#: ../../networking/virtual_private_cloud_config.rst:900
+msgid "Select the tier and the destination VM, then click Apply."
+msgstr "选择层和目标虚机，然后点击“应用”。"
+
+# 6bc44c698b784002948ea93ac931ccb3
+#: ../../networking/virtual_private_cloud_config.rst:904
+msgid "Adding Load Balancing Rules on a VPC"
+msgstr "VPC中添加负载均衡规则"
+
+# d55b224d3d4d427da85774962a911e9b
+#: ../../networking/virtual_private_cloud_config.rst:906
+msgid ""
+"In a VPC, you can configure two types of load balancing: external LB and "
+"internal LB. External LB is nothing but a LB rule created to redirect the "
+"traffic received at a public IP of the VPC virtual router. The traffic is "
+"load balanced within a tier based on your configuration. Citrix NetScaler "
+"and VPC virtual router are supported for external LB. When you use internal "
+"LB service, traffic received at a tier is load balanced across different VMs"
+" within that tier. For example, traffic reached at Web tier is redirected to"
+" another VM in that tier. External load balancing devices are not supported "
+"for internal LB. The service is provided by a internal LB VM configured on "
+"the target tier."
+msgstr "在VPC中，你可以配置外部或内部负载均衡。外部负载均衡就是将VPC虚拟路由器接收到的公网流量进行转发的规则。这个流量如何在层里进行均衡取决于你的配置。Citrix NetScaler 和 VPC virtual router都支持外部负载均衡。内部均衡是在层内的虚拟之间进行均衡。比如，到达WEB层请求的流量可以转发到此层另外的虚拟机。外部负载均衡设备不支持内部均衡。内部负载均衡的服务是由目标层的内部虚拟机配置后提供支持服务的。"
+
+# 40e935f35e0c40ada19216e535aa1258
+#: ../../networking/virtual_private_cloud_config.rst:919
+msgid "Load Balancing Within a Tier (External LB)"
+msgstr "在层内进行负载均衡(外部负载均衡)"
+
+# f415c289521945488fc0ee0094a1dab0
+#: ../../networking/virtual_private_cloud_config.rst:921
+msgid ""
+"A CloudStack user or administrator may create load balancing rules that "
+"balance traffic received at a public IP to one or more VMs that belong to a "
+"network tier that provides load balancing service in a VPC. A user creates a"
+" rule, specifies an algorithm, and assigns the rule to a set of VMs within a"
+" tier."
+msgstr " CloudStack用户或管理员可以创建负载均衡规则。负载均衡规则用于将一个公网IP的流量分担到在VPC提供负载均衡服务的网络层内的一个或多个VM中。用户可以创建规则，指定算法，然后将规则指定到VPC的一套VM中。"
+
+# 3e4fdfab26c8433f985733abf6b8fab2
+#: ../../networking/virtual_private_cloud_config.rst:929
+msgid "Enabling NetScaler as the LB Provider on a VPC Tier"
+msgstr "在VPC层中启用基于NetScaler的负载均衡"
+
+# f4009b64ee9a4abc935568ba00072b14
+#: ../../networking/virtual_private_cloud_config.rst:931
+msgid "Add and enable Netscaler VPX in dedicated mode."
+msgstr "添加并启用 Netscaler VPX独立模块。"
+
+# 11c807f9e62a4acb9f8b3ef0d007c2c9
+#: ../../networking/virtual_private_cloud_config.rst:933
+msgid ""
+"Netscaler can be used in a VPC environment only if it is in dedicated mode."
+msgstr "Netscaler只能在独立模块的形式下应用于VPC环境中。"
+
+# 57a85fbc857449ee89781dd4fce1788c
+#: ../../networking/virtual_private_cloud_config.rst:936
+msgid ""
+"Create a network offering, as given in \":ref:`create-net-offering-ext-"
+"lb`\"."
+msgstr "创建启用持久化选项的网络方案。请参考\":ref:`create-net-offering-ext-lb`\"."
+
+# 08a0f277fc3f43b694322360de337dfc
+#: ../../networking/virtual_private_cloud_config.rst:938
+msgid "Create a VPC with Netscaler as the Public LB provider."
+msgstr "在VPC中创建一个基于Netscaler的公用负载均衡。"
+
+# ecc067da6bf9448587d900d0602ecacd
+#: ../../networking/virtual_private_cloud_config.rst:940
+msgid ""
+"For more information, see `\"Adding a Virtual Private Cloud\" <#adding-a"
+"-virtual-private-cloud>`_."
+msgstr "更多信息，请参考 `\"添加一个VPC\" <#adding-a-virtual-private-cloud>`_."
+
+# aa3b5b48c05343338d0ee08f3382b40d
+#: ../../networking/virtual_private_cloud_config.rst:943
+msgid "For the VPC, acquire an IP."
+msgstr "在VPC中获取一个IP地址。"
+
+# 7c4c3743af9240d882f3ba1d438b3bd8
+#: ../../networking/virtual_private_cloud_config.rst:945
+msgid ""
+"Create an external load balancing rule and apply, as given in :ref:`create-"
+"ext-lb-rule`."
+msgstr "创建并应用一个外部负载均衡规则。请参考:ref:`create-ext-lb-rule`."
+
+# 65a1193d54904d989149249c4257b9c1
+#: ../../networking/virtual_private_cloud_config.rst:952
+msgid "Creating a Network Offering for External LB"
+msgstr "创建一个外部负载均衡网络方案"
+
+# e69c20a921124dc7b5ac28a8bc23f254
+#: ../../networking/virtual_private_cloud_config.rst:954
+msgid ""
+"To have external LB support on VPC, create a network offering as follows:"
+msgstr "要在VPC中启用外部负载均衡支持，依如下操作建立网络方案："
+
+# 27d475982a384fed8f13220941eded23
+# 2da0ddfe20c0412a9dc8725da9ebfb08
+#: ../../networking/virtual_private_cloud_config.rst:957
+#: ../../networking/virtual_private_cloud_config.rst:1163
+msgid "Log in to the CloudStack UI as a user or admin."
+msgstr "使用用户或管理员登录到CloudStack用户界面。"
+
+# 2e6d402ef3d044488597c6501ca6749d
+# f974a014675745ceae4ebb19113bc49e
+#: ../../networking/virtual_private_cloud_config.rst:959
+#: ../../networking/virtual_private_cloud_config.rst:1165
+msgid "From the Select Offering drop-down, choose Network Offering."
+msgstr "下拉选择方案，选择网络方案："
+
+# 08107e25d3ae4ed5a4e72a9ef68249af
+# f88397d4525c49d4b10ca8f6d24c5999
+#: ../../networking/virtual_private_cloud_config.rst:961
+#: ../../networking/virtual_private_cloud_config.rst:1167
+msgid "Click Add Network Offering."
+msgstr "点击添加网络方案。"
+
+# 0b77090696474c0a9cab45f79b1c7986
+# e1cffd47fe2e4f3089c2620a68b839a1
+#: ../../networking/virtual_private_cloud_config.rst:963
+#: ../../networking/virtual_private_cloud_config.rst:1169
+msgid "In the dialog, make the following choices:"
+msgstr "在对话框中，选择如下操作："
+
+# 60d2abd68eb948dbaba04e1ac5723b86
+# 2e15e5f8b3704612a4d58813e4d32f6b
+#: ../../networking/virtual_private_cloud_config.rst:965
+#: ../../networking/virtual_private_cloud_config.rst:1171
+msgid "**Name**: Any desired name for the network offering."
+msgstr "**名称**: 任何网络方案的名称。"
+
+# 3959d6091cd747cb937e8f842088c32e
+# 5f694898705c49328c1a2e142eb14d1f
+#: ../../networking/virtual_private_cloud_config.rst:967
+#: ../../networking/virtual_private_cloud_config.rst:1173
+msgid ""
+"**Description**: A short description of the offering that can be displayed "
+"to users."
+msgstr "**描述**: 提供一个简短的方案描述。 "
+
+# 2e0e45c2f8604206ab9ab52b64e032e0
+# 40a66509e3424c24bb6186610a441bac
+#: ../../networking/virtual_private_cloud_config.rst:970
+#: ../../networking/virtual_private_cloud_config.rst:1176
+msgid "**Network Rate**: Allowed data transfer rate in MB per second."
+msgstr "**网络速度**: 允许的数据传输速度（MB/秒）。"
+
+# 33f13b044bc94b5b8696d75ddf4b8bc3
+# a160a569847143f797400c4ff977efdf
+#: ../../networking/virtual_private_cloud_config.rst:972
+#: ../../networking/virtual_private_cloud_config.rst:1178
+msgid ""
+"**Traffic Type**: The type of network traffic that will be carried on the "
+"network."
+msgstr "**流量类型**: 允许承载的网络流量类型。"
+
+# aaf9ff68483341d98ede19f290845e4d
+# c3356024660a4455a0ceac2dcae5caee
+#: ../../networking/virtual_private_cloud_config.rst:975
+#: ../../networking/virtual_private_cloud_config.rst:1181
+msgid ""
+"**Guest Type**: Choose whether the guest network is isolated or shared."
+msgstr "**来宾类型**: 选择来宾网络为隔离或共享网络。"
+
+# 78da437179454d2e9bb2b2566016b345
+# 8e43b8eb7620486dafe2037f9644fc74
+#: ../../networking/virtual_private_cloud_config.rst:978
+#: ../../networking/virtual_private_cloud_config.rst:1184
+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."
+msgstr "**持续性**: 表明来宾网络是否支持持续性。无需提供任何VM部署的网络，称之为持续性网络。"
+
+# b8efdabd98ae4986a6423993e842848f
+# a09dbae19ba24a44abe4d1e06d94391d
+#: ../../networking/virtual_private_cloud_config.rst:982
+#: ../../networking/virtual_private_cloud_config.rst:1188
+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\" <#about-virtual-private-clouds>`_."
+msgstr "**VPC**: 此选项表明是否在来宾网络中启用VPC。 CloudStack中的虚拟专用云(VPC)是专用、隔离的。 一个VPC可以有一个类似于传统物理网络的虚拟网络拓扑结构。有关的VPC的详细信息，请参考`\"关于VPC\" <#about-virtual-private-clouds>`_."
+
+# f833921e66e7405e90b64ecab4f06585
+# 60780dc0b1414010b97ef9ee9fdf6896
+#: ../../networking/virtual_private_cloud_config.rst:988
+#: ../../networking/virtual_private_cloud_config.rst:1195
+msgid ""
+"**Specify VLAN**: (Isolated guest networks only) Indicate whether a VLAN "
+"should be specified when this offering is used."
+msgstr "**指定**: (仅隔离的来宾网络) 表明在使用这个网络方案时，是否指定VLAN。"
+
+# c39ddc76ab104334a4dc179d2666185f
+#: ../../networking/virtual_private_cloud_config.rst:991
+msgid ""
+"**Supported Services**: Select Load Balancer. Use Netscaler or "
+"VpcVirtualRouter."
+msgstr "**支持服务**:选择负载均衡，使用Netscaler 或 VpcVirtualRouter."
+
+# 0f2a2787484945d4893a95c93e013659
+#: ../../networking/virtual_private_cloud_config.rst:994
+msgid "**Load Balancer Type**: Select Public LB from the drop-down."
+msgstr "**负载均衡类型**:从下拉列表里选择公用负载均衡。"
+
+# 012d5de507d14d86a63f00c612267262
+#: ../../networking/virtual_private_cloud_config.rst:996
+msgid ""
+"**LB Isolation**: Select Dedicated if Netscaler is used as the external LB "
+"provider."
+msgstr "**负载均衡隔离**: 如果使用Netscale作为外部负载均衡，选择此项进行隔离。"
+
+# 32714ec60c95462a86fad6f4ea8a389f
+# 6d1b55437586405195f96d4e1901a030
+#: ../../networking/virtual_private_cloud_config.rst:999
+#: ../../networking/virtual_private_cloud_config.rst:1203
+msgid ""
+"**System Offering**: Choose the system service offering that you want "
+"virtual routers to use in this network."
+msgstr "**系统方案**: 选择你想在这个网络中使用的虚拟路由器的系统服务方案。"
+
+# ccddc4e596ac4b9590b1e89143679f4c
+# 5b0c2de816bb4f3489ea6c0aaf56dd92
+#: ../../networking/virtual_private_cloud_config.rst:1002
+#: ../../networking/virtual_private_cloud_config.rst:1206
+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."
+msgstr "**保护模式**: 表明是否使用保护模式。在这个模式中，只有网络中第一个虚拟机启动时才分配网络资源。"
+
+# 64b8ac5900b040949abdbe1be369798e
+# 86eacc968b5642af9d7708d20b05fa0b
+#: ../../networking/virtual_private_cloud_config.rst:1006
+#: ../../networking/virtual_private_cloud_config.rst:1210
+msgid "Click OK and the network offering is created."
+msgstr "点击OK按钮，网络方案就创建好了。"
+
+# 7d8aa307714e45a48e2b8a026f88ecd5
+#: ../../networking/virtual_private_cloud_config.rst:1012
+msgid "Creating an External LB Rule"
+msgstr "创建一个外部负载均衡规则"
+
+# ec858cbb6d054d82b7344347f3d1f80a
+#: ../../networking/virtual_private_cloud_config.rst:1023
+msgid ""
+"Click the Configure button of the VPC, for which you want to configure load "
+"balancing rules."
+msgstr "点击要配置负载均衡规则的VPC的配置按钮。"
+
+# 24c4acc56c8546b48b0d1ba8225aa2c3
+# 8623ea1fa5f64fc882bc161a00e0de31
+#: ../../networking/virtual_private_cloud_config.rst:1026
+#: ../../networking/virtual_private_cloud_config.rst:1239
+msgid ""
+"The VPC page is displayed where all the tiers you created listed in a "
+"diagram."
+msgstr "系统会显示VPC页面，您创建的所有层都列在图中。"
+
+# faa2aca06f244ec79e1495f403d60fba
+# f6b4d72a1ace463aaeae65e85f5351fe
+#: ../../networking/virtual_private_cloud_config.rst:1055
+#: ../../networking/virtual_private_cloud_config.rst:1323
+msgid ""
+"Click the IP address for which you want to create the rule, then click the "
+"Configuration tab."
+msgstr "点击你希望创建规则的IP地址，然后点击配置"
+
+# 05fb941cda1540a6ae76a68c80d28164
+#: ../../networking/virtual_private_cloud_config.rst:1058
+msgid "In the Load Balancing node of the diagram, click View All."
+msgstr "在图的负载均衡节点点上，点击 查看全部。"
+
+# a68bbaad32ad4fb1a32434a21627c7df
+# 513eb1682d554f15af9624073505f185
+#: ../../networking/virtual_private_cloud_config.rst:1060
+#: ../../networking/virtual_private_cloud_config.rst:1328
+msgid "Select the tier to which you want to apply the rule."
+msgstr "选择应用规则的层。"
+
+# 48072a5bd67b4fc2b091903b2930ef20
+# 23e879002b734874bb3fb8648d82ec9f
+#: ../../networking/virtual_private_cloud_config.rst:1064
+#: ../../networking/virtual_private_cloud_config.rst:1249
+msgid "**Name**: A name for the load balancer rule."
+msgstr "**名称**: 负载均衡规则的名称。"
+
+# 035ce1c6b7094ddfb03cf84e79fe13fb
+#: ../../networking/virtual_private_cloud_config.rst:1066
+msgid ""
+"**Public Port**: The port that receives the incoming traffic to be balanced."
+msgstr "**公网端口**: 接收待负载均衡的流入流量的端口。"
+
+# 95e57b758d354580b0723b1cf69b1ad9
+#: ../../networking/virtual_private_cloud_config.rst:1069
+msgid ""
+"**Private Port**: The port that the VMs will use to receive the traffic."
+msgstr "**私有端口**: 虚拟机会使用此端口接收流量。"
+
+# 9401419db1ac40dd8912809bfb47d5fa
+# c29c451e2c474605af3093430f4fe416
+#: ../../networking/virtual_private_cloud_config.rst:1072
+#: ../../networking/virtual_private_cloud_config.rst:1268
+msgid ""
+"**Algorithm**. Choose the load balancing algorithm you want CloudStack to "
+"use. CloudStack supports the following well-known algorithms:"
+msgstr "**算法**。选择您希望CloudStack 使用的负载均衡算法。CloudStack 支持下列知名的算法："
+
+# 45872bf350da46e8915a4c200e500d47
+# 2fe10525962546129f438019ddb43570
+#: ../../networking/virtual_private_cloud_config.rst:1076
+#: ../../networking/virtual_private_cloud_config.rst:1272
+msgid "Round-robin"
+msgstr "轮询"
+
+# b89b8c35da0e4067aa0e2dfc46507db4
+# 384c8fd5fe8049389138586119a8e392
+#: ../../networking/virtual_private_cloud_config.rst:1078
+#: ../../networking/virtual_private_cloud_config.rst:1274
+msgid "Least connections"
+msgstr "最少连接"
+
+# 75b481e88cb749ee9744fa2d4153d658
+# a656566824f644a7a9bf0c5aa7f7ce82
+#: ../../networking/virtual_private_cloud_config.rst:1080
+#: ../../networking/virtual_private_cloud_config.rst:1276
+msgid "Source"
+msgstr "源IP"
+
+# 156eaabf00d6402fb1a6f26cdc8bdc3a
+#: ../../networking/virtual_private_cloud_config.rst:1082
+msgid ""
+"**Stickiness**. (Optional) Click Configure and choose the algorithm for the "
+"stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr "**粘性**. (可选)点击配置，选择粘性策略使用的算法。参见负载均衡规则的粘性会话策略。"
+
+# 5a609fc01f0c442fbaa6859f3c48de9d
+#: ../../networking/virtual_private_cloud_config.rst:1086
+msgid ""
+"**Add VMs**: Click Add VMs, then select two or more VMs that will divide the"
+" load of incoming traffic, and click Apply."
+msgstr "点击添加VM，选择两个或更多的VM分担流入的流量，然后点击应用。"
+
+# 227920ab85304ccd9ef2ff2fcc816394
+#: ../../networking/virtual_private_cloud_config.rst:1089
+msgid ""
+"The new load balancing rule appears in the list. You can repeat these steps "
+"to add more load balancing rules for this IP address."
+msgstr "新的负载均衡策略会显示在列表中。您可以重复以上步骤为该IP地址添加更多的负载均衡策略。"
+
+# 9e2c252f60374e98b336b982bdb5a807
+#: ../../networking/virtual_private_cloud_config.rst:1094
+msgid "Load Balancing Across Tiers"
+msgstr "跨越层的负载均衡"
+
+# b0b3d2bc1154428ea7aa2a73ccf65ca9
+#: ../../networking/virtual_private_cloud_config.rst:1096
+msgid ""
+"CloudStack supports sharing workload across different tiers within your VPC."
+" Assume that multiple tiers are set up in your environment, such as Web tier"
+" and Application tier. Traffic to each tier is balanced on the VPC virtual "
+"router on the public side, as explained in `\"Adding Load Balancing Rules on"
+" a VPC\" <#adding-load-balancing-rules-on-a-vpc>`_. If you want the traffic "
+"coming from the Web tier to the Application tier to be balanced, use the "
+"internal load balancing feature offered by CloudStack."
+msgstr "CloudStack支持在VPC内不同层之间共享工作负载。这需要先在你的环境里设置好多个层，比如WEB层，应用层。每一个层的流量通过VPC虚拟路由机进行负载均衡。关于这方面的内容， `\"在VPC里添加负载均衡规则\" <#adding-load-balancing-rules-on-a-vpc>`_. 如果你想将WEB层发向应用层的流量进行负载均衡，需要使用Cloudstack的内部负载均衡功能。"
+
+# fbb2a59a26334767857dae55b7dd76d2
+#: ../../networking/virtual_private_cloud_config.rst:1107
+msgid "How Does Internal LB Work in VPC?"
+msgstr "在VPC中，内部负载均衡是如何工作的呢？"
+
+# 9f3100aad1e345bb8ac547e9ff36084f
+#: ../../networking/virtual_private_cloud_config.rst:1109
+msgid ""
+"In this figure, a public LB rule is created for the public IP 72.52.125.10 "
+"with public port 80 and private port 81. The LB rule, created on the VPC "
+"virtual router, is applied on the traffic coming from the Internet to the "
+"VMs on the Web tier. On the Application tier two internal load balancing "
+"rules are created. An internal LB rule for the guest IP 10.10.10.4 with load"
+" balancer port 23 and instance port 25 is configured on the VM, "
+"InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.4 with "
+"load balancer port 45 and instance port 46 is configured on the VM, "
+"InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.6, with "
+"load balancer port 23 and instance port 25 is configured on the VM, "
+"InternalLBVM2."
+msgstr "在这个图中，公网负载均衡规则是这样创建的：公网IP为IP 72.52.125.10，外网端口为80，内网端口为81。VPC的虚拟路由机创建的负载均衡规则将互联网的流量分配到WEB层的各个虚拟机上。在应用层创建了两个内部负载均衡规则。其中一个规则是：客户IP为10.10.10.4的将端口23进行负载分发，实例VM和InternalLBVM1的端口25进行了负载。另一条规则是：客户IP为10.10.10.4的将端口45进行负载分发，实例VM和InternalLBVM1的端口46进行了负载。另一条规则是：客户IP为10.10.10.6的将端口23进行负载分发，实例VM和InternalLBVM1的端口25进行了负载。（两条规则还是三条规则？原文如此，希望图示能明解）"
+
+# c94baade36ca41029339b5771845f6eb
+#: ../../networking/virtual_private_cloud_config.rst:1121
+msgid "|vpc-lb.png|"
+msgstr "|vpc-lb.png|"
+
+# 6b5c736fe39c453f9df86d49e415bb0d
+#: ../../networking/virtual_private_cloud_config.rst:1125
+msgid "Guidelines"
+msgstr "指南"
+
+# f48db5cf237f48c1b83470d2b3619c89
+#: ../../networking/virtual_private_cloud_config.rst:1127
+msgid ""
+"Internal LB and Public LB are mutually exclusive on a tier. If the tier has "
+"LB on the public side, then it can't have the Internal LB."
+msgstr "内部和公网负载均衡在一个层里往往是互斥的。如果一个层已应用了公网负载均衡之后，此层就不能再应用内部负载均衡。"
+
+# 39c3726d0f1e417ba4856caefdc69c5f
+#: ../../networking/virtual_private_cloud_config.rst:1130
+msgid ""
+"Internal LB is supported just on VPC networks in CloudStack 4.2 release."
+msgstr "在 CloudStack 4.2版本中，只有VPC网络支持内部负载均衡。"
+
+# c9b5009bd45949ca9adfe8bad469126e
+#: ../../networking/virtual_private_cloud_config.rst:1133
+msgid ""
+"Only Internal LB VM can act as the Internal LB provider in CloudStack 4.2 "
+"release."
+msgstr "在CloudStack 4.2 版本中，只有Internal LB VM才能作内部负载均衡的提供方。"
+
+# f0db26b4389241deb62e3e62af4ae108
+#: ../../networking/virtual_private_cloud_config.rst:1136
+msgid ""
+"Network upgrade is not supported from the network offering with Internal LB "
+"to the network offering with Public LB."
+msgstr "将网络方案由内部负载均衡更改为公网负载均衡是不可行的。"
+
+# cdacc61443a24192b33aa89bf454081d
+#: ../../networking/virtual_private_cloud_config.rst:1139
+msgid "Multiple tiers can have internal LB support in a VPC."
+msgstr "在VPC中，多层可以应用内部负载均衡。"
+
+# 08ebb9d7ed624f58a875207bb6be9859
+#: ../../networking/virtual_private_cloud_config.rst:1141
+msgid "Only one tier can have Public LB support in a VPC."
+msgstr "在VPC中，只有一层只支持公网负载均衡。"
+
+# 0cf099b085094a858d1b083c8e2f72f6
+#: ../../networking/virtual_private_cloud_config.rst:1145
+msgid "Enabling Internal LB on a VPC Tier"
+msgstr "在VPC层上启用内部负载均衡功能"
+
+# 381918d116bf406189b9d4dd38f04f33
+#: ../../networking/virtual_private_cloud_config.rst:1147
+msgid ""
+"Create a network offering, as given in :ref:`creating-net-offering-internal-"
+"lb`."
+msgstr "创建一个新的网络方案，请参考:ref:`creating-net-offering-internal-lb`."
+
+# f09e6b3612574602ae51429ca4126c05
+#: ../../networking/virtual_private_cloud_config.rst:1150
+msgid ""
+"Create an internal load balancing rule and apply, as given in :ref:`create-"
+"int-lb-rule`."
+msgstr "创建并应用一个内部负载均衡规则。参考:ref:`create-int-lb-rule`."
+
+# 25a70af8ca1e41f18f48eb08ef5d850a
+#: ../../networking/virtual_private_cloud_config.rst:1157
+msgid "Creating a Network Offering for Internal LB"
+msgstr "创建一个内部负载均衡网络方案"
+
+# 08c27533594e44e582e605b3e9b3df6a
+#: ../../networking/virtual_private_cloud_config.rst:1159
+msgid ""
+"To have internal LB support on VPC, either use the default offering, "
+"DefaultIsolatedNetworkOfferingForVpcNetworksWithInternalLB, or create a "
+"network offering as follows:"
+msgstr "要在VPC当中使用内部负载均衡，可以使用默认的DefaultIsolatedNetworkOfferingForVpcNetworksWithInternalLB,或按如下操作新建一个网络方案："
+
+# a41f382608f64d309fbe464cf7137a17
+#: ../../networking/virtual_private_cloud_config.rst:1198
+msgid ""
+"**Supported Services**: Select Load Balancer. Select ``InternalLbVM`` from "
+"the provider list."
+msgstr "**支持服务**: 选择负载均衡，从待提供的下拉列表里选择`InternalLbVM。"
+
+# 163583059e0b4dc38ec9a9324be12914
+#: ../../networking/virtual_private_cloud_config.rst:1201
+msgid "**Load Balancer Type**: Select Internal LB from the drop-down."
+msgstr "**负载均衡类型**: 从下拉列表里选择内部负载均衡。"
+
+# c468f85bcd804f59b3e50b6395b59e2a
+#: ../../networking/virtual_private_cloud_config.rst:1216
+msgid "Creating an Internal LB Rule"
+msgstr "创建一个内部负载均衡规则"
+
+# 97768defcebc48e484aca56eed453215
+#: ../../networking/virtual_private_cloud_config.rst:1218
+msgid ""
+"When you create the Internal LB rule and applies to a VM, an Internal LB VM,"
+" which is responsible for load balancing, is created."
+msgstr "当你创建好一个内部负载均衡规则，并将之用于一个虚拟之后，一个内部负载均衡的应用就建立起来了。"
+
+# 68b5cb10c6e7463690bbeefba32870fb
+#: ../../networking/virtual_private_cloud_config.rst:1221
+msgid ""
+"You can view the created Internal LB VM in the Instances page if you "
+"navigate to **Infrastructure** > **Zones** > <zone\\_ name> > "
+"<physical\\_network\\_name> > **Network Service Providers** > **Internal LB "
+"VM**. You can manage the Internal LB VMs as and when required from the "
+"location."
+msgstr "你可以在实例页面中查看创建的内部LB VM 按如下导航 **基础构架** > **区域** > <zone\\_ name> > <physical\\_network\\_name> > **网络服务提供** > **内部负载均衡虚拟机**，你就可以看到已创建了内部负载均衡的实例上。也可以在此进行内部负载均衡的管理。"
+
+# 3df2a5995876429facf54c5a8446811d
+#: ../../networking/virtual_private_cloud_config.rst:1236
+msgid ""
+"Locate the VPC for which you want to configure internal LB, then click "
+"Configure."
+msgstr "点击要配置内部负载均衡规则的VPC的配置按钮。"
+
+# 6f207d8e5df84a4b8c67c56fd431c1d7
+#: ../../networking/virtual_private_cloud_config.rst:1242
+msgid ""
+"Locate the Tier for which you want to configure an internal LB rule, click "
+"Internal LB."
+msgstr "指向你想配置内部负载均衡的层，点击内部负载均衡。"
+
+# 3d886b162d3b4cb78187e716d7935265
+#: ../../networking/virtual_private_cloud_config.rst:1245
+msgid "In the Internal LB page, click Add Internal LB."
+msgstr "在 Internal LB页面里，点击添加 Internal LB。"
+
+# f08b145932924c3caba6b02b3e38b19a
+#: ../../networking/virtual_private_cloud_config.rst:1247
+msgid "In the dialog, specify the following:"
+msgstr "在对话框里，定义以下内容："
+
+# 551399e510014c7fbc3cf5f1a0110627
+#: ../../networking/virtual_private_cloud_config.rst:1251
+msgid ""
+"**Description**: A short description of the rule that can be displayed to "
+"users."
+msgstr "**描述**: 提供一个简短的规则描述。 "
+
+# 6cf0e4a86d4043878ef3a656833ff790
+#: ../../networking/virtual_private_cloud_config.rst:1254
+msgid ""
+"**Source IP Address**: (Optional) The source IP from which traffic "
+"originates. The IP is acquired from the CIDR of that particular tier on "
+"which you want to create the Internal LB rule. If not specified, the IP "
+"address is automatically allocated from the network CIDR."
+msgstr "**源IP地址**: (可选) 是指产生流量的源IP地址。这个地址是从你创建内部负载均衡的层中的CIDR中获取的。如果没有指定，则系统会自动从CIDR中分配。"
+
+# 2feac41c2e1b49e48df5d82f1bda3eef
+#: ../../networking/virtual_private_cloud_config.rst:1260
+msgid ""
+"For every Source IP, a new Internal LB VM is created for load balancing."
+msgstr "对于每一个源IP地址，都可以建立一个针对它的内部负载均衡。"
+
+# 4063dce4a7c94bc19982815512a92efa
+#: ../../networking/virtual_private_cloud_config.rst:1263
+msgid ""
+"**Source Port**: The port associated with the source IP. Traffic on this "
+"port is load balanced."
+msgstr "**源端口**: 与源IP地址关联的端口，此端口上的流量是基于负载均衡的。"
+
+# 7c1698db8e014d99ba6821c2749a280a
+#: ../../networking/virtual_private_cloud_config.rst:1266
+msgid "**Instance Port**: The port of the internal LB VM."
+msgstr "**实例端口**: 内部负载均衡虚拟机的端口。"
+
+# 22a6cc81098f4226b86f3e9b82cd4bba
+#: ../../networking/virtual_private_cloud_config.rst:1280
+msgid "Adding a Port Forwarding Rule on a VPC"
+msgstr "在VPC里添加一个端口转发规则。"
+
+# d8e4477eb9414ccbad83f00d2dbb0bcc
+#: ../../networking/virtual_private_cloud_config.rst:1326
+msgid "In the Port Forwarding node of the diagram, click View All."
+msgstr "在图表的端口转发节点，点击查看所有。"
+
+# 0dae384f57174980aacd91725f200202
+#: ../../networking/virtual_private_cloud_config.rst:1332
+msgid ""
+"**Public Port**: The port to which public traffic will be addressed on the "
+"IP address you acquired in the previous step."
+msgstr "**公用端口**: 你在前面操作所获取的供公共流量使用的公用IP地址的端口。 "
+
+# e58b66b804154984ac2848feded76f18
+#: ../../networking/virtual_private_cloud_config.rst:1335
+msgid ""
+"**Private Port**: The port on which the instance is listening for forwarded "
+"public traffic."
+msgstr "**私有端口**: 虚拟机实例将被转发到公共流量的监听端口。"
+
+# fdf35395971c43d7b03e9bf1a85afd10
+#: ../../networking/virtual_private_cloud_config.rst:1338
+msgid "**Protocol**: The communication protocol in use between the two ports."
+msgstr "**Protocol**: 两个端口之间所用的互联协议。"
+
+# 3488a82bf48c43dbbcf214cbc6915803
+#: ../../networking/virtual_private_cloud_config.rst:1341
+msgid "TCP"
+msgstr "TCP"
+
+# 65fd29db5c09403aad6a2b1688af4414
+#: ../../networking/virtual_private_cloud_config.rst:1343
+msgid "UDP"
+msgstr "UDP"
+
+# 3092d0bc5e29456e9c83bf700d0989ed
+#: ../../networking/virtual_private_cloud_config.rst:1345
+msgid ""
+"**Add VM**: Click Add VM. Select the name of the instance to which this rule"
+" applies, and click Apply."
+msgstr "**Add VM**: 点击增加虚拟机，选择你想将此规则应用上的虚拟机，点击应用。"
+
+# 957a6544516446768dd3e34e10b081d8
+#: ../../networking/virtual_private_cloud_config.rst:1348
+msgid "You can test the rule by opening an SSH session to the instance."
+msgstr "你可以通过SSH连接实例来测试此规则。"
+
+# fa091c39660d4a79ad8d7663f777f9b0
+#: ../../networking/virtual_private_cloud_config.rst:1352
+msgid "Removing Tiers"
+msgstr "删除层"
+
+# 23a5734e02084bdcb2075d5b7ff872ef
+#: ../../networking/virtual_private_cloud_config.rst:1354
+msgid ""
+"You can remove a tier from a VPC. A removed tier cannot be revoked. When a "
+"tier is removed, only the resources of the tier are expunged. All the "
+"network rules (port forwarding, load balancing and staticNAT) and the IP "
+"addresses associated to the tier are removed. The IP address still be "
+"belonging to the same VPC."
+msgstr "你可以从一个VPC中删除一个层。一个被删除的层是不能被擦除的。当一个层被删除后，只有层的资源被删去。所有的网络规则(端口转发，负载均衡，静态NAT)还有关联到此层的IP地址都会删除。但这些IP地址仍然属于这个VPC。"
+
+# 9b3b9eb7db0b4fc3983bc9bd94eb5f2c
+#: ../../networking/virtual_private_cloud_config.rst:1372
+msgid ""
+"The Configure VPC page is displayed. Locate the tier you want to work with."
+msgstr "配置VPC的页面显示出来了。指向你需要操作的层。"
+
+# b4b3c46f5c7c43d2a38281a25cff0a95
+#: ../../networking/virtual_private_cloud_config.rst:1375
+msgid "Select the tier you want to remove."
+msgstr "选择你想删除的层。"
+
+# 1c7ac4dbb28d46be86f3ab4794676d8c
+#: ../../networking/virtual_private_cloud_config.rst:1377
+msgid ""
+"In the Network Details tab, click the Delete Network button. |del-tier.png|"
+msgstr "在网络详细栏，点击删除网络按钮。|del-tier.png|"
+
+# b2a09950453549488f1a8233090286dd
+#: ../../networking/virtual_private_cloud_config.rst:1380
+msgid "Click Yes to confirm. Wait for some time for the tier to be removed."
+msgstr "点击YES按钮。稍等片片刻，层就会被删除了。"
+
+# 4dc06c7515ba4393856799669ecf6a8a
+#: ../../networking/virtual_private_cloud_config.rst:1384
+msgid "Editing, Restarting, and Removing a Virtual Private Cloud"
+msgstr "编辑，重启，删除VPC。"
+
+# c61c02b8451b4d52bc9e0b8232ce8d73
+#: ../../networking/virtual_private_cloud_config.rst:1386
+msgid "Ensure that all the tiers are removed before you remove a VPC."
+msgstr "在删除VPC前，需要先删除所有的层。"
+
+# 7e354bd7277d4569a94e6a022ae111e5
+#: ../../networking/virtual_private_cloud_config.rst:1397
+msgid "Select the VPC you want to work with."
+msgstr "选择你需要的VPC。"
+
+# 4e23279e59874fcdb4e38c54c1054efa
+#: ../../networking/virtual_private_cloud_config.rst:1399
+msgid "In the Details tab, click the Remove VPC button |remove-vpc.png|"
+msgstr "在详细栏，点击删除VPC按钮。|remove-vpc.png|"
+
+# 3227af3c60cb400c8679fd84202d852a
+#: ../../networking/virtual_private_cloud_config.rst:1401
+msgid ""
+"You can remove the VPC by also using the remove button in the Quick View."
+msgstr "你也可以在快速查看视图里点击删除按钮进行VPC的删除。"
+
+# 0e3026db29aa4e3780f95b598c5483fc
+#: ../../networking/virtual_private_cloud_config.rst:1404
+msgid ""
+"You can edit the name and description of a VPC. To do that, select the VPC, "
+"then click the Edit button. |vpc-edit-icon.png|"
+msgstr ""
+
+# 5d731df0a6ca4174a2b9f85dba537a8a
+#: ../../networking/virtual_private_cloud_config.rst:1407
+msgid ""
+"To restart a VPC, select the VPC, then click the Restart button. |restart-"
+"vpc.png|"
+msgstr "如果要重启一个VPC，点击重启按钮。|restart-vpc.png|"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking2.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking2.mo
new file mode 100644
index 0000000..20f8247
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking2.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking2.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking2.po
new file mode 100644
index 0000000..f2a12a8
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking2.po
@@ -0,0 +1,8448 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+# aguncn <aguncn@163.com>, 2014
+# renoshen <shenkuan-ghq@sinosig.com>, 2014
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:08-0400\n"
+"PO-Revision-Date: 2014-05-08 08:01+0000\n"
+"Last-Translator: aguncn <aguncn@163.com>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 4c134b7a710148a3ab2766ead2eecc37
+#: ../../networking2.rst:18
+msgid "Managing Networks and Traffic"
+msgstr "网络和流量管理"
+
+# 3dea6f52fda445569cf65ce098c1b84c
+#: ../../networking2.rst:20
+msgid ""
+"In a CloudStack, guest VMs can communicate with each other using shared "
+"infrastructure with the security and user perception that the guests have a "
+"private LAN. The CloudStack virtual router is the main component providing "
+"networking features for guest traffic."
+msgstr "在CLOUDSTACK中，客户虚拟机之间可以在共享构架下相互通讯，并且可以在一个私有LAN中实现安全和用户互通。CLOUDSTACK的虚拟路由器是实现客户网络功能的主要组件。"
+
+# c845ad86dd2c41e091ae6234539d6672
+#: ../../networking2.rst:26
+msgid "Guest Traffic"
+msgstr "来宾流量"
+
+# d8fc8ee73a5d4bc5915b1fd2e4eb7108
+#: ../../networking2.rst:28
+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 "在同一个区域内，客户虚拟机之间可以互访，但在不同的区域内，客户虚拟机之间不可以通过（内网）IP地址互访，而只能通过公网IP路由才可以互连。"
+
+# e56f7eded9f441659c145763662800d5
+#: ../../networking2.rst:33
+msgid "See a typical guest traffic setup given below:"
+msgstr "下图是一个典型的来宾流量设置："
+
+# 6823c848cad04848a61dbff31215055b
+#: ../../networking2.rst:35
+msgid "|guest-traffic-setup.png|"
+msgstr "|guest-traffic-setup.png|"
+
+# 5cc5110f1ee142468aaacae83aca4060
+#: ../../networking2.rst:37
+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 router. Its eth2 interface is assigned a"
+" public IP address for public traffic. If multiple public VLAN is used, the "
+"router will have multiple public interfaces."
+msgstr "通常，管理服务器会自动为每一个网络建立一个虚拟路由。一个虚拟路由实际上就是运行在物理主机上的一台特殊的虚拟机。每一台在一个独立网络中的虚拟路由有3个网口。如果使用多个公共 VLAN，相应的这台路由器就有多个公共的网口。 它的 eth0 网口是提供客户机通信的网关服务的，它的IP地址是 10.1.1.1。eth1 网口是为系统来配置这个虚拟路由而提供的。eth2 网口被赋予一个公共 IP 地址用来实现外部的公共通信。 同样如果使用了多个公共 VLAN 接入，这台路由器将会拥有多个公共的网口。"
+
+# b252663b377641b6a497a33ae549a1c3
+#: ../../networking2.rst:48
+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 "虚拟路由器提供DHCP功能，能自动的为每一个客户虚拟机在预先定义好的IP范围之内分配IP地址。用户也可以为虚拟机手工配置不同的IP地址。"
+
+# 08366e677b394ff486de117a98b53a1c
+#: ../../networking2.rst:53
+msgid ""
+"Source NAT is automatically configured in the virtual router to forward "
+"outbound traffic for all guest VMs"
+msgstr "Source NAT功能是在虚拟路由里自动配置好的，它可以转发所有来宾虚拟机的外出流量。"
+
+# 8db3692749f44d209bc4b6643b4bed42
+#: ../../networking2.rst:57
+msgid "Networking in a Pod"
+msgstr "一个提供点里的网络"
+
+# f92d73cb904740b69bb3044663745ef9
+#: ../../networking2.rst:59
+msgid ""
+"The figure below illustrates network setup within a single pod. The hosts "
+"are connected to a pod-level switch. At a minimum, the hosts should have one"
+" physical uplink to each switch. Bonded NICs are supported as well. The pod-"
+"level switch is a pair of redundant gigabit switches with 10 G uplinks."
+msgstr "下图演示了一个单提供点的网络配置。主机均连接到提供点层级的交换机。每一个主机至少有一个物理网卡连接到交换机。当然，这种环境也支持网卡绑定。提供点层级的交换机由两个1000M冗余组成，它们通过10G线路上联。"
+
+# 3cf0b62b19c942899bbf90f9c3e111be
+#: ../../networking2.rst:65
+msgid "|networksinglepod.png|"
+msgstr "|networksinglepod.png|"
+
+# 61fa2a0f3f6046b2a1d038ab3e5ea255
+#: ../../networking2.rst:67
+msgid "Servers are connected as follows:"
+msgstr "服务器以如下形式连接："
+
+# 9dd3a988270c471db1794e964c4a56c7
+#: ../../networking2.rst:71
+msgid ""
+"Storage devices are connected to only the network that carries management "
+"traffic."
+msgstr "存储设备只与管理网络连接。"
+
+# 2e2c8c8881fa4cd5be1de3eec14c1d1c
+#: ../../networking2.rst:76
+msgid ""
+"Hosts are connected to networks for both management traffic and public "
+"traffic."
+msgstr "主机同时与管理网络和公共网络连接。"
+
+# 3e2f4aed8c924b9e80395bdf1e1c2f73
+#: ../../networking2.rst:81
+msgid ""
+"Hosts are also connected to one or more networks carrying guest traffic."
+msgstr "主机也与一个或多个来宾网络连接。"
+
+# d85f7dccd3784410a2b1d16863f27a73
+#: ../../networking2.rst:84
+msgid ""
+"We recommend the use of multiple physical Ethernet cards to implement each "
+"network interface as well as redundant switch fabric in order to maximize "
+"throughput and improve reliability."
+msgstr "我们推荐用多个物理网卡以改进性能，也推荐用冗余的光纤交换机以改进网络可靠性。"
+
+# d776e46765c84e1181b3e580c688c626
+#: ../../networking2.rst:89
+msgid "Networking in a Zone"
+msgstr "一个区域里的网络"
+
+# d239d21a20c649aba205a75b8c13f10d
+#: ../../networking2.rst:91
+msgid ""
+"The following figure illustrates the network setup within a single zone."
+msgstr "下图说明了一个单一区域内的网络设置。"
+
+# a576182d84c04ab98566ba031289abb1
+#: ../../networking2.rst:93
+msgid "|networksetupzone.png|"
+msgstr "|networksetupzone.png|"
+
+# f9ec1f6b949e428b918524444e4e4c2d
+#: ../../networking2.rst:95
+msgid ""
+"A firewall for management traffic operates in the NAT mode. The network "
+"typically is assigned IP addresses in the 192.168.0.0/16 Class B private "
+"address space. Each pod is assigned IP addresses in the 192.168.\\*.0/24 "
+"Class C private address space."
+msgstr "用于管理通信的防火墙工作在NAT模式。通常是分配给网络中的IP地址192.168.0.0/16 B类私有地址空间。每个机柜（POD）分配的IP地址是192.168.*.0/24 C类私有地址空间。"
+
+# f0acacb8a1ac4f92b32c742e22c0aa30
+#: ../../networking2.rst:100
+msgid ""
+"Each zone has its own set of public IP addresses. Public IP addresses from "
+"different zones do not overlap."
+msgstr "每个区域都有自己的一套公网IP地址。来自不同区域的公网IP地址不重叠。"
+
+# 48df0d18a8e448909a0b484414468735
+#: ../../networking2.rst:104
+msgid "Basic Zone Physical Network Configuration"
+msgstr "基本区域物理网络配置"
+
+# 20494f4a5f604216bed0571fa51a7ddb
+#: ../../networking2.rst:106
+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 "在一个基本的网络中，物理网络的配置非常直接明了。你只需要配置一个客户网络（虚拟）以承载由客户虚拟机产生的流量。当你首次增加一个区域（Zone）到 CloudStack 中，你通过添加域（Add Zone）页面来设置客户网络（虚拟）。"
+
+# b5ca7152b69d4a2d8fcc434cb9267f7c
+#: ../../networking2.rst:112
+msgid "Advanced Zone Physical Network Configuration"
+msgstr "高级区域物理网络的配置"
+
+# 954218a2f4204be989c2436ecd73edc1
+#: ../../networking2.rst:114
+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 "在使用复杂网络的区域中，你需要告知管理服务器，为了实现隔离不同类型的通讯，物理网络是如何设置的。"
+
+# b3ba0f73a0df4d36a3cb4f204c4dee2d
+#: ../../networking2.rst:119
+msgid "Configure Guest Traffic in an Advanced Zone"
+msgstr "在高级域中设置客户通信"
+
+# ecd9d16a0a0c4dff9373a2dbf58e4c09
+#: ../../networking2.rst:121
+msgid ""
+"These steps assume you have already logged in to the CloudStack UI. To "
+"configure the base guest network:"
+msgstr "下面的步骤假定你已经登录进入 CloudStack 的界面。设置基本的客户网络："
+
+# 78523deb5f20412383b00c879c3b21aa
+#: ../../networking2.rst:126
+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 "在左边的导航栏，选择基础架构。在区域界面点击查看全部，然后点击你要添加网络的区域。"
+
+# 6257a61390924cb3bd8aeeac1a071780
+# 991bb1da835442988405cc08b7001c28
+# 61c9a678d28f40d599b72b6c2670f13d
+#: ../../networking2.rst:131 ../../networking2.rst:215
+#: ../../networking2.rst:1597
+msgid "Click the Network tab."
+msgstr "点击网络选项卡。"
+
+# 81ea8b8553864a83843ba71e6bf101af
+# 2d5debf29d7e42428b6c6d0ea25b7b92
+# e156f160e7c64f60a6d9c5bd8b8164a9
+#: ../../networking2.rst:135 ../../networking2.rst:219
+#: ../../networking2.rst:1601
+msgid "Click Add guest network."
+msgstr "点击 添加来宾网络。"
+
+# 7b664064e09a4c25ac5afbc839d6bf94
+#: ../../networking2.rst:137
+msgid "The Add guest network window is displayed:"
+msgstr "添加来宾网络窗口显示："
+
+# 467663954a4745be91a92b1d95b23080
+#: ../../networking2.rst:139
+msgid "|addguestnetwork.png|"
+msgstr "|addguestnetwork.png|"
+
+# a7bd588835354863bf7622de307358f6
+# e19b9c5096354c629c5cb237adbb7845
+# d0d70642a5104df08ab13289bdd0c02b
+#: ../../networking2.rst:143 ../../networking2.rst:4200
+#: ../../networking2.rst:5082
+msgid "Provide the following information:"
+msgstr "填写以下内容："
+
+# 02150922f26d47f3b7a13ca653f96421
+#: ../../networking2.rst:147
+msgid "**Name**. The name of the network. This will be user-visible"
+msgstr "“Name”。要建立的网络结构的名字。这个是用户可见的"
+
+# 71b93ff5fc154455a9e31bb96fc71d72
+#: ../../networking2.rst:151
+msgid ""
+"**Display Text**: The description of the network. This will be user-visible"
+msgstr "“Display Text”：网络的描述。用户可见"
+
+# 3aa2ff94b2f3453caf3cf8a60cf57294
+#: ../../networking2.rst:156
+msgid "**Zone**: The zone in which you are configuring the guest network."
+msgstr "“Zone”: 这里的区域是指你要配置客户网络的区域。"
+
+# 8020d9a242d94611b622a7fbbf730632
+#: ../../networking2.rst:160
+msgid ""
+"**Network offering**: If the administrator has configured multiple network "
+"offerings, select the one you want to use for this network"
+msgstr "“网络提议”: 如果管理员已经配置了多个网络方案，可以选择你需要的那个"
+
+# 409cf198865e4ed4a4ceda18fb9c08f8
+#: ../../networking2.rst:165
+msgid "**Guest Gateway**: The gateway that the guests should use"
+msgstr "“Guest gateway”：虚拟机需要使用的网关"
+
+# 1b24f9a1dc1a468fa60412939100a476
+#: ../../networking2.rst:169
+msgid ""
+"**Guest Netmask**: The netmask in use on the subnet the guests will use"
+msgstr "“Guest Netmask”：客户虚拟机会使用的子网掩码"
+
+# 91173c96c5184ed8a0542f56f340c125
+# 6968c572935348d89aa2cfe9419c00cd
+# 9ee0ac806d854e47bd3f486e9e128034
+# 5d45344f6070463bb25599b8c1ac7145
+# 0527e80fdbfe4508a05ede62a047cd51
+# c6016b8b267942548713429d3c7e74e0
+# 3ccbb578962b42588bd495e0dbd57f76
+# f5954071e2a24961b74b3dcca98a33b1
+# e6ab2eac57564f63bfeea06d1691c574
+# 6d9b635b27544fb3adc30d7e8bc3070b
+# aae381906435443489b7db544138dc66
+# 0218e655795843808690f324bad3bbf9
+# 2c8c3e70a3904e0fb57a195a43305818
+# bc97ad0f132944ffbb337c4649b00a51
+#: ../../networking2.rst:174 ../../networking2.rst:870
+#: ../../networking2.rst:1251 ../../networking2.rst:1428
+#: ../../networking2.rst:1755 ../../networking2.rst:3144
+#: ../../networking2.rst:3662 ../../networking2.rst:4319
+#: ../../networking2.rst:4355 ../../networking2.rst:5118
+#: ../../networking2.rst:5211 ../../networking2.rst:5458
+#: ../../networking2.rst:5499 ../../networking2.rst:6953
+msgid "Click OK."
+msgstr "点击确定。"
+
+# bb8994cf25ed4d0f9c1738b0a288a66d
+#: ../../networking2.rst:177
+msgid "Configure Public Traffic in an Advanced Zone"
+msgstr "在高级区域中配置公共通信"
+
+# 53d266b50a684d08b2b57469d0ba2117
+#: ../../networking2.rst:179
+msgid ""
+"In a zone that uses advanced networking, you need to configure at least one "
+"range of IP addresses for Internet traffic."
+msgstr "在一个使用高级网络配置的区域中，你需要配置至少一个用于Internet通信的IP地址范围。"
+
+# 173ecef5b8d34d51b8690fdff5bcfc1f
+#: ../../networking2.rst:183
+msgid "Configuring a Shared Guest Network"
+msgstr "配置共享的客户网络"
+
+# 93a4d181244541b381a3a70d1daea74e
+# 55cf11dd995e463eb0015820a7998825
+# 648d4dddf66542dd975f89802e4efaec
+#: ../../networking2.rst:187 ../../networking2.rst:761
+#: ../../networking2.rst:1569
+msgid "Log in to the CloudStack UI as administrator."
+msgstr "作为管理员登录到CloudStack用户界面。"
+
+# ef46dafa14464c0580eef19b6347e754
+# f88933a8ce404a74b4dbfb012972639e
+# 1a1e2e9b76e842d2ad6653556d716440
+#: ../../networking2.rst:191 ../../networking2.rst:1363
+#: ../../networking2.rst:1573
+msgid "In the left navigation, choose Infrastructure."
+msgstr "在左边的导航，选择基础架构。"
+
+# e6266ec66e47425eaefdebd94b55e3d6
+# 9b6fa85ad73145c2a68b917e13c4dd74
+#: ../../networking2.rst:195 ../../networking2.rst:1577
+msgid "On Zones, click View More."
+msgstr "在区域页面，点击查看全部。"
+
+# ae18ac4302694c399605762c754adc89
+# a83fd7a01a4d4702815c49eabf8d6f45
+#: ../../networking2.rst:199 ../../networking2.rst:1581
+msgid "Click the zone to which you want to add a guest network."
+msgstr "选择要添加客户网络的那个区域。"
+
+# 35ace6a71a514813adb835b0e291e59a
+# 92a70044e0a64276aca71c727238658c
+# e7a6054e0cac452abbdf14af1fcf9ab7
+# 1dc7e2ce80f242c792c3eadfdf57d1f8
+#: ../../networking2.rst:203 ../../networking2.rst:777
+#: ../../networking2.rst:898 ../../networking2.rst:1585
+msgid "Click the Physical Network tab."
+msgstr "点击物理网络标签卡。"
+
+# 7d1c35e3c6fb45268f88743d4f33fc4a
+# 5d24c24102dc463b8df955cea14e8321
+#: ../../networking2.rst:207 ../../networking2.rst:1589
+msgid "Click the physical network you want to work with."
+msgstr "选择您要操作的物理网络。"
+
+# d69f9202aba443119708b15355371054
+# b50eb62ce8e94fdf956d6c49a9d8c539
+#: ../../networking2.rst:211 ../../networking2.rst:1593
+msgid "On the Guest node of the diagram, click Configure."
+msgstr "在客户节点界面，点击配置。"
+
+# 61f94d523e2b4257ac005b54b2300cd1
+# e69e4aa9dc5d4b77b59760f32d4410e5
+#: ../../networking2.rst:221 ../../networking2.rst:1603
+msgid "The Add guest network window is displayed."
+msgstr "现实添加客户网络窗口。"
+
+# 4af18c5d61a6456caf73f7a9369e2fee
+# cd3004192b7247d6b3d8df85d071c687
+# cefbbdc700e1418791c24fa0e9ff9991
+# 7d7d79ee61514455a6bd14b72d23c697
+# 9eddccf9e3ed490ba485fed483665910
+# ad7396c2fa194389a72869772975a651
+# ba22f3a686da4d51be0844159353ec45
+# 813ce0c39bee45a6b48988f7b8abcccd
+# 49c644d753054859b04b0040656835a6
+# 6851774e7c7b4a888987619af18e594a
+# 5bb2026725a84546bbf11325cca1e760
+# ca837cbb6534464a8d34b465a79f3b42
+# 1766498324004d1b9d70c399f1671335
+# 3fcb97db48704b65b73bdf48cfc719df
+#: ../../networking2.rst:225 ../../networking2.rst:806
+#: ../../networking2.rst:822 ../../networking2.rst:856
+#: ../../networking2.rst:916 ../../networking2.rst:1227
+#: ../../networking2.rst:1400 ../../networking2.rst:1607
+#: ../../networking2.rst:2480 ../../networking2.rst:3177
+#: ../../networking2.rst:5166 ../../networking2.rst:5592
+#: ../../networking2.rst:6347 ../../networking2.rst:6741
+msgid "Specify the following:"
+msgstr "指定以下信息："
+
+# 8779be8d9d6846f085dbce3da3461bc3
+# b0b915aaeb67486684b659dc291d6454
+#: ../../networking2.rst:229 ../../networking2.rst:1611
+msgid "**Name**: The name of the network. This will be visible to the user."
+msgstr "“Name”。要建立的网络的名字。这个是用户可见的"
+
+# 5074f17c728f4f3a8a7f794e8374c034
+# 0a5db820304048068d1845c134b8df63
+#: ../../networking2.rst:234 ../../networking2.rst:1616
+msgid ""
+"**Description**: The short description of the network that can be displayed "
+"to users."
+msgstr "**描述**: 提供一个简短的方案描述。 "
+
+# 2b82a4bc6aa046f3b00d043934c959d7
+# 41c1edb5305a4945842709a1c5cf1ad6
+#: ../../networking2.rst:239 ../../networking2.rst:1621
+msgid "**VLAN ID**: The unique ID of the VLAN."
+msgstr "“VLAN ID”：VLAN 的ID。"
+
+# 418bb2fcab5742fb987163b73807d96b
+#: ../../networking2.rst:243
+msgid "**Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr "“Isolated VLAN ID”: 二级独立 VLAN 的 ID。"
+
+# f26b6b49568f43ac84898deb5855609f
+# 969c263588994f74ac62592a499a4b31
+#: ../../networking2.rst:248 ../../networking2.rst:1633
+msgid "**Scope**: The available scopes are Domain, Account, Project, and All."
+msgstr "“Scope”：可用的范围，包括域，帐户，项目和其他所以。"
+
+# 178c532fedf44f0fb1a2993bf0f625a0
+# 15faa541a4ce4327913cfce7e0c3f217
+#: ../../networking2.rst:253 ../../networking2.rst:1638
+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 "“Domain”：域，指定客户网络范围的域。指定域中的网络相对其他域是隔离不可见的。如果指定子域访问，域中的客户网络将在所有的子域中可用。"
+
+# 91422a2eb500489a88e0a6f4b976e5c8
+# eb7d195938c445079e17b8d4de34c9b0
+#: ../../networking2.rst:261 ../../networking2.rst:1646
+msgid ""
+"**Account**: The account for which the guest network is being created for. "
+"You must specify the domain the account belongs to."
+msgstr "“Account”：这里的帐户是为建立客户网络所指定的。必须指定域中所属的帐户。"
+
+# acbed03163c746f394f0b6065ac5d267
+# b6481103a23442a698dd33a8241fd4a5
+#: ../../networking2.rst:267 ../../networking2.rst:1652
+msgid ""
+"**Project**: The project for which the guest network is being created for. "
+"You must specify the domain the project belongs to."
+msgstr "“Project”：项目是客户网络所建立的项目。必须为这个项目指定域。"
+
+# 7515546501ea4a229f3d24cb1957114c
+# 14055c49cff34a97af7586b6692b395f
+#: ../../networking2.rst:273 ../../networking2.rst:1658
+msgid ""
+"**All**: The guest network is available for all the domains, account, "
+"projects within the selected zone."
+msgstr "“All”：选择它，会让客户网络对这个区域（Zone）中的所有域，帐户和项目都可用。"
+
+# 9e7d75c438d04916a6c8e41212a5add4
+# d311a00faddf44fb969a7362e8525846
+#: ../../networking2.rst:278 ../../networking2.rst:1663
+msgid ""
+"**Network Offering**: If the administrator has configured multiple network "
+"offerings, select the one you want to use for this network."
+msgstr "“网络提议”: 如果管理员已经配置了多个网络方案，可以选择你需要的那个。"
+
+# 3b34a00342f74aabb8f06ef47a71928f
+# cec7265b43cc44c985fc19c1aada24ca
+#: ../../networking2.rst:284 ../../networking2.rst:1669
+msgid "**Gateway**: The gateway that the guests should use."
+msgstr "“Guest gateway”：虚拟机需要使用的网关。"
+
+# e8b1ed0c13f24b28b17097da6a906553
+# e376b4730d514e9cb67f58490f5323da
+#: ../../networking2.rst:288 ../../networking2.rst:1673
+msgid "**Netmask**: The netmask in use on the subnet the guests will use."
+msgstr "“Netmask”：虚拟机子网要使用的网络掩码。"
+
+# e95322f93824448f8b5213679edb09a1
+# f9867bf0fe584ea68c8d8697b398a35d
+#: ../../networking2.rst:292 ../../networking2.rst:1677
+msgid ""
+"**IP Range**: A range of IP addresses that are accessible from the Internet "
+"and are assigned to the guest VMs."
+msgstr "“IP Range”：定义公网IP范围，这些IP用来访问公网或是从公网访问客户虚拟机。"
+
+# e30dfcdbb56b4fdab7ac50d318f8cfee
+#: ../../networking2.rst:295
+msgid ""
+"If one NIC is used, these IPs should be in the same CIDR in the case of "
+"IPv6."
+msgstr "如果使用了网卡，这些IP应该在相同的IPv6的CIDR中。"
+
+# c999c7758e4644bb960bd36b4934a153
+#: ../../networking2.rst:300
+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 "“IPv6 CIDR”：用于定义网络子网的网络前缀。"
+
+# 06222d5aca4f4401b3e50b9562eafd93
+# bdec8ee29ad7416da22dd28dfee5836c
+#: ../../networking2.rst:307 ../../networking2.rst:1682
+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 "\"网络域\":如果你想为客户虚机网络定义一个域名，在此处输入后缀名。"
+
+# 6cbf270deb434c49a37109538320e729
+# e3f042ecf42f48179722b1f43ed74365
+# 6a7ddea8dd2248ce9c184a2ecb2a727c
+# 3048777b2bf143b7b0cf2d931ebf1461
+# 007a1927e30b4659b6f5b8dad349a236
+#: ../../networking2.rst:313 ../../networking2.rst:1688
+#: ../../networking2.rst:3215 ../../networking2.rst:3256
+#: ../../networking2.rst:4559
+msgid "Click OK to confirm."
+msgstr "点击确定。"
+
+# 6dae7352ba9441b4ab5afb0eb736de8e
+#: ../../networking2.rst:316
+msgid "Using Multiple Guest Networks"
+msgstr "使用多个来宾网络"
+
+# 2b127f6d5dfd4f3aa7e896c69fa530fc
+#: ../../networking2.rst:318
+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 "在使用高级网络的资源域里, 额外的来宾网络可以在初始安装后任何时间添加. 你还可以通过指定DNS后缀为每个网络自定义关联的域名."
+
+# 57493d5abb6d42e29119db9cfbd72df0
+#: ../../networking2.rst:323
+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 "一个虚机的网络在其创建时定义. 当一个虚机创建以后, 就不能对其网络添加删除, 即便用户可以进入客户虚机删除指定网卡的IP地址."
+
+# df560b1f84f74fa096be5526e9f253c2
+#: ../../networking2.rst:328
+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 "每一个虚机只有一个默认的网络. 在这个默认网络里, 虚拟路由器的DHCP响应将设置客户的默认网关. 除了单一,必须的默认网络, 多个非默认的网络也可以添加到客户虚机里. 管理员可以控制哪个网络作为默认的网络."
+
+# 1b89ed0c211f490d9ab7e3873f785995
+#: ../../networking2.rst:334
+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 "附加的网络可以给所有账户使用或者分配给特定的账户. 对所有账户都可用的网络在整个资源域有效. 任何可以访问这个资源域的用户都可以使用这个网络创建虚机. 这些资源域一级的网络基本不提供客户之间的隔离. 分配给特定帐户的网络提供强制隔离的功能."
+
+# 03479d92c4f3472fbf1c837f78ae38b9
+#: ../../networking2.rst:342
+msgid "Adding an Additional Guest Network"
+msgstr "增添一个虚拟机的网络"
+
+# dcc9b20e05d94a90a82df638e638d914
+# bf1857069dbe437da757dd8117d7a8f6
+# b00f09bd670c4e6bb6a9d90b98d3ee27
+# 06d1f9568c404045a154fa7800b17b42
+# 3a1cc0396efd4b8ebd8a6128932f37f3
+# ded02e7a4c5d4431a40e7c763efe892e
+# 2bf9437aec83464ca8aa33fb4d5bc7d2
+# 474cb61b7d6d414bb525496395e11ac0
+# cf958678b40649e395bf748ed3a82341
+# c6386d8cdb7f4830ac34eb0e3d53d353
+# e419b4e20de34ab59ca3fd7119a6a509
+# cb96251ca7834bcfb93698899e36997c
+# c24de51d817f4b8b86aa10d3c56327e6
+# 1970352df0b24327ab0040b0248447d1
+# b69b28bceebf484d9240513871a69e53
+# efd7ff6f49f24baebd8a7054ca0fcb6a
+# 855b8ad33e0942859a9fb87da979bff6
+# b853131f26c84398bd3ab3b28e7c8c10
+# 0415ee973c9e4f138f81c716a5897661
+# a2d18d98840548f1994851b84a11d06b
+# dafb981c4cd44ff284f9609a6d78076f
+# 8b5b3770bbea4a4b91bce618eaa95579
+# 0f348eefc7a140f0bfa10c40ab0de750
+# 20e4bf643dc649a5adf2b96c98aad755
+# 229dd2bf881340558fca0975604b2643
+# 470f52bcfa37419386c12e3c2112f795
+# bbf8e4596d4c4216a94cb7fd144372c1
+# bbeffb28c2c749518103fe11d941e8f3
+# 910d29d282334e13b2f84bdba7e4ae2f
+# d94ff6f14e7643a9832ac593d1c69ffb
+# 534c0a26f9b24f54a399020a1716f7ed
+# e92cc9d2cd1d448e9f9d848b7a0f8851
+# a96d8dddd84c4103b8b7afff0db24cfe
+# e307dc8da8084a23951ba5a0f61c85d4
+# 538a9fc2f7b941d8831cf7952f1eac3f
+# a6c65c894c464e4f928395582357dc97
+# 786b76e0eb6b4cadba166292663da2ea
+# 6530063879054b16a643c0b8d345a236
+#: ../../networking2.rst:346 ../../networking2.rst:413
+#: ../../networking2.rst:478 ../../networking2.rst:509
+#: ../../networking2.rst:543 ../../networking2.rst:688
+#: ../../networking2.rst:1205 ../../networking2.rst:1258
+#: ../../networking2.rst:1359 ../../networking2.rst:1735
+#: ../../networking2.rst:1815 ../../networking2.rst:2210
+#: ../../networking2.rst:3284 ../../networking2.rst:3327
+#: ../../networking2.rst:3370 ../../networking2.rst:3444
+#: ../../networking2.rst:3548 ../../networking2.rst:3695
+#: ../../networking2.rst:3829 ../../networking2.rst:4184
+#: ../../networking2.rst:4329 ../../networking2.rst:4362
+#: ../../networking2.rst:4459 ../../networking2.rst:4650
+#: ../../networking2.rst:5066 ../../networking2.rst:5131
+#: ../../networking2.rst:5262 ../../networking2.rst:5344
+#: ../../networking2.rst:5513 ../../networking2.rst:5752
+#: ../../networking2.rst:5843 ../../networking2.rst:5931
+#: ../../networking2.rst:6022 ../../networking2.rst:6265
+#: ../../networking2.rst:6575 ../../networking2.rst:6659
+#: ../../networking2.rst:6784 ../../networking2.rst:6823
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# c650c895a3ac4ff2851197288859be98
+# 65e8807d38054bd1b0027a7155f8085f
+# 6cbdfa0e6a0e46cdab35e3223f504119
+# 2f9490cb25514f8283f8dec06a79102d
+# 5563fe265c1a429d967cda0edab813f4
+# 54d9e12cb3164286a92aceeba0a664e5
+# 612ff33bd3f84bdd84ef63b9c3cb6cf3
+# 6fc81420daf44701856963aa3d9f4a87
+# 07cefb7f05bc4714bf198cbd879aea33
+# ab72dbc455b843cfb4c72e923297fc4d
+# 2e8cbb1231ef43fb9b387b21b0f97305
+# 9cb098264bbf4fc79077a14d44ff4e4d
+# ceb0f3b90cd2499b89cc614d577384d9
+# f15f55387b954e10a6e5a4417bfa6071
+# c298749dee624dae9ac00c5329f45af3
+# e222d654cbbb4a0a9bfcec6a887925e2
+# aa6ece8cd97543d091148cc4a9db4c04
+# 412366a772fc462991958a94917d88ee
+# e838e4d54a33420fad3f9b5aac4181ea
+# ef4b5d8b2c1f4efcb1dcb0909dd0610b
+# fb954e22b2e247cfbf72c9525d556f10
+# e9064194f98e4db6bb1374bc04afd258
+# da3f29bc5aa344e99d840c524c97ff52
+# 931799f15e4f4ef78f34f77acc6a84a5
+# 0035008431074c10b6f9cdcd88cf746a
+# 7a1970bdf40a45d3acd7f9db64c34c2f
+# f9b9878b284a440380845f18adc4dc02
+# 1108ad1b0aa449c198fc5fbf7b2f6f72
+# cea2011545724bc2b72940d23a00d3d7
+#: ../../networking2.rst:350 ../../networking2.rst:553
+#: ../../networking2.rst:692 ../../networking2.rst:1262
+#: ../../networking2.rst:2214 ../../networking2.rst:3288
+#: ../../networking2.rst:3331 ../../networking2.rst:3374
+#: ../../networking2.rst:3448 ../../networking2.rst:3552
+#: ../../networking2.rst:4188 ../../networking2.rst:4333
+#: ../../networking2.rst:4366 ../../networking2.rst:4463
+#: ../../networking2.rst:4654 ../../networking2.rst:5070
+#: ../../networking2.rst:5135 ../../networking2.rst:5266
+#: ../../networking2.rst:5348 ../../networking2.rst:5517
+#: ../../networking2.rst:5756 ../../networking2.rst:5847
+#: ../../networking2.rst:5935 ../../networking2.rst:6026
+#: ../../networking2.rst:6269 ../../networking2.rst:6579
+#: ../../networking2.rst:6663 ../../networking2.rst:6788
+#: ../../networking2.rst:6827
+msgid "In the left navigation, choose Network."
+msgstr "在左侧的导航栏，选择网络。"
+
+# f6aa7a61ff37420d9f141635bdbce188
+#: ../../networking2.rst:354
+msgid "Click Add guest network. Provide the following information:"
+msgstr "地阿基添加来宾网络。提供以下信息："
+
+# 94e3451e541243a590fc75a1c6838168
+#: ../../networking2.rst:358
+msgid "**Name**: The name of the network. This will be user-visible."
+msgstr "**Name**：网络的名称。对于最终用户可见。"
+
+# 24a87a4d530b4a8c9af892bd51a53c2b
+#: ../../networking2.rst:362
+msgid ""
+"**Display Text**: The description of the network. This will be user-visible."
+msgstr "**Display Text**:网络的描述信息。对于最终用户可见。"
+
+# 4491ce6396264b9f805777eca895a720
+#: ../../networking2.rst:367
+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 "**Zone**：此网络所应用到zone的名称。每个zone都是一个广播域，因此每个zone中的来宾网络都有不同的IP范围。管理员必须为每个zone配置IP范围。"
+
+# 738c6e4f1dac40f6ae58cfa12e3fafb6
+#: ../../networking2.rst:374
+msgid ""
+"**Network offering**: If the administrator has configured multiple network "
+"offerings, select the one you want to use for this network."
+msgstr "**Network offering**如果管理员已经配置了多个网络，选择一个你想使用的。"
+
+# 4d5b30b8ae754940bd24bf9ce873f62c
+#: ../../networking2.rst:380
+msgid "**Guest Gateway**: The gateway that the guests should use."
+msgstr "**Guest Gateway**：来宾网络的网关。"
+
+# d2cc46c6e57d4a74b0f41b06645d7905
+#: ../../networking2.rst:384
+msgid ""
+"**Guest Netmask**: The netmask in use on the subnet the guests will use."
+msgstr "**Guest Netmask**：来宾网络的子网掩码。"
+
+# 0eef322a01b1441c968f5d08a7d1205d
+# 0fd1c8972f504925a86019b475f8cf7a
+#: ../../networking2.rst:389 ../../networking2.rst:4032
+msgid "Click Create."
+msgstr "点击创建。"
+
+# de4eb821eff84801b56973e967b9870e
+#: ../../networking2.rst:392
+msgid "Reconfiguring Networks in VMs"
+msgstr "在VMs中重新配置网络"
+
+# 0f2fe4ab745e4f7fb65fe812f7d64f1a
+#: ../../networking2.rst:394
+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 "CloudStack能让你在不同网络间移动VMs和重新配置VM的网络。你可以从一个网络中移除一个VM，再将其移动到另一个网络。"
+
+# 74ad1316798b4f60a8f0033d2c970d86
+#: ../../networking2.rst:400
+msgid "This feature is supported on XenServer, VMware, and KVM hypervisors."
+msgstr "XenServer、VMware和KVM hypervisors支持这个特性。"
+
+# 65c68a2b86274b91a6ec6ed32d0eb511
+# b0f423eb9e1444fa8072955fb8cbe955
+# c9a7dedb4fe74538a84d59bba4b0ea21
+#: ../../networking2.rst:403 ../../networking2.rst:1526
+#: ../../networking2.rst:2416
+msgid "Prerequisites"
+msgstr "先决条件"
+
+# bc2166808aa14a3d84e34f7a073eda9b
+#: ../../networking2.rst:405
+msgid ""
+"Ensure that vm-tools are running on guest VMs for adding or removing "
+"networks to work on VMware hypervisor."
+msgstr "确保虚拟机上安装了vm-tools以便通过VMware hypervisor添加或移除网络。"
+
+# 5edc5eb13c714fdcb4bc76dfefee938a
+#: ../../networking2.rst:409
+msgid "Adding a Network"
+msgstr "添加网络"
+
+# e9c46729b8e44e9b86983fc1d062228c
+# 69e1fa7916874968ad5f68de2af2cbc4
+# 53892275c4d84a16b7aa19e912822afe
+#: ../../networking2.rst:417 ../../networking2.rst:482
+#: ../../networking2.rst:513
+msgid "In the left navigation, click Instances."
+msgstr "在左侧的导航菜单中，点击实例。"
+
+# 237aa96a8b6047e2abb22526bd4bac7c
+# 2b3f21ea21b24697b7196dc8f6846009
+# 274e34eca30542b289b9dccb8063fa1f
+#: ../../networking2.rst:421 ../../networking2.rst:486
+#: ../../networking2.rst:517
+msgid "Choose the VM that you want to work with."
+msgstr "选择你要处理的VM。"
+
+# a616e6054be2484499468033d21dea1c
+# 7df447c421184ebd8362e78e05a81058
+# 57cb30b5f480462abef7c6f73b23f46e
+#: ../../networking2.rst:425 ../../networking2.rst:490
+#: ../../networking2.rst:521
+msgid "Click the NICs tab."
+msgstr "点击网络适配器标签。"
+
+# dccdbd5be35b43fda6baf17f2c628af7
+#: ../../networking2.rst:429
+msgid "Click Add network to VM."
+msgstr "将网络添加到 VM"
+
+# 05af00bbbfae48b0869d614090792531
+#: ../../networking2.rst:431
+msgid "The Add network to VM dialog is displayed."
+msgstr "显示添加网络对话框。"
+
+# 9d15b4dcf3c8457785334338c368aa26
+#: ../../networking2.rst:435
+msgid ""
+"In the drop-down list, select the network that you would like to add this VM"
+" to."
+msgstr "在下拉列表里选择你要添加给VM的网络。"
+
+# 9747107d35eb413e81aa96529adf5506
+#: ../../networking2.rst:438
+msgid ""
+"A new NIC is added for this network. You can view the following details in "
+"the NICs page:"
+msgstr "这样就为这个网络添加了一个新网卡。你可以在网卡页面查看下列信息："
+
+# 96ffcc74f3da41ee9f7fade2c284e2cc
+#: ../../networking2.rst:443
+msgid "ID"
+msgstr "ID"
+
+# 0930c07f915e4e8f8321b47ce1b2546c
+#: ../../networking2.rst:447
+msgid "Network Name"
+msgstr "网络名称"
+
+# 2166ea3836e64777968d20d97a551782
+#: ../../networking2.rst:451
+msgid "Type"
+msgstr "类型"
+
+# ebba5967ce5b40c6a4b9557338f01ce6
+# 3d4b724e0c8241c1ba31b6395bc04008
+# 5af256fd3dbb4fdd841ef05a4ec9b838
+#: ../../networking2.rst:455 ../../networking2.rst:4442
+#: ../../networking2.rst:4567
+msgid "IP Address"
+msgstr "IP地址"
+
+# a5e87e2a4b4d4ddd80f323f49ceee587
+# ad200504779f4909905c825a837ecb20
+#: ../../networking2.rst:459 ../../networking2.rst:4571
+msgid "Gateway"
+msgstr "网关"
+
+# b15a081ce5664e48891a6f018aa8f161
+#: ../../networking2.rst:463
+msgid "Netmask"
+msgstr "子网掩码"
+
+# 297b7172628240e1a2c5b8cabc302f62
+#: ../../networking2.rst:467
+msgid "Is default"
+msgstr "默认的"
+
+# 8a2efed9a7e74c7f9fe0f1d5eb5d090c
+#: ../../networking2.rst:471
+msgid "CIDR (for IPv6)"
+msgstr "CIDR（IPv6）"
+
+# 9398952782e64b64b3867a3fe12fd7bc
+#: ../../networking2.rst:474
+msgid "Removing a Network"
+msgstr "移除网络"
+
+# a093eadb6ac145cbae36f5faaaa2c9a1
+#: ../../networking2.rst:494
+msgid "Locate the NIC you want to remove."
+msgstr "找到你要移除的网卡上。"
+
+# 5785d874c0944a0caf08db20f4f9e446
+#: ../../networking2.rst:498
+msgid "Click Remove NIC button. |remove-nic.png|"
+msgstr "点击移除网卡按钮。|remove-nic.png|"
+
+# c2771766c44443d1bb463bd5a0f9ecef
+# ed60114d9fff4ae6871302c0c6b0aed2
+#: ../../networking2.rst:502 ../../networking2.rst:533
+msgid "Click Yes to confirm."
+msgstr "点击Yes确认。"
+
+# 6b25b8b44f294113afdfb3b97d2eac02
+#: ../../networking2.rst:505
+msgid "Selecting the Default Network"
+msgstr "选择默认网络"
+
+# 86d95a73e3274acc9285a47537212537
+#: ../../networking2.rst:525
+msgid "Locate the NIC you want to work with."
+msgstr "找到你想要的网卡。"
+
+# 998ed551fd1a45f4ac897f9f38552afe
+#: ../../networking2.rst:529
+msgid "Click the Set default NIC button. |set-default-nic.png|."
+msgstr "点击设置为默认网卡按钮。 |set-default-nic.png|."
+
+# df5fbaabb7364cf599673d6b129dc3a4
+#: ../../networking2.rst:536
+msgid "Changing the Network Offering on a Guest Network"
+msgstr "在来宾网络上更改网络方案"
+
+# 7fc2bd82deb7433b8d2b5f310500de46
+#: ../../networking2.rst:538
+msgid ""
+"A user or administrator can change the network offering that is associated "
+"with an existing guest network."
+msgstr "用户或者管理员可以更改与之相关的来宾网络的网络方案。"
+
+# 9961a724d3c9484ca0b4c1d5978d448c
+#: ../../networking2.rst:547
+msgid ""
+"If you are changing from a network offering that uses the CloudStack virtual"
+" router to one that uses external devices as network service providers, you "
+"must first stop all the VMs on the network."
+msgstr "如果你将使用CloudStack虚拟路由的一个网络方案改成使用公共网络设备作为网络服务商，那么你必须先关掉该网络中的所有虚机。"
+
+# 449cac531ff847d796c389fb42f64c5c
+# 44aa044295ce4f078b84c89406c09bb3
+#: ../../networking2.rst:557 ../../networking2.rst:696
+msgid "Click the name of the network you want to modify."
+msgstr "点击你要修改的网络名称。"
+
+# 013515a624984a4181813aa619128c01
+# fb4f4c6fee5a4d54a8210453ae8fea0b
+#: ../../networking2.rst:561 ../../networking2.rst:700
+msgid "In the Details tab, click Edit. |edit-icon.png|"
+msgstr "在 详细 页签，点击 编辑按钮。|edit-icon.png|"
+
+# 2af58d6970ae4fa49f1d797131ae88e5
+#: ../../networking2.rst:565
+msgid ""
+"In Network Offering, choose the new network offering, then click Apply."
+msgstr "在网络方案中，选择新的网络方案，然后点击应用。"
+
+# bc3a2c3c3d324782ae47b4da0e17c214
+#: ../../networking2.rst:568
+msgid ""
+"A prompt is displayed asking whether you want to keep the existing CIDR. "
+"This is to let you know that if you change the network offering, the CIDR "
+"will be affected."
+msgstr "这时会有一个提示问你是否保持已存在的CIDR不变。这是让你了解如果你改变网络了方案，那么CIDR会受到影响。"
+
+# 1b6db56bbeec4098851005614591b4f2
+#: ../../networking2.rst:572
+msgid ""
+"If you upgrade between virtual router as a provider and an external network "
+"device as provider, acknowledge the change of CIDR to continue, so choose "
+"Yes."
+msgstr "如果你将虚拟路由升级到外网设备，在看到变更CIDR以继续时，请选择Yes。"
+
+# 146e4502698d4bedb783dec26532e410
+#: ../../networking2.rst:578
+msgid ""
+"Wait for the update to complete. Don't try to restart VMs until the network "
+"change is complete."
+msgstr "等待更新完成。在网络变更完成之前不要试图重启虚拟机。"
+
+# 4ae7ada6f8e841c4bab421568ca6c79c
+#: ../../networking2.rst:583
+msgid "If you stopped any VMs, restart them."
+msgstr "如果你停止了任何VMs，请重启他们。"
+
+# 9725e5abe5b24d5b9b938be30e1e60f9
+#: ../../networking2.rst:586
+msgid "IP Reservation in Isolated Guest Networks"
+msgstr "隔离的来宾网络中的预留IP"
+
+# 2160ad6d081d44638ebbdfb06dbfae1f
+#: ../../networking2.rst:588
+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 "在隔离的来宾网络中，来宾IP地址空间中的一部分可以被保留下来以供非CloudStack VMs或者物理服务器使用。要真么做，你应该在来宾网络应用状态时依靠指定CIDR来配置一个预留IP地址范围。如果你的客户希望在同一个网络中有非CloudStack控制的VMs或者物理服务器，它们可以共享一部分主要为来宾网络提供的IP地址空间。"
+
+# fbba0aa499f74b36b378c6c99ef2ea87
+#: ../../networking2.rst:596
+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 called Reserved IP Range. When IP "
+"reservation is configured, the administrator can add additional VMs or "
+"physical servers that are not part of CloudStack to the same network and "
+"assign them the Reserved IP addresses. CloudStack guest VMs cannot acquire "
+"IPs from the Reserved IP Range."
+msgstr "在高级域中，定义一个网络时要给其赋予一个IP地址范围或CIDR。CloudStack虚拟路由器起着DHCP的作用，并通过CIDR来给客户虚拟机分配IP地址。如果为了预留CIDR不用于cloudstack，应当进行说明，即部分IP地址范围或CIDR仅能被DHCP服务分配给在cloudstack中创建的虚拟机。剩下的IP地址被称作预留IP地址范围。当预留的IP被配置时，管理员可以增加额外的虚拟机或并不属于cloudstack的物理服务器到同一个网络，可以将预留的IP地址指定给他们。cloudstack的客户虚拟机不能够从预留的IP地址中获得地址。"
+
+# 90bf1a7d2c754ac4902085a1fd1ba748
+#: ../../networking2.rst:610
+msgid "IP Reservation Considerations"
+msgstr "IP预留事项"
+
+# bc5248dcc785447289018e7cdfcbae8a
+#: ../../networking2.rst:612
+msgid ""
+"Consider the following before you reserve an IP range for non-CloudStack "
+"machines:"
+msgstr "在给非cloudstack内的机器预留IP地址时，要考虑以下几个方面："
+
+# 7c3b4a1806bc46caaec696068e353f33
+#: ../../networking2.rst:617
+msgid "IP Reservation is supported only in Isolated networks."
+msgstr "IP预留仅在隔离网络内支持"
+
+# a58ea815910f4eeebf5310fba2f2b4e6
+#: ../../networking2.rst:621
+msgid ""
+"IP Reservation can be applied only when the network is in Implemented state."
+msgstr "仅当网络在实施状态时，IP预留才能被应用。"
+
+# b1e7853953d34392be43f635d609444e
+#: ../../networking2.rst:626
+msgid "No IP Reservation is done by default."
+msgstr "默认不做IP预留。"
+
+# c5d1c53bfa0a4acb8b354fa73f021b37
+#: ../../networking2.rst:630
+msgid "Guest VM CIDR you specify must be a subset of the network CIDR."
+msgstr "指定客户的CIDR必须是网络CIDR的子网。"
+
+# 71e39d8747064bfa95ff48adddf42e34
+#: ../../networking2.rst:634
+msgid ""
+"Specify a valid Guest VM CIDR. IP Reservation is applied only if no active "
+"IPs exist outside the Guest VM CIDR."
+msgstr "指定一个有效的客户虚拟机CIDR。只有不活动的IP在客户虚拟机CIDR存在时，IP预留才能被应用。"
+
+# 7cd262eb2864435f953ba2f8d9b2e0a0
+#: ../../networking2.rst:637
+msgid ""
+"You cannot apply IP Reservation if any VM is alloted with an IP address that"
+" is outside the Guest VM CIDR."
+msgstr "如果任一虚拟机被分配了客户虚拟机CIDR之外的IP地址时，IP预留将不能应用。"
+
+# e135731ad79443bcb5dd396201d24cf1
+#: ../../networking2.rst:642
+msgid ""
+"To reset an existing IP Reservation, apply IP reservation by specifying the "
+"value of network CIDR in the CIDR field."
+msgstr "为重置一个已存在的IP预留，通过在CIDR框指定CIDR值就可应用IP预留。"
+
+# 3019eee8f787404483287650255b0fe0
+#: ../../networking2.rst:645
+msgid ""
+"For example, the following table describes three scenarios of guest network "
+"creation:"
+msgstr "例如，下表描述了客户网络创建的三种情形："
+
+# 80174dfa477741e8a428588c2de692c5
+#: ../../networking2.rst:649
+msgid "Case"
+msgstr "案例"
+
+# eef86be3eee44a648412010005fb2333
+# 5f16a478e68c498db89c7157f7a1baf2
+# 60559aa9aec74533a0723a299680c8a8
+# fe93ec4b20274d52a8708a5cf4922fbd
+# a51541e1ff974e5b9cec68fc9bcf7ea7
+# d31c3f23647842caa0554fd1db873ce4
+# 94126de200d245e5a36add083af0c115
+# d3690595a81542b3a1a8daec4b800f9c
+# 7cb858db9ac346838a97c8e7ed8dcd87
+# e2cbdab6f6d04ca3a9579faffa22f221
+# d1254ad4a86545a8ac507083e4787780
+# 7abcfe51770247ca88d17c97fb261b52
+# ab3f6c13fcea4cdf8df4054fc6c55960
+#: ../../networking2.rst:649 ../../networking2.rst:3931
+#: ../../networking2.rst:4403 ../../networking2.rst:4503
+#: ../../networking2.rst:4695 ../../networking2.rst:5251
+#: ../../networking2.rst:5299 ../../networking2.rst:5558
+#: ../../networking2.rst:5884 ../../networking2.rst:5971
+#: ../../networking2.rst:6063 ../../networking2.rst:6306
+#: ../../networking2.rst:6700
+msgid "CIDR"
+msgstr "CIDR"
+
+# 7190e9a05c824c698c369f059903140f
+#: ../../networking2.rst:649
+msgid "Network CIDR"
+msgstr "网络CIDR"
+
+# 7b3e79ea891f42948ec144865f44db13
+#: ../../networking2.rst:649
+msgid "Reserved IP Range for Non-CloudStack VMs"
+msgstr "非cloudstack虚拟机的IP预留范围"
+
+# 4c1abc1728ab4017a78ab13faa073d32
+#: ../../networking2.rst:649
+msgid "Description"
+msgstr "描述"
+
+# 95c1f9dcea57490f9baba27f6052d7df
+# c7dc34629f4a4f3380ad7fa0415823fe
+#: ../../networking2.rst:651 ../../networking2.rst:5253
+msgid "1"
+msgstr "1"
+
+# ca251edef20a4a09a96d4439f40e9fcc
+# 47ec19dde3c14d2daf3a5f567a8ab892
+# 96ce4f76ef034c6c8ad91aa5358390ea
+#: ../../networking2.rst:651 ../../networking2.rst:652
+#: ../../networking2.rst:655
+msgid "10.1.1.0/24"
+msgstr "10.1.1.0/24"
+
+# 9553954ea80b4c108951c22f66b1f907
+# 9d8d02ccc8624c42ab63f95c1e6e61d2
+# 1711e6d7b17c49c1bbacdfe2f237bc1c
+# 3fe4ae27728949db852e351bdc3590a0
+#: ../../networking2.rst:651 ../../networking2.rst:651
+#: ../../networking2.rst:655 ../../networking2.rst:655
+msgid "None"
+msgstr "无"
+
+# 4cefe96c4cd048d6ab5bba6b2b2b2c1f
+#: ../../networking2.rst:651
+msgid "No IP Reservation."
+msgstr "无"
+
+# 9743a326091e467d9b6bca3cd0e35000
+# 326ceea3093e4ad2bc955dd15a12fcaa
+#: ../../networking2.rst:652 ../../networking2.rst:5254
+msgid "2"
+msgstr "2"
+
+# 28839e89c7b84228a801613e0c9ed896
+#: ../../networking2.rst:652
+msgid "10.1.1.0/26"
+msgstr "10.1.1.0/26"
+
+# fb5379ee12174589ad3d2da83e61667c
+#: ../../networking2.rst:652
+msgid "10.1.1.64 to 10.1.1.254"
+msgstr "10.1.1.64-10.1.1.254"
+
+# a9558f6e733545849f81f3ae6fc11f08
+#: ../../networking2.rst:652
+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 "在界面的CIDR框内输入10.1.1.0/26或通过更新网络的API配置为guestvmcidr=10.1.1.0/26，进行IP预留配置"
+
+# b3beece5bd0f4a3d8a0234aa9980a330
+#: ../../networking2.rst:655
+msgid "3"
+msgstr "3"
+
+# 79c55aa2874f4650b96805d27acfee4e
+#: ../../networking2.rst:655
+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 "在界面的CIDR框内输入10.1.1.0/24或通过更新网络的API配置为guestvmcidr=10.1.1.0/24，进行IP预留清除"
+
+# 69a8f32537914ac6a722239a9dc07582
+# d8ca4fc7bf014daa9437cc4d5c7eb4f6
+#: ../../networking2.rst:661 ../../networking2.rst:1774
+msgid "Limitations"
+msgstr "局限性"
+
+# 6d66399f47684bc1940beb29a805e60c
+#: ../../networking2.rst:665
+msgid ""
+"The IP Reservation is not supported if active IPs that are found outside the"
+" Guest VM CIDR."
+msgstr "如果在客户虚拟机CIDR外发现活动的IP地址，IP预留将不被支持。"
+
+# db05ec3e0280485b9f6f8c5d902cbcc7
+#: ../../networking2.rst:670
+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 "在IP预留中，引起CIDR变化的网络升级方案都将无效，如将无外部设备的方案升级到带有外部设备的方案。在新实施的网络中，要重新配置IP预留。"
+
+# 6edc84466bc24a3d85247cab80c0cd80
+#: ../../networking2.rst:676
+msgid "Best Practices"
+msgstr "最佳实践"
+
+# 4bd0b852d6474b84accb421f128331f4
+#: ../../networking2.rst:678
+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 "一旦网络状态变为实施，应尽快应用IP预留到客户网络。如果在第一台客户虚拟机部署后应用IP预留，则会在应用IP会有较少的冲突发生。"
+
+# e601241fba8a43feb30b4dcde1dc89a6
+#: ../../networking2.rst:684
+msgid "Reserving an IP Range"
+msgstr "预留一个IP范围"
+
+# dd9d0df809aa420899439632c2e7019f
+#: ../../networking2.rst:702
+msgid "The CIDR field changes to editable one."
+msgstr "CIDR框将变为可编辑状态"
+
+# 0ffc29b024624ccdb36d0ea407209d7f
+#: ../../networking2.rst:706
+msgid "In CIDR, specify the Guest VM CIDR."
+msgstr "在CIDR框，说明客户虚拟机的CIDR"
+
+# b2b4f195c2e847418d352a7e1ef06061
+#: ../../networking2.rst:710
+msgid "Click Apply."
+msgstr "点击应用"
+
+# d33d489b7f234940bc59878574087127
+#: ../../networking2.rst:712
+msgid ""
+"Wait for the update to complete. The Network CIDR and the Reserved IP Range "
+"are displayed on the Details page."
+msgstr "等待更新完成。"
+
+# 06aed4f105fd47d283331f291310c288
+#: ../../networking2.rst:716
+msgid "Reserving Public IP Addresses and VLANs for Accounts"
+msgstr "为账户预留公共IP地址及VLANS"
+
+# d29491316baf475184dbf3bd53bb19c3
+#: ../../networking2.rst:718
+msgid ""
+"CloudStack provides you the ability to reserve a set of public IP addresses "
+"and VLANs exclusively for an account. During zone creation, you can continue"
+" defining a set of VLANs and multiple public IP ranges. This feature extends"
+" the functionality to enable you to dedicate a fixed set of VLANs and guest "
+"IP addresses for a tenant."
+msgstr "CloudStack可以让你能够独立的为账户预留一部分公共IP地址和VLANS。在创建区域阶段，你可以继续定义一部分VLANS以及多个公共IP范围。这种功能扩展特性可以让你能够为客户预留固定的一部分VLAN和客户IP地址"
+
+# 68a3748797434d67bcbfc405a263a065
+#: ../../networking2.rst:724
+msgid ""
+"Note that if an account has consumed all the VLANs and IPs dedicated to it, "
+"the account can acquire two more resources from the system. CloudStack "
+"provides the root admin with two configuration parameter to modify this "
+"default behavior: use.system.public.ips and use.system.guest.vlans. These "
+"global parameters enable the root admin to disallow an account from "
+"acquiring public IPs and guest VLANs from the system, if the account has "
+"dedicated resources and these dedicated resources have all been consumed. "
+"Both these configurations are configurable at the account level."
+msgstr "注意，如果一个账户使用了所有分配给他的VLAN和IP，这个账户可以从系统获得二个以上的资源。CloudStack为根管理员提供了二个参数可以进行控制，分别是use.system.public.ips和use.system.guest.vlans。当一个账户分配了资源并且这些资源已经被消耗掉时，这二个全局参数可以使根管理员拒绝此账户从公共IP和来宾VLAN获取资源。二个配置都能在帐户级别进行配置。"
+
+# 40f4120539264e8fb5dbf5a7064d1fe9
+#: ../../networking2.rst:734
+msgid "This feature provides you the following capabilities:"
+msgstr "这些特性可提供以下的功能："
+
+# 9bf2889fc36847ebabce3e8f9b625163
+#: ../../networking2.rst:738
+msgid ""
+"Reserve a VLAN range and public IP address range from an Advanced zone and "
+"assign it to an account"
+msgstr "从一个高级区域中预留一个VLAN范围和公共IP地址，并可以将其指定给一个账户。"
+
+# e1e3b63901214e39b4cd5ded0ff47ab6
+#: ../../networking2.rst:743
+msgid "Disassociate a VLAN and public IP address range from an account"
+msgstr "将一个VLAN和IP地址从一个账户解除联系。"
+
+# a849c48967014ee4ab4c29e6250ac9bc
+#: ../../networking2.rst:747
+msgid "View the number of public IP addresses allocated to an account"
+msgstr "查看分配给帐户的公共IP地址。"
+
+# 4c148c9f929f4394861c0230a52f46ea
+#: ../../networking2.rst:751
+msgid ""
+"Check whether the required range is available and is conforms to account "
+"limits."
+msgstr "检查需要的范围是否可用并且要符合帐户限制。"
+
+# b03cc0c4939e4538b33463b1acfa081f
+#: ../../networking2.rst:754
+msgid "The maximum IPs per account limit cannot be superseded."
+msgstr "不能超过每个账户最大的IP限制数。"
+
+# 331f9e80ff07451f833ea2f1e6592f48
+#: ../../networking2.rst:757
+msgid "Dedicating IP Address Ranges to an Account"
+msgstr "分配IP地址给一个账户"
+
+# cc9f01ca9cd04090b9ef074c6c68eb34
+# af5838600fdc41f68b104a44ea03d81a
+# 6230bfd5086842d69df7366e01ad5977
+#: ../../networking2.rst:765 ../../networking2.rst:886
+#: ../../networking2.rst:3054
+msgid "In the left navigation bar, click Infrastructure."
+msgstr "在左侧导航栏中，点击基础架构"
+
+# 732571fdd87e45b2ba3d0c99d319dada
+# 0a044cf03cd04706a971cfd6747f3972
+#: ../../networking2.rst:769 ../../networking2.rst:890
+msgid "In Zones, click View All."
+msgstr "在区域中，点击查看全部"
+
+# 718b87bdd1b24472a05561bc487af593
+# f0113ce9f8584511a94348c59e5098e9
+# 11d188714878411189998fcd7fb05a07
+#: ../../networking2.rst:773 ../../networking2.rst:894
+#: ../../networking2.rst:3062
+msgid "Choose the zone you want to work with."
+msgstr "选择你要设置的区域。"
+
+# e2c9d117a33a4ca698597ea697c642a8
+#: ../../networking2.rst:781
+msgid "In the Public node of the diagram, click Configure."
+msgstr "在图的公共节点上，点击配置。"
+
+# b587547f92d54da6a66fb328a1f90aa1
+#: ../../networking2.rst:785
+msgid "Click the IP Ranges tab."
+msgstr "点击IP范围页签。"
+
+# 71762e4009804e12af198d32409f6abe
+#: ../../networking2.rst:787
+msgid ""
+"You can either assign an existing IP range to an account, or create a new IP"
+" range and assign to an account."
+msgstr "或者指定一个已经的IP范围给帐户，或创建一个新的IP范围并指定给一个帐户。"
+
+# 89865009ad614a7caefc9d7e195d1f2c
+#: ../../networking2.rst:792
+msgid "To assign an existing IP range to an account, perform the following:"
+msgstr "要指定一个已有IP范围给帐户，按以下操作进行"
+
+# 023883e725b743e790c6c7d378fae5d1
+#: ../../networking2.rst:796
+msgid "Locate the IP range you want to work with."
+msgstr "确定需要分配的IP范围"
+
+# 727f9c60c5a149af95962b79fb673136
+#: ../../networking2.rst:800
+msgid "Click Add Account |addAccount-icon.png| button."
+msgstr "点击添加帐户按钮。|addAccount-icon.png| "
+
+# 98609249ea444461a727d851b23bdb4a
+#: ../../networking2.rst:802
+msgid "The Add Account dialog is displayed."
+msgstr "会弹出添加帐户对话框。"
+
+# 91a874f4d53548b5a54dd26c7a8070c4
+#: ../../networking2.rst:810
+msgid ""
+"**Account**: The account to which you want to assign the IP address range."
+msgstr "帐户，即需要指定IP地址范围的帐户"
+
+# d765ebdf04b540e9bb49f050bc9d5d1c
+#: ../../networking2.rst:815
+msgid "**Domain**: The domain associated with the account."
+msgstr "域名，与帐户关联的域名"
+
+# 68e22a0328b543599b5c092cb1be55c8
+#: ../../networking2.rst:817
+msgid "To create a new IP range and assign an account, perform the following:"
+msgstr "要指定一个新的IP范围给帐户，按以下操作进行"
+
+# a7351c3fc8aa4e6ab6f6de9982df895a
+#: ../../networking2.rst:826
+msgid "**Gateway**"
+msgstr "网关"
+
+# a8212080596548efb06b7f360af77801
+#: ../../networking2.rst:830
+msgid "**Netmask**"
+msgstr "掩码"
+
+# 2bac81ea68b044c99364b2e06d943f9e
+#: ../../networking2.rst:834
+msgid "**VLAN**"
+msgstr "VLAN"
+
+# a4fe8a556467404db7fc7ce462d9d690
+#: ../../networking2.rst:838
+msgid "**Start IP**"
+msgstr "起始IP"
+
+# b86850aa7e104d75b25613535bda6ad1
+#: ../../networking2.rst:842
+msgid "**End IP**"
+msgstr "结束IP"
+
+# 0cb6e7bb5c24462ca8eba42cba3c2ba0
+#: ../../networking2.rst:846
+msgid "**Account**: Perform the following:"
+msgstr "帐户，按以下操作进行："
+
+# ba26e0ab36b64d9a9e00350c439eb9ec
+#: ../../networking2.rst:850
+msgid "Click Account."
+msgstr "点击帐户"
+
+# 7ef94c9e8e0b407d82dc09a915d88b3e
+#: ../../networking2.rst:852
+msgid "The Add Account page is displayed."
+msgstr "会显示添加帐户页"
+
+# 2e18417b732143f89ffa9ab5c5767d1d
+#: ../../networking2.rst:860
+msgid ""
+"****Account****: The account to which you want to assign an IP address "
+"range."
+msgstr "帐户，即需要指定IP地址范围的帐户"
+
+# 24326080425a4f7ba299c24defa8ee63
+# 3360555202854da8a230941d49441cb7
+#: ../../networking2.rst:865 ../../networking2.rst:930
+msgid "****Domain****: The domain associated with the account."
+msgstr "****域****：域账号关联的域。"
+
+# 57dd5ad50af947868ed60fb4f4871b8e
+# fd71c947508a4b19a74d5e8e68ab028a
+# df1c4b86b0574044b3b1e2f59f86e433
+# 911725135046474fbb858f58a060c70c
+# 7f4d32193a8e441ba5d3ba76afdc660d
+# 0d1a59ac450f4913861519bb5690af46
+# 68ec8457b8f6477a877539749238ecd7
+#: ../../networking2.rst:874 ../../networking2.rst:1935
+#: ../../networking2.rst:3493 ../../networking2.rst:3595
+#: ../../networking2.rst:3751 ../../networking2.rst:3984
+#: ../../networking2.rst:5732
+msgid "Click Add."
+msgstr "点击 添加"
+
+# 6ef67854e5d346c7913e58e20a2b72f4
+#: ../../networking2.rst:877
+msgid "Dedicating VLAN Ranges to an Account"
+msgstr "确定需要分配的IP范围"
+
+# 37745b0f98834f4b805af70b9546e2d7
+#: ../../networking2.rst:881
+msgid ""
+"After the CloudStack Management Server is installed, log in to the "
+"CloudStack UI as administrator."
+msgstr "安装好CloudStack管理端后，使用管理员帐号登录CloudStack用户界面。"
+
+# f8bb5c0c781349a6ad62cac445eb11cc
+# eab05b15433e427aa1bb42cc204ab3e9
+#: ../../networking2.rst:902 ../../networking2.rst:1376
+msgid "In the Guest node of the diagram, click Configure."
+msgstr "在图中的来宾节点上，点击配置"
+
+# 61505cd3d4344e769a534aed469c073d
+#: ../../networking2.rst:906
+msgid "Select the Dedicated VLAN Ranges tab."
+msgstr "选择分配VLAN范围页签"
+
+# 1df8c107f4854732a4f8a3a50c9cec49
+#: ../../networking2.rst:910
+msgid "Click Dedicate VLAN Range."
+msgstr "点击分配VLAN范围"
+
+# c02ef1fcb0e642a28e69bd463286ec33
+#: ../../networking2.rst:912
+msgid "The Dedicate VLAN Range dialog is displayed."
+msgstr "会弹出分配VLAN对话框。"
+
+# acd323fd8ca8468880666db446b5d222
+#: ../../networking2.rst:920
+msgid ""
+"****VLAN Range****: The VLAN range that you want to assign to an account."
+msgstr "VLAN范围：即需要指定给帐户的VLAN范围"
+
+# 1a79b0742f1a4aefa692f541aa4b5892
+#: ../../networking2.rst:925
+msgid ""
+"****Account****: The account to which you want to assign the selected VLAN "
+"range."
+msgstr "帐户：即需要指定选定的VLAN的帐户"
+
+# fe1be017fe7644368cd98ae4c68575eb
+#: ../../networking2.rst:933
+msgid "Configuring Multiple IP Addresses on a Single NIC"
+msgstr "在单网卡配置多个IP地址"
+
+# c38d77c3c3a04ece8ca7568348264c1c
+#: ../../networking2.rst:935
+msgid ""
+"CloudStack provides you the ability to associate multiple private IP "
+"addresses per guest VM NIC. In addition to the primary IP, you can assign "
+"additional IPs to the guest VM NIC. This feature is supported on all the "
+"network configurations: Basic, Advanced, and VPC. Security Groups, Static "
+"NAT and Port forwarding services are supported on these additional IPs."
+msgstr "CloudStack能够让你给每个客户虚拟机网卡配置多个私有IP地址，除主IP地址外，你可以指定额外的IP地址到客户虚拟机网卡。在所有的网络配置中，如基础配置，高级配置，VPC，均支持这一功能。安全组，静态NAT及端口转发服务在额外的IP地址上也都被支持。"
+
+# f6ae31a4bdbf477bb30c85f877c5c6b6
+#: ../../networking2.rst:942
+msgid ""
+"As always, you can specify an IP from the guest subnet; if not specified, an"
+" IP is automatically picked up from the guest VM subnet. You can view the "
+"IPs associated with for each guest VM NICs on the UI. You can apply NAT on "
+"these additional guest IPs by using network configuration option in the "
+"CloudStack UI. You must specify the NIC to which the IP should be "
+"associated."
+msgstr "当然，你也可以从来宾子网中指定一个IP，如果没有指定，将会从来宾虚拟机子网中自动选择一个。可以从UI中查看每一个与来宾虚拟机网卡关联的IP地址。也可以在CloudStack界面中通过网络配置选项在那些额外的来宾虚拟机上应用NAT。但必须指明网卡与哪一个IP关联。"
+
+# e122667851cc41cbb7ee1643ac94d437
+#: ../../networking2.rst:949
+msgid ""
+"This feature is supported on XenServer, KVM, and VMware hypervisors. Note "
+"that Basic zone security groups are not supported on VMware."
+msgstr "在XenServer，KVM和VMware虚拟机中，都支持这些功能。注意，VMware不支持基础区域的安全组。"
+
+# d244bec96a6742dcba6445489ebe5218
+#: ../../networking2.rst:953
+msgid "Use Cases"
+msgstr "使用案例"
+
+# 6bb7477d1acc4f3fbd79cd0dbfc2ca5e
+#: ../../networking2.rst:955
+msgid "Some of the use cases are described below:"
+msgstr "一些使用案例见以下描述"
+
+# deaccf09c30b469a945f6c92f5b3e9e8
+#: ../../networking2.rst:959
+msgid ""
+"Network devices, such as firewalls and load balancers, generally work best "
+"when they have access to multiple IP addresses on the network interface."
+msgstr "网络设备，如防火墙或负责均衡设备，一般来讲，当他们在网络接口上接入更多的IP地址时，他们能够更好的工作。"
+
+# b3bb1a633fb0431687fc030d4f1135d3
+#: ../../networking2.rst:965
+msgid ""
+"Moving private IP addresses between interfaces or instances. Applications "
+"that are bound to specific IP addresses can be moved between instances."
+msgstr "在接口和实例中迁移IP地址。绑定到特定IP地址的应用可以在实例中迁移。"
+
+# 5d372ef180164330a3adddfbf3c1cc0f
+#: ../../networking2.rst:971
+msgid ""
+"Hosting multiple SSL Websites on a single instance. You can install multiple"
+" SSL certificates on a single instance, each associated with a distinct IP "
+"address."
+msgstr "在单个实例上开启多个SSL网站。可以在单个实例上安装多个SSL认证，每一个认证都关联一个单独的IP地址。"
+
+# 37f9e5af46a34673a930879c2e5cba6f
+# c7db437925a34c6a87c825ef10de2e9a
+# 3f3eba9611d84d6aae271d271019803b
+#: ../../networking2.rst:976 ../../networking2.rst:1194
+#: ../../networking2.rst:6425
+msgid "Guidelines"
+msgstr "指导方针"
+
+# 3e292b09263b4b97bfd6c423204dbc2f
+#: ../../networking2.rst:978
+msgid ""
+"To prevent IP conflict, configure different subnets when multiple networks "
+"are connected to the same VM."
+msgstr "为防止IP冲突，当多个网络连接至同一个虚拟机时，要配置不同的子网。"
+
+# 95785c3d19f449f78cc05d757ee25d24
+#: ../../networking2.rst:982
+msgid "Assigning Additional IPs to a VM"
+msgstr "指定额外的IP给虚拟机"
+
+# 59a152d36896406a8e27bc6d934ee420
+#: ../../networking2.rst:986
+msgid "Log in to the CloudStack UI."
+msgstr "登录到CloudStack的界面"
+
+# 62ef4fc700f2458282be770129fbe8f3
+#: ../../networking2.rst:990
+msgid "In the left navigation bar, click Instances."
+msgstr "在左侧导航栏，点击实例"
+
+# e481a0bf01464ec993e94b0b35787eed
+#: ../../networking2.rst:994
+msgid "Click the name of the instance you want to work with."
+msgstr "点击拟配置的实例"
+
+# 040e0aa0901c4a738201d7f2b345c0f1
+#: ../../networking2.rst:998
+msgid "In the Details tab, click NICs."
+msgstr "在详细 页签，点击网卡"
+
+# 783db8f186394495ad0ab1546a97951e
+#: ../../networking2.rst:1002
+msgid "Click View Secondary IPs."
+msgstr "点击查看二级地址"
+
+# 81df8a9f3f814aaa861dd841284985ef
+#: ../../networking2.rst:1006
+msgid ""
+"Click Acquire New Secondary IP, and click Yes in the confirmation dialog."
+msgstr "点击获取新二级IP，在确认对话框点击确定。"
+
+# 5bee3ae73622433aaf3ff3502d16bfcb
+#: ../../networking2.rst:1009
+msgid ""
+"You need to configure the IP on the guest VM NIC manually. CloudStack will "
+"not automatically configure the acquired IP address on the VM. Ensure that "
+"the IP address configuration persist on VM reboot."
+msgstr "需要手动配置来宾虚拟机的网卡。在虚拟机上，CloudStack不会自动配置获取IP。确保在虚拟机重启IP地址配置仍有效。"
+
+# f5aed3f52f76443b9810ed9d0bd1d47c
+#: ../../networking2.rst:1013
+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 StaticNAT "
+"rules."
+msgstr "稍等一会，新的IP地址会出现，状态栏为会显示为分配。现在可以在端口转发或静态NAT规则中使用此IP地址了。"
+
+# 91390ddfe5794441a909d512aaf69b16
+#: ../../networking2.rst:1018
+msgid "Port Forwarding and StaticNAT Services Changes"
+msgstr "更改端口转发和静态NAT服务"
+
+# 178e8a8fb2244a73af81938965720ec0
+#: ../../networking2.rst:1020
+msgid ""
+"Because multiple IPs can be associated per NIC, you are allowed to select a "
+"desired IP for the Port Forwarding and StaticNAT services. The default is "
+"the primary IP. To enable this functionality, an extra optional parameter "
+"'vmguestip' is added to the Port forwarding and StaticNAT APIs "
+"(enableStaticNat, createIpForwardingRule) to indicate on what IP address NAT"
+" need to be configured. If vmguestip is passed, NAT is configured on the "
+"specified private IP of the VM. if not passed, NAT is configured on the "
+"primary IP of the VM."
+msgstr "因为每一个网卡都可关联至多IP，CloudStack可以允许为端口转发及静态NAT服务选择一个目标IP。默认为主IP。为开启此功能，另一个可选的配置参数 虚拟机来宾IP 需要被加至端口转发及静态NAT 的API中去（开启静态NAT，创建IP端口转发），以示IP地址NAT需要配置。如果虚拟机来宾IP 没有设置，NAT会配置在虚拟机的私有IP上，如果设置了，NAT会配置在虚拟机的主IP上。"
+
+# 9a799b4a628a476f9d231bc81b470264
+#: ../../networking2.rst:1030
+msgid "About Multiple IP Ranges"
+msgstr "关于多IP范围"
+
+# 028ff8cab15f440e877ecf3ac468a1a2
+#: ../../networking2.rst:1032
+msgid "The feature can only be implemented on IPv4 addresses."
+msgstr "这些功能仅能在IPV4的地址是实现。"
+
+# e4d2239d0d0c410c8f96922f8da73fd8
+#: ../../networking2.rst:1034
+msgid ""
+"CloudStack provides you with the flexibility to add guest IP ranges from "
+"different subnets in Basic zones and security groups-enabled Advanced zones."
+" For security groups-enabled Advanced zones, it implies multiple subnets can"
+" be added to the same VLAN. With the addition of this feature, you will be "
+"able to add IP address ranges from the same subnet or from a different one "
+"when IP address are exhausted. This would in turn allows you to employ "
+"higher number of subnets and thus reduce the address management overhead. To"
+" support this feature, the capability of ``createVlanIpRange`` API is "
+"extended to add IP ranges also from a different subnet."
+msgstr "在基础区域以及高级区域的开启安全组，CloudStack能够让你从不同的子网添加来宾IP范围。对于高级区域的开启安全组，多个子网可被加至同一个VLAN。随着此功能的增加，当IP地址耗尽时，你能够从同一个子网或从不同的子网添加IP范围。这会允许你添加更多的子网，因此减少了了地址管理的问题。为支持这一特性，创建VLANIP范围的API被加以扩展，这样就能从不同的子网添加IP范围"
+
+# 2881a530808e42f5be3d6298eeb47271
+#: ../../networking2.rst:1045
+msgid ""
+"Ensure that you manually configure the gateway of the new subnet before "
+"adding the IP range. Note that CloudStack supports only one gateway for a "
+"subnet; overlapping subnets are not currently supported."
+msgstr "确实在添加IP范围前，手动配置了子网的网关。注意，CloudStack仅支持一个子网有一个网关。不支持重叠的子网。"
+
+# 003e5d07c0794227bc714b0f29892867
+#: ../../networking2.rst:1049
+msgid ""
+"Use the ``deleteVlanRange`` API to delete IP ranges. This operation fails if"
+" an IP from the remove range is in use. If the remove range contains the IP "
+"address on which the DHCP server is running, CloudStack acquires a new IP "
+"from the same subnet. If no IP is available in the subnet, the remove "
+"operation fails."
+msgstr "使用删除VLAN范围的API删除IP范围。如果拟删除的IP在被使用时，此操作会失败。如果删除的范围包含DHCP服务器拟分配的IP地址CloudStack会从同一个子网下获取新的IP。如果在子网内没有可供利用的IP时，删除操作会失败。"
+
+# b8a91ec2e02844bd85db4f28846aad2b
+#: ../../networking2.rst:1055
+msgid "This feature is supported on KVM, xenServer, and VMware hypervisors."
+msgstr "在KVM, xenServer以及VMware虚拟机中，都支持这项功能。 "
+
+# ed378b716b614e5ea18ea508d7ecccb8
+#: ../../networking2.rst:1058
+msgid "About Elastic IP"
+msgstr "关于弹性IP"
+
+# cb979912025d4652b170b423b3323451
+#: ../../networking2.rst:1060
+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 is down, the IP address can be "
+"reassigned to a new VM in your account."
+msgstr "弹性IP（EIP）地址是指与帐户关联的IP地址，能起到静态IP地址的作用。帐户所有者能完全控制隶属于此账户的弹性IP。作为帐户拥有者，你可以从你帐户的EIP池中选择一个IP分配给虚拟机。如果后续需要，你可以继续分配此IP地址给另一个虚拟机。在VM宕机时，此功能特别有用。此IP地址可以重新指定给一个新的虚拟机，而不是取代已经宕机的虚拟机。"
+
+# a05811529f014d1aa52b2974f0bba51e
+#: ../../networking2.rst:1069
+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 "与公共IP地址一样，弹性IP地址通过使用静态NAT关联至与之相关的私有IP地址。在起用了EIP的基础域中，EIP的服务与静态NAT的服务一一对应。默认的网络方案，默认共享EIP与负载均衡网络方案，在区域部署了NetScaler设备的前提下，能够提供EIP以及ELB网络服务。参见以下更详细的说明。"
+
+# d254f6b5f23f4583bf38593e35204bd5
+#: ../../networking2.rst:1077
+msgid "|eip-ns-basiczone.png|"
+msgstr "|eip-ns-basiczone.png|"
+
+# ec87f8235ad14731b88fa165faf2855f
+#: ../../networking2.rst:1079
+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 data center goes through the firewall."
+msgstr "在图中，NetScaler设备对CloudStack的实例而言是一个默认的入口或出口，防火墙是剩余数据中心的出口或入口。Netscaler对来宾网络提供负载均衡以及静态NAT的服务。在机架和管理服务器上，来宾流量是不同的子网或VLAN。在数据中心的核心交换机的基础路由策略是通过NetScaler转发公共流量，其他数据中心的流量则通过防火墙。"
+
+# cccbede2f664419a97a65174be17cfba
+#: ../../networking2.rst:1088
+msgid "The EIP work flow is as follows:"
+msgstr "EIP的工作流如下："
+
+# 748bdba8746d4237862652eeefe51b0c
+#: ../../networking2.rst:1092
+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 "当部署一个用户虚拟机时，会从区域配置的IP中自动获得一个公共IP。这个IP为虚拟机帐户所拥有。"
+
+# b453f18754a649e5913c58ce4a28993b
+#: ../../networking2.rst:1098
+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 "每一个虚拟机都有自己的私有IP。当来客户虚拟机启动时，通过使用在公共IP和私有IP之间的入口网络地址转换（INAT）以及预留地址转换（RNAT），NetScaler设备可以提供静态NAT"
+
+# 6e1a151b2c704623941c8c05d3a90134
+#: ../../networking2.rst:1104
+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 "入口网络地址转换（INAT）是NetScaler支持的一类NAT类型，在此类型中，来自公共网络（如Internet)的数据包中的目标IP地址被私有网络中虚拟机的私有地址取代。预留地址转换（RNAT）也是NetScaler支持的一类NAT类型，私有网络中虚拟机产生的数据包中的源IP地址被公共IP地址取代。"
+
+# e64823a0214b46d8a6326da740b47131
+#: ../../networking2.rst:1113
+msgid "This default public IP will be released in two cases:"
+msgstr "默认的公共IP在两种情况下会被释放："
+
+# ec3de61219d640b2baa722270d509f9b
+#: ../../networking2.rst:1117
+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 "当虚拟机停止时。当虚拟机启动时，可以重新获取一个新的公共IP，并不必须是从公共IP地址池中最初分配的那一个。"
+
+# 9429fa004e17414e88ed8a023486ac59
+#: ../../networking2.rst:1123
+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 "当用户获取公共IP（弹性IP）时。这些公共IP与帐户相关联，但不与任何私有IP相关。然而，用户可以开启静态NAT将帐户中虚拟机的私有IP与之关联。对应公共IP的静态NAT规则可随时取消。当静态NAT关闭时，会从地址池中分配的一个新的公共IP，并不必须是最初分配的那一个。"
+
+# 469830a9248b4593a5aac71adbba4340
+#: ../../networking2.rst:1131
+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 and enable static NAT."
+msgstr "对部署而言，公共IP会受限于资源，可以灵活的选择默认不分配公共IP。可以在开启了EIP的基础区域中，通过关联公共IP选项来打开或关闭自动公共IP指定。如果在创建网络方案时，你关闭了自动公共IP指定，则在使用此网络方案部署时，仅会分配一个私有IP给虚拟机。此后，用户虚拟机可以获取一个IP，并可以开启静态NAT。"
+
+# 0ecd0ac61194408a98281da0aadd9e1a
+#: ../../networking2.rst:1140
+msgid ""
+"For more information on the Associate Public IP option, see `\"Creating a "
+"New Network Offering\" <networking.html#creating-a-new-network-offering>`_."
+msgstr "要了解更多关于关联公共IP的选项，请参考`\"创建一个新的网络方案\" <networking.html#creating-a-new-network-offering>`_."
+
+# 3cd8dd1307094741b10ebb57dc03d260
+#: ../../networking2.rst:1144
+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 "设计关联公共IP的功能，仅是为使用用户虚拟机。系统虚拟机仍然默认会获取公共IP和私有IP，与网络配置并不相关。"
+
+# 3ff9c04d9cd44e088c20dfd89e9b3b8b
+#: ../../networking2.rst:1148
+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 "在基础区域中，使用默认具有EIP和ELB服务的网络方案来创建共享网络时，仍然会给每一个用户虚拟机分配公共IP。"
+
+# 16c8dc460b214f4894425176314b9cb3
+#: ../../networking2.rst:1153
+msgid "Portable IPs"
+msgstr "端口IP"
+
+# 3a5bf095b28f463397be53d043c810c8
+#: ../../networking2.rst:1156
+msgid "About Portable IP"
+msgstr "关于端口IP"
+
+# 5458a5ed86214e4c93481bcc51808719
+#: ../../networking2.rst:1158
+msgid ""
+"Portable IPs in CloudStack are region-level pool of IPs, which are elastic "
+"in nature, that can be transferred across geographically separated zones. As"
+" an administrator, you can provision a pool of portable public IPs at region"
+" level and are available for user consumption. The users can acquire "
+"portable IPs if admin has provisioned portable IPs at the region level they "
+"are part of. These IPs can be use for any service within an advanced zone. "
+"You can also use portable IPs for EIP services in basic zones."
+msgstr "在CloudStack中，端口IP是地域级的IP地址池，其天然具有弹性，亦即可以在地理隔离的区域中进行转发。作为管理员,可以在地域级提供IP地址池供用户使用。如果在用户所属的地域，其管理员提供了端口IP，用户就可以获取此类IP。在高级区域内，这些IP可用于任一服务。也可以在基础区域中为EIP服务使用端口IP。"
+
+# 7315df7ef52e4cf1b934b6af1441d884
+#: ../../networking2.rst:1167
+msgid "The salient features of Portable IP are as follows:"
+msgstr "端口IP的主要功能如下："
+
+# 891115e5cf6a48ada1f4095573352338
+#: ../../networking2.rst:1171
+msgid "IP is statically allocated"
+msgstr "IP是静态分配的。"
+
+# 4d10cf62b6c743b8b592cc802be6cc92
+#: ../../networking2.rst:1175
+msgid "IP need not be associated with a network"
+msgstr "IP与网络无关。"
+
+# 24d3e403f0aa4c39ad463d1fa0ae207d
+#: ../../networking2.rst:1179
+msgid "IP association is transferable across networks"
+msgstr "IP关联是可以通过网络转发的。"
+
+# 74cb916a3d374a76b971841f8b2379a5
+#: ../../networking2.rst:1183
+msgid "IP is transferable across both Basic and Advanced zones"
+msgstr "IP可以在基础区域和高级区域中转发。"
+
+# 7d33ab9a52444bbe9b3f7b3128209e6b
+#: ../../networking2.rst:1187
+msgid "IP is transferable across VPC, non-VPC isolated and shared networks"
+msgstr "IP可通过VPC，非VPC隔离和共享网络进行转发。"
+
+# df1a612ddd7d4098a0ddf9b83ad8a93e
+#: ../../networking2.rst:1191
+msgid "Portable IP transfer is available only for static NAT."
+msgstr "端口IP转发仅对静态NAT可用。"
+
+# bb4f9954dc894d61abfa568fb2e16957
+#: ../../networking2.rst:1196
+msgid ""
+"Before transferring to another network, ensure that no network rules "
+"(Firewall, Static NAT, Port Forwarding, and so on) exist on that portable "
+"IP."
+msgstr "在转发至另一网络前，确保没有网络规则（如防火墙，静态NAT，端口转发等等）不存在于端口IP。"
+
+# 6219f205752d4e34a5f1fbf3a5de51cc
+#: ../../networking2.rst:1201
+msgid "Configuring Portable IPs"
+msgstr "配置端口IP"
+
+# d64282ef04d447a599ddece7139055f7
+#: ../../networking2.rst:1209
+msgid "In the left navigation, click Regions."
+msgstr "在左侧导航栏中，点击地域"
+
+# 8b31c7af9d8541d79d6b98d0ed76d82d
+#: ../../networking2.rst:1213
+msgid "Choose the Regions that you want to work with."
+msgstr "选择拟修改的地域。"
+
+# 1938f07ea2c94222a20b08898972dc0c
+#: ../../networking2.rst:1217
+msgid "Click View Portable IP."
+msgstr "点击查看端口IP"
+
+# 3fd59fc0c5804ab58ed115888d070d9d
+#: ../../networking2.rst:1221
+msgid "Click Portable IP Range."
+msgstr "点击端口IP范围"
+
+# 289d79706e0d4aac949867e57202c169
+#: ../../networking2.rst:1223
+msgid "The Add Portable IP Range window is displayed."
+msgstr "会出现 添加端口IP范围的窗口"
+
+# 6ba39db9be5d430986ffe15997a7b655
+#: ../../networking2.rst:1231
+msgid ""
+"**Start IP/ End IP**: A range of IP addresses that are accessible from the "
+"Internet and will be allocated to guest VMs. Enter the first and last IP "
+"addresses that define a range that CloudStack can assign to guest VMs."
+msgstr "起始IP/结束IP：从Internet可以访问的一个IP地址范围，将会分配给客户虚拟机。输入起始IP以及结束IP，定义CloudStack指定给客户虚拟机的IP范围。"
+
+# a79eef6844454a7e8d9fe27202723b53
+#: ../../networking2.rst:1238
+msgid ""
+"**Gateway**: The gateway in use for the Portable IP addresses you are "
+"configuring."
+msgstr "网关：配置端口IP地址所使用的网关。"
+
+# ade2b585b1ff4b51b25c1f72d1f5a03e
+#: ../../networking2.rst:1243
+msgid "**Netmask**: The netmask associated with the Portable IP range."
+msgstr "掩码：与端口IP范围关联的掩码。"
+
+# 2cce53fcfa9e4ebdb7cec25d4dd3f797
+#: ../../networking2.rst:1247
+msgid "**VLAN**: The VLAN that will be used for public traffic."
+msgstr "VLAN：公共流量拟使用的VLAN。"
+
+# 5c4576cb4d01410ea44f66b3560eec1c
+#: ../../networking2.rst:1254
+msgid "Acquiring a Portable IP"
+msgstr "获取端口IP。"
+
+# fd1b3a3c5e574a7ebb4e782d04f0746b
+# 3ec5393b7aa8486ca2b52df1597e7a98
+# b4889435dd5a4b8986acad62a13ddd6a
+# bfc4acd9c38f49138744c5671d7deb8b
+# 9eae88f558024bafa1c71d5b5f8f6d94
+#: ../../networking2.rst:1266 ../../networking2.rst:3292
+#: ../../networking2.rst:3335 ../../networking2.rst:3378
+#: ../../networking2.rst:3452
+msgid "Click the name of the network where you want to work with."
+msgstr "点击拟修改的网络名称。"
+
+# e986c959252444b99b7c5594762994fb
+# 2809642deff2421db1593ab57615dc68
+# d64bfe77233d4d59b07129a931a574b3
+# 15c8b96721f3464380599d2d5d2f02bc
+# 9751f6d58300447198381c3549bd481e
+# f8c3a0b896d14361b59692083c989410
+# 4bccc75dc7d0449097629003483b3545
+#: ../../networking2.rst:1270 ../../networking2.rst:2223
+#: ../../networking2.rst:3296 ../../networking2.rst:3339
+#: ../../networking2.rst:3382 ../../networking2.rst:3456
+#: ../../networking2.rst:3870
+msgid "Click View IP Addresses."
+msgstr "点击查看IP地址。"
+
+# 667a207d51d24ec19784a9167e8565b8
+# 5605f1edaf4a463a84ae99cdd32825a4
+#: ../../networking2.rst:1274 ../../networking2.rst:3300
+msgid "Click Acquire New IP."
+msgstr "点击获取新IP。"
+
+# 6f484ad19a9e4e70b96bf198ddbcf3f4
+# ac45a6f42e5e42a29e4eb09f827d12a3
+#: ../../networking2.rst:1276 ../../networking2.rst:3302
+msgid "The Acquire New IP window is displayed."
+msgstr "获取新IP的窗口会出现。"
+
+# a62089adc7304fe1a0c39b6e337ddca2
+# 9baf10608a674ae292c3dea0a0859da7
+#: ../../networking2.rst:1280 ../../networking2.rst:3306
+msgid "Specify whether you want cross-zone IP or not."
+msgstr "说明是否需要IP跨区。"
+
+# 3bb7d4dc99f341248a9c5c892bc12485
+#: ../../networking2.rst:1284
+msgid "Click Yes in the confirmation dialog."
+msgstr "在确认对话框中点击确定。"
+
+# 38c1b6967ebb4ec9852ba01c1f005f98
+# 197a1c50649d486ca45fb94f4900aa2d
+#: ../../networking2.rst:1286 ../../networking2.rst:3314
+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 "稍等一会，新的IP地址会出现，状态栏为会显示为分配。现在可以在端口转发或静态NAT规则中使用此IP地址了。"
+
+# 524a4bfc4e03495584030002db87273b
+#: ../../networking2.rst:1291
+msgid "Transferring Portable IP"
+msgstr "便携式IP"
+
+# 68465770f0cb4381ac7ce0eb0b65ecbc
+#: ../../networking2.rst:1293
+msgid ""
+"An IP can be transferred from one network to another only if Static NAT is "
+"enabled. However, when a portable IP is associated with a network, you can "
+"use it for any service in the network."
+msgstr "IP要从一个网络转换至另一网络的话，只需启用静态NAT。但是，当一个portable IP对应一个网络的时候，你可以在网络中为任何服务使用它 。"
+
+# b51d59c49aad4d2c82dc7ff551a1e515
+#: ../../networking2.rst:1297
+msgid ""
+"To transfer a portable IP across the networks, execute the following API:"
+msgstr "要跨网络转换一个portable IP，执行下列API："
+
+# baaa47d9664443df8004dbd797ca37f0
+#: ../../networking2.rst:1304
+msgid ""
+"Replace the UUID with appropriate UUID. For example, if you want to transfer"
+" a portable IP to network X and VM Y in a network, execute the following:"
+msgstr "用正确的UUID替换此处的UUID。比如，如果你想转换一个portable IP至X网络和一个网络中的VM Y，请执行下列操作："
+
+# 2ab16bedc435498fa54a92c12d41873b
+#: ../../networking2.rst:1313
+msgid "Multiple Subnets in Shared Network"
+msgstr "共享网络中的多子网"
+
+# 052e7dd83a5d49f6830d255583296f7d
+#: ../../networking2.rst:1315
+msgid ""
+"CloudStack provides you with the flexibility to add guest IP ranges from "
+"different subnets in Basic zones and security groups-enabled Advanced zones."
+" For security groups-enabled Advanced zones, it implies multiple subnets can"
+" be added to the same VLAN. With the addition of this feature, you will be "
+"able to add IP address ranges from the same subnet or from a different one "
+"when IP address are exhausted. This would in turn allows you to employ "
+"higher number of subnets and thus reduce the address management overhead. "
+"You can delete the IP ranges you have added."
+msgstr "CloudStack为你提供了在基本zones和启用了安全组的高级zones不同的子网中灵活的添加来宾IP段功能 。在启用了安全组的高级zones中，这意味着多子网可以被添加到同一个VLAN。这个特性还意味着，当IP地址用尽的时候，你可以从同一个子网或从不同的子网添加IP地址范围。这将允许你使用更多的子网，降低地址管理工作量。你也可以删除已经添加的IP地址范围。"
+
+# 39d6185c2a9142778ebfcfaa45d53ea4
+# a87fd7c6cc4d4983be85e89d3f15de49
+# dff9442af85b489c8e6c974a633e5646
+#: ../../networking2.rst:1326 ../../networking2.rst:2963
+#: ../../networking2.rst:3510
+msgid "Prerequisites and Guidelines"
+msgstr "先决条件和指南"
+
+# b12da91685134a71866c8fa74aeaa4de
+#: ../../networking2.rst:1330
+msgid "This feature can only be implemented:"
+msgstr "这个特性只能被实现在："
+
+# 1393ad33a993459f81ea3de1149b6a09
+#: ../../networking2.rst:1334
+msgid "on IPv4 addresses"
+msgstr "IPv4地址"
+
+# 4764589edb39403a9fd8558614490a61
+#: ../../networking2.rst:1338
+msgid "if virtual router is the DHCP provider"
+msgstr "如果虚拟路由是由DHCP提供的"
+
+# b1541de5c3f0486faa35809ad77b0359
+#: ../../networking2.rst:1342
+msgid "on KVM, xenServer, and VMware hypervisors"
+msgstr "在KVM，XenServer和VMware hypervisors"
+
+# 2422d92308cd49628de0caa0efcad9c7
+#: ../../networking2.rst:1346
+msgid ""
+"Manually configure the gateway of the new subnet before adding the IP range."
+msgstr "在添加IP范围之前，手动配置新子网的网关。"
+
+# bf5e159cb4c54583a861e417824b26a3
+#: ../../networking2.rst:1351
+msgid ""
+"CloudStack supports only one gateway for a subnet; overlapping subnets are "
+"not currently supported"
+msgstr "CloudStack只支持一个子网对应一个网关；交叉子网目前不支持。"
+
+# 7e64cd24270240e9bef22bc1491bf837
+#: ../../networking2.rst:1355
+msgid "Adding Multiple Subnets to a Shared Network"
+msgstr "给共享网络添加多子网"
+
+# 1f05243395c24667a0f7e9c75bbc190f
+#: ../../networking2.rst:1367
+msgid ""
+"On Zones, click View More, then click the zone to which you want to work "
+"with.."
+msgstr "在Zones上，点击查看更多，然后点击你要进行操作的zone.."
+
+# 2b58f0a641ae4d80a61839330e31435b
+#: ../../networking2.rst:1372
+msgid "Click Physical Network."
+msgstr "点击物理网络。"
+
+# 01147d3437e04c6c93201551e05eec93
+#: ../../networking2.rst:1380
+msgid "Click Networks."
+msgstr "点击网络。"
+
+# f5611c1c2d6f4bc2935f6fcb462429ac
+#: ../../networking2.rst:1384
+msgid "Select the networks you want to work with."
+msgstr "选择你想要操作的网络。"
+
+# 8c8af6183f054d4b87cd5369985f279b
+#: ../../networking2.rst:1388
+msgid "Click View IP Ranges."
+msgstr "点击查看IP范围。"
+
+# 27bfee4a94154becadc04d190e2248f0
+#: ../../networking2.rst:1392
+msgid "Click Add IP Range."
+msgstr "点击添加IP范围。"
+
+# 0b8e9d89d4724266b4f358cddb5b5dae
+#: ../../networking2.rst:1394
+msgid "The Add IP Range dialog is displayed, as follows:"
+msgstr "显示的添加IP范围对话框如下："
+
+# b80689bd7547487da595f615e2462e55
+#: ../../networking2.rst:1396
+msgid "|add-ip-range.png|"
+msgstr "|add-ip-range.png|"
+
+# ecfac85bd0504455b3d64af38c930d89
+# b0284174465747738037a24f289b32cd
+#: ../../networking2.rst:1402 ../../networking2.rst:5168
+msgid "All the fields are mandatory."
+msgstr "所有的区域必须填写的。"
+
+# 2a42d646d37c4df6add5bdf38ceca64d
+# d96a1cf974414215858b14602328707b
+#: ../../networking2.rst:1406 ../../networking2.rst:5186
+msgid ""
+"**Gateway**: The gateway for the tier you create. Ensure that the gateway is"
+" within the Super CIDR range that you specified while creating the VPC, and "
+"is not overlapped with the CIDR of any existing tier within the VPC."
+msgstr "**网关**：你创建网络层的网关。确保网关在你创建VPC时指定的超级CIDR范围内，并且不能与已存在VPC的任何网络层的CIDR重叠。"
+
+# 135026f2c8ab4d77a877e4d100640178
+# 035c6987b29147ebb036cad74b0ca7e2
+#: ../../networking2.rst:1413 ../../networking2.rst:5203
+msgid "**Netmask**: The netmask for the tier you create."
+msgstr "**子网掩码**：你创建的网络层的子网掩码。"
+
+# ff580244e12e4780b2df473d710b2271
+# 8323a108551a443f8e02e4e8bf7cb1cc
+#: ../../networking2.rst:1415 ../../networking2.rst:5205
+msgid ""
+"For example, if the VPC CIDR is 10.0.0.0/16 and the network tier CIDR is "
+"10.0.1.0/24, the gateway of the tier is 10.0.1.1, and the netmask of the "
+"tier is 255.255.255.0."
+msgstr "比如，如果VPC CIDR是10.0.0.0/16并且该网络层CIDR是10.0.1.0/24，那么这个网络层的网关是10.0.1.1，子网掩码是255.255.255.0."
+
+# e68e024d0d01404c95c2dfc37f213a3e
+#: ../../networking2.rst:1421
+msgid ""
+"**Start IP/ End IP**: A range of IP addresses that are accessible from the "
+"Internet and will be allocated to guest VMs. Enter the first and last IP "
+"addresses that define a range that CloudStack can assign to guest VMs ."
+msgstr "**起始/结束IP**：从互联网获得的和将被分配给来宾VMsIP地址范围。输入第一个和最后一个IP地址，该地址范围定义的是CloudStack能分配给来宾VMs的范围。"
+
+# 878c548f176b4ef18a4c21be8ace7a7b
+#: ../../networking2.rst:1431
+msgid "Isolation in Advanced Zone Using Private VLAN"
+msgstr "使用Private VLAN隔离高级Zone中的网络"
+
+# a24c2265540a4aef9c82390bf465ff16
+#: ../../networking2.rst:1433
+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 users' VMs."
+msgstr "在共享网络中的隔离来宾流量能被Private VLAN（PVLAN）获取。PVLANs提供同一个VLAN里端口间的2层网络隔离。在启用了PVLAN的共享网络，一个用户VM不能到达其他用户VM，但是他们能与DHCP服务器和网关通讯，反过来这样能允许用户去控制网络内部的流量，并且帮助他们像阻止与其他用户VMs通讯一样的去部署无需通讯的多个应用程序。"
+
+# 4a22b32ca020436b81dd8f07f34306f4
+#: ../../networking2.rst:1444
+msgid "Isolate VMs in a shared networks by using Private VLANs."
+msgstr "使用PVLAN在共享网络中隔离VMs。"
+
+# abb78195383c40838e8616f04b87f7f2
+#: ../../networking2.rst:1448
+msgid "Supported on KVM, XenServer, and VMware hypervisors"
+msgstr "在KVM，XenServer和VMware hypervisors中支持"
+
+# 2b02488a70fc420996644982994ac6eb
+#: ../../networking2.rst:1452
+msgid ""
+"PVLAN-enabled shared network can be a part of multiple networks of a guest "
+"VM."
+msgstr "启用了PVLAN的共享网络可以是来宾VM的多个网络的一部分。"
+
+# d86c07b7947d412799db280d59e3f9e5
+#: ../../networking2.rst:1456
+msgid "About Private VLAN"
+msgstr "关于Private VLAN"
+
+# 892b94b696954a8e9527248d969742c6
+#: ../../networking2.rst:1458
+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 VLAN that is being divided "
+"into smaller groups is called Primary, which implies that all VLAN pairs in "
+"a private VLAN share the same Primary VLAN. All the secondary VLANs exist "
+"only inside the Primary. Each Secondary VLAN has a specific VLAN ID "
+"associated to it, which differentiates one sub-domain from another."
+msgstr "在以太网交换机中，VLAN是二层网络中的一个主机之间主机能建立直接通讯的广播域 。Private VLAN被设计成一个标准的VLAN的延伸，为了进一步细分逻辑广播域。一个规则的VLAN是单一广播域，但是一个 private VLAN将一个较大的VLAN广播域划分为较小的多个子域。子域表现为一对VLANs：一个主VLAN和一个辅助VLAN。被划分为较小组的原始VLAN叫主，这意味着所有的在private VLAN中的VLAN对共享着同一个主VLAN。所有的辅助VLANs存在与主VLAN中。每个辅助VLAN有一个特定的区别于其他子域VLAN ID。"
+
+# 65264ae745f94985b736d5abe4446401
+#: ../../networking2.rst:1471
+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 "在private VLAN中有三种端口类型，它们实质上决定了所包含的主机的流量走势。每组端口都有自己唯一的策略，它能控制配置同一个private VLAN域中连接到端口的主机与其他已连接主机的通讯。使用下面三种端口定义中的一种来配置每个PVLAN对中的主机："
+
+# 65ce874571f0428cbe807261ef5c91ff
+#: ../../networking2.rst:1480
+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 "**混杂模式（Promiscuous）**：混杂模式的端口能与所有的接口通讯，包括可通讯与隔离属于辅助VLANs的主机端口。在混杂模式中，主机被连接到混在模式端口并且能够直接与主VLAN和辅助VLAN中的资源。典型的连接到混杂模式端口的是路由器，DHCP服务器和其他受信任的设备。"
+
+# 11d7e1e2a07f44da85da53d61de9130b
+#: ../../networking2.rst:1490
+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 "**隔离模式（Isolated）VLANs**隔离模式VLAN中的端口不能与其他二层网络中的端口通讯。连接隔离模式端口上的主机只能直接与混杂模式下的资源通讯。如果你的客户设备只访问网关路由器，请将其附加至隔离端口。"
+
+# c008cae9b2a74d48a4170c54a17a63d6
+#: ../../networking2.rst:1498
+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 communicate among themselves, deploy them in "
+"community ports."
+msgstr "**Community VLANs**：中的端口能与其他端口和混杂模式下的端口通讯，但是他们不能与二层网络中的其他community VLAN中的端口通讯。在Community模式下，主机能与同一community中的主机和连接到混杂模式中的主VLAN的主机可以通讯。如果你的客户有两个设备需要与其他客户的设备隔离，但是他们之间又要通讯，请将他们部署至 community 端口。"
+
+# eca73570aa5c496ba46877b3392feba4
+#: ../../networking2.rst:1508
+msgid "For further reading:"
+msgstr "延伸阅读："
+
+# 3fb1a7985e5143939ea6ed3db5517634
+#: ../../networking2.rst:1512
+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 "`理解 Private VLANs <http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_25_see/configuration/guide/swpvlan.html#wp1038379>`_"
+
+# 413321509f2d47a8b184ec2e8adbfcb5
+#: ../../networking2.rst:1517
+msgid ""
+"`Cisco Systems' Private VLANs: Scalable Security in a Multi-Client "
+"Environment <http://tools.ietf.org/html/rfc5517>`_"
+msgstr "`Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment <http://tools.ietf.org/html/rfc5517>`_"
+
+# d92ce4bc2e25409b903ed61ed410286d
+#: ../../networking2.rst:1522
+msgid ""
+"`Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview "
+"(1010691) <http://kb.vmware.com>`_"
+msgstr "`Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview (1010691) <http://kb.vmware.com>`_"
+
+# 7b72e0b764624a06bcaed4e13da2da3d
+#: ../../networking2.rst:1530
+msgid "Use a PVLAN supported switch."
+msgstr "在支持的交换机上使用PVLAN。"
+
+# 4c3023eb7cbe49fdbc0af7708061b61c
+#: ../../networking2.rst:1532
+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 "更多信息，请参考 `Private VLAN Catalyst Switch Support Matrix <http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a0080094830.shtml>`_ "
+
+# 3d53c6dd5e0c47c98d6a7945385c1baa
+#: ../../networking2.rst:1538
+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 "将所有能识别PVLAN的二层交换机之间互连，并且其中一个要连至一个路由器。主机连接到的所有端口需配置为trunk模式。打开VLAN管理，主VLAN（公共网络）和隔离的辅助VLAN端口。配置交换机连接到路由器的端口为PVLAN混杂trunk，这样可以为不识别PVLAN的路由器转换一个隔离的VLAN到主VLAN。"
+
+# c0a596996cd541c399ba489470a762f3
+#: ../../networking2.rst:1546
+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 "注意只有Cisco Catalyst 4500有PVLAN混杂trunk模式，可以连接所有普通VLAN和PVLAN到不能识别PVLAN的交换机。其他支持PVLAN的Catalyst交换机，在PVALN对中的每个交换机上使用级联线连接到上联交换机。"
+
+# cc4e6fc0e1f245528985b2117be84d9f
+#: ../../networking2.rst:1553
+msgid "Configure private VLAN on your physical switches out-of-band."
+msgstr "在你的物理交换机上使用带外管理配置private VLAN。"
+
+# 62074ec8d4834007976930e3c6191196
+#: ../../networking2.rst:1557
+msgid "Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS)."
+msgstr "在XenServer和KVM上使用PVALN之前，请启用Open vSwitch (OVS)。"
+
+# 801f968d2c41437ab6df2a4e4ba571f9
+#: ../../networking2.rst:1560
+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 "XenServer和KVM中的OVS不支持原生的PVLAN。因此，靠修改flow table，CloudStack为XenServer和KVM模拟OVS中的PVLAN。"
+
+# 11c21ce678fe4324bddd45de27ee2be7
+#: ../../networking2.rst:1565
+msgid "Creating a PVLAN-Enabled Guest Network"
+msgstr "配置一个启用了PVLAN的来宾网络"
+
+# 3a96dbbceb574c5fa075e67bf6efd8eb
+#: ../../networking2.rst:1625
+msgid ""
+"**Secondary Isolated VLAN ID**: The unique ID of the Secondary Isolated "
+"VLAN."
+msgstr "**辅助隔离VLAN ID**：辅助隔离VLAN的唯一ID。"
+
+# 7030034cd1d8428a993a53ec2cf81a4b
+#: ../../networking2.rst:1628
+msgid ""
+"For the description on Secondary Isolated VLAN, see `About Private VLAN\" "
+"<#about-private-vlan>`_."
+msgstr "更多关于辅助隔离VLAN的描述，请参考see `关于 Private VLAN\" <#about-private-vlan>`_."
+
+# 3334596753684a6cae9e21d47cf11119
+#: ../../networking2.rst:1691
+msgid "Security Groups"
+msgstr "安全组"
+
+# e6afa18d968443a988f9cda5396370a6
+#: ../../networking2.rst:1694
+msgid "About Security Groups"
+msgstr "关于安全组"
+
+# 12db6b6e0abb441ca307862c39b2f3a7
+#: ../../networking2.rst:1696
+msgid ""
+"Security groups provide a way to isolate traffic to VMs. 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. Security groups are particularly useful in zones that use basic "
+"networking, because there is a single guest network for all guest VMs. In "
+"advanced zones, security groups are supported only on the KVM hypervisor."
+msgstr "安全组提供一种方法来隔离VMs流量。一个安全组是一组依照设置名为入口规则和出口规则来过滤他们进出流量的VMs，这些规则依靠与VM通讯的IP地址来过滤网络流量。安全组在使用基础网络的zones中尤为重要，因为这里只有一个来宾网络。在高级zones中，只有KVM hypervisor支持安全组。"
+
+# 5e0a423faa66428cb475ef10f065148b
+#: ../../networking2.rst:1706
+msgid ""
+"In a zone that uses advanced networking, you can instead define multiple "
+"guest networks to isolate traffic to VMs."
+msgstr "在一个使用高级网络的zone中，你可以改为定义多个来宾网络隔离流量至VMs。"
+
+# d58dc8ccb7ac4d10926fb53edabf176a
+#: ../../networking2.rst:1708
+msgid ""
+"Each CloudStack account comes with a default security group that denies all "
+"inbound traffic and allows all outbound traffic. The default security group "
+"can be modified so that all new VMs inherit some other desired set of rules."
+msgstr "每个CloudStack账号匹配一个拒绝所有入站流量和允许所有出口流量的默认安全组 。可以编辑默认的安全组以便所有新VMs的策略继承一些的想要的设置。"
+
+# 39f399e25b2f415d8584bd6f5dd19360
+#: ../../networking2.rst:1713
+msgid ""
+"Any CloudStack user can set up any number of additional security groups. "
+"When a new VM is launched, it is assigned to the default security group "
+"unless another user-defined security group is specified. A VM can be a "
+"member of any number of security groups. Once a VM is assigned to a security"
+" group, it remains in that group for its entire lifetime; you can not move a"
+" running VM from one security group to another."
+msgstr "任何CloudStack用户可以增加任意数量的安全组。当一个新的VM运行起来的时候，它会被添加到默认安全组除非其他用户指定了其他安全组。一个VM可以是任何安全组的成员。一旦VM被添加到一个安全组，它会继承这个组的生命周期；你不能移动一台正在运行的VM到其他安全组。"
+
+# bd1a3a7c766a49568e5d389c615a00fd
+#: ../../networking2.rst:1720
+msgid ""
+"You can modify a security group by deleting or adding any number of ingress "
+"and egress rules. When you do, the new rules apply to all VMs in the group, "
+"whether running or stopped."
+msgstr "你可以通过删除或添加任意的入口和出口策略来修改一个安全组。当你这么做的时候，新的策略会应用到组中的所有VMs，无论是运行的还是关机的。"
+
+# a52edc5536e9495bbf1410f462d5932b
+#: ../../networking2.rst:1724
+msgid ""
+"If no ingress rules are specified, then no traffic will be allowed in, "
+"except for responses to any traffic that has been allowed out through an "
+"egress rule."
+msgstr "如果没有指定入口规则，那么流量会被禁止，除了已经允许通过一个出口规则响应任何流量 。"
+
+# 7d25ba3d47574104ae0d8c4085970ddc
+#: ../../networking2.rst:1729
+msgid "Adding a Security Group"
+msgstr "添加一个安全组"
+
+# 4a52e8eaf7f5498e9cac0ef8d3e753bb
+#: ../../networking2.rst:1731
+msgid "A user or administrator can define a new security group."
+msgstr "一个用户或者管理员能定义一个新的安全组。"
+
+# a705e539e74940a78a8983f0585d2556
+# c227631e574645b2b6062f0bf192b879
+#: ../../networking2.rst:1739 ../../networking2.rst:1819
+msgid "In the left navigation, choose Network"
+msgstr "在左侧的导航栏，选择网络"
+
+# 7c3b2c1204ad4116b2771e974c0cf4c2
+#: ../../networking2.rst:1743
+msgid "In Select view, choose Security Groups."
+msgstr "在选择视图中，选择安全组。"
+
+# 721d38433467434482cb1c4486f14572
+#: ../../networking2.rst:1747
+msgid "Click Add Security Group."
+msgstr "点击添加安全组。"
+
+# 02ecffe07c904fc2a4c3fa6a392afd04
+#: ../../networking2.rst:1751
+msgid "Provide a name and description."
+msgstr "提供一个名称和描述。"
+
+# 3e0ee4bc42fc4ea2a3189f69cde928db
+#: ../../networking2.rst:1757
+msgid "The new security group appears in the Security Groups Details tab."
+msgstr "新的安全组出现在安全组详细信息标签中。"
+
+# 1b1ca02aa0b348c1b8d8e92f7dbe459d
+#: ../../networking2.rst:1761
+msgid ""
+"To make the security group useful, continue to Adding Ingress and Egress "
+"Rules to a Security Group."
+msgstr "要使安全组生效，继续给这个安全组添加入口和出口策略。"
+
+# 6d68ff5e482a496ea71d636366da8518
+#: ../../networking2.rst:1765
+msgid "Security Groups in Advanced Zones (KVM Only)"
+msgstr "高级区域中的安全组（只针对KVM）"
+
+# bf3e0daa32bd4d928334c6593b3da60d
+#: ../../networking2.rst:1767
+msgid ""
+"CloudStack provides the ability to use security groups to provide isolation "
+"between guests on a single shared, zone-wide network in an advanced zone "
+"where KVM is the hypervisor. Using security groups in advanced zones rather "
+"than multiple VLANs allows a greater range of options for setting up guest "
+"isolation in a cloud."
+msgstr "以KVM作为虚拟机时，在单共享广域的网络内，CloudStack可以通过安全组来隔离客户。通过使用安全组而不是多VLAN，可以在云中隔离客户时具有更高的灵活性"
+
+# a13d1f37385b4e7b86996acde4babec4
+#: ../../networking2.rst:1776
+msgid "The following are not supported for this feature:"
+msgstr "下列不支持此功能："
+
+# 8fc8b70b5cde4f87a62e5b1ca4a75e2a
+#: ../../networking2.rst:1780
+msgid ""
+"Two IP ranges with the same VLAN and different gateway or netmask in "
+"security group-enabled shared network."
+msgstr "在开启了安全组的共享网络内，同一VLAN内具有不同网关或掩码的二个IP范围，"
+
+# 9afc1351e88841e18eb5fe14fc168913
+#: ../../networking2.rst:1785
+msgid ""
+"Two IP ranges with the same VLAN and different gateway or netmask in "
+"account-specific shared networks."
+msgstr "在共享网络的特殊帐户内，同一VLAN内具有不同网关或掩码的二个IP范围"
+
+# 964239c4525b49c48d33e98fa19650e7
+#: ../../networking2.rst:1790
+msgid "Multiple VLAN ranges in security group-enabled shared network."
+msgstr "在开启了安全组共享网络的多VLAN范围"
+
+# 0e18491db0744181b7e4947503a5bf06
+#: ../../networking2.rst:1794
+msgid "Multiple VLAN ranges in account-specific shared networks."
+msgstr "在共享网络的特殊帐户内，多个VLAN范围"
+
+# 05bc77a1a85b4d40ac91eb83feacc795
+#: ../../networking2.rst:1796
+msgid ""
+"Security groups must be enabled in the zone in order for this feature to be "
+"used."
+msgstr "为使用此特性，在区域内必须开启安全组"
+
+# e64a176e0d1a4f50992f36b58586ff9e
+#: ../../networking2.rst:1800
+msgid "Enabling Security Groups"
+msgstr "开启安全组"
+
+# 6ad796b8b65541758fa9ac87509ecbc2
+#: ../../networking2.rst:1802
+msgid ""
+"In order for security groups to function in a zone, the security groups "
+"feature must first be enabled for the zone. The administrator can do this "
+"when creating a new zone, by selecting a network offering that includes "
+"security groups. The procedure is described in Basic Zone Configuration in "
+"the Advanced Installation Guide. The administrator can not enable security "
+"groups for an existing zone, only when creating a new zone."
+msgstr "使用安全组功能之前，必须先在Zone中启用安全组功能。系统管理员可以在创建一个新的Zone时，通过选择带‘安全组’功能的网络方案进行启用。在高级安装指南的基本Zone配置中有该过程的详细描述。系统管理员不能对现有Zone启用安全组，只能在新建Zone时启用。"
+
+# e2ba36a71c01454c872db51e3f32589d
+#: ../../networking2.rst:1811
+msgid "Adding Ingress and Egress Rules to a Security Group"
+msgstr "对安全组添加入口出口规则"
+
+# a1a516287e0441a7bfff434dc4c25818
+#: ../../networking2.rst:1823
+msgid ""
+"In Select view, choose Security Groups, then click the security group you "
+"want ."
+msgstr "在选择视图中，选择安全组，然后点击需要的安全组"
+
+# d6e55c16dfbc4f85a9169f71f66a2804
+#: ../../networking2.rst:1828
+msgid ""
+"To add an ingress rule, click the Ingress Rules tab and fill out the "
+"following fields to specify what network traffic is allowed into VM "
+"instances in this security group. If no ingress rules are specified, then no"
+" traffic will be allowed in, except for responses to any traffic that has "
+"been allowed out through an egress rule."
+msgstr "为增加入口规则，点击入口规则并填写相应内容，以说明在此安全组内何种网络流量可以到达虚拟机实例。如果没有说明入口规则，则不会允许流量进入。也就只有出口规允许的流量了。"
+
+# 42943b264de7449685e9e46efc6a170c
+#: ../../networking2.rst:1836
+msgid ""
+"**Add by CIDR/Account**. Indicate whether the source of the traffic will be "
+"defined by IP address (CIDR) or an existing security group in a CloudStack "
+"account (Account). Choose Account if you want to allow incoming traffic from"
+" all VMs in another security group"
+msgstr "通过CIDR帐户添加。表明在CloudStack帐户中是否有CIDR定义的流量来源或是已存在的安全组。如果允许来自另一安全组的所有虚拟机的流量进入，则添加此帐户。"
+
+# e2cc45d1de64494db50fe0a1c454f1de
+#: ../../networking2.rst:1844
+msgid ""
+"**Protocol**. The networking protocol that sources will use to send traffic "
+"to the security group. TCP and UDP are typically used for data exchange and "
+"end-user communications. ICMP is typically used to send error messages or "
+"network monitoring data."
+msgstr "协议。发送源会使用网络协议来发送流量到安全组。TCP和UDP是典型的二种用来数据交换和终端用户交流的协议。ICMP则用来发送错误信息或网络监控数据"
+
+# 3830ab6e902f4099a0d5bcd5f94c98f9
+#: ../../networking2.rst:1851
+msgid ""
+"**Start Port, End Port**. (TCP, UDP only) A range of listening ports that "
+"are the destination for the incoming traffic. If you are opening a single "
+"port, use the same number in both fields."
+msgstr "开始端口，结束端口。（仅对TCP，UDP）。目的地为进入流量而设的监听端口范围。如果仅开放了单个端口，则在两者的区域中用同一端口。"
+
+# 8964c7df1073444194c59e9ddf9726c6
+#: ../../networking2.rst:1857
+msgid ""
+"**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code "
+"that will be accepted."
+msgstr "ICMP类型，ICMP编码。（仅对ICMP）。接受的信息及错误码的类型。"
+
+# b0cf8f7cc93e4879aab846412508fb1a
+#: ../../networking2.rst:1862
+msgid ""
+"**CIDR**. (Add by CIDR only) To accept only traffic from 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 incoming traffic. For example,"
+" 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr "CIDR（仅通过CIDR添加）。为接受来来自特殊地址块的流量，输入一个CIDR，多个时用逗号隔开。CIDR是进入流量的基础IP地址。例如：192.168.0.0/22，为允许所有CIDR，请设为0.0.0.0/0"
+
+# 76c5ca0cfe334149a512d3956349b0df
+#: ../../networking2.rst:1870
+msgid ""
+"**Account, Security Group**. (Add by Account only) To accept only traffic "
+"from another security group, enter the CloudStack account and name of a "
+"security group that has already been defined in that account. To allow "
+"traffic between VMs within the security group you are editing now, enter the"
+" same name you used in step 7."
+msgstr "帐户，安全组。（仅通过帐户添加）。为接受来自另一安全组的流量，输入一个CloudStack帐户和在此帐户中已经定义的安全组的名字。为允许你正在编辑的安全组内虚拟机之间的流量，输入你在第7步使用的相同的名字。"
+
+# 3903c6ce7d964ff99823291ab66fd97e
+#: ../../networking2.rst:1876
+msgid "The following example allows inbound HTTP access from anywhere:"
+msgstr "下面这个例子允许内部任何地方的HTTP访问"
+
+# 0ca36e66c67f4b0fbc6e9642f98244e2
+#: ../../networking2.rst:1878
+msgid "|httpaccess.png|"
+msgstr "|httpaccess.png|"
+
+# 0e328d3fe5ff4d199d094778ca339694
+#: ../../networking2.rst:1882
+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 security group. If no egress rules are specified, then all"
+" traffic will be allowed out. Once egress rules are specified, the following"
+" types of traffic are allowed out: traffic specified in egress rules; "
+"queries to DNS and DHCP servers; and responses to any traffic that has been "
+"allowed in through an ingress rule"
+msgstr "为添加一个出口规则，点击出口规则并填写以下内容，以说明在此安全组内的虚拟机，被允许哪一类型的流量送出。如果出口规则没有说明，所以的流量都被允许出去一旦进行了说明，则以下流量可以允许出去：在出口规则中进行说明的，查询DNS和DHCP服务器的，响应来自入口规则允许进入的流量的"
+
+# 6345c89e81524779ab6e143c18064dbf
+#: ../../networking2.rst:1893
+msgid ""
+"**Add by CIDR/Account**. Indicate whether the destination of the traffic "
+"will be defined by IP address (CIDR) or an existing security group in a "
+"CloudStack account (Account). Choose Account if you want to allow outgoing "
+"traffic to all VMs in another security group."
+msgstr "通过CIDR帐户添加。表明流量目的地是否已通过CIDR定义或是CloudStack帐户内存在的安全组。选择帐户，以允许流量到其安全组内所有虚拟机"
+
+# 3aacbdb631954d769b273926968b7e76
+#: ../../networking2.rst:1901
+msgid ""
+"**Protocol**. The networking protocol that VMs will use to send outgoing "
+"traffic. TCP and UDP are typically used for data exchange and end-user "
+"communications. ICMP is typically used to send error messages or network "
+"monitoring data."
+msgstr "协议：虚拟机发送流量需要的协议。TCP和UDP是典型的二种用来数据交换和终端用户交流的协议。ICMP则用来发送错误信息或网络监控数据"
+
+# bf325442015447ccacf5f769195e3e42
+#: ../../networking2.rst:1908
+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 "开始端口，结束端口。（仅对TCP，UDP）。目的地为进入流量而设的监听端口范围。如果仅开放了单个端口，则在两者的区域中用同一端口。"
+
+# 6018cd1041b946a9a0e09343687a2ef2
+#: ../../networking2.rst:1914
+msgid ""
+"**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code "
+"that will be sent"
+msgstr "ICMP类型，ICMP编码。（仅对ICMP）。信息及错误码的类型。"
+
+# dcedb9aa8a5f45fc8708767a08ba30e5
+#: ../../networking2.rst:1919
+msgid ""
+"**CIDR**. (Add by CIDR only) To send traffic only to 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 "CIDR（仅通过CIDR添加）。为接受来来自特殊地址块的流量，输入一个CIDR，多个时用逗号隔开。CIDR是进入流量的基础IP地址。例如：192.168.0.0/22，为允许所有CIDR，请设为0.0.0.0/0"
+
+# 7fe28834c4e944fa960b6bc798395bb8
+#: ../../networking2.rst:1927
+msgid ""
+"**Account, Security Group**. (Add by Account only) To allow traffic to be "
+"sent to another security group, enter the CloudStack account and name of a "
+"security group that has already been defined in that account. To allow "
+"traffic between VMs within the security group you are editing now, enter its"
+" name."
+msgstr "帐户，安全组。（仅通过帐户添加）。为接受来自另一安全组的流量，输入一个CloudStack帐户和在此帐户中已经定义的安全组的名字。为允许你正在编辑的安全组内虚拟机之间的流量，输入名字。"
+
+# b98f0fffba9942f6b1c8338e399cd238
+#: ../../networking2.rst:1938
+msgid "External Firewalls and Load Balancers"
+msgstr "外部防火墙及负载均衡"
+
+# 538d6ddab6754d2f95ed16d1c8c19a47
+#: ../../networking2.rst:1940
+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 "CloudStack允许通过外部的Jniper SRX 设备和外部NetScaler设备或网关负载均衡设备和负载均衡服务。在此情形下，虚拟机使用SRX作为网关。"
+
+# 5b34eb6058a24e94801076fbb7ad2149
+#: ../../networking2.rst:1946
+msgid "About Using a NetScaler Load Balancer"
+msgstr "关于使用NetScaler负载均衡器"
+
+# a78cf7cfee394628aaab85679c2ff14d
+#: ../../networking2.rst:1948
+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 "在区域中，或高级区域使用隔离网络时，CloudStack支持思杰的NetScaler作为外部网络设备元素作为负责均衡。拟通过其他方案提供负载均衡而不是CloudStack的虚拟路由器时，就可以建立一个外部负载均衡器"
+
+# b05631eea76f43049dad194f18a6a9b6
+#: ../../networking2.rst:1954
+msgid ""
+"In a Basic zone, load balancing service is supported only if Elastic IP or "
+"Elastic LB services are enabled."
+msgstr "在基础区域中，仅在弹性IP或弹性负载均衡服务开启时，才支持负载均衡服务"
+
+# 705041b2434b4ca483b18e0e974897dc
+#: ../../networking2.rst:1956
+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 device providing "
+"EIP/ELB, layer 3 router must have a policy-based routing. A policy-based "
+"route must be set up so that all traffic originated from the guest VM's are "
+"directed to NetScaler device. This is required to ensure that the outbound "
+"traffic from the guest VM's is routed to a public IP by using NAT.For more "
+"information on Elastic IP, see `\"About Elastic IP\" <#about-elastic-ip>`_."
+msgstr "在基础域中使用NetScaler负载均衡提供EIP或ELB服务时，确保所有的客户虚拟机流量必须通过NetScaler设备进出。当入流量通过NetScaler设备时流量通过使用NAT协议被路由，此NAT协议依赖于公共IP到私有IP的配置。来自客户虚拟机的流量通常要经过3层路由器，为确保出流量通过提供EIP/ELB的NetScaler设备，3层路由器，必须具有基础策略。必有设立一个具有基础策略的路由器可保证所有客户机的流量都能转向NetScaler设备。这也需要确保客户虚拟机的出流量通过使用NAT被路由到公共IP。关于EIP的更多信息，参看`\"关于EIP\" <#about-elastic-ip>`_."
+
+# 6bfdd4158ad14aa38deebe45fb9cbb9a
+#: ../../networking2.rst:1970
+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 "NetScaler可以设置成直通模式。它必须在区域中部署客户虚拟机负载均衡规则之前加入。"
+
+# d0b9fb7fee614995a8c6fa5905fff158
+#: ../../networking2.rst:1974
+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 "CloudStack中NetScaler的功能作用与CloudStack文档中说明的使用F5 外部负载均衡器的功能作用相同。一点差别就是，F5支持路由域名，而NetScaler无此功能。NetScaler也不可以用作防火墙。"
+
+# 11e9cfee2a764a7fb0b70afb98d31c3b
+#: ../../networking2.rst:1979
+msgid ""
+"To install and enable an external load balancer for CloudStack management, "
+"see External Guest Load Balancer Integration in the Installation Guide."
+msgstr "为CLOUDSTACK管理端安装和启用外部负载均衡功能，参阅安装文档里的外部客户负载均衡。"
+
+# 1fb1edcb2b6d4ffaa95d0fbe2737024a
+#: ../../networking2.rst:1983
+msgid ""
+"The Citrix NetScaler comes in three varieties. The following table "
+"summarizes how these variants are treated in CloudStack."
+msgstr "思杰的NetScaler有三种变化，下表总结了在CloudStack中如何处理那些变化。"
+
+# 12edf1030b1a46dea557408534fb87af
+#: ../../networking2.rst:1986
+msgid "NetScaler ADC Type"
+msgstr "NetScaler ADC Type"
+
+# 76d92f88c012490b8f745539f5beff17
+#: ../../networking2.rst:1988
+msgid "Description of Capabilities"
+msgstr "性能描述"
+
+# 85070d10ba6a46b6b7e646e0e6e68101
+#: ../../networking2.rst:1990
+msgid "CloudStack Supported Features"
+msgstr "CLOUDSTACK支持的功能"
+
+# 04cb1b68ff3b48edabc301bf64ccf560
+#: ../../networking2.rst:1992
+msgid "MPX"
+msgstr "MPX"
+
+# 2d07236e0fb24abc935fc25da378dc09
+#: ../../networking2.rst:1994
+msgid ""
+"Physical appliance. Capable of deep packet inspection. Can act as "
+"application firewall and load balancer"
+msgstr "物理应用。能够进行深度数据包检测。可作为防火墙和负载均衡应用。"
+
+# ec6682993a804b9e9f80b1d00004182e
+#: ../../networking2.rst:1997
+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 "在高级区域中，完全支持负载均衡功能，没有限制。在基础区域中，也提供静态NAT，EIP，ELB功能。"
+
+# b9ff4330d7774617b6ae9a5e7a8a6f1d
+#: ../../networking2.rst:2001
+msgid "VPX"
+msgstr "VPX"
+
+# 9005b76458ad41a483ee097a591c21db
+#: ../../networking2.rst:2003
+msgid ""
+"Virtual appliance. Can run as VM on XenServer, ESXi, and Hyper-V "
+"hypervisors. Same functionality as MPX"
+msgstr "虚拟应用，可以运行在XenServer，ESXi以及Hyper-V上虚拟机上。与MPX功能相同。"
+
+# 3685fe921180440098631978824bd41e
+#: ../../networking2.rst:2006
+msgid ""
+"Supported on ESXi and XenServer. Same functional support as for MPX. "
+"CloudStack will treat VPX and MPX as the same device type."
+msgstr "在ESXi和XenServer上支持。对MPX也支持一些功能。CloudStack将VPX和MPX作为同一类型的设备看待。"
+
+# b4d1336da974407c9db6af169f5b24ff
+#: ../../networking2.rst:2009
+msgid "SDX"
+msgstr "SDX"
+
+# 62d3529ceb9a40a5a2112aff3c4ee083
+#: ../../networking2.rst:2011
+msgid ""
+"Physical appliance. Can create multiple fully isolated VPX instances on a "
+"single appliance to support multi-tenant usage"
+msgstr "物理应用。可以在单个应用上创建多个完全隔离的VPX实例，以支持多客户使用。"
+
+# 926617dc198f41458aa9112b482a4259
+#: ../../networking2.rst:2014
+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 "CloudStack会动态分配，配置，管理在SDX上的虚拟机实例的生命周期。分配的实例会自动加入到CloudStack，不需要管理员进行手动配置。一旦一个VPX实例加入到CloudStack，将会认为是ESXi主机上的一个VPX。"
+
+# 05a9bff4e49b4e6faaeeecdcf5ef0c7e
+#: ../../networking2.rst:2021
+msgid "Configuring SNMP Community String on a RHEL Server"
+msgstr "在RHEL服务器上配置SNMP社区字符串"
+
+# 75f35b06310648d3a4b6bfddf33bc68e
+#: ../../networking2.rst:2023
+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 "SNMP社区字符串类似于用户ID或用户密码，用来登录网络设备，如路由器。这类字符串随着所有的SNMP请求发送。如果社区字符串正确，设备将反馈相应的字符串若不正确，设备将丢弃请求，不进行处理。"
+
+# 9c719f6ec799444b9ad1bf98205eabc8
+#: ../../networking2.rst:2029
+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 "NetScaler设备使用SNMP与虚拟机进行通讯。为保证NetScaler设备与RHEL机器之间安全的通讯，必须安装并配置社区字符串。"
+
+# bdc592b5c12d4fc9bbfb1cb4bf44b046
+#: ../../networking2.rst:2035
+msgid ""
+"Ensure that you installed SNMP on RedHat. If not, run the following command:"
+msgstr "确保在RedHat上安装了SNMP，如果没有，执行以下命令:"
+
+# 02cf855a387949f3b83f4bb528cbf1c4
+#: ../../networking2.rst:2044
+msgid ""
+"Edit the /etc/snmp/snmpd.conf file to allow the SNMP polling from the "
+"NetScaler device."
+msgstr "编辑/etc/snmp/snmpd.conf 文件，以允许来自NetScaler设备的SNMP查询"
+
+# 1decbe06fdbd45039c5b61ab7d3088d9
+#: ../../networking2.rst:2049
+msgid ""
+"Map the community name into a security name (local and mynetwork, depending "
+"on where the request is coming from):"
+msgstr "映射社区名到一个安全的名字（本地，我的网络，依赖于其来源）"
+
+# 8a17ab86a6dd4d5787e52b8e4414895f
+#: ../../networking2.rst:2053
+msgid ""
+"Use a strong password instead of public when you edit the following table."
+msgstr "编辑下表时，使用一个强密码"
+
+# 0179988cd69648e98566be83bd2dff14
+#: ../../networking2.rst:2062
+msgid "Setting to 0.0.0.0 allows all IPs to poll the NetScaler server."
+msgstr "设置0.0.0.0以允许所有的IP都可以查询NetScaler设备"
+
+# 6577e90762254a09835bb6467df5a6ba
+#: ../../networking2.rst:2066
+msgid "Map the security names into group names:"
+msgstr "映射一个安全名到组名"
+
+# e25e9e1efba84febaa488370009ea353
+#: ../../networking2.rst:2078
+msgid "Create a view to allow the groups to have the permission to:"
+msgstr "创建一个视图，以允许组有权限执行："
+
+# 45d988cd96b04573b080085fbd6ee6cb
+#: ../../networking2.rst:2086
+msgid ""
+"Grant access with different write permissions to the two groups to the view "
+"you created."
+msgstr "授权不同的写权限给二个组及你创建的视图"
+
+# 9fc121277fb04877af683ce49e88b40b
+#: ../../networking2.rst:2097
+msgid "Unblock SNMP in iptables."
+msgstr "在iptalbes中解除对SNMP的锁定。"
+
+# ce86c5292fa840f194d550efe25863bf
+#: ../../networking2.rst:2105
+msgid "Start the SNMP service:"
+msgstr "开启SNMP服务："
+
+# c68c4cc6430e45fb8625e65486ad2c89
+#: ../../networking2.rst:2113
+msgid ""
+"Ensure that the SNMP service is started automatically during the system "
+"startup:"
+msgstr "确保在系统启动时，SNMP服务能够自动启动。"
+
+# 9a86418eaea24d238f86754265515817
+#: ../../networking2.rst:2121
+msgid "Initial Setup of External Firewalls and Load Balancers"
+msgstr "初始化安装外部防火墙和负载均衡"
+
+# 06a101bd0fb84bd0b26f130d1a867429
+#: ../../networking2.rst:2123
+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 "当为一个新帐户创建一个虚拟机时，CloudStack会设置程序以让外部防火墙和负载均衡与虚拟机共同工作。会在防火墙上创建以下对象："
+
+# ab3bbc626f914afe9ac2a1b689262029
+#: ../../networking2.rst:2129
+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 "一个新的逻辑接口，用以连接帐户的私有VLAN。接口的IP通常是私有帐户私有子网的第一个IP。"
+
+# f006b40c148b48a08def3072e5ad067c
+#: ../../networking2.rst:2135
+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 "一个源NAT规则转发帐户从私有VLAN到公共网络的的出口流量，使用帐户的公共IP地址作为源地址。"
+
+# cd7a4e14c7984cd284aa60828cf93747
+#: ../../networking2.rst:2141
+msgid ""
+"A firewall filter counter that measures the number of bytes of outgoing "
+"traffic for the account"
+msgstr "防火墙过滤计数器计量帐户出口流量的字节数"
+
+# 6863d2e715784256ae2aa22351962b89
+#: ../../networking2.rst:2144
+msgid "The following objects are created on the load balancer:"
+msgstr "以下对象会在负载均衡上创建："
+
+# 9f6423f23a65442d8e2bda3bb6db462b
+#: ../../networking2.rst:2148
+msgid "A new VLAN that matches the account's provisioned Zone VLAN"
+msgstr "匹配帐户区域VLAN的私有VLAN。"
+
+# 72187f0b05e848e6967cdb9a555381db
+#: ../../networking2.rst:2152
+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 "一个VLAN的自有IP。经常是帐户私有子网的第二个IP。"
+
+# ab8a654963914f2baa6cec082bc98b83
+#: ../../networking2.rst:2156
+msgid "Ongoing Configuration of External Firewalls and Load Balancers"
+msgstr "继续配置外部防火墙和负载均衡"
+
+# 6cc8786791794c06befa8a17509abd10
+#: ../../networking2.rst:2158
+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 objects:"
+msgstr "增加的用户行为(如设置端口转发)会引起防火墙和负载均衡的程序化。一个用户可以请求增加公共IP地址以及转发使用此公共IP地址的虚拟机接受到的流量。这是通过静态NAT功能完成的，静态NAT将一个公共IP地址映射给一个虚拟机，并指定一组特定协议，开放一组特定端口。当静态NAT建立好之后，CLOUDSTACK会在区域的外部防火墙上通过程序定制如下对象："
+
+# 1264629934524065bc84801e9205e4a5
+#: ../../networking2.rst:2169
+msgid ""
+"A static NAT rule that maps the public IP address to the private IP address "
+"of a VM."
+msgstr "一条静态NAT规则将虚拟机的私有IP地址映射到公共IP地址。"
+
+# c5fc12f27ace4872a52cb589ca35d678
+#: ../../networking2.rst:2174
+msgid ""
+"A security policy that allows traffic within the set of protocols and port "
+"ranges that are specified."
+msgstr "一个安全策略可以允许说明的协议和端口范围内的流量通过。"
+
+# 3987c5c775d14d12b88cb87ad208f691
+#: ../../networking2.rst:2179
+msgid ""
+"A firewall filter counter that measures the number of bytes of incoming "
+"traffic to the public IP."
+msgstr "防火墙过滤计数器计量到达此公共IP的流量"
+
+# c5db6b14c530477fbdab470760ab4530
+#: ../../networking2.rst:2182
+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 "通过源NAT，静态NAT以及负载均衡规则进出的字节数均被计量并保存在每一个外部设备中。按一定的规则对这些数据进行收集，并将其存储在CloudStack的数据库中。"
+
+# ffe7e0e1d6a54f58847e94107290cdea
+#: ../../networking2.rst:2188
+msgid "Load Balancer Rules"
+msgstr "负载均衡规则"
+
+# c4c2a4ed95bf4c308ca4f5e48b75081b
+#: ../../networking2.rst:2190
+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 "一个CloudStack的用户或管理员可以创建负载均衡规则以平衡一个公共IP地址收到的针对一个或多个虚拟机的外部流量。一个用户可以创建一条规则，说明一个算法，并将其指定给一部分虚拟机。"
+
+# 5edeb5d8028f43088fd22e105d890c45
+#: ../../networking2.rst:2196
+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 "如果你创建了一个负载均衡规则且使用包括外部负载均衡设备的网络服务方案，如包括NetScaler，但随后将网络方案改成使用CloudStack的虚拟路由器，则你必须在虚拟路由器上创建一个防火墙规则，这些防火墙规则与已经设置的负载均衡规则一一对应，只有这样，才能使那些负载均衡规则继续起作用。"
+
+# aee5ead118ba49d2af6fd663749cb21a
+#: ../../networking2.rst:2206
+msgid "Adding a Load Balancer Rule"
+msgstr "增加一条负载均衡规则"
+
+# ef9ec7e8608f4622a42b9006e67332f1
+#: ../../networking2.rst:2218
+msgid ""
+"Click the name of the network where you want to load balance the traffic."
+msgstr "点击拟进行负载均衡的网络名称"
+
+# d56ea994f5094995b0b1a4f7aa68eca8
+# 7764a67f3ade40b1b3dc2075fac839f4
+# ff64344bfa4d4a28a323dffd869d78cc
+#: ../../networking2.rst:2227 ../../networking2.rst:6334
+#: ../../networking2.rst:6728
+msgid ""
+"Click the IP address for which you want to create the rule, then click the "
+"Configuration tab."
+msgstr "点击你希望创建规则的IP地址，然后点击配置"
+
+# bd1517a9c2da449f8664512b691ebb65
+# 563ad659bddb4945a34373de5161db96
+#: ../../networking2.rst:2232 ../../networking2.rst:6339
+msgid "In the Load Balancing node of the diagram, click View All."
+msgstr "在图的负载均衡节点点上，点击 查看全部。"
+
+# 5c4e645be6564d2981406da6582c05fa
+#: ../../networking2.rst:2234
+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 "在基础区域中，在不需要或不选择IP的条件下，你可以创建一条负载均衡规则。当你创建负载均衡规则时，CloudStack会内部指定一个IP地址。当规则创建完成时，IP地址会在IP地址页列出来。"
+
+# 19e72807452b47e3a1cc379d4795b3d9
+#: ../../networking2.rst:2239
+msgid ""
+"To do that, select the name of the network, then click Add Load Balancer "
+"tab. Continue with #7."
+msgstr "为此，选择网络名称，点击 增加负载均衡。按#7继续进行配置。"
+
+# 92a8a5aa771d4722b5156213b1af4fd5
+# 130044af73ab495bab3655cce16db603
+#: ../../networking2.rst:2244 ../../networking2.rst:3732
+msgid "Fill in the following:"
+msgstr "填写以下内容："
+
+# 96cfbfac34a546b2aabfdd57984816d9
+# 2f3e7f66b6854ce1bf779bd548cb6f12
+# 0e0ff88d07eb4baf9edfced6bfbc8d7b
+#: ../../networking2.rst:2248 ../../networking2.rst:6351
+#: ../../networking2.rst:6609
+msgid "**Name**: A name for the load balancer rule."
+msgstr "名称，负载均衡规则的名称。"
+
+# d159c92df5a7480c9ea3390d74166c14
+#: ../../networking2.rst:2252
+msgid "**Public Port**: The port receiving incoming traffic to be balanced."
+msgstr "公共端口。这个端口接受到负载均衡的进入流量。"
+
+# b581656e45d34c8d81bf85c2f5e1687d
+# 4bc8d2ff0de548bfac5f09a67456130e
+#: ../../networking2.rst:2257 ../../networking2.rst:6360
+msgid ""
+"**Private Port**: The port that the VMs will use to receive the traffic."
+msgstr "私有端口，虚拟机会使用此端口接收流量。"
+
+# 2543a97cf11048648e1d03e65b26ff8e
+#: ../../networking2.rst:2262
+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 "算法，选择让CloudStack使用的负载均衡算法。CloudStack各类已知的算法，如果不熟悉那些选项，通过goole搜索会发现大量信息。"
+
+# 0e85be5a5f044e87a64418a1378234c5
+#: ../../networking2.rst:2269
+msgid ""
+"**Stickiness**: (Optional) Click Configure and choose the algorithm for the "
+"stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr "粘性：点击配置，为粘性策略选择一个算法。可参见为负载均衡规则制定的粘性会话策略。"
+
+# d254fa1eae76499aa9dd3674a7ccb16e
+#: ../../networking2.rst:2275
+msgid ""
+"**AutoScale**: Click Configure and complete the AutoScale configuration as "
+"explained in :ref:`conf-autoscale`."
+msgstr "**自动缩放**：点击配置完成自动缩放配置，在 :ref:`conf-autoscale`中有介绍。"
+
+# 80c293bf8b72415daff417f7d1e485c2
+#: ../../networking2.rst:2280
+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 "**健康检查**：(可选，只针对NetScaler的负载均衡设备)点击配置并填写健康检查特性，参见15.16.5.3 负载均衡规则的健康检查。参见 :ref:`health-check`."
+
+# 7646c6b438bc4f6a95b867bca86d2778
+#: ../../networking2.rst:2286
+msgid ""
+"**Ping path (Optional)**: Sequence of destinations to which to send health "
+"check queries. Default: / (all)."
+msgstr "ping 路径：需要发送健康检查的目的地顺序。默认为全部。"
+
+# f2e4bc38af6b4daf89f145d9739466f4
+#: ../../networking2.rst:2291
+msgid ""
+"**Response time (Optional)**: How long to wait for a response from the "
+"health check (2 - 60 seconds). Default: 5 seconds."
+msgstr "响应时间（可选）：从健康检查返回的响应时间（2-60秒），默认为5秒。"
+
+# b56f106902c64b1c8aa0a36c64aec4ac
+#: ../../networking2.rst:2296
+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 "间隔时间（可选）：健康检查的间隔时间（1秒-5分钟）。默认值在全局参数lbrule health check_time_interval"
+
+# 4295d940156f4b3ba091563f2533eb12
+#: ../../networking2.rst:2303
+msgid ""
+"**Healthy threshold (Optional)**: Number of consecutive health check "
+"successes that are required before declaring an instance healthy. Default: "
+"2."
+msgstr "健康阀值：在声明一个实例健康之前，连续健康检查成功的次数。"
+
+# 7ac5054f47b24947b246698f28438d57
+#: ../../networking2.rst:2309
+msgid ""
+"**Unhealthy threshold (Optional)**: Number of consecutive health check "
+"failures that are required before declaring an instance unhealthy. Default: "
+"10."
+msgstr "不健康阀值（可选）：在声音一个实例不健康之前连续健康检查失败的次数。"
+
+# 7836878559f34b60b1399d767ae28a29
+#: ../../networking2.rst:2315
+msgid ""
+"Click Add VMs, then select two or more VMs that will divide the load of "
+"incoming traffic, and click Apply."
+msgstr "点击添加虚拟机，选择拟分散进入流量的二个或多个虚拟机，点击应用。"
+
+# 6a2803e8da5f48318b4b61fd67bcd43f
+#: ../../networking2.rst:2318
+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 "在列表中会出现新加的负载均衡规则。可以重复以上步骤以对此IP增加更多的负载均衡规则。"
+
+# d24dcf4899a54968b3b3db61c818c67d
+#: ../../networking2.rst:2322
+msgid "Sticky Session Policies for Load Balancer Rules"
+msgstr "为负载均衡规则制定的粘性会话策略。"
+
+# 8ab79ec71a4e4b98ad38ad17ec22af5f
+#: ../../networking2.rst:2324
+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 "粘性会话应用于基于网页的应用中，以确保在用户的会话中，对用户的多种请求持续提供信息。例如，购物者正在向购物车中增加东西，则需要记住到目前为止已买的东西。粘性的概念也指持久发现或维护状态。"
+
+# c3519ee8b4b344cabb8750b51ce2309d
+#: ../../networking2.rst:2330
+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, cookies are used. The cookie "
+"generated by the load balancer or application is included in request and "
+"response URLs to create persistence. The cookie name can be specified by the"
+" administrator or automatically generated. A variety of options are provided"
+" to control the exact behavior of cookies, such as how they are generated "
+"and whether they are cached."
+msgstr "在CloudStack中定义的任何负载均衡规则，都可以具有粘性策略。策略有名字，粘性方法以及参数组成。参数是成对的值-名或标志，这些由负载均衡提供商进行定义。粘发现方法可以加载负载均衡设备产生的cookie，应用生产的cookie，或基于源产生的cookie。在基于源的方法中，源IP地址被用来区分用户和定位用户存储的数据。在其他方法中，则使用cookie。由负载均衡或应用产生的cookie，包含在请求或响应的url中，以产生持久性。cookie的名称可以有管理员指定或自动产生。提供了多种选择来准确控制cookie行为。诸如如何产生的以及是否进行缓存。"
+
+# 79f3c606c002408f917d8fa2d8fdd9eb
+#: ../../networking2.rst:2344
+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 "对于多数粘性方法变量列表，可以参看CloudStack UI或者调用网络列表，并检查粘性方法支持能力。"
+
+# 3f62bdba5f31457aadd915d45be545a7
+#: ../../networking2.rst:2351
+msgid "Health Checks for Load Balancer Rules"
+msgstr "负载均衡规则的健康检查。"
+
+# b083bc41aca34d9b98d86dc1d0206017
+#: ../../networking2.rst:2353
+msgid "(NetScaler load balancer only; requires NetScaler version 10.0)"
+msgstr "（仅对NetScaler负载均衡设备，需要NetScaler版本10.0以上。）"
+
+# 1bf841d08f9947a9a22824b89f8e09d4
+#: ../../networking2.rst:2355
+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 "负载均衡应用中的健康检查，能够确保转发需求运行，服务可用。当创建一个负载均衡规则里，你可以指定一个健康检查策略。这是对粘性策略，算法，其他负载均衡设备规则的附加说明。可以为每一条负载均衡设备进行配置。"
+
+# 85c9feea4e8743198f31cc482695a279
+#: ../../networking2.rst:2362
+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 "在CloudStackk中的NetScaler负载均衡设备定义的任一负载均衡规则都可以有一条健康检查策略。该策略有ping路径，定义健康或非健康状态的阀值，健康检查频率以及等待超时间隔。"
+
+# 352dde5daf9c433c88293769a6bb0553
+#: ../../networking2.rst:2367
+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 with a health check "
+"configured, the state will be shown as UP or DOWN in the UI depending on the"
+" result of the most recent health check."
+msgstr "当健康检查策略生效时，负载均衡被发现处于非健康状态时，会停止转发到源的任何请求。如果随后资源变为可用，周期性进行的健康检查就会发现，此资源就会再一次被添加至从负载均衡器收到的请求资源池里。任一时刻，最近的健康检查结果会显示在UI中。对绑定了负载均衡规则的虚拟机，且此规则配置了健康检查，依据最近的检查，状态会显示为正常或失败。"
+
+# 7487d03bd3954a619c9deab8432eccb5
+#: ../../networking2.rst:2377
+msgid "You can delete or modify existing health check policies."
+msgstr "可以删除或修改存在的健康检查策略。"
+
+# 9bb908ef254545669272a47771402d19
+#: ../../networking2.rst:2379
+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 "为配置默认的健康检查执行频率，通过全局配置参数 healthcheck.update.interval进行设备，默认值是600秒。可以根据需要进行设置此值。"
+
+# a4a4e4ced2f64992a7090ec99eec5b74
+#: ../../networking2.rst:2384
+msgid ""
+"For details on how to set a health check policy using the UI, see :ref"
+":`adding-lb-rule`."
+msgstr "如何通过UI进行健康检查策略的设置，可参看 :ref:`adding-lb-rule`。"
+
+# 7583c6f2d7c04c729c049fe5fb20f1d0
+#: ../../networking2.rst:2390
+msgid "Configuring AutoScale"
+msgstr "配置自缩放"
+
+# 110dc69ca3524adf841208bc3b2afa45
+#: ../../networking2.rst:2392
+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 "自缩放允许你能够根据定义的条件进行无缝且自动的增加或减少后端服务或应用虚拟机。当开启自缩放时，可以确保在需求增加时，无缝的增加正在使用虚拟机的数量。因此他会通过关闭未使用的虚拟机或者需要时开启新的虚拟机，从而节省你的计算成本。这些操作，都不需要手动干预。"
+
+# 6067162c83174a73b67766fe147a1105
+#: ../../networking2.rst:2400
+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 CPU usage is less than 20 "
+"percent for 30 minutes."
+msgstr "NetScaler的自缩放定义为基于用户定义的条件，无缝的开启或关闭虚拟机。触发扩大或缩小行为的条件从监控服务器cpu的使用率的单一用例到监控服务器响应及cpu使用率的组合用例，各不相同。例如，你可以一个自缩放，能够在CPU使用超过80%持续15分钟时启动一个新的虚拟机，或CPU使用率低于20%持续30分钟时，移除一个虚拟机。"
+
+# 4178b892ea11419ca207b4f23416d240
+#: ../../networking2.rst:2409
+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 "CloudStack使用NetScaler负载均衡器来监控系统健康的各方面，并与CloudStack共同工作以初始化扩大或缩小的行为。"
+
+# 720fc42dfba2445580316d8a7c7b6446
+#: ../../networking2.rst:2413
+msgid ""
+"AutoScale is supported on NetScaler Release 10 Build 74.4006.e and beyond."
+msgstr "自缩放在NetScaler发布的10版本以上适用。（Build 74.4006.e 及以上）"
+
+# 25d5a916dcd24f8c93a8a2270ea1dec8
+#: ../../networking2.rst:2418
+msgid "Before you configure an AutoScale rule, consider the following:"
+msgstr "在配置自缩放前，需要考虑以下几点："
+
+# e5e20ba2d3ec4d3492856bcfe74d40f1
+#: ../../networking2.rst:2422
+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 "确保在配置自缩放时有必需的模板。当使用模板部署虚拟机并使虚拟机启动时，应用能够起动并运行。"
+
+# a3786b1dded84da299934e36c6d9e71a
+#: ../../networking2.rst:2427
+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 "如果应用没有运行，NetScaler设备会认为虚拟机无效并持续无条件的创建虚拟机，直到资源耗尽。"
+
+# 848edeadae8842dd9b6660533e51cb84
+#: ../../networking2.rst:2433
+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 "部署准备好的模板。确保应用在第一次启动时能够开启并准备好接管流量。观察部署模板需要的时间。在配置自缩放时，要考虑这段时间。"
+
+# 47a8c8b854724128bca574cad390341b
+#: ../../networking2.rst:2440
+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 RHEL Server\" "
+"<#configuring-snmp-community-string-on-a-rhel-server>`_ to configure SNMP on"
+" a RHEL machine."
+msgstr "自缩放功能支持SNMP计数，这可以用来定义扩大或缩小的前提条件。为监测SNMP计数，确保SNMP代理已经在创建自缩放虚拟机的模板中安装。通过使用标准SNMP管理器，SNMP操作可以与配置好的社区SNMP和端口一起工作。更多示例，可参见`\"在RHEL服务器上配置SNMP社区字符串\" <#configuring-snmp-community-string-on-a-rhel-server>`_ to configure SNMP on a RHEL machine.。"
+
+# c4bb8c60d3214089b1726fe9bea68db1
+#: ../../networking2.rst:2451
+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 "确保在全局配置中的结束点地址参数已设置为管理服务器的API地址。例如：``http://10.102.102.22:8080/client/api``。 在多管理节点的部署中，使用配置在负载均衡器上的虚拟IP地址作为管理服务器集群的IP地址。此外，确保NetScaler设备有读取为提供自缩放而配置的IP地址的权限。"
+
+# f6027494d923450aa21e243d185af107
+#: ../../networking2.rst:2459
+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 "如果更新了endpointe.url，在系统自动负载均衡器规则里，先关闭自缩放功能随后再开启，以应用此更新。。更多信息，参见 :ref:`update-autoscale`。"
+
+# 30b6a0dcaf8e406d930c2671bee73f49
+#: ../../networking2.rst:2465
+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 "如果为自缩放用户生成了API值和秘钥，确保用户参与的负载均衡器的自缩放功能先关闭，再开启，以应用NetScaler配置的变化。"
+
+# 8e11275ad7bc4f9bbae8488f9270ddb9
+#: ../../networking2.rst:2472
+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 "在高级区域中，在配置带自缩放的负载均衡规则时，确保至少要有一个虚拟机。在网络中存在一个虚拟机，可保证在配置自缩放时，网络处于使用状态。"
+
+# 2f62ff61696a4b28b1fe7a6e9ed379af
+#: ../../networking2.rst:2478
+msgid "Configuration"
+msgstr "配置"
+
+# 6ecf74a9baef420b8f4cf0f4a633ee47
+#: ../../networking2.rst:2482
+msgid "|autoscaleateconfig.png|"
+msgstr "|autoscaleateconfig.png|"
+
+# f28a8f2eaa864c579595a69d9339a432
+#: ../../networking2.rst:2486
+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 "模板：模板由基本的操作系统镜像和应用组成。在自缩放动作中，模板用来提供一个应用的新的实例。当从模板部署虚拟机时，虚拟机在管理员不干预的情形下开始从负载均衡器那里接管流量。例如，如果虚拟机部署为WEB服务应用，则虚拟机上的WEB服务器应该在运行，并且连接了数据库，等等。"
+
+# ab74533b03a84bf99ebf74e5eb9a1f2d
+#: ../../networking2.rst:2496
+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 "计算方案：一个预定义的虚拟硬件资源集，包括CPU速度，CPU数量，RAM，用户在创建虚拟时可以选择这些。选择一个计算方案作为提供虚拟机实例中自缩放行为的一部分。"
+
+# e0ca6e4baff64455862f60837590f305
+#: ../../networking2.rst:2504
+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 "最小实例：指定给负载均衡规则活动的虚拟机实例的最小数量，活动的虚拟机实例是开启的应用实例，并服务于流量和负载均衡。这个参数确保负载均衡规则拥有至少一个配置的活动虚拟机实例，并且能够服务于流量。"
+
+# 985d35506cb34451b0d15a405feae1a7
+#: ../../networking2.rst:2512
+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 active instance count breaches the Max"
+" instance value."
+msgstr "如果一个应用程序，比如SAP，它运行在一个VM实例上，但是VM因为某些原因宕机了，那么这个VM没有被算成是Min实例的一部分，并且如果这些活动的VM实例是下面配置的数值，那么自动扩展功能启动一个扩展的动作。同样的，当应用程序实例从宕机的状态恢复了以后，这个应用程序实例会被算为活动实例计数的一部分，并且当活动实例计数超出Max实例数值的时候，自动扩展启动一个缩减动作。"
+
+# fb0ddc4d1f94403ebeed8e5714b4f617
+#: ../../networking2.rst:2524
+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 "**最大实例数**：最大数量的**应该被指派到**\\ 一条负载均衡策略的活动VM实例。这个参数定义了能被指派到一条负载均衡策略的活动VM实例的上限。"
+
+# 783c86a84d0f4c1b833db963b51c82af
+#: ../../networking2.rst:2529
+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 "给最大量实例参数指定一个大的值可能引发大量VM实例的分发，这个过程会导致一个负载均衡策略耗尽账户或者域级别下VM实例指定的限制。"
+
+# 1a3b1e1b09e04f57993e13c4afcb55e0
+#: ../../networking2.rst:2535
+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 "如果一个应用程序，比如SAP，它运行在一个VM实例上，但是VM因为某些原因宕机了，那么这个VM没有被算成是Max实例的一部分。所以这个情况中为扩展动作分发的VMs数量可能会超过配置的MAX实例数值。一旦这个VMs中的应用程序实例从先前的宕机中恢复的时候，自动扩展功能就会校正Max实例的数值。"
+
+# 6a70933964e74afe83fe5d290058b273
+#: ../../networking2.rst:2543
+msgid "Specify the following scale-up and scale-down policies:"
+msgstr "指定下列扩展和缩减的策略："
+
+# cf10d74a5d0c41e589755735a7cedc27
+#: ../../networking2.rst:2547
+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 "**持续**：持续，以秒为单位，你必须指定条件为true以触发一个扩展动作。这个条件定义的是为了触发一个自动扩展动作，你指定的全部持续值应保持为true。"
+
+# a57ca091c3bd43c096bfa98631b1cdde
+#: ../../networking2.rst:2554
+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 "**计数器**：性能计数器直接体现了被监视实例的状态。默认情况下，CloudStack提供了4个性能计数器：3个SNMP计数器和1个NetScaler计数器。SNMP计数器是Linux User CPU、Linux System CPU和Linux CPU Idle。NetScaler计数器是ResponseTime。root管理员能够使用CloudStack API给CloudStack添加额外的计数器。"
+
+# a0b4564310ab4971b3f47a61f665d061
+#: ../../networking2.rst:2563
+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 "**运算符**：自动扩展功能支持下列5种关系型运算符：大于、小于、小于或等于、大于或等于和等于。"
+
+# e0ce29c287f846fab5b519e88ea090ee
+#: ../../networking2.rst:2569
+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 "**阈值**：阈值用于计数器。一旦上面计数器中定义的值超出阈值，自动扩展功能会启动扩展或者缩减动作。"
+
+# 6561f9d06cfe4f6d9874575da794592a
+#: ../../networking2.rst:2575
+msgid "**Add**: Click Add to add the condition."
+msgstr "**添加**:：点击添加来添加条件。"
+
+# 1497e6bea4e1463b844a038331cb983f
+#: ../../networking2.rst:2577
+msgid ""
+"Additionally, if you want to configure the advanced settings, click Show "
+"advanced settings, and specify the following:"
+msgstr "另外，如果你想配置高级设置，点击显示高级设置，接着指定下列参数："
+
+# eb929ac5f36d4e0685a50c5cc16f0df5
+#: ../../networking2.rst:2582
+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 "**轮询间隔**：组合计数器，运算和阈值这几个条件的频率在触发扩展和缩减动作之前都要被评估。默认的轮询间隔是30秒。"
+
+# 8d0aedaf4e0f45a6beda1b9421388942
+#: ../../networking2.rst:2589
+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 "**平静期**：这是自动扩展动作被触发之后的冷静期。这个时间包括完成从模板分发一个VM实例的时间和一个应用程序准备好提供服务的时间。平静期允许机群在发生任何动作之前进入稳定状态。默认值是300秒。"
+
+# fdefaeca99e24f218e68b41bfe85e3ce
+#: ../../networking2.rst:2598
+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 "**VM销毁宽限期**：此宽限期以秒计算，在一个缩减动作运行之后，在VMs被视为缩减动作的一部分从而销毁之前的等待时间。它保证了能够彻底关闭任何服务于被标记为销毁的VM的挂起中的进程或者事务。默认值是120秒。"
+
+# cf6ffe6f0c4c4e1a868a853debfcdbbf
+#: ../../networking2.rst:2606
+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 "**安全组**：安全组提供一种方法来隔离VMs流量。一个安全组是一组依照设置名为入口规则和出口规则来过滤他们进出流量的VMs，这些规则依靠与VM通讯的IP地址来过滤网络流量。"
+
+# c4bd403a66d64d868f4d5b0442abb5f7
+#: ../../networking2.rst:2615
+msgid ""
+"**Disk Offerings**: A predefined set of disk size for primary data storage."
+msgstr "**磁盘方案**：一组预定义的主数据存储磁盘大小。"
+
+# 8976b1a845f84354ab47314b3cc692d7
+#: ../../networking2.rst:2620
+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 "**SNMP 联系**：SNMP 联系字符串被用于NetScaler设备从分发的VM实例中查询已配置的计数器的值。默认是public。"
+
+# cca89ffa679d47ad992fe021145932eb
+#: ../../networking2.rst:2626
+msgid ""
+"**SNMP Port**: The port number on which the SNMP agent that run on the "
+"provisioned VMs is listening. Default port is 161."
+msgstr "**SNMP端口**：运行在已分发的VMs上的SNMP代理端口号。默认的端口是161."
+
+# e00f8d3ec41440b5b002e2041a08220f
+#: ../../networking2.rst:2631
+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 "**用户**：在云中NetScaler设备中用于发起扩展和缩减API调用的用户。如果没有指定选项，那么该用户被配置为自动扩展。指定其他用户名可以覆盖此配置。"
+
+# 9b84f1bc76c44c38a35321973e56210c
+#: ../../networking2.rst:2638
+msgid "**Apply**: Click Apply to create the AutoScale configuration."
+msgstr "**应用**：点击应用创建自动扩展配置。"
+
+# b547fd51c7ac43f6896f5326d0bc8ba8
+#: ../../networking2.rst:2641
+msgid "Disabling and Enabling an AutoScale Configuration"
+msgstr "禁止和启用自动扩展配置"
+
+# 38e5928d47d14bc19e1fab9539b611a0
+#: ../../networking2.rst:2643
+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 "如果你想对一个自动扩展VM实例执行任何维护操作，请禁用自动扩展配置。当自动扩展配置被禁用，扩展和缩减动作不会执行。你可以利用停机时间进行维护活动。要禁用自动扩展配置，点击禁用自动扩展按钮 |EnableDisable.png|。"
+
+# 9e667521e0ed422c97c64cd3cd3a8b27
+#: ../../networking2.rst:2649
+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 "这个按钮是启用和禁止的切换开关，取决于当前是否启用了自动扩展。在执行完维护操作以后，你可以启用回自动扩展配置。要启用，请再次打开自动扩展配置页面，然后点击启用自动扩展按钮|EnableDisable.png|。"
+
+# 8c265f29a2494792991abbb3daed1b9e
+#: ../../networking2.rst:2658
+msgid "Updating an AutoScale Configuration"
+msgstr "更新自动扩展配置"
+
+# 280deb0a83064852b5f2ddd3b80809a6
+#: ../../networking2.rst:2660
+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 "你可以更新各种参数和添加或者删除扩展或缩减策略中的条件。在你更新自动扩展配置之前，请确保你已经通过点击禁止自动扩展按钮禁止了自动扩展负载均衡策略。"
+
+# e7070f9e778042a7aa68aeb88bde2257
+#: ../../networking2.rst:2665
+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 "在你修改了所需的自动扩展参数之后，点击应用。要应新的自动扩展策略，再次打开自动扩展配置页面，然后点击启用自动扩展按钮。"
+
+# e92451dccecb4a40a0c35bcc6e42105a
+#: ../../networking2.rst:2670
+msgid "Runtime Considerations"
+msgstr "运行时注意事项"
+
+# 5a7ed98221fc42848a83b71bcc5439f8
+#: ../../networking2.rst:2674
+msgid ""
+"An administrator should not assign a VM to a load balancing rule which is "
+"configured for AutoScale."
+msgstr "管理员不应该分配VM到配置为AutoScale的负载均衡规则中。"
+
+# 3afe9927a67b460a9e6faea30ba427fb
+#: ../../networking2.rst:2679
+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 "在分配虚拟机到一个负载均衡的规则配置完成前如果NetScaler被关闭或重启，则配置的虚拟机不能成为负载均衡规则的一部分。要解决此问题，重命名基于AutoScale配置的虚拟机名称或ID，以便在任何时间点负载平衡规则可以调节该虚拟机。"
+
+# eee56e4a2e474a04988980cace231253
+#: ../../networking2.rst:2688
+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 "在自动扩展上下文之外使用API调用，如destroyVM，那么自动扩展下的VM会处于负载均衡配置冲突状态中。虽然VM被负载均衡策略所销毁，但NetScaler仍然会把VM作为一个设备分配一条策略。"
+
+# 6da746ba5a56414f91ec2e2db3f82484
+#: ../../networking2.rst:2695
+msgid "Global Server Load Balancing Support"
+msgstr "全局服务器负载均衡 支持"
+
+# 81e233e5a8774fe7912bb9d777b02098
+#: ../../networking2.rst:2697
+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 "CLOUDSTACK支持全局服务器负载均衡 (GSLB) 功能以提供可持续的商业运营。GSLB可以在CLOUDSTACK环境中实现资源的无缝迁移。CLOUDSTACK通过集成NetScaler应用交付控制器 (ADC)来提供GSLB功能，ADC可以提供各种各样的GSLB能力，比如灾难恢复，负载均衡。CLOUDSTACK在实现GSLB功能进，使用了DNS重定向技术。"
+
+# 182ac54151764429a54597e47be09455
+#: ../../networking2.rst:2705
+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 "为了支持这个功能，引进了地域级别的服务和服务提供者。引进了一项新服务“GSLB”作为地域级别的服务。该GSLB服务提供者介绍将提供GSLB服务。目前，CloudStack中NetScaler可作为GSLB提供者。 GSLB功能工作在Active-Active数据中心环境。"
+
+# 8250959d1c994c618634ca275a2acf89
+#: ../../networking2.rst:2713
+msgid "About Global Server Load Balancing"
+msgstr "关于全局服务器负载均衡"
+
+# 23d6ad0ee7e345bd8b6e5a4ff72f0bde
+#: ../../networking2.rst:2715
+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 accessing a resource in the event of a "
+"failure, or to provide a means of shifting traffic easily to simplify "
+"maintenance, or both."
+msgstr "全局服务器负载均衡(GSLB)是负载均衡功能的扩展，为了高效的避免停机时间。基于部署的性质，GSLB代表一组技术的集合，用于各种用途，如负载均衡，灾难恢复，性能，和法定义务。使用GSLB，工作负载可以分布在位于不同地理位置的多个数据中心。 GSLB也可以用于在发生故障时访问资源的另一个备用位置，或对流量提供了简易的维护方式，或两者兼得。"
+
+# 9df73711bf05422aa3ff011e97b010d0
+#: ../../networking2.rst:2726
+msgid "Components of GSLB"
+msgstr "GSLB服务组件"
+
+# 0dbce0ca6baa46aeaad670109fbc187b
+#: ../../networking2.rst:2728
+msgid "A typical GSLB environment is comprised of the following components:"
+msgstr "一个典型的GSLB环境由以下服务组件组成："
+
+# be687e83d654431899ed881ba56746a0
+#: ../../networking2.rst:2732
+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 "**GSLB站点**：在CloudStack专业术语中，GSLB站点表现为映射至数据中心的zones，每个GSLB有多个网络设备。每个GSLB站点由一个位于站点中的NetScaler设备管理。每个NetScaler设备将他管理的站点视为本地站点，并且由其他NetScaler设备管理的站点视为远程站点。在GSLB部署中它是一个中央实体，具体表现为一个名称和一个IP地址。"
+
+# 1a724093f2854945a12f90a9aac0cdf7
+#: ../../networking2.rst:2742
+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 "**GSLB服务**：GSLB服务表现为典型的负载均衡或者内容交换虚拟服务器。在一个GSLB环境中，你可以有本地及远程GSLB服务。本地GSLB服务表现为一个本地负载均衡或者内容交换虚拟服务器。远程GSLB服务是配置在GSLB设置中的其他站点。在每个站点中的GSLB设置里，你可以创建一个本地GSLB服务和任意数量的远程GSLB服务。"
+
+# 5fa2919887bc460f94bbe24c89b9d442
+#: ../../networking2.rst:2753
+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 a FQDN DNS name."
+msgstr "**GSLB虚拟服务器**：GSLB虚拟服务器指的是一个或多个GSLB服务和平衡跨越多个使用CloudStack功能的zones之间VMs的流量。它通过评估配置的GSLB方法或者算法来选择一个GSLB服务发送客户端请求。来自不同zone的一个或多个虚拟服务器被绑定到GSLB虚拟服务器上。GSLB虚拟服务器没有对应的公共IP，只有一个FQDN DNS名称。"
+
+# 20cb61cdbd444e9a9f11f683a1ee4b35
+#: ../../networking2.rst:2764
+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 balancing or content switching virtual "
+"server, the client sends the request to that virtual server's VIP address."
+msgstr "**负载均衡或内容交换虚拟服务器**：依照Citrix NetScaler的专业术语，一个负载均衡或者内容交换虚拟服务器表现为本地网络上的一个或多个服务器。客户端发送他们的请求至负载均衡或内容交换虚拟服务器IP(VIP)地址，并且由虚拟服务器平衡本地服务器之间的负载。在GSLB虚拟服务器选择了一个基于本地或者远程负载均衡或者内容交换虚拟服务器的GSLB服务之后，客户端发送请求至虚拟服务器的VIP地址。"
+
+# a5ecee28e9bb433a8951bf3350e6aa91
+#: ../../networking2.rst:2776
+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 "**DNS VIPs**：DNS虚拟IP是一个在GSLB服务供应者上的DNS负载均衡虚拟服务器。在有GSLB服务提供者的域中的DNS请求会被发送至一个DNS VIP。"
+
+# 4eb2a120e2de43caad10fb89f83d8158
+#: ../../networking2.rst:2783
+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 and port."
+msgstr "**权威DNS**：ADNS(权威域名称服务器)是一个为DNS请求提供真实响应的服务，比如web站点IP地址。在GSLB环境中，一个ADNS服务只响应权威的GSLB服务提供者所在域的DNS请求。当配置了一个ADNS服务，该服务的提供者即拥有该服务IP并且广播它。当你创建一个ADNS服务的时候，NetScaler通过配置的ADNS服务IP和端口响应DNS请求。"
+
+# cd935874099944bd8bd07f110b11f0c3
+#: ../../networking2.rst:2793
+msgid "How Does GSLB Works in CloudStack?"
+msgstr "在CloudStack中，GSLB的工作原理是什么？"
+
+# a07db76162554695b05812b43a222375
+#: ../../networking2.rst:2795
+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 xyztelco cloud. For that purpose, they "
+"launch two instances each in both the zones: VM1 and VM2 in Zone-1 and VM5 "
+"and VM6 in Zone-2. Tenant-A acquires a public IP, IP-1 in Zone-1, and "
+"configures a load balancer rule to load balance the traffic between VM1 and "
+"VM2 instances. CloudStack orchestrates setting up a virtual server on the LB"
+" service provider in Zone-1. Virtual server 1 that is set up on the LB "
+"service provider in Zone-1 represents a publicly accessible virtual server "
+"that client reaches at IP-1. The client traffic to virtual server 1 at IP-1 "
+"will be load balanced across VM1 and VM2 instances."
+msgstr "全局服务器负载均衡-GSLB-用于在不同地域的不同独立区域之间管理WEB服务器的访问流量。以下是CLOUDSTACK中提供的GSLB功能图示：EXZTELCO这个组织用CLOUDSTACK在不同的数据中心部署一个公有云，此云环境包括两个区域，Zone-1 和Zone-2。XYZTELCO里有租户A需要部署一个高可用方案。为了达到此目标，他们分别在两个区域里部署了两个虚拟机实例：Zone-1中有VM1和VM2，Zone-2中有VM5和VM6。租户A在Zone-1中得到一个公网IP-IP-1，并且在VM1和VM2之间配置了负载均衡规则。CLOUDSTACK 编排系统在 Zone-1中LB服务上设置了一个虚拟服务器-Virtual server 1 。客户端对-IP-1的访问会到达Virtual server 1，此虚拟服务器再将流量转发到VM1和VM2上进行流量负载均衡。"
+
+# 7522dda4534f412e9114fbef583cdbc4
+#: ../../networking2.rst:2812
+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 instances. At this point Tenant-A "
+"has the service enabled in both the zones, but has no means to set up a "
+"disaster recovery plan if one of the zone fails. Additionally, there is no "
+"way for Tenant-A to load balance the traffic intelligently to one of the "
+"zones based on load, proximity and so on. The cloud administrator of "
+"xyztelco provisions a GSLB service provider to both the zones. A GSLB "
+"provider is typically an ADC that has the ability to act as an ADNS "
+"(Authoritative Domain Name Server) and has the mechanism to monitor health "
+"of virtual servers both at local and remote sites. The cloud admin enables "
+"GSLB as a service to the tenants that use zones 1 and 2."
+msgstr "租户A在Zone-2中得到一个公网IP-IP-2，并且在VM5和VM6之间配置了负载均衡规则。CLOUDSTACK 编排系统在 Zone-2中LB服务上设置了一个虚拟服务器-Virtual server 2 。客户端对-IP-2的访问会到达Virtual server 2，此虚拟服务器再将流量转发到VM5和VM6上进行流量负载均衡。此时，租户A在两个区域里都启用了服务，但是，无法在这种环境下部署灾难恢复计划，也无法更智能在区域内使用负载均衡。要解决这些问题，XYZTELCO云管理员可以在两个区域内启用GSLB服务，一个GSLB服务通常是一个具有ADNS(认证域名服务器)能力的ADC，并且具有监测本地和远程站点健康状况的手段。云管理员可以在ZONE 1和2中为租户启用GSLB服务。"
+
+# 89319188219b404eb12377733494db5a
+#: ../../networking2.rst:2830
+msgid "|gslb.png|"
+msgstr "|gslb.png|"
+
+# b984591edede4102820e3e91af964094
+#: ../../networking2.rst:2832
+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 start monitoring the health of "
+"virtual server 1 and 2 in Zone-1. CloudStack will also orchestrate setting "
+"up GSLB virtual server 2 on GSLB service provider at Zone-2. CloudStack will"
+" bind virtual server 1 of Zone-1 and virtual server 2 of Zone-2 to GLSB "
+"virtual server 2. GSLB virtual server 2 is configured to start monitoring "
+"the health of virtual server 1 and 2. CloudStack will bind the domain "
+"A.xyztelco.com to both the GSLB virtual server 1 and 2. At this point, "
+"Tenant-A service will be globally reachable at A.xyztelco.com. The private "
+"DNS server for the domain xyztelcom.com is configured by the admin out-of-"
+"band to resolve the domain A.xyztelco.com to the GSLB providers at both the "
+"zones, which are configured as ADNS for the domain A.xyztelco.com. A client "
+"when sends a DNS request to resolve A.xyztelcom.com, will eventually get DNS"
+" delegation to the address of GSLB providers at zone 1 and 2. A client DNS "
+"request will be received by the GSLB provider. The GSLB provider, depending "
+"on the domain for which it needs to resolve, will pick up the GSLB virtual "
+"server associated with the domain. Depending on the health of the virtual "
+"servers being load balanced, DNS request for the domain will be resolved to "
+"the public IP associated with the selected virtual server."
+msgstr "租户- A希望利用由xyztelco cloud提供的GSLB服务。租户-A配置了一个GSLB规则对Zone-1中的虚拟服务器1和Zone-2中的虚拟服务器2提供流量负载均衡。假设域名是A.xyztelco.com 。CloudStack中协调设置GSLB服务提供者Zone-1中的GSLB虚拟服务器1。 CloudStack绑定Zone-1中的虚拟服务器1和Zone-2中的虚拟服务器2到GSLB虚拟服务器1。CloudStack也将协调设置GSLB服务提供者Zone-2中的GSLB虚拟服务器2.CloudStack绑定Zone-1中的虚拟服务器1和Zone-2中的虚拟服务器2到GSLB虚拟服务器2.GSLB虚拟服务器2配置为开始监视虚拟服务器1和2的健康。CloudStack中会绑定域名A.xyztelco.com到GSLB虚拟服务器1和2。在这一点上，租户-A的服务将在全球范围内可达于A.xyztelco.com。域名xyztelcom.com的专用DNS服务器，被管理员配置为外带管理，由两个区域的GSLB提供者对域名A.xyztelco.com提供解析。它将被配置为域名A.xyztelco.com的ADNS。当客户端请求解析A.xyztelcom.com域名时，将最终由DNS指派到GSLB提供者Zone 1 和Zone2。客户DNS请求将被GSLB提供者接获。GSLB提供者，根据需要解析的域名，将获得与域名关联的GSLB虚拟服务器。根据用于负载均衡的虚拟服务器的运行健康状况，域名DNS请求将被解析到所选择关联的虚拟服务器中。"
+
+# 8456ab01fb394c3383eeb5029e812dc5
+#: ../../networking2.rst:2860
+msgid "Configuring GSLB"
+msgstr "配置GSLB"
+
+# a2ddfa5eb5c04d4b8969f09f92f69456
+#: ../../networking2.rst:2862
+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 servers. Finally, bind the domain to "
+"the GSLB virtual servers. The GSLB configurations on the two appliances at "
+"the two different zones are identical, although each sites load-balancing "
+"configuration is specific to that site."
+msgstr "要配置GSLB的部署，您必须首先为每个区域配置一个标准的负载平衡设置。这使您能够在该地域中每个区域的不同服务器之间进行负载均衡。然后在NetScaler方面，配置您计划添加到每个区域作为权威DNS(ADNS)服务器的两个NetScaler应用。接下来，为每个区域创建GSLB站点、配置GSLB虚拟服务器、创建GSLB服务并绑定GSLB服务到GSLB虚拟服务器中。最后，绑定该域到GSLB虚拟服务器。两个应用的GSLB配置在两个不同区域中是完全相同的，尽管每个网站的负载均衡配置特定于该网站。"
+
+# 6d13a7e3c72d4d0fbbf094a3a0048b5e
+#: ../../networking2.rst:2874
+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 "作为云管理员执行以下操作。按照上面给出的例子中，由管理员xyztelco设置GSLB："
+
+# 1b13dfc3a4704d5a8fa68973611763ec
+#: ../../networking2.rst:2879
+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 "在全局变量 cloud.dns.name中，为您租户云定义DNS名称并供GSLB服务使用。"
+
+# 24fa8e0bc85a4858bb09168558689b88
+#: ../../networking2.rst:2884
+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 "在NetScaler方面，给出GSLB配置 `配置全局服务器负载均衡 (GSLB)<http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-con.html>`_:"
+
+# 4527dca57f1440febc672d19e072283e
+#: ../../networking2.rst:2890
+msgid "Configuring a standard load balancing setup."
+msgstr "配置一个标准的负载均衡设置。"
+
+# 0c91751454f842ed867ba1142e0082af
+#: ../../networking2.rst:2894
+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 "配置权威DNS，如下解释 `配置权威的DNS服务 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-adns-svc-tsk.html>`__."
+
+# 81d14d2da5084c1491a9261135038ca2
+#: ../../networking2.rst:2900
+msgid ""
+"Configure a GSLB site with site name formed from the domain name details."
+msgstr "由域名详细信息配置一个GSLB站点和站点名称。"
+
+# b8bd9fe16daa4ddab41339b4016d8128
+#: ../../networking2.rst:2903
+msgid "Configure a GSLB site with the site name formed from the domain name."
+msgstr "由域名配置一个GSLB站点和站点名称。"
+
+# ec8346bdb6fb4e9b85623f3b7fedc33b
+#: ../../networking2.rst:2906
+msgid ""
+"As per the example given above, the site names are A.xyztelco.com and "
+"B.xyztelco.com."
+msgstr "按照上面给出的例子，站点名称为 A.xyztelco.com 和 B.xyztelco.com"
+
+# 7e764b73be594f529ea85676104ba0d9
+#: ../../networking2.rst:2909
+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 "更多信息，请参阅 `配置基本的GSLB站点 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-basic-site-tsk.html>`__."
+
+# e8b2b78d2bcc4ead899d033a82688d6a
+#: ../../networking2.rst:2914
+msgid "Configure a GSLB virtual server."
+msgstr "配置GSLB虚拟服务器。"
+
+# a658718fb49e4176814d60e01d81a6c3
+#: ../../networking2.rst:2916
+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 "更多信息，请参阅 `配置GSLB虚拟服务器 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-vsvr-tsk.html>`__."
+
+# 5bc91629e58046eabfa170a8ff9228cd
+#: ../../networking2.rst:2921
+msgid "Configure a GSLB service for each virtual server."
+msgstr "为每个虚拟服务器配置GSLB服务。"
+
+# ad990e26ce2c411081c88e66a273cb2c
+#: ../../networking2.rst:2923
+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 "更多信息，请参阅 `配置GSLB服务 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-svc-tsk.html>`__."
+
+# c239f4ef8dcf4da58541d9bb39333eb2
+#: ../../networking2.rst:2928
+msgid "Bind the GSLB services to the GSLB virtual server."
+msgstr "绑定GSLB服务到GSLB虚拟服务器。"
+
+# 1e702a12b98043e2bacf01a137ee482e
+#: ../../networking2.rst:2930
+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 "更多信息，请参阅 `绑定GSLB服务到GSLB虚拟服务器 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-bind-svc-vsvr-tsk.html>`__."
+
+# 10e534b7d92e4b40ad06805f6092f802
+#: ../../networking2.rst:2935
+msgid ""
+"Bind domain name to GSLB virtual server. Domain name is obtained from the "
+"domain details."
+msgstr "绑定GSLB域名到GSLB虚拟服务器。从域的详细信息中获得域名。"
+
+# 604d20e5aff64a2e9c6634fcbc5268e5
+#: ../../networking2.rst:2938
+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 "更多信息，请参阅 `绑定GSLB域名到GSLB虚拟服务器 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-bind-dom-vsvr-tsk.html>`__."
+
+# 0ac7add23ac4439ca08fc7caba76441e
+#: ../../networking2.rst:2943
+msgid ""
+"In each zone that are participating in GSLB, add GSLB-enabled NetScaler "
+"device."
+msgstr "在每个参与GSLB的区域内，添加启用GSLB功能的NetScaler设备。"
+
+# 5d9a5dd2235f42579a6118838bb636fa
+#: ../../networking2.rst:2946
+msgid "For more information, see :ref:`enabling-gslb-in-ns`."
+msgstr "更多信息请参考 :ref:`enabling-gslb-in-ns`."
+
+# ff5093bc021b4c379b8656f628935267
+#: ../../networking2.rst:2948
+msgid "As a domain administrator/ user perform the following:"
+msgstr "以域管理员/用户执行以下操作："
+
+# 1ef3c0fd004d43e69534e4a5de7f38d8
+#: ../../networking2.rst:2952
+msgid "Add a GSLB rule on both the sites."
+msgstr "在两个站点中添加GSLB规则。"
+
+# 5779d01501a3442eadc72060d6a298e3
+#: ../../networking2.rst:2954
+msgid "See \":ref:`adding-gslb-rule`\"."
+msgstr "参考\":ref:`adding-gslb-rule`\"."
+
+# cbd719c880074f4d8e40125c6a766be2
+#: ../../networking2.rst:2958
+msgid "Assign load balancer rules."
+msgstr "分配负载均衡规则。"
+
+# c9a1fb87306b486dad29aa18bd3d8819
+#: ../../networking2.rst:2960
+msgid "See \":ref:`assigning-lb-rule-gslb`\"."
+msgstr "参考\":ref:`assigning-lb-rule-gslb`\"."
+
+# a1b0865343b54113bc0065aa808ec8cb
+#: ../../networking2.rst:2967
+msgid "The GSLB functionality is supported both Basic and Advanced zones."
+msgstr "GSLB功能支持基本和高级区域。"
+
+# da30d8fa37d94effb410d14171ff906b
+#: ../../networking2.rst:2971
+msgid "GSLB is added as a new network service."
+msgstr "GSLB是新添加的网络服务。"
+
+# 13eb68d1468e4d7c99753052f9b72a15
+#: ../../networking2.rst:2975
+msgid "GSLB service provider can be added to a physical network in a zone."
+msgstr "GSLB服务提供者可以被添加至区域中的物理网络。"
+
+# 6384b810c9a4410c9ae8f67816e13cd9
+#: ../../networking2.rst:2979
+msgid ""
+"The admin is allowed to enable or disable GSLB functionality at region "
+"level."
+msgstr "管理员允许开启或禁用地域级别的GSLB功能。"
+
+# dbd35e047b8d4eb89dde586187f3d0eb
+#: ../../networking2.rst:2984
+msgid "The admin is allowed to configure a zone as GSLB capable or enabled."
+msgstr "管理员具有启用或配置区域为GSLB的能力"
+
+# 58bd5b2c58a9407692791abdff3e6e54
+#: ../../networking2.rst:2986
+msgid ""
+"A zone shall be considered as GSLB capable only if a GSLB service provider "
+"is provisioned in the zone."
+msgstr "只有在GSLB服务提供者提供的区域中，该区域才被视为有GSLB能力。"
+
+# efc18977b5ac4e84a963305554993e11
+#: ../../networking2.rst:2991
+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 "当用户的VMs部署在启用GSLB功能的多个可用区域中时，他们可以使用GSLB功能在多个区域中将VM的流量进行负载均衡。"
+
+# e793a1e1efc84729991ede4558891921
+#: ../../networking2.rst:2997
+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 "如果管理员在地域中启用了GSLB，用户可以使用GSLB对地狱中的所有区域的VMs进行负载均衡。"
+
+# 4c4a8f9e84ea44b19390f5fd020277fb
+#: ../../networking2.rst:3002
+msgid ""
+"The users can load balance traffic across the availability zones in the same"
+" region or different regions."
+msgstr "用户可以为同一个区域或不同地域间可用的区域流量进行负载均衡。"
+
+# 4a914f83d04549c29de6013290e3e7f4
+#: ../../networking2.rst:3007
+msgid "The admin can configure DNS name for the entire cloud."
+msgstr "管理员可以为整个云配置DNS名称。"
+
+# 596f9eade21844dfa16d3d964f7ce03d
+#: ../../networking2.rst:3011
+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 "用户可以为云中的全局负载均衡服务指定一个唯一的名称。所提供名称的域名相当于云的DNS名称。"
+
+# 6547e809a9f240ed88dd1d5c4a9d325d
+#: ../../networking2.rst:3015
+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 "用户提供的名称与管理员提供的DNS名称一起为用户的全局负载均衡服务产生一个全局解析的FQDN。例如，如果管理员已经配置xyztelco.com为云中的DNS名称，以及用户为GSLB虚拟服务器指定的名称为'foo'，那么GSLB虚拟服务器的FQDN名称是foo.xyztelco.com。"
+
+# 954c733062ed4faaae39782c315285fc
+#: ../../networking2.rst:3024
+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 "设置GSLB时，用户可以为GSLB跨区域的一部分选择负载均衡方式，例如 round robin。"
+
+# b7249d54a14f4c3e9ab5f0ef17a864dd
+#: ../../networking2.rst:3029
+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 "用户应能设置区域级虚拟服务器的权重。负载均衡在分配流量时会考虑该权重。"
+
+# d0d2828b22794506bce6cc04c652759f
+#: ../../networking2.rst:3035
+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 "该GSLB功能必须支持会话持久性，特定域名的一系列客户端请求被发送到同一个区域中的虚拟服务器上。"
+
+# fe2366a38bbf4359aa47d04dbbe9ef53
+#: ../../networking2.rst:3039
+msgid "Statistics is collected from each GSLB virtual server."
+msgstr "从每个GSLB虚拟服务器中收集统计数据。"
+
+# 310bede319094d1a81dd13ae031d171e
+#: ../../networking2.rst:3044
+msgid "Enabling GSLB in NetScaler"
+msgstr "开启NetScaler的GSLB"
+
+# 6cf5dc558b0541b38ee30e8b09f0a119
+#: ../../networking2.rst:3046
+msgid "In each zone, add GSLB-enabled NetScaler device for load balancing."
+msgstr "在每个区域中，添加启用GSLB的NetScaler设备提供负载均衡。"
+
+# db33d472d3bd4ea6aefc696bbb848e61
+#: ../../networking2.rst:3050
+msgid "Log in as administrator to the CloudStack UI."
+msgstr "使用管理员登录到CloudStack管理界面。"
+
+# 71afbe01841a4e11a0fcc15b17786d36
+#: ../../networking2.rst:3058
+msgid "In Zones, click View More."
+msgstr "点击区域中的查看更多。"
+
+# e790f063f0054d8fa2f47e81ff50ca59
+#: ../../networking2.rst:3066
+msgid ""
+"Click the Physical Network tab, then click the name of the physical network."
+msgstr "点击物理网络选项卡，然后点击物理网络的名称。"
+
+# 9e1c9696e24a415ca0080414be0196e6
+#: ../../networking2.rst:3071
+msgid "In the Network Service Providers node of the diagram, click Configure."
+msgstr "点击示意图'网络服务提供程序'中的配置"
+
+# 536e22d770c44b319d5ee4d2ae4b2153
+#: ../../networking2.rst:3074
+msgid "You might have to scroll down to see this."
+msgstr "你可能需要向下滚动才能看到。"
+
+# 21cd237381d44ee58898516d998a4372
+#: ../../networking2.rst:3078
+msgid "Click NetScaler."
+msgstr "点击NetScaler."
+
+# 5bca2c9d180b435bb43c10f72d8b4f50
+#: ../../networking2.rst:3082
+msgid "Click Add NetScaler device and provide the following:"
+msgstr "点击添加NetScaler设备并提供如下信息："
+
+# c101c1fb776f45a3b10751c976f19dff
+#: ../../networking2.rst:3084
+msgid "For NetScaler:"
+msgstr "对于NetScaler:"
+
+# 2ba731212f4e4d97bf33b98b02462f31
+#: ../../networking2.rst:3088
+msgid "**IP Address**: The IP address of the SDX."
+msgstr "**IP地址**: SDX的IP地址。"
+
+# f6756edb0b2749a28f89727cedd914de
+#: ../../networking2.rst:3092
+msgid ""
+"**Username/Password**: The authentication credentials to access the device. "
+"CloudStack uses these credentials to access the device."
+msgstr "**用户名/密码.** 访问此设备的认证许可。CloudStack使用这些认证信息访问此设备。"
+
+# c289535d0983447bb28313242c1afcfd
+#: ../../networking2.rst:3098
+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 "**类型**：添加设备的类型。可以是F5 BigIP负载均衡器、NetScaler VPX、NetScaler MPX或 NetScaler SDX等设备。关于NetScaler的类型比较，请参阅CloudStack管理指南。"
+
+# fcf8d7c54d854ef6ac2504c8b710bdea
+#: ../../networking2.rst:3105
+msgid ""
+"**Public interface**: Interface of device that is configured to be part of "
+"the public network."
+msgstr "**公共接口**: 配置为公共网络部分的设备接口。"
+
+# 770c0db7ca88466d9f7a6723075a9f24
+#: ../../networking2.rst:3110
+msgid ""
+"**Private interface**: Interface of device that is configured to be part of "
+"the private network."
+msgstr "**专用接口**: 配置为专用网络部分的设备接口。"
+
+# ea63258ee8704f1d9b63279f814a6194
+#: ../../networking2.rst:3115
+msgid "**GSLB service**: Select this option."
+msgstr "**GSLB 服务**:选择该选项。"
+
+# 8b775a110efc48adafc54539a743a373
+#: ../../networking2.rst:3119
+msgid ""
+"**GSLB service Public IP**: The public IP address of the NAT translator for "
+"a GSLB service that is on a private network."
+msgstr "**GSLB 服务公共IP**:在专用网络中，为GSLB服务提供NAT转换的公共IP地址。"
+
+# 721d09d62d574127acbc4eedf582a400
+#: ../../networking2.rst:3124
+msgid "**GSLB service Private IP**: The private IP of the GSLB service."
+msgstr "**GSLB 服务专用IP**: GSLB服务的专用IP地址。"
+
+# 58903b1562ff43d3ac2842018f153a1f
+#: ../../networking2.rst:3128
+msgid ""
+"**Number of Retries**. Number of times to attempt a command on the device "
+"before considering the operation failed. Default is 2."
+msgstr "**重试次数** 尝试控制设备失败时重试的次数，默认为2次。"
+
+# 8453399635794a5dafd95e6644881b34
+#: ../../networking2.rst:3133
+msgid "**Capacity**: The number of networks the device can handle."
+msgstr "**容量**：该设备能处理的网络数量。"
+
+# 032a009f433441a7a9ea141a1a37190f
+#: ../../networking2.rst:3137
+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 "**专用**: 当标记为专用后，这个设备只对单个帐号专用。该选项被勾选后，容量选项就没有了实际意义且值会被置为1。"
+
+# 9c1c5bdbb7b04a5081ee5ee1be823231
+#: ../../networking2.rst:3149
+msgid "Adding a GSLB Rule"
+msgstr "添加 GSLB规则"
+
+# 9886f1b9081c4b2b9f94068c36234301
+# c0bb3b92c34f4bc79ff38db4f1867976
+#: ../../networking2.rst:3153 ../../networking2.rst:3224
+msgid "Log in to the CloudStack UI as a domain administrator or user."
+msgstr "使用管理员或者用户账号登录CloudStack UI。"
+
+# cf94d6818dfd454bb24a0197b45b1c89
+# 1631e25bb98e44a68e0491ede5dc221d
+#: ../../networking2.rst:3157 ../../networking2.rst:3228
+msgid "In the left navigation pane, click Region."
+msgstr "在左边的导航栏里，点击区域（为文档翻译中地域的概念，英文为region，下同）"
+
+# 99089f1571d2400ba327b8e2e914141f
+# d38f849a92654b41b37919edf2efdf78
+#: ../../networking2.rst:3161 ../../networking2.rst:3232
+msgid "Select the region for which you want to create a GSLB rule."
+msgstr "选择你想创建GSLB规则的地域。"
+
+# 17cf4f5a1948405ab27b253588ef1352
+# 98821ced62fd453b90d3870422da2536
+#: ../../networking2.rst:3165 ../../networking2.rst:3236
+msgid "In the Details tab, click View GSLB."
+msgstr "在详细选项卡中，点击查看GSLB。"
+
+# 6a85608ee29b4baca127e393abe5ad11
+#: ../../networking2.rst:3169
+msgid "Click Add GSLB."
+msgstr "点击添加GSLB。"
+
+# 0ae5d0eae58a463db228c0ee3c3f2d0e
+#: ../../networking2.rst:3171
+msgid "The Add GSLB page is displayed as follows:"
+msgstr "添加GSLB页面显示如下："
+
+# b9b04ceabaa9463d85a4faf511f47d57
+#: ../../networking2.rst:3173
+msgid "|gslb-add.png|"
+msgstr "|gslb-add.png|"
+
+# 3cc1ebf185774545998478f479bffa85
+#: ../../networking2.rst:3181
+msgid "**Name**: Name for the GSLB rule."
+msgstr "**名称**: GSLB规则的名称。"
+
+# c0e402372e814565bdeff0182a1d1779
+#: ../../networking2.rst:3185
+msgid ""
+"**Description**: (Optional) A short description of the GSLB rule that can be"
+" displayed to users."
+msgstr "**描述**: (可选)为用户提供一个简短的GSLB规则描述。 "
+
+# 727d582900354d2bb9e4a0301b19cc35
+#: ../../networking2.rst:3190
+msgid "**GSLB Domain Name**: A preferred domain name for the service."
+msgstr "**GSLB 域名**: 首选的域名服务。"
+
+# ef12427c38c94561abed938f4a2bbd8c
+#: ../../networking2.rst:3194
+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 "**算法**: (可选) 用于跨区域流量负载均衡的算法。可选项为 Round Robin, Least Connection, 和Proximity."
+
+# 241c813551f64e92b78dfd290df99cfe
+#: ../../networking2.rst:3200
+msgid ""
+"**Service Type**: The transport protocol to use for GSLB. The options are "
+"TCP and UDP."
+msgstr "**服务类型**: GSLB使用的传输协议。可选项为TCP和UDP。"
+
+# aa4bcbd25cf647e1ab4384586b654409
+#: ../../networking2.rst:3205
+msgid ""
+"**Domain**: (Optional) The domain for which you want to create the GSLB "
+"rule."
+msgstr "**域**: (可选) 你想要创建GSLB规则的域。"
+
+# 839afecaeeed4cbbb6ef0bb21bf498f3
+#: ../../networking2.rst:3210
+msgid ""
+"**Account**: (Optional) The account on which you want to apply the GSLB "
+"rule."
+msgstr "**账户**: (可选) 应用GSLB规则的账户。"
+
+# 2ab62b2492a3407ca085e8666b106fa4
+#: ../../networking2.rst:3220
+msgid "Assigning Load Balancing Rules to GSLB"
+msgstr "为GSLB分配负载均衡规则"
+
+# 7c5601cd6ce640e8b5dc8a45589bad59
+#: ../../networking2.rst:3240
+msgid "Select the desired GSLB."
+msgstr "选择所需的GSLB。"
+
+# cf5bad08cdb4408c83d7b139e0c64547
+#: ../../networking2.rst:3244
+msgid "Click view assigned load balancing."
+msgstr "点击已分配的负载均衡视图。"
+
+# e8ee6a81561b4140a5fc1b69a76cc736
+#: ../../networking2.rst:3248
+msgid "Click assign more load balancing."
+msgstr "点击分配更多负载平衡"
+
+# 645c7738ea8643bb8dc363416867e170
+#: ../../networking2.rst:3252
+msgid "Select the load balancing rule you have created for the zone."
+msgstr "选择你将为区域创建的负载均衡规则。"
+
+# 607875c969314174b33d5ffe591d6d01
+#: ../../networking2.rst:3259
+msgid "Known Limitation"
+msgstr "已知的局限性"
+
+# 7b4f744d0ba14d0793259da18acaa8e4
+#: ../../networking2.rst:3261
+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 "目前，CloudStack并不支持跨区域的服务编排。将引入服务的概念和地域服务提供者。"
+
+# 07d2c270666b4ce5b27e2329f4a46336
+#: ../../networking2.rst:3266
+msgid "Guest IP Ranges"
+msgstr "来宾IP范围"
+
+# 5ba35a4bec1d4cd086d34463a8fd3b26
+#: ../../networking2.rst:3268
+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 "宾客网络流量的IP是由用户以帐号为基础设置的。这允许用户以在他们的宾客网络和他们的客户端之间开通VPN连接的方式配置他们的网络。"
+
+# 24793eb079054dad8ef15f9ce2ce53ad
+#: ../../networking2.rst:3273
+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 "存在基本网络和启用安全组的高级网络中的共享网络，你可以灵活的在不同子网中添加多个来宾IP范围。你可以同时添加或移除IP范围。更多信息，请参阅 `章节 15.10, “关于多IP范围”<#about-multiple-ip-ranges>`_."
+
+# 1a16911ddff840da827812b45ff09025
+#: ../../networking2.rst:3280
+msgid "Acquiring a New IP Address"
+msgstr "获得一个新的IP地址"
+
+# 2959313cb3534153848362cb02ce12c0
+#: ../../networking2.rst:3308
+msgid ""
+"If you want Portable IP click Yes in the confirmation dialog. If you want a "
+"normal Public IP click No."
+msgstr "如果你想作为 Portable IP则在确认窗口中点击Yes，如果你想作为正常的公共IP则点击No。"
+
+# 83e09cc7cc8940f6aa9b890d0011f628
+#: ../../networking2.rst:3311
+msgid ""
+"For more information on Portable IP, see `\"Portable IPs\" <#portable-"
+"ips>`_."
+msgstr "关于便携式IP的更多信息，查看 `\"便携式IP\" <#portable-ips>`_."
+
+# e238190f4d8f4177ac72494fa5eb1d72
+#: ../../networking2.rst:3319
+msgid "Releasing an IP Address"
+msgstr "释放IP地址"
+
+# 84c5bd1b7c19450b9c9a23243730fa62
+#: ../../networking2.rst:3321
+msgid ""
+"When the last rule for an IP address is removed, you can release that IP "
+"address. The IP address still belongs to the VPC; however, it can be picked "
+"up for any guest network again."
+msgstr "当IP的最后一条规则删除后，您就能够释放该IP。然而，该IP仍属于VPC，无论如何，该IP可以再次被VPC中的来宾网络再次获取。"
+
+# cf51c9fcec0b45fa99f4d7aeeb1b1c06
+#: ../../networking2.rst:3343
+msgid "Click the IP address you want to release."
+msgstr "点击要释放的IP地址。"
+
+# e09fbcc9c5114e19a679764fe1714c1a
+#: ../../networking2.rst:3347
+msgid "Click the Release IP button. |ReleaseIPButton.png|"
+msgstr "Click the Release IP button. |ReleaseIPButton.png|"
+
+# a1e27ff808d74a1ca5f49c2d72593b00
+# c329d8910228495faeb8d66b4e61c0b6
+# f699725aeceb41beb4bd661924beb0fe
+# b55b701c8a634f42a9019c46b5f7a204
+# 7c788a2a5d3640c99e8cc0ae99940251
+# 160c7d49caad47f7ae0c0b2f98aff672
+# 37a5880aa697458fb42243e1e26fc671
+# 8980bc62961847a7bb55dc12efac6df7
+# 1918561df94f4fa4bfa406d4ed4cd1a1
+# b5960db5e5104fafa693db42db76ba47
+# 9cd72aa996794ce4bd207159d1fa8742
+# abe42da7383441778d0131125e8ff6c8
+#: ../../networking2.rst:3351 ../../networking2.rst:3923
+#: ../../networking2.rst:4395 ../../networking2.rst:4495
+#: ../../networking2.rst:4687 ../../networking2.rst:5291
+#: ../../networking2.rst:5550 ../../networking2.rst:5876
+#: ../../networking2.rst:5963 ../../networking2.rst:6055
+#: ../../networking2.rst:6298 ../../networking2.rst:6692
+msgid "Static NAT"
+msgstr "静态 NAT"
+
+# b1f96220fd994b41b5fa5fdebccab0b4
+#: ../../networking2.rst:3353
+msgid ""
+"A static NAT rule maps a public IP address to the private IP address of a VM"
+" in order to allow Internet traffic into the VM. The public IP address "
+"always remains the same, which is why it is called “static†NAT. This "
+"section tells how to enable or disable static NAT for a particular IP "
+"address."
+msgstr "一条静态 NAT 规则映射一个公网 IP 地址到一台虚拟机的私网 IP 地址，目的是允许互联网的流量到该虚拟机。 公网 IP 地址总是保持为同一地址，这就是为什么被称为 \"静态\" NAT。 本节描述如何将一个特定的IP地址设为或取消静态NAT。"
+
+# d98473b1ef2041a7877e6841336bbe2f
+#: ../../networking2.rst:3360
+msgid "Enabling or Disabling Static NAT"
+msgstr "启用或禁用静态NAT"
+
+# 66e31a75defd4e2e88802eaa37a23902
+# 507d4788f25d423c84d95132346afd2b
+#: ../../networking2.rst:3362 ../../networking2.rst:6014
+msgid ""
+"If port forwarding rules are already in effect for an IP address, you cannot"
+" enable static NAT to that IP."
+msgstr "如果该公网IP上已经有端口转发规则，则不允许再启用静态NAT。"
+
+# 28d0504840374a70bd1ec4eab3c57295
+# dd68e0b051b34d709557d0f739c568ac
+#: ../../networking2.rst:3365 ../../networking2.rst:6017
+msgid ""
+"If a guest VM is part of more than one network, static NAT rules will "
+"function only if they are defined on the default network."
+msgstr "如果用户VM存在多个网络，则静态NAT规则仅在默认网络上定义时生效。"
+
+# 4f6ac41af4434f21b7bbb61428e5bd46
+# 6f85b85b1cd24dbeb7fffdbd01f0afa2
+#: ../../networking2.rst:3386 ../../networking2.rst:3460
+msgid "Click the IP address you want to work with."
+msgstr "点击你要修改的IP地址"
+
+# 326984a3cc3446ed806cf614b48f5841
+#: ../../networking2.rst:3390
+msgid "Click the Static NAT |enabledisablenat.png| button."
+msgstr "点击静态NAT按钮。 |enabledisablenat.png| "
+
+# a372a7da12b54432889a1a60bab4be8a
+#: ../../networking2.rst:3393
+msgid ""
+"The button toggles between Enable and Disable, depending on whether static "
+"NAT is currently enabled for the IP address."
+msgstr "该按钮在启用和禁用之间切换，这取决于IP地址是否已经启用了静态NAT。"
+
+# 78c5d4edd8db44cf9d448e10f2a89813
+#: ../../networking2.rst:3398
+msgid ""
+"If you are enabling static NAT, a dialog appears where you can choose the "
+"destination VM and click Apply."
+msgstr "如果是启用静态NAT，会出现一个对话框让您选择目标VM然后点击应用。"
+
+# 88e457a0ae3145f49ab4f361af8d4a4a
+#: ../../networking2.rst:3402
+msgid "IP Forwarding and Firewalling"
+msgstr "IP转发及防火墙"
+
+# 9abca0c542c1441f8b116871bcce046d
+#: ../../networking2.rst:3404
+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 "默认情况下, 所有从公共IP进来的流量都会被拒绝. 所有在来宾网络出去的流量默认也被阻挡。"
+
+# 1dd28301d9264826b4c64d6f13edf77f
+#: ../../networking2.rst:3407
+msgid ""
+"To allow outgoing traffic, follow the procedure in :ref:`egress-fw-rules`."
+msgstr "为了允许外出的流量，遵循:ref:`egress-fw-rules`中的操作步骤。"
+
+# 35f67e1320f941ac85f0fbb87f8fb385
+#: ../../networking2.rst:3409
+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 "为了允许接收到的流量, 用户可以设置一些防火墙规则和/或端口转发规则. 例如, 你可以在公共IP地址上设定防火墙规则来打开一个端口范围, 比如从33到44端口. 然后使用端口转发将流量从这个特定的范围内的端口直接送到指定的用户虚机端口. 例如, 一个端口转发的规则可以将接收的流量从公共IP的33端口到用户虚机私有IP的100端口."
+
+# 9229b4cb0661463cab6efc5582184abc
+#: ../../networking2.rst:3418
+msgid "Firewall Rules"
+msgstr "防火墙规则"
+
+# d51a292426874329a0951777c1772476
+#: ../../networking2.rst:3420
+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 "默认情况下，防火墙拒绝所有流入公共IP的流量。要允许外部流量，你需要制定防火墙规则打开防火墙端口。你可以选择性的制定一个或多个CIDR来过滤来源IP。这在当你只需要允许特定IP请求时会很有用。"
+
+# 59963a8e5da34833bc437796df5d300c
+#: ../../networking2.rst:3426
+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 "你不能使用防火墙规则打开弹性IP的端口。当弹性IP处在使用状态时，外部的通过请求将被安全组管理。参阅 `\"添加安全组\" <#adding-a-security-group>`_."
+
+# f9d2eb76396f4589896d0f4797e8c77b
+#: ../../networking2.rst:3431
+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 "在高级Zone中，您也可以用虚拟路由器来创建流出的防火墙规则。更多信息，请查阅\":ref:`egress-fw-rules`\"。"
+
+# ee967d9902434ce68b69c49226492070
+#: ../../networking2.rst:3434
+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 "防火墙规则能在管理服务器的UI中防火墙选项卡里创建，CloudStac安装好以后，这个规则选项卡默认不显示，你需要以管理员身份修改全局变量 firewall.rule.ui.enabled为 \"true\"才能显示。"
+
+# 9ceb40041acc44ed8cb1dbd759ffa528
+#: ../../networking2.rst:3440
+msgid "To create a firewall rule:"
+msgstr "创建防火墙规则："
+
+# c2c48ea9ba7d4778bc6bc6820adf83f0
+#: ../../networking2.rst:3464
+msgid "Click the Configuration tab and fill in the following values."
+msgstr "点击设置选项卡 填入以下值："
+
+# f889ae51ce804cde9da76459ef8ca9f6
+#: ../../networking2.rst:3468
+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 "**源 CIDR**.(可选)只允许在某个特定地址块的IP流量的话，输入一个CIDR或者一个逗号隔开的CIDR列表。例如：192.168.0.0/22或者192.168.0.0/24,192.168.1.0/24,192.168.2.0/24。留空则为允许所有的CIDR。"
+
+# 036b027b27144215b7da6ad75fa7c68e
+#: ../../networking2.rst:3475
+msgid "**Protocol**. The communication protocol in use on the opened port(s)."
+msgstr "**Protocol**: 已打开的端口所使用的通信协议。"
+
+# d8ab296b3ccd4f159dba1554303104e4
+#: ../../networking2.rst:3480
+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 "**起始端口和结束端口**. 你想要在防火墙上开放的端口。如果你只打开单个端口，在两个空格中填入相同的端口号。"
+
+# 45ba206ce4584c259c3d086badc5d9dc
+#: ../../networking2.rst:3486
+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 "**ICMP 类型和编号**.只有在设置ICMP协议时才会用到。提供需要填写的ICMP协议，ICMP包头的类型和编号。如果你不知道如何填写请参看ICMP文档。（这里推荐一个 http://wenku.baidu.com/view/e235e8ecaeaad1f346933fed.html）"
+
+# 83c407ae9e1d47c5a3a71b8e00327dee
+#: ../../networking2.rst:3498
+msgid "Egress Firewall Rules in an Advanced Zone"
+msgstr "高级区域中的出口防火墙规则"
+
+# 5c422781131a4989a954e4495b8e8630
+#: ../../networking2.rst:3500
+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 rules are removed the default "
+"policy, Block, is applied."
+msgstr "出口流量起源于从专用网络访问公共网络，例如Internet。默认情况下，在默认网络方案中，出口流量被拒绝，所以没有从来宾网络到Internet的出口流量被允许。不过，你可以通过创建出口防火墙规则来控制高级网络中的出口流量。当出口防火墙规则被应用时，规则指定的流量被允许，其余的流量被阻止。当所有的防火墙规则从默认策略中移除，阻止策略再次被应用。"
+
+# 9feacce2e10b4e7890c88a3bcc0a75fa
+#: ../../networking2.rst:3512
+msgid "Consider the following scenarios to apply egress firewall rules:"
+msgstr "应用出口防火墙规则时请思考如下方案："
+
+# 2fbbeae49f87458890dd0c859e95d758
+#: ../../networking2.rst:3516
+msgid "Egress firewall rules are supported on Juniper SRX and virtual router."
+msgstr "出口防火墙规则在Jniper SRX和虚拟路由器中均支持。"
+
+# 4559d85d3913439095bf17b9b34c926e
+#: ../../networking2.rst:3521
+msgid "The egress firewall rules are not supported on shared networks."
+msgstr "共享网络中不支持出口防火墙规则。"
+
+# 83d00a1385a048c1a78d6ff81e6d2c18
+#: ../../networking2.rst:3525
+msgid ""
+"Allow the egress traffic from specified source CIDR. The Source CIDR is part"
+" of guest network CIDR."
+msgstr "允许特定源CIDR的出口流量。源CIDR是来宾网络CIDR的一部分。"
+
+# 958ef1560ca04b98b84aad9240aa503e
+#: ../../networking2.rst:3530
+msgid "Allow the egress traffic with protocol TCP,UDP,ICMP, or ALL."
+msgstr "允许出口流量的协议为TCP，UDP,ICMP或ALL。"
+
+# 07016fef8ef94149b04668cd6107f2a4
+#: ../../networking2.rst:3534
+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 "允许出口流量协议和目标端口范围。端口范围需要指定TCP，UDP或ICMP类型和代码。"
+
+# d4588055cabf49ef8eb1caa7313a181a
+#: ../../networking2.rst:3539
+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 "新网络方案的默认策略是允许的，然而升级现有的网络方案后，防火墙服务提供商的出口策略默认将是拒绝。"
+
+# 73084bef40134e449ffe9d78b00d3ba2
+#: ../../networking2.rst:3544
+msgid "Configuring an Egress Firewall Rule"
+msgstr "配置出口防火墙规则"
+
+# eed98622c7604cfa83eec241a54202d7
+#: ../../networking2.rst:3556
+msgid ""
+"In Select view, choose Guest networks, then click the Guest network you "
+"want."
+msgstr "在选择视图中，选择来宾网络，然后点击需要的来宾网络。"
+
+# 8d5d5eaa44ef455786d9d7d6a412826e
+#: ../../networking2.rst:3561
+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 "要添加出口策略，点击出口策略选项卡并填写以下字段指定哪种类型的流量在来宾网络中是被允许从VM中实例发送出的。"
+
+# 615b7e1b5d4a4afba201cbd868ebcae4
+#: ../../networking2.rst:3565
+msgid "|egress-firewall-rule.png|"
+msgstr "|egress-firewall-rule.png|"
+
+# 3b0e293e06344c648450ac61d33c6e86
+#: ../../networking2.rst:3569
+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 "**CIDR**:(仅通过CIDR添加)为接受来来自特殊地址块的流量，输入一个CIDR，多个时用逗号隔开。CIDR是进入流量的基础IP地址。例如：192.168.0.0/22，为允许所有CIDR，请设为0.0.0.0/0"
+
+# a81a39ae46914bcbb4b99900eb016883
+#: ../../networking2.rst:3577
+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 "**协议**: 虚拟机发送流量所使用的网络协议。TCP和UDP通常用于数据交换和用户通讯。ICMP通常用于发送出错信息和网络监控数据。"
+
+# cf939bab32ca4167afcce4eddff3015e
+#: ../../networking2.rst:3584
+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 "**开始端口，结束端口**: (仅对TCP，UDP)。目的地为进入流量而设的监听端口范围。如果仅开放了单个端口，则在两者的区域中用同一端口。"
+
+# 12c38b633f1f4796af7e5704d6128627
+#: ../../networking2.rst:3590
+msgid ""
+"**ICMP Type, ICMP Code**: (ICMP only) The type of message and error code "
+"that are sent."
+msgstr "**ICMP类型**, **ICMP代码** (ICMP only): 信息类型及发送错误的代码。"
+
+# 2cd26bb0b191473db9267cd6ec1492e7
+#: ../../networking2.rst:3598
+msgid "Configuring the Default Egress Policy"
+msgstr "配置默认出口策略"
+
+# 68762a16d8b94ae298a95f68573272e3
+#: ../../networking2.rst:3600
+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 "通过网络方案配置隔离来宾网络的默认出口策略。通过创建网络方案选项决定来宾网络到公共网络的所有流量在默认策略中是允许或者拒绝。使用该网络方案创建网络。如果没有指定策略，你创建的来宾网络中的所有流量将被允许。"
+
+# 1113d91089884de2966c0431459b50af
+#: ../../networking2.rst:3608
+msgid "You have two options: Allow and Deny."
+msgstr "你有两个选择：允许和拒绝。"
+
+# 675178fcb7144053a9b257ebdc760670
+#: ../../networking2.rst:3611
+msgid "Allow"
+msgstr "允许"
+
+# db1c618c19734644b9f8f3714393f25c
+#: ../../networking2.rst:3613
+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 "如果你选择网络方案为允许，则默认出口流量被允许。无论如何，当配置了来宾网络的出口规则，规则被应用于阻止特定的流量和允许其他的 。如果网络中没有配置出口规则，则出口流量会被放行。"
+
+# cd74f40051e845018f993bc3377272b7
+# ada70d776fb44fff9ae52224ac02290a
+# 6870c74dca5142b0a048f825f2f357dc
+#: ../../networking2.rst:3620 ../../networking2.rst:5253
+#: ../../networking2.rst:5254
+msgid "Deny"
+msgstr "拒绝"
+
+# 8766188244b541e08448f923693d31d9
+#: ../../networking2.rst:3622
+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 "如果你选择网络方案为拒绝，则来宾网络中的默认出口流量将被阻挡。无论如何，当配置了来宾网络的出口规则，规则被应用于允许特定的流量。当实施来宾网络时，CloudStack为来宾网络添加防火墙出口规则指定默认的出口策略。"
+
+# 57f1dde63b4949e5a229d6af14593571
+#: ../../networking2.rst:3629
+msgid "This feature is supported only on virtual router and Juniper SRX."
+msgstr "该特定只支持虚拟路由器和Juniper SRX。"
+
+# a711b3baa28c4e3fa0ee4a98adacfcc8
+#: ../../networking2.rst:3633
+msgid "Create a network offering with your desirable default egress policy:"
+msgstr "为合适的默认出口策略创建一个网络方案："
+
+# c311057000004a4bb96e882cffcc28ce
+#: ../../networking2.rst:3637
+msgid "Log in with admin privileges to the CloudStack UI."
+msgstr "以管理员权限登录CloudStack用户界面。"
+
+# 25106537239545dc82409a24f0e06bd6
+#: ../../networking2.rst:3641
+msgid "In the left navigation bar, click Service Offerings."
+msgstr "在左侧导航栏中，点击 服务方案。"
+
+# 9289d78fd54546e3ac890ba5e790db43
+#: ../../networking2.rst:3645
+msgid "In Select Offering, choose Network Offering."
+msgstr "在选择方案中，选择网络方案。"
+
+# 09e3077c1dd044d899bb41898736a9b2
+# f6c2630b089b4f4ab8805c97a1cae4af
+# e7fccdf8282c4f6c8d7a6e5836840c19
+#: ../../networking2.rst:3649 ../../networking2.rst:6181
+#: ../../networking2.rst:6486
+msgid "Click Add Network Offering."
+msgstr "点击添加网络方案。"
+
+# 9c68f5258ad84445be883d57d0570c1e
+#: ../../networking2.rst:3653
+msgid "In the dialog, make necessary choices, including firewall provider."
+msgstr "在对话框中，填写必选项，包括防火墙提供者。"
+
+# cc2848c801fa426abd8304928f336162
+#: ../../networking2.rst:3658
+msgid "In the Default egress policy field, specify the behaviour."
+msgstr "在默认出口策略选项中，指定行为。"
+
+# a536099bc33f41dca54d66a4d01bd083
+#: ../../networking2.rst:3666
+msgid "Create an isolated network by using this network offering."
+msgstr "使用网络方案创建隔离网络。"
+
+# 4d9a8aef2dad4881b4fc8e1396be6aa2
+#: ../../networking2.rst:3668
+msgid ""
+"Based on your selection, the network will have the egress public traffic "
+"blocked or allowed."
+msgstr "根据你的选择，网络的出口公共流量将被拒绝或允许。"
+
+# fbdeecae49e641c1b71f8f62cb19d1e8
+#: ../../networking2.rst:3672
+msgid "Port Forwarding"
+msgstr "端口转发"
+
+# 242ca59ae1ec44818bf282c05c1a6171
+#: ../../networking2.rst:3674
+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 "一个端口转发服务是一系列转发转发规则的集合。一个端口转发服务随后可以应用于一个或多个来宾虚拟机。来宾虚拟机会根据端口转发规则作相关进入端口的管理。你可以定义一个或多个CIDR来过滤源IP地址。当你只希望特定的IP流量进入时是相当有用的。"
+
+# 6d1f9b4d8e6d4fe090b4bbf4f93459bd
+#: ../../networking2.rst:3682
+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 "一个客户VM可以在任意数量的端口转发服务中。端口转发服务可以不包含客户VM。如果客户VM在多个网络中，则端口转发仅在默认网络中定义时才生效。"
+
+# 0986f075d3ae43e980cfa47acdab6ffe
+#: ../../networking2.rst:3687
+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 "您不能使用端口转发打开弹性IP地址的端口。当使用弹性IP时，外部访问是由安全组控制的。参见安全组。"
+
+# 31bccf868e794f2cbdddcca69224bad3
+#: ../../networking2.rst:3691
+msgid "To set up port forwarding:"
+msgstr "设置端口转发："
+
+# 16dcd6a5ef644770900cdcce80794c67
+#: ../../networking2.rst:3699
+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 "如果还没有，请在 CloudStack中为Zone添加公网IP段。参阅 安装指南中的添加Zone和Pod。"
+
+# 3bd594ec854b43b583f5c33092e99657
+#: ../../networking2.rst:3705
+msgid "Add one or more VM instances to CloudStack."
+msgstr "在 CloudStack中创建1台或更多VM。"
+
+# 67e6520d95a749bca1dfd8ee7d653c61
+#: ../../networking2.rst:3709
+msgid "In the left navigation bar, click Network."
+msgstr "在左边导航栏，点击网络。"
+
+# 8ec41137f3064dbf9b135e9131c01078
+#: ../../networking2.rst:3713
+msgid "Click the name of the guest network where the VMs are running."
+msgstr "点击需要操作VM所在的网络名称。"
+
+# edc2c92eb5c940938babba424e0ab0a7
+#: ../../networking2.rst:3717
+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 "选择一个已有的IP或者获取一个新的IP地址。参阅 `\"获取一个新的IP\" <#acquiring-a-new-ip-address>`_.。 点击列表中IP地址的名称。"
+
+# 94e2eab0e63b4fc3857c9bd41223a42c
+#: ../../networking2.rst:3724
+msgid "Click the Configuration tab."
+msgstr "点击配置选项卡。"
+
+# 44faf09e38934875bdb4123f711051b7
+# 5bd7a3feb2a74eedb79b444a48452c5d
+#: ../../networking2.rst:3728 ../../networking2.rst:6733
+msgid "In the Port Forwarding node of the diagram, click View All."
+msgstr "在图表的端口转发节点，点击查看所有。"
+
+# f513170f116e42d98255397872cd84b2
+#: ../../networking2.rst:3736
+msgid ""
+"**Public Port**. The port to which public traffic will be addressed on the "
+"IP address you acquired in the previous step."
+msgstr "**公用端口**:你在之前操作时所获取的供公共流量使用的公用IP地址的端口。 "
+
+# 1e1f06ab8e7d4b228f0671927b1d37b7
+#: ../../networking2.rst:3741
+msgid ""
+"**Private Port**. The port on which the instance is listening for forwarded "
+"public traffic."
+msgstr "**专用端口**: 虚拟机监听转发的公网流量的端口。"
+
+# b96619b413e4435494d46e6c18e985b6
+#: ../../networking2.rst:3746
+msgid "**Protocol**. The communication protocol in use between the two ports"
+msgstr "**Protocol**:两个端口之间使用的通信协议。"
+
+# 189bbad94193454d80e285996b14f052
+#: ../../networking2.rst:3754
+msgid "IP Load Balancing"
+msgstr "IP负载均衡"
+
+# 8bb4fc89584047a4979eb7ade38555ac
+#: ../../networking2.rst:3756
+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 "用户可以选择关联同一个公网IP到多个虚拟机。 CloudStack实现了TCP级别的负载平衡器，有以下策略。"
+
+# 2d62543390a44d9b86be0973a26237e3
+# 71d3f562cf68451d95abf2e2855c938f
+# a91ad3d092144bad9c7c61b4fae3c2e9
+#: ../../networking2.rst:3762 ../../networking2.rst:6371
+#: ../../networking2.rst:6644
+msgid "Round-robin"
+msgstr "轮询"
+
+# 8fd8ce7230194556b444745abd07c778
+#: ../../networking2.rst:3766
+msgid "Least connection"
+msgstr "最少连接数"
+
+# 5f1fa380f5a1493cbb22ae41bd77eab0
+#: ../../networking2.rst:3770
+msgid "Source IP"
+msgstr "源IP"
+
+# e337b776e21743439b7207bfb4c76b76
+#: ../../networking2.rst:3772
+msgid ""
+"This is similar to port forwarding but the destination may be multiple IP "
+"addresses."
+msgstr "这类似于端口转发，但目标可能会有多个IP地址。"
+
+# 348ae44471844fa39d0776a54c21522c
+#: ../../networking2.rst:3776
+msgid "DNS and DHCP"
+msgstr "DNS和DHCP"
+
+# e9f3ca6c9e6f429bb4fe851ef31d2037
+#: ../../networking2.rst:3778
+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 "虚拟路由器为来宾提供DNS和DHCP服务。它将DNS请求代理到在可用区域中配置的DNS服务器。"
+
+# dd8cfae4c4df4db5abe405b9fc23f91c
+#: ../../networking2.rst:3783
+msgid "Remote Access VPN"
+msgstr "远程访问VPN"
+
+# 421361e0532246a2b00b1aabc0663fa7
+#: ../../networking2.rst:3785
+msgid ""
+"CloudStack account owners can create virtual private networks (VPN) to "
+"access their virtual machines. If the guest network is instantiated from a "
+"network offering that offers the Remote Access VPN service, the virtual "
+"router (based on the System VM) is used to provide the service. CloudStack "
+"provides a L2TP-over-IPsec-based remote access VPN service to guest virtual "
+"networks. Since each network gets its own virtual router, VPNs are not "
+"shared across the networks. VPN clients native to Windows, Mac OS X and iOS "
+"can be used to connect to the guest networks. The account owner can create "
+"and manage users for their VPN. CloudStack does not use its account database"
+" for this purpose but uses a separate table. The VPN user database is shared"
+" across all the VPNs created by the account owner. All VPN users get access "
+"to all VPNs created by the account owner."
+msgstr "CloudStack中的账户拥有者可以建立虚拟专用网(VPN)以便访问他们的虚拟机。如果通过网络方案对来宾网络提供远程VPN访问服务的实例化，虚拟路由(基于System VM)将被用于提供服务。CloudStack为来宾虚拟网络提供了一个基于L2TP-over-IPsec-based协议的远程VPN访问服务。因为每个网络有它自己的虚拟路由器，VPNs不能跨网络共享。Windows, Mac OS X和iOS自带的VPN客户端可以用于访问来宾网络。账户拥有者可以建立并管理他们的VPN用户。CloudStack并不为此使用自己的账户数据库，而是使用一个独立的表。VPN用户数据库在同一个账户拥有者建立的VPN网络中被共享。 也就是说，同一个账户拥有者创建的所有VPN可以被它的所有VPN用户访问。"
+
+# a732cf37468141f3b91c785a8153d60d
+#: ../../networking2.rst:3800
+msgid ""
+"Make sure that not all traffic goes through the VPN. That is, the route "
+"installed by the VPN should be only for the guest network and not for all "
+"traffic."
+msgstr "确保不是所有的网络流量走VPN。也就是说，用于配置VPN的route不是唯一用于该guest network，也不承担全部的网络流量。"
+
+# 4dbb5c3287b64cd5abc3987f02c48b48
+#: ../../networking2.rst:3806
+msgid ""
+"**Road Warrior / Remote Access**. Users want to be able to connect securely "
+"from a home or office to a private network in the cloud. Typically, the IP "
+"address of the connecting client is dynamic and cannot be preconfigured on "
+"the VPN server."
+msgstr "**公路勇士/远程访问**. .用户希望可以安全地从家里或者办公室连接到云里的一个 私有网络。特别是连接的客户端的IP地址是动态决定的，不能预先配置到VPN 服务器上。"
+
+# eb6134e7170946da9f096bcd062d7aad
+#: ../../networking2.rst:3813
+msgid ""
+"**Site to Site**. In this scenario, two private subnets are connected over "
+"the public Internet with a secure VPN tunnel. The cloud user's subnet (for "
+"example, an office network) is connected through a gateway to the network in"
+" the cloud. The address of the user's gateway must be preconfigured on the "
+"VPN server in the cloud. Note that although L2TP-over-IPsec can be used to "
+"set up Site-to-Site VPNs, this is not the primary intent of this feature. "
+"For more information, see \":ref:`setting-s2s-vpn-conn`\"."
+msgstr "**Site to Site 站点到站点**。在这个场景中，两个私有子网通过公共互联网上的一个安全VPN隧道互联。云用户的子网 （例如：办公室的网络）通过一个网关连接到云中的网络。用户的网关地址必须被预先配置到云的VPN服务器上。注意：通过 L2TP-over-IPsec 协议可以用来配置站点到站点的 VPN，虽然这不是该特性的最初目标。更多信息，参考\":ref:`setting-s2s-vpn-conn`\"。"
+
+# 7dd56949a6f74a439a60c07ad67f722a
+#: ../../networking2.rst:3823
+msgid "Configuring Remote Access VPN"
+msgstr "配置远程访问VPN"
+
+# 0061faa9e6cd4ad59954ed3c0856b411
+#: ../../networking2.rst:3825
+msgid "To set up VPN for the cloud:"
+msgstr "为云设置VPN："
+
+# 0e3ff971fa3d4442848a972f64282837
+#: ../../networking2.rst:3833
+msgid "In the left navigation, click Global Settings."
+msgstr "在左侧导航栏，点击 全局设置"
+
+# c2fc515f4e564cf48108c56364709b7b
+#: ../../networking2.rst:3837
+msgid "Set the following global configuration parameters."
+msgstr "设置以下全局配置参数。"
+
+# 6e225aa038964885a007931b82b18986
+#: ../../networking2.rst:3841
+msgid ""
+"remote.access.vpn.client.ip.range - The range of IP addresses to be "
+"allocated to remote access VPN clients. The first IP in the range is used by"
+" the VPN server."
+msgstr "remote.access.vpn.client.ip.range – 分配给远程访问VPN客户端的IP地址范围。第一个IP被VPN服务器使用。"
+
+# 1639d05b22d9481b8b92fc8a707d027a
+#: ../../networking2.rst:3847
+msgid "remote.access.vpn.psk.length - Length of the IPSec key."
+msgstr "remote.access.vpn.psk.length – IPsec密钥长度。"
+
+# d8c75e5dc742435ca19c4a06e2a61ecd
+#: ../../networking2.rst:3851
+msgid ""
+"remote.access.vpn.user.limit - Maximum number of VPN users per account."
+msgstr "remote.access.vpn.user.limit – 单个账户的最大VPN用户数量。"
+
+# 3f55599605614d13a5e11b6eb4a74bfa
+#: ../../networking2.rst:3854
+msgid "To enable VPN for a particular network:"
+msgstr "为特定的网络启用VPN："
+
+# 37b4e592dd084399a75751ec656055ca
+# f5662606b3e94deaa8d00053c5b1f843
+#: ../../networking2.rst:3858 ../../networking2.rst:3894
+msgid "Log in as a user or administrator to the CloudStack UI."
+msgstr "使用用户或管理员身份登录到CloudStack用户界面。"
+
+# c949dee3a72b40e1aa492da5a563a3bf
+# b4fa7486bbc9431d8834b563df517c52
+#: ../../networking2.rst:3862 ../../networking2.rst:3898
+msgid "In the left navigation, click Network."
+msgstr "在左边导航栏，点击网络。"
+
+# 89d5b593db5e47e4b8d8ba9343bb9a81
+#: ../../networking2.rst:3866
+msgid "Click the name of the network you want to work with."
+msgstr "选择你要操作的网络名称"
+
+# 7f1c96aff09c4aca89166670c00e135b
+#: ../../networking2.rst:3874
+msgid "Click one of the displayed IP address names."
+msgstr "点击一个显示的IP地址名称。"
+
+# c037fe41e67e44569c8ef9d9ed2c87de
+# 0b7e6681912942398e9b55f50db5fabb
+#: ../../networking2.rst:3878 ../../networking2.rst:3963
+msgid "Click the Enable VPN button. |vpn-icon.png|"
+msgstr "点击启用VPN按钮。|vpn-icon.png|"
+
+# d8ac0fa0cc1f430ab2dabd3976e35a13
+#: ../../networking2.rst:3880
+msgid "The IPsec key is displayed in a popup window."
+msgstr "IPsec密钥将显示在弹出的窗口中。"
+
+# 3b6c749a19ac411e85a91bebde5620ac
+#: ../../networking2.rst:3883
+msgid "Configuring Remote Access VPN in VPC"
+msgstr "为VPC配置远程访问VPN"
+
+# 24849989ce59453cb53461958b872d24
+#: ../../networking2.rst:3885
+msgid ""
+"On enabling Remote Access VPN on a VPC, any VPN client present outside the "
+"VPC can access VMs present in the VPC by using the Remote VPN connection. "
+"The VPN client can be present anywhere except inside the VPC on which the "
+"user enabled the Remote Access VPN service."
+msgstr "在VPC中启用远程访问VPN，任何VPC以外的VPN客户端都可以使用远程VPN连接访问VPC中的VM。VPN客户端可以在除了用户启用了远程访问VPN服务的VPC中的任何位置。"
+
+# 9fe0ef310ce946a4b81eb99779e7d6e2
+#: ../../networking2.rst:3890
+msgid "To enable VPN for a VPC:"
+msgstr "为VPC开启VPN："
+
+# a35416d0aa534a0786c5008000fd8e43
+# e9f7b5e6165a407b8c8f26dbd4564cea
+# 70b305de6a494311b862c80f66aec1ce
+# 77e179e8fd184282bca07276311f4193
+# c258a12f71d44428b74e9dace4023355
+# e34ba66fcef1410680e2597a9d2a8954
+# 2becfb5ca8464b0486c1fe7c82b5a4e3
+# 0712e1bd6b914f2885daf1e5febb7442
+# 97c2acefafb34f709fcc84b7a4dc40b9
+# b527a3e4798548ab91c07365a835ea9c
+# 3e347e3728d44b79a3475adb8b0600f2
+# b12fa2f420ac47059eb47eb95abebe58
+# 27fcf04f38494625a2efecfad5de2f9c
+# 9f39d7e9da4d40e5be4cbf6b4666758a
+# f624d82ab7e649288e146d0cebab16e0
+# 1895dd237c1341b295430829d5c5950c
+# f40ec8edcf6f46ff93c1db49b2d59307
+# 0eb2cf52b2f144dfb78982d1caa03b35
+#: ../../networking2.rst:3902 ../../networking2.rst:4370
+#: ../../networking2.rst:4467 ../../networking2.rst:4658
+#: ../../networking2.rst:5074 ../../networking2.rst:5139
+#: ../../networking2.rst:5270 ../../networking2.rst:5352
+#: ../../networking2.rst:5521 ../../networking2.rst:5760
+#: ../../networking2.rst:5851 ../../networking2.rst:5939
+#: ../../networking2.rst:6030 ../../networking2.rst:6273
+#: ../../networking2.rst:6583 ../../networking2.rst:6667
+#: ../../networking2.rst:6792 ../../networking2.rst:6831
+msgid "In the Select view, select VPC."
+msgstr "在选择视图中，选择VPC。"
+
+# ec4a1f9371cd43e39a21d45da9e513e9
+# 903528c98fb6402081d0c518396e4d5a
+# 02c81362a5294fe885a28cc0abe9f5a9
+# 8449bcf110af4969aeb6172fafda2205
+# a213eb463b5c421bbd5a602580f1b51a
+# 32bed119537345e7aa5c1f4d2ec728a5
+# f826c1e8499f44a7b886ac07bbeb0b5f
+# e3d9e5ecc1964bd880bc814a1c8a935b
+# 0d0c7e45230d4a7bb6d548c856fa8f7a
+# f4df1631caf646afad3bba723757c066
+# e30097b3b31c4398bab851342cc05e17
+# f26cae26e34e447e86996448bd94ee59
+# 5e20c449bba64885af814ea48d956e2c
+# ac7881d3dc5743a1baad101ab5045e35
+#: ../../networking2.rst:3904 ../../networking2.rst:4372
+#: ../../networking2.rst:4660 ../../networking2.rst:5272
+#: ../../networking2.rst:5354 ../../networking2.rst:5523
+#: ../../networking2.rst:5762 ../../networking2.rst:5853
+#: ../../networking2.rst:5941 ../../networking2.rst:6032
+#: ../../networking2.rst:6275 ../../networking2.rst:6585
+#: ../../networking2.rst:6669 ../../networking2.rst:6833
+msgid ""
+"All the VPCs that you have created for the account is listed in the page."
+msgstr "此帐号创建的所有VPC将显示在页面中。"
+
+# 7b4b5acd29144a01a92211053af28180
+# 8993b44d5f7c418aafe0163c0dc2f320
+# 1c850ec226f5448797b19cee4f4bbdda
+#: ../../networking2.rst:3909 ../../networking2.rst:5277
+#: ../../networking2.rst:5359
+msgid "Click the Configure button of the VPC."
+msgstr "点击VPC的配置按钮。"
+
+# 41f127a431e44ea1af73a4efd93d50dd
+# 4663a4f2b9d749bdaa308b9c71f6625a
+# 6517ef547f114583b55ea471ddfa3e96
+# f95ad4b883994ccab44a025f2b50f7e7
+# 8e35937d2ca84fa6905cf264caabfb6b
+# b7d205c295044f38ad749b9b58a45281
+# c33a19c6331843fca695c025eef65638
+#: ../../networking2.rst:3911 ../../networking2.rst:4383
+#: ../../networking2.rst:4483 ../../networking2.rst:4675
+#: ../../networking2.rst:5279 ../../networking2.rst:6286
+#: ../../networking2.rst:6680
+msgid "For each tier, the following options are displayed:"
+msgstr "对于每一个层，会显示以下选项。"
+
+# d36b5f8182cf4512aadad3221d7dd83d
+# dc877a54fec94d7cae1f81bdb0023b94
+# 8a8bdc30b2174cacbb572f5ad4c98a7b
+# 1b988edb0d8e4314a7eb8c37c3cfbf77
+# c30de8bbacbe4334a9b05a16ff351461
+# df7817d8060843d69314130c722fe9b6
+# c68c4a643bc0413a811ad7a01bfdc606
+# 0166943624e64d68860eafa9e58ab9bd
+# d21582e266e543afb57737fda85467b5
+# 6fa5c9555c7e46ac9ef191dd4173f8da
+# e6cdbca9e85d47b9b042e1f0310461fe
+#: ../../networking2.rst:3915 ../../networking2.rst:4387
+#: ../../networking2.rst:4487 ../../networking2.rst:4679
+#: ../../networking2.rst:5283 ../../networking2.rst:5542
+#: ../../networking2.rst:5868 ../../networking2.rst:5955
+#: ../../networking2.rst:6047 ../../networking2.rst:6290
+#: ../../networking2.rst:6684
+msgid "Internal LB"
+msgstr "内部LB"
+
+# 6fa74bd617c04d698de6f38bf2416158
+# b4ec2750e056403ab30e230857867f11
+# 051be71f2d03468f854f32b5dfdb6439
+# e6dce01524cb4e9392a365a592674ec5
+# 3ac84bc009234f6a8e8a1f1caebe83a1
+# fc8ff98a80744b8a811a5f1c8f805de5
+# 7d23ee0ec36f41ed93929f00828f848d
+# 37dc837b902246d3855ec01eda4c0be2
+# 64590fae08ae4c8bbba1feb231077932
+# e77c1fc68625472b9ecf752fb5790551
+# 00a7eccc5d684130b79b1d1451b6390f
+#: ../../networking2.rst:3919 ../../networking2.rst:4391
+#: ../../networking2.rst:4491 ../../networking2.rst:4683
+#: ../../networking2.rst:5287 ../../networking2.rst:5546
+#: ../../networking2.rst:5872 ../../networking2.rst:5959
+#: ../../networking2.rst:6051 ../../networking2.rst:6294
+#: ../../networking2.rst:6688
+msgid "Public LB IP"
+msgstr "公共LB IP"
+
+# fab3827cfc494ecd8b648f564a195172
+# 19cff60834f84a7b91d3dd25f4eff4f5
+# d38259f3d32d473980ccdef9d1689608
+# 0846fc98b6fc40eabb78391a7641f248
+# 14c417b19bdf4c3f8a22c9302c8edc7f
+# 11a737406efb4d0d987480bda52770e0
+# 65eadb3d777e4e10b89edf86e21a965e
+# d0731ebc92ab457d919264f55f94e1d8
+# ecfaad1840444dc5b5fc9fecfd3a5db8
+# f87032d442244dd9ace6770bd77cc552
+# 53d5237aaea24a448651d13727dcba17
+#: ../../networking2.rst:3927 ../../networking2.rst:4399
+#: ../../networking2.rst:4499 ../../networking2.rst:4691
+#: ../../networking2.rst:5295 ../../networking2.rst:5554
+#: ../../networking2.rst:5880 ../../networking2.rst:5967
+#: ../../networking2.rst:6059 ../../networking2.rst:6302
+#: ../../networking2.rst:6696
+msgid "Virtual Machines"
+msgstr "虚拟机"
+
+# 55332d391cdd468495ad76f952811577
+# 46bedbc30be240609724ff6eee13c73e
+# 78e5566733024d098b27e7a0ac093950
+# 4ffb5ac895d04c9bb052f07e28e82fa9
+# ba68a5eb30484d1ca76c23fc9bc74a09
+# 3dec4fac4a1446248f59d4ba0fe33666
+# afabe87fc2fc4de1bf89a7643d99ed17
+# 9d72e437059c43b39a0369449b50ce08
+# 58c6f2db6cff4dc49e7412bb20e7a01a
+# 23eee839c1c34752ac8eab15d0029064
+# 498838fb8fe040329abb978aea99f2be
+#: ../../networking2.rst:3933 ../../networking2.rst:4405
+#: ../../networking2.rst:4505 ../../networking2.rst:4697
+#: ../../networking2.rst:5301 ../../networking2.rst:5560
+#: ../../networking2.rst:5886 ../../networking2.rst:5973
+#: ../../networking2.rst:6065 ../../networking2.rst:6308
+#: ../../networking2.rst:6702
+msgid "The following router information is displayed:"
+msgstr "显示以下路由器信息："
+
+# c26c1853bc4f4277b2210032d9fb8c71
+# 0139a8b25d624810bd6bd843f489005e
+# 1a93bacd56834a9a8b5b28a8a7860331
+# 37f0f96d9ff840e2bc3edfce09290220
+# 361aba2c5dde45f78980a4afef525afe
+# c0a4cfa4e5fe4cc5a0ad6e9b742ba56c
+# 77a0686377bb4665b5d5069fb6b3ce35
+# 0a570734113f4de18e33b19bcf20dc8c
+# f55e6f457a684df2b425513b5ebb8f84
+# e04ebd7737dc4c5d905b4a2e898dd1dd
+# dac82df8dc6e4aeb9f668a0fce3839f7
+#: ../../networking2.rst:3937 ../../networking2.rst:4409
+#: ../../networking2.rst:4509 ../../networking2.rst:4701
+#: ../../networking2.rst:5305 ../../networking2.rst:5564
+#: ../../networking2.rst:5890 ../../networking2.rst:5977
+#: ../../networking2.rst:6069 ../../networking2.rst:6312
+#: ../../networking2.rst:6706
+msgid "Private Gateways"
+msgstr "专用网关"
+
+# a9e24dfd29a3416d90e3051d7adbfd22
+# f868061634e14c84ad71294278a83859
+# 48ca230e37f745998e82d810cac0601f
+# 7e3d042b215f496eadd246802bc8d222
+# 5ff70875c6a34da991576fa2cb6c9383
+# e3012be55eb74fcf88d4ef4e6b761efd
+# e3050c23e81b4d149d94857d393c88e2
+# ddae1748531d48bbbdd4d197c05796fb
+# efeffe0be53f4e16a0484bfa29446228
+# 0b41ea343fdd486c8076aafd64b39af0
+# f3c278d0a4e1481da2d1684a5128a925
+#: ../../networking2.rst:3941 ../../networking2.rst:4413
+#: ../../networking2.rst:4513 ../../networking2.rst:4705
+#: ../../networking2.rst:5309 ../../networking2.rst:5568
+#: ../../networking2.rst:5894 ../../networking2.rst:5981
+#: ../../networking2.rst:6073 ../../networking2.rst:6316
+#: ../../networking2.rst:6710
+msgid "Public IP Addresses"
+msgstr "公共IP地址"
+
+# 2e72f864a49742349a9ac3443b812ace
+# 34ef012f20b144bd90ebf24e0b12b44a
+# 5913d2bdbb4a4e53a3ac3b0298e92e49
+# 40012c7aa1ee4262bd10d91b96e8a9c9
+# 6f57a5bdf67e4cb58990f4d008083823
+# 853f28cafe0a4fc2891f7fabaae17a63
+# 3e495712a7e54c939d916fc98129d091
+# e3f120e5aaaf463c8ecc396d8abbd9d5
+# 97c98429541c4be592183749d007886c
+# 7a721c1ac43b4854b117cbce3eb74212
+# f91d27b21a40457eafd937a34be8e496
+#: ../../networking2.rst:3945 ../../networking2.rst:4417
+#: ../../networking2.rst:4517 ../../networking2.rst:4709
+#: ../../networking2.rst:5313 ../../networking2.rst:5572
+#: ../../networking2.rst:5898 ../../networking2.rst:5985
+#: ../../networking2.rst:6077 ../../networking2.rst:6320
+#: ../../networking2.rst:6714
+msgid "Site-to-Site VPNs"
+msgstr "站点到站点 VPN"
+
+# 349f95fa06f64797aff0edd3c925735e
+# 38e399fbd60f4bf5bf7ed82ae8ca8e0a
+# 5a4c91418b0a4ff99bb9831c5d46345b
+# 4f3ed50fa2084beab6f50bf893480074
+# 1e5d1d73bc104f34bcd1a3323e0735ef
+# 1191bcc81f424ae0b9582151a69b7c74
+# f62a78e753f344e1a9aa50099eea6317
+# b7b2d9ae13c340259dc2ccd54fd143d4
+# c450b0235bc74c36970ffde3fc943e02
+# 6e50d4714233432ca68b491f4d81721f
+# 86a0e3bd6be54e0a883c965b6aa369c8
+#: ../../networking2.rst:3949 ../../networking2.rst:4421
+#: ../../networking2.rst:4521 ../../networking2.rst:4713
+#: ../../networking2.rst:5317 ../../networking2.rst:5576
+#: ../../networking2.rst:5902 ../../networking2.rst:5989
+#: ../../networking2.rst:6081 ../../networking2.rst:6324
+#: ../../networking2.rst:6718
+msgid "Network ACL Lists"
+msgstr "网络 ACL列表"
+
+# 4ea069860ba74bfdbaa2253dec4c494b
+# 13c12d90b1e84f96ad76cba5a47982c5
+# c218f564b23b41ea9e5193fb707b10fc
+# 82b5209e8daf48ef940f3188b13d1773
+#: ../../networking2.rst:3953 ../../networking2.rst:6085
+#: ../../networking2.rst:6328 ../../networking2.rst:6722
+msgid "In the Router node, select Public IP Addresses."
+msgstr "在路由器节点中，选择公共IP地址。"
+
+# ba7c1886ce2f4ee2b912e553ebc3d61b
+# 0bfc7d4f8b8342789c24f18c3050712e
+# 580ba0ab2bca4c888e0a88e20bdbea27
+# d809889924b44274b70abfc5c5e45700
+# 25e20e9a574348cdaa22b580e2eda1e7
+#: ../../networking2.rst:3955 ../../networking2.rst:5995
+#: ../../networking2.rst:6087 ../../networking2.rst:6330
+#: ../../networking2.rst:6724
+msgid "The IP Addresses page is displayed."
+msgstr "系统显示IP地址页面。"
+
+# b79d01255d3242b2bca0f5b82a3f42a7
+#: ../../networking2.rst:3959
+msgid "Click Source NAT IP address."
+msgstr "点击源NAT IP地址。"
+
+# 124e19bc247541509add9967859dbd05
+#: ../../networking2.rst:3965
+msgid "Click OK to confirm. The IPsec key is displayed in a pop-up window."
+msgstr "点击OK确认。IPsec密钥将显示在弹出的窗口中。"
+
+# d67e0d11d2a84def84932c99310a36fc
+#: ../../networking2.rst:3967
+msgid "Now, you need to add the VPN users."
+msgstr "现在，需要添加VPN用户。"
+
+# b4de336c841f4553b07b5e167ffa4d21
+#: ../../networking2.rst:3971
+msgid "Click the Source NAT IP."
+msgstr "点击源NAT IP。"
+
+# 4d3e59a6636142a4b87a1bc3e1114a0b
+#: ../../networking2.rst:3975
+msgid "Select the VPN tab."
+msgstr "选择VPN选项卡。"
+
+# 27ab772233bc45b3926b22bfac64318c
+#: ../../networking2.rst:3979
+msgid ""
+"Add the username and the corresponding password of the user you wanted to "
+"add."
+msgstr "为你要创建的用户添加用户名和对应的密码。"
+
+# 389210e40ce143f7a96d6c93a81f9f34
+#: ../../networking2.rst:3988
+msgid "Repeat the same steps to add the VPN users."
+msgstr "重复相同的步骤添加VPN用户。"
+
+# b3ada11c846b4cd9a7ea6de9608b48ed
+#: ../../networking2.rst:3991
+msgid "Using Remote Access VPN with Windows"
+msgstr "在Windows系统中使用远程访问VPN"
+
+# 4dacd242f3fc46b58f15b96d910b2a54
+#: ../../networking2.rst:3993
+msgid ""
+"The procedure to use VPN varies by Windows version. Generally, the user must"
+" edit the VPN properties and make sure that the default route is not the "
+"VPN. The following steps are for Windows L2TP clients on Windows Vista. The "
+"commands should be similar for other Windows versions."
+msgstr "程序使用不同Windows版本的VPN。通常用户必须编辑VPN属性并确保不使用VPN的默认路由。以下步骤使用基于Windows Vista的Windows L2TP客户端。命令应该类似于其他版本的Windows。"
+
+# e7a57a9061b640579542551d1c1a0a6a
+#: ../../networking2.rst:4000
+msgid ""
+"Log in to the CloudStack UI and click on the source NAT IP for the account. "
+"The VPN tab should display the IPsec preshared key. Make a note of this and "
+"the source NAT IP. The UI also lists one or more users and their passwords. "
+"Choose one of these users, or, if none exists, add a user and password."
+msgstr "登录到CloudStack用户界面并点击账户下的源NAT IP。VPN选项卡应该会显示IPsec预共享密钥。记录该密钥和源NAT IP。用户界面同样也列出了一个多或多个用户他们的密码。选择一个用户，或者如果不存在任何用户，则创建一个用户。"
+
+# d1fc77ea9ff74b79be7e81efd85d177a
+#: ../../networking2.rst:4008
+msgid ""
+"On the Windows box, go to Control Panel, then select Network and Sharing "
+"center. Click Setup a connection or network."
+msgstr "在Windows中，进入控制面板，然后选择网络和共享中心，点击设置一个网络连接。"
+
+# 7e4498aa4e0a4ebdafe3f2dab310a0f6
+#: ../../networking2.rst:4013
+msgid "In the next dialog, select No, create a new connection."
+msgstr "在下一个对话框中，选择否，创建一个新的连接。"
+
+# 90e3f9cc2fc740aca1edb2b0edc930f9
+#: ../../networking2.rst:4017
+msgid "In the next dialog, select Use my Internet Connection (VPN)."
+msgstr "在下一个对话框中，选择使用我的Internet连接(VPN)."
+
+# 8e80995c739c4114ac013a88f71347e9
+#: ../../networking2.rst:4021
+msgid ""
+"In the next dialog, enter the source NAT IP from step #1 and give the "
+"connection a name. Check Don't connect now."
+msgstr "在下一个对话框中，输入此步骤#1中的源NAT IP地址并填写连接名称。勾选现在不连接。"
+
+# 2b3c410c5ec74b4eb6b7d269c04bdfb6
+#: ../../networking2.rst:4027
+msgid ""
+"In the next dialog, enter the user name and password selected in step #1."
+msgstr "在下一个对话框中，输入此步骤#1中的用户名和密码。"
+
+# 56b71e910d734f4b93b857548bcc867d
+#: ../../networking2.rst:4036
+msgid ""
+"Go back to the Control Panel and click Network Connections to see the new "
+"connection. The connection is not active yet."
+msgstr "返回控制面板并点击网络连接查看这个新的连接。但当前连接并不是活动状态。"
+
+# 5032581f1fe042c1844ebad881b3d41a
+#: ../../networking2.rst:4041
+msgid ""
+"Right-click the new connection and select Properties. In the Properties "
+"dialog, select the Networking tab."
+msgstr "在新创建的连接上点击右键并选择属性。在属性对话框中，选择网络选项卡。"
+
+# 23ee9538e54a49c39f87d22e2a8aae65
+#: ../../networking2.rst:4046
+msgid ""
+"In Type of VPN, choose L2TP IPsec VPN, then click IPsec settings. Select Use"
+" preshared key. Enter the preshared key from step #1."
+msgstr "在VPN类型中，选择L2TP IPsec VPN,然后点击IPsec设置，选择用户预共享密钥。并输入此步骤#1中提供的密钥。"
+
+# e432bdf75f62482ab7522b9a120ab5b1
+#: ../../networking2.rst:4051
+msgid ""
+"The connection is ready for activation. Go back to Control Panel -> Network "
+"Connections and double-click the created connection."
+msgstr "该连接已经准备好被激活。返回到控制面板 -> 网络连接，双击创建连接。"
+
+# fd7a739563464507bd2c37c2ad54953c
+#: ../../networking2.rst:4056
+msgid "Enter the user name and password from step #1."
+msgstr "输入此步骤 #1中提供的用户名和密码。"
+
+# aebae91f3d7c45eb9f3dd5fa89388da5
+#: ../../networking2.rst:4059
+msgid "Using Remote Access VPN with Mac OS X"
+msgstr "在Mac OS X 中使用远程访问VPN"
+
+# 580e45aef47e4d37846427f1b651a7e2
+#: ../../networking2.rst:4061
+msgid ""
+"First, be sure you've configured the VPN settings in your CloudStack "
+"install. This section is only concerned with connecting via Mac OS X to your"
+" VPN."
+msgstr "首先，确保在你的CloudStack中已经设置好VPN。本章节仅涉及通过Mac OS X 连接至VPN。"
+
+# 093bbd04cdab4e429fd3a568f011382f
+#: ../../networking2.rst:4065
+msgid ""
+"Note, these instructions were written on Mac OS X 10.7.5. They may differ "
+"slightly in older or newer releases of Mac OS X."
+msgstr "请注意，此指南只基于Mac OS X 10.7.5 。在旧版或新版本的Mac OS X中可能会略有不同。"
+
+# 50d800b2cf72450f8bd890270e0e0ee6
+#: ../../networking2.rst:4070
+msgid "On your Mac, open System Preferences and click Network."
+msgstr "在Mac中，打开系统偏好设置然后点击网络。"
+
+# 3a1af061748d4e418eaaf8b5f8877f09
+#: ../../networking2.rst:4074
+msgid "Make sure Send all traffic over VPN connection is not checked."
+msgstr "确保Send all traffic over VPN connection没有被选定。"
+
+# ef3e10026dbb4d1798d2133b3e9c22dd
+#: ../../networking2.rst:4078
+msgid ""
+"If your preferences are locked, you'll need to click the lock in the bottom "
+"left-hand corner to make any changes and provide your administrator "
+"credentials."
+msgstr "如果你的首选项框被锁住，你如果要做些改动需要点击底部左侧的锁按钮，并提供管理员认证。"
+
+# 292ec3cfa46e48a9a541875456694b77
+#: ../../networking2.rst:4084
+msgid ""
+"You will need to create a new network entry. Click the plus icon on the "
+"bottom left-hand side and you'll see a dialog that says \"Select the "
+"interface and enter a name for the new service.\" Select VPN from the "
+"Interface drop-down menu, and \"L2TP over IPSec\" for the VPN Type. Enter "
+"whatever you like within the \"Service Name\" field."
+msgstr "您将需要创建一个新的网络入口。点击底部左侧的加号图标，你会看到一个对话框，写着“选择接口并输入新服务的名称”。在接口下拉菜单中选择VPN，VPN类型为“基于IPSec的L2TP”。在“服务名称”中输入任何你喜欢的字段。"
+
+# 164c5574c52f41baabcf85d8a575f7fa
+#: ../../networking2.rst:4092
+msgid ""
+"You'll now have a new network interface with the name of whatever you put in"
+" the \"Service Name\" field. For the purposes of this example, we'll assume "
+"you've named it \"CloudStack.\" Click on that interface and provide the IP "
+"address of the interface for your VPN under the Server Address field, and "
+"the user name for your VPN under Account Name."
+msgstr "现在你需要在\"Service Name\" 中填入新的网络接口的名称。对于这个例子，我们假设你已经把它命名为“CloudStack”。点击该接口，并在服务器地址字段中填入提供的VPN IP地址，并在账户名称中填入您的VPN用户名。"
+
+# 581debc7245446b48e5e1c54984c711d
+#: ../../networking2.rst:4101
+msgid ""
+"Click Authentication Settings, and add the user's password under User "
+"Authentication and enter the pre-shared IPSec key in the Shared Secret field"
+" under Machine Authentication. Click OK."
+msgstr "点击身份验证设置，在机器验证中，用户身份验证下输入用户名和密码，在共享密钥下输入预共享IPsec密钥。点击OK。"
+
+# 37bca241509a4e3198b5a084939f14e5
+#: ../../networking2.rst:4107
+msgid ""
+"You may also want to click the \"Show VPN status in menu bar\" but that's "
+"entirely optional."
+msgstr "你也可以点击\"在菜单栏中查看VPN状态\",这完全是可选的操作。"
+
+# 0cb9849a0685438b81bdcd0818eb6202
+#: ../../networking2.rst:4112
+msgid "Now click \"Connect\" and you will be connected to the CloudStack VPN."
+msgstr "现在点击\"连接\" 你将会连接到CloudStack VPN。"
+
+# 3bac353e80464ab9856af6e4cd87363e
+#: ../../networking2.rst:4117
+msgid "Setting Up a Site-to-Site VPN Connection"
+msgstr "配置站点到站点的VPN连接"
+
+# 38ff1a3ce4164fa994abfc693aeaffec
+#: ../../networking2.rst:4119
+msgid ""
+"A Site-to-Site VPN connection helps you establish a secure connection from "
+"an enterprise datacenter to the cloud infrastructure. This allows users to "
+"access the guest VMs by establishing a VPN connection to the virtual router "
+"of the account from a device in the datacenter of the enterprise. You can "
+"also establish a secure connection between two VPC setups or high "
+"availability zones in your environment. Having this facility eliminates the "
+"need to establish VPN connections to individual VMs."
+msgstr "一个站点到站点的VPN连接可以帮助你建立从云基础架构到企业内部数据中心的安全连接.这就允许一个账户从企业内部数据中心的设备连接到此账户启用VPN连接的虚拟路由器上, 从而通过VPN连接到该账户的虚拟机.你也可以在两个VPC之间或是高可用区域之间建立VPC以加强安全。这样一来，就不需要在虚拟机之间建立VPN连接的必要了。"
+
+# bcd63d9bd1044fcd99b0164249abc73b
+#: ../../networking2.rst:4128
+msgid ""
+"The difference from Remote VPN is that Site-to-site VPNs connects entire "
+"networks to each other, for example, connecting a branch office network to a"
+" company headquarters network. In a site-to-site VPN, hosts do not have VPN "
+"client software; they send and receive normal TCP/IP traffic through a VPN "
+"gateway."
+msgstr "与Remote VPN不同，Site-to-site VPNs是将两个网络相互连接。比如，将一个分支办公室的网络与总公司网络互联，Site-to-site VPN的两个主机不需要VPN客户端软件，它们通过VPN网关收发普通的TCP/IP数据包流量 。"
+
+# 00b0a4bc2c4642a1844c93fbefe3d0d4
+#: ../../networking2.rst:4134
+msgid "The supported endpoints on the remote datacenters are:"
+msgstr "目前支持的数据中心的终端设备是:"
+
+# 39b1debdf4a34a63a316d90993e9826d
+#: ../../networking2.rst:4138
+msgid "Cisco ISR with IOS 12.4 or later"
+msgstr "Cisco ISR IOS 12.4或更新"
+
+# e913039ba6aa428892f596416afe8630
+#: ../../networking2.rst:4142
+msgid "Juniper J-Series routers with JunOS 9.5 or later"
+msgstr "Juniper J-系统 路由器 JunOS 9.5 或更新版本"
+
+# 2e26cd40d2ed445d8929a3a0c02a5751
+#: ../../networking2.rst:4146
+msgid "CloudStack virtual routers"
+msgstr "CloudStack虚拟路由器。"
+
+# 049e25279dbc416c937b6fecf03e8e08
+#: ../../networking2.rst:4149
+msgid ""
+"In addition to the specific Cisco and Juniper devices listed above, the "
+"expectation is that any Cisco or Juniper device running on the supported "
+"operating systems are able to establish VPN connections."
+msgstr "除了上述指定的Cisco和Juniper设备, 所期望的是任何Cisco或Juniper的设备在支持的操作系统上都可以建立VPN连接."
+
+# e3328079c0ec42049907920ee99daf6e
+#: ../../networking2.rst:4153
+msgid "To set up a Site-to-Site VPN connection, perform the following:"
+msgstr "为了建立站点到站点的VPN连接, 需要执行以下步骤:"
+
+# 29a806dda94c425ab905caa5f7709805
+#: ../../networking2.rst:4157
+msgid "Create a Virtual Private Cloud (VPC)."
+msgstr "创建一个虚拟私有云(VPC)."
+
+# 7adc784ea1124f6f8fca7553c17ca916
+#: ../../networking2.rst:4159
+msgid "See \":ref:`configuring-vpc`\"."
+msgstr "参考\":ref:`configuring-vpc`\"."
+
+# 9649c39af37946ccbc1cba0e6b044fda
+#: ../../networking2.rst:4163
+msgid "Create a VPN Customer Gateway."
+msgstr "创建一个VPN客户网关."
+
+# 27873ddb52d14bef9f93d4c83fc88464
+#: ../../networking2.rst:4167
+msgid "Create a VPN gateway for the VPC that you created."
+msgstr "为你创建的VPC设定一个VPN网关."
+
+# 43ca7677d7b844209b1c70d588741934
+#: ../../networking2.rst:4171
+msgid ""
+"Create VPN connection from the VPC VPN gateway to the customer VPN gateway."
+msgstr "从VPC的VPN网关到客户的VPN网关建立VPN连接."
+
+# 232821d4f81947f1885a8e8355905d9d
+#: ../../networking2.rst:4175
+msgid "Creating and Updating a VPN Customer Gateway"
+msgstr "创建和更新一个VPN客户网关."
+
+# e0e6f58531f24a02852eb092cba35ff8
+#: ../../networking2.rst:4178
+msgid ""
+"A VPN customer gateway can be connected to only one VPN gateway at a time."
+msgstr "一个VPN客户网关在同一时间只能连接一个VPN网关。"
+
+# 95d554ca702946bca83b30c6adf6a445
+#: ../../networking2.rst:4180
+msgid "To add a VPN Customer Gateway:"
+msgstr "添加 VPN 客户网关"
+
+# 46009b4629e8480591e1052e0a368962
+# d92d044f9c1f417cb5166046b62ef99a
+#: ../../networking2.rst:4192 ../../networking2.rst:4337
+msgid "In the Select view, select VPN Customer Gateway."
+msgstr "在选择视图里，选择VPN客户网关。"
+
+# 5b578ba46d8f4757aaf5620e6f77b1dc
+#: ../../networking2.rst:4196
+msgid "Click Add VPN Customer Gateway."
+msgstr "点击添加 VPN 客户网关。"
+
+# c3fa00baefd74a0eab971c38b2e19251
+#: ../../networking2.rst:4198
+msgid "|addvpncustomergateway.png|"
+msgstr "|addvpncustomergateway.png|"
+
+# fd022a19e85d42918e285828af4c3698
+#: ../../networking2.rst:4204
+msgid "**Name**: A unique name for the VPN customer gateway you create."
+msgstr "**名称**: 你添加的VPN客户网关的一个唯一的名称。"
+
+# 33ddd28d37da46f38c17f701efbd46d1
+#: ../../networking2.rst:4208
+msgid "**Gateway**: The IP address for the remote gateway."
+msgstr "**IP地址**: 远端网关的IP地址。"
+
+# a29af3f7a7934e4d88f2cd38dd8f70a1
+#: ../../networking2.rst:4212
+msgid ""
+"**CIDR list**: The guest CIDR list of the remote subnets. Enter a CIDR or a "
+"comma-separated list of CIDRs. Ensure that a guest CIDR list is not "
+"overlapped with the VPC's CIDR, or another guest CIDR. The CIDR must be "
+"RFC1918-compliant."
+msgstr "**CIDR列表**: 远端客户子网的CIDR。输入一个CIDR或是以逗号分隔的多个CIDR。在确认客户的CIDR和VPC的CIDR或是另一个客户的CIDR不重叠冲突。CIDR的格式必须符合 RFC1918标准。"
+
+# 4fdaac9ee4004de68ddbea33d37d1e43
+#: ../../networking2.rst:4219
+msgid ""
+"**IPsec Preshared Key**: Preshared keying is a method where the endpoints of"
+" the VPN share a secret key. This key value is used to authenticate the "
+"customer gateway and the VPC VPN gateway to each other."
+msgstr "**IPsec预共享密钥**: 预共享密钥在两个端点之间共享同一个密钥。这个密钥用来在客户网关和VPN的VPN网关之间相互认证。"
+
+# 05946c6fb7bd4305bb2e20af004a01e3
+#: ../../networking2.rst:4225
+msgid ""
+"The IKE peers (VPN end points) authenticate each other by computing and "
+"sending a keyed hash of data that includes the Preshared key. If the "
+"receiving peer is able to create the same hash independently by using its "
+"Preshared key, it knows that both peers must share the same secret, thus "
+"authenticating the customer gateway."
+msgstr "Internet密钥交换协议（IKE）匹配点 ( VPN 端点 ) 通过计算并发送包含预共享密钥的哈希键值来进行相互验证。如果收接点通过自己的预共享密钥算出同一个键值的话，这就说明两个点是用的同一个密钥，相互之间认证通过，形成匹配。"
+
+# b56b82f20e33400d8c4b39ce0b55bab2
+#: ../../networking2.rst:4234
+msgid ""
+"**IKE Encryption**: The Internet Key Exchange (IKE) policy for phase-1. The "
+"supported encryption algorithms are AES128, AES192, AES256, and 3DES. "
+"Authentication is accomplished through the Preshared Keys."
+msgstr "**IKE 加密**: Internet密钥交换协议(IKE)第一阶段（phase-1）策略。支持的加密算法包括 AES128, AES192, AES256和3DES.。认证通过预共享密钥完成。"
+
+# bd7c468509ca4ad5840e115efaa7e1ca
+#: ../../networking2.rst:4240
+msgid ""
+"The phase-1 is the first phase in the IKE process. In this initial "
+"negotiation phase, the two VPN endpoints agree on the methods to be used to "
+"provide security for the underlying IP traffic. The phase-1 authenticates "
+"the two VPN gateways to each other, by confirming that the remote gateway "
+"has a matching Preshared Key."
+msgstr "phase-1是IKE过程的第一阶段。在这个开始的协商阶段，两个VPN端点在将底层IP流量加密安全的方法上取得一致。第一阶段认证通过的条件是：两个VPN网关之间使用的是同一个预定义密钥。"
+
+# 13e9c659a1764d4fba7fc6de838ff8b1
+#: ../../networking2.rst:4248
+msgid ""
+"**IKE Hash**: The IKE hash for phase-1. The supported hash algorithms are "
+"SHA1 and MD5."
+msgstr "**IKE 哈希**: IKE第一阶段（ phase-1）哈希散列使用的算法。支持SHA1 和 MD5."
+
+# 23efa859bff14bc69f132fda62399cbe
+#: ../../networking2.rst:4253
+msgid ""
+"**IKE DH**: A public-key cryptography protocol which allows two parties to "
+"establish a shared secret over an insecure communications channel. The "
+"1536-bit Diffie-Hellman group is used within IKE to establish session keys. "
+"The supported options are None, Group-5 (1536-bit) and Group-2 (1024-bit)."
+msgstr "**IKE DH（Diffie-Hellman组）**: IKE的DH加密协议，可以在不安全的连接上确保共享KEY的安全。1536位的DH组用在IKE中用来建立会话KEYS。在这里，支持的选项是 None, Group-5 (1536-bit) 和 Group-2 (1024-bit)."
+
+# 208ddb7be762449e9a6bb569f815f0ed
+#: ../../networking2.rst:4261
+msgid ""
+"**ESP Encryption**: Encapsulating Security Payload (ESP) algorithm within "
+"phase-2. The supported encryption algorithms are AES128, AES192, AES256, and"
+" 3DES."
+msgstr "**ESP 加密**: 封装安全有效负荷（Encapsulating Security Payload,ESP）算法是发生在第二阶段(phase-2)。其支持的加密算法包括 AES128, AES192, AES256, 和 3DES。"
+
+# b5dd17cc99c744d39b800b3df090e674
+#: ../../networking2.rst:4266
+msgid ""
+"The phase-2 is the second phase in the IKE process. The purpose of IKE "
+"phase-2 is to negotiate IPSec security associations (SA) to set up the IPSec"
+" tunnel. In phase-2, new keying material is extracted from the Diffie-"
+"Hellman key exchange in phase-1, to provide session keys to use in "
+"protecting the VPN data flow."
+msgstr "phase-2是IKE过程的第二阶段，其目标是协助IPSec安全关联 (SA) 以建立IPSec通道。在 phase-2阶段，会利用 phase-1阶段建立好的DH安全协议方法来交换新的密钥。"
+
+# 0b0d1207149646f7b20a26a97a43f2d2
+#: ../../networking2.rst:4274
+msgid ""
+"**ESP Hash**: Encapsulating Security Payload (ESP) hash for phase-2. "
+"Supported hash algorithms are SHA1 and MD5."
+msgstr "**ESP哈希散列**:phase-2支持的封装安全有效负荷(Encapsulating Security Payload,ESP)哈希算法包括：SHA1 和MD5."
+
+# 24ada2be8386490aafda31663e439f6f
+#: ../../networking2.rst:4279
+msgid ""
+"**Perfect Forward Secrecy**: Perfect Forward Secrecy (or PFS) is the "
+"property that ensures that a session key derived from a set of long-term "
+"public and private keys will not be compromised. This property enforces a "
+"new Diffie-Hellman key exchange. It provides the keying material that has "
+"greater key material life and thereby greater resistance to cryptographic "
+"attacks. The available options are None, Group-5 (1536-bit) and Group-2 "
+"(1024-bit). The security of the key exchanges increase as the DH groups grow"
+" larger, as does the time of the exchanges."
+msgstr "**Perfect forward secrecy(完全正向保密,PFS) **:PFS的性质是确保来自一组的长期的公共密钥和私人密钥之间的会话密钥不会妥协失效。PFS会促使一组新的DH KEY发生交换。这组新KEY具有更长的生命周期因此可以抵制更强大的功击。DH的可用选项是 None, Group-5 (1536-bit)和 Group-2 (1024-bit). 当新KEY交换之后，DH组会变得更大。"
+
+# 7070c64276df4df0bf10b79718192550
+#: ../../networking2.rst:4290
+msgid ""
+"When PFS is turned on, for every negotiation of a new phase-2 SA the two "
+"gateways must generate a new set of phase-1 keys. This adds an extra layer "
+"of protection that PFS adds, which ensures if the phase-2 SA's have expired,"
+" the keys used for new phase-2 SA's have not been generated from the current"
+" phase-1 keying material."
+msgstr "当PFS打开后，两个网关之间的新的phase-2 SA协商都会产生新的phase-1的一组KEY，这就会导致增加一个额外的层。这个层的作用是保证即使phase-2 SA失效过期，其KEY也不会由phase-1生成。"
+
+# 2ca89467ccc94df5a7bef6468f566b46
+#: ../../networking2.rst:4298
+msgid ""
+"**IKE Lifetime (seconds)**: The phase-1 lifetime of the security association"
+" in seconds. Default is 86400 seconds (1 day). Whenever the time expires, a "
+"new phase-1 exchange is performed."
+msgstr "*IKE 存活期(秒)**: SA的phase-1的存活期。默认是86400 秒 (1 天).当这个时间过了之后，会发生一次新的 phase-1 KEY交换。"
+
+# 8ca35ecaf59e42cfbef7fe98bfd8f264
+#: ../../networking2.rst:4304
+msgid ""
+"**ESP Lifetime (seconds)**: The phase-2 lifetime of the security association"
+" in seconds. Default is 3600 seconds (1 hour). Whenever the value is "
+"exceeded, a re-key is initiated to provide a new IPsec encryption and "
+"authentication session keys."
+msgstr "**ESP存活期 (秒)**:SA的 phase-2存活期。默认为 3600 秒(1 小时). 当过了这个时间之后，会有一个新的KEY初始化，用来加密和认证 IPsec的会话KEY。"
+
+# f5df9d75cd524b5b92d8c85cce626655
+#: ../../networking2.rst:4311
+msgid ""
+"**Dead Peer Detection**: A method to detect an unavailable Internet Key "
+"Exchange (IKE) peer. Select this option if you want the virtual router to "
+"query the liveliness of its IKE peer at regular intervals. It's recommended "
+"to have the same configuration of DPD on both side of VPN connection."
+msgstr "**死亡匹配点检测**:这是一种检测不可用IKE节点的方法。如果你希望虚拟路由器随时测试IKE节点的存活情况，选择了这个选项。 一般来说，最好在VPN连接的两端都同时配置DPD(Dead Peer Detectio)."
+
+# d5d1124c4e124407a611667296f6ffac
+#: ../../networking2.rst:4322
+msgid "Updating and Removing a VPN Customer Gateway"
+msgstr "更新和删除一个VPN客户网关."
+
+# 04bbad214e7c4a6884dbfa7b6367b57d
+#: ../../networking2.rst:4324
+msgid ""
+"You can update a customer gateway either with no VPN connection, or related "
+"VPN connection is in error state."
+msgstr "你可以更新一个客户网关：即可以从无到有新建一个VPN，或是将有错误提示的VPN改正。"
+
+# 1ab9886431a14731ae0c50e12a2203d6
+#: ../../networking2.rst:4341
+msgid "Select the VPN customer gateway you want to work with."
+msgstr "选择您要操作的客户VPN连接。"
+
+# ba453f5b81544287922dde81efcc590b
+#: ../../networking2.rst:4345
+msgid ""
+"To modify the required parameters, click the Edit VPN Customer Gateway "
+"button |edit-icon.png|"
+msgstr "如需要修改一些参数，点击编辑客户VPN网关按钮。|edit-icon.png|"
+
+# 46a97e97cc034e4e91727e4f784cc8b7
+#: ../../networking2.rst:4350
+msgid ""
+"To remove the VPN customer gateway, click the Delete VPN Customer Gateway "
+"button |delete.png|"
+msgstr "删除一个客户VPN网关，点击删除客户VPN网关按钮。 |delete.png|"
+
+# 60adfabe1723470599d91c8c7e4d173a
+#: ../../networking2.rst:4358
+msgid "Creating a VPN gateway for the VPC"
+msgstr "为VPC创建一个VPN网关"
+
+# 3500ca75a83147c19f1ed28777444c7d
+# a64efaea89b24d67a8e4d1e4d36d34eb
+# ce5b35fdd4964dd398d49233e31b5fcd
+# 67bc60dd8b6046558a097762240decf1
+# 6c5213a6e5524a83bd5c41c59f290442
+# f25b37649f5d4cd5b04a737641c79d73
+# 5b21b4e1cb1045269d9814e3cc029bd0
+#: ../../networking2.rst:4377 ../../networking2.rst:4473
+#: ../../networking2.rst:4665 ../../networking2.rst:5767
+#: ../../networking2.rst:5858 ../../networking2.rst:6037
+#: ../../networking2.rst:6674
+msgid ""
+"Click the Configure button of the VPC to which you want to deploy the VMs."
+msgstr "点击要部署虚机的VPC的配置按钮。"
+
+# e1358ecd8ab54314873c0775c0880f75
+# 19d3fa0227e84261bf1cd4663828636e
+# 4de39a3991db4dfc901c6279c5294ac2
+# 1a2f3ce6a491468ab7a3459fcdfe215a
+# 469af671796348f5b92558710d159c36
+# c11ffe7f7c0949189706c0df2f2ff581
+# 94a0dea0d2b04ba797bfe1f2164cac7b
+# 30b175b156724a81b03bd2d42e85a0a1
+#: ../../networking2.rst:4380 ../../networking2.rst:4476
+#: ../../networking2.rst:4668 ../../networking2.rst:5531
+#: ../../networking2.rst:5861 ../../networking2.rst:5948
+#: ../../networking2.rst:6040 ../../networking2.rst:6677
+msgid ""
+"The VPC page is displayed where all the tiers you created are listed in a "
+"diagram."
+msgstr "系统会显示VPC页面，您创建的所有层都列在图中。"
+
+# 795d87a7e4884bc9954978635c4a0ce3
+# bfc77b95ba024e828af5e01a0235044f
+# c412e8677d9f43bd91d874297d2a51b1
+#: ../../networking2.rst:4425 ../../networking2.rst:4525
+#: ../../networking2.rst:4717
+msgid "Select Site-to-Site VPN."
+msgstr "选择点对点VPN"
+
+# 8284273706754d38a31bf76d8261f3ed
+#: ../../networking2.rst:4427
+msgid ""
+"If you are creating the VPN gateway for the first time, selecting Site-to-"
+"Site VPN prompts you to create a VPN gateway."
+msgstr "如果您是第一次创建VPN网关，选择点对点VPN会提示您创建一个VPN网关。"
+
+# 9403ca5a182a46bea09047c00af73183
+#: ../../networking2.rst:4432
+msgid "In the confirmation dialog, click Yes to confirm."
+msgstr "在信息确认对话框，点击“是”。"
+
+# e4ae30f09bbb4771b8c6f422926370fd
+#: ../../networking2.rst:4434
+msgid ""
+"Within a few moments, the VPN gateway is created. You will be prompted to "
+"view the details of the VPN gateway you have created. Click Yes to confirm."
+msgstr "过一会儿，VPN网关就创建出来了。系统会提示您查看VPN网关的详细信息，请点击“是”。"
+
+# 92509e2b8fd34d06a5026dc84df93572
+#: ../../networking2.rst:4438
+msgid "The following details are displayed in the VPN Gateway page:"
+msgstr "VPN网关页面会显示以下详细信息："
+
+# 0d9b83c3c7c14ceb89902aa2acd77eef
+#: ../../networking2.rst:4446
+msgid "Account"
+msgstr "帐号"
+
+# de092a05c0cb4352a757a99ec8ec10cc
+#: ../../networking2.rst:4450
+msgid "Domain"
+msgstr "域名"
+
+# f9de76d1de924804aada31d4d335a636
+#: ../../networking2.rst:4453
+msgid "Creating a VPN Connection"
+msgstr "新建vpn连接"
+
+# 041a061561c240feb48418d06b345f9d
+#: ../../networking2.rst:4455
+msgid "CloudStack supports creating up to 8 VPN connections."
+msgstr "CloudStack最多支持建立8个VPN连接。"
+
+# c343d040bbf94652805f9913087df284
+#: ../../networking2.rst:4469
+msgid "All the VPCs that you create for the account are listed in the page."
+msgstr "页面上列出了该账号下所有的VPC。"
+
+# 6ab7b79bc9384d7e80adc871af997847
+# 49acb49a732346378816e6bb92cf285d
+# 02fa5743f59b45619d573323e28ba038
+#: ../../networking2.rst:4481 ../../networking2.rst:4673
+#: ../../networking2.rst:5536
+msgid "Click the Settings icon."
+msgstr "点击设置图标。"
+
+# fc6f5140f3c942dca23fcfd1ab68c6a7
+# 51c44ccda83c4464a1e80005c54790fc
+#: ../../networking2.rst:4527 ../../networking2.rst:4719
+msgid "The Site-to-Site VPN page is displayed."
+msgstr "系统会显示点对点VPN页面。"
+
+# 786eac580afe4c91a9f86515ed758789
+# 17b40c7b7853452ea96b30e63059db2c
+#: ../../networking2.rst:4531 ../../networking2.rst:4723
+msgid ""
+"From the Select View drop-down, ensure that VPN Connection is selected."
+msgstr "在选择视图下拉框，请确保选择VPN连接。"
+
+# 163923e5fc7e45a9b9022496845d5da4
+#: ../../networking2.rst:4536
+msgid "Click Create VPN Connection."
+msgstr "选择创建vpn连接按钮"
+
+# 3755699dc4ef4c60846d045f671bfcee
+#: ../../networking2.rst:4538
+msgid "The Create VPN Connection dialog is displayed:"
+msgstr "系统会显示创建VPN连接对话框："
+
+# 63e805ab6ce6420d97103dc7a20b5506
+#: ../../networking2.rst:4540
+msgid "|createvpnconnection.png|"
+msgstr "|createvpnconnection.png|"
+
+# e897f05865fe4bf3b6daee5504dcf357
+#: ../../networking2.rst:4544
+msgid "Select the desired customer gateway."
+msgstr "选择想要的用户网关。"
+
+# cc72f3e20e344c9f8e3202d92866c9ce
+#: ../../networking2.rst:4548
+msgid ""
+"Select Passive if you want to establish a connection between two VPC virtual"
+" routers."
+msgstr "如果你希望在两个VPC虚拟路由器之间建立连接，选择被动模式。"
+
+# b1e77d6e88094abc8f1efc7fc737c62a
+#: ../../networking2.rst:4551
+msgid ""
+"If you want to establish a connection between two VPC virtual routers, "
+"select Passive only on one of the VPC virtual routers, which waits for the "
+"other VPC virtual router to initiate the connection. Do not select Passive "
+"on the VPC virtual router that initiates the connection."
+msgstr "如果你希望在两个VPC虚拟路由器之间建立连接，需要等待另一个虚拟路由器来初始化连接，则只有其中一个虚拟器上选择被动模式。在这种情况下，不要在初始化连接的虚拟路由器上选择被动模式。"
+
+# e81cf6ee9dbe4cf8a512334ae708d8e0
+#: ../../networking2.rst:4561
+msgid "Within a few moments, the VPN Connection is displayed."
+msgstr "过一会儿，系统会显示该VPN连接。"
+
+# ceccd67800e84c5f86872fc8697f97d5
+#: ../../networking2.rst:4563
+msgid "The following information on the VPN connection is displayed:"
+msgstr "VPN连接信息"
+
+# d7d71c18469c485d9cf0c62d4e18ee44
+#: ../../networking2.rst:4575
+msgid "State"
+msgstr "状态 "
+
+# 7e17d8eed6e64a6bb98dfcc6688f7011
+#: ../../networking2.rst:4579
+msgid "IPSec Preshared Key"
+msgstr "IPSec 预共享密钥"
+
+# 7698868ecfe742709ac2201b3c176a62
+#: ../../networking2.rst:4583
+msgid "IKE Policy"
+msgstr "IKE策略"
+
+# f8b615756067468c82c8cc29bd97d4f6
+#: ../../networking2.rst:4587
+msgid "ESP Policy"
+msgstr "ESP策略"
+
+# 2885f5a0b00e4f45bac61fa489576241
+#: ../../networking2.rst:4590
+msgid "Site-to-Site VPN Connection Between VPC Networks"
+msgstr "在VPC网络之间的站点的VPN连接"
+
+# cffe70c20ec8443a93e09b3c742a055b
+#: ../../networking2.rst:4592
+msgid ""
+"CloudStack provides you with the ability to establish a site-to-site VPN "
+"connection between CloudStack virtual routers. To achieve that, add a "
+"passive mode Site-to-Site VPN. With this functionality, users can deploy "
+"applications in multiple Availability Zones or VPCs, which can communicate "
+"with each other by using a secure Site-to-Site VPN Tunnel."
+msgstr "CloudStack可以在虚拟路由器之间部署站点到站点的VPN连接，这需要添加一个被动模式的站点到站点VPN。有了这个功能之后，用户就可以在多个区域或VPC之间通过安全的VPN通道互联。"
+
+# 1a50c272367a482fb9fb4939f3e4baa1
+#: ../../networking2.rst:4598
+msgid "This feature is supported on all the hypervisors."
+msgstr "这个特性支持所有类型的HYPERVISOR."
+
+# 2f0c1484f8594418b1f21b468680914a
+#: ../../networking2.rst:4602
+msgid "Create two VPCs. For example, VPC A and VPC B."
+msgstr "创建两个VPC。比如，VPC A和VPC B。"
+
+# 2db40aa80b84423f9d304bb0b3745676
+#: ../../networking2.rst:4604
+msgid "For more information, see \":ref:`configuring-vpc`\"."
+msgstr "更多信息，参考\":ref:`configuring-vpc`\"."
+
+# 8cbc2e0b316a42489765523577ab7e6a
+#: ../../networking2.rst:4608
+msgid "Create VPN gateways on both the VPCs you created."
+msgstr "在创建的VPC两边都添加VPN网关。"
+
+# c68bd6435db949d791a0372688848f1a
+#: ../../networking2.rst:4610
+msgid ""
+"For more information, see `\"Creating a VPN gateway for the VPC\" "
+"<#creating-a-vpn-gateway-for-the-vpc>`_."
+msgstr "更多信息，参考 `\"为VPC创建VPN网关\" <#creating-a-vpn-gateway-for-the-vpc>`_."
+
+# f8b154e601404d4abdd3a9a4e6374500
+#: ../../networking2.rst:4615
+msgid "Create VPN customer gateway for both the VPCs."
+msgstr "在VPC两边都创建VPN客户网关。"
+
+# 7e4fb977595840019e437c0884f0a8f1
+#: ../../networking2.rst:4617
+msgid ""
+"For more information, see `\"Creating and Updating a VPN Customer Gateway\" "
+"<#creating-and-updating-a-vpn-customer-gateway>`_."
+msgstr "更多信息，参考`\"创建和更新VPN客户网关\" <#creating-and-updating-a-vpn-customer-gateway>`_."
+
+# ade608d3a3ea45829af36e650cd98e47
+#: ../../networking2.rst:4622
+msgid "Enable a VPN connection on VPC A in passive mode."
+msgstr "在VPC A这边启用VPN的被动连接模式。"
+
+# 7a5159ba5d354f659fa0b9c6291f9413
+#: ../../networking2.rst:4624
+msgid ""
+"For more information, see `\"Creating a VPN Connection\" <#creating-a-vpn-"
+"connection>`_."
+msgstr "更多信息，请参阅 `\"创建VPN连接\" <#creating-a-vpn-connection>`_。"
+
+# 17674753d913496ea042cb7c2039383f
+#: ../../networking2.rst:4627
+msgid ""
+"Ensure that the customer gateway is pointed to VPC B. The VPN connection is "
+"shown in the Disconnected state."
+msgstr "确保客户网关指向VPC B。这个VPN当前显示的是未连接状态。"
+
+# d8feab6deab8404a9912bb7ea7882511
+#: ../../networking2.rst:4632
+msgid "Enable a VPN connection on VPC B."
+msgstr "在VPC B上启用VPN连接。"
+
+# 9234f47ff9fb4a4a86a85bcc6d518287
+#: ../../networking2.rst:4634
+msgid ""
+"Ensure that the customer gateway is pointed to VPC A. Because virtual router"
+" of VPC A, in this case, is in passive mode and is waiting for the virtual "
+"router of VPC B to initiate the connection, VPC B virtual router should not "
+"be in passive mode."
+msgstr "确保客户网关指向VPC A。在这个示例里，因为VPC A的虚拟路由器是处于被动模式且等待着VPC B进行初始化连接，所以VPC B的虚拟路由器不要设置为被动模式。"
+
+# 85d2c38cd2d0427a833207d6c3b42087
+#: ../../networking2.rst:4639
+msgid "The VPN connection is shown in the Disconnected state."
+msgstr "VPN连接当前显示为未连接状态。"
+
+# 6a7541ea6fa1406eacf4db796e79ef64
+#: ../../networking2.rst:4641
+msgid ""
+"Creating VPN connection on both the VPCs initiates a VPN connection. Wait "
+"for few seconds. The default is 30 seconds for both the VPN connections to "
+"show the Connected state."
+msgstr "VPC两边的VPN会进行初始化连接。默认为30秒之后，两边VPN都会显示为已连接状态。"
+
+# 894d44a883c248778d9598ba46e3f27f
+#: ../../networking2.rst:4646
+msgid "Restarting and Removing a VPN Connection"
+msgstr "VPN连接的重启和删除"
+
+# 83fe3a90f3094225aecb250153297a3d
+#: ../../networking2.rst:4726
+msgid "All the VPN connections you created are displayed."
+msgstr "系统会显示创建VPN连接对话框："
+
+# b94b1fdaf1c844a28ccf4863998d8635
+#: ../../networking2.rst:4730
+msgid "Select the VPN connection you want to work with."
+msgstr "选择您要操作的VPN连接。"
+
+# a9f2559596ff44e281d29137f23566ef
+#: ../../networking2.rst:4732
+msgid "The Details tab is displayed."
+msgstr "系统显示详细信息页。"
+
+# a233c3b9788d41f38eb802e1f9d989c9
+#: ../../networking2.rst:4736
+msgid ""
+"To remove a VPN connection, click the Delete VPN connection button |remove-"
+"vpn.png|"
+msgstr "删除一个VPN连接，点击删除VPN连接按钮。 |remove-vpn.png|"
+
+# 41b780de0b934756a92a9ca0269e75e5
+#: ../../networking2.rst:4739
+msgid ""
+"To restart a VPN connection, click the Reset VPN connection button present "
+"in the Details tab. |reset-vpn.png|"
+msgstr "要重启VPN连接，请点击详细信息页的重置VPN连接按钮。 |reset-vpn.png|"
+
+# 183bb10ab504444faae13d81f2319f23
+#: ../../networking2.rst:4743
+msgid "About Inter-VLAN Routing (nTier Apps)"
+msgstr "关于vlan间路由(多层应用)"
+
+# 13ccb675390f4150acd57078694a88dd
+#: ../../networking2.rst:4745
+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 the VMs. In effect, "
+"you can segment VMs by means of VLANs into different networks that can host "
+"multi-tier applications, such as Web, Application, or Database. Such "
+"segmentation by means of VLANs logically separate application VMs for higher"
+" security and lower broadcasts, while remaining physically connected to the "
+"same device."
+msgstr "vlan间路由(多层应用)提供了在vlan间通过流量路由的功能。这个特性使你能够j建立私有云(vpc)，独立分割的云，可容纳多层应用程序。这些层被部署在不同的VLAN，可以互相沟通。您提供的VLAN层的创建和部署虚拟机可以在不同的层上。VLAN连接到一个虚拟路由器，这有利于虚拟机之间的通信。实际上，你可以通过不同定义的vlan来分割你的虚拟机到不同网络，以便承担多层应用，如Web，应用程序或数据库的虚拟机。通过VLAN的逻辑上独立的应用程序的虚拟具有较高的安全性和较低的广播，同时任然物理连接到同一设备。"
+
+# 8e00b9f53dfe4448b8fe2664f0725c1e
+#: ../../networking2.rst:4758
+msgid "This feature is supported on XenServer, KVM, and VMware hypervisors."
+msgstr "在 XenServer ,KVM和 VMware hypervisors支持这个特性"
+
+# cf6ee1a9b0f24cf2b239f5c5ee3e1ccb
+#: ../../networking2.rst:4760
+msgid "The major advantages are:"
+msgstr "主要的优势为："
+
+# 9914db80271c45879b3763424ebbbe4e
+#: ../../networking2.rst:4764
+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 "管理可以部署一个vlans集，同时运行用户部署虚拟机在这些vlan上。从预先指定的vlan集中随机的为租户分配一个来宾vlan.租户处于同一层的所有vm处于分配给这个租户的来宾vlan."
+
+# 7c49b6960b3e4fe98267c66963d07a32
+#: ../../networking2.rst:4770
+msgid ""
+"A VLAN allocated for an account cannot be shared between multiple accounts."
+msgstr "一个租户分配到的vlan不能被多个租户共享"
+
+# 079fa9b5868843beb9ef64f20fd14208
+#: ../../networking2.rst:4774
+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 "管理员允许所有用户创建自己的vpc,并部署应用。这个场景中，租户的虚拟机被部署到改租户的分配到的vlan中"
+
+# cdc5e1a97e7347ed92c034645cf61bb8
+#: ../../networking2.rst:4780
+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 "管理员和用户都可以创建多个vpcs.当第一个虚拟机被部署到该层时候，一个来宾网络nic插入到这个vpc虚拟路由器上"
+
+# b939e06705db41289dc97594160ccd4b
+#: ../../networking2.rst:4786
+msgid ""
+"The administrator can create the following gateways to send to or receive "
+"traffic from the VMs:"
+msgstr "管理员创建网关用接受和发送来自vm的流量："
+
+# 3f3d39b2a9544b7dbe578450c863c442
+#: ../../networking2.rst:4791
+msgid ""
+"**VPN Gateway**: For more information, see `\"Creating a VPN gateway for the"
+" VPC\" <#creating-a-vpn-gateway-for-the-vpc>`_."
+msgstr "**VPN网关**:更多信息，参考 `\"为VPC创建VPN网关\" <#creating-a-vpn-gateway-for-the-vpc>`_."
+
+# 563958c0c69e44a79fb209179e6f5ef8
+#: ../../networking2.rst:4796
+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 "**公网网关**：当为vpc创建一个虚拟路由器时，这个vpc的公共网关就添加到虚拟路由器当中。公共网关还没有暴露到最终用户。你不允许其列出，也不允许建立任何静态路由。"
+
+# 1178d5307b4a4df3b4982bb2985004e1
+#: ../../networking2.rst:4803
+msgid ""
+"**Private Gateway**: For more information, see \":ref:`adding-priv-gw-"
+"vpc`\"."
+msgstr "**私有网关**: 更多信息，参考 \":ref:`adding-priv-gw-vpc`\"."
+
+# c652b274f1d44ceebe3ea04ee8beb31c
+#: ../../networking2.rst:4807
+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 "管理员和用户可以创建各种可能的目的地的网关组合。但是，在部署中每种类型只能有一个网关。"
+
+# 5d134a3e16ec432a972f90fb955629c9
+#: ../../networking2.rst:4811
+msgid "For example:"
+msgstr "例如："
+
+# 47a88da418a64634b2908fb3999fec58
+#: ../../networking2.rst:4815
+msgid ""
+"**VLANs and Public Gateway**: For example, an application is deployed in the"
+" cloud, and the Web application VMs communicate with the Internet."
+msgstr "**VLAN和公网网关**: 比如，在云中部署了一个应用，并且这个web应用所在的虚拟机要和因特网通信。"
+
+# e5054d8177ff4ecd817c1e9b50370893
+#: ../../networking2.rst:4821
+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 "**VLANs, VPN网关和公网网关**: 比如, 云中部署了一个应用;部署这个web应用的虚拟机要和因特网通信; 并且数据库虚拟要个先前提到的设备通信"
+
+# 9cf8b80f8da6486e8a190779839a52af
+#: ../../networking2.rst:4828
+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 "管理员可以在虚拟路由器定义一个访问控制列表(ACL)用于过滤vlan或者因特网和vlan直接的流量。你可定义基于CIDR,端口范围，协议，类型代码(如果选用ICPM协议)和进出流量的acl"
+
+# f03fcc7d11a24d6d9058d56e0690ee72
+#: ../../networking2.rst:4834
+msgid ""
+"The following figure shows the possible deployment scenarios of a Inter-VLAN"
+" setup:"
+msgstr "下图显示了可能的部署一个VLAN间的场景设置的："
+
+# 8da1d43a48f54d3cadd9a2ab40446452
+#: ../../networking2.rst:4837
+msgid "|mutltier.png|"
+msgstr "|mutltier.png|"
+
+# b5b5c31e4e374e9c80fbb2bb5d5178cd
+#: ../../networking2.rst:4839
+msgid ""
+"To set up a multi-tier Inter-VLAN deployment, see \":ref:`configuring-"
+"vpc`\"."
+msgstr "要建立一个多层次的跨VLAN部署，请参考\":ref:`configuring-vpc`\"."
+
+# 019f7c2e7a1c40289e074fc89915b010
+#: ../../networking2.rst:4844
+msgid "Configuring a Virtual Private Cloud"
+msgstr "配置一个虚拟私有云（VPC）"
+
+# cf430774172c4664b8c8126dc2f8f2a9
+#: ../../networking2.rst:4847
+msgid "About Virtual Private Clouds"
+msgstr "关于虚拟私有云（VPC）"
+
+# 06c06ce2f5fe4b2e8a3464b3c4becf6a
+#: ../../networking2.rst:4849
+msgid ""
+"CloudStack Virtual Private Cloud is a private, isolated part of CloudStack. "
+"A VPC can have its own virtual network topology that resembles a traditional"
+" physical network. You can launch VMs in the virtual network that can have "
+"private addresses in the range of your choice, for example: 10.0.0.0/16. You"
+" can define network tiers within your VPC network range, which in turn "
+"enables you to group similar kinds of instances based on IP address range."
+msgstr "CloudStackVPC是CloudStack云中私有并隔离的部分。一个VPC可以使用自己的虚拟网络拓扑来组建传统物理网络。在这个虚拟网络中，您创建的虚机的私网地址可以由您自主选择IP范围，例如10.0.0.0/16。您可以在VPC网络范围内定义多个网络层，这些层可以让你将类似的虚机按IP地址范围分组。"
+
+# 46308016994049eb85cdc73e86db616e
+#: ../../networking2.rst:4857
+msgid ""
+"For example, if a VPC has the private range 10.0.0.0/16, its guest networks "
+"can have the network ranges 10.0.1.0/24, 10.0.2.0/24, 10.0.3.0/24, and so "
+"on."
+msgstr "例如：一个VPC的私有地址范围是10.0.0.0/16，其中的用户网络的地址范围可以分别是10.0.1.0/24、10.0.2.0/24、10.0.3.0/24等等。"
+
+# ef383bc8b7d54a0785f2b4828b5290ee
+#: ../../networking2.rst:4862
+msgid "Major Components of a VPC:"
+msgstr "VPC的主要组件："
+
+# b90235f5e79947b7a57dee0d5c08e244
+#: ../../networking2.rst:4864
+msgid "A VPC is comprised of the following network components:"
+msgstr "VPC主要由以下网络组件构成："
+
+# 9a373d73d3ae48309685ddecb2399f89
+#: ../../networking2.rst:4868
+msgid ""
+"**VPC**: A VPC acts as a container for multiple isolated networks that can "
+"communicate with each other via its virtual router."
+msgstr "**VPC**：一个VPC是多个隔离网络的容器，隔离网络间可以通过VPC的虚拟路由器互通。"
+
+# 4d1cc64429d44838942ce9d9290d09f6
+#: ../../networking2.rst:4873
+msgid ""
+"**Network Tiers**: Each tier acts as an isolated network with its own VLANs "
+"and CIDR list, where you can place groups of resources, such as VMs. The "
+"tiers are segmented by means of VLANs. The NIC of each tier acts as its "
+"gateway."
+msgstr "**网络层**：每个层是一个拥有各自VLAN和CIDR的隔离网络。您可以在层内放置VM等各种资源组。层与层之间通过VLAN方式隔离。VPC虚拟路由器在每个层中的网卡是该层的网关。"
+
+# 4e202e5460e24d838d858dc82fd70fee
+#: ../../networking2.rst:4880
+msgid ""
+"**Virtual Router**: A virtual router is automatically created and started "
+"when you create a VPC. The virtual router connect the tiers and direct "
+"traffic among the public gateway, the VPN gateways, and the NAT instances. "
+"For each tier, a corresponding NIC and IP exist in the virtual router. The "
+"virtual router provides DNS and DHCP services through its IP."
+msgstr "**虚拟路由器**：创建VPC时会自动创建并启动一个虚拟路由器。该虚拟路由器连接了各层，并负责各层与公网网关、VPN网关和NAT实例间的网络流量。对于每个层，该虚拟路由器都会有对应的网卡和IP，并通过该IP提供DNS和DHCP服务。"
+
+# 5620f9a835ae40ac9f844be5648dafad
+#: ../../networking2.rst:4889
+msgid ""
+"**Public Gateway**: The traffic to and from the Internet routed to the VPC "
+"through the public gateway. In a VPC, the public gateway is not exposed to "
+"the end user; therefore, static routes are not support for the public "
+"gateway."
+msgstr "**公网网关**：VPC进出互联网的流量会走公网网关。VPC中的公网网关不暴露给最终用户，因此公网网关上不支持静态路由。"
+
+# c72e1f296d024bf6a636137059d31752
+#: ../../networking2.rst:4896
+msgid ""
+"**Private Gateway**: All the traffic to and from a private network routed to"
+" the VPC through the private gateway. For more information, see \":ref"
+":`adding-priv-gw-vpc`\"."
+msgstr "**私有网关**：VPC进出某个私有网络的流量通过私有网关。更多信息，请查阅 \":ref:`adding-priv-gw-vpc`\"."
+
+# 741b3998454f43bbad3608dd86a74114
+#: ../../networking2.rst:4902
+msgid "**VPN Gateway**: The VPC side of a VPN connection."
+msgstr "**VPN 网关**：VPN连接的VPC端。"
+
+# 6487d4f72da84801ae40e38bcb8f7458
+#: ../../networking2.rst:4906
+msgid ""
+"**Site-to-Site VPN Connection**: A hardware-based VPN connection between "
+"your VPC and your datacenter, home network, or co-location facility. For "
+"more information, see \":ref:`setting-s2s-vpn-conn`\"."
+msgstr "**点对点VPN连接**：您的VPC和您的数据中心、家庭网络、主机托管设施之间基于硬件的VPN连接。更多信息，请参考\":ref:`setting-s2s-vpn-conn`\"."
+
+# d4b8df91ae5d4307835174a0c96640f1
+#: ../../networking2.rst:4912
+msgid ""
+"**Customer Gateway**: The customer side of a VPN Connection. For more "
+"information, see `\"Creating and Updating a VPN Customer Gateway\" "
+"<#creating-and-updating-a-vpn-customer-gateway>`_."
+msgstr "**客户网关**:客户这边的VPN连接。更多信息，请参考 `\"创建和更新VPN客户网关\" <#creating-and-updating-a-vpn-customer-gateway>`_."
+
+# f97a3ebbcde34d3a82a37aa401487760
+#: ../../networking2.rst:4918
+msgid ""
+"**NAT Instance**: An instance that provides Port Address Translation for "
+"instances to access the Internet via the public gateway. For more "
+"information, see \":ref:`enabling-disabling-static-nat-on-vpc`\"."
+msgstr "**NAT实例**:在用户虚机通过公网网关访问公网时，提供端口地址转换的实例。关于更多信息，请参考 \":ref:`enabling-disabling-static-nat-on-vpc`\"."
+
+# 0e9442c446e34500a845a7dff022554d
+#: ../../networking2.rst:4924
+msgid ""
+"**Network ACL**: Network ACL is a group of Network ACL items. Network ACL "
+"items are nothing but numbered rules that are evaluated in order, starting "
+"with the lowest numbered rule. These rules determine whether traffic is "
+"allowed in or out of any tier associated with the network ACL. For more "
+"information, see \":ref:`conf-net-acl`\"."
+msgstr "**网络ACL**: 网络ACL是一组网络访问控制列表。这些列表就是一个按顺序编号的规则，执行的时候，从最小的编号开始。这些规则决定了与此ACL关联的各个层的进出流量会被允许或阻止。更多信息，请参考 \":ref:`conf-net-acl`\"."
+
+# daf38611958e42f7b832673319b348fb
+#: ../../networking2.rst:4931
+msgid "Network Architecture in a VPC"
+msgstr "VPC的网络架构"
+
+# cc60b077b9ff4de19f842b6afab2e62b
+#: ../../networking2.rst:4933
+msgid ""
+"In a VPC, the following four basic options of network architectures are "
+"present:"
+msgstr "VPC有以下四个基本的网络架构："
+
+# f1eb7bb1a38f4dc68def9d12e7a3e178
+#: ../../networking2.rst:4938
+msgid "VPC with a public gateway only"
+msgstr "只有一个公网网关的VPC"
+
+# b0e2f221d7b14320bbc1222a776de41f
+#: ../../networking2.rst:4942
+msgid "VPC with public and private gateways"
+msgstr "VPC的公有和私有网关"
+
+# 0994c597eccb4d299d4dc9b107fb9fa7
+#: ../../networking2.rst:4946
+msgid "VPC with public and private gateways and site-to-site VPN access"
+msgstr "VPC的公有和私有网关以及site-to-site VPN访问"
+
+# 870f363e446c47b4b668cb236c51be3b
+#: ../../networking2.rst:4950
+msgid "VPC with a private gateway only and site-to-site VPN access"
+msgstr "只有私有网关的VPC以及site-to-site VPN访问"
+
+# 0875278053ce4aa7a964657f5ef7ca92
+#: ../../networking2.rst:4953
+msgid "Connectivity Options for a VPC"
+msgstr "VPC的连接选择"
+
+# 5d9bd85e540b4cd89292060896221da5
+#: ../../networking2.rst:4955
+msgid "You can connect your VPC to:"
+msgstr "你可以连接你的VPC："
+
+# d4a48f7eedb24cd0ada3d40f216fd98e
+#: ../../networking2.rst:4959
+msgid "The Internet through the public gateway."
+msgstr "通过公有网关连接到Internet."
+
+# 24471a284e4241e0bd0c5c456168c7a8
+#: ../../networking2.rst:4963
+msgid ""
+"The corporate datacenter by using a site-to-site VPN connection through the "
+"VPN gateway."
+msgstr "通过site-to-siteVPN网关连接到相邻数据中心。"
+
+# 25fc02e4454849d4a573bd5dd0d7449a
+#: ../../networking2.rst:4968
+msgid ""
+"Both the Internet and your corporate datacenter by using both the public "
+"gateway and a VPN gateway."
+msgstr "通过公有和私有VPN网关同时连接到Internet和相邻数据中心。"
+
+# de5ded73de514bd5a57ecb362fc2faff
+#: ../../networking2.rst:4972
+msgid "VPC Network Considerations"
+msgstr "VPC网络的考虑事项"
+
+# 78994af1e78348c9ba1f4b1565241a38
+#: ../../networking2.rst:4974
+msgid "Consider the following before you create a VPC:"
+msgstr "在创建VPC之前，确认以下事项："
+
+# cb564008696f42c493ba11e1ed4f80dc
+#: ../../networking2.rst:4978
+msgid "A VPC, by default, is created in the enabled state."
+msgstr "在创建好VPC之后，其默认处于启用状态。"
+
+# 000ae42b46f34e98836dd0ae06ce491f
+#: ../../networking2.rst:4982
+msgid ""
+"A VPC can be created in Advance zone only, and can't belong to more than one"
+" zone at a time."
+msgstr "只能在高级区域中创建VPC，并且VPC只能属于一个区域。"
+
+# 057235f5ffdf462bb0c747d2d3069fe8
+#: ../../networking2.rst:4987
+msgid ""
+"The default number of VPCs an account can create is 20. However, you can "
+"change it by using the max.account.vpcs global parameter, which controls the"
+" maximum number of VPCs an account is allowed to create."
+msgstr "默认VPC的数量是20个。如果你需要更多的VPC的话，可以通过修改max.account.vpcs这个全局参数。这个参数是控制创建VPC的最大数量的。"
+
+# 6356075be5b54a679178f3b08844bb13
+#: ../../networking2.rst:4993
+msgid ""
+"The default number of tiers an account can create within a VPC is 3. You can"
+" configure this number by using the vpc.max.networks parameter."
+msgstr "默认一个用户能创建VPC的层数是三层。也可以通过vpc.max.networks这个参数修改。"
+
+# 14ee39b30ff7411188721f6d19152415
+#: ../../networking2.rst:4999
+msgid ""
+"Each tier should have an unique CIDR in the VPC. Ensure that the tier's CIDR"
+" should be within the VPC CIDR range."
+msgstr "VPC中每一层都需要是唯一的CIDR，并且这个CIDR是在VPC的CIDR的范围之内。"
+
+# 227b4656e25549c3ae49cbd3eadee4da
+#: ../../networking2.rst:5004
+msgid "A tier belongs to only one VPC."
+msgstr "每一层只能属于一个VPC。"
+
+# 8c1c0a2daf2f454daf51a743c52d1875
+#: ../../networking2.rst:5008
+msgid "All network tiers inside the VPC should belong to the same account."
+msgstr "VPC中所有网络层都应属于同一个帐号。"
+
+# 151ef843569c413592482f23408cc0b1
+#: ../../networking2.rst:5012
+msgid ""
+"When a VPC is created, by default, a SourceNAT IP is allocated to it. The "
+"Source NAT IP is released only when the VPC is removed."
+msgstr "当VPC创建好之后，默认会分配好SourceNAT IP。当此VPC删除之后，SourceNAT IP也会被释放。"
+
+# a4dbf6325246473c80fa288a2c05f46f
+#: ../../networking2.rst:5017
+msgid ""
+"A public IP can be used for only one purpose at a time. If the IP is a "
+"sourceNAT, it cannot be used for StaticNAT or port forwarding."
+msgstr "一个公网IP只能用一个用途。如果此IP用于SourceNAT作用的话，就不能同时再用作StaticNAT 或端口转发。"
+
+# 66e9af0df38d44acbdfd5b4f7c7f2209
+#: ../../networking2.rst:5022
+msgid ""
+"The instances can only have a private IP address that you provision. To "
+"communicate with the Internet, enable NAT to an instance that you launch in "
+"your VPC."
+msgstr "一个实例只能有一个私有IP地址，为了访问Internet,你可以为VPC里的此实例启用NAT功能。"
+
+# a7fc2cd6204b4ccdb272b79d22b93120
+#: ../../networking2.rst:5028
+msgid ""
+"Only new networks can be added to a VPC. The maximum number of networks per "
+"VPC is limited by the value you specify in the vpc.max.networks parameter. "
+"The default value is three."
+msgstr "只有新的网络才能加入VPC。每一个VPC的最大网络数量由参数vpc.max.networks指定。其默认值为3."
+
+# 636571d03b1244af968495ed107bce4f
+#: ../../networking2.rst:5034
+msgid ""
+"The load balancing service can be supported by only one tier inside the VPC."
+msgstr "VPC中只有一层支持负载均衡服务。"
+
+# 690bdd20a5e449298f4d89ca8d62c663
+#: ../../networking2.rst:5039
+msgid "If an IP address is assigned to a tier:"
+msgstr "如果一个IP地址被赋予一个网络层："
+
+# 58b11a4dc63949a7a3052e4aa24933d5
+#: ../../networking2.rst:5043
+msgid ""
+"That IP can't be used by more than one tier at a time in the VPC. For "
+"example, if you have tiers A and B, and a public IP1, you can create a port "
+"forwarding rule by using the IP either for A or B, but not for both."
+msgstr "那么这个IP就不能在VPC里被另外的层所使用。比如：如果你有A层和B层以及一个公网IP地址，则你可以为A或B创建一个端口转发规则，但不能同时在A和B上创建。"
+
+# 856f012d37d643d8804e106bcbfc20f7
+#: ../../networking2.rst:5050
+msgid ""
+"That IP can't be used for StaticNAT, load balancing, or port forwarding "
+"rules for another guest network inside the VPC."
+msgstr "那个IP也不能在VPC的其它的客户网络里用作StaticNAT,负载均衡，端口转发规则。"
+
+# 4683db25b3ea4e4188deea16746ee8e9
+#: ../../networking2.rst:5055
+msgid "Remote access VPN is not supported in VPC networks."
+msgstr "VPC网络不支持Remote access VPN。"
+
+# d6e7cab15dfe4412bd18e44c210098b5
+#: ../../networking2.rst:5058
+msgid "Adding a Virtual Private Cloud"
+msgstr "添加一个VPC"
+
+# aebf60ad9d2040f5a4693f4948d8ee9f
+#: ../../networking2.rst:5060
+msgid ""
+"When creating the VPC, you simply provide the zone and a set of IP addresses"
+" for the VPC network address space. You specify this set of addresses in the"
+" form of a Classless Inter-Domain Routing (CIDR) block."
+msgstr "当创建VPC时，你只需要提供区域名和VPC要使用的一组IP地址。这组IP地址是以CIDR块的形式提供。"
+
+# e96c8770c7a94c51a0e5abf05e27349d
+#: ../../networking2.rst:5078
+msgid "Click Add VPC. The Add VPC page is displayed as follows:"
+msgstr "点击添加VPC按钮。页面呈现以下："
+
+# 5c49f3b134ab451fb0baebec74eb6d02
+#: ../../networking2.rst:5080
+msgid "|add-vpc.png|"
+msgstr "|add-vpc.png|"
+
+# fa0553b67cec41e993031eaa2cfdaf13
+#: ../../networking2.rst:5086
+msgid "**Name**: A short name for the VPC that you are creating."
+msgstr "**名称**: 要创建的VPC的名称。"
+
+# 97f59ddee9cd4c10bc7c6f87d980837a
+#: ../../networking2.rst:5090
+msgid "**Description**: A brief description of the VPC."
+msgstr "**描述**: 关于此VPC的简短描述."
+
+# fb51bf0a8fcf42bf90044a947eeb19d5
+#: ../../networking2.rst:5094
+msgid "**Zone**: Choose the zone where you want the VPC to be available."
+msgstr "**区域**: 你希望将此VPN应用在哪个区域中。"
+
+# d7698df9efa0453db3df61a65907f84e
+#: ../../networking2.rst:5098
+msgid ""
+"**Super CIDR for Guest Networks**: Defines the CIDR range for all the tiers "
+"(guest networks) within a VPC. When you create a tier, ensure that its CIDR "
+"is within the Super CIDR value you enter. The CIDR must be RFC1918 "
+"compliant."
+msgstr "**客户网络超级CIDR**: 定义一个VPC内所有层（客户网络）的CIDR范围。当你新创建一个层时，这个层的CIDR必须在这个超级CIDR范围之内。CIDR的格式定义必须符合RFC1918。"
+
+# 927e8a069df94b7ab7c15ce7c08682f2
+#: ../../networking2.rst:5105
+msgid ""
+"**DNS domain for Guest Networks**: If you want to assign a special domain "
+"name, specify the DNS suffix. This parameter is applied to all the tiers "
+"within the VPC. That implies, all the tiers you create in the VPC belong to "
+"the same DNS domain. If the parameter is not specified, a DNS domain name is"
+" generated automatically."
+msgstr "**客户网络的DNS域名**: 如果你需要一个域名，则需要在此指定域名后缀。这个参数会应用到VPC中所有的层中。这表示，VPC中所有的层都属于同一个域。如果没有指定域名，则域名会由系统随机产生。"
+
+# db3617bea0a7437a98e0ceb8acf7525b
+#: ../../networking2.rst:5113
+msgid ""
+"**Public Load Balancer Provider**: You have two options: VPC Virtual Router "
+"and Netscaler."
+msgstr "**公共负载均衡提供者**: 有两个选项：VPC虚拟路由器和 Netscaler。"
+
+# 4cfebf8fa1714d45b8ad960ae9f7ab29
+#: ../../networking2.rst:5121
+msgid "Adding Tiers"
+msgstr "添加层"
+
+# c329d2c258cc49dba5536840ef027842
+#: ../../networking2.rst:5123
+msgid ""
+"Tiers are distinct locations within a VPC that act as isolated networks, "
+"which do not have access to other tiers by default. Tiers are set up on "
+"different VLANs that can communicate with each other by using a virtual "
+"router. Tiers provide inexpensive, low latency network connectivity to other"
+" tiers within the VPC."
+msgstr "层在VPC里起来隔离网络的作用，默认规则是层之间不能互访。不同VLAN之间的层可以通过虚拟机实现连接。层在VPC内部提供一种廉价，低延迟的网络连接。"
+
+# 28ee0841ce014e79a7a281d4bb216ebc
+# c6dc02263cdf449d9a13e9076217f576
+#: ../../networking2.rst:5141 ../../networking2.rst:6794
+msgid ""
+"All the VPC that you have created for the account is listed in the page."
+msgstr "此帐号创建的所有VPC将显示在页面中。"
+
+# c99084307ecd4209897fc97c610b02b1
+#: ../../networking2.rst:5145
+msgid ""
+"The end users can see their own VPCs, while root and domain admin can see "
+"any VPC they are authorized to see."
+msgstr "最终用户能看到他们自己的VPC，系统管理用户和域管理员可以看到所有被授权查看的VPC。"
+
+# 1470c73ac281442a9cd21cee278957a9
+# 7c8420344fe944869eb9ffe03433dc65
+#: ../../networking2.rst:5150 ../../networking2.rst:6799
+msgid ""
+"Click the Configure button of the VPC for which you want to set up tiers."
+msgstr "在你希望设置层的VPC里，点击配置按钮。"
+
+# c0383203b6324f44bca1f8d64372fd12
+#: ../../networking2.rst:5155
+msgid "Click Create network."
+msgstr "点击新建网络。"
+
+# 71dfd71fa8254a17b162b5ecbea81465
+#: ../../networking2.rst:5157
+msgid "The Add new tier dialog is displayed, as follows:"
+msgstr "然后，添加层的对话界面就会出现。如下："
+
+# 74a521a42b084463aec6f5c6b7a135d8
+#: ../../networking2.rst:5159
+msgid "|add-tier.png|"
+msgstr "|add-tier.png|"
+
+# cd56a1cb2ee5401699918cb0e48192d6
+#: ../../networking2.rst:5161
+msgid ""
+"If you have already created tiers, the VPC diagram is displayed. Click "
+"Create Tier to add a new tier."
+msgstr "如果你已添加层，VPC界面就会出现。点击添加层可以增加一个新的层。"
+
+# 08999394431847eb807438afe40264eb
+#: ../../networking2.rst:5172
+msgid "**Name**: A unique name for the tier you create."
+msgstr "**名称**: 你添加的层的一个唯一的层名。"
+
+# b1d5cef8af774c368f4db6f7adb35ae4
+#: ../../networking2.rst:5176
+msgid ""
+"**Network Offering**: The following default network offerings are listed: "
+"Internal LB, DefaultIsolatedNetworkOfferingForVpcNetworksNoLB, "
+"DefaultIsolatedNetworkOfferingForVpcNetworks"
+msgstr "**网络方案**: 默认有以下几种网络方案: Internal LB, DefaultIsolatedNetworkOfferingForVpcNetworksNoLB, DefaultIsolatedNetworkOfferingForVpcNetworks"
+
+# a109edde2faf4ec4b1f5de31c2c91472
+#: ../../networking2.rst:5181
+msgid ""
+"In a VPC, only one tier can be created by using LB-enabled network offering."
+msgstr "在一个VPC中，用LB-enabled network offering只能创建一个层。"
+
+# cb1a1e05c80349aba5c29f7eb19fb029
+#: ../../networking2.rst:5193
+msgid "**VLAN**: The VLAN ID for the tier that the root admin creates."
+msgstr "**VLAN**: 指定系统管理员创建的层的VLAN ID号。"
+
+# 3a87f69636d34930b6e2382a6c0df8ed
+#: ../../networking2.rst:5195
+msgid ""
+"This option is only visible if the network offering you selected is VLAN-"
+"enabled."
+msgstr "这个选项只在你选择的方案在VLAN-enabled的情况下才会显示出来。"
+
+# 94a1b1fbefab4cd88665da31ab04dff5
+#: ../../networking2.rst:5198
+msgid ""
+"For more information, see `\"Assigning VLANs to Isolated Networks\" "
+"<hosts.html#assigning-vlans-to-isolated-networks>`_."
+msgstr "如需要更多信息，请参考\"为隔离网络分配VLAN\" <hosts.html#assigning-vlans-to-isolated-networks>`_.节。"
+
+# 2c2c9c5c56b24b02b949731d057ccece
+#: ../../networking2.rst:5215
+msgid "Continue with configuring access control list for the tier."
+msgstr "继续为层配置访问控制列表。"
+
+# fe50554812f144079082cb76d478f030
+#: ../../networking2.rst:5220
+msgid "Configuring Network Access Control List"
+msgstr "配置网络访问控制列表"
+
+# e6ac09ebbb494a58abe8f4e2b48ab189
+#: ../../networking2.rst:5222
+msgid ""
+"Define Network Access Control List (ACL) on the VPC virtual router to "
+"control incoming (ingress) and outgoing (egress) traffic between the VPC "
+"tiers, and the tiers and Internet. By default, all incoming traffic to the "
+"guest networks is blocked and all outgoing traffic from guest networks is "
+"allowed, once you add an ACL rule for outgoing traffic, then only outgoing "
+"traffic specified in this ACL rule is allowed, the rest is blocked. To open "
+"the ports, you must create a new network ACL. The network ACLs can be "
+"created for the tiers only if the NetworkACL service is supported."
+msgstr "定义网络访问控制列表（ACL），用以在VPC的层之间，或是层与互联网之间控制进出流量。默认情况下，客户网络的所有进入流量被阻止，所有外出流量被允许。一旦在外出流量方向添加了ACL，则只有ACL规则允许的流量可以被允许，其余的外出流量会被阻止。如果要开放其它端口，则需要在新的ACL中明确定义。只有在支持NetworkACL服务的条件下，只能创建层的ACL。"
+
+# 98625caa21a9468fa1732748d2a17096
+#: ../../networking2.rst:5233
+msgid "About Network ACL Lists"
+msgstr "关于ACL列表"
+
+# 09938c6b069c491ea32225bf40b4c1cb
+#: ../../networking2.rst:5235
+msgid ""
+"In CloudStack terminology, Network ACL is a group of Network ACL items. "
+"Network ACL items are nothing but numbered rules that are evaluated in "
+"order, starting with the lowest numbered rule. These rules determine whether"
+" traffic is allowed in or out of any tier associated with the network ACL. "
+"You need to add the Network ACL items to the Network ACL, then associate the"
+" Network ACL with a tier. Network ACL is associated with a VPC and can be "
+"assigned to multiple VPC tiers within a VPC. A Tier is associated with a "
+"Network ACL at all the times. Each tier can be associated with only one ACL."
+msgstr "在CloudStack术语中，ACL指的是一组针对网络条目。其按条目规则顺序执行，从最小值开始。这些规则决定了与此ACL关联的层的进出流量是被允许还是阻止。操作的方法是添加一个ACL，然后将这个ACL与层关联。ACL在整个VPC中使用，它可以被关系到一个VPC当中多个层中。一个层能及只能关联到一个ACL中。"
+
+# c66744937e154fa482ad3a3e61f312b8
+#: ../../networking2.rst:5245
+msgid ""
+"The default Network ACL is used when no ACL is associated. Default behavior "
+"is all the incoming traffic is blocked and outgoing traffic is allowed from "
+"the tiers. Default network ACL cannot be removed or modified. Contents of "
+"the default Network ACL is:"
+msgstr "当没有ACL明确关联时，会有一个默认的ACL起作用。默认规则是层中所有进入流量被阻止，所有外出流量被允许默认的ACL不能被删除或修改。默认ACL的内容如下："
+
+# e83245e0845e43b2974a692e326ac4d0
+#: ../../networking2.rst:5251
+msgid "Rule"
+msgstr "规则"
+
+# 80ab5b23b00f4d199c8b9abbf436bb6c
+#: ../../networking2.rst:5251
+msgid "Protocol"
+msgstr "协议"
+
+# fd729c57b4ea4e5eba4b9567d5fb91c0
+#: ../../networking2.rst:5251
+msgid "Traffic type"
+msgstr "流量类型"
+
+# c829bf78c58d40288a0ea4fc4372babf
+#: ../../networking2.rst:5251
+msgid "Action"
+msgstr "动作"
+
+# 428dd3d46f624c17b6333ea245a479d1
+# 0044bb0439f34285b617e17b26a24c31
+#: ../../networking2.rst:5253 ../../networking2.rst:5254
+msgid "All"
+msgstr "所有"
+
+# fab35c06087d44a7874a0f5bcd4b49a3
+#: ../../networking2.rst:5253
+msgid "Ingress"
+msgstr "进入流量"
+
+# 28a1e4dff1af4530b1bc7247d7231156
+# f074d55a63a84bdd93f4679ef5703083
+#: ../../networking2.rst:5253 ../../networking2.rst:5254
+msgid "0.0.0.0/0"
+msgstr "0.0.0.0/0"
+
+# b4f811fade53417f914ba70fdda841eb
+#: ../../networking2.rst:5254
+msgid "Egress"
+msgstr "外出流量"
+
+# 8cc5201e9ef74389bf852a8c965d8c58
+#: ../../networking2.rst:5258
+msgid "Creating ACL Lists"
+msgstr "创建ACL列表"
+
+# 1d2d971c7e064b558d73374bc47d82d0
+# 3404c28191eb451a91f3cfa59aefaba4
+#: ../../networking2.rst:5321 ../../networking2.rst:5363
+msgid "Select Network ACL Lists."
+msgstr "选择网络ACL列表。"
+
+# faf3ffe663364217b1a4616fa0286cf2
+#: ../../networking2.rst:5323
+msgid ""
+"The following default rules are displayed in the Network ACLs page: "
+"default\\_allow, default\\_deny."
+msgstr "在ACL页面，下面默认规则将会显示出来：default\\_allow, default\\_deny."
+
+# f9e4f48e72cc497a8f9dcdbb42107837
+#: ../../networking2.rst:5328
+msgid "Click Add ACL Lists, and specify the following:"
+msgstr "点击添加ACL列表，指定以下配置："
+
+# 90439c9713414c43aa9c2e05eb942726
+#: ../../networking2.rst:5332
+msgid "**ACL List Name**: A name for the ACL list."
+msgstr "**ACL列表名称**: 为ACL列表命名。"
+
+# d7606f1b49fa42f190dcf0037e7a7f82
+#: ../../networking2.rst:5336
+msgid ""
+"**Description**: A short description of the ACL list that can be displayed "
+"to users."
+msgstr "**描述**: ACL列表的简短描述。"
+
+# 48a4f463117347eb8b319809642e7da8
+#: ../../networking2.rst:5340
+msgid "Creating an ACL Rule"
+msgstr "创建一个ACL规则"
+
+# 2651d622eb634957a6d286e42b35b431
+#: ../../networking2.rst:5365
+msgid ""
+"In addition to the custom ACL lists you have created, the following default "
+"rules are displayed in the Network ACLs page: default\\_allow, "
+"default\\_deny."
+msgstr "除了创建的你自定义的ACL列表之后，以下默认ACL规则也会显示在页面中：default\\_allow, default\\_deny."
+
+# 8589eb86d31d49b0b8b3a066e403dea3
+# 9fe9f83f4eea466b8c268bff18971db7
+#: ../../networking2.rst:5371 ../../networking2.rst:5495
+msgid "Select the desired ACL list."
+msgstr "选择需要的ACL列表。"
+
+# 526f674e5a544241bfcb69fec29f6b30
+#: ../../networking2.rst:5375
+msgid "Select the ACL List Rules tab."
+msgstr "选择ACL规则栏"
+
+# 6b315c7b1ebe42268824f83af55fae75
+#: ../../networking2.rst:5377
+msgid ""
+"To add an ACL rule, fill in the following fields to specify what kind of "
+"network traffic is allowed in the VPC."
+msgstr "为了创建ACL规则，需要在VPC中定义下面哪些网络流量是允许的。"
+
+# e9fd41991f514decba25f1e0b8bacf9a
+#: ../../networking2.rst:5382
+msgid "**Rule Number**: The order in which the rules are evaluated."
+msgstr "**规则序号**: 规则被执行的顺序。"
+
+# 74e33543194246e9bf723eb7f8579770
+#: ../../networking2.rst:5386
+msgid ""
+"**CIDR**: The CIDR acts as the Source CIDR for the Ingress rules, and "
+"Destination CIDR for the Egress rules. To accept traffic only from or 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 incoming "
+"traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr "**CIDR**: 对于进入的规则，CIDR对源地址起作用，对于外出的规则，CIDR对目标地址起作用。如果要定义多个可接受进出流量的特定地址段，需要以逗号分隔各个CIDR。CIDR是进入流量的基IP地址。比如， 192.168.0.0/22. 如要对所有CIDR允许流量, 设置为 0.0.0.0/0."
+
+# 56275e37fc8b4caea8702ef3e16f0361
+#: ../../networking2.rst:5395
+msgid "**Action**: What action to be taken. Allow traffic or block."
+msgstr "**操作**: 定义要进行的操作，允许或阻止。"
+
+# 3a81766b5639471dad96fc442722931a
+#: ../../networking2.rst:5399
+msgid ""
+"**Protocol**: The networking protocol that sources use to send traffic to "
+"the tier. 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. All supports all the traffic. Other "
+"option is Protocol Number."
+msgstr "**协议**: 发送到层的源地址的网络协议。最终用户的访问和数据交换通常是用TCP和UDP协议。ICMP协议通常用来发送错误信息或网络监控。ALL表示支持所有协议流量，其它选项是协议编号。"
+
+# f182719948c24202b52f34f53d6237ca
+#: ../../networking2.rst:5408
+msgid ""
+"**Start Port**, **End Port** (TCP, UDP only): A range of listening ports "
+"that are the destination for the incoming traffic. If you are opening a "
+"single port, use the same number in both fields."
+msgstr "**起始端口**, **结束端口** (TCP, UDP only):对进入流量，这些端口是指需要监听的目标地址的端口范围。如果你只开放一个端口，则在起始和结束端口里填写同一个端口。"
+
+# 95cc0c49ceea4d609a66a6f010f464a8
+#: ../../networking2.rst:5414
+msgid ""
+"**Protocol Number**: The protocol number associated with IPv4 or IPv6. For "
+"more information, see `Protocol Numbers <http://www.iana.org/assignments"
+"/protocol-numbers/protocol-numbers.xml>`_."
+msgstr "**协议编号**: 协议编号是与IPV4或IPV6相关联的。更多信息，请参考 `协议号 <http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xml>`_."
+
+# 9557a03428624acd806829547ae0ca87
+#: ../../networking2.rst:5420
+msgid ""
+"**ICMP Type**, **ICMP Code** (ICMP only): The type of message and error code"
+" that will be sent."
+msgstr "**ICMP类型**, **ICMP代码** (ICMP only): 信息类型及发送错误的代码。"
+
+# daa0c660c1ee4f7c86a1abd1282d5aa5
+#: ../../networking2.rst:5425
+msgid "**Traffic Type**: The type of traffic: Incoming or outgoing."
+msgstr "**流量类型**: 进出流量的类型。"
+
+# 2a986f306a534501ac5ce1869c4879b2
+#: ../../networking2.rst:5429
+msgid "Click Add. The ACL rule is added."
+msgstr "点击添加。这个ACL规则就添加好了。"
+
+# 1ff7a90c1c8b4226b22c2f267b0cd329
+#: ../../networking2.rst:5431
+msgid ""
+"You can edit the tags assigned to the ACL rules and delete the ACL rules you"
+" have created. Click the appropriate button in the Details tab."
+msgstr "你可以重新编辑ACL标签，或是删除ACL。点击详细信息里的appropriate按钮。"
+
+# 497f804bbce846e084e10331e6e0079b
+#: ../../networking2.rst:5436
+msgid "Creating a Tier with Custom ACL List"
+msgstr "创建一个具有自定义ACL列表的层。"
+
+# d0c0bf84620447fc8dfa178137f97b16
+# d930dbc632b042b188ba54a843e568f1
+#: ../../networking2.rst:5440 ../../networking2.rst:5465
+msgid "Create a VPC."
+msgstr "创建一个VPC。"
+
+# 25eee7556d974e60bbeb1f18e85c55df
+# 6ed43363cfac4b8987d1e2d72304c877
+#: ../../networking2.rst:5444 ../../networking2.rst:5477
+msgid "Create a custom ACL list."
+msgstr "创建一个自定义ACL列表。"
+
+# 6dcc5bedc2554ba1a3e36b2e2b3645be
+# 5463933959af4e5288a81e194a5e6a58
+#: ../../networking2.rst:5448 ../../networking2.rst:5481
+msgid "Add ACL rules to the ACL list."
+msgstr "将ACL规则加入ACL列表。"
+
+# 029e9aecbf464779994d37ec61ad7314
+# 0413f59339f64f0b873ba87c7d559a84
+#: ../../networking2.rst:5452 ../../networking2.rst:5469
+msgid "Create a tier in the VPC."
+msgstr "在VPC里创建一个层。"
+
+# d789fdcbc43847f981d99a6c6a203caf
+#: ../../networking2.rst:5454
+msgid "Select the desired ACL list while creating a tier."
+msgstr "在创建层的过程中选择需要的ACL列表。"
+
+# d2aee63fb26240c8ab5829112ee254c1
+#: ../../networking2.rst:5461
+msgid "Assigning a Custom ACL List to a Tier"
+msgstr "将一个自定义的ACL关联到一个层。"
+
+# b0606dffaee64d4994e5e57c20a1c455
+#: ../../networking2.rst:5473
+msgid "Associate the tier with the default ACL rule."
+msgstr "将默认的ACL规则关联到层。"
+
+# 6113c98ff3804f59808cc2f432c7312e
+#: ../../networking2.rst:5485
+msgid "Select the tier for which you want to assign the custom ACL."
+msgstr "选中你希望赋予自定义ACL的层。"
+
+# 14772476c28c4746811457f94c763124
+#: ../../networking2.rst:5489
+msgid "Click the Replace ACL List icon. |replace-acl-icon.png|"
+msgstr "点击替换ACL图标。|replace-acl-icon.png|"
+
+# c4482d85ed6040e0978d138c1416283a
+#: ../../networking2.rst:5491
+msgid "The Replace ACL List dialog is displayed."
+msgstr "替换ACL的对话界面将会弹出来。"
+
+# 8abffdce40894b3fafb845f68b82bc74
+#: ../../networking2.rst:5504
+msgid "Adding a Private Gateway to a VPC"
+msgstr "在一个VPC里加入私有网关。"
+
+# 743a879733de4969814a821843950e18
+#: ../../networking2.rst:5506
+msgid ""
+"A private gateway can be added by the root admin only. The VPC private "
+"network has 1:1 relationship with the NIC of the physical network. You can "
+"configure multiple private gateways to a single VPC. No gateways with "
+"duplicated VLAN and IP are allowed in the same data center."
+msgstr "私有网关只能被系统管理员添加。VPC私有网络和物理网络之间是1：1的对应关系。你可以在一个VPC里定义多个私有网关。在同一个数据中心，不允许复制VLAN和IP的网关。"
+
+# dd777f72c6814da7a4e087c6c8c60cbe
+#: ../../networking2.rst:5528
+msgid ""
+"Click the Configure button of the VPC to which you want to configure load "
+"balancing rules."
+msgstr "在你想配置负载均衡的VPC上点击配置按钮。"
+
+# 27478e3646e84848b0ead2c5ad0d50f9
+# d08325208f454c9b8c778e4776c4daa3
+# bc97c76d6cd648dc9717c2058744a84e
+#: ../../networking2.rst:5538 ../../networking2.rst:5864
+#: ../../networking2.rst:5951
+msgid "The following options are displayed."
+msgstr "下面这些选项就会出现。"
+
+# 394a3dcb6e3741b489d58eb9830c71e9
+#: ../../networking2.rst:5580
+msgid "Select Private Gateways."
+msgstr "选择私有网关。"
+
+# e4a0570c1e7a471cb5d358378b06e7fe
+#: ../../networking2.rst:5582
+msgid "The Gateways page is displayed."
+msgstr "网关对话框就会显示出来。"
+
+# 6ca2b7325b9e4244a7785ff0e1ddbfd9
+#: ../../networking2.rst:5586
+msgid "Click Add new gateway:"
+msgstr "点击添加新网关："
+
+# 1d19d16a595c4323b72e7afcfa725bee
+#: ../../networking2.rst:5588
+msgid "|add-new-gateway-vpc.png|"
+msgstr "|add-new-gateway-vpc.png|"
+
+# 8413e5ef903842ec837e56605289465f
+#: ../../networking2.rst:5596
+msgid ""
+"**Physical Network**: The physical network you have created in the zone."
+msgstr "**物理网络**: 此处为你已在区域内建好的物理网络。"
+
+# 0a11f680d5cf4a41a7a387b092f56f28
+#: ../../networking2.rst:5601
+msgid "**IP Address**: The IP address associated with the VPC gateway."
+msgstr "**IP地址**: 关联VPC网关的IP地址。"
+
+# fd907890f582482d8e4cf0dd81960ff5
+#: ../../networking2.rst:5605
+msgid ""
+"**Gateway**: The gateway through which the traffic is routed to and from the"
+" VPC."
+msgstr "**网关**: 定义进出VPC流量的网关。"
+
+# 7487738adef9453d85604bfba671fa3f
+#: ../../networking2.rst:5610
+msgid "**Netmask**: The netmask associated with the VPC gateway."
+msgstr "**Netmask**: VPC网关的子网掩码。"
+
+# 16e78548659f4f26a1bda70303cc2316
+#: ../../networking2.rst:5614
+msgid "**VLAN**: The VLAN associated with the VPC gateway."
+msgstr "**VLAN**: VPC网关的VLAN。"
+
+# 4cdaeb9a18454c5a91c6210ae427c1a9
+#: ../../networking2.rst:5618
+msgid ""
+"**Source NAT**: Select this option to enable the source NAT service on the "
+"VPC private gateway."
+msgstr "**Source NAT**: 这个选项会启用VPC私有网关的source NAT服务。"
+
+# c6b56cf49a42479893378e9da36129da
+#: ../../networking2.rst:5621
+msgid "See \":ref:`source-nat-priv-gw`\"."
+msgstr "参考\":ref:`source-nat-priv-gw`\"."
+
+# c362a5b1af954f8c9a1fd9e40fb438db
+#: ../../networking2.rst:5625
+msgid ""
+"**ACL**: Controls both ingress and egress traffic on a VPC private gateway. "
+"By default, all the traffic is blocked."
+msgstr "**ACL**: 控制VPC私有网关的进出流量，默认情况下，所有流量被阻止。"
+
+# a6398dc9bed3442296a3f9cac8a90a34
+#: ../../networking2.rst:5628
+msgid "See \":ref:`acl-priv-gw`\"."
+msgstr "参考\":ref:`acl-priv-gw`\"."
+
+# b9e1f64ee58f4a9fa3bdd10dd0cfaa4f
+#: ../../networking2.rst:5630
+msgid ""
+"The new gateway appears in the list. You can repeat these steps to add more "
+"gateway for this VPC."
+msgstr "新的网关就会出现在列表中。你可以重复这些步骤为VPC增加更多的网关。"
+
+# f6c87880d85a40cfa41db29b98eb2194
+#: ../../networking2.rst:5636
+msgid "Source NAT on Private Gateway"
+msgstr "私有网关的Source NAT"
+
+# 5a7c4b197f044c9bbb56e419cc6153a8
+#: ../../networking2.rst:5638
+msgid ""
+"You might want to deploy multiple VPCs with the same super CIDR and guest "
+"tier CIDR. Therefore, multiple guest VMs from different VPCs can have the "
+"same IPs to reach a enterprise data center through the private gateway. In "
+"such cases, a NAT service need to be configured on the private gateway to "
+"avoid IP conflicts. If Source NAT is enabled, the guest VMs in VPC reaches "
+"the enterprise network via private gateway IP address by using the NAT "
+"service."
+msgstr "你可能希望在同一个超级CIDR和客户层CIDR中部署多个VPC。因此，在一个数据中心，不同VPC中的虚拟机通过私有网络可以拥有相同的IP地址。在这种情况下，就需要在私有网关里配置Source NAT服务以避免IP冲突。如果Source NAT服务启用，VPC中的客户虚拟机使用私有网关IP地址与数据中心其它机器交流。"
+
+# 5a246caddff54fc8aeda076ee6ad6da2
+#: ../../networking2.rst:5646
+msgid ""
+"The Source NAT service on a private gateway can be enabled while adding the "
+"private gateway. On deletion of a private gateway, source NAT rules specific"
+" to the private gateway are deleted."
+msgstr "Source NAT服务是添加私有网关时启用。如果删除了私有网关，关联到此私有网关的Source NAT规则也会被删除。"
+
+# 7b68b00b8cae40daa6b6e018b007407f
+#: ../../networking2.rst:5650
+msgid ""
+"To enable source NAT on existing private gateways, delete them and create "
+"afresh with source NAT."
+msgstr "如要有已有私有网关中启用Source NAT，需要先删除（私有网关），然后再建一个启用Source NAT的私有网关。"
+
+# 5eb31def4dea44a8b45223d8bfba9bc1
+#: ../../networking2.rst:5656
+msgid "ACL on Private Gateway"
+msgstr "私有网关的ACL"
+
+# 43dd38fb6bcb4da99519465cd2fee79e
+#: ../../networking2.rst:5658
+msgid ""
+"The traffic on the VPC private gateway is controlled by creating both "
+"ingress and egress network ACL rules. The ACLs contains both allow and deny "
+"rules. As per the rule, all the ingress traffic to the private gateway "
+"interface and all the egress traffic out from the private gateway interface "
+"are blocked."
+msgstr "VPC私有网关的进出流量是被ACL规则控制的。ACL均包含允许和阻止的规则。在每一条规则中，所有进出私有网关接口的流量是被阻止的。"
+
+# 968f844cb23249299b07710fbdea8328
+#: ../../networking2.rst:5664
+msgid ""
+"You can change this default behaviour while creating a private gateway. "
+"Alternatively, you can do the following:"
+msgstr "你可以在创建私有网关时，改变这个默认的行为。或者，你也可以按如下方式操作："
+
+# c42acc331624417e9e3770047d128c45
+# f426686ca214461286b5b27085ef9e07
+#: ../../networking2.rst:5669 ../../networking2.rst:5715
+msgid "In a VPC, identify the Private Gateway you want to work with."
+msgstr "在VPC中，验证你想操作的私有网关。"
+
+# bebf8abea37d4d5da748d4dc7da121e9
+#: ../../networking2.rst:5673
+msgid "In the Private Gateway page, do either of the following:"
+msgstr "在私有网关页面，按如下步骤操作："
+
+# 83b961b102be4930990a6f24d2f61788
+#: ../../networking2.rst:5677
+msgid "Use the Quickview. See 3."
+msgstr "使用快速查看视图，参考3."
+
+# af59e46963cc4dfcae44b860b6d546a1
+#: ../../networking2.rst:5681
+msgid "Use the Details tab. See 4 through ."
+msgstr "使用详细查看栏。参考4。"
+
+# d774795a1b854c8e9b7b135859f6dc59
+#: ../../networking2.rst:5685
+msgid ""
+"In the Quickview of the selected Private Gateway, click Replace ACL, select "
+"the ACL rule, then click OK"
+msgstr "在所选择的私有网关的快速查看视图里，点击替换ACL，选中ACL规则，然后点击OK按钮。"
+
+# 24203d2c129848b3a54d2a2a6f231ce4
+#: ../../networking2.rst:5690
+msgid "Click the IP address of the Private Gateway you want to work with."
+msgstr "点击你需要操作的私有网关的IP地址。"
+
+# 1374de69edfb44449764f2be1dcb29e2
+#: ../../networking2.rst:5694
+msgid ""
+"In the Detail tab, click the Replace ACL button. |replace-acl-icon.png|"
+msgstr "在详细查看栏。点击替换ACL按钮。|replace-acl-icon.png|"
+
+# 0a1a67c900a645b587377ce0696fcc69
+#: ../../networking2.rst:5697
+msgid "The Replace ACL dialog is displayed."
+msgstr "替换ACL的对话框就会出现。"
+
+# b054350634fe4a6a93e997e7888de509
+#: ../../networking2.rst:5701
+msgid "select the ACL rule, then click OK."
+msgstr "选择ACL规则，然后点击OK按钮。"
+
+# 89bdf37574754f799764bcd9ea9b8154
+#: ../../networking2.rst:5703
+msgid ""
+"Wait for few seconds. You can see that the new ACL rule is displayed in the "
+"Details page."
+msgstr "稍等片刻。你就会看到新的ACL规则出现在详细页面里了。"
+
+# 5156bdb1b2c6423aa03d31c6d234cdbb
+#: ../../networking2.rst:5707
+msgid "Creating a Static Route"
+msgstr "创建一个静态静由。"
+
+# 188c119a7dde4624a113c36b70910b9e
+#: ../../networking2.rst:5709
+msgid ""
+"CloudStack enables you to specify routing for the VPN connection you create."
+" You can enter one or CIDR addresses to indicate which traffic is to be "
+"routed back to the gateway."
+msgstr "CloudStack可以让你指定你创建的VPN链接的路由。你可以输入一个或CIDR地址来指定路由返回到网关的具体流量。"
+
+# c483d63531ae420796887a1e3a3f5ab3
+#: ../../networking2.rst:5719
+msgid ""
+"In the Private Gateway page, click the IP address of the Private Gateway you"
+" want to work with."
+msgstr "在私有网关页面，点击你需要的私有网关的IP地址。"
+
+# df50f83dcb434a239f5ce4054573908a
+#: ../../networking2.rst:5724
+msgid "Select the Static Routes tab."
+msgstr "选择静态路由栏。"
+
+# ddbc917d09ae47a1a33bb2e422a41ac8
+#: ../../networking2.rst:5728
+msgid "Specify the CIDR of destination network."
+msgstr "指定目标网络的CIDR。"
+
+# 14be55f3d8354339befda018b8959689
+#: ../../networking2.rst:5734
+msgid "Wait for few seconds until the new route is created."
+msgstr "稍等片刻，新的路由就创建好了。"
+
+# 4bb61ba3dd1444269d2f517a3d774dac
+#: ../../networking2.rst:5737
+msgid "Blacklisting Routes"
+msgstr "路由黑名单"
+
+# bf15aaf7395c48438bdfb1c5a1b303cd
+#: ../../networking2.rst:5739
+msgid ""
+"CloudStack enables you to block a list of routes so that they are not "
+"assigned to any of the VPC private gateways. Specify the list of routes that"
+" you want to blacklist in the ``blacklisted.routes`` global parameter. Note "
+"that the parameter update affects only new static route creations. If you "
+"block an existing static route, it remains intact and continue functioning. "
+"You cannot add a static route if the route is blacklisted for the zone."
+msgstr "CloudStack允许你定义一个路由黑名单，这样它们就不能关联到任何VPC私有网关。你需要在全局参数blacklisted.routes里定义。要注意，此参数只在新路由创建时才会生效。如果你在黑名单里加入了已存在的静态路由，则此静态路由还是会继续起作用。你不能把在路由黑名单里的路由加入到静态路由当中去。"
+
+# 0331141edca34d0d88619127d2766371
+#: ../../networking2.rst:5748
+msgid "Deploying VMs to the Tier"
+msgstr "将虚拟机部署到层。"
+
+# 704ce74d41e94806a21f067331377028
+#: ../../networking2.rst:5770
+msgid ""
+"The VPC page is displayed where all the tiers you have created are listed."
+msgstr "所有创建好的层都会有VPC页面里列出来。"
+
+# bb949e6b291d4db5b13cf4fe9834f452
+#: ../../networking2.rst:5775
+msgid "Click Virtual Machines tab of the tier to which you want to add a VM."
+msgstr "指向你想添加虚拟机的层，点击虚拟机栏。"
+
+# 71ad9ca13d4c4362972cdf2637e41c93
+#: ../../networking2.rst:5777
+msgid "|add-vm-vpc.png|"
+msgstr "|add-vm-vpc.png|"
+
+# 2f2516ad2c5942d999843c0a9a68933e
+#: ../../networking2.rst:5779
+msgid "The Add Instance page is displayed."
+msgstr "添加实例的页面就会出现。"
+
+# 1d62201e441d48f788fa541062d4c596
+#: ../../networking2.rst:5781
+msgid ""
+"Follow the on-screen instruction to add an instance. For information on "
+"adding an instance, see the Installation Guide."
+msgstr "按照屏幕所指示的操作加入实例。至于如何添加实例，参照安装指南文档。"
+
+# 635c6aa90270428badb026296ec37787
+#: ../../networking2.rst:5785
+msgid "Deploying VMs to VPC Tier and Shared Networks"
+msgstr "在VPC层中部署虚拟，共享网络。"
+
+# dd3534643d7a477c824d8e185d5475e4
+#: ../../networking2.rst:5787
+msgid ""
+"CloudStack allows you deploy VMs on a VPC tier and one or more shared "
+"networks. With this feature, VMs deployed in a multi-tier application can "
+"receive monitoring services via a shared network provided by a service "
+"provider."
+msgstr "CloudStack允许你在VPC层中部署虚拟机和共享网络。有了这个功能，分布在多层当中的虚拟机可以通过共享网络接收到监控服务。"
+
+# b14c4ec942684d4d8a32be3cc684ba90
+#: ../../networking2.rst:5794
+msgid "Log in to the CloudStack UI as an administrator."
+msgstr "用系统管理员登陆到CloudStack UI界面。"
+
+# 47af434606084162a5d43bfca5f9a35c
+#: ../../networking2.rst:5798
+msgid "In the left navigation, choose Instances."
+msgstr "在左边的导航栏里，选择实例。"
+
+# 75908924f9fe449db880b8f340e3e1b9
+#: ../../networking2.rst:5802
+msgid "Click Add Instance."
+msgstr "点击添加实例。"
+
+# 1129214998c14deca387e232b2b61a2c
+#: ../../networking2.rst:5806
+msgid "Select a zone."
+msgstr "选择一个区域。"
+
+# 447c3075519c4efcb0cce18f747c5fdc
+#: ../../networking2.rst:5810
+msgid "Select a template or ISO, then follow the steps in the wizard."
+msgstr "选择一个模板或ISO，按向导步骤操作。 "
+
+# ac1ff1f49a954b0dbd5cd4e18543ec70
+#: ../../networking2.rst:5814
+msgid ""
+"Ensure that the hardware you have allows starting the selected service "
+"offering."
+msgstr "请确认你的硬件支持所选择的服务方案。"
+
+# 5e9d7d945a51416db45c9d4c136cf660
+#: ../../networking2.rst:5819
+msgid ""
+"Under Networks, select the desired networks for the VM you are launching."
+msgstr "在网络导航栏，选择你希望虚拟机所在的网络。"
+
+# 6a193b8ef2e14baab4287c9227dbd94f
+#: ../../networking2.rst:5822
+msgid "You can deploy a VM to a VPC tier and multiple shared networks."
+msgstr "你可以将虚拟机部署在一个拥有多个共享网络的VPC层中。"
+
+# 69378b350f8540138b3659036450b93e
+#: ../../networking2.rst:5824
+msgid "|addvm-tier-sharednw.png|"
+msgstr "|addvm-tier-sharednw.png|"
+
+# c32a2db50b2b44dfa529d303ae7737ca
+#: ../../networking2.rst:5828
+msgid "Click Next, review the configuration and click Launch."
+msgstr "点击下一步，审看已配置信息，然后点击启动。"
+
+# 424cd68b49af4936b7a29172ce8b21c6
+#: ../../networking2.rst:5830
+msgid "Your VM will be deployed to the selected VPC tier and shared network."
+msgstr "你的这个虚拟机就已被部署到所选择的VPC层和共享网络中。"
+
+# a466e870147241b7a6266b24ffb983be
+#: ../../networking2.rst:5833
+msgid "Acquiring a New IP Address for a VPC"
+msgstr "VPC获取新的IP地址。"
+
+# 2469c8b87a5b404695be7cd3d52d8540
+#: ../../networking2.rst:5835
+msgid ""
+"When you acquire an IP address, all IP addresses are allocated to VPC, not "
+"to the guest networks within the VPC. The IPs are associated to the guest "
+"network only when the first port-forwarding, load balancing, or Static NAT "
+"rule is created for the IP or the network. IP can't be associated to more "
+"than one network at a time."
+msgstr "当获取IP地址时，所有的IP地址会被分配到该VPC，而不是VPC中的用户网络。只有当在IP或用户网络上创建第一个网络规则（端口映射、负载均衡、静态NAT）时，该IP才会关联到用户网络。一个IP不能同时关联一个以上的网络。"
+
+# 20c45cce73544593af8aea069f4556ce
+#: ../../networking2.rst:5906
+msgid "Select IP Addresses."
+msgstr "选择IP地址。"
+
+# e00bf099dd75477787b7732cadc10c50
+#: ../../networking2.rst:5908
+msgid "The Public IP Addresses page is displayed."
+msgstr "公网IP地址页面就显示出来。"
+
+# decf033da44c4b64b64175bbace5e37d
+#: ../../networking2.rst:5912
+msgid "Click Acquire New IP, and click Yes in the confirmation dialog."
+msgstr "点击获得一个新IP, 并且在确认的对话框中点击确定."
+
+# f9206ddfd2ad4b9ba496b7bcaa139527
+#: ../../networking2.rst:5914
+msgid ""
+"You are prompted for confirmation because, typically, IP addresses are a "
+"limited resource. Within a few moments, the new IP address should appear "
+"with the state Allocated. You can now use the IP address in port forwarding,"
+" load balancing, and static NAT rules."
+msgstr "因为通常IP地址是有限资源，系统会提示您确认。 在稍等片刻之后，新的IP地址将会出现并且状态是已分配。现在您就可以使用这个IP地址做端口转发、负载均衡或静态NAT。"
+
+# 1b26f54458754874a03b4d4bf65d1776
+#: ../../networking2.rst:5920
+msgid "Releasing an IP Address Alloted to a VPC"
+msgstr "释放VPC分配的IP地址"
+
+# be262f6b7e5d45269e0940307ba4a209
+#: ../../networking2.rst:5922
+msgid ""
+"The IP address is a limited resource. If you no longer need a particular IP,"
+" you can disassociate it from its VPC and return it to the pool of available"
+" addresses. An IP address can be released from its tier, only when all the "
+"networking ( port forwarding, load balancing, or StaticNAT ) rules are "
+"removed for this IP address. The released IP address will still belongs to "
+"the same VPC."
+msgstr "IP地址是有限资源。如果您不再需要某个IP，请解除该IP和VPC的关联，使其返回到可用地址池中。只有当IP上所有的网络规则（端口映射、负载均衡、静态NAT）都删除后，该IP才能从所属层释放。释放的IP仍属于该VPC。"
+
+# b689860f9d8243e488f59f407397d0f2
+#: ../../networking2.rst:5946
+msgid "Click the Configure button of the VPC whose IP you want to release."
+msgstr "点击要释放IP的VPC的配置按钮。"
+
+# 275b1067e783409fa57673f2c9079c5f
+#: ../../networking2.rst:5993
+msgid "Select Public IP Addresses."
+msgstr "选择公网IP地址。"
+
+# 03719974990f4be2ab4ef5acfece3c8e
+#: ../../networking2.rst:5999
+msgid "Click the IP you want to release."
+msgstr "点击要释放的IP地址。"
+
+# 0cfc510897374fe28fa93542914d6cf3
+#: ../../networking2.rst:6003
+msgid "In the Details tab, click the Release IP button |release-ip-icon.png|"
+msgstr "在详细查看栏，点击释放IP按钮。 |release-ip-icon.png|"
+
+# be0f2d3e3f7a4e4485e68f2f4eb4339d
+#: ../../networking2.rst:6008
+msgid "Enabling or Disabling Static NAT on a VPC"
+msgstr "VPC中启用或禁用静态NAT"
+
+# b3b3c30b45744238bdaaee1fe21a6ae1
+#: ../../networking2.rst:6010
+msgid ""
+"A static NAT rule maps a public IP address to the private IP address of a VM"
+" in a VPC to allow Internet traffic to it. This section tells how to enable "
+"or disable static NAT for a particular IP address in a VPC."
+msgstr "静态NAT规则是将公网IP映射到VPC中虚机的私网IP，以便允许互联网流量访问该虚机。本节描述如何在VPC中启用或禁用某个公网IP地址的静态NAT。"
+
+# 8d4539553a8249e59a6c06a65466159f
+#: ../../networking2.rst:6043
+msgid "For each tier, the following options are displayed."
+msgstr "对于每一个层，会显示以下选项。"
+
+# d38f21f4fa594fc99e3fe3eb6bcaac34
+#: ../../networking2.rst:6091
+msgid "Click the IP you want to work with."
+msgstr "点击您要操作的IP。"
+
+# 17644423675640bdafb3f481e66d08cd
+#: ../../networking2.rst:6095
+msgid ""
+"In the Details tab,click the Static NAT button. |enable-disable.png| The "
+"button toggles between Enable and Disable, depending on whether static NAT "
+"is currently enabled for the IP address."
+msgstr "在“详细信息”页，点击静态NAT按钮|enable-disable.png| 。该按钮会根据公网IP的静态NAT当前状态，在启用和禁用间切换。"
+
+# d5a0063d431a449b822e840cf68321c0
+#: ../../networking2.rst:6102
+msgid "If you are enabling static NAT, a dialog appears as follows:"
+msgstr "如果是启用静态NAT，会显示如下对话框："
+
+# addd4d2aaf5345c486dcddaf20d41069
+#: ../../networking2.rst:6104
+msgid "|select-vmstatic-nat.png|"
+msgstr "|select-vmstatic-nat.png|"
+
+# e794f8894d7c4c4fb1d144b53ba3eef5
+#: ../../networking2.rst:6108
+msgid "Select the tier and the destination VM, then click Apply."
+msgstr "选择层和目标虚机，然后点击“应用”。"
+
+# d7cc633eb7064d0e98b22cf3441dea8f
+#: ../../networking2.rst:6111
+msgid "Adding Load Balancing Rules on a VPC"
+msgstr "VPC中添加负载均衡规则"
+
+# 1690cddd7d4544da8afebf41a357f0f6
+#: ../../networking2.rst:6113
+msgid ""
+"In a VPC, you can configure two types of load balancing: external LB and "
+"internal LB. External LB is nothing but a LB rule created to redirect the "
+"traffic received at a public IP of the VPC virtual router. The traffic is "
+"load balanced within a tier based on your configuration. Citrix NetScaler "
+"and VPC virtual router are supported for external LB. When you use internal "
+"LB service, traffic received at a tier is load balanced across different VMs"
+" within that tier. For example, traffic reached at Web tier is redirected to"
+" another VM in that tier. External load balancing devices are not supported "
+"for internal LB. The service is provided by a internal LB VM configured on "
+"the target tier."
+msgstr "在VPC中，你可以配置外部或内部负载均衡。外部负载均衡就是将VPC虚拟路由器接收到的公网流量进行转发的规则。这个流量如何在层里进行均衡取决于你的配置。Citrix NetScaler 和 VPC virtual router都支持外部负载均衡。内部均衡是在层内的虚拟之间进行均衡。比如，到达WEB层请求的流量可以转发到此层另外的虚拟机。外部负载均衡设备不支持内部均衡。内部负载均衡的服务是由目标层的内部虚拟机配置后提供支持服务的。"
+
+# 5ab48adf63474d97b4570c40a24420bb
+#: ../../networking2.rst:6125
+msgid "Load Balancing Within a Tier (External LB)"
+msgstr "在层内进行负载均衡（外部负载均衡）"
+
+# c70e83e371234131bf11479286cdbb1c
+#: ../../networking2.rst:6127
+msgid ""
+"A CloudStack user or administrator may create load balancing rules that "
+"balance traffic received at a public IP to one or more VMs that belong to a "
+"network tier that provides load balancing service in a VPC. A user creates a"
+" rule, specifies an algorithm, and assigns the rule to a set of VMs within a"
+" tier."
+msgstr " CloudStack用户或管理员可以创建负载均衡规则。负载均衡规则用于将一个公网IP的流量分担到在VPC提供负载均衡服务的网络层内的一个或多个VM中。用户可以创建规则，指定算法，然后将规则指定到VPC的一套VM中。"
+
+# 793b75511a124eb49bc054c366095f7f
+#: ../../networking2.rst:6134
+msgid "Enabling NetScaler as the LB Provider on a VPC Tier"
+msgstr "在VPC层中启用基于NetScaler的负载均衡"
+
+# 2cba8bc745e44ac4a8d2aaeca47e11f7
+#: ../../networking2.rst:6138
+msgid "Add and enable Netscaler VPX in dedicated mode."
+msgstr "添加并启用 Netscaler VPX独立模块。"
+
+# 2994a10476d64a719afb3c651265ac88
+#: ../../networking2.rst:6140
+msgid ""
+"Netscaler can be used in a VPC environment only if it is in dedicated mode."
+msgstr "Netscaler只能在独立模块的形式下应用于VPC环境中。"
+
+# d112b0ba00654e278f9b1475857355b0
+#: ../../networking2.rst:6145
+msgid ""
+"Create a network offering, as given in \":ref:`create-net-offering-ext-"
+"lb`\"."
+msgstr "创建启用持久化选项的网络方案。请参考\":ref:`create-net-offering-ext-lb`\"."
+
+# 909680d1f1b34b728fbb4a720169c60b
+#: ../../networking2.rst:6149
+msgid "Create a VPC with Netscaler as the Public LB provider."
+msgstr "在VPC中创建一个基于Netscaler的公用负载均衡。"
+
+# 7ff9cc3865b44322afc77e6c4c063878
+#: ../../networking2.rst:6151
+msgid ""
+"For more information, see `\"Adding a Virtual Private Cloud\" <#adding-a"
+"-virtual-private-cloud>`_."
+msgstr "更多信息，请参考 `\"添加一个VPC\" <#adding-a-virtual-private-cloud>`_."
+
+# 9f9ae62b0b214cba91857447245a18d6
+#: ../../networking2.rst:6156
+msgid "For the VPC, acquire an IP."
+msgstr "在VPC中获取一个IP地址。"
+
+# c75b7cc4b3234929a881c47cc9eac788
+#: ../../networking2.rst:6160
+msgid ""
+"Create an external load balancing rule and apply, as given in :ref:`create-"
+"ext-lb-rule`."
+msgstr "创建并应用一个外部负载均衡规则。请参考:ref:`create-ext-lb-rule`."
+
+# d874e75e8da946b99ed923dcdaed1708
+#: ../../networking2.rst:6166
+msgid "Creating a Network Offering for External LB"
+msgstr "创建一个外部负载均衡网络方案"
+
+# 7f3a18897d37416bb87a733cb3943071
+#: ../../networking2.rst:6168
+msgid ""
+"To have external LB support on VPC, create a network offering as follows:"
+msgstr "要在VPC中启用外部负载均衡支持，依如下操作建立网络方案："
+
+# f8f209ed13a948109fa2bb53a02c1658
+# 2681733d801147e687ba507663618ba4
+#: ../../networking2.rst:6173 ../../networking2.rst:6478
+msgid "Log in to the CloudStack UI as a user or admin."
+msgstr "使用用户或管理员登录到CloudStack用户界面。"
+
+# bfaeb8a949fb4d25a618540dcc365471
+# 6c6e4ac1110442ba9ec325328e96bfb8
+#: ../../networking2.rst:6177 ../../networking2.rst:6482
+msgid "From the Select Offering drop-down, choose Network Offering."
+msgstr "下拉选择方案，选择网络方案："
+
+# 7d4dc49f6e224caa9bee24da2b622a4c
+# 8e12000ca5ad480ab9dab674135a18a8
+#: ../../networking2.rst:6185 ../../networking2.rst:6490
+msgid "In the dialog, make the following choices:"
+msgstr "在对话框中，选择如下操作："
+
+# 3d9e45006e6b427b94e238e0f793a577
+# 066c1cd8d7414486bd0a821ccffc100b
+#: ../../networking2.rst:6189 ../../networking2.rst:6494
+msgid "**Name**: Any desired name for the network offering."
+msgstr "**名称**: 任何网络方案的名称。"
+
+# acbfe1094f0643fea1072cd746f35188
+# f27a5e7e95c64d4b984ce309aaaee266
+#: ../../networking2.rst:6193 ../../networking2.rst:6498
+msgid ""
+"**Description**: A short description of the offering that can be displayed "
+"to users."
+msgstr "**描述**: 提供一个简短的方案描述。 "
+
+# 15f09db814bb43e2832e26ce351b9ae6
+# d6ebc01d2aea41328bd788a943cea913
+#: ../../networking2.rst:6198 ../../networking2.rst:6503
+msgid "**Network Rate**: Allowed data transfer rate in MB per second."
+msgstr "**网络速度**: 允许的数据传输速度（MB/秒）。"
+
+# a4945e04912944f89c7073bdac1af7af
+# a9b549ff67de4071aad4f568bc2d7d2b
+#: ../../networking2.rst:6202 ../../networking2.rst:6507
+msgid ""
+"**Traffic Type**: The type of network traffic that will be carried on the "
+"network."
+msgstr "**流量类型**: 允许承载的网络流量类型。"
+
+# aefb9c140bc34d2b9b3c2d433d14c685
+# 169e4a6365194916a452f640cf688fb0
+#: ../../networking2.rst:6207 ../../networking2.rst:6512
+msgid ""
+"**Guest Type**: Choose whether the guest network is isolated or shared."
+msgstr "**来宾类型**: 选择来宾网络为隔离或共享网络。"
+
+# bdfc22e5126944f5bca7168232a3f3f5
+# d937940688b44a349057cd0905cd57b2
+#: ../../networking2.rst:6212 ../../networking2.rst:6517
+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."
+msgstr "**持续性**: 表明来宾网络是否支持持续性。无需提供任何VM部署的网络，称之为持续性网络。"
+
+# 24cbc093f168445995bd443ca153e32c
+# b1ee73a6428247b38f74321037409214
+#: ../../networking2.rst:6218 ../../networking2.rst:6523
+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\" <#about-virtual-private-clouds>`_."
+msgstr "**VPC**: 此选项表明是否在来宾网络中启用VPC。 CloudStack中的虚拟专用云(VPC)是专用、隔离的。 一个VPC可以有一个类似于传统物理网络的虚拟网络拓扑结构。有关的VPC的详细信息，请参考`\"关于VPC\" <#about-virtual-private-clouds>`_."
+
+# 4bf8da8a72a240cd858cf9a55cb035ad
+# 6db873f4ea9f410fb0a58b146ce86962
+#: ../../networking2.rst:6226 ../../networking2.rst:6532
+msgid ""
+"**Specify VLAN**: (Isolated guest networks only) Indicate whether a VLAN "
+"should be specified when this offering is used."
+msgstr "**指定**: (仅隔离的来宾网络) 表明在使用这个网络方案时，是否指定VLAN。"
+
+# 1d81bbc322a54e489b5b1da1c925266c
+#: ../../networking2.rst:6231
+msgid ""
+"**Supported Services**: Select Load Balancer. Use Netscaler or "
+"VpcVirtualRouter."
+msgstr "**支持服务**:选择负载均衡，使用Netscaler 或 VpcVirtualRouter."
+
+# b7b1ce246f71472ebf576db84b53c0e2
+#: ../../networking2.rst:6236
+msgid "**Load Balancer Type**: Select Public LB from the drop-down."
+msgstr "**负载均衡类型**:从下拉列表里选择公用负载均衡。"
+
+# 7b38714001f849eaac70496b3c171131
+#: ../../networking2.rst:6240
+msgid ""
+"**LB Isolation**: Select Dedicated if Netscaler is used as the external LB "
+"provider."
+msgstr "*负载均衡隔离**: 如果使用Netscale作为外部负载均衡，选择此项进行隔离。"
+
+# f8eb59d83f644c33b8ee256b3cb69be1
+# f03b089f4f1442e99afc923137ed1f0f
+#: ../../networking2.rst:6245 ../../networking2.rst:6546
+msgid ""
+"**System Offering**: Choose the system service offering that you want "
+"virtual routers to use in this network."
+msgstr "**系统方案**: 选择你想在这个网络中使用的虚拟路由器的系统服务方案。"
+
+# e2ce12394dea4b1abc2c67c40b3f20ce
+# 537aea511f3244d880cd207f11c31028
+#: ../../networking2.rst:6250 ../../networking2.rst:6551
+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."
+msgstr "**保护模式**: 表明是否使用保护模式。在这个模式中，只有网络中第一个虚拟机启动时才分配网络资源。"
+
+# f89be0d5cb8f47a581ef67c728561fc4
+# 05c7f9a8f2fa439ba289bc25ce6430ab
+#: ../../networking2.rst:6256 ../../networking2.rst:6557
+msgid "Click OK and the network offering is created."
+msgstr "点击OK按钮，网络方案就创建好了。"
+
+# 492f96c74e934c4385e58a39f4c1633b
+#: ../../networking2.rst:6261
+msgid "Creating an External LB Rule"
+msgstr "创建一个外部负载均衡规则"
+
+# b8dd2aecb6fa4106bfed11ed839c7aca
+#: ../../networking2.rst:6280
+msgid ""
+"Click the Configure button of the VPC, for which you want to configure load "
+"balancing rules."
+msgstr "点击要配置负载均衡规则的VPC的配置按钮。"
+
+# 522435c1f1414cc18a01df702d9f6281
+# bcacf41ce9934ed095e8f719398c45b3
+#: ../../networking2.rst:6283 ../../networking2.rst:6593
+msgid ""
+"The VPC page is displayed where all the tiers you created listed in a "
+"diagram."
+msgstr "系统会显示VPC页面，您创建的所有层都列在图中。"
+
+# 0ccde3dd807a4f04ac772a7cf191a828
+# c8b1e6fcd7554efd9584f9488b591a1f
+#: ../../networking2.rst:6343 ../../networking2.rst:6737
+msgid "Select the tier to which you want to apply the rule."
+msgstr "选择应用规则的层。"
+
+# 1744ccff1ce1472ea311af081db3ec2f
+#: ../../networking2.rst:6355
+msgid ""
+"**Public Port**: The port that receives the incoming traffic to be balanced."
+msgstr "**公网端口**: 接收待负载均衡的流入流量的端口。"
+
+# 841c7cfded624598a7091a1eb3f3f894
+# 1342d03c9f7e4b4a879cc635b80b627e
+#: ../../networking2.rst:6365 ../../networking2.rst:6638
+msgid ""
+"**Algorithm**. Choose the load balancing algorithm you want CloudStack to "
+"use. CloudStack supports the following well-known algorithms:"
+msgstr "**算法**。选择您希望CloudStack 使用的负载均衡算法。CloudStack 支持下列知名的算法："
+
+# ca0b21cbc71045ef9d692689bdf8753b
+# c5c7bc131cb24e8a89af17bc2ee39a95
+#: ../../networking2.rst:6375 ../../networking2.rst:6648
+msgid "Least connections"
+msgstr "最少连接"
+
+# 6c473e5828a34e0287d62955ca824812
+# a9615fbf431b46e4b58d02737e405bca
+#: ../../networking2.rst:6379 ../../networking2.rst:6652
+msgid "Source"
+msgstr "源IP"
+
+# 1dc54356abfe4ffa8b1fba11d7728393
+#: ../../networking2.rst:6383
+msgid ""
+"**Stickiness**. (Optional) Click Configure and choose the algorithm for the "
+"stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr "**粘性**.（可选）点击配置，选择粘性策略使用的算法。参见负载均衡规则的粘性会话策略。"
+
+# 237d74628ed349cf856380cefedd651f
+#: ../../networking2.rst:6389
+msgid ""
+"**Add VMs**: Click Add VMs, then select two or more VMs that will divide the"
+" load of incoming traffic, and click Apply."
+msgstr "点击添加VM，选择两个或更多的VM分担流入的流量，然后点击应用。"
+
+# 71e872c5170d4050b696e3ce82700548
+#: ../../networking2.rst:6392
+msgid ""
+"The new load balancing rule appears in the list. You can repeat these steps "
+"to add more load balancing rules for this IP address."
+msgstr "新的负载均衡策略会显示在列表中。您可以重复以上步骤为该IP地址添加更多的负载均衡策略。"
+
+# 4574a620c8424f90a6c9a8c28f5460a1
+#: ../../networking2.rst:6396
+msgid "Load Balancing Across Tiers"
+msgstr "跨越层的负载均衡"
+
+# 843b230d3f9d4a50946db6b4012be2cc
+#: ../../networking2.rst:6398
+msgid ""
+"CloudStack supports sharing workload across different tiers within your VPC."
+" Assume that multiple tiers are set up in your environment, such as Web tier"
+" and Application tier. Traffic to each tier is balanced on the VPC virtual "
+"router on the public side, as explained in `\"Adding Load Balancing Rules on"
+" a VPC\" <#adding-load-balancing-rules-on-a-vpc>`_. If you want the traffic "
+"coming from the Web tier to the Application tier to be balanced, use the "
+"internal load balancing feature offered by CloudStack."
+msgstr "CloudStack支持在VPC内不同层之间共享工作负载。这需要先在你的环境里设置好多个层，比如WEB层，应用层。每一个层的流量通过VPC虚拟路由机进行负载均衡。关于这方面的内容， `\"在VPC里添加负载均衡规则\" <#adding-load-balancing-rules-on-a-vpc>`_. 如果你想将WEB层发向应用层的流量进行负载均衡，需要使用Cloudstack的内部负载均衡功能。"
+
+# 525cb00286734509a00f17f18c86ced6
+#: ../../networking2.rst:6408
+msgid "How Does Internal LB Work in VPC?"
+msgstr "在VPC中，内部负载均衡是如何工作的呢？"
+
+# 4cd2c13cae1c4f91876bc2767c81d9a1
+#: ../../networking2.rst:6410
+msgid ""
+"In this figure, a public LB rule is created for the public IP 72.52.125.10 "
+"with public port 80 and private port 81. The LB rule, created on the VPC "
+"virtual router, is applied on the traffic coming from the Internet to the "
+"VMs on the Web tier. On the Application tier two internal load balancing "
+"rules are created. An internal LB rule for the guest IP 10.10.10.4 with load"
+" balancer port 23 and instance port 25 is configured on the VM, "
+"InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.4 with "
+"load balancer port 45 and instance port 46 is configured on the VM, "
+"InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.6, with "
+"load balancer port 23 and instance port 25 is configured on the VM, "
+"InternalLBVM2."
+msgstr "在这个图中，公网负载均衡规则是这样创建的：公网IP为IP 72.52.125.10，外网端口为80，内网端口为81。VPC的虚拟路由机创建的负载均衡规则将互联网的流量分配到WEB层的各个虚拟机上。在应用层创建了两个内部负载均衡规则。其中一个规则是：客户IP为10.10.10.4的将端口23进行负载分发，实例VM和InternalLBVM1的端口25进行了负载。另一条规则是：客户IP为10.10.10.4的将端口45进行负载分发，实例VM和InternalLBVM1的端口46进行了负载。另一条规则是：客户IP为10.10.10.6的将端口23进行负载分发，实例VM和InternalLBVM1的端口25进行了负载。（两条规则还是三条规则？原文如此，希望图示能明解）"
+
+# b3129b5c753047129a01b1ba3c4fede8
+#: ../../networking2.rst:6422
+msgid "|vpc-lb.png|"
+msgstr "|vpc-lb.png|"
+
+# 8b1b1a74897143cb88a7542e79cf51f3
+#: ../../networking2.rst:6429
+msgid ""
+"Internal LB and Public LB are mutually exclusive on a tier. If the tier has "
+"LB on the public side, then it can't have the Internal LB."
+msgstr "内部和公网负载均衡在一个层里往往是互斥的。如果一个层已应用了公网负载均衡之后，此层就不能再应用内部负载均衡。"
+
+# 4388c29d8e264047afa9fe7ff8b116fd
+#: ../../networking2.rst:6434
+msgid ""
+"Internal LB is supported just on VPC networks in CloudStack 4.2 release."
+msgstr "在 CloudStack 4.2版本中，只有VPC网络支持内部负载均衡。"
+
+# f446d0a1aad04939840f2e711a509b3e
+#: ../../networking2.rst:6439
+msgid ""
+"Only Internal LB VM can act as the Internal LB provider in CloudStack 4.2 "
+"release."
+msgstr "在CloudStack 4.2 版本中，只有Internal LB VM才能作内部负载均衡的提供方。"
+
+# f4b320548bdb4614952985433f8b1177
+#: ../../networking2.rst:6444
+msgid ""
+"Network upgrade is not supported from the network offering with Internal LB "
+"to the network offering with Public LB."
+msgstr "将网络方案由内部负载均衡更改为公网负载均衡是不可行的。"
+
+# 264141b663754516b518d1f6d1a96ebf
+#: ../../networking2.rst:6449
+msgid "Multiple tiers can have internal LB support in a VPC."
+msgstr "在VPC中，多层可以应用内部负载均衡。"
+
+# f09c422386a34597a8def34515b103c9
+#: ../../networking2.rst:6453
+msgid "Only one tier can have Public LB support in a VPC."
+msgstr "在VPC中，只有一层只支持公网负载均衡。"
+
+# 028d12b705c040d4a796b5085738d685
+#: ../../networking2.rst:6456
+msgid "Enabling Internal LB on a VPC Tier"
+msgstr "在VPC层上启用内部负载均衡功能"
+
+# 7c0d2274b60242a58ed2cf1355a72079
+#: ../../networking2.rst:6460
+msgid ""
+"Create a network offering, as given in :ref:`creating-net-offering-internal-"
+"lb`."
+msgstr "创建一个新的网络方案，请参考:ref:`creating-net-offering-internal-lb`."
+
+# 6c4da6439e3f4b018afd1c51169ab257
+#: ../../networking2.rst:6464
+msgid ""
+"Create an internal load balancing rule and apply, as given in :ref:`create-"
+"int-lb-rule`."
+msgstr "创建并应用一个内部负载均衡规则。参考:ref:`create-int-lb-rule`."
+
+# 7632bb75de7b4419ab26471d1f3e2cdd
+#: ../../networking2.rst:6470
+msgid "Creating a Network Offering for Internal LB"
+msgstr "创建一个内部负载均衡网络方案"
+
+# bb39964280e14e828cb77bd8faad4389
+#: ../../networking2.rst:6472
+msgid ""
+"To have internal LB support on VPC, either use the default offering, "
+"DefaultIsolatedNetworkOfferingForVpcNetworksWithInternalLB, or create a "
+"network offering as follows:"
+msgstr "要在VPC当中使用内部负载均衡，可以使用默认的DefaultIsolatedNetworkOfferingForVpcNetworksWithInternalLB,或按如下操作新建一个网络方案："
+
+# 8f9488a3121d483a90d04b721d6d1d67
+#: ../../networking2.rst:6537
+msgid ""
+"**Supported Services**: Select Load Balancer. Select ``InternalLbVM`` from "
+"the provider list."
+msgstr "**支持服务**:选择负载均衡，从待提供的下拉列表里选择`InternalLbVM。"
+
+# 10f1614fb17846fc84ab119ba2e48c82
+#: ../../networking2.rst:6542
+msgid "**Load Balancer Type**: Select Internal LB from the drop-down."
+msgstr "**负载均衡类型**:从下拉列表里选择内部负载均衡。"
+
+# 1554f48553a24d8eb75e184a1a3dcaae
+#: ../../networking2.rst:6562
+msgid "Creating an Internal LB Rule"
+msgstr "创建一个内部负载均衡规则"
+
+# 7c93f86fe3d04b018ebc0f755fdd3bd9
+#: ../../networking2.rst:6564
+msgid ""
+"When you create the Internal LB rule and applies to a VM, an Internal LB VM,"
+" which is responsible for load balancing, is created."
+msgstr "当你创建好一个内部负载均衡规则，并将之用于一个虚拟之后，一个内部负载均衡的应用就建立起来了。"
+
+# c341cb78685b4d799b920d6abfc1379d
+#: ../../networking2.rst:6567
+msgid ""
+"You can view the created Internal LB VM in the Instances page if you "
+"navigate to **Infrastructure** > **Zones** > <zone\\_ name> > "
+"<physical\\_network\\_name> > **Network Service Providers** > **Internal LB "
+"VM**. You can manage the Internal LB VMs as and when required from the "
+"location."
+msgstr "You can view the created Internal LB VM in the Instances page 按如下导航 **基础构架** > **区域** > <zone\\_ name> > <physical\\_network\\_name> > **网络服务提供** > **内部负载均衡虚拟机**，你就可以看到已创建了内部负载均衡的实例上。也可以在此进行内部负载均衡的管理。"
+
+# bb074ba85b95485ab2000aa11bbf8f33
+#: ../../networking2.rst:6590
+msgid ""
+"Locate the VPC for which you want to configure internal LB, then click "
+"Configure."
+msgstr "点击要配置内部负载均衡规则的VPC的配置按钮。"
+
+# 9f89311df2d04728b293005448c4dc44
+#: ../../networking2.rst:6598
+msgid ""
+"Locate the Tier for which you want to configure an internal LB rule, click "
+"Internal LB."
+msgstr "指向你想配置内部负载均衡的层，点击内部负载均衡。"
+
+# a048cf82b55a4a65a79b907eddb27da1
+#: ../../networking2.rst:6601
+msgid "In the Internal LB page, click Add Internal LB."
+msgstr "在 Internal LB页面里，点击添加 Internal LB。"
+
+# ec4dcfcce0a24d839230f062df3b4b64
+#: ../../networking2.rst:6605
+msgid "In the dialog, specify the following:"
+msgstr "在对话框里，定义以下内容："
+
+# 74434a3d36fb484a804a01e12ce24764
+#: ../../networking2.rst:6613
+msgid ""
+"**Description**: A short description of the rule that can be displayed to "
+"users."
+msgstr "**描述**: 提供一个简短的规则描述。 "
+
+# daed72af843943e9baccd05bcb786a21
+#: ../../networking2.rst:6618
+msgid ""
+"**Source IP Address**: (Optional) The source IP from which traffic "
+"originates. The IP is acquired from the CIDR of that particular tier on "
+"which you want to create the Internal LB rule. If not specified, the IP "
+"address is automatically allocated from the network CIDR."
+msgstr "**源IP地址**: (可选) 是指产生流量的源IP地址。这个地址是从你创建内部负载均衡的层中的CIDR中获取的。如果没有指定，则系统会自动从CIDR中分配。"
+
+# 15b760898c8e4743b7a45bdb78cc5d29
+#: ../../networking2.rst:6624
+msgid ""
+"For every Source IP, a new Internal LB VM is created for load balancing."
+msgstr "对于每一个源IP地址，都可以建立一个针对它的内部负载均衡。"
+
+# 7d4fda85029c411f98060e303e433ebe
+#: ../../networking2.rst:6629
+msgid ""
+"**Source Port**: The port associated with the source IP. Traffic on this "
+"port is load balanced."
+msgstr "**源端口**: 与源IP地址关联的端口，此端口上的流量是基于负载均衡的。"
+
+# b8760e9c1eb746b98a4deb723cad698b
+#: ../../networking2.rst:6634
+msgid "**Instance Port**: The port of the internal LB VM."
+msgstr "**实例端口**:内部负载均衡虚拟机的端口。"
+
+# eb41a8a1275d4f319cf708bbc6cbd615
+#: ../../networking2.rst:6655
+msgid "Adding a Port Forwarding Rule on a VPC"
+msgstr "在VPC里添加一个端口转发规则。"
+
+# b7b954709aca4ed4b65909249a1445cf
+#: ../../networking2.rst:6745
+msgid ""
+"**Public Port**: The port to which public traffic will be addressed on the "
+"IP address you acquired in the previous step."
+msgstr "**公用端口**:你在前面操作所获取的供公共流量使用的公用IP地址的端口。 "
+
+# 3457f6b6eb9945b2adb0a5de7deafea8
+#: ../../networking2.rst:6750
+msgid ""
+"**Private Port**: The port on which the instance is listening for forwarded "
+"public traffic."
+msgstr "**私有端口**: 虚拟机实例将被转发到公共流量的监听端口。"
+
+# 109d7b5b794343e3b14449585d750125
+#: ../../networking2.rst:6755
+msgid "**Protocol**: The communication protocol in use between the two ports."
+msgstr "**Protocol**:两个端口之间所用的互联协议。"
+
+# a52983a3295b440e854b8e8de723ab47
+#: ../../networking2.rst:6760
+msgid "TCP"
+msgstr "TCP"
+
+# a80d548790614268b9a37014436e3b33
+#: ../../networking2.rst:6764
+msgid "UDP"
+msgstr "UDP"
+
+# 3045d1ed30694200ab89150942fe8a6a
+#: ../../networking2.rst:6768
+msgid ""
+"**Add VM**: Click Add VM. Select the name of the instance to which this rule"
+" applies, and click Apply."
+msgstr "**Add VM**: 点击增加虚拟机，选择你想将此规则应用上的虚拟机，点击应用。"
+
+# 4b9ed6535e914dd89e1a04c8c2f345d7
+#: ../../networking2.rst:6771
+msgid "You can test the rule by opening an SSH session to the instance."
+msgstr "你可以通过SSH连接实例来测试此规则。"
+
+# 4a6c93a072f04111a01f85167fd2755d
+#: ../../networking2.rst:6774
+msgid "Removing Tiers"
+msgstr "删除层"
+
+# 5142d19ad4794b65970714b4e4bbbec5
+#: ../../networking2.rst:6776
+msgid ""
+"You can remove a tier from a VPC. A removed tier cannot be revoked. When a "
+"tier is removed, only the resources of the tier are expunged. All the "
+"network rules (port forwarding, load balancing and staticNAT) and the IP "
+"addresses associated to the tier are removed. The IP address still be "
+"belonging to the same VPC."
+msgstr "你可以从一个VPC中删除一个层。一个被删除的层是不能被擦除的。当一个层被删除后，只有层的资源被删去。所有的网络规则(端口转发，负载均衡，静态NAT)还有关联到此层的IP地址都会删除。但这些IP地址仍然属于这个VPC。"
+
+# 7c041faaebfa4ddab0237d7749ac57b0
+#: ../../networking2.rst:6802
+msgid ""
+"The Configure VPC page is displayed. Locate the tier you want to work with."
+msgstr "配置VPC的页面显示出来了。指向你需要操作的层。"
+
+# df27c86ec4a94161b3370aae61a474f0
+#: ../../networking2.rst:6807
+msgid "Select the tier you want to remove."
+msgstr "选择你想删除的层。"
+
+# 36316512ad134fdd8cf52cee54ea5230
+#: ../../networking2.rst:6811
+msgid ""
+"In the Network Details tab, click the Delete Network button. |del-tier.png|"
+msgstr "在网络详细栏，点击删除网络按钮。|del-tier.png|"
+
+# 50fe8c3d59b048c5b83145acbe8be4e5
+#: ../../networking2.rst:6814
+msgid "Click Yes to confirm. Wait for some time for the tier to be removed."
+msgstr "点击YES按钮。稍等片片刻，层就会被删除了。"
+
+# 2946ed6a189c43f58b6c443a883de36f
+#: ../../networking2.rst:6817
+msgid "Editing, Restarting, and Removing a Virtual Private Cloud"
+msgstr "编辑，重启，删除VPC。"
+
+# 41e51cc9e9d14164a66fb7e95f9f8a12
+#: ../../networking2.rst:6819
+msgid "Ensure that all the tiers are removed before you remove a VPC."
+msgstr "在删除VPC前，需要先删除所有的层。"
+
+# 98e5e7fe7bff4cb18c826b8a17fbca71
+#: ../../networking2.rst:6838
+msgid "Select the VPC you want to work with."
+msgstr "选择你需要的VPC。"
+
+# fdc4b5db10a245f68c46b4793a5b052e
+#: ../../networking2.rst:6842
+msgid "In the Details tab, click the Remove VPC button |remove-vpc.png|"
+msgstr "在详细栏，点击删除VPC按钮。|remove-vpc.png|"
+
+# 3fabd3a8fb6b4546887df7e7f8c4212c
+#: ../../networking2.rst:6844
+msgid ""
+"You can remove the VPC by also using the remove button in the Quick View."
+msgstr "你也可以在快速查看视图里点击删除按钮进行VPC的删除。"
+
+# 8f6ce6f0fc7943e8965aeb7c157eef28
+#: ../../networking2.rst:6847
+msgid ""
+"You can edit the name and description of a VPC. To do that, select the VPC, "
+"then click the Edit button. |edit-icon.png|"
+msgstr "您可以编辑VPC的名称和描述。选择VPC，然后点击编辑按钮。 |edit-icon.png|"
+
+# 44868ef425a9478c9a51b13b823cb75d
+#: ../../networking2.rst:6850
+msgid ""
+"To restart a VPC, select the VPC, then click the Restart button. |restart-"
+"vpc.png|"
+msgstr "如果要重启一个VPC，点击重启按钮。|restart-vpc.png|"
+
+# f535c4d4c6e542569b645467558a84ba
+#: ../../networking2.rst:6854
+msgid "Persistent Networks"
+msgstr "Persistent网络"
+
+# ac16a1f817024aa4ba3804fcab51f851
+#: ../../networking2.rst:6856
+msgid ""
+"The network that you can provision without having to deploy any VMs on it is"
+" called a persistent network. A persistent network can be part of a VPC or a"
+" non-VPC environment."
+msgstr "在不部署任何VM的情况下就初始化好的网络称为持久化网络。持久化网络可以是VPC的一部分，也可以不是。"
+
+# 69a29ed2704f4f48b0796699ad7a36eb
+#: ../../networking2.rst:6860
+msgid ""
+"When you create other types of network, a network is only a database entry "
+"until the first VM is created on that network. When the first VM is created,"
+" a VLAN ID is assigned and the network is provisioned. Also, when the last "
+"VM is destroyed, the VLAN ID is released and the network is no longer "
+"available. With the addition of persistent network, you will have the "
+"ability to create a network in CloudStack in which physical devices can be "
+"deployed without having to run any VMs. Additionally, you can deploy "
+"physical devices on that network."
+msgstr "在您创建其它类型的网络时，在网络中第一台VM创建之前，该网络仅是数据库的一条记录。当第一个VM创建时，网络会指定一个VLAN ID并初始化。同样，当网络中最后一个VM销毁后，VLAN ID会被释放，这样该网络就不再可用。通过使用持久化网络，您就有能力在不部署VM的情况下在&PRODUCT;中创建一个网络用来部署物理设备。而且，您可以在该网络中部署物理设备。"
+
+# 58f4be07725f415581616cb03772a7a7
+#: ../../networking2.rst:6869
+msgid ""
+"One of the advantages of having a persistent network is that you can create "
+"a VPC with a tier consisting of only physical devices. For example, you "
+"might create a VPC for a three-tier application, deploy VMs for Web and "
+"Application tier, and use physical machines for the Database tier. Another "
+"use case is that if you are providing services by using physical hardware, "
+"you can define the network as persistent and therefore even if all its VMs "
+"are destroyed the services will not be discontinued."
+msgstr "使用持久化网络的一个优点是您可以创建具有一个只包含物理设备的层的VPC。例如，您可以为一个三层应用创建一个VPC，在Web层和应用层部署VM，在数据库层使用物理机器。另一个使用场景为如果您使用物理硬件提供网络服务，您可以定义网络为持久化的。这样即便网络中所有VM都销毁了，服务还可以继续提供。"
+
+# 8ff007bee6954fe199b3c83d78392acf
+#: ../../networking2.rst:6879
+msgid "Persistent Network Considerations"
+msgstr "持久化网络的考虑事项"
+
+# f6f834bfef49425085d2d0742d6ef874
+#: ../../networking2.rst:6883
+msgid "Persistent network is designed for isolated networks."
+msgstr "Persistent网络是为隔离网络而设计的。"
+
+# 0bb5d0eb31464beaa3c07b2ff9af3aa2
+#: ../../networking2.rst:6887
+msgid "All default network offerings are non-persistent."
+msgstr "所有默认的网络方案都是非Persistent的。"
+
+# 5051557b950f477e8d115a69bf8150d4
+#: ../../networking2.rst:6891
+msgid ""
+"A network offering cannot be editable because changing it affects the "
+"behavior of the existing networks that were created using this network "
+"offering."
+msgstr "网络方案的持久化选项不可编辑。因为修改该选项会影响使用该网络方案创建的已有网络的行为。"
+
+# 593697221e614fe980bca6c00979e531
+#: ../../networking2.rst:6897
+msgid ""
+"When you create a guest network, the network offering that you select "
+"defines the network persistence. This in turn depends on whether persistent "
+"network is enabled in the selected network offering."
+msgstr "当您创建客户网络时，您选择的网络方案定义了该网络的持久化。反过来，这依赖于选择的网络方案是否启用持久化网络。"
+
+# 34302861eff548dd9e9007020f1c927b
+#: ../../networking2.rst:6903
+msgid ""
+"An existing network can be made persistent by changing its network offering "
+"to an offering that has the Persistent option enabled. While setting this "
+"property, even if the network has no running VMs, the network is "
+"provisioned."
+msgstr "通过修改使用的网络方案为启用持久化的方案，现有网络可以变为持久化。在设置该属性时，即便网络中没有运行的VM，该网络也会初始化。"
+
+# e3974307d7cd464eb0a6028ee8f57e4b
+#: ../../networking2.rst:6910
+msgid ""
+"An existing network can be made non-persistent by changing its network "
+"offering to an offering that has the Persistent option disabled. If the "
+"network has no running VMs, during the next network garbage collection run "
+"the network is shut down."
+msgstr "通过修改使用的网络方案为禁用持久化的方案，现有网络可以变为非持久化。如果网络中没有运行的VM，在下次网络垃圾回收运行时，该网络会被关闭。"
+
+# 1c9032badc034107b57250169a03a890
+#: ../../networking2.rst:6917
+msgid ""
+"When the last VM on a network is destroyed, the network garbage collector "
+"checks if the network offering associated with the network is persistent, "
+"and shuts down the network only if it is non-persistent."
+msgstr "当网络中最后一台VM销毁时，网络垃圾回收器会检查该网络的网络方案是否为持久化，若不是持久化，则会关闭网络。"
+
+# 56e305bc255e4c999e504e5acb010e4f
+#: ../../networking2.rst:6923
+msgid "Creating a Persistent Guest Network"
+msgstr "创建一个Persistent客户网络"
+
+# 8ce284f6e33a44e5860a579e00f4fc80
+#: ../../networking2.rst:6925
+msgid "To create a persistent network, perform the following:"
+msgstr "要创建一个Persistent网络，请按如下操作："
+
+# e3ce54a0de2342309210a549828f25b0
+#: ../../networking2.rst:6929
+msgid "Create a network offering with the Persistent option enabled."
+msgstr "创建一个Persistent选项启用的网络方案。"
+
+# 916c1c8c0ef34df2868a5a38c4dd609a
+#: ../../networking2.rst:6931
+msgid ""
+"See `\"Creating a New Network Offering\" <networking.html#creating-a-new-"
+"network-offering>`_."
+msgstr "请参考`\"创建一个新的网络方案\" <networking.html#creating-a-new-network-offering>`_."
+
+# 2fd5e35855fe4fa4bae6d7cc0d53b7d8
+#: ../../networking2.rst:6935
+msgid "Select Network from the left navigation pane."
+msgstr "从左边的导航栏里选择网络。"
+
+# 37e16c8d0d9044dbb0f2d02677062c8d
+#: ../../networking2.rst:6939
+msgid ""
+"Select the guest network that you want to offer this network service to."
+msgstr "选择你希望提供此网络方案服务的客户网络。"
+
+# 5fbd5c95b15941c29f95b337f8ebade8
+#: ../../networking2.rst:6944
+msgid "Click the Edit button."
+msgstr "点击编辑按钮。"
+
+# 706e3f3239cb45f2a6f669847cf5c0ff
+#: ../../networking2.rst:6948
+msgid ""
+"From the Network Offering drop-down, select the persistent network offering "
+"you have just created."
+msgstr "在网络方案下拉列表里，选择你刚才创建的persistent网络方案。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking_and_traffic.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking_and_traffic.mo
new file mode 100644
index 0000000..ac44f4d
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking_and_traffic.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/networking_and_traffic.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking_and_traffic.po
new file mode 100644
index 0000000..7093a23
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/networking_and_traffic.po
@@ -0,0 +1,9580 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:05+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 2e88968824744a699d5b9e641bba935c
+#: ../../networking_and_traffic.rst:18
+msgid "Managing Networks and Traffic"
+msgstr "网络和流量管理"
+
+# 5f4766ac0c9e42fb808ce551ae256f24
+#: ../../networking_and_traffic.rst:20
+msgid ""
+"In a CloudStack, guest VMs can communicate with each other using shared "
+"infrastructure with the security and user perception that the guests have a "
+"private LAN. The CloudStack virtual router is the main component providing "
+"networking features for guest traffic."
+msgstr "在CLOUDSTACK中，客户虚拟机之间可以在共享构架下相互通讯，并且可以在一个私有LAN中实现安全和用户互通。CLOUDSTACK的虚拟路由器是实现客户网络功能的主要组件。"
+
+# 547c4ea0a4df4369904d3e89102a2ff0
+#: ../../networking/guest_traffic.rst:18
+msgid "Guest Traffic"
+msgstr "来宾流量"
+
+# 66d2b2ce8a6e4cd2a1129c71097c9ffd
+#: ../../networking/guest_traffic.rst:20
+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 "在同一个区域内，客户虚拟机之间可以互访，但在不同的区域内，客户虚拟机之间不可以通过（内网）IP地址互访，而只能通过公网IP路由才可以互连。"
+
+# d283edc27a994358b1d82be3efe292b3
+#: ../../networking/guest_traffic.rst:25
+msgid "See a typical guest traffic setup given below:"
+msgstr "下图是一个典型的来宾流量设置："
+
+# 585953ea4f7741d289a4d3930fbea7f8
+#: ../../networking/guest_traffic.rst:27
+msgid "|guest-traffic-setup.png|"
+msgstr "|guest-traffic-setup.png|"
+
+# 231054f3bb304ca8b569aae0ca379d62
+#: ../../networking/guest_traffic.rst:29
+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 router. Its eth2 interface is assigned a"
+" public IP address for public traffic. If multiple public VLAN is used, the "
+"router will have multiple public interfaces."
+msgstr "通常，管理服务会自动为每一个网络建立一个虚拟路由。一个虚拟路由实际上就是运行在物理主机上的一台特殊的虚拟机。每一台在一个独立网络中的虚拟路由有3个网口。如果使用多个公共 VLAN，相应的这台路由器就有多个公共的网口。 它的 eth0 网口是提供客户机通信的网关服务的，它的IP地址是 10.1.1.1。eth1 网口是为系统来配置这个虚拟路由而提供的。eth2 网口被赋予一个公共 IP 地址用来实现外部的公共通信。 同样如果使用了多个公共 VLAN 接入，这台路由器将会拥有多个公共的网口。"
+
+# fac52c70fa3c497faa044acd49d26532
+#: ../../networking/guest_traffic.rst:40
+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 "虚拟路由器提供DHCP功能，能自动的为每一个客户虚拟机在预先定义好的IP范围之内分配IP地址。用户也可以为虚拟机手工配置不同的IP地址。"
+
+# 60254b35a5ca48dcb79bab826da4a5ab
+#: ../../networking/guest_traffic.rst:45
+msgid ""
+"Source NAT is automatically configured in the virtual router to forward "
+"outbound traffic for all guest VMs"
+msgstr "Source NAT功能是在虚拟路由里自动配置好的，它可以转发所有来宾虚拟机的外出流量。"
+
+# ffe1b004a96f43bc974d111d3a433cce
+#: ../../networking/networking_in_pod.rst:18
+msgid "Networking in a Pod"
+msgstr "一个提供点里的网络"
+
+# b0f1a12d5e7543ab99e1e3a70c348c57
+#: ../../networking/networking_in_pod.rst:20
+msgid ""
+"The figure below illustrates network setup within a single pod. The hosts "
+"are connected to a pod-level switch. At a minimum, the hosts should have one"
+" physical uplink to each switch. Bonded NICs are supported as well. The pod-"
+"level switch is a pair of redundant gigabit switches with 10 G uplinks."
+msgstr "下图演示了一个单提供点的网络配置。主机均连接到提供点层级的交换机。每一个主机至少有一个物理网卡连接到交换机。当然，这种环境也支持网卡绑定。提供点层级的交换机由两个1000M冗余组成，它们通过10G线路上联。"
+
+# fa46cc84fe1b4d539c299613f2ea90f8
+#: ../../networking/networking_in_pod.rst:26
+msgid "|networksinglepod.png|"
+msgstr "|networksinglepod.png|"
+
+# 0b80653796454fe7b33fc3de812c6200
+#: ../../networking/networking_in_pod.rst:28
+msgid "Servers are connected as follows:"
+msgstr "服务器以如下形式连接："
+
+# 91c1e31402e44614ac425a77ffd95c12
+#: ../../networking/networking_in_pod.rst:30
+msgid ""
+"Storage devices are connected to only the network that carries management "
+"traffic."
+msgstr "存储设备只与管理网络连接。"
+
+# 7c9c0e94df7a4c19b6cd106477d3162b
+#: ../../networking/networking_in_pod.rst:33
+msgid ""
+"Hosts are connected to networks for both management traffic and public "
+"traffic."
+msgstr "主机同时与管理网络和公共网络连接。"
+
+# ab64d976f00e480885bb92e5d544d3ec
+#: ../../networking/networking_in_pod.rst:36
+msgid ""
+"Hosts are also connected to one or more networks carrying guest traffic."
+msgstr "主机也与一个或多个来宾网络连接。"
+
+# 2d032fc9112345a8b2b9c78d5f64a723
+#: ../../networking/networking_in_pod.rst:39
+msgid ""
+"We recommend the use of multiple physical Ethernet cards to implement each "
+"network interface as well as redundant switch fabric in order to maximize "
+"throughput and improve reliability."
+msgstr "我们推荐用多个物理网卡以改进性能，也推荐用冗余的光纤交换机以改进网络可靠性。"
+
+# 34f26bc9bb954421b5a49ea5148512a1
+#: ../../networking/networking_in_zone.rst:18
+msgid "Networking in a Zone"
+msgstr "一个区域里的网络"
+
+# 42aa6b7f996f49748a02f70fa69cac5d
+#: ../../networking/networking_in_zone.rst:20
+msgid ""
+"The following figure illustrates the network setup within a single zone."
+msgstr "下图说明了一个单一区域内的网络设置。"
+
+# cec13401ef5743db802dc373651f4cee
+#: ../../networking/networking_in_zone.rst:22
+msgid "|networksetupzone.png|"
+msgstr "|networksetupzone.png|"
+
+# caf254a7b27b483ab945007e27ab2454
+#: ../../networking/networking_in_zone.rst:24
+msgid ""
+"A firewall for management traffic operates in the NAT mode. The network "
+"typically is assigned IP addresses in the 192.168.0.0/16 Class B private "
+"address space. Each pod is assigned IP addresses in the 192.168.\\*.0/24 "
+"Class C private address space."
+msgstr "用于管理通信的防火墙工作在NAT模式。通常是分配给网络中的IP地址192.168.0.0/16 B类私有地址空间。每个机柜（POD）分配的IP地址是192.168.*.0/24 C类私有地址空间。"
+
+# 0de7f4a8ad2349cc87a373a814392846
+#: ../../networking/networking_in_zone.rst:29
+msgid ""
+"Each zone has its own set of public IP addresses. Public IP addresses from "
+"different zones do not overlap."
+msgstr "每个区域都有自己的一套公网IP地址。来自不同区域的公网IP地址不重叠。"
+
+# 8133c02743444c1691e584fe82e3dbdb
+#: ../../networking/basic_zone_config.rst:19
+msgid "Basic Zone Physical Network Configuration"
+msgstr "基本区域物理网络配置"
+
+# 501779cb0c9441e4a29799acb6518b3e
+#: ../../networking/basic_zone_config.rst:21
+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 "在一个基本的网络中，物理网络的配置非常直接明了。你只需要配置一个客户网络（虚拟）以承载由客户虚拟机产生的流量。当你首次增加一个区域（Zone）到 CloudStack 中，你通过添加域（Add Zone）页面来设置客户网络（虚拟）。"
+
+# 309e851c308a4e6eb88d0b9cb9eca1a4
+#: ../../networking/advanced_zone_config.rst:19
+msgid "Advanced Zone Physical Network Configuration"
+msgstr "高级区域物理网络的配置"
+
+# 5ba22edac905490bac4351986297202e
+#: ../../networking/advanced_zone_config.rst:21
+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 "在使用复杂网络的区域中，你需要告知管理服务器，为了实现隔离不同类型的通讯，物理网络是如何设置的。"
+
+# 7433a105cf0f4c4a8b5eb2d1b71b5278
+#: ../../networking/advanced_zone_config.rst:27
+msgid "Configure Guest Traffic in an Advanced Zone"
+msgstr "在高级域中设置客户通信"
+
+# 0479d8eccf0646bda9f39cac51ca890c
+#: ../../networking/advanced_zone_config.rst:29
+msgid ""
+"These steps assume you have already logged in to the CloudStack UI. To "
+"configure the base guest network:"
+msgstr "下面的步骤假定你已经登录进入 CloudStack 的界面。设置基本的客户网络："
+
+# 6a02a9096d534a41aa433f728dd55749
+#: ../../networking/advanced_zone_config.rst:32
+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 "在左边的导航栏，选择基础架构。在区域界面点击查看全部，然后点击你要添加网络的区域。"
+
+# 9d184022aba349b2aa9aeb49c5222497
+# e23a8b99ae3d4beb87a9db4e87291025
+# 367ee4d166f843e6b790c71cbbf8f9e3
+#: ../../networking/advanced_zone_config.rst:35
+#: ../../networking/advanced_zone_config.rst:87
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:145
+msgid "Click the Network tab."
+msgstr "点击网络选项卡。"
+
+# 3245c61546fe4a81bc5e6e8a09167804
+# aeb508d106f6462bbdae174ca0a17b83
+# b07a9c22d66f4cd59a846a846778af53
+#: ../../networking/advanced_zone_config.rst:37
+#: ../../networking/advanced_zone_config.rst:89
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:147
+msgid "Click Add guest network."
+msgstr "点击 添加来宾网络。"
+
+# be8bee6943514afda63cb052034b5613
+#: ../../networking/advanced_zone_config.rst:39
+msgid "The Add guest network window is displayed:"
+msgstr "添加来宾网络窗口显示："
+
+# 1c4523333dc64212b845c2b6912c260c
+#: ../../networking/advanced_zone_config.rst:41
+msgid "|addguestnetwork.png|"
+msgstr "|addguestnetwork.png|"
+
+# acadf5b43bd44355836e260ef18944cb
+# 914acc88287948198f6d2e928d524cff
+# 00444541c712470cabb10e4c18d44754
+#: ../../networking/advanced_zone_config.rst:43
+#: ../../networking/remote_access_vpn.rst:311
+#: ../../networking/virtual_private_cloud_config.rst:189
+msgid "Provide the following information:"
+msgstr "填写以下内容："
+
+# 3a472c2f7bd74e88894a25b50b2ecc0b
+#: ../../networking/advanced_zone_config.rst:45
+msgid "**Name**: The name of the network. This will be user-visible"
+msgstr ""
+
+# cd0d4d5ebb2843508a34eef3fa3cbf95
+#: ../../networking/advanced_zone_config.rst:47
+msgid ""
+"**Display Text**: The description of the network. This will be user-visible"
+msgstr "**Display Text**：网络的描述。用户可见"
+
+# 458b580931c147f39c8754144178743c
+#: ../../networking/advanced_zone_config.rst:50
+msgid "**Zone**: The zone in which you are configuring the guest network."
+msgstr "**Zone**: 这里的区域是指你要配置客户网络的区域。"
+
+# 5a598415cdd64826baeb7bf89f1d991e
+#: ../../networking/advanced_zone_config.rst:52
+msgid ""
+"**Network offering**: If the administrator has configured multiple network "
+"offerings, select the one you want to use for this network"
+msgstr "**网络提议**: 如果管理员已经配置了多个网络方案，可以选择你需要的那个"
+
+# 1bd47cc800e74d299fd0a2f14dc79b82
+#: ../../networking/advanced_zone_config.rst:55
+msgid "**Guest Gateway**: The gateway that the guests should use"
+msgstr "**Guest gateway**：虚拟机需要使用的网关"
+
+# dbd235f763be4ac3bd961dfeab6a4119
+#: ../../networking/advanced_zone_config.rst:57
+msgid ""
+"**Guest Netmask**: The netmask in use on the subnet the guests will use"
+msgstr "**Guest Netmask**：客户虚拟机会使用的子网掩码"
+
+# 7a600295ac7141be85b91494277f8bae
+# 1699ac2b1b66466896e3e308100bc131
+# c2b6ddd6457b41cda3df2cbb62cbb901
+# 3929bccca11f489993ac83ea79cc8f48
+# c6b55626cac14e82aa807bfced97b64d
+# 46ab1fed30c44cb386441db1762dd430
+# 4562b7f8a5e64cf78cdd7c58d62866fc
+# 692b7464148b43a49edb927fbd74fd4b
+# 70bd2e1ea0524a7882ca8a0d1d607829
+# a6fb58ce33b74a20894b08e4aeffb48f
+# 3c8f6b6fdfc447fb8ee7f3a409e82bad
+# 7673a522d97348a9bc4533f2c623e3b6
+# e92a6822a63b483d92dfedd0eb104b22
+# d8d73b45f64a4ba0a15a6bf8124841f0
+#: ../../networking/advanced_zone_config.rst:60
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:115
+#: ../../networking/portable_ips.rst:84
+#: ../../networking/multiple_subnets_in_shared_network.rst:95
+#: ../../networking/security_groups.rst:72
+#: ../../networking/global_server_load_balancing.rst:371
+#: ../../networking/ip_forwarding_and_firewalling.rst:215
+#: ../../networking/remote_access_vpn.rst:402
+#: ../../networking/remote_access_vpn.rst:425
+#: ../../networking/virtual_private_cloud_config.rst:211
+#: ../../networking/virtual_private_cloud_config.rst:281
+#: ../../networking/virtual_private_cloud_config.rst:455
+#: ../../networking/virtual_private_cloud_config.rst:479
+#: ../../networking/persistent_networks.rst:94
+msgid "Click OK."
+msgstr "点击确定。"
+
+# c735b3c2a79d4a97ba3b2798068b9032
+#: ../../networking/advanced_zone_config.rst:64
+msgid "Configure Public Traffic in an Advanced Zone"
+msgstr "在高级区域中配置公共通信"
+
+# b6188c4a11a04e4da53e69931cea7e92
+#: ../../networking/advanced_zone_config.rst:66
+msgid ""
+"In a zone that uses advanced networking, you need to configure at least one "
+"range of IP addresses for Internet traffic."
+msgstr "在一个使用高级网络配置的区域中，你需要配置至少一个用于Internet通信的IP地址范围。"
+
+# 382eb9f366b44454835a00e621aa1743
+#: ../../networking/advanced_zone_config.rst:71
+msgid "Configuring a Shared Guest Network"
+msgstr "配置共享的客户网络"
+
+# 017873e7ecfe4402a18cf99f80504c6b
+# a45daa5eec1d4fa68d75831b169fafa5
+# b177d05e7fb54f8ab7429856f854dd16
+#: ../../networking/advanced_zone_config.rst:73
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:54
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:131
+msgid "Log in to the CloudStack UI as administrator."
+msgstr "作为管理员登录到CloudStack用户界面。"
+
+# 84a0ef2ad9f943ad9f91eb6a8abb8ae7
+# 76b78351191646ffa98f8ec8e59fea01
+# ef875cadd3c647089970c4b011189042
+#: ../../networking/advanced_zone_config.rst:75
+#: ../../networking/multiple_subnets_in_shared_network.rst:54
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:133
+msgid "In the left navigation, choose Infrastructure."
+msgstr "在左边的导航，选择基础架构。"
+
+# 06247e8726024f7098ba1a2c8ffb7cd9
+# 4d47e34008e44518b3ce4ffc1d522b5e
+#: ../../networking/advanced_zone_config.rst:77
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:135
+msgid "On Zones, click View More."
+msgstr "在区域页面，点击查看全部。"
+
+# 11a261c7ce9a4280b2283b3420540729
+# a53663a4596d4418b2447b2f34253c13
+#: ../../networking/advanced_zone_config.rst:79
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:137
+msgid "Click the zone to which you want to add a guest network."
+msgstr "选择要添加客户网络的那个区域。"
+
+# ad879d34c24644c6be82095823dd2634
+# f4034b1a820b425bbbd9b51218978bac
+# dda2aaaac56e490da82fb8570abcec7c
+# 7ee99e2d45ac49679a2ffc018fb9bada
+#: ../../networking/advanced_zone_config.rst:81
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:62
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:132
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:139
+msgid "Click the Physical Network tab."
+msgstr "点击物理网络标签卡。"
+
+# 8e7c54c3dff94e4c975465a247fdc749
+# 6904ead432c948b1a353d1a14cf24ba3
+#: ../../networking/advanced_zone_config.rst:83
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:141
+msgid "Click the physical network you want to work with."
+msgstr "选择您要操作的物理网络。"
+
+# 5198c123311c4dedb764b0fad9b75511
+# b6b304bb36064d9795035a047d554897
+#: ../../networking/advanced_zone_config.rst:85
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:143
+msgid "On the Guest node of the diagram, click Configure."
+msgstr "在客户节点界面，点击配置。"
+
+# 9b0560860e8142b6acacce6dee68f77d
+# f66ffb16e9e34d2fab95288ecddbc072
+#: ../../networking/advanced_zone_config.rst:91
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:149
+msgid "The Add guest network window is displayed."
+msgstr "现实添加客户网络窗口。"
+
+# 177f27f031a444b2a8fd7dd381980b4d
+# bf9352536eb942a18db080fc500523d3
+# a08d4b6ba13540ceab3e8058b95f89af
+# bc8ca26c46054b58b949250071678da5
+# 65686255f3e34e33b7c9014b22a1f32c
+# 0d69bb44a42b4273942af07cece87f40
+# 40882d4726394e6eabd4a92f88844717
+# df42ee8c70dc4c80884bb2241dce3ff9
+# 392bb66c4eed477b8f17b7327c094d70
+# 67322aa6283c41329898fae4fcd9d14a
+# f8a7557a036c4c2d9e8a1664f9788eb0
+# 15e16203d42441acbfb55f6d515c2648
+# 7dbdb60b7de340c08a41ac492f5f5f2b
+# c11b631f982340159764b1fc93b73259
+#: ../../networking/advanced_zone_config.rst:93
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:79
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:89
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:107
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:142
+#: ../../networking/portable_ips.rst:70
+#: ../../networking/multiple_subnets_in_shared_network.rst:75
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:151
+#: ../../networking/external_firewalls_and_load_balancers.rst:482
+#: ../../networking/global_server_load_balancing.rst:393
+#: ../../networking/virtual_private_cloud_config.rst:248
+#: ../../networking/virtual_private_cloud_config.rst:539
+#: ../../networking/virtual_private_cloud_config.rst:1062
+#: ../../networking/virtual_private_cloud_config.rst:1330
+msgid "Specify the following:"
+msgstr "指定以下信息："
+
+# 6554135d72104186ad415b989326d68a
+# f5bee2ab4a8a4cd1bb25c20ef7021f7c
+#: ../../networking/advanced_zone_config.rst:95
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:153
+msgid "**Name**: The name of the network. This will be visible to the user."
+msgstr "**Name**: 要建立的网络的名字。这个是用户可见的"
+
+# b63b119a113e499fb649c6b668452512
+# 53f9619369324f10bbc8f0dfb003c5af
+#: ../../networking/advanced_zone_config.rst:97
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:156
+msgid ""
+"**Description**: The short description of the network that can be displayed "
+"to users."
+msgstr "**描述**: 提供一个简短的方案描述。 "
+
+# 7623ee3426cd4a4b8719ca1027787ee0
+# fa610595c19f43feb0a9916b4c61517e
+#: ../../networking/advanced_zone_config.rst:100
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:159
+msgid "**VLAN ID**: The unique ID of the VLAN."
+msgstr "**VLAN ID**: VLAN 的ID。"
+
+# a6a3c73efe124f6690c9949d7466b2cd
+#: ../../networking/advanced_zone_config.rst:102
+msgid "**Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr "**Isolated VLAN ID**: 二级独立 VLAN 的 ID。"
+
+# eb5d4e3b37bb4d94bd1e4ce02cf03368
+# 8401ce13c8b14fc7ba27b4342afc3f7f
+#: ../../networking/advanced_zone_config.rst:105
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:167
+msgid "**Scope**: The available scopes are Domain, Account, Project, and All."
+msgstr "**Scope**: 可用的范围，包括域，帐户，项目和其他所以。"
+
+# 484bd18b48f64d8190817eb10bf25d94
+# 7991b529beef453ba5728f8ca2b2b220
+#: ../../networking/advanced_zone_config.rst:108
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:170
+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 "**Domain**: 域，指定客户网络范围的域。指定域中的网络相对其他域是隔离不可见的。如果指定子域访问，域中的客户网络将在所有的子域中可用。"
+
+# 252ca851074346a6be3e6f4c74f7834d
+# 621835256ebd4c57a89c9353ef9852f2
+#: ../../networking/advanced_zone_config.rst:114
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:176
+msgid ""
+"**Account**: The account for which the guest network is being created for. "
+"You must specify the domain the account belongs to."
+msgstr "**Account**: 这里的帐户是为建立客户网络所指定的。必须指定域中所属的帐户。"
+
+# 0ab56139ecb94d0e8c9655e557cb946c
+# d4a5c2d9539246839f4dd99383968ef9
+#: ../../networking/advanced_zone_config.rst:118
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:180
+msgid ""
+"**Project**: The project for which the guest network is being created for. "
+"You must specify the domain the project belongs to."
+msgstr "**Project**: 项目是客户网络所建立的项目。必须为这个项目指定域。"
+
+# 2b9a0513ff7e422db20b3251b2fbe195
+# 0f2a1593be4f484781fdadc2f41437da
+#: ../../networking/advanced_zone_config.rst:122
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:184
+msgid ""
+"**All**: The guest network is available for all the domains, account, "
+"projects within the selected zone."
+msgstr "**All**: 选择它，会让客户网络对这个区域（Zone）中的所有域，帐户和项目都可用。"
+
+# ca6ea5abd11c4e1788e84dfe1bff99a2
+# d3110bc74ceb49d3be22fc9aae58619b
+#: ../../networking/advanced_zone_config.rst:125
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:187
+msgid ""
+"**Network Offering**: If the administrator has configured multiple network "
+"offerings, select the one you want to use for this network."
+msgstr "**网络提议**: 如果管理员已经配置了多个网络方案，可以选择你需要的那个。"
+
+# f51f569ac91a494caa7f8c799bfdbb9f
+# a9df4480acb64d5bbd3f3ceef50ef146
+#: ../../networking/advanced_zone_config.rst:129
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:191
+msgid "**Gateway**: The gateway that the guests should use."
+msgstr "**Guest gateway**: 虚拟机需要使用的网关。"
+
+# 1a04acb9a38148f68b32c27969c45f73
+# 283222bd73704d83b1a3edb949df0350
+#: ../../networking/advanced_zone_config.rst:131
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:193
+msgid "**Netmask**: The netmask in use on the subnet the guests will use."
+msgstr "**Netmask**: 虚拟机子网要使用的网络掩码。"
+
+# 615ae59795614770a2544f5a3b35cd87
+# 3564dbe5dcda4549a0101e20522adce2
+#: ../../networking/advanced_zone_config.rst:133
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:195
+msgid ""
+"**IP Range**: A range of IP addresses that are accessible from the Internet "
+"and are assigned to the guest VMs."
+msgstr "**IP Range**: 定义公网IP范围，这些IP用来访问公网或是从公网访问客户虚拟机。"
+
+# 83b96bd50ac546028d9179711930d8b4
+#: ../../networking/advanced_zone_config.rst:136
+msgid ""
+"If one NIC is used, these IPs should be in the same CIDR in the case of "
+"IPv6."
+msgstr "如果使用了网卡，这些IP应该在相同的IPv6的CIDR中。"
+
+# e8f7fd43c9964fb39020455720c2ace1
+#: ../../networking/advanced_zone_config.rst:139
+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 "**IPv6 CIDR**: 用于定义网络子网的网络前缀。"
+
+# 447ec4231b6249d0a2be7e648cf05a4b
+# 9f34c3ebe1d44cc59d6246b9e1ef1cc6
+#: ../../networking/advanced_zone_config.rst:144
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:198
+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 "**网络域**: 如果你想为客户虚机网络定义一个域名，在此处输入后缀名。"
+
+# 47c08e953e5a4dc6a1fea963aef82e35
+# eda271a950a6423f91f6019045850a96
+# 6866ffd602874da0a27c9d867eef7121
+# 0d2313e6a2b24e99a9800598ca9f6d0a
+# 210ec4b443e34cedbeb2ac91183bbc9e
+#: ../../networking/advanced_zone_config.rst:148
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:202
+#: ../../networking/global_server_load_balancing.rst:415
+#: ../../networking/global_server_load_balancing.rst:439
+#: ../../networking/remote_access_vpn.rst:555
+msgid "Click OK to confirm."
+msgstr "点击确定。"
+
+# 62aeac41fec848808050e2e871a2b129
+#: ../../networking/multiple_guest_networks.rst:18
+msgid "Using Multiple Guest Networks"
+msgstr "使用多个来宾网络"
+
+# 173b4dafa8a24c8d8ef490a9e5d1a2a3
+#: ../../networking/multiple_guest_networks.rst:20
+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 "在使用高级网络的资源域里, 额外的来宾网络可以在初始安装后任何时间添加. 你还可以通过指定DNS后缀为每个网络自定义关联的域名."
+
+# c8b83803c190449586b842e47655e008
+#: ../../networking/multiple_guest_networks.rst:25
+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 "一个虚机的网络在其创建时定义. 当一个虚机创建以后, 就不能对其网络添加删除, 即便用户可以进入客户虚机删除指定网卡的IP地址."
+
+# 71b0ed98702b4b929a15ba55f3aa6352
+#: ../../networking/multiple_guest_networks.rst:30
+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 "每一个虚机只有一个默认的网络. 在这个默认网络里, 虚拟路由器的DHCP响应将设置客户的默认网关. 除了单一,必须的默认网络, 多个非默认的网络也可以添加到客户虚机里. 管理员可以控制哪个网络作为默认的网络."
+
+# 849cc36464bd447d99a2d270e0b8c0b3
+#: ../../networking/multiple_guest_networks.rst:36
+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 "附加的网络可以给所有账户使用或者分配给特定的账户. 对所有账户都可用的网络在整个资源域有效. 任何可以访问这个资源域的用户都可以使用这个网络创建虚机. 这些资源域一级的网络基本不提供客户之间的隔离. 分配给特定帐户的网络提供强制隔离的功能."
+
+# a3fc8a922f68476db11bacc83c025d3d
+#: ../../networking/multiple_guest_networks.rst:45
+msgid "Adding an Additional Guest Network"
+msgstr "增添一个虚拟机的网络"
+
+# dc6276841e84471ba268d113e94e1fde
+# cbab5080c8724ae6b32d638711c47ad3
+# 48fc29cc7efc4b409a45c98ead6968af
+# ace2e79a21274181a0e6a1418b773520
+# 6befffe2a21747639acd37de4675a94a
+# f5963e2398134322866f292a2ba5637c
+# 551332081c79467bb0b0ae8d270e12fc
+# ecb9ef417cf8480db8b57ca2d9f61454
+# ce46c3a278f44eb5b1e7654fa8161e03
+# 9424276887a84ee99fd0b5822bdcd91a
+# cf03db0555ba4247b9b9cf2b658dc39c
+# 3e08d28b8e2f41d18f75caa20d66f640
+# 16776cbc4ef94f86a8459cd47cf975b6
+# 5d6031b242154874a2eea237547f4e27
+# 4556ff5dc1a74038a41b53936c78f484
+# 671400e41c7c4103bbcba44d13f5f1da
+# 62daba2f10ce4203b9a4ace43acaf3e6
+# 349c3fc0ae0045c091b01248f7139bd9
+# 6488b7ea43c743ea94940e1c1f3f2898
+# 3eb6a0e839144aac93bd3202f87081a4
+# 16a312e861604ecca8b56044c71267a5
+# 6a8b51d9d05c4ac48c274e364f981a83
+# d5aee6dabdd249118c7128383890359b
+# 5c15fdde88e743f4b18aea3fe127d933
+# 7a23456b027045198970bd22c7e8c26d
+# 2e31addff9374029b171be7e6159ce7e
+# 4e46d0a70f45414098f422f177f3ac81
+# 285f7a9fc04f4d6489fda4d6a5f605bb
+# 6803fb7ef5e947a19da33579f371d0fa
+# 989f403b307946939b500439893373fa
+# f3ea7727060d4b25b4a675666aa53047
+# 1c9c88a759cd4868990e4b477dc4a97f
+# 8fac984de8c04571aed052d41660d304
+# 155c85bc6c6c471c8933826c53d412db
+# a87fa80f420b452a9c4e0fb44344cd64
+# de7a6e86366d4763b6ed6974061246e9
+# 8e1be4aa91664f038b1f00940c6fef85
+# a9f7303f7b5c4984a44ef3c6a938123e
+#: ../../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
+#: ../../networking/ip_reservation_in_guest_networks.rst:106
+#: ../../networking/portable_ips.rst:58 ../../networking/portable_ips.rst:90
+#: ../../networking/multiple_subnets_in_shared_network.rst:52
+#: ../../networking/security_groups.rst:62
+#: ../../networking/security_groups.rst:124
+#: ../../networking/external_firewalls_and_load_balancers.rst:255
+#: ../../networking/acquiring_an_ip_address.rst:20
+#: ../../networking/releasing_an_ip_address.rst:24
+#: ../../networking/static_nat.rst:36
+#: ../../networking/ip_forwarding_and_firewalling.rst:59
+#: ../../networking/ip_forwarding_and_firewalling.rst:132
+#: ../../networking/ip_forwarding_and_firewalling.rst:245
+#: ../../networking/remote_access_vpn.rst:59
+#: ../../networking/remote_access_vpn.rst:301
+#: ../../networking/remote_access_vpn.rst:411
+#: ../../networking/remote_access_vpn.rst:431
+#: ../../networking/remote_access_vpn.rst:493
+#: ../../networking/remote_access_vpn.rst:624
+#: ../../networking/virtual_private_cloud_config.rst:179
+#: ../../networking/virtual_private_cloud_config.rst:223
+#: ../../networking/virtual_private_cloud_config.rst:331
+#: ../../networking/virtual_private_cloud_config.rst:380
+#: ../../networking/virtual_private_cloud_config.rst:492
+#: ../../networking/virtual_private_cloud_config.rst:662
+#: ../../networking/virtual_private_cloud_config.rst:729
+#: ../../networking/virtual_private_cloud_config.rst:788
+#: ../../networking/virtual_private_cloud_config.rst:848
+#: ../../networking/virtual_private_cloud_config.rst:1014
+#: ../../networking/virtual_private_cloud_config.rst:1227
+#: ../../networking/virtual_private_cloud_config.rst:1282
+#: ../../networking/virtual_private_cloud_config.rst:1360
+#: ../../networking/virtual_private_cloud_config.rst:1388
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# 237757a1c35441d4b6a1d0138d51de32
+# 39b4377eadca44f88700dca104d2f2a4
+# 14e144b6e7d84af79103518642863237
+# e38926ea76d24deabf34f94cc6156141
+# 1cafa5021f254ccdb3e66342906cbbe0
+# 76644abeaf9b49d48e5c26fd3863d65d
+# fd119509867a413eb5b071e9da496e8e
+# 957b74b12b1a45c7b9b8114b38f97d77
+# aa4565d6e2ed407b960640041eb584ff
+# 4e76e138c9884ac8beba173f7412d536
+# 44488e4d095a4f2d8266449c8307fc21
+# af7438793b9e44748cabc8348e59fda1
+# 4eb14251b140410c9af761d030914dc5
+# 60c4993c8a9a4e568ee599adb94f496d
+# ac22aded37484d4f98a0e5a40819d801
+# 8cc4478d868544b9848e14dfbd88437c
+# 7c473fc1dc29485bab80620cb5516658
+# 5719d26cc6b34a00b95be2ce35247df4
+# 10dbf0d03759490a8446988e520c079c
+# 92cb7c01ff9f4be098792e0ef2848938
+# fd1c21fdf57f4352984d33f74a0ffe94
+# 10c9ca3bb4e64794961df411c87283c0
+# 9ceabecc68364512ba46aba32daf9204
+# d77f1f6f348745e08a97c31b73820e52
+# f7bed0f61bd84981b3ec3692340f0005
+# 9981e33a734c445c98a725f067fc9940
+# e068bf6b3bc14e1b90f2154ebf50cc7f
+# 37ca9de5ef034ad4a025068c67b7cda8
+# 3f72ad0b7cf24c6cad9063dd0771a6b0
+# 52a95f6853b440feb680fdfbf7854d1e
+#: ../../networking/multiple_guest_networks.rst:49
+#: ../../networking/multiple_guest_networks.rst:179
+#: ../../networking/ip_reservation_in_guest_networks.rst:108
+#: ../../networking/portable_ips.rst:92
+#: ../../networking/security_groups.rst:64
+#: ../../networking/external_firewalls_and_load_balancers.rst:257
+#: ../../networking/acquiring_an_ip_address.rst:22
+#: ../../networking/releasing_an_ip_address.rst:26
+#: ../../networking/static_nat.rst:38
+#: ../../networking/ip_forwarding_and_firewalling.rst:61
+#: ../../networking/ip_forwarding_and_firewalling.rst:134
+#: ../../networking/remote_access_vpn.rst:303
+#: ../../networking/remote_access_vpn.rst:413
+#: ../../networking/remote_access_vpn.rst:433
+#: ../../networking/remote_access_vpn.rst:495
+#: ../../networking/remote_access_vpn.rst:626
+#: ../../networking/virtual_private_cloud_config.rst:181
+#: ../../networking/virtual_private_cloud_config.rst:225
+#: ../../networking/virtual_private_cloud_config.rst:333
+#: ../../networking/virtual_private_cloud_config.rst:382
+#: ../../networking/virtual_private_cloud_config.rst:494
+#: ../../networking/virtual_private_cloud_config.rst:664
+#: ../../networking/virtual_private_cloud_config.rst:731
+#: ../../networking/virtual_private_cloud_config.rst:790
+#: ../../networking/virtual_private_cloud_config.rst:850
+#: ../../networking/virtual_private_cloud_config.rst:1016
+#: ../../networking/virtual_private_cloud_config.rst:1229
+#: ../../networking/virtual_private_cloud_config.rst:1284
+#: ../../networking/virtual_private_cloud_config.rst:1362
+#: ../../networking/virtual_private_cloud_config.rst:1390
+msgid "In the left navigation, choose Network."
+msgstr "在左侧的导航栏，选择网络。"
+
+# cb6079f81a4a444c8445b03dfffb3384
+#: ../../networking/multiple_guest_networks.rst:51
+msgid "Click Add guest network. Provide the following information:"
+msgstr "地阿基添加来宾网络。提供以下信息："
+
+# a733015f94ce486a85c1b03cddfbc38d
+#: ../../networking/multiple_guest_networks.rst:53
+msgid "**Name**: The name of the network. This will be user-visible."
+msgstr "**Name**：网络的名称。对于最终用户可见。"
+
+# c09b04d766c44686adfb027006335ba6
+#: ../../networking/multiple_guest_networks.rst:55
+msgid ""
+"**Display Text**: The description of the network. This will be user-visible."
+msgstr "**Display Text**:网络的描述信息。对于最终用户可见。"
+
+# 2c86bf84ff20496e9c0dbae8475b8796
+#: ../../networking/multiple_guest_networks.rst:58
+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 "**Zone**：此网络所应用到zone的名称。每个zone都是一个广播域，因此每个zone中的来宾网络都有不同的IP范围。管理员必须为每个zone配置IP范围。"
+
+# afa6888ba15346988e310755527a9c8c
+#: ../../networking/multiple_guest_networks.rst:63
+msgid ""
+"**Network offering**: If the administrator has configured multiple network "
+"offerings, select the one you want to use for this network."
+msgstr "**Network offering**: 如果管理员已经配置了多个网络，选择一个你想使用的。"
+
+# 7f1d89fa4b5b43eabe3a6dcd6a33dfeb
+#: ../../networking/multiple_guest_networks.rst:67
+msgid "**Guest Gateway**: The gateway that the guests should use."
+msgstr "**Guest Gateway**: 来宾网络的网关。"
+
+# b882e804c5a845c2bb51f84c46f7e4b2
+#: ../../networking/multiple_guest_networks.rst:69
+msgid ""
+"**Guest Netmask**: The netmask in use on the subnet the guests will use."
+msgstr "**Guest Netmask**: 来宾网络的子网掩码。"
+
+# fae38490ef9a46b1849e4b2335cc0fed
+# 78b272d2f17d4c2aa5e3c38757550038
+#: ../../networking/multiple_guest_networks.rst:72
+#: ../../networking/remote_access_vpn.rst:186
+msgid "Click Create."
+msgstr "点击创建。"
+
+# 89ec799633d344d9a83b6db46a6c828c
+#: ../../networking/multiple_guest_networks.rst:76
+msgid "Reconfiguring Networks in VMs"
+msgstr "在VMs中重新配置网络"
+
+# a88f5c6d61374a3b928e78e6b1ea34aa
+#: ../../networking/multiple_guest_networks.rst:78
+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 "CloudStack能让你在不同网络间移动VMs和重新配置VM的网络。你可以从一个网络中移除一个VM，再将其移动到另一个网络。你同样可以修改虚拟机的默认我拿过来，使用这个功能，混合和传统的服务器负载可以被轻松缓解。"
+
+# 2316dff2f40f4d3f86f201bc60758648
+#: ../../networking/multiple_guest_networks.rst:84
+msgid "This feature is supported on XenServer, VMware, and KVM hypervisors."
+msgstr "XenServer、VMware和KVM hypervisors支持这个特性。"
+
+# 616dba5e33b041d58b10b5d6e07ee798
+# 537bba5fd9ca4e46a540acdaa254af70
+# cedaba73cb0d47a88420f975227d5918
+#: ../../networking/multiple_guest_networks.rst:88
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:97
+#: ../../networking/external_firewalls_and_load_balancers.rst:428
+msgid "Prerequisites"
+msgstr "先决条件"
+
+# 96d0ba198631458b9ed9d4fa9ed7a7e8
+#: ../../networking/multiple_guest_networks.rst:90
+msgid ""
+"Ensure that vm-tools are running on guest VMs for adding or removing "
+"networks to work on VMware hypervisor."
+msgstr "确保虚拟机上安装了vm-tools以便通过VMware hypervisor添加或移除网络。"
+
+# 0329f8bc61c245c990fbec99fc953f92
+#: ../../networking/multiple_guest_networks.rst:95
+msgid "Adding a Network"
+msgstr "添加网络"
+
+# 97b216f50e31423b9810c721a305ff6a
+# 9a2142ffcdd841c6add827da072540a3
+# 472370d3518e4d43897027152ff4f4a4
+#: ../../networking/multiple_guest_networks.rst:99
+#: ../../networking/multiple_guest_networks.rst:137
+#: ../../networking/multiple_guest_networks.rst:155
+msgid "In the left navigation, click Instances."
+msgstr "在左侧的导航菜单中，点击实例。"
+
+# a42801e9f96a4b12aef748033faea01f
+# 81f21ab3baef4f45b105fc9089d4e0d3
+# 635dc740070544bc8307380af26d34fa
+#: ../../networking/multiple_guest_networks.rst:101
+#: ../../networking/multiple_guest_networks.rst:139
+#: ../../networking/multiple_guest_networks.rst:157
+msgid "Choose the VM that you want to work with."
+msgstr "选择你要处理的VM。"
+
+# 6bac6d526e3d4904baf4586d1d888847
+# fc1fad0459ba46678afe706a5a01d3e2
+# 1975c5cefdba4f0e8aeb59dd9eace947
+#: ../../networking/multiple_guest_networks.rst:103
+#: ../../networking/multiple_guest_networks.rst:141
+#: ../../networking/multiple_guest_networks.rst:159
+msgid "Click the NICs tab."
+msgstr "点击网络适配器标签。"
+
+# 4fab29c3388c444694883cc767e38d1a
+#: ../../networking/multiple_guest_networks.rst:105
+msgid "Click Add network to VM."
+msgstr "将网络添加到 VM"
+
+# 2607dcbcf15f4c8dafde44a5570a2766
+#: ../../networking/multiple_guest_networks.rst:107
+msgid "The Add network to VM dialog is displayed."
+msgstr "显示添加网络对话框。"
+
+# 078937d5a79043d497e0b24671ff352d
+#: ../../networking/multiple_guest_networks.rst:109
+msgid ""
+"In the drop-down list, select the network that you would like to add this VM"
+" to."
+msgstr "在下拉列表里选择你要添加给VM的网络。"
+
+# 45834b3a55d14caebf167b7bd28ebd2f
+#: ../../networking/multiple_guest_networks.rst:112
+msgid ""
+"A new NIC is added for this network. You can view the following details in "
+"the NICs page:"
+msgstr "这样就为这个网络添加了一个新网卡。你可以在网卡页面查看下列信息："
+
+# 2e97354cbec940b796eec8b025dc982e
+#: ../../networking/multiple_guest_networks.rst:115
+msgid "ID"
+msgstr "ID"
+
+# 122b599d9d7d4f8c8fb462bd0c5b5f2e
+#: ../../networking/multiple_guest_networks.rst:117
+msgid "Network Name"
+msgstr "网络名称"
+
+# 6766a85b557b460c8955aa3fb09bfb8d
+#: ../../networking/multiple_guest_networks.rst:119
+msgid "Type"
+msgstr "类型"
+
+# 3bd581b01cb243438e2e27273acdbedf
+# 5933f737b419411fa7207a44b3bdea6a
+# 940af38d78dc494ab2ad01f61aafe5d1
+#: ../../networking/multiple_guest_networks.rst:121
+#: ../../networking/remote_access_vpn.rst:481
+#: ../../networking/remote_access_vpn.rst:561
+msgid "IP Address"
+msgstr "IP地址"
+
+# daa389d546724738b57068be58e101d3
+# 95d8f0e06cb94200ae5681c2d2a96628
+#: ../../networking/multiple_guest_networks.rst:123
+#: ../../networking/remote_access_vpn.rst:563
+msgid "Gateway"
+msgstr "网关"
+
+# c39faf6b191042feb2d8ef693d09e473
+#: ../../networking/multiple_guest_networks.rst:125
+msgid "Netmask"
+msgstr "子网掩码"
+
+# 84a7fde285214a59a6105b424d0e3616
+#: ../../networking/multiple_guest_networks.rst:127
+msgid "Is default"
+msgstr "默认的"
+
+# 7689a2a82f5c496e89049b4c6c30a8a0
+#: ../../networking/multiple_guest_networks.rst:129
+msgid "CIDR (for IPv6)"
+msgstr "CIDR（IPv6）"
+
+# 8d0db3320eaf4c88be0ac3e518bfb002
+#: ../../networking/multiple_guest_networks.rst:133
+msgid "Removing a Network"
+msgstr "移除网络"
+
+# 5aa8d15ef25e4b49b6eebcd1275b2a27
+#: ../../networking/multiple_guest_networks.rst:143
+msgid "Locate the NIC you want to remove."
+msgstr "找到你要移除的网卡上。"
+
+# 839f1682ea074a07990190ec500a473f
+#: ../../networking/multiple_guest_networks.rst:145
+msgid "Click Remove NIC button. |remove-nic.png|"
+msgstr "点击移除网卡按钮。|remove-nic.png|"
+
+# 00cc631ddf71493784b992fb54efb226
+# aba902f0e4d940768424cda703f41a00
+#: ../../networking/multiple_guest_networks.rst:147
+#: ../../networking/multiple_guest_networks.rst:165
+msgid "Click Yes to confirm."
+msgstr "点击Yes确认。"
+
+# 4628fde155ff46dab3f60b7acb743a7a
+#: ../../networking/multiple_guest_networks.rst:151
+msgid "Selecting the Default Network"
+msgstr "选择默认网络"
+
+# cd2ff5578eb8448fb8960115c581a240
+#: ../../networking/multiple_guest_networks.rst:161
+msgid "Locate the NIC you want to work with."
+msgstr "找到你想要的网卡。"
+
+# b267fb4c8ea944a896d8494196363127
+#: ../../networking/multiple_guest_networks.rst:163
+msgid "Click the Set default NIC button. |set-default-nic.png|."
+msgstr "点击设置为默认网卡按钮。 |set-default-nic.png|."
+
+# b1e087e064cd4c8ebe77979cdeb59029
+#: ../../networking/multiple_guest_networks.rst:168
+msgid "Changing the Network Offering on a Guest Network"
+msgstr "在来宾网络上更改网络方案"
+
+# 98f57e4d0fe143c39ec77fdc7afbbc1a
+#: ../../networking/multiple_guest_networks.rst:170
+msgid ""
+"A user or administrator can change the network offering that is associated "
+"with an existing guest network."
+msgstr "用户或者管理员可以更改与之相关的来宾网络的网络方案。"
+
+# 8c3a2eaed1fa46a09bab8a2fb9394033
+#: ../../networking/multiple_guest_networks.rst:175
+msgid ""
+"If you are changing from a network offering that uses the CloudStack virtual"
+" router to one that uses external devices as network service providers, you "
+"must first stop all the VMs on the network."
+msgstr "如果你将使用CloudStack虚拟路由的一个网络方案改成使用公共网络设备作为网络服务商，那么你必须先关掉该网络中的所有虚机。"
+
+# deb6cb39e0f942ef8537ff0805aee20c
+# d19c0a1a49dd41129e10a67ab3d452dc
+#: ../../networking/multiple_guest_networks.rst:181
+#: ../../networking/ip_reservation_in_guest_networks.rst:110
+msgid "Click the name of the network you want to modify."
+msgstr "点击你要修改的网络名称。"
+
+# ecccedf20bf340e2ba7ead538934109d
+#: ../../networking/multiple_guest_networks.rst:183
+msgid "In the Details tab, click Edit. |edit-icon.png|"
+msgstr "在 详细 页签，点击 编辑按钮。|edit-icon.png|"
+
+# edc1fb28dc1b449cacf52a30f5e913b6
+#: ../../networking/multiple_guest_networks.rst:185
+msgid ""
+"In Network Offering, choose the new network offering, then click Apply."
+msgstr "在网络方案中，选择新的网络方案，然后点击应用。"
+
+# 19df93b01dc24fd594f644c960aac9d3
+#: ../../networking/multiple_guest_networks.rst:188
+msgid ""
+"A prompt is displayed asking whether you want to keep the existing CIDR. "
+"This is to let you know that if you change the network offering, the CIDR "
+"will be affected."
+msgstr "这时会有一个提示问你是否保持已存在的CIDR不变。这是让你了解如果你改变网络了方案，那么CIDR会受到影响。"
+
+# 31721f214c5b41e0902e0192cb732fd2
+#: ../../networking/multiple_guest_networks.rst:192
+msgid ""
+"If you upgrade between virtual router as a provider and an external network "
+"device as provider, acknowledge the change of CIDR to continue, so choose "
+"Yes."
+msgstr "如果你将虚拟路由升级到外网设备，在看到变更CIDR以继续时，请选择Yes。"
+
+# 3bd6b923a2f64dfe984b12e9d7a9989a
+#: ../../networking/multiple_guest_networks.rst:196
+msgid ""
+"Wait for the update to complete. Don't try to restart VMs until the network "
+"change is complete."
+msgstr "等待更新完成。在网络变更完成之前不要试图重启虚拟机。"
+
+# 33336e86a2f748f6a87662d9f20dc804
+#: ../../networking/multiple_guest_networks.rst:199
+msgid "If you stopped any VMs, restart them."
+msgstr "如果你停止了任何VMs，请重启他们。"
+
+# 685effa0d8104882b0a30dc6b824029a
+#: ../../networking/ip_reservation_in_guest_networks.rst:18
+msgid "IP Reservation in Isolated Guest Networks"
+msgstr "隔离的来宾网络中的预留IP"
+
+# 359e7f6b58f44d209b72518d79eaa4a1
+#: ../../networking/ip_reservation_in_guest_networks.rst:20
+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 "在隔离的来宾网络中，来宾IP地址空间中的一部分可以被保留下来以供非CloudStack VMs或者物理服务器使用。要真么做，你应该在来宾网络应用状态时依靠指定CIDR来配置一个预留IP地址范围。如果你的客户希望在同一个网络中有非CloudStack控制的VMs或者物理服务器，它们可以共享一部分主要为来宾网络提供的IP地址空间。"
+
+# e20dc9218ab14a249b1976460b6ff50e
+#: ../../networking/ip_reservation_in_guest_networks.rst:28
+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 called Reserved IP Range. When IP "
+"reservation is configured, the administrator can add additional VMs or "
+"physical servers that are not part of CloudStack to the same network and "
+"assign them the Reserved IP addresses. CloudStack guest VMs cannot acquire "
+"IPs from the Reserved IP Range."
+msgstr "在高级域中，定义一个网络时要给其赋予一个IP地址范围或CIDR。CloudStack虚拟路由器起着DHCP的作用，并通过CIDR来给客户虚拟机分配IP地址。如果为了预留CIDR不用于cloudstack，应当进行说明，即部分IP地址范围或CIDR仅能被DHCP服务分配给在cloudstack中创建的虚拟机。剩下的IP地址被称作预留IP地址范围。当预留的IP被配置时，管理员可以增加额外的虚拟机或并不属于cloudstack的物理服务器到同一个网络，可以将预留的IP地址指定给他们。cloudstack的客户虚拟机不能够从预留的IP地址中获得地址。"
+
+# aa0353a0869b430a9e00cc950d697674
+#: ../../networking/ip_reservation_in_guest_networks.rst:43
+msgid "IP Reservation Considerations"
+msgstr "IP预留事项"
+
+# 22d783b25a1a4a81835a9f474578360d
+#: ../../networking/ip_reservation_in_guest_networks.rst:45
+msgid ""
+"Consider the following before you reserve an IP range for non-CloudStack "
+"machines:"
+msgstr "在给非cloudstack内的机器预留IP地址时，要考虑以下几个方面："
+
+# 0b76d0acbe274475b3d5501612754809
+#: ../../networking/ip_reservation_in_guest_networks.rst:48
+msgid "IP Reservation is supported only in Isolated networks."
+msgstr "IP预留仅在隔离网络内支持"
+
+# 5bc6f26160614e04a5e091d9ce7f7b41
+#: ../../networking/ip_reservation_in_guest_networks.rst:50
+msgid ""
+"IP Reservation can be applied only when the network is in Implemented state."
+msgstr "仅当网络在实施状态时，IP预留才能被应用。"
+
+# ab5412a6ce1d4c0cb3eef49dfab3e255
+#: ../../networking/ip_reservation_in_guest_networks.rst:53
+msgid "No IP Reservation is done by default."
+msgstr "默认不做IP预留。"
+
+# 428a3fe4ee25419a968877cb3d6e16e8
+#: ../../networking/ip_reservation_in_guest_networks.rst:55
+msgid "Guest VM CIDR you specify must be a subset of the network CIDR."
+msgstr "指定客户的CIDR必须是网络CIDR的子网。"
+
+# 172c915bb06f46d498d3fc10f4f49011
+#: ../../networking/ip_reservation_in_guest_networks.rst:57
+msgid ""
+"Specify a valid Guest VM CIDR. IP Reservation is applied only if no active "
+"IPs exist outside the Guest VM CIDR."
+msgstr "指定一个有效的客户虚拟机CIDR。只有不活动的IP在客户虚拟机CIDR存在时，IP预留才能被应用。"
+
+# 0e5b7bff020d494b9f4e85c641380036
+#: ../../networking/ip_reservation_in_guest_networks.rst:60
+msgid ""
+"You cannot apply IP Reservation if any VM is alloted with an IP address that"
+" is outside the Guest VM CIDR."
+msgstr "如果任一虚拟机被分配了客户虚拟机CIDR之外的IP地址时，IP预留将不能应用。"
+
+# dd5d34dcc85b438e9f317da8db24673b
+#: ../../networking/ip_reservation_in_guest_networks.rst:63
+msgid ""
+"To reset an existing IP Reservation, apply IP reservation by specifying the "
+"value of network CIDR in the CIDR field."
+msgstr "为重置一个已存在的IP预留，通过在CIDR框指定CIDR值就可应用IP预留。"
+
+# 56f3f34b92224637b58c7c86bb310fd1
+#: ../../networking/ip_reservation_in_guest_networks.rst:66
+msgid ""
+"For example, the following table describes three scenarios of guest network "
+"creation:"
+msgstr "例如，下表描述了客户网络创建的三种情形："
+
+# 96cbc8ccee6044a3a4e224d82dda12dd
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+msgid "Case"
+msgstr "案例"
+
+# 2982ca1c12bf49f2866744193ff6f578
+# f16720ba82ad472da40e8ad034254fe4
+# 24dfa509e12d4af98062dd3ae0b48f52
+# 8e4bbd56239d4c71954370d8ef6e8cbe
+# 1f15602058a04c8ebef82e324bb336e6
+# 9ba99b464c2a41bdbe57d55fafae2ccb
+# ebb32770ece6425e9748b0b6a9e2f681
+# ddc08af8ce4f4978a487c0467816270a
+# 642e10bd685b467ead08d1a5a1df5a5f
+# 4060fb167ecd47c882155784f918a887
+# 4c47fa58c98943ec8448eb44ecf621c2
+# 2bf6e84c5f66458f9ed8b4566d751075
+# 606de62e4a0643e89e7cc0809decf0d1
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+#: ../../networking/remote_access_vpn.rst:122
+#: ../../networking/remote_access_vpn.rst:456
+#: ../../networking/remote_access_vpn.rst:519
+#: ../../networking/remote_access_vpn.rst:651
+#: ../../networking/virtual_private_cloud_config.rst:321
+#: ../../networking/virtual_private_cloud_config.rst:352
+#: ../../networking/virtual_private_cloud_config.rst:519
+#: ../../networking/virtual_private_cloud_config.rst:754
+#: ../../networking/virtual_private_cloud_config.rst:812
+#: ../../networking/virtual_private_cloud_config.rst:873
+#: ../../networking/virtual_private_cloud_config.rst:1039
+#: ../../networking/virtual_private_cloud_config.rst:1307
+msgid "CIDR"
+msgstr "CIDR"
+
+# d4529e4573f1422e89f8705d72b14fa6
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+msgid "Network CIDR"
+msgstr "网络CIDR"
+
+# 8717091b7d574910ae7f7db398dec4df
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+msgid "Reserved IP Range for Non-CloudStack VMs"
+msgstr "非cloudstack虚拟机的IP预留范围"
+
+# f596416e0a6849629c21a6b74715913c
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+msgid "Description"
+msgstr "描述"
+
+# 3982ebcb186c4a28bf3ffa4552438c72
+# 15b7293e51984eb1be8bb66b8d99d6e1
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+#: ../../networking/virtual_private_cloud_config.rst:323
+msgid "1"
+msgstr "1"
+
+# f627b7351048414296987b276f691d64
+# 696d3ab791fa4146be4d6793d9894204
+# df688c92b303499f87d27d2a6fda5fc3
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+msgid "10.1.1.0/24"
+msgstr "10.1.1.0/24"
+
+# a5a742b38ae847cb99bd9339c2d47e94
+# 332c38a7b5df4f1ca82b88c659c623bd
+# 8adf0d6c1d72460eb7310b93522b0346
+# d4268a954eb94931af19f1c48598c309
+#: ../../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
+msgid "None"
+msgstr "无"
+
+# f2eddeac640e48e5b16991ce8b7bfa93
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+msgid "No IP Reservation."
+msgstr "无"
+
+# 5bb07f152b264e86ae6eda03cc31e1c1
+# f5f2048cf9714b9ea68d2049570c4f6c
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+#: ../../networking/virtual_private_cloud_config.rst:324
+msgid "2"
+msgstr "2"
+
+# 01110998a1c74b3c80ef1a4dc83268a1
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+msgid "10.1.1.0/26"
+msgstr "10.1.1.0/26"
+
+# e5cce0b4eb08472589cd816030a3de7d
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+msgid "10.1.1.64 to 10.1.1.254"
+msgstr "10.1.1.64-10.1.1.254"
+
+# 9e5926a76629431e9e75a9c27ec25211
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+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 "在界面的CIDR框内输入10.1.1.0/26或通过UpdateNetwork的API配置为guestvmcidr=10.1.1.0/26，进行IP预留配置"
+
+# a1279f60da4448408c8b4ef94ae25031
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+msgid "3"
+msgstr "3"
+
+# 24e829a2afac40eaa86a07045b551c40
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+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 "在界面的CIDR框内输入10.1.1.0/24或通过UpdateNetwork API配置为guestvmcidr=10.1.1.0/24，进行IP预留清除"
+
+# d2dda38687714f138add9a3210ce94ec
+# 46aafdafc5b941cc973bf413019aea2d
+# 72b66fa9b2694682919a62c46d2a7506
+#: ../../networking/ip_reservation_in_guest_networks.rst:83
+#: ../../networking/security_groups.rst:91
+#: ../../networking/palo_alto_config.rst:467
+msgid "Limitations"
+msgstr "局限性"
+
+# 6c3ae7eb716447539cf6ce3a087485f8
+#: ../../networking/ip_reservation_in_guest_networks.rst:85
+msgid ""
+"The IP Reservation is not supported if active IPs that are found outside the"
+" Guest VM CIDR."
+msgstr "如果在客户虚拟机CIDR外发现活动的IP地址，IP预留将不被支持。"
+
+# 2b40b03295c04e3384d785ee53b756e2
+#: ../../networking/ip_reservation_in_guest_networks.rst:88
+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 "在IP预留中，引起CIDR变化的网络升级方案都将无效，如将无外部设备的方案升级到带有外部设备的方案。在新实施的网络中，要重新配置IP预留。"
+
+# 583ca0216ee74e1581158dc7533c07d0
+#: ../../networking/ip_reservation_in_guest_networks.rst:95
+msgid "Best Practices"
+msgstr "最佳实践"
+
+# 388bdfcc95f147538a75b7767724cbda
+#: ../../networking/ip_reservation_in_guest_networks.rst:97
+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 "一旦网络状态变为实施，应尽快应用IP预留到客户网络。如果在第一台客户虚拟机部署后应用IP预留，则会在应用IP会有较少的冲突发生。"
+
+# a3c4555e018a445ca599010a280d64a5
+#: ../../networking/ip_reservation_in_guest_networks.rst:104
+msgid "Reserving an IP Range"
+msgstr "预留一个IP范围"
+
+# 6242f71ba63246c7a5080997cf22f7c6
+#: ../../networking/ip_reservation_in_guest_networks.rst:112
+msgid "In the Details tab, click Edit. |ip-edit-icon.png|"
+msgstr ""
+
+# df98c1294588410ca38bdcafe1f1a634
+#: ../../networking/ip_reservation_in_guest_networks.rst:114
+msgid "The CIDR field changes to editable one."
+msgstr "CIDR框将变为可编辑状态"
+
+# e18e130a65f64f129965e464668821cc
+#: ../../networking/ip_reservation_in_guest_networks.rst:116
+msgid "In CIDR, specify the Guest VM CIDR."
+msgstr "在CIDR框，说明客户虚拟机的CIDR"
+
+# e1926c61c2e24ac9bb3568b5425e6640
+#: ../../networking/ip_reservation_in_guest_networks.rst:118
+msgid "Click Apply."
+msgstr "点击应用"
+
+# 8e47676d285f403ab1c11aacbe5ad256
+#: ../../networking/ip_reservation_in_guest_networks.rst:120
+msgid ""
+"Wait for the update to complete. The Network CIDR and the Reserved IP Range "
+"are displayed on the Details page."
+msgstr "等待更新完成。"
+
+# b15f7528cec041d084db2225a51abbd1
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:18
+msgid "Reserving Public IP Addresses and VLANs for Accounts"
+msgstr "为账户预留公共IP地址及VLANS"
+
+# 1237af30bb46480aa12ce39cfe5e593c
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:20
+msgid ""
+"CloudStack provides you the ability to reserve a set of public IP addresses "
+"and VLANs exclusively for an account. During zone creation, you can continue"
+" defining a set of VLANs and multiple public IP ranges. This feature extends"
+" the functionality to enable you to dedicate a fixed set of VLANs and guest "
+"IP addresses for a tenant."
+msgstr "CloudStack可以让你能够独立的为账户预留一部分公共IP地址和VLANS。在创建区域阶段，你可以继续定义一部分VLANS以及多个公共IP范围。这种功能扩展特性可以让你能够为客户预留固定的一部分VLAN和客户IP地址"
+
+# 17369f839a29414b986f6bea29ed68ba
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:26
+msgid ""
+"Note that if an account has consumed all the VLANs and IPs dedicated to it, "
+"the account can acquire two more resources from the system. CloudStack "
+"provides the root admin with two configuration parameter to modify this "
+"default behavior: use.system.public.ips and use.system.guest.vlans. These "
+"global parameters enable the root admin to disallow an account from "
+"acquiring public IPs and guest VLANs from the system, if the account has "
+"dedicated resources and these dedicated resources have all been consumed. "
+"Both these configurations are configurable at the account level."
+msgstr "注意，如果一个账户使用了所有分配给他的VLAN和IP，这个账户可以从系统获得二个以上的资源。CloudStack为根管理员提供了二个参数可以进行控制，分别是use.system.public.ips和use.system.guest.vlans。当一个账户分配了资源并且这些资源已经被消耗掉时，这二个全局参数可以使根管理员拒绝此账户从公共IP和来宾VLAN获取资源。二个配置都能在帐户级别进行配置。"
+
+# eb7adb4a348943f4a8a202f85e7fb8d5
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:36
+msgid "This feature provides you the following capabilities:"
+msgstr "这些特性可提供以下的功能："
+
+# 358e7d880b0749daa4dc8a226925c073
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:38
+msgid ""
+"Reserve a VLAN range and public IP address range from an Advanced zone and "
+"assign it to an account"
+msgstr "从一个高级区域中预留一个VLAN范围和公共IP地址，并可以将其指定给一个账户。"
+
+# 6e0eb4612e474dc984111d18bb95fc83
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:41
+msgid "Disassociate a VLAN and public IP address range from an account"
+msgstr "将一个VLAN和IP地址从一个账户解除联系。"
+
+# bab06e5f1a2f454aa3b08743ba57c793
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:43
+msgid "View the number of public IP addresses allocated to an account"
+msgstr "查看分配给帐户的公共IP地址。"
+
+# a6866fc5db5347209e221b84742c3365
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:45
+msgid ""
+"Check whether the required range is available and is conforms to account "
+"limits."
+msgstr "检查需要的范围是否可用并且要符合帐户限制。"
+
+# 1620986a4ae94f2485a54cd91ccaac56
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:48
+msgid "The maximum IPs per account limit cannot be superseded."
+msgstr "不能超过每个账户最大的IP限制数。"
+
+# 22120243221443aebd306ac3563d496f
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:52
+msgid "Dedicating IP Address Ranges to an Account"
+msgstr "分配IP地址给一个账户"
+
+# 41eada43c00c47d3af3049e17e3a5ed4
+# 3a4fc14485e04b878d42c2f16d2c1874
+# 3b0a5efffc524d5a89c218f531388b51
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:56
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:126
+#: ../../networking/global_server_load_balancing.rst:317
+msgid "In the left navigation bar, click Infrastructure."
+msgstr "在左侧导航栏中，点击基础架构"
+
+# afa72273b7894980af0176c1cbb8d600
+# 1b7787454ba64ef5bde4f8dc55076690
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:58
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:128
+msgid "In Zones, click View All."
+msgstr "在区域中，点击查看全部"
+
+# 3538cd7eca744d5dbedb17d4d1df1490
+# 737bb1531046470f96395e869b9b3d0d
+# 1c6a07051f2f4a1eb71d9cb9a6cbb984
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:60
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:130
+#: ../../networking/global_server_load_balancing.rst:321
+msgid "Choose the zone you want to work with."
+msgstr "选择你要设置的区域。"
+
+# 2afee3aa9d964227ad8abeec4cff164d
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:64
+msgid "In the Public node of the diagram, click Configure."
+msgstr "在图的公共节点上，点击配置。"
+
+# 31af885ac08540b1a345a76ed1c81e3a
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:66
+msgid "Click the IP Ranges tab."
+msgstr "点击IP范围页签。"
+
+# d99c704f2b3e4e829337b91b0e1af56a
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:68
+msgid ""
+"You can either assign an existing IP range to an account, or create a new IP"
+" range and assign to an account."
+msgstr "或者指定一个已经的IP范围给帐户，或创建一个新的IP范围并指定给一个帐户。"
+
+# 781bb561940748e88798ab180120b3e8
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:71
+msgid "To assign an existing IP range to an account, perform the following:"
+msgstr "要指定一个已有IP范围给帐户，按以下操作进行"
+
+# 64caee3705894ae5b7eb188e82c8d260
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:73
+msgid "Locate the IP range you want to work with."
+msgstr "确定需要分配的IP范围"
+
+# 9e0730ca65ac4442a517f39c9056cee8
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:75
+msgid "Click Add Account |addAccount-icon.png| button."
+msgstr "点击添加帐户按钮。|addAccount-icon.png| "
+
+# 6c4ee6b7080e4fd7a90d8edddfda5845
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:77
+msgid "The Add Account dialog is displayed."
+msgstr "会弹出添加帐户对话框。"
+
+# 2c50704135d54e319c54ab3e0aade306
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:81
+msgid ""
+"**Account**: The account to which you want to assign the IP address range."
+msgstr "**帐户**: 即需要指定IP地址范围的帐户"
+
+# ee19ac37f89e4403997fdca99142dad5
+# 2ba3bff62178453c93570a1e85aa2879
+# 265ed744d98042a9bbcb2c139f70e7fb
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:84
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:112
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:150
+msgid "**Domain**: The domain associated with the account."
+msgstr "**域**: 与帐户关联的域名"
+
+# 8fbac9b35cdb43ea90d07e27edb5a231
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:86
+msgid "To create a new IP range and assign an account, perform the following:"
+msgstr "要指定一个新的IP范围给帐户，按以下操作进行"
+
+# 16602be853314d1ca41010b8d9c70203
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:91
+msgid "**Gateway**"
+msgstr "**网关**"
+
+# 2b07551df7d347b2877a717602b072a0
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:93
+msgid "**Netmask**"
+msgstr "**掩码**"
+
+# 8302fe6345ff497088145a583593bea1
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:95
+msgid "**VLAN**"
+msgstr "**VLAN**"
+
+# 34b38799ec734aa89366e4c3f651a3e4
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:97
+msgid "**Start IP**"
+msgstr "**起始IP**"
+
+# 70bab7c8bc9a44b8b72a460686975a2a
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:99
+msgid "**End IP**"
+msgstr "**结束IP**"
+
+# 02aaa72ff90843289ad5aeb650f65a9d
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:101
+msgid "**Account**: Perform the following:"
+msgstr "**帐户**: 按以下操作进行："
+
+# 9a58082c89c9466fba38134f240e1b52
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:103
+msgid "Click Account."
+msgstr "点击帐户"
+
+# dcb5729930024223b016b7cbdb424ba1
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:105
+msgid "The Add Account page is displayed."
+msgstr "会显示添加帐户页"
+
+# 5c2df9219e7346a6bfc5ecb3bf074542
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:109
+msgid ""
+"**Account**: The account to which you want to assign an IP address range."
+msgstr ""
+
+# f149473b61b340ca9e017c5f4aad3762
+# 2ddbd5f2481d4b119ddad24b954900cc
+# b48da4e586f54f578325e5a80b7d9f43
+# 5b0f318024d544438e606644459f750b
+# 065cefba75724c0a8d56d7931eea5c3d
+# 589f4a9092e34b8f8382b017ebf0259f
+# b103ac8cfde9495fb1cd24a491540360
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:117
+#: ../../networking/security_groups.rst:210
+#: ../../networking/ip_forwarding_and_firewalling.rst:88
+#: ../../networking/ip_forwarding_and_firewalling.rst:163
+#: ../../networking/ip_forwarding_and_firewalling.rst:276
+#: ../../networking/remote_access_vpn.rst:153
+#: ../../networking/virtual_private_cloud_config.rst:642
+msgid "Click Add."
+msgstr "点击 添加"
+
+# 6f051411c8144bdc9db1c5f418ca9e6b
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:121
+msgid "Dedicating VLAN Ranges to an Account"
+msgstr "确定需要分配的IP范围"
+
+# 0624b2939c5d4e5f9f0769c68abba80a
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:123
+msgid ""
+"After the CloudStack Management Server is installed, log in to the "
+"CloudStack UI as administrator."
+msgstr "安装好CloudStack管理端后，使用管理员帐号登录CloudStack用户界面。"
+
+# 40248bd661704cdb80e80629fe09d500
+# f99a23ecda8047cfa0314a138db2515e
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:134
+#: ../../networking/multiple_subnets_in_shared_network.rst:61
+msgid "In the Guest node of the diagram, click Configure."
+msgstr "在图中的来宾节点上，点击配置"
+
+# 092aa112394946a6a4808b597cc9d85d
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:136
+msgid "Select the Dedicated VLAN Ranges tab."
+msgstr "选择分配VLAN范围页签"
+
+# 1fdecb917bc84f50afd745175be5d7e7
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:138
+msgid "Click Dedicate VLAN Range."
+msgstr "点击分配VLAN范围"
+
+# b67fd2523d364441a6c82f24bc357ab5
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:140
+msgid "The Dedicate VLAN Range dialog is displayed."
+msgstr "会弹出分配VLAN对话框。"
+
+# 542f999a29c64479b5f5d452895813bd
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:144
+msgid "**VLAN Range**: The VLAN range that you want to assign to an account."
+msgstr ""
+
+# 55217660cfb0479ebc430fe86772c808
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:147
+msgid ""
+"**Account**: The account to which you want to assign the selected VLAN "
+"range."
+msgstr ""
+
+# 4b6378bc482446339fca13029388310a
+#: ../../networking/multiple_ips_on_single_nic.rst:18
+msgid "Configuring Multiple IP Addresses on a Single NIC"
+msgstr "在单网卡配置多个IP地址"
+
+# 3cb13c102ebb495b944a5ea2571c0ea6
+#: ../../networking/multiple_ips_on_single_nic.rst:20
+msgid ""
+"CloudStack provides you the ability to associate multiple private IP "
+"addresses per guest VM NIC. In addition to the primary IP, you can assign "
+"additional IPs to the guest VM NIC. This feature is supported on all the "
+"network configurations: Basic, Advanced, and VPC. Security Groups, Static "
+"NAT and Port forwarding services are supported on these additional IPs."
+msgstr "CloudStack能够让你给每个客户虚拟机网卡配置多个私有IP地址，除主IP地址外，你可以指定额外的IP地址到客户虚拟机网卡。在所有的网络配置中，如基础配置，高级配置，VPC，均支持这一功能。安全组，静态NAT及端口转发服务在额外的IP地址上也都被支持。"
+
+# cda7fad448d845659243893d3485d00f
+#: ../../networking/multiple_ips_on_single_nic.rst:27
+msgid ""
+"As always, you can specify an IP from the guest subnet; if not specified, an"
+" IP is automatically picked up from the guest VM subnet. You can view the "
+"IPs associated with for each guest VM NICs on the UI. You can apply NAT on "
+"these additional guest IPs by using network configuration option in the "
+"CloudStack UI. You must specify the NIC to which the IP should be "
+"associated."
+msgstr "当然，你也可以从来宾子网中指定一个IP，如果没有指定，将会从来宾虚拟机子网中自动选择一个。可以从UI中查看每一个与来宾虚拟机网卡关联的IP地址。也可以在CloudStack界面中通过网络配置选项在那些额外的来宾虚拟机上应用NAT。但必须指明网卡与哪一个IP关联。"
+
+# de43d093c3fa4819badd7e95a605662c
+#: ../../networking/multiple_ips_on_single_nic.rst:34
+msgid ""
+"This feature is supported on XenServer, KVM, and VMware hypervisors. Note "
+"that Basic zone security groups are not supported on VMware."
+msgstr "在XenServer，KVM和VMware虚拟机中，都支持这些功能。注意，VMware不支持基础区域的安全组。"
+
+# b0dc091ada714fc080fbb52f2ea8f427
+#: ../../networking/multiple_ips_on_single_nic.rst:39
+msgid "Use Cases"
+msgstr "使用案例"
+
+# f716fd8c0f43409d9b85a31bfd022770
+#: ../../networking/multiple_ips_on_single_nic.rst:41
+msgid "Some of the use cases are described below:"
+msgstr "一些使用案例见以下描述"
+
+# 39e24f20af4e4a389da098c9fb80f1f5
+#: ../../networking/multiple_ips_on_single_nic.rst:43
+msgid ""
+"Network devices, such as firewalls and load balancers, generally work best "
+"when they have access to multiple IP addresses on the network interface."
+msgstr "网络设备，如防火墙或负责均衡设备，一般来讲，当他们在网络接口上接入更多的IP地址时，他们能够更好的工作。"
+
+# 75801965b1464997a865772f1ea040ef
+#: ../../networking/multiple_ips_on_single_nic.rst:47
+msgid ""
+"Moving private IP addresses between interfaces or instances. Applications "
+"that are bound to specific IP addresses can be moved between instances."
+msgstr "在接口和实例中迁移IP地址。绑定到特定IP地址的应用可以在实例中迁移。"
+
+# 1f4805e6057f4a5f97735f57cc71033c
+#: ../../networking/multiple_ips_on_single_nic.rst:51
+msgid ""
+"Hosting multiple SSL Websites on a single instance. You can install multiple"
+" SSL certificates on a single instance, each associated with a distinct IP "
+"address."
+msgstr "在单个实例上开启多个SSL网站。可以在单个实例上安装多个SSL认证，每一个认证都关联一个单独的IP地址。"
+
+# c0033b8d9992490791fbd0dc7f89fa6f
+# 4c7d965ae98540498820d6359998db6c
+# 924fe16b17a346a1b175d02a5701f4db
+#: ../../networking/multiple_ips_on_single_nic.rst:57
+#: ../../networking/portable_ips.rst:48
+#: ../../networking/virtual_private_cloud_config.rst:1125
+msgid "Guidelines"
+msgstr "指南"
+
+# ab36c55d792048e78529f118b75f7169
+#: ../../networking/multiple_ips_on_single_nic.rst:59
+msgid ""
+"To prevent IP conflict, configure different subnets when multiple networks "
+"are connected to the same VM."
+msgstr "为防止IP冲突，当多个网络连接至同一个虚拟机时，要配置不同的子网。"
+
+# a16d7477fb8d418abbe4a25970ed93ac
+#: ../../networking/multiple_ips_on_single_nic.rst:64
+msgid "Assigning Additional IPs to a VM"
+msgstr "指定额外的IP给虚拟机"
+
+# 8913586016c847b1b942015f371fff55
+#: ../../networking/multiple_ips_on_single_nic.rst:66
+msgid "Log in to the CloudStack UI."
+msgstr "登录到CloudStack的界面"
+
+# 93115e86c11446058862e5525c9fcc6d
+#: ../../networking/multiple_ips_on_single_nic.rst:68
+msgid "In the left navigation bar, click Instances."
+msgstr "在左侧导航栏，点击实例"
+
+# 197ab17d29454cdc8de866d1f2c0be83
+#: ../../networking/multiple_ips_on_single_nic.rst:70
+msgid "Click the name of the instance you want to work with."
+msgstr "点击拟配置的实例"
+
+# c7863b679faf4fb6ac1f9e48e70ba5d4
+#: ../../networking/multiple_ips_on_single_nic.rst:72
+msgid "In the Details tab, click NICs."
+msgstr "在详细 页签，点击网卡"
+
+# 9dfa60a220ed42018f74c7bd78e6d7cd
+#: ../../networking/multiple_ips_on_single_nic.rst:74
+msgid "Click View Secondary IPs."
+msgstr "点击查看二级地址"
+
+# e783f44753f8491689c78956994376bd
+#: ../../networking/multiple_ips_on_single_nic.rst:76
+msgid ""
+"Click Acquire New Secondary IP, and click Yes in the confirmation dialog."
+msgstr "点击获取新二级IP，在确认对话框点击确定。"
+
+# ae7779933a044ea395e2bfa5e67ca484
+#: ../../networking/multiple_ips_on_single_nic.rst:79
+msgid ""
+"You need to configure the IP on the guest VM NIC manually. CloudStack will "
+"not automatically configure the acquired IP address on the VM. Ensure that "
+"the IP address configuration persist on VM reboot."
+msgstr "需要手动配置来宾虚拟机的网卡。在虚拟机上，CloudStack不会自动配置获取IP。确保在虚拟机重启IP地址配置仍有效。"
+
+# e08145cc27e24301982a9f2f45bd93d8
+#: ../../networking/multiple_ips_on_single_nic.rst:83
+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 StaticNAT "
+"rules."
+msgstr "稍等一会，新的IP地址会出现，状态栏为会显示为分配。现在可以在端口转发或静态NAT规则中使用此IP地址了。"
+
+# 1aa79a21e0f24d109fbf1a380be58b37
+#: ../../networking/multiple_ips_on_single_nic.rst:89
+msgid "Port Forwarding and StaticNAT Services Changes"
+msgstr "更改端口转发和静态NAT服务"
+
+# ffac07bcb64d47f7bcb39e02c46e43b5
+#: ../../networking/multiple_ips_on_single_nic.rst:91
+msgid ""
+"Because multiple IPs can be associated per NIC, you are allowed to select a "
+"desired IP for the Port Forwarding and StaticNAT services. The default is "
+"the primary IP. To enable this functionality, an extra optional parameter "
+"'vmguestip' is added to the Port forwarding and StaticNAT APIs "
+"(enableStaticNat, createIpForwardingRule) to indicate on what IP address NAT"
+" need to be configured. If vmguestip is passed, NAT is configured on the "
+"specified private IP of the VM. if not passed, NAT is configured on the "
+"primary IP of the VM."
+msgstr "因为每一个网卡都可关联至多IP，CloudStack可以允许为端口转发及静态NAT服务选择一个目标IP。默认为主IP。为开启此功能，另一个可选的配置参数 虚拟机来宾IP 需要被加至端口转发及静态NAT 的API中去（开启静态NAT，创建IP端口转发），以示IP地址NAT需要配置。如果虚拟机来宾IP 没有设置，NAT会配置在虚拟机的私有IP上，如果设置了，NAT会配置在虚拟机的主IP上。"
+
+# 0e8ade71092049f9bae900723c45e41a
+#: ../../networking/multiple_ip_ranges.rst:18
+msgid "About Multiple IP Ranges"
+msgstr "关于多IP范围"
+
+# e46b13dd887941a78dd4dde1a9c91f7b
+#: ../../networking/multiple_ip_ranges.rst:20
+msgid "The feature can only be implemented on IPv4 addresses."
+msgstr "这些功能仅能在IPV4的地址是实现。"
+
+# 6bd2d25649fc4326b60a07cefee0f204
+#: ../../networking/multiple_ip_ranges.rst:22
+msgid ""
+"CloudStack provides you with the flexibility to add guest IP ranges from "
+"different subnets in Basic zones and security groups-enabled Advanced zones."
+" For security groups-enabled Advanced zones, it implies multiple subnets can"
+" be added to the same VLAN. With the addition of this feature, you will be "
+"able to add IP address ranges from the same subnet or from a different one "
+"when IP address are exhausted. This would in turn allows you to employ "
+"higher number of subnets and thus reduce the address management overhead. To"
+" support this feature, the capability of ``createVlanIpRange`` API is "
+"extended to add IP ranges also from a different subnet."
+msgstr "在基础区域以及高级区域的开启安全组，CloudStack能够让你从不同的子网添加来宾IP范围。对于高级区域的开启安全组，多个子网可被加至同一个VLAN。随着此功能的增加，当IP地址耗尽时，你能够从同一个子网或从不同的子网添加IP范围。这会允许你添加更多的子网，因此减少了了地址管理的问题。为支持这一特性，创建VLANIP范围的API被加以扩展，这样就能从不同的子网添加IP范围"
+
+# 3ba0c789bb3449fe86585f4c8c841997
+#: ../../networking/multiple_ip_ranges.rst:33
+msgid ""
+"Ensure that you manually configure the gateway of the new subnet before "
+"adding the IP range. Note that CloudStack supports only one gateway for a "
+"subnet; overlapping subnets are not currently supported."
+msgstr "确实在添加IP范围前，手动配置了子网的网关。注意，CloudStack仅支持一个子网有一个网关。不支持重叠的子网。"
+
+# e5e487ee073f4d56be1f4666a45f4dfe
+#: ../../networking/multiple_ip_ranges.rst:37
+msgid ""
+"Use the ``deleteVlanRange`` API to delete IP ranges. This operation fails if"
+" an IP from the remove range is in use. If the remove range contains the IP "
+"address on which the DHCP server is running, CloudStack acquires a new IP "
+"from the same subnet. If no IP is available in the subnet, the remove "
+"operation fails."
+msgstr "使用删除VLAN范围的API删除IP范围。如果拟删除的IP在被使用时，此操作会失败。如果删除的范围包含DHCP服务器拟分配的IP地址CloudStack会从同一个子网下获取新的IP。如果在子网内没有可供利用的IP时，删除操作会失败。"
+
+# bc188db60e2742989c16aedac841809e
+#: ../../networking/multiple_ip_ranges.rst:43
+msgid "This feature is supported on KVM, xenServer, and VMware hypervisors."
+msgstr "在KVM, xenServer以及VMware虚拟机中，都支持这项功能。 "
+
+# 866f7bd8690f4e378e4a55a7c80d196c
+#: ../../networking/elastic_ips.rst:18
+msgid "About Elastic IPs"
+msgstr ""
+
+# 53c01f3c606045ad9beed865c2233d50
+#: ../../networking/elastic_ips.rst:20
+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 is down, the IP address can be "
+"reassigned to a new VM in your account."
+msgstr "弹性IP（EIP）地址是指与帐户关联的IP地址，能起到静态IP地址的作用。帐户所有者能完全控制隶属于此账户的弹性IP。作为帐户拥有者，你可以从你帐户的EIP池中选择一个IP分配给虚拟机。如果后续需要，你可以继续分配此IP地址给另一个虚拟机。在VM宕机时，此功能特别有用。此IP地址可以重新指定给一个新的虚拟机，而不是取代已经宕机的虚拟机。"
+
+# eeb2c5db0229477692e9e379117ad90e
+#: ../../networking/elastic_ips.rst:29
+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 "与公共IP地址一样，弹性IP地址通过使用静态NAT关联至与之相关的私有IP地址。在起用了EIP的基础域中，EIP的服务与静态NAT的服务一一对应。默认的网络方案，默认共享EIP与负载均衡网络方案，在区域部署了NetScaler设备的前提下，能够提供EIP以及ELB网络服务。参见以下更详细的说明。"
+
+# c188c126629840a7a54f6b8956cb2c76
+#: ../../networking/elastic_ips.rst:37
+msgid "|eip-ns-basiczone.png|"
+msgstr "|eip-ns-basiczone.png|"
+
+# 51020097041145ddb6805633c7eb819c
+#: ../../networking/elastic_ips.rst:39
+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 data center goes through the firewall."
+msgstr "在图中，NetScaler设备对CloudStack的实例而言是一个默认的入口或出口，防火墙是剩余数据中心的出口或入口。Netscaler对来宾网络提供负载均衡以及静态NAT的服务。在机架和管理服务器上，来宾流量是不同的子网或VLAN。在数据中心的核心交换机的基础路由策略是通过NetScaler转发公共流量，其他数据中心的流量则通过防火墙。"
+
+# 3f2630ad1d0343c68eb8a2303ccb4c9c
+#: ../../networking/elastic_ips.rst:48
+msgid "The EIP work flow is as follows:"
+msgstr "EIP的工作流如下："
+
+# d20e19311068491ba44b06500472b710
+#: ../../networking/elastic_ips.rst:50
+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 "当部署一个用户虚拟机时，会从区域配置的IP中自动获得一个公共IP。这个IP为虚拟机帐户所拥有。"
+
+# d15702d110a942848fa6cef69cece507
+#: ../../networking/elastic_ips.rst:54
+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 "每一个虚拟机都有自己的私有IP。当来客户虚拟机启动时，通过使用在公共IP和私有IP之间的入口网络地址转换（INAT）以及预留地址转换（RNAT），NetScaler设备可以提供静态NAT"
+
+# ff6cb27225094523ba3a17d305016521
+#: ../../networking/elastic_ips.rst:60
+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 "入口网络地址转换（INAT）是NetScaler支持的一类NAT类型，在此类型中，来自公共网络（如Internet)的数据包中的目标IP地址被私有网络中虚拟机的私有地址取代。预留地址转换（RNAT）也是NetScaler支持的一类NAT类型，私有网络中虚拟机产生的数据包中的源IP地址被公共IP地址取代。"
+
+# e9dde6b9e99a42a4b1141fa7cde9549e
+#: ../../networking/elastic_ips.rst:67
+msgid "This default public IP will be released in two cases:"
+msgstr "默认的公共IP在两种情况下会被释放："
+
+# bb3ef5bc34c24d44980be5d6f69e0c5c
+#: ../../networking/elastic_ips.rst:69
+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 "当虚拟机停止时。当虚拟机启动时，可以重新获取一个新的公共IP，并不必须是从公共IP地址池中最初分配的那一个。"
+
+# 571a9e4939ea4287a8aa0ddf426417b4
+#: ../../networking/elastic_ips.rst:73
+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 "当用户获取公共IP（弹性IP）时。这些公共IP与帐户相关联，但不与任何私有IP相关。然而，用户可以开启静态NAT将帐户中虚拟机的私有IP与之关联。对应公共IP的静态NAT规则可随时取消。当静态NAT关闭时，会从地址池中分配的一个新的公共IP，并不必须是最初分配的那一个。"
+
+# aaf805319e4341d8a268392acb2bda8e
+#: ../../networking/elastic_ips.rst:81
+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 and enable static NAT."
+msgstr "对部署而言，公共IP会受限于资源，可以灵活的选择默认不分配公共IP。可以在开启了EIP的基础区域中，通过关联公共IP选项来打开或关闭自动公共IP指定。如果在创建网络方案时，你关闭了自动公共IP指定，则在使用此网络方案部署时，仅会分配一个私有IP给虚拟机。此后，用户虚拟机可以获取一个IP，并可以开启静态NAT。"
+
+# 31babd6d6dfd4d079192f8d6984817ee
+#: ../../networking/elastic_ips.rst:90
+msgid ""
+"For more information on the Associate Public IP option, see `\"Creating a "
+"New Network Offering\" <networking.html#creating-a-new-network-offering>`_."
+msgstr "要了解更多关于关联公共IP的选项，请参考`\"创建一个新的网络方案\" <networking.html#creating-a-new-network-offering>`_."
+
+# dbb9cddd535f4a438059357783272fe3
+#: ../../networking/elastic_ips.rst:94
+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 "设计关联公共IP的功能，仅是为使用用户虚拟机。系统虚拟机仍然默认会获取公共IP和私有IP，与网络配置并不相关。"
+
+# d898deec360a48b1851e6a597385713b
+#: ../../networking/elastic_ips.rst:98
+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 "在基础区域中，使用默认具有EIP和ELB服务的网络方案来创建共享网络时，仍然会给每一个用户虚拟机分配公共IP。"
+
+# 0f08f4f232ba497eb9cd9c3e04f96afc
+#: ../../networking/portable_ips.rst:18
+msgid "Portable IPs"
+msgstr "端口IP"
+
+# 7ac92bb50f6449d988fcc630639a18fc
+#: ../../networking/portable_ips.rst:21
+msgid "About Portable IP"
+msgstr "关于端口IP"
+
+# 6ae5874856114307829101c5c704d620
+#: ../../networking/portable_ips.rst:23
+msgid ""
+"Portable IPs in CloudStack are region-level pool of IPs, which are elastic "
+"in nature, that can be transferred across geographically separated zones. As"
+" an administrator, you can provision a pool of portable public IPs at region"
+" level and are available for user consumption. The users can acquire "
+"portable IPs if admin has provisioned portable IPs at the region level they "
+"are part of. These IPs can be use for any service within an advanced zone. "
+"You can also use portable IPs for EIP services in basic zones."
+msgstr "在CloudStack中，端口IP是地域级的IP地址池，其天然具有弹性，亦即可以在地理隔离的区域中进行转发。作为管理员,可以在地域级提供IP地址池供用户使用。如果在用户所属的地域，其管理员提供了端口IP，用户就可以获取此类IP。在高级区域内，这些IP可用于任一服务。也可以在基础区域中为EIP服务使用端口IP。"
+
+# 742f98931c1a44baa38129e2d9707866
+#: ../../networking/portable_ips.rst:32
+msgid "The salient features of Portable IP are as follows:"
+msgstr "端口IP的主要功能如下："
+
+# a4472d2004c943f1ad88325b36b6a440
+#: ../../networking/portable_ips.rst:34
+msgid "IP is statically allocated"
+msgstr "IP是静态分配的。"
+
+# fcd6dca4d30d4a1f92bb64c7635abeb1
+#: ../../networking/portable_ips.rst:36
+msgid "IP need not be associated with a network"
+msgstr "IP与网络无关。"
+
+# 7409719b9ce74f6c8d91b07f9079a6ef
+#: ../../networking/portable_ips.rst:38
+msgid "IP association is transferable across networks"
+msgstr "IP关联是可以通过网络转发的。"
+
+# 5aeff85fa3704f3ab93dbbba900c80f2
+#: ../../networking/portable_ips.rst:40
+msgid "IP is transferable across both Basic and Advanced zones"
+msgstr "IP可以在基础区域和高级区域中转发。"
+
+# 96ffa5d02ec9464e8866c8d272aad9c1
+#: ../../networking/portable_ips.rst:42
+msgid "IP is transferable across VPC, non-VPC isolated and shared networks"
+msgstr "IP可通过VPC，非VPC隔离和共享网络进行转发。"
+
+# 6207a2e79e024acc8ef256c36daec0ff
+#: ../../networking/portable_ips.rst:44
+msgid "Portable IP transfer is available only for static NAT."
+msgstr "端口IP转发仅对静态NAT可用。"
+
+# c3d0138ce57f44a9becb32df52ca0fb9
+#: ../../networking/portable_ips.rst:50
+msgid ""
+"Before transferring to another network, ensure that no network rules "
+"(Firewall, Static NAT, Port Forwarding, and so on) exist on that portable "
+"IP."
+msgstr "在转发至另一网络前，确保没有网络规则（如防火墙，静态NAT，端口转发等等）不存在于端口IP。"
+
+# 18cc0645453a43eebf52beaa73a9a6a6
+#: ../../networking/portable_ips.rst:56
+msgid "Configuring Portable IPs"
+msgstr "配置端口IP"
+
+# 740ad8e23fac49f8950f5161989c18e9
+#: ../../networking/portable_ips.rst:60
+msgid "In the left navigation, click Regions."
+msgstr "在左侧导航栏中，点击地域"
+
+# 40704d729f114cbcb667118f671238ef
+#: ../../networking/portable_ips.rst:62
+msgid "Choose the Regions that you want to work with."
+msgstr "选择拟修改的地域。"
+
+# 03bf5d8664204ec084df0a9d5940644a
+#: ../../networking/portable_ips.rst:64
+msgid "Click View Portable IP."
+msgstr "点击查看端口IP"
+
+# ddc000619eb94419951b60265902d979
+#: ../../networking/portable_ips.rst:66
+msgid "Click Portable IP Range."
+msgstr "点击端口IP范围"
+
+# c8a67f00327e4e37bfae6b2882e40fa0
+#: ../../networking/portable_ips.rst:68
+msgid "The Add Portable IP Range window is displayed."
+msgstr "会出现 添加端口IP范围的窗口"
+
+# 873cae2265344ab384d2b0f8956b8cbe
+#: ../../networking/portable_ips.rst:72
+msgid ""
+"**Start IP/ End IP**: A range of IP addresses that are accessible from the "
+"Internet and will be allocated to guest VMs. Enter the first and last IP "
+"addresses that define a range that CloudStack can assign to guest VMs."
+msgstr "**起始IP/结束IP**: 从Internet可以访问的一个IP地址范围，将会分配给客户虚拟机。输入起始IP以及结束IP，定义CloudStack指定给客户虚拟机的IP范围。"
+
+# 47a17aedcd9a46d4aa9426bc133f7593
+#: ../../networking/portable_ips.rst:77
+msgid ""
+"**Gateway**: The gateway in use for the Portable IP addresses you are "
+"configuring."
+msgstr "**网关**: 配置端口IP地址所使用的网关。"
+
+# 7979e6a1cf8a4b2d8e8673ed132db41e
+#: ../../networking/portable_ips.rst:80
+msgid "**Netmask**: The netmask associated with the Portable IP range."
+msgstr "**掩码**: 与端口IP范围关联的掩码。"
+
+# 63cb5224252e403480ba1ddc53337de8
+#: ../../networking/portable_ips.rst:82
+msgid "**VLAN**: The VLAN that will be used for public traffic."
+msgstr "**VLAN**: 公共流量拟使用的VLAN。"
+
+# 124023448c074dcea01be7eddc177170
+#: ../../networking/portable_ips.rst:88
+msgid "Acquiring a Portable IP"
+msgstr "获取端口IP。"
+
+# ac222ffaf3d1404a885f643c228d2c83
+# baf678baec6247bb94c9eab6b3b1e84e
+# ffdddf1fe28240469a8090a522b32151
+# 663ad172db854afdadd95fc1d3db1f64
+# 2bf3f81e7dbb4b2cb34d627506ee9889
+#: ../../networking/portable_ips.rst:94
+#: ../../networking/acquiring_an_ip_address.rst:24
+#: ../../networking/releasing_an_ip_address.rst:28
+#: ../../networking/static_nat.rst:40
+#: ../../networking/ip_forwarding_and_firewalling.rst:63
+msgid "Click the name of the network where you want to work with."
+msgstr "点击拟修改的网络名称。"
+
+# 442ce3999e8d427da57daa610533fb7c
+# 9cc585cd1a5740acba75c898195b0eab
+# 4c9d3404671a4e4d99d3323175204d8e
+# e8c449dffe3c49e8938437a96cef0ca6
+# d605e8bf3fb74b278bf0d265f1db6084
+# 5f4eacd3a2ba48349a41f04f8756ee37
+# ba3dfb6ca3af4d51a17fa31861d95379
+#: ../../networking/portable_ips.rst:96
+#: ../../networking/external_firewalls_and_load_balancers.rst:262
+#: ../../networking/acquiring_an_ip_address.rst:26
+#: ../../networking/releasing_an_ip_address.rst:30
+#: ../../networking/static_nat.rst:42
+#: ../../networking/ip_forwarding_and_firewalling.rst:65
+#: ../../networking/remote_access_vpn.rst:82
+msgid "Click View IP Addresses."
+msgstr "点击查看IP地址。"
+
+# fbc9c26eb4f041618e668c4addb7f051
+# eab860b6d87641698d96cf5e11803339
+#: ../../networking/portable_ips.rst:98
+#: ../../networking/acquiring_an_ip_address.rst:28
+msgid "Click Acquire New IP."
+msgstr "点击获取新IP。"
+
+# 294bab6d3d9f43aa8d85acabb8fdbdf5
+# 5ebf3c5ce9154b57bf3cf2ef8e449b4b
+#: ../../networking/portable_ips.rst:100
+#: ../../networking/acquiring_an_ip_address.rst:30
+msgid "The Acquire New IP window is displayed."
+msgstr "获取新IP的窗口会出现。"
+
+# 54c07b2049174cceae5d75abcd11939f
+# d82eff4f2d2d4e8cb8c9fe694607832a
+#: ../../networking/portable_ips.rst:102
+#: ../../networking/acquiring_an_ip_address.rst:32
+msgid "Specify whether you want cross-zone IP or not."
+msgstr "说明是否需要IP跨区。"
+
+# 3c0460b1928b474e8347baf870d93061
+#: ../../networking/portable_ips.rst:104
+msgid "Click Yes in the confirmation dialog."
+msgstr "在确认对话框中点击确定。"
+
+# c6d079ae16bb440d9430701ba56f68a1
+# 5c09ad0de69f460bbc10914cf114f514
+#: ../../networking/portable_ips.rst:106
+#: ../../networking/acquiring_an_ip_address.rst:40
+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 "稍等一会，新的IP地址会出现，状态栏为会显示为分配。现在可以在端口转发或静态NAT规则中使用此IP地址了。"
+
+# 8f37986b8a4e47ba93264a3bb9af1a18
+#: ../../networking/portable_ips.rst:112
+msgid "Transferring Portable IP"
+msgstr "便携式IP"
+
+# 8a4e3d4a96ea471794ae2d68687fa797
+#: ../../networking/portable_ips.rst:114
+msgid ""
+"An IP can be transferred from one network to another only if Static NAT is "
+"enabled. However, when a portable IP is associated with a network, you can "
+"use it for any service in the network."
+msgstr "IP要从一个网络转换至另一网络的话，只需启用静态NAT。但是，当一个portable IP对应一个网络的时候，你可以在网络中为任何服务使用它 。"
+
+# 680b04281ce240339902b0a08da4ecd8
+#: ../../networking/portable_ips.rst:118
+msgid ""
+"To transfer a portable IP across the networks, execute the following API:"
+msgstr "要跨网络转换一个portable IP，执行下列API："
+
+# 8a701f169d1449e7b4cc16e3e4ae8b8f
+#: ../../networking/portable_ips.rst:125
+msgid ""
+"Replace the UUID with appropriate UUID. For example, if you want to transfer"
+" a portable IP to network X and VM Y in a network, execute the following:"
+msgstr "用正确的UUID替换此处的UUID。比如，如果你想转换一个portable IP至X网络和一个网络中的VM Y，请执行下列操作："
+
+# 7089d5ba1bd84cd788dd5c22ca2b1bd2
+#: ../../networking/multiple_subnets_in_shared_network.rst:18
+msgid "Multiple Subnets in Shared Network"
+msgstr "共享网络中的多子网"
+
+# 0477f56fce2e483d8971ed6598538bac
+#: ../../networking/multiple_subnets_in_shared_network.rst:20
+msgid ""
+"CloudStack provides you with the flexibility to add guest IP ranges from "
+"different subnets in Basic zones and security groups-enabled Advanced zones."
+" For security groups-enabled Advanced zones, it implies multiple subnets can"
+" be added to the same VLAN. With the addition of this feature, you will be "
+"able to add IP address ranges from the same subnet or from a different one "
+"when IP address are exhausted. This would in turn allows you to employ "
+"higher number of subnets and thus reduce the address management overhead. "
+"You can delete the IP ranges you have added."
+msgstr "CloudStack为你提供了在基本zones和启用了安全组的高级zones不同的子网中灵活的添加来宾IP段功能 。在启用了安全组的高级zones中，这意味着多子网可以被添加到同一个VLAN。这个特性还意味着，当IP地址用尽的时候，你可以从同一个子网或从不同的子网添加IP地址范围。这将允许你使用更多的子网，降低地址管理工作量。你也可以删除已经添加的IP地址范围。"
+
+# 2ad5b5d4ac7c4c81bb8f93f0bc9ec255
+# 788fe7caacfd434d9974e747cc5b6975
+# 6a8d2ba526f244f0867dd3ba399837cc
+#: ../../networking/multiple_subnets_in_shared_network.rst:32
+#: ../../networking/global_server_load_balancing.rst:255
+#: ../../networking/ip_forwarding_and_firewalling.rst:107
+msgid "Prerequisites and Guidelines"
+msgstr "先决条件和指南"
+
+# 6ba395678a3b488d83285fef91d03eb8
+#: ../../networking/multiple_subnets_in_shared_network.rst:34
+msgid "This feature can only be implemented:"
+msgstr "这个特性只能被实现在："
+
+# d0797766d8c8418a944d9351c7a7d5f2
+#: ../../networking/multiple_subnets_in_shared_network.rst:36
+msgid "on IPv4 addresses"
+msgstr "IPv4地址"
+
+# dfbc41f238524d26b2412643554b3dda
+#: ../../networking/multiple_subnets_in_shared_network.rst:38
+msgid "if virtual router is the DHCP provider"
+msgstr "如果虚拟路由是由DHCP提供的"
+
+# b16927d0778c489d8684d17d6d5080a5
+#: ../../networking/multiple_subnets_in_shared_network.rst:40
+msgid "on KVM, xenServer, and VMware hypervisors"
+msgstr "在KVM，XenServer和VMware hypervisors"
+
+# da5c39ee692344d9ad7e4baa53792f99
+#: ../../networking/multiple_subnets_in_shared_network.rst:42
+msgid ""
+"Manually configure the gateway of the new subnet before adding the IP range."
+msgstr "在添加IP范围之前，手动配置新子网的网关。"
+
+# 12c49c34743945559bdac3337e94b72b
+#: ../../networking/multiple_subnets_in_shared_network.rst:45
+msgid ""
+"CloudStack supports only one gateway for a subnet; overlapping subnets are "
+"not currently supported"
+msgstr "CloudStack只支持一个子网对应一个网关；交叉子网目前不支持。"
+
+# 5e0122bb568b4cb89567b4d417ff860d
+#: ../../networking/multiple_subnets_in_shared_network.rst:50
+msgid "Adding Multiple Subnets to a Shared Network"
+msgstr "给共享网络添加多子网"
+
+# 5dead61f678f4f708dc471eb41eb51d7
+#: ../../networking/multiple_subnets_in_shared_network.rst:56
+msgid ""
+"On Zones, click View More, then click the zone to which you want to work "
+"with.."
+msgstr "在Zones上，点击查看更多，然后点击你要进行操作的zone.."
+
+# 113bdf0910ef4fa181ae7e1dd6b4965a
+#: ../../networking/multiple_subnets_in_shared_network.rst:59
+msgid "Click Physical Network."
+msgstr "点击物理网络。"
+
+# 93cb70825bb2406bb280993bb96c1423
+#: ../../networking/multiple_subnets_in_shared_network.rst:63
+msgid "Click Networks."
+msgstr "点击网络。"
+
+# a8776092b5274a8f85bb80eea30fc74e
+#: ../../networking/multiple_subnets_in_shared_network.rst:65
+msgid "Select the networks you want to work with."
+msgstr "选择你想要操作的网络。"
+
+# 1bee5ce455ca48a99e79744a7d62e425
+#: ../../networking/multiple_subnets_in_shared_network.rst:67
+msgid "Click View IP Ranges."
+msgstr "点击查看IP范围。"
+
+# bda3572323594aa4b29c6a6b5757d2b3
+#: ../../networking/multiple_subnets_in_shared_network.rst:69
+msgid "Click Add IP Range."
+msgstr "点击添加IP范围。"
+
+# 9f735ab5dccd454ba2337ef570347dd5
+#: ../../networking/multiple_subnets_in_shared_network.rst:71
+msgid "The Add IP Range dialog is displayed, as follows:"
+msgstr "显示的添加IP范围对话框如下："
+
+# 83f6544a7bc44bc09cf19bfaf591db11
+#: ../../networking/multiple_subnets_in_shared_network.rst:73
+msgid "|add-ip-range.png|"
+msgstr "|add-ip-range.png|"
+
+# d555abc08eb3476c9e5aa15b14cb5ecb
+# fbc89fdbac934907bce2121e6b919e02
+#: ../../networking/multiple_subnets_in_shared_network.rst:77
+#: ../../networking/virtual_private_cloud_config.rst:250
+msgid "All the fields are mandatory."
+msgstr "所有的区域必须填写的。"
+
+# a0f1b8e275a849a79eefa4a842795497
+# da34b3884ae5434b9e9aa6bcf68fd955
+#: ../../networking/multiple_subnets_in_shared_network.rst:79
+#: ../../networking/virtual_private_cloud_config.rst:262
+msgid ""
+"**Gateway**: The gateway for the tier you create. Ensure that the gateway is"
+" within the Super CIDR range that you specified while creating the VPC, and "
+"is not overlapped with the CIDR of any existing tier within the VPC."
+msgstr "**网关**：你创建网络层的网关。确保网关在你创建VPC时指定的超级CIDR范围内，并且不能与已存在VPC的任何网络层的CIDR重叠。"
+
+# 9a478560b45f4c7fa3a7749ae1781e2f
+# 625aa7b3683d4ab686623285a759d03e
+#: ../../networking/multiple_subnets_in_shared_network.rst:84
+#: ../../networking/virtual_private_cloud_config.rst:275
+msgid "**Netmask**: The netmask for the tier you create."
+msgstr "**子网掩码**：你创建的网络层的子网掩码。"
+
+# bc0ecfa80a4b43e4881c58b85f681266
+# c8ffd6a926fe4eefbdc0e84ebc7dd348
+#: ../../networking/multiple_subnets_in_shared_network.rst:86
+#: ../../networking/virtual_private_cloud_config.rst:277
+msgid ""
+"For example, if the VPC CIDR is 10.0.0.0/16 and the network tier CIDR is "
+"10.0.1.0/24, the gateway of the tier is 10.0.1.1, and the netmask of the "
+"tier is 255.255.255.0."
+msgstr "比如，如果VPC CIDR是10.0.0.0/16并且该网络层CIDR是10.0.1.0/24，那么这个网络层的网关是10.0.1.1，子网掩码是255.255.255.0."
+
+# b48ff10b434e49e5abe6714cfb3452d9
+#: ../../networking/multiple_subnets_in_shared_network.rst:90
+msgid ""
+"**Start IP/ End IP**: A range of IP addresses that are accessible from the "
+"Internet and will be allocated to guest VMs. Enter the first and last IP "
+"addresses that define a range that CloudStack can assign to guest VMs ."
+msgstr "**起始/结束IP**：从互联网获得的和将被分配给来宾VMsIP地址范围。输入第一个和最后一个IP地址，该地址范围定义的是CloudStack能分配给来宾VMs的范围。"
+
+# cc7a99018f204eb3b14ae4407e439d52
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:18
+msgid "Isolation in Advanced Zone Using Private VLAN"
+msgstr "使用Private VLAN隔离高级Zone中的网络"
+
+# d4c63a56d1c541179877426fec001db5
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:20
+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 users' VMs."
+msgstr "在共享网络中的隔离来宾流量能被Private VLAN（PVLAN）获取。PVLANs提供同一个VLAN里端口间的2层网络隔离。在启用了PVLAN的共享网络，一个用户VM不能到达其他用户VM，但是他们能与DHCP服务器和网关通讯，反过来这样能允许用户去控制网络内部的流量，并且帮助他们像阻止与其他用户VMs通讯一样的去部署无需通讯的多个应用程序。"
+
+# 662c4fdd4bd34b7b9c55b5525c739c11
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:29
+msgid "Isolate VMs in a shared networks by using Private VLANs."
+msgstr "使用PVLAN在共享网络中隔离VMs。"
+
+# 1a255e04a5154ff0be5f76264b93453e
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:31
+msgid "Supported on KVM, XenServer, and VMware hypervisors"
+msgstr "在KVM，XenServer和VMware hypervisors中支持"
+
+# 8f8a37c238cc4670b3152c2a622787c7
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:33
+msgid ""
+"PVLAN-enabled shared network can be a part of multiple networks of a guest "
+"VM."
+msgstr "启用了PVLAN的共享网络可以是来宾VM的多个网络的一部分。"
+
+# 8be0c81861ea4d4f9f8a9e2403e11250
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:38
+msgid "About Private VLAN"
+msgstr "关于Private VLAN"
+
+# 19221ad3a5f64011b70c802da07bee31
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:40
+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 VLAN that is being divided "
+"into smaller groups is called Primary, which implies that all VLAN pairs in "
+"a private VLAN share the same Primary VLAN. All the secondary VLANs exist "
+"only inside the Primary. Each Secondary VLAN has a specific VLAN ID "
+"associated to it, which differentiates one sub-domain from another."
+msgstr "在以太网交换机中，VLAN是二层网络中的一个主机之间主机能建立直接通讯的广播域 。Private VLAN被设计成一个标准的VLAN的延伸，为了进一步细分逻辑广播域。一个规则的VLAN是单一广播域，但是一个 private VLAN将一个较大的VLAN广播域划分为较小的多个子域。子域表现为一对VLANs：一个主VLAN和一个辅助VLAN。被划分为较小组的原始VLAN叫主，这意味着所有的在private VLAN中的VLAN对共享着同一个主VLAN。所有的辅助VLANs存在与主VLAN中。每个辅助VLAN有一个特定的区别于其他子域VLAN ID。"
+
+# c46e1be64b4e467aaa0a2109cb87bc24
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:53
+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 "在private VLAN中有三种端口类型，它们实质上决定了所包含的主机的流量走势。每组端口都有自己唯一的策略，它能控制配置同一个private VLAN域中连接到端口的主机与其他已连接主机的通讯。使用下面三种端口定义中的一种来配置每个PVLAN对中的主机："
+
+# 8773791ad68744dbbef479a5a63348f1
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:60
+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 "**混杂模式（Promiscuous）**：混杂模式的端口能与所有的接口通讯，包括可通讯与隔离属于辅助VLANs的主机端口。在混杂模式中，主机被连接到混在模式端口并且能够直接与主VLAN和辅助VLAN中的资源。典型的连接到混杂模式端口的是路由器，DHCP服务器和其他受信任的设备。"
+
+# 91c780247f2c4db2a19e098d51fb2a1f
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:68
+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 "**隔离(Isolated)VLANs**: 隔离模式VLAN中的端口不能与其他二层网络中的端口通讯。连接隔离模式端口上的主机只能直接与混杂模式下的资源通讯。如果你的客户设备只访问网关路由器，请将其附加至隔离端口。"
+
+# 4e94602bf9fa44c6b94244cf55cb1aeb
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:74
+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 communicate among themselves, deploy them in "
+"community ports."
+msgstr "**Community VLANs**：中的端口能与其他端口和混杂模式下的端口通讯，但是他们不能与二层网络中的其他community VLAN中的端口通讯。在Community模式下，主机能与同一community中的主机和连接到混杂模式中的主VLAN的主机可以通讯。如果你的客户有两个设备需要与其他客户的设备隔离，但是他们之间又要通讯，请将他们部署至 community 端口。"
+
+# 362d4b4e5dd242628fe508d3abbe3361
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:84
+msgid "For further reading:"
+msgstr "延伸阅读："
+
+# 9dc2e8a81d2e4418ae9f6222887a9bd3
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:86
+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 "`理解 Private VLANs <http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_25_see/configuration/guide/swpvlan.html#wp1038379>`_"
+
+# 7e9fd9cf1c9b469ebd5bd961175982df
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:89
+msgid ""
+"`Cisco Systems' Private VLANs: Scalable Security in a Multi-Client "
+"Environment <http://tools.ietf.org/html/rfc5517>`_"
+msgstr "`Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment <http://tools.ietf.org/html/rfc5517>`_"
+
+# 7cd6254dad1c4523b2c2be1867cca7cb
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:92
+msgid ""
+"`Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview "
+"(1010691) <http://kb.vmware.com>`_"
+msgstr "`Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview (1010691) <http://kb.vmware.com>`_"
+
+# e7159581e2aa4e7f82fcc3e3e5b8e9b2
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:99
+msgid "Use a PVLAN supported switch."
+msgstr "在支持的交换机上使用PVLAN。"
+
+# 558f121cf82b419cbacce6914151513e
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:101
+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 "更多信息，请参考 `Private VLAN Catalyst Switch Support Matrix <http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a0080094830.shtml>`_ "
+
+# bc44ba94ec284076984bcf8bd7345e42
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:105
+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 "将所有能识别PVLAN的二层交换机之间互连，并且其中一个要连至一个路由器。主机连接到的所有端口需配置为trunk模式。打开VLAN管理，主VLAN（公共网络）和隔离的辅助VLAN端口。配置交换机连接到路由器的端口为PVLAN混杂trunk，这样可以为不识别PVLAN的路由器转换一个隔离的VLAN到主VLAN。"
+
+# 71abf1e9b2ae4a149e565ca17b45f51c
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:113
+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 "注意只有Cisco Catalyst 4500有PVLAN混杂trunk模式，可以连接所有普通VLAN和PVLAN到不能识别PVLAN的交换机。其他支持PVLAN的Catalyst交换机，在PVALN对中的每个交换机上使用级联线连接到上联交换机。"
+
+# 6b7feb8b8f8646848e0fc9321c60bb0f
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:118
+msgid "Configure private VLAN on your physical switches out-of-band."
+msgstr "在你的物理交换机上使用带外管理配置private VLAN。"
+
+# 06b27f4c4355406886e4aa1e037d9467
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:120
+msgid "Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS)."
+msgstr "在XenServer和KVM上使用PVALN之前，请启用Open vSwitch (OVS)。"
+
+# d9b9a5e0ce044d7b94cc7f36f40dac75
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:123
+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 "XenServer和KVM中的OVS不支持原生的PVLAN。因此，靠修改flow table，CloudStack为XenServer和KVM模拟OVS中的PVLAN。"
+
+# 579764808b8b4cee81634b52e650e7f4
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:129
+msgid "Creating a PVLAN-Enabled Guest Network"
+msgstr "配置一个启用了PVLAN的来宾网络"
+
+# 5fd76d10b7a245ca92d599f5d84b04aa
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:161
+msgid ""
+"**Secondary Isolated VLAN ID**: The unique ID of the Secondary Isolated "
+"VLAN."
+msgstr "**辅助隔离VLAN ID**：辅助隔离VLAN的唯一ID。"
+
+# ba80bf59655f4806845c6b592500c85a
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:164
+msgid ""
+"For the description on Secondary Isolated VLAN, see `About Private VLAN\" "
+"<#about-private-vlan>`_."
+msgstr "更多关于辅助隔离VLAN的描述，请参考see `关于 Private VLAN\" <#about-private-vlan>`_."
+
+# cb6cc7de1ccf43ceb4fee732f2374d3a
+#: ../../networking/security_groups.rst:18
+msgid "Security Groups"
+msgstr "安全组"
+
+# d27a88932a2a40c580ff31cd04f7c5b1
+#: ../../networking/security_groups.rst:21
+msgid "About Security Groups"
+msgstr "关于安全组"
+
+# f5ba715a47234ff3a2bb8f9c56d490ab
+#: ../../networking/security_groups.rst:23
+msgid ""
+"Security groups provide a way to isolate traffic to VMs. 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. Security groups are particularly useful in zones that use basic "
+"networking, because there is a single guest network for all guest VMs. In "
+"advanced zones, security groups are supported only on the KVM hypervisor."
+msgstr "安全组提供一种方法来隔离VMs流量。一个安全组是一组依照设置名为入口规则和出口规则来过滤他们进出流量的VMs，这些规则依靠与VM通讯的IP地址来过滤网络流量。安全组在使用基础网络的zones中尤为重要，因为这里只有一个来宾网络。在高级zones中，只有KVM hypervisor支持安全组。"
+
+# 29c17e93f2554fe99e042dbc72b337d9
+#: ../../networking/security_groups.rst:33
+msgid ""
+"In a zone that uses advanced networking, you can instead define multiple "
+"guest networks to isolate traffic to VMs."
+msgstr "在一个使用高级网络的zone中，你可以改为定义多个来宾网络隔离流量至VMs。"
+
+# b0e658a849c44ade96fd212d6c6b2589
+#: ../../networking/security_groups.rst:36
+msgid ""
+"Each CloudStack account comes with a default security group that denies all "
+"inbound traffic and allows all outbound traffic. The default security group "
+"can be modified so that all new VMs inherit some other desired set of rules."
+msgstr "每个CloudStack账号匹配一个拒绝所有入站流量和允许所有出口流量的默认安全组 。可以编辑默认的安全组以便所有新VMs的策略继承一些的想要的设置。"
+
+# 03c3350e08fe420da4f2f221c5773dba
+#: ../../networking/security_groups.rst:41
+msgid ""
+"Any CloudStack user can set up any number of additional security groups. "
+"When a new VM is launched, it is assigned to the default security group "
+"unless another user-defined security group is specified. A VM can be a "
+"member of any number of security groups. Once a VM is assigned to a security"
+" group, it remains in that group for its entire lifetime; you can not move a"
+" running VM from one security group to another."
+msgstr "任何CloudStack用户可以增加任意数量的安全组。当一个新的VM运行起来的时候，它会被添加到默认安全组除非其他用户指定了其他安全组。一个VM可以是任何安全组的成员。一旦VM被添加到一个安全组，它会继承这个组的生命周期；你不能移动一台正在运行的VM到其他安全组。"
+
+# 4b6f67cf254b46589e9ddd94ff94b1bc
+#: ../../networking/security_groups.rst:48
+msgid ""
+"You can modify a security group by deleting or adding any number of ingress "
+"and egress rules. When you do, the new rules apply to all VMs in the group, "
+"whether running or stopped."
+msgstr "你可以通过删除或添加任意的入口和出口策略来修改一个安全组。当你这么做的时候，新的策略会应用到组中的所有VMs，无论是运行的还是关机的。"
+
+# d23292c15bd3444c9ce839ff69392d35
+#: ../../networking/security_groups.rst:52
+msgid ""
+"If no ingress rules are specified, then no traffic will be allowed in, "
+"except for responses to any traffic that has been allowed out through an "
+"egress rule."
+msgstr "如果没有指定入口规则，那么流量会被禁止，除了已经允许通过一个出口规则响应任何流量 。"
+
+# c22e98199bb447fd9a71ddcec88a9deb
+#: ../../networking/security_groups.rst:58
+msgid "Adding a Security Group"
+msgstr "添加一个安全组"
+
+# 8a6a28fa1d434e4fbe428253b48eb3b8
+#: ../../networking/security_groups.rst:60
+msgid "A user or administrator can define a new security group."
+msgstr "一个用户或者管理员能定义一个新的安全组。"
+
+# 1ed905affb2a472aa04efaf4868c54d6
+#: ../../networking/security_groups.rst:66
+msgid "In Select view, choose Security Groups."
+msgstr "在选择视图中，选择安全组。"
+
+# b052c553469c485a8ff0422d5b0abf73
+#: ../../networking/security_groups.rst:68
+msgid "Click Add Security Group."
+msgstr "点击添加安全组。"
+
+# 3db27ac74dd94357a381d19d64f5759e
+#: ../../networking/security_groups.rst:70
+msgid "Provide a name and description."
+msgstr "提供一个名称和描述。"
+
+# 5715f7737e534f99853d1f7ef2ff13f0
+#: ../../networking/security_groups.rst:74
+msgid "The new security group appears in the Security Groups Details tab."
+msgstr "新的安全组出现在安全组详细信息标签中。"
+
+# 581f75deea1c4ce98b419a71f864130e
+#: ../../networking/security_groups.rst:76
+msgid ""
+"To make the security group useful, continue to Adding Ingress and Egress "
+"Rules to a Security Group."
+msgstr "要使安全组生效，继续给这个安全组添加入口和出口策略。"
+
+# f35cc6563a5e4857b8feee6cf88f29a3
+#: ../../networking/security_groups.rst:81
+msgid "Security Groups in Advanced Zones (KVM Only)"
+msgstr "高级区域中的安全组（只针对KVM）"
+
+# fe26402e50fd46458f4ad511d322ba21
+#: ../../networking/security_groups.rst:83
+msgid ""
+"CloudStack provides the ability to use security groups to provide isolation "
+"between guests on a single shared, zone-wide network in an advanced zone "
+"where KVM is the hypervisor. Using security groups in advanced zones rather "
+"than multiple VLANs allows a greater range of options for setting up guest "
+"isolation in a cloud."
+msgstr "以KVM作为虚拟机时，在单共享广域的网络内，CloudStack可以通过安全组来隔离客户。通过使用安全组而不是多VLAN，可以在云中隔离客户时具有更高的灵活性"
+
+# 6199b2fe0a1346459e8db63371e35db5
+#: ../../networking/security_groups.rst:93
+msgid "The following are not supported for this feature:"
+msgstr "下列不支持此功能："
+
+# 68ca4f1c51804347a9af6d0fd227f701
+#: ../../networking/security_groups.rst:95
+msgid ""
+"Two IP ranges with the same VLAN and different gateway or netmask in "
+"security group-enabled shared network."
+msgstr "在开启了安全组的共享网络内，同一VLAN内具有不同网关或掩码的二个IP范围，"
+
+# 6d6ded6fa4fe4853b91bbaea875c3db7
+#: ../../networking/security_groups.rst:98
+msgid ""
+"Two IP ranges with the same VLAN and different gateway or netmask in "
+"account-specific shared networks."
+msgstr "在共享网络的特殊帐户内，同一VLAN内具有不同网关或掩码的二个IP范围"
+
+# fb280b17f22e4093b26c6e9d1891f60c
+#: ../../networking/security_groups.rst:101
+msgid "Multiple VLAN ranges in security group-enabled shared network."
+msgstr "在开启了安全组共享网络的多VLAN范围"
+
+# 465a90dfe47647f28f1d23f859ff2f8a
+#: ../../networking/security_groups.rst:103
+msgid "Multiple VLAN ranges in account-specific shared networks."
+msgstr "在共享网络的特殊帐户内，多个VLAN范围"
+
+# d5d9f22d58634efcbbd25a21f05d9ddf
+#: ../../networking/security_groups.rst:105
+msgid ""
+"Security groups must be enabled in the zone in order for this feature to be "
+"used."
+msgstr "为使用此特性，在区域内必须开启安全组"
+
+# 4f0382c2c0e349d0b3df1e3c6f9ae199
+#: ../../networking/security_groups.rst:110
+msgid "Enabling Security Groups"
+msgstr "开启安全组"
+
+# 5b48cea9b0254d6b92404b64173b5f9f
+#: ../../networking/security_groups.rst:112
+msgid ""
+"In order for security groups to function in a zone, the security groups "
+"feature must first be enabled for the zone. The administrator can do this "
+"when creating a new zone, by selecting a network offering that includes "
+"security groups. The procedure is described in Basic Zone Configuration in "
+"the Advanced Installation Guide. The administrator can not enable security "
+"groups for an existing zone, only when creating a new zone."
+msgstr "使用安全组功能之前，必须先在Zone中启用安全组功能。系统管理员可以在创建一个新的Zone时，通过选择带‘安全组’功能的网络方案进行启用。在高级安装指南的基本Zone配置中有该过程的详细描述。系统管理员不能对现有Zone启用安全组，只能在新建Zone时启用。"
+
+# f31414cc005f439194236fdcf63adaba
+#: ../../networking/security_groups.rst:122
+msgid "Adding Ingress and Egress Rules to a Security Group"
+msgstr "对安全组添加入口出口规则"
+
+# 13f6fe7914834d94be54eccfd3a6571e
+#: ../../networking/security_groups.rst:126
+msgid "In the left navigation, choose Network"
+msgstr "在左侧的导航栏，选择网络"
+
+# 012c6f8bd96840d5b500950bbb99d37a
+#: ../../networking/security_groups.rst:128
+msgid ""
+"In Select view, choose Security Groups, then click the security group you "
+"want."
+msgstr ""
+
+# c5c93da9ab4542f288c0ea7dacc7015d
+#: ../../networking/security_groups.rst:131
+msgid ""
+"To add an ingress rule, click the Ingress Rules tab and fill out the "
+"following fields to specify what network traffic is allowed into VM "
+"instances in this security group. If no ingress rules are specified, then no"
+" traffic will be allowed in, except for responses to any traffic that has "
+"been allowed out through an egress rule."
+msgstr "为增加入口规则，点击入口规则并填写相应内容，以说明在此安全组内何种网络流量可以到达虚拟机实例。如果没有说明入口规则，则不会允许流量进入。也就只有出口规允许的流量了。"
+
+# a2545fd9c6a14c158863af3aca3b3a6d
+#: ../../networking/security_groups.rst:137
+msgid ""
+"**Add by CIDR/Account**. Indicate whether the source of the traffic will be "
+"defined by IP address (CIDR) or an existing security group in a CloudStack "
+"account (Account). Choose Account if you want to allow incoming traffic from"
+" all VMs in another security group"
+msgstr "**通过CIDR帐户添加**. 表明在CloudStack帐户中是否有CIDR定义的流量来源或是已存在的安全组。如果允许来自另一安全组的所有虚拟机的流量进入，则添加此帐户。"
+
+# b0594fd78a124efd8984037ef17e6b89
+#: ../../networking/security_groups.rst:143
+msgid ""
+"**Protocol**. The networking protocol that sources will use to send traffic "
+"to the security group. TCP and UDP are typically used for data exchange and "
+"end-user communications. ICMP is typically used to send error messages or "
+"network monitoring data."
+msgstr "**协议**. 发送源会使用网络协议来发送流量到安全组。TCP和UDP是典型的二种用来数据交换和终端用户交流的协议。ICMP则用来发送错误信息或网络监控数据"
+
+# 3af9a8d515614eccafed5e09672a8f15
+#: ../../networking/security_groups.rst:148
+msgid ""
+"**Start Port, End Port**. (TCP, UDP only) A range of listening ports that "
+"are the destination for the incoming traffic. If you are opening a single "
+"port, use the same number in both fields."
+msgstr "**开始端口，结束端口**. (仅对TCP，UDP)。目的地为进入流量而设的监听端口范围。如果仅开放了单个端口，则在两者的区域中用同一端口。"
+
+# 27a7bc38a030400e9d8f1dedb608659e
+#: ../../networking/security_groups.rst:152
+msgid ""
+"**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code "
+"that will be accepted."
+msgstr "**ICMP类型，ICMP编码**. (仅对ICMP)。接受的信息及错误码的类型。"
+
+# 0ce4ad2050184376bdd26ed654e59599
+#: ../../networking/security_groups.rst:155
+msgid ""
+"**CIDR**. (Add by CIDR only) To accept only traffic from 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 incoming traffic. For example,"
+" 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr "**CIDR**. (仅通过CIDR添加)。为接受来来自特殊地址块的流量，输入一个CIDR，多个时用逗号隔开。CIDR是进入流量的基础IP地址。例如：192.168.0.0/22，为允许所有CIDR，请设为0.0.0.0/0"
+
+# 91ef8eb9529941acbded2108e7c153e0
+#: ../../networking/security_groups.rst:161
+msgid ""
+"**Account, Security Group**. (Add by Account only) To accept only traffic "
+"from another security group, enter the CloudStack account and name of a "
+"security group that has already been defined in that account. To allow "
+"traffic between VMs within the security group you are editing now, enter the"
+" same name you used in step 7."
+msgstr "**帐户，安全组**. (仅通过帐户添加)。为接受来自另一安全组的流量，输入一个CloudStack帐户和在此帐户中已经定义的安全组的名字。为允许你正在编辑的安全组内虚拟机之间的流量，输入你在第7步使用的相同的名字。"
+
+# 813409a701e84482ab284821eb359fe2
+#: ../../networking/security_groups.rst:167
+msgid "The following example allows inbound HTTP access from anywhere:"
+msgstr "下面这个例子允许内部任何地方的HTTP访问"
+
+# 7ac1c499669b4a3cafd27ef10695d298
+#: ../../networking/security_groups.rst:169
+msgid "|httpaccess.png|"
+msgstr "|httpaccess.png|"
+
+# e1083636f84c412fab7099c64bed463a
+#: ../../networking/security_groups.rst:171
+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 security group. If no egress rules are specified, then all"
+" traffic will be allowed out. Once egress rules are specified, the following"
+" types of traffic are allowed out: traffic specified in egress rules; "
+"queries to DNS and DHCP servers; and responses to any traffic that has been "
+"allowed in through an ingress rule"
+msgstr "为添加一个出口规则，点击出口规则并填写以下内容，以说明在此安全组内的虚拟机，被允许哪一类型的流量送出。如果出口规则没有说明，所以的流量都被允许出去一旦进行了说明，则以下流量可以允许出去：在出口规则中进行说明的，查询DNS和DHCP服务器的，响应来自入口规则允许进入的流量的"
+
+# 69e5e83165db4e4ea9fd33a5bd1b0fff
+#: ../../networking/security_groups.rst:180
+msgid ""
+"**Add by CIDR/Account**. Indicate whether the destination of the traffic "
+"will be defined by IP address (CIDR) or an existing security group in a "
+"CloudStack account (Account). Choose Account if you want to allow outgoing "
+"traffic to all VMs in another security group."
+msgstr "**通过CIDR帐户添加**. 表明流量目的地是否已通过IP地址(CIDR)定义或是CloudStack帐户(Account)内存在的安全组。选择帐户，以允许流量到其安全组内所有虚拟机"
+
+# 63fc0c9e030d4dc193c101bcb0e4b3fb
+#: ../../networking/security_groups.rst:186
+msgid ""
+"**Protocol**. The networking protocol that VMs will use to send outgoing "
+"traffic. TCP and UDP are typically used for data exchange and end-user "
+"communications. ICMP is typically used to send error messages or network "
+"monitoring data."
+msgstr "**协议**. 虚拟机发送流量需要的协议。TCP和UDP是典型的二种用来数据交换和终端用户交流的协议。ICMP则用来发送错误信息或网络监控数据"
+
+# 0aa4b36b063a4f05a08b6a2ebb65d1f7
+#: ../../networking/security_groups.rst:191
+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 "**开始端口，结束端口**. (仅对TCP，UDP) 。目的地为进入流量而设的监听端口范围。如果仅开放了单个端口，则在两者的区域中用同一端口。"
+
+# c2b03378b50f4e2b8ad15946702ddb5c
+#: ../../networking/security_groups.rst:195
+msgid ""
+"**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code "
+"that will be sent"
+msgstr "**ICMP类型，ICMP编码**. (仅对ICMP) 。信息及错误码的类型。"
+
+# f8d9e0334b9a4b1faa27a9fa5f918dae
+#: ../../networking/security_groups.rst:198
+msgid ""
+"**CIDR**. (Add by CIDR only) To send traffic only to 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 "**CIDR**. (仅通过CIDR添加) 。为接受来来自特殊地址块的流量，输入一个CIDR，多个时用逗号隔开。CIDR是进入流量的基础IP地址。例如：192.168.0.0/22，为允许所有CIDR，请设为0.0.0.0/0"
+
+# 748c734315774d6ea521e50471bbadab
+#: ../../networking/security_groups.rst:204
+msgid ""
+"**Account, Security Group**. (Add by Account only) To allow traffic to be "
+"sent to another security group, enter the CloudStack account and name of a "
+"security group that has already been defined in that account. To allow "
+"traffic between VMs within the security group you are editing now, enter its"
+" name."
+msgstr "**帐户，安全组**. (仅通过帐户添加) 。为接受来自另一安全组的流量，输入一个CloudStack帐户和在此帐户中已经定义的安全组的名字。为允许你正在编辑的安全组内虚拟机之间的流量，输入名字。"
+
+# 121a5a4d0fdf4adbadf0e9018abbb3f2
+#: ../../networking/external_firewalls_and_load_balancers.rst:18
+msgid "External Firewalls and Load Balancers"
+msgstr "外部防火墙及负载均衡"
+
+# da0033de7a88452b92b35dc42a5409ca
+#: ../../networking/external_firewalls_and_load_balancers.rst:20
+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 "CloudStack允许通过外部的Jniper SRX 设备和外部NetScaler设备或网关负载均衡设备和负载均衡服务。在此情形下，虚拟机使用SRX作为网关。"
+
+# 1758f3bbc4ec49b6a87df151d32c7822
+#: ../../networking/external_firewalls_and_load_balancers.rst:27
+msgid "About Using a NetScaler Load Balancer"
+msgstr "关于使用NetScaler负载均衡器"
+
+# edf025a8432d4d2e916b9e1e4506292b
+#: ../../networking/external_firewalls_and_load_balancers.rst:29
+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 "在区域中，或高级区域使用隔离网络时，CloudStack支持思杰的NetScaler作为外部网络设备元素作为负责均衡。拟通过其他方案提供负载均衡而不是CloudStack的虚拟路由器时，就可以建立一个外部负载均衡器"
+
+# e6c1fa94b4a44fe9af51313b701a4c0a
+#: ../../networking/external_firewalls_and_load_balancers.rst:35
+msgid ""
+"In a Basic zone, load balancing service is supported only if Elastic IP or "
+"Elastic LB services are enabled."
+msgstr "在基础区域中，仅在弹性IP或弹性负载均衡服务开启时，才支持负载均衡服务"
+
+# 919e3b6335ec43cbb41cd06193a91872
+#: ../../networking/external_firewalls_and_load_balancers.rst:38
+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 device providing "
+"EIP/ELB, layer 3 router must have a policy-based routing. A policy-based "
+"route must be set up so that all traffic originated from the guest VM's are "
+"directed to NetScaler device. This is required to ensure that the outbound "
+"traffic from the guest VM's is routed to a public IP by using NAT.For more "
+"information on Elastic IP, see `\"About Elastic IP\" <#about-elastic-ip>`_."
+msgstr "在基础域中使用NetScaler负载均衡提供EIP或ELB服务时，确保所有的客户虚拟机流量必须通过NetScaler设备进出。当入流量通过NetScaler设备时流量通过使用NAT协议被路由，此NAT协议依赖于公共IP到私有IP的配置。来自客户虚拟机的流量通常要经过3层路由器，为确保出流量通过提供EIP/ELB的NetScaler设备，3层路由器，必须具有基础策略。必有设立一个具有基础策略的路由器可保证所有客户机的流量都能转向NetScaler设备。这也需要确保客户虚拟机的出流量通过使用NAT被路由到公共IP。关于EIP的更多信息，参看`\"关于EIP\" <#about-elastic-ip>`_."
+
+# e8f3e9f2b1bd412a99284612b6c7e030
+#: ../../networking/external_firewalls_and_load_balancers.rst:52
+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 "NetScaler可以设置成直通模式。它必须在区域中部署客户虚拟机负载均衡规则之前加入。"
+
+# 523f98e01f234306b388d42100392a01
+#: ../../networking/external_firewalls_and_load_balancers.rst:56
+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 "CloudStack中NetScaler的功能作用与CloudStack文档中说明的使用F5 外部负载均衡器的功能作用相同。一点差别就是，F5支持路由域名，而NetScaler无此功能。NetScaler也不可以用作防火墙。"
+
+# 9526107823ab4b9bbdf3aeabea512cbd
+#: ../../networking/external_firewalls_and_load_balancers.rst:61
+msgid ""
+"To install and enable an external load balancer for CloudStack management, "
+"see External Guest Load Balancer Integration in the Installation Guide."
+msgstr "为CLOUDSTACK管理端安装和启用外部负载均衡功能，参阅安装文档里的外部客户负载均衡。"
+
+# b606dd0a26944ae7abe244a91ae68dce
+#: ../../networking/external_firewalls_and_load_balancers.rst:65
+msgid ""
+"The Citrix NetScaler comes in three varieties. The following summarizes how "
+"these variants are treated in CloudStack."
+msgstr ""
+
+# 4d4acf453ee34b99bcd9422624a29d4f
+#: ../../networking/external_firewalls_and_load_balancers.rst:68
+msgid "**MPX**"
+msgstr ""
+
+# 31bf9c295f6f41ceba97d553ee88a09e
+#: ../../networking/external_firewalls_and_load_balancers.rst:70
+msgid ""
+"Physical appliance. Capable of deep packet inspection. Can act as "
+"application firewall and load balancer"
+msgstr "物理应用。能够进行深度数据包检测。可作为防火墙和负载均衡应用。"
+
+# 9393642591e14352a7b452e06213da83
+#: ../../networking/external_firewalls_and_load_balancers.rst:73
+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 "在高级区域中，完全支持负载均衡功能，没有限制。在基础区域中，也提供静态NAT，EIP，ELB功能。"
+
+# b9313747ed1d4f2bb9ceb37cc651ef0e
+#: ../../networking/external_firewalls_and_load_balancers.rst:77
+msgid "**VPX**"
+msgstr ""
+
+# 726835d9e8994018bac41442046eebab
+#: ../../networking/external_firewalls_and_load_balancers.rst:79
+msgid ""
+"Virtual appliance. Can run as VM on XenServer, ESXi, and Hyper-V "
+"hypervisors. Same functionality as MPX"
+msgstr "虚拟应用，可以运行在XenServer，ESXi以及Hyper-V上虚拟机上。与MPX功能相同。"
+
+# c85737d038fa4926a9e5e9ea965a24ce
+#: ../../networking/external_firewalls_and_load_balancers.rst:82
+msgid ""
+"Supported on ESXi and XenServer. Same functional support as for MPX. "
+"CloudStack will treat VPX and MPX as the same device type."
+msgstr "在ESXi和XenServer上支持。对MPX也支持一些功能。CloudStack将VPX和MPX作为同一类型的设备看待。"
+
+# 6aa4be1b809449b48793dde65f3fee9c
+#: ../../networking/external_firewalls_and_load_balancers.rst:85
+msgid "**SDX**"
+msgstr ""
+
+# ffe20a22c29347ff81fd3ac28699bc4c
+#: ../../networking/external_firewalls_and_load_balancers.rst:87
+msgid ""
+"Physical appliance. Can create multiple fully isolated VPX instances on a "
+"single appliance to support multi-tenant usage"
+msgstr "物理应用。可以在单个应用上创建多个完全隔离的VPX实例，以支持多客户使用。"
+
+# 363ff0dd6af349ae9fb5dfe4b0264655
+#: ../../networking/external_firewalls_and_load_balancers.rst:90
+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 "CloudStack会动态分配，配置，管理在SDX上的虚拟机实例的生命周期。分配的实例会自动加入到CloudStack，不需要管理员进行手动配置。一旦一个VPX实例加入到CloudStack，将会认为是ESXi主机上的一个VPX。"
+
+# 48be3cf5cf894ea3be2012a3fd52b693
+#: ../../networking/external_firewalls_and_load_balancers.rst:98
+msgid "Configuring SNMP Community String on a RHEL Server"
+msgstr "在RHEL服务器上配置SNMP社区字符串"
+
+# 124686b380a8434fbe22ff4861dcf466
+#: ../../networking/external_firewalls_and_load_balancers.rst:100
+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 "SNMP社区字符串类似于用户ID或用户密码，用来登录网络设备，如路由器。这类字符串随着所有的SNMP请求发送。如果社区字符串正确，设备将反馈相应的字符串若不正确，设备将丢弃请求，不进行处理。"
+
+# db1b06466d9042489699add305179ed0
+#: ../../networking/external_firewalls_and_load_balancers.rst:106
+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 "NetScaler设备使用SNMP与虚拟机进行通讯。为保证NetScaler设备与RHEL机器之间安全的通讯，必须安装并配置社区字符串。"
+
+# 86bf1082cfba4dd0ab1ae1cd1fc55280
+#: ../../networking/external_firewalls_and_load_balancers.rst:110
+msgid ""
+"Ensure that you installed SNMP on RedHat. If not, run the following command:"
+msgstr "确保在RedHat上安装了SNMP，如果没有，执行以下命令:"
+
+# b57fd1f457bb47559202771c0c0e81b9
+#: ../../networking/external_firewalls_and_load_balancers.rst:117
+msgid ""
+"Edit the /etc/snmp/snmpd.conf file to allow the SNMP polling from the "
+"NetScaler device."
+msgstr "编辑/etc/snmp/snmpd.conf 文件，以允许来自NetScaler设备的SNMP查询"
+
+# 7cc4f86ef08341519c58b04122531955
+#: ../../networking/external_firewalls_and_load_balancers.rst:120
+msgid ""
+"Map the community name into a security name (local and mynetwork, depending "
+"on where the request is coming from):"
+msgstr "映射社区名到一个安全的名字（本地，我的网络，依赖于其来源）"
+
+# 96e1da8de4da414f8ba5659fc97790f5
+#: ../../networking/external_firewalls_and_load_balancers.rst:124
+msgid ""
+"Use a strong password instead of public when you edit the following table."
+msgstr "编辑下表时，使用一个强密码"
+
+# e0dfb13b632f40ee91f2522b6545638c
+#: ../../networking/external_firewalls_and_load_balancers.rst:133
+msgid "Setting to 0.0.0.0 allows all IPs to poll the NetScaler server."
+msgstr "设置0.0.0.0以允许所有的IP都可以查询NetScaler设备"
+
+# 8bbf09e13cf4449eab6802c2e431d166
+#: ../../networking/external_firewalls_and_load_balancers.rst:135
+msgid "Map the security names into group names:"
+msgstr "映射一个安全名到组名"
+
+# 28f26a19a75e4d38b8cbe455da453945
+#: ../../networking/external_firewalls_and_load_balancers.rst:145
+msgid "Create a view to allow the groups to have the permission to:"
+msgstr "创建一个视图，以允许组有权限执行："
+
+# cbb139269f8f422ea3ced1eb9e1f20d4
+#: ../../networking/external_firewalls_and_load_balancers.rst:151
+msgid ""
+"Grant access with different write permissions to the two groups to the view "
+"you created."
+msgstr "授权不同的写权限给二个组及你创建的视图"
+
+# 4b8fa0c0c42b41e585535c6e0a66012c
+#: ../../networking/external_firewalls_and_load_balancers.rst:160
+msgid "Unblock SNMP in iptables."
+msgstr "在iptalbes中解除对SNMP的锁定。"
+
+# 62e7b099d03c4a73bfcac8ea208630d3
+#: ../../networking/external_firewalls_and_load_balancers.rst:166
+msgid "Start the SNMP service:"
+msgstr "开启SNMP服务："
+
+# 54522a637adb4007a9a82f11819c2c59
+#: ../../networking/external_firewalls_and_load_balancers.rst:172
+msgid ""
+"Ensure that the SNMP service is started automatically during the system "
+"startup:"
+msgstr "确保在系统启动时，SNMP服务能够自动启动。"
+
+# 5949212234ed48b6adc372a7c7ce1637
+#: ../../networking/external_firewalls_and_load_balancers.rst:181
+msgid "Initial Setup of External Firewalls and Load Balancers"
+msgstr "初始化安装外部防火墙和负载均衡"
+
+# 4cac2b9077964674844de4e3e3a93a0b
+#: ../../networking/external_firewalls_and_load_balancers.rst:183
+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 "当为一个新帐户创建一个虚拟机时，CloudStack会设置程序以让外部防火墙和负载均衡与虚拟机共同工作。会在防火墙上创建以下对象："
+
+# 4bf4042c7f4f4def95f95bb7a9c4c3ec
+#: ../../networking/external_firewalls_and_load_balancers.rst:187
+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 "一个新的逻辑接口，用以连接帐户的私有VLAN。接口的IP通常是私有帐户私有子网的第一个IP。"
+
+# 0691cec2a7cf4c178b39117f7d1ae324
+#: ../../networking/external_firewalls_and_load_balancers.rst:191
+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 "一个源NAT规则转发帐户从私有VLAN到公共网络的的出口流量，使用帐户的公共IP地址作为源地址。"
+
+# 493986833b5c4b068a45f8c644330cc3
+#: ../../networking/external_firewalls_and_load_balancers.rst:195
+msgid ""
+"A firewall filter counter that measures the number of bytes of outgoing "
+"traffic for the account"
+msgstr "防火墙过滤计数器计量帐户出口流量的字节数"
+
+# d94c05bebe7142f69087aa01f32a8dd2
+#: ../../networking/external_firewalls_and_load_balancers.rst:198
+msgid "The following objects are created on the load balancer:"
+msgstr "以下对象会在负载均衡上创建："
+
+# 3038b6bbaf9a40e4bf717fc65b7b5f7a
+#: ../../networking/external_firewalls_and_load_balancers.rst:200
+msgid "A new VLAN that matches the account's provisioned Zone VLAN"
+msgstr "匹配帐户区域VLAN的私有VLAN。"
+
+# 6babff57f8864990afeabf3aa8702676
+#: ../../networking/external_firewalls_and_load_balancers.rst:202
+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 "一个VLAN的自有IP。经常是帐户私有子网的第二个IP。"
+
+# c78efbcb1b344675a63143a5fa305c80
+#: ../../networking/external_firewalls_and_load_balancers.rst:207
+msgid "Ongoing Configuration of External Firewalls and Load Balancers"
+msgstr "继续配置外部防火墙和负载均衡"
+
+# 778d4134b7bd4fec9bc3c731d1dd006f
+#: ../../networking/external_firewalls_and_load_balancers.rst:209
+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 objects:"
+msgstr "增加的用户行为(如设置端口转发)会引起防火墙和负载均衡的程序化。一个用户可以请求增加公共IP地址以及转发使用此公共IP地址的虚拟机接受到的流量。这是通过静态NAT功能完成的，静态NAT将一个公共IP地址映射给一个虚拟机，并指定一组特定协议，开放一组特定端口。当静态NAT建立好之后，CLOUDSTACK会在区域的外部防火墙上通过程序定制如下对象："
+
+# 98d20f26e4be4a6693dbe1d69cbd1dc6
+#: ../../networking/external_firewalls_and_load_balancers.rst:218
+msgid ""
+"A static NAT rule that maps the public IP address to the private IP address "
+"of a VM."
+msgstr "一条静态NAT规则将虚拟机的私有IP地址映射到公共IP地址。"
+
+# 21bcfd0a7295477cb6daae191a4b5300
+#: ../../networking/external_firewalls_and_load_balancers.rst:221
+msgid ""
+"A security policy that allows traffic within the set of protocols and port "
+"ranges that are specified."
+msgstr "一个安全策略可以允许说明的协议和端口范围内的流量通过。"
+
+# d57954e8fd754ec291d98eda142d626c
+#: ../../networking/external_firewalls_and_load_balancers.rst:224
+msgid ""
+"A firewall filter counter that measures the number of bytes of incoming "
+"traffic to the public IP."
+msgstr "防火墙过滤计数器计量到达此公共IP的流量"
+
+# fe43a5a0e7e9497595d1e43626bc76de
+#: ../../networking/external_firewalls_and_load_balancers.rst:227
+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 "通过源NAT，静态NAT以及负载均衡规则进出的字节数均被计量并保存在每一个外部设备中。按一定的规则对这些数据进行收集，并将其存储在CloudStack的数据库中。"
+
+# 6db8db0667bd4e58b757a87adabda6bc
+#: ../../networking/external_firewalls_and_load_balancers.rst:234
+msgid "Load Balancer Rules"
+msgstr "负载均衡规则"
+
+# 146c1ce3466a4755a2e0733761dc4ed0
+#: ../../networking/external_firewalls_and_load_balancers.rst:236
+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 "一个CloudStack的用户或管理员可以创建负载均衡规则以平衡一个公共IP地址收到的针对一个或多个虚拟机的外部流量。一个用户可以创建一条规则，说明一个算法，并将其指定给一部分虚拟机。"
+
+# c95ce127b66547f6922052b2dd046529
+#: ../../networking/external_firewalls_and_load_balancers.rst:242
+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 "如果你创建了一个负载均衡规则且使用包括外部负载均衡设备的网络服务方案，如包括NetScaler，但随后将网络方案改成使用CloudStack的虚拟路由器，则你必须在虚拟路由器上创建一个防火墙规则，这些防火墙规则与已经设置的负载均衡规则一一对应，只有这样，才能使那些负载均衡规则继续起作用。"
+
+# 1cb0607405a54290aac63427224142d3
+#: ../../networking/external_firewalls_and_load_balancers.rst:253
+msgid "Adding a Load Balancer Rule"
+msgstr "增加一条负载均衡规则"
+
+# e9125f99985c4930b8ca325f3fcf515a
+#: ../../networking/external_firewalls_and_load_balancers.rst:259
+msgid ""
+"Click the name of the network where you want to load balance the traffic."
+msgstr "点击拟进行负载均衡的网络名称"
+
+# e2976048502c4d5a9d5bee635ce5ee1b
+# 5b388625f3784583b0752e36f9353e8a
+# aa8c8d52101742e9a804ccc41cbcfbb3
+#: ../../networking/external_firewalls_and_load_balancers.rst:264
+#: ../../networking/virtual_private_cloud_config.rst:1055
+#: ../../networking/virtual_private_cloud_config.rst:1323
+msgid ""
+"Click the IP address for which you want to create the rule, then click the "
+"Configuration tab."
+msgstr "点击你希望创建规则的IP地址，然后点击配置"
+
+# d0100e755da442c3a5f073f8219b5816
+# bc3f9224355b4e66b73a49411a2326b8
+#: ../../networking/external_firewalls_and_load_balancers.rst:267
+#: ../../networking/virtual_private_cloud_config.rst:1058
+msgid "In the Load Balancing node of the diagram, click View All."
+msgstr "在图的负载均衡节点点上，点击 查看全部。"
+
+# aed2916e2f794074898738f6a54fd470
+#: ../../networking/external_firewalls_and_load_balancers.rst:269
+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 "在基础区域中，在不需要或不选择IP的条件下，你可以创建一条负载均衡规则。当你创建负载均衡规则时，CloudStack会内部指定一个IP地址。当规则创建完成时，IP地址会在IP地址页列出来。"
+
+# cdcdffd84542448691328bee08d8de97
+#: ../../networking/external_firewalls_and_load_balancers.rst:274
+msgid ""
+"To do that, select the name of the network, then click Add Load Balancer "
+"tab. Continue with #7."
+msgstr "为此，选择网络名称，点击 增加负载均衡。按#7继续进行配置。"
+
+# c90d375729ae4857b6cbfad14e955c25
+# 899cdfae1e1b423fa4228db904e74d4c
+#: ../../networking/external_firewalls_and_load_balancers.rst:277
+#: ../../networking/ip_forwarding_and_firewalling.rst:265
+msgid "Fill in the following:"
+msgstr "填写以下内容："
+
+# ee36f3f0257549b5a157b2c373cc595f
+# 03c1b13d01dd4d93abf1db0df4d270c3
+# 35a1954cf7ed4135a2a506e65626b63b
+#: ../../networking/external_firewalls_and_load_balancers.rst:279
+#: ../../networking/virtual_private_cloud_config.rst:1064
+#: ../../networking/virtual_private_cloud_config.rst:1249
+msgid "**Name**: A name for the load balancer rule."
+msgstr "**名称**: 负载均衡规则的名称。"
+
+# 13aa4f60513144f581eaaea2a25fc259
+#: ../../networking/external_firewalls_and_load_balancers.rst:281
+msgid "**Public Port**: The port receiving incoming traffic to be balanced."
+msgstr "**公共端口**: 这个端口接受到负载均衡的进入流量。"
+
+# 94a4f9710f0548e9b5efb1ced085ee7c
+# 43dd6392f9004b9ea68310e1bda21332
+#: ../../networking/external_firewalls_and_load_balancers.rst:284
+#: ../../networking/virtual_private_cloud_config.rst:1069
+msgid ""
+"**Private Port**: The port that the VMs will use to receive the traffic."
+msgstr "**私有端口**: 虚拟机会使用此端口接收流量。"
+
+# 6dadc08ee20e449882fb626362f7af7f
+#: ../../networking/external_firewalls_and_load_balancers.rst:287
+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 "**算法**: 选择让CloudStack使用的负载均衡算法。CloudStack各类已知的算法，如果不熟悉那些选项，通过goole搜索会发现大量信息。"
+
+# b7ba39ce29984655a3fee83759341968
+#: ../../networking/external_firewalls_and_load_balancers.rst:292
+msgid ""
+"**Stickiness**: (Optional) Click Configure and choose the algorithm for the "
+"stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr "**粘性**: (可选) 点击配置，为粘性策略选择一个算法。可参见为负载均衡规则制定的粘性会话策略。"
+
+# a79ee74d2a374432bae88b284375af8d
+#: ../../networking/external_firewalls_and_load_balancers.rst:296
+msgid ""
+"**AutoScale**: Click Configure and complete the AutoScale configuration as "
+"explained in :ref:`conf-autoscale`."
+msgstr "**自动缩放**：点击配置完成自动缩放配置，在 :ref:`conf-autoscale`中有介绍。"
+
+# 748f88b5e1234460b650bb46124ebf32
+#: ../../networking/external_firewalls_and_load_balancers.rst:299
+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 "**健康检查**：(可选，只针对NetScaler的负载均衡设备)点击配置并填写健康检查特性，参见15.16.5.3 负载均衡规则的健康检查。参见 :ref:`health-check`."
+
+# 57115cc9cda44c37ab09f3b0a846ddb6
+#: ../../networking/external_firewalls_and_load_balancers.rst:303
+msgid ""
+"**Ping path (Optional)**: Sequence of destinations to which to send health "
+"check queries. Default: / (all)."
+msgstr "**ping 路径(可选)**: 需要发送健康检查的目的地顺序。默认：/ (all)。"
+
+# 4f4a56c64b114bfbbc4a00ffe27666f1
+#: ../../networking/external_firewalls_and_load_balancers.rst:306
+msgid ""
+"**Response time (Optional)**: How long to wait for a response from the "
+"health check (2 - 60 seconds). Default: 5 seconds."
+msgstr "**响应时间(可选)**: 从健康检查返回的响应时间(2-60秒)，默认为5秒。"
+
+# 5d063fd6cf084d458e9bb553fdcaa398
+#: ../../networking/external_firewalls_and_load_balancers.rst:309
+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 "**间隔时间(可选)**: 健康检查的间隔时间(1秒-5分)）。默认值在全局参数 lbrule\\_health check\\_time\\_interval"
+
+# 6550d0fabfa042e698d1e24bab46eae8
+#: ../../networking/external_firewalls_and_load_balancers.rst:314
+msgid ""
+"**Healthy threshold (Optional)**: Number of consecutive health check "
+"successes that are required before declaring an instance healthy. Default: "
+"2."
+msgstr "**健康阀值(可选)**: 在声明一个实例健康之前，连续健康检查成功的次数。默认为2."
+
+# d30d4c6e04f84624988f359219dfe504
+#: ../../networking/external_firewalls_and_load_balancers.rst:318
+msgid ""
+"**Unhealthy threshold (Optional)**: Number of consecutive health check "
+"failures that are required before declaring an instance unhealthy. Default: "
+"10."
+msgstr "**不健康阀值(可选)**: 在声音一个实例不健康之前连续健康检查失败的次数。默认为10。"
+
+# 427464c4195c4474982b88b06a60bd2b
+#: ../../networking/external_firewalls_and_load_balancers.rst:322
+msgid ""
+"Click Add VMs, then select two or more VMs that will divide the load of "
+"incoming traffic, and click Apply."
+msgstr "点击添加虚拟机，选择拟分散进入流量的二个或多个虚拟机，点击应用。"
+
+# b57e6480829e4e1ea39a935dfae60828
+#: ../../networking/external_firewalls_and_load_balancers.rst:325
+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 "在列表中会出现新加的负载均衡规则。可以重复以上步骤以对此IP增加更多的负载均衡规则。"
+
+# 5b7fc7b5ea6d40a5bc3f415a80425764
+#: ../../networking/external_firewalls_and_load_balancers.rst:330
+msgid "Sticky Session Policies for Load Balancer Rules"
+msgstr "为负载均衡规则制定的粘性会话策略。"
+
+# b9827a93606d4bd78ba8176109a6543b
+#: ../../networking/external_firewalls_and_load_balancers.rst:332
+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 "粘性会话应用于基于网页的应用中，以确保在用户的会话中，对用户的多种请求持续提供信息。例如，购物者正在向购物车中增加东西，则需要记住到目前为止已买的东西。粘性的概念也指持久发现或维护状态。"
+
+# a0e599620e7d421795bf10da5e68221f
+#: ../../networking/external_firewalls_and_load_balancers.rst:338
+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, cookies are used. The cookie "
+"generated by the load balancer or application is included in request and "
+"response URLs to create persistence. The cookie name can be specified by the"
+" administrator or automatically generated. A variety of options are provided"
+" to control the exact behavior of cookies, such as how they are generated "
+"and whether they are cached."
+msgstr "在CloudStack中定义的任何负载均衡规则，都可以具有粘性策略。策略有名字，粘性方法以及参数组成。参数是成对的值-名或标志，这些由负载均衡提供商进行定义。粘发现方法可以加载负载均衡设备产生的cookie，应用生产的cookie，或基于源产生的cookie。在基于源的方法中，源IP地址被用来区分用户和定位用户存储的数据。在其他方法中，则使用cookie。由负载均衡或应用产生的cookie，包含在请求或响应的url中，以产生持久性。cookie的名称可以有管理员指定或自动产生。提供了多种选择来准确控制cookie行为。诸如如何产生的以及是否进行缓存。"
+
+# 788d44c8346c41e88c23f175e62c939b
+#: ../../networking/external_firewalls_and_load_balancers.rst:352
+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 "对于多数粘性方法变量列表，可以参看CloudStack UI或者调用网络列表，并检查粘性方法支持能力。"
+
+# 44e5efde27ff453a945b83ed79f8935b
+#: ../../networking/external_firewalls_and_load_balancers.rst:360
+msgid "Health Checks for Load Balancer Rules"
+msgstr "负载均衡规则的健康检查。"
+
+# e0222e643eba40e5b2a9d97fbebef725
+#: ../../networking/external_firewalls_and_load_balancers.rst:362
+msgid "(NetScaler load balancer only; requires NetScaler version 10.0)"
+msgstr "（仅对NetScaler负载均衡设备，需要NetScaler版本10.0以上。）"
+
+# cdf4e72bdd1842b38d1c7c61809209b5
+#: ../../networking/external_firewalls_and_load_balancers.rst:364
+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 "负载均衡应用中的健康检查，能够确保转发需求运行，服务可用。当创建一个负载均衡规则里，你可以指定一个健康检查策略。这是对粘性策略，算法，其他负载均衡设备规则的附加说明。可以为每一条负载均衡设备进行配置。"
+
+# 3186740a23ed4c6ba61108544d0a4aec
+#: ../../networking/external_firewalls_and_load_balancers.rst:371
+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 "在CloudStackk中的NetScaler负载均衡设备定义的任一负载均衡规则都可以有一条健康检查策略。该策略有ping路径，定义健康或非健康状态的阀值，健康检查频率以及等待超时间隔。"
+
+# ec37f719769d4b7386f0b940981fed70
+#: ../../networking/external_firewalls_and_load_balancers.rst:376
+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 with a health check "
+"configured, the state will be shown as UP or DOWN in the UI depending on the"
+" result of the most recent health check."
+msgstr "当健康检查策略生效时，负载均衡被发现处于非健康状态时，会停止转发到源的任何请求。如果随后资源变为可用，周期性进行的健康检查就会发现，此资源就会再一次被添加至从负载均衡器收到的请求资源池里。任一时刻，最近的健康检查结果会显示在UI中。对绑定了负载均衡规则的虚拟机，且此规则配置了健康检查，依据最近的检查，状态会显示为正常或失败。"
+
+# e7b935bafd4a47d68590f912c335e640
+#: ../../networking/external_firewalls_and_load_balancers.rst:386
+msgid "You can delete or modify existing health check policies."
+msgstr "可以删除或修改存在的健康检查策略。"
+
+# c111733988ec45f6bcd2979e368c5226
+#: ../../networking/external_firewalls_and_load_balancers.rst:388
+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 "为配置默认的健康检查执行频率，通过全局配置参数 healthcheck.update.interval进行设备，默认值是600秒。可以根据需要进行设置此值。"
+
+# 4c9ae4abb3c04ebda936ddf28d4b1250
+#: ../../networking/external_firewalls_and_load_balancers.rst:393
+msgid ""
+"For details on how to set a health check policy using the UI, see :ref"
+":`adding-lb-rule`."
+msgstr "如何通过UI进行健康检查策略的设置，可参看 :ref:`adding-lb-rule`。"
+
+# 3d3b622fa6c24a71a43dfb7d262e68ff
+#: ../../networking/external_firewalls_and_load_balancers.rst:400
+msgid "Configuring AutoScale"
+msgstr "配置自缩放"
+
+# 5b23f0c9a3884ba4a454fd703688166f
+#: ../../networking/external_firewalls_and_load_balancers.rst:402
+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 "自缩放允许你能够根据定义的条件进行无缝且自动的增加或减少后端服务或应用虚拟机。当开启自缩放时，可以确保在需求增加时，无缝的增加正在使用虚拟机的数量。因此他会通过关闭未使用的虚拟机或者需要时开启新的虚拟机，从而节省你的计算成本。这些操作，都不需要手动干预。"
+
+# 5141d63f3ea14b7cb903e6c53d86085f
+#: ../../networking/external_firewalls_and_load_balancers.rst:410
+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 CPU usage is less than 20 "
+"percent for 30 minutes."
+msgstr "NetScaler的自缩放定义为基于用户定义的条件，无缝的开启或关闭虚拟机。触发扩大或缩小行为的条件从监控服务器cpu的使用率的单一用例到监控服务器响应及cpu使用率的组合用例，各不相同。例如，你可以一个自缩放，能够在CPU使用超过80%持续15分钟时启动一个新的虚拟机，或CPU使用率低于20%持续30分钟时，移除一个虚拟机。"
+
+# f32191641b9644909945358cb69ebe4d
+#: ../../networking/external_firewalls_and_load_balancers.rst:419
+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 "CloudStack使用NetScaler负载均衡器来监控系统健康的各方面，并与CloudStack共同工作以初始化扩大或缩小的行为。"
+
+# 56002db08e75494cac10bdd7f2b5c707
+#: ../../networking/external_firewalls_and_load_balancers.rst:424
+msgid ""
+"AutoScale is supported on NetScaler Release 10 Build 74.4006.e and beyond."
+msgstr "自缩放在NetScaler发布的10版本以上适用。（Build 74.4006.e 及以上）"
+
+# 45a1a6402e1e40a0a91763809e1b7729
+#: ../../networking/external_firewalls_and_load_balancers.rst:430
+msgid "Before you configure an AutoScale rule, consider the following:"
+msgstr "在配置自缩放前，需要考虑以下几点："
+
+# 0a687417e2094c359d8a604e95095fc5
+#: ../../networking/external_firewalls_and_load_balancers.rst:432
+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 "确保在配置自缩放时有必需的模板。当使用模板部署虚拟机并使虚拟机启动时，应用能够起动并运行。"
+
+# 7d9b17872f514d4c88eedbe080005a94
+#: ../../networking/external_firewalls_and_load_balancers.rst:437
+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 "如果应用没有运行，NetScaler设备会认为虚拟机无效并持续无条件的创建虚拟机，直到资源耗尽。"
+
+# c72572ced880471fa607c51156f11bda
+#: ../../networking/external_firewalls_and_load_balancers.rst:441
+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 "部署准备好的模板。确保应用在第一次启动时能够开启并准备好接管流量。观察部署模板需要的时间。在配置自缩放时，要考虑这段时间。"
+
+# ff134327842d420886adb98a42f2723a
+#: ../../networking/external_firewalls_and_load_balancers.rst:446
+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-server>`_ to configure SNMP on"
+" a RHEL machine."
+msgstr ""
+
+# d8cef4ea8860477489a80f3a715fbd90
+#: ../../networking/external_firewalls_and_load_balancers.rst:456
+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 "确保在全局配置中的结束点地址参数已设置为管理服务器的API地址。例如：``http://10.102.102.22:8080/client/api``。 在多管理节点的部署中，使用配置在负载均衡器上的虚拟IP地址作为管理服务器集群的IP地址。此外，确保NetScaler设备有读取为提供自缩放而配置的IP地址的权限。"
+
+# 1cd70adcb30d47abbcc3dc69e3707036
+#: ../../networking/external_firewalls_and_load_balancers.rst:464
+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 "如果更新了endpointe.url，在系统自动负载均衡器规则里，先关闭自缩放功能随后再开启，以应用此更新。。更多信息，参见 :ref:`update-autoscale`。"
+
+# 55df6ae7033b4ca3a3f52dd90fd74501
+#: ../../networking/external_firewalls_and_load_balancers.rst:468
+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 "如果为自缩放用户生成了API值和秘钥，确保用户参与的负载均衡器的自缩放功能先关闭，再开启，以应用NetScaler配置的变化。"
+
+# f6552bde1aaf4055b316eb9c17b5f64a
+#: ../../networking/external_firewalls_and_load_balancers.rst:473
+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 "在高级区域中，在配置带自缩放的负载均衡规则时，确保至少要有一个虚拟机。在网络中存在一个虚拟机，可保证在配置自缩放时，网络处于使用状态。"
+
+# a79a1b3a477d4397abe465f3b5ba2c56
+#: ../../networking/external_firewalls_and_load_balancers.rst:480
+msgid "Configuration"
+msgstr "配置"
+
+# 7d9d1fe996094830bd4e91ea3b3632e7
+#: ../../networking/external_firewalls_and_load_balancers.rst:484
+msgid "|autoscaleateconfig.png|"
+msgstr "|autoscaleateconfig.png|"
+
+# 4fc1aed8f2864acba56525d8509dfc38
+#: ../../networking/external_firewalls_and_load_balancers.rst:486
+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 "**模板**: 模板由基本的操作系统镜像和应用组成。在自缩放动作中，模板用来提供一个应用的新的实例。当从模板部署虚拟机时，虚拟机在管理员不干预的情形下开始从负载均衡器那里接管流量。例如，如果虚拟机部署为WEB服务应用，则虚拟机上的WEB服务器应该在运行，并且连接了数据库，等等。"
+
+# 15493a90f6c04d51a80a4caaa5a833c5
+#: ../../networking/external_firewalls_and_load_balancers.rst:494
+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 "**计算方案**: 一个预定义的虚拟硬件资源集，包括CPU速度，CPU数量，RAM，用户在创建虚拟时可以选择这些。选择一个计算方案作为提供虚拟机实例中自缩放行为的一部分。"
+
+# 55397884cbb84b2cb778668b2f01bb7e
+#: ../../networking/external_firewalls_and_load_balancers.rst:500
+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 "**最小实例**: 指定给负载均衡规则活动的虚拟机实例的最小数量，活动的虚拟机实例是开启的应用实例，并服务于流量和负载均衡。这个参数确保负载均衡规则拥有至少一个配置的活动虚拟机实例，并且能够服务于流量。"
+
+# c33b18f0b309446eb974ca219945f004
+#: ../../networking/external_firewalls_and_load_balancers.rst:508
+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 active instance count breaches the Max"
+" instance value."
+msgstr "如果一个应用程序，比如SAP，它运行在一个VM实例上，但是VM因为某些原因宕机了，那么这个VM没有被算成是Min实例的一部分，并且如果这些活动的VM实例是下面配置的数值，那么自动扩展功能启动一个扩展的动作。同样的，当应用程序实例从宕机的状态恢复了以后，这个应用程序实例会被算为活动实例计数的一部分，并且当活动实例计数超出Max实例数值的时候，自动扩展启动一个缩减动作。"
+
+# f040e7755d074bee8817ada9261b421b
+#: ../../networking/external_firewalls_and_load_balancers.rst:518
+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 "**最大实例数**：最大数量的**应该被指派到**\\ 一条负载均衡策略的活动VM实例。这个参数定义了能被指派到一条负载均衡策略的活动VM实例的上限。"
+
+# 2115dadd36d541558713322993492848
+#: ../../networking/external_firewalls_and_load_balancers.rst:523
+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 "给最大量实例参数指定一个大的值可能引发大量VM实例的分发，这个过程会导致一个负载均衡策略耗尽账户或者域级别下VM实例指定的限制。"
+
+# 40a5c798ef9d4d7584efa6400c0edfac
+#: ../../networking/external_firewalls_and_load_balancers.rst:529
+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 "如果一个应用程序，比如SAP，它运行在一个VM实例上，但是VM因为某些原因宕机了，那么这个VM没有被算成是Max实例的一部分。所以这个情况中为扩展动作分发的VMs数量可能会超过配置的MAX实例数值。一旦这个VMs中的应用程序实例从先前的宕机中恢复的时候，自动扩展功能就会校正Max实例的数值。"
+
+# 19812fc19c6a4a7d9ebc51b8e0ecb75b
+#: ../../networking/external_firewalls_and_load_balancers.rst:537
+msgid "Specify the following scale-up and scale-down policies:"
+msgstr "指定下列扩展和缩减的策略："
+
+# 74891b0d3cfd491f863a6557f788d493
+#: ../../networking/external_firewalls_and_load_balancers.rst:539
+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 "**持续**：持续，以秒为单位，你必须指定条件为true以触发一个扩展动作。这个条件定义的是为了触发一个自动扩展动作，你指定的全部持续值应保持为true。"
+
+# 436acb44653a45cc9c54ff9c950b7a56
+#: ../../networking/external_firewalls_and_load_balancers.rst:544
+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 "**计数器**：性能计数器直接体现了被监视实例的状态。默认情况下，CloudStack提供了4个性能计数器：3个SNMP计数器和1个NetScaler计数器。SNMP计数器是Linux User CPU、Linux System CPU和Linux CPU Idle。NetScaler计数器是ResponseTime。root管理员能够使用CloudStack API给CloudStack添加额外的计数器。"
+
+# 2137176110684b2db672902ab582654c
+#: ../../networking/external_firewalls_and_load_balancers.rst:551
+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 "**运算符**：自动扩展功能支持下列5种关系型运算符：大于、小于、小于或等于、大于或等于和等于。"
+
+# fce26387204d4e949d43cee1c917b9c0
+#: ../../networking/external_firewalls_and_load_balancers.rst:555
+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 "**阈值**：阈值用于计数器。一旦上面计数器中定义的值超出阈值，自动扩展功能会启动扩展或者缩减动作。"
+
+# f9e47cc9e3ad4739a2e6ef1470a50570
+#: ../../networking/external_firewalls_and_load_balancers.rst:559
+msgid "**Add**: Click Add to add the condition."
+msgstr "**添加**:：点击添加来添加条件。"
+
+# 3ea8d8738fdd408fb23e11b899d7b418
+#: ../../networking/external_firewalls_and_load_balancers.rst:561
+msgid ""
+"Additionally, if you want to configure the advanced settings, click Show "
+"advanced settings, and specify the following:"
+msgstr "另外，如果你想配置高级设置，点击显示高级设置，接着指定下列参数："
+
+# 9fafd8d4c0614661af2bc64d9c06879e
+#: ../../networking/external_firewalls_and_load_balancers.rst:564
+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 "**轮询间隔**：组合计数器，运算和阈值这几个条件的频率在触发扩展和缩减动作之前都要被评估。默认的轮询间隔是30秒。"
+
+# c719d597315640dc81a33fab44ae0a0e
+#: ../../networking/external_firewalls_and_load_balancers.rst:569
+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 "**平静期**：这是自动扩展动作被触发之后的冷静期。这个时间包括完成从模板分发一个VM实例的时间和一个应用程序准备好提供服务的时间。平静期允许机群在发生任何动作之前进入稳定状态。默认值是300秒。"
+
+# 98b814f48ff24f0c9ed3bca9f2dd1619
+#: ../../networking/external_firewalls_and_load_balancers.rst:576
+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 "**VM销毁宽限期**：此宽限期以秒计算，在一个缩减动作运行之后，在VMs被视为缩减动作的一部分从而销毁之前的等待时间。它保证了能够彻底关闭任何服务于被标记为销毁的VM的挂起中的进程或者事务。默认值是120秒。"
+
+# bcae2f20091343669f94311a955eb918
+#: ../../networking/external_firewalls_and_load_balancers.rst:582
+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 "**安全组**：安全组提供一种方法来隔离VMs流量。一个安全组是一组依照设置名为入口规则和出口规则来过滤他们进出流量的VMs，这些规则依靠与VM通讯的IP地址来过滤网络流量。"
+
+# 24e7476382c24a7a8bdb85ceef987fcb
+#: ../../networking/external_firewalls_and_load_balancers.rst:589
+msgid ""
+"**Disk Offerings**: A predefined set of disk size for primary data storage."
+msgstr "**磁盘方案**：一组预定义的主数据存储磁盘大小。"
+
+# 8b28accd4fce47b6afc47f2341e26d5d
+#: ../../networking/external_firewalls_and_load_balancers.rst:592
+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 "**SNMP 联系**：SNMP 联系字符串被用于NetScaler设备从分发的VM实例中查询已配置的计数器的值。默认是public。"
+
+# e01443d94f864a8e80ec211f1a96c910
+#: ../../networking/external_firewalls_and_load_balancers.rst:596
+msgid ""
+"**SNMP Port**: The port number on which the SNMP agent that run on the "
+"provisioned VMs is listening. Default port is 161."
+msgstr "**SNMP端口**：运行在已分发的VMs上的SNMP代理端口号。默认的端口是161."
+
+# 64c6d2f9ae6f4ac3b09f31d6fb0e360c
+#: ../../networking/external_firewalls_and_load_balancers.rst:599
+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 "**用户**：在云中NetScaler设备中用于发起扩展和缩减API调用的用户。如果没有指定选项，那么该用户被配置为自动扩展。指定其他用户名可以覆盖此配置。"
+
+# 062c87f44c6f4c92916dae1a85b891cc
+#: ../../networking/external_firewalls_and_load_balancers.rst:604
+msgid "**Apply**: Click Apply to create the AutoScale configuration."
+msgstr "**应用**：点击应用创建自动扩展配置。"
+
+# 6563ec698c3d499ab5e8e86cb3073ff0
+#: ../../networking/external_firewalls_and_load_balancers.rst:608
+msgid "Disabling and Enabling an AutoScale Configuration"
+msgstr "禁止和启用自动扩展配置"
+
+# e1b4da3ad2534f6c8fba4e5ec4616af2
+#: ../../networking/external_firewalls_and_load_balancers.rst:610
+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 "如果你想对一个自动扩展VM实例执行任何维护操作，请禁用自动扩展配置。当自动扩展配置被禁用，扩展和缩减动作不会执行。你可以利用停机时间进行维护活动。要禁用自动扩展配置，点击禁用自动扩展按钮 |EnableDisable.png|。"
+
+# eb31769bc729463bbdd6b8d9bd472847
+#: ../../networking/external_firewalls_and_load_balancers.rst:616
+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 "这个按钮是启用和禁止的切换开关，取决于当前是否启用了自动扩展。在执行完维护操作以后，你可以启用回自动扩展配置。要启用，请再次打开自动扩展配置页面，然后点击启用自动扩展按钮|EnableDisable.png|。"
+
+# 800c645e10c34f3b96d364a7e7b44570
+#: ../../networking/external_firewalls_and_load_balancers.rst:626
+msgid "Updating an AutoScale Configuration"
+msgstr "更新自动扩展配置"
+
+# 35012a4fdbe84c63a612c99f0ba31d1b
+#: ../../networking/external_firewalls_and_load_balancers.rst:628
+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 "你可以更新各种参数和添加或者删除扩展或缩减策略中的条件。在你更新自动扩展配置之前，请确保你已经通过点击禁止自动扩展按钮禁止了自动扩展负载均衡策略。"
+
+# b87ea7a2a6c5474392ec23163db4cadb
+#: ../../networking/external_firewalls_and_load_balancers.rst:633
+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 "在你修改了所需的自动扩展参数之后，点击应用。要应新的自动扩展策略，再次打开自动扩展配置页面，然后点击启用自动扩展按钮。"
+
+# 4b66b8ccf0284d27afeafec62196c28b
+#: ../../networking/external_firewalls_and_load_balancers.rst:639
+msgid "Runtime Considerations"
+msgstr "运行时注意事项"
+
+# c38f40d156554c08a840a51d5bc01d89
+#: ../../networking/external_firewalls_and_load_balancers.rst:641
+msgid ""
+"An administrator should not assign a VM to a load balancing rule which is "
+"configured for AutoScale."
+msgstr "管理员不应该分配VM到配置为AutoScale的负载均衡规则中。"
+
+# dee362b009924ebea8ca92bdd9f61f8d
+#: ../../networking/external_firewalls_and_load_balancers.rst:644
+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 "在分配虚拟机到一个负载均衡的规则配置完成前如果NetScaler被关闭或重启，则配置的虚拟机不能成为负载均衡规则的一部分。要解决此问题，重命名基于AutoScale配置的虚拟机名称或ID，以便在任何时间点负载平衡规则可以调节该虚拟机。"
+
+# 68fd9fba22874c88aeee1a1e17da457f
+#: ../../networking/external_firewalls_and_load_balancers.rst:651
+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 "在自动扩展上下文之外使用API调用，如destroyVM，那么自动扩展下的VM会处于负载均衡配置冲突状态中。虽然VM被负载均衡策略所销毁，但NetScaler仍然会把VM作为一个设备分配一条策略。"
+
+# 25734f8479cd4aeaa96bc94c9e97b3f0
+#: ../../networking/global_server_load_balancing.rst:18
+msgid "Global Server Load Balancing Support"
+msgstr "全局服务器负载均衡 支持"
+
+# 4281e272ec6741e89ba2c668c2b466e9
+#: ../../networking/global_server_load_balancing.rst:20
+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 "CLOUDSTACK支持全局服务器负载均衡 (GSLB) 功能以提供可持续的商业运营。GSLB可以在CLOUDSTACK环境中实现资源的无缝迁移。CLOUDSTACK通过集成NetScaler应用交付控制器 (ADC)来提供GSLB功能，ADC可以提供各种各样的GSLB能力，比如灾难恢复，负载均衡。CLOUDSTACK在实现GSLB功能进，使用了DNS重定向技术。"
+
+# 6945e2d89c9d4d758cba8b0168f0b818
+#: ../../networking/global_server_load_balancing.rst:28
+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 "为了支持这个功能，引进了地域级别的服务和服务提供者。引进了一项新服务“GSLB”作为地域级别的服务。该GSLB服务提供者介绍将提供GSLB服务。目前，CloudStack中NetScaler可作为GSLB提供者。 GSLB功能工作在Active-Active数据中心环境。"
+
+# e5df28b9850c419293fdae6e4e253ab5
+#: ../../networking/global_server_load_balancing.rst:37
+msgid "About Global Server Load Balancing"
+msgstr "关于全局服务器负载均衡"
+
+# 0b8dcd5aa2ba4b9984c94850cd1c44a9
+#: ../../networking/global_server_load_balancing.rst:39
+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 accessing a resource in the event of a "
+"failure, or to provide a means of shifting traffic easily to simplify "
+"maintenance, or both."
+msgstr "全局服务器负载均衡(GSLB)是负载均衡功能的扩展，为了高效的避免停机时间。基于部署的性质，GSLB代表一组技术的集合，用于各种用途，如负载均衡，灾难恢复，性能，和法定义务。使用GSLB，工作负载可以分布在位于不同地理位置的多个数据中心。 GSLB也可以用于在发生故障时访问资源的另一个备用位置，或对流量提供了简易的维护方式，或两者兼得。"
+
+# ab0467a3e9d24e78b8e9e16d225ce4b3
+#: ../../networking/global_server_load_balancing.rst:51
+msgid "Components of GSLB"
+msgstr "GSLB服务组件"
+
+# f131bfe486894f13961e91b6409ae286
+#: ../../networking/global_server_load_balancing.rst:53
+msgid "A typical GSLB environment is comprised of the following components:"
+msgstr "一个典型的GSLB环境由以下服务组件组成："
+
+# 6bc81bb78e4c4bd9974edba31c58d4cf
+#: ../../networking/global_server_load_balancing.rst:55
+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 "**GSLB站点**：在CloudStack专业术语中，GSLB站点表现为映射至数据中心的zones，每个GSLB有多个网络设备。每个GSLB站点由一个位于站点中的NetScaler设备管理。每个NetScaler设备将他管理的站点视为本地站点，并且由其他NetScaler设备管理的站点视为远程站点。在GSLB部署中它是一个中央实体，具体表现为一个名称和一个IP地址。"
+
+# ed55296b3210425390ee6cb680b0f347
+#: ../../networking/global_server_load_balancing.rst:63
+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 "**GSLB服务**：GSLB服务表现为典型的负载均衡或者内容交换虚拟服务器。在一个GSLB环境中，你可以有本地及远程GSLB服务。本地GSLB服务表现为一个本地负载均衡或者内容交换虚拟服务器。远程GSLB服务是配置在GSLB设置中的其他站点。在每个站点中的GSLB设置里，你可以创建一个本地GSLB服务和任意数量的远程GSLB服务。"
+
+# f00eb1ec7b75437699e4603066de4f63
+#: ../../networking/global_server_load_balancing.rst:72
+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 a FQDN DNS name."
+msgstr "**GSLB虚拟服务器**：GSLB虚拟服务器指的是一个或多个GSLB服务和平衡跨越多个使用CloudStack功能的zones之间VMs的流量。它通过评估配置的GSLB方法或者算法来选择一个GSLB服务发送客户端请求。来自不同zone的一个或多个虚拟服务器被绑定到GSLB虚拟服务器上。GSLB虚拟服务器没有对应的公共IP，只有一个FQDN DNS名称。"
+
+# ca80f04e2c8542269d92af6e7de92d03
+#: ../../networking/global_server_load_balancing.rst:81
+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 balancing or content switching virtual "
+"server, the client sends the request to that virtual server's VIP address."
+msgstr "**负载均衡或内容交换虚拟服务器**：依照Citrix NetScaler的专业术语，一个负载均衡或者内容交换虚拟服务器表现为本地网络上的一个或多个服务器。客户端发送他们的请求至负载均衡或内容交换虚拟服务器IP(VIP)地址，并且由虚拟服务器平衡本地服务器之间的负载。在GSLB虚拟服务器选择了一个基于本地或者远程负载均衡或者内容交换虚拟服务器的GSLB服务之后，客户端发送请求至虚拟服务器的VIP地址。"
+
+# d008156342444851b79a1c914ff2dbcb
+#: ../../networking/global_server_load_balancing.rst:91
+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 "**DNS VIPs**：DNS虚拟IP是一个在GSLB服务供应者上的DNS负载均衡虚拟服务器。在有GSLB服务提供者的域中的DNS请求会被发送至一个DNS VIP。"
+
+# 71d33e18670d4b49a2881ebc9a6de115
+#: ../../networking/global_server_load_balancing.rst:96
+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 and port."
+msgstr "**权威DNS**：ADNS(权威域名称服务器)是一个为DNS请求提供真实响应的服务，比如web站点IP地址。在GSLB环境中，一个ADNS服务只响应权威的GSLB服务提供者所在域的DNS请求。当配置了一个ADNS服务，该服务的提供者即拥有该服务IP并且广播它。当你创建一个ADNS服务的时候，NetScaler通过配置的ADNS服务IP和端口响应DNS请求。"
+
+# 0a4b19e96b7140af83a35ab77bc744af
+#: ../../networking/global_server_load_balancing.rst:107
+msgid "How Does GSLB Works in CloudStack?"
+msgstr "在CloudStack中，GSLB的工作原理是什么？"
+
+# 3fcf9c5675d647d09f1b6df17ad60cc1
+#: ../../networking/global_server_load_balancing.rst:109
+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 xyztelco cloud. For that purpose, they "
+"launch two instances each in both the zones: VM1 and VM2 in Zone-1 and VM5 "
+"and VM6 in Zone-2. Tenant-A acquires a public IP, IP-1 in Zone-1, and "
+"configures a load balancer rule to load balance the traffic between VM1 and "
+"VM2 instances. CloudStack orchestrates setting up a virtual server on the LB"
+" service provider in Zone-1. Virtual server 1 that is set up on the LB "
+"service provider in Zone-1 represents a publicly accessible virtual server "
+"that client reaches at IP-1. The client traffic to virtual server 1 at IP-1 "
+"will be load balanced across VM1 and VM2 instances."
+msgstr "全局服务器负载均衡-GSLB-用于在不同地域的不同独立区域之间管理WEB服务器的访问流量。以下是CLOUDSTACK中提供的GSLB功能图示：EXZTELCO这个组织用CLOUDSTACK在不同的数据中心部署一个公有云，此云环境包括两个区域，Zone-1 和Zone-2。XYZTELCO里有租户A需要部署一个高可用方案。为了达到此目标，他们分别在两个区域里部署了两个虚拟机实例：Zone-1中有VM1和VM2，Zone-2中有VM5和VM6。租户A在Zone-1中得到一个公网IP-IP-1，并且在VM1和VM2之间配置了负载均衡规则。CLOUDSTACK 编排系统在 Zone-1中LB服务上设置了一个虚拟服务器-Virtual server 1 。客户端对-IP-1的访问会到达Virtual server 1，此虚拟服务器再将流量转发到VM1和VM2上进行流量负载均衡。"
+
+# 16209a7b07e746f19adc6902ea420f50
+#: ../../networking/global_server_load_balancing.rst:126
+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 instances. At this point Tenant-A "
+"has the service enabled in both the zones, but has no means to set up a "
+"disaster recovery plan if one of the zone fails. Additionally, there is no "
+"way for Tenant-A to load balance the traffic intelligently to one of the "
+"zones based on load, proximity and so on. The cloud administrator of "
+"xyztelco provisions a GSLB service provider to both the zones. A GSLB "
+"provider is typically an ADC that has the ability to act as an ADNS "
+"(Authoritative Domain Name Server) and has the mechanism to monitor health "
+"of virtual servers both at local and remote sites. The cloud admin enables "
+"GSLB as a service to the tenants that use zones 1 and 2."
+msgstr "租户A在Zone-2中得到一个公网IP-IP-2，并且在VM5和VM6之间配置了负载均衡规则。CLOUDSTACK 编排系统在 Zone-2中LB服务上设置了一个虚拟服务器-Virtual server 2 。客户端对-IP-2的访问会到达Virtual server 2，此虚拟服务器再将流量转发到VM5和VM6上进行流量负载均衡。此时，租户A在两个区域里都启用了服务，但是，无法在这种环境下部署灾难恢复计划，也无法更智能在区域内使用负载均衡。要解决这些问题，XYZTELCO云管理员可以在两个区域内启用GSLB服务，一个GSLB服务通常是一个具有ADNS(认证域名服务器)能力的ADC，并且具有监测本地和远程站点健康状况的手段。云管理员可以在ZONE 1和2中为租户启用GSLB服务。"
+
+# d073e26f378940f9b2b7bacfdc8d7e0a
+#: ../../networking/global_server_load_balancing.rst:144
+msgid "|gslb.png|"
+msgstr "|gslb.png|"
+
+# 78fe59c21fad44febb867459cdd3c4fc
+#: ../../networking/global_server_load_balancing.rst:146
+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 start monitoring the health of "
+"virtual server 1 and 2 in Zone-1. CloudStack will also orchestrate setting "
+"up GSLB virtual server 2 on GSLB service provider at Zone-2. CloudStack will"
+" bind virtual server 1 of Zone-1 and virtual server 2 of Zone-2 to GLSB "
+"virtual server 2. GSLB virtual server 2 is configured to start monitoring "
+"the health of virtual server 1 and 2. CloudStack will bind the domain "
+"A.xyztelco.com to both the GSLB virtual server 1 and 2. At this point, "
+"Tenant-A service will be globally reachable at A.xyztelco.com. The private "
+"DNS server for the domain xyztelcom.com is configured by the admin out-of-"
+"band to resolve the domain A.xyztelco.com to the GSLB providers at both the "
+"zones, which are configured as ADNS for the domain A.xyztelco.com. A client "
+"when sends a DNS request to resolve A.xyztelcom.com, will eventually get DNS"
+" delegation to the address of GSLB providers at zone 1 and 2. A client DNS "
+"request will be received by the GSLB provider. The GSLB provider, depending "
+"on the domain for which it needs to resolve, will pick up the GSLB virtual "
+"server associated with the domain. Depending on the health of the virtual "
+"servers being load balanced, DNS request for the domain will be resolved to "
+"the public IP associated with the selected virtual server."
+msgstr "租户- A希望利用由xyztelco cloud提供的GSLB服务。租户-A配置了一个GSLB规则对Zone-1中的虚拟服务器1和Zone-2中的虚拟服务器2提供流量负载均衡。假设域名是A.xyztelco.com 。CloudStack中协调设置GSLB服务提供者Zone-1中的GSLB虚拟服务器1。 CloudStack绑定Zone-1中的虚拟服务器1和Zone-2中的虚拟服务器2到GSLB虚拟服务器1。CloudStack也将协调设置GSLB服务提供者Zone-2中的GSLB虚拟服务器2.CloudStack绑定Zone-1中的虚拟服务器1和Zone-2中的虚拟服务器2到GSLB虚拟服务器2.GSLB虚拟服务器2配置为开始监视虚拟服务器1和2的健康。CloudStack中会绑定域名A.xyztelco.com到GSLB虚拟服务器1和2。在这一点上，租户-A的服务将在全球范围内可达于A.xyztelco.com。域名xyztelcom.com的专用DNS服务器，被管理员配置为外带管理，由两个区域的GSLB提供者对域名A.xyztelco.com提供解析。它将被配置为域名A.xyztelco.com的ADNS。当客户端请求解析A.xyztelcom.com域名时，将最终由DNS指派到GSLB提供者Zone 1 和Zone2。客户DNS请求将被GSLB提供者接获。GSLB提供者，根据需要解析的域名，将获得与域名关联的GSLB虚拟服务器。根据用于负载均衡的虚拟服务器的运行健康状况，域名DNS请求将被解析到所选择关联的虚拟服务器中。"
+
+# ec2c5b7b09154785b795d77e01eadd4d
+#: ../../networking/global_server_load_balancing.rst:175
+msgid "Configuring GSLB"
+msgstr "配置GSLB"
+
+# 9df6a592e23d49148060b5c6ca5e52ac
+#: ../../networking/global_server_load_balancing.rst:177
+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 servers. Finally, bind the domain to "
+"the GSLB virtual servers. The GSLB configurations on the two appliances at "
+"the two different zones are identical, although each sites load-balancing "
+"configuration is specific to that site."
+msgstr "要配置GSLB的部署，您必须首先为每个区域配置一个标准的负载平衡设置。这使您能够在该地域中每个区域的不同服务器之间进行负载均衡。然后在NetScaler方面，配置您计划添加到每个区域作为权威DNS(ADNS)服务器的两个NetScaler应用。接下来，为每个区域创建GSLB站点、配置GSLB虚拟服务器、创建GSLB服务并绑定GSLB服务到GSLB虚拟服务器中。最后，绑定该域到GSLB虚拟服务器。两个应用的GSLB配置在两个不同区域中是完全相同的，尽管每个网站的负载均衡配置特定于该网站。"
+
+# ea099698d96f40f7adcc38a2fc9c997d
+#: ../../networking/global_server_load_balancing.rst:189
+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 "作为云管理员执行以下操作。按照上面给出的例子中，由管理员xyztelco设置GSLB："
+
+# ac5abddeadb048d794cccae84c2689cb
+#: ../../networking/global_server_load_balancing.rst:192
+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 "在全局变量 cloud.dns.name中，为您租户云定义DNS名称并供GSLB服务使用。"
+
+# 628b54626394479caf7ea8d6fd8d3210
+#: ../../networking/global_server_load_balancing.rst:195
+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 "在NetScaler方面，给出GSLB配置 `配置全局服务器负载均衡 (GSLB)<http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-con.html>`_:"
+
+# 4ae673b1b0a741d4a8ae715022d39bfc
+#: ../../networking/global_server_load_balancing.rst:199
+msgid "Configuring a standard load balancing setup."
+msgstr "配置一个标准的负载均衡设置。"
+
+# a3e3a1d93b6a48128aea3a0dee30c2ce
+#: ../../networking/global_server_load_balancing.rst:201
+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 "配置权威DNS，如下解释 `配置权威的DNS服务 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-adns-svc-tsk.html>`__."
+
+# 1bbbaf3fabe54fa8bd1f12d3cf85553d
+#: ../../networking/global_server_load_balancing.rst:205
+msgid ""
+"Configure a GSLB site with site name formed from the domain name details."
+msgstr "由域名详细信息配置一个GSLB站点和站点名称。"
+
+# 9bbfadb6046f4a089e701c8968231bf1
+#: ../../networking/global_server_load_balancing.rst:208
+msgid "Configure a GSLB site with the site name formed from the domain name."
+msgstr "由域名配置一个GSLB站点和站点名称。"
+
+# 5c91f57c9b0a4c1b81467b113da3b368
+#: ../../networking/global_server_load_balancing.rst:211
+msgid ""
+"As per the example given above, the site names are A.xyztelco.com and "
+"B.xyztelco.com."
+msgstr "按照上面给出的例子，站点名称为 A.xyztelco.com 和 B.xyztelco.com"
+
+# cf4285866ee549228e56d7a5b5423e75
+#: ../../networking/global_server_load_balancing.rst:214
+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 "更多信息，请参阅 `配置基本的GSLB站点 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-basic-site-tsk.html>`__."
+
+# 665433a1ecba490ca6d1a6f594d8d15d
+#: ../../networking/global_server_load_balancing.rst:217
+msgid "Configure a GSLB virtual server."
+msgstr "配置GSLB虚拟服务器。"
+
+# 62a5af1b8ba947619f77fffcc044737e
+#: ../../networking/global_server_load_balancing.rst:219
+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 "更多信息，请参阅 `配置GSLB虚拟服务器 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-vsvr-tsk.html>`__."
+
+# b5348156d5684555bf4a16f7b0aed2e1
+#: ../../networking/global_server_load_balancing.rst:222
+msgid "Configure a GSLB service for each virtual server."
+msgstr "为每个虚拟服务器配置GSLB服务。"
+
+# 1be7e75accb342118f2db621053cd0ca
+#: ../../networking/global_server_load_balancing.rst:224
+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 "更多信息，请参阅 `配置GSLB服务 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-svc-tsk.html>`__."
+
+# a057f57840c249baa28d0ea92fb18a4d
+#: ../../networking/global_server_load_balancing.rst:227
+msgid "Bind the GSLB services to the GSLB virtual server."
+msgstr "绑定GSLB服务到GSLB虚拟服务器。"
+
+# 54fde0c1b28d4b218b1b38fd69512fc7
+#: ../../networking/global_server_load_balancing.rst:229
+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 "更多信息，请参阅 `绑定GSLB服务到GSLB虚拟服务器 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-bind-svc-vsvr-tsk.html>`__."
+
+# b238ffa658954d6bb8950514feb4309e
+#: ../../networking/global_server_load_balancing.rst:232
+msgid ""
+"Bind domain name to GSLB virtual server. Domain name is obtained from the "
+"domain details."
+msgstr "绑定GSLB域名到GSLB虚拟服务器。从域的详细信息中获得域名。"
+
+# ddb89d80e86542fca93e99d812871a42
+#: ../../networking/global_server_load_balancing.rst:235
+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 "更多信息，请参阅 `绑定GSLB域名到GSLB虚拟服务器 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-bind-dom-vsvr-tsk.html>`__."
+
+# 994ecce5579142d68bbcabc7fbbcee66
+#: ../../networking/global_server_load_balancing.rst:238
+msgid ""
+"In each zone that are participating in GSLB, add GSLB-enabled NetScaler "
+"device."
+msgstr "在每个参与GSLB的区域内，添加启用GSLB功能的NetScaler设备。"
+
+# 77a9ecb28f3c42fa871ca4293f5fb3c2
+#: ../../networking/global_server_load_balancing.rst:241
+msgid "For more information, see :ref:`enabling-gslb-in-ns`."
+msgstr "更多信息请参考 :ref:`enabling-gslb-in-ns`."
+
+# 9d1700ef75be4986a54fd1e51b7daf09
+#: ../../networking/global_server_load_balancing.rst:243
+msgid "As a domain administrator/ user perform the following:"
+msgstr "以域管理员/用户执行以下操作："
+
+# 1b28e385ddd9459f934219e64252f08a
+#: ../../networking/global_server_load_balancing.rst:245
+msgid "Add a GSLB rule on both the sites."
+msgstr "在两个站点中添加GSLB规则。"
+
+# b3f6d2228fdd4f249692765a44df3257
+#: ../../networking/global_server_load_balancing.rst:247
+msgid "See \":ref:`adding-gslb-rule`\"."
+msgstr "参考\":ref:`adding-gslb-rule`\"."
+
+# d4539ca63ba143f5a57e95a7cc50c138
+#: ../../networking/global_server_load_balancing.rst:249
+msgid "Assign load balancer rules."
+msgstr "分配负载均衡规则。"
+
+# 5e832683ca534485b0fbd672a249e511
+#: ../../networking/global_server_load_balancing.rst:251
+msgid "See \":ref:`assigning-lb-rule-gslb`\"."
+msgstr "参考\":ref:`assigning-lb-rule-gslb`\"."
+
+# 9fd9a67186904ceda46fa7d9e61e6dce
+#: ../../networking/global_server_load_balancing.rst:257
+msgid "The GSLB functionality is supported both Basic and Advanced zones."
+msgstr "GSLB功能支持基本和高级区域。"
+
+# 155a1b915c7840afae25327ef3a7f6bb
+#: ../../networking/global_server_load_balancing.rst:259
+msgid "GSLB is added as a new network service."
+msgstr "GSLB是新添加的网络服务。"
+
+# b5681032556f4430a86b311f53d393c5
+#: ../../networking/global_server_load_balancing.rst:261
+msgid "GSLB service provider can be added to a physical network in a zone."
+msgstr "GSLB服务提供者可以被添加至区域中的物理网络。"
+
+# ba83a0e977bc4a3abc65c3f30c4684d4
+#: ../../networking/global_server_load_balancing.rst:263
+msgid ""
+"The admin is allowed to enable or disable GSLB functionality at region "
+"level."
+msgstr "管理员允许开启或禁用地域级别的GSLB功能。"
+
+# 682239c65afe4c2fa7312feeac21e9bf
+#: ../../networking/global_server_load_balancing.rst:266
+msgid "The admin is allowed to configure a zone as GSLB capable or enabled."
+msgstr "管理员具有启用或配置区域为GSLB的能力"
+
+# 16c808c16f1e4f22a5294f1060dfe2c3
+#: ../../networking/global_server_load_balancing.rst:268
+msgid ""
+"A zone shall be considered as GSLB capable only if a GSLB service provider "
+"is provisioned in the zone."
+msgstr "只有在GSLB服务提供者提供的区域中，该区域才被视为有GSLB能力。"
+
+# 54c1b30001084a9d88eb89799461dc9f
+#: ../../networking/global_server_load_balancing.rst:271
+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 "当用户的VMs部署在启用GSLB功能的多个可用区域中时，他们可以使用GSLB功能在多个区域中将VM的流量进行负载均衡。"
+
+# 04c2a492332c437daed8f4ef774ba016
+#: ../../networking/global_server_load_balancing.rst:275
+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 "如果管理员在地域中启用了GSLB，用户可以使用GSLB对地狱中的所有区域的VMs进行负载均衡。"
+
+# 1f9b8a3555524eaea6e144288b6f74a6
+#: ../../networking/global_server_load_balancing.rst:278
+msgid ""
+"The users can load balance traffic across the availability zones in the same"
+" region or different regions."
+msgstr "用户可以为同一个区域或不同地域间可用的区域流量进行负载均衡。"
+
+# 56f19e5d46de43f5b7e3ac6674a8084b
+#: ../../networking/global_server_load_balancing.rst:281
+msgid "The admin can configure DNS name for the entire cloud."
+msgstr "管理员可以为整个云配置DNS名称。"
+
+# 5d62e65b44ab487688e71984b4665f2b
+#: ../../networking/global_server_load_balancing.rst:283
+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 "用户可以为云中的全局负载均衡服务指定一个唯一的名称。所提供名称的域名相当于云的DNS名称。"
+
+# ed7a5577959a4271b7b98ac369d63874
+#: ../../networking/global_server_load_balancing.rst:287
+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 "用户提供的名称与管理员提供的DNS名称一起为用户的全局负载均衡服务产生一个全局解析的FQDN。例如，如果管理员已经配置xyztelco.com为云中的DNS名称，以及用户为GSLB虚拟服务器指定的名称为'foo'，那么GSLB虚拟服务器的FQDN名称是foo.xyztelco.com。"
+
+# 8cac76f1529943b5a001cc5e9e8978ac
+#: ../../networking/global_server_load_balancing.rst:294
+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 "设置GSLB时，用户可以为GSLB跨区域的一部分选择负载均衡方式，例如 round robin。"
+
+# d53da99edf45482fae37a6beabd277e0
+#: ../../networking/global_server_load_balancing.rst:297
+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 "用户应能设置区域级虚拟服务器的权重。负载均衡在分配流量时会考虑该权重。"
+
+# 7a49a6392b3841eea149e6bda34bf00a
+#: ../../networking/global_server_load_balancing.rst:301
+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 "该GSLB功能必须支持会话持久性，特定域名的一系列客户端请求被发送到同一个区域中的虚拟服务器上。"
+
+# bb4138b786e9474fb0ed35738608df60
+#: ../../networking/global_server_load_balancing.rst:305
+msgid "Statistics is collected from each GSLB virtual server."
+msgstr "从每个GSLB虚拟服务器中收集统计数据。"
+
+# 47055f92a29342529bfcdc61d569e7e5
+#: ../../networking/global_server_load_balancing.rst:311
+msgid "Enabling GSLB in NetScaler"
+msgstr "开启NetScaler的GSLB"
+
+# 993ee7e5933440be90a5d733c261dbfa
+#: ../../networking/global_server_load_balancing.rst:313
+msgid "In each zone, add GSLB-enabled NetScaler device for load balancing."
+msgstr "在每个区域中，添加启用GSLB的NetScaler设备提供负载均衡。"
+
+# 1ccc47562da1485ebadaf564a75a1e8f
+#: ../../networking/global_server_load_balancing.rst:315
+msgid "Log in as administrator to the CloudStack UI."
+msgstr "使用管理员登录到CloudStack管理界面。"
+
+# 50c53a288e5c4ba8a5873ae93ce2ebc1
+#: ../../networking/global_server_load_balancing.rst:319
+msgid "In Zones, click View More."
+msgstr "点击区域中的查看更多。"
+
+# 426b0fac04b243adae39f7591362417b
+#: ../../networking/global_server_load_balancing.rst:323
+msgid ""
+"Click the Physical Network tab, then click the name of the physical network."
+msgstr "点击物理网络选项卡，然后点击物理网络的名称。"
+
+# fafed439faa145cfbd6e0660489f0c23
+#: ../../networking/global_server_load_balancing.rst:326
+msgid "In the Network Service Providers node of the diagram, click Configure."
+msgstr "点击示意图'网络服务提供程序'中的配置"
+
+# fd8f072b359a4f04ad326eb3d908940d
+#: ../../networking/global_server_load_balancing.rst:329
+msgid "You might have to scroll down to see this."
+msgstr "你可能需要向下滚动才能看到。"
+
+# 4cb81ecc1e2041ac85015a942c236caf
+#: ../../networking/global_server_load_balancing.rst:331
+msgid "Click NetScaler."
+msgstr "点击NetScaler."
+
+# fd9c663d6f344362bc282938fa9a7568
+#: ../../networking/global_server_load_balancing.rst:333
+msgid "Click Add NetScaler device and provide the following:"
+msgstr "点击添加NetScaler设备并提供如下信息："
+
+# 482e597c23cc41b798a1610afce4cdeb
+#: ../../networking/global_server_load_balancing.rst:335
+msgid "For NetScaler:"
+msgstr "对于NetScaler:"
+
+# 3294458f8c544dd2b784f2fa14c2aa67
+#: ../../networking/global_server_load_balancing.rst:337
+msgid "**IP Address**: The IP address of the SDX."
+msgstr "**IP地址**: SDX的IP地址。"
+
+# b70b5b91f59c409c9dd3966293451a99
+#: ../../networking/global_server_load_balancing.rst:339
+msgid ""
+"**Username/Password**: The authentication credentials to access the device. "
+"CloudStack uses these credentials to access the device."
+msgstr "**用户名/密码.** 访问此设备的认证许可。CloudStack使用这些认证信息访问此设备。"
+
+# 8ef3b665ac154e6287ad6ea81148049c
+#: ../../networking/global_server_load_balancing.rst:343
+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 "**类型**：添加设备的类型。可以是F5 BigIP负载均衡器、NetScaler VPX、NetScaler MPX或 NetScaler SDX等设备。关于NetScaler的类型比较，请参阅CloudStack管理指南。"
+
+# 2e237e04e2dc44aa9a63e9b610481683
+#: ../../networking/global_server_load_balancing.rst:348
+msgid ""
+"**Public interface**: Interface of device that is configured to be part of "
+"the public network."
+msgstr "**公共接口**: 配置为公共网络部分的设备接口。"
+
+# 1768efdd0e38457882de8c3f6a4bc7ac
+#: ../../networking/global_server_load_balancing.rst:351
+msgid ""
+"**Private interface**: Interface of device that is configured to be part of "
+"the private network."
+msgstr "**专用接口**: 配置为专用网络部分的设备接口。"
+
+# d7a97e5326bf493ea8de67360056032f
+#: ../../networking/global_server_load_balancing.rst:354
+msgid "**GSLB service**: Select this option."
+msgstr "**GSLB 服务**:选择该选项。"
+
+# 3169f742f2b541cf9ba5e47685b71979
+#: ../../networking/global_server_load_balancing.rst:356
+msgid ""
+"**GSLB service Public IP**: The public IP address of the NAT translator for "
+"a GSLB service that is on a private network."
+msgstr "**GSLB 服务公共IP**:在专用网络中，为GSLB服务提供NAT转换的公共IP地址。"
+
+# 8aea303aff5746d887377f892f81bedb
+#: ../../networking/global_server_load_balancing.rst:359
+msgid "**GSLB service Private IP**: The private IP of the GSLB service."
+msgstr "**GSLB 服务专用IP**: GSLB服务的专用IP地址。"
+
+# 12ef6d7387b1493fbb70926187f28853
+#: ../../networking/global_server_load_balancing.rst:361
+msgid ""
+"**Number of Retries**. Number of times to attempt a command on the device "
+"before considering the operation failed. Default is 2."
+msgstr "**重试次数** 尝试控制设备失败时重试的次数，默认为2次。"
+
+# 66bbb327d60548f78a85f6f748811885
+#: ../../networking/global_server_load_balancing.rst:364
+msgid "**Capacity**: The number of networks the device can handle."
+msgstr "**容量**：该设备能处理的网络数量。"
+
+# d60d1dd86fb4433b99b28a0c96f1576a
+#: ../../networking/global_server_load_balancing.rst:366
+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 "**专用**: 当标记为专用后，这个设备只对单个帐号专用。该选项被勾选后，容量选项就没有了实际意义且值会被置为1。"
+
+# 69bd10926c1b4f639cc360e4c6418c3e
+#: ../../networking/global_server_load_balancing.rst:377
+msgid "Adding a GSLB Rule"
+msgstr "添加 GSLB规则"
+
+# d8d474dabeab4c1f8f00fa162277cd18
+# 2533afdf8c2f4af0ae6a8c0a349218af
+#: ../../networking/global_server_load_balancing.rst:379
+#: ../../networking/global_server_load_balancing.rst:423
+msgid "Log in to the CloudStack UI as a domain administrator or user."
+msgstr "使用管理员或者用户账号登录CloudStack UI。"
+
+# 7550ed528a27426c853c744100fd4ae1
+# a6856d0d96014ad4bcf0169664b844e3
+#: ../../networking/global_server_load_balancing.rst:381
+#: ../../networking/global_server_load_balancing.rst:425
+msgid "In the left navigation pane, click Region."
+msgstr "在左边的导航栏里，点击区域（为文档翻译中地域的概念，英文为region，下同）"
+
+# 5a1ef80e398e476bb8d0a513004669b9
+# 8f5b19bc2a244501b359c7b31af3d903
+#: ../../networking/global_server_load_balancing.rst:383
+#: ../../networking/global_server_load_balancing.rst:427
+msgid "Select the region for which you want to create a GSLB rule."
+msgstr "选择你想创建GSLB规则的地域。"
+
+# de6f8ae256d04834b07c2f957c2d329f
+# 14610babee3a4c4f98ccda032d8a1a24
+#: ../../networking/global_server_load_balancing.rst:385
+#: ../../networking/global_server_load_balancing.rst:429
+msgid "In the Details tab, click View GSLB."
+msgstr "在详细选项卡中，点击查看GSLB。"
+
+# 9c265b9b1d6f450fbb90a2dab4a3dd4d
+#: ../../networking/global_server_load_balancing.rst:387
+msgid "Click Add GSLB."
+msgstr "点击添加GSLB。"
+
+# 7b20c6e1ba68451d9c097b40cf182ed5
+#: ../../networking/global_server_load_balancing.rst:389
+msgid "The Add GSLB page is displayed as follows:"
+msgstr "添加GSLB页面显示如下："
+
+# 156298ad77934768a3936c310cb506c7
+#: ../../networking/global_server_load_balancing.rst:391
+msgid "|gslb-add.png|"
+msgstr "|gslb-add.png|"
+
+# 94ceaa226a6348128cee4e536b67def7
+#: ../../networking/global_server_load_balancing.rst:395
+msgid "**Name**: Name for the GSLB rule."
+msgstr "**名称**: GSLB规则的名称。"
+
+# 1bedbf6a59124f5ab5ad9ae9d676f428
+#: ../../networking/global_server_load_balancing.rst:397
+msgid ""
+"**Description**: (Optional) A short description of the GSLB rule that can be"
+" displayed to users."
+msgstr "**描述**: (可选)为用户提供一个简短的GSLB规则描述。 "
+
+# 760fed68b0f1425d813d3da44e010ef0
+#: ../../networking/global_server_load_balancing.rst:400
+msgid "**GSLB Domain Name**: A preferred domain name for the service."
+msgstr "**GSLB 域名**: 首选的域名服务。"
+
+# f10e909d63a847f2ac92ce505fbe7453
+#: ../../networking/global_server_load_balancing.rst:402
+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 "**算法**: (可选) 用于跨区域流量负载均衡的算法。可选项为 Round Robin, Least Connection, 和Proximity."
+
+# 5bd10eaef9ea49fdafb1aaf2a6d04f89
+#: ../../networking/global_server_load_balancing.rst:406
+msgid ""
+"**Service Type**: The transport protocol to use for GSLB. The options are "
+"TCP and UDP."
+msgstr "**服务类型**: GSLB使用的传输协议。可选项为TCP和UDP。"
+
+# 5a07001702fd46899b6363fe3e335dda
+#: ../../networking/global_server_load_balancing.rst:409
+msgid ""
+"**Domain**: (Optional) The domain for which you want to create the GSLB "
+"rule."
+msgstr "**域**: (可选) 你想要创建GSLB规则的域。"
+
+# f95e0967cf5b4586af07b8c278fa7f2c
+#: ../../networking/global_server_load_balancing.rst:412
+msgid ""
+"**Account**: (Optional) The account on which you want to apply the GSLB "
+"rule."
+msgstr "**账户**: (可选) 应用GSLB规则的账户。"
+
+# 8e6fff3aabfc4338a6d75cc7a0817e74
+#: ../../networking/global_server_load_balancing.rst:421
+msgid "Assigning Load Balancing Rules to GSLB"
+msgstr "为GSLB分配负载均衡规则"
+
+# c1a5b66d72da4e03acd469f7c6097117
+#: ../../networking/global_server_load_balancing.rst:431
+msgid "Select the desired GSLB."
+msgstr "选择所需的GSLB。"
+
+# 1a740350bc534faaaa40f53959d4fee9
+#: ../../networking/global_server_load_balancing.rst:433
+msgid "Click view assigned load balancing."
+msgstr "点击已分配的负载均衡视图。"
+
+# daff37ebdd2349a497dab10e0d234426
+#: ../../networking/global_server_load_balancing.rst:435
+msgid "Click assign more load balancing."
+msgstr "点击分配更多负载平衡"
+
+# d63a5166197e4a17b6bd9ab1cd618814
+#: ../../networking/global_server_load_balancing.rst:437
+msgid "Select the load balancing rule you have created for the zone."
+msgstr "选择你将为区域创建的负载均衡规则。"
+
+# 35f5b11c84c142c58580b76bb4ddadfd
+#: ../../networking/global_server_load_balancing.rst:443
+msgid "Known Limitation"
+msgstr "已知的局限性"
+
+# 89c2b07fa33e40838e9c4de58e3296be
+#: ../../networking/global_server_load_balancing.rst:445
+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 "目前，CloudStack并不支持跨区域的服务编排。将引入服务的概念和地域服务提供者。"
+
+# 43426b72e0e24e35a5898286a3dd3dc2
+#: ../../networking/guest_ip_ranges.rst:18
+msgid "Guest IP Ranges"
+msgstr "来宾IP范围"
+
+# 8ad2743b8f6d4eb1bf10b5afb1c89f54
+#: ../../networking/guest_ip_ranges.rst:20
+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 "宾客网络流量的IP是由用户以帐号为基础设置的。这允许用户以在他们的宾客网络和他们的客户端之间开通VPN连接的方式配置他们的网络。"
+
+# dc1be0f75ec04a468b17af4d2750b1ca
+#: ../../networking/guest_ip_ranges.rst:25
+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 "存在基本网络和启用安全组的高级网络中的共享网络，你可以灵活的在不同子网中添加多个来宾IP范围。你可以同时添加或移除IP范围。更多信息，请参阅 `章节 15.10, “关于多IP范围”<#about-multiple-ip-ranges>`_."
+
+# 5daf1c058a0c43718015e5812d9c0836
+#: ../../networking/acquiring_an_ip_address.rst:18
+msgid "Acquiring a New IP Address"
+msgstr "获得一个新的IP地址"
+
+# 32dbea4bf3a6422da3941f2407b12a71
+#: ../../networking/acquiring_an_ip_address.rst:34
+msgid ""
+"If you want Portable IP click Yes in the confirmation dialog. If you want a "
+"normal Public IP click No."
+msgstr "如果你想作为 Portable IP则在确认窗口中点击Yes，如果你想作为正常的公共IP则点击No。"
+
+# b8ffa6eff3794134bf11db68c7c32099
+#: ../../networking/acquiring_an_ip_address.rst:37
+msgid ""
+"For more information on Portable IP, see `\"Portable IPs\" <#portable-"
+"ips>`_."
+msgstr "关于便携式IP的更多信息，查看 `\"便携式IP\" <#portable-ips>`_."
+
+# d5be22795b3d4926be02f94cc069db79
+#: ../../networking/releasing_an_ip_address.rst:18
+msgid "Releasing an IP Address"
+msgstr "释放IP地址"
+
+# d608beb5fbb544afaaad161b9661dcb0
+#: ../../networking/releasing_an_ip_address.rst:20
+msgid ""
+"When the last rule for an IP address is removed, you can release that IP "
+"address. The IP address still belongs to the VPC; however, it can be picked "
+"up for any guest network again."
+msgstr "当IP的最后一条规则删除后，您就能够释放该IP。然而，该IP仍属于VPC，无论如何，该IP可以再次被VPC中的来宾网络再次获取。"
+
+# cbede7f4af98499c97ff53a446ca173d
+#: ../../networking/releasing_an_ip_address.rst:32
+msgid "Click the IP address you want to release."
+msgstr "点击要释放的IP地址。"
+
+# b5f7d64cc75b4ee18855fa6ad6f1438d
+#: ../../networking/releasing_an_ip_address.rst:34
+msgid "Click the Release IP button. |ReleaseIPButton.png|"
+msgstr "Click the Release IP button. |ReleaseIPButton.png|"
+
+# 6d82408293c1416ca310c302379aa09a
+# 2fb7e2316ee54739935361a2c3eaeeb3
+# e63c1fef73664de395b24f2fd3232139
+# a499d21cfffe4303bb3b23988d32ed53
+# 692e4e5ab7df4a7cbc791aa7fa428661
+# bd6701c2c7bb43c3b81bd5a810215d73
+# e357c811590c493c8341f10d87e99492
+# ad2e62635b524cfd95d4640c69979c8e
+# ba9cd4d358194f5bb69c7779b84c8c27
+# 24720c3dbfa6455a9c417b49062ebfd7
+# c7886284bd2c4db990aecc9f5d015a0c
+# b1144b4196da4257868a1599fb14431d
+#: ../../networking/static_nat.rst:18
+#: ../../networking/remote_access_vpn.rst:118
+#: ../../networking/remote_access_vpn.rst:452
+#: ../../networking/remote_access_vpn.rst:515
+#: ../../networking/remote_access_vpn.rst:647
+#: ../../networking/virtual_private_cloud_config.rst:348
+#: ../../networking/virtual_private_cloud_config.rst:515
+#: ../../networking/virtual_private_cloud_config.rst:750
+#: ../../networking/virtual_private_cloud_config.rst:808
+#: ../../networking/virtual_private_cloud_config.rst:869
+#: ../../networking/virtual_private_cloud_config.rst:1035
+#: ../../networking/virtual_private_cloud_config.rst:1303
+msgid "Static NAT"
+msgstr "静态 NAT"
+
+# 894073bd52434748977055e7ee9a6604
+#: ../../networking/static_nat.rst:20
+msgid ""
+"A static NAT rule maps a public IP address to the private IP address of a VM"
+" in order to allow Internet traffic into the VM. The public IP address "
+"always remains the same, which is why it is called static NAT. This section "
+"tells how to enable or disable static NAT for a particular IP address."
+msgstr ""
+
+# 3ce1cecac4bf48f6bc8b81b403d9e42b
+#: ../../networking/static_nat.rst:28
+msgid "Enabling or Disabling Static NAT"
+msgstr "启用或禁用静态NAT"
+
+# ca8d159797c4416288520787181cb2f5
+# 7732dac53f9c44c3884d468654271191
+#: ../../networking/static_nat.rst:30
+#: ../../networking/virtual_private_cloud_config.rst:842
+msgid ""
+"If port forwarding rules are already in effect for an IP address, you cannot"
+" enable static NAT to that IP."
+msgstr "如果该公网IP上已经有端口转发规则，则不允许再启用静态NAT。"
+
+# a931121d677f4d04b656aca83f043d26
+# c2bb747e18d64159bd3605ffa4f2f044
+#: ../../networking/static_nat.rst:33
+#: ../../networking/virtual_private_cloud_config.rst:845
+msgid ""
+"If a guest VM is part of more than one network, static NAT rules will "
+"function only if they are defined on the default network."
+msgstr "如果用户VM存在多个网络，则静态NAT规则仅在默认网络上定义时生效。"
+
+# 33a01340d067438a8dfaf19d33406d95
+# 39954d50f8bc407f84931182c3e7dd86
+#: ../../networking/static_nat.rst:44
+#: ../../networking/ip_forwarding_and_firewalling.rst:67
+msgid "Click the IP address you want to work with."
+msgstr "点击你要修改的IP地址"
+
+# a33212ef265c4bc68a9ed53a9c693df0
+#: ../../networking/static_nat.rst:46
+msgid "Click the Static NAT |enabledisablenat.png| button."
+msgstr "点击静态NAT按钮。 |enabledisablenat.png| "
+
+# c6c4c974f1b44a05823bc42e28095e76
+#: ../../networking/static_nat.rst:48
+msgid ""
+"The button toggles between Enable and Disable, depending on whether static "
+"NAT is currently enabled for the IP address."
+msgstr "该按钮在启用和禁用之间切换，这取决于IP地址是否已经启用了静态NAT。"
+
+# 0e003c10fb6b4b86a1c8fb0d260fb702
+#: ../../networking/static_nat.rst:51
+msgid ""
+"If you are enabling static NAT, a dialog appears where you can choose the "
+"destination VM and click Apply."
+msgstr "如果是启用静态NAT，会出现一个对话框让您选择目标VM然后点击应用。"
+
+# ab5d3e20a35044a490aa5251c4b85f4d
+#: ../../networking/ip_forwarding_and_firewalling.rst:18
+msgid "IP Forwarding and Firewalling"
+msgstr "IP转发及防火墙"
+
+# aee28d66b74c499597d47124ee883143
+#: ../../networking/ip_forwarding_and_firewalling.rst:20
+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 "默认情况下, 所有从公共IP进来的流量都会被拒绝. 所有在来宾网络出去的流量默认也被阻挡。"
+
+# 387c2271d56a4e12beb6624f511851c8
+#: ../../networking/ip_forwarding_and_firewalling.rst:23
+msgid ""
+"To allow outgoing traffic, follow the procedure in :ref:`egress-fw-rules`."
+msgstr "为了允许外出的流量，遵循:ref:`egress-fw-rules`中的操作步骤。"
+
+# 2e337162d6dd4714a9a6a2542e8a146e
+#: ../../networking/ip_forwarding_and_firewalling.rst:25
+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 "为了允许接收到的流量, 用户可以设置一些防火墙规则和/或端口转发规则. 例如, 你可以在公共IP地址上设定防火墙规则来打开一个端口范围, 比如从33到44端口. 然后使用端口转发将流量从这个特定的范围内的端口直接送到指定的用户虚机端口. 例如, 一个端口转发的规则可以将接收的流量从公共IP的33端口到用户虚机私有IP的100端口."
+
+# 3b46ec3be763405b94a219d0c00a44d9
+#: ../../networking/ip_forwarding_and_firewalling.rst:35
+msgid "Firewall Rules"
+msgstr "防火墙规则"
+
+# 289b2b9b80b942a7bd122ec6a45830a1
+#: ../../networking/ip_forwarding_and_firewalling.rst:37
+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 "默认情况下，防火墙拒绝所有流入公共IP的流量。要允许外部流量，你需要制定防火墙规则打开防火墙端口。你可以选择性的制定一个或多个CIDR来过滤来源IP。这在当你只需要允许特定IP请求时会很有用。"
+
+# aebb1c0165554e0eaf7198fa58bb0243
+#: ../../networking/ip_forwarding_and_firewalling.rst:43
+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 "你不能使用防火墙规则打开弹性IP的端口。当弹性IP处在使用状态时，外部的通过请求将被安全组管理。参阅 `\"添加安全组\" <#adding-a-security-group>`_."
+
+# a63a51dddfbc4821b71342f76ea15396
+#: ../../networking/ip_forwarding_and_firewalling.rst:48
+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 "在高级Zone中，您也可以用虚拟路由器来创建流出的防火墙规则。更多信息，请查阅\":ref:`egress-fw-rules`\"。"
+
+# 9cdd6b4c846447d8bf19cfb8b5b22829
+#: ../../networking/ip_forwarding_and_firewalling.rst:51
+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 "防火墙规则能在管理服务器的UI中防火墙选项卡里创建，CloudStac安装好以后，这个规则选项卡默认不显示，你需要以管理员身份修改全局变量 firewall.rule.ui.enabled为 \"true\"才能显示。"
+
+# 109ed3b0aad347d99e3cff3240722f30
+#: ../../networking/ip_forwarding_and_firewalling.rst:57
+msgid "To create a firewall rule:"
+msgstr "创建防火墙规则："
+
+# ec5934105a19458782c675dd18684173
+#: ../../networking/ip_forwarding_and_firewalling.rst:69
+msgid "Click the Configuration tab and fill in the following values."
+msgstr "点击设置选项卡 填入以下值："
+
+# 61cd332681ea4fccb7a69d35effdfbe0
+#: ../../networking/ip_forwarding_and_firewalling.rst:71
+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 ""
+
+# fbecf77ee36345b38502a02307d58865
+#: ../../networking/ip_forwarding_and_firewalling.rst:76
+msgid "**Protocol**: The communication protocol in use on the opened port(s)."
+msgstr ""
+
+# 87689392abf14a949afbc25ee0410466
+#: ../../networking/ip_forwarding_and_firewalling.rst:79
+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 ""
+
+# 9e4666af35d043358c3246ec14509b78
+#: ../../networking/ip_forwarding_and_firewalling.rst:83
+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 ""
+
+# c0ae5406014e43d4a50a05ed74aa8dc8
+#: ../../networking/ip_forwarding_and_firewalling.rst:94
+msgid "Egress Firewall Rules in an Advanced Zone"
+msgstr "高级区域中的出口防火墙规则"
+
+# bf3e32d6e33f4bb199a83e9ee2a6d307
+#: ../../networking/ip_forwarding_and_firewalling.rst:96
+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 rules are removed the default "
+"policy, Block, is applied."
+msgstr "出口流量起源于从专用网络访问公共网络，例如Internet。默认情况下，在默认网络方案中，出口流量被拒绝，所以没有从来宾网络到Internet的出口流量被允许。不过，你可以通过创建出口防火墙规则来控制高级网络中的出口流量。当出口防火墙规则被应用时，规则指定的流量被允许，其余的流量被阻止。当所有的防火墙规则从默认策略中移除，阻止策略再次被应用。"
+
+# bedc63fb7a3b4ba2ad3a4f4c4992b742
+#: ../../networking/ip_forwarding_and_firewalling.rst:109
+msgid "Consider the following scenarios to apply egress firewall rules:"
+msgstr "应用出口防火墙规则时请思考如下方案："
+
+# 20406d7e04b74d6d9adb04b039195d77
+#: ../../networking/ip_forwarding_and_firewalling.rst:111
+msgid "Egress firewall rules are supported on Juniper SRX and virtual router."
+msgstr "出口防火墙规则在Jniper SRX和虚拟路由器中均支持。"
+
+# 97a42a58db4c4505919b767f168001e8
+#: ../../networking/ip_forwarding_and_firewalling.rst:114
+msgid "The egress firewall rules are not supported on shared networks."
+msgstr "共享网络中不支持出口防火墙规则。"
+
+# 1bd785cd4def48be9265615471d02ced
+#: ../../networking/ip_forwarding_and_firewalling.rst:116
+msgid ""
+"Allow the egress traffic from specified source CIDR. The Source CIDR is part"
+" of guest network CIDR."
+msgstr "允许特定源CIDR的出口流量。源CIDR是来宾网络CIDR的一部分。"
+
+# ff0740d14f3f454395f0342767084065
+#: ../../networking/ip_forwarding_and_firewalling.rst:119
+msgid "Allow the egress traffic with protocol TCP,UDP,ICMP, or ALL."
+msgstr "允许出口流量的协议为TCP，UDP,ICMP或ALL。"
+
+# 3da424158d4a46fb955bad940049cfaf
+#: ../../networking/ip_forwarding_and_firewalling.rst:121
+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 "允许出口流量协议和目标端口范围。端口范围需要指定TCP，UDP或ICMP类型和代码。"
+
+# bfec00d70b32484abdd2be7a7067fb12
+#: ../../networking/ip_forwarding_and_firewalling.rst:124
+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 "新网络方案的默认策略是允许的，然而升级现有的网络方案后，防火墙服务提供商的出口策略默认将是拒绝。"
+
+# 77a21030af6444aaac365dc1d6c1a40e
+#: ../../networking/ip_forwarding_and_firewalling.rst:130
+msgid "Configuring an Egress Firewall Rule"
+msgstr "配置出口防火墙规则"
+
+# d7e0415b36d0404bb5d71baf38d49af2
+#: ../../networking/ip_forwarding_and_firewalling.rst:136
+msgid ""
+"In Select view, choose Guest networks, then click the Guest network you "
+"want."
+msgstr "在选择视图中，选择来宾网络，然后点击需要的来宾网络。"
+
+# acbfbe60bbfa423ab99d7faeea324dac
+#: ../../networking/ip_forwarding_and_firewalling.rst:139
+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 "要添加出口策略，点击出口策略选项卡并填写以下字段指定哪种类型的流量在来宾网络中是被允许从VM中实例发送出的。"
+
+# 93d9dbdbdf68488fb08f2c93714eb381
+#: ../../networking/ip_forwarding_and_firewalling.rst:143
+msgid "|egress-firewall-rule.png|"
+msgstr "|egress-firewall-rule.png|"
+
+# 71041bfd382d4c2ea6e0339c055e8e66
+#: ../../networking/ip_forwarding_and_firewalling.rst:145
+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 "**CIDR**:(仅通过CIDR添加)为接受来来自特殊地址块的流量，输入一个CIDR，多个时用逗号隔开。CIDR是进入流量的基础IP地址。例如：192.168.0.0/22，为允许所有CIDR，请设为0.0.0.0/0"
+
+# 136a4ea4a1424e4fb3a4e36f7ba438c7
+#: ../../networking/ip_forwarding_and_firewalling.rst:151
+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 "**协议**: 虚拟机发送流量所使用的网络协议。TCP和UDP通常用于数据交换和用户通讯。ICMP通常用于发送出错信息和网络监控数据。"
+
+# a710752f5a514f3e92ca3474b03d66b0
+#: ../../networking/ip_forwarding_and_firewalling.rst:156
+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 "**开始端口，结束端口**: (仅对TCP，UDP)。目的地为进入流量而设的监听端口范围。如果仅开放了单个端口，则在两者的区域中用同一端口。"
+
+# 273049a1dabe4b00aab163a686500120
+#: ../../networking/ip_forwarding_and_firewalling.rst:160
+msgid ""
+"**ICMP Type, ICMP Code**: (ICMP only) The type of message and error code "
+"that are sent."
+msgstr "**ICMP类型**, **ICMP代码** (ICMP only): 信息类型及发送错误的代码。"
+
+# 0ba1bc60e7114766b5562aa9f590799d
+#: ../../networking/ip_forwarding_and_firewalling.rst:167
+msgid "Configuring the Default Egress Policy"
+msgstr "配置默认出口策略"
+
+# 8b256b4cb62e43fe879f448d1cb5c940
+#: ../../networking/ip_forwarding_and_firewalling.rst:169
+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 "通过网络方案配置隔离来宾网络的默认出口策略。通过创建网络方案选项决定来宾网络到公共网络的所有流量在默认策略中是允许或者拒绝。使用该网络方案创建网络。如果没有指定策略，你创建的来宾网络中的所有流量将被允许。"
+
+# b03f1cb4957b4a18b437e26cca194176
+#: ../../networking/ip_forwarding_and_firewalling.rst:177
+msgid "You have two options: Allow and Deny."
+msgstr "你有两个选择：允许和拒绝。"
+
+# faccf3355885414e87bbb03070f6a7c0
+#: ../../networking/ip_forwarding_and_firewalling.rst:180
+msgid "Allow"
+msgstr "允许"
+
+# a7d3b32fbf8448c5ab02390ca3e1cc21
+#: ../../networking/ip_forwarding_and_firewalling.rst:182
+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 "如果你选择网络方案为允许，则默认出口流量被允许。无论如何，当配置了来宾网络的出口规则，规则被应用于阻止特定的流量和允许其他的 。如果网络中没有配置出口规则，则出口流量会被放行。"
+
+# 17b36c3415d3468896d8b48ae47ca8a8
+# 6cccf344439e4750904131cef8ef2b39
+# 1208ff713d13448f8bb67189a2a733dd
+#: ../../networking/ip_forwarding_and_firewalling.rst:189
+#: ../../networking/virtual_private_cloud_config.rst:323
+#: ../../networking/virtual_private_cloud_config.rst:324
+msgid "Deny"
+msgstr "拒绝"
+
+# 933662ed493243f599791cfc52e41965
+#: ../../networking/ip_forwarding_and_firewalling.rst:191
+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 "如果你选择网络方案为拒绝，则来宾网络中的默认出口流量将被阻挡。无论如何，当配置了来宾网络的出口规则，规则被应用于允许特定的流量。当实施来宾网络时，CloudStack为来宾网络添加防火墙出口规则指定默认的出口策略。"
+
+# 0f97837bd48b43808e4499c3bca32f0a
+#: ../../networking/ip_forwarding_and_firewalling.rst:198
+msgid "This feature is supported only on virtual router and Juniper SRX."
+msgstr "该特定只支持虚拟路由器和Juniper SRX。"
+
+# 12362b3472604a26858c49a699414934
+#: ../../networking/ip_forwarding_and_firewalling.rst:200
+msgid "Create a network offering with your desirable default egress policy:"
+msgstr "为合适的默认出口策略创建一个网络方案："
+
+# e3686a1cbaa54de4adb23df170fdbb9a
+#: ../../networking/ip_forwarding_and_firewalling.rst:202
+msgid "Log in with admin privileges to the CloudStack UI."
+msgstr "以管理员权限登录CloudStack用户界面。"
+
+# 2b34103f06b74a83956a2e4aa4c43e89
+#: ../../networking/ip_forwarding_and_firewalling.rst:204
+msgid "In the left navigation bar, click Service Offerings."
+msgstr "在左侧导航栏中，点击 服务方案。"
+
+# be40a0ea880c4159a9d420c70881eeba
+#: ../../networking/ip_forwarding_and_firewalling.rst:206
+msgid "In Select Offering, choose Network Offering."
+msgstr "在选择方案中，选择网络方案。"
+
+# 3b005d62ac404f7a971817f2e813a88a
+# 42bbce384f5b43a39000860f820fe3a0
+# 80979f7b880b45f0864683361aa46fd3
+#: ../../networking/ip_forwarding_and_firewalling.rst:208
+#: ../../networking/virtual_private_cloud_config.rst:961
+#: ../../networking/virtual_private_cloud_config.rst:1167
+msgid "Click Add Network Offering."
+msgstr "点击添加网络方案。"
+
+# d3e708006ce243298b2fdbfef4a94a28
+#: ../../networking/ip_forwarding_and_firewalling.rst:210
+msgid "In the dialog, make necessary choices, including firewall provider."
+msgstr "在对话框中，填写必选项，包括防火墙提供者。"
+
+# a6aaeba01e87402cab4799e384a7e8b7
+#: ../../networking/ip_forwarding_and_firewalling.rst:213
+msgid "In the Default egress policy field, specify the behaviour."
+msgstr "在默认出口策略选项中，指定行为。"
+
+# dfeed74eee834f7aa70dc9a0ebca0b5d
+#: ../../networking/ip_forwarding_and_firewalling.rst:217
+msgid "Create an isolated network by using this network offering."
+msgstr "使用网络方案创建隔离网络。"
+
+# d4f2f0db67ad4becad9ecf217e63fc08
+#: ../../networking/ip_forwarding_and_firewalling.rst:219
+msgid ""
+"Based on your selection, the network will have the egress public traffic "
+"blocked or allowed."
+msgstr "根据你的选择，网络的出口公共流量将被拒绝或允许。"
+
+# 49dbcf0869cc408aac40d8ace99c793b
+#: ../../networking/ip_forwarding_and_firewalling.rst:224
+msgid "Port Forwarding"
+msgstr "端口转发"
+
+# d63e7dc020174931a136b5f851d10342
+#: ../../networking/ip_forwarding_and_firewalling.rst:226
+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 "一个端口转发服务是一系列转发转发规则的集合。一个端口转发服务随后可以应用于一个或多个来宾虚拟机。来宾虚拟机会根据端口转发规则作相关进入端口的管理。你可以定义一个或多个CIDR来过滤源IP地址。当你只希望特定的IP流量进入时是相当有用的。"
+
+# 28ad8f3213ac41ed9debe3407c4cf783
+#: ../../networking/ip_forwarding_and_firewalling.rst:234
+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 "一个客户VM可以在任意数量的端口转发服务中。端口转发服务可以不包含客户VM。如果客户VM在多个网络中，则端口转发仅在默认网络中定义时才生效。"
+
+# acee955e81034850834c7f10a308dd65
+#: ../../networking/ip_forwarding_and_firewalling.rst:239
+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 "您不能使用端口转发打开弹性IP地址的端口。当使用弹性IP时，外部访问是由安全组控制的。参见安全组。"
+
+# 456211f25f094d9090dc8de808d1c666
+#: ../../networking/ip_forwarding_and_firewalling.rst:243
+msgid "To set up port forwarding:"
+msgstr "设置端口转发："
+
+# d0f998d8aa0a48f9a3f19ea0d36f07d2
+#: ../../networking/ip_forwarding_and_firewalling.rst:247
+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 "如果还没有，请在 CloudStack中为Zone添加公网IP段。参阅 安装指南中的添加Zone和Pod。"
+
+# 10d08ed8092843f18456b1a0752ba168
+#: ../../networking/ip_forwarding_and_firewalling.rst:251
+msgid "Add one or more VM instances to CloudStack."
+msgstr "在 CloudStack中创建1台或更多VM。"
+
+# bdd495a8008d4823b8bd78a763cca275
+#: ../../networking/ip_forwarding_and_firewalling.rst:253
+msgid "In the left navigation bar, click Network."
+msgstr "在左边导航栏，点击网络。"
+
+# 73ad1f9cd260427bb05aeb2d4ca2f056
+#: ../../networking/ip_forwarding_and_firewalling.rst:255
+msgid "Click the name of the guest network where the VMs are running."
+msgstr "点击需要操作VM所在的网络名称。"
+
+# 89c3b56ae71346e9b89fa5e446f3f43d
+#: ../../networking/ip_forwarding_and_firewalling.rst:257
+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 "选择一个已有的IP或者获取一个新的IP地址。参阅 `\"获取一个新的IP\" <#acquiring-a-new-ip-address>`_.。 点击列表中IP地址的名称。"
+
+# 2c19d7e25d8845cbba9fd2d132c04fb7
+#: ../../networking/ip_forwarding_and_firewalling.rst:261
+msgid "Click the Configuration tab."
+msgstr "点击配置选项卡。"
+
+# a9244a779ecb4355bbabd6689495a9ae
+# 35dbd54b25cb438f97ccf2f32ff9370e
+#: ../../networking/ip_forwarding_and_firewalling.rst:263
+#: ../../networking/virtual_private_cloud_config.rst:1326
+msgid "In the Port Forwarding node of the diagram, click View All."
+msgstr "在图表的端口转发节点，点击查看所有。"
+
+# a51ed2228b8a437386ad9ff99ee96a04
+# e6d29f52eea44172bfaa95b47d20d5b9
+#: ../../networking/ip_forwarding_and_firewalling.rst:267
+#: ../../networking/virtual_private_cloud_config.rst:1332
+msgid ""
+"**Public Port**: The port to which public traffic will be addressed on the "
+"IP address you acquired in the previous step."
+msgstr "**公用端口**: 你在前面操作所获取的供公共流量使用的公用IP地址的端口。 "
+
+# 994ccfa7425f4863ade7a74a14b9e011
+# 5fbd968022954bba912d0dfdbe504ad9
+#: ../../networking/ip_forwarding_and_firewalling.rst:270
+#: ../../networking/virtual_private_cloud_config.rst:1335
+msgid ""
+"**Private Port**: The port on which the instance is listening for forwarded "
+"public traffic."
+msgstr "**私有端口**: 虚拟机实例将被转发到公共流量的监听端口。"
+
+# 98023e5bfedb4649a79fadc67850521f
+#: ../../networking/ip_forwarding_and_firewalling.rst:273
+msgid "**Protocol**: The communication protocol in use between the two ports"
+msgstr ""
+
+# b71d2a4a35644691974638b71dbe56b1
+#: ../../networking/ip_load_balancing.rst:18
+msgid "IP Load Balancing"
+msgstr "IP负载均衡"
+
+# 982a5f5a6b7f481dbf623c4ae30c9ef1
+#: ../../networking/ip_load_balancing.rst:20
+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 "用户可以选择关联同一个公网IP到多个虚拟机。 CloudStack实现了TCP级别的负载平衡器，有以下策略。"
+
+# a01b6fefc32a4fce911ca69c16c670d9
+# 28c60cdb8d574461b463ea6e8e14675c
+# b09a939f044f421d83e16513b3a9dc7b
+#: ../../networking/ip_load_balancing.rst:24
+#: ../../networking/virtual_private_cloud_config.rst:1076
+#: ../../networking/virtual_private_cloud_config.rst:1272
+msgid "Round-robin"
+msgstr "轮询"
+
+# e8cdafa2b1f645e99d3133d52f0a355a
+#: ../../networking/ip_load_balancing.rst:26
+msgid "Least connection"
+msgstr "最少连接数"
+
+# 803259d2ae8f446a9c4ec7c8ed71a28b
+#: ../../networking/ip_load_balancing.rst:28
+msgid "Source IP"
+msgstr "源IP"
+
+# 6ba67a79525947f49fd89a4630112c11
+#: ../../networking/ip_load_balancing.rst:30
+msgid ""
+"This is similar to port forwarding but the destination may be multiple IP "
+"addresses."
+msgstr "这类似于端口转发，但目标可能会有多个IP地址。"
+
+# f64b9bee4c5c4f5b8edb7227f447c380
+#: ../../networking/dns_and_dhcp.rst:18
+msgid "DNS and DHCP"
+msgstr "DNS和DHCP"
+
+# b1490bbc343240eba492e29dd3431440
+#: ../../networking/dns_and_dhcp.rst:20
+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 "虚拟路由器为来宾提供DNS和DHCP服务。它将DNS请求代理到在可用区域中配置的DNS服务器。"
+
+# 380298c917b144379af6fe612e2d842a
+#: ../../networking/remote_access_vpn.rst:18
+msgid "Remote Access VPN"
+msgstr "远程访问VPN"
+
+# 6e90c60bc41e4969b0281b09531745b8
+#: ../../networking/remote_access_vpn.rst:20
+msgid ""
+"CloudStack account owners can create virtual private networks (VPN) to "
+"access their virtual machines. If the guest network is instantiated from a "
+"network offering that offers the Remote Access VPN service, the virtual "
+"router (based on the System VM) is used to provide the service. CloudStack "
+"provides a L2TP-over-IPsec-based remote access VPN service to guest virtual "
+"networks. Since each network gets its own virtual router, VPNs are not "
+"shared across the networks. VPN clients native to Windows, Mac OS X and iOS "
+"can be used to connect to the guest networks. The account owner can create "
+"and manage users for their VPN. CloudStack does not use its account database"
+" for this purpose but uses a separate table. The VPN user database is shared"
+" across all the VPNs created by the account owner. All VPN users get access "
+"to all VPNs created by the account owner."
+msgstr "CloudStack中的账户拥有者可以建立虚拟专用网(VPN)以便访问他们的虚拟机。如果通过网络方案对来宾网络提供远程VPN访问服务的实例化，虚拟路由(基于System VM)将被用于提供服务。CloudStack为来宾虚拟网络提供了一个基于L2TP-over-IPsec-based协议的远程VPN访问服务。因为每个网络有它自己的虚拟路由器，VPNs不能跨网络共享。Windows, Mac OS X和iOS自带的VPN客户端可以用于访问来宾网络。账户拥有者可以建立并管理他们的VPN用户。CloudStack并不为此使用自己的账户数据库，而是使用一个独立的表。VPN用户数据库在同一个账户拥有者建立的VPN网络中被共享。 也就是说，同一个账户拥有者创建的所有VPN可以被它的所有VPN用户访问。"
+
+# c670185e66c148958a214fecee43aff5
+#: ../../networking/remote_access_vpn.rst:35
+msgid ""
+"Make sure that not all traffic goes through the VPN. That is, the route "
+"installed by the VPN should be only for the guest network and not for all "
+"traffic."
+msgstr "确保不是所有的网络流量走VPN。也就是说，用于配置VPN的route不是唯一用于该guest network，也不承担全部的网络流量。"
+
+# dba6da095c764124a25c5a98d801496e
+#: ../../networking/remote_access_vpn.rst:39
+msgid ""
+"**Road Warrior / Remote Access**. Users want to be able to connect securely "
+"from a home or office to a private network in the cloud. Typically, the IP "
+"address of the connecting client is dynamic and cannot be preconfigured on "
+"the VPN server."
+msgstr "**公路勇士/远程访问**. .用户希望可以安全地从家里或者办公室连接到云里的一个 私有网络。特别是连接的客户端的IP地址是动态决定的，不能预先配置到VPN 服务器上。"
+
+# 8793d40a1a80441398907f711e568b99
+#: ../../networking/remote_access_vpn.rst:44
+msgid ""
+"**Site to Site**. In this scenario, two private subnets are connected over "
+"the public Internet with a secure VPN tunnel. The cloud user's subnet (for "
+"example, an office network) is connected through a gateway to the network in"
+" the cloud. The address of the user's gateway must be preconfigured on the "
+"VPN server in the cloud. Note that although L2TP-over-IPsec can be used to "
+"set up Site-to-Site VPNs, this is not the primary intent of this feature. "
+"For more information, see \":ref:`setting-s2s-vpn-conn`\"."
+msgstr "**Site to Site 站点到站点**。在这个场景中，两个私有子网通过公共互联网上的一个安全VPN隧道互联。云用户的子网 （例如：办公室的网络）通过一个网关连接到云中的网络。用户的网关地址必须被预先配置到云的VPN服务器上。注意：通过 L2TP-over-IPsec 协议可以用来配置站点到站点的 VPN，虽然这不是该特性的最初目标。更多信息，参考\":ref:`setting-s2s-vpn-conn`\"。"
+
+# 8c8d8279293b421c868d44267f2291d1
+#: ../../networking/remote_access_vpn.rst:55
+msgid "Configuring Remote Access VPN"
+msgstr "配置远程访问VPN"
+
+# 90ad6dccf00c4430ac2951fce79496d6
+#: ../../networking/remote_access_vpn.rst:57
+msgid "To set up VPN for the cloud:"
+msgstr "为云设置VPN："
+
+# e37d36e8639e48b5a1043c2e57008523
+#: ../../networking/remote_access_vpn.rst:61
+msgid "In the left navigation, click Global Settings."
+msgstr "在左侧导航栏，点击 全局设置"
+
+# 505b3a7726bc48fda8c03560c7bf88b1
+#: ../../networking/remote_access_vpn.rst:63
+msgid "Set the following global configuration parameters."
+msgstr "设置以下全局配置参数。"
+
+# 53ec16f914374f86a2beb90e7af26ece
+#: ../../networking/remote_access_vpn.rst:65
+msgid ""
+"remote.access.vpn.client.ip.range - The range of IP addresses to be "
+"allocated to remote access VPN clients. The first IP in the range is used by"
+" the VPN server."
+msgstr "remote.access.vpn.client.ip.range – 分配给远程访问VPN客户端的IP地址范围。第一个IP被VPN服务器使用。"
+
+# f4300671c2a149c284a642b6f79ef00e
+#: ../../networking/remote_access_vpn.rst:69
+msgid "remote.access.vpn.psk.length - Length of the IPSec key."
+msgstr "remote.access.vpn.psk.length – IPsec密钥长度。"
+
+# 231df586fa3c4ed1970d5b7575cc5b83
+#: ../../networking/remote_access_vpn.rst:71
+msgid ""
+"remote.access.vpn.user.limit - Maximum number of VPN users per account."
+msgstr "remote.access.vpn.user.limit – 单个账户的最大VPN用户数量。"
+
+# 76cfe55cf6cf458e93e7c31c53fd06c7
+#: ../../networking/remote_access_vpn.rst:74
+msgid "To enable VPN for a particular network:"
+msgstr "为特定的网络启用VPN："
+
+# 7c4372020568480ea2a617b164d7fde7
+# 84de4841949448d09c061ed72abcd263
+#: ../../networking/remote_access_vpn.rst:76
+#: ../../networking/remote_access_vpn.rst:101
+msgid "Log in as a user or administrator to the CloudStack UI."
+msgstr "使用用户或管理员身份登录到CloudStack用户界面。"
+
+# 1b8df6da450a4c73b2f16aa4eaca745f
+# 5be9a0df2c9b497c95947824049942f6
+#: ../../networking/remote_access_vpn.rst:78
+#: ../../networking/remote_access_vpn.rst:103
+msgid "In the left navigation, click Network."
+msgstr "在左边导航栏，点击网络。"
+
+# 4a0bb2f81c4f4829853bbbb9f5fdcdea
+#: ../../networking/remote_access_vpn.rst:80
+msgid "Click the name of the network you want to work with."
+msgstr "选择你要操作的网络名称"
+
+# dcdbca37932e4934822095b46a7460fd
+#: ../../networking/remote_access_vpn.rst:84
+msgid "Click one of the displayed IP address names."
+msgstr "点击一个显示的IP地址名称。"
+
+# c58b358559ab46a8b37d20c157cabb78
+# 3d371180587a4467995d29840af82de7
+#: ../../networking/remote_access_vpn.rst:86
+#: ../../networking/remote_access_vpn.rst:140
+msgid "Click the Enable VPN button. |vpn-icon.png|"
+msgstr "点击启用VPN按钮。|vpn-icon.png|"
+
+# d3fc3632ae204d92945354ecf5b17a1c
+#: ../../networking/remote_access_vpn.rst:88
+msgid "The IPsec key is displayed in a popup window."
+msgstr "IPsec密钥将显示在弹出的窗口中。"
+
+# 866b778ea915477a8513f360a7923a9f
+#: ../../networking/remote_access_vpn.rst:92
+msgid "Configuring Remote Access VPN in VPC"
+msgstr "为VPC配置远程访问VPN"
+
+# 4f7b18dfcf584e5c90d57d8e8a471744
+#: ../../networking/remote_access_vpn.rst:94
+msgid ""
+"On enabling Remote Access VPN on a VPC, any VPN client present outside the "
+"VPC can access VMs present in the VPC by using the Remote VPN connection. "
+"The VPN client can be present anywhere except inside the VPC on which the "
+"user enabled the Remote Access VPN service."
+msgstr "在VPC中启用远程访问VPN，任何VPC以外的VPN客户端都可以使用远程VPN连接访问VPC中的VM。VPN客户端可以在除了用户启用了远程访问VPN服务的VPC中的任何位置。"
+
+# cf87d57665af4942874e753a98b32768
+#: ../../networking/remote_access_vpn.rst:99
+msgid "To enable VPN for a VPC:"
+msgstr "为VPC开启VPN："
+
+# a851855e564c4ad2abb7f191c35fc2e8
+# 7696ccb576dc417482a5c054ceca9b60
+# e018f229d0304c21bc251e3bcaf4174e
+# 853e8a12190242e1922b7e3eceeacd90
+# 858d04db9e0d49328574f666ca08832b
+# 7e353532572644f29c0956717585ae5d
+# 3788df11cb0b4d9f99e69906815734a3
+# 2bb59ff5316a4315ad133017bc7aaa7b
+# 19560e560096444384f47cc8bcc957a9
+# 92e2187aa49046a4a1c1d8e8b50caeda
+# 74ff9845b2fc4a28a4f6e5c10d5b5e41
+# 3f4c3248f6b74195aadf920c9d064ea0
+# 37596bbfca114dd292c20a4d712a56d4
+# 474cd3b9ddcf45209e8b7f7c20094087
+# f011af1bc62c416bb2cc09b3e6d1da82
+# 51106dd7db2e450480c1b806d5f8c575
+# 20cb483c8c1a457d88d907105a2df0b6
+# 20037f12721b44a5b069106ec01c9037
+#: ../../networking/remote_access_vpn.rst:105
+#: ../../networking/remote_access_vpn.rst:435
+#: ../../networking/remote_access_vpn.rst:497
+#: ../../networking/remote_access_vpn.rst:628
+#: ../../networking/virtual_private_cloud_config.rst:183
+#: ../../networking/virtual_private_cloud_config.rst:227
+#: ../../networking/virtual_private_cloud_config.rst:335
+#: ../../networking/virtual_private_cloud_config.rst:384
+#: ../../networking/virtual_private_cloud_config.rst:496
+#: ../../networking/virtual_private_cloud_config.rst:666
+#: ../../networking/virtual_private_cloud_config.rst:733
+#: ../../networking/virtual_private_cloud_config.rst:792
+#: ../../networking/virtual_private_cloud_config.rst:852
+#: ../../networking/virtual_private_cloud_config.rst:1018
+#: ../../networking/virtual_private_cloud_config.rst:1231
+#: ../../networking/virtual_private_cloud_config.rst:1286
+#: ../../networking/virtual_private_cloud_config.rst:1364
+#: ../../networking/virtual_private_cloud_config.rst:1392
+msgid "In the Select view, select VPC."
+msgstr "在选择视图中，选择VPC。"
+
+# 433a058aaf2c4f7abcac16a4a89c0cb0
+# 253f99defd504664bca4c20805fad8d8
+# b03f74003e0f49f7b107d129dc8378f5
+# 0c712fdfecf145558f1363a547a5be30
+# 73d10dfbf9fe4ada98571d825e6a514f
+# df3ab8626fa64f6aac0e4c7b4baba5f6
+# 7d49d58694804462b40ebf7853c9f722
+# b343232e12944a0fa7e090d98eb63cdd
+# 01f2e1ef8d4a4fdd977b417d2e5a263f
+# 93c2804d558a4e9d838e266756a2a563
+# d561a8755b42408f897f89f7078867ec
+# c51038c5a8a44985867d6ba9c27b9d9d
+# fbee3b23e526460b81062dca124f6118
+# 0e98fee7920f4d06bebf81cf58e4cc47
+#: ../../networking/remote_access_vpn.rst:107
+#: ../../networking/remote_access_vpn.rst:437
+#: ../../networking/remote_access_vpn.rst:630
+#: ../../networking/virtual_private_cloud_config.rst:337
+#: ../../networking/virtual_private_cloud_config.rst:386
+#: ../../networking/virtual_private_cloud_config.rst:498
+#: ../../networking/virtual_private_cloud_config.rst:668
+#: ../../networking/virtual_private_cloud_config.rst:735
+#: ../../networking/virtual_private_cloud_config.rst:794
+#: ../../networking/virtual_private_cloud_config.rst:854
+#: ../../networking/virtual_private_cloud_config.rst:1020
+#: ../../networking/virtual_private_cloud_config.rst:1233
+#: ../../networking/virtual_private_cloud_config.rst:1288
+#: ../../networking/virtual_private_cloud_config.rst:1394
+msgid ""
+"All the VPCs that you have created for the account is listed in the page."
+msgstr "此帐号创建的所有VPC将显示在页面中。"
+
+# 9be1f95a9d58404cbd6e4417d049f493
+# 101241fe7ad147dd849d0b52d7648247
+# 1448cfd34b3f43a480717b41c5eebb77
+#: ../../networking/remote_access_vpn.rst:110
+#: ../../networking/virtual_private_cloud_config.rst:340
+#: ../../networking/virtual_private_cloud_config.rst:389
+msgid "Click the Configure button of the VPC."
+msgstr "点击VPC的配置按钮。"
+
+# c95b38d3084f49a79782733848b3ecca
+# ab89f03b01054efcbdc4b304e895e95b
+# e9dc8a6495354766a07447565741a528
+# 985ac077ba8248a7a48dfa8c5c506d16
+# 9bc1baaed7ec4515ad2c3b5c6ce0451e
+# 801d602110c041cabcf0cc684584957a
+# be7596ebba2542159b95b5abc0607142
+#: ../../networking/remote_access_vpn.rst:112
+#: ../../networking/remote_access_vpn.rst:446
+#: ../../networking/remote_access_vpn.rst:509
+#: ../../networking/remote_access_vpn.rst:641
+#: ../../networking/virtual_private_cloud_config.rst:342
+#: ../../networking/virtual_private_cloud_config.rst:1029
+#: ../../networking/virtual_private_cloud_config.rst:1297
+msgid "For each tier, the following options are displayed:"
+msgstr "对于每一个层，会显示以下选项。"
+
+# 0d83a023e9014f9aade55353c79e3170
+# 401ffa05eaf246a28e37840ebe9292cc
+# 067e314f365a480ca4a21f8e163015f1
+# f9a89e98ace24da0b17c3378764628ec
+# df1588b26c554c8ebb2120108c70f35d
+# 14d477e028374bc7ba1a23e02c9a1b4c
+# 3961aede6bf54c31b9c546f46b4e6aa5
+# 8f1f5dfc2d674fc194d70276d8d18468
+# 0a8f19a5e8734bcab55acd9fca629358
+# 445b7ca76fea45e8a3439159d1faa90e
+# 1487ab642c08402ca5ba42c3837ea69a
+#: ../../networking/remote_access_vpn.rst:114
+#: ../../networking/remote_access_vpn.rst:448
+#: ../../networking/remote_access_vpn.rst:511
+#: ../../networking/remote_access_vpn.rst:643
+#: ../../networking/virtual_private_cloud_config.rst:344
+#: ../../networking/virtual_private_cloud_config.rst:511
+#: ../../networking/virtual_private_cloud_config.rst:746
+#: ../../networking/virtual_private_cloud_config.rst:804
+#: ../../networking/virtual_private_cloud_config.rst:865
+#: ../../networking/virtual_private_cloud_config.rst:1031
+#: ../../networking/virtual_private_cloud_config.rst:1299
+msgid "Internal LB"
+msgstr "内部LB"
+
+# 31d49abe67634960a557928d198a117b
+# d9f6c55773f44decab0c8f7c54706ab1
+# 77bc18fed48f46e4ac2df77187e262df
+# 2261a78bcdfd4e6da5136e979c35bb88
+# cbbd2dca656549c884e00639b9ae2035
+# e61e6beeae9c412bbe90181105cf2ae1
+# 909e61b8202a4b838f82ea576f748d63
+# 44b5133723344f3bbd1c7783e59642ed
+# b4286c8c1b954ab2bf7fe43800649c15
+# 0c9f5baff8f847a8871c2dc07441e145
+# 39db39923d924abba04f7eb190b0c065
+#: ../../networking/remote_access_vpn.rst:116
+#: ../../networking/remote_access_vpn.rst:450
+#: ../../networking/remote_access_vpn.rst:513
+#: ../../networking/remote_access_vpn.rst:645
+#: ../../networking/virtual_private_cloud_config.rst:346
+#: ../../networking/virtual_private_cloud_config.rst:513
+#: ../../networking/virtual_private_cloud_config.rst:748
+#: ../../networking/virtual_private_cloud_config.rst:806
+#: ../../networking/virtual_private_cloud_config.rst:867
+#: ../../networking/virtual_private_cloud_config.rst:1033
+#: ../../networking/virtual_private_cloud_config.rst:1301
+msgid "Public LB IP"
+msgstr "公共LB IP"
+
+# 5eaac9ad38594847b17964661cf9236c
+# 92df7a88e8e04a3483d10de7d9e73800
+# 5a76cc0a9455476cbc8b2c81878d7f05
+# 89f6fcd63e4f4cd1a5c2ae9d98d431d3
+# 3848ce6d7b224573a45a3daa5e369d11
+# ef82afc618e2465d879fb6566335f979
+# 4270f6ecdc324f22951c5acb77c4ee23
+# 39a7d2038d76415498e328d304159562
+# 593c2b74c4fc46a68613d48864ea1ea1
+# 442f49fa53564d63ac1c056170b5b4a8
+# 1679c7f2f3d74f87941189cd7a8eadf1
+#: ../../networking/remote_access_vpn.rst:120
+#: ../../networking/remote_access_vpn.rst:454
+#: ../../networking/remote_access_vpn.rst:517
+#: ../../networking/remote_access_vpn.rst:649
+#: ../../networking/virtual_private_cloud_config.rst:350
+#: ../../networking/virtual_private_cloud_config.rst:517
+#: ../../networking/virtual_private_cloud_config.rst:752
+#: ../../networking/virtual_private_cloud_config.rst:810
+#: ../../networking/virtual_private_cloud_config.rst:871
+#: ../../networking/virtual_private_cloud_config.rst:1037
+#: ../../networking/virtual_private_cloud_config.rst:1305
+msgid "Virtual Machines"
+msgstr "虚拟机"
+
+# f5bae5ffb2f542f1a50da6263d5830fc
+# 1353046d5778408f926e87efdf7cfff4
+# 86105ce7fed24f5cb1731b0445e71c58
+# d0a50513766f4193a8ae3ce206f4f27f
+# 9494e63e7f1345eab39614b094d5418c
+# e840260e3fbe4d8e9ee76819e55c2271
+# 6e3d9062bdbb4bba84da4f570fd7c7fb
+# b76b5756109d44ddb7bcf3eee9b52377
+# ad03548aa7c148f1b0bb6d6489c1b169
+# 2eeb832b8f2744ff994afa7f34a8d110
+# fef8407d652246f9b64d3af9fab77e4c
+#: ../../networking/remote_access_vpn.rst:124
+#: ../../networking/remote_access_vpn.rst:458
+#: ../../networking/remote_access_vpn.rst:521
+#: ../../networking/remote_access_vpn.rst:653
+#: ../../networking/virtual_private_cloud_config.rst:354
+#: ../../networking/virtual_private_cloud_config.rst:521
+#: ../../networking/virtual_private_cloud_config.rst:756
+#: ../../networking/virtual_private_cloud_config.rst:814
+#: ../../networking/virtual_private_cloud_config.rst:875
+#: ../../networking/virtual_private_cloud_config.rst:1041
+#: ../../networking/virtual_private_cloud_config.rst:1309
+msgid "The following router information is displayed:"
+msgstr "显示以下路由器信息："
+
+# daf0d5dc2d9040e19b1366f58af4b3c6
+# a4596fec8cdb45bba1c99bc713b0d10c
+# 8da0cfd9fed2460cb97816a778997f9d
+# 056a09262bfc4d6482a20801b8acaaf5
+# 777bc6a7065949dbb37c74c841759e3c
+# b2c193538ac94be38e2a27ee2bf943d0
+# 0f492f18d1ae4cee885b69b82980784f
+# 5afe0c98d94b4a129c170577873b4208
+# d371bf7bd366484abd327ba22b4906d8
+# 7cf1fde7dabe40ecb52db6750a1508f7
+# 0369ed96499e48b3a23519de10fa02a8
+#: ../../networking/remote_access_vpn.rst:126
+#: ../../networking/remote_access_vpn.rst:460
+#: ../../networking/remote_access_vpn.rst:523
+#: ../../networking/remote_access_vpn.rst:655
+#: ../../networking/virtual_private_cloud_config.rst:356
+#: ../../networking/virtual_private_cloud_config.rst:523
+#: ../../networking/virtual_private_cloud_config.rst:758
+#: ../../networking/virtual_private_cloud_config.rst:816
+#: ../../networking/virtual_private_cloud_config.rst:877
+#: ../../networking/virtual_private_cloud_config.rst:1043
+#: ../../networking/virtual_private_cloud_config.rst:1311
+msgid "Private Gateways"
+msgstr "专用网关"
+
+# 5f0457bd87ee495a8d5bfe9c4e4140b9
+# be6d3ce6cbaf4b5784187f736898bbb4
+# 137340b6a07047f5b4105b550bd2dea5
+# 16a448bd22a34fd59b341f0be0cfad13
+# 98dd6a7c42284bd7ab5a086176692d74
+# 77e662d10339479c93999acb83f50aab
+# f87b9d1bf7c8489d824e4bc2c1edb94a
+# 4627c69d41294c8fab4d9898db33c83f
+# 0c430ab6225a479a8e58afe0436292db
+# f224a8b6cbea436aaea2ce0b6c58b5a5
+# 50ff9ec30a43472aaaea14d658f3ede1
+#: ../../networking/remote_access_vpn.rst:128
+#: ../../networking/remote_access_vpn.rst:462
+#: ../../networking/remote_access_vpn.rst:525
+#: ../../networking/remote_access_vpn.rst:657
+#: ../../networking/virtual_private_cloud_config.rst:358
+#: ../../networking/virtual_private_cloud_config.rst:525
+#: ../../networking/virtual_private_cloud_config.rst:760
+#: ../../networking/virtual_private_cloud_config.rst:818
+#: ../../networking/virtual_private_cloud_config.rst:879
+#: ../../networking/virtual_private_cloud_config.rst:1045
+#: ../../networking/virtual_private_cloud_config.rst:1313
+msgid "Public IP Addresses"
+msgstr "公共IP地址"
+
+# 2a01498545a9403e8315ab2b9dc8d3ff
+# 5c6c556abdb042cd95b91af10067d5b6
+# 863fdc1a436149ec81d2a240d4d22a2f
+# 79192eb67b614bd58e10729375bddf8c
+# d36fe14908f246bf83e43933e55ef3b4
+# 65e2c761e70f4440ad714dd09cd91349
+# 5aeddf583b6743bb889616c075b0793a
+# 147238d0cb65480c9d78837c05e43bd9
+# 1b2e46ec5bea49d09a0c7c272595d111
+# 26fcc9420a3f49edb4de8b1efbb457bc
+# 63efa7ad47a34105874929f9bbd9427f
+#: ../../networking/remote_access_vpn.rst:130
+#: ../../networking/remote_access_vpn.rst:464
+#: ../../networking/remote_access_vpn.rst:527
+#: ../../networking/remote_access_vpn.rst:659
+#: ../../networking/virtual_private_cloud_config.rst:360
+#: ../../networking/virtual_private_cloud_config.rst:527
+#: ../../networking/virtual_private_cloud_config.rst:762
+#: ../../networking/virtual_private_cloud_config.rst:820
+#: ../../networking/virtual_private_cloud_config.rst:881
+#: ../../networking/virtual_private_cloud_config.rst:1047
+#: ../../networking/virtual_private_cloud_config.rst:1315
+msgid "Site-to-Site VPNs"
+msgstr "站点到站点 VPN"
+
+# b27df81c137d4ada8a78b99a42ce9318
+# ce6512f959b543ed84a43badeb5efb3c
+# b81bad1751644d18810aa0953be2bea5
+# 9f3e88679a5d4387855b32022dbff52c
+# 0e0ee230ef824ba0a10c19e3b311b598
+# 78ef6f691db5444eb53d8f8e2876e4e9
+# 3a98e8ef4c754c41ab1345025b5cc625
+# 0e6c5b8161104349a11cb3207b8b813a
+# 383a9b461f6b4113acb24f60ec71b1fc
+# cc1ad8b9d34945a9baa02216efbc2555
+# 299782736e884755a67a9ff9eae837dd
+#: ../../networking/remote_access_vpn.rst:132
+#: ../../networking/remote_access_vpn.rst:466
+#: ../../networking/remote_access_vpn.rst:529
+#: ../../networking/remote_access_vpn.rst:661
+#: ../../networking/virtual_private_cloud_config.rst:362
+#: ../../networking/virtual_private_cloud_config.rst:529
+#: ../../networking/virtual_private_cloud_config.rst:764
+#: ../../networking/virtual_private_cloud_config.rst:822
+#: ../../networking/virtual_private_cloud_config.rst:883
+#: ../../networking/virtual_private_cloud_config.rst:1049
+#: ../../networking/virtual_private_cloud_config.rst:1317
+msgid "Network ACL Lists"
+msgstr "网络 ACL列表"
+
+# c6c2c79f850f4077829c5505885e62f5
+# 1062ef9c7f464e158c482bea53e6ea61
+# e6718162b3284e44a60f542408ae32fc
+# 6a480049441d4ccc8a31e3f11799dd7b
+#: ../../networking/remote_access_vpn.rst:134
+#: ../../networking/virtual_private_cloud_config.rst:885
+#: ../../networking/virtual_private_cloud_config.rst:1051
+#: ../../networking/virtual_private_cloud_config.rst:1319
+msgid "In the Router node, select Public IP Addresses."
+msgstr "在路由器节点中，选择公共IP地址。"
+
+# 7d553b7fbdc6413d8c633ce8dfb4868c
+# 2b2b55ab8a624bb78e95913869ab2a05
+# 0de20186cc34473cb61133c9b865f960
+# 3e9dafbca1bc4a50b60617d6c81f170f
+# 9abe20eba64240cd90a18743af0e00c2
+#: ../../networking/remote_access_vpn.rst:136
+#: ../../networking/virtual_private_cloud_config.rst:826
+#: ../../networking/virtual_private_cloud_config.rst:887
+#: ../../networking/virtual_private_cloud_config.rst:1053
+#: ../../networking/virtual_private_cloud_config.rst:1321
+msgid "The IP Addresses page is displayed."
+msgstr "系统显示IP地址页面。"
+
+# f1ce2b4d26b145d49d98a4cecca586e8
+#: ../../networking/remote_access_vpn.rst:138
+msgid "Click Source NAT IP address."
+msgstr "点击源NAT IP地址。"
+
+# e83452437c9449d7b1f7508735d5e35a
+#: ../../networking/remote_access_vpn.rst:142
+msgid "Click OK to confirm. The IPsec key is displayed in a pop-up window."
+msgstr "点击OK确认。IPsec密钥将显示在弹出的窗口中。"
+
+# d9c262cf3fdb476ea6a3500b5c9e3102
+#: ../../networking/remote_access_vpn.rst:144
+msgid "Now, you need to add the VPN users."
+msgstr "现在，需要添加VPN用户。"
+
+# 93e980a2795646be9a5fbc975be42289
+#: ../../networking/remote_access_vpn.rst:146
+msgid "Click the Source NAT IP."
+msgstr "点击源NAT IP。"
+
+# 15e0e443545942579a324fda601e2686
+#: ../../networking/remote_access_vpn.rst:148
+msgid "Select the VPN tab."
+msgstr "选择VPN选项卡。"
+
+# 400f2955d75b4fe29ece4d0b82cdadf3
+#: ../../networking/remote_access_vpn.rst:150
+msgid ""
+"Add the username and the corresponding password of the user you wanted to "
+"add."
+msgstr "为你要创建的用户添加用户名和对应的密码。"
+
+# 13bbf1c44ce8451e9fda9df0a55488d9
+#: ../../networking/remote_access_vpn.rst:155
+msgid "Repeat the same steps to add the VPN users."
+msgstr "重复相同的步骤添加VPN用户。"
+
+# f882d1b965574377abb5c47c46d2017d
+#: ../../networking/remote_access_vpn.rst:159
+msgid "Using Remote Access VPN with Windows"
+msgstr "在Windows系统中使用远程访问VPN"
+
+# 7dac5068f0b244e1a144a09d45c39932
+#: ../../networking/remote_access_vpn.rst:161
+msgid ""
+"The procedure to use VPN varies by Windows version. Generally, the user must"
+" edit the VPN properties and make sure that the default route is not the "
+"VPN. The following steps are for Windows L2TP clients on Windows Vista. The "
+"commands should be similar for other Windows versions."
+msgstr "程序使用不同Windows版本的VPN。通常用户必须编辑VPN属性并确保不使用VPN的默认路由。以下步骤使用基于Windows Vista的Windows L2TP客户端。命令应该类似于其他版本的Windows。"
+
+# 9863de47db9f4572ad58ea772de9f36d
+#: ../../networking/remote_access_vpn.rst:166
+msgid ""
+"Log in to the CloudStack UI and click on the source NAT IP for the account. "
+"The VPN tab should display the IPsec preshared key. Make a note of this and "
+"the source NAT IP. The UI also lists one or more users and their passwords. "
+"Choose one of these users, or, if none exists, add a user and password."
+msgstr "登录到CloudStack用户界面并点击账户下的源NAT IP。VPN选项卡应该会显示IPsec预共享密钥。记录该密钥和源NAT IP。用户界面同样也列出了一个多或多个用户他们的密码。选择一个用户，或者如果不存在任何用户，则创建一个用户。"
+
+# 7fda5d36b51847d49837befe10623588
+#: ../../networking/remote_access_vpn.rst:172
+msgid ""
+"On the Windows box, go to Control Panel, then select Network and Sharing "
+"center. Click Setup a connection or network."
+msgstr "在Windows中，进入控制面板，然后选择网络和共享中心，点击设置一个网络连接。"
+
+# da78d151c9234aed8997f0bc85337cf6
+#: ../../networking/remote_access_vpn.rst:175
+msgid "In the next dialog, select No, create a new connection."
+msgstr "在下一个对话框中，选择否，创建一个新的连接。"
+
+# 43e868088a2941f2b050d28f6420c815
+#: ../../networking/remote_access_vpn.rst:177
+msgid "In the next dialog, select Use my Internet Connection (VPN)."
+msgstr "在下一个对话框中，选择使用我的Internet连接(VPN)."
+
+# 239288f41e5547d280e2293ec8da8206
+#: ../../networking/remote_access_vpn.rst:179
+msgid ""
+"In the next dialog, enter the source NAT IP from step #1 and give the "
+"connection a name. Check Don't connect now."
+msgstr "在下一个对话框中，输入此步骤#1中的源NAT IP地址并填写连接名称。勾选现在不连接。"
+
+# 38f025d6b59c4032a92973f1c1a27c07
+#: ../../networking/remote_access_vpn.rst:183
+msgid ""
+"In the next dialog, enter the user name and password selected in step #1."
+msgstr "在下一个对话框中，输入此步骤#1中的用户名和密码。"
+
+# 65891d17f3074ed9b484f59841022124
+#: ../../networking/remote_access_vpn.rst:188
+msgid ""
+"Go back to the Control Panel and click Network Connections to see the new "
+"connection. The connection is not active yet."
+msgstr "返回控制面板并点击网络连接查看这个新的连接。但当前连接并不是活动状态。"
+
+# 90aee2a731374796ae19cb91e6c4eaca
+#: ../../networking/remote_access_vpn.rst:191
+msgid ""
+"Right-click the new connection and select Properties. In the Properties "
+"dialog, select the Networking tab."
+msgstr "在新创建的连接上点击右键并选择属性。在属性对话框中，选择网络选项卡。"
+
+# 785904429cc24b31a7cf663347b72344
+#: ../../networking/remote_access_vpn.rst:196
+msgid ""
+"In Type of VPN, choose L2TP IPsec VPN, then click IPsec settings. Select Use"
+" preshared key. Enter the preshared key from step #1."
+msgstr "在VPN类型中，选择L2TP IPsec VPN,然后点击IPsec设置，选择用户预共享密钥。并输入此步骤#1中提供的密钥。"
+
+# 3e29d7f5cd6b43428b98157632b35cfe
+#: ../../networking/remote_access_vpn.rst:199
+msgid ""
+"The connection is ready for activation. Go back to Control Panel -> Network "
+"Connections and double-click the created connection."
+msgstr "该连接已经准备好被激活。返回到控制面板 -> 网络连接，双击创建连接。"
+
+# 658b86e57b2145119bff660e836d339d
+#: ../../networking/remote_access_vpn.rst:202
+msgid "Enter the user name and password from step #1."
+msgstr "输入此步骤 #1中提供的用户名和密码。"
+
+# f28b68b93a984f618a8681036210e3b9
+#: ../../networking/remote_access_vpn.rst:206
+msgid "Using Remote Access VPN with Mac OS X"
+msgstr "在Mac OS X 中使用远程访问VPN"
+
+# 8b76f5b992cc490bad145d28495ce704
+#: ../../networking/remote_access_vpn.rst:208
+msgid ""
+"First, be sure you've configured the VPN settings in your CloudStack "
+"install. This section is only concerned with connecting via Mac OS X to your"
+" VPN."
+msgstr "首先，确保在你的CloudStack中已经设置好VPN。本章节仅涉及通过Mac OS X 连接至VPN。"
+
+# 7da87b538a3b4bd98149a9dc28b99cb5
+#: ../../networking/remote_access_vpn.rst:212
+msgid ""
+"Note, these instructions were written on Mac OS X 10.7.5. They may differ "
+"slightly in older or newer releases of Mac OS X."
+msgstr "请注意，此指南只基于Mac OS X 10.7.5 。在旧版或新版本的Mac OS X中可能会略有不同。"
+
+# 99afa11cb02448889b90260c46e6daf2
+#: ../../networking/remote_access_vpn.rst:215
+msgid "On your Mac, open System Preferences and click Network."
+msgstr "在Mac中，打开系统偏好设置然后点击网络。"
+
+# 1b60714f0b664945b51a0b61be0399a5
+#: ../../networking/remote_access_vpn.rst:217
+msgid "Make sure Send all traffic over VPN connection is not checked."
+msgstr "确保Send all traffic over VPN connection没有被选定。"
+
+# bcd319828ca0418fb3c241dfe5096e41
+#: ../../networking/remote_access_vpn.rst:219
+msgid ""
+"If your preferences are locked, you'll need to click the lock in the bottom "
+"left-hand corner to make any changes and provide your administrator "
+"credentials."
+msgstr "如果你的首选项框被锁住，你如果要做些改动需要点击底部左侧的锁按钮，并提供管理员认证。"
+
+# 4300ee6f178548d5a9905a6bbe2d9860
+#: ../../networking/remote_access_vpn.rst:223
+msgid ""
+"You will need to create a new network entry. Click the plus icon on the "
+"bottom left-hand side and you'll see a dialog that says \"Select the "
+"interface and enter a name for the new service.\" Select VPN from the "
+"Interface drop-down menu, and \"L2TP over IPSec\" for the VPN Type. Enter "
+"whatever you like within the \"Service Name\" field."
+msgstr "您将需要创建一个新的网络入口。点击底部左侧的加号图标，你会看到一个对话框，写着“选择接口并输入新服务的名称”。在接口下拉菜单中选择VPN，VPN类型为“基于IPSec的L2TP”。在“服务名称”中输入任何你喜欢的字段。"
+
+# 23650c313b074382a57881042b50304e
+#: ../../networking/remote_access_vpn.rst:229
+msgid ""
+"You'll now have a new network interface with the name of whatever you put in"
+" the \"Service Name\" field. For the purposes of this example, we'll assume "
+"you've named it \"CloudStack.\" Click on that interface and provide the IP "
+"address of the interface for your VPN under the Server Address field, and "
+"the user name for your VPN under Account Name."
+msgstr "现在你需要在\"Service Name\" 中填入新的网络接口的名称。对于这个例子，我们假设你已经把它命名为“CloudStack”。点击该接口，并在服务器地址字段中填入提供的VPN IP地址，并在账户名称中填入您的VPN用户名。"
+
+# 6b61feadee8d476583c5ac8024ecf9dc
+#: ../../networking/remote_access_vpn.rst:236
+msgid ""
+"Click Authentication Settings, and add the user's password under User "
+"Authentication and enter the pre-shared IPSec key in the Shared Secret field"
+" under Machine Authentication. Click OK."
+msgstr "点击身份验证设置，在机器验证中，用户身份验证下输入用户名和密码，在共享密钥下输入预共享IPsec密钥。点击OK。"
+
+# 82160d6db5874a5fb691804a0f4064ee
+#: ../../networking/remote_access_vpn.rst:240
+msgid ""
+"You may also want to click the \"Show VPN status in menu bar\" but that's "
+"entirely optional."
+msgstr "你也可以点击\"在菜单栏中查看VPN状态\",这完全是可选的操作。"
+
+# 7888991db08f4692af070e20a8f548e4
+#: ../../networking/remote_access_vpn.rst:243
+msgid "Now click \"Connect\" and you will be connected to the CloudStack VPN."
+msgstr "现在点击\"连接\" 你将会连接到CloudStack VPN。"
+
+# b8fcb8654d4045cabab65cc607473fa0
+#: ../../networking/remote_access_vpn.rst:249
+msgid "Setting Up a Site-to-Site VPN Connection"
+msgstr "配置站点到站点的VPN连接"
+
+# bf33833486e34298bbd54de0d5e5c883
+#: ../../networking/remote_access_vpn.rst:251
+msgid ""
+"A Site-to-Site VPN connection helps you establish a secure connection from "
+"an enterprise datacenter to the cloud infrastructure. This allows users to "
+"access the guest VMs by establishing a VPN connection to the virtual router "
+"of the account from a device in the datacenter of the enterprise. You can "
+"also establish a secure connection between two VPC setups or high "
+"availability zones in your environment. Having this facility eliminates the "
+"need to establish VPN connections to individual VMs."
+msgstr "一个站点到站点的VPN连接可以帮助你建立从云基础架构到企业内部数据中心的安全连接.这就允许一个账户从企业内部数据中心的设备连接到此账户启用VPN连接的虚拟路由器上, 从而通过VPN连接到该账户的虚拟机.你也可以在两个VPC之间或是高可用区域之间建立VPC以加强安全。这样一来，就不需要在虚拟机之间建立VPN连接的必要了。"
+
+# 4bf27ce4183e47dda88b6603d61b46b8
+#: ../../networking/remote_access_vpn.rst:260
+msgid ""
+"The difference from Remote VPN is that Site-to-site VPNs connects entire "
+"networks to each other, for example, connecting a branch office network to a"
+" company headquarters network. In a site-to-site VPN, hosts do not have VPN "
+"client software; they send and receive normal TCP/IP traffic through a VPN "
+"gateway."
+msgstr "与Remote VPN不同，Site-to-site VPNs是将两个网络相互连接。比如，将一个分支办公室的网络与总公司网络互联，Site-to-site VPN的两个主机不需要VPN客户端软件，它们通过VPN网关收发普通的TCP/IP数据包流量 。"
+
+# 153b937b1c0e4de69b3b94451840a13f
+#: ../../networking/remote_access_vpn.rst:266
+msgid "The supported endpoints on the remote datacenters are:"
+msgstr "目前支持的数据中心的终端设备是:"
+
+# 5ebb68947e8846959fdb844894eba6eb
+#: ../../networking/remote_access_vpn.rst:268
+msgid "Cisco ISR with IOS 12.4 or later"
+msgstr "Cisco ISR IOS 12.4或更新"
+
+# e3a55a3999da49baa81621a7f7ffb70a
+#: ../../networking/remote_access_vpn.rst:270
+msgid "Juniper J-Series routers with JunOS 9.5 or later"
+msgstr "Juniper J-系统 路由器 JunOS 9.5 或更新版本"
+
+# ffc402a2243c4da9bcd196372f78bf94
+#: ../../networking/remote_access_vpn.rst:272
+msgid "CloudStack virtual routers"
+msgstr "CloudStack虚拟路由器。"
+
+# af60329a6d1b421db96e66d969e7148a
+#: ../../networking/remote_access_vpn.rst:275
+msgid ""
+"In addition to the specific Cisco and Juniper devices listed above, the "
+"expectation is that any Cisco or Juniper device running on the supported "
+"operating systems are able to establish VPN connections."
+msgstr "除了上述指定的Cisco和Juniper设备, 所期望的是任何Cisco或Juniper的设备在支持的操作系统上都可以建立VPN连接."
+
+# 4e099c5b2d15403d841fca6ab971b147
+#: ../../networking/remote_access_vpn.rst:279
+msgid "To set up a Site-to-Site VPN connection, perform the following:"
+msgstr "为了建立站点到站点的VPN连接, 需要执行以下步骤:"
+
+# 9f0c55b7e3d1405ea91d412d82570573
+#: ../../networking/remote_access_vpn.rst:281
+msgid "Create a Virtual Private Cloud (VPC)."
+msgstr "创建一个虚拟私有云(VPC)."
+
+# 1cc41acb25564437bf47069632c1e47f
+#: ../../networking/remote_access_vpn.rst:283
+msgid "See \":ref:`configuring-vpc`\"."
+msgstr "参考\":ref:`configuring-vpc`\"."
+
+# 0350dab55c154adb8bfb5fc2329bc99b
+#: ../../networking/remote_access_vpn.rst:285
+msgid "Create a VPN Customer Gateway."
+msgstr "创建一个VPN客户网关."
+
+# 9e0ade3afda44783837277f292aac18e
+#: ../../networking/remote_access_vpn.rst:287
+msgid "Create a VPN gateway for the VPC that you created."
+msgstr "为你创建的VPC设定一个VPN网关."
+
+# bd574fc0e611460eb6f1cf836570d65a
+#: ../../networking/remote_access_vpn.rst:289
+msgid ""
+"Create VPN connection from the VPC VPN gateway to the customer VPN gateway."
+msgstr "从VPC的VPN网关到客户的VPN网关建立VPN连接."
+
+# 94a11afb4f284c39876ab9e7ad9b4203
+#: ../../networking/remote_access_vpn.rst:294
+msgid "Creating and Updating a VPN Customer Gateway"
+msgstr "创建和更新一个VPN客户网关."
+
+# d7741a7964f14270836f90faa50dee5e
+#: ../../networking/remote_access_vpn.rst:297
+msgid ""
+"A VPN customer gateway can be connected to only one VPN gateway at a time."
+msgstr "一个VPN客户网关在同一时间只能连接一个VPN网关。"
+
+# b0237b80ce7945038ccf7e43814bc271
+#: ../../networking/remote_access_vpn.rst:299
+msgid "To add a VPN Customer Gateway:"
+msgstr "添加 VPN 客户网关"
+
+# 101bb0d15ff04d2b833841a38622b5a3
+# 2b4e8de7b2b8461685571e9bd8677151
+#: ../../networking/remote_access_vpn.rst:305
+#: ../../networking/remote_access_vpn.rst:415
+msgid "In the Select view, select VPN Customer Gateway."
+msgstr "在选择视图里，选择VPN客户网关。"
+
+# 7731e51aab804267b5d9a1b77c2a563f
+#: ../../networking/remote_access_vpn.rst:307
+msgid "Click Add VPN Customer Gateway."
+msgstr "点击添加 VPN 客户网关。"
+
+# a28ae413767b455ba902116cbfb65b62
+#: ../../networking/remote_access_vpn.rst:309
+msgid "|addvpncustomergateway.png|"
+msgstr "|addvpncustomergateway.png|"
+
+# 4b1ee71a183a40f08f2c0f6153980745
+#: ../../networking/remote_access_vpn.rst:313
+msgid "**Name**: A unique name for the VPN customer gateway you create."
+msgstr "**名称**: 你添加的VPN客户网关的一个唯一的名称。"
+
+# 4a55d6fffb10456eb7eedd3b877f3290
+#: ../../networking/remote_access_vpn.rst:315
+msgid "**Gateway**: The IP address for the remote gateway."
+msgstr "**IP地址**: 远端网关的IP地址。"
+
+# a1719efbdbf3445e88fe8b57058e647d
+#: ../../networking/remote_access_vpn.rst:317
+msgid ""
+"**CIDR list**: The guest CIDR list of the remote subnets. Enter a CIDR or a "
+"comma-separated list of CIDRs. Ensure that a guest CIDR list is not "
+"overlapped with the VPC's CIDR, or another guest CIDR. The CIDR must be "
+"RFC1918-compliant."
+msgstr "**CIDR列表**: 远端客户子网的CIDR。输入一个CIDR或是以逗号分隔的多个CIDR。在确认客户的CIDR和VPC的CIDR或是另一个客户的CIDR不重叠冲突。CIDR的格式必须符合 RFC1918标准。"
+
+# 45e753e1aca84d72a27705c47e7359fe
+#: ../../networking/remote_access_vpn.rst:322
+msgid ""
+"**IPsec Preshared Key**: Preshared keying is a method where the endpoints of"
+" the VPN share a secret key. This key value is used to authenticate the "
+"customer gateway and the VPC VPN gateway to each other."
+msgstr "**IPsec预共享密钥**: 预共享密钥在两个端点之间共享同一个密钥。这个密钥用来在客户网关和VPN的VPN网关之间相互认证。"
+
+# 685253a274ff4f8ab93ec131da0a8e17
+#: ../../networking/remote_access_vpn.rst:328
+msgid ""
+"The IKE peers (VPN end points) authenticate each other by computing and "
+"sending a keyed hash of data that includes the Preshared key. If the "
+"receiving peer is able to create the same hash independently by using its "
+"Preshared key, it knows that both peers must share the same secret, thus "
+"authenticating the customer gateway."
+msgstr "Internet密钥交换协议（IKE）匹配点 ( VPN 端点 ) 通过计算并发送包含预共享密钥的哈希键值来进行相互验证。如果收接点通过自己的预共享密钥算出同一个键值的话，这就说明两个点是用的同一个密钥，相互之间认证通过，形成匹配。"
+
+# 99c6b3d0d9b644ac963db1bbbec803aa
+#: ../../networking/remote_access_vpn.rst:335
+msgid ""
+"**IKE Encryption**: The Internet Key Exchange (IKE) policy for phase-1. The "
+"supported encryption algorithms are AES128, AES192, AES256, and 3DES. "
+"Authentication is accomplished through the Preshared Keys."
+msgstr "**IKE 加密**: Internet密钥交换协议(IKE)第一阶段（phase-1）策略。支持的加密算法包括 AES128, AES192, AES256和3DES.。认证通过预共享密钥完成。"
+
+# 5fc1a26b6376451e99e9e5edb6e43b8c
+#: ../../networking/remote_access_vpn.rst:341
+msgid ""
+"The phase-1 is the first phase in the IKE process. In this initial "
+"negotiation phase, the two VPN endpoints agree on the methods to be used to "
+"provide security for the underlying IP traffic. The phase-1 authenticates "
+"the two VPN gateways to each other, by confirming that the remote gateway "
+"has a matching Preshared Key."
+msgstr "phase-1是IKE过程的第一阶段。在这个开始的协商阶段，两个VPN端点在将底层IP流量加密安全的方法上取得一致。第一阶段认证通过的条件是：两个VPN网关之间使用的是同一个预定义密钥。"
+
+# 4a50daea38b94c4c8f566640f9423d59
+#: ../../networking/remote_access_vpn.rst:347
+msgid ""
+"**IKE Hash**: The IKE hash for phase-1. The supported hash algorithms are "
+"SHA1 and MD5."
+msgstr "**IKE 哈希**: IKE第一阶段（ phase-1）哈希散列使用的算法。支持SHA1 和 MD5."
+
+# 164ad3cc6c1d4be09637856b2caebc73
+#: ../../networking/remote_access_vpn.rst:350
+msgid ""
+"**IKE DH**: A public-key cryptography protocol which allows two parties to "
+"establish a shared secret over an insecure communications channel. The "
+"1536-bit Diffie-Hellman group is used within IKE to establish session keys. "
+"The supported options are None, Group-5 (1536-bit) and Group-2 (1024-bit)."
+msgstr "**IKE DH（Diffie-Hellman组）**: IKE的DH加密协议，可以在不安全的连接上确保共享KEY的安全。1536位的DH组用在IKE中用来建立会话KEYS。在这里，支持的选项是 None, Group-5 (1536-bit) 和 Group-2 (1024-bit)."
+
+# 7f48a32285424744aed43ca25afe1013
+#: ../../networking/remote_access_vpn.rst:356
+msgid ""
+"**ESP Encryption**: Encapsulating Security Payload (ESP) algorithm within "
+"phase-2. The supported encryption algorithms are AES128, AES192, AES256, and"
+" 3DES."
+msgstr "**ESP 加密**: 封装安全有效负荷（Encapsulating Security Payload,ESP）算法是发生在第二阶段(phase-2)。其支持的加密算法包括 AES128, AES192, AES256, 和 3DES。"
+
+# b406299f4fea47069d76bb649b8708f9
+#: ../../networking/remote_access_vpn.rst:361
+msgid ""
+"The phase-2 is the second phase in the IKE process. The purpose of IKE "
+"phase-2 is to negotiate IPSec security associations (SA) to set up the IPSec"
+" tunnel. In phase-2, new keying material is extracted from the Diffie-"
+"Hellman key exchange in phase-1, to provide session keys to use in "
+"protecting the VPN data flow."
+msgstr "phase-2是IKE过程的第二阶段，其目标是协助IPSec安全关联 (SA) 以建立IPSec通道。在 phase-2阶段，会利用 phase-1阶段建立好的DH安全协议方法来交换新的密钥。"
+
+# a27571240d7c4f3c9acf4a0a4aa3b628
+#: ../../networking/remote_access_vpn.rst:367
+msgid ""
+"**ESP Hash**: Encapsulating Security Payload (ESP) hash for phase-2. "
+"Supported hash algorithms are SHA1 and MD5."
+msgstr "**ESP哈希散列**:phase-2支持的封装安全有效负荷(Encapsulating Security Payload,ESP)哈希算法包括：SHA1 和MD5."
+
+# 4b7ceba042f249029e0dbf978aa690d3
+#: ../../networking/remote_access_vpn.rst:370
+msgid ""
+"**Perfect Forward Secrecy**: Perfect Forward Secrecy (or PFS) is the "
+"property that ensures that a session key derived from a set of long-term "
+"public and private keys will not be compromised. This property enforces a "
+"new Diffie-Hellman key exchange. It provides the keying material that has "
+"greater key material life and thereby greater resistance to cryptographic "
+"attacks. The available options are None, Group-5 (1536-bit) and Group-2 "
+"(1024-bit). The security of the key exchanges increase as the DH groups grow"
+" larger, as does the time of the exchanges."
+msgstr "**Perfect forward secrecy(完全正向保密,PFS) **: PFS的性质是确保来自一组的长期的公共密钥和私人密钥之间的会话密钥不会妥协失效。PFS会促使一组新的DH KEY发生交换。这组新KEY具有更长的生命周期因此可以抵制更强大的功击。DH的可用选项是 None, Group-5 (1536-bit)和 Group-2 (1024-bit). 当新KEY交换之后，DH组会变得更大。"
+
+# 31cd21a987c94c2593fa18b480d5655a
+#: ../../networking/remote_access_vpn.rst:381
+msgid ""
+"When PFS is turned on, for every negotiation of a new phase-2 SA the two "
+"gateways must generate a new set of phase-1 keys. This adds an extra layer "
+"of protection that PFS adds, which ensures if the phase-2 SA's have expired,"
+" the keys used for new phase-2 SA's have not been generated from the current"
+" phase-1 keying material."
+msgstr "当PFS打开后，两个网关之间的新的phase-2 SA协商都会产生新的phase-1的一组KEY，这就会导致增加一个额外的层。这个层的作用是保证即使phase-2 SA失效过期，其KEY也不会由phase-1生成。"
+
+# c4fac70acb7546528e8f03a69aec87d6
+#: ../../networking/remote_access_vpn.rst:387
+msgid ""
+"**IKE Lifetime (seconds)**: The phase-1 lifetime of the security association"
+" in seconds. Default is 86400 seconds (1 day). Whenever the time expires, a "
+"new phase-1 exchange is performed."
+msgstr "**IKE 存活期(秒)**: SA的phase-1的存活期。默认是86400 秒 (1 天).当这个时间过了之后，会发生一次新的 phase-1 KEY交换。"
+
+# 253e1c3775154909922b7f978944cd3e
+#: ../../networking/remote_access_vpn.rst:391
+msgid ""
+"**ESP Lifetime (seconds)**: The phase-2 lifetime of the security association"
+" in seconds. Default is 3600 seconds (1 hour). Whenever the value is "
+"exceeded, a re-key is initiated to provide a new IPsec encryption and "
+"authentication session keys."
+msgstr "**ESP存活期 (秒)**:SA的 phase-2存活期。默认为 3600 秒(1 小时). 当过了这个时间之后，会有一个新的KEY初始化，用来加密和认证 IPsec的会话KEY。"
+
+# c0c484db7f344e408d168f25bb654809
+#: ../../networking/remote_access_vpn.rst:396
+msgid ""
+"**Dead Peer Detection**: A method to detect an unavailable Internet Key "
+"Exchange (IKE) peer. Select this option if you want the virtual router to "
+"query the liveliness of its IKE peer at regular intervals. It's recommended "
+"to have the same configuration of DPD on both side of VPN connection."
+msgstr "**死亡匹配点检测**:这是一种检测不可用IKE节点的方法。如果你希望虚拟路由器随时测试IKE节点的存活情况，选择了这个选项。 一般来说，最好在VPN连接的两端都同时配置DPD(Dead Peer Detectio)."
+
+# bbbaed88ff1d435c8172e82d1ba38621
+#: ../../networking/remote_access_vpn.rst:406
+msgid "Updating and Removing a VPN Customer Gateway"
+msgstr "更新和删除一个VPN客户网关."
+
+# dce2c8dc1af941d3995eccd689185d2f
+#: ../../networking/remote_access_vpn.rst:408
+msgid ""
+"You can update a customer gateway either with no VPN connection, or related "
+"VPN connection is in error state."
+msgstr "你可以更新一个客户网关：即可以从无到有新建一个VPN，或是将有错误提示的VPN改正。"
+
+# a2663d4c4c664967b66aed432bc15feb
+#: ../../networking/remote_access_vpn.rst:417
+msgid "Select the VPN customer gateway you want to work with."
+msgstr "选择您要操作的客户VPN连接。"
+
+# a7ded8e5a4764341a0616505650a00e8
+#: ../../networking/remote_access_vpn.rst:419
+msgid ""
+"To modify the required parameters, click the Edit VPN Customer Gateway "
+"button |vpn-edit-icon.png|"
+msgstr ""
+
+# 756841a8fa024fd8a5c97c8f30e876d3
+#: ../../networking/remote_access_vpn.rst:422
+msgid ""
+"To remove the VPN customer gateway, click the Delete VPN Customer Gateway "
+"button |delete.png|"
+msgstr "删除一个客户VPN网关，点击删除客户VPN网关按钮。 |delete.png|"
+
+# b8b2a50b82054314966bddcea5e58624
+#: ../../networking/remote_access_vpn.rst:429
+msgid "Creating a VPN gateway for the VPC"
+msgstr "为VPC创建一个VPN网关"
+
+# 55ffd9d38baf4689915216b245eb0345
+# 9dffc7abb0334653a04e9da28c3986eb
+# cafe1c918b254231856621d595a969ea
+# 629408b6b4d44c488f179e9d12c9d1c8
+# 12f2c2ca637145198bd85e6aefc78803
+# 322ff7890b6647d89fc773f95de5ca97
+# b5eb13586b2d401b9224cc304d4d596e
+#: ../../networking/remote_access_vpn.rst:440
+#: ../../networking/remote_access_vpn.rst:501
+#: ../../networking/remote_access_vpn.rst:633
+#: ../../networking/virtual_private_cloud_config.rst:671
+#: ../../networking/virtual_private_cloud_config.rst:738
+#: ../../networking/virtual_private_cloud_config.rst:857
+#: ../../networking/virtual_private_cloud_config.rst:1291
+msgid ""
+"Click the Configure button of the VPC to which you want to deploy the VMs."
+msgstr "点击要部署虚机的VPC的配置按钮。"
+
+# 3ede94e26b2243618297004100dde13e
+# 2f52e248552b455a87f010302f709dad
+# 053eb6822dcf4582b9bba73ede381afb
+# d368f1f8019d471eb6596301beba362c
+# dfea3c0fff89489eac70a967cc49c5aa
+# 73059e34302c43d1a5a4c816f43b9382
+# fb07c649ea2b4a768d6e5716e8030063
+# 28f7d7ee821449b29c5cd912fde10a27
+#: ../../networking/remote_access_vpn.rst:443
+#: ../../networking/remote_access_vpn.rst:504
+#: ../../networking/remote_access_vpn.rst:636
+#: ../../networking/virtual_private_cloud_config.rst:504
+#: ../../networking/virtual_private_cloud_config.rst:741
+#: ../../networking/virtual_private_cloud_config.rst:799
+#: ../../networking/virtual_private_cloud_config.rst:860
+#: ../../networking/virtual_private_cloud_config.rst:1294
+msgid ""
+"The VPC page is displayed where all the tiers you created are listed in a "
+"diagram."
+msgstr "系统会显示VPC页面，您创建的所有层都列在图中。"
+
+# bb47b6a4c9894b0ba98c007547e23a7b
+# 5f44ee9703334af187a5f781a5bdd3ca
+# 90eeedf47dda43f69ca4cd79e42918d7
+#: ../../networking/remote_access_vpn.rst:468
+#: ../../networking/remote_access_vpn.rst:531
+#: ../../networking/remote_access_vpn.rst:663
+msgid "Select Site-to-Site VPN."
+msgstr "选择点对点VPN"
+
+# 3904e2f97d404bd0ac8c9e9461127c9c
+#: ../../networking/remote_access_vpn.rst:470
+msgid ""
+"If you are creating the VPN gateway for the first time, selecting Site-to-"
+"Site VPN prompts you to create a VPN gateway."
+msgstr "如果您是第一次创建VPN网关，选择点对点VPN会提示您创建一个VPN网关。"
+
+# 58e6c2a9a3ca472c8470f2da068490b4
+#: ../../networking/remote_access_vpn.rst:473
+msgid "In the confirmation dialog, click Yes to confirm."
+msgstr "在信息确认对话框，点击“是”。"
+
+# 0dcce7d9ba7e44fea93fd343b6eb8ccd
+#: ../../networking/remote_access_vpn.rst:475
+msgid ""
+"Within a few moments, the VPN gateway is created. You will be prompted to "
+"view the details of the VPN gateway you have created. Click Yes to confirm."
+msgstr "过一会儿，VPN网关就创建出来了。系统会提示您查看VPN网关的详细信息，请点击“是”。"
+
+# 08c91c396238462eb6a6a86c3bc34356
+#: ../../networking/remote_access_vpn.rst:479
+msgid "The following details are displayed in the VPN Gateway page:"
+msgstr "VPN网关页面会显示以下详细信息："
+
+# a77fc54a7c8146a3ac276762ce040121
+#: ../../networking/remote_access_vpn.rst:483
+msgid "Account"
+msgstr "帐号"
+
+# 7d5a08b580ca444fa94ea41cf933bbed
+#: ../../networking/remote_access_vpn.rst:485
+msgid "Domain"
+msgstr "域名"
+
+# a9bedddab6d94613aa7949d22530c563
+#: ../../networking/remote_access_vpn.rst:489
+msgid "Creating a VPN Connection"
+msgstr "新建vpn连接"
+
+# eb9ff504d03f4098abe385052da3a163
+#: ../../networking/remote_access_vpn.rst:491
+msgid "CloudStack supports creating up to 8 VPN connections."
+msgstr "CloudStack最多支持建立8个VPN连接。"
+
+# 4106c6c68d6d468fa69e8066df52a37d
+#: ../../networking/remote_access_vpn.rst:499
+msgid "All the VPCs that you create for the account are listed in the page."
+msgstr "页面上列出了该账号下所有的VPC。"
+
+# 30ef75902e6a416e943de29ba0ae78f2
+# 2ea0f0278379492ba4ae3fe6df1acc1e
+# 9120ca60dcc143a28655716ade74dd8d
+#: ../../networking/remote_access_vpn.rst:507
+#: ../../networking/remote_access_vpn.rst:639
+#: ../../networking/virtual_private_cloud_config.rst:507
+msgid "Click the Settings icon."
+msgstr "点击设置图标。"
+
+# c17fddae85054e48acc62417d618005b
+# d51c787e2c3641bda74032c8dda674a2
+#: ../../networking/remote_access_vpn.rst:533
+#: ../../networking/remote_access_vpn.rst:665
+msgid "The Site-to-Site VPN page is displayed."
+msgstr "系统会显示点对点VPN页面。"
+
+# d20933656e614d3c90bbeca3c9dfa1e8
+# ae7c48ded27f46fba258b7713abe8020
+#: ../../networking/remote_access_vpn.rst:535
+#: ../../networking/remote_access_vpn.rst:667
+msgid ""
+"From the Select View drop-down, ensure that VPN Connection is selected."
+msgstr "在选择视图下拉框，请确保选择VPN连接。"
+
+# e805d37fb5de4010a4e653ecc10fe88f
+#: ../../networking/remote_access_vpn.rst:538
+msgid "Click Create VPN Connection."
+msgstr "选择创建vpn连接按钮"
+
+# 6461a9409d0d43af95085f7592764ec5
+#: ../../networking/remote_access_vpn.rst:540
+msgid "The Create VPN Connection dialog is displayed:"
+msgstr "系统会显示创建VPN连接对话框："
+
+# 302fc42f8855480ea855ba83253ae510
+#: ../../networking/remote_access_vpn.rst:542
+msgid "|createvpnconnection.png|"
+msgstr "|createvpnconnection.png|"
+
+# 256fd2eeb83d4c8ca42223952cda2eaa
+#: ../../networking/remote_access_vpn.rst:544
+msgid "Select the desired customer gateway."
+msgstr "选择想要的用户网关。"
+
+# 1216cafe939448ce89002732610150f9
+#: ../../networking/remote_access_vpn.rst:546
+msgid ""
+"Select Passive if you want to establish a connection between two VPC virtual"
+" routers."
+msgstr "如果你希望在两个VPC虚拟路由器之间建立连接，选择被动模式。"
+
+# 31801a53933d4e8e98ac8b775c9547ad
+#: ../../networking/remote_access_vpn.rst:549
+msgid ""
+"If you want to establish a connection between two VPC virtual routers, "
+"select Passive only on one of the VPC virtual routers, which waits for the "
+"other VPC virtual router to initiate the connection. Do not select Passive "
+"on the VPC virtual router that initiates the connection."
+msgstr "如果你希望在两个VPC虚拟路由器之间建立连接，需要等待另一个虚拟路由器来初始化连接，则只有其中一个虚拟器上选择被动模式。在这种情况下，不要在初始化连接的虚拟路由器上选择被动模式。"
+
+# 06301a1ae56d4aa0829075cea0e779b2
+#: ../../networking/remote_access_vpn.rst:557
+msgid "Within a few moments, the VPN Connection is displayed."
+msgstr "过一会儿，系统会显示该VPN连接。"
+
+# aa7133cb7a2f415180d09d0a134d39b2
+#: ../../networking/remote_access_vpn.rst:559
+msgid "The following information on the VPN connection is displayed:"
+msgstr "VPN连接信息"
+
+# 0c0a058f5bba400ba3f349f62ea660f1
+#: ../../networking/remote_access_vpn.rst:565
+msgid "State"
+msgstr "状态 "
+
+# c7cdf1f2c13b4df7852fb798ffb852f1
+#: ../../networking/remote_access_vpn.rst:567
+msgid "IPSec Preshared Key"
+msgstr "IPSec 预共享密钥"
+
+# 97c84bf1a75c4e84a20bda2e28f8dd99
+#: ../../networking/remote_access_vpn.rst:569
+msgid "IKE Policy"
+msgstr "IKE策略"
+
+# 7d9d2e44ca2e45118dd87874aab3660c
+#: ../../networking/remote_access_vpn.rst:571
+msgid "ESP Policy"
+msgstr "ESP策略"
+
+# 53ad2d1f828e40a5a6e793ae3c464cf6
+#: ../../networking/remote_access_vpn.rst:575
+msgid "Site-to-Site VPN Connection Between VPC Networks"
+msgstr "在VPC网络之间的站点的VPN连接"
+
+# bfe3ddb6f0054692ade09235d6409226
+#: ../../networking/remote_access_vpn.rst:577
+msgid ""
+"CloudStack provides you with the ability to establish a site-to-site VPN "
+"connection between CloudStack virtual routers. To achieve that, add a "
+"passive mode Site-to-Site VPN. With this functionality, users can deploy "
+"applications in multiple Availability Zones or VPCs, which can communicate "
+"with each other by using a secure Site-to-Site VPN Tunnel."
+msgstr "CloudStack可以在虚拟路由器之间部署站点到站点的VPN连接，这需要添加一个被动模式的站点到站点VPN。有了这个功能之后，用户就可以在多个区域或VPC之间通过安全的VPN通道互联。"
+
+# 4d7b48c89729493fab30a6c8fa3e3d8a
+#: ../../networking/remote_access_vpn.rst:583
+msgid "This feature is supported on all the hypervisors."
+msgstr "这个特性支持所有类型的HYPERVISOR."
+
+# 63d33594095642d6bd759d685c327728
+#: ../../networking/remote_access_vpn.rst:585
+msgid "Create two VPCs. For example, VPC A and VPC B."
+msgstr "创建两个VPC。比如，VPC A和VPC B。"
+
+# f38ada5b2bf347699a13c440cdbb6d6d
+#: ../../networking/remote_access_vpn.rst:587
+msgid "For more information, see \":ref:`configuring-vpc`\"."
+msgstr "更多信息，参考\":ref:`configuring-vpc`\"."
+
+# 9725f2c0a7804cd08dabeb07ccced69e
+#: ../../networking/remote_access_vpn.rst:589
+msgid "Create VPN gateways on both the VPCs you created."
+msgstr "在创建的VPC两边都添加VPN网关。"
+
+# 863b39380dc440b39636aefc3f305286
+#: ../../networking/remote_access_vpn.rst:591
+msgid ""
+"For more information, see `\"Creating a VPN gateway for the VPC\" "
+"<#creating-a-vpn-gateway-for-the-vpc>`_."
+msgstr "更多信息，参考 `\"为VPC创建VPN网关\" <#creating-a-vpn-gateway-for-the-vpc>`_."
+
+# 80e6cc23902e4983926d330301305245
+#: ../../networking/remote_access_vpn.rst:594
+msgid "Create VPN customer gateway for both the VPCs."
+msgstr "在VPC两边都创建VPN客户网关。"
+
+# 8b053f18f0cf45d7a54c9a55525e51d5
+#: ../../networking/remote_access_vpn.rst:596
+msgid ""
+"For more information, see `\"Creating and Updating a VPN Customer Gateway\" "
+"<#creating-and-updating-a-vpn-customer-gateway>`_."
+msgstr "更多信息，参考`\"创建和更新VPN客户网关\" <#creating-and-updating-a-vpn-customer-gateway>`_."
+
+# e62bfd0cb16b4506af656ac300d2b9d6
+#: ../../networking/remote_access_vpn.rst:599
+msgid "Enable a VPN connection on VPC A in passive mode."
+msgstr "在VPC A这边启用VPN的被动连接模式。"
+
+# e9a973fc175a4c358a0961c603185a9b
+#: ../../networking/remote_access_vpn.rst:601
+msgid ""
+"For more information, see `\"Creating a VPN Connection\" <#creating-a-vpn-"
+"connection>`_."
+msgstr "更多信息，请参阅 `\"创建VPN连接\" <#creating-a-vpn-connection>`_。"
+
+# 077205cc874949ebb23a94463f757867
+#: ../../networking/remote_access_vpn.rst:604
+msgid ""
+"Ensure that the customer gateway is pointed to VPC B. The VPN connection is "
+"shown in the Disconnected state."
+msgstr "确保客户网关指向VPC B。这个VPN当前显示的是未连接状态。"
+
+# a1f2ec5982ca4ee88e0e1b6d64a341e4
+#: ../../networking/remote_access_vpn.rst:607
+msgid "Enable a VPN connection on VPC B."
+msgstr "在VPC B上启用VPN连接。"
+
+# 9b111a2dd2fb47d384d121a954fb00d0
+#: ../../networking/remote_access_vpn.rst:609
+msgid ""
+"Ensure that the customer gateway is pointed to VPC A. Because virtual router"
+" of VPC A, in this case, is in passive mode and is waiting for the virtual "
+"router of VPC B to initiate the connection, VPC B virtual router should not "
+"be in passive mode."
+msgstr "确保客户网关指向VPC A。在这个示例里，因为VPC A的虚拟路由器是处于被动模式且等待着VPC B进行初始化连接，所以VPC B的虚拟路由器不要设置为被动模式。"
+
+# 6f48c7f01a334934959f0048f9a19913
+#: ../../networking/remote_access_vpn.rst:614
+msgid "The VPN connection is shown in the Disconnected state."
+msgstr "VPN连接当前显示为未连接状态。"
+
+# f9289b1f358541dcbbea60dd60547408
+#: ../../networking/remote_access_vpn.rst:616
+msgid ""
+"Creating VPN connection on both the VPCs initiates a VPN connection. Wait "
+"for few seconds. The default is 30 seconds for both the VPN connections to "
+"show the Connected state."
+msgstr "VPC两边的VPN会进行初始化连接。默认为30秒之后，两边VPN都会显示为已连接状态。"
+
+# 9fe12894f28c427a9daba08709f4326d
+#: ../../networking/remote_access_vpn.rst:622
+msgid "Restarting and Removing a VPN Connection"
+msgstr "VPN连接的重启和删除"
+
+# 4f1aa09db210412ca829b0fadcbc3175
+#: ../../networking/remote_access_vpn.rst:670
+msgid "All the VPN connections you created are displayed."
+msgstr "系统会显示创建VPN连接对话框："
+
+# 17e6855dfa4241a58cce788d5d96a057
+#: ../../networking/remote_access_vpn.rst:672
+msgid "Select the VPN connection you want to work with."
+msgstr "选择您要操作的VPN连接。"
+
+# bc52370e920b4f288050d7fcf2c623f4
+#: ../../networking/remote_access_vpn.rst:674
+msgid "The Details tab is displayed."
+msgstr "系统显示详细信息页。"
+
+# dd3715695c204665987222ab000106cd
+#: ../../networking/remote_access_vpn.rst:676
+msgid ""
+"To remove a VPN connection, click the Delete VPN connection button |remove-"
+"vpn.png|"
+msgstr "删除一个VPN连接，点击删除VPN连接按钮。 |remove-vpn.png|"
+
+# 4b987b9761934af19b5d8a4be76875a5
+#: ../../networking/remote_access_vpn.rst:679
+msgid ""
+"To restart a VPN connection, click the Reset VPN connection button present "
+"in the Details tab. |reset-vpn.png|"
+msgstr "要重启VPN连接，请点击详细信息页的重置VPN连接按钮。 |reset-vpn.png|"
+
+# 1280b685b60c4cd9b6c84035e7c3ff2a
+#: ../../networking/inter_vlan_routing.rst:18
+msgid "About Inter-VLAN Routing (nTier Apps)"
+msgstr "关于vlan间路由(多层应用)"
+
+# be2045156b3041218bc42ecd27d7d6f0
+#: ../../networking/inter_vlan_routing.rst:20
+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 the VMs. In effect, "
+"you can segment VMs by means of VLANs into different networks that can host "
+"multi-tier applications, such as Web, Application, or Database. Such "
+"segmentation by means of VLANs logically separate application VMs for higher"
+" security and lower broadcasts, while remaining physically connected to the "
+"same device."
+msgstr "vlan间路由(多层应用)提供了在vlan间通过流量路由的功能。这个特性使你能够j建立私有云(vpc)，独立分割的云，可容纳多层应用程序。这些层被部署在不同的VLAN，可以互相沟通。您提供的VLAN层的创建和部署虚拟机可以在不同的层上。VLAN连接到一个虚拟路由器，这有利于虚拟机之间的通信。实际上，你可以通过不同定义的vlan来分割你的虚拟机到不同网络，以便承担多层应用，如Web，应用程序或数据库的虚拟机。通过VLAN的逻辑上独立的应用程序的虚拟具有较高的安全性和较低的广播，同时任然物理连接到同一设备。"
+
+# ee648742bfb3421f8a3889c2349f279b
+#: ../../networking/inter_vlan_routing.rst:33
+msgid "This feature is supported on XenServer, KVM, and VMware hypervisors."
+msgstr "在 XenServer ,KVM和 VMware hypervisors支持这个特性"
+
+# ef162a16526641098e51a139989ae97e
+#: ../../networking/inter_vlan_routing.rst:35
+msgid "The major advantages are:"
+msgstr "主要的优势为："
+
+# 3e6de8dbeba5419abdb2b03019116141
+#: ../../networking/inter_vlan_routing.rst:37
+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 "管理可以部署一个vlans集，同时运行用户部署虚拟机在这些vlan上。从预先指定的vlan集中随机的为租户分配一个来宾vlan.租户处于同一层的所有vm处于分配给这个租户的来宾vlan."
+
+# bc8ba74b90594f12a5fd5677cc9ff6d1
+#: ../../networking/inter_vlan_routing.rst:43
+msgid ""
+"A VLAN allocated for an account cannot be shared between multiple accounts."
+msgstr "一个租户分配到的vlan不能被多个租户共享"
+
+# 1ab1ca8e96254434870948d662709b43
+#: ../../networking/inter_vlan_routing.rst:45
+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 "管理员允许所有用户创建自己的vpc,并部署应用。这个场景中，租户的虚拟机被部署到改租户的分配到的vlan中"
+
+# a3116bd8472e48a7aa7cda71b97e27cc
+#: ../../networking/inter_vlan_routing.rst:49
+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 "管理员和用户都可以创建多个vpcs.当第一个虚拟机被部署到该层时候，一个来宾网络nic插入到这个vpc虚拟路由器上"
+
+# 6fd43509fad74559adbc29b02d394dc9
+#: ../../networking/inter_vlan_routing.rst:53
+msgid ""
+"The administrator can create the following gateways to send to or receive "
+"traffic from the VMs:"
+msgstr "管理员创建网关用接受和发送来自vm的流量："
+
+# 8ddc983de3d241f09f98b725eb5816b9
+#: ../../networking/inter_vlan_routing.rst:56
+msgid ""
+"**VPN Gateway**: For more information, see `\"Creating a VPN gateway for the"
+" VPC\" <#creating-a-vpn-gateway-for-the-vpc>`_."
+msgstr "**VPN网关**:更多信息，参考 `\"为VPC创建VPN网关\" <#creating-a-vpn-gateway-for-the-vpc>`_."
+
+# 61e9f85faff44050a4964c4318e14c71
+#: ../../networking/inter_vlan_routing.rst:59
+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 "**公网网关**：当为vpc创建一个虚拟路由器时，这个vpc的公共网关就添加到虚拟路由器当中。公共网关还没有暴露到最终用户。你不允许其列出，也不允许建立任何静态路由。"
+
+# b56703bb9e304d9eb985cf50d8467b88
+#: ../../networking/inter_vlan_routing.rst:64
+msgid ""
+"**Private Gateway**: For more information, see \":ref:`adding-priv-gw-"
+"vpc`\"."
+msgstr "**私有网关**: 更多信息，参考 \":ref:`adding-priv-gw-vpc`\"."
+
+# 971a020719584df99604941837f413e9
+#: ../../networking/inter_vlan_routing.rst:66
+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 "管理员和用户可以创建各种可能的目的地的网关组合。但是，在部署中每种类型只能有一个网关。"
+
+# a959d3a87f854875b155e4dd0378bc58
+#: ../../networking/inter_vlan_routing.rst:70
+msgid "For example:"
+msgstr "例如："
+
+# c8562933cf3a49dabea40ebda77c173e
+#: ../../networking/inter_vlan_routing.rst:72
+msgid ""
+"**VLANs and Public Gateway**: For example, an application is deployed in the"
+" cloud, and the Web application VMs communicate with the Internet."
+msgstr "**VLAN和公网网关**: 比如，在云中部署了一个应用，并且这个web应用所在的虚拟机要和因特网通信。"
+
+# 9a0414207cf1455fa28030b70576f628
+#: ../../networking/inter_vlan_routing.rst:76
+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 "**VLANs, VPN网关和公网网关**: 比如, 云中部署了一个应用;部署这个web应用的虚拟机要和因特网通信; 并且数据库虚拟要个先前提到的设备通信"
+
+# 8534c0f613cb4afd87cee4abbbeb1864
+#: ../../networking/inter_vlan_routing.rst:81
+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 "管理员可以在虚拟路由器定义一个访问控制列表(ACL)用于过滤vlan或者因特网和vlan直接的流量。你可定义基于CIDR,端口范围，协议，类型代码(如果选用ICPM协议)和进出流量的acl"
+
+# dbc5184ebe294b3c978a2597145d1afc
+#: ../../networking/inter_vlan_routing.rst:87
+msgid ""
+"The following figure shows the possible deployment scenarios of a Inter-VLAN"
+" setup:"
+msgstr "下图显示了可能的部署一个VLAN间的场景设置的："
+
+# 7b6b27d712ab4049bb9e18da1df3f10f
+#: ../../networking/inter_vlan_routing.rst:90
+msgid "|mutltier.png|"
+msgstr "|mutltier.png|"
+
+# a73c0ccfe9e242bbafc920ed4db89f8c
+#: ../../networking/inter_vlan_routing.rst:92
+msgid ""
+"To set up a multi-tier Inter-VLAN deployment, see \":ref:`configuring-"
+"vpc`\"."
+msgstr "要建立一个多层次的跨VLAN部署，请参考\":ref:`configuring-vpc`\"."
+
+# 68230541a8c04698a2cd4782fa199025
+#: ../../networking/virtual_private_cloud_config.rst:20
+msgid "Configuring a Virtual Private Cloud"
+msgstr "配置一个虚拟私有云（VPC）"
+
+# c96dce204b9449f096ddff43e7c501e4
+#: ../../networking/virtual_private_cloud_config.rst:23
+msgid "About Virtual Private Clouds"
+msgstr "关于虚拟私有云（VPC）"
+
+# 39a15c9ebdbf402189072d4ad538b511
+#: ../../networking/virtual_private_cloud_config.rst:25
+msgid ""
+"CloudStack Virtual Private Cloud is a private, isolated part of CloudStack. "
+"A VPC can have its own virtual network topology that resembles a traditional"
+" physical network. You can launch VMs in the virtual network that can have "
+"private addresses in the range of your choice, for example: 10.0.0.0/16. You"
+" can define network tiers within your VPC network range, which in turn "
+"enables you to group similar kinds of instances based on IP address range."
+msgstr "CloudStackVPC是CloudStack云中私有并隔离的部分。一个VPC可以使用自己的虚拟网络拓扑来组建传统物理网络。在这个虚拟网络中，您创建的虚机的私网地址可以由您自主选择IP范围，例如10.0.0.0/16。您可以在VPC网络范围内定义多个网络层，这些层可以让你将类似的虚机按IP地址范围分组。"
+
+# 52f1ec4df5f14d00acc410893a48cd12
+#: ../../networking/virtual_private_cloud_config.rst:33
+msgid ""
+"For example, if a VPC has the private range 10.0.0.0/16, its guest networks "
+"can have the network ranges 10.0.1.0/24, 10.0.2.0/24, 10.0.3.0/24, and so "
+"on."
+msgstr "例如：一个VPC的私有地址范围是10.0.0.0/16，其中的用户网络的地址范围可以分别是10.0.1.0/24、10.0.2.0/24、10.0.3.0/24等等。"
+
+# c427f4f401964436adf6600e085f1c73
+#: ../../networking/virtual_private_cloud_config.rst:39
+msgid "Major Components of a VPC"
+msgstr ""
+
+# aa65d02ab49c4593ab9a6304e97b0499
+#: ../../networking/virtual_private_cloud_config.rst:41
+msgid "A VPC is comprised of the following network components:"
+msgstr "VPC主要由以下网络组件构成："
+
+# 6ce250346a5b4839af2f807498d27a93
+#: ../../networking/virtual_private_cloud_config.rst:43
+msgid ""
+"**VPC**: A VPC acts as a container for multiple isolated networks that can "
+"communicate with each other via its virtual router."
+msgstr "**VPC**：一个VPC是多个隔离网络的容器，隔离网络间可以通过VPC的虚拟路由器互通。"
+
+# bf8dcbee37f94f398e40dcc29aa1b1f2
+#: ../../networking/virtual_private_cloud_config.rst:46
+msgid ""
+"**Network Tiers**: Each tier acts as an isolated network with its own VLANs "
+"and CIDR list, where you can place groups of resources, such as VMs. The "
+"tiers are segmented by means of VLANs. The NIC of each tier acts as its "
+"gateway."
+msgstr "**网络层**：每个层是一个拥有各自VLAN和CIDR的隔离网络。您可以在层内放置VM等各种资源组。层与层之间通过VLAN方式隔离。VPC虚拟路由器在每个层中的网卡是该层的网关。"
+
+# 85c01a3feddd4eefa12e8569dc29abdb
+#: ../../networking/virtual_private_cloud_config.rst:51
+msgid ""
+"**Virtual Router**: A virtual router is automatically created and started "
+"when you create a VPC. The virtual router connect the tiers and direct "
+"traffic among the public gateway, the VPN gateways, and the NAT instances. "
+"For each tier, a corresponding NIC and IP exist in the virtual router. The "
+"virtual router provides DNS and DHCP services through its IP."
+msgstr "**虚拟路由器**：创建VPC时会自动创建并启动一个虚拟路由器。该虚拟路由器连接了各层，并负责各层与公网网关、VPN网关和NAT实例间的网络流量。对于每个层，该虚拟路由器都会有对应的网卡和IP，并通过该IP提供DNS和DHCP服务。"
+
+# 084d9e9386154de29f7c85e78edcbddf
+#: ../../networking/virtual_private_cloud_config.rst:58
+msgid ""
+"**Public Gateway**: The traffic to and from the Internet routed to the VPC "
+"through the public gateway. In a VPC, the public gateway is not exposed to "
+"the end user; therefore, static routes are not support for the public "
+"gateway."
+msgstr "**公网网关**：VPC进出互联网的流量会走公网网关。VPC中的公网网关不暴露给最终用户，因此公网网关上不支持静态路由。"
+
+# 0a67aeaa8469476786141e2d15792113
+#: ../../networking/virtual_private_cloud_config.rst:63
+msgid ""
+"**Private Gateway**: All the traffic to and from a private network routed to"
+" the VPC through the private gateway. For more information, see \":ref"
+":`adding-priv-gw-vpc`\"."
+msgstr "**私有网关**：VPC进出某个私有网络的流量通过私有网关。更多信息，请查阅 \":ref:`adding-priv-gw-vpc`\"."
+
+# 7f1df774c21345d183d04571db70c24d
+#: ../../networking/virtual_private_cloud_config.rst:67
+msgid "**VPN Gateway**: The VPC side of a VPN connection."
+msgstr "**VPN 网关**：VPN连接的VPC端。"
+
+# d4f1eced716140b2ba2e5c4a4bb94733
+#: ../../networking/virtual_private_cloud_config.rst:69
+msgid ""
+"**Site-to-Site VPN Connection**: A hardware-based VPN connection between "
+"your VPC and your datacenter, home network, or co-location facility. For "
+"more information, see \":ref:`setting-s2s-vpn-conn`\"."
+msgstr "**点对点VPN连接**：您的VPC和您的数据中心、家庭网络、主机托管设施之间基于硬件的VPN连接。更多信息，请参考\":ref:`setting-s2s-vpn-conn`\"."
+
+# d96c6c8f7e914115913908328dafe225
+#: ../../networking/virtual_private_cloud_config.rst:73
+msgid ""
+"**Customer Gateway**: The customer side of a VPN Connection. For more "
+"information, see `\"Creating and Updating a VPN Customer Gateway\" "
+"<#creating-and-updating-a-vpn-customer-gateway>`_."
+msgstr "**客户网关**:客户这边的VPN连接。更多信息，请参考 `\"创建和更新VPN客户网关\" <#creating-and-updating-a-vpn-customer-gateway>`_."
+
+# 4a709f7fe7a644bcbf353a4841f01b9d
+#: ../../networking/virtual_private_cloud_config.rst:77
+msgid ""
+"**NAT Instance**: An instance that provides Port Address Translation for "
+"instances to access the Internet via the public gateway. For more "
+"information, see \":ref:`enabling-disabling-static-nat-on-vpc`\"."
+msgstr "**NAT实例**:在用户虚机通过公网网关访问公网时，提供端口地址转换的实例。关于更多信息，请参考 \":ref:`enabling-disabling-static-nat-on-vpc`\"."
+
+# d3585dd79a1e4e7e89912c04813bb102
+#: ../../networking/virtual_private_cloud_config.rst:81
+msgid ""
+"**Network ACL**: Network ACL is a group of Network ACL items. Network ACL "
+"items are nothing but numbered rules that are evaluated in order, starting "
+"with the lowest numbered rule. These rules determine whether traffic is "
+"allowed in or out of any tier associated with the network ACL. For more "
+"information, see \":ref:`conf-net-acl`\"."
+msgstr "**网络ACL**: 网络ACL是一组网络访问控制列表。这些列表就是一个按顺序编号的规则，执行的时候，从最小的编号开始。这些规则决定了与此ACL关联的各个层的进出流量会被允许或阻止。更多信息，请参考 \":ref:`conf-net-acl`\"."
+
+# d9a20cb6323241afa91a6c2cbc307ff9
+#: ../../networking/virtual_private_cloud_config.rst:89
+msgid "Network Architecture in a VPC"
+msgstr "VPC的网络架构"
+
+# 7ee1153de76a4c929d0b1fa6a71fd31d
+#: ../../networking/virtual_private_cloud_config.rst:91
+msgid ""
+"In a VPC, the following four basic options of network architectures are "
+"present:"
+msgstr "VPC有以下四个基本的网络架构："
+
+# 1451c0ec747146d4b4c7cef8cb2721de
+#: ../../networking/virtual_private_cloud_config.rst:94
+msgid "VPC with a public gateway only"
+msgstr "只有一个公网网关的VPC"
+
+# 10f537ebc4544eb487ff69cb3d4925f7
+#: ../../networking/virtual_private_cloud_config.rst:96
+msgid "VPC with public and private gateways"
+msgstr "VPC的公有和私有网关"
+
+# 6df0df8e0b47452e978347b896d0550a
+#: ../../networking/virtual_private_cloud_config.rst:98
+msgid "VPC with public and private gateways and site-to-site VPN access"
+msgstr "VPC的公有和私有网关以及site-to-site VPN访问"
+
+# 7210a6e941a1458299c8b7853414ea18
+#: ../../networking/virtual_private_cloud_config.rst:100
+msgid "VPC with a private gateway only and site-to-site VPN access"
+msgstr "只有私有网关的VPC以及site-to-site VPN访问"
+
+# 41f1471fc8d144d4a2ae08eaa26079e5
+#: ../../networking/virtual_private_cloud_config.rst:104
+msgid "Connectivity Options for a VPC"
+msgstr "VPC的连接选择"
+
+# 7939a1a9ae10427e945a7598b60a6acb
+#: ../../networking/virtual_private_cloud_config.rst:106
+msgid "You can connect your VPC to:"
+msgstr "你可以连接你的VPC："
+
+# 92785d31fb8449578b7a7d78f8d59eb4
+#: ../../networking/virtual_private_cloud_config.rst:108
+msgid "The Internet through the public gateway."
+msgstr "通过公有网关连接到Internet."
+
+# 013122ffc01c46aabad011737399bc1b
+#: ../../networking/virtual_private_cloud_config.rst:110
+msgid ""
+"The corporate datacenter by using a site-to-site VPN connection through the "
+"VPN gateway."
+msgstr "通过site-to-siteVPN网关连接到相邻数据中心。"
+
+# 3199327142444fe1bd185a5b40149130
+#: ../../networking/virtual_private_cloud_config.rst:113
+msgid ""
+"Both the Internet and your corporate datacenter by using both the public "
+"gateway and a VPN gateway."
+msgstr "通过公有和私有VPN网关同时连接到Internet和相邻数据中心。"
+
+# 2a91b9eca4284fbcb69ab5478b249d29
+#: ../../networking/virtual_private_cloud_config.rst:118
+msgid "VPC Network Considerations"
+msgstr "VPC网络的考虑事项"
+
+# 8e8bd043a0c34c77885f6c613181a421
+#: ../../networking/virtual_private_cloud_config.rst:120
+msgid "Consider the following before you create a VPC:"
+msgstr "在创建VPC之前，确认以下事项："
+
+# f39001cdf8054dcfbd61db983190b41f
+#: ../../networking/virtual_private_cloud_config.rst:122
+msgid "A VPC, by default, is created in the enabled state."
+msgstr "在创建好VPC之后，其默认处于启用状态。"
+
+# 82792dd3f27546d2a3c42b67ba5b29f4
+#: ../../networking/virtual_private_cloud_config.rst:124
+msgid ""
+"A VPC can be created in Advance zone only, and can't belong to more than one"
+" zone at a time."
+msgstr "只能在高级区域中创建VPC，并且VPC只能属于一个区域。"
+
+# 8a09712594af4741822a39824fdef070
+#: ../../networking/virtual_private_cloud_config.rst:127
+msgid ""
+"The default number of VPCs an account can create is 20. However, you can "
+"change it by using the max.account.vpcs global parameter, which controls the"
+" maximum number of VPCs an account is allowed to create."
+msgstr "默认VPC的数量是20个。如果你需要更多的VPC的话，可以通过修改max.account.vpcs这个全局参数。这个参数是控制创建VPC的最大数量的。"
+
+# 261cae4270494826bf83e0dcae8af848
+#: ../../networking/virtual_private_cloud_config.rst:131
+msgid ""
+"The default number of tiers an account can create within a VPC is 3. You can"
+" configure this number by using the vpc.max.networks parameter."
+msgstr "默认一个用户能创建VPC的层数是三层。也可以通过vpc.max.networks这个参数修改。"
+
+# 62fc1185526b4470b7cc2d5eebfcbdfd
+#: ../../networking/virtual_private_cloud_config.rst:135
+msgid ""
+"Each tier should have an unique CIDR in the VPC. Ensure that the tier's CIDR"
+" should be within the VPC CIDR range."
+msgstr "VPC中每一层都需要是唯一的CIDR，并且这个CIDR是在VPC的CIDR的范围之内。"
+
+# 96300f5d5fe44005a32e9cf1f40b4ea4
+#: ../../networking/virtual_private_cloud_config.rst:138
+msgid "A tier belongs to only one VPC."
+msgstr "每一层只能属于一个VPC。"
+
+# 3fa6bb2bbfc54d1da2bab5ebfe5b22b2
+#: ../../networking/virtual_private_cloud_config.rst:140
+msgid "All network tiers inside the VPC should belong to the same account."
+msgstr "VPC中所有网络层都应属于同一个帐号。"
+
+# abd18af86f4e44958067a2f7dc82012f
+#: ../../networking/virtual_private_cloud_config.rst:142
+msgid ""
+"When a VPC is created, by default, a SourceNAT IP is allocated to it. The "
+"Source NAT IP is released only when the VPC is removed."
+msgstr "当VPC创建好之后，默认会分配好SourceNAT IP。当此VPC删除之后，SourceNAT IP也会被释放。"
+
+# 14ebd559d22240e29e435b14253ef654
+#: ../../networking/virtual_private_cloud_config.rst:145
+msgid ""
+"A public IP can be used for only one purpose at a time. If the IP is a "
+"sourceNAT, it cannot be used for StaticNAT or port forwarding."
+msgstr "一个公网IP只能用一个用途。如果此IP用于SourceNAT作用的话，就不能同时再用作StaticNAT 或端口转发。"
+
+# c29d747872084beb8924548c54211fae
+#: ../../networking/virtual_private_cloud_config.rst:148
+msgid ""
+"The instances can only have a private IP address that you provision. To "
+"communicate with the Internet, enable NAT to an instance that you launch in "
+"your VPC."
+msgstr "一个实例只能有一个私有IP地址，为了访问Internet,你可以为VPC里的此实例启用NAT功能。"
+
+# 8d3468d50b334a3389cb81da8b464dea
+#: ../../networking/virtual_private_cloud_config.rst:152
+msgid ""
+"Only new networks can be added to a VPC. The maximum number of networks per "
+"VPC is limited by the value you specify in the vpc.max.networks parameter. "
+"The default value is three."
+msgstr "只有新的网络才能加入VPC。每一个VPC的最大网络数量由参数vpc.max.networks指定。其默认值为3."
+
+# af8282a7c19c4580a62b69371106d6f2
+#: ../../networking/virtual_private_cloud_config.rst:156
+msgid ""
+"The load balancing service can be supported by only one tier inside the VPC."
+msgstr "VPC中只有一层支持负载均衡服务。"
+
+# 39cb5b3dc8fe40988ffba7f5ede4490d
+#: ../../networking/virtual_private_cloud_config.rst:159
+msgid "If an IP address is assigned to a tier:"
+msgstr "如果一个IP地址被赋予一个网络层："
+
+# 176c27ebe07048b3a7836a228d011441
+#: ../../networking/virtual_private_cloud_config.rst:161
+msgid ""
+"That IP can't be used by more than one tier at a time in the VPC. For "
+"example, if you have tiers A and B, and a public IP1, you can create a port "
+"forwarding rule by using the IP either for A or B, but not for both."
+msgstr "那么这个IP就不能在VPC里被另外的层所使用。比如：如果你有A层和B层以及一个公网IP地址，则你可以为A或B创建一个端口转发规则，但不能同时在A和B上创建。"
+
+# f43348e85da24485a1d92b63da2366ac
+#: ../../networking/virtual_private_cloud_config.rst:166
+msgid ""
+"That IP can't be used for StaticNAT, load balancing, or port forwarding "
+"rules for another guest network inside the VPC."
+msgstr "那个IP也不能在VPC的其它的客户网络里用作StaticNAT,负载均衡，端口转发规则。"
+
+# fee8e4c6c5954adeb9005bf1d5ce023e
+#: ../../networking/virtual_private_cloud_config.rst:169
+msgid "Remote access VPN is not supported in VPC networks."
+msgstr "VPC网络不支持Remote access VPN。"
+
+# 96fc9927ad5141bba2d657b1963d9d87
+#: ../../networking/virtual_private_cloud_config.rst:173
+msgid "Adding a Virtual Private Cloud"
+msgstr "添加一个VPC"
+
+# 5f129175d6144d298c7ede91ac9ec513
+#: ../../networking/virtual_private_cloud_config.rst:175
+msgid ""
+"When creating the VPC, you simply provide the zone and a set of IP addresses"
+" for the VPC network address space. You specify this set of addresses in the"
+" form of a Classless Inter-Domain Routing (CIDR) block."
+msgstr "当创建VPC时，你只需要提供区域名和VPC要使用的一组IP地址。这组IP地址是以CIDR块的形式提供。"
+
+# c91fb511977940b7b6f4adbffe2da030
+#: ../../networking/virtual_private_cloud_config.rst:185
+msgid "Click Add VPC. The Add VPC page is displayed as follows:"
+msgstr "点击添加VPC按钮。页面呈现以下："
+
+# 7632a958cf894fb9a2bfac92d1f5600d
+#: ../../networking/virtual_private_cloud_config.rst:187
+msgid "|add-vpc.png|"
+msgstr "|add-vpc.png|"
+
+# 8ecd10dee5dc44baa12a0ec575b6f501
+#: ../../networking/virtual_private_cloud_config.rst:191
+msgid "**Name**: A short name for the VPC that you are creating."
+msgstr "**名称**: 要创建的VPC的名称。"
+
+# 27ae714de91a400780ba0479927daaf5
+#: ../../networking/virtual_private_cloud_config.rst:193
+msgid "**Description**: A brief description of the VPC."
+msgstr "**描述**: 关于此VPC的简短描述."
+
+# 1824e109bd6c46ac8a5a0c0f2057b2fa
+#: ../../networking/virtual_private_cloud_config.rst:195
+msgid "**Zone**: Choose the zone where you want the VPC to be available."
+msgstr "**区域**: 你希望将此VPN应用在哪个区域中。"
+
+# e936203c2e05451299d2de67f4f47ebc
+#: ../../networking/virtual_private_cloud_config.rst:197
+msgid ""
+"**Super CIDR for Guest Networks**: Defines the CIDR range for all the tiers "
+"(guest networks) within a VPC. When you create a tier, ensure that its CIDR "
+"is within the Super CIDR value you enter. The CIDR must be RFC1918 "
+"compliant."
+msgstr "**客户网络超级CIDR**: 定义一个VPC内所有层（客户网络）的CIDR范围。当你新创建一个层时，这个层的CIDR必须在这个超级CIDR范围之内。CIDR的格式定义必须符合RFC1918。"
+
+# 6ca68d15f75048b0b195f40134796a2c
+#: ../../networking/virtual_private_cloud_config.rst:202
+msgid ""
+"**DNS domain for Guest Networks**: If you want to assign a special domain "
+"name, specify the DNS suffix. This parameter is applied to all the tiers "
+"within the VPC. That implies, all the tiers you create in the VPC belong to "
+"the same DNS domain. If the parameter is not specified, a DNS domain name is"
+" generated automatically."
+msgstr "**客户网络的DNS域名**: 如果你需要一个域名，则需要在此指定域名后缀。这个参数会应用到VPC中所有的层中。这表示，VPC中所有的层都属于同一个域。如果没有指定域名，则域名会由系统随机产生。"
+
+# 71b34c1e720143dfa39c979df560f4ca
+#: ../../networking/virtual_private_cloud_config.rst:208
+msgid ""
+"**Public Load Balancer Provider**: You have two options: VPC Virtual Router "
+"and Netscaler."
+msgstr "**公共负载均衡提供者**: 有两个选项：VPC虚拟路由器和 Netscaler。"
+
+# 8798d1945a1c4084a1b2a0614ec9db32
+#: ../../networking/virtual_private_cloud_config.rst:215
+msgid "Adding Tiers"
+msgstr "添加层"
+
+# 98d4e1b6db094ef3be8c292cd0efa54b
+#: ../../networking/virtual_private_cloud_config.rst:217
+msgid ""
+"Tiers are distinct locations within a VPC that act as isolated networks, "
+"which do not have access to other tiers by default. Tiers are set up on "
+"different VLANs that can communicate with each other by using a virtual "
+"router. Tiers provide inexpensive, low latency network connectivity to other"
+" tiers within the VPC."
+msgstr "层在VPC里起来隔离网络的作用，默认规则是层之间不能互访。不同VLAN之间的层可以通过虚拟机实现连接。层在VPC内部提供一种廉价，低延迟的网络连接。"
+
+# 3314f3a5a14a4b969d7ee70acab97a4a
+# f747c26b980441cc9b6ecb7baf8f8557
+#: ../../networking/virtual_private_cloud_config.rst:229
+#: ../../networking/virtual_private_cloud_config.rst:1366
+msgid ""
+"All the VPC that you have created for the account is listed in the page."
+msgstr "此帐号创建的所有VPC将显示在页面中。"
+
+# 8844e1d7896046a7881fdb53a34d3dce
+#: ../../networking/virtual_private_cloud_config.rst:233
+msgid ""
+"The end users can see their own VPCs, while root and domain admin can see "
+"any VPC they are authorized to see."
+msgstr "最终用户能看到他们自己的VPC，系统管理用户和域管理员可以看到所有被授权查看的VPC。"
+
+# 9771fbcf9e3e4bc7adeceaeb5db1a8ff
+# 19ef7e315e30411398c644e4ee829252
+#: ../../networking/virtual_private_cloud_config.rst:236
+#: ../../networking/virtual_private_cloud_config.rst:1369
+msgid ""
+"Click the Configure button of the VPC for which you want to set up tiers."
+msgstr "在你希望设置层的VPC里，点击配置按钮。"
+
+# c78aa8064f6342b481fd5870fce87c54
+#: ../../networking/virtual_private_cloud_config.rst:239
+msgid "Click Create network."
+msgstr "点击新建网络。"
+
+# c405f8d748a04cbe8c19e538c402ff7e
+#: ../../networking/virtual_private_cloud_config.rst:241
+msgid "The Add new tier dialog is displayed, as follows:"
+msgstr "然后，添加层的对话界面就会出现。如下："
+
+# 34e2e606b003480ab786bf798340707f
+#: ../../networking/virtual_private_cloud_config.rst:243
+msgid "|add-tier.png|"
+msgstr "|add-tier.png|"
+
+# e176f3eb0eff46849004f861f27d70ba
+#: ../../networking/virtual_private_cloud_config.rst:245
+msgid ""
+"If you have already created tiers, the VPC diagram is displayed. Click "
+"Create Tier to add a new tier."
+msgstr "如果你已添加层，VPC界面就会出现。点击添加层可以增加一个新的层。"
+
+# 6da7a219b10c4cd393a25728f68792f6
+#: ../../networking/virtual_private_cloud_config.rst:252
+msgid "**Name**: A unique name for the tier you create."
+msgstr "**名称**: 你添加的层的一个唯一的层名。"
+
+# 1b4af9e2df5d4c45a8fe0846d9421847
+#: ../../networking/virtual_private_cloud_config.rst:254
+msgid ""
+"**Network Offering**: The following default network offerings are listed: "
+"Internal LB, DefaultIsolatedNetworkOfferingForVpcNetworksNoLB, "
+"DefaultIsolatedNetworkOfferingForVpcNetworks"
+msgstr "**网络方案**: 默认有以下几种网络方案: Internal LB, DefaultIsolatedNetworkOfferingForVpcNetworksNoLB, DefaultIsolatedNetworkOfferingForVpcNetworks"
+
+# ee49520ec77a4c7097618acebca06e0a
+#: ../../networking/virtual_private_cloud_config.rst:259
+msgid ""
+"In a VPC, only one tier can be created by using LB-enabled network offering."
+msgstr "在一个VPC中，用LB-enabled network offering只能创建一个层。"
+
+# fe3e7690b8434d17bee25931f77b4060
+#: ../../networking/virtual_private_cloud_config.rst:267
+msgid "**VLAN**: The VLAN ID for the tier that the root admin creates."
+msgstr "**VLAN**: 指定系统管理员创建的层的VLAN ID号。"
+
+# ac4187501eb24391a8fe48b9eaea78db
+#: ../../networking/virtual_private_cloud_config.rst:269
+msgid ""
+"This option is only visible if the network offering you selected is VLAN-"
+"enabled."
+msgstr "这个选项只在你选择的方案在VLAN-enabled的情况下才会显示出来。"
+
+# 4f0b4d89f6904969ae3ee5e09664a312
+#: ../../networking/virtual_private_cloud_config.rst:272
+msgid ""
+"For more information, see `\"Assigning VLANs to Isolated Networks\" "
+"<hosts.html#assigning-vlans-to-isolated-networks>`_."
+msgstr "如需要更多信息，请参考\"为隔离网络分配VLAN\" <hosts.html#assigning-vlans-to-isolated-networks>`_.节。"
+
+# 9d2a27efdd3340729e2b4d326a7ae82f
+#: ../../networking/virtual_private_cloud_config.rst:283
+msgid "Continue with configuring access control list for the tier."
+msgstr "继续为层配置访问控制列表。"
+
+# cfc11ab12602462ea15568f2ee59a571
+#: ../../networking/virtual_private_cloud_config.rst:289
+msgid "Configuring Network Access Control List"
+msgstr "配置网络访问控制列表"
+
+# 80d05b449ec74dcf9676a890310dd627
+#: ../../networking/virtual_private_cloud_config.rst:291
+msgid ""
+"Define Network Access Control List (ACL) on the VPC virtual router to "
+"control incoming (ingress) and outgoing (egress) traffic between the VPC "
+"tiers, and the tiers and Internet. By default, all incoming traffic to the "
+"guest networks is blocked and all outgoing traffic from guest networks is "
+"allowed, once you add an ACL rule for outgoing traffic, then only outgoing "
+"traffic specified in this ACL rule is allowed, the rest is blocked. To open "
+"the ports, you must create a new network ACL. The network ACLs can be "
+"created for the tiers only if the NetworkACL service is supported."
+msgstr "定义网络访问控制列表（ACL），用以在VPC的层之间，或是层与互联网之间控制进出流量。默认情况下，客户网络的所有进入流量被阻止，所有外出流量被允许。一旦在外出流量方向添加了ACL，则只有ACL规则允许的流量可以被允许，其余的外出流量会被阻止。如果要开放其它端口，则需要在新的ACL中明确定义。只有在支持NetworkACL服务的条件下，只能创建层的ACL。"
+
+# aa42198a93034f1c84348ea431669aa6
+#: ../../networking/virtual_private_cloud_config.rst:303
+msgid "About Network ACL Lists"
+msgstr "关于ACL列表"
+
+# b8c70fbf1bc54242a435cb7f6a8bcfff
+#: ../../networking/virtual_private_cloud_config.rst:305
+msgid ""
+"In CloudStack terminology, Network ACL is a group of Network ACL items. "
+"Network ACL items are nothing but numbered rules that are evaluated in "
+"order, starting with the lowest numbered rule. These rules determine whether"
+" traffic is allowed in or out of any tier associated with the network ACL. "
+"You need to add the Network ACL items to the Network ACL, then associate the"
+" Network ACL with a tier. Network ACL is associated with a VPC and can be "
+"assigned to multiple VPC tiers within a VPC. A Tier is associated with a "
+"Network ACL at all the times. Each tier can be associated with only one ACL."
+msgstr "在CloudStack术语中，ACL指的是一组针对网络条目。其按条目规则顺序执行，从最小值开始。这些规则决定了与此ACL关联的层的进出流量是被允许还是阻止。操作的方法是添加一个ACL，然后将这个ACL与层关联。ACL在整个VPC中使用，它可以被关系到一个VPC当中多个层中。一个层能及只能关联到一个ACL中。"
+
+# 2b2f7cf9c53546368b42fa70f544bd0a
+#: ../../networking/virtual_private_cloud_config.rst:315
+msgid ""
+"The default Network ACL is used when no ACL is associated. Default behavior "
+"is all the incoming traffic is blocked and outgoing traffic is allowed from "
+"the tiers. Default network ACL cannot be removed or modified. Contents of "
+"the default Network ACL is:"
+msgstr "当没有ACL明确关联时，会有一个默认的ACL起作用。默认规则是层中所有进入流量被阻止，所有外出流量被允许默认的ACL不能被删除或修改。默认ACL的内容如下："
+
+# 94ec3c0bd9ad4d2694658ae87c05a6dc
+#: ../../networking/virtual_private_cloud_config.rst:321
+msgid "Rule"
+msgstr "规则"
+
+# cdf1ee2618b8425fa236a5ba71e879f8
+#: ../../networking/virtual_private_cloud_config.rst:321
+msgid "Protocol"
+msgstr "协议"
+
+# 71beb1131ecc4bf79f519067b0cc0421
+#: ../../networking/virtual_private_cloud_config.rst:321
+msgid "Traffic type"
+msgstr "流量类型"
+
+# 02feb18dc4204c6d816848bece6753f2
+#: ../../networking/virtual_private_cloud_config.rst:321
+msgid "Action"
+msgstr "动作"
+
+# 7b039a75bc4e40b0998ee720fc9be7af
+# b4c3a2a2f8274af8b1e3a9590128b37e
+#: ../../networking/virtual_private_cloud_config.rst:323
+#: ../../networking/virtual_private_cloud_config.rst:324
+msgid "All"
+msgstr "所有"
+
+# 29b1464ed65441e9aef0eac71c0aee88
+#: ../../networking/virtual_private_cloud_config.rst:323
+msgid "Ingress"
+msgstr "进入流量"
+
+# 0f25a9ce81214a8db99b2c15ca68ecaf
+# 1f7b00eb40c84e49afad68ec636cf017
+#: ../../networking/virtual_private_cloud_config.rst:323
+#: ../../networking/virtual_private_cloud_config.rst:324
+msgid "0.0.0.0/0"
+msgstr "0.0.0.0/0"
+
+# 2a938982deaf4bee91999a560045df0f
+#: ../../networking/virtual_private_cloud_config.rst:324
+msgid "Egress"
+msgstr "外出流量"
+
+# a89760a050314e7687a774e021984e36
+#: ../../networking/virtual_private_cloud_config.rst:329
+msgid "Creating ACL Lists"
+msgstr "创建ACL列表"
+
+# 3eda1f1ad1e84a5fa0abdd0d63298377
+# c9c0ef8b2d724a88af647c817e2e60b3
+#: ../../networking/virtual_private_cloud_config.rst:364
+#: ../../networking/virtual_private_cloud_config.rst:391
+msgid "Select Network ACL Lists."
+msgstr "选择网络ACL列表。"
+
+# d948b72948e443708b6aa2c594cbf48c
+#: ../../networking/virtual_private_cloud_config.rst:366
+msgid ""
+"The following default rules are displayed in the Network ACLs page: "
+"default\\_allow, default\\_deny."
+msgstr "在ACL页面，下面默认规则将会显示出来：default\\_allow, default\\_deny."
+
+# a06453197ea54b78a1671d85bf9e73d7
+#: ../../networking/virtual_private_cloud_config.rst:369
+msgid "Click Add ACL Lists, and specify the following:"
+msgstr "点击添加ACL列表，指定以下配置："
+
+# 936eba7c1c614d71b4d81a9836930774
+#: ../../networking/virtual_private_cloud_config.rst:371
+msgid "**ACL List Name**: A name for the ACL list."
+msgstr "**ACL列表名称**: 为ACL列表命名。"
+
+# 33929738488f4ea9919dcf6a7e3fe2f5
+#: ../../networking/virtual_private_cloud_config.rst:373
+msgid ""
+"**Description**: A short description of the ACL list that can be displayed "
+"to users."
+msgstr "**描述**: ACL列表的简短描述。"
+
+# 7c8c60eca2c549f5b45770647d1aa00c
+#: ../../networking/virtual_private_cloud_config.rst:378
+msgid "Creating an ACL Rule"
+msgstr "创建一个ACL规则"
+
+# 9dd4e8a5913f4029b9009edcec1a873e
+#: ../../networking/virtual_private_cloud_config.rst:393
+msgid ""
+"In addition to the custom ACL lists you have created, the following default "
+"rules are displayed in the Network ACLs page: default\\_allow, "
+"default\\_deny."
+msgstr "除了创建的你自定义的ACL列表之后，以下默认ACL规则也会显示在页面中：default\\_allow, default\\_deny."
+
+# a6f4bd8cfb1b4f6fad84ffaa0cb8be7d
+# 8f83289dee8e4333b67e394e3c8d0f0d
+#: ../../networking/virtual_private_cloud_config.rst:397
+#: ../../networking/virtual_private_cloud_config.rst:477
+msgid "Select the desired ACL list."
+msgstr "选择需要的ACL列表。"
+
+# 92b66b5dafcf4032a201494a372c5a09
+#: ../../networking/virtual_private_cloud_config.rst:399
+msgid "Select the ACL List Rules tab."
+msgstr "选择ACL规则栏"
+
+# dfaf3ab49c4a4d8c89f6e9f968c769ac
+#: ../../networking/virtual_private_cloud_config.rst:401
+msgid ""
+"To add an ACL rule, fill in the following fields to specify what kind of "
+"network traffic is allowed in the VPC."
+msgstr "为了创建ACL规则，需要在VPC中定义下面哪些网络流量是允许的。"
+
+# 51c1de77519e4d1dbd873ec733e2ba75
+#: ../../networking/virtual_private_cloud_config.rst:404
+msgid "**Rule Number**: The order in which the rules are evaluated."
+msgstr "**规则序号**: 规则被执行的顺序。"
+
+# 86a9b66780f94ece927187a782db5a7b
+#: ../../networking/virtual_private_cloud_config.rst:406
+msgid ""
+"**CIDR**: The CIDR acts as the Source CIDR for the Ingress rules, and "
+"Destination CIDR for the Egress rules. To accept traffic only from or 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 incoming "
+"traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr "**CIDR**: 对于进入的规则，CIDR对源地址起作用，对于外出的规则，CIDR对目标地址起作用。如果要定义多个可接受进出流量的特定地址段，需要以逗号分隔各个CIDR。CIDR是进入流量的基IP地址。比如， 192.168.0.0/22. 如要对所有CIDR允许流量, 设置为 0.0.0.0/0."
+
+# 8330289162464c20a853e935c0a8994c
+#: ../../networking/virtual_private_cloud_config.rst:413
+msgid "**Action**: What action to be taken. Allow traffic or block."
+msgstr "**操作**: 定义要进行的操作，允许或阻止。"
+
+# 498ccf8b2f69422382f0f84e1ca4539c
+#: ../../networking/virtual_private_cloud_config.rst:415
+msgid ""
+"**Protocol**: The networking protocol that sources use to send traffic to "
+"the tier. 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. All supports all the traffic. Other "
+"option is Protocol Number."
+msgstr "**协议**: 发送到层的源地址的网络协议。最终用户的访问和数据交换通常是用TCP和UDP协议。ICMP协议通常用来发送错误信息或网络监控。ALL表示支持所有协议流量，其它选项是协议编号。"
+
+# e63c6c1906af4a6b8ed6d87b9c73ed40
+#: ../../networking/virtual_private_cloud_config.rst:422
+msgid ""
+"**Start Port**, **End Port** (TCP, UDP only): A range of listening ports "
+"that are the destination for the incoming traffic. If you are opening a "
+"single port, use the same number in both fields."
+msgstr "**起始端口**, **结束端口** (TCP, UDP only):对进入流量，这些端口是指需要监听的目标地址的端口范围。如果你只开放一个端口，则在起始和结束端口里填写同一个端口。"
+
+# 7c79246e902c4bbc8186dda26670b328
+#: ../../networking/virtual_private_cloud_config.rst:426
+msgid ""
+"**Protocol Number**: The protocol number associated with IPv4 or IPv6. For "
+"more information, see `Protocol Numbers <http://www.iana.org/assignments"
+"/protocol-numbers/protocol-numbers.xml>`_."
+msgstr "**协议编号**: 协议编号是与IPV4或IPV6相关联的。更多信息，请参考 `协议号 <http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xml>`_."
+
+# f108c8672b5549f0b7bccead5633f71e
+#: ../../networking/virtual_private_cloud_config.rst:430
+msgid ""
+"**ICMP Type**, **ICMP Code** (ICMP only): The type of message and error code"
+" that will be sent."
+msgstr "**ICMP类型**, **ICMP代码** (ICMP only): 信息类型及发送错误的代码。"
+
+# aea6fa8baba04251bd617d19ec0fac50
+#: ../../networking/virtual_private_cloud_config.rst:433
+msgid "**Traffic Type**: The type of traffic: Incoming or outgoing."
+msgstr "**流量类型**: 进出流量的类型。"
+
+# 8837fecc5cbe4deb9b9b32eb1e7a22bb
+#: ../../networking/virtual_private_cloud_config.rst:435
+msgid "Click Add. The ACL rule is added."
+msgstr "点击添加。这个ACL规则就添加好了。"
+
+# ff24506a3edf4b368b6851738d3cd4a6
+#: ../../networking/virtual_private_cloud_config.rst:437
+msgid ""
+"You can edit the tags assigned to the ACL rules and delete the ACL rules you"
+" have created. Click the appropriate button in the Details tab."
+msgstr "你可以重新编辑ACL标签，或是删除ACL。点击详细信息里的appropriate按钮。"
+
+# 686d25e2eb934b228756cffad503dc14
+#: ../../networking/virtual_private_cloud_config.rst:443
+msgid "Creating a Tier with Custom ACL List"
+msgstr "创建一个具有自定义ACL列表的层。"
+
+# 12b4daba446b406188c175ab28efa5c1
+# e044ead1ada14ab5b3ec8b3e711b655c
+#: ../../networking/virtual_private_cloud_config.rst:445
+#: ../../networking/virtual_private_cloud_config.rst:461
+msgid "Create a VPC."
+msgstr "创建一个VPC。"
+
+# 5f8cae5888424f2a90e4e67bb1174768
+# 1a83d09401c84e96a549f864c6695017
+#: ../../networking/virtual_private_cloud_config.rst:447
+#: ../../networking/virtual_private_cloud_config.rst:467
+msgid "Create a custom ACL list."
+msgstr "创建一个自定义ACL列表。"
+
+# a0a748dbf9a14a6292e606e617c28d64
+# b359fbe706df412e8209f49644e377e0
+#: ../../networking/virtual_private_cloud_config.rst:449
+#: ../../networking/virtual_private_cloud_config.rst:469
+msgid "Add ACL rules to the ACL list."
+msgstr "将ACL规则加入ACL列表。"
+
+# 3c202066013d4bc0adfd54fbb57b6a40
+# c1084edbb18d4e88a8862f51a676882d
+#: ../../networking/virtual_private_cloud_config.rst:451
+#: ../../networking/virtual_private_cloud_config.rst:463
+msgid "Create a tier in the VPC."
+msgstr "在VPC里创建一个层。"
+
+# 2693d2f98f2144d2bd046d2a6ee9edc4
+#: ../../networking/virtual_private_cloud_config.rst:453
+msgid "Select the desired ACL list while creating a tier."
+msgstr "在创建层的过程中选择需要的ACL列表。"
+
+# 8d75f722483847bfbaf121d50683108f
+#: ../../networking/virtual_private_cloud_config.rst:459
+msgid "Assigning a Custom ACL List to a Tier"
+msgstr "将一个自定义的ACL关联到一个层。"
+
+# fb8e5f4022c7464683a31b78f61d773e
+#: ../../networking/virtual_private_cloud_config.rst:465
+msgid "Associate the tier with the default ACL rule."
+msgstr "将默认的ACL规则关联到层。"
+
+# 39e12cdf7861405b9cb6e499e2a43a69
+#: ../../networking/virtual_private_cloud_config.rst:471
+msgid "Select the tier for which you want to assign the custom ACL."
+msgstr "选中你希望赋予自定义ACL的层。"
+
+# 948fcbc5ab17415abed167dfec847398
+#: ../../networking/virtual_private_cloud_config.rst:473
+msgid "Click the Replace ACL List icon. |replace-acl-icon.png|"
+msgstr "点击替换ACL图标。|replace-acl-icon.png|"
+
+# 1e59b7c5187d410c84f77a2de169bfd2
+#: ../../networking/virtual_private_cloud_config.rst:475
+msgid "The Replace ACL List dialog is displayed."
+msgstr "替换ACL的对话界面将会弹出来。"
+
+# 6a8102624df0467d816ba212863e0f4a
+#: ../../networking/virtual_private_cloud_config.rst:485
+msgid "Adding a Private Gateway to a VPC"
+msgstr "在一个VPC里加入私有网关。"
+
+# d90a68b590214ef5a6ef4f86afbf6fd5
+#: ../../networking/virtual_private_cloud_config.rst:487
+msgid ""
+"A private gateway can be added by the root admin only. The VPC private "
+"network has 1:1 relationship with the NIC of the physical network. You can "
+"configure multiple private gateways to a single VPC. No gateways with "
+"duplicated VLAN and IP are allowed in the same data center."
+msgstr "私有网关只能被系统管理员添加。VPC私有网络和物理网络之间是1：1的对应关系。你可以在一个VPC里定义多个私有网关。在同一个数据中心，不允许复制VLAN和IP的网关。"
+
+# 8834cea2024a427e8ed0a565fd66bd19
+#: ../../networking/virtual_private_cloud_config.rst:501
+msgid ""
+"Click the Configure button of the VPC to which you want to configure load "
+"balancing rules."
+msgstr "在你想配置负载均衡的VPC上点击配置按钮。"
+
+# b947ba8a391e4148ae31611b4dd8a083
+# 97f4415d522c4cd0bcb3fccbe14ce6bb
+# 3ee1ffc35ae4421ab543c330faa61f59
+#: ../../networking/virtual_private_cloud_config.rst:509
+#: ../../networking/virtual_private_cloud_config.rst:744
+#: ../../networking/virtual_private_cloud_config.rst:802
+msgid "The following options are displayed."
+msgstr "下面这些选项就会出现。"
+
+# 0486f473e9e3414bb92b039e48b87494
+#: ../../networking/virtual_private_cloud_config.rst:531
+msgid "Select Private Gateways."
+msgstr "选择私有网关。"
+
+# a70922624b2b4f53abab8e82e8145edb
+#: ../../networking/virtual_private_cloud_config.rst:533
+msgid "The Gateways page is displayed."
+msgstr "网关对话框就会显示出来。"
+
+# 997a7c9466244a49a73f4b7b36f80498
+#: ../../networking/virtual_private_cloud_config.rst:535
+msgid "Click Add new gateway:"
+msgstr "点击添加新网关："
+
+# 46ae796875074a9bb87aa12a389ff481
+#: ../../networking/virtual_private_cloud_config.rst:537
+msgid "|add-new-gateway-vpc.png|"
+msgstr "|add-new-gateway-vpc.png|"
+
+# 2bdb16a51b0c4b0ebc5ecc1fe2301931
+#: ../../networking/virtual_private_cloud_config.rst:541
+msgid ""
+"**Physical Network**: The physical network you have created in the zone."
+msgstr "**物理网络**: 此处为你已在区域内建好的物理网络。"
+
+# 40e19742c3d6491ba0358d3376dca15c
+#: ../../networking/virtual_private_cloud_config.rst:544
+msgid "**IP Address**: The IP address associated with the VPC gateway."
+msgstr "**IP地址**: 关联VPC网关的IP地址。"
+
+# b992f8b2e26749a7b8eb0483fbe18516
+#: ../../networking/virtual_private_cloud_config.rst:546
+msgid ""
+"**Gateway**: The gateway through which the traffic is routed to and from the"
+" VPC."
+msgstr "**网关**: 定义进出VPC流量的网关。"
+
+# 08b7e18cfef146d5aac5e3a932b9ceee
+#: ../../networking/virtual_private_cloud_config.rst:549
+msgid "**Netmask**: The netmask associated with the VPC gateway."
+msgstr "**Netmask**: VPC网关的子网掩码。"
+
+# 17bf2c0bfeb849c286ef214c11472b88
+#: ../../networking/virtual_private_cloud_config.rst:551
+msgid "**VLAN**: The VLAN associated with the VPC gateway."
+msgstr "**VLAN**: VPC网关的VLAN。"
+
+# 7c787d4d6da0489494c04559abeb12bb
+#: ../../networking/virtual_private_cloud_config.rst:553
+msgid ""
+"**Source NAT**: Select this option to enable the source NAT service on the "
+"VPC private gateway."
+msgstr "**Source NAT**: 这个选项会启用VPC私有网关的source NAT服务。"
+
+# d3c83ba870aa46f481f5b326130c542f
+#: ../../networking/virtual_private_cloud_config.rst:556
+msgid "See \":ref:`source-nat-priv-gw`\"."
+msgstr "参考\":ref:`source-nat-priv-gw`\"."
+
+# d19b3a39546842e5a175f1e7e7819cef
+#: ../../networking/virtual_private_cloud_config.rst:558
+msgid ""
+"**ACL**: Controls both ingress and egress traffic on a VPC private gateway. "
+"By default, all the traffic is blocked."
+msgstr "**ACL**: 控制VPC私有网关的进出流量，默认情况下，所有流量被阻止。"
+
+# eb9e7232fbad4dc5b0bae719d0592256
+#: ../../networking/virtual_private_cloud_config.rst:561
+msgid "See \":ref:`acl-priv-gw`\"."
+msgstr "参考\":ref:`acl-priv-gw`\"."
+
+# 7aa9fc8200334aa4901dc0974c908c27
+#: ../../networking/virtual_private_cloud_config.rst:563
+msgid ""
+"The new gateway appears in the list. You can repeat these steps to add more "
+"gateway for this VPC."
+msgstr "新的网关就会出现在列表中。你可以重复这些步骤为VPC增加更多的网关。"
+
+# 2b0ce92e7bed418b936208b7bad7d5b7
+#: ../../networking/virtual_private_cloud_config.rst:570
+msgid "Source NAT on Private Gateway"
+msgstr "私有网关的Source NAT"
+
+# fe7ed22a9393446c9cc5ad4d4cd5edc3
+#: ../../networking/virtual_private_cloud_config.rst:572
+msgid ""
+"You might want to deploy multiple VPCs with the same super CIDR and guest "
+"tier CIDR. Therefore, multiple guest VMs from different VPCs can have the "
+"same IPs to reach a enterprise data center through the private gateway. In "
+"such cases, a NAT service need to be configured on the private gateway to "
+"avoid IP conflicts. If Source NAT is enabled, the guest VMs in VPC reaches "
+"the enterprise network via private gateway IP address by using the NAT "
+"service."
+msgstr "你可能希望在同一个超级CIDR和客户层CIDR中部署多个VPC。因此，在一个数据中心，不同VPC中的虚拟机通过私有网络可以拥有相同的IP地址。在这种情况下，就需要在私有网关里配置Source NAT服务以避免IP冲突。如果Source NAT服务启用，VPC中的客户虚拟机使用私有网关IP地址与数据中心其它机器交流。"
+
+# 5a711a13a70c4237b78e207150d2aa6b
+#: ../../networking/virtual_private_cloud_config.rst:580
+msgid ""
+"The Source NAT service on a private gateway can be enabled while adding the "
+"private gateway. On deletion of a private gateway, source NAT rules specific"
+" to the private gateway are deleted."
+msgstr "Source NAT服务是添加私有网关时启用。如果删除了私有网关，关联到此私有网关的Source NAT规则也会被删除。"
+
+# 63952cd0c2df4a2ba370e8e3f499ebb3
+#: ../../networking/virtual_private_cloud_config.rst:584
+msgid ""
+"To enable source NAT on existing private gateways, delete them and create "
+"afresh with source NAT."
+msgstr "如要有已有私有网关中启用Source NAT，需要先删除（私有网关），然后再建一个启用Source NAT的私有网关。"
+
+# ca4ce702729d44de9545633f08b8e2c0
+#: ../../networking/virtual_private_cloud_config.rst:591
+msgid "ACL on Private Gateway"
+msgstr "私有网关的ACL"
+
+# f6b347934c2d421d9b87c66c8944a8b9
+#: ../../networking/virtual_private_cloud_config.rst:593
+msgid ""
+"The traffic on the VPC private gateway is controlled by creating both "
+"ingress and egress network ACL rules. The ACLs contains both allow and deny "
+"rules. As per the rule, all the ingress traffic to the private gateway "
+"interface and all the egress traffic out from the private gateway interface "
+"are blocked."
+msgstr "VPC私有网关的进出流量是被ACL规则控制的。ACL均包含允许和阻止的规则。在每一条规则中，所有进出私有网关接口的流量是被阻止的。"
+
+# 6f1f3b0dd74f4ce594dbb45f33ef48e9
+#: ../../networking/virtual_private_cloud_config.rst:599
+msgid ""
+"You can change this default behaviour while creating a private gateway. "
+"Alternatively, you can do the following:"
+msgstr "你可以在创建私有网关时，改变这个默认的行为。或者，你也可以按如下方式操作："
+
+# 8238d9adc04246d9a930b0b546fc0dc4
+# b52342a1c90a4d8588ad601a3cb95384
+#: ../../networking/virtual_private_cloud_config.rst:602
+#: ../../networking/virtual_private_cloud_config.rst:633
+msgid "In a VPC, identify the Private Gateway you want to work with."
+msgstr "在VPC中，验证你想操作的私有网关。"
+
+# d0331cbe6cb343e9baeed7ebabf6898b
+#: ../../networking/virtual_private_cloud_config.rst:604
+msgid "In the Private Gateway page, do either of the following:"
+msgstr "在私有网关页面，按如下步骤操作："
+
+# d004af9551994806b983a6b59283779b
+#: ../../networking/virtual_private_cloud_config.rst:606
+msgid "Use the Quickview. See 3."
+msgstr "使用快速查看视图，参考3."
+
+# 40cc4d8cf410478e812d5cb50a621341
+#: ../../networking/virtual_private_cloud_config.rst:608
+msgid "Use the Details tab. See 4 through ."
+msgstr "使用详细查看栏。参考4。"
+
+# 6d609b2091244d7ca3405dc4269efe6f
+#: ../../networking/virtual_private_cloud_config.rst:610
+msgid ""
+"In the Quickview of the selected Private Gateway, click Replace ACL, select "
+"the ACL rule, then click OK"
+msgstr "在所选择的私有网关的快速查看视图里，点击替换ACL，选中ACL规则，然后点击OK按钮。"
+
+# 83b99b7439014125a36b48a6b0a7f80e
+#: ../../networking/virtual_private_cloud_config.rst:613
+msgid "Click the IP address of the Private Gateway you want to work with."
+msgstr "点击你需要操作的私有网关的IP地址。"
+
+# 14187251994f4a8c8ccffac034d839d3
+#: ../../networking/virtual_private_cloud_config.rst:615
+msgid ""
+"In the Detail tab, click the Replace ACL button. |replace-acl-icon.png|"
+msgstr "在详细查看栏。点击替换ACL按钮。|replace-acl-icon.png|"
+
+# 9dbebf0df0394108a99bc5c305a172cb
+#: ../../networking/virtual_private_cloud_config.rst:618
+msgid "The Replace ACL dialog is displayed."
+msgstr "替换ACL的对话框就会出现。"
+
+# ec9140575d1943d0b76f6536f0862e43
+#: ../../networking/virtual_private_cloud_config.rst:620
+msgid "select the ACL rule, then click OK."
+msgstr "选择ACL规则，然后点击OK按钮。"
+
+# a324b1ff2ee443c885f67b4510b32b3e
+#: ../../networking/virtual_private_cloud_config.rst:622
+msgid ""
+"Wait for few seconds. You can see that the new ACL rule is displayed in the "
+"Details page."
+msgstr "稍等片刻。你就会看到新的ACL规则出现在详细页面里了。"
+
+# 9a47b3e0d1cf4da0990cb87352ca3de5
+#: ../../networking/virtual_private_cloud_config.rst:627
+msgid "Creating a Static Route"
+msgstr "创建一个静态静由。"
+
+# e189527e17704f7cab4e4e21f6b2549f
+#: ../../networking/virtual_private_cloud_config.rst:629
+msgid ""
+"CloudStack enables you to specify routing for the VPN connection you create."
+" You can enter one or CIDR addresses to indicate which traffic is to be "
+"routed back to the gateway."
+msgstr "CloudStack可以让你指定你创建的VPN链接的路由。你可以输入一个或CIDR地址来指定路由返回到网关的具体流量。"
+
+# b95c782aec15430ab351080cb9dc47ba
+#: ../../networking/virtual_private_cloud_config.rst:635
+msgid ""
+"In the Private Gateway page, click the IP address of the Private Gateway you"
+" want to work with."
+msgstr "在私有网关页面，点击你需要的私有网关的IP地址。"
+
+# f62c207d59b144dd8e5724167fb00821
+#: ../../networking/virtual_private_cloud_config.rst:638
+msgid "Select the Static Routes tab."
+msgstr "选择静态路由栏。"
+
+# 98e5544022bb4cf39452861c830d9665
+#: ../../networking/virtual_private_cloud_config.rst:640
+msgid "Specify the CIDR of destination network."
+msgstr "指定目标网络的CIDR。"
+
+# 35f9f527d4364d4db2faefcd92d3a394
+#: ../../networking/virtual_private_cloud_config.rst:644
+msgid "Wait for few seconds until the new route is created."
+msgstr "稍等片刻，新的路由就创建好了。"
+
+# f5f80f387b5246caa603111d30dcfab7
+#: ../../networking/virtual_private_cloud_config.rst:648
+msgid "Blacklisting Routes"
+msgstr "路由黑名单"
+
+# 8515025cd30a4b30b46f527ea9be5b2b
+#: ../../networking/virtual_private_cloud_config.rst:650
+msgid ""
+"CloudStack enables you to block a list of routes so that they are not "
+"assigned to any of the VPC private gateways. Specify the list of routes that"
+" you want to blacklist in the ``blacklisted.routes`` global parameter. Note "
+"that the parameter update affects only new static route creations. If you "
+"block an existing static route, it remains intact and continue functioning. "
+"You cannot add a static route if the route is blacklisted for the zone."
+msgstr "CloudStack允许你定义一个路由黑名单，这样它们就不能关联到任何VPC私有网关。你需要在全局参数blacklisted.routes里定义。要注意，此参数只在新路由创建时才会生效。如果你在黑名单里加入了已存在的静态路由，则此静态路由还是会继续起作用。你不能把在路由黑名单里的路由加入到静态路由当中去。"
+
+# 0a8f5a5461c9432188d46d5dc80a91a0
+#: ../../networking/virtual_private_cloud_config.rst:660
+msgid "Deploying VMs to the Tier"
+msgstr "将虚拟机部署到层。"
+
+# ad6ac67751dc4a668c90b3901921cecf
+#: ../../networking/virtual_private_cloud_config.rst:674
+msgid ""
+"The VPC page is displayed where all the tiers you have created are listed."
+msgstr "所有创建好的层都会有VPC页面里列出来。"
+
+# 8da453ba01704444966e4877573b0073
+#: ../../networking/virtual_private_cloud_config.rst:677
+msgid "Click Virtual Machines tab of the tier to which you want to add a VM."
+msgstr "指向你想添加虚拟机的层，点击虚拟机栏。"
+
+# 7564a13e0be543f29abd89bd7ef0c987
+#: ../../networking/virtual_private_cloud_config.rst:679
+msgid "|add-vm-vpc.png|"
+msgstr "|add-vm-vpc.png|"
+
+# ceb06d16d0d545d79a24d120e0cc1557
+#: ../../networking/virtual_private_cloud_config.rst:681
+msgid "The Add Instance page is displayed."
+msgstr "添加实例的页面就会出现。"
+
+# e0c2b5aaefda4e768eca34fdf762257c
+#: ../../networking/virtual_private_cloud_config.rst:683
+msgid ""
+"Follow the on-screen instruction to add an instance. For information on "
+"adding an instance, see the Installation Guide."
+msgstr "按照屏幕所指示的操作加入实例。至于如何添加实例，参照安装指南文档。"
+
+# 23b31383376b429ab397c708f57a73bb
+#: ../../networking/virtual_private_cloud_config.rst:688
+msgid "Deploying VMs to VPC Tier and Shared Networks"
+msgstr "在VPC层中部署虚拟，共享网络。"
+
+# 2bac09bc2c4a4906abd70bb5d83a5111
+#: ../../networking/virtual_private_cloud_config.rst:690
+msgid ""
+"CloudStack allows you deploy VMs on a VPC tier and one or more shared "
+"networks. With this feature, VMs deployed in a multi-tier application can "
+"receive monitoring services via a shared network provided by a service "
+"provider."
+msgstr "CloudStack允许你在VPC层中部署虚拟机和共享网络。有了这个功能，分布在多层当中的虚拟机可以通过共享网络接收到监控服务。"
+
+# e86ba5c678024942ba0da9ff54dd94ae
+#: ../../networking/virtual_private_cloud_config.rst:695
+msgid "Log in to the CloudStack UI as an administrator."
+msgstr "用系统管理员登陆到CloudStack UI界面。"
+
+# 50b2ea4e91a94d79b91efe6ba058dadd
+#: ../../networking/virtual_private_cloud_config.rst:697
+msgid "In the left navigation, choose Instances."
+msgstr "在左边的导航栏里，选择实例。"
+
+# 0f4af44df518497191f2b3af865061d2
+#: ../../networking/virtual_private_cloud_config.rst:699
+msgid "Click Add Instance."
+msgstr "点击添加实例。"
+
+# a5a3bb272f26416fa231be8972453e35
+#: ../../networking/virtual_private_cloud_config.rst:701
+msgid "Select a zone."
+msgstr "选择一个区域。"
+
+# 51a5385be8d5470b859a693b22b5c52b
+#: ../../networking/virtual_private_cloud_config.rst:703
+msgid "Select a template or ISO, then follow the steps in the wizard."
+msgstr "选择一个模板或ISO，按向导步骤操作。 "
+
+# bb1283c54a10494a96923abd8273c452
+#: ../../networking/virtual_private_cloud_config.rst:705
+msgid ""
+"Ensure that the hardware you have allows starting the selected service "
+"offering."
+msgstr "请确认你的硬件支持所选择的服务方案。"
+
+# afcf609fa1fb4cc5a296c5eb20e7c9f5
+#: ../../networking/virtual_private_cloud_config.rst:708
+msgid ""
+"Under Networks, select the desired networks for the VM you are launching."
+msgstr "在网络导航栏，选择你希望虚拟机所在的网络。"
+
+# f749aa3668cd4b44bb2ebeff764f56dd
+#: ../../networking/virtual_private_cloud_config.rst:711
+msgid "You can deploy a VM to a VPC tier and multiple shared networks."
+msgstr "你可以将虚拟机部署在一个拥有多个共享网络的VPC层中。"
+
+# b0aa4f80622f4438a373dce39b0c6537
+#: ../../networking/virtual_private_cloud_config.rst:713
+msgid "|addvm-tier-sharednw.png|"
+msgstr "|addvm-tier-sharednw.png|"
+
+# d3d95e78e214447ab42817d669d4fb61
+#: ../../networking/virtual_private_cloud_config.rst:715
+msgid "Click Next, review the configuration and click Launch."
+msgstr "点击下一步，审看已配置信息，然后点击启动。"
+
+# 2f1d867de64e4eef8f377943f7f76f2b
+#: ../../networking/virtual_private_cloud_config.rst:717
+msgid "Your VM will be deployed to the selected VPC tier and shared network."
+msgstr "你的这个虚拟机就已被部署到所选择的VPC层和共享网络中。"
+
+# 5dfeffe5b39b420b8932120cf5a86f75
+#: ../../networking/virtual_private_cloud_config.rst:721
+msgid "Acquiring a New IP Address for a VPC"
+msgstr "VPC获取新的IP地址。"
+
+# 31693458308e43659d6be92a4f78c332
+#: ../../networking/virtual_private_cloud_config.rst:723
+msgid ""
+"When you acquire an IP address, all IP addresses are allocated to VPC, not "
+"to the guest networks within the VPC. The IPs are associated to the guest "
+"network only when the first port-forwarding, load balancing, or Static NAT "
+"rule is created for the IP or the network. IP can't be associated to more "
+"than one network at a time."
+msgstr "当获取IP地址时，所有的IP地址会被分配到该VPC，而不是VPC中的用户网络。只有当在IP或用户网络上创建第一个网络规则（端口映射、负载均衡、静态NAT）时，该IP才会关联到用户网络。一个IP不能同时关联一个以上的网络。"
+
+# 075db32f8684487ebf86e97f17da3fb0
+#: ../../networking/virtual_private_cloud_config.rst:766
+msgid "Select IP Addresses."
+msgstr "选择IP地址。"
+
+# ca26d66e3c0644258b7e33c973c87793
+#: ../../networking/virtual_private_cloud_config.rst:768
+msgid "The Public IP Addresses page is displayed."
+msgstr "公网IP地址页面就显示出来。"
+
+# 501fe4755a8a4045952f5337c4e34ad3
+#: ../../networking/virtual_private_cloud_config.rst:770
+msgid "Click Acquire New IP, and click Yes in the confirmation dialog."
+msgstr "点击获得一个新IP, 并且在确认的对话框中点击确定."
+
+# 6654947db0c74b30bedc7c3644dad688
+#: ../../networking/virtual_private_cloud_config.rst:772
+msgid ""
+"You are prompted for confirmation because, typically, IP addresses are a "
+"limited resource. Within a few moments, the new IP address should appear "
+"with the state Allocated. You can now use the IP address in port forwarding,"
+" load balancing, and static NAT rules."
+msgstr "因为通常IP地址是有限资源，系统会提示您确认。 在稍等片刻之后，新的IP地址将会出现并且状态是已分配。现在您就可以使用这个IP地址做端口转发、负载均衡或静态NAT。"
+
+# 8c7d4d3811bd4e5a9cdc8fd5b9fc07a4
+#: ../../networking/virtual_private_cloud_config.rst:779
+msgid "Releasing an IP Address Alloted to a VPC"
+msgstr "释放VPC分配的IP地址"
+
+# fa1d68cb193b4e8186bc44093bb34441
+#: ../../networking/virtual_private_cloud_config.rst:781
+msgid ""
+"The IP address is a limited resource. If you no longer need a particular IP,"
+" you can disassociate it from its VPC and return it to the pool of available"
+" addresses. An IP address can be released from its tier, only when all the "
+"networking ( port forwarding, load balancing, or StaticNAT ) rules are "
+"removed for this IP address. The released IP address will still belongs to "
+"the same VPC."
+msgstr "IP地址是有限资源。如果您不再需要某个IP，请解除该IP和VPC的关联，使其返回到可用地址池中。只有当IP上所有的网络规则(端口映射、负载均衡、静态NAT)都删除后，该IP才能从所属层释放。释放的IP仍属于该VPC。"
+
+# 2ce137b1395747dc8e893c80bcda0e22
+#: ../../networking/virtual_private_cloud_config.rst:797
+msgid "Click the Configure button of the VPC whose IP you want to release."
+msgstr "点击要释放IP的VPC的配置按钮。"
+
+# 9fd161045cbe45a281c9d8e874926856
+#: ../../networking/virtual_private_cloud_config.rst:824
+msgid "Select Public IP Addresses."
+msgstr "选择公网IP地址。"
+
+# 5efdb9a8c3284fe195862d5624cd2ad7
+#: ../../networking/virtual_private_cloud_config.rst:828
+msgid "Click the IP you want to release."
+msgstr "点击要释放的IP地址。"
+
+# 2a495a61f8ae472bb5500bb1d609c595
+#: ../../networking/virtual_private_cloud_config.rst:830
+msgid "In the Details tab, click the Release IP button |release-ip-icon.png|"
+msgstr "在详细查看栏，点击释放IP按钮。 |release-ip-icon.png|"
+
+# 0d6369bc16a24d93ab131097fa1c26d0
+#: ../../networking/virtual_private_cloud_config.rst:836
+msgid "Enabling or Disabling Static NAT on a VPC"
+msgstr "VPC中启用或禁用静态NAT"
+
+# ca62a217246f4a06a8d12965cdfa849c
+#: ../../networking/virtual_private_cloud_config.rst:838
+msgid ""
+"A static NAT rule maps a public IP address to the private IP address of a VM"
+" in a VPC to allow Internet traffic to it. This section tells how to enable "
+"or disable static NAT for a particular IP address in a VPC."
+msgstr "静态NAT规则是将公网IP映射到VPC中虚机的私网IP，以便允许互联网流量访问该虚机。本节描述如何在VPC中启用或禁用某个公网IP地址的静态NAT。"
+
+# 2b8f37a180cf44aabf4c1102171a0a0f
+#: ../../networking/virtual_private_cloud_config.rst:863
+msgid "For each tier, the following options are displayed."
+msgstr "对于每一个层，会显示以下选项。"
+
+# 27a3e8f27ef74f348d38e0a750d4b22d
+#: ../../networking/virtual_private_cloud_config.rst:889
+msgid "Click the IP you want to work with."
+msgstr "点击您要操作的IP。"
+
+# cdf3e4bc65504a1ba280c33c311c5ff3
+#: ../../networking/virtual_private_cloud_config.rst:891
+msgid ""
+"In the Details tab,click the Static NAT button. |enable-disable.png| The "
+"button toggles between Enable and Disable, depending on whether static NAT "
+"is currently enabled for the IP address."
+msgstr "在“详细信息”页，点击静态NAT按钮|enable-disable.png| 。该按钮会根据公网IP的静态NAT当前状态，在启用和禁用间切换。"
+
+# 5d57c9b6170d475cb726d63bd8a7d4b4
+#: ../../networking/virtual_private_cloud_config.rst:896
+msgid "If you are enabling static NAT, a dialog appears as follows:"
+msgstr "如果是启用静态NAT，会显示如下对话框："
+
+# 8652f2ad4f894964b5749224fa457264
+#: ../../networking/virtual_private_cloud_config.rst:898
+msgid "|select-vmstatic-nat.png|"
+msgstr "|select-vmstatic-nat.png|"
+
+# 8642184696854f59a8be93ce090ef2fb
+#: ../../networking/virtual_private_cloud_config.rst:900
+msgid "Select the tier and the destination VM, then click Apply."
+msgstr "选择层和目标虚机，然后点击“应用”。"
+
+# 3f81050b54e046ce8e1509efface1df4
+#: ../../networking/virtual_private_cloud_config.rst:904
+msgid "Adding Load Balancing Rules on a VPC"
+msgstr "VPC中添加负载均衡规则"
+
+# 64775e05d52c4fd68cdf87d2e24c802f
+#: ../../networking/virtual_private_cloud_config.rst:906
+msgid ""
+"In a VPC, you can configure two types of load balancing: external LB and "
+"internal LB. External LB is nothing but a LB rule created to redirect the "
+"traffic received at a public IP of the VPC virtual router. The traffic is "
+"load balanced within a tier based on your configuration. Citrix NetScaler "
+"and VPC virtual router are supported for external LB. When you use internal "
+"LB service, traffic received at a tier is load balanced across different VMs"
+" within that tier. For example, traffic reached at Web tier is redirected to"
+" another VM in that tier. External load balancing devices are not supported "
+"for internal LB. The service is provided by a internal LB VM configured on "
+"the target tier."
+msgstr "在VPC中，你可以配置外部或内部负载均衡。外部负载均衡就是将VPC虚拟路由器接收到的公网流量进行转发的规则。这个流量如何在层里进行均衡取决于你的配置。Citrix NetScaler 和 VPC virtual router都支持外部负载均衡。内部均衡是在层内的虚拟之间进行均衡。比如，到达WEB层请求的流量可以转发到此层另外的虚拟机。外部负载均衡设备不支持内部均衡。内部负载均衡的服务是由目标层的内部虚拟机配置后提供支持服务的。"
+
+# 5f34d7b800174adea102238371bbf537
+#: ../../networking/virtual_private_cloud_config.rst:919
+msgid "Load Balancing Within a Tier (External LB)"
+msgstr "在层内进行负载均衡(外部负载均衡)"
+
+# 060c73cf4ee8497d961587b4e5e88f8e
+#: ../../networking/virtual_private_cloud_config.rst:921
+msgid ""
+"A CloudStack user or administrator may create load balancing rules that "
+"balance traffic received at a public IP to one or more VMs that belong to a "
+"network tier that provides load balancing service in a VPC. A user creates a"
+" rule, specifies an algorithm, and assigns the rule to a set of VMs within a"
+" tier."
+msgstr " CloudStack用户或管理员可以创建负载均衡规则。负载均衡规则用于将一个公网IP的流量分担到在VPC提供负载均衡服务的网络层内的一个或多个VM中。用户可以创建规则，指定算法，然后将规则指定到VPC的一套VM中。"
+
+# e988811e64294d9690e628d0a32d6f6e
+#: ../../networking/virtual_private_cloud_config.rst:929
+msgid "Enabling NetScaler as the LB Provider on a VPC Tier"
+msgstr "在VPC层中启用基于NetScaler的负载均衡"
+
+# 1a47a4579a094d95b8a0de664ef21a91
+#: ../../networking/virtual_private_cloud_config.rst:931
+msgid "Add and enable Netscaler VPX in dedicated mode."
+msgstr "添加并启用 Netscaler VPX独立模块。"
+
+# 9cd82ffd68b24939ae095006b094d212
+#: ../../networking/virtual_private_cloud_config.rst:933
+msgid ""
+"Netscaler can be used in a VPC environment only if it is in dedicated mode."
+msgstr "Netscaler只能在独立模块的形式下应用于VPC环境中。"
+
+# b3484bb76994414e9ea417121e40d040
+#: ../../networking/virtual_private_cloud_config.rst:936
+msgid ""
+"Create a network offering, as given in \":ref:`create-net-offering-ext-"
+"lb`\"."
+msgstr "创建启用持久化选项的网络方案。请参考\":ref:`create-net-offering-ext-lb`\"."
+
+# 121f69be457f40c5a9230d5ea3592bfb
+#: ../../networking/virtual_private_cloud_config.rst:938
+msgid "Create a VPC with Netscaler as the Public LB provider."
+msgstr "在VPC中创建一个基于Netscaler的公用负载均衡。"
+
+# e3da4dec088145cdab1337246f694c25
+#: ../../networking/virtual_private_cloud_config.rst:940
+msgid ""
+"For more information, see `\"Adding a Virtual Private Cloud\" <#adding-a"
+"-virtual-private-cloud>`_."
+msgstr "更多信息，请参考 `\"添加一个VPC\" <#adding-a-virtual-private-cloud>`_."
+
+# a9a66b4ea7f240caa72b7230eb594dca
+#: ../../networking/virtual_private_cloud_config.rst:943
+msgid "For the VPC, acquire an IP."
+msgstr "在VPC中获取一个IP地址。"
+
+# 41f7df1af1ff4bd8b55750efc9e38211
+#: ../../networking/virtual_private_cloud_config.rst:945
+msgid ""
+"Create an external load balancing rule and apply, as given in :ref:`create-"
+"ext-lb-rule`."
+msgstr "创建并应用一个外部负载均衡规则。请参考:ref:`create-ext-lb-rule`."
+
+# 6f16d85076c347eb9f22335560475ef4
+#: ../../networking/virtual_private_cloud_config.rst:952
+msgid "Creating a Network Offering for External LB"
+msgstr "创建一个外部负载均衡网络方案"
+
+# 709e2fd0e27745f68f26028a48c613a5
+#: ../../networking/virtual_private_cloud_config.rst:954
+msgid ""
+"To have external LB support on VPC, create a network offering as follows:"
+msgstr "要在VPC中启用外部负载均衡支持，依如下操作建立网络方案："
+
+# 76d5fee0b6ef4598b2f4f80ee690c974
+# 80171134c89b4246b8e6d948ddf36a21
+#: ../../networking/virtual_private_cloud_config.rst:957
+#: ../../networking/virtual_private_cloud_config.rst:1163
+msgid "Log in to the CloudStack UI as a user or admin."
+msgstr "使用用户或管理员登录到CloudStack用户界面。"
+
+# d6358f1cb80b45c6becf012d6670f0ff
+# 19877c93762c4d95b38bfafc90fc110c
+#: ../../networking/virtual_private_cloud_config.rst:959
+#: ../../networking/virtual_private_cloud_config.rst:1165
+msgid "From the Select Offering drop-down, choose Network Offering."
+msgstr "下拉选择方案，选择网络方案："
+
+# 34b1dc57da234cfcbef32cbb10126c3c
+# 1bba2b0d34da443ea11b5a194c8a3b59
+#: ../../networking/virtual_private_cloud_config.rst:963
+#: ../../networking/virtual_private_cloud_config.rst:1169
+msgid "In the dialog, make the following choices:"
+msgstr "在对话框中，选择如下操作："
+
+# 86e34c74e6134c7bb7c04554bfed9df0
+# 4e3f1479665d42f78ead497e7f965f00
+#: ../../networking/virtual_private_cloud_config.rst:965
+#: ../../networking/virtual_private_cloud_config.rst:1171
+msgid "**Name**: Any desired name for the network offering."
+msgstr "**名称**: 任何网络方案的名称。"
+
+# c960eb115c114434af67b0fbc25be487
+# bc5490caeeff4328865c3f318b98cfee
+#: ../../networking/virtual_private_cloud_config.rst:967
+#: ../../networking/virtual_private_cloud_config.rst:1173
+msgid ""
+"**Description**: A short description of the offering that can be displayed "
+"to users."
+msgstr "**描述**: 提供一个简短的方案描述。 "
+
+# 84e47db19f574c3ba5d0b2f1154fbc45
+# 93388787993544a4901e262399be3022
+#: ../../networking/virtual_private_cloud_config.rst:970
+#: ../../networking/virtual_private_cloud_config.rst:1176
+msgid "**Network Rate**: Allowed data transfer rate in MB per second."
+msgstr "**网络速度**: 允许的数据传输速度（MB/秒）。"
+
+# 816b6192dc2f4e3ca02aeb6804edb355
+# 27411d0400294e9ba1bfb67609002343
+#: ../../networking/virtual_private_cloud_config.rst:972
+#: ../../networking/virtual_private_cloud_config.rst:1178
+msgid ""
+"**Traffic Type**: The type of network traffic that will be carried on the "
+"network."
+msgstr "**流量类型**: 允许承载的网络流量类型。"
+
+# c74a767bceed4a628199500712d7c8c7
+# eb0786cb716a4706a211b3b6088bb4b9
+#: ../../networking/virtual_private_cloud_config.rst:975
+#: ../../networking/virtual_private_cloud_config.rst:1181
+msgid ""
+"**Guest Type**: Choose whether the guest network is isolated or shared."
+msgstr "**来宾类型**: 选择来宾网络为隔离或共享网络。"
+
+# c522088c1c6e47d79f06f5fe842e40ee
+# 0aea3f7e943e49b291046f8fc45d6484
+#: ../../networking/virtual_private_cloud_config.rst:978
+#: ../../networking/virtual_private_cloud_config.rst:1184
+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."
+msgstr "**持续性**: 表明来宾网络是否支持持续性。无需提供任何VM部署的网络，称之为持续性网络。"
+
+# b84887ec1f6c4513aa057f3a630484a1
+# 930505e9acaa4d9193047e12ab7c3a3e
+#: ../../networking/virtual_private_cloud_config.rst:982
+#: ../../networking/virtual_private_cloud_config.rst:1188
+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\" <#about-virtual-private-clouds>`_."
+msgstr "**VPC**: 此选项表明是否在来宾网络中启用VPC。 CloudStack中的虚拟专用云(VPC)是专用、隔离的。 一个VPC可以有一个类似于传统物理网络的虚拟网络拓扑结构。有关的VPC的详细信息，请参考`\"关于VPC\" <#about-virtual-private-clouds>`_."
+
+# ed834a8fdce7467eb36d015cba5a8227
+# dbc9e89b121148e296344a7619ca01db
+#: ../../networking/virtual_private_cloud_config.rst:988
+#: ../../networking/virtual_private_cloud_config.rst:1195
+msgid ""
+"**Specify VLAN**: (Isolated guest networks only) Indicate whether a VLAN "
+"should be specified when this offering is used."
+msgstr "**指定**: (仅隔离的来宾网络) 表明在使用这个网络方案时，是否指定VLAN。"
+
+# 6e7a1944576040bbb72e01310aa2b99d
+#: ../../networking/virtual_private_cloud_config.rst:991
+msgid ""
+"**Supported Services**: Select Load Balancer. Use Netscaler or "
+"VpcVirtualRouter."
+msgstr "**支持服务**:选择负载均衡，使用Netscaler 或 VpcVirtualRouter."
+
+# 89f5557a4a6546158f9fdc778ad029c1
+#: ../../networking/virtual_private_cloud_config.rst:994
+msgid "**Load Balancer Type**: Select Public LB from the drop-down."
+msgstr "**负载均衡类型**:从下拉列表里选择公用负载均衡。"
+
+# 7a932d710a9843c0af0b0cf4522a5284
+#: ../../networking/virtual_private_cloud_config.rst:996
+msgid ""
+"**LB Isolation**: Select Dedicated if Netscaler is used as the external LB "
+"provider."
+msgstr "**负载均衡隔离**: 如果使用Netscale作为外部负载均衡，选择此项进行隔离。"
+
+# 4ac8eb66ecab474195206ca9dd076d42
+# fe97ea397c194e4284760800bee72bea
+#: ../../networking/virtual_private_cloud_config.rst:999
+#: ../../networking/virtual_private_cloud_config.rst:1203
+msgid ""
+"**System Offering**: Choose the system service offering that you want "
+"virtual routers to use in this network."
+msgstr "**系统方案**: 选择你想在这个网络中使用的虚拟路由器的系统服务方案。"
+
+# fdf046b7980844e19139feacede80d66
+# 6f5f9241b8e1492a846b95d1bf8c9fe1
+#: ../../networking/virtual_private_cloud_config.rst:1002
+#: ../../networking/virtual_private_cloud_config.rst:1206
+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."
+msgstr "**保护模式**: 表明是否使用保护模式。在这个模式中，只有网络中第一个虚拟机启动时才分配网络资源。"
+
+# d3ed6db3fe1745b78b2b927bc7d01a53
+# c9781285467f4ad1b249ead320965229
+#: ../../networking/virtual_private_cloud_config.rst:1006
+#: ../../networking/virtual_private_cloud_config.rst:1210
+msgid "Click OK and the network offering is created."
+msgstr "点击OK按钮，网络方案就创建好了。"
+
+# 88f68116cf4240d1b534cf9122dca89d
+#: ../../networking/virtual_private_cloud_config.rst:1012
+msgid "Creating an External LB Rule"
+msgstr "创建一个外部负载均衡规则"
+
+# 08a7150e85df4a9f8efd234f87de819b
+#: ../../networking/virtual_private_cloud_config.rst:1023
+msgid ""
+"Click the Configure button of the VPC, for which you want to configure load "
+"balancing rules."
+msgstr "点击要配置负载均衡规则的VPC的配置按钮。"
+
+# ea4d0a7fdac64d889620ae55b699113e
+# 0d81aa1b316a4977838e69024fa1072a
+#: ../../networking/virtual_private_cloud_config.rst:1026
+#: ../../networking/virtual_private_cloud_config.rst:1239
+msgid ""
+"The VPC page is displayed where all the tiers you created listed in a "
+"diagram."
+msgstr "系统会显示VPC页面，您创建的所有层都列在图中。"
+
+# a5ab0f5fbd054d0790aeb9802997b2d0
+# 5ff05892aa8e4255bd7bc42730f2c699
+#: ../../networking/virtual_private_cloud_config.rst:1060
+#: ../../networking/virtual_private_cloud_config.rst:1328
+msgid "Select the tier to which you want to apply the rule."
+msgstr "选择应用规则的层。"
+
+# ef5c662d47e24cd2bd98a84a97bf37cd
+#: ../../networking/virtual_private_cloud_config.rst:1066
+msgid ""
+"**Public Port**: The port that receives the incoming traffic to be balanced."
+msgstr "**公网端口**: 接收待负载均衡的流入流量的端口。"
+
+# 36f023f1ff9f4854a6413a29e48a1be5
+# 4842c5ef77d840658853291a3ee85181
+#: ../../networking/virtual_private_cloud_config.rst:1072
+#: ../../networking/virtual_private_cloud_config.rst:1268
+msgid ""
+"**Algorithm**. Choose the load balancing algorithm you want CloudStack to "
+"use. CloudStack supports the following well-known algorithms:"
+msgstr "**算法**。选择您希望CloudStack 使用的负载均衡算法。CloudStack 支持下列知名的算法："
+
+# 70c9123d5f194ebf9c345f9ad993cdc0
+# 7ac4ebb233324a8eb27698cc7a04a5be
+#: ../../networking/virtual_private_cloud_config.rst:1078
+#: ../../networking/virtual_private_cloud_config.rst:1274
+msgid "Least connections"
+msgstr "最少连接"
+
+# 23d0139cefac4b7a805b0d7e4a1a43e5
+# 7eeb60a40f294f1dacce7d723e8e193c
+#: ../../networking/virtual_private_cloud_config.rst:1080
+#: ../../networking/virtual_private_cloud_config.rst:1276
+msgid "Source"
+msgstr "源IP"
+
+# 75a5279c04344957bc0a080be77c8274
+#: ../../networking/virtual_private_cloud_config.rst:1082
+msgid ""
+"**Stickiness**. (Optional) Click Configure and choose the algorithm for the "
+"stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr "**粘性**. (可选)点击配置，选择粘性策略使用的算法。参见负载均衡规则的粘性会话策略。"
+
+# 43d9888e2f9440e984b9541afc588eea
+#: ../../networking/virtual_private_cloud_config.rst:1086
+msgid ""
+"**Add VMs**: Click Add VMs, then select two or more VMs that will divide the"
+" load of incoming traffic, and click Apply."
+msgstr "点击添加VM，选择两个或更多的VM分担流入的流量，然后点击应用。"
+
+# 59f6f69006154b2f8ce3eb5d9e9e5351
+#: ../../networking/virtual_private_cloud_config.rst:1089
+msgid ""
+"The new load balancing rule appears in the list. You can repeat these steps "
+"to add more load balancing rules for this IP address."
+msgstr "新的负载均衡策略会显示在列表中。您可以重复以上步骤为该IP地址添加更多的负载均衡策略。"
+
+# b829d10e71d44f6eae3ea7663c35f418
+#: ../../networking/virtual_private_cloud_config.rst:1094
+msgid "Load Balancing Across Tiers"
+msgstr "跨越层的负载均衡"
+
+# ee38327ce5984aab9e56b1a4096f683f
+#: ../../networking/virtual_private_cloud_config.rst:1096
+msgid ""
+"CloudStack supports sharing workload across different tiers within your VPC."
+" Assume that multiple tiers are set up in your environment, such as Web tier"
+" and Application tier. Traffic to each tier is balanced on the VPC virtual "
+"router on the public side, as explained in `\"Adding Load Balancing Rules on"
+" a VPC\" <#adding-load-balancing-rules-on-a-vpc>`_. If you want the traffic "
+"coming from the Web tier to the Application tier to be balanced, use the "
+"internal load balancing feature offered by CloudStack."
+msgstr "CloudStack支持在VPC内不同层之间共享工作负载。这需要先在你的环境里设置好多个层，比如WEB层，应用层。每一个层的流量通过VPC虚拟路由机进行负载均衡。关于这方面的内容， `\"在VPC里添加负载均衡规则\" <#adding-load-balancing-rules-on-a-vpc>`_. 如果你想将WEB层发向应用层的流量进行负载均衡，需要使用Cloudstack的内部负载均衡功能。"
+
+# d83d8db5511d4aba8c9c4efd61e0f5e6
+#: ../../networking/virtual_private_cloud_config.rst:1107
+msgid "How Does Internal LB Work in VPC?"
+msgstr "在VPC中，内部负载均衡是如何工作的呢？"
+
+# c710a43f15e34b5ab71f20ea2709e950
+#: ../../networking/virtual_private_cloud_config.rst:1109
+msgid ""
+"In this figure, a public LB rule is created for the public IP 72.52.125.10 "
+"with public port 80 and private port 81. The LB rule, created on the VPC "
+"virtual router, is applied on the traffic coming from the Internet to the "
+"VMs on the Web tier. On the Application tier two internal load balancing "
+"rules are created. An internal LB rule for the guest IP 10.10.10.4 with load"
+" balancer port 23 and instance port 25 is configured on the VM, "
+"InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.4 with "
+"load balancer port 45 and instance port 46 is configured on the VM, "
+"InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.6, with "
+"load balancer port 23 and instance port 25 is configured on the VM, "
+"InternalLBVM2."
+msgstr "在这个图中，公网负载均衡规则是这样创建的：公网IP为IP 72.52.125.10，外网端口为80，内网端口为81。VPC的虚拟路由机创建的负载均衡规则将互联网的流量分配到WEB层的各个虚拟机上。在应用层创建了两个内部负载均衡规则。其中一个规则是：客户IP为10.10.10.4的将端口23进行负载分发，实例VM和InternalLBVM1的端口25进行了负载。另一条规则是：客户IP为10.10.10.4的将端口45进行负载分发，实例VM和InternalLBVM1的端口46进行了负载。另一条规则是：客户IP为10.10.10.6的将端口23进行负载分发，实例VM和InternalLBVM1的端口25进行了负载。（两条规则还是三条规则？原文如此，希望图示能明解）"
+
+# 37cf27e0f1d34d6eb0aed4b83bbd2b4c
+#: ../../networking/virtual_private_cloud_config.rst:1121
+msgid "|vpc-lb.png|"
+msgstr "|vpc-lb.png|"
+
+# 2ebee5edba904c0a9de6b022c5d1e3d8
+#: ../../networking/virtual_private_cloud_config.rst:1127
+msgid ""
+"Internal LB and Public LB are mutually exclusive on a tier. If the tier has "
+"LB on the public side, then it can't have the Internal LB."
+msgstr "内部和公网负载均衡在一个层里往往是互斥的。如果一个层已应用了公网负载均衡之后，此层就不能再应用内部负载均衡。"
+
+# 82754be2930f483c83607cde35e73470
+#: ../../networking/virtual_private_cloud_config.rst:1130
+msgid ""
+"Internal LB is supported just on VPC networks in CloudStack 4.2 release."
+msgstr "在 CloudStack 4.2版本中，只有VPC网络支持内部负载均衡。"
+
+# a8769b5a4a9e48caab6c9ecc82e77234
+#: ../../networking/virtual_private_cloud_config.rst:1133
+msgid ""
+"Only Internal LB VM can act as the Internal LB provider in CloudStack 4.2 "
+"release."
+msgstr "在CloudStack 4.2 版本中，只有Internal LB VM才能作内部负载均衡的提供方。"
+
+# b076139f831c4e3ba6417259ac863de8
+#: ../../networking/virtual_private_cloud_config.rst:1136
+msgid ""
+"Network upgrade is not supported from the network offering with Internal LB "
+"to the network offering with Public LB."
+msgstr "将网络方案由内部负载均衡更改为公网负载均衡是不可行的。"
+
+# 969d6f5939874bca859151e7d0d68447
+#: ../../networking/virtual_private_cloud_config.rst:1139
+msgid "Multiple tiers can have internal LB support in a VPC."
+msgstr "在VPC中，多层可以应用内部负载均衡。"
+
+# 67372cabb36b437a8232a78a78f08515
+#: ../../networking/virtual_private_cloud_config.rst:1141
+msgid "Only one tier can have Public LB support in a VPC."
+msgstr "在VPC中，只有一层只支持公网负载均衡。"
+
+# 69768caec218466dafc06876ae8e797f
+#: ../../networking/virtual_private_cloud_config.rst:1145
+msgid "Enabling Internal LB on a VPC Tier"
+msgstr "在VPC层上启用内部负载均衡功能"
+
+# daf581a704674dc287b6516c737b20e9
+#: ../../networking/virtual_private_cloud_config.rst:1147
+msgid ""
+"Create a network offering, as given in :ref:`creating-net-offering-internal-"
+"lb`."
+msgstr "创建一个新的网络方案，请参考:ref:`creating-net-offering-internal-lb`."
+
+# a3b6f09db9e44bc597c6dd364de8f2ec
+#: ../../networking/virtual_private_cloud_config.rst:1150
+msgid ""
+"Create an internal load balancing rule and apply, as given in :ref:`create-"
+"int-lb-rule`."
+msgstr "创建并应用一个内部负载均衡规则。参考:ref:`create-int-lb-rule`."
+
+# e6d4695c11f545a09e177701ad41e3c4
+#: ../../networking/virtual_private_cloud_config.rst:1157
+msgid "Creating a Network Offering for Internal LB"
+msgstr "创建一个内部负载均衡网络方案"
+
+# b711b583939045f2b881dd3d65a60666
+#: ../../networking/virtual_private_cloud_config.rst:1159
+msgid ""
+"To have internal LB support on VPC, either use the default offering, "
+"DefaultIsolatedNetworkOfferingForVpcNetworksWithInternalLB, or create a "
+"network offering as follows:"
+msgstr "要在VPC当中使用内部负载均衡，可以使用默认的DefaultIsolatedNetworkOfferingForVpcNetworksWithInternalLB,或按如下操作新建一个网络方案："
+
+# 3248edb0427641c389adc91e927709f9
+#: ../../networking/virtual_private_cloud_config.rst:1198
+msgid ""
+"**Supported Services**: Select Load Balancer. Select ``InternalLbVM`` from "
+"the provider list."
+msgstr "**支持服务**: 选择负载均衡，从待提供的下拉列表里选择`InternalLbVM。"
+
+# e7e35dcafc134423bff098fbd63e22e9
+#: ../../networking/virtual_private_cloud_config.rst:1201
+msgid "**Load Balancer Type**: Select Internal LB from the drop-down."
+msgstr "**负载均衡类型**: 从下拉列表里选择内部负载均衡。"
+
+# 56e0a94386164762912004a783f992e4
+#: ../../networking/virtual_private_cloud_config.rst:1216
+msgid "Creating an Internal LB Rule"
+msgstr "创建一个内部负载均衡规则"
+
+# 89853887164549829b5d2bf60bd1820d
+#: ../../networking/virtual_private_cloud_config.rst:1218
+msgid ""
+"When you create the Internal LB rule and applies to a VM, an Internal LB VM,"
+" which is responsible for load balancing, is created."
+msgstr "当你创建好一个内部负载均衡规则，并将之用于一个虚拟之后，一个内部负载均衡的应用就建立起来了。"
+
+# 353f381499f141628587960d6e26f5b0
+#: ../../networking/virtual_private_cloud_config.rst:1221
+msgid ""
+"You can view the created Internal LB VM in the Instances page if you "
+"navigate to **Infrastructure** > **Zones** > <zone\\_ name> > "
+"<physical\\_network\\_name> > **Network Service Providers** > **Internal LB "
+"VM**. You can manage the Internal LB VMs as and when required from the "
+"location."
+msgstr "你可以在实例页面中查看创建的内部LB VM 按如下导航 **基础构架** > **区域** > <zone\\_ name> > <physical\\_network\\_name> > **网络服务提供** > **内部负载均衡虚拟机**，你就可以看到已创建了内部负载均衡的实例上。也可以在此进行内部负载均衡的管理。"
+
+# 695b01da42ba4aafa25052faf19cfb61
+#: ../../networking/virtual_private_cloud_config.rst:1236
+msgid ""
+"Locate the VPC for which you want to configure internal LB, then click "
+"Configure."
+msgstr "点击要配置内部负载均衡规则的VPC的配置按钮。"
+
+# 353f4dce86ad490c9f02ffb55550faf1
+#: ../../networking/virtual_private_cloud_config.rst:1242
+msgid ""
+"Locate the Tier for which you want to configure an internal LB rule, click "
+"Internal LB."
+msgstr "指向你想配置内部负载均衡的层，点击内部负载均衡。"
+
+# 2950ef7334d8445db81781a662805752
+#: ../../networking/virtual_private_cloud_config.rst:1245
+msgid "In the Internal LB page, click Add Internal LB."
+msgstr "在 Internal LB页面里，点击添加 Internal LB。"
+
+# c7bb9deb227d41a08b2d4a17f0c56272
+#: ../../networking/virtual_private_cloud_config.rst:1247
+msgid "In the dialog, specify the following:"
+msgstr "在对话框里，定义以下内容："
+
+# acee91ffe73343149992e4445c25639d
+#: ../../networking/virtual_private_cloud_config.rst:1251
+msgid ""
+"**Description**: A short description of the rule that can be displayed to "
+"users."
+msgstr "**描述**: 提供一个简短的规则描述。 "
+
+# 21c16720a2424baba66dd99f17596511
+#: ../../networking/virtual_private_cloud_config.rst:1254
+msgid ""
+"**Source IP Address**: (Optional) The source IP from which traffic "
+"originates. The IP is acquired from the CIDR of that particular tier on "
+"which you want to create the Internal LB rule. If not specified, the IP "
+"address is automatically allocated from the network CIDR."
+msgstr "**源IP地址**: (可选) 是指产生流量的源IP地址。这个地址是从你创建内部负载均衡的层中的CIDR中获取的。如果没有指定，则系统会自动从CIDR中分配。"
+
+# 09ee6ad213fe4332930cd10d34913eba
+#: ../../networking/virtual_private_cloud_config.rst:1260
+msgid ""
+"For every Source IP, a new Internal LB VM is created for load balancing."
+msgstr "对于每一个源IP地址，都可以建立一个针对它的内部负载均衡。"
+
+# d79a0aa56c2d43a99118d61cdee35de5
+#: ../../networking/virtual_private_cloud_config.rst:1263
+msgid ""
+"**Source Port**: The port associated with the source IP. Traffic on this "
+"port is load balanced."
+msgstr "**源端口**: 与源IP地址关联的端口，此端口上的流量是基于负载均衡的。"
+
+# 2aa21466b141411194bccbfbce825ad3
+#: ../../networking/virtual_private_cloud_config.rst:1266
+msgid "**Instance Port**: The port of the internal LB VM."
+msgstr "**实例端口**: 内部负载均衡虚拟机的端口。"
+
+# 519302d094284d71b5c6fb38328a1324
+#: ../../networking/virtual_private_cloud_config.rst:1280
+msgid "Adding a Port Forwarding Rule on a VPC"
+msgstr "在VPC里添加一个端口转发规则。"
+
+# 8637eb165f5a4accba725d09dc0f0a2b
+#: ../../networking/virtual_private_cloud_config.rst:1338
+msgid "**Protocol**: The communication protocol in use between the two ports."
+msgstr "**Protocol**: 两个端口之间所用的互联协议。"
+
+# 6acdc3f1bfe647e8bc3f77d1c6ebe7cc
+#: ../../networking/virtual_private_cloud_config.rst:1341
+msgid "TCP"
+msgstr "TCP"
+
+# a94613fd8a23416cbcd8dddc6013a988
+#: ../../networking/virtual_private_cloud_config.rst:1343
+msgid "UDP"
+msgstr "UDP"
+
+# 10549636e52849679931a001d1d335eb
+#: ../../networking/virtual_private_cloud_config.rst:1345
+msgid ""
+"**Add VM**: Click Add VM. Select the name of the instance to which this rule"
+" applies, and click Apply."
+msgstr "**Add VM**: 点击增加虚拟机，选择你想将此规则应用上的虚拟机，点击应用。"
+
+# 5be772f552314f2d8e9cee0ff65bf489
+#: ../../networking/virtual_private_cloud_config.rst:1348
+msgid "You can test the rule by opening an SSH session to the instance."
+msgstr "你可以通过SSH连接实例来测试此规则。"
+
+# e0d8c785784b42e5b872d0d1e0e01fc8
+#: ../../networking/virtual_private_cloud_config.rst:1352
+msgid "Removing Tiers"
+msgstr "删除层"
+
+# 7568184600d04040b5e2be7097d75720
+#: ../../networking/virtual_private_cloud_config.rst:1354
+msgid ""
+"You can remove a tier from a VPC. A removed tier cannot be revoked. When a "
+"tier is removed, only the resources of the tier are expunged. All the "
+"network rules (port forwarding, load balancing and staticNAT) and the IP "
+"addresses associated to the tier are removed. The IP address still be "
+"belonging to the same VPC."
+msgstr "你可以从一个VPC中删除一个层。一个被删除的层是不能被擦除的。当一个层被删除后，只有层的资源被删去。所有的网络规则(端口转发，负载均衡，静态NAT)还有关联到此层的IP地址都会删除。但这些IP地址仍然属于这个VPC。"
+
+# f487d939ba954e449d7080e7517574a6
+#: ../../networking/virtual_private_cloud_config.rst:1372
+msgid ""
+"The Configure VPC page is displayed. Locate the tier you want to work with."
+msgstr "配置VPC的页面显示出来了。指向你需要操作的层。"
+
+# c7fbdf1d685a4919a2ea4a0624d9d045
+#: ../../networking/virtual_private_cloud_config.rst:1375
+msgid "Select the tier you want to remove."
+msgstr "选择你想删除的层。"
+
+# f5493869c62248649482971d798e37ca
+#: ../../networking/virtual_private_cloud_config.rst:1377
+msgid ""
+"In the Network Details tab, click the Delete Network button. |del-tier.png|"
+msgstr "在网络详细栏，点击删除网络按钮。|del-tier.png|"
+
+# aa755672baae4d7697f96b16039da071
+#: ../../networking/virtual_private_cloud_config.rst:1380
+msgid "Click Yes to confirm. Wait for some time for the tier to be removed."
+msgstr "点击YES按钮。稍等片片刻，层就会被删除了。"
+
+# 9b44d6e7259c4c4d88ddd3fbec0511de
+#: ../../networking/virtual_private_cloud_config.rst:1384
+msgid "Editing, Restarting, and Removing a Virtual Private Cloud"
+msgstr "编辑，重启，删除VPC。"
+
+# a72ab3649f44452fad64ca5e5c27699f
+#: ../../networking/virtual_private_cloud_config.rst:1386
+msgid "Ensure that all the tiers are removed before you remove a VPC."
+msgstr "在删除VPC前，需要先删除所有的层。"
+
+# 528e37d6eed24e24a482eda24bba84b4
+#: ../../networking/virtual_private_cloud_config.rst:1397
+msgid "Select the VPC you want to work with."
+msgstr "选择你需要的VPC。"
+
+# 85aecab9e0aa42e285e0946a9b7fc270
+#: ../../networking/virtual_private_cloud_config.rst:1399
+msgid "In the Details tab, click the Remove VPC button |remove-vpc.png|"
+msgstr "在详细栏，点击删除VPC按钮。|remove-vpc.png|"
+
+# d499762e52f543f7a82c853e728a5516
+#: ../../networking/virtual_private_cloud_config.rst:1401
+msgid ""
+"You can remove the VPC by also using the remove button in the Quick View."
+msgstr "你也可以在快速查看视图里点击删除按钮进行VPC的删除。"
+
+# db5c63c401ed457d8296666c3e708e2b
+#: ../../networking/virtual_private_cloud_config.rst:1404
+msgid ""
+"You can edit the name and description of a VPC. To do that, select the VPC, "
+"then click the Edit button. |vpc-edit-icon.png|"
+msgstr ""
+
+# 85223757733c41afac7e59be10812ad4
+#: ../../networking/virtual_private_cloud_config.rst:1407
+msgid ""
+"To restart a VPC, select the VPC, then click the Restart button. |restart-"
+"vpc.png|"
+msgstr "如果要重启一个VPC，点击重启按钮。|restart-vpc.png|"
+
+# c73707abeeee4762af99c2fe10074730
+#: ../../networking/persistent_networks.rst:18
+msgid "Persistent Networks"
+msgstr "持久化网络"
+
+# f57736d14d734e409d67507b6128fbec
+#: ../../networking/persistent_networks.rst:20
+msgid ""
+"The network that you can provision without having to deploy any VMs on it is"
+" called a persistent network. A persistent network can be part of a VPC or a"
+" non-VPC environment."
+msgstr "在不部署任何VM的情况下就初始化好的网络称为持久化网络。持久化网络可以是VPC的一部分，也可以不是。"
+
+# ce6fd8a3ec00423d86e7ba4f4cba6189
+#: ../../networking/persistent_networks.rst:24
+msgid ""
+"When you create other types of network, a network is only a database entry "
+"until the first VM is created on that network. When the first VM is created,"
+" a VLAN ID is assigned and the network is provisioned. Also, when the last "
+"VM is destroyed, the VLAN ID is released and the network is no longer "
+"available. With the addition of persistent network, you will have the "
+"ability to create a network in CloudStack in which physical devices can be "
+"deployed without having to run any VMs. Additionally, you can deploy "
+"physical devices on that network."
+msgstr "在您创建其它类型的网络时，在网络中第一台VM创建之前，该网络仅是数据库的一条记录。当第一个VM创建时，网络会指定一个VLAN ID并初始化。同样，当网络中最后一个VM销毁后，VLAN ID会被释放，这样该网络就不再可用。通过使用持久化网络，您就有能力在不部署VM的情况下在&PRODUCT;中创建一个网络用来部署物理设备。而且，您可以在该网络中部署物理设备。"
+
+# 6fcce92beeff40cb864882157e6e38eb
+#: ../../networking/persistent_networks.rst:33
+msgid ""
+"One of the advantages of having a persistent network is that you can create "
+"a VPC with a tier consisting of only physical devices. For example, you "
+"might create a VPC for a three-tier application, deploy VMs for Web and "
+"Application tier, and use physical machines for the Database tier. Another "
+"use case is that if you are providing services by using physical hardware, "
+"you can define the network as persistent and therefore even if all its VMs "
+"are destroyed the services will not be discontinued."
+msgstr "使用持久化网络的一个优点是您可以创建具有一个只包含物理设备的层的VPC。例如，您可以为一个三层应用创建一个VPC，在Web层和应用层部署VM，在数据库层使用物理机器。另一个使用场景为如果您使用物理硬件提供网络服务，您可以定义网络为持久化的。这样即便网络中所有VM都销毁了，服务还可以继续提供。"
+
+# 2967de4df3df472abd55988c65ca1c07
+#: ../../networking/persistent_networks.rst:44
+msgid "Persistent Network Considerations"
+msgstr "持久化网络的考虑事项"
+
+# 4091d1efe69a4148864ddea8b1361e5f
+#: ../../networking/persistent_networks.rst:46
+msgid "Persistent network is designed for isolated networks."
+msgstr "Persistent网络是为隔离网络而设计的。"
+
+# 153b60917c5c49d3982f1098e01b59b7
+#: ../../networking/persistent_networks.rst:48
+msgid "All default network offerings are non-persistent."
+msgstr "所有默认网络方案都不是持久化的。"
+
+# 77c3328fec084f13967871c9b7123076
+#: ../../networking/persistent_networks.rst:50
+msgid ""
+"A network offering cannot be editable because changing it affects the "
+"behavior of the existing networks that were created using this network "
+"offering."
+msgstr "网络方案的持久化选项不可编辑。因为修改该选项会影响使用该网络方案创建的已有网络的行为。"
+
+# 06bccf901e8a4ee8be58f15bfd579e68
+#: ../../networking/persistent_networks.rst:54
+msgid ""
+"When you create a guest network, the network offering that you select "
+"defines the network persistence. This in turn depends on whether persistent "
+"network is enabled in the selected network offering."
+msgstr "当您创建客户网络时，您选择的网络方案定义了该网络的持久化。反过来，这依赖于选择的网络方案是否启用持久化网络。"
+
+# d92b9c95102f488ba671717466ac055f
+#: ../../networking/persistent_networks.rst:58
+msgid ""
+"An existing network can be made persistent by changing its network offering "
+"to an offering that has the Persistent option enabled. While setting this "
+"property, even if the network has no running VMs, the network is "
+"provisioned."
+msgstr "通过修改使用的网络方案为启用持久化的方案，现有网络可以变为持久化。在设置该属性时，即便网络中没有运行的VM，该网络也会初始化。"
+
+# ef669f1e80be470eb1e8a8db355b2d4a
+#: ../../networking/persistent_networks.rst:63
+msgid ""
+"An existing network can be made non-persistent by changing its network "
+"offering to an offering that has the Persistent option disabled. If the "
+"network has no running VMs, during the next network garbage collection run "
+"the network is shut down."
+msgstr "通过修改使用的网络方案为禁用持久化的方案，现有网络可以变为非持久化。如果网络中没有运行的VM，在下次网络垃圾回收运行时，该网络会被关闭。"
+
+# 007f1cc1aa7c42f8a66e3fb305143475
+#: ../../networking/persistent_networks.rst:68
+msgid ""
+"When the last VM on a network is destroyed, the network garbage collector "
+"checks if the network offering associated with the network is persistent, "
+"and shuts down the network only if it is non-persistent."
+msgstr "当网络中最后一台VM销毁时，网络垃圾回收器会检查该网络的网络方案是否为持久化，若不是持久化，则会关闭网络。"
+
+# 4d27044c9aad4e059509066b13f9dc3a
+#: ../../networking/persistent_networks.rst:75
+msgid "Creating a Persistent Guest Network"
+msgstr "创建一个Persistent客户网络"
+
+# 30f307ec95db44a0b8c70317f2a9c100
+#: ../../networking/persistent_networks.rst:77
+msgid "To create a persistent network, perform the following:"
+msgstr "要创建一个Persistent网络，请按如下操作："
+
+# f479c47b1f454044bc8c2e67d6f14f0a
+#: ../../networking/persistent_networks.rst:79
+msgid "Create a network offering with the Persistent option enabled."
+msgstr "创建一个Persistent选项启用的网络方案。"
+
+# 08ed25ddd4a8403e98bddb19816af5cf
+#: ../../networking/persistent_networks.rst:81
+msgid ""
+"See `\"Creating a New Network Offering\" <networking.html#creating-a-new-"
+"network-offering>`_."
+msgstr "请参考`\"创建一个新的网络方案\" <networking.html#creating-a-new-network-offering>`_."
+
+# fd6c23139519494b901a461ef6fd445e
+#: ../../networking/persistent_networks.rst:84
+msgid "Select Network from the left navigation pane."
+msgstr "从左边的导航栏里选择网络。"
+
+# 92c525d55a6643c6a9f89f6b1ee2ff2e
+#: ../../networking/persistent_networks.rst:86
+msgid ""
+"Select the guest network that you want to offer this network service to."
+msgstr "选择你希望提供此网络方案服务的客户网络。"
+
+# 7c5a5842cf864317a92199d463521c9f
+#: ../../networking/persistent_networks.rst:89
+msgid "Click the Edit button."
+msgstr "点击编辑按钮。"
+
+# 552f67c193a3437586fc226221b340e3
+#: ../../networking/persistent_networks.rst:91
+msgid ""
+"From the Network Offering drop-down, select the persistent network offering "
+"you have just created."
+msgstr "在网络方案下拉列表里，选择你刚才创建的persistent网络方案。"
+
+# 4cd6d99517e445589fe0847cd2035e84
+#: ../../networking/palo_alto_config.rst:18
+msgid "Setup a Palo Alto Networks Firewall"
+msgstr ""
+
+# a25de960bb5944a9a2ffe54913707ab8
+#: ../../networking/palo_alto_config.rst:22
+msgid "Functionality Provided"
+msgstr ""
+
+# c9b058343ea14748825cfcc53a551dcf
+#: ../../networking/palo_alto_config.rst:24
+msgid ""
+"This implementation enables the orchestration of a Palo Alto Networks "
+"Firewall from within CloudStack UI and API."
+msgstr ""
+
+# 0f204dd9374d4ca281f9fa055813bcb0
+#: ../../networking/palo_alto_config.rst:27
+msgid "**The following features are supported**:"
+msgstr ""
+
+# 0a04c861f9c64663836468cf37783f6d
+#: ../../networking/palo_alto_config.rst:29
+msgid "List/Add/Delete Palo Alto Networks service provider"
+msgstr ""
+
+# f032d6431c414cb3bbb06b959df9a121
+#: ../../networking/palo_alto_config.rst:31
+msgid "List/Add/Delete Palo Alto Networks network service offering"
+msgstr ""
+
+# c1ad64a629ce42868368c8787dd4f3b8
+#: ../../networking/palo_alto_config.rst:33
+msgid ""
+"List/Add/Delete Palo Alto Networks network using the above service offering"
+msgstr ""
+
+# 983ec08ac8f442c580217a2a2fb8a596
+#: ../../networking/palo_alto_config.rst:35
+msgid "Add an instance to a Palo Alto Networks network"
+msgstr ""
+
+# 3ad3b15459c64a6eae255957c08316de
+#: ../../networking/palo_alto_config.rst:37
+msgid "Source NAT management on network create and delete"
+msgstr ""
+
+# 452d433b69644504b60597d2c0abd868
+#: ../../networking/palo_alto_config.rst:39
+msgid "List/Add/Delete Ingress Firewall rule"
+msgstr ""
+
+# 0a537c6e22f5405a970698d492049bda
+#: ../../networking/palo_alto_config.rst:41
+msgid ""
+"List/Add/Delete Egress Firewall rule (both 'Allow' and 'Deny' default rules "
+"supported)"
+msgstr ""
+
+# 6df7942d9fdd4433a02767a4b6bbd97a
+#: ../../networking/palo_alto_config.rst:44
+msgid "List/Add/Delete Port Forwarding rule"
+msgstr ""
+
+# 5adfa913867943e9a5334e717ba621b6
+#: ../../networking/palo_alto_config.rst:46
+msgid "List/Add/Delete Static NAT rule"
+msgstr ""
+
+# 9073fd9f1c574f99830d3323ff81b059
+#: ../../networking/palo_alto_config.rst:48
+msgid ""
+"Apply a Threat Profile to all firewall rules (more details in the Additional"
+" Features section)"
+msgstr ""
+
+# de1483044bfa4bb6a8d75e7825ab54af
+#: ../../networking/palo_alto_config.rst:51
+msgid ""
+"Apply a Log Forwarding profile to all firewall rules (more details in the "
+"Additional Features section)"
+msgstr ""
+
+# bb979ee8007748adb71a5a35c819303f
+#: ../../networking/palo_alto_config.rst:57
+msgid "Initial Palo Alto Networks Firewall Configuration"
+msgstr ""
+
+# 933f635eb00e45d291ea9b284dde50c8
+#: ../../networking/palo_alto_config.rst:60
+msgid "Anatomy of the Palo Alto Networks Firewall"
+msgstr ""
+
+# 6c130d9bd83d4265aa57e471d8849d87
+#: ../../networking/palo_alto_config.rst:62
+msgid ""
+"In **'Network > Interfaces'** there is a list of physical interfaces as well"
+" as aggregated physical interfaces which are used for managing traffic in "
+"and out of the Palo Alto Networks Firewall device."
+msgstr ""
+
+# f3ed9b3a42c94267a7aa3c8799d6f2d4
+#: ../../networking/palo_alto_config.rst:66
+msgid ""
+"In **'Network > Zones'** there is a list of the different configuration "
+"zones. This implementation will use two zones; a public (defaults to "
+"'untrust') and private (defaults to 'trust') zone."
+msgstr ""
+
+# 702c5d78734a4fb8ad9bdde0f6fe0fa8
+#: ../../networking/palo_alto_config.rst:70
+msgid ""
+"In **'Network > Virtual Routers'** there is a list of VRs which handle "
+"traffic routing for the Palo Alto Firewall. We only use a single Virtual "
+"Router on the firewall and it is used to handle all the routing to the next "
+"network hop."
+msgstr ""
+
+# fa5e01b476f8473cb2cd6dba3c93b26d
+#: ../../networking/palo_alto_config.rst:75
+msgid ""
+"In **'Objects > Security Profile Groups'** there is a list of profiles which"
+" can be applied to firewall rules. These profiles are used to better "
+"understand the types of traffic that is flowing through your network. "
+"Configured when you add the firewall provider to CloudStack."
+msgstr ""
+
+# 6ec861ebd15247b2a9d647243d07b9dc
+#: ../../networking/palo_alto_config.rst:80
+msgid ""
+"In **'Objects > Log Forwarding'** there is a list of profiles which can be "
+"applied to firewall rules. These profiles are used to better track the logs"
+" generated by the firewall. Configured when you add the firewall provider "
+"to CloudStack."
+msgstr ""
+
+# 10bd8a298e9b4499a4e2b8158b2781ec
+#: ../../networking/palo_alto_config.rst:85
+msgid ""
+"In **'Policies > Security'** there is a list of firewall rules that are "
+"currently configured. You will not need to modify this section because it "
+"will be completely automated by CloudStack, but you can review the firewall "
+"rules which have been created here."
+msgstr ""
+
+# 5deafeaa993b405cafa909f5c07398af
+#: ../../networking/palo_alto_config.rst:90
+msgid ""
+"In **'Policies > NAT'** there is a list of the different NAT rules. You "
+"will not need to modify this section because it will be completely automated"
+" by CloudStack, but you can review the different NAT rules that have been "
+"created here. Source NAT, Static NAT and Destination NAT (Port Forwarding) "
+"rules will show up in this list."
+msgstr ""
+
+# 97d928354c784496b323810668db7981
+#: ../../networking/palo_alto_config.rst:99
+msgid "Configure the Public / Private Zones on the firewall"
+msgstr ""
+
+# fc57f3d20fc6497093dfee06aed841b5
+#: ../../networking/palo_alto_config.rst:101
+msgid ""
+"No manual configuration is required to setup these zones because CloudStack "
+"will configure them automatically when you add the Palo Alto Networks "
+"firewall device to CloudStack as a service provider. This implementation "
+"depends on two zones, one for the public side and one for the private side "
+"of the firewall."
+msgstr ""
+
+# 5dc660fae9f340ae9d54c5ba27bccdc1
+#: ../../networking/palo_alto_config.rst:107
+msgid ""
+"The public zone (defaults to 'untrust') will contain all of the public "
+"interfaces and public IPs."
+msgstr ""
+
+# af5503e4adbb4dff94c7db0cbfeda2b0
+#: ../../networking/palo_alto_config.rst:110
+msgid ""
+"The private zone (defaults to 'trust') will contain all of the private "
+"interfaces and guest network gateways."
+msgstr ""
+
+# 0c1f328f71d949568997a16e0ee29ebb
+#: ../../networking/palo_alto_config.rst:113
+msgid "The NAT and firewall rules will be configured between these zones."
+msgstr ""
+
+# 4edccd68911e4eb8ad8d16aae69c40c7
+#: ../../networking/palo_alto_config.rst:118
+msgid "Configure the Public / Private Interfaces on the firewall"
+msgstr ""
+
+# 7b5d71324ae94b4eb1345496cb5fc980
+#: ../../networking/palo_alto_config.rst:120
+msgid ""
+"This implementation supports standard physical interfaces as well as grouped"
+" physical interfaces called aggregated interfaces. Both standard interfaces"
+" and aggregated interfaces are treated the same, so they can be used "
+"interchangeably. For this document, we will assume that we are using "
+"'ethernet1/1' as the public interface and 'ethernet1/2' as the private "
+"interface. If aggregated interfaces where used, you would use something "
+"like 'ae1' and 'ae2' as the interfaces."
+msgstr ""
+
+# ce56405d9b404dd8abcbd2b47dbd6002
+#: ../../networking/palo_alto_config.rst:128
+msgid ""
+"This implementation requires that the 'Interface Type' be set to 'Layer3' "
+"for both the public and private interfaces. If you want to be able to use "
+"the 'Untagged' VLAN tag for public traffic in CloudStack, you will need to "
+"enable support for it in the public 'ethernet1/1' interface (details below)."
+msgstr ""
+
+# e655877c1c3c4268b51d1f17b4d569e1
+#: ../../networking/palo_alto_config.rst:133
+msgid "**Steps to configure the Public Interface**:"
+msgstr ""
+
+# e8057bd4216c433a90d5747562875a83
+# e308adb3c6de47c3998377447d260f7e
+# 25d30e44808748d2bb2915a15019e45e
+#: ../../networking/palo_alto_config.rst:135
+#: ../../networking/palo_alto_config.rst:171
+#: ../../networking/palo_alto_config.rst:228
+msgid "Log into Palo Alto Networks Firewall"
+msgstr ""
+
+# 86c58907aa3c4905ac84366e69565cd9
+# 9e1f9a8ecebd488e8489f498bfc9409a
+#: ../../networking/palo_alto_config.rst:137
+#: ../../networking/palo_alto_config.rst:230
+msgid "Navigate to 'Network > Interfaces'"
+msgstr ""
+
+# d130fc55cd9d49c5a73893a0c995e367
+#: ../../networking/palo_alto_config.rst:139
+msgid ""
+"Click on 'ethernet1/1' (for aggregated ethernet, it will probably be called "
+"'ae1')"
+msgstr ""
+
+# 33208ee8235747389e981e3758d7dc4e
+# 39345e835bac41baa611bcf824968ff2
+#: ../../networking/palo_alto_config.rst:142
+#: ../../networking/palo_alto_config.rst:155
+msgid "Select 'Layer3' from the 'Interface Type' list"
+msgstr ""
+
+# b0867e0d6cb34b75b442b55cfa026322
+#: ../../networking/palo_alto_config.rst:144
+msgid "Click 'Advanced'"
+msgstr ""
+
+# 0c56d4c03cf243f6a1a87f9d8ca7e880
+#: ../../networking/palo_alto_config.rst:146
+msgid "Check the 'Untagged Subinterface' check-box"
+msgstr ""
+
+# 9166a2200b574af9b0ffe071ed3f4b87
+# 00c33fde208a445a9be7a319592575fc
+# 987a5a8988304ce2896e1879196846a5
+# 065cd5ad2daf471ea266f1b0d2fda873
+# c3f6ec8691624d8ab74249c07e266983
+# 91645da523df4c5ab7b8492737d911f5
+# 4240529e3bd14c3ca9c9d3376612f6f7
+# d3d09b3543e544f3bddba24c6963e421
+# 380b2d7379934a6da1b399eab4d37c07
+#: ../../networking/palo_alto_config.rst:148
+#: ../../networking/palo_alto_config.rst:157
+#: ../../networking/palo_alto_config.rst:193
+#: ../../networking/palo_alto_config.rst:195
+#: ../../networking/palo_alto_config.rst:265
+#: ../../networking/palo_alto_config.rst:339
+#: ../../networking/palo_alto_config.rst:388
+#: ../../networking/palo_alto_config.rst:426
+#: ../../networking/palo_alto_config.rst:455
+msgid "Click 'OK'"
+msgstr ""
+
+# a53d6716c3174e058cf5ad15298f16e9
+#: ../../networking/palo_alto_config.rst:150
+msgid "**Steps to configure the Private Interface**:"
+msgstr ""
+
+# 3aa72dc4f76541deb400a07b2b6b6787
+#: ../../networking/palo_alto_config.rst:152
+msgid ""
+"Click on 'ethernet1/2' (for aggregated ethernet, it will probably be called "
+"'ae2')"
+msgstr ""
+
+# 9be091f2707545c88df4139ff618a457
+#: ../../networking/palo_alto_config.rst:162
+msgid "Configure a Virtual Router on the firewall"
+msgstr ""
+
+# 84d511674355441bbe7dbe76d66c768f
+#: ../../networking/palo_alto_config.rst:164
+msgid ""
+"The Virtual Router on the Palo Alto Networks Firewall is not to be confused "
+"with the Virtual Routers that CloudStack provisions. For this "
+"implementation, the Virtual Router on the Palo Alto Networks Firewall will "
+"ONLY handle the upstream routing from the Firewall to the next hop."
+msgstr ""
+
+# e82ded6aea36475f968637969a284573
+#: ../../networking/palo_alto_config.rst:169
+msgid "**Steps to configure the Virtual Router**:"
+msgstr ""
+
+# 579fa3c360f448d08cbcf3ed1ac4c275
+#: ../../networking/palo_alto_config.rst:173
+msgid "Navigate to 'Network > Virtual Routers'"
+msgstr ""
+
+# c0ff1f9d1a7247718698f44028af33b5
+#: ../../networking/palo_alto_config.rst:175
+msgid ""
+"Select the 'default' Virtual Router or Add a new Virtual Router if there are"
+" none in the list"
+msgstr ""
+
+# 9d99adc7f2b74c30b6053032d36fabb3
+#: ../../networking/palo_alto_config.rst:178
+msgid "If you added a new Virtual Router, you will need to give it a 'Name'"
+msgstr ""
+
+# feab30a949cd4a22885bd65920931c99
+#: ../../networking/palo_alto_config.rst:180
+msgid "Navigate to 'Static Routes > IPv4'"
+msgstr ""
+
+# ac625a8780de43ed897656d4cfb74bcd
+#: ../../networking/palo_alto_config.rst:182
+msgid "'Add' a new static route"
+msgstr ""
+
+# 472da2053fed453e96fb4acb49fd7e62
+#: ../../networking/palo_alto_config.rst:184
+msgid "**Name**: next_hop (you can name it anything you want)"
+msgstr ""
+
+# cbfb1fb365b04c96b7df8ee388ae85d7
+#: ../../networking/palo_alto_config.rst:186
+msgid "**Destination**: 0.0.0.0/0 (send all traffic to this route)"
+msgstr ""
+
+# cda878dca5164d2f8e01aa0ff2848a96
+#: ../../networking/palo_alto_config.rst:188
+msgid ""
+"**Interface**: ethernet1/1 (or whatever you set your public interface as)"
+msgstr ""
+
+# a8dff252ac8841e1b30d1b61396e2f83
+#: ../../networking/palo_alto_config.rst:191
+msgid ""
+"**Next Hop**: (specify the gateway IP for the next hop in your network)"
+msgstr ""
+
+# 903e21b9a4a14125bacefde84d94aff4
+#: ../../networking/palo_alto_config.rst:200
+msgid "Configure the default Public Subinterface"
+msgstr ""
+
+# 2bd085187cbc476bbd72de056c01f9b1
+#: ../../networking/palo_alto_config.rst:202
+msgid ""
+"The current implementation of the Palo Alto Networks firewall integration "
+"uses CIDRs in the form of 'w.x.y.z/32' for the public IP addresses that "
+"CloudStack provisions. Because no broadcast or gateway IPs are in this "
+"single IP range, there is no way for the firewall to route the traffic for "
+"these IPs. To route the traffic for these IPs, we create a single "
+"subinterface on the public interface with an IP and a CIDR which "
+"encapsulates the CloudStack public IP range. This IP will need to be inside"
+" the subnet defined by the CloudStack public range netmask, but outside the "
+"CloudStack public IP range. The CIDR should reflect the same subnet defined"
+" by the CloudStack public range netmask. The name of the subinterface is "
+"determined by the VLAN configured for the public range in CloudStack."
+msgstr ""
+
+# 1027972bdb804444a04abfcb173c3213
+#: ../../networking/palo_alto_config.rst:214
+msgid "To clarify this concept, we will use the following example."
+msgstr ""
+
+# a217cfb35c1942b49aad39cf26323af1
+#: ../../networking/palo_alto_config.rst:216
+msgid "**Example CloudStack Public Range Configuration**:"
+msgstr ""
+
+# 0d8df54c42af461d957cae7fb26c8b0f
+#: ../../networking/palo_alto_config.rst:218
+msgid "**Gateway**: 172.30.0.1"
+msgstr ""
+
+# 203a1dcc624243cebe5260b914ca588d
+#: ../../networking/palo_alto_config.rst:220
+msgid "**Netmask**: 255.255.255.0"
+msgstr ""
+
+# fe0cf8e78a914ef6a9d994d84e33f273
+#: ../../networking/palo_alto_config.rst:222
+msgid "**IP Range**: 172.30.0.100 - 172.30.0.199"
+msgstr ""
+
+# 763cbf33799e4a66ba4ebba67deedea8
+#: ../../networking/palo_alto_config.rst:224
+msgid "**VLAN**: Untagged"
+msgstr ""
+
+# ef7b22d901134531a4ddc52d109f3884
+#: ../../networking/palo_alto_config.rst:226
+msgid "**Configure the Public Subinterface**:"
+msgstr ""
+
+# ce16b404e8fa422cb8d798d367d8ef89
+#: ../../networking/palo_alto_config.rst:232
+msgid "Select the 'ethernet1/1' line (not clicking on the name)"
+msgstr ""
+
+# 032bbee32d6343328a3ad9989c008a6d
+#: ../../networking/palo_alto_config.rst:234
+msgid "Click 'Add Subinterface' at the bottom of the window"
+msgstr ""
+
+# 6359f5f7ec124236b0f34c9d7e6c3635
+#: ../../networking/palo_alto_config.rst:236
+msgid "Enter 'Interface Name': 'ethernet1/1' . '9999'"
+msgstr ""
+
+# ed56cd87d56b41ed87efb9d1bf1c66f8
+#: ../../networking/palo_alto_config.rst:238
+msgid "9999 is used if the CloudStack public range VLAN is 'Untagged'"
+msgstr ""
+
+# 57a09d78c0084f9d839011aec1eed2eb
+#: ../../networking/palo_alto_config.rst:240
+msgid ""
+"If the CloudStack public range VLAN is tagged (eg: 333), then the name will "
+"reflect that tag"
+msgstr ""
+
+# bcde49681f784127a31d97e7b792eed0
+#: ../../networking/palo_alto_config.rst:243
+msgid ""
+"The 'Tag' is the VLAN tag that the traffic is sent to the next hop with, so "
+"set it accordingly. If you are passing 'Untagged' traffic from CloudStack "
+"to your next hop, leave it blank. If you want to pass tagged traffic from "
+"CloudStack, specify the tag."
+msgstr ""
+
+# 579804e4cdd9464eb30e3ff2621fb8a1
+#: ../../networking/palo_alto_config.rst:248
+msgid ""
+"Select 'default' from the 'Config > Virtual Router' drop-down (assuming that"
+" is what your virtual router is called)"
+msgstr ""
+
+# 3a5160b4f5c042c6b940642fa2b05b2c
+#: ../../networking/palo_alto_config.rst:251
+msgid "Click the 'IPv4' tab"
+msgstr ""
+
+# 84bf732b36934a829114ed49a2742f17
+#: ../../networking/palo_alto_config.rst:253
+msgid "Select 'Static' from the 'Type' radio options"
+msgstr ""
+
+# 5870dee962e9418d9d87eeacec3d35ad
+#: ../../networking/palo_alto_config.rst:255
+msgid "Click 'Add' in the 'IP' section"
+msgstr ""
+
+# 5b9f289d72b14be9b4cfa38ef1728f76
+#: ../../networking/palo_alto_config.rst:257
+msgid "Enter '172.30.0.254/24' in the new line"
+msgstr ""
+
+# a57d0d5ce83540e0a1b3d855b376e6b8
+#: ../../networking/palo_alto_config.rst:259
+msgid ""
+"The IP can be any IP outside the CloudStack public IP range, but inside the "
+"CloudStack public range netmask (it can NOT be the gateway IP)"
+msgstr ""
+
+# 359215f62863484ba745f8d2e03ce161
+#: ../../networking/palo_alto_config.rst:262
+msgid ""
+"The subnet defined by the CIDR should match the CloudStack public range "
+"netmask"
+msgstr ""
+
+# c46252e83d114010880044c824b7e57b
+#: ../../networking/palo_alto_config.rst:269
+msgid "Commit configuration on the Palo Alto Networks Firewall"
+msgstr ""
+
+# 365f937b3fec42aea6aea597efca79fd
+#: ../../networking/palo_alto_config.rst:271
+msgid ""
+"In order for all the changes we just made to take effect, we need to commit "
+"the changes."
+msgstr ""
+
+# e5f848bca30e4beba84d97eb6c369c28
+#: ../../networking/palo_alto_config.rst:274
+msgid "Click the 'Commit' link in the top right corner of the window"
+msgstr ""
+
+# 506c144a4d5e4583b1ac84b1eead3373
+#: ../../networking/palo_alto_config.rst:276
+msgid "Click 'OK' in the commit window overlay"
+msgstr ""
+
+# c6025e0b37e240a4bbb98c10672afae7
+#: ../../networking/palo_alto_config.rst:278
+msgid ""
+"Click 'Close' to the resulting commit status window after the commit "
+"finishes"
+msgstr ""
+
+# 37fa8b13701846cc9138c340b9c5c1c9
+#: ../../networking/palo_alto_config.rst:284
+msgid "Setup the Palo Alto Networks Firewall in CloudStack"
+msgstr ""
+
+# bf172f38242047e6a97f2181882e672f
+#: ../../networking/palo_alto_config.rst:287
+msgid "Add the Palo Alto Networks Firewall as a Service Provider"
+msgstr ""
+
+# 937455f6c6d4494680d9216fc506771b
+#: ../../networking/palo_alto_config.rst:289
+msgid ""
+"Navigate to 'Infrastructure > Zones > ZONE_NAME > Physical Network > "
+"NETWORK_NAME (guest) > Configure; Network Service Providers'"
+msgstr ""
+
+# cf68cff820a249ceb84fe458347aa12b
+#: ../../networking/palo_alto_config.rst:292
+msgid "Click on 'Palo Alto' in the list"
+msgstr ""
+
+# 46ab280934294383a25c46ec2f79b443
+#: ../../networking/palo_alto_config.rst:294
+msgid "Click 'View Devices'"
+msgstr ""
+
+# 7560d69ce9b843b6bf611c931c0675bb
+#: ../../networking/palo_alto_config.rst:296
+msgid "Click 'Add Palo Alto Device'"
+msgstr ""
+
+# 8956b2ff67f7426190554aae0701fcfa
+#: ../../networking/palo_alto_config.rst:298
+msgid ""
+"Enter your configuration in the overlay. This example will reflect the "
+"details previously used in this guide."
+msgstr ""
+
+# 30d5213a36ba4d038e33bd011c545565
+#: ../../networking/palo_alto_config.rst:301
+msgid "**IP Address**: (the IP of the Palo Alto Networks Firewall)"
+msgstr ""
+
+# 521f94e44aa74f7d80c7fa7e161c899e
+#: ../../networking/palo_alto_config.rst:303
+msgid "**Username**: (the admin username for the firewall)"
+msgstr ""
+
+# 8e9ee920bf3e4af9ac7f6b3577fa353d
+#: ../../networking/palo_alto_config.rst:305
+msgid "**Password**: (the admin password for the firewall)"
+msgstr ""
+
+# bb1105db236c4fe2a3565df1a58ce8f1
+#: ../../networking/palo_alto_config.rst:307
+msgid "**Type**: Palo Alto Firewall"
+msgstr ""
+
+# dc49c3aae7c3461cbd16d505f7fd294b
+#: ../../networking/palo_alto_config.rst:309
+msgid ""
+"**Public Interface**: ethernet1/1 (use what you setup earlier as the public "
+"interface if it is different from my examples)"
+msgstr ""
+
+# 752d21019c2944548bded6ff17d05189
+#: ../../networking/palo_alto_config.rst:312
+msgid ""
+"**Private Interface**: ethernet1/2 (use what you setup earlier as the "
+"private interface if it is different from my examples)"
+msgstr ""
+
+# d71bcfebd9824cd59280dfb23f87fc94
+#: ../../networking/palo_alto_config.rst:315
+msgid "**Number of Retries**: 2 (the default is fine)"
+msgstr ""
+
+# 8f1e92bb49df4bf69a4983820930b5b6
+#: ../../networking/palo_alto_config.rst:317
+msgid "**Timeout**: 300 (the default is fine)"
+msgstr ""
+
+# ac1090afc1b14b8a9dd41ebfe6fd059e
+#: ../../networking/palo_alto_config.rst:319
+msgid ""
+"**Public Network**: untrust (this is the public zone on the firewall and did"
+" not need to be configured)"
+msgstr ""
+
+# 81323dc3b1b5477a84f1f9a0aca02f1d
+#: ../../networking/palo_alto_config.rst:322
+msgid ""
+"**Private Network**: trust (this is the private zone on the firewall and did"
+" not need to be configured)"
+msgstr ""
+
+# 0587f506923242dba7d30acfa5f444bc
+#: ../../networking/palo_alto_config.rst:325
+msgid ""
+"**Virtual Router**: default (this is the name of the Virtual Router we setup"
+" on the firewall)"
+msgstr ""
+
+# 64503dfbfc6a4a52a027fb5580d77e45
+#: ../../networking/palo_alto_config.rst:328
+msgid ""
+"**Palo Alto Threat Profile**: (not required. name of the 'Security Profile "
+"Groups' to apply. more details in the 'Additional Features' section)"
+msgstr ""
+
+# 6a825e2b4acf42e89c8918ec303b4857
+#: ../../networking/palo_alto_config.rst:332
+msgid ""
+"**Palo Alto Log Profile**: (not required. name of the 'Log Forwarding' "
+"profile to apply. more details in the 'Additional Features' section)"
+msgstr ""
+
+# 096b8832d07e48e49b72747a73f81495
+#: ../../networking/palo_alto_config.rst:335
+msgid "**Capacity**: (not required)"
+msgstr ""
+
+# f58dd37d12ff463a8cf1cf7fd24c6249
+#: ../../networking/palo_alto_config.rst:337
+msgid "**Dedicated**: (not required)"
+msgstr ""
+
+# fffae74d8e664c85be11eaef42463e99
+#: ../../networking/palo_alto_config.rst:341
+msgid "Click on 'Palo Alto' in the breadcrumbs to go back one screen."
+msgstr ""
+
+# 3eb2449be08d4f88b8175a9fbd1e399a
+#: ../../networking/palo_alto_config.rst:343
+msgid "Click on 'Enable Provider' |EnableDisableFeature.png|"
+msgstr ""
+
+# f471b4d3e1334984931fdfba6c1e3630
+#: ../../networking/palo_alto_config.rst:347
+msgid "Add a Network Service Offering to use the new Provider"
+msgstr ""
+
+# 4e9125d7228d4e1d82ac0e317b41a5db
+#: ../../networking/palo_alto_config.rst:349
+msgid ""
+"There are 6 'Supported Services' that need to be configured in the network "
+"service offering for this functionality. They are DHCP, DNS, Firewall, "
+"Source NAT, Static NAT and Port Forwarding. For the other settings, there "
+"are probably additional configurations which will work, but I will just "
+"document a common case."
+msgstr ""
+
+# b591b1d771584a438ede97f7071cd655
+#: ../../networking/palo_alto_config.rst:355
+msgid "Navigate to 'Service Offerings'"
+msgstr ""
+
+# 14059062e0634e599485931cf2e0733b
+#: ../../networking/palo_alto_config.rst:357
+msgid "In the drop-down at the top, select 'Network Offerings'"
+msgstr ""
+
+# 2b3a92a7cce44d9792ac52aea4305a79
+#: ../../networking/palo_alto_config.rst:359
+msgid "Click 'Add Network Offering'"
+msgstr ""
+
+# 6b9a36687b1c429aa2bedbe8afb2a16c
+#: ../../networking/palo_alto_config.rst:361
+msgid "**Name**: (name it whatever you want)"
+msgstr ""
+
+# 3dd061afb48b49d5828e2ffafa973281
+#: ../../networking/palo_alto_config.rst:363
+msgid "**Description**: (again, can be whatever you want)"
+msgstr ""
+
+# 49f121a90bb6407484225354829e4f76
+#: ../../networking/palo_alto_config.rst:365
+msgid "**Guest Type**: Isolated"
+msgstr ""
+
+# 3ac932b614024736adfe4404b0994b15
+#: ../../networking/palo_alto_config.rst:367
+msgid "**Supported Services**:"
+msgstr ""
+
+# 5326f2fa7c3046859d71e526cbb378d3
+#: ../../networking/palo_alto_config.rst:369
+msgid "**DHCP**: Provided by 'VirtualRouter'"
+msgstr ""
+
+# 8380eb62feed49cf9defb0c46d0d965a
+#: ../../networking/palo_alto_config.rst:371
+msgid "**DNS**: Provided by 'VirtualRouter'"
+msgstr ""
+
+# c1a7cc369b54411b886e9cf936f96da2
+#: ../../networking/palo_alto_config.rst:373
+msgid "**Firewall**: Provided by 'PaloAlto'"
+msgstr ""
+
+# 2c93d4effcc3444b8ab2c3da1933602d
+#: ../../networking/palo_alto_config.rst:375
+msgid "**Source NAT**: Provided by 'PaloAlto'"
+msgstr ""
+
+# 4279d687aefd4657a9a25f5a81681496
+#: ../../networking/palo_alto_config.rst:377
+msgid "**Static NAT**: Provided by 'PaloAlto'"
+msgstr ""
+
+# 629dfab5c1dc40cc99930ae86c10df50
+#: ../../networking/palo_alto_config.rst:379
+msgid "**Port Forwarding**: Provided by 'PaloAlto'"
+msgstr ""
+
+# 7d48d89ad530444db29511d673a7df5e
+#: ../../networking/palo_alto_config.rst:381
+msgid "**System Offering for Router**: System Offering For Software Router"
+msgstr ""
+
+# 5ea8ba9b5eab4284ae26af32a837796e
+#: ../../networking/palo_alto_config.rst:383
+msgid ""
+"**Supported Source NAT Type**: Per account (this is the only supported "
+"option)"
+msgstr ""
+
+# c1ce203c827e446d855abb79dc033d31
+#: ../../networking/palo_alto_config.rst:386
+msgid "**Default egress policy**: (both 'Allow' and 'Deny' are supported)"
+msgstr ""
+
+# 1e2fa21b7c18491d943e71b38a893339
+#: ../../networking/palo_alto_config.rst:390
+msgid "Click on the newly created service offering"
+msgstr ""
+
+# ded26656c3714a89969c20ed0145aeca
+#: ../../networking/palo_alto_config.rst:392
+msgid "Click 'Enable network offering' |EnableDisableFeature.png|"
+msgstr ""
+
+# 961c14735e81493e85f84b384a2cf059
+#: ../../networking/palo_alto_config.rst:394
+msgid ""
+"When adding networks in CloudStack, select this network offering to use the "
+"Palo Alto Networks firewall."
+msgstr ""
+
+# 625a28d178864aeba73bb243f68af405
+#: ../../networking/palo_alto_config.rst:399
+msgid "Additional Features"
+msgstr ""
+
+# 966abd9906d540eeb3992080bfa4e79b
+#: ../../networking/palo_alto_config.rst:401
+msgid ""
+"In addition to the standard functionality exposed by CloudStack, we have "
+"added a couple additional features to this implementation. We did not add "
+"any new screens to CloudStack, but we have added a couple fields to the 'Add"
+" Palo Alto Service Provider' screen which will add functionality globally "
+"for the device."
+msgstr ""
+
+# a0955c0b218e4ead9953db5f3e933ebc
+#: ../../networking/palo_alto_config.rst:408
+msgid "Palo Alto Networks Threat Profile"
+msgstr ""
+
+# b56617dd1b7a49439204d45bd3ddc540
+#: ../../networking/palo_alto_config.rst:410
+msgid ""
+"This feature allows you to specify a 'Security Profile Group' to be applied "
+"to all of the firewall rules which are created on the Palo Alto Networks "
+"firewall device."
+msgstr ""
+
+# ddf43faad14a41deb2f807650433579e
+#: ../../networking/palo_alto_config.rst:414
+msgid ""
+"To create a 'Security Profile Group' on the Palo Alto Networks firewall, do "
+"the following:"
+msgstr ""
+
+# a77eb7c4a55b45db96ba922310c92a31
+# 401e0ddfb24441f3a01f0406fed5ea8c
+#: ../../networking/palo_alto_config.rst:417
+#: ../../networking/palo_alto_config.rst:446
+msgid "Log into the Palo Alto Networks firewall"
+msgstr ""
+
+# d1cffa0eb5b84c4fac78345a6a1eac14
+#: ../../networking/palo_alto_config.rst:419
+msgid "Navigate to 'Objects > Security Profile Groups'"
+msgstr ""
+
+# d8a2cff026f443e48ddc23e758c6b433
+#: ../../networking/palo_alto_config.rst:421
+msgid "Click 'Add' at the bottom of the page to add a new group"
+msgstr ""
+
+# 2260b8c3d00f4fb48409751005878ea3
+#: ../../networking/palo_alto_config.rst:423
+msgid ""
+"Give the group a Name and specify the profiles you would like to include in "
+"the group"
+msgstr ""
+
+# 71409d6bba4e4cefb293a3a2adb62a58
+# b0ff6a165cf648f59bb775cb80b7bae8
+#: ../../networking/palo_alto_config.rst:428
+#: ../../networking/palo_alto_config.rst:457
+msgid ""
+"Click the 'Commit' link in the top right of the screen and follow the on "
+"screen instructions"
+msgstr ""
+
+# 39f6f68e96514eb687aee18212a17720
+#: ../../networking/palo_alto_config.rst:431
+msgid ""
+"Once you have created a profile, you can reference it by Name in the 'Palo "
+"Alto Threat Profile' field in the 'Add the Palo Alto Networks Firewall as a "
+"Service Provider' step."
+msgstr ""
+
+# 19e3020b2cb741dcbeaf2757b1c46b0e
+#: ../../networking/palo_alto_config.rst:437
+msgid "Palo Alto Networks Log Forwarding Profile"
+msgstr ""
+
+# 8e702ba47eb14d06953df77990976d35
+#: ../../networking/palo_alto_config.rst:439
+msgid ""
+"This feature allows you to specify a 'Log Forwarding' profile to better "
+"manage where the firewall logs are sent to. This is helpful for keeping "
+"track of issues that can arise on the firewall."
+msgstr ""
+
+# a924dcc217f44a8d9ea1bf038038cc48
+#: ../../networking/palo_alto_config.rst:443
+msgid ""
+"To create a 'Log Forwarding' profile on the Palo Alto Networks Firewall, do "
+"the following:"
+msgstr ""
+
+# ae0e76d3eff94c3aae3e4b2c7d55b745
+#: ../../networking/palo_alto_config.rst:448
+msgid "Navigate to 'Objects > Log Forwarding'"
+msgstr ""
+
+# 2568e7109c7a4034872602eaf73fc171
+#: ../../networking/palo_alto_config.rst:450
+msgid "Click 'Add' at the bottom of the page to add a new profile"
+msgstr ""
+
+# b3e2a50453874aa591e0592eea54a974
+#: ../../networking/palo_alto_config.rst:452
+msgid ""
+"Give the profile a Name and specify the details you want for the traffic and"
+" threat settings"
+msgstr ""
+
+# 15fa6db47be1443fa69fb555db7583b7
+#: ../../networking/palo_alto_config.rst:460
+msgid ""
+"Once you have created a profile, you can reference it by Name in the 'Palo "
+"Alto Log Profile' field in the 'Add the Palo Alto Networks Firewall as a "
+"Service Provider' step."
+msgstr ""
+
+# 5d10eda1d77e4cdcaef70d1cded35c75
+#: ../../networking/palo_alto_config.rst:469
+msgid ""
+"The implementation currently only supports a single public IP range in "
+"CloudStack"
+msgstr ""
+
+# 01f1108e82134be5bf3daf49f3d331ea
+#: ../../networking/palo_alto_config.rst:472
+msgid "Usage tracking is not yet implemented"
+msgstr ""
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/projects.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/projects.mo
new file mode 100644
index 0000000..e1f84f3
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/projects.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/projects.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/projects.po
new file mode 100644
index 0000000..dd3a3ed
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/projects.po
@@ -0,0 +1,755 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:04+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 4b4ac9e9d63047e88707cfbcf936a425
+#: ../../projects.rst:18
+msgid "Using Projects to Organize Users and Resources"
+msgstr "使用项目来管理用户和资源。"
+
+# dd53e71c97984e29944fd5f92845fc70
+#: ../../projects.rst:21
+msgid "Overview of Projects"
+msgstr "项目概览"
+
+# 9ad708c803064abcbaa0ba5c9d5efe55
+#: ../../projects.rst:23
+msgid ""
+"Projects are used to organize people and resources. CloudStack users within "
+"a single domain can group themselves into project teams so they can "
+"collaborate and share virtual resources such as VMs, snapshots, templates, "
+"data disks, and IP addresses. CloudStack tracks resource usage per project "
+"as well as per user, so the usage can be billed to either a user account or "
+"a project. For example, a private cloud within a software company might have"
+" all members of the QA department assigned to one project, so the company "
+"can track the resources used in testing while the project members can more "
+"easily isolate their efforts from other users of the same cloud"
+msgstr "项目用来管理用户和资源。处于单独域中的CloudStack用户可以自组，他们可以集中并分享虚拟资源，如VM、快照、模板、磁盘、IP地址等。CloudStack可以像跟踪每个用户一样跟踪每个项目的资源，所以可以按照用户或者项目对资源使用收费。例如，一个软件公司的私有云可能将所有QA部门的员工分配到一个项目，当需要在测试中区分同一云中该项目组员工的贡献时，测试中的资源跟踪将变的容易。"
+
+# df157ec524304800a9ced5d428bd234c
+#: ../../projects.rst:34
+msgid ""
+"You can configure CloudStack to allow any user to create a new project, or "
+"you can restrict that ability to just CloudStack administrators. Once you "
+"have created a project, you become that project’s administrator, and you can"
+" add others within your domain to the project. CloudStack can be set up "
+"either so that you can add people directly to a project, or so that you have"
+" to send an invitation which the recipient must accept. Project members can "
+"view and manage all virtual resources created by anyone in the project (for "
+"example, share VMs). A user can be a member of any number of projects and "
+"can switch views in the CloudStack UI to show only project-related "
+"information, such as project VMs, fellow project members, project-related "
+"alerts, and so on."
+msgstr "你可以配置 CloudStack允许任何用户创建项目，或者你也可以只允许CloudStack管理员进行此项操作。一旦你创建了项目，你就成为项目管理员，你可以将域中的其他用户加入到项目。CloudStack可以设置成将用户直接加入项目或者向接受者发送邀请。项目组成员可以浏览和管理项目中的所有虚拟资源（例如，共享VM）。一个用户可以属于任何项目组，并可在CloudStack界面中切换只与项目相关的信息，如项目VM，项目成员，项目相关警告等。"
+
+# d29f7ae31802463281f05dac9610d8d2
+#: ../../projects.rst:46
+msgid ""
+"The project administrator can pass on the role to another project member. "
+"The project administrator can also add more members, remove members from the"
+" project, set new resource limits (as long as they are below the global "
+"defaults set by the CloudStack administrator), and delete the project. When "
+"the administrator removes a member from the project, resources created by "
+"that user, such as VM instances, remain with the project. This brings us to "
+"the subject of resource ownership and which resources can be used by a "
+"project."
+msgstr "项目管理员可以将角色传递给项目另外的成员。项目管理员也可以添加、删除项目成员，设置新的资源限制（只要在CloudStack管理员默认的全局设置范围之内），删除项目。当管理员将成员移出项目，那个成员所创建的资源，如VM实例，仍旧在项目中。这将我们带到了资源归属以及项目可用资源的课题下."
+
+# dde002b5830f493b94778605a4014583
+#: ../../projects.rst:55
+msgid ""
+"Resources created within a project are owned by the project, not by any "
+"particular CloudStack account, and they can be used only within the project."
+" A user who belongs to one or more projects can still create resources "
+"outside of those projects, and those resources belong to the user’s account;"
+" they will not be counted against the project’s usage or resource limits. "
+"You can create project-level networks to isolate traffic within the project "
+"and provide network services such as port forwarding, load balancing, VPN, "
+"and static NAT. A project can also make use of certain types of resources "
+"from outside the project, if those resources are shared. For example, a "
+"shared network or public template is available to any project in the domain."
+" A project can get access to a private template if the template’s owner will"
+" grant permission. A project can use any service offering or disk offering "
+"available in its domain; however, you can not create private service and "
+"disk offerings at the project level.."
+msgstr "项目内创建的资源为项目所有，不属于任何特殊的CloudStack帐户，仅能在项目内使用。属于一个或多个项目的用户扔可在这些项目之外创建资源，这些资源属于这个用户帐户；与项目使用和资源限制并不冲突。你可以在项目内创建项目级的网络来隔离流量，并提供网络服务，如端口转发，负载均衡，VPN，静态NAT。项目也可以在项目之外使用特定资源，只要这些资源是共享的。例如，域中的共享网络，公用模板对任何项目都是可用的。模板所有者如果赋予权限，项目也可以使用私有模板。项目可以使用域中设置的服务方案或磁盘方案；然后，你无法在项目层级创建私有服务和磁盘方案。"
+
+# 847217dcf84349fc9c5c719bfde3ec7f
+#: ../../projects.rst:73
+msgid "Configuring Projects"
+msgstr "配置项目"
+
+# 8a115b7683d3463087791eaed5a40d85
+#: ../../projects.rst:75
+msgid ""
+"Before CloudStack users start using projects, the CloudStack administrator "
+"must set up various systems to support them, including membership "
+"invitations, limits on project resources, and controls on who can create "
+"projects."
+msgstr "在CloudStack用户使用项目前，CloudStack管理员必须设置不同的系统以支持它们，包括成员身份邀请，项目资源的限制，以及对谁可以创建项目的控制。"
+
+# 327e0569d0c44de5b93b9f7e446920cc
+#: ../../projects.rst:82
+msgid "Setting Up Invitations"
+msgstr "设置邀请"
+
+# 3e242eb556ee478cb2f58ad9f6d5ce85
+#: ../../projects.rst:84
+msgid ""
+"CloudStack can be set up either so that project administrators can add "
+"people directly to a project, or so that it is necessary to send an "
+"invitation which the recipient must accept. The invitation can be sent by "
+"email or through the user’s CloudStack account. If you want administrators "
+"to use invitations to add members to projects, turn on and set up the "
+"invitations feature in CloudStack."
+msgstr "CloudStack可以设置成项目管理员直接添加用户或者向接受者发送邀请。邀请可以通过邮件或者用户的CloudStack帐户。如果你希望管理员使用邀请来添加项目成员，那么打开并设置CloudStack中的邀请属性。"
+
+# 8e48e6338f444e73898549bf0932c731
+# 2309d4b19c6d404181b591f4f6d205fc
+# 2e84d8cc479e4cf0af43cd20e4fa190b
+# ccfea269215f463d9fe35998c9494c53
+# 8c0130530bbe4c28b429436a6d8e61c9
+#: ../../projects.rst:91 ../../projects.rst:158 ../../projects.rst:177
+#: ../../projects.rst:214 ../../projects.rst:242
+msgid "Log in as administrator to the CloudStack UI."
+msgstr "使用管理员登录到CloudStack管理界面。"
+
+# e539c47bc6254e2c8a1382c03574a8c0
+# c7df097745ac41e1ab3b12f5ede84582
+# 989f33da3208451a8bcb145c25a7d1c9
+#: ../../projects.rst:93 ../../projects.rst:179 ../../projects.rst:216
+msgid "In the left navigation, click Global Settings."
+msgstr "在左侧导航栏，点击 全局设置"
+
+# 37e43d6f62be443998cb185f24333cdf
+#: ../../projects.rst:95
+msgid ""
+"In the search box, type project and click the search button. |Searches "
+"projects|"
+msgstr "在搜索栏中，输入项目，点击搜索按钮。 |搜索项目|"
+
+# e42abfd82e134939b6d5b7d2fed2f4cc
+#: ../../projects.rst:98
+msgid ""
+"In the search results, you can see a few other parameters you need to set to"
+" control how invitations behave. The table below shows global configuration "
+"parameters related to project invitations. Click the edit button to set each"
+" parameter."
+msgstr "在搜索结果中，你还需要设置一些其他的参数来控制邀请行为。下表所示的是全局配置参数中与项目邀请相关的部分，点击编辑按钮设置每个参数。"
+
+# 9a803ec0fbce49a1bfcbdcb1961d9fe9
+#: ../../projects.rst:104
+msgid "Configuration Parameters"
+msgstr "配置参数"
+
+# 2eb9f6fe8d7148b99a39f5ba5c0b8acf
+#: ../../projects.rst:104
+msgid "Description"
+msgstr "描述"
+
+# 8f015394c22643a89189371d0708f414
+#: ../../projects.rst:106
+msgid "project.invite.required"
+msgstr "project.invite.required"
+
+# 3f3e2860eff34ffaad4d84f57b53f46d
+#: ../../projects.rst:106
+msgid "Set to true to turn on the invitations feature."
+msgstr "将值设置为 true以打开邀请特性。"
+
+# c3dd124564eb4178a6f272ed89393757
+#: ../../projects.rst:108
+msgid "project.email.sender"
+msgstr "project.email.sender"
+
+# 1c83afe8caa5414181a01e7c8e31627f
+#: ../../projects.rst:108
+msgid "The email address to show in the From field of invitation emails."
+msgstr "邀请邮件中填入发送区域的邮件地址。"
+
+# 31cb407a37cc40c79b6cdb1c8171c153
+#: ../../projects.rst:110
+msgid "project.invite.timeout"
+msgstr "project.invite.timeout"
+
+# 1ff23ba5f3174049a1f067acd434fa47
+#: ../../projects.rst:110
+msgid "Amount of time to allow for a new member to respond to the invitation."
+msgstr "新成员对于邀请的允许响应时间。"
+
+# 9daf130db7394b60aae7266b51a04ff6
+#: ../../projects.rst:112
+msgid "project.smtp.host"
+msgstr "project.smtp.host"
+
+# dd464c374e9049c4995f6ea455014f6a
+#: ../../projects.rst:112
+msgid "Name of the host that acts as an email server to handle invitations."
+msgstr "作为处理邀请的邮件服务器的主机名。"
+
+# 89967c84b58c4a69af3b1718861da2b1
+#: ../../projects.rst:114
+msgid "project.smtp.password"
+msgstr "project.smtp.password"
+
+# 1815f51cddd147efb8c9cd0bf2fb66dd
+#: ../../projects.rst:114
+msgid ""
+"(Optional) Password required by the SMTP server. You must also set "
+"project.smtp.username and set project.smtp.useAuth to true."
+msgstr "(可选)SMTP服务器要求的密码。你必须将project.smtp.username和project.smtp.useAuth也设置为true。"
+
+# bb3f4cd97d8c4c5881aaded19029f405
+#: ../../projects.rst:116
+msgid "project.smtp.port"
+msgstr "project.smtp.port"
+
+# 30ad11730ae14fc5a8a26e34a244704d
+#: ../../projects.rst:116
+msgid "SMTP server’s listening port."
+msgstr "SMTP服务器的监听端口。"
+
+# 1e41abde08fb4385ad49ccdd91e5d856
+#: ../../projects.rst:118
+msgid "project.smtp.useAuth"
+msgstr "project.smtp.useAuth"
+
+# 41fc2bf9b98d4dd7af52e18e21334a4a
+#: ../../projects.rst:118
+msgid "Set to true if the SMTP server requires a username and password."
+msgstr "如果SMTP服务器需要用户名和密码，则设置为true"
+
+# d22498c945d14f65bd0892d1a3bbb4ab
+#: ../../projects.rst:120
+msgid "project.smtp.username"
+msgstr "project.smtp.username"
+
+# a025e0ccc7b641c8b1c1c18d0884a7e8
+#: ../../projects.rst:120
+msgid ""
+"(Optional) User name required by the SMTP server for authentication. You "
+"must also set project.smtp.password and set project.smtp.useAuth to true.."
+msgstr "(可选) 用于SMTPU认证的用户名。必须将project.smtp.password 和project.smtp.useAuth也设置为true。"
+
+# 5a399b5498814feb8d1d90ac249c0f06
+#: ../../projects.rst:123
+msgid "Restart the Management Server:"
+msgstr "重启管理服务器："
+
+# cc25b73903da4b3eb00ef5dca983a9b6
+#: ../../projects.rst:130
+msgid "Setting Resource Limits for Projects"
+msgstr "设置项目的资源限制"
+
+# 4554a70f1086483a8feea5f0c15eafd0
+#: ../../projects.rst:132
+msgid ""
+"The CloudStack administrator can set global default limits to control the "
+"amount of resources that can be owned by each project in the cloud. This "
+"serves to prevent uncontrolled usage of resources such as snapshots, IP "
+"addresses, and virtual machine instances. Domain administrators can override"
+" these resource limits for individual projects with their domains, as long "
+"as the new limits are below the global defaults set by the CloudStack root "
+"administrator. The root administrator can also set lower resource limits for"
+" any project in the cloud"
+msgstr "CloudStack管理员可以设置全局默认限制来控制云中每个项目可拥有的资源量。该服务用来限制不可控的资源使用，如快照，IP地址，虚拟机实例。域管理员在域中可以覆盖个人项目中的这些资源限制，只要这些限制在CloudStack根管理员的全局默认限制范围内。CloudStack根管理员可以为云中的任何项目设置更低的资源限制。"
+
+# 87c2e78e1e344c2fa0e550443ff641e3
+#: ../../projects.rst:143
+msgid "Setting Per-Project Resource Limits"
+msgstr "按项目设置资源限制"
+
+# 7e81041e8a9147bd84fde49f3f569465
+#: ../../projects.rst:145
+msgid ""
+"The CloudStack root administrator or the domain administrator of the domain "
+"where the project resides can set new resource limits for an individual "
+"project. The project owner can set resource limits only if the owner is also"
+" a domain or root administrator."
+msgstr " CloudStack系统管理员和项目所在域的域管理员可以设置单个项目的资源限制。项目所有者只有在其同时为域或系统管理员的情况下才能设置资源限制。"
+
+# 47029644eddd41d1b4647b5332d9c061
+#: ../../projects.rst:150
+msgid ""
+"The new limits must be below the global default limits set by the CloudStack"
+" administrator (as described in `“Setting Resource Limits for Projects” "
+"<#setting-resource-limits-for-projects>`_). If the project already owns more"
+" of a given type of resource than the new maximum, the resources are not "
+"affected; however, the project can not add any new resources of that type "
+"until the total drops below the new limit."
+msgstr "新限制值必须小于 CloudStack系统管理员设置的全局限制值（参见`“设置项目的资源限制” <#setting-resource-limits-for-projects>`_）。如果项目中的某种资源数量已经超过了新限制值，现有资源不受影响。然而，该项目将不能再添加该类型的新资源，直到资源数低于新限制值。"
+
+# f22a47ab0c5948e6b1e37d8a2ea696c9
+# e197ae8d631c487694852e4f6de2552f
+# befd6ea180404a3bb8cc85b535ec7a84
+# c2260b29d8b94395b2be966c4a99333d
+# 322b7293e93f44dcb5b9d2b201132963
+# 9f3d412110854b50a846dbdbcf15d67a
+#: ../../projects.rst:160 ../../projects.rst:244 ../../projects.rst:284
+#: ../../projects.rst:328 ../../projects.rst:350 ../../projects.rst:380
+msgid "In the left navigation, click Projects."
+msgstr "在左侧导航栏点击项目。"
+
+# 028c250e7e6144e2a78bcb28aeb20c20
+# 2eb7b64a81f44d6381ff74cb4876454f
+# ced1ffd77bfc4a769d87a1e02b4f605b
+# c52047f8f2064bb2a2e81d5aa52a4c86
+#: ../../projects.rst:162 ../../projects.rst:286 ../../projects.rst:330
+#: ../../projects.rst:382
+msgid "In Select View, choose Projects."
+msgstr "在选择视图选择项目。"
+
+# af4be7e8b89f4da08c1391967263e362
+# dc1fc36ced6d4c48984c0a599e2893ba
+# 79ab804df9234bd0af6b4f89d1b545b5
+#: ../../projects.rst:164 ../../projects.rst:288 ../../projects.rst:332
+msgid "Click the name of the project you want to work with."
+msgstr "点击您要操作的项目名称。"
+
+# 5e274b4f574149edaa1899709a04a1d3
+#: ../../projects.rst:166
+msgid ""
+"Click the Resources tab. This tab lists the current maximum amount that the "
+"project is allowed to own for each type of resource."
+msgstr "点击资源页。该页列出了项目当前可拥有的各类资源的最大数量。"
+
+# b0861fc478514256ad0ca41e6184ba3a
+#: ../../projects.rst:169
+msgid "Type new values for one or more resources."
+msgstr "为一种或几种资源输入新值。"
+
+# 363f4b7e52b04d4ba5bf081c3c51dc8a
+#: ../../projects.rst:171
+msgid "Click Apply."
+msgstr "点击应用"
+
+# 7263280c84454f05be8680c02efbd4c3
+#: ../../projects.rst:175
+msgid "Setting the Global Project Resource Limits"
+msgstr "设置全局项目资源限制"
+
+# 81a908897f4d4aacb979288d14e8f4ad
+#: ../../projects.rst:181
+msgid "In the search box, type max.projects and click the search button."
+msgstr "在搜索栏输入“max.projects”，点击搜索按钮。"
+
+# 7a132176784548a1bb80edb054b486b9
+#: ../../projects.rst:183
+msgid ""
+"In the search results, you will see the parameters you can use to set per-"
+"project maximum resource amounts that apply to all projects in the cloud. No"
+" project can have more resources, but an individual project can have lower "
+"limits. Click the edit button to set each parameter. |Edits parameters|"
+msgstr "在搜索结果中，你可以看到应用于云中所有项目的参数，你可以使用它们设置每个项目的最大资源量。没有项目能拥有更多资源，但个人项目能拥有更低的限制。点击编辑按钮设置每个参数。|编辑参数|"
+
+# 241b29e357a047dc890813c8021b8bfa
+#: ../../projects.rst:190
+msgid "max.project.public.ips"
+msgstr "max.project.public.ips"
+
+# ca118c2a5e6d41b0ae029c8780d99883
+#: ../../projects.rst:190
+msgid ""
+"Maximum number of public IP addresses that can be owned by any project in "
+"the cloud. See About Public IP Addresses."
+msgstr "项目拥有的公共IP最大值，参看公共IP地址。"
+
+# 2c1e0ade7edc46ff97ef948312221adb
+#: ../../projects.rst:192
+msgid "max.project.snapshots"
+msgstr "max.project.snapshots"
+
+# a809d74e8e264f2f8544e96dacf33d1a
+#: ../../projects.rst:192
+msgid ""
+"Maximum number of snapshots that can be owned by any project in the cloud. "
+"See Working with Snapshots."
+msgstr "项目可拥有的最大快照数。参看工作相关快照。"
+
+# 977134a911f844f98a39206991e01c12
+#: ../../projects.rst:194
+msgid "max.project.templates"
+msgstr "max.project.templates"
+
+# 44dcf66c930a42869b7601e0250466ac
+#: ../../projects.rst:194
+msgid ""
+"Maximum number of templates that can be owned by any project in the cloud. "
+"See Working with Templates."
+msgstr "项目可拥有的最大模板数。参看工作相关模板。"
+
+# 9007c476909543678660480c9c5cca8e
+#: ../../projects.rst:196
+msgid "max.project.uservms"
+msgstr "max.project.uservms"
+
+# fa7756a39a51499aa79542f6a9aebd0a
+#: ../../projects.rst:196
+msgid ""
+"Maximum number of guest virtual machines that can be owned by any project in"
+" the cloud. See Working With Virtual Machines."
+msgstr "项目中的虚拟客户机最大数目。参看工作相关虚拟机。"
+
+# 4bd44963b3c84bd09612d0c16cb2b21f
+#: ../../projects.rst:198
+msgid "max.project.volumes"
+msgstr "max.project.volumes"
+
+# b684120b36d54144b7d6bfd1b9cb26fd
+#: ../../projects.rst:198
+msgid ""
+"Maximum number of data volumes that can be owned by any project in the "
+"cloud. See Working with Volumes."
+msgstr "项目中所拥有的最大数据卷数，参看工作相关卷。"
+
+# 0a08e573ccff40ed964877c1e0a25422
+# 30bf816d7d164ebc9a3527bb06dcd0f5
+#: ../../projects.rst:202 ../../projects.rst:228
+msgid "Restart the Management Server."
+msgstr "重启管理服务器。"
+
+# 7a9e7b11d9204da7b5e4ae5b0cad6e15
+#: ../../projects.rst:209
+msgid "Setting Project Creator Permissions"
+msgstr "设置项目创建许可"
+
+# c9583a67341f459c94f3aa76485a5fd8
+#: ../../projects.rst:211
+msgid ""
+"You can configure CloudStack to allow any user to create a new project, or "
+"you can restrict that ability to just CloudStack administrators."
+msgstr "你可以配置 CloudStack允许所有用户创建新项目，或限制只有 CloudStack管理员具备此项能力。"
+
+# 0c5d1047bef445548c0c40109d391eca
+#: ../../projects.rst:218
+msgid "In the search box, type allow.user.create.projects."
+msgstr "在搜索框中，输入allow.user.create.projects。"
+
+# 44b11d9aac27438eb4bfa70d31759c86
+#: ../../projects.rst:220
+msgid "Click the edit button to set the parameter. |Edits parameters|"
+msgstr "点击编辑按钮设置参数。|编辑参数|"
+
+# fb277fa119e0496885f889a3ae48d1e7
+#: ../../projects.rst:222
+msgid "``allow.user.create.projects``"
+msgstr "``allow.user.create.projects``"
+
+# 9cdac884b4f1482599019f9178759604
+#: ../../projects.rst:224
+msgid ""
+"Set to true to allow end users to create projects. Set to false if you want "
+"only the CloudStack root administrator and domain administrators to create "
+"projects."
+msgstr "设置为true以允许端用户创建项目。设置为false如果你仅希望CloudStack根管理员和域管理员创建项目。"
+
+# c36ba31002c74ec98d2dcdec7bd9374e
+#: ../../projects.rst:236
+msgid "Creating a New Project"
+msgstr "创建新项目"
+
+# 6b62d8460a034f809371e1886bd34e80
+#: ../../projects.rst:238
+msgid ""
+"CloudStack administrators and domain administrators can create projects. If "
+"the global configuration parameter allow.user.create.projects is set to "
+"true, end users can also create projects."
+msgstr "CloudStack系统管理员和域管理员能创建项目。如果全局变量allow.user.create.projects设置为true，终端用户也能创建项目。"
+
+# 4a302cfc6cb34ba5baf6615abcae28ec
+#: ../../projects.rst:246
+msgid "In Select view, click Projects."
+msgstr "在选择视图点击项目。"
+
+# 520e75eebfb24c338a07edbd8119b8b8
+#: ../../projects.rst:248
+msgid "Click New Project."
+msgstr "点击新建项目。"
+
+# 42a42b0b1bb24125b530a8fb28a3b31a
+#: ../../projects.rst:250
+msgid ""
+"Give the project a name and description for display to users, then click "
+"Create Project."
+msgstr "为项目命名并添加描述，然后点击创建项目。"
+
+# 2c2486f0447d4f138b5e1c0e8ceace41
+#: ../../projects.rst:253
+msgid ""
+"A screen appears where you can immediately add more members to the project. "
+"This is optional. Click Next when you are ready to move on."
+msgstr "会出现一个界面，你可以很快的添加更多成员到项目中，此步可选。当你准备好继续，点击下一步。"
+
+# 2bc3c862668e44e78c5ec777dc974839
+#: ../../projects.rst:256
+msgid "Click Save."
+msgstr "点击保存。"
+
+# 986f0cb8853a42738eabaab830e43267
+#: ../../projects.rst:260
+msgid "Adding Members to a Project"
+msgstr "添加成员到一个项目"
+
+# 50647c0e69974fbba211aabef3bcda09
+#: ../../projects.rst:262
+msgid ""
+"New members can be added to a project by the project’s administrator, the "
+"domain administrator of the domain where the project resides or any parent "
+"domain, or the CloudStack root administrator. There are two ways to add "
+"members in CloudStack, but only one way is enabled at a time:"
+msgstr "项目管理员、项目所属域的域及其父域的管理员，CloudStack根管理员均可以添加新成员。CloudStack有两种方法可以添加成员，但每次只能使能一种："
+
+# ef81123f6c0e4fc3b1c2521f4324fc93
+#: ../../projects.rst:267
+msgid ""
+"If invitations have been enabled, you can send invitations to new members."
+msgstr "如果邀请已被使能，你可以向新成员发送邀请。"
+
+# f7125c407042411f8a4f35feff955784
+#: ../../projects.rst:270
+msgid ""
+"If invitations are not enabled, you can add members directly through the UI."
+msgstr "如果邀请未被使能，你可以直接通过界面添加成员。"
+
+# a4433f30587f4374807fa615b7d326cb
+#: ../../projects.rst:275
+msgid "Sending Project Membership Invitations"
+msgstr "发送项目成员关系邀请"
+
+# 4417ea897e4e418caf7f9050b019b36e
+#: ../../projects.rst:277
+msgid ""
+"Use these steps to add a new member to a project if the invitations feature "
+"is enabled in the cloud as described in `“Setting Up Invitations” <#setting-"
+"up-invitations>`_. If the invitations feature is not turned on, use the "
+"procedure in Adding Project Members From the UI."
+msgstr "如果邀请特性按照 `“设置邀请” <#设置邀请>`_中描述的方式被打开，使用这些步骤添加项目成员。如果邀请特性没有被打开，使用在界面中添加项目成员的步骤。"
+
+# b67c9d2fbb734979be7d9a0b06c83e07
+# 09c3e88bd9394c8ebecf83e40f6dfef9
+# 2b65ac18e6e14d988ed9d105965093b3
+# 0f9433a953604a24aaa3936b6304ff37
+# aaabf61386aa4e90a83121dd76c55ca6
+#: ../../projects.rst:282 ../../projects.rst:326 ../../projects.rst:348
+#: ../../projects.rst:378 ../../projects.rst:402
+msgid "Log in to the CloudStack UI."
+msgstr "登录到CloudStack的界面"
+
+# 6848798224324e658909d941615e3c71
+#: ../../projects.rst:290
+msgid "Click the Invitations tab."
+msgstr "点击邀请标签。"
+
+# 49786f4671bb4afbb13144fb5cdb22de
+#: ../../projects.rst:292
+msgid "In Add by, select one of the following:"
+msgstr "在添加中，选择以下其中一个："
+
+# 00420a7de6a943b5bea54e2930363c7b
+#: ../../projects.rst:294
+msgid ""
+"Account – The invitation will appear in the user’s Invitations tab in the "
+"Project View. See Using the Project View."
+msgstr "帐户 – 邀请将出现在用户项目概览的邀请标签中。参见使用项目概览。"
+
+# 23674aa094d8476181833f1077c82ce9
+#: ../../projects.rst:297
+msgid ""
+"Email – The invitation will be sent to the user’s email address. Each "
+"emailed invitation includes a unique code called a token which the recipient"
+" will provide back to CloudStack when accepting the invitation. Email "
+"invitations will work only if the global parameters related to the SMTP "
+"server have been set. See `“Setting Up Invitations” <#setting-up-"
+"invitations>`_."
+msgstr "邮件 – 邀请将发送到用户的邮箱地址。每个被发送的邀请中包含一个唯一的编码，称为令牌，当接收者接受邀请时需要向 CloudStack提供此令牌。只有当SMTP服务器相关的参数设置完毕后，邮件邀请才能工作。参见`“设置邀请” <#setting-up-invitations>`_。"
+
+# 98b4ad1148b94b9ba8e815a3ce4214a8
+#: ../../projects.rst:304
+msgid ""
+"Type the user name or email address of the new member you want to add, and "
+"click Invite. Type the CloudStack user name if you chose Account in the "
+"previous step. If you chose Email, type the email address. You can invite "
+"only people who have an account in this cloud within the same domain as the "
+"project. However, you can send the invitation to any email address."
+msgstr "输入想要添加的新用户的用户名称或邮件地址，点击邀请。如果你在前述步骤中选择了帐户那么输入CloudStack用户名。如果你选择了邮箱，那么输入邮箱地址，你只能邀请在云中拥有帐户并在与项目组同一域中的用户。然而，你可以向任何邮箱发送邀请。"
+
+# 9a6d6ea948754921bbc259b87b29ba60
+#: ../../projects.rst:311
+msgid ""
+"To view and manage the invitations you have sent, return to this tab. When "
+"an invitation is accepted, the new member will appear in the project’s "
+"Accounts tab."
+msgstr "为了浏览和管理你所发送的邀请，返回到这个标签。当邀请被接受，新成员将显示在项目帐户标签中。"
+
+# 2cf29d018a2c48a79262e2f02cd30162
+#: ../../projects.rst:317
+msgid "Adding Project Members From the UI"
+msgstr "在界面中添加项目成员"
+
+# fdbf78a90732473689bcedc64864415d
+#: ../../projects.rst:319
+msgid ""
+"The steps below tell how to add a new member to a project if the invitations"
+" feature is not enabled in the cloud. If the invitations feature is enabled "
+"cloud,as described in `“Setting Up Invitations” <#setting-up-invitations>`_,"
+" use the procedure in `“Sending Project Membership Invitations” <#sending-"
+"project-membership-invitations>`_."
+msgstr "下面的步骤介绍在邀请特性未使能的情况下如何添加项目新成员。如果邀请特性已按照 `“设置邀请” <#设置邀请>`_在云中被使能，那么使用 `“发送项目成员关系邀请” <#发送项目成员关系邀请>`_中的步骤。"
+
+# 069a956c95384174a82d2d0302f3dfd7
+#: ../../projects.rst:334
+msgid "Click the Accounts tab. The current members of the project are listed."
+msgstr "点击项目按钮，项目目前的成员将被列表显示。"
+
+# 7654413243e545579270bc7c8b813727
+#: ../../projects.rst:337
+msgid ""
+"Type the account name of the new member you want to add, and click Add "
+"Account. You can add only people who have an account in this cloud and "
+"within the same domain as the project."
+msgstr "输入你想添加的新成员帐户名称，点击添加帐户。你只能添加云中已有并与项目存在于相同域中的帐户。"
+
+# 774bd03942ea4a3ab9023bb4f72b627b
+#: ../../projects.rst:343
+msgid "Accepting a Membership Invitation"
+msgstr "接受成员关系邀请"
+
+# 462eace7144340bc8bc65c06d8056b5d
+#: ../../projects.rst:345
+msgid ""
+"If you have received an invitation to join a CloudStack project, and you "
+"want to accept the invitation, follow these steps:"
+msgstr "如果你收到了一个加入CloudStack项目的邀请，并希望接受邀请，请按照以下步骤："
+
+# 0196721635cc470094d28372774afeac
+#: ../../projects.rst:352
+msgid "In Select View, choose Invitations."
+msgstr "在选择概览，选择邀请。"
+
+# f5c8ed37ac54486f8d3f20f9129936a9
+#: ../../projects.rst:354
+msgid "If you see the invitation listed onscreen, click the Accept button."
+msgstr "如果你看到有邀请列表显示，点击接受按钮。"
+
+# f33506966c894c8eb0f91c35c2d506ee
+#: ../../projects.rst:356
+msgid ""
+"Invitations listed on screen were sent to you using your CloudStack account "
+"name."
+msgstr "屏幕上所显示的邀请是通过你的CloudStack帐户发送的。"
+
+# 67733042a89a4b969d73efc5f2fa6e94
+#: ../../projects.rst:359
+msgid ""
+"If you received an email invitation, click the Enter Token button, and "
+"provide the project ID and unique ID code (token) from the email."
+msgstr "如果你收到的是邮件邀请，点击输入令牌按钮，提供邮件中的项目ID和唯一的ID编码（令牌）。"
+
+# c33bd4e1071f4d9dab4b1d9a3be3f052
+#: ../../projects.rst:364
+msgid "Suspending or Deleting a Project"
+msgstr "挂起或删除项目"
+
+# b401169d94da465097ecd686cf60ced2
+#: ../../projects.rst:366
+msgid ""
+"When a project is suspended, it retains the resources it owns, but they can "
+"no longer be used. No new resources or members can be added to a suspended "
+"project."
+msgstr "当项目被挂起，它仍保有资源，但这些资源不能被使用。新资源及用户不能被加入到挂起的项目。"
+
+# d08b758fd1754360a7334fa51c6067cf
+#: ../../projects.rst:370
+msgid ""
+"When a project is deleted, its resources are destroyed, and member accounts "
+"are removed from the project. The project’s status is shown as Disabled "
+"pending final deletion."
+msgstr "当项目被删除，资源将被销毁，成员帐户也从项目中移除。项目状态被显示为禁止有待最后删除。"
+
+# 400db324f49c472881028c92fb1082c8
+#: ../../projects.rst:374
+msgid ""
+"A project can be suspended or deleted by the project administrator, the "
+"domain administrator of the domain the project belongs to or of its parent "
+"domain, or the CloudStack root administrator."
+msgstr "项目可以被管理员，项目所属的域及其父域管理员， CloudStack根管理员挂起或删除，"
+
+# d8a96b11443d49109477879ebdf4e6c1
+#: ../../projects.rst:384
+msgid "Click the name of the project."
+msgstr "点击项目名称。"
+
+# 6c5f88a0ad7443cdb4f778b9d3d8da58
+#: ../../projects.rst:386
+msgid "Click one of the buttons:"
+msgstr "点击以下按钮："
+
+# 29804834398d400d9518f86f6aadc9ca
+#: ../../projects.rst:388
+msgid "To delete, use |Removes a project|"
+msgstr "使用 |移除项目|进行删除"
+
+# 41920e56886b48dbb25f86128a21a0c2
+#: ../../projects.rst:390
+msgid "To suspend, use |Suspends a project|"
+msgstr "使用 |挂起项目|进行挂起"
+
+# fe947634ec70449bb7e58adb8700e805
+#: ../../projects.rst:394
+msgid "Using the Project View"
+msgstr "使用项目概览"
+
+# b2b759558262491e98fb0636eae9bd35
+#: ../../projects.rst:396
+msgid ""
+"If you are a member of a project, you can use CloudStack’s project view to "
+"see project members, resources consumed, and more. The project view shows "
+"only information related to one project. It is a useful way to filter out "
+"other information so you can concentrate on a project status and resources."
+msgstr "如果你是项目成员，你可以通过CloudStack项目概览查看项目成员，资源消耗等。项目概览仅显示与一个项目相关的信息，从众多信息中筛选出项目状态及资源，这是种有效的方法。"
+
+# b2d475dcc43b441da5592c11733cec95
+#: ../../projects.rst:404
+msgid "Click Project View."
+msgstr "点击项目概览。"
+
+# 697e02ba1d754fab8d93b30aa2692085
+#: ../../projects.rst:406
+msgid ""
+"The project dashboard appears, showing the project’s VMs, volumes, users, "
+"events, network settings, and more. From the dashboard, you can:"
+msgstr "出现项目控制板，显示项目VM，卷，用户，事件，网络设置等，在控制板中，你可以："
+
+# 0439e9369d664d92be0b7b1fdb1ca88f
+#: ../../projects.rst:410
+msgid ""
+"Click the Accounts tab to view and manage project members. If you are the "
+"project administrator, you can add new members, remove members, or change "
+"the role of a member from user to admin. Only one member at a time can have "
+"the admin role, so if you set another user’s role to admin, your role will "
+"change to regular user."
+msgstr "点击帐户按钮浏览和管理项目成员。如果你是项目管理员，你可以添加新成员，或者将成员从用户改为管理员。每次只有一名成员能成为管理员，如果你将另外的用户设置为管理员，你将成为普通用户。"
+
+# cfe2dfd46e014224a3ec791add73746c
+#: ../../projects.rst:417
+msgid ""
+"(If invitations are enabled) Click the Invitations tab to view and manage "
+"invitations that have been sent to new project members but not yet accepted."
+" Pending invitations will remain in this list until the new member accepts, "
+"the invitation timeout is reached, or you cancel the invitation."
+msgstr "(如果邀请已被使能)点击邀请按钮来浏览或管理已经想新项目成员发出未被接受的邀请。有待确认的邀请将一直在列表中知道被新成员接受，或邀请时间超时，或你取消了邀请。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/reliability.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/reliability.mo
new file mode 100644
index 0000000..eb0f294
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/reliability.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/reliability.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/reliability.po
new file mode 100644
index 0000000..141543d
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/reliability.po
@@ -0,0 +1,485 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:04+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 87e0763c1e254b4d865a6575d53cd476
+#: ../../reliability.rst:18
+msgid "System Reliability and High Availability"
+msgstr "系统可靠性与高可用性"
+
+# c2cb2128aadc481d823ace426cd60607
+#: ../../reliability.rst:21
+msgid "HA for Management Server"
+msgstr "管理服务器的HA"
+
+# 2cf0c6cbde074e988216174d32a34366
+#: ../../reliability.rst:23
+msgid ""
+"The CloudStack Management Server should be deployed in a multi-node "
+"configuration such that it is not susceptible to individual server failures."
+" The Management Server itself (as distinct from the MySQL database) is "
+"stateless and may be placed behind a load balancer."
+msgstr "CloudStack管理服务器可以部署为多节点的配置，使得它不容易受到单个服务器故障影响。管理服务器(不同于MySQL数据库)本身是无状态的，可以被部署在负载均衡设备后面。"
+
+# 0fa3d9ec6d144621b71b2a0077137930
+#: ../../reliability.rst:28
+msgid ""
+"Normal operation of Hosts is not impacted by an outage of all Management "
+"Serves. All guest VMs will continue to work."
+msgstr "停止的所有管理服务不会影响主机的正常操作。所有来宾VM将继续工作。"
+
+# 161abac9b6d7470bbf7a984e225c9a6d
+#: ../../reliability.rst:31
+msgid ""
+"When the Management Server is down, no new VMs can be created, and the end "
+"user and admin UI, API, dynamic load distribution, and HA will cease to "
+"work."
+msgstr "当管理主机下线后，不能创建新的VMs、最终用户，管理UI、API、动态负载以及HA都将停止工作。"
+
+# c2abacc0b20149d5b7a4683aedfe4f32
+#: ../../reliability.rst:37
+msgid "Management Server Load Balancing"
+msgstr "管理服务器负载均衡"
+
+# 0dc6eb435a354cf3b4279772461cbf7f
+#: ../../reliability.rst:39
+msgid ""
+"CloudStack can use a load balancer to provide a virtual IP for multiple "
+"Management Servers. The administrator is responsible for creating the load "
+"balancer rules for the Management Servers. The application requires "
+"persistence or stickiness across multiple sessions. The following chart "
+"lists the ports that should be load balanced and whether or not persistence "
+"is required."
+msgstr "CloudStack可以使用负载均衡器为多管理服务器提供一个虚拟IP。管理员负责创建管理服务器的负载均衡规则。应用程序需要跨多个持久性或stickiness的会话。下表列出了需要进行负载平衡的端口和是否有持久性要求。"
+
+# c998c6decbb94666aa6b7c6191a0f4ce
+#: ../../reliability.rst:46
+msgid "Even if persistence is not required, enabling it is permitted."
+msgstr "即使不需要持久性，也使它是允许的。"
+
+# fa7858c33d194002ade885780b974057
+#: ../../reliability.rst:49
+msgid "Source Port"
+msgstr "源端口"
+
+# 8e4749c413de4b28a281ada8d2d64112
+#: ../../reliability.rst:49
+msgid "Destination Port"
+msgstr "目标端口"
+
+# 044f0a55ef9143028e6a1442c2d75ee4
+#: ../../reliability.rst:49
+msgid "Protocol"
+msgstr "协议"
+
+# 50fdab6c4d254b51be652286846ebac8
+#: ../../reliability.rst:49
+msgid "Persistence Required?"
+msgstr "持续请求"
+
+# f5fcf842916f48bba5a1ef7630fe9998
+#: ../../reliability.rst:51
+msgid "80 or 443"
+msgstr "80或者443"
+
+# 3a276b78a619418392895c04f2b8e5f0
+#: ../../reliability.rst:51
+msgid "8080 (or 20400 with AJP)"
+msgstr "8080 (或者 20400 with AJP)"
+
+# d09ff40864724d449227f282f2c255b4
+#: ../../reliability.rst:51
+msgid "HTTP (or AJP)"
+msgstr "HTTP (或者AJP)"
+
+# 10b0e96112a54a5b92b53ee2ad9bf186
+# fb100cffa01e43e2b2b5880237a41528
+#: ../../reliability.rst:51 ../../reliability.rst:52
+msgid "Yes"
+msgstr "是"
+
+# f3007601ae444c0796d25c5e58d09d7a
+# 1393fb040df84ca781d1000f40e4794a
+#: ../../reliability.rst:52 ../../reliability.rst:52
+msgid "8250"
+msgstr "8250"
+
+# 6443f2a5e1d840699fd47b726ff379f9
+#: ../../reliability.rst:52
+msgid "TCP"
+msgstr "TCP"
+
+# 1e51ee3a6cd14a0a954cce617a60c19d
+# a50ea41d89cf476eadb2a4ad960c9c6a
+#: ../../reliability.rst:53 ../../reliability.rst:53
+msgid "8096"
+msgstr "8096"
+
+# c2b280074d6f40d685182ce0770b0146
+#: ../../reliability.rst:53
+msgid "HTTP"
+msgstr "HTTP"
+
+# 759f4cdc678a4b149c52cf0e39205f9c
+#: ../../reliability.rst:53
+msgid "No"
+msgstr "否"
+
+# a6f72463a9f44a83992ea95a6ca2d121
+#: ../../reliability.rst:56
+msgid ""
+"In addition to above settings, the administrator is responsible for setting "
+"the 'host' global config value from the management server IP to load "
+"balancer virtual IP address. If the 'host' value is not set to the VIP for "
+"Port 8250 and one of your management servers crashes, the UI is still "
+"available but the system VMs will not be able to contact the management "
+"server."
+msgstr "除了上面的设置，管理员还负责设置‘host’全局配置值，由管理服务器IP地址更改为负载均衡虚拟IP地址。如果‘host’值未设置为VIP的8250端口并且一台管理服务器崩溃时，用户界面依旧可用，但系统虚拟机将无法与管理服务器联系。"
+
+# 4ea4aac15f0649b9a4ec0335de47dde1
+#: ../../reliability.rst:65
+msgid "HA-Enabled Virtual Machines"
+msgstr "启用了HA的虚拟机"
+
+# c3b807bd9019482093758c219005a8af
+# 15a6c6ff487d4b4ab6f7088de5c25301
+#: ../../reliability.rst:67 ../../reliability.rst:84
+msgid ""
+"The user can specify a virtual machine as HA-enabled. By default, all "
+"virtual router VMs and Elastic Load Balancing VMs are automatically "
+"configured as HA-enabled. When an HA-enabled VM crashes, CloudStack detects "
+"the crash and restarts the VM automatically within the same Availability "
+"Zone. HA is never performed across different Availability Zones. CloudStack "
+"has a conservative policy towards restarting VMs and ensures that there will"
+" never be two instances of the same VM running at the same time. The "
+"Management Server attempts to start the VM on another Host in the same "
+"cluster."
+msgstr "用户可以给指定的虚拟机开启高可用特性。默认情况下所有的虚拟路由虚拟机和弹性负载均衡虚拟机自动开启了高可用特性。当CloudStack检测到开启了高可用特性的虚拟机崩溃时将会在相同的可用资源与中自动重新启动该虚拟机。高可用特性不会跨资源域执行。CloudStack采用比较保守的方式重启虚拟机，以确使不会同时运行两个相同的实例。管理服务器会尝试在本集群的另一台主机上开启该虚拟机。"
+
+# 07861c848b9c4db19a1648e1e80cfabd
+# 69462f0a341c4b64a73b9f2e6a9dbb2d
+#: ../../reliability.rst:77 ../../reliability.rst:94
+msgid ""
+"HA features work with iSCSI or NFS primary storage. HA with local storage is"
+" not supported."
+msgstr "高可用特性只在使用iSCSI和NFS做主存储的时候才可以使用。不支持使用本地存储作为主存储的高可用。"
+
+# d6b616e863194085b6c28e537822b4b0
+#: ../../reliability.rst:82
+msgid "HA for Hosts"
+msgstr "主机的HA"
+
+# 00c672182ced409dbf9628273c7e72cc
+#: ../../reliability.rst:99
+msgid "Dedicated HA Hosts"
+msgstr "专用的HA主机"
+
+# d615a157c03a46f8a4185819e7d53f6a
+#: ../../reliability.rst:101
+msgid ""
+"One or more hosts can be designated for use only by HA-enabled VMs that are "
+"restarting due to a host failure. Setting up a pool of such dedicated HA "
+"hosts as the recovery destination for all HA-enabled VMs is useful to:"
+msgstr "一台或更多台主机可以被设计为只有启用HA的VMs才能使用，这些VMs在主机出现问题的时候会重启。出于灾难恢复目的为所有启用了HA的VMs设置一个像专用HA主机这样的池是有用的："
+
+# 3b2ac4cb2fd24384adc49f8f6de78d12
+#: ../../reliability.rst:106
+msgid ""
+"Make it easier to determine which VMs have been restarted as part of the "
+"CloudStack high-availability function. If a VM is running on a dedicated HA "
+"host, then it must be an HA-enabled VM whose original host failed. (With one"
+" exception: It is possible for an administrator to manually migrate any VM "
+"to a dedicated HA host.)."
+msgstr "确定哪些VMs作为CloudStack高可用功能的一部分而重启是比较容易的。如果一个VM正运行在专用的HA主机上，那么它必须是一个启用了HA的，从失败的主机上迁移过来的VM。(有一个例外：它可能是管理员手工迁移过来的任何VM。)。"
+
+# 2814f71a4772417494be794e95ed6189
+#: ../../reliability.rst:112
+msgid ""
+"Keep HA-enabled VMs from restarting on hosts which may be reserved for other"
+" purposes."
+msgstr "出于其他目的，可能保留一些启用了HA的VMs在主机上不要重启。"
+
+# f29ad59410ba484d81a40d3ab33cfb75
+#: ../../reliability.rst:115
+msgid ""
+"The dedicated HA option is set through a special host tag when the host is "
+"created. To allow the administrator to dedicate hosts to only HA-enabled "
+"VMs, set the global configuration variable ha.tag to the desired tag (for "
+"example, \"ha\\_host\"), and restart the Management Server. Enter the value "
+"in the Host Tags field when adding the host(s) that you want to dedicate to "
+"HA-enabled VMs."
+msgstr "当创建了主机之后，通过指定一个主机标签来设置专用HA选项。要允许管理员只给启用了HA的VMs制定专用主机，请设置全局配置变量ha.tag为想要的tag(比如， \"ha\\_host\")，并且重启管理服务器。当添加你想给启用HA的VMs配置专用主机(s\n)时，在主机标签区域中输入值。"
+
+# d5444df1dd2240bea9615234f1703727
+#: ../../reliability.rst:123
+msgid ""
+"If you set ha.tag, be sure to actually use that tag on at least one host in "
+"your cloud. If the tag specified in ha.tag is not set for any host in the "
+"cloud, the HA-enabled VMs will fail to restart after a crash."
+msgstr "如果你设置ha.tag，请确认在你的云中至少有一台主机真的在使用该标签。如果在ha.tag中没有为云中的任何主机设置指定的标签，那么启用了HA的VMs在崩溃之后不会重启。"
+
+# 41dd6b225a02456f873c956ecc4e6018
+#: ../../reliability.rst:130
+msgid "Primary Storage Outage and Data Loss"
+msgstr "主存储故障和数据丢失"
+
+# 982e58c7dfd644a9a8e0eaf38fbf516a
+#: ../../reliability.rst:132
+msgid ""
+"When a primary storage outage occurs the hypervisor immediately stops all "
+"VMs stored on that storage device. Guests that are marked for HA will be "
+"restarted as soon as practical when the primary storage comes back on line. "
+"With NFS, the hypervisor may allow the virtual machines to continue running "
+"depending on the nature of the issue. For example, an NFS hang will cause "
+"the guest VMs to be suspended until storage connectivity is restored.Primary"
+" storage is not designed to be backed up. Individual volumes in primary "
+"storage can be backed up using snapshots."
+msgstr "当主存储发生故障，hypervisor 立即停止该存储设备上存储的所有虚拟机。客户机被标记为当主存储重新上线时，HA根据实际情况尽快将重新启动。使用NFS时，hypervisor 可以允许虚拟机继续运行，这取决于问题的性质。例如，NFS挂起将导致客户虚拟机暂停，直至恢复存储连接。主存储没有被设计进行备份。在主存储中的单个卷，可以使用快照备份。"
+
+# 2d193df58d2c4fcb867416d740fd9657
+#: ../../reliability.rst:144
+msgid "Secondary Storage Outage and Data Loss"
+msgstr "二级存储的故障和数据丢失"
+
+# 2d7b3415392e4e8ba762191a40dafa04
+#: ../../reliability.rst:146
+msgid ""
+"For a Zone that has only one secondary storage server, a secondary storage "
+"outage will have feature level impact to the system but will not impact "
+"running guest VMs. It may become impossible to create a VM with the selected"
+" template for a user. A user may also not be able to save snapshots or "
+"examine/restore saved snapshots. These features will automatically be "
+"available when the secondary storage comes back online."
+msgstr "由于一个资源域只有一个二级存储服务器，二级存储的中断将会对系统的一些功能产生影响，但不影响正在运行的客户虚拟机。可能会让用户无法选择模版来创建虚拟机。用户也可能无法保存快照，检查或恢复已保存的快照。当二级存储恢复连接后，这些功能也就可以自动恢复。"
+
+# 8cda194548a545c0864b2334b52ac6c1
+#: ../../reliability.rst:153
+msgid ""
+"Secondary storage data loss will impact recently added user data including "
+"templates, snapshots, and ISO images. Secondary storage should be backed up "
+"periodically. Multiple secondary storage servers can be provisioned within "
+"each zone to increase the scalability of the system."
+msgstr "二级存储的数据丢失将会影响最近添加的用户数据，包括模版、快照、和ISO镜像。二级存储应该进行定期备份。为每个资源域提供多个二级存储服务器能够增强系统的可扩展性。"
+
+# 5d6dd861732344e1a4563e92beaf4b89
+#: ../../reliability.rst:160
+msgid "Database High Availability"
+msgstr "数据库的高可用"
+
+# 2ab1e8b94c5447719fe99d7a1f876d22
+#: ../../reliability.rst:162
+msgid ""
+"To help ensure high availability of the databases that store the internal "
+"data for CloudStack, you can set up database replication. This covers both "
+"the main CloudStack database and the Usage database. Replication is achieved"
+" using the MySQL connector parameters and two-way replication. Tested with "
+"MySQL 5.1 and 5.5."
+msgstr "为了确保存储CloudStack内部数据的数据库的高可用性，你可以设置数据库复制。这涉及到所有CloudStack主数据库和用量数据库。复制是指完全使用MySQL连接参数和双向复制。MySQL 5.1和5.5已测试通过。"
+
+# 2f86c6796ebc476ba0a054b55ec4199d
+#: ../../reliability.rst:170
+msgid "How to Set Up Database Replication"
+msgstr "如何设置数据库复制"
+
+# 9c0172a3e34d439ca93117a4c922b4cf
+#: ../../reliability.rst:172
+msgid ""
+"Database replication in CloudStack is provided using the MySQL replication "
+"capabilities. The steps to set up replication can be found in the MySQL "
+"documentation (links are provided below). It is suggested that you set up "
+"two-way replication, which involves two database nodes. In this case, for "
+"example, you might have node1 and node2."
+msgstr "CloudStack中的数据库复制是由MySQL复制功能提供的。设置复制的步骤可在MySQL的文档中找到(链接在下面提供)。它建议你设置双向复制，涉及两个数据库节点。在这个情形下，比如，你可能有node1和node2。"
+
+# c0c448bf2d294f1f99d5a0715263bf84
+#: ../../reliability.rst:178
+msgid ""
+"You can also set up chain replication, which involves more than two nodes. "
+"In this case, you would first set up two-way replication with node1 and "
+"node2. Next, set up one-way replication from node2 to node3. Then set up "
+"one-way replication from node3 to node4, and so on for all the additional "
+"nodes."
+msgstr "你同样可以设置链式复制，这涉及到多于两个节点。在这个情况下，你可以先设置node1和node2的双向复制。然后，设置node2和node3的单向复制。在设置node3和node4的单向复制，其他所有的节点依次类推。"
+
+# 946a91ee699241e981ff92c48293ebe9
+#: ../../reliability.rst:184
+msgid "References:"
+msgstr "参考文献："
+
+# 0e89f25f5f474fa8a51de012dc293160
+#: ../../reliability.rst:186
+msgid ""
+"`http://dev.mysql.com/doc/refman/5.0/en/replication-howto.html "
+"<http://dev.mysql.com/doc/refman/5.0/en/replication-howto.html>`_"
+msgstr "`http://dev.mysql.com/doc/refman/5.0/en/replication-howto.html <http://dev.mysql.com/doc/refman/5.0/en/replication-howto.html>`_"
+
+# 4b174fc7f8484911b245607384172cae
+#: ../../reliability.rst:188
+msgid ""
+"`https://wikis.oracle.com/display/CommSuite/MySQL+High+Availability+and+Replication+Information+For+Calendar+Server"
+" "
+"<https://wikis.oracle.com/display/CommSuite/MySQL+High+Availability+and+Replication+Information+For+Calendar+Server>`_"
+msgstr "`https://wikis.oracle.com/display/CommSuite/MySQL+High+Availability+and+Replication+Information+For+Calendar+Server <https://wikis.oracle.com/display/CommSuite/MySQL+High+Availability+and+Replication+Information+For+Calendar+Server>`_"
+
+# 4fe437de91df4ffa8fe0925f0acdbfc5
+#: ../../reliability.rst:192
+msgid "Configuring Database High Availability"
+msgstr "配置数据库高可用"
+
+# f284eab37564471292cd2af70ef18ae5
+#: ../../reliability.rst:194
+msgid ""
+"To control the database high availability behavior, use the following "
+"configuration settings in the file /etc/cloudstack/management/db.properties."
+msgstr "要控制数据库高可用特性，在/etc/cloudstack/management/db.properties文件中使用以下配置设置。"
+
+# f79c8f4273854ceb83977ca0474e9594
+#: ../../reliability.rst:198
+msgid "**Required Settings**"
+msgstr "**需求设置**"
+
+# 239ea1c4ea2a4c428cbfdd0ae1d3c2a3
+#: ../../reliability.rst:200
+msgid "Be sure you have set the following in db.properties:"
+msgstr "确定你在 db.properties中使用了以下设置："
+
+# e03d864abdca47daa90be6c6c5eccecc
+#: ../../reliability.rst:202
+msgid ""
+"``db.ha.enabled``: set to true if you want to use the replication feature."
+msgstr "``db.ha.enabled``：如果你想使用复制功能，请设置为true。"
+
+# affe10ff738642c4b25a6cbfc26c498e
+#: ../../reliability.rst:205
+msgid "Example: ``db.ha.enabled=true``"
+msgstr "例如：``db.ha.enabled=true``"
+
+# 147ac9efb2314312b6e97323a267fd7c
+#: ../../reliability.rst:207
+msgid ""
+"``db.cloud.slaves``: set to a comma-delimited set of slave hosts for the "
+"cloud database. This is the list of nodes set up with replication. The "
+"master node is not in the list, since it is already mentioned elsewhere in "
+"the properties file."
+msgstr "``db.cloud.slaves``：为云数据库设置多台slave主机，用逗号隔开。这是用于复制的节点清单。主节点不在列表中，因为在属性文件中的别处已经使用了它。"
+
+# aa38f185ca8b4c1b86e19da970eb3901
+#: ../../reliability.rst:212
+msgid "Example: ``db.cloud.slaves=node2,node3,node4``"
+msgstr "例如：``db.cloud.slaves=node2,node3,node4``"
+
+# 1783ef0808884e28ab22f6b3172dba41
+#: ../../reliability.rst:214
+msgid ""
+"``db.usage.slaves``: set to a comma-delimited set of slave hosts for the "
+"usage database. This is the list of nodes set up with replication. The "
+"master node is not in the list, since it is already mentioned elsewhere in "
+"the properties file."
+msgstr "``db.usage.slaves``：为用量数据库设置多台slave主机，用逗号隔开。这是用于复制的节点清单。主节点不在列表中，因为在属性文件中的别处已经使用了它。"
+
+# 573fb04445dd4b0ba4f5b9a5f8517c75
+#: ../../reliability.rst:219
+msgid "Example: ``db.usage.slaves=node2,node3,node4``"
+msgstr "例如：``db.usage.slaves=node2,node3,node4``"
+
+# 739f9df2617d4e24aaa9adb209c65969
+#: ../../reliability.rst:221
+msgid "**Optional Settings**"
+msgstr "**可选的设置**"
+
+# 21e38ceba8e84d3f8b520026cae7d1b7
+#: ../../reliability.rst:223
+msgid ""
+"The following settings must be present in db.properties, but you are not "
+"required to change the default values unless you wish to do so for tuning "
+"purposes:"
+msgstr "必须在db.properties中提供以下设置，但是你不用改变默认值除非你希望做一些优化："
+
+# bcfa8dcb331c4185bab0cbdfbb3624ca
+#: ../../reliability.rst:227
+msgid ""
+"``db.cloud.secondsBeforeRetryMaster``: The number of seconds the MySQL "
+"connector should wait before trying again to connect to the master after the"
+" master went down. Default is 1 hour. The retry might happen sooner if "
+"db.cloud.queriesBeforeRetryMaster is reached first."
+msgstr "``db.cloud.secondsBeforeRetryMaster``：在master宕机之后，MySQL连接器重试连接到master之前所等待的秒数。默认是1小时。如果首先达到了db.cloud.queriesBeforeRetryMaster 的限制，重试可能更早发生。"
+
+# 55d7217f8ea6408e8389bd39dbbfc3fc
+#: ../../reliability.rst:232
+msgid "Example: ``db.cloud.secondsBeforeRetryMaster=3600``"
+msgstr "例如：``db.cloud.secondsBeforeRetryMaster=3600``"
+
+# d8cfb3b10706434d8ad7c63b231e7ee9
+#: ../../reliability.rst:234
+msgid ""
+"``db.cloud.queriesBeforeRetryMaster``: The minimum number of queries to be "
+"sent to the database before trying again to connect to the master after the "
+"master went down. Default is 5000. The retry might happen sooner if "
+"db.cloud.secondsBeforeRetryMaster is reached first."
+msgstr "``db.cloud.queriesBeforeRetryMaster``：在master宕机之后，重新尝试连接到master之前向数据库查询的最小次数。默认值是5000。如果首先达到了db.cloud.secondsBeforeRetryMaster的限制，重试可能更早发生。"
+
+# f7b672a867c64854accef70177a0dd73
+#: ../../reliability.rst:239
+msgid "Example: ``db.cloud.queriesBeforeRetryMaster=5000``"
+msgstr "例如：``db.cloud.queriesBeforeRetryMaster=5000``"
+
+# 2283aca3081443c585804a3c9d63a45d
+#: ../../reliability.rst:241
+msgid ""
+"``db.cloud.initialTimeout``: Initial time the MySQL connector should wait "
+"before trying again to connect to the master. Default is 3600."
+msgstr "``db.cloud.initialTimeout``：在重新尝试连接至master之前，MySQL连接器等待的初始时间。默认是3600。"
+
+# bae95908743e448b967b6992b4e88816
+#: ../../reliability.rst:244
+msgid "Example: ``db.cloud.initialTimeout=3600``"
+msgstr "例如：``db.cloud.initialTimeout=3600``"
+
+# 6b17824c97504228abd0de9726eb598e
+#: ../../reliability.rst:248
+msgid "Limitations on Database High Availability"
+msgstr "数据库高可用性的限制"
+
+# 5df2f93aff944e03bd3c9f9e21c95cb6
+#: ../../reliability.rst:250
+msgid ""
+"The following limitations exist in the current implementation of this "
+"feature."
+msgstr "目前此功能的实现还存在下列限制。"
+
+# 7c4a38ab45c943a489f2e7ae8f3ab0e2
+#: ../../reliability.rst:253
+msgid ""
+"Slave hosts can not be monitored through CloudStack. You will need to have a"
+" separate means of monitoring."
+msgstr "Slave主机不能被CloudStack监控。你必须有单独的监控手段。"
+
+# 5270e63b8008415bbe847a54002660bc
+#: ../../reliability.rst:256
+msgid ""
+"Events from the database side are not integrated with the CloudStack "
+"Management Server events system."
+msgstr "数据库端的事件没有集成到CloudStack管理服务器事件系统。"
+
+# 1bef8f38060a49e7ba30b234ad377f32
+#: ../../reliability.rst:259
+msgid ""
+"You must periodically perform manual clean-up of bin log files generated by "
+"replication on database nodes. If you do not clean up the log files, the "
+"disk can become full."
+msgstr "你必须定期的执行手动清除由数据库节点复制产生的二进制log文件。如果你不清理log文件，磁盘就会被占满。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/service_offerings.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/service_offerings.mo
new file mode 100644
index 0000000..d3f7a2a
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/service_offerings.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/service_offerings.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/service_offerings.po
new file mode 100644
index 0000000..b4f4688
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/service_offerings.po
@@ -0,0 +1,1079 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:04+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 003ddcd4027d44e1bae1560113612be3
+#: ../../service_offerings.rst:18
+msgid "Service Offerings"
+msgstr "服务方案"
+
+# db77c1944ac947e79b5c76bac2c1cc4d
+#: ../../service_offerings.rst:20
+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 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."
+msgstr "除了云中的物理和逻辑基础设施以及 CloudStack 软件和服务器，你还需要一个用户服务层以便让人们能够真正利用云。这不仅仅意味这一个用户界面，而是一组用户可选择的选项和资源，如通过模版创建虚拟机，磁盘存储等等。如果您正在运行一个商业服务，您将可以跟踪服务和用户资源的使用以及使用计费情况。即使你不对使用云的人收费，-比如说，用户是你的内部组织，或只是你的朋友共享你的云 - 你仍然可以跟踪他们所使用的服务以及有多少人。"
+
+# eac4f2f6a6f346d991640acd102c8d0f
+#: ../../service_offerings.rst:34
+msgid "Service Offerings, Disk Offerings, Network Offerings, and Templates"
+msgstr "服务方案，磁盘方案，网络方案和模版"
+
+# f620092a7ebb41d79ed21c4a5c81d56c
+#: ../../service_offerings.rst:36
+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 "用户可以根据不同的功能和特性来创建新的实例，CloudStack提供了几种方法供用户选择以便创建一个新的实例:"
+
+# ab361873de2144c095169458d8a25cb1
+#: ../../service_offerings.rst:40
+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 "服务方案，由CloudStack管理员定义，提供了CPU速率，CPU核数，内存大小，根磁盘标签等多种选项供选择。可参阅创建新的计算方案。"
+
+# 1044e18059f346f9ac414afad0f176ff
+#: ../../service_offerings.rst:44
+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 "磁盘方案，由CloudStack管理员定义，针对主数据存储提供磁盘大小和IOPS(QOS)等选项供选择。可参阅创建新的磁盘方案。"
+
+# 8fa5935f6811416784633a016e64dff9
+#: ../../service_offerings.rst:48
+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 "网络方案，由 CloudStack 管理员定义，约定来宾网络中虚拟路由器或外部网络设备提供给终端用户可用的功能描述集。"
+
+# 0e8bd7f2f14a4d698ef10eb8f7bd3059
+#: ../../service_offerings.rst:53
+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 "模版，由CloudStack管理员或其他CloudStack用户定义，用户创建新的实例时可选择的基本操作系统镜像。例如，CloudStack中包含的CentOS模版。可参阅使用模版。"
+
+# 52afe58166814f258c3426dd55249f7d
+#: ../../service_offerings.rst:58
+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 "除了给用户提供了这些选择，还有另一种类型的服务方案只提供给CloudStack管理员，用于配置虚拟基础设施资源。欲了解更多信息，请参阅使用系统服务方案升级虚拟路由器。"
+
+# b05b989a07394a3eafabebb48aeaa29b
+#: ../../service_offerings.rst:66
+msgid "Compute and Disk Service Offerings"
+msgstr "计算和磁盘服务方案"
+
+# 494d86b3d06340ab855b7df7a298410a
+#: ../../service_offerings.rst:68
+msgid ""
+"A service offering is a set of virtual hardware features such as CPU core "
+"count and speed, memory, and disk size. The CloudStack administrator can set"
+" up various offerings, and then end users choose from the available "
+"offerings when they create a new VM. Based on the user’s selected offering, "
+"CloudStack emits usage records that can be integrated with billing systems."
+msgstr "一个服务方案是一个虚拟硬件特征集合，比如 CPU 核心数量和速度，内存，已经磁盘大小。 CloudStack 管理员可以建立各种方案，接着终端用户在建立一个新虚拟机时就可以选择可用方案。基于用户的选择方案， CloudStack 可以发送整合在计费系统中的使用记录。"
+
+# d5a6cbcc11594496b3347a195f561c03
+#: ../../service_offerings.rst:75
+msgid ""
+"Some characteristics of service offerings must be defined by the CloudStack "
+"administrator, and others can be left undefined so that the end-user can "
+"enter their own desired values. This is useful to reduce the number of "
+"offerings the CloudStack administrator has to define. Instead of defining a "
+"compute offering for every imaginable combination of values that a user "
+"might want, the administrator can define offerings that provide some "
+"flexibility to the users and can serve as the basis for several different VM"
+" configurations."
+msgstr "CloudStack 管理员必须定义一些服务方案的特征，同时留下一些未定义的，让终端用户输入自己需要的值。这个对于降低 CloudStack 管理员定义的方案的数量很有用处。代替为每个用户定义一个他们想要可能组合值的计算方案，管理员可以为用户定义灵活的计算方案，并作为基本的若干不同虚拟机配置。"
+
+# 57a11b0d87cd4cb6bd64aa2c1b61db19
+#: ../../service_offerings.rst:84
+msgid "A service offering includes the following elements:"
+msgstr "一个服务方案包含以下元素："
+
+# 314c7c80394a45fe9bd7869f420d84b0
+#: ../../service_offerings.rst:86
+msgid "CPU, memory, and network resource guarantees"
+msgstr "必备的CPU,内存和网络资源"
+
+# b88f65b187394191a414ccf797fb3c8a
+#: ../../service_offerings.rst:88
+msgid "How resources are metered"
+msgstr "如何计算资源"
+
+# 0f00c0ffe83246cdbebaae3ad3295fb6
+#: ../../service_offerings.rst:90
+msgid "How the resource usage is charged"
+msgstr "使用资源如何收费"
+
+# 168105b5e4554db0b0cb46f61c6763c3
+#: ../../service_offerings.rst:92
+msgid "How often the charges are generated"
+msgstr "产生了多少费用"
+
+# 4ed86a2b44c647c4991679260cf019f9
+#: ../../service_offerings.rst:94
+msgid ""
+"For example, one service offering might allow users to create a virtual "
+"machine instance that is equivalent to a 1 GHz Intel® Core™ 2 CPU, with 1 GB"
+" memory at $0.20/hour, with network traffic metered at $0.10/GB."
+msgstr "比如，一个服务方案允许用户创建一个虚拟机实例，这个实例等于： 1 GHz Intel® Core™ 2 CPU, $0.20/hour 的 1G 内存, $0.10/GB. 的网络流量。"
+
+# c41f30feb0b442d4b39c95168d4ea2cc
+#: ../../service_offerings.rst:98
+msgid ""
+"CloudStack separates service offerings into compute offerings and disk "
+"offerings. The compute service offering specifies:"
+msgstr "CloudStack 把服务方案分割为计算方案和磁盘放哪。计算方案指定："
+
+# 03b79e1695f6418596fbf3dfdae6fdf5
+#: ../../service_offerings.rst:101
+msgid ""
+"Guest CPU (optional). If not defined by the CloudStack administrator, users "
+"can pick the CPU attributes."
+msgstr "来宾 CPU（可选）。如果 CloudStack 管理员未定义，用户可选择 CPU 特性。"
+
+# a9484632eacc49aaaa151b0462236017
+#: ../../service_offerings.rst:104
+msgid ""
+"Guest RAM (optional). If not defined by the CloudStack administrator, users "
+"can pick the RAM."
+msgstr "来宾 RAM ( 可选)。如果 CloudStack 管理员未定义，用户可选择 RAM。"
+
+# 8566fe8312914c68bedcb2c81b3c0c7b
+#: ../../service_offerings.rst:107
+msgid "Guest Networking type (virtual or direct)"
+msgstr "来宾网络类型（虚拟或者直连）"
+
+# 083cf96ec0c24344baef88ec1b1b562b
+#: ../../service_offerings.rst:109
+msgid "Tags on the root disk"
+msgstr "根磁盘标签"
+
+# 49478998f1fc4c37a9278a56f4e95eac
+#: ../../service_offerings.rst:111
+msgid "The disk offering specifies:"
+msgstr "磁盘方案特指："
+
+# e819601d04c3430f97d349bc00ef953b
+#: ../../service_offerings.rst:113
+msgid ""
+"Disk size (optional). If not defined by the CloudStack administrator, users "
+"can pick the disk size."
+msgstr "磁盘大小 （可选）。如果 CloudStack 管理员未定义，用户可选择磁盘大小。"
+
+# a4d4936154c4482d889d800ccf8426ef
+#: ../../service_offerings.rst:116
+msgid "Tags on the data disk"
+msgstr "数据磁盘标签"
+
+# a561332470b74e3e90cdf9bcabe2317e
+#: ../../service_offerings.rst:120
+msgid "Custom Compute Offering"
+msgstr "自定义计算方案"
+
+# 55f34a846c444887ad4349ad37fe65f8
+#: ../../service_offerings.rst:122
+msgid ""
+"CloudStack provides you the flexibility to specify the desired values for "
+"the number of CPU, CPU speed, and memory while deploying a VM. As an admin, "
+"you create a Compute Offering by marking it as custom, and the users will be"
+" able to customize this dynamic Compute Offering by specifying the memory, "
+"and CPU at the time of VM creation or upgrade. Custom Compute Offering is "
+"same as the normal Compute Offering except that the values of the dynamic "
+"parameters will be set to zeros in the given set of templates. Use this "
+"offering to deploy VM by specifying custom values for the dynamic "
+"parameters. Memory, CPU and number of CPUs are considered as dynamic "
+"parameters."
+msgstr " 部署虚拟机时，CloudStack 为你灵活地提供指定的 CPU 数量，CPU 速度和内存需要的值。作为管理员，你通过标记为自定义创建一个新的计算方案，并且用户将能够在虚拟机创建和更新时动态的定制计算方案的内存和 CPU 。自定义计算方案和普通的计算方案一样，除了在模板中配置为0的动态参数。使用该方案通过为动态参数指定自定义值来部署虚拟机。内存，CPU 和 CPU 数量被认为是动态参数。"
+
+# 50cd9056418842c08eb28fdce54e3deb
+#: ../../service_offerings.rst:133
+msgid ""
+"Dynamic Compute Offerings can be used in following cases: deploying a VM, "
+"changing the compute offering of a stopped VM and running VMs, which is "
+"nothing but scaling up. To support this feature a new field, Custom, has "
+"been added to the Create Compute Offering page. If the Custom field is "
+"checked, the user will be able to create a custom Compute Offering by "
+"filling in the desired values for number of CPU, CPU speed, and memory. See "
+"? for more information on this."
+msgstr "动态计算方案可以在下列情况下使用：部署虚拟机，改变停止状态虚拟机和运行中的虚拟机的计算方案，单独扩容。为了支持此功能的新字段，自定义，已经被添加到创建计算方案页面。如果自定义字段被选中，用户将可以通过填写所需 CPU ，CPU 速度和内存数量的值来创建自定义计方案。看到了吗？有关它的更多信息。"
+
+# efbe01f182224e6a96c59f3165e87c47
+#: ../../service_offerings.rst:141
+msgid "*Recording Usage Events for Dynamically Assigned Resources*."
+msgstr "* 记录动态分配资源使用事件 * "
+
+# b098284613414134b2cd3e2527db633b
+#: ../../service_offerings.rst:143
+msgid ""
+"To support this feature, usage events has been enhanced to register events "
+"for dynamically assigned resources. Usage events are registered when a VM is"
+" created from a custom compute offering, and upon changing the compute "
+"offering of a stopped or running VM. The values of the parameters, such as "
+"CPU, speed, RAM are recorded."
+msgstr "为了支持该功能，使用事件已经被增强到动态分配资源注册事件中。当从一个自定义计算方案创建一个虚拟机时，使用事件被注册，并紧接更改处于停止状态或者运行状态虚拟机的计算方案。如 CPU ，速度，RAM 这些参数的值被记录下来。"
+
+# 64a1b09cdfbd4e95b1fcdf2ba0db010b
+#: ../../service_offerings.rst:151
+msgid "Creating a New Compute Offering"
+msgstr "创建一个新的计算方案"
+
+# a989d37873d84df993d59a7d089d7cdd
+#: ../../service_offerings.rst:153
+msgid "To create a new compute offering:"
+msgstr "为了创建一个新的计算方案"
+
+# cd40916e685345c99849ac58022fd684
+# 3f783f61450b417ea824bafee21771db
+# a464ec4a658b4d9884f389505fe3ad18
+#: ../../service_offerings.rst:155 ../../service_offerings.rst:276
+#: ../../service_offerings.rst:375
+msgid "Log in with admin privileges to the CloudStack UI."
+msgstr "以管理员权限登录CloudStack用户界面。"
+
+# 430fa2ee248b407f9d4085fb63dd7d77
+# 999d0aeef65e43539cf25bcb3f791342
+# b51af425528d45d6b50797a303b9badc
+#: ../../service_offerings.rst:157 ../../service_offerings.rst:278
+#: ../../service_offerings.rst:377
+msgid "In the left navigation bar, click Service Offerings."
+msgstr "在左侧导航栏中，点击 服务方案。"
+
+# 9d93f2c8859741418b99ea21160f5717
+#: ../../service_offerings.rst:159
+msgid "In Select Offering, choose Compute Offering."
+msgstr "选择方案中，选择计算方案"
+
+# 7167eb3ab24d4bba83156b7b67a2474a
+#: ../../service_offerings.rst:161
+msgid "Click Add Compute Offering."
+msgstr "点击 添加计算方案"
+
+# d66b1055632049b3be191768ce8d3f6f
+# 8282a7241f674568b997c0dcd2b08b88
+# 22f14b2d47e140ae9fa9f96c736f51f5
+#: ../../service_offerings.rst:163 ../../service_offerings.rst:284
+#: ../../service_offerings.rst:383
+msgid "In the dialog, make the following choices:"
+msgstr "在对话框中，选择如下操作："
+
+# 248a64cf597a40f29490a97743581cae
+#: ../../service_offerings.rst:165
+msgid "**Name**: Any desired name for the service offering."
+msgstr "** 名称 **: 服务方案所需的名称。"
+
+# 16069fbe3c51423eba16ddfb98cd4dd2
+#: ../../service_offerings.rst:167
+msgid ""
+"**Description**: A short description of the offering that can be displayed "
+"to users"
+msgstr "** 描述 ** ：显示给用户的简短方案描述。"
+
+# 347237d86b124a00be0d69850897539d
+#: ../../service_offerings.rst:170
+msgid ""
+"**Storage type**: The type of disk that should be allocated. Local allocates"
+" from storage attached directly to the host where the system VM is running. "
+"Shared allocates from storage accessible via NFS."
+msgstr "** 存储类型 *：磁盘类型应该被分配。系统VM 运行时所在主机挂载的存储作为本地分配。通过 NFS 可访问的存储作为 共享分配。"
+
+# 2740734abb894968ad28ec481f8be6f8
+#: ../../service_offerings.rst:175
+msgid ""
+"**Custom**: Custom compute offerings can be used in following cases: "
+"deploying a VM, changing the compute offering of a stopped VM and running "
+"VMs, which is nothing but scaling up."
+msgstr "** 自定义 ** ：自定义计算方案使用在以下场景：部署虚拟机，改变停止状态和运行中虚拟机的计算方案，仅仅为了扩大规模。"
+
+# ca83dc70a28544378533fd9391d96e06
+#: ../../service_offerings.rst:179
+msgid ""
+"If the Custom field is checked, the end-user must fill in the desired values"
+" for number of CPU, CPU speed, and RAM Memory when using a custom compute "
+"offering. When you check this box, those three input fields are hidden in "
+"the dialog box."
+msgstr "如果自定义字段被选中，最终用户必须为CPU，CPU速度和RAM存储器的数量所需的值使用自定义计算产品时填写。当您选中该复选框，这三个输入字段隐藏在该对话框。"
+
+# 8ca7932a8f254ece814179f9c5690c71
+#: ../../service_offerings.rst:184
+msgid ""
+"**# of CPU cores**: The number of cores which should be allocated to a "
+"system VM with this offering. If Custom is checked, this field does not "
+"appear."
+msgstr "**# of CPU cores**: 在该方案中分配核心数量给系统 VM , 如果选择自定义，该区域不会出现。"
+
+# 179de46f279a47c38263160519e05bc8
+#: ../../service_offerings.rst:188
+msgid ""
+"**CPU (in MHz)**: The CPU speed of the cores that the system VM is "
+"allocated. For example, “2000” would provide for a 2 GHz clock. If Custom is"
+" checked, this field does not appear."
+msgstr "** CPU (in MHz) **: 分配给系统 VM 的 CPU 核心速度。比如 “ 2000 ” 将提供 2 GHz 时钟频率。如果选择订制，该区域不会出现"
+
+# b4862e3476024139a5791b56f164bf54
+#: ../../service_offerings.rst:192
+msgid ""
+"**Memory (in MB)**: The amount of memory in megabytes that the system VM "
+"should be allocated. For example, “2048” would provide for a 2 GB RAM "
+"allocation. If Custom is checked, this field does not appear."
+msgstr "** Memory (in MB) **: 分配给系统 VM 的内存M数。比如，, “ 2048 ” 应该提供 2 G RAM。如果选择订制，该区域不会出现。"
+
+# 75b2531b57c743c1b6077813a925c97c
+#: ../../service_offerings.rst:197
+msgid "**Network Rate**: Allowed data transfer rate in MB per second."
+msgstr "**网络速度**: 允许的数据传输速度（MB/秒）。"
+
+# d8427006117040188afa00c409a53e9c
+#: ../../service_offerings.rst:199
+msgid "**Disk Read Rate**: Allowed disk read rate in bits per second."
+msgstr "** 磁盘读取速率 ** ：磁盘每秒允许读取的bit数"
+
+# d7c08f798b324b0fa241b2bc293d9fe1
+#: ../../service_offerings.rst:201
+msgid "**Disk Write Rate**: Allowed disk write rate in bits per second."
+msgstr "** 磁盘写入速率 **： 磁盘每秒允许写入的bit数。"
+
+# 657abd8d993d47f98da0e15c0842aadd
+#: ../../service_offerings.rst:203
+msgid ""
+"**Disk Read Rate**: Allowed disk read rate in IOPS (input/output operations "
+"per second)."
+msgstr "** 磁盘读取速率 ** : IPOS (每秒的输入/输出操作 )中运行磁盘读取的速率"
+
+# 41c2fbc1baef42c6b5df3e05a520019a
+#: ../../service_offerings.rst:206
+msgid ""
+"**Disk Write Rate**: Allowed disk write rate in IOPS (input/output "
+"operations per second)."
+msgstr "** 磁盘写入速率 ** : IPOS (每秒的输入/输出操作 )中运行磁盘写入的速率"
+
+# 1ec28ce24ead4f2486f7368ade10a4e8
+#: ../../service_offerings.rst:209
+msgid ""
+"**Offer HA**: If yes, the administrator can choose to have the system VM be "
+"monitored and as highly available as possible."
+msgstr "** HA 方案 ** : 如果必要，管理员可以选择监控系统 VM 和尽可能采用高可用。"
+
+# 6d4c0c7c0d8548e3825edabb5d73d731
+#: ../../service_offerings.rst:212
+msgid ""
+"**Storage Tags**: The tags that should be associated with the primary "
+"storage used by the system VM."
+msgstr "** 存储标签 ** ：这个标签应该和系统 VM 使用的主存储相关联。"
+
+# b730850e604446d89aba06366e8302be
+#: ../../service_offerings.rst:215
+msgid "**Host Tags**: (Optional) Any tags that you use to organize your hosts"
+msgstr "** 主机标签 ** ：（可选）用于组织你的主机的任何标签。"
+
+# 6fb3e5e926cc49038912a81d7d3c1a1c
+#: ../../service_offerings.rst:218
+msgid ""
+"**CPU cap**: Whether to limit the level of CPU usage even if spare capacity "
+"is available."
+msgstr "** CPU 容量 ** : 是否限制CPU使用率的水平，即使备用容量仍可用。"
+
+# 5eff635b882c422680849b6f7d511fdb
+#: ../../service_offerings.rst:221
+msgid ""
+"**Public**: Indicate whether the service offering should be available all "
+"domains or only some domains. Choose Yes to make it available to all "
+"domains. Choose No to limit the scope to a subdomain; CloudStack will then "
+"prompt for the subdomain's name."
+msgstr "** 公共 ** : 指明系统方案是对所有域或者部分域是否可用。 选择 Yes 则所有域可用。选择 No 则限制一定范围的域可用； CloudStack 会给出一个字域名字提示。"
+
+# d401f5f62aaa4778bce3429d100a06de
+#: ../../service_offerings.rst:226
+msgid ""
+"**isVolatile**: If checked, VMs created from this service offering will have"
+" their root disks reset upon reboot. This is useful for secure environments "
+"that need a fresh start on every boot and for desktops that should not "
+"retain state."
+msgstr "** 隔离 ** ： 如果选中，从这个服务方案创建的虚拟机重启复位后都会有自己的根磁盘。这对于需要通过重启获得全新开始和无需保持桌面状态的安全环境中非常有用。"
+
+# 7ea10a7203db4d629ba1fc7dfd120b28
+#: ../../service_offerings.rst:231
+msgid ""
+"**Deployment Planner**: Choose the technique that you would like CloudStack "
+"to use when deploying VMs based on this service offering."
+msgstr "** 部署方案 ** ：当部署基于这个服务方案的虚拟机时，你会让 CloudStack 选择使用这个技术。"
+
+# 09d1468dffad438fa4266aa82987ce0e
+#: ../../service_offerings.rst:235
+msgid ""
+"First Fit places new VMs on the first host that is found having sufficient "
+"capacity to support the VM's requirements."
+msgstr "首先，存放新虚拟机的第一台主机必须有足够的容量来满足虚拟机的要求。"
+
+# 9a877ddb3dab4ad69db6b5c7627dd22c
+#: ../../service_offerings.rst:238
+msgid ""
+"User Dispersing makes the best effort to evenly distribute VMs belonging to "
+"the same account on different clusters or pods."
+msgstr " 用户分散尽最大努力均匀分配同一个账户的虚拟机在不同的集群或者提供点。"
+
+# e2716f72710c4569899cebc9a22840ab
+#: ../../service_offerings.rst:241
+msgid ""
+"User Concentrated prefers to deploy VMs belonging to the same account within"
+" a single pod."
+msgstr "用户更倾向于集中部署同一帐户内的虚拟机在单一提供点."
+
+# 5e285b8b246b49bbb76fdf939e1dc838
+#: ../../service_offerings.rst:244
+msgid ""
+"Implicit Dedication will deploy VMs on private infrastructure that is "
+"dedicated to a specific domain or account. If you choose this planner, then "
+"you must also pick a value for Planner Mode. See `“Dedicating Resources to "
+"Accounts and Domains” <accounts.html#dedicating-resources-to-accounts-and-"
+"domains>`_."
+msgstr "默认将虚拟机部署在特定域或账户的专属基础设施中。如果你选择，那么你必须为规划者参考 `“ 为账号和域指定资源 ” <accounts.html#dedicating-resources-to-accounts-and-domains>`_."
+
+# 6e9b2cfece7840a3a281d17fbf4d19cd
+#: ../../service_offerings.rst:250
+msgid ""
+"Bare Metal is used with bare metal hosts. See Bare Metal Installation in the"
+" Installation Guide."
+msgstr "裸机协同全裸机使用。参考安装向导中的全裸机安装。"
+
+# 3a40b2888d8b4d0bb06501a2d726411d
+#: ../../service_offerings.rst:253
+msgid ""
+"**Planner Mode**: Used when ImplicitDedicationPlanner is selected in the "
+"previous field. The planner mode determines how VMs will be deployed on "
+"private infrastructure that is dedicated to a single domain or account."
+msgstr "** 方案模式 ** :当在之前场景中默认指定方案被选中时使用。方案模式决定了在分享的单独域或账户的私有基础架构中部署多少虚拟机。"
+
+# 8c6a6d1601d5409f9cf07e89162fe229
+#: ../../service_offerings.rst:258
+msgid ""
+"Strict: 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 "严禁：一个主机禁止通过多个账号共享。例如，严格默认指定对于部署的某些应用是有用处的，例如，在无隔离桌面软件授权主机上不能在不同账号间进行桌面共享。"
+
+# 36d35c740f134708ade301fc640503d9
+#: ../../service_offerings.rst:264
+msgid ""
+"Preferred: The VM will be deployed in dedicated infrastructure if possible. "
+"Otherwise, the VM can be deployed in shared infrastructure."
+msgstr "优先：VM 尽可能的部署在专属基础架构。否则部署在共享基础架构。"
+
+# 094aad8be1574fa385667bebf06ed3b6
+# 857fa2723e0b4bf4916f435ba0604892
+# ac56513abaae4c1895b390a2f0333ab0
+#: ../../service_offerings.rst:268 ../../service_offerings.rst:333
+#: ../../service_offerings.rst:426
+msgid "Click Add."
+msgstr "点击 添加"
+
+# 1a46fadd2f3a42c68b8cdeef05745eca
+#: ../../service_offerings.rst:272
+msgid "Creating a New Disk Offering"
+msgstr "创建一个新的磁盘方案"
+
+# 06fce5a6dad94dfa84eed86ae00ec617
+#: ../../service_offerings.rst:274
+msgid "To create a new disk offering:"
+msgstr "为了创建一个新的磁盘方案"
+
+# d3eb3c404772407da39449916e1953ca
+#: ../../service_offerings.rst:280
+msgid "In Select Offering, choose Disk Offering."
+msgstr "在选择方案中，选择 磁盘方案"
+
+# da2d57c6d441495685b440392d59c162
+#: ../../service_offerings.rst:282
+msgid "Click Add Disk Offering."
+msgstr "点击 添加磁盘方案"
+
+# d178f97b76c84de0bfd097ef93c110d3
+#: ../../service_offerings.rst:286
+msgid "Name. Any desired name for the disk offering."
+msgstr "名字"
+
+# efaecce14927441aa329961c4d485567
+# e7bfb9a5943b405a8cae32d04743b528
+#: ../../service_offerings.rst:288 ../../service_offerings.rst:387
+msgid ""
+"Description. A short description of the offering that can be displayed to "
+"users"
+msgstr "描述。显示给用户的方案简短描述。"
+
+# 4f1a836b18b74aaf94d4ad7e5b83152c
+#: ../../service_offerings.rst:291
+msgid ""
+"Custom Disk Size. If checked, the user can set their own disk size. If not "
+"checked, the root administrator must define a value in Disk Size."
+msgstr "订制磁盘大小。如果选中，用户可以设置自己磁盘大小。如果没选中，管理员必须定义这个磁盘大小的值。"
+
+# 5663fa2cb649450db44f795449d5dd9f
+#: ../../service_offerings.rst:295
+msgid ""
+"Disk Size. Appears only if Custom Disk Size is not selected. Define the "
+"volume size in GB."
+msgstr "磁盘大小。只有 订制磁盘大小 未被选择才会显示。按照ＧＢ定义卷大小。"
+
+# d06aab69bbd44359a42d1eaebcb4ca5a
+#: ../../service_offerings.rst:298
+msgid ""
+"QoS Type. Three options: Empty (no Quality of Service), hypervisor (rate "
+"limiting enforced on the hypervisor side), and storage (guaranteed minimum "
+"and maximum IOPS enforced on the storage side). If leveraging QoS, make sure"
+" that the hypervisor or storage system supports this feature."
+msgstr "QoS 类型。三种可选：空 （ 无服务质量）， hypervisor （在 hypervisor侧强制速率限制），存储 （在存储侧保证最小和最大 IOPS)。如需使用 QoS ,确保 hypervisor 或存储系统支持此功能。"
+
+# 665e3b5c270e42979195e2837591595b
+#: ../../service_offerings.rst:304
+msgid ""
+"Custom IOPS. If checked, the user can set their own IOPS. If not checked, "
+"the root administrator can define values. If the root admin does not set "
+"values when using storage QoS, default values are used (the defauls can be "
+"overridden if the proper parameters are passed into CloudStack when creating"
+" the primary storage in question)."
+msgstr "订制 IOPS 。 如选中，用户可以设置自己的 IOPS。如未被选中，root 管理员则能够定义该值。如果使用存储 QoS时，root 管理员没有设置该值，则采用默认值（如果创建主存储时考虑到对应的参数被传递到 CloudStack 中，则默认值将被覆盖）"
+
+# 3fdd090110144e8fae3a8a6d77e6e426
+#: ../../service_offerings.rst:311
+msgid ""
+"Min IOPS. Appears only if storage QoS is to be used. Set a guaranteed "
+"minimum number of IOPS to be enforced on the storage side."
+msgstr "最小 IOPS 。只有使用存储 QoS 才会出现。在存储侧进行保障最小 IOPS 数量。"
+
+# 5f904e8920db455192f6af78633b6f22
+#: ../../service_offerings.rst:315
+msgid ""
+"Max IOPS. Appears only if storage QoS is to be used. Set a maximum number of"
+" IOPS to be enforced on the storage side (the system may go above this limit"
+" in certain circumstances for short intervals)."
+msgstr "最大 IOPS 。 使用了存储 QoS才会显示。IPOS 最大数量将在存储侧被强制设置（系统可以在短时间内超过这个限制）"
+
+# ea14b97cc586470c8be3da25ef0a3ae1
+#: ../../service_offerings.rst:319
+msgid ""
+"(Optional)Storage Tags. The tags that should be associated with the primary "
+"storage for this disk. Tags are a comma separated list of attributes of the "
+"storage. For example \"ssd,blue\". Tags are also added on Primary Storage. "
+"CloudStack matches tags on a disk offering to tags on the storage. If a tag "
+"is present on a disk offering that tag (or tags) must also be present on "
+"Primary Storage for the volume to be provisioned. If no such primary storage"
+" exists, allocation from the disk offering will fail.."
+msgstr "（可选）存储标签.这个标签应与这个磁盘的主存储相关联。标签以逗号分隔存储的属性列表。比如 \"ssd,blue\". 标签被添加在主存储上。CloudStack 通过标记匹配磁盘方案到主存储。 如果一个标签出（或多个标签）现在磁盘方案里, 那这个标签也必须出现在将要分配这个卷的主存储上。如果这样的主存储不存在, 从这个磁盘方案中进行分配将失败。"
+
+# dda851b25a4c44ae92e6890fb2542e04
+# 5034af57e1514329ba054bf08be12e5a
+#: ../../service_offerings.rst:328 ../../service_offerings.rst:421
+msgid ""
+"Public. Indicate whether the service offering should be available all "
+"domains or only some domains. Choose Yes to make it available to all "
+"domains. Choose No to limit the scope to a subdomain; CloudStack will then "
+"prompt for the subdomain's name."
+msgstr "** 公共 ** : 指明系统方案是对所有域或者部分域是否可用。 选择 Yes 则所有域可用。选择 No 则限制一定范围的域可用； CloudStack 会给出一个子域名字提示。"
+
+# 5c44a4ba4c074c4caf886309d1aba4f1
+#: ../../service_offerings.rst:337
+msgid "Modifying or Deleting a Service Offering"
+msgstr "修改或删除一个服务方案"
+
+# 5aab86d5c8e443609a4613d0073f7314
+#: ../../service_offerings.rst:339
+msgid ""
+"Service offerings cannot be changed once created. This applies to both "
+"compute offerings and disk offerings."
+msgstr "服务方案一旦被创建则不能被修改。这个特性同样适用于计算方案和磁盘方案。"
+
+# 1bab2fd909c74ac299118dcd6c9848b4
+#: ../../service_offerings.rst:342
+msgid ""
+"A service offering can be deleted. If it is no longer in use, it is deleted "
+"immediately and permanently. If the service offering is still in use, it "
+"will remain in the database until all the virtual machines referencing it "
+"have been deleted. After deletion by the administrator, a service offering "
+"will not be available to end users that are creating new instances."
+msgstr "系统服务方案可以被删除。它不再处于使用中，它可以被立即永久删除。如果服务方案处于使用中，它会留在数据库中，直到所有引用它的虚拟机被删除。管理员删除后，管理员创建新的虚拟机时这个服务方案将不可用。"
+
+# 0f1e4fe248f24ff6b4e4f47ef4a4ef55
+#: ../../service_offerings.rst:351
+msgid "System Service Offerings"
+msgstr "系统服务方案"
+
+# 007749e74de54391b1664b4166e80259
+#: ../../service_offerings.rst:353
+msgid ""
+"System service offerings provide a choice of CPU speed, number of CPUs, "
+"tags, and RAM size, just as other service offerings do. But rather than "
+"being used for virtual machine instances and exposed to users, system "
+"service offerings are used to change the default properties of virtual "
+"routers, console proxies, and other system VMs. System service offerings are"
+" visible only to the CloudStack root administrator. CloudStack provides "
+"default system service offerings. The CloudStack root administrator can "
+"create additional custom system service offerings."
+msgstr "系统服务方案提供CPU速度，CPU数量，标签和RAM大小的选择，就像其他服务方案那样。但不被用于虚拟机实例和暴露给用户，系统服务方案是用来改变虚拟路由器，console 代理，和其他系统的虚拟机的默认属性。系统服务方案只对 CloudStack中 root 管理员是可见的。CloudStack 提供默认的系统管理方案。CloudStack 中 root 管理员可以创建其他自定义系统服务方案。"
+
+# 4201666336094c93ae198477756df881
+#: ../../service_offerings.rst:362
+msgid ""
+"When CloudStack creates a virtual router for a guest network, it uses "
+"default settings which are defined in the system service offering associated"
+" with the network offering. You can upgrade the capabilities of the virtual "
+"router by applying a new network offering that contains a different system "
+"service offering. All virtual routers in that network will begin using the "
+"settings from the new service offering."
+msgstr "当 CloudStack 中创建一个虚拟路由器的来宾网络，它使用系统服务方案中的默认设置和网络方案进行关联。你可以通过应用包含不同的系统服务方案的网络方案升级的虚拟路由器的功能。该网络中的所有虚拟路由器将使用来自新服务方案的设置。"
+
+# f91e393f388b4e6481cd8a71e7f79278
+#: ../../service_offerings.rst:371
+msgid "Creating a New System Service Offering"
+msgstr "创建一个新的系统服务方案"
+
+# 0d2bc72cb0364a098544d79a257c89d8
+#: ../../service_offerings.rst:373
+msgid "To create a system service offering:"
+msgstr "为了创建一个系统服务方案："
+
+# 6e5e507b5bf94c149b3113e07ca5ce03
+#: ../../service_offerings.rst:379
+msgid "In Select Offering, choose System Offering."
+msgstr "在选择方案中，选择 系统方案"
+
+# 42a35e0d5b5e434f8fa210dfa25c0edf
+#: ../../service_offerings.rst:381
+msgid "Click Add System Service Offering."
+msgstr "点击 添加系统服务方案"
+
+# c20bf047c83a44d89017825a2228c46d
+#: ../../service_offerings.rst:385
+msgid "Name. Any desired name for the system offering."
+msgstr "名称。系统方案任意名称。"
+
+# 1d970335d51e46ac9bda9c706759ba65
+#: ../../service_offerings.rst:390
+msgid ""
+"System VM Type. Select the type of system virtual machine that this offering"
+" is intended to support."
+msgstr "系统 VM 类型。选中方案支持的系统虚拟机的类型。"
+
+# 8086a4f1336049c19479206b751d04ea
+#: ../../service_offerings.rst:393
+msgid ""
+"Storage type. The type of disk that should be allocated. Local allocates "
+"from storage attached directly to the host where the system VM is running. "
+"Shared allocates from storage accessible via NFS."
+msgstr "存储类型。应该指明磁盘类型。运行中的虚拟机所在主机关联的存储采用本地分配。通过 NFS 可访问存储共享分配。"
+
+# 913ba08b0770492cba53d3d247655710
+#: ../../service_offerings.rst:398
+msgid ""
+"# of CPU cores. The number of cores which should be allocated to a system VM"
+" with this offering"
+msgstr "# CPU 核心。方案中提供给系统 VM 可分配的核心数量。"
+
+# fb5a2f7abf0a4e18b7847db64d898bc2
+#: ../../service_offerings.rst:401
+msgid ""
+"CPU (in MHz). The CPU speed of the cores that the system VM is allocated. "
+"For example, \"2000\" would provide for a 2 GHz clock."
+msgstr "CPU ( MHz )。 分配给系统 VM CPU 核心频率。例如，” 2000 “ 将提供一个2 GHz 时钟。"
+
+# de2eaf45f59b471b9d37d34ab02ce6e2
+#: ../../service_offerings.rst:404
+msgid ""
+"Memory (in MB). The amount of memory in megabytes that the system VM should "
+"be allocated. For example, \"2048\" would provide for a 2 GB RAM allocation."
+msgstr "内存 （ MB ）。系统 VM 应该总计分配兆字节内存。例如，” 2048 “ 应该分配 2GB RAM."
+
+# c1d2470c7b62430481a4de61c2356410
+#: ../../service_offerings.rst:408
+msgid "Network Rate. Allowed data transfer rate in MB per second."
+msgstr "网络速率。每秒允许传输多少 MB 数据。"
+
+# a7d7af4efcf94e478441f58eb4ab9ec1
+#: ../../service_offerings.rst:410
+msgid ""
+"Offer HA. If yes, the administrator can choose to have the system VM be "
+"monitored and as highly available as possible."
+msgstr "提供HA。如果提供，管理员可以为监控系统 VM 并且提供必要的高可用。"
+
+# 41c4d5f0752e44e98e557a65b65a14c0
+#: ../../service_offerings.rst:413
+msgid ""
+"Storage Tags. The tags that should be associated with the primary storage "
+"used by the system VM."
+msgstr "存储标签。它应该和系统 VM 使用的主存储相关联。"
+
+# 22cd45b0933841f3bf3106245a42af05
+#: ../../service_offerings.rst:416
+msgid "Host Tags. (Optional) Any tags that you use to organize your hosts"
+msgstr "主机标签。 （ 可选 ）你可以选择任何标签用于规范你的主机。"
+
+# c8df696c132647959ca16dcad278053e
+#: ../../service_offerings.rst:418
+msgid ""
+"CPU cap. Whether to limit the level of CPU usage even if spare capacity is "
+"available."
+msgstr "CPU 容量。是否限制 CPU 使用水平不管是否还有可用的空闲容量。"
+
+# 53c64783d59d4debb2c9c1ebe4a0bb7d
+#: ../../service_offerings.rst:430
+msgid "Network Throttling"
+msgstr "网络限速"
+
+# 26cf64df6529406f922adcedb9234f9f
+#: ../../service_offerings.rst:432
+msgid ""
+"Network throttling is the process of controlling the network access and "
+"bandwidth usage based on certain rules. CloudStack controls this behaviour "
+"of the guest networks in the cloud by using the network rate parameter. This"
+" parameter is defined as the default data transfer rate in Mbps (Megabits "
+"Per Second) allowed in a guest network. It defines the upper limits for "
+"network utilization. If the current utilization is below the allowed upper "
+"limits, access is granted, else revoked."
+msgstr "网络限速是基于明确规则来控制网络访问和带宽使用率的一个进程。 CloudStack 中通过网络速率参数来控制来宾网络在云中的行为。这个参数定义一个来宾网络允许的默认数据传输速率为 Mbps （兆比特每秒）。它定义了网络利用上限。如果目前的使用率低于允许的上限，则允许访问，否则拒绝。"
+
+# 27806198975d424082e8dab6ce49f0b4
+#: ../../service_offerings.rst:440
+msgid ""
+"You can throttle the network bandwidth either to control the usage above a "
+"certain limit for some accounts, or to control network congestion in a large"
+" cloud environment. The network rate for your cloud can be configured on the"
+" following:"
+msgstr "你可以在大型云环境中通过限制一些账户明确的使用率或拥塞控制来节省网络带宽。以下是可以在你的云中进行配置的网络速率："
+
+# 7432018ff67f4894a723bdca6bff087b
+#: ../../service_offerings.rst:445
+msgid "Network Offering"
+msgstr "网络方案"
+
+# 506188e4ff414063a2491e10c81e51c9
+#: ../../service_offerings.rst:447
+msgid "Service Offering"
+msgstr "服务方案"
+
+# 320ac2d073ce4bf5af25029badc0cdb4
+#: ../../service_offerings.rst:449
+msgid "Global parameter"
+msgstr "全局参数"
+
+# 9c2fc1907fa34cf7b21cefc002bff096
+#: ../../service_offerings.rst:451
+msgid ""
+"If network rate is set to NULL in service offering, the value provided in "
+"the vm.network.throttling.rate global parameter is applied. If the value is "
+"set to NULL for network offering, the value provided in the "
+"network.throttling.rate global parameter is considered."
+msgstr "服务方案中如果网络速率设置为 NULL , vm.network.throttling.rate 值作为全局参数被应用。网络方案中如果这个值设置为 NULL 。network.throttling.rate 值被看做全局参数。"
+
+# 70d2185fb70847edb5c332fb612484e7
+#: ../../service_offerings.rst:456
+msgid ""
+"For the default public, storage, and management networks, network rate is "
+"set to 0. This implies that the public, storage, and management networks "
+"will have unlimited bandwidth by default. For default guest networks, "
+"network rate is set to NULL. In this case, network rate is defaulted to the "
+"global parameter value."
+msgstr "对于默认的公共，存储和管理网络，网络速度被设置为0，这意味着，公共，存储和管理网络默认不被限制带宽。对于默认来宾网络，网络速率设置为 NULL 。在这种情况下，网络速率被默认为全局参数值。"
+
+# 88f665be2f3e4cfd87c6d89ae2b118ef
+#: ../../service_offerings.rst:462
+msgid ""
+"The following table gives you an overview of how network rate is applied on "
+"different types of networks in CloudStack."
+msgstr "你可以在大型云环境中通过限制一些账户明确的使用率或拥塞控制来节省网络带宽。以下是可以在你的云中进行配置的网络速率："
+
+# 2df7571b44394db29aa0803e1bd515ae
+#: ../../service_offerings.rst:466
+msgid "Networks"
+msgstr "网络"
+
+# 30beee005ab04cb3947aa3a093695d15
+#: ../../service_offerings.rst:466
+msgid "Network Rate Is Taken from"
+msgstr "网络速率起源"
+
+# 2d1b0256284f4e9196bed7491709337e
+#: ../../service_offerings.rst:468
+msgid "Guest network of Virtual Router"
+msgstr "来宾网络虚拟路由器"
+
+# 710cff98d40d47b1b4691f4ef4cc0ed7
+# 7301bab7c1654ab09e4495741b32f409
+#: ../../service_offerings.rst:468 ../../service_offerings.rst:469
+msgid "Guest Network Offering"
+msgstr "来宾网络方案"
+
+# b9550d4e593644f7997ae2b59833d30e
+#: ../../service_offerings.rst:469
+msgid "Public network of Virtual Router"
+msgstr "公网网络虚拟路由器"
+
+# 5fbb2616fe4146139b5adddf90e140c5
+#: ../../service_offerings.rst:470
+msgid "Storage network of Secondary Storage VM"
+msgstr "辅助存储 VM 的存储网络"
+
+# 149bbe361c7b4f85bc046a55d9a0147e
+# f68c6d576d58455194ee074721af9ab1
+# 6767654cd1d74942a8dc4a4a997c0e62
+# 9784131010fd47ce8cbdf1d9b322bdd6
+# fcb50bbb01464259bf0060a49547950f
+# 3499985b0b95428c8cf13bdceeacae5c
+# 9eb605f5c4204f7a93451b0af6b0ac63
+# a5eff8a6947548b99a5e9c63a24f4890
+#: ../../service_offerings.rst:470 ../../service_offerings.rst:471
+#: ../../service_offerings.rst:472 ../../service_offerings.rst:473
+#: ../../service_offerings.rst:474 ../../service_offerings.rst:475
+#: ../../service_offerings.rst:476 ../../service_offerings.rst:477
+msgid "System Network Offering"
+msgstr "系统网络方案"
+
+# d0e8015a02d74f79a085327db997c47a
+#: ../../service_offerings.rst:471
+msgid "Management network of Secondary Storage VM"
+msgstr "辅助存储 VM 的管理网络"
+
+# 5ec6da9e6d934d9fad3bede5813f70f9
+#: ../../service_offerings.rst:472
+msgid "Storage network of Console Proxy VM"
+msgstr "Console 代理 VM 的存储网络"
+
+# 4cf8b23c38354b708cd82d9c7e31ff03
+#: ../../service_offerings.rst:473
+msgid "Management network of Console Proxy VM"
+msgstr "Console 代理 VM 的管理玩了过"
+
+# 2ff0726b224449c08b32d13597df71a7
+#: ../../service_offerings.rst:474
+msgid "Storage network of Virtual Router"
+msgstr "虚拟路由器的存储网络"
+
+# 91083f647e9345d4a21912156d7990dd
+#: ../../service_offerings.rst:475
+msgid "Management network of Virtual Router"
+msgstr "虚拟路由器的管理网络"
+
+# 20a8e9d21dda41208554a4065467ea8e
+#: ../../service_offerings.rst:476
+msgid "Public network of Secondary Storage VM"
+msgstr "辅助存储 VM 的公共网络"
+
+# 801f07af30a34b239adb18ef1edcd47c
+#: ../../service_offerings.rst:477
+msgid "Public network of Console Proxy VM"
+msgstr "Console 代理 VM 的公共玩了过"
+
+# 860138dcf0344072bed2a8184a5336c7
+#: ../../service_offerings.rst:478
+msgid "Default network of a guest VM"
+msgstr "Console 代理 VM 的默认网络"
+
+# a6f07fe2acf94351951e197227848984
+#: ../../service_offerings.rst:478
+msgid "Compute Offering"
+msgstr "计算方案"
+
+# bb5e6134192f48038cbdfcc8141882da
+#: ../../service_offerings.rst:479
+msgid "Additional networks of a guest VM"
+msgstr "来宾 VM 的附加网络"
+
+# 9cdc4ff5ef2e42b39986c9157d856fc7
+#: ../../service_offerings.rst:479
+msgid "Corresponding Network Offerings"
+msgstr "对应的网络方案"
+
+# 82ee01b4006f4ba48baf48b75381dac7
+#: ../../service_offerings.rst:482
+msgid ""
+"A guest VM must have a default network, and can also have many additional "
+"networks. Depending on various parameters, such as the host and virtual "
+"switch used, you can observe a difference in the network rate in your cloud."
+" For example, on a VMware host the actual network rate varies based on where"
+" they are configured (compute offering, network offering, or both); the "
+"network type (shared or isolated); and traffic direction (ingress or "
+"egress)."
+msgstr "一个来宾虚拟机必须有一个默认网络，也可拥有多个附加网。根据各种参数，如主机和虚拟交换机使用，你可以观察到在云网络中的不同速率。例如，在 VMware 主机的实际网络速率依赖于其他配置( 计算方案，网络方案，或两者兼有 )；网络类型( 共享或隔离 )和流量方向( 入口或出口 )。"
+
+# a3a45b2e646846f984140407ef18cd47
+#: ../../service_offerings.rst:490
+msgid ""
+"The network rate set for a network offering used by a particular network in "
+"CloudStack is used for the traffic shaping policy of a port group, for "
+"example: port group A, for that network: a particular subnet or VLAN on the "
+"actual network. The virtual routers for that network connects to the port "
+"group A, and by default instances in that network connects to this port "
+"group. However, if an instance is deployed with a compute offering with the "
+"network rate set, and if this rate is used for the traffic shaping policy of"
+" another port group for the network, for example port group B, then "
+"instances using this compute offering are connected to the port group B, "
+"instead of connecting to port group A."
+msgstr "CloudStack 中特定网络使用网络方案的网络速率设置将应用到端口组的流量整形策略中。例如：端口组 A , 网络 : 现实网络的特定子网或 VLAN 。网络通过虚拟路由器连接端口组 A ，同时网络中默认实例也连接该端口组。尽管如此，如果通过设置了网络速率的计算方案部署虚拟机，并且如果这个网络速率通过流量整形策略应用到其他端口组。例如端口组 B , 使用该计算方案的实例连接到端口组 B 将 替换到端口组 A 的连接。"
+
+# 439cfd7a4cdd405c9eb7e554009d476e
+#: ../../service_offerings.rst:501
+msgid ""
+"The traffic shaping policy on standard port groups in VMware only applies to"
+" the egress traffic, and the net effect depends on the type of network used "
+"in CloudStack. In shared networks, ingress traffic is unlimited for "
+"CloudStack, and egress traffic is limited to the rate that applies to the "
+"port group used by the instance if any. If the compute offering has a "
+"network rate configured, this rate applies to the egress traffic, otherwise "
+"the network rate set for the network offering applies. For isolated "
+"networks, the network rate set for the network offering, if any, effectively"
+" applies to the ingress traffic. This is mainly because the network rate set"
+" for the network offering applies to the egress traffic from the virtual "
+"router to the instance. The egress traffic is limited by the rate that "
+"applies to the port group used by the instance if any, similar to shared "
+"networks."
+msgstr "VMWARE中基于标准端口组流量整形策略只被应用于出口流量，并且网络效果依赖于 CloudStack 中使用的网络类型。共享网络中，不限制 CloudStack 入口流量，同时限制出口流量到任何实例应用到端口组的速率。如果计算方案配置了网络速率，速率应用到出口流量，否则应用网络方案的网络速率设置。对于隔离网络，网络方案设置网络速率，如果明确了范围，会对入口流量产生影响。这个主要是因为网络方案的网络速率设置应用在虚拟路由器到实例之间的出口流量上。在一定范围内，实例通过端口组速率限制出口流量，这个和共享网络类似。"
+
+# 1a67086f74d24fdca3d3c8ddc160b6a1
+#: ../../service_offerings.rst:515
+msgid "For example:"
+msgstr "例如："
+
+# 1ef70fcdcb7742dd9f1e68d72b62bab8
+#: ../../service_offerings.rst:517
+msgid "Network rate of network offering = 10 Mbps"
+msgstr "网络方案网络速率 = 10 Mbps"
+
+# 4aed36fd4b1e47b994e240a5180902f7
+#: ../../service_offerings.rst:519
+msgid "Network rate of compute offering = 200 Mbps"
+msgstr "计算方案网络速率 = 200 Mbps"
+
+# 728d67e125214dc69bcb42e87a0bd8ae
+#: ../../service_offerings.rst:521
+msgid ""
+"In shared networks, ingress traffic will not be limited for CloudStack, "
+"while egress traffic will be limited to 200 Mbps. In an isolated network, "
+"ingress traffic will be limited to 10 Mbps and egress to 200 Mbps."
+msgstr "共享网络中。CloudStack 这种进入流量不进行限制，同时出口流量限制为 200 Mbps。隔离网络入口流量限制为 10 Mbps，同时出口流量限制到 200 Mbps"
+
+# c18fc63ba86d45f6a4a69c240bcbd863
+#: ../../service_offerings.rst:528
+msgid "Changing the Default System Offering for System VMs"
+msgstr "修改系统 VM 的默系统方案"
+
+# dce8139f2a074eda9f35ccab7be40838
+#: ../../service_offerings.rst:530
+msgid ""
+"You can manually change the system offering for a particular System VM. "
+"Additionally, as a CloudStack administrator, you can also change the default"
+" system offering used for System VMs."
+msgstr "你可认为的修改一个特殊系统 VM 的系统方案。此外，作为一个 CloudStack 管理员，你也可以改变系统 VM 使用的默认系统方案。"
+
+# d7758b140e8f4c8ea68093fe1bd87309
+#: ../../service_offerings.rst:534
+msgid "Create a new system offering."
+msgstr "创建一个新的系统方案"
+
+# 60b70b45018c4c8398470022264172b3
+#: ../../service_offerings.rst:536
+msgid "For more information, see Creating a New System Service Offering."
+msgstr "获取更多信息，查看 创建一个新的系统服务方案"
+
+# c8a9263bb9974a9fb39e3ce36805a635
+#: ../../service_offerings.rst:538
+msgid "Back up the database:"
+msgstr "备份数据库："
+
+# 7a52c92add7a4ae696f4727651be9ba4
+#: ../../service_offerings.rst:544
+msgid "Open an MySQL prompt:"
+msgstr "打开一个 MySQL 提示："
+
+# 51c46ec1b2844020aea4f791b5a5950e
+#: ../../service_offerings.rst:550
+msgid "Run the following queries on the cloud database."
+msgstr "在 cloud 数据库运行以下查询。"
+
+# 6ee5a9e0f1d249749376ed26cf656f31
+#: ../../service_offerings.rst:552
+msgid ""
+"In the disk\\_offering table, identify the original default offering and the"
+" new offering you want to use by default."
+msgstr "在磁盘 \\_offering 表，验证原始默认方案和你想默认使用的新方案。"
+
+# 2611865e94844c71b289c6243b7a2e4c
+#: ../../service_offerings.rst:555
+msgid "Take a note of the ID of the new offering."
+msgstr "记录新方案的 ID"
+
+# 31118e91861d48389cbab25fa138f75e
+#: ../../service_offerings.rst:561
+msgid ""
+"For the original default offering, set the value of unique\\_name to NULL."
+msgstr "对于原始默认方案，设置 \\_name 唯一值为 NULL"
+
+# 04fa9b26725d4ca09b7fd864838698ac
+#: ../../service_offerings.rst:568
+msgid "Ensure that you use the correct value for the ID."
+msgstr "确保你使用正确的 ID 值"
+
+# 8884980ed2d74f3ab78d5bfec97e5861
+#: ../../service_offerings.rst:570
+msgid ""
+"For the new offering that you want to use by default, set the value of "
+"unique\\_name as follows:"
+msgstr "对于你想使用默认值的新方案，参照以下进行唯一 \\_name 值设置："
+
+# bc246e06f82a4bc2a0d1c4ba3aad6618
+#: ../../service_offerings.rst:573
+msgid ""
+"For the default Console Proxy VM (CPVM) offering,set unique\\_name to 'Cloud"
+".com-ConsoleProxy'. For the default Secondary Storage VM (SSVM) offering, "
+"set unique\\_name to 'Cloud.com-SecondaryStorage'. For example:"
+msgstr "对于默认控制台代理虚拟机 （ CPVM ）方案， 设置唯一 \\_name 为 ' Cloud.com-ConsoleProxy '。对于默认辅助存储虚拟机 （ SSVM ) 方案， 设置唯一 \\_name 为 ' Cloud.com-SecondaryStorage '。例如："
+
+# aebfd61c6ee344829f0ec8db45c37d75
+#: ../../service_offerings.rst:582
+msgid ""
+"Restart CloudStack Management Server. Restarting is required because the "
+"default offerings are loaded into the memory at startup."
+msgstr "重启 CloudStack 管理器服务器。因为默认方案启动时被加载到内存，要求重启。"
+
+# 9f700ce4ec00451991c06d4850686fa9
+#: ../../service_offerings.rst:589
+msgid ""
+"Destroy the existing CPVM or SSVM offerings and wait for them to be "
+"recreated. The new CPVM or SSVM are configured with the new offering."
+msgstr "销毁存在的 CPVM 或 SSVM 方案，并等待它们重建。 通过新的系统方案配置新的 CPVM 或 SSVM。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/storage.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/storage.mo
new file mode 100644
index 0000000..5c691d8
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/storage.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/storage.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/storage.po
new file mode 100644
index 0000000..af85d5e
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/storage.po
@@ -0,0 +1,1460 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:04+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 32b44221e38d43c08f57ce3a72c53f03
+#: ../../storage.rst:18
+msgid "Working with Storage"
+msgstr "使用存储"
+
+# 10d8b20690d442af8af5376748e600e0
+#: ../../storage.rst:21
+msgid "Storage Overview"
+msgstr "存储概述"
+
+# 59f0d86b537245ecb2688c84730ca29a
+#: ../../storage.rst:23
+msgid ""
+"CloudStack defines two types of storage: primary and secondary. Primary "
+"storage can be accessed by either iSCSI or NFS. Additionally, direct "
+"attached storage may be used for primary storage. Secondary storage is "
+"always accessed using NFS."
+msgstr "CloudStack定义了两种存储：主存储和辅助存储。主存储可以使用iSCSI或NFS协议。另外，直接附加存储可被用于主存储。辅助存储通常使用NFS协议。"
+
+# 20876e254ad044ddaa6b6090751c79d2
+#: ../../storage.rst:28
+msgid ""
+"There is no ephemeral storage in CloudStack. All volumes on all nodes are "
+"persistent."
+msgstr "CloudStack不支持临时存储。所有节点上的所有卷都是持久存储。"
+
+# bf8fb32949b941d98036a5312e70d5a4
+#: ../../storage.rst:33
+msgid "Primary Storage"
+msgstr "主存储"
+
+# d56fc829e85b469dae70016a093f1050
+#: ../../storage.rst:35
+msgid ""
+"This section gives concepts and technical details about CloudStack primary "
+"storage. For information about how to install and configure primary storage "
+"through the CloudStack UI, see the Installation Guide."
+msgstr "本章节讲述的是关于CloudStack的主存储概念和技术细节。更多关于如何通过CloudStack UI安装和配置主存储的信息，请参阅安装向导。"
+
+# 950476049a7645b887c0f50e0a4d1f27
+#: ../../storage.rst:39
+msgid ""
+"`“About Primary Storage” "
+"<http://docs.cloudstack.apache.org/en/latest/concepts.html#about-primary-"
+"storage>`_"
+msgstr "`“关于主存储” <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-primary-storage>`_"
+
+# c26af650001f4c28b6d9803b7efde40e
+#: ../../storage.rst:43
+msgid "Best Practices for Primary Storage"
+msgstr "主存储的最佳实践"
+
+# 6f52e89385424e26a23b25f5784a3491
+#: ../../storage.rst:45
+msgid ""
+"The speed of primary storage will impact guest performance. If possible, "
+"choose smaller, higher RPM drives or SSDs for primary storage."
+msgstr "主存储的速度会直接影响来宾虚机的性能。如果可能，为主存储选择选择容量小，转速高的硬盘或SSDs。"
+
+# f8f87fc7d7e4415b831b34939cbe9b12
+#: ../../storage.rst:49
+msgid "There are two ways CloudStack can leverage primary storage:"
+msgstr "CloudStack用两种方式使用主存储："
+
+# 52ac4abe89dd4b3586b61386e9b5b0e5
+#: ../../storage.rst:51
+msgid ""
+"Static: This is CloudStack's traditional way of handling storage. In this "
+"model, a preallocated amount of storage (ex. a volume from a SAN) is given "
+"to CloudStack. CloudStack then permits many of its volumes to be created on "
+"this storage (can be root and/or data disks). If using this technique, "
+"ensure that nothing is stored on the storage. Adding the storage to "
+"CloudStack will destroy any existing data."
+msgstr "静态：CloudStack管理存储的传统方式。在这个模式下，要给CloudStack预先分配几个存储(比如一个SAN上的卷)。然后CloudStack在上面创建若干个卷(可以是root和/或者数据盘)。如果使用这种技术，确保存储上没有数据。给CloudStack添加存储会销毁已存在的所有数据。"
+
+# 813a87ee26ba4259a5c3ef52a1b0ef5a
+#: ../../storage.rst:59
+msgid ""
+"Dynamic: This is a newer way for CloudStack to manage storage. In this "
+"model, a storage system (rather than a preallocated amount of storage) is "
+"given to CloudStack. CloudStack, working in concert with a storage plug-in, "
+"dynamically creates volumes on the storage system and each volume on the "
+"storage system maps to a single CloudStack volume. This is highly useful for"
+" features such as storage Quality of Service. Currently this feature is "
+"supported for data disks (Disk Offerings)."
+msgstr "动态：这是一个比较新的CloudStack管理存储的方式。在这个模式中，给CloudStack使用的是一个存储系统(但不是预分配的存储)。CloudStack配合存储一起工作，动态的在存储系统上创建卷并且存储系统上的每个卷都映射到一个CloudStack卷。这样做非常有利于存储的QoS。目前数据磁盘(磁盘方案)支持这个特性。"
+
+# f97cbc96312f49aba2a6bab0d1e1b2a4
+#: ../../storage.rst:70
+msgid "Runtime Behavior of Primary Storage"
+msgstr "主存储的运行时行为"
+
+# 5bf02a65cf3a40df9e7e165fd9ecd864
+#: ../../storage.rst:72
+msgid ""
+"Root volumes are created automatically when a virtual machine is created. "
+"Root volumes are deleted when the VM is destroyed. Data volumes can be "
+"created and dynamically attached to VMs. Data volumes are not deleted when "
+"VMs are destroyed."
+msgstr "当创建虚拟机的时候，root卷也会自动的创建。在VM被销毁的时候root卷也会被删除。数据卷可以被创建并动态的挂载到VMs上。VMs销毁时并不会删除数据卷。"
+
+# 80ad3630b276444cac7f5324ecf5a326
+#: ../../storage.rst:77
+msgid ""
+"Administrators should monitor the capacity of primary storage devices and "
+"add additional primary storage as needed. See the Advanced Installation "
+"Guide."
+msgstr "管理员可以监控主存储设备的容量和在需要时添加其他的主存储。强参阅高级安装指导。"
+
+# 073d4376c5e04c77bbfdba19e134418c
+#: ../../storage.rst:81
+msgid ""
+"Administrators add primary storage to the system by creating a CloudStack "
+"storage pool. Each storage pool is associated with a cluster or a zone."
+msgstr "管理员通过CloudStack创建存储池来给系统添加主存储。每个存储池对应一个群集或者区域。"
+
+# 79ff1a8b27224fff8510e3a5ce37a304
+#: ../../storage.rst:85
+msgid ""
+"With regards to data disks, when a user executes a Disk Offering to create a"
+" data disk, the information is initially written to the CloudStack database "
+"only. Upon the first request that the data disk be attached to a VM, "
+"CloudStack determines what storage to place the volume on and space is taken"
+" from that storage (either from preallocated storage or from a storage "
+"system (ex. a SAN), depending on how the primary storage was added to "
+"CloudStack)."
+msgstr "对于数据磁盘，当一个用户执行一个磁盘方案来创建数据磁盘的时候，初始化信息就被写到了CloudStack的数据库中。根据第一次给VM附加数据磁盘的请求，CloudStack决定这个卷的位置和空间占用在哪个存储(预分配存储和存储系统(比如SAN)中的任意一种，这取决于CloudStack使用的哪种主存储)。"
+
+# 03d9238ac1b44704b10a3c6cbc9a194c
+#: ../../storage.rst:95
+msgid "Hypervisor Support for Primary Storage"
+msgstr "Hypervisor对主存储的支持"
+
+# f9043e1c7c614dcab5cc48b83c777751
+#: ../../storage.rst:97
+msgid ""
+"The following table shows storage options and parameters for different "
+"hypervisors."
+msgstr "下表显示了针对不同Hypervisors的存储选项和参数。"
+
+# df81aa4abfe0426f8ea7b5d76689b532
+#: ../../storage.rst:101
+msgid "Storage media \\\\ hypervisor"
+msgstr "存储媒介 \\\\ hypervisor"
+
+# 21dd8b1cdc0d40dc8559cbcf4fbfab3d
+# 6e7b702add314a16a42c7e999147c3c9
+#: ../../storage.rst:101 ../../storage.rst:709
+msgid "VMware vSphere"
+msgstr "VMware vSphere"
+
+# 95085080f31c48d7a3c6eeb26d596976
+# fd649d92db414b198a27e37febfdfe07
+#: ../../storage.rst:101 ../../storage.rst:709
+msgid "Citrix XenServer"
+msgstr "Citrix XenServer"
+
+# 94199ee2b07049529bc3e9c2b7eb8707
+# 7b0dbf552cc34bb0ac898f31180f3a83
+# 3f78f67d3c14490da80f847d2a00fc5d
+#: ../../storage.rst:101 ../../storage.rst:332 ../../storage.rst:709
+msgid "KVM"
+msgstr "KVM"
+
+# b63b5cf8a70b492f82138dc7fd0b3d4f
+#: ../../storage.rst:101
+msgid "Hyper-V"
+msgstr "Hyper-V"
+
+# 6b911e3d65954475be2786623c89bfee
+#: ../../storage.rst:103
+msgid "**Format for Disks, Templates, and Snapshots**"
+msgstr "**磁盘、模板和快照的格式**"
+
+# 597a7a22248749eab119febe7cad0654
+#: ../../storage.rst:103
+msgid "VMDK"
+msgstr "VMDK"
+
+# dcb226ea6af24150b270ebd0e57ce0d6
+# 06b1f702f7ae492c9259258d6cdb9bba
+#: ../../storage.rst:103 ../../storage.rst:330
+msgid "VHD"
+msgstr "VHD"
+
+# 3c8131f767e745659f09e7635e52de1d
+# 891d2deb650249bdaaa476d91cedea41
+#: ../../storage.rst:103 ../../storage.rst:332
+msgid "QCOW2"
+msgstr "QCOW2"
+
+# 0ef733d6419b49ddb03a35218b141dad
+#: ../../storage.rst:103
+msgid "VHD Snapshots are not supported."
+msgstr "不支持VHD快照。"
+
+# 366c31ae3c524e20bcbff9f5b0f33865
+#: ../../storage.rst:105
+msgid "**iSCSI support**"
+msgstr "**支持iSCSI**"
+
+# 169329b4d94f4d5a9a71e806fc6493ee
+# eb8734785e1e4253ae29efadaea66c18
+#: ../../storage.rst:105 ../../storage.rst:106
+msgid "VMFS"
+msgstr "VMFS"
+
+# 439fbab809dc46b291a52de0067fb0f5
+#: ../../storage.rst:105
+msgid "Clustered LVM"
+msgstr "集群化的LVM"
+
+# 7166fec7c32746bea34118f3db301ae6
+# aa36e5087ca64a9590ad2b643c91d5f7
+#: ../../storage.rst:105 ../../storage.rst:106
+msgid "Yes, via Shared Mountpoint"
+msgstr "支持，通过Shared Mountpoint"
+
+# 03d269fc73bc48348ab1896256774ae1
+# ce5af21795294bc697ba5aa4474636da
+# 785a027864c94241bdfc6686ade2836e
+# 3099d25cace04a4788cd2531e69b4710
+# 2e285148115d4a2da6cae3f373aba27f
+# 895e4b1ff76840cc94de98328f387f6f
+# 8353d798b3004fb5bbd003df12fac8a2
+# 9695a4455edd45c899785834ba6fef74
+# 7857cd4194be451faa95e02696061cf8
+#: ../../storage.rst:105 ../../storage.rst:106 ../../storage.rst:107
+#: ../../storage.rst:109 ../../storage.rst:110 ../../storage.rst:110
+#: ../../storage.rst:110 ../../storage.rst:711 ../../storage.rst:711
+msgid "No"
+msgstr "否"
+
+# b70b0d5267be474c85b0240f24b6a2b9
+#: ../../storage.rst:106
+msgid "**Fiber Channel support**"
+msgstr "**支持FC**"
+
+# 443c6e664d6b46a9a0f879410a6e1aa7
+#: ../../storage.rst:106
+msgid "Yes, via Existing SR"
+msgstr "支持，通过已有的SR"
+
+# b46dc3d64ece43109c0051e5fc0d66e5
+#: ../../storage.rst:107
+msgid "**NFS support**"
+msgstr "**支持NFS**"
+
+# ac7f31ad38674dd5bd5040d072b67e09
+# de71afbac6cb457caff9416ed30e2d9c
+# 12e7d7ffb19d4610a624484aaffeebf2
+# 10601f00b2d54ae1833a5b8cf47428ea
+# cfade3e6b2824c0b8ae1ddfc34d36e9a
+# 4b311bb6db4b41779b0c525c589c00a7
+# 6ab3b70adba24666a78774746ccfabad
+# bed48ae68b8e4818aad52abb69bbc24b
+# 11121f7bcfdc45db85459a8f12982e26
+#: ../../storage.rst:107 ../../storage.rst:107 ../../storage.rst:107
+#: ../../storage.rst:108 ../../storage.rst:108 ../../storage.rst:108
+#: ../../storage.rst:108 ../../storage.rst:110 ../../storage.rst:711
+msgid "Yes"
+msgstr "是"
+
+# 8c9b266cc80241eda65595fd19a54dc7
+#: ../../storage.rst:108
+msgid "**Local storage support**"
+msgstr "**支持本地存储**"
+
+# 1b48c07eb50544109f66a49c39c5d38c
+#: ../../storage.rst:109
+msgid "**Storage over-provisioning**"
+msgstr "**存储超配**"
+
+# 36ee1094090c495d95a6a7650892ffae
+#: ../../storage.rst:109
+msgid "NFS and iSCSI"
+msgstr "NFS 和 iSCSI"
+
+# 565842e982394810bcd8454836b9b271
+# bb172a9d571244538e501ba593025cd6
+#: ../../storage.rst:109 ../../storage.rst:109
+msgid "NFS"
+msgstr "NFS"
+
+# a5915b6a85a64a268e5a1e41080fa835
+#: ../../storage.rst:110
+msgid "**SMB/CIFS**"
+msgstr "**SMB/CIFS**"
+
+# 8f37dda63c1a49f084a39311ad775fd6
+#: ../../storage.rst:113
+msgid ""
+"XenServer uses a clustered LVM system to store VM images on iSCSI and Fiber "
+"Channel volumes and does not support over-provisioning in the hypervisor. "
+"The storage server itself, however, can support thin-provisioning. As a "
+"result the CloudStack can still support storage over-provisioning by running"
+" on thin-provisioned storage volumes."
+msgstr "XenServer通过在iSCSI和FC卷上使用集群化的LVM系统来存储VM镜像，并且不支持存储超配。尽管存储本身支持自动精简配置。不过CloudStack仍然支持在有自动精简配置的存储卷上使用存储超配。"
+
+# d8bfde747fd541bcb2d1f62d1d2ddd9c
+#: ../../storage.rst:119
+msgid ""
+"KVM supports \"Shared Mountpoint\" storage. A shared mountpoint is a file "
+"system path local to each server in a given cluster. The path must be the "
+"same across all Hosts in the cluster, for example /mnt/primary1. This shared"
+" mountpoint is assumed to be a clustered filesystem such as OCFS2. In this "
+"case the CloudStack does not attempt to mount or unmount the storage as is "
+"done with NFS. The CloudStack requires that the administrator insure that "
+"the storage is available"
+msgstr "KVM支持 \"Shared Mountpoint\"存储。Shared Mountpoint是群集中每个服务器本地文件系统中的一个路径。群集所有主机中的该路径必须一致，比如/mnt/primary1。并假设Shared Mountpoint是一个集群文件系统如OCFS2。在这种情况下，CloudStack不会把它当做NFS存储去尝试挂载或卸载。CloudStack需要管理员确保该存储是可用的。"
+
+# 80ebb012a77045e9b3a5a47d82cef42c
+#: ../../storage.rst:127
+msgid ""
+"With NFS storage, CloudStack manages the overprovisioning. In this case the "
+"global configuration parameter storage.overprovisioning.factor controls the "
+"degree of overprovisioning. This is independent of hypervisor type."
+msgstr "在NFS存储中，CloudStack管理超配。这种情况下，使用全局配置参数storage.overprovisioning.factor来控制超配的范围。且不受hyperviso类型约束。"
+
+# 46f7d4fdff4d4ea996d136375ac93805
+#: ../../storage.rst:132
+msgid ""
+"Local storage is an option for primary storage for vSphere, XenServer, and "
+"KVM. When the local disk option is enabled, a local disk storage pool is "
+"automatically created on each host. To use local storage for the System "
+"Virtual Machines (such as the Virtual Router), set "
+"system.vm.use.local.storage to true in global configuration."
+msgstr "在vSphere, XenServer和KVM中，本地存储是一个可选项。当选择了使用本地存储，所有主机会自动创建本地存储池。想要系统虚拟机 (例如虚拟路由器)使用本地存储，请设置全局配置参数system.vm.use.local.storage为true."
+
+# 84339fc995ab461cb30e853b024629a4
+#: ../../storage.rst:138
+msgid ""
+"CloudStack supports multiple primary storage pools in a Cluster. For "
+"example, you could provision 2 NFS servers in primary storage. Or you could "
+"provision 1 iSCSI LUN initially and then add a second iSCSI LUN when the "
+"first approaches capacity."
+msgstr "CloudStack支持在一个群集内有多个主存储池。比如，使用2个NFS服务器提供主存储。或原有的1个iSCSI LUN达到一定容量时再添加第二个iSCSI LUN。"
+
+# 16767f52da5e4a3ea351cb7c2208207a
+#: ../../storage.rst:145
+msgid "Storage Tags"
+msgstr "存储标签"
+
+# d0ffba1bad5942adaca099b572104c63
+#: ../../storage.rst:147
+msgid ""
+"Storage may be \"tagged\". A tag is a text string attribute associated with "
+"primary storage, a Disk Offering, or a Service Offering. Tags allow "
+"administrators to provide additional information about the storage. For "
+"example, that is a \"SSD\" or it is \"slow\". Tags are not interpreted by "
+"CloudStack. They are matched against tags placed on service and disk "
+"offerings. CloudStack requires all tags on service and disk offerings to "
+"exist on the primary storage before it allocates root or data disks on the "
+"primary storage. Service and disk offering tags are used to identify the "
+"requirements of the storage that those offerings have. For example, the high"
+" end service offering may require \"fast\" for its root disk volume."
+msgstr "存储是可以被\"标签\"的。标签是与主存储、磁盘方案或服务方案关联的字符串属性。标签允许管理员给存储添加额外的信息。比如\"SSD\"或者\"慢速\"。CloudStack不负责解释标签。它不会匹配服务和磁盘方案的标签。CloudStack要求在主存储上分配root或数据磁盘之前，所有服务和磁盘方案的都已存在对应的标签。服务和磁盘方案的标签被用于识别方案对存储的要求。比如，高端服务方案可能需要它的root磁盘卷是\"快速的\""
+
+# 81b0523239f34456bfe222f88c9520e0
+#: ../../storage.rst:159
+msgid ""
+"The interaction between tags, allocation, and volume copying across clusters"
+" and pods can be complex. To simplify the situation, use the same set of "
+"tags on the primary storage for all clusters in a pod. Even if different "
+"devices are used to present those tags, the set of exposed tags can be the "
+"same."
+msgstr "标签，分配，跨集群或机架的卷复制之间的关系是很复杂的。简单的环境就是在一个机架内所有集群的主存储使用相同的标签。即使用这些标签表示不同设备，展现出来的标签组仍可以是一样的。"
+
+# b85907f2a2a546ae9312b9c9d9a443e3
+#: ../../storage.rst:167
+msgid "Maintenance Mode for Primary Storage"
+msgstr "主存储的维护模式"
+
+# 0e84968be86b4971b80b0b9f4f141840
+#: ../../storage.rst:169
+msgid ""
+"Primary storage may be placed into maintenance mode. This is useful, for "
+"example, to replace faulty RAM in a storage device. Maintenance mode for a "
+"storage device will first stop any new guests from being provisioned on the "
+"storage device. Then it will stop all guests that have any volume on that "
+"storage device. When all such guests are stopped the storage device is in "
+"maintenance mode and may be shut down. When the storage device is online "
+"again you may cancel maintenance mode for the device. The CloudStack will "
+"bring the device back online and attempt to start all guests that were "
+"running at the time of the entry into maintenance mode."
+msgstr "主存储可以被设置成维护模式。这很有用，例如，替换存储设备中坏的RAM。对存储设备的维护模式将首先停止任何新的来自预处理的来宾虚机，然后停止所有有数据卷的来宾虚机。当所有来宾虚机被停止的时候，这个存储设备就进入维护模式了并且可以关机。当存储设备再次上线的时候，你可以对这个设备取消维护模式。CloudStack将返回在线状态并且试着启动所有曾在这个设备进入维护模式前运行的来宾机器。"
+
+# 67a803ad730347ec9a5e5667d7ceadfa
+#: ../../storage.rst:182
+msgid "Secondary Storage"
+msgstr "辅助存储"
+
+# d48d908ab2384420a19689dfc1957c12
+#: ../../storage.rst:184
+msgid ""
+"This section gives concepts and technical details about CloudStack secondary"
+" storage. For information about how to install and configure secondary "
+"storage through the CloudStack UI, see the Advanced Installation Guide."
+msgstr "本章节讲述的是关于CloudStack的辅助存储概念和技术细节。更多关于如何通过CloudStack UI安装和配置主存储的信息，请参阅高级安装向导。"
+
+# 4c9b91f3c5dd4d8a83a8c2706ac95f41
+#: ../../storage.rst:189
+msgid ""
+"`“About Secondary Storage” "
+"<http://docs.cloudstack.apache.org/en/latest/concepts.html#about-secondary-"
+"storage>`_"
+msgstr "`“关于辅助存储” <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-secondary-storage>`_。"
+
+# 6ca82acb4184482298cdd589b41fdd16
+#: ../../storage.rst:193
+msgid "Working With Volumes"
+msgstr "使用磁盘卷"
+
+# d8b653a972c54421a4405a011c4ca3e7
+#: ../../storage.rst:195
+msgid ""
+"A volume provides storage to a guest VM. The volume can provide for a root "
+"disk or an additional data disk. CloudStack supports additional volumes for "
+"guest VMs."
+msgstr "卷为来宾虚机提供存储。卷可以作为root分区或附加数据磁盘。CloudStack支持为来宾虚机添加卷。"
+
+# 2197b194989d434ca7e999eb0f6cfaa9
+#: ../../storage.rst:199
+msgid ""
+"Volumes are created for a specific hypervisor type. A volume that has been "
+"attached to guest using one hypervisor type (e.g, XenServer) may not be "
+"attached to a guest that is using another hypervisor type, for "
+"example:vSphere, KVM. This is because the different hypervisors use "
+"different disk image formats."
+msgstr "不同的hypervisor创建的磁盘卷有所不同。当磁盘卷被附加到一种hypervisor的虚拟机(如：xenserver)，就不能再被附加到其他类型的hypervisor,如：vmware、kvm的虚拟机中。因为它们所用的磁盘分区模式不同。"
+
+# 6d23b58657fd41c2aba08ac7ae7eaabe
+#: ../../storage.rst:205
+msgid ""
+"CloudStack defines a volume as a unit of storage available to a guest VM. "
+"Volumes are either root disks or data disks. The root disk has \"/\" in the "
+"file system and is usually the boot device. Data disks provide for "
+"additional storage, for example: \"/opt\" or \"D:\". Every guest VM has a "
+"root disk, and VMs can also optionally have a data disk. End users can mount"
+" multiple data disks to guest VMs. Users choose data disks from the disk "
+"offerings created by administrators. The user can create a template from a "
+"volume as well; this is the standard procedure for private template "
+"creation. Volumes are hypervisor-specific: a volume from one hypervisor type"
+" may not be used on a guest of another hypervisor type."
+msgstr "CloudStack定义一个卷作为来宾虚机的一个有效的存储单元。卷可能是root磁盘或者数据磁盘。root磁盘在文件系统中有 \"/\" 并且通常用于启动设备。数据磁盘提供额外的存储，比如：\"/opt\"或者\"D:\"。每个来宾VM都有一个root磁盘，VMs可能也还有数据磁盘。终端用可以给来宾VMs挂在多个数据磁盘。用户通过管理员创建的磁盘方案来选择数据磁盘。用户同样可以在卷上创建模板；这是标准私有模板的创建流程。针对不同的hypervisor卷也不同：一个hypervisor类型上的卷不能用于其它的hypervisor类型上的来宾虚机。"
+
+# 0dfd84618eba4890bd79fdde4a5681c2
+#: ../../storage.rst:217
+msgid ""
+"CloudStack supports attaching up to 13 data disks to a VM on XenServer "
+"hypervisor versions 6.0 and above. For the VMs on other hypervisor types, "
+"the data disk limit is 6."
+msgstr "CloudStack支持给XenServer 6.0和以上版本的VM最多附加13个数据磁盘。其它hypervisor类型上的VMs，最多附加6个数据磁盘。"
+
+# f423c15d3d884dd295629f532792322b
+#: ../../storage.rst:223
+msgid "Creating a New Volume"
+msgstr "创建新卷"
+
+# 288ba1fb3a644f05a3cd4b08e05b1524
+#: ../../storage.rst:225
+msgid ""
+"You can add more data disk volumes to a guest VM at any time, up to the "
+"limits of your storage capacity. Both CloudStack administrators and users "
+"can add volumes to VM instances. When you create a new volume, it is stored "
+"as an entity in CloudStack, but the actual storage resources are not "
+"allocated on the physical storage device until you attach the volume. This "
+"optimization allows the CloudStack to provision the volume nearest to the "
+"guest that will use it when the first attachment is made."
+msgstr "你可以在符合你存储能力的情况下随时向来宾虚拟机添加多个数据卷。CloudStack的管理员和普通用户都可以向虚拟机实例中添加卷。当你创建了一个新卷，他以一个实体的形式存在于CloudStack中，但是在你将其附加到实例中之前他并不会被分配实际的物理空间。这个优化项允许CloudStack提供最接近来宾虚机的卷，并在第一个附加至虚机的时候使用它。"
+
+# 09420f12f6d84b9ebe5882b8a922b802
+#: ../../storage.rst:235
+msgid "Using Local Storage for Data Volumes"
+msgstr "使用本地存储作为数据卷"
+
+# 87d84c3ad80f4c65ae01116db8e49f5b
+#: ../../storage.rst:237
+msgid ""
+"You can create data volumes on local storage (supported with XenServer, KVM,"
+" and VMware). The data volume is placed on the same host as the VM instance "
+"that is attached to the data volume. These local data volumes can be "
+"attached to virtual machines, detached, re-attached, and deleted just as "
+"with the other types of data volume."
+msgstr "您可以将数据盘创建在本地存储上(XenServer、KVM和VMware支持)。数据盘会存放在和所挂载的虚机相同的主机上。这些本地数据盘可以象其它类型的数据盘一样挂载到虚机、卸载、再挂载和删除。"
+
+# 2092c3e84a0040c88df79f6600d12b26
+#: ../../storage.rst:243
+msgid ""
+"Local storage is ideal for scenarios where persistence of data volumes and "
+"HA is not required. Some of the benefits include reduced disk I/O latency "
+"and cost reduction from using inexpensive local disks."
+msgstr "在不需要持久化数据卷和HA的情况下，本地存储是个理想的选择。其优点包括降低磁盘I/O延迟、使用廉价的本地磁盘来降低费用等。"
+
+# 24091baabed046c79bbde0f55cc59de6
+#: ../../storage.rst:247
+msgid ""
+"In order for local volumes to be used, the feature must be enabled for the "
+"zone."
+msgstr "为了能使用本地磁盘，区域中必须启用该功能。"
+
+# a3fc0fa189a444759468f8645397fc0a
+#: ../../storage.rst:250
+msgid ""
+"You can create a data disk offering for local storage. When a user creates a"
+" new VM, they can select this disk offering in order to cause the data disk "
+"volume to be placed in local storage."
+msgstr "您可以为本地存储创建一个数据盘方案。当创建新虚机时，用户就能够选择该磁盘方案使数据盘存放到本地存储上。"
+
+# 2884a62219544ddea52e40fbabdfc590
+#: ../../storage.rst:254
+msgid ""
+"You can not migrate a VM that has a volume in local storage to a different "
+"host, nor migrate the volume itself away to a different host. If you want to"
+" put a host into maintenance mode, you must first stop any VMs with local "
+"data volumes on that host."
+msgstr "你不能将使用了本地存储作为磁盘的虚机迁移到别的主机，也不能迁移磁盘本身到别的主机。若要将主机置于维护模式，您必须先将该主机上所有拥有本地数据卷的虚机关机。"
+
+# 427238ca555946cc8792695ca92136df
+#: ../../storage.rst:261
+msgid "To Create a New Volume"
+msgstr "创建新卷"
+
+# 70f2f0de47b04a1cbb185fe77792e139
+# 629422b536114a33be189acc56c6cc01
+# 541ad7fafe48443d97a67692a359748c
+# b61f2bef29ea454bb44952aebc53c22c
+# 0e5cea32ef9848a0a96a9ede62313c86
+# 8e3b1d8db33d44fabb0894f24d17d358
+# e35965b604404bef9f199b32675ad907
+#: ../../storage.rst:263 ../../storage.rst:357 ../../storage.rst:390
+#: ../../storage.rst:456 ../../storage.rst:477 ../../storage.rst:506
+#: ../../storage.rst:562
+msgid "Log in to the CloudStack UI as a user or admin."
+msgstr "使用用户或管理员登录到CloudStack用户界面。"
+
+# 146d31151f5e442c8b76e9ef512eac29
+# 11db8955c3494f43b8d2e1bc13a914df
+# 54c24ff429df4622aa1ce17ff0817663
+# f9babc8c9c9941049be79d67a3c60c82
+#: ../../storage.rst:265 ../../storage.rst:312 ../../storage.rst:564
+#: ../../storage.rst:664
+msgid "In the left navigation bar, click Storage."
+msgstr "在左侧导航栏点击存储。"
+
+# 9df84607b2a94838bb6739342d1e0bd7
+# 1f30687ee1374b74bb647174e701cc9b
+# 47fcd7e70cc34717b426f9bf08a626c8
+#: ../../storage.rst:267 ../../storage.rst:361 ../../storage.rst:566
+msgid "In Select View, choose Volumes."
+msgstr "在选择视图中选择卷。"
+
+# d9affc0389314e7cadbe9e0340e6bddd
+#: ../../storage.rst:269
+msgid ""
+"To create a new volume, click Add Volume, provide the following details, and"
+" click OK."
+msgstr "点击添加卷来创建一个新卷，填写以下信息后点击确定。"
+
+# 8aa967b67394416b9971e9986853fc0e
+#: ../../storage.rst:272
+msgid "Name. Give the volume a unique name so you can find it later."
+msgstr "名字。给卷取个唯一的名字以便于你以后找到它。"
+
+# b95f18a10ac946d8bb6e4424522125a5
+#: ../../storage.rst:274
+msgid ""
+"Availability Zone. Where do you want the storage to reside? This should be "
+"close to the VM that will use the volume."
+msgstr "可用的资源域。你想让这个存储在哪个地方有效？这个应该接近要是用这个卷的VM。（就是说你要 在单个资源域内使用这个存储就选择单个资源域，如果此存储要在多个资源与内共享你就选所有资源域）"
+
+# 55b275ed6b1b4c7e965e8d9c3fc64d99
+#: ../../storage.rst:277
+msgid "Disk Offering. Choose the characteristics of the storage."
+msgstr "磁盘方案。选择存储特性。"
+
+# 75cbb5f7984642d8a86bb71c3f274c52
+#: ../../storage.rst:279
+msgid ""
+"The new volume appears in the list of volumes with the state “Allocated.” "
+"The volume data is stored in CloudStack, but the volume is not yet ready for"
+" use"
+msgstr "新建的存储会在卷列表中显示为“已分配”状态。卷数据已经存储到CloudStack了，但是该卷还不能被使用。"
+
+# 97a7e13d891c4ab78df0cd8ebcafdfc7
+#: ../../storage.rst:283
+msgid "To start using the volume, continue to Attaching a Volume"
+msgstr "通过附加卷来开始使用这个卷。"
+
+# 890dc04ff24f497186a44bb7d537412d
+#: ../../storage.rst:287
+msgid "Uploading an Existing Volume to a Virtual Machine"
+msgstr "上传一个已存在的卷给虚拟机"
+
+# 17f14f4d6eec4e609b6e183abaa18556
+#: ../../storage.rst:289
+msgid ""
+"Existing data can be made accessible to a virtual machine. This is called "
+"uploading a volume to the VM. For example, this is useful to upload data "
+"from a local file system and attach it to a VM. Root administrators, domain "
+"administrators, and end users can all upload existing volumes to VMs."
+msgstr "已存在的数据现在可以被虚拟机存取。这个被称为上传一个卷到VM。例如，这对于从本地数据系统上传数据并将数据附加到VM是非常有用的。Root管理员、域管理员和终端用户都可以给VMs上传已存在的卷。"
+
+# f18a289b1dae403cb4a540ec6280499b
+#: ../../storage.rst:295
+msgid ""
+"The upload is performed using HTTP. The uploaded volume is placed in the "
+"zone's secondary storage"
+msgstr "使用HTTP上传。上传的卷被存储在区域中的辅助存储中。"
+
+# e22b07fc396b4455bf886c103b353298
+#: ../../storage.rst:298
+msgid ""
+"You cannot upload a volume if the preconfigured volume limit has already "
+"been reached. The default limit for the cloud is set in the global "
+"configuration parameter max.account.volumes, but administrators can also set"
+" per-domain limits that are different from the global default. See Setting "
+"Usage Limits"
+msgstr "如果预配置的卷已经达到了上限的话，那么你就不能上传卷了。默认的限制在全局配置参数max.account.volumes中设置，但是管理员同样可以为每个用户域设置不同于全局默认的上限值。请参阅设置使用限制。"
+
+# e8b13fa3aadd48cca116ddff3d8ac16a
+#: ../../storage.rst:304
+msgid "To upload a volume:"
+msgstr "要上传一个卷："
+
+# 2032475f0e514f0d87b48fde37cfda03
+#: ../../storage.rst:306
+msgid ""
+"(Optional) Create an MD5 hash (checksum) of the disk image file that you are"
+" going to upload. After uploading the data disk, CloudStack will use this "
+"value to verify that no data corruption has occurred."
+msgstr "(可选项)为将要上传的磁盘镜像文件创建一个MD5哈希(校验)。再上传数据磁盘之后，CloudStack将使用这个校验值来检查这个磁盘文件再上传过程中没有出错。"
+
+# 0fc87857d60e4b6e8d2d80130b6dd64d
+#: ../../storage.rst:310
+msgid "Log in to the CloudStack UI as an administrator or user"
+msgstr "用管理员或用户账号登录CloudStack UI"
+
+# cfa804b4dc5e4b539613e1693f19c041
+#: ../../storage.rst:314
+msgid "Click Upload Volume."
+msgstr "点击上传卷。"
+
+# b664bc425cd54ca4917358c8830843e7
+#: ../../storage.rst:316
+msgid "Provide the following:"
+msgstr "填写以下内容："
+
+# 33a6b2a32f3646e98a44862cba5bea26
+#: ../../storage.rst:318
+msgid ""
+"Name and Description. Any desired name and a brief description that can be "
+"shown in the UI."
+msgstr "名称和描述。你想要的任何名称和一个简洁的描述，这些都会显示在UI中。"
+
+# 1c773983c9a14bda81f657b9831390d5
+#: ../../storage.rst:321
+msgid ""
+"Availability Zone. Choose the zone where you want to store the volume. VMs "
+"running on hosts in this zone can attach the volume."
+msgstr "可用的区域：选择你想存储卷的区域。运行在该区域中的主机上的VMs都可以附加这个卷。"
+
+# d0263e16ccf649a88f3265f9cbd34b80
+#: ../../storage.rst:324
+msgid ""
+"Format. Choose one of the following to indicate the disk image format of the"
+" volume."
+msgstr "格式。在下面所指出的卷的磁盘镜像格式中选择一种。"
+
+# 9e62f8681cf6466c87525f623ab74761
+#: ../../storage.rst:328
+msgid "Hypervisor"
+msgstr "Hypervisor"
+
+# 18fa4b974ece4a8fae34fccd9062dc6a
+#: ../../storage.rst:328
+msgid "Disk Image Format"
+msgstr "磁盘镜像格式"
+
+# fd430608386e4e7db755bcbf9a932e8a
+#: ../../storage.rst:330
+msgid "XenServer"
+msgstr "XenServer"
+
+# 6e5d75ea06c7464cb4ec871161a4a108
+#: ../../storage.rst:331
+msgid "VMware"
+msgstr "VMware"
+
+# 01efef53521d4f8189c939afdd9c1cbb
+#: ../../storage.rst:331
+msgid "OVA"
+msgstr "OVA"
+
+# 9e300c5607d34ce6837b1817e414992a
+#: ../../storage.rst:335
+msgid ""
+"URL. The secure HTTP or HTTPS URL that CloudStack can use to access your "
+"disk. The type of file at the URL must match the value chosen in Format. For"
+" example, if Format is VHD, the URL might look like the following:"
+msgstr "URL。CloudStack用来访问你的磁盘的安全HTTP或HTTPS URL。URL对应的文件种类必须符合在格式中选择的。例如，格式为VHD，则URL必须像下面的："
+
+# 82d85bc5e5704af5a3256a92d5c02114
+#: ../../storage.rst:340
+msgid "``http://yourFileServerIP/userdata/myDataDisk.vhd``"
+msgstr "``http://yourFileServerIP/userdata/myDataDisk.vhd``"
+
+# 2a1e40703cff43efba2d4349b3a16219
+#: ../../storage.rst:342
+msgid "MD5 checksum. (Optional) Use the hash that you created in step 1."
+msgstr "MD5校验。(可选项)使用在步骤1中创建的哈希。"
+
+# c13069ba6499470eb80792d35b8177e5
+#: ../../storage.rst:344
+msgid ""
+"Wait until the status of the volume shows that the upload is complete. Click"
+" Instances - Volumes, find the name you specified in step 5, and make sure "
+"the status is Uploaded."
+msgstr "等到卷的上传显示完成。点击实例-卷，找到你在步骤5中指定的名称，单后确保状态是已上传。"
+
+# 0fd449f8d801478d84a4b2700da5e8b6
+#: ../../storage.rst:350
+msgid "Attaching a Volume"
+msgstr "附加一个卷"
+
+# da2f32e627974c378217daaed2a05282
+#: ../../storage.rst:352
+msgid ""
+"You can attach a volume to a guest VM to provide extra disk storage. Attach "
+"a volume when you first create a new volume, when you are moving an existing"
+" volume from one VM to another, or after you have migrated a volume from one"
+" storage pool to another."
+msgstr "你可以通过附加一个卷来提供虚拟机的额外磁盘存储。当你第一次创建新卷，或移动已存在的卷到另一台虚拟机，或实在从另一个存储池迁移过来一个卷的时候你才可以附加一个卷。"
+
+# e98f959945e047bc950d507b756c28e7
+#: ../../storage.rst:359
+msgid "In the left navigation, click Storage."
+msgstr "在左侧导航栏点击存储。"
+
+# 4334745af8f24f039eba4f0736befe7f
+#: ../../storage.rst:363
+msgid ""
+"Click the volume name in the Volumes list, then click the Attach Disk button"
+" |AttachDiskButton.png|"
+msgstr "在卷列表中点击卷的名称，然后点击附加磁盘按钮 |AttachDiskButton.png|"
+
+# 0840d7b567f84dbcbf9820547c2e68b2
+#: ../../storage.rst:366
+msgid ""
+"In the Instance popup, choose the VM to which you want to attach the volume."
+" You will only see instances to which you are allowed to attach volumes; for"
+" example, a user will see only instances created by that user, but the "
+"administrator will have more choices."
+msgstr "在弹出的实例界面，选择你打算附加卷的那台虚拟机。你只能看到允许你附加卷的实例；比如，普通用户只能看到他自己创建的实例，而管理员将会有更多的选择。"
+
+# 6e680f84bdb84267a7d2d60e4e7fcdf9
+#: ../../storage.rst:371
+msgid ""
+"When the volume has been attached, you should be able to see it by clicking "
+"Instances, the instance name, and View Volumes."
+msgstr "当卷被附加之后，你通过点击实例看到实例名和该实例所附加的卷。"
+
+# dc8f48c99c24477fa1924ef7a1fb28dc
+#: ../../storage.rst:376
+msgid "Detaching and Moving Volumes"
+msgstr "卸载和移动卷"
+
+# 988a57d9e81b49e6be5b37db8f4970c2
+#: ../../storage.rst:379
+msgid ""
+"This procedure is different from moving volumes from one storage pool to "
+"another as described in `“VM Storage Migration” <#vm-storage-migration>`_."
+msgstr "这个过程不同于从一个存储池移动卷到其他的池。这些内容在 `“VM存储迁移” <#vm-storage-migration>`_中有描述。"
+
+# 87a675231744495a92d09e12337edda0
+#: ../../storage.rst:383
+msgid ""
+"A volume can be detached from a guest VM and attached to another guest. Both"
+" CloudStack administrators and users can detach volumes from VMs and move "
+"them to other VMs."
+msgstr "卷可以从来宾虚机上卸载再附加到其他来宾虚机上。CloudStack管理员和用户都能从VMs上卸载卷再给其他VMs附加上。"
+
+# f3a14cfb3fe242fd95952025a2f91323
+#: ../../storage.rst:387
+msgid ""
+"If the two VMs are in different clusters, and the volume is large, it may "
+"take several minutes for the volume to be moved to the new VM."
+msgstr "如果两个VMs存在于不同的群集中，并且卷很大，那么卷移动至新的VM上可能要耗费比较长的时间。"
+
+# 8c279d5d59154e34b12465e6c1b2088a
+#: ../../storage.rst:392
+msgid ""
+"In the left navigation bar, click Storage, and choose Volumes in Select "
+"View. Alternatively, if you know which VM the volume is attached to, you can"
+" click Instances, click the VM name, and click View Volumes."
+msgstr "在左侧的导航栏，点击存储，在选择视图中选择卷。或者，如果你知道卷要附加给哪个VM的话，你可以点击实例，再点击VM名称，然后点击查看卷。"
+
+# 02ba88b018e140248a056d426fd7c9ea
+#: ../../storage.rst:397
+msgid ""
+"Click the name of the volume you want to detach, then click the Detach Disk "
+"button. |DetachDiskButton.png|"
+msgstr "点击你想卸载卷的名字，然后点击卸载磁盘按钮。 |DetachDiskButton.png|"
+
+# 2ef3b0f777434eb58770702236698b0d
+#: ../../storage.rst:400
+msgid ""
+"To move the volume to another VM, follow the steps in `“Attaching a Volume” "
+"<#attaching-a-volume>`_."
+msgstr "要移动卷至其他VM，按照`“附加卷” <#attaching-a-volume>`_中的步骤。"
+
+# 7bce94ec5cda4cfd9031d62fa230127d
+#: ../../storage.rst:405
+msgid "VM Storage Migration"
+msgstr "VM存储迁移"
+
+# 1bc602fbceb14e5ab29eb5e9189ae80d
+#: ../../storage.rst:407
+msgid "Supported in XenServer, KVM, and VMware."
+msgstr "支持XenServer、KVM和VMware。"
+
+# 8183ae7d15c748109dabfa42d80894c4
+#: ../../storage.rst:410
+msgid ""
+"This procedure is different from moving disk volumes from one VM to another "
+"as described in `“Detaching and Moving Volumes” <#detaching-and-moving-"
+"volumes>`_."
+msgstr "这个过程不同于从一个虚拟机移动磁盘卷到另外的虚拟机。这些内容在 \"查看挂载和移动卷\" <#detaching-and-moving-volumes>`_中有描述。"
+
+# 1124cbad549d456f858d2dd00e5689b4
+#: ../../storage.rst:414
+msgid ""
+"You can migrate a virtual machine’s root disk volume or any additional data "
+"disk volume from one storage pool to another in the same zone."
+msgstr "你可以从同一区域中的一个存储池迁移虚机的root磁盘卷或任何其他的数据磁盘卷到其他的池"
+
+# cb9592a82bf84a7c8393f53e9e18ef77
+#: ../../storage.rst:417
+msgid ""
+"You can use the storage migration feature to achieve some commonly desired "
+"administration goals, such as balancing the load on storage pools and "
+"increasing the reliability of virtual machines by moving them away from any "
+"storage pool that is experiencing issues."
+msgstr "你可以使用存储迁移功能完成一些常用的管理目标。如将它们从有问题的存储池中迁移出去以平衡存储池的负载和增加虚拟机的可靠性。"
+
+# a2bcc01e8bd8426dba63dd8846123778
+#: ../../storage.rst:422
+msgid ""
+"On XenServer and VMware, live migration of VM storage is enabled through "
+"CloudStack support for XenMotion and vMotion. Live storage migration allows "
+"VMs to be moved from one host to another, where the VMs are not located on "
+"storage shared between the two hosts. It provides the option to live migrate"
+" a VM’s disks along with the VM itself. It is possible to migrate a VM from "
+"one XenServer resource pool / VMware cluster to another, or to migrate a VM "
+"whose disks are on local storage, or even to migrate a VM’s disks from one "
+"storage repository to another, all while the VM is running."
+msgstr "在XenServer和VMware上，由于CloudStack支持XenMotion和vMotion，VM存储的在线迁移是启用的。在线存储迁移允许没有在共享存储上的VMs从一台主机迁移到另一台主机上。它提供选项让VM的磁盘与VM本身一起在线迁移。它让XenServer资源池之间/VMware群集之间迁移VM，或者在本地存储运行的VM，甚至是存储库之间迁移VM的磁盘成为可能，而且迁移同时VM是正在运行的。"
+
+# ebbd4f4ab1654020b6c6bd65f6c8bf34
+#: ../../storage.rst:433
+msgid ""
+"Because of a limitation in VMware, live migration of storage for a VM is "
+"allowed only if the source and target storage pool are accessible to the "
+"source host; that is, the host where the VM is running when the live "
+"migration operation is requested."
+msgstr "由于VMware中的限制，仅当源和目标存储池都能被源主机访问时才允许VM存储的在线迁移；也就是说，当需要在线迁移操作时，源主机是运行VM的主机。"
+
+# ebbe88108b474e6fbcb0bf7db34d5473
+#: ../../storage.rst:440
+msgid "Migrating a Data Volume to a New Storage Pool"
+msgstr "将数据卷迁移到新的存储池"
+
+# c5d71980858c4c34a0fa4c90024e9f49
+#: ../../storage.rst:442
+msgid "There are two situations when you might want to migrate a disk:"
+msgstr "当你想迁移磁盘的时候可能有两种情况："
+
+# 787fcb424e3a474794856b6e4c36294a
+#: ../../storage.rst:444
+msgid ""
+"Move the disk to new storage, but leave it attached to the same running VM."
+msgstr "将磁盘移动到新的存储，但是还将其附加在原来正在运行的VM上。"
+
+# d3a83f9da3984d7285731f35b1577f61
+#: ../../storage.rst:447
+msgid ""
+"Detach the disk from its current VM, move it to new storage, and attach it "
+"to a new VM."
+msgstr "从当前VM上卸载磁盘，然后将其移动至新的存储，再将其附加至新的VM。"
+
+# 47132cdecc7e40bdbe0b73b197292474
+#: ../../storage.rst:452
+msgid "Migrating Storage For a Running VM"
+msgstr "为正在运行的VM迁移存储"
+
+# 49fb8bbee6ed48a0a77ef96befb12bde
+#: ../../storage.rst:454
+msgid "(Supported on XenServer and VMware)"
+msgstr "(支持XenServer和VMware)"
+
+# 22e57c1b2aa74b2681ccf49f19103618
+#: ../../storage.rst:458
+msgid ""
+"In the left navigation bar, click Instances, click the VM name, and click "
+"View Volumes."
+msgstr "在左侧的导航栏，点击实例，再点击VM名，接着点击查看卷。"
+
+# afc084613de9415cb23e3125751a0dbe
+#: ../../storage.rst:461
+msgid "Click the volume you want to migrate."
+msgstr "点击你想迁移的卷。"
+
+# 162037fc56d042c085a994af770ebe2c
+# 35b4f135a003412db306d5c378f6f2b8
+#: ../../storage.rst:463 ../../storage.rst:479
+msgid ""
+"Detach the disk from the VM. See `“Detaching and Moving Volumes” "
+"<#detaching-and-moving-volumes>`_ but skip the “reattach” step at the end. "
+"You will do that after migrating to new storage."
+msgstr "从VM卸载磁盘。请参阅 `“卸载和移动卷” <#detaching-and-moving-volumes>`_ 但是跳过最后的\"重新附加\"步骤。你会在迁移过后在新的存储上做这一步。"
+
+# bc76fcc2fe05464dbd69894e5d2d4746
+# d3951fd18db542b9b7fa617306a1f07c
+#: ../../storage.rst:467 ../../storage.rst:483
+msgid ""
+"Click the Migrate Volume button |Migrateinstance.png| and choose the "
+"destination from the dropdown list."
+msgstr "点击迁移卷按钮 |Migrateinstance.png| ，然后从下拉列表里面选择目标位置。"
+
+# 98ce5d9b63084686a8b2a0c0ad1bf658
+#: ../../storage.rst:470
+msgid ""
+"Watch for the volume status to change to Migrating, then back to Ready."
+msgstr "这期间，卷的状态会变成正在迁移，然后又变回已就绪。"
+
+# f5d81aecca72450bac7269a86bf20b26
+#: ../../storage.rst:475
+msgid "Migrating Storage and Attaching to a Different VM"
+msgstr "迁移存储和附加到不同的VM"
+
+# 614797ab3f9a44f08c275e1f6ed61f13
+#: ../../storage.rst:486
+msgid ""
+"Watch for the volume status to change to Migrating, then back to Ready. You "
+"can find the volume by clicking Storage in the left navigation bar. Make "
+"sure that Volumes is displayed at the top of the window, in the Select View "
+"dropdown."
+msgstr "观察卷的状态会变成正在迁移，然后又变回已就绪。你可以点击左侧导航条中的存储找到卷。在选择查看的下拉列表中，确保卷显示在窗口的顶部。"
+
+# 5dafaedc6390428eb94978091d3808ad
+#: ../../storage.rst:491
+msgid ""
+"Attach the volume to any desired VM running in the same cluster as the new "
+"storage server. See `“Attaching a Volume” <#attaching-a-volume>`_"
+msgstr "在新的存储服务器中给运行在同一群集中的任何想要的VM附加卷。请参阅 `“附加卷” <#attaching-a-volume>`_。"
+
+# 2b29f819fd9f4a61b39cd73dbc205e65
+#: ../../storage.rst:497
+msgid "Migrating a VM Root Volume to a New Storage Pool"
+msgstr "迁移VM的Root卷到新的存储池"
+
+# 2fdc3aca153f473fac5ef5e7ba874b2a
+#: ../../storage.rst:499
+msgid ""
+"(XenServer, VMware) You can live migrate a VM's root disk from one storage "
+"pool to another, without stopping the VM first."
+msgstr "(XenServer、VMware)你可以在停止VM的情况下，使用在线迁移将VM的root磁盘从一个存储池移动到另外一个。"
+
+# f6a2cc4f4e2c40ce85564e77487a6051
+#: ../../storage.rst:502
+msgid ""
+"(KVM) When migrating the root disk volume, the VM must first be stopped, and"
+" users can not access the VM. After migration is complete, the VM can be "
+"restarted."
+msgstr "(KVM)当前已root磁盘卷的时候，VM必须关机，这时用户不能访问VM。在迁移完成之后，VM就能重启了。"
+
+# 99e0360f9cff4f3595658d757416655e
+#: ../../storage.rst:508
+msgid "In the left navigation bar, click Instances, and click the VM name."
+msgstr "在左侧的导航栏里，点击实例，然后点击VM名。"
+
+# 40a52b70ece74eeb83347bcca88c58c0
+#: ../../storage.rst:510
+msgid "(KVM only) Stop the VM."
+msgstr "(仅限于KVM)停止VM。"
+
+# 918eb301d15e4e369656d3ab9c3eb850
+#: ../../storage.rst:512
+msgid ""
+"Click the Migrate button |Migrateinstance.png| and choose the destination "
+"from the dropdown list."
+msgstr "点击迁移按钮 |Migrateinstance.png| ，然后从下拉列表中选择目标位置。"
+
+# d43200e809304acdad782782547fe7b0
+#: ../../storage.rst:516
+msgid ""
+"If the VM's storage has to be migrated along with the VM, this will be noted"
+" in the host list. CloudStack will take care of the storage migration for "
+"you."
+msgstr "如果VM的存储与VM必须一起被迁移，这点会在主机列表中标注。CloudStack会为你自动的进行存储迁移。"
+
+# 7e0343377d674714bb987eed30d9687e
+#: ../../storage.rst:520
+msgid ""
+"Watch for the volume status to change to Migrating, then back to Running (or"
+" Stopped, in the case of KVM). This can take some time."
+msgstr "观察卷的状态会变成迁移中，然后变回运行中(或者停止，在KVM中)。这过程会持续一段时间。"
+
+# cf995ac6b00e4ede877a0a869d35d0c3
+#: ../../storage.rst:523
+msgid "(KVM only) Restart the VM."
+msgstr "(仅限于KVM)重启VM。"
+
+# fe6a0aed97e24cd7a80e1e10b113296f
+#: ../../storage.rst:527
+msgid "Resizing Volumes"
+msgstr "重新规划卷"
+
+# d5de1d251de94750aef7188031910714
+#: ../../storage.rst:529
+msgid ""
+"CloudStack provides the ability to resize data disks; CloudStack controls "
+"volume size by using disk offerings. This provides CloudStack administrators"
+" with the flexibility to choose how much space they want to make available "
+"to the end users. Volumes within the disk offerings with the same storage "
+"tag can be resized. For example, if you only want to offer 10, 50, and 100 "
+"GB offerings, the allowed resize should stay within those limits. That "
+"implies if you define a 10 GB, a 50 GB and a 100 GB disk offerings, a user "
+"can upgrade from 10 GB to 50 GB, or 50 GB to 100 GB. If you create a custom-"
+"sized disk offering, then you have the option to resize the volume by "
+"specifying a new, larger size."
+msgstr "CloudStack提供了调整数据盘大小的功能；CloudStack借助磁盘方案控制卷大小。这样提供了CloudStack管理员可以灵活地选择他们想要给终端用户多少可用空间。使用相同存储标签的磁盘方案中的卷可以重新划分。比如，如果你只想提供 10,50和100GB的方案，重新划分允许的极限就不会超过这些。也就是说，如果你定义了10GB，50GB和100GB的磁盘方案，用户可以从10GB升级到50GB，或者从50GB升级到100GB。如果你创建了自定义大小的磁盘方案，那么你可以重新规划卷的大小为更大的值。"
+
+# 6111e137df7f47a99f428cab9e407bda
+#: ../../storage.rst:540
+msgid ""
+"Additionally, using the resizeVolume API, a data volume can be moved from a "
+"static disk offering to a custom disk offering with the size specified. This"
+" functionality allows those who might be billing by certain volume sizes or "
+"disk offerings to stick to that model, while providing the flexibility to "
+"migrate to whatever custom size necessary."
+msgstr "另外，使用 resizeVolume API，数据卷可以从一个静态磁盘方案移动到指定大小的自定义磁盘方案。此功能允对特定容量或磁盘方案进行收费，同时可以灵活地更改磁盘大小。"
+
+# c25a67ebb3344e2c951583bec9826b9e
+#: ../../storage.rst:546
+msgid ""
+"This feature is supported on KVM, XenServer, and VMware hosts. However, "
+"shrinking volumes is not supported on VMware hosts."
+msgstr "KVM, XenServer和VMware主机支持这个功能。但是VMware主机不支持卷的收缩。"
+
+# f3d3d1c66a9a46a49a97000ce2d104ee
+#: ../../storage.rst:549
+msgid "Before you try to resize a volume, consider the following:"
+msgstr "在你试图重新规划卷大小之前，请考虑以下几点："
+
+# 1c0434424baf4f79a95622559c9119b2
+#: ../../storage.rst:551
+msgid "The VMs associated with the volume are stopped."
+msgstr "与卷关联的VMs是停止状态。"
+
+# bb545d0a9cf34f5e864a5b016d15775d
+#: ../../storage.rst:553
+msgid "The data disks associated with the volume are removed."
+msgstr "与卷关联的数据磁盘已经移除了。"
+
+# 157e4971d3784646a5df1fc2c27026fa
+#: ../../storage.rst:555
+msgid ""
+"When a volume is shrunk, the disk associated with it is simply truncated, "
+"and doing so would put its content at risk of data loss. Therefore, resize "
+"any partitions or file systems before you shrink a data disk so that all the"
+" data is moved off from that disk."
+msgstr "当卷缩小的时候，上面的磁盘会被截断，这么做的话可能会丢失数据。因此，在缩小数据磁盘之前，重新规划任何分区或文件系统以便数据迁移出这个磁盘。"
+
+# ea92d28ccffe4acbb40da15110829f69
+#: ../../storage.rst:560
+msgid "To resize a volume:"
+msgstr "要重新规划卷容量："
+
+# 4bcbe35ab7f749c49a97fc0b69386143
+#: ../../storage.rst:568
+msgid ""
+"Select the volume name in the Volumes list, then click the Resize Volume "
+"button |resize-volume-icon.png|"
+msgstr "在卷列表中选择卷名称，然后点击调整卷大小按钮 |resize-volume-icon.png|"
+
+# 7e6057281d384902b45704d88725b3b2
+#: ../../storage.rst:571
+msgid ""
+"In the Resize Volume pop-up, choose desired characteristics for the storage."
+msgstr "在弹出的调整卷大小窗口中，为存储选择想要的方案。"
+
+# 837580ae5e7d422eb6d54ca24b547f32
+#: ../../storage.rst:574
+msgid "|resize-volume.png|"
+msgstr "|resize-volume.png|"
+
+# 2a4fef4505014a8c9cee37ce70dc08a3
+#: ../../storage.rst:576
+msgid "If you select Custom Disk, specify a custom size."
+msgstr "如果你选择自定义磁盘，请指定一个自定义大小。"
+
+# 0f0109182c0345099ae713929c4c1f4d
+#: ../../storage.rst:578
+msgid "Click Shrink OK to confirm that you are reducing the size of a volume."
+msgstr "点击是否确实要缩小卷大小来确认你要缩小的容量。"
+
+# 86a5314fba614528805c75a1ce993c5b
+#: ../../storage.rst:581
+msgid ""
+"This parameter protects against inadvertent shrinking of a disk, which might"
+" lead to the risk of data loss. You must sign off that you know what you are"
+" doing."
+msgstr "此参数避免了不小心的失误造成数据的丢失。你必须知道你在做什么。"
+
+# fa1e5898785847d0acd130136d2b3e4b
+#: ../../storage.rst:585
+msgid "Click OK."
+msgstr "点击确定。"
+
+# 7416d78fc57b4a21a1c5a748c35efa62
+#: ../../storage.rst:589
+msgid "Reset VM to New Root Disk on Reboot"
+msgstr "在VM重启时重设VM的root盘"
+
+# aa266ce7558249a58dc21c85bbe527c1
+#: ../../storage.rst:591
+msgid ""
+"You can specify that you want to discard the root disk and create a new one "
+"whenever a given VM is rebooted. This is useful for secure environments that"
+" need a fresh start on every boot and for desktops that should not retain "
+"state. The IP address of the VM will not change due to this operation."
+msgstr "你可以指定你想要放弃的root磁盘和创建一个新的，并且无论何时在VM重启时都使用新的。每次启动时都是一个全新的VM并且桌面不需要保存它的状态，出于安全环境考虑这非常有用。VM的IP地址在这个操作期间不会改变。"
+
+# f4a034b658174e23b49d8a0dae7faf9d
+#: ../../storage.rst:597
+msgid "**To enable root disk reset on VM reboot:**"
+msgstr "**要启用在VM重启时重置root磁盘：**"
+
+# 0d8e7c9c2b4b461bb00b40c89b19ca07
+#: ../../storage.rst:599
+msgid ""
+"When creating a new service offering, set the parameter isVolatile to True. "
+"VMs created from this service offering will have their disks reset upon "
+"reboot. See `“Creating a New Compute Offering” "
+"<service_offerings.html#creating-a-new-compute-offering>`_."
+msgstr "当创建一个新的服务方案时，设置isVolatile这个参数为True。从这个服务方案创建的VMs一旦重启，它们的磁盘就会重置。请参阅 `“创建新的计算方案” <service_offerings.html#creating-a-new-compute-offering>`_。"
+
+# 80b7517a265a468a91758a97f1049265
+#: ../../storage.rst:606
+msgid "Volume Deletion and Garbage Collection"
+msgstr "卷的删除和回收"
+
+# 97ddeaa6235d4294ace130e1f8fd97c0
+#: ../../storage.rst:608
+msgid ""
+"The deletion of a volume does not delete the snapshots that have been "
+"created from the volume"
+msgstr "删除卷不会删除曾经对卷做的快照"
+
+# 0050f5041dd04b1dbeff8201bd20e44e
+#: ../../storage.rst:611
+msgid ""
+"When a VM is destroyed, data disk volumes that are attached to the VM are "
+"not deleted."
+msgstr "当一个VM被销毁时，附加到该VM的数据磁盘卷不会被删除。"
+
+# f3a035c41fca41908db4d1f0f724f360
+#: ../../storage.rst:614
+msgid ""
+"Volumes are permanently destroyed using a garbage collection process. The "
+"global configuration variables expunge.delay and expunge.interval determine "
+"when the physical deletion of volumes will occur."
+msgstr "使用回收程序后，卷就永久的被销毁了。全局配置变量expunge.delay和expunge.interval决定了何时物理删除卷。"
+
+# e4eb84092e8b4ea9a1a97fecac24acbb
+#: ../../storage.rst:618
+msgid ""
+"`expunge.delay`: determines how old the volume must be before it is "
+"destroyed, in seconds"
+msgstr "`expunge.delay`：决定在卷被销毁之前卷存在多长时间，以秒计算。"
+
+# 7564390647064858ac8aa5f26279afe5
+#: ../../storage.rst:621
+msgid ""
+"`expunge.interval`: determines how often to run the garbage collection check"
+msgstr "`expunge.interval`：决定回收检查运行频率。"
+
+# 000948d93f8f4cdba6f8fbab90adf234
+#: ../../storage.rst:624
+msgid ""
+"Administrators should adjust these values depending on site policies around "
+"data retention."
+msgstr "管理员可以根据站点数据保留策略来调整这些值。"
+
+# a8d6b53bbfe04f9198da340f624d7b85
+#: ../../storage.rst:629
+msgid "Working with Volume Snapshots"
+msgstr "使用卷快照"
+
+# 86801042196e4703adde0a0f8f421cc2
+# ecd40cf685aa497094053129489ffa6d
+#: ../../storage.rst:631 ../../storage.rst:676
+msgid ""
+"(Supported for the following hypervisors: **XenServer**, **VMware vSphere**,"
+" and **KVM**)"
+msgstr "(支持以下hypervisors：**XenServer**, **VMware vSphere** 和 **KVM**)"
+
+# 084599a159574408809d1cfaa15f2160
+#: ../../storage.rst:634
+msgid ""
+"CloudStack supports snapshots of disk volumes. Snapshots are a point-in-time"
+" capture of virtual machine disks. Memory and CPU states are not captured. "
+"If you are using the Oracle VM hypervisor, you can not take snapshots, since"
+" OVM does not support them."
+msgstr "CloudStack支持磁盘卷的快照。快照为虚拟机某一时间点的抓取。内存和CPU状态不会被抓取。如果你使用Oracle VM hypervisor，那么你不能做快照，因为OVM不支持。"
+
+# bd4b18a4d2374e20ae0af95dad8d53e5
+#: ../../storage.rst:639
+msgid ""
+"Snapshots may be taken for volumes, including both root and data disks "
+"(except when the Oracle VM hypervisor is used, which does not support "
+"snapshots). The administrator places a limit on the number of stored "
+"snapshots per user. Users can create new volumes from the snapshot for "
+"recovery of particular files and they can create templates from snapshots to"
+" boot from a restored disk."
+msgstr "卷，包括root和数据磁盘(使用Oracle VM hypervisor除外，因为OVM不支持快照)都可以做快照。管理员可以限制每个用户的快照数量。用户可以通过快照创建新的卷，用来恢复特定的文件，还可以通过快照创建模板来启动恢复的磁盘。"
+
+# 61d7db60070b43a4a6a950e12598da22
+#: ../../storage.rst:646
+msgid ""
+"Users can create snapshots manually or by setting up automatic recurring "
+"snapshot policies. Users can also create disk volumes from snapshots, which "
+"may be attached to a VM like any other disk volume. Snapshots of both root "
+"disks and data disks are supported. However, CloudStack does not currently "
+"support booting a VM from a recovered root disk. A disk recovered from "
+"snapshot of a root disk is treated as a regular data disk; the data on "
+"recovered disk can be accessed by attaching the disk to a VM."
+msgstr "用户可以手动或者设置自动循环快照策略创建快照。用户也可以从快照创建附磁盘卷，并像其他磁盘卷一样附加到虚机上。root和数据磁盘支持快照。但是，CloudStack目前不支持通过恢复的root盘启动VM。从快照恢复的root盘会被认为是数据盘；恢复的磁盘可以附加到VM上以访问上面的数据。"
+
+# 42324227e8644e9dae9c6866285da289
+#: ../../storage.rst:655
+msgid ""
+"A completed snapshot is copied from primary storage to secondary storage, "
+"where it is stored until deleted or purged by newer snapshot."
+msgstr "完整快照慧聪主存储拷贝到附加存储，并会一直存储在里面知道删除或被新的快照覆盖。"
+
+# 6d4012e38675491e950c4095403168d4
+#: ../../storage.rst:660
+msgid "How to Snapshot a Volume"
+msgstr "如何给卷做快照"
+
+# c8a3e39ed65148c1b2db5692449e3ec0
+#: ../../storage.rst:662
+msgid "Log in to the CloudStack UI as a user or administrator."
+msgstr "是用用户或者管理员登录CloudStack。"
+
+# ee26042497e54259b376064aafe9cebf
+#: ../../storage.rst:666
+msgid "In Select View, be sure Volumes is selected."
+msgstr "在选择视图，确认选择的是卷。"
+
+# 2f05b064d8b245a99e010a0f45f944e2
+#: ../../storage.rst:668
+msgid "Click the name of the volume you want to snapshot."
+msgstr "点击你要做快照的卷的名称。"
+
+# b4d7d4eaa5a149f0812cdddc1fd45a61
+#: ../../storage.rst:670
+msgid "Click the Snapshot button. |SnapshotButton.png|"
+msgstr "点击快照按钮。 |SnapshotButton.png|"
+
+# 6daa1fb5225e4efe8672fc86408e7055
+#: ../../storage.rst:674
+msgid "Automatic Snapshot Creation and Retention"
+msgstr "创建和保留自动快照"
+
+# 01044207c30b40148eedee96353f6ad9
+#: ../../storage.rst:679
+msgid ""
+"Users can set up a recurring snapshot policy to automatically create "
+"multiple snapshots of a disk at regular intervals. Snapshots can be created "
+"on an hourly, daily, weekly, or monthly interval. One snapshot policy can be"
+" set up per disk volume. For example, a user can set up a daily snapshot at "
+"02:30."
+msgstr "用户可以设置循环快照策略来自动的为磁盘定期地创建多个快照。快照可以按小时，天，周或者月为周期。每个磁盘卷都可以设置快照策略。比如，用户可以设置每天的02:30做快照。"
+
+# bc81c587ad8b4032b27d61690390e258
+#: ../../storage.rst:685
+msgid ""
+"With each snapshot schedule, users can also specify the number of scheduled "
+"snapshots to be retained. Older snapshots that exceed the retention limit "
+"are automatically deleted. This user-defined limit must be equal to or lower"
+" than the global limit set by the CloudStack administrator. See `“Globally "
+"Configured Limits” <usage.html#globally-configured-limits>`_. The limit "
+"applies only to those snapshots that are taken as part of an automatic "
+"recurring snapshot policy. Additional manual snapshots can be created and "
+"retained."
+msgstr "依靠每个快照计划，用户还可以指定计划快照的保留数量。超出保留期限的老快照会被自动的删除。用户定义的限制必须等于或小于CloudStack管理员设置的全局限制。请参阅 `“全局配置的限制” <usage.html#globally-configured-limits>`_.。限制只能应用给作为自动循环快照策略的一部分的快照。额外的手动快照能被创建和保留。"
+
+# 4d944a9ae89444379355fd0f48bd592a
+#: ../../storage.rst:697
+msgid "Incremental Snapshots and Backup"
+msgstr "增量快照和备份"
+
+# d0114a6db3e54775a44f58bd333b2916
+#: ../../storage.rst:699
+msgid ""
+"Snapshots are created on primary storage where a disk resides. After a "
+"snapshot is created, it is immediately backed up to secondary storage and "
+"removed from primary storage for optimal utilization of space on primary "
+"storage."
+msgstr "创建的快照保存在磁盘所在的主存储。在创建快照之后，它会立即被备份到辅助存储并在主存储上删除以节省主存储的空间。"
+
+# 1c3dce8473ed47388f4d6175b8e34c81
+#: ../../storage.rst:704
+msgid ""
+"CloudStack does incremental backups for some hypervisors. When incremental "
+"backups are supported, every N backup is a full backup."
+msgstr "CloudStack给一些 hypervisors做增量备份。当使用了增量备份，那么每N备份就是一个完全备份。"
+
+# 4559fc5082f543d6b1cdacaa46ed5a23
+#: ../../storage.rst:711
+msgid "Support incremental backup"
+msgstr "支持增量备份"
+
+# 1c981e7b2c7b445a9061e36444287afb
+#: ../../storage.rst:716
+msgid "Volume Status"
+msgstr "卷状态"
+
+# b7db2aabc187479797c7424c5a1bb1f8
+#: ../../storage.rst:718
+msgid ""
+"When a snapshot operation is triggered by means of a recurring snapshot "
+"policy, a snapshot is skipped if a volume has remained inactive since its "
+"last snapshot was taken. A volume is considered to be inactive if it is "
+"either detached or attached to a VM that is not running. CloudStack ensures "
+"that at least one snapshot is taken since the volume last became inactive."
+msgstr "当快照操作是由一个循环快照策略所引发的时候，如果从其上次创建快照后，卷一直处于非活跃状态，快照被跳过。如果卷被分离或附加的虚拟机没有运行，那么它就被认为是非活跃的。CloudStack会确保从卷上一次变得不活跃后，至少创建了一个快照。"
+
+# b5a7b1b8f3fe4e47a40bc594491a0643
+#: ../../storage.rst:725
+msgid ""
+"When a snapshot is taken manually, a snapshot is always created regardless "
+"of whether a volume has been active or not."
+msgstr "当手动创建了快照，不管改卷是不是活跃的，快照会一直被创建。"
+
+# e8778a84f2d142489ea29fa0793066b1
+#: ../../storage.rst:730
+msgid "Snapshot Restore"
+msgstr "快照恢复"
+
+# 4bcf574b0e484b7ebf81324e87069f67
+#: ../../storage.rst:732
+msgid ""
+"There are two paths to restoring snapshots. Users can create a volume from "
+"the snapshot. The volume can then be mounted to a VM and files recovered as "
+"needed. Alternatively, a template may be created from the snapshot of a root"
+" disk. The user can then boot a VM from this template to effect recovery of "
+"the root disk."
+msgstr "有两种方式恢复快照。用户能够从快照中创建一个卷。卷可以随后被挂载到虚拟机上并且文件根据需要被复原。另一种方式是，模板可以从一个root 盘的快照创建。用户能够从这个模板启动虚拟机从而实际上复原root盘。"
+
+# cf46f177e13341079bac27a54806636b
+#: ../../storage.rst:740
+msgid "Snapshot Job Throttling"
+msgstr "快照工作调节"
+
+# 6ba670f617a541788c30476794cde2c6
+#: ../../storage.rst:742
+msgid ""
+"When a snapshot of a virtual machine is requested, the snapshot job runs on "
+"the same host where the VM is running or, in the case of a stopped VM, the "
+"host where it ran last. If many snapshots are requested for VMs on a single "
+"host, this can lead to problems with too many snapshot jobs overwhelming the"
+" resources of the host."
+msgstr "当虚拟机需要快照时，VM所在的主机上就会运行快照工作，或者在VM最后运行的主机上。如果在一台主机上的VMs需要很多快照，那么这会导致太多的快照工作进而占用过多的主机资源。"
+
+# aedc3df480554bd59de19f4c4ba17dff
+#: ../../storage.rst:748
+msgid ""
+"To address this situation, the cloud's root administrator can throttle how "
+"many snapshot jobs are executed simultaneously on the hosts in the cloud by "
+"using the global configuration setting "
+"concurrent.snapshots.threshold.perhost. By using this setting, the "
+"administrator can better ensure that snapshot jobs do not time out and "
+"hypervisor hosts do not experience performance issues due to hosts being "
+"overloaded with too many snapshot requests."
+msgstr "针对这种情况，云端的root管理员可以利用全局配置设置中的concurrent.snapshots.threshold.perhost调节有多少快照工作同时在主机上运行。借助这个设置，当太多快照请求发生时，管理员更好的确认快照工作不会超时并且hypervisor主机不会有性能问题。"
+
+# 9a43b07f0da64addaa4eb478d80b82a2
+#: ../../storage.rst:756
+msgid ""
+"Set concurrent.snapshots.threshold.perhost to a value that represents a best"
+" guess about how many snapshot jobs the hypervisor hosts can execute at one "
+"time, given the current resources of the hosts and the number of VMs running"
+" on the hosts. If a given host has more snapshot requests, the additional "
+"requests are placed in a waiting queue. No new snapshot jobs will start "
+"until the number of currently executing snapshot jobs falls below the "
+"configured limit."
+msgstr "给concurrent.snapshots.threshold.perhost设置一个你结合目前主机资源和在主机上运行的VMs数量的最佳值，这个值代表了在同一时刻有多少快照工作在hypervisor主机上执行。如果一个主机有比较多的快照请求，额外的请求就会被放在等待队列里。在当前执行 的快照工作数量下降至限制值之内，新的快照工作才会开始。"
+
+# 2fd65be78bf841d9911d51c1de67cd86
+#: ../../storage.rst:764
+msgid ""
+"The admin can also set job.expire.minutes to place a maximum on how long a "
+"snapshot request will wait in the queue. If this limit is reached, the "
+"snapshot request fails and returns an error message."
+msgstr "管理员也可以通过job.expire.minutes给快照请求等待队列的长度设置一个最大值。如果达到了这个限制，那么快照请求会失败并且返回一个错误消息。"
+
+# 45b8545120ba486ca2cbee08b18502d3
+#: ../../storage.rst:770
+msgid "VMware Volume Snapshot Performance"
+msgstr "VMware卷快照性能"
+
+# aa81997f26a64d1399b138ae79ae8ab7
+#: ../../storage.rst:772
+msgid ""
+"When you take a snapshot of a data or root volume on VMware, CloudStack uses"
+" an efficient storage technique to improve performance."
+msgstr "当你为VMware中的数据卷或root卷做快照时，CloudStack使用一种高效率的存储技术来提高性能。"
+
+# edf5b2aae9f54e098d3b6627c10fe21d
+#: ../../storage.rst:775
+msgid ""
+"A snapshot is not immediately exported from vCenter to a mounted NFS share "
+"and packaged into an OVA file format. This operation would consume time and "
+"resources. Instead, the original file formats (e.g., VMDK) provided by "
+"vCenter are retained. An OVA file will only be created as needed, on demand."
+" To generate the OVA, CloudStack uses information in a properties file "
+"(\\*.ova.meta) which it stored along with the original snapshot data."
+msgstr "快照不会立即从vCenter导出OVA格式文件到挂载的NFS共享中。这个操作会消耗时间和资源。相反的，由vCenter提供的原始文件格式(比如VMDK)被保留。OVA文件只有在需要的时候被创建。CloudStack使用与原始快照数据存储在一起的属性文件(\\*.ova.meta)中的信息来生成OVA。"
+
+# c2bf4f95ccfe40aea4c948e5145c1e45
+#: ../../storage.rst:784
+msgid ""
+"For upgrading customers: This process applies only to newly created "
+"snapshots after upgrade to CloudStack 4.2. Snapshots that have already been "
+"taken and stored in OVA format will continue to exist in that format, and "
+"will continue to work as expected."
+msgstr "对于旧版本升级的客户：这个过程只适用于在升级到CloudStack 4.2之后新创建的快照。已经做过快照并且使用OVA格式存储的将继续使用已有的格式，并且也能正常工作。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/systemvm.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/systemvm.mo
new file mode 100644
index 0000000..1060a41
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/systemvm.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/systemvm.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/systemvm.po
new file mode 100644
index 0000000..c880c7e
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/systemvm.po
@@ -0,0 +1,955 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:04+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# a1ba7b5ddeaa4674a16ca755b4399374
+#: ../../systemvm.rst:18
+msgid "Working with System Virtual Machines"
+msgstr "使用系统虚拟机"
+
+# 8adf74bd899541a180455ab6582554ec
+#: ../../systemvm.rst:20
+msgid ""
+"CloudStack uses several types of system virtual machines to perform tasks in"
+" the cloud. In general CloudStack manages these system VMs and creates, "
+"starts, and stops them as needed based on scale and immediate needs. "
+"However, the administrator should be aware of them and their roles to assist"
+" in debugging issues."
+msgstr "CloudStack使用几类系统虚拟机来完成云中的任务。总的来说，CloudStack管理这些系统虚拟机，并根据某些范围内或快速需要创建、启动和停止它们。然而，管理员需要意识到他们在调试中的作用。"
+
+# 9309f035653a42c2a2abfdaced6acabe
+#: ../../systemvm.rst:28
+msgid "The System VM Template"
+msgstr "系统VM模板"
+
+# c845974251da4739b29ae9338d9f85f0
+#: ../../systemvm.rst:30
+msgid ""
+"The System VMs come from a single template. The System VM has the following "
+"characteristics:"
+msgstr "系统VM来自于一个单独的模板，系统VM具有以下特性："
+
+# 6ce60c193c5547e38390bda23ad9acff
+#: ../../systemvm.rst:33
+msgid ""
+"Debian 6.0 (\"Squeeze\"), 2.6.32 kernel with the latest security patches "
+"from the Debian security APT repository"
+msgstr "Debian 6.0(“Squeeze”)，2.6.32内核具有最新的来自Debian安全APT存储库的安全补丁"
+
+# 7ba8f1dd850e4472b93271c07b12e27e
+#: ../../systemvm.rst:36
+msgid ""
+"Has a minimal set of packages installed thereby reducing the attack surface"
+msgstr "具有一系列最小化安装的包，可以降低安全攻击风险。"
+
+# 157f5d425def480e9b24095a62b2f059
+#: ../../systemvm.rst:39
+msgid "32-bit for enhanced performance on Xen/VMWare"
+msgstr "基于 Xen/VMWare 的32位增强性能"
+
+# 7a44b4350ff6457cab519a552bd9afca
+#: ../../systemvm.rst:41
+msgid ""
+"pvops kernel with Xen PV drivers, KVM virtio drivers, and VMware tools for "
+"optimum performance on all hypervisors"
+msgstr "包含Xen PV 驱动，KVM virtio 驱动和VMware tools的pvops 内核可以使所有hypervisor得到最佳性能。"
+
+# 3e0764891a5141e2b34368e7bb8aeb84
+#: ../../systemvm.rst:44
+msgid "Xen tools inclusion allows performance monitoring"
+msgstr "Xen tools 包含性能监控"
+
+# 60aeed2365974b86a64bdf02460e8ef7
+#: ../../systemvm.rst:46
+msgid ""
+"Latest versions of HAProxy, iptables, IPsec, and Apache from debian "
+"repository ensures improved security and speed"
+msgstr "最新版本的HAProxy,iptables，IPsec和来自debian库的Apache保证了提高安全性和速度。"
+
+# 5dab0ffe88944ef3ad1ceb02e640ed9d
+#: ../../systemvm.rst:49
+msgid ""
+"Latest version of JRE from Sun/Oracle ensures improved security and speed"
+msgstr "从 Sun/Oracle 安装最新版本的JRE可以保证安全性与速度的提高"
+
+# 9f806f6735e64fb786b5ab22d695493f
+#: ../../systemvm.rst:54
+msgid "Changing the Default System VM Template"
+msgstr "改变默认系统VM模板"
+
+# 88cf932e61dd41a8bc1c583aa0bd38b7
+#: ../../systemvm.rst:56
+msgid ""
+"CloudStack allows you to change the default 32-bit System VM template to "
+"64-bit one. Using the 64-bit template, upgrade the virtual router to manage "
+"larger number of connection in your network."
+msgstr "CloudStack允许你将默认的32位系统模板变为64位，使用64位模板，可以升级虚拟路由器，使得网络支撑更大的连接数。"
+
+# a4f753c8b20b411495b4077d429fadda
+#: ../../systemvm.rst:60
+msgid ""
+"Based on the hypervisor you use, download the 64-bit template from the "
+"following location:"
+msgstr "基于你所使用的hypervisor，从以下地址下载64位模板："
+
+# 0c56be6861554fe2b5519acffca4bbbf
+#: ../../systemvm.rst:64
+msgid "Hypervisor"
+msgstr "Hypervisor"
+
+# 2d2c7eabf8364232911d6ea74c1ebce2
+#: ../../systemvm.rst:64
+msgid "Download Location"
+msgstr "下载地址"
+
+# 18c32afddeff4951a466847a983335fe
+#: ../../systemvm.rst:66
+msgid "XenServer"
+msgstr "XenServer"
+
+# 6ea0f846b0a34711b7c0090cb48d8c32
+#: ../../systemvm.rst:66
+msgid ""
+"http://download.cloud.com/templates/4.2/64bit/systemvmtemplate64-2013-07-15"
+"-master-xen.vhd.bz2"
+msgstr "http://download.cloud.com/templates/4.2/64bit/systemvmtemplate64-2013-07-15-master-xen.vhd.bz2"
+
+# e8a51da6f6614114a91e4006eedfc912
+#: ../../systemvm.rst:67
+msgid "KVM"
+msgstr "KVM"
+
+# fe251bca2b854129890cba8e7ac9bbbf
+#: ../../systemvm.rst:67
+msgid ""
+"http://download.cloud.com/templates/4.2/64bit/systemvmtemplate64-2013-07-15"
+"-master-kvm.qcow2.bz2"
+msgstr "http://download.cloud.com/templates/4.2/64bit/systemvmtemplate64-2013-07-15-master-kvm.qcow2.bz2"
+
+# 2d498240d20c4683ab11ac2232135a16
+#: ../../systemvm.rst:70
+msgid "As an administrator, log in to the CloudStack UI"
+msgstr "使用管理员登录到CloudStack管理界面。"
+
+# cb836b9320584dfe917198280919b2a8
+#: ../../systemvm.rst:72
+msgid "Register the 64 bit template."
+msgstr "注册64位的模板。"
+
+# c8cab1a649c94d0ba1393b80e7bf411b
+#: ../../systemvm.rst:74
+msgid "For example: KVM64bitTemplate"
+msgstr "例如：KVM64bit 模板"
+
+# d88c6f133f114456914ec8807ccef386
+#: ../../systemvm.rst:76
+msgid "While registering the template, select Routing."
+msgstr "当注册模板时，选择路由（routing）。"
+
+# b7e2b731ae7e4c789be6af9ed2d185af
+#: ../../systemvm.rst:78
+msgid "Navigate to Infrastructure > Zone > Settings."
+msgstr "导航至 基础结构 > 地域 > 设置"
+
+# b58d5557ddeb454fbae55b570e2c68f0
+#: ../../systemvm.rst:80
+msgid ""
+"Set the name of the 64-bit template, KVM64bitTemplate, in the "
+"*``router.template.kvm``* global parameter."
+msgstr "在全局参数 *``router.template.kvm``*中设置64位模板的名称，KVM64bitTemplate。"
+
+# 951cf2ccd5d34614a87679078d22599c
+#: ../../systemvm.rst:83
+msgid ""
+"If you are using a XenServer 64-bit template, set the name in the "
+"*``router.template.xen``* global parameter."
+msgstr "如果你正在使用XenServer64位模板，将名字设置在*``router.template.xen``*全局参数中。"
+
+# 534ac4d13b2a4560aa420c9aa2fb9e57
+#: ../../systemvm.rst:86
+msgid ""
+"Any new virtual router created in this Zone automatically picks up this "
+"template."
+msgstr "任何在此地域中创建的新虚拟路由器均使用这个模板。"
+
+# be4168abcbfd4eed8d7d73b2284d3ac4
+#: ../../systemvm.rst:89
+msgid "Restart the Management Server."
+msgstr "重启管理服务器。"
+
+# 266b4692ed0b4fb4bae8eb4d1ce9af1f
+#: ../../systemvm.rst:93
+msgid "Multiple System VM Support for VMware"
+msgstr "支持VMware的多种系统虚拟机"
+
+# 2e1e78598bc94637b2c8fdfb6387a908
+#: ../../systemvm.rst:95
+msgid ""
+"Every CloudStack zone has single System VM for template processing tasks "
+"such as downloading templates, uploading templates, and uploading ISOs. In a"
+" zone where VMware is being used, additional System VMs can be launched to "
+"process VMware-specific tasks such as taking snapshots and creating private "
+"templates. The CloudStack management server launches additional System VMs "
+"for VMware-specific tasks as the load increases. The management server "
+"monitors and weights all commands sent to these System VMs and performs "
+"dynamic load balancing and scaling-up of more System VMs."
+msgstr "每个CloudStack 区域都有一个单独的系统VM用于模板处理任务，如下载模板，上传模板，上传ISO。在使用VMware的区域中，有另外的系统VM用来处理VMware专有的任务，如制作快照，创建私有模板。 当VMware专有任务的负载增加时，CloudStack管理端将推出额外的系统VM。管理端监控并平衡发送到这些系统VM的命令，实行动态负载均衡并增加更多的系统VM。"
+
+# 37fb441bcdb34d6fb7432fa98ef8886b
+#: ../../systemvm.rst:107
+msgid "Console Proxy"
+msgstr "控制台代理"
+
+# 9217568c55be47b7bd405187d23f7777
+#: ../../systemvm.rst:109
+msgid ""
+"The Console Proxy is a type of System Virtual Machine that has a role in "
+"presenting a console view via the web UI. It connects the user’s browser to "
+"the VNC port made available via the hypervisor for the console of the guest."
+" Both the administrator and end user web UIs offer a console connection."
+msgstr "控制台代理是一种系统VM，可以通过网页用户接口为用户呈现一个控制台视图。它通过hypervisor为来宾提供控制台将用户的浏览器与vnc端口相连。管理员和终端用户动能通过网页用户接口获得一个控制台连接。"
+
+# f0a0de282eec4d69a9f65b3ff7114cf8
+#: ../../systemvm.rst:115
+msgid ""
+"Clicking a console icon brings up a new window. The AJAX code downloaded "
+"into that window refers to the public IP address of a console proxy VM. "
+"There is exactly one public IP address allocated per console proxy VM. The "
+"AJAX application connects to this IP. The console proxy then proxies the "
+"connection to the VNC port for the requested VM on the Host hosting the "
+"guest."
+msgstr "点击控制台图标会弹出一个新窗口。根据控制台代理的公共IP ，AJAX代码会下载到这个新窗口。每个控制台代理都会分配一个公共IP。AJAX程序会连接到这个IP。控制台代理会将连接代理到正在运行所请求虚拟机的宿主机的vnc端口。"
+
+# b8ee3c97a12f494fadd3971c927e4f87
+#: ../../systemvm.rst:123
+msgid ""
+"The hypervisors will have many ports assigned to VNC usage so that multiple "
+"VNC sessions can occur simultaneously."
+msgstr "hypervisors可能会分配很多端口到VNC上，因此可能同时并发多个VNC会话。"
+
+# 04dcecfe7e024822a311ba18520f6cce
+#: ../../systemvm.rst:126
+msgid ""
+"There is never any traffic to the guest virtual IP, and there is no need to "
+"enable VNC within the guest."
+msgstr "不会有任何流量是来宾虚拟IP的，因此不需要打开来宾虚拟机的vnc。"
+
+# 15e8724d26714949a10f88914e7038db
+#: ../../systemvm.rst:129
+msgid ""
+"The console proxy VM will periodically report its active session count to "
+"the Management Server. The default reporting interval is five seconds. This "
+"can be changed through standard Management Server configuration with the "
+"parameter consoleproxy.loadscan.interval."
+msgstr "控制台虚拟机会定时的向管理服务器汇报当前活动的会话数。默认报告间隔是五秒钟。可以通过管理服务器的配置参数 consoleproxy.loadscan.interval.更改。"
+
+# 67b327e6f92f4c69a649679cf88b933c
+#: ../../systemvm.rst:134
+msgid ""
+"Assignment of guest VM to console proxy is determined by first determining "
+"if the guest VM has a previous session associated with a console proxy. If "
+"it does, the Management Server will assign the guest VM to the target "
+"Console Proxy VM regardless of the load on the proxy VM. Failing that, the "
+"first available running Console Proxy VM that has the capacity to handle new"
+" sessions is used."
+msgstr "如果来宾虚拟机之前有已经分配的关联控制台代理的会话，控制台代理的分配会由第一次分配的控制台代理决定。如果该来宾虚拟机之前存在已分配的控制台代理，则不论该控制台代理目前负载如何管理服务器都会将该来宾虚拟机分配到目标控制台代理虚拟机。如果失败则会将来宾虚拟机分配到第一个拥有足够资源处理新会话的控制台代理上。"
+
+# 0fcca189c0b0490fb490988079cca591
+#: ../../systemvm.rst:141
+msgid ""
+"Console proxies can be restarted by administrators but this will interrupt "
+"existing console sessions for users."
+msgstr "管理员能重启控制台代理，但此操作会中断用户与控制台会话。"
+
+# 9c3b4c70f4cf47379b07b5f24863023b
+#: ../../systemvm.rst:146
+msgid "Using a SSL Certificate for the Console Proxy"
+msgstr "对控制台代理使用SSL证书。"
+
+# 7be31349d45949dfa61f79105ade746f
+#: ../../systemvm.rst:149
+msgid ""
+"In the past CloudStack used the ``realhostip.com`` dynamic DNS resolution "
+"service. As this service will be shut down as of June 30th, 2014, CloudStack"
+" has stopped using the service as of version 4.3."
+msgstr ""
+
+# ff149d60a5d74070bb252689b6e724ab
+#: ../../systemvm.rst:154
+msgid ""
+"By default, the console viewing functionality uses plaintext HTTP. In any "
+"production environment, the console proxy connection should be encrypted via"
+" SSL at the mininum."
+msgstr "默认情况下，代理视图功能使用HTTP协议，在任何生产环境下，代理服务连接至少要通过SSL进行加密。"
+
+# 471907f542334e94b211495c26beacff
+#: ../../systemvm.rst:158
+msgid ""
+"A CloudStack administrator has 2 ways to secure the console proxy "
+"communication with SSL:"
+msgstr "CloudStack管理员有2种方式来保证SSL加密控制代理连接的安全："
+
+# bd5c72a779c74100ada4a4e0ebd65633
+#: ../../systemvm.rst:161
+msgid "Set up a SSL wild-card certificate and domain name resolution"
+msgstr "建立一个SSL通配证书以及域名解析。"
+
+# 9d2106a856664feba8d3ed31ffef47b3
+#: ../../systemvm.rst:163
+msgid "Set up SSL certificate for specific FQDN and configure load-balancer"
+msgstr "为指定的FQDN建立一个SSL证书并配置负载均衡"
+
+# fbea784e67f546259f790571d5c68d02
+#: ../../systemvm.rst:167
+msgid "Changing the Console Proxy SSL Certificate and Domain"
+msgstr "更改控制代理SSL证书及域"
+
+# 0ef9de23136a444a802cb1fb49929072
+#: ../../systemvm.rst:169
+msgid ""
+"The administrator can configure SSL encryption by selecting a domain and "
+"uploading a new SSL certificate and private key. The domain must run a DNS "
+"service that is capable of resolving queries for addresses of the form aaa-"
+"bbb-ccc-ddd.your.domain to an IPv4 IP address in the form aaa.bbb.ccc.ddd, "
+"for example, 202.8.44.1. To change the console proxy domain, SSL "
+"certificate, and private key:"
+msgstr "管理员可以通过选择一个域并上传一个新的SSL证书和密钥配置SSL加密。这个域必须运行一个能DNS服务器，该服务器能解决地址格式是aaa-bbb-ccc-ddd.your.domain到IPv4 IP地址的结构aaa.bbb.ccc.ddd，例如 for example, 202.8.44.1。就是为了改变终端代理与，SSL证书和私有密钥。"
+
+# 21ed531476934988b073b6db592f8ded
+#: ../../systemvm.rst:176
+msgid ""
+"Set up dynamic name resolution or populate all possible DNS names in your "
+"public IP range into your existing DNS server with the format aaa-bbb-ccc-"
+"ddd.consoleproxy.company.com -> aaa.bbb.ccc.ddd."
+msgstr "建立一个动态的方案或者适用于所有可能DNS名称在你的公共IP范围以format aaa-bbb-ccc-ddd.consoleproxy.company.com-> aaa.bbb.ccc.ddd.到你已经存在的DNS服务器上"
+
+# 8e0e99fee7274b59a2f75b2439a28528
+#: ../../systemvm.rst:181
+msgid ""
+"In these steps you will notice *consoleproxy.company.com* -For security best"
+" practices, we recommend creating a wildcard SSL certificate on a separate "
+"subdomain so in the event that the certificate is compromised, a malicious "
+"user cannot impersonate a company.com domain."
+msgstr "在上述步骤中你会注意到*consoleproxy.company.com* -为安全最好的实践，我们推荐在独立的子域中创建一个新的有通配符的SSL证书，所以证书在事件中可能妥协，一个恶意的用户不能模仿一个company.com域。"
+
+# 8840c66ff2704cbca38c9c9f5daddc09
+#: ../../systemvm.rst:187
+msgid ""
+"Generate the private key and certificate signing request (CSR). When you are"
+" using openssl to generate private/public key pairs and CSRs, for the "
+"private key that you are going to paste into the CloudStack UI, be sure to "
+"convert it into PKCS#8 format."
+msgstr "通常有私钥和证书签名请求(CSR)。当你使用openssl产生私钥/公钥对和CSR,你将私钥复制到CloudStack中，保证转换为PKCS#8格式。"
+
+# efd9b8a8ee594499800d89e3257cef8c
+#: ../../systemvm.rst:192
+msgid "Generate a new 2048-bit private key"
+msgstr "产生一个新的2048位的私钥"
+
+# 95cd5c1544fd480784d73f497d0474a9
+#: ../../systemvm.rst:198
+msgid ""
+"Generate a new certificate CSR. Ensure the creation of a wildcard "
+"certificate, eg ``*.consoleproxy.company.com``"
+msgstr ""
+
+# 8501f0bd21d3496f9a95f55217ad5715
+#: ../../systemvm.rst:205
+msgid ""
+"Head to the website of your favorite trusted Certificate Authority, purchase"
+" an SSL certificate, and submit the CSR. You should receive a valid "
+"certificate in return"
+msgstr "前往你喜爱的站点相信授权证书，购买一个SSL证书并获得CSR确认。你将会收到一个返回的有效地证书"
+
+# c5e0a99a8e5548a7b30a82aad6008419
+#: ../../systemvm.rst:209
+msgid "Convert your private key format into PKCS#8 encrypted format."
+msgstr "转化你的私钥格式成PKCS#8加密格式。"
+
+# 21138c806f2e48abab8f0748512628e2
+#: ../../systemvm.rst:215
+msgid ""
+"Convert your PKCS#8 encrypted private key into the PKCS#8 format that is "
+"compliant with CloudStack"
+msgstr "转化你的PKC#8加密的私钥到PKC#8格式是CloudStack遵循的方式。"
+
+# 021b9614a4c740eb995d66bb07551c5d
+#: ../../systemvm.rst:222
+msgid ""
+"In the Update SSL Certificate screen of the CloudStack UI, paste the "
+"following:"
+msgstr "在CloudStack用户界面的修改SSL证书，复制以下内容："
+
+# 93d3977b1fbf4bdcaa3cb7c106025be0
+#: ../../systemvm.rst:225
+msgid "The certificate you've just generated."
+msgstr "刚刚生成的证书。"
+
+# f8f025d190ce4094a3dd63915b29267f
+#: ../../systemvm.rst:227
+msgid "The private key you've just generated."
+msgstr "刚刚生成的私钥。"
+
+# a44d63f6a2084e029bf84c965e10cae2
+#: ../../systemvm.rst:229
+msgid ""
+"The desired domain name, prefixed with ``*.``; for example, "
+"``*.consoleproxy.company.com``"
+msgstr ""
+
+# d69ea42c636247548be90fe1cb7c5f51
+#: ../../systemvm.rst:231
+msgid "|update-ssl.png|"
+msgstr "|update-ssl.png|"
+
+# b0dd0973913649e1876bac396552c02e
+#: ../../systemvm.rst:233
+msgid ""
+"This stops all currently running console proxy VMs, then restarts them with "
+"the new certificate and key. Users might notice a brief interruption in "
+"console availability."
+msgstr "这停止了所有正运行的终端代理VM,然后已新的许可和密钥重启。用户可能会注意到对控制台有益的一个简短的打断。"
+
+# 88d8a0760f5641a6a3d5dac7f7ecb8e2
+#: ../../systemvm.rst:237
+msgid ""
+"The Management Server generates URLs of the form \"aaa-bbb-ccc-"
+"ddd.consoleproxy.company.com\" after this change is made. The new console "
+"requests will be served with the new DNS domain name, certificate, and key."
+msgstr "管理服务器在这个改变后生成格式如 \"aaa-bbb-ccc-ddd.consoleproxy.company.com\" 的URLs。这个新的终端请求将会依照新的DNS域名，证书和密钥提供服务。"
+
+# d9ae75c0be0d474f8707a09850ff25db
+#: ../../systemvm.rst:244
+msgid "Load-balancing Console Proxies"
+msgstr "负载均衡终端代理"
+
+# baf2bcf57fed4f82aa193fd45f2f2140
+#: ../../systemvm.rst:245
+msgid ""
+"An alternative to using dynamic DNS or creating a range of DNS entries as "
+"described in the last section would be to create a SSL certificate for a "
+"specific domain name, configure CloudStack to use that particular FQDN, and "
+"then configure a load balancer to load balance the console proxy's IP "
+"address behind the FQDN. As the functionality for this is still new, please "
+"see "
+"https://cwiki.apache.org/confluence/display/CLOUDSTACK/Realhost+IP+changes "
+"for more details."
+msgstr "一个在最近的段落中使用动态DNS或者创建一定范围DNS记录作为可替换的描述将被用来创建一个特定域名的SSL证书，配置CloudStack使用特定的FQDN,然后配置一个负载均衡以均衡终端代理IP地址后的FQDN。作为这项新功能的更多详情，参见 http://cwiki.apache.org/confluence/display/CLOUDSTACK/Realhost+IP+changes。"
+
+# f8bc0488fcae4eed874f0719dcbd03dc
+#: ../../systemvm.rst:256
+msgid "Virtual Router"
+msgstr "虚拟路由"
+
+# 5aa09837be9b4cbbb6e84ebaabca6559
+#: ../../systemvm.rst:258
+msgid ""
+"The virtual router is a type of System Virtual Machine. The virtual router "
+"is one of the most frequently used service providers in CloudStack. The end "
+"user has no direct access to the virtual router. Users can ping the virtual "
+"router and take actions that affect it (such as setting up port forwarding),"
+" but users do not have SSH access into the virtual router."
+msgstr "虚拟路由器是一个系统虚拟机。它经常在CloudStack服务方案中被使用；终端用户不能够直接访问虚拟路由器。用户可ping和影响它(比如设置端口转发)但是不能通过ssh访问"
+
+# b1afb70840d04ed6917b9fd0e68a312b
+#: ../../systemvm.rst:265
+msgid ""
+"There is no mechanism for the administrator to log in to the virtual router."
+" Virtual routers can be restarted by administrators, but this will interrupt"
+" public network access and other services for end users. A basic test in "
+"debugging networking issues is to attempt to ping the virtual router from a "
+"guest VM. Some of the characteristics of the virtual router are determined "
+"by its associated system service offering."
+msgstr "这里没有一种机制使得管理员可以登录虚拟路由器。管理员可以重启虚拟路由器，但是会中断终端用户网络访问和服务。在一个基本的网络故障排错中，尝试在一个虚拟机上ping虚拟路由器。虚拟路由器的一些功能特性是通过系统服务方案配置的。"
+
+# a07561d1be02426f9c20ec39d37ebfda
+#: ../../systemvm.rst:274
+msgid "Configuring the Virtual Router"
+msgstr "配置虚拟路由"
+
+# 33b921e943764375b7e2833cd80501f1
+#: ../../systemvm.rst:276
+msgid "You can set the following:"
+msgstr "你可以设置以下内容："
+
+# f4bf9f0a9f5341ce9751734831cb4100
+#: ../../systemvm.rst:278
+msgid "IP range"
+msgstr "IP地址范围"
+
+# 63e37af44a1644428067b31b62f0c6b2
+#: ../../systemvm.rst:280
+msgid "Supported network services"
+msgstr "支持的网络服务"
+
+# e1a2e37b67a14415b27cdce549422c45
+#: ../../systemvm.rst:282
+msgid "Default domain name for the network serviced by the virtual router"
+msgstr "由虚拟路由为网络服务提供的默认域名"
+
+# a78c71c42d6b400e8c6a037d8be60b00
+#: ../../systemvm.rst:284
+msgid "Gateway IP address"
+msgstr "网关IP地址"
+
+# c17203f5ab7c4339ab3bf6d4b276357c
+#: ../../systemvm.rst:286
+msgid ""
+"How often CloudStack fetches network usage statistics from CloudStack "
+"virtual routers. If you want to collect traffic metering data from the "
+"virtual router, set the global configuration parameter "
+"router.stats.interval. If you are not using the virtual router to gather "
+"network usage statistics, set it to 0."
+msgstr "CloudStack多久从虚拟路由器获取一次网络使用数据。如果你想搜集虚拟路由器的流量计量数据，设置全局变量router.stats.interval。如果你不使用虚拟路由器收集网络使用数据，设置该值为0"
+
+# db1198a11ec947f18c4cf2244c33eb08
+#: ../../systemvm.rst:294
+msgid "Upgrading a Virtual Router with System Service Offerings"
+msgstr "使用系统计算服务升级虚拟路由器"
+
+# 35a9d4cee92b4a9fb1654d44110881fa
+#: ../../systemvm.rst:296
+msgid ""
+"When CloudStack creates a virtual router, it uses default settings which are"
+" defined in a default system service offering. See `“System Service "
+"Offerings” <#system-service-offerings>`_. All the virtual routers in a "
+"single guest network use the same system service offering. You can upgrade "
+"the capabilities of the virtual router by creating and applying a custom "
+"system service offering."
+msgstr "当 CloudStack创建一个虚拟路由器，它是按照默认的系统计算服务方案进行的设置。参见 <xref linkend=\"system-service-offerings\" />。所有在单独客户网络中的虚拟路由器都使用相同的系统计算服务方案。可以通过新建和使用自定义的系统计算服务方案来提高虚拟路由器的性能。"
+
+# cd27cfafbeca4a8dbe03d9b84184a373
+#: ../../systemvm.rst:303
+msgid ""
+"Define your custom system service offering. See `“Creating a New System "
+"Service Offering” <#creating-a-new-system-service-offering>`_. In System VM "
+"Type, choose Domain Router."
+msgstr "定义定制的系统计算服务方案，参见<xref linkend=\"creating-system-service-offerings\" />。在系统虚拟机类型中，选择域路由器。"
+
+# 59d868f989f44a7daf1bfbc0e292db28
+#: ../../systemvm.rst:308
+msgid ""
+"Associate the system service offering with a network offering. See "
+"`“Creating a New Network Offering” <networking.html#creating-a-new-network-"
+"offering>`_."
+msgstr "使用网络服务方案配合系统计算服务方案，参见 `“创建一个新网络方案” <networking.html#creating-a-new-network-offering>`_."
+
+# dfa56664a39341bcbf503aa23d46f1d4
+#: ../../systemvm.rst:312
+msgid ""
+"Apply the network offering to the network where you want the virtual routers"
+" to use the new system service offering. If this is a new network, follow "
+"the steps in Adding an Additional Guest Network on page 66. To change the "
+"service offering for existing virtual routers, follow the steps in "
+"`“Changing the Network Offering on a Guest Network” <networking2.html"
+"#changing-the-network-offering-on-a-guest-network>`_."
+msgstr "将网络服务方案应用到使用新系统计算服务方案的虚拟路由器的网络上。如果这是一个新的网络，请根据66页的添加额外客户网络的步骤操作。想要改变已生成的虚拟路由器的计算服务方案，请根据 `“在客户端网络改变网络方案” <networking2.html#changing-the-network-offering-on-a-guest-network>`_."
+
+# 24d02637553648a99ee527214679997f
+#: ../../systemvm.rst:321
+msgid "Best Practices for Virtual Routers"
+msgstr "虚拟路由器的最佳实践"
+
+# 9264d919f1d24e30b3ff39600891fd32
+#: ../../systemvm.rst:323
+msgid ""
+"WARNING: Restarting a virtual router from a hypervisor console deletes all "
+"the iptables rules. To work around this issue, stop the virtual router and "
+"start it from the CloudStack UI."
+msgstr "警告：从一个虚拟机管理程序控制台重新启动一台虚拟路由器，将删除所有iptables规则。要解决这个问题，从CloudStack用户界面停止虚拟路由器和启动。"
+
+# f0a98ab823014588ba7a79e496358417
+#: ../../systemvm.rst:328
+msgid ""
+"Do not use the destroyRouter API when only one router is available in the "
+"network, because restartNetwork API with the cleanup=false parameter can't "
+"recreate it later. If you want to destroy and recreate the single router "
+"available in the network, use the restartNetwork API with the cleanup=true "
+"parameter."
+msgstr "在网络中只有一个路由器可用时，不要使用destroyRouter API，因为restartNetwork API 带cleanup=false参数不能随后重新创建它。如果你想销毁并重新创建网络中的单一路由器，使用restartNetwork API 带cleanup=true参数。"
+
+# c9fe7a0ac42f4b8ba7e912ff1ccd88a6
+#: ../../systemvm.rst:336
+msgid "Service Monitoring Tool for Virtual Router"
+msgstr "虚拟路由的服务监视工具"
+
+# 8c7761b870df47549d73c8e0a8e21ec0
+#: ../../systemvm.rst:338
+msgid ""
+"Various services running on the CloudStack virtual routers can be monitored "
+"by using a Service Monitoring tool. The tool ensures that services are "
+"successfully running until CloudStack deliberately disables them. If a "
+"service goes down, the tool automatically restarts the service, and if that "
+"does not help bringing up the service, an alert as well as an event is "
+"generated indicating the failure. A new global parameter, "
+"``network.router.enableservicemonitoring``, has been introduced to control "
+"this feature. The default value is false, implies, monitoring is disabled. "
+"When you enable, ensure that the Management Server and the router are "
+"restarted."
+msgstr "运行在CloudStack虚拟路由上的不同的各种服务都可以使用服务监视工具监视。工具将确保服务成功运行除非CloudStack被故意损坏。如果一个服务停止，工具将自动重启该服务，如果不能帮助重启该服务，将产生一个导致失败的警报事件。一个全局参数，\"network.router.enableservicemonitoring\",已经被介绍了它能控制这种特性。默认值是false,也就是说监控不是默认。当你激活后，确保服务管理器和路由被重启。"
+
+# eb435554762a44ae9561f7c121329709
+#: ../../systemvm.rst:349
+msgid ""
+"Monitoring tool can help to start a VR service, which is crashed due to an "
+"unexpected reason. For example:"
+msgstr "监视工具可以帮助启动一个由不期望的原因导致的冲突的VR服务。例如："
+
+# c64d62fa24064373919f92f8bb26dab6
+#: ../../systemvm.rst:352
+msgid "The services crashed due to defects in the source code."
+msgstr "由原代码的缺点引起的服务冲突。"
+
+# 19f8982ead484814b9812242f98822cf
+#: ../../systemvm.rst:354
+msgid ""
+"The services that are terminated by the OS when memory or CPU is not "
+"sufficiently available for the service."
+msgstr "当此服务的内存空间或者CPU运算出现不足时，OS将终止此服务。"
+
+# 88522e16c4ad4587887f207c3cb1de9f
+#: ../../systemvm.rst:358
+msgid ""
+"Only those services with daemons are monitored. The services that are failed"
+" due to errors in the service/daemon configuration file cannot be restarted "
+"by the Monitoring tool. VPC networks are not supported."
+msgstr "只有这些服务的守护进程仍被监视。这些服务因在服务器/守护进程配置文件中的错误而失败将导致不能被监视工具重启。VPC网络不予支持。"
+
+# d6dde7af5158444683442aab05bf244e
+#: ../../systemvm.rst:362
+msgid "The following services are monitored in a VR:"
+msgstr "在VR中监视下列服务："
+
+# 919f0a593e4c494588e1859a5fccfae0
+# b9653f8b1d8744999883790ea0990b01
+#: ../../systemvm.rst:364 ../../systemvm.rst:424
+msgid "DNS"
+msgstr "DNS"
+
+# c8fa5957a2504e62afaf2aef337a064b
+#: ../../systemvm.rst:366
+msgid "HA Proxy"
+msgstr "HA代理"
+
+# d5ed20a1e7744cb0b70dcfa442d18ee0
+#: ../../systemvm.rst:368
+msgid "SSH"
+msgstr "SSH"
+
+# 9a5f6db0ba8441d4ad47c0946c9230bb
+#: ../../systemvm.rst:370
+msgid "Apache Web Server"
+msgstr "Apache网络服务器"
+
+# 6f2ae7c39bfd4fd3b950701b42e2f0fa
+#: ../../systemvm.rst:372
+msgid "The following networks are supported:"
+msgstr "支持以下网络："
+
+# 6ed18a5a0c7f48feacc05607c212daf6
+#: ../../systemvm.rst:374
+msgid "Isolated Networks"
+msgstr "独立的网络"
+
+# fd2ab5e43ac34e0fa5bade7bde71c5cf
+#: ../../systemvm.rst:376
+msgid "Shared Networks in both Advanced and Basic zone"
+msgstr "在高级和基础域中分享网络"
+
+# fb5714c33d284b61af774529226b1346
+#: ../../systemvm.rst:378
+msgid "VPC networks are not supported"
+msgstr "VPC网络不被支持"
+
+# d22c1884f61f4ed5b1e3c6c1b2b8b218
+#: ../../systemvm.rst:380
+msgid ""
+"This feature is supported on the following hypervisors: XenServer, VMware, "
+"and KVM."
+msgstr "在下列hypervisor上支持此特性：XenServer,VMware和KVM"
+
+# 209b4c2a4ff24293988606ece94dcc3d
+#: ../../systemvm.rst:385
+msgid "Enhanced Upgrade for Virtual Routers"
+msgstr "增强的网络路由升级"
+
+# fe5f961e7475463681b5ffacfc66cadd
+#: ../../systemvm.rst:387
+msgid ""
+"Upgrading VR is made flexible. The CloudStack administrators will be able to"
+" control the sequence of the VR upgrades. The sequencing is based on "
+"Infrastructure hierarchy, such as by Cluster, Pod, or Zone, and "
+"Administrative (Account) hierarchy, such as by Tenant or Domain. As an "
+"administrator, you can also determine when a particular customer service, "
+"such as VR, is upgraded within a specified upgrade interval. Upgrade "
+"operation is enhanced to increase the upgrade speed by allowing as many "
+"upgrade operations in parallel as possible."
+msgstr "升级VR也是很灵活的。CloudStack管理员将能够控制VR升级序列。该序列基于Infrastructure层，例如Cluster,pod或者Zone,管理层 (账户)，例如Tenan或者Domain.作为管理员，当一个特殊的用户服务,例如VR,在一个短暂的具体升级后的间隔后，你可以终止它。升级操作将允许多个升级操作并行操作促使升级速度增加。"
+
+# 0a2326eddab447b690fd8118e9f41940
+#: ../../systemvm.rst:396
+msgid ""
+"During the entire duration of the upgrade, users cannot launch new services "
+"or make changes to an existing service."
+msgstr "在一个完整的持续的升级过程中，用户不能启动新服务或者改变已经存在的服务。"
+
+# 4fb42cca852e4f548c30cb9034654413
+#: ../../systemvm.rst:399
+msgid ""
+"Additionally, using multiple versions of VRs in a single instance is "
+"supported. In the Details tab of a VR, you can view the version and whether "
+"it requires upgrade. During the Management Server upgrade, CloudStack checks"
+" whether VR is at the latest version before performing any operation on the "
+"VR. To support this, a new global parameter, *``router.version.check``*, has"
+" been added. This parameter is set to true by default, which implies minimum"
+" required version is checked before performing any operation. No operation "
+"is performed if the VR is not at the required version. Services of the older"
+" version VR continue to be available, but no further operations can be "
+"performed on the VR until it is upgraded to the latest version. This will be"
+" a transient state until the VR is upgraded. This will ensure that the "
+"availability of VR services and VR state is not impacted due to the "
+"Management Server upgrade."
+msgstr "另外，使用多版本的VR在一个单例上也是支持的。对于具体地VR，你可以预览版本和是否升级。在管理服务器升级时，CLoudStack检查VR是否是VR上操作的最新版本。为支持此特点，一个新的全局参数，*``router.version.check``*, 已经被加入.这个参数默认设置为true,它意味着当操作前，最少要求版本检查。如果不是VR要求的版本就没有任何操作。在旧的版本上的VR仍然是有效地，但必须升级后才能进行更多的操作。在升级之前，它将是临时状态。这将保证VR服务和状态不受管理服务器升级的影响。"
+
+# 0567e75c33134bcea3a1caa72a5aaa00
+#: ../../systemvm.rst:414
+msgid ""
+"The following service will be available even if the VR is not upgraded. "
+"However, no changes for any of the services can be sent to the VR, until it "
+"is upgraded:"
+msgstr "以下服务将是有效的，无论VR是否升级。或者，没有任何服务在VR升级后发送到VR."
+
+# 48fcfc3f076b494e942f868e0372e0b9
+#: ../../systemvm.rst:418
+msgid "SecurityGroup"
+msgstr "安全组"
+
+# 1bee20546a154520ba2788c22c1f3486
+#: ../../systemvm.rst:420
+msgid "UserData"
+msgstr "用户数据"
+
+# 60d206f07ef3446fa4fb2747aa88893b
+#: ../../systemvm.rst:422
+msgid "DHCP"
+msgstr "DHCP"
+
+# ace288f1a1044792b92215d6a79af5d1
+#: ../../systemvm.rst:426
+msgid "LB"
+msgstr "LB"
+
+# 4ccc43be9ec44655b59657daed06a562
+#: ../../systemvm.rst:428
+msgid "Port Forwarding"
+msgstr "端口转发"
+
+# 1ffbebe241a745ebaaea80aa5ff7e00e
+#: ../../systemvm.rst:430
+msgid "VPN"
+msgstr "VPN"
+
+# 9bfb5e6221b142eab579bea52cded3a4
+#: ../../systemvm.rst:432
+msgid "Static NAT"
+msgstr "静态 NAT"
+
+# 2b905be150d94c69b81d0dfbcf8e70ec
+#: ../../systemvm.rst:434
+msgid "Source NAT"
+msgstr "Source NAT"
+
+# 952471d71a404a99b736c2438fd03018
+#: ../../systemvm.rst:436
+msgid "Firewall"
+msgstr "防火墙"
+
+# 4051d26b7c91408999d41f021c3ca178
+#: ../../systemvm.rst:438
+msgid "Gateway"
+msgstr "网关"
+
+# 69c89cdcc4844f728351fe01740e32ef
+#: ../../systemvm.rst:440
+msgid "NetworkACL"
+msgstr "网络ACL"
+
+# 769b3ed7ed5c4ccf85d9386e5aea8b3f
+#: ../../systemvm.rst:444
+msgid "Supported Virtual Routers"
+msgstr "支持虚拟路由"
+
+# b3bd3d522cca4802afae131818e0df27
+#: ../../systemvm.rst:446
+msgid "VR"
+msgstr "VR"
+
+# 6378fb7b02b248cb8e34872a3d19b51d
+#: ../../systemvm.rst:448
+msgid "VPC VR"
+msgstr "VPC VR"
+
+# dd5c03dc42ae4454a713ff50a2be91e9
+#: ../../systemvm.rst:450
+msgid "Redundant VR"
+msgstr "多余的VR"
+
+# d9325031af0f4d1597f136b4d9f0e3e3
+#: ../../systemvm.rst:454
+msgid "Upgrading Virtual Routers"
+msgstr "升级中的虚拟路由"
+
+# 975d8f6d95014399909cc0cd8a2b16c6
+#: ../../systemvm.rst:456
+msgid "Download the latest System VM template."
+msgstr "下载最新的系统VM模板。"
+
+# c25708086d324a38b701d238b7463924
+#: ../../systemvm.rst:458
+msgid "Download the latest System VM to all the primary storage pools."
+msgstr "下载最新的系统VM到所有主存储池。"
+
+# c9378adb82f140be8f8663c096c895c5
+#: ../../systemvm.rst:460
+msgid "Upgrade the Management Server."
+msgstr "升级管理服务器"
+
+# 40387558057548f98875005c7ceabeb7
+#: ../../systemvm.rst:462
+msgid ""
+"Upgrade CPVM and SSVM either from the UI or by using the following script:"
+msgstr "从用户界面和使用下列描述中升级CPVM和SSVM"
+
+# d28d9ad5f0a0451bbff0baf5b102d9dd
+#: ../../systemvm.rst:469
+msgid ""
+"Even when the VRs are still on older versions, existing services will "
+"continue to be available to the VMs. The Management Server cannot perform "
+"any operations on the VRs until they are upgraded."
+msgstr "即使VR仍然是老版本，已经存在的服务会继续对VM有效。管理服务器除非升级，否则不会再VR上有任何动作。"
+
+# 2a8027346ddf4f988d4554184bcdb544
+#: ../../systemvm.rst:473
+msgid "Selectively upgrade the VRs:"
+msgstr "选择性的升级VR:"
+
+# 6e59012980ce40deba2b51593d9d8901
+#: ../../systemvm.rst:475
+msgid "Log in to the CloudStack UI as the root administrator."
+msgstr "用系统管理员登陆到CloudStack UI界面。"
+
+# 728ae8ec4eb74571819bf5ec86b38073
+#: ../../systemvm.rst:477
+msgid "In the left navigation, choose Infrastructure."
+msgstr "在左边的导航，选择基础架构。"
+
+# 2d56351b1a1644bda4f342dce58b51d7
+#: ../../systemvm.rst:479
+msgid "On Virtual Routers, click View More."
+msgstr "在虚拟路由上，单击更多视图。"
+
+# 9af9b62d86b14af2a745e1a359d1c940
+#: ../../systemvm.rst:481
+msgid "All the VRs are listed in the Virtual Routers page."
+msgstr "所有的VR都在虚拟路由页中列出。"
+
+# f19642bbaf564ca0a26f3e8dff683a65
+#: ../../systemvm.rst:483
+msgid ""
+"In Select View drop-down, select desired grouping based on your requirement."
+msgstr "在选择视图的下拉列表中，选择所需的群组"
+
+# a76c013f7da8482eb097248fb3757989
+#: ../../systemvm.rst:486
+msgid "You can use either of the following:"
+msgstr "你可以设置以下内容："
+
+# 0b60f1059d8e4b1faadac9b7a3113d8b
+#: ../../systemvm.rst:488
+msgid "Group by zone"
+msgstr "按域分组"
+
+# 5a12e32c9b0c4862a582cca80cd74030
+#: ../../systemvm.rst:490
+msgid "Group by pod"
+msgstr "按提供点分组"
+
+# a83f4a59498e44e09b79b5eb014f9d4f
+#: ../../systemvm.rst:492
+msgid "Group by cluster"
+msgstr "按群集分组"
+
+# a1c022abb009480bb49288cdad2b5210
+#: ../../systemvm.rst:494
+msgid "Group by account"
+msgstr "按账户分组"
+
+# 87a6b85df243430293aa4d5a55e00c4a
+#: ../../systemvm.rst:496
+msgid "Click the group which has the VRs to be upgraded."
+msgstr "单击已经被升级的VR组"
+
+# 9e519d5a83be4513a0a20c665777a298
+#: ../../systemvm.rst:498
+msgid ""
+"For example, if you have selected Group by zone, select the name of the "
+"desired zone."
+msgstr "例如，你可以按域分组，选择希望的域名。"
+
+# bd6d3d8bf8954923909c8147a4718053
+#: ../../systemvm.rst:501
+msgid "Click the Upgrade button to upgrade all the VRs. |vr-upgrade.png|"
+msgstr "单击升级按钮升级所有的VRs.|vr-upgrade.png|"
+
+# 56d36b4fbb234438a6e0fce7d66a0ac1
+#: ../../systemvm.rst:503
+msgid "Click OK to confirm."
+msgstr "点击确定。"
+
+# 2b7574a9be0e46a9bd04bff25c748a13
+#: ../../systemvm.rst:507
+msgid "Secondary Storage VM"
+msgstr "辅助存储VM"
+
+# e941ae432ef24ea2a8b4987accf91257
+#: ../../systemvm.rst:509
+msgid ""
+"In addition to the hosts, CloudStack’s Secondary Storage VM mounts and "
+"writes to secondary storage."
+msgstr "除了主机，CloudStack的二级存储虚拟机会挂载和往二级存储中写入内容。"
+
+# f062d628750b4d5bbf97ac967cf17788
+#: ../../systemvm.rst:512
+msgid ""
+"Submissions to secondary storage go through the Secondary Storage VM. The "
+"Secondary Storage VM can retrieve templates and ISO images from URLs using a"
+" variety of protocols."
+msgstr "通过二级存储虚拟机来提交信息到二级存储。二级存储虚拟机会使用多种协议通过URL来获取模版和ISO镜像文件。"
+
+# cedfcfe3cd38411ca2633b120ab0d034
+#: ../../systemvm.rst:516
+msgid ""
+"The secondary storage VM provides a background task that takes care of a "
+"variety of secondary storage activities: downloading a new template to a "
+"Zone, copying templates between Zones, and snapshot backups."
+msgstr "二级存储虚拟机会提供后台任务来负责各种二级存储的活动：将新模版的下载到资源域中，多个资源域之间的模版复制，和快照备份。"
+
+# c2a68c523bf14634b2f881ce767633cc
+#: ../../systemvm.rst:520
+msgid "The administrator can log in to the secondary storage VM if needed."
+msgstr "如果有需要，管理员可以登录到辅助存储VM上。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/templates.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/templates.mo
new file mode 100644
index 0000000..4f9da4b
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/templates.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/templates.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/templates.po
new file mode 100644
index 0000000..5c7077f
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/templates.po
@@ -0,0 +1,1554 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:04+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# cf61f319f9464e6a8d50baac31e9b5ec
+#: ../../templates.rst:18
+msgid "Working with Templates"
+msgstr "使用模板"
+
+# 9fd79a40a20d4709abcae61ed6a93dfd
+#: ../../templates.rst:20
+msgid ""
+"A template is a reusable configuration for virtual machines. When users "
+"launch VMs, they can choose from a list of templates in CloudStack."
+msgstr "模板相当于虚拟机的重用配置。当用户创建虚拟机时能从CloudStack的模板列表中选择一个。"
+
+# 882ddad869e440869d4f74c92ab41271
+#: ../../templates.rst:23
+msgid ""
+"Specifically, a template is a virtual disk image that includes one of a "
+"variety of operating systems, optional additional software such as office "
+"applications, and settings such as access control to determine who can use "
+"the template. Each template is associated with a particular type of "
+"hypervisor, which is specified when the template is added to CloudStack."
+msgstr "特殊情况下，模板可以是一个包含一个或多个操作系统的虚拟磁盘镜像，你可以选择性的安装另外的软件，比如office应用并设置访问控制来决定谁能使用这个模板。每个模板对应一个特殊类型的虚拟机，此类虚拟机在将模板添加入CloudStack时指定。"
+
+# 100cd7a983eb4961b368c8ba7734c42d
+#: ../../templates.rst:30
+msgid ""
+"CloudStack ships with a default template. In order to present more choices "
+"to users, CloudStack administrators and users can create templates and add "
+"them to CloudStack."
+msgstr "CloudStack附带一个默认模板。为了向用户呈现出更多选择，CloudStack的管理员和用户能创建模板并添加到CloudStack中。"
+
+# 18309d4f55464acabeff92b1bab9055f
+#: ../../templates.rst:36
+msgid "Creating Templates: Overview"
+msgstr "创建模板概览"
+
+# 51d039ce8ec945faabf8f8999b3d3c0f
+#: ../../templates.rst:38
+msgid ""
+"CloudStack ships with a default template for the CentOS operating system. "
+"There are a variety of ways to add more templates. Administrators and end "
+"users can add templates. The typical sequence of events is:"
+msgstr "CloudStack默认已经有了一个带CentOS系统的默认模板。有许多添加更多模板的方法，管理员和普通用户均能添加。一般是这样的顺序："
+
+# 06dcc3e2b2554e33bbfdf892226179bd
+#: ../../templates.rst:43
+msgid ""
+"Launch a VM instance that has the operating system you want. Make any other "
+"desired configuration changes to the VM."
+msgstr "运行一个带有你需要的操作系统的虚拟机实例，并进行一些你期望的设置。"
+
+# 991daad714364dbdb6c7429365bfb041
+#: ../../templates.rst:46
+msgid "Stop the VM."
+msgstr "停止VM。"
+
+# 284657ff1abc49e09a72598a4a379a00
+#: ../../templates.rst:48
+msgid "Convert the volume into a template."
+msgstr "将卷转换为模板。"
+
+# ee2b8742854b46679adc6fced33914ab
+#: ../../templates.rst:50
+msgid ""
+"There are other ways to add templates to CloudStack. For example, you can "
+"take a snapshot of the VM's volume and create a template from the snapshot, "
+"or import a VHD from another system into CloudStack."
+msgstr "还有其他方法向CloudStack中添加模板。比如你可以对虚机磁盘卷做个快照然后通过这个快照创建模板，或者从另一个系统导入一个VHD到CloudStack。"
+
+# 7dee2cf1359f4fcdb0bc7f03150b7582
+#: ../../templates.rst:54
+msgid ""
+"The various techniques for creating templates are described in the next few "
+"sections."
+msgstr "接下来的几节中将继续讲述各种创建模板的技术。"
+
+# 9fa8a8480b0345fd8fa7ccd71dcf1b0c
+#: ../../templates.rst:59
+msgid "Requirements for Templates"
+msgstr "模板的需求"
+
+# cb14c5b032c24423959c7044dc64c47f
+#: ../../templates.rst:61
+msgid ""
+"For XenServer, install PV drivers / Xen tools on each template that you "
+"create. This will enable live migration and clean guest shutdown."
+msgstr "对于 XenServer, 在每一个你创建的模板上安装 PV 驱动 / Xen tools。 这将使动态迁移和干净的宾客关机成为可能。"
+
+# f69f5344e03e49e78a793d4ca605d703
+#: ../../templates.rst:64
+msgid ""
+"For vSphere, install VMware Tools on each template that you create. This "
+"will enable console view to work properly."
+msgstr "对于 vSphere, 在每一个你创建的模板上安装VMware 工具。这将使控制台视图能够正常工作。"
+
+# edd05ad541bd4f498f39bb0645713513
+#: ../../templates.rst:69
+msgid "Best Practices for Templates"
+msgstr "模板最佳实践"
+
+# fd430ee9ee634ec9bf53dfcec6786ee3
+#: ../../templates.rst:71
+msgid ""
+"If you plan to use large templates (100 GB or larger), be sure you have a "
+"10-gigabit network to support the large templates. A slower network can lead"
+" to timeouts and other errors when large templates are used."
+msgstr "如果你计划使用大的模板(100 GB 或更大)，确保你有10g 的网络以支持大的模板。 当大的模板被使用时，较慢的网络可能导致超时及其它错误。"
+
+# 4405e8f642174cb3afc031cd7fdb4dd4
+#: ../../templates.rst:77
+msgid "The Default Template"
+msgstr "默认模版"
+
+# 1f4b4121eca94788a949ff8bbb9b6377
+#: ../../templates.rst:79
+msgid ""
+"CloudStack includes a CentOS template. This template is downloaded by the "
+"Secondary Storage VM after the primary and secondary storage are configured."
+" You can use this template in your production deployment or you can delete "
+"it and use custom templates."
+msgstr "CloudStack包含一个CentOS 模版。当主存储和二级存储配置完成后，这个模版会由二级存储虚拟机下载。可以在生产部署中使用这个模版，也可以删除掉它，使用自定义的模版。"
+
+# a5936c6c63214301b0a732ab8a848614
+#: ../../templates.rst:84
+msgid "The root password for the default template is \"password\"."
+msgstr "默认模版的root用户密码是“password”。"
+
+# 56f17d0ded4f4175b6a8c78f5e04b44f
+#: ../../templates.rst:86
+msgid ""
+"A default template is provided for each of XenServer, KVM, and vSphere. The "
+"templates that are downloaded depend on the hypervisor type that is "
+"available in your cloud. Each template is approximately 2.5 GB physical "
+"size."
+msgstr "为XenServer，KVM和vSphere各提供了一个默认模板。下载的模板取决于你的云中使用的hypervisor类型。每个模板大概占用2.5GB的存储空间。"
+
+# 5c9065097a2b42dbb7b454a66807e888
+#: ../../templates.rst:91
+msgid ""
+"The default template includes the standard iptables rules, which will block "
+"most access to the template excluding ssh."
+msgstr "默认模版包括标准的iptables 规则，会阻止除了ssh以外的其他访问。"
+
+# 466a67f6a17249d19212da0a1d4ae915
+#: ../../templates.rst:123
+msgid "Private and Public Templates"
+msgstr "私有模板和公共模板"
+
+# 9c4cef26750347d693d5d9d2abc33ab3
+#: ../../templates.rst:125
+msgid ""
+"When a user creates a template, it can be designated private or public."
+msgstr "用户创建模板时可选择模板为公有还是私有。"
+
+# 0a5c2d13d7de4c8696c17de766c7ff8e
+#: ../../templates.rst:127
+msgid ""
+"Private templates are only available to the user who created them. By "
+"default, an uploaded template is private."
+msgstr "私有模板只对创建者可用。默认上传的模板都是私有的。"
+
+# 28c6ea956b7145bf87d5c591a262ed56
+#: ../../templates.rst:130
+msgid ""
+"When a user marks a template as “public,” the template becomes available to "
+"all users in all accounts in the user's domain, as well as users in any "
+"other domains that have access to the Zone where the template is stored. "
+"This depends on whether the Zone, in turn, was defined as private or public."
+" A private Zone is assigned to a single domain, and a public Zone is "
+"accessible to any domain. If a public template is created in a private Zone,"
+" it is available only to users in the domain assigned to that Zone. If a "
+"public template is created in a public Zone, it is available to all users in"
+" all domains."
+msgstr "当用户将模板标识为“公有”，该模板不但能让该用户域中所有账户中的所有用户使用，还可以让能访问存储该模板的区域的其他域中用户使用。这取决于zone是设置成公用还是私有。私有区域被分配到一个单一的域，而公共区域能被任何域访问。"
+
+# 8cc9490673de43a29b0fa3b899a796c0
+#: ../../templates.rst:142
+msgid "Creating a Template from an Existing Virtual Machine"
+msgstr "通过已存在的虚拟机创建模板"
+
+# 0cd7674a6e674324a8b36a9eef61b924
+#: ../../templates.rst:144
+msgid ""
+"Once you have at least one VM set up in the way you want, you can use it as "
+"the prototype for other VMs."
+msgstr "当你已经有了一台按你的想法已经配置好的虚拟机，你就能以他为原型创建别的虚拟机。"
+
+# e16345095f804e34ba10cdf1772864c5
+#: ../../templates.rst:147
+msgid ""
+"Create and start a virtual machine using any of the techniques given in "
+"`“Creating VMs” <virtual_machines.html#creating-vms>`_."
+msgstr "使用 `“创建VMs” <virtual_machines.html#creating-vms>`_给出的方法创建并且开启一个虚拟机。"
+
+# 9ecb6312deb04964a10192717ca021b5
+#: ../../templates.rst:150
+msgid ""
+"Make any desired configuration changes on the running VM, then click Stop."
+msgstr "在虚拟机中做好需要的配置，然后点击按钮关闭该虚拟机。"
+
+# 3bf1cf52e2f44c9bb0cc976b5b3217d4
+#: ../../templates.rst:153
+msgid ""
+"Wait for the VM to stop. When the status shows Stopped, go to the next step."
+msgstr "等待虚拟机关闭。当虚拟机状态显示为“已停止”，执行下一步。"
+
+# 51cee376de054012b33542272d214e67
+#: ../../templates.rst:156
+msgid "Click Create Template and provide the following:"
+msgstr "点击创建模板并填写如下内容："
+
+# 3dc70b806977409392d741e01a49337b
+#: ../../templates.rst:158
+msgid ""
+"**Name and Display Text**. These will be shown in the UI, so choose "
+"something descriptive."
+msgstr "**名称和显示文本**。这些会在UI中显示，所以建议写一些描述信息。"
+
+# b7cb11e24ec1424abcb2fd299d27e6f8
+#: ../../templates.rst:161
+msgid ""
+"**OS Type**. This helps CloudStack and the hypervisor perform certain "
+"operations and make assumptions that improve the performance of the guest. "
+"Select one of the following."
+msgstr "**操作系统类型*:。这有助于CloudStack和Hypervisor执行某些操作并可能提高来宾虚拟机的性能。选择下列之一。"
+
+# b79a71e908b643308ec4fe326a113d06
+# 3a9638381a74458e8dc78d91fcd5d121
+#: ../../templates.rst:165 ../../templates.rst:242
+msgid "If the operating system of the stopped VM is listed, choose it."
+msgstr "如果已停止虚拟机的系统在列表中，选择它。"
+
+# c2046860ca7a420282727c68e7e0bd8d
+# 612b47eacf5a4564b7557383ab6085ff
+#: ../../templates.rst:167 ../../templates.rst:244
+msgid "If the OS type of the stopped VM is not listed, choose Other."
+msgstr "如果已停止虚拟机系统类型不在列表中就选择其他。"
+
+# a132a4db61c047f6843764cb4ad468c3
+#: ../../templates.rst:169
+msgid ""
+"If you want to boot from this template in PV mode, choose Other PV (32-bit) "
+"or Other PV (64-bit). This choice is available only for XenServere:"
+msgstr "如果你打算以PV模式启动该模板，请选择其他PV(32位)或其他PV(64位)。这个选项只对XenServer有效："
+
+# 400f23d7aa30429cadbbcf6d927ea291
+#: ../../templates.rst:174
+msgid ""
+"Generally you should not choose an older version of the OS than the version "
+"in the image. For example, choosing CentOS 5.4 to support a CentOS 6.2 image"
+" will in general not work. In those cases you should choose Other."
+msgstr "通常你不能选择比镜像版本老的OS版本。比如，选择CentOS 5.4来支持CentOS 6.2镜像通常来说是不工作的。在这种情况下，你应该选择其他。"
+
+# a74d603504464359801664a22644ecf1
+# f36349a0b7934f51bc4238b6ce12d3bd
+#: ../../templates.rst:179 ../../templates.rst:266
+msgid ""
+"**Public**. Choose Yes to make this template accessible to all users of this"
+" CloudStack installation. The template will appear in the Community "
+"Templates list. See `“Private and Public Templates” <#private-and-public-"
+"templates>`_."
+msgstr "**公共**。选择是来让CloudStack里面的所有用户都能访问这个模板。模板将会出现在社区模板列表中。请参阅 `“私有和公共模板” <#private-and-public-templates>`_。"
+
+# cad391d15484479f99460980862c7571
+# f596589a997f4443a0ac19eee063c09f
+#: ../../templates.rst:184 ../../templates.rst:258
+msgid ""
+"**Password Enabled**. Choose Yes if your template has the CloudStack "
+"password change script installed. See :ref:`adding-password-management-to-"
+"templates`."
+msgstr "**启用密码**。如果你的模板中安装了CLoudStack密码修改脚本，选择是。请参阅 :ref:`adding-password-management-to-templates`。"
+
+# 0ad3f0f48f50458e8c753d6a087e4736
+#: ../../templates.rst:188
+msgid "Click Add."
+msgstr "点击 添加"
+
+# 7560e86cb7f64b25a24a8adffa210672
+#: ../../templates.rst:190
+msgid ""
+"The new template will be visible in the Templates section when the template "
+"creation process has been completed. The template is then available when "
+"creating a new VM."
+msgstr "当模版创建过程完成后，新模版会出现在模版页面。在创建虚机时就可以使用新模版了。"
+
+# f25db73d631a4cf2b1a90ddbc720ebea
+#: ../../templates.rst:196
+msgid "Creating a Template from a Snapshot"
+msgstr "从一个快照创建一个模板"
+
+# 37c2eb36164e46d982140684d23eccc7
+#: ../../templates.rst:198
+msgid ""
+"If you do not want to stop the VM in order to use the Create Template menu "
+"item (as described in `“Creating a Template from an Existing Virtual "
+"Machine” <#creating-a-template-from-an-existing-virtual-machine>`_), you can"
+" create a template directly from any snapshot through the CloudStack UI."
+msgstr "如果你不想为了使用创建模板菜单项而停止虚拟机(如在`“从已有的虚机创建模板” <#creating-a-template-from-an-existing-virtual-machine>`_中描述的)， 你可以通过CloudStack UI从任何快照直接创建模板。"
+
+# 1fddfc6f75c745558d997e2c6af314cf
+#: ../../templates.rst:206
+msgid "Uploading Templates"
+msgstr "上传模板"
+
+# f50af047d15042849fd3b9d1ea923270
+#: ../../templates.rst:210
+msgid "vSphere Templates and ISOs"
+msgstr "vSphere模板和ISOs"
+
+# 942a210bb20f467b98414c592d71af20
+#: ../../templates.rst:212
+msgid ""
+"If you are uploading a template that was created using vSphere Client, be "
+"sure the OVA file does not contain an ISO. If it does, the deployment of VMs"
+" from the template will fail."
+msgstr "如果你通过vSphere Client上传模板，请确认OVA文件不包含ISO。如果是的话，从模板部署虚拟机将失败。"
+
+# 6b6237e29230422f8b97fbbbc07dffd7
+#: ../../templates.rst:216
+msgid ""
+"Templates are uploaded based on a URL. HTTP is the supported access "
+"protocol. Templates are frequently large files. You can optionally gzip them"
+" to decrease upload times."
+msgstr "模板是使用HTTP协议通过URL来上传的。模板通常都很大。你可以使用gzip压缩它们以缩短上传时间。"
+
+# 40368082877e412c87f9a15e9b28e64a
+#: ../../templates.rst:220
+msgid "To upload a template:"
+msgstr "要上传模板："
+
+# b954f933d2b84ec6bdc9dcf119fd3657
+#: ../../templates.rst:222
+msgid "In the left navigation bar, click Templates."
+msgstr "在左侧的导航栏，点击模板。"
+
+# 8d360dd921b54190850f9eb8bcfd5832
+#: ../../templates.rst:224
+msgid "Click Register Template."
+msgstr "点击注册模板。"
+
+# 641dd9e5a6d24e33ba70513e4c194dde
+#: ../../templates.rst:226
+msgid "Provide the following:"
+msgstr "填写以下内容："
+
+# ee2439f863e4425a9b1d3eed40b451cb
+#: ../../templates.rst:228
+msgid ""
+"**Name and Description**. These will be shown in the UI, so choose something"
+" descriptive."
+msgstr "**名称和显示文本**。这些会在UI中显示，所以建议写一些描述信息。"
+
+# c521e0a0730348a88e0393d8c53e0fd8
+#: ../../templates.rst:231
+msgid ""
+"**URL**. The Management Server will download the file from the specified "
+"URL, such as ``http://my.web.server/filename.vhd.gz``."
+msgstr "**URL**。管理服务器会从指定的URL下载模板，就像 ``http://my.web.server/filename.vhd.gz``。"
+
+# 935dbff52fbc49e2bc3effdfe8343c7f
+#: ../../templates.rst:234
+msgid ""
+"**Zone**. Choose the zone where you want the template to be available, or "
+"All Zones to make it available throughout CloudStack."
+msgstr "**区域**:：选择你希望该模板在到哪个区域可用，或者选择所有区域使该模板在CloudStack中全部区域中可用。"
+
+# ef7a5cbcab564351b11799afe2f3221f
+#: ../../templates.rst:238
+msgid ""
+"**OS Type**: This helps CloudStack and the hypervisor perform certain "
+"operations and make assumptions that improve the performance of the guest. "
+"Select one of the following:"
+msgstr "**操作系统类型*:：这有助于CloudStack和Hypervisor执行某些操作并假设可提高来宾虚拟机的性能。选择下列之一。"
+
+# e179d642fb334f9fa4073821044a5116
+#: ../../templates.rst:247
+msgid ""
+"You should not choose an older version of the OS than the version in the "
+"image. For example, choosing CentOS 5.4 to support a CentOS 6.2 image will "
+"in general not work. In those cases you should choose Other."
+msgstr "你不能选择比镜像版本老的OS版本。比如，选择CentOS 5.4来支持CentOS 6.2镜像通常来说是不工作的。在这种情况下，你应该选择其他。"
+
+# 558b914220d948188698827bc674fa3a
+#: ../../templates.rst:252
+msgid ""
+"**Hypervisor**: The supported hypervisors are listed. Select the desired "
+"one."
+msgstr "**Hypervisor**：列表中显示支持的hypervisors。选择想要的一个。"
+
+# 362c6490da7e426ead7c28ef7bca2f3d
+#: ../../templates.rst:255
+msgid ""
+"**Format**. The format of the template upload file, such as VHD or OVA."
+msgstr "**格式**。上传的模板文件的格式，如VHD或OVA。"
+
+# 475796efd2dd4d64a7897d80ccf02191
+#: ../../templates.rst:262
+msgid ""
+"**Extractable**. Choose Yes if the template is available for extraction. If "
+"this option is selected, end users can download a full image of a template."
+msgstr "**可提取**。如果模板可以被提取请选择是。如果选择了此选项，终端用户可以下载此模板的完全镜。"
+
+# 7f676cb6f6844001ac5af17d480dd595
+#: ../../templates.rst:271
+msgid ""
+"**Featured**. Choose Yes if you would like this template to be more "
+"prominent for users to select. The template will appear in the Featured "
+"Templates list. Only an administrator can make a template Featured."
+msgstr "**精选**: 。如果你想这个用户在选择这个模板时更明显则选择Yes。该模板将出现在精选模板列表中。只有管理员可以设置模板为精选。"
+
+# 4f1b071c71184d61b1e20db9a1408381
+#: ../../templates.rst:278
+msgid "Exporting Templates"
+msgstr "导出模板"
+
+# 07e8cf807f6341c981fd8028383cae01
+#: ../../templates.rst:280
+msgid ""
+"End users and Administrators may export templates from the CloudStack. "
+"Navigate to the template in the UI and choose the Download function from the"
+" Actions menu."
+msgstr "最终用户和管理员可以从CloudStack导出模板。导航到用户界面中的模板并选择动作菜单中的下载功能。"
+
+# ff3b2f1a01194b86a94ca7406e2c9e4c
+#: ../../templates.rst:286
+msgid "Creating a Linux Template"
+msgstr "创建Linux模板"
+
+# 942a09f060a248499ad52006fb12910b
+#: ../../templates.rst:288
+msgid ""
+"Linux templates should be prepared using this documentation in order to "
+"prepare your linux VMs for template deployment. For ease of documentation, "
+"the VM which you are configuring the template on will be referred to as "
+"\"Template Master\". This guide currently covers legacy setups which do not "
+"take advantage of UserData and cloud-init and assumes openssh-server is "
+"installed during installation."
+msgstr "为了准备使用模板部署你的Linux VMs，可以使用此文档来准备Linux模板。对于文档中的情况，你要通过配置模板，这会涉及\"主模板\"。这个指导目前覆盖了传统的安装，但不会涉及用户数据和cloud-init还有假设在装过程中安装了openshh服务。"
+
+# c110f6248b3b4a56a32c3a3c42a213b0
+#: ../../templates.rst:295
+msgid "An overview of the procedure is as follow:"
+msgstr "过程概述如下："
+
+# fccf60393f704035b1c6fceaae12ea12
+#: ../../templates.rst:297
+msgid "Upload your Linux ISO."
+msgstr "上传你的Linux ISO。"
+
+# 0a498b0d37ad4ca29ed96268e032ca4f
+# a70aa21eac0643d2908840edc2bf61b8
+#: ../../templates.rst:299 ../../templates.rst:549
+msgid ""
+"For more information, see `“Adding an ISO” <virtual_machines.html#adding-an-"
+"iso>`_."
+msgstr "更多信息，请参阅 `“添加ISO” <virtual_machines.html#adding-an-iso>`_。"
+
+# a2c6ef939b3644e5a63b94756a7ef72e
+# 949a4ba056404bb29cc67697a1f50b33
+#: ../../templates.rst:302 ../../templates.rst:552
+msgid "Create a VM Instance with this ISO."
+msgstr "使用这个ISO创建VM实例。"
+
+# eb1605dc63014381b489c931a38377e3
+# 6cf1e105b8a542adb4ea1daf3718eb15
+#: ../../templates.rst:304 ../../templates.rst:554
+msgid ""
+"For more information, see `“Creating VMs” <virtual_machines.html#creating-"
+"vms>`_."
+msgstr "更多信息，请参阅 `“创建VMs” <virtual_machines.html#creating-vms>`_。"
+
+# 6e61739ba7024680bdf5d1c3a4fb8ddc
+#: ../../templates.rst:307
+msgid "Prepare the Linux VM"
+msgstr "准备Linux VM"
+
+# 86ecdc3984a446e69db7d31db4b0f355
+#: ../../templates.rst:309
+msgid "Create a template from the VM."
+msgstr "从VM创建模板。"
+
+# e865dcc3232e4f51972fe0f554d58eeb
+#: ../../templates.rst:311
+msgid ""
+"For more information, see `“Creating a Template from an Existing Virtual "
+"Machine” <#creating-a-template-from-an-existing-virtual-machine>`_."
+msgstr "更多信息，请参阅 `“从已有的虚拟机创建模板” <#creating-a-template-from-an-existing-virtual-machine>`_。"
+
+# dce1b0c69ea14188bf5d99e9aa364a4d
+#: ../../templates.rst:316
+msgid "System preparation for Linux"
+msgstr "Linux的系统准备工作"
+
+# 9d4c8a98ec1c466da2893fd12538e3ba
+#: ../../templates.rst:318
+msgid ""
+"The following steps will prepare a basic Linux installation for templating."
+msgstr "下列步骤将会为模板准备一个基本的Linux安装。"
+
+# 3de223a77c284109956a2eef988638db
+#: ../../templates.rst:321
+msgid "**Installation**"
+msgstr "**安装**"
+
+# 4f6808052a554f3cbb8697209cafc2de
+#: ../../templates.rst:323
+msgid ""
+"It is good practice to name your VM something generic during installation, "
+"this will ensure components such as LVM do not appear unique to a machine. "
+"It is recommended that the name of \"localhost\" is used for installation."
+msgstr "通常在安装过程中给VM命名是一个好的做法，这么做能确保某些组件如LVM不会只在一台机器中出现。推荐在在安装过程中使用\"localhost\"命名。"
+
+# ff8376cf4b4b40899df3911a0216a3f8
+#: ../../templates.rst:329
+msgid ""
+"For CentOS, it is necessary to take unique identification out of the "
+"interface configuration file, for this edit /etc/sysconfig/network-scripts"
+"/ifcfg-eth0 and change the content to the following."
+msgstr "对于CentOS，必须要修改网络接口的配置文件，在这里我们编辑/etc/sysconfig/network-scripts/ifcfg-eth0文件，更改下面的内容。"
+
+# f68b6e4efb764f92a1e56ad9ea54f90c
+#: ../../templates.rst:341
+msgid "The next steps updates the packages on the Template Master."
+msgstr "下一步更新主模板中的包。"
+
+# 143c241d86a44e32b496b66a9934ec6a
+# 4de01ffab6a44664b87eb62c32e550a4
+# 141d36e8817e444e94e29f6c889f76d9
+#: ../../templates.rst:343 ../../templates.rst:390 ../../templates.rst:446
+msgid "Ubuntu"
+msgstr "Ubuntu"
+
+# 7b51d3bdb3c2417486c37949b1978dab
+# a37b78dad81f45429074776c11add237
+#: ../../templates.rst:353 ../../templates.rst:453
+msgid "CentOS"
+msgstr "CentOS"
+
+# b6d69c72e22e4f40bd0d7d7bdaa1be7e
+#: ../../templates.rst:361
+msgid "**Password management**"
+msgstr "**密码管理**"
+
+# f71ab72462f5424fbc900751e054d736
+#: ../../templates.rst:364
+msgid ""
+"If preferred, custom users (such as ones created during the Ubuntu "
+"installation) should be removed. First ensure the root user account is "
+"enabled by giving it a password and then login as root to continue."
+msgstr "如果需要，客户(如在Ubuntu的安装过程中创建的用户)应该被移除。首先确认root用户账户是启用的并且使用了密码，然后使用root登录。"
+
+# ef5341894f7e40a4a9c300485f9f1367
+#: ../../templates.rst:373
+msgid ""
+"As root, remove any custom user accounts created during the installation "
+"process."
+msgstr "使用root，移除任何在安装过程中创建的自定义用户账户。"
+
+# a81798014288476da8e256abdea8526b
+#: ../../templates.rst:380
+msgid ""
+"See :ref:`adding-password-management-to-templates` for instructions to setup"
+" the password management script, this will allow CloudStack to change your "
+"root password from the web interface."
+msgstr "关于设置密码管理脚本的相关说明，请参阅 :ref:`adding-password-management-to-templates` ，这样能允许CloudStack通过web界面更改root密码。"
+
+# 9d00097815b24c0ca4034a304afee047
+#: ../../templates.rst:384
+msgid "**Hostname Management**"
+msgstr "**主机名管理**"
+
+# c41219c74c2b4b138cdfd88c986a2a02
+#: ../../templates.rst:386
+msgid ""
+"CentOS configures the hostname by default on boot. Unfortunately Ubuntu does"
+" not have this functionality, for Ubuntu installations use the following "
+"steps."
+msgstr "默认情况下CentOS在启动的时候配置主机名。但是，Ubuntu却没有此功能，对于Ubuntu，安装时使用下面步骤。"
+
+# ad9bf73797c24558b7e106dc2ce8510b
+#: ../../templates.rst:392
+msgid ""
+"The hostname of a Templated VM is set by a custom script in `/etc/dhcp"
+"/dhclient-exit-hooks.d`, this script first checks if the current hostname is"
+" localhost, if true, it will get the host-name, domain-name and fixed-ip "
+"from the DHCP lease file and use those values to set the hostname and append"
+" the `/etc/hosts` file for local hostname resolution. Once this script, or a"
+" user has changed the hostname from localhost, it will no longer adjust "
+"system files regardless of it's new hostname. The script also recreates "
+"openssh-server keys, which should have been deleted before templating (shown"
+" below). Save the following script to `/etc/dhcp/dhclient-exit-"
+"hooks.d/sethostname`, and adjust the permissions."
+msgstr "一个模板化的VM使用`/etc/dhcp/dhclient-exit-hooks.d`中的一个自定义脚本来设置主机名，这个脚本首先检查当前的主机名是是否是hostname，如果是，它将从DHCP租约文件获取host-name，domain-name和fix-ip，并且使用这些值来设置主机名并将其追加到 `/etc/hosts` 文件以用来本地主机名解析。一旦这个脚本或者一个用户从本地改变了主机名，那么它将不再根据新的主机名调整系统文件。此脚本同样也会重建openssh-server keys，这个keys在做模板(如下所示)之前被删除了。保存下面的脚本到`/etc/dhcp/dhclient-exit-hooks.d/sethostname`，并且调整权限。"
+
+# 1f68693847f1433bb6541b70f1abedd5
+#: ../../templates.rst:434
+msgid ""
+"The following steps should be run when you are ready to template your "
+"Template Master. If the Template Master is rebooted during these steps you "
+"will have to run all the steps again. At the end of this process the "
+"Template Master should be shutdown and the template created in order to "
+"create and deploy the final template."
+msgstr "当你准备好做你的主模板的时候请运行下列步骤。如果主模板在这些步骤期间重启了，那么你要重新运行所有的步骤。在这个过程的最后，主模板应该关机并且将其创建为模板，然后再部署。"
+
+# 79b32100447b4464a62f56cf91492a6c
+#: ../../templates.rst:440
+msgid "**Remove the udev persistent device rules**"
+msgstr "**移除udev持久设备规则**"
+
+# 7a1b5554792c4cb1aa676f8e73a843b8
+#: ../../templates.rst:442
+msgid ""
+"This step removes information unique to your Template Master such as network"
+" MAC addresses, lease files and CD block devices, the files are "
+"automatically generated on next boot."
+msgstr "这一步会移除你的主模板的特殊信息，如网络MAC地址，租约信息和CD块设备，这个文件会在下次启动时自动生成。"
+
+# 381e458992444a499e21908b7bf88a68
+#: ../../templates.rst:460
+msgid "**Remove SSH Keys**"
+msgstr "**移除SSH Keys**"
+
+# 9badfc5f4bfa454e8ca0d64a71a11c24
+#: ../../templates.rst:462
+msgid ""
+"This step is to ensure all your Templated VMs do not have the same SSH keys,"
+" which would decrease the security of the machines dramatically."
+msgstr "这步是为了确认所有要作为模板的VMs的SSH Keys都不相同，否则这样会降低虚拟机的安全性。"
+
+# 0d2aa14e20f04c3bb2bad70954a1291a
+#: ../../templates.rst:470
+msgid "**Cleaning log files**"
+msgstr "**清除日志文件**"
+
+# af913fb8f91b484bb83ac0737e1b1d10
+#: ../../templates.rst:472
+msgid "It is good practice to remove old logs from the Template Master."
+msgstr "从主模板移除旧的日志文件是一个好习惯。"
+
+# db125d8aa6cc45c8bdf9340dde1d3d45
+#: ../../templates.rst:481
+msgid "**Setting hostname**"
+msgstr "**设置主机名**"
+
+# 5a2162138fca40088196712b5650f551
+#: ../../templates.rst:483
+msgid ""
+"In order for the Ubuntu DHCP script to function and the CentOS dhclient to "
+"set the VM hostname they both require the Template Master's hostname to be "
+"\"localhost\", run the following commands to change the hostname."
+msgstr "为了Ubuntu DHCP的脚本功能和CentOS dhclient能设置VM主机名，他们都去要设置主模板的主机名设置为“localhost”，运行下面的命令来更改主机名。"
+
+# 3ed2b72c9128441ab39130f547642191
+#: ../../templates.rst:493
+msgid "**Set user password to expire**"
+msgstr "**设置用户密码期限**"
+
+# 10db50989ebe48c4a10ebdefa260c489
+#: ../../templates.rst:495
+msgid ""
+"This step forces the user to change the password of the VM after the "
+"template has been deployed."
+msgstr "这步是要在模板部署之后强制用户更改VM的密码。"
+
+# abe301956bd54c1c86c35fca1411ece6
+#: ../../templates.rst:502
+msgid "**Clearing User History**"
+msgstr "**清除用户历史**"
+
+# 9b6183972b934b91be6da40e93a1c12a
+#: ../../templates.rst:504
+msgid "The next step clears the bash commands you have just run."
+msgstr "下一步来清除你曾经运行过的bash命令。"
+
+# b8a76342290b46209f3bf8c468dc5cee
+#: ../../templates.rst:511
+msgid "**Shutdown the VM**"
+msgstr "**关闭VM**"
+
+# f92b1a930b3e4d859616309b9db518e1
+#: ../../templates.rst:513
+msgid "Your now ready to shutdown your Template Master and create a template!"
+msgstr "现在你可以关闭你的主模板并且创建模板了！"
+
+# 43e271d15b2742238d231b3f7fe85ed1
+#: ../../templates.rst:520
+msgid "**Create the template!**"
+msgstr "**创建模板！**"
+
+# 1db89306e7ae4b99b486fb9d7c783da4
+#: ../../templates.rst:522
+msgid ""
+"You are now ready to create the template, for more information see "
+"`“Creating a Template from an Existing Virtual Machine” <#creating-a"
+"-template-from-an-existing-virtual-machine>`_."
+msgstr "现在你可以创建模板了，更多信息请参阅 `“从已存在的虚拟机创建模板” <#creating-a-template-from-an-existing-virtual-machine>`_。"
+
+# 43f673483bbc490ca475ad5e0e1f1736
+#: ../../templates.rst:527
+msgid ""
+"Templated VMs for both Ubuntu and CentOS may require a reboot after "
+"provisioning in order to pickup the hostname."
+msgstr "通过Ubuntu和CentOS的模板分发的虚机可能需要重启才让主机名生效。"
+
+# 96fe0ca1217f4c6789bb7ef7bf304036
+#: ../../templates.rst:532
+msgid "Creating a Windows Template"
+msgstr "创建Windows模板"
+
+# dc56a5c13129464f9d23300535eedbcc
+#: ../../templates.rst:534
+msgid ""
+"Windows templates must be prepared with Sysprep before they can be "
+"provisioned on multiple machines. Sysprep allows you to create a generic "
+"Windows template and avoid any possible SID conflicts."
+msgstr "Windows模板在分发多个虚拟机的之前必须使用Sysprep初始化。Sysprep允许你创建一个通用的Windows模板和避免任何可能的SID冲突。"
+
+# fcbe31f9497c46618be1ae04f1c300d2
+#: ../../templates.rst:539
+msgid ""
+"(XenServer) Windows VMs running on XenServer require PV drivers, which may "
+"be provided in the template or added after the VM is created. The PV drivers"
+" are necessary for essential management functions such as mounting "
+"additional volumes and ISO images, live migration, and graceful shutdown."
+msgstr "(XenServer)XXenServer上运行的Windows VMs需要安装PV驱动，它可能在模板中或在创建完VM后添加。PV驱动对于基本的管理功能是必要的，比如挂载额外的卷和ISO镜像、在线迁移和正常关机。"
+
+# 6918a5f84f9e483484479aa24d4ec044
+#: ../../templates.rst:545
+msgid "An overview of the procedure is as follows:"
+msgstr "过程概述如下："
+
+# c48d96b9ff9d430780c7eefe88c19a2d
+#: ../../templates.rst:547
+msgid "Upload your Windows ISO."
+msgstr "上传你的Windows ISO。"
+
+# c29e3a4c4aec4418a525b07f70e30657
+#: ../../templates.rst:557
+msgid ""
+"Follow the steps in Sysprep for Windows Server 2008 R2 (below) or Sysprep "
+"for Windows Server 2003 R2, depending on your version of Windows Server"
+msgstr "按照你所使用的WIndows Server版本进行Windows Server 2008 R2(下面的)或者Windows Server 2003 R2中Sysprep的操作步骤。"
+
+# d526a7794b20490094eb4688b02c0a58
+#: ../../templates.rst:561
+msgid ""
+"The preparation steps are complete. Now you can actually create the template"
+" as described in Creating the Windows Template."
+msgstr "准本工作完成了。现在你可以按照创建Windows模板中描述的来创建模板。"
+
+# 9e309b24a2eb479e878115e7e5af8cd0
+#: ../../templates.rst:566
+msgid "System Preparation for Windows Server 2008 R2"
+msgstr "为Windows Server 2008 R2进行系统准备"
+
+# a195817082c4472ea5bb4e287b2b8718
+#: ../../templates.rst:568
+msgid ""
+"For Windows 2008 R2, you run Windows System Image Manager to create a custom"
+" sysprep response XML file. Windows System Image Manager is installed as "
+"part of the Windows Automated Installation Kit (AIK). Windows AIK can be "
+"downloaded from `Microsoft Download Center <http://www.microsoft.com/en-"
+"us/download/details.aspx?id=9085>`_."
+msgstr "对于Windows 2008 R2，你运行Windows系统镜像管理来创建一个自定义的sysprep应答XML文件。Windows系统镜像管理作为Windows Automated Installation Kit (AIK)的一部分安装在系统中。Windows AIK可以从 `微软下载中心 <http://www.microsoft.com/en-us/download/details.aspx?id=9085>`_下载到。"
+
+# 8add2ef3ee0741feb9b1575421ee590d
+#: ../../templates.rst:574
+msgid "Use the following steps to run sysprep for Windows 2008 R2:"
+msgstr "按照以下步骤运行Windows 2008 R2的sysprep："
+
+# 0e82209c29214738a91cd3233c54314c
+#: ../../templates.rst:577
+msgid ""
+"The steps outlined here are derived from the excellent guide by Charity "
+"Shelbourne, originally published at `Windows Server 2008 Sysprep Mini-Setup."
+" <http://blogs.technet.com/askcore/archive/2008/10/31/automating-the-oobe-"
+"process-during-windows-server-2008-sysprep-mini-setup.aspx>`_"
+msgstr "这些步骤的概述来源于Charity Shelbourne一个非常棒的指导，发布在 `Windows Server 2008 Sysprep Mini-Setup. <http://blogs.technet.com/askcore/archive/2008/10/31/automating-the-oobe-process-during-windows-server-2008-sysprep-mini-setup.aspx>`_。"
+
+# 9392d5c10c02447f82b7413a71b09128
+#: ../../templates.rst:582
+msgid "Download and install the Windows AIK"
+msgstr "下载和安装Windows AIK"
+
+# a4389660d8ad4d1b8c036e5a312acf49
+#: ../../templates.rst:585
+msgid ""
+"Windows AIK should not be installed on the Windows 2008 R2 VM you just "
+"created. Windows AIK should not be part of the template you create. It is "
+"only used to create the sysprep answer file."
+msgstr "刚刚创建的Windows 2008 R2上面并没有安装Windows AIK。Windows AIK不是你创建的模板中的一部分。它仅仅用于创建sysprep应答文件。"
+
+# b6b2049c23774943958f7539fc0624db
+#: ../../templates.rst:589
+msgid ""
+"Copy the install.wim file in the \\\\sources directory of the Windows 2008 "
+"R2 installation DVD to the hard disk. This is a very large file and may take"
+" a long time to copy. Windows AIK requires the WIM file to be writable."
+msgstr "在\\\\Windows 2008 R2安装DVD中的源目录复制install.wim文件到本地硬盘。这是一个非常大的文件可能会复制较长时间。Windows AIK要求WIM文件是可写的。"
+
+# 6a1367c35ec54816823cc2f821fb42c3
+#: ../../templates.rst:594
+msgid ""
+"Start the Windows System Image Manager, which is part of the Windows AIK."
+msgstr "打开Windows系统镜像管理器。"
+
+# 210d191e2b2540c6986358e0c0b9c87d
+#: ../../templates.rst:597
+msgid ""
+"In the Windows Image pane, right click the Select a Windows image or catalog"
+" file option to load the install.wim file you just copied."
+msgstr "在Windows镜像面板，右击选择一个Windows镜像或编录文件选项来读取你刚刚复制的install.wim文件。"
+
+# 2ae1354725354401b1c6774b56210b30
+#: ../../templates.rst:600
+msgid "Select the Windows 2008 R2 Edition."
+msgstr "选择Windows 2008 R2版本。"
+
+# a4139f632731431fa6c278ed49a402a3
+#: ../../templates.rst:602
+msgid ""
+"You may be prompted with a warning that the catalog file cannot be opened. "
+"Click Yes to create a new catalog file."
+msgstr "你可能会收到一个警告提示说不能打开编录文件。点击是来创建一个新的编录文件。"
+
+# 6daadc2945704fdbae1a77fab0ef5843
+#: ../../templates.rst:605
+msgid "In the Answer File pane, right click to create a new answer file."
+msgstr "在应答文件面板，右击来创建一个新的应答文件。"
+
+# 0d84d28c59424fc39b5a2f36f3dd6bfd
+#: ../../templates.rst:607
+msgid ""
+"Generate the answer file from the Windows System Image Manager using the "
+"following steps:"
+msgstr "使用以下步骤从Windows系统镜像管理器生成应答文件："
+
+# fed0398c42684441a6958c5be21f5c07
+#: ../../templates.rst:610
+msgid ""
+"The first page you need to automate is the Language and Country or Region "
+"Selection page. To automate this, expand Components in your Windows Image "
+"pane, right-click and add the Microsoft-Windows-International-Core setting "
+"to Pass 7 oobeSystem. In your Answer File pane, configure the InputLocale, "
+"SystemLocale, UILanguage, and UserLocale with the appropriate settings for "
+"your language and country or region. Should you have a question about any of"
+" these settings, you can right-click on the specific setting and select "
+"Help. This will open the appropriate CHM help file with more information, "
+"including examples on the setting you are attempting to configure."
+msgstr "第一个页面你必须让语言和国家或位置选择页面是自动的。要使这个自动化，请在你的Windows 镜像面板扩展组件，右击Microsoft-Windows-International-Core添加设置以传送 7 oobeSystem。在你的应答文件面板中，为语言和国家或位置用适当的设置配置InputLocale、SystemLocale、UILanguage、和UserLocale。你可能对这些设置有疑问，你可以指定一个设置右击选择帮助。这将打开对应的CHM帮助文件，这里面包括了与你尝试配置的设置相关的一些示例。"
+
+# e1b641ce1c5d42e0bc8e530c840f89c0
+#: ../../templates.rst:622
+msgid "|sysmanager.png|"
+msgstr "|sysmanager.png|"
+
+# fd41b3e0931141e5971248dfb811dc0a
+#: ../../templates.rst:624
+msgid ""
+"You need to automate the Software License Terms Selection page, otherwise "
+"known as the End-User License Agreement (EULA). To do this, expand the "
+"Microsoft-Windows-Shell-Setup component. High-light the OOBE setting, and "
+"add the setting to the Pass 7 oobeSystem. In Settings, set HideEULAPage "
+"true."
+msgstr "你需要将软件授权选择页配置为自动进行，这不是众所周知的EULA。为此，展开Microsoft-Windows-Shell-Setup组件，选中OOBE 设置，将此设置加入到Pass 7 oobeSystem中去。在设置中，将HideEULAPage 设置为true。"
+
+# 72f9459967ad49cdaebc5ac0cf7e0940
+#: ../../templates.rst:630
+msgid "|software-license.png|"
+msgstr "|software-license.png|"
+
+# d818473f321c4c2594fbc0d903e86837
+#: ../../templates.rst:632
+msgid ""
+"Make sure the license key is properly set. If you use MAK key, you can just "
+"enter the MAK key on the Windows 2008 R2 VM. You need not input the MAK into"
+" the Windows System Image Manager. If you use KMS host for activation you "
+"need not enter the Product Key. Details of Windows Volume Activation can be "
+"found at `http://technet.microsoft.com/en-us/library/bb892849.aspx "
+"<http://technet.microsoft.com/en-us/library/bb892849.aspx>`_"
+msgstr "确保恰当的设置了序列号。如果使用MAK的话，可以在Windows2008R2的虚拟机上输入MAK。并不需要将MAK输入到Windows映像管理器中。如果你使用KMS主机进行激活，则不需要输入产品序列号。Windows卷激活的详细信息可以在http://technet.microsoft.com/en-us/library/bb892849.aspx 上查看。"
+
+# 0941ea38dbb84c5ab3a37e64ff29e6d1
+#: ../../templates.rst:640
+msgid ""
+"You need to automate is the Change Administrator Password page. Expand the "
+"Microsoft-Windows-Shell-Setup component (if it is not still expanded), "
+"expand UserAccounts, right-click on AdministratorPassword, and add the "
+"setting to the Pass 7 oobeSystem configuration pass of your answer file. "
+"Under Settings, specify a password next to Value."
+msgstr "类似机械化的操作还有更改管理员密码页。展开Microsoft-Windows-Shell-Setup组件（如果没有展开的话），展开用户账户，右键点击管理员密码，添加设置到Pass 7 oobeSystem配置，在设置中，指定一个密码。"
+
+# 8092f90cf8784fc0bc8408b84b547e18
+#: ../../templates.rst:647
+msgid "|change-admin-password.png|"
+msgstr "|change-admin-password.png|"
+
+# e7e1281b1ae04398b43ab9c70d0f8370
+#: ../../templates.rst:649
+msgid ""
+"You may read the AIK documentation and set many more options that suit your "
+"deployment. The steps above are the minimum needed to make Windows "
+"unattended setup work."
+msgstr "可能会需要阅读AIK文档并设置多个选项来适合你的部署。以上的步骤至少需要使windows脱离建立网络的过程。"
+
+# 9461bfba70d24cebb27c1d65ea4bdcfa
+#: ../../templates.rst:653
+msgid ""
+"Save the answer file as unattend.xml. You can ignore the warning messages "
+"that appear in the validation window."
+msgstr "将答案文件保存为unattend.xml，可以忽略验证窗口中的警告信息。"
+
+# e03af6631f444bac834875feb1551d93
+#: ../../templates.rst:656
+msgid ""
+"Copy the unattend.xml file into the c:\\\\windows\\\\system32\\\\sysprep "
+"directory of the Windows 2008 R2 Virtual Machine"
+msgstr "将unattend.xml文件拷贝到Windows 2008 R2 虚拟机的c:\\\\windows\\\\system32\\\\sysprep 文件夹下，"
+
+# f25b60a2d1c64b00ab525ccb2ca1488e
+#: ../../templates.rst:659
+msgid ""
+"Once you place the unattend.xml file in c:\\\\windows\\\\system32\\\\sysprep"
+" directory, you run the sysprep tool as follows:"
+msgstr "一旦将unattend.xml文件放到 c:\\\\windows\\\\system32\\\\sysprep文件夹下，则按以下步骤运行sysprep工具："
+
+# c8ba22aeffd14733b20fd2ddadb189dd
+#: ../../templates.rst:668
+msgid ""
+"The Windows 2008 R2 VM will automatically shut down after sysprep is "
+"complete."
+msgstr "Windows 2008 R2虚拟机在sysprep完成后，会自动关闭。"
+
+# 8d4d691768fd4d2a9d131f80a0af05cc
+#: ../../templates.rst:673
+msgid "System Preparation for Windows Server 2003 R2"
+msgstr "针对Windows Server 2003R2的系统准备"
+
+# 25fcbd475b3842f69219e1db506c148d
+#: ../../templates.rst:675
+msgid ""
+"Earlier versions of Windows have a different sysprep tool. Follow these "
+"steps for Windows Server 2003 R2."
+msgstr "早期的windows版本有个不同的sysprep的工具，按照这些步骤准备Windows Server 2003 R2。"
+
+# e4b387caeb524e64b8e43a7256ad002b
+#: ../../templates.rst:678
+msgid ""
+"Extract the content of \\\\support\\\\tools\\\\deploy.cab on the Windows "
+"installation CD into a directory called c:\\\\sysprep on the Windows 2003 R2"
+" VM."
+msgstr "从Windows 安装CD中提取\\\\support\\\\tools\\\\deploy.cab到WIndows 2003 R2 虚拟机中的此目录 c:\\\\sysprep。"
+
+# 678e1857aae14091ad3954e190199112
+#: ../../templates.rst:682
+msgid "Run c:\\\\sysprep\\\\setupmgr.exe to create the sysprep.inf file."
+msgstr "运行 c:\\\\sysprep\\\\setupmgr.exe 来创建syprep.inf文件。"
+
+# eaaddf71b1e144ba9354ecdc3e61237f
+#: ../../templates.rst:684
+msgid "Select Create New to create a new Answer File."
+msgstr "选择创建新的来创建一个新的应答文件。"
+
+# 3a59447b097e4d6a8bbef6303be9c428
+#: ../../templates.rst:686
+msgid "Enter “Sysprep setup” for the Type of Setup."
+msgstr "安装的类型选择 “Sysprep 安装”"
+
+# 511f5fa4a9e04084a2344c13153944c3
+#: ../../templates.rst:688
+msgid "Select the appropriate OS version and edition."
+msgstr "选择合适的OS版本"
+
+# c36d76222fa14fe39dfdd33baf171555
+#: ../../templates.rst:690
+msgid ""
+"On the License Agreement screen, select “Yes fully automate the "
+"installation”."
+msgstr "在许可协议界面，选择\"是，完全自动安装\""
+
+# 42eac0aa963c4b138bba5785ecc4a9ab
+#: ../../templates.rst:693
+msgid "Provide your name and organization."
+msgstr "提供你的名称和组织。"
+
+# 923d7a62003b4bb28c6fdcec04988da5
+#: ../../templates.rst:695
+msgid "Leave display settings at default."
+msgstr "保留显示设置为默认。"
+
+# 28ff1531e0574780b26bbcdab535f18d
+#: ../../templates.rst:697
+msgid "Set the appropriate time zone."
+msgstr "设置合适的时区。"
+
+# c166a631d91d4ec5ba1fe55fb27e9071
+#: ../../templates.rst:699
+msgid "Provide your product key."
+msgstr "提供你的产品key。"
+
+# bb448a5c8bad409b910a983aafc7e7e5
+#: ../../templates.rst:701
+msgid "Select an appropriate license mode for your deployment"
+msgstr "给你的部署选择一个合适的许可模式。"
+
+# 5961b7acd3964ece89961a88ac1c9e49
+#: ../../templates.rst:703
+msgid "Select “Automatically generate computer name”."
+msgstr "选择\"自动生成计算机名\"。"
+
+# ee71045d980c48c3b4229992144775db
+#: ../../templates.rst:705
+msgid ""
+"Type a default administrator password. If you enable the password reset "
+"feature, the users will not actually use this password. This password will "
+"be reset by the instance manager after the guest boots up."
+msgstr "输入一个默认的管理员密码。如果你启用了密码重置功能，用户实际上将不会使用这个密码。在来宾虚机启动之后实例管理器会重置密码。"
+
+# 662f974f66a84b258158cc6d888d31ff
+#: ../../templates.rst:710
+msgid "Leave Network Components at “Typical Settings”."
+msgstr "网络组件使用\"典型设置\"。"
+
+# b382f00fffc54d2092dea46275ce07e0
+#: ../../templates.rst:712
+msgid "Select the “WORKGROUP” option."
+msgstr "选择“WORKGROUP”选项。"
+
+# 864a8297271a4b9c9310a8e580d93f85
+#: ../../templates.rst:714
+msgid "Leave Telephony options at default."
+msgstr "电话服务使用默认。"
+
+# f9104d77ee794b999a52c430bde6f5e0
+#: ../../templates.rst:716
+msgid "Select appropriate Regional Settings."
+msgstr "选择合适的区域设置。"
+
+# 7a038c948aee40caad5fdbd408680a4e
+#: ../../templates.rst:718
+msgid "Select appropriate language settings."
+msgstr "选择合适的语言选项。"
+
+# 8fe7a793a4b149fc8b2c04b222bb95ff
+#: ../../templates.rst:720
+msgid "Do not install printers."
+msgstr "不要安装打印机。"
+
+# 0bd5cf14d63149e8a68370eb7b35c1b5
+#: ../../templates.rst:722
+msgid "Do not specify “Run Once commands”."
+msgstr "不要指定\"运行一次\"。"
+
+# 05694b63059140748f90c4a339c83a2e
+#: ../../templates.rst:724
+msgid "You need not specify an identification string."
+msgstr "你不必指定标示字符串。"
+
+# a48d1b90a9bc405daa8af11e577a21dc
+#: ../../templates.rst:726
+msgid "Save the Answer File as c:\\\\sysprep\\\\sysprep.inf."
+msgstr "将应答文件保存到c:\\\\sysprep\\\\sysprep.inf。"
+
+# a2f33c40df224c318576f392e89a029e
+#: ../../templates.rst:728
+msgid "Run the following command to sysprep the image:"
+msgstr "运行以下命令行来sysprep镜像："
+
+# 47370d15208e44779af8dc395473c3ab
+#: ../../templates.rst:734
+msgid "After this step the machine will automatically shut down"
+msgstr "在这个步骤之后，虚拟机会自动关机。"
+
+# 6a05bb80ea29400084b33d565fcc1600
+#: ../../templates.rst:738
+msgid "Importing Amazon Machine Images"
+msgstr "导入Amazon Machine Images"
+
+# eaa1897518c8471ca61593a7b64fd3e2
+#: ../../templates.rst:740
+msgid ""
+"The following procedures describe how to import an Amazon Machine Image "
+"(AMI) into CloudStack when using the XenServer hypervisor."
+msgstr "以下过程描述了当使用XenServer hypervisor时，如何导入一个AMI到Cloudstack中。"
+
+# f83727180aee4a54aa1735df061a32d3
+#: ../../templates.rst:743
+msgid ""
+"Assume you have an AMI file and this file is called CentOS\\_6.2\\_x64. "
+"Assume further that you are working on a CentOS host. If the AMI is a Fedora"
+" image, you need to be working on a Fedora host initially."
+msgstr "假定你有一个叫做CentOS\\_6.2|_x64的AMI文件。假定未来你将工作在CentOS主机上。如果AMI是一个Fedora镜像，你需要将它立即安装到Fedora主机上。"
+
+# d52c5657eb014680ba5dcb4cd793964b
+#: ../../templates.rst:747
+msgid ""
+"You need to have a XenServer host with a file-based storage repository "
+"(either a local ext3 SR or an NFS SR) to convert to a VHD once the image "
+"file has been customized on the Centos/Fedora host."
+msgstr "一旦镜像文件在CentOS/Fedora主机上自定义完毕，你必须有一台使用文件存储库(本地ext3 SR或者NFS SP)的XenServer主机将其转换VHD。"
+
+# c6369502d5ec442bba824ba9ebd3399f
+#: ../../templates.rst:752
+msgid ""
+"When copying and pasting a command, be sure the command has pasted as a "
+"single line before executing. Some document viewers may introduce unwanted "
+"line breaks in copied text."
+msgstr "当复制和粘贴命令时，请确保没有多余的换行符，因为一些文档查看器可能会在复制时加上换行符。"
+
+# b12f0319181043b6ace0737e16ca933e
+#: ../../templates.rst:756
+msgid "To import an AMI:"
+msgstr "导入一个AMI:"
+
+# 516bca51c4054cb9a0a7c70f455cfb50
+#: ../../templates.rst:758
+msgid "Set up loopback on image file:"
+msgstr "建立在镜像文件上的回滚"
+
+# c40cb6ea1f3a41dbbdfca02adc87b77a
+#: ../../templates.rst:765
+msgid ""
+"Install the kernel-xen package into the image. This downloads the PV kernel "
+"and ramdisk to the image."
+msgstr "安装kernel-xen包到镜像文件中。下载PV内核和ramdisk到镜像中。"
+
+# 0cf205e0b1214bfd85b81840483a7e11
+#: ../../templates.rst:772
+msgid "Create a grub entry in /boot/grub/grub.conf."
+msgstr "在 /boot/grub/grub.conf中创建一个引导。"
+
+# ea05e45228434e6eb41f8d92afdcb402
+#: ../../templates.rst:780
+msgid ""
+"Determine the name of the PV kernel that has been installed into the image."
+msgstr "终止已经安装到镜像文件中的PV内核名称"
+
+# 3395c5bd2c424bf08e6b7c6e789b89b8
+#: ../../templates.rst:793
+msgid ""
+"Xen kernels/ramdisk always end with \"xen\". For the kernel version you "
+"choose, there has to be an entry for that version under lib/modules, there "
+"has to be an initrd and vmlinuz corresponding to that. Above, the only "
+"kernel that satisfies this condition is 2.6.18-164.15.1.el5xen."
+msgstr "Xen的kernels/ramdisk通常以“xen\"结尾。在lib/modules中选择相应的内核版本，intrd和vmlinuz将作出相应的反应.综上，唯一要求的条件是版本为2.6.18-164.15.1.el5xen。"
+
+# cd3138f8605141a1a0ef5f9ae345c8cc
+#: ../../templates.rst:799
+msgid ""
+"Based on your findings, create an entry in the grub.conf file. Below is an "
+"example entry."
+msgstr "根据你要找的内容，在grub.conf文件中创建一个入口。以下为入口例子。"
+
+# 82b126faf726428faa043e59b48fab5c
+#: ../../templates.rst:812
+msgid ""
+"Edit etc/fstab, changing “sda1” to “xvda” and changing “sdb” to “xvdb”."
+msgstr "编辑 etc/fstab,将”sda1“改为”xvda\"并将“sdb\"改为”xbdb\"."
+
+# 158d080ac2c845c089c610cf10e51f6e
+#: ../../templates.rst:824
+msgid ""
+"Enable login via the console. The default console device in a XenServer "
+"system is xvc0. Ensure that etc/inittab and etc/securetty have the following"
+" lines respectively:"
+msgstr "通过终端开启登陆。在默认终端设备XenServer系统上的是xvc0.确定在etc/inittab和etc/securetty中有以下各自的行："
+
+# 78c0483458064433a5dcf14ba528eb3e
+#: ../../templates.rst:835
+msgid ""
+"Ensure the ramdisk supports PV disk and PV network. Customize this for the "
+"kernel version you have determined above."
+msgstr "确保虚拟盘支持PV磁盘和PV网络。为你之前选择好的kernel版本自定义这些。"
+
+# c5985961045c4177b2d3d8f684fbd61b
+#: ../../templates.rst:845
+msgid "Change the password."
+msgstr "修改密码"
+
+# a26809b7f44741e898c17da609bbd7fd
+#: ../../templates.rst:855
+msgid "Exit out of chroot."
+msgstr "退出chroot"
+
+# 3fc6a7c5bbaf414da8d8a91f9f2e1056
+#: ../../templates.rst:861
+msgid ""
+"Check `etc/ssh/sshd_config` for lines allowing ssh login using a password."
+msgstr "检查 `etc/ssh/sshd_config`中关于允许在ssh登录时使用密码的相关行。"
+
+# 664c645f17104a9689c80c1722a33864
+#: ../../templates.rst:870
+msgid ""
+"If you need the template to be enabled to reset passwords from the "
+"CloudStack UI or API, install the password change script into the image at "
+"this point. See :ref:`adding-password-management-to-templates`."
+msgstr "如果你需要通过CloudStack· UI或API启用重置模板的密码功能，在镜像中安装密码更改脚本。相关内容请参考:ref:`adding-password-management-to-templates`。"
+
+# a4f18c75d1074dd2b110ac78ffe5265f
+#: ../../templates.rst:874
+msgid "Unmount and delete loopback mount."
+msgstr "卸载或删除loopback挂载。"
+
+# 8edfb6c75d614771b3b350cbc348a938
+#: ../../templates.rst:881
+msgid ""
+"Copy the image file to your XenServer host's file-based storage repository. "
+"In the example below, the Xenserver is \"xenhost\". This XenServer has an "
+"NFS repository whose uuid is a9c5b8c8-536b-a193-a6dc-51af3e5ff799."
+msgstr "复制镜像文件到XenServer主机的文件存储库。在下面的例子中，XenServer是\"xenhost\"。这个XenServer有一个UUID为a9c5b8c8-536b-a193-a6dc-51af3e5ff799的NFS库。"
+
+# 0dc1d9510e784714bcdec1384e8755f1
+#: ../../templates.rst:890
+msgid "Log in to the Xenserver and create a VDI the same size as the image."
+msgstr "登录到XenServer然后创建一个与镜像同样大小的VDI。"
+
+# 4e8f8e659e434bc5a3f36dc2fd9f822d
+#: ../../templates.rst:900
+msgid "Import the image file into the VDI. This may take 10–20 minutes."
+msgstr "将镜像导入到VDI中。这可能会花费10-20分钟。"
+
+# 0b58122603704ebda3d2342ee6515ff7
+#: ../../templates.rst:906
+msgid ""
+"Locate a the VHD file. This is the file with the VDI’s UUID as its name. "
+"Compress it and upload it to your web server."
+msgstr "找到这个VHD文件。它的名字是以VDI的UUID命名的。压缩并上床至你的web服务器。"
+
+# 7691e9d11b8b49d29aec196fe6cb380c
+#: ../../templates.rst:916
+msgid "Converting a Hyper-V VM to a Template"
+msgstr "将Hyper-V的VM转换为模板"
+
+# 3edfac90ab644da58894eab904cc447c
+#: ../../templates.rst:918
+msgid ""
+"To convert a Hyper-V VM to a XenServer-compatible CloudStack template, you "
+"will need a standalone XenServer host with an attached NFS VHD SR. Use "
+"whatever XenServer version you are using with CloudStack, but use XenCenter "
+"5.6 FP1 or SP2 (it is backwards compatible to 5.6). Additionally, it may "
+"help to have an attached NFS ISO SR."
+msgstr "要转换Hyper-V的VM到兼容XenServer的CloudStack模板，你需要一个独立的添加了NFS VHD SR的XenServer主机。无论使用CloudStack管理哪个版本XenServer，但必须是XenCenter 5.6 FP1或SP2(它向下兼容5.6)。另外，添加了NFS ISO SR是有帮助的。"
+
+# b65f920f7aa24af9b850a9b006b20069
+#: ../../templates.rst:924
+msgid ""
+"For Linux VMs, you may need to do some preparation in Hyper-V before trying "
+"to get the VM to work in XenServer. Clone the VM and work on the clone if "
+"you still want to use the VM in Hyper-V. Uninstall Hyper-V Integration "
+"Components and check for any references to device names in /etc/fstab:"
+msgstr "对于Linux VMs，在尝试让VM在XenServer中工作之前你可能必须在Hyper-V做一些准备工作。如果你仍然想要在Hyper-V中使用这个VM的话，克隆这个VM然后在克隆的虚机上操作。卸载Hyper-V集成组件然后检查任何/etc/fstab中涉及的相关设备名称："
+
+# 163cf95a7ec7444d8308e6f3915b94f7
+#: ../../templates.rst:930
+msgid ""
+"From the linux\\_ic/drivers/dist directory, run make uninstall (where "
+"\"linux\\_ic\" is the path to the copied Hyper-V Integration Components "
+"files)."
+msgstr "从 linux\\_ic/drivers/dist 目录中，运行make uninstall(\"linux\\_ic\" 是复制的Hyper-V集成组件的路径)。"
+
+# 32eb47eefa0b4af493237f82dd0f08e1
+#: ../../templates.rst:934
+msgid ""
+"Restore the original initrd from backup in /boot/ (the backup is named "
+"\\*.backup0)."
+msgstr "从备份/boot/ 恢复原始的文件系统(备份名称为 \\*.backup0)。"
+
+# b7363d0658ff4efcb9bdf4657296d185
+#: ../../templates.rst:937
+msgid "Remove the \"hdX=noprobe\" entries from /boot/grub/menu.lst."
+msgstr "从 /boot/grub/menu.lst移除 \"hdX=noprobe\" 。"
+
+# f8878c3d06ea47b0b8c1cfaf1721f34b
+#: ../../templates.rst:939
+msgid ""
+"Check /etc/fstab for any partitions mounted by device name. Change those "
+"entries (if any) to mount by LABEL or UUID. You can get that information "
+"with the blkid command."
+msgstr "通过名称从 /etc/fstab中检查任何挂载的分区。将这些条目(如果有)改成使用LABEL或者UUID挂载。你能通过 blkid命令获得这些信息。"
+
+# 685ac8156ffb427f853074d04df8be85
+#: ../../templates.rst:943
+msgid ""
+"The next step is make sure the VM is not running in Hyper-V, then get the "
+"VHD into XenServer. There are two options for doing this."
+msgstr "下一步请确保Hyper-V中的这个VM没有运行，然后把VHD送至XenServer。有两个选择。"
+
+# 2a0e0f2e121b4d30bb10710db99fd9cb
+#: ../../templates.rst:946
+msgid "Option one:"
+msgstr "选项一："
+
+# 7006009b5d4d452d9a3936d365133d47
+#: ../../templates.rst:948
+msgid ""
+"Import the VHD using XenCenter. In XenCenter, go to Tools>Virtual Appliance "
+"Tools>Disk Image Import."
+msgstr "使用XenCenter导入VHD。在XenCenter中，找到Tools>Virtual Appliance Tools>Disk Image Import。"
+
+# 0b382531327d4323aa4983bacc4ed07f
+# d535d0d741a64664bf63603df9967f1f
+#: ../../templates.rst:951 ../../templates.rst:963
+msgid "Choose the VHD, then click Next."
+msgstr "选择VHD，然后点击下一步。"
+
+# 2a052e079f674601944c0ba73a344456
+#: ../../templates.rst:953
+msgid ""
+"Name the VM, choose the NFS VHD SR under Storage, enable \"Run Operating "
+"System Fixups\" and choose the NFS ISO SR."
+msgstr "给VM起个名字，在Storage下选择 NFS VHD SR，启用\"Run Operating System Fixups\" 然后选择NFS ISO SR。"
+
+# cc2978604a5d4e41bc9bf810c2d56de3
+#: ../../templates.rst:956
+msgid "Click Next, then Finish. A VM should be created."
+msgstr "点击下一步 完成。完成虚拟机创建。"
+
+# 67a0e0a79a8a4361a4a7a54ce0f7d4bb
+#: ../../templates.rst:958
+msgid "Option two:"
+msgstr "选项二："
+
+# 30a1d3fd83154d909f816cbdb7f05e1e
+#: ../../templates.rst:960
+msgid ""
+"Run XenConvert, under From choose VHD, under To choose XenServer. Click "
+"Next."
+msgstr "运行 XenConvert ,选择 VHD,选择 XenServer,点击下一步。"
+
+# a00bf9e6d260466fbec3fa0226669cdb
+#: ../../templates.rst:965
+msgid "Input the XenServer host info, then click Next."
+msgstr "输入XenServer主机信息，点击下一步。"
+
+# 44711d8c01324ee79a30d8ce8b327a78
+#: ../../templates.rst:967
+msgid "Name the VM, then click Next, then Convert. A VM should be created."
+msgstr "输入VM名称，点击“下一步”，点击“转换”。VM应该就创建了。"
+
+# 92901943e7874fb1a3d951cd238e0711
+#: ../../templates.rst:969
+msgid ""
+"Once you have a VM created from the Hyper-V VHD, prepare it using the "
+"following steps:"
+msgstr "一旦你完成从hyper-v VHD到虚拟机的创建，准备使用以下步骤："
+
+# 86356c840f4d4588a591dc27d244bfca
+#: ../../templates.rst:972
+msgid "Boot the VM, uninstall Hyper-V Integration Services, and reboot."
+msgstr "启动虚拟机，卸载Hyper-V集成服务，并重新启动。"
+
+# b7695ac5e06a43afb682c51148ea61a2
+#: ../../templates.rst:974
+msgid "Install XenServer Tools, then reboot."
+msgstr "安装XenServer Tools，然后重新启动。"
+
+# 35c3a56ed699450c91f45bdba9627f4c
+#: ../../templates.rst:976
+msgid ""
+"Prepare the VM as desired. For example, run sysprep on Windows VMs. See "
+"`“Creating a Windows Template” <#creating-a-windows-template>`_."
+msgstr "按需要准备VM。例如在Windows VM上执行sysprep。请参阅 `“创建Windows模板” <#creating-a-windows-template>`_。"
+
+# 35897d5ecf6144a88204cb836ee76084
+#: ../../templates.rst:980
+msgid ""
+"Either option above will create a VM in HVM mode. This is fine for Windows "
+"VMs, but Linux VMs may not perform optimally. Converting a Linux VM to PV "
+"mode will require additional steps and will vary by distribution."
+msgstr "以上任一选项将在HVM模式下创建一个VM。对于Windows虚拟机来说这是很好的，但Linux的虚拟机可能无法达到最佳性能。要转换Linux虚拟机到PV模式，对于不同的发行版本将需要额外的步骤。"
+
+# e4c0e0e192034e3b9e9439d79eae9bb3
+#: ../../templates.rst:985
+msgid ""
+"Shut down the VM and copy the VHD from the NFS storage to a web server; for "
+"example, mount the NFS share on the web server and copy it, or from the "
+"XenServer host use sftp or scp to upload it to the web server."
+msgstr "关闭虚拟机，从NFS存储拷贝VHD到一个web服务器；比如，在web服务器上挂载NFS共享然后拷贝它，或者是在XenServer主机上用sftp或scp将VHD上传到web服务器。"
+
+# 96fa0ff0b9e842af9381d561f9534955
+#: ../../templates.rst:990
+msgid "In CloudStack, create a new template using the following values:"
+msgstr "在 CloudStack中，使用以下值创建一个新的模板："
+
+# 713fe06958f947ecb69e69b7d6b4d85e
+#: ../../templates.rst:992
+msgid "URL. Give the URL for the VHD"
+msgstr "URL。给VHD指定URL。"
+
+# 4af6eb652e6744cca4ac135718ee31e2
+#: ../../templates.rst:994
+msgid ""
+"OS Type. Use the appropriate OS. For PV mode on CentOS, choose Other PV "
+"(32-bit) or Other PV (64-bit). This choice is available only for XenServer."
+msgstr "OS类型。使用适当的OS。对于CentOS的PV模式来说，选择其他PV (32位)或其他PV(64位)。这个选项仅适用于XenServer。"
+
+# 2d17699c6d72457e94c849e9369be071
+#: ../../templates.rst:998
+msgid "Hypervisor. XenServer"
+msgstr "Hypervisor。XenServer"
+
+# 0fe80c0299054980a5b04cae8c3a89c4
+#: ../../templates.rst:1000
+msgid "Format. VHD"
+msgstr "格式。VHD"
+
+# 0a2022d596764dda94ee0b8c61a7b8f6
+#: ../../templates.rst:1002
+msgid "The template will be created, and you can create instances from it."
+msgstr "模板就创建好了，然后你可以通过它创建实例。"
+
+# 4a48b7a200f84177bc4c2935b3cb7020
+#: ../../templates.rst:1008
+msgid "Adding Password Management to Your Templates"
+msgstr "给你的模板添加密码管理"
+
+# c24c604a1aa648859c9853bd23207c13
+#: ../../templates.rst:1010
+msgid ""
+"CloudStack provides an optional password reset feature that allows users to "
+"set a temporary admin or root password as well as reset the existing admin "
+"or root password from the CloudStack UI."
+msgstr "CloudStack提供了可选的密码重置功能，该功能允许用户在CloudStack UI上设置临时的admin或root密码，也可以重置现有的admin或root密码。"
+
+# 217ddf1185f5412999996969e470b02e
+#: ../../templates.rst:1014
+msgid ""
+"To enable the Reset Password feature, you will need to download an "
+"additional script to patch your template. When you later upload the template"
+" into CloudStack, you can specify whether reset admin/root password feature "
+"should be enabled for this template."
+msgstr "为启用密码重置功能，您需要下载额外的脚本到模版上。当您之后在CloudStack中添加模版时，您可以指定该模版是否启用重置admin或root密码的功能。"
+
+# bed2001bd6fd4768808ffe617fb80007
+#: ../../templates.rst:1019
+msgid ""
+"The password management feature works always resets the account password on "
+"instance boot. The script does an HTTP call to the virtual router to "
+"retrieve the account password that should be set. As long as the virtual "
+"router is accessible the guest will have access to the account password that"
+" should be used. When the user requests a password reset the management "
+"server generates and sends a new password to the virtual router for the "
+"account. Thus an instance reboot is necessary to effect any password "
+"changes."
+msgstr "密码管理功能总是在虚机启动时重置账号的密码。该脚本通过对虚拟路由器的HTTP调用，获取需要重置的账号密码。启动时，只要虚拟路由器可以访问，虚机就可以获得应该设置的账号密码。当用户请求密码重置时，管理服务器会生成新密码，并发送到虚拟路由器。因而，虚机需要重启新密码才能生效。"
+
+# 6294578d1b274e62ad53e3b5b90dba5e
+#: ../../templates.rst:1028
+msgid ""
+"If the script is unable to contact the virtual router during instance boot "
+"it will not set the password but boot will continue normally."
+msgstr "在虚机重启时，如果脚本不能连接到虚拟路由器，则密码不会被重置，但启动过程还会继续正常执行。"
+
+# 19d468fa67b84dc4ad8a85a6c367545c
+#: ../../templates.rst:1033
+msgid "Linux OS Installation"
+msgstr "Linux系统安装"
+
+# 8dafc3143daa4624ac256c0d1deebdb3
+#: ../../templates.rst:1035
+msgid "Use the following steps to begin the Linux OS installation:"
+msgstr "使用一下步骤开始Linux系统的安装："
+
+# 4cc0194e2b4049d186735606a395ff0c
+#: ../../templates.rst:1037
+msgid "Download the script file cloud-set-guest-password:"
+msgstr "下载cloud-set-guest-password脚本文件："
+
+# 7dfc38f9a99c4d0bbb5007329350693e
+#: ../../templates.rst:1039
+msgid ""
+"`http://download.cloud.com/templates/4.2/bindir/cloud-set-guest-password.in "
+"<http://download.cloud.com/templates/4.2/bindir/cloud-set-guest-"
+"password.in>`_"
+msgstr "`http://download.cloud.com/templates/4.2/bindir/cloud-set-guest-password.in <http://download.cloud.com/templates/4.2/bindir/cloud-set-guest-password.in>`_"
+
+# 6eead5e6602446c78f65d37e092b049f
+#: ../../templates.rst:1042
+msgid "Copy this file to /etc/init.d."
+msgstr "拷贝本文件到 /etc/init.d 。"
+
+# 2819cf0c972f4042931c612b737e8f1d
+#: ../../templates.rst:1044
+msgid "On some Linux distributions, copy the file to ``/etc/rc.d/init.d``."
+msgstr "在某些linux发行版拷贝此文件到 ``/etc/rc.d/init.d``。"
+
+# f914b404aef44aa1a7fbc43160c833b3
+#: ../../templates.rst:1046
+msgid "Run the following command to make the script executable:"
+msgstr "执行以下命令使脚本可执行："
+
+# ae8119d7538749fb95c1ce6ac6541c59
+#: ../../templates.rst:1052
+msgid ""
+"Depending on the Linux distribution, continue with the appropriate step."
+msgstr "根据不同的Linux发行版，选择适当的步骤继续。"
+
+# c85e239054a542e88bb0030af7cb7a19
+#: ../../templates.rst:1055
+msgid "On Fedora, CentOS/RHEL, and Debian, run:"
+msgstr "在Fedora,CentOS/RHEL和Debian上运行："
+
+# e83101bd5fd3442f817ec22d010edc3e
+#: ../../templates.rst:1063
+msgid "Windows OS Installation"
+msgstr "Windows OS 安装"
+
+# c40beb0a6d5c466c994729dba2d4b12e
+#: ../../templates.rst:1065
+msgid ""
+"Download the installer, CloudInstanceManager.msi, from the `Download page "
+"<http://sourceforge.net/projects/cloudstack/files/Password%20Management%20Scripts/CloudInstanceManager.msi/download>`_"
+" and run the installer in the newly created Windows VM."
+msgstr "从`下载页<http://sourceforge.net/projects/cloudstack/files/Password%20Management%20Scripts/CloudInstanceManager.msi/download>`_ 下载安装程序CloudInstanceManager.msi，并在新创建的Windows 虚拟机中运行安装程序。"
+
+# 56df3bfa3de0447b9f0a0b4f02a1fb4c
+#: ../../templates.rst:1071
+msgid "Deleting Templates"
+msgstr "删除模板"
+
+# 2d005d50f15746f793e20a2343fe6e29
+#: ../../templates.rst:1073
+msgid ""
+"Templates may be deleted. In general, when a template spans multiple Zones, "
+"only the copy that is selected for deletion will be deleted; the same "
+"template in other Zones will not be deleted. The provided CentOS template is"
+" an exception to this. If the provided CentOS template is deleted, it will "
+"be deleted from all Zones."
+msgstr "模板可以被删除。在一般情况下，当一个模板跨越多个区域，只有被选中的副本才会被删除，在其他区域相同的模板将不会被删除。CentOS的模板是一个例外。如果所提供的CentOS的模板被删除，它从所有区域都将被删除。"
+
+# 4ddffe7d5d2b4f14814054eea2d8fd47
+#: ../../templates.rst:1079
+msgid ""
+"When templates are deleted, the VMs instantiated from them will continue to "
+"run. However, new VMs cannot be created based on the deleted template."
+msgstr "当删除模板时，从它们中产生的虚拟机实例将继续运行。然而，新的虚拟机不能在被删除模板的基础上创建。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/troubleshooting.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/troubleshooting.mo
new file mode 100644
index 0000000..e0f7201
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/troubleshooting.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/troubleshooting.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/troubleshooting.po
new file mode 100644
index 0000000..cd464f7
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/troubleshooting.po
@@ -0,0 +1,497 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:04+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 453abc0964244620ab303e8bbdd16340
+#: ../../troubleshooting.rst:18
+msgid "TroubleShooting"
+msgstr "故障排查"
+
+# b90eea0457d64f3cb90be7deabcaa0c3
+#: ../../troubleshooting.rst:21
+msgid "Working with Server Logs"
+msgstr "使用服务器日志"
+
+# 9d89b655688d4af2bfc8302c8a0c9134
+#: ../../troubleshooting.rst:23
+msgid ""
+"The CloudStack Management Server logs all web site, middle tier, and "
+"database activities for diagnostics purposes in "
+"`/var/log/cloudstack/management/`. The CloudStack logs a variety of error "
+"messages. We recommend this command to find the problematic output in the "
+"Management Server log:."
+msgstr "为了方便诊断系统，CloudStack 管理服务器在目录/var/log/cloud/management/下记录了所有网站、中间层和数据库的活动。CloudStack 会记录各种出错信息。我们推荐使用下述命令从管理服务器日志中寻找有问题的输出日志："
+
+# 3fc8e92bb3a741c3bd3a67d67cf0e9a3
+#: ../../troubleshooting.rst:30
+msgid ""
+"When copying and pasting a command, be sure the command has pasted as a "
+"single line before executing. Some document viewers may introduce unwanted "
+"line breaks in copied text."
+msgstr "当复制和粘贴命令时，请确保没有多余的换行符，因为一些文档查看器可能会在复制时加上换行符。"
+
+# 845cfc971cf84bbca9edce162a942ad2
+#: ../../troubleshooting.rst:38
+msgid ""
+"The CloudStack processes requests with a Job ID. If you find an error in the"
+" logs and you are interested in debugging the issue you can grep for this "
+"job ID in the management server log. For example, suppose that you find the "
+"following ERROR message:"
+msgstr "CloudStack处理请求时会生成一个任务ID。如果您发现了日志中的某个错误，然后想调试该问题，您可以在管理服务器日志中grep这个任务ID。例如，假设您发现了以下的ERROR信息："
+
+# f7529d9ff27a4e27bdad7d8a6435087a
+#: ../../troubleshooting.rst:47
+msgid ""
+"Note that the job ID is 1076. You can track back the events relating to job "
+"1076 with the following grep:"
+msgstr "注意到任务ID是1076。你可以追踪返回事件的相近任务1076按照以下grep:"
+
+# 4da5450950cc43b79b6d4391e28f4f41
+#: ../../troubleshooting.rst:54
+msgid ""
+"The CloudStack Agent Server logs its activities in "
+"`/var/log/cloudstack/agent/`."
+msgstr "CloudStack代理服务器在 `/var/log/cloudstack/agent/`记录了它的活动。"
+
+# ba4670a0c5444406a2eb230cb99333d5
+#: ../../troubleshooting.rst:58
+msgid "Data Loss on Exported Primary Storage"
+msgstr "在导出主存储时的数据丢失"
+
+# b0ef204b69a54f32bd49070c4b9b6a91
+# 96d811275eea4240af38ec923db3c739
+# 03085fe48e6f4b379bcb1b827fff32d4
+# 83a83346af6342ae960e60c796e896d3
+# dc69c8f4922e4f69a378d3a16a609df7
+# 3970143e5afb4c03a4b3aed0f9e50fc7
+#: ../../troubleshooting.rst:61 ../../troubleshooting.rst:99
+#: ../../troubleshooting.rst:140 ../../troubleshooting.rst:162
+#: ../../troubleshooting.rst:185 ../../troubleshooting.rst:219
+msgid "Symptom"
+msgstr "症状"
+
+# a5727b8982354aaeb9aaa3eaccf41ef9
+#: ../../troubleshooting.rst:63
+msgid ""
+"Loss of existing data on primary storage which has been exposed as a Linux "
+"NFS server export on an iSCSI volume."
+msgstr "主存储的已有数据丢失。该主存储是用iSCSI卷导出的一个Linux NFS服务器输出。"
+
+# 77646ea81e804cb9ada6c17c6289cbbe
+# e5b68ba31d5948388069cf4e01357332
+# 48d47c0902414b5194a1d38398971eb6
+# 8c13e9a8446c49ef90ae29a314ee0d33
+# 8a80e812487d4bf6b38f6cdc6feddae0
+# 350e1aaa22b5432f8065bdf94cc27e02
+#: ../../troubleshooting.rst:68 ../../troubleshooting.rst:106
+#: ../../troubleshooting.rst:146 ../../troubleshooting.rst:168
+#: ../../troubleshooting.rst:197 ../../troubleshooting.rst:226
+msgid "Cause"
+msgstr "原因"
+
+# 8ca868ba6d9349e6b0d83564a152f19e
+#: ../../troubleshooting.rst:70
+msgid ""
+"It is possible that a client from outside the intended pool has mounted the "
+"storage. When this occurs, the LVM is wiped and all data in the volume is "
+"lost"
+msgstr "可能的原因是存储池之外的某个客户端挂载了该存储。如果发生了这种情况，LVM会被擦除，该卷上的所有数据都会丢失。"
+
+# 4934510ae4ce4c79a0ed5d6ee26fea0a
+# df9bd94f2f95481f93b741b643baedfb
+# 5d33b8b45f404f25abcb9d3fbfeafb70
+# 044a6cc8e613432ab218a02d3bbde2a1
+# 4445e221c952428fb2585060c4540dee
+# 7c3b4d63c42d4990999e96195fe72cca
+#: ../../troubleshooting.rst:76 ../../troubleshooting.rst:112
+#: ../../troubleshooting.rst:153 ../../troubleshooting.rst:176
+#: ../../troubleshooting.rst:207 ../../troubleshooting.rst:235
+msgid "Solution"
+msgstr "解决方案"
+
+# 990ebb2f5e854a479d94d06df1280a15
+#: ../../troubleshooting.rst:78
+msgid ""
+"When setting up LUN exports, restrict the range of IP addresses that are "
+"allowed access by specifying a subnet mask. For example:"
+msgstr "配置LUN输出时，通过指定子网掩码来限制可以访问存储的IP地址范围。例如："
+
+# 17f9dff87a0b4b848b2938ad46c42bfc
+#: ../../troubleshooting.rst:85
+msgid "Adjust the above command to suit your deployment needs."
+msgstr "根据你的部署需求，调整如上参数。"
+
+# 9dd74bb044b640dcb1b4e410db1a44e2
+#: ../../troubleshooting.rst:89
+msgid "More Information"
+msgstr "更多信息"
+
+# 6c10365641b54f549e84579ccb8d4fe2
+#: ../../troubleshooting.rst:91
+msgid ""
+"See the export procedure in the \"Secondary Storage\" section of the "
+"CloudStack Installation Guide"
+msgstr "请参考CloudStack安装指南的“辅助存储”章节中的导出过程。"
+
+# 08ecc200c09045599e0c1f960186fdc4
+#: ../../troubleshooting.rst:96
+msgid "Recovering a Lost Virtual Router"
+msgstr "恢复丢失的虚拟路由器"
+
+# db28bc81f196417980c31fd2d4b63f29
+#: ../../troubleshooting.rst:101
+msgid ""
+"A virtual router is running, but the host is disconnected. A virtual router "
+"no longer functions as expected."
+msgstr "虚拟路由器是运行着的，但主机失去连接。虚拟路由器不再按期望工作。"
+
+# a6ac53ae9be44b4e8b3602647222e9ac
+#: ../../troubleshooting.rst:108
+msgid "The Virtual router is lost or down."
+msgstr "虚拟路由器丢失或宕机。"
+
+# 1bd58bc5e2314d0cbf2e0059b096bf0a
+#: ../../troubleshooting.rst:114
+msgid ""
+"If you are sure that a virtual router is down forever, or no longer "
+"functions as expected, destroy it. You must create one afresh while keeping "
+"the backup router up and running (it is assumed this is in a redundant "
+"router setup):"
+msgstr "如果您确定虚拟路由器宕机了，或不再正常工作，请销毁它。您必须再建一个新的，此时备份路由器应保持运行(假定在使用冗余路由器配置的情况下)。"
+
+# 19e8516bc79a4b7faeb2645670f3a6a1
+#: ../../troubleshooting.rst:119
+msgid ""
+"Force stop the router. Use the stopRouter API with forced=true parameter to "
+"do so."
+msgstr "强制停止虚拟路由器。请使用带参数forced=true的stopRouter API执行该步。"
+
+# 340f24e153484784bc1cf3b493c32ea3
+#: ../../troubleshooting.rst:122
+msgid ""
+"Before you continue with destroying this router, ensure that the backup "
+"router is running. Otherwise the network connection will be lost."
+msgstr "在销毁虚拟路由器之前，请确保备份路由器正常运行。否则用户的网络连接将中断。"
+
+# c2db1e8bd10547bfacb3e2d044ca6d06
+#: ../../troubleshooting.rst:126
+msgid "Destroy the router by using the destroyRouter API."
+msgstr "使用destroyRouter API销毁该虚拟路由器。"
+
+# af3e07ca34034b49b6dba68eb7da16f3
+#: ../../troubleshooting.rst:128
+msgid ""
+"Recreate the missing router by using the restartNetwork API with "
+"cleanup=false parameter. For more information about redundant router setup, "
+"see Creating a New Network Offering."
+msgstr "使用restartNetwork API（参数cleanup=false）重建丢失的虚拟路由器。关于冗余虚拟路由器的配置，请参考创建新的网络方案。"
+
+# 25bdb5c7a6a7454ea25d62c3f0a02c57
+#: ../../troubleshooting.rst:132
+msgid ""
+"For more information about the API syntax, see the API Reference at "
+"`http://cloudstack.apache.org/docs/api/ "
+"<http://cloudstack.apache.org/docs/api/>`_."
+msgstr "关于更多的API语法信息，参见API参考`http://cloudstack.apache.org/docs/api/ <http://cloudstack.apache.org/docs/api/>`_。"
+
+# d1a32a2023024c72907911b8c7757cae
+#: ../../troubleshooting.rst:137
+msgid "Maintenance mode not working on vCenter"
+msgstr "维护模式没在vCenter中生效"
+
+# bd6813f30ddc4a0da8cf13b7725c9748
+#: ../../troubleshooting.rst:142
+msgid ""
+"Host was placed in maintenance mode, but still appears live in vCenter."
+msgstr "主机已经置为维护模式，但在vCenter中还是活动的。"
+
+# 7241c889dd0842189f0c38eda241d14b
+#: ../../troubleshooting.rst:148
+msgid ""
+"The CloudStack administrator UI was used to place the host in scheduled "
+"maintenance mode. This mode is separate from vCenter's maintenance mode."
+msgstr "CloudStack管理员用户界面使用日程中的主机维护模式。该模式与vCenter的维护模式无关。"
+
+# a959d82ede064a89ad631ce910f8f7df
+#: ../../troubleshooting.rst:155
+msgid "Use vCenter to place the host in maintenance mode."
+msgstr "请使用vCenter将主机置为维护模式。"
+
+# f3c4a03f0b5042009b2e858d5b259496
+#: ../../troubleshooting.rst:159
+msgid "Unable to deploy VMs from uploaded vSphere template"
+msgstr "无法从上传的vSphere模板部署虚拟机"
+
+# f0d6310e9be647eda1506c7161d33a8b
+#: ../../troubleshooting.rst:164
+msgid "When attempting to create a VM, the VM will not deploy."
+msgstr "当试图创建一个虚拟机，虚拟机将无法部署。"
+
+# 82efe5f025f8468c99e720b0e00c067e
+#: ../../troubleshooting.rst:170
+msgid ""
+"If the template was created by uploading an OVA file that was created using "
+"vSphere Client, it is possible the OVA contained an ISO image. If it does, "
+"the deployment of VMs from the template will fail."
+msgstr "如果模板通过上传OVA文件创建，而OVA文件是使用vSphere Client创建的，可能OVA中包含ISO镜像。如果是的话，从模板部署虚拟机将失败。"
+
+# c61b5fec4b5d4b75afac37386a78b766
+#: ../../troubleshooting.rst:178
+msgid "Remove the ISO and re-upload the template."
+msgstr "移除ISO并重新上传模板。"
+
+# 7d4b56be6f504129860c6d5c12fd73d5
+#: ../../troubleshooting.rst:182
+msgid "Unable to power on virtual machine on VMware"
+msgstr "无法启动VMware的虚机"
+
+# bb0c46e2f09647f9a260c9e676f72afb
+#: ../../troubleshooting.rst:187
+msgid "Virtual machine does not power on. You might see errors like:"
+msgstr "虚机不能启动。可能出现以下错误："
+
+# 92c768be206b4267bb993ce6b1b74d77
+#: ../../troubleshooting.rst:189
+msgid "Unable to open Swap File"
+msgstr "不能打开交换文件"
+
+# a63cf9eda829479b835aff2d3b017460
+#: ../../troubleshooting.rst:191
+msgid "Unable to access a file since it is locked"
+msgstr "不能访问文件，因为文件被锁定"
+
+# 0deea4202b4b41d9a4fab5ae3dad09bf
+#: ../../troubleshooting.rst:193
+msgid "Unable to access Virtual machine configuration"
+msgstr "不能访问虚机配置"
+
+# 0605d083a0fa4569ad92e3ea1cfe6634
+#: ../../troubleshooting.rst:199
+msgid ""
+"A known issue on VMware machines. ESX hosts lock certain critical virtual "
+"machine files and file systems to prevent concurrent changes. Sometimes the "
+"files are not unlocked when the virtual machine is powered off. When a "
+"virtual machine attempts to power on, it can not access these critical "
+"files, and the virtual machine is unable to power on."
+msgstr "这是VMware机器的已知问题。为防止并发修改，ESX主机会锁定特定的关键虚机文件和文件系统。有时，虚机关机时没有解锁这些文件。当虚机再次开机时，由于不能访问这些关键文件，虚机就不能启动。"
+
+# 177329a9571d49b5bce7dc8d84731724
+#: ../../troubleshooting.rst:209
+msgid "See the following:"
+msgstr "参见："
+
+# 344210667a0d414a89c35ba8bce56ca0
+#: ../../troubleshooting.rst:211
+msgid ""
+"`VMware Knowledge Base Article "
+"<http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=10051/>`_"
+msgstr "`VMware Knowledge Base Article <http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=10051/>`_"
+
+# 7e82b8b3093b42cfb1088af2632abacf
+#: ../../troubleshooting.rst:216
+msgid "Load balancer rules fail after changing network offering"
+msgstr "改变网络方案后负载均衡规则失效"
+
+# 8feb8c6245fb490d835881b4996a3504
+#: ../../troubleshooting.rst:221
+msgid ""
+"After changing the network offering on a network, load balancer rules stop "
+"working."
+msgstr "修改网络的网络方案后，负载均衡规则不再生效。"
+
+# dea9609b31dc4131b77505535e3aca09
+#: ../../troubleshooting.rst:228
+msgid ""
+"Load balancing rules were created while using a network service offering "
+"that includes an external load balancer device such as NetScaler, and later "
+"the network service offering changed to one that uses the CloudStack virtual"
+" router."
+msgstr "负载均衡规则创建时使用的是包含外部负载均衡器，例如NetScaler的网络方案，后来改为使用CloudStack虚拟路由器的网络方案。"
+
+# e344e7e16a5145ee9dfeb6c9057e6cb6
+#: ../../troubleshooting.rst:237
+msgid ""
+"Create a firewall rule on the virtual router for each of your existing load "
+"balancing rules so that they continue to function."
+msgstr "针对每条已有的负载均衡规则，在虚拟路由器上创建相同的防火墙规则，以便规则继续生效。"
+
+# 8bc5100986b347c1a08bbeb52b64f7f7
+#: ../../troubleshooting.rst:242
+msgid "Troubleshooting Internet Traffic"
+msgstr "故障排查网络传输"
+
+# 5f383b9190f34ebcbdd6bb92b713ee21
+#: ../../troubleshooting.rst:244
+msgid ""
+"Below are a few troubleshooting steps to check whats going wrong with your "
+"network..."
+msgstr "在下列故障排查步骤中检验你网络中出现的故障..."
+
+# 07599df9fe734016810667b0edbc9a49
+#: ../../troubleshooting.rst:249
+msgid "Trouble Shooting Steps"
+msgstr "故障排查步骤"
+
+# 1a82d41b488b46c2bef892a561b3756c
+#: ../../troubleshooting.rst:251
+msgid ""
+"The switches have to be configured correctly to pass VLAN traffic. You can "
+"verify if VLAN traffic is working by bringing up a tagged interface on the "
+"hosts and pinging between them as below..."
+msgstr "交换机上可以完成正确的配置VLAN通信。你可以辨别主机上的VLAN是否通讯通过提出标记接口，并在上述两个VLAN中使用ping命令。"
+
+# 6b44f2f662ed49199d66820be6f6de02
+#: ../../troubleshooting.rst:255
+msgid "On *host1 (kvm1)*"
+msgstr "在*host1 (kvm1)*上"
+
+# 5120295551574a56817a504f54bfe602
+#: ../../troubleshooting.rst:263
+msgid "On *host2 (kvm2)*"
+msgstr "在*host2 (kvm2)*上"
+
+# 417a511656394e62ab6533726322a54e
+#: ../../troubleshooting.rst:271
+msgid ""
+"If the pings dont work, run *tcpdump(8)* all over the place to check who is "
+"gobbling up the packets. Ultimately, if the switches are not configured "
+"correctly, CloudStack networking wont work so fix the physical networking "
+"issues before you proceed to the next steps"
+msgstr "如果ping不通，运行 *tcpdump(8)*在所有VLAN上检查丢失的数据包。最终，如果交换机配置失败，CloudStack网络将无法工作，所以在处理下一部前要确定物理网络设备的问题。"
+
+# 63be4a452fb043e1ad03834e2b6afc37
+#: ../../troubleshooting.rst:276
+msgid ""
+"Ensure `Traffic Labels <http://cloudstack.apache.org/docs/en-"
+"US/Apache_CloudStack/4.2.0/html/Installation_Guide/about-physical-"
+"networks.html>`_ are set for the Zone."
+msgstr "确保 `流量标签 <http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/about-physical-networks.html>`_ 已经设置在域中。 "
+
+# 997b8cf202374996adfbc66cf272e85d
+#: ../../troubleshooting.rst:278
+msgid ""
+"Traffic labels need to be set for all hypervisors including XenServer, KVM "
+"and VMware types. You can configure traffic labels when you creating a new "
+"zone from the *Add Zone Wizard*."
+msgstr "流量标签需要在包括XenServer，KVM和VMwarel在内的所有类型的hypervisors设置。当你从*Add Zone Wizard*创建一个域时，你可以配置流量标签。"
+
+# 7f2757fe05a54b7890d5b634724bd166
+#: ../../troubleshooting.rst:284
+msgid ""
+"On an existing zone, you can modify the traffic labels by going to "
+"*Infrastructure, Zones, Physical Network* tab."
+msgstr "在一个已经存在的域总，你可以通过*Add Zone Wizard*修改流量标签。"
+
+# de6b7290f1874731bab19679f2b1c123
+#: ../../troubleshooting.rst:289
+msgid "List labels using *CloudMonkey*"
+msgstr "列出正在使用的*CloudMonkey*"
+
+# d7be5d89abc2416a81c2e11ae80e5c5e
+#: ../../troubleshooting.rst:321
+msgid ""
+"KVM traffic labels require to be named as *\"cloudbr0\"*, *\"cloudbr2\"*, "
+"*\"cloudbrN\"* etc and the corresponding bridge must exist on the KVM hosts."
+" If you create labels/bridges with any other names, CloudStack (atleast "
+"earlier versions did) seems to ignore them. CloudStack does not create the "
+"physical bridges on the KVM hosts, you need to create them **before** before"
+" adding the host to Cloudstack."
+msgstr "KVM流量标签要求被命名为*\"cloudbr0\"*, *\"cloudbr2\"*, *\"cloudbrN\"* 等而且响应桥必须在KVM主机上。如果你以其他名字命名标记/桥，CloudStack(至少是较早版本)将会忽略它。CloudStack不能再KVM主机上创建物理桥，你需要在向CloudStackt添加主机前 **before**创建它们。"
+
+# 4d5d185d16bb4379b29d90b15b9e9855
+#: ../../troubleshooting.rst:340
+msgid ""
+"The Virtual Router, SSVM, CPVM *public* interface would be bridged to a "
+"physical interface on the host. In the example below, *cloudbr0* is the "
+"public interface and CloudStack has correctly created the virtual interfaces"
+" bridge. This virtual interface to physical interface mapping is done "
+"automatically by CloudStack using the traffic label settings for the Zone. "
+"If you have provided correct settings and still dont have a working working "
+"Internet, check the switching layer before you debug any further. You can "
+"verify traffic using tcpdump on the virtual, physical and bridge interfaces."
+msgstr "虚拟路由，SSVM,CPVM *public*接口将被桥接到主机的物理接口上。在下例中， *cloudbr0*是公共接口，CloudStack将创建虚拟接口桥。这个虚拟接口到物理接口映射式CloudStack用设置在域中的流量标签自动设置的。如果你提供争取的设置，但仍不能在网络上工作，在下一步调试前检查下交换层的设备。你可以在虚拟，物理和桥设备上使用tcpdump证实流量。"
+
+# f261f43d727440edbeaf4c36ca611f7c
+#: ../../troubleshooting.rst:372
+msgid ""
+"Pre-create labels on the XenServer Hosts. Similar to KVM bridge setup, "
+"traffic labels must also be pre-created on the XenServer hosts before adding"
+" them to CloudStack."
+msgstr "在XenServer上预先创建标签。类似于KVM桥启动，流量标签必须在加入CloudStack的XenServer主机上提前创建。"
+
+# e75bf706d6a745c9a94ee34516e86d1f
+#: ../../troubleshooting.rst:385
+msgid ""
+"The Internet would be accessible from both the SSVM and CPVM instances by "
+"default. Their public IPs will also be directly pingable from the Internet. "
+"Please note that these test would work only if your switches and traffic "
+"labels are configured correctly for your environment. If your SSVM/CPVM cant"
+" reach the Internet, its very unlikely that the Virtual Router (VR) can also"
+" the reach the Internet suggesting that its either a switching issue or "
+"incorrectly assigned traffic labels. Fix the SSVM/CPVM issues before you "
+"debug VR issues."
+msgstr "网络将会从SSVM和CPVM实例上默认获取。它们的公共IP也将会直接由网络ping通。请注意一下这些测试仅在交换机或者流量标签已被成功配置在你的环境中实现。如果你的 SSVM/CPVM可以连接到Internet, 它非常不同于虚拟路由器(VR)也可以连接到Internet,建议可能是交换时的问题或者是错误分配了流量标签。确定SSVM/CPVM的问题前请先调试VR问题。"
+
+# c1f11bc2b9ea470382b5f863e8d1a146
+#: ../../troubleshooting.rst:417
+msgid ""
+"The Virtual Router (VR) should also be able to reach the Internet without "
+"having any Egress rules. The Egress rules only control forwarded traffic and"
+" not traffic that originates on the VR itself."
+msgstr "除非有些Egress规则，Virtual Router(VR)也是不能到达Internet。Egress规则仅控制VR自身的通讯与否。"
+
+# fd961e75e43d4c48a4b779ef136e1d12
+#: ../../troubleshooting.rst:432
+msgid ""
+"However, the Virtual Router's (VR) Source NAT Public IP address **WONT** be "
+"reachable until appropriate Ingress rules are in place. You can add "
+"*Ingress* rules under *Network, Guest Network, IP Address, Firewall* setting"
+" page."
+msgstr "尽管如此，Virtual Router(VR) Source NAT Pulic IP地址除非有近似的Ingress规则在此，要么**WONT** 达到。你可以添加 *Ingress* rules under *Network, Guest Network, IP Address, Firewall* 设置页。"
+
+# 7a1ba3d03cd64a0cb60486d361453ebd
+#: ../../troubleshooting.rst:439
+msgid ""
+"The VM Instances by default wont be able to access the Internet. Add Egress "
+"rules to permit traffic."
+msgstr "默认的VM Instances不能够连接Internet。添加Egress规则后可允许连接。"
+
+# 2d798a14dcd149af8197080268c1b12b
+#: ../../troubleshooting.rst:444
+msgid ""
+"Some users have reported that flushing IPTables rules (or changing routes) "
+"on the SSVM, CPVM or the Virtual Router makes the Internet work. This is not"
+" expected behaviour and suggests that your networking settings are "
+"incorrect. No IPtables/route changes are required on the SSVM, CPVM or the "
+"VR. Go back and double check all your settings."
+msgstr "一些用户报告在SSVM，CPVM或者是Vir Router刷新IPTables规则(或改变路由)可以使Internet工作。这不是系统期望的行为并建议这样的网络设置是错误的。SSVM,CPVM或者是VR上没有要求IPtables/route改变。回去重新检查你所有的设置吧。"
+
+# e14dab36e181467a9fd09fb6d0283176
+#: ../../troubleshooting.rst:451
+msgid ""
+"In a vast majority of the cases, the problem has turned out to be at the "
+"switching layer where the L3 switches were configured incorrectly."
+msgstr "在海量的实例中，问题会出现在交换层，原因是L3的配置错误."
+
+# 5fff1dc7083a4412a9e4051f2e239180
+#: ../../troubleshooting.rst:454
+msgid ""
+"This section was contibuted by Shanker Balan and was originally published on"
+" `Shapeblue's blog <http://shankerbalan.net/blog/internet-not-working-on-"
+"cloudstack-vms/>`_"
+msgstr "这些内容有Shanker Balan贡献，其原文发布在`Shapeblue'博客中<http://shankerbalan.net/blog/internet-not-working-on-cloudstack-vms/>`_"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/tuning.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/tuning.mo
new file mode 100644
index 0000000..feb3327
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/tuning.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/tuning.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/tuning.po
new file mode 100644
index 0000000..209b1a2
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/tuning.po
@@ -0,0 +1,165 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:04+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 0c7c82c60c1c4ce4b2ec9838cc883b84
+#: ../../tuning.rst:18
+msgid "Tuning"
+msgstr "调优"
+
+# 9a2a025467014e929276cfa1e9e73e71
+#: ../../tuning.rst:20
+msgid ""
+"This section provides tips on how to improve the performance of your cloud."
+msgstr "本节提示如何提高云性能。"
+
+# 9b00143dbb7b4b4b97baab2aa95815aa
+#: ../../tuning.rst:25
+msgid "Performance Monitoring"
+msgstr "性能监控"
+
+# 43c6615bb7084bc58dbf0561984e39f3
+#: ../../tuning.rst:27
+msgid ""
+"Host and guest performance monitoring is available to end users and "
+"administrators. This allows the user to monitor their utilization of "
+"resources and determine when it is appropriate to choose a more powerful "
+"service offering or larger disk."
+msgstr "终端用户和管理员都能使用宿主机和虚拟机的性能监控。性能监控将允许用户监控他们的资源利用并且帮助用户决定何时将需要选择一个更高性能的服务或者更大的硬盘。"
+
+# 470932b76e664973b7568b285a10a77d
+#: ../../tuning.rst:34
+msgid "Increase Management Server Maximum Memory"
+msgstr "增加管理服务器到最大内存"
+
+# 82b1560c6fbf421b952de1c8424aa4a2
+#: ../../tuning.rst:36
+msgid ""
+"If the Management Server is subject to high demand, the default maximum JVM "
+"memory allocation can be insufficient. To increase the memory:"
+msgstr "如果管理服务器用于高需求，默认JVM的最大内存分配可能不足。增加内存:"
+
+# 1b69cb03d370442f913397dde140c37c
+#: ../../tuning.rst:39
+msgid "Edit the Tomcat configuration file:"
+msgstr "编辑Tomcat配置文件："
+
+# d9a022a48b8a4076872b335db29f658c
+#: ../../tuning.rst:45
+msgid "Change the command-line parameter -XmxNNNm to a higher value of N."
+msgstr "改变命令行参数 -XmxNNNm中的N为更高的值。"
+
+# bf5935dc78264c1baf8cd4984a631b98
+#: ../../tuning.rst:47
+msgid ""
+"For example, if the current value is -Xmx128m, change it to -Xmx1024m or "
+"higher."
+msgstr "例如，如果当前值为 -Xmx128m，则改为 -Xmx1024m或更高。"
+
+# e4dda8bcace04b10a404493586f871a1
+#: ../../tuning.rst:50
+msgid "To put the new setting into effect, restart the Management Server."
+msgstr "将新的设置生效，重启管理服务。"
+
+# 4b11c5fd61d0469480f110a7ebe528d0
+#: ../../tuning.rst:56
+msgid ""
+"For more information about memory issues, see \"FAQ: Memory\" at `Tomcat "
+"Wiki. <http://wiki.apache.org/tomcat/FAQ/Memory>`_"
+msgstr "欲了解更多管理内存问题的详细信息，请参阅\"FAQ:内存\" 在 `Tomcat Wiki. <http://wiki.apache.org/tomcat/FAQ/Memory>`_"
+
+# 588f5981eb3843ac91a1041e9f3bb832
+#: ../../tuning.rst:61
+msgid "Set Database Buffer Pool Size"
+msgstr "设置数据库缓冲池大小"
+
+# 2a1e327a1aa04838bfefce6674d9ec3e
+#: ../../tuning.rst:63
+msgid ""
+"It is important to provide enough memory space for the MySQL database to "
+"cache data and indexes:"
+msgstr "为MySQL数据库提供足够的内存空间来缓存数据和索引是很重要的："
+
+# 55bafed06cb5401fba6713f86660fe74
+#: ../../tuning.rst:66
+msgid "Edit the MySQL configuration file:"
+msgstr "编辑MySQL配置文件："
+
+# a2719920b1ad4f2388c10ed8f19e5437
+#: ../../tuning.rst:72
+msgid ""
+"Insert the following line in the [mysqld] section, below the datadir line. "
+"Use a value that is appropriate for your situation. We recommend setting the"
+" buffer pool at 40% of RAM if MySQL is on the same server as the management "
+"server or 70% of RAM if MySQL has a dedicated server. The following example "
+"assumes a dedicated server with 1024M of RAM."
+msgstr "在 [mysqld]部分的datadir下面插入如下行。使用适合您情况的值。如果MySQL和管理服务器在同一台服务器上面我们建议设置缓冲池为内存的40%，如果MySQL为专用的服务器我们建议设置为内存的70%。下面的示例假设一台专用的服务器的内存为1024M。"
+
+# 30d79aae5ff745b789f7e402c61d4164
+#: ../../tuning.rst:83
+msgid "Restart the MySQL service."
+msgstr "重启MySQL服务."
+
+# b12c7032e74b411d9d9c7bc32a92a3ab
+#: ../../tuning.rst:89
+msgid ""
+"For more information about the buffer pool, see \"The InnoDB Buffer Pool\" "
+"at `MySQL Reference Manual <http://dev.mysql.com/doc/refman/5.5/en/innodb-"
+"buffer-pool.html>`_."
+msgstr "欲了解更多关于缓冲池的信息，请参阅\"InnoDB缓冲池\" `MySQL参考手册<http://dev.mysql.com/doc/refman/5.5/en/innodb-buffer-pool.html>`_."
+
+# 1cbfe60313d445848eb5e90f708b55a1
+#: ../../tuning.rst:95
+msgid "Set and Monitor Total VM Limits per Host"
+msgstr "设置和监控每个主机的总VM数限制"
+
+# 36520c7bbf2b4888813341615ca176fa
+#: ../../tuning.rst:97
+msgid ""
+"The CloudStack administrator should monitor the total number of VM instances"
+" in each cluster, and disable allocation to the cluster if the total is "
+"approaching the maximum that the hypervisor can handle. Be sure to leave a "
+"safety margin to allow for the possibility of one or more hosts failing, "
+"which would increase the VM load on the other hosts as the VMs are "
+"automatically redeployed. Consult the documentation for your chosen "
+"hypervisor to find the maximum permitted number of VMs per host, then use "
+"CloudStack global configuration settings to set this as the default limit. "
+"Monitor the VM activity in each cluster at all times. Keep the total number "
+"of VMs below a safe level that allows for the occasional host failure. For "
+"example, if there are N hosts in the cluster, and you want to allow for one "
+"host in the cluster to be down at any given time, the total number of VM "
+"instances you can permit in the cluster is at most (N-1) \\* (per-host-"
+"limit). Once a cluster reaches this number of VMs, use the CloudStack UI to "
+"disable allocation of more VMs to the cluster."
+msgstr "管理员应该监视每个集群中的虚拟机实例的总数，如果总量快达到hypervisor允许的最大虚拟机数量时，不再向此群集分配虚拟机。并且，要注意为主机预留一定的计算能力，以防止群集中有主机发生故障,因为发生故障的主机上的虚拟机需要重新部署在这些预留主机上。请咨询您所选择hypervisor的文档，了解此hypervisor能支持的最大虚拟机数量，并将此数值设置在CloudStack的全局设置里。监控每个群集里虚拟机的活跃程序，并将活跃虚拟机保持在一个安全线内。这样，CloudStack就能允许偶尔的主机故障。举个示例：如果集群里有N个主机，而你只能让其中任一主机的停机时间不超过特定时间。那么，你能在此集群部署的最多虚拟主机数量值为：(N-1) \\* (每主机最大虚拟量数量限值)。一旦群集中的虚拟机达到此数量，必须在CloudStack的用户界面中禁止向此群集分配新的虚拟机。"
+
+# 87fad0d347f845e4b589cf1b70bfaad0
+#: ../../tuning.rst:116
+msgid "Configure XenServer dom0 Memory"
+msgstr "配置XenServer dom0内存"
+
+# e6d8fead31da4d2880407fe308a0c13a
+#: ../../tuning.rst:118
+msgid ""
+"Configure the XenServer dom0 settings to allocate more memory to dom0. This "
+"can enable XenServer to handle larger numbers of virtual machines. We "
+"recommend 2940 MB of RAM for XenServer dom0. For instructions on how to do "
+"this, see `Citrix Knowledgebase Article "
+"<http://support.citrix.com/article/CTX126531>`_.The article refers to "
+"XenServer 5.6, but the same information applies to XenServer 6"
+msgstr "配置XenServer为dom0分配更多的内存，可使XenServer处理更多的虚拟机。我们推荐为dom0设置的内存数值为2940 MB。至于如何操作，可以参阅如下URL： `Citrix 知识库文章 <http://support.citrix.com/article/CTX126531>`_.。这篇文章同时适用于XenServer 5.6和6.0版本。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/ui.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/ui.mo
new file mode 100644
index 0000000..c8eb976
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/ui.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/ui.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/ui.po
new file mode 100644
index 0000000..e68420d
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/ui.po
@@ -0,0 +1,265 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:04+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 823af79fce60474780309ce761b8cbb3
+#: ../../ui.rst:18
+msgid "User Interface"
+msgstr "用户界面"
+
+# a41f3714ea474cafa002318580d95e84
+#: ../../ui.rst:21
+msgid "Log In to the UI"
+msgstr "登陆到用户界面"
+
+# aab161d8e0fa441c97c979ad5befdaf2
+#: ../../ui.rst:23
+msgid ""
+"CloudStack provides a web-based UI that can be used by both administrators "
+"and end users. The appropriate version of the UI is displayed depending on "
+"the credentials used to log in. The UI is available in popular browsers "
+"including IE7, IE8, IE9, Firefox 3.5+, Firefox 4, Safari 4, and Safari 5. "
+"The URL is: (substitute your own management server IP address)"
+msgstr "CloudStack提供一个基于web的UI，管理员和终端用户能够使用这个界面。用户界面版本依赖于登陆时使用的凭证不同而不同。用户界面是适用于大多数流行的浏览器包括IE7,IE8,IE9,Firefox3.5+,Firefox4,Safari4,和Safari5。URL是:(用你自己的管理控制服务器IP地址代替)"
+
+# 5757c519124e45b4b91631b922360a4c
+#: ../../ui.rst:34
+msgid ""
+"On a fresh Management Server installation, a guided tour splash screen "
+"appears. On later visits, you’ll see a login screen where you specify the "
+"following to proceed to your Dashboard:"
+msgstr "如果管理服务器是全新的安装,。那么会出现一个安装向导。在稍后的访问中,，你将看到一个登录界面,，你需要通过用户名和密码登入来查看你的仪表盘."
+
+# 192d35e05058441db921256f04a28daf
+#: ../../ui.rst:38
+msgid ""
+"Username -> The user ID of your account. The default username is admin."
+msgstr "用户名 -> 你账号的用户ID。默认用户名是admin。"
+
+# 7ca04676225345a3a4d7e9f05fa900b9
+#: ../../ui.rst:40
+msgid ""
+"Password -> The password associated with the user ID. The password for the "
+"default username is password."
+msgstr "密码 -> 用户ID对应的密码。默认用户名的密码是password。"
+
+# fff9c234e7724e1aa8a5ca63b9cbc714
+#: ../../ui.rst:43
+msgid "Domain -> If you are a root user, leave this field blank."
+msgstr "域 -> 如果你是root用户，此处留空即可。"
+
+# f7cc367a3acb49149809ad5212740659
+#: ../../ui.rst:45
+msgid ""
+"If you are a user in the sub-domains, enter the full path to the domain, "
+"excluding the root domain."
+msgstr "如果你是一个子域用户，在域中输入完全路径，不包括根域。"
+
+# 2716e01ce2b446be9cf2b3c098897945
+#: ../../ui.rst:48
+msgid ""
+"For example, suppose multiple levels are created under the root domain, such"
+" as Comp1/hr. The users in the Comp1 domain should enter Comp1 in the Domain"
+" field, whereas the users in the Comp1/sales domain should enter "
+"Comp1/sales."
+msgstr "例如，假设在根域下建立了多个层级，像Comp1/hr，在Comp1域的用户在域字段处应该输入Comp1，在Comp1/sales域的用户应该输入Comp1/sales。"
+
+# dab31f7d62b846799291e80598d3534d
+#: ../../ui.rst:53
+msgid ""
+"For more guidance about the choices that appear when you log in to this UI, "
+"see Logging In as the Root Administrator."
+msgstr "更多关于当你登录这个界面时选项的指导，参照作为根管理员登录。"
+
+# f89e19a4f46d49d3899770c2d8d858ae
+#: ../../ui.rst:58
+msgid "End User's UI Overview"
+msgstr "最终用户界面概览"
+
+# fab0b6e0d255493e9c1a1800bffbd107
+#: ../../ui.rst:60
+msgid ""
+"The CloudStack UI helps users of cloud infrastructure to view and use their "
+"cloud resources, including virtual machines, templates and ISOs, data "
+"volumes and snapshots, guest networks, and IP addresses. If the user is a "
+"member or administrator of one or more CloudStack projects, the UI can "
+"provide a project-oriented view."
+msgstr "CloudStack用户界面帮助云基础设施的用户查看和使用他们的云资源，包括虚拟机、模板和ISO、数据卷和快照、宾客网络，以及IP 地址。如果用户是一个或多个CloudStack项目的成员或管理员，用户界面能提供一个面向项目的视图。"
+
+# 03bffb509d6342f09a88c6c18b4a0041
+#: ../../ui.rst:68
+msgid "Root Administrator's UI Overview"
+msgstr "根管理员界面的概述"
+
+# f46ea02636f0416ab79e48c05c194422
+#: ../../ui.rst:70
+msgid ""
+"The CloudStack UI helps the CloudStack administrator provision, view, and "
+"manage the cloud infrastructure, domains, user accounts, projects, and "
+"configuration settings. The first time you start the UI after a fresh "
+"Management Server installation, you can choose to follow a guided tour to "
+"provision your cloud infrastructure. On subsequent logins, the dashboard of "
+"the logged-in user appears. The various links in this screen and the "
+"navigation bar on the left provide access to a variety of administrative "
+"functions. The root administrator can also use the UI to perform all the "
+"same tasks that are present in the end-user’s UI."
+msgstr "CloudStack界面帮助CloudStack管理员配置、查看和管理云的基础设施、用户域、账号、项目和配置。当一个全新的管理服务器安装完成后，在第一次启动界面的时候，可以选择根随引导步骤配置云的基础设施。当再次登录时，会显示当前登录用户的仪表板。在这个页面有很多的连接，可以通过左边的导航栏访问各种管理功能。根管理员也可以使用界面像最终用户一样来执行所有的功能。 "
+
+# 2010e004d6354a46899b6e0a6177a36a
+#: ../../ui.rst:82
+msgid "Logging In as the Root Administrator"
+msgstr "作为根管理员登录"
+
+# beb82ae526444b67b6c2baff8c7901a7
+#: ../../ui.rst:84
+msgid ""
+"After the Management Server software is installed and running, you can run "
+"the CloudStack user interface. This UI is there to help you provision, view,"
+" and manage your cloud infrastructure."
+msgstr "在管理服务器软件安装并且运行后, 你就可以运行CloudStack的用户界面.了。在这里通过UI，可以供给、查看并管理你的云基础架构。"
+
+# 6beabdba74e7408e8fcc8ffa226a704e
+# 8c7e2423aea64ae6b5b2f13c8c000895
+#: ../../ui.rst:88 ../../ui.rst:151
+msgid ""
+"Open your favorite Web browser and go to this URL. Substitute the IP address"
+" of your own Management Server:"
+msgstr "打开你自己喜欢的浏览器并访问这个URL。请把IP地址替换成你自己的管理服务器的IP。"
+
+# 5afc8c800bcb4248a79f7b7dc8ea6173
+#: ../../ui.rst:95
+msgid ""
+"After logging into a fresh Management Server installation, a guided tour "
+"splash screen appears. On later visits, you’ll be taken directly into the "
+"Dashboard."
+msgstr "初次登录管理服务器时，会出现一个向导启动画面。后续访问时，您会直接进入控制面板。"
+
+# a27fd5db6a0d41dbb4d17954889871c7
+#: ../../ui.rst:99
+msgid "If you see the first-time splash screen, choose one of the following."
+msgstr "如果你看到第一次的向导屏幕, 可以选择下面步骤之一进行。"
+
+# f9579429faa6431a9cc007c91af49e61
+#: ../../ui.rst:101
+msgid ""
+"**Continue with basic setup.** Choose this if you're just trying CloudStack,"
+" and you want a guided walkthrough of the simplest possible configuration so"
+" that you can get started right away. We'll help you set up a cloud with the"
+" following features: a single machine that runs CloudStack software and uses"
+" NFS to provide storage; a single machine running VMs under the XenServer or"
+" KVM hypervisor; and a shared public network."
+msgstr "**继续执行基本安装。**如果你仅仅是想体验CloudStack，请选择这个，并且这样你可以马上开始跟着向导进行简单的配置。我们将帮助你建立一个有以下功能的云：一个运行CloudStack软件的机器和使用NFS协议的存储；一个运行VMs的XenServer或KVM hypervisor的服务器；一个共享的公有网络。"
+
+# 8a24a6a0c06f440087e093cad917bffb
+#: ../../ui.rst:109
+msgid ""
+"The prompts in this guided tour should give you all the information you "
+"need, but if you want just a bit more detail, you can follow along in the "
+"Trial Installation Guide."
+msgstr "安装向导的提示会给你需要的所有信息。但如果你需要更多的详细信息，你可以按照试用安装向导进行。"
+
+# 81d70c27e4d842afbbdc4f74e0c19acb
+#: ../../ui.rst:113
+msgid ""
+"**I have used CloudStack before.** Choose this if you have already gone "
+"through a design phase and planned a more sophisticated deployment, or you "
+"are ready to start scaling up a trial cloud that you set up earlier with the"
+" basic setup screens. In the Administrator UI, you can start using the more "
+"powerful features of CloudStack, such as advanced VLAN networking, high "
+"availability, additional network elements such as load balancers and "
+"firewalls, and support for multiple hypervisors including Citrix XenServer, "
+"KVM, and VMware vSphere."
+msgstr "**我之前用过CloudStack。** 如果您已经完成设计阶段，计划部署一个复杂CloudStack云，或是准备对用基础安装向导搭建的试验云进行扩展，请选择此项。在管理员UI中，您可以使用CloudStack中更强大的功能，例如高级VLAN网络、高可用、负载均衡器和防火墙等额外网络设备，以及支持Citrix XenServer、KVM、VMware vSphere等多种虚拟化平台。"
+
+# 031ecbafb6b14054869c6a4202b5c1fd
+#: ../../ui.rst:123
+msgid "The root administrator Dashboard appears."
+msgstr "根管理员的仪表盘显示出来。"
+
+# 7d9e4e036dec429db9386110482d17fa
+#: ../../ui.rst:125
+msgid ""
+"You should set a new root administrator password. If you chose basic setup, "
+"you’ll be prompted to create a new password right away. If you chose "
+"experienced user, use the steps in :ref:`changing-root-password`."
+msgstr "你应该为根管理员设置一个新的密码。如果你选择基础设置。将会提示你立即创建一个新的密码。如果你选择有经验的用户，请选择:ref:`changing-root-password`里的步骤。"
+
+# 812d903dc8bc4cf5a98f694baeb328a0
+#: ../../ui.rst:130
+msgid ""
+"You are logging in as the root administrator. This account manages the "
+"CloudStack deployment, including physical infrastructure. The root "
+"administrator can modify configuration settings to change basic "
+"functionality, create or delete user accounts, and take many actions that "
+"should be performed only by an authorized person. Please change the default "
+"password to a new, unique password."
+msgstr "使用根管理员登录。这个账号管理CloudStack的部署，包括物理架构。根管理员可以通过更改配置来变更基本的功能，创建或删除用户账号，以及其它许多只有被授权的用户执行的操作。请更改默认的密码，确保其唯一性和安全性。"
+
+# b350994b6904403db6d30d524f0eed32
+#: ../../ui.rst:140
+msgid "Changing the Root Password"
+msgstr "更改Root密码"
+
+# 3a06c8a9892b4cbeaac7e2dec367ddd7
+#: ../../ui.rst:142
+msgid ""
+"During installation and ongoing cloud administration, you will need to log "
+"in to the UI as the root administrator. The root administrator account "
+"manages the CloudStack deployment, including physical infrastructure. The "
+"root administrator can modify configuration settings to change basic "
+"functionality, create or delete user accounts, and take many actions that "
+"should be performed only by an authorized person. When first installing "
+"CloudStack, be sure to change the default password to a new, unique value."
+msgstr "在云的安装及后续管理过程中，您需要用根管理员登录UI。根管理员账号管理着CloudStack的部署以及物理设施。根管理员可以修改系统配置，改变基本功能，创建和删除用户账号，以及其他仅限于已授权人员执行的操作。在初始安CloudStack时，请务必修改默认密码为新的较独特的密码。"
+
+# 7057f98c0cb94bceb1dc66c14a0b5802
+#: ../../ui.rst:158
+msgid ""
+"Log in to the UI using the current root user ID and password. The default is"
+" admin, password."
+msgstr "使用当前root用户的ID和口令登录UI。缺省为admin，pawword。"
+
+# fdf104279af341739d24347f0e1fce4e
+#: ../../ui.rst:161
+msgid "Click Accounts."
+msgstr "点击帐户。"
+
+# c12c934bf488453e9c209dcf140e5b22
+#: ../../ui.rst:163
+msgid "Click the admin account name."
+msgstr "点击管理员帐号名。"
+
+# 9941a672247948c09ee39a2119dcbb22
+#: ../../ui.rst:165
+msgid "Click View Users."
+msgstr "点击查看用户。"
+
+# 482e7c8a3e904702a4089d4643cdae41
+#: ../../ui.rst:167
+msgid "Click the admin user name."
+msgstr "点击管理员用户名。"
+
+# ae46b97a741b49e4b1c2422f074135e9
+#: ../../ui.rst:169
+msgid "Click the Change Password button. |change-password.png|"
+msgstr "点击更改密码按钮。 |change-password.png|"
+
+# 9ba47399deaa4e378669ad789c0a47c0
+#: ../../ui.rst:171
+msgid "Type the new password, and click OK."
+msgstr "输入新密码，然后点击确认。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/usage.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/usage.mo
new file mode 100644
index 0000000..6902cb2
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/usage.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/usage.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/usage.po
new file mode 100644
index 0000000..253aee2
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/usage.po
@@ -0,0 +1,1655 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:05+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# f960d1bdf1ff4edcab85c8de14d937d9
+#: ../../usage.rst:18
+msgid "Working with Usage"
+msgstr "使用服务"
+
+# 15ed9c55a30744308390d710f71e001e
+#: ../../usage.rst:20
+msgid ""
+"The Usage Server is an optional, separately-installed part of CloudStack "
+"that provides aggregated usage records which you can use to create billing "
+"integration for CloudStack. The Usage Server works by taking data from the "
+"events log and creating summary usage records that you can access using the "
+"listUsageRecords API call."
+msgstr "使用服务器是CloudStack一个可选项,分别安装产品的一部分,提供了聚合使用记录您可以使用它来创建计费集成产品。使用服务器通过使用数据从事件日志和创建汇总使用记录,您可以访问使用listUsageRecords API调用。"
+
+# 96a54f49657f4ecb814c7babc3d12cd5
+#: ../../usage.rst:26
+msgid ""
+"The usage records show the amount of resources, such as VM run time or "
+"template storage space, consumed by guest instances."
+msgstr "使用记录显示数量的资源,比如虚拟机运行时间或模板存储空间，以被客人消耗为例。"
+
+# 55c9c7dee78b4ff284f8a3775ee15d80
+#: ../../usage.rst:29
+msgid ""
+"The Usage Server runs at least once per day. It can be configured to run "
+"multiple times per day."
+msgstr "使用服务器运行至少每天一次。它可以被配置为每天多次运行。"
+
+# e3e786135adc456da195d8c62094e4cf
+#: ../../usage.rst:34
+msgid "Configuring the Usage Server"
+msgstr "配置使用服务器"
+
+# 6fb60ef9e16e4db0878d21a3d8ae162b
+#: ../../usage.rst:36
+msgid "To configure the usage server:"
+msgstr "配置使用服务器"
+
+# 5adc62eff1f640a094ea087767a99266
+#: ../../usage.rst:38
+msgid ""
+"Be sure the Usage Server has been installed. This requires extra steps "
+"beyond just installing the CloudStack software. See Installing the Usage "
+"Server (Optional) in the Advanced Installation Guide."
+msgstr "确定使用服务器已经被安装。它要求安装额外的CloudStack软件步骤。参见高级安装手册中的使用服务器（可选）。"
+
+# 79b6062dbd284c60a7d174315e5ddf4f
+#: ../../usage.rst:42
+msgid "Log in to the CloudStack UI as administrator."
+msgstr "作为管理员登录到CloudStack用户界面。"
+
+# 19a9f5fbef3041d9b13807ca7c2cb8b9
+#: ../../usage.rst:44
+msgid "Click Global Settings."
+msgstr "单击全局设置"
+
+# 667e5b8b21924fb69b4fa8afbf76896b
+#: ../../usage.rst:46
+msgid ""
+"In Search, type usage. Find the configuration parameter that controls the "
+"behavior you want to set. See the table below for a description of the "
+"available parameters."
+msgstr "在搜索栏输入 usage。找到no需要改变的配置参数。下表是这些参数的详细描述。"
+
+# 8fa5855d775b43958fe08525d0e94aae
+#: ../../usage.rst:50
+msgid "In Actions, click the Edit icon."
+msgstr "在操作栏点击编辑图标。"
+
+# 63178267fdd94998ab92da5146692648
+#: ../../usage.rst:52
+msgid "Type the desired value and click the Save icon."
+msgstr "输入数值点击保存图标。"
+
+# 5d851f4543c0408f8e57dce0857766a3
+#: ../../usage.rst:54
+msgid ""
+"Restart the Management Server (as usual with any global configuration "
+"change) and also the Usage Server:"
+msgstr "重新启动管理服务器（通常在改变了全局配置之后都要进行这步）并重启使用服务器。"
+
+# b91f29141e0f4cdaaa81be318e86c10e
+#: ../../usage.rst:62
+msgid ""
+"The following table shows the global configuration settings that control the"
+" behavior of the Usage Server."
+msgstr "下表列出了全局配置中控制使用服务器的配置项。"
+
+# 1e76426d14bf4fc6915a0e1c79ef2b9a
+#: ../../usage.rst:65
+msgid "Parameter Name Description"
+msgstr "参数名描述"
+
+# 668e6317ce104d72ab45c55b9411ea8e
+#: ../../usage.rst:67
+msgid "enable.usage.server Whether the Usage Server is active."
+msgstr "enable.usage.server是否开启使用服务器。"
+
+# 1fcaf07a4ddb4e8c958cd1b6ef8cfe91
+#: ../../usage.rst:69
+msgid "usage.aggregation.timezone"
+msgstr "usage.aggregation.timezone"
+
+# fb381c2892df4ea7b1c44440f03ba556
+#: ../../usage.rst:71
+msgid ""
+"Time zone of usage records. Set this if the usage records and daily job "
+"execution are in different time zones. For example, with the following "
+"settings, the usage job will run at PST 00:15 and generate usage records for"
+" the 24 hours from 00:00:00 GMT to 23:59:59 GMT:"
+msgstr "记录使用信息所用的时区。如果使用记录和日程工作执行在不同的时区时进行设置。例如，进行下列设置，使用任务运行在PST 00:15和24小时内产生的从00:00:00GMT到23:59:59GMT的使用记录："
+
+# 509f3bce303a4ab7a526dcc19e3c3e50
+#: ../../usage.rst:82
+msgid ""
+"Valid values for the time zone are specified in `Appendix A, *Time Zones* "
+"<http://docs.cloudstack.apache.org/en/latest/dev.html?highlight=time%20zones"
+"#time-zones>`_"
+msgstr "时间域的有效值已经被具体化到 `Appendix A, *Time Zones* 中 <http://docs.cloudstack.apache.org/en/latest/dev.html?highlight=time%20zones#time-zones>`_"
+
+# 3133231b20dd4c9da1fe9fd7d09136a3
+#: ../../usage.rst:85
+msgid "Default: GMT"
+msgstr "默认：GMT"
+
+# 22dabfab93eb4361b26eb9088cad5134
+#: ../../usage.rst:87
+msgid "usage.execution.timezone"
+msgstr "usage.execution.timezone"
+
+# a27f0dcfc71847ee846e80cb1b5c6e66
+#: ../../usage.rst:89
+msgid ""
+"The time zone of usage.stats.job.exec.time. Valid values for the time zone "
+"are specified in `Appendix A, *Time Zones* "
+"<http://docs.cloudstack.apache.org/en/latest/dev.html?highlight=time%20zones"
+"#time-zones>`_"
+msgstr "域时间项usage.stats.job.exec.time。时间域的有效值被具体化在`Appendix A, *Time Zones* <http://docs.cloudstack.apache.org/en/latest/dev.html?highlight=time%20zones#time-zones>`_"
+
+# 101b64630291428aa4dce0f295b51f96
+#: ../../usage.rst:93
+msgid "Default: The time zone of the management server."
+msgstr "默认时区是管理服务器的时区。"
+
+# e5296f4116c949e282dda12b62a2e31b
+#: ../../usage.rst:95
+msgid "usage.sanity.check.interval"
+msgstr "usage.sanity.check.interval"
+
+# 12e3d1486808475ba2d50b4b1f480b20
+#: ../../usage.rst:97
+msgid ""
+"The number of days between sanity checks. Set this in order to periodically "
+"search for records with erroneous data before issuing customer invoices. For"
+" example, this checks for VM usage records created after the VM was "
+"destroyed, and similar checks for templates, volumes, and so on. It also "
+"checks for usage times longer than the aggregation range. If any issue is "
+"found, the alert ALERT\\_TYPE\\_USAGE\\_SANITY\\_RESULT = 21 is sent."
+msgstr "完整性检查时间间隔。设置此值来定期在生成用户账单之前检查出错误的数据。比如，他能检查虚拟机被销毁之后的使用记录和模板，卷等的类似记录。还会检查超过聚合时间的使用时间。如果发生了错误就会发送ALERT_TYPE_USAGE_SANITY_RESULT = 21 警告。"
+
+# d6a51defdc9b4ca1900dca6ee38d488b
+#: ../../usage.rst:105
+msgid "usage.stats.job.aggregation.range"
+msgstr "usage.stats.job.aggregation.range"
+
+# f200ecf1491a41c58c58d607a2030621
+#: ../../usage.rst:107
+msgid ""
+"The time period in minutes between Usage Server processing jobs. For "
+"example, if you set it to 1440, the Usage Server will run once per day. If "
+"you set it to 600, it will run every ten hours. In general, when a Usage "
+"Server job runs, it processes all events generated since usage was last run."
+msgstr "使用服务器执行任务时间间隔（分钟为单位）。比如，如果你将此值设为1440，使用服务器将每天执行一次。如果你将此值设为600，则会10小时执行一次。一般情况下使用服务器执行任务时会继续在上次的使用统计基础上处理所有事件。"
+
+# 3fb2ba9c61a64f54bb226a97eff0e59f
+#: ../../usage.rst:113
+msgid ""
+"There is special handling for the case of 1440 (once per day). In this case "
+"the Usage Server does not necessarily process all records since Usage was "
+"last run. CloudStack assumes that you require processing once per day for "
+"the previous, complete day’s records. For example, if the current day is "
+"October 7, then it is assumed you would like to process records for October "
+"6, from midnight to midnight. CloudStack assumes this “midnight to midnight”"
+" is relative to the usage.execution.timezone."
+msgstr "当值为1440（一天一次）时有点特殊。该情况下，用量服务器并不需要处理上次运行之后的所有事件。&PRODUCT;假定您要一天一次处理昨天的，完成每日记录。例如，如果今天是10月7号，会假定您要处理6号的记录，从0点到24点。CloudStack假定的0点到24点采用的时区为 usage.execution.timezone的值。"
+
+# 657e01fff8404e7086e1a5cd318ed5b9
+#: ../../usage.rst:121
+msgid "Default: 1440"
+msgstr "默认：1440"
+
+# 8e231a3dfe9b4ac494f5ae8dc3e03001
+#: ../../usage.rst:123
+msgid "usage.stats.job.exec.time"
+msgstr "usage.stats.job.exec.time"
+
+# 05f6de4a7dd947ceba3246443c6e2ace
+#: ../../usage.rst:125
+msgid ""
+"The time when the Usage Server processing will start. It is specified in "
+"24-hour format (HH:MM) in the time zone of the server, which should be GMT. "
+"For example, to start the Usage job at 10:30 GMT, enter “10:30”."
+msgstr "使用服务器处理任务的启动时间。采用24小时格式 （HH:MM），时区为服务器的时区，应该为GMT。比如要在GMT时区10:30 启动用量任务，请输入“10:30”"
+
+# 54677f1477574ba58b744ade5f531ddd
+#: ../../usage.rst:129
+msgid ""
+"If usage.stats.job.aggregation.range is also set, and its value is not 1440,"
+" then its value will be added to usage.stats.job.exec.time to get the time "
+"to run the Usage Server job again. This is repeated until 24 hours have "
+"elapsed, and the next day's processing begins again at "
+"usage.stats.job.exec.time."
+msgstr "如果同时设置了usage.stats.job.aggregation.range参数，并且该参数值不是1440，这个值将被添加到usage.stats.job.exec.time到时再次运行使用服务器任务。重复此过程,直到24小时已经过去,第二天到达 usage.stats.job.exec.time处理任务开始。"
+
+# 870bef8e0dc54e1a87ab39acc1c59e7b
+#: ../../usage.rst:135
+msgid "Default: 00:15."
+msgstr "默认：00:15。"
+
+# 3c30b2b9e20f485c8ac878c1c8b62ef5
+#: ../../usage.rst:137
+msgid ""
+"For example, suppose that your server is in GMT, your user population is "
+"predominantly in the East Coast of the United States, and you would like to "
+"process usage records every night at 2 AM local (EST) time. Choose these "
+"settings:"
+msgstr "比如,假设你服务器时区是GMT，你的用户主要在美国东海岸，而你有打算在当地时间（EST）每天凌晨两点执行使用记录统计。选择这些选项："
+
+# 910e4a77b6c34e64ad844e417ab623d5
+#: ../../usage.rst:142
+msgid "enable.usage.server = true"
+msgstr "enable.usage.server = true"
+
+# 078da3cc8569439c9002cbbb7337d936
+#: ../../usage.rst:144
+msgid "usage.execution.timezone = America/New\\_York"
+msgstr "usage.execution.timezone = America/New\\_York"
+
+# 42e66162ae97481083688b89c626c8cc
+#: ../../usage.rst:146
+msgid ""
+"usage.stats.job.exec.time = 07:00. This will run the Usage job at 2:00 AM "
+"EST. Note that this will shift by an hour as the East Coast of the U.S. "
+"enters and exits Daylight Savings Time."
+msgstr "usage.stats.job.exec.time = 07:00。这将会在东部时间2：00执行使用任务。注意考虑进出白昼保存时间在将时间迁移大U.S.东海岸。"
+
+# 5ba2fd5fa7004081a393783418655cdd
+#: ../../usage.rst:150
+msgid "usage.stats.job.aggregation.range = 1440"
+msgstr "usage.stats.job.aggregation.range = 1440"
+
+# 1c9ce06adfa54705878ac2e20fcc8462
+#: ../../usage.rst:152
+msgid ""
+"With this configuration, the Usage job will run every night at 2 AM EST and "
+"will process records for the previous day’s midnight-midnight as defined by "
+"the EST (America/New\\_York) time zone."
+msgstr "在这种配置下，使用任务 会在东部时间每天2 AM执行，同时会如定义的一样以东部时间(美国纽约时间)统计前一天的“午夜到午夜使用记录。”"
+
+# 1e914c7e818e47d8b13676d7f92bbe0b
+#: ../../usage.rst:157
+msgid ""
+"Because the special value 1440 has been used for "
+"usage.stats.job.aggregation.range, the Usage Server will ignore the data "
+"between midnight and 2 AM. That data will be included in the next day's run."
+msgstr "由于在usage.stats.job.aggregation.range中使用特殊值1440，用量服务器将忽略午夜到凌晨2：00之间的数据。这些数据将会包含在第二天的统计中。"
+
+# 40d99d806e4949158aa5ab2e841cfa2a
+#: ../../usage.rst:164
+msgid "Setting Usage Limits"
+msgstr "设置使用限制"
+
+# 579aaca84d1548508b091885f6e9e9da
+#: ../../usage.rst:166
+msgid ""
+"CloudStack provides several administrator control points for capping "
+"resource usage by users. Some of these limits are global configuration "
+"parameters. Others are applied at the ROOT domain and may be overridden on a"
+" per-account basis."
+msgstr "CloudStack提供多个管理员控制点以便控制用户资源使用。其中一些限制是全局配置参数。其他一些应用在root域，并且会覆盖每个账号的基本配置"
+
+# 229ad89efb9c4cb0ab03a6ce99f44f23
+#: ../../usage.rst:173
+msgid "Globally Configured Limits"
+msgstr "全局配置限制"
+
+# e2b6313d1a4d4917a2544b4440379415
+#: ../../usage.rst:175
+msgid ""
+"In a zone, the guest virtual network has a 24 bit CIDR by default. This "
+"limits the guest virtual network to 254 running instances. It can be "
+"adjusted as needed, but this must be done before any instances are created "
+"in the zone. For example, 10.1.1.0/22 would provide for ~1000 addresses."
+msgstr "在一个域中，客户虚拟网络默认有24位CIDR.它限制了客户网络运行上线是254个实例。它可以根据需求调节，但必须在域中实例创建之前。例如，10.1.1.0/22 将提供 ~1000 地址。"
+
+# 84670b12426b4429831f536c401fc323
+#: ../../usage.rst:181
+msgid "The following table lists limits set in the Global Configuration:"
+msgstr "下表列出了设置全局配置的限制："
+
+# 7da9c9f6c4464762b975b5c84e4ebf9c
+# 146d490544914790b152209b009cacb9
+# 1bb822fa0c3e4b7db77988b5cf5efdbd
+# c79e2332c1ba4ad5883126f553ad5388
+#: ../../usage.rst:184 ../../usage.rst:239 ../../usage.rst:343
+#: ../../usage.rst:414
+msgid "Parameter Name"
+msgstr "参数名称"
+
+# 69e6a02d3513471b89dca9419976e56b
+#: ../../usage.rst:184
+msgid "Definition"
+msgstr "定义"
+
+# 8f803160c7ef4b258545cf19783a2cb2
+#: ../../usage.rst:186
+msgid "max.account.public.ips"
+msgstr "max.account.public.ips"
+
+# 33a9e7f75edb450eb385f759769e8a27
+#: ../../usage.rst:186
+msgid "Number of public IP addresses that can be owned by an account"
+msgstr "账户可拥有的公用IP地址个数"
+
+# 9d54d7043dfa4cfdba9892d7b4987d27
+#: ../../usage.rst:188
+msgid "max.account.snapshots"
+msgstr "max.account.snapshots"
+
+# 53e9c6336fc343f58d5d0f0c982ecd16
+#: ../../usage.rst:188
+msgid "Number of snapshots that can exist for an account"
+msgstr "快照的数量存在于一个记述中"
+
+# 6979458b8f824d9ea8eb1a932cb3700a
+#: ../../usage.rst:190
+msgid "max.account.templates"
+msgstr "max.account.templates"
+
+# a450954b78c549129d90f452f3261c83
+#: ../../usage.rst:190
+msgid "Number of templates that can exist for an account"
+msgstr "模板的数量可能存于一个记述中"
+
+# e090c2956d874c139e10f94be47e21bd
+#: ../../usage.rst:192
+msgid "max.account.user.vms"
+msgstr "max.account.user.vms"
+
+# d30280c4822b48cf86341f0c6f0e9f40
+#: ../../usage.rst:192
+msgid "Number of virtual machine instances that can exist for an account"
+msgstr "虚拟机实例的数量也可能存在于一个记述中"
+
+# ecaf59ece9264e429a9664b72c83c9d5
+#: ../../usage.rst:194
+msgid "max.account.volumes"
+msgstr "max.account.volumes"
+
+# 352d53dede964c53adaba408485377bb
+#: ../../usage.rst:194
+msgid "Number of disk volumes that can exist for an account"
+msgstr "磁盘卷的数量也可能存于一个记述中"
+
+# 4855308d9e7f453ca68c4f73a23b7da2
+#: ../../usage.rst:196
+msgid "max.template.iso.size"
+msgstr "max.template.iso.size"
+
+# c3cf19fabb7b41c6bfeda6bfcb0d40c6
+#: ../../usage.rst:196
+msgid "Maximum size for a downloaded template or ISO in GB"
+msgstr "下载的模板或ISO最大的单位是GB"
+
+# e2bd816e02a74341ac3b504ef37abf9b
+#: ../../usage.rst:198
+msgid "max.volume.size.gb"
+msgstr "max.volume.size.gb"
+
+# ac589029cbaa451fb486f219b27caf43
+#: ../../usage.rst:198
+msgid "Maximum size for a volume in GB"
+msgstr "卷的最大单位是GB"
+
+# 3b152b7effc14a2098e6b2f885125e11
+#: ../../usage.rst:200
+msgid "network.throttling.rate"
+msgstr "network.throttling.rate"
+
+# d66b6e2b68304b4d97dae0d72709be2f
+#: ../../usage.rst:200
+msgid ""
+"Default data transfer rate in megabits per second allowed per user "
+"(supported on XenServer)"
+msgstr "默认的传输速率是允许用户按照Mb每秒(支持XenServer)"
+
+# e01d028d0d5643a3a283f12888581998
+#: ../../usage.rst:202
+msgid "snapshot.max.hourly"
+msgstr "snapshot.max.hourly"
+
+# 305a224a1c5946ab949570233597705b
+#: ../../usage.rst:202
+msgid ""
+"Maximum recurring hourly snapshots to be retained for a volume. If the limit"
+" is reached, early snapshots from the start of the hour are deleted so that "
+"newer ones can be saved. This limit does not apply to manual snapshots. If "
+"set to 0, recurring hourly snapshots can not be scheduled"
+msgstr "最大的可再现时时性快照可以保存在卷中。如果数量的限制达到，早期的来自开始阶段的快照就会被删除以使新的快照可以被存储。这种限制方法不支持手工快照。若设为0，可再现性时时快照将没有保存。"
+
+# 7734cc014872464a8d8672c1190ff731
+#: ../../usage.rst:204
+msgid "snapshot.max.daily"
+msgstr "snapshot.max.daily"
+
+# ddca821bebdf4a12a2b4fb3d9e089efe
+#: ../../usage.rst:204
+msgid ""
+"Maximum recurring daily snapshots to be retained for a volume. If the limit "
+"is reached, snapshots from the start of the day are deleted so that newer "
+"ones can be saved. This limit does not apply to manual snapshots. If set to "
+"0, recurring daily snapshots can not be scheduled"
+msgstr "最大的可再现时时性快照可以保存在卷中。如果数量的限制达到，早期的来自开始阶段的快照就会被删除以使新的快照可以被存储。这种限制方法不支持手工快照。若设为0，可再现性时时快照将没有保存。"
+
+# 90b70954860841d5a31b17b85cc10f84
+#: ../../usage.rst:206
+msgid "snapshot.max.weekly"
+msgstr "snapshot.max.weekly"
+
+# 8ee51877c42a40da9039bdc877f388c5
+#: ../../usage.rst:206
+msgid ""
+"Maximum recurring weekly snapshots to be retained for a volume. If the limit"
+" is reached, snapshots from the beginning of the week are deleted so that "
+"newer ones can be saved. This limit does not apply to manual snapshots. If "
+"set to 0, recurring weekly snapshots can not be scheduled"
+msgstr "最大的可再现时时性快照可以保存在卷中。如果数量的限制达到，早期的来自开始阶段的快照就会被删除以使新的快照可以被存储。这种限制方法不支持手工快照。若设为0，可再现性时时快照将没有保存。"
+
+# 65aa1a30aab34f218756e423bac8f482
+#: ../../usage.rst:208
+msgid "snapshot.max.monthly"
+msgstr "snapshot.max.monthly"
+
+# 631eba2a40fe48f3b4f179dfe6e9fdc7
+#: ../../usage.rst:208
+msgid ""
+"Maximum recurring monthly snapshots to be retained for a volume. If the "
+"limit is reached, snapshots from the beginning of the month are deleted so "
+"that newer ones can be saved. This limit does not apply to manual snapshots."
+" If set to 0, recurring monthly snapshots can not be scheduled."
+msgstr "最大的可再现时时性快照可以保存在卷中。如果数量的限制达到，早期的来自开始阶段的快照就会被删除以使新的快照可以被存储。这种限制方法不支持手工快照。若设为0，可再现性时时快照将没有保存。"
+
+# dce0ccf760cb481290483d2e6c7439e4
+#: ../../usage.rst:211
+msgid ""
+"To modify global configuration parameters, use the global configuration "
+"screen in the CloudStack UI. See Setting Global Configuration Parameters"
+msgstr "使用CloudStack中的用户界面中的全局配置界面可以修改全局配置参数。"
+
+# adacfb1bcc74482cbac23e9a14c1803c
+#: ../../usage.rst:216
+msgid "Limiting Resource Usage"
+msgstr "限制资源使用"
+
+# 354d5dde0afe47a982710d8800da3315
+#: ../../usage.rst:218
+msgid ""
+"CloudStack allows you to control resource usage based on the types of "
+"resources, such as CPU, RAM, Primary storage, and Secondary storage. A new "
+"set of resource types has been added to the existing pool of resources to "
+"support the new customization model—need-basis usage, such as large VM or "
+"small VM. The new resource types are now broadly classified as CPU, RAM, "
+"Primary storage, and Secondary storage. The root administrator is able to "
+"impose resource usage limit by the following resource types for Domain, "
+"Project, and Accounts."
+msgstr "CloudStack允许根据资源类型控制资源使用，例如CPU,RAM,主存储，辅助存储。一个新的资源类型集已经被添加到了已经存在的支持新通俗模型的资源池-基于需要使用，例如大型VM或者小型VM.新的资源类型被广泛分类在如CPU,RAM,主存储和辅助存储中。超级管理员能够利用下列资源的使用限制，例如域，项目或者账户。"
+
+# b80deb66aa1244279f48b9e17db7f7a0
+#: ../../usage.rst:227
+msgid "CPUs"
+msgstr "CPUs"
+
+# a7c54e874cae4016b7a1d2a17c5a7a89
+#: ../../usage.rst:229
+msgid "Memory (RAM)"
+msgstr "Memory (RAM)"
+
+# 3db51597d1dd4f328899070b88325384
+#: ../../usage.rst:231
+msgid "Primary Storage (Volumes)"
+msgstr "主存储(卷)"
+
+# 6de9a84059e7408e85e9fdb47dbb341d
+#: ../../usage.rst:233
+msgid "Secondary Storage (Snapshots, Templates, ISOs)"
+msgstr "辅助存储（快照，模板，ISOs）"
+
+# 36f9c552269b44e49eb2f86fa2bd98c8
+#: ../../usage.rst:235
+msgid ""
+"To control the behaviour of this feature, the following configuration "
+"parameters have been added:"
+msgstr "为了控制该特征的行为，以下配置参数已经添加："
+
+# fc46eaac2efd4bf289bbd9025fd78502
+# 160c8719552a4684880d4f4a8ada714c
+# 947dba25316d4d74959935b65c8c5a33
+# 161ab30e9a60413d90729511c5fe9ec1
+#: ../../usage.rst:239 ../../usage.rst:345 ../../usage.rst:416
+#: ../../usage.rst:750
+msgid "Description"
+msgstr "描述"
+
+# 23d6c966c2c94a1f986282a729352f38
+#: ../../usage.rst:241
+msgid "max.account.cpus"
+msgstr "max.account.cpus"
+
+# cdd19d9379ec43648cd224ba64a960dd
+# 2ca1b2c4fdc44e0e940da7f75cb5788b
+#: ../../usage.rst:241 ../../usage.rst:249
+msgid ""
+"Maximum number of CPU cores that can be used for an account. Default is 40."
+msgstr "最大的可以被账户使用的CPU核心个数。默认是40."
+
+# 4979d3f2676e4809a49cc696c48d2f8d
+#: ../../usage.rst:243
+msgid "max.account.ram (MB)"
+msgstr "max.account.ram (MB)"
+
+# f3c0b37fc2ea4617b811cef9791eda3b
+# 00fb0cdbac5b4ad291bc50a5e1219a47
+#: ../../usage.rst:243 ../../usage.rst:251
+msgid "Maximum RAM that can be used for an account. Default is 40960."
+msgstr "最大的可以被账户使用的RMA容量。默认值是40960。"
+
+# 45df7928f7174808a2083dd11add33c0
+#: ../../usage.rst:245
+msgid "max.account.primary.storage (GB)"
+msgstr "max.account.primary.storage (GB)"
+
+# 1ee6c5009abd4668a5dd0a640a18c8ea
+# 254b02916fc34ad6a649c8c990d4f41a
+#: ../../usage.rst:245 ../../usage.rst:253
+msgid ""
+"Maximum primary storage space that can be used for an account. Default is "
+"200."
+msgstr "最大的可以被账户使用的主存储个数。默认是200。"
+
+# cdeb23ce821d4c3196c6ea784f4367b6
+#: ../../usage.rst:247
+msgid "max.account.secondary.storage (GB)"
+msgstr "max.account.secondary.storage (GB)"
+
+# c51c46bd539f4093a4393f2d6d4e9b79
+# 982aa6e78c6f4ecda0f24acd5f6564d3
+#: ../../usage.rst:247 ../../usage.rst:255
+msgid ""
+"Maximum secondary storage space that can be used for an account. Default is "
+"400."
+msgstr "最大的可被账户使用的辅助存储空间。默认是400。"
+
+# 01081c6a660a44f5851d914915a1281b
+#: ../../usage.rst:249
+msgid "max.project.cpus"
+msgstr "max.project.cpus"
+
+# b7aede866d8a41298cf2c284450aea39
+#: ../../usage.rst:251
+msgid "max.project.ram (MB)"
+msgstr "max.project.ram (MB)"
+
+# 6a66f463c8a14145b745751a99ff5412
+#: ../../usage.rst:253
+msgid "max.project.primary.storage (GB)"
+msgstr "max.project.primary.storage (GB)"
+
+# 86d804726f994f5ea14d1a29e97eb968
+#: ../../usage.rst:255
+msgid "max.project.secondary.storage (GB)"
+msgstr "max.project.secondary.storage (GB)"
+
+# 8ea9def42949482d99838f5ebe00a5e2
+#: ../../usage.rst:261
+msgid "User Permission"
+msgstr "用户许可"
+
+# 31b6a320c933489c96b4ce8db09ee012
+#: ../../usage.rst:263
+msgid ""
+"The root administrator, domain administrators and users are able to list "
+"resources. Ensure that proper logs are maintained in the ``vmops.log`` and "
+"``api.log`` files."
+msgstr "超级管理员，域管理员和用户能够列出资源。确保合适的属性日至保存在 ``vmops.log`` 和 ``api.log``文件中。"
+
+# 41b569e3765441d69d540fed030e34e2
+#: ../../usage.rst:267
+msgid ""
+"The root admin will have the privilege to list and update resource limits."
+msgstr "超级管理员将有列出和升级资源限制的特权。"
+
+# 9f791a84c2014d73b5f8b74f287ad010
+#: ../../usage.rst:270
+msgid ""
+"The domain administrators are allowed to list and change these resource "
+"limits only for the sub-domains and accounts under their own domain or the "
+"sub-domains."
+msgstr "域管理员仅允许列出和改变在其拥有的域或者子域的子域和账户的资源限制。"
+
+# df23a35291874e2d9f7af5d93db4dae4
+#: ../../usage.rst:274
+msgid ""
+"The end users will the privilege to list resource limits. Use the "
+"listResourceLimits API."
+msgstr "终端用户拥有改变列出资源限制的特权。使用listResourceLimits API.。"
+
+# 474425750935446e84565dc2a2f561b6
+#: ../../usage.rst:279
+msgid "Limit Usage Considerations"
+msgstr "限制使用注意事项："
+
+# c96935ecfc1545448c6a31bf7e9bcefa
+#: ../../usage.rst:281
+msgid ""
+"Primary or Secondary storage space refers to the stated size of the volume "
+"and not the physical size— the actual consumed size on disk in case of thin "
+"provisioning."
+msgstr "主存储或者辅助存储空间参考启动的容器大小而不是物理容量，实际使用的物理空间要小于提供的空间。"
+
+# 003d62e3a41b4ec0838c1ad1e22ab0c8
+#: ../../usage.rst:285
+msgid ""
+"If the admin reduces the resource limit for an account and set it to less "
+"than the resources that are currently being consumed, the existing "
+"VMs/templates/volumes are not destroyed. Limits are imposed only if the user"
+" under that account tries to execute a new operation using any of these "
+"resources. For example, the existing behavior in the case of a VM are:"
+msgstr "如果管理员为账户减少资源限制，并设置少于目前设定的资源数，已经存在的VM/模板/卷也不会破坏。限制仅在账户中的用户试图使用这些资源执行新的操作时表现出来。例如，在一个VM中倘若存在下列行为："
+
+# 61f14d0421dc4f27885ac8f93946dbe6
+#: ../../usage.rst:292
+msgid ""
+"migrateVirtualMachine: The users under that account will be able to migrate "
+"the running VM into any other host without facing any limit issue."
+msgstr "迁移虚拟机：在账户中的用户试图迁移一个正在运行的VM到任何不面临限制问题的主机。"
+
+# 287edb83794948b4b1509e7c1ed82b17
+#: ../../usage.rst:296
+msgid "recoverVirtualMachine: Destroyed VMs cannot be recovered."
+msgstr "恢复虚拟机：破坏的VM不能被修复。"
+
+# 2b57273cf486489e856ef1a97146d73a
+#: ../../usage.rst:298
+msgid ""
+"For any resource type, if a domain has limit X, sub-domains or accounts "
+"under that domain can have there own limits. However, the sum of resource "
+"allocated to a sub-domain or accounts under the domain at any point of time "
+"should not exceed the value X."
+msgstr "对于更多资源类型，如果一个域存在限制X，这个域的子域或者账户也能也有它们自身的限制。尽管如此，一个子域允许分配的资源总和或者域中账户在任何时间点都不能执行X限制。"
+
+# 9f35315b3f6b4560abe71837984f2ed7
+#: ../../usage.rst:303
+msgid ""
+"For example, if a domain has the CPU limit of 40 and the sub-domain D1 and "
+"account A1 can have limits of 30 each, but at any point of time the resource"
+" allocated to D1 and A1 should not exceed the limit of 40."
+msgstr "例如，当一个域有CPU的限制数量为40，其子域D1和账户A1可以有每个30的限制，但是任何时候分配给D1和A1的资源都不能超过限制40."
+
+# cfc912fe9e294238a5a41841f8636ecf
+#: ../../usage.rst:308
+msgid ""
+"If any operation needs to pass through two of more resource limit check, "
+"then the lower of 2 limits will be enforced, For example: if an account has "
+"the VM limit of 10 and CPU limit of 20, and a user under that account "
+"requests 5 VMs of 4 CPUs each. The user can deploy 5 more VMs because VM "
+"limit is 10. However, the user cannot deploy any more instances because the "
+"CPU limit has been exhausted."
+msgstr "如果一些操作需要通过两个或更多的资源限制核查，最少的两个限制将被执行，例如：如果一个账户有10个限制VM和20个限制CPU,用户在账户中申请每4个CPU5个VM。用户可以部署5个或更多的VM,因为VM的限制个数是10。尽管如此，用户不能部署任何实例，因为CPU的限制已经用尽。"
+
+# fd7e43ba4fc2492cb1117d9f171cb475
+#: ../../usage.rst:317
+msgid "Limiting Resource Usage in a Domain"
+msgstr "在一个域中限制资源使用"
+
+# d7bae8b0c64640aaab9b686ccb641ca1
+#: ../../usage.rst:319
+msgid ""
+"CloudStack allows the configuration of limits on a domain basis. With a "
+"domain limit in place, all users still have their account limits. They are "
+"additionally limited, as a group, to not exceed the resource limits set on "
+"their domain. Domain limits aggregate the usage of all accounts in the "
+"domain as well as all the accounts in all the sub-domains of that domain. "
+"Limits set at the root domain level apply to the sum of resource usage by "
+"the accounts in all the domains and sub-domains below that root domain."
+msgstr "CloudStack允许在一个域基础上配置限制。使用域限制的地点是所有的用户都有其账户的的限制。它们有额外的限制，例如群组，不能执行设置在它们域上的资源限制。域限制聚集了任何域中使用的账户和任何账户的所有域的子域。限制设定在根域层次应用于所有域的账户和子域使用的资源综合都低于根域的限制。"
+
+# 42cc77754b864082aff2b2d5e091fa0f
+#: ../../usage.rst:328
+msgid "To set a domain limit:"
+msgstr "设定一个域限制："
+
+# bb5fc3b2710e4ea59810c1d28209dfc2
+# b83cbc0f83d7410e8b117351958fc591
+#: ../../usage.rst:330 ../../usage.rst:401
+msgid "Log in to the CloudStack UI."
+msgstr "登录到CloudStack的界面"
+
+# 530247f4ca1a4475ae86e656ceff6abb
+#: ../../usage.rst:332
+msgid "In the left navigation tree, click Domains."
+msgstr "在导航栏左侧树中，单击域。"
+
+# a9bff41fd28c435cbb09170c5b103277
+#: ../../usage.rst:334
+msgid ""
+"Select the domain you want to modify. The current domain limits are "
+"displayed."
+msgstr "选择你想修改的域。当前域限制将被显示出来。"
+
+# 519c174598aa4e55b86e899664c75018
+# 182d21886ebb4a09aebb0ef93e1fba63
+#: ../../usage.rst:337 ../../usage.rst:408
+msgid "A value of -1 shows that there is no limit in place."
+msgstr "值为-1表明此处没有任何限制。"
+
+# b83647ec9f344cccbf360b1f8b85c119
+#: ../../usage.rst:339
+msgid "Click the Edit button |editbutton.png|"
+msgstr "单击编辑按钮 |editbutton.png|"
+
+# c209d72330bd40f887995563563a6337
+# 99aa0e22f71d481eb51b72047c456f3a
+#: ../../usage.rst:341 ../../usage.rst:412
+msgid "Edit the following as per your requirement:"
+msgstr "编辑下列每一条要求："
+
+# cd271c3e43ea4c79a12f3f84924b6307
+# f889d8a628fd4b0ba7972855f0dbdc45
+#: ../../usage.rst:347 ../../usage.rst:418
+msgid "Instance Limits"
+msgstr "实例限制："
+
+# 5ef71e88c22848aeb261dfceed3f0ad3
+#: ../../usage.rst:349
+msgid "The number of instances that can be used in a domain."
+msgstr "可以被用在域中的实例的个数"
+
+# 8eb91b3c4b884b1886b84388b430c4b5
+# 50f79b10ffa84d4e8d63df31d54a18bc
+#: ../../usage.rst:351 ../../usage.rst:424
+msgid "Public IP Limits"
+msgstr "公共IP限制"
+
+# 9c123828b8bd44759ea889e13f4ab4bb
+#: ../../usage.rst:353
+msgid "The number of public IP addresses that can be used in a domain."
+msgstr "可以被用在域中的公共IP地址的个数。"
+
+# 682adde29cb64e42b391dcb5e5cdc9ad
+# f9ffeebe6c1a4111ab27c1b8d080143f
+#: ../../usage.rst:355 ../../usage.rst:430
+msgid "Volume Limits"
+msgstr "卷限制"
+
+# 57ca197f678f416c961a36d6a71f9bf5
+#: ../../usage.rst:357
+msgid "The number of disk volumes that can be created in a domain."
+msgstr "可以被创建在雨中的磁盘卷的个数"
+
+# 014dffd5f65443088674d2ee9df38979
+# ae967a3a9a714ab2892d18c80a55f652
+#: ../../usage.rst:359 ../../usage.rst:436
+msgid "Snapshot Limits"
+msgstr "快照限制"
+
+# 11f338d7f95041eaa7b84b9960a9f12f
+#: ../../usage.rst:361
+msgid "The number of snapshots that can be created in a domain."
+msgstr "可以被创建在域中的快照个数"
+
+# 07a01397e2404e18a667da23df9e7bf3
+# 6ba3ca1a17df418cac4387d71ddd7656
+#: ../../usage.rst:363 ../../usage.rst:442
+msgid "Template Limits"
+msgstr "模板限制"
+
+# 6dc70a7ce5ec48f3bcf254b4a20b4145
+#: ../../usage.rst:365
+msgid "The number of templates that can be registered in a domain."
+msgstr "可以在域中注册的模板数量"
+
+# 3bf5c725f231453cb6152f1bade12d17
+# 0b2a474b089d426d850f25818db1d152
+#: ../../usage.rst:367 ../../usage.rst:448
+msgid "VPC limits"
+msgstr "VPC限制"
+
+# 6041d380cc8b460e838d34d542c0fe6f
+#: ../../usage.rst:369
+msgid "The number of VPCs that can be created in a domain."
+msgstr "可以被创建在域中的VPC的个数"
+
+# 6167d0a236e346cdac41980cca4b61a1
+# efac374c510144af805a206947596f0d
+#: ../../usage.rst:371 ../../usage.rst:454
+msgid "CPU limits"
+msgstr "CPU限制"
+
+# c3bb1f4173a04335bd9f9a2aa60ffb7f
+#: ../../usage.rst:373
+msgid "The number of CPU cores that can be used for a domain."
+msgstr "可以在域中使用的CPU核心数。"
+
+# 5b77e8eb1eed4b89a6add832c6efa78d
+# 0f97c6c6f6bd48d49582e4a5773420a0
+#: ../../usage.rst:375 ../../usage.rst:460
+msgid "Memory limits (MB)"
+msgstr "内存限制(MB)"
+
+# 46ff0275d44b492790fbf06cfcc202f9
+#: ../../usage.rst:377
+msgid "The number of RAM that can be used for a domain."
+msgstr "可以在域中使用的RAM数量。"
+
+# cfada3bdc3304c91b6093699cc7aba26
+# e09ca8ab179747818fc4be09918773c3
+#: ../../usage.rst:379 ../../usage.rst:466
+msgid "Primary Storage limits (GB)"
+msgstr "主存储限制(GB)"
+
+# fadd0e1341ce4a40a364f8e7e5cbd720
+#: ../../usage.rst:381
+msgid "The primary storage space that can be used for a domain."
+msgstr "在域中可以使用的主存储空间大小。"
+
+# 94e6ad3512c64a968eba503aae4228e9
+# 88b20b1a22f5450abfd0371827b8a662
+#: ../../usage.rst:383 ../../usage.rst:472
+msgid "Secondary Storage limits (GB)"
+msgstr "辅助存储限制(GB)"
+
+# af7bbd32f2d744bbb6bc8bc38f2a6fff
+#: ../../usage.rst:385
+msgid "The secondary storage space that can be used for a domain."
+msgstr "在域中可使用的辅助存储空间大小。"
+
+# 9c4e390eeaf74125aff2fabb290d7508
+# 8554c878b3db4319b1e9ff271f3f2e16
+#: ../../usage.rst:387 ../../usage.rst:478
+msgid "Click Apply."
+msgstr "点击应用"
+
+# 0aea17dfad1c43818257b74482bdc4ec
+#: ../../usage.rst:391
+msgid "Default Account Resource Limits"
+msgstr "默认账户资源限制"
+
+# 5aec04d06e414d8c85567ee7ad5fa5a2
+#: ../../usage.rst:393
+msgid ""
+"You can limit resource use by accounts. The default limits are set by using "
+"Global configuration parameters, and they affect all accounts within a "
+"cloud. The relevant parameters are those beginning with max.account, for "
+"example: max.account.snapshots."
+msgstr "你可以限制账户使用的资源。默认限制通过全局配置参数设置，它们影响在云中的所有账户。其相关参数开始于max.account,例如:max.account.snapshots。"
+
+# 49c964b0ef8840ef953d87ef3115cf7f
+#: ../../usage.rst:398
+msgid ""
+"To override a default limit for a particular account, set a per-account "
+"resource limit."
+msgstr "对于覆盖一个默认限制的特殊账户，设置per-account资源限制。"
+
+# 7954a55684b74afbb3e48736fb619dfe
+#: ../../usage.rst:403
+msgid "In the left navigation tree, click Accounts."
+msgstr "在导航树左侧，单击账户。"
+
+# 30a0c7b93a044a24b1bbcab3362c9130
+#: ../../usage.rst:405
+msgid ""
+"Select the account you want to modify. The current limits are displayed."
+msgstr "选择你想修改的账户。当前限制将显示出来。"
+
+# 247dcfe79c914ac0a42c2bb5f617c3b2
+#: ../../usage.rst:410
+msgid "Click the Edit button. |editbutton.png|"
+msgstr "单击编辑按钮。|editbutton.png|"
+
+# a5b53a96d84f4cb993b2539562072ba0
+#: ../../usage.rst:420
+msgid "The number of instances that can be used in an account."
+msgstr "在一个账户中可以适用的实例个数。"
+
+# 4f148fb22eeb4cd5867de40af5d6957d
+# f6aef839dc7e4814a93524ac42691632
+# c8a80cc9dabc47b7908b2be9906b47e6
+# b1fc64706b924e37bcdf44b959b1a10b
+# a4c96e4f6931454c803ad5d310dd832a
+# 37ebe0cf9b3644a59962fb5255cd1e7c
+#: ../../usage.rst:422 ../../usage.rst:428 ../../usage.rst:434
+#: ../../usage.rst:440 ../../usage.rst:446 ../../usage.rst:452
+msgid "The default is 20."
+msgstr "默认是20个。"
+
+# b71498e20d9c45f5b4e6246502846b7a
+#: ../../usage.rst:426
+msgid "The number of public IP addresses that can be used in an account."
+msgstr "在账户中可以使用的公共IP地址个数。"
+
+# a7a78f1d32244bd7ae3f36a8706565ec
+#: ../../usage.rst:432
+msgid "The number of disk volumes that can be created in an account."
+msgstr "在账户中可以创建的磁盘卷个数。"
+
+# f22d973606cc4fe68cdf2ef0d22fb7b9
+#: ../../usage.rst:438
+msgid "The number of snapshots that can be created in an account."
+msgstr "在账户中可以创建的快照数量。"
+
+# 78aa50a7ed74400c8d0a3bcc278ed06b
+#: ../../usage.rst:444
+msgid "The number of templates that can be registered in an account."
+msgstr "在账户中可以注册的模板数量。"
+
+# 17544e59335b42c2b1dcb5439be274a4
+#: ../../usage.rst:450
+msgid "The number of VPCs that can be created in an account."
+msgstr "在账户中可以创建的VPC数量。"
+
+# dab1fd7da66d424fa313f0a8da2fd672
+#: ../../usage.rst:456
+msgid "The number of CPU cores that can be used for an account."
+msgstr "在账户中可以使用的CPU内核的个数。"
+
+# f8813118e7014ec4b09e2ce57e9826a0
+#: ../../usage.rst:458
+msgid "The default is 40."
+msgstr "默认是40。"
+
+# 5ee54380b1c7418aa85f1b4aa3d18f5c
+#: ../../usage.rst:462
+msgid "The number of RAM that can be used for an account."
+msgstr "在账户中可以使用的RAM数量。"
+
+# 463fe26a18c747bdba2e4c943174df89
+#: ../../usage.rst:464
+msgid "The default is 40960."
+msgstr "默认值是40960。"
+
+# 483d95c867804bd7a67bd7c5db5d7250
+#: ../../usage.rst:468
+msgid "The primary storage space that can be used for an account."
+msgstr "在账户中可以使用的主存储空间。"
+
+# b5792f85ad5748629247339cddc34442
+#: ../../usage.rst:470
+msgid "The default is 200."
+msgstr "默认是200。"
+
+# cf2794b976cb4597a1c7c46023d92939
+#: ../../usage.rst:474
+msgid "The secondary storage space that can be used for an account."
+msgstr "在账户中可以使用的辅助存储空间。"
+
+# e31012695d1342b893a7afc797d9efc8
+#: ../../usage.rst:476
+msgid "The default is 400."
+msgstr "默认是400。"
+
+# 58fd1b50da564cbfbe626a0c715242a2
+#: ../../usage.rst:482
+msgid "Usage Record Format"
+msgstr "使用记录格式"
+
+# bd6e6ad5dd4441038efbfa8256d54fbb
+#: ../../usage.rst:485
+msgid "Virtual Machine Usage Record Format"
+msgstr "虚拟机使用记录格式"
+
+# f4090312493645f999618d3518704fe4
+#: ../../usage.rst:487
+msgid ""
+"For running and allocated virtual machine usage, the following fields exist "
+"in a usage record:"
+msgstr "对运行或者已分配虚拟机使用，下列字段存在于使用记录中："
+
+# 1ea8ad4e82f849199566823e669d2e60
+# cb746968f7ea4c6eaeae3a8696c37487
+# 800271ae9863449db8b5d5a7a20f41be
+# 40d84f3b7c0243a2b680c8c5ee6fe699
+# b060e5d0dfc94db5a3dc884d3afc9829
+# 34a867e377074d8b8b7a9d16f17250f8
+#: ../../usage.rst:490 ../../usage.rst:531 ../../usage.rst:590
+#: ../../usage.rst:624 ../../usage.rst:685 ../../usage.rst:719
+msgid "account – name of the account"
+msgstr "account--账户的名字"
+
+# 0c884e63b3b6479d8ee0a652be74d5d4
+# 374676d104da4bb795381a260c95ddf1
+# cdf46e85f5ce46b6b29adc8183f20bc5
+# 0afdb6434c584c61acb197cf1a10f04c
+# 871a1002f0e34f38a9d8b6511ac9c04e
+# e13b8b9c705048e583810469fcd0a485
+#: ../../usage.rst:492 ../../usage.rst:533 ../../usage.rst:592
+#: ../../usage.rst:626 ../../usage.rst:687 ../../usage.rst:721
+msgid "accountid – ID of the account"
+msgstr "accountid--账户的ID"
+
+# 422137b0ab2b4696a321d367b6d26f6d
+# 86455aead7614969ab37a2e295a26530
+# 0c7934f2579a497cb68757e53895fe18
+# cd40f5f568ed41969adeb774e54813da
+# bdd3a9da32134e1e8ca88e1d720abcef
+# e797f39fdbc04ecbbbe2bdc559a0b118
+#: ../../usage.rst:494 ../../usage.rst:535 ../../usage.rst:594
+#: ../../usage.rst:628 ../../usage.rst:689 ../../usage.rst:723
+msgid "domainid – ID of the domain in which this account resides"
+msgstr "domainid --在此账户存在的域的 ID"
+
+# d938ef5bbcc140c3a43fe372485e16af
+# 0e8bcce04fb34321a8e64ed6f0511dc6
+# 989ad97f092f4ef38b22b0112e749925
+# a74af98e8b4f4970805d2c13cdf90c37
+# 07ebb7ef423743fa8f659f3ab930b615
+# 7f6481f066a049c68b8df922020b9f23
+#: ../../usage.rst:496 ../../usage.rst:537 ../../usage.rst:596
+#: ../../usage.rst:630 ../../usage.rst:691 ../../usage.rst:725
+msgid "zoneid – Zone where the usage occurred"
+msgstr "zoneid – 使用资源域的ID号"
+
+# 603607ff4edb47e9a79f7310b5606576
+# 54a63f2835ce4ebcab6a5e8f61822468
+# 6c1cd88b31ef47699a96c86e2dc2fd57
+# a97e62aec444404ba90732a66e38ba16
+# 851e49d28b7748bc84040d925da26fc0
+# cdf33c6ee5c24ddd843c0c573f0236c9
+#: ../../usage.rst:498 ../../usage.rst:539 ../../usage.rst:598
+#: ../../usage.rst:632 ../../usage.rst:693 ../../usage.rst:727
+msgid "description – A string describing what the usage record is tracking"
+msgstr "description – 字符描述，用于追查使用量的记录"
+
+# 18c681fd6a6d4db7ac9c8d0c14546df8
+#: ../../usage.rst:500
+msgid ""
+"usage – String representation of the usage, including the units of usage "
+"(e.g. 'Hrs' for VM running time)"
+msgstr "usage – 代表使用量的文字，包括使用量的单位(如 'Hrs'代表虚机运行时间)"
+
+# b56f48c2ce7e4ef8a421781cd8ac72d9
+# 367c8fbc6c3040e1b454649a311e5f24
+# 7a9a014a24af4f13afdf4091e920b2c7
+# 5ea8dfa3838546fea2bc64e05c8c673a
+# 3d7a93e77f944490999348ecfa138347
+# 65753a35c9384d9488a6ba39494069d9
+# 72b65cd48a914780a818c78d2b39df45
+# defb130ed24d43fcbdd05f28d6551b33
+#: ../../usage.rst:503 ../../usage.rst:541 ../../usage.rst:603
+#: ../../usage.rst:637 ../../usage.rst:698 ../../usage.rst:704
+#: ../../usage.rst:732 ../../usage.rst:738
+msgid "usagetype – A number representing the usage type (see Usage Types)"
+msgstr "usagetype – 代表使用量类型的数字 (参见使用量类型)"
+
+# dead7906f5ff49c88d8e41f0a3140bd3
+# 8ee236cbfec44c23a571ce1209509110
+# 51b806027dda42548e0b46c7e5f0c468
+# 2b60dfbda65048239a38cba051b05cd8
+# da840cc63b26444a8154da21e65d5f6b
+# 0f380999106d476eae77a3f78ab9bd69
+#: ../../usage.rst:505 ../../usage.rst:543 ../../usage.rst:605
+#: ../../usage.rst:639 ../../usage.rst:700 ../../usage.rst:734
+msgid "rawusage – A number representing the actual usage in hours"
+msgstr "rawusage – 代表以小时为单位实时使用量的数字"
+
+# e398aeba3cd0401992be1f2f12e5fc91
+# e9e71b3111f84185baca323877a352fd
+# 28490f43f8cd44f4bf26a2abb77429ed
+#: ../../usage.rst:507 ../../usage.rst:708 ../../usage.rst:710
+msgid "virtualMachineId – The ID of the virtual machine"
+msgstr "virtualMachineId – 虚拟服务器的ID号"
+
+# adce21eabe0243be8c394e06dd5f7790
+#: ../../usage.rst:509
+msgid "name – The name of the virtual machine"
+msgstr "name - 虚机名称"
+
+# 6b520c414595424cad27b0ae57527c1f
+#: ../../usage.rst:511
+msgid "offeringid – The ID of the service offering"
+msgstr "offeringid - 计算方案的ID"
+
+# 9329a1f52e57454a9b515f46ce1e110c
+#: ../../usage.rst:513
+msgid ""
+"templateid – The ID of the template or the ID of the parent template. The "
+"parent template value is present when the current template was created from "
+"a volume."
+msgstr "templateid – 模版或父模版的ID。当模版是从磁盘卷创建时，此处会使用父模版的ID。"
+
+# d061eac093024ebb867ea323cb34bbc0
+#: ../../usage.rst:517
+msgid "usageid – Virtual machine"
+msgstr "usageid -- 虚拟机"
+
+# 047ce224b91448ba964e79cc572efd1e
+# db530f7238e94cb295d4cf30edceb4bc
+#: ../../usage.rst:519 ../../usage.rst:611
+msgid "type – Hypervisor"
+msgstr "type - 虚拟化平台"
+
+# 13784faf965d4cae937aa6cdbbb601b3
+# f723716e1445424cbc729bcae6910bae
+# 193cb9ce321c4844bfc67c7421b46b78
+# 3362120577564331af89079c96e60819
+# 48e9160ce71b475d961c452d6984a6fc
+# ed62c302bb274df094275fbf56674a91
+#: ../../usage.rst:521 ../../usage.rst:549 ../../usage.rst:617
+#: ../../usage.rst:650 ../../usage.rst:712 ../../usage.rst:740
+msgid ""
+"startdate, enddate – The range of time for which the usage is aggregated; "
+"see Dates in the Usage Record"
+msgstr "startdate, enddate –一定时间内的使用量总和; 参见 使用量记录中的日期"
+
+# eedaa3906dfd445e8bccefccc0c58cf6
+#: ../../usage.rst:526
+msgid "Network Usage Record Format"
+msgstr "网络用量记录格式"
+
+# a62195cc17e14143a58822cf0c485c0e
+#: ../../usage.rst:528
+msgid ""
+"For network usage (bytes sent/received), the following fields exist in a "
+"usage record."
+msgstr "网络用量(发送/接收字节数)记录中存在以下字段："
+
+# e2aa41ae9fda438280903d7de43e9fa7
+#: ../../usage.rst:545
+msgid "usageid – Device ID (virtual router ID or external device ID)"
+msgstr "usageid - 设备ID(虚拟路由器ID或外部设备ID)"
+
+# cba1335aecd94359b17f04495d757350
+#: ../../usage.rst:547
+msgid "type – Device type (domain router, external load balancer, etc.)"
+msgstr "type - 设备类型(虚拟路由器、外部负载均衡等)"
+
+# f60aa591df79401691c6f36e9a9372cd
+#: ../../usage.rst:554
+msgid "IP Address Usage Record Format"
+msgstr "IP地址使用记录格式"
+
+# 8c83a518ebf94bda95be14bed415fbdd
+#: ../../usage.rst:556
+msgid "For IP address usage the following fields exist in a usage record."
+msgstr "对于IP地址使用下列字段存在于使用记录中。"
+
+# 872facde9d324938a2dc358b6f91d3d6
+# a38435a4207846d386ed6690dbeb757c
+#: ../../usage.rst:558 ../../usage.rst:657
+msgid "account - name of the account"
+msgstr "account - 账户的名称"
+
+# c2361416c29c4fbd838cca88df7fce39
+# bc06c74f16144181bca49330654a8470
+#: ../../usage.rst:560 ../../usage.rst:659
+msgid "accountid - ID of the account"
+msgstr "accountid-账户的ID"
+
+# 7ad667e8f90242c5b4cacb1421dc53a2
+# e6e2d964ef1a4c8b94bc42f08beea530
+#: ../../usage.rst:562 ../../usage.rst:661
+msgid "domainid - ID of the domain in which this account resides"
+msgstr "domainid-本账户具有的鱼的ID"
+
+# c05809fe04764a479c42fe337b8f32a7
+# 051704b34aa84fecb879697aa4461b9c
+#: ../../usage.rst:564 ../../usage.rst:663
+msgid "zoneid - Zone where the usage occurred"
+msgstr "zoneid-已经使用的域ID"
+
+# ef2388373bf042c79862477f5068f84f
+# ac7162ddbf9b4f07a70378f7cb4f1376
+#: ../../usage.rst:566 ../../usage.rst:665
+msgid "description - A string describing what the usage record is tracking"
+msgstr "description – 字符描述追查用量记录"
+
+# 680a2939f1ab4cd0b4c7d7ba19346be0
+#: ../../usage.rst:568
+msgid ""
+"usage - String representation of the usage, including the units of usage"
+msgstr "usage – 代表使用量的字符串，包括使用量的单位 "
+
+# 552772e8c5f745518dc6484ef776e37b
+# 8b658740424143e0804a450732cc90d5
+# 79adc7a2a02248f8a0ee7771272a5624
+#: ../../usage.rst:571 ../../usage.rst:670 ../../usage.rst:676
+msgid "usagetype - A number representing the usage type (see Usage Types)"
+msgstr "usagetype – 代表使用量类型的数字 (参见使用量类型)"
+
+# 565c646fcbed4427bf835e888529e76c
+# af9345ffb0554f0eb0ad166c00406ea8
+#: ../../usage.rst:573 ../../usage.rst:672
+msgid "rawusage - A number representing the actual usage in hours"
+msgstr "rawusage – 代表以小时为单位实时使用量的数字"
+
+# 1ce3b40124484eefb27601e1907f939a
+#: ../../usage.rst:575
+msgid "usageid - IP address ID"
+msgstr "usageid-IP地址ID"
+
+# abfd139b052e4864afc695aba432783c
+# a5cbc24cefb54a2996cf860cf2b1e75c
+#: ../../usage.rst:577 ../../usage.rst:678
+msgid ""
+"startdate, enddate - The range of time for which the usage is aggregated; "
+"see Dates in the Usage Record"
+msgstr "startdate, enddate – 一定时间范围内的用量总和; 参见 用量记录中的日期"
+
+# 7631780188e9474f8a1041b55d0ac20b
+#: ../../usage.rst:580
+msgid "issourcenat - Whether source NAT is enabled for the IP address"
+msgstr "issourcenat - IP地址的NAT资源是否有效"
+
+# 85f7d46f4fd5425cad1b87a37ec9ecf7
+#: ../../usage.rst:582
+msgid "iselastic - True if the IP address is elastic."
+msgstr "iselastic - 如果IP地址是弹性的为True"
+
+# fd56a0a694804aa884be5fdefcfd3320
+#: ../../usage.rst:586
+msgid "Disk Volume Usage Record Format"
+msgstr "磁盘用量记录格式"
+
+# dc66789696474008bbbc81eb24bec679
+#: ../../usage.rst:588
+msgid "For disk volumes, the following fields exist in a usage record."
+msgstr "对于磁盘，用量记录存在下列字段。"
+
+# 4a12e3d8b23f40078657c836a946af1e
+# d33548fd1fe240509c2c86f75c6bd701
+# 38cb41b0bdc94d2e94ee5c3a6492e281
+# 95202bd84a0e4a61991829c07c2c0720
+#: ../../usage.rst:600 ../../usage.rst:634 ../../usage.rst:695
+#: ../../usage.rst:729
+msgid ""
+"usage – String representation of the usage, including the units of usage "
+"(e.g. 'Hrs' for hours)"
+msgstr "usage – 代表使用量的文字，包括使用量的单位 (如 'Hrs'是小时)"
+
+# c2f1554e72084e81892a0b538a19c7f8
+#: ../../usage.rst:607
+msgid "usageid – The volume ID"
+msgstr "usageid - 磁盘ID"
+
+# b7525535c67b49b98b4d922f07293bcb
+# c781024621454a418e050f006e91921c
+#: ../../usage.rst:609 ../../usage.rst:643
+msgid "offeringid – The ID of the disk offering"
+msgstr "offeringid - 磁盘方案的ID"
+
+# 543db09e00804cd787e00be0867a5c6e
+#: ../../usage.rst:613
+msgid "templateid – ROOT template ID"
+msgstr "templateid - 根模版ID"
+
+# f2ab3e39617449bf8a68f1fbc0eb4fbe
+#: ../../usage.rst:615
+msgid "size – The amount of storage allocated"
+msgstr "size - 分配的存储大小"
+
+# e54797d2c60c4441ac584d3abb0f9c77
+#: ../../usage.rst:622
+msgid "Template, ISO, and Snapshot Usage Record Format"
+msgstr "模版、ISO和快照用量记录格式"
+
+# 60eda22a3c7d4756847f64ff53b961e2
+#: ../../usage.rst:641
+msgid "usageid – The ID of the the template, ISO, or snapshot"
+msgstr "usageid - 模版、ISO或快照的ID"
+
+# 3562063eefc04af28187703974e45228
+#: ../../usage.rst:645
+msgid ""
+"templateid – – Included only for templates (usage type 7). Source template "
+"ID."
+msgstr "templateid -- 仅模版（用量类型为7）时包括。源模版ID。"
+
+# 9fbfbc974f184b2983595a2d4fed5cdb
+#: ../../usage.rst:648
+msgid "size – Size of the template, ISO, or snapshot"
+msgstr "size - 模版、ISO或快照的大小"
+
+# aa26900876304f758262788c79483c44
+#: ../../usage.rst:655
+msgid "Load Balancer Policy or Port Forwarding Rule Usage Record Format"
+msgstr "负载均衡策略或端口导向用量记录格式"
+
+# f493ad9446bd4b0d84e50c9937d2b21c
+#: ../../usage.rst:667
+msgid ""
+"usage - String representation of the usage, including the units of usage "
+"(e.g. 'Hrs' for hours)"
+msgstr "usage – 代表使用量的字符串，包括使用量的单位 (如 'Hrs'是小时)"
+
+# 03d262a193f246749d1ed6f6df6d3930
+#: ../../usage.rst:674
+msgid "usageid - ID of the load balancer policy or port forwarding rule"
+msgstr "usageid -负载均衡或端口导向规则ID"
+
+# b01513d3fd8e466ba943f21dd926c03a
+#: ../../usage.rst:683
+msgid "Network Offering Usage Record Format"
+msgstr "网络服务方案用量记录格式"
+
+# d5c5360548e6437882e13f383f854c51
+#: ../../usage.rst:702
+msgid "usageid – ID of the network offering"
+msgstr "usageid – 网络服务方案的ID"
+
+# 1dd0260b113b4149979baeec2b430e69
+#: ../../usage.rst:706
+msgid "offeringid – Network offering ID"
+msgstr "offeringid – 网络服务方案的ID"
+
+# 2e3b410e70064b95997310d4b2f2d6bb
+#: ../../usage.rst:717
+msgid "VPN User Usage Record Format"
+msgstr "VPN用户用量记录格式"
+
+# 78984789b8f74fcb9ae0dc8712b092fa
+#: ../../usage.rst:736
+msgid "usageid – VPN user ID"
+msgstr "usageid - VPN用户ID"
+
+# 371ab2afddac4c8ebe7b59df3a7e3150
+#: ../../usage.rst:745
+msgid "Usage Types"
+msgstr "用量类型"
+
+# bb807347fed448728c3e17662b8b1ebc
+#: ../../usage.rst:747
+msgid "The following table shows all usage types."
+msgstr "下表显示了所有的用量类型。"
+
+# 9d81d10d8b5343f19edc1316cfbf4854
+#: ../../usage.rst:750
+msgid "Type ID"
+msgstr "类型ID"
+
+# e5f69db4f5e44d94804a6a1fa96b3da8
+#: ../../usage.rst:750
+msgid "Type Name"
+msgstr "类型名称"
+
+# 78ead0d9336c42648a3ca740bc0c71c3
+#: ../../usage.rst:752
+msgid "1"
+msgstr "1"
+
+# e747e335348c4f96b8157b30a1f87074
+#: ../../usage.rst:752
+msgid "RUNNING\\_VM"
+msgstr "RUNNING\\_VM"
+
+# 477ac63f7f36460ea08116c949753044
+#: ../../usage.rst:752
+msgid ""
+"Tracks the total running time of a VM per usage record period. If the VM is "
+"upgraded during the usage period, you will get a separate Usage Record for "
+"the new upgraded VM."
+msgstr "追踪VM每个用量记录时期所有运行时间总和。如果VM在用量时期升级，你将会获得新升级后的VM单独的用量记录。"
+
+# 64af61ae9a154740bc59c51cf93b8e50
+#: ../../usage.rst:762
+msgid "2"
+msgstr "2"
+
+# 7e1e8fb7beaf45439e7683227a55abb7
+#: ../../usage.rst:762
+msgid "ALLOCATED\\_VM"
+msgstr "ALLOCATED\\_VM"
+
+# 12dcdffa3a2f4d5faaece0b8ee808625
+#: ../../usage.rst:762
+msgid ""
+"Tracks the total time the VM has been created to the time when it has been "
+"destroyed. This usage type is also useful in determining usage for specific "
+"templates such as Windows-based templates."
+msgstr "追踪VM从创建到销毁的所有时间总和。这个用量类型也是在终止例如 Windows-based模板这样的具体模板用量上是有用的。"
+
+# 56a5110004de419981e5f220ae4e8552
+#: ../../usage.rst:774
+msgid "3"
+msgstr "3"
+
+# 9300fc0a0c054c8cb8cf1c50a798ccfe
+#: ../../usage.rst:774
+msgid "IP\\_ADDRESS"
+msgstr "IP\\_ADDRESS"
+
+# bdd7930fce7d439cac6b82c99e189623
+#: ../../usage.rst:774
+msgid "Tracks the public IP address owned by the account."
+msgstr "追踪拥有公共IP地址的账户"
+
+# 8f41c0480a214679a34ebff91433884a
+#: ../../usage.rst:778
+msgid "4"
+msgstr "4"
+
+# 3468bfe1926344ed8b778f78f298e356
+#: ../../usage.rst:778
+msgid "NETWORK\\_BYTES\\_SENT"
+msgstr "NETWORK\\_BYTES\\_SENT"
+
+# 4fc69e9acd00430db5d7bdd162d53a88
+#: ../../usage.rst:778
+msgid ""
+"Tracks the total number of bytes sent by all the VMs for an account. "
+"Cloud.com does not currently track network traffic per VM."
+msgstr "追踪一个账户发送所有VM的比特的总时间。Cloud.com不仅追踪当前网络传输时的每个VM。"
+
+# 9c0a0d79a0ee491b99fc2f18847a9c29
+#: ../../usage.rst:786
+msgid "5"
+msgstr "5"
+
+# 8053534caf9a43cfbe6f344918e90568
+#: ../../usage.rst:786
+msgid "NETWORK\\_BYTES\\_RECEIVED"
+msgstr "NETWORK\\_BYTES\\_RECEIVED"
+
+# a09f77e6b1d540fdb4c9e398f8042f22
+#: ../../usage.rst:786
+msgid ""
+"Tracks the total number of bytes received by all the VMs for an account. "
+"Cloud.com does not currently track network traffic per VM."
+msgstr "追踪一个账户接受所有VM的比特的总时间。Cloud.com不仅追踪当前网络传输时的每个VM。"
+
+# 5d8944a3cb7d444aa82efaa09053af2d
+#: ../../usage.rst:795
+msgid "6"
+msgstr "6"
+
+# bd9f4acea1a34fb5ada48e39c65e7781
+#: ../../usage.rst:795
+msgid "VOLUME"
+msgstr "VOLUME"
+
+# e39b0cb9d477433db943c1dfbeb90bb5
+#: ../../usage.rst:795
+msgid ""
+"Tracks the total time a disk volume has been created to the time when it has"
+" been destroyed."
+msgstr "追踪磁盘从创建到销毁的总时间。"
+
+# fb74bed3e64f40f4b1b99833cdfb858b
+#: ../../usage.rst:801
+msgid "7"
+msgstr "7"
+
+# 8dbe0a482b8740bcaba3e70100493143
+#: ../../usage.rst:801
+msgid "TEMPLATE"
+msgstr "TEMPLATE"
+
+# e01ba5c82149495a87253a75e8f1ee5c
+#: ../../usage.rst:801
+msgid ""
+"Tracks the total time a template (either created from a snapshot or uploaded"
+" to the cloud) has been created to the time it has been destroyed. The size "
+"of the template is also returned."
+msgstr "追踪模板（包含从快照中创建的或是已经上传到云的）从创建到销毁的总时间。模板的大小也被返回。"
+
+# ea46b251003a4703b4db0e8e9ca83a4a
+#: ../../usage.rst:812
+msgid "8"
+msgstr "8"
+
+# f349c4660c004c8f81133723f6ac350c
+#: ../../usage.rst:812
+msgid "ISO"
+msgstr "ISO"
+
+# 7c32db79c4a944e294459472e67ef9a5
+#: ../../usage.rst:812
+msgid ""
+"Tracks the total time an ISO has been uploaded to the time it has been "
+"removed from the cloud. The size of the ISO is also returned."
+msgstr "追踪ISO在云中从上传到移除的总时间。ISO的大小也被返回。"
+
+# b0dacdf41a1c4d989f2f39ef17257ecc
+#: ../../usage.rst:820
+msgid "9"
+msgstr "9"
+
+# 1405b90e80e34b8381a814756e95d768
+#: ../../usage.rst:820
+msgid "SNAPSHOT"
+msgstr "SNAPSHOT"
+
+# e5fa93c081164375acc3fd52345b1187
+#: ../../usage.rst:820
+msgid ""
+"Tracks the total time from when a snapshot has been created to the time it "
+"have been destroyed."
+msgstr "追踪快照从创建到销毁的总时间。"
+
+# 4f2594d3f1f24d2c9169fcfc149a62e9
+#: ../../usage.rst:826
+msgid "11"
+msgstr "11"
+
+# d37ae3d5c27447e4a1078346d90a373f
+#: ../../usage.rst:826
+msgid "LOAD\\_BALANCER\\_POLICY"
+msgstr "LOAD\\_BALANCER\\_POLICY"
+
+# 024b703ada76417194235a1d10290b53
+#: ../../usage.rst:826
+msgid ""
+"Tracks the total time a load balancer policy has been created to the time it"
+" has been removed. Cloud.com does not track whether a VM has been assigned "
+"to a policy."
+msgstr "追踪负载均衡策略从创建到移除的总时间。Cloud.com不追踪VM是否已经分配到了的策略。"
+
+# 6ebb8ff8421347ba8d0f37e13f9738a1
+#: ../../usage.rst:836
+msgid "12"
+msgstr "12"
+
+# 4f5ff172a156494c910377d3273476ca
+#: ../../usage.rst:836
+msgid "PORT\\_FORWARDING\\_RULE"
+msgstr "PORT\\_FORWARDING\\_RULE"
+
+# 00141f10a4c040fd9c1981d4c44a5d6b
+#: ../../usage.rst:836
+msgid ""
+"Tracks the time from when a port forwarding rule was created until the time "
+"it was removed."
+msgstr "追踪端口导向规则从创建到移除的时间。"
+
+# bc4b98fcdabc461a8ede71b5285838b0
+#: ../../usage.rst:842
+msgid "13"
+msgstr "13"
+
+# 6123d10ab7004c9b943a532e894e2e20
+#: ../../usage.rst:842
+msgid "NETWORK\\_OFFERING"
+msgstr "NETWORK\\_OFFERING"
+
+# ec1c84a50ae5471ba6539ff923b81caa
+#: ../../usage.rst:842
+msgid ""
+"The time from when a network offering was assigned to a VM until it is "
+"removed."
+msgstr "从网络方案分配到VM到移除的时间。"
+
+# 04d219bbd49540e7a4d433b51cb42d2b
+#: ../../usage.rst:847
+msgid "14"
+msgstr "14"
+
+# d70576ee50674251a6ee58e7a072795a
+#: ../../usage.rst:847
+msgid "VPN\\_USERS"
+msgstr "VPN\\_USERS"
+
+# 7031f45ce0894436b7ab77616de3681f
+#: ../../usage.rst:847
+msgid "The time from when a VPN user is created until it is removed."
+msgstr "计时从VPN用户创建时开始，移除时结束。"
+
+# da745a0b82b6445e998e6d31a0f107b7
+#: ../../usage.rst:854
+msgid "Example response from listUsageRecords"
+msgstr "listUsageRecords指令的反应示例："
+
+# 73da4de663384d6ba278d517dc44eeef
+#: ../../usage.rst:856
+msgid ""
+"All CloudStack API requests are submitted in the form of a HTTP GET/POST "
+"with an associated command and any parameters. A request is composed of the "
+"following whether in HTTP or HTTPS:"
+msgstr "所有CloudStack API请求都是以HTTP GET/POST形式提交, 同时附上相关的命令和参数. 无论是HTTP或HTTPS, 一个请求都有以下内容组成:"
+
+# b1267ab3f74744b8966d6c8dce38d38a
+#: ../../usage.rst:888
+msgid "Dates in the Usage Record"
+msgstr "在使用记录中的数据"
+
+# f9638c3a7a0c4939922d9b03330f3a5a
+#: ../../usage.rst:890
+msgid ""
+"Usage records include a start date and an end date. These dates define the "
+"period of time for which the raw usage number was calculated. If daily "
+"aggregation is used, the start date is midnight on the day in question and "
+"the end date is 23:59:59 on the day in question (with one exception; see "
+"below). A virtual machine could have been deployed at noon on that day, "
+"stopped at 6pm on that day, then started up again at 11pm. When usage is "
+"calculated on that day, there will be 7 hours of running VM usage (usage "
+"type 1) and 12 hours of allocated VM usage (usage type 2). If the same "
+"virtual machine runs for the entire next day, there will 24 hours of both "
+"running VM usage (type 1) and allocated VM usage (type 2)."
+msgstr "用量记录包含了开始日期和结束日期。这些日期定义了原始用量数字的统计时间阶段。如果每天统计被使用，开始日期是问题出现的的当天午夜，结束日期是问题(关于异常，参见本内容）出现的当天23:59:59。虚拟机可以被部署到当天正午，在次日6pm,然后在11pm重启。在用量统计的当天，将有7小时运行VM用量(用量类型1)和12个小时分配VM用量(用量类型2)。如果同一个VM完全运行到下一天，将会有24小时的运行VM用量(类型1)和已分配用量(类型2)。"
+
+# aa505995145d4de796ce7a54c69e8c04
+#: ../../usage.rst:902
+msgid ""
+"Note: The start date is not the time a virtual machine was started, and the "
+"end date is not the time when a virtual machine was stopped. The start and "
+"end dates give the time range within which usage was calculated."
+msgstr "注意：开始日期不是虚拟机启动时间，结束日期不是虚拟机停止时间。开始日期和结束日期在用量统计的给定范围内。"
+
+# ffee51b332cd4e589de90c6abf2b8476
+#: ../../usage.rst:907
+msgid ""
+"For network usage, the start date and end date again define the range in "
+"which the number of bytes transferred was calculated. If a user downloads 10"
+" MB and uploads 1 MB in one day, there will be two records, one showing the "
+"10 megabytes received and one showing the 1 megabyte sent."
+msgstr "对于网络用量，开始日期和结束日期定义为一定数量的比特传输统计的时间范围。如果用户一天内下载10MB并上传1M，将会有两个记录，一个显示10MB接受和一个显示1MB发送。"
+
+# de58fb769cc74ed3a62616b4158bd9e8
+#: ../../usage.rst:913
+msgid ""
+"There is one case where the start date and end date do not correspond to "
+"midnight and 11:59:59pm when daily aggregation is used. This occurs only for"
+" network usage records. When the usage server has more than one day's worth "
+"of unprocessed data, the old data will be included in the aggregation "
+"period. The start date in the usage record will show the date and time of "
+"the earliest event. For other types of usage, such as IP addresses and VMs, "
+"the old unprocessed data is not included in daily aggregation."
+msgstr "当每日统计使用时，只有一种情况开始日期和结束日期不响应午夜到11:59:59。它仅发生在网络用量记录。当用量记录服务器有超过一天的未处理数据时，旧数据将被包含在统计区间内。用量记录中的开始日期将显示最早的事件的日期和时间。对于其它类型的用量，例如IP地址和VM,旧的未处理数据是不包含在每日统计中的。"
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/virtual_machines.mo b/source/adminguide/locale/zh_CN/LC_MESSAGES/virtual_machines.mo
new file mode 100644
index 0000000..a80a5dc
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/virtual_machines.mo
Binary files differ
diff --git a/source/adminguide/locale/zh_CN/LC_MESSAGES/virtual_machines.po b/source/adminguide/locale/zh_CN/LC_MESSAGES/virtual_machines.po
new file mode 100644
index 0000000..656bdba
--- /dev/null
+++ b/source/adminguide/locale/zh_CN/LC_MESSAGES/virtual_machines.po
@@ -0,0 +1,2048 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C)
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: 2014-06-30 12:05+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-administration-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 825181279d9643c3ae9e1a485765f79a
+#: ../../virtual_machines.rst:18
+msgid "Working with Virtual Machines"
+msgstr "使用虚拟机"
+
+# 8ef9955cc01742fb833f6f4cb20ddc40
+#: ../../virtual_machines.rst:21
+msgid "About Working with Virtual Machines"
+msgstr "关于虚拟机的使用"
+
+# 5dfc79c076ae4bcf9b78cbc7e7998fb1
+#: ../../virtual_machines.rst:23
+msgid ""
+"CloudStack provides administrators with complete control over the lifecycle "
+"of all guest VMs executing in the cloud. CloudStack provides several guest "
+"management operations for end users and administrators. VMs may be stopped, "
+"started, rebooted, and destroyed."
+msgstr "CloudStack在云中为管理员提供了完整的管理所有来宾VMs整个生命周期的功能。CloudStack为终端用户和管理员提供了许多来宾虚机管理操作。VMs能被关机、开机、重启和销毁。"
+
+# a74753cd5a1e4e87b2b25bb214d76583
+#: ../../virtual_machines.rst:28
+msgid ""
+"Guest VMs have a name and group. VM names and groups are opaque to "
+"CloudStack and are available for end users to organize their VMs. Each VM "
+"can have three names for use in different contexts. Only two of these names "
+"can be controlled by the user:"
+msgstr "来宾VMs有名称和组。VM的名称和组对于CloudStack是不透明的，对终端用户整理他们的VMs可用。每个VM可以有三个用于不同环境的名称。其中有两个名字受用户控制："
+
+# 33b7dd1035fe468788852c131410d355
+#: ../../virtual_machines.rst:33
+msgid ""
+"Instance name – a unique, immutable ID that is generated by CloudStack and "
+"can not be modified by the user. This name conforms to the requirements in "
+"IETF RFC 1123."
+msgstr "实例名称 – 一个唯一的，不可变的由CloudStack生成的ID，此ID不能被用户修改。此名称符合 IETF RFC 1123中的要求。"
+
+# f1b72ed931524f89a7d072ed361a635e
+#: ../../virtual_machines.rst:37
+msgid ""
+"Display name – the name displayed in the CloudStack web UI. Can be set by "
+"the user. Defaults to instance name."
+msgstr "显示名称 – 在CloudStack UI中显示的名称。可以由用户设置。默认跟实例名称一致。"
+
+# adc0efb3ff154603a38bf9294009ac65
+#: ../../virtual_machines.rst:40
+msgid ""
+"Name – host name that the DHCP server assigns to the VM. Can be set by the "
+"user. Defaults to instance name"
+msgstr "名称 – 由DHCP服务器分配给VM的主机名。可以由用户设置。默认跟实例名称一致。"
+
+# 14d2256532ea4ba9ab19bed35890856a
+#: ../../virtual_machines.rst:44
+msgid ""
+"You can append the display name of a guest VM to its internal name. For more"
+" information, see `“Appending a Display Name to the Guest VM’s Internal "
+"Name” <#appending-a-display-name-to-the-guest-vms-internal-name>`_."
+msgstr "你能把来宾VM的显示名附加到它的内部名称上。更多信息，请参考 `“将显示名附加到VM的内部名称” <#appending-a-display-name-to-the-guest-vms-internal-name>`_."
+
+# a8d661456c4f45b28ad427c44e9b6325
+#: ../../virtual_machines.rst:48
+msgid ""
+"Guest VMs can be configured to be Highly Available (HA). An HA-enabled VM is"
+" monitored by the system. If the system detects that the VM is down, it will"
+" attempt to restart the VM, possibly on a different host. For more "
+"information, see HA-Enabled Virtual Machines on"
+msgstr "来宾VMs可以配置成高可用（HA）。启用了HA的VM由系统监控。如果系统检测到此VM宕机，它可能将尝试在不同的主机上重启VM。更多信息，请参考在虚拟机上启用HA"
+
+# 5305c3fec9d94b62aa5980618331557e
+#: ../../virtual_machines.rst:53
+msgid ""
+"Each new VM is allocated one public IP address. When the VM is started, "
+"CloudStack automatically creates a static NAT between this public IP address"
+" and the private IP address of the VM."
+msgstr "每个新VM都有一个公共网络IP地址。当VM启动后，CloudStack为此VM的公共网络IP地址与内网IP地址自动创建一个静态NAT。"
+
+# 587dd3d141fc46bca48b617989e96f59
+#: ../../virtual_machines.rst:57
+msgid ""
+"If elastic IP is in use (with the NetScaler load balancer), the IP address "
+"initially allocated to the new VM is not marked as elastic. The user must "
+"replace the automatically configured IP with a specifically acquired elastic"
+" IP, and set up the static NAT mapping between this new IP and the guest "
+"VM’s private IP. The VM’s original IP address is then released and returned "
+"to the pool of available public IPs. Optionally, you can also decide not to "
+"allocate a public IP to a VM in an EIP-enabled Basic zone. For more "
+"information on Elastic IP, see `“About Elastic IP” <networking2.html#about-"
+"elastic-ip>`_."
+msgstr "如果使用了弹性IP（与Netscaler负载均衡同时使用），初始分配给新VM的IP地址并没有标记为弹性的。用户必须将自动配置IP改为获得一个弹性IP，并在新IP与来宾VM的内网IP之间设置静态NAT映射。VM的原始IP地址随后会被释放到可用公共网络IPs池中。同样，你也可以在启用了EIP的基础zone中不为VM分配公网IP。关于弹性IP的更多信息，请参考`“关于弹性IP” <networking2.html#about-elastic-ip>`_。"
+
+# 6fbeb0da9ef448f98d0a7a11b1032be6
+#: ../../virtual_machines.rst:67
+msgid ""
+"CloudStack cannot distinguish a guest VM that was shut down by the user "
+"(such as with the “shutdown” command in Linux) from a VM that shut down "
+"unexpectedly. If an HA-enabled VM is shut down from inside the VM, "
+"CloudStack will restart it. To shut down an HA-enabled VM, you must go "
+"through the CloudStack UI or API."
+msgstr "CloudStack不能区分是VM突然关机还是用户对来宾VM进行的关机操作（像Linux中的“shutdown”命令）。如果从启用了HA功能的VM系统中执行了关机操作，CloudStack会重启它。要对启用了HA功能的VM进行关机操作，你必须通过CloudStack UI或者API。"
+
+# 9787aabb3dc94e8db7a5de0c51ea7443
+#: ../../virtual_machines.rst:75
+msgid "Best Practices for Virtual Machines"
+msgstr "虚拟机的最佳实践"
+
+# 6372fe37d9ed4beeb1424ae97b03ad24
+#: ../../virtual_machines.rst:77
+msgid ""
+"For VMs to work as expected and provide excellent service, follow these "
+"guidelines."
+msgstr "为了让VMs能够按照预期的工作并提供最好的服务，请按照下面的指导进行操作。"
+
+# d2a792bb33c2418bba1e90839b5208d4
+#: ../../virtual_machines.rst:82
+msgid "Monitor VMs for Max Capacity"
+msgstr "监视VMs的最大容量"
+
+# aaa155f7b055496592fb19179ed93f73
+#: ../../virtual_machines.rst:84
+msgid ""
+"The CloudStack administrator should monitor the total number of VM instances"
+" in each cluster, and disable allocation to the cluster if the total is "
+"approaching the maximum that the hypervisor can handle. Be sure to leave a "
+"safety margin to allow for the possibility of one or more hosts failing, "
+"which would increase the VM load on the other hosts as the VMs are "
+"automatically redeployed. Consult the documentation for your chosen "
+"hypervisor to find the maximum permitted number of VMs per host, then use "
+"CloudStack global configuration settings to set this as the default limit. "
+"Monitor the VM activity in each cluster at all times. Keep the total number "
+"of VMs below a safe level that allows for the occasional host failure. For "
+"example, if there are N hosts in the cluster, and you want to allow for one "
+"host in the cluster to be down at any given time, the total number of VM "
+"instances you can permit in the cluster is at most (N-1) \\* (per-host-"
+"limit). Once a cluster reaches this number of VMs, use the CloudStack UI to "
+"disable allocation of more VMs to the cluster."
+msgstr "管理员应该监视每个集群中的虚拟机实例的总数，如果总量快达到hypervisor允许的最大虚拟机数量时，不再向此群集分配虚拟机。并且，要注意为主机预留一定的计算能力，以防止群集中有主机发生故障,因为发生故障的主机上的虚拟机需要重新部署在这些预留主机上。请咨询您所选择hypervisor的文档，了解此hypervisor能支持的最大虚拟机数量，并将此数值设置在CloudStack的全局设置里。监控每个群集里虚拟机的活跃程序，并将活跃虚拟机保持在一个安全线内。这样，CloudStack就能允许偶尔的主机故障。举个示例：如果集群里有N个主机，而你只能让其中任一主机的停机时间不超过特定时间。那么，你能在此集群部署的最多虚拟主机数量值为：(N-1) \\* (每主机最大虚拟量数量限值)。一旦群集中的虚拟机达到此数量，必须在CloudStack的用户界面中禁止向此群集分配新的虚拟机。"
+
+# e6554027f7f9466a8a5ab12bbbf30fb9
+#: ../../virtual_machines.rst:103
+msgid "Install Required Tools and Drivers"
+msgstr "安装需要的工具和驱动"
+
+# 6b07dcd845a944ea872a6ace009f7f24
+#: ../../virtual_machines.rst:105
+msgid "Be sure the following are installed on each VM:"
+msgstr "确认在每个VM上都安装了下列软件和驱动："
+
+# 31fe2e3e61ec4b15865970eafecc35df
+#: ../../virtual_machines.rst:107
+msgid ""
+"For XenServer, install PV drivers and Xen tools on each VM. This will enable"
+" live migration and clean guest shutdown. Xen tools are required in order "
+"for dynamic CPU and RAM scaling to work."
+msgstr "对于XenServer，在每个VM上安装PV驱动和Xen tools。这将启用动态迁移和干净的来宾虚机关机。安装Xen tools也是为了使动态的CPU和RAM扩展能够工作。"
+
+# 59c6618b482a4e8590293c7da8aaf7ef
+#: ../../virtual_machines.rst:111
+msgid ""
+"For vSphere, install VMware Tools on each VM. This will enable console view "
+"to work properly. VMware Tools are required in order for dynamic CPU and RAM"
+" scaling to work."
+msgstr "对于vSphere，在每台VM上安装VMware Tools。这是为了能让控制台查看正常工作。安装VMware Tools也是为了使动态的CPU和RAM扩展能够工作。"
+
+# 0054a653c9ee4d008cb5fff30bcb3de8
+#: ../../virtual_machines.rst:115
+msgid ""
+"To be sure that Xen tools or VMware Tools is installed, use one of the "
+"following techniques:"
+msgstr "使用下面其中一个方法确认已经安装了Xen tools或VMware Tools："
+
+# 183593c0142745a49f4f2a3791981e31
+#: ../../virtual_machines.rst:118
+msgid ""
+"Create each VM from a template that already has the tools installed; or,"
+msgstr "从已经安装了tools的模板创建的每个VM；或者，"
+
+# 4ad9dec1226046d48a5dba3598abbf0a
+#: ../../virtual_machines.rst:121
+msgid ""
+"When registering a new template, the administrator or user can indicate "
+"whether tools are installed on the template. This can be done through the UI"
+" or using the updateTemplate API; or,"
+msgstr "当注册一个新的模板时，管理员或者用户可以标示出哪个在模板上安装了tools。这可以通过UI或者使用updateTemplate API来做；或者，"
+
+# 3a12a213c40345018c066a0ec37e65a9
+#: ../../virtual_machines.rst:125
+msgid ""
+"If a user deploys a virtual machine with a template that does not have Xen "
+"tools or VMware Tools, and later installs the tools on the VM, then the user"
+" can inform CloudStack using the updateVirtualMachine API. After installing "
+"the tools and updating the virtual machine, stop and start the VM."
+msgstr "如果用户通过一个没有安装Xen tools或者VMware Tools的模板部署虚机，然后在VM上安装了tools，之后用户可以使用updateVirtualMachine API告知CloudStack。在安装tools和更新虚拟机之后，请重启虚拟机。"
+
+# b7a0169d017a496787e38b9e50311a88
+#: ../../virtual_machines.rst:133
+msgid "VM Lifecycle"
+msgstr "虚拟机的生命周期"
+
+# 0af797cf30df4ac984c7b8d11ede977e
+#: ../../virtual_machines.rst:135
+msgid "Virtual machines can be in the following states:"
+msgstr "虚拟机可能处于下列状态："
+
+# f5d2991885b4440f8c7062a60633f065
+#: ../../virtual_machines.rst:137
+msgid "|basic-deployment.png|"
+msgstr "|basic-deployment.png|"
+
+# 4c2d3ebcce3744b481035492578b6e3c
+#: ../../virtual_machines.rst:139
+msgid ""
+"Once a virtual machine is destroyed, it cannot be recovered. All the "
+"resources used by the virtual machine will be reclaimed by the system. This "
+"includes the virtual machine’s IP address."
+msgstr "一旦一个虚拟机被销毁，那么它就不能被恢复。该虚拟机使用的所有资源被系统回收。其中包括虚拟机的IP地址。"
+
+# 08c95a701e5348e789bd295aa7819d86
+#: ../../virtual_machines.rst:143
+msgid ""
+"A stop will attempt to gracefully shut down the operating system, which "
+"typically involves terminating all the running applications. If the "
+"operation system cannot be stopped, it will be forcefully terminated. This "
+"has the same effect as pulling the power cord to a physical machine."
+msgstr "停止操作是比较稳妥的关闭操作系统的方式，因为这样做能正常的关闭所有正在运行的应用程序。如果操作系统不能被停止，才要强制关闭它。这么做跟拔掉物理机器的电源线是一个效果。"
+
+# 6d5fb2afbc1e44ad842f052187cc201f
+#: ../../virtual_machines.rst:149
+msgid "A reboot is a stop followed by a start."
+msgstr "重启是关机再开机的过程。"
+
+# eb78f755807e4fe59ff45bc534fa6dc5
+#: ../../virtual_machines.rst:151
+msgid ""
+"CloudStack preserves the state of the virtual machine hard disk until the "
+"machine is destroyed."
+msgstr "CloudStack会保存虚机硬盘的状态直到它被销毁。"
+
+# e18941c1f49b40d4ae53034763c41e57
+#: ../../virtual_machines.rst:154
+msgid ""
+"A running virtual machine may fail because of hardware or network issues. A "
+"failed virtual machine is in the down state."
+msgstr "正在运行的虚机可能会因为硬件或者网络故障而出现问题。出现问题的虚机是down状态。"
+
+# 73bd5337e5854464a320f36cca3d4964
+#: ../../virtual_machines.rst:157
+msgid ""
+"The system places the virtual machine into the down state if it does not "
+"receive the heartbeat from the hypervisor for three minutes."
+msgstr "如果系统在三分钟内收不到hypervisor的心跳信号，那么它就会将虚机切换至down状态。"
+
+# a45ff69a534b47189b4457ff2d058d8c
+#: ../../virtual_machines.rst:160
+msgid "The user can manually restart the virtual machine from the down state."
+msgstr "用户能够手动从down状态下重启虚机。"
+
+# 42d0a445aab2404abad8ce54e6ff5947
+#: ../../virtual_machines.rst:162
+msgid ""
+"The system will start the virtual machine from the down state automatically "
+"if the virtual machine is marked as HA-enabled."
+msgstr "如果虚机被标记上启用了HA，那么系统会自动地重启down状态中的虚机。"
+
+# fdeb58579e7749fe88bdf405f79049e5
+#: ../../virtual_machines.rst:167
+msgid "Creating VMs"
+msgstr "创建VMs"
+
+# 7453d7d0a14e4a9dab16d5580766c5d5
+#: ../../virtual_machines.rst:169
+msgid ""
+"Virtual machines are usually created from a template. Users can also create "
+"blank virtual machines. A blank virtual machine is a virtual machine without"
+" an OS template. Users can attach an ISO file and install the OS from the CD"
+"/DVD-ROM."
+msgstr "虚拟机通常是从模板创建的。用户也能创建空白虚拟机。空白虚拟机就是一个重新安装的操作系统。用户可以通过CD/DVD-ROM加载ISO文件安装。"
+
+# 3edf15d4b2054f90ae481e9bde143346
+#: ../../virtual_machines.rst:175
+msgid ""
+"You can create a VM without starting it. You can determine whether the VM "
+"needs to be started as part of the VM deployment. A request parameter, "
+"startVM, in the deployVm API provides this feature. For more information, "
+"see the Developer's Guide."
+msgstr "你可以创建一个VM，但不要启动它。你来决定此VM是否需要作为VM部署的一部分而启动。在deployVm API里面提供了一个startVM参数，提供了这个功能。更多信息，请参考开发者指导。"
+
+# e3cf740a72c247ea8cdb5ff298a2e7b3
+#: ../../virtual_machines.rst:180
+msgid "To create a VM from a template:"
+msgstr "从模板创建一个VM。"
+
+# 6b4fb12f7826449389052e48b175bf9a
+# 1c346e18dafd4ac7977a7dc98d85926c
+# 4d63920f853642a68b92f2632d3a1ba1
+# d667b7df24994fc4ac857e47436efd5d
+#: ../../virtual_machines.rst:182 ../../virtual_machines.rst:212
+#: ../../virtual_machines.rst:330 ../../virtual_machines.rst:366
+msgid "Log in to the CloudStack UI as an administrator or user."
+msgstr "用管理员或用户账号登录CloudStack UI。"
+
+# 243b4d8b914d49d19dd68312aae2042a
+# fbbc9105a1f14883918e0460b902a681
+# 74fc4567c9104ff0ae51ec0d88dc5006
+#: ../../virtual_machines.rst:184 ../../virtual_machines.rst:214
+#: ../../virtual_machines.rst:368
+msgid "In the left navigation bar, click Instances."
+msgstr "在左侧导航栏，点击实例"
+
+# be1be45993694cb6ab943a5c229ac71e
+# 7d1b7b4f15c349c68567df62e225bc34
+#: ../../virtual_machines.rst:186 ../../virtual_machines.rst:216
+msgid "Click Add Instance."
+msgstr "点击添加实例。"
+
+# 64202b2c542d459596118bf9dd4ad508
+# 7f1cbee620c946a88f43e9b6c8f1e9bf
+#: ../../virtual_machines.rst:188 ../../virtual_machines.rst:218
+msgid "Select a zone."
+msgstr "选择一个区域。"
+
+# a0aa0f810b974edcb1d8f305c1b24a5d
+#: ../../virtual_machines.rst:190
+msgid ""
+"Select a template, then follow the steps in the wizard. For more information"
+" about how the templates came to be in this list, see `*Working with "
+"Templates* <templates.html>`_."
+msgstr "选择一个模板，然后按照向导中的步骤操作。更多关于如何上传模板的更多信息，请参考`*使用模板* <templates.html>`_。"
+
+# 33bbf5e131484a929c10053278adddde
+#: ../../virtual_machines.rst:194
+msgid ""
+"Be sure that the hardware you have allows starting the selected service "
+"offering."
+msgstr "确认你的硬件设备满足运行所选的服务条件。"
+
+# 9a01eecf26a748e198056df4f7e9b825
+# 82109b204e5841308ff5e74b12cf24a4
+#: ../../virtual_machines.rst:197 ../../virtual_machines.rst:222
+msgid "Click Submit and your VM will be created and started."
+msgstr "点击提交，你的VM就会被创建并启动。"
+
+# 7a2965e6d5004b7088a5e5bc18da649c
+#: ../../virtual_machines.rst:200
+msgid ""
+"For security reason, the internal name of the VM is visible only to the root"
+" admin."
+msgstr "出于安全原因，VM的内部名称仅root管理员可见。"
+
+# c19e66233eaa4d00b5b615550ebc0c11
+#: ../../virtual_machines.rst:203
+msgid "To create a VM from an ISO:"
+msgstr "从ISO创建虚拟机："
+
+# ff3d83c8dc1b40baab04b8c1bcfe3619
+#: ../../virtual_machines.rst:206
+msgid ""
+"(XenServer) Windows VMs running on XenServer require PV drivers, which may "
+"be provided in the template or added after the VM is created. The PV drivers"
+" are necessary for essential management functions such as mounting "
+"additional volumes and ISO images, live migration, and graceful shutdown."
+msgstr "(XenServer)XXenServer上运行的Windows VMs需要安装PV驱动，它可能在模板中或在创建完VM后添加。PV驱动对于基本的管理功能是必要的，比如挂载额外的卷和ISO镜像、在线迁移和正常关机。"
+
+# aceacbbcfec4422e939ff1ed89aa25c5
+#: ../../virtual_machines.rst:220
+msgid "Select ISO Boot, and follow the steps in the wizard."
+msgstr "选择ISO启动，然后按照向导中的步骤进行操作。"
+
+# a843dc7f749c44d89ba116d3c6af89f8
+#: ../../virtual_machines.rst:226
+msgid "Accessing VMs"
+msgstr "访问VMs"
+
+# 0bf035db01dd401abc60fc76e71330ba
+#: ../../virtual_machines.rst:228
+msgid ""
+"Any user can access their own virtual machines. The administrator can access"
+" all VMs running in the cloud."
+msgstr "任何用户都可以访问他们自己的虚拟机。管理员能够访问在云中运行的所有虚拟机。"
+
+# ff40a54bdc2e4f3f8b310d37998c096b
+# b719e6aa6218441b864dbd9dbb664b20
+#: ../../virtual_machines.rst:231 ../../virtual_machines.rst:555
+msgid "To access a VM through the CloudStack UI:"
+msgstr "通过CloudStack UI访问VM："
+
+# 72fdf34366e84d53a902f30170e96826
+# 3b5b89a3e29346439a79e6c9625ab11a
+# 5d3ec5e17ef1449a85064c70381209dc
+# 151cdfe9cd414184908d5b1c15cc7de9
+# 995bd5571b2446418ec4a6f27a17fe5f
+#: ../../virtual_machines.rst:233 ../../virtual_machines.rst:557
+#: ../../virtual_machines.rst:618 ../../virtual_machines.rst:792
+#: ../../virtual_machines.rst:820
+msgid "Log in to the CloudStack UI as a user or admin."
+msgstr "使用用户或管理员登录到CloudStack用户界面。"
+
+# c09833ddb4424c4e82d2b49397dbf82e
+#: ../../virtual_machines.rst:235
+msgid "Click Instances, then click the name of a running VM."
+msgstr "点击实例，然后点击运行VM的名字。"
+
+# 7276130f1e014d969cbd9246b1310121
+#: ../../virtual_machines.rst:237
+msgid "Click the View Console button |console-icon.png|."
+msgstr "点击查看控制台按钮 |console-icon.png|。"
+
+# c06df9b367c1493a908523e863cade69
+#: ../../virtual_machines.rst:239
+msgid "To access a VM directly over the network:"
+msgstr "通过网络直接访问VM："
+
+# 3a9997d1c0444c66b00f908de1b14f74
+#: ../../virtual_machines.rst:241
+msgid ""
+"The VM must have some port open to incoming traffic. For example, in a basic"
+" zone, a new VM might be assigned to a security group which allows incoming "
+"traffic. This depends on what security group you picked when creating the "
+"VM. In other cases, you can open a port by setting up a port forwarding "
+"policy. See `“IP Forwarding and Firewalling” <networking2.html#ip-"
+"forwarding-and-firewalling>`_."
+msgstr "VM必须开通相关端口以便外部访问。比如，在基础zone中，新的VM可能被关联到一个允许流量进入的安全组。但这取决于你在创建VM的时候选择的安全组。在其他情况下，你可以通过设置端口转发策略来打开一个端口。请参考 `“IP转发及防火墙” <networking2.html#ip-forwarding-and-firewalling>`_。"
+
+# aa1d9ea00c0f47d58155e9aa67793a80
+#: ../../virtual_machines.rst:248
+msgid ""
+"If a port is open but you can not access the VM using ssh, it’s possible "
+"that ssh is not already enabled on the VM. This will depend on whether ssh "
+"is enabled in the template you picked when creating the VM. Access the VM "
+"through the CloudStack UI and enable ssh on the machine using the commands "
+"for the VM’s operating system."
+msgstr "如果打开端口后，你仍然不能使用SSH访问VM，那么可能是VM中没有启用SSH。这取决于当你创建VM的时候选的模板是否启用了SSH。通过CloudStack UI访问VM，然后使用VM操作系统中的命令行启用SSH。"
+
+# af42226ae2f845c4ae39472cd44d62cf
+#: ../../virtual_machines.rst:254
+msgid ""
+"If the network has an external firewall device, you will need to create a "
+"firewall rule to allow access. See `“IP Forwarding and Firewalling” "
+"<networking2.html#ip-forwarding-and-firewalling>`_."
+msgstr "如果网络中有外部防火墙设备，你需要创建一个防火墙策略来允许访问。请参考`“IP转发及防火墙” <networking2.html#ip-forwarding-and-firewalling>`_。"
+
+# 334cb66ea0fd46fab55d62d6c94401cc
+#: ../../virtual_machines.rst:260
+msgid "Stopping and Starting VMs"
+msgstr "停止和启动VMs"
+
+# 194b6682b53b4c028e9387e57f318392
+#: ../../virtual_machines.rst:262
+msgid ""
+"Once a VM instance is created, you can stop, restart, or delete it as "
+"needed. In the CloudStack UI, click Instances, select the VM, and use the "
+"Stop, Start, Reboot, and Destroy buttons."
+msgstr "一旦VM实例被创建，你可以根据需要停止、重启或删除它。在CloudStack UI里，点击实例，选择VM，然后使用停止、启动、重启和销毁按钮。"
+
+# 3475020a222a4190b9e4e184a4be143c
+#: ../../virtual_machines.rst:268
+msgid "Assigning VMs to Hosts"
+msgstr "将VMs指定到主机"
+
+# ab04e4134ad1499abbfb64970cd8d83b
+#: ../../virtual_machines.rst:270
+msgid ""
+"At any point in time, each virtual machine instance is running on a single "
+"host. How does CloudStack determine which host to place a VM on? There are "
+"several ways:"
+msgstr "在任何时刻，每个虚拟机实例都运行在一台主机上。CloudStack如何决定在哪个主机上放置VM呢？通常是这几种方式："
+
+# c9fcda8e47454c1b9ccdd115dc618ffb
+#: ../../virtual_machines.rst:274
+msgid ""
+"Automatic default host allocation. CloudStack can automatically pick the "
+"most appropriate host to run each virtual machine."
+msgstr "自动分配默认主机。CloudStack可以自动的选取最合适的主机来运行每个虚机。"
+
+# 13722d82fe934c8fbe47baadf772e4b3
+#: ../../virtual_machines.rst:277
+msgid ""
+"Instance type preferences. CloudStack administrators can specify that "
+"certain hosts should have a preference for particular types of guest "
+"instances. For example, an administrator could state that a host should have"
+" a preference to run Windows guests. The default host allocator will attempt"
+" to place guests of that OS type on such hosts first. If no such host is "
+"available, the allocator will place the instance wherever there is "
+"sufficient physical capacity."
+msgstr "实例类型偏好设置。CloudStack管理员可以指定专门为某些特殊来宾实例做过优化的主机。比如，管理员指定为Windows来宾实例做过优化的主机。默认主机分配器会尝试将此类来宾实例运行到这些主机上。如果这些主机不够用，分配器会把实例运行在容量充足的物理机上。"
+
+# a32cedb1c3d54276bafa87b47914776e
+#: ../../virtual_machines.rst:285
+msgid ""
+"Vertical and horizontal allocation. Vertical allocation consumes all the "
+"resources of a given host before allocating any guests on a second host. "
+"This reduces power consumption in the cloud. Horizontal allocation places a "
+"guest on each host in a round-robin fashion. This may yield better "
+"performance to the guests in some cases."
+msgstr "纵向和横向定位。纵向定位是指，在消耗完当前主机提供的所有资源的时候会将所有来宾虚机定位到第二台主机上。这会云中的节省电力成本。横向定位在每个主机上使用轮询的方式放置来宾虚机。在某些情况下这样会给来宾虚机带来更好的性能。"
+
+# cc5699db1af34f3a9b499307c558a058
+#: ../../virtual_machines.rst:291
+msgid ""
+"End user preferences. Users can not control exactly which host will run a "
+"given VM instance, but they can specify a zone for the VM. CloudStack is "
+"then restricted to allocating the VM only to one of the hosts in that zone."
+msgstr "最终用户偏好设置。用户不能控制VM实例运行在哪台主机上，但是他们能为VM指定区域。这样CloudStack就只能将VM分配到该区域中的主机上。"
+
+# 0411284295194622b05a0cb1879eeb76
+#: ../../virtual_machines.rst:296
+msgid ""
+"Host tags. The administrator can assign tags to hosts. These tags can be "
+"used to specify which host a VM should use. The CloudStack administrator "
+"decides whether to define host tags, then create a service offering using "
+"those tags and offer it to the user."
+msgstr "主机标签。管理员可以给主机分配标签。这些标签是用来指定VM该使用哪台主机的。CloudStack管理员自己决定如何定义主机标签，然后使用这些标签创建一个服务方案来提供给用户。"
+
+# ead4cb40fadd4eefa3f8eeddf36bea8e
+#: ../../virtual_machines.rst:301
+msgid ""
+"Affinity groups. By defining affinity groups and assigning VMs to them, the "
+"user or administrator can influence (but not dictate) which VMs should run "
+"on separate hosts. This feature is to let users specify that certain VMs "
+"won't be on the same host."
+msgstr "关联性组。依靠定义关联性组并把VMs分配给它们，用户或管理员可以影响(但不是指令)VMs运行在不同的主机上。这个功能是让用户可以规定某些VMs不会运行在同一台主机上。"
+
+# 475f207be88542b496285e35e6edb937
+#: ../../virtual_machines.rst:306
+msgid ""
+"CloudStack also provides a pluggable interface for adding new allocators. "
+"These custom allocators can provide any policy the administrator desires."
+msgstr "CloudStack为添加新的分配器提供了一个插件似的接口。这些自定义的分配器可以提供任何管理员想要的策略。"
+
+# 838c2813c99f4ea89cb67e8b2ff25abd
+#: ../../virtual_machines.rst:312
+msgid "Affinity Groups"
+msgstr "关联性组"
+
+# d72b6ebfff7246118fbc4df220e6f966
+#: ../../virtual_machines.rst:314
+msgid ""
+"By defining affinity groups and assigning VMs to them, the user or "
+"administrator can influence (but not dictate) which VMs should run on "
+"separate hosts. This feature is to let users specify that VMs with the same "
+"“host anti-affinity” type won’t be on the same host. This serves to increase"
+" fault tolerance. If a host fails, another VM offering the same service (for"
+" example, hosting the user's website) is still up and running on another "
+"host."
+msgstr "依靠定义关联性组并把VMs分配给它们，用户或管理员可以影响(但不是指令)VMs运行在不同的主机上。这个功能是让用户可以规定某些VMs运行在同“host anti-affinity”类型的而非同一台主机上。这写类服务器增强了容错功能。如果一个主机出现问题，那么另一个提供同样服务的VM(比如，运行用户的网站)依然在别的主机上运行。"
+
+# 7dad3924b6fe49e9b9e6ed13a6316bbf
+#: ../../virtual_machines.rst:322
+msgid "The scope of an affinity group is per user account."
+msgstr "一个关联性组的作用域是针对每个用户账号的。"
+
+# 537f3770162d4c7db20724e2cd3a6d25
+#: ../../virtual_machines.rst:326
+msgid "Creating a New Affinity Group"
+msgstr "创建一个新的关联性组"
+
+# 89ec84e3b1004702a136fe33ae40a620
+#: ../../virtual_machines.rst:328
+msgid "To add an affinity group:"
+msgstr "要添加一个关联性组："
+
+# 2e4c181542d24eceadbedafacef6a048
+# 129e5d65a94748d49cc72d49901d7982
+# bfe6c54e9b1d4b95b230d06a783465c2
+#: ../../virtual_machines.rst:332 ../../virtual_machines.rst:382
+#: ../../virtual_machines.rst:397
+msgid "In the left navigation bar, click Affinity Groups."
+msgstr "在左侧的导航条，点击关联性组。"
+
+# 2d49709c41b24dcfa6cbec72f9655ecb
+#: ../../virtual_machines.rst:334
+msgid ""
+"Click Add affinity group. In the dialog box, fill in the following fields:"
+msgstr "点击添加关联性组。在对话框中的下列区域中输入："
+
+# 8f2541aa578d480ab600f234860b710f
+#: ../../virtual_machines.rst:337
+msgid "Name. Give the group a name."
+msgstr "名称。组的名称。"
+
+# 283fc43838584136ada4a8670741a62f
+#: ../../virtual_machines.rst:339
+msgid ""
+"Description. Any desired text to tell more about the purpose of the group."
+msgstr "描述。给出更多关于这个组的说明。"
+
+# 6ad15d35202c4aa3829229be0b4dc5a3
+#: ../../virtual_machines.rst:342
+msgid ""
+"Type. The only supported type shipped with CloudStack is Host Anti-Affinity."
+" This indicates that the VMs in this group should avoid being placed on the "
+"same host with each other. If you see other types in this list, it means "
+"that your installation of CloudStack has been extended with customized "
+"affinity group plugins."
+msgstr ""
+
+# 9dd18a72cf94423295b7f4e16ebdd474
+#: ../../virtual_machines.rst:351
+msgid "Assign a New VM to an Affinity Group"
+msgstr "将一个新的VM分配给一个关联性组"
+
+# f986290eacc04fcd88cddb44e54dd110
+#: ../../virtual_machines.rst:353
+msgid "To assign a new VM to an affinity group:"
+msgstr "要将一个新的VM分配给一个关联性组："
+
+# b7ecd6311df24770b2f5ff16290be095
+#: ../../virtual_machines.rst:355
+msgid ""
+"Create the VM as usual, as described in `“Creating VMs” "
+"<virtual_machines.html#creating-vms>`_. In the Add Instance wizard, there is"
+" a new Affinity tab where you can select the affinity group."
+msgstr "如何创建VM，在 `“Creating VMs” <virtual_machines.html#creating-vms>`_中有描述。在添加实例向导中，有一个新的关联性组标签，你可以选择关联性组。"
+
+# d887ac9c84494254beaf5d7c2d1d8b17
+#: ../../virtual_machines.rst:362
+msgid "Change Affinity Group for an Existing VM"
+msgstr "给已有的VM更改关联性组"
+
+# ac05d8cab3d84c0fb5fecc7ff5be7a41
+#: ../../virtual_machines.rst:364
+msgid "To assign an existing VM to an affinity group:"
+msgstr "要将已有的VM添加到关联性组："
+
+# 406004d08a994c7e83f19eb8d3d5ccb4
+#: ../../virtual_machines.rst:370
+msgid "Click the name of the VM you want to work with."
+msgstr "点击你想更改的VM的名称。"
+
+# 5198d04fabab4aba81bb176cafd9cd5f
+#: ../../virtual_machines.rst:372
+msgid "Stop the VM by clicking the Stop button."
+msgstr "点击停止按钮，将此VM关机。"
+
+# d7c213c32fa64651beb6d71b29a2f881
+#: ../../virtual_machines.rst:374
+msgid "Click the Change Affinity button. |change-affinity-button.png|"
+msgstr "点击变更关联性组按钮。 |change-affinity-button.png|"
+
+# 7964ffac44554385887c85ac33410324
+#: ../../virtual_machines.rst:378
+msgid "View Members of an Affinity Group"
+msgstr "查看关联性组的成员"
+
+# 60958f4621bd45d68c4c4e5ff8e6166b
+#: ../../virtual_machines.rst:380
+msgid ""
+"To see which VMs are currently assigned to a particular affinity group:"
+msgstr "要查看当前哪些VMs被分配到指定的关联性组："
+
+# 44277c6e70cc49f5a0262172b42602cd
+# 84c34fd8f1024bc3b3b89c6074d25602
+#: ../../virtual_machines.rst:384 ../../virtual_machines.rst:399
+msgid "Click the name of the group you are interested in."
+msgstr "点击要查看的组的名称。"
+
+# d621ae0b24c54f108a31c5dc8cf05476
+#: ../../virtual_machines.rst:386
+msgid "Click View Instances. The members of the group are listed."
+msgstr "点击查看实例。组的成员会列在此处。"
+
+# 43f372265bc14aa89389bbc7b9584816
+#: ../../virtual_machines.rst:388
+msgid ""
+"From here, you can click the name of any VM in the list to access all its "
+"details and controls."
+msgstr "在这里，你可以点击列表中任何VM的名称来访问它所有的详细信息并控制它。"
+
+# c126741a86364834b153814dff481a58
+#: ../../virtual_machines.rst:393
+msgid "Delete an Affinity Group"
+msgstr "删除一个关联性组"
+
+# 41b2a9676116417a9cc26ddecd8e35c0
+#: ../../virtual_machines.rst:395
+msgid "To delete an affinity group:"
+msgstr "要删除关联性组："
+
+# 97c32e0a3b4d4a039f0167b916626e38
+#: ../../virtual_machines.rst:401
+msgid "Click Delete."
+msgstr "点击删除。"
+
+# 2f1e052c0a0441988e9ccb2459b64996
+#: ../../virtual_machines.rst:403
+msgid ""
+"Any VM that is a member of the affinity group will be disassociated from the"
+" group. The former group members will continue to run normally on the "
+"current hosts, but if the VM is restarted, it will no longer follow the host"
+" allocation rules from its former affinity group."
+msgstr "任何属于关联性组的VM都会被踢出此组。之前组里的成员会继续在当前主机上正常的运行，但是如果VM重启了，它就不再按照之前关联性组的主机分配策略。"
+
+# 1500b2cdf2f8433f9dc55740099c7554
+#: ../../virtual_machines.rst:411
+msgid "Virtual Machine Snapshots"
+msgstr "虚拟机快照"
+
+# 352168175d0f45c7944fb134e5e1ccb0
+# f1ff6b7e77974160b7eb0e268b6c8adf
+#: ../../virtual_machines.rst:413 ../../virtual_machines.rst:643
+msgid "(Supported on VMware and XenServer)"
+msgstr "(支持XenServer、KVM和VMware)"
+
+# 4b76741f3c964e48b09015a19ac9ffe6
+#: ../../virtual_machines.rst:415
+msgid ""
+"In addition to the existing CloudStack ability to snapshot individual VM "
+"volumes, you can take a VM snapshot to preserve all the VM's data volumes as"
+" well as (optionally) its CPU/memory state. This is useful for quick restore"
+" of a VM. For example, you can snapshot a VM, then make changes such as "
+"software upgrades. If anything goes wrong, simply restore the VM to its "
+"previous state using the previously saved VM snapshot."
+msgstr "利用CloudStack的VM卷快照功能，你可以对VM做快照像保存它的CPU/内存状态一样保护VM的数据卷(可选的)。这对快速还原一个VM来说是非常有用的。比如，你可以对一个VM做快照，然后做了一些像软件升级的操作。如果期间有问题出现，使用之前保存的VM快照就可以将VM恢复到之前的状态了。"
+
+# 9ea94fa6d9804e22af343c5c65a0362d
+#: ../../virtual_machines.rst:423
+msgid ""
+"The snapshot is created using the hypervisor's native snapshot facility. The"
+" VM snapshot includes not only the data volumes, but optionally also whether"
+" the VM is running or turned off (CPU state) and the memory contents. The "
+"snapshot is stored in CloudStack's primary storage."
+msgstr "快照的创建使用的是 hypervisor本地快照工具。VM快照不但包括数据卷还可选择性的包括VM的运行或关机时(CPU状态)和内存内容的状态。快照保存在CloudStack的主存储里。"
+
+# b710a2e6c248420bb55ebfa8f0f376dc
+#: ../../virtual_machines.rst:428
+msgid ""
+"VM snapshots can have a parent/child relationship. Each successive snapshot "
+"of the same VM is the child of the snapshot that came before it. Each time "
+"you take an additional snapshot of the same VM, it saves only the "
+"differences between the current state of the VM and the state stored in the "
+"most recent previous snapshot. The previous snapshot becomes a parent, and "
+"the new snapshot is its child. It is possible to create a long chain of "
+"these parent/child snapshots, which amount to a \"redo\" record leading from"
+" the current state of the VM back to the original."
+msgstr "VM快照存在父/子关系。同一个VM的每次快照都是之前快照的子级。每次你对同一VM追加的快照，它仅仅保存两次快照之间系统状态差异。之前的快照变成父级，新的快照变成子级。它可能对这些父/子快照创建一个长链，它实际上是一个从当前的VM状态还原到之前的\"还原\"记录。"
+
+# efe6658a42c34ba1badb3bb03008f9f0
+#: ../../virtual_machines.rst:438
+msgid ""
+"If you need more information about VM snapshots on VMware, check out the "
+"VMware documentation and the VMware Knowledge Base, especially "
+"`Understanding virtual machine snapshots "
+"<http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1015180>`_."
+msgstr "如果你需要了解更多关于VMware的VM快照，请转去VMware文档中心和VMwareBK库，查找 `了解虚拟机的快照-英文 <http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1015180>`_、`了解虚拟机的快照-中文<http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2075429>`_。"
+
+# 8fb9c61d831b4840801c19c568c3e2f7
+#: ../../virtual_machines.rst:445
+msgid "Limitations on VM Snapshots"
+msgstr "VM快照的限制"
+
+# b40a26e614ff482b83dd6fe7ca66a097
+#: ../../virtual_machines.rst:447
+msgid ""
+"If a VM has some stored snapshots, you can't attach new volume to the VM or "
+"delete any existing volumes. If you change the volumes on the VM, it would "
+"become impossible to restore the VM snapshot which was created with the "
+"previous volume structure. If you want to attach a volume to such a VM, "
+"first delete its snapshots."
+msgstr "如果一个VM存储了一些快照，你就不能给他附加新卷或删除存在的卷。如果你更改了VM的卷，他将不能通过之前卷结构下所做快照来进行恢复。如果你想给这样一个VM附加卷，请先删除快照。"
+
+# 137adaa8ad304bad8e6a62a539a5b277
+#: ../../virtual_machines.rst:453
+msgid ""
+"VM snapshots which include both data volumes and memory can't be kept if you"
+" change the VM's service offering. Any existing VM snapshots of this type "
+"will be discarded."
+msgstr "如果你更改了VM的服务方案，那么包含了数据卷和内存的VM快照就不能保留了，任何已有的此类型的VM快照都将被丢弃。"
+
+# 9890e43dc8174a959a93587c2843f753
+#: ../../virtual_machines.rst:457
+msgid ""
+"You can't make a VM snapshot at the same time as you are taking a volume "
+"snapshot."
+msgstr "你不能同时对VM在做卷快照和VM快照。"
+
+# 0ffbf8b4539648a4884ee457c3ab1cb1
+#: ../../virtual_machines.rst:460
+msgid ""
+"You should use only CloudStack to create VM snapshots on hosts managed by "
+"CloudStack. Any snapshots that you make directly on the hypervisor will not "
+"be tracked in CloudStack."
+msgstr "你只能使用CloudStack来创建其管理的主机上的VM快照。你在hypervisor上直接创建的任何快照都不能被CloudStack识别。"
+
+# 77f6cb8f4c0f41fcb04fe4aa2c2f5268
+#: ../../virtual_machines.rst:466
+msgid "Configuring VM Snapshots"
+msgstr "配置VM快照"
+
+# 8582f7496ba340e7b18f0ec535fc74c1
+#: ../../virtual_machines.rst:468
+msgid ""
+"The cloud administrator can use global configuration variables to control "
+"the behavior of VM snapshots. To set these variables, go through the Global "
+"Settings area of the CloudStack UI."
+msgstr "云管理员可以使用全局配置变量来控制VM快照的行为。要设置这些变量，移步至CloudStack UI中的全局设置。"
+
+# f9f9fa5a5bf040cf942989a479a5e690
+#: ../../virtual_machines.rst:472
+msgid "Configuration Setting Name"
+msgstr "配置设置名"
+
+# 68ee9c1c4d5a4d0b85ee63309d7b1db0
+#: ../../virtual_machines.rst:474
+msgid "Description"
+msgstr "描述"
+
+# 85763ceb28de4f0eaca494db0a967117
+#: ../../virtual_machines.rst:476
+msgid "vmsnapshots.max"
+msgstr "vmsnapshots.max"
+
+# 7466c6685f504780a8c5d77c5d580374
+#: ../../virtual_machines.rst:478
+msgid ""
+"The maximum number of VM snapshots that can be saved for any given virtual "
+"machine in the cloud. The total possible number of VM snapshots in the cloud"
+" is (number of VMs) \\* vmsnapshots.max. If the number of snapshots for any "
+"VM ever hits the maximum, the older ones are removed by the snapshot expunge"
+" job."
+msgstr "云中虚拟机能够保存快照的最大数。 (number of VMs) \\* vmsnapshots.max是云中VM快照的总共可能数量。如果任何一个VM的快照数达到了最大值，那么快照删除任务会把最老的快照删掉。"
+
+# 2fd939410c2b4b3aa8b3003ab8a3b968
+#: ../../virtual_machines.rst:484
+msgid "vmsnapshot.create.wait"
+msgstr "vmsnapshot.create.wait"
+
+# 375a0959e9c94eb1a423b278ae046b5b
+#: ../../virtual_machines.rst:486
+msgid ""
+"Number of seconds to wait for a snapshot job to succeed before declaring "
+"failure and issuing an error."
+msgstr "在提示失败和发生错误之前快照工作为了成功的做快照而等待的秒数。"
+
+# 2b92af396f6c475a81e3dd289b5b2058
+#: ../../virtual_machines.rst:491
+msgid "Using VM Snapshots"
+msgstr "是用VM的快照"
+
+# 936e0bc234f649d98911b973d2a89f24
+#: ../../virtual_machines.rst:493
+msgid "To create a VM snapshot using the CloudStack UI:"
+msgstr "是用CloudStack UI创建一个VM快照："
+
+# 7cd076f83efb4c1bbf3fd895f87582e8
+#: ../../virtual_machines.rst:495
+msgid "Log in to the CloudStack UI as a user or administrator."
+msgstr "是用用户或者管理员登录CloudStack。"
+
+# 79e76d457cf54a80bf3e15e93c930b60
+#: ../../virtual_machines.rst:497
+msgid "Click Instances."
+msgstr "点击实例。"
+
+# 271888c8e7844949b68a79c940659c7b
+#: ../../virtual_machines.rst:499
+msgid "Click the name of the VM you want to snapshot."
+msgstr "点击你想做快照的VM名称。"
+
+# e60b0597ab2c4b37b9c1b6e585208f39
+#: ../../virtual_machines.rst:501
+msgid "Click the Take VM Snapshot button. |VMSnapshotButton.png|"
+msgstr "点击抓取VM快照按钮。 |VMSnapshotButton.png|"
+
+# 516b8188c37544fe9289100fa8fd6f81
+#: ../../virtual_machines.rst:504
+msgid ""
+"If a snapshot is already in progress, then clicking this button will have no"
+" effect."
+msgstr "如果一个快照处理过程正在进行，那么点击这个按钮是没有反应的。"
+
+# 3af8f23237d44f6a82ff3805d8748f9b
+#: ../../virtual_machines.rst:507
+msgid ""
+"Provide a name and description. These will be displayed in the VM Snapshots "
+"list."
+msgstr "提供一个名称和秒数。这些会显示在VM快照列表中。"
+
+# 213a0335d6b44dc3a98d11a064dc6168
+#: ../../virtual_machines.rst:510
+msgid ""
+"(For running VMs only) If you want to include the VM's memory in the "
+"snapshot, click the Memory checkbox. This saves the CPU and memory state of "
+"the virtual machine. If you don't check this box, then only the current "
+"state of the VM disk is saved. Checking this box makes the snapshot take "
+"longer."
+msgstr "(仅限运行中的VMs)如果你想在快照中包含VM的内存状态，请勾选内存。这可以保存虚拟机的CPU和内存状态。如果你不勾选这个选项，那么只有VM目前磁盘状态会被保存。勾选了这个选项会让快照过程变长。"
+
+# d45f3edd0bc741a7a60bc61f1687caae
+#: ../../virtual_machines.rst:516
+msgid ""
+"Quiesce VM: check this box if you want to quiesce the file system on the VM "
+"before taking the snapshot. Not supported on XenServer when used with "
+"CloudStack-provided primary storage."
+msgstr "静止VM：如果你想在做快照之前让VM的文件系统处于静止状态，请勾选此选项。使用CloudStack提供的主存储的XenServer环境不受支持。"
+
+# fe21f13b62b746c7a13b2f7f85a6eaa9
+#: ../../virtual_machines.rst:520
+msgid ""
+"When this option is used with CloudStack-provided primary storage, the "
+"quiesce operation is performed by the underlying hypervisor (VMware is "
+"supported). When used with another primary storage vendor's plugin, the "
+"quiesce operation is provided according to the vendor's implementation."
+msgstr "当这个选项在CloudStack提供的主存储中使用了，那么静止操作是由底层的hypervisor完成的(VMware支持)。当使用了其他主存储提供商的插件，静止操作是由其提供商的软件完成的，"
+
+# 2a6c32cefec74407bd7fbe5e305ad9fc
+# a8e7b2f2b1c94ee9ab5aacd3929d2b84
+# cd457f5e102e42109f716c58cae05fee
+# 2226bef2616a496e93a295e437d134ec
+# 48260fa4b2a8429582628ee0a4834f18
+#: ../../virtual_machines.rst:526 ../../virtual_machines.rst:635
+#: ../../virtual_machines.rst:808 ../../virtual_machines.rst:951
+#: ../../virtual_machines.rst:975
+msgid "Click OK."
+msgstr "点击确定。"
+
+# f4d9b9197aca4868ab4d46cfeaeeeb8d
+#: ../../virtual_machines.rst:528
+msgid ""
+"To delete a snapshot or restore a VM to the state saved in a particular "
+"snapshot:"
+msgstr "要删除一个快照或者还原VM的状态到指定的一个快照："
+
+# 36f6cf98d55c41459202b6750b7eb7f4
+#: ../../virtual_machines.rst:531
+msgid "Navigate to the VM as described in the earlier steps."
+msgstr "通过之前描述的步骤定位至VM。"
+
+# bf91c94f8979476a930e9dbf513be4d4
+#: ../../virtual_machines.rst:533
+msgid "Click View VM Snapshots."
+msgstr "点击查看VM快照。"
+
+# e7ccaab839314560b552b6071fc14e64
+#: ../../virtual_machines.rst:535
+msgid ""
+"In the list of snapshots, click the name of the snapshot you want to work "
+"with."
+msgstr "在快照列表中，点击你要操作的快照名字。"
+
+# 8e39335e75044ff99ab9e0def4fdc7d3
+#: ../../virtual_machines.rst:538
+msgid "Depending on what you want to do:"
+msgstr "取决于你想做什么："
+
+# 1992a3d840bc470fabd250937c4de81e
+#: ../../virtual_machines.rst:540
+msgid "To delete the snapshot, click the Delete button. |delete-button.png|"
+msgstr "要删除快照，点击删除按钮。 |delete-button.png|"
+
+# 00f5fcea682d428c9a9e195edb1178e9
+#: ../../virtual_machines.rst:542
+msgid "To revert to the snapshot, click the Revert button. |revert-vm.png|"
+msgstr "要还原至此快照，点击还原按钮。 |revert-vm.png|"
+
+# d31395bcdf554ce6a1057725cfec443b
+#: ../../virtual_machines.rst:545
+msgid ""
+"VM snapshots are deleted automatically when a VM is destroyed. You don't "
+"have to manually delete the snapshots in this case."
+msgstr "当VM被销毁了，那么它的快照也会被自动的删除。这种情况下，你不用手动的去删除快照。"
+
+# b68606a2ccc14896810536c55cfc1b43
+#: ../../virtual_machines.rst:550
+msgid "Changing the VM Name, OS, or Group"
+msgstr "更改VM名字，OS或组"
+
+# c3a4b62362fc4863a6506f6a5e3187de
+#: ../../virtual_machines.rst:552
+msgid ""
+"After a VM is created, you can modify the display name, operating system, "
+"and the group it belongs to."
+msgstr "在VM被创建之后，你可以修改显示名，操作系统和它所属的组。"
+
+# 72447d94968d48569debc5b7e37e4e80
+# 635b0652817c46e8929098fb5425c79b
+# edcc32c2db4948f7b0702e1fec2c46dd
+# af3dab76cece4fbfa032b786f5efe55f
+# 19861b8d6dbc4928b12763a78bf07383
+#: ../../virtual_machines.rst:559 ../../virtual_machines.rst:620
+#: ../../virtual_machines.rst:794 ../../virtual_machines.rst:822
+#: ../../virtual_machines.rst:967
+msgid "In the left navigation, click Instances."
+msgstr "在左侧的导航菜单中，点击实例。"
+
+# b339e4730d0445bebdcb106a5c75c2f4
+#: ../../virtual_machines.rst:561
+msgid "Select the VM that you want to modify."
+msgstr "选择你想修改的VM。"
+
+# 304e46f42670493198568fd5f0ff4ee9
+# 7fdd96b1f7e0497fb108cb28b45a1d3c
+#: ../../virtual_machines.rst:563 ../../virtual_machines.rst:627
+msgid "Click the Stop button to stop the VM. |StopButton.png|"
+msgstr "点击停止按钮来关闭虚机。 |StopButton.png|"
+
+# 8b84a60389bf4387933672f32d30340e
+#: ../../virtual_machines.rst:565
+msgid "Click Edit. |EditButton.png|"
+msgstr "点击编辑。 |EditButton.png|"
+
+# f5ce6fcba1ca478e9bd1598907c1a601
+#: ../../virtual_machines.rst:567
+msgid "Make the desired changes to the following:"
+msgstr "更改以下几项为所需要的："
+
+# 96da85f1c1db4d90b6131a4e7bbe1267
+#: ../../virtual_machines.rst:569
+msgid ""
+"**Display name**: Enter a new display name if you want to change the name of"
+" the VM."
+msgstr "**显示名**：如果你想更改VM的名字，那么输入一个新的显示名。"
+
+# b2eb919b8d15426a86942e811b6b785a
+#: ../../virtual_machines.rst:572
+msgid "**OS Type**: Select the desired operating system."
+msgstr "**OS类型**：选择所需的操作系统。"
+
+# 963531001c6f471fae769294df407de4
+#: ../../virtual_machines.rst:574
+msgid "**Group**: Enter the group name for the VM."
+msgstr "**组**：输入VM的组名。"
+
+# 1f8f9ed119ca43b291afa2ae2b572532
+# acdd7ec88c4b4a27a7b9ade935e17aad
+#: ../../virtual_machines.rst:576 ../../virtual_machines.rst:691
+msgid "Click Apply."
+msgstr "点击应用"
+
+# 35efc08bc7314a2a83b202b6bfd078c6
+#: ../../virtual_machines.rst:580
+msgid "Appending a Display Name to the Guest VM’s Internal Name"
+msgstr "给来宾VM的内部名称附加显示名"
+
+# 090483f924564a9d8180f7df880f4066
+#: ../../virtual_machines.rst:582
+msgid ""
+"Every guest VM has an internal name. The host uses the internal name to "
+"identify the guest VMs. CloudStack gives you an option to provide a guest VM"
+" with a display name. You can set this display name as the internal name so "
+"that the vCenter can use it to identify the guest VM. A new global "
+"parameter, vm.instancename.flag, has now been added to achieve this "
+"functionality."
+msgstr "每个来宾VM都有一个内部名称。主机使用内部名称来识别来宾VMs。CloudStack为来宾VM提供了一个关于显示名的选项。你可以设置显示名作为内部名称以便vCenter可以使用它来识别来宾VM。vm.instancename.flag作为一个新的全局参数，已被添加用来实现此功能。"
+
+# f1544ed6d7c34d8ebadbc2726fd7edb9
+#: ../../virtual_machines.rst:589
+msgid ""
+"The default format of the internal name is "
+"i-<user\\_id>-<vm\\_id>-<instance.name>, where instance.name is a global "
+"parameter. However, If vm.instancename.flag is set to true, and if a display"
+" name is provided during the creation of a guest VM, the display name is "
+"appended to the internal name of the guest VM on the host. This makes the "
+"internal name format as i-<user\\_id>-<vm\\_id>-<displayName>. The default "
+"value of vm.instancename.flag is set to false. This feature is intended to "
+"make the correlation between instance names and internal names easier in "
+"large data center deployments."
+msgstr "默认的内部名称的格式是 i-<user\\_id>-<vm\\_id>-<instance.name>，这里instance.name是全局参数。但是，如果vm.instancename.flag被设置为true，并且来宾VM在创建的过程中提供了显示名，那么显示名就会被附加至该主机的来宾VM的内部名称上。这样就使得内部名称的格式类似于 i-<user\\_id>-<vm\\_id>-<displayName>。vm.instancename.flag的默认值被设置为false。这个功能可以比较容易的在大型数据中心的部署中表示实例名和内部名之间的相互关系。"
+
+# fa48ed23ffd24df4a02ee5f2167670e9
+#: ../../virtual_machines.rst:599
+msgid ""
+"The following table explains how a VM name is displayed in different "
+"scenarios."
+msgstr "下面的表格解释了不同场景下VM的名称是如何显示的。"
+
+# 76ff8c667a8c480fb21958db7dd65d12
+#: ../../virtual_machines.rst:603
+msgid "User-Provided Display Name"
+msgstr "用户提供的显示名"
+
+# 77b3d04a25244f7b88843f76b0269874
+#: ../../virtual_machines.rst:603
+msgid "vm.instancename.flag"
+msgstr "vm.instancename.flag"
+
+# eb539380b01a4ba7abe6fab6cbef8d37
+#: ../../virtual_machines.rst:603
+msgid "Hostname on the VM"
+msgstr "VM的主机名"
+
+# 44a68176f9334f3d893063ea88a1880e
+#: ../../virtual_machines.rst:603
+msgid "Name on vCenter"
+msgstr "vCenter中的名称"
+
+# 09d5fe54336843e99505c1bd9d7c24c9
+#: ../../virtual_machines.rst:603
+msgid "Internal Name"
+msgstr "内部名称"
+
+# 8a2a30cd89b8470ab636c82eea18e3a4
+# 8c02dc549daa4804be4ee3b3bf8216a7
+#: ../../virtual_machines.rst:605 ../../virtual_machines.rst:607
+msgid "Yes"
+msgstr "是"
+
+# 854c972116cd4ffea1dd8e5be0d72b55
+# 2d6b531677a8463b806c81b61c640ad8
+#: ../../virtual_machines.rst:605 ../../virtual_machines.rst:606
+msgid "True"
+msgstr "True"
+
+# e24020ac7abe425a8fc5ae02e4464a87
+# 1eaa0ac4785f44bf90d042a044d9500f
+#: ../../virtual_machines.rst:605 ../../virtual_machines.rst:607
+msgid "Display name"
+msgstr "显示名"
+
+# da8b1b08fbf24753a7ad71dc4c6e910a
+# b909f46baf824afb95db14b2c7a3628a
+#: ../../virtual_machines.rst:605 ../../virtual_machines.rst:605
+msgid "i-<user\\_id>-<vm\\_id>-displayName"
+msgstr "i-<user\\_id>-<vm\\_id>-displayName"
+
+# fe84676df63e465ab7918b5f44790a34
+# 799a550bf2024c8db25a267cd0eac622
+#: ../../virtual_machines.rst:606 ../../virtual_machines.rst:608
+msgid "No"
+msgstr "否"
+
+# 2f6abcbb57e24820b71d94a8d721a901
+# 05c2b0965dab4221a022ca3f4d1fb71e
+#: ../../virtual_machines.rst:606 ../../virtual_machines.rst:608
+msgid "UUID"
+msgstr "UUID"
+
+# 5179011192fa4530bf1aa6561ba03e80
+# 0e4881cabf544619b6ed3f98b666fa4d
+# 923b87aaf25d404cb843c35fde7e8abf
+# 14cf566f26974c38b4ceaa39a9c10a2b
+# 5351204fc9aa4a09ac443444dcb12cf5
+# 1b26f9393c914e4bbc0f6099ee278a0e
+#: ../../virtual_machines.rst:606 ../../virtual_machines.rst:606
+#: ../../virtual_machines.rst:607 ../../virtual_machines.rst:607
+#: ../../virtual_machines.rst:608 ../../virtual_machines.rst:608
+msgid "i-<user\\_id>-<vm\\_id>-<instance.name>"
+msgstr "i-<user\\_id>-<vm\\_id>-<instance.name>"
+
+# 882c61362e02473eb3d26c71fc8a1d93
+# 2e62c668c7b74882a7c5518dd4e345b7
+#: ../../virtual_machines.rst:607 ../../virtual_machines.rst:608
+msgid "False"
+msgstr "False"
+
+# c1aad1317c774f3cb8be7a171d4c7615
+#: ../../virtual_machines.rst:613
+msgid "Changing the Service Offering for a VM"
+msgstr "为VM变更服务方案"
+
+# aa826a1e593e4934b4bd9a30bd004c64
+#: ../../virtual_machines.rst:615
+msgid ""
+"To upgrade or downgrade the level of compute resources available to a "
+"virtual machine, you can change the VM's compute offering."
+msgstr "要给虚拟机提升或降低可用计算资源的级别，你可以更改VM的计算方案。"
+
+# 8c522d8ff0c341f08389ff47a300b9be
+#: ../../virtual_machines.rst:622
+msgid "Choose the VM that you want to work with."
+msgstr "选择你要处理的VM。"
+
+# 0efe6503c5934cb0b193cabcb06131e0
+#: ../../virtual_machines.rst:624
+msgid ""
+"(Skip this step if you have enabled dynamic VM scaling; see :ref:`cpu-and-"
+"memory-scaling`.)"
+msgstr "(如果你启用了动态VM扩展或缩减，请跳过此步；查看:ref:`cpu-and-memory-scaling。`)"
+
+# 8a714661de844774afa81e0071868b59
+#: ../../virtual_machines.rst:629
+msgid "Click the Change Service button. |ChangeServiceButton.png|"
+msgstr "点击更改服务按钮。 |ChangeServiceButton.png|"
+
+# 83f39b159c464727b6fccf6e6b055c0e
+#: ../../virtual_machines.rst:631
+msgid "The Change service dialog box is displayed."
+msgstr "显示更改服务对话框。"
+
+# c981bd6e1e7f49bab3deb9b83f0477f6
+#: ../../virtual_machines.rst:633
+msgid "Select the offering you want to apply to the selected VM."
+msgstr "选择你想应用到选择的VM的方案。"
+
+# a01d7307691b4520a87be0d9d9b9da2d
+#: ../../virtual_machines.rst:641
+msgid "CPU and Memory Scaling for Running VMs"
+msgstr "运行中VMs的CPU和内存的扩展和缩减"
+
+# ab0e9786b026430a9847f2f68311aeb3
+#: ../../virtual_machines.rst:645
+msgid ""
+"It is not always possible to accurately predict the CPU and RAM requirements"
+" when you first deploy a VM. You might need to increase these resources at "
+"any time during the life of a VM. You can dynamically modify CPU and RAM "
+"levels to scale up these resources for a running VM without incurring any "
+"downtime."
+msgstr "通常当你第一次部署VM的时候不太可能精确地预计CPU和RAM需求。你可能必须在VM的生命周期内的任何时间增加这些资源。你可以在不中断运行状态中的VM的情况下，动态的修改CPU和RAM级别来提升这些资源，、。"
+
+# 115161eb80b3499bacb45dfdfebee485
+#: ../../virtual_machines.rst:651
+msgid "Dynamic CPU and RAM scaling can be used in the following cases:"
+msgstr "动态CPU和RAM扩展和缩减能被用于一下情况："
+
+# 30297090e50d4dde9f897f9a136fe4f6
+#: ../../virtual_machines.rst:653
+msgid "User VMs on hosts running VMware and XenServer."
+msgstr "运行VMware和XenServer的主机上的用户VMs。"
+
+# 6232185457af46168206dcb77fbe3d5a
+#: ../../virtual_machines.rst:655
+msgid "System VMs on VMware."
+msgstr "VMware上的系统VMs。"
+
+# f6a39632a5fc44fc95fe18b95ec76dca
+#: ../../virtual_machines.rst:657
+msgid ""
+"VMware Tools or XenServer Tools must be installed on the virtual machine."
+msgstr "虚拟机上必须安装VMware Tools或者XenServer Tools。"
+
+# 3a9ff2ea379947d1a7d14452ee5a9f23
+#: ../../virtual_machines.rst:660
+msgid ""
+"The new requested CPU and RAM values must be within the constraints allowed "
+"by the hypervisor and the VM operating system."
+msgstr "对于新的CPU和RAM大小必须在hypervisor和VM操作系统要求之内。"
+
+# 5110926c89cb47f6b2f174d9b7fd2074
+#: ../../virtual_machines.rst:663
+msgid ""
+"New VMs that are created after the installation of CloudStack 4.2 can use "
+"the dynamic scaling feature. If you are upgrading from a previous version of"
+" CloudStack, your existing VMs created with previous versions will not have "
+"the dynamic scaling capability unless you update them using the following "
+"procedure."
+msgstr "在CloudStack 4.2安装完以后创建的新VMs都可以使用动态扩展和缩减功能。如果你的CloudStack是从旧版本升级而来的，其上已有的VMs不会支持动态扩展和缩减功能，除非你按照下面的过程来升级这些VM。"
+
+# 1ad181d6d7c7496e95ae7d8940fdae5e
+#: ../../virtual_machines.rst:671
+msgid "Updating Existing VMs"
+msgstr "升级已有VMs"
+
+# 869cd5d508b846d8bac2af633484f301
+#: ../../virtual_machines.rst:673
+msgid ""
+"If you are upgrading from a previous version of CloudStack, and you want "
+"your existing VMs created with previous versions to have the dynamic scaling"
+" capability, update the VMs using the following steps:"
+msgstr "如果你正在升级旧版本的CloudStack，并且你还想让你的旧版本VMs拥有动态扩展和缩减能力，请使用以下步骤来升级VMs："
+
+# 11e41c992a6545bca58c3d47b712fc40
+#: ../../virtual_machines.rst:677
+msgid ""
+"Make sure the zone-level setting enable.dynamic.scale.vm is set to true. In "
+"the left navigation bar of the CloudStack UI, click Infrastructure, then "
+"click Zones, click the zone you want, and click the Settings tab."
+msgstr "确保区域级别设置enable.dynamic.scale.vm被设置为true。在CloudStack UI的左侧导航条，点击基础架构，然后点击区域，点击你要操作的区域，然后点击Settings标签。"
+
+# 62c28d859ce4495393ca05ebe80feab9
+#: ../../virtual_machines.rst:682
+msgid ""
+"Install Xen tools (for XenServer hosts) or VMware Tools (for VMware hosts) "
+"on each VM if they are not already installed."
+msgstr "在每台VM上安装Xen tools(适用于XenServer主机)或者VMware Tools(适用于VMware主机)。"
+
+# d20322e380d44022b1ff5c61fdb66462
+#: ../../virtual_machines.rst:685
+msgid "Stop the VM."
+msgstr "停止VM。"
+
+# 7fb4a5e90f7240faa3517081515db067
+#: ../../virtual_machines.rst:687
+msgid "Click the Edit button."
+msgstr "点击编辑按钮。"
+
+# e27c8efe5a804069964feebad14fc869
+#: ../../virtual_machines.rst:689
+msgid "Click the Dynamically Scalable checkbox."
+msgstr "点击动态伸缩选框。"
+
+# cfbb1778b1b04d149bb2c2bb69c274d3
+#: ../../virtual_machines.rst:693
+msgid "Restart the VM."
+msgstr "重启VM。"
+
+# f11c788c7fd447179dd19538674fb81c
+#: ../../virtual_machines.rst:697
+msgid "Configuring Dynamic CPU and RAM Scaling"
+msgstr "配置动态CPU和RAM伸缩"
+
+# 30af79a24d8f48a1b834110d8374abbc
+#: ../../virtual_machines.rst:699
+msgid ""
+"To configure this feature, use the following new global configuration "
+"variables:"
+msgstr "要配置此功能，请使用下面的全局配置变量："
+
+# 5a2816315adb4870943cb43b6d0cf99c
+#: ../../virtual_machines.rst:702
+msgid ""
+"enable.dynamic.scale.vm: Set to True to enable the feature. By default, the "
+"feature is turned off."
+msgstr "enable.dynamic.scale.vm：设置为True以启用此功能。默认情况下，此功能是被关闭的。"
+
+# cdeb9f1cb4df4b029610a510842cc284
+#: ../../virtual_machines.rst:705
+msgid ""
+"scale.retry: How many times to attempt the scaling operation. Default = 2."
+msgstr "scale.retry：伸缩操作的重试次数。默认为2。"
+
+# 07decccd4eb04199817b30945867ed27
+#: ../../virtual_machines.rst:710
+msgid "How to Dynamically Scale CPU and RAM"
+msgstr "如果动态伸缩CPU和RAM"
+
+# ae889fadf36342a6a037fb765a54fd59
+#: ../../virtual_machines.rst:712
+msgid ""
+"To modify the CPU and/or RAM capacity of a virtual machine, you need to "
+"change the compute offering of the VM to a new compute offering that has the"
+" desired CPU and RAM values. You can use the same steps described above in "
+"`“Changing the Service Offering for a VM” <#changing-the-service-offering-"
+"for-a-vm>`_, but skip the step where you stop the virtual machine. Of "
+"course, you might have to create a new compute offering first."
+msgstr "要修改虚拟机的CPU和/或RAM，你必须更改VM的计算方案为你想要的。你可以按照上文中所述的同样的步骤 `“Changing the Service Offering for a VM” <#changing-the-service-offering-for-a-vm>`_，但是要跳过停止虚拟机的步骤。当然，你可能必须先创建一个新的计算方案。"
+
+# 4ad82ed62390433a83075a6fe291e6c6
+#: ../../virtual_machines.rst:720
+msgid ""
+"When you submit a dynamic scaling request, the resources will be scaled up "
+"on the current host if possible. If the host does not have enough resources,"
+" the VM will be live migrated to another host in the same cluster. If there "
+"is no host in the cluster that can fulfill the requested level of CPU and "
+"RAM, the scaling operation will fail. The VM will continue to run as it was "
+"before."
+msgstr "当你提交一个动态伸缩的请求的时候，当前主机可能会扩展资源。如果主机没有足够的资源，VM会被在线迁移至同一群集中的其他主机。如果群集中没有能满足CPU和RAM条件的主机，那么扩展操作会失败。不用担心，VM会往常一样继续运行。"
+
+# 04a78ffb0e8a4995a6fbbf8870ef3c01
+#: ../../virtual_machines.rst:729
+msgid "Limitations"
+msgstr "局限性"
+
+# 4d4543f814604671a8582fd47d1298ca
+#: ../../virtual_machines.rst:731
+msgid "You can not do dynamic scaling for system VMs on XenServer."
+msgstr "你不能为XenServer上运行的系统VMs进行动态伸缩操作。"
+
+# 0c3b91b5ecc54cb1b79f79eea7129458
+#: ../../virtual_machines.rst:733
+msgid ""
+"CloudStack will not check to be sure that the new CPU and RAM levels are "
+"compatible with the OS running on the VM."
+msgstr "CloudStack不会检查新的CPU和RAM级别是不是符合VM操作系统的要求。"
+
+# c8b490e8cfa64c6c992a761349ffcec9
+#: ../../virtual_machines.rst:736
+msgid ""
+"When scaling memory or CPU for a Linux VM on VMware, you might need to run "
+"scripts in addition to the other steps mentioned above. For more "
+"information, see `Hot adding memory in Linux (1012764) "
+"<http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012764>`_"
+" in the VMware Knowledge Base."
+msgstr "当为VMware上运行的Linux VM扩展内存或者CPU的时候，你可能需要运行额外的脚本。更多信息，请参阅VMware知识库中的 `在Linux中热添加内存 (1012764) <http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012764>`_"
+
+# 4e112807f7f146ccb7683bafe9845553
+#: ../../virtual_machines.rst:742
+msgid ""
+"(VMware) If resources are not available on the current host, scaling up will"
+" fail on VMware because of a known issue where CloudStack and vCenter "
+"calculate the available capacity differently. For more information, see "
+"`https://issues.apache.org/jira/browse/CLOUDSTACK-1809 "
+"<https://issues.apache.org/jira/browse/CLOUDSTACK-1809>`_."
+msgstr "(VMware)如果当前主机上没有可用资源，因为一个已知的问题，VMware上的虚机扩展会失败，这是因为CloudStack和vCenter计算可用容量方法的不同。更多信息，请参阅`https://issues.apache.org/jira/browse/CLOUDSTACK-1809 <https://issues.apache.org/jira/browse/CLOUDSTACK-1809>`_。"
+
+# eed3ea4ba4134de1b4cb819e07cb8326
+#: ../../virtual_machines.rst:748
+msgid ""
+"On VMs running Linux 64-bit and Windows 7 32-bit operating systems, if the "
+"VM is initially assigned a RAM of less than 3 GB, it can be dynamically "
+"scaled up to 3 GB, but not more. This is due to a known issue with these "
+"operating systems, which will freeze if an attempt is made to dynamically "
+"scale from less than 3 GB to more than 3 GB."
+msgstr "对于运行Linux 64位和Windows 7 32位操作系统的VMs，如果VM初始分配的RAM小于3GB，那么它最大能动态的扩展到3GB。这是因为这些操作系统已知的问题，如果尝试从小于3G动态扩展至超过3G的话，操作系统会宕机。"
+
+# 0f66f02496244365a1fc127038eafca0
+#: ../../virtual_machines.rst:756
+msgid "Resetting the Virtual Machine Root Volume on Reboot"
+msgstr "在重启时重置虚拟机的Root卷"
+
+# 63185701fdb845c78448a80722e1e1f9
+#: ../../virtual_machines.rst:758
+msgid ""
+"For secure environments, and to ensure that VM state is not persisted across"
+" reboots, you can reset the root disk. For more information, see `“Reset VM "
+"to New Root Disk on Reboot” <storage.html#reset-vm-to-new-root-disk-on-"
+"reboot>`_."
+msgstr "为安全环境和确保VM重启期间不被中断状态，你可以重置root磁盘。更多信息，请参阅 `“在重启时给VM重置一个新的Root磁盘” <storage.html#reset-vm-to-new-root-disk-on-reboot>`_。"
+
+# 66018bd4d29d47f5b9921b2b638bd9e5
+#: ../../virtual_machines.rst:765
+msgid "Moving VMs Between Hosts (Manual Live Migration)"
+msgstr "在主机之间移动VMs(手动在线迁移)"
+
+# 4a11ec0f0f7849af900329d21eb5021a
+#: ../../virtual_machines.rst:767
+msgid ""
+"The CloudStack administrator can move a running VM from one host to another "
+"without interrupting service to users or going into maintenance mode. This "
+"is called manual live migration, and can be done under the following "
+"conditions:"
+msgstr "CloudStack管理员可以从一个主机将运行中的VM不中断服务地移动到其他主机或者将其进入维护模式。这个过程叫手动在线迁移，要满足以下条件："
+
+# f7d30be3c9c04c2890163879415fbec7
+#: ../../virtual_machines.rst:772
+msgid ""
+"The root administrator is logged in. Domain admins and users can not perform"
+" manual live migration of VMs."
+msgstr "root管理员已登录。域管理员和用户不能执行手动在线迁移操作。"
+
+# 17e5f9d4b5d849c395dc3660e836ea8c
+#: ../../virtual_machines.rst:775
+msgid "The VM is running. Stopped VMs can not be live migrated."
+msgstr "VM正在运行。停止的VMs不能进行在线迁移。"
+
+# 948845ad74164fee9ba6899a995747ff
+#: ../../virtual_machines.rst:777
+msgid ""
+"The destination host must have enough available capacity. If not, the VM "
+"will remain in the \"migrating\" state until memory becomes available."
+msgstr "目标主机必须有足够的可用容量。如果没有，VM会一直停留在\"迁移中\"状态，直到有多余内存可用。"
+
+# 926ce179048d440ba2bea6731af74b85
+#: ../../virtual_machines.rst:781
+msgid ""
+"(KVM) The VM must not be using local disk storage. (On XenServer and VMware,"
+" VM live migration with local disk is enabled by CloudStack support for "
+"XenMotion and vMotion.)"
+msgstr "(KVM)VM必须不能使用本地磁盘存储。(在XenServer和VMware中，CloudStack依靠XenMotion和vMotion允许使用了本地磁盘的VM能够在线迁移。)"
+
+# 7afc45cd0fd64406bf6773ae8ca01061
+#: ../../virtual_machines.rst:785
+msgid ""
+"(KVM) The destination host must be in the same cluster as the original host."
+" (On XenServer and VMware, VM live migration from one cluster to another is "
+"enabled by CloudStack support for XenMotion and vMotion.)"
+msgstr "(KVM)目标主机必须跟源主机在同一个群集。(在XenServer和VMware上，CloudStack依靠XenMotion和vMotion，允许VM从一个群集在线迁移到另一个群集)"
+
+# 5b314d24029f4c3b8005118729a96b8a
+#: ../../virtual_machines.rst:790
+msgid "To manually live migrate a virtual machine"
+msgstr "手动在线迁移一个虚拟机"
+
+# 1e1e47dac41d499993b564e4a93cb2d3
+#: ../../virtual_machines.rst:796
+msgid "Choose the VM that you want to migrate."
+msgstr "选择你想迁移的VM。"
+
+# 761a3094e3774e94a810eb219c96c394
+#: ../../virtual_machines.rst:798
+msgid "Click the Migrate Instance button. |Migrateinstance.png|"
+msgstr "点击迁移实例按钮。 |Migrateinstance.png|"
+
+# fd690eecd191485bb7d1b4908411a5cc
+#: ../../virtual_machines.rst:800
+msgid ""
+"From the list of suitable hosts, choose the one to which you want to move "
+"the VM."
+msgstr "从可用主机列表中，选择一个目标主机。"
+
+# 726aae3ee8924808ba550a28342fc0e5
+#: ../../virtual_machines.rst:804
+msgid ""
+"If the VM's storage has to be migrated along with the VM, this will be noted"
+" in the host list. CloudStack will take care of the storage migration for "
+"you."
+msgstr "如果VM的存储与VM必须一起被迁移，这点会在主机列表中标注。CloudStack会为你自动的进行存储迁移。"
+
+# 8f08330a7d1e42caaf5ef765aa58882a
+#: ../../virtual_machines.rst:812
+msgid "Deleting VMs"
+msgstr "删除VMs"
+
+# c3d724719a8246f193d97c4f0d121699
+#: ../../virtual_machines.rst:814
+msgid ""
+"Users can delete their own virtual machines. A running virtual machine will "
+"be abruptly stopped before it is deleted. Administrators can delete any "
+"virtual machines."
+msgstr "用户可以删除他们拥有的虚拟机。在删除运行中的虚拟机之前，虚拟机会被强制停止。管理员可以删除任何虚拟机。"
+
+# 7ce9ae8ec54a41f9a717fdf87bd9c144
+#: ../../virtual_machines.rst:818
+msgid "To delete a virtual machine:"
+msgstr "要删除虚拟机："
+
+# e404b64388f74a71bbfc6af41ccd3ff1
+#: ../../virtual_machines.rst:824
+msgid "Choose the VM that you want to delete."
+msgstr "选择你想删除的VM。"
+
+# 2d8231a2d7c149b796ed88861d1bb909
+#: ../../virtual_machines.rst:826
+msgid "Click the Destroy Instance button. |Destroyinstance.png|"
+msgstr "点击销毁实例按钮。 |Destroyinstance.png|"
+
+# e060074ca29143089e33cdd841b6e53c
+#: ../../virtual_machines.rst:830
+msgid "Working with ISOs"
+msgstr "使用ISOs"
+
+# 49e588f8f3d3457396167bfe47840a9c
+#: ../../virtual_machines.rst:832
+msgid ""
+"CloudStack supports ISOs and their attachment to guest VMs. An ISO is a "
+"read-only file that has an ISO/CD-ROM style file system. Users can upload "
+"their own ISOs and mount them on their guest VMs."
+msgstr "CloudStack支持ISOs和将其挂载到来宾VMs。ISO是一种只读的ISO/CD-ROM格式的文件文件系统。用户可以上传他们自己的ISOs并且将其挂载至他们的来宾VMs。"
+
+# 43da1c69da0e4ff3ba3867e9061ad9c4
+#: ../../virtual_machines.rst:836
+msgid ""
+"ISOs are uploaded based on a URL. HTTP is the supported protocol. Once the "
+"ISO is available via HTTP specify an upload URL such as "
+"http://my.web.server/filename.iso."
+msgstr "ISOs文件通过URL上传。HTTP是受支持的协议。一旦ISO通过HTTP指定一个上传URL，比如http://my.web.server/filename.iso上传成功，那么文件就可以用了。"
+
+# 646b8bd2384245229f23171a7a8d7712
+#: ../../virtual_machines.rst:840
+msgid ""
+"ISOs may be public or private, like templates.ISOs are not hypervisor-"
+"specific. That is, a guest on vSphere can mount the exact same image that a "
+"guest on KVM can mount."
+msgstr "ISOs可能是私有的也可以是共有的，像templates.ISOs并不针对某种hypervisor。也就是说，运行在vSphere上的来宾虚机和运行在KVM上的虚机可以挂载同一个ISO。"
+
+# 3d98a7d5d5ef47d5b8a0ccafaa66e0e7
+#: ../../virtual_machines.rst:844
+msgid ""
+"ISO images may be stored in the system and made available with a privacy "
+"level similar to templates. ISO images are classified as either bootable or "
+"not bootable. A bootable ISO image is one that contains an OS image. "
+"CloudStack allows a user to boot a guest VM off of an ISO image. Users can "
+"also attach ISO images to guest VMs. For example, this enables installing PV"
+" drivers into Windows. ISO images are not hypervisor-specific."
+msgstr "ISO镜像可能存储在系统中并且隐私级别与模板相似。ISO镜像分为可引导或不可引导的。可引导的ISO镜像是包含了OS镜像的。CloudStack允许用户通过ISO镜像来启动来宾虚机。用户同样可以将ISO镜像挂载到来宾VMs。比如，给Windows安装PV驱动。ISO镜像不指定hypervisor。"
+
+# 8d9568801830478a848ccdac420a263f
+#: ../../virtual_machines.rst:854
+msgid "Adding an ISO"
+msgstr "添加ISO"
+
+# ba8d1a29acc24d7ca0da86abbc13d3d2
+#: ../../virtual_machines.rst:856
+msgid ""
+"To make additional operating system or other software available for use with"
+" guest VMs, you can add an ISO. The ISO is typically thought of as an "
+"operating system image, but you can also add ISOs for other types of "
+"software, such as desktop applications that you want to be installed as part"
+" of a template."
+msgstr "为了添加额外的操作系统或者给来宾VMs使用其它软件，你可以添加ISO。操作系统镜像被认为是最典型的ISO，但是你也能添加软件类型的ISOs，例如你想把安装的桌面应用作为模板的一部分。"
+
+# 79227c9ef0904022a147fb56ff1f7530
+#: ../../virtual_machines.rst:862
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# 0241367a6d3f4783a3b774447b3e7ba8
+#: ../../virtual_machines.rst:864
+msgid "In the left navigation bar, click Templates."
+msgstr "在左侧的导航栏，点击模板。"
+
+# 0f973ef8ca224955a380e55e4cb178f7
+#: ../../virtual_machines.rst:866
+msgid "In Select View, choose ISOs."
+msgstr "在选择视图中，选择ISOs。"
+
+# 7fa77a1f7f2c433b9a91a2674c905e0f
+#: ../../virtual_machines.rst:868
+msgid "Click Add ISO."
+msgstr "点击添加ISO。"
+
+# d823b6abfa4f4f90a537b89a3028cbf8
+#: ../../virtual_machines.rst:870
+msgid "In the Add ISO screen, provide the following:"
+msgstr "在添加ISO界面中，提供下列信息:"
+
+# 3685d0bb311b4ed380fda725b7cd9278
+#: ../../virtual_machines.rst:872
+msgid ""
+"**Name**: Short name for the ISO image. For example, CentOS 6.2 64-bit."
+msgstr "**名称**: ISO 镜像的简称。例如，CentOS6.2 64-bit。"
+
+# 2b4eed14408848cdba835ad59d43680e
+#: ../../virtual_machines.rst:875
+msgid ""
+"**Description**: Display test for the ISO image. For example, CentOS 6.2 "
+"64-bit."
+msgstr "**描述**: 对于ISO镜像的描述。例如，CentOS 6.2 64-bit."
+
+# f186dace19cc4fb78d4e957564d8542e
+#: ../../virtual_machines.rst:878
+msgid ""
+"**URL**: The URL that hosts the ISO image. The Management Server must be "
+"able to access this location via HTTP. If needed you can place the ISO image"
+" directly on the Management Server"
+msgstr "**URL**: ISO镜像主机的URL。管理服务器必须能够通过HTTP访问这个地址。如果有需要你可以直接将ISO放置到管理服务器中。"
+
+# 425e7404b8194bb5931d02792793408e
+#: ../../virtual_machines.rst:882
+msgid ""
+"**Zone**: Choose the zone where you want the ISO to be available, or All "
+"Zones to make it available throughout CloudStack."
+msgstr "**区域**: 选择你希望该ISO在到哪个区域可用，或者选择所有区域使该ISO在CloudStack中全部区域中可用。"
+
+# aa204bdaf6d9433bb4412c757dc5d44b
+#: ../../virtual_machines.rst:885
+msgid ""
+"**Bootable**: Whether or not a guest could boot off this ISO image. For "
+"example, a CentOS ISO is bootable, a Microsoft Office ISO is not bootable."
+msgstr "**可启动**: 来宾是否可以通过该ISO镜像启动。例如，一个CentOS ISO 是可启动的，一个Microsoft Office ISO 是不可启动的。"
+
+# 8b59d99740ca42ecbb70e61c148a6cea
+#: ../../virtual_machines.rst:889
+msgid ""
+"**OS Type**: This helps CloudStack and the hypervisor perform certain "
+"operations and make assumptions that improve the performance of the guest. "
+"Select one of the following."
+msgstr "**操作系统类型*: 这有助于CloudStack和Hypervisor执行某些操作并假设可提高来宾虚拟机的性能。选择下列之一。"
+
+# 55d339b4332b4f8d90ab0c41ac4064b8
+#: ../../virtual_machines.rst:893
+msgid ""
+"If the operating system of your desired ISO image is listed, choose it."
+msgstr "如果你需要的ISO镜像对应的操作系统在列表中，请选择它。"
+
+# 7181c3bfc6ea45d29f5de6686bdbc0c8
+#: ../../virtual_machines.rst:896
+msgid ""
+"If the OS Type of the ISO is not listed or if the ISO is not bootable, "
+"choose Other."
+msgstr "如果ISO镜像的操作系统类型没有被列出或者ISO是不可引导的，选择Other。"
+
+# 121ed273b9d942f0bcab107605fbc155
+#: ../../virtual_machines.rst:899
+msgid ""
+"(XenServer only) If you want to boot from this ISO in PV mode, choose Other "
+"PV (32-bit) or Other PV (64-bit)"
+msgstr "(仅针对XenServer) 如果你想使用这个ISO在PV 模式中引导，选择 Other PV (32-bit) 或 Other PV(64-bit)"
+
+# 4630b5213f5447b692ec7949d9d2d0b8
+#: ../../virtual_machines.rst:902
+msgid ""
+"(KVM only) If you choose an OS that is PV-enabled, the VMs created from this"
+" ISO will have a SCSI (virtio) root disk. If the OS is not PV-enabled, the "
+"VMs will have an IDE root disk. The PV-enabled types are:"
+msgstr "(仅针对KVM) 如果你选择一个操作系统为PV-enabled,， 通过这个ISO创建的虚拟机会有一个SCSI(virtio)根磁盘。如果这个操作系统没有PV-enabled,,虚拟机将有一个IDE根磁盘。PV-enabled 类型是:"
+
+# 635be29dfcf3483a8f0a22d1a6baccd9
+#: ../../virtual_machines.rst:907
+msgid "Fedora 13"
+msgstr "Fedora 13"
+
+# 93e9c1d5a6a3487d8c2c3fa739eaf98d
+#: ../../virtual_machines.rst:909
+msgid "Fedora 12"
+msgstr "Fedora 12"
+
+# 2a8eeb99d2ea4a3bac651072df26da55
+#: ../../virtual_machines.rst:911
+msgid "Fedora 11"
+msgstr "Fedora 11"
+
+# c31cbc941bb44094846e2e60cddb38b8
+#: ../../virtual_machines.rst:913
+msgid "Fedora 10"
+msgstr "Fedora 10"
+
+# 46d96452f5e645899cdbeed2f1d8dd64
+#: ../../virtual_machines.rst:915
+msgid "Fedora 9"
+msgstr "Fedora 9"
+
+# 4b44f056e016456b86e5d94d780f5c70
+#: ../../virtual_machines.rst:917
+msgid "Other PV"
+msgstr "Other PV"
+
+# 1f0bbb7dcde34e43a90ab458542c9245
+#: ../../virtual_machines.rst:919
+msgid "Debian GNU/Linux"
+msgstr "Debian GNU/Linux"
+
+# fa0ff295703648b6a27c3051e80cc1a7
+#: ../../virtual_machines.rst:921
+msgid "CentOS 5.3"
+msgstr "CentOS 5.3"
+
+# 10c5d0e4740249ef938a3af66c83cbd4
+#: ../../virtual_machines.rst:923
+msgid "CentOS 5.4"
+msgstr "CentOS 5.4"
+
+# 3abebb97eac94950b3928ed76316c4fb
+#: ../../virtual_machines.rst:925
+msgid "CentOS 5.5"
+msgstr "CentOS 5.5"
+
+# 6e43cd1649cc453eb9ddd4fd035c80cc
+#: ../../virtual_machines.rst:927
+msgid "Red Hat Enterprise Linux 5.3"
+msgstr "Red Hat Enterprise Linux 5.3"
+
+# 460371604538459f9aaab9dbec447cdd
+#: ../../virtual_machines.rst:929
+msgid "Red Hat Enterprise Linux 5.4"
+msgstr "Red Hat Enterprise Linux 5.4"
+
+# 7d68f48aeac44031b6cd313d5fc799a1
+#: ../../virtual_machines.rst:931
+msgid "Red Hat Enterprise Linux 5.5"
+msgstr "Red Hat Enterprise Linux 5.5"
+
+# a2764fbb27c34b978dae6142215c6850
+#: ../../virtual_machines.rst:933
+msgid "Red Hat Enterprise Linux 6"
+msgstr "Red Hat Enterprise Linux 6"
+
+# 94dfebd340a74c8b88a2994cc95f58ec
+#: ../../virtual_machines.rst:936
+msgid ""
+"It is not recommended to choose an older version of the OS than the version "
+"in the image. For example, choosing CentOS 5.4 to support a CentOS 6.2 image"
+" will usually not work. In these cases, choose Other."
+msgstr "不建议选择一个比操作系统镜像老的版本。例如，选择CentOS 5.4 去支持一个CentOS6.2的镜像通常导致不能工作。在这种情况下，去选择Other。"
+
+# f097cba5535645278ee6719b4a03072a
+#: ../../virtual_machines.rst:941
+msgid ""
+"**Extractable**: Choose Yes if the ISO should be available for extraction."
+msgstr "**可提取**: 如果该ISO可以被提取出来，则选择Yes。"
+
+# 7d047a068b0a49599ef129b9c79a6666
+#: ../../virtual_machines.rst:944
+msgid "**Public**: Choose Yes if this ISO should be available to other users."
+msgstr "**公共**: 如果该ISO可以被所有用户使用，则选择Yes。"
+
+# cc70871cc63f4a778f5a762c96814820
+#: ../../virtual_machines.rst:947
+msgid ""
+"**Featured**: Choose Yes if you would like this ISO to be more prominent for"
+" users to select. The ISO will appear in the Featured ISOs list. Only an "
+"administrator can make an ISO Featured."
+msgstr "**精选**: 如果你想这个用户在选择这个ISO时更加突出则选择Yes。该ISO将出现在精选ISO列表中。只有管理员可以设置ISO为精选。"
+
+# 0ada7b2845314dff81bc2025971a349d
+#: ../../virtual_machines.rst:953
+msgid ""
+"The Management Server will download the ISO. Depending on the size of the "
+"ISO, this may take a long time. The ISO status column will display Ready "
+"once it has been successfully downloaded into secondary storage. Clicking "
+"Refresh updates the download percentage."
+msgstr "管理服务器将下载该ISO。根据ISO镜像的大小，下载过程可能会用很长时间。一旦该镜像已经被成功下载到辅助存储时ISO 状态栏将会显示Ready。点击刷新更新更新百分比。"
+
+# 6918d4062b5b40fe9ec994fe73602e85
+#: ../../virtual_machines.rst:958
+msgid ""
+"**Important**: Wait for the ISO to finish downloading. If you move on to the"
+" next task and try to use the ISO right away, it will appear to fail. The "
+"entire ISO must be available before CloudStack can work with it."
+msgstr "**重要**: 等等ISO下载完成过程中。如果你想执行下一个任务并且尝试正常使用该ISO，这将会失败。在CloudStack 使用它之前该ISO必须是完整且有效的。"
+
+# b14f8c054f394494acb88245da8ba860
+#: ../../virtual_machines.rst:965
+msgid "Attaching an ISO to a VM"
+msgstr "附加ISO到虚拟机"
+
+# b5dd3e88e7fd4e289eaba6d0a5144d12
+#: ../../virtual_machines.rst:969
+msgid "Choose the virtual machine you want to work with."
+msgstr "选择要使用的虚拟机。"
+
+# 7dc31f79f1d14b79a420d462bfee1c59
+#: ../../virtual_machines.rst:971
+msgid "Click the Attach ISO button. |iso.png|"
+msgstr "点击附加ISO按钮。 |iso.png|"
+
+# c8a3faf4703b4ccd9b1e8108195cc959
+#: ../../virtual_machines.rst:973
+msgid "In the Attach ISO dialog box, select the desired ISO."
+msgstr "在附加ISO对话框中，选择所需的ISO。"
+
+# 549b92307c7f47f98184d3f1124fa408
+#: ../../virtual_machines.rst:979
+msgid "Changing a VM's Base Image"
+msgstr "改变VM's 的基础镜像"
+
+# 13e3fdc48e0047a987a24ca40e0e1a87
+#: ../../virtual_machines.rst:981
+msgid ""
+"Every VM is created from a base image, which is a template or ISO which has "
+"been created and stored in CloudStack. Both cloud administrators and end "
+"users can create and modify templates, ISOs, and VMs."
+msgstr "每个VM都是通过基础镜像创建的，可以是创建并存储在CloudStack中的一个模版或者一个ISO镜像。云管理员和终端用户都可以创建和修改模版，ISO和VM。"
+
+# f5fa30e2adb14813a20639e4efb5b685
+#: ../../virtual_machines.rst:985
+msgid ""
+"In CloudStack, you can change an existing VM's base image from one template "
+"to another, or from one ISO to another. (You can not change from an ISO to a"
+" template, or from a template to an ISO)."
+msgstr "在CloudStack中，你可以改变虚拟机的基础磁盘从一个模版换成其他模版，或从一个ISO换成其他ISO。(你不能把ISO变成模版或模版变成ISO。)"
+
+# 950431c149ec42938db84b6db95abf20
+#: ../../virtual_machines.rst:989
+msgid ""
+"For example, suppose there is a template based on a particular operating "
+"system, and the OS vendor releases a software patch. The administrator or "
+"user naturally wants to apply the patch and then make sure existing VMs "
+"start using it. Whether a software update is involved or not, it's also "
+"possible to simply switch a VM from its current template to any other "
+"desired template."
+msgstr "例如，假设有一个模板基于一个特定的操作系统，并且操作系统厂商发布了一个补丁。管理员和用户理所当然的想要将该补丁应用到已经存在的虚拟机中，并确保虚拟机开始使用它。无论是否涉及软件更新，也有可能只是将虚拟机从当前的模板切换至其他所需的模板。"
+
+# fee5003ddd3f4dbbaba68ad0e14fe0d0
+#: ../../virtual_machines.rst:996
+msgid ""
+"To change a VM's base image, call the restoreVirtualMachine API command and "
+"pass in the virtual machine ID and a new template ID. The template ID "
+"parameter may refer to either a template or an ISO, depending on which type "
+"of base image the VM was already using (it must match the previous type of "
+"image). When this call occurs, the VM's root disk is first destroyed, then a"
+" new root disk is created from the source designated in the template ID "
+"parameter. The new root disk is attached to the VM, and now the VM is based "
+"on the new template."
+msgstr "要改变熏鸡的基础镜像，通过虚拟机iD和新的模版ID调用restoreVirtualMachine API命令。模版ID参数可以参考模版或者ISO，取决于虚拟机正在使用的基础镜像类型(它必须匹配先前的镜像类型)。当这个调用生效时，虚拟机的根磁盘首先被摧毁，然后通过指定的模版ID参数创建根磁盘。新的根磁盘会附件到虚拟机中，现在虚拟机已经基于新的模版了。"
+
+# 0b104b6b42e9463c92201dd3799d82d6
+#: ../../virtual_machines.rst:1005
+msgid ""
+"You can also omit the template ID parameter from the restoreVirtualMachine "
+"call. In this case, the VM's root disk is destroyed and recreated, but from "
+"the same template or ISO that was already in use by the VM."
+msgstr "你同样可以在调用restoreVirtualMachine时忽略模版ID参数。在这个情况下，虚拟机的根磁盘被摧毁并重新创建。但相同的模版或ISO已经被该虚拟机使用。"
+
+# e0d3653b842a43b7bd3f9cba8bfb4397
+#: ../../virtual_machines.rst:1012
+msgid "Using SSH Keys for Authentication"
+msgstr "未验证使用SSH秘钥"
+
+# f04e7ecfb1314f84ab38410cef835634
+#: ../../virtual_machines.rst:1014
+msgid ""
+"In addition to the username and password authentication, CloudStack supports"
+" using SSH keys to log in to the cloud infrastructure for additional "
+"security. You can use the createSSHKeyPair API to generate the SSH keys."
+msgstr "除了用户名和密码验证之外，出于额外的安全性考虑，CloudStack还支持使用SSH秘钥来登录到云架构。你可以使用createSSHKeyPair API来生成SSH秘钥。"
+
+# 007515e3abea40618c568f35513e1571
+#: ../../virtual_machines.rst:1019
+msgid ""
+"Because each cloud user has their own SSH key, one cloud user cannot log in "
+"to another cloud user's instances unless they share their SSH key files. "
+"Using a single SSH key pair, you can manage multiple instances."
+msgstr "因为每个云用户都有他们自己的SSH秘钥，一个云用户不能登录到另一个云用户的实例中，除非他们共享了他们的SSH key文件。使用一个SSH秘钥对，你可以管理多个实例。"
+
+# 0edd947ce47c438daad162beb19d2fd7
+#: ../../virtual_machines.rst:1025
+msgid "Creating an Instance Template that Supports SSH Keys"
+msgstr "创建一个支持SSH秘钥的实例模板"
+
+# f2ce122e2dcf433a8945e8c2d923e2b6
+#: ../../virtual_machines.rst:1027
+msgid "Create an instance template that supports SSH Keys."
+msgstr "创建一个支持SSH秘钥的实例模板。"
+
+# c683112d085244fabffdc696c868fdf2
+#: ../../virtual_machines.rst:1029
+msgid "Create a new instance by using the template provided by cloudstack."
+msgstr "使用CloudStack提供的模板创建一个新的实例。"
+
+# 0409d2f2d7964ac28bfeb8bed3f58e12
+#: ../../virtual_machines.rst:1031
+msgid "For more information on creating a new instance, see"
+msgstr "关于创建新实例的更多信息，请参阅"
+
+# 497da833fd9642c39f7ca84fadb0ce84
+#: ../../virtual_machines.rst:1033
+msgid ""
+"Download the cloudstack script from `The SSH Key Gen Script "
+"<http://sourceforge.net/projects/cloudstack/files/SSH%20Key%20Gen%20Script/>`_"
+" to the instance you have created."
+msgstr "从 `The SSH Key Gen Script <http://sourceforge.net/projects/cloudstack/files/SSH%20Key%20Gen%20Script/>`_ 下载CloudStack脚本到你已经创建的实例中。"
+
+# 339a3d87be144308915639d37c89ea1d
+#: ../../virtual_machines.rst:1041
+msgid "Copy the file to /etc/init.d."
+msgstr "复制这个脚本到 /etc/init.d。"
+
+# f601fce5097849559dc10a71eeb440a9
+#: ../../virtual_machines.rst:1047
+msgid "Give the necessary permissions on the script:"
+msgstr "给这个脚本必要的权限："
+
+# a5a38d6cf81845aa81cbb049a6c03108
+#: ../../virtual_machines.rst:1053
+msgid "Run the script while starting up the operating system:"
+msgstr "当系统启动的时候运行脚本："
+
+# 733b18c1fccb453396b69626f1da7452
+#: ../../virtual_machines.rst:1059
+msgid "Stop the instance."
+msgstr "停止实例。"
+
+# 580da0c9298f41699deb34011b0310e6
+#: ../../virtual_machines.rst:1063
+msgid "Creating the SSH Keypair"
+msgstr "创建SSH秘钥对"
+
+# c5ac52360d7941528588398acbb420e8
+#: ../../virtual_machines.rst:1065
+msgid ""
+"You must make a call to the createSSHKeyPair api method. You can either use "
+"the CloudStack Python API library or the curl commands to make the call to "
+"the cloudstack api."
+msgstr "你必须给createSSHKeyPair api方法做一个调用。你可以使用CloudStack Python API 库或curl 命令给CloudStack API做调用。"
+
+# 89cec2df86664c26bafeddd6fd2aa054
+#: ../../virtual_machines.rst:1069
+msgid ""
+"For example, make a call from the cloudstack server to create a SSH keypair "
+"called \"keypair-doc\" for the admin account in the root domain:"
+msgstr "比如，从CloudStack服务器为根域中的管理员帐户做调用来创建一个SSH秘钥对 ，名称为 \"keypair-doc\" ："
+
+# c57fbd36512446559d91c1b7eeff7cea
+#: ../../virtual_machines.rst:1073
+msgid ""
+"Ensure that you adjust these values to meet your needs. If you are making "
+"the API call from a different server, your URL/PORT will be different, and "
+"you will need to use the API keys."
+msgstr "确认你调整这些值是你所需要的。如果你从不同的服务器上做API调用，你的 URL/PORT 也是不同的，并且你必须使用API 秘钥。"
+
+# 6d651f1b57ef4e81ade3cdafcc642e4b
+#: ../../virtual_machines.rst:1077
+msgid "Run the following curl command:"
+msgstr "运行如下curl命令："
+
+# 665246c92ab74234b1790979863082a7
+#: ../../virtual_machines.rst:1083
+msgid "The output is something similar to what is given below:"
+msgstr "输出的内容与下面所示的类似："
+
+# 64c5993f04f043b5a0e5925aef2db171
+#: ../../virtual_machines.rst:1101
+msgid "Copy the key data into a file. The file looks like this:"
+msgstr "复制秘钥的数据到一个文件。这个文件类似于："
+
+# cf75a310b6854564b8053aa63328f6ce
+#: ../../virtual_machines.rst:1118
+msgid "Save the file."
+msgstr "保存文件。"
+
+# 87cc3ec398db47f09bc21e1a66c8720f
+#: ../../virtual_machines.rst:1122
+msgid "Creating an Instance"
+msgstr "创建实例"
+
+# e115c665e72345fcab3fc94458caa818
+#: ../../virtual_machines.rst:1124
+msgid ""
+"After you save the SSH keypair file, you must create an instance by using "
+"the template that you created at `Section 5.2.1, “ Creating an Instance "
+"Template that Supports SSH Keys” <#create-ssh-template>`__. Ensure that you "
+"use the same SSH key name that you created at `Section 5.2.2, “Creating the "
+"SSH Keypair” <#create-ssh-keypair>`__."
+msgstr "在你保存了SSH秘钥对文件之后，你必须使用你在`章节 5.2.1, “ 创建支持SSH秘钥的实例模板” <#create-ssh-template>`__中创建的模来板创建一个实例。确保你使用与你在`章节 5.2.2, “创建秘钥对” <#create-ssh-keypair>`__中创建的同样的SSH秘钥名称。"
+
+# 8e5a7943aaf741989b2f9aa7c92fa061
+#: ../../virtual_machines.rst:1131
+msgid ""
+"You cannot create the instance by using the GUI at this time and associate "
+"the instance with the newly created SSH keypair."
+msgstr "这时候你不能通过使用 GUI来创建实例，要使用新创建的SSH秘钥对来关联实例。"
+
+# bb36e5f1a5cc497bb95f96481cd3c232
+#: ../../virtual_machines.rst:1134
+msgid "A sample curl command to create a new instance is:"
+msgstr "使用简单的curl命令创建新的实例："
+
+# 9a98f03016ba40f1b8eb932e8e15a75c
+#: ../../virtual_machines.rst:1140
+msgid ""
+"Substitute the template, service offering and security group IDs (if you are"
+" using the security group feature) that are in your cloud environment."
+msgstr "在你的云环境中，服务方案和安全组IDs(如果你使用安全组功能)可以替代模板。"
+
+# 9c448726db0b469bb32323df48aeba12
+#: ../../virtual_machines.rst:1146
+msgid "Logging In Using the SSH Keypair"
+msgstr "使用SSH秘钥对登录"
+
+# 5276ff9c384b4372bc6814b7f7461ae2
+#: ../../virtual_machines.rst:1148
+msgid ""
+"To test your SSH key generation is successful, check whether you can log in "
+"to the cloud setup."
+msgstr "测试你的SSH秘钥的生成是否成功，需要检查是否能够登录到云中。"
+
+# 632b48d2ebaf4620be47c9bc1b6e1d39
+#: ../../virtual_machines.rst:1151
+msgid "For example, from a Linux OS, run:"
+msgstr "举个例子，在LinuxOS中，运行："
+
+# b597ba33b4154d5c95931e7a30a1aa41
+#: ../../virtual_machines.rst:1157
+msgid ""
+"The -i parameter tells the ssh client to use a ssh key found at ~/.ssh"
+"/keypair-doc."
+msgstr "参数-i是通知ssh客户端使用一个在~/.ssh/keypair-doc中找到的ssh秘钥。"
+
+# 0ebe651140d94e709efff80066e042b7
+#: ../../virtual_machines.rst:1162
+msgid "Resetting SSH Keys"
+msgstr "重置SSH密钥"
+
+# 1367090489eb4ad68179bce4ba266e37
+#: ../../virtual_machines.rst:1164
+msgid ""
+"With the API command resetSSHKeyForVirtualMachine, a user can set or reset "
+"the SSH keypair assigned to a virtual machine. A lost or compromised SSH "
+"keypair can be changed, and the user can access the VM by using the new "
+"keypair. Just create or register a new keypair, then call "
+"resetSSHKeyForVirtualMachine."
+msgstr "通过API命令resetSSHKeyForVirtualMachine，用户可以设置或者重设分配给虚拟机的SSH秘钥对。可以更改丢失或被盗用的SSH密钥对，并且用户可以使用新的秘钥对来访问VM。只要创建或注册新的密钥对然后调用resetSSHKeyForVirtualMachine。"
diff --git a/source/adminguide/management.rst b/source/adminguide/management.rst
new file mode 100644
index 0000000..d45def1
--- /dev/null
+++ b/source/adminguide/management.rst
@@ -0,0 +1,512 @@
+.. 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.
+
+
+Using Tags to Organize Resources in the Cloud
+---------------------------------------------
+
+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.
+
+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.
+
+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.
+
+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:
+
+.. code:: bash
+
+ command=listVolumes
+ &listAll=true
+ &tags[0].key=region
+ &tags[0].value=canada
+ &tags[1].key=city
+ &tags[1].value=Toronto
+
+The following API commands have the "tags" input parameter:
+
+- listVirtualMachines
+
+- listVolumes
+
+- listSnapshots
+
+- listNetworks
+
+- listTemplates
+
+- listIsos
+
+- listFirewallRules
+
+- listPortForwardingRules
+
+- listPublicIpAddresses
+
+- listSecurityGroups
+
+- listLoadBalancerRules
+
+- listProjects
+
+- listVPCs
+
+- listNetworkACLs
+
+- listStaticRoutes
+
+
+Reporting CPU Sockets
+---------------------
+
+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 the
+number of hosts and sockets used for each host type.
+
+1. Log in to the PRODUCT UI.
+
+2. In the left navigation bar, click Infrastructure.
+
+3. On CPU Sockets, click View all.
+
+ The CPU Socket page is displayed. The page shows the number of hosts
+ and CPU sockets based on hypervisor types.
+
+
+Changing the Database Configuration
+-----------------------------------
+
+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.
+
+Changing the Database Password
+------------------------------
+
+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``.
+
+#. Before changing the password, you'll need to stop CloudStack's
+ management server and the usage engine if you've deployed that
+ component.
+
+ .. code:: bash
+
+ # service cloudstack-management stop
+ # service cloudstack-usage stop
+
+#. Next, you'll update the password for the CloudStack user on the MySQL
+ server.
+
+ .. code:: bash
+
+ # mysql -u root -p
+
+ At the MySQL shell, you'll change the password and flush privileges:
+
+ .. code:: bash
+
+ update mysql.user set password=PASSWORD("newpassword123") where User='cloud';
+ flush privileges;
+ quit;
+
+#. The next step is to encrypt the password and copy the encrypted
+ password to CloudStack's database configuration
+ (``/etc/cloudstack/management/db.properties``).
+
+ .. code:: bash
+
+ # java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.0.jar \ org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh \ input="newpassword123" password="`cat /etc/cloudstack/management/key`" \ verbose=false
+
+
+File encryption type
+--------------------
+
+ 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"
+
+#. 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:
+
+ .. code:: bash
+
+ db.cloud.password=ENC(encrypted_password_from_above)
+ db.usage.password=ENC(encrypted_password_from_above)
+
+#. After copying the new password over, you can now start CloudStack
+ (and the usage engine, if necessary).
+
+ .. code:: bash
+
+ # service cloudstack-management start
+ # service cloud-usage start
+
+
+Administrator Alerts
+--------------------
+
+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.
+
+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.
+
+Emails will be sent to administrators under the following circumstances:
+
+- The Management Server cluster runs low on CPU, memory, or storage
+ resources
+
+- The Management Server loses heartbeat from a Host for more than 3
+ minutes
+
+- The Host cluster runs low on CPU, memory, or storage resources
+
+
+Sending Alerts to External SNMP and Syslog Managers
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+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.
+
+The alerts which can be sent are:
+
+The following is the list of alert type numbers. The current alerts can
+be found by calling listAlerts.
+
+::
+
+ MEMORY = 0 // Available Memory below configured threshold
+
+::
+
+ CPU = 1 // Unallocated CPU below configured threshold
+
+::
+
+ STORAGE =2 // Available Storage below configured threshold
+
+::
+
+ STORAGE_ALLOCATED = 3 // Remaining unallocated Storage is below configured threshold
+
+::
+
+ PUBLIC_IP = 4 // Number of unallocated virtual network public IPs is below configured threshold
+
+::
+
+ PRIVATE_IP = 5 // Number of unallocated private IPs is below configured threshold
+
+::
+
+ SECONDARY_STORAGE = 6 // Available Secondary Storage in availability zone is below configured threshold
+
+::
+
+ HOST = 7 // Host related alerts like host disconnected
+
+::
+
+ USERVM = 8 // User VM stopped unexpectedly
+
+::
+
+ DOMAIN_ROUTER = 9 // Domain Router VM stopped unexpectedly
+
+::
+
+ CONSOLE_PROXY = 10 // Console Proxy VM stopped unexpectedly
+
+::
+
+ ROUTING = 11 // Lost connection to default route (to the gateway)
+
+::
+
+ STORAGE_MISC = 12 // Storage issue in system VMs
+
+::
+
+ USAGE_SERVER = 13 // No usage server process running
+
+::
+
+ MANAGMENT_NODE = 14 // Management network CIDR is not configured originally
+
+::
+
+ DOMAIN_ROUTER_MIGRATE = 15 // Domain Router VM Migration was unsuccessful
+
+::
+
+ CONSOLE_PROXY_MIGRATE = 16 // Console Proxy VM Migration was unsuccessful
+
+::
+
+ USERVM_MIGRATE = 17 // User VM Migration was unsuccessful
+
+::
+
+ VLAN = 18 // Number of unallocated VLANs is below configured threshold in availability zone
+
+::
+
+ SSVM = 19 // SSVM stopped unexpectedly
+
+::
+
+ USAGE_SERVER_RESULT = 20 // Usage job failed
+
+::
+
+ STORAGE_DELETE = 21 // Failed to delete storage pool
+
+::
+
+ UPDATE_RESOURCE_COUNT = 22 // Failed to update the resource count
+
+::
+
+ USAGE_SANITY_RESULT = 23 // Usage Sanity Check failed
+
+::
+
+ DIRECT_ATTACHED_PUBLIC_IP = 24 // Number of unallocated shared network IPs is low in availability zone
+
+::
+
+ LOCAL_STORAGE = 25 // Remaining unallocated Local Storage is below configured threshold
+
+::
+
+ RESOURCE_LIMIT_EXCEEDED = 26 //Generated when the resource limit exceeds the limit. Currently used for recurring snapshots only
+
+
+You can also display the most up to date list by calling the API command ``listAlerts``.
+
+
+SNMP Alert Details
+^^^^^^^^^^^^^^^^^^
+
+The supported protocol is SNMP version 2.
+
+Each SNMP trap contains the following information: message, podId,
+dataCenterId, clusterId, and generationTime.
+
+
+Syslog Alert Details
+^^^^^^^^^^^^^^^^^^^^
+
+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.
+
+.. code:: bash
+
+ Date severity_level Management_Server_IP_Address/Name alertType:: value dataCenterId:: value podId:: value clusterId:: value message:: value
+
+For example:
+
+.. code:: bash
+
+ Mar 4 10:13:47 WARN localhost alertType:: managementNode message:: Management server node 127.0.0.1 is up
+
+Configuring SNMP and Syslog Managers
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+To configure one or more SNMP managers or Syslog managers to receive
+alerts from CloudStack:
+
+#. 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.
+
+#. Edit the file /etc/cloudstack/management/log4j-cloud.xml.
+
+ .. code:: bash
+
+ # vi /etc/cloudstack/management/log4j-cloud.xml
+
+#. 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 (,).
+
+ .. note::
+ The recommended maximum number of SNMP or Syslog managers is 20
+ for each.
+
+ 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).
+
+ .. code:: bash
+
+ <appender name="SNMP" class="org.apache.cloudstack.alert.snmp.SnmpTrapAppender">
+ <param name="Threshold" value="WARN"/> <!-- Do not edit. The alert feature assumes WARN. -->
+ <param name="SnmpManagerIpAddresses" value="10.1.1.1,10.1.1.2"/>
+ <param name="SnmpManagerPorts" value="162,162"/>
+ <param name="SnmpManagerCommunities" value="public,public"/>
+ <layout class="org.apache.cloudstack.alert.snmp.SnmpEnhancedPatternLayout"> <!-- Do not edit -->
+ <param name="PairDelimeter" value="//"/>
+ <param name="KeyValueDelimeter" value="::"/>
+ </layout>
+ </appender>
+
+ 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.
+
+ .. code:: bash
+
+ <appender name="ALERTSYSLOG">
+ <param name="Threshold" value="WARN"/>
+ <param name="SyslogHosts" value="10.1.1.1,10.1.1.2"/>
+ <param name="Facility" value="LOCAL6"/>
+ <layout>
+ <param name="ConversionPattern" value=""/>
+ </layout>
+ </appender>
+
+#. If your cloud has multiple Management Server nodes, repeat these
+ steps to edit log4j-cloud.xml on every instance.
+
+#. If you have made these changes while the Management Server is
+ running, wait a few minutes for the change to take effect.
+
+**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.
+
+
+Deleting an SNMP or Syslog Manager
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+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``.
+
+
+Customizing the Network Domain Name
+-----------------------------------
+
+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.
+
+#. Set the DNS suffix at the desired scope
+
+ - 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.
+
+ - 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.
+
+ - 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.
+
+#. 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.
+
+The source of the network domain that is used depends on the following
+rules.
+
+- For all networks, if a network domain is specified as part of a
+ network's own configuration, that value is used.
+
+- 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.
+
+- 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.
+
+- 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.
+
+
+Stopping and Restarting the Management Server
+---------------------------------------------------
+
+The root administrator will need to stop and restart the Management
+Server from time to time.
+
+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..
+
+To stop the Management Server, issue the following command at the
+operating system prompt on the Management Server node:
+
+.. code:: bash
+
+ # service cloudstack-management stop
+
+To start the Management Server:
+
+.. code:: bash
+
+ # service cloudstack-management start
+
diff --git a/source/adminguide/networking.rst b/source/adminguide/networking.rst
new file mode 100644
index 0000000..589c70e
--- /dev/null
+++ b/source/adminguide/networking.rst
@@ -0,0 +1,408 @@
+.. 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.
+
+Overview of Setting Up Networking for Users
+-------------------------------------------
+
+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:
+
+- Set up physical networks in zones
+
+- Set up several different providers for the same service on a single
+ physical network (for example, both Cisco and Juniper firewalls)
+
+- Bundle different types of network services into network offerings, so
+ users can choose the desired network services for any given virtual
+ machine
+
+- Add new network offerings as time goes on so end users can upgrade to
+ a better class of service on their network
+
+- Provide more ways for a network to be accessed by a user, such as
+ through a project of which the user is a member
+
+
+About Virtual Networks
+---------------------------
+
+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.
+
+
+Isolated Networks
+~~~~~~~~~~~~~~~~~
+
+An isolated network can be accessed only by virtual machines of a single
+account. Isolated networks have the following properties.
+
+- Resources such as VLAN are allocated and garbage collected
+ dynamically
+
+- There is one network offering for the entire network
+
+- The network offering can be upgraded or downgraded but it is for the
+ entire network
+
+For more information, see `“Configure Guest Traffic in an Advanced Zone”
+<networking2.html#configure-guest-traffic-in-an-advanced-zone>`_.
+
+
+Shared Networks
+~~~~~~~~~~~~~~~
+
+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.
+
+- Shared Networks are created by the administrator
+
+- Shared Networks can be designated to a certain domain
+
+- Shared Network resources such as VLAN and physical network that it
+ maps to are designated by the administrator
+
+- Shared Networks can be isolated by security groups
+
+- Public Network is a shared network that is not shown to the end users
+
+- 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>`_.
+
+
+Runtime Allocation of Virtual Network Resources
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+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.
+
+
+Network Service Providers
+-------------------------
+
+.. note::
+ For the most up-to-date list of supported network service providers,
+ see the CloudStack UI or call `listNetworkServiceProviders`.
+
+A service provider (also called a network element) is hardware or
+virtual appliance that makes a network service possible; for example, a
+firewall appliance can be installed in the cloud to provide firewall
+service. On a single network, multiple providers can provide the same
+network service. For example, a firewall service may be provided by
+Cisco or Juniper devices in the same physical network.
+
+You can have multiple instances of the same service provider in a
+network (say, more than one Juniper SRX device).
+
+If different providers are set up to provide the same service on the
+network, the administrator can create network offerings so users can
+specify which network service provider they prefer (along with the other
+choices offered in network offerings). Otherwise, CloudStack will choose
+which provider to use whenever the service is called for.
+
+*Supported Network Service Providers*
+
+CloudStack ships with an internal list of the supported service
+providers, and you can choose from this list when creating a network
+offering.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++----------------------+-----------+------------+----------+-------------+-------------+
+| | Virtual | Citrix | Juniper | F5 BigIP | Host based |
+| | Router | NetScaler | SRX | | (KVM/Xen) |
++======================+===========+============+==========+=============+=============+
+| Remote Access VPN | Yes | No | No | No | No |
++----------------------+-----------+------------+----------+-------------+-------------+
+| DNS/DHCP/User Data | Yes | No | No | No | No |
++----------------------+-----------+------------+----------+-------------+-------------+
+| Firewall | Yes | No | Yes | No | No |
++----------------------+-----------+------------+----------+-------------+-------------+
+| Load Balancing | Yes | Yes | No | Yes | No |
++----------------------+-----------+------------+----------+-------------+-------------+
+| Elastic IP | No | Yes | No | No | No |
++----------------------+-----------+------------+----------+-------------+-------------+
+| Elastic LB | No | Yes | No | No | No |
++----------------------+-----------+------------+----------+-------------+-------------+
+| Source NAT | Yes | No | Yes | No | No |
++----------------------+-----------+------------+----------+-------------+-------------+
+| Static NAT | Yes | Yes | Yes | No | No |
++----------------------+-----------+------------+----------+-------------+-------------+
+| Port Forwarding | Yes | No | Yes | No | No |
++----------------------+-----------+------------+----------+-------------+-------------+
+
+
+Network Offerings
+-----------------
+
+.. note::
+ For the most up-to-date list of supported network services, see the
+ CloudStack UI or call listNetworkServices.
+
+A network offering is a named set of network services, such as:
+
+- DHCP
+
+- DNS
+
+- Source NAT
+
+- Static NAT
+
+- Port Forwarding
+
+- Load Balancing
+
+- Firewall
+
+- VPN
+
+- (Optional) Name one of several available providers to use for a given
+ service, such as Juniper for the firewall
+
+- (Optional) Network tag to specify which physical network to use
+
+When creating a new VM, the user chooses one of the available network
+offerings, and that determines which network services the VM can use.
+
+The 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 a web server farm and require a scalable firewall solution, load
+balancing solution, and alternate networks for accessing the database
+backend.
+
+.. note::
+ 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.
+
+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.
+
+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.
+
+
+Creating a New Network Offering
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To create a network offering:
+
+#. Log in with admin privileges to the CloudStack UI.
+
+#. In the left navigation bar, click Service Offerings.
+
+#. In Select Offering, choose Network Offering.
+
+#. Click Add Network Offering.
+
+#. In the dialog, make the following choices:
+
+ - **Name**. Any desired name for the network offering.
+
+ - **Description**. A short description of the offering that can be
+ displayed to users.
+
+ - **Network Rate**. Allowed data transfer rate in MB per second.
+
+ - **Guest Type**. Choose whether the guest network is isolated or
+ shared.
+
+ For a description of this term, see `“About Virtual
+ Networks” <#about-virtual-networks>`_.
+
+ - **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>`_.
+
+ - **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.
+
+ - **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>`_.
+
+ - **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.
+
+ Based on the guest network type selected, you can see the
+ following supported services:
+
+ .. cssclass:: table-striped table-bordered table-hover
+
+ =================== ============================================================================ ============= =============
+ Supported Services Description Isolated Shared
+ =================== ============================================================================ ============= =============
+ DHCP For more information, see `“DNS and DHCP” <networking2.html#dns-and-dhcp>`_. Supported Supported
+ DNS For more information, see `“DNS and DHCP” <networking2.html#dns-and-dhcp>`_. Supported Supported
+ Load Balancer If you select Load Balancer, you can choose the CloudStack virtual Supported Supported
+ router or any other load balancers that have been configured in
+ the cloud.
+ Firewall For more information, see the Administration Guide. Supported Supported
+ Source NAT If you select Source NAT, you can choose the CloudStack virtual Supported Supported
+ router or any other Source NAT providers that have been configured
+ in the cloud.
+ Static NAT If you select Static NAT, you can choose the CloudStack virtual Supported Supported
+ router or any other Static NAT providers that have been configured
+ in the cloud.
+ Port Forwarding If you select Port Forwarding, you can choose the CloudStack Supported Not Supported
+ virtual router or any other Port Forwarding providers that have
+ been configured in the cloud.
+ VPN For more information, see `“Remote Access Supported Not Supported
+ VPN” <networking2.html#remote-access-vpn>`_.
+ User Data For more information, see `“User Data and Meta Not Supported Supported
+ Data” <api.html#user-data-and-meta-data>`_.
+ Network ACL For more information, see `“Configuring Network Access Supported Not Supported
+ Control List” <networking2.html#configuring-network-access-control-list>`_.
+ Security Groups For more information, see `“Adding a Security Not Supported Supported
+ Group” <networking2.html#adding-a-security-group>`_.
+ =================== ============================================================================ ============= =============
+
+
+ - **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 custom system service offerings
+ that have been defined by the CloudStack root administrator.
+
+ For more information, see `“System Service Offerings”
+ <service_offerings.html#system-service-offerings>`_.
+
+ - **LB Isolation**: Specify what type of load balancer isolation you
+ want for the network: Shared or Dedicated.
+
+ **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.
+
+ **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.
+
+ - **Mode**: You can select either Inline mode or Side by Side mode:
+
+ **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.
+
+ **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.
+
+ - **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
+
+ - Guest network is shared.
+
+ - StaticNAT is enabled.
+
+ - Elastic IP is enabled.
+
+ For information on Elastic IP, see `“About Elastic IP”
+ <networking2.html#about-elastic-ip>`_.
+
+ - **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 master virtual router.
+ CloudStack deploys the routers on different hosts to ensure
+ reliability if one host is down.
+
+ - **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.
+
+ .. note::
+ 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.
+
+ - **Tags**: Network tag to specify which physical network to use.
+
+ - **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.
+
+ 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.
+
+#. Click Add.
+
diff --git a/source/adminguide/networking/acquiring_an_ip_address.rst b/source/adminguide/networking/acquiring_an_ip_address.rst
new file mode 100644
index 0000000..b6556db
--- /dev/null
+++ b/source/adminguide/networking/acquiring_an_ip_address.rst
@@ -0,0 +1,42 @@
+.. 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.
+
+
+Acquiring a New IP Address
+--------------------------
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. Click the name of the network where you want to work with.
+
+#. Click View IP Addresses.
+
+#. Click Acquire New IP.
+
+ The Acquire New IP window is displayed.
+
+#. Specify whether you want cross-zone IP or not.
+
+ If you want Portable IP click Yes in the confirmation dialog. If you
+ want a normal Public IP click No.
+
+ For more information on Portable IP, see `"Portable
+ IPs" <#portable-ips>`_.
+
+ 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.
diff --git a/source/adminguide/networking/advanced_zone_config.rst b/source/adminguide/networking/advanced_zone_config.rst
new file mode 100644
index 0000000..63027b3
--- /dev/null
+++ b/source/adminguide/networking/advanced_zone_config.rst
@@ -0,0 +1,152 @@
+.. 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.
+
+
+
+Advanced Zone Physical Network Configuration
+--------------------------------------------
+
+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.
+
+
+Configure Guest Traffic in an Advanced Zone
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+These steps assume you have already logged in to the CloudStack UI. To
+configure the base guest network:
+
+#. In the left navigation, choose Infrastructure. On Zones, click View
+ More, then click the zone to which you want to add a network.
+
+#. Click the Network tab.
+
+#. Click Add guest network.
+
+ The Add guest network window is displayed:
+
+ |addguestnetwork.png|
+
+#. Provide the following information:
+
+ - **Name**: The name of the network. This will be user-visible
+
+ - **Display Text**: The description of the network. This will be
+ user-visible
+
+ - **Zone**: The zone in which you are configuring the guest network.
+
+ - **Network offering**: If the administrator has configured multiple
+ network offerings, select the one you want to use for this network
+
+ - **Guest Gateway**: The gateway that the guests should use
+
+ - **Guest Netmask**: The netmask in use on the subnet the guests
+ will use
+
+#. Click OK.
+
+
+Configure Public Traffic in an Advanced Zone
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+In a zone that uses advanced networking, you need to configure at least
+one range of IP addresses for Internet traffic.
+
+
+Configuring a Shared Guest Network
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. Log in to the CloudStack UI as administrator.
+
+#. In the left navigation, choose Infrastructure.
+
+#. On Zones, click View More.
+
+#. Click the zone to which you want to add a guest network.
+
+#. Click the Physical Network tab.
+
+#. Click the physical network you want to work with.
+
+#. On the Guest node of the diagram, click Configure.
+
+#. Click the Network tab.
+
+#. Click Add guest network.
+
+ The Add guest network window is displayed.
+
+#. Specify the following:
+
+ - **Name**: The name of the network. This will be visible to the user.
+
+ - **Description**: The short description of the network that can be
+ displayed to users.
+
+ - **VLAN ID**: The unique ID of the VLAN.
+
+ - **Isolated VLAN ID**: The unique ID of the Secondary Isolated
+ VLAN.
+
+ - **Scope**: The available scopes are Domain, Account, Project, and
+ All.
+
+ - **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.
+
+ - **Account**: The account for which the guest network is being
+ created for. You must specify the domain the account belongs
+ to.
+
+ - **Project**: The project for which the guest network is being
+ created for. You must specify the domain the project belongs
+ to.
+
+ - **All**: The guest network is available for all the domains,
+ account, projects within the selected zone.
+
+ - **Network Offering**: If the administrator has configured multiple
+ network offerings, select the one you want to use for this
+ network.
+
+ - **Gateway**: The gateway that the guests should use.
+
+ - **Netmask**: The netmask in use on the subnet the guests will use.
+
+ - **IP Range**: A range of IP addresses that are accessible from the
+ Internet and are assigned to the guest VMs.
+
+ If one NIC is used, these IPs should be in the same CIDR in the
+ case of IPv6.
+
+ - **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.
+
+ - **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.
+
+#. Click OK to confirm.
+
+
+.. |addguestnetwork.png| image:: /_static/images/add-guest-network.png
+ :alt: Add Guest network setup in a single zone.
\ No newline at end of file
diff --git a/source/adminguide/networking/basic_zone_config.rst b/source/adminguide/networking/basic_zone_config.rst
new file mode 100644
index 0000000..a1ba26c
--- /dev/null
+++ b/source/adminguide/networking/basic_zone_config.rst
@@ -0,0 +1,24 @@
+.. 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.
+
+
+
+Basic Zone Physical Network Configuration
+-----------------------------------------
+
+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.
\ No newline at end of file
diff --git a/source/adminguide/networking/dns_and_dhcp.rst b/source/adminguide/networking/dns_and_dhcp.rst
new file mode 100644
index 0000000..c84cffa
--- /dev/null
+++ b/source/adminguide/networking/dns_and_dhcp.rst
@@ -0,0 +1,22 @@
+.. 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.
+
+
+DNS and DHCP
+------------
+
+The Virtual Router provides DNS and DHCP services to the guests. It
+proxies DNS requests to the DNS server configured on the Availability
+Zone.
diff --git a/source/adminguide/networking/elastic_ips.rst b/source/adminguide/networking/elastic_ips.rst
new file mode 100644
index 0000000..fe83a3b
--- /dev/null
+++ b/source/adminguide/networking/elastic_ips.rst
@@ -0,0 +1,104 @@
+.. 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.
+
+
+About Elastic IPs
+-----------------
+
+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 is down,
+the IP address can be reassigned to a new VM in your account.
+
+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.
+
+|eip-ns-basiczone.png|
+
+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 data center goes
+through the firewall.
+
+The EIP work flow is as follows:
+
+- 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.
+
+- 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.
+
+ .. note::
+ 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.
+
+- This default public IP will be released in two cases:
+
+ - 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.
+
+ - 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.
+
+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 and enable static
+NAT.
+
+For more information on the Associate Public IP option, see
+`"Creating a New Network Offering" <networking.html#creating-a-new-network-offering>`_.
+
+.. note::
+ 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.
+
+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.
+
+
+.. |eip-ns-basiczone.png| image:: /_static/images/eip-ns-basiczone.png
+ :alt: Elastic IP in a NetScaler-enabled Basic Zone.
diff --git a/source/adminguide/networking/external_firewalls_and_load_balancers.rst b/source/adminguide/networking/external_firewalls_and_load_balancers.rst
new file mode 100644
index 0000000..c0a2caa
--- /dev/null
+++ b/source/adminguide/networking/external_firewalls_and_load_balancers.rst
@@ -0,0 +1,661 @@
+.. 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.
+
+
+External Firewalls and Load Balancers
+-------------------------------------
+
+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.
+
+
+About Using a NetScaler Load Balancer
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+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.
+
+.. note::
+ In a Basic zone, load balancing service is supported only if
+ Elastic IP or Elastic LB services are enabled.
+
+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 device
+providing EIP/ELB, layer 3 router must have a policy-based routing. A
+policy-based route must be set up so that all traffic originated from
+the guest VM's are directed to NetScaler device. This is required to
+ensure that the outbound traffic from the guest VM's is routed to a
+public IP by using NAT.For more information on Elastic IP, see
+`"About Elastic IP" <#about-elastic-ip>`_.
+
+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.
+
+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.
+
+To install and enable an external load balancer for CloudStack
+management, see External Guest Load Balancer Integration in the
+Installation Guide.
+
+The Citrix NetScaler comes in three varieties. The following
+summarizes how these variants are treated in CloudStack.
+
+**MPX**
+
+- Physical appliance. Capable of deep packet inspection. Can act as
+ application firewall and load balancer
+
+- 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.
+
+**VPX**
+
+- Virtual appliance. Can run as VM on XenServer, ESXi, and Hyper-V
+ hypervisors. Same functionality as MPX
+
+- Supported on ESXi and XenServer. Same functional support as for MPX.
+ CloudStack will treat VPX and MPX as the same device type.
+
+**SDX**
+
+- Physical appliance. Can create multiple fully isolated VPX instances on
+ a single appliance to support multi-tenant usage
+
+- 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.
+
+
+Configuring SNMP Community String on a RHEL Server
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+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.
+
+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.
+
+#. Ensure that you installed SNMP on RedHat. If not, run the following
+ command:
+
+ .. code:: bash
+
+ yum install net-snmp-utils
+
+#. Edit the /etc/snmp/snmpd.conf file to allow the SNMP polling from the
+ NetScaler device.
+
+ #. Map the community name into a security name (local and mynetwork,
+ depending on where the request is coming from):
+
+ .. note::
+ Use a strong password instead of public when you edit the
+ following table.
+
+ .. code:: bash
+
+ # sec.name source community
+ com2sec local localhost public
+ com2sec mynetwork 0.0.0.0 public
+
+ .. note:: Setting to 0.0.0.0 allows all IPs to poll the NetScaler server.
+
+ #. Map the security names into group names:
+
+ .. code:: bash
+
+ # group.name sec.model sec.name
+ group MyRWGroup v1 local
+ group MyRWGroup v2c local
+ group MyROGroup v1 mynetwork
+ group MyROGroup v2c mynetwork
+
+ #. Create a view to allow the groups to have the permission to:
+
+ .. code:: bash
+
+ incl/excl subtree mask view all included .1
+
+ #. Grant access with different write permissions to the two groups to
+ the view you created.
+
+ .. code:: bash
+
+ # context sec.model sec.level prefix read write notif
+ access MyROGroup "" any noauth exact all none none
+ access MyRWGroup "" any noauth exact all all all
+
+#. Unblock SNMP in iptables.
+
+ .. code:: bash
+
+ iptables -A INPUT -p udp --dport 161 -j ACCEPT
+
+#. Start the SNMP service:
+
+ .. code:: bash
+
+ service snmpd start
+
+#. Ensure that the SNMP service is started automatically during the
+ system startup:
+
+ .. code:: bash
+
+ chkconfig snmpd on
+
+
+Initial Setup of External Firewalls and Load Balancers
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+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:
+
+- 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).
+
+- 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
+
+- A firewall filter counter that measures the number of bytes of
+ outgoing traffic for the account
+
+The following objects are created on the load balancer:
+
+- A new VLAN that matches the account's provisioned Zone VLAN
+
+- A self IP for the VLAN. This is always the second IP of the account's
+ private subnet (e.g. 10.1.1.2).
+
+
+Ongoing Configuration of External Firewalls and Load Balancers
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+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
+objects:
+
+- A static NAT rule that maps the public IP address to the private IP
+ address of a VM.
+
+- A security policy that allows traffic within the set of protocols and
+ port ranges that are specified.
+
+- A firewall filter counter that measures the number of bytes of
+ incoming traffic to the public IP.
+
+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.
+
+
+Load Balancer Rules
+~~~~~~~~~~~~~~~~~~~
+
+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.
+
+.. note::
+ 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.
+
+
+.. _adding-lb-rule:
+
+Adding a Load Balancer Rule
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. Click the name of the network where you want to load balance the
+ traffic.
+
+#. Click View IP Addresses.
+
+#. Click the IP address for which you want to create the rule, then
+ click the Configuration tab.
+
+#. In the Load Balancing node of the diagram, click View All.
+
+ In a Basic zone, you can also create a load 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.
+
+ To do that, select the name of the network, then click Add Load
+ Balancer tab. Continue with #7.
+
+#. Fill in the following:
+
+ - **Name**: A name for the load balancer rule.
+
+ - **Public Port**: The port receiving incoming traffic to be
+ balanced.
+
+ - **Private Port**: The port that the VMs will use to receive the
+ traffic.
+
+ - **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.
+
+ - **Stickiness**: (Optional) Click Configure and choose the
+ algorithm for the stickiness policy. See Sticky Session Policies
+ for Load Balancer Rules.
+
+ - **AutoScale**: Click Configure and complete the AutoScale
+ configuration as explained in :ref:`conf-autoscale`.
+
+ - **Health Check**: (Optional; NetScaler load balancers only) Click
+ Configure and fill in the characteristics of the health check
+ policy. See :ref:`health-check`.
+
+ - **Ping path (Optional)**: Sequence of destinations to which to
+ send health check queries. Default: / (all).
+
+ - **Response time (Optional)**: How long to wait for a response
+ from the health check (2 - 60 seconds). Default: 5 seconds.
+
+ - **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.
+
+ - **Healthy threshold (Optional)**: Number of consecutive health
+ check successes that are required before declaring an instance
+ healthy. Default: 2.
+
+ - **Unhealthy threshold (Optional)**: Number of consecutive
+ health check failures that are required before declaring an
+ instance unhealthy. Default: 10.
+
+#. Click Add VMs, then select two or more VMs that will divide the load
+ of incoming traffic, and click Apply.
+
+ The new load balancer rule appears in the list. You can repeat these
+ steps to add more load balancer rules for this IP address.
+
+
+Sticky Session Policies for Load Balancer Rules
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+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.
+
+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, cookies are used. The cookie generated by the load balancer or
+application is included in request and response URLs to create
+persistence. The cookie name can be specified by the administrator or
+automatically generated. A variety of options are provided to control
+the exact behavior of cookies, such as how they are generated and
+whether they are cached.
+
+For the most up to date list of available stickiness methods, see the
+CloudStack UI or call listNetworks and check the
+SupportedStickinessMethods capability.
+
+
+.. _health-check:
+
+Health Checks for Load Balancer Rules
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+(NetScaler load balancer only; requires NetScaler version 10.0)
+
+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.
+
+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.
+
+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 with a
+health check configured, the state will be shown as UP or DOWN in the UI
+depending on the result of the most recent health check.
+
+You can delete or modify existing health check policies.
+
+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.
+
+For details on how to set a health check policy using the UI, see
+:ref:`adding-lb-rule`.
+
+
+.. _conf-autoscale:
+
+Configuring AutoScale
+~~~~~~~~~~~~~~~~~~~~~
+
+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.
+
+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 CPU usage
+is less than 20 percent for 30 minutes.
+
+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.
+
+.. note::
+ AutoScale is supported on NetScaler Release 10 Build 74.4006.e and beyond.
+
+
+Prerequisites
+^^^^^^^^^^^^^
+
+Before you configure an AutoScale rule, consider the following:
+
+- 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.
+
+ .. note::
+ 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.
+
+- 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.
+
+- 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-server>`_
+ to configure SNMP on a RHEL machine.
+
+- 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.
+
+ 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`.
+
+- 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.
+
+- 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.
+
+
+Configuration
+^^^^^^^^^^^^^
+
+Specify the following:
+
+|autoscaleateconfig.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.
+
+ .. note::
+ 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 active instance count breaches the Max instance
+ value.
+
+- **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.
+
+ .. note::
+ 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.
+
+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. 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.
+
+- **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.
+
+- **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.
+
+- **Disk Offerings**: A predefined set of disk size for primary data
+ storage.
+
+- **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.
+
+- **SNMP Port**: The port number on which the SNMP agent that run on
+ the provisioned VMs is listening. Default port is 161.
+
+- **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.
+
+- **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 |EnableDisable.png| 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 |EnableDisable.png| button.
+
+
+.. _update-autoscale:
+
+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.
+
+- 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.
+
+- 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.
+
+
+.. |autoscaleateconfig.png| image:: /_static/images/autoscale-config.png
+ :alt: Configuring AutoScale.
+.. |EnableDisable.png| image:: /_static/images/enable-disable-autoscale.png
+ :alt: button to enable or disable AutoScale.
diff --git a/source/adminguide/networking/global_server_load_balancing.rst b/source/adminguide/networking/global_server_load_balancing.rst
new file mode 100644
index 0000000..e25ea45
--- /dev/null
+++ b/source/adminguide/networking/global_server_load_balancing.rst
@@ -0,0 +1,453 @@
+.. 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.
+
+
+Global Server Load Balancing Support
+------------------------------------
+
+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.
+
+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.
+
+
+About Global Server Load Balancing
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Global Server Load Balancing (GSLB) is an extension of load balancing
+functionality, which is highly efficient in avoiding downtime. Based on
+the nature of deployment, GSLB represents a set of technologies that is
+used for various purposes, such as load sharing, disaster recovery,
+performance, and legal obligations. With GSLB, workloads can be
+distributed across multiple data centers situated at geographically
+separated locations. GSLB can also provide an alternate location for
+accessing a resource in the event of a failure, or to provide a means of
+shifting traffic easily to simplify maintenance, or both.
+
+
+Components of GSLB
+^^^^^^^^^^^^^^^^^^
+
+A typical GSLB environment is comprised of the following components:
+
+- **GSLB Site**: In 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.
+
+- **GSLB Services**: A GSLB service is typically represented by a load
+ balancing or content switching virtual server. In a GSLB environment,
+ you can have a local as well as remote GSLB services. A local GSLB
+ service represents a local load balancing or content switching
+ virtual server. A remote GSLB service is the one configured at one of
+ the other sites in the GSLB setup. At each site in the GSLB setup,
+ you can create one local GSLB service and any number of remote GSLB
+ services.
+
+- **GSLB Virtual Servers**: A GSLB virtual server refers to one or more
+ GSLB services and balances traffic between traffic across the VMs in
+ multiple zones by using the 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 a FQDN DNS name.
+
+- **Load Balancing or Content Switching Virtual Servers**: According to
+ Citrix NetScaler terminology, a load balancing or content switching
+ virtual server represents one or many servers on the local network.
+ Clients send their requests to the load balancing or content
+ switching virtual server's virtual IP (VIP) address, and the virtual
+ server balances the load across the local servers. After a GSLB
+ virtual server selects a GSLB service representing either a local or
+ a remote load balancing or content switching virtual server, the
+ client sends the request to that virtual server's VIP address.
+
+- **DNS VIPs**: DNS virtual IP represents a load balancing DNS virtual
+ server on the GSLB service provider. The DNS requests for domains for
+ which the GSLB service provider is authoritative can be sent to a DNS
+ VIP.
+
+- **Authoritative DNS**: ADNS (Authoritative Domain Name Server) is a
+ service that provides actual answer to DNS queries, such as web site
+ IP address. In a GSLB environment, an ADNS service responds only to
+ DNS requests for domains for which the GSLB service provider is
+ authoritative. When an ADNS service is configured, the service
+ provider owns that IP address and advertises it. When you create an
+ ADNS service, the NetScaler responds to DNS queries on the configured
+ ADNS service IP and port.
+
+
+How Does GSLB Works in CloudStack?
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+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
+xyztelco cloud. For that purpose, they launch two instances each in both
+the zones: VM1 and VM2 in Zone-1 and VM5 and VM6 in Zone-2. Tenant-A
+acquires a public IP, IP-1 in Zone-1, and configures a load balancer
+rule to load balance the traffic between VM1 and VM2 instances.
+CloudStack orchestrates setting up a virtual server on the LB service
+provider in Zone-1. Virtual server 1 that is set up on the LB service
+provider in Zone-1 represents a publicly accessible virtual server that
+client reaches at IP-1. The client traffic to virtual server 1 at IP-1
+will be load balanced across VM1 and VM2 instances.
+
+Tenant-A acquires another public IP, IP-2 in Zone-2 and sets up a load
+balancer rule to load balance the traffic between VM5 and VM6 instances.
+Similarly in Zone-2, 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 instances.
+At this point Tenant-A has the service enabled in both the zones, but
+has no means to set up a disaster recovery plan if one of the zone
+fails. Additionally, there is no way for Tenant-A to load balance the
+traffic intelligently to one of the zones based on load, proximity and
+so on. The cloud administrator of xyztelco provisions a GSLB service
+provider to both the zones. A GSLB provider is typically an ADC that has
+the ability to act as an ADNS (Authoritative Domain Name Server) and has
+the mechanism to monitor health of virtual servers both at local and
+remote sites. The cloud admin enables GSLB as a service to the tenants
+that use zones 1 and 2.
+
+|gslb.png|
+
+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 start
+monitoring the health of virtual server 1 and 2 in Zone-1. CloudStack
+will also orchestrate setting up GSLB virtual server 2 on GSLB service
+provider at Zone-2. CloudStack will bind virtual server 1 of Zone-1 and
+virtual server 2 of Zone-2 to GLSB virtual server 2. GSLB virtual server
+2 is configured to start monitoring the health of virtual server 1 and
+2. CloudStack will bind the domain A.xyztelco.com to both the GSLB
+virtual server 1 and 2. At this point, Tenant-A service will be globally
+reachable at A.xyztelco.com. The private DNS server for the domain
+xyztelcom.com is configured by the admin out-of-band to resolve the
+domain A.xyztelco.com to the GSLB providers at both the zones, which are
+configured as ADNS for the domain A.xyztelco.com. A client when sends a
+DNS request to resolve A.xyztelcom.com, will eventually get DNS
+delegation to the address of GSLB providers at zone 1 and 2. A client
+DNS request will be received by the GSLB provider. The GSLB provider,
+depending on the domain for which it needs to resolve, will pick up the
+GSLB virtual server associated with the domain. Depending on the health
+of the virtual servers being load balanced, DNS request for the domain
+will be resolved to the public IP associated with the selected virtual
+server.
+
+
+Configuring GSLB
+~~~~~~~~~~~~~~~~
+
+To configure a GSLB deployment, you must first configure a standard load
+balancing setup for each zone. This enables you to balance load across
+the different servers in each zone in the region. Then on the NetScaler
+side, configure both NetScaler appliances that you plan to add to each
+zone as authoritative DNS (ADNS) servers. Next, create a GSLB site for
+each zone, configure GSLB virtual servers for each site, create GLSB
+services, and bind the GSLB services to the GSLB virtual servers.
+Finally, bind the domain to the GSLB virtual servers. The GSLB
+configurations on the two appliances at the two different zones are
+identical, although each sites load-balancing configuration is specific
+to that site.
+
+Perform the following as a cloud administrator. As per the example given
+above, the administrator of xyztelco is the one who sets up GSLB:
+
+#. In the cloud.dns.name global parameter, specify the DNS name of your
+ tenant's cloud that make use of the GSLB service.
+
+#. On the NetScaler side, configure GSLB as given in `Configuring Global
+ Server Load Balancing (GSLB)
+ <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-con.html>`_:
+
+ #. Configuring a standard load balancing setup.
+
+ #. 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>`_.
+
+ #. Configure a GSLB site with site name formed from the domain name
+ details.
+
+ Configure a GSLB site with the site name formed from the domain
+ name.
+
+ As per the example given above, the site names are A.xyztelco.com
+ and B.xyztelco.com.
+
+ For more information, see `Configuring a Basic GSLB Site
+ <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-basic-site-tsk.html>`_.
+
+ #. Configure a GSLB virtual server.
+
+ 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>`_.
+
+ #. Configure a GSLB service for each virtual server.
+
+ 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>`_.
+
+ #. Bind the GSLB services to the GSLB virtual server.
+
+ 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>`_.
+
+ #. Bind domain name to GSLB virtual server. Domain name is obtained
+ from the domain details.
+
+ For more information, see `Binding a Domain to a GSLB Virtual
+ Server <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-bind-dom-vsvr-tsk.html>`_.
+
+#. In each zone that are participating in GSLB, add GSLB-enabled
+ NetScaler device.
+
+ For more information, see :ref:`enabling-gslb-in-ns`.
+
+As a domain administrator/ user perform the following:
+
+#. Add a GSLB rule on both the sites.
+
+ See ":ref:`adding-gslb-rule`".
+
+#. Assign load balancer rules.
+
+ See ":ref:`assigning-lb-rule-gslb`".
+
+
+Prerequisites and Guidelines
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+- The GSLB functionality is supported both Basic and Advanced zones.
+
+- GSLB is added as a new network service.
+
+- GSLB service provider can be added to a physical network in a zone.
+
+- The admin is allowed to enable or disable GSLB functionality at
+ region level.
+
+- The admin is allowed to configure a zone as GSLB capable or enabled.
+
+ A zone shall be considered as GSLB capable only if a GSLB service
+ provider is provisioned in the zone.
+
+- When users have VMs deployed in multiple availability zones which are
+ GSLB enabled, they can use the GSLB functionality to load balance
+ traffic across the VMs in multiple zones.
+
+- The users can use GSLB to load balance across the VMs across zones in
+ a region only if the admin has enabled GSLB in that region.
+
+- The users can load balance traffic across the availability zones in
+ the same region or different regions.
+
+- The admin can configure DNS name for the entire cloud.
+
+- The users can specify an unique name across the cloud for a globally
+ load balanced service. The provided name is used as the domain name
+ under the DNS name associated with the cloud.
+
+ The user-provided name along with the admin-provided DNS name is used
+ to produce a globally resolvable FQDN for the globally load balanced
+ service of the user. For example, if the admin has configured
+ xyztelco.com as the DNS name for the cloud, and user specifies 'foo'
+ for the GSLB virtual service, then the FQDN name of the GSLB virtual
+ service is foo.xyztelco.com.
+
+- While setting up GSLB, users can select a load balancing method, such
+ as round robin, for using across the zones that are part of GSLB.
+
+- The user shall be able to set weight to zone-level virtual server.
+ Weight shall be considered by the load balancing method for
+ distributing the traffic.
+
+- The GSLB functionality shall support session persistence, where
+ series of client requests for particular domain name is sent to a
+ virtual server on the same zone.
+
+ Statistics is collected from each GSLB virtual server.
+
+
+.. _enabling-gslb-in-ns:
+
+Enabling GSLB in NetScaler
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+In each zone, add GSLB-enabled NetScaler device for load balancing.
+
+#. Log in as administrator to the CloudStack UI.
+
+#. In the left navigation bar, click Infrastructure.
+
+#. In Zones, click View More.
+
+#. Choose the zone you want to work with.
+
+#. Click the Physical Network tab, then click the name of the physical
+ network.
+
+#. In the Network Service Providers node of the diagram, click
+ Configure.
+
+ You might have to scroll down to see this.
+
+#. Click NetScaler.
+
+#. Click Add NetScaler device and provide the following:
+
+ For NetScaler:
+
+ - **IP Address**: The IP address of the SDX.
+
+ - **Username/Password**: The authentication credentials to access
+ the device. CloudStack uses these credentials to access the
+ device.
+
+ - **Type**: The type of device that is being added. It could be F5
+ Big Ip Load Balancer, NetScaler VPX, NetScaler MPX, or NetScaler
+ SDX. For a comparison of the NetScaler types, see the CloudStack
+ Administration Guide.
+
+ - **Public interface**: Interface of device that is configured to be
+ part of the public network.
+
+ - **Private interface**: Interface of device that is configured to
+ be part of the private network.
+
+ - **GSLB service**: Select this option.
+
+ - **GSLB service Public IP**: The public IP address of the NAT
+ translator for a GSLB service that is on a private network.
+
+ - **GSLB service Private IP**: The private IP of the GSLB service.
+
+ - **Number of Retries**. Number of times to attempt a command on the
+ device before considering the operation failed. Default is 2.
+
+ - **Capacity**: The number of networks the device can handle.
+
+ - **Dedicated**: When marked as dedicated, this device will be
+ dedicated to a single account. When Dedicated is checked, the
+ value in the Capacity field has no significance implicitly, its
+ value is 1.
+
+#. Click OK.
+
+
+.. _adding-gslb-rule:
+
+Adding a GSLB Rule
+^^^^^^^^^^^^^^^^^^
+
+#. Log in to the CloudStack UI as a domain administrator or user.
+
+#. In the left navigation pane, click Region.
+
+#. Select the region for which you want to create a GSLB rule.
+
+#. In the Details tab, click View GSLB.
+
+#. Click Add GSLB.
+
+ The Add GSLB page is displayed as follows:
+
+ |gslb-add.png|
+
+#. Specify the following:
+
+ - **Name**: Name for the GSLB rule.
+
+ - **Description**: (Optional) A short description of the GSLB rule
+ that can be displayed to users.
+
+ - **GSLB Domain Name**: A preferred domain name for the service.
+
+ - **Algorithm**: (Optional) The algorithm to use to load balance the
+ traffic across the zones. The options are Round Robin, Least
+ Connection, and Proximity.
+
+ - **Service Type**: The transport protocol to use for GSLB. The
+ options are TCP and UDP.
+
+ - **Domain**: (Optional) The domain for which you want to create the
+ GSLB rule.
+
+ - **Account**: (Optional) The account on which you want to apply the
+ GSLB rule.
+
+#. Click OK to confirm.
+
+
+.. _assigning-lb-rule-gslb:
+
+Assigning Load Balancing Rules to GSLB
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. Log in to the CloudStack UI as a domain administrator or user.
+
+#. In the left navigation pane, click Region.
+
+#. Select the region for which you want to create a GSLB rule.
+
+#. In the Details tab, click View GSLB.
+
+#. Select the desired GSLB.
+
+#. Click view assigned load balancing.
+
+#. Click assign more load balancing.
+
+#. Select the load balancing rule you have created for the zone.
+
+#. Click OK to confirm.
+
+
+Known Limitation
+~~~~~~~~~~~~~~~~
+
+Currently, CloudStack does not support orchestration of services across
+the zones. The notion of services and service providers in region are to
+be introduced.
+
+
+.. |gslb.png| image:: /_static/images/gslb.png
+ :alt: GSLB architecture
+.. |gslb-add.png| image:: /_static/images/add-gslb.png
+ :alt: adding a gslb rule.
diff --git a/source/adminguide/networking/guest_ip_ranges.rst b/source/adminguide/networking/guest_ip_ranges.rst
new file mode 100644
index 0000000..d0edf78
--- /dev/null
+++ b/source/adminguide/networking/guest_ip_ranges.rst
@@ -0,0 +1,29 @@
+.. 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.
+
+
+Guest IP Ranges
+---------------
+
+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.
+
+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>`_.
\ No newline at end of file
diff --git a/source/adminguide/networking/guest_traffic.rst b/source/adminguide/networking/guest_traffic.rst
new file mode 100644
index 0000000..51374d1
--- /dev/null
+++ b/source/adminguide/networking/guest_traffic.rst
@@ -0,0 +1,50 @@
+.. 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.
+
+
+Guest Traffic
+-------------
+
+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.
+
+See a typical guest traffic setup given below:
+
+|guest-traffic-setup.png|
+
+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 router.
+Its eth2 interface is assigned a public IP address for public traffic.
+If multiple public VLAN is used, the router will have multiple public
+interfaces.
+
+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.
+
+Source NAT is automatically configured in the virtual router to forward
+outbound traffic for all guest VMs
+
+
+.. |guest-traffic-setup.png| image:: /_static/images/guest-traffic-setup.png
+ :alt: Depicts a guest traffic setup
diff --git a/source/adminguide/networking/inter_vlan_routing.rst b/source/adminguide/networking/inter_vlan_routing.rst
new file mode 100644
index 0000000..fd651a8
--- /dev/null
+++ b/source/adminguide/networking/inter_vlan_routing.rst
@@ -0,0 +1,96 @@
+.. 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.
+
+
+About Inter-VLAN Routing (nTier Apps)
+-------------------------------------
+
+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
+the VMs. In effect, you can segment VMs by means of VLANs into different
+networks that can host multi-tier applications, such as Web,
+Application, or Database. Such segmentation by means of VLANs logically
+separate application VMs for higher security and lower broadcasts, while
+remaining physically connected to the same device.
+
+This feature is supported on XenServer, KVM, and VMware hypervisors.
+
+The major advantages are:
+
+- 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.
+
+ .. note::
+ A VLAN allocated for an account cannot be shared between multiple accounts.
+
+- 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.
+
+- 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.
+
+- The administrator can create the following gateways to send to or
+ receive traffic from the VMs:
+
+ - **VPN Gateway**: For more information, see `"Creating a VPN gateway for the
+ VPC" <#creating-a-vpn-gateway-for-the-vpc>`_.
+
+ - **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.
+
+ - **Private Gateway**: For more information, see ":ref:`adding-priv-gw-vpc`".
+
+- Both administrators and users can create various possible
+ destinations-gateway combinations. However, only one gateway of each
+ type can be used in a deployment.
+
+ For example:
+
+ - **VLANs and Public Gateway**: For example, an application is
+ deployed in the cloud, and the Web application VMs communicate
+ with the Internet.
+
+ - **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.
+
+- 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.
+
+The following figure shows the possible deployment scenarios of a
+Inter-VLAN setup:
+
+|mutltier.png|
+
+To set up a multi-tier Inter-VLAN deployment, see ":ref:`configuring-vpc`".
+
+
+.. |mutltier.png| image:: /_static/images/multi-tier-app.png
+ :alt: a multi-tier setup.
diff --git a/source/adminguide/networking/ip_forwarding_and_firewalling.rst b/source/adminguide/networking/ip_forwarding_and_firewalling.rst
new file mode 100644
index 0000000..0999eb7
--- /dev/null
+++ b/source/adminguide/networking/ip_forwarding_and_firewalling.rst
@@ -0,0 +1,280 @@
+.. 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.
+
+
+IP Forwarding and Firewalling
+-----------------------------
+
+By default, all incoming traffic to the public IP address is rejected.
+All outgoing traffic from the guests is also blocked by default.
+
+To allow outgoing traffic, follow the procedure in :ref:`egress-fw-rules`.
+
+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.
+
+
+Firewall Rules
+~~~~~~~~~~~~~~
+
+By default, all incoming traffic to the public IP address is rejected by
+the firewall. To allow external traffic, you can open firewall ports by
+specifying firewall rules. You can optionally specify one or more CIDRs
+to filter the source IPs. This is useful when you want to allow only
+incoming requests from certain IP addresses.
+
+You cannot use firewall rules to open ports for an elastic IP address.
+When elastic IP is used, outside access is instead controlled through
+the use of security groups. See `"Adding a Security
+Group" <#adding-a-security-group>`_.
+
+In an advanced zone, you can also create egress firewall rules by using
+the virtual router. For more information, see ":ref:`egress-fw-rules`".
+
+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."
+
+To create a firewall rule:
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. Click the name of the network where you want to work with.
+
+#. Click View IP Addresses.
+
+#. Click the IP address you want to work with.
+
+#. Click the Configuration tab and fill in the following values.
+
+ - **Source CIDR**: (Optional) To accept only traffic from IP
+ addresses within a particular address block, enter a CIDR or a
+ comma-separated list of CIDRs. Example: 192.168.0.0/22. Leave
+ empty to allow all CIDRs.
+
+ - **Protocol**: The communication protocol in use on the opened
+ port(s).
+
+ - **Start Port and End Port**: The port(s) you want to open on the
+ firewall. If you are opening a single port, use the same number in
+ both fields
+
+ - **ICMP Type and ICMP Code**: Used only if Protocol is set to ICMP.
+ Provide the type and code required by the ICMP protocol to fill
+ out the ICMP header. Refer to ICMP documentation for more details
+ if you are not sure what to enter
+
+#. Click Add.
+
+
+.. _egress-fw-rules:
+
+Egress Firewall Rules in an Advanced Zone
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+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
+rules are removed the default policy, Block, is applied.
+
+
+Prerequisites and Guidelines
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Consider the following scenarios to apply egress firewall rules:
+
+- Egress firewall rules are supported on Juniper SRX and virtual
+ router.
+
+- The egress firewall rules are not supported on shared networks.
+
+- Allow the egress traffic from specified source CIDR. The Source CIDR
+ is part of guest network CIDR.
+
+- Allow the egress traffic with protocol TCP,UDP,ICMP, or ALL.
+
+- Allow the egress traffic with protocol and destination port range.
+ The port range is specified for TCP, UDP or for ICMP type and code.
+
+- 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.
+
+
+Configuring an Egress Firewall Rule
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In Select view, choose Guest networks, then click the Guest network
+ you want.
+
+#. 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:
+
+ |egress-firewall-rule.png|
+
+ - **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.
+
+ - **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.
+
+ - **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.
+
+ - **ICMP Type, ICMP Code**: (ICMP only) The type of message and
+ error code that are sent.
+
+#. Click Add.
+
+
+Configuring the Default Egress Policy
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+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.
+
+You have two options: Allow and Deny.
+
+Allow
+'''''
+
+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.
+
+Deny
+''''
+
+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.
+
+This feature is supported only on virtual router and Juniper SRX.
+
+#. Create a network offering with your desirable default egress policy:
+
+ #. Log in with admin privileges to the CloudStack UI.
+
+ #. In the left navigation bar, click Service Offerings.
+
+ #. In Select Offering, choose Network Offering.
+
+ #. Click Add Network Offering.
+
+ #. In the dialog, make necessary choices, including firewall
+ provider.
+
+ #. In the Default egress policy field, specify the behaviour.
+
+ #. Click OK.
+
+#. Create an isolated network by using this network offering.
+
+ Based on your selection, the network will have the egress public
+ traffic blocked or allowed.
+
+
+Port Forwarding
+~~~~~~~~~~~~~~~
+
+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.
+
+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
+
+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.
+
+To set up port forwarding:
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. 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.
+
+#. Add one or more VM instances to CloudStack.
+
+#. In the left navigation bar, click Network.
+
+#. Click the name of the guest network where the VMs are running.
+
+#. 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.
+
+#. Click the Configuration tab.
+
+#. In the Port Forwarding node of the diagram, click View All.
+
+#. Fill in the following:
+
+ - **Public Port**: The port to which public traffic will be
+ addressed on the IP address you acquired in the previous step.
+
+ - **Private Port**: The port on which the instance is listening for
+ forwarded public traffic.
+
+ - **Protocol**: The communication protocol in use between the two
+ ports
+
+#. Click Add.
+
+
+.. |egress-firewall-rule.png| image:: /_static/images/egress-firewall-rule.png
+ :alt: adding an egress firewall rule.
diff --git a/source/adminguide/networking/ip_load_balancing.rst b/source/adminguide/networking/ip_load_balancing.rst
new file mode 100644
index 0000000..6d2edd9
--- /dev/null
+++ b/source/adminguide/networking/ip_load_balancing.rst
@@ -0,0 +1,31 @@
+.. 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.
+
+
+IP Load Balancing
+-----------------
+
+The user may choose to associate the same public IP for multiple guests.
+CloudStack implements a TCP-level load balancer with the following
+policies.
+
+- Round-robin
+
+- Least connection
+
+- Source IP
+
+This is similar to port forwarding but the destination may be multiple
+IP addresses.
diff --git a/source/adminguide/networking/ip_reservation_in_guest_networks.rst b/source/adminguide/networking/ip_reservation_in_guest_networks.rst
new file mode 100644
index 0000000..021fd79
--- /dev/null
+++ b/source/adminguide/networking/ip_reservation_in_guest_networks.rst
@@ -0,0 +1,127 @@
+.. 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.
+
+
+IP Reservation in Isolated Guest Networks
+-----------------------------------------
+
+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.
+
+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 called
+Reserved IP Range. When IP reservation is configured, the administrator
+can add additional VMs or physical servers that are not part of
+CloudStack to the same network and assign them the Reserved IP
+addresses. CloudStack guest VMs cannot acquire IPs from the Reserved IP
+Range.
+
+
+IP Reservation Considerations
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Consider the following before you reserve an IP range for non-CloudStack
+machines:
+
+- IP Reservation is supported only in Isolated networks.
+
+- IP Reservation can be applied only when the network is in Implemented
+ state.
+
+- No IP Reservation is done by default.
+
+- Guest VM CIDR you specify must be a subset of the network CIDR.
+
+- Specify a valid Guest VM CIDR. IP Reservation is applied only if no
+ active IPs exist outside the Guest VM CIDR.
+
+ You cannot apply IP Reservation if any VM is alloted with an IP
+ address that is outside the Guest VM CIDR.
+
+- To reset an existing IP Reservation, apply IP reservation by
+ specifying the value of network CIDR in the CIDR field.
+
+ For example, the following table describes three scenarios of guest
+ network creation:
+
+ .. cssclass:: table-striped table-bordered table-hover
+
+ ===== ============= ============== ======================================== ========================================================
+ Case CIDR Network CIDR Reserved IP Range for Non-CloudStack VMs Description
+ ===== ============= ============== ======================================== ========================================================
+ 1 10.1.1.0/24 None None No IP Reservation.
+ 2 10.1.1.0/26 10.1.1.0/24 10.1.1.64 to 10.1.1.254 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.
+ 3 10.1.1.0/24 None None 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.
+ ===== ============= ============== ======================================== ========================================================
+
+
+Limitations
+~~~~~~~~~~~
+
+- The IP Reservation is not supported if active IPs that are found
+ outside the Guest VM CIDR.
+
+- 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.
+
+
+Best Practices
+~~~~~~~~~~~~~~
+
+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.
+
+
+Reserving an IP Range
+~~~~~~~~~~~~~~~~~~~~~
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. Click the name of the network you want to modify.
+
+#. In the Details tab, click Edit. |ip-edit-icon.png|
+
+ The CIDR field changes to editable one.
+
+#. In CIDR, specify the Guest VM CIDR.
+
+#. Click Apply.
+
+ Wait for the update to complete. The Network CIDR and the Reserved IP
+ Range are displayed on the Details page.
+
+
+.. |ip-edit-icon.png| image:: /_static/images/edit-icon.png
+ :alt: button to edit.
diff --git a/source/adminguide/networking/isolation_in_advanced_zone_with_vlan.rst b/source/adminguide/networking/isolation_in_advanced_zone_with_vlan.rst
new file mode 100644
index 0000000..61a4e57
--- /dev/null
+++ b/source/adminguide/networking/isolation_in_advanced_zone_with_vlan.rst
@@ -0,0 +1,202 @@
+.. 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.
+
+
+Isolation in Advanced Zone Using Private VLAN
+---------------------------------------------
+
+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 users'
+VMs.
+
+- Isolate VMs in a shared networks by using Private VLANs.
+
+- Supported on KVM, XenServer, and VMware hypervisors
+
+- PVLAN-enabled shared network can be a part of multiple networks of a
+ guest VM.
+
+
+About Private VLAN
+~~~~~~~~~~~~~~~~~~
+
+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
+VLAN that is being divided into smaller groups is called Primary, which
+implies that all VLAN pairs in a private VLAN share the same Primary
+VLAN. All the secondary VLANs exist only inside the Primary. Each
+Secondary VLAN has a specific VLAN ID associated to it, which
+differentiates one sub-domain from another.
+
+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:
+
+- **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.
+
+- **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.
+
+- **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 communicate among themselves, deploy them in community
+ ports.
+
+For further reading:
+
+- `Understanding Private
+ VLANs <http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_25_see/configuration/guide/swpvlan.html#wp1038379>`_
+
+- `Cisco Systems' Private VLANs: Scalable Security in a Multi-Client
+ Environment <http://tools.ietf.org/html/rfc5517>`_
+
+- `Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept
+ Overview (1010691) <http://kb.vmware.com>`_
+
+
+Prerequisites
+~~~~~~~~~~~~~
+
+- Use a PVLAN supported switch.
+
+ See `Private VLAN Catalyst Switch Support
+ Matrix <http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a0080094830.shtml>`_ for
+ more information.
+
+- 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.
+
+ 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.
+
+- Configure private VLAN on your physical switches out-of-band.
+
+- Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS).
+
+ .. note::
+ 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.
+
+
+Creating a PVLAN-Enabled Guest Network
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. Log in to the CloudStack UI as administrator.
+
+#. In the left navigation, choose Infrastructure.
+
+#. On Zones, click View More.
+
+#. Click the zone to which you want to add a guest network.
+
+#. Click the Physical Network tab.
+
+#. Click the physical network you want to work with.
+
+#. On the Guest node of the diagram, click Configure.
+
+#. Click the Network tab.
+
+#. Click Add guest network.
+
+ The Add guest network window is displayed.
+
+#. Specify the following:
+
+ - **Name**: The name of the network. This will be visible to the
+ user.
+
+ - **Description**: The short description of the network that can be
+ displayed to users.
+
+ - **VLAN ID**: The unique ID of the VLAN.
+
+ - **Secondary Isolated VLAN ID**: The unique ID of the Secondary
+ Isolated VLAN.
+
+ For the description on Secondary Isolated VLAN, see
+ `About Private VLAN" <#about-private-vlan>`_.
+
+ - **Scope**: The available scopes are Domain, Account, Project, and
+ All.
+
+ - **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.
+
+ - **Account**: The account for which the guest network is being
+ created for. You must specify the domain the account belongs
+ to.
+
+ - **Project**: The project for which the guest network is being
+ created for. You must specify the domain the project belongs
+ to.
+
+ - **All**: The guest network is available for all the domains,
+ account, projects within the selected zone.
+
+ - **Network Offering**: If the administrator has configured multiple
+ network offerings, select the one you want to use for this
+ network.
+
+ - **Gateway**: The gateway that the guests should use.
+
+ - **Netmask**: The netmask in use on the subnet the guests will use.
+
+ - **IP Range**: A range of IP addresses that are accessible from the
+ Internet and are assigned to the guest VMs.
+
+ - **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.
+
+#. Click OK to confirm.
diff --git a/source/adminguide/networking/multiple_guest_networks.rst b/source/adminguide/networking/multiple_guest_networks.rst
new file mode 100644
index 0000000..dd90f66
--- /dev/null
+++ b/source/adminguide/networking/multiple_guest_networks.rst
@@ -0,0 +1,207 @@
+.. 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.
+
+
+Using Multiple Guest Networks
+-----------------------------
+
+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.
+
+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.
+
+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.
+
+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.
+
+
+Adding an Additional Guest Network
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. Click Add guest network. Provide the following information:
+
+ - **Name**: The name of the network. This will be user-visible.
+
+ - **Display Text**: The description of the network. This will be
+ user-visible.
+
+ - **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.
+
+ - **Network offering**: If the administrator has configured multiple
+ network offerings, select the one you want to use for this
+ network.
+
+ - **Guest Gateway**: The gateway that the guests should use.
+
+ - **Guest Netmask**: The netmask in use on the subnet the guests
+ will use.
+
+#. Click Create.
+
+
+Reconfiguring Networks in VMs
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+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.
+
+This feature is supported on XenServer, VMware, and KVM hypervisors.
+
+
+Prerequisites
+^^^^^^^^^^^^^
+
+Ensure that vm-tools are running on guest VMs for adding or removing
+networks to work on VMware hypervisor.
+
+
+Adding a Network
+^^^^^^^^^^^^^^^^
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, click Instances.
+
+#. Choose the VM that you want to work with.
+
+#. Click the NICs tab.
+
+#. Click Add network to VM.
+
+ The Add network to VM dialog is displayed.
+
+#. In the drop-down list, select the network that you would like to add
+ this VM to.
+
+ A new NIC is added for this network. You can view the following
+ details in the NICs page:
+
+ - ID
+
+ - Network Name
+
+ - Type
+
+ - IP Address
+
+ - Gateway
+
+ - Netmask
+
+ - Is default
+
+ - CIDR (for IPv6)
+
+
+Removing a Network
+^^^^^^^^^^^^^^^^^^
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, click Instances.
+
+#. Choose the VM that you want to work with.
+
+#. Click the NICs tab.
+
+#. Locate the NIC you want to remove.
+
+#. Click Remove NIC button. |remove-nic.png|
+
+#. Click Yes to confirm.
+
+
+Selecting the Default Network
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, click Instances.
+
+#. Choose the VM that you want to work with.
+
+#. Click the NICs tab.
+
+#. Locate the NIC you want to work with.
+
+#. Click the Set default NIC button. |set-default-nic.png|.
+
+#. Click Yes to confirm.
+
+Changing the Network Offering on a Guest Network
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+A user or administrator can change the network offering that is
+associated with an existing guest network.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. If you are changing from a network offering that uses the CloudStack
+ virtual router to one that uses external devices as network service
+ providers, you must first stop all the VMs on the network.
+
+#. In the left navigation, choose Network.
+
+#. Click the name of the network you want to modify.
+
+#. In the Details tab, click Edit. |edit-icon.png|
+
+#. In Network Offering, choose the new network offering, then click
+ Apply.
+
+ A prompt is displayed asking whether you want to keep the existing
+ CIDR. This is to let you know that if you change the network
+ offering, the CIDR will be affected.
+
+ If you upgrade between virtual router as a provider and an external
+ network device as provider, acknowledge the change of CIDR to
+ continue, so choose Yes.
+
+#. Wait for the update to complete. Don't try to restart VMs until the
+ network change is complete.
+
+#. If you stopped any VMs, restart them.
+
+
+.. |remove-nic.png| image:: /_static/images/remove-nic.png
+ :alt: button to remove a NIC.
+.. |set-default-nic.png| image:: /_static/images/set-default-nic.png
+ :alt: button to set a NIC as default one.
+.. |edit-icon.png| image:: /_static/images/edit-icon.png
+ :alt: button to edit.
diff --git a/source/adminguide/networking/multiple_ip_ranges.rst b/source/adminguide/networking/multiple_ip_ranges.rst
new file mode 100644
index 0000000..2833c60
--- /dev/null
+++ b/source/adminguide/networking/multiple_ip_ranges.rst
@@ -0,0 +1,43 @@
+.. 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.
+
+
+About Multiple IP Ranges
+------------------------
+
+.. note:: The feature can only be implemented on IPv4 addresses.
+
+CloudStack provides you with the flexibility to add guest IP ranges from
+different subnets in Basic zones and security groups-enabled Advanced
+zones. For security groups-enabled Advanced zones, it implies multiple
+subnets can be added to the same VLAN. With the addition of this
+feature, you will be able to add IP address ranges from the same subnet
+or from a different one when IP address are exhausted. This would in
+turn allows you to employ higher number of subnets and thus reduce the
+address management overhead. To support this feature, the capability of
+``createVlanIpRange`` API is extended to add IP ranges also from a
+different subnet.
+
+Ensure that you manually configure the gateway of the new subnet before
+adding the IP range. Note that CloudStack supports only one gateway for
+a subnet; overlapping subnets are not currently supported.
+
+Use the ``deleteVlanRange`` API to delete IP ranges. This operation
+fails if an IP from the remove range is in use. If the remove range
+contains the IP address on which the DHCP server is running, CloudStack
+acquires a new IP from the same subnet. If no IP is available in the
+subnet, the remove operation fails.
+
+This feature is supported on KVM, xenServer, and VMware hypervisors.
\ No newline at end of file
diff --git a/source/adminguide/networking/multiple_ips_on_single_nic.rst b/source/adminguide/networking/multiple_ips_on_single_nic.rst
new file mode 100644
index 0000000..b67109a
--- /dev/null
+++ b/source/adminguide/networking/multiple_ips_on_single_nic.rst
@@ -0,0 +1,98 @@
+.. 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 Multiple IP Addresses on a Single NIC
+-------------------------------------------------
+
+CloudStack provides you the ability to associate multiple private IP
+addresses per guest VM NIC. In addition to the primary IP, you can
+assign additional IPs to the guest VM NIC. This feature is supported on
+all the network configurations: Basic, Advanced, and VPC. Security
+Groups, Static NAT and Port forwarding services are supported on these
+additional IPs.
+
+As always, you can specify an IP from the guest subnet; if not
+specified, an IP is automatically picked up from the guest VM subnet.
+You can view the IPs associated with for each guest VM NICs on the UI.
+You can apply NAT on these additional guest IPs by using network
+configuration option in the CloudStack UI. You must specify the NIC to
+which the IP should be associated.
+
+This feature is supported on XenServer, KVM, and VMware hypervisors.
+Note that Basic zone security groups are not supported on VMware.
+
+
+Use Cases
+~~~~~~~~~
+
+Some of the use cases are described below:
+
+- Network devices, such as firewalls and load balancers, generally work
+ best when they have access to multiple IP addresses on the network
+ interface.
+
+- Moving private IP addresses between interfaces or instances.
+ Applications that are bound to specific IP addresses can be moved
+ between instances.
+
+- Hosting multiple SSL Websites on a single instance. You can install
+ multiple SSL certificates on a single instance, each associated with
+ a distinct IP address.
+
+
+Guidelines
+~~~~~~~~~~
+
+To prevent IP conflict, configure different subnets when multiple
+networks are connected to the same VM.
+
+
+Assigning Additional IPs to a VM
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. Log in to the CloudStack UI.
+
+#. In the left navigation bar, click Instances.
+
+#. Click the name of the instance you want to work with.
+
+#. In the Details tab, click NICs.
+
+#. Click View Secondary IPs.
+
+#. Click Acquire New Secondary IP, and click Yes in the confirmation
+ dialog.
+
+ You need to configure the IP on the guest VM NIC manually. CloudStack
+ will not automatically configure the acquired IP address on the VM.
+ Ensure that the IP address configuration persist on VM reboot.
+
+ Within a few moments, the new IP address should appear with the state
+ Allocated. You can now use the IP address in Port Forwarding or
+ StaticNAT rules.
+
+
+Port Forwarding and StaticNAT Services Changes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Because multiple IPs can be associated per NIC, you are allowed to
+select a desired IP for the Port Forwarding and StaticNAT services. The
+default is the primary IP. To enable this functionality, an extra
+optional parameter 'vmguestip' is added to the Port forwarding and
+StaticNAT APIs (enableStaticNat, createIpForwardingRule) to indicate on
+what IP address NAT need to be configured. If vmguestip is passed, NAT
+is configured on the specified private IP of the VM. if not passed, NAT
+is configured on the primary IP of the VM.
diff --git a/source/adminguide/networking/multiple_subnets_in_shared_network.rst b/source/adminguide/networking/multiple_subnets_in_shared_network.rst
new file mode 100644
index 0000000..53b30bb
--- /dev/null
+++ b/source/adminguide/networking/multiple_subnets_in_shared_network.rst
@@ -0,0 +1,99 @@
+.. 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.
+
+
+Multiple Subnets in Shared Network
+----------------------------------
+
+CloudStack provides you with the flexibility to add guest IP ranges from
+different subnets in Basic zones and security groups-enabled Advanced
+zones. For security groups-enabled Advanced zones, it implies multiple
+subnets can be added to the same VLAN. With the addition of this
+feature, you will be able to add IP address ranges from the same subnet
+or from a different one when IP address are exhausted. This would in
+turn allows you to employ higher number of subnets and thus reduce the
+address management overhead. You can delete the IP ranges you have
+added.
+
+
+Prerequisites and Guidelines
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- This feature can only be implemented:
+
+ - on IPv4 addresses
+
+ - if virtual router is the DHCP provider
+
+ - on KVM, xenServer, and VMware hypervisors
+
+- Manually configure the gateway of the new subnet before adding the IP
+ range.
+
+- CloudStack supports only one gateway for a subnet; overlapping
+ subnets are not currently supported
+
+
+Adding Multiple Subnets to a Shared Network
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. 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 Networks.
+
+#. Select the networks you want to work with.
+
+#. Click View IP Ranges.
+
+#. Click Add IP Range.
+
+ The Add IP Range dialog is displayed, as follows:
+
+ |add-ip-range.png|
+
+#. Specify the following:
+
+ All the fields are mandatory.
+
+ - **Gateway**: The gateway for the tier you create. Ensure that the
+ gateway is within the Super CIDR range that you specified while
+ creating the VPC, and is not overlapped with the CIDR of any
+ existing tier within the VPC.
+
+ - **Netmask**: The netmask for the tier you create.
+
+ For example, if the VPC CIDR is 10.0.0.0/16 and the network tier
+ CIDR is 10.0.1.0/24, the gateway of the tier is 10.0.1.1, and the
+ netmask of the tier is 255.255.255.0.
+
+ - **Start IP/ End IP**: A range of IP addresses that are accessible
+ from the Internet and will be allocated to guest VMs. Enter the
+ first and last IP addresses that define a range that CloudStack
+ can assign to guest VMs .
+
+#. Click OK.
+
+
+.. |add-ip-range.png| image:: /_static/images/add-ip-range.png
+ :alt: adding an IP range to a network.
diff --git a/source/adminguide/networking/networking_in_pod.rst b/source/adminguide/networking/networking_in_pod.rst
new file mode 100644
index 0000000..b7305be
--- /dev/null
+++ b/source/adminguide/networking/networking_in_pod.rst
@@ -0,0 +1,45 @@
+.. 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.
+
+
+Networking in a Pod
+-------------------
+
+The figure below illustrates network setup within a single pod. The
+hosts are connected to a pod-level switch. At a minimum, the hosts
+should have one physical uplink to each switch. Bonded NICs are
+supported as well. The pod-level switch is a pair of redundant gigabit
+switches with 10 G uplinks.
+
+|networksinglepod.png|
+
+Servers are connected as follows:
+
+- Storage devices are connected to only the network that carries
+ management traffic.
+
+- Hosts are connected to networks for both management traffic and
+ public traffic.
+
+- Hosts are also connected to one or more networks carrying guest
+ traffic.
+
+We recommend the use of multiple physical Ethernet cards to implement
+each network interface as well as redundant switch fabric in order to
+maximize throughput and improve reliability.
+
+
+.. |networksinglepod.png| image:: /_static/images/network-singlepod.png
+ :alt: diagram showing logical view of network in a pod.
\ No newline at end of file
diff --git a/source/adminguide/networking/networking_in_zone.rst b/source/adminguide/networking/networking_in_zone.rst
new file mode 100644
index 0000000..ae6231d
--- /dev/null
+++ b/source/adminguide/networking/networking_in_zone.rst
@@ -0,0 +1,34 @@
+.. 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.
+
+
+Networking in a Zone
+--------------------
+
+The following figure illustrates the network setup within a single zone.
+
+|networksetupzone.png|
+
+A firewall for management traffic operates in the NAT mode. The network
+typically is assigned IP addresses in the 192.168.0.0/16 Class B private
+address space. Each pod is assigned IP addresses in the 192.168.\*.0/24
+Class C private address space.
+
+Each zone has its own set of public IP addresses. Public IP addresses
+from different zones do not overlap.
+
+
+.. |networksetupzone.png| image:: /_static/images/network-setup-zone.png
+ :alt: Depicts network setup in a single zone.
\ No newline at end of file
diff --git a/source/adminguide/networking/palo_alto_config.rst b/source/adminguide/networking/palo_alto_config.rst
new file mode 100644
index 0000000..456b3c2
--- /dev/null
+++ b/source/adminguide/networking/palo_alto_config.rst
@@ -0,0 +1,475 @@
+.. 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.
+
+
+Setup a Palo Alto Networks Firewall
+-----------------------------------
+
+
+Functionality Provided
+~~~~~~~~~~~~~~~~~~~~~~
+
+This implementation enables the orchestration of a Palo Alto Networks Firewall
+from within CloudStack UI and API.
+
+**The following features are supported**:
+
+- List/Add/Delete Palo Alto Networks service provider
+
+- List/Add/Delete Palo Alto Networks network service offering
+
+- List/Add/Delete Palo Alto Networks network using the above service offering
+
+- Add an instance to a Palo Alto Networks network
+
+- Source NAT management on network create and delete
+
+- List/Add/Delete Ingress Firewall rule
+
+- List/Add/Delete Egress Firewall rule (both 'Allow' and 'Deny' default rules
+ supported)
+
+- List/Add/Delete Port Forwarding rule
+
+- List/Add/Delete Static NAT rule
+
+- Apply a Threat Profile to all firewall rules (more details in the
+ Additional Features section)
+
+- Apply a Log Forwarding profile to all firewall rules (more details in the
+ Additional Features section)
+
+
+
+Initial Palo Alto Networks Firewall Configuration
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Anatomy of the Palo Alto Networks Firewall
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+- In **'Network > Interfaces'** there is a list of physical interfaces as
+ well as aggregated physical interfaces which are used for managing traffic
+ in and out of the Palo Alto Networks Firewall device.
+
+- In **'Network > Zones'** there is a list of the different configuration
+ zones. This implementation will use two zones; a public (defaults to
+ 'untrust') and private (defaults to 'trust') zone.
+
+- In **'Network > Virtual Routers'** there is a list of VRs which handle
+ traffic routing for the Palo Alto Firewall. We only use a single Virtual
+ Router on the firewall and it is used to handle all the routing to the next
+ network hop.
+
+- In **'Objects > Security Profile Groups'** there is a list of profiles
+ which can be applied to firewall rules. These profiles are used to better
+ understand the types of traffic that is flowing through your network.
+ Configured when you add the firewall provider to CloudStack.
+
+- In **'Objects > Log Forwarding'** there is a list of profiles which can be
+ applied to firewall rules. These profiles are used to better track the
+ logs generated by the firewall. Configured when you add the firewall
+ provider to CloudStack.
+
+- In **'Policies > Security'** there is a list of firewall rules that are
+ currently configured. You will not need to modify this section because it
+ will be completely automated by CloudStack, but you can review the firewall
+ rules which have been created here.
+
+- In **'Policies > NAT'** there is a list of the different NAT rules. You
+ will not need to modify this section because it will be completely
+ automated by CloudStack, but you can review the different NAT rules that
+ have been created here. Source NAT, Static NAT and Destination NAT (Port
+ Forwarding) rules will show up in this list.
+
+
+
+Configure the Public / Private Zones on the firewall
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+No manual configuration is required to setup these zones because CloudStack
+will configure them automatically when you add the Palo Alto Networks firewall
+device to CloudStack as a service provider. This implementation depends on
+two zones, one for the public side and one for the private side of the
+firewall.
+
+- The public zone (defaults to 'untrust') will contain all of the public
+ interfaces and public IPs.
+
+- The private zone (defaults to 'trust') will contain all of the private
+ interfaces and guest network gateways.
+
+The NAT and firewall rules will be configured between these zones.
+
+
+
+Configure the Public / Private Interfaces on the firewall
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+This implementation supports standard physical interfaces as well as grouped
+physical interfaces called aggregated interfaces. Both standard interfaces
+and aggregated interfaces are treated the same, so they can be used
+interchangeably. For this document, we will assume that we are using
+'ethernet1/1' as the public interface and 'ethernet1/2' as the private
+interface. If aggregated interfaces where used, you would use something
+like 'ae1' and 'ae2' as the interfaces.
+
+This implementation requires that the 'Interface Type' be set to 'Layer3' for
+both the public and private interfaces. If you want to be able to use the
+'Untagged' VLAN tag for public traffic in CloudStack, you will need to enable
+support for it in the public 'ethernet1/1' interface (details below).
+
+**Steps to configure the Public Interface**:
+
+#. Log into Palo Alto Networks Firewall
+
+#. Navigate to 'Network > Interfaces'
+
+#. Click on 'ethernet1/1' (for aggregated ethernet, it will probably be called
+ 'ae1')
+
+#. Select 'Layer3' from the 'Interface Type' list
+
+#. Click 'Advanced'
+
+#. Check the 'Untagged Subinterface' check-box
+
+#. Click 'OK'
+
+**Steps to configure the Private Interface**:
+
+#. Click on 'ethernet1/2' (for aggregated ethernet, it will probably be called
+ 'ae2')
+
+#. Select 'Layer3' from the 'Interface Type' list
+
+#. Click 'OK'
+
+
+
+Configure a Virtual Router on the firewall
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The Virtual Router on the Palo Alto Networks Firewall is not to be confused
+with the Virtual Routers that CloudStack provisions. For this implementation,
+the Virtual Router on the Palo Alto Networks Firewall will ONLY handle the
+upstream routing from the Firewall to the next hop.
+
+**Steps to configure the Virtual Router**:
+
+#. Log into Palo Alto Networks Firewall
+
+#. Navigate to 'Network > Virtual Routers'
+
+#. Select the 'default' Virtual Router or Add a new Virtual Router if there
+ are none in the list
+
+ - If you added a new Virtual Router, you will need to give it a 'Name'
+
+#. Navigate to 'Static Routes > IPv4'
+
+#. 'Add' a new static route
+
+ - **Name**: next_hop (you can name it anything you want)
+
+ - **Destination**: 0.0.0.0/0 (send all traffic to this route)
+
+ - **Interface**: ethernet1/1 (or whatever you set your public interface
+ as)
+
+ - **Next Hop**: (specify the gateway IP for the next hop in your network)
+
+ - Click 'OK'
+
+#. Click 'OK'
+
+
+
+Configure the default Public Subinterface
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The current implementation of the Palo Alto Networks firewall integration uses
+CIDRs in the form of 'w.x.y.z/32' for the public IP addresses that CloudStack
+provisions. Because no broadcast or gateway IPs are in this single IP range,
+there is no way for the firewall to route the traffic for these IPs. To route
+the traffic for these IPs, we create a single subinterface on the public
+interface with an IP and a CIDR which encapsulates the CloudStack public IP
+range. This IP will need to be inside the subnet defined by the CloudStack
+public range netmask, but outside the CloudStack public IP range. The CIDR
+should reflect the same subnet defined by the CloudStack public range netmask.
+The name of the subinterface is determined by the VLAN configured for the
+public range in CloudStack.
+
+To clarify this concept, we will use the following example.
+
+**Example CloudStack Public Range Configuration**:
+
+- **Gateway**: 172.30.0.1
+
+- **Netmask**: 255.255.255.0
+
+- **IP Range**: 172.30.0.100 - 172.30.0.199
+
+- **VLAN**: Untagged
+
+**Configure the Public Subinterface**:
+
+#. Log into Palo Alto Networks Firewall
+
+#. Navigate to 'Network > Interfaces'
+
+#. Select the 'ethernet1/1' line (not clicking on the name)
+
+#. Click 'Add Subinterface' at the bottom of the window
+
+#. Enter 'Interface Name': 'ethernet1/1' . '9999'
+
+ - 9999 is used if the CloudStack public range VLAN is 'Untagged'
+
+ - If the CloudStack public range VLAN is tagged (eg: 333), then the name
+ will reflect that tag
+
+#. The 'Tag' is the VLAN tag that the traffic is sent to the next hop with, so
+ set it accordingly. If you are passing 'Untagged' traffic from CloudStack
+ to your next hop, leave it blank. If you want to pass tagged traffic from
+ CloudStack, specify the tag.
+
+#. Select 'default' from the 'Config > Virtual Router' drop-down (assuming
+ that is what your virtual router is called)
+
+#. Click the 'IPv4' tab
+
+#. Select 'Static' from the 'Type' radio options
+
+#. Click 'Add' in the 'IP' section
+
+#. Enter '172.30.0.254/24' in the new line
+
+ - The IP can be any IP outside the CloudStack public IP range, but inside
+ the CloudStack public range netmask (it can NOT be the gateway IP)
+
+ - The subnet defined by the CIDR should match the CloudStack public range
+ netmask
+
+#. Click 'OK'
+
+
+Commit configuration on the Palo Alto Networks Firewall
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+In order for all the changes we just made to take effect, we need to commit
+the changes.
+
+#. Click the 'Commit' link in the top right corner of the window
+
+#. Click 'OK' in the commit window overlay
+
+#. Click 'Close' to the resulting commit status window after the commit
+ finishes
+
+
+
+Setup the Palo Alto Networks Firewall in CloudStack
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Add the Palo Alto Networks Firewall as a Service Provider
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. Navigate to 'Infrastructure > Zones > ZONE_NAME > Physical Network >
+ NETWORK_NAME (guest) > Configure; Network Service Providers'
+
+#. Click on 'Palo Alto' in the list
+
+#. Click 'View Devices'
+
+#. Click 'Add Palo Alto Device'
+
+#. Enter your configuration in the overlay. This example will reflect the
+ details previously used in this guide.
+
+ - **IP Address**: (the IP of the Palo Alto Networks Firewall)
+
+ - **Username**: (the admin username for the firewall)
+
+ - **Password**: (the admin password for the firewall)
+
+ - **Type**: Palo Alto Firewall
+
+ - **Public Interface**: ethernet1/1 (use what you setup earlier as the
+ public interface if it is different from my examples)
+
+ - **Private Interface**: ethernet1/2 (use what you setup earlier as the
+ private interface if it is different from my examples)
+
+ - **Number of Retries**: 2 (the default is fine)
+
+ - **Timeout**: 300 (the default is fine)
+
+ - **Public Network**: untrust (this is the public zone on the firewall and
+ did not need to be configured)
+
+ - **Private Network**: trust (this is the private zone on the firewall and
+ did not need to be configured)
+
+ - **Virtual Router**: default (this is the name of the Virtual Router we
+ setup on the firewall)
+
+ - **Palo Alto Threat Profile**: (not required. name of the 'Security
+ Profile Groups' to apply. more details in the 'Additional Features'
+ section)
+
+ - **Palo Alto Log Profile**: (not required. name of the 'Log Forwarding'
+ profile to apply. more details in the 'Additional Features' section)
+
+ - **Capacity**: (not required)
+
+ - **Dedicated**: (not required)
+
+#. Click 'OK'
+
+#. Click on 'Palo Alto' in the breadcrumbs to go back one screen.
+
+#. Click on 'Enable Provider' |EnableDisableFeature.png|
+
+
+Add a Network Service Offering to use the new Provider
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+There are 6 'Supported Services' that need to be configured in the network
+service offering for this functionality. They are DHCP, DNS, Firewall, Source
+NAT, Static NAT and Port Forwarding. For the other settings, there are
+probably additional configurations which will work, but I will just document a
+common case.
+
+#. Navigate to 'Service Offerings'
+
+#. In the drop-down at the top, select 'Network Offerings'
+
+#. Click 'Add Network Offering'
+
+ - **Name**: (name it whatever you want)
+
+ - **Description**: (again, can be whatever you want)
+
+ - **Guest Type**: Isolated
+
+ - **Supported Services**:
+
+ - **DHCP**: Provided by 'VirtualRouter'
+
+ - **DNS**: Provided by 'VirtualRouter'
+
+ - **Firewall**: Provided by 'PaloAlto'
+
+ - **Source NAT**: Provided by 'PaloAlto'
+
+ - **Static NAT**: Provided by 'PaloAlto'
+
+ - **Port Forwarding**: Provided by 'PaloAlto'
+
+ - **System Offering for Router**: System Offering For Software Router
+
+ - **Supported Source NAT Type**: Per account (this is the only supported
+ option)
+
+ - **Default egress policy**: (both 'Allow' and 'Deny' are supported)
+
+#. Click 'OK'
+
+#. Click on the newly created service offering
+
+#. Click 'Enable network offering' |EnableDisableFeature.png|
+
+When adding networks in CloudStack, select this network offering to use the
+Palo Alto Networks firewall.
+
+
+Additional Features
+~~~~~~~~~~~~~~~~~~~
+
+In addition to the standard functionality exposed by CloudStack, we have added
+a couple additional features to this implementation. We did not add any new
+screens to CloudStack, but we have added a couple fields to the 'Add Palo Alto
+Service Provider' screen which will add functionality globally for the device.
+
+
+Palo Alto Networks Threat Profile
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+This feature allows you to specify a 'Security Profile Group' to be applied to
+all of the firewall rules which are created on the Palo Alto Networks firewall
+device.
+
+To create a 'Security Profile Group' on the Palo Alto Networks firewall, do
+the following:
+
+#. Log into the Palo Alto Networks firewall
+
+#. Navigate to 'Objects > Security Profile Groups'
+
+#. Click 'Add' at the bottom of the page to add a new group
+
+#. Give the group a Name and specify the profiles you would like to include in
+ the group
+
+#. Click 'OK'
+
+#. Click the 'Commit' link in the top right of the screen and follow the on
+ screen instructions
+
+Once you have created a profile, you can reference it by Name in the 'Palo
+Alto Threat Profile' field in the 'Add the Palo Alto Networks Firewall as a
+Service Provider' step.
+
+
+Palo Alto Networks Log Forwarding Profile
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+This feature allows you to specify a 'Log Forwarding' profile to better manage
+where the firewall logs are sent to. This is helpful for keeping track of
+issues that can arise on the firewall.
+
+To create a 'Log Forwarding' profile on the Palo Alto Networks Firewall, do
+the following:
+
+#. Log into the Palo Alto Networks firewall
+
+#. Navigate to 'Objects > Log Forwarding'
+
+#. Click 'Add' at the bottom of the page to add a new profile
+
+#. Give the profile a Name and specify the details you want for the traffic
+ and threat settings
+
+#. Click 'OK'
+
+#. Click the 'Commit' link in the top right of the screen and follow the on
+ screen instructions
+
+Once you have created a profile, you can reference it by Name in the 'Palo
+Alto Log Profile' field in the 'Add the Palo Alto Networks Firewall as a
+Service Provider' step.
+
+
+
+Limitations
+~~~~~~~~~~~
+
+- The implementation currently only supports a single public IP range in
+ CloudStack
+
+- Usage tracking is not yet implemented
+
+.. |EnableDisableFeature.png| image:: /_static/images/enable-disable-autoscale.png
+ :alt: button to enable or disable feature.
\ No newline at end of file
diff --git a/source/adminguide/networking/persistent_networks.rst b/source/adminguide/networking/persistent_networks.rst
new file mode 100644
index 0000000..9aa15d5
--- /dev/null
+++ b/source/adminguide/networking/persistent_networks.rst
@@ -0,0 +1,94 @@
+.. 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.
+
+
+Persistent Networks
+-------------------
+
+The network that you can provision without having to deploy any VMs on
+it is called a persistent network. A persistent network can be part of a
+VPC or a non-VPC environment.
+
+When you create other types of network, a network is only a database
+entry until the first VM is created on that network. When the first VM
+is created, a VLAN ID is assigned and the network is provisioned. Also,
+when the last VM is destroyed, the VLAN ID is released and the network
+is no longer available. With the addition of persistent network, you
+will have the ability to create a network in CloudStack in which
+physical devices can be deployed without having to run any VMs.
+Additionally, you can deploy physical devices on that network.
+
+One of the advantages of having a persistent network is that you can
+create a VPC with a tier consisting of only physical devices. For
+example, you might create a VPC for a three-tier application, deploy VMs
+for Web and Application tier, and use physical machines for the Database
+tier. Another use case is that if you are providing services by using
+physical hardware, you can define the network as persistent and
+therefore even if all its VMs are destroyed the services will not be
+discontinued.
+
+
+Persistent Network Considerations
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- Persistent network is designed for isolated networks.
+
+- All default network offerings are non-persistent.
+
+- A network offering cannot be editable because changing it affects the
+ behavior of the existing networks that were created using this
+ network offering.
+
+- When you create a guest network, the network offering that you select
+ defines the network persistence. This in turn depends on whether
+ persistent network is enabled in the selected network offering.
+
+- An existing network can be made persistent by changing its network
+ offering to an offering that has the Persistent option enabled. While
+ setting this property, even if the network has no running VMs, the
+ network is provisioned.
+
+- An existing network can be made non-persistent by changing its
+ network offering to an offering that has the Persistent option
+ disabled. If the network has no running VMs, during the next network
+ garbage collection run the network is shut down.
+
+- When the last VM on a network is destroyed, the network garbage
+ collector checks if the network offering associated with the network
+ is persistent, and shuts down the network only if it is
+ non-persistent.
+
+
+Creating a Persistent Guest Network
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To create a persistent network, perform the following:
+
+#. Create a network offering with the Persistent option enabled.
+
+ See `"Creating a New Network Offering"
+ <networking.html#creating-a-new-network-offering>`_.
+
+#. Select Network from the left navigation pane.
+
+#. Select the guest network that you want to offer this network service
+ to.
+
+#. Click the Edit button.
+
+#. From the Network Offering drop-down, select the persistent network
+ offering you have just created.
+
+#. Click OK.
diff --git a/source/adminguide/networking/portable_ips.rst b/source/adminguide/networking/portable_ips.rst
new file mode 100644
index 0000000..55b3cd2
--- /dev/null
+++ b/source/adminguide/networking/portable_ips.rst
@@ -0,0 +1,131 @@
+.. 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.
+
+
+Portable IPs
+------------
+
+About Portable IP
+~~~~~~~~~~~~~~~~~
+
+Portable IPs in CloudStack are region-level pool of IPs, which are
+elastic in nature, that can be transferred across geographically
+separated zones. As an administrator, you can provision a pool of
+portable public IPs at region level and are available for user
+consumption. The users can acquire portable IPs if admin has provisioned
+portable IPs at the region level they are part of. These IPs can be use
+for any service within an advanced zone. You can also use portable IPs
+for EIP services in basic zones.
+
+The salient features of Portable IP are as follows:
+
+- IP is statically allocated
+
+- IP need not be associated with a network
+
+- IP association is transferable across networks
+
+- IP is transferable across both Basic and Advanced zones
+
+- IP is transferable across VPC, non-VPC isolated and shared networks
+
+- Portable IP transfer is available only for static NAT.
+
+
+Guidelines
+^^^^^^^^^^
+
+Before transferring to another network, ensure that no network rules
+(Firewall, Static NAT, Port Forwarding, and so on) exist on that
+portable IP.
+
+
+Configuring Portable IPs
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, click Regions.
+
+#. Choose the Regions that you want to work with.
+
+#. Click View Portable IP.
+
+#. Click Portable IP Range.
+
+ The Add Portable IP Range window is displayed.
+
+#. Specify the following:
+
+ - **Start IP/ End IP**: A range of IP addresses that are accessible
+ from the Internet and will be allocated to guest VMs. Enter the
+ first and last IP addresses that define a range that CloudStack
+ can assign to guest VMs.
+
+ - **Gateway**: The gateway in use for the Portable IP addresses you
+ are configuring.
+
+ - **Netmask**: The netmask associated with the Portable IP range.
+
+ - **VLAN**: The VLAN that will be used for public traffic.
+
+#. Click OK.
+
+
+Acquiring a Portable IP
+~~~~~~~~~~~~~~~~~~~~~~~
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. Click the name of the network where you want to work with.
+
+#. Click View IP Addresses.
+
+#. Click Acquire New IP.
+
+ The Acquire New IP window is displayed.
+
+#. Specify whether you want cross-zone IP or not.
+
+#. Click Yes in the confirmation dialog.
+
+ 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.
+
+
+Transferring Portable IP
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+An IP can be transferred from one network to another only if Static NAT
+is enabled. However, when a portable IP is associated with a network,
+you can use it for any service in the network.
+
+To transfer a portable IP across the networks, execute the following
+API:
+
+.. code:: bash
+
+ http://localhost:8096/client/api?command=enableStaticNat&response=json&ipaddressid=a4bc37b2-4b4e-461d-9a62-b66414618e36&virtualmachineid=a242c476-ef37-441e-9c7b-b303e2a9cb4f&networkid=6e7cd8d1-d1ba-4c35-bdaf-333354cbd49810
+
+Replace the UUID with appropriate UUID. For example, if you want to
+transfer a portable IP to network X and VM Y in a network, execute the
+following:
+
+.. code:: bash
+
+ http://localhost:8096/client/api?command=enableStaticNat&response=json&ipaddressid=a4bc37b2-4b4e-461d-9a62-b66414618e36&virtualmachineid=Y&networkid=X
diff --git a/source/adminguide/networking/public_ips_and_vlans_for_accounts.rst b/source/adminguide/networking/public_ips_and_vlans_for_accounts.rst
new file mode 100644
index 0000000..42a4640
--- /dev/null
+++ b/source/adminguide/networking/public_ips_and_vlans_for_accounts.rst
@@ -0,0 +1,154 @@
+.. 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.
+
+
+Reserving Public IP Addresses and VLANs for Accounts
+----------------------------------------------------
+
+CloudStack provides you the ability to reserve a set of public IP
+addresses and VLANs exclusively for an account. During zone creation,
+you can continue defining a set of VLANs and multiple public IP ranges.
+This feature extends the functionality to enable you to dedicate a fixed
+set of VLANs and guest IP addresses for a tenant.
+
+Note that if an account has consumed all the VLANs and IPs dedicated to
+it, the account can acquire two more resources from the system.
+CloudStack provides the root admin with two configuration parameter to
+modify this default behavior: use.system.public.ips and
+use.system.guest.vlans. These global parameters enable the root admin to
+disallow an account from acquiring public IPs and guest VLANs from the
+system, if the account has dedicated resources and these dedicated
+resources have all been consumed. Both these configurations are
+configurable at the account level.
+
+This feature provides you the following capabilities:
+
+- Reserve a VLAN range and public IP address range from an Advanced
+ zone and assign it to an account
+
+- Disassociate a VLAN and public IP address range from an account
+
+- View the number of public IP addresses allocated to an account
+
+- Check whether the required range is available and is conforms to
+ account limits.
+
+ The maximum IPs per account limit cannot be superseded.
+
+
+Dedicating IP Address Ranges to an Account
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. Log in to the CloudStack UI as administrator.
+
+#. In the left navigation bar, click Infrastructure.
+
+#. In Zones, click View All.
+
+#. Choose the zone you want to work with.
+
+#. Click the Physical Network tab.
+
+#. In the Public node of the diagram, click Configure.
+
+#. Click the IP Ranges tab.
+
+ You can either assign an existing IP range to an account, or create a
+ new IP range and assign to an account.
+
+#. To assign an existing IP range to an account, perform the following:
+
+ #. Locate the IP range you want to work with.
+
+ #. Click Add Account |addAccount-icon.png| button.
+
+ The Add Account dialog is displayed.
+
+ #. Specify the following:
+
+ - **Account**: The account to which you want to assign the IP
+ address range.
+
+ - **Domain**: The domain associated with the account.
+
+ To create a new IP range and assign an account, perform the
+ following:
+
+ #. Specify the following:
+
+ - **Gateway**
+
+ - **Netmask**
+
+ - **VLAN**
+
+ - **Start IP**
+
+ - **End IP**
+
+ - **Account**: Perform the following:
+
+ #. Click Account.
+
+ The Add Account page is displayed.
+
+ #. Specify the following:
+
+ - **Account**: The account to which you want to
+ assign an IP address range.
+
+ - **Domain**: The domain associated with the
+ account.
+
+ #. Click OK.
+
+ #. Click Add.
+
+
+Dedicating VLAN Ranges to an Account
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. After the CloudStack Management Server is installed, log in to the
+ CloudStack UI as administrator.
+
+#. In the left navigation bar, click Infrastructure.
+
+#. In Zones, click View All.
+
+#. Choose the zone you want to work with.
+
+#. Click the Physical Network tab.
+
+#. In the Guest node of the diagram, click Configure.
+
+#. Select the Dedicated VLAN Ranges tab.
+
+#. Click Dedicate VLAN Range.
+
+ The Dedicate VLAN Range dialog is displayed.
+
+#. Specify the following:
+
+ - **VLAN Range**: The VLAN range that you want to assign to an
+ account.
+
+ - **Account**: The account to which you want to assign the
+ selected VLAN range.
+
+ - **Domain**: The domain associated with the account.
+
+
+.. |addAccount-icon.png| image:: /_static/images/addAccount-icon.png
+ :alt: button to assign an IP range to an account.
diff --git a/source/adminguide/networking/releasing_an_ip_address.rst b/source/adminguide/networking/releasing_an_ip_address.rst
new file mode 100644
index 0000000..a662d0d
--- /dev/null
+++ b/source/adminguide/networking/releasing_an_ip_address.rst
@@ -0,0 +1,38 @@
+.. 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.
+
+
+Releasing an IP Address
+-----------------------
+
+When the last rule for an IP address is removed, you can release that IP
+address. The IP address still belongs to the VPC; however, it can be
+picked up for any guest network again.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. Click the name of the network where you want to work with.
+
+#. Click View IP Addresses.
+
+#. Click the IP address you want to release.
+
+#. Click the Release IP button. |ReleaseIPButton.png|
+
+
+.. |ReleaseIPButton.png| image:: /_static/images/release-ip-icon.png
+ :alt: button to release an IP
diff --git a/source/adminguide/networking/remote_access_vpn.rst b/source/adminguide/networking/remote_access_vpn.rst
new file mode 100644
index 0000000..85e43ed
--- /dev/null
+++ b/source/adminguide/networking/remote_access_vpn.rst
@@ -0,0 +1,157 @@
+.. 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.
+
+
+.. _remote-access-vpn:
+
+Remote Access VPN
+-----------------
+
+CloudStack account owners can create virtual private networks (VPN) to
+access their virtual machines. If the guest network is instantiated from
+a network offering that offers the Remote Access VPN service, the
+virtual router (based on the System VM) is used to provide the service.
+CloudStack provides a L2TP-over-IPsec-based remote access VPN service to
+guest virtual networks. Since each network gets its own virtual router,
+VPNs are not shared across the networks. VPN clients native to `Windows,
+Mac OS X <networking/using_remote_access.html>`_ and iOS can be used to connect to the guest networks. The
+account owner can create and manage users for their VPN. CloudStack does
+not use its account database for this purpose but uses a separate table.
+The VPN user database is shared across all the VPNs created by the
+account owner. All VPN users get access to all VPNs created by the
+account owner.
+
+.. note::
+ Make sure that not all traffic goes through the VPN. That is, the route
+ installed by the VPN should be only for the guest network and not for
+ all traffic.
+
+- **Road Warrior / Remote Access**. Users want to be able to connect
+ securely from a home or office to a private network in the cloud.
+ Typically, the IP address of the connecting client is dynamic and
+ cannot be preconfigured on the VPN server.
+
+- **Site to Site**. In this scenario, two private subnets are connected
+ over the public Internet with a secure VPN tunnel. The cloud user's
+ subnet (for example, an office network) is connected through a
+ gateway to the network in the cloud. The address of the user's
+ gateway must be preconfigured on the VPN server in the cloud. Note
+ that although L2TP-over-IPsec can be used to set up Site-to-Site
+ VPNs, this is not the primary intent of this feature. For more
+ information, see ":ref:`setting-s2s-vpn-conn`".
+
+
+Configuring Remote Access VPN
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To set up VPN for the cloud:
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, click Global Settings.
+
+#. Set the following global configuration parameters.
+
+ - remote.access.vpn.client.ip.range - The range of IP addresses to
+ be allocated to remote access VPN clients. The first IP in the
+ range is used by the VPN server.
+
+ - remote.access.vpn.psk.length - Length of the IPSec key.
+
+ - remote.access.vpn.user.limit - Maximum number of VPN users per
+ account.
+
+To enable VPN for a particular network:
+
+#. Log in as a user or administrator to the CloudStack UI.
+
+#. In the left navigation, click Network.
+
+#. Click the name of the network you want to work with.
+
+#. Click View IP Addresses.
+
+#. Click one of the displayed IP address names.
+
+#. Click the Enable VPN button. |vpn-icon.png|
+
+ The IPsec key is displayed in a popup window.
+
+
+Configuring Remote Access VPN in VPC
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+On enabling Remote Access VPN on a VPC, any VPN client present outside
+the VPC can access VMs present in the VPC by using the Remote VPN
+connection. The VPN client can be present anywhere except inside the VPC
+on which the user enabled the Remote Access VPN service.
+
+To enable VPN for a VPC:
+
+#. Log in as a user or administrator to the CloudStack UI.
+
+#. In the left navigation, click Network.
+
+#. In the Select view, select VPC.
+
+ All the VPCs that you have created for the account is listed in the
+ page.
+
+#. Click the Configure button of the VPC.
+
+ For each tier, the following options are displayed:
+
+ - Internal LB
+
+ - Public LB IP
+
+ - Static NAT
+
+ - Virtual Machines
+
+ - CIDR
+
+ The following router information is displayed:
+
+ - Private Gateways
+
+ - Public IP Addresses
+
+ - Site-to-Site VPNs
+
+ - Network ACL Lists
+
+#. In the Router node, select Public IP Addresses.
+
+ The IP Addresses page is displayed.
+
+#. Click Source NAT IP address.
+
+#. Click the Enable VPN button. |vpn-icon.png|
+
+ Click OK to confirm. The IPsec key is displayed in a pop-up window.
+
+Now, you need to add the VPN users.
+
+#. Click the Source NAT IP.
+
+#. Select the VPN tab.
+
+#. Add the username and the corresponding password of the user you
+ wanted to add.
+
+#. Click Add.
+
+#. Repeat the same steps to add the VPN users.
\ No newline at end of file
diff --git a/source/adminguide/networking/security_groups.rst b/source/adminguide/networking/security_groups.rst
new file mode 100644
index 0000000..8ef58b8
--- /dev/null
+++ b/source/adminguide/networking/security_groups.rst
@@ -0,0 +1,215 @@
+.. 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.
+
+
+Security Groups
+---------------
+
+About Security Groups
+~~~~~~~~~~~~~~~~~~~~~
+
+Security groups provide a way to isolate traffic to VMs. 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. Security groups are particularly
+useful in zones that use basic networking, because there is a single
+guest network for all guest VMs. In advanced zones, security groups are
+supported only on the KVM hypervisor.
+
+.. note::
+ In a zone that uses advanced networking, you can instead define
+ multiple guest networks to isolate traffic to VMs.
+
+Each CloudStack account comes with a default security group that denies
+all inbound traffic and allows all outbound traffic. The default
+security group can be modified so that all new VMs inherit some other
+desired set of rules.
+
+Any CloudStack user can set up any number of additional security groups.
+When a new VM is launched, it is assigned to the default security group
+unless another user-defined security group is specified. A VM can be a
+member of any number of security groups. Once a VM is assigned to a
+security group, it remains in that group for its entire lifetime; you
+can not move a running VM from one security group to another.
+
+You can modify a security group by deleting or adding any number of
+ingress and egress rules. When you do, the new rules apply to all VMs in
+the group, whether running or stopped.
+
+If no ingress rules are specified, then no traffic will be allowed in,
+except for responses to any traffic that has been allowed out through an
+egress rule.
+
+
+Adding a Security Group
+~~~~~~~~~~~~~~~~~~~~~~~
+
+A user or administrator can define a new security group.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In Select view, choose Security Groups.
+
+#. Click Add Security Group.
+
+#. Provide a name and description.
+
+#. Click OK.
+
+ The new security group appears in the Security Groups Details tab.
+
+#. To make the security group useful, continue to Adding Ingress and
+ Egress Rules to a Security Group.
+
+
+Security Groups in Advanced Zones (KVM Only)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack provides the ability to use security groups to provide
+isolation between guests on a single shared, zone-wide network in an
+advanced zone where KVM is the hypervisor. Using security groups in
+advanced zones rather than multiple VLANs allows a greater range of
+options for setting up guest isolation in a cloud.
+
+
+Limitations
+^^^^^^^^^^^
+
+The following are not supported for this feature:
+
+- Two IP ranges with the same VLAN and different gateway or netmask in
+ security group-enabled shared network.
+
+- Two IP ranges with the same VLAN and different gateway or netmask in
+ account-specific shared networks.
+
+- Multiple VLAN ranges in security group-enabled shared network.
+
+- Multiple VLAN ranges in account-specific shared networks.
+
+Security groups must be enabled in the zone in order for this feature to
+be used.
+
+
+Enabling Security Groups
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+In order for security groups to function in a zone, the security groups
+feature must first be enabled for the zone. The administrator can do
+this when creating a new zone, by selecting a network offering that
+includes security groups. The procedure is described in Basic Zone
+Configuration in the Advanced Installation Guide. The administrator can
+not enable security groups for an existing zone, only when creating a
+new zone.
+
+
+Adding Ingress and Egress Rules to a Security Group
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network
+
+#. In Select view, choose Security Groups, then click the security group
+ you want.
+
+#. To add an ingress rule, click the Ingress Rules tab and fill out the
+ following fields to specify what network traffic is allowed into VM
+ instances in this security group. If no ingress rules are specified,
+ then no traffic will be allowed in, except for responses to any
+ traffic that has been allowed out through an egress rule.
+
+ - **Add by CIDR/Account**. Indicate whether the source of the
+ traffic will be defined by IP address (CIDR) or an existing
+ security group in a CloudStack account (Account). Choose Account
+ if you want to allow incoming traffic from all VMs in another
+ security group
+
+ - **Protocol**. The networking protocol that sources will use to
+ send traffic to the security group. TCP and UDP are typically used
+ for data exchange and end-user communications. ICMP is typically
+ used to send error messages or network monitoring data.
+
+ - **Start Port, End Port**. (TCP, UDP only) A range of listening
+ ports that are the destination for the incoming traffic. If you
+ are opening a single port, use the same number in both fields.
+
+ - **ICMP Type, ICMP Code**. (ICMP only) The type of message and
+ error code that will be accepted.
+
+ - **CIDR**. (Add by CIDR only) To accept only traffic from 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 incoming traffic. For example, 192.168.0.0/22. To allow all
+ CIDRs, set to 0.0.0.0/0.
+
+ - **Account, Security Group**. (Add by Account only) To accept only
+ traffic from another security group, enter the CloudStack account
+ and name of a security group that has already been defined in that
+ account. To allow traffic between VMs within the security group
+ you are editing now, enter the same name you used in step 7.
+
+ The following example allows inbound HTTP access from anywhere:
+
+ |httpaccess.png|
+
+#. 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 security group. If no egress rules
+ are specified, then all traffic will be allowed out. Once egress
+ rules are specified, the following types of traffic are allowed out:
+ traffic specified in egress rules; queries to DNS and DHCP servers;
+ and responses to any traffic that has been allowed in through an
+ ingress rule
+
+ - **Add by CIDR/Account**. Indicate whether the destination of the
+ traffic will be defined by IP address (CIDR) or an existing
+ security group in a CloudStack account (Account). Choose Account
+ if you want to allow outgoing traffic to all VMs in another
+ security group.
+
+ - **Protocol**. The networking protocol that VMs will use to send
+ outgoing traffic. TCP and UDP are typically used for data exchange
+ and end-user communications. ICMP is typically used to send error
+ messages or network monitoring data.
+
+ - **Start Port, End Port**. (TCP, UDP only) A range of listening
+ ports that are the destination for the outgoing traffic. If you
+ are opening a single port, use the same number in both fields.
+
+ - **ICMP Type, ICMP Code**. (ICMP only) The type of message and
+ error code that will be sent
+
+ - **CIDR**. (Add by CIDR only) To send traffic only to 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.
+
+ - **Account, Security Group**. (Add by Account only) To allow
+ traffic to be sent to another security group, enter the CloudStack
+ account and name of a security group that has already been defined
+ in that account. To allow traffic between VMs within the security
+ group you are editing now, enter its name.
+
+#. Click Add.
+
+
+.. |httpaccess.png| image:: /_static/images/http-access.png
+ :alt: allows inbound HTTP access from anywhere.
+
diff --git a/source/adminguide/networking/site_to_site_vpn.rst b/source/adminguide/networking/site_to_site_vpn.rst
new file mode 100644
index 0000000..3049396
--- /dev/null
+++ b/source/adminguide/networking/site_to_site_vpn.rst
@@ -0,0 +1,451 @@
+.. _setting-s2s-vpn-conn:
+
+Setting Up a Site-to-Site VPN Connection
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+A Site-to-Site VPN connection helps you establish a secure connection
+from an enterprise datacenter to the cloud infrastructure. This allows
+users to access the guest VMs by establishing a VPN connection to the
+virtual router of the account from a device in the datacenter of the
+enterprise. You can also establish a secure connection between two VPC
+setups or high availability zones in your environment. Having this
+facility eliminates the need to establish VPN connections to individual
+VMs.
+
+The difference from Remote VPN is that Site-to-site VPNs connects entire
+networks to each other, for example, connecting a branch office network
+to a company headquarters network. In a site-to-site VPN, hosts do not
+have VPN client software; they send and receive normal TCP/IP traffic
+through a VPN gateway.
+
+The supported endpoints on the remote datacenters are:
+
+- Cisco ISR with IOS 12.4 or later
+
+- Juniper J-Series routers with JunOS 9.5 or later
+
+- CloudStack virtual routers
+
+.. note::
+ In addition to the specific Cisco and Juniper devices listed above, the
+ expectation is that any Cisco or Juniper device running on the supported
+ operating systems are able to establish VPN connections.
+
+To set up a Site-to-Site VPN connection, perform the following:
+
+#. Create a Virtual Private Cloud (VPC).
+
+ See ":ref:`configuring-vpc`".
+
+#. Create a VPN Customer Gateway.
+
+#. Create a VPN gateway for the VPC that you created.
+
+#. Create VPN connection from the VPC VPN gateway to the customer VPN
+ gateway.
+
+
+Creating and Updating a VPN Customer Gateway
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. note::
+ A VPN customer gateway can be connected to only one VPN gateway at a time.
+
+To add a VPN Customer Gateway:
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPN Customer Gateway.
+
+#. Click Add VPN Customer Gateway.
+
+ |addvpncustomergateway.png|
+
+ Provide the following information:
+
+ - **Name**: A unique name for the VPN customer gateway you create.
+
+ - **Gateway**: The IP address for the remote gateway.
+
+ - **CIDR list**: The guest CIDR list of the remote subnets. Enter a
+ CIDR or a comma-separated list of CIDRs. Ensure that a guest CIDR
+ list is not overlapped with the VPC's CIDR, or another guest CIDR.
+ The CIDR must be RFC1918-compliant.
+
+ - **IPsec Preshared Key**: Preshared keying is a method where the
+ endpoints of the VPN share a secret key. This key value is used to
+ authenticate the customer gateway and the VPC VPN gateway to each
+ other. The sequence cannot contain a newline or double-quote.
+
+ .. note::
+ The IKE peers (VPN end points) authenticate each other by
+ computing and sending a keyed hash of data that includes the
+ Preshared key. If the receiving peer is able to create the same
+ hash independently by using its Preshared key, it knows that both
+ peers must share the same secret, thus authenticating the customer
+ gateway.
+
+ - **IKE Encryption**: The Internet Key Exchange (IKE) policy for
+ phase-1. The supported encryption algorithms are AES128, AES192,
+ AES256, and 3DES. Authentication is accomplished through the
+ Preshared Keys.
+
+ .. note::
+ The phase-1 is the first phase in the IKE process. In this initial
+ negotiation phase, the two VPN endpoints agree on the methods to
+ be used to provide security for the underlying IP traffic. The
+ phase-1 authenticates the two VPN gateways to each other, by
+ confirming that the remote gateway has a matching Preshared Key.
+
+ - **IKE Hash**: The IKE hash for phase-1. The supported hash
+ algorithms are SHA1 and MD5.
+
+ - **IKE DH**: A public-key cryptography protocol which allows two
+ parties to establish a shared secret over an insecure
+ communications channel. The 1536-bit Diffie-Hellman group is used
+ within IKE to establish session keys. The supported options are
+ None, Group-5 (1536-bit) and Group-2 (1024-bit).
+
+ - **ESP Encryption**: Encapsulating Security Payload (ESP) algorithm
+ within phase-2. The supported encryption algorithms are AES128,
+ AES192, AES256, and 3DES.
+
+ .. note::
+ The phase-2 is the second phase in the IKE process. The purpose of
+ IKE phase-2 is to negotiate IPSec security associations (SA) to
+ set up the IPSec tunnel. In phase-2, new keying material is
+ extracted from the Diffie-Hellman key exchange in phase-1, to
+ provide session keys to use in protecting the VPN data flow.
+
+ - **ESP Hash**: Encapsulating Security Payload (ESP) hash for
+ phase-2. Supported hash algorithms are SHA1 and MD5.
+
+ - **Perfect Forward Secrecy**: Perfect Forward Secrecy (or PFS) is
+ the property that ensures that a session key derived from a set of
+ long-term public and private keys will not be compromised. This
+ property enforces a new Diffie-Hellman key exchange. It provides
+ the keying material that has greater key material life and thereby
+ greater resistance to cryptographic attacks. The available options
+ are None, Group-5 (1536-bit) and Group-2 (1024-bit). The security
+ of the key exchanges increase as the DH groups grow larger, as
+ does the time of the exchanges.
+
+ .. note::
+ When PFS is turned on, for every negotiation of a new phase-2 SA
+ the two gateways must generate a new set of phase-1 keys. This
+ adds an extra layer of protection that PFS adds, which ensures if
+ the phase-2 SA's have expired, the keys used for new phase-2 SA's
+ have not been generated from the current phase-1 keying material.
+
+ - **IKE Lifetime (seconds)**: The phase-1 lifetime of the security
+ association in seconds. Default is 86400 seconds (1 day). Whenever
+ the time expires, a new phase-1 exchange is performed.
+
+ - **ESP Lifetime (seconds)**: The phase-2 lifetime of the security
+ association in seconds. Default is 3600 seconds (1 hour). Whenever
+ the value is exceeded, a re-key is initiated to provide a new
+ IPsec encryption and authentication session keys.
+
+ - **Dead Peer Detection**: A method to detect an unavailable
+ Internet Key Exchange (IKE) peer. Select this option if you want
+ the virtual router to query the liveliness of its IKE peer at
+ regular intervals. It's recommended to have the same configuration
+ of DPD on both side of VPN connection.
+
+#. Click OK.
+
+
+Updating and Removing a VPN Customer Gateway
+''''''''''''''''''''''''''''''''''''''''''''
+
+You can update a customer gateway either with no VPN connection, or
+related VPN connection is in error state.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPN Customer Gateway.
+
+#. Select the VPN customer gateway you want to work with.
+
+#. To modify the required parameters, click the Edit VPN Customer
+ Gateway button |vpn-edit-icon.png|
+
+#. To remove the VPN customer gateway, click the Delete VPN Customer
+ Gateway button |delete.png|
+
+#. Click OK.
+
+
+Creating a VPN gateway for the VPC
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+ All the VPCs that you have created for the account is listed in the
+ page.
+
+#. Click the Configure button of the VPC to which you want to deploy the
+ VMs.
+
+ The VPC page is displayed where all the tiers you created are listed
+ in a diagram.
+
+ For each tier, the following options are displayed:
+
+ - Internal LB
+
+ - Public LB IP
+
+ - Static NAT
+
+ - Virtual Machines
+
+ - CIDR
+
+ The following router information is displayed:
+
+ - Private Gateways
+
+ - Public IP Addresses
+
+ - Site-to-Site VPNs
+
+ - Network ACL Lists
+
+#. Select Site-to-Site VPN.
+
+ If you are creating the VPN gateway for the first time, selecting
+ Site-to-Site VPN prompts you to create a VPN gateway.
+
+#. In the confirmation dialog, click Yes to confirm.
+
+ Within a few moments, the VPN gateway is created. You will be
+ prompted to view the details of the VPN gateway you have created.
+ Click Yes to confirm.
+
+ The following details are displayed in the VPN Gateway page:
+
+ - IP Address
+
+ - Account
+
+ - Domain
+
+
+Creating a VPN Connection
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. note:: CloudStack supports creating up to 8 VPN connections.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+ All the VPCs that you create for the account are listed in the page.
+
+#. Click the Configure button of the VPC to which you want to deploy the
+ VMs.
+
+ The VPC page is displayed where all the tiers you created are listed
+ in a diagram.
+
+#. Click the Settings icon.
+
+ For each tier, the following options are displayed:
+
+ - Internal LB
+
+ - Public LB IP
+
+ - Static NAT
+
+ - Virtual Machines
+
+ - CIDR
+
+ The following router information is displayed:
+
+ - Private Gateways
+
+ - Public IP Addresses
+
+ - Site-to-Site VPNs
+
+ - Network ACL Lists
+
+#. Select Site-to-Site VPN.
+
+ The Site-to-Site VPN page is displayed.
+
+#. From the Select View drop-down, ensure that VPN Connection is
+ selected.
+
+#. Click Create VPN Connection.
+
+ The Create VPN Connection dialog is displayed:
+
+ |createvpnconnection.png|
+
+#. Select the desired customer gateway.
+
+#. Select Passive if you want to establish a connection between two VPC
+ virtual routers.
+
+ If you want to establish a connection between two VPC virtual
+ routers, select Passive only on one of the VPC virtual routers, which
+ waits for the other VPC virtual router to initiate the connection. Do
+ not select Passive on the VPC virtual router that initiates the
+ connection.
+
+#. Click OK to confirm.
+
+ Within a few moments, the VPN Connection is displayed.
+
+ The following information on the VPN connection is displayed:
+
+ - IP Address
+
+ - Gateway
+
+ - State
+
+ - IPSec Preshared Key
+
+ - IKE Policy
+
+ - ESP Policy
+
+
+Site-to-Site VPN Connection Between VPC Networks
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+CloudStack provides you with the ability to establish a site-to-site VPN
+connection between CloudStack virtual routers. To achieve that, add a
+passive mode Site-to-Site VPN. With this functionality, users can deploy
+applications in multiple Availability Zones or VPCs, which can
+communicate with each other by using a secure Site-to-Site VPN Tunnel.
+
+This feature is supported on all the hypervisors.
+
+#. Create two VPCs. For example, VPC A and VPC B.
+
+ For more information, see ":ref:`configuring-vpc`".
+
+#. Create VPN gateways on both the VPCs you created.
+
+ For more information, see `"Creating a VPN gateway
+ for the VPC" <#creating-a-vpn-gateway-for-the-vpc>`_.
+
+#. Create VPN customer gateway for both the VPCs.
+
+ For more information, see `"Creating and Updating
+ a VPN Customer Gateway" <#creating-and-updating-a-vpn-customer-gateway>`_.
+
+#. Enable a VPN connection on VPC A in passive mode.
+
+ For more information, see `"Creating a VPN
+ Connection" <#creating-a-vpn-connection>`_.
+
+ Ensure that the customer gateway is pointed to VPC B. The VPN
+ connection is shown in the Disconnected state.
+
+#. Enable a VPN connection on VPC B.
+
+ Ensure that the customer gateway is pointed to VPC A. Because virtual
+ router of VPC A, in this case, is in passive mode and is waiting for
+ the virtual router of VPC B to initiate the connection, VPC B virtual
+ router should not be in passive mode.
+
+ The VPN connection is shown in the Disconnected state.
+
+ Creating VPN connection on both the VPCs initiates a VPN connection.
+ Wait for few seconds. The default is 30 seconds for both the VPN
+ connections to show the Connected state.
+
+
+Restarting and Removing a VPN Connection
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+ All the VPCs that you have created for the account is listed in the
+ page.
+
+#. Click the Configure button of the VPC to which you want to deploy the
+ VMs.
+
+ The VPC page is displayed where all the tiers you created are listed
+ in a diagram.
+
+#. Click the Settings icon.
+
+ For each tier, the following options are displayed:
+
+ - Internal LB
+
+ - Public LB IP
+
+ - Static NAT
+
+ - Virtual Machines
+
+ - CIDR
+
+ The following router information is displayed:
+
+ - Private Gateways
+
+ - Public IP Addresses
+
+ - Site-to-Site VPNs
+
+ - Network ACL Lists
+
+#. Select Site-to-Site VPN.
+
+ The Site-to-Site VPN page is displayed.
+
+#. From the Select View drop-down, ensure that VPN Connection is
+ selected.
+
+ All the VPN connections you created are displayed.
+
+#. Select the VPN connection you want to work with.
+
+ The Details tab is displayed.
+
+#. To remove a VPN connection, click the Delete VPN connection button
+ |remove-vpn.png|
+
+ To restart a VPN connection, click the Reset VPN connection button
+ present in the Details tab. |reset-vpn.png|
+
+
+.. |vpn-icon.png| image:: /_static/images/vpn-icon.png
+ :alt: button to enable VPN.
+.. |addvpncustomergateway.png| image:: /_static/images/add-vpn-customer-gateway.png
+ :alt: adding a customer gateway.
+.. |createvpnconnection.png| image:: /_static/images/create-vpn-connection.png
+ :alt: creating a VPN connection to the customer gateway.
+.. |remove-vpn.png| image:: /_static/images/remove-vpn.png
+ :alt: button to remove a VPN connection
+.. |reset-vpn.png| image:: /_static/images/reset-vpn.png
+ :alt: button to reset a VPN connection
+.. |delete.png| image:: /_static/images/delete-button.png
+ :alt: button to remove a VPN customer gateway.
+.. |vpn-edit-icon.png| image:: /_static/images/edit-icon.png
+ :alt: button to edit.
diff --git a/source/adminguide/networking/static_nat.rst b/source/adminguide/networking/static_nat.rst
new file mode 100644
index 0000000..4e6199e
--- /dev/null
+++ b/source/adminguide/networking/static_nat.rst
@@ -0,0 +1,56 @@
+.. 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.
+
+
+Static NAT
+----------
+
+A static NAT rule maps a public IP address to the private IP address of
+a VM in order to allow Internet traffic into the VM. The public IP
+address always remains the same, which is why it is called static NAT.
+This section tells how to enable or disable static NAT for a particular
+IP address.
+
+
+Enabling or Disabling Static NAT
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If port forwarding rules are already in effect for an IP address, you
+cannot enable static NAT to that IP.
+
+If a guest VM is part of more than one network, static NAT rules will
+function only if they are defined on the default network.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. Click the name of the network where you want to work with.
+
+#. Click View IP Addresses.
+
+#. Click the IP address you want to work with.
+
+#. Click the Static NAT |enabledisablenat.png| button.
+
+ The button toggles between Enable and Disable, depending on whether
+ static NAT is currently enabled for the IP address.
+
+#. If you are enabling static NAT, a dialog appears where you can choose
+ the destination VM and click Apply.
+
+
+.. |enabledisablenat.png| image:: /_static/images/enable-disable.png
+ :alt: button to enable/disable NAT.
diff --git a/source/adminguide/networking/using_remote_access.rst b/source/adminguide/networking/using_remote_access.rst
new file mode 100644
index 0000000..2161abe
--- /dev/null
+++ b/source/adminguide/networking/using_remote_access.rst
@@ -0,0 +1,148 @@
+.. 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.
+
+
+Using Remote Access VPN
+=======================
+
+.. sidebar:: Clients
+ :subtitle: Per Operating System instructions
+
+ .. contents::
+ :local:
+ :depth: 1
+
+Remote Access VPN connection to VPC or Guest Network to access Instances and applications. This section consider you have enable Remonte acccess VPN, refer to: :ref:`remote-access-vpn`.
+
+When connected to a VPC via VPN, the client have access to all Tiers.
+
+Following information is required to confiture VPN client:
+
+ - ``Public IP``: source NAT with VPN enabled.
+ - ``IPsec pre-shared key``: Provide at the VPN activation.
+ - ``Username`` VPN account username.
+ - ``Password`` VPN account password.
+
+
+Mac OSX
+-------
+
+Mac OSX provide native IPsec VPN client.
+
+#. Into System Preferences -> Network
+
+#. Click "+" button and add a VPN:
+
+ - Interface: VPN
+ - VPN Type: L2TP over IPSec
+ - Service Name: (ex: test-vpc1)
+
+ .. image:: /_static/images/vpn/osxvpn_netconf.png
+ :align: center
+ :width: 400 px
+
+#. Configure L2TP over IPsec
+
+ .. image:: /_static/images/vpn/osxvpn_form1.png
+ :align: center
+ :width: 400 px
+
+ .. image:: /_static/images/vpn/osxvpn_form2.png
+ :align: center
+ :width: 400 px
+
+#. Inside Authentication Settings...
+
+ .. image:: /_static/images/vpn/osxvpn_form3.png
+ :align: center
+ :width: 400 px
+
+#. Connect into VPN
+
+ #. Click Apply to apply Network configuration changes.
+ #. Click Connect to initiate VPN connection.
+
+ .. image:: /_static/images/vpn/osxvpn_connected.png
+ :align: center
+ :width: 400 px
+
+
+Microsoft Windows 8
+-------------------
+
+Following instruction have been perform using Windows 8.1 using Native VPN client.
+
+#. Create network VPN connection
+
+ .. image:: /_static/images/vpn/win1.png
+ :align: center
+ :width: 400 px
+
+ .. image:: /_static/images/vpn/win2.png
+ :align: center
+ :width: 400 px
+
+ .. image:: /_static/images/vpn/win3.png
+ :align: center
+ :width: 400 px
+
+ .. image:: /_static/images/vpn/win4.png
+ :align: center
+ :width: 400 px
+
+ .. image:: /_static/images/vpn/win5.png
+ :align: center
+ :width: 400 px
+
+ .. image:: /_static/images/vpn/win6.png
+ :align: center
+ :width: 400 px
+
+
+#. Configure VPN settings
+
+ .. image:: /_static/images/vpn/win7.png
+ :align: center
+ :width: 400 px
+
+ .. image:: /_static/images/vpn/win8.png
+ :align: center
+ :width: 400 px
+
+ .. image:: /_static/images/vpn/win9.png
+ :align: center
+ :width: 400 px
+
+ .. image:: /_static/images/vpn/win10.png
+ :align: center
+ :width: 400 px
+
+ .. image:: /_static/images/vpn/win11.png
+ :align: center
+ :width: 400 px
+
+#. Initiate VPN connection
+
+ .. image:: /_static/images/vpn/win12.png
+ :align: center
+ :width: 400 px
+
+ .. image:: /_static/images/vpn/win13.png
+ :align: center
+ :width: 400 px
+
+ .. image:: /_static/images/vpn/win14.png
+ :align: center
+ :width: 400 px
diff --git a/source/adminguide/networking/virtual_private_cloud_config.rst b/source/adminguide/networking/virtual_private_cloud_config.rst
new file mode 100644
index 0000000..75042b2
--- /dev/null
+++ b/source/adminguide/networking/virtual_private_cloud_config.rst
@@ -0,0 +1,1442 @@
+.. 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-vpc:
+
+Configuring a Virtual Private Cloud
+-----------------------------------
+
+.. _about-vpc:
+
+About Virtual Private Clouds
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack Virtual Private Cloud is a private, isolated part of
+CloudStack. A VPC can have its own virtual network topology that
+resembles a traditional physical network. You can launch VMs in the
+virtual network that can have private addresses in the range of your
+choice, for example: 10.0.0.0/16. You can define network tiers within
+your VPC network range, which in turn enables you to group similar kinds
+of instances based on IP address range.
+
+For example, if a VPC has the private range 10.0.0.0/16, its guest
+networks can have the network ranges 10.0.1.0/24, 10.0.2.0/24,
+10.0.3.0/24, and so on.
+
+
+Major Components of a VPC
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+A VPC is comprised of the following network components:
+
+- **VPC**: A VPC acts as a container for multiple isolated networks
+ that can communicate with each other via its virtual router.
+
+- **Network Tiers**: Each tier acts as an isolated network with its own
+ VLANs and CIDR list, where you can place groups of resources, such as
+ VMs. The tiers are segmented by means of VLANs. The NIC of each tier
+ acts as its gateway.
+
+- **Virtual Router**: A virtual router is automatically created and
+ started when you create a VPC. The virtual router connect the tiers
+ and direct traffic among the public gateway, the VPN gateways, and
+ the NAT instances. For each tier, a corresponding NIC and IP exist in
+ the virtual router. The virtual router provides DNS and DHCP services
+ through its IP.
+
+- **Public Gateway**: The traffic to and from the Internet routed to
+ the VPC through the public gateway. In a VPC, the public gateway is
+ not exposed to the end user; therefore, static routes are not support
+ for the public gateway.
+
+- **Private Gateway**: All the traffic to and from a private network
+ routed to the VPC through the private gateway. For more information,
+ see ":ref:`adding-priv-gw-vpc`".
+
+- **VPN Gateway**: The VPC side of a VPN connection.
+
+- **Site-to-Site VPN Connection**: A hardware-based VPN connection
+ between your VPC and your datacenter, home network, or co-location
+ facility. For more information, see ":ref:`setting-s2s-vpn-conn`".
+
+- **Customer Gateway**: The customer side of a VPN Connection. For more
+ information, see `"Creating and Updating a VPN
+ Customer Gateway" <#creating-and-updating-a-vpn-customer-gateway>`_.
+
+- **NAT Instance**: An instance that provides Port Address Translation
+ for instances to access the Internet via the public gateway. For more
+ information, see ":ref:`enabling-disabling-static-nat-on-vpc`".
+
+- **Network ACL**: Network ACL is a group of Network ACL items. Network
+ ACL items are nothing but numbered rules that are evaluated in order,
+ starting with the lowest numbered rule. These rules determine whether
+ traffic is allowed in or out of any tier associated with the network
+ ACL. For more information, see ":ref:`conf-net-acl`".
+
+
+Network Architecture in a VPC
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+In a VPC, the following four basic options of network architectures are
+present:
+
+- VPC with a public gateway only
+
+- VPC with public and private gateways
+
+- VPC with public and private gateways and site-to-site VPN access
+
+- VPC with a private gateway only and site-to-site VPN access
+
+
+Connectivity Options for a VPC
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+You can connect your VPC to:
+
+- The Internet through the public gateway.
+
+- The corporate datacenter by using a site-to-site VPN connection
+ through the VPN gateway.
+
+- Both the Internet and your corporate datacenter by using both the
+ public gateway and a VPN gateway.
+
+
+VPC Network Considerations
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Consider the following before you create a VPC:
+
+- A VPC, by default, is created in the enabled state.
+
+- A VPC can be created in Advance zone only, and can't belong to more
+ than one zone at a time.
+
+- The default number of VPCs an account can create is 20. However, you
+ can change it by using the max.account.vpcs global parameter, which
+ controls the maximum number of VPCs an account is allowed to create.
+
+- The default number of tiers an account can create within a VPC is 3.
+ You can configure this number by using the vpc.max.networks
+ parameter.
+
+- Each tier should have an unique CIDR in the VPC. Ensure that the
+ tier's CIDR should be within the VPC CIDR range.
+
+- A tier belongs to only one VPC.
+
+- All network tiers inside the VPC should belong to the same account.
+
+- When a VPC is created, by default, a SourceNAT IP is allocated to it.
+ The Source NAT IP is released only when the VPC is removed.
+
+- A public IP can be used for only one purpose at a time. If the IP is
+ a sourceNAT, it cannot be used for StaticNAT or port forwarding.
+
+- The instances can only have a private IP address that you provision.
+ To communicate with the Internet, enable NAT to an instance that you
+ launch in your VPC.
+
+- Only new networks can be added to a VPC. The maximum number of
+ networks per VPC is limited by the value you specify in the
+ vpc.max.networks parameter. The default value is three.
+
+- The load balancing service can be supported by only one tier inside
+ the VPC.
+
+- If an IP address is assigned to a tier:
+
+ - That IP can't be used by more than one tier at a time in the VPC.
+ For example, if you have tiers A and B, and a public IP1, you can
+ create a port forwarding rule by using the IP either for A or B,
+ but not for both.
+
+ - That IP can't be used for StaticNAT, load balancing, or port
+ forwarding rules for another guest network inside the VPC.
+
+- Remote access VPN is not supported in VPC networks.
+
+
+Adding a Virtual Private Cloud
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When creating the VPC, you simply provide the zone and a set of IP
+addresses for the VPC network address space. You specify this set of
+addresses in the form of a Classless Inter-Domain Routing (CIDR) block.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+#. Click Add VPC. The Add VPC page is displayed as follows:
+
+ |add-vpc.png|
+
+ Provide the following information:
+
+ - **Name**: A short name for the VPC that you are creating.
+
+ - **Description**: A brief description of the VPC.
+
+ - **Zone**: Choose the zone where you want the VPC to be available.
+
+ - **Super CIDR for Guest Networks**: Defines the CIDR range for all
+ the tiers (guest networks) within a VPC. When you create a tier,
+ ensure that its CIDR is within the Super CIDR value you enter. The
+ CIDR must be RFC1918 compliant.
+
+ - **DNS domain for Guest Networks**: If you want to assign a special
+ domain name, specify the DNS suffix. This parameter is applied to
+ all the tiers within the VPC. That implies, all the tiers you
+ create in the VPC belong to the same DNS domain. If the parameter
+ is not specified, a DNS domain name is generated automatically.
+
+ - **Public Load Balancer Provider**: You have two options: VPC
+ Virtual Router and Netscaler.
+
+#. Click OK.
+
+
+Adding Tiers
+~~~~~~~~~~~~
+
+Tiers are distinct locations within a VPC that act as isolated networks,
+which do not have access to other tiers by default. Tiers are set up on
+different VLANs that can communicate with each other by using a virtual
+router. Tiers provide inexpensive, low latency network connectivity to
+other tiers within the VPC.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+ All the VPC that you have created for the account is listed in the
+ page.
+
+ .. note::
+ The end users can see their own VPCs, while root and domain admin can
+ see any VPC they are authorized to see.
+
+#. Click the Configure button of the VPC for which you want to set up
+ tiers.
+
+#. Click Create network.
+
+ The Add new tier dialog is displayed, as follows:
+
+ |add-tier.png|
+
+ If you have already created tiers, the VPC diagram is displayed.
+ Click Create Tier to add a new tier.
+
+#. Specify the following:
+
+ All the fields are mandatory.
+
+ - **Name**: A unique name for the tier you create.
+
+ - **Network Offering**: The following default network offerings are
+ listed: Internal LB,
+ DefaultIsolatedNetworkOfferingForVpcNetworksNoLB,
+ DefaultIsolatedNetworkOfferingForVpcNetworks
+
+ In a VPC, only one tier can be created by using LB-enabled network
+ offering.
+
+ - **Gateway**: The gateway for the tier you create. Ensure that the
+ gateway is within the Super CIDR range that you specified while
+ creating the VPC, and is not overlapped with the CIDR of any
+ existing tier within the VPC.
+
+ - **VLAN**: The VLAN ID for the tier that the root admin creates.
+
+ This option is only visible if the network offering you selected
+ is VLAN-enabled.
+
+ For more information, see `"Assigning VLANs to
+ Isolated Networks" <hosts.html#assigning-vlans-to-isolated-networks>`_.
+
+ - **Netmask**: The netmask for the tier you create.
+
+ For example, if the VPC CIDR is 10.0.0.0/16 and the network tier
+ CIDR is 10.0.1.0/24, the gateway of the tier is 10.0.1.1, and the
+ netmask of the tier is 255.255.255.0.
+
+#. Click OK.
+
+#. Continue with configuring access control list for the tier.
+
+
+.. _conf-net-acl:
+
+Configuring Network Access Control List
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Define Network Access Control List (ACL) on the VPC virtual router to
+control incoming (ingress) and outgoing (egress) traffic between the VPC
+tiers, and the tiers and Internet. By default, all incoming traffic to
+the guest networks is blocked and all outgoing traffic from guest
+networks is allowed, once you add an ACL rule for outgoing traffic, then
+only outgoing traffic specified in this ACL rule is allowed, the rest is
+blocked. To open the ports, you must create a new network ACL. The
+network ACLs can be created for the tiers only if the NetworkACL service
+is supported.
+
+
+About Network ACL Lists
+^^^^^^^^^^^^^^^^^^^^^^^
+
+In CloudStack terminology, Network ACL is a group of Network ACL items.
+Network ACL items are nothing but numbered rules that are evaluated in
+order, starting with the lowest numbered rule. These rules determine
+whether traffic is allowed in or out of any tier associated with the
+network ACL. You need to add the Network ACL items to the Network ACL,
+then associate the Network ACL with a tier. Network ACL is associated
+with a VPC and can be assigned to multiple VPC tiers within a VPC. A
+Tier is associated with a Network ACL at all the times. Each tier can be
+associated with only one ACL.
+
+The default Network ACL is used when no ACL is associated. Default
+behavior is all the incoming traffic is blocked and outgoing traffic is
+allowed from the tiers. Default network ACL cannot be removed or
+modified. Contents of the default Network ACL is:
+
+.. cssclass:: table-striped table-bordered table-hover
+
+===== ======== ============ ====== =========
+Rule Protocol Traffic type Action CIDR
+===== ======== ============ ====== =========
+1 All Ingress Deny 0.0.0.0/0
+2 All Egress Deny 0.0.0.0/0
+===== ======== ============ ====== =========
+
+
+Creating ACL Lists
+^^^^^^^^^^^^^^^^^^
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+ All the VPCs that you have created for the account is listed in the
+ page.
+
+#. Click the Configure button of the VPC.
+
+ For each tier, the following options are displayed:
+
+ - Internal LB
+
+ - Public LB IP
+
+ - Static NAT
+
+ - Virtual Machines
+
+ - CIDR
+
+ The following router information is displayed:
+
+ - Private Gateways
+
+ - Public IP Addresses
+
+ - Site-to-Site VPNs
+
+ - Network ACL Lists
+
+#. Select Network ACL Lists.
+
+ The following default rules are displayed in the Network ACLs page:
+ default\_allow, default\_deny.
+
+#. Click Add ACL Lists, and specify the following:
+
+ - **ACL List Name**: A name for the ACL list.
+
+ - **Description**: A short description of the ACL list that can be
+ displayed to users.
+
+
+Creating an ACL Rule
+^^^^^^^^^^^^^^^^^^^^
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+ All the VPCs that you have created for the account is listed in the
+ page.
+
+#. Click the Configure button of the VPC.
+
+#. Select Network ACL Lists.
+
+ In addition to the custom ACL lists you have created, the following
+ default rules are displayed in the Network ACLs page: default\_allow,
+ default\_deny.
+
+#. Select the desired ACL list.
+
+#. Select the ACL List Rules tab.
+
+ To add an ACL rule, fill in the following fields to specify what kind
+ of network traffic is allowed in the VPC.
+
+ - **Rule Number**: The order in which the rules are evaluated.
+
+ - **CIDR**: The CIDR acts as the Source CIDR for the Ingress rules,
+ and Destination CIDR for the Egress rules. To accept traffic only
+ from or 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 incoming traffic. For example,
+ 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0.
+
+ - **Action**: What action to be taken. Allow traffic or block.
+
+ - **Protocol**: The networking protocol that sources use to send
+ traffic to the tier. 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. All supports all the traffic. Other option is Protocol
+ Number.
+
+ - **Start Port**, **End Port** (TCP, UDP only): A range of listening
+ ports that are the destination for the incoming traffic. If you
+ are opening a single port, use the same number in both fields.
+
+ - **Protocol Number**: The protocol number associated with IPv4 or
+ IPv6. For more information, see `Protocol Numbers
+ <http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xml>`_.
+
+ - **ICMP Type**, **ICMP Code** (ICMP only): The type of message and
+ error code that will be sent.
+
+ - **Traffic Type**: The type of traffic: Incoming or outgoing.
+
+#. Click Add. The ACL rule is added.
+
+ You can edit the tags assigned to the ACL rules and delete the ACL
+ rules you have created. Click the appropriate button in the Details
+ tab.
+
+
+Creating a Tier with Custom ACL List
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. Create a VPC.
+
+#. Create a custom ACL list.
+
+#. Add ACL rules to the ACL list.
+
+#. Create a tier in the VPC.
+
+ Select the desired ACL list while creating a tier.
+
+#. Click OK.
+
+
+Assigning a Custom ACL List to a Tier
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. Create a VPC.
+
+#. Create a tier in the VPC.
+
+#. Associate the tier with the default ACL rule.
+
+#. Create a custom ACL list.
+
+#. Add ACL rules to the ACL list.
+
+#. Select the tier for which you want to assign the custom ACL.
+
+#. Click the Replace ACL List icon. |replace-acl-icon.png|
+
+ The Replace ACL List dialog is displayed.
+
+#. Select the desired ACL list.
+
+#. Click OK.
+
+
+.. _adding-priv-gw-vpc:
+
+Adding a Private Gateway to a VPC
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+A private gateway can be added by the root admin only. The VPC private
+network has 1:1 relationship with the NIC of the physical network. You
+can configure multiple private gateways to a single VPC. No gateways
+with duplicated VLAN and IP are allowed in the same data center.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+ All the VPCs that you have created for the account is listed in the
+ page.
+
+#. Click the Configure button of the VPC to which you want to configure
+ load balancing rules.
+
+ The VPC page is displayed where all the tiers you created are listed
+ in a diagram.
+
+#. Click the Settings icon.
+
+ The following options are displayed.
+
+ - Internal LB
+
+ - Public LB IP
+
+ - Static NAT
+
+ - Virtual Machines
+
+ - CIDR
+
+ The following router information is displayed:
+
+ - Private Gateways
+
+ - Public IP Addresses
+
+ - Site-to-Site VPNs
+
+ - Network ACL Lists
+
+#. Select Private Gateways.
+
+ The Gateways page is displayed.
+
+#. Click Add new gateway:
+
+ |add-new-gateway-vpc.png|
+
+#. Specify the following:
+
+ - **Physical Network**: The physical network you have created in the
+ zone.
+
+ - **IP Address**: The IP address associated with the VPC gateway.
+
+ - **Gateway**: The gateway through which the traffic is routed to
+ and from the VPC.
+
+ - **Netmask**: The netmask associated with the VPC gateway.
+
+ - **VLAN**: The VLAN associated with the VPC gateway.
+
+ - **Source NAT**: Select this option to enable the source NAT
+ service on the VPC private gateway.
+
+ See ":ref:`source-nat-priv-gw`".
+
+ - **ACL**: Controls both ingress and egress traffic on a VPC private
+ gateway. By default, all the traffic is blocked.
+
+ See ":ref:`acl-priv-gw`".
+
+ The new gateway appears in the list. You can repeat these steps to
+ add more gateway for this VPC.
+
+
+.. _source-nat-priv-gw:
+
+Source NAT on Private Gateway
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+You might want to deploy multiple VPCs with the same super CIDR and
+guest tier CIDR. Therefore, multiple guest VMs from different VPCs can
+have the same IPs to reach a enterprise data center through the private
+gateway. In such cases, a NAT service need to be configured on the
+private gateway to avoid IP conflicts. If Source NAT is enabled, the
+guest VMs in VPC reaches the enterprise network via private gateway IP
+address by using the NAT service.
+
+The Source NAT service on a private gateway can be enabled while adding
+the private gateway. On deletion of a private gateway, source NAT rules
+specific to the private gateway are deleted.
+
+To enable source NAT on existing private gateways, delete them and
+create afresh with source NAT.
+
+
+.. _acl-priv-gw:
+
+ACL on Private Gateway
+^^^^^^^^^^^^^^^^^^^^^^
+
+The traffic on the VPC private gateway is controlled by creating both
+ingress and egress network ACL rules. The ACLs contains both allow and
+deny rules. As per the rule, all the ingress traffic to the private
+gateway interface and all the egress traffic out from the private
+gateway interface are blocked.
+
+You can change this default behaviour while creating a private gateway.
+Alternatively, you can do the following:
+
+#. In a VPC, identify the Private Gateway you want to work with.
+
+#. In the Private Gateway page, do either of the following:
+
+ - Use the Quickview. See 3.
+
+ - Use the Details tab. See 4 through .
+
+#. In the Quickview of the selected Private Gateway, click Replace ACL,
+ select the ACL rule, then click OK
+
+#. Click the IP address of the Private Gateway you want to work with.
+
+#. In the Detail tab, click the Replace ACL button.
+ |replace-acl-icon.png|
+
+ The Replace ACL dialog is displayed.
+
+#. select the ACL rule, then click OK.
+
+ Wait for few seconds. You can see that the new ACL rule is displayed
+ in the Details page.
+
+
+Creating a Static Route
+^^^^^^^^^^^^^^^^^^^^^^^
+
+CloudStack enables you to specify routing for the VPN connection you
+create. You can enter one or CIDR addresses to indicate which traffic is
+to be routed back to the gateway.
+
+#. In a VPC, identify the Private Gateway you want to work with.
+
+#. In the Private Gateway page, click the IP address of the Private
+ Gateway you want to work with.
+
+#. Select the Static Routes tab.
+
+#. Specify the CIDR of destination network.
+
+#. Click Add.
+
+ Wait for few seconds until the new route is created.
+
+
+Blacklisting Routes
+^^^^^^^^^^^^^^^^^^^
+
+CloudStack enables you to block a list of routes so that they are not
+assigned to any of the VPC private gateways. Specify the list of routes
+that you want to blacklist in the ``blacklisted.routes`` global
+parameter. Note that the parameter update affects only new static route
+creations. If you block an existing static route, it remains intact and
+continue functioning. You cannot add a static route if the route is
+blacklisted for the zone.
+
+
+Deploying VMs to the Tier
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+ All the VPCs that you have created for the account is listed in the
+ page.
+
+#. Click the Configure button of the VPC to which you want to deploy the
+ VMs.
+
+ The VPC page is displayed where all the tiers you have created are
+ listed.
+
+#. Click Virtual Machines tab of the tier to which you want to add a VM.
+
+ |add-vm-vpc.png|
+
+ The Add Instance page is displayed.
+
+ Follow the on-screen instruction to add an instance. For information
+ on adding an instance, see the Installation Guide.
+
+
+Deploying VMs to VPC Tier and Shared Networks
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack allows you deploy VMs on a VPC tier and one or more shared
+networks. With this feature, VMs deployed in a multi-tier application
+can receive monitoring services via a shared network provided by a
+service provider.
+
+#. Log in to the CloudStack UI as an administrator.
+
+#. In the left navigation, choose Instances.
+
+#. Click Add Instance.
+
+#. Select a zone.
+
+#. Select a template or ISO, then follow the steps in the wizard.
+
+#. Ensure that the hardware you have allows starting the selected
+ service offering.
+
+#. Under Networks, select the desired networks for the VM you are
+ launching.
+
+ You can deploy a VM to a VPC tier and multiple shared networks.
+
+ |addvm-tier-sharednw.png|
+
+#. Click Next, review the configuration and click Launch.
+
+ Your VM will be deployed to the selected VPC tier and shared network.
+
+
+Acquiring a New IP Address for a VPC
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When you acquire an IP address, all IP addresses are allocated to VPC,
+not to the guest networks within the VPC. The IPs are associated to the
+guest network only when the first port-forwarding, load balancing, or
+Static NAT rule is created for the IP or the network. IP can't be
+associated to more than one network at a time.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+ All the VPCs that you have created for the account is listed in the
+ page.
+
+#. Click the Configure button of the VPC to which you want to deploy the
+ VMs.
+
+ The VPC page is displayed where all the tiers you created are listed
+ in a diagram.
+
+ The following options are displayed.
+
+ - Internal LB
+
+ - Public LB IP
+
+ - Static NAT
+
+ - Virtual Machines
+
+ - CIDR
+
+ The following router information is displayed:
+
+ - Private Gateways
+
+ - Public IP Addresses
+
+ - Site-to-Site VPNs
+
+ - Network ACL Lists
+
+#. Select IP Addresses.
+
+ The Public IP Addresses page is displayed.
+
+#. Click Acquire New IP, and click Yes in the confirmation dialog.
+
+ You are prompted for confirmation because, typically, IP addresses
+ are a limited resource. Within a few moments, the new IP address
+ should appear with the state Allocated. You can now use the IP
+ address in port forwarding, load balancing, and static NAT rules.
+
+
+Releasing an IP Address Alloted to a VPC
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The IP address is a limited resource. If you no longer need a particular
+IP, you can disassociate it from its VPC and return it to the pool of
+available addresses. An IP address can be released from its tier, only
+when all the networking ( port forwarding, load balancing, or StaticNAT
+) rules are removed for this IP address. The released IP address will
+still belongs to the same VPC.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+ All the VPCs that you have created for the account is listed in the
+ page.
+
+#. Click the Configure button of the VPC whose IP you want to release.
+
+ The VPC page is displayed where all the tiers you created are listed
+ in a diagram.
+
+ The following options are displayed.
+
+ - Internal LB
+
+ - Public LB IP
+
+ - Static NAT
+
+ - Virtual Machines
+
+ - CIDR
+
+ The following router information is displayed:
+
+ - Private Gateways
+
+ - Public IP Addresses
+
+ - Site-to-Site VPNs
+
+ - Network ACL Lists
+
+#. Select Public IP Addresses.
+
+ The IP Addresses page is displayed.
+
+#. Click the IP you want to release.
+
+#. In the Details tab, click the Release IP button |release-ip-icon.png|
+
+
+.. _enabling-disabling-static-nat-on-vpc:
+
+Enabling or Disabling Static NAT on a VPC
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+A static NAT rule maps a public IP address to the private IP address of
+a VM in a VPC to allow Internet traffic to it. This section tells how to
+enable or disable static NAT for a particular IP address in a VPC.
+
+If port forwarding rules are already in effect for an IP address, you
+cannot enable static NAT to that IP.
+
+If a guest VM is part of more than one network, static NAT rules will
+function only if they are defined on the default network.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+ All the VPCs that you have created for the account is listed in the
+ page.
+
+#. Click the Configure button of the VPC to which you want to deploy the
+ VMs.
+
+ The VPC page is displayed where all the tiers you created are listed
+ in a diagram.
+
+ For each tier, the following options are displayed.
+
+ - Internal LB
+
+ - Public LB IP
+
+ - Static NAT
+
+ - Virtual Machines
+
+ - CIDR
+
+ The following router information is displayed:
+
+ - Private Gateways
+
+ - Public IP Addresses
+
+ - Site-to-Site VPNs
+
+ - Network ACL Lists
+
+#. In the Router node, select Public IP Addresses.
+
+ The IP Addresses page is displayed.
+
+#. Click the IP you want to work with.
+
+#. In the Details tab,click the Static NAT button. |enable-disable.png|
+ The button toggles between Enable and
+ Disable, depending on whether static NAT is currently enabled for the
+ IP address.
+
+#. If you are enabling static NAT, a dialog appears as follows:
+
+ |select-vmstatic-nat.png|
+
+#. Select the tier and the destination VM, then click Apply.
+
+
+Adding Load Balancing Rules on a VPC
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+In a VPC, you can configure two types of load balancing: external LB and
+internal LB. External LB is nothing but a LB rule created to redirect
+the traffic received at a public IP of the VPC virtual router. The
+traffic is load balanced within a tier based on your configuration.
+Citrix NetScaler and VPC virtual router are supported for external LB.
+When you use internal LB service, traffic received at a tier is load
+balanced across different VMs within that tier. For example, traffic
+reached at Web tier is redirected to another VM in that tier. External
+load balancing devices are not supported for internal LB. The service is
+provided by a internal LB VM configured on the target tier.
+
+
+Load Balancing Within a Tier (External LB)
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+A CloudStack user or administrator may create load balancing rules that
+balance traffic received at a public IP to one or more VMs that belong
+to a network tier that provides load balancing service in a VPC. A user
+creates a rule, specifies an algorithm, and assigns the rule to a set of
+VMs within a tier.
+
+
+Enabling NetScaler as the LB Provider on a VPC Tier
+'''''''''''''''''''''''''''''''''''''''''''''''''''
+
+#. Add and enable Netscaler VPX in dedicated mode.
+
+ Netscaler can be used in a VPC environment only if it is in dedicated
+ mode.
+
+#. Create a network offering, as given in ":ref:`create-net-offering-ext-lb`".
+
+#. Create a VPC with Netscaler as the Public LB provider.
+
+ For more information, see `"Adding a Virtual Private
+ Cloud" <#adding-a-virtual-private-cloud>`_.
+
+#. For the VPC, acquire an IP.
+
+#. Create an external load balancing rule and apply, as given in
+ :ref:`create-ext-lb-rule`.
+
+
+.. _create-net-offering-ext-lb:
+
+Creating a Network Offering for External LB
+'''''''''''''''''''''''''''''''''''''''''''
+
+To have external LB support on VPC, create a network offering as
+follows:
+
+#. Log in to the CloudStack UI as a user or admin.
+
+#. From the Select Offering drop-down, choose Network Offering.
+
+#. Click Add Network Offering.
+
+#. In the dialog, make the following choices:
+
+ - **Name**: Any desired name for the network offering.
+
+ - **Description**: A short description of the offering that can be
+ displayed to users.
+
+ - **Network Rate**: Allowed data transfer rate in MB per second.
+
+ - **Traffic Type**: The type of network traffic that will be carried
+ on the network.
+
+ - **Guest Type**: Choose whether the guest network is isolated or
+ shared.
+
+ - **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.
+
+ - **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 :ref: `about-vpc`.
+
+ - **Specify VLAN**: (Isolated guest networks only) Indicate whether
+ a VLAN should be specified when this offering is used.
+
+ - **Supported Services**: Select Load Balancer. Use Netscaler or
+ VpcVirtualRouter.
+
+ - **Load Balancer Type**: Select Public LB from the drop-down.
+
+ - **LB Isolation**: Select Dedicated if Netscaler is used as the
+ external LB provider.
+
+ - **System Offering**: Choose the system service offering that you
+ want virtual routers to use in this network.
+
+ - **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.
+
+#. Click OK and the network offering is created.
+
+
+.. _create-ext-lb-rule:
+
+Creating an External LB Rule
+''''''''''''''''''''''''''''
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+ All the VPCs that you have created for the account is listed in the
+ page.
+
+#. Click the Configure button of the VPC, for which you want to
+ configure load balancing rules.
+
+ The VPC page is displayed where all the tiers you created listed in a
+ diagram.
+
+ For each tier, the following options are displayed:
+
+ - Internal LB
+
+ - Public LB IP
+
+ - Static NAT
+
+ - Virtual Machines
+
+ - CIDR
+
+ The following router information is displayed:
+
+ - Private Gateways
+
+ - Public IP Addresses
+
+ - Site-to-Site VPNs
+
+ - Network ACL Lists
+
+#. In the Router node, select Public IP Addresses.
+
+ The IP Addresses page is displayed.
+
+#. Click the IP address for which you want to create the rule, then
+ click the Configuration tab.
+
+#. In the Load Balancing node of the diagram, click View All.
+
+#. Select the tier to which you want to apply the rule.
+
+#. Specify the following:
+
+ - **Name**: A name for the load balancer rule.
+
+ - **Public Port**: The port that receives the incoming traffic to be
+ balanced.
+
+ - **Private Port**: The port that the VMs will use to receive the
+ traffic.
+
+ - **Algorithm**. Choose the load balancing algorithm you want
+ CloudStack to use. CloudStack supports the following well-known
+ algorithms:
+
+ - Round-robin
+
+ - Least connections
+
+ - Source
+
+ - **Stickiness**. (Optional) Click Configure and choose the
+ algorithm for the stickiness policy. See Sticky Session Policies
+ for Load Balancer Rules.
+
+ - **Add VMs**: Click Add VMs, then select two or more VMs that will
+ divide the load of incoming traffic, and click Apply.
+
+The new load balancing rule appears in the list. You can repeat these
+steps to add more load balancing rules for this IP address.
+
+
+Load Balancing Across Tiers
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+CloudStack supports sharing workload across different tiers within your
+VPC. Assume that multiple tiers are set up in your environment, such as
+Web tier and Application tier. Traffic to each tier is balanced on the
+VPC virtual router on the public side, as explained in
+`"Adding Load Balancing Rules on a VPC" <#adding-load-balancing-rules-on-a-vpc>`_.
+If you want the traffic coming
+from the Web tier to the Application tier to be balanced, use the
+internal load balancing feature offered by CloudStack.
+
+
+How Does Internal LB Work in VPC?
+'''''''''''''''''''''''''''''''''
+
+In this figure, a public LB rule is created for the public IP
+72.52.125.10 with public port 80 and private port 81. The LB rule,
+created on the VPC virtual router, is applied on the traffic coming from
+the Internet to the VMs on the Web tier. On the Application tier two
+internal load balancing rules are created. An internal LB rule for the
+guest IP 10.10.10.4 with load balancer port 23 and instance port 25 is
+configured on the VM, InternalLBVM1. Another internal LB rule for the
+guest IP 10.10.10.4 with load balancer port 45 and instance port 46 is
+configured on the VM, InternalLBVM1. Another internal LB rule for the
+guest IP 10.10.10.6, with load balancer port 23 and instance port 25 is
+configured on the VM, InternalLBVM2.
+
+|vpc-lb.png|
+
+
+Guidelines
+''''''''''
+
+- Internal LB and Public LB are mutually exclusive on a tier. If the
+ tier has LB on the public side, then it can't have the Internal LB.
+
+- Internal LB is supported just on VPC networks in CloudStack 4.2
+ release.
+
+- Only Internal LB VM can act as the Internal LB provider in CloudStack
+ 4.2 release.
+
+- Network upgrade is not supported from the network offering with
+ Internal LB to the network offering with Public LB.
+
+- Multiple tiers can have internal LB support in a VPC.
+
+- Only one tier can have Public LB support in a VPC.
+
+
+Enabling Internal LB on a VPC Tier
+''''''''''''''''''''''''''''''''''
+
+#. Create a network offering, as given in
+ :ref:`creating-net-offering-internal-lb`.
+
+#. Create an internal load balancing rule and apply, as given in
+ :ref:`create-int-lb-rule`.
+
+
+.. _creating-net-offering-internal-lb:
+
+Creating a Network Offering for Internal LB
+'''''''''''''''''''''''''''''''''''''''''''
+
+To have internal LB support on VPC, either use the default offering,
+DefaultIsolatedNetworkOfferingForVpcNetworksWithInternalLB, or create a
+network offering as follows:
+
+#. Log in to the CloudStack UI as a user or admin.
+
+#. From the Select Offering drop-down, choose Network Offering.
+
+#. Click Add Network Offering.
+
+#. In the dialog, make the following choices:
+
+ - **Name**: Any desired name for the network offering.
+
+ - **Description**: A short description of the offering that can be
+ displayed to users.
+
+ - **Network Rate**: Allowed data transfer rate in MB per second.
+
+ - **Traffic Type**: The type of network traffic that will be carried
+ on the network.
+
+ - **Guest Type**: Choose whether the guest network is isolated or
+ shared.
+
+ - **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.
+
+ - **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" <#about-virtual-private-clouds>`_.
+
+ - **Specify VLAN**: (Isolated guest networks only) Indicate whether
+ a VLAN should be specified when this offering is used.
+
+ - **Supported Services**: Select Load Balancer. Select
+ ``InternalLbVM`` from the provider list.
+
+ - **Load Balancer Type**: Select Internal LB from the drop-down.
+
+ - **System Offering**: Choose the system service offering that you
+ want virtual routers to use in this network.
+
+ - **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.
+
+#. Click OK and the network offering is created.
+
+
+.. _create-int-lb-rule:
+
+Creating an Internal LB Rule
+''''''''''''''''''''''''''''
+
+When you create the Internal LB rule and applies to a VM, an Internal LB
+VM, which is responsible for load balancing, is created.
+
+You can view the created Internal LB VM in the Instances page if you
+navigate to **Infrastructure** > **Zones** > <zone\_ name> >
+<physical\_network\_name> > **Network Service Providers** > **Internal
+LB VM**. You can manage the Internal LB VMs as and when required from
+the location.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+ All the VPCs that you have created for the account is listed in the
+ page.
+
+#. Locate the VPC for which you want to configure internal LB, then
+ click Configure.
+
+ The VPC page is displayed where all the tiers you created listed in a
+ diagram.
+
+#. Locate the Tier for which you want to configure an internal LB rule,
+ click Internal LB.
+
+ In the Internal LB page, click Add Internal LB.
+
+#. In the dialog, specify the following:
+
+ - **Name**: A name for the load balancer rule.
+
+ - **Description**: A short description of the rule that can be
+ displayed to users.
+
+ - **Source IP Address**: (Optional) The source IP from which traffic
+ originates. The IP is acquired from the CIDR of that particular
+ tier on which you want to create the Internal LB rule. If not
+ specified, the IP address is automatically allocated from the
+ network CIDR.
+
+ For every Source IP, a new Internal LB VM is created for load
+ balancing.
+
+ - **Source Port**: The port associated with the source IP. Traffic
+ on this port is load balanced.
+
+ - **Instance Port**: The port of the internal LB VM.
+
+ - **Algorithm**. Choose the load balancing algorithm you want
+ CloudStack to use. CloudStack supports the following well-known
+ algorithms:
+
+ - Round-robin
+
+ - Least connections
+
+ - Source
+
+
+Adding a Port Forwarding Rule on a VPC
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+ All the VPCs that you have created for the account is listed in the
+ page.
+
+#. Click the Configure button of the VPC to which you want to deploy the
+ VMs.
+
+ The VPC page is displayed where all the tiers you created are listed
+ in a diagram.
+
+ For each tier, the following options are displayed:
+
+ - Internal LB
+
+ - Public LB IP
+
+ - Static NAT
+
+ - Virtual Machines
+
+ - CIDR
+
+ The following router information is displayed:
+
+ - Private Gateways
+
+ - Public IP Addresses
+
+ - Site-to-Site VPNs
+
+ - Network ACL Lists
+
+#. In the Router node, select Public IP Addresses.
+
+ The IP Addresses page is displayed.
+
+#. Click the IP address for which you want to create the rule, then
+ click the Configuration tab.
+
+#. In the Port Forwarding node of the diagram, click View All.
+
+#. Select the tier to which you want to apply the rule.
+
+#. Specify the following:
+
+ - **Public Port**: The port to which public traffic will be
+ addressed on the IP address you acquired in the previous step.
+
+ - **Private Port**: The port on which the instance is listening for
+ forwarded public traffic.
+
+ - **Protocol**: The communication protocol in use between the two
+ ports.
+
+ - TCP
+
+ - UDP
+
+ - **Add VM**: Click Add VM. Select the name of the instance to which
+ this rule applies, and click Apply.
+
+ You can test the rule by opening an SSH session to the instance.
+
+
+Removing Tiers
+~~~~~~~~~~~~~~
+
+You can remove a tier from a VPC. A removed tier cannot be revoked. When
+a tier is removed, only the resources of the tier are expunged. All the
+network rules (port forwarding, load balancing and staticNAT) and the IP
+addresses associated to the tier are removed. The IP address still be
+belonging to the same VPC.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+ All the VPC that you have created for the account is listed in the
+ page.
+
+#. Click the Configure button of the VPC for which you want to set up
+ tiers.
+
+ The Configure VPC page is displayed. Locate the tier you want to work
+ with.
+
+#. Select the tier you want to remove.
+
+#. In the Network Details tab, click the Delete Network button.
+ |del-tier.png|
+
+ Click Yes to confirm. Wait for some time for the tier to be removed.
+
+
+Editing, Restarting, and Removing a Virtual Private Cloud
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. note:: Ensure that all the tiers are removed before you remove a VPC.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation, choose Network.
+
+#. In the Select view, select VPC.
+
+ All the VPCs that you have created for the account is listed in the
+ page.
+
+#. Select the VPC you want to work with.
+
+#. In the Details tab, click the Remove VPC button |remove-vpc.png|
+
+ You can remove the VPC by also using the remove button in the Quick
+ View.
+
+ You can edit the name and description of a VPC. To do that, select
+ the VPC, then click the Edit button. |vpc-edit-icon.png|
+
+ To restart a VPC, select the VPC, then click the Restart button.
+ |restart-vpc.png|
+
+
+.. |add-vpc.png| image:: /_static/images/add-vpc.png
+ :alt: adding a vpc.
+.. |add-tier.png| image:: /_static/images/add-tier.png
+ :alt: adding a tier to a vpc.
+.. |replace-acl-icon.png| image:: /_static/images/replace-acl-icon.png
+ :alt: button to replace an ACL list
+.. |add-new-gateway-vpc.png| image:: /_static/images/add-new-gateway-vpc.png
+ :alt: adding a private gateway for the VPC.
+.. |add-vm-vpc.png| image:: /_static/images/add-vm-vpc.png
+ :alt: adding a VM to a vpc.
+.. |addvm-tier-sharednw.png| image:: /_static/images/addvm-tier-sharednw.png
+ :alt: adding a VM to a VPC tier and shared network.
+.. |release-ip-icon.png| image:: /_static/images/release-ip-icon.png
+ :alt: button to release an IP.
+.. |enable-disable.png| image:: /_static/images/enable-disable.png
+ :alt: button to enable Static NAT.
+.. |select-vmstatic-nat.png| image:: /_static/images/select-vm-staticnat-vpc.png
+ :alt: selecting a tier to apply staticNAT.
+.. |vpc-lb.png| image:: /_static/images/vpc-lb.png
+ :alt: Configuring internal LB for VPC
+.. |del-tier.png| image:: /_static/images/del-tier.png
+ :alt: button to remove a tier
+.. |vpc-edit-icon.png| image:: /_static/images/edit-icon.png
+ :alt: button to edit.
+.. |remove-vpc.png| image:: /_static/images/remove-vpc.png
+ :alt: button to remove a VPC
+.. |restart-vpc.png| image:: /_static/images/restart-vpc.png
+ :alt: button to restart a VPC
diff --git a/source/adminguide/networking_and_traffic.rst b/source/adminguide/networking_and_traffic.rst
new file mode 100644
index 0000000..33b8231
--- /dev/null
+++ b/source/adminguide/networking_and_traffic.rst
@@ -0,0 +1,81 @@
+.. 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.
+
+
+In a CloudStack, guest VMs can communicate with each other using shared
+infrastructure with the security and user perception that the guests
+have a private LAN. The CloudStack virtual router is the main component
+providing networking features for guest traffic.
+
+.. include:: networking/guest_traffic.rst
+
+.. include:: networking/networking_in_pod.rst
+
+.. include:: networking/networking_in_zone.rst
+
+.. include:: networking/basic_zone_config.rst
+
+.. include:: networking/advanced_zone_config.rst
+
+.. include:: networking/multiple_guest_networks.rst
+
+.. include:: networking/ip_reservation_in_guest_networks.rst
+
+.. include:: networking/public_ips_and_vlans_for_accounts.rst
+
+.. include:: networking/multiple_ips_on_single_nic.rst
+
+.. include:: networking/multiple_ip_ranges.rst
+
+.. include:: networking/elastic_ips.rst
+
+.. include:: networking/portable_ips.rst
+
+.. include:: networking/multiple_subnets_in_shared_network.rst
+
+.. include:: networking/isolation_in_advanced_zone_with_vlan.rst
+
+.. include:: networking/security_groups.rst
+
+.. include:: networking/external_firewalls_and_load_balancers.rst
+
+.. include:: networking/global_server_load_balancing.rst
+
+.. include:: networking/guest_ip_ranges.rst
+
+.. include:: networking/acquiring_an_ip_address.rst
+
+.. include:: networking/releasing_an_ip_address.rst
+
+.. include:: networking/static_nat.rst
+
+.. include:: networking/ip_forwarding_and_firewalling.rst
+
+.. include:: networking/ip_load_balancing.rst
+
+.. include:: networking/dns_and_dhcp.rst
+
+.. include:: networking/remote_access_vpn.rst
+
+.. include:: networking/site_to_site_vpn.rst
+
+.. include:: networking/inter_vlan_routing.rst
+
+.. include:: networking/virtual_private_cloud_config.rst
+
+.. include:: networking/persistent_networks.rst
+
+.. include:: networking/palo_alto_config.rst
+
diff --git a/source/adminguide/projects.rst b/source/adminguide/projects.rst
new file mode 100644
index 0000000..010c3c3
--- /dev/null
+++ b/source/adminguide/projects.rst
@@ -0,0 +1,428 @@
+.. 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.
+
+
+Overview of Projects
+--------------------
+
+Projects are used to organize people and resources. CloudStack users
+within a single domain can group themselves into project teams so they
+can collaborate and share virtual resources such as VMs, snapshots,
+templates, data disks, and IP addresses. CloudStack tracks resource
+usage per project as well as per user, so the usage can be billed to
+either a user account or a project. For example, a private cloud within
+a software company might have all members of the QA department assigned
+to one project, so the company can track the resources used in testing
+while the project members can more easily isolate their efforts from
+other users of the same cloud
+
+You can configure CloudStack to allow any user to create a new project,
+or you can restrict that ability to just CloudStack administrators. Once
+you have created a project, you become that project’s administrator, and
+you can add others within your domain to the project. CloudStack can be
+set up either so that you can add people directly to a project, or so
+that you have to send an invitation which the recipient must accept.
+Project members can view and manage all virtual resources created by
+anyone in the project (for example, share VMs). A user can be a member
+of any number of projects and can switch views in the CloudStack UI to
+show only project-related information, such as project VMs, fellow
+project members, project-related alerts, and so on.
+
+The project administrator can pass on the role to another project
+member. The project administrator can also add more members, remove
+members from the project, set new resource limits (as long as they are
+below the global defaults set by the CloudStack administrator), and
+delete the project. When the administrator removes a member from the
+project, resources created by that user, such as VM instances, remain
+with the project. This brings us to the subject of resource ownership
+and which resources can be used by a project.
+
+Resources created within a project are owned by the project, not by any
+particular CloudStack account, and they can be used only within the
+project. A user who belongs to one or more projects can still create
+resources outside of those projects, and those resources belong to the
+user’s account; they will not be counted against the project’s usage or
+resource limits. You can create project-level networks to isolate
+traffic within the project and provide network services such as port
+forwarding, load balancing, VPN, and static NAT. A project can also make
+use of certain types of resources from outside the project, if those
+resources are shared. For example, a shared network or public template
+is available to any project in the domain. A project can get access to a
+private template if the template’s owner will grant permission. A
+project can use any service offering or disk offering available in its
+domain; however, you can not create private service and disk offerings
+at the project level..
+
+
+Configuring Projects
+--------------------
+
+Before CloudStack users start using projects, the CloudStack
+administrator must set up various systems to support them, including
+membership invitations, limits on project resources, and controls on who
+can create projects.
+
+
+Setting Up Invitations
+~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack can be set up either so that project administrators can add
+people directly to a project, or so that it is necessary to send an
+invitation which the recipient must accept. The invitation can be sent
+by email or through the user’s CloudStack account. If you want
+administrators to use invitations to add members to projects, turn on
+and set up the invitations feature in CloudStack.
+
+#. Log in as administrator to the CloudStack UI.
+
+#. In the left navigation, click Global Settings.
+
+#. In the search box, type project and click the search button.
+ |Searches projects|
+
+#. In the search results, you can see a few other parameters you need to
+ set to control how invitations behave. The table below shows global
+ configuration parameters related to project invitations. Click the
+ edit button to set each parameter.
+
+ .. cssclass:: table-striped table-bordered table-hover
+
+ +----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+
+ | Configuration Parameters | Description |
+ +============================+=======================================================================================================================================================+
+ | project.invite.required | Set to true to turn on the invitations feature. |
+ +----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+
+ | project.email.sender | The email address to show in the From field of invitation emails. |
+ +----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+
+ | project.invite.timeout | Amount of time to allow for a new member to respond to the invitation. |
+ +----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+
+ | project.smtp.host | Name of the host that acts as an email server to handle invitations. |
+ +----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+
+ | project.smtp.password | (Optional) Password required by the SMTP server. You must also set project.smtp.username and set project.smtp.useAuth to true. |
+ +----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+
+ | project.smtp.port | SMTP server’s listening port. |
+ +----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+
+ | project.smtp.useAuth | Set to true if the SMTP server requires a username and password. |
+ +----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+
+ | project.smtp.username | (Optional) User name required by the SMTP server for authentication. You must also set project.smtp.password and set project.smtp.useAuth to true.. |
+ +----------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------+
+
+#. Restart the Management Server:
+
+ .. code:: bash
+
+ service cloudstack-management restart
+
+Setting Resource Limits for Projects
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The CloudStack administrator can set global default limits to control
+the amount of resources that can be owned by each project in the cloud.
+This serves to prevent uncontrolled usage of resources such as
+snapshots, IP addresses, and virtual machine instances. Domain
+administrators can override these resource limits for individual
+projects with their domains, as long as the new limits are below the
+global defaults set by the CloudStack root administrator. The root
+administrator can also set lower resource limits for any project in the
+cloud
+
+Setting Per-Project Resource Limits
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The CloudStack root administrator or the domain administrator of the
+domain where the project resides can set new resource limits for an
+individual project. The project owner can set resource limits only if
+the owner is also a domain or root administrator.
+
+The new limits must be below the global default limits set by the
+CloudStack administrator (as described in `“Setting
+Resource Limits for Projects” <#setting-resource-limits-for-projects>`_).
+If the project already owns more of a given type of resource than the
+new maximum, the resources are not affected; however, the project can
+not add any new resources of that type until the total drops below the
+new limit.
+
+#. Log in as administrator to the CloudStack UI.
+
+#. In the left navigation, click Projects.
+
+#. In Select View, choose Projects.
+
+#. Click the name of the project you want to work with.
+
+#. Click the Resources tab. This tab lists the current maximum amount
+ that the project is allowed to own for each type of resource.
+
+#. Type new values for one or more resources.
+
+#. Click Apply.
+
+
+Setting the Global Project Resource Limits
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. Log in as administrator to the CloudStack UI.
+
+#. In the left navigation, click Global Settings.
+
+#. In the search box, type max.projects and click the search button.
+
+#. In the search results, you will see the parameters you can use to set
+ per-project maximum resource amounts that apply to all projects in
+ the cloud. No project can have more resources, but an individual
+ project can have lower limits. Click the edit button to set each
+ parameter. |Edits parameters|
+
+ .. cssclass:: table-striped table-bordered table-hover
+
+ +--------------------------+------------------------------------------------------------------------------------------------------------------------------+
+ | max.project.public.ips | Maximum number of public IP addresses that can be owned by any project in the cloud. See About Public IP Addresses. |
+ +--------------------------+------------------------------------------------------------------------------------------------------------------------------+
+ | max.project.snapshots | Maximum number of snapshots that can be owned by any project in the cloud. See Working with Snapshots. |
+ +--------------------------+------------------------------------------------------------------------------------------------------------------------------+
+ | max.project.templates | Maximum number of templates that can be owned by any project in the cloud. See Working with Templates. |
+ +--------------------------+------------------------------------------------------------------------------------------------------------------------------+
+ | max.project.uservms | Maximum number of guest virtual machines that can be owned by any project in the cloud. See Working With Virtual Machines. |
+ +--------------------------+------------------------------------------------------------------------------------------------------------------------------+
+ | max.project.volumes | Maximum number of data volumes that can be owned by any project in the cloud. See Working with Volumes. |
+ +--------------------------+------------------------------------------------------------------------------------------------------------------------------+
+
+
+#. Restart the Management Server.
+
+ .. code:: bash
+
+ # service cloudstack-management restart
+
+Setting Project Creator Permissions
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can configure CloudStack to allow any user to create a new project,
+or you can restrict that ability to just CloudStack administrators.
+
+#. Log in as administrator to the CloudStack UI.
+
+#. In the left navigation, click Global Settings.
+
+#. In the search box, type allow.user.create.projects.
+
+#. Click the edit button to set the parameter. |Edits parameters|
+
+ ``allow.user.create.projects``
+
+ Set to true to allow end users to create projects. Set to false if
+ you want only the CloudStack root administrator and domain
+ administrators to create projects.
+
+#. Restart the Management Server.
+
+ .. code:: bash
+
+ # service cloudstack-management restart
+
+
+Creating a New Project
+----------------------
+
+CloudStack administrators and domain administrators can create projects.
+If the global configuration parameter allow.user.create.projects is set
+to true, end users can also create projects.
+
+#. Log in as administrator to the CloudStack UI.
+
+#. In the left navigation, click Projects.
+
+#. In Select view, click Projects.
+
+#. Click New Project.
+
+#. Give the project a name and description for display to users, then
+ click Create Project.
+
+#. A screen appears where you can immediately add more members to the
+ project. This is optional. Click Next when you are ready to move on.
+
+#. Click Save.
+
+
+Adding Members to a Project
+---------------------------
+
+New members can be added to a project by the project’s administrator,
+the domain administrator of the domain where the project resides or any
+parent domain, or the CloudStack root administrator. There are two ways
+to add members in CloudStack, but only one way is enabled at a time:
+
+- If invitations have been enabled, you can send invitations to new
+ members.
+
+- If invitations are not enabled, you can add members directly through
+ the UI.
+
+
+Sending Project Membership Invitations
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Use these steps to add a new member to a project if the invitations
+feature is enabled in the cloud as described in `“Setting
+Up Invitations” <#setting-up-invitations>`_. If the invitations feature is
+not turned on, use the procedure in Adding Project Members From the UI.
+
+#. Log in to the CloudStack UI.
+
+#. In the left navigation, click Projects.
+
+#. In Select View, choose Projects.
+
+#. Click the name of the project you want to work with.
+
+#. Click the Invitations tab.
+
+#. In Add by, select one of the following:
+
+ #. Account – The invitation will appear in the user’s Invitations tab
+ in the Project View. See Using the Project View.
+
+ #. Email – The invitation will be sent to the user’s email address.
+ Each emailed invitation includes a unique code called a token
+ which the recipient will provide back to CloudStack when accepting
+ the invitation. Email invitations will work only if the global
+ parameters related to the SMTP server have been set. See
+ `“Setting Up Invitations” <#setting-up-invitations>`_.
+
+#. Type the user name or email address of the new member you want to
+ add, and click Invite. Type the CloudStack user name if you chose
+ Account in the previous step. If you chose Email, type the email
+ address. You can invite only people who have an account in this cloud
+ within the same domain as the project. However, you can send the
+ invitation to any email address.
+
+#. To view and manage the invitations you have sent, return to this tab.
+ When an invitation is accepted, the new member will appear in the
+ project’s Accounts tab.
+
+
+Adding Project Members From the UI
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The steps below tell how to add a new member to a project if the
+invitations feature is not enabled in the cloud. If the invitations
+feature is enabled cloud,as described in `“Setting Up
+Invitations” <#setting-up-invitations>`_, use the procedure in
+`“Sending Project Membership
+Invitations” <#sending-project-membership-invitations>`_.
+
+#. Log in to the CloudStack UI.
+
+#. In the left navigation, click Projects.
+
+#. In Select View, choose Projects.
+
+#. Click the name of the project you want to work with.
+
+#. Click the Accounts tab. The current members of the project are
+ listed.
+
+#. Type the account name of the new member you want to add, and click
+ Add Account. You can add only people who have an account in this
+ cloud and within the same domain as the project.
+
+
+Accepting a Membership Invitation
+---------------------------------
+
+If you have received an invitation to join a CloudStack project, and you
+want to accept the invitation, follow these steps:
+
+#. Log in to the CloudStack UI.
+
+#. In the left navigation, click Projects.
+
+#. In Select View, choose Invitations.
+
+#. If you see the invitation listed onscreen, click the Accept button.
+
+ Invitations listed on screen were sent to you using your CloudStack
+ account name.
+
+#. If you received an email invitation, click the Enter Token button,
+ and provide the project ID and unique ID code (token) from the email.
+
+
+Suspending or Deleting a Project
+--------------------------------
+
+When a project is suspended, it retains the resources it owns, but they
+can no longer be used. No new resources or members can be added to a
+suspended project.
+
+When a project is deleted, its resources are destroyed, and member
+accounts are removed from the project. The project’s status is shown as
+Disabled pending final deletion.
+
+A project can be suspended or deleted by the project administrator, the
+domain administrator of the domain the project belongs to or of its
+parent domain, or the CloudStack root administrator.
+
+#. Log in to the CloudStack UI.
+
+#. In the left navigation, click Projects.
+
+#. In Select View, choose Projects.
+
+#. Click the name of the project.
+
+#. Click one of the buttons:
+
+ To delete, use |Removes a project|
+
+ To suspend, use |Suspends a project|
+
+
+Using the Project View
+----------------------
+
+If you are a member of a project, you can use CloudStack’s project view
+to see project members, resources consumed, and more. The project view
+shows only information related to one project. It is a useful way to
+filter out other information so you can concentrate on a project status
+and resources.
+
+#. Log in to the CloudStack UI.
+
+#. Click Project View.
+
+#. The project dashboard appears, showing the project’s VMs, volumes,
+ users, events, network settings, and more. From the dashboard, you
+ can:
+
+ - Click the Accounts tab to view and manage project members. If you
+ are the project administrator, you can add new members, remove
+ members, or change the role of a member from user to admin. Only
+ one member at a time can have the admin role, so if you set
+ another user’s role to admin, your role will change to regular
+ user.
+
+ - (If invitations are enabled) Click the Invitations tab to view and
+ manage invitations that have been sent to new project members but
+ not yet accepted. Pending invitations will remain in this list
+ until the new member accepts, the invitation timeout is reached,
+ or you cancel the invitation.
+
+
+.. |Edits Parameters| image:: /_static/images/edit-icon.png
+.. |Searches projects| image:: /_static/images/search-button.png
+.. |Removes a project| image:: /_static/images/delete-button.png
+.. |Suspends a project| image:: /_static/images/suspend-icon.png
diff --git a/source/adminguide/reliability.rst b/source/adminguide/reliability.rst
new file mode 100644
index 0000000..44647cb
--- /dev/null
+++ b/source/adminguide/reliability.rst
@@ -0,0 +1,261 @@
+.. 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.
+
+
+HA for Management Server
+------------------------
+
+The CloudStack Management Server should be deployed in a multi-node
+configuration such that it is not susceptible to individual server
+failures. The Management Server itself (as distinct from the MySQL
+database) is stateless and may be placed behind a load balancer.
+
+Normal operation of Hosts is not impacted by an outage of all Management
+Serves. All guest VMs will continue to work.
+
+When the Management Server is down, no new VMs can be created, and the
+end user and admin UI, API, dynamic load distribution, and HA will cease
+to work.
+
+.. _management-server-load-balancing:
+
+Management Server Load Balancing
+--------------------------------
+
+CloudStack can use a load balancer to provide a virtual IP for multiple
+Management Servers. The administrator is responsible for creating the
+load balancer rules for the Management Servers. The application requires
+persistence or stickiness across multiple sessions. The following chart
+lists the ports that should be load balanced and whether or not
+persistence is required.
+
+Even if persistence is not required, enabling it is permitted.
+
+.. cssclass:: table-striped table-bordered table-hover
+
+============== ======================== ================ =====================
+Source Port Destination Port Protocol Persistence Required?
+============== ======================== ================ =====================
+80 or 443 8080 (or 20400 with AJP) HTTP (or AJP) Yes
+8250 8250 TCP Yes
+8096 8096 HTTP No
+============== ======================== ================ =====================
+
+In addition to above settings, the administrator is responsible for
+setting the 'host' global config value from the management server IP to
+load balancer virtual IP address. If the 'host' value is not set to the
+VIP for Port 8250 and one of your management servers crashes, the UI is
+still available but the system VMs will not be able to contact the
+management server.
+
+
+HA-Enabled Virtual Machines
+---------------------------
+
+The user can specify a virtual machine as HA-enabled. By default, all
+virtual router VMs and Elastic Load Balancing VMs are automatically
+configured as HA-enabled. When an HA-enabled VM crashes, CloudStack
+detects the crash and restarts the VM automatically within the same
+Availability Zone. HA is never performed across different Availability
+Zones. CloudStack has a conservative policy towards restarting VMs and
+ensures that there will never be two instances of the same VM running at
+the same time. The Management Server attempts to start the VM on another
+Host in the same cluster.
+
+HA features work with iSCSI or NFS primary storage. HA with local
+storage is not supported.
+
+
+HA for Hosts
+------------
+
+The user can specify a virtual machine as HA-enabled. By default, all
+virtual router VMs and Elastic Load Balancing VMs are automatically
+configured as HA-enabled. When an HA-enabled VM crashes, CloudStack
+detects the crash and restarts the VM automatically within the same
+Availability Zone. HA is never performed across different Availability
+Zones. CloudStack has a conservative policy towards restarting VMs and
+ensures that there will never be two instances of the same VM running at
+the same time. The Management Server attempts to start the VM on another
+Host in the same cluster.
+
+HA features work with iSCSI or NFS primary storage. HA with local
+storage is not supported.
+
+
+Dedicated HA Hosts
+~~~~~~~~~~~~~~~~~~
+
+One or more hosts can be designated for use only by HA-enabled VMs that
+are restarting due to a host failure. Setting up a pool of such
+dedicated HA hosts as the recovery destination for all HA-enabled VMs is
+useful to:
+
+- Make it easier to determine which VMs have been restarted as part of
+ the CloudStack high-availability function. If a VM is running on a
+ dedicated HA host, then it must be an HA-enabled VM whose original
+ host failed. (With one exception: It is possible for an administrator
+ to manually migrate any VM to a dedicated HA host.).
+
+- Keep HA-enabled VMs from restarting on hosts which may be reserved
+ for other purposes.
+
+The dedicated HA option is set through a special host tag when the host
+is created. To allow the administrator to dedicate hosts to only
+HA-enabled VMs, set the global configuration variable ha.tag to the
+desired tag (for example, "ha\_host"), and restart the Management
+Server. Enter the value in the Host Tags field when adding the host(s)
+that you want to dedicate to HA-enabled VMs.
+
+.. note::
+ If you set ha.tag, be sure to actually use that tag on at least one
+ host in your cloud. If the tag specified in ha.tag is not set for
+ any host in the cloud, the HA-enabled VMs will fail to restart after
+ a crash.
+
+
+Primary Storage Outage and Data Loss
+------------------------------------
+
+When a primary storage outage occurs the hypervisor immediately stops
+all VMs stored on that storage device. Guests that are marked for HA
+will be restarted as soon as practical when the primary storage comes
+back on line. With NFS, the hypervisor may allow the virtual machines to
+continue running depending on the nature of the issue. For example, an
+NFS hang will cause the guest VMs to be suspended until storage
+connectivity is restored.Primary storage is not designed to be backed
+up. Individual volumes in primary storage can be backed up using
+snapshots.
+
+
+Secondary Storage Outage and Data Loss
+--------------------------------------
+
+For a Zone that has only one secondary storage server, a secondary
+storage outage will have feature level impact to the system but will not
+impact running guest VMs. It may become impossible to create a VM with
+the selected template for a user. A user may also not be able to save
+snapshots or examine/restore saved snapshots. These features will
+automatically be available when the secondary storage comes back online.
+
+Secondary storage data loss will impact recently added user data
+including templates, snapshots, and ISO images. Secondary storage should
+be backed up periodically. Multiple secondary storage servers can be
+provisioned within each zone to increase the scalability of the system.
+
+
+Database High Availability
+--------------------------
+
+To help ensure high availability of the databases that store the
+internal data for CloudStack, you can set up database replication. This
+covers both the main CloudStack database and the Usage database.
+Replication is achieved using the MySQL connector parameters and two-way
+replication. Tested with MySQL 5.1 and 5.5.
+
+
+How to Set Up Database Replication
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Database replication in CloudStack is provided using the MySQL
+replication capabilities. The steps to set up replication can be found
+in the MySQL documentation (links are provided below). It is suggested
+that you set up two-way replication, which involves two database nodes.
+In this case, for example, you might have node1 and node2.
+
+You can also set up chain replication, which involves more than two
+nodes. In this case, you would first set up two-way replication with
+node1 and node2. Next, set up one-way replication from node2 to node3.
+Then set up one-way replication from node3 to node4, and so on for all
+the additional nodes.
+
+References:
+
+- `http://dev.mysql.com/doc/refman/5.0/en/replication-howto.html <http://dev.mysql.com/doc/refman/5.0/en/replication-howto.html>`_
+
+- `https://wikis.oracle.com/display/CommSuite/MySQL+High+Availability+and+Replication+Information+For+Calendar+Server <https://wikis.oracle.com/display/CommSuite/MySQL+High+Availability+and+Replication+Information+For+Calendar+Server>`_
+
+
+Configuring Database High Availability
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To control the database high availability behavior, use the following
+configuration settings in the file
+/etc/cloudstack/management/db.properties.
+
+**Required Settings**
+
+Be sure you have set the following in db.properties:
+
+- ``db.ha.enabled``: set to true if you want to use the replication
+ feature.
+
+ Example: ``db.ha.enabled=true``
+
+- ``db.cloud.slaves``: set to a comma-delimited set of slave hosts for the
+ cloud database. This is the list of nodes set up with replication.
+ The master node is not in the list, since it is already mentioned
+ elsewhere in the properties file.
+
+ Example: ``db.cloud.slaves=node2,node3,node4``
+
+- ``db.usage.slaves``: set to a comma-delimited set of slave hosts for the
+ usage database. This is the list of nodes set up with replication.
+ The master node is not in the list, since it is already mentioned
+ elsewhere in the properties file.
+
+ Example: ``db.usage.slaves=node2,node3,node4``
+
+**Optional Settings**
+
+The following settings must be present in db.properties, but you are not
+required to change the default values unless you wish to do so for
+tuning purposes:
+
+- ``db.cloud.secondsBeforeRetryMaster``: The number of seconds the MySQL
+ connector should wait before trying again to connect to the master
+ after the master went down. Default is 1 hour. The retry might happen
+ sooner if db.cloud.queriesBeforeRetryMaster is reached first.
+
+ Example: ``db.cloud.secondsBeforeRetryMaster=3600``
+
+- ``db.cloud.queriesBeforeRetryMaster``: The minimum number of queries to
+ be sent to the database before trying again to connect to the master
+ after the master went down. Default is 5000. The retry might happen
+ sooner if db.cloud.secondsBeforeRetryMaster is reached first.
+
+ Example: ``db.cloud.queriesBeforeRetryMaster=5000``
+
+- ``db.cloud.initialTimeout``: Initial time the MySQL connector should wait
+ before trying again to connect to the master. Default is 3600.
+
+ Example: ``db.cloud.initialTimeout=3600``
+
+
+Limitations on Database High Availability
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The following limitations exist in the current implementation of this
+feature.
+
+- Slave hosts can not be monitored through CloudStack. You will need to
+ have a separate means of monitoring.
+
+- Events from the database side are not integrated with the CloudStack
+ Management Server events system.
+
+- You must periodically perform manual clean-up of bin log files
+ generated by replication on database nodes. If you do not clean up
+ the log files, the disk can become full.
diff --git a/source/adminguide/service_offerings.rst b/source/adminguide/service_offerings.rst
new file mode 100644
index 0000000..01bb76e
--- /dev/null
+++ b/source/adminguide/service_offerings.rst
@@ -0,0 +1,647 @@
+.. 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.
+
+
+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.
+
+
+Compute and Disk Service Offerings
+----------------------------------
+
+A service offering is a set of virtual hardware features such as CPU
+core count and speed, memory, and disk size. The CloudStack administrator
+can set up various offerings, and then end users choose from the
+available offerings when they create a new VM. Based on the user’s
+selected offering, CloudStack emits usage records that can be integrated
+with billing systems.
+
+Some characteristics of service offerings must be defined by the CloudStack
+administrator, and others can be left undefined so that the end-user can
+enter their own desired values. This is useful to reduce the number of
+offerings the CloudStack administrator has to define. Instead of defining a
+compute offering for every imaginable combination of values that a user
+might want, the administrator can define offerings that provide some
+flexibility to the users and can serve as the basis for several
+different VM configurations.
+
+A service offering includes the following elements:
+
+- CPU, memory, and network resource guarantees
+
+- How resources are metered
+
+- How the resource usage is charged
+
+- How often the charges are generated
+
+For example, one service offering might allow users to create a virtual
+machine instance that is equivalent to a 1 GHz Intel® Core™ 2 CPU, with
+1 GB memory at $0.20/hour, with network traffic metered at $0.10/GB.
+
+CloudStack separates service offerings into compute offerings and disk
+offerings. The compute service offering specifies:
+
+- Guest CPU (optional). If not defined by the CloudStack administrator,
+ users can pick the CPU attributes.
+
+- Guest RAM (optional). If not defined by the CloudStack administrator,
+ users can pick the RAM.
+
+- Guest Networking type (virtual or direct)
+
+- Tags on the root disk
+
+The disk offering specifies:
+
+- Disk size (optional). If not defined by the CloudStack administrator,
+ users can pick the disk size.
+
+- Tags on the data disk
+
+
+Custom Compute Offering
+~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack provides you the flexibility to specify the desired values for
+the number of CPU, CPU speed, and memory while deploying a VM. As an
+admin, you create a Compute Offering by marking it as custom, and the
+users will be able to customize this dynamic Compute Offering by
+specifying the memory, and CPU at the time of VM creation or upgrade.
+Custom Compute Offering is same as the normal Compute Offering except
+that the values of the dynamic parameters will be set to zeros in the
+given set of templates. Use this offering to deploy VM by specifying
+custom values for the dynamic parameters. Memory, CPU and number of CPUs
+are considered as dynamic parameters.
+
+Dynamic Compute Offerings can be used in following cases: deploying a
+VM, changing the compute offering of a stopped VM and running VMs, which
+is nothing but scaling up. To support this feature a new field, Custom,
+has been added to the Create Compute Offering page. If the Custom field
+is checked, the user will be able to create a custom Compute Offering by
+filling in the desired values for number of CPU, CPU speed, and memory.
+See ? for more information on this.
+
+*Recording Usage Events for Dynamically Assigned Resources*.
+
+To support this feature, usage events has been enhanced to register
+events for dynamically assigned resources. Usage events are registered
+when a VM is created from a custom compute offering, and upon changing
+the compute offering of a stopped or running VM. The values of the
+parameters, such as CPU, speed, RAM are recorded.
+
+
+Creating a New Compute Offering
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To create a new compute offering:
+
+#. Log in with admin privileges to the CloudStack UI.
+
+#. In the left navigation bar, click Service Offerings.
+
+#. In Select Offering, choose Compute Offering.
+
+#. Click Add Compute Offering.
+
+#. In the dialog, make the following choices:
+
+ - **Name**: Any desired name for the service offering.
+
+ - **Description**: A short description of the offering that can be
+ displayed to users
+
+ - **Storage type**: The type of disk that should be allocated. Local
+ allocates from storage attached directly to the host where the
+ system VM is running. Shared allocates from storage accessible via
+ NFS.
+
+ - **Custom**: Custom compute offerings can be used in following
+ cases: deploying a VM, changing the compute offering of a stopped
+ VM and running VMs, which is nothing but scaling up.
+
+ If the Custom field is checked, the end-user must fill in the
+ desired values for number of CPU, CPU speed, and RAM Memory when
+ using a custom compute offering. When you check this box, those
+ three input fields are hidden in the dialog box.
+
+ - **# of CPU cores**: The number of cores which should be allocated
+ to a system VM with this offering. If Custom is checked, this
+ field does not appear.
+
+ - **CPU (in MHz)**: The CPU speed of the cores that the system VM is
+ allocated. For example, “2000” would provide for a 2 GHz clock. If
+ Custom is checked, this field does not appear.
+
+ - **Memory (in MB)**: The amount of memory in megabytes that the
+ system VM should be allocated. For example, “2048” would provide
+ for a 2 GB RAM allocation. If Custom is checked, this field does
+ not appear.
+
+ - **Network Rate**: Allowed data transfer rate in MB per second.
+
+ - **Disk Read Rate**: Allowed disk read rate in bits per second.
+
+ - **Disk Write Rate**: Allowed disk write rate in bits per second.
+
+ - **Disk Read Rate**: Allowed disk read rate in IOPS (input/output
+ operations per second).
+
+ - **Disk Write Rate**: Allowed disk write rate in IOPS (input/output
+ operations per second).
+
+ - **Offer HA**: If yes, the administrator can choose to have the
+ system VM be monitored and as highly available as possible.
+
+ - **QoS Type**: Three options: Empty (no Quality of Service), hypervisor
+ (rate limiting enforced on the hypervisor side), and storage
+ (guaranteed minimum and maximum IOPS enforced on the storage
+ side). If leveraging QoS, make sure that the hypervisor or storage
+ system supports this feature.
+
+ - **Custom IOPS**: If checked, the user can set their own IOPS. If not
+ checked, the root administrator can define values. If the root
+ admin does not set values when using storage QoS, default values
+ are used (the defauls can be overridden if the proper parameters
+ are passed into CloudStack when creating the primary storage in
+ question).
+
+ - **Min IOPS**: Appears only if storage QoS is to be used. Set a
+ guaranteed minimum number of IOPS to be enforced on the storage
+ side.
+
+ - **Max IOPS**: Appears only if storage QoS is to be used. Set a maximum
+ number of IOPS to be enforced on the storage side (the system may
+ go above this limit in certain circumstances for short intervals).
+
+ - **Hypervisor Snapshot Reserve**: For managed storage only. This is
+ a value that is a percentage of the size of the root disk. For example:
+ if the root disk is 20 GB and Hypervisor Snapshot Reserve is 200%, the
+ storage volume that backs the storage repository (XenServer) or
+ datastore (VMware) in question is sized at 60 GB (20 GB + (20 GB * 2)).
+ This enables space for hypervisor snapshots in addition to the virtual
+ disk that represents the root disk. This does not apply for KVM.
+
+ - **Storage Tags**: The tags that should be associated with the
+ primary storage used by the system VM.
+
+ - **Host Tags**: (Optional) Any tags that you use to organize your
+ hosts
+
+ - **CPU cap**: Whether to limit the level of CPU usage even if spare
+ capacity is available.
+
+ - **Public**: Indicate whether the service offering should be
+ available all domains or only some domains. Choose Yes to make it
+ available to all domains. Choose No to limit the scope to a
+ subdomain; CloudStack will then prompt for the subdomain's name.
+
+ - **isVolatile**: If checked, VMs created from this service offering
+ will have their root disks reset upon reboot. This is useful for
+ secure environments that need a fresh start on every boot and for
+ desktops that should not retain state.
+
+ - **Deployment Planner**: Choose the technique that you would like
+ CloudStack to use when deploying VMs based on this service
+ offering.
+
+ First Fit places new VMs on the first host that is found having
+ sufficient capacity to support the VM's requirements.
+
+ User Dispersing makes the best effort to evenly distribute VMs
+ belonging to the same account on different clusters or pods.
+
+ User Concentrated prefers to deploy VMs belonging to the same
+ account within a single pod.
+
+ Implicit Dedication will deploy VMs on private infrastructure that
+ is dedicated to a specific domain or account. If you choose this
+ planner, then you must also pick a value for Planner Mode. See
+ `“Dedicating Resources to Accounts and Domains”
+ <accounts.html#dedicating-resources-to-accounts-and-domains>`_.
+
+ Bare Metal is used with bare metal hosts. See Bare Metal
+ Installation in the Installation Guide.
+
+ - **Planner Mode**: Used when ImplicitDedicationPlanner is selected
+ in the previous field. The planner mode determines how VMs will be
+ deployed on private infrastructure that is dedicated to a single
+ domain or account.
+
+ Strict: 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: The VM will be deployed in dedicated infrastructure if
+ possible. Otherwise, the VM can be deployed in shared
+ infrastructure.
+
+ - **GPU**: Assign a physical GPU(GPU-passthrough) or a portion of a physicalGPU
+ GPU card(vGPU) to the guest VM. It allows graphical applications to run on the VM.
+ Select the card from the supported list of cards.
+
+ The options given are NVIDIA GRID K1 and NVIDIA GRID K2. These are vGPU
+ capable cards that allow multiple vGPUs on a single physical GPU. If you
+ want to use a card other than these, follow the instructions in the
+ **"GPU and vGPU support for CloudStack Guest VMs"** page in the
+ Cloudstack Version 4.4 Design Docs found in the Cloudstack Wiki.
+
+ - **vGPU Type**: Represents the type of virtual GPU to be assigned to a
+ guest VM. In this case, only a portion of a physical GPU card (vGPU) is
+ assigned to the guest VM.
+
+ Additionally, the **passthrough vGPU** type is defined to represent a physical GPU
+ device. A **passthrough vGPU** can directly be assigned to a single guest VM.
+ In this case, a physical GPU device is exclusively allotted to a single
+ guest VM.
+
+
+#. Click Add.
+
+
+Creating a New Disk Offering
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To create a new disk offering:
+
+#. Log in with admin privileges to the CloudStack UI.
+
+#. In the left navigation bar, click Service Offerings.
+
+#. In Select Offering, choose Disk Offering.
+
+#. Click Add Disk Offering.
+
+#. In the dialog, make the following choices:
+
+ - **Name**: Any desired name for the disk offering.
+
+ - **Description**: A short description of the offering that can be
+ displayed to users
+
+ - **Custom Disk Size**: If checked, the user can set their own disk
+ size. If not checked, the root administrator must define a value
+ in Disk Size.
+
+ - **Disk Size**: Appears only if Custom Disk Size is not selected.
+ Define the volume size in GB (2^30 1GB = 1,073,741,824 Bytes).
+
+ - **QoS Type**: Three options: Empty (no Quality of Service), hypervisor
+ (rate limiting enforced on the hypervisor side), and storage
+ (guaranteed minimum and maximum IOPS enforced on the storage
+ side). If leveraging QoS, make sure that the hypervisor or storage
+ system supports this feature.
+
+ - **Custom IOPS**: If checked, the user can set their own IOPS. If not
+ checked, the root administrator can define values. If the root
+ admin does not set values when using storage QoS, default values
+ are used (the defauls can be overridden if the proper parameters
+ are passed into CloudStack when creating the primary storage in
+ question).
+
+ - **Min IOPS**: Appears only if storage QoS is to be used. Set a
+ guaranteed minimum number of IOPS to be enforced on the storage
+ side.
+
+ - **Max IOPS**: Appears only if storage QoS is to be used. Set a maximum
+ number of IOPS to be enforced on the storage side (the system may
+ go above this limit in certain circumstances for short intervals).
+
+ - **Hypervisor Snapshot Reserve**: For managed storage only. This is
+ a value that is a percentage of the size of the data disk. For example:
+ if the data disk is 20 GB and Hypervisor Snapshot Reserve is 200%, the
+ storage volume that backs the storage repository (XenServer) or
+ datastore (VMware) in question is sized at 60 GB (20 GB + (20 GB * 2)).
+ This enables space for hypervisor snapshots in addition to the virtual
+ disk that represents the data disk. This does not apply for KVM.
+
+ - **(Optional)Storage Tags**: The tags that should be associated with
+ the primary storage for this disk. Tags are a comma separated list
+ of attributes of the storage. For example "ssd,blue". Tags are
+ also added on Primary Storage. CloudStack matches tags on a disk
+ offering to tags on the storage. If a tag is present on a disk
+ offering that tag (or tags) must also be present on Primary
+ Storage for the volume to be provisioned. If no such primary
+ storage exists, allocation from the disk offering will fail..
+
+ - **Public**: Indicate whether the service offering should be available
+ all domains or only some domains. Choose Yes to make it available
+ to all domains. Choose No to limit the scope to a subdomain;
+ CloudStack will then prompt for the subdomain's name.
+
+#. Click Add.
+
+
+Modifying or Deleting a Service Offering
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Service offerings cannot be changed once created. This applies to both
+compute offerings and disk offerings.
+
+A service offering can be deleted. If it is no longer in use, it is
+deleted immediately and permanently. If the service offering is still in
+use, it will remain in the database until all the virtual machines
+referencing it have been deleted. After deletion by the administrator, a
+service offering will not be available to end users that are creating
+new instances.
+
+
+System Service Offerings
+------------------------
+
+System service offerings provide a choice of CPU speed, number of CPUs,
+tags, and RAM size, just as other service offerings do. But rather than
+being used for virtual machine instances and exposed to users, system
+service offerings are used to change the default properties of virtual
+routers, console proxies, and other system VMs. System service offerings
+are visible only to the CloudStack root administrator. CloudStack
+provides default system service offerings. The CloudStack root
+administrator can create additional custom system service offerings.
+
+When CloudStack creates a virtual router for a guest network, it uses
+default settings which are defined in the system service offering
+associated with the network offering. You can upgrade the capabilities
+of the virtual router by applying a new network offering that contains a
+different system service offering. All virtual routers in that network
+will begin using the settings from the new service offering.
+
+
+Creating a New System Service Offering
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To create a system service offering:
+
+#. Log in with admin privileges to the CloudStack UI.
+
+#. In the left navigation bar, click Service Offerings.
+
+#. In Select Offering, choose System Offering.
+
+#. Click Add System Service Offering.
+
+#. In the dialog, make the following choices:
+
+ - Name. Any desired name for the system offering.
+
+ - Description. A short description of the offering that can be
+ displayed to users
+
+ - System VM Type. Select the type of system virtual machine that
+ this offering is intended to support.
+
+ - Storage type. The type of disk that should be allocated. Local
+ allocates from storage attached directly to the host where the
+ system VM is running. Shared allocates from storage accessible via
+ NFS.
+
+ - # of CPU cores. The number of cores which should be allocated to a
+ system VM with this offering
+
+ - CPU (in MHz). The CPU speed of the cores that the system VM is
+ allocated. For example, "2000" would provide for a 2 GHz clock.
+
+ - Memory (in MB). The amount of memory in megabytes that the system
+ VM should be allocated. For example, "2048" would provide for a 2
+ GB RAM allocation.
+
+ - Network Rate. Allowed data transfer rate in MB per second.
+
+ - Offer HA. If yes, the administrator can choose to have the system
+ VM be monitored and as highly available as possible.
+
+ - Storage Tags. The tags that should be associated with the primary
+ storage used by the system VM.
+
+ - Host Tags. (Optional) Any tags that you use to organize your hosts
+
+ - CPU cap. Whether to limit the level of CPU usage even if spare
+ capacity is available.
+
+ - Public. Indicate whether the service offering should be available
+ all domains or only some domains. Choose Yes to make it available
+ to all domains. Choose No to limit the scope to a subdomain;
+ CloudStack will then prompt for the subdomain's name.
+
+#. Click Add.
+
+
+Network Throttling
+------------------
+
+Network throttling is the process of controlling the network access and
+bandwidth usage based on certain rules. CloudStack controls this
+behaviour of the guest networks in the cloud by using the network rate
+parameter. This parameter is defined as the default data transfer rate
+in Mbps (Megabits Per Second) allowed in a guest network. It defines the
+upper limits for network utilization. If the current utilization is
+below the allowed upper limits, access is granted, else revoked.
+
+You can throttle the network bandwidth either to control the usage above
+a certain limit for some accounts, or to control network congestion in a
+large cloud environment. The network rate for your cloud can be
+configured on the following:
+
+- Network Offering
+
+- Service Offering
+
+- Global parameter
+
+If network rate is set to NULL in service offering, the value provided
+in the vm.network.throttling.rate global parameter is applied. If the
+value is set to NULL for network offering, the value provided in the
+network.throttling.rate global parameter is considered.
+
+For the default public, storage, and management networks, network rate
+is set to 0. This implies that the public, storage, and management
+networks will have unlimited bandwidth by default. For default guest
+networks, network rate is set to NULL. In this case, network rate is
+defaulted to the global parameter value.
+
+The following table gives you an overview of how network rate is applied
+on different types of networks in CloudStack.
+
+.. cssclass:: table-striped table-bordered table-hover
+
+=========================================== ===============================
+Networks Network Rate Is Taken from
+=========================================== ===============================
+Guest network of Virtual Router Guest Network Offering
+Public network of Virtual Router Guest Network Offering
+Storage network of Secondary Storage VM System Network Offering
+Management network of Secondary Storage VM System Network Offering
+Storage network of Console Proxy VM System Network Offering
+Management network of Console Proxy VM System Network Offering
+Storage network of Virtual Router System Network Offering
+Management network of Virtual Router System Network Offering
+Public network of Secondary Storage VM System Network Offering
+Public network of Console Proxy VM System Network Offering
+Default network of a guest VM Compute Offering
+Additional networks of a guest VM Corresponding Network Offerings
+=========================================== ===============================
+
+A guest VM must have a default network, and can also have many
+additional networks. Depending on various parameters, such as the host
+and virtual switch used, you can observe a difference in the network
+rate in your cloud. For example, on a VMware host the actual network
+rate varies based on where they are configured (compute offering,
+network offering, or both); the network type (shared or isolated); and
+traffic direction (ingress or egress).
+
+The network rate set for a network offering used by a particular network
+in CloudStack is used for the traffic shaping policy of a port group,
+for example: port group A, for that network: a particular subnet or VLAN
+on the actual network. The virtual routers for that network connects to
+the port group A, and by default instances in that network connects to
+this port group. However, if an instance is deployed with a compute
+offering with the network rate set, and if this rate is used for the
+traffic shaping policy of another port group for the network, for
+example port group B, then instances using this compute offering are
+connected to the port group B, instead of connecting to port group A.
+
+The traffic shaping policy on standard port groups in VMware only
+applies to the egress traffic, and the net effect depends on the type of
+network used in CloudStack. In shared networks, ingress traffic is
+unlimited for CloudStack, and egress traffic is limited to the rate that
+applies to the port group used by the instance if any. If the compute
+offering has a network rate configured, this rate applies to the egress
+traffic, otherwise the network rate set for the network offering
+applies. For isolated networks, the network rate set for the network
+offering, if any, effectively applies to the ingress traffic. This is
+mainly because the network rate set for the network offering applies to
+the egress traffic from the virtual router to the instance. The egress
+traffic is limited by the rate that applies to the port group used by
+the instance if any, similar to shared networks.
+
+For example:
+
+Network rate of network offering = 10 Mbps
+
+Network rate of compute offering = 200 Mbps
+
+In shared networks, ingress traffic will not be limited for CloudStack,
+while egress traffic will be limited to 200 Mbps. In an isolated
+network, ingress traffic will be limited to 10 Mbps and egress to 200
+Mbps.
+
+
+Changing the Default System Offering for System VMs
+---------------------------------------------------
+
+You can manually change the system offering for a particular System VM.
+Additionally, as a CloudStack administrator, you can also change the
+default system offering used for System VMs.
+
+#. Create a new system offering.
+
+ For more information, see Creating a New System Service Offering.
+
+#. Back up the database:
+
+ .. code:: bash
+
+ mysqldump -u root -p cloud | bzip2 > cloud_backup.sql.bz2
+
+#. Open an MySQL prompt:
+
+ .. code:: bash
+
+ mysql -u cloud -p cloud
+
+#. Run the following queries on the cloud database.
+
+ #. In the disk\_offering table, identify the original default
+ offering and the new offering you want to use by default.
+
+ Take a note of the ID of the new offering.
+
+ .. code:: bash
+
+ select id,name,unique_name,type from disk_offering;
+
+ #. For the original default offering, set the value of unique\_name
+ to NULL.
+
+ .. code:: bash
+
+ # update disk_offering set unique_name = NULL where id = 10;
+
+ Ensure that you use the correct value for the ID.
+
+ #. For the new offering that you want to use by default, set the
+ value of unique\_name as follows:
+
+ For the default Console Proxy VM (CPVM) offering,set unique\_name
+ to 'Cloud.com-ConsoleProxy'. For the default Secondary Storage VM
+ (SSVM) offering, set unique\_name to 'Cloud.com-SecondaryStorage'.
+ For example:
+
+ .. code:: bash
+
+ update disk_offering set unique_name = 'Cloud.com-ConsoleProxy' where id = 16;
+
+#. Restart CloudStack Management Server. Restarting is required because
+ the default offerings are loaded into the memory at startup.
+
+ .. code:: bash
+
+ service cloudstack-management restart
+
+#. Destroy the existing CPVM or SSVM offerings and wait for them to be
+ recreated. The new CPVM or SSVM are configured with the new offering.
+
diff --git a/source/adminguide/storage.rst b/source/adminguide/storage.rst
new file mode 100644
index 0000000..44f5fcb
--- /dev/null
+++ b/source/adminguide/storage.rst
@@ -0,0 +1,804 @@
+.. 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.
+
+Storage Overview
+----------------
+
+CloudStack defines two types of storage: primary and secondary. Primary
+storage can be accessed by either iSCSI or NFS. Additionally, direct
+attached storage may be used for primary storage. Secondary storage is
+always accessed using NFS.
+
+There is no ephemeral storage in CloudStack. All volumes on all nodes
+are persistent.
+
+
+Primary Storage
+---------------
+
+This section gives technical details about CloudStack
+primary storage. For more information about the concepts behind primary storage
+see :ref:`about-primary-storage` . For information about how to install and configure
+primary storage through the CloudStack UI, see the in the Installation Guide.
+
+Best Practices for Primary Storage
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- The speed of primary storage will impact guest performance. If
+ possible, choose smaller, higher RPM drives or SSDs for primary
+ storage.
+
+- There are two ways CloudStack can leverage primary storage:
+
+ Static: This is CloudStack's traditional way of handling storage. In
+ this model, a preallocated amount of storage (ex. a volume from a
+ SAN) is given to CloudStack. CloudStack then permits many of its
+ volumes to be created on this storage (can be root and/or data
+ disks). If using this technique, ensure that nothing is stored on the
+ storage. Adding the storage to CloudStack will destroy any existing
+ data.
+
+ Dynamic: This is a newer way for CloudStack to manage storage. In
+ this model, a storage system (rather than a preallocated amount of
+ storage) is given to CloudStack. CloudStack, working in concert with
+ a storage plug-in, dynamically creates volumes on the storage system
+ and each volume on the storage system maps to a single CloudStack
+ volume. This is highly useful for features such as storage Quality of
+ Service. Currently this feature is supported for data disks (Disk
+ Offerings).
+
+
+Runtime Behavior of Primary Storage
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Root volumes are created automatically when a virtual machine is
+created. Root volumes are deleted when the VM is destroyed. Data volumes
+can be created and dynamically attached to VMs. Data volumes are not
+deleted when VMs are destroyed.
+
+Administrators should monitor the capacity of primary storage devices
+and add additional primary storage as needed. See the Advanced
+Installation Guide.
+
+Administrators add primary storage to the system by creating a
+CloudStack storage pool. Each storage pool is associated with a cluster
+or a zone.
+
+With regards to data disks, when a user executes a Disk Offering to
+create a data disk, the information is initially written to the
+CloudStack database only. Upon the first request that the data disk be
+attached to a VM, CloudStack determines what storage to place the volume
+on and space is taken from that storage (either from preallocated
+storage or from a storage system (ex. a SAN), depending on how the
+primary storage was added to CloudStack).
+
+
+Hypervisor Support for Primary Storage
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The following table shows storage options and parameters for different
+hypervisors.
+
+.. cssclass:: table-striped table-bordered table-hover
+
+============================================== ================ ==================== =========================== ============================
+Storage media \\ hypervisor VMware vSphere Citrix XenServer KVM Hyper-V
+============================================== ================ ==================== =========================== ============================
+**Format for Disks, Templates, and Snapshots** VMDK VHD QCOW2 VHD
+ Snapshots are not supported.
+**iSCSI support** VMFS Clustered LVM Yes, via Shared Mountpoint No
+**Fiber Channel support** VMFS Yes, via Existing SR Yes, via Shared Mountpoint No
+**NFS support** Yes Yes Yes No
+**Local storage support** Yes Yes Yes Yes
+**Storage over-provisioning** NFS and iSCSI NFS NFS No
+**SMB/CIFS** No No No Yes
+**Ceph/RBD** No No Yes No
+============================================== ================ ==================== =========================== ============================
+
+XenServer uses a clustered LVM system to store VM images on iSCSI and
+Fiber Channel volumes and does not support over-provisioning in the
+hypervisor. The storage server itself, however, can support
+thin-provisioning. As a result the CloudStack can still support storage
+over-provisioning by running on thin-provisioned storage volumes.
+
+KVM supports "Shared Mountpoint" storage. A shared mountpoint is a file
+system path local to each server in a given cluster. The path must be
+the same across all Hosts in the cluster, for example /mnt/primary1.
+This shared mountpoint is assumed to be a clustered filesystem such as
+OCFS2. In this case the CloudStack does not attempt to mount or unmount
+the storage as is done with NFS. The CloudStack requires that the
+administrator insure that the storage is available
+
+With NFS storage, CloudStack manages the overprovisioning. In this case
+the global configuration parameter storage.overprovisioning.factor
+controls the degree of overprovisioning. This is independent of
+hypervisor type.
+
+Local storage is an option for primary storage for vSphere, XenServer,
+and KVM. When the local disk option is enabled, a local disk storage
+pool is automatically created on each host. To use local storage for the
+System Virtual Machines (such as the Virtual Router), set
+system.vm.use.local.storage to true in global configuration.
+
+CloudStack supports multiple primary storage pools in a Cluster. For
+example, you could provision 2 NFS servers in primary storage. Or you
+could provision 1 iSCSI LUN initially and then add a second iSCSI LUN
+when the first approaches capacity.
+
+
+Storage Tags
+~~~~~~~~~~~~
+
+Storage may be "tagged". A tag is a text string attribute associated
+with primary storage, a Disk Offering, or a Service Offering. Tags allow
+administrators to provide additional information about the storage. For
+example, that is a "SSD" or it is "slow". Tags are not interpreted by
+CloudStack. They are matched against tags placed on service and disk
+offerings. CloudStack requires all tags on service and disk offerings to
+exist on the primary storage before it allocates root or data disks on
+the primary storage. Service and disk offering tags are used to identify
+the requirements of the storage that those offerings have. For example,
+the high end service offering may require "fast" for its root disk
+volume.
+
+The interaction between tags, allocation, and volume copying across
+clusters and pods can be complex. To simplify the situation, use the
+same set of tags on the primary storage for all clusters in a pod. Even
+if different devices are used to present those tags, the set of exposed
+tags can be the same.
+
+
+Maintenance Mode for Primary Storage
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Primary storage may be placed into maintenance mode. This is useful, for
+example, to replace faulty RAM in a storage device. Maintenance mode for
+a storage device will first stop any new guests from being provisioned
+on the storage device. Then it will stop all guests that have any volume
+on that storage device. When all such guests are stopped the storage
+device is in maintenance mode and may be shut down. When the storage
+device is online again you may cancel maintenance mode for the device.
+The CloudStack will bring the device back online and attempt to start
+all guests that were running at the time of the entry into maintenance
+mode.
+
+
+Secondary Storage
+-----------------
+
+This section gives concepts and technical details about CloudStack
+secondary storage. For information about how to install and configure
+secondary storage through the CloudStack UI, see the Advanced
+Installation Guide. about-secondary-storage>`_
+
+
+Working With Volumes
+--------------------
+
+A volume provides storage to a guest VM. The volume can provide for a
+root disk or an additional data disk. CloudStack supports additional
+volumes for guest VMs.
+
+Volumes are created for a specific hypervisor type. A volume that has
+been attached to guest using one hypervisor type (e.g, XenServer) may
+not be attached to a guest that is using another hypervisor type, for
+example:vSphere, KVM. This is because the different hypervisors use
+different disk image formats.
+
+CloudStack defines a volume as a unit of storage available to a guest
+VM. Volumes are either root disks or data disks. The root disk has "/"
+in the file system and is usually the boot device. Data disks provide
+for additional storage, for example: "/opt" or "D:". Every guest VM has
+a root disk, and VMs can also optionally have a data disk. End users can
+mount multiple data disks to guest VMs. Users choose data disks from the
+disk offerings created by administrators. The user can create a template
+from a volume as well; this is the standard procedure for private
+template creation. Volumes are hypervisor-specific: a volume from one
+hypervisor type may not be used on a guest of another hypervisor type.
+
+.. note::
+ CloudStack supports attaching up to
+
+ - 13 data disks on XenServer hypervisor versions 6.0 and above,
+ And all versions of VMware.
+
+ - 64 data disks on Hyper-V.
+
+ - 6 data disks on other hypervisor types.
+
+
+Creating a New Volume
+~~~~~~~~~~~~~~~~~~~~~
+
+You can add more data disk volumes to a guest VM at any time, up to the
+limits of your storage capacity. Both CloudStack administrators and
+users can add volumes to VM instances. When you create a new volume, it
+is stored as an entity in CloudStack, but the actual storage resources
+are not allocated on the physical storage device until you attach the
+volume. This optimization allows the CloudStack to provision the volume
+nearest to the guest that will use it when the first attachment is made.
+
+
+Using Local Storage for Data Volumes
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+You can create data volumes on local storage (supported with XenServer,
+KVM, and VMware). The data volume is placed on the same host as the VM
+instance that is attached to the data volume. These local data volumes
+can be attached to virtual machines, detached, re-attached, and deleted
+just as with the other types of data volume.
+
+Local storage is ideal for scenarios where persistence of data volumes
+and HA is not required. Some of the benefits include reduced disk I/O
+latency and cost reduction from using inexpensive local disks.
+
+In order for local volumes to be used, the feature must be enabled for
+the zone.
+
+You can create a data disk offering for local storage. When a user
+creates a new VM, they can select this disk offering in order to cause
+the data disk volume to be placed in local storage.
+
+You can not migrate a VM that has a volume in local storage to a
+different host, nor migrate the volume itself away to a different host.
+If you want to put a host into maintenance mode, you must first stop any
+VMs with local data volumes on that host.
+
+
+To Create a New Volume
+^^^^^^^^^^^^^^^^^^^^^^
+
+#. Log in to the CloudStack UI as a user or admin.
+
+#. In the left navigation bar, click Storage.
+
+#. In Select View, choose Volumes.
+
+#. To create a new volume, click Add Volume, provide the following
+ details, and click OK.
+
+ - Name. Give the volume a unique name so you can find it later.
+
+ - Availability Zone. Where do you want the storage to reside? This
+ should be close to the VM that will use the volume.
+
+ - Disk Offering. Choose the characteristics of the storage.
+
+ The new volume appears in the list of volumes with the state
+ “Allocated.” The volume data is stored in CloudStack, but the volume
+ is not yet ready for use
+
+#. To start using the volume, continue to Attaching a Volume
+
+
+Uploading an Existing Volume to a Virtual Machine
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Existing data can be made accessible to a virtual machine. This is
+called uploading a volume to the VM. For example, this is useful to
+upload data from a local file system and attach it to a VM. Root
+administrators, domain administrators, and end users can all upload
+existing volumes to VMs.
+
+The upload is performed using HTTP. The uploaded volume is placed in the
+zone's secondary storage
+
+You cannot upload a volume if the preconfigured volume limit has already
+been reached. The default limit for the cloud is set in the global
+configuration parameter max.account.volumes, but administrators can also
+set per-domain limits that are different from the global default. See
+Setting Usage Limits
+
+To upload a volume:
+
+#. (Optional) Create an MD5 hash (checksum) of the disk image file that
+ you are going to upload. After uploading the data disk, CloudStack
+ will use this value to verify that no data corruption has occurred.
+
+#. Log in to the CloudStack UI as an administrator or user
+
+#. In the left navigation bar, click Storage.
+
+#. Click Upload Volume.
+
+#. Provide the following:
+
+ - Name and Description. Any desired name and a brief description
+ that can be shown in the UI.
+
+ - Availability Zone. Choose the zone where you want to store the
+ volume. VMs running on hosts in this zone can attach the volume.
+
+ - Format. Choose one of the following to indicate the disk image
+ format of the volume.
+
+ .. cssclass:: table-striped table-bordered table-hover
+
+ ========== =================
+ Hypervisor Disk Image Format
+ ========== =================
+ XenServer VHD
+ VMware OVA
+ KVM QCOW2
+ ========== =================
+
+ - URL. The secure HTTP or HTTPS URL that CloudStack can use to
+ access your disk. The type of file at the URL must match the value
+ chosen in Format. For example, if Format is VHD, the URL might
+ look like the following:
+
+ ``http://yourFileServerIP/userdata/myDataDisk.vhd``
+
+ - MD5 checksum. (Optional) Use the hash that you created in step 1.
+
+#. Wait until the status of the volume shows that the upload is
+ complete. Click Instances - Volumes, find the name you specified in
+ step 5, and make sure the status is Uploaded.
+
+
+Attaching a Volume
+~~~~~~~~~~~~~~~~~~
+
+You can attach a volume to a guest VM to provide extra disk storage.
+Attach a volume when you first create a new volume, when you are moving
+an existing volume from one VM to another, or after you have migrated a
+volume from one storage pool to another.
+
+#. Log in to the CloudStack UI as a user or admin.
+
+#. In the left navigation, click Storage.
+
+#. In Select View, choose Volumes.
+
+#. Click the volume name in the Volumes list, then click the Attach Disk
+ button |AttachDiskButton.png|
+
+#. In the Instance popup, choose the VM to which you want to attach the
+ volume. You will only see instances to which you are allowed to
+ attach volumes; for example, a user will see only instances created
+ by that user, but the administrator will have more choices.
+
+#. When the volume has been attached, you should be able to see it by
+ clicking Instances, the instance name, and View Volumes.
+
+
+Detaching and Moving Volumes
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. note::
+ This procedure is different from moving volumes from one storage pool
+ to another as described in `“VM Storage Migration”
+ <#vm-storage-migration>`_.
+
+A volume can be detached from a guest VM and attached to another guest.
+Both CloudStack administrators and users can detach volumes from VMs and
+move them to other VMs.
+
+If the two VMs are in different clusters, and the volume is large, it
+may take several minutes for the volume to be moved to the new VM.
+
+#. Log in to the CloudStack UI as a user or admin.
+
+#. In the left navigation bar, click Storage, and choose Volumes in
+ Select View. Alternatively, if you know which VM the volume is
+ attached to, you can click Instances, click the VM name, and click
+ View Volumes.
+
+#. Click the name of the volume you want to detach, then click the
+ Detach Disk button. |DetachDiskButton.png|
+
+#. To move the volume to another VM, follow the steps in
+ `“Attaching a Volume” <#attaching-a-volume>`_.
+
+
+VM Storage Migration
+~~~~~~~~~~~~~~~~~~~~
+
+Supported in XenServer, KVM, and VMware.
+
+.. note::
+ This procedure is different from moving disk volumes from one VM to
+ another as described in `“Detaching and Moving Volumes”
+ <#detaching-and-moving-volumes>`_.
+
+You can migrate a virtual machine’s root disk volume or any additional
+data disk volume from one storage pool to another in the same zone.
+
+You can use the storage migration feature to achieve some commonly
+desired administration goals, such as balancing the load on storage
+pools and increasing the reliability of virtual machines by moving them
+away from any storage pool that is experiencing issues.
+
+On XenServer and VMware, live migration of VM storage is enabled through
+CloudStack support for XenMotion and vMotion. Live storage migration
+allows VMs to be moved from one host to another, where the VMs are not
+located on storage shared between the two hosts. It provides the option
+to live migrate a VM’s disks along with the VM itself. It is possible to
+migrate a VM from one XenServer resource pool / VMware cluster to
+another, or to migrate a VM whose disks are on local storage, or even to
+migrate a VM’s disks from one storage repository to another, all while
+the VM is running.
+
+.. note::
+ Because of a limitation in VMware, live migration of storage for a
+ VM is allowed only if the source and target storage pool are
+ accessible to the source host; that is, the host where the VM is
+ running when the live migration operation is requested.
+
+
+Migrating a Data Volume to a New Storage Pool
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+There are two situations when you might want to migrate a disk:
+
+- Move the disk to new storage, but leave it attached to the same
+ running VM.
+
+- Detach the disk from its current VM, move it to new storage, and
+ attach it to a new VM.
+
+
+Migrating Storage For a Running VM
+''''''''''''''''''''''''''''''''''
+
+(Supported on XenServer and VMware)
+
+#. Log in to the CloudStack UI as a user or admin.
+
+#. In the left navigation bar, click Instances, click the VM name, and
+ click View Volumes.
+
+#. Click the volume you want to migrate.
+
+#. Detach the disk from the VM. See `“Detaching and
+ Moving Volumes” <#detaching-and-moving-volumes>`_ but skip the “reattach”
+ step at the end. You will do that after migrating to new storage.
+
+#. Click the Migrate Volume button |Migrateinstance.png| and choose the
+ destination from the dropdown list.
+
+#. Watch for the volume status to change to Migrating, then back to
+ Ready.
+
+
+Migrating Storage and Attaching to a Different VM
+'''''''''''''''''''''''''''''''''''''''''''''''''
+
+#. Log in to the CloudStack UI as a user or admin.
+
+#. Detach the disk from the VM. See `“Detaching and
+ Moving Volumes” <#detaching-and-moving-volumes>`_ but skip the “reattach”
+ step at the end. You will do that after migrating to new storage.
+
+#. Click the Migrate Volume button |Migrateinstance.png| and choose the
+ destination from the dropdown list.
+
+#. Watch for the volume status to change to Migrating, then back to
+ Ready. You can find the volume by clicking Storage in the left
+ navigation bar. Make sure that Volumes is displayed at the top of the
+ window, in the Select View dropdown.
+
+#. Attach the volume to any desired VM running in the same cluster as
+ the new storage server. See `“Attaching a
+ Volume” <#attaching-a-volume>`_
+
+
+Migrating a VM Root Volume to a New Storage Pool
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+(XenServer, VMware) You can live migrate a VM's root disk from one
+storage pool to another, without stopping the VM first.
+
+(KVM) When migrating the root disk volume, the VM must first be stopped,
+and users can not access the VM. After migration is complete, the VM can
+be restarted.
+
+#. Log in to the CloudStack UI as a user or admin.
+
+#. In the left navigation bar, click Instances, and click the VM name.
+
+#. (KVM only) Stop the VM.
+
+#. Click the Migrate button |Migrateinstance.png| and choose the
+ destination from the dropdown list.
+
+ .. note::
+ If the VM's storage has to be migrated along with the VM, this will
+ be noted in the host list. CloudStack will take care of the storage
+ migration for you.
+
+#. Watch for the volume status to change to Migrating, then back to
+ Running (or Stopped, in the case of KVM). This can take some time.
+
+#. (KVM only) Restart the VM.
+
+
+Resizing Volumes
+~~~~~~~~~~~~~~~~
+
+CloudStack provides the ability to resize data disks; CloudStack
+controls volume size by using disk offerings. This provides CloudStack
+administrators with the flexibility to choose how much space they want
+to make available to the end users. Volumes within the disk offerings
+with the same storage tag can be resized. For example, if you only want
+to offer 10, 50, and 100 GB offerings, the allowed resize should stay
+within those limits. That implies if you define a 10 GB, a 50 GB and a
+100 GB disk offerings, a user can upgrade from 10 GB to 50 GB, or 50 GB
+to 100 GB. If you create a custom-sized disk offering, then you have the
+option to resize the volume by specifying a new, larger size.
+
+Additionally, using the resizeVolume API, a data volume can be moved
+from a static disk offering to a custom disk offering with the size
+specified. This functionality allows those who might be billing by
+certain volume sizes or disk offerings to stick to that model, while
+providing the flexibility to migrate to whatever custom size necessary.
+
+This feature is supported on KVM, XenServer, and VMware hosts. However,
+shrinking volumes is not supported on VMware hosts.
+
+Before you try to resize a volume, consider the following:
+
+- The VMs associated with the volume are stopped.
+
+- The data disks associated with the volume are removed.
+
+- When a volume is shrunk, the disk associated with it is simply
+ truncated, and doing so would put its content at risk of data loss.
+ Therefore, resize any partitions or file systems before you shrink a
+ data disk so that all the data is moved off from that disk.
+
+To resize a volume:
+
+#. Log in to the CloudStack UI as a user or admin.
+
+#. In the left navigation bar, click Storage.
+
+#. In Select View, choose Volumes.
+
+#. Select the volume name in the Volumes list, then click the Resize
+ Volume button |resize-volume-icon.png|
+
+#. In the Resize Volume pop-up, choose desired characteristics for the
+ storage.
+
+ |resize-volume.png|
+
+ #. If you select Custom Disk, specify a custom size.
+
+ #. Click Shrink OK to confirm that you are reducing the size of a
+ volume.
+
+ This parameter protects against inadvertent shrinking of a disk,
+ which might lead to the risk of data loss. You must sign off that
+ you know what you are doing.
+
+#. Click OK.
+
+
+Reset VM to New Root Disk on Reboot
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can specify that you want to discard the root disk and create a new
+one whenever a given VM is rebooted. This is useful for secure
+environments that need a fresh start on every boot and for desktops that
+should not retain state. The IP address of the VM will not change due to
+this operation.
+
+**To enable root disk reset on VM reboot:**
+
+When creating a new service offering, set the parameter isVolatile to
+True. VMs created from this service offering will have their disks reset
+upon reboot. See `“Creating a New Compute
+Offering” <service_offerings.html#creating-a-new-compute-offering>`_.
+
+
+Volume Deletion and Garbage Collection
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The deletion of a volume does not delete the snapshots that have been
+created from the volume
+
+When a VM is destroyed, data disk volumes that are attached to the VM
+are not deleted.
+
+Volumes are permanently destroyed using a garbage collection process.
+The global configuration variables expunge.delay and expunge.interval
+determine when the physical deletion of volumes will occur.
+
+- `expunge.delay`: determines how old the volume must be before it is
+ destroyed, in seconds
+
+- `expunge.interval`: determines how often to run the garbage collection
+ check
+
+Administrators should adjust these values depending on site policies
+around data retention.
+
+
+Working with Volume Snapshots
+-----------------------------
+
+(Supported for the following hypervisors: **XenServer**, **VMware
+vSphere**, and **KVM**)
+
+CloudStack supports snapshots of disk volumes. Snapshots are a
+point-in-time capture of virtual machine disks. Memory and CPU states
+are not captured. If you are using the Oracle VM hypervisor, you can not
+take snapshots, since OVM does not support them.
+
+Snapshots may be taken for volumes, including both root and data disks
+(except when the Oracle VM hypervisor is used, which does not support
+snapshots). The administrator places a limit on the number of stored
+snapshots per user. Users can create new volumes from the snapshot for
+recovery of particular files and they can create templates from
+snapshots to boot from a restored disk.
+
+Users can create snapshots manually or by setting up automatic recurring
+snapshot policies. Users can also create disk volumes from snapshots,
+which may be attached to a VM like any other disk volume. Snapshots of
+both root disks and data disks are supported. However, CloudStack does
+not currently support booting a VM from a recovered root disk. A disk
+recovered from snapshot of a root disk is treated as a regular data
+disk; the data on recovered disk can be accessed by attaching the disk
+to a VM.
+
+A completed snapshot is copied from primary storage to secondary
+storage, where it is stored until deleted or purged by newer snapshot.
+
+
+How to Snapshot a Volume
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. Log in to the CloudStack UI as a user or administrator.
+
+#. In the left navigation bar, click Storage.
+
+#. In Select View, be sure Volumes is selected.
+
+#. Click the name of the volume you want to snapshot.
+
+#. Click the Snapshot button. |SnapshotButton.png|
+
+
+Automatic Snapshot Creation and Retention
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+(Supported for the following hypervisors: **XenServer**, **VMware
+vSphere**, and **KVM**)
+
+Users can set up a recurring snapshot policy to automatically create
+multiple snapshots of a disk at regular intervals. Snapshots can be
+created on an hourly, daily, weekly, or monthly interval. One snapshot
+policy can be set up per disk volume. For example, a user can set up a
+daily snapshot at 02:30.
+
+With each snapshot schedule, users can also specify the number of
+scheduled snapshots to be retained. Older snapshots that exceed the
+retention limit are automatically deleted. This user-defined limit must
+be equal to or lower than the global limit set by the CloudStack
+administrator. See `“Globally Configured
+Limits” <usage.html#globally-configured-limits>`_. The limit applies only
+to those snapshots that are taken as part of an automatic recurring
+snapshot policy. Additional manual snapshots can be created and
+retained.
+
+
+Incremental Snapshots and Backup
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Snapshots are created on primary storage where a disk resides. After a
+snapshot is created, it is immediately backed up to secondary storage
+and removed from primary storage for optimal utilization of space on
+primary storage.
+
+CloudStack does incremental backups for some hypervisors. When
+incremental backups are supported, every N backup is a full backup.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++------------------------------+------------------+------------------+-----+
+| | VMware vSphere | Citrix XenServer | KVM |
++==============================+==================+==================+=====+
+| Support incremental backup | No | Yes | No |
++------------------------------+------------------+------------------+-----+
+
+
+Volume Status
+~~~~~~~~~~~~~
+
+When a snapshot operation is triggered by means of a recurring snapshot
+policy, a snapshot is skipped if a volume has remained inactive since
+its last snapshot was taken. A volume is considered to be inactive if it
+is either detached or attached to a VM that is not running. CloudStack
+ensures that at least one snapshot is taken since the volume last became
+inactive.
+
+When a snapshot is taken manually, a snapshot is always created
+regardless of whether a volume has been active or not.
+
+
+Snapshot Restore
+~~~~~~~~~~~~~~~~
+
+There are two paths to restoring snapshots. Users can create a volume
+from the snapshot. The volume can then be mounted to a VM and files
+recovered as needed. Alternatively, a template may be created from the
+snapshot of a root disk. The user can then boot a VM from this template
+to effect recovery of the root disk.
+
+
+Snapshot Job Throttling
+~~~~~~~~~~~~~~~~~~~~~~~
+
+When a snapshot of a virtual machine is requested, the snapshot job runs
+on the same host where the VM is running or, in the case of a stopped
+VM, the host where it ran last. If many snapshots are requested for VMs
+on a single host, this can lead to problems with too many snapshot jobs
+overwhelming the resources of the host.
+
+To address this situation, the cloud's root administrator can throttle
+how many snapshot jobs are executed simultaneously on the hosts in the
+cloud by using the global configuration setting
+concurrent.snapshots.threshold.perhost. By using this setting, the
+administrator can better ensure that snapshot jobs do not time out and
+hypervisor hosts do not experience performance issues due to hosts being
+overloaded with too many snapshot requests.
+
+Set concurrent.snapshots.threshold.perhost to a value that represents a
+best guess about how many snapshot jobs the hypervisor hosts can execute
+at one time, given the current resources of the hosts and the number of
+VMs running on the hosts. If a given host has more snapshot requests,
+the additional requests are placed in a waiting queue. No new snapshot
+jobs will start until the number of currently executing snapshot jobs
+falls below the configured limit.
+
+The admin can also set job.expire.minutes to place a maximum on how long
+a snapshot request will wait in the queue. If this limit is reached, the
+snapshot request fails and returns an error message.
+
+
+VMware Volume Snapshot Performance
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When you take a snapshot of a data or root volume on VMware, CloudStack
+uses an efficient storage technique to improve performance.
+
+A snapshot is not immediately exported from vCenter to a mounted NFS
+share and packaged into an OVA file format. This operation would consume
+time and resources. Instead, the original file formats (e.g., VMDK)
+provided by vCenter are retained. An OVA file will only be created as
+needed, on demand. To generate the OVA, CloudStack uses information in a
+properties file (\*.ova.meta) which it stored along with the original
+snapshot data.
+
+.. note::
+ For upgrading customers: This process applies only to newly created
+ snapshots after upgrade to CloudStack 4.2. Snapshots that have already
+ been taken and stored in OVA format will continue to exist in that
+ format, and will continue to work as expected.
+
+
+.. |AttachDiskButton.png| image:: /_static/images/attach-disk-icon.png
+ :alt: Attach Disk Button.
+.. |resize-volume-icon.png| image:: /_static/images/resize-volume-icon.png
+ :alt: button to display the resize volume option.
+.. |resize-volume.png| image:: /_static/images/resize-volume.png
+ :alt: option to resize a volume.
+.. |SnapshotButton.png| image:: /_static/images/SnapshotButton.png
+ :alt: Snapshot Button.
+.. |DetachDiskButton.png| image:: /_static/images/detach-disk-icon.png
+ :alt: Detach Disk Button.
+.. |Migrateinstance.png| image:: /_static/images/migrate-instance.png
+ :alt: button to migrate a volume.
diff --git a/source/adminguide/systemvm.rst b/source/adminguide/systemvm.rst
new file mode 100644
index 0000000..286e5e4
--- /dev/null
+++ b/source/adminguide/systemvm.rst
@@ -0,0 +1,554 @@
+.. 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 uses several types of system virtual machines to perform
+tasks in the cloud. In general CloudStack manages these system VMs and
+creates, starts, and stops them as needed based on scale and immediate
+needs. However, the administrator should be aware of them and their
+roles to assist in debugging issues.
+
+
+The System VM Template
+----------------------
+
+The System VMs come from a single template. The System VM has the
+following characteristics:
+
+- Debian 7.8 ("wheezy"), 3.2.0 kernel with the latest security
+ patches from the Debian security APT repository
+
+- Has a minimal set of packages installed thereby reducing the attack
+ surface
+
+- 64-bit for enhanced performance on Xen/VMWare
+
+- pvops kernel with Xen PV drivers, KVM virtio drivers, and VMware
+ tools for optimum performance on all hypervisors
+
+- Xen tools inclusion allows performance monitoring
+
+- Latest versions of HAProxy, iptables, IPsec, and Apache from debian
+ repository ensures improved security and speed
+
+- Latest version of JRE from Sun/Oracle ensures improved security and
+ speed
+
+
+Changing the Default System VM Template
+---------------------------------------
+
+Using the 64-bit template should be use with a System Offering of at least 512MB
+of memory.
+
+#. Based on the hypervisor you use, download the 64-bit template from
+ the following location:
+
+ .. cssclass:: table-striped table-bordered table-hover
+
+ ========== ================================================================================================
+ Hypervisor Download Location
+ ========== ================================================================================================
+ XenServer |sysvm64-url-xen|
+ KVM |sysvm64-url-kvm|
+ VMware |sysvm64-url-vmware|
+ Hyper-V |sysvm64-url-hyperv|
+ ========== ================================================================================================
+
+#. As an administrator, log in to the CloudStack UI
+
+#. Register the 64 bit template.
+
+ For example: KVM64bitTemplate
+
+#. While registering the template, select Routing.
+
+#. Navigate to Infrastructure > Zone > Settings.
+
+#. Set the name of the 64-bit template, KVM64bitTemplate, in the
+ *``router.template.kvm``* global parameter.
+
+ If you are using a XenServer 64-bit template, set the name in the
+ *``router.template.xen``* global parameter.
+
+ Any new virtual router created in this Zone automatically picks up
+ this template.
+
+#. Restart the Management Server.
+
+
+Multiple System VM Support for VMware
+-------------------------------------
+
+Every CloudStack zone has single System VM for template processing tasks
+such as downloading templates, uploading templates, and uploading ISOs.
+In a zone where VMware is being used, additional System VMs can be
+launched to process VMware-specific tasks such as taking snapshots and
+creating private templates. The CloudStack management server launches
+additional System VMs for VMware-specific tasks as the load increases.
+The management server monitors and weights all commands sent to these
+System VMs and performs dynamic load balancing and scaling-up of more
+System VMs.
+
+
+Console Proxy
+-------------
+
+The Console Proxy is a type of System Virtual Machine that has a role in
+presenting a console view via the web UI. It connects the user’s browser
+to the VNC port made available via the hypervisor for the console of the
+guest. Both the administrator and end user web UIs offer a console
+connection.
+
+Clicking a console icon brings up a new window. The AJAX code downloaded
+into that window refers to the public IP address of a console proxy VM.
+There is exactly one public IP address allocated per console proxy VM.
+The AJAX application connects to this IP. The console proxy then proxies
+the connection to the VNC port for the requested VM on the Host hosting
+the guest.
+
+.. note::
+ The hypervisors will have many ports assigned to VNC usage so that
+ multiple VNC sessions can occur simultaneously.
+
+There is never any traffic to the guest virtual IP, and there is no need
+to enable VNC within the guest.
+
+The console proxy VM will periodically report its active session count
+to the Management Server. The default reporting interval is five
+seconds. This can be changed through standard Management Server
+configuration with the parameter consoleproxy.loadscan.interval.
+
+Assignment of guest VM to console proxy is determined by first
+determining if the guest VM has a previous session associated with a
+console proxy. If it does, the Management Server will assign the guest
+VM to the target Console Proxy VM regardless of the load on the proxy
+VM. Failing that, the first available running Console Proxy VM that has
+the capacity to handle new sessions is used.
+
+Console proxies can be restarted by administrators but this will
+interrupt existing console sessions for users.
+
+
+Using a SSL Certificate for the Console Proxy
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+By default, the console viewing functionality uses plaintext HTTP. In
+any production environment, the console proxy connection should be
+encrypted via SSL at the mininum.
+
+A CloudStack administrator has 2 ways to secure the console proxy
+communication with SSL:
+
+- Set up a SSL wild-card certificate and domain name resolution
+
+- Set up SSL certificate for specific FQDN and configure load-balancer
+
+
+Changing the Console Proxy SSL Certificate and Domain
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The administrator can configure SSL encryption by selecting a domain
+and uploading a new SSL certificate and private key. The domain must
+run a DNS service that is capable of resolving queries for addresses
+of the form aaa-bbb-ccc-ddd.your.domain to an IPv4 IP address in the
+form aaa.bbb.ccc.ddd, for example, 202.8.44.1. To change the console
+proxy domain, SSL certificate, and private key:
+
+#. Set up dynamic name resolution or populate all possible DNS names in
+ your public IP range into your existing DNS server with the format
+ aaa-bbb-ccc-ddd.consoleproxy.company.com -> aaa.bbb.ccc.ddd.
+
+ .. note::
+ In these steps you will notice *consoleproxy.company.com* -For
+ security best practices, we recommend creating a wildcard SSL
+ certificate on a separate subdomain so in the event that the
+ certificate is compromised, a malicious user cannot impersonate
+ a company.com domain.
+
+#. Generate the private key and certificate signing request (CSR). When
+ you are using openssl to generate private/public key pairs and CSRs,
+ for the private key that you are going to paste into the CloudStack
+ UI, be sure to convert it into PKCS#8 format.
+
+ #. Generate a new 2048-bit private key
+
+ .. code:: bash
+
+ openssl genrsa -des3 -out yourprivate.key 2048
+
+ #. Generate a new certificate CSR. Ensure the creation of a wildcard
+ certificate, eg ``*.consoleproxy.company.com``
+
+ .. code:: bash
+
+ openssl req -new -key yourprivate.key -out yourcertificate.csr
+
+ #. Head to the website of your favorite trusted Certificate
+ Authority, purchase an SSL certificate, and submit the CSR. You
+ should receive a valid certificate in return
+
+ #. Convert your private key format into PKCS#8 encrypted format.
+
+ .. code:: bash
+
+ openssl pkcs8 -topk8 -in yourprivate.key -out yourprivate.pkcs8.encrypted.key
+
+ #. Convert your PKCS#8 encrypted private key into the PKCS#8 format
+ that is compliant with CloudStack
+
+ .. code:: bash
+
+ openssl pkcs8 -in yourprivate.pkcs8.encrypted.key -out yourprivate.pkcs8.key
+
+#. In the Update SSL Certificate screen of the CloudStack UI, paste the
+ following:
+
+ - The certificate you've just generated.
+
+ - The private key you've just generated.
+
+ - The desired domain name, prefixed with ``*.``; for example, ``*.consoleproxy.company.com``
+
+ |update-ssl.png|
+
+#. This stops all currently running console proxy VMs, then restarts
+ them with the new certificate and key. Users might notice a brief
+ interruption in console availability.
+
+The Management Server generates URLs of the form
+"aaa-bbb-ccc-ddd.consoleproxy.company.com" after this change is made.
+The new console requests will be served with the new DNS domain name,
+certificate, and key.
+
+Uploading ROOT CA and Intermediate CA
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+If you need to upload custom certificate with ROOT CA and intermediate CA, you can find more details here:
+https://cwiki.apache.org/confluence/display/CLOUDSTACK/Procedure+to+Replace+realhostip.com+with+Your+Own+Domain+Name
+
+IMPORTANT NOTES:
+
+In order to avoid errors and problems while uploading custom certificates, please check following:
+
+1. While doing URL encoding of ROOT CA and any Intermediate CA, be sure that the plus signs ("+") inside certificates
+are not replaced by space (" "), because some URL/string encoding tools tend to do that.
+
+2. If you are renewing certificates it might happen you need to upload new ROOT CA and Intermediate CA, together with new Server Certificate and key.
+In this case please be sure to use same names for certificates during API upload of certificate, example:
+
+http://123.123.123.123:8080/client/api?command=uploadCustomCertificate&...&name=root1...
+http://123.123.123.123:8080/client/api?command=uploadCustomCertificate&...&name=intermed1...
+
+Here names are "root1" and "intermed1".
+If you used other names previously, please check the cloud.keystore table to obtain used names.
+
+If you still have problems and folowing errors in management.log while destroying CPVM:
+
+- Unable to build keystore for CPVMCertificate due to CertificateException
+- Cold not find and construct a valid SSL certificate
+
+that means that still some of the Root/intermediate/server certificates or the key is not in a good format, or incorrectly encoded or multiply Root CA/Intemediate CA present in database by mistake.
+
+Other way to renew Certificates (Root,Intermediates,Server certificates and key) - although not recommended
+unless you fill comfortable - is to directly edit the database,
+while still respect the main requirement that the private key is PKCS8 encoded, while Root CA, Intemediate and Server certificates
+are still in default PEM format (no URL encoding needed here).
+After editing the database, please restart management server, and destroy SSVM and CPVM after that,
+so the new SSVM and CPVM with new certificates are created.
+
+Load-balancing Console Proxies
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+An alternative to using dynamic DNS or creating a range of DNS entries
+as described in the last section would be to create a SSL certificate
+for a specific domain name, configure CloudStack to use that particular
+FQDN, and then configure a load balancer to load balance the console
+proxy's IP address behind the FQDN. As the functionality for this is
+still new, please see
+https://cwiki.apache.org/confluence/display/CLOUDSTACK/Realhost+IP+changes
+for more details.
+
+
+Virtual Router
+--------------
+
+The virtual router is a type of System Virtual Machine. The virtual
+router is one of the most frequently used service providers in
+CloudStack. The end user has no direct access to the virtual router.
+Users can ping the virtual router and take actions that affect it (such
+as setting up port forwarding), but users do not have SSH access into
+the virtual router.
+
+There is no mechanism for the administrator to log in to the virtual
+router. Virtual routers can be restarted by administrators, but this
+will interrupt public network access and other services for end users. A
+basic test in debugging networking issues is to attempt to ping the
+virtual router from a guest VM. Some of the characteristics of the
+virtual router are determined by its associated system service offering.
+
+
+Configuring the Virtual Router
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can set the following:
+
+- IP range
+
+- Supported network services
+
+- Default domain name for the network serviced by the virtual router
+
+- Gateway IP address
+
+- How often CloudStack fetches network usage statistics from CloudStack
+ virtual routers. If you want to collect traffic metering data from
+ the virtual router, set the global configuration parameter
+ router.stats.interval. If you are not using the virtual router to
+ gather network usage statistics, set it to 0.
+
+
+Upgrading a Virtual Router with System Service Offerings
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When CloudStack creates a virtual router, it uses default settings which
+are defined in a default system service offering. See `“System Service
+Offerings” <#system-service-offerings>`_. All the
+virtual routers in a single guest network use the same system service
+offering. You can upgrade the capabilities of the virtual router by
+creating and applying a custom system service offering.
+
+#. Define your custom system service offering.
+ See `“Creating a New System Service Offering”
+ <#creating-a-new-system-service-offering>`_.
+ In System VM Type, choose Domain Router.
+
+#. Associate the system service offering with a network offering. See
+ `“Creating a New Network Offering”
+ <networking.html#creating-a-new-network-offering>`_.
+
+#. Apply the network offering to the network where you want the virtual
+ routers to use the new system service offering. If this is a new
+ network, follow the steps in Adding an Additional Guest Network on
+ page 66. To change the service offering for existing virtual routers,
+ follow the steps in `“Changing the Network Offering on a Guest Network”
+ <networking2.html#changing-the-network-offering-on-a-guest-network>`_.
+
+
+Best Practices for Virtual Routers
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- WARNING: Restarting a virtual router from a hypervisor console
+ deletes all the iptables rules. To work around this issue, stop the
+ virtual router and start it from the CloudStack UI.
+
+- .. warning::
+ Do not use the destroyRouter API when only one router is available
+ in the network, because restartNetwork API with the cleanup=false
+ parameter can't recreate it later. If you want to destroy and
+ recreate the single router available in the network, use the
+ restartNetwork API with the cleanup=true parameter.
+
+
+Service Monitoring Tool for Virtual Router
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Various services running on the CloudStack virtual routers can be
+monitored by using a Service Monitoring tool. The tool ensures that
+services are successfully running until CloudStack deliberately disables
+them. If a service goes down, the tool automatically restarts the
+service, and if that does not help bringing up the service, an alert as
+well as an event is generated indicating the failure. A new global
+parameter, ``network.router.enableservicemonitoring``, has been
+introduced to control this feature. The default value is false, implies,
+monitoring is disabled. When you enable, ensure that the Management
+Server and the router are restarted.
+
+Monitoring tool can help to start a VR service, which is crashed due to
+an unexpected reason. For example:
+
+- The services crashed due to defects in the source code.
+
+- The services that are terminated by the OS when memory or CPU is not
+ sufficiently available for the service.
+
+.. note::
+ Only those services with daemons are monitored. The services that are
+ failed due to errors in the service/daemon configuration file cannot
+ be restarted by the Monitoring tool. VPC networks are not supported.
+
+The following services are monitored in a VR:
+
+- DNS
+
+- HA Proxy
+
+- SSH
+
+- Apache Web Server
+
+The following networks are supported:
+
+- Isolated Networks
+
+- Shared Networks in both Advanced and Basic zone
+
+ .. note:: VPC networks are not supported
+
+This feature is supported on the following hypervisors: XenServer,
+VMware, and KVM.
+
+
+Enhanced Upgrade for Virtual Routers
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Upgrading VR is made flexible. The CloudStack administrators will be
+able to control the sequence of the VR upgrades. The sequencing is based
+on Infrastructure hierarchy, such as by Cluster, Pod, or Zone, and
+Administrative (Account) hierarchy, such as by Tenant or Domain. As an
+administrator, you can also determine when a particular customer
+service, such as VR, is upgraded within a specified upgrade interval.
+Upgrade operation is enhanced to increase the upgrade speed by allowing
+as many upgrade operations in parallel as possible.
+
+During the entire duration of the upgrade, users cannot launch new
+services or make changes to an existing service.
+
+Additionally, using multiple versions of VRs in a single instance is
+supported. In the Details tab of a VR, you can view the version and
+whether it requires upgrade. During the Management Server upgrade,
+CloudStack checks whether VR is at the latest version before performing
+any operation on the VR. To support this, a new global parameter,
+*``router.version.check``*, has been added. This parameter is set to
+true by default, which implies minimum required version is checked
+before performing any operation. No operation is performed if the VR is
+not at the required version. Services of the older version VR continue
+to be available, but no further operations can be performed on the VR
+until it is upgraded to the latest version. This will be a transient
+state until the VR is upgraded. This will ensure that the availability
+of VR services and VR state is not impacted due to the Management Server
+upgrade.
+
+The following service will be available even if the VR is not upgraded.
+However, no changes for any of the services can be sent to the VR, until
+it is upgraded:
+
+- SecurityGroup
+
+- UserData
+
+- DHCP
+
+- DNS
+
+- LB
+
+- Port Forwarding
+
+- VPN
+
+- Static NAT
+
+- Source NAT
+
+- Firewall
+
+- Gateway
+
+- NetworkACL
+
+
+Supported Virtual Routers
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+- VR
+
+- VPC VR
+
+- Redundant VR
+
+
+Upgrading Virtual Routers
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. Download the latest System VM template.
+
+#. Download the latest System VM to all the primary storage pools.
+
+#. Upgrade the Management Server.
+
+#. Upgrade CPVM and SSVM either from the UI or by using the following
+ script:
+
+ .. code:: bash
+
+ # cloudstack-sysvmadm -d <IP address> -u cloud -p -s
+
+ Even when the VRs are still on older versions, existing services will
+ continue to be available to the VMs. The Management Server cannot
+ perform any operations on the VRs until they are upgraded.
+
+#. Selectively upgrade the VRs:
+
+ #. Log in to the CloudStack UI as the root administrator.
+
+ #. In the left navigation, choose Infrastructure.
+
+ #. On Virtual Routers, click View More.
+
+ All the VRs are listed in the Virtual Routers page.
+
+ #. In Select View drop-down, select desired grouping based on your
+ requirement.
+
+ You can use either of the following:
+
+ - Group by zone
+
+ - Group by pod
+
+ - Group by cluster
+
+ - Group by account
+
+ #. Click the group which has the VRs to be upgraded.
+
+ For example, if you have selected Group by zone, select the name
+ of the desired zone.
+
+ #. Click the Upgrade button to upgrade all the VRs. |vr-upgrade.png|
+
+ #. Click OK to confirm.
+
+
+Secondary Storage VM
+--------------------
+
+In addition to the hosts, CloudStack’s Secondary Storage VM mounts and
+writes to secondary storage.
+
+Submissions to secondary storage go through the Secondary Storage VM.
+The Secondary Storage VM can retrieve templates and ISO images from URLs
+using a variety of protocols.
+
+The secondary storage VM provides a background task that takes care of a
+variety of secondary storage activities: downloading a new template to a
+Zone, copying templates between Zones, and snapshot backups.
+
+The administrator can log in to the secondary storage VM if needed.
+
+
+.. |update-ssl.png| image:: /_static/images/update-ssl.png
+ :alt: Updating Console Proxy SSL Certificate
+.. |vr-upgrade.png| image:: /_static/images/vr-upgrade.png
+ :alt: Button to upgrade VR to use the new template.
diff --git a/source/adminguide/templates.rst b/source/adminguide/templates.rst
new file mode 100644
index 0000000..ed60295
--- /dev/null
+++ b/source/adminguide/templates.rst
@@ -0,0 +1,313 @@
+.. 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.
+
+
+A template is a reusable configuration for virtual machines. When users
+launch VMs, they can choose from a list of templates in CloudStack.
+
+Specifically, a template is a virtual disk image that includes one of a
+variety of operating systems, optional additional software such as
+office applications, and settings such as access control to determine
+who can use the template. Each template is associated with a particular
+type of hypervisor, which is specified when the template is added to
+CloudStack.
+
+CloudStack ships with a default template. In order to present more
+choices to users, CloudStack administrators and users can create
+templates and add them to CloudStack.
+
+
+Creating Templates: Overview
+----------------------------
+
+CloudStack ships with a default template for the CentOS operating
+system. There are a variety of ways to add more templates.
+Administrators and end users can add templates. The typical sequence of
+events is:
+
+#. Launch a VM instance that has the operating system you want. Make any
+ other desired configuration changes to the VM.
+
+#. Stop the VM.
+
+#. Convert the volume into a template.
+
+There are other ways to add templates to CloudStack. For example, you
+can take a snapshot of the VM's volume and create a template from the
+snapshot, or import a VHD from another system into CloudStack.
+
+The various techniques for creating templates are described in the next
+few sections.
+
+
+Requirements for Templates
+--------------------------
+
+- For XenServer, install PV drivers / Xen tools on each template that
+ you create. This will enable live migration and clean guest shutdown.
+
+- For vSphere, install VMware Tools on each template that you create.
+ This will enable console view to work properly.
+
+
+Best Practices for Templates
+----------------------------
+
+If you plan to use large templates (100 GB or larger), be sure you have
+a 10-gigabit network to support the large templates. A slower network
+can lead to timeouts and other errors when large templates are used.
+
+
+The Default Template
+--------------------
+
+CloudStack includes a CentOS template. This template is downloaded by
+the Secondary Storage VM after the primary and secondary storage are
+configured. You can use this template in your production deployment or
+you can delete it and use custom templates.
+
+The root password for the default template is "password".
+
+A default template is provided for each of XenServer, KVM, and vSphere.
+The templates that are downloaded depend on the hypervisor type that is
+available in your cloud. Each template is approximately 2.5 GB physical
+size.
+
+The default template includes the standard iptables rules, which will
+block most access to the template excluding ssh.
+
+.. code:: bash
+
+ # iptables --list
+ Chain INPUT (policy ACCEPT)
+ target prot opt source destination
+ RH-Firewall-1-INPUT all -- anywhere anywhere
+
+ Chain FORWARD (policy ACCEPT)
+ target prot opt source destination
+ RH-Firewall-1-INPUT all -- anywhere anywhere
+
+ Chain OUTPUT (policy ACCEPT)
+ target prot opt source destination
+
+ Chain RH-Firewall-1-INPUT (2 references)
+ target prot opt source destination
+ ACCEPT all -- anywhere anywhere
+ ACCEPT icmp -- anywhere anywhere icmp any
+ ACCEPT esp -- anywhere anywhere
+ ACCEPT ah -- anywhere anywhere
+ ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns
+ ACCEPT udp -- anywhere anywhere udp dpt:ipp
+ ACCEPT tcp -- anywhere anywhere tcp dpt:ipp
+ ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
+ ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh
+ REJECT all -- anywhere anywhere reject-with icmp-host-
+
+
+Private and Public Templates
+----------------------------
+
+When a user creates a template, it can be designated private or public.
+
+Private templates are only available to the user who created them. By
+default, an uploaded template is private.
+
+When a user marks a template as “public,” the template becomes available
+to all users in all accounts in the user's domain, as well as users in
+any other domains that have access to the Zone where the template is
+stored. This depends on whether the Zone, in turn, was defined as
+private or public. A private Zone is assigned to a single domain, and a
+public Zone is accessible to any domain. If a public template is created
+in a private Zone, it is available only to users in the domain assigned
+to that Zone. If a public template is created in a public Zone, it is
+available to all users in all domains.
+
+
+Creating a Template from an Existing Virtual Machine
+----------------------------------------------------
+
+Once you have at least one VM set up in the way you want, you can use it
+as the prototype for other VMs.
+
+#. Create and start a virtual machine using any of the techniques given
+ in `“Creating VMs” <virtual_machines.html#creating-vms>`_.
+
+#. Make any desired configuration changes on the running VM, then click
+ Stop.
+
+#. Wait for the VM to stop. When the status shows Stopped, go to the
+ next step.
+
+#. Go into "View Volumes" and select the Volume having the type "ROOT".
+
+#. Click Create Template and provide the following:
+
+ - **Name and Display Text**. These will be shown in the UI, so
+ choose something descriptive.
+
+ - **OS Type**. This helps CloudStack and the hypervisor perform
+ certain operations and make assumptions that improve the
+ performance of the guest. Select one of the following.
+
+ - If the operating system of the stopped VM is listed, choose it.
+
+ - If the OS type of the stopped VM is not listed, choose Other.
+
+ - If you want to boot from this template in PV mode, choose Other
+ PV (32-bit) or Other PV (64-bit). This choice is available only
+ for XenServere:
+
+ .. note::
+ Generally you should not choose an older version of the OS
+ than the version in the image. For example, choosing CentOS
+ 5.4 to support a CentOS 6.2 image will in general not work.
+ In those cases you should choose Other.
+
+ - **Public**. Choose Yes to make this template accessible to all
+ users of this CloudStack installation. The template will appear in
+ the Community Templates list. See `“Private and
+ Public Templates” <#private-and-public-templates>`_.
+
+ - **Password Enabled**. Choose Yes if your template has the
+ CloudStack password change script installed. See
+ :ref:`adding-password-management-to-templates`.
+
+#. Click Add.
+
+The new template will be visible in the Templates section when the
+template creation process has been completed. The template is then
+available when creating a new VM.
+
+
+Creating a Template from a Snapshot
+-----------------------------------
+
+If you do not want to stop the VM in order to use the Create Template
+menu item (as described in `“Creating a Template from an Existing
+Virtual Machine” <#creating-a-template-from-an-existing-virtual-machine>`_),
+you can create a template directly from any snapshot through the
+CloudStack UI.
+
+
+Uploading Templates
+-------------------
+
+
+vSphere Templates and ISOs
+--------------------------
+
+If you are uploading a template that was created using vSphere Client,
+be sure the OVA file does not contain an ISO. If it does, the deployment
+of VMs from the template will fail.
+
+Templates are uploaded based on a URL. HTTP is the supported access
+protocol. Templates are frequently large files. You can optionally gzip
+them to decrease upload times.
+
+To upload a template:
+
+#. In the left navigation bar, click Templates.
+
+#. Click Register Template.
+
+#. Provide the following:
+
+ - **Name and Description**. These will be shown in the UI, so choose
+ something descriptive.
+
+ - **URL**. The Management Server will download the file from the
+ specified URL, such as ``http://my.web.server/filename.vhd.gz``.
+
+ - **Zone**. Choose the zone where you want the template to be
+ available, or All Zones to make it available throughout
+ CloudStack.
+
+ - **OS Type**: This helps CloudStack and the hypervisor perform
+ certain operations and make assumptions that improve the
+ performance of the guest. Select one of the following:
+
+ - If the operating system of the stopped VM is listed, choose it.
+
+ - If the OS type of the stopped VM is not listed, choose Other.
+
+ .. note::
+ You should not choose an older version of the OS than the
+ version in the image. For example, choosing CentOS 5.4 to
+ support a CentOS 6.2 image will in general not work. In
+ those cases you should choose Other.
+
+ - **Hypervisor**: The supported hypervisors are listed. Select the
+ desired one.
+
+ - **Format**. The format of the template upload file, such as VHD or
+ OVA.
+
+ - **Password Enabled**. Choose Yes if your template has the
+ CloudStack password change script installed.
+ See :ref:`adding-password-management-to-templates`.
+
+ - **Extractable**. Choose Yes if the template is available for
+ extraction. If this option is selected, end users can download a
+ full image of a template.
+
+ - **Public**. Choose Yes to make this template accessible to all
+ users of this CloudStack installation. The template will appear in
+ the Community Templates list. See `“Private and
+ Public Templates” <#private-and-public-templates>`_.
+
+ - **Featured**. Choose Yes if you would like this template to be
+ more prominent for users to select. The template will appear in
+ the Featured Templates list. Only an administrator can make a
+ template Featured.
+
+
+Exporting Templates
+-------------------
+
+End users and Administrators may export templates from the CloudStack.
+Navigate to the template in the UI and choose the Download function from
+the Actions menu.
+
+.. include:: templates/_create_linux.rst
+
+.. include:: templates/_create_windows.rst
+
+.. include:: templates/_import_ami.rst
+
+.. include:: templates/_convert_hyperv.rst
+
+.. include:: templates/_password.rst
+
+
+Deleting Templates
+------------------
+
+Templates may be deleted. In general, when a template spans multiple
+Zones, only the copy that is selected for deletion will be deleted; the
+same template in other Zones will not be deleted. The provided CentOS
+template is an exception to this. If the provided CentOS template is
+deleted, it will be deleted from all Zones.
+
+When templates are deleted, the VMs instantiated from them will continue
+to run. However, new VMs cannot be created based on the deleted
+template.
+
+
+.. |sysmanager.png| image:: /_static/images/sysmanager.png
+ :alt: System Image Manager
+.. |software-license.png| image:: /_static/images/software-license.png
+ :alt: Depicts hiding the EULA page.
+.. |change-admin-password.png| image:: /_static/images/change-admin-password.png
+ :alt: Depicts changing the administrator password
diff --git a/source/adminguide/templates/_convert_hyperv.rst b/source/adminguide/templates/_convert_hyperv.rst
new file mode 100644
index 0000000..9e15490
--- /dev/null
+++ b/source/adminguide/templates/_convert_hyperv.rst
@@ -0,0 +1,88 @@
+Converting a Hyper-V VM to a Template
+-------------------------------------
+
+To convert a Hyper-V VM to a XenServer-compatible CloudStack template,
+you will need a standalone XenServer host with an attached NFS VHD SR.
+Use whatever XenServer version you are using with CloudStack, but use
+XenCenter 5.6 FP1 or SP2 (it is backwards compatible to 5.6).
+Additionally, it may help to have an attached NFS ISO SR.
+
+For Linux VMs, you may need to do some preparation in Hyper-V before
+trying to get the VM to work in XenServer. Clone the VM and work on the
+clone if you still want to use the VM in Hyper-V. Uninstall Hyper-V
+Integration Components and check for any references to device names in
+/etc/fstab:
+
+#. From the linux\_ic/drivers/dist directory, run make uninstall (where
+ "linux\_ic" is the path to the copied Hyper-V Integration Components
+ files).
+
+#. Restore the original initrd from backup in /boot/ (the backup is
+ named \*.backup0).
+
+#. Remove the "hdX=noprobe" entries from /boot/grub/menu.lst.
+
+#. Check /etc/fstab for any partitions mounted by device name. Change
+ those entries (if any) to mount by LABEL or UUID. You can get that
+ information with the blkid command.
+
+The next step is make sure the VM is not running in Hyper-V, then get
+the VHD into XenServer. There are two options for doing this.
+
+Option one:
+
+#. Import the VHD using XenCenter. In XenCenter, go to Tools>Virtual
+ Appliance Tools>Disk Image Import.
+
+#. Choose the VHD, then click Next.
+
+#. Name the VM, choose the NFS VHD SR under Storage, enable "Run
+ Operating System Fixups" and choose the NFS ISO SR.
+
+#. Click Next, then Finish. A VM should be created.
+
+Option two:
+
+#. Run XenConvert, under From choose VHD, under To choose XenServer.
+ Click Next.
+
+#. Choose the VHD, then click Next.
+
+#. Input the XenServer host info, then click Next.
+
+#. Name the VM, then click Next, then Convert. A VM should be created.
+
+Once you have a VM created from the Hyper-V VHD, prepare it using the
+following steps:
+
+#. Boot the VM, uninstall Hyper-V Integration Services, and reboot.
+
+#. Install XenServer Tools, then reboot.
+
+#. Prepare the VM as desired. For example, run sysprep on Windows VMs.
+ See `“Creating a Windows
+ Template” <#creating-a-windows-template>`_.
+
+Either option above will create a VM in HVM mode. This is fine for
+Windows VMs, but Linux VMs may not perform optimally. Converting a Linux
+VM to PV mode will require additional steps and will vary by
+distribution.
+
+#. Shut down the VM and copy the VHD from the NFS storage to a web
+ server; for example, mount the NFS share on the web server and copy
+ it, or from the XenServer host use sftp or scp to upload it to the
+ web server.
+
+#. In CloudStack, create a new template using the following values:
+
+ - URL. Give the URL for the VHD
+
+ - OS Type. Use the appropriate OS. For PV mode on CentOS, choose
+ Other PV (32-bit) or Other PV (64-bit). This choice is available
+ only for XenServer.
+
+ - Hypervisor. XenServer
+
+ - Format. VHD
+
+The template will be created, and you can create instances from it.
diff --git a/source/adminguide/templates/_create_linux.rst b/source/adminguide/templates/_create_linux.rst
new file mode 100644
index 0000000..24a9061
--- /dev/null
+++ b/source/adminguide/templates/_create_linux.rst
@@ -0,0 +1,261 @@
+.. 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.
+
+
+Creating a Linux Template
+-------------------------
+
+Linux templates should be prepared using this documentation in order to
+prepare your linux VMs for template deployment. For ease of
+documentation, the VM which you are configuring the template on will be
+referred to as "Template Master". This guide currently covers legacy
+setups which do not take advantage of UserData and cloud-init and
+assumes openssh-server is installed during installation.
+
+An overview of the procedure is as follow:
+
+#. Upload your Linux ISO.
+
+ For more information, see `“Adding an
+ ISO” <virtual_machines.html#adding-an-iso>`_.
+
+#. Create a VM Instance with this ISO.
+
+ For more information, see `“Creating
+ VMs” <virtual_machines.html#creating-vms>`_.
+
+#. Prepare the Linux VM
+
+#. Create a template from the VM.
+
+ For more information, see `“Creating a Template from an Existing
+ Virtual Machine” <#creating-a-template-from-an-existing-virtual-machine>`_.
+
+
+System preparation for Linux
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The following steps will prepare a basic Linux installation for
+templating.
+
+#. **Installation**
+
+ It is good practice to name your VM something generic during
+ installation, this will ensure components such as LVM do not appear
+ unique to a machine. It is recommended that the name of "localhost"
+ is used for installation.
+
+ .. warning::
+ For CentOS, it is necessary to take unique identification out of the
+ interface configuration file, for this edit
+ /etc/sysconfig/network-scripts/ifcfg-eth0 and change the content to
+ the following.
+
+ .. code:: bash
+
+ DEVICE=eth0
+ TYPE=Ethernet
+ BOOTPROTO=dhcp
+ ONBOOT=yes
+
+ The next steps updates the packages on the Template Master.
+
+ - Ubuntu
+
+ .. code:: bash
+
+ sudo -i
+ apt-get update
+ apt-get upgrade -y
+ apt-get install -y acpid ntp
+ reboot
+
+ - CentOS
+
+ .. code:: bash
+
+ ifup eth0
+ yum update -y
+ reboot
+
+#. **Password management**
+
+ .. note::
+ If preferred, custom users (such as ones created during the Ubuntu
+ installation) should be removed. First ensure the root user account
+ is enabled by giving it a password and then login as root to continue.
+
+ .. code:: bash
+
+ sudo passwd root
+ logout
+
+ As root, remove any custom user accounts created during the
+ installation process.
+
+ .. code:: bash
+
+ deluser myuser --remove-home
+
+ See :ref:`adding-password-management-to-templates` for
+ instructions to setup the password management script, this will allow
+ CloudStack to change your root password from the web interface.
+
+#. **Hostname Management**
+
+ CentOS configures the hostname by default on boot. Unfortunately
+ Ubuntu does not have this functionality, for Ubuntu installations use
+ the following steps.
+
+ - Ubuntu
+
+ The hostname of a Templated VM is set by a custom script in
+ `/etc/dhcp/dhclient-exit-hooks.d`, this script first checks if the
+ current hostname is localhost, if true, it will get the host-name,
+ domain-name and fixed-ip from the DHCP lease file and use those
+ values to set the hostname and append the `/etc/hosts` file for
+ local hostname resolution. Once this script, or a user has changed
+ the hostname from localhost, it will no longer adjust system files
+ regardless of its new hostname. The script also recreates
+ openssh-server keys, which should have been deleted before
+ templating (shown below). Save the following script to
+ `/etc/dhcp/dhclient-exit-hooks.d/sethostname`, and adjust the
+ permissions.
+
+ .. code:: bash
+
+ #!/bin/sh
+ # dhclient change hostname script for Ubuntu
+ oldhostname=$(hostname -s)
+ if [ $oldhostname = 'localhost' ]
+ then
+ sleep 10 # Wait for configuration to be written to disk
+ hostname=$(cat /var/lib/dhcp/dhclient.eth0.leases | awk ' /host-name/ { host = $3 } END { printf host } ' | sed 's/[";]//g' )
+ fqdn="$hostname.$(cat /var/lib/dhcp/dhclient.eth0.leases | awk ' /domain-name/ { domain = $3 } END { printf domain } ' | sed 's/[";]//g')"
+ ip=$(cat /var/lib/dhcp/dhclient.eth0.leases | awk ' /fixed-address/ { lease = $2 } END { printf lease } ' | sed 's/[";]//g')
+ echo "cloudstack-hostname: Hostname _localhost_ detected. Changing hostname and adding hosts."
+ printf " Hostname: $hostname\n FQDN: $fqdn\n IP: $ip"
+ # Update /etc/hosts
+ awk -v i="$ip" -v f="$fqdn" -v h="$hostname" "/^127/{x=1} !/^127/ && x { x=0; print i,f,h; } { print $0; }" /etc/hosts > /etc/hosts.dhcp.tmp
+ mv /etc/hosts /etc/hosts.dhcp.bak
+ mv /etc/hosts.dhcp.tmp /etc/hosts
+ # Rename Host
+ echo $hostname > /etc/hostname
+ hostname -b -F /etc/hostname
+ echo $hostname > /proc/sys/kernel/hostname
+ # Recreate SSH2
+ export DEBIAN_FRONTEND=noninteractive
+ dpkg-reconfigure openssh-server
+ fi
+ ### End of Script ###
+
+ chmod 774 /etc/dhcp/dhclient-exit-hooks.d/sethostname
+
+ .. warning::
+ The following steps should be run when you are ready to template
+ your Template Master. If the Template Master is rebooted during
+ these steps you will have to run all the steps again. At the end
+ of this process the Template Master should be shutdown and the
+ template created in order to create and deploy the final template.
+
+#. **Remove the udev persistent device rules**
+
+ This step removes information unique to your Template Master such as
+ network MAC addresses, lease files and CD block devices, the files
+ are automatically generated on next boot.
+
+ - Ubuntu
+
+ .. code:: bash
+
+ rm -f /etc/udev/rules.d/70*
+ rm -f /var/lib/dhcp/dhclient.*
+
+ - CentOS
+
+ .. code:: bash
+
+ rm -f /etc/udev/rules.d/70*
+ rm -f /var/lib/dhclient/*
+
+#. **Remove SSH Keys**
+
+ This step is to ensure all your Templated VMs do not have the same
+ SSH keys, which would decrease the security of the machines
+ dramatically.
+
+ .. code:: bash
+
+ rm -f /etc/ssh/*key*
+
+#. **Cleaning log files**
+
+ It is good practice to remove old logs from the Template Master.
+
+ .. code:: bash
+
+ cat /dev/null > /var/log/audit/audit.log 2>/dev/null
+ cat /dev/null > /var/log/wtmp 2>/dev/null
+ logrotate -f /etc/logrotate.conf 2>/dev/null
+ rm -f /var/log/*-* /var/log/*.gz 2>/dev/null
+
+#. **Setting hostname**
+
+ In order for the Ubuntu DHCP script to function and the CentOS
+ dhclient to set the VM hostname they both require the Template
+ Master's hostname to be "localhost", run the following commands to
+ change the hostname.
+
+ .. code:: bash
+
+ hostname localhost
+ echo "localhost" > /etc/hostname
+
+#. **Set user password to expire**
+
+ This step forces the user to change the password of the VM after the
+ template has been deployed.
+
+ .. code:: bash
+
+ passwd --expire root
+
+#. **Clearing User History**
+
+ The next step clears the bash commands you have just run.
+
+ .. code:: bash
+
+ history -c
+ unset HISTFILE
+
+#. **Shutdown the VM**
+
+ Your now ready to shutdown your Template Master and create a
+ template!
+
+ .. code:: bash
+
+ halt -p
+
+#. **Create the template!**
+
+ You are now ready to create the template, for more information see
+ `“Creating a Template from an Existing Virtual
+ Machine” <#creating-a-template-from-an-existing-virtual-machine>`_.
+
+.. note::
+ Templated VMs for both Ubuntu and CentOS may require a reboot after
+ provisioning in order to pickup the hostname.
diff --git a/source/adminguide/templates/_create_windows.rst b/source/adminguide/templates/_create_windows.rst
new file mode 100644
index 0000000..cb1d554
--- /dev/null
+++ b/source/adminguide/templates/_create_windows.rst
@@ -0,0 +1,220 @@
+.. 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.
+
+
+Creating a Windows Template
+---------------------------
+
+Windows templates must be prepared with Sysprep before they can be
+provisioned on multiple machines. Sysprep allows you to create a generic
+Windows template and avoid any possible SID conflicts.
+
+.. note::
+ (XenServer) Windows VMs running on XenServer require PV drivers, which
+ may be provided in the template or added after the VM is created. The
+ PV drivers are necessary for essential management functions such as
+ mounting additional volumes and ISO images, live migration, and
+ graceful shutdown.
+
+An overview of the procedure is as follows:
+
+#. Upload your Windows ISO.
+
+ For more information, see `“Adding an
+ ISO” <virtual_machines.html#adding-an-iso>`_.
+
+#. Create a VM Instance with this ISO.
+
+ For more information, see `“Creating
+ VMs” <virtual_machines.html#creating-vms>`_.
+
+#. Follow the steps in Sysprep for Windows Server 2008 R2 (below) or
+ Sysprep for Windows Server 2003 R2, depending on your version of
+ Windows Server
+
+#. The preparation steps are complete. Now you can actually create the
+ template as described in Creating the Windows Template.
+
+
+System Preparation for Windows Server 2008 R2
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+For Windows 2008 R2, you run Windows System Image Manager to create a
+custom sysprep response XML file. Windows System Image Manager is
+installed as part of the Windows Automated Installation Kit (AIK).
+Windows AIK can be downloaded from `Microsoft Download
+Center <http://www.microsoft.com/en-us/download/details.aspx?id=9085>`_.
+
+Use the following steps to run sysprep for Windows 2008 R2:
+
+.. note::
+ The steps outlined here are derived from the excellent guide by
+ Charity Shelbourne, originally published at `Windows Server 2008
+ Sysprep Mini-Setup.
+ <http://blogs.technet.com/askcore/archive/2008/10/31/automating-the-oobe-process-during-windows-server-2008-sysprep-mini-setup.aspx>`_
+
+#. Download and install the Windows AIK
+
+ .. note::
+ Windows AIK should not be installed on the Windows 2008 R2 VM you
+ just created. Windows AIK should not be part of the template you
+ create. It is only used to create the sysprep answer file.
+
+#. Copy the install.wim file in the \\sources directory of the Windows
+ 2008 R2 installation DVD to the hard disk. This is a very large file
+ and may take a long time to copy. Windows AIK requires the WIM file
+ to be writable.
+
+#. Start the Windows System Image Manager, which is part of the Windows
+ AIK.
+
+#. In the Windows Image pane, right click the Select a Windows image or
+ catalog file option to load the install.wim file you just copied.
+
+#. Select the Windows 2008 R2 Edition.
+
+ You may be prompted with a warning that the catalog file cannot be
+ opened. Click Yes to create a new catalog file.
+
+#. In the Answer File pane, right click to create a new answer file.
+
+#. Generate the answer file from the Windows System Image Manager using
+ the following steps:
+
+ #. The first page you need to automate is the Language and Country or
+ Region Selection page. To automate this, expand Components in your
+ Windows Image pane, right-click and add the
+ Microsoft-Windows-International-Core setting to Pass 7 oobeSystem.
+ In your Answer File pane, configure the InputLocale, SystemLocale,
+ UILanguage, and UserLocale with the appropriate settings for your
+ language and country or region. Should you have a question about
+ any of these settings, you can right-click on the specific setting
+ and select Help. This will open the appropriate CHM help file with
+ more information, including examples on the setting you are
+ attempting to configure.
+
+ |sysmanager.png|
+
+ #. You need to automate the Software License Terms Selection page,
+ otherwise known as the End-User License Agreement (EULA). To do
+ this, expand the Microsoft-Windows-Shell-Setup component.
+ High-light the OOBE setting, and add the setting to the Pass 7
+ oobeSystem. In Settings, set HideEULAPage true.
+
+ |software-license.png|
+
+ #. Make sure the license key is properly set. If you use MAK key, you
+ can just enter the MAK key on the Windows 2008 R2 VM. You need not
+ input the MAK into the Windows System Image Manager. If you use
+ KMS host for activation you need not enter the Product Key.
+ Details of Windows Volume Activation can be found at
+ `http://technet.microsoft.com/en-us/library/bb892849.aspx
+ <http://technet.microsoft.com/en-us/library/bb892849.aspx>`_
+
+ #. You need to automate is the Change Administrator Password page.
+ Expand the Microsoft-Windows-Shell-Setup component (if it is not
+ still expanded), expand UserAccounts, right-click on
+ AdministratorPassword, and add the setting to the Pass 7
+ oobeSystem configuration pass of your answer file. Under Settings,
+ specify a password next to Value.
+
+ |change-admin-password.png|
+
+ You may read the AIK documentation and set many more options that
+ suit your deployment. The steps above are the minimum needed to
+ make Windows unattended setup work.
+
+#. Save the answer file as unattend.xml. You can ignore the warning
+ messages that appear in the validation window.
+
+#. Copy the unattend.xml file into the c:\\windows\\system32\\sysprep
+ directory of the Windows 2008 R2 Virtual Machine
+
+#. Once you place the unattend.xml file in
+ c:\\windows\\system32\\sysprep directory, you run the sysprep tool as
+ follows:
+
+ .. code:: bash
+
+ cd c:\Windows\System32\sysprep
+ sysprep.exe /oobe /generalize /shutdown
+
+ The Windows 2008 R2 VM will automatically shut down after sysprep is
+ complete.
+
+
+System Preparation for Windows Server 2003 R2
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Earlier versions of Windows have a different sysprep tool. Follow these
+steps for Windows Server 2003 R2.
+
+#. Extract the content of \\support\\tools\\deploy.cab on the Windows
+ installation CD into a directory called c:\\sysprep on the Windows
+ 2003 R2 VM.
+
+#. Run c:\\sysprep\\setupmgr.exe to create the sysprep.inf file.
+
+ #. Select Create New to create a new Answer File.
+
+ #. Enter “Sysprep setup” for the Type of Setup.
+
+ #. Select the appropriate OS version and edition.
+
+ #. On the License Agreement screen, select “Yes fully automate the
+ installation”.
+
+ #. Provide your name and organization.
+
+ #. Leave display settings at default.
+
+ #. Set the appropriate time zone.
+
+ #. Provide your product key.
+
+ #. Select an appropriate license mode for your deployment
+
+ #. Select “Automatically generate computer name”.
+
+ #. Type a default administrator password. If you enable the password
+ reset feature, the users will not actually use this password. This
+ password will be reset by the instance manager after the guest
+ boots up.
+
+ #. Leave Network Components at “Typical Settings”.
+
+ #. Select the “WORKGROUP” option.
+
+ #. Leave Telephony options at default.
+
+ #. Select appropriate Regional Settings.
+
+ #. Select appropriate language settings.
+
+ #. Do not install printers.
+
+ #. Do not specify “Run Once commands”.
+
+ #. You need not specify an identification string.
+
+ #. Save the Answer File as c:\\sysprep\\sysprep.inf.
+
+#. Run the following command to sysprep the image:
+
+ .. code:: bash
+
+ c:\sysprep\sysprep.exe -reseal -mini -activated
+
+ After this step the machine will automatically shut down
diff --git a/source/adminguide/templates/_import_ami.rst b/source/adminguide/templates/_import_ami.rst
new file mode 100644
index 0000000..b81829f
--- /dev/null
+++ b/source/adminguide/templates/_import_ami.rst
@@ -0,0 +1,192 @@
+.. 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.
+
+
+Importing Amazon Machine Images
+-------------------------------
+
+The following procedures describe how to import an Amazon Machine Image
+(AMI) into CloudStack when using the XenServer hypervisor.
+
+Assume you have an AMI file and this file is called CentOS\_6.2\_x64.
+Assume further that you are working on a CentOS host. If the AMI is a
+Fedora image, you need to be working on a Fedora host initially.
+
+You need to have a XenServer host with a file-based storage repository
+(either a local ext3 SR or an NFS SR) to convert to a VHD once the image
+file has been customized on the Centos/Fedora host.
+
+.. note::
+ When copying and pasting a command, be sure the command has pasted as
+ a single line before executing. Some document viewers may introduce
+ unwanted line breaks in copied text.
+
+To import an AMI:
+
+#. Set up loopback on image file:
+
+ .. code:: bash
+
+ # mkdir -p /mnt/loop/centos62
+ # mount -o loop CentOS_6.2_x64 /mnt/loop/centos54
+
+#. Install the kernel-xen package into the image. This downloads the PV
+ kernel and ramdisk to the image.
+
+ .. code:: bash
+
+ # yum -c /mnt/loop/centos54/etc/yum.conf --installroot=/mnt/loop/centos62/ -y install kernel-xen
+
+#. Create a grub entry in /boot/grub/grub.conf.
+
+ .. code:: bash
+
+ # mkdir -p /mnt/loop/centos62/boot/grub
+ # touch /mnt/loop/centos62/boot/grub/grub.conf
+ # echo "" > /mnt/loop/centos62/boot/grub/grub.conf
+
+#. Determine the name of the PV kernel that has been installed into the
+ image.
+
+ .. code:: bash
+
+ # cd /mnt/loop/centos62
+ # ls lib/modules/
+ 2.6.16.33-xenU 2.6.16-xenU 2.6.18-164.15.1.el5xen 2.6.18-164.6.1.el5.centos.plus 2.6.18-xenU-ec2-v1.0 2.6.21.7-2.fc8xen 2.6.31-302-ec2
+ # ls boot/initrd*
+ boot/initrd-2.6.18-164.6.1.el5.centos.plus.img boot/initrd-2.6.18-164.15.1.el5xen.img
+ # ls boot/vmlinuz*
+ boot/vmlinuz-2.6.18-164.15.1.el5xen boot/vmlinuz-2.6.18-164.6.1.el5.centos.plus boot/vmlinuz-2.6.18-xenU-ec2-v1.0 boot/vmlinuz-2.6.21-2952.fc8xen
+
+ Xen kernels/ramdisk always end with "xen". For the kernel version you
+ choose, there has to be an entry for that version under lib/modules,
+ there has to be an initrd and vmlinuz corresponding to that. Above,
+ the only kernel that satisfies this condition is
+ 2.6.18-164.15.1.el5xen.
+
+#. Based on your findings, create an entry in the grub.conf file. Below
+ is an example entry.
+
+ .. code:: bash
+
+ default=0
+ timeout=5
+ hiddenmenu
+ title CentOS (2.6.18-164.15.1.el5xen)
+ root (hd0,0)
+ kernel /boot/vmlinuz-2.6.18-164.15.1.el5xen ro root=/dev/xvda
+ initrd /boot/initrd-2.6.18-164.15.1.el5xen.img
+
+#. Edit etc/fstab, changing “sda1” to “xvda” and changing “sdb” to
+ “xvdb”.
+
+ .. code:: bash
+
+ # cat etc/fstab
+ /dev/xvda / ext3 defaults 1 1
+ /dev/xvdb /mnt ext3 defaults 0 0
+ none /dev/pts devpts gid=5,mode=620 0 0
+ none /proc proc defaults 0 0
+ none /sys sysfs defaults 0 0
+
+#. Enable login via the console. The default console device in a
+ XenServer system is xvc0. Ensure that etc/inittab and etc/securetty
+ have the following lines respectively:
+
+ .. code:: bash
+
+ # grep xvc0 etc/inittab
+ co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav
+ # grep xvc0 etc/securetty
+ xvc0
+
+#. Ensure the ramdisk supports PV disk and PV network. Customize this
+ for the kernel version you have determined above.
+
+ .. code:: bash
+
+ # chroot /mnt/loop/centos54
+ # cd /boot/
+ # mv initrd-2.6.18-164.15.1.el5xen.img initrd-2.6.18-164.15.1.el5xen.img.bak
+ # mkinitrd -f /boot/initrd-2.6.18-164.15.1.el5xen.img --with=xennet --preload=xenblk --omit-scsi-modules 2.6.18-164.15.1.el5xen
+
+#. Change the password.
+
+ .. code:: bash
+
+ # passwd
+ Changing password for user root.
+ New UNIX password:
+ Retype new UNIX password:
+ passwd: all authentication tokens updated successfully.
+
+#. Exit out of chroot.
+
+ .. code:: bash
+
+ # exit
+
+#. Check `etc/ssh/sshd_config` for lines allowing ssh login using a
+ password.
+
+ .. code:: bash
+
+ # egrep "PermitRootLogin|PasswordAuthentication" /mnt/loop/centos54/etc/ssh/sshd_config
+ PermitRootLogin yes
+ PasswordAuthentication yes
+
+#. If you need the template to be enabled to reset passwords from the
+ CloudStack UI or API, install the password change script into the
+ image at this point. See :ref:`adding-password-management-to-templates`.
+
+#. Unmount and delete loopback mount.
+
+ .. code:: bash
+
+ # umount /mnt/loop/centos54
+ # losetup -d /dev/loop0
+
+#. Copy the image file to your XenServer host's file-based storage
+ repository. In the example below, the Xenserver is "xenhost". This
+ XenServer has an NFS repository whose uuid is
+ a9c5b8c8-536b-a193-a6dc-51af3e5ff799.
+
+ .. code:: bash
+
+ # scp CentOS_6.2_x64 xenhost:/var/run/sr-mount/a9c5b8c8-536b-a193-a6dc-51af3e5ff799/
+
+#. Log in to the Xenserver and create a VDI the same size as the image.
+
+ .. code:: bash
+
+ [root@xenhost ~]# cd /var/run/sr-mount/a9c5b8c8-536b-a193-a6dc-51af3e5ff799
+ [root@xenhost a9c5b8c8-536b-a193-a6dc-51af3e5ff799]# ls -lh CentOS_6.2_x64
+ -rw-r--r-- 1 root root 10G Mar 16 16:49 CentOS_6.2_x64
+ [root@xenhost a9c5b8c8-536b-a193-a6dc-51af3e5ff799]# xe vdi-create virtual-size=10GiB sr-uuid=a9c5b8c8-536b-a193-a6dc-51af3e5ff799 type=user name-label="Centos 6.2 x86_64"
+ cad7317c-258b-4ef7-b207-cdf0283a7923
+
+#. Import the image file into the VDI. This may take 10–20 minutes.
+
+ .. code:: bash
+
+ [root@xenhost a9c5b8c8-536b-a193-a6dc-51af3e5ff799]# xe vdi-import filename=CentOS_6.2_x64 uuid=cad7317c-258b-4ef7-b207-cdf0283a7923
+
+#. Locate a the VHD file. This is the file with the VDI’s UUID as its
+ name. Compress it and upload it to your web server.
+
+ .. code:: bash
+
+ [root@xenhost a9c5b8c8-536b-a193-a6dc-51af3e5ff799]# bzip2 -c cad7317c-258b-4ef7-b207-cdf0283a7923.vhd > CentOS_6.2_x64.vhd.bz2
+ [root@xenhost a9c5b8c8-536b-a193-a6dc-51af3e5ff799]# scp CentOS_6.2_x64.vhd.bz2 webserver:/var/www/html/templates/
diff --git a/source/adminguide/templates/_password.rst b/source/adminguide/templates/_password.rst
new file mode 100644
index 0000000..dffde52
--- /dev/null
+++ b/source/adminguide/templates/_password.rst
@@ -0,0 +1,85 @@
+.. 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-password-management-to-templates:
+
+Adding Password Management to Your Templates
+--------------------------------------------
+
+CloudStack provides an optional password reset feature that allows users
+to set a temporary admin or root password as well as reset the existing
+admin or root password from the CloudStack UI.
+
+To enable the Reset Password feature, you will need to download an
+additional script to patch your template. When you later upload the
+template into CloudStack, you can specify whether reset admin/root
+password feature should be enabled for this template.
+
+The password management feature works always resets the account password
+on instance boot. The script does an HTTP call to the virtual router to
+retrieve the account password that should be set. As long as the virtual
+router is accessible the guest will have access to the account password
+that should be used. When the user requests a password reset the
+management server generates and sends a new password to the virtual
+router for the account. Thus an instance reboot is necessary to effect
+any password changes.
+
+If the script is unable to contact the virtual router during instance
+boot it will not set the password but boot will continue normally.
+
+
+Linux OS Installation
+~~~~~~~~~~~~~~~~~~~~~
+
+Use the following steps to begin the Linux OS installation:
+
+#. Download the script file cloud-set-guest-password:
+
+ - `http://download.cloud.com/templates/4.2/bindir/cloud-set-guest-password.in
+ <http://download.cloud.com/templates/4.2/bindir/cloud-set-guest-password.in>`_
+
+#. Rename the file:
+
+ .. code:: bash
+
+ mv cloud-set-guest-password.in cloud-set-guest-password
+
+#. Copy this file to /etc/init.d.
+
+ On some Linux distributions, copy the file to ``/etc/rc.d/init.d``.
+
+#. Run the following command to make the script executable:
+
+ .. code:: bash
+
+ chmod +x /etc/init.d/cloud-set-guest-password
+
+#. Depending on the Linux distribution, continue with the appropriate
+ step.
+
+ On Fedora, CentOS/RHEL, and Debian, run:
+
+ .. code:: bash
+
+ chkconfig --add cloud-set-guest-password
+
+
+Windows OS Installation
+~~~~~~~~~~~~~~~~~~~~~~~
+
+Download the installer, CloudInstanceManager.msi, from the `Download
+page <http://sourceforge.net/projects/cloudstack/files/Password%20Management%20Scripts/CloudInstanceManager.msi/download>`_
+and run the installer in the newly created Windows VM.
diff --git a/source/adminguide/troubleshooting.rst b/source/adminguide/troubleshooting.rst
new file mode 100644
index 0000000..667c727
--- /dev/null
+++ b/source/adminguide/troubleshooting.rst
@@ -0,0 +1,456 @@
+.. 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.
+
+
+TroubleShooting
+===============
+
+Working with Server Logs
+------------------------
+
+The CloudStack Management Server logs all web site, middle tier, and
+database activities for diagnostics purposes in
+`/var/log/cloudstack/management/`. The CloudStack logs a variety of error
+messages. We recommend this command to find the problematic output in
+the Management Server log:.
+
+.. note::
+ When copying and pasting a command, be sure the command has pasted as a
+ single line before executing. Some document viewers may introduce
+ unwanted line breaks in copied text.
+
+.. code:: bash
+
+ grep -i -E 'exception|unable|fail|invalid|leak|warn|error' /var/log/cloudstack/management/management-server.log
+
+The CloudStack processes requests with a Job ID. If you find an error in
+the logs and you are interested in debugging the issue you can grep for
+this job ID in the management server log. For example, suppose that you
+find the following ERROR message:
+
+.. code:: bash
+
+ 2010-10-04 13:49:32,595 ERROR [cloud.vm.UserVmManagerImpl] (Job-Executor-11:job-1076) Unable to find any host for [User|i-8-42-VM-untagged]
+
+Note that the job ID is 1076. You can track back the events relating to
+job 1076 with the following grep:
+
+.. code:: bash
+
+ grep "job-1076)" management-server.log
+
+The CloudStack Agent Server logs its activities in `/var/log/cloudstack/agent/`.
+
+
+Data Loss on Exported Primary Storage
+-------------------------------------
+
+Symptom
+~~~~~~~
+
+Loss of existing data on primary storage which has been exposed as a
+Linux NFS server export on an iSCSI volume.
+
+
+Cause
+~~~~~
+
+It is possible that a client from outside the intended pool has mounted
+the storage. When this occurs, the LVM is wiped and all data in the
+volume is lost
+
+
+Solution
+~~~~~~~~
+
+When setting up LUN exports, restrict the range of IP addresses that are
+allowed access by specifying a subnet mask. For example:
+
+.. code:: bash
+
+ echo “/export 192.168.1.0/24(rw,async,no_root_squash,no_subtree_check)” > /etc/exports
+
+Adjust the above command to suit your deployment needs.
+
+
+More Information
+~~~~~~~~~~~~~~~~
+
+See the export procedure in the "Secondary Storage" section of the
+CloudStack Installation Guide
+
+
+Recovering a Lost Virtual Router
+--------------------------------
+
+Symptom
+~~~~~~~
+
+A virtual router is running, but the host is disconnected. A virtual
+router no longer functions as expected.
+
+
+Cause
+~~~~~
+
+The Virtual router is lost or down.
+
+
+Solution
+~~~~~~~~
+
+If you are sure that a virtual router is down forever, or no longer
+functions as expected, destroy it. You must create one afresh while
+keeping the backup router up and running (it is assumed this is in a
+redundant router setup):
+
+- Force stop the router. Use the stopRouter API with forced=true
+ parameter to do so.
+
+- Before you continue with destroying this router, ensure that the
+ backup router is running. Otherwise the network connection will be
+ lost.
+
+- Destroy the router by using the destroyRouter API.
+
+Recreate the missing router by using the restartNetwork API with
+cleanup=false parameter. For more information about redundant router
+setup, see Creating a New Network Offering.
+
+For more information about the API syntax, see the API Reference at
+`http://cloudstack.apache.org/docs/api/ <http://cloudstack.apache.org/docs/api/>`_.
+
+
+Maintenance mode not working on vCenter
+---------------------------------------
+
+Symptom
+~~~~~~~
+
+Host was placed in maintenance mode, but still appears live in vCenter.
+
+
+Cause
+~~~~~~
+
+The CloudStack administrator UI was used to place the host in scheduled
+maintenance mode. This mode is separate from vCenter's maintenance mode.
+
+
+Solution
+~~~~~~~~
+
+Use vCenter to place the host in maintenance mode.
+
+
+Unable to deploy VMs from uploaded vSphere template
+---------------------------------------------------
+
+Symptom
+~~~~~~~~
+
+When attempting to create a VM, the VM will not deploy.
+
+
+Cause
+~~~~~
+
+If the template was created by uploading an OVA file that was created
+using vSphere Client, it is possible the OVA contained an ISO image. If
+it does, the deployment of VMs from the template will fail.
+
+
+Solution
+~~~~~~~~
+
+Remove the ISO and re-upload the template.
+
+
+Unable to power on virtual machine on VMware
+--------------------------------------------
+
+Symptom
+~~~~~~~
+
+Virtual machine does not power on. You might see errors like:
+
+- Unable to open Swap File
+
+- Unable to access a file since it is locked
+
+- Unable to access Virtual machine configuration
+
+
+Cause
+~~~~~
+
+A known issue on VMware machines. ESX hosts lock certain critical
+virtual machine files and file systems to prevent concurrent changes.
+Sometimes the files are not unlocked when the virtual machine is powered
+off. When a virtual machine attempts to power on, it can not access
+these critical files, and the virtual machine is unable to power on.
+
+
+Solution
+~~~~~~~~
+
+See the following:
+
+`VMware Knowledge Base Article
+<http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=10051/>`_
+
+
+Load balancer rules fail after changing network offering
+--------------------------------------------------------
+
+Symptom
+~~~~~~~
+
+After changing the network offering on a network, load balancer rules
+stop working.
+
+
+Cause
+~~~~~
+
+Load balancing rules were created while using a network service offering
+that includes an external load balancer device such as NetScaler, and
+later the network service offering changed to one that uses the
+CloudStack virtual router.
+
+
+Solution
+~~~~~~~~
+
+Create a firewall rule on the virtual router for each of your existing
+load balancing rules so that they continue to function.
+
+
+Troubleshooting Internet Traffic
+--------------------------------
+
+Below are a few troubleshooting steps to check whats going wrong with your
+network...
+
+
+Trouble Shooting Steps
+~~~~~~~~~~~~~~~~~~~~~~
+
+#. The switches have to be configured correctly to pass VLAN traffic. You can
+ verify if VLAN traffic is working by bringing up a tagged interface on the
+ hosts and pinging between them as below...
+
+ On *host1 (kvm1)*
+
+ ::
+
+ kvm1 ~$ vconfig add eth0 64
+ kvm1 ~$ ifconfig eth0.64 1.2.3.4 netmask 255.255.255.0 up
+ kvm1 ~$ ping 1.2.3.5
+
+ On *host2 (kvm2)*
+
+ ::
+
+ kvm2 ~$ vconfig add eth0 64
+ kvm2 ~$ ifconfig eth0.64 1.2.3.5 netmask 255.255.255.0 up
+ kvm2 ~$ ping 1.2.3.4
+
+ If the pings dont work, run *tcpdump(8)* all over the place to check
+ who is gobbling up the packets. Ultimately, if the switches are not
+ configured correctly, CloudStack networking wont work so fix the
+ physical networking issues before you proceed to the next steps
+
+#. Ensure `Traffic Labels <http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/about-physical-networks.html>`_ are set for the Zone.
+
+ Traffic labels need to be set for all hypervisors including
+ XenServer, KVM and VMware types. You can configure traffic labels when
+ you creating a new zone from the *Add Zone Wizard*.
+
+ .. image:: /_static/images/networking-zone-traffic-labels.png
+
+ On an existing zone, you can modify the traffic labels by going to
+ *Infrastructure, Zones, Physical Network* tab.
+
+ .. image:: /_static/images/networking-infra-traffic-labels.png
+
+ List labels using *CloudMonkey*
+
+ ::
+
+ acs-manager ~$ cloudmonkey list traffictypes physicalnetworkid=41cb7ff6-8eb2-4630-b577-1da25e0e1145
+ count = 4
+ traffictype:
+ id = cd0915fe-a660-4a82-9df7-34aebf90003e
+ kvmnetworklabel = cloudbr0
+ physicalnetworkid = 41cb7ff6-8eb2-4630-b577-1da25e0e1145
+ traffictype = Guest
+ xennetworklabel = MGMT
+ ========================================================
+ id = f5524b8f-6605-41e4-a982-81a356b2a196
+ kvmnetworklabel = cloudbr0
+ physicalnetworkid = 41cb7ff6-8eb2-4630-b577-1da25e0e1145
+ traffictype = Management
+ xennetworklabel = MGMT
+ ========================================================
+ id = 266bad0e-7b68-4242-b3ad-f59739346cfd
+ kvmnetworklabel = cloudbr0
+ physicalnetworkid = 41cb7ff6-8eb2-4630-b577-1da25e0e1145
+ traffictype = Public
+ xennetworklabel = MGMT
+ ========================================================
+ id = a2baad4f-7ce7-45a8-9caf-a0b9240adf04
+ kvmnetworklabel = cloudbr0
+ physicalnetworkid = 41cb7ff6-8eb2-4630-b577-1da25e0e1145
+ traffictype = Storage
+ xennetworklabel = MGMT
+ =========================================================
+
+#. KVM traffic labels require to be named as *"cloudbr0"*, *"cloudbr2"*,
+ *"cloudbrN"* etc and the corresponding bridge must exist on the KVM
+ hosts. If you create labels/bridges with any other names, CloudStack
+ (atleast earlier versions did) seems to ignore them. CloudStack does not
+ create the physical bridges on the KVM hosts, you need to create them
+ **before** before adding the host to Cloudstack.
+
+ ::
+
+ kvm1 ~$ ifconfig cloudbr0
+ cloudbr0 Link encap:Ethernet HWaddr 00:0C:29:EF:7D:78
+ inet addr:192.168.44.22 Bcast:192.168.44.255 Mask:255.255.255.0
+ inet6 addr: fe80::20c:29ff:feef:7d78/64 Scope:Link
+ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
+ RX packets:92435 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:50596 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:0
+ RX bytes:94985932 (90.5 MiB) TX bytes:61635793 (58.7 MiB)
+
+#. The Virtual Router, SSVM, CPVM *public* interface would be bridged to
+ a physical interface on the host. In the example below, *cloudbr0* is
+ the public interface and CloudStack has correctly created the virtual
+ interfaces bridge. This virtual interface to physical interface mapping
+ is done automatically by CloudStack using the traffic label settings for
+ the Zone. If you have provided correct settings and still dont have a
+ working working Internet, check the switching layer before you debug any
+ further. You can verify traffic using tcpdump on the virtual, physical
+ and bridge interfaces.
+
+ ::
+
+ kvm-host1 ~$ brctl show
+ bridge name bridge id STP enabled interfaces
+ breth0-64 8000.000c29ef7d78 no eth0.64
+ vnet2
+ cloud0 8000.fe00a9fe0219 no vnet0
+ cloudbr0 8000.000c29ef7d78 no eth0
+ vnet1
+ vnet3
+ virbr0 8000.5254008e321a yes virbr0-nic
+
+ ::
+
+ xenserver1 ~$ brctl show
+ bridge name bridge id STP enabled interfaces
+ xapi0 0000.e2b76d0a1149 no vif1.0
+ xenbr0 0000.000c299b54dc no eth0
+ xapi1
+ vif1.1
+ vif1.2
+
+#. Pre-create labels on the XenServer Hosts. Similar to KVM bridge
+ setup, traffic labels must also be pre-created on the XenServer hosts
+ before adding them to CloudStack.
+
+ ::
+
+ xenserver1 ~$ xe network-list
+ uuid ( RO) : aaa-bbb-ccc-ddd
+ name-label ( RW): MGMT
+ name-description ( RW):
+ bridge ( RO): xenbr0
+
+
+#. The Internet would be accessible from both the SSVM and CPVM
+ instances by default. Their public IPs will also be directly pingable
+ from the Internet. Please note that these test would work only if your
+ switches and traffic labels are configured correctly for your
+ environment. If your SSVM/CPVM cant reach the Internet, its very
+ unlikely that the Virtual Router (VR) can also the reach the Internet
+ suggesting that its either a switching issue or incorrectly assigned
+ traffic labels. Fix the SSVM/CPVM issues before you debug VR issues.
+
+ ::
+
+ root@s-1-VM:~# ping -c 3 google.com
+ PING google.com (74.125.236.164): 56 data bytes
+ 64 bytes from 74.125.236.164: icmp_seq=0 ttl=55 time=26.932 ms
+ 64 bytes from 74.125.236.164: icmp_seq=1 ttl=55 time=29.156 ms
+ 64 bytes from 74.125.236.164: icmp_seq=2 ttl=55 time=25.000 ms
+ --- google.com ping statistics ---
+ 3 packets transmitted, 3 packets received, 0% packet loss
+ round-trip min/avg/max/stddev = 25.000/27.029/29.156/1.698 ms
+
+ ::
+
+ root@v-2-VM:~# ping -c 3 google.com
+ PING google.com (74.125.236.164): 56 data bytes
+ 64 bytes from 74.125.236.164: icmp_seq=0 ttl=55 time=32.125 ms
+ 64 bytes from 74.125.236.164: icmp_seq=1 ttl=55 time=26.324 ms
+ 64 bytes from 74.125.236.164: icmp_seq=2 ttl=55 time=37.001 ms
+ --- google.com ping statistics ---
+ 3 packets transmitted, 3 packets received, 0% packet loss
+ round-trip min/avg/max/stddev = 26.324/31.817/37.001/4.364 ms
+
+
+#. The Virtual Router (VR) should also be able to reach the Internet
+ without having any Egress rules. The Egress rules only control forwarded
+ traffic and not traffic that originates on the VR itself.
+
+ ::
+
+ root@r-4-VM:~# ping -c 3 google.com
+ PING google.com (74.125.236.164): 56 data bytes
+ 64 bytes from 74.125.236.164: icmp_seq=0 ttl=55 time=28.098 ms
+ 64 bytes from 74.125.236.164: icmp_seq=1 ttl=55 time=34.785 ms
+ 64 bytes from 74.125.236.164: icmp_seq=2 ttl=55 time=69.179 ms
+ --- google.com ping statistics ---
+ 3 packets transmitted, 3 packets received, 0% packet loss
+ round-trip min/avg/max/stddev = 28.098/44.021/69.179/17.998 ms
+
+#. However, the Virtual Router's (VR) Source NAT Public IP address
+ **WONT** be reachable until appropriate Ingress rules are
+ in place. You can add *Ingress* rules under *Network, Guest Network, IP
+ Address, Firewall* setting page.
+
+ .. image:: /_static/images/networking-ingress-rule.png
+
+#. The VM Instances by default wont be able to access the Internet. Add
+ Egress rules to permit traffic.
+
+ .. image:: /_static/images/networking-egress-rule.png
+
+#. Some users have reported that flushing IPTables rules (or changing
+ routes) on the SSVM, CPVM or the Virtual Router makes the Internet work.
+ This is not expected behaviour and suggests that your networking
+ settings are incorrect. No IPtables/route changes are required on the
+ SSVM, CPVM or the VR. Go back and double check all your settings.
+
+
+In a vast majority of the cases, the problem has turned out to be at the
+switching layer where the L3 switches were configured incorrectly.
+
+This section was contibuted by Shanker Balan and was originally published on
+`Shapeblue's blog <http://shankerbalan.net/blog/internet-not-working-on-cloudstack-vms/>`_
+
diff --git a/source/adminguide/tuning.rst b/source/adminguide/tuning.rst
new file mode 100644
index 0000000..75b0954
--- /dev/null
+++ b/source/adminguide/tuning.rst
@@ -0,0 +1,125 @@
+.. 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.
+
+
+Tuning
+======
+
+This section provides tips on how to improve the performance of your
+cloud.
+
+
+Performance Monitoring
+----------------------
+
+Host and guest performance monitoring is available to end users and
+administrators. This allows the user to monitor their utilization of
+resources and determine when it is appropriate to choose a more powerful
+service offering or larger disk.
+
+
+Increase Management Server Maximum Memory
+-----------------------------------------
+
+If the Management Server is subject to high demand, the default maximum
+JVM memory allocation can be insufficient. To increase the memory:
+
+#. Edit the Tomcat configuration file:
+
+ .. code:: bash
+
+ /etc/cloudstack/management/tomcat6.conf
+
+#. Change the command-line parameter -XmxNNNm to a higher value of N.
+
+ For example, if the current value is -Xmx128m, change it to -Xmx1024m
+ or higher.
+
+#. To put the new setting into effect, restart the Management Server.
+
+ .. code:: bash
+
+ # service cloudstack-management restart
+
+For more information about memory issues, see "FAQ: Memory" at `Tomcat
+Wiki. <http://wiki.apache.org/tomcat/FAQ/Memory>`_
+
+
+Set Database Buffer Pool Size
+-----------------------------
+
+It is important to provide enough memory space for the MySQL database to
+cache data and indexes:
+
+#. Edit the MySQL configuration file:
+
+ .. code:: bash
+
+ /etc/my.cnf
+
+#. Insert the following line in the [mysqld] section, below the datadir
+ line. Use a value that is appropriate for your situation. We
+ recommend setting the buffer pool at 40% of RAM if MySQL is on the
+ same server as the management server or 70% of RAM if MySQL has a
+ dedicated server. The following example assumes a dedicated server
+ with 1024M of RAM.
+
+ .. code:: bash
+
+ innodb_buffer_pool_size=700M
+
+#. Restart the MySQL service.
+
+ .. code:: bash
+
+ # service mysqld restart
+
+For more information about the buffer pool, see "The InnoDB Buffer Pool"
+at `MySQL Reference
+Manual <http://dev.mysql.com/doc/refman/5.5/en/innodb-buffer-pool.html>`_.
+
+
+Set and Monitor Total VM Limits per Host
+----------------------------------------
+
+The CloudStack administrator should monitor the total number of VM
+instances in each cluster, and disable allocation to the cluster if the
+total is approaching the maximum that the hypervisor can handle. Be sure
+to leave a safety margin to allow for the possibility of one or more
+hosts failing, which would increase the VM load on the other hosts as
+the VMs are automatically redeployed. Consult the documentation for your
+chosen hypervisor to find the maximum permitted number of VMs per host,
+then use CloudStack global configuration settings to set this as the
+default limit. Monitor the VM activity in each cluster at all times.
+Keep the total number of VMs below a safe level that allows for the
+occasional host failure. For example, if there are N hosts in the
+cluster, and you want to allow for one host in the cluster to be down at
+any given time, the total number of VM instances you can permit in the
+cluster is at most (N-1) \* (per-host-limit). Once a cluster reaches
+this number of VMs, use the CloudStack UI to disable allocation of more
+VMs to the cluster.
+
+
+Configure XenServer dom0 Memory
+-------------------------------
+
+Configure the XenServer dom0 settings to allocate more memory to dom0.
+This can enable XenServer to handle larger numbers of virtual machines.
+We recommend 2940 MB of RAM for XenServer dom0. For instructions on how
+to do this, see `Citrix Knowledgebase
+Article <http://support.citrix.com/article/CTX126531>`_.The article
+refers to XenServer 5.6, but the same information applies to XenServer 6
+
+
diff --git a/source/adminguide/ui.rst b/source/adminguide/ui.rst
new file mode 100644
index 0000000..7c7fd81
--- /dev/null
+++ b/source/adminguide/ui.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.
+
+.. _log-in-to-ui:
+
+Log In to the UI
+----------------
+
+CloudStack provides a web-based UI that can be used by both
+administrators and end users. The appropriate version of the UI is
+displayed depending on the credentials used to log in. The UI is
+available in popular browsers including IE7, IE8, IE9, Firefox 3.5+,
+Firefox 4, Safari 4, and Safari 5. The URL is: (substitute your own
+management server IP address)
+
+.. parsed-literal::
+
+ http://<management-server-ip-address>:8080/client
+
+On a fresh Management Server installation, a guided tour splash screen
+appears. On later visits, you’ll see a login screen where you specify
+the following to proceed to your Dashboard:
+
+Username -> The user ID of your account. The default username is admin.
+
+Password -> The password associated with the user ID. The password for
+the default username is password.
+
+Domain -> If you are a root user, leave this field blank.
+
+If you are a user in the sub-domains, enter the full path to the domain,
+excluding the root domain.
+
+For example, suppose multiple levels are created under the root domain,
+such as Comp1/hr. The users in the Comp1 domain should enter Comp1 in
+the Domain field, whereas the users in the Comp1/sales domain should
+enter Comp1/sales.
+
+For more guidance about the choices that appear when you log in to this
+UI, see Logging In as the Root Administrator.
+
+
+End User's UI Overview
+~~~~~~~~~~~~~~~~~~~~~~
+
+The CloudStack UI helps users of cloud infrastructure to view and use
+their cloud resources, including virtual machines, templates and ISOs,
+data volumes and snapshots, guest networks, and IP addresses. If the
+user is a member or administrator of one or more CloudStack projects,
+the UI can provide a project-oriented view.
+
+
+Root Administrator's UI Overview
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The CloudStack UI helps the CloudStack administrator provision, view,
+and manage the cloud infrastructure, domains, user accounts, projects,
+and configuration settings. The first time you start the UI after a
+fresh Management Server installation, you can choose to follow a guided
+tour to provision your cloud infrastructure. On subsequent logins, the
+dashboard of the logged-in user appears. The various links in this
+screen and the navigation bar on the left provide access to a variety of
+administrative functions. The root administrator can also use the UI to
+perform all the same tasks that are present in the end-user’s UI.
+
+
+Logging In as the Root Administrator
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+After the Management Server software is installed and running, you can
+run the CloudStack user interface. This UI is there to help you
+provision, view, and manage your cloud infrastructure.
+
+#. Open your favorite Web browser and go to this URL. Substitute the IP
+ address of your own Management Server:
+
+ .. parsed-literal::
+
+ http://<management-server-ip-address>:8080/client
+
+ After logging into a fresh Management Server installation, a guided
+ tour splash screen appears. On later visits, you’ll be taken directly
+ into the Dashboard.
+
+#. If you see the first-time splash screen, choose one of the following.
+
+ - **Continue with basic setup.** Choose this if you're just trying
+ CloudStack, and you want a guided walkthrough of the simplest
+ possible configuration so that you can get started right away.
+ We'll help you set up a cloud with the following features: a
+ single machine that runs CloudStack software and uses NFS to
+ provide storage; a single machine running VMs under the XenServer
+ or KVM hypervisor; and a shared public network.
+
+ The prompts in this guided tour should give you all the
+ information you need, but if you want just a bit more detail, you
+ can follow along in the Trial Installation Guide.
+
+ - **I have used CloudStack before.** Choose this if you have already
+ gone through a design phase and planned a more sophisticated
+ deployment, or you are ready to start scaling up a trial cloud
+ that you set up earlier with the basic setup screens. In the
+ Administrator UI, you can start using the more powerful features
+ of CloudStack, such as advanced VLAN networking, high
+ availability, additional network elements such as load balancers
+ and firewalls, and support for multiple hypervisors including
+ Citrix XenServer, KVM, and VMware vSphere.
+
+ The root administrator Dashboard appears.
+
+#. You should set a new root administrator password. If you chose basic
+ setup, you’ll be prompted to create a new password right away. If you
+ chose experienced user, use the steps in :ref:`changing-root-password`.
+
+.. warning::
+ You are logging in as the root administrator. This account manages the
+ CloudStack deployment, including physical infrastructure. The root
+ administrator can modify configuration settings to change basic
+ functionality, create or delete user accounts, and take many actions
+ that should be performed only by an authorized person. Please change
+ the default password to a new, unique password.
+
+.. _changing-root-password:
+
+Changing the Root Password
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+During installation and ongoing cloud administration, you will need to
+log in to the UI as the root administrator. The root administrator
+account manages the CloudStack deployment, including physical
+infrastructure. The root administrator can modify configuration settings
+to change basic functionality, create or delete user accounts, and take
+many actions that should be performed only by an authorized person. When
+first installing CloudStack, be sure to change the default password to a
+new, unique value.
+
+#. Open your favorite Web browser and go to this URL. Substitute the IP
+ address of your own Management Server:
+
+ .. parsed-literal::
+
+ http://<management-server-ip-address>:8080/client
+
+#. Log in to the UI using the current root user ID and password. The
+ default is admin, password.
+
+#. Click Accounts.
+
+#. Click the admin account name.
+
+#. Click View Users.
+
+#. Click the admin user name.
+
+#. Click the Change Password button. |change-password.png|
+
+#. Type the new password, and click OK.
+
+
+.. |change-password.png| image:: /_static/images/change-password.png
+ :alt: button to change a user's password
diff --git a/source/adminguide/usage.rst b/source/adminguide/usage.rst
new file mode 100644
index 0000000..3e05ed8
--- /dev/null
+++ b/source/adminguide/usage.rst
@@ -0,0 +1,929 @@
+.. 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.
+
+.. _working-with-usage:
+
+Working with Usage
+==================
+
+The Usage Server is an optional, separately-installed part of CloudStack
+that provides aggregated usage records which you can use to create
+billing integration for CloudStack. The Usage Server works by taking
+data from the events log and creating summary usage records that you can
+access using the listUsageRecords API call.
+
+The usage records show the amount of resources, such as VM run time or
+template storage space, consumed by guest instances.
+
+The Usage Server runs at least once per day. It can be configured to run
+multiple times per day.
+
+
+Configuring the Usage Server
+----------------------------
+
+To configure the usage server:
+
+#. Be sure the Usage Server has been installed. This requires extra
+ steps beyond just installing the CloudStack software. See Installing
+ the Usage Server (Optional) in the Advanced Installation Guide.
+
+#. Log in to the CloudStack UI as administrator.
+
+#. Click Global Settings.
+
+#. In Search, type usage. Find the configuration parameter that controls
+ the behavior you want to set. See the table below for a description
+ of the available parameters.
+
+#. In Actions, click the Edit icon.
+
+#. Type the desired value and click the Save icon.
+
+#. Restart the Management Server (as usual with any global configuration
+ change) and also the Usage Server:
+
+ .. code:: bash
+
+ # service cloudstack-management restart
+ # service cloudstack-usage restart
+
+The following table shows the global configuration settings that control
+the behavior of the Usage Server.
+
+Parameter Name Description
+
+enable.usage.server Whether the Usage Server is active.
+
+usage.aggregation.timezone
+
+Time zone of usage records. Set this if the usage records and daily job
+execution are in different time zones. For example, with the following
+settings, the usage job will run at PST 00:15 and generate usage records
+for the 24 hours from 00:00:00 GMT to 23:59:59 GMT:
+
+.. code:: bash
+
+ usage.stats.job.exec.time = 00:15
+ usage.execution.timezone = PST
+ usage.aggregation.timezone = GMT
+
+Valid values for the time zone are specified in the :ref:`time-zones` section
+
+Default: GMT
+
+usage.execution.timezone
+
+The time zone of usage.stats.job.exec.time. Valid values for the time
+zone are specified in the :ref:`time-zones` section
+
+Default: The time zone of the management server.
+
+usage.sanity.check.interval
+
+The number of days between sanity checks. Set this in order to
+periodically search for records with erroneous data before issuing
+customer invoices. For example, this checks for VM usage records created
+after the VM was destroyed, and similar checks for templates, volumes,
+and so on. It also checks for usage times longer than the aggregation
+range. If any issue is found, the alert
+ALERT\_TYPE\_USAGE\_SANITY\_RESULT = 21 is sent.
+
+usage.stats.job.aggregation.range
+
+The time period in minutes between Usage Server processing jobs. For
+example, if you set it to 1440, the Usage Server will run once per day.
+If you set it to 600, it will run every ten hours. In general, when a
+Usage Server job runs, it processes all events generated since usage was
+last run.
+
+There is special handling for the case of 1440 (once per day). In this
+case the Usage Server does not necessarily process all records since
+Usage was last run. CloudStack assumes that you require processing once
+per day for the previous, complete day’s records. For example, if the
+current day is October 7, then it is assumed you would like to process
+records for October 6, from midnight to midnight. CloudStack assumes
+this “midnight to midnight” is relative to the usage.execution.timezone.
+
+Default: 1440
+
+usage.stats.job.exec.time
+
+The time when the Usage Server processing will start. It is specified in
+24-hour format (HH:MM) in the time zone of the server, which should be
+GMT. For example, to start the Usage job at 10:30 GMT, enter “10:30”.
+
+If usage.stats.job.aggregation.range is also set, and its value is not
+1440, then its value will be added to usage.stats.job.exec.time to get
+the time to run the Usage Server job again. This is repeated until 24
+hours have elapsed, and the next day's processing begins again at
+usage.stats.job.exec.time.
+
+Default: 00:15.
+
+For example, suppose that your server is in GMT, your user population is
+predominantly in the East Coast of the United States, and you would like
+to process usage records every night at 2 AM local (EST) time. Choose
+these settings:
+
+- enable.usage.server = true
+
+- usage.execution.timezone = America/New\_York
+
+- usage.stats.job.exec.time = 07:00. This will run the Usage job at
+ 2:00 AM EST. Note that this will shift by an hour as the East Coast
+ of the U.S. enters and exits Daylight Savings Time.
+
+- usage.stats.job.aggregation.range = 1440
+
+With this configuration, the Usage job will run every night at 2 AM EST
+and will process records for the previous day’s midnight-midnight as
+defined by the EST (America/New\_York) time zone.
+
+.. note::
+ Because the special value 1440 has been used for
+ usage.stats.job.aggregation.range, the Usage Server will ignore the data
+ between midnight and 2 AM. That data will be included in the next day's
+ run.
+
+
+Setting Usage Limits
+--------------------
+
+CloudStack provides several administrator control points for capping
+resource usage by users. Some of these limits are global configuration
+parameters. Others are applied at the ROOT domain and may be overridden
+on a per-account basis.
+
+
+Globally Configured Limits
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+In a zone, the guest virtual network has a 24 bit CIDR by default. This
+limits the guest virtual network to 254 running instances. It can be
+adjusted as needed, but this must be done before any instances are
+created in the zone. For example, 10.1.1.0/22 would provide for ~1000
+addresses.
+
+The following table lists limits set in the Global Configuration:
+
+.. cssclass:: table-striped table-bordered table-hover
+
++---------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| Parameter Name | Definition |
++===========================+==================================================================================================================================================================================================================================================================================================+
+| max.account.public.ips | Number of public IP addresses that can be owned by an account |
++---------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| max.account.snapshots | Number of snapshots that can exist for an account |
++---------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| max.account.templates | Number of templates that can exist for an account |
++---------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| max.account.user.vms | Number of virtual machine instances that can exist for an account |
++---------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| max.account.volumes | Number of disk volumes that can exist for an account |
++---------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| max.template.iso.size | Maximum size for a downloaded template or ISO in GB |
++---------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| max.volume.size.gb | Maximum size for a volume in GB |
++---------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| network.throttling.rate | Default data transfer rate in megabits per second allowed per user (supported on XenServer) |
++---------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| snapshot.max.hourly | Maximum recurring hourly snapshots to be retained for a volume. If the limit is reached, early snapshots from the start of the hour are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring hourly snapshots can not be scheduled |
++---------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| snapshot.max.daily | Maximum recurring daily snapshots to be retained for a volume. If the limit is reached, snapshots from the start of the day are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring daily snapshots can not be scheduled |
++---------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| snapshot.max.weekly | Maximum recurring weekly snapshots to be retained for a volume. If the limit is reached, snapshots from the beginning of the week are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring weekly snapshots can not be scheduled |
++---------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| snapshot.max.monthly | Maximum recurring monthly snapshots to be retained for a volume. If the limit is reached, snapshots from the beginning of the month are deleted so that newer ones can be saved. This limit does not apply to manual snapshots. If set to 0, recurring monthly snapshots can not be scheduled. |
++---------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+
+To modify global configuration parameters, use the global configuration
+screen in the CloudStack UI. See Setting Global Configuration Parameters
+
+
+Limiting Resource Usage
+~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack allows you to control resource usage based on the types of
+resources, such as CPU, RAM, Primary storage, and Secondary storage. A
+new set of resource types has been added to the existing pool of
+resources to support the new customization model—need-basis usage, such
+as large VM or small VM. The new resource types are now broadly
+classified as CPU, RAM, Primary storage, and Secondary storage. The root
+administrator is able to impose resource usage limit by the following
+resource types for Domain, Project, and Accounts.
+
+- CPUs
+
+- Memory (RAM)
+
+- Primary Storage (Volumes)
+
+- Secondary Storage (Snapshots, Templates, ISOs)
+
+To control the behaviour of this feature, the following configuration
+parameters have been added:
+
+.. cssclass:: table-striped table-bordered table-hover
+
+=================================== =================================================================
+Parameter Name Description
+=================================== =================================================================
+max.account.cpus Maximum number of CPU cores that can be used for an account.
+ Default is 40.
+max.account.ram (MB) Maximum RAM that can be used for an account.
+ Default is 40960.
+max.account.primary.storage (GB) Maximum primary storage space that can be used for an account.
+ Default is 200.
+max.account.secondary.storage (GB) Maximum secondary storage space that can be used for an account.
+ Default is 400.
+max.project.cpus Maximum number of CPU cores that can be used for an account.
+ Default is 40.
+max.project.ram (MB) Maximum RAM that can be used for an account.
+ Default is 40960.
+max.project.primary.storage (GB) Maximum primary storage space that can be used for an account.
+ Default is 200.
+max.project.secondary.storage (GB) Maximum secondary storage space that can be used for an account.
+ Default is 400.
+=================================== =================================================================
+
+
+User Permission
+~~~~~~~~~~~~~~~
+
+The root administrator, domain administrators and users are able to list
+resources. Ensure that proper logs are maintained in the ``vmops.log``
+and ``api.log`` files.
+
+- The root admin will have the privilege to list and update resource
+ limits.
+
+- The domain administrators are allowed to list and change these
+ resource limits only for the sub-domains and accounts under their own
+ domain or the sub-domains.
+
+- The end users will the privilege to list resource limits. Use the
+ listResourceLimits API.
+
+
+Limit Usage Considerations
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- Primary or Secondary storage space refers to the stated size of the
+ volume and not the physical size— the actual consumed size on disk in
+ case of thin provisioning.
+
+- If the admin reduces the resource limit for an account and set it to
+ less than the resources that are currently being consumed, the
+ existing VMs/templates/volumes are not destroyed. Limits are imposed
+ only if the user under that account tries to execute a new operation
+ using any of these resources. For example, the existing behavior in
+ the case of a VM are:
+
+ - migrateVirtualMachine: The users under that account will be able
+ to migrate the running VM into any other host without facing any
+ limit issue.
+
+ - recoverVirtualMachine: Destroyed VMs cannot be recovered.
+
+- For any resource type, if a domain has limit X, sub-domains or
+ accounts under that domain can have there own limits. However, the
+ sum of resource allocated to a sub-domain or accounts under the
+ domain at any point of time should not exceed the value X.
+
+ For example, if a domain has the CPU limit of 40 and the sub-domain
+ D1 and account A1 can have limits of 30 each, but at any point of
+ time the resource allocated to D1 and A1 should not exceed the limit
+ of 40.
+
+- If any operation needs to pass through two of more resource limit
+ check, then the lower of 2 limits will be enforced, For example: if
+ an account has the VM limit of 10 and CPU limit of 20, and a user
+ under that account requests 5 VMs of 4 CPUs each. The user can deploy
+ 5 more VMs because VM limit is 10. However, the user cannot deploy
+ any more instances because the CPU limit has been exhausted.
+
+
+Limiting Resource Usage in a Domain
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack allows the configuration of limits on a domain basis. With a
+domain limit in place, all users still have their account limits. They
+are additionally limited, as a group, to not exceed the resource limits
+set on their domain. Domain limits aggregate the usage of all accounts
+in the domain as well as all the accounts in all the sub-domains of that
+domain. Limits set at the root domain level apply to the sum of resource
+usage by the accounts in all the domains and sub-domains below that root
+domain.
+
+To set a domain limit:
+
+#. Log in to the CloudStack UI.
+
+#. In the left navigation tree, click Domains.
+
+#. Select the domain you want to modify. The current domain limits are
+ displayed.
+
+ A value of -1 shows that there is no limit in place.
+
+#. Click the Edit button |editbutton.png|
+
+#. Edit the following as per your requirement:
+
+ - Parameter Name
+
+ - Description
+
+ - Instance Limits
+
+ The number of instances that can be used in a domain.
+
+ - Public IP Limits
+
+ The number of public IP addresses that can be used in a domain.
+
+ - Volume Limits
+
+ The number of disk volumes that can be created in a domain.
+
+ - Snapshot Limits
+
+ The number of snapshots that can be created in a domain.
+
+ - Template Limits
+
+ The number of templates that can be registered in a domain.
+
+ - VPC limits
+
+ The number of VPCs that can be created in a domain.
+
+ - CPU limits
+
+ The number of CPU cores that can be used for a domain.
+
+ - Memory limits (MB)
+
+ The number of RAM that can be used for a domain.
+
+ - Primary Storage limits (GB)
+
+ The primary storage space that can be used for a domain.
+
+ - Secondary Storage limits (GB)
+
+ The secondary storage space that can be used for a domain.
+
+#. Click Apply.
+
+
+Default Account Resource Limits
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can limit resource use by accounts. The default limits are set by
+using Global configuration parameters, and they affect all accounts
+within a cloud. The relevant parameters are those beginning with
+max.account, for example: max.account.snapshots.
+
+To override a default limit for a particular account, set a per-account
+resource limit.
+
+#. Log in to the CloudStack UI.
+
+#. In the left navigation tree, click Accounts.
+
+#. Select the account you want to modify. The current limits are
+ displayed.
+
+ A value of -1 shows that there is no limit in place.
+
+#. Click the Edit button. |editbutton.png|
+
+#. Edit the following as per your requirement:
+
+ - Parameter Name
+
+ - Description
+
+ - Instance Limits
+
+ The number of instances that can be used in an account.
+
+ The default is 20.
+
+ - Public IP Limits
+
+ The number of public IP addresses that can be used in an account.
+
+ The default is 20.
+
+ - Volume Limits
+
+ The number of disk volumes that can be created in an account.
+
+ The default is 20.
+
+ - Snapshot Limits
+
+ The number of snapshots that can be created in an account.
+
+ The default is 20.
+
+ - Template Limits
+
+ The number of templates that can be registered in an account.
+
+ The default is 20.
+
+ - VPC limits
+
+ The number of VPCs that can be created in an account.
+
+ The default is 20.
+
+ - CPU limits
+
+ The number of CPU cores that can be used for an account.
+
+ The default is 40.
+
+ - Memory limits (MB)
+
+ The number of RAM that can be used for an account.
+
+ The default is 40960.
+
+ - Primary Storage limits (GB)
+
+ The primary storage space that can be used for an account.
+
+ The default is 200.
+
+ - Secondary Storage limits (GB)
+
+ The secondary storage space that can be used for an account.
+
+ The default is 400.
+
+#. Click Apply.
+
+
+Usage Record Format
+-------------------
+
+Virtual Machine Usage Record Format
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+For running and allocated virtual machine usage, the following fields
+exist in a usage record:
+
+- account – name of the account
+
+- accountid – ID of the account
+
+- domainid – ID of the domain in which this account resides
+
+- zoneid – Zone where the usage occurred
+
+- description – A string describing what the usage record is tracking
+
+- usage – String representation of the usage, including the units of
+ usage (e.g. 'Hrs' for VM running time)
+
+- usagetype – A number representing the usage type (see Usage Types)
+
+- rawusage – A number representing the actual usage in hours
+
+- virtualMachineId – The ID of the virtual machine
+
+- name – The name of the virtual machine
+
+- offeringid – The ID of the service offering
+
+- templateid – The ID of the template or the ID of the parent template.
+ The parent template value is present when the current template was
+ created from a volume.
+
+- usageid – Virtual machine
+
+- type – Hypervisor
+
+- startdate, enddate – The range of time for which the usage is
+ aggregated; see Dates in the Usage Record
+
+
+Network Usage Record Format
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+For network usage (bytes sent/received), the following fields exist in a
+usage record.
+
+- account – name of the account
+
+- accountid – ID of the account
+
+- domainid – ID of the domain in which this account resides
+
+- zoneid – Zone where the usage occurred
+
+- description – A string describing what the usage record is tracking
+
+- usagetype – A number representing the usage type (see Usage Types)
+
+- rawusage – A number representing the actual usage in hours
+
+- usageid – Device ID (virtual router ID or external device ID)
+
+- type – Device type (domain router, external load balancer, etc.)
+
+- startdate, enddate – The range of time for which the usage is
+ aggregated; see Dates in the Usage Record
+
+
+IP Address Usage Record Format
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+For IP address usage the following fields exist in a usage record.
+
+- account - name of the account
+
+- accountid - ID of the account
+
+- domainid - ID of the domain in which this account resides
+
+- zoneid - Zone where the usage occurred
+
+- description - A string describing what the usage record is tracking
+
+- usage - String representation of the usage, including the units of
+ usage
+
+- usagetype - A number representing the usage type (see Usage Types)
+
+- rawusage - A number representing the actual usage in hours
+
+- usageid - IP address ID
+
+- startdate, enddate - The range of time for which the usage is
+ aggregated; see Dates in the Usage Record
+
+- issourcenat - Whether source NAT is enabled for the IP address
+
+- iselastic - True if the IP address is elastic.
+
+
+Disk Volume Usage Record Format
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+For disk volumes, the following fields exist in a usage record.
+
+- account – name of the account
+
+- accountid – ID of the account
+
+- domainid – ID of the domain in which this account resides
+
+- zoneid – Zone where the usage occurred
+
+- description – A string describing what the usage record is tracking
+
+- usage – String representation of the usage, including the units of
+ usage (e.g. 'Hrs' for hours)
+
+- usagetype – A number representing the usage type (see Usage Types)
+
+- rawusage – A number representing the actual usage in hours
+
+- usageid – The volume ID
+
+- offeringid – The ID of the disk offering
+
+- type – Hypervisor
+
+- templateid – ROOT template ID
+
+- size – The amount of storage allocated
+
+- startdate, enddate – The range of time for which the usage is
+ aggregated; see Dates in the Usage Record
+
+
+Template, ISO, and Snapshot Usage Record Format
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- account – name of the account
+
+- accountid – ID of the account
+
+- domainid – ID of the domain in which this account resides
+
+- zoneid – Zone where the usage occurred
+
+- description – A string describing what the usage record is tracking
+
+- usage – String representation of the usage, including the units of
+ usage (e.g. 'Hrs' for hours)
+
+- usagetype – A number representing the usage type (see Usage Types)
+
+- rawusage – A number representing the actual usage in hours
+
+- usageid – The ID of the the template, ISO, or snapshot
+
+- offeringid – The ID of the disk offering
+
+- templateid – – Included only for templates (usage type 7). Source
+ template ID.
+
+- size – Size of the template, ISO, or snapshot
+
+- startdate, enddate – The range of time for which the usage is
+ aggregated; see Dates in the Usage Record
+
+
+Load Balancer Policy or Port Forwarding Rule Usage Record Format
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- account - name of the account
+
+- accountid - ID of the account
+
+- domainid - ID of the domain in which this account resides
+
+- zoneid - Zone where the usage occurred
+
+- description - A string describing what the usage record is tracking
+
+- usage - String representation of the usage, including the units of
+ usage (e.g. 'Hrs' for hours)
+
+- usagetype - A number representing the usage type (see Usage Types)
+
+- rawusage - A number representing the actual usage in hours
+
+- usageid - ID of the load balancer policy or port forwarding rule
+
+- usagetype - A number representing the usage type (see Usage Types)
+
+- startdate, enddate - The range of time for which the usage is
+ aggregated; see Dates in the Usage Record
+
+
+Network Offering Usage Record Format
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- account – name of the account
+
+- accountid – ID of the account
+
+- domainid – ID of the domain in which this account resides
+
+- zoneid – Zone where the usage occurred
+
+- description – A string describing what the usage record is tracking
+
+- usage – String representation of the usage, including the units of
+ usage (e.g. 'Hrs' for hours)
+
+- usagetype – A number representing the usage type (see Usage Types)
+
+- rawusage – A number representing the actual usage in hours
+
+- usageid – ID of the network offering
+
+- usagetype – A number representing the usage type (see Usage Types)
+
+- offeringid – Network offering ID
+
+- virtualMachineId – The ID of the virtual machine
+
+- virtualMachineId – The ID of the virtual machine
+
+- startdate, enddate – The range of time for which the usage is
+ aggregated; see Dates in the Usage Record
+
+
+VPN User Usage Record Format
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- account – name of the account
+
+- accountid – ID of the account
+
+- domainid – ID of the domain in which this account resides
+
+- zoneid – Zone where the usage occurred
+
+- description – A string describing what the usage record is tracking
+
+- usage – String representation of the usage, including the units of
+ usage (e.g. 'Hrs' for hours)
+
+- usagetype – A number representing the usage type (see Usage Types)
+
+- rawusage – A number representing the actual usage in hours
+
+- usageid – VPN user ID
+
+- usagetype – A number representing the usage type (see Usage Types)
+
+- startdate, enddate – The range of time for which the usage is
+ aggregated; see Dates in the Usage Record
+
+
+Usage Types
+-----------
+
+The following table shows all usage types.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++------------------+-----------------------------------+-----------------------+
+| Type ID | Type Name | Description |
++==================+===================================+=======================+
+| 1 | RUNNING\_VM | Tracks the total |
+| | | running time of a VM |
+| | | per usage record |
+| | | period. If the VM is |
+| | | upgraded during the |
+| | | usage period, you |
+| | | will get a separate |
+| | | Usage Record for the |
+| | | new upgraded VM. |
++------------------+-----------------------------------+-----------------------+
+| 2 | ALLOCATED\_VM | Tracks the total time |
+| | | the VM has been |
+| | | created to the time |
+| | | when it has been |
+| | | destroyed. This usage |
+| | | type is also useful |
+| | | in determining usage |
+| | | for specific |
+| | | templates such as |
+| | | Windows-based |
+| | | templates. |
++------------------+-----------------------------------+-----------------------+
+| 3 | IP\_ADDRESS | Tracks the public IP |
+| | | address owned by the |
+| | | account. |
++------------------+-----------------------------------+-----------------------+
+| 4 | NETWORK\_BYTES\_SENT | Tracks the total |
+| | | number of bytes sent |
+| | | by all the VMs for an |
+| | | account. Cloud.com |
+| | | does not currently |
+| | | track network traffic |
+| | | per VM. |
++------------------+-----------------------------------+-----------------------+
+| 5 | NETWORK\_BYTES\_RECEIVED | Tracks the total |
+| | | number of bytes |
+| | | received by all the |
+| | | VMs for an account. |
+| | | Cloud.com does not |
+| | | currently track |
+| | | network traffic per |
+| | | VM. |
++------------------+-----------------------------------+-----------------------+
+| 6 | VOLUME | Tracks the total time |
+| | | a disk volume has |
+| | | been created to the |
+| | | time when it has been |
+| | | destroyed. |
++------------------+-----------------------------------+-----------------------+
+| 7 | TEMPLATE | Tracks the total time |
+| | | a template (either |
+| | | created from a |
+| | | snapshot or uploaded |
+| | | to the cloud) has |
+| | | been created to the |
+| | | time it has been |
+| | | destroyed. The size |
+| | | of the template is |
+| | | also returned. |
++------------------+-----------------------------------+-----------------------+
+| 8 | ISO | Tracks the total time |
+| | | an ISO has been |
+| | | uploaded to the time |
+| | | it has been removed |
+| | | from the cloud. The |
+| | | size of the ISO is |
+| | | also returned. |
++------------------+-----------------------------------+-----------------------+
+| 9 | SNAPSHOT | Tracks the total time |
+| | | from when a snapshot |
+| | | has been created to |
+| | | the time it have been |
+| | | destroyed. |
++------------------+-----------------------------------+-----------------------+
+| 11 | LOAD\_BALANCER\_POLICY | Tracks the total time |
+| | | a load balancer |
+| | | policy has been |
+| | | created to the time |
+| | | it has been removed. |
+| | | Cloud.com does not |
+| | | track whether a VM |
+| | | has been assigned to |
+| | | a policy. |
++------------------+-----------------------------------+-----------------------+
+| 12 | PORT\_FORWARDING\_RULE | Tracks the time from |
+| | | when a port |
+| | | forwarding rule was |
+| | | created until the |
+| | | time it was removed. |
++------------------+-----------------------------------+-----------------------+
+| 13 | NETWORK\_OFFERING | The time from when a |
+| | | network offering was |
+| | | assigned to a VM |
+| | | until it is removed. |
++------------------+-----------------------------------+-----------------------+
+| 14 | VPN\_USERS | The time from when a |
+| | | VPN user is created |
+| | | until it is removed. |
++------------------+-----------------------------------+-----------------------+
+
+
+Example response from listUsageRecords
+--------------------------------------
+
+All CloudStack API requests are submitted in the form of a HTTP GET/POST
+with an associated command and any parameters. A request is composed of
+the following whether in HTTP or HTTPS:
+
+::
+
+ <listusagerecordsresponse>
+ <count>1816</count>
+ <usagerecord>
+ <account>user5</account>
+ <accountid>10004</accountid>
+ <domainid>1</domainid>
+ <zoneid>1</zoneid>
+ <description>i-3-4-WC running time (ServiceOffering: 1) (Template: 3)</description>
+ <usage>2.95288 Hrs</usage>
+ <usagetype>1</usagetype>
+ <rawusage>2.95288</rawusage>
+ <virtualmachineid>4</virtualmachineid>
+ <name>i-3-4-WC</name>
+ <offeringid>1</offeringid>
+ <templateid>3</templateid>
+ <usageid>245554</usageid>
+ <type>XenServer</type>
+ <startdate>2009-09-15T00:00:00-0700</startdate>
+ <enddate>2009-09-18T16:14:26-0700</enddate>
+ </usagerecord>
+
+ … (1,815 more usage records)
+ </listusagerecordsresponse>
+
+
+Dates in the Usage Record
+-------------------------
+
+Usage records include a start date and an end date. These dates define
+the period of time for which the raw usage number was calculated. If
+daily aggregation is used, the start date is midnight on the day in
+question and the end date is 23:59:59 on the day in question (with one
+exception; see below). A virtual machine could have been deployed at
+noon on that day, stopped at 6pm on that day, then started up again at
+11pm. When usage is calculated on that day, there will be 7 hours of
+running VM usage (usage type 1) and 12 hours of allocated VM usage
+(usage type 2). If the same virtual machine runs for the entire next
+day, there will 24 hours of both running VM usage (type 1) and allocated
+VM usage (type 2).
+
+Note: The start date is not the time a virtual machine was started, and
+the end date is not the time when a virtual machine was stopped. The
+start and end dates give the time range within which usage was
+calculated.
+
+For network usage, the start date and end date again define the range in
+which the number of bytes transferred was calculated. If a user
+downloads 10 MB and uploads 1 MB in one day, there will be two records,
+one showing the 10 megabytes received and one showing the 1 megabyte
+sent.
+
+There is one case where the start date and end date do not correspond to
+midnight and 11:59:59pm when daily aggregation is used. This occurs only
+for network usage records. When the usage server has more than one day's
+worth of unprocessed data, the old data will be included in the
+aggregation period. The start date in the usage record will show the
+date and time of the earliest event. For other types of usage, such as
+IP addresses and VMs, the old unprocessed data is not included in daily
+aggregation.
+
+
+.. |editbutton.png| image:: /_static/images/edit-icon.png
+ :alt: edits the settings.
diff --git a/source/adminguide/virtual_machines.rst b/source/adminguide/virtual_machines.rst
new file mode 100644
index 0000000..f8c34de
--- /dev/null
+++ b/source/adminguide/virtual_machines.rst
@@ -0,0 +1,1356 @@
+.. 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.
+
+
+Working with Virtual Machines
+=============================
+
+About Working with Virtual Machines
+-----------------------------------
+
+CloudStack provides administrators with complete control over the
+lifecycle of all guest VMs executing in the cloud. CloudStack provides
+several guest management operations for end users and administrators.
+VMs may be stopped, started, rebooted, and destroyed.
+
+Guest VMs have a name and group. VM names and groups are opaque to
+CloudStack and are available for end users to organize their VMs. Each
+VM can have three names for use in different contexts. Only two of these
+names can be controlled by the user:
+
+- Instance name – a unique, immutable ID that is generated by
+ CloudStack and can not be modified by the user. This name conforms to
+ the requirements in IETF RFC 1123.
+
+- Display name – the name displayed in the CloudStack web UI. Can be
+ set by the user. Defaults to instance name.
+
+- Name – host name that the DHCP server assigns to the VM. Can be set
+ by the user. Defaults to instance name
+
+.. note::
+ You can append the display name of a guest VM to its internal name.
+ For more information, see `“Appending a Display Name to the Guest VM’s
+ Internal Name” <#appending-a-display-name-to-the-guest-vms-internal-name>`_.
+
+Guest VMs can be configured to be Highly Available (HA). An HA-enabled
+VM is monitored by the system. If the system detects that the VM is
+down, it will attempt to restart the VM, possibly on a different host.
+For more information, see HA-Enabled Virtual Machines on
+
+Each new VM is allocated one public IP address. When the VM is started,
+CloudStack automatically creates a static NAT between this public IP
+address and the private IP address of the VM.
+
+If elastic IP is in use (with the NetScaler load balancer), the IP
+address initially allocated to the new VM is not marked as elastic. The
+user must replace the automatically configured IP with a specifically
+acquired elastic IP, and set up the static NAT mapping between this new
+IP and the guest VM’s private IP. The VM’s original IP address is then
+released and returned to the pool of available public IPs. Optionally,
+you can also decide not to allocate a public IP to a VM in an
+EIP-enabled Basic zone. For more information on Elastic IP, see
+`“About Elastic IP” <networking2.html#about-elastic-ip>`_.
+
+CloudStack cannot distinguish a guest VM that was shut down by the user
+(such as with the “shutdown” command in Linux) from a VM that shut down
+unexpectedly. If an HA-enabled VM is shut down from inside the VM,
+CloudStack will restart it. To shut down an HA-enabled VM, you must go
+through the CloudStack UI or API.
+
+
+Best Practices for Virtual Machines
+-----------------------------------
+
+For VMs to work as expected and provide excellent service, follow these
+guidelines.
+
+
+Monitor VMs for Max Capacity
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The CloudStack administrator should monitor the total number of VM
+instances in each cluster, and disable allocation to the cluster if the
+total is approaching the maximum that the hypervisor can handle. Be sure
+to leave a safety margin to allow for the possibility of one or more
+hosts failing, which would increase the VM load on the other hosts as
+the VMs are automatically redeployed. Consult the documentation for your
+chosen hypervisor to find the maximum permitted number of VMs per host,
+then use CloudStack global configuration settings to set this as the
+default limit. Monitor the VM activity in each cluster at all times.
+Keep the total number of VMs below a safe level that allows for the
+occasional host failure. For example, if there are N hosts in the
+cluster, and you want to allow for one host in the cluster to be down at
+any given time, the total number of VM instances you can permit in the
+cluster is at most (N-1) \* (per-host-limit). Once a cluster reaches
+this number of VMs, use the CloudStack UI to disable allocation of more
+VMs to the cluster.
+
+
+Install Required Tools and Drivers
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Be sure the following are installed on each VM:
+
+- For XenServer, install PV drivers and Xen tools on each VM. This will
+ enable live migration and clean guest shutdown. Xen tools are
+ required in order for dynamic CPU and RAM scaling to work.
+
+- For vSphere, install VMware Tools on each VM. This will enable
+ console view to work properly. VMware Tools are required in order for
+ dynamic CPU and RAM scaling to work.
+
+To be sure that Xen tools or VMware Tools is installed, use one of the
+following techniques:
+
+- Create each VM from a template that already has the tools installed;
+ or,
+
+- When registering a new template, the administrator or user can
+ indicate whether tools are installed on the template. This can be
+ done through the UI or using the updateTemplate API; or,
+
+- If a user deploys a virtual machine with a template that does not
+ have Xen tools or VMware Tools, and later installs the tools on the
+ VM, then the user can inform CloudStack using the
+ updateVirtualMachine API. After installing the tools and updating the
+ virtual machine, stop and start the VM.
+
+
+VM Lifecycle
+------------
+
+Virtual machines can be in the following states:
+
+|basic-deployment.png|
+
+Once a virtual machine is destroyed, it cannot be recovered. All the
+resources used by the virtual machine will be reclaimed by the system.
+This includes the virtual machine’s IP address.
+
+A stop will attempt to gracefully shut down the operating system, which
+typically involves terminating all the running applications. If the
+operation system cannot be stopped, it will be forcefully terminated.
+This has the same effect as pulling the power cord to a physical
+machine.
+
+A reboot is a stop followed by a start.
+
+CloudStack preserves the state of the virtual machine hard disk until
+the machine is destroyed.
+
+A running virtual machine may fail because of hardware or network
+issues. A failed virtual machine is in the down state.
+
+The system places the virtual machine into the down state if it does not
+receive the heartbeat from the hypervisor for three minutes.
+
+The user can manually restart the virtual machine from the down state.
+
+The system will start the virtual machine from the down state
+automatically if the virtual machine is marked as HA-enabled.
+
+
+Creating VMs
+------------
+
+Virtual machines are usually created from a template. Users can also
+create blank virtual machines. A blank virtual machine is a virtual
+machine without an OS template. Users can attach an ISO file and install
+the OS from the CD/DVD-ROM.
+
+.. note::
+ You can create a VM without starting it. You can determine whether the
+ VM needs to be started as part of the VM deployment. A request parameter,
+ startVM, in the deployVm API provides this feature. For more information,
+ see the Developer's Guide.
+
+To create a VM from a template:
+
+#. Log in to the CloudStack UI as an administrator or user.
+
+#. In the left navigation bar, click Instances.
+
+#. Click Add Instance.
+
+#. Select a zone.
+
+#. Select a template, then follow the steps in the wizard. For more
+ information about how the templates came to be in this list, see
+ `*Working with Templates* <templates.html>`_.
+
+#. Be sure that the hardware you have allows starting the selected
+ service offering.
+
+#. Click Submit and your VM will be created and started.
+
+ .. note::
+ For security reason, the internal name of the VM is visible
+ only to the root admin.
+
+To create a VM from an ISO:
+
+.. note::
+ (XenServer) Windows VMs running on XenServer require PV drivers,
+ which may be provided in the template or added after the VM is
+ created. The PV drivers are necessary for essential management
+ functions such as mounting additional volumes and ISO images,
+ live migration, and graceful shutdown.
+
+#. Log in to the CloudStack UI as an administrator or user.
+
+#. In the left navigation bar, click Instances.
+
+#. Click Add Instance.
+
+#. Select a zone.
+
+#. Select ISO Boot, and follow the steps in the wizard.
+
+#. Click Submit and your VM will be created and started.
+
+
+Accessing VMs
+-------------
+
+Any user can access their own virtual machines. The administrator can
+access all VMs running in the cloud.
+
+To access a VM through the CloudStack UI:
+
+#. Log in to the CloudStack UI as a user or admin.
+
+#. Click Instances, then click the name of a running VM.
+
+#. Click the View Console button |console-icon.png|.
+
+To access a VM directly over the network:
+
+#. The VM must have some port open to incoming traffic. For example, in
+ a basic zone, a new VM might be assigned to a security group which
+ allows incoming traffic. This depends on what security group you
+ picked when creating the VM. In other cases, you can open a port by
+ setting up a port forwarding policy. See `“IP
+ Forwarding and Firewalling” <networking2.html#ip-forwarding-and-firewalling>`_.
+
+#. If a port is open but you can not access the VM using ssh, it’s
+ possible that ssh is not already enabled on the VM. This will depend
+ on whether ssh is enabled in the template you picked when creating
+ the VM. Access the VM through the CloudStack UI and enable ssh on the
+ machine using the commands for the VM’s operating system.
+
+#. If the network has an external firewall device, you will need to
+ create a firewall rule to allow access. See `“IP
+ Forwarding and Firewalling” <networking2.html#ip-forwarding-and-firewalling>`_.
+
+
+Stopping and Starting VMs
+-------------------------
+
+Once a VM instance is created, you can stop, restart, or delete it as
+needed. In the CloudStack UI, click Instances, select the VM, and use
+the Stop, Start, Reboot, and Destroy buttons.
+
+
+Assigning VMs to Hosts
+----------------------
+
+At any point in time, each virtual machine instance is running on a
+single host. How does CloudStack determine which host to place a VM on?
+There are several ways:
+
+- Automatic default host allocation. CloudStack can automatically pick
+ the most appropriate host to run each virtual machine.
+
+- Instance type preferences. CloudStack administrators can specify that
+ certain hosts should have a preference for particular types of guest
+ instances. For example, an administrator could state that a host
+ should have a preference to run Windows guests. The default host
+ allocator will attempt to place guests of that OS type on such hosts
+ first. If no such host is available, the allocator will place the
+ instance wherever there is sufficient physical capacity.
+
+- Vertical and horizontal allocation. Vertical allocation consumes all
+ the resources of a given host before allocating any guests on a
+ second host. This reduces power consumption in the cloud. Horizontal
+ allocation places a guest on each host in a round-robin fashion. This
+ may yield better performance to the guests in some cases.
+
+- End user preferences. Users can not control exactly which host will
+ run a given VM instance, but they can specify a zone for the VM.
+ CloudStack is then restricted to allocating the VM only to one of the
+ hosts in that zone.
+
+- Host tags. The administrator can assign tags to hosts. These tags can
+ be used to specify which host a VM should use. The CloudStack
+ administrator decides whether to define host tags, then create a
+ service offering using those tags and offer it to the user.
+
+- Affinity groups. By defining affinity groups and assigning VMs to
+ them, the user or administrator can influence (but not dictate) which
+ VMs should run on separate hosts. This feature is to let users
+ specify that certain VMs won't be on the same host.
+
+- CloudStack also provides a pluggable interface for adding new
+ allocators. These custom allocators can provide any policy the
+ administrator desires.
+
+
+Affinity Groups
+~~~~~~~~~~~~~~~
+
+By defining affinity groups and assigning VMs to them, the user or
+administrator can influence (but not dictate) which VMs should run on
+separate hosts. This feature is to let users specify that VMs with the
+same “host anti-affinity” type won’t be on the same host. This serves to
+increase fault tolerance. If a host fails, another VM offering the same
+service (for example, hosting the user's website) is still up and
+running on another host.
+
+The scope of an affinity group is per user account.
+
+
+Creating a New Affinity Group
+'''''''''''''''''''''''''''''
+
+To add an affinity group:
+
+#. Log in to the CloudStack UI as an administrator or user.
+
+#. In the left navigation bar, click Affinity Groups.
+
+#. Click Add affinity group. In the dialog box, fill in the following
+ fields:
+
+ - Name. Give the group a name.
+
+ - Description. Any desired text to tell more about the purpose of
+ the group.
+
+ - Type. The only supported type shipped with CloudStack is Host
+ Anti-Affinity. This indicates that the VMs in this group should
+ avoid being placed on the same host with each other. If you see
+ other types in this list, it means that your installation of
+ CloudStack has been extended with customized affinity group
+ plugins.
+
+
+Assign a New VM to an Affinity Group
+''''''''''''''''''''''''''''''''''''
+
+To assign a new VM to an affinity group:
+
+- Create the VM as usual, as described in `“Creating
+ VMs” <virtual_machines.html#creating-vms>`_. In the Add Instance
+ wizard, there is a new Affinity tab where you can select the
+ affinity group.
+
+
+Change Affinity Group for an Existing VM
+''''''''''''''''''''''''''''''''''''''''
+
+To assign an existing VM to an affinity group:
+
+#. Log in to the CloudStack UI as an administrator or user.
+
+#. In the left navigation bar, click Instances.
+
+#. Click the name of the VM you want to work with.
+
+#. Stop the VM by clicking the Stop button.
+
+#. Click the Change Affinity button. |change-affinity-button.png|
+
+
+View Members of an Affinity Group
+'''''''''''''''''''''''''''''''''
+
+To see which VMs are currently assigned to a particular affinity group:
+
+#. In the left navigation bar, click Affinity Groups.
+
+#. Click the name of the group you are interested in.
+
+#. Click View Instances. The members of the group are listed.
+
+ From here, you can click the name of any VM in the list to access all
+ its details and controls.
+
+
+Delete an Affinity Group
+''''''''''''''''''''''''
+
+To delete an affinity group:
+
+#. In the left navigation bar, click Affinity Groups.
+
+#. Click the name of the group you are interested in.
+
+#. Click Delete.
+
+ Any VM that is a member of the affinity group will be disassociated
+ from the group. The former group members will continue to run
+ normally on the current hosts, but if the VM is restarted, it will no
+ longer follow the host allocation rules from its former affinity
+ group.
+
+
+Virtual Machine Snapshots
+-------------------------
+
+(Supported on VMware and XenServer)
+
+In addition to the existing CloudStack ability to snapshot individual VM
+volumes, you can take a VM snapshot to preserve all the VM's data
+volumes as well as (optionally) its CPU/memory state. This is useful for
+quick restore of a VM. For example, you can snapshot a VM, then make
+changes such as software upgrades. If anything goes wrong, simply
+restore the VM to its previous state using the previously saved VM
+snapshot.
+
+The snapshot is created using the hypervisor's native snapshot facility.
+The VM snapshot includes not only the data volumes, but optionally also
+whether the VM is running or turned off (CPU state) and the memory
+contents. The snapshot is stored in CloudStack's primary storage.
+
+VM snapshots can have a parent/child relationship. Each successive
+snapshot of the same VM is the child of the snapshot that came before
+it. Each time you take an additional snapshot of the same VM, it saves
+only the differences between the current state of the VM and the state
+stored in the most recent previous snapshot. The previous snapshot
+becomes a parent, and the new snapshot is its child. It is possible to
+create a long chain of these parent/child snapshots, which amount to a
+"redo" record leading from the current state of the VM back to the
+original.
+
+If you need more information about VM snapshots on VMware, check out the
+VMware documentation and the VMware Knowledge Base, especially
+`Understanding virtual machine snapshots
+<http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1015180>`_.
+
+
+Limitations on VM Snapshots
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- If a VM has some stored snapshots, you can't attach new volume to the
+ VM or delete any existing volumes. If you change the volumes on the
+ VM, it would become impossible to restore the VM snapshot which was
+ created with the previous volume structure. If you want to attach a
+ volume to such a VM, first delete its snapshots.
+
+- VM snapshots which include both data volumes and memory can't be kept
+ if you change the VM's service offering. Any existing VM snapshots of
+ this type will be discarded.
+
+- You can't make a VM snapshot at the same time as you are taking a
+ volume snapshot.
+
+- You should use only CloudStack to create VM snapshots on hosts
+ managed by CloudStack. Any snapshots that you make directly on the
+ hypervisor will not be tracked in CloudStack.
+
+
+Configuring VM Snapshots
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+The cloud administrator can use global configuration variables to
+control the behavior of VM snapshots. To set these variables, go through
+the Global Settings area of the CloudStack UI.
+
+Configuration Setting Name
+
+Description
+
+vmsnapshots.max
+
+The maximum number of VM snapshots that can be saved for any given
+virtual machine in the cloud. The total possible number of VM snapshots
+in the cloud is (number of VMs) \* vmsnapshots.max. If the number of
+snapshots for any VM ever hits the maximum, the older ones are removed
+by the snapshot expunge job.
+
+vmsnapshot.create.wait
+
+Number of seconds to wait for a snapshot job to succeed before declaring
+failure and issuing an error.
+
+
+Using VM Snapshots
+~~~~~~~~~~~~~~~~~~
+
+To create a VM snapshot using the CloudStack UI:
+
+#. Log in to the CloudStack UI as a user or administrator.
+
+#. Click Instances.
+
+#. Click the name of the VM you want to snapshot.
+
+#. Click the Take VM Snapshot button. |VMSnapshotButton.png|
+
+ .. note::
+ If a snapshot is already in progress, then clicking this button
+ will have no effect.
+
+#. Provide a name and description. These will be displayed in the VM
+ Snapshots list.
+
+#. (For running VMs only) If you want to include the VM's memory in the
+ snapshot, click the Memory checkbox. This saves the CPU and memory
+ state of the virtual machine. If you don't check this box, then only
+ the current state of the VM disk is saved. Checking this box makes
+ the snapshot take longer.
+
+#. Quiesce VM: check this box if you want to quiesce the file system on
+ the VM before taking the snapshot. Not supported on XenServer when
+ used with CloudStack-provided primary storage.
+
+ When this option is used with CloudStack-provided primary storage,
+ the quiesce operation is performed by the underlying hypervisor
+ (VMware is supported). When used with another primary storage
+ vendor's plugin, the quiesce operation is provided according to the
+ vendor's implementation.
+
+#. Click OK.
+
+To delete a snapshot or restore a VM to the state saved in a particular
+snapshot:
+
+#. Navigate to the VM as described in the earlier steps.
+
+#. Click View VM Snapshots.
+
+#. In the list of snapshots, click the name of the snapshot you want to
+ work with.
+
+#. Depending on what you want to do:
+
+ To delete the snapshot, click the Delete button. |delete-button.png|
+
+ To revert to the snapshot, click the Revert button. |revert-vm.png|
+
+.. note::
+ VM snapshots are deleted automatically when a VM is destroyed. You don't
+ have to manually delete the snapshots in this case.
+
+
+Changing the VM Name, OS, or Group
+----------------------------------
+
+After a VM is created, you can modify the display name, operating
+system, and the group it belongs to.
+
+To access a VM through the CloudStack UI:
+
+#. Log in to the CloudStack UI as a user or admin.
+
+#. In the left navigation, click Instances.
+
+#. Select the VM that you want to modify.
+
+#. Click the Stop button to stop the VM. |StopButton.png|
+
+#. Click Edit. |EditButton.png|
+
+#. Make the desired changes to the following:
+
+#. **Display name**: Enter a new display name if you want to change the
+ name of the VM.
+
+#. **OS Type**: Select the desired operating system.
+
+#. **Group**: Enter the group name for the VM.
+
+#. Click Apply.
+
+
+Appending a Display Name to the Guest VM’s Internal Name
+--------------------------------------------------------
+
+Every guest VM has an internal name. The host uses the internal name to
+identify the guest VMs. CloudStack gives you an option to provide a
+guest VM with a display name. You can set this display name as the
+internal name so that the vCenter can use it to identify the guest VM. A
+new global parameter, vm.instancename.flag, has now been added to
+achieve this functionality.
+
+The default format of the internal name is
+i-<user\_id>-<vm\_id>-<instance.name>, where instance.name is a global
+parameter. However, If vm.instancename.flag is set to true, and if a
+display name is provided during the creation of a guest VM, the display
+name is appended to the internal name of the guest VM on the host. This
+makes the internal name format as i-<user\_id>-<vm\_id>-<displayName>.
+The default value of vm.instancename.flag is set to false. This feature
+is intended to make the correlation between instance names and internal
+names easier in large data center deployments.
+
+The following table explains how a VM name is displayed in different
+scenarios.
+
+.. cssclass:: table-striped table-bordered table-hover
+
+============================= ======================= ==================== ===================================== ==========================
+User-Provided Display Name vm.instancename.flag Hostname on the VM Name on vCenter Internal Name
+============================= ======================= ==================== ===================================== ==========================
+Yes True Display name i-<user\_id>-<vm\_id>-displayName i-<user\_id>-<vm\_id>-displayName
+No True UUID i-<user\_id>-<vm\_id>-<instance.name> i-<user\_id>-<vm\_id>-<instance.name>
+Yes False Display name i-<user\_id>-<vm\_id>-<instance.name> i-<user\_id>-<vm\_id>-<instance.name>
+No False UUID i-<user\_id>-<vm\_id>-<instance.name> i-<user\_id>-<vm\_id>-<instance.name>
+============================= ======================= ==================== ===================================== ==========================
+
+
+Changing the Service Offering for a VM
+--------------------------------------
+
+To upgrade or downgrade the level of compute resources available to a
+virtual machine, you can change the VM's compute offering.
+
+#. Log in to the CloudStack UI as a user or admin.
+
+#. In the left navigation, click Instances.
+
+#. Choose the VM that you want to work with.
+
+#. (Skip this step if you have enabled dynamic VM scaling; see
+ :ref:`cpu-and-memory-scaling`.)
+
+ Click the Stop button to stop the VM. |StopButton.png|
+
+#. Click the Change Service button. |ChangeServiceButton.png|
+
+ The Change service dialog box is displayed.
+
+#. Select the offering you want to apply to the selected VM.
+
+#. Click OK.
+
+
+.. _cpu-and-memory-scaling:
+
+CPU and Memory Scaling for Running VMs
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+(Supported on VMware and XenServer)
+
+It is not always possible to accurately predict the CPU and RAM
+requirements when you first deploy a VM. You might need to increase
+these resources at any time during the life of a VM. You can dynamically
+modify CPU and RAM levels to scale up these resources for a running VM
+without incurring any downtime.
+
+Dynamic CPU and RAM scaling can be used in the following cases:
+
+- User VMs on hosts running VMware and XenServer.
+
+- System VMs on VMware.
+
+- VMware Tools or XenServer Tools must be installed on the virtual
+ machine.
+
+- The new requested CPU and RAM values must be within the constraints
+ allowed by the hypervisor and the VM operating system.
+
+- New VMs that are created after the installation of CloudStack 4.2 can
+ use the dynamic scaling feature. If you are upgrading from a previous
+ version of CloudStack, your existing VMs created with previous
+ versions will not have the dynamic scaling capability unless you
+ update them using the following procedure.
+
+
+Updating Existing VMs
+~~~~~~~~~~~~~~~~~~~~~
+
+If you are upgrading from a previous version of CloudStack, and you want
+your existing VMs created with previous versions to have the dynamic
+scaling capability, update the VMs using the following steps:
+
+#. Make sure the zone-level setting enable.dynamic.scale.vm is set to
+ true. In the left navigation bar of the CloudStack UI, click
+ Infrastructure, then click Zones, click the zone you want, and click
+ the Settings tab.
+
+#. Install Xen tools (for XenServer hosts) or VMware Tools (for VMware
+ hosts) on each VM if they are not already installed.
+
+#. Stop the VM.
+
+#. Click the Edit button.
+
+#. Click the Dynamically Scalable checkbox.
+
+#. Click Apply.
+
+#. Restart the VM.
+
+
+Configuring Dynamic CPU and RAM Scaling
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To configure this feature, use the following new global configuration
+variables:
+
+- enable.dynamic.scale.vm: Set to True to enable the feature. By
+ default, the feature is turned off.
+
+- scale.retry: How many times to attempt the scaling operation. Default
+ = 2.
+
+
+How to Dynamically Scale CPU and RAM
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To modify the CPU and/or RAM capacity of a virtual machine, you need to
+change the compute offering of the VM to a new compute offering that has
+the desired CPU and RAM values. You can use the same steps described
+above in `“Changing the Service Offering for a
+VM” <#changing-the-service-offering-for-a-vm>`_, but skip the step where you
+stop the virtual machine. Of course, you might have to create a new
+compute offering first.
+
+When you submit a dynamic scaling request, the resources will be scaled
+up on the current host if possible. If the host does not have enough
+resources, the VM will be live migrated to another host in the same
+cluster. If there is no host in the cluster that can fulfill the
+requested level of CPU and RAM, the scaling operation will fail. The VM
+will continue to run as it was before.
+
+
+Limitations
+~~~~~~~~~~~
+
+- You can not do dynamic scaling for system VMs on XenServer.
+
+- CloudStack will not check to be sure that the new CPU and RAM levels
+ are compatible with the OS running on the VM.
+
+- When scaling memory or CPU for a Linux VM on VMware, you might need
+ to run scripts in addition to the other steps mentioned above. For
+ more information, see `Hot adding memory in Linux
+ (1012764) <http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012764>`_
+ in the VMware Knowledge Base.
+
+- (VMware) If resources are not available on the current host, scaling
+ up will fail on VMware because of a known issue where CloudStack and
+ vCenter calculate the available capacity differently. For more
+ information, see
+ `https://issues.apache.org/jira/browse/CLOUDSTACK-1809 <https://issues.apache.org/jira/browse/CLOUDSTACK-1809>`_.
+
+- On VMs running Linux 64-bit and Windows 7 32-bit operating systems,
+ if the VM is initially assigned a RAM of less than 3 GB, it can be
+ dynamically scaled up to 3 GB, but not more. This is due to a known
+ issue with these operating systems, which will freeze if an attempt
+ is made to dynamically scale from less than 3 GB to more than 3 GB.
+
+
+Resetting the Virtual Machine Root Volume on Reboot
+---------------------------------------------------
+
+For secure environments, and to ensure that VM state is not persisted
+across reboots, you can reset the root disk. For more information, see
+`“Reset VM to New Root Disk on
+Reboot” <storage.html#reset-vm-to-new-root-disk-on-reboot>`_.
+
+
+Moving VMs Between Hosts (Manual Live Migration)
+------------------------------------------------
+
+The CloudStack administrator can move a running VM from one host to
+another without interrupting service to users or going into maintenance
+mode. This is called manual live migration, and can be done under the
+following conditions:
+
+- The root administrator is logged in. Domain admins and users can not
+ perform manual live migration of VMs.
+
+- The VM is running. Stopped VMs can not be live migrated.
+
+- The destination host must have enough available capacity. If not, the
+ VM will remain in the "migrating" state until memory becomes
+ available.
+
+- (KVM) The VM must not be using local disk storage. (On XenServer and
+ VMware, VM live migration with local disk is enabled by CloudStack
+ support for XenMotion and vMotion.)
+
+- (KVM) The destination host must be in the same cluster as the
+ original host. (On XenServer and VMware, VM live migration from one
+ cluster to another is enabled by CloudStack support for XenMotion and
+ vMotion.)
+
+To manually live migrate a virtual machine
+
+#. Log in to the CloudStack UI as a user or admin.
+
+#. In the left navigation, click Instances.
+
+#. Choose the VM that you want to migrate.
+
+#. Click the Migrate Instance button. |Migrateinstance.png|
+
+#. From the list of suitable hosts, choose the one to which you want to
+ move the VM.
+
+ .. note::
+ If the VM's storage has to be migrated along with the VM, this will
+ be noted in the host list. CloudStack will take care of the storage
+ migration for you.
+
+#. Click OK.
+
+
+Deleting VMs
+------------
+
+Users can delete their own virtual machines. A running virtual machine
+will be abruptly stopped before it is deleted. Administrators can delete
+any virtual machines.
+
+To delete a virtual machine:
+
+#. Log in to the CloudStack UI as a user or admin.
+
+#. In the left navigation, click Instances.
+
+#. Choose the VM that you want to delete.
+
+#. Click the Destroy Instance button. |Destroyinstance.png|
+
+
+Working with ISOs
+-----------------
+
+CloudStack supports ISOs and their attachment to guest VMs. An ISO is a
+read-only file that has an ISO/CD-ROM style file system. Users can
+upload their own ISOs and mount them on their guest VMs.
+
+ISOs are uploaded based on a URL. HTTP is the supported protocol. Once
+the ISO is available via HTTP specify an upload URL such as
+http://my.web.server/filename.iso.
+
+ISOs may be public or private, like templates.ISOs are not
+hypervisor-specific. That is, a guest on vSphere can mount the exact
+same image that a guest on KVM can mount.
+
+ISO images may be stored in the system and made available with a privacy
+level similar to templates. ISO images are classified as either bootable
+or not bootable. A bootable ISO image is one that contains an OS image.
+CloudStack allows a user to boot a guest VM off of an ISO image. Users
+can also attach ISO images to guest VMs. For example, this enables
+installing PV drivers into Windows. ISO images are not
+hypervisor-specific.
+
+
+Adding an ISO
+~~~~~~~~~~~~~
+
+To make additional operating system or other software available for use
+with guest VMs, you can add an ISO. The ISO is typically thought of as
+an operating system image, but you can also add ISOs for other types of
+software, such as desktop applications that you want to be installed as
+part of a template.
+
+#. Log in to the CloudStack UI as an administrator or end user.
+
+#. In the left navigation bar, click Templates.
+
+#. In Select View, choose ISOs.
+
+#. Click Add ISO.
+
+#. In the Add ISO screen, provide the following:
+
+ - **Name**: Short name for the ISO image. For example, CentOS 6.2
+ 64-bit.
+
+ - **Description**: Display test for the ISO image. For example,
+ CentOS 6.2 64-bit.
+
+ - **URL**: The URL that hosts the ISO image. The Management Server
+ must be able to access this location via HTTP. If needed you can
+ place the ISO image directly on the Management Server
+
+ - **Zone**: Choose the zone where you want the ISO to be available,
+ or All Zones to make it available throughout CloudStack.
+
+ - **Bootable**: Whether or not a guest could boot off this ISO
+ image. For example, a CentOS ISO is bootable, a Microsoft Office
+ ISO is not bootable.
+
+ - **OS Type**: This helps CloudStack and the hypervisor perform
+ certain operations and make assumptions that improve the
+ performance of the guest. Select one of the following.
+
+ - If the operating system of your desired ISO image is listed,
+ choose it.
+
+ - If the OS Type of the ISO is not listed or if the ISO is not
+ bootable, choose Other.
+
+ - (XenServer only) If you want to boot from this ISO in PV mode,
+ choose Other PV (32-bit) or Other PV (64-bit)
+
+ - (KVM only) If you choose an OS that is PV-enabled, the VMs
+ created from this ISO will have a SCSI (virtio) root disk. If
+ the OS is not PV-enabled, the VMs will have an IDE root disk.
+ The PV-enabled types are:
+
+ - Fedora 13
+
+ - Fedora 12
+
+ - Fedora 11
+
+ - Fedora 10
+
+ - Fedora 9
+
+ - Other PV
+
+ - Debian GNU/Linux
+
+ - CentOS 5.3
+
+ - CentOS 5.4
+
+ - CentOS 5.5
+
+ - Red Hat Enterprise Linux 5.3
+
+ - Red Hat Enterprise Linux 5.4
+
+ - Red Hat Enterprise Linux 5.5
+
+ - Red Hat Enterprise Linux 6
+
+ .. note::
+ It is not recommended to choose an older version of the OS than
+ the version in the image. For example, choosing CentOS 5.4 to
+ support a CentOS 6.2 image will usually not work. In these
+ cases, choose Other.
+
+ - **Extractable**: Choose Yes if the ISO should be available for
+ extraction.
+
+ - **Public**: Choose Yes if this ISO should be available to other
+ users.
+
+ - **Featured**: Choose Yes if you would like this ISO to be more
+ prominent for users to select. The ISO will appear in the Featured
+ ISOs list. Only an administrator can make an ISO Featured.
+
+#. Click OK.
+
+ The Management Server will download the ISO. Depending on the size of
+ the ISO, this may take a long time. The ISO status column will
+ display Ready once it has been successfully downloaded into secondary
+ storage. Clicking Refresh updates the download percentage.
+
+#. **Important**: Wait for the ISO to finish downloading. If you move on
+ to the next task and try to use the ISO right away, it will appear to
+ fail. The entire ISO must be available before CloudStack can work
+ with it.
+
+
+Attaching an ISO to a VM
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. In the left navigation, click Instances.
+
+#. Choose the virtual machine you want to work with.
+
+#. Click the Attach ISO button. |iso.png|
+
+#. In the Attach ISO dialog box, select the desired ISO.
+
+#. Click OK.
+
+
+Changing a VM's Base Image
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Every VM is created from a base image, which is a template or ISO which
+has been created and stored in CloudStack. Both cloud administrators and
+end users can create and modify templates, ISOs, and VMs.
+
+In CloudStack, you can change an existing VM's base image from one
+template to another, or from one ISO to another. (You can not change
+from an ISO to a template, or from a template to an ISO).
+
+For example, suppose there is a template based on a particular operating
+system, and the OS vendor releases a software patch. The administrator
+or user naturally wants to apply the patch and then make sure existing
+VMs start using it. Whether a software update is involved or not, it's
+also possible to simply switch a VM from its current template to any
+other desired template.
+
+To change a VM's base image, call the restoreVirtualMachine API command
+and pass in the virtual machine ID and a new template ID. The template
+ID parameter may refer to either a template or an ISO, depending on
+which type of base image the VM was already using (it must match the
+previous type of image). When this call occurs, the VM's root disk is
+first destroyed, then a new root disk is created from the source
+designated in the template ID parameter. The new root disk is attached
+to the VM, and now the VM is based on the new template.
+
+You can also omit the template ID parameter from the
+restoreVirtualMachine call. In this case, the VM's root disk is
+destroyed and recreated, but from the same template or ISO that was
+already in use by the VM.
+
+
+Using SSH Keys for Authentication
+---------------------------------
+
+In addition to the username and password authentication, CloudStack
+supports using SSH keys to log in to the cloud infrastructure for
+additional security. You can use the createSSHKeyPair API to generate
+the SSH keys.
+
+Because each cloud user has their own SSH key, one cloud user cannot log
+in to another cloud user's instances unless they share their SSH key
+files. Using a single SSH key pair, you can manage multiple instances.
+
+
+Creating an Instance Template that Supports SSH Keys
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Create an instance template that supports SSH Keys.
+
+#. Create a new instance by using the template provided by cloudstack.
+
+ For more information on creating a new instance, see
+
+#. Download the cloudstack script from `The SSH Key Gen Script
+ <http://sourceforge.net/projects/cloudstack/files/SSH%20Key%20Gen%20Script/>`_
+ to the instance you have created.
+
+ .. parsed-literal::
+
+ wget http://downloads.sourceforge.net/project/cloudstack/SSH%20Key%20Gen%20Script/cloud-set-guest-sshkey.in?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fcloudstack%2Ffiles%2FSSH%2520Key%2520Gen%2520Script%2F&ts=1331225219&use_mirror=iweb
+
+#. Copy the file to /etc/init.d.
+
+ .. parsed-literal::
+
+ cp cloud-set-guest-sshkey.in /etc/init.d/
+
+#. Give the necessary permissions on the script:
+
+ .. parsed-literal::
+
+ chmod +x /etc/init.d/cloud-set-guest-sshkey.in
+
+#. Run the script while starting up the operating system:
+
+ .. parsed-literal::
+
+ chkconfig --add cloud-set-guest-sshkey.in
+
+#. Stop the instance.
+
+
+Creating the SSH Keypair
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+You must make a call to the createSSHKeyPair api method. You can either
+use the CloudStack Python API library or the curl commands to make the
+call to the cloudstack api.
+
+For example, make a call from the cloudstack server to create a SSH
+keypair called "keypair-doc" for the admin account in the root domain:
+
+.. note::
+ Ensure that you adjust these values to meet your needs. If you are
+ making the API call from a different server, your URL/PORT will be
+ different, and you will need to use the API keys.
+
+#. Run the following curl command:
+
+ .. parsed-literal::
+
+ curl --globoff "http://localhost:8096/?command=createSSHKeyPair&name=keypair-doc&account=admin&domainid=5163440e-c44b-42b5-9109-ad75cae8e8a2"
+
+ The output is something similar to what is given below:
+
+ .. parsed-literal::
+
+ <?xml version="1.0" encoding="ISO-8859-1"?><createsshkeypairresponse cloud-stack-version="3.0.0.20120228045507"><keypair><name>keypair-doc</name><fingerprint>f6:77:39:d5:5e:77:02:22:6a:d8:7f:ce:ab:cd:b3:56</fingerprint><privatekey>-----BEGIN RSA PRIVATE KEY-----
+ MIICXQIBAAKBgQCSydmnQ67jP6lNoXdX3noZjQdrMAWNQZ7y5SrEu4wDxplvhYci
+ dXYBeZVwakDVsU2MLGl/K+wefwefwefwefwefJyKJaogMKn7BperPD6n1wIDAQAB
+ AoGAdXaJ7uyZKeRDoy6wA0UmF0kSPbMZCR+UTIHNkS/E0/4U+6lhMokmFSHtu
+ mfDZ1kGGDYhMsdytjDBztljawfawfeawefawfawfawQQDCjEsoRdgkduTy
+ QpbSGDIa11Jsc+XNDx2fgRinDsxXI/zJYXTKRhSl/LIPHBw/brW8vzxhOlSOrwm7
+ VvemkkgpAkEAwSeEw394LYZiEVv395ar9MLRVTVLwpo54jC4tsOxQCBlloocK
+ lYaocpk0yBqqOUSBawfIiDCuLXSdvBo1Xz5ICTM19vgvEp/+kMuECQBzm
+ nVo8b2Gvyagqt/KEQo8wzH2THghZ1qQ1QRhIeJG2aissEacF6bGB2oZ7Igim5L14
+ 4KR7OeEToyCLC2k+02UCQQCrniSnWKtDVoVqeK/zbB32JhW3Wullv5p5zUEcd
+ KfEEuzcCUIxtJYTahJ1pvlFkQ8anpuxjSEDp8x/18bq3
+ -----END RSA PRIVATE KEY-----
+ </privatekey></keypair></createsshkeypairresponse>
+
+#. Copy the key data into a file. The file looks like this:
+
+ .. parsed-literal::
+
+ -----BEGIN RSA PRIVATE KEY-----
+ MIICXQIBAAKBgQCSydmnQ67jP6lNoXdX3noZjQdrMAWNQZ7y5SrEu4wDxplvhYci
+ dXYBeZVwakDVsU2MLGl/K+wefwefwefwefwefJyKJaogMKn7BperPD6n1wIDAQAB
+ AoGAdXaJ7uyZKeRDoy6wA0UmF0kSPbMZCR+UTIHNkS/E0/4U+6lhMokmFSHtu
+ mfDZ1kGGDYhMsdytjDBztljawfawfeawefawfawfawQQDCjEsoRdgkduTy
+ QpbSGDIa11Jsc+XNDx2fgRinDsxXI/zJYXTKRhSl/LIPHBw/brW8vzxhOlSOrwm7
+ VvemkkgpAkEAwSeEw394LYZiEVv395ar9MLRVTVLwpo54jC4tsOxQCBlloocK
+ lYaocpk0yBqqOUSBawfIiDCuLXSdvBo1Xz5ICTM19vgvEp/+kMuECQBzm
+ nVo8b2Gvyagqt/KEQo8wzH2THghZ1qQ1QRhIeJG2aissEacF6bGB2oZ7Igim5L14
+ 4KR7OeEToyCLC2k+02UCQQCrniSnWKtDVoVqeK/zbB32JhW3Wullv5p5zUEcd
+ KfEEuzcCUIxtJYTahJ1pvlFkQ8anpuxjSEDp8x/18bq3
+ -----END RSA PRIVATE KEY-----
+
+#. Save the file.
+
+
+Creating an Instance
+~~~~~~~~~~~~~~~~~~~~
+
+After you save the SSH keypair file, you must create an instance by
+using the template that you created at `Section 5.2.1, “ Creating an
+Instance Template that Supports SSH Keys” <#create-ssh-template>`__.
+Ensure that you use the same SSH key name that you created at
+`Section 5.2.2, “Creating the SSH Keypair” <#create-ssh-keypair>`__.
+
+.. note::
+ You cannot create the instance by using the GUI at this time and
+ associate the instance with the newly created SSH keypair.
+
+A sample curl command to create a new instance is:
+
+.. parsed-literal::
+
+ curl --globoff http://localhost:<port number>/?command=deployVirtualMachine\&zoneId=1\&serviceOfferingId=18727021-7556-4110-9322-d625b52e0813\&templateId=e899c18a-ce13-4bbf-98a9-625c5026e0b5\&securitygroupids=ff03f02f-9e3b-48f8-834d-91b822da40c5\&account=admin\&domainid=1\&keypair=keypair-doc
+
+Substitute the template, service offering and security group IDs (if you
+are using the security group feature) that are in your cloud
+environment.
+
+
+Logging In Using the SSH Keypair
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To test your SSH key generation is successful, check whether you can log
+in to the cloud setup.
+
+For example, from a Linux OS, run:
+
+.. parsed-literal::
+
+ ssh -i ~/.ssh/keypair-doc <ip address>
+
+The -i parameter tells the ssh client to use a ssh key found at
+~/.ssh/keypair-doc.
+
+
+Resetting SSH Keys
+~~~~~~~~~~~~~~~~~~
+
+With the API command resetSSHKeyForVirtualMachine, a user can set or
+reset the SSH keypair assigned to a virtual machine. A lost or
+compromised SSH keypair can be changed, and the user can access the VM
+by using the new keypair. Just create or register a new keypair, then
+call resetSSHKeyForVirtualMachine.
+
+.. include:: virtual_machines/user-data.rst
+
+
+Assigning GPU/vGPU to Guest VMs
+-------------------------------
+
+CloudStack can deploy guest VMs with Graphics Processing Unit (GPU) or Virtual
+Graphics Processing Unit (vGPU) capabilities on XenServer hosts. At the time of
+VM deployment or at a later stage, you can assign a physical GPU ( known as
+GPU-passthrough) or a portion of a physical GPU card (vGPU) to a guest VM by
+changing the Service Offering. With this capability, the VMs running on
+CloudStack meet the intensive graphical processing requirement by means of the
+high computation power of GPU/vGPU, and CloudStack users can run multimedia
+rich applications, such as Auto-CAD, that they otherwise enjoy at their desk on
+a virtualized environment.
+CloudStack leverages the XenServer support for NVIDIA GRID Kepler 1 and 2 series
+to run GPU/vGPU enabled VMs. NVIDIA GRID cards allows sharing a single GPU cards
+among multiple VMs by creating vGPUs for each VM. With vGPU technology, the
+graphics commands from each VM are passed directly to the underlying dedicated
+GPU, without the intervention of the hypervisor. This allows the GPU hardware
+to be time-sliced and shared across multiple VMs. XenServer hosts use the GPU
+cards in following ways:
+
+**GPU passthrough**: GPU passthrough represents a physical GPU which can be
+directly assigned to a VM. GPU passthrough can be used on a hypervisor alongside
+GRID vGPU, with some restrictions: A GRID physical GPU can either host GRID
+vGPUs or be used as passthrough, but not both at the same time.
+
+**GRID vGPU**: GRID vGPU enables multiple VMs to share a single physical GPU.
+The VMs run an NVIDIA driver stack and get direct access to the GPU. GRID
+physical GPUs are capable of supporting multiple virtual GPU devices (vGPUs)
+that can be assigned directly to guest VMs. Guest VMs use GRID virtual GPUs in
+the same manner as a physical GPU that has been passed through by the
+hypervisor: an NVIDIA driver loaded in the guest VM provides direct access to
+the GPU for performance-critical fast paths, and a paravirtualized interface to
+the GRID Virtual GPU Manager, which is used for nonperformant management
+operations. NVIDIA GRID Virtual GPU Manager for XenServer runs in dom0.
+CloudStack provides you with the following capabilities:
+
+- Adding XenServer hosts with GPU/vGPU capability provisioned by the administrator.
+
+- Creating a Compute Offering with GPU/vGPU capability.
+
+- Deploying a VM with GPU/vGPU capability.
+
+- Destroying a VM with GPU/vGPU capability.
+
+- Allowing an user to add GPU/vGPU support to a VM without GPU/vGPU support by
+ changing the Service Offering and vice-versa.
+
+- Migrating VMs (cold migration) with GPU/vGPU capability.
+
+- Managing GPU cards capacity.
+
+- Querying hosts to obtain information about the GPU cards, supported vGPU types
+ in case of GRID cards, and capacity of the cards.
+
+Prerequisites and System Requirements
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Before proceeding, ensure that you have these prerequisites:
+
+- The vGPU-enabled XenServer 6.2 and later versions.
+ For more information, see `Citrix 3D Graphics Pack <https://www.citrix.com/go/private/vgpu.html>`_.
+
+- GPU/vPGU functionality is supported for following HVM guest operating systems:
+ For more information, see `Citrix 3D Graphics Pack <https://www.citrix.com/go/private/vgpu.html>`_.
+
+- Windows 7 (x86 and x64)
+
+- Windows Server 2008 R2
+
+- Windows Server 2012
+
+- Windows 8 (x86 and x64)
+
+- Windows 8.1 ("Blue") (x86 and x64)
+
+- Windows Server 2012 R2 (server equivalent of "Blue")
+
+- CloudStack does not restrict the deployment of GPU-enabled VMs with guest OS types that are not supported by XenServer for GPU/vGPU functionality. The deployment would be successful and a GPU/vGPU will also get allocated for VMs; however, due to missing guest OS drivers, VM would not be able to leverage GPU resources. Therefore, it is recommended to use GPU-enabled service offering only with supported guest OS.
+
+- NVIDIA GRID K1 (16 GiB video RAM) AND K2 (8 GiB of video RAM) cards supports homogeneous virtual GPUs, implies that at any given time, the vGPUs resident on a single physical GPU must be all of the same type. However, this restriction doesn't extend across physical GPUs on the same card. Each physical GPU on a K1 or K2 may host different types of virtual GPU at the same time. For example, a GRID K2 card has two physical GPUs, and supports four types of virtual GPU; GRID K200, GRID K220Q, GRID K240Q, AND GRID K260Q.
+
+- NVIDIA driver must be installed to enable vGPU operation as for a physical NVIDIA GPU.
+
+- XenServer tools are installed in the VM to get maximum performance on XenServer, regardless of type of vGPU you are using. Without the optimized networking and storage drivers that the XenServer tools provide, remote graphics applications running on GRID vGPU will not deliver maximum performance.
+
+- To deliver high frames from multiple heads on vGPU, install XenDesktop with HDX 3D Pro remote graphics.
+
+Before continuing with configuration, consider the following:
+
+- Deploying VMs GPU/vGPU capability is not supported if hosts are not available with enough GPU capacity.
+
+- A Service Offering cannot be created with the GPU values that are not supported by CloudStack UI. However, you can make an API call to achieve this.
+
+- Dynamic scaling is not supported. However, you can choose to deploy a VM without GPU support, and at a later point, you can change the system offering to upgrade to the one with vGPU. You can achieve this by offline upgrade: stop the VM, upgrade the Service Offering to the one with vGPU, then start the VM.
+
+- Live migration of GPU/vGPU enabled VM is not supported.
+
+- Limiting GPU resources per Account/Domain is not supported.
+
+- Disabling GPU at Cluster level is not supported.
+
+- Notification thresholds for GPU resource is not supported.
+
+Supported GPU Devices
+~~~~~~~~~~~~~~~~~~~~~
+
+.. cssclass:: table-striped table-bordered table-hover
+
+=========== ========================
+Device Type
+=========== ========================
+GPU - Group of NVIDIA Corporation GK107GL [GRID K1] GPUs
+ - Group of NVIDIA Corporation GK104GL [GRID K2] GPUs
+ - Any other GPU Group
+vGPU - GRID K100
+ - GRID K120Q
+ - GRID K140Q
+ - GRID K200
+ - GRID K220Q
+ - GRID K240Q
+ - GRID K260Q
+=========== ========================
+
+GPU/vGPU Assignment Workflow
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+
+CloudStack follows the below sequence of operations to provide GPU/vGPU support for VMs:
+
+#. Ensure that XenServer host is ready with GPU installed and configured.
+ For more information, see `Citrix 3D Graphics Pack <https://www.citrix.com/go/private/vgpu.html>`_.
+
+#. Add the host to CloudStack.
+ CloudStack checks if the host is GPU-enabled or not. CloudStack queries the host and detect if it's GPU enabled.
+
+#. Create a compute offering with GPU/vGPU support:
+ For more information, see `Creating a New Compute Offering <#creating-a-new-compute-offering>`__..
+
+#. Continue with any of the following operations:
+
+ - Deploy a VM.
+
+ Deploy a VM with GPU/vGPU support by selecting appropriate Service Offering. CloudStack decide which host to choose for VM deployment based on following criteria:
+
+ - Host has GPU cards in it. In case of vGPU, CloudStack checks if cards have the required vGPU type support and enough capacity available. Having no appropriate hosts results in an InsufficientServerCapacity exception.
+
+ - Alternately, you can choose to deploy a VM without GPU support, and at a later point, you can change the system offering. You can achieve this by offline upgrade: stop the VM, upgrade the Service Offering to the one with vGPU, then start the VM.
+ In this case, CloudStack gets a list of hosts which have enough capacity to host the VM. If there is a GPU-enabled host, CloudStack reorders this host list and place the GPU-enabled hosts at the bottom of the list.
+
+ - Migrate a VM.
+
+ CloudStack searches for hosts available for VM migration, which satisfies GPU requirement. If the host is available, stop the VM in the current host and perform the VM migration task. If the VM migration is successful, the remaining GPU capacity is updated for both the hosts accordingly.
+
+ - Destroy a VM.
+
+ GPU resources are released automatically when you stop a VM. Once the destroy VM is successful, CloudStack will make a resource call to the host to get the remaining GPU capacity in the card and update the database accordingly.
+
+
+
+.. |basic-deployment.png| image:: /_static/images/basic-deployment.png
+ :alt: Basic two-machine CloudStack deployment
+.. |VMSnapshotButton.png| image:: /_static/images/VMSnapshotButton.png
+ :alt: button to restart a VPC
+.. |delete-button.png| image:: /_static/images/delete-button.png
+.. |EditButton.png| image:: /_static/images/edit-icon.png
+ :alt: button to edit the properties of a VM
+.. |change-affinity-button.png| image:: /_static/images/change-affinity-button.png
+ :alt: button to assign an affinity group to a virtual machine.
+.. |ChangeServiceButton.png| image:: /_static/images/change-service-icon.png
+ :alt: button to change the service of a VM
+.. |Migrateinstance.png| image:: /_static/images/migrate-instance.png
+ :alt: button to migrate an instance
+.. |Destroyinstance.png| image:: /_static/images/destroy-instance.png
+ :alt: button to destroy an instance
+.. |iso.png| image:: /_static/images/iso-icon.png
+ :alt: depicts adding an iso image
+.. |console-icon.png| image:: /_static/images/console-icon.png
+ :alt: depicts adding an iso image
+.. |revert-vm.png| image:: /_static/images/revert-vm.png
+ :alt: depicts adding an iso image
+.. |StopButton.png| image:: /_static/images/stop-instance-icon.png
+ :alt: depicts adding an iso image
diff --git a/source/adminguide/virtual_machines/user-data.rst b/source/adminguide/virtual_machines/user-data.rst
new file mode 100644
index 0000000..c5db9e1
--- /dev/null
+++ b/source/adminguide/virtual_machines/user-data.rst
@@ -0,0 +1,119 @@
+.. 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-Data and Meta-Data
+-----------------------
+
+CloudStack provides API access to attach up to 2KB of data after base64 encoding
+to a deployed VM. Using HTTP POST(via POST body), you can send up to 32K of data
+after base64 encoding. Deployed VMs also have access to instance metadata via
+the virtual router.
+
+Create virtual machine thru the API: `deployVirtualMachine <http://cloudstack.apache.org/docs/api/apidocs-4.5/user/deployVirtualMachine.html>`_
+using the parameter ``userdata=`` to include user-data formated in
+`base64 <https://www.base64encode.org/>`_.
+
+Accessed user-data from VM. Once the IP address of the virtual router is
+known, use the following steps to retrieve 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
+
+
+Using Cloud-Init
+~~~~~~~~~~~~~~~~
+
+`Cloud-Init <https://cloudinit.readthedocs.org/en/latest>`_ can be use to access
+an interpret user-data from virtual machines. Cloud-Init be installed into
+templates and also require CloudStack password and sshkey scripts (:ref:`adding-password-management-to-templates` and `using ssh keys <virtual_machines.html#using-ssh-keys-for-authentication>`_). User password management and
+``resetSSHKeyForVirtualMachine`` API are not yet supported by cloud-init.
+
+#. Install cloud-init package into a template:
+
+ .. code:: bash
+
+ # yum install cloud-init
+ or
+ $ sudo apt-get install cloud-init
+
+#. Create datasource configuration file: ``/etc/cloud/cloud.cfg.d/99_cloudstack.cfg``
+
+ .. code:: yaml
+
+ datasource:
+ CloudStack: {}
+ None: {}
+ datasource_list:
+ - CloudStack
+
+
+user-data example
+~~~~~~~~~~~~~~~~~
+
+This example use cloud-init to Upgrade Operating-System of the newly created VM:
+
+.. code:: yaml
+
+ #cloud-config
+
+ # Upgrade the instance on first boot
+ # (ie run apt-get upgrade)
+ #
+ # Default: false
+ # Aliases: apt_upgrade
+ package_upgrade: true
+
+
+base64 formated:
+
+.. code:: bash
+
+ I2Nsb3VkLWNvbmZpZw0KDQojIFVwZ3JhZGUgdGhlIGluc3RhbmNlIG9uIGZpcnN0IGJvb3QNCiMgKGllIHJ1biBhcHQtZ2V0IHVwZ3JhZGUpDQojDQojIERlZmF1bHQ6IGZhbHNlDQojIEFsaWFzZXM6IGFwdF91cGdyYWRlDQpwYWNrYWdlX3VwZ3JhZGU6IHRydWUNCg==
+
+Refer to `Cloud-Init CloudStack datasource <http://cloudinit.readthedocs.org/en/latest/topics/datasources.html#cloudstack>`_
+documentation for latest capabilities. Cloud-Init and Cloud-Init CloudStack
+datasource are not supported by Apache CloudStack community.
+
diff --git a/source/conceptsandterminology/choosing_deployment_architecture.rst b/source/conceptsandterminology/choosing_deployment_architecture.rst
new file mode 100644
index 0000000..b3a9dec
--- /dev/null
+++ b/source/conceptsandterminology/choosing_deployment_architecture.rst
@@ -0,0 +1,367 @@
+.. 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 architecture used in a deployment will vary depending on the size
+and purpose of the deployment. This section contains examples of
+deployment architecture, including a small-scale deployment useful for
+test and trial deployments and a fully-redundant large-scale setup for
+production deployments.
+
+
+Small-Scale Deployment
+----------------------
+
+|Small-Scale Deployment|
+
+This diagram illustrates the network architecture of a small-scale
+CloudStack deployment.
+
+- A firewall provides a connection to the Internet. The firewall is
+ configured in NAT mode. The firewall forwards HTTP requests and API
+ calls from the Internet to the Management Server. The Management
+ Server resides on the management network.
+
+- A layer-2 switch connects all physical servers and storage.
+
+- A single NFS server functions as both the primary and secondary
+ storage.
+
+- The Management Server is connected to the management network.
+
+
+Large-Scale Redundant Setup
+---------------------------
+
+|Large-Scale Redundant Setup|
+
+This diagram illustrates the network architecture of a large-scale
+CloudStack deployment.
+
+- A layer-3 switching layer is at the core of the data center. A router
+ redundancy protocol like VRRP should be deployed. Typically high-end
+ core switches also include firewall modules. Separate firewall
+ appliances may also be used if the layer-3 switch does not have
+ integrated firewall capabilities. The firewalls are configured in NAT
+ mode. The firewalls provide the following functions:
+
+ - Forwards HTTP requests and API calls from the Internet to the
+ Management Server. The Management Server resides on the management
+ network.
+
+ - When the cloud spans multiple zones, the firewalls should enable
+ site-to-site VPN such that servers in different zones can directly
+ reach each other.
+
+- A layer-2 access switch layer is established for each pod. Multiple
+ switches can be stacked to increase port count. In either case,
+ redundant pairs of layer-2 switches should be deployed.
+
+- The Management Server cluster (including front-end load balancers,
+ Management Server nodes, and the MySQL database) is connected to the
+ management network through a pair of load balancers.
+
+- Secondary storage servers are connected to the management network.
+
+- Each pod contains storage and computing servers. Each storage and
+ computing server should have redundant NICs connected to separate
+ layer-2 access switches.
+
+
+Separate Storage Network
+------------------------
+
+In the large-scale redundant setup described in the previous section,
+storage traffic can overload the management network. A separate storage
+network is optional for deployments. Storage protocols such as iSCSI are
+sensitive to network delays. A separate storage network ensures guest
+network traffic contention does not impact storage performance.
+
+
+Multi-Node Management Server
+----------------------------
+
+The CloudStack Management Server is deployed on one or more front-end
+servers connected to a single MySQL database. Optionally a pair of
+hardware load balancers distributes requests from the web. A backup
+management server set may be deployed using MySQL replication at a
+remote site to add DR capabilities.
+
+|Multi-Node Management Server|
+
+The administrator must decide the following.
+
+- Whether or not load balancers will be used.
+
+- How many Management Servers will be deployed.
+
+- Whether MySQL replication will be deployed to enable disaster
+ recovery.
+
+
+Multi-Site Deployment
+---------------------
+
+The CloudStack platform scales well into multiple sites through the use
+of zones. The following diagram shows an example of a multi-site
+deployment.
+
+|Example Of A Multi-Site Deployment|
+
+Data Center 1 houses the primary Management Server as well as zone 1.
+The MySQL database is replicated in real time to the secondary
+Management Server installation in Data Center 2.
+
+|Separate Storage Network|
+
+This diagram illustrates a setup with a separate storage network. Each
+server has four NICs, two connected to pod-level network switches and
+two connected to storage network switches.
+
+There are two ways to configure the storage network:
+
+- Bonded NIC and redundant switches can be deployed for NFS. In NFS
+ deployments, redundant switches and bonded NICs still result in one
+ network (one CIDR block+ default gateway address).
+
+- iSCSI can take advantage of two separate storage networks (two CIDR
+ blocks each with its own default gateway). Multipath iSCSI client can
+ failover and load balance between separate storage networks.
+
+|NIC Bonding And Multipath I/O|
+
+This diagram illustrates the differences between NIC bonding and
+Multipath I/O (MPIO). NIC bonding configuration involves only one
+network. MPIO involves two separate networks.
+
+
+Choosing a Hypervisor
+---------------------
+
+CloudStack supports many popular hypervisors. Your cloud can consist
+entirely of hosts running a single hypervisor, or you can use multiple
+hypervisors. Each cluster of hosts must run the same hypervisor.
+
+You might already have an installed base of nodes running a particular
+hypervisor, in which case, your choice of hypervisor has already been
+made. If you are starting from scratch, you need to decide what
+hypervisor software best suits your needs. A discussion of the relative
+advantages of each hypervisor is outside the scope of our documentation.
+However, it will help you to know which features of each hypervisor are
+supported by CloudStack. The following table provides this information.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++----------------------------------+-----------+--------------+------------+-----+--------+------------+
+| Feature | XenServer | vSphere | KVM - RHEL | LXC | HyperV | Bare Metal |
++==================================+===========+==============+============+=====+========+============+
+| Network Throttling | Yes | Yes | No | No | ? | N/A |
++----------------------------------+-----------+--------------+------------+-----+--------+------------+
+| Security groups in zones that use| Yes | No | Yes | Yes | ? | No |
+| basic networking | | | | | | |
++----------------------------------+-----------+--------------+------------+-----+--------+------------+
+| iSCSI | Yes | Yes | Yes | Yes | Yes | N/A |
++----------------------------------+-----------+--------------+------------+-----+--------+------------+
+| FibreChannel | Yes | Yes | Yes | Yes | Yes | N/A |
++----------------------------------+-----------+--------------+------------+-----+--------+------------+
+| Local Disk | Yes | Yes | Yes | Yes | Yes | Yes |
++----------------------------------+-----------+--------------+------------+-----+--------+------------+
+| HA | Yes | Yes (Native) | Yes | ? | Yes | N/A |
++----------------------------------+-----------+--------------+------------+-----+--------+------------+
+| Snapshots of local disk | Yes | Yes | Yes | ? | ? | N/A |
++----------------------------------+-----------+--------------+------------+-----+--------+------------+
+| Local disk as data disk | Yes | No | Yes | Yes | Yes | N/A |
++----------------------------------+-----------+--------------+------------+-----+--------+------------+
+| Work load balancing | No | DRS | No | No | ? | N/A |
++----------------------------------+-----------+--------------+------------+-----+--------+------------+
+| Manual live migration of VMs from| Yes | Yes | Yes | ? | Yes | N/A |
+| host to host | | | | | | |
++----------------------------------+-----------+--------------+------------+-----+--------+------------+
+| Conserve management traffic IP | Yes | No | Yes | Yes | ? | N/A |
+| address by using link local | | | | | | |
+| network to communicate with | | | | | | |
+| virtual router | | | | | | |
++----------------------------------+-----------+--------------+------------+-----+--------+------------+
+
+
+Hypervisor Support for Primary Storage
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The following table shows storage options and parameters for different
+hypervisors.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++----------------------------------+-------------+---------------+----------------+----------------+--------+
+| Primary Storage Type | XenServer | vSphere | KVM - RHEL | LXC | HyperV |
++==================================+=============+===============+================+================+========+
+| Format for Disks, Templates, | VHD | VMDK | QCOW2 | | VHD |
+| and Snapshots | | | | | |
++----------------------------------+-------------+---------------+----------------+----------------+--------+
+| iSCSI support | CLVM | VMFS | Yes via Shared | Yes via Shared | No |
+| | | | Mountpoint | Mountpoint | |
++----------------------------------+-------------+---------------+----------------+----------------+--------+
+| Fiber Channel support | Yes, Via | VMFS | Yes via Shared | Yes via Shared | No |
+| | existing SR | | Mountpoint | Mountpoint | |
++----------------------------------+-------------+---------------+----------------+----------------+--------+
+| NFS support | Yes | Yes | Yes | Yes | No |
++----------------------------------+-------------+---------------+----------------+----------------+--------+
+| Local storage support | Yes | Yes | Yes | Yes | Yes |
++----------------------------------+-------------+---------------+----------------+----------------+--------+
+| Storage over-provisioning | NFS | NFS and iSCSI | NFS | | No |
++----------------------------------+-------------+---------------+----------------+----------------+--------+
+| SMB/CIFS | No | No | No | No | Yes |
++----------------------------------+-------------+---------------+----------------+----------------+--------+
+
+XenServer uses a clustered LVM system to store VM images on iSCSI and
+Fiber Channel volumes and does not support over-provisioning in the
+hypervisor. The storage server itself, however, can support
+thin-provisioning. As a result the CloudStack can still support storage
+over-provisioning by running on thin-provisioned storage volumes.
+
+KVM supports "Shared Mountpoint" storage. A shared mountpoint is a file
+system path local to each server in a given cluster. The path must be
+the same across all Hosts in the cluster, for example /mnt/primary1.
+This shared mountpoint is assumed to be a clustered filesystem such as
+OCFS2. In this case the CloudStack does not attempt to mount or unmount
+the storage as is done with NFS. The CloudStack requires that the
+administrator insure that the storage is available
+
+With NFS storage, CloudStack manages the overprovisioning. In this case
+the global configuration parameter storage.overprovisioning.factor
+controls the degree of overprovisioning. This is independent of
+hypervisor type.
+
+Local storage is an option for primary storage for vSphere, XenServer,
+and KVM. When the local disk option is enabled, a local disk storage
+pool is automatically created on each host. To use local storage for the
+System Virtual Machines (such as the Virtual Router), set
+system.vm.use.local.storage to true in global configuration.
+
+CloudStack supports multiple primary storage pools in a Cluster. For
+example, you could provision 2 NFS servers in primary storage. Or you
+could provision 1 iSCSI LUN initially and then add a second iSCSI LUN
+when the first approaches capacity.
+
+
+Best Practices
+--------------
+
+Deploying a cloud is challenging. There are many different technology
+choices to make, and CloudStack is flexible enough in its configuration
+that there are many possible ways to combine and configure the chosen
+technology. This section contains suggestions and requirements about
+cloud deployments.
+
+These should be treated as suggestions and not absolutes. However, we do
+encourage anyone planning to build a cloud outside of these guidelines
+to seek guidance and advice on the project mailing lists.
+
+
+Process Best Practices
+~~~~~~~~~~~~~~~~~~~~~~
+
+- A staging system that models the production environment is strongly
+ advised. It is critical if customizations have been applied to
+ CloudStack.
+
+- Allow adequate time for installation, a beta, and learning the
+ system. Installs with basic networking can be done in hours. Installs
+ with advanced networking usually take several days for the first
+ attempt, with complicated installations taking longer. For a full
+ production system, allow at least 4-8 weeks for a beta to work
+ through all of the integration issues. You can get help from fellow
+ users on the cloudstack-users mailing list.
+
+
+Setup Best Practices
+~~~~~~~~~~~~~~~~~~~~
+
+- Each host should be configured to accept connections only from
+ well-known entities such as the CloudStack Management Server or your
+ network monitoring software.
+
+- Use multiple clusters per pod if you need to achieve a certain switch
+ density.
+
+- Primary storage mountpoints or LUNs should not exceed 6 TB in size.
+ It is better to have multiple smaller primary storage elements per
+ cluster than one large one.
+
+- When exporting shares on primary storage, avoid data loss by
+ restricting the range of IP addresses that can access the storage.
+ See "Linux NFS on Local Disks and DAS" or "Linux NFS on iSCSI".
+
+- NIC bonding is straightforward to implement and provides increased
+ reliability.
+
+- 10G networks are generally recommended for storage access when larger
+ servers that can support relatively more VMs are used.
+
+- Host capacity should generally be modeled in terms of RAM for the
+ guests. Storage and CPU may be overprovisioned. RAM may not. RAM is
+ usually the limiting factor in capacity designs.
+
+- (XenServer) Configure the XenServer dom0 settings to allocate more
+ memory to dom0. This can enable XenServer to handle larger numbers of
+ virtual machines. We recommend 2940 MB of RAM for XenServer dom0. For
+ instructions on how to do this, see
+ `http://support.citrix.com/article/CTX126531
+ <http://support.citrix.com/article/CTX126531>`_.
+ The article refers to XenServer 5.6, but the same information applies
+ to XenServer 6.0.
+
+
+Maintenance Best Practices
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- Monitor host disk space. Many host failures occur because the host's
+ root disk fills up from logs that were not rotated adequately.
+
+- Monitor the total number of VM instances in each cluster, and disable
+ allocation to the cluster if the total is approaching the maximum
+ that the hypervisor can handle. Be sure to leave a safety margin to
+ allow for the possibility of one or more hosts failing, which would
+ increase the VM load on the other hosts as the VMs are redeployed.
+ Consult the documentation for your chosen hypervisor to find the
+ maximum permitted number of VMs per host, then use CloudStack global
+ configuration settings to set this as the default limit. Monitor the
+ VM activity in each cluster and keep the total number of VMs below a
+ safe level that allows for the occasional host failure. For example,
+ if there are N hosts in the cluster, and you want to allow for one
+ host in the cluster to be down at any given time, the total number of
+ VM instances you can permit in the cluster is at most (N-1) \*
+ (per-host-limit). Once a cluster reaches this number of VMs, use the
+ CloudStack UI to disable allocation to the cluster.
+
+.. warning::
+ The lack of up-do-date hotfixes can lead to data corruption and lost VMs.
+
+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.
+
+
+.. |Small-Scale Deployment| image:: /_static/images/small-scale-deployment.png
+.. |Large-Scale Redundant Setup| image:: /_static/images/large-scale-redundant-setup.png
+.. |Multi-Node Management Server| image:: /_static/images/multi-node-management-server.png
+.. |Example Of A Multi-Site Deployment| image:: /_static/images/multi-site-deployment.png
+.. |Separate Storage Network| image:: /_static/images/separate-storage-network.png
+.. |NIC Bonding And Multipath I/O| image:: /_static/images/nic-bonding-and-multipath-io.png
diff --git a/source/conceptsandterminology/concepts.rst b/source/conceptsandterminology/concepts.rst
new file mode 100644
index 0000000..6649d58
--- /dev/null
+++ b/source/conceptsandterminology/concepts.rst
@@ -0,0 +1,723 @@
+.. 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.
+
+
+
+What is Apache CloudStack?
+--------------------------
+
+Apache CloudStack is an open source Infrastructure-as-a-Service platform that
+manages and orchestrates pools of storage, network, and computer resources to
+build a public or private IaaS compute cloud.
+
+With CloudStack you can:
+
+- Set up an on-demand elastic cloud computing service.
+
+- Allow end-users to provision resources
+
+
+What can Apache CloudStack do?
+------------------------------
+
+Multiple Hypervisor Support
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack works with a variety of hypervisors and hypervisor-like
+technologies. A single cloud can contain multiple hypervisor implementations.
+As of the current release CloudStack supports:
+
+- BareMetal (via IPMI)
+
+- Hyper-V
+
+- KVM
+
+- LXC
+
+- vSphere (via vCenter)
+
+- Xenserver
+
+- Xen Project
+
+
+Massively Scalable Infrastructure Management
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack can manage tens of thousands of physical servers installed in
+geographically distributed datacenters. The management server scales
+near-linearly eliminating the need for cluster-level management servers.
+Maintenance or other outages of the management server can occur without
+affecting the virtual machines running in the cloud.
+
+
+Automatic Cloud Configuration Management
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack automatically configures the network and storage settings for each
+virtual machine deployment. Internally, a pool of virtual appliances support
+the operation of configuration of the cloud itself. These appliances offer
+services such as firewalling, routing, DHCP, VPN, console proxy, storage
+access, and storage replication. The extensive use of horizontally scalable
+virtual machines simplifies the installation and ongoing operation of a cloud.
+
+
+Graphical User Interface
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack offers an administrators web interface used for provisioning and
+managing the cloud, as well as an end-user's Web interface, used for running
+VMs and managing VM templates. The UI can be customized to reflect the desired
+service provider or enterprise look and feel.
+
+
+API
+~~~
+
+CloudStack provides a REST-like API for the operation, management and use of
+the cloud.
+
+
+AWS EC2 API Support
+~~~~~~~~~~~~~~~~~~~
+
+CloudStack provides an EC2 API translation layer to permit the common EC2
+tools to be used in the use of a CloudStack cloud.
+
+
+High Availability
+~~~~~~~~~~~~~~~~~
+
+CloudStack has a number of features to increase the availability of the
+system. The Management Server itself may be deployed in a multi-node
+installation where the servers are load balanced. MySQL may be configured to
+use replication to provide for failover in the event of database loss. For the
+hosts, CloudStack supports NIC bonding and the use of separate networks for
+storage as well as iSCSI Multipath.
+
+
+Deployment Architecture Overview
+--------------------------------
+
+Generally speaking, most CloudStack deployments consist of the management
+server and the resources to be managed. During deployment you inform the
+management server of the resources to be managed, such as IP address blocks,
+storage devices, hypervisors, and VLANs.
+
+The minimum installation consists of one machine running the CloudStack
+Management Server and another machine to act as the cloud infrastructure (in
+this case, a very simple infrastructure consisting of one host running
+hypervisor software). In its smallest deployment, a single machine can act as
+both the Management Server and the hypervisor host (using the KVM hypervisor).
+
+.. image:: /_static/images/basic-deployment.png
+
+A more full-featured installation consists of a highly-available multi-node
+Management Server installation and up to tens of thousands of hosts using any
+of several networking technologies.
+
+
+Management Server Overview
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The management server orchestrates and allocates the resources in your cloud
+deployment.
+
+The management server typically runs on a dedicated machine or as a virtual
+machine. It controls allocation of virtual machines to hosts and assigns
+storage and IP addresses to the virtual machine instances. The Management
+Server runs in an Apache Tomcat container and requires a MySQL database for
+persistence.
+
+The management server:
+
+- Provides the web interface for both the adminstrator and end user.
+
+- Provides the API interfaces for both the CloudStack API as well as the EC2
+ interface.
+
+- Manages the assignment of guest VMs to a specific compute resource
+
+- Manages the assignment of public and private IP addresses.
+
+- Allocates storage during the VM instantiation process.
+
+- Manages snapshots, disk images (templates), and ISO images.
+
+- Provides a single point of configuration for your cloud.
+
+.. _infrastructure-overview:
+
+Cloud Infrastructure Overview
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Resources within the cloud are managed as follows:
+
+- Regions: A collection of one or more geographically proximate zones managed
+ by one or more management servers.
+
+- Zones: Typically, a zone is equivalent to a single datacenter. A zone
+ consists of one or more pods and secondary storage.
+
+- Pods: A pod is usually a rack, or row of racks that includes a layer-2
+ switch and one or more clusters.
+
+- Clusters: A cluster consists of one or more homogenous hosts and primary
+ storage.
+
+- Host: A single compute node within a cluster; often a hypervisor.
+
+- Primary Storage: A storage resource typically provided to a single cluster
+ for the actual running of instance disk images. (Zone-wide primary storage
+ is an option, though not typically used.)
+
+- Secondary Storage: A zone-wide resource which stores disk templates, ISO
+ images, and snapshots.
+
+
+Networking Overview
+~~~~~~~~~~~~~~~~~~~
+
+CloudStack offers many types of networking, but they typically fall into one
+of two scenarios:
+
+- Basic: Most analogous to AWS-classic style networking. Provides a single
+ flat layer-2 network where guest isolation is provided at layer-3 by the
+ hypervisors bridge device.
+
+- Advanced: This typically uses layer-2 isolation such as VLANs, though this
+ category also includes SDN technologies such as Nicira NVP.
+
+
+CloudStack Terminology
+----------------------
+
+.. _about-regions:
+
+About Regions
+~~~~~~~~~~~~~
+
+To increase reliability of the cloud, you can optionally group resources
+into multiple geographic regions. A region is the largest available
+organizational unit within a CloudStack deployment. A region is made up
+of several availability zones, where each zone is roughly equivalent to
+a datacenter. Each region is controlled by its own cluster of Management
+Servers, running in one of the zones. The zones in a region are
+typically located in close geographical proximity. Regions are a useful
+technique for providing fault tolerance and disaster recovery.
+
+By grouping zones into regions, the cloud can achieve higher
+availability and scalability. User accounts can span regions, so that
+users can deploy VMs in multiple, widely-dispersed regions. Even if one
+of the regions becomes unavailable, the services are still available to
+the end-user through VMs deployed in another region. And by grouping
+communities of zones under their own nearby Management Servers, the
+latency of communications within the cloud is reduced compared to
+managing widely-dispersed zones from a single central Management Server.
+
+Usage records can also be consolidated and tracked at the region level,
+creating reports or invoices for each geographic region.
+
+.. figure:: /_static/images/region-overview.png
+
+
+Regions are visible to the end user. When a user starts a guest VM on a
+particular CloudStack Management Server, the user is implicitly
+selecting that region for their guest. Users might also be required to
+copy their private templates to additional regions to enable creation of
+guest VMs using their templates in those regions.
+
+
+.. _about-zones:
+
+About Zones
+~~~~~~~~~~~
+
+A zone is the second largest organizational unit within a CloudStack
+deployment. A zone typically corresponds to a single datacenter,
+although it is permissible to have multiple zones in a datacenter. The
+benefit of organizing infrastructure into zones is to provide physical
+isolation and redundancy. For example, each zone can have its own power
+supply and network uplink, and the zones can be widely separated
+geographically (though this is not required).
+
+A zone consists of:
+
+- One or more pods. Each pod contains one or more clusters of hosts and
+ one or more primary storage servers.
+
+- A zone may contain one or more primary storage servers, which are
+ shared by all the pods in the zone.
+
+- Secondary storage, which is shared by all the pods in the zone.
+
+.. figure:: /_static/images/zone-overview.png
+
+Zones are visible to the end user. When a user starts a guest VM, the
+user must select a zone for their guest. Users might also be required to
+copy their private templates to additional zones to enable creation of
+guest VMs using their templates in those zones.
+
+Zones can be public or private. Public zones are visible to all users.
+This means that any user may create a guest in that zone. Private zones
+are reserved for a specific domain. Only users in that domain or its
+subdomains may create guests in that zone.
+
+Hosts in the same zone are directly accessible to each other without
+having to go through a firewall. Hosts in different zones can access
+each other through statically configured VPN tunnels.
+
+For each zone, the administrator must decide the following.
+
+- How many pods to place in each zone.
+
+- How many clusters to place in each pod.
+
+- How many hosts to place in each cluster.
+
+- (Optional) How many primary storage servers to place in each zone and
+ total capacity for these storage servers.
+
+- How many primary storage servers to place in each cluster and total
+ capacity for these storage servers.
+
+- How much secondary storage to deploy in a zone.
+
+When you add a new zone using the CloudStack UI, you will be prompted to
+configure the zone’s physical network and add the first pod, cluster,
+host, primary storage, and secondary storage.
+
+In order to support zone-wide functions for VMware, CloudStack is aware
+of VMware Datacenters and can map each Datacenter to a CloudStack zone.
+To enable features like storage live migration and zone-wide primary
+storage for VMware hosts, CloudStack has to make sure that a zone
+contains only a single VMware Datacenter. Therefore, when you are
+creating a new CloudStack zone, you can select a VMware Datacenter for
+the zone. If you are provisioning multiple VMware Datacenters, each one
+will be set up as a single zone in CloudStack.
+
+.. note::
+ If you are upgrading from a previous CloudStack version, and your existing
+ deployment contains a zone with clusters from multiple VMware Datacenters,
+ that zone will not be forcibly migrated to the new model. It will continue
+ to function as before. However, any new zone-wide operations, such as
+ zone-wide primary storage and live storage migration, will not be available
+ in that zone.
+
+.. _about-pods:
+
+About Pods
+~~~~~~~~~~
+
+A pod often represents a single rack. Hosts in the same pod are in the
+same subnet. A pod is the third-largest organizational unit within a
+CloudStack deployment. Pods are contained within zones. Each zone can
+contain one or more pods. A pod consists of one or more clusters of
+hosts and one or more primary storage servers. Pods are not visible to
+the end user.
+
+.. figure:: /_static/images/pod-overview.png
+
+.. _about-clusters:
+
+About Clusters
+~~~~~~~~~~~~~~
+
+A cluster provides a way to group hosts. To be precise, a cluster is a
+XenServer server pool, a set of KVM servers, , or a VMware cluster
+preconfigured in vCenter. The hosts in a cluster all have identical
+hardware, run the same hypervisor, are on the same subnet, and access
+the same shared primary storage. Virtual machine instances (VMs) can be
+live-migrated from one host to another within the same cluster, without
+interrupting service to the user.
+
+A cluster is the fourth-largest organizational unit within a CloudStack
+deployment. Clusters are contained within pods, and pods are contained
+within zones. Size of the cluster is limited by the underlying
+hypervisor, although the CloudStack recommends less in most cases; see
+Best Practices.
+
+A cluster consists of one or more hosts and one or more primary storage
+servers.
+
+.. figure:: /_static/images/cluster-overview.png
+
+CloudStack allows multiple clusters in a cloud deployment.
+
+Even when local storage is used exclusively, clusters are still required
+organizationally, even if there is just one host per cluster.
+
+When VMware is used, every VMware cluster is managed by a vCenter
+server. An Administrator must register the vCenter server with
+CloudStack. There may be multiple vCenter servers per zone. Each vCenter
+server may manage multiple VMware clusters.
+
+.. _about-hosts:
+
+About Hosts
+~~~~~~~~~~~
+
+A host is a single computer. Hosts provide the computing resources that
+run guest virtual machines. Each host has hypervisor software installed
+on it to manage the guest VMs. For example, a host can be a Citrix
+XenServer server, a Linux KVM-enabled server, an ESXi server, or a
+Windows Hyper-V server.
+
+The host is the smallest organizational unit within a CloudStack
+deployment. Hosts are contained within clusters, clusters are contained
+within pods, pods are contained within zones, and zones can be contained
+within regions.
+
+Hosts in a CloudStack deployment:
+
+- Provide the CPU, memory, storage, and networking resources needed to
+ host the virtual machines
+
+- Interconnect using a high bandwidth TCP/IP network and connect to the
+ Internet
+
+- May reside in multiple data centers across different geographic
+ locations
+
+- May have different capacities (different CPU speeds, different
+ amounts of RAM, etc.), although the hosts within a cluster must all
+ be homogeneous
+
+Additional hosts can be added at any time to provide more capacity for
+guest VMs.
+
+CloudStack automatically detects the amount of CPU and memory resources
+provided by the hosts.
+
+Hosts are not visible to the end user. An end user cannot determine
+which host their guest has been assigned to.
+
+For a host to function in CloudStack, you must do the following:
+
+- Install hypervisor software on the host
+
+- Assign an IP address to the host
+
+- Ensure the host is connected to the CloudStack Management Server.
+
+
+About Primary Storage
+~~~~~~~~~~~~~~~~~~~~~
+
+Primary storage is associated with a cluster, and it stores
+virtual disks for all the VMs running on hosts in that cluster.
+On KVM and VMware, you can provision primary storage on a per-zone basis.
+
+You can add multiple primary storage servers to a cluster or zone. At
+least one is required. It is typically located close to the hosts for
+increased performance. CloudStack manages the allocation of guest
+virtual disks to particular primary storage devices.
+
+It is useful to set up zone-wide primary storage when you want to avoid
+extra data copy operations. With cluster-based primary storage, data in
+the primary storage is directly available only to VMs within that
+cluster. If a VM in a different cluster needs some of the data, it must
+be copied from one cluster to another, using the zone's secondary
+storage as an intermediate step. This operation can be unnecessarily
+time-consuming.
+
+For Hyper-V, SMB/CIFS storage is supported. Note that Zone-wide Primary
+Storage is not supported in Hyper-V.
+
+Ceph/RBD storage is only supported by the KVM hypervisor. It can be used
+as Zone-wide Primary Storage.
+
+CloudStack is designed to work with all standards-compliant iSCSI and
+NFS servers that are supported by the underlying hypervisor, including,
+for example:
+
+- SolidFire for iSCSI
+
+- Dell EqualLogic™ for iSCSI
+
+- Network Appliances filers for NFS and iSCSI
+
+- Scale Computing for NFS
+
+If you intend to use only local disk for your installation, you can skip
+adding separate primary storage.
+
+
+About Secondary Storage
+~~~~~~~~~~~~~~~~~~~~~~~
+
+Secondary storage stores the following:
+
+- Templates — OS images that can be used to boot VMs and can include
+ additional configuration information, such as installed applications
+
+- ISO images — disc images containing data or bootable media for
+ operating systems
+
+- Disk volume snapshots — saved copies of VM data which can be used for
+ data recovery or to create new templates
+
+The items in secondary storage are available to all hosts in the scope
+of the secondary storage, which may be defined as per zone or per
+region.
+
+To make items in secondary storage available to all hosts throughout the
+cloud, you can add object storage in addition to the zone-based NFS
+Secondary Staging Store. It is not necessary to copy templates and
+snapshots from one zone to another, as would be required when using zone
+NFS alone. Everything is available everywhere.
+
+For Hyper-V hosts, SMB/CIFS storage is supported.
+
+CloudStack provides plugins that enable both OpenStack Object Storage
+(Swift, `swift.openstack.org <http://swift.openstack.org>`__) and Amazon
+Simple Storage Service (S3) object storage. When using one of these
+storage plugins, you configure Swift or S3 storage for the entire
+CloudStack, then set up the NFS Secondary Staging Store for each zone.
+The NFS storage in each zone acts as a staging area through which all
+templates and other secondary storage data pass before being forwarded
+to Swift or S3. The backing object storage acts as a cloud-wide
+resource, making templates and other data available to any zone in the
+cloud.
+
+.. warning::
+ Heterogeneous Secondary Storage is not supported in Regions. For example,
+ you cannot set up multiple zones, one using NFS secondary and the other
+ using S3 or Swift secondary.
+
+
+About Physical Networks
+~~~~~~~~~~~~~~~~~~~~~~~
+
+Part of adding a zone is setting up the physical network. One or (in an
+advanced zone) more physical networks can be associated with each zone.
+The network corresponds to a NIC on the hypervisor host. Each physical
+network can carry one or more types of network traffic. The choices of
+traffic type for each network vary depending on whether you are creating
+a zone with basic networking or advanced networking.
+
+A physical network is the actual network hardware and wiring in a zone.
+A zone can have multiple physical networks. An administrator can:
+
+- Add/Remove/Update physical networks in a zone
+
+- Configure VLANs on the physical network
+
+- Configure a name so the network can be recognized by hypervisors
+
+- Configure the service providers (firewalls, load balancers, etc.)
+ available on a physical network
+
+- Configure the IP addresses trunked to a physical network
+
+- Specify what type of traffic is carried on the physical network, as
+ well as other properties like network speed
+
+
+Basic Zone Network Traffic Types
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+When basic networking is used, there can be only one physical network in
+the zone. That physical network carries the following traffic types:
+
+- Guest. When end users run VMs, they generate guest traffic. The guest
+ VMs communicate with each other over a network that can be referred
+ to as the guest network. Each pod in a basic zone is a broadcast
+ domain, and therefore each pod has a different IP range for the guest
+ network. The administrator must configure the IP range for each pod.
+
+- Management. When CloudStack's internal resources communicate with
+ each other, they generate management traffic. This includes
+ communication between hosts, system VMs (VMs used by CloudStack to
+ perform various tasks in the cloud), and any other component that
+ communicates directly with the CloudStack Management Server. You must
+ configure the IP range for the system VMs to use.
+
+.. note::
+ We strongly recommend the use of separate NICs for management traffic
+ and guest traffic.
+
+- Public. Public traffic is generated when VMs in the cloud access the
+ Internet. Publicly accessible IPs must be allocated for this purpose.
+ End users can use the CloudStack UI to acquire these IPs to implement
+ NAT between their guest network and the public network, as described
+ in Acquiring a New IP Address.
+
+- Storage. While labeled "storage" this is specifically about secondary
+ storage, and doesn't affect traffic for primary storage. This
+ includes traffic such as VM templates and snapshots, which is sent
+ between the secondary storage VM and secondary storage servers.
+ CloudStack uses a separate Network Interface Controller (NIC) named
+ storage NIC for storage network traffic. Use of a storage NIC that
+ always operates on a high bandwidth network allows fast template and
+ snapshot copying. You must configure the IP range to use for the
+ storage network.
+
+In a basic network, configuring the physical network is fairly
+straightforward. In most cases, you only need to configure one guest
+network to carry traffic that is generated by guest VMs. If you use a
+NetScaler load balancer and enable its elastic IP and elastic load
+balancing (EIP and ELB) features, you must also configure a network to
+carry public traffic. CloudStack takes care of presenting the necessary
+network configuration steps to you in the UI when you add a new zone.
+
+
+Basic Zone Guest IP Addresses
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+When basic networking is used, CloudStack will assign IP addresses in
+the CIDR of the pod to the guests in that pod. The administrator must
+add a Direct IP range on the pod for this purpose. These IPs are in the
+same VLAN as the hosts.
+
+.. _about-adv-network-traffic-types:
+
+Advanced Zone Network Traffic Types
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+When advanced networking is used, there can be multiple physical
+networks in the zone. Each physical network can carry one or more
+traffic types, and you need to let CloudStack know which type of network
+traffic you want each network to carry. The traffic types in an advanced
+zone are:
+
+- Guest. When end users run VMs, they generate guest traffic. The guest
+ VMs communicate with each other over a network that can be referred
+ to as the guest network. This network can be isolated or shared. In
+ an isolated guest network, the administrator needs to reserve VLAN
+ ranges to provide isolation for each CloudStack account’s network
+ (potentially a large number of VLANs). In a shared guest network, all
+ guest VMs share a single network.
+
+- Management. When CloudStack’s internal resources communicate with
+ each other, they generate management traffic. This includes
+ communication between hosts, system VMs (VMs used by CloudStack to
+ perform various tasks in the cloud), and any other component that
+ communicates directly with the CloudStack Management Server. You must
+ configure the IP range for the system VMs to use.
+
+- Public. Public traffic is generated when VMs in the cloud access the
+ Internet. Publicly accessible IPs must be allocated for this purpose.
+ End users can use the CloudStack UI to acquire these IPs to implement
+ NAT between their guest network and the public network, as described
+ in “Acquiring a New IP Address” in the Administration Guide.
+
+- Storage. While labeled "storage" this is specifically about secondary
+ storage, and doesn't affect traffic for primary storage. This
+ includes traffic such as VM templates and snapshots, which is sent
+ between the secondary storage VM and secondary storage servers.
+ CloudStack uses a separate Network Interface Controller (NIC) named
+ storage NIC for storage network traffic. Use of a storage NIC that
+ always operates on a high bandwidth network allows fast template and
+ snapshot copying. You must configure the IP range to use for the
+ storage network.
+
+These traffic types can each be on a separate physical network, or they
+can be combined with certain restrictions. When you use the Add Zone
+wizard in the UI to create a new zone, you are guided into making only
+valid choices.
+
+
+Advanced Zone Guest IP Addresses
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+When advanced networking is used, the administrator can create
+additional networks for use by the guests. These networks can span the
+zone and be available to all accounts, or they can be scoped to a single
+account, in which case only the named account may create guests that
+attach to these networks. The networks are defined by a VLAN ID, IP
+range, and gateway. The administrator may provision thousands of these
+networks if desired. Additionally, the administrator can reserve a part
+of the IP address space for non-CloudStack VMs and servers.
+
+
+Advanced Zone Public IP Addresses
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+When advanced networking is used, the administrator can create
+additional networks for use by the guests. These networks can span the
+zone and be available to all accounts, or they can be scoped to a single
+account, in which case only the named account may create guests that
+attach to these networks. The networks are defined by a VLAN ID, IP
+range, and gateway. The administrator may provision thousands of these
+networks if desired.
+
+.. _about_system_reserved_ip_addresses:
+
+System Reserved IP Addresses
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+In each zone, you need to configure a range of reserved IP addresses for
+the management network. This network carries communication between the
+CloudStack Management Server and various system VMs, such as Secondary
+Storage VMs, Console Proxy VMs, and DHCP.
+
+The reserved IP addresses must be unique across the cloud. You cannot,
+for example, have a host in one zone which has the same private IP
+address as a host in another zone.
+
+The hosts in a pod are assigned private IP addresses. These are
+typically RFC1918 addresses. The Console Proxy and Secondary Storage
+system VMs are also allocated private IP addresses in the CIDR of the
+pod that they are created in.
+
+Make sure computing servers and Management Servers use IP addresses
+outside of the System Reserved IP range. For example, suppose the System
+Reserved IP range starts at 192.168.154.2 and ends at 192.168.154.7.
+CloudStack can use .2 to .7 for System VMs. This leaves the rest of the
+pod CIDR, from .8 to .254, for the Management Server and hypervisor
+hosts.
+
+**In all zones:**
+
+Provide private IPs for the system in each pod and provision them in
+CloudStack.
+
+For KVM and XenServer, the recommended number of private IPs per pod is
+one per host. If you expect a pod to grow, add enough private IPs now to
+accommodate the growth.
+
+**In a zone that uses advanced networking:**
+
+For zones with advanced networking, we recommend provisioning enough
+private IPs for your total number of customers, plus enough for the
+required CloudStack System VMs. Typically, about 10 additional IPs are
+required for the System VMs. For more information about System VMs, see
+the section on working with SystemVMs in the Administrator's Guide.
+
+When advanced networking is being used, the number of private IP
+addresses available in each pod varies depending on which hypervisor is
+running on the nodes in that pod. Citrix XenServer and KVM use
+link-local addresses, which in theory provide more than 65,000 private
+IP addresses within the address block. As the pod grows over time, this
+should be more than enough for any reasonable number of hosts as well as
+IP addresses for guest virtual routers. VMWare ESXi, by contrast uses
+any administrator-specified subnetting scheme, and the typical
+administrator provides only 255 IPs per pod. Since these are shared by
+physical machines, the guest virtual router, and other entities, it is
+possible to run out of private IPs when scaling up a pod whose nodes are
+running ESXi.
+
+To ensure adequate headroom to scale private IP space in an ESXi pod
+that uses advanced networking, use one or both of the following
+techniques:
+
+- Specify a larger CIDR block for the subnet. A subnet mask with a /20
+ suffix will provide more than 4,000 IP addresses.
+
+- Create multiple pods, each with its own subnet. For example, if you
+ create 10 pods and each pod has 255 IPs, this will provide 2,550 IP
+ addresses.
diff --git a/source/conceptsandterminology/index.rst b/source/conceptsandterminology/index.rst
new file mode 100644
index 0000000..9e57598
--- /dev/null
+++ b/source/conceptsandterminology/index.rst
@@ -0,0 +1,64 @@
+.. 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 Installation Documentation master file, created by
+ sphinx-quickstart on Sat Jan 25 15:15:31 2014.
+ You can adapt this file completely to your liking, but it should at least
+ contain the root `toctree` directive.
+
+|menu_acs_logo|
+
+
+CloudStack Concepts and Terminology
+===================================
+
+This is the Apache CloudStack installation guide. In this guide we first go through some design and architectural to build your cloud.
+
+.. toctree::
+
+Concepts and Terminolgy
+------------------------
+.. toctree::
+ :maxdepth: 2
+
+ concepts.rst
+
+.. architecture:
+
+Choosing a Deployment Architecture
+----------------------------------
+.. toctree::
+ :maxdepth: 2
+
+ choosing_deployment_architecture
+
+.. _network:
+
+Network Setup
+-------------
+.. toctree::
+ :maxdepth: 2
+
+ network_setup
+
+.. _storage:
+
+
+Storage Setup
+-------------
+.. toctree::
+ :maxdepth: 2
+
+ storage_setup
diff --git a/source/conceptsandterminology/locale/pot/administration_guide.pot b/source/conceptsandterminology/locale/pot/administration_guide.pot
new file mode 100644
index 0000000..b26c37d
--- /dev/null
+++ b/source/conceptsandterminology/locale/pot/administration_guide.pot
@@ -0,0 +1,1011 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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_guide.rst:2
+# f93ee7d929a94d1aa72564b1870baf22
+msgid "Apache CloudStack Administration Guide"
+msgstr ""
+
+#: ../../administration_guide.rst:5
+# 991318d1af8b4843b6b599dd8efc6fd3
+msgid "Backups"
+msgstr ""
+
+#: ../../administration_guide.rst:8
+# 917231f850524d1ba0f1eb122f495ede
+msgid "Monitoring"
+msgstr ""
+
+#: ../../administration_guide.rst:11
+# 7ad6e9ad4b414f67a22054dcabf5fd93
+msgid "SNMP"
+msgstr ""
+
+#: ../../administration_guide.rst:13
+# a61d4132541c4dc6aa18461706c73805
+msgid "CloudStack will send alerts for a number of"
+msgstr ""
+
+#: ../../administration_guide.rst:16
+# e9b1920a542846c4b6dd7350f24604ff
+msgid "Syslog"
+msgstr ""
+
+#: ../../administration_guide.rst:19
+# 79a88d29791844eb871f809b9f93b92a
+msgid "AMQP"
+msgstr ""
+
+#: ../../administration_guide.rst:22
+# 3b8760c6578349c3b77f6f4ea36bbd5a
+msgid "JMX"
+msgstr ""
+
+#: ../../administration_guide.rst:25
+# b39837fbf8d44f1782538f8355388429
+msgid "API Queries"
+msgstr ""
+
+#: ../../administration_guide.rst:29
+# 2e929ed37ab146e999d737a2a372af41
+msgid "Usage"
+msgstr ""
+
+#: ../../administration_guide.rst:32
+# 4c07a35f678448539c1b8e6cf720d6a0
+msgid "Tuning"
+msgstr ""
+
+#: ../../administration_guide.rst:35
+# 9eae43d89b224ca89534b9a12061f257
+msgid "Configuration Parameters"
+msgstr ""
+
+#: ../../administration_guide.rst:38
+# 3975ef164d6744b2a634522261de942b
+msgid "System Reliability and Availability"
+msgstr ""
+
+#: ../../administration_guide.rst:41
+# 2c563940c8a04c2dadce14ae1234e87a
+msgid "HA for Management Server"
+msgstr ""
+
+#: ../../administration_guide.rst:43
+# 8c3d685775114722b0287e3aa03c4f11
+msgid "The CloudStack Management Server should be deployed in a multi-node configuration such that it is not susceptible to individual server failures. The Management Server itself (as distinct from the MySQL database) is stateless and may be placed behind a load balancer."
+msgstr ""
+
+#: ../../administration_guide.rst:45
+# 98974855279a4cbaa867412f06e89600
+msgid "Normal operation of Hosts is not impacted by an outage of all Management Serves. All guest VMs will continue to work."
+msgstr ""
+
+#: ../../administration_guide.rst:47
+# b5c9018bcbc8477db8c34093fc16116c
+msgid "When the Management Server is down, no new VMs can be created, and the end user and admin UI, API, dynamic load distribution, and HA will cease to work."
+msgstr ""
+
+#: ../../administration_guide.rst:50
+# 5fc98a91cc354695bb9eff610b8667e7
+msgid "Management Server Load Balancing"
+msgstr ""
+
+#: ../../administration_guide.rst:52
+# 84b4167f5b1a4b4c9744f07cff1bab35
+msgid "CloudStack can use a load balancer to provide a virtual IP for multiple Management Servers. The administrator is responsible for creating the load balancer rules for the Management Servers. The application requires persistence or stickiness across multiple sessions. The following chart lists the ports that should be load balanced and whether or not persistence is required."
+msgstr ""
+
+#: ../../administration_guide.rst:55
+# cd27881746f04a0d929b9b6efd8b3d32
+msgid "Source port"
+msgstr ""
+
+#: ../../administration_guide.rst:55
+# 91f8db675e8f450a8bcd25455b6bd233
+msgid "Destination port"
+msgstr ""
+
+#: ../../administration_guide.rst:55
+# 2ed27a6df81448a9aa9c47172789d416
+msgid "Protocol"
+msgstr ""
+
+#: ../../administration_guide.rst:55
+# 644cdfa1ecaa49d496e7178d9d07fc69
+msgid "Persistence Required?"
+msgstr ""
+
+#: ../../administration_guide.rst:57
+# b656bdc5be594529bb49cddceb0bda5e
+msgid "80 or 443"
+msgstr ""
+
+#: ../../administration_guide.rst:57
+# e16e25248cb14bae876a878e767125b0
+msgid "8080 (or 20400 with AJP)"
+msgstr ""
+
+#: ../../administration_guide.rst:57
+# ce20e784c0e24c4ea83294648499787e
+msgid "HTTP (or AJP)"
+msgstr ""
+
+#: ../../administration_guide.rst:57
+#: ../../administration_guide.rst:58
+# ab33be8dc5424aedb9ee5f24062b29c5
+# 46d9c33fc2274527b9346717f23cfad5
+msgid "Yes"
+msgstr ""
+
+#: ../../administration_guide.rst:58
+#: ../../administration_guide.rst:58
+# e9feebce20be4306bd10338e1ff06068
+# 11f22c09784940779d1699defd245efe
+msgid "8250"
+msgstr ""
+
+#: ../../administration_guide.rst:58
+# a791a4167bcb4daca73ecd1b64a23fa2
+msgid "TCP"
+msgstr ""
+
+#: ../../administration_guide.rst:61
+# 33d8b086229e4f19a53a623fb5e62a13
+msgid "In addition to above settings, the administrator is responsible for setting the 'host' global config value from the management server IP to load balancer virtual IP address. If the 'host' value is not set to the VIP for Port 8250 and one of your management servers crashes, the UI is still available but the system VMs will not be able to contact the management server."
+msgstr ""
+
+#: ../../administration_guide.rst:64
+# 2006569208ac4cf7bf748dff1cfe0953
+msgid "Limiting the Rate of API Requests"
+msgstr ""
+
+#: ../../administration_guide.rst:66
+# fcee3fe6cc9d43c0a398617ba6470d26
+msgid "You can limit the rate at which API requests can be placed for each account. This is useful to avoid malicious attacks on the Management Server, prevent performance degradation, and provide fairness to all accounts."
+msgstr ""
+
+#: ../../administration_guide.rst:68
+# 19fee786cade47c6a5592329e9b61745
+msgid "If the number of API calls exceeds the threshold, an error message is returned for any additional API calls. The caller will have to retry these API calls at another time."
+msgstr ""
+
+#: ../../administration_guide.rst:71
+# ad4394d6414847698ae7ba0e0f06ce30
+msgid "Configuring the API Request Rate"
+msgstr ""
+
+#: ../../administration_guide.rst:73
+# f1b90e13ad004a9d86dff559e7cddd6f
+msgid "To control the API request rate, use the following global configuration settings:"
+msgstr ""
+
+#: ../../administration_guide.rst:75
+# 9516f8c3a536423eaadf5546bc517da5
+msgid "api.throttling.enabled - Enable/Disable API throttling. By default, this setting is false, so API throttling is not enabled."
+msgstr ""
+
+#: ../../administration_guide.rst:76
+# b54b779ffe264d118f981c55fe99e7a7
+msgid "api.throttling.interval (in seconds) - Time interval during which the number of API requests is to be counted. When the interval has passed, the API count is reset to 0."
+msgstr ""
+
+#: ../../administration_guide.rst:77
+# a7bea7af86a04d71b340651cadc683c1
+msgid "api.throttling.max - Maximum number of APIs that can be placed within the api.throttling.interval period."
+msgstr ""
+
+#: ../../administration_guide.rst:78
+# 83fa5f527dd84379bd9b795c5b5312c6
+msgid "api.throttling.cachesize - Cache size for storing API counters. Use a value higher than the total number of accounts managed by the cloud. One cache entry is needed for each account, to store the running API total for that account."
+msgstr ""
+
+#: ../../administration_guide.rst:81
+# 20c51c7e8faf419484e834d822f70c51
+msgid "Limitations on API Throttling"
+msgstr ""
+
+#: ../../administration_guide.rst:83
+# 71af836eabc940d5bb07abee65674cb7
+msgid "The following limitations exist in the current implementation of this feature:"
+msgstr ""
+
+#: ../../administration_guide.rst:85
+# 9e18534ecf064499bb0a36dc67ac205b
+msgid "In a deployment with multiple Management Servers, the cache is not synchronized across them. In this case, CloudStack might not be able to ensure that only the exact desired number of API requests are allowed. In the worst case, the number of API calls that might be allowed is (number of Management Servers) * (api.throttling.max)."
+msgstr ""
+
+#: ../../administration_guide.rst:86
+# a96908c8874b46d9b7c8178344780dc7
+msgid "The API commands resetApiLimit and getApiLimit are limited to the Management Server where the API is invoked."
+msgstr ""
+
+#: ../../administration_guide.rst:89
+# 93858f39b7614989bc3678c8cd1df365
+msgid "HA-Enabled Virtual Machines"
+msgstr ""
+
+#: ../../administration_guide.rst:91
+# 0d6415d5b5574039a38efe8b1de02cf6
+msgid "The user can specify a virtual machine as HA-enabled. By default, all virtual router VMs and Elastic Load Balancing VMs are automatically configured as HA-enabled. When an HA-enabled VM crashes, CloudStack detects the crash and restarts the VM automatically within the same Availability Zone. HA is never performed across different Availability Zones. CloudStack has a conservative policy towards restarting VMs and ensures that there will never be two instances of the same VM running at the same time. The Management Server attempts to start the VM on another Host in the same cluster."
+msgstr ""
+
+#: ../../administration_guide.rst:93
+# 486b5760db6f46c3af439c515638845f
+msgid "VM HA is not supported when the VM is using local storage."
+msgstr ""
+
+#: ../../administration_guide.rst:96
+# f75f84bdde994ee38e2355c7c09804cb
+msgid "Dedicated HA Hosts"
+msgstr ""
+
+#: ../../administration_guide.rst:98
+# 4afa4063f74d44709ca6f06c01f4ef5e
+msgid "One or more hosts can be designated for use only by HA-enabled VMs that are restarting due to a host failure. Setting up a pool of such dedicated HA hosts as the recovery destination for all HA-enabled VMs is useful to:"
+msgstr ""
+
+#: ../../administration_guide.rst:100
+# c85d9a411f3d445fa32d5756aa4eb8b0
+msgid "Make it easier to determine which VMs have been restarted as part of the CloudStack high-availability function. If a VM is running on a dedicated HA host, then it must be an HA-enabled VM whose original host failed. (With one exception: It is possible for an administrator to manually migrate any VM to a dedicated HA host.)."
+msgstr ""
+
+#: ../../administration_guide.rst:101
+# e8278e9aa42f4badb54a36dcf4bbb83f
+msgid "Keep HA-enabled VMs from restarting on hosts which may be reserved for other purposes."
+msgstr ""
+
+#: ../../administration_guide.rst:103
+# b601599b35184733b326c909fcd39e4c
+msgid "The dedicated HA option is set through a special host tag when the host is created. To allow the administrator to dedicate hosts to only HA-enabled VMs, set the global configuration variable ha.tag to the desired tag (for example, \"ha_host\"), and restart the Management Server. Enter the value in the Host Tags field when adding the host(s) that you want to dedicate to HA-enabled VMs."
+msgstr ""
+
+#: ../../administration_guide.rst:106
+# 04fc21b488b04cbeb84c04decd054192
+msgid "Primary Storage Outage and Data Loss"
+msgstr ""
+
+#: ../../administration_guide.rst:108
+# abba717b117a4182a128d7d3da4ca9e5
+msgid "When a primary storage outage occurs the hypervisor immediately stops all VMs stored on that storage device. Guests that are marked for HA will be restarted as soon as practical when the primary storage comes back on line. With NFS, the hypervisor may allow the virtual machines to continue running depending on the nature of the issue. For example, an NFS hang will cause the guest VMs to be suspended until storage connectivity is restored.Primary storage is not designed to be backed up. Individual volumes in primary storage can be backed up using snapshots."
+msgstr ""
+
+#: ../../administration_guide.rst:111
+# 58deb58752c8404f988211162156aafe
+msgid "Secondary Storage Outage and Data Loss"
+msgstr ""
+
+#: ../../administration_guide.rst:113
+# c131fb29bcb44bac876dfd75bd2da66f
+msgid "For a Zone that has only one secondary storage server, a secondary storage outage will have feature level impact to the system but will not impact running guest VMs. It may become impossible to create a VM with the selected template for a user. A user may also not be able to save snapshots or examine/restore saved snapshots. These features will automatically be available when the secondary storage comes back online."
+msgstr ""
+
+#: ../../administration_guide.rst:115
+# 3f319f23eed9475f90dd4375c5b143e9
+msgid "Secondary storage data loss will impact recently added user data including templates, snapshots, and ISO images. Secondary storage should be backed up periodically. Multiple secondary storage servers can be provisioned within each zone to increase the scalability of the system."
+msgstr ""
+
+#: ../../administration_guide.rst:118
+# 63431ac28ab94015bc3d22a2c9aa5588
+msgid "Managing System VMs"
+msgstr ""
+
+#: ../../administration_guide.rst:120
+# 9cc6d4d767c94824b178fe69f6d3cdd6
+msgid "CloudStack uses several types of system virtual machines to perform tasks in the cloud. In general CloudStack manages these system VMs and creates, starts, and stops them as needed based on scale and immediate needs. However, the administrator should be aware of them and their roles to assist in debugging issues."
+msgstr ""
+
+#: ../../administration_guide.rst:122
+# 266cccfbc6e745ffacd810b2ff7f20c6
+msgid "You can configure the system.vm.random.password parameter to create a random system VM password to ensure higher security. If you reset the value for system.vm.random.password to true and restart the Management Server, a random password is generated and stored encrypted in the database. You can view the decrypted password under the system.vm.password global parameter on the CloudStack UI or by calling the listConfigurations API."
+msgstr ""
+
+#: ../../administration_guide.rst:125
+# 6e644c2ed32b473cb4385b23cefe3063
+msgid "The System VM Template"
+msgstr ""
+
+#: ../../administration_guide.rst:127
+# dae55d4f72894cdfb4f76d76684dcc89
+msgid "The System VMs come from a single template. The System VM has the following characteristics:"
+msgstr ""
+
+#: ../../administration_guide.rst:129
+# 4ca2782f2c2a47999695afbc38836c65
+msgid "Debian 6.0 (\"Squeeze\"), 2.6.32 kernel with the latest security patches from the Debian security APT repository"
+msgstr ""
+
+#: ../../administration_guide.rst:130
+# 3c22e6bff3f74fd9a021e96bae35f25f
+msgid "Has a minimal set of packages installed thereby reducing the attack surface"
+msgstr ""
+
+#: ../../administration_guide.rst:131
+# ea7e6186b6c0472098727daa064a051b
+msgid "32-bit for enhanced performance on Xen/VMWare"
+msgstr ""
+
+#: ../../administration_guide.rst:132
+# d9a9609f2bff4a49bdf88a77257782dd
+msgid "pvops kernel with Xen PV drivers, KVM virtio drivers, and VMware tools for optimum performance on all hypervisors"
+msgstr ""
+
+#: ../../administration_guide.rst:133
+# 99dccc1bfff645c8a364e8e49f0f6c21
+msgid "Xen tools inclusion allows performance monitoring"
+msgstr ""
+
+#: ../../administration_guide.rst:134
+# 50f216bb2fc0492c84ab67700014248e
+msgid "Latest versions of HAProxy, iptables, IPsec, and Apache from debian repository ensures improved security and speed"
+msgstr ""
+
+#: ../../administration_guide.rst:135
+# d114044a0adb4170a56fb3c8c214d032
+msgid "Latest version of JRE from Sun/Oracle ensures improved security and speed"
+msgstr ""
+
+#: ../../administration_guide.rst:138
+# 6a535f3f13ad438d9c47d244bdd057fa
+msgid "Accessing System VMs"
+msgstr ""
+
+#: ../../administration_guide.rst:140
+# 7a5c16c43c6247e48e18cd3e7fcd6495
+msgid "It may sometimes be necessary to access System VMs for diagnostics of certain issues, for example if you are experiencing SSVM (Secondary Storage VM) connection issues. Use the steps below in order to connect to the SSH console of a running System VM."
+msgstr ""
+
+#: ../../administration_guide.rst:142
+# f13f9e8ecc4148f18b10202f85506f55
+msgid "Accessing System VMs over the network requires the use of private keys and connecting to System VMs SSH Daemon on port 3922. XenServer/KVM Hypervisors store this key at /root/.ssh/id_rsa.cloud on each CloudStack agent. To access System VMs running on ESXi, the key is stored on the management server at /var/lib/cloudstack/management/.ssh/id_rsa."
+msgstr ""
+
+#: ../../administration_guide.rst:144
+# 1e8067437ee2421db9b197daa00bae7c
+msgid "Find the details of the System VM #. Log in with admin privileges to the CloudStack UI. #. Click Infrastructure, then System VMs, and then click the name of a running VM. #. Take a note of the 'Host', 'Private IP Address' and 'Link Local IP Address' of the System VM you wish to access."
+msgstr ""
+
+#: ../../administration_guide.rst:148
+# bd2ce6ef46d04462a075510c7534980b
+msgid "XenServer/KVM Hypervisors #. Connect to the Host of which the System VM is running. #. SSH to the 'Link Local IP Address' of the System VM from the Host on which the VM is running."
+msgstr ""
+
+#: ../../administration_guide.rst:151
+# 6433ce3a240d4b2b9c627bd2a5de1dfe
+msgid "Format: ssh -i <path-to-private-key> <link-local-ip> -p 3922 Example: root@faith:~# ssh -i /root/.ssh/id_rsa.cloud 169.254.3.93 -p 3922"
+msgstr ""
+
+#: ../../administration_guide.rst:153
+# de9f86caeb63454e8c576f34193cf7ab
+msgid "ESXi Hypervisors #. Connect to your CloudStack Management Server. #. ESXi users should SSH to the private IP address of the System VM."
+msgstr ""
+
+#: ../../administration_guide.rst:156
+# dcc9b190ecda432bbde1662354d32bef
+msgid "Format: ssh -i <path-to-private-key> <vm-private-ip> -p 3922 Example: root@management:~# ssh -i /var/lib/cloudstack/management/.ssh/id_rsa 172.16.0.250 -p 3922"
+msgstr ""
+
+#: ../../administration_guide.rst:160
+# 2e86ae8ea7464bbd9beeb726acb8b043
+msgid "Multiple System VM Support for VMware"
+msgstr ""
+
+#: ../../administration_guide.rst:162
+# 561c949006c243cf961bff0f079dfe07
+msgid "Every CloudStack zone has single System VM for template processing tasks such as downloading templates, uploading templates, and uploading ISOs. In a zone where VMware is being used, additional System VMs can be launched to process VMware-specific tasks such as taking snapshots and creating private templates. The CloudStack management server launches additional System VMs for VMware-specific tasks as the load increases. The management server monitors and weights all commands sent to these System VMs and performs dynamic load balancing and scaling-up of more System VMs."
+msgstr ""
+
+#: ../../administration_guide.rst:165
+# 912e4a1374ac4bf2925b070cb244ce2a
+msgid "Console Proxy"
+msgstr ""
+
+#: ../../administration_guide.rst:167
+# 22ad7a0de1064dda80e4f083405157f6
+msgid "The Console Proxy is a type of System Virtual Machine that has a role in presenting a console view via the web UI. It connects the user’s browser to the VNC port made available via the hypervisor for the console of the guest. Both the administrator and end user web UIs offer a console connection."
+msgstr ""
+
+#: ../../administration_guide.rst:169
+# e5867fc657414edaa8f94d3deee5fd49
+msgid "Clicking a console icon brings up a new window. The AJAX code downloaded into that window refers to the public IP address of a console proxy VM. There is exactly one public IP address allocated per console proxy VM. The AJAX application connects to this IP. The console proxy then proxies the connection to the VNC port for the requested VM on the Host hosting the guest."
+msgstr ""
+
+#: ../../administration_guide.rst:171
+# fea1c6871dc84d9a921bc61b226fa67b
+msgid "The console proxy VM will periodically report its active session count to the Management Server. The default reporting interval is five seconds. This can be changed through standard Management Server configuration with the parameter consoleproxy.loadscan.interval."
+msgstr ""
+
+#: ../../administration_guide.rst:173
+# f93efafb07bb4c65af3fd841829ed70d
+msgid "Assignment of guest VM to console proxy is determined by first determining if the guest VM has a previous session associated with a console proxy. If it does, the Management Server will assign the guest VM to the target Console Proxy VM regardless of the load on the proxy VM. Failing that, the first available running Console Proxy VM that has the capacity to handle new sessions is used."
+msgstr ""
+
+#: ../../administration_guide.rst:175
+# 79a72a9b6fba4469a648e9e7b4bca111
+msgid "Console proxies can be restarted by administrators but this will interrupt existing console sessions for users."
+msgstr ""
+
+#: ../../administration_guide.rst:178
+# 839f885b3021494684f423b34ea819ce
+msgid "Using a SSL Certificate for the Console Proxy"
+msgstr ""
+
+#: ../../administration_guide.rst:180
+# 13867cd7762344ab9077f325f8730cfa
+msgid "The console viewing functionality uses a dynamic DNS service under the domain name realhostip.com to assist in providing SSL security to console sessions. The console proxy is assigned a public IP address. In order to avoid browser warnings for mismatched SSL certificates, the URL for the new console window is set to the form of https://aaa-bbb-ccc-ddd.realhostip.com. You will see this URL during console session creation. CloudStack includes the realhostip.com SSL certificate in the console proxy VM. Of course, CloudStack cannot know about the DNS A records for our customers' public IPs prior to shipping the software. CloudStack therefore runs a dynamic DNS server that is authoritative for the realhostip.com domain. It maps the aaa-bbb-ccc-ddd part of the DNS name to the IP address aaa.bbb.ccc.ddd on lookups. This allows the browser to correctly connect to the console proxy's public IP, where it then expects and receives a SSL certificate for realhostip.com, and SSL is set up without browser warnings."
+msgstr ""
+
+#: ../../administration_guide.rst:183
+# 7bc985d7c4fa46998631086a174c7e33
+msgid "Changing the Console Proxy SSL Certificate and Domain"
+msgstr ""
+
+#: ../../administration_guide.rst:185
+# be495135cea0497eabd43f1977563093
+msgid "If the administrator prefers, it is possible for the URL of the customer's console session to show a domain other than realhostip.com. The administrator can customize the displayed domain by selecting a different domain and uploading a new SSL certificate and private key. The domain must run a DNS service that is capable of resolving queries for addresses of the form aaa-bbb-ccc-ddd.your.domain to an IPv4 IP address in the form aaa.bbb.ccc.ddd, for example, 202.8.44.1. To change the console proxy domain, SSL certificate, and private key:"
+msgstr ""
+
+#: ../../administration_guide.rst:187
+# 6e1c3859863545bca1234725d578d62c
+msgid "Set up dynamic name resolution or populate all possible DNS names in your public IP range into your existing DNS server with the format aaa-bbb-ccc-ddd.company.com -> aaa.bbb.ccc.ddd."
+msgstr ""
+
+#: ../../administration_guide.rst:188
+# ea592a9486d243eb998954bfcc5621cf
+msgid "Generate the private key and certificate signing request (CSR). When you are using openssl to generate private/public key pairs and CSRs, for the private key that you are going to paste into the CloudStack UI, be sure to convert it into PKCS#8 format."
+msgstr ""
+
+#: ../../administration_guide.rst:190
+# 75aacc2da9c4408caa2777a4b4c9a49d
+msgid "Generate a new 2048-bit private key::"
+msgstr ""
+
+#: ../../administration_guide.rst:192
+# a047f4c4f4ec402c926de521dd46a5cc
+msgid "openssl genrsa -des3 -out yourprivate.key 2048"
+msgstr ""
+
+#: ../../administration_guide.rst:194
+# 54f81ed070be40d48f5bed678a7eb8ed
+msgid "Generate a new certificate CSR::"
+msgstr ""
+
+#: ../../administration_guide.rst:196
+# 4260ff8e5ab7400cb292e890d7b0aa9d
+msgid "openssl req -new -key yourprivate.key -out yourcertificate.csr"
+msgstr ""
+
+#: ../../administration_guide.rst:198
+# a8c4e79660e34691a4a73a719fb9eb31
+msgid "Head to the website of your favorite trusted Certificate Authority, purchase an SSL certificate, and submit the CSR. You should receive a valid certificate in return"
+msgstr ""
+
+#: ../../administration_guide.rst:199
+# 29bb21dc37ce46f78fffa06e4b71302a
+msgid "Convert your private key format into PKCS#8 encrypted format.::"
+msgstr ""
+
+#: ../../administration_guide.rst:201
+# a2fa3e01cb89457190182d716691c200
+msgid "openssl pkcs8 -topk8 -in yourprivate.key -out yourprivate.pkcs8.encrypted.key"
+msgstr ""
+
+#: ../../administration_guide.rst:203
+# b62ad584d36048da8a20f050f4a18f85
+msgid "Convert your PKCS#8 encrypted private key into the PKCS#8 format that is compliant with CloudStack::"
+msgstr ""
+
+#: ../../administration_guide.rst:205
+# a5ccd5855fb5436696cb211da2ee0ba3
+msgid "openssl pkcs8 -in yourprivate.pkcs8.encrypted.key -out yourprivate.pkcs8.key"
+msgstr ""
+
+#: ../../administration_guide.rst:207
+# 7d5fd6db293b4d33afe9046cb296bb4d
+msgid "In the Update SSL Certificate screen of the CloudStack UI, paste the following: *. The certificate you've just generated. *. The private key you've just generated. *. The desired new domain name; for example, company.com"
+msgstr ""
+
+#: ../../administration_guide.rst:212
+# 6d79a146218c4624b5cf981d5bff6257
+msgid "4. The desired new domain name; for example, company.com This stops all currently running console proxy VMs, then restarts them with the new certificate and key. Users might notice a brief interruption in console availability."
+msgstr ""
+
+#: ../../administration_guide.rst:215
+# 8e998b147518419b8c5503db597b2855
+msgid "The Management Server generates URLs of the form \"aaa-bbb-ccc-ddd.company.com\" after this change is made. The new console requests will be served with the new DNS domain name, certificate, and key."
+msgstr ""
+
+#: ../../administration_guide.rst:218
+# d2d3d433bf244542bd961449d46e5899
+msgid "Virtual Router"
+msgstr ""
+
+#: ../../administration_guide.rst:220
+# 9b86999a5c224420bd803344df34468f
+msgid "The virtual router is a type of System Virtual Machine. The virtual router is one of the most frequently used service providers in CloudStack. The end user has no direct access to the virtual router. Users can ping the virtual router and take actions that affect it (such as setting up port forwarding), but users do not have SSH access into the virtual router."
+msgstr ""
+
+#: ../../administration_guide.rst:222
+# a70cb88cc6e3420cabb4f6491fc94ac2
+msgid "Virtual routers can be restarted by administrators, but this will interrupt public network access and other services for end users. A basic test in debugging networking issues is to attempt to ping the virtual router from a guest VM. Some of the characteristics of the virtual router are determined by its associated system service offering.."
+msgstr ""
+
+#: ../../administration_guide.rst:225
+# 1a9122077ee64356a9bba962146fa923
+msgid "Configuring the Virtual Router"
+msgstr ""
+
+#: ../../administration_guide.rst:227
+# 7580f3cac07348bc846c961a3f909830
+msgid "You can set the following: *. IP range *. Supported network services *. Default domain name for the network serviced by the virtual router *. Gateway IP address *. How often CloudStack fetches network usage statistics from CloudStack virtual routers. If you want to collect traffic metering data from the virtual router, set the global configuration parameter router.stats.interval. If you are not using the virtual router to gather network usage statistics, set it to 0."
+msgstr ""
+
+#: ../../administration_guide.rst:235
+# d6b114ce9869442589bdf6a3497ec9f2
+msgid "Upgrading a Virtual Router with System Service Offerings"
+msgstr ""
+
+#: ../../administration_guide.rst:237
+# e32118155eeb466d8480f0c1b7dd3722
+msgid "When CloudStack creates a virtual router, it uses default settings which are defined in a default system service offering. See Section 8.2, “System Service Offerings”. All the virtual routers in a single guest network use the same system service offering. You can upgrade the capabilities of the virtual router by creating and applying a custom system service offering. Define your custom system service offering. Associate the system service offering with a network offering. Apply the network offering to the network where you want the virtual routers to use the new system service offering."
+msgstr ""
+
+#: ../../administration_guide.rst:243
+# 601dda89c2494c4ab1bd253484d3e712
+msgid "Best Practices for Virtual Routers"
+msgstr ""
+
+#: ../../administration_guide.rst:245
+# 7a7205873af44801aeda6f66a69b801d
+msgid "Restarting a virtual router from a hypervisor console deletes all the iptables rules. To work around this issue, stop the virtual router and start it from the CloudStack UI."
+msgstr ""
+
+#: ../../administration_guide.rst:246
+# 454b3914655c456cad86c222d18f6b0c
+msgid "Do not use the destroyRouter API when only one router is available in the network, because restartNetwork API with the cleanup=false parameter can't recreate it later. If you want to destroy and recreate the single router available in the network, use the restartNetwork API with the cleanup=true parameter."
+msgstr ""
+
+#: ../../administration_guide.rst:249
+# 06dc6516cdef42669857d3cfe718cdcd
+msgid "Secondary Storage VM"
+msgstr ""
+
+#: ../../administration_guide.rst:251
+# 62c65c2618d843f9b268de2c88c8be0a
+msgid "In addition to the hosts, CloudStack’s Secondary Storage VM mounts and writes to secondary storage. Submissions to secondary storage go through the Secondary Storage VM. The Secondary Storage VM can retrieve templates and ISO images from URLs using a variety of protocols. The secondary storage VM provides a background task that takes care of a variety of secondary storage activities: downloading a new template to a Zone, copying templates between Zones, and snapshot backups. The administrator can log in to the secondary storage VM if needed."
+msgstr ""
+
+#: ../../administration_guide.rst:258
+# b2b7431b44ed44b98582c98087d894a7
+msgid "Storage Administration"
+msgstr ""
+
+#: ../../administration_guide.rst:261
+# 4d40f40b40294722a88f1949a46cbde9
+msgid "Hypervisor Host Management"
+msgstr ""
+
+#: ../../administration_guide.rst:264
+# 9a05a7311fa54e3e9926dc5f7cd573a3
+msgid "Maintenance mode"
+msgstr ""
+
+#: ../../administration_guide.rst:266
+# 0a40fb0dc55148c8b9150737a3838c80
+msgid "Maintenance mode makes a host unavailable to have new virtual machines allocated to it. It also starts a process by which running virtual machines are live migrated to other available hosts within the same cluster. It should be noted that the live migration is not universally perfect, and you may end up with recalcitrant virtual machines which are unable to be live migrated. This can be due to lack of hypervisor-specific tooling or other problems."
+msgstr ""
+
+#: ../../administration_guide.rst:269
+# 49b847172c8b4366b82efcce5987d880
+msgid "vCenter and Maintenance mode"
+msgstr ""
+
+#: ../../administration_guide.rst:271
+# 034dd713a7d44a43825529cca70afb32
+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 ""
+
+#: ../../administration_guide.rst:273
+# ffa262f627384c329ab46dfe92cb40cc
+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 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 ""
+
+#: ../../administration_guide.rst:274
+# 75b75474bea1490ea5ea35271fd988a7
+msgid "Wait for the \"Ready for Maintenance\" indicator to appear in the UI."
+msgstr ""
+
+#: ../../administration_guide.rst:275
+# 3be72549ff1f4fd4a3c3b471f1a9865d
+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 ""
+
+#: ../../administration_guide.rst:276
+# 0c977a03a8644901bc53be37b0312ad1
+msgid "When the maintenance tasks are complete, take the host out of maintenance mode as follows: a. First use vCenter to exit the vCenter maintenance mode. This makes the host ready for CloudStack to reactivate it. b. 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."
+msgstr ""
+
+#: ../../administration_guide.rst:281
+# 6c1a9c2e7ff1400daa889815e4ffb33d
+msgid "XenServer Maintenance Mode"
+msgstr ""
+
+#: ../../administration_guide.rst:283
+# 805f4ccfdd5e40e88e3ccdd57585f19e
+msgid "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 ""
+
+#: ../../administration_guide.rst:286
+# bcf2b628e6944e33bab4fb118d72de69
+msgid "To place a XenServer host in Maintenace Mode"
+msgstr ""
+
+#: ../../administration_guide.rst:288
+# be9fc81b21864113b444bcdfa60d8575
+msgid "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."
+msgstr ""
+
+#: ../../administration_guide.rst:291
+# d8fa3fc85b964c7981677d1619752eb0
+msgid "Click Enter Maintenance Mode."
+msgstr ""
+
+#: ../../administration_guide.rst:293
+# c0374cf7ce0d48559f5120e3d205f078
+msgid "The server's status in the Resources pane shows when all running VMs have been successfully migrated off the server."
+msgstr ""
+
+#: ../../administration_guide.rst:296
+# 1e19387e9ad04b7d94c1a7cf05e3a773
+msgid "To take a Xenserver host out of Maintenance mode"
+msgstr ""
+
+#: ../../administration_guide.rst:298
+# 94d2cbc337c64bdf8d607a5df92e98a5
+msgid "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."
+msgstr ""
+
+#: ../../administration_guide.rst:301
+# c9326e7208a64ca684a56a38cc7aa332
+msgid "Click Exit Maintenance Mode."
+msgstr ""
+
+#: ../../administration_guide.rst:304
+# ec570b7fa796494eafbaf074c90f322e
+msgid "Disabling and enabling Zones, Pods, and Clusters"
+msgstr ""
+
+#: ../../administration_guide.rst:306
+# 5694f1e98fe849d297e898a5da8648ac
+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. To disable and enable a zone, pod, or cluster:"
+msgstr ""
+
+#: ../../administration_guide.rst:309
+# 83dc1490b2104f3bbf4e3639c0430c61
+msgid "Log in to the CloudStack UI as administrator"
+msgstr ""
+
+#: ../../administration_guide.rst:310
+#: ../../administration_guide.rst:431
+# 3ed8e3e52e234f45b1c0f052ca458bcc
+# cd6f4bb9146e4e9a9018c3066dacab5b
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../administration_guide.rst:311
+# 5e006224fa21497ea7151f8cd9aae1bb
+msgid "In Zones, click View More."
+msgstr ""
+
+#: ../../administration_guide.rst:312
+# 4d77f0e634da42b9ae2447f2fd463d88
+msgid "If you are disabling or enabling a zone, find the name of the zone in the list, and click the Enable/Disable button."
+msgstr ""
+
+#: ../../administration_guide.rst:313
+# 6b2d8b9b33b444d7a0810e78cd39367d
+msgid "If you are disabling or enabling a pod or cluster, click the name of the zone that contains the pod or cluster."
+msgstr ""
+
+#: ../../administration_guide.rst:314
+# f3afc7444ff340848e9db06e1c2344e5
+msgid "Click the Compute tab."
+msgstr ""
+
+#: ../../administration_guide.rst:315
+# dbd6f2cda70a423e8fce05cbf8e07f34
+msgid "In the Pods or Clusters node of the diagram, click View All."
+msgstr ""
+
+#: ../../administration_guide.rst:316
+# 8b38f319abc447e880ee490e347ca82a
+msgid "Click the pod or cluster name in the list."
+msgstr ""
+
+#: ../../administration_guide.rst:317
+# fe5bc552f0c64f7797c894cf1412d2a7
+msgid "Click the Enable/Disable button."
+msgstr ""
+
+#: ../../administration_guide.rst:320
+# 96b1b42987f04136b94d358fe109e27d
+msgid "Removing hypervisor hosts"
+msgstr ""
+
+#: ../../administration_guide.rst:322
+# 21b14acd77c843d6b304b5e5ada65b2c
+msgid "Hosts can be removed from the cloud as needed. The procedure to remove a host depends on the hypervisor type."
+msgstr ""
+
+#: ../../administration_guide.rst:325
+# 5764a1f3b5504905ab2716b487b14b73
+msgid "Removing XenServer and KVM Hosts"
+msgstr ""
+
+#: ../../administration_guide.rst:326
+# 64851f97d4864165a918d783aacf2146
+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 CloudStack:"
+msgstr ""
+
+#: ../../administration_guide.rst:328
+# 8501b1b8ed96490c8f082644861760be
+msgid "Place the node in maintenance mode."
+msgstr ""
+
+#: ../../administration_guide.rst:329
+# 742504a2363043eda29d9583a580bbba
+msgid "For KVM, stop the cloud-agent service."
+msgstr ""
+
+#: ../../administration_guide.rst:330
+# 25e529a1ed534077b4554684f796e60a
+msgid "Use the UI option to remove the node."
+msgstr ""
+
+#: ../../administration_guide.rst:331
+# 3748d1e9df464087a1ffe1ff96240883
+msgid "Then you may power down the Host, re-use its IP address, re-install it, etc"
+msgstr ""
+
+#: ../../administration_guide.rst:334
+# 89d630d304df4b6da185b6f8838b61b9
+msgid "Removing vSphere Hosts"
+msgstr ""
+
+#: ../../administration_guide.rst:335
+# 1219da8f0bd7440190e8d553858df5f4
+msgid "To remove this type of host, first place it in maintenance mode, as described above. 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 ""
+
+#: ../../administration_guide.rst:338
+# a0f69abb2cf4444c99110f98389cafc3
+msgid "Changing hypervisor host password"
+msgstr ""
+
+#: ../../administration_guide.rst:339
+# f2496529c2a74ac4bc7b4b7c41a8871c
+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. To change a hosts password:"
+msgstr ""
+
+#: ../../administration_guide.rst:342
+# 52f8f40fb2b042d395ff895d8275629a
+msgid "Identify all hosts in the cluster."
+msgstr ""
+
+#: ../../administration_guide.rst:343
+# ebc1674d6b164834ab5680e033835ee3
+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 ""
+
+#: ../../administration_guide.rst:344
+# 5364fca0ca7e4a3c918da14795d570eb
+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 ""
+
+#: ../../administration_guide.rst:346
+# 5f9a5267e03246a0b8a4fe18c602cb11
+msgid "mysql> select id from cloud.host where name like '%h%';"
+msgstr ""
+
+#: ../../administration_guide.rst:348
+# 4d1c5ebe23a94d6d91adabbb787b83c9
+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 ""
+
+#: ../../administration_guide.rst:350
+# 44c4b8a1b4874a33885b01d27e877d63
+msgid "mysql> update cloud.host set password='password' where id=5 or id=10 or id=12;"
+msgstr ""
+
+#: ../../administration_guide.rst:353
+# e80d3d60b8b24290920db5afafb13f4c
+msgid "Overprovisioning and Service Offering Limits"
+msgstr ""
+
+#: ../../administration_guide.rst:355
+# 1883429edbe74fdd8a5fb620aec5fdb6
+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 ""
+
+#: ../../administration_guide.rst:357
+# 37b343a408374b90a7a4000a86cf66c1
+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. Over-provisioning ratios are dynamically substituted in CloudStack's capacity calculations. For example:::"
+msgstr ""
+
+#: ../../administration_guide.rst:367
+# 10a7f91d1b664361837ca349ac15d8fe
+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. 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."
+msgstr ""
+
+#: ../../administration_guide.rst:370
+# b0413938593f4a7786b951b21e507d09
+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 ""
+
+#: ../../administration_guide.rst:372
+# 1aaa3fd0e30b4b059a45d437ea210c2e
+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 ""
+
+#: ../../administration_guide.rst:375
+# 69e7d2a62c294b1387f1bc52a47e9a2a
+msgid "Limitations on over-provisioning in KVM and XenServer"
+msgstr ""
+
+#: ../../administration_guide.rst:377
+# d0da750d0eac48eca9e90d923eebab99
+msgid "In XenServer, due to a constraint of this hypervisor, you can not use an over-provisioning factor greater than 4."
+msgstr ""
+
+#: ../../administration_guide.rst:379
+# cb6f018a43e24fea81857c044855d950
+msgid "KVM 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 ""
+
+#: ../../administration_guide.rst:382
+# fe616dbc701e4b61a912343f7be00b58
+msgid "Requirements for Over-Provisioning"
+msgstr ""
+
+#: ../../administration_guide.rst:384
+# 445d78119e204479b74e8418f43a6d37
+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 ""
+
+#: ../../administration_guide.rst:387
+# 0ffbd97c59c2417e8a097daf7b7d19c5
+msgid "Balloon Driver"
+msgstr ""
+
+#: ../../administration_guide.rst:389
+# 499993d9952a44ec935372610be1ba69
+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 ""
+
+#: ../../administration_guide.rst:392
+#: ../../administration_guide.rst:412
+# 4b2a1ef88e894648b0ee154892e11076
+# 631a9ce321b249d8b30164201011194f
+msgid "XenServer"
+msgstr ""
+
+#: ../../administration_guide.rst:394
+# e5a221eef356494a85f9ff179af25612
+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 ""
+
+#: ../../administration_guide.rst:397
+# 2e279386f6e64c04b48f7683628a149e
+msgid "VMware"
+msgstr ""
+
+#: ../../administration_guide.rst:399
+# 90e5b561b31e44a6b8d4ab785d75cfc2
+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 ""
+
+#: ../../administration_guide.rst:402
+# 17b7036f18dc4a279cbd09dc97d887b6
+msgid "KVM"
+msgstr ""
+
+#: ../../administration_guide.rst:404
+# 90644866fa4f42ba8eb2772327104c08
+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 ""
+
+#: ../../administration_guide.rst:407
+# fb51035c29d44f61a1cd1ca69db4f08c
+msgid "Hypervisor capabilities"
+msgstr ""
+
+#: ../../administration_guide.rst:409
+# 3dc6760bd76a49fb82e221c82c02a49a
+msgid "The hypervisor must be capable of using the memory ballooning."
+msgstr ""
+
+#: ../../administration_guide.rst:414
+# a2c2cbb7fc304f1eaedc4f80bc0080a7
+msgid "The DMC (Dynamic Memory Control) capability of the hypervisor should be enabled. Only XenServer Advanced and above versions have this feature."
+msgstr ""
+
+#: ../../administration_guide.rst:417
+# 69e523e5c1a54ce6b70499c8e815d2df
+msgid "VMware, KVM"
+msgstr ""
+
+#: ../../administration_guide.rst:419
+# 4b9a57bcf0c44c0881b43f78263e659a
+msgid "Memory ballooning is supported by default."
+msgstr ""
+
+#: ../../administration_guide.rst:422
+# 842b46aac75e4b55bc95a2884df153b1
+msgid "Setting Over-Provisioning Rations"
+msgstr ""
+
+#: ../../administration_guide.rst:424
+# 8d093dbea4db42028ab4bf0469d67452
+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 ""
+
+#: ../../administration_guide.rst:426
+# d585ebbb38104db185a30519f122ef38
+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 ""
+
+#: ../../administration_guide.rst:428
+# b3bf39b26142443c92ac98f1aa4e7be4
+msgid "To change the over-provisioning ratios for an existing cluster:"
+msgstr ""
+
+#: ../../administration_guide.rst:430
+# 95630036ec0e4f9ba1f10054990ba84d
+msgid "Log in as administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../administration_guide.rst:432
+# a64dd51e12c547658db1ade7de98ebd2
+msgid "Under Clusters, click View All."
+msgstr ""
+
+#: ../../administration_guide.rst:433
+# 23c09f71b4e04bad89d9fc8af656468c
+msgid "Select the cluster you want to work with, and click the Edit button."
+msgstr ""
+
+#: ../../administration_guide.rst:434
+# 0e804d9f17db4c8a981a54fd41556317
+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 ""
+
+#: ../../administration_guide.rst:437
+# c2d182c3388a4abda55289726d7ffcd7
+msgid "Service Offering Limits and Over-Provisioning"
+msgstr ""
+
+#: ../../administration_guide.rst:439
+# 35ebc55bb645476192b0b7676f94c260
+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 ""
+
+#: ../../administration_guide.rst:441
+# 35b941c26c5e4016b305ed1742023a82
+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 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."
+msgstr ""
+
diff --git a/source/conceptsandterminology/locale/pot/alloc.pot b/source/conceptsandterminology/locale/pot/alloc.pot
new file mode 100644
index 0000000..749cb05
--- /dev/null
+++ b/source/conceptsandterminology/locale/pot/alloc.pot
@@ -0,0 +1,409 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../alloc.rst:2
+# b24b21f06cc04967a756901f0d0e77cb
+msgid "Allocators"
+msgstr ""
+
+#: ../../alloc.rst:4
+# 89923eb3bf724b2e92cc7759fbd32e24
+msgid "CloudStack enables administrators to write custom allocators that will choose the Host to place a new guest and the storage host from which to allocate guest virtual disk images."
+msgstr ""
+
+#: ../../alloc.rst:8
+# adab67c72cee443ea0a9fd7a032019e1
+msgid "These are following categories of allocators currently supported:"
+msgstr ""
+
+#: ../../alloc.rst:10
+# 4cdc118725374ee9ba93e57fa19bd227
+msgid "HostAllocators - Allows you to create custom rules to determine which physical host to allocate the guest virtual machines on."
+msgstr ""
+
+#: ../../alloc.rst:13
+# 44ca87f9ea7b4395b5a77aba97b5f8dc
+msgid "StoragePoolAllocators - Allows you to create custom rules to determine which storage pool to allocate the guest virtual machines on."
+msgstr ""
+
+#: ../../alloc.rst:18
+# 6c45cb067c19470da4aeb3e1a20e7e6b
+msgid "Implementing a custom HostAllocator"
+msgstr ""
+
+#: ../../alloc.rst:20
+# 0b22e37a87484153896f253084682a27
+msgid "HostAllocators are written by extending com.cloud.agent.manager.allocator.HostAllocator interface."
+msgstr ""
+
+#: ../../alloc.rst:24
+# 9d13e0b0954e44ffb4460f1f6e76ce3b
+msgid "HostAllocator Interface"
+msgstr ""
+
+#: ../../alloc.rst:26
+# ebabcdc234ab4c7bbf51975a632bea1d
+msgid "The interface defines the following two methods."
+msgstr ""
+
+#: ../../alloc.rst:53
+# b7e66f063c6f489a811321cfc2adbe49
+msgid "A custom HostAllocator can be written by implementing the ‘allocateTo’ method"
+msgstr ""
+
+#: ../../alloc.rst:57
+# 8e50e53c1b264c018cacc95a7a595be9
+msgid "Input Parameters for the method ‘HostAllocator :: allocateTo’"
+msgstr ""
+
+#: ../../alloc.rst:59
+#: ../../alloc.rst:205
+# 101cff90e33d45349e556f5acb90097d
+# f7743f3c0bab4b85a9a542e74fb0fc79
+msgid "*com.cloud.vm.VirtualMachineProfile vmProfile*"
+msgstr ""
+
+#: ../../alloc.rst:61
+#: ../../alloc.rst:207
+# 500f68497c304bb398a46d0f2c71cb82
+# a93dfc81e89e40049463bcf61823d254
+msgid "VirtualMachineProfile describes one virtual machine. This allows the adapters like Allocators to process the information in the virtual machine and make determinations on what the virtual machine profile should look like before it is actually started on the hypervisor."
+msgstr ""
+
+#: ../../alloc.rst:66
+# 7bb65f8cf85c40249c4c86e4013ebb08
+msgid "HostAllocators can make use of the following information present in the VirtualMachineProfile:"
+msgstr ""
+
+#: ../../alloc.rst:69
+# ab33f4550b4b4f5398dae9ff967613e7
+msgid "The ServiceOffering that specifies configuration like requested CPU speed, RAM etc necessary for the guest VM."
+msgstr ""
+
+#: ../../alloc.rst:72
+#: ../../alloc.rst:218
+# 8a58c120af2d48a5891cbebf324799a1
+# 66bd396fb4e04a1d87abd92a050c6ea1
+msgid "The VirtualMachineTemplate, the template to be used to start the VM."
+msgstr ""
+
+#: ../../alloc.rst:74
+#: ../../alloc.rst:220
+# 00608807ab6f46499f2a0479d4c9f5ec
+# 6431648fde024c25b24826374f86a887
+msgid "*com.cloud.deploy.DeploymentPlan plan*"
+msgstr ""
+
+#: ../../alloc.rst:76
+#: ../../alloc.rst:222
+# e5dd1566033a4a7cbdbe5e874416dbac
+# 6e2d9db891cc4a9e9840ceb384aaa5f0
+msgid "DeploymentPlan should specify:"
+msgstr ""
+
+#: ../../alloc.rst:78
+#: ../../alloc.rst:224
+# 7516a5bc7a9a4162a650275c5cd52a60
+# 7bcc7157b86045ebb6ecb62127995eeb
+msgid "dataCenterId: The data center the VM should deploy in"
+msgstr ""
+
+#: ../../alloc.rst:80
+# 9acd60a116b94beea25811ec07007a22
+msgid "podId: The pod the Vm should deploy in; null if no preference"
+msgstr ""
+
+#: ../../alloc.rst:82
+#: ../../alloc.rst:228
+# 81ba4443812c44e7ae390dde322cd2f0
+# f8ef1a4988214cbd84faa3bd3c7bb4d8
+msgid "clusterId: The cluster the VM should deploy in; null if no preference"
+msgstr ""
+
+#: ../../alloc.rst:84
+#: ../../alloc.rst:230
+# 1e9ad629bf7546baa1ef733ff7649794
+# 7d31ebe319f04eae8fc914f0d9b15dfd
+msgid "poolId: The storage pool the VM should be created in; null if no preference"
+msgstr ""
+
+#: ../../alloc.rst:87
+# a56db2027fc14fe8851adbb0d20f4bb3
+msgid "*com.cloud.host.Host.Type type*"
+msgstr ""
+
+#: ../../alloc.rst:89
+# 117330d5149346e893940824a7cc0f13
+msgid "Type of the Host needed for this guest VM. Currently com.cloud.host.Host.Type interface defines the following Host types:"
+msgstr ""
+
+#: ../../alloc.rst:92
+# f4c862266e0748c3b82a54cc3cf4e11b
+msgid "Storage"
+msgstr ""
+
+#: ../../alloc.rst:94
+# 5e8cacd550d34cbf9f4a2331d9047508
+msgid "Routing"
+msgstr ""
+
+#: ../../alloc.rst:96
+# c2c7fa103b0d42d9a048b9ba94539d7e
+msgid "SecondaryStorage"
+msgstr ""
+
+#: ../../alloc.rst:98
+# 7039d6864f4641c88b963761815441d9
+msgid "ConsoleProxy"
+msgstr ""
+
+#: ../../alloc.rst:100
+# 188966fdb5ea4866b645a73c1f46203e
+msgid "ExternalFirewall"
+msgstr ""
+
+#: ../../alloc.rst:102
+# 886ce574c22f470b86d2e2dabc4dedf8
+msgid "ExternalLoadBalancer"
+msgstr ""
+
+#: ../../alloc.rst:104
+#: ../../alloc.rst:233
+# 98d8618b11f4418394a49756ee34f0d1
+# 73004922ca734363a23b1828058ada96
+msgid "*com.cloud.deploy.DeploymentPlanner.ExcludeList avoid*"
+msgstr ""
+
+#: ../../alloc.rst:106
+# 3e92b2a746b94fe28d77bcf0dc7cd07d
+msgid "The ExcludeList specifies what datacenters, pods, clusters, hosts, storagePools should not be considered for allocating this guest VM. HostAllocators should avoid the hosts that are mentioned in ExcludeList.hostIds."
+msgstr ""
+
+#: ../../alloc.rst:111
+#: ../../alloc.rst:240
+# 448bc6d6adae4fdcb730025e56873627
+# 40756f9187a944b2b7d94c9d1382494f
+msgid "Set Long dcIds;"
+msgstr ""
+
+#: ../../alloc.rst:113
+#: ../../alloc.rst:242
+# d2504f426a0049d0ace9b214c6bd7953
+# 6140ffc617dc4a2985bfb74a278d41b9
+msgid "Set Long podIds;"
+msgstr ""
+
+#: ../../alloc.rst:115
+#: ../../alloc.rst:244
+# 8aa146a476c7463595b14b96873a20e3
+# 86deaf0d209249dfa759b338c46ac0be
+msgid "Set Long clusterIds;"
+msgstr ""
+
+#: ../../alloc.rst:117
+#: ../../alloc.rst:246
+# 9fdc441f089941d5943c1136f1b86e2a
+# 610a66aed6e64b46be125b1294931664
+msgid "Set Long hostIds;"
+msgstr ""
+
+#: ../../alloc.rst:119
+#: ../../alloc.rst:248
+# b5399df37cd7423883f64b670d07cf47
+# ebe7497409b8407a9fee2cd3565ba6db
+msgid "Set Long poolIds;"
+msgstr ""
+
+#: ../../alloc.rst:121
+#: ../../alloc.rst:250
+# 4d44cc93626b4131bb652953a2560628
+# ea297796ac634038b897f044d98d9bad
+msgid "*int returnUpTo*"
+msgstr ""
+
+#: ../../alloc.rst:123
+# 4afa7f5bef3c4ae583c38ffb62a765f9
+msgid "This specifies return up to that many available hosts for this guest VM."
+msgstr ""
+
+#: ../../alloc.rst:125
+# eab39d31cb4247efb1538ccb5bf6c7ba
+msgid "To get all possible hosts, set this value to -1."
+msgstr ""
+
+#: ../../alloc.rst:128
+# 3224e4b69b424d29ba834cc170599b1e
+msgid "Reference HostAllocator implementation"
+msgstr ""
+
+#: ../../alloc.rst:130
+# 44a1d6e9f79d426b9d3fc47dac17f086
+msgid "Refer com.cloud.agent.manager.allocator.impl.FirstFitAllocator that implements the HostAllocator interface. This allocator checks available hosts in the specified datacenter, Pod, Cluster and considering the given ServiceOffering requirements."
+msgstr ""
+
+#: ../../alloc.rst:135
+# 5562696f2a6e4158b2317f8674a65764
+msgid "If returnUpTo = 1, this allocator would return the first Host that fits the requirements of the guest VM."
+msgstr ""
+
+#: ../../alloc.rst:139
+# 354cd895a9f1419f951f2d2dbb480147
+msgid "Loading a custom HostAllocator"
+msgstr ""
+
+#: ../../alloc.rst:141
+# 54e588e1b5a242c79a961cf83b931c9a
+msgid "Write a custom HostAllocator class, implementing the interface described above."
+msgstr ""
+
+#: ../../alloc.rst:144
+#: ../../alloc.rst:273
+# f9c0a0a8e19b463ead48dd0f181efe00
+# 25506beab7514a94b9a14938e4a568bf
+msgid "Package the code into a JAR file and make the JAR available in the classpath of the Management Server/tomcat."
+msgstr ""
+
+#: ../../alloc.rst:147
+#: ../../alloc.rst:276
+# 4af2d8a69dee48cd8a7c3ccfbac5631c
+# 928c5259176f4c829c12d2c3e07b307b
+msgid "Modify the components.xml and components-premium.xml files found in /client/ tomcatconf as follows."
+msgstr ""
+
+#: ../../alloc.rst:150
+# 840bb1bb0bab49d3a0ac320ed3041f64
+msgid "Search for ‘HostAllocator’ in these files."
+msgstr ""
+
+#: ../../alloc.rst:159
+# c835db1603ac49fbadd6d4e7d60dbad8
+msgid "Replace the FirstFitAllocator with your class name. Optionally, you can change the name of the adapter as well."
+msgstr ""
+
+#: ../../alloc.rst:162
+#: ../../alloc.rst:290
+# 85c3d7ba304941cfa509a7b52f2bd205
+# f95ca1d23efe456ab39d2e725a2036a0
+msgid "Restart the Management Server."
+msgstr ""
+
+#: ../../alloc.rst:165
+# 15bff855293d4273b95a3b617b5df378
+msgid "Implementing a custom StoragePoolAllocator"
+msgstr ""
+
+#: ../../alloc.rst:167
+# 73bf3330eb4f417ab2560cc855d3cc6d
+msgid "StoragePoolAllocators are written by extending com.cloud.storage.allocator. StoragePoolAllocator interface."
+msgstr ""
+
+#: ../../alloc.rst:171
+# a94ec7aeb9984f75b53356320e64d512
+msgid "StoragePoolAllocator Interface"
+msgstr ""
+
+#: ../../alloc.rst:173
+# 95dffe7e76f944b09ba93c62a7e293f1
+msgid "A custom StoragePoolAllocator can be written by implementing the ‘allocateTo’ method."
+msgstr ""
+
+#: ../../alloc.rst:191
+# 5d8387e6a7894494aeca6ddeb48b53ff
+msgid "This interface also contains some other methods to support some legacy code. However your custom allocator can extend the existing com.cloud.storage.allocator. AbstractStoragePoolAllocator. This class provides default implementation for all the other interface methods."
+msgstr ""
+
+#: ../../alloc.rst:197
+# 34b5c706a80b43819ad96e48f36ec5d4
+msgid "Input Parameters for the method ‘StoragePoolAllocator :: allocateTo’"
+msgstr ""
+
+#: ../../alloc.rst:199
+# b3487e08c96843719a022eb9c673d711
+msgid "*com.cloud.vm.DiskProfile dskCh*"
+msgstr ""
+
+#: ../../alloc.rst:201
+# aba86c4ec9ec4269b17b4b00cfe428a6
+msgid "DiskCharacteristics describes a disk and what functionality is required from it. It specifies the storage pool tags if any to be used while searching for a storage pool."
+msgstr ""
+
+#: ../../alloc.rst:212
+# e09f9104505143559febc21f3b4a8d3b
+msgid "StoragePoolAllocators can make use of the following information present in the VirtualMachineProfile:"
+msgstr ""
+
+#: ../../alloc.rst:215
+# 456e11be56f04f1a8fe2f16c00df57f8
+msgid "The VirtualMachine instance that specifies properties of the guest VM."
+msgstr ""
+
+#: ../../alloc.rst:226
+# 76cafb6cdcd649f78d4f82df21085297
+msgid "podId: The pod the VM should deploy in; null if no preference"
+msgstr ""
+
+#: ../../alloc.rst:235
+# 7c73dbba2b6440949b2b97677bb271cc
+msgid "The ExcludeList specifies what datacenters, pods, clusters, hosts, storagePools should not be considered for allocating this guest VM. StoragePoolAllocators should avoid the pools that are mentioned in ExcludeList.poolIds"
+msgstr ""
+
+#: ../../alloc.rst:252
+# 21093c1b8fb642689c24b0232e85c441
+msgid "This specifies return up to that many available pools for this guest VM"
+msgstr ""
+
+#: ../../alloc.rst:254
+# 12487cb7610942068f5cec67e00e73dd
+msgid "To get all possible pools, set this value to -1"
+msgstr ""
+
+#: ../../alloc.rst:257
+# 88ed7f8e81914e3681b4391f15d60939
+msgid "Reference StoragePoolAllocator implementation"
+msgstr ""
+
+#: ../../alloc.rst:259
+# 3808521ba2eb425db2239e0fe1d0789b
+msgid "Refer com.cloud.storage.allocator.FirstFitStoragePoolAllocator that implements the StoragePoolAllocator interface. This allocator checks available pools in the specified datacenter, Pod, Cluster and considering the given DiskProfile characteristics."
+msgstr ""
+
+#: ../../alloc.rst:264
+# f50dfc1dbce44eddbe27be2f26df3ac7
+msgid "If returnUpTo = 1, this allocator would return the first Storage Pool that fits the requirements of the guest VM."
+msgstr ""
+
+#: ../../alloc.rst:268
+# 9c246f19fb0f49918c77cf5f2b5d6119
+msgid "Loading a custom StoragePoolAllocator"
+msgstr ""
+
+#: ../../alloc.rst:270
+# 5fc036623a834bd792b5e222c530c9fb
+msgid "Write a custom StoragePoolAllocator class, implementing the interface described above."
+msgstr ""
+
+#: ../../alloc.rst:279
+# f74bddd68a3b40169de9e67da02f8edc
+msgid "Search for ‘StoragePoolAllocator’ in these files."
+msgstr ""
+
+#: ../../alloc.rst:287
+# 33990be5d35e4bcb83bf38a712d31e58
+msgid "Replace the FirstFitStoragePoolAllocator with your class name. Optionally, you can change the name of the adapter as well."
+msgstr ""
+
diff --git a/source/conceptsandterminology/locale/pot/ansible.pot b/source/conceptsandterminology/locale/pot/ansible.pot
new file mode 100644
index 0000000..0ea3a7e
--- /dev/null
+++ b/source/conceptsandterminology/locale/pot/ansible.pot
@@ -0,0 +1,383 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../ansible.rst:2
+# 1859d2f68f21412b8db2824edfae907f
+msgid "Deploying CloudStack with Ansible"
+msgstr ""
+
+#: ../../ansible.rst:4
+# 6e30eb00e6aa452eb537f0340f2f7556
+msgid "In this article, `Paul Angus <https://twitter.com/CloudyAngus>`__ Cloud Architect at ShapeBlue takes a look at using Ansible to Deploy an Apache CloudStack cloud."
+msgstr ""
+
+#: ../../ansible.rst:9
+# 17351fc3621b4e56afb679f57b7eb2fc
+msgid "What is Ansible"
+msgstr ""
+
+#: ../../ansible.rst:11
+# e0cbed0b5b6f4f81ac4a47ef3b9fcbec
+msgid "Ansible is a deployment and configuration management tool similar in intent to Chef and Puppet. It allows (usually) DevOps teams to orchestrate the deployment and configuration of their environments without having to re-write custom scripts to make changes."
+msgstr ""
+
+#: ../../ansible.rst:16
+# 9ac502daf71441a5add7f1779cb19b62
+msgid "Like Chef and Puppet, Ansible is designed to be idempotent, these means that you determine the state you want a host to be in and Ansible will decide if it needs to act in order to achieve that state."
+msgstr ""
+
+#: ../../ansible.rst:21
+# 91a4a9ec711e4564a704919e51ad288a
+msgid "There’s already Chef and Puppet, so what’s the fuss about Ansible?"
+msgstr ""
+
+#: ../../ansible.rst:23
+# 85246b43e8e4405b97abc46c4c48ad1c
+msgid "Let’s take it as a given that configuration management makes life much easier (and is quite cool), Ansible only needs an SSH connection to the hosts that you’re going to manage to get started. While Ansible requires Python 2.4 or greater to on the host you’re going to manage in order to leverage the vast majority of its functionality, it is able to connect to hosts which don’t have Python installed in order to then install Python, so it’s not really a problem. This greatly simplifies the deployment procedure for hosts, avoiding the need to pre-install agents onto the clients before the configuration management can take over."
+msgstr ""
+
+#: ../../ansible.rst:33
+# f9c8d470e48a46a3bf54200afc699d6d
+msgid "Ansible will allow you to connect as any user to a managed host (with that user’s privileges) or by using public/private keys – allowing fully automated management."
+msgstr ""
+
+#: ../../ansible.rst:37
+# e4cd5c2b100b42f287d4ff22be7e0154
+msgid "There also doesn’t need to be a central server to run everything, as long as your playbooks and inventories are in-sync you can create as many Ansible servers as you need (generally a bit of Git pushing and pulling will do the trick)."
+msgstr ""
+
+#: ../../ansible.rst:42
+# e0edcb5a78fb43e69bef735a58ee8659
+msgid "Finally – its structure and language is pretty simple and clean. I’ve found it a bit tricky to get the syntax correct for variables in some circumstances, but otherwise I’ve found it one of the easier tools to get my head around."
+msgstr ""
+
+#: ../../ansible.rst:48
+# f7e6bae4e21c4e209fc35954999298f2
+msgid "So let’s see something"
+msgstr ""
+
+#: ../../ansible.rst:50
+# 8ab9c7fec0dc4be49ad4e125357f4d7a
+msgid "For this example we’re going to create an Ansible server which will then deploy a CloudStack server. Both of these servers will be CentOS 6.4 virtual machines."
+msgstr ""
+
+#: ../../ansible.rst:55
+# 5f0e94b7659b4d409b333b789158e84e
+msgid "Installing Ansible"
+msgstr ""
+
+#: ../../ansible.rst:57
+# 915043a5d8904bb7aa64f2dde8a92391
+msgid "Installing Ansible is blessedly easy. We generally prefer to use CentOS so to install Ansible you run the following commands on the Ansible server."
+msgstr ""
+
+#: ../../ansible.rst:66
+# 36f217057d324ed58620a8813c3eabef
+msgid "And that’s it."
+msgstr ""
+
+#: ../../ansible.rst:68
+# cf61954055d44444975ccf8a7a78a916
+msgid "*(There is a commercial version which has more features such as callback to request configurations and a RESTful API and also support. The installation of this is different)*"
+msgstr ""
+
+#: ../../ansible.rst:72
+# 9363f0968af64b6aa46bb5905cf4251a
+msgid "By default Ansible uses /etc/ansible to store your playbooks, I tend to move it, but there’s no real problem with using the default location. Create yourself a little directory structure to get started with. The documentation recommends something like this:"
+msgstr ""
+
+#: ../../ansible.rst:79
+# 9868b1e2ebd24ceab9858c7787e9ccba
+msgid "Playbooks"
+msgstr ""
+
+#: ../../ansible.rst:81
+# 0d8e95c78ba84d22bf1b0ee3038508ea
+msgid "Ansible uses playbooks to specify the state in which you wish the target host to be in to be able to accomplish its role. Ansible playbooks are written in YAML format."
+msgstr ""
+
+#: ../../ansible.rst:86
+# a1f7c79f3f724cdba81c303040553b5e
+msgid "Modules"
+msgstr ""
+
+#: ../../ansible.rst:88
+# 564296611bdb46e6a8bd0a38db4b8e01
+msgid "To get Ansible to do things you specify the hosts a playbook will act upon and then call modules and supply arguments which determine what Ansible will do to those hosts."
+msgstr ""
+
+#: ../../ansible.rst:92
+# ebb846fa6db14f94b4b7a4cc98607749
+msgid "To keep things simple, this example is a cut-down version of a full deployment. This example creates a single management server with a local MySQL server and assumes you have your secondary storage already provisioned somewhere. For this example I’m also not going to include securing the MySQL server, configuring NTP or using Ansible to configure the networking on the hosts either. Although normally we’d use Ansible to do exactly that."
+msgstr ""
+
+#: ../../ansible.rst:100
+# d040b1b00b08437fafc87fa3320b0e4a
+msgid "The pre-requisites to this CloudStack build are:"
+msgstr ""
+
+#: ../../ansible.rst:102
+# cce9101b609045a2b3f394516d45093e
+msgid "A CentOS 6.4 host to install CloudStack on"
+msgstr ""
+
+#: ../../ansible.rst:103
+# e207a3f7f037488ea1b6328c91e33806
+msgid "An IP address already assigned on the ACS management host"
+msgstr ""
+
+#: ../../ansible.rst:104
+# fe440835a2a74cf48eb7c18ea908839e
+msgid "The ACS management host should have a resolvable FQDN (either through DNS or the host file on the ACS management host)"
+msgstr ""
+
+#: ../../ansible.rst:106
+# 41450f1731f14a729024313ec6a710fe
+msgid "Internet connectivity on the ACS management host"
+msgstr ""
+
+#: ../../ansible.rst:109
+# b5ddaceb1e764f74b2813ea96969445c
+msgid "Planning"
+msgstr ""
+
+#: ../../ansible.rst:111
+# 013969c7e2b9492db82e2d33164297c4
+msgid "The first step I use is to list all of the tasks I think I’ll need and group them or split them into logical blocks. So for this deployment of CloudStack I’d start with:"
+msgstr ""
+
+#: ../../ansible.rst:115
+# dd9e1395ccef429988e3e88376d858e7
+msgid "Configure selinux"
+msgstr ""
+
+#: ../../ansible.rst:116
+# 99b8406503ab4f12aae62a87d020722b
+msgid "(libselinux-python required for Ansible to work with selinux enabled hosts)"
+msgstr ""
+
+#: ../../ansible.rst:118
+# db945f8d47d0492a9162d0b8c17b048c
+msgid "Install and configure MySQL"
+msgstr ""
+
+#: ../../ansible.rst:119
+# d53d2720f9634906b3db980400d04d91
+msgid "(Python MySQL-DB required for Ansible MySQL module)"
+msgstr ""
+
+#: ../../ansible.rst:120
+# 7d22acf5b782426c8bcf68228188559b
+msgid "Install cloud-client"
+msgstr ""
+
+#: ../../ansible.rst:121
+# e2bcdc7a20274f28a27eec8996498c23
+msgid "Seed secondary storage"
+msgstr ""
+
+#: ../../ansible.rst:123
+# be33c86aba4945c585fce7c88942d496
+msgid "Ansible is built around the idea of hosts having roles, so generally you would group or manage your hosts by their roles. So now to create some roles for these tasks"
+msgstr ""
+
+#: ../../ansible.rst:127
+# e13ff16771754ed485d9e2c92d16debc
+msgid "I’ve created:"
+msgstr ""
+
+#: ../../ansible.rst:129
+# 7935027693af496e861255a6bc772036
+msgid "cloudstack-manager"
+msgstr ""
+
+#: ../../ansible.rst:130
+# 99590b1bc4024a08b0c0f182dbc60ef8
+msgid "mysql"
+msgstr ""
+
+#: ../../ansible.rst:132
+# a18f24daf8924855a44a9d0e633c94fc
+msgid "First up we need to tell Ansible where to find our CloudStack management host. In the root Ansible directory there is a file called ‘hosts’ (/etc/Ansible/hosts) add a section like this:"
+msgstr ""
+
+#: ../../ansible.rst:141
+# 7b170fd6a43342619530fb0aeee059d2
+msgid "where xxx.xxx.xxx.xxx is the ip address of your ACS management host."
+msgstr ""
+
+#: ../../ansible.rst:144
+# 144ffdd76bc148f39f790ada64cd4fc0
+msgid "MySQL"
+msgstr ""
+
+#: ../../ansible.rst:146
+# d7a41e7d8b9744e385f2a53ad29f8fdd
+msgid "So let’s start with the MySQL server. We’ll need to create a task within the mysql role directory called main.yml. The ‘task’ in this case to have MySQL running and configured on the target host. The contents of the file will look like this:"
+msgstr ""
+
+#: ../../ansible.rst:207
+# 26122051675049278058cecdb173238d
+msgid "This needs to be saved as `/etc/ansible/roles/mysql/tasks/main.yml`"
+msgstr ""
+
+#: ../../ansible.rst:209
+# b896847dc3d748e6813c7bad10be7b4b
+msgid "As explained earlier, this playbook in fact describes the state of the host rather than setting out commands to be run. For instance, we specify certain lines which must be in the my.cnf file and allow Ansible to decide whether or not it needs to add them."
+msgstr ""
+
+#: ../../ansible.rst:214
+# 09f9988a7cc441068987429418680739
+msgid "Most of the modules are self-explanatory once you see them, but to run through them briefly;"
+msgstr ""
+
+#: ../../ansible.rst:217
+# 5c1e4a497ed64e27ace8c66aa718abf8
+msgid "The ‘yum’ module is used to specify which packages are required, the ‘service’ module controls the running of services, while the ‘mysql\\_user’ module controls mysql user configuration. The ‘lineinfile’ module controls the contents in a file."
+msgstr ""
+
+#: ../../ansible.rst:222
+# f9b01f4c803e4686b8176db909562c4b
+msgid "We have a couple of variables which need declaring. You could do that within this playbook or its ‘parent’ playbook, or as a higher level variable. I’m going to declare them in a higher level playbook. More on this later."
+msgstr ""
+
+#: ../../ansible.rst:227
+# b129bd6c3c1f4252acbf6e3ab39da0d8
+msgid "That’s enough to provision a MySQL server. Now for the management server."
+msgstr ""
+
+#: ../../ansible.rst:232
+# e2a69788c8914660a4e7ec5a1da788fc
+msgid "CloudStack Management server service"
+msgstr ""
+
+#: ../../ansible.rst:234
+# f86e9d9aed5f4b688eeab2232617abf4
+msgid "For the management server role we create a main.yml task like this:"
+msgstr ""
+
+#: ../../ansible.rst:268
+# 374da105e3c441a993c731bb823d37ef
+msgid "Save this as `/etc/ansible/roles/cloudstack-management/tasks/main.yml`"
+msgstr ""
+
+#: ../../ansible.rst:270
+# 81313977c7c34c23b2bee532e64d64b8
+msgid "Now we have some new elements to deal with. The Ansible template module uses Jinja2 based templating. As we’re doing a simplified example here, the Jinja template for the cloudstack.repo won’t have any variables in it, so it would simply look like this:"
+msgstr ""
+
+#: ../../ansible.rst:283
+# 780fbe6357154bcf831d03abbffa1a0c
+msgid "This is saved in `/etc/ansible/roles/cloudstack-manager/templates/cloudstack.repo.j2`"
+msgstr ""
+
+#: ../../ansible.rst:285
+# 0e150c1a3bd147d783217e662e64a456
+msgid "That gives us the packages installed, we need to set up the database. To do this I’ve created a separate task called setupdb.yml"
+msgstr ""
+
+#: ../../ansible.rst:297
+# f140c48ee40e495bbf6e4f00451188a7
+msgid "Save this as: `/etc/ansible/roles/cloudstack-management/tasks/setupdb.yml`"
+msgstr ""
+
+#: ../../ansible.rst:299
+# ab0ad808c1b74a0da1d3701114d7d265
+msgid "As there isn’t (as yet) a CloudStack module, Ansible doesn’t inherently know whether or not the databases have already been provisioned, therefore this step is not currently idempotent and will overwrite any previously provisioned databases."
+msgstr ""
+
+#: ../../ansible.rst:304
+# 61bbd93955ed4ef680b0005e6fe4c4db
+msgid "There are some more variables here for us to declare later."
+msgstr ""
+
+#: ../../ansible.rst:308
+# 907d082c8f834643a0a0d47f85ed7853
+msgid "System VM Templates:"
+msgstr ""
+
+#: ../../ansible.rst:311
+# 892ba69b5c9e4077b755762af5b353c0
+msgid "Finally we would want to seed the system VM templates into the secondary storage. The playbook for this would look as follows:"
+msgstr ""
+
+#: ../../ansible.rst:335
+# 245722e5625e41b3be3d67384dbd309b
+msgid "Save this as `/etc/ansible/roles/cloudstack-manager/tasks/seedstorage.yml`"
+msgstr ""
+
+#: ../../ansible.rst:337
+# b224369b3afb4d0ab4107842e7794d39
+msgid "Again, there isn’t a CloudStack module so Ansible will always run this even if the secondary storage already has the templates in it."
+msgstr ""
+
+#: ../../ansible.rst:342
+# 5ebfbb97903b40ba85dc1668a1618296
+msgid "Bringing it all together"
+msgstr ""
+
+#: ../../ansible.rst:344
+# c265f43e11a743239b94833df8f80ba4
+msgid "Ansible can use playbooks which run other playbooks, this allows us to group these playbooks together and declare variables across all of the individual playbooks. So in the Ansible playbook directory create a file called deploy-cloudstack.yml, which would look like this:"
+msgstr ""
+
+#: ../../ansible.rst:373
+# 5451f71073da4c428c19974c633cda87
+msgid "Save this as `/etc/ansible/deploy-cloudstack.yml` inserting the IP address and path for your secondary storage and changing the passwords if you wish to."
+msgstr ""
+
+#: ../../ansible.rst:379
+# 51f57532edfe47a3bf340a6ef3ec8005
+msgid "To run this go to the Ansible directory (cd /etc/ansible ) and run:"
+msgstr ""
+
+#: ../../ansible.rst:385
+# 7f15fe37a51a461ebd1554bd3b9b606c
+msgid "‘-k’ tells Ansible to ask you for the root password to connect to the remote host."
+msgstr ""
+
+#: ../../ansible.rst:388
+# 0eb541457f53444395a4f37fcf63cbea
+msgid "Now log in to the CloudStack UI on the new management server."
+msgstr ""
+
+#: ../../ansible.rst:393
+# 7adf17b4cc68467c9cbc81ee862c3753
+msgid "How is this example different from a production deployment?"
+msgstr ""
+
+#: ../../ansible.rst:395
+# 55f1b360102642c992d5a63319701117
+msgid "In a production deployment, the Ansible playbooks would configure multiple management servers connected to master/slave replicating MySQL databases along with any other infrastructure components required and deploy and configure the hypervisor hosts. We would also have a dedicated file describing the hosts in the environment and a dedicated file containing variables which describe the environment."
+msgstr ""
+
+#: ../../ansible.rst:402
+# 9767e9a1a97c49f99bdbb781b67a14b4
+msgid "The advantage of using a configuration management tool such as Ansible is that we can specify components like the MySQL database VIP once and use it multiple times when configuring the MySQL server itself and other components which need to use that information."
+msgstr ""
+
+#: ../../ansible.rst:409
+# 95500bea3a42402b9097acfd1246c320
+msgid "Acknowledgements"
+msgstr ""
+
+#: ../../ansible.rst:411
+# b26a941e90e445beab8646793a36fe57
+msgid "Thanks to Shanker Balan for introducing me to Ansible and a load of handy hints along the way."
+msgstr ""
+
diff --git a/source/conceptsandterminology/locale/pot/concepts.pot b/source/conceptsandterminology/locale/pot/concepts.pot
new file mode 100644
index 0000000..de31e09
--- /dev/null
+++ b/source/conceptsandterminology/locale/pot/concepts.pot
@@ -0,0 +1,1181 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../concepts.rst:17
+# ff38df278b6b427bbcc0ae8629300425
+msgid "Concepts and Terminology"
+msgstr ""
+
+#: ../../concepts.rst:20
+# 987b7e9834864335a292b23b7606342e
+msgid "What is Apache CloudStack?"
+msgstr ""
+
+#: ../../concepts.rst:22
+# 6a80177e5b404ca29f3615856b3d4a04
+msgid "Apache CloudStack is an open source Infrastructure-as-a-Service platform that manages and orchestrates pools of storage, network, and computer resources to build a public or private IaaS compute cloud."
+msgstr ""
+
+#: ../../concepts.rst:26
+# cd99442cc2de4607a6e68ee786158ed2
+msgid "With CloudStack you can:"
+msgstr ""
+
+#: ../../concepts.rst:28
+# 5f469cd298a84339b85ef95dc9ecd9f0
+msgid "Set up an on-demand elastic cloud computing service."
+msgstr ""
+
+#: ../../concepts.rst:29
+# f049916f533a4760aab64b754de21b0c
+msgid "Allow end-users to provision resources"
+msgstr ""
+
+#: ../../concepts.rst:32
+# e5df4fdaa57241ba861ec065ad290a8a
+msgid "What can Apache CloudStack do?"
+msgstr ""
+
+#: ../../concepts.rst:35
+# b32ee3c0a8b04a219624f36f45a80294
+msgid "Multiple Hypervisor Support"
+msgstr ""
+
+#: ../../concepts.rst:37
+# b2e92c0efc86485ea0a439a293873fc4
+msgid "CloudStack works with a variety of hypervisors and hypervisor-like technologies. A single cloud can contain multiple hypervisor implementations. As of the current release CloudStack supports:"
+msgstr ""
+
+#: ../../concepts.rst:41
+# 9a8cf08e323f44ca8d021cfeab657895
+msgid "vSphere (via vCenter)"
+msgstr ""
+
+#: ../../concepts.rst:42
+# 3d49790c67b943a69aa298d7269a1182
+msgid "KVM"
+msgstr ""
+
+#: ../../concepts.rst:43
+# 181151d4c9b74cf59ab1e9107275c932
+msgid "Xenserver"
+msgstr ""
+
+#: ../../concepts.rst:44
+# b556e16fe3ae461db6af3d65b7a1f610
+msgid "LXC"
+msgstr ""
+
+#: ../../concepts.rst:45
+# 79e7d36bd64245359e12a587e6274d52
+msgid "BareMetal (via IPMI)"
+msgstr ""
+
+#: ../../concepts.rst:48
+# 3182482cabe247af9482c3762fef3017
+msgid "Massively Scalable Infrastructure Management"
+msgstr ""
+
+#: ../../concepts.rst:50
+# 589db3182dac49e398ea50a422f61063
+msgid "CloudStack can manage tens of thousands of physical servers installed in geographically distributed datacenters. The management server scales near-linearly eliminating the need for cluster-level management servers. Maintenance or other outages of the management server can occur without affecting the virtual machines running in the cloud."
+msgstr ""
+
+#: ../../concepts.rst:56
+# f36ad8bee3e44cc2a4452cc4d88c412d
+msgid "Automatic Cloud Configuration Management"
+msgstr ""
+
+#: ../../concepts.rst:58
+# 954df973e0c04df59010d279b937d870
+msgid "CloudStack automatically configures the network and storage settings for each virtual machine deployment. Internally, a pool of virtual appliances support the operation of configuration of the cloud itself. These appliances offer services such as firewalling, routing, DHCP, VPN, console proxy, storage acces, and storage replication. The extensive use of horizontally scalable virtual machines simplifies the installation and ongoing operation of a cloud."
+msgstr ""
+
+#: ../../concepts.rst:65
+# 9b74733aa28741a7b6964e1807a72a8d
+msgid "Graphical User Interface"
+msgstr ""
+
+#: ../../concepts.rst:67
+# b55d7ad93d7f43c0a0654409b017e085
+msgid "CloudStack offers an administrators web interface used for provisioning and managing the cloud, as well as an end-user's Web interface, used for running VMs and managing VM templates. The UI can be customized to reflect the desired service provider or enterprise look and feel."
+msgstr ""
+
+#: ../../concepts.rst:72
+# 13e4ba5fb045431c96bd6a6bfb9b0c47
+msgid "API"
+msgstr ""
+
+#: ../../concepts.rst:74
+# 4cca4c0057904d119293daf854c492f9
+msgid "CloudStack provides a REST-like API for the operation, management and use of the cloud."
+msgstr ""
+
+#: ../../concepts.rst:77
+# 907642e40be7483abe15bd11b1d0d2bd
+msgid "AWS EC2 API Support"
+msgstr ""
+
+#: ../../concepts.rst:79
+# b4859925ffba4cb7bcb78e512b2e12f2
+msgid "CloudStack provides an EC2 API translation layer to permit the common EC2 tools to be used in the use of a CloudStack cloud."
+msgstr ""
+
+#: ../../concepts.rst:83
+# 9ca0dfd02bab44a5b2876118360bdec5
+msgid "High Availability"
+msgstr ""
+
+#: ../../concepts.rst:85
+# abc3111162074f78a5f125d52fbd39ed
+msgid "CloudStack has a number of features to increase the availability of the system. The Management Server itself may be deployed in a multi-node installation where the servers are load balanced. MySQL may be configured to use replication to provide for failover in the event of database loss. For the hosts, CloudStack supports NIC bonding and the use of separate networks for storage as well as iSCSI Multipath."
+msgstr ""
+
+#: ../../concepts.rst:91
+# 65f38b6a98244d4792c02eeccaa2d263
+msgid "Deployment Architecture Overview"
+msgstr ""
+
+#: ../../concepts.rst:93
+# f7691551cecf4795845273b7644abc9c
+msgid "Generally speaking, most CloudStack deployments consist of the management server and the resources to be managed. During deployment you inform the management server of the resources to be managed, such as IP address blocks, storage devices, hypervisors, and VLANs."
+msgstr ""
+
+#: ../../concepts.rst:97
+# 387390681232476cbc3cb6d9a688e686
+msgid "The minimum installation consists of one machine running the CloudStack Management Server and another machine to act as the cloud infrastructure (in this case, a very simple infrastructure consisting of one host running hypervisor software). In its smallest deployment, a single machine can act as both the Management Server and the hypervisor host (using the KVM hypervisor)."
+msgstr ""
+
+#: ../../concepts.rst:104
+# 10ca735f9c5c46fca39647ac1347679d
+msgid "A more full-featured installation consists of a highly-available multi-node Management Server installation and up to tens of thousands of hosts using any of severa networking technologies."
+msgstr ""
+
+#: ../../concepts.rst:108
+# b8652ea0066c4053b12682ffc7f30bef
+msgid "Management Server Overview"
+msgstr ""
+
+#: ../../concepts.rst:110
+# 240ebb34afe94a58a48015d44079f040
+msgid "The management server orchestrates and allocates the resources in your cloud deployment."
+msgstr ""
+
+#: ../../concepts.rst:112
+# 2f94d5a92bab47fdb3859bebfb9afbdc
+msgid "The management server typically runs on a dedicated machine or as a virtual machine. It controls allocation of virtual machines to hosts and assigns storage and IP addresses to the virtual machine instances. The Management Server runs in an Apache Tomcat container and requires a MySQL database for persistence."
+msgstr ""
+
+#: ../../concepts.rst:116
+# 8d0f35882eb24bc5a9c08c78e5602f5c
+msgid "The management server:"
+msgstr ""
+
+#: ../../concepts.rst:118
+# 4652f2e494364fbcb4839028180aba00
+msgid "Provides the web interface for both the adminstrator and end user."
+msgstr ""
+
+#: ../../concepts.rst:119
+# 74adcdb7447943d1b1104f8eb37ea363
+msgid "Provides the API interfaces for both the CloudStack API as well as the EC2 interface."
+msgstr ""
+
+#: ../../concepts.rst:120
+# 6d0efeb2362f4c7ca1aada6c7440bfe0
+msgid "Manages the assignment of guest VMs to a specific compute resource"
+msgstr ""
+
+#: ../../concepts.rst:121
+# b03e3bd8fdf548c9944fc3cbe1bb9cf6
+msgid "Manages the assignment of public and private IP addresses."
+msgstr ""
+
+#: ../../concepts.rst:122
+# 6c8133776eff4190a0c969b1055aa3f9
+msgid "Allocates storage during the VM instantiation process."
+msgstr ""
+
+#: ../../concepts.rst:123
+# 11de99b9ee284066b17ec2fde6453b3d
+msgid "Manages snapshots, disk images (templates), and ISO images."
+msgstr ""
+
+#: ../../concepts.rst:124
+# 108fdcfb117d44c9b11484184f31c574
+msgid "Provides a single point of configuration for your cloud."
+msgstr ""
+
+#: ../../concepts.rst:127
+# 300f4224ac2c4a568eca39a7a357259c
+msgid "Cloud Infrastructure Overview"
+msgstr ""
+
+#: ../../concepts.rst:129
+# b091b998016d49d0ace3cdc25e5b6162
+msgid "Resources within the cloud are managed as follows:"
+msgstr ""
+
+#: ../../concepts.rst:131
+# 335c3f2f7ec1419e9cd654c116d3eb4d
+msgid "Regions: A collection of one or more geographically proximate zones managed by one or more management servers."
+msgstr ""
+
+#: ../../concepts.rst:132
+# 7a077b2a461042058ee95b2d8841bd4b
+msgid "Zones: Typically, a zone is equivalent to a single datacenter. A zone consists of one or more pods and secondary storage."
+msgstr ""
+
+#: ../../concepts.rst:133
+# 32477360a735403d9ca2bc7e91cd0a54
+msgid "Pods: A pod is usually a rack, or row of racks that includes a layer-2 switch and one or more clusters."
+msgstr ""
+
+#: ../../concepts.rst:134
+# d33af50f42ee45deb987f9d2ade53d3b
+msgid "Clusters: A cluster consists of one or more homogenous hosts and primary storage."
+msgstr ""
+
+#: ../../concepts.rst:135
+# 7e093aff5e3e4a00b8f88936620ba58f
+msgid "Host: A single compute node within a cluster; often a hypervisor."
+msgstr ""
+
+#: ../../concepts.rst:136
+# 2bf7c321a3654f468a29cb08b28a73ac
+msgid "Primary Storage: A storage resource typically provided to a single cluster for the actual running of instance disk images. (Zone-wide primary storage is an option, though not typically used.)"
+msgstr ""
+
+#: ../../concepts.rst:137
+# b06340fcd44f47b4a40c4938b7341f94
+msgid "Secondary Storage: A zone-wide resource which stores disk templates, ISO images, and snapshots."
+msgstr ""
+
+#: ../../concepts.rst:140
+# e9cf76fee1ec498689b0ff20dc126e6e
+msgid "Networking Overview"
+msgstr ""
+
+#: ../../concepts.rst:142
+# c467409211f94b9687be3a2b1bfad489
+msgid "CloudStack offers many types of networking, but they typically fall into one of two scenarios:"
+msgstr ""
+
+#: ../../concepts.rst:144
+# 0821d08ee93b4d2bb76708b03c48edbd
+msgid "Basic: Most analogous to AWS-classic style networking. Provides a single flat layer-2 network where guest isolation is provided at layer-3 by the hypervisors bridge device."
+msgstr ""
+
+#: ../../concepts.rst:145
+# f3617b6f83354f55b99b92296dde725e
+msgid "Advanced: This typically uses layer-2 isolation such as VLANs, though this category also includes SDN technologies such as Nicira NVP."
+msgstr ""
+
+#: ../../concepts.rst:148
+# 62d443310175475fb835841598392342
+msgid "Cloud Infrastructure Concepts"
+msgstr ""
+
+#: ../../concepts.rst:151
+# 59126a61842545aaa3d96c7df0083839
+msgid "Regions"
+msgstr ""
+
+#: ../../concepts.rst:153
+#: ../../concepts.rst:402
+# 8e46c2fc89f347aaa6f615b273af1310
+# 4ad01c974c564a24b124ceb41761b136
+msgid "To increase reliability of the cloud, you can optionally group resources into multiple geographic regions. A region is the largest available organizational unit within a CloudStack deployment. A region is made up of several availability zones, where each zone is roughly equivalent to a datacenter. Each region is controlled by its own cluster of Management Servers, running in one of the zones. The zones in a region are typically located in close geographical proximity. Regions are a useful technique for providing fault tolerance and disaster recovery."
+msgstr ""
+
+#: ../../concepts.rst:159
+#: ../../concepts.rst:411
+# f6701bba7648406e948b876a1ba58a27
+# 6058afa6bec24d22a3cbc7a92907bff2
+msgid "By grouping zones into regions, the cloud can achieve higher availability and scalability. User accounts can span regions, so that users can deploy VMs in multiple, widely-dispersed regions. Even if one of the regions becomes unavailable, the services are still available to the end-user through VMs deployed in another region. And by grouping communities of zones under their own nearby Management Servers, the latency of communications within the cloud is reduced compared to managing widely-dispersed zones from a single central Management Server."
+msgstr ""
+
+#: ../../concepts.rst:165
+#: ../../concepts.rst:420
+# c561a80250434a22aedb0c4c6a4cfca9
+# 9e21ac69dc3443a4941d601f7b41f710
+msgid "Usage records can also be consolidated and tracked at the region level, creating reports or invoices for each geographic region."
+msgstr ""
+
+#: ../../concepts.rst:169
+#: ../../concepts.rst:425
+# 5cea4050a14f4de3aeb38b46a59ecf7d
+# b2ff55bd20544ec8bd4e3c24e6fd70e5
+msgid "Regions are visible to the end user. When a user starts a guest VM on a particular CloudStack Management Server, the user is implicitly selecting that region for their guest. Users might also be required to copy their private templates to additional regions to enable creation of guest VMs using their templates in those regions."
+msgstr ""
+
+#: ../../concepts.rst:174
+# 627923ada10e4c1d9789a4f0e7f2ccda
+msgid "Zones"
+msgstr ""
+
+#: ../../concepts.rst:176
+#: ../../concepts.rst:434
+# befd4aa4b3dd4d3595caf74ccc51913d
+# 657a047026eb4fc5a89e6adc6a503ce5
+msgid "A zone is the second largest organizational unit within a CloudStack deployment. A zone typically corresponds to a single datacenter, although it is permissible to have multiple zones in a datacenter. The benefit of organizing infrastructure into zones is to provide physical isolation and redundancy. For example, each zone can have its own power supply and network uplink, and the zones can be widely separated geographically (though this is not required)."
+msgstr ""
+
+#: ../../concepts.rst:181
+#: ../../concepts.rst:442
+# 6ac4581b29d346ea80c2ca28ac1cc9f3
+# 34a3804509f94e56983cbab9a7da8f08
+msgid "A zone consists of:"
+msgstr ""
+
+#: ../../concepts.rst:183
+#: ../../concepts.rst:446
+# a2a93c49ced7443d83c7142de3b2a3c0
+# 77fe19c6a8914f919c7c7b4480fb997c
+msgid "One or more pods. Each pod contains one or more clusters of hosts and one or more primary storage servers."
+msgstr ""
+
+#: ../../concepts.rst:184
+#: ../../concepts.rst:451
+# 54cd3d09a9564596820af0c2f8b797bb
+# 93dac9bd873040cbada20aa49f354fcc
+msgid "A zone may contain one or more primary storage servers, which are shared by all the pods in the zone."
+msgstr ""
+
+#: ../../concepts.rst:185
+#: ../../concepts.rst:456
+# 8d1c7e07b86444689288ea82e3aa0030
+# 30a6aa1442b8422f8104af67f4b60826
+msgid "Secondary storage, which is shared by all the pods in the zone."
+msgstr ""
+
+#: ../../concepts.rst:189
+#: ../../concepts.rst:460
+# e909b5cd25384b6aa06daffc782174fb
+# de76395efb94465997ef2167d697a2d2
+msgid "Zones are visible to the end user. When a user starts a guest VM, the user must select a zone for their guest. Users might also be required to copy their private templates to additional zones to enable creation of guest VMs using their templates in those zones."
+msgstr ""
+
+#: ../../concepts.rst:193
+#: ../../concepts.rst:465
+# a9272fa6b4eb48c6ad285e9101107348
+# fa18323b0b154fbebcebfbb7bab34110
+msgid "Zones can be public or private. Public zones are visible to all users. This means that any user may create a guest in that zone. Private zones are reserved for a specific domain. Only users in that domain or its subdomains may create guests in that zone."
+msgstr ""
+
+#: ../../concepts.rst:197
+#: ../../concepts.rst:470
+# 4c4175c4e26e463d85b384047c1d8e3e
+# a0e4c6875a6c40768a31d50fc7abd630
+msgid "Hosts in the same zone are directly accessible to each other without having to go through a firewall. Hosts in different zones can access each other through statically configured VPN tunnels."
+msgstr ""
+
+#: ../../concepts.rst:200
+#: ../../concepts.rst:474
+# 95fe6ba9ef1b41e782dd2e013f9d2f50
+# b36589880a184eaf9d929db8343b3c07
+msgid "For each zone, the administrator must decide the following."
+msgstr ""
+
+#: ../../concepts.rst:202
+#: ../../concepts.rst:478
+# 42fc2b04eee74bc09c075228d211be72
+# befd465185ff45ffa60c9c045efec837
+msgid "How many pods to place in each zone."
+msgstr ""
+
+#: ../../concepts.rst:203
+#: ../../concepts.rst:482
+# 4dc60d42d89a49b4aaad76ad544427b1
+# 7c2885cf066c4472b4bf878e2b9df225
+msgid "How many clusters to place in each pod."
+msgstr ""
+
+#: ../../concepts.rst:204
+#: ../../concepts.rst:486
+# 65e4c970f3e84dd3a17cc9a4914851d8
+# 9aeacb01116544fdaffe228e91991884
+msgid "How many hosts to place in each cluster."
+msgstr ""
+
+#: ../../concepts.rst:205
+#: ../../concepts.rst:490
+# f1bc4eba9d894b9eb9cc2a80b5ddb82b
+# a25998f735d641f0a212c2a16614ef2f
+msgid "(Optional) How many primary storage servers to place in each zone and total capacity for these storage servers."
+msgstr ""
+
+#: ../../concepts.rst:206
+#: ../../concepts.rst:495
+# 4636b44eada0412e872b0aa5af561d30
+# b87141f2b24d4e11ac49523c0d11b5f1
+msgid "How many primary storage servers to place in each cluster and total capacity for these storage servers."
+msgstr ""
+
+#: ../../concepts.rst:207
+#: ../../concepts.rst:500
+# 1d0a58823e334c73bfc38780900b48f3
+# 6bd68b9edccd42059714a8901af3daac
+msgid "How much secondary storage to deploy in a zone."
+msgstr ""
+
+#: ../../concepts.rst:209
+#: ../../concepts.rst:506
+# e8eea81aa4f44f4ea7f4222b67b8c089
+# 6b6f3bde7fec42df8cb8a6dc2affde8d
+msgid "In order to support zone-wide functions for VMware, CloudStack is aware of VMware Datacenters and can map each Datacenter to a CloudStack zone. To enable features like storage live migration and zone-wide primary storage for VMware hosts, CloudStack has to make sure that a zone contains only a single VMware Datacenter. Therefore, when you are creating a new CloudStack zone, you can select a VMware Datacenter for the zone. If you are provisioning multiple VMware Datacenters, each one will be set up as a single zone in CloudStack."
+msgstr ""
+
+#: ../../concepts.rst:216
+# 173494bd553249c39dcf3a1c12004242
+msgid "Pods"
+msgstr ""
+
+#: ../../concepts.rst:218
+# 9e239f33815b400a9afc4ca6a60cd8b1
+msgid "A pod often represents a single rack or row of racks. Hosts in the same pod are in the same subnet. A pod is the second-largest organizational unit within a CloudStack deployment. Pods are contained within zones. Each zone can contain one or more pods. A pod consists of one or more clusters of hosts and one or more primary storage servers. Pods are not visible to the end user."
+msgstr ""
+
+#: ../../concepts.rst:226
+# 9d49a4c915274ae88d14c5470f3cfc23
+msgid "Clusters"
+msgstr ""
+
+#: ../../concepts.rst:228
+# f3bef6825da94521ac3bc7880437d870
+msgid "A cluster consists of one or more hosts and one or more primary storage resources."
+msgstr ""
+
+#: ../../concepts.rst:230
+# 186f42983c01472b9bdb24347e815860
+msgid "A cluster provides a way to group hosts. To be precise, a cluster is a XenServer server pool, a set of KVM servers, or a VMware cluster preconfigured in vCenter. The hosts in a cluster should all have identical hardware, run the same hypervisor, are on the same subnet, and access the same shared primary storage. Virtual machine instances (VMs) can be live-migrated from one host to another within the same cluster, without interrupting service to the user."
+msgstr ""
+
+#: ../../concepts.rst:235
+# 4ef41b7c4493491d97e7520dfbb30e0b
+msgid "The size of the cluster is limited by the underlying hypervisor, although the CloudStack recommends less in most cases; see Best Practices."
+msgstr ""
+
+#: ../../concepts.rst:237
+#: ../../concepts.rst:555
+# 4bd7939a698c4b01b082b24a8b558dee
+# dcc625b8d81c4a7ebf62c75b0b9d8bf4
+msgid "Even when local storage is used exclusively, clusters are still required organizationally, even if there is just one host per cluster."
+msgstr ""
+
+#: ../../concepts.rst:239
+#: ../../concepts.rst:558
+# 068d2e011a0a4368915669d0468b364f
+# 412c8e80c5454415bc755f5805748fbb
+msgid "When VMware is used, every VMware cluster is managed by a vCenter server. An Administrator must register the vCenter server with CloudStack. There may be multiple vCenter servers per zone. Each vCenter server may manage multiple VMware clusters."
+msgstr ""
+
+#: ../../concepts.rst:243
+# e12a2e41a6a04a0c8c2a3c68c7859819
+msgid "Hosts"
+msgstr ""
+
+#: ../../concepts.rst:245
+# 6db43fe675294bdd8fde6a9a20828633
+msgid "A host is a single physical computer. Hosts provide the computing resources that run the guest machines."
+msgstr ""
+
+#: ../../concepts.rst:247
+# 30f88a20767d405385974a2927010c8b
+msgid "The host is the smallest organizational unit within a CloudStack deployment and are not visible to an end user."
+msgstr ""
+
+#: ../../concepts.rst:251
+# de600353067c4e9498a2ac9999fc8d02
+msgid "Primary Storage"
+msgstr ""
+
+#: ../../concepts.rst:253
+# 350198ae9ce54694a6bdba01506da107
+msgid "Primary storage is associated with a cluster and/or a zone. It stores the disk volumes for all of the VMs running on hosts in that cluster. You can add multiple primary storage servers to a cluster or a zone (at least one is required at the cluster level). Primary storage is typically located close to the hosts for increased performance. CloudStack manages the allocation of guest virtual disks to particular primary storage devices."
+msgstr ""
+
+#: ../../concepts.rst:258
+# c057cc657d3c4c7a86217ff789836ed7
+msgid "Primary storage can be either static or dynamic. Static primary storage is what CloudStack has traditionally supported. In this model, the administrator must present CloudStack with a certain amount of preallocated storage (ex. a volume from a SAN) and CloudStack can place many of its volumes on this storage. In the newer, dynamic model, the administrator can present CloudStack with a storage system itself (i.e. a SAN). CloudStack, working in concert with a plug-in developed for that storage system, can dynamically create volumes on the storage system. A valuable use for this ability is Quality of Service (QoS). If a volume created in CloudStack can be backed by a dedicated volume on a SAN (i.e. a one-to-one mapping between a SAN volume and a CloudStack volume) and the SAN provides QoS functionality, then CloudStack can also orchestrate storage QoS."
+msgstr ""
+
+#: ../../concepts.rst:267
+# 8a6a29004f7a48709a1a3d41399d49ec
+msgid "CloudStack is designed to work with all standards-compliant iSCSI and NFS servers that are supported by the underlying hypervisor"
+msgstr ""
+
+#: ../../concepts.rst:269
+# e5eb6c77e9ab45499723e6a4e4c6c27b
+msgid "You may also use local disks as secondary storage, though naturally they don't support live migration."
+msgstr ""
+
+#: ../../concepts.rst:272
+# 4499a9e52aa140a19473933eba3de16a
+msgid "Secondary Storage"
+msgstr ""
+
+#: ../../concepts.rst:274
+#: ../../concepts.rst:671
+# b34204827cfa4c779a1ffced2aa92966
+# 18608ded92924bbf96719cc289392636
+msgid "Secondary storage stores the following:"
+msgstr ""
+
+#: ../../concepts.rst:276
+#: ../../concepts.rst:675
+# 7bc4f80d01b5421db9ae4aeafd947957
+# 167d579993404a03bdb768d3e2b539fd
+msgid "Templates — OS images that can be used to boot VMs and can include additional configuration information, such as installed applications"
+msgstr ""
+
+#: ../../concepts.rst:277
+#: ../../concepts.rst:680
+# 5d98b266bb7245d580a56f8482c39262
+# 0b521b2715f340b7845c94b5fb9cdfd4
+msgid "ISO images — disc images containing data or bootable media for operating systems"
+msgstr ""
+
+#: ../../concepts.rst:278
+#: ../../concepts.rst:685
+# 889bfdad47d64b1fa536a8f40327e0a3
+# 301a1b6d4f6e453d81190810735d3a31
+msgid "Disk volume snapshots — saved copies of VM data which can be used for data recovery or to create new templates"
+msgstr ""
+
+#: ../../concepts.rst:280
+# f05dcac39d704557a0f970fc82cbaf2a
+msgid "The items in secondary storage are available to all hosts in the scope of the secondary storage, which may be defined as per zone or per region. CloudStack supports both NFS and Object Storage supporting either the AWS S3 API or the Swift API as a backing store for Secondary Storage."
+msgstr ""
+
+#: ../../concepts.rst:285
+# 08cfb9856b0a491a8b80bc7aca0e3656
+msgid "Physical Networks"
+msgstr ""
+
+#: ../../concepts.rst:287
+# 4e976e231c45495abc1b5a8f3c17a35d
+msgid "One or more physical networks can be associated with each zone. The physical network typically corresponds to a physical NIC on the host. Each physical network can carry one or more types of network traffic. The choices of traffic type for each network vary depending on your network choices."
+msgstr ""
+
+#: ../../concepts.rst:291
+# 2bad69755ad4458c9fd7b719a88583f2
+msgid "A physical network is the actual network hardware and wiring in a zone. A zone can have multiple physical networks."
+msgstr ""
+
+#: ../../concepts.rst:293
+# 8dc1bebd2d62453f86443cd1b1ed64f2
+msgid "An administrator can:"
+msgstr ""
+
+#: ../../concepts.rst:294
+#: ../../concepts.rst:730
+# 673e055e17e449dcb0ab7cf4e312eb87
+# 4e613ff0b38f47518010324627f2f97b
+msgid "Add/Remove/Update physical networks in a zone"
+msgstr ""
+
+#: ../../concepts.rst:295
+#: ../../concepts.rst:734
+# 6139f902423b47d5b552ae8c19fbcb9c
+# abfd546cfd074ee59013001e4049007a
+msgid "Configure VLANs on the physical network"
+msgstr ""
+
+#: ../../concepts.rst:296
+#: ../../concepts.rst:738
+# 6965d16293b1455c96af0cf908e27b24
+# a09235b0dc774dca9a55392cc7169fe4
+msgid "Configure a name so the network can be recognized by hypervisors"
+msgstr ""
+
+#: ../../concepts.rst:297
+#: ../../concepts.rst:742
+# a0487172ebf546bbbeb1f3df2f50803a
+# c7ab9b29c64b41ba969d89046a76446c
+msgid "Configure the service providers (firewalls, load balancers, etc.) available on a physical network"
+msgstr ""
+
+#: ../../concepts.rst:298
+# b06a129c42574e568380dc64dae12288
+msgid "Configure the IP addresses available to a physical network"
+msgstr ""
+
+#: ../../concepts.rst:299
+#: ../../concepts.rst:751
+# 644023d6849e4861bab38317f62597e8
+# 203d396f0f254b709f521965921090ad
+msgid "Specify what type of traffic is carried on the physical network, as well as other properties like network speed"
+msgstr ""
+
+#: ../../concepts.rst:302
+# 716989fb6e6f4b9b9d99d9c945a6ce82
+msgid "Basic Zone Network Types"
+msgstr ""
+
+#: ../../concepts.rst:304
+#: ../../concepts.rst:757
+# 7e70c69401c3482b88aa41e69bdd57f0
+# a9a7d4c0251b4e36adfbe567da895890
+msgid "When basic networking is used, there can be only one physical network in the zone. That physical network carries the following traffic types:"
+msgstr ""
+
+#: ../../concepts.rst:306
+# 3ac12abeccbd494bad6d9245e62c5422
+msgid "Guest: When end users run VMs, they generate guest traffic. The guest VMs communicate with each other over a network that can be referred to as the guest network. Each pod in a basic zone is a broadcast domain, and therefore each pod has a different IP range for the guest network. The administrator must configure the IP range for each pod."
+msgstr ""
+
+#: ../../concepts.rst:307
+# bff3dd3f0f654c659142572359fae389
+msgid "Management: When CloudStack's internal resources communicate with each other, they generate management traffic. This includes communication between hosts, system VMs (VMs used by CloudStack to perform various tasks in the cloud), and any other component that communicates directly with the CloudStack Management Server. You must configure the IP range for the system VMs to use."
+msgstr ""
+
+#: ../../concepts.rst:308
+# a44d404aec22436cad1c2299d1bbd4a3
+msgid "Public: Public traffic is generated when VMs in the cloud access the Internet. Publicly accessible IPs must be allocated for this purpose. End users can use the CloudStack UI to acquire these IPs to implement NAT between their guest network and the public network, as described in Acquiring a New IP Address."
+msgstr ""
+
+#: ../../concepts.rst:309
+# 42a656c708254cf6a1496e932c0ff068
+msgid "Storage: While labeled \"storage\" this is specifically about secondary storage, and doesn't affect traffic for primary storage. This includes traffic such as VM templates and snapshots, which is sent between the secondary storage VM and secondary storage servers. CloudStack uses a separate Network Interface Controller (NIC) named storage NIC for storage network traffic. Use of a storage NIC that always operates on a high bandwidth network allows fast template and snapshot copying. You must configure the IP range to use for the storage network."
+msgstr ""
+
+#: ../../concepts.rst:311
+#: ../../concepts.rst:802
+# da1af1bd6d90428b849863c866cb558c
+# 191007504ed74f12a036b7b4aa80eb02
+msgid "In a basic network, configuring the physical network is fairly straightforward. In most cases, you only need to configure one guest network to carry traffic that is generated by guest VMs. If you use a NetScaler load balancer and enable its elastic IP and elastic load balancing (EIP and ELB) features, you must also configure a network to carry public traffic. CloudStack takes care of presenting the necessary network configuration steps to you in the UI when you add a new zone."
+msgstr ""
+
+#: ../../concepts.rst:317
+#: ../../concepts.rst:811
+# 52ed9564f5564301b8ca7f7a28d52230
+# 7f7851b143664a31bc5ad1359cd44999
+msgid "Basic Zone Guest IP Addresses"
+msgstr ""
+
+#: ../../concepts.rst:319
+#: ../../concepts.rst:813
+# 7cdc690d38a74425b1fa34daa7d4dc53
+# 3b96868afb964f30b8e97dc558e5d353
+msgid "When basic networking is used, CloudStack will assign IP addresses in the CIDR of the pod to the guests in that pod. The administrator must add a Direct IP range on the pod for this purpose. These IPs are in the same VLAN as the hosts."
+msgstr ""
+
+#: ../../concepts.rst:323
+# c30cdaafea804e4b9de562c8c9caa9cc
+msgid "Advanced Zone Network Types"
+msgstr ""
+
+#: ../../concepts.rst:325
+# fcc04e4ceff84117b3e53bee51437f89
+msgid "When advanced networking is used, there can be multiple physical networks in the zone. Each physical network can carry one or more traffic types, and you need to let CloudStack know which type of network traffic you want each network to carry."
+msgstr ""
+
+#: ../../concepts.rst:328
+# 5a0e6b3314644c8dbef972f02423c28d
+msgid "The traffic types in an advanced zone are:"
+msgstr ""
+
+#: ../../concepts.rst:330
+# 90065dd487b34a26b77e5cc55ed0b4f4
+msgid "**Guest**: When end users run VMs, they generate guest traffic. The guest VMs communicate with each other over a network that can be referred to as the guest network. This network can be isolated or shared. In an isolated guest network, the administrator needs to reserve VLAN ranges to provide isolation for each CloudStack account’s network (potentially a large number of VLANs). In a shared guest network, all guest VMs share a single network."
+msgstr ""
+
+#: ../../concepts.rst:331
+# d2eb0c505d0342ddb32f2ea044d23de6
+msgid "**Management**: When CloudStack’s internal resources communicate with each other, they generate management traffic. This includes communication between hosts, system VMs (VMs used by CloudStack to perform various tasks in the cloud), and any other component that communicates directly with the CloudStack Management Server. You must configure the IP range for the system VMs to use."
+msgstr ""
+
+#: ../../concepts.rst:332
+# a2a81b57809f4d1d8155613824407cfb
+msgid "**Public**: Public traffic is generated when VMs in the cloud access the Internet. Publicly accessible IPs must be allocated for this purpose. End users can use the CloudStack UI to acquire these IPs to implement NAT between their guest network and the public network, as described in “Acquiring a New IP Address” in the Administration Guide."
+msgstr ""
+
+#: ../../concepts.rst:333
+# cc48dcce460248a09e15337063a76c63
+msgid "**Storage**: While labeled \"storage\" this is specifically about secondary storage, and doesn't affect traffic for primary storage. This includes traffic such as VM templates and snapshots, which is sent between the secondary storage VM and secondary storage servers. CloudStack uses a separate Network Interface Controller (NIC) named storage NIC for storage network traffic. Use of a storage NIC that always operates on a high bandwidth network allows fast template and snapshot copying. You must configure the IP range to use for the storage network."
+msgstr ""
+
+#: ../../concepts.rst:335
+# 59b04a547a534553b2b5574c99c8946f
+msgid "These traffic types can each be on a separate physical network, or they can be combined with certain restrictions."
+msgstr ""
+
+#: ../../concepts.rst:338
+#: ../../concepts.rst:872
+# 581125884ee848b19adc4c4310344c2c
+# 6ca1da8a16104aee9f75283327a76b31
+msgid "Advanced Zone Guest IP Addresses"
+msgstr ""
+
+#: ../../concepts.rst:340
+#: ../../concepts.rst:874
+# 5fb5522293ec4ebf836f183a1c0724fb
+# 76db0a52e18245018be54f6193d9ab7d
+msgid "When advanced networking is used, the administrator can create additional networks for use by the guests. These networks can span the zone and be available to all accounts, or they can be scoped to a single account, in which case only the named account may create guests that attach to these networks. The networks are defined by a VLAN ID, IP range, and gateway. The administrator may provision thousands of these networks if desired. Additionally, the administrator can reserve a part of the IP address space for non-CloudStack VMs and servers."
+msgstr ""
+
+#: ../../concepts.rst:347
+#: ../../concepts.rst:884
+# d892c1cc5ef94dd2a238710fcc62b3f3
+# d3231b1597e54924af2efe64f2752996
+msgid "Advanced Zone Public IP Addresses"
+msgstr ""
+
+#: ../../concepts.rst:349
+# 48529282c66f4e818c596eac0b22f4dc
+msgid "In an advanced network, Public IP addresses are typically on one or more dedicated VLANs and are routed or NATed to guest VMs."
+msgstr ""
+
+#: ../../concepts.rst:352
+#: ../../concepts.rst:895
+# bef5f9b7dcf848d5a23e159598861bde
+# 21efd19a0a61497e903a5c90ac00c17a
+msgid "System Reserved IP Addresses"
+msgstr ""
+
+#: ../../concepts.rst:354
+#: ../../concepts.rst:897
+# 4e508c81014d4e29887a3293b9782831
+# 6e227bc9e49e4306a7fa72e1b0475ad0
+msgid "In each zone, you need to configure a range of reserved IP addresses for the management network. This network carries communication between the CloudStack Management Server and various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP."
+msgstr ""
+
+#: ../../concepts.rst:357
+#: ../../concepts.rst:902
+# d385f28804a049149e1dc7d64f1b8b78
+# 3264c18fd3ca489c96c9bf34f7e08f47
+msgid "The reserved IP addresses must be unique across the cloud. You cannot, for example, have a host in one zone which has the same private IP address as a host in another zone."
+msgstr ""
+
+#: ../../concepts.rst:360
+#: ../../concepts.rst:906
+# 8bd3ab39146d465fb707abed820432bf
+# d78c6b7284f8455e8e2708bd1ddb8f31
+msgid "The hosts in a pod are assigned private IP addresses. These are typically RFC1918 addresses. The Console Proxy and Secondary Storage system VMs are also allocated private IP addresses in the CIDR of the pod that they are created in."
+msgstr ""
+
+#: ../../concepts.rst:363
+# ddc8e2a3b2324070a33acc6eae3de7bf
+msgid "Make sure computing servers and Management Servers use IP addresses outside of the System Reserved IP range. In example, suppose the System Reserved IP range starts at 192.168.154.2 and ends at 192.168.154.7. CloudStack can use .2 to .7 for System VMs. This leaves the rest of the pod CIDR, from .8 to .254, for the Management Server and hypervisor hosts."
+msgstr ""
+
+#: ../../concepts.rst:368
+# eca6adde7164436e95f9f0b7ca27f3d2
+msgid "In all zones"
+msgstr ""
+
+#: ../../concepts.rst:370
+#: ../../concepts.rst:920
+# 805296fd2460493e9da6efef11a237d8
+# 97254c396f974c28899a695da5a256bc
+msgid "Provide private IPs for the system in each pod and provision them in CloudStack."
+msgstr ""
+
+#: ../../concepts.rst:372
+#: ../../concepts.rst:923
+# dd17defbc77844f3ae99664b2dd14669
+# 9d974eb2e59d418e95c8cab21c4cb765
+msgid "For KVM and XenServer, the recommended number of private IPs per pod is one per host. If you expect a pod to grow, add enough private IPs now to accommodate the growth."
+msgstr ""
+
+#: ../../concepts.rst:376
+# 201c6ab211a6483299774ba062c21759
+msgid "In a zone that uses advanced networking"
+msgstr ""
+
+#: ../../concepts.rst:378
+#: ../../concepts.rst:929
+# b83e478a382d49189d28f20d21deefb3
+# 7d09c246921c4149a7e2cf0b1354861b
+msgid "For zones with advanced networking, we recommend provisioning enough private IPs for your total number of customers, plus enough for the required CloudStack System VMs. Typically, about 10 additional IPs are required for the System VMs. For more information about System VMs, see the section on working with SystemVMs in the Administrator's Guide."
+msgstr ""
+
+#: ../../concepts.rst:382
+#: ../../concepts.rst:935
+# 007bfa0acd5a48689fc6a288169b4152
+# 21bf97bde5264f9f8d6b8c7b250e8559
+msgid "When advanced networking is being used, the number of private IP addresses available in each pod varies depending on which hypervisor is running on the nodes in that pod. Citrix XenServer and KVM use link-local addresses, which in theory provide more than 65,000 private IP addresses within the address block. As the pod grows over time, this should be more than enough for any reasonable number of hosts as well as IP addresses for guest virtual routers. VMWare ESXi, by contrast uses any administrator-specified subnetting scheme, and the typical administrator provides only 255 IPs per pod. Since these are shared by physical machines, the guest virtual router, and other entities, it is possible to run out of private IPs when scaling up a pod whose nodes are running ESXi."
+msgstr ""
+
+#: ../../concepts.rst:390
+#: ../../concepts.rst:948
+# 87751541797d455d9a8895a446a4c699
+# fd6f72eb0ae04120aec4b9d55dc8e9d3
+msgid "To ensure adequate headroom to scale private IP space in an ESXi pod that uses advanced networking, use one or both of the following techniques:"
+msgstr ""
+
+#: ../../concepts.rst:392
+#: ../../concepts.rst:954
+# 27d54cfd61944602a6e4c1a6620312e2
+# 0c5aa832bb5d431c9a6bcf25d0ceb6cb
+msgid "Specify a larger CIDR block for the subnet. A subnet mask with a /20 suffix will provide more than 4,000 IP addresses."
+msgstr ""
+
+#: ../../concepts.rst:393
+# 670cb02dfb504639b0c10af5a1b05736
+msgid "Create multiple pods, each with its own subnet. In example, if you create 10 pods and each pod has 255 IPs, this will provide 2,550 IP addresses."
+msgstr ""
+
+#: ../../concepts.rst:397
+# 48f643ed242e4501b8761273a71ee960
+msgid "CloudStack Terminology"
+msgstr ""
+
+#: ../../concepts.rst:400
+# 7f83b27f3b074d4798ba28ebaa8e9dc5
+msgid "About Regions"
+msgstr ""
+
+#: ../../concepts.rst:423
+# 77489477fc9c4ac182a3e03f1cdd9a6d
+msgid "|region-overview.png: Nested structure of a region.|"
+msgstr ""
+
+#: ../../concepts.rst:432
+# 8c52014de7f74a86a087cdd0b524c3bd
+msgid "About Zones"
+msgstr ""
+
+#: ../../concepts.rst:458
+# c2a0e65f22b04f279dadce7331a885e2
+msgid "|zone-overview.png: Nested structure of a simple zone.|"
+msgstr ""
+
+#: ../../concepts.rst:502
+# 9b94cbd4c96c462caa6d4012880e39d2
+msgid "When you add a new zone using the CloudStack UI, you will be prompted to configure the zone’s physical network and add the first pod, cluster, host, primary storage, and secondary storage."
+msgstr ""
+
+#: ../../concepts.rst:517
+# dba480aeca244d718b2d6ebcafea03e9
+msgid "If you are upgrading from a previous CloudStack version, and your existing deployment contains a zone with clusters from multiple VMware Datacenters, that zone will not be forcibly migrated to the new model. It will continue to function as before. However, any new zone-wide operations, such as zone-wide primary storage and live storage migration, will not be available in that zone."
+msgstr ""
+
+#: ../../concepts.rst:520
+# 54db4ee812af4afeb4022ba56f6042c2
+msgid "About Pods"
+msgstr ""
+
+#: ../../concepts.rst:522
+# aae3ab7a910741328f9dea985ae6c141
+msgid "A pod often represents a single rack. Hosts in the same pod are in the same subnet. A pod is the third-largest organizational unit within a CloudStack deployment. Pods are contained within zones. Each zone can contain one or more pods. A pod consists of one or more clusters of hosts and one or more primary storage servers. Pods are not visible to the end user."
+msgstr ""
+
+#: ../../concepts.rst:529
+# 4c861ca60e304b1fb87ad569764097d7
+msgid "|pod-overview.png: Nested structure of a simple pod|"
+msgstr ""
+
+#: ../../concepts.rst:532
+# 096b727fd7444148a2c51998c1132116
+msgid "About Clusters"
+msgstr ""
+
+#: ../../concepts.rst:534
+# d8d6efc761534d708ee129f70a0e5cc5
+msgid "A cluster provides a way to group hosts. To be precise, a cluster is a XenServer server pool, a set of KVM servers, , or a VMware cluster preconfigured in vCenter. The hosts in a cluster all have identical hardware, run the same hypervisor, are on the same subnet, and access the same shared primary storage. Virtual machine instances (VMs) can be live-migrated from one host to another within the same cluster, without interrupting service to the user."
+msgstr ""
+
+#: ../../concepts.rst:542
+# 7351147d578e4ecda91e712f39534df2
+msgid "A cluster is the fourth-largest organizational unit within a CloudStack deployment. Clusters are contained within pods, and pods are contained within zones. Size of the cluster is limited by the underlying hypervisor, although the CloudStack recommends less in most cases; see Best Practices."
+msgstr ""
+
+#: ../../concepts.rst:548
+# f4244191ac2a41058ff5d2202e0aaa51
+msgid "A cluster consists of one or more hosts and one or more primary storage servers."
+msgstr ""
+
+#: ../../concepts.rst:551
+# 0b0cb15f7bec487eb3099ea1c494db01
+msgid "|cluster-overview.png: Structure of a simple cluster|"
+msgstr ""
+
+#: ../../concepts.rst:553
+# 3ee369925fad4ae2b64b0d10eeeae914
+msgid "CloudStack allows multiple clusters in a cloud deployment."
+msgstr ""
+
+#: ../../concepts.rst:564
+# 3a0b47da5f2b4880a1e6c5463b4138f7
+msgid "About Hosts"
+msgstr ""
+
+#: ../../concepts.rst:566
+# 205fdc6d2c01429b9ed6756a4b980ded
+msgid "A host is a single computer. Hosts provide the computing resources that run guest virtual machines. Each host has hypervisor software installed on it to manage the guest VMs. For example, a host can be a Citrix XenServer server, a Linux KVM-enabled server, an ESXi server, or a Windows Hyper-V server."
+msgstr ""
+
+#: ../../concepts.rst:572
+# 97449427b2834b5a910f749370834a3c
+msgid "The host is the smallest organizational unit within a CloudStack deployment. Hosts are contained within clusters, clusters are contained within pods, pods are contained within zones, and zones can be contained within regions."
+msgstr ""
+
+#: ../../concepts.rst:577
+# 58a7f1c53f844ff292a15d04befeb5ce
+msgid "Hosts in a CloudStack deployment:"
+msgstr ""
+
+#: ../../concepts.rst:581
+# f671a906b30a42e1a516954f4e20c606
+msgid "Provide the CPU, memory, storage, and networking resources needed to host the virtual machines"
+msgstr ""
+
+#: ../../concepts.rst:586
+# 765e1241863645eba92568a45ac677f4
+msgid "Interconnect using a high bandwidth TCP/IP network and connect to the Internet"
+msgstr ""
+
+#: ../../concepts.rst:591
+# 5820e8689f01475b9e873d5dc6179a6f
+msgid "May reside in multiple data centers across different geographic locations"
+msgstr ""
+
+#: ../../concepts.rst:596
+# 062511e0a1fa417bad68cce103d84666
+msgid "May have different capacities (different CPU speeds, different amounts of RAM, etc.), although the hosts within a cluster must all be homogeneous"
+msgstr ""
+
+#: ../../concepts.rst:600
+# 23aec79990ea417598eea7c77847a775
+msgid "Additional hosts can be added at any time to provide more capacity for guest VMs."
+msgstr ""
+
+#: ../../concepts.rst:603
+# e1adace21ae0456dbcf93531f4957248
+msgid "CloudStack automatically detects the amount of CPU and memory resources provided by the hosts."
+msgstr ""
+
+#: ../../concepts.rst:606
+# e6b130b004b7446aa1601c31a04ec880
+msgid "Hosts are not visible to the end user. An end user cannot determine which host their guest has been assigned to."
+msgstr ""
+
+#: ../../concepts.rst:609
+# 855a204e524044c0b8b0966e23500edc
+msgid "For a host to function in CloudStack, you must do the following:"
+msgstr ""
+
+#: ../../concepts.rst:613
+# 8a6eda274c124ba7a819d60409feda29
+msgid "Install hypervisor software on the host"
+msgstr ""
+
+#: ../../concepts.rst:617
+# 05c37b7642704df08b323c1676a611ef
+msgid "Assign an IP address to the host"
+msgstr ""
+
+#: ../../concepts.rst:621
+# b5a14bffa6c0494094b1437abbdffb24
+msgid "Ensure the host is connected to the CloudStack Management Server."
+msgstr ""
+
+#: ../../concepts.rst:624
+# 0461535a3ff54eb890711bd518df5a2f
+msgid "About Primary Storage"
+msgstr ""
+
+#: ../../concepts.rst:626
+# 61eabe7827a34e75a9280dc9d6ae6a01
+msgid "Primary storage is associated with a cluster or (in KVM and VMware) a zone, and it stores the disk volumes for all the VMs running on hosts."
+msgstr ""
+
+#: ../../concepts.rst:629
+# 8a0469a7335942a787a9af2154ccfd35
+msgid "You can add multiple primary storage servers to a cluster or zone. At least one is required. It is typically located close to the hosts for increased performance. CloudStack manages the allocation of guest virtual disks to particular primary storage devices."
+msgstr ""
+
+#: ../../concepts.rst:634
+# e8bd1c7d24f44522bf5c9321d36534eb
+msgid "It is useful to set up zone-wide primary storage when you want to avoid extra data copy operations. With cluster-based primary storage, data in the primary storage is directly available only to VMs within that cluster. If a VM in a different cluster needs some of the data, it must be copied from one cluster to another, using the zone's secondary storage as an intermediate step. This operation can be unnecessarily time-consuming."
+msgstr ""
+
+#: ../../concepts.rst:642
+# c7f83a84661a43f2b010ab9aef5cca67
+msgid "For Hyper-V, SMB/CIFS storage is supported. Note that Zone-wide Primary Storage is not supported in Hyper-V."
+msgstr ""
+
+#: ../../concepts.rst:645
+# b634131439874a00a2ee27850bce0321
+msgid "CloudStack is designed to work with all standards-compliant iSCSI and NFS servers that are supported by the underlying hypervisor, including, for example:"
+msgstr ""
+
+#: ../../concepts.rst:651
+# 679f58d91ca547b381015341a15876e7
+msgid "SolidFire for iSCSI"
+msgstr ""
+
+#: ../../concepts.rst:655
+# 0074b93405934cd9af05d2d7dee1eff7
+msgid "Dell EqualLogic™ for iSCSI"
+msgstr ""
+
+#: ../../concepts.rst:659
+# 7bbec1e2cd6d4562a07d26dc3729c274
+msgid "Network Appliances filers for NFS and iSCSI"
+msgstr ""
+
+#: ../../concepts.rst:663
+# 09fab1fa10654e6fb7cd7d11c6bfc186
+msgid "Scale Computing for NFS"
+msgstr ""
+
+#: ../../concepts.rst:665
+# 3538437e1d8841d68caca6d2cfc38a49
+msgid "If you intend to use only local disk for your installation, you can skip adding separate primary storage."
+msgstr ""
+
+#: ../../concepts.rst:669
+# ad3da3f468ca4f31b1ad424695d356d6
+msgid "About Secondary Storage"
+msgstr ""
+
+#: ../../concepts.rst:688
+# 75d27a88966c4c6dae20b8fa670b8993
+msgid "The items in secondary storage are available to all hosts in the scope of the secondary storage, which may be defined as per zone or per region."
+msgstr ""
+
+#: ../../concepts.rst:692
+# ed4098415be54095b396714cb7c514c3
+msgid "To make items in secondary storage available to all hosts throughout the cloud, you can add object storage in addition to the zone-based NFS Secondary Staging Store. It is not necessary to copy templates and snapshots from one zone to another, as would be required when using zone NFS alone. Everything is available everywhere."
+msgstr ""
+
+#: ../../concepts.rst:698
+# 79c26db02f0249f8b6c794319a0ea2b1
+msgid "For Hyper-V hosts, SMB/CIFS storage is supported."
+msgstr ""
+
+#: ../../concepts.rst:700
+# 913e44de9bcd4ad39ef301e44f9f4912
+msgid "CloudStack provides plugins that enable both OpenStack Object Storage (Swift, `swift.openstack.org <http://swift.openstack.org>`__) and Amazon Simple Storage Service (S3) object storage. When using one of these storage plugins, you configure Swift or S3 storage for the entire CloudStack, then set up the NFS Secondary Staging Store for each zone. The NFS storage in each zone acts as a staging area through which all templates and other secondary storage data pass before being forwarded to Swift or S3. The backing object storage acts as a cloud-wide resource, making templates and other data available to any zone in the cloud."
+msgstr ""
+
+#: ../../concepts.rst:713
+# 923b43f36d6a43779d097362df5eeecc
+msgid "Heterogeneous Secondary Storage is not supported in Regions. For example, you cannot set up multiple zones, one using NFS secondary and the other using S3 or Swift secondary."
+msgstr ""
+
+#: ../../concepts.rst:716
+# 61ac7438b69a4a86af94a1bf2fe64fe3
+msgid "About Physical Networks"
+msgstr ""
+
+#: ../../concepts.rst:718
+# 4dcdb324118640269de7380c6bee06f1
+msgid "Part of adding a zone is setting up the physical network. One or (in an advanced zone) more physical networks can be associated with each zone. The network corresponds to a NIC on the hypervisor host. Each physical network can carry one or more types of network traffic. The choices of traffic type for each network vary depending on whether you are creating a zone with basic networking or advanced networking."
+msgstr ""
+
+#: ../../concepts.rst:725
+# f7b77ed223b4433987d4702a01fb8c47
+msgid "A physical network is the actual network hardware and wiring in a zone. A zone can have multiple physical networks. An administrator can:"
+msgstr ""
+
+#: ../../concepts.rst:747
+# 24d09735b0ca4143ad8978d89842d154
+msgid "Configure the IP addresses trunked to a physical network"
+msgstr ""
+
+#: ../../concepts.rst:755
+# bd87d1fd70d34ff3958228f36bf6538e
+msgid "Basic Zone Network Traffic Types"
+msgstr ""
+
+#: ../../concepts.rst:762
+# a9dadbb1895845ecaffeb810b06b7ec8
+msgid "Guest. When end users run VMs, they generate guest traffic. The guest VMs communicate with each other over a network that can be referred to as the guest network. Each pod in a basic zone is a broadcast domain, and therefore each pod has a different IP range for the guest network. The administrator must configure the IP range for each pod."
+msgstr ""
+
+#: ../../concepts.rst:770
+# dc406b9190ce4cc48f7f4b3443ff4cda
+msgid "Management. When CloudStack's internal resources communicate with each other, they generate management traffic. This includes communication between hosts, system VMs (VMs used by CloudStack to perform various tasks in the cloud), and any other component that communicates directly with the CloudStack Management Server. You must configure the IP range for the system VMs to use."
+msgstr ""
+
+#: ../../concepts.rst:779
+# 39db7e6a26f746ceb0672acda7fd8080
+msgid "We strongly recommend the use of separate NICs for management traffic and guest traffic."
+msgstr ""
+
+#: ../../concepts.rst:784
+# 3ee341c4481d464d9ade2fe2546540d8
+msgid "Public. Public traffic is generated when VMs in the cloud access the Internet. Publicly accessible IPs must be allocated for this purpose. End users can use the CloudStack UI to acquire these IPs to implement NAT between their guest network and the public network, as described in Acquiring a New IP Address."
+msgstr ""
+
+#: ../../concepts.rst:792
+#: ../../concepts.rst:856
+# 9f0a166f4cdd4eaba88ff44521189e57
+# d61ccfa4d6b6457189863747e25fe247
+msgid "Storage. While labeled \"storage\" this is specifically about secondary storage, and doesn't affect traffic for primary storage. This includes traffic such as VM templates and snapshots, which is sent between the secondary storage VM and secondary storage servers. CloudStack uses a separate Network Interface Controller (NIC) named storage NIC for storage network traffic. Use of a storage NIC that always operates on a high bandwidth network allows fast template and snapshot copying. You must configure the IP range to use for the storage network."
+msgstr ""
+
+#: ../../concepts.rst:819
+# c58251d2d6c34f4eaef1b3e7b07bee7b
+msgid "Advanced Zone Network Traffic Types"
+msgstr ""
+
+#: ../../concepts.rst:821
+# 64b15543219244289efe314f52a850aa
+msgid "When advanced networking is used, there can be multiple physical networks in the zone. Each physical network can carry one or more traffic types, and you need to let CloudStack know which type of network traffic you want each network to carry. The traffic types in an advanced zone are:"
+msgstr ""
+
+#: ../../concepts.rst:829
+# 6d72677dcf1d4796a4ed9b8e2bfd36c7
+msgid "Guest. When end users run VMs, they generate guest traffic. The guest VMs communicate with each other over a network that can be referred to as the guest network. This network can be isolated or shared. In an isolated guest network, the administrator needs to reserve VLAN ranges to provide isolation for each CloudStack account’s network (potentially a large number of VLANs). In a shared guest network, all guest VMs share a single network."
+msgstr ""
+
+#: ../../concepts.rst:839
+# 00a3aa2f55574d10ac98903ab4705480
+msgid "Management. When CloudStack’s internal resources communicate with each other, they generate management traffic. This includes communication between hosts, system VMs (VMs used by CloudStack to perform various tasks in the cloud), and any other component that communicates directly with the CloudStack Management Server. You must configure the IP range for the system VMs to use."
+msgstr ""
+
+#: ../../concepts.rst:848
+# b04011567f254066b55ed823e80437c1
+msgid "Public. Public traffic is generated when VMs in the cloud access the Internet. Publicly accessible IPs must be allocated for this purpose. End users can use the CloudStack UI to acquire these IPs to implement NAT between their guest network and the public network, as described in “Acquiring a New IP Address” in the Administration Guide."
+msgstr ""
+
+#: ../../concepts.rst:866
+# c0e1e92bce5348458d8da10a51171774
+msgid "These traffic types can each be on a separate physical network, or they can be combined with certain restrictions. When you use the Add Zone wizard in the UI to create a new zone, you are guided into making only valid choices."
+msgstr ""
+
+#: ../../concepts.rst:886
+# db963f68933d4705bbfd94377585e0e5
+msgid "When advanced networking is used, the administrator can create additional networks for use by the guests. These networks can span the zone and be available to all accounts, or they can be scoped to a single account, in which case only the named account may create guests that attach to these networks. The networks are defined by a VLAN ID, IP range, and gateway. The administrator may provision thousands of these networks if desired."
+msgstr ""
+
+#: ../../concepts.rst:911
+# fb0ea82f51c14b77915b642a9480bc28
+msgid "Make sure computing servers and Management Servers use IP addresses outside of the System Reserved IP range. For example, suppose the System Reserved IP range starts at 192.168.154.2 and ends at 192.168.154.7. CloudStack can use .2 to .7 for System VMs. This leaves the rest of the pod CIDR, from .8 to .254, for the Management Server and hypervisor hosts."
+msgstr ""
+
+#: ../../concepts.rst:918
+# e772bcd2076945f1803767331cb65080
+msgid "**In all zones:**"
+msgstr ""
+
+#: ../../concepts.rst:927
+# 5cd0b2295fe54192bdb8dbae7d2e902a
+msgid "**In a zone that uses advanced networking:**"
+msgstr ""
+
+#: ../../concepts.rst:959
+# 6851d74b7aa544dda60f5c0e80f5a2db
+msgid "Create multiple pods, each with its own subnet. For example, if you create 10 pods and each pod has 255 IPs, this will provide 2,550 IP addresses."
+msgstr ""
+
diff --git a/source/conceptsandterminology/locale/pot/dev.pot b/source/conceptsandterminology/locale/pot/dev.pot
new file mode 100644
index 0000000..e97c9d1
--- /dev/null
+++ b/source/conceptsandterminology/locale/pot/dev.pot
@@ -0,0 +1,2817 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../dev.rst:2
+# 88f847a36ab24727950459a3432c0d4e
+msgid "Programmer Guide"
+msgstr ""
+
+#: ../../dev.rst:4
+# 0f57e8ddad1c42e484b86fabd6e7c7fd
+msgid "This guide shows how to develop CloudStack, use the API for operation and integration, access the usage data and use CloudStack specific tools to ease development, testing and integration."
+msgstr ""
+
+#: ../../dev.rst:9
+# b4dde114728d4a729b84dad8a71507ad
+msgid "The CloudStack API"
+msgstr ""
+
+#: ../../dev.rst:12
+# 2faafa276d4e4ec88166c7c604c83c2e
+msgid "Getting Started"
+msgstr ""
+
+#: ../../dev.rst:14
+# d2952855db3649debf7352fd97ca4dbd
+msgid "To get started using the CloudStack API, you should have the following:"
+msgstr ""
+
+#: ../../dev.rst:18
+# 6e34aa46096b49b5be7da378474756f6
+msgid "URL of the CloudStack server you wish to integrate with."
+msgstr ""
+
+#: ../../dev.rst:22
+# e20e5d4ce4794e1691532c2ae747fad4
+msgid "Both the API Key and Secret Key for an account. This should have been generated by the administrator of the cloud instance and given to you."
+msgstr ""
+
+#: ../../dev.rst:28
+# ce44c9141f7e47ab901755a829921fc4
+msgid "Familiarity with HTTP GET/POST and query strings."
+msgstr ""
+
+#: ../../dev.rst:32
+# 44afe433c3ba402592498a6d55054c3a
+msgid "Knowledge of either XML or JSON."
+msgstr ""
+
+#: ../../dev.rst:36
+# 8cc15fe3964b44f3bf7f5b081a63501a
+msgid "Knowledge of a programming language that can generate HTTP requests; for example, Java or PHP."
+msgstr ""
+
+#: ../../dev.rst:40
+# 0d1fd7417b374a92a6e8ff42c7de5f5f
+msgid "Roles"
+msgstr ""
+
+#: ../../dev.rst:42
+# a07a254a222b4b028ebfea899f24c427
+msgid "The CloudStack API supports three access roles:"
+msgstr ""
+
+#: ../../dev.rst:46
+# 392ae4bd66d64586966361344f43d7cb
+msgid "Root Admin. Access to all features of the cloud, including both virtual and physical resource management."
+msgstr ""
+
+#: ../../dev.rst:51
+# 37c6d4ae56ed4b8a9ad98403b5e5c96c
+msgid "Domain Admin. Access to only the virtual resources of the clouds that belong to the administrator’s domain."
+msgstr ""
+
+#: ../../dev.rst:56
+# b6ead3abd7c6436e98f8add08e0b6550
+msgid "User. Access to only the features that allow management of the user’s virtual instances, storage, and network."
+msgstr ""
+
+#: ../../dev.rst:60
+# d72c3200f2224e248b1fe29033daa2d8
+msgid "API Reference Documentation"
+msgstr ""
+
+#: ../../dev.rst:62
+# d579042449a446acbbc65afcb8262fe6
+msgid "You can find all the API reference documentation at the below site:"
+msgstr ""
+
+#: ../../dev.rst:64
+# bcdf9d282f994c9e9cfc62a64151533a
+msgid "`http://cloudstack.apache.org/docs/api/ <http://cloudstack.apache.org/docs/api/>`__"
+msgstr ""
+
+#: ../../dev.rst:68
+# fdfacdd621784fc297905261cad0e2b0
+msgid "Making API Requests"
+msgstr ""
+
+#: ../../dev.rst:70
+# e1e9b59b70534ede8be8075893d353bf
+msgid "All CloudStack API requests are submitted in the form of a HTTP GET/POST with an associated command and any parameters. A request is composed of the following whether in HTTP or HTTPS:"
+msgstr ""
+
+#: ../../dev.rst:76
+# c71e5c34c5184f5480acb14acce1b2fd
+msgid "CloudStack API URL: This is the web services API entry point(for example, http://www.cloud.com:8080/client/api)"
+msgstr ""
+
+#: ../../dev.rst:81
+# 4af664897d734c228901165674b5f9c9
+msgid "Command: The web services command you wish to execute, such as start a virtual machine or create a disk volume"
+msgstr ""
+
+#: ../../dev.rst:86
+# 8161421f5e1e4ce4995d92771ed5f337
+msgid "Parameters: Any additional required or optional parameters for the command"
+msgstr ""
+
+#: ../../dev.rst:89
+# e7a76dd2b0b44e78be07604e1c297fa6
+msgid "A sample API GET request looks like the following:"
+msgstr ""
+
+#: ../../dev.rst:93
+#: ../../dev.rst:218
+# 839ab4dd86ff46168b63999452785de2
+# 92503d159e174305aea2ec57b9970197
+msgid "http://localhost:8080/client/api?command=deployVirtualMachine&serviceOfferingId=1&diskOfferingId=1&templateId=2&zoneId=4&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D"
+msgstr ""
+
+#: ../../dev.rst:95
+# c4dcb67b67be49aa97bf850855f2e570
+msgid "Or in a more readable format:"
+msgstr ""
+
+#: ../../dev.rst:108
+# 5658859b97f84f9fb99df745f03051dd
+msgid "The first line is the CloudStack API URL. This is the Cloud instance you wish to interact with."
+msgstr ""
+
+#: ../../dev.rst:111
+# cb39ff065be04c6d9928471bb0a63195
+msgid "The second line refers to the command you wish to execute. In our example, we are attempting to deploy a fresh new virtual machine. It is preceded by a (?) to separate itself from the CloudStack API URL."
+msgstr ""
+
+#: ../../dev.rst:115
+# f871421126304dc095187dd439c11227
+msgid "Lines 3-6 are the parameters for this given command. To see the command and its request parameters, please refer to the appropriate section in the CloudStack API documentation. Each parameter field-value pair (field=value) is preceded by an ampersand character (&)."
+msgstr ""
+
+#: ../../dev.rst:120
+# e21bba7a1c744465ad31aaac4e06e929
+msgid "Line 7 is the user API Key that uniquely identifies the account. See Signing API Requests on page 7."
+msgstr ""
+
+#: ../../dev.rst:123
+# e26911e8e5064274b96a833855baf9c1
+msgid "Line 8 is the signature hash created to authenticate the user account executing the API command."
+msgstr ""
+
+#: ../../dev.rst:127
+# cd3619220ee145afb7e0d7fe3d447341
+msgid "Signing API Requests"
+msgstr ""
+
+#: ../../dev.rst:129
+# 3e2a0ec5c9de4183869e2a5669dc91e6
+msgid "Whether you access the CloudStack API with HTTP or HTTPS, it must still be signed so that CloudStack can verify the caller has been authenticated and authorized to execute the command. Make sure that you have both the API Key and Secret Key provided by the CloudStack administrator for your account before proceeding with the signing process."
+msgstr ""
+
+#: ../../dev.rst:136
+# d443f5ac0cce419f98b4469aa4c74efc
+msgid "To show how to sign a request, we will re-use the previous example."
+msgstr ""
+
+#: ../../dev.rst:140
+# aae90ce3351a4bb8a5e8c0331cbf00cd
+msgid "http://http://localhost:8080/client/api?command=deployVirtualMachine&serviceOfferingId=1&diskOfferingId=1&templateId=2&zoneId=4&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D"
+msgstr ""
+
+#: ../../dev.rst:142
+# 35dcfbf008ad4133ad5dc64fb30232fe
+msgid "Breaking this down, we have several distinct parts to this URL."
+msgstr ""
+
+#: ../../dev.rst:146
+# 6abafe49687f4dee8772fec806d0fbd0
+msgid "Base URL: This is the base URL to the CloudStack Management Server."
+msgstr ""
+
+#: ../../dev.rst:154
+# 502701cea95040dd901c250e2d0e8059
+msgid "API Path: This is the path to the API Servlet that processes the incoming requests."
+msgstr ""
+
+#: ../../dev.rst:163
+# 5fd2fb195663434b8eae0db2e905f7f3
+msgid "Command String: This part of the query string comprises of the command, its parameters, and the API Key that identifies the account."
+msgstr ""
+
+#: ../../dev.rst:166
+# 6d8b992821454cf78809f60e02caf972
+msgid "As with all query string parameters of field-value pairs, the \"field\""
+msgstr ""
+
+#: ../../dev.rst:167
+# 32e9c80b9e674a428009e106c65505ac
+msgid "component is case insensitive while all \"value\" values are case sensitive."
+msgstr ""
+
+#: ../../dev.rst:171
+# 833166ee436145508ce6902e1aeffc36
+msgid "command=deployVirtualMachine&serviceOfferingId=1&diskOfferingId=1&templateId=2&zoneId=4&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ"
+msgstr ""
+
+#: ../../dev.rst:175
+# e0507ec466f2491b916cafe05332028e
+msgid "Signature: This is the signature of the command string that is generated using a combination of the user’s Secret Key and the HMAC SHA-1 hashing algorithm."
+msgstr ""
+
+#: ../../dev.rst:183
+# 56bc11e5a54743cead5ba505735d0f79
+msgid "Every API request has the format Base URL+API Path+Command String+Signature."
+msgstr ""
+
+#: ../../dev.rst:186
+# 66917cd0ddef4cbfa9969c8c62803fd5
+msgid "To generate the signature."
+msgstr ""
+
+#: ../../dev.rst:190
+# c1d626c724ca48c2bb66f26a7036f65c
+msgid "For each field-value pair (as separated by a '&') in the Command String, URL encode each value so that it can be safely sent via HTTP GET."
+msgstr ""
+
+#: ../../dev.rst:194
+# 849f31408097498fbc9fb864c4435713
+msgid "Make sure all spaces are encoded as \"%20\" rather than \"+\"."
+msgstr ""
+
+#: ../../dev.rst:198
+# 20123502d7d44283b033a23b098a6cd4
+msgid "Lower case the entire Command String and sort it alphabetically via the field for each field-value pair. The result of this step would look like the following."
+msgstr ""
+
+#: ../../dev.rst:207
+# 53d9f03880b24e7992cd7b942d23ecbc
+msgid "Take the sorted Command String and run it through the HMAC SHA-1 hashing algorithm (most programming languages offer a utility method to do this) with the user’s Secret Key. Base64 encode the resulting byte array in UTF-8 so that it can be safely transmitted via HTTP. The final string produced after Base64 encoding should be \"Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D\"."
+msgstr ""
+
+#: ../../dev.rst:214
+# 20f9ee5f604b44fe82bf083906283ebc
+msgid "By reconstructing the final URL in the format Base URL+API Path+Command String+Signature, the final URL should look like:"
+msgstr ""
+
+#: ../../dev.rst:218
+# 2734f0e154c9498c9f65854c74d2b783
+msgid "::"
+msgstr ""
+
+#: ../../dev.rst:221
+# 3ce7bf410679444083db2b9723ce5a09
+msgid "How to sign an API call with Python"
+msgstr ""
+
+#: ../../dev.rst:223
+# 45495f340169452bbd9d83500c6b54d7
+msgid "To illustrate the procedure used to sign API calls we present a step by step interactive session using Python."
+msgstr ""
+
+#: ../../dev.rst:226
+# a9445dca7193488db115b1dd27e16395
+msgid "First import the required modules:"
+msgstr ""
+
+#: ../../dev.rst:241
+# 24398af487f5422ea5406e130f926fbe
+msgid "Define the endpoint of the Cloud, the command that you want to execute and the keys of the user."
+msgstr ""
+
+#: ../../dev.rst:254
+# b8f133da9e9845f584a2d15536349c5b
+msgid "Build the request string:"
+msgstr ""
+
+#: ../../dev.rst:263
+# dc2504e7f3ee48a6ba9653dbb4da0589
+msgid "Compute the signature with hmac, do a 64 bit encoding and a url encoding:"
+msgstr ""
+
+#: ../../dev.rst:285
+# f894c91edede40f89c0ad62bbb5248bc
+msgid "Finally, build the entire string and do an http GET:"
+msgstr ""
+
+#: ../../dev.rst:298
+# 1fce99e27cc64e45990fc200e6766c42
+msgid "Enabling API Call Expiration"
+msgstr ""
+
+#: ../../dev.rst:300
+# 9624c8d51175474abd13be2f82f22b03
+msgid "You can set an expiry timestamp on API calls to prevent replay attacks over non-secure channels, such as HTTP. The server tracks the expiry timestamp you have specified and rejects all the subsequent API requests that come in after this validity period."
+msgstr ""
+
+#: ../../dev.rst:305
+# 514e9deb7f1643fda9234008bffaa453
+msgid "To enable this feature, add the following parameters to the API request:"
+msgstr ""
+
+#: ../../dev.rst:309
+# 832359e119854ea5bb64af41c59b2258
+msgid "signatureVersion=3: If the signatureVersion parameter is missing or is not equal to 3, the expires parameter is ignored in the API request."
+msgstr ""
+
+#: ../../dev.rst:315
+# feb0edf3984b47e6bff184977e549c3a
+msgid "expires=YYYY-MM-DDThh:mm:ssZ: Specifies the date and time at which the signature included in the request is expired. The timestamp is expressed in the YYYY-MM-DDThh:mm:ssZ format, as specified in the ISO 8601 standard."
+msgstr ""
+
+#: ../../dev.rst:320
+# 486d0b76a367414699a9cf2679731557
+msgid "For example:"
+msgstr ""
+
+#: ../../dev.rst:326
+# e69f535ec1054617ba6b1f945568616d
+msgid "A sample API request with expiration is given below:"
+msgstr ""
+
+#: ../../dev.rst:330
+# cb3c57ee68b64c18a36b87f60302039e
+msgid "http://<IPAddress>:8080/client/api?command=listZones&signatureVersion=3&expires=2011-10-10T12:00:00+0530&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D"
+msgstr ""
+
+#: ../../dev.rst:334
+# c4ce501303704bfca5c61ce887cb649d
+msgid "Limiting the Rate of API Requests"
+msgstr ""
+
+#: ../../dev.rst:336
+# 0efa32dc30464f9f84f8beaedac11307
+msgid "You can limit the rate at which API requests can be placed for each account. This is useful to avoid malicious attacks on the Management Server, prevent performance degradation, and provide fairness to all accounts."
+msgstr ""
+
+#: ../../dev.rst:341
+# 72c69812e9714487a4215ddf8895699d
+msgid "If the number of API calls exceeds the threshold, an error message is returned for any additional API calls. The caller will have to retry these API calls at another time."
+msgstr ""
+
+#: ../../dev.rst:346
+# 5bf3283a5a704f7d91d1c78dd39ca2d6
+msgid "Configuring the API Request Rate"
+msgstr ""
+
+#: ../../dev.rst:348
+# b20bb6dcdfa0405495e11fa07c1911a4
+msgid "To control the API request rate, use the following global configuration settings:"
+msgstr ""
+
+#: ../../dev.rst:353
+# 93448fd2551e4687864f59929f698391
+msgid "`api.throttling.enabled` - Enable/Disable API throttling. By default, this setting is false, so API throttling is not enabled."
+msgstr ""
+
+#: ../../dev.rst:358
+# d92963ed9fdc414199763fb36436dabf
+msgid "`api.throttling.interval` (in seconds) - Time interval during which the number of API requests is to be counted. When the interval has passed, the API count is reset to 0."
+msgstr ""
+
+#: ../../dev.rst:364
+# e226e0fe5d9f4905a28c7b087de7867f
+msgid "`api.throttling.max` - Maximum number of APIs that can be placed within the `api.throttling.interval` period."
+msgstr ""
+
+#: ../../dev.rst:369
+# ef2be420b80540f3a805c54f6308d99b
+msgid "`api.throttling.cachesize` - Cache size for storing API counters. Use a value higher than the total number of accounts managed by the cloud. One cache entry is needed for each account, to store the running API total for that account."
+msgstr ""
+
+#: ../../dev.rst:375
+# 57cca97fd0c641a28479d2225b0aed15
+msgid "Limitations on API Throttling"
+msgstr ""
+
+#: ../../dev.rst:377
+# 20ee349cff1142938abd48470a0ac379
+msgid "The following limitations exist in the current implementation of this feature."
+msgstr ""
+
+#: ../../dev.rst:380
+# 2d10220a408149aeaf19331f5fa06f93
+msgid "Even with these limitations, CloudStack is still able to effectively use"
+msgstr ""
+
+#: ../../dev.rst:381
+# 6f2e12e0cf55408ea86a8c65d298202a
+msgid "API throttling to avoid malicious attacks causing denial of service."
+msgstr ""
+
+#: ../../dev.rst:386
+# f0469961f74243e887c7e7b93b00b36d
+msgid "In a deployment with multiple Management Servers, the cache is not synchronized across them. In this case, CloudStack might not be able to ensure that only the exact desired number of API requests are allowed. In the worst case, the number of API calls that might be allowed is (number of Management Servers) \\* (api.throttling.max)."
+msgstr ""
+
+#: ../../dev.rst:394
+# a45bc58c314d41a3bc4016b34304248c
+msgid "The API commands resetApiLimit and getApiLimit are limited to the Management Server where the API is invoked."
+msgstr ""
+
+#: ../../dev.rst:398
+# ff3c016220c6457a8c596adbe284cb4e
+msgid "API Responses"
+msgstr ""
+
+#: ../../dev.rst:401
+# 15968f1e84944fb2abdb573b78b32727
+msgid "Response Formats: XML and JSON"
+msgstr ""
+
+#: ../../dev.rst:403
+# 9efb63e9197e421d94628f73f0cb03ac
+msgid "CloudStack supports two formats as the response to an API call. The default response is XML. If you would like the response to be in JSON, add `&response=json` to the Command String."
+msgstr ""
+
+#: ../../dev.rst:407
+# 177028ee76cd4d94b66b45d6ef644cb1
+msgid "The two response formats differ in how they handle blank fields. In JSON, if there is no value for a response field, it will not appear in the response. If all the fields were empty, there might be no response at all. In XML, even if there is no value to be returned, an empty field will be returned as a placeholder XML element."
+msgstr ""
+
+#: ../../dev.rst:413
+# 824259cd2e9a405598c12835bb76ecb8
+msgid "Sample XML Response:"
+msgstr ""
+
+#: ../../dev.rst:427
+# 97dd89cd0fee43c6a3cae91abccb2b78
+msgid "Sample JSON Response:"
+msgstr ""
+
+#: ../../dev.rst:446
+# 58212032f7154c1883e84432d8e4d731
+msgid "Maximum Result Pages Returned"
+msgstr ""
+
+#: ../../dev.rst:448
+# 7f37d69d4d574e64a9a8ab88ef46a41d
+msgid "For each cloud, there is a default upper limit on the number of results that any API command will return in a single page. This is to help prevent overloading the cloud servers and prevent DOS attacks. For example, if the page size limit is 500 and a command returns 10,000 results, the command will return 20 pages."
+msgstr ""
+
+#: ../../dev.rst:454
+# efbf23a9cd034a62ab0615e69055eca7
+msgid "The default page size limit can be different for each cloud. It is set in the global configuration parameter `default.page.size`. If your cloud has many users with lots of VMs, you might need to increase the value of this parameter. At the same time, be careful not to set it so high that your site can be taken down by an enormous return from an API call. For more information about how to set global configuration parameters, see \"Describe Your Deployment\" in the Installation Guide."
+msgstr ""
+
+#: ../../dev.rst:462
+# 0265adcbb3e04c42ad6b93eba4793e37
+msgid "To decrease the page size limit for an individual API command, override the global setting with the page and pagesize parameters, which are available in any list\\* command (listCapabilities, listDiskOfferings, etc.)."
+msgstr ""
+
+#: ../../dev.rst:469
+# 85f5e1e695134081a55593c632d76fd3
+msgid "Both parameters must be specified together."
+msgstr ""
+
+#: ../../dev.rst:473
+# a1d697103c2d4059b7ce8e1ee7f22d46
+msgid "The value of the pagesize parameter must be smaller than the value of default.page.size. That is, you can not increase the number of possible items in a result page, only decrease it."
+msgstr ""
+
+#: ../../dev.rst:477
+# d6ed74d6611848a290eb5fb93eee5c6f
+msgid "For syntax information on the list\\* commands, see the API Reference."
+msgstr ""
+
+#: ../../dev.rst:480
+# 5bcdc2f0b4454ad1ac6b3733f52eac9b
+msgid "Error Handling"
+msgstr ""
+
+#: ../../dev.rst:482
+# 916ce269074b4dbb8c87b25f9013d681
+msgid "If an error occurs while processing an API request, the appropriate response in the format specified is returned. Each error response consists of an error code and an error text describing what possibly can go wrong. Below is a list of possible error codes:"
+msgstr ""
+
+#: ../../dev.rst:487
+# 66c32999ce2a406ba8eb54f875480eb3
+msgid "You can now find the CloudStack-specific error code in the exception response for each type of exception. The following list of error codes is added to the new class named CSExceptionErrorCode."
+msgstr ""
+
+#: ../../dev.rst:491
+# ccebf00b44ad4eb3a4215373acb07b44
+msgid "4250 : \"com.cloud.utils.exception.CloudRuntimeException\""
+msgstr ""
+
+#: ../../dev.rst:493
+# ed256ade3d414e38979e51608aa2801d
+msgid "4255 : \"com.cloud.utils.exception.ExceptionUtil\""
+msgstr ""
+
+#: ../../dev.rst:495
+# ed0d3d0b1d4b49ae85d70de2ad5d7e62
+msgid "4260 : \"com.cloud.utils.exception.ExecutionException\""
+msgstr ""
+
+#: ../../dev.rst:497
+# 11dbbbbb5d9e467484d307bccb64880d
+msgid "4265 : \"com.cloud.utils.exception.HypervisorVersionChangedException\""
+msgstr ""
+
+#: ../../dev.rst:499
+# 55e75631973241099121d893bfa860cd
+msgid "4270 : \"com.cloud.utils.exception.RuntimeCloudException\""
+msgstr ""
+
+#: ../../dev.rst:501
+# 65da6007d7254cb289c2091ee83ab2d7
+msgid "4275 : \"com.cloud.exception.CloudException\""
+msgstr ""
+
+#: ../../dev.rst:503
+# f131941c3b794e56978128a95bc282fc
+msgid "4280 : \"com.cloud.exception.AccountLimitException\""
+msgstr ""
+
+#: ../../dev.rst:505
+# 4e613b7caeb94249a8a341b3b9074a88
+msgid "4285 : \"com.cloud.exception.AgentUnavailableException\""
+msgstr ""
+
+#: ../../dev.rst:507
+# e9df4f85e8ad4785a8e557c376fdf043
+msgid "4290 : \"com.cloud.exception.CloudAuthenticationException\""
+msgstr ""
+
+#: ../../dev.rst:509
+# 4504f51121f74de0a8639ffcfc17e0c9
+msgid "4295 : \"com.cloud.exception.CloudExecutionException\""
+msgstr ""
+
+#: ../../dev.rst:511
+# 265aea8998a24d649fa88365c8bd2f15
+msgid "4300 : \"com.cloud.exception.ConcurrentOperationException\""
+msgstr ""
+
+#: ../../dev.rst:513
+# e2d91e1ac20a4cadaa1b971c4c7ff3fe
+msgid "4305 : \"com.cloud.exception.ConflictingNetworkSettingsException\""
+msgstr ""
+
+#: ../../dev.rst:515
+# 9421e3203b5b4e1c847bffbbf5a9bbe4
+msgid "4310 : \"com.cloud.exception.DiscoveredWithErrorException\""
+msgstr ""
+
+#: ../../dev.rst:517
+# bed8f76dc0cf41d387694eeda72d4365
+msgid "4315 : \"com.cloud.exception.HAStateException\""
+msgstr ""
+
+#: ../../dev.rst:519
+# 3d66fe1fbad84905a0267f4c81df270a
+msgid "4320 : \"com.cloud.exception.InsufficientAddressCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:521
+# 762132c12835488abe023b285ddaaaf0
+msgid "4325 : \"com.cloud.exception.InsufficientCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:523
+# ca329206e01944308f28c189618e1ca5
+msgid "4330 : \"com.cloud.exception.InsufficientNetworkCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:525
+# 842cd2cceb2f4beead8fba9b3ff8eb16
+msgid "4335 : \"com.cloud.exception.InsufficientServerCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:527
+# 0436b78cc6ef458992b9308f1c35e12c
+msgid "4340 : \"com.cloud.exception.InsufficientStorageCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:529
+# 57175a79979a460d86c7c40cee15441c
+msgid "4345 : \"com.cloud.exception.InternalErrorException\""
+msgstr ""
+
+#: ../../dev.rst:531
+# 99c3e63e69d941368c3b155918669905
+msgid "4350 : \"com.cloud.exception.InvalidParameterValueException\""
+msgstr ""
+
+#: ../../dev.rst:533
+# fa28472261294bc39d5a70a149f7ad11
+msgid "4355 : \"com.cloud.exception.ManagementServerException\""
+msgstr ""
+
+#: ../../dev.rst:535
+# a3deb030592844e5a9cd5bcd4f04ae31
+msgid "4360 : \"com.cloud.exception.NetworkRuleConflictException\""
+msgstr ""
+
+#: ../../dev.rst:537
+# fa6bfc0a9f894c3a99ff80b18ac8eed4
+msgid "4365 : \"com.cloud.exception.PermissionDeniedException\""
+msgstr ""
+
+#: ../../dev.rst:539
+# 9c9b5d4e5be2488691ec292bbf274c44
+msgid "4370 : \"com.cloud.exception.ResourceAllocationException\""
+msgstr ""
+
+#: ../../dev.rst:541
+# a6bd0b470fb347df81cd0c05972ffdf5
+msgid "4375 : \"com.cloud.exception.ResourceInUseException\""
+msgstr ""
+
+#: ../../dev.rst:543
+# 9a964f1cede94d71a70f71335abdb3c4
+msgid "4380 : \"com.cloud.exception.ResourceUnavailableException\""
+msgstr ""
+
+#: ../../dev.rst:545
+# 6651d4a6e3934a62acfdabcb4cb54861
+msgid "4385 : \"com.cloud.exception.StorageUnavailableException\""
+msgstr ""
+
+#: ../../dev.rst:547
+# 7b33be0641984ca4a244e4e72ecc25ee
+msgid "4390 : \"com.cloud.exception.UnsupportedServiceException\""
+msgstr ""
+
+#: ../../dev.rst:549
+# cc42b4fc26144e9591c1994a14433387
+msgid "4395 : \"com.cloud.exception.VirtualMachineMigrationException\""
+msgstr ""
+
+#: ../../dev.rst:551
+# d1b52de5031041a49c255578c83d3066
+msgid "4400 : \"com.cloud.exception.AccountLimitException\""
+msgstr ""
+
+#: ../../dev.rst:553
+# 62c4d7f5e4c4497085dd6408ed374de8
+msgid "4405 : \"com.cloud.exception.AgentUnavailableException\""
+msgstr ""
+
+#: ../../dev.rst:555
+# 8a8742dbe79a4f4f9cc57806a91dd668
+msgid "4410 : \"com.cloud.exception.CloudAuthenticationException\""
+msgstr ""
+
+#: ../../dev.rst:557
+# e6bc37bad0c24deeb12e990e5d2d9846
+msgid "4415 : \"com.cloud.exception.CloudException\""
+msgstr ""
+
+#: ../../dev.rst:559
+# 29bdcde3a3824b758d135a6556a23400
+msgid "4420 : \"com.cloud.exception.CloudExecutionException\""
+msgstr ""
+
+#: ../../dev.rst:561
+# 4026eb49a4b84d2abca965c0a9fba59d
+msgid "4425 : \"com.cloud.exception.ConcurrentOperationException\""
+msgstr ""
+
+#: ../../dev.rst:563
+# 79ca0947ecda4b5bb1a7bfe6daf43fb9
+msgid "4430 : \"com.cloud.exception.ConflictingNetworkSettingsException\""
+msgstr ""
+
+#: ../../dev.rst:565
+# 687ea642c68f42ba98a5db0263593ac2
+msgid "4435 : \"com.cloud.exception.ConnectionException\""
+msgstr ""
+
+#: ../../dev.rst:567
+# 8a6eafd640a04650ba06e78b3d1d0fb7
+msgid "4440 : \"com.cloud.exception.DiscoveredWithErrorException\""
+msgstr ""
+
+#: ../../dev.rst:569
+# 444014c160aa4020887cfa88de787f72
+msgid "4445 : \"com.cloud.exception.DiscoveryException\""
+msgstr ""
+
+#: ../../dev.rst:571
+# 99f689ad42894544b243accb4ce0575f
+msgid "4450 : \"com.cloud.exception.HAStateException\""
+msgstr ""
+
+#: ../../dev.rst:573
+# c70428b1eaf6453fa93427732c5084fb
+msgid "4455 : \"com.cloud.exception.InsufficientAddressCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:575
+# df47d21577f843c7a08f97fe35c4b2ba
+msgid "4460 : \"com.cloud.exception.InsufficientCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:577
+# 55edef8ad41a404e82248b1a84037b8f
+msgid "4465 : \"com.cloud.exception.InsufficientNetworkCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:579
+# ff2df775bee341c1a76830cea07f961e
+msgid "4470 : \"com.cloud.exception.InsufficientServerCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:581
+# e67dd04cf5a54cb38a565390d3826d6d
+msgid "4475 : \"com.cloud.exception.InsufficientStorageCapacityException\""
+msgstr ""
+
+#: ../../dev.rst:583
+# b9d6b1ef0f3d452eaef2b46177152cf6
+msgid "4480 : \"com.cloud.exception.InsufficientVirtualNetworkCapcityException\""
+msgstr ""
+
+#: ../../dev.rst:585
+# 3cbb6383b39f44e2b85fbb4254bf68bb
+msgid "4485 : \"com.cloud.exception.InternalErrorException\""
+msgstr ""
+
+#: ../../dev.rst:587
+# 67b8b777ef2040478db5c426e0b2f3a4
+msgid "4490 : \"com.cloud.exception.InvalidParameterValueException\""
+msgstr ""
+
+#: ../../dev.rst:589
+# dca641bdb0584421b4b791107452c489
+msgid "4495 : \"com.cloud.exception.ManagementServerException\""
+msgstr ""
+
+#: ../../dev.rst:591
+# 8f1377661f654d838990891fcae375b0
+msgid "4500 : \"com.cloud.exception.NetworkRuleConflictException\""
+msgstr ""
+
+#: ../../dev.rst:593
+# 3082fbc9cb744b37927d3b3e86431091
+msgid "4505 : \"com.cloud.exception.PermissionDeniedException\""
+msgstr ""
+
+#: ../../dev.rst:595
+# ae210e7072ee49f7bf0ac85d099851e5
+msgid "4510 : \"com.cloud.exception.ResourceAllocationException\""
+msgstr ""
+
+#: ../../dev.rst:597
+# 7497da0b15ca4f64a1ce434ccf1099b8
+msgid "4515 : \"com.cloud.exception.ResourceInUseException\""
+msgstr ""
+
+#: ../../dev.rst:599
+# 8efb71e351de4403a66a04382f40a873
+msgid "4520 : \"com.cloud.exception.ResourceUnavailableException\""
+msgstr ""
+
+#: ../../dev.rst:601
+# 811f5d8995f54d72a2fa1c09d0720bc7
+msgid "4525 : \"com.cloud.exception.StorageUnavailableException\""
+msgstr ""
+
+#: ../../dev.rst:603
+# 7dd4324f99194117890076e5bab85c37
+msgid "4530 : \"com.cloud.exception.UnsupportedServiceException\""
+msgstr ""
+
+#: ../../dev.rst:605
+# 1a6ba33177d5419c9d3feed1f6ab0aca
+msgid "4535 : \"com.cloud.exception.VirtualMachineMigrationException\""
+msgstr ""
+
+#: ../../dev.rst:607
+# 8eefebfb00ee405abce8f9a00d2ce812
+msgid "9999 : \"org.apache.cloudstack.api.ServerApiException\""
+msgstr ""
+
+#: ../../dev.rst:609
+# 5318790ebacb45cb81706d1aa5b0ec4b
+msgid "An HTTP error code of 401 is always returned if API request was rejected due to bad signatures, missing API Keys, or the user simply did not have the permissions to execute the command."
+msgstr ""
+
+#: ../../dev.rst:614
+# b084cf11fe95484aa67688b00c8361b8
+msgid "Asynchronous Commands"
+msgstr ""
+
+#: ../../dev.rst:616
+# 8704f9a4fde4479ebca7b958ee9ea9fa
+msgid "Asynchronous commands were introduced in CloudStack 2.x. Commands are designated as asynchronous when they can potentially take a long period of time to complete such as creating a snapshot or disk volume. They differ from synchronous commands by the following:"
+msgstr ""
+
+#: ../../dev.rst:623
+# 17dd9ece69d74a08af583815c6938a2b
+msgid "They are identified in the API Reference by an (A)."
+msgstr ""
+
+#: ../../dev.rst:627
+# faf96453a5d9414f93cd2ceec901d1b3
+msgid "They will immediately return a job ID to refer to the job that will be responsible in processing the command."
+msgstr ""
+
+#: ../../dev.rst:632
+# 3567f44c20fd40fabaa906479c1ea490
+msgid "If executed as a \"create\" resource command, it will return the resource ID as well as the job ID."
+msgstr ""
+
+#: ../../dev.rst:635
+# cb1f99a392db43a990c7eb63bc00e600
+msgid "You can periodically check the status of the job by making a simple API call to the command, `queryAsyncJobResult` and passing in the job ID."
+msgstr ""
+
+#: ../../dev.rst:640
+# db2db81abce24e009335f15e6c0db86f
+msgid "Job Status"
+msgstr ""
+
+#: ../../dev.rst:642
+# 7fe5da2e577b4ecaa7d1e16cb76d3117
+msgid "The key to using an asynchronous command is the job ID that is returned immediately once the command has been executed. With the job ID, you can periodically check the job status by making calls to queryAsyncJobResult command. The command will return three possible job status integer values:"
+msgstr ""
+
+#: ../../dev.rst:650
+# 2ede3d8a734b40d691b99e058ef4c94c
+msgid "0 - Job is still in progress. Continue to periodically poll for any status changes."
+msgstr ""
+
+#: ../../dev.rst:655
+# 64e0214bb67c4717b6b3c18109d38f0d
+msgid "1 - Job has successfully completed. The job will return any successful response values associated with command that was originally executed."
+msgstr ""
+
+#: ../../dev.rst:661
+# c35e1393c870448fb9ab896f0ff1e7eb
+msgid "2 - Job has failed to complete. Please check the \"jobresultcode\" tag for failure reason code and \"jobresult\" for the failure reason."
+msgstr ""
+
+#: ../../dev.rst:665
+# 3667e152b1f1432fbd13a0805138b39f
+msgid "Example"
+msgstr ""
+
+#: ../../dev.rst:667
+# b86f8fe120ea4e979bd0f140876f85cc
+msgid "The following shows an example of using an asynchronous command. Assume the API command:"
+msgstr ""
+
+#: ../../dev.rst:674
+# f2282484364642e197b91d6a86328513
+msgid "CloudStack will immediately return a job ID and any other additional data."
+msgstr ""
+
+#: ../../dev.rst:684
+# 335a315726c743f4898691c4e3f1ac78
+msgid "Using the job ID, you can periodically poll for the results by using the queryAsyncJobResult command."
+msgstr ""
+
+#: ../../dev.rst:691
+# 3c14ddbd950048a0a91b9e3883c711ff
+msgid "Three possible results could come from this query."
+msgstr ""
+
+#: ../../dev.rst:693
+# ab8d636b7eee440199c9d60d4c319d16
+msgid "Job is still pending:"
+msgstr ""
+
+#: ../../dev.rst:703
+# 3f89d22e928242f88bcc14721c7323f3
+msgid "Job has succeeded:"
+msgstr ""
+
+#: ../../dev.rst:757
+# cd3a69591de442d0bf5f0d300459402d
+msgid "Job has failed:"
+msgstr ""
+
+#: ../../dev.rst:772
+# 4fd111a3a74b4dc38f376af537acdb93
+msgid "Event Types"
+msgstr ""
+
+#: ../../dev.rst:775
+# 477d5dc73bfe41ad9c7eda2987ac5e85
+msgid "Types"
+msgstr ""
+
+#: ../../dev.rst:775
+# fa4d32c97cf544f9b3cf3f47187c6155
+msgid "Events"
+msgstr ""
+
+#: ../../dev.rst:777
+# 2ff2614b2a7b42488d9a425b1803b899
+msgid "VM"
+msgstr ""
+
+#: ../../dev.rst:777
+# 087b18b695a14ce98e9f093181181a80
+msgid "VM.CREATE"
+msgstr ""
+
+#: ../../dev.rst:779
+# 14dece28da0f4b12b4ebee77a028b033
+msgid "VM.DESTROY"
+msgstr ""
+
+#: ../../dev.rst:781
+# c2dcbb7f0ff74f3ab392f306338c5a7c
+msgid "VM.START"
+msgstr ""
+
+#: ../../dev.rst:783
+# 1da7e95ff42941d79420631065b78e36
+msgid "VM.STOP"
+msgstr ""
+
+#: ../../dev.rst:785
+# 21d3b2775cdf4f1d8d95b8a6091c29af
+msgid "VM.REBOOT"
+msgstr ""
+
+#: ../../dev.rst:787
+# 99de318cd5794f7b812164f36c9b41d0
+msgid "VM.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:789
+# a84b920924934dd88d9e6a382cc76748
+msgid "VM.UPGRADE"
+msgstr ""
+
+#: ../../dev.rst:791
+# ef5fd09876944c13bf2089f20759f460
+msgid "VM.DYNAMIC.SCALE"
+msgstr ""
+
+#: ../../dev.rst:793
+# 98d863622caa45cabc5e91577c9af8f2
+msgid "VM.RESETPASSWORD"
+msgstr ""
+
+#: ../../dev.rst:795
+# 9a2ca792849c47ddbb2e1fe34bf96718
+msgid "VM.RESETSSHKEY"
+msgstr ""
+
+#: ../../dev.rst:797
+# 7fe6dddc53d74a458c7b06b548bbb0ab
+msgid "VM.MIGRATE"
+msgstr ""
+
+#: ../../dev.rst:799
+# f5bb29d40e5942e49a4f38bd8bc947a6
+msgid "VM.MOVE"
+msgstr ""
+
+#: ../../dev.rst:801
+# 1cf27c3b2adf4078b1bed7b82f6b1754
+msgid "VM.RESTORE"
+msgstr ""
+
+#: ../../dev.rst:803
+# 6cc42b9032264e4aa02b906b78e308a6
+msgid "Domain Router"
+msgstr ""
+
+#: ../../dev.rst:803
+# b5bf7240eb1848bf929535a8ce5e45d1
+msgid "ROUTER.CREATE"
+msgstr ""
+
+#: ../../dev.rst:805
+# e170804cd908478f88cabdbca054d215
+msgid "ROUTER.DESTROY"
+msgstr ""
+
+#: ../../dev.rst:807
+# 4ed310f34c2547f68c21efc7c7dfb3d8
+msgid "ROUTER.START"
+msgstr ""
+
+#: ../../dev.rst:809
+# 8ee01c4eb9b542ad85537c42c720d8b3
+msgid "ROUTER.STOP"
+msgstr ""
+
+#: ../../dev.rst:811
+# 620890a493944dd183ee1edbe2356449
+msgid "ROUTER.REBOOT"
+msgstr ""
+
+#: ../../dev.rst:813
+# 64f00d974f9d46c1a43ffce7cfc00d07
+msgid "ROUTER.HA"
+msgstr ""
+
+#: ../../dev.rst:815
+# b8c151857e26407ba93493cdce5d0cab
+msgid "ROUTER.UPGRADE"
+msgstr ""
+
+#: ../../dev.rst:817
+# a8772cc955ca464488f7d6de1d1e0d41
+msgid "Console proxy"
+msgstr ""
+
+#: ../../dev.rst:817
+# db641bb0472546a5883f7ea1b0c3b1f2
+msgid "PROXY.CREATE"
+msgstr ""
+
+#: ../../dev.rst:819
+# 534375819956448dbcfb6f8c17e2e77b
+msgid "PROXY.DESTROY"
+msgstr ""
+
+#: ../../dev.rst:821
+# 6cf282d189704578820f8b28fa73ebbc
+msgid "PROXY.START"
+msgstr ""
+
+#: ../../dev.rst:823
+# 8634f9c421e64dbfb4106108e59aa3eb
+msgid "PROXY.STOP"
+msgstr ""
+
+#: ../../dev.rst:825
+# ae0139513aa74deaa2d6533b357b55b0
+msgid "PROXY.REBOOT"
+msgstr ""
+
+#: ../../dev.rst:827
+# 3729e7afd0224ed3b105aebc7750df28
+msgid "PROXY.HA"
+msgstr ""
+
+#: ../../dev.rst:829
+# 03afd42a6ff24a45bc315f2a514eb9c5
+msgid "VNC Console Events"
+msgstr ""
+
+#: ../../dev.rst:829
+# ea07e9e5008446a7b7f08e25faf8a0cb
+msgid "VNC.CONNECT"
+msgstr ""
+
+#: ../../dev.rst:831
+# 0e78144836de4034ae415843728c6cac
+msgid "VNC.DISCONNECT"
+msgstr ""
+
+#: ../../dev.rst:833
+# b4e9ed895d6f44aaa84461bc939dbfc2
+msgid "Network Events"
+msgstr ""
+
+#: ../../dev.rst:833
+# e32578c6790e4694a736931b06b7ff38
+msgid "NET.IPASSIGN"
+msgstr ""
+
+#: ../../dev.rst:835
+# 66e20530b70b480e9e08a4727320b69e
+msgid "NET.IPRELEASE"
+msgstr ""
+
+#: ../../dev.rst:837
+# edd59ba63ff5451aa0c5668101c6d3c1
+msgid "PORTABLE.IPASSIGN"
+msgstr ""
+
+#: ../../dev.rst:839
+# 3fbfe209784043f1bb38ca9a42e17d72
+msgid "PORTABLE.IPRELEASE"
+msgstr ""
+
+#: ../../dev.rst:841
+# dd097f8a6e10461cb34b90d4587fbbc9
+msgid "NET.RULEADD"
+msgstr ""
+
+#: ../../dev.rst:843
+# 7abbc44cd8c94daeaaa8e243967ebb86
+msgid "NET.RULEDELETE"
+msgstr ""
+
+#: ../../dev.rst:845
+# 8b6decb3262a43a4a90b330d68c3913e
+msgid "NET.RULEMODIFY"
+msgstr ""
+
+#: ../../dev.rst:847
+# 1ef01bed0801421596a29a58d7e1d868
+msgid "NETWORK.CREATE"
+msgstr ""
+
+#: ../../dev.rst:849
+# 5fa56b58104442028954e0ddd1c67caf
+msgid "NETWORK.DELETE"
+msgstr ""
+
+#: ../../dev.rst:851
+# 57ebc3932bea4adb9f234f0f901937dc
+msgid "NETWORK.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:853
+# 56b89fb2707e4da9949d6052d3ad61f3
+msgid "FIREWALL.OPEN"
+msgstr ""
+
+#: ../../dev.rst:855
+# afb1aacc89014c62bb0ade25fe8e0915
+msgid "FIREWALL.CLOSE"
+msgstr ""
+
+#: ../../dev.rst:857
+# 973a258897ba41a7a0ad1ab2aca396ce
+msgid "NIC Events"
+msgstr ""
+
+#: ../../dev.rst:857
+# d2804a9e8a0b42208bcb06eb85ad66ea
+msgid "NIC.CREATE"
+msgstr ""
+
+#: ../../dev.rst:859
+# 47bb842256964eaa80aa949409ac2528
+msgid "NIC.DELETE"
+msgstr ""
+
+#: ../../dev.rst:861
+# f13c5ecd11584efbbfb32d2a5fc7060f
+msgid "NIC.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:863
+# 7ef0554c83ba4b0ba7f7a8dad3102914
+msgid "NIC.DETAIL.ADD"
+msgstr ""
+
+#: ../../dev.rst:865
+# c31611b4c4fa481886c165977ec2c1da
+msgid "NIC.DETAIL.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:867
+# dcb91cb2687d4a168a875c38d674eabc
+msgid "NIC.DETAIL.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:869
+# 2fb546bc324249b3895856f3949ff5b0
+msgid "Load Balancers"
+msgstr ""
+
+#: ../../dev.rst:869
+# c1726be0d0774ac6aa26a79118127d5c
+msgid "LB.ASSIGN.TO.RULE"
+msgstr ""
+
+#: ../../dev.rst:871
+# 09da0eaa1af146e38148140c2efd9a9a
+msgid "LB.REMOVE.FROM.RULE"
+msgstr ""
+
+#: ../../dev.rst:873
+# 635428fd7a664b51a8ebea428855ce66
+msgid "LB.CREATE"
+msgstr ""
+
+#: ../../dev.rst:875
+# 7a4a8b841e0341e7a22243fe6c6e1dcd
+msgid "LB.DELETE"
+msgstr ""
+
+#: ../../dev.rst:877
+# ee971ca17057454f97e33187982f550b
+msgid "LB.STICKINESSPOLICY.CREATE"
+msgstr ""
+
+#: ../../dev.rst:879
+# c2393b5d398b49bc85f1866098a4a4fc
+msgid "LB.STICKINESSPOLICY.DELETE"
+msgstr ""
+
+#: ../../dev.rst:881
+# 35260a926bd14945934522a2b2d715a2
+msgid "LB.HEALTHCHECKPOLICY.CREATE"
+msgstr ""
+
+#: ../../dev.rst:883
+# b92f67d67c15428b9a147f11698da158
+msgid "LB.HEALTHCHECKPOLICY.DELETE"
+msgstr ""
+
+#: ../../dev.rst:885
+# 003d3810251843e9b4c82fe606be43af
+msgid "LB.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:887
+# 464a1cde83014f9aa3faa7c99d77625c
+msgid "Global Load Balancer rules"
+msgstr ""
+
+#: ../../dev.rst:887
+# 41b26bff91d84bb2b2139d7fdc9d33eb
+msgid "GLOBAL.LB.ASSIGN"
+msgstr ""
+
+#: ../../dev.rst:889
+# 3ac45158cb2d4912a974f0984fa0a7fa
+msgid "GLOBAL.LB.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:891
+# c9427518c3d34703b95f6eb252443f6d
+msgid "GLOBAL.LB.CREATE"
+msgstr ""
+
+#: ../../dev.rst:893
+# 72e796805a5645538a36c5f8cffd203e
+msgid "GLOBAL.LB.DELETE"
+msgstr ""
+
+#: ../../dev.rst:895
+# e64dd258f032416fa873cc2ec7168c6a
+msgid "GLOBAL.LB.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:897
+# f159d834b1164c2aa3271730dffe0969
+msgid "Account events"
+msgstr ""
+
+#: ../../dev.rst:897
+# c03a996579ca498db0ab5dbaa26de6e0
+msgid "ACCOUNT.ENABLE"
+msgstr ""
+
+#: ../../dev.rst:899
+# 9abced699c07425985b4e3f50a1e82b9
+msgid "ACCOUNT.DISABLE"
+msgstr ""
+
+#: ../../dev.rst:901
+# af40529a74fb4d3e948e336013107e2f
+msgid "ACCOUNT.CREATE"
+msgstr ""
+
+#: ../../dev.rst:903
+# 804d0b3521ee4d3f9f359a9ffa6dedf2
+msgid "ACCOUNT.DELETE"
+msgstr ""
+
+#: ../../dev.rst:905
+# d9324c6675a34f07ada12c83bd90f259
+msgid "ACCOUNT.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:907
+# 1584515abe07488d9c1ebe76f4c3f83e
+msgid "ACCOUNT.MARK.DEFAULT.ZONE"
+msgstr ""
+
+#: ../../dev.rst:909
+# 89003da38b5a421dbf2a50717bf3065e
+msgid "UserVO Events"
+msgstr ""
+
+#: ../../dev.rst:909
+# 3b342997f3dd496e9d5bcca934120251
+msgid "USER.LOGIN"
+msgstr ""
+
+#: ../../dev.rst:911
+# 067db23da7124ada888755206590e575
+msgid "USER.LOGOUT"
+msgstr ""
+
+#: ../../dev.rst:913
+# 9b29d8a91f944c829e1f2acff5f63b14
+msgid "USER.CREATE"
+msgstr ""
+
+#: ../../dev.rst:915
+# eafa3a5913e347b8b7f87c3079d872b0
+msgid "USER.DELETE"
+msgstr ""
+
+#: ../../dev.rst:917
+# c3d626a3dac14a278faf60b7889da651
+msgid "USER.DISABLE"
+msgstr ""
+
+#: ../../dev.rst:919
+# 444fc2dd12ef42459abd494142a50ade
+msgid "USER.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:921
+# 31a1e444fc424f96a39d6cf61c195a7c
+msgid "USER.ENABLE"
+msgstr ""
+
+#: ../../dev.rst:923
+# be704e9963a045d588fbafd11b8ef0b7
+msgid "USER.LOCK"
+msgstr ""
+
+#: ../../dev.rst:925
+# ff939cdbfb174e6ba2f38a79e93597f2
+msgid "Registering SSH keypair events"
+msgstr ""
+
+#: ../../dev.rst:925
+# 56dac4f833b842a1a18c48bba6352e8d
+msgid "REGISTER.SSH.KEYPAIR"
+msgstr ""
+
+#: ../../dev.rst:928
+# 69f8bb424fb34ee2a1983188fbe1691d
+msgid "Register for user API and secret keys"
+msgstr ""
+
+#: ../../dev.rst:928
+# 0c115305735e44bfb98342afa46588b4
+msgid "REGISTER.USER.KEY"
+msgstr ""
+
+#: ../../dev.rst:932
+# 1c7d40a0c63d4c61a21abee9c4205ba6
+msgid "Template Events"
+msgstr ""
+
+#: ../../dev.rst:932
+# 4a7c0eb790ae40eba4c6f49ef416c9da
+msgid "TEMPLATE.CREATE"
+msgstr ""
+
+#: ../../dev.rst:934
+# cf5d7b4f4e9540cf8f7c789ff4ee300b
+msgid "TEMPLATE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:936
+# 9c493c95524a4533a143f55ab04c28fb
+msgid "TEMPLATE.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:938
+# c873bf23024543159c8e93721961609a
+msgid "TEMPLATE.DOWNLOAD.START"
+msgstr ""
+
+#: ../../dev.rst:940
+# c2b7dd18c6264c00b019556150d2cd37
+msgid "TEMPLATE.DOWNLOAD.SUCCESS"
+msgstr ""
+
+#: ../../dev.rst:942
+# 695a7ce33a55441b8b8800a31e587187
+msgid "TEMPLATE.DOWNLOAD.FAILED"
+msgstr ""
+
+#: ../../dev.rst:944
+# efc5f38eedd04ebb8831f86502ae9766
+msgid "TEMPLATE.COPY"
+msgstr ""
+
+#: ../../dev.rst:946
+# 237c07b2d3494deeacae4fdde5355af8
+msgid "TEMPLATE.EXTRACT"
+msgstr ""
+
+#: ../../dev.rst:948
+# e97449a8070047b7a1524bcdc3576164
+msgid "TEMPLATE.UPLOAD"
+msgstr ""
+
+#: ../../dev.rst:950
+# b50c3621c3684513963429cbff9d44a7
+msgid "TEMPLATE.CLEANUP"
+msgstr ""
+
+#: ../../dev.rst:952
+# 31af437baa534384a6122a8688bfad52
+msgid "Volume Events"
+msgstr ""
+
+#: ../../dev.rst:952
+# d98424bf1fcc48da8f4bf407bf8a37c4
+msgid "VOLUME.CREATE"
+msgstr ""
+
+#: ../../dev.rst:954
+# 1e8ca3f13cfd4e578bf8e4abc22a9349
+msgid "VOLUME.DELETE"
+msgstr ""
+
+#: ../../dev.rst:956
+# 711ca9115b574945b76811a3c54194d8
+msgid "VOLUME.ATTACH"
+msgstr ""
+
+#: ../../dev.rst:958
+# dfda68fbc1554ff4917635954f2c3117
+msgid "VOLUME.DETACH"
+msgstr ""
+
+#: ../../dev.rst:960
+# 2aae2a6617a84bf8afcbacb113bc9964
+msgid "VOLUME.EXTRACT"
+msgstr ""
+
+#: ../../dev.rst:962
+# c504b0688f854062820da9e1fbc4497e
+msgid "VOLUME.UPLOAD"
+msgstr ""
+
+#: ../../dev.rst:964
+# 9063bcc457a64df6a241822a9b054efd
+msgid "VOLUME.MIGRATE"
+msgstr ""
+
+#: ../../dev.rst:966
+# 2a35d4168abd446abd88441c9568faa9
+msgid "VOLUME.RESIZE"
+msgstr ""
+
+#: ../../dev.rst:968
+# 2297293b53bd4857b4e60b00fefa9d57
+msgid "VOLUME.DETAIL.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:970
+# f05b0f0e1c824577a7364153487eef46
+msgid "VOLUME.DETAIL.ADD"
+msgstr ""
+
+#: ../../dev.rst:972
+# 7cfe6be5841e4fe680c8d1a3836394ba
+msgid "VOLUME.DETAIL.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:974
+# e75a27c6b791458ab493ac0695b482ed
+msgid "Domains"
+msgstr ""
+
+#: ../../dev.rst:974
+# e4dec4a668a341a3be00504a11820dd3
+msgid "DOMAIN.CREATE"
+msgstr ""
+
+#: ../../dev.rst:976
+# f9cb908cc14c434e9daf37a73ecb3edf
+msgid "DOMAIN.DELETE"
+msgstr ""
+
+#: ../../dev.rst:978
+# fa86ece523294cd695a664379793934d
+msgid "DOMAIN.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:980
+# 332b61c96e9b43cda511a1187019b95d
+msgid "Snapshots"
+msgstr ""
+
+#: ../../dev.rst:980
+# a1bdfb5ce327403abf92c4a9fff3dc7a
+msgid "SNAPSHOT.CREATE"
+msgstr ""
+
+#: ../../dev.rst:982
+# 4d1f5d870261420e818d673b4253baa9
+msgid "SNAPSHOT.DELETE"
+msgstr ""
+
+#: ../../dev.rst:984
+# 9391c45700ee4c70a8041819fb3bb61f
+msgid "SNAPSHOTPOLICY.CREATE"
+msgstr ""
+
+#: ../../dev.rst:986
+# 28c24f345f9e492babd8da4788d47a05
+msgid "SNAPSHOTPOLICY.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:988
+# bf31c9b68314463ba99544fd24bdb370
+msgid "SNAPSHOTPOLICY.DELETE"
+msgstr ""
+
+#: ../../dev.rst:990
+# 6e32d7c362fc46eab940c281b50f153a
+msgid "ISO"
+msgstr ""
+
+#: ../../dev.rst:990
+# ce6946bf3c2f4dbfb112b8f4e7ca61b7
+msgid "ISO.CREATE"
+msgstr ""
+
+#: ../../dev.rst:992
+# 375c9e47499e432187e2035ad70b622f
+msgid "ISO.DELETE"
+msgstr ""
+
+#: ../../dev.rst:994
+# d35b4b7ac0844458bf92e4c037c0c35f
+msgid "ISO.COPY"
+msgstr ""
+
+#: ../../dev.rst:996
+# 640bdcedac1d436aaa23a3c74547e67d
+msgid "ISO.ATTACH"
+msgstr ""
+
+#: ../../dev.rst:998
+# 85297a9ad7f244ba926f1a447495f28a
+msgid "ISO.DETACH"
+msgstr ""
+
+#: ../../dev.rst:1000
+# 2e87e726a12b4cfba535cda2c15438af
+msgid "ISO.EXTRACT"
+msgstr ""
+
+#: ../../dev.rst:1002
+# 1105026873ee40e4b9cadef2e98debc6
+msgid "ISO.UPLOAD"
+msgstr ""
+
+#: ../../dev.rst:1004
+# 8fbc8cb673c94a5aa7ed5f4fc68800e5
+msgid "SSVM"
+msgstr ""
+
+#: ../../dev.rst:1004
+# 9e46ea023ded4544902aa174f045d643
+msgid "SSVM.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1006
+# 64b4115f71a448d58999c72cc7bb9a25
+msgid "SSVM.DESTROY"
+msgstr ""
+
+#: ../../dev.rst:1008
+# a93ffcfd9c4741ce8596774daaafe157
+msgid "SSVM.START"
+msgstr ""
+
+#: ../../dev.rst:1010
+# cf0729d95bed4a7ca381547be9cd8d7a
+msgid "SSVM.STOP"
+msgstr ""
+
+#: ../../dev.rst:1012
+# b78e6d90ed5a431981d02081e8ed52d1
+msgid "SSVM.REBOOT"
+msgstr ""
+
+#: ../../dev.rst:1014
+# de758884dcd7492ba8f9d0fffa2b115f
+msgid "SSVM.HA"
+msgstr ""
+
+#: ../../dev.rst:1016
+# ffd6bd7086104744a78972955fdf5b63
+msgid "Service Offerings"
+msgstr ""
+
+#: ../../dev.rst:1016
+# b70fa1e9f97a4d968e140e59ff2efa0c
+msgid "SERVICE.OFFERING.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1018
+# 83cf0b49f2c04f8ca4fcd3714393c8f6
+msgid "SERVICE.OFFERING.EDIT"
+msgstr ""
+
+#: ../../dev.rst:1020
+# 51d961c2c39847ac86a124b58cadef1e
+msgid "SERVICE.OFFERING.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1022
+# 78aa61a6e6104d24b9e8c97eadab6e89
+msgid "Disk Offerings"
+msgstr ""
+
+#: ../../dev.rst:1022
+# 0be7fc96572d47d5a89a14a090506ed9
+msgid "DISK.OFFERING.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1024
+# 0009799f038e4aea882d889e92384af0
+msgid "DISK.OFFERING.EDIT"
+msgstr ""
+
+#: ../../dev.rst:1026
+# ae3e98e623a347b8b73a59f51bee0e68
+msgid "DISK.OFFERING.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1028
+# 6c9be6933b934f11a591770ee201f9e1
+msgid "Network offerings"
+msgstr ""
+
+#: ../../dev.rst:1028
+# da996264ebd54802b0d22dffcdd41238
+msgid "NETWORK.OFFERING.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1030
+# 105e37949f1b4553913a95975659efdc
+msgid "NETWORK.OFFERING.ASSIGN"
+msgstr ""
+
+#: ../../dev.rst:1032
+# ea544f05c05e424d8f41bba4675e3b4b
+msgid "NETWORK.OFFERING.EDIT"
+msgstr ""
+
+#: ../../dev.rst:1034
+# 91a42fe69b794608a089e54d49ef3b91
+msgid "NETWORK.OFFERING.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:1036
+# e0e7111502454f53b6ee3c22661c42c1
+msgid "NETWORK.OFFERING.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1038
+# 0d0bf72de6e4438aac8923733f75b0a5
+msgid "Pods"
+msgstr ""
+
+#: ../../dev.rst:1038
+# ace72761444544f18eceaf727effef84
+msgid "POD.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1040
+# 94c28b64ba2a484fb88157737697b852
+msgid "POD.EDIT"
+msgstr ""
+
+#: ../../dev.rst:1042
+# 6ff8d9286fac49cf808875b23e50f539
+msgid "POD.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1044
+# 1467c66608c14660998c64c30fb1a4c0
+msgid "Zones"
+msgstr ""
+
+#: ../../dev.rst:1044
+# 5c3804942cd341bfb76b5b564e70a91b
+msgid "ZONE.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1046
+# 8fe574fc8629445fabf6651c9639dea8
+msgid "ZONE.EDIT"
+msgstr ""
+
+#: ../../dev.rst:1048
+# e076fd7ad346426fa004e64ccf91e21f
+msgid "ZONE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1050
+# 46c94df1984840e7a714fdba1a10ec82
+msgid "VLANs/IP ranges"
+msgstr ""
+
+#: ../../dev.rst:1050
+# 895d9b6d3d834ed580993209e08c3474
+msgid "VLAN.IP.RANGE.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1052
+# ab95f80c48e24256a5685db3b07f9c5f
+msgid "VLAN.IP.RANGE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1054
+# 63f68eca92f449b6b450026407799c2e
+msgid "VLAN.IP.RANGE.DEDICATE"
+msgstr ""
+
+#: ../../dev.rst:1056
+# 5ed41e8a0f804109800f2485a932ac34
+msgid "VLAN.IP.RANGE.RELEASE"
+msgstr ""
+
+#: ../../dev.rst:1058
+# 2a3a189785c141409c0a77036a394ac2
+msgid "STORAGE.IP.RANGE.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1060
+# 11dee92eaf1b42fb8297f7d3445cdf42
+msgid "STORAGE.IP.RANGE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1062
+# 02cbc1b176bf44fc89fb912aaa842d5b
+msgid "STORAGE.IP.RANGE.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1064
+# c94b4a15b7b3432c85c6dd1a64ec2ba0
+msgid "Configuration Table"
+msgstr ""
+
+#: ../../dev.rst:1064
+# e258aaf5b13942dea329e7a9cb02bc0c
+msgid "CONFIGURATION.VALUE.EDIT"
+msgstr ""
+
+#: ../../dev.rst:1067
+# fa0ab24f4e0646c9be9005eda7e214be
+msgid "Security Groups"
+msgstr ""
+
+#: ../../dev.rst:1067
+# 607a8809376d4e3a9fb5147668ab7f23
+msgid "SG.AUTH.INGRESS"
+msgstr ""
+
+#: ../../dev.rst:1069
+# 9ffbea0b8ee94394b413b8e542ca36a0
+msgid "SG.REVOKE.INGRESS"
+msgstr ""
+
+#: ../../dev.rst:1071
+# 0907ae0daa2a4a97880a33aea22f7ab2
+msgid "SG.AUTH.EGRESS"
+msgstr ""
+
+#: ../../dev.rst:1073
+# 07e432a9c8494d89a35cef7a1284e03b
+msgid "SG.REVOKE.EGRESS"
+msgstr ""
+
+#: ../../dev.rst:1075
+# 54026fb2a6294cf2b0cbd14da8d6246d
+msgid "SG.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1077
+# ff28fa3d071247bd811857b1d6355671
+msgid "SG.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1079
+# e1a67631e2914cbfb2245ebe482488c1
+msgid "SG.ASSIGN"
+msgstr ""
+
+#: ../../dev.rst:1081
+# ef980dd60e0b4ca3aa3c241fe6f1e051
+msgid "SG.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:1083
+# 7c7ab578207e4305918d6bf7c8891671
+msgid "Host"
+msgstr ""
+
+#: ../../dev.rst:1083
+# 67ef96f70e1f43a2a35be93e10a18555
+msgid "HOST.RECONNECT"
+msgstr ""
+
+#: ../../dev.rst:1085
+# 5e8cbc3ef6ac4829a9aeaddf9e5b8368
+msgid "Maintenance"
+msgstr ""
+
+#: ../../dev.rst:1085
+# df753f25151f4d4b8cfc942915ee8eda
+msgid "MAINT.CANCEL"
+msgstr ""
+
+#: ../../dev.rst:1087
+# a6281f29bc684656bfef1ef3f107ee5c
+msgid "MAINT.CANCEL.PS"
+msgstr ""
+
+#: ../../dev.rst:1089
+# 6b1cdae2b61c404aaa7bfa74cf561ab2
+msgid "MAINT.PREPARE"
+msgstr ""
+
+#: ../../dev.rst:1091
+# 1a7651b09ce240f8accaeb6243b72a09
+msgid "MAINT.PREPARE.PS"
+msgstr ""
+
+#: ../../dev.rst:1093
+# f35d8679d0ab41158f0a0253ef992d5e
+msgid "VPN"
+msgstr ""
+
+#: ../../dev.rst:1093
+# 6d37121536084cfcb28a6e5f1ddd63a0
+msgid "VPN.REMOTE.ACCESS.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1095
+# b26c3d13b7a640bcaa1b31cd101003e6
+msgid "VPN.REMOTE.ACCESS.DESTROY"
+msgstr ""
+
+#: ../../dev.rst:1097
+# 03e51d7400474807b95af6af01f2abcf
+msgid "VPN.USER.ADD"
+msgstr ""
+
+#: ../../dev.rst:1099
+# 0887283d2b7d47e99ed511a653b19eb6
+msgid "VPN.USER.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:1101
+# 0c7c48a65ed444cab6ffadcc5f3e0f35
+msgid "VPN.S2S.VPN.GATEWAY.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1103
+# 088c8bddcda3437ba38c84c64ed4dd8b
+msgid "VPN.S2S.VPN.GATEWAY.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1105
+# f2d842d577b641bb80d42eea7815e307
+msgid "VPN.S2S.CUSTOMER.GATEWAY.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1107
+# 8f9e54e0a03d48d682bb6ebbf1e264bd
+msgid "VPN.S2S.CUSTOMER.GATEWAY.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1109
+# 0ecb424bff794dfe8f901acfce93d691
+msgid "VPN.S2S.CUSTOMER.GATEWAY.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1111
+# 3a7665c215d645eb9ef4051ad64228f1
+msgid "VPN.S2S.CONNECTION.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1113
+# 8f5a8ae08b534beb9e0ef1af501017d2
+msgid "VPN.S2S.CONNECTION.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1115
+# 17214507d9f14f5c8ebc878d4033675b
+msgid "VPN.S2S.CONNECTION.RESET"
+msgstr ""
+
+#: ../../dev.rst:1117
+# 71e70a0125374d7e8474cae1f20309fc
+msgid "Network"
+msgstr ""
+
+#: ../../dev.rst:1117
+# 2de54588bd304e5dafe5aa0c2b9c4da3
+msgid "NETWORK.RESTART"
+msgstr ""
+
+#: ../../dev.rst:1119
+# af862cac0842498798cdb70ce8ee2ac7
+msgid "Custom certificates"
+msgstr ""
+
+#: ../../dev.rst:1119
+# c4c6edfceadd496ca1cd3ceba59efafa
+msgid "UPLOAD.CUSTOM.CERTIFICATE"
+msgstr ""
+
+#: ../../dev.rst:1122
+# 28dcff1303834708b3620092652de860
+msgid "OneToOnenat"
+msgstr ""
+
+#: ../../dev.rst:1122
+# a6992e10d43d46cab03bcf39abfe742a
+msgid "STATICNAT.ENABLE"
+msgstr ""
+
+#: ../../dev.rst:1124
+# 639558116a054b13947f4525c89330ca
+msgid "STATICNAT.DISABLE"
+msgstr ""
+
+#: ../../dev.rst:1126
+# 10d2bd0eba47406883e95627ac65dae8
+msgid "ZONE.VLAN.ASSIGN"
+msgstr ""
+
+#: ../../dev.rst:1128
+# 055f3349617943379586168c9e8a4dd0
+msgid "ZONE.VLAN.RELEASE"
+msgstr ""
+
+#: ../../dev.rst:1130
+# a400a4a312b44772a14f04265a18e2f0
+msgid "Projects"
+msgstr ""
+
+#: ../../dev.rst:1130
+# 92043a54ddef4d929b14554c9f9eeebd
+msgid "PROJECT.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1132
+# 91c7c55cacd14ad9b709804ab65fa25c
+msgid "PROJECT.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1134
+# cefa689b18154e09b114141438d171ac
+msgid "PROJECT.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1136
+# 2a165e4549a8462e95ce3bd956226722
+msgid "PROJECT.ACTIVATE"
+msgstr ""
+
+#: ../../dev.rst:1138
+# 55e9f1af12854c9e80e5dc26a2a20a10
+msgid "PROJECT.SUSPEND"
+msgstr ""
+
+#: ../../dev.rst:1140
+# 3fbf10e620754801917eca5cce0cb06a
+msgid "PROJECT.ACCOUNT.ADD"
+msgstr ""
+
+#: ../../dev.rst:1142
+# 10152d2739d24a018e0ff295ee719fb2
+msgid "PROJECT.INVITATION.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1144
+# 0281e748e87f42e4ae5dc419f5fe5a2c
+msgid "PROJECT.INVITATION.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:1146
+# a79b5f168feb4d3cb393383c54a2ecba
+msgid "PROJECT.ACCOUNT.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:1148
+# f57c1a43fa0a49b39e475e79668e2a85
+msgid "Network as a Service"
+msgstr ""
+
+#: ../../dev.rst:1148
+# 228f56d86cd34d538773621b26be1d0a
+msgid "NETWORK.ELEMENT.CONFIGURE"
+msgstr ""
+
+#: ../../dev.rst:1151
+# 637555fe29dc456fa2128bb20a03ce07
+msgid "Physical Network Events"
+msgstr ""
+
+#: ../../dev.rst:1151
+# 5a143eeef182460da69f52203355f297
+msgid "PHYSICAL.NETWORK.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1153
+# 18fff6851b71468ba3a024c224b5da38
+msgid "PHYSICAL.NETWORK.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1155
+# 27194312cabd497a868c18814812b788
+msgid "PHYSICAL.NETWORK.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1157
+# a9e59d6750e44ff1a62705d3f85a0180
+msgid "Physical Network Service Provider Events"
+msgstr ""
+
+#: ../../dev.rst:1157
+# 075aca1844e445f6b43546beb174c2d6
+msgid "SERVICE.PROVIDER.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1159
+# 5644882c962c4bc8a09c1389af4fc80c
+msgid "SERVICE.PROVIDER.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1161
+# 3eee170522344c9ab1c095beb07cb81e
+msgid "SERVICE.PROVIDER.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1163
+# b5ac0b14b4ba477484d60bc53dc37bee
+msgid "Physical Network Traffic Type Events"
+msgstr ""
+
+#: ../../dev.rst:1163
+# 2126c2311d9b4f5eab41b797d7f1c79d
+msgid "TRAFFIC.TYPE.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1165
+# f574f7fa432249d4b77d9ef69c2a438e
+msgid "TRAFFIC.TYPE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1167
+# 5e3ebc4061f44d9fa2b360be1919056b
+msgid "TRAFFIC.TYPE.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1169
+#: ../../dev.rst:1239
+# 5694676d0fea49f9be10a19d945eb6f3
+# f2c2a8b2a29a4914b5ba80db28d4a9e5
+msgid "External network device events"
+msgstr ""
+
+#: ../../dev.rst:1169
+# 3a40fe68f0ba4769be7f068a47498353
+msgid "PHYSICAL.LOADBALANCER.ADD"
+msgstr ""
+
+#: ../../dev.rst:1171
+# a9d01a930a2a4d449d348de6ce22f321
+msgid "PHYSICAL.LOADBALANCER.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1173
+# 860d3fb2956f4f2d94665c35e57b996f
+msgid "PHYSICAL.LOADBALANCER.CONFIGURE"
+msgstr ""
+
+#: ../../dev.rst:1175
+# 99432960a5dc4084825347f24bb1d90b
+msgid "External switch management device events"
+msgstr ""
+
+#: ../../dev.rst:1179
+# cab557c970b1454493f950d61bcbf762
+msgid "For example: Cisco Nexus 1000v Virtual Supervisor Module."
+msgstr ""
+
+#: ../../dev.rst:1175
+# 57e1cf12e3db43eebfada0791ec75ed0
+msgid "SWITCH.MGMT.ADD"
+msgstr ""
+
+#: ../../dev.rst:1177
+# ad8a274c736a46f9bcd06daea2799101
+msgid "SWITCH.MGMT.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1179
+# da4cbe6b2a6043d6abf9f6154f742d49
+msgid "SWITCH.MGMT.CONFIGURE"
+msgstr ""
+
+#: ../../dev.rst:1181
+# 29f7513425ad46359b65a47845f157a7
+msgid "SWITCH.MGMT.ENABLE"
+msgstr ""
+
+#: ../../dev.rst:1183
+# 67f7640000c74f07b2f6ab5f6651fcb6
+msgid "SWITCH.MGMT.DISABLE"
+msgstr ""
+
+#: ../../dev.rst:1185
+# 635749d2fe074c6d83e919d072819672
+msgid "PHYSICAL.FIREWALL.ADD"
+msgstr ""
+
+#: ../../dev.rst:1187
+# 63291158ae1045188bbd373cd3a79356
+msgid "PHYSICAL.FIREWALL.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1189
+# 795f61d09f344fa9b211823d019e221c
+msgid "PHYSICAL.FIREWALL.CONFIGURE"
+msgstr ""
+
+#: ../../dev.rst:1191
+# 89cf06cca36c4a4ca5ba897ddbaf4d58
+msgid "VPC"
+msgstr ""
+
+#: ../../dev.rst:1191
+# 7e9d36a793144a0b8e35ed7695caaa69
+msgid "VPC.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1193
+# bf14a605bb5b47c78733f6ee22cba2ce
+msgid "VPC.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1195
+# dfc4073a3c464c60a671151b192904d1
+msgid "VPC.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1197
+# 9d60ce613d2d46f5a8ce5a1602c880e6
+msgid "VPC.RESTART"
+msgstr ""
+
+#: ../../dev.rst:1199
+# d0c21aaa24f44b78b782c07b899cd78e
+msgid "Network ACL"
+msgstr ""
+
+#: ../../dev.rst:1199
+# ed5aeefb83d6466bb0ce40d2218326cf
+msgid "NETWORK.ACL.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1201
+# 02e6f982f8d44f538e252c70789133e0
+msgid "NETWORK.ACL.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1203
+# f8b87afb1b404efc89ab5f7559fe6361
+msgid "NETWORK.ACL.REPLACE"
+msgstr ""
+
+#: ../../dev.rst:1205
+# 431c84963d904458ba23b47a76e28dc5
+msgid "NETWORK.ACL.ITEM.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1207
+# f01a3c3a38844cdf8ec3b5ea4a3be85b
+msgid "NETWORK.ACL.ITEM.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1209
+# 9069cff1a8f94fc88d3d5e2c6f19d926
+msgid "NETWORK.ACL.ITEM.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1211
+# 654b46e911374c35807fc71e16876959
+msgid "VPC offerings"
+msgstr ""
+
+#: ../../dev.rst:1211
+# b5b644a13c774295a90b59a869535251
+msgid "VPC.OFFERING.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1213
+# d247a74805a541e584e97fa223e8feba
+msgid "VPC.OFFERING.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1215
+# 96d8c963e2e34d198297fb38ae2ba154
+msgid "VPC.OFFERING.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1217
+# 074d3b974dcb43c993cb065450f1f25f
+msgid "Private gateway"
+msgstr ""
+
+#: ../../dev.rst:1217
+# 2f84b8f7a0014c1f9772e0474ccd0a88
+msgid "PRIVATE.GATEWAY.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1219
+# ddfe7767f2894438a228e7d8aaa01bdb
+msgid "PRIVATE.GATEWAY.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1221
+# 3982ad2d0af648859177e40c742c6fa8
+msgid "Static routes"
+msgstr ""
+
+#: ../../dev.rst:1221
+# 97a6cb1cbd7f4d8380e3d064753e4a76
+msgid "STATIC.ROUTE.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1223
+# 0744a134a90a41bd94043e89f981c290
+msgid "STATIC.ROUTE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1225
+# 4054268ea7184437a13fe652f634b83d
+msgid "Tag-related events"
+msgstr ""
+
+#: ../../dev.rst:1225
+# 8297ba38795649f08afd5d95df3fad35
+msgid "CREATE\\_TAGS"
+msgstr ""
+
+#: ../../dev.rst:1227
+# e41461c480c3456c9ba4331a54b5bda2
+msgid "DELETE\\_TAGS"
+msgstr ""
+
+#: ../../dev.rst:1229
+# 6fbca5203601434498b01a51b644f63a
+msgid "Meta data-related events"
+msgstr ""
+
+#: ../../dev.rst:1229
+# cdb5effcff30492eabdd3e895719c19c
+msgid "CREATE\\_RESOURCE\\_DETAILS"
+msgstr ""
+
+#: ../../dev.rst:1231
+# 76c4af5b2fe64580b664adf8a6556de7
+msgid "DELETE\\_RESOURCE\\_DETAILS"
+msgstr ""
+
+#: ../../dev.rst:1233
+# 8b326f8e2d4b4c91844b9dbe972362e5
+msgid "VM snapshot events"
+msgstr ""
+
+#: ../../dev.rst:1233
+# e81388d5cf2f4d0bbca408d9f51e8832
+msgid "VMSNAPSHOT.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1235
+# e4e79cfe40ac470cbfe2b740a15c8a22
+msgid "VMSNAPSHOT.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1237
+# e8afb9179ee041b5bcf21671db55c610
+msgid "VMSNAPSHOT.REVERTTO"
+msgstr ""
+
+#: ../../dev.rst:1239
+# b01153a95b404dd6a739d7ca7cb5dc6f
+msgid "PHYSICAL.NVPCONTROLLER.ADD"
+msgstr ""
+
+#: ../../dev.rst:1241
+# 632af0c1da5e4d4ca79199a8d9217275
+msgid "PHYSICAL.NVPCONTROLLER.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1243
+# c41b43b4e47c418a94954dcf4659630d
+msgid "PHYSICAL.NVPCONTROLLER.CONFIGURE"
+msgstr ""
+
+#: ../../dev.rst:1245
+# 2446bc5f48f947f898a30d4ee2429108
+msgid "AutoScale"
+msgstr ""
+
+#: ../../dev.rst:1245
+# 5ce3e63a54dd4c15b1f5cc7cd2bcc96b
+msgid "COUNTER.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1247
+# 00d5ea5c3142408d9ed52d952433ea55
+msgid "COUNTER.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1249
+# d46552187a2e4093bab6cd33120c01b6
+msgid "CONDITION.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1251
+# f74458c9c9e2474195caea1ab66d0258
+msgid "CONDITION.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1253
+# 6b2d513100e040ad908533a2626ef58e
+msgid "AUTOSCALEPOLICY.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1255
+# 4d492b6b5f894eccb34a579d6df18197
+msgid "AUTOSCALEPOLICY.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1257
+# 3bb42c29abb3473daeb32d519bd56d5e
+msgid "AUTOSCALEPOLICY.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1259
+# 4cc4026a3d5b4a4eb635f09ce0f2439a
+msgid "AUTOSCALEVMPROFILE.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1261
+# caa130acb2734766a3e5b0442a5c5ade
+msgid "AUTOSCALEVMPROFILE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1263
+# 6be5dec329464b0e8ec5e0305d09a5a2
+msgid "AUTOSCALEVMPROFILE.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1265
+# b370a64985ba4ab5ab0106cd97ae31b3
+msgid "AUTOSCALEVMGROUP.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1267
+# e33476c0ee31487ea856c938d33f3b2d
+msgid "AUTOSCALEVMGROUP.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1269
+# 88dff327d5ca43de814a3a5c9e068457
+msgid "AUTOSCALEVMGROUP.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1271
+# 11de45d76eda4776915a59e50e18ac68
+msgid "AUTOSCALEVMGROUP.ENABLE"
+msgstr ""
+
+#: ../../dev.rst:1273
+# 5145ef5e7a374588bc5c5c9173da6b01
+msgid "AUTOSCALEVMGROUP.DISABLE"
+msgstr ""
+
+#: ../../dev.rst:1275
+# ecf312f56bc644759dd02b247dbaca35
+msgid "PHYSICAL.DHCP.ADD"
+msgstr ""
+
+#: ../../dev.rst:1277
+# 12239c1e044c4de38c61d2910f135b81
+msgid "PHYSICAL.DHCP.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1279
+# d3925718fc1a48cb913d438ae47c8e52
+msgid "PHYSICAL.PXE.ADD"
+msgstr ""
+
+#: ../../dev.rst:1281
+# f23e06df5fa94c41b341d3afdc34cbdb
+msgid "PHYSICAL.PXE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1283
+# e981870078114b04b0378178faa81720
+msgid "AG.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1285
+# 061397efbf934a16aa0435b029f6cb31
+msgid "AG.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1287
+# 26a254121f3f467e844419710c78642a
+msgid "AG.ASSIGN"
+msgstr ""
+
+#: ../../dev.rst:1289
+# ebcf9520267b4a90a5c265dc76d00d95
+msgid "AG.REMOVE"
+msgstr ""
+
+#: ../../dev.rst:1291
+# be2c1b9db8c34740a1fe20628ab40f01
+msgid "VM.AG.UPDATE"
+msgstr ""
+
+#: ../../dev.rst:1293
+# a709d3732f46421cbcda9f5ac24eb305
+msgid "INTERNALLBVM.START"
+msgstr ""
+
+#: ../../dev.rst:1295
+# b6715cc86c994240b485e949bf1598e3
+msgid "INTERNALLBVM.STOP"
+msgstr ""
+
+#: ../../dev.rst:1297
+# 8421ad90aacf46edb14a274ec36395aa
+msgid "HOST.RESERVATION.RELEASE"
+msgstr ""
+
+#: ../../dev.rst:1299
+# 3a084fff72bf4c489d3164e6160ad4cb
+msgid "Dedicated guest vlan range"
+msgstr ""
+
+#: ../../dev.rst:1299
+# 71cf76d6a1f44cf79780eac797da01c9
+msgid "GUESTVLANRANGE.DEDICATE"
+msgstr ""
+
+#: ../../dev.rst:1301
+# 36c642904da14b8fa59d5e8134d82009
+msgid "GUESTVLANRANGE.RELEASE"
+msgstr ""
+
+#: ../../dev.rst:1303
+# 030e512c5a554106b872744ce40bcc55
+msgid "PORTABLE.IP.RANGE.CREATE"
+msgstr ""
+
+#: ../../dev.rst:1305
+# 896dc2d533814346800fda0e0e063e93
+msgid "PORTABLE.IP.RANGE.DELETE"
+msgstr ""
+
+#: ../../dev.rst:1307
+# e3dae733d43349feb5161a9e30d1371c
+msgid "PORTABLE.IP.TRANSFER"
+msgstr ""
+
+#: ../../dev.rst:1309
+# 8ec3cf7227864b018dddef09969ae817
+msgid "Dedicated Resources"
+msgstr ""
+
+#: ../../dev.rst:1309
+# 5fb2eec5fe874352b3b7fd3760285739
+msgid "DEDICATE.RESOURCE"
+msgstr ""
+
+#: ../../dev.rst:1311
+# d0cc51dc064a418e841a4a46cb9e6751
+msgid "DEDICATE.RESOURCE.RELEASE"
+msgstr ""
+
+#: ../../dev.rst:1313
+# b5cb673ae0b64c499ae9788823168239
+msgid "VM.RESERVATION.CLEANUP"
+msgstr ""
+
+#: ../../dev.rst:1315
+# 04b13e6b43974f82976c390d6110071d
+msgid "UCS.ASSOCIATEPROFILE"
+msgstr ""
+
+#: ../../dev.rst:1317
+# b6423fa0906c455f829ae87b6f2d29b0
+msgid "UCS.DISASSOCIATEPROFILE"
+msgstr ""
+
+#: ../../dev.rst:1321
+# d5c3019aa78c437fa7ed6a0497abffaf
+msgid "Time Zones"
+msgstr ""
+
+#: ../../dev.rst:1323
+# 116de5edf8e449378280c02a410c56f1
+msgid "The following time zone identifiers are accepted by PRODUCT. There are several places that have a time zone as a required or optional parameter. These include scheduling recurring snapshots, creating a user, and specifying the usage time zone in the Configuration table."
+msgstr ""
+
+#: ../../dev.rst:1329
+# 826b28ef0e904dc38481fba5de6f01d8
+msgid "Etc/GMT+12"
+msgstr ""
+
+#: ../../dev.rst:1329
+# d1ee5ea0cf8b482d9f9bb58ae6f25d3b
+msgid "Etc/GMT+11"
+msgstr ""
+
+#: ../../dev.rst:1329
+# bf29b6e911df40d489b5dcc001ccf668
+msgid "Pacific/Samoa"
+msgstr ""
+
+#: ../../dev.rst:1331
+# 0f032e031e684469963d0d3313b53728
+msgid "Pacific/Honolulu"
+msgstr ""
+
+#: ../../dev.rst:1331
+# b4c90f9e4db84df3aa650cc650a5cd80
+msgid "US/Alaska"
+msgstr ""
+
+#: ../../dev.rst:1331
+# dcde82c56f6845dc8d6d1c12e2a5a643
+msgid "America/Los\\_Angeles"
+msgstr ""
+
+#: ../../dev.rst:1333
+# 2db93cf46c004a5a869e073a4642580d
+msgid "Mexico/BajaNorte"
+msgstr ""
+
+#: ../../dev.rst:1333
+# 34c07dd5cb5f420e97c5508ab975bf3c
+msgid "US/Arizona"
+msgstr ""
+
+#: ../../dev.rst:1333
+# a13b8c545eae434ba626d2dc036b461c
+msgid "US/Mountain"
+msgstr ""
+
+#: ../../dev.rst:1335
+# b6fede29ab21428ca0682e4cccf4f5b1
+msgid "America/Chihuahua"
+msgstr ""
+
+#: ../../dev.rst:1335
+# 634c419e82934a0ea351b3d99c3d6561
+msgid "America/Chicago"
+msgstr ""
+
+#: ../../dev.rst:1335
+# 656848e4004b4a9a9f2c21a789e36572
+msgid "America/Costa\\_Rica"
+msgstr ""
+
+#: ../../dev.rst:1337
+# 7c4d4c2391be4ca29fbb3a9fea5351e8
+msgid "America/Mexico\\_City"
+msgstr ""
+
+#: ../../dev.rst:1337
+# aee23664cb9d4182b2feae400a38a11e
+msgid "Canada/Saskatchewan"
+msgstr ""
+
+#: ../../dev.rst:1337
+# 10d105410731498f89d87ad6efc87a70
+msgid "America/Bogota"
+msgstr ""
+
+#: ../../dev.rst:1339
+# 5fa4882f1b3d4f12b87a03edec888952
+msgid "America/New\\_York"
+msgstr ""
+
+#: ../../dev.rst:1339
+# b81535c4904044cb99d950c6ff3b73c2
+msgid "America/Caracas"
+msgstr ""
+
+#: ../../dev.rst:1339
+# 7467c1ea627a4a6b943e9dc11519c148
+msgid "America/Asuncion"
+msgstr ""
+
+#: ../../dev.rst:1341
+# 3f5598da34fc494eb60836684683e9d1
+msgid "America/Cuiaba"
+msgstr ""
+
+#: ../../dev.rst:1341
+# b44bd176077846608c9154828fe17bcf
+msgid "America/Halifax"
+msgstr ""
+
+#: ../../dev.rst:1341
+# c5a671425aa645e48ca5e6be639d3b47
+msgid "America/La\\_Paz"
+msgstr ""
+
+#: ../../dev.rst:1343
+# a0e45644509541e29e7ff3892d29a43f
+msgid "America/Santiago"
+msgstr ""
+
+#: ../../dev.rst:1343
+# 29dc0b49bfca4c04a4dae85abef0fd73
+msgid "America/St\\_Johns"
+msgstr ""
+
+#: ../../dev.rst:1343
+# 58a82f8d3d494e66a34d3e0c237636db
+msgid "America/Araguaina"
+msgstr ""
+
+#: ../../dev.rst:1345
+# 5eb2f12569994569b889e252c121cab4
+msgid "America/Argentina/Buenos\\_Aires"
+msgstr ""
+
+#: ../../dev.rst:1345
+# c0e280db42da49069491a621fb47e797
+msgid "America/Cayenne"
+msgstr ""
+
+#: ../../dev.rst:1345
+# 3b6ac15163534a83ad4912f04b6f647c
+msgid "America/Godthab"
+msgstr ""
+
+#: ../../dev.rst:1347
+# 53214010b12741a291c22600879bec15
+msgid "America/Montevideo"
+msgstr ""
+
+#: ../../dev.rst:1347
+# ed82003665954529b286afe7c3469042
+msgid "Etc/GMT+2"
+msgstr ""
+
+#: ../../dev.rst:1347
+# 51d8d1bb8ab2480d98d28b9f9a447b4d
+msgid "Atlantic/Azores"
+msgstr ""
+
+#: ../../dev.rst:1349
+# c61f4b615d274d368cad81dcdbb9b7a2
+msgid "Atlantic/Cape\\_Verde"
+msgstr ""
+
+#: ../../dev.rst:1349
+# f9d4e688062c42fbafbfe3a9c4f58b4c
+msgid "Africa/Casablanca"
+msgstr ""
+
+#: ../../dev.rst:1349
+# 9b681fc4d898424c9fabfdb630ee269b
+msgid "Etc/UTC"
+msgstr ""
+
+#: ../../dev.rst:1351
+# a67e41b70bea47fd9cbdcbde39993cfc
+msgid "Atlantic/Reykjavik"
+msgstr ""
+
+#: ../../dev.rst:1351
+# 50c1ed24011c4ba0ad7d2253d5ca7cea
+msgid "Europe/London"
+msgstr ""
+
+#: ../../dev.rst:1351
+# 4484c135ceaa41068801eca54c861c94
+msgid "CET"
+msgstr ""
+
+#: ../../dev.rst:1353
+# bce1e8f01b3d42d4b7d49bf033474acb
+msgid "Europe/Bucharest"
+msgstr ""
+
+#: ../../dev.rst:1353
+# 7d1b52a170d74857ae27f2aedd17dc98
+msgid "Africa/Johannesburg"
+msgstr ""
+
+#: ../../dev.rst:1353
+# f231b78cbc48480684461d7bc739ef8e
+msgid "Asia/Beirut"
+msgstr ""
+
+#: ../../dev.rst:1355
+# 6747f64e178249d48a4d77c1bdbc5193
+msgid "Africa/Cairo"
+msgstr ""
+
+#: ../../dev.rst:1355
+# 33156f8d830c4ca4b4b1ba771de526d9
+msgid "Asia/Jerusalem"
+msgstr ""
+
+#: ../../dev.rst:1355
+# afcbe08d5e2546ea9b2f1c65664408db
+msgid "Europe/Minsk"
+msgstr ""
+
+#: ../../dev.rst:1357
+# 0f082c471d22446a80ceb0c1d6db6724
+msgid "Europe/Moscow"
+msgstr ""
+
+#: ../../dev.rst:1357
+# 3b743c29a1e44d82b03502baa0493920
+msgid "Africa/Nairobi"
+msgstr ""
+
+#: ../../dev.rst:1357
+# d4ad3b6a25534b3d99fb57bfe804a9f6
+msgid "Asia/Karachi"
+msgstr ""
+
+#: ../../dev.rst:1359
+# 7336fd24e11a49919c81b27808f8f7b3
+msgid "Asia/Kolkata"
+msgstr ""
+
+#: ../../dev.rst:1359
+# 9be1ff8a167945d18ed0f5d337d72dbe
+msgid "Asia/Bangkok"
+msgstr ""
+
+#: ../../dev.rst:1359
+# 507cb5a2068046cdb526c37a2b4781ab
+msgid "Asia/Shanghai"
+msgstr ""
+
+#: ../../dev.rst:1361
+# f03e006791a144b390c53cb1eedfb979
+msgid "Asia/Kuala\\_Lumpur"
+msgstr ""
+
+#: ../../dev.rst:1361
+# e16d88cb949b4c23b61fced79bb9be74
+msgid "Australia/Perth"
+msgstr ""
+
+#: ../../dev.rst:1361
+# c1eeabdd9492421ca820326d5f5a6bdb
+msgid "Asia/Taipei"
+msgstr ""
+
+#: ../../dev.rst:1363
+# cdb1296e6ff247f1bec854c83d5d3c5d
+msgid "Asia/Tokyo"
+msgstr ""
+
+#: ../../dev.rst:1363
+# 681168bfa81f4148b15066fe97341e46
+msgid "Asia/Seoul"
+msgstr ""
+
+#: ../../dev.rst:1363
+# 88d44fd632124c8fb29a909a45acdac7
+msgid "Australia/Adelaide"
+msgstr ""
+
+#: ../../dev.rst:1365
+# 6edbd9d03d5b418a8abc9baa6828c62e
+msgid "Australia/Darwin"
+msgstr ""
+
+#: ../../dev.rst:1365
+# c2da9953f84043caaf3e3a4b58c8e3da
+msgid "Australia/Brisbane"
+msgstr ""
+
+#: ../../dev.rst:1365
+# 0d793eb4459e4c22991796e567924f99
+msgid "Australia/Canberra"
+msgstr ""
+
+#: ../../dev.rst:1367
+# e524313a85ba4b209c5de1d49051d1b8
+msgid "Pacific/Guam"
+msgstr ""
+
+#: ../../dev.rst:1367
+# 8e890fe610da40a782aa5ae36e97ccff
+msgid "Pacific/Auckland"
+msgstr ""
+
diff --git a/source/conceptsandterminology/locale/pot/developer_guide.pot b/source/conceptsandterminology/locale/pot/developer_guide.pot
new file mode 100644
index 0000000..2e6995b
--- /dev/null
+++ b/source/conceptsandterminology/locale/pot/developer_guide.pot
@@ -0,0 +1,528 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../developer_guide.rst:2
+# bb72baa2a42c478fa65fa1c9b410f0b6
+msgid "CloudStack Installation from Source for Developers"
+msgstr ""
+
+#: ../../developer_guide.rst:4
+# d5339eb5aa3a4e4797040c45829f7a12
+msgid "This book is aimed at CloudStack developers who need to build the code. These instructions are valid on a Ubuntu 12.04 and CentOS 6.4 systems and were tested with the 4.2 release of Apache CloudStack, please adapt them if you are on a different operating system or using a newer/older version of CloudStack. This book is composed of the following sections:"
+msgstr ""
+
+#: ../../developer_guide.rst:10
+# 2513ed5b50064ad5baea6e2d6ca56667
+msgid "Installation of the prerequisites"
+msgstr ""
+
+#: ../../developer_guide.rst:11
+# b609f7feda6e484ab28214d803d9ddb4
+msgid "Compiling and installation from source"
+msgstr ""
+
+#: ../../developer_guide.rst:12
+# 04a3de1bd1d548b5a551870f1087bba4
+msgid "Using the CloudStack simulator"
+msgstr ""
+
+#: ../../developer_guide.rst:13
+# df71d1f0b01c4b44a75c4d216cd5f03f
+msgid "Installation with DevCloud the CloudStack sandbox"
+msgstr ""
+
+#: ../../developer_guide.rst:14
+# fecac2ddc3b4418588b49180b4d1e60b
+msgid "Building your own packages"
+msgstr ""
+
+#: ../../developer_guide.rst:15
+#: ../../developer_guide.rst:458
+# fc80af4f6f25482088389dc04fc822c8
+# f6c0d2e4f50d4f1a8ce2a237d8fa69e2
+msgid "The CloudStack API"
+msgstr ""
+
+#: ../../developer_guide.rst:16
+#: ../../developer_guide.rst:596
+# 2956ea125ee24f14a451fd03a284d663
+# f78027510f8a487f8d4e8bf274978c61
+msgid "Testing the AWS API interface"
+msgstr ""
+
+#: ../../developer_guide.rst:20
+# 74ac0a26ef2e4fad99f218beafca959b
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../developer_guide.rst:22
+# d62a80da8f72450fb3042984efc65381
+msgid "In this section we'll look at installing the dependencies you'll need for Apache CloudStack development."
+msgstr ""
+
+#: ../../developer_guide.rst:26
+# 1293735d08304e438df4d231fd9a602c
+msgid "On Ubuntu 12.04"
+msgstr ""
+
+#: ../../developer_guide.rst:28
+#: ../../developer_guide.rst:105
+# d1ad39d0193e4fdfb1b38a70a5409bfd
+# be623c5672e64a878c69313bd57bf97d
+msgid "First update and upgrade your system:"
+msgstr ""
+
+#: ../../developer_guide.rst:35
+# 515cc3ee920143b0a86beef63bd6d782
+msgid "NTP might already be installed, check it with ``service ntp status``. If it's not then install NTP to synchronize the clocks:"
+msgstr ""
+
+#: ../../developer_guide.rst:42
+#: ../../developer_guide.rst:118
+# 4a52a01411eb42b98e46f94978008eb4
+# 2c13eaff12c04b18af30f899add0eb45
+msgid "Install ``openjdk``. As we're using Linux, OpenJDK is our first choice."
+msgstr ""
+
+#: ../../developer_guide.rst:48
+# f04daa6be11c45beae58c455901d8f6c
+msgid "Install ``tomcat6``, note that the new version of tomcat on `Ubuntu <http://packages.ubuntu.com/precise/all/tomcat6>`__ is the 6.0.35 version."
+msgstr ""
+
+#: ../../developer_guide.rst:56
+#: ../../developer_guide.rst:141
+# 35da40eb45c84d80bce02f7e347c27f7
+# 9b90bffd5d744e20acf7be0491b4ce65
+msgid "Next, we'll install MySQL if it's not already present on the system."
+msgstr ""
+
+#: ../../developer_guide.rst:62
+#: ../../developer_guide.rst:147
+# e26c79313e5e4528aba516b8b8ece9d8
+# d8fb218502874578a85a5b15da88c447
+msgid "Remember to set the correct ``mysql`` password in the CloudStack properties file. Mysql should be running but you can check it's status with:"
+msgstr ""
+
+#: ../../developer_guide.rst:70
+# 706465b6a843445099c5b27e7d83a8d7
+msgid "Developers wanting to build CloudStack from source will want to install the following additional packages. If you dont' want to build from source just jump to the next section."
+msgstr ""
+
+#: ../../developer_guide.rst:74
+#: ../../developer_guide.rst:155
+# f2054657f7a740a3a913c84c8b106f75
+# fdc1c399ba0c41d49fdd4f90b0a4b203
+msgid "Install ``git`` to later clone the CloudStack source code:"
+msgstr ""
+
+#: ../../developer_guide.rst:80
+# 36e58aa93a534a019dcd4bb2d179b1dc
+msgid "Install ``Maven`` to later build CloudStack"
+msgstr ""
+
+#: ../../developer_guide.rst:86
+#: ../../developer_guide.rst:185
+# 266630e646c14f149a80a8080bc4a605
+# b362ed17e6ea43919b1119134acbee67
+msgid "This should have installed Maven 3.0, check the version number with ``mvn --version``"
+msgstr ""
+
+#: ../../developer_guide.rst:89
+#: ../../developer_guide.rst:188
+# 0b84891f11754ca1b6aa57d307b41da0
+# 7eea27fb13d64a71afe4098449f7941a
+msgid "A little bit of Python can be used (e.g simulator), install the Python package management tools:"
+msgstr ""
+
+#: ../../developer_guide.rst:96
+#: ../../developer_guide.rst:207
+# f241bf5ebf2b426c8ca5da09dd3c2926
+# 872eab2916d24aa2b16ef1dec59b6ae4
+msgid "Finally install ``mkisofs`` with:"
+msgstr ""
+
+#: ../../developer_guide.rst:103
+# 4c8d5bdb7efc4ad297090744e0b5041b
+msgid "On centOS 6.4"
+msgstr ""
+
+#: ../../developer_guide.rst:112
+# 7bf47463418146c19a2a78e6eb8c704a
+msgid "If not already installed, install NTP for clock synchornization"
+msgstr ""
+
+#: ../../developer_guide.rst:124
+# 3eb3a55c55a64e89bf977cacab10742b
+msgid "Install ``tomcat6``, note that the version of tomcat6 in the default CentOS 6.4 repo is 6.0.24, so we will grab the 6.0.35 version. The 6.0.24 version will be installed anyway as a dependency to cloudstack."
+msgstr ""
+
+#: ../../developer_guide.rst:133
+# 152fbd52e1674b388c1563eee33ac833
+msgid "Setup tomcat6 system wide by creating a file ``/etc/profile.d/tomcat.sh`` with the following content:"
+msgstr ""
+
+#: ../../developer_guide.rst:161
+# 890e6701f64c4b778299fbb766c03a08
+msgid "Install ``Maven`` to later build CloudStack. Grab the 3.0.5 release from the Maven `website <http://maven.apache.org/download.cgi>`__"
+msgstr ""
+
+#: ../../developer_guide.rst:171
+# e4f4020b65d54bcca21983184d1ebf14
+msgid "Setup Maven system wide by creating a ``/etc/profile.d/maven.sh`` file with the following content:"
+msgstr ""
+
+#: ../../developer_guide.rst:179
+# 93a2a4707fbb4f3c9dca441314ef0f5b
+msgid "Log out and log in again and you will have maven in your PATH:"
+msgstr ""
+
+#: ../../developer_guide.rst:195
+# 705ab873d8594008836944d2fdb91ad0
+msgid "To install python-pip you might want to setup the Extra Packages for Enterprise Linux (EPEL) repo"
+msgstr ""
+
+#: ../../developer_guide.rst:204
+# 54199fd0c3f14def8421b213f70c72cd
+msgid "Then update you repository cache ``yum update`` and install pip ``yum -y install python-pip``"
+msgstr ""
+
+#: ../../developer_guide.rst:215
+# 436a0377e85244e6a89d96d94c6beef9
+msgid "Installing from Source"
+msgstr ""
+
+#: ../../developer_guide.rst:217
+# b4b0b7748d0e448b9c381f7675f7806b
+msgid "CloudStack uses git for source version control, if you know little about `git <http://book.git-scm.com/>`__ is a good start. Once you have git setup on your machine, pull the source with:"
+msgstr ""
+
+#: ../../developer_guide.rst:225
+# 959ab8583f1c488096ee96002d7430bb
+msgid "To build the latest stable release:"
+msgstr ""
+
+#: ../../developer_guide.rst:231
+# 32c17b3a428d4f13a0424591bc786dbb
+msgid "To compile Apache CloudStack, go to the cloudstack source folder and run:"
+msgstr ""
+
+#: ../../developer_guide.rst:238
+# 0a54ef76f0e64d71b6a360f37d44a53f
+msgid "If you want to skip the tests add ``-DskipTests`` to the command above. Do NOT use ``-Dmaven.test.skip=true`` because that will break the build."
+msgstr ""
+
+#: ../../developer_guide.rst:241
+# f0271a41ba4f45f690af10f47502929e
+msgid "You will have made sure to set the proper db password in ``utils/conf/db.properties``"
+msgstr ""
+
+#: ../../developer_guide.rst:244
+# 54b58ef51d8e4ad285647fe474a79982
+msgid "Deploy the database next:"
+msgstr ""
+
+#: ../../developer_guide.rst:250
+# 2122fb6f613d43a781c2f4007e3fd921
+msgid "Run Apache CloudStack with jetty for testing. Note that ``tomcat`` maybe be running on port 8080, stop it before you use ``jetty``"
+msgstr ""
+
+#: ../../developer_guide.rst:257
+# 5b053ff2ea4742869f84d9168092cd85
+msgid "Log Into Apache CloudStack:"
+msgstr ""
+
+#: ../../developer_guide.rst:259
+# 0257fca9cb6a4e7cb348b6a94d6c5c16
+msgid "Open your Web browser and use this URL to connect to CloudStack:"
+msgstr ""
+
+#: ../../developer_guide.rst:265
+# 3c66106a410a484db9f40c126c10d71f
+msgid "Replace ``localhost`` with the IP of your management server if need be."
+msgstr ""
+
+#: ../../developer_guide.rst:267
+# 0bb7c9cacc68411b8f2531ede4d1864d
+msgid "If you have iptables enabled, you may have to open the ports used by CloudStack. Specifically, ports 8080, 8250, and 9090."
+msgstr ""
+
+#: ../../developer_guide.rst:269
+# 66464a03df3a4a21898be477a7ba82ce
+msgid "You can now start configuring a Zone, playing with the API. Of course we did not setup any infrastructure, there is no storage, no hypervisors...etc. However you can run tests using the simulator. The following section shows you how to use the simulator so that you don't have to setup a physical infrastructure."
+msgstr ""
+
+#: ../../developer_guide.rst:276
+# 7b8da57d07b6433591f284e715d12591
+msgid "Using the Simulator"
+msgstr ""
+
+#: ../../developer_guide.rst:278
+# c5a7fd74375f49ba9b6ac5f20c8b62a3
+msgid "CloudStack comes with a simulator based on Python bindings called *Marvin*. Marvin is available in the CloudStack source code or on Pypi. With Marvin you can simulate your data center infrastructure by providing CloudStack with a configuration file that defines the number of zones/pods/clusters/hosts, types of storage etc. You can then develop and test the CloudStack management server *as if* it was managing your production infrastructure."
+msgstr ""
+
+#: ../../developer_guide.rst:286
+# 910cc167b7ea42cdaf3c2c8194ae8a2b
+msgid "Do a clean build:"
+msgstr ""
+
+#: ../../developer_guide.rst:292
+# 60dfd43a808f43efa474d6c33f97a310
+msgid "Deploy the database:"
+msgstr ""
+
+#: ../../developer_guide.rst:299
+# c2ddf475c9a4458095381fdf5b36b7c8
+msgid "Install marvin. Note that you will need to have installed ``pip`` properly in the prerequisites step."
+msgstr ""
+
+#: ../../developer_guide.rst:306
+# 1dc977631ad34ca7a239c5ecbb85e4ee
+msgid "Stop jetty (from any previous runs)"
+msgstr ""
+
+#: ../../developer_guide.rst:312
+# e2356af9ad664188b84f183581bee912
+msgid "Start jetty"
+msgstr ""
+
+#: ../../developer_guide.rst:318
+# 81afb780da8545b6acc1c20b0e58af14
+msgid "Setup a basic zone with Marvin. In a separate shell://"
+msgstr ""
+
+#: ../../developer_guide.rst:324
+# 1c70455811e54629bfd79ac64c3fc76a
+msgid "At this stage log in the CloudStack management server at http://localhost:8080/client with the credentials admin/password, you should see a fully configured basic zone infrastructure. To simulate an advanced zone replace ``basic.cfg`` with ``advanced.cfg``."
+msgstr ""
+
+#: ../../developer_guide.rst:329
+# fc4686e3709d491c95f3817ca634b9aa
+msgid "You can now run integration tests, use the API etc..."
+msgstr ""
+
+#: ../../developer_guide.rst:332
+# f43ce08473a443e0bce6cb55638ff6fb
+msgid "Using DevCloud"
+msgstr ""
+
+#: ../../developer_guide.rst:334
+# d99c1e63a66443539d663a0cba7beca0
+msgid "The Installing from source section will only get you to the point of runnign the management server, it does not get you any hypervisors. The simulator section gets you a simulated datacenter for testing. With DevCloud you can run at least one hypervisor and add it to your management server the way you would a real physical machine."
+msgstr ""
+
+#: ../../developer_guide.rst:340
+# 168253f881c04354b99dca74e7f5b0f1
+msgid "`DevCloud <https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud>`__ is the CloudStack sandbox, the standard version is a VirtualBox based image. There is also a KVM based image for it. Here we only show steps with the VirtualBox image. For KVM see the `wiki <https://cwiki.apache.org/confluence/display/CLOUDSTACK/devcloud-kvm>`__."
+msgstr ""
+
+#: ../../developer_guide.rst:346
+# 356c77a0078f47408537fe8f1e31d6dd
+msgid "\\*\\* DevCloud Pre-requisites"
+msgstr ""
+
+#: ../../developer_guide.rst:348
+# 11bd2fad2f484f2f8b8c6b7ed60b1250
+msgid "Install `VirtualBox <http://www.virtualbox.org>`__ on your machine"
+msgstr ""
+
+#: ../../developer_guide.rst:350
+# d7bc0d03f3444e498f06a605608b9052
+msgid "Run VirtualBox and under >Preferences create a *host-only interface* on which you disable the DHCP server"
+msgstr ""
+
+#: ../../developer_guide.rst:353
+# 5c0b9c8ea6014082898304ea288ea1cf
+msgid "Download the DevCloud `image <http://people.apache.org/~bhaisaab/cloudstack/devcloud/devcloud2.ova>`__"
+msgstr ""
+
+#: ../../developer_guide.rst:356
+# e0a8e6ff6f5e4fcf9e0249f0ba785ecc
+msgid "In VirtualBox, under File > Import Appliance import the DevCloud image."
+msgstr ""
+
+#: ../../developer_guide.rst:359
+# c4ddca1ab8fd40938573ab654fbc2169
+msgid "Verify the settings under > Settings and check the ``enable PAE`` option in the processor menu"
+msgstr ""
+
+#: ../../developer_guide.rst:362
+# 086a74de91ec46829227fe969cbf8b0c
+msgid "Once the VM has booted try to ``ssh`` to it with credentials: ``root/password``"
+msgstr ""
+
+#: ../../developer_guide.rst:365
+# 5306cafba5b649ff96137347bd6739cf
+msgid "ssh root@192.168.56.10"
+msgstr ""
+
+#: ../../developer_guide.rst:368
+# ba0b24b4a7914152bf9c97b90f0456d9
+msgid "Adding DevCloud as an Hypervisor"
+msgstr ""
+
+#: ../../developer_guide.rst:370
+# 90a83e4e6fc246f383835f00daea0315
+msgid "Picking up from a clean build:"
+msgstr ""
+
+#: ../../developer_guide.rst:377
+# 18e7f5520af948fd9f6cd2215ddd2b4f
+msgid "At this stage install marvin similarly than with the simulator:"
+msgstr ""
+
+#: ../../developer_guide.rst:383
+# 4081a35f553c4690b8c41bed96c20e81
+msgid "Start the management server"
+msgstr ""
+
+#: ../../developer_guide.rst:389
+# cd9dceaaa6d3449f8260f7987d24e0e4
+msgid "Then you are going to configure CloudStack to use the running DevCloud instance:"
+msgstr ""
+
+#: ../../developer_guide.rst:397
+# 2a20e453295741e0addd797848f68254
+msgid "If you are curious, check the ``devcloud.cfg`` file and see how the data center is defined: 1 Zone, 1 Pod, 1 Cluster, 1 Host, 1 primary Storage, 1 Seondary Storage, all provided by Devcloud."
+msgstr ""
+
+#: ../../developer_guide.rst:401
+# 287ad3cc0fc64288a0f2cae9770decb2
+msgid "You can now log in the management server at ``http://localhost:8080/client`` and start experimenting with the UI or the API."
+msgstr ""
+
+#: ../../developer_guide.rst:405
+# a35e6fa14ec84e00acef35655b70837a
+msgid "Do note that the management server is running in your local machine and that DevCloud is used only as a n Hypervisor. You could potentially run the management server within DevCloud as well, or memory granted, run multiple DevClouds."
+msgstr ""
+
+#: ../../developer_guide.rst:411
+# 0b216797731e464fb1daa87f7f9dce1c
+msgid "Building Packages"
+msgstr ""
+
+#: ../../developer_guide.rst:413
+# aa52ec9b95b94fff98aeb64a23855ff5
+msgid "Working from source is necessary when developing CloudStack. As mentioned earlier this is not primarily intended for users. However some may want to modify the code for their own use and specific infrastructure. The may also need to build their own packages for security reasons and due to network connectivity constraints. This section shows you the gist of how to build packages. We assume that the reader will know how to create a repository to serve this packages. The complete documentation is available on the `website <http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Installation_Guide/sect-source-builddebs.html>`__"
+msgstr ""
+
+#: ../../developer_guide.rst:423
+# 2dc15f1c96914156a0e85887844d8a90
+msgid "To build debian packages you will need couple extra packages that we did not need to install for source compilation:"
+msgstr ""
+
+#: ../../developer_guide.rst:431
+# e0134f646f2b416ca19265ef188af9a7
+msgid "Then build the packages with:"
+msgstr ""
+
+#: ../../developer_guide.rst:437
+# 7fc94e8e24f64ccbb9a5f7e2a1a0fefc
+msgid "One directory up from the CloudStack root dir you will find:"
+msgstr ""
+
+#: ../../developer_guide.rst:452
+# 9e40c2af8b5d4ff088904366476f5d4b
+msgid "Of course the community provides a repository for these packages and you can use it instead of building your own packages and putting them in your own repo. Instructions on how to use this community repository are available in the installation book."
+msgstr ""
+
+#: ../../developer_guide.rst:460
+# 7c104d4cd0fe475e863b91f53449a5c5
+msgid "The CloudStack API is a query based API using http that return results in XML or JSON. It is used to implement the default web UI. This API is not a standard like `OGF OCCI <http://www.ogf.org/gf/group_info/view.php?group=occi-wg>`__ or `DMTF CIMI <http://dmtf.org/standards/cloud>`__ but is easy to learn. Mapping exists between the AWS API and the CloudStack API as will be seen in the next section. Recently a Google Compute Engine interface was also developed that maps the GCE REST API to the CloudStack API described here. The API `docs <http://cloudstack.apache.org/docs/api/>`__ are a good start to learn the extent of the API. Multiple clients exist on `github <https://github.com/search?q=cloudstack+client&ref=cmdform>`__ to use this API, you should be able to find one in your favorite language. The reference documentation for the API and changes that might occur from version to version is availble `on-line <http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.1/html/Developers_Guide/index.html>`__. This short section is aimed at providing a quick summary to give you a base understanding of how to use this API. As a quick start, a good way to explore the API is to navigate the dashboard with a firebug console (or similar developer console) to study the queries."
+msgstr ""
+
+#: ../../developer_guide.rst:481
+# 0bcb8dd851254f9b9b0240917b405d84
+msgid "In a succint statement, the CloudStack query API can be used via http GET requests made against your cloud endpoint (e.g http://localhost:8080/client/api). The API name is passed using the ``command`` key and the various parameters for this API call are passed as key value pairs. The request is signed using the access key and secret key of the user making the call. Some calls are synchronous while some are asynchronous, this is documented in the API `docs <http://cloudstack.apache.org/docs/api/>`__. Asynchronous calls return a ``jobid``, the status and result of a job can be queried with the ``queryAsyncJobResult`` call. Let's get started and give an example of calling the ``listUsers`` API in Python."
+msgstr ""
+
+#: ../../developer_guide.rst:493
+# cb1f2074fce34b94ad77db3be1d917ce
+msgid "First you will need to generate keys to make requests. Going through the dashboard, go under ``Accounts`` select the appropriate account then click on ``Show Users`` select the intended users and generate keys using the ``Generate Keys`` icon. You will see an ``API Key`` and ``Secret Key`` field being generated. The keys will be of the form:"
+msgstr ""
+
+#: ../../developer_guide.rst:504
+# f06d2f79776845b69c69945a988dc02d
+msgid "Open a Python shell and import the basic modules necessary to make the request. Do note that this request could be made many different ways, this is just a low level example. The ``urllib*`` modules are used to make the http request and do url encoding. The ``hashlib`` module gives us the sha1 hash function. It used to geenrate the ``hmac`` (Keyed Hashing for Message Authentication) using the secretkey. The result is encoded using the ``base64`` module."
+msgstr ""
+
+#: ../../developer_guide.rst:524
+# 1bc86523e28745838203bfdeacc85364
+msgid "Define the endpoint of the Cloud, the command that you want to execute, the type of the response (i.e XML or JSON) and the keys of the user. Note that we do not put the secretkey in our request dictionary because it is only used to compute the hmac."
+msgstr ""
+
+#: ../../developer_guide.rst:538
+# 4096823c52da4b9d97971621c6bbdee5
+msgid "Build the base request string, the combination of all the key/pairs of the request, url encoded and joined with ampersand."
+msgstr ""
+
+#: ../../developer_guide.rst:547
+# 475167fa6f4f4187bc62b8c7b7dac9e1
+msgid "Compute the signature with hmac, do a 64 bit encoding and a url encoding, the string used for the signature is similar to the base request string shown above but the keys/values are lower cased and joined in a sorted order"
+msgstr ""
+
+#: ../../developer_guide.rst:568
+# e8ab8e0b9eaf4b9183fd8784025e5828
+msgid "Finally, build the entire string by joining the baseurl, the request str and the signature. Then do an http GET:"
+msgstr ""
+
+#: ../../developer_guide.rst:586
+# 34385cfcf355434bbfec59e948728211
+msgid "All the clients that you will find on github will implement this signature technique, you should not have to do it by hand. Now that you have explored the API through the UI and that you understand how to make low level calls, pick your favorite client of use `CloudMonkey <https://pypi.python.org/pypi/cloudmonkey/>`__. CloudMonkey is a sub-project of Apache CloudStack and gives operators/developers the ability to use any of the API methods. It has nice auto-completion and help feature as well as an API discovery mechanism since 4.2."
+msgstr ""
+
+#: ../../developer_guide.rst:598
+# 4bf1c04a89934aca9d24a5a585888739
+msgid "While the native CloudStack API is not a standard, CloudStack provides a AWS EC2 compatible interface. It has the great advantage that existing tools written with EC2 libraries can be re-used against a CloudStack based cloud. In the installation books we described how to run this interface from installing packages. In this section we show you how to compile the interface with ``maven`` and test it with Python boto module."
+msgstr ""
+
+#: ../../developer_guide.rst:606
+# a7d617f55dc447a49c45f903bced3aa6
+msgid "Starting from a running management server (with DevCloud for instance), start the AWS API interface in a separate shell with:"
+msgstr ""
+
+#: ../../developer_guide.rst:613
+# aa447203e885410e967cab647e8fa684
+msgid "Log into the CloudStack UI ``http://localhost:8080/client``, go to *Service Offerings* and edit one of the compute offerings to have the name ``m1.small`` or any of the other AWS EC2 instance types."
+msgstr ""
+
+#: ../../developer_guide.rst:617
+# 84e4d20e634f4ceab2d6ae95fe0bc920
+msgid "With access and secret keys generated for a user you should now be able to use Python `Boto <http://docs.pythonboto.org/en/latest/>`__ module:"
+msgstr ""
+
+#: ../../developer_guide.rst:636
+# 662e136af4714221a6a0414e4e68f928
+msgid "Note the new ``api_version`` number in the connection object and also note that there was no user registration to make like in previous CloudStack releases."
+msgstr ""
+
+#: ../../developer_guide.rst:641
+# b2bbf2564c724ebe98d0ac08c0ec5e58
+msgid "Conclusions"
+msgstr ""
+
+#: ../../developer_guide.rst:643
+# 590c4edda76644fe9a6410b6b2cb10fd
+msgid "CloudStack is a mostly Java application running with Tomcat and Mysql. It consists of a management server and depending on the hypervisors being used, an agent installed on the hypervisor farm. To complete a Cloud infrastructure however you will also need some Zone wide storage a.k.a Secondary Storage and some Cluster wide storage a.k.a Primary storage. The choice of hypervisor, storage solution and type of Zone (i.e Basic vs. Advanced) will dictate how complex your installation can be. As a quick start, you might want to consider KVM+NFS and a Basic Zone."
+msgstr ""
+
+#: ../../developer_guide.rst:653
+# 035523d6dcd4492cb920fdd912716794
+msgid "If you've run into any problems with this, please ask on the cloudstack-dev `mailing list </mailing-lists.html>`__."
+msgstr ""
+
diff --git a/source/conceptsandterminology/locale/pot/index.pot b/source/conceptsandterminology/locale/pot/index.pot
new file mode 100644
index 0000000..94276b8
--- /dev/null
+++ b/source/conceptsandterminology/locale/pot/index.pot
@@ -0,0 +1,78 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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:7
+# 23c03bcc367d4722babe767a2ded0a0a
+msgid "Welcome to CloudStack Documentation !"
+msgstr ""
+
+#: ../../index.rst:12
+# 3351811001dc4ad88fd1c24e26edc842
+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:16
+# 0c1f1b982e1f4ea0ab2e59763b54e0af
+msgid "Introduction"
+msgstr ""
+
+#: ../../index.rst:24
+# e5a4d610461549f2b9e9052a9bd37144
+msgid "Navigating the docs"
+msgstr ""
+
+#: ../../index.rst:26
+# b6ac1efdb8e346ad887e3d1bca3353cf
+msgid "Now that you have gone over the basic concepts of CloudStack you are ready to dive into the installation and operation."
+msgstr ""
+
+#: ../../index.rst:28
+# cbfe4ed11b86453ba3a3afc35075b554
+msgid "See the `Installation Guide <http://docs.cloudstack.apache.org/projects/cloudstack-installation>`_"
+msgstr ""
+
+#: ../../index.rst:30
+# 5fede185b96b42dea9024c0107dc3cbd
+msgid "See the `Administration Guide <http://docs.cloudstack.apache.org/projects/cloudstack-administration>`_"
+msgstr ""
+
+#: ../../index.rst:32
+# 0e4c89a1c62a42c687b191be08fce2bd
+msgid "See the `Release Notes <http://docs.cloudstack.apache.org/projects/cloudstack-release-notes>`_"
+msgstr ""
+
+#: ../../index.rst:34
+# ceeeb54aa3c144398acf5e519ee0948d
+msgid "Below you will find very specific documentation on advanced networking_ which you can skip if you are just getting started."
+msgstr ""
+
+#: ../../index.rst:36
+# bbf8a8d000f444838cea0bbca7cba655
+msgid "Developers will also find below a short developers_ guide."
+msgstr ""
+
+#: ../../index.rst:41
+# 8f8db100dd114a79a5c5ccb6e82fb3b9
+msgid "Advanced Networking Guides"
+msgstr ""
+
+#: ../../index.rst:56
+# 0fbbad32147342afad57da40b4b35f6d
+msgid "Developers Guide"
+msgstr ""
+
diff --git a/source/conceptsandterminology/locale/pot/networking.pot b/source/conceptsandterminology/locale/pot/networking.pot
new file mode 100644
index 0000000..c27f11e
--- /dev/null
+++ b/source/conceptsandterminology/locale/pot/networking.pot
@@ -0,0 +1,1940 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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/autoscale_without_netscaler.rst:2
+# 6d7543ab9fc046888af483d6a88b3fea
+msgid "Configuring AutoScale without using NetScaler"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:4
+# c9d0712245864f35982f232729bae189
+msgid "This feature is currently only available on the master branch and will be released in the 4.4 release."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:7
+# c06b36bcc0e945ed8ec5e832340e956d
+msgid "What is AutoScaling?"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:9
+# 9ef0e0f6d684458099daa4e2cbd8604b
+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/autoscale_without_netscaler.rst:12
+# d507077958d348a6a693de6775bfe989
+msgid "Hypervisor support"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:14
+# f9b069efcb974b079122d2c95723e601
+msgid "At that time, AutoScaling without NetScaler only supports for Xenserver. We are working to support KVM also."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:17
+#: ../../networking/midonet.rst:46
+#: ../../networking/nicira-plugin.rst:54
+#: ../../networking/ovs-plugin.rst:51
+# d15bd6b6f1064d51bfaf9e80a5565e96
+# 642427380e4746dc891e7fc38b37579c
+# 7f80ef902c494483b24d6d578c1d80d6
+# e49601d54ace43859a71cb43a746b49c
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:19
+# a3a685cf58fd4c9da4004b4f0ecfc871
+msgid "Before you configure an AutoScale rule, consider the following:"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:21
+# f58b7e2821534230a2dd48d7c0439189
+msgid "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."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:24
+# bd06b9d81c444e9ebf31854526b8c67f
+msgid "Configuration"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:26
+# f5b4b5fcd129488a826127aefa0a2c4a
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:30
+# 12cb34f03c3d4ef8b03fbd8a70bacc25
+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/autoscale_without_netscaler.rst:32
+# 417240213f024697b69eceede3796359
+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/autoscale_without_netscaler.rst:34
+# 4bcdcc4590a84f1385fa772041cea3cc
+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/autoscale_without_netscaler.rst:36
+# d0c371a515394389bb7add6a02f00eb4
+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/autoscale_without_netscaler.rst:38
+# 80fcbe70099f4105a927b595228409e4
+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/autoscale_without_netscaler.rst:40
+# b8283e1247a741a988e15d29da160851
+msgid "Specify the following scale-up and scale-down policies:"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:42
+# b2806defc678481a8198f37f837b7904
+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/autoscale_without_netscaler.rst:44
+# 31426b6f769148b2bef529c22ca6553b
+msgid "Counter: The performance counters expose the state of the monitored instances. We added two new counter to work with that feature:"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:46
+# 526679bfa9d3462180ab853fa20f8680
+msgid "Linux User CPU [native] - percentage"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:47
+# bdb11da3ca3c45a082b4acc27901d16c
+msgid "Linux User RAM [native] - percentage"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:49
+# a04a71965cb04316be4c79fdb9244b25
+msgid "Remember to choose one of them. If you choose anything else, the autoscaling will not work."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:51
+# 966b02f38d1f4928b5c562133bf8a0fe
+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/autoscale_without_netscaler.rst:53
+# 64b33fb24e6f4bf280e7d0137f7de18b
+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/autoscale_without_netscaler.rst:55
+# 80ff783a33004fb9b41f00e516ca4b5f
+msgid "Add: Click Add to add the condition."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:57
+# c9330ee4e4ec4a0fab4fba627aef3692
+msgid "Additionally, if you want to configure the advanced settings, click Show advanced settings, and specify the following:"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:59
+# 81ad44e324de4a7981892ca55611000e
+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/autoscale_without_netscaler.rst:61
+# 6269ce68ba3644a7aef1617b8a06b037
+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/autoscale_without_netscaler.rst:63
+# c6e65c1812814496bd1282ec97c7df0c
+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/autoscale_without_netscaler.rst:65
+# 6a90629fb18546df9eef77cb74d6d15e
+msgid "Apply: Click Apply to create the AutoScale configuration."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:68
+# ba9c7c2d58454a53940874911d9edefe
+msgid "Disabling and Enabling an AutoScale Configuration"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:70
+# 58935b9d39ad4fdaaf8cc7d4a8a4c69b
+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 button."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:72
+# 3e4ba6cb6d1b4bc79688675cbe57c75b
+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 button."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:75
+# 9ce87103773042ca88fd9b14d20ffe70
+msgid "Updating an AutoScale Configuration"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:77
+# c9cea96d124b46f4ab55f5b5b212453b
+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. 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/autoscale_without_netscaler.rst:81
+# 6738decbbf98438eaf0a2fc8f5d260d6
+msgid "Runtime Considerations"
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:83
+# 217b68ea35fc4cf2a5ad264d0e24f2db
+msgid "An administrator should not assign a VM to a load balancing rule which is configured for AutoScale."
+msgstr ""
+
+#: ../../networking/autoscale_without_netscaler.rst:85
+# 7ea14773c17b47cc98fb83abe744e19e
+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, it continues be showed as a service assigned to a rule inside the context of AutoScale."
+msgstr ""
+
+#: ../../networking/ipv6.rst:2
+# 9063c69b83cc4675b677f47968689ba7
+msgid "IPv6 Support in CloudStack"
+msgstr ""
+
+#: ../../networking/ipv6.rst:4
+# 41c57b3d50204fb7963f34ab1d591afd
+msgid "CloudStack supports Internet Protocol version 6 (IPv6), the recent version of the Internet Protocol (IP) that defines routing the network traffic. IPv6 uses a 128-bit address that exponentially expands the current address space that is available to the users. IPv6 addresses consist of eight groups of four hexadecimal digits separated by colons, for example, 5001:0dt8:83a3:1012:1000:8s2e:0870:7454. CloudStack supports IPv6 for public IPs in shared networks. With IPv6 support, VMs in shared networks can obtain both IPv4 and IPv6 addresses from the DHCP server. You can deploy VMs either in a IPv6 or IPv4 network, or in a dual network environment. If IPv6 network is used, the VM generates a link-local IPv6 address by itself, and receives a stateful IPv6 address from the DHCPv6 server."
+msgstr ""
+
+#: ../../networking/ipv6.rst:17
+# 79ebb2325f5b4e8e8cac37bfa0d04fa5
+msgid "IPv6 is supported only on KVM and XenServer hypervisors. The IPv6 support is only an experimental feature."
+msgstr ""
+
+#: ../../networking/ipv6.rst:20
+# 53b327c0565745c58193a2a636f6b508
+msgid "Here's the sequence of events when IPv6 is used:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:24
+# 8a26e433fd0b476792d0bf704b27cdcf
+msgid "The administrator creates an IPv6 shared network in an advanced zone."
+msgstr ""
+
+#: ../../networking/ipv6.rst:28
+# bae33a2f19004456a2ab80520bf87e3f
+msgid "The user deploys a VM in an IPv6 shared network."
+msgstr ""
+
+#: ../../networking/ipv6.rst:32
+# d94e348fb434423788634e5ad292b053
+msgid "The user VM generates an IPv6 link local address by itself, and gets an IPv6 global or site local address through DHCPv6."
+msgstr ""
+
+#: ../../networking/ipv6.rst:37
+# 2251bd2a3fae426e8c8833a37fb1e8ed
+msgid "Prerequisites and Guidelines"
+msgstr ""
+
+#: ../../networking/ipv6.rst:39
+# b0a1bb7836c9452d92a65788bee8b8a3
+msgid "Consider the following:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:43
+# afe38a72dbd14cdeb4d9dc752f130e59
+msgid "CIDR size must be 64 for IPv6 networks."
+msgstr ""
+
+#: ../../networking/ipv6.rst:47
+# c8ea1b7c1a9c49539151a78f22659658
+msgid "The DHCP client of the guest VMs should support generating DUID based on Link-layer Address (DUID- LL). DUID-LL derives from the MAC address of guest VMs, and therefore the user VM can be identified by using DUID. See `Dynamic Host Configuration Protocol for IPv6 <http://tools.ietf.org/html/rfc3315>`__\\ for more information."
+msgstr ""
+
+#: ../../networking/ipv6.rst:55
+# 8ddad136696547268df22d1813bf7ed4
+msgid "The gateway of the guest network generates Router Advisement and Response messages to Router Solicitation. The M (Managed Address Configuration) flag of Router Advisement should enable stateful IP address configuration. Set the M flag to where the end nodes receive their IPv6 addresses from the DHCPv6 server as opposed to the router or switch."
+msgstr ""
+
+#: ../../networking/ipv6.rst:62
+# 018ea1acf74f45559953f36b219c962f
+msgid "The M flag is the 1-bit Managed Address Configuration flag for Router"
+msgstr ""
+
+#: ../../networking/ipv6.rst:63
+# 0fe982af1fb44ffa95b13393cb6bcd97
+msgid "Advisement. When set, Dynamic Host Configuration Protocol (DHCPv6) is available for address configuration in addition to any IPs set by using stateless address auto-configuration."
+msgstr ""
+
+#: ../../networking/ipv6.rst:69
+# 93db14f646d24aa5acffca5d20338975
+msgid "Use the System VM template exclusively designed to support IPv6. Download the System VM template from `http://cloudstack.apt-get.eu/systemvm/ <http://cloudstack.apt-get.eu/systemvm/>`__."
+msgstr ""
+
+#: ../../networking/ipv6.rst:75
+# 516cb011d5914d10b3c49e9796299f74
+msgid "The concept of Default Network applies to IPv6 networks. However, unlike IPv4 CloudStack does not control the routing information of IPv6 in shared network; the choice of Default Network will not affect the routing in the user VM."
+msgstr ""
+
+#: ../../networking/ipv6.rst:82
+# e72596a773f14d379a92ec92afa10cce
+msgid "In a multiple shared network, the default route is set by the rack router, rather than the DHCP server, which is out of CloudStack control. Therefore, in order for the user VM to get only the default route from the default NIC, modify the configuration of the user VM, and set non-default NIC's ``accept_ra`` to 0 explicitly. The ``accept_ra`` parameter accepts Router Advertisements and auto-configure ``/proc/sys/net/ipv6/conf/interface`` with received data."
+msgstr ""
+
+#: ../../networking/ipv6.rst:92
+# dcaf10acb3f34de380f2eec1b9170253
+msgid "Limitations of IPv6 in CloudStack"
+msgstr ""
+
+#: ../../networking/ipv6.rst:94
+# fb2bfd214ac547ff97ee00d937f01b02
+msgid "The following are not yet supported:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:98
+# db335d19e6c047379e156b18f9d937f4
+msgid "Security groups"
+msgstr ""
+
+#: ../../networking/ipv6.rst:102
+# a3ea0a4439b1496fb507520690094baf
+msgid "Userdata and metadata"
+msgstr ""
+
+#: ../../networking/ipv6.rst:106
+# 6b8f88ad9ab547138fbd3e9f40c83d7f
+msgid "Passwords"
+msgstr ""
+
+#: ../../networking/ipv6.rst:109
+# 0d4771d5873a429984066fed90876c50
+msgid "Guest VM Configuration for DHCPv6"
+msgstr ""
+
+#: ../../networking/ipv6.rst:111
+# 01d0d92255b34c64a62845f02b8a8a4e
+msgid "For the guest VMs to get IPv6 address, run dhclient command manually on each of the VMs. Use DUID-LL to set up dhclient."
+msgstr ""
+
+#: ../../networking/ipv6.rst:114
+# f81673230f4447d680980559d7175a57
+msgid "The IPv6 address is lost when a VM is stopped and started. Therefore,"
+msgstr ""
+
+#: ../../networking/ipv6.rst:115
+# bb68d3447803467fa644192f3ee97415
+msgid "use the same procedure to get an IPv6 address when a VM is stopped and started."
+msgstr ""
+
+#: ../../networking/ipv6.rst:120
+# 1ac57146ad144c0e889d7f366e9df765
+msgid "Set up dhclient by using DUID-LL."
+msgstr ""
+
+#: ../../networking/ipv6.rst:122
+# cca1077553b14ea588e13553ca5d6a15
+msgid "Perform the following for DHCP Client 4.2 and above:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:126
+# 8fdbfe4d8c434120b67eb59e81d51d8b
+msgid "Run the following command on the selected VM to get the dhcpv6 offer from VR:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:133
+# 656eff7b6ce241928e7a9cb840be833e
+msgid "Perform the following for DHCP Client 4.1:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:137
+# a4d789246cad41a1b4d23bd3ed929217
+msgid "Open the following to the dhclient configuration file:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:145
+# 77af02d23c8e47f3b22d8d204a1870ae
+msgid "Add the following to the dhclient configuration file:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:153
+# 21b6ea25a4a748cf8e91acdaf3003e19
+msgid "Get IPv6 address from DHCP server as part of the system or network restart."
+msgstr ""
+
+#: ../../networking/ipv6.rst:156
+# b6c0f47d45b34e44acaaca779414b9cd
+msgid "Based on the operating systems, perform the following:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:158
+# ccd975fe312049fd896c38cc020b3fa9
+msgid "On CentOS 6.2:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:162
+# 0b3572ab3af943e48535af636ead58c5
+msgid "Open the Ethernet interface configuration file:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:168
+# b65f97c19a704a6d9d47de7c27b6c154
+msgid "The ``ifcfg-eth0`` file controls the first NIC in a system."
+msgstr ""
+
+#: ../../networking/ipv6.rst:172
+#: ../../networking/ipv6.rst:197
+#: ../../networking/ipv6.rst:218
+# b294b17bb15c4c6e93597ac4fb108b8f
+# 0afbae1c0d984242acfb32d4639fb73d
+# 796e2de0cb9a4194ab47d7f51f720614
+msgid "Make the necessary configuration changes, as given below:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:189
+#: ../../networking/ipv6.rst:210
+# 9f45f88d1d0543bcb315e99481fddf64
+# e374feefe5c04ff09a138d5020e42aa9
+msgid "Open the following:"
+msgstr ""
+
+#: ../../networking/ipv6.rst:206
+# f72a159dff2c4923a6fb4cdc96baefdd
+msgid "On Ubuntu 12.10"
+msgstr ""
+
+#: ../../networking/midonet.rst:2
+# f4e5c6a4da61434aa40dd7ba93484347
+msgid "The MidoNet Plugin"
+msgstr ""
+
+#: ../../networking/midonet.rst:5
+# 5b3351f0b1bc467ab6133d431de2a226
+msgid "Introduction to the MidoNet Plugin"
+msgstr ""
+
+#: ../../networking/midonet.rst:7
+# 43f5b5c6fc1241dfb632510a30e519ae
+msgid "The MidoNet plugin allows CloudStack to use the MidoNet virtualized networking solution as a provider for CloudStack networks and services. For more information on MidoNet and how it works, see http://www.midokura.com/midonet/."
+msgstr ""
+
+#: ../../networking/midonet.rst:13
+# c889a6c491c042388e4a20497669eb79
+msgid "Features of the MidoNet Plugin"
+msgstr ""
+
+#: ../../networking/midonet.rst:15
+# 835bde43c8534aefac5e1ccd81e317f4
+msgid "In CloudStack 4.2.0 only the KVM hypervisor is supported for use in combination with MidoNet."
+msgstr ""
+
+#: ../../networking/midonet.rst:18
+# cb53a8ffabf047298535ec3e31beb1ad
+msgid "In CloudStack release 4.2.0 this plugin supports several services in the Advanced Isolated network mode."
+msgstr ""
+
+#: ../../networking/midonet.rst:21
+# 5408bf0f7ed04335a07c1ac3f3448d26
+msgid "When tenants create new isolated layer 3 networks, instead of spinning up extra Virtual Router VMs, the relevant L3 elements (routers etc) are created in the MidoNet virtual topology by making the appropriate calls to the MidoNet API. Instead of using VLANs, isolation is provided by MidoNet."
+msgstr ""
+
+#: ../../networking/midonet.rst:27
+# 08c1c37a1bbd47dc96340d462ad72de6
+msgid "Aside from the above service (Connectivity), several extra features are supported in the 4.2.0 release:"
+msgstr ""
+
+#: ../../networking/midonet.rst:30
+#: ../../networking/nicira-plugin.rst:135
+#: ../../networking/nicira-plugin.rst:171
+#: ../../networking/nicira-plugin.rst:249
+#: ../../networking/ovs-plugin.rst:165
+#: ../../networking/ovs-plugin.rst:201
+# 49b7d4c5843d48e6a4d1903891dae0d5
+# ce613877293142fcb602392053011779
+# ef05554567b64823a676c47eb718aca1
+# 2d54607e20174f57bb939e3a4e34290b
+# 6785cd841d124fba8786fbffe6cddc8e
+# 19964c1d31624c81bece37d61d6b9f12
+msgid "DHCP"
+msgstr ""
+
+#: ../../networking/midonet.rst:32
+# 0114445c01474c868169c1cc09fcf6a3
+msgid "Firewall (ingress)"
+msgstr ""
+
+#: ../../networking/midonet.rst:34
+#: ../../networking/nicira-plugin.rst:23
+#: ../../networking/nicira-plugin.rst:145
+#: ../../networking/nicira-plugin.rst:177
+#: ../../networking/nicira-plugin.rst:257
+#: ../../networking/ovs-plugin.rst:175
+#: ../../networking/ovs-plugin.rst:207
+# cc25fff9d5124386ade225fd5bd434b9
+# 114e75dc258c41639ef45e1509e70e6a
+# 756d3782de384f7fa56ece273f820f1f
+# a59f45b448464b9c901841cb1c22fa73
+# 112c6589b3f0476fa047e31ff811c08a
+# 8ee18467dfbd4b41a9978d7b19ef330c
+# aaf6aab6d1244928b9202443ed4ef6b5
+msgid "Source NAT"
+msgstr ""
+
+#: ../../networking/midonet.rst:36
+#: ../../networking/nicira-plugin.rst:25
+#: ../../networking/nicira-plugin.rst:147
+#: ../../networking/nicira-plugin.rst:179
+#: ../../networking/nicira-plugin.rst:259
+#: ../../networking/ovs-plugin.rst:22
+#: ../../networking/ovs-plugin.rst:177
+#: ../../networking/ovs-plugin.rst:209
+# 5b959f094f524c5bad49148c2f11da16
+# bcacdbd92685435e8f2a5df1a1dd3b88
+# c13412cc9cce43e7a004eae8f13befe2
+# 85c67b794ccd46c0b46abaebd7630ec5
+# 0f45e03e929e49058061a4a2e0443085
+# bd9381baaa4d4fb7b4c942427d3ea4f3
+# f4d9288c69e545b1a9259940ea478a01
+# 1f40ca7af9414412b7526701cf836922
+msgid "Static NAT"
+msgstr ""
+
+#: ../../networking/midonet.rst:38
+#: ../../networking/nicira-plugin.rst:27
+#: ../../networking/ovs-plugin.rst:24
+# 0de776336a694f4dafd899038007d024
+# 992479d12e61499ca18b368c020bc4f1
+# 513cd51fab824f0cacb77ff2a6753ed0
+msgid "Port Forwarding"
+msgstr ""
+
+#: ../../networking/midonet.rst:40
+# 5ecfd1fd0fc6494988c5a472673fbc7d
+msgid "The plugin has been tested with MidoNet version 12.12. (Caddo)."
+msgstr ""
+
+#: ../../networking/midonet.rst:43
+# b8b2387b8d4b4e849ba66caea5e01c81
+msgid "Using the MidoNet Plugin"
+msgstr ""
+
+#: ../../networking/midonet.rst:48
+# 2668ec6a367641e69ff49062e49ce7e6
+msgid "In order to use the MidoNet plugin, the compute hosts must be running the MidoNet Agent, and the MidoNet API server must be available. Please consult the MidoNet User Guide for more information. The following section describes the CloudStack side setup."
+msgstr ""
+
+#: ../../networking/midonet.rst:53
+# 99b96e8acec34a0d8d7c21d78e2703fd
+msgid "CloudStack needs to have at least one physical network with the isolation method set to \"MIDO\". This network should be enabled for the Guest and Public traffic types."
+msgstr ""
+
+#: ../../networking/midonet.rst:57
+# 8b171ca5cb9e484397531f31e7b4d842
+msgid "Next, we need to set the following CloudStack settings under \"Global Settings\" in the UI:"
+msgstr ""
+
+#: ../../networking/midonet.rst:61
+# b69a22dee5ce48f4938914d6c4377874
+msgid "Setting Name"
+msgstr ""
+
+#: ../../networking/midonet.rst:61
+# db6dfe91d7fc49a7a23c8ec6f5589d9b
+msgid "Description"
+msgstr ""
+
+#: ../../networking/midonet.rst:61
+# 8ce816e9b802465f8f5f6375c4bda427
+msgid "Example"
+msgstr ""
+
+#: ../../networking/midonet.rst:63
+# 9b5539562d8347e5a40e744f9b8086e7
+msgid "midonet.apiserver.address"
+msgstr ""
+
+#: ../../networking/midonet.rst:63
+# a95222e0e61e4a3c9b250cd37d5cf298
+msgid "Specify the address at which the Midonet API server can be contacted"
+msgstr ""
+
+#: ../../networking/midonet.rst:63
+# 4188583e5177441b9821e4f5f89578a2
+msgid "http://192.168.1.144:8081/midolmanj-mgmt"
+msgstr ""
+
+#: ../../networking/midonet.rst:65
+# 665afa499ac44b54a7a8c0e53a749d66
+msgid "midonet.providerrouter.id"
+msgstr ""
+
+#: ../../networking/midonet.rst:65
+# 78c4feefb6d543d1ba12f3992e48e7fa
+msgid "Specifies the UUID of the Midonet provider router"
+msgstr ""
+
+#: ../../networking/midonet.rst:65
+# f7035c39c3a04d189249f37810cd413f
+msgid "d7c5e6a3-e2f4-426b-b728-b7ce6a0448e5"
+msgstr ""
+
+#: ../../networking/midonet.rst:68
+# 65914ae089bc4ab6ad82c66df94e9d49
+msgid "Table: CloudStack settings"
+msgstr ""
+
+#: ../../networking/midonet.rst:70
+# 20e830daf68a461a81d396114ad184ec
+msgid "We also want MidoNet to take care of public traffic, so in *componentContext.xml* we need to replace this line:"
+msgstr ""
+
+#: ../../networking/midonet.rst:78
+# 00b49b309af944c58397a9f4dbf0ff2a
+msgid "With this:"
+msgstr ""
+
+#: ../../networking/midonet.rst:85
+# 6c11d6b3c68e4451a5ca2b6c31e2c584
+msgid "On the compute host, MidoNet takes advantage of per-traffic type VIF driver support in CloudStack KVM."
+msgstr ""
+
+#: ../../networking/midonet.rst:88
+# d02ca0b479ba4720b56679504af434b7
+msgid "In agent.properties, we set the following to make MidoNet take care of Guest and Public traffic:"
+msgstr ""
+
+#: ../../networking/midonet.rst:96
+# 29db8f221b5641ea84be16cfdf0202f0
+msgid "This is explained further in MidoNet User Guide."
+msgstr ""
+
+#: ../../networking/midonet.rst:99
+# 3a516331b1ea440298354c98069645bb
+msgid "Enabling the MidoNet service provider via the UI"
+msgstr ""
+
+#: ../../networking/midonet.rst:101
+# 830c1e31051e44c98c0f34a05952b2f7
+msgid "To allow CloudStack to use the MidoNet Plugin the network service provider needs to be enabled on the physical network."
+msgstr ""
+
+#: ../../networking/midonet.rst:104
+# cb5416ba9cad4f6b82d36a759957167f
+msgid "The steps to enable via the UI are as follows:"
+msgstr ""
+
+#: ../../networking/midonet.rst:106
+# 3c9f034a471d460fa1e78d7fc0d23038
+msgid "In the left navbar, click Infrastructure"
+msgstr ""
+
+#: ../../networking/midonet.rst:108
+# bcb7494347d2406d87ebd01a0c91fb20
+msgid "In Zones, click View All"
+msgstr ""
+
+#: ../../networking/midonet.rst:110
+# 95f2fb5dc5884524a69094143f6bb76d
+msgid "Click the name of the Zone on which you are setting up MidoNet"
+msgstr ""
+
+#: ../../networking/midonet.rst:112
+# 188fd04a8ae145fda2c3a8c890d5462e
+msgid "Click the Physical Network tab"
+msgstr ""
+
+#: ../../networking/midonet.rst:114
+# 1e542d7390884d2bad2f3c47877542b1
+msgid "Click the Name of the Network on which you are setting up MidoNet"
+msgstr ""
+
+#: ../../networking/midonet.rst:116
+# aaaf74a3d52b42ebae8f4e88c8b40355
+msgid "Click Configure on the Network Service Providers box"
+msgstr ""
+
+#: ../../networking/midonet.rst:118
+# 04d5bfd6646f4a97989e347474116368
+msgid "Click on the name MidoNet"
+msgstr ""
+
+#: ../../networking/midonet.rst:120
+# 642adc3b1cf44faab16425e912c923f5
+msgid "Click the Enable Provider button in the Network tab"
+msgstr ""
+
+#: ../../networking/midonet.rst:123
+# cf7eda3b5d3f4866846e763c3caf4b70
+msgid "Enabling the MidoNet service provider via the API"
+msgstr ""
+
+#: ../../networking/midonet.rst:125
+# c59c00a7fa6f46119faf3eca40367b44
+msgid "To enable via the API, use the following API calls:"
+msgstr ""
+
+#: ../../networking/midonet.rst:127
+# 8282ec8f110b4fe89bffca6181a46725
+msgid "*addNetworkServiceProvider*"
+msgstr ""
+
+#: ../../networking/midonet.rst:129
+# 60147b795fda499aa9cf7558014d88d5
+msgid "name = \"MidoNet\""
+msgstr ""
+
+#: ../../networking/midonet.rst:131
+# bcc67ccf4214467e8e400256884b5a51
+msgid "physicalnetworkid = <the uuid of the physical network>"
+msgstr ""
+
+#: ../../networking/midonet.rst:133
+# ea8ad1ea1ce440f293268c6ce2be6c7d
+msgid "*updateNetworkServiceProvider*"
+msgstr ""
+
+#: ../../networking/midonet.rst:135
+# 4415a0b5d7c345c297f91727eda61212
+msgid "id = <the provider uuid returned by the previous call>"
+msgstr ""
+
+#: ../../networking/midonet.rst:137
+# df55f4d520bf4f90a9d0988e752af678
+msgid "state = \"Enabled\""
+msgstr ""
+
+#: ../../networking/midonet.rst:140
+#: ../../networking/nicira-plugin.rst:338
+#: ../../networking/ovs-plugin.rst:226
+# dfc989938200446f8f7792e0488afccf
+# 82db7e6f7b3144439a90257872b027ff
+# 05f9bc2018e743d09a919067bab537a8
+msgid "Revision History"
+msgstr ""
+
+#: ../../networking/midonet.rst:142
+# 65c949887213426e8c750fcc37c11160
+msgid "0-0 Wed Mar 13 2013 Dave Cahill dcahill@midokura.com Documentation created for 4.2.0 version of the MidoNet Plugin"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:2
+# 5a81d39c1e9e4666b11b0d2062315f8b
+msgid "The Nicira NVP Plugin"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:5
+# cb5aa76e8916452dbe92065c109fda58
+msgid "Introduction to the Nicira NVP Plugin"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:7
+# 0c134c3d04de4ba49f31e0c3f0108144
+msgid "The Nicira NVP plugin adds Nicira NVP as one of the available SDN implementations in CloudStack. With the plugin an exisiting Nicira NVP setup can be used by CloudStack to implement isolated guest networks and to provide additional services like routing and NAT."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:13
+# 5d2369e469d14a4d9cf445bcd893c1cc
+msgid "Features of the Nicira NVP Plugin"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:15
+# 6aff4bc970e04090b584058d98f39113
+msgid "The following table lists the CloudStack network services provided by the Nicira NVP Plugin."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:19
+#: ../../networking/ovs-plugin.rst:18
+# 618aa9ed3ee14e63890a722f29d34f8f
+# 0b2e8bbc17194ce1a6f82dd96bd13b78
+msgid "Network Service"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:19
+#: ../../networking/nicira-plugin.rst:38
+#: ../../networking/ovs-plugin.rst:18
+#: ../../networking/ovs-plugin.rst:37
+# d3962c8e69d44b74bd77cd1c575b7792
+# 8328a42be97a41c8aa575ee34b6fcf9b
+# dba6e8a2bae44ea484d6c5fe146e30f1
+# a31335a8c7454a1a8dd94f2772c9b0b2
+msgid "CloudStack version"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:19
+# f5d14881fe124e5ebcc4ac0f736bfbf8
+msgid "NVP version"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:21
+#: ../../networking/nicira-plugin.rst:151
+#: ../../networking/nicira-plugin.rst:183
+#: ../../networking/nicira-plugin.rst:265
+#: ../../networking/ovs-plugin.rst:20
+#: ../../networking/ovs-plugin.rst:181
+#: ../../networking/ovs-plugin.rst:215
+# 31df7547b72748daaa738f7796b5d45f
+# c61de43323664b898739f2d79f6353a2
+# be88317c512544d79d822bf5bcb8c7cc
+# 63f4305ccce749aa98ab4fca8ad01a7e
+# d08c3df5e050478e9e467de862f6212f
+# 7756125b529445188dfa228957dea3d5
+# 51b720e6b5b24589aafe127499b9815a
+msgid "Virtual Networking"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:21
+#: ../../networking/nicira-plugin.rst:40
+#: ../../networking/ovs-plugin.rst:20
+#: ../../networking/ovs-plugin.rst:39
+# 1f8de4ae2cf948f784c605ef8accd105
+# 1afbc018f09c416797709cef931c5b78
+# e2b0698af48b47659311b5f9c8c7d735
+# 2ccb535cbc8444d7b5f09a2531fad22a
+msgid ">= 4.0"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:21
+# 45109fe45d4c41c09733a1c206754e23
+msgid ">= 2.2.1"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:23
+#: ../../networking/nicira-plugin.rst:25
+#: ../../networking/nicira-plugin.rst:27
+#: ../../networking/nicira-plugin.rst:42
+# 7ab01a4140024745b65ddd03be090f5c
+# 574293701d7844b1971e1f620a2d75ac
+# 19f979d2da69435e9c609234c0ed80a1
+# 2754366ea78e49f78fb7f27bc85da121
+msgid ">= 4.1"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:23
+#: ../../networking/nicira-plugin.rst:25
+#: ../../networking/nicira-plugin.rst:27
+# 62a2875bd16e44409061c004560b584e
+# 1f25483790be4a13aa0f8d5d1c9516dc
+# e06ac671db424fee844691f37c4a0b4a
+msgid ">= 3.0.1"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:30
+#: ../../networking/ovs-plugin.rst:29
+# e54b61fd04a34850aa0d2c8836e91428
+# 03569648f6cf400a81547171df27afe6
+msgid "Table: Supported Services"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:32
+#: ../../networking/ovs-plugin.rst:31
+# fe134237dd3c41eeaf00bf7b5e90cd0b
+# 1e2ef00d06a148a7a074c4e8ad341963
+msgid "The Virtual Networking service was originally called 'Connectivity' in CloudStack 4.0"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:35
+# ed15aa5806314c3fb2f34341ec69e7b2
+msgid "The following hypervisors are supported by the Nicira NVP Plugin."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:38
+#: ../../networking/ovs-plugin.rst:37
+#: ../../networking/vxlan.rst:15
+# 6e79e2b14d884902adec144d58c0615b
+# 9dade5da23f44b52abad25189603005b
+# e127c87468024894ad783fbe0121c009
+msgid "Hypervisor"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:40
+#: ../../networking/ovs-plugin.rst:39
+# e5da1a2aebc84c168d9f5a3429e7be98
+# 8d14a15a62954f4587194401c7aa71d4
+msgid "XenServer"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:42
+#: ../../networking/ovs-plugin.rst:41
+#: ../../networking/vxlan.rst:15
+# 41413a228a0741fd8b8f0d7d541f1373
+# b0ff6e7152884e1792c9c977f7204b5d
+# f9510dd06b0040de93865b0d84796393
+msgid "KVM"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:45
+#: ../../networking/ovs-plugin.rst:44
+# d81b53ff53a44951a380e29b9c6db7df
+# 7196efd73f5a4c01bc053a00bc2e4d97
+msgid "Table: Supported Hypervisors"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:47
+# f63025ea491548c1bed572ab06439e2f
+msgid "Please refer to the Nicira NVP configuration guide on how to prepare the hypervisors for Nicira NVP integration."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:51
+# a0c72bc47354485cb25a1cf0d6b73bbb
+msgid "Configuring the Nicira NVP Plugin"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:56
+# 93da17b4cc344e97bf764847d0e20f12
+msgid "Before enabling the Nicira NVP plugin the NVP Controller needs to be configured. Please review the NVP User Guide on how to do that."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:59
+# 13a1a3abe3da4254bccf580f00103ca7
+msgid "Make sure you have the following information ready:"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:61
+# 524d6581dc15405f9b3304a7403faf24
+msgid "The IP address of the NVP Controller"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:63
+# a533d9652e3443849a8c2f21a6abd1a0
+msgid "The username to access the API"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:65
+# 70aa49763ae14501bffaf353e46ad140
+msgid "The password to access the API"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:67
+# dd7aa1c5a8b14a6ea68ab52a9bbc00c0
+msgid "The UUID of the Transport Zone that contains the hypervisors in this Zone"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:70
+# 1ecd9bc2a14b4726a1a7eec1331ba0ea
+msgid "The UUID of the Gateway Service used to provide router and NAT services."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:74
+# e25bf818aecf40409312b9add51d8914
+msgid "The gateway service uuid is optional and is used for Layer 3 services only (SourceNat, StaticNat and PortForwarding)"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:78
+#: ../../networking/ovs-plugin.rst:62
+# be1fb34770334288bc4f3e86eac3448e
+# a9d10c0c1d5b46ebb765172d5a41e610
+msgid "Zone Configuration"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:80
+# 245e6e002d5c4d448ca331c29392751f
+msgid "CloudStack needs to have at least one physical network with the isolation method set to \"STT\". This network should be enabled for the Guest traffic type."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:84
+# 6d8d7a099e344032b83c39376904b5c0
+msgid "The Guest traffic type should be configured with the traffic label that matches the name of the Integration Bridge on the hypervisor. See the Nicira NVP User Guide for more details on how to set this up in XenServer or KVM."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:94
+#: ../../networking/ovs-plugin.rst:141
+# 5adf72459a4d481a8a809a15a643954a
+# 3c583190756a4b1d8480134c93515228
+msgid "Enabling the service provider"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:96
+# f48b20ae59ea49ff8ab3e6b842c2f77f
+msgid "The Nicira NVP provider is disabled by default. Navigate to the \"Network Service Providers\" configuration of the physical network with the STT isolation type. Navigate to the Nicira NVP provider and press the \"Enable Provider\" button."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:101
+# d9006bf7e42e4a4caffb126799e04756
+msgid "CloudStack 4.0 does not have the UI interface to configure the Nicira NVP plugin. Configuration needs to be done using the API directly."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:110
+# 9d2d62d686ae4d9f83a1a1e9083c7974
+msgid "Device Management"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:112
+# cb620ac34ed6482f8820f59b902fdf9b
+msgid "In CloudStack a Nicira NVP setup is considered a \"device\" that can be added and removed from a physical network. To complete the configuration of the Nicira NVP plugin a device needs to be added to the physical network. Press the \"Add NVP Controller\" button on the provider panel and enter the configuration details."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:123
+#: ../../networking/ovs-plugin.rst:153
+# c68f6f105758477bb153fa55a6d89824
+# 541f0595f05f4f6b848945774fa978e6
+msgid "Network Offerings"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:125
+# c110a9dda09c4f5cbd4fe818ae3f9bd3
+msgid "Using the Nicira NVP plugin requires a network offering with Virtual Networking enabled and configured to use the NiciraNvp element. Typical use cases combine services from the Virtual Router appliance and the Nicira NVP plugin."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:131
+#: ../../networking/nicira-plugin.rst:169
+#: ../../networking/nicira-plugin.rst:245
+#: ../../networking/ovs-plugin.rst:161
+#: ../../networking/ovs-plugin.rst:199
+# d11f5b34530745449796c4378664d8f9
+# 1151cc3e359e4f3caf7029ad0e23ba9e
+# bae2c53a24aa4438a52b5425973327b5
+# abbb6c562b014227b3953d4cd5268e48
+# 6b44ce13956d476db147cbd7a82cb152
+msgid "Service"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:131
+#: ../../networking/nicira-plugin.rst:169
+#: ../../networking/nicira-plugin.rst:245
+#: ../../networking/ovs-plugin.rst:161
+#: ../../networking/ovs-plugin.rst:199
+# b7143394676041f3bc4c8ad0a8469195
+# fe1bb58eda974fc7abd9738556c892b1
+# ba2cc68f1ecc4542a40d411546b65af4
+# cf717075d6d74475b45d0fc2cd2058c5
+# 4d2a2b9215ef410ea5ebb21ad692af05
+msgid "Provider"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:133
+#: ../../networking/nicira-plugin.rst:247
+#: ../../networking/ovs-plugin.rst:163
+# b65b3ee91ca34d20946f693ce05d4034
+# 969ee76a22ee4bc5afeb620adbb41223
+# 7c03de44f9ec4344b9f9c7de192971cd
+msgid "VPN"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:133
+#: ../../networking/nicira-plugin.rst:135
+#: ../../networking/nicira-plugin.rst:137
+#: ../../networking/nicira-plugin.rst:139
+#: ../../networking/nicira-plugin.rst:141
+#: ../../networking/nicira-plugin.rst:143
+#: ../../networking/nicira-plugin.rst:145
+#: ../../networking/nicira-plugin.rst:147
+#: ../../networking/nicira-plugin.rst:149
+#: ../../networking/nicira-plugin.rst:171
+#: ../../networking/nicira-plugin.rst:173
+#: ../../networking/nicira-plugin.rst:175
+#: ../../networking/ovs-plugin.rst:163
+#: ../../networking/ovs-plugin.rst:165
+#: ../../networking/ovs-plugin.rst:167
+#: ../../networking/ovs-plugin.rst:169
+#: ../../networking/ovs-plugin.rst:173
+#: ../../networking/ovs-plugin.rst:175
+#: ../../networking/ovs-plugin.rst:201
+#: ../../networking/ovs-plugin.rst:203
+#: ../../networking/ovs-plugin.rst:205
+#: ../../networking/ovs-plugin.rst:207
+# 6bb38e5eff67483a80799e862b90a124
+# 777951d5dbd4419ca2a25e414bcc7591
+# d10b1e05ea064c9a91819119c8cbda9e
+# bf47cc26fa794985a7bf910d61248b21
+# e931c891651d43fcb8d27a57e0f7e8f9
+# 019b3d5bd11b48f2b10509ba58a380df
+# 5d337fd5e0d74eafbd860b79f190f32f
+# c6ca2df243a4423baf7a00847b8c50e2
+# 22ea972bf5064cf48bdbd8beab4574aa
+# 3af8c5a80e49430599c7f126f3b0c751
+# 0e0e35ffd2524ac4a956dc4bfb162948
+# 4a7f16dcf0434ae79b3dc9057050c06e
+# 1144b076cb5d4db99bb36f56afae9bac
+# 0a20026bac144d6ea321101034e427b0
+# 13f8ccfb544e4830b5ecd3b27c7ae757
+# 75f20c559a4e41dc9d6d4bd593a12e36
+# 57c3fd888a914375a37f95535d6d4a6b
+# 15446ee0c8e048898567bb5032a49f59
+# 25700ed7799f4cdca6f2685c84ea0fea
+# 9a644998b5e74fd9a41b518199f5ce34
+# c4e514a822f844f7bbd003be750ccac8
+# 27a0898b87144cb29250777f16082d9a
+msgid "VirtualRouter"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:137
+#: ../../networking/nicira-plugin.rst:173
+#: ../../networking/nicira-plugin.rst:251
+#: ../../networking/ovs-plugin.rst:167
+#: ../../networking/ovs-plugin.rst:203
+# bc5830c742c04ccb932d4a21bf61dfba
+# b5e769e11e364694ae8495a6f8141407
+# d68ae4be18c4489a8d7ad5dc21a239da
+# ad8f4409b4734bad99428c468d656f20
+# 28d60e4ec08644959d354bed45917592
+msgid "DNS"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:139
+#: ../../networking/ovs-plugin.rst:169
+# 5dbbf495e13c479486e733c1aaaee2b8
+# 20a037a6abbb429a975af056016135fa
+msgid "Firewall"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:141
+#: ../../networking/nicira-plugin.rst:253
+#: ../../networking/ovs-plugin.rst:171
+# dc7afd6a74b1471a8e123e41c26453fa
+# 5559e64b2a46440e8aa9901e19d33b92
+# f40748c9c69c4dc1bfce45c3fe98659d
+msgid "Load Balancer"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:143
+#: ../../networking/nicira-plugin.rst:175
+#: ../../networking/nicira-plugin.rst:255
+#: ../../networking/ovs-plugin.rst:173
+#: ../../networking/ovs-plugin.rst:205
+# b62a7e934b13466bbdfe5ad26d1dbf53
+# 885b162963ad48e6974ccd23426f57fa
+# 5fac16f4f2194d50a920361031fbc661
+# 5b5f0ec76735461b9a446a11ec469eb9
+# 0d6707ddaca049cfa168740106127322
+msgid "User Data"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:149
+#: ../../networking/nicira-plugin.rst:181
+#: ../../networking/nicira-plugin.rst:261
+#: ../../networking/ovs-plugin.rst:179
+#: ../../networking/ovs-plugin.rst:211
+# 8b82c6fa4c9c4cddb6f4c1ca8c0683a6
+# 065e08db00404b8f89b223fe90ab1b29
+# 1bb7705e53734ad99e28325655bcc586
+# 09d688dc773945f98c75862ba10ed000
+# a80e84a19fd946c3be08c3473e496973
+msgid "Post Forwarding"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:151
+#: ../../networking/nicira-plugin.rst:177
+#: ../../networking/nicira-plugin.rst:179
+#: ../../networking/nicira-plugin.rst:181
+#: ../../networking/nicira-plugin.rst:183
+#: ../../networking/nicira-plugin.rst:265
+#: ../../networking/nicira-plugin.rst:316
+# f79e81a377e24effb74f5f89551e3549
+# 3852e0bc80634ce7b88f50163b68d857
+# 87727014789943899c8e78513637d1ab
+# edd6581341c1480cbec0aa25d03d72b0
+# 2c64489bc4fe49dba21a248db0edf772
+# 50340451a1ad4b558a855a411fa9f9d0
+# 31ec210d01c5430cb7b65e64fc559a17
+msgid "NiciraNVP"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:154
+#: ../../networking/ovs-plugin.rst:184
+# d1bd6cbe9f5d42068d72ff50c7e82d79
+# c3f06b80ac50400aa7add1dbc7d55308
+msgid "Table: Isolated network offering with regular services from the Virtual Router."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:162
+# a78995044b664d38884f6e91114bc873
+msgid "The tag in the network offering should be set to the name of the physical network with the NVP provider."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:165
+#: ../../networking/ovs-plugin.rst:195
+# 1a00a98b97234956860ea67999daa3db
+# d5005e0409714e719720bdd204ef72ff
+msgid "Isolated network with network services. The virtual router is still required to provide network services like dns and dhcp."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:186
+#: ../../networking/ovs-plugin.rst:218
+# da5d426b8c74472aad063a8c695c4fd0
+# 38eeebf828e94e64b0973ab2a5940847
+msgid "Table: Isolated network offering with network services"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:189
+# 96d160fe57ea4da6a6f718f3daf6338d
+msgid "Using the Nicira NVP plugin with VPC"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:192
+# d1ec478dd3074e4e9c7b29606ea10ee6
+msgid "Supported VPC features"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:194
+# ba8e48822f2a46ca80ff6b208f107ca5
+msgid "The Nicira NVP plugin supports CloudStack VPC to a certain extent. Starting with CloudStack version 4.1 VPCs can be deployed using NVP isolated networks."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:198
+# d5f40344da8041c09b3571801e9ba1f2
+msgid "It is not possible to use a Nicira NVP Logical Router for as a VPC Router"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:201
+# f1c3905dd9c840398de7c1409b3357b8
+msgid "It is not possible to connect a private gateway using a Nicira NVP Logical Switch"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:205
+# 7065f8a39b504e49b39858dab512b447
+msgid "VPC Offering with Nicira NVP"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:207
+# 89ff2e7e4c8c49df8a8a155f80f6f70f
+msgid "To allow a VPC to use the Nicira NVP plugin to provision networks, a new VPC offering needs to be created which allows the Virtual Networking service to be implemented by NiciraNVP."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:211
+# bda837a0d67e4989ae3c409c9d35c475
+msgid "This is not currently possible with the UI. The API does provide the proper calls to create a VPC offering with Virtual Networking enabled. However due to a limitation in the 4.1 API it is not possible to select the provider for this network service. To configure the VPC offering with the NiciraNVP provider edit the database table 'vpc\\_offering\\_service\\_map' and change the provider to NiciraNvp for the service 'Connectivity'"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:219
+# ac4f3b0154084c0483a97ad89415e100
+msgid "It is also possible to update the default VPC offering by adding a row to the 'vpc\\_offering\\_service\\_map' with service 'Connectivity' and provider 'NiciraNvp'"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:228
+# 543b60828f814713b96ae87fc487ea48
+msgid "When creating a new VPC offering please note that the UI does not allow you to select a VPC offering yet. The VPC needs to be created using the API with the offering UUID."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:233
+# 22a1220a7f2c48968771c9d2290d2a02
+msgid "VPC Network Offerings"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:235
+# a08bef2a55e34b0e90b0626b1996943a
+msgid "The VPC needs specific network offerings with the VPC flag enabled. Otherwise these network offerings are identical to regular network offerings. To allow VPC networks with a Nicira NVP isolated network the offerings need to support the Virtual Networking service with the NiciraNVP provider."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:241
+# a385bb41b1aa473c9c44ad9b14c49d11
+msgid "In a typical configuration two network offerings need to be created. One with the loadbalancing service enabled and one without loadbalancing."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:247
+#: ../../networking/nicira-plugin.rst:249
+#: ../../networking/nicira-plugin.rst:251
+#: ../../networking/nicira-plugin.rst:253
+#: ../../networking/nicira-plugin.rst:255
+#: ../../networking/nicira-plugin.rst:257
+#: ../../networking/nicira-plugin.rst:259
+#: ../../networking/nicira-plugin.rst:261
+#: ../../networking/nicira-plugin.rst:263
+# d07087f1c69c455a834109561b0cfde2
+# 6530274146874b219df8e4775e3f6034
+# 5be193885d0b4645a68639153a591dcf
+# 9e3399ae187d4a58aff25d7c81205a34
+# 8a4e3ab19ca741e89aefb76bb9ba5ba7
+# 06565101b5a74ab48d6b91266e6ac9b1
+# 2e35b697aa564ccdbd28a8b573cd6c20
+# 31060b1bfc784f7085e25206b8ccd85b
+# 0980ef0687a8410c86496abb6b3e8a06
+msgid "VpcVirtualRouter"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:263
+# 00c30e3971c14821ae0ed06455eb5709
+msgid "NetworkACL"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:268
+# 519a6c52784246919dee03ed6e35eb4b
+msgid "Table: VPC Network Offering with Loadbalancing"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:271
+# 3a5f7b0d37ed456692acd60a4715d5c4
+msgid "Troubleshooting the Nicira NVP Plugin"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:274
+# 3fd7e8170bb64421911c19a02274bd53
+msgid "UUID References"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:276
+# 789d734c55d84be699048adbabf4dad3
+msgid "The plugin maintains several references in the CloudStack database to items created on the NVP Controller."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:279
+# edea32c3b89046ffa67ed4aea6bb7a6f
+msgid "Every guest network that is created will have its broadcast type set to Lswitch and if the network is in state \"Implemented\", the broadcast URI will have the UUID of the Logical Switch that was created for this network on the NVP Controller."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:284
+# 6b8e3360507443389cc13e1cd24a7fc2
+msgid "The Nics that are connected to one of the Logical Switches will have their Logical Switch Port UUID listed in the nicira\\_nvp\\_nic\\_map table"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:287
+# 1cebca6fd8304afe97371edf8d995d7e
+msgid "All devices created on the NVP Controller will have a tag set to domain-account of the owner of the network, this string can be used to search for items in the NVP Controller."
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:292
+# 6af46290da7d4824b2d5b357097fbd61
+msgid "Database tables"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:294
+# d5f5219626854f709e657fcd621767a6
+msgid "The following tables are added to the cloud database for the Nicira NVP Plugin"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:298
+#: ../../networking/nicira-plugin.rst:310
+#: ../../networking/nicira-plugin.rst:326
+# 53c8b3b2f25c4f47bbb53c7db9196b51
+# 0c142416faf547e4a149fa19d4a29f34
+# af2397e101774456b392ae473a8ac616
+msgid "id"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:298
+#: ../../networking/nicira-plugin.rst:310
+#: ../../networking/nicira-plugin.rst:326
+# 42bc0a25597f4099acca8c07abb0d47f
+# 6b9bf4f773774fccae37b49f7f45179d
+# ef7b099241fd44889d8af022a2c0d408
+msgid "auto incrementing id"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:300
+# a33c26507ef541d784a022a6d515e0f5
+msgid "logicalswitch"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:300
+# 75292eb7b6194cc9a7d194e1faec0388
+msgid "uuid of the logical switch this port is connected to"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:302
+# 668bf5ade1a2492b9cf0f6a15d1aa8b8
+msgid "logicalswitchport"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:302
+# 094b2c0685c34d8698ea4121fc4a88eb
+msgid "uuid of the logical switch port for this nic"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:304
+# cdb4155d3476483aa07c869bc8ac78b6
+msgid "nic"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:304
+# caecd436ae884261a3bfadede5ab9dce
+msgid "the CloudStack uuid for this nic, reference to the nics table"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:307
+# 6c10a96d48d84ae8b9190cb8c626b697
+msgid "Table: nicira\\_nvp\\_nic\\_map"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:312
+# 6eb2d75abc814d21b629814fbac9664e
+msgid "uuid"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:312
+# 34350d0d06cf4418b61a4cbe92abdf05
+msgid "UUID identifying this device"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:314
+# 935c6786ee0048d99f0c9dcb139ed85a
+msgid "physical\\_network\\_id"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:314
+# ea440688d7f643f6b11b83ca3a040128
+msgid "the physical network this device is configured on"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:316
+# cd3800860ac044f898a3245467008af5
+msgid "provider\\_name"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:318
+# 87bc5c5f703b4270a808133d3860792e
+msgid "device\\_name"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:318
+# 97ca0c7c7ea74734830b00d6ee3b614e
+msgid "display name for this device"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:320
+# 2baacc960233427e91829af5f967d22a
+msgid "host\\_id"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:320
+# 7d1bc27e2b5e4329864c15cca9089af6
+msgid "reference to the host table with the device configuration"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:323
+# f71a43d6ec914205a351c27e9432fa1b
+msgid "Table: external\\_nicira\\_nvp\\_devices"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:328
+# 30f1c62a6bc3479eaa3fca1c99a342cb
+msgid "logicalrouter\\_uuid"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:328
+# 24fc0e08e3844c049250201f0f5a6943
+msgid "uuid of the logical router"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:330
+# b654ff3c1d7b40ffb8cd27a0e5eb292f
+msgid "network\\_id"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:330
+# 5e919015c2e44058b7abcca55fdba0b3
+msgid "id of the network this router is linked to"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:333
+# 70287e5e55d24b1ab49f44b0dbb4f0f8
+msgid "Table: nicira\\_nvp\\_router\\_map"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:335
+# dde40d6b8f274f58b2ee49ac2d5e8ca1
+msgid "nicira\\_nvp\\_router\\_map is only available in CloudStack 4.1 and above"
+msgstr ""
+
+#: ../../networking/nicira-plugin.rst:340
+# 3698c81ecf44478bb41133498b56e83f
+msgid "0-0 Wed Oct 03 2012 Hugo Trippaers hugo@apache.org Documentation created for 4.0.0-incubating version of the NVP Plugin 1-0 Wed May 22 2013 Hugo Trippaers hugo@apache.org Documentation updated for CloudStack 4.1.0"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:2
+# 0c186222f32b4bbda715262783ba3cf7
+msgid "The OVS Plugin"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:5
+# 8063b6a753804137b6b5a38c53764c89
+msgid "Introduction to the OVS Plugin"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:7
+# 738b7d7d38ef40d097cb25594387ba11
+msgid "The OVS plugin is the native SDN implementations in CloudStack, using GRE isolation method. The plugin can be used by CloudStack to implement isolated guest networks and to provide additional services like NAT, port forwarding and load balancing."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:12
+# 8738288471674363afa921ecbaec1867
+msgid "Features of the OVS Plugin"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:14
+# e2c0a6c8d2a54c11ab038aea7437ee1c
+msgid "The following table lists the CloudStack network services provided by the OVS Plugin."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:22
+#: ../../networking/ovs-plugin.rst:24
+#: ../../networking/ovs-plugin.rst:26
+#: ../../networking/ovs-plugin.rst:41
+# 94b705d1919f42dc93ee3bde143cc9e4
+# a8bcd55c8af9483bab85a27e2e858463
+# c5adedbd9c034eebb5de1bd95a2782ad
+# d66b2462d1d74e5dba6272e9ca905e7b
+msgid ">= 4.3"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:26
+#: ../../networking/ovs-plugin.rst:213
+# 1c98b0381c96437a88b133d8ac4fc504
+# 3870fad2a1c2490e91bada596aa92f94
+msgid "Load Balancing"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:34
+# ab32a538a9b2476abf00b78f369ad247
+msgid "The following hypervisors are supported by the OVS Plugin."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:48
+# d1f299f091ce45a3b5596dc0a9a978f1
+msgid "Configuring the OVS Plugin"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:53
+# a5997f6fd754488ba5c92e4603cf1c1f
+msgid "Before enabling the OVS plugin the hypervisor needs to be install OpenvSwitch. Default, XenServer has already installed OpenvSwitch. However, you must install OpenvSwitch manually on KVM. CentOS 6.4 and OpenvSwitch 1.10 are recommended."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:55
+# 42c5d4f701cd475f82263345ed2643f8
+msgid "KVM hypervisor:"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:57
+# ff6b9ce75064465faf40f28294a4a4d2
+msgid "CentOS 6.4 is recommended."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:58
+# aec6d4e64ef34c9785419abc0d40a4ff
+msgid "To make sure that the native bridge module will not interfere with openvSwitch the bridge module should be added to the blacklist. See the modprobe documentation for your distribution on where to find the blacklist. Make sure the module is not loaded either by rebooting or executing rmmod bridge before executing next steps."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:64
+# 59bc3e26166b49929ac57352426c0e1b
+msgid "CloudStack needs to have at least one physical network with the isolation method set to “GRE”. This network should be enabled for the Guest traffic type."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:69
+# 577a289d75244f688fe34676d433f6cf
+msgid "With KVM, the traffic type should be configured with the traffic label that matches the name of the Integration Bridge on the hypervisor. For example, you should set the traffic label as following: - Management & Storage traffic: cloudbr0 - Guest & Public traffic: cloudbr1 See KVM networking configuration guide for more detail."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:81
+# 37d246b9af8c4143b25810d171f5673e
+msgid "Agent Configuration"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:83
+# e95ef7c66b834737824020929e57a510
+msgid "Only for KVM hypervisor"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:85
+# 198013b8c9c5432ab8c266399deacab1
+msgid "Configure network interfaces:"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:133
+# 9af721992b2946409aef0299c78bef7e
+msgid "Edit /etc/cloudstack/agent/agent.properties"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:143
+# 682ec9ff48d647e7a1202dcef28c0ee7
+msgid "The OVS provider is disabled by default. Navigate to the \"Network Service Providers\" configuration of the physical network with the GRE isolation type. Navigate to the OVS provider and press the \"Enable Provider\" button."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:155
+# 840e28ff519d454cb23bab644b4b6ec2
+msgid "Using the OVS plugin requires a network offering with Virtual Networking enabled and configured to use the OVS element. Typical use cases combine services from the Virtual Router appliance and the OVS plugin."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:171
+#: ../../networking/ovs-plugin.rst:177
+#: ../../networking/ovs-plugin.rst:179
+#: ../../networking/ovs-plugin.rst:181
+#: ../../networking/ovs-plugin.rst:209
+#: ../../networking/ovs-plugin.rst:211
+#: ../../networking/ovs-plugin.rst:213
+#: ../../networking/ovs-plugin.rst:215
+# 1d3b225edb8b482d8c582f632dc71313
+# ebdef897609040a283a250c5c1eb4151
+# b6ca83ff9ff7470ebc1a3af094449997
+# 32cdce0ada9d4fad837c1757dfe00cb6
+# cb5fd652d72044879d30e2b4818b3f15
+# c84ee4d20f7c48c488cbb6ed7a552ab3
+# dcc48e27341c45c2a35622f24fd2e194
+# f8560d7a491c4087a8e64879c3cb7d16
+msgid "OVS"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:192
+# 849b742162ee49498b9dd99abddfcda0
+msgid "The tag in the network offering should be set to the name of the physical network with the OVS provider."
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:221
+# 231676daf7d6469585cec8201d618078
+msgid "Using the OVS plugin with VPC"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:223
+# aa4e41d6c1444a668af3748de69e5281
+msgid "OVS plugin does not work with VPC at that time"
+msgstr ""
+
+#: ../../networking/ovs-plugin.rst:228
+# f8d4fdca37ad453c9e9d478e4bcd1e63
+msgid "0-0 Mon Dec 2 2013 Nguyen Anh Tu tuna@apache.org Documentation created for 4.3.0 version of the OVS Plugin"
+msgstr ""
+
+#: ../../networking/vxlan.rst:2
+# aba9a0debf774aa0944cb432adf8ef5d
+msgid "The VXLAN Plugin"
+msgstr ""
+
+#: ../../networking/vxlan.rst:5
+# 7e47773835b34f62b638c9063c13ac0d
+msgid "System Requirements for VXLAN"
+msgstr ""
+
+#: ../../networking/vxlan.rst:7
+# 0856b955a54e4897a16abb275756a9fd
+msgid "In PRODUCT 4.X.0, this plugin only supports the KVM hypervisor with the standard linux bridge."
+msgstr ""
+
+#: ../../networking/vxlan.rst:10
+# 3d2b1751d05a45d9a07403171f7f5925
+msgid "The following table lists the requirements for the hypervisor."
+msgstr ""
+
+#: ../../networking/vxlan.rst:13
+# cf661800742e45b78795a27fc183b902
+msgid "Item"
+msgstr ""
+
+#: ../../networking/vxlan.rst:13
+# 819ffab2f6da41e09ffcda38bcfe555e
+msgid "Requirement"
+msgstr ""
+
+#: ../../networking/vxlan.rst:13
+#: ../../networking/vxlan.rst:30
+# 43dad0f458fd4256af5210266203e63e
+# c2000a1583f74039ba4e81e33d1bfb4f
+msgid "Note"
+msgstr ""
+
+#: ../../networking/vxlan.rst:15
+# e5bde3c30dc5441eb12a4ec4b45e7060
+msgid "OvsVifDriver is not supported by this plugin in PRODUCT 4.X, use BridgeVifDriver (default)."
+msgstr ""
+
+#: ../../networking/vxlan.rst:17
+# 3911379ce0704038bd265efc35b968d5
+msgid "Linux kernel"
+msgstr ""
+
+#: ../../networking/vxlan.rst:17
+# 0481712b141d4f3e94139b17db34afd5
+msgid "version >= 3.7, VXLAN kernel module enabled"
+msgstr ""
+
+#: ../../networking/vxlan.rst:17
+# 09493271ea8b4c26b832bf6444ecc41c
+msgid "It is recommended to use kernel >=3.9, since Linux kernel categorizes the VXLAN driver as experimental <3.9."
+msgstr ""
+
+#: ../../networking/vxlan.rst:19
+# 5aeec29ada874c7399081093439a08b4
+msgid "iproute2"
+msgstr ""
+
+#: ../../networking/vxlan.rst:19
+# e8eb5592e8704feb9938a222c6bd37a9
+msgid "matches kernel version"
+msgstr ""
+
+#: ../../networking/vxlan.rst:22
+# 752c3ff3115d4533938927673fc8256e
+msgid "Table: Hypervisor Requirement for VXLAN"
+msgstr ""
+
+#: ../../networking/vxlan.rst:25
+# 972f006525e946c7a239d2ebaecca487
+msgid "Linux Distributions that meet the requirements"
+msgstr ""
+
+#: ../../networking/vxlan.rst:27
+# db3d7314090e428dbd26878e44b96698
+msgid "The following table lists distributions which meet requirements."
+msgstr ""
+
+#: ../../networking/vxlan.rst:30
+# e489f83c058d4843b0edddf4d5f7ed80
+msgid "Distribution"
+msgstr ""
+
+#: ../../networking/vxlan.rst:30
+# a6be099619614c06ac446220c77210a8
+msgid "Release Version"
+msgstr ""
+
+#: ../../networking/vxlan.rst:30
+# 7aa86d66ab7f4d9c8cf8188e6f9f021f
+msgid "Kernel Version (Date confirmed)"
+msgstr ""
+
+#: ../../networking/vxlan.rst:32
+# e9ecad2cccc74cb7aa00b46a5e3a0570
+msgid "Ubuntu"
+msgstr ""
+
+#: ../../networking/vxlan.rst:32
+# edbdd7c57081462e8d40ef0d9656151d
+msgid "13.04"
+msgstr ""
+
+#: ../../networking/vxlan.rst:32
+# 29f1312a9ae74bb99e6a7ec4c3693240
+msgid "3.8.0 (2013/07/23)"
+msgstr ""
+
+#: ../../networking/vxlan.rst:34
+# 5cd45188355b4d0eb21163ec4a720324
+msgid "Fedora"
+msgstr ""
+
+#: ../../networking/vxlan.rst:34
+# 34d9f4bac41e4a0691bcc15d3ee2468a
+msgid ">= 17"
+msgstr ""
+
+#: ../../networking/vxlan.rst:34
+# daff7db17c0042bb9cf674241df52912
+msgid "3.9.10 (2013/07/23)"
+msgstr ""
+
+#: ../../networking/vxlan.rst:34
+# 3008367b713047198803fa848a0ee4db
+msgid "Latest kernel packages are available in \"update\" repository."
+msgstr ""
+
+#: ../../networking/vxlan.rst:36
+# a2d7c1bb423341cca75ddda74037bdb1
+msgid "CentOS"
+msgstr ""
+
+#: ../../networking/vxlan.rst:36
+# 02acedd346e5464dbc4493b0f3ff205b
+msgid ">= 6.5"
+msgstr ""
+
+#: ../../networking/vxlan.rst:36
+# f87b94fed04c4aa6a0022f519a578d18
+msgid "2.6.32-431.3.1.el6.x86\\_64 (2014/01/21)"
+msgstr ""
+
+#: ../../networking/vxlan.rst:39
+# 164f35e12f76425285cbc95de79c38e9
+msgid "Table: List of Linux distributions which meet the hypervisor requirements"
+msgstr ""
+
+#: ../../networking/vxlan.rst:43
+# eca34e237e7347a982fefa12a663cc49
+msgid "Check the capability of your system"
+msgstr ""
+
+#: ../../networking/vxlan.rst:45
+# 23645375c0fe4e68a7096b4418965490
+msgid "To check the capability of your system, execute the following commands."
+msgstr ""
+
+#: ../../networking/vxlan.rst:59
+# 08ea45b15b224cedbd7c5b25ee9d8fb2
+msgid "Advanced: Build kernel and iproute2"
+msgstr ""
+
+#: ../../networking/vxlan.rst:61
+# 50467500d4d54ffe8e06d413c70fc679
+msgid "Even if your system doesn't support VXLAN, you can compile the kernel and iproute2 by yourself. The following procedure is an example for CentOS 6.4."
+msgstr ""
+
+#: ../../networking/vxlan.rst:66
+# 3cbc89b3e65049b5a8af5067dfd3b12f
+msgid "Build kernel"
+msgstr ""
+
+#: ../../networking/vxlan.rst:116
+# 96113e7068244ddcbc74d0628b23b864
+msgid "Build iproute2"
+msgstr ""
+
+#: ../../networking/vxlan.rst:134
+# 13971197a0884005b1bbec7e88751a55
+msgid "Please use rebuild kernel and tools at your own risk."
+msgstr ""
+
+#: ../../networking/vxlan.rst:137
+# 6082e428d1cb4b658d787c71d0ad1dd5
+msgid "Configure PRODUCT to use VXLAN Plugin"
+msgstr ""
+
+#: ../../networking/vxlan.rst:140
+# 51018b2e8a20496c95143f40c4c2e7b1
+msgid "Configure hypervisor"
+msgstr ""
+
+#: ../../networking/vxlan.rst:143
+# 1bda3ef5767243159c1f32723071aedf
+msgid "Configure hypervisor: KVM"
+msgstr ""
+
+#: ../../networking/vxlan.rst:145
+# 0b30975586c54132a8722bffbd37f88d
+msgid "In addition to \"KVM Hypervisor Host Installation\" in \"PRODUCT Installation Guide\", you have to configure the following item on the host."
+msgstr ""
+
+#: ../../networking/vxlan.rst:150
+# e86c1c67cbc246b284db4bdc68b79c64
+msgid "Create bridge interface with IPv4 address"
+msgstr ""
+
+#: ../../networking/vxlan.rst:152
+# 6856ea7ca74549fb91a97823fda39f40
+msgid "This plugin requires an IPv4 address on the KVM host to terminate and originate VXLAN traffic. The address should be assinged to a physical interface or a bridge interface bound to a physical interface. Both a private address or a public address are fine for the purpose. It is not required to be in the same subnet for all hypervisors in a zone, but they should be able to reach each other via IP multicast with UDP/8472 port. A name of a physical interface or a name of a bridge interface bound to a physical interface can be used as a traffic label. Physical interface name fits for almost all cases, but if physical interface name differs per host, you may use a bridge to set a same name. If you would like to use a bridge name as a traffic label, you may create a bridge in this way."
+msgstr ""
+
+#: ../../networking/vxlan.rst:165
+# 43bd2f0570fd4eaab96d1220d515286a
+msgid "Let ``cloudbr1`` be the bridge interface for the instances' private network."
+msgstr ""
+
+#: ../../networking/vxlan.rst:169
+#: ../../networking/vxlan.rst:288
+# 8ee47f12c6e140c29727a53e1411a9ff
+# a92bdc6a59d1445bb35f02ae1bbf2ff8
+msgid "Configure in RHEL or CentOS"
+msgstr ""
+
+#: ../../networking/vxlan.rst:171
+# 625b6babbbe14c7297b1db229a8e1bae
+msgid "When you configured the ``cloudbr1`` interface as below,"
+msgstr ""
+
+#: ../../networking/vxlan.rst:190
+#: ../../networking/vxlan.rst:246
+# 904e121f26a14fde81c4de98e7b24c0e
+# 6cf0b410f0a8449d8e65149baf7ce094
+msgid "you would change the configuration similar to below."
+msgstr ""
+
+#: ../../networking/vxlan.rst:207
+#: ../../networking/vxlan.rst:318
+# db9a28a25978461db08f0fdf995ea8c3
+# 00e194cf8c824537a2b5b8e26458dd30
+msgid "Configure in Ubuntu"
+msgstr ""
+
+#: ../../networking/vxlan.rst:209
+# 2a74cc1f2afd4082bdbf0ba50f6a629f
+msgid "When you configured ``cloudbr1`` as below,"
+msgstr ""
+
+#: ../../networking/vxlan.rst:282
+# cbe3d7f5a83f4d898797c7e80eb79049
+msgid "Configure iptables to pass XVLAN packets"
+msgstr ""
+
+#: ../../networking/vxlan.rst:284
+# 2f4c96bb0b4e40dfbdab9874f6891a33
+msgid "Since VXLAN uses UDP packet to forward encapsulated the L2 frames, UDP/8472 port must be opened."
+msgstr ""
+
+#: ../../networking/vxlan.rst:290
+# 22017b1c949f41099cfc19e25c2322c1
+msgid "RHEL and CentOS use iptables for firewalling the system, you can open extra ports by executing the following iptable commands:"
+msgstr ""
+
+#: ../../networking/vxlan.rst:298
+# 494b6216726d4b41ac1143c03c93ede2
+msgid "These iptable settings are not persistent accross reboots, we have to save them first."
+msgstr ""
+
+#: ../../networking/vxlan.rst:306
+#: ../../networking/vxlan.rst:332
+# e4c7fa92a9c0468e8da1450958c88fba
+# 65ea92e3dff5470387625254bb1c42db
+msgid "With this configuration you should be able to restart the network, although a reboot is recommended to see if everything works properly."
+msgstr ""
+
+#: ../../networking/vxlan.rst:315
+#: ../../networking/vxlan.rst:341
+# 2d1c77a3ce254c0eb8fac95e5895d8ae
+# 765412ce099b4da18bc65bc977dacabd
+msgid "Make sure you have an alternative way like IPMI or ILO to reach the machine in case you made a configuration error and the network stops functioning!"
+msgstr ""
+
+#: ../../networking/vxlan.rst:320
+# 854fd1560d9344e8ac82043d2db28452
+msgid "The default firewall under Ubuntu is UFW (Uncomplicated FireWall), which is a Python wrapper around iptables."
+msgstr ""
+
+#: ../../networking/vxlan.rst:323
+# f90c18bbf2c14a2394917bc8afb0d9fe
+msgid "To open the required ports, execute the following commands:"
+msgstr ""
+
+#: ../../networking/vxlan.rst:330
+# 88a38bd1e33c46929e6fc18a9447362a
+msgid "By default UFW is not enabled on Ubuntu. Executing these commands with the firewall disabled does not enable the firewall."
+msgstr ""
+
+#: ../../networking/vxlan.rst:344
+# 55f975bbaf7f4dffa989e42598176360
+msgid "Setup zone using VXLAN"
+msgstr ""
+
+#: ../../networking/vxlan.rst:346
+# 151a7ea2c74744eeb7e1c0a2c6efa55e
+msgid "In almost all parts of zone setup, you can just follow the advanced zone setup istruction in \"PRODUCT Installation Guide\" to use this plugin. It is not required to add a network element nor to reconfigure the network offering. The only thing you have to do is configure the physical network to use VXLAN as the isolation method for Guest Network."
+msgstr ""
+
+#: ../../networking/vxlan.rst:353
+# b98161ffc6e94d978fedfabfa111e148
+msgid "Configure the physical network"
+msgstr ""
+
+#: ../../networking/vxlan.rst:357
+# 90b276bf94d1402aa0ee2596f2721705
+msgid "CloudStack needs to have one physical network for Guest Traffic with the isolation method set to \"VXLAN\"."
+msgstr ""
+
+#: ../../networking/vxlan.rst:362
+# 280cd3cc511c4f9da067fdd49db6975c
+msgid "Guest Network traffic label should be the name of the physical interface or the name of the bridge interface and the bridge interface and they should have an IPv4 address. See ? for details."
+msgstr ""
+
+#: ../../networking/vxlan.rst:367
+# d5a846d9f8a148b49d60346f4b1adfb5
+msgid "Configure the guest traffic"
+msgstr ""
+
+#: ../../networking/vxlan.rst:371
+# c1b08286a7fc47958c0620ea96d11201
+msgid "Specify a range of VNIs you would like to use for carrying guest network traffic."
+msgstr ""
+
+#: ../../networking/vxlan.rst:374
+# aa3c048fba4b4a53a4bb2e3016f33a1f
+msgid "VNI must be unique per zone and no duplicate VNIs can exist in the zone. Exercise care when designing your VNI allocation policy."
+msgstr ""
+
diff --git a/source/conceptsandterminology/locale/pot/plugins.pot b/source/conceptsandterminology/locale/pot/plugins.pot
new file mode 100644
index 0000000..54cbfa3
--- /dev/null
+++ b/source/conceptsandterminology/locale/pot/plugins.pot
@@ -0,0 +1,783 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 13:49-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../plugins.rst:2
+# 379a7814be5a45bcadcc0fd536656b4f
+msgid "Plugins"
+msgstr ""
+
+#: ../../plugins.rst:6
+# 276ba73433bd44b49f3176b4fdcaf5a9
+msgid "Storage Plugins"
+msgstr ""
+
+#: ../../plugins.rst:8
+# 358954e5ae1b4bca9b9314f8cbd00da8
+msgid "This section gives an outline of how to implement a plugin to integrate a third-party storage provider. For details and an example, you will need to read the code."
+msgstr ""
+
+#: ../../plugins.rst:12
+# bcbf1c53396a440f8f0a50ed5591f57b
+msgid "Example code is available at: `plugins/storage/volume/sample`"
+msgstr ""
+
+#: ../../plugins.rst:14
+# 7943819f1f8a49bfb21b6aedfc6864dd
+msgid "Third party storage providers can integrate with CloudStack to provide either primary storage or secondary storage. For example, CloudStack provides plugins for Amazon Simple Storage Service (S3) or OpenStack Object Storage (Swift). The S3 plugin can be used for any object storage that supports the Amazon S3 interface."
+msgstr ""
+
+#: ../../plugins.rst:20
+# e8a7044f1e9642cea286930007548cff
+msgid "Additional third party object storages that do not support the S3 interface can be integrated with CloudStack by writing plugin software that uses the object storage plugin framework. Several new interfaces are available so that storage providers can develop vendor-specific plugins based on well-defined contracts that can be seamlessly managed by CloudStack."
+msgstr ""
+
+#: ../../plugins.rst:27
+# 0a515957cb6e4b4bbe92c1331577f84f
+msgid "Artifacts such as templates, ISOs and snapshots are kept in storage which CloudStack refers to as secondary storage. To improve scalability and performance, as when a number of hosts access secondary storage concurrently, object storage can be used for secondary storage. Object storage can also provide built-in high availability capability. When using object storage, access to secondary storage data can be made available across multiple zones in a region. This is a huge benefit, as it is no longer necessary to copy templates, snapshots etc. across zones as would be needed in an environment using only zone-based NFS storage."
+msgstr ""
+
+#: ../../plugins.rst:37
+# 6648eb6e267b443f83e38ff557fa9dcd
+msgid "The user enables a storage plugin through the UI. A new dialog box choice is offered to select the storage provider. Depending on which provider is selected, additional input fields may appear so that the user can provide the additional details required by that provider, such as a user name and password for a third-party storage account."
+msgstr ""
+
+#: ../../plugins.rst:44
+# 79590964b2d94df7b8ee961a9f0e1c77
+msgid "Overview of How to Write a Storage Plugin"
+msgstr ""
+
+#: ../../plugins.rst:46
+# 81da42c9a3fd43a6ae81de0def33d980
+msgid "To add a third-party storage option to CloudStack, follow these general steps (explained in more detail later in this section):"
+msgstr ""
+
+#: ../../plugins.rst:49
+# a59f1b6a6401428b8df44ef5c815b529
+msgid "Implement the following interfaces in Java:"
+msgstr ""
+
+#: ../../plugins.rst:51
+# d4706d7bd37f4ecfb17e700d567de04b
+msgid "DataStoreDriver"
+msgstr ""
+
+#: ../../plugins.rst:53
+# 4059bcbbcc9f42aea6d8eaaff7e19d45
+msgid "DataStoreLifecycle"
+msgstr ""
+
+#: ../../plugins.rst:55
+# cd23139c1ca9496f95616a6447c7982f
+msgid "DataStoreProvider"
+msgstr ""
+
+#: ../../plugins.rst:57
+# 0b42430ad6754a7cb5d98d5ef1b9cfbb
+msgid "VMSnapshotStrategy (if you want to customize the VM snapshot functionality)"
+msgstr ""
+
+#: ../../plugins.rst:60
+# 58743ad0ef874f8a82ec02659f100b2c
+msgid "Hardcode your plugin's required additional input fields into the code for the Add Secondary Storage or Add Primary Storage dialog box."
+msgstr ""
+
+#: ../../plugins.rst:63
+# 3db5b1bcf41c43d2b41395ec10bb9f0a
+msgid "Place your .jar file in `plugins/storage/volume/` or `plugins/storage/image/`."
+msgstr ""
+
+#: ../../plugins.rst:65
+# cb55ad5ab266458ca52e817fff92e46c
+msgid "Edit `/client/tomcatconf/componentContext.xml.in`."
+msgstr ""
+
+#: ../../plugins.rst:67
+# eb20fc9877d64f35ab554e9466f4658f
+msgid "Edit `client/pom.xml`."
+msgstr ""
+
+#: ../../plugins.rst:70
+# 9688b201ec7a44d9bec3f68a3834f661
+msgid "Implementing DataStoreDriver"
+msgstr ""
+
+#: ../../plugins.rst:72
+# 6b45021dacd74b4db08570aca747baaf
+msgid "DataStoreDriver contains the code that CloudStack will use to provision the object store, when needed."
+msgstr ""
+
+#: ../../plugins.rst:75
+#: ../../plugins.rst:99
+#: ../../plugins.rst:118
+# 110e2faf453d4019acc78dc1de958e03
+# 50d2a350ffdd446ebed3501451547a93
+# 36623b0788e84ae7b8fe9cbaa8793214
+msgid "You must implement the following methods:"
+msgstr ""
+
+#: ../../plugins.rst:77
+# 978b91799e7a441483f89ee5094951c7
+msgid "getTO()"
+msgstr ""
+
+#: ../../plugins.rst:79
+# c5f4d5267f494a3d8103694ff97230cc
+msgid "getStoreTO()"
+msgstr ""
+
+#: ../../plugins.rst:81
+# ceab640d5f294e33b654eeb341a236f6
+msgid "createAsync()"
+msgstr ""
+
+#: ../../plugins.rst:83
+# d40f5f65b6c142e3982b32e617d13ee1
+msgid "deleteAsync()"
+msgstr ""
+
+#: ../../plugins.rst:85
+#: ../../plugins.rst:135
+# 1c581d60ec8f437b946609e5005d4615
+# 6ee9c079baf14294b50ac646b0b17148
+msgid "The following methods are optional:"
+msgstr ""
+
+#: ../../plugins.rst:87
+# a4ddd58fad6a4efab4f54031b45b1895
+msgid "resize()"
+msgstr ""
+
+#: ../../plugins.rst:89
+# 07a3e3904a8f4e23ab9d2719ceadc3bb
+msgid "canCopy() is optional. If you set it to true, then you must implement copyAsync()."
+msgstr ""
+
+#: ../../plugins.rst:93
+# dfa07e5db908457d8cf4ab3ea629351f
+msgid "Implementing DataStoreLifecycle"
+msgstr ""
+
+#: ../../plugins.rst:95
+# 3508baad34c349f18bee1a469dbdd2f4
+msgid "DataStoreLifecycle contains the code to manage the storage operations for ongoing use of the storage. Several operations are needed, like create, maintenance mode, delete, etc."
+msgstr ""
+
+#: ../../plugins.rst:101
+# be7eccc5cbf94427ab62c3ac621e0904
+msgid "initialize()"
+msgstr ""
+
+#: ../../plugins.rst:103
+# 05c12b7857f9409a85b667444db0bf4b
+msgid "maintain()"
+msgstr ""
+
+#: ../../plugins.rst:105
+# e2cdf5a6cbfc40df9637fbd1625d0739
+msgid "cancelMaintain()"
+msgstr ""
+
+#: ../../plugins.rst:107
+# c531bef6c8934f778fd67919afa4e0b2
+msgid "deleteDataStore()"
+msgstr ""
+
+#: ../../plugins.rst:109
+# a37c6307cd0243c795a40ca093011f09
+msgid "Implement one of the attach\\*() methods depending on what scope you want the storage to have: attachHost(), attachCluster(), or attachZone()."
+msgstr ""
+
+#: ../../plugins.rst:114
+# 8dfafd1749a144f7889ee0f225b66288
+msgid "Implementing DataStoreProvider"
+msgstr ""
+
+#: ../../plugins.rst:116
+# b7400386153243b39742ffb719dda277
+msgid "DataStoreProvider contains the main code of the data store."
+msgstr ""
+
+#: ../../plugins.rst:120
+# d46222d7926a42f19c4b4716e4afc608
+msgid "getDatastoreLifeCycle()"
+msgstr ""
+
+#: ../../plugins.rst:122
+# a69737a8b6ab40d39e67a74c899e5574
+msgid "getDataStoreDriver()"
+msgstr ""
+
+#: ../../plugins.rst:124
+# ce12672ec9844f7c8d88a9d3871e8bdd
+msgid "getTypes(). Returns one or more types of storage for which this data store provider can be used. For secondary object storage, return IMAGE, and for a Secondary Staging Store, return ImageCache."
+msgstr ""
+
+#: ../../plugins.rst:128
+# 683ccb9981724336886a1597876d99da
+msgid "configure(). First initialize the lifecycle implementation and the driver implementation, then call registerDriver() to register the new object store provider instance with CloudStack."
+msgstr ""
+
+#: ../../plugins.rst:132
+# 6eae2e2f3984408d83382a7e643ac1ea
+msgid "getName(). Returns the unique name of your provider; for example, this can be used to get the name to display in the UI."
+msgstr ""
+
+#: ../../plugins.rst:137
+# 1d479396becb4f31907471b9247b47cf
+msgid "getHostListener() is optional; it's for monitoring the status of the host."
+msgstr ""
+
+#: ../../plugins.rst:141
+# 52eaa6fa0b484432a9bd1bbc77a5c37d
+msgid "Implementing VMSnapshotStrategy"
+msgstr ""
+
+#: ../../plugins.rst:143
+# 9ad0037ad86d4a1b8d1f135cefbbc6c5
+msgid "VMSnapshotStrategy has the following methods:"
+msgstr ""
+
+#: ../../plugins.rst:145
+# 20970991ba784f3b9d54cf1cfe12f8e6
+msgid "takeVMSnapshot()"
+msgstr ""
+
+#: ../../plugins.rst:147
+# 9bff86587100420e93573c9bee23e992
+msgid "deleteVMSnapshot()"
+msgstr ""
+
+#: ../../plugins.rst:149
+# 3a52e11272284484a6e72f035dee36c8
+msgid "revertVMSnapshot()"
+msgstr ""
+
+#: ../../plugins.rst:151
+# f3306e4fc05f4c4fb6065e8be9ae7790
+msgid "canHandle(). For a given VM snapshot, tells whether this implementation of VMSnapshotStrategy can handle it."
+msgstr ""
+
+#: ../../plugins.rst:155
+# 992261ff6c7e418da8e50ffc311bdd92
+msgid "Place the .jar File in the Right Directory"
+msgstr ""
+
+#: ../../plugins.rst:157
+# 525e7141d0414c5990833d09bda59b48
+msgid "For a secondary storage plugin, place your .jar file here:"
+msgstr ""
+
+#: ../../plugins.rst:163
+# 95400fb6d085440797180cf692b4bf94
+msgid "For a primary storage plugin, place your .jar file here:"
+msgstr ""
+
+#: ../../plugins.rst:170
+# f9bace45b78d4ca1b3581f1978438637
+msgid "Edit Configuration Files"
+msgstr ""
+
+#: ../../plugins.rst:172
+# 076d6a8e32c547ef9774ce76b6956107
+msgid "First, edit the following file tell CloudStack to include your .jar file. Add a line to this file to tell the CloudStack Management Server that it now has a dependency on your code:"
+msgstr ""
+
+#: ../../plugins.rst:180
+# 41863713ce5b44af8daa29b52ea9b884
+msgid "Place some facts about your code in the following file so CloudStack can run it:"
+msgstr ""
+
+#: ../../plugins.rst:187
+# b918b6ed56d140ff8013cb47574e0e42
+msgid "In the section “Deployment configurations of various adapters,” add this:"
+msgstr ""
+
+#: ../../plugins.rst:194
+# 30190892871c43188cf466ccd65f65d7
+msgid "In the section “Storage Providers,” add this:"
+msgstr ""
+
+#: ../../plugins.rst:203
+# 2ae7b51840ee4af992fc223832fc4671
+msgid "Minimum Required Interfaces"
+msgstr ""
+
+#: ../../plugins.rst:205
+# 8b945071a1ca4028a8e4d66b660e9a37
+msgid "The classes, interfaces, and methods used by CloudStack from the Amazon Web Services (AWS) Java SDK are listed in this section. An object storage that supports the S3 interface is minimally required to support the below in order to be compatible with CloudStack."
+msgstr ""
+
+#: ../../plugins.rst:211
+# 608dc2680b3647418a090b59602e0fae
+msgid "Interface AmazonS3"
+msgstr ""
+
+#: ../../plugins.rst:213
+# aee399034a2f4543badc14a61f4c271d
+msgid "http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/AmazonS3.html"
+msgstr ""
+
+#: ../../plugins.rst:216
+#: ../../plugins.rst:292
+#: ../../plugins.rst:305
+# 524902fe6335491e90113db2e7dcf32c
+# e98040534c694fa79fa31e2055d1952d
+# 14a01140525943f992129262e3d80f7d
+msgid "Modifier and Type"
+msgstr ""
+
+#: ../../plugins.rst:216
+#: ../../plugins.rst:292
+#: ../../plugins.rst:305
+# 425d6aa0a9064b96a9ca0885a619c38d
+# f6a0c9e17a6243779f44932ea5a23c89
+# 9a049f576a8e4962950b98430348d2a4
+msgid "Method and Description"
+msgstr ""
+
+#: ../../plugins.rst:219
+# dab6c8ccc228474bbdee27d4828d4f54
+msgid "Bucket"
+msgstr ""
+
+#: ../../plugins.rst:219
+# b5245e58b4104653874763bf3ebc456b
+msgid "createBucket(String bucketName)"
+msgstr ""
+
+#: ../../plugins.rst:221
+# 098525d2951148a3ab0b98ccc0daa468
+msgid "Creates a new Amazon S3 bucket with the specified name in the default (US) region, Region.US\\_Standard."
+msgstr ""
+
+#: ../../plugins.rst:224
+#: ../../plugins.rst:246
+#: ../../plugins.rst:275
+#: ../../plugins.rst:279
+# 10e1e53e84814a759d18a529af6afb21
+# 19df007e41794cdcb5068190dc725b50
+# 9b936bfde7324c11bc53237bee0ab743
+# f9e2310af56643ea89a85e7a49179a42
+msgid "void"
+msgstr ""
+
+#: ../../plugins.rst:224
+# d0edd5f0784c4d0d80b649435413969c
+msgid "deleteObject(String bucketName, String key)"
+msgstr ""
+
+#: ../../plugins.rst:226
+# b000a048de2c4b73a38deb0f3453329e
+msgid "Deletes the specified object in the specified bucket."
+msgstr ""
+
+#: ../../plugins.rst:228
+# 93db5db5c5d04b14996eee4cced36b84
+msgid "ObjectMetadata"
+msgstr ""
+
+#: ../../plugins.rst:228
+# 6c36346fa1884122b6103c28b5d4bdd7
+msgid "getObject(GetObjectRequest getObjectRequest, File destinationFile)"
+msgstr ""
+
+#: ../../plugins.rst:231
+# 733bb2a121894a158b4dbed604144383
+msgid "Gets the object metadata for the object stored in Amazon S3 under the specified bucket and key, and saves the object contents to the specified file."
+msgstr ""
+
+#: ../../plugins.rst:235
+# 69058f54f58342d094836ad752e4d4e7
+msgid "S3Object"
+msgstr ""
+
+#: ../../plugins.rst:235
+# 8e4699041a0a403594cff314173bad13
+msgid "getObject(String bucketName, String key)"
+msgstr ""
+
+#: ../../plugins.rst:237
+# 565e5ccbf07643d8bdb2e31697118021
+msgid "Gets the object stored in Amazon S3 under the specified bucket and key."
+msgstr ""
+
+#: ../../plugins.rst:240
+# e434609fbde942f7b2667a2bd2b74526
+msgid "URL"
+msgstr ""
+
+#: ../../plugins.rst:240
+# 0049113021404c0398d28d0090fc4e86
+msgid "generatePresignedUrl(String bucketName, String key, Date expiration, HttpMethod method)"
+msgstr ""
+
+#: ../../plugins.rst:243
+# 4a6a23c7ae664c61a5d54eab6c49bddd
+msgid "Returns a pre-signed URL for accessing an Amazon S3 resource."
+msgstr ""
+
+#: ../../plugins.rst:246
+# 904cfc6f8c244f8fbfc859e381069663
+msgid "deleteBucket(String bucketName)"
+msgstr ""
+
+#: ../../plugins.rst:248
+# e1dac24bb0e14b4697219c79b113fd7f
+msgid "Deletes the specified bucket."
+msgstr ""
+
+#: ../../plugins.rst:250
+# 8cdb948275894bdb97c1b8b5f6e249ed
+msgid "List<Bucket>"
+msgstr ""
+
+#: ../../plugins.rst:250
+# 4948cb9aa0fe47b5a0b4133c51aac5ae
+msgid "listBuckets()"
+msgstr ""
+
+#: ../../plugins.rst:252
+# a7f7c254dfc743e6986d6f87157e8ca1
+msgid "Returns a list of all Amazon S3 buckets that the authenticated sender of the request owns."
+msgstr ""
+
+#: ../../plugins.rst:255
+# 3e40fd85e1734299b80d1a20543aa634
+msgid "ObjectListing"
+msgstr ""
+
+#: ../../plugins.rst:255
+# bb216e1e97f64c06b56d8b5d63f55e6f
+msgid "listObjects(String bucketName, String prefix)"
+msgstr ""
+
+#: ../../plugins.rst:257
+# 410a7878aa1a423a8924f0639fd9d503
+msgid "Returns a list of summary information about the objects in the specified bucket."
+msgstr ""
+
+#: ../../plugins.rst:260
+#: ../../plugins.rst:264
+#: ../../plugins.rst:269
+# c9d4c91129ea44d3b04bc4fec6625e45
+# bdebb85f1c164924b617faf009556842
+# 07c5d99ac05a4fa288989e3abc26136a
+msgid "PutObjectResult"
+msgstr ""
+
+#: ../../plugins.rst:260
+# a026c1f32bfb4bb5880c29ae0a65e253
+msgid "putObject(PutObjectRequest putObjectRequest)"
+msgstr ""
+
+#: ../../plugins.rst:262
+# 4f55cf31f4d241e1822a673575690fd8
+msgid "Uploads a new object to the specified Amazon S3 bucket."
+msgstr ""
+
+#: ../../plugins.rst:264
+# 3bc33b26a775484088543c50ccd242b9
+msgid "putObject(String bucketName, String key, File file)"
+msgstr ""
+
+#: ../../plugins.rst:266
+# 7da2800a6855410ba7aba90d4eb247f9
+msgid "Uploads the specified file to Amazon S3 under the specified bucket and key name."
+msgstr ""
+
+#: ../../plugins.rst:269
+# 84b1447f696947f188e49d20266ab31a
+msgid "putObject(String bucketName, String key, InputStream input, ObjectMetadata metadata)"
+msgstr ""
+
+#: ../../plugins.rst:272
+# ffd50b9c64944d7c94b59db13f429502
+msgid "Uploads the specified input stream and object metadata to Amazon S3 under the specified bucket and key name."
+msgstr ""
+
+#: ../../plugins.rst:275
+# 6ff9f7752d544dce87370cff755b5c04
+msgid "setEndpoint(String endpoint)"
+msgstr ""
+
+#: ../../plugins.rst:277
+# bb223a72df024071bd3fcf9a104ea867
+msgid "Overrides the default endpoint for this client."
+msgstr ""
+
+#: ../../plugins.rst:279
+# a1c7af6f2ced47df89b4f06a106004ea
+msgid "setObjectAcl(String bucketName, String key, CannedAccessControlList acl)"
+msgstr ""
+
+#: ../../plugins.rst:282
+# fc1eb83daba44fb8b3d7c874b1b78eb4
+msgid "Sets the CannedAccessControlList for the specified object in Amazon S3 using one of the pre-configured CannedAccessControlLists."
+msgstr ""
+
+#: ../../plugins.rst:287
+# 0ca9dc98fa69442da459049fa130bb3e
+msgid "*Class TransferManager*"
+msgstr ""
+
+#: ../../plugins.rst:289
+# af0a0cd7fe054fa0b429690eb93d7f08
+msgid "http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/transfer/TransferManager.html"
+msgstr ""
+
+#: ../../plugins.rst:295
+#: ../../plugins.rst:308
+# 3bf5fd4667e14704827091487cba6732
+# 063f2d2856ac430f82e49cb6a131a104
+msgid "Upload"
+msgstr ""
+
+#: ../../plugins.rst:295
+#: ../../plugins.rst:308
+# 85985bdb07bb4407ac643217da6cc939
+# bcb6b7381776465fbad331f3a2f1fa72
+msgid "upload(PutObjectRequest putObjectRequest)"
+msgstr ""
+
+#: ../../plugins.rst:297
+#: ../../plugins.rst:310
+# bae421e1a5db4ee7a2dab5d554ec7198
+# aa005a5c26e74b76a91b4f14cefed7b1
+msgid "Schedules a new transfer to upload data to Amazon S3."
+msgstr ""
+
+#: ../../plugins.rst:300
+# 62992df00ab34f92971b3885d85b3bfc
+msgid "*Class PutObjectRequest*"
+msgstr ""
+
+#: ../../plugins.rst:302
+# e6c803af72274ebc9580b6a7f60bdb67
+msgid "http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/model/PutObjectRequest.html"
+msgstr ""
+
+#: ../../plugins.rst:315
+# 047cb9e48a3d481c934d16c02bd9a87d
+msgid "Third Party UI Plugins"
+msgstr ""
+
+#: ../../plugins.rst:317
+# be7d0e07285f4351bda1ceb9a1fb337b
+msgid "Using the new third-party plugin framework, you can write and install extensions to CloudStack. The installed and enabled plugins will appear in the UI alongside the other features. The code for the plugin is simply placed in a special directory within CloudStack’s installed code at any time after CloudStack installation. The new plugin appears only when it is enabled by the cloud administrator."
+msgstr ""
+
+#: ../../plugins.rst:328
+# 21c50cf0d5564016b44442790fe84fb1
+msgid "The left navigation bar of the CloudStack UI has a new Plugins button to help you work with UI plugins."
+msgstr ""
+
+#: ../../plugins.rst:332
+# 3181ee393ee54ca0bec634ac6c3ff3ff
+msgid "How to Write a Plugin: Overview"
+msgstr ""
+
+#: ../../plugins.rst:334
+# 7e214f0cab7b4e82bc7b17125b4d573d
+msgid "The basic procedure for writing a plugin is:"
+msgstr ""
+
+#: ../../plugins.rst:336
+# 08098d9c051a422f9f119e12fb801b90
+msgid "Write the code and create the other files needed. You will need the plugin code itself (in Javascript), a thumbnail image, the plugin listing, and a CSS file."
+msgstr ""
+
+#: ../../plugins.rst:344
+# 23807d67ae0347b3bf61aac8b62dab08
+msgid "All UI plugins have the following set of files:"
+msgstr ""
+
+#: ../../plugins.rst:359
+# 26387214ce7d4db38de919e4af305edc
+msgid "The same files must also be present at `/tomcat/webapps/client/plugins`."
+msgstr ""
+
+#: ../../plugins.rst:362
+# 88678459528c45bcb71214b6c06cbe00
+msgid "The CloudStack administrator adds the folder containing your plugin code under the CloudStack PLUGINS folder."
+msgstr ""
+
+#: ../../plugins.rst:369
+# b7a4f78ddc254478acac9a6d4896db7f
+msgid "The administrator also adds the name of your plugin to the plugin.js file in the PLUGINS folder."
+msgstr ""
+
+#: ../../plugins.rst:376
+# b4a1e6dcbbe943b7b02eff49df570e25
+msgid "The next time the user refreshes the UI in the browser, your plugin will appear in the left navigation bar."
+msgstr ""
+
+#: ../../plugins.rst:384
+# ad4d6a6816c34431bad231e9fdf8b2c4
+msgid "How to Write a Plugin: Implementation Details"
+msgstr ""
+
+#: ../../plugins.rst:386
+# 32860106c46f407caa5037981b45fd0a
+msgid "This section requires an understanding of JavaScript and the CloudStack API. You don't need knowledge of specific frameworks for this tutorial (jQuery, etc.), since the CloudStack UI handles the front-end rendering for you."
+msgstr ""
+
+#: ../../plugins.rst:391
+# d43ce7e869b44abb8aa8ced854031f33
+msgid "There is much more to the CloudStack UI framework than can be described here. The UI is very flexible to handle many use cases, so there are countless options and variations. The best reference right now is to read the existing code for the main UI, which is in the /ui folder. Plugins are written in a very similar way to the main UI."
+msgstr ""
+
+#: ../../plugins.rst:397
+# c983b0a3b2e34f47891a7f3e21d300aa
+msgid "**Create the directory to hold your plugin.**"
+msgstr ""
+
+#: ../../plugins.rst:399
+# 7fcc90ae1483437c8452ecd3a63cb12e
+msgid "All plugins are composed of set of required files in the directory /ui/plugins/pluginID, where pluginID is a short name for your plugin. It's recommended that you prefix your folder name (for example, bfMyPlugin) to avoid naming conflicts with other people's plugins."
+msgstr ""
+
+#: ../../plugins.rst:405
+# cea645979e1e42dfa9fb8a4e6c835b14
+msgid "In this example, the plugin is named csMyFirstPlugin."
+msgstr ""
+
+#: ../../plugins.rst:418
+# dac80f13146d46d69f6024199420a5f1
+msgid "**Change to your new plugin directory.**"
+msgstr ""
+
+#: ../../plugins.rst:425
+# 4649d30c029947efb26e9689fe4d0a42
+msgid "**Set up the listing.**"
+msgstr ""
+
+#: ../../plugins.rst:427
+# da3530d14f3141bf8fd825e1d590183a
+msgid "Add the file `config.js`, using your favorite editor."
+msgstr ""
+
+#: ../../plugins.rst:433
+# 7a6b02d1946d4f2293b3fec3d21d8545
+msgid "Add the following content to config.js. This information will be displayed on the plugin listing page in the UI:"
+msgstr ""
+
+#: ../../plugins.rst:449
+# e5bb9ce4c369479cbe7cc590e7865105
+msgid "**Add a new main section.**"
+msgstr ""
+
+#: ../../plugins.rst:451
+# c6a54f8b6b2542779303438bf225ead2
+msgid "Add the file csMyFirstPlugin.js, using your favorite editor."
+msgstr ""
+
+#: ../../plugins.rst:457
+# e9a74896a2564517ab0b1cad702af069
+msgid "Add the following content to csMyFirstPlugin.js:"
+msgstr ""
+
+#: ../../plugins.rst:477
+# 6b508943154f4a91ad9212145454b729
+msgid "**Register the plugin.**"
+msgstr ""
+
+#: ../../plugins.rst:479
+# 99232d63e1574ee0a219e4f47db26c12
+msgid "You now have the minimal content needed to run the plugin, so you can activate the plugin in the UI by adding it to plugins.js. First, edit the file:"
+msgstr ""
+
+#: ../../plugins.rst:489
+# aecc1460eb7a4f39bfc2974ccbd9c8df
+msgid "Now add the following to plugins.js:"
+msgstr ""
+
+#: ../../plugins.rst:500
+# dda46490dded4befab18cc890e4a8685
+msgid "**Check the plugin in the UI.**"
+msgstr ""
+
+#: ../../plugins.rst:502
+# 64676cd9d1b945ccbb61f2660ad70c96
+msgid "First, copy all the plugin code that you have created so far to `/tomcat/webapps/client/plugins`. Then refresh the browser and click Plugins in the side navigation bar. You should see your new plugin."
+msgstr ""
+
+#: ../../plugins.rst:506
+# 3b028f17d2f94b28966e30fe979808a7
+msgid "**Make the plugin do something.**"
+msgstr ""
+
+#: ../../plugins.rst:508
+# 6c65b20c7e6f487ca68539eab0b480d3
+msgid "Right now, you just have placeholder content in the new plugin. It's time to add real code. In this example, you will write a basic list view, which renders data from an API call. You will list all virtual machines owned by the logged-in user. To do this, replace the 'show' function in the plugin code with a 'listView' block, containing the required syntax for a list view. To get the data, use the listVirtualMachines API call. Without any parameters, it will return VMs only for your active user. Use the provided 'apiCall' helper method to handle the server call. Of course, you are free to use any other method for making the AJAX call (for example, jQuery's $.ajax method)."
+msgstr ""
+
+#: ../../plugins.rst:520
+# 813e82c6e71c4a11b86c8fcb1997906b
+msgid "First, open your plugin's JavaScript source file in your favorite editor:"
+msgstr ""
+
+#: ../../plugins.rst:529
+# 2d33a542619b4d55a0e9f87a9516a1dd
+msgid "Add the following code in csMyFirstPlugin.js:"
+msgstr ""
+
+#: ../../plugins.rst:573
+# 436498903a8348ca82d0c2b7e7c474bd
+msgid "**Test the plugin.**"
+msgstr ""
+
+#: ../../plugins.rst:575
+# fc6df374ec774dcca802ea34ff7af4c1
+msgid "First, copy all the plugin code that you have created so far to `/tomcat/webapps/client/plugins`. Then refresh the browser. You can see that your placeholder content was replaced with a list table, containing 4 columns of virtual machine data."
+msgstr ""
+
+#: ../../plugins.rst:580
+# ac308906d1774a4181bf17b00da818ea
+msgid "**Add an action button.**"
+msgstr ""
+
+#: ../../plugins.rst:582
+# 83bd0fe3cefa45a393d1a3ff21a4ce34
+msgid "Let's add an action button to the list view, which will reboot the VM. To do this, add an actions block under listView. After specifying the correct format, the actions will appear automatically to the right of each row of data."
+msgstr ""
+
+#: ../../plugins.rst:592
+# 7d22cbd6ab2c4a4da120584e0b7e9dfb
+msgid "Now add the following new code in csMyFirstPlugin.js. (The dots ... show where we have omitted some existing code for the sake of space. Don't actually cut and paste that part):"
+msgstr ""
+
+#: ../../plugins.rst:677
+# 5acc3c90549c46adaff6a95a22b18e8d
+msgid "**Add the thumbnail icon.**"
+msgstr ""
+
+#: ../../plugins.rst:679
+# 645ff826822448548982c45e8aa9e189
+msgid "Create an icon file; it should be square, about 50x50 pixels, and named `icon.png`. Copy it into the same directory with your plugin code: `cloudstack/ui/plugins/csMyFirstPlugin/icon.png`."
+msgstr ""
+
+#: ../../plugins.rst:683
+# dc9c9e24edb440f6a5daefbe14510efe
+msgid "**Add the stylesheet.**"
+msgstr ""
+
+#: ../../plugins.rst:685
+# 176437827f1047cbbfb1eb8b39f7f054
+msgid "Create a CSS file, with the same name as your `.js` file. Copy it into the same directory with your plugin code: `cloudstack/ui/plugins/csMyFirstPlugin/csMyFirstPlugin.css`."
+msgstr ""
+
diff --git a/source/conceptsandterminology/network_setup.rst b/source/conceptsandterminology/network_setup.rst
new file mode 100644
index 0000000..08ddf5e
--- /dev/null
+++ b/source/conceptsandterminology/network_setup.rst
@@ -0,0 +1,1048 @@
+.. 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.
+
+
+Achieving the correct networking setup is crucial to a successful
+CloudStack installation. This section contains information to help you
+make decisions and follow the right procedures to get your network set
+up correctly.
+
+
+Basic and Advanced Networking
+-----------------------------
+
+CloudStack provides two styles of networking:.
+
+**Basic**
+For AWS-style networking. Provides a single network where guest isolation can
+be provided through layer-3 means such as security groups (IP address source
+filtering).
+
+**Advanced**
+For more sophisticated network topologies. This network model provides the
+most flexibility in defining guest networks, but requires more configuration
+steps than basic networking.
+
+Each zone has either basic or advanced networking. Once the choice of
+networking model for a zone has been made and configured in CloudStack,
+it can not be changed. A zone is either basic or advanced for its entire
+lifetime.
+
+The following table compares the networking features in the two networking models.
+
+.. cssclass:: table-striped table-bordered table-hover
+
+========================= =================================== ===============================
+Networking Feature Basic Network Advanced Network
+========================= =================================== ===============================
+Number of networks Single network Multiple networks
+Firewall type Physical Physical and Virtual
+Load balancer Physical Physical and Virtual
+Isolation type Layer 3 Layer 2 and Layer 3
+VPN support No Yes
+Port forwarding Physical Physical and Virtual
+1:1 NAT Physical Physical and Virtual
+Source NAT No Physical and Virtual
+Userdata Yes Yes
+Network usage monitoring sFlow / netFlow at physical router Hypervisor and Virtual Router
+DNS and DHCP Yes Yes
+========================= =================================== ===============================
+
+The two types of networking may be in use in the same cloud. However, a
+given zone must use either Basic Networking or Advanced Networking.
+
+Different types of network traffic can be segmented on the same physical
+network. Guest traffic can also be segmented by account. To isolate
+traffic, you can use separate VLANs. If you are using separate VLANs on
+a single physical network, make sure the VLAN tags are in separate
+numerical ranges.
+
+
+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
+================== ========================================================= =======================================================================
+
+
+Example Hardware Configuration
+------------------------------
+
+This section contains an example configuration of specific switch models
+for zone-level layer-3 switching. It assumes VLAN management protocols,
+such as VTP or GVRP, have been disabled. The example scripts must be
+changed appropriately if you choose to use VTP or GVRP.
+
+
+Dell 62xx
+~~~~~~~~~
+
+The following steps show how a Dell 62xx is configured for zone-level
+layer-3 switching. These steps assume VLAN 201 is used to route untagged
+private IPs for pod 1, and pod 1’s layer-2 switch is connected to
+Ethernet port 1/g1.
+
+The Dell 62xx Series switch supports up to 1024 VLANs.
+
+#. Configure all the VLANs in the database.
+
+ .. parsed-literal::
+
+ vlan database
+ vlan 200-999
+ exit
+
+#. Configure Ethernet port 1/g1.
+
+ .. parsed-literal::
+
+ interface ethernet 1/g1
+ switchport mode general
+ switchport general pvid 201
+ switchport general allowed vlan add 201 untagged
+ switchport general allowed vlan add 300-999 tagged
+ exit
+
+The statements configure Ethernet port 1/g1 as follows:
+
+- VLAN 201 is the native untagged VLAN for port 1/g1.
+
+- All VLANs (300-999) are passed to all the pod-level layer-2 switches.
+
+
+Cisco 3750
+~~~~~~~~~~
+
+The following steps show how a Cisco 3750 is configured for zone-level
+layer-3 switching. These steps assume VLAN 201 is used to route untagged
+private IPs for pod 1, and pod 1’s layer-2 switch is connected to
+GigabitEthernet1/0/1.
+
+#. Setting VTP mode to transparent allows us to utilize VLAN IDs above
+ 1000. Since we only use VLANs up to 999, vtp transparent mode is not
+ strictly required.
+
+ .. parsed-literal::
+
+ vtp mode transparent
+ vlan 200-999
+ exit
+
+#. Configure GigabitEthernet1/0/1.
+
+ .. parsed-literal::
+
+ interface GigabitEthernet1/0/1
+ switchport trunk encapsulation dot1q
+ switchport mode trunk
+ switchport trunk native vlan 201
+ exit
+
+The statements configure GigabitEthernet1/0/1 as follows:
+
+- VLAN 201 is the native untagged VLAN for port GigabitEthernet1/0/1.
+
+- Cisco passes all VLANs by default. As a result, all VLANs (300-999)
+ are passed to all the pod-level layer-2 switches.
+
+
+Layer-2 Switch
+--------------
+
+The layer-2 switch is the access switching layer inside the pod.
+
+- It should trunk all VLANs into every computing host.
+
+- It should switch traffic for the management network containing
+ computing and storage hosts. The layer-3 switch will serve as the
+ gateway for the management network.
+
+The following sections contain example configurations for specific switch models
+for pod-level layer-2 switching. It assumes VLAN management protocols
+such as VTP or GVRP have been disabled. The scripts must be changed
+appropriately if you choose to use VTP or GVRP.
+
+Dell 62xx
+~~~~~~~~~
+
+The following steps show how a Dell 62xx is configured for pod-level
+layer-2 switching.
+
+#. Configure all the VLANs in the database.
+
+ .. parsed-literal::
+
+ vlan database
+ vlan 300-999
+ exit
+
+#. VLAN 201 is used to route untagged private IP addresses for pod 1,
+ and pod 1 is connected to this layer-2 switch.
+
+ .. parsed-literal::
+
+ interface range ethernet all
+ switchport mode general
+ switchport general allowed vlan add 300-999 tagged
+ exit
+
+The statements configure all Ethernet ports to function as follows:
+
+- All ports are configured the same way.
+
+- All VLANs (300-999) are passed through all the ports of the layer-2
+ switch.
+
+
+Cisco 3750
+~~~~~~~~~~
+
+The following steps show how a Cisco 3750 is configured for pod-level
+layer-2 switching.
+
+#. Setting VTP mode to transparent allows us to utilize VLAN IDs above
+ 1000. Since we only use VLANs up to 999, vtp transparent mode is not
+ strictly required.
+
+ .. parsed-literal::
+
+ vtp mode transparent
+ vlan 300-999
+ exit
+
+#. Configure all ports to dot1q and set 201 as the native VLAN.
+
+ .. parsed-literal::
+
+ interface range GigabitEthernet 1/0/1-24
+ switchport trunk encapsulation dot1q
+ switchport mode trunk
+ switchport trunk native vlan 201
+ exit
+
+By default, Cisco passes all VLANs. Cisco switches complain of the
+native VLAN IDs are different when 2 ports are connected together.
+That’s why you must specify VLAN 201 as the native VLAN on the layer-2
+switch.
+
+
+Hardware Firewall
+-----------------
+
+All deployments should have a firewall protecting the management server;
+see Generic Firewall Provisions. Optionally, some deployments may also
+have a Juniper SRX firewall that will be the default gateway for the
+guest networks; see :ref:`external-guest-firewall-integration-for-juniper-srx-optional`
+
+
+Generic Firewall Provisions
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The hardware firewall is required to serve two purposes:
+
+- Protect the Management Servers. NAT and port forwarding should be
+ configured to direct traffic from the public Internet to the
+ Management Servers.
+
+- Route management network traffic between multiple zones. Site-to-site
+ VPN should be configured between multiple zones.
+
+To achieve the above purposes you must set up fixed configurations for
+the firewall. Firewall rules and policies need not change as users are
+provisioned into the cloud. Any brand of hardware firewall that supports
+NAT and site-to-site VPN can be used.
+
+.. _external-guest-firewall-integration-for-juniper-srx-optional:
+
+External Guest Firewall Integration for Juniper SRX (Optional)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. note::
+ Available only for guests using advanced networking.
+
+CloudStack provides for direct management of the Juniper SRX series of
+firewalls. This enables CloudStack to establish static NAT mappings from
+public IPs to guest VMs, and to use the Juniper device in place of the
+virtual router for firewall services. You can have one or more Juniper
+SRX per zone. This feature is optional. If Juniper integration is not
+provisioned, CloudStack will use the virtual router for these services.
+
+The Juniper SRX can optionally be used in conjunction with an external
+load balancer. External Network elements can be deployed in a
+side-by-side or inline configuration.
+
+|parallel-mode.png: adding a firewall and load balancer in parallel
+mode.|
+
+CloudStack requires the Juniper SRX firewall to be configured as follows:
+
+.. note::
+ Supported SRX software version is 10.3 or higher.
+
+#. Install your SRX appliance according to the vendor's instructions.
+
+#. Connect one interface to the management network and one interface to
+ the public network. Alternatively, you can connect the same interface
+ to both networks and a use a VLAN for the public network.
+
+#. Make sure "vlan-tagging" is enabled on the private interface.
+
+#. Record the public and private interface names. If you used a VLAN for
+ the public interface, add a ".[VLAN TAG]" after the interface name.
+ For example, if you are using ge-0/0/3 for your public interface and
+ VLAN tag 301, your public interface name would be "ge-0/0/3.301".
+ Your private interface name should always be untagged because the
+ CloudStack software automatically creates tagged logical interfaces.
+
+#. Create a public security zone and a private security zone. By
+ default, these will already exist and will be called "untrust" and
+ "trust". Add the public interface to the public zone and the private
+ interface to the private zone. Note down the security zone names.
+
+#. Make sure there is a security policy from the private zone to the
+ public zone that allows all traffic.
+
+#. Note the username and password of the account you want the CloudStack
+ software to log in to when it is programming rules.
+
+#. Make sure the "ssh" and "xnm-clear-text" system services are enabled.
+
+#. If traffic metering is desired:
+
+ #. Create an incoming firewall filter and an outgoing firewall
+ filter. These filters should be the same names as your public
+ security zone name and private security zone name respectively.
+ The filters should be set to be "interface-specific". For example,
+ here is the configuration where the public zone is "untrust" and
+ the private zone is "trust":
+
+ .. parsed-literal::
+
+ root@cloud-srx# show firewall
+ filter trust {
+ interface-specific;
+ }
+ filter untrust {
+ interface-specific;
+ }
+
+ #. Add the firewall filters to your public interface. For example, a
+ sample configuration output (for public interface ge-0/0/3.0,
+ public security zone untrust, and private security zone trust) is:
+
+ .. parsed-literal::
+
+ ge-0/0/3 {
+ unit 0 {
+ family inet {
+ filter {
+ input untrust;
+ output trust;
+ }
+ address 172.25.0.252/16;
+ }
+ }
+ }
+
+#. Make sure all VLANs are brought to the private interface of the SRX.
+
+#. After the CloudStack Management Server is installed, log in to the
+ CloudStack UI as administrator.
+
+#. In the left navigation bar, click Infrastructure.
+
+#. In Zones, click View More.
+
+#. Choose the zone you want to work with.
+
+#. Click the Network tab.
+
+#. In the Network Service Providers node of the diagram, click
+ Configure. (You might have to scroll down to see this.)
+
+#. Click SRX.
+
+#. Click the Add New SRX button (+) and provide the following:
+
+ - IP Address: The IP address of the SRX.
+
+ - Username: The user name of the account on the SRX that CloudStack
+ should use.
+
+ - Password: The password of the account.
+
+ - Public Interface. The name of the public interface on the SRX. For
+ example, ge-0/0/2. A ".x" at the end of the interface indicates
+ the VLAN that is in use.
+
+ - Private Interface: The name of the private interface on the SRX.
+ For example, ge-0/0/1.
+
+ - Usage Interface: (Optional) Typically, the public interface is
+ used to meter traffic. If you want to use a different interface,
+ specify its name here
+
+ - Number of Retries: The number of times to attempt a command on the
+ SRX before failing. The default value is 2.
+
+ - Timeout (seconds): The time to wait for a command on the SRX
+ before considering it failed. Default is 300 seconds.
+
+ - Public Network: The name of the public network on the SRX. For
+ example, trust.
+
+ - Private Network: The name of the private network on the SRX. For
+ example, untrust.
+
+ - Capacity: The number of networks the device can handle
+
+ - Dedicated: When marked as dedicated, this device will be dedicated
+ to a single account. When Dedicated is checked, the value in the
+ Capacity field has no significance implicitly, its value is 1
+
+#. Click OK.
+
+#. Click Global Settings. Set the parameter
+ external.network.stats.interval to indicate how often you want
+ CloudStack to fetch network usage statistics from the Juniper SRX. If
+ you are not using the SRX to gather network usage statistics, set to 0.
+
+
+External Guest Firewall Integration for Cisco VNMC (Optional)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Cisco Virtual Network Management Center (VNMC) provides centralized
+multi-device and policy management for Cisco Network Virtual Services.
+You can integrate Cisco VNMC with CloudStack to leverage the firewall
+and NAT service offered by ASA 1000v Cloud Firewall. Use it in a Cisco
+Nexus 1000v dvSwitch-enabled cluster in CloudStack. In such a
+deployment, you will be able to:
+
+- Configure Cisco ASA 1000v firewalls. You can configure one per guest
+ network.
+
+- Use Cisco ASA 1000v firewalls to create and apply security profiles
+ that contain ACL policy sets for both ingress and egress traffic.
+
+- Use Cisco ASA 1000v firewalls to create and apply Source NAT, Port
+ Forwarding, and Static NAT policy sets.
+
+CloudStack supports Cisco VNMC on Cisco Nexus 1000v dvSwich-enabled
+VMware hypervisors.
+
+
+Using Cisco ASA 1000v Firewall, Cisco Nexus 1000v dvSwitch, and Cisco VNMC in a Deployment
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Guidelines
+'''''''''''
+
+- Cisco ASA 1000v firewall is supported only in Isolated Guest
+ Networks.
+
+- Cisco ASA 1000v firewall is not supported on VPC.
+
+- Cisco ASA 1000v firewall is not supported for load balancing.
+
+- When a guest network is created with Cisco VNMC firewall provider, an
+ additional public IP is acquired along with the Source NAT IP. The
+ Source NAT IP is used for the rules, whereas the additional IP is
+ used to for the ASA outside interface. Ensure that this additional
+ public IP is not released. You can identify this IP as soon as the
+ network is in implemented state and before acquiring any further
+ public IPs. The additional IP is the one that is not marked as Source
+ NAT. You can find the IP used for the ASA outside interface by
+ looking at the Cisco VNMC used in your guest network.
+
+- Use the public IP address range from a single subnet. You cannot add
+ IP addresses from different subnets.
+
+- Only one ASA instance per VLAN is allowed because multiple VLANS
+ cannot be trunked to ASA ports. Therefore, you can use only one ASA
+ instance in a guest network.
+
+- Only one Cisco VNMC per zone is allowed.
+
+- Supported only in Inline mode deployment with load balancer.
+
+- The ASA firewall rule is applicable to all the public IPs in the
+ guest network. Unlike the firewall rules created on virtual router, a
+ rule created on the ASA device is not tied to a specific public IP.
+
+- Use a version of Cisco Nexus 1000v dvSwitch that support the vservice
+ command. For example: nexus-1000v.4.2.1.SV1.5.2b.bin
+
+ Cisco VNMC requires the vservice command to be available on the Nexus
+ switch to create a guest network in CloudStack.
+
+
+Prerequisites
+'''''''''''''
+
+#. Configure Cisco Nexus 1000v dvSwitch in a vCenter environment.
+
+ Create Port profiles for both internal and external network
+ interfaces on Cisco Nexus 1000v dvSwitch. Note down the inside port
+ profile, which needs to be provided while adding the ASA appliance to
+ CloudStack.
+
+ For information on configuration, see :ref:`configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch`.
+
+#. Deploy and configure Cisco VNMC.
+
+ For more information, see
+ `Installing Cisco Virtual Network Management Center
+ <http://www.cisco.com/en/US/docs/switches/datacenter/vsg/sw/4_2_1_VSG_2_1_1/install_upgrade/guide/b_Cisco_VSG_for_VMware_vSphere_Rel_4_2_1_VSG_2_1_1_and_Cisco_VNMC_Rel_2_1_Installation_and_Upgrade_Guide_chapter_011.html>`_
+ and `Configuring Cisco Virtual Network Management Center
+ <http://www.cisco.com/en/US/docs/unified_computing/vnmc/sw/1.2/VNMC_GUI_Configuration/b_VNMC_GUI_Configuration_Guide_1_2_chapter_010.html>`_.
+
+#. Register Cisco Nexus 1000v dvSwitch with Cisco VNMC.
+
+ For more information, see `Registering a Cisco Nexus 1000V with Cisco VNMC
+ <http://www.cisco.com/en/US/docs/switches/datacenter/vsg/sw/4_2_1_VSG_1_2/vnmc_and_vsg_qi/guide/vnmc_vsg_install_5register.html#wp1064301>`_.
+
+#. Create Inside and Outside port profiles in Cisco Nexus 1000v dvSwitch.
+
+ For more information, see :ref:`configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch`.
+
+#. Deploy and Cisco ASA 1000v appliance.
+
+ For more information, see `Setting Up the ASA 1000V Using VNMC
+ <http://www.cisco.com/en/US/docs/security/asa/quick_start/asa1000V/setup_vnmc.html>`_.
+
+ Typically, you create a pool of ASA 1000v appliances and register
+ them with CloudStack.
+
+ Specify the following while setting up a Cisco ASA 1000v instance:
+
+ - VNMC host IP.
+
+ - Ensure that you add ASA appliance in VNMC mode.
+
+ - Port profiles for the Management and HA network interfaces. This
+ need to be pre-created on Cisco Nexus 1000v dvSwitch.
+
+ - Internal and external port profiles.
+
+ - The Management IP for Cisco ASA 1000v appliance. Specify the
+ gateway such that the VNMC IP is reachable.
+
+ - Administrator credentials
+
+ - VNMC credentials
+
+#. Register Cisco ASA 1000v with VNMC.
+
+ After Cisco ASA 1000v instance is powered on, register VNMC from the
+ ASA console.
+
+
+Using Cisco ASA 1000v Services
+''''''''''''''''''''''''''''''
+
+#. Ensure that all the prerequisites are met.
+
+ See `“Prerequisites” <#prerequisites>`_.
+
+#. Add a VNMC instance.
+
+ See `“Adding a VNMC Instance” <#adding-a-vnmc-instance>`_.
+
+#. Add a ASA 1000v instance.
+
+ See :ref:`adding-an-asa-1000v-instance`.
+
+#. Create a Network Offering and use Cisco VNMC as the service provider
+ for desired services.
+
+ See :ref:`creating-a-network-offering-using-cisco-asa-1000v`.
+
+#. Create an Isolated Guest Network by using the network offering you
+ just created.
+
+
+Adding a VNMC Instance
+^^^^^^^^^^^^^^^^^^^^^^
+
+#. Log in to the CloudStack UI as administrator.
+
+#. In the left navigation bar, click Infrastructure.
+
+#. In Zones, click View More.
+
+#. Choose the zone you want to work with.
+
+#. Click the Physical Network tab.
+
+#. In the Network Service Providers node of the diagram, click
+ Configure.
+
+ You might have to scroll down to see this.
+
+#. Click Cisco VNMC.
+
+#. Click View VNMC Devices.
+
+#. Click the Add VNMC Device and provide the following:
+
+ - Host: The IP address of the VNMC instance.
+
+ - Username: The user name of the account on the VNMC instance that
+ CloudStack should use.
+
+ - Password: The password of the account.
+
+#. Click OK.
+
+.. adding-an-asa-1000v-instance:
+
+Adding an ASA 1000v Instance
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. Log in to the CloudStack UI as administrator.
+
+#. In the left navigation bar, click Infrastructure.
+
+#. In Zones, click View More.
+
+#. Choose the zone you want to work with.
+
+#. Click the Physical Network tab.
+
+#. In the Network Service Providers node of the diagram, click
+ Configure.
+
+ You might have to scroll down to see this.
+
+#. Click Cisco VNMC.
+
+#. Click View ASA 1000v.
+
+#. Click the Add CiscoASA1000v Resource and provide the following:
+
+ - **Host**: The management IP address of the ASA 1000v instance. The
+ IP address is used to connect to ASA 1000V.
+
+ - **Inside Port Profile**: The Inside Port Profile configured on
+ Cisco Nexus1000v dvSwitch.
+
+ - **Cluster**: The VMware cluster to which you are adding the ASA
+ 1000v instance.
+
+ Ensure that the cluster is Cisco Nexus 1000v dvSwitch enabled.
+
+#. Click OK.
+
+.. _creating-a-network-offering-using-cisco-asa-1000v:
+
+Creating a Network Offering Using Cisco ASA 1000v
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+To have Cisco ASA 1000v support for a guest network, create a network
+offering as follows:
+
+#. Log in to the CloudStack UI as a user or admin.
+
+#. From the Select Offering drop-down, choose Network Offering.
+
+#. Click Add Network Offering.
+
+#. In the dialog, make the following choices:
+
+ - **Name**: Any desired name for the network offering.
+
+ - **Description**: A short description of the offering that can be
+ displayed to users.
+
+ - **Network Rate**: Allowed data transfer rate in MB per second.
+
+ - **Traffic Type**: The type of network traffic that will be carried
+ on the network.
+
+ - **Guest Type**: Choose whether the guest network is isolated or
+ shared.
+
+ - **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.
+
+ - **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 :ref: `about-vpc`.
+
+ - **Specify VLAN**: (Isolated guest networks only) Indicate whether
+ a VLAN should be specified when this offering is used.
+
+ - **Supported Services**: Use Cisco VNMC as the service provider for
+ Firewall, Source NAT, Port Forwarding, and Static NAT to create an
+ Isolated guest network offering.
+
+ - **System Offering**: Choose the system service offering that you
+ want virtual routers to use in this network.
+
+ - **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.
+
+#. Click OK
+
+ The network offering is created.
+
+
+Reusing ASA 1000v Appliance in new Guest Networks
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+You can reuse an ASA 1000v appliance in a new guest network after the
+necessary cleanup. Typically, ASA 1000v is cleaned up when the logical
+edge firewall is cleaned up in VNMC. If this cleanup does not happen,
+you need to reset the appliance to its factory settings for use in new
+guest networks. As part of this, enable SSH on the appliance and store
+the SSH credentials by registering on VNMC.
+
+#. Open a command line on the ASA appliance:
+
+ #. Run the following:
+
+ .. parsed-literal::
+
+ ASA1000V(config)# reload
+
+ You are prompted with the following message:
+
+ .. parsed-literal::
+
+ System config has been modified. Save? [Y]es/[N]o:"
+
+ #. Enter N.
+
+ You will get the following confirmation message:
+
+ .. parsed-literal::
+
+ "Proceed with reload? [confirm]"
+
+ #. Restart the appliance.
+
+#. Register the ASA 1000v appliance with the VNMC:
+
+ .. parsed-literal::
+
+ ASA1000V(config)# vnmc policy-agent
+ ASA1000V(config-vnmc-policy-agent)# registration host vnmc_ip_address
+ ASA1000V(config-vnmc-policy-agent)# shared-secret key where key is the shared secret for authentication of the ASA 1000V connection to the Cisco VNMC
+
+
+External Guest Load Balancer Integration (Optional)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack can optionally use a Citrix NetScaler or BigIP F5 load
+balancer to provide load balancing services to guests. If this is not
+enabled, CloudStack will use the software load balancer in the virtual
+router.
+
+To install and enable an external load balancer for CloudStack
+management:
+
+#. Set up the appliance according to the vendor's directions.
+
+#. Connect it to the networks carrying public traffic and management
+ traffic (these could be the same network).
+
+#. Record the IP address, username, password, public interface name, and
+ private interface name. The interface names will be something like
+ "1.1" or "1.2".
+
+#. Make sure that the VLANs are trunked to the management network
+ interface.
+
+#. After the CloudStack Management Server is installed, log in as
+ administrator to the CloudStack UI.
+
+#. In the left navigation bar, click Infrastructure.
+
+#. In Zones, click View More.
+
+#. Choose the zone you want to work with.
+
+#. Click the Network tab.
+
+#. In the Network Service Providers node of the diagram, click
+ Configure. (You might have to scroll down to see this.)
+
+#. Click NetScaler or F5.
+
+#. Click the Add button (+) and provide the following:
+
+ For NetScaler:
+
+ - IP Address: The IP address of the SRX.
+
+ - Username/Password: The authentication credentials to access the
+ device. CloudStack uses these credentials to access the device.
+
+ - Type: The type of device that is being added. It could be F5 Big
+ Ip Load Balancer, NetScaler VPX, NetScaler MPX, or NetScaler SDX.
+ For a comparison of the NetScaler types, see the CloudStack
+ Administration Guide.
+
+ - Public interface: Interface of device that is configured to be
+ part of the public network.
+
+ - Private interface: Interface of device that is configured to be
+ part of the private network.
+
+ - Number of retries. Number of times to attempt a command on the
+ device before considering the operation failed. Default is 2.
+
+ - Capacity: The number of networks the device can handle.
+
+ - Dedicated: When marked as dedicated, this device will be dedicated
+ to a single account. When Dedicated is checked, the value in the
+ Capacity field has no significance implicitly, its value is 1.
+
+#. Click OK.
+
+The installation and provisioning of the external load balancer is
+finished. You can proceed to add VMs and NAT or load balancing rules.
+
+
+Management Server Load Balancing
+--------------------------------
+
+CloudStack can use a load balancer to provide a virtual IP for multiple
+Management Servers. The administrator is responsible for creating the
+load balancer rules for the Management Servers. The application requires
+persistence or stickiness across multiple sessions. The following chart
+lists the ports that should be load balanced and whether or not
+persistence is required.
+
+Even if persistence is not required, enabling it is permitted.
+
+.. cssclass:: table-striped table-bordered table-hover
+
+=========== ======================== ============= =====================
+Source Port Destination Port Protocol Persistence Required?
+=========== ======================== ============= =====================
+80 or 443 8080 (or 20400 with AJP) HTTP (or AJP) Yes
+8250 8250 TCP Yes
+8096 8096 HTTP No
+=========== ======================== ============= =====================
+
+In addition to above settings, the administrator is responsible for
+setting the 'host' global config value from the management server IP to
+load balancer virtual IP address. If the 'host' value is not set to the
+VIP for Port 8250 and one of your management servers crashes, the UI is
+still available but the system VMs will not be able to contact the
+management server.
+
+
+Topology Requirements
+---------------------
+
+Security Requirements
+~~~~~~~~~~~~~~~~~~~~~
+
+The public Internet must not be able to access port 8096 or port 8250 on
+the Management Server.
+
+
+Runtime Internal Communications Requirements
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- The Management Servers communicate with each other to coordinate
+ tasks. This communication uses TCP on ports 8250 and 9090.
+
+- The console proxy VMs connect to all hosts in the zone over the
+ management traffic network. Therefore the management traffic network
+ of any given pod in the zone must have connectivity to the management
+ traffic network of all other pods in the zone.
+
+- The secondary storage VMs and console proxy VMs connect to the
+ Management Server on port 8250. If you are using multiple Management
+ Servers, the load balanced IP address of the Management Servers on
+ port 8250 must be reachable.
+
+
+Storage Network Topology Requirements
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The secondary storage NFS export is mounted by the secondary storage VM.
+Secondary storage traffic goes over the management traffic network, even
+if there is a separate storage network. Primary storage traffic goes
+over the storage network, if available. If you choose to place secondary
+storage NFS servers on the storage network, you must make sure there is
+a route from the management traffic network to the storage network.
+
+
+External Firewall Topology Requirements
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When external firewall integration is in place, the public IP VLAN must
+still be trunked to the Hosts. This is required to support the Secondary
+Storage VM and Console Proxy VM.
+
+
+Advanced Zone Topology Requirements
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+With Advanced Networking, separate subnets must be used for private and
+public networks.
+
+
+XenServer Topology Requirements
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The Management Servers communicate with XenServer hosts on ports 22
+(ssh), 80 (HTTP), and 443 (HTTPs).
+
+
+VMware Topology Requirements
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- The Management Server and secondary storage VMs must be able to
+ access vCenter and all ESXi hosts in the zone. To allow the necessary
+ access through the firewall, keep port 443 open.
+
+- The Management Servers communicate with VMware vCenter servers on
+ port 443 (HTTPs).
+
+- The Management Servers communicate with the System VMs on port 3922
+ (ssh) on the management traffic network.
+
+
+Hyper-V Topology Requirements
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack Management Server communicates with Hyper-V Agent by using
+HTTPS. For secure communication between the Management Server and the
+Hyper-V host, open port 8250.
+
+
+KVM Topology Requirements
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The Management Servers communicate with KVM hosts on port 22 (ssh).
+
+
+LXC Topology Requirements
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The Management Servers communicate with LXC hosts on port 22 (ssh).
+
+
+Guest Network Usage Integration for Traffic Sentinel
+----------------------------------------------------
+
+To collect usage data for a guest network, CloudStack needs to pull the
+data from an external network statistics collector installed on the
+network. Metering statistics for guest networks are available through
+CloudStack’s integration with inMon Traffic Sentinel.
+
+Traffic Sentinel is a network traffic usage data collection package.
+CloudStack can feed statistics from Traffic Sentinel into its own usage
+records, providing a basis for billing users of cloud infrastructure.
+Traffic Sentinel uses the traffic monitoring protocol sFlow. Routers
+and switches generate sFlow records and provide them for collection by
+Traffic Sentinel, then CloudStack queries the Traffic Sentinel database
+to obtain this information
+
+To construct the query, CloudStack determines what guest IPs were in use
+during the current query interval. This includes both newly assigned IPs
+and IPs that were assigned in a previous time period and continued to be
+in use. CloudStack queries Traffic Sentinel for network statistics that
+apply to these IPs during the time period they remained allocated in
+CloudStack. The returned data is correlated with the customer account
+that owned each IP and the timestamps when IPs were assigned and
+released in order to create billable metering records in CloudStack.
+When the Usage Server runs, it collects this data.
+
+To set up the integration between CloudStack and Traffic Sentinel:
+
+#. On your network infrastructure, install Traffic Sentinel and
+ configure it to gather traffic data. For installation and
+ configuration steps, see inMon documentation at
+ `Traffic Sentinel Documentation <http://inmon.com.>`_.
+
+#. In the Traffic Sentinel UI, configure Traffic Sentinel to accept
+ script querying from guest users. CloudStack will be the guest user
+ performing the remote queries to gather network usage for one or more
+ IP addresses.
+
+ Click File > Users > Access Control > Reports Query, then select
+ Guest from the drop-down list.
+
+#. On CloudStack, add the Traffic Sentinel host by calling the
+ CloudStack API command addTrafficMonitor. Pass in the URL of the
+ Traffic Sentinel as protocol + host + port (optional); for example,
+ http://10.147.28.100:8080. For the addTrafficMonitor command syntax,
+ see the API Reference at `API Documentation
+ <http://cloudstack.apache.org/docs/api/index.html>`_.
+
+ For information about how to call the CloudStack API, see the
+ Developer’s Guide at the CloudStack API Developer's Guide :ref:`the-api`
+
+#. Log in to the CloudStack UI as administrator.
+
+#. Select Configuration from the Global Settings page, and set the
+ following:
+
+ direct.network.stats.interval: How often you want CloudStack to query
+ Traffic Sentinel.
+
+
+Setting Zone VLAN and Running VM Maximums
+-----------------------------------------
+
+In the external networking case, every VM in a zone must have a unique
+guest IP address. There are two variables that you need to consider in
+determining how to configure CloudStack to support this: how many Zone
+VLANs do you expect to have and how many VMs do you expect to have
+running in the Zone at any one time.
+
+Use the following table to determine how to configure CloudStack for
+your deployment.
+
+.. cssclass:: table-striped table-bordered table-hover
+
+=============== ============================ ==================
+guest.vlan.bits Maximum Running VMs per Zone Maximum Zone VLANs
+=============== ============================ ==================
+12 4096 4094
+11 8192 2048
+10 16384 1024
+10 32768 512
+=============== ============================ ==================
+
+Based on your deployment's needs, choose the appropriate value of
+guest.vlan.bits. Set it as described in Edit the Global Configuration
+Settings (Optional) section and restart the Management Server.
+
+
+.. |parallel-mode.png: adding a firewall and load balancer in parallel mode.| image:: /_static/images/parallel-mode.png
diff --git a/source/conceptsandterminology/storage_setup.rst b/source/conceptsandterminology/storage_setup.rst
new file mode 100644
index 0000000..24e6706
--- /dev/null
+++ b/source/conceptsandterminology/storage_setup.rst
@@ -0,0 +1,361 @@
+.. 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.
+
+Introduction
+************
+
+.. _about-primary-storage:
+
+Primary Storage
+===============
+
+CloudStack is designed to work with a wide variety of commodity and enterprise-rated storage systems.
+CloudStack can also leverage the local disks within the hypervisor hosts if supported by the selected
+hypervisor. Storage type support for guest virtual disks differs based on hypervisor selection.
+
+============= ============================== ================== ===================================
+Storage Type XenServer vSphere KVM
+============= ============================== ================== ===================================
+NFS Supported Supported Supported
+iSCSI Supported Supported via VMFS Supported via Clustered Filesystems
+Fiber Channel Supported via Pre-existing SR Supported Supported via Clustered Filesystems
+Local Disk Supported Supported Supported
+============= ============================== ================== ===================================
+
+The use of the Cluster Logical Volume Manager (CLVM) for KVM is not officially supported with
+CloudStack.
+
+.. _about-secondary-storage:
+
+Secondary Storage
+=================
+
+CloudStack is designed to work with any scalable secondary storage system. The only requirement is
+that the secondary storage system supports the NFS protocol. For large, multi-zone deployments, S3
+compatible storage is also supported for secondary storage. This allows for secondary storage which can
+span an entire region, however an NFS staging area must be maintained in each zone as most hypervisors
+are not capable of directly mounting S3 type storage.
+
+Configurations
+**************
+
+Small-Scale Setup
+=================
+
+In a small-scale setup, a single NFS server can function as both primary and secondary storage. The NFS
+server must export two separate shares, one for primary storage and the other for secondary storage. This
+could be a VM or physical host running an NFS service on a Linux OS or a virtual software appliance. Disk
+and network performance are still important in a small scale setup to get a good experience when deploying,
+running or snapshotting VMs.
+
+
+Large-Scale Setup
+=================
+
+In large-scale environments primary and secondary storage typically consist of independent physical storage arrays.
+
+Primary storage is likely to have to support mostly random read/write I/O once a template has been
+deployed. Secondary storage is only going to experience sustained sequential reads or writes.
+
+In clouds which will experience a large number of users taking snapshots or deploying VMs at the
+same time, secondary storage performance will be important to maintain a good user experience.
+
+It is important to start the design of your storage with the a rough profile of the workloads which it will
+be required to support. Care should be taken to consider the IOPS demands of your guest VMs as much as the
+volume of data to be stored and the bandwidth (MB/s) available at the storage interfaces.
+
+Storage Architecture
+********************
+
+There are many different storage types available which are generally suitable for CloudStack environments.
+Specific use cases should be considered when deciding the best one for your environment and financial
+constraints often make the 'perfect' storage architecture economically unrealistic.
+
+Broadly, the architectures of the available primary storage types can be split into 3 types:
+
+Local Storage
+=============
+
+Local storage works best for pure 'cloud-era' workloads which rarely need to be migrated between storage
+pools and where HA of individual VMs is not required. As SSDs become more mainstream/affordable, local
+storage based VMs can now be served with the size of IOPS which previously could only be generated by
+large arrays with 10s of spindles. Local storage is highly scalable because as you add hosts you would
+add the same proportion of storage. Local Storage is relatively inefficent as it can not take advantage
+of linked clones or any deduplication.
+
+
+'Traditional' node-based Shared Storage
+=======================================
+
+Traditional node-based storage are arrays which consist of a controller/controller pair attached to a
+number of disks in shelves.
+Ideally a cloud architecture would have one of these physical arrays per CloudStack pod to limit the
+'blast-radius' of a failure to a single pod. This is often not economically viable, however one should
+look to try to reduce the scale of any incident relative to any zone with any single array where
+possible.
+The use of shared storage enables workloads to be immediately restarted on an alternate host should a
+host fail. These shared storage arrays often have the ability to create 'tiers' of storage utilising
+say large SATA disks, 15k SAS disks and SSDs. These differently performing tiers can then be presented as
+different offerings to users.
+The sizing of an array should take into account the IOPS required by the workload as well as the volume
+of data to be stored. One should also consider the number of VMs which a storage array will be expected
+to support, and the maximum network bandwidth possible through the controllers.
+
+
+Clustered Shared Storage
+========================
+
+Clustered shared storage arrays are the new generation of storage which do not have a single set of
+interfaces where data enters and exits the array. Instead it is distributed between all of the active
+nodes giving greatly improved scalability and performance. Some shared storage arrays enable all data
+to continue to be accessible even in the event of the loss of an entire node.
+
+The network topology should be carefully considered when using clustered shared storage to avoid creating
+bottlenecks in the network fabric.
+
+
+Network Configuration For Storage
+=================================
+
+Care should be taken when designing your cloud to take into consideration not only the performance
+of your disk arrays but also the bandwidth available to move that traffic between the switch fabric and
+the array interfaces.
+
+CloudStack Networking For Storage
+*********************************
+
+The first thing to understand is the process of provisioning primary storage. When you create a primary
+storage pool for any given cluster, the CloudStack management server tells each hosts’ hypervisor to
+mount the NFS share or (iSCSI LUN). The storage pool will be presented within the hypervisor as a
+datastore (VMware), storage repository (XenServer/XCP) or a mount point (KVM), the important point is
+that it is the hypervisor itself that communicates with the primary storage, the CloudStack management
+server only communicates with the host hypervisor. Now, all hypervisors communicate with the outside
+world via some kind of management interface – think VMKernel port on ESXi or ‘Management Interface’ on
+XenServer. As the CloudStack management server needs to communicate with the hypervisor in the host,
+this management interface must be on the CloudStack ‘management’ or ‘private’ network. There may be
+other interfaces configured on your host carrying guest and public traffic to/from VMs within the hosts
+but the hypervisor itself doesn’t/can’t communicate over these interfaces.
+
+|hypervisorcomms.png|
+*Figure 1*: Hypervisor communications
+
+Separating Primary Storage traffic
+For those from a pure virtualisation background, the concept of creating a specific interface for storage
+traffic will not be new; it has long been best practice for iSCSI traffic to have a dedicated switch
+fabric to avoid any latency or contention issues.
+Sometimes in the cloud(Stack) world we forget that we are simply orchestrating processes that the
+hypervisors already carry out and that many ‘normal’ hypervisor configurations still apply.
+The logical reasoning which explains how this splitting of traffic works is as follows:
+
+1. If you want an additional interface over which the hypervisor can communicate (excluding teamed or bonded interfaces) you need to give it an IP address.
+#. The mechanism to create an additional interface that the hypervisor can use is to create an additional management interface
+#. So that the hypervisor can differentiate between the management interfaces they have to be in different (non-overlapping) subnets
+#. In order for the ‘primary storage’ management interface to communicate with the primary storage, the interfaces on the primary storage arrays must be in the same CIDR as the ‘primary storage’ management interface.
+#. Therefore the primary storage must be in a different subnet to the management network
+
+|subnetting storage.png|
+*Figure 2*: Subnetting of Storage Traffic
+
+|hypervisorcomms-secstorage.png|
+*Figure 3*: Hypervisor Communications with Separated Storage Traffic
+
+Other Primary Storage Types
+If you are using PreSetup or SharedMountPoints to connect to IP based storage then the same principles
+apply; if the primary storage and ‘primary storage interface’ are in a different subnet to the ‘management
+subnet’ then the hypervisor will use the ‘primary storage interface’ to communicate with the primary
+storage.
+
+
+Small-Scale Example Configurations
+==================================
+
+In this section we go through a few examples of how to set up storage to
+work properly on a few types of NFS and iSCSI storage systems.
+
+
+Linux NFS on Local Disks and DAS
+--------------------------------
+
+This section describes how to configure an NFS export on a standard
+Linux installation. The exact commands might vary depending on the
+operating system version.
+
+#. Install the RHEL/CentOS distribution on the storage server.
+
+#. If the root volume is more than 2 TB in size, create a smaller boot
+ volume to install RHEL/CentOS. A root volume of 20 GB should be
+ sufficient.
+
+#. After the system is installed, create a directory called /export.
+ This can each be a directory in the root partition itself or a mount
+ point for a large disk volume.
+
+#. If you have more than 16TB of storage on one host, create multiple
+ EXT3 file systems and multiple NFS exports. Individual EXT3 file
+ systems cannot exceed 16TB.
+
+#. After /export directory is created, run the following command to
+ configure it as an NFS export.
+
+ .. parsed-literal::
+
+ # echo "/export <CIDR>(rw,async,no_root_squash,no_subtree_check)" >> /etc/exports
+
+ Adjust the above command to suit your deployment needs.
+
+- **Limiting NFS export.** It is highly recommended that you limit the NFS export to a particular subnet by specifying a subnet mask (e.g.,”192.168.1.0/24”). By allowing access from only within the expected cluster, you avoid having non-pool member mount the storage. The limit you place must include the management network(s) and the storage network(s). If the two are the same network then one CIDR is sufficient. If you have a separate storage network you must provide separate CIDR’s for both or one CIDR that is broad enough to span both.
+
+
+ The following is an example with separate CIDRs:
+
+ .. parsed-literal::
+
+ /export 192.168.1.0/24(rw,async,no_root_squash,no_subtree_check) 10.50.1.0/24(rw,async,no_root_squash,no_subtree_check)
+
+- **Removing the async flag.** The async flag improves performance by allowing the NFS server to respond before writes are committed to the disk. Remove the async flag in your mission critical production deployment.
+
+6. Run the following command to enable NFS service.
+
+ .. parsed-literal::
+
+ # chkconfig nfs on
+
+#. Edit the /etc/sysconfig/nfs file and uncomment the following lines.
+
+ .. parsed-literal::
+
+ LOCKD_TCPPORT=32803
+ LOCKD_UDPPORT=32769
+ MOUNTD_PORT=892
+ RQUOTAD_PORT=875
+ STATD_PORT=662
+ STATD_OUTGOING_PORT=2020
+
+#. Edit the /etc/sysconfig/iptables file and add the following lines at
+ the beginning of the INPUT chain.
+
+ .. parsed-literal::
+
+ -A INPUT -m state --state NEW -p udp --dport 111 -j ACCEPT
+ -A INPUT -m state --state NEW -p tcp --dport 111 -j ACCEPT
+ -A INPUT -m state --state NEW -p tcp --dport 2049 -j ACCEPT
+ -A INPUT -m state --state NEW -p tcp --dport 32803 -j ACCEPT
+ -A INPUT -m state --state NEW -p udp --dport 32769 -j ACCEPT
+ -A INPUT -m state --state NEW -p tcp --dport 892 -j ACCEPT
+ -A INPUT -m state --state NEW -p udp --dport 892 -j ACCEPT
+ -A INPUT -m state --state NEW -p tcp --dport 875 -j ACCEPT
+ -A INPUT -m state --state NEW -p udp --dport 875 -j ACCEPT
+ -A INPUT -m state --state NEW -p tcp --dport 662 -j ACCEPT
+ -A INPUT -m state --state NEW -p udp --dport 662 -j ACCEPT
+
+#. Reboot the server.
+
+ An NFS share called /export is now set up.
+
+.. note::
+ When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text.
+
+
+Linux NFS on iSCSI
+------------------
+
+Use the following steps to set up a Linux NFS server export on an iSCSI
+volume. These steps apply to RHEL/CentOS 5 distributions.
+
+#. Install iscsiadm.
+
+ .. parsed-literal::
+
+ # yum install iscsi-initiator-utils
+ # service iscsi start
+ # chkconfig --add iscsi
+ # chkconfig iscsi on
+
+#. Discover the iSCSI target.
+
+ .. parsed-literal::
+
+ # iscsiadm -m discovery -t st -p <iSCSI Server IP address>:3260
+
+ For example:
+
+ .. parsed-literal::
+
+ # iscsiadm -m discovery -t st -p 172.23.10.240:3260 172.23.10.240:3260,1 iqn.2001-05.com.equallogic:0-8a0906-83bcb3401-16e0002fd0a46f3d-rhel5-test
+
+#. Log in.
+
+ .. parsed-literal::
+
+ # iscsiadm -m node -T <Complete Target Name> -l -p <Group IP>:3260
+
+ For example:
+
+ .. parsed-literal::
+
+ # iscsiadm -m node -l -T iqn.2001-05.com.equallogic:83bcb3401-16e0002fd0a46f3d-rhel5-test -p 172.23.10.240:3260
+
+#. Discover the SCSI disk. For example:
+
+ .. parsed-literal::
+
+ # iscsiadm -m session -P3 | grep Attached
+ Attached scsi disk sdb State: running
+
+#. Format the disk as ext3 and mount the volume.
+
+ .. parsed-literal::
+
+ # mkfs.ext3 /dev/sdb
+ # mkdir -p /export
+ # mount /dev/sdb /export
+
+#. Add the disk to /etc/fstab to make sure it gets mounted on boot.
+
+ .. parsed-literal::
+
+ /dev/sdb /export ext3 _netdev 0 0
+
+Now you can set up /export as an NFS share.
+
+- **Limiting NFS export.** In order to avoid data loss, it is highly
+ recommended that you limit the NFS export to a particular subnet by
+ specifying a subnet mask (e.g.,”192.168.1.0/24”). By allowing access
+ from only within the expected cluster, you avoid having non-pool
+ member mount the storage and inadvertently delete all its data. The
+ limit you place must include the management network(s) and the
+ storage network(s). If the two are the same network then one CIDR is
+ sufficient. If you have a separate storage network you must provide
+ separate CIDRs for both or one CIDR that is broad enough to span
+ both.
+
+ The following is an example with separate CIDRs:
+
+ .. parsed-literal::
+
+ /export 192.168.1.0/24(rw,async,no_root_squash,no_subtree_check) 10.50.1.0/24(rw,async,no_root_squash,no_subtree_check)
+
+- **Removing the async flag.** The async flag improves performance by
+ allowing the NFS server to respond before writes are committed to the
+ disk. Remove the async flag in your mission critical production
+ deployment.
+
+
+.. |hypervisorcomms.png| image:: /_static/images/hypervisorcomms.png
+ :alt: hypervisor storage communication
+.. |subnetting storage.png| image:: /_static/images/subnetting_storage.png
+ :alt: subnetted storage interfaces
+.. |hypervisorcomms-secstorage.png| image:: /_static/images/hypervisorcomms-secstorage.png
+ :alt: hypervisor communications to secondary storage
diff --git a/source/conf.py b/source/conf.py
new file mode 100644
index 0000000..5bc7660
--- /dev/null
+++ b/source/conf.py
@@ -0,0 +1,195 @@
+# -*- coding: utf-8 -*-
+#
+# Configuration file for the Sphinx documentation builder.
+#
+# This file does only contain a selection of the most common options. For a
+# full list see the documentation:
+# http://www.sphinx-doc.org/en/master/config
+
+# -- Path setup --------------------------------------------------------------
+
+# If extensions (or modules to document with autodoc) are in another directory,
+# add these directories to sys.path here. If the directory is relative to the
+# documentation root, use os.path.abspath to make it absolute, like shown here.
+#
+# import os
+# import sys
+# sys.path.insert(0, os.path.abspath('.'))
+
+
+# -- Project information -----------------------------------------------------
+
+project = 'Apache CloudStack'
+copyright = '2018, Apache Foundation'
+author = 'Apache CloudStack Project'
+
+# The short X.Y version
+version = '4.11'
+# The full version, including alpha/beta/rc tags
+release = '4.11.1.0'
+
+rst_epilog = """
+.. include:: /_global.rst
+"""
+# -- General configuration ---------------------------------------------------
+
+# If your documentation needs a minimal Sphinx version, state it here.
+#
+# needs_sphinx = '1.0'
+
+# Add any Sphinx extension module names here, as strings. They can be
+# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
+# ones.
+extensions = [
+ 'sphinx.ext.autodoc',
+ 'sphinx.ext.doctest',
+ 'sphinx.ext.intersphinx',
+ 'sphinx.ext.todo',
+]
+
+# Add any paths that contain templates here, relative to this directory.
+templates_path = ['_templates']
+
+# The suffix(es) of source filenames.
+# You can specify multiple suffix as a list of string:
+#
+# source_suffix = ['.rst', '.md']
+source_suffix = '.rst'
+
+# The master toctree document.
+master_doc = 'index'
+
+# The language for content autogenerated by Sphinx. Refer to documentation
+# for a list of supported languages.
+#
+# This is also used if you do content translation via gettext catalogs.
+# Usually you set "language" from the command line for these cases.
+language = None
+
+# List of patterns, relative to source directory, that match files and
+# directories to ignore when looking for source files.
+# This pattern also affects html_static_path and html_extra_path .
+exclude_patterns = []
+
+# The name of the Pygments (syntax highlighting) style to use.
+pygments_style = 'sphinx'
+
+
+# -- Options for HTML output -------------------------------------------------
+
+# The theme to use for HTML and HTML Help pages. See the documentation for
+# a list of builtin themes.
+#
+html_theme = 'sphinx_rtd_theme'
+
+# Theme options are theme-specific and customize the look and feel of a theme
+# further. For a list of options available for each theme, see the
+# documentation.
+#
+# html_theme_options = {}
+
+# Add any paths that contain custom static files (such as style sheets) here,
+# relative to this directory. They are copied after the builtin static files,
+# so a file named "default.css" will overwrite the builtin "default.css".
+html_static_path = ['_static']
+
+# Custom sidebar templates, must be a dictionary that maps document names
+# to template names.
+#
+# The default sidebars (for documents that don't match any pattern) are
+# defined by theme itself. Builtin themes are using these templates by
+# default: ``['localtoc.html', 'relations.html', 'sourcelink.html',
+# 'searchbox.html']``.
+#
+# html_sidebars = {}
+
+
+# -- Options for HTMLHelp output ---------------------------------------------
+
+# Output file base name for HTML help builder.
+htmlhelp_basename = 'ApacheCloudStackdoc'
+
+
+# -- Options for LaTeX output ------------------------------------------------
+
+latex_elements = {
+ # The paper size ('letterpaper' or 'a4paper').
+ #
+ # 'papersize': 'letterpaper',
+
+ # The font size ('10pt', '11pt' or '12pt').
+ #
+ # 'pointsize': '10pt',
+
+ # Additional stuff for the LaTeX preamble.
+ #
+ # 'preamble': '',
+
+ # Latex figure (float) alignment
+ #
+ # 'figure_align': 'htbp',
+}
+
+# Grouping the document tree into LaTeX files. List of tuples
+# (source start file, target name, title,
+# author, documentclass [howto, manual, or own class]).
+latex_documents = [
+ (master_doc, 'ApacheCloudStack.tex', 'Apache CloudStack Documentation',
+ 'Paul Angus', 'manual'),
+]
+
+
+# -- Options for manual page output ------------------------------------------
+
+# One entry per manual page. List of tuples
+# (source start file, name, description, authors, manual section).
+man_pages = [
+ (master_doc, 'apachecloudstack', 'Apache CloudStack Documentation',
+ [author], 1)
+]
+
+
+# -- Options for Texinfo output ----------------------------------------------
+
+# Grouping the document tree into Texinfo files. List of tuples
+# (source start file, target name, title, author,
+# dir menu entry, description, category)
+texinfo_documents = [
+ (master_doc, 'ApacheCloudStack', 'Apache CloudStack Documentation',
+ author, 'ApacheCloudStack', 'One line description of project.',
+ 'Miscellaneous'),
+]
+
+
+# -- Options for Epub output -------------------------------------------------
+
+# Bibliographic Dublin Core info.
+epub_title = project
+epub_author = author
+epub_publisher = author
+epub_copyright = copyright
+
+# The unique identifier of the text. This can be a ISBN number
+# or the project homepage.
+#
+# epub_identifier = ''
+
+# A unique identification for the text.
+#
+# epub_uid = ''
+
+# A list of files that should not be packed into the epub file.
+epub_exclude_files = ['search.html']
+
+
+# -- Extension configuration -------------------------------------------------
+
+# -- Options for intersphinx extension ---------------------------------------
+
+# Example configuration for intersphinx: refer to the Python standard library.
+intersphinx_mapping = {'https://docs.python.org/': None}
+
+# -- Options for todo extension ----------------------------------------------
+
+# If true, `todo` and `todoList` produce output, else they produce nothing.
+todo_include_todos = True
\ No newline at end of file
diff --git a/source/developersguide/alloc.rst b/source/developersguide/alloc.rst
new file mode 100644
index 0000000..00ce8c9
--- /dev/null
+++ b/source/developersguide/alloc.rst
@@ -0,0 +1,315 @@
+.. 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.
+
+
+Allocators
+==========
+
+CloudStack enables administrators to write custom allocators that will
+choose the Host to place a new guest and the storage host from which to
+allocate guest virtual disk images.
+
+These are following categories of allocators currently supported:
+
+- HostAllocators - Allows you to create custom rules to determine which
+ physical host to allocate the guest virtual machines on.
+
+- StoragePoolAllocators - Allows you to create custom rules to
+ determine which storage pool to allocate the guest virtual machines
+ on.
+
+
+Implementing a custom HostAllocator
+-----------------------------------
+
+HostAllocators are written by extending
+com.cloud.agent.manager.allocator.HostAllocator interface.
+
+
+HostAllocator Interface
+~~~~~~~~~~~~~~~~~~~~~~~
+
+The interface defines the following two methods.
+
+::
+
+ /**
+ * Checks if the VM can be upgraded to the specified ServiceOffering
+ * @param UserVm vm
+ * @param ServiceOffering offering
+ * @return boolean true if the VM can be upgraded
+ **/
+
+ publicboolean isVirtualMachineUpgradable(final UserVm vm, final ServiceOffering offering);
+
+ /**
+ * Determines which physical hosts are suitable to allocate the guest virtual machines on
+ *
+ * @paramVirtualMachineProfile vmProfile
+ * @paramDeploymentPlan plan
+ * @paramType type
+ * @paramExcludeList avoid
+ * @paramint returnUpTo
+ * @returnList<Host>List of hosts that are suitable for VM allocation
+ **/
+
+ publicList<Host> allocateTo( VirtualMachineProfile<?extendsVirtualMachine> vmProfile, DeploymentPlan plan, Type type, ExcludeList avoid, intreturnUpTo);
+
+A custom HostAllocator can be written by implementing the ‘allocateTo’
+method
+
+
+Input Parameters for the method ‘HostAllocator :: allocateTo’
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+*com.cloud.vm.VirtualMachineProfile vmProfile*
+
+VirtualMachineProfile describes one virtual machine. This allows the
+adapters like Allocators to process the information in the virtual
+machine and make determinations on what the virtual machine profile
+should look like before it is actually started on the hypervisor.
+
+HostAllocators can make use of the following information present in the
+VirtualMachineProfile:
+
+- The ServiceOffering that specifies configuration like requested CPU
+ speed, RAM etc necessary for the guest VM.
+
+- The VirtualMachineTemplate, the template to be used to start the VM.
+
+*com.cloud.deploy.DeploymentPlan plan*
+
+DeploymentPlan should specify:
+
+- dataCenterId: The data center the VM should deploy in
+
+- podId: The pod the Vm should deploy in; null if no preference
+
+- clusterId: The cluster the VM should deploy in; null if no preference
+
+- poolId: The storage pool the VM should be created in; null if no
+ preference
+
+*com.cloud.host.Host.Type type*
+
+Type of the Host needed for this guest VM. Currently
+com.cloud.host.Host.Type interface defines the following Host types:
+
+- Storage
+
+- Routing
+
+- SecondaryStorage
+
+- ConsoleProxy
+
+- ExternalFirewall
+
+- ExternalLoadBalancer
+
+*com.cloud.deploy.DeploymentPlanner.ExcludeList avoid*
+
+The ExcludeList specifies what datacenters, pods, clusters, hosts,
+storagePools should not be considered for allocating this guest VM.
+HostAllocators should avoid the hosts that are mentioned in
+ExcludeList.hostIds.
+
+- Set Long dcIds;
+
+- Set Long podIds;
+
+- Set Long clusterIds;
+
+- Set Long hostIds;
+
+- Set Long poolIds;
+
+*int returnUpTo*
+
+This specifies return up to that many available hosts for this guest VM.
+
+To get all possible hosts, set this value to -1.
+
+
+Reference HostAllocator implementation
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Refer com.cloud.agent.manager.allocator.impl.FirstFitAllocator that
+implements the HostAllocator interface. This allocator checks available
+hosts in the specified datacenter, Pod, Cluster and considering the
+given ServiceOffering requirements.
+
+If returnUpTo = 1, this allocator would return the first Host that fits
+the requirements of the guest VM.
+
+
+Loading a custom HostAllocator
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. Write a custom HostAllocator class, implementing the interface
+ described above.
+
+#. Package the code into a JAR file and make the JAR available in the
+ classpath of the Management Server/tomcat.
+
+#. Modify the components.xml and components-premium.xml files found in
+ /client/ tomcatconf as follows.
+
+#. Search for ‘HostAllocator’ in these files.
+
+ ::
+
+ <adapters key="com.cloud.agent.manager.allocator.HostAllocator">
+ <adapter name="FirstFit" class="com.cloud.agent.manager.allocator.impl.FirstFitAllocator"/>
+ </adapters>
+
+
+#. Replace the FirstFitAllocator with your class name. Optionally, you
+ can change the name of the adapter as well.
+
+#. Restart the Management Server.
+
+
+Implementing a custom StoragePoolAllocator
+------------------------------------------
+
+StoragePoolAllocators are written by extending
+com.cloud.storage.allocator. StoragePoolAllocator interface.
+
+
+StoragePoolAllocator Interface
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+A custom StoragePoolAllocator can be written by implementing the
+‘allocateTo’ method.
+
+::
+
+ /**
+ * Determines which storage pools are suitable for the guest virtual machine
+ * @param DiskProfile dskCh
+ * @param VirtualMachineProfile vmProfile
+ * @param DeploymentPlan plan
+ * @param ExcludeList avoid
+ * @param int returnUpTo
+ * @return List<StoragePool> List of storage pools that are suitable for the VM
+ **/
+
+ public List<StoragePool> allocateToPool(DiskProfile dskCh, VirtualMachineProfile<? extends VirtualMachine> vm, DeploymentPlan plan, ExcludeList avoid, int returnUpTo);
+
+
+This interface also contains some other methods to support some legacy
+code. However your custom allocator can extend the existing
+com.cloud.storage.allocator. AbstractStoragePoolAllocator. This class
+provides default implementation for all the other interface methods.
+
+
+Input Parameters for the method ‘StoragePoolAllocator :: allocateTo’
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+*com.cloud.vm.DiskProfile dskCh*
+
+DiskCharacteristics describes a disk and what functionality is required
+from it. It specifies the storage pool tags if any to be used while
+searching for a storage pool.
+
+*com.cloud.vm.VirtualMachineProfile vmProfile*
+
+VirtualMachineProfile describes one virtual machine. This allows the
+adapters like Allocators to process the information in the virtual
+machine and make determinations on what the virtual machine profile
+should look like before it is actually started on the hypervisor.
+
+StoragePoolAllocators can make use of the following information present
+in the VirtualMachineProfile:
+
+- The VirtualMachine instance that specifies properties of the guest
+ VM.
+
+- The VirtualMachineTemplate, the template to be used to start the VM.
+
+*com.cloud.deploy.DeploymentPlan plan*
+
+DeploymentPlan should specify:
+
+- dataCenterId: The data center the VM should deploy in
+
+- podId: The pod the VM should deploy in; null if no preference
+
+- clusterId: The cluster the VM should deploy in; null if no preference
+
+- poolId: The storage pool the VM should be created in; null if no
+ preference
+
+*com.cloud.deploy.DeploymentPlanner.ExcludeList avoid*
+
+The ExcludeList specifies what datacenters, pods, clusters, hosts,
+storagePools should not be considered for allocating this guest VM.
+StoragePoolAllocators should avoid the pools that are mentioned in
+ExcludeList.poolIds
+
+- Set Long dcIds;
+
+- Set Long podIds;
+
+- Set Long clusterIds;
+
+- Set Long hostIds;
+
+- Set Long poolIds;
+
+*int returnUpTo*
+
+This specifies return up to that many available pools for this guest VM
+
+To get all possible pools, set this value to -1
+
+
+Reference StoragePoolAllocator implementation
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Refer com.cloud.storage.allocator.FirstFitStoragePoolAllocator that
+implements the StoragePoolAllocator interface. This allocator checks
+available pools in the specified datacenter, Pod, Cluster and
+considering the given DiskProfile characteristics.
+
+If returnUpTo = 1, this allocator would return the first Storage Pool
+that fits the requirements of the guest VM.
+
+
+Loading a custom StoragePoolAllocator
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. Write a custom StoragePoolAllocator class, implementing the interface
+ described above.
+
+#. Package the code into a JAR file and make the JAR available in the
+ classpath of the Management Server/tomcat.
+
+#. Modify the components.xml and components-premium.xml files found in
+ /client/ tomcatconf as follows.
+
+#. Search for ‘StoragePoolAllocator’ in these files.
+
+ ::
+
+ <adapters key="com.cloud.storage.allocator.StoragePoolAllocator">
+ <adapter name="Storage" class="com.cloud.storage.allocator.FirstFitStoragePoolAllocator"/>
+ </adapters>
+
+#. Replace the FirstFitStoragePoolAllocator with your class name.
+ Optionally, you can change the name of the adapter as well.
+
+#. Restart the Management Server.
diff --git a/source/developersguide/ansible.rst b/source/developersguide/ansible.rst
new file mode 100644
index 0000000..c0627db
--- /dev/null
+++ b/source/developersguide/ansible.rst
@@ -0,0 +1,441 @@
+.. 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.
+
+
+Deploying CloudStack with Ansible
+=================================
+
+In this article, `Paul Angus <https://twitter.com/CloudyAngus>`__ Cloud
+Architect at ShapeBlue takes a look at using Ansible to Deploy an
+Apache CloudStack cloud.
+
+
+What is Ansible
+---------------
+
+Ansible is a deployment and configuration management tool similar in
+intent to Chef and Puppet. It allows (usually) DevOps teams to
+orchestrate the deployment and configuration of their environments
+without having to re-write custom scripts to make changes.
+
+Like Chef and Puppet, Ansible is designed to be idempotent. This means
+that you determine the state you want a host to be in and Ansible will
+decide if it needs to act in order to achieve that state.
+
+
+There’s already Chef and Puppet, so what’s the fuss about Ansible?
+------------------------------------------------------------------
+
+Let’s take it as a given that configuration management makes life much
+easier (and is quite cool), Ansible only needs an SSH connection to the
+hosts that you’re going to manage to get started. While Ansible requires
+Python 2.4 or greater on the host you’re going to manage in order to
+leverage the vast majority of its functionality, it is able to connect
+to hosts which don’t have Python installed in order to then install
+Python, so it’s not really a problem. This greatly simplifies the
+deployment procedure for hosts, avoiding the need to pre-install agents
+onto the clients before the configuration management can take over.
+
+Ansible will allow you to connect as any user to a managed host (with
+that user’s privileges) or by using public/private keys – allowing fully
+automated management.
+
+There also doesn’t need to be a central server to run everything, as
+long as your playbooks and inventories are in-sync you can create as
+many Ansible servers as you need (generally a bit of Git pushing and
+pulling will do the trick).
+
+Finally – its structure and language is pretty simple and clean. I’ve
+found it a bit tricky to get the syntax correct for variables in some
+circumstances, but otherwise I’ve found it one of the easier tools to
+get my head around.
+
+
+So let’s see something
+----------------------
+
+For this example we’re going to create an Ansible server which will then
+deploy a CloudStack server. Both of these servers will be CentOS 6.4
+virtual machines.
+
+
+Installing Ansible
+------------------
+
+Installing Ansible is blessedly easy. We generally prefer to use CentOS
+so to install Ansible you run the following commands on the Ansible
+server.
+
+::
+
+ # rpm -ivh http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
+ # yum install -y ansible
+
+And that’s it.
+
+*(There is a commercial version which has more features such as callback
+to request configurations and a RESTful API and also support. The
+installation of this is different)*
+
+By default Ansible uses /etc/ansible to store your playbooks, I tend to
+move it, but there’s no real problem with using the default location.
+Create yourself a little directory structure to get started with. The
+documentation recommends something like this:
+
+
+Playbooks
+---------
+
+Ansible uses playbooks to specify the state in which you wish the target
+host to be in to be able to accomplish its role. Ansible playbooks are
+written in YAML format.
+
+
+Modules
+-------
+
+To get Ansible to do things you specify the hosts a playbook will act
+upon and then call modules and supply arguments which determine what
+Ansible will do to those hosts.
+
+To keep things simple, this example is a cut-down version of a full
+deployment. This example creates a single management server with a local
+MySQL server and assumes you have your secondary storage already
+provisioned somewhere. For this example I’m also not going to include
+securing the MySQL server, configuring NTP or using Ansible to configure
+the networking on the hosts either. Although normally we’d use Ansible
+to do exactly that.
+
+The pre-requisites to this CloudStack build are:
+
+- A CentOS 6.4 host to install CloudStack on
+
+- An IP address already assigned on the ACS management host
+
+- The ACS management host should have a resolvable FQDN (either through
+ DNS or the host file on the ACS management host)
+
+- Internet connectivity on the ACS management host
+
+
+Planning
+--------
+
+The first step I use is to list all of the tasks I think I’ll need and
+group them or split them into logical blocks. So for this deployment of
+CloudStack I’d start with:
+
+- Configure selinux
+
+- (libselinux-python required for Ansible to work with selinux enabled
+ hosts)
+
+- Install and configure MySQL
+
+- (Python MySQL-DB required for Ansible MySQL module)
+
+- Install cloud-client
+
+- Seed secondary storage
+
+Ansible is built around the idea of hosts having roles, so generally you
+would group or manage your hosts by their roles. So now to create some
+roles for these tasks
+
+I’ve created:
+
+- cloudstack-manager
+
+- mysql
+
+First up we need to tell Ansible where to find our CloudStack management
+host. In the root Ansible directory there is a file called ‘hosts’
+(/etc/Ansible/hosts) add a section like this:
+
+::
+
+ [acs-manager]
+ xxx.xxx.xxx.xxx
+
+where xxx.xxx.xxx.xxx is the ip address of your ACS management host.
+
+
+MySQL
+-----
+
+So let’s start with the MySQL server. We’ll need to create a task
+within the mysql role directory called main.yml. The ‘task’ in this case
+to have MySQL running and configured on the target host. The contents of
+the file will look like this:
+
+::
+
+ -name: Ensure mysql server is installed
+
+ yum: name=mysql-server state=present
+
+ - name: Ensure mysql python is installed
+
+ yum: name=MySQL-python state=present
+
+
+ - name: Ensure selinux python bindings are installed
+
+ yum: name=libselinux-python state=present
+
+ - name: Ensure cloudstack specfic my.cnf lines are present
+
+ lineinfile: dest=/etc/my.cnf regexp=’$item’ insertafter=”symbolic-links=0″ line=’$item’
+
+ with\_items:
+
+ – skip-name-resolve
+
+ – default-time-zone=’+00:00′
+
+ – innodb\_rollback\_on\_timeout=1
+
+ – innodb\_lock\_wait\_timeout=600
+
+ – max\_connections=350
+
+ – log-bin=mysql-bin
+
+ – binlog-format = ‘ROW’
+
+
+ - name: Ensure MySQL service is started
+
+ service: name=mysqld state=started
+
+ - name: Ensure MySQL service is enabled at boot
+
+ service: name=mysqld enabled=yes
+
+
+
+ - name: Ensure root password is set
+
+ mysql\_user: user=root password=$mysql\_root\_password host=localhost
+
+ ignore\_errors: true
+
+ - name: Ensure root has sufficient privileges
+
+ mysql\_user: login\_user=root login\_password=$mysql\_root\_password user=root host=% password=$mysql\_root\_password priv=\*.\*:GRANT,ALL state=present
+
+This needs to be saved as `/etc/ansible/roles/mysql/tasks/main.yml`
+
+As explained earlier, this playbook in fact describes the state of the
+host rather than setting out commands to be run. For instance, we
+specify certain lines which must be in the my.cnf file and allow Ansible
+to decide whether or not it needs to add them.
+
+Most of the modules are self-explanatory once you see them, but to run
+through them briefly;
+
+The ‘yum’ module is used to specify which packages are required, the
+‘service’ module controls the running of services, while the
+‘mysql\_user’ module controls mysql user configuration. The ‘lineinfile’
+module controls the contents in a file.
+
+ We have a couple of variables which need declaring. You could do that
+within this playbook or its ‘parent’ playbook, or as a higher level
+variable. I’m going to declare them in a higher level playbook. More on
+this later.
+
+ That’s enough to provision a MySQL server. Now for the management
+server.
+
+
+CloudStack Management server service
+------------------------------------
+
+For the management server role we create a main.yml task like this:
+
+::
+
+ - name: Ensure selinux python bindings are installed
+
+ yum: name=libselinux-python state=present
+
+
+ - name: Ensure the Apache Cloudstack Repo file exists as per template
+
+ template: src=cloudstack.repo.j2 dest=/etc/yum.repos.d/cloudstack.repo
+
+
+ - name: Ensure selinux is in permissive mode
+
+ command: setenforce permissive
+
+
+ - name: Ensure selinux is set permanently
+
+ selinux: policy=targeted state=permissive
+
+
+ -name: Ensure CloudStack packages are installed
+
+ yum: name=cloud-client state=present
+
+
+ - name: Ensure vhdutil is in correct location
+
+ get\_url: url=http://download.cloudstack.org/tools/vhd-util dest=/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/vhd-util mode=0755
+
+
+Save this as `/etc/ansible/roles/cloudstack-management/tasks/main.yml`
+
+Now we have some new elements to deal with. The Ansible template module
+uses Jinja2 based templating. As we’re doing a simplified example here,
+the Jinja template for the cloudstack.repo won’t have any variables in
+it, so it would simply look like this:
+
+::
+
+ [cloudstack]
+ name=cloudstack
+ baseurl=http://download.cloudstack.org/rhel/4.2/
+ enabled=1
+ gpgcheck=0
+
+This is saved in
+`/etc/ansible/roles/cloudstack-manager/templates/cloudstack.repo.j2`
+
+That gives us the packages installed, we need to set up the database. To
+do this I’ve created a separate task called setupdb.yml
+
+::
+
+ - name: cloudstack-setup-databases
+ command: /usr/bin/cloudstack-setup-databases cloud:{{mysql\_cloud\_password }}@localhost –deploy-as=root:{{mysql\_root\_password }}
+
+ - name: Setup CloudStack manager
+ command: /usr/bin/cloudstack-setup-management
+
+
+Save this as: `/etc/ansible/roles/cloudstack-management/tasks/setupdb.yml`
+
+As there isn’t (as yet) a CloudStack module, Ansible doesn’t inherently
+know whether or not the databases have already been provisioned,
+therefore this step is not currently idempotent and will overwrite any
+previously provisioned databases.
+
+There are some more variables here for us to declare later.
+
+
+System VM Templates:
+--------------------
+
+Finally we would want to seed the system VM templates into the secondary
+storage. The playbook for this would look as follows:
+
+::
+
+ - name: Ensure secondary storage mount exists
+ file: path={{ tmp\_nfs\_path }} state=directory
+
+
+ - name: Ensure NFS storage is mounted
+ mount: name={{ tmp\_nfs\_path }} src={{ sec\_nfs\_ip }}:{{sec\_nfs\_path }} fstype=nfs state=mounted opts=nolock
+
+
+ - name: Seed secondary storage
+ command:
+ /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt -m {{ tmp\_nfs\_path }} -u http://download.cloud.com/templates/4.2/systemvmtemplate-2013-06-12-master-kvm.qcow2.bz2 -h kvm -F
+
+ command:
+ /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt -m {{ tmp\_nfs\_path }} -u http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master-xen.vhd.bz2 -h xenserver -F
+
+ command:
+ /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt -m {{ tmp\_nfs\_path }} -u http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ov -h vmware -F
+
+
+Save this as `/etc/ansible/roles/cloudstack-manager/tasks/seedstorage.yml`
+
+Again, there isn’t a CloudStack module so Ansible will always run this
+even if the secondary storage already has the templates in it.
+
+
+Bringing it all together
+------------------------
+
+Ansible can use playbooks which run other playbooks, this allows us to
+group these playbooks together and declare variables across all of the
+individual playbooks. So in the Ansible playbook directory create a file
+called deploy-cloudstack.yml, which would look like this:
+
+::
+
+ -hosts: acs-manager
+
+ vars:
+
+ mysql\_root\_password: Cl0ud5tack
+ mysql\_cloud\_password: Cl0ud5tack
+ tmp\_nfs\_path: /mnt/secondary
+ sec\_nfs\_ip: IP\_OF\_YOUR\_SECONDARY\_STORAGE
+ sec\_nfs\_path: PATH\_TO\_YOUR\_SECONDARY\_STORAGE\_MOUNT
+
+
+ roles:
+
+ – mysql
+ – cloudstack-manager
+
+ tasks:
+
+ – include: /etc/ansible/roles/cloudstack-manager/tasks/setupdb.yml
+ – include: /etc/ansible/roles/cloudstack-manager/tasks/seedstorage.yml
+
+
+Save this as `/etc/ansible/deploy-cloudstack.yml` inserting the IP
+address and path for your secondary storage and changing the passwords
+if you wish to.
+
+To run this go to the Ansible directory (cd /etc/ansible ) and run:
+
+::
+
+ # ansible-playbook deploy-cloudstack.yml -k
+
+‘-k’ tells Ansible to ask you for the root password to connect to the
+remote host.
+
+Now log in to the CloudStack UI on the new management server.
+
+
+How is this example different from a production deployment?
+-----------------------------------------------------------
+
+In a production deployment, the Ansible playbooks would configure
+multiple management servers connected to master/slave replicating MySQL
+databases along with any other infrastructure components required and
+deploy and configure the hypervisor hosts. We would also have a
+dedicated file describing the hosts in the environment and a dedicated
+file containing variables which describe the environment.
+
+The advantage of using a configuration management tool such as Ansible
+is that we can specify components like the MySQL database VIP once and
+use it multiple times when configuring the MySQL server itself and other
+components which need to use that information.
+
+
+Acknowledgements
+----------------
+
+Thanks to Shanker Balan for introducing me to Ansible and a load of
+handy hints along the way.
diff --git a/source/developersguide/dev.rst b/source/developersguide/dev.rst
new file mode 100644
index 0000000..7c7b31b
--- /dev/null
+++ b/source/developersguide/dev.rst
@@ -0,0 +1,1340 @@
+.. 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.
+
+
+Programmer Guide
+================
+
+This guide shows how to develop CloudStack, use the API for operation
+and integration, access the usage data and use CloudStack specific tools
+to ease development, testing and integration.
+
+
+The CloudStack API
+------------------
+
+Getting Started
+~~~~~~~~~~~~~~~
+
+To get started using the CloudStack API, you should have the following:
+
+- URL of the CloudStack server you wish to integrate with.
+
+- Both the API Key and Secret Key for an account. This should have been
+ generated by the administrator of the cloud instance and given to
+ you.
+
+- Familiarity with HTTP GET/POST and query strings.
+
+- Knowledge of either XML or JSON.
+
+- Knowledge of a programming language that can generate HTTP requests;
+ for example, Java or PHP.
+
+
+Roles
+~~~~~
+
+The CloudStack API supports three access roles:
+
+#. Root Admin. Access to all features of the cloud, including both
+ virtual and physical resource management.
+
+#. Domain Admin. Access to only the virtual resources of the clouds that
+ belong to the administrator’s domain.
+
+#. User. Access to only the features that allow management of the user’s
+ virtual instances, storage, and network.
+
+
+API Reference Documentation
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can find all the API reference documentation at the below site:
+
+`http://cloudstack.apache.org/docs/api/
+<http://cloudstack.apache.org/docs/api/>`__
+
+
+Making API Requests
+~~~~~~~~~~~~~~~~~~~~
+
+All CloudStack API requests are submitted in the form of a HTTP GET/POST
+with an associated command and any parameters. A request is composed of
+the following whether in HTTP or HTTPS:
+
+- CloudStack API URL: This is the web services API entry point(for
+ example, http://www.example.com:8080/client/api)
+
+- Command: The web services command you wish to execute, such as start
+ a virtual machine or create a disk volume
+
+- Parameters: Any additional required or optional parameters for the
+ command
+
+A sample API GET request looks like the following:
+
+.. parsed-literal::
+
+ http://localhost:8080/client/api?command=deployVirtualMachine&serviceOfferingId=1&diskOfferingId=1&templateId=2&zoneId=4&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D
+
+Or in a more readable format:
+
+.. parsed-literal::
+
+ 1. http://localhost:8080/client/api
+ 2. ?command=deployVirtualMachine
+ 3. &serviceOfferingId=1
+ 4. &diskOfferingId=1
+ 5. &templateId=2
+ 6. &zoneId=4
+ 7. &apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXqjB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ
+ 8. &signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D
+
+The first line is the CloudStack API URL. This is the Cloud instance you
+wish to interact with.
+
+The second line refers to the command you wish to execute. In our
+example, we are attempting to deploy a fresh new virtual machine. It is
+preceded by a (?) to separate itself from the CloudStack API URL.
+
+Lines 3-6 are the parameters for this given command. To see the command
+and its request parameters, please refer to the appropriate section in
+the CloudStack API documentation. Each parameter field-value pair
+(field=value) is preceded by an ampersand character (&).
+
+Line 7 is the user API Key that uniquely identifies the account. See
+Signing API Requests on page 7.
+
+Line 8 is the signature hash created to authenticate the user account
+executing the API command.
+
+
+Signing API Requests
+~~~~~~~~~~~~~~~~~~~~
+
+Whether you access the CloudStack API with HTTP or HTTPS, it must still
+be signed so that CloudStack can verify the caller has been
+authenticated and authorized to execute the command. Make sure that you
+have both the API Key and Secret Key provided by the CloudStack
+administrator for your account before proceeding with the signing
+process.
+
+To show how to sign a request, we will re-use the previous example.
+
+.. parsed-literal::
+
+ http://http://localhost:8080/client/api?command=deployVirtualMachine&serviceOfferingId=1&diskOfferingId=1&templateId=2&zoneId=4&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D
+
+Breaking this down, we have several distinct parts to this URL.
+
+- Base URL: This is the base URL to the CloudStack Management Server.
+
+ .. parsed-literal::
+
+ http://localhost:8080
+
+- API Path: This is the path to the API Servlet that processes the
+ incoming requests.
+
+ .. parsed-literal::
+
+ /client/api?
+
+- Command String: This part of the query string comprises of the
+ command, its parameters, and the API Key that identifies the account.
+
+ .. note::
+ As with all query string parameters of field-value pairs, the "field"
+ component is case insensitive while all "value" values are case
+ sensitive.
+
+ .. sourcecode: bash
+
+ command=deployVirtualMachine&serviceOfferingId=1&diskOfferingId=1&templateId=2&zoneId=4&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ
+
+- Signature: This is the signature of the command string that is
+ generated using a combination of the user’s Secret Key and the HMAC
+ SHA-1 hashing algorithm.
+
+ .. parsed-literal::
+
+ &signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D
+
+Every API request has the format Base URL+API Path+Command
+String+Signature.
+
+To generate the signature.
+
+#. For each field-value pair (as separated by a '&') in the Command
+ String, URL encode each value so that it can be safely sent via HTTP
+ GET.
+
+ .. note:: Make sure all spaces are encoded as "%20" rather than "+".
+
+#. Lower case the entire Command String and sort it alphabetically via
+ the field for each field-value pair. The result of this step would
+ look like the following.
+
+ .. parsed-literal::
+
+ apikey=mivr6x7u6bn_sdahobpjnejpgest35exq-jb8cg20yi3yaxxcgpyuairmfi_ejtvwz0nukkjbpmy3y2bcikwfq&command=deployvirtualmachine&diskofferingid=1&serviceofferingid=1&templateid=2&zoneid=4
+
+#. Take the sorted Command String and run it through the HMAC SHA-1
+ hashing algorithm (most programming languages offer a utility method
+ to do this) with the user’s Secret Key. Base64 encode the resulting
+ byte array in UTF-8 so that it can be safely transmitted via HTTP.
+ The final string produced after Base64 encoding should be
+ "Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D".
+
+ By reconstructing the final URL in the format Base URL+API
+ Path+Command String+Signature, the final URL should look like:
+
+ .. parsed-literal::
+
+ http://localhost:8080/client/api?command=deployVirtualMachine&serviceOfferingId=1&diskOfferingId=1&templateId=2&zoneId=4&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D
+
+
+How to sign an API call with Python
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To illustrate the procedure used to sign API calls we present a step by
+step interactive session using Python.
+
+First import the required modules:
+
+.. parsed-literal::
+
+ $python
+ Python 2.7.3 (default, Nov 17 2012, 19:54:34)
+ [GCC 4.2.1 Compatible Apple Clang 4.1 ((tags/Apple/clang-421.11.66))] on darwin
+ Type "help", "copyright", "credits" or "license" for more information.
+ >>> import urllib2
+ >>> import urllib
+ >>> import hashlib
+ >>> import hmac
+ >>> import base64
+
+
+Define the endpoint of the Cloud, the command that you want to execute
+and the keys of the user.
+
+.. parsed-literal::
+
+ >>> baseurl='http://localhost:8080/client/api?'
+ >>> request={}
+ >>> request['command']='listUsers'
+ >>> request['response']='json'
+ >>> request['apikey']='plgWJfZK4gyS3mOMTVmjUVg-X-jlWlnfaUJ9GAbBbf9EdM-kAYMmAiLqzzq1ElZLYq_u38zCm0bewzGUdP66mg'
+ >>> secretkey='VDaACYb0LV9eNjTetIOElcVQkvJck_J_QljX_FcHRj87ZKiy0z0ty0ZsYBkoXkY9b7eq1EhwJaw7FF3akA3KBQ'
+
+
+Build the request string:
+
+.. parsed-literal::
+
+ >>> request_str='&'.join(['='.join([k,urllib.quote_plus(request[k])]) for k in request.keys()])
+ >>> request_str
+ 'apikey=plgWJfZK4gyS3mOMTVmjUVg-X-jlWlnfaUJ9GAbBbf9EdM-kAYMmAiLqzzq1ElZLYq_u38zCm0bewzGUdP66mg&command=listUsers&response=json'
+
+
+Compute the signature with hmac, do a 64 bit encoding and a url
+encoding:
+
+.. parsed-literal::
+
+ >>> sig_str='&'.join(['='.join([k.lower(),urllib.quote_plus(request[k].lower().replace('+','%20'))])for k in sorted(request.iterkeys())])
+ >>> sig_str 'apikey=plgwjfzk4gys3momtvmjuvg-x-jlwlnfauj9gabbbf9edm-kaymmailqzzq1elzlyq_u38zcm0bewzgudp66mg&command=listusers&response=json'
+ >>> sig=hmac.new(secretkey,sig_str,hashlib.sha1)
+ >>> sig
+ <hmac.HMAC instance at 0x10d91d680>
+ >>> sig=hmac.new(secretkey,sig_str,hashlib.sha1).digest()
+ >>> sig
+ 'M:]\x0e\xaf\xfb\x8f\xf2y\xf1p\x91\x1e\x89\x8a\xa1\x05\xc4A\xdb'
+ >>> sig=base64.encodestring(hmac.new(secretkey,sig_str,hashlib.sha1).digest())
+ >>> sig
+ 'TTpdDq/7j/J58XCRHomKoQXEQds=\n'
+ >>> sig=base64.encodestring(hmac.new(secretkey,sig_str,hashlib.sha1).digest()).strip()
+ >>> sig
+ 'TTpdDq/7j/J58XCRHomKoQXEQds='
+ >>> sig=urllib.quote_plus(base64.encodestring(hmac.new(secretkey,sig_str,hashlib.sha1).digest()).strip())
+
+
+Finally, build the entire string and do an http GET:
+
+.. parsed-literal::
+
+ >>> req=baseurl+request_str+'&signature='+sig
+ >>> req
+ 'http://localhost:8080/client/api?apikey=plgWJfZK4gyS3mOMTVmjUVg-X-jlWlnfaUJ9GAbBbf9EdM-kAYMmAiLqzzq1ElZLYq_u38zCm0bewzGUdP66mg&command=listUsers&response=json&signature=TTpdDq%2F7j%2FJ58XCRHomKoQXEQds%3D'
+ >>> res=urllib2.urlopen(req)
+ >>> res.read()
+ '{ "listusersresponse" : { "count":3 ,"user" : [ {"id":"7ed6d5da-93b2-4545-a502-23d20b48ef2a","username":"admin","firstname":"admin","lastname":"cloud","created":"2012-07-05T12:18:27-0700","state":"enabled","account":"admin","accounttype":1,"domainid":"8a111e58-e155-4482-93ce-84efff3c7c77","domain":"ROOT","apikey":"plgWJfZK4gyS3mOMTVmjUVg-X-jlWlnfaUJ9GAbBbf9EdM-kAYMmAiLqzzq1ElZLYq_u38zCm0bewzGUdP66mg","secretkey":"VDaACYb0LV9eNjTetIOElcVQkvJck_J_QljX_FcHRj87ZKiy0z0ty0ZsYBkoXkY9b7eq1EhwJaw7FF3akA3KBQ","accountid":"7548ac03-af1d-4c1c-9064-2f3e2c0eda0d"}, {"id":"1fea6418-5576-4989-a21e-4790787bbee3","username":"runseb","firstname":"foobar","lastname":"goa","email":"joe@smith.com","created":"2013-04-10T16:52:06-0700","state":"enabled","account":"admin","accounttype":1,"domainid":"8a111e58-e155-4482-93ce-84efff3c7c77","domain":"ROOT","apikey":"Xhsb3MewjJQaXXMszRcLvQI9_NPy_UcbDj1QXikkVbDC9MDSPwWdtZ1bUY1H7JBEYTtDDLY3yuchCeW778GkBA","secretkey":"gIsgmi8C5YwxMHjX5o51pSe0kqs6JnKriw0jJBLceY5bgnfzKjL4aM6ctJX-i1ddQIHJLbLJDK9MRzsKk6xZ_w","accountid":"7548ac03-af1d-4c1c-9064-2f3e2c0eda0d"}, {"id":"52f65396-183c-4473-883f-a37e7bb93967","username":"toto","firstname":"john","lastname":"smith","email":"john@smith.com","created":"2013-04-23T04:27:22-0700","state":"enabled","account":"admin","accounttype":1,"domainid":"8a111e58-e155-4482-93ce-84efff3c7c77","domain":"ROOT","apikey":"THaA6fFWS_OmvU8od201omxFC8yKNL_Hc5ZCS77LFCJsRzSx48JyZucbUul6XYbEg-ZyXMl_wuEpECzK-wKnow","secretkey":"O5ywpqJorAsEBKR_5jEvrtGHfWL1Y_j1E4Z_iCr8OKCYcsPIOdVcfzjJQ8YqK0a5EzSpoRrjOFiLsG0hQrYnDA","accountid":"7548ac03-af1d-4c1c-9064-2f3e2c0eda0d"} ] } }'
+
+
+Enabling API Call Expiration
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can set an expiry timestamp on API calls to prevent replay attacks
+over non-secure channels, such as HTTP. The server tracks the expiry
+timestamp you have specified and rejects all the subsequent API requests
+that come in after this validity period.
+
+To enable this feature, add the following parameters to the API request:
+
+- signatureVersion=3: If the signatureVersion parameter is missing or
+ is not equal to 3, the expires parameter is ignored in the API
+ request.
+
+- expires=YYYY-MM-DDThh:mm:ssZ: Specifies the date and time at which
+ the signature included in the request is expired. The timestamp is
+ expressed in the YYYY-MM-DDThh:mm:ssZ format, as specified in the ISO
+ 8601 standard.
+
+For example:
+
+.. parsed-literal::
+
+ expires=2011-10-10T12:00:00+0530
+
+A sample API request with expiration is given below:
+
+.. parsed-literal::
+
+ http://<IPAddress>:8080/client/api?command=listZones&signatureVersion=3&expires=2011-10-10T12:00:00+0530&apiKey=miVr6X7u6bN_sdahOBpjNejPgEsT35eXq-jB8CG20YI3yaxXcgpyuaIRmFI_EJTVwZ0nUkkJbPmY3y2bciKwFQ&signature=Lxx1DM40AjcXU%2FcaiK8RAP0O1hU%3D
+
+
+Limiting the Rate of API Requests
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You can limit the rate at which API requests can be placed for each
+account. This is useful to avoid malicious attacks on the Management
+Server, prevent performance degradation, and provide fairness to all
+accounts.
+
+If the number of API calls exceeds the threshold, an error message is
+returned for any additional API calls. The caller will have to retry
+these API calls at another time.
+
+
+Configuring the API Request Rate
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To control the API request rate, use the following global configuration
+settings:
+
+- `api.throttling.enabled` - Enable/Disable API throttling. By default,
+ this setting is false, so API throttling is not enabled.
+
+- `api.throttling.interval` (in seconds) - Time interval during which the
+ number of API requests is to be counted. When the interval has
+ passed, the API count is reset to 0.
+
+- `api.throttling.max` - Maximum number of APIs that can be placed within
+ the `api.throttling.interval` period.
+
+- `api.throttling.cachesize` - Cache size for storing API counters. Use a
+ value higher than the total number of accounts managed by the cloud.
+ One cache entry is needed for each account, to store the running API
+ total for that account.
+
+
+Limitations on API Throttling
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The following limitations exist in the current implementation of this
+feature.
+
+.. note::
+ Even with these limitations, CloudStack is still able to effectively use
+ API throttling to avoid malicious attacks causing denial of service.
+
+- In a deployment with multiple Management Servers, the cache is not
+ synchronized across them. In this case, CloudStack might not be able
+ to ensure that only the exact desired number of API requests are
+ allowed. In the worst case, the number of API calls that might be
+ allowed is (number of Management Servers) \* (api.throttling.max).
+
+- The API commands resetApiLimit and getApiLimit are limited to the
+ Management Server where the API is invoked.
+
+
+API Responses
+~~~~~~~~~~~~~
+
+Response Formats: XML and JSON
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+CloudStack supports two formats as the response to an API call. The
+default response is XML. If you would like the response to be in JSON,
+add `&response=json` to the Command String.
+
+The two response formats differ in how they handle blank fields. In
+JSON, if there is no value for a response field, it will not appear in
+the response. If all the fields were empty, there might be no response
+at all. In XML, even if there is no value to be returned, an empty field
+will be returned as a placeholder XML element.
+
+Sample XML Response:
+
+.. parsed-literal::
+
+ <listipaddressesresponse>
+ <allocatedipaddress>
+ <ipaddress>192.168.10.141</ipaddress>
+ <allocated>2009-09-18T13:16:10-0700</allocated>
+ <zoneid>4</zoneid>
+ <zonename>WC</zonename>
+ <issourcenat>true</issourcenat>
+ </allocatedipaddress>
+ </listipaddressesresponse>
+
+Sample JSON Response:
+
+.. parsed-literal::
+
+ { "listipaddressesresponse" :
+ { "allocatedipaddress" :
+ [
+ {
+ "ipaddress" : "192.168.10.141",
+ "allocated" : "2009-09-18T13:16:10-0700",
+ "zoneid" : "4",
+ "zonename" : "WC",
+ "issourcenat" : "true"
+ }
+ ]
+ }
+ }
+
+
+Maximum Result Pages Returned
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+For each cloud, there is a default upper limit on the number of results
+that any API command will return in a single page. This is to help
+prevent overloading the cloud servers and prevent DOS attacks. For
+example, if the page size limit is 500 and a command returns 10,000
+results, the command will return 20 pages.
+
+The default page size limit can be different for each cloud. It is set
+in the global configuration parameter `default.page.size`. If your cloud
+has many users with lots of VMs, you might need to increase the value of
+this parameter. At the same time, be careful not to set it so high that
+your site can be taken down by an enormous return from an API call. For
+more information about how to set global configuration parameters, see
+"Describe Your Deployment" in the Installation Guide.
+
+To decrease the page size limit for an individual API command, override
+the global setting with the page and pagesize parameters, which are
+available in any list\* command (listCapabilities, listDiskOfferings,
+etc.).
+
+- Both parameters must be specified together.
+
+- The value of the pagesize parameter must be smaller than the value of
+ default.page.size. That is, you can not increase the number of
+ possible items in a result page, only decrease it.
+
+For syntax information on the list\* commands, see the API Reference.
+
+
+Error Handling
+~~~~~~~~~~~~~~
+
+If an error occurs while processing an API request, the appropriate
+response in the format specified is returned. Each error response
+consists of an error code and an error text describing what possibly can
+go wrong. Below is a list of possible error codes:
+
+You can now find the CloudStack-specific error code in the exception
+response for each type of exception. The following list of error codes
+is added to the new class named CSExceptionErrorCode.
+
+4250 : "com.cloud.utils.exception.CloudRuntimeException"
+
+4255 : "com.cloud.utils.exception.ExceptionUtil"
+
+4260 : "com.cloud.utils.exception.ExecutionException"
+
+4265 : "com.cloud.utils.exception.HypervisorVersionChangedException"
+
+4270 : "com.cloud.utils.exception.RuntimeCloudException"
+
+4275 : "com.cloud.exception.CloudException"
+
+4280 : "com.cloud.exception.AccountLimitException"
+
+4285 : "com.cloud.exception.AgentUnavailableException"
+
+4290 : "com.cloud.exception.CloudAuthenticationException"
+
+4295 : "com.cloud.exception.CloudExecutionException"
+
+4300 : "com.cloud.exception.ConcurrentOperationException"
+
+4305 : "com.cloud.exception.ConflictingNetworkSettingsException"
+
+4310 : "com.cloud.exception.DiscoveredWithErrorException"
+
+4315 : "com.cloud.exception.HAStateException"
+
+4320 : "com.cloud.exception.InsufficientAddressCapacityException"
+
+4325 : "com.cloud.exception.InsufficientCapacityException"
+
+4330 : "com.cloud.exception.InsufficientNetworkCapacityException"
+
+4335 : "com.cloud.exception.InsufficientServerCapacityException"
+
+4340 : "com.cloud.exception.InsufficientStorageCapacityException"
+
+4345 : "com.cloud.exception.InternalErrorException"
+
+4350 : "com.cloud.exception.InvalidParameterValueException"
+
+4355 : "com.cloud.exception.ManagementServerException"
+
+4360 : "com.cloud.exception.NetworkRuleConflictException"
+
+4365 : "com.cloud.exception.PermissionDeniedException"
+
+4370 : "com.cloud.exception.ResourceAllocationException"
+
+4375 : "com.cloud.exception.ResourceInUseException"
+
+4380 : "com.cloud.exception.ResourceUnavailableException"
+
+4385 : "com.cloud.exception.StorageUnavailableException"
+
+4390 : "com.cloud.exception.UnsupportedServiceException"
+
+4395 : "com.cloud.exception.VirtualMachineMigrationException"
+
+4400 : "com.cloud.exception.AccountLimitException"
+
+4405 : "com.cloud.exception.AgentUnavailableException"
+
+4410 : "com.cloud.exception.CloudAuthenticationException"
+
+4415 : "com.cloud.exception.CloudException"
+
+4420 : "com.cloud.exception.CloudExecutionException"
+
+4425 : "com.cloud.exception.ConcurrentOperationException"
+
+4430 : "com.cloud.exception.ConflictingNetworkSettingsException"
+
+4435 : "com.cloud.exception.ConnectionException"
+
+4440 : "com.cloud.exception.DiscoveredWithErrorException"
+
+4445 : "com.cloud.exception.DiscoveryException"
+
+4450 : "com.cloud.exception.HAStateException"
+
+4455 : "com.cloud.exception.InsufficientAddressCapacityException"
+
+4460 : "com.cloud.exception.InsufficientCapacityException"
+
+4465 : "com.cloud.exception.InsufficientNetworkCapacityException"
+
+4470 : "com.cloud.exception.InsufficientServerCapacityException"
+
+4475 : "com.cloud.exception.InsufficientStorageCapacityException"
+
+4480 : "com.cloud.exception.InsufficientVirtualNetworkCapcityException"
+
+4485 : "com.cloud.exception.InternalErrorException"
+
+4490 : "com.cloud.exception.InvalidParameterValueException"
+
+4495 : "com.cloud.exception.ManagementServerException"
+
+4500 : "com.cloud.exception.NetworkRuleConflictException"
+
+4505 : "com.cloud.exception.PermissionDeniedException"
+
+4510 : "com.cloud.exception.ResourceAllocationException"
+
+4515 : "com.cloud.exception.ResourceInUseException"
+
+4520 : "com.cloud.exception.ResourceUnavailableException"
+
+4525 : "com.cloud.exception.StorageUnavailableException"
+
+4530 : "com.cloud.exception.UnsupportedServiceException"
+
+4535 : "com.cloud.exception.VirtualMachineMigrationException"
+
+9999 : "org.apache.cloudstack.api.ServerApiException"
+
+An HTTP error code of 401 is always returned if API request was rejected
+due to bad signatures, missing API Keys, or the user simply did not have
+the permissions to execute the command.
+
+
+Asynchronous Commands
+~~~~~~~~~~~~~~~~~~~~~
+
+Asynchronous commands were introduced in CloudStack 2.x. Commands are
+designated as asynchronous when they can potentially take a long period
+of time to complete such as creating a snapshot or disk volume. They
+differ from synchronous commands by the following:
+
+- They are identified in the API Reference by an (A).
+
+- They will immediately return a job ID to refer to the job that will
+ be responsible in processing the command.
+
+- If executed as a "create" resource command, it will return the
+ resource ID as well as the job ID.
+
+ You can periodically check the status of the job by making a simple
+ API call to the command, `queryAsyncJobResult` and passing in the job
+ ID.
+
+
+Job Status
+~~~~~~~~~~
+
+The key to using an asynchronous command is the job ID that is returned
+immediately once the command has been executed. With the job ID, you can
+periodically check the job status by making calls to queryAsyncJobResult
+command. The command will return three possible job status integer
+values:
+
+- 0 - Job is still in progress. Continue to periodically poll for any
+ status changes.
+
+- 1 - Job has successfully completed. The job will return any
+ successful response values associated with command that was
+ originally executed.
+
+- 2 - Job has failed to complete. Please check the "jobresultcode" tag
+ for failure reason code and "jobresult" for the failure reason.
+
+
+Example
+~~~~~~~
+
+The following shows an example of using an asynchronous command. Assume
+the API command:
+
+.. parsed-literal::
+
+ command=deployVirtualMachine&zoneId=1&serviceOfferingId=1&diskOfferingId=1&templateId=1
+
+CloudStack will immediately return a job ID and any other additional
+data.
+
+.. parsed-literal::
+
+ <deployvirtualmachineresponse>
+ <jobid>1</jobid>
+ <id>100</id>
+ </deployvirtualmachineresponse>
+
+Using the job ID, you can periodically poll for the results by using the
+queryAsyncJobResult command.
+
+.. parsed-literal::
+
+ command=queryAsyncJobResult&jobId=1
+
+Three possible results could come from this query.
+
+Job is still pending:
+
+.. parsed-literal::
+
+ <queryasyncjobresult>
+ <jobid>1</jobid>
+ <jobstatus>0</jobstatus>
+ <jobprocstatus>1</jobprocstatus>
+ </queryasyncjobresult>
+
+Job has succeeded:
+
+.. parsed-literal::
+
+ <queryasyncjobresultresponse cloud-stack-version="3.0.1.6">
+ <jobid>1</jobid>
+ <jobstatus>1</jobstatus>
+ <jobprocstatus>0</jobprocstatus>
+ <jobresultcode>0</jobresultcode>
+ <jobresulttype>object</jobresulttype>
+ <jobresult>
+ <virtualmachine>
+ <id>450</id>
+ <name>i-2-450-VM</name>
+ <displayname>i-2-450-VM</displayname>
+ <account>admin</account>
+ <domainid>1</domainid>
+ <domain>ROOT</domain>
+ <created>2011-03-10T18:20:25-0800</created>
+ <state>Running</state>
+ <haenable>false</haenable>
+ <zoneid>1</zoneid>
+ <zonename>San Jose 1</zonename>
+ <hostid>2</hostid>
+ <hostname>905-13.sjc.lab.vmops.com</hostname>
+ <templateid>1</templateid>
+ <templatename>CentOS 5.3 64bit LAMP</templatename>
+ <templatedisplaytext>CentOS 5.3 64bit LAMP</templatedisplaytext>
+ <passwordenabled>false</passwordenabled>
+ <serviceofferingid>1</serviceofferingid>
+ <serviceofferingname>Small Instance</serviceofferingname>
+ <cpunumber>1</cpunumber>
+ <cpuspeed>500</cpuspeed>
+ <memory>512</memory>
+ <guestosid>12</guestosid>
+ <rootdeviceid>0</rootdeviceid>
+ <rootdevicetype>NetworkFilesystem</rootdevicetype>
+ <nic>
+ <id>561</id>
+ <networkid>205</networkid>
+ <netmask>255.255.255.0</netmask>
+ <gateway>10.1.1.1</gateway>
+ <ipaddress>10.1.1.225</ipaddress>
+ <isolationuri>vlan://295</isolationuri>
+ <broadcasturi>vlan://295</broadcasturi>
+ <traffictype>Guest</traffictype>
+ <type>Virtual</type>
+ <isdefault>true</isdefault>
+ </nic>
+ <hypervisor>XenServer</hypervisor>
+ </virtualmachine>
+ </jobresult>
+ </queryasyncjobresultresponse>
+
+Job has failed:
+
+.. parsed-literal::
+
+ <queryasyncjobresult>
+ <jobid>1</jobid>
+ <jobstatus>2</jobstatus>
+ <jobprocstatus>0</jobprocstatus>
+ <jobresultcode>551</jobresultcode>
+ <jobresulttype>text</jobresulttype>
+ <jobresult>Unable to deploy virtual machine id = 100 due to not enough capacity</jobresult>
+ </queryasyncjobresult>
+
+
+Event Types
+-----------
+
+.. cssclass:: table-striped table-bordered table-hover
+
++-------------------+--------------------------------------------------------+
+| Types | Events |
++===================+========================================================+
+| VM | VM.CREATE |
+| | |
+| | VM.DESTROY |
+| | |
+| | VM.START |
+| | |
+| | VM.STOP |
+| | |
+| | VM.REBOOT |
+| | |
+| | VM.UPDATE |
+| | |
+| | VM.UPGRADE |
+| | |
+| | VM.DYNAMIC.SCALE |
+| | |
+| | VM.RESETPASSWORD |
+| | |
+| | VM.RESETSSHKEY |
+| | |
+| | VM.MIGRATE |
+| | |
+| | VM.MOVE |
+| | |
+| | VM.RESTORE |
++-------------------+--------------------------------------------------------+
+| Domain Router | ROUTER.CREATE |
+| | |
+| | ROUTER.DESTROY |
+| | |
+| | ROUTER.START |
+| | |
+| | ROUTER.STOP |
+| | |
+| | ROUTER.REBOOT |
+| | |
+| | ROUTER.HA |
+| | |
+| | ROUTER.UPGRADE |
++-------------------+--------------------------------------------------------+
+| Console proxy | PROXY.CREATE |
+| | |
+| | PROXY.DESTROY |
+| | |
+| | PROXY.START |
+| | |
+| | PROXY.STOP |
+| | |
+| | PROXY.REBOOT |
+| | |
+| | PROXY.HA |
++-------------------+--------------------------------------------------------+
+| VNC Console | VNC.CONNECT |
+| Events | |
+| | VNC.DISCONNECT |
++-------------------+--------------------------------------------------------+
+| Network Events | NET.IPASSIGN |
+| | |
+| | NET.IPRELEASE |
+| | |
+| | PORTABLE.IPASSIGN |
+| | |
+| | PORTABLE.IPRELEASE |
+| | |
+| | NET.RULEADD |
+| | |
+| | NET.RULEDELETE |
+| | |
+| | NET.RULEMODIFY |
+| | |
+| | NETWORK.CREATE |
+| | |
+| | NETWORK.DELETE |
+| | |
+| | NETWORK.UPDATE |
+| | |
+| | FIREWALL.OPEN |
+| | |
+| | FIREWALL.CLOSE |
++-------------------+--------------------------------------------------------+
+| NIC Events | NIC.CREATE |
+| | |
+| | NIC.DELETE |
+| | |
+| | NIC.UPDATE |
+| | |
+| | NIC.DETAIL.ADD |
+| | |
+| | NIC.DETAIL.UPDATE |
+| | |
+| | NIC.DETAIL.REMOVE |
++-------------------+--------------------------------------------------------+
+| Load Balancers | LB.ASSIGN.TO.RULE |
+| | |
+| | LB.REMOVE.FROM.RULE |
+| | |
+| | LB.CREATE |
+| | |
+| | LB.DELETE |
+| | |
+| | LB.STICKINESSPOLICY.CREATE |
+| | |
+| | LB.STICKINESSPOLICY.DELETE |
+| | |
+| | LB.HEALTHCHECKPOLICY.CREATE |
+| | |
+| | LB.HEALTHCHECKPOLICY.DELETE |
+| | |
+| | LB.UPDATE |
++-------------------+--------------------------------------------------------+
+| Global Load | GLOBAL.LB.ASSIGN |
+| Balancer rules | |
+| | GLOBAL.LB.REMOVE |
+| | |
+| | GLOBAL.LB.CREATE |
+| | |
+| | GLOBAL.LB.DELETE |
+| | |
+| | GLOBAL.LB.UPDATE |
++-------------------+--------------------------------------------------------+
+| Account events | ACCOUNT.ENABLE |
+| | |
+| | ACCOUNT.DISABLE |
+| | |
+| | ACCOUNT.CREATE |
+| | |
+| | ACCOUNT.DELETE |
+| | |
+| | ACCOUNT.UPDATE |
+| | |
+| | ACCOUNT.MARK.DEFAULT.ZONE |
++-------------------+--------------------------------------------------------+
+| UserVO Events | USER.LOGIN |
+| | |
+| | USER.LOGOUT |
+| | |
+| | USER.CREATE |
+| | |
+| | USER.DELETE |
+| | |
+| | USER.DISABLE |
+| | |
+| | USER.UPDATE |
+| | |
+| | USER.ENABLE |
+| | |
+| | USER.LOCK |
++-------------------+--------------------------------------------------------+
+| Registering SSH | REGISTER.SSH.KEYPAIR |
+| keypair events | |
++-------------------+--------------------------------------------------------+
+| Register for user | REGISTER.USER.KEY |
+| API and secret | |
+| keys | |
++-------------------+--------------------------------------------------------+
+| Template Events | TEMPLATE.CREATE |
+| | |
+| | TEMPLATE.DELETE |
+| | |
+| | TEMPLATE.UPDATE |
+| | |
+| | TEMPLATE.DOWNLOAD.START |
+| | |
+| | TEMPLATE.DOWNLOAD.SUCCESS |
+| | |
+| | TEMPLATE.DOWNLOAD.FAILED |
+| | |
+| | TEMPLATE.COPY |
+| | |
+| | TEMPLATE.EXTRACT |
+| | |
+| | TEMPLATE.UPLOAD |
+| | |
+| | TEMPLATE.CLEANUP |
++-------------------+--------------------------------------------------------+
+| Volume Events | VOLUME.CREATE |
+| | |
+| | VOLUME.DELETE |
+| | |
+| | VOLUME.ATTACH |
+| | |
+| | VOLUME.DETACH |
+| | |
+| | VOLUME.EXTRACT |
+| | |
+| | VOLUME.UPLOAD |
+| | |
+| | VOLUME.MIGRATE |
+| | |
+| | VOLUME.RESIZE |
+| | |
+| | VOLUME.DETAIL.UPDATE |
+| | |
+| | VOLUME.DETAIL.ADD |
+| | |
+| | VOLUME.DETAIL.REMOVE |
++-------------------+--------------------------------------------------------+
+| Domains | DOMAIN.CREATE |
+| | |
+| | DOMAIN.DELETE |
+| | |
+| | DOMAIN.UPDATE |
++-------------------+--------------------------------------------------------+
+| Snapshots | SNAPSHOT.CREATE |
+| | |
+| | SNAPSHOT.DELETE |
+| | |
+| | SNAPSHOTPOLICY.CREATE |
+| | |
+| | SNAPSHOTPOLICY.UPDATE |
+| | |
+| | SNAPSHOTPOLICY.DELETE |
++-------------------+--------------------------------------------------------+
+| ISO | ISO.CREATE |
+| | |
+| | ISO.DELETE |
+| | |
+| | ISO.COPY |
+| | |
+| | ISO.ATTACH |
+| | |
+| | ISO.DETACH |
+| | |
+| | ISO.EXTRACT |
+| | |
+| | ISO.UPLOAD |
++-------------------+--------------------------------------------------------+
+| SSVM | SSVM.CREATE |
+| | |
+| | SSVM.DESTROY |
+| | |
+| | SSVM.START |
+| | |
+| | SSVM.STOP |
+| | |
+| | SSVM.REBOOT |
+| | |
+| | SSVM.HA |
++-------------------+--------------------------------------------------------+
+| Service Offerings | SERVICE.OFFERING.CREATE |
+| | |
+| | SERVICE.OFFERING.EDIT |
+| | |
+| | SERVICE.OFFERING.DELETE |
++-------------------+--------------------------------------------------------+
+| Disk Offerings | DISK.OFFERING.CREATE |
+| | |
+| | DISK.OFFERING.EDIT |
+| | |
+| | DISK.OFFERING.DELETE |
++-------------------+--------------------------------------------------------+
+| Network offerings | NETWORK.OFFERING.CREATE |
+| | |
+| | NETWORK.OFFERING.ASSIGN |
+| | |
+| | NETWORK.OFFERING.EDIT |
+| | |
+| | NETWORK.OFFERING.REMOVE |
+| | |
+| | NETWORK.OFFERING.DELETE |
++-------------------+--------------------------------------------------------+
+| Pods | POD.CREATE |
+| | |
+| | POD.EDIT |
+| | |
+| | POD.DELETE |
++-------------------+--------------------------------------------------------+
+| Zones | ZONE.CREATE |
+| | |
+| | ZONE.EDIT |
+| | |
+| | ZONE.DELETE |
++-------------------+--------------------------------------------------------+
+| VLANs/IP ranges | VLAN.IP.RANGE.CREATE |
+| | |
+| | VLAN.IP.RANGE.DELETE |
+| | |
+| | VLAN.IP.RANGE.DEDICATE |
+| | |
+| | VLAN.IP.RANGE.RELEASE |
+| | |
+| | STORAGE.IP.RANGE.CREATE |
+| | |
+| | STORAGE.IP.RANGE.DELETE |
+| | |
+| | STORAGE.IP.RANGE.UPDATE |
++-------------------+--------------------------------------------------------+
+| Configuration | CONFIGURATION.VALUE.EDIT |
+| Table | |
++-------------------+--------------------------------------------------------+
+| Security Groups | SG.AUTH.INGRESS |
+| | |
+| | SG.REVOKE.INGRESS |
+| | |
+| | SG.AUTH.EGRESS |
+| | |
+| | SG.REVOKE.EGRESS |
+| | |
+| | SG.CREATE |
+| | |
+| | SG.DELETE |
+| | |
+| | SG.ASSIGN |
+| | |
+| | SG.REMOVE |
++-------------------+--------------------------------------------------------+
+| Host | HOST.RECONNECT |
++-------------------+--------------------------------------------------------+
+| Maintenance | MAINT.CANCEL |
+| | |
+| | MAINT.CANCEL.PS |
+| | |
+| | MAINT.PREPARE |
+| | |
+| | MAINT.PREPARE.PS |
++-------------------+--------------------------------------------------------+
+| VPN | VPN.REMOTE.ACCESS.CREATE |
+| | |
+| | VPN.REMOTE.ACCESS.DESTROY |
+| | |
+| | VPN.USER.ADD |
+| | |
+| | VPN.USER.REMOVE |
+| | |
+| | VPN.S2S.VPN.GATEWAY.CREATE |
+| | |
+| | VPN.S2S.VPN.GATEWAY.DELETE |
+| | |
+| | VPN.S2S.CUSTOMER.GATEWAY.CREATE |
+| | |
+| | VPN.S2S.CUSTOMER.GATEWAY.DELETE |
+| | |
+| | VPN.S2S.CUSTOMER.GATEWAY.UPDATE |
+| | |
+| | VPN.S2S.CONNECTION.CREATE |
+| | |
+| | VPN.S2S.CONNECTION.DELETE |
+| | |
+| | VPN.S2S.CONNECTION.RESET |
++-------------------+--------------------------------------------------------+
+| Network | NETWORK.RESTART |
++-------------------+--------------------------------------------------------+
+| Custom | UPLOAD.CUSTOM.CERTIFICATE |
+| certificates | |
++-------------------+--------------------------------------------------------+
+| OneToOnenat | STATICNAT.ENABLE |
+| | |
+| | STATICNAT.DISABLE |
+| | |
+| | ZONE.VLAN.ASSIGN |
+| | |
+| | ZONE.VLAN.RELEASE |
++-------------------+--------------------------------------------------------+
+| Projects | PROJECT.CREATE |
+| | |
+| | PROJECT.UPDATE |
+| | |
+| | PROJECT.DELETE |
+| | |
+| | PROJECT.ACTIVATE |
+| | |
+| | PROJECT.SUSPEND |
+| | |
+| | PROJECT.ACCOUNT.ADD |
+| | |
+| | PROJECT.INVITATION.UPDATE |
+| | |
+| | PROJECT.INVITATION.REMOVE |
+| | |
+| | PROJECT.ACCOUNT.REMOVE |
++-------------------+--------------------------------------------------------+
+| Network as a | NETWORK.ELEMENT.CONFIGURE |
+| Service | |
++-------------------+--------------------------------------------------------+
+| Physical Network | PHYSICAL.NETWORK.CREATE |
+| Events | |
+| | PHYSICAL.NETWORK.DELETE |
+| | |
+| | PHYSICAL.NETWORK.UPDATE |
++-------------------+--------------------------------------------------------+
+| Physical Network | SERVICE.PROVIDER.CREATE |
+| Service Provider | |
+| Events | SERVICE.PROVIDER.DELETE |
+| | |
+| | SERVICE.PROVIDER.UPDATE |
++-------------------+--------------------------------------------------------+
+| Physical Network | TRAFFIC.TYPE.CREATE |
+| Traffic Type | |
+| Events | TRAFFIC.TYPE.DELETE |
+| | |
+| | TRAFFIC.TYPE.UPDATE |
++-------------------+--------------------------------------------------------+
+| External network | PHYSICAL.LOADBALANCER.ADD |
+| device events | |
+| | PHYSICAL.LOADBALANCER.DELETE |
+| | |
+| | PHYSICAL.LOADBALANCER.CONFIGURE |
++-------------------+--------------------------------------------------------+
+| External switch | SWITCH.MGMT.ADD |
+| management device | |
+| events | SWITCH.MGMT.DELETE |
+| | |
+| For example: | SWITCH.MGMT.CONFIGURE |
+| Cisco Nexus 1000v | |
+| Virtual | SWITCH.MGMT.ENABLE |
+| Supervisor | |
+| Module. | SWITCH.MGMT.DISABLE |
+| | |
+| | PHYSICAL.FIREWALL.ADD |
+| | |
+| | PHYSICAL.FIREWALL.DELETE |
+| | |
+| | PHYSICAL.FIREWALL.CONFIGURE |
++-------------------+--------------------------------------------------------+
+| VPC | VPC.CREATE |
+| | |
+| | VPC.UPDATE |
+| | |
+| | VPC.DELETE |
+| | |
+| | VPC.RESTART |
++-------------------+--------------------------------------------------------+
+| Network ACL | NETWORK.ACL.CREATE |
+| | |
+| | NETWORK.ACL.DELETE |
+| | |
+| | NETWORK.ACL.REPLACE |
+| | |
+| | NETWORK.ACL.ITEM.CREATE |
+| | |
+| | NETWORK.ACL.ITEM.UPDATE |
+| | |
+| | NETWORK.ACL.ITEM.DELETE |
++-------------------+--------------------------------------------------------+
+| VPC offerings | VPC.OFFERING.CREATE |
+| | |
+| | VPC.OFFERING.UPDATE |
+| | |
+| | VPC.OFFERING.DELETE |
++-------------------+--------------------------------------------------------+
+| Private gateway | PRIVATE.GATEWAY.CREATE |
+| | |
+| | PRIVATE.GATEWAY.DELETE |
++-------------------+--------------------------------------------------------+
+| Static routes | STATIC.ROUTE.CREATE |
+| | |
+| | STATIC.ROUTE.DELETE |
++-------------------+--------------------------------------------------------+
+| Tag-related | CREATE\_TAGS |
+| events | |
+| | DELETE\_TAGS |
++-------------------+--------------------------------------------------------+
+| Meta data-related | CREATE\_RESOURCE\_DETAILS |
+| events | |
+| | DELETE\_RESOURCE\_DETAILS |
++-------------------+--------------------------------------------------------+
+| VM snapshot | VMSNAPSHOT.CREATE |
+| events | |
+| | VMSNAPSHOT.DELETE |
+| | |
+| | VMSNAPSHOT.REVERTTO |
++-------------------+--------------------------------------------------------+
+| External network | PHYSICAL.NVPCONTROLLER.ADD |
+| device events | |
+| | PHYSICAL.NVPCONTROLLER.DELETE |
+| | |
+| | PHYSICAL.NVPCONTROLLER.CONFIGURE |
++-------------------+--------------------------------------------------------+
+| AutoScale | COUNTER.CREATE |
+| | |
+| | COUNTER.DELETE |
+| | |
+| | CONDITION.CREATE |
+| | |
+| | CONDITION.DELETE |
+| | |
+| | AUTOSCALEPOLICY.CREATE |
+| | |
+| | AUTOSCALEPOLICY.UPDATE |
+| | |
+| | AUTOSCALEPOLICY.DELETE |
+| | |
+| | AUTOSCALEVMPROFILE.CREATE |
+| | |
+| | AUTOSCALEVMPROFILE.DELETE |
+| | |
+| | AUTOSCALEVMPROFILE.UPDATE |
+| | |
+| | AUTOSCALEVMGROUP.CREATE |
+| | |
+| | AUTOSCALEVMGROUP.DELETE |
+| | |
+| | AUTOSCALEVMGROUP.UPDATE |
+| | |
+| | AUTOSCALEVMGROUP.ENABLE |
+| | |
+| | AUTOSCALEVMGROUP.DISABLE |
+| | |
+| | PHYSICAL.DHCP.ADD |
+| | |
+| | PHYSICAL.DHCP.DELETE |
+| | |
+| | PHYSICAL.PXE.ADD |
+| | |
+| | PHYSICAL.PXE.DELETE |
+| | |
+| | AG.CREATE |
+| | |
+| | AG.DELETE |
+| | |
+| | AG.ASSIGN |
+| | |
+| | AG.REMOVE |
+| | |
+| | VM.AG.UPDATE |
+| | |
+| | INTERNALLBVM.START |
+| | |
+| | INTERNALLBVM.STOP |
+| | |
+| | HOST.RESERVATION.RELEASE |
++-------------------+--------------------------------------------------------+
+| Dedicated guest | GUESTVLANRANGE.DEDICATE |
+| vlan range | |
+| | GUESTVLANRANGE.RELEASE |
+| | |
+| | PORTABLE.IP.RANGE.CREATE |
+| | |
+| | PORTABLE.IP.RANGE.DELETE |
+| | |
+| | PORTABLE.IP.TRANSFER |
++-------------------+--------------------------------------------------------+
+| Dedicated | DEDICATE.RESOURCE |
+| Resources | |
+| | DEDICATE.RESOURCE.RELEASE |
+| | |
+| | VM.RESERVATION.CLEANUP |
+| | |
+| | UCS.ASSOCIATEPROFILE |
+| | |
+| | UCS.DISASSOCIATEPROFILE |
++-------------------+--------------------------------------------------------+
+
+.. _time-zones:
+
+Time Zones
+----------
+
+The following time zone identifiers are accepted by PRODUCT. There are
+several places that have a time zone as a required or optional
+parameter. These include scheduling recurring snapshots, creating a
+user, and specifying the usage time zone in the Configuration table.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++-----------------------------------+-----------------------+------------------------+
+| Etc/GMT+12 | Etc/GMT+11 | Pacific/Samoa |
++-----------------------------------+-----------------------+------------------------+
+| Pacific/Honolulu | US/Alaska | America/Los\_Angeles |
++-----------------------------------+-----------------------+------------------------+
+| Mexico/BajaNorte | US/Arizona | US/Mountain |
++-----------------------------------+-----------------------+------------------------+
+| America/Chihuahua | America/Chicago | America/Costa\_Rica |
++-----------------------------------+-----------------------+------------------------+
+| America/Mexico\_City | Canada/Saskatchewan | America/Bogota |
++-----------------------------------+-----------------------+------------------------+
+| America/New\_York | America/Caracas | America/Asuncion |
++-----------------------------------+-----------------------+------------------------+
+| America/Cuiaba | America/Halifax | America/La\_Paz |
++-----------------------------------+-----------------------+------------------------+
+| America/Santiago | America/St\_Johns | America/Araguaina |
++-----------------------------------+-----------------------+------------------------+
+| America/Argentina/Buenos\_Aires | America/Cayenne | America/Godthab |
++-----------------------------------+-----------------------+------------------------+
+| America/Montevideo | Etc/GMT+2 | Atlantic/Azores |
++-----------------------------------+-----------------------+------------------------+
+| Atlantic/Cape\_Verde | Africa/Casablanca | Etc/UTC |
++-----------------------------------+-----------------------+------------------------+
+| Atlantic/Reykjavik | Europe/London | CET |
++-----------------------------------+-----------------------+------------------------+
+| Europe/Bucharest | Africa/Johannesburg | Asia/Beirut |
++-----------------------------------+-----------------------+------------------------+
+| Africa/Cairo | Asia/Jerusalem | Europe/Minsk |
++-----------------------------------+-----------------------+------------------------+
+| Europe/Moscow | Africa/Nairobi | Asia/Karachi |
++-----------------------------------+-----------------------+------------------------+
+| Asia/Kolkata | Asia/Bangkok | Asia/Shanghai |
++-----------------------------------+-----------------------+------------------------+
+| Asia/Kuala\_Lumpur | Australia/Perth | Asia/Taipei |
++-----------------------------------+-----------------------+------------------------+
+| Asia/Tokyo | Asia/Seoul | Australia/Adelaide |
++-----------------------------------+-----------------------+------------------------+
+| Australia/Darwin | Australia/Brisbane | Australia/Canberra |
++-----------------------------------+-----------------------+------------------------+
+| Pacific/Guam | Pacific/Auckland | |
++-----------------------------------+-----------------------+------------------------+
diff --git a/source/developersguide/developer_guide.rst b/source/developersguide/developer_guide.rst
new file mode 100644
index 0000000..78cef01
--- /dev/null
+++ b/source/developersguide/developer_guide.rst
@@ -0,0 +1,703 @@
+.. 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 Installation from GIT repo for Developers
+====================================================
+
+This book is aimed at CloudStack developers who need to build the code.
+These instructions are valid on a Ubuntu 12.04 and CentOS 6.4 systems
+and were tested with the 4.2 release of Apache CloudStack, please adapt
+them if you are on a different operating system or using a newer/older
+version of CloudStack. This book is composed of the following sections:
+
+#. Installation of the prerequisites
+
+#. Compiling and installation from source
+
+#. Using the CloudStack simulator
+
+#. Installation with DevCloud the CloudStack sandbox
+
+#. Building your own packages
+
+#. The CloudStack API
+
+#. Testing the AWS API interface
+
+
+Prerequisites
+-------------
+
+In this section we'll look at installing the dependencies you'll need
+for Apache CloudStack development.
+
+
+On Ubuntu 12.04
+~~~~~~~~~~~~~~~
+
+First update and upgrade your system:
+
+::
+
+ apt-get update
+ apt-get upgrade
+
+NTP might already be installed, check it with ``service ntp status``. If
+it's not then install NTP to synchronize the clocks:
+
+::
+
+ apt-get install openntpd
+
+Install ``openjdk``. As we're using Linux, OpenJDK is our first choice.
+
+::
+
+ apt-get install openjdk-7-jdk
+
+Install ``tomcat6``, note that the new version of tomcat on
+`Ubuntu <http://packages.ubuntu.com/precise/all/tomcat6>`__ is the
+6.0.35 version.
+
+::
+
+ apt-get install tomcat6
+
+Next, we'll install MySQL if it's not already present on the system.
+
+::
+
+ apt-get install mysql-server
+
+Remember to set the correct ``mysql`` password in the CloudStack
+properties file. Mysql should be running but you can check it's status
+with:
+
+::
+
+ service mysql status
+
+Developers wanting to build CloudStack from source will want to install
+the following additional packages. If you dont' want to build from
+source just jump to the next section.
+
+Install ``git`` to later clone the CloudStack source code:
+
+::
+
+ apt-get install git
+
+Install ``Maven`` to later build CloudStack
+
+::
+
+ apt-get install maven
+
+This should have installed Maven 3.0, check the version number with
+``mvn --version``
+
+A little bit of Python can be used (e.g simulator), install the Python
+package management tools:
+
+::
+
+ apt-get install python-pip python-setuptools
+
+Finally install ``mkisofs`` with:
+
+::
+
+ apt-get install genisoimage
+
+
+On CentOS 6.4
+~~~~~~~~~~~~~
+
+First update and upgrade your system:
+
+::
+
+ yum -y update
+ yum -y upgrade
+
+If not already installed, install NTP for clock synchornization
+
+::
+
+ yum -y install ntp
+
+Install ``openjdk``. As we're using Linux, OpenJDK is our first choice.
+
+::
+
+ yum -y install java-1.7.0-openjdk-devel
+
+Install ``tomcat6``, note that the version of tomcat6 in the default
+CentOS 6.4 repo is 6.0.24, so we will grab the 6.0.35 version. The
+6.0.24 version will be installed anyway as a dependency to cloudstack.
+
+::
+
+ wget https://archive.apache.org/dist/tomcat/tomcat-6/v6.0.35/bin/apache-tomcat-6.0.35.tar.gz
+ tar xzvf apache-tomcat-6.0.35.tar.gz -C /usr/local
+
+Setup tomcat6 system wide by creating a file
+``/etc/profile.d/tomcat.sh`` with the following content:
+
+::
+
+ export CATALINA_BASE=/usr/local/apache-tomcat-6.0.35
+ export CATALINA_HOME=/usr/local/apache-tomcat-6.0.35
+
+Next, we'll install MySQL if it's not already present on the system.
+
+::
+
+ yum -y install mysql mysql-server
+
+Remember to set the correct ``mysql`` password in the CloudStack
+properties file. Mysql should be running but you can check it's status
+with:
+
+::
+
+ service mysqld status
+
+Install ``git`` to later clone the CloudStack source code:
+
+::
+
+ yum -y install git
+
+Install ``Maven`` to later build CloudStack. Grab the 3.0.5 release from
+the Maven `website <http://maven.apache.org/download.cgi>`__
+
+::
+
+ wget http://mirror.cc.columbia.edu/pub/software/apache/maven/maven-3/3.0.5/binaries/apache-maven-3.0.5-bin.tar.gz
+ tar xzf apache-maven-3.0.5-bin.tar.gz -C /usr/local
+ cd /usr/local
+ ln -s apache-maven-3.0.5 maven
+
+Setup Maven system wide by creating a ``/etc/profile.d/maven.sh`` file
+with the following content:
+
+::
+
+ export M2_HOME=/usr/local/maven
+ export PATH=${M2_HOME}/bin:${PATH}
+
+Log out and log in again and you will have maven in your PATH:
+
+::
+
+ mvn --version
+
+This should have installed Maven 3.0, check the version number with
+``mvn --version``
+
+A little bit of Python can be used (e.g simulator), install the Python
+package management tools:
+
+::
+
+ yum -y install python-setuptools
+
+To install python-pip you might want to setup the Extra Packages for
+Enterprise Linux (EPEL) repo
+
+::
+
+ cd /tmp
+ wget http://mirror-fpt-telecom.fpt.net/fedora/epel/6/i386/epel-release-6-8.noarch.rpm
+ rpm -ivh epel-release-6-8.noarch.rpm
+
+Then update you repository cache ``yum update`` and install pip
+``yum -y install python-pip``
+
+Finally install ``mkisofs`` with:
+
+::
+
+ yum -y install genisoimage
+
+
+Installing from Source
+----------------------
+
+CloudStack uses git for source version control, if you know little about
+`git <http://book.git-scm.com/>`__ is a good start. Once you have git
+setup on your machine, pull the source with:
+
+::
+
+ git clone https://git-wip-us.apache.org/repos/asf/cloudstack.git
+
+To build the latest stable release:
+
+::
+
+ git checkout 4.8
+
+To compile Apache CloudStack, go to the cloudstack source folder and
+run:
+
+::
+
+ mvn -Pdeveloper,systemvm clean install
+
+If you want to skip the tests add ``-DskipTests`` to the command above.
+Do NOT use ``-Dmaven.test.skip=true`` because that will break the build.
+
+You will have made sure to set the proper db password in
+``utils/conf/db.properties``
+
+Deploy the database next:
+
+::
+
+ mvn -P developer -pl developer -Ddeploydb
+
+Run Apache CloudStack with jetty for testing. Note that ``tomcat`` maybe
+be running on port 8080, stop it before you use ``jetty``
+
+::
+
+ mvn -pl :cloud-client-ui jetty:run
+
+Log Into Apache CloudStack:
+
+Open your Web browser and use this URL to connect to CloudStack:
+
+::
+
+ http://localhost:8080/client/
+
+Replace ``localhost`` with the IP of your management server if need be.
+
+.. note::
+ If you have iptables enabled, you may have to open the ports used by
+ CloudStack. Specifically, ports 8080, 8250, and 9090.
+
+You can now start configuring a Zone, playing with the API. Of course we
+did not setup any infrastructure, there is no storage, no
+hypervisors...etc. However you can run tests using the simulator. The
+following section shows you how to use the simulator so that you don't
+have to setup a physical infrastructure.
+
+
+Using the Simulator
+-------------------
+
+CloudStack comes with a simulator based on Python bindings called
+*Marvin*. Marvin is available in the CloudStack source code or on Pypi.
+With Marvin you can simulate your data center infrastructure by
+providing CloudStack with a configuration file that defines the number
+of zones/pods/clusters/hosts, types of storage etc. You can then develop
+and test the CloudStack management server *as if* it was managing your
+production infrastructure.
+
+Do a clean build:
+
+::
+
+ mvn -Pdeveloper -Dsimulator -DskipTests clean install
+
+Deploy the database:
+
+::
+
+ mvn -Pdeveloper -pl developer -Ddeploydb
+ mvn -Pdeveloper -pl developer -Ddeploydb-simulator
+
+Install marvin. Note that you will need to have installed ``pip``
+properly in the prerequisites step.
+
+::
+
+ pip install tools/marvin/dist/Marvin-|release|.tar.gz
+
+Stop jetty (from any previous runs)
+
+::
+
+ mvn -pl :cloud-client-ui jetty:stop
+
+Start jetty
+
+::
+
+ mvn -pl client jetty:run
+
+Setup a basic zone with Marvin. In a separate shell://
+
+::
+
+ mvn -Pdeveloper,marvin.setup -Dmarvin.config=setup/dev/basic.cfg -pl :cloud-marvin integration-test
+
+At this stage log in the CloudStack management server at
+http://localhost:8080/client with the credentials admin/password, you
+should see a fully configured basic zone infrastructure. To simulate an
+advanced zone replace ``basic.cfg`` with ``advanced.cfg``.
+
+You can now run integration tests, use the API etc...
+
+
+Using DevCloud
+--------------
+
+The Installing from source section will only get you to the point of
+runnign the management server, it does not get you any hypervisors. The
+simulator section gets you a simulated datacenter for testing. With
+DevCloud you can run at least one hypervisor and add it to your
+management server the way you would a real physical machine.
+
+`DevCloud <https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud>`__
+is the CloudStack sandbox, the standard version is a VirtualBox based
+image. There is also a KVM based image for it. Here we only show steps
+with the VirtualBox image. For KVM see the
+`wiki <https://cwiki.apache.org/confluence/display/CLOUDSTACK/devcloud-kvm>`__.
+
+\*\* DevCloud Pre-requisites
+
+#. Install `VirtualBox <http://www.virtualbox.org>`__ on your machine
+
+#. Run VirtualBox and under >Preferences create a *host-only interface*
+ on which you disable the DHCP server
+
+#. Download the DevCloud `image
+ <http://people.apache.org/~bhaisaab/cloudstack/devcloud/devcloud2.ova>`__
+
+#. In VirtualBox, under File > Import Appliance import the DevCloud
+ image.
+
+#. Verify the settings under > Settings and check the ``enable PAE``
+ option in the processor menu
+
+#. Once the VM has booted try to ``ssh`` to it with credentials:
+ ``root/password``
+
+ ssh root@192.168.56.10
+
+
+Adding DevCloud as an Hypervisor
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Picking up from a clean build:
+
+::
+
+ mvn -Pdeveloper,systemvm clean install
+ mvn -P developer -pl developer,tools/devcloud -Ddeploydb
+
+At this stage install marvin similarly than with the simulator:
+
+::
+
+ pip install tools/marvin/dist/Marvin-|release|.tar.gz
+
+Start the management server
+
+::
+
+ mvn -pl client jetty:run
+
+Then you are going to configure CloudStack to use the running DevCloud
+instance:
+
+::
+
+ cd tools/devcloud
+ python ../marvin/marvin/deployDataCenter.py -i devcloud.cfg
+
+If you are curious, check the ``devcloud.cfg`` file and see how the data
+center is defined: 1 Zone, 1 Pod, 1 Cluster, 1 Host, 1 primary Storage,
+1 Seondary Storage, all provided by Devcloud.
+
+You can now log in the management server at
+``http://localhost:8080/client`` and start experimenting with the UI or
+the API.
+
+Do note that the management server is running in your local machine and
+that DevCloud is used only as a n Hypervisor. You could potentially run
+the management server within DevCloud as well, or memory granted, run
+multiple DevClouds.
+
+
+Building Packages
+-----------------
+
+Working from source is necessary when developing CloudStack. As
+mentioned earlier this is not primarily intended for users. However some
+may want to modify the code for their own use and specific
+infrastructure. The may also need to build their own packages for
+security reasons and due to network connectivity constraints. This
+section shows you the gist of how to build packages. We assume that the
+reader will know how to create a repository to serve this packages. The
+complete documentation is available in the :ref:`building_deb_packages` section.
+
+To build debian packages you will need couple extra packages that we did
+not need to install for source compilation:
+
+::
+
+ apt-get install python-mysqldb
+ apt-get install debhelper
+
+Then build the packages with:
+
+::
+
+ dpkg-buildpackage -uc -us
+
+One directory up from the CloudStack root dir you will find:
+
+::
+
+ cloudstack_|release|_amd64.changes
+ cloudstack_|release|.dsc
+ cloudstack_|release|.tar.gz
+ cloudstack-agent_|release|_all.deb
+ cloudstack-awsapi_|release|_all.deb
+ cloudstack-cli_|release|_all.deb
+ cloudstack-common_|release|_all.deb
+ cloudstack-docs_|release|_all.deb
+ cloudstack-management_|release|_all.deb
+ cloudstack-usage_|release|_all.deb
+
+Of course the community provides a repository for these packages and you
+can use it instead of building your own packages and putting them in
+your own repo. Instructions on how to use this community repository are
+available in the installation book.
+
+.. _the-api:
+
+The CloudStack API
+------------------
+
+The CloudStack API is a query based API using http that return results
+in XML or JSON. It is used to implement the default web UI. This API is
+not a standard like `OGF
+OCCI <http://www.ogf.org/gf/group_info/view.php?group=occi-wg>`__ or
+`DMTF CIMI <http://dmtf.org/standards/cloud>`__ but is easy to learn.
+Mapping exists between the AWS API and the CloudStack API as will be
+seen in the next section. Recently a Google Compute Engine interface was
+also developed that maps the GCE REST API to the CloudStack API
+described here. The API
+`docs <http://cloudstack.apache.org/docs/api/>`__ are a good start to
+learn the extent of the API. Multiple clients exist on
+`github <https://github.com/search?q=cloudstack+client&ref=cmdform>`__
+to use this API, you should be able to find one in your favorite
+language. The reference documentation for the API and changes that might
+occur from version to version is availble
+`on-line <http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.1/html/Developers_Guide/index.html>`__.
+This short section is aimed at providing a quick summary to give you a
+base understanding of how to use this API. As a quick start, a good way
+to explore the API is to navigate the dashboard with a firebug console
+(or similar developer console) to study the queries.
+
+In a succint statement, the CloudStack query API can be used via http
+GET requests made against your cloud endpoint (e.g
+http://localhost:8080/client/api). The API name is passed using the
+``command`` key and the various parameters for this API call are passed
+as key value pairs. The request is signed using the access key and
+secret key of the user making the call. Some calls are synchronous while
+some are asynchronous, this is documented in the API
+`docs <http://cloudstack.apache.org/docs/api/>`__. Asynchronous calls
+return a ``jobid``, the status and result of a job can be queried with
+the ``queryAsyncJobResult`` call. Let's get started and give an example
+of calling the ``listUsers`` API in Python.
+
+First you will need to generate keys to make requests. Going through the
+dashboard, go under ``Accounts`` select the appropriate account then
+click on ``Show Users`` select the intended users and generate keys
+using the ``Generate Keys`` icon. You will see an ``API Key`` and
+``Secret Key`` field being generated. The keys will be of the form:
+
+::
+
+ API Key : XzAz0uC0t888gOzPs3HchY72qwDc7pUPIO8LxC-VkIHo4C3fvbEBY_Ccj8fo3mBapN5qRDg_0_EbGdbxi8oy1A
+ Secret Key: zmBOXAXPlfb-LIygOxUVblAbz7E47eukDS_0JYUxP3JAmknOYo56T0R-AcM7rK7SMyo11Y6XW22gyuXzOdiybQ
+
+Open a Python shell and import the basic modules necessary to make the
+request. Do note that this request could be made many different ways,
+this is just a low level example. The ``urllib*`` modules are used to
+make the http request and do url encoding. The ``hashlib`` module gives
+us the sha1 hash function. It used to geenrate the ``hmac`` (Keyed
+Hashing for Message Authentication) using the secretkey. The result is
+encoded using the ``base64`` module.
+
+::
+
+ $python
+ Python 2.7.3 (default, Nov 17 2012, 19:54:34)
+ [GCC 4.2.1 Compatible Apple Clang 4.1 ((tags/Apple/clang-421.11.66))] on darwin
+ Type "help", "copyright", "credits" or "license" for more information.
+ >>> import urllib2
+ >>> import urllib
+ >>> import hashlib
+ >>> import hmac
+ >>> import base64
+
+Define the endpoint of the Cloud, the command that you want to execute,
+the type of the response (i.e XML or JSON) and the keys of the user.
+Note that we do not put the secretkey in our request dictionary because
+it is only used to compute the hmac.
+
+::
+
+ >>> baseurl='http://localhost:8080/client/api?'
+ >>> request={}
+ >>> request['command']='listUsers'
+ >>> request['response']='json'
+ >>> request['apikey']='plgWJfZK4gyS3mOMTVmjUVg-X-jlWlnfaUJ9GAbBbf9EdM-kAYMmAiLqzzq1ElZLYq_u38zCm0bewzGUdP66mg'
+ >>> secretkey='VDaACYb0LV9eNjTetIOElcVQkvJck_J_QljX_FcHRj87ZKiy0z0ty0ZsYBkoXkY9b7eq1EhwJaw7FF3akA3KBQ'
+
+Build the base request string, the combination of all the key/pairs of
+the request, url encoded and joined with ampersand.
+
+::
+
+ >>> request_str='&'.join(['='.join([k,urllib.quote_plus(request[k])]) for k in request.keys()])
+ >>> request_str
+ 'apikey=plgWJfZK4gyS3mOMTVmjUVg-X-jlWlnfaUJ9GAbBbf9EdM-kAYMmAiLqzzq1ElZLYq_u38zCm0bewzGUdP66mg&command=listUsers&response=json'
+
+Compute the signature with hmac, do a 64 bit encoding and a url
+encoding, the string used for the signature is similar to the base
+request string shown above but the keys/values are lower cased and
+joined in a sorted order
+
+::
+
+ >>> sig_str='&'.join(['='.join([k.lower(),urllib.quote_plus(request[k].lower().replace('+','%20'))])for k in sorted(request.iterkeys())])
+ >>> sig_str
+ 'apikey=plgwjfzk4gys3momtvmjuvg-x-jlwlnfauj9gabbbf9edm-kaymmailqzzq1elzlyq_u38zcm0bewzgudp66mg&command=listusers&response=json'
+ >>> sig=hmac.new(secretkey,sig_str,hashlib.sha1).digest()
+ >>> sig
+ 'M:]\x0e\xaf\xfb\x8f\xf2y\xf1p\x91\x1e\x89\x8a\xa1\x05\xc4A\xdb'
+ >>> sig=base64.encodestring(hmac.new(secretkey,sig_str,hashlib.sha1).digest())
+ >>> sig
+ 'TTpdDq/7j/J58XCRHomKoQXEQds=\n'
+ >>> sig=base64.encodestring(hmac.new(secretkey,sig_str,hashlib.sha1).digest()).strip()
+ >>> sig
+ 'TTpdDq/7j/J58XCRHomKoQXEQds='
+ >>> sig=urllib.quote_plus(base64.encodestring(hmac.new(secretkey,sig_str,hashlib.sha1).digest()).strip())
+
+Finally, build the entire string by joining the baseurl, the request str
+and the signature. Then do an http GET:
+
+::
+
+ >>> req=baseurl+request_str+'&signature='+sig
+ >>> req
+ 'http://localhost:8080/client/api?apikey=plgWJfZK4gyS3mOMTVmjUVg-X-jlWlnfaUJ9GAbBbf9EdM-kAYMmAiLqzzq1ElZLYq_u38zCm0bewzGUdP66mg&command=listUsers&response=json&signature=TTpdDq%2F7j%2FJ58XCRHomKoQXEQds%3D'
+ >>> res=urllib2.urlopen(req)
+ >>> res.read()
+ {
+ "listusersresponse" : {
+ "count":1 ,
+ "user" : [
+ {
+ "id":"7ed6d5da-93b2-4545-a502-23d20b48ef2a",
+ "username":"admin",
+ "firstname":"admin",
+ "lastname":"cloud",
+ "created":"2012-07-05T12:18:27-0700",
+ "state":"enabled",
+ "account":"admin",
+ "accounttype":1,
+ "domainid":"8a111e58-e155-4482-93ce-84efff3c7c77",
+ "domain":"ROOT",
+ "apikey":"plgWJfZK4gyS3mOMTVmjUVg-X-jlWlnfaUJ9GAbBbf9EdM-kAYMmAiLqzzq1ElZLYq_u38zCm0bewzGUdP66mg",
+ "secretkey":"VDaACYb0LV9eNjTetIOElcVQkvJck_J_QljX_FcHRj87ZKiy0z0ty0ZsYBkoXkY9b7eq1EhwJaw7FF3akA3KBQ",
+ "accountid":"7548ac03-af1d-4c1c-9064-2f3e2c0eda0d"
+ }
+ ]
+ }
+ }
+
+
+All the clients that you will find on github will implement this
+signature technique, you should not have to do it by hand. Now that you
+have explored the API through the UI and that you understand how to make
+low level calls, pick your favorite client of use
+`CloudMonkey <https://pypi.python.org/pypi/cloudmonkey/>`__. CloudMonkey
+is a sub-project of Apache CloudStack and gives operators/developers the
+ability to use any of the API methods. It has nice auto-completion and
+help feature as well as an API discovery mechanism since 4.2.
+
+
+Testing the AWS API interface
+-----------------------------
+
+While the native CloudStack API is not a standard, CloudStack provides a
+AWS EC2 compatible interface. It has the great advantage that existing
+tools written with EC2 libraries can be re-used against a CloudStack
+based cloud. In the installation books we described how to run this
+interface from installing packages. In this section we show you how to
+compile the interface with ``maven`` and test it with Python boto
+module.
+
+Starting from a running management server (with DevCloud for instance),
+start the AWS API interface in a separate shell with:
+
+::
+
+ mvn -Pawsapi -pl :cloud-awsapi jetty:run
+
+Log into the CloudStack UI ``http://localhost:8080/client``, go to
+*Service Offerings* and edit one of the compute offerings to have the
+name ``m1.small`` or any of the other AWS EC2 instance types.
+
+With access and secret keys generated for a user you should now be able
+to use Python `Boto <http://docs.pythonboto.org/en/latest/>`__ module:
+
+::
+
+ import boto
+ import boto.ec2
+
+ accesskey="2IUSA5xylbsPSnBQFoWXKg3RvjHgsufcKhC1SeiCbeEc0obKwUlwJamB_gFmMJkFHYHTIafpUx0pHcfLvt-dzw"
+ secretkey="oxV5Dhhk5ufNowey7OVHgWxCBVS4deTl9qL0EqMthfPBuy3ScHPo2fifDxw1aXeL5cyH10hnLOKjyKphcXGeDA"
+
+ region = boto.ec2.regioninfo.RegionInfo(name="ROOT", endpoint="localhost")
+ conn = boto.connect_ec2(aws_access_key_id=accesskey, aws_secret_access_key=secretkey, is_secure=False, region=region, port=7080, path="/awsapi", api_version="2012-08-15")
+
+ images=conn.get_all_images()
+ print images
+
+ res = images[0].run(instance_type='m1.small',security_groups=['default'])
+
+Note the new ``api_version`` number in the connection object and also
+note that there was no user registration to make like in previous
+CloudStack releases.
+
+
+Conclusions
+-----------
+
+CloudStack is a mostly Java application running with Tomcat and Mysql.
+It consists of a management server and depending on the hypervisors
+being used, an agent installed on the hypervisor farm. To complete a
+Cloud infrastructure however you will also need some Zone wide storage
+a.k.a Secondary Storage and some Cluster wide storage a.k.a Primary
+storage. The choice of hypervisor, storage solution and type of Zone
+(i.e Basic vs. Advanced) will dictate how complex your installation can
+be. As a quick start, you might want to consider KVM+NFS and a Basic
+Zone.
+
+If you've run into any problems with this, please ask on the
+cloudstack-dev `mailing list </mailing-lists.html>`__.
diff --git a/source/developersguide/get_help.rst b/source/developersguide/get_help.rst
new file mode 100644
index 0000000..e10d2e5
--- /dev/null
+++ b/source/developersguide/get_help.rst
@@ -0,0 +1,78 @@
+.. 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.
+
+
+Getting Help
+============
+
+Need some help getting started? Feel free to ask on the `mailing list
+<http://cloudstack.apache.org/mailing-lists.html>`_:
+
+- `users@ <http://mail-archives.apache.org/mod_mbox/cloudstack-users/>`_: This
+ list is for users of CloudStack to seek and provide support. This is a
+ moderately high volume list.
+- `dev@ <http://mail-archives.apache.org/mod_mbox/cloudstack-dev/>`_: Where
+ discussions about development and the project itself happen. This is a high
+ volume list.
+
+
+Or on one of the following IRC channels on irc.freenode.net:
+
+- #cloudstack - General Apache CloudStack conversation and end user support
+- #cloudstack-dev - Development discussions
+- #cloudstack-meeting - Weekly and ad-hoc meeting room for the Apache CloudStack community
+
+
+Documentation Available
+-----------------------
+
+The following guides are available:
+
+- CloudStack Concepts and Terminology
+- Quick Installation Guide
+- Installation Guide
+- Upgradong CloudStack
+- Usage Guide
+- Developers Guide
+- Plugins Guide
+- Release Notes
+
+All at |documentation_home|
+
+Books
+-----
+
+|60recipe| |acs-packt| |jp1| |jp2|
+
+
+Commercial support
+------------------
+
+Some companies offer commercial support for Apache CloudStack or their own
+product based on CloudStack.
+
+
+.. |60recipe| image:: /_static/images/60recipe.gif
+ :alt: O'Reilly 60 Recipes for Apache CloudStack
+ :target: http://shop.oreilly.com/product/0636920034377.do
+.. |acs-packt| image:: /_static/images/packt.png
+ :alt: Apache CloudStack Cloud Computing
+ :target: https://www.packtpub.com/virtualization-and-cloud/apache-cloudstack-cloud-computing
+.. |jp1| image:: /_static/images/jp1.jpg
+ :alt: CloudStack徹底入門 大型本
+ :target: http://www.amazon.co.jp/gp/product/4798130583/ref=as_li_ss_tl?ie=UTF8&camp=247&creative=7399&creativeASIN=4798130583&linkCode=as2&tag=aaaaaaaeaeaea-22
+.. |jp2| image:: /_static/images/jp2.jpg
+ :alt: CloudStack実践ガイド[前編]
+ :target: http://www.amazon.co.jp/CloudStack%E5%AE%9F%E8%B7%B5%E3%82%AC%E3%82%A4%E3%83%89-%E5%89%8D%E7%B7%A8-NextPublishing-%E5%A4%A7%E5%89%8A-%E7%B7%91/dp/4844395920/ref=pd_bxgy_b_img_y
\ No newline at end of file
diff --git a/source/developersguide/index.rst b/source/developersguide/index.rst
new file mode 100644
index 0000000..343dd44
--- /dev/null
+++ b/source/developersguide/index.rst
@@ -0,0 +1,38 @@
+.. 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 Installation Documentation master file, created by
+ sphinx-quickstart on Sat Jan 25 15:15:31 2014.
+ You can adapt this file completely to your liking, but it should at least
+ contain the root `toctree` directive.
+
+|menu_acs_logo|
+
+Developers Guide
+================
+
+
+This is the Apache CloudStack developers guide. This section gives information for those wishing to develop CloudStack either contributing to the CloudStack core software or writing external plugins. Futher information can also be found at CloudStack's wiki https://cwiki.apache.org/confluence/display/CLOUDSTACK/Home and on the CloudStack mailing lists http://cloudstack.apache.org/mailing-lists.html
+
+.. toctree::
+ :maxdepth: 2
+
+ developer_guide
+ dev
+ plugins
+ alloc
+ ansible
+ get_help
+
diff --git a/source/developersguide/plugins.rst b/source/developersguide/plugins.rst
new file mode 100644
index 0000000..7773bfe
--- /dev/null
+++ b/source/developersguide/plugins.rst
@@ -0,0 +1,723 @@
+.. 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.
+
+
+Plugins
+=======
+
+Storage Plugins
+---------------
+
+This section gives an outline of how to implement a plugin to integrate
+a third-party storage provider. For details and an example, you will
+need to read the code.
+
+.. note:: Example code is available at: `plugins/storage/volume/sample`
+
+Third party storage providers can integrate with CloudStack to provide
+either primary storage or secondary storage. For example, CloudStack
+provides plugins for Amazon Simple Storage Service (S3) or OpenStack
+Object Storage (Swift). The S3 plugin can be used for any object storage
+that supports the Amazon S3 interface.
+
+Additional third party object storages that do not support the S3
+interface can be integrated with CloudStack by writing plugin software that
+uses the object storage plugin framework. Several new interfaces are
+available so that storage providers can develop vendor-specific plugins
+based on well-defined contracts that can be seamlessly managed by
+CloudStack.
+
+Artifacts such as templates, ISOs and snapshots are kept in storage
+which CloudStack refers to as secondary storage. To improve scalability and
+performance, as when a number of hosts access secondary storage
+concurrently, object storage can be used for secondary storage. Object
+storage can also provide built-in high availability capability. When
+using object storage, access to secondary storage data can be made
+available across multiple zones in a region. This is a huge benefit, as
+it is no longer necessary to copy templates, snapshots etc. across zones
+as would be needed in an environment using only zone-based NFS storage.
+
+The user enables a storage plugin through the UI. A new dialog box
+choice is offered to select the storage provider. Depending on which
+provider is selected, additional input fields may appear so that the
+user can provide the additional details required by that provider, such
+as a user name and password for a third-party storage account.
+
+
+Overview of How to Write a Storage Plugin
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To add a third-party storage option to CloudStack, follow these general
+steps (explained in more detail later in this section):
+
+#. Implement the following interfaces in Java:
+
+ - DataStoreDriver
+
+ - DataStoreLifecycle
+
+ - DataStoreProvider
+
+ - VMSnapshotStrategy (if you want to customize the VM snapshot
+ functionality)
+
+#. Hardcode your plugin's required additional input fields into the code
+ for the Add Secondary Storage or Add Primary Storage dialog box.
+
+#. Place your .jar file in `plugins/storage/volume/` or
+ `plugins/storage/image/`.
+
+#. Edit `/client/tomcatconf/componentContext.xml.in`.
+
+#. Edit `client/pom.xml`.
+
+
+Implementing DataStoreDriver
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+DataStoreDriver contains the code that CloudStack will use to provision the
+object store, when needed.
+
+You must implement the following methods:
+
+- getTO()
+
+- getStoreTO()
+
+- createAsync()
+
+- deleteAsync()
+
+The following methods are optional:
+
+- resize()
+
+- canCopy() is optional. If you set it to true, then you must implement
+ copyAsync().
+
+
+Implementing DataStoreLifecycle
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+DataStoreLifecycle contains the code to manage the storage operations
+for ongoing use of the storage. Several operations are needed, like
+create, maintenance mode, delete, etc.
+
+You must implement the following methods:
+
+- initialize()
+
+- maintain()
+
+- cancelMaintain()
+
+- deleteDataStore()
+
+- Implement one of the attach\*() methods depending on what scope you
+ want the storage to have: attachHost(), attachCluster(), or attachZone().
+
+
+Implementing DataStoreProvider
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+DataStoreProvider contains the main code of the data store.
+
+You must implement the following methods:
+
+- getDatastoreLifeCycle()
+
+- getDataStoreDriver()
+
+- getTypes(). Returns one or more types of storage for which this data
+ store provider can be used. For secondary object storage, return
+ IMAGE, and for a Secondary Staging Store, return ImageCache.
+
+- configure(). First initialize the lifecycle implementation and the
+ driver implementation, then call registerDriver() to register the new
+ object store provider instance with CloudStack.
+
+- getName(). Returns the unique name of your provider; for example,
+ this can be used to get the name to display in the UI.
+
+The following methods are optional:
+
+- getHostListener() is optional; it's for monitoring the status of the host.
+
+
+Implementing VMSnapshotStrategy
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+VMSnapshotStrategy has the following methods:
+
+- takeVMSnapshot()
+
+- deleteVMSnapshot()
+
+- revertVMSnapshot()
+
+- canHandle(). For a given VM snapshot, tells whether this
+ implementation of VMSnapshotStrategy can handle it.
+
+
+Place the .jar File in the Right Directory
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+For a secondary storage plugin, place your .jar file here:
+
+::
+
+ plugins/storage/image/
+
+For a primary storage plugin, place your .jar file here:
+
+::
+
+ plugins/storage/volume/
+
+
+Edit Configuration Files
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+First, edit the following file tell CloudStack to include your .jar file.
+Add a line to this file to tell the CloudStack Management Server that it
+now has a dependency on your code:
+
+::
+
+ client/pom.xml
+
+Place some facts about your code in the following file so CloudStack can
+run it:
+
+::
+
+ /client/tomcatconf/componentContext.xml.in
+
+In the section “Deployment configurations of various adapters,” add
+this:
+
+::
+
+ <bean>id=”some unique ID” class=”package name of your implementation of DataStoreProvider”</bean>
+
+In the section “Storage Providers,” add this:
+
+::
+
+ <property name=”providers”>
+ <ref local=”same ID from the bean tag's id attribute”>
+ </property>
+
+
+Minimum Required Interfaces
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The classes, interfaces, and methods used by CloudStack from the Amazon Web
+Services (AWS) Java SDK are listed in this section. An object storage
+that supports the S3 interface is minimally required to support the
+below in order to be compatible with CloudStack.
+
+
+Interface AmazonS3
+^^^^^^^^^^^^^^^^^^
+
+http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/AmazonS3.html
+
+.. cssclass:: table-striped table-bordered table-hover
+
++------------------+---------------------------------------------------------+
+| Modifier and | Method and Description |
+| Type | |
++==================+=========================================================+
+| Bucket | createBucket(String bucketName) |
+| | |
+| | Creates a new Amazon S3 bucket with the specified name |
+| | in the default (US) region, Region.US\_Standard. |
++------------------+---------------------------------------------------------+
+| void | deleteObject(String bucketName, String key) |
+| | |
+| | Deletes the specified object in the specified bucket. |
++------------------+---------------------------------------------------------+
+| ObjectMetadata | getObject(GetObjectRequest getObjectRequest, |
+| | File destinationFile) |
+| | |
+| | Gets the object metadata for the object stored in |
+| | Amazon S3 under the specified bucket and key, and saves |
+| | the object contents to the specified file. |
++------------------+---------------------------------------------------------+
+| S3Object | getObject(String bucketName, String key) |
+| | |
+| | Gets the object stored in Amazon S3 under the specified |
+| | bucket and key. |
++------------------+---------------------------------------------------------+
+| URL | generatePresignedUrl(String bucketName, String key, |
+| | Date expiration, HttpMethod method) |
+| | |
+| | Returns a pre-signed URL for accessing an Amazon S3 |
+| | resource. |
++------------------+---------------------------------------------------------+
+| void | deleteBucket(String bucketName) |
+| | |
+| | Deletes the specified bucket. |
++------------------+---------------------------------------------------------+
+| List<Bucket> | listBuckets() |
+| | |
+| | Returns a list of all Amazon S3 buckets that the |
+| | authenticated sender of the request owns. |
++------------------+---------------------------------------------------------+
+| ObjectListing | listObjects(String bucketName, String prefix) |
+| | |
+| | Returns a list of summary information about the objects |
+| | in the specified bucket. |
++------------------+---------------------------------------------------------+
+| PutObjectResult | putObject(PutObjectRequest putObjectRequest) |
+| | |
+| | Uploads a new object to the specified Amazon S3 bucket. |
++------------------+---------------------------------------------------------+
+| PutObjectResult | putObject(String bucketName, String key, File file) |
+| | |
+| | Uploads the specified file to Amazon S3 under the |
+| | specified bucket and key name. |
++------------------+---------------------------------------------------------+
+| PutObjectResult | putObject(String bucketName, String key, |
+| | InputStream input, ObjectMetadata metadata) |
+| | |
+| | Uploads the specified input stream and object metadata |
+| | to Amazon S3 under the specified bucket and key name. |
++------------------+---------------------------------------------------------+
+| void | setEndpoint(String endpoint) |
+| | |
+| | Overrides the default endpoint for this client. |
++------------------+---------------------------------------------------------+
+| void | setObjectAcl(String bucketName, String key, |
+| | CannedAccessControlList acl) |
+| | |
+| | Sets the CannedAccessControlList for the specified |
+| | object in Amazon S3 using one of the pre-configured |
+| | CannedAccessControlLists. |
++------------------+---------------------------------------------------------+
+
+*Class TransferManager*
+
+http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/transfer/TransferManager.html
+
+.. cssclass:: table-striped table-bordered table-hover
+
++------------------+---------------------------------------------------------+
+| Modifier and | Method and Description |
+| Type | |
++==================+=========================================================+
+| Upload | upload(PutObjectRequest putObjectRequest) |
+| | |
+| | Schedules a new transfer to upload data to Amazon S3. |
++------------------+---------------------------------------------------------+
+
+*Class PutObjectRequest*
+
+http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/model/PutObjectRequest.html
+
+.. cssclass:: table-striped table-bordered table-hover
+
++------------------+---------------------------------------------------------+
+| Modifier and | Method and Description |
+| Type | |
++==================+=========================================================+
+| Upload | upload(PutObjectRequest putObjectRequest) |
+| | |
+| | Schedules a new transfer to upload data to Amazon S3. |
++------------------+---------------------------------------------------------+
+
+
+Third Party UI Plugins
+----------------------
+
+Using the new third-party plugin framework, you can write and install
+extensions to CloudStack. The installed and enabled plugins will appear in
+the UI alongside the other features. The code for the plugin is simply
+placed in a special directory within CloudStack’s installed code at any
+time after CloudStack installation. The new plugin appears only when it is
+enabled by the cloud administrator.
+
+.. figure:: /_static/images/plugin_intro.jpg
+ :align: center
+ :alt: New plugin button in CloudStack navbar
+
+The left navigation bar of the CloudStack UI has a new Plugins button to
+help you work with UI plugins.
+
+
+How to Write a Plugin: Overview
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The basic procedure for writing a plugin is:
+
+#. Write the code and create the other files needed. You will need the
+ plugin code itself (in Javascript), a thumbnail image, the plugin
+ listing, and a CSS file.
+
+ .. figure:: /_static/images/plugin1.jpg
+ :align: center
+ :alt: Write the plugin code
+
+ All UI plugins have the following set of files:
+
+ ::
+
+ +-- cloudstack/
+ +-- ui/
+ +-- plugins/
+ +-- csMyFirstPlugin/
+ +-- config.js --> Plugin metadata (title, author, vendor URL, etc.)
+ +-- icon.png --> Icon, shown on side nav bar and plugin listing
+ (should be square, and ~50x50px)
+ +-- csMyFirstPlugin.css --> CSS file, loaded automatically when plugin loads
+ +-- csMyFirstPlugin.js --> Main JS file, containing plugin code
+
+
+ The same files must also be present at
+ `/tomcat/webapps/client/plugins`.
+
+#. The CloudStack administrator adds the folder containing your plugin code
+ under the CloudStack PLUGINS folder.
+
+ .. figure:: /_static/images/plugin2.jpg
+ :align: center
+ :alt: The plugin code is placed in the PLUGINS folder
+
+#. The administrator also adds the name of your plugin to the plugin.js
+ file in the PLUGINS folder.
+
+ .. figure:: /_static/images/plugin3.jpg
+ :align: center
+ :alt: The plugin name is added to `plugin.js` in the PLUGINS folder
+
+#. The next time the user refreshes the UI in the browser, your plugin
+ will appear in the left navigation bar.
+
+ .. figure:: /_static/images/plugin4.jpg
+ :align: center
+ :alt: The plugin appears in the UI
+
+
+How to Write a Plugin: Implementation Details
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+This section requires an understanding of JavaScript and the CloudStack
+API. You don't need knowledge of specific frameworks for this tutorial
+(jQuery, etc.), since the CloudStack UI handles the front-end rendering for
+you.
+
+There is much more to the CloudStack UI framework than can be described
+here. The UI is very flexible to handle many use cases, so there are
+countless options and variations. The best reference right now is to
+read the existing code for the main UI, which is in the /ui folder.
+Plugins are written in a very similar way to the main UI.
+
+#. **Create the directory to hold your plugin.**
+
+ All plugins are composed of set of required files in the directory
+ /ui/plugins/pluginID, where pluginID is a short name for your
+ plugin. It's recommended that you prefix your folder name (for
+ example, bfMyPlugin) to avoid naming conflicts with other people's
+ plugins.
+
+ In this example, the plugin is named csMyFirstPlugin.
+
+ ::
+
+ $ cd cloudstack/ui/plugins
+ $ mkdir csMyFirstPlugin
+ $ ls -l
+
+ total 8
+ drwxr-xr-x 2 bgregory staff 68 Feb 11 14:44 csMyFirstPlugin
+ -rw-r--r-- 1 bgregory staff 101 Feb 11 14:26 plugins.js
+
+#. **Change to your new plugin directory.**
+
+ ::
+
+ $ cd csMyFirstPlugin
+
+#. **Set up the listing.**
+
+ Add the file `config.js`, using your favorite editor.
+
+ ::
+
+ $ vi config.js
+
+ Add the following content to config.js. This information will be
+ displayed on the plugin listing page in the UI:
+
+ ::
+
+ (function (cloudStack) {
+ cloudStack.plugins.csMyFirstPlugin.config = {
+ title: 'My first plugin',
+ desc: 'Tutorial plugin',
+ externalLink: 'http://www.cloudstack.org/',
+ authorName: 'Test Plugin Developer',
+ authorEmail: 'plugin.developer@example.com'
+ };
+ }(cloudStack));
+
+
+#. **Add a new main section.**
+
+ Add the file csMyFirstPlugin.js, using your favorite editor.
+
+ ::
+
+ $ vi csMyFirstPlugin.js
+
+ Add the following content to csMyFirstPlugin.js:
+
+ ::
+
+ (function (cloudStack) {
+ cloudStack.plugins.csMyFirstPlugin = function(plugin) {
+ plugin.ui.addSection({
+ id: 'csMyFirstPlugin',
+ title: 'My Plugin',
+ preFilter: function(args) {
+ return isAdmin();
+ },
+ show: function() {
+ return $('<div>').html('Content will go here');
+ }
+ });
+ };
+ }(cloudStack));
+
+
+#. **Register the plugin.**
+
+ You now have the minimal content needed to run the plugin, so you
+ can activate the plugin in the UI by adding it to plugins.js. First,
+ edit the file:
+
+ ::
+
+ $ cd cloudstack/ui/plugins
+ $ vi plugins.js
+
+
+ Now add the following to plugins.js:
+
+ ::
+
+ (function($, cloudStack) {
+ cloudStack.plugins = [
+ 'csMyFirstPlugin'
+ ];
+ }(jQuery, cloudStack));
+
+
+#. **Check the plugin in the UI.**
+
+ First, copy all the plugin code that you have created so far to
+ `/tomcat/webapps/client/plugins`. Then refresh the browser and click
+ Plugins in the side navigation bar. You should see your new plugin.
+
+#. **Make the plugin do something.**
+
+ Right now, you just have placeholder content in the new plugin. It's
+ time to add real code. In this example, you will write a basic list
+ view, which renders data from an API call. You will list all virtual
+ machines owned by the logged-in user. To do this, replace the 'show'
+ function in the plugin code with a 'listView' block, containing the
+ required syntax for a list view. To get the data, use the
+ listVirtualMachines API call. Without any parameters, it will return
+ VMs only for your active user. Use the provided 'apiCall' helper
+ method to handle the server call. Of course, you are free to use any
+ other method for making the AJAX call (for example, jQuery's $.ajax
+ method).
+
+ First, open your plugin's JavaScript source file in your favorite
+ editor:
+
+ ::
+
+ $ cd csMyFirstPlugin
+ $ vi csMyFirstPlugin.js
+
+
+ Add the following code in csMyFirstPlugin.js:
+
+ ::
+
+ (function (cloudStack) {
+ cloudStack.plugins.csMyFirstPlugin = function(plugin) {
+ plugin.ui.addSection({
+ id: 'csMyFirstPlugin',
+ title: 'My Plugin',
+ preFilter: function(args) {
+ return isAdmin();
+ },
+
+ // Render page as a list view
+ listView: {
+ id: 'testPluginInstances',
+ fields: {
+ name: { label: 'label.name' },
+ instancename: { label: 'label.internal.name' },
+ displayname: { label: 'label.display.name' },
+ zonename: { label: 'label.zone.name' }
+ },
+ dataProvider: function(args) {
+ // API calls go here, to retrive the data asynchronously
+ //
+ // On successful retrieval, call
+ // args.response.success({ data: [data array] });
+ plugin.ui.apiCall('listVirtualMachines', {
+ success: function(json) {
+ var vms = json.listvirtualmachinesresponse.virtualmachine;
+
+ args.response.success({ data: vms });
+ },
+ error: function(errorMessage) {
+ args.response.error(errorMessage)
+ }
+ });
+ }
+ }
+ });
+ };
+ }(cloudStack));
+
+
+#. **Test the plugin.**
+
+ First, copy all the plugin code that you have created so far to
+ `/tomcat/webapps/client/plugins`. Then refresh the browser. You can
+ see that your placeholder content was replaced with a list table,
+ containing 4 columns of virtual machine data.
+
+#. **Add an action button.**
+
+ Let's add an action button to the list view, which will reboot the
+ VM. To do this, add an actions block under listView. After
+ specifying the correct format, the actions will appear automatically
+ to the right of each row of data.
+
+ ::
+
+ $ vi csMyFirstPlugin.js
+
+
+ Now add the following new code in csMyFirstPlugin.js. (The dots ...
+ show where we have omitted some existing code for the sake of space.
+ Don't actually cut and paste that part):
+
+ ::
+
+ ...
+ listView: {
+ id: 'testPluginInstances',
+ ...
+
+ actions: {
+ // The key/ID you specify here will determine what icon is
+ // shown in the UI for this action,
+ // and will be added as a CSS class to the action's element
+ // (i.e., '.action.restart')
+ //
+ // -- here, 'restart' is a predefined name in CloudStack that will
+ // automatically show a 'reboot' arrow as an icon;
+ // this can be changed in csMyFirstPlugin.css
+ restart: {
+ label: 'Restart VM',
+ messages: {
+ confirm: function() { return 'Are you sure you want to restart this VM?' },
+ notification: function() { return 'Rebooted VM' }
+ },
+ action: function(args) {
+ // Get the instance object of the selected row from context
+ //
+ // -- all currently loaded state is stored in 'context' as objects,
+ // such as the selected list view row,
+ // the selected section, and active user
+ //
+ // -- for list view actions, the object's key will be the same as
+ // listView.id, specified above;
+ // always make sure you specify an 'id' for the listView,
+ // or else it will be 'undefined!'
+ var instance = args.context.testPluginInstances[0];
+
+ plugin.ui.apiCall('rebootVirtualMachine', {
+ // These will be appended to the API request
+ //
+ // i.e., rebootVirtualMachine&id=...
+ data: {
+ id: instance.id
+ },
+ success: function(json) {
+ args.response.success({
+ // This is an async job, so success here only indicates
+ // that the job was initiated.
+ //
+ // To pass the job ID to the notification UI
+ // (for checking to see when action is completed),
+ // '_custom: { jobID: ... }' needs to always be passed on success,
+ // in the same format as below
+ _custom: { jobId: json.rebootvirtualmachineresponse.jobid }
+ });
+ },
+
+
+ error: function(errorMessage) {
+ args.response.error(errorMessage); // Cancel action, show error message returned
+ }
+ });
+ },
+
+ // Because rebootVirtualMachine is an async job, we need to add
+ // a poll function, which will perodically check
+ // the management server to see if the job is ready
+ // (via pollAsyncJobResult API call)
+ //
+ // The plugin API provides a helper function, 'plugin.ui.pollAsyncJob',
+ / which will work for most jobs
+ // in CloudStack
+ notification: {
+ poll: plugin.ui.pollAsyncJob
+ }
+ }
+ },
+
+ dataProvider: function(args) {
+ ...
+ ...
+
+
+#. **Add the thumbnail icon.**
+
+ Create an icon file; it should be square, about 50x50 pixels, and
+ named `icon.png`. Copy it into the same directory with your plugin
+ code: `cloudstack/ui/plugins/csMyFirstPlugin/icon.png`.
+
+#. **Add the stylesheet.**
+
+ Create a CSS file, with the same name as your `.js` file. Copy it into
+ the same directory with your plugin code:
+ `cloudstack/ui/plugins/csMyFirstPlugin/csMyFirstPlugin.css`.
+
+
+.. | plugin_intro.jpg: New plugin button in CloudStack navbar | image:: _static/images/plugin_intro.jpg
+.. | plugin1.jpg: Write the plugin code | image:: _static/images/plugin1.jpg
+.. | plugin2.jpg: The plugin code is placed in the PLUGINS folder | image:: _static/images/plugin2.jpg
+.. | plugin3.jpg: The plugin name is added to plugin.js in the PLUGINS folder | image:: _static/images/plugin3.jpg
+.. | plugin4.jpg: The plugin appears in the UI | image:: _static/images/plugin4.jpg
diff --git a/source/index.rst b/source/index.rst
new file mode 100644
index 0000000..ba69e42
--- /dev/null
+++ b/source/index.rst
@@ -0,0 +1,68 @@
+.. 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.
+
+.. Apache CloudStack documentation master file, created by
+ sphinx-quickstart on Fri Jul 20 17:32:34 2018.
+ You can adapt this file completely to your liking, but it should at least
+ contain the root `toctree` directive.
+
+
+|menu_acs_logo|
+
+
+Welcome to Apache CloudStack's Documentation
+============================================
+
+We have a number of guides, starting with a guide to cloudstack's terminology and concepts, moving through some information about possible topologies. We then have a quick start guide to help you get a very simple cloudstack up and running. Followed by the full installation guide, an administrator's guide and then further detailed guides on complex configurations.
+
+Information can also be found at CloudStack's wiki https://cwiki.apache.org/confluence/display/CLOUDSTACK/Home and on cloudstack mailing lists http://cloudstack.apache.org/mailing-lists.html
+
+.. toctree::
+ :maxdepth: 3
+ :caption: Contents:
+
+ conceptsandterminology/index
+ quickinstallationguide/qig
+ installguide/index
+ upgrading/index
+ adminguide/index
+ developersguide/index
+ plugins/index
+ releasenotes/index
+
+
+.. toctree::
+ :caption: Other Documentation:
+
+ API Documentation <http://cloudstack.apache.org/api.html>
+ Apache CloudStack Wiki <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Home>
+ Apache CloudStack web site <http://cloudstack.apache.org/>
+ Apache CloudStack Source Code <http://cloudstack.apache.org/downloads.html>
+ Apache CloudStack on GitHub <https://github.com/apache/cloudstack>
+
+
+.. toctree::
+ :caption: Pre 4.11 Documentation:
+
+ Installation Guide <http://docs.cloudstack.apache.org/projects/cloudstack-installation>
+ Administration Guide <http://docs.cloudstack.apache.org/projects/cloudstack-administration>
+ Release Notes <http://docs.cloudstack.apache.org/projects/cloudstack-release-notes>
+
+
+Indices and Tables
+==================
+
+* :ref:`genindex`
+* :ref:`search`
diff --git a/source/installguide/building_from_source.rst b/source/installguide/building_from_source.rst
new file mode 100644
index 0000000..508899d
--- /dev/null
+++ b/source/installguide/building_from_source.rst
@@ -0,0 +1,511 @@
+.. 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.
+
+
+Introduction
+------------
+
+The official CloudStack release is always in source code form. You will
+likely be able to find "convenience binaries," the source is the
+canonical release. In this section, we'll cover acquiring the source
+release and building that so that you can deploy it using Maven or
+create Debian packages or RPMs.
+
+Note that building and deploying directly from source is typically not
+the most efficient way to deploy an IaaS. However, we will cover that
+method as well as building RPMs or Debian packages for deploying
+CloudStack.
+
+The instructions here are likely version-specific. That is, the method
+for building from source for the 4.7.x series is different from the
+4.2.x series.
+
+If you are working with a unreleased version of CloudStack, see the
+INSTALL.md file in the top-level directory of the release.
+
+
+Downloading the release
+-----------------------
+
+You can download the latest CloudStack release from the `Apache
+CloudStack project download page
+<http://cloudstack.apache.org/downloads.html>`_.
+
+Prior releases are available via archive.apache.org as well. See the
+downloads page for more information on archived releases.
+
+You'll notice several links under the 'Latest release' section. A link
+to a file ending in ``tar.bz2``, as well as a PGP/GPG signature, MD5,
+and SHA512 file.
+
+- The ``tar.bz2`` file contains the Bzip2-compressed tarball with the
+ source code.
+
+- The ``.asc`` file is a detached cryptographic signature that can be
+ used to help verify the authenticity of the release.
+
+- The ``.md5`` file is an MD5 hash of the release to aid in verify the
+ validity of the release download.
+
+- The ``.sha`` file is a SHA512 hash of the release to aid in verify
+ the validity of the release download.
+
+
+Verifying the downloaded release
+--------------------------------
+
+There are a number of mechanisms to check the authenticity and validity
+of a downloaded release.
+
+
+Getting the KEYS
+~~~~~~~~~~~~~~~~
+
+To enable you to verify the GPG signature, you will need to download the
+`KEYS <http://www.apache.org/dist/cloudstack/KEYS>`_ file.
+
+You next need to import those keys, which you can do by running:
+
+.. parsed-literal::
+
+ $ wget http://www.apache.org/dist/cloudstack/KEYS
+ $ gpg --import KEYS
+
+
+GPG
+~~~
+
+The CloudStack project provides a detached GPG signature of the release.
+To check the signature, run the following command:
+
+.. parsed-literal::
+
+ $ gpg --verify apache-cloudstack-|release|-src.tar.bz2.asc
+
+If the signature is valid you will see a line of output that contains
+'Good signature'.
+
+
+MD5
+~~~
+
+In addition to the cryptographic signature, CloudStack has an MD5
+checksum that you can use to verify the download matches the release.
+You can verify this hash by executing the following command:
+
+.. parsed-literal::
+
+ $ gpg --print-md MD5 apache-cloudstack-|release|-src.tar.bz2 | diff - apache-cloudstack-|release|-src.tar.bz2.md5
+
+If this successfully completes you should see no output. If there is any
+output from them, then there is a difference between the hash you
+generated locally and the hash that has been pulled from the server.
+
+
+SHA512
+~~~~~~
+
+In addition to the MD5 hash, the CloudStack project provides a SHA512
+cryptographic hash to aid in assurance of the validity of the downloaded
+release. You can verify this hash by executing the following command:
+
+.. parsed-literal::
+
+ $ gpg --print-md SHA512 apache-cloudstack-|release|-src.tar.bz2 | diff - apache-cloudstack-|release|-src.tar.bz2.sha
+
+If this command successfully completes you should see no output. If
+there is any output from them, then there is a difference between the
+hash you generated locally and the hash that has been pulled from the
+server.
+
+
+Prerequisites for building Apache CloudStack
+--------------------------------------------
+
+There are a number of prerequisites needed to build CloudStack. This
+document assumes compilation on a Linux system that uses RPMs or DEBs
+for package management.
+
+You will need, at a minimum, the following to compile CloudStack:
+
+#. Maven (version 3)
+
+#. Java (Java 8/OpenJDK 1.8)
+
+#. Apache Web Services Common Utilities (ws-commons-util)
+
+#. MySQL
+
+#. MySQLdb (provides Python database API)
+
+#. genisoimage
+
+#. rpmbuild or dpkg-dev
+
+
+Extracting source
+-----------------
+
+Extracting the CloudStack release is relatively simple and can be done
+with a single command as follows:
+
+.. parsed-literal::
+
+ $ tar -jxvf apache-cloudstack-|release|-src.tar.bz2
+
+You can now move into the directory:
+
+.. parsed-literal::
+
+ $ cd ./apache-cloudstack-|release|-src
+
+Install new MySQL connector
+---------------------------
+
+Install Python MySQL connector using the official MySQL packages repository.
+
+
+MySQL connector APT repository
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Install the following package provided by MySQL to enable official repositories:
+
+.. note:
+
+ If the download fails check the current version number. The version available may
+ have been updated.
+
+.. parsed-literal::
+
+ wget http://dev.mysql.com/get/mysql-apt-config_0.7.3-1_all.deb
+ sudo dpkg -i mysql-apt-config_0.7.3-1_all.deb
+
+Make sure to activate the repository for MySQL connectors.
+
+.. parsed-literal::
+
+ sudo apt-get update
+ sudo apt-get install mysql-connector-python
+
+
+MySQL connector RPM repository
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Add a new yum repo ``/etc/yum.repos.d/mysql.repo``:
+
+.. parsed-literal::
+
+ [mysql-community]
+ name=MySQL Community connectors
+ baseurl=http://repo.mysql.com/yum/mysql-connectors-community/el/$releasever/$basearch/
+ enabled=1
+ gpgcheck=1
+
+Import GPG public key from MySQL:
+
+.. parsed-literal::
+
+ rpm --import http://repo.mysql.com/RPM-GPG-KEY-mysql
+
+Install mysql-connector
+
+.. parsed-literal::
+
+ yum install mysql-connector-python
+
+.. _building_deb_packages:
+
+Building DEB packages
+---------------------
+
+In addition to the bootstrap dependencies, you'll also need to install
+several other dependencies. Note that we recommend using Maven 3.
+
+.. parsed-literal::
+
+ $ sudo apt-get update
+ $ sudo apt-get install python-software-properties
+ $ sudo apt-get update
+ $ sudo apt-get install debhelper openjdk-8-jdk libws-commons-util-java genisoimage libcommons-codec-java libcommons-httpclient-java liblog4j1.2-java maven
+
+While we have defined, and you have presumably already installed the
+bootstrap prerequisites, there are a number of build time prerequisites
+that need to be resolved. CloudStack uses maven for dependency
+resolution. You can resolve the buildtime depdencies for CloudStack by
+running:
+
+.. parsed-literal::
+
+ $ mvn -P deps
+
+Now that we have resolved the dependencies we can move on to building
+CloudStack and packaging them into DEBs by issuing the following
+command.
+
+.. parsed-literal::
+
+ $ dpkg-buildpackage -uc -us
+
+This command will build the following debian packages. You should have
+all of the following:
+
+.. parsed-literal::
+
+ cloudstack-common-|release|.amd64.deb
+ cloudstack-management-|release|.amd64.deb
+ cloudstack-agent-|release|.amd64.deb
+ cloudstack-usage-|release|.amd64.deb
+ cloudstack-cli-|release|.amd64.deb
+
+
+Setting up an APT repo
+~~~~~~~~~~~~~~~~~~~~~~
+
+After you've created the packages, you'll want to copy them to a system
+where you can serve the packages over HTTP. You'll create a directory
+for the packages and then use ``dpkg-scanpackages`` to create
+``Packages.gz``, which holds information about the archive structure.
+Finally, you'll add the repository to your system(s) so you can install
+the packages using APT.
+
+The first step is to make sure that you have the **dpkg-dev** package
+installed. This should have been installed when you pulled in the
+**debhelper** application previously, but if you're generating
+``Packages.gz`` on a different system, be sure that it's installed there
+as well.
+
+.. parsed-literal::
+
+ $ sudo apt-get install dpkg-dev
+
+The next step is to copy the DEBs to the directory where they can be
+served over HTTP. We'll use ``/var/www/cloudstack/repo`` in the
+examples, but change the directory to whatever works for you.
+
+.. parsed-literal::
+
+ $ sudo mkdir -p /var/www/cloudstack/repo/binary
+ $ sudo cp \*.deb /var/www/cloudstack/repo/binary
+ $ cd /var/www/cloudstack/repo/binary
+ $ sudo sh -c 'dpkg-scanpackages . /dev/null | tee Packages | gzip -9 > Packages.gz'
+
+.. note::
+
+ You can safely ignore the warning about a missing override file.
+
+Now you should have all of the DEB packages and ``Packages.gz`` in the
+``binary`` directory and available over HTTP. (You may want to use
+``wget`` or ``curl`` to test this before moving on to the next step.)
+
+
+Configuring your machines to use the APT repository
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Now that we have created the repository, you need to configure your
+machine to make use of the APT repository. You can do this by adding a
+repository file under ``/etc/apt/sources.list.d``. Use your preferred
+editor to create ``/etc/apt/sources.list.d/cloudstack.list`` with this
+line:
+
+.. parsed-literal::
+
+ deb http://server.url/cloudstack/repo/binary ./
+
+Now that you have the repository info in place, you'll want to run
+another update so that APT knows where to find the CloudStack packages.
+
+.. parsed-literal::
+
+ $ sudo apt-get update
+
+You can now move on to the instructions under Install on Ubuntu.
+
+
+Building RPMs from Source
+-------------------------
+
+As mentioned previously in `“Prerequisites for building Apache CloudStack”
+<#prerequisites-for-building-apache-cloudstack>`_, you will need to install
+several prerequisites before you can build packages for CloudStack. Here we'll
+assume you're working with a 64-bit build of CentOS or Red Hat Enterprise
+Linux.
+
+.. parsed-literal::
+
+ # yum groupinstall "Development Tools"
+
+.. parsed-literal::
+
+ # yum install java-1.8.0-openjdk-devel.x86_64 genisoimage mysql mysql-server ws-commons-util MySQL-python createrepo
+
+Next, you'll need to install build-time dependencies for CloudStack with
+Maven. We're using Maven 3, so you'll want to grab `Maven 3.0.5 (Binary tar.gz)
+<http://maven.apache.org/download.cgi>`_ and uncompress it in
+your home directory (or whatever location you prefer):
+
+.. parsed-literal::
+
+ $ cd ~
+ $ tar zxvf apache-maven-3.0.5-bin.tar.gz
+
+.. parsed-literal::
+
+ $ export PATH=~/apache-maven-3.0.5/bin:$PATH
+
+Maven also needs to know where Java is, and expects the JAVA\_HOME
+environment variable to be set:
+
+.. parsed-literal::
+
+ $ export JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk.x86_64
+
+Verify that Maven is installed correctly:
+
+.. parsed-literal::
+
+ $ mvn --version
+
+You probably want to ensure that your environment variables will survive
+a logout/reboot. Be sure to update ``~/.bashrc`` with the PATH and
+JAVA\_HOME variables.
+
+Building RPMs for CloudStack is fairly simple. Assuming you already have
+the source downloaded and have uncompressed the tarball into a local
+directory, you're going to be able to generate packages in just a few
+minutes.
+
+.. note::
+
+ Packaging has changed. If you've created packages for CloudStack
+ previously, you should be aware that the process has changed considerably
+ since the project has moved to using Apache Maven. Please be sure to follow
+ the steps in this section closely.
+
+
+Generating RPMS
+~~~~~~~~~~~~~~~
+
+Now that we have the prerequisites and source, you will cd to the
+`packaging/` directory.
+
+.. parsed-literal::
+
+ $ cd packaging/
+
+Generating RPMs is done using the ``package.sh`` script:
+
+.. parsed-literal::
+
+ $ ./package.sh -d centos63
+
+For other supported options(like centos7), run ``./package.sh --help``
+
+That will run for a bit and then place the finished packages in
+``dist/rpmbuild/RPMS/x86_64/``.
+
+You should see the following RPMs in that directory:
+
+.. parsed-literal::
+
+ cloudstack-agent-|release|.el6.x86_64.rpm
+ cloudstack-cli-|release|.el6.x86_64.rpm
+ cloudstack-common-|release|.el6.x86_64.rpm
+ cloudstack-management-|release|.el6.x86_64.rpm
+ cloudstack-usage-|release|.el6.x86_64.rpm
+
+
+Creating a yum repo
+^^^^^^^^^^^^^^^^^^^
+
+While RPMs is a useful packaging format - it's most easily consumed from
+Yum repositories over a network. The next step is to create a Yum Repo
+with the finished packages:
+
+.. parsed-literal::
+
+ $ mkdir -p ~/tmp/repo
+
+ $ cd ../..
+ $ cp dist/rpmbuild/RPMS/x86_64/\*rpm ~/tmp/repo/
+
+ $ createrepo /tmp/repo
+
+The files and directories within ``~/tmp/repo`` can now be uploaded to a
+web server and serve as a yum repository.
+
+
+Configuring your systems to use your new yum repository
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Now that your yum repository is populated with RPMs and metadata we need
+to configure the machines that need to install CloudStack. Create a file
+named ``/etc/yum.repos.d/cloudstack.repo`` with this information:
+
+.. parsed-literal::
+
+ [apache-cloudstack]
+ name=Apache CloudStack
+ baseurl=http://webserver.tld/path/to/repo
+ enabled=1
+ gpgcheck=0
+
+Completing this step will allow you to easily install CloudStack on a
+number of machines across the network.
+
+.. _building-noredist:
+
+Building Non-OSS
+----------------
+
+If you need support for the VMware, NetApp, F5, NetScaler, SRX, or any
+other non-Open Source Software (nonoss) plugins, you'll need to download
+a few components on your own and follow a slightly different procedure
+to build from source.
+
+.. warning::
+
+ Some of the plugins supported by CloudStack cannot be distributed with
+ CloudStack for licensing reasons. In some cases, some of the required
+ libraries/JARs are under a proprietary license. In other cases, the
+ required libraries may be under a license that's not compatible with
+ `Apache's licensing guidelines for third-party products
+ <http://www.apache.org/legal/resolved.html#category-x>`_.
+
+#. To build the Non-OSS plugins, you'll need to have the requisite JARs
+ installed under the ``deps`` directory.
+
+ Because these modules require dependencies that can't be distributed
+ with CloudStack you'll need to download them yourself. Links to the
+ most recent dependencies are listed on the `*How to build CloudStack*
+ <https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack>`_
+ page on the wiki.
+
+#. You may also need to download
+ `vhd-util <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_,
+ which was removed due to licensing issues. You'll copy vhd-util to
+ the ``scripts/vm/hypervisor/xenserver/`` directory.
+
+#. Once you have all the dependencies copied over, you'll be able to
+ build CloudStack with the ``noredist`` option:
+
+.. parsed-literal::
+
+ $ mvn clean
+ $ mvn install -Dnoredist
+
+#. Once you've built CloudStack with the ``noredist`` profile, you can
+ package it using the `“Building RPMs from Source” <#building-rpms-from-source>`_
+ or `“Building DEB packages” <#building-deb-packages>`_ instructions.
+
diff --git a/source/installguide/configuration.rst b/source/installguide/configuration.rst
new file mode 100644
index 0000000..86cff2a
--- /dev/null
+++ b/source/installguide/configuration.rst
@@ -0,0 +1,1633 @@
+.. 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_your_CloudStack_Installation:
+
+Configuring your CloudStack Installation
+========================================
+
+This section tells how to add regions, zones, pods, clusters, hosts,
+storage, and networks to your cloud. If you are unfamiliar with these
+entities, please begin by looking through :ref:`infrastructure-overview`
+
+
+Overview of Provisioning Steps
+------------------------------
+
+After the Management Server is installed and running, you can add the
+compute resources for it to manage. For an overview of how a CloudStack
+cloud infrastructure is organized, see :ref:`infrastructure-overview`
+
+To provision the cloud infrastructure, or to scale it up at any time,
+follow these procedures:
+
+#. Define regions (optional). See :ref:`adding-regions`.
+
+#. Add a zone to the region. See :ref:`adding-a-zone`.
+
+#. Add more pods to the zone (optional). See :ref:`adding-a-pod`.
+
+#. Add more clusters to the pod (optional). See :ref:`adding-a-cluster`.
+
+#. Add more hosts to the cluster (optional). See :ref:`adding-a-host`.
+
+#. Add primary storage to the cluster. See :ref:`add-primary-storage`.
+
+#. Add secondary storage to the zone. See :ref:`add-secondary-storage`.
+
+#. Initialize and test the new cloud. See :ref:`initialize-and-test`.
+
+When you have finished these steps, you will have a deployment with the
+following basic structure:
+
+|provisioning-overview.png: Conceptual overview of a basic deployment|
+
+
+.. _adding-regions:
+
+Adding Regions (optional)
+-------------------------
+
+Grouping your cloud resources into geographic regions is an optional
+step when provisioning the cloud. For an overview of regions, see :ref:`about-regions`
+
+
+The First Region: The Default Region
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If you do not take action to define regions, then all the zones in your
+cloud will be automatically grouped into a single default region. This
+region is assigned the region ID of 1. You can change the name or URL of
+the default region by displaying the region in the CloudStack UI and
+clicking the Edit button.
+
+
+Adding a Region
+~~~~~~~~~~~~~~~
+
+Use these steps to add a second region in addition to the default
+region.
+
+#. Each region has its own CloudStack instance. Therefore, the first
+ step of creating a new region is to install the Management Server
+ software, on one or more nodes, in the geographic area where you want
+ to set up the new region. Use the steps in the Installation guide.
+ When you come to the step where you set up the database, use the
+ additional command-line flag ``-r <region_id>`` to set a region ID
+ for the new region. The default region is automatically assigned a
+ region ID of 1, so your first additional region might be region 2.
+
+ .. parsed-literal::
+
+ # cloudstack-setup-databases cloud:<dbpassword>@localhost --deploy-as=root:<password> -e <encryption_type> -m <management_server_key> -k <database_key> -r <region_id>
+
+#. By the end of the installation procedure, the Management Server
+ should have been started. Be sure that the Management Server
+ installation was successful and complete.
+
+#. Now add the new region to region 1 in CloudStack.
+
+ #. Log in to CloudStack in the first region as root administrator
+ (that is, log in to <region.1.IP.address>:8080/client).
+
+ #. In the left navigation bar, click Regions.
+
+ #. Click Add Region. In the dialog, fill in the following fields:
+
+ - ID. A unique identifying number. Use the same number you set in
+ the database during Management Server installation in the new
+ region; for example, 2.
+
+ - Name. Give the new region a descriptive name.
+
+ - Endpoint. The URL where you can log in to the Management Server
+ in the new region. This has the format
+ <region.2.IP.address>:8080/client.
+
+#. Now perform the same procedure in reverse. Log in to region 2, and
+ add region 1.
+
+#. Copy the account, user, and domain tables from the region 1 database
+ to the region 2 database.
+
+ In the following commands, it is assumed that you have set the root
+ password on the database, which is a CloudStack recommended best
+ practice. Substitute your own MySQL root password.
+
+ #. First, run this command to copy the contents of the database:
+
+ .. parsed-literal::
+
+ # mysqldump -u root -p<mysql_password> -h <region1_db_host> cloud account user domain > region1.sql
+
+ #. Then run this command to put the data onto the region 2 database:
+
+ .. parsed-literal::
+
+ # mysql -u root -p<mysql_password> -h <region2_db_host> cloud < region1.sql
+
+#. Remove project accounts. Run these commands on the region 2 database:
+
+ .. parsed-literal::
+
+ # mysql> delete from account where type = 5;
+
+#. Set the default zone as null:
+
+ .. parsed-literal::
+
+ # mysql> update account set default_zone_id = null;
+
+#. Restart the Management Servers in region 2.
+
+
+Adding Third and Subsequent Regions
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To add the third region, and subsequent additional regions, the steps
+are similar to those for adding the second region. However, you must
+repeat certain steps additional times for each additional region:
+
+#. Install CloudStack in each additional region. Set the region ID for
+ each region during the database setup step.
+
+ .. parsed-literal::
+
+ cloudstack-setup-databases cloud:<dbpassword>@localhost --deploy-as=root:<password> -e <encryption_type> -m <management_server_key> -k <database_key> -r <region_id>
+
+#. Once the Management Server is running, add your new region to all
+ existing regions by repeatedly using the Add Region button in the UI.
+ For example, if you were adding region 3:
+
+ #. Log in to CloudStack in the first region as root administrator
+ (that is, log in to <region.1.IP.address>:8080/client), and add a
+ region with ID 3, the name of region 3, and the endpoint
+ <region.3.IP.address>:8080/client.
+
+ #. Log in to CloudStack in the second region as root administrator
+ (that is, log in to <region.2.IP.address>:8080/client), and add a
+ region with ID 3, the name of region 3, and the endpoint
+ <region.3.IP.address>:8080/client.
+
+#. Repeat the procedure in reverse to add all existing regions to the
+ new region. For example, for the third region, add the other two
+ existing regions:
+
+ #. Log in to CloudStack in the third region as root administrator
+ (that is, log in to <region.3.IP.address>:8080/client).
+
+ #. Add a region with ID 1, the name of region 1, and the endpoint
+ <region.1.IP.address>:8080/client.
+
+ #. Add a region with ID 2, the name of region 2, and the endpoint
+ <region.2.IP.address>:8080/client.
+
+#. Copy the account, user, and domain tables from any existing region's
+ database to the new region's database.
+
+ In the following commands, it is assumed that you have set the root
+ password on the database, which is a CloudStack recommended best
+ practice. Substitute your own MySQL root password.
+
+ #. First, run this command to copy the contents of the database:
+
+ .. parsed-literal::
+
+ # mysqldump -u root -p<mysql_password> -h <region1_db_host> cloud account user domain > region1.sql
+
+ #. Then run this command to put the data onto the new region's
+ database. For example, for region 3:
+
+ .. parsed-literal::
+
+ # mysql -u root -p<mysql_password> -h <region3_db_host> cloud < region1.sql
+
+#. Remove project accounts. Run these commands on the region 3 database:
+
+ .. parsed-literal::
+
+ mysql> delete from account where type = 5;
+
+#. Set the default zone as null:
+
+ .. parsed-literal::
+
+ mysql> update account set default_zone_id = null;
+
+#. Restart the Management Servers in the new region.
+
+
+Deleting a Region
+~~~~~~~~~~~~~~~~~
+
+Log in to each of the other regions, navigate to the one you want to
+delete, and click Remove Region. For example, to remove the third region
+in a 3-region cloud:
+
+#. Log in to <region.1.IP.address>:8080/client.
+
+#. In the left navigation bar, click Regions.
+
+#. Click the name of the region you want to delete.
+
+#. Click the Remove Region button.
+
+#. Repeat these steps for <region.2.IP.address>:8080/client.
+
+
+.. _adding-a-zone:
+
+Adding a Zone
+-------------
+
+When you add a new zone, you will be prompted to configure the zone’s
+physical network and add the first pod, cluster, host, primary storage,
+and secondary storage.
+
+#. Log in to the CloudStack UI as the root administrator. See :ref:`log-in-to-ui`.
+
+#. In the left navigation, choose Infrastructure.
+
+#. On Zones, click View More.
+
+#. Click Add Zone. The zone creation wizard will appear.
+
+#. Choose one of the following network types:
+
+ - **Basic.** For AWS-style networking. Provides a single network
+ where each VM instance is assigned an IP directly from the
+ network. Guest isolation can be provided through layer-3 means
+ such as security groups (IP address source filtering).
+
+ - **Advanced.** For more sophisticated network topologies. This
+ network model provides the most flexibility in defining guest
+ networks and providing custom network offerings such as firewall,
+ VPN, or load balancer support.
+
+#. The rest of the steps differ depending on whether you chose Basic or
+ Advanced. Continue with the steps that apply to you:
+
+ - `“Basic Zone Configuration” <#basic-zone-configuration>`_
+
+ - `“Advanced Zone Configuration” <#advanced-zone-configuration>`_
+
+
+Basic Zone Configuration
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. After you select Basic in the Add Zone wizard and click Next, you
+ will be asked to enter the following details. Then click Next.
+
+ - **Name.** A name for the zone.
+
+ - **DNS 1 and 2.** These are DNS servers for use by guest VMs in the
+ zone. These DNS servers will be accessed via the public network
+ you will add later. The public IP addresses for the zone must have
+ a route to the DNS server named here.
+
+ - **Internal DNS 1 and Internal DNS 2.** These are DNS servers for
+ use by system VMs in the zone (these are VMs used by CloudStack
+ itself, such as virtual routers, console proxies, and Secondary
+ Storage VMs.) These DNS servers will be accessed via the
+ management traffic network interface of the System VMs. The
+ private IP address you provide for the pods must have a route to
+ the internal DNS server named here.
+
+ - **Hypervisor.** (Introduced in version 3.0.1) Choose the
+ hypervisor for the first cluster in the zone. You can add clusters
+ with different hypervisors later, after you finish adding the
+ zone.
+
+ - **Network Offering.** Your choice here determines what network
+ services will be available on the network for guest VMs.
+
+ .. cssclass:: table-striped table-bordered table-hover
+
+ =============================================== ===================================================================================================================
+ Network Offering Description
+ =============================================== ===================================================================================================================
+ DefaultSharedNetworkOfferingWithSGService If you want to enable security groups for guest traffic isolation, choose this. (See Using Security Groups to Control Traffic to VMs.)
+ DefaultSharedNetworkOffering If you do not need security groups, choose this.
+ DefaultSharedNetscalerEIPandELBNetworkOffering If you have installed a Citrix NetScaler appliance as part of your zone network, and you will be using its Elastic IP and Elastic Load Balancing features, choose this. With the EIP and ELB features, a basic zone with security groups enabled can offer 1:1 static NAT and load balancing.
+ =============================================== ===================================================================================================================
+
+
+ - **Network Domain.** (Optional) If you want to assign a special
+ domain name to the guest VM network, specify the DNS suffix.
+
+ - **Public.** A public zone is available to all users. A zone that
+ is not public will be assigned to a particular domain. Only users
+ in that domain will be allowed to create guest VMs in this zone.
+
+#. Choose which traffic types will be carried by the physical network.
+
+ The traffic types are management, public, guest, and storage traffic.
+ For more information about the types, roll over the icons to display
+ their tool tips, or see Basic Zone Network Traffic Types. This screen
+ starts out with some traffic types already assigned. To add more,
+ drag and drop traffic types onto the network. You can also change the
+ network name if desired.
+
+#. Assign a network traffic label to each traffic type on the physical
+ network. These labels must match the labels you have already defined
+ on the hypervisor host. To assign each label, click the Edit button
+ under the traffic type icon. A popup dialog appears where you can
+ type the label, then click OK.
+
+ These traffic labels will be defined only for the hypervisor selected
+ for the first cluster. For all other hypervisors, the labels can be
+ configured after the zone is created.
+
+#. Click Next.
+
+#. (NetScaler only) If you chose the network offering for NetScaler, you
+ have an additional screen to fill out. Provide the requested details
+ to set up the NetScaler, then click Next.
+
+ - **IP address.** The NSIP (NetScaler IP) address of the NetScaler
+ device.
+
+ - **Username/Password.** The authentication credentials to access
+ the device. CloudStack uses these credentials to access the
+ device.
+
+ - **Type.** NetScaler device type that is being added. It could be
+ NetScaler VPX, NetScaler MPX, or NetScaler SDX. For a comparison
+ of the types, see About Using a NetScaler Load Balancer.
+
+ - **Public interface.** Interface of NetScaler that is configured to
+ be part of the public network.
+
+ - **Private interface.** Interface of NetScaler that is configured
+ to be part of the private network.
+
+ - **Number of retries.** Number of times to attempt a command on the
+ device before considering the operation failed. Default is 2.
+
+ - **Capacity.** Number of guest networks/accounts that will share
+ this NetScaler device.
+
+ - **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.
+
+#. (NetScaler only) Configure the IP range for public traffic. The IPs
+ in this range will be used for the static NAT capability which you
+ enabled by selecting the network offering for NetScaler with EIP and
+ ELB. Enter the following details, then click Add. If desired, you can
+ repeat this step to add more IP ranges. When done, click Next.
+
+ - **Gateway.** The gateway in use for these IP addresses.
+
+ - **Netmask.** The netmask associated with this IP range.
+
+ - **VLAN.** The VLAN that will be used for public traffic.
+
+ - **Start IP/End IP.** A range of IP addresses that are assumed to
+ be accessible from the Internet and will be allocated for access
+ to guest VMs.
+
+#. In a new zone, CloudStack adds the first pod for you. You can always
+ add more pods later. For an overview of what a pod is, see :ref:`about-pods`
+
+ To configure the first pod, enter the following, then click Next:
+
+ - **Pod Name.** A name for the pod.
+
+ - **Reserved system gateway.** The gateway for the hosts in that
+ pod.
+
+ - **Reserved system netmask.** The network prefix that defines the
+ pod's subnet. Use CIDR notation.
+
+ - **Start/End Reserved System IP.** The IP range in the management
+ network that CloudStack uses to manage various system VMs, such as
+ Secondary Storage VMs, Console Proxy VMs, and DHCP. For more
+ information, see System Reserved IP Addresses.
+
+#. Configure the network for guest traffic. Provide the following, then
+ click Next:
+
+ - **Guest gateway.** The gateway that the guests should use.
+
+ - **Guest netmask.** The netmask in use on the subnet the guests
+ will use.
+
+ - **Guest start IP/End IP.** Enter the first and last IP addresses
+ that define a range that CloudStack can assign to guests.
+
+ - We strongly recommend the use of multiple NICs. If multiple
+ NICs are used, they may be in a different subnet.
+
+ - If one NIC is used, these IPs should be in the same CIDR as the
+ pod CIDR.
+
+#. In a new pod, CloudStack adds the first cluster for you. You can
+ always add more clusters later. For an overview of what a cluster is,
+ see About Clusters.
+
+ To configure the first cluster, enter the following, then click Next:
+
+ - **Hypervisor.** (Version 3.0.0 only; in 3.0.1, this field is read
+ only) Choose the type of hypervisor software that all hosts in
+ this cluster will run. If you choose VMware, additional fields
+ appear so you can give information about a vSphere cluster. For
+ vSphere servers, we recommend creating the cluster of hosts in
+ vCenter and then adding the entire cluster to CloudStack. See Add
+ Cluster: vSphere.
+
+ - **Cluster name.** Enter a name for the cluster. This can be text
+ of your choosing and is not used by CloudStack.
+
+#. In a new cluster, CloudStack adds the first host for you. You can
+ always add more hosts later. For an overview of what a host is, see
+ About Hosts.
+
+ .. note::
+ When you add a hypervisor host to CloudStack, the host must not have
+ any VMs already running.
+
+ Before you can configure the host, you need to install the hypervisor
+ software on the host. You will need to know which version of the
+ hypervisor software version is supported by CloudStack and what
+ additional configuration is required to ensure the host will work
+ with CloudStack. To find these installation details, see:
+
+ - Citrix XenServer Installation and Configuration
+
+ - VMware vSphere Installation and Configuration
+
+ - KVM vSphere Installation and Configuration
+
+ To configure the first host, enter the following, then click Next:
+
+ - **Host Name.** The DNS name or IP address of the host.
+
+ - **Username.** The username is root.
+
+ - **Password.** This is the password for the user named above (from
+ your XenServer or KVM install).
+
+ - **Host Tags.** (Optional) Any labels that you use to categorize
+ hosts for ease of maintenance. For example, you can set this to
+ the cloud's HA tag (set in the ha.tag global configuration
+ parameter) if you want this host to be used only for VMs with the
+ "high availability" feature enabled. For more information, see
+ HA-Enabled Virtual Machines as well as HA for Hosts.
+
+#. In a new cluster, CloudStack adds the first primary storage server
+ for you. You can always add more servers later. For an overview of
+ what primary storage is, see About Primary Storage.
+
+ To configure the first primary storage server, enter the following,
+ then click Next:
+
+ - **Name.** The name of the storage device.
+
+ - **Protocol.** For XenServer, choose either NFS, iSCSI, or
+ PreSetup. For KVM, choose NFS, SharedMountPoint,CLVM, or RBD. For
+ vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. The
+ remaining fields in the screen vary depending on what you choose
+ here.
+
+
+Advanced Zone Configuration
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. After you select Advanced in the Add Zone wizard and click Next, you
+ will be asked to enter the following details. Then click Next.
+
+ - **Name.** A name for the zone.
+
+ - **DNS 1 and 2.** These are DNS servers for use by guest VMs in the
+ zone. These DNS servers will be accessed via the public network
+ you will add later. The public IP addresses for the zone must have
+ a route to the DNS server named here.
+
+ - **Internal DNS 1 and Internal DNS 2.** These are DNS servers for
+ use by system VMs in the zone(these are VMs used by CloudStack
+ itself, such as virtual routers, console proxies,and Secondary
+ Storage VMs.) These DNS servers will be accessed via the
+ management traffic network interface of the System VMs. The
+ private IP address you provide for the pods must have a route to
+ the internal DNS server named here.
+
+ - **Network Domain.** (Optional) If you want to assign a special
+ domain name to the guest VM network, specify the DNS suffix.
+
+ - **Guest CIDR.** This is the CIDR that describes the IP addresses
+ in use in the guest virtual networks in this zone. For example,
+ 10.1.1.0/24. As a matter of good practice you should set different
+ CIDRs for different zones. This will make it easier to set up VPNs
+ between networks in different zones.
+
+ - **Hypervisor.** (Introduced in version 3.0.1) Choose the
+ hypervisor for the first cluster in the zone. You can add clusters
+ with different hypervisors later, after you finish adding the
+ zone.
+
+ - **Public.** A public zone is available to all users. A zone that
+ is not public will be assigned to a particular domain. Only users
+ in that domain will be allowed to create guest VMs in this zone.
+
+#. Choose which traffic types will be carried by the physical network.
+
+ The traffic types are management, public, guest, and storage traffic.
+ For more information about the types, roll over the icons to display
+ their tool tips, or see :ref:`about-adv-network-traffic-types`.
+ This screenstarts out with one network already configured. If you have
+ multiple physical networks, you need to add more. Drag and drop traffic
+ types onto a greyed-out network and it will become active. You can move the
+ traffic icons from one network to another; for example, if the
+ default traffic types shown for Network 1 do not match your actual
+ setup, you can move them down. You can also change the network names
+ if desired.
+
+#. (Introduced in version 3.0.1) Assign a network traffic label to each
+ traffic type on each physical network. These labels must match the
+ labels you have already defined on the hypervisor host. To assign
+ each label, click the Edit button under the traffic type icon within
+ each physical network. A popup dialog appears where you can type the
+ label, then click OK.
+
+ These traffic labels will be defined only for the hypervisor selected
+ for the first cluster. For all other hypervisors, the labels can be
+ configured after the zone is created.
+
+ (VMware only) If you have enabled Nexus dvSwitch in the environment,
+ you must specify the corresponding Ethernet port profile names as
+ network traffic label for each traffic type on the physical network.
+ For more information on Nexus dvSwitch, see Configuring a vSphere
+ Cluster with Nexus 1000v Virtual Switch in the Installation Guide. If
+ you have enabled VMware dvSwitch in the environment, you must specify
+ the corresponding Switch name as network traffic label for each
+ traffic type on the physical network. For more information, see
+ Configuring a VMware Datacenter with VMware Distributed Virtual
+ Switch in the Installation Guide.
+
+#. Click Next.
+
+#. Configure the IP range for public Internet traffic. Enter the
+ following details, then click Add. If desired, you can repeat this
+ step to add more public Internet IP ranges. When done, click Next.
+
+ - **Gateway.** The gateway in use for these IP addresses.
+
+ - **Netmask.** The netmask associated with this IP range.
+
+ - **VLAN.** The VLAN that will be used for public traffic.
+
+ - **Start IP/End IP.** A range of IP addresses that are assumed to
+ be accessible from the Internet and will be allocated for access
+ to guest networks.
+
+#. In a new zone, CloudStack adds the first pod for you. You can always
+ add more pods later. For an overview of what a pod is, see :ref:`about-pods`
+
+ To configure the first pod, enter the following, then click Next:
+
+ - **Pod Name.** A name for the pod.
+
+ - **Reserved system gateway.** The gateway for the hosts in that
+ pod.
+
+ - **Reserved system netmask.** The network prefix that defines the
+ pod's subnet. Use CIDR notation.
+
+ - **Start/End Reserved System IP.** The IP range in the management
+ network that CloudStack uses to manage various system VMs, such as
+ Secondary Storage VMs, Console Proxy VMs, and DHCP. For more
+ information, see :ref:`about_system_reserved_ip_addresses`
+#. Specify a range of VLAN IDs to carry guest traffic for each physical
+ network (see VLAN Allocation Example ), then click Next.
+
+#. In a new pod, CloudStack adds the first cluster for you. You can
+ always add more clusters later. For an overview of what a cluster is,
+ see :ref:`about-clusters`
+
+ To configure the first cluster, enter the following, then click Next:
+
+ - **Hypervisor.** (Version 3.0.0 only; in 3.0.1, this field is read
+ only) Choose the type of hypervisor software that all hosts in
+ this cluster will run. If you choose VMware, additional fields
+ appear so you can give information about a vSphere cluster. For
+ vSphere servers, we recommend creating the cluster of hosts in
+ vCenter and then adding the entire cluster to CloudStack. See Add
+ Cluster: vSphere .
+
+ - **Cluster name.** Enter a name for the cluster. This can be text
+ of your choosing and is not used by CloudStack.
+
+#. In a new cluster, CloudStack adds the first host for you. You can
+ always add more hosts later. For an overview of what a host is, see :ref:`about-hosts`.
+
+ .. note::
+ When you deploy CloudStack, the hypervisor host must not have any VMs
+ already running.
+
+ Before you can configure the host, you need to install the hypervisor
+ software on the host. You will need to know which version of the
+ hypervisor software version is supported by CloudStack and what
+ additional configuration is required to ensure the host will work
+ with CloudStack. To find these installation details, see:
+
+ - Citrix XenServer Installation for CloudStack
+
+ - VMware vSphere Installation and Configuration
+
+ - KVM Installation and Configuration
+
+ To configure the first host, enter the following, then click Next:
+
+ - **Host Name.** The DNS name or IP address of the host.
+
+ - **Username.** Usually root.
+
+ - **Password.** This is the password for the user named above (from
+ your XenServer or KVM install).
+
+ - **Host Tags.** (Optional) Any labels that you use to categorize
+ hosts for ease of maintenance. For example, you can set to the
+ cloud's HA tag (set in the ha.tag global configuration parameter)
+ if you want this host to be used only for VMs with the "high
+ availability" feature enabled. For more information, see
+ HA-Enabled Virtual Machines as well as HA for Hosts, both in the
+ Administration Guide.
+
+#. In a new cluster, CloudStack adds the first primary storage server
+ for you. You can always add more servers later. For an overview of
+ what primary storage is, see :ref:`about-primary-storage`
+
+ To configure the first primary storage server, enter the following,
+ then click Next:
+
+ - **Name.** The name of the storage device.
+
+ - **Protocol.** For XenServer, choose either NFS, iSCSI, or
+ PreSetup. For KVM, choose NFS, SharedMountPoint, CLVM, and RBD.
+ For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. The
+ remaining fields in the screen vary depending on what you choose
+ here.
+
+ .. cssclass:: table-striped table-bordered table-hover
+
+ =================== ===========================================================================
+ NFS - **Server.** The IP address or DNS name of the storage device.
+
+ - **Path.** The exported path from the server.
+
+ - **Tags (optional).** The comma-separated list of tags for this
+ storage device. It should be an equivalent set or superset of
+ the tags on your disk offerings.
+
+ iSCSI - **Server.** The IP address or DNS name of the storage device.
+
+ - **Target IQN.** The IQN of the target. For example,
+ iqn.1986-03.com.sun:02:01ec9bb549-1271378984.
+
+ - **Lun.** The LUN number. For example, 3.
+
+ - **Tags (optional).** The comma-separated list of tags for this
+ storage device. It should be an equivalent set or superset of
+ the tags on your disk offerings.
+
+ preSetup - **Server.** The IP address or DNS name of the storage device.
+
+ - **SR Name-Label.** Enter the name-label of the SR that has been
+ set up outside CloudStack.
+
+ - **Tags (optional).** The comma-separated list of tags for this
+ storage device. It should be an equivalent set or superset of
+ the tags on your disk offerings.
+
+ SharedMountPoint - **Path.** The path on each host that is where this primary
+ storage is mounted. For example, "/mnt/primary".
+
+ - **Tags (optional).** The comma-separated list of tags for this
+ storage device. It should be an equivalent set or superset of
+ the tags on your disk offerings.
+
+ VMFS - **Server.** The IP address or DNS name of the vCenter server.
+
+ - **Path.** A combination of the datacenter name and the
+ datastore name. The format is "/" datacenter name "/" datastore
+ name. For example, "/cloud.dc.VM/cluster1datastore".
+
+ - **Tags (optional).** The comma-separated list of tags for this
+ storage device. It should be an equivalent set or superset of
+ the tags on your disk offerings.
+ =================== ===========================================================================
+
+
+ The tag sets on primary storage across clusters in a Zone must be
+ identical. For example, if cluster A provides primary storage that
+ has tags T1 and T2, all other clusters in the Zone must also
+ provide primary storage that has tags T1 and T2.
+
+.. _installing-secondary-storage:
+
+#. In a new zone, CloudStack connects the first secondary storage server for
+ you. For an overview of what secondary storage is, see :ref:`about-secondary-storage`
+
+ Before you can fill out this screen, you need to prepare the
+ secondary storage by setting up NFS shares and installing the latest
+ CloudStack System VM template. See Adding Secondary Storage :
+
+ - **NFS Server.** The IP address of the server or fully qualified
+ domain name of the server.
+
+ - **Path.** The exported path from the server.
+
+#. Click Launch.
+
+
+.. _adding-a-pod:
+
+Adding a Pod
+------------
+
+When you created a new zone, CloudStack adds the first pod for you. You
+can add more pods at any time using the procedure in this section.
+
+#. Log in to the CloudStack UI. See :ref:`log-in-to-ui`.
+
+#. In the left navigation, choose Infrastructure. In Zones, click View
+ More, then click the zone to which you want to add a pod.
+
+#. Click the Compute and Storage tab. In the Pods node of the diagram,
+ click View All.
+
+#. Click Add Pod.
+
+#. Enter the following details in the dialog.
+
+ - **Name.** The name of the pod.
+
+ - **Gateway.** The gateway for the hosts in that pod.
+
+ - **Netmask.** The network prefix that defines the pod's subnet. Use
+ CIDR notation.
+
+ - **Start/End Reserved System IP.** The IP range in the management
+ network that CloudStack uses to manage various system VMs, such as
+ Secondary Storage VMs, Console Proxy VMs, and DHCP. For more
+ information, see System Reserved IP Addresses.
+
+#. Click OK.
+
+
+.. _adding-a-cluster:
+
+Adding a Cluster
+----------------
+
+You need to tell CloudStack about the hosts that it will manage. Hosts
+exist inside clusters, so before you begin adding hosts to the cloud,
+you must add at least one cluster.
+
+
+Add Cluster: KVM or XenServer
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+These steps assume you have already installed the hypervisor on the
+hosts and logged in to the CloudStack UI.
+
+#. In the left navigation, choose Infrastructure. In Zones, click View
+ More, then click the zone in which you want to add the cluster.
+
+#. Click the Compute tab.
+
+#. In the Clusters node of the diagram, click View All.
+
+#. Click Add Cluster.
+
+#. Choose the hypervisor type for this cluster.
+
+#. Choose the pod in which you want to create the cluster.
+
+#. Enter a name for the cluster. This can be text of your choosing and
+ is not used by CloudStack.
+
+#. Click OK.
+
+
+Add Cluster: vSphere
+~~~~~~~~~~~~~~~~~~~~
+
+Host management for vSphere is done through a combination of vCenter and
+the CloudStack admin UI. CloudStack requires that all hosts be in a
+CloudStack cluster, but the cluster may consist of a single host. As an
+administrator you must decide if you would like to use clusters of one
+host or of multiple hosts. Clusters of multiple hosts allow for features
+like live migration. Clusters also require shared storage such as NFS or
+iSCSI.
+
+For vSphere servers, we recommend creating the cluster of hosts in
+vCenter and then adding the entire cluster to CloudStack. Follow these
+requirements:
+
+- Do not put more than 8 hosts in a vSphere cluster
+
+- Make sure the hypervisor hosts do not have any VMs already running
+ before you add them to CloudStack.
+
+To add a vSphere cluster to CloudStack:
+
+#. Create the cluster of hosts in vCenter. Follow the vCenter
+ instructions to do this. You will create a cluster that looks
+ something like this in vCenter.
+
+ |vsphereclient.png: vSphere client|
+
+#. Log in to the UI.
+
+#. In the left navigation, choose Infrastructure. In Zones, click View
+ More, then click the zone in which you want to add the cluster.
+
+#. Click the Compute tab, and click View All on Pods. Choose the pod to
+ which you want to add the cluster.
+
+#. Click View Clusters.
+
+#. Click Add Cluster.
+
+#. In Hypervisor, choose VMware.
+
+#. Provide the following information in the dialog. The fields below
+ make reference to the values from vCenter.
+
+ |addcluster.png: add a cluster|
+
+ - **Cluster Name**: Enter the name of the cluster you created in
+ vCenter. For example, "cloud.cluster.2.2.1"
+
+ - **vCenter Username**: Enter the username that CloudStack should
+ use to connect to vCenter. This user must have all the
+ administrative privileges.
+
+ - **CPU overcommit ratio**: Enter the CPU overcommit ratio for the
+ cluster. The value you enter determines the CPU consumption of
+ each VM in the selected cluster. By increasing the
+ over-provisioning ratio, more resource capacity will be used. If
+ no value is specified, the value is defaulted to 1, which implies
+ no over-provisioning is done.
+
+ - **RAM overcommit ratio**: Enter the RAM overcommit ratio for the
+ cluster. The value you enter determines the memory consumption of
+ each VM in the selected cluster. By increasing the
+ over-provisioning ratio, more resource capacity will be used. If
+ no value is specified, the value is defaulted to 1, which implies
+ no over-provisioning is done.
+
+ - **vCenter Host**: Enter the hostname or IP address of the vCenter
+ server.
+
+ - **vCenter Password**: Enter the password for the user named above.
+
+ - **vCenter Datacenter**: Enter the vCenter datacenter that the
+ cluster is in. For example, "cloud.dc.VM".
+
+ - **Override Public Traffic**: Enable this option to override the
+ zone-wide public traffic for the cluster you are creating.
+
+ - **Public Traffic vSwitch Type**: This option is displayed only if
+ you enable the Override Public Traffic option. Select a desirable
+ switch. If the vmware.use.dvswitch global parameter is true, the
+ default option will be VMware vNetwork Distributed Virtual Switch.
+
+ If you have enabled Nexus dvSwitch in the environment, the
+ following parameters for dvSwitch configuration are displayed:
+
+ - Nexus dvSwitch IP Address: The IP address of the Nexus VSM
+ appliance.
+
+ - Nexus dvSwitch Username: The username required to access the
+ Nexus VSM appliance.
+
+ - Nexus dvSwitch Password: The password associated with the
+ username specified above.
+
+ - **Override Guest Traffic**: Enable this option to override the
+ zone-wide guest traffic for the cluster you are creating.
+
+ - **Guest Traffic vSwitch Type**: This option is displayed only if
+ you enable the Override Guest Traffic option. Select a desirable
+ switch.
+
+ If the vmware.use.dvswitch global parameter is true, the default
+ option will be VMware vNetwork Distributed Virtual Switch.
+
+ If you have enabled Nexus dvSwitch in the environment, the
+ following parameters for dvSwitch configuration are displayed:
+
+ - Nexus dvSwitch IP Address: The IP address of the Nexus VSM
+ appliance.
+
+ - Nexus dvSwitch Username: The username required to access the
+ Nexus VSM appliance.
+
+ - Nexus dvSwitch Password: The password associated with the
+ username specified above.
+
+ - There might be a slight delay while the cluster is provisioned. It
+ will automatically display in the UI.
+
+
+.. _adding-a-host:
+
+Adding a Host
+-------------
+
+#. Before adding a host to the CloudStack configuration, you must first
+ install your chosen hypervisor on the host. CloudStack can manage
+ hosts running VMs under a variety of hypervisors.
+
+ The CloudStack Installation Guide provides instructions on how to
+ install each supported hypervisor and configure it for use with
+ CloudStack. See the appropriate section in the Installation Guide for
+ information about which version of your chosen hypervisor is
+ supported, as well as crucial additional steps to configure the
+ hypervisor hosts for use with CloudStack.
+
+ .. warning::
+ Be sure you have performed the additional CloudStack-specific
+ configuration steps described in the hypervisor installation section for
+ your particular hypervisor.
+
+#. Now add the hypervisor host to CloudStack. The technique to use
+ varies depending on the hypervisor.
+
+ - :ref:`adding-a-host-xenserver-kvm`
+
+ - :ref:`adding-a-host-vsphere`
+
+
+.. _adding-a-host-xenserver-kvm:
+
+Adding a Host (XenServer or KVM)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+XenServer and KVM hosts can be added to a cluster at any time.
+
+
+Requirements for XenServer and KVM Hosts
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. warning::
+ Make sure the hypervisor host does not have any VMs already running before
+ you add it to CloudStack.
+
+Configuration requirements:
+
+- Each cluster must contain only hosts with the identical hypervisor.
+
+- For XenServer, do not put more than 8 hosts in a cluster.
+
+- For KVM, do not put more than 16 hosts in a cluster.
+
+For hardware requirements, see the installation section for your
+hypervisor in the CloudStack Installation Guide.
+
+
+XenServer Host Additional Requirements
+''''''''''''''''''''''''''''''''''''''
+
+If network bonding is in use, the administrator must cable the new host
+identically to other hosts in the cluster.
+
+For all additional hosts to be added to the cluster, run the following
+command. This will cause the host to join the master in a XenServer
+pool.
+
+.. parsed-literal::
+
+ # xe pool-join master-address=[master IP] master-username=root master-password=[your password]
+
+.. note::
+ When copying and pasting a command, be sure the command has pasted as a
+ single line before executing. Some document viewers may introduce unwanted
+ line breaks in copied text.
+
+With all hosts added to the XenServer pool, run the cloud-setup-bond
+script. This script will complete the configuration and setup of the
+bonds on the new hosts in the cluster.
+
+#. Copy the script from the Management Server in
+ /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh
+ to the master host and ensure it is executable.
+
+#. Run the script:
+
+ .. parsed-literal::
+
+ # ./cloud-setup-bonding.sh
+
+
+KVM Host Additional Requirements
+''''''''''''''''''''''''''''''''
+
+- If shared mountpoint storage is in use, the administrator should
+ ensure that the new host has all the same mountpoints (with storage
+ mounted) as the other hosts in the cluster.
+
+- Make sure the new host has the same network configuration (guest,
+ private, and public network) as other hosts in the cluster.
+
+- If you are using OpenVswitch bridges edit the file agent.properties
+ on the KVM host and set the parameter network.bridge.type to
+ openvswitch before adding the host to CloudStack
+
+- If you're using a non-root user to add a KVM host, please add the user to
+ sudoers file:
+
+ .. parsed-literal::
+
+ cloudstack ALL=NOPASSWD: /usr/bin/cloudstack-setup-agent
+ defaults:cloudstack !requiretty
+
+Adding a XenServer or KVM Host
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. If you have not already done so, install the hypervisor software on
+ the host. You will need to know which version of the hypervisor
+ software version is supported by CloudStack and what additional
+ configuration is required to ensure the host will work with
+ CloudStack. To find these installation details, see the appropriate
+ section for your hypervisor in the CloudStack Installation Guide.
+
+#. Log in to the CloudStack UI as administrator.
+
+#. In the left navigation, choose Infrastructure. In Zones, click View
+ More, then click the zone in which you want to add the host.
+
+#. Click the Compute tab. In the Clusters node, click View All.
+
+#. Click the cluster where you want to add the host.
+
+#. Click View Hosts.
+
+#. Click Add Host.
+
+#. Provide the following information.
+
+ - Host Name. The DNS name or IP address of the host.
+
+ - Username. Usually root.
+
+ - Password. This is the password for the user from your XenServer or
+ KVM install).
+
+ - Host Tags (Optional). Any labels that you use to categorize hosts
+ for ease of maintenance. For example, you can set to the cloud's
+ HA tag (set in the ha.tag global configuration parameter) if you
+ want this host to be used only for VMs with the "high
+ availability" feature enabled. For more information, see
+ HA-Enabled Virtual Machines as well as HA for Hosts.
+
+ There may be a slight delay while the host is provisioned. It should
+ automatically display in the UI.
+
+#. Repeat for additional hosts.
+
+
+.. _adding-a-host-vsphere:
+
+Adding a Host (vSphere)
+~~~~~~~~~~~~~~~~~~~~~~~
+
+For vSphere servers, we recommend creating the cluster of hosts in
+vCenter and then adding the entire cluster to CloudStack. See Add
+Cluster: vSphere.
+
+
+.. _add-primary-storage:
+
+Add Primary Storage
+-------------------
+
+System Requirements for Primary Storage
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Hardware requirements:
+
+- Any standards-compliant iSCSI, SMB, or NFS server that is supported
+ by the underlying hypervisor.
+
+- The storage server should be a machine with a large number of disks.
+ The disks should ideally be managed by a hardware RAID controller.
+
+- Minimum required capacity depends on your needs.
+
+When setting up primary storage, follow these restrictions:
+
+- Primary storage cannot be added until a host has been added to the
+ cluster.
+
+- If you do not provision shared primary storage, you must set the
+ global configuration parameter system.vm.local.storage.required to
+ true, or else you will not be able to start VMs.
+
+
+Adding Primary Storage
+~~~~~~~~~~~~~~~~~~~~~~
+
+When you create a new zone, the first primary storage is added as part
+of that procedure. You can add primary storage servers at any time, such
+as when adding a new cluster or adding more servers to an existing
+cluster.
+
+.. warning::
+ When using preallocated storage for primary storage, be sure there is
+ nothing on the storage (ex. you have an empty SAN volume or an empty NFS
+ share). Adding the storage to CloudStack will destroy any existing data.
+
+#. Log in to the CloudStack UI :ref:`log-in-to-ui`.
+
+#. In the left navigation, choose Infrastructure. In Zones, click View
+ More, then click the zone in which you want to add the primary
+ storage.
+
+#. Click the Compute tab.
+
+#. In the Primary Storage node of the diagram, click View All.
+
+#. Click Add Primary Storage.
+
+#. Provide the following information in the dialog. The information
+ required varies depending on your choice in Protocol.
+
+ - **Scope.** Indicate whether the storage is available to all hosts
+ in the zone or only to hosts in a single cluster.
+
+ - **Pod.** (Visible only if you choose Cluster in the Scope field.)
+ The pod for the storage device.
+
+ - **Cluster.** (Visible only if you choose Cluster in the Scope
+ field.) The cluster for the storage device.
+
+ - **Name.** The name of the storage device.
+
+ - **Protocol.** For XenServer, choose either NFS, iSCSI, or
+ PreSetup. For KVM, choose NFS or SharedMountPoint. For vSphere
+ choose either VMFS (iSCSI or FiberChannel) or NFS. For Hyper-V,
+ choose SMB.
+
+ - **Server (for NFS, iSCSI, or PreSetup).** The IP address or DNS
+ name of the storage device.
+
+ - **Server (for VMFS).** The IP address or DNS name of the vCenter
+ server.
+
+ - **Path (for NFS).** In NFS this is the exported path from the
+ server.
+
+ - **Path (for VMFS).** In vSphere this is a combination of the
+ datacenter name and the datastore name. The format is "/"
+ datacenter name "/" datastore name. For example,
+ "/cloud.dc.VM/cluster1datastore".
+
+ - **Path (for SharedMountPoint).** With KVM this is the path on each
+ host that is where this primary storage is mounted. For example,
+ "/mnt/primary".
+
+ - **SMB Username** (for SMB/CIFS): Applicable only if you select
+ SMB/CIFS provider. The username of the account which has the
+ necessary permissions to the SMB shares. The user must be part of
+ the Hyper-V administrator group.
+
+ - **SMB Password** (for SMB/CIFS): Applicable only if you select
+ SMB/CIFS provider. The password associated with the account.
+
+ - **SMB Domain**\ (for SMB/CIFS): Applicable only if you select
+ SMB/CIFS provider. The Active Directory domain that the SMB share
+ is a part of.
+
+ - **SR Name-Label (for PreSetup).** Enter the name-label of the SR
+ that has been set up outside CloudStack.
+
+ - **Target IQN (for iSCSI).** In iSCSI this is the IQN of the
+ target. For example, iqn.1986-03.com.sun:02:01ec9bb549-1271378984.
+
+ - **Lun # (for iSCSI).** In iSCSI this is the LUN number. For
+ example, 3.
+
+ - **Tags (optional).** The comma-separated list of tags for this
+ storage device. It should be an equivalent set or superset of the
+ tags on your disk offerings..
+
+ The tag sets on primary storage across clusters in a Zone must be
+ identical. For example, if cluster A provides primary storage that
+ has tags T1 and T2, all other clusters in the Zone must also provide
+ primary storage that has tags T1 and T2.
+
+#. Click OK.
+
+
+Configuring a Storage Plug-in
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. note::
+ Primary storage that is based on a custom plug-in (ex. SolidFire) must be
+ added through the CloudStack API (described later in this section). There
+ is no support at this time through the CloudStack UI to add this type of
+ primary storage (although most of its features are available through the
+ CloudStack UI).
+
+.. note::
+ The SolidFire storage plug-in for CloudStack is part of the standard
+ CloudStack install. There is no additional work required to add this
+ component.
+
+Adding primary storage that is based on the SolidFire plug-in enables
+CloudStack to provide hard quality-of-service (QoS) guarantees.
+
+When used with Compute or Disk Offerings, an administrator is able to
+build an environment in which a root or data disk that a user creates
+leads to the dynamic creation of a SolidFire volume, which has guaranteed
+performance. Such a SolidFire volume is associated with one (and only
+ever one) CloudStack volume, so performance of the CloudStack volume
+does not vary depending on how heavily other tenants are using the
+system.
+
+The createStoragePool API has been augmented to support plugable storage
+providers. The following is a list of parameters to use when adding
+storage to CloudStack that is based on the SolidFire plug-in:
+
+- command=createStoragePool
+
+- scope=zone
+
+- zoneId=[your zone id]
+
+- name=[name for primary storage]
+
+- hypervisor=Any
+
+- provider=SolidFire
+
+- capacityIops=[whole number of IOPS from the SAN to give to
+ CloudStack]
+
+- capacityBytes=[whole number of bytes from the SAN to give to
+ CloudStack]
+
+The url parameter is somewhat unique in that its value can contain
+additional key/value pairs.
+
+url=[key/value pairs detailed below (values are URL encoded; for
+example, '=' is represented as '%3D')]
+
+- MVIP%3D[Management Virtual IP Address] (can be suffixed with :[port
+ number])
+
+- SVIP%3D[Storage Virtual IP Address] (can be suffixed with :[port
+ number])
+
+- clusterAdminUsername%3D[cluster admin's username]
+
+- clusterAdminPassword%3D[cluster admin's password]
+
+- clusterDefaultMinIops%3D[Min IOPS (whole number) to set for a volume;
+ used if Min IOPS is not specified by administrator or user]
+
+- clusterDefaultMaxIops%3D[Max IOPS (whole number) to set for a volume;
+ used if Max IOPS is not specified by administrator or user]
+
+- clusterDefaultBurstIopsPercentOfMaxIops%3D[Burst IOPS is determined
+ by (Min IOPS \* clusterDefaultBurstIopsPercentOfMaxIops parameter)
+ (can be a decimal value)]
+
+
+.. _add-secondary-storage:
+
+Add Secondary Storage
+---------------------
+
+System Requirements for Secondary Storage
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- NFS storage appliance or Linux NFS server
+
+- SMB/CIFS (Hyper-V)
+
+- (Optional) OpenStack Object Storage (Swift) (see
+ http://swift.openstack.org)
+
+- 100GB minimum capacity
+
+- A secondary storage device must be located in the same zone as the
+ guest VMs it serves.
+
+- Each Secondary Storage server must be available to all hosts in the
+ zone.
+
+
+Adding Secondary Storage
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+When you create a new zone, the first secondary storage is added as part
+of that procedure. You can add secondary storage servers at any time to
+add more servers to an existing zone.
+
+.. warning::
+ Ensure that nothing is stored on the server. Adding the server to
+ CloudStack will destroy any existing data.
+
+#. To prepare for the zone-based Secondary Staging Store, you should
+ have created and mounted an NFS share during Management Server
+ installation. See :ref:`prepare-nfs-shares`.
+
+ If you are using an Hyper-V host, ensure that you have created a SMB
+ share.
+
+#. Make sure you prepared the system VM template during Management
+ Server installation. See `“Prepare the System VM Template”
+ <installation.html#prepare-the-system-vm-template>`_.
+
+#. Log in to the CloudStack UI as root administrator.
+
+#. In the left navigation bar, click Infrastructure.
+
+#. In Secondary Storage, click View All.
+
+#. Click Add Secondary Storage.
+
+#. Fill in the following fields:
+
+ - Name. Give the storage a descriptive name.
+
+ - Provider. Choose S3, Swift, NFS, or CIFS then fill in the related
+ fields which appear. The fields will vary depending on the storage
+ provider; for more information, consult the provider's
+ documentation (such as the S3 or Swift website). NFS can be used
+ for zone-based storage, and the others for region-wide storage.
+ For Hyper-V, select SMB/CIFS.
+
+ .. warning::
+ Heterogeneous Secondary Storage is not supported in Regions. You can
+ use only a single NFS, S3, or Swift account per region.
+
+ - Create NFS Secondary Staging Store. This box must always be
+ checked.
+
+ .. warning::
+ Even if the UI allows you to uncheck this box, do not do so. This
+ checkbox and the three fields below it must be filled in. Even when
+ Swift or S3 is used as the secondary storage provider, an NFS staging
+ storage in each zone is still required.
+
+ - Zone. The zone where the NFS Secondary Staging Store is to be
+ located.
+
+ - **SMB Username**: Applicable only if you select SMB/CIFS provider.
+ The username of the account which has the necessary permissions to
+ the SMB shares. The user must be part of the Hyper-V administrator
+ group.
+
+ - **SMB Password**: Applicable only if you select SMB/CIFS provider.
+ The password associated with the account.
+
+ - **SMB Domain**: Applicable only if you select SMB/CIFS provider.
+ The Active Directory domain that the SMB share is a part of.
+
+ - NFS server. The name of the zone's Secondary Staging Store.
+
+ - Path. The path to the zone's Secondary Staging Store.
+
+
+Adding an NFS Secondary Staging Store for Each Zone
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Every zone must have at least one NFS store provisioned; multiple NFS
+servers are allowed per zone. To provision an NFS Staging Store for a
+zone:
+
+#. Log in to the CloudStack UI as root administrator.
+
+#. In the left navigation bar, click Infrastructure.
+
+#. In Secondary Storage, click View All.
+
+#. In Select View, choose Secondary Staging Store.
+
+#. Click the Add NFS Secondary Staging Store button.
+
+#. Fill out the dialog box fields, then click OK:
+
+ - Zone. The zone where the NFS Secondary Staging Store is to be
+ located.
+
+ - NFS server. The name of the zone's Secondary Staging Store.
+
+ - Path. The path to the zone's Secondary Staging Store.
+
+
+.. _initialize-and-test:
+
+Initialize and Test
+-------------------
+
+After everything is configured, CloudStack will perform its
+initialization. This can take 30 minutes or more, depending on the speed
+of your network. When the initialization has completed successfully, the
+administrator's Dashboard should be displayed in the CloudStack UI.
+
+#. Verify that the system is ready. In the left navigation bar, select
+ Templates. Click on the CentOS 5.5 (64bit) no Gui (KVM) template.
+ Check to be sure that the status is "Download Complete." Do not
+ proceed to the next step until this status is displayed.
+
+#. Go to the Instances tab, and filter by My Instances.
+
+#. Click Add Instance and follow the steps in the wizard.
+
+ #. Choose the zone you just added.
+
+ #. In the template selection, choose the template to use in the VM.
+ If this is a fresh installation, likely only the provided CentOS
+ template is available.
+
+ #. Select a service offering. Be sure that the hardware you have
+ allows starting the selected service offering.
+
+ #. In data disk offering, if desired, add another data disk. This is
+ a second volume that will be available to but not mounted in the
+ guest. For example, in Linux on XenServer you will see /dev/xvdb
+ in the guest after rebooting the VM. A reboot is not required if
+ you have a PV-enabled OS kernel in use.
+
+ #. In default network, choose the primary network for the guest. In a
+ trial installation, you would have only one option here.
+
+ #. Optionally give your VM a name and a group. Use any descriptive
+ text you would like.
+
+ #. Click Launch VM. Your VM will be created and started. It might
+ take some time to download the template and complete the VM
+ startup. You can watch the VM’s progress in the Instances
+ screen.
+
+#. To use the VM, click the View Console button. |ConsoleButton.png:
+ button to launch a console|
+
+ For more information about using VMs, including instructions for how
+ to allow incoming network traffic to the VM, start, stop, and delete
+ VMs, and move a VM from one host to another, see Working With Virtual
+ Machines in the Administrator’s Guide.
+
+Congratulations! You have successfully completed a CloudStack
+Installation.
+
+If you decide to grow your deployment, you can add more hosts, primary
+storage, zones, pods, and clusters.
+
+.. _configuration-parameters:
+
+Configuration Parameters
+------------------------
+
+About Configuration Parameters
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack provides a variety of settings you can use to set limits,
+configure features, and enable or disable features in the cloud. Once
+your Management Server is running, you might need to set some of these
+configuration parameters, depending on what optional features you are
+setting up. You can set default values at the global level, which will
+be in effect throughout the cloud unless you override them at a lower
+level. You can make local settings, which will override the global
+configuration parameter values, at the level of an account, zone,
+cluster, or primary storage.
+
+The documentation for each CloudStack feature should direct you to the
+names of the applicable parameters. The following table shows a few of
+the more useful parameters.
+
+.. cssclass:: table-striped table-bordered table-hover
+
+================================= ================================================================================
+Field Value
+================================= ================================================================================
+management.network.cidr A CIDR that describes the network that the management CIDRs reside on. This variable must be set for deployments that use vSphere. It is recommended to be set for other deployments as well. Example: 192.168.3.0/24.
+xen.setup.multipath For XenServer nodes, this is a true/false variable that instructs CloudStack to enable iSCSI multipath on the XenServer Hosts when they are added. This defaults to false. Set it to true if you would like CloudStack to enable multipath.If this is true for a NFS-based deployment multipath will still be enabled on the XenServer host. However, this does not impact NFS operation and is harmless.
+secstorage.allowed.internal.sites This is used to protect your internal network from rogue attempts to download arbitrary files using the template download feature. This is a comma-separated list of CIDRs. If a requested URL matches any of these CIDRs the Secondary Storage VM will use the private network interface to fetch the URL. Other URLs will go through the public interface. We suggest you set this to 1 or 2 hardened internal machines where you keep your templates. For example, set it to 192.168.1.66/32.
+use.local.storage Determines whether CloudStack will use storage that is local to the Host for data disks, templates, and snapshots. By default CloudStack will not use this storage. You should change this to true if you want to use local storage and you understand the reliability and feature drawbacks to choosing local storage.
+host This is the IP address of the Management Server. If you are using multiple Management Servers you should enter a load balanced IP address that is reachable via the private network.
+default.page.size Maximum number of items per page that can be returned by a CloudStack API command. The limit applies at the cloud level and can vary from cloud to cloud. You can override this with a lower value on a particular API call by using the page and pagesize API command parameters. For more information, see the Developer's Guide. Default: 500.
+ha.tag The label you want to use throughout the cloud to designate certain hosts as dedicated HA hosts. These hosts will be used only for HA-enabled VMs that are restarting due to the failure of another host. For example, you could set this to ha\_host. Specify the ha.tag value asa host tag when you add a new host to the cloud.
+vmware.vcenter.session.timeout Determines the vCenter session timeout value by using this parameter. The default value is 20 minutes. Increase the timeout value to avoid timeout errors in VMware deployments because certain VMware operations take more than 20 minutes.
+================================= ================================================================================
+
+
+Setting Global Configuration Parameters
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Use the following steps to set global configuration parameters. These
+values will be the defaults in effect throughout your CloudStack
+deployment.
+
+#. Log in to the UI as administrator.
+
+#. In the left navigation bar, click Global Settings.
+
+#. In Select View, choose one of the following:
+
+ - Global Settings. This displays a list of the parameters with brief
+ descriptions and current values.
+
+ - Hypervisor Capabilities. This displays a list of hypervisor
+ versions with the maximum number of guests supported for each.
+
+#. Use the search box to narrow down the list to those you are
+ interested in.
+
+#. In the Actions column, click the Edit icon to modify a value. If you
+ are viewing Hypervisor Capabilities, you must click the name of the
+ hypervisor first to display the editing screen.
+
+
+Setting Local Configuration Parameters
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Use the following steps to set local configuration parameters for an
+account, zone, cluster, or primary storage. These values will override
+the global configuration settings.
+
+#. Log in to the UI as administrator.
+
+#. In the left navigation bar, click Infrastructure or Accounts,
+ depending on where you want to set a value.
+
+#. Find the name of the particular resource that you want to work with.
+ For example, if you are in Infrastructure, click View All on the
+ Zones, Clusters, or Primary Storage area.
+
+#. Click the name of the resource where you want to set a limit.
+
+#. Click the Settings tab.
+
+#. Use the search box to narrow down the list to those you are
+ interested in.
+
+#. In the Actions column, click the Edit icon to modify a value.
+
+
+Granular Global Configuration Parameters
+----------------------------------------
+
+The following global configuration parameters have been made more
+granular. The parameters are listed under three different scopes:
+account, cluster, and zone.
+
+.. cssclass:: table-striped table-bordered table-hover
+
+======== ========================================================= ======================================================================================================================================
+Field Field Value
+======== ========================================================= ======================================================================================================================================
+account remote.access.vpn.client.iprange The range of IPs to be allocated to remotely access the VPN clients. The first IP in the range is used by the VPN server.
+account allow.public.user.templates If false, users will not be able to create public templates.
+account use.system.public.ips If true and if an account has one or more dedicated public IP ranges, IPs are acquired from the system pool after all the IPs dedicated to the account have been consumed.
+account use.system.guest.vlans If true and if an account has one or more dedicated guest VLAN ranges, VLANs are allocated from the system pool after all the VLANs dedicated to the account have been consumed.
+cluster cluster.storage.allocated.capacity.notificationthreshold The percentage, as a value between 0 and 1, of allocated storage utilization above which alerts are sent that the storage is below the threshold.
+cluster cluster.storage.capacity.notificationthreshold The percentage, as a value between 0 and 1, of storage utilization above which alerts are sent that the available storage is below the threshold.
+cluster cluster.cpu.allocated.capacity.notificationthreshold The percentage, as a value between 0 and 1, of cpu utilization above which alerts are sent that the available CPU is below the threshold.
+cluster cluster.memory.allocated.capacity.notificationthreshold The percentage, as a value between 0 and 1, of memory utilization above which alerts are sent that the available memory is below the threshold.
+cluster cluster.cpu.allocated.capacity.disablethreshold The percentage, as a value between 0 and 1, of CPU utilization above which allocators will disable that cluster from further usage. Keep the corresponding notification threshold lower than this value to be notified beforehand.
+cluster cluster.memory.allocated.capacity.disablethreshold The percentage, as a value between 0 and 1, of memory utilization above which allocators will disable that cluster from further usage. Keep the corresponding notification threshold lower than this value to be notified beforehand.
+cluster cpu.overprovisioning.factor Used for CPU over-provisioning calculation; the available CPU will be
+ the mathematical product of actualCpuCapacity and cpu.overprovisioning.factor.
+cluster mem.overprovisioning.factor Used for memory over-provisioning calculation.
+cluster vmware.reserve.cpu Specify whether or not to reserve CPU when not over-provisioning; In case of CPU over-provisioning, CPU is always reserved.
+cluster vmware.reserve.mem Specify whether or not to reserve memory when not over-provisioning; In case of memory over-provisioning memory is always reserved.
+zone pool.storage.allocated.capacity.disablethreshold The percentage, as a value between 0 and 1, of allocated storage utilization above which allocators will disable that pool because the
+ available allocated storage is below the threshold.
+zone pool.storage.capacity.disablethreshold The percentage, as a value between 0 and 1, of storage utilization above which allocators will disable the pool because the available storage capacity is below the threshold.
+zone storage.overprovisioning.factor Used for storage over-provisioning calculation; available storage will be the mathematical product of actualStorageSize and storage.overprovisioning.factor.
+zone network.throttling.rate Default data transfer rate in megabits per second allowed in a network.
+zone guest.domain.suffix Default domain name for VMs inside a virtual networks with a router.
+zone router.template.xen Name of the default router template on Xenserver.
+zone router.template.kvm Name of the default router template on KVM.
+zone router.template.vmware Name of the default router template on VMware.
+zone enable.dynamic.scale.vm Enable or diable dynamically scaling of a VM.
+zone use.external.dns Bypass internal DNS, and use the external DNS1 and DNS2
+zone blacklisted.routes Routes that are blacklisted cannot be used for creating static routes for a VPC Private Gateway.
+======== ========================================================= ======================================================================================================================================
+
+
+.. |provisioning-overview.png: Conceptual overview of a basic deployment| image:: /_static/images/provisioning-overview.png
+.. |vsphereclient.png: vSphere client| image:: /_static/images/vsphere-client.png
+.. |addcluster.png: add a cluster| image:: /_static/images/add-cluster.png
+.. |ConsoleButton.png: button to launch a console| image:: /_static/images/console-icon.png
diff --git a/source/installguide/encryption.rst b/source/installguide/encryption.rst
new file mode 100644
index 0000000..dae4375
--- /dev/null
+++ b/source/installguide/encryption.rst
@@ -0,0 +1,132 @@
+.. 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.
+
+.. _about-password-key-encryption:
+
+About Password and Key Encryption
+---------------------------------
+
+CloudStack stores several sensitive passwords and secret keys that are
+used to provide security. These values are always automatically
+encrypted:
+
+- Database secret key
+
+- Database password
+
+- SSH keys
+
+- Compute node root password
+
+- VPN password
+
+- User API secret key
+
+- VNC password
+
+CloudStack uses the Java Simplified Encryption (JASYPT) library. The
+data values are encrypted and decrypted using a database secret key,
+which is stored in one of CloudStack’s internal properties files along
+with the database password. The other encrypted values listed above,
+such as SSH keys, are in the CloudStack internal database.
+
+Of course, the database secret key itself can not be stored in the open
+– it must be encrypted. How then does CloudStack read it? A second
+secret key must be provided from an external source during Management
+Server startup. This key can be provided in one of two ways: loaded from
+a file or provided by the CloudStack administrator. The CloudStack
+database has a configuration setting that lets it know which of these
+methods will be used. If the encryption type is set to "file," the key
+must be in a file in a known location. If the encryption type is set to
+"web," the administrator runs the utility
+com.cloud.utils.crypt.EncryptionSecretKeySender, which relays the key to
+the Management Server over a known port.
+
+The encryption type, database secret key, and Management Server secret
+key are set during CloudStack installation. They are all parameters to
+the CloudStack database setup script (cloudstack-setup-databases). The
+default values are file, password, and password. It is, of course,
+highly recommended that you change these to more secure keys.
+
+
+Changing the Default Password Encryption
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Passwords are encoded when creating or updating users. CloudStack allows
+you to determine the default encoding and authentication mechanism for
+admin and user logins. Two new configurable lists have been
+introduced—userPasswordEncoders and userAuthenticators.
+userPasswordEncoders allows you to configure the order of preference for
+encoding passwords, whereas userAuthenticators allows you to configure
+the order in which authentication schemes are invoked to validate user
+passwords.
+
+Additionally, the plain text user authenticator has been modified not to
+convert supplied passwords to their md5 sums before checking them with
+the database entries. It performs a simple string comparison between
+retrieved and supplied login passwords instead of comparing the
+retrieved md5 hash of the stored password against the supplied md5 hash
+of the password because clients no longer hash the password. The
+following method determines what encoding scheme is used to encode the
+password supplied during user creation or modification.
+
+When a new user is created, the user password is encoded by using the
+first valid encoder loaded as per the sequence specified in the
+``UserPasswordEncoders`` property in the ``ComponentContext.xml`` or
+``nonossComponentContext.xml`` files. The order of authentication
+schemes is determined by the ``UserAuthenticators`` property in the same
+files. If Non-OSS components, such as VMware environments, are to be
+deployed, modify the ``UserPasswordEncoders`` and ``UserAuthenticators``
+lists in the ``nonossComponentContext.xml`` file, for OSS environments,
+such as XenServer or KVM, modify the ``ComponentContext.xml`` file. It
+is recommended to make uniform changes across both the files. When a new
+authenticator or encoder is added, you can add them to this list. While
+doing so, ensure that the new authenticator or encoder is specified as a
+bean in both these files. The administrator can change the ordering of
+both these properties as preferred to change the order of schemes.
+Modify the following list properties available in
+``client/tomcatconf/nonossComponentContext.xml.in`` or
+``client/tomcatconf/componentContext.xml.in`` as applicable, to the
+desired order:
+
+.. sourcecode:: xml
+
+ <property name="UserAuthenticators">
+ <list>
+ <ref bean="SHA256SaltedUserAuthenticator"/>
+ <ref bean="MD5UserAuthenticator"/>
+ <ref bean="LDAPUserAuthenticator"/>
+ <ref bean="PlainTextUserAuthenticator"/>
+ </list>
+ </property>
+ <property name="UserPasswordEncoders">
+ <list>
+ <ref bean="SHA256SaltedUserAuthenticator"/>
+ <ref bean="MD5UserAuthenticator"/>
+ <ref bean="LDAPUserAuthenticator"/>
+ <ref bean="PlainTextUserAuthenticator"/>
+ </list>
+ </property>
+
+In the above default ordering, SHA256Salt is used first for
+``UserPasswordEncoders``. If the module is found and encoding returns a
+valid value, the encoded password is stored in the user table's password
+column. If it fails for any reason, the MD5UserAuthenticator will be
+tried next, and the order continues. For ``UserAuthenticators``,
+SHA256Salt authentication is tried first. If it succeeds, the user is
+logged into the Management server. If it fails, md5 is tried next, and
+attempts continues until any of them succeeds and the user logs in . If
+none of them works, the user is returned an invalid credential message.
+
diff --git a/source/installguide/hypervisor/hyperv.rst b/source/installguide/hypervisor/hyperv.rst
new file mode 100644
index 0000000..4763461
--- /dev/null
+++ b/source/installguide/hypervisor/hyperv.rst
@@ -0,0 +1,268 @@
+.. 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.
+
+
+Host Hyper-V Installation
+-------------------------
+
+If you want to use Hyper-V hypervisor to run guest virtual machines,
+install Hyper-V on the hosts in your cloud. The instructions in this
+section doesn't duplicate Hyper-V Installation documentation. It
+provides the CloudStack-specific steps that are needed to prepare a
+Hyper-V host to work with CloudStack.
+
+
+System Requirements for Hyper-V Hypervisor Hosts
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+
+Supported Operating Systems for Hyper-V Hosts
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+- Windows Server 2012 R2 Standard
+
+- Windows Server 2012 R2 Datacenter
+
+- Hyper-V 2012 R2
+
+
+Minimum System Requirements for Hyper-V Hosts
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+- 1.4 GHz 64-bit processor with hardware-assisted virtualization.
+
+- 800 MB of RAM
+
+- 32 GB of disk space
+
+- Gigabit (10/100/1000baseT) Ethernet adapter
+
+
+Supported Storage
+^^^^^^^^^^^^^^^^^
+
+- Primary Storage: Server Message Block (SMB) Version 3, Local
+
+- Secondary Storage: SMB
+
+
+Preparation Checklist for Hyper-V
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+For a smoother installation, gather the following information before you
+start:
+
+.. cssclass:: table-striped table-bordered table-hover
+
++------------+----------+------------------------------------------------------+
+| Hyper-V | Value | Description |
+| Requiremen | | |
+| ts | | |
++============+==========+======================================================+
+| Server | Hyper-V | After the Windows Server 2012 R2 installation, |
+| Roles | | ensure that Hyper-V is selected from Server Roles. |
+| | | For more information, see `Installing |
+| | | Hyper-V <http://technet.microsoft.com/en-us/library/ |
+| | | jj134187.aspx#BKMK_Step2>`__. |
++------------+----------+------------------------------------------------------+
+| Share | New | Ensure that folders are created for Primary and |
+| Location | folders | Secondary storage. The SMB share and the hosts |
+| | in the | should be part of the same domain. |
+| | /Share | |
+| | director | If you are using Windows SMB share, the location of |
+| | y | the file share for the Hyper-V deployment will be |
+| | | the new folder created in the \\Shares on the |
+| | | selected volume. You can create sub-folders for both |
+| | | PRODUCT Primary and Secondary storage within the |
+| | | share location. When you select the profile for the |
+| | | file shares, ensure that you select SMB Share |
+| | | -Applications. This creates the file shares with |
+| | | settings appropriate for Hyper-V. |
++------------+----------+------------------------------------------------------+
+| Domain and | | Hosts should be part of the same Active Directory |
+| Hosts | | domain. |
++------------+----------+------------------------------------------------------+
+| Hyper-V | Full | Full control on the SMB file share. |
+| Users | control | |
++------------+----------+------------------------------------------------------+
+| Virtual | | If you are using Hyper-V 2012 R2, manually create an |
+| Switch | | external virtual switch before adding the host to |
+| | | PRODUCT. If the Hyper-V host is added to the Hyper-V |
+| | | manager, select the host, then click Virtual Switch |
+| | | Manager, then New Virtual Switch. In the External |
+| | | Network, select the desired NIC adapter and click |
+| | | Apply. |
+| | | |
+| | | If you are using Windows 2012 R2, virtual switch is |
+| | | created automatically. |
++------------+----------+------------------------------------------------------+
+| Virtual | | Take a note of the name of the virtual switch. You |
+| Switch | | need to specify that when configuring PRODUCT |
+| Name | | physical network labels. |
++------------+----------+------------------------------------------------------+
+| Hyper-V | | - Add the Hyper-V domain users to the Hyper-V |
+| Domain | | Administrators group. |
+| Users | | |
+| | | - A domain user should have full control on the SMB |
+| | | share that is exported for primary and secondary |
+| | | storage. |
+| | | |
+| | | - This domain user should be part of the Hyper-V |
+| | | Administrators and Local Administrators group on |
+| | | the Hyper-V hosts that are to be managed by |
+| | | PRODUCT. |
+| | | |
+| | | - The Hyper-V Agent service runs with the |
+| | | credentials of this domain user account. |
+| | | |
+| | | - Specify the credential of the domain user while |
+| | | adding a host to PRODUCT so that it can manage |
+| | | it. |
+| | | |
+| | | - Specify the credential of the domain user while |
+| | | adding a shared SMB primary or secondary storage. |
+| | | |
++------------+----------+------------------------------------------------------+
+| Migration | Migratio | Enable Migration. |
+| | n | |
++------------+----------+------------------------------------------------------+
+| Migration | Delegati | If you want to use Live Migration, enable |
+| | on | Delegation. Enable the following services of other |
+| | | hosts participating in Live Migration: CIFS and |
+| | | Microsoft Virtual System Migration Service. |
++------------+----------+------------------------------------------------------+
+| Migration | Kerberos | Enable Kerberos for Live Migration. |
++------------+----------+------------------------------------------------------+
+| Network | Allow | Allow access for Dial-in connections. |
+| Access | access | |
+| Permission | | |
+| for | | |
+| Dial-in | | |
++------------+----------+------------------------------------------------------+
+
+
+Hyper-V Installation Steps
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. Download the operating system from `Windows Server 2012 R2
+ <http://technet.microsoft.com/en-us/windowsserver/hh534429>`_.
+
+#. Install it on the host as given in `Install and Deploy Windows Server 2012
+ R2 <http://technet.microsoft.com/library/hh831620>`_.
+
+#. Post installation, ensure that you enable Hyper-V role in the server.
+
+#. If no Active Directory domain exists in your deployment, create one
+ and add users to the domain.
+
+#. In the Active Directory domain, ensure that all the Hyper-v hosts are
+ added so that all the hosts are part of the domain.
+
+#. Add the domain user to the following groups on the Hyper-V host:
+ Hyper-V Administrators and Local Administrators.
+
+
+Installing the CloudStack Agent on a Hyper-V Host
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The Hyper-V Agent helps CloudStack perform operations on the Hyper-V
+hosts. This Agent communicates with the Management Server and controls
+all the instances on the host. Each Hyper-V host must have the Hyper-V
+Agent installed on it for successful interaction between the host and
+CloudStack. The Hyper-V Agent runs as a Windows service. Install the
+Agent on each host using the following steps.
+
+CloudStack Management Server communicates with Hyper-V Agent by using
+HTTPS. For secure communication between the Management Server and the
+host, install a self-signed certificate on port 8250.
+
+.. note::
+ The Agent installer automatically perform this operation. You have not
+ selected this option during the Agent installation, it can also be done
+ manually as given in step 1.
+
+#. Create and add a self-signed SSL certificate on port 8250:
+
+ #. Create A self-signed SSL certificate:
+
+ .. parsed-literal::
+
+ # New-SelfSignedCertificate -DnsName apachecloudstack -CertStoreLocation Cert:\LocalMachine\My
+
+ This command creates the self-signed certificate and add that to
+ the certificate store ``LocalMachine\My``.
+
+ #. Add the created certificate to port 8250 for https communication:
+
+ .. parsed-literal::
+
+ netsh http add sslcert ipport=0.0.0.0:8250 certhash=<thumbprint> appid="{727beb1c-6e7c-49b2-8fbd-f03dbe481b08}"
+
+ Thumbprint is the thumbprint of the certificate you created.
+
+#. Build the CloudStack Agent for Hyper-V as given in `Building CloudStack
+ Hyper-V Agent <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Creating+Hyperv+Agent+Installer>`__.
+
+#. As an administrator, run the installer.
+
+#. Provide the Hyper-V admin credentials when prompted.
+
+ When the agent installation is finished, the agent runs as a service
+ on the host machine.
+
+
+Physical Network Configuration for Hyper-V
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+You should have a plan for how the hosts will be cabled and which
+physical NICs will carry what types of traffic. By default, CloudStack
+will use the device that is used for the default route.
+
+If you are using Hyper-V 2012 R2, manually create an external virtual
+switch before adding the host to CloudStack. If the Hyper-V host is
+added to the Hyper-V manager, select the host, then click Virtual Switch
+Manager, then New Virtual Switch. In the External Network, select the
+desired NIC adapter and click Apply.
+
+If you are using Windows 2012 R2, virtual switch is created
+automatically.
+
+
+Storage Preparation for Hyper-V (Optional)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack allows administrators to set up shared Primary Storage and
+Secondary Storage that uses SMB.
+
+#. Create a SMB storage and expose it over SMB Version 3.
+
+ For more information, see `Deploying Hyper-V over SMB
+ <http://technet.microsoft.com/en-us/library/jj134187.aspx>`_.
+
+ You can also create and export SMB share using Windows. After the
+ Windows Server 2012 R2 installation, select File and Storage Services
+ from Server Roles to create an SMB file share. For more information,
+ see `Creating an SMB File Share Using Server Manager
+ <http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step3>`_.
+
+#. Add the SMB share to the Active Directory domain.
+
+ The SMB share and the hosts managed by CloudStack need to be in the
+ same domain. However, the storage should be accessible from the
+ Management Server with the domain user privileges.
+
+#. While adding storage to CloudStack, ensure that the correct domain,
+ and credentials are supplied. This user should be able to access the
+ storage from the Management Server.
diff --git a/source/installguide/hypervisor/kvm.rst b/source/installguide/hypervisor/kvm.rst
new file mode 100644
index 0000000..1ea8eec
--- /dev/null
+++ b/source/installguide/hypervisor/kvm.rst
@@ -0,0 +1,1112 @@
+.. 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.
+
+
+Host KVM Installation
+---------------------
+
+System Requirements for KVM Hypervisor Hosts
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+KVM is included with a variety of Linux-based operating systems.
+Although you are not required to run these distributions, the following
+are recommended:
+
+- CentOS / RHEL: 7.X
+
+- Ubuntu: 14.04
+
+The main requirement for KVM hypervisors is the libvirt and Qemu
+version. No matter what Linux distribution you are using, make sure the
+following requirements are met:
+
+- libvirt: 1.2.0 or higher
+
+- Qemu/KVM: 2.0 or higher
+
+The default bridge in CloudStack is the Linux native bridge
+implementation (bridge module). CloudStack includes an option to work
+with OpenVswitch, the requirements are listed below
+
+- libvirt: 1.2.0 or higher
+
+- openvswitch: 1.7.1 or higher
+
+In addition, the following hardware requirements apply:
+
+- Within a single cluster, the hosts must be of the same distribution
+ version.
+
+- All hosts within a cluster must be homogenous. The CPUs must be of
+ the same type, count, and feature flags.
+
+- Must support HVM (Intel-VT or AMD-V enabled)
+
+- 64-bit x86 CPU (more cores results in better performance)
+
+- 4 GB of memory
+
+- At least 1 NIC
+
+- When you deploy CloudStack, the hypervisor host must not have any VMs
+ already running. These will be destroy by CloudStack.
+
+
+KVM Installation Overview
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If you want to use the Linux Kernel Virtual Machine (KVM) hypervisor to
+run guest virtual machines, install KVM on the host(s) in your cloud.
+The material in this section doesn't duplicate KVM installation docs. It
+provides the CloudStack-specific steps that are needed to prepare a KVM
+host to work with CloudStack.
+
+.. warning::
+ Before continuing, make sure that you have applied the latest updates to
+ your host.
+
+.. warning::
+ It is NOT recommended to run services on this host not controlled by
+ CloudStack.
+
+The procedure for installing a KVM Hypervisor Host is:
+
+#. Prepare the Operating System
+
+#. Install and configure libvirt
+
+#. Configure Security Policies (AppArmor and SELinux)
+
+#. Install and configure the Agent
+
+
+Prepare the Operating System
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The OS of the Host must be prepared to host the CloudStack Agent and run
+KVM instances.
+
+#. Log in to your OS as root.
+
+#. Check for a fully qualified hostname.
+
+ .. parsed-literal::
+
+ $ hostname --fqdn
+
+ This should return a fully qualified hostname such as
+ "kvm1.lab.example.org". If it does not, edit /etc/hosts so that it
+ does.
+
+#. Make sure that the machine can reach the Internet.
+
+ .. parsed-literal::
+
+ $ ping www.cloudstack.org
+
+#. Turn on NTP for time synchronization.
+
+ .. note::
+ NTP is required to synchronize the clocks of the servers in your
+ cloud. Unsynchronized clocks can cause unexpected problems.
+
+ #. Install NTP
+
+ .. parsed-literal::
+
+ $ yum install ntp
+
+ .. parsed-literal::
+
+ $ apt-get install openntpd
+
+#. Repeat all of these steps on every hypervisor host.
+
+
+Install and configure the Agent
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To manage KVM instances on the host CloudStack uses a Agent. This Agent
+communicates with the Management server and controls all the instances
+on the host.
+
+First we start by installing the agent:
+
+In RHEL or CentOS:
+
+.. parsed-literal::
+
+ $ yum install cloudstack-agent
+
+In Ubuntu:
+
+.. parsed-literal::
+
+ $ apt-get install cloudstack-agent
+
+The host is now ready to be added to a cluster. This is covered in a
+later section, see :ref:`adding-a-host`. It is
+recommended that you continue to read the documentation before adding
+the host!
+
+If you're using a non-root user to add the KVM host, please add the user to
+sudoers file:
+
+.. parsed-literal::
+
+ cloudstack ALL=NOPASSWD: /usr/bin/cloudstack-setup-agent
+ defaults:cloudstack !requiretty
+
+
+Configure CPU model for KVM guest (Optional)
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+In additional,the CloudStack Agent allows host administrator to control
+the guest CPU model which is exposed to KVM instances. By default, the
+CPU model of KVM instance is likely QEMU Virtual CPU version x.x.x with
+least CPU features exposed. There are a couple of reasons to specify the
+CPU model:
+
+- To maximise performance of instances by exposing new host CPU
+ features to the KVM instances;
+
+- To ensure a consistent default CPU across all machines,removing
+ reliance of variable QEMU defaults;
+
+For the most part it will be sufficient for the host administrator to
+specify the guest CPU config in the per-host configuration file
+(/etc/cloudstack/agent/agent.properties). This will be achieved by
+introducing following configuration parameters:
+
+.. parsed-literal::
+
+ guest.cpu.mode=custom|host-model|host-passthrough
+ guest.cpu.model=from /usr/share/libvirt/cpu_map.xml(only valid when guest.cpu.mode=custom)
+ guest.cpu.features=vmx ept aes smx mmx ht (space separated list of cpu flags to apply)
+
+There are three choices to fulfill the cpu model changes:
+
+#. **custom:** you can explicitly specify one of the supported named
+ model in /usr/share/libvirt/cpu\_map.xml
+
+#. **host-model:** libvirt will identify the CPU model in
+ /usr/share/libvirt/cpu\_map.xml which most closely matches the host,
+ and then request additional CPU flags to complete the match. This
+ should give close to maximum functionality/performance, which
+ maintaining good reliability/compatibility if the guest is migrated
+ to another host with slightly different host CPUs.
+
+#. **host-passthrough:** libvirt will tell KVM to passthrough the host
+ CPU with no modifications. The difference to host-model, instead of
+ just matching feature flags, every last detail of the host CPU is
+ matched. This gives absolutely best performance, and can be important
+ to some apps which check low level CPU details, but it comes at a
+ cost with respect to migration: the guest can only be migrated to an
+ exactly matching host CPU.
+
+Here are some examples:
+
+- custom
+
+ .. parsed-literal::
+
+ guest.cpu.mode=custom
+ guest.cpu.model=SandyBridge
+
+- host-model
+
+ .. parsed-literal::
+
+ guest.cpu.mode=host-model
+
+- host-passthrough
+
+ .. parsed-literal::
+
+ guest.cpu.mode=host-passthrough
+ guest.cpu.features=vmx
+
+.. note::
+ host-passthrough may lead to migration failure,if you have this problem,
+ you should use host-model or custom. guest.cpu.features will force cpu features
+ as a required policy so make sure to put only those features that are provided
+ by the host CPU.
+
+Install and Configure libvirt
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack uses libvirt for managing virtual machines. Therefore it is
+vital that libvirt is configured correctly. Libvirt is a dependency of
+cloudstack-agent and should already be installed.
+
+#. In order to have live migration working libvirt has to listen for
+ unsecured TCP connections. We also need to turn off libvirts attempt
+ to use Multicast DNS advertising. Both of these settings are in
+ ``/etc/libvirt/libvirtd.conf``
+
+ Set the following parameters:
+
+ .. parsed-literal::
+
+ listen_tls = 0
+
+ .. parsed-literal::
+
+ listen_tcp = 1
+
+ .. parsed-literal::
+
+ tcp_port = "16509"
+
+ .. parsed-literal::
+
+ auth_tcp = "none"
+
+ .. parsed-literal::
+
+ mdns_adv = 0
+
+#. Turning on "listen\_tcp" in libvirtd.conf is not enough, we have to
+ change the parameters as well:
+
+ On RHEL or CentOS modify ``/etc/sysconfig/libvirtd``:
+
+ Uncomment the following line:
+
+ .. parsed-literal::
+
+ #LIBVIRTD_ARGS="--listen"
+
+ On Ubuntu 14.04: modify ``/etc/default/libvirt-bin``
+
+ Add "-l" to the following line
+
+ .. parsed-literal::
+
+ libvirtd_opts="-d"
+
+ so it looks like:
+
+ .. parsed-literal::
+
+ libvirtd_opts="-d -l"
+
+ And modify ``/etc/init/libvirt-bin.conf``
+
+ Add "-l" to the following line
+
+ .. parsed-literal::
+
+ env libvirtd_opts="-d"
+
+ so it looks like:
+
+ .. parsed-literal::
+
+ env libvirtd_opts="-d -l"
+
+ On Ubuntu 16.04: just modify ``/etc/init/libvirt-bin.conf``
+
+ Add "-l" to the following line
+
+ .. parsed-literal::
+
+ env libvirtd_opts="-d"
+
+ so it looks like:
+
+ .. parsed-literal::
+
+ env libvirtd_opts="-d -l"
+
+
+
+
+#. Restart libvirt
+
+ In RHEL or CentOS:
+
+ .. parsed-literal::
+
+ $ service libvirtd restart
+
+ In Ubuntu:
+
+ .. parsed-literal::
+
+ $ service libvirt-bin restart
+
+
+Configure the Security Policies
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack does various things which can be blocked by security
+mechanisms like AppArmor and SELinux. These have to be disabled to
+ensure the Agent has all the required permissions.
+
+#. Configure SELinux (RHEL and CentOS)
+
+ #. Check to see whether SELinux is installed on your machine. If not,
+ you can skip this section.
+
+ In RHEL or CentOS, SELinux is installed and enabled by default.
+ You can verify this with:
+
+ .. parsed-literal::
+
+ $ rpm -qa | grep selinux
+
+ #. Set the SELINUX variable in ``/etc/selinux/config`` to
+ "permissive". This ensures that the permissive setting will be
+ maintained after a system reboot.
+
+ In RHEL or CentOS:
+
+ .. parsed-literal::
+
+ $ vi /etc/selinux/config
+
+ Change the following line
+
+ .. parsed-literal::
+
+ SELINUX=enforcing
+
+ to this
+
+ .. parsed-literal::
+
+ SELINUX=permissive
+
+ #. Then set SELinux to permissive starting immediately, without
+ requiring a system reboot.
+
+ .. parsed-literal::
+
+ $ setenforce permissive
+
+#. Configure Apparmor (Ubuntu)
+
+ #. Check to see whether AppArmor is installed on your machine. If
+ not, you can skip this section.
+
+ In Ubuntu AppArmor is installed and enabled by default. You can
+ verify this with:
+
+ .. parsed-literal::
+
+ $ dpkg --list 'apparmor'
+
+ #. Disable the AppArmor profiles for libvirt
+
+ .. parsed-literal::
+
+ $ ln -s /etc/apparmor.d/usr.sbin.libvirtd /etc/apparmor.d/disable/
+
+ .. parsed-literal::
+
+ $ ln -s /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper /etc/apparmor.d/disable/
+
+ .. parsed-literal::
+
+ $ apparmor_parser -R /etc/apparmor.d/usr.sbin.libvirtd
+
+ .. parsed-literal::
+
+ $ apparmor_parser -R /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper
+
+
+Configuring the Networking
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. warning::
+ This is a very important section, please make sure you read this thoroughly.
+
+.. note::
+ This section details how to configure bridges using the native
+ implementation in Linux. Please refer to the next section if you intend to
+ use OpenVswitch
+
+CloudStack uses the network bridges in conjunction with KVM to connect the guest instances to
+each other and the outside world. They also are used to connect the System VMs to your
+infrastructure.
+
+By default these bridges are called *cloudbr0* and *cloudbr1* etc, but this can be
+changed to be more description.
+
+.. warning::
+ It is essential that you keep the configuration consistent across all of your hypervisors.
+
+There are many ways to configure your networking. Even within the scope of a given
+network mode. Below are a few simple examples.
+
+
+Network example for Basic Networks
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+In the Basic networking, all of the guests in a given pod will be on the same VLAN/subnet.
+It is common to use the native (untagged) VLAN for the private/management network, so in
+this example we will have two VLANs, one (native) for your private/management network and one
+for the guest network.
+
+We assume that the hypervisor has one NIC (eth0) with one tagged VLAN trunked from the switch:
+
+#. Native VLAN for management network (cloudbr0)
+#. VLAN 200 for guest network of the instances (cloudbr1)
+
+In this the following example we give the Hypervisor the IP-Address 192.168.42.11/24
+with the gateway 192.168.42.1
+
+.. note::
+ The Hypervisor and Management server don't have to be in the same subnet
+
+Configuring the Network Bridges for Basic Networks
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+It depends on the distribution you are using how to configure these,
+below you'll find examples for RHEL/CentOS and Ubuntu.
+
+.. note::
+ The goal is to have two bridges called 'cloudbr0' and 'cloudbr1' after this
+ section. This should be used as a guideline only. The exact configuration
+ will depend on your network layout.
+
+Configure RHEL or CentOS for Basic Networks
+'''''''''''''''''''''''''''''''''''''''''''
+
+The required packages were installed when libvirt was installed, we can
+proceed to configuring the network.
+
+First we configure eth0
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-eth0
+
+Make sure it looks similar to:
+
+.. parsed-literal::
+
+ DEVICE=eth0
+ HWADDR=00:04:xx:xx:xx:xx
+ ONBOOT=yes
+ HOTPLUG=no
+ BOOTPROTO=none
+ TYPE=Ethernet
+ BRIDGE=cloudbr0
+
+We now have to configure the VLAN interfaces:
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-eth0.200
+
+.. parsed-literal::
+
+ DEVICE=eth0.200
+ HWADDR=00:04:xx:xx:xx:xx
+ ONBOOT=yes
+ HOTPLUG=no
+ BOOTPROTO=none
+ TYPE=Ethernet
+ VLAN=yes
+ BRIDGE=cloudbr1
+
+Now that we have the VLAN interfaces configured we can add the bridges on top
+of them.
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-cloudbr0
+
+Now we configure cloudbr0 and include the Management IP of the hypervisor.
+
+.. note::
+ The management IP of the hypervisor doesn't have to be in same subnet/VLAN as the
+ management network, but its quite common.
+
+.. parsed-literal::
+
+ DEVICE=cloudbr0
+ TYPE=Bridge
+ ONBOOT=yes
+ BOOTPROTO=none
+ IPV6INIT=no
+ IPV6_AUTOCONF=no
+ DELAY=5
+ IPADDR=192.168.42.11
+ GATEWAY=192.168.42.1
+ NETMASK=255.255.255.0
+ STP=yes
+
+We configure cloudbr1 as a plain bridge without an IP address
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-cloudbr1
+
+.. parsed-literal::
+
+ DEVICE=cloudbr1
+ TYPE=Bridge
+ ONBOOT=yes
+ BOOTPROTO=none
+ IPV6INIT=no
+ IPV6_AUTOCONF=no
+ DELAY=5
+ STP=yes
+
+With this configuration you should be able to restart the network,
+although a reboot is recommended to see if everything works properly.
+
+.. warning::
+ Make sure you have an alternative way like IPMI or ILO to reach the machine
+ in case you made a configuration error and the network stops functioning!
+
+
+Configure Ubuntu for Basic Networks
+'''''''''''''''''''''''''''''''''''
+
+All the required packages were installed when you installed libvirt, so
+we only have to configure the network.
+
+.. parsed-literal::
+
+ $ vi /etc/network/interfaces
+
+Modify the interfaces file to look like this:
+
+.. parsed-literal::
+
+ auto lo
+ iface lo inet loopback
+
+ # The primary network interface
+ auto eth0
+ iface eth0 inet manual
+
+ auto eth0.200
+ iface eth0 inet manual
+
+ # management network
+ auto cloudbr0
+ iface cloudbr0 inet static
+ bridge_ports eth0
+ bridge_fd 5
+ bridge_stp off
+ bridge_maxwait 1
+ address 192.168.42.11
+ netmask 255.255.255.240
+ gateway 192.168.42.1
+ dns-nameservers 8.8.8.8 8.8.4.4
+ dns-domain lab.example.org
+
+ # guest network
+ auto cloudbr1
+ iface cloudbr1 inet manual
+ bridge_ports eth0.200
+ bridge_fd 5
+ bridge_stp off
+ bridge_maxwait 1
+
+With this configuration you should be able to restart the network,
+although a reboot is recommended to see if everything works properly.
+
+.. warning::
+ Make sure you have an alternative way like IPMI or ILO to reach the machine
+ in case you made a configuration error and the network stops functioning!
+
+
+
+Network Example for Advanced Networks
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+In the Advanced networking mode is most common to have (at least) two physical interfaces.
+In this example we will again have the hypervisor management interface on cloudbr0 on the
+untagged (native) VLAN. But now we will have a bridge on top of our additional interface (eth1)
+for public and guest traffic with no VLANs applied by us - CloudStack will add the VLANs
+as required.
+
+We again give the Hypervisor the IP-Address 192.168.42.11/24 with
+the gateway 192.168.42.1
+
+.. note::
+ The Hypervisor and Management server don't have to be in the same subnet
+
+
+Configuring the Network Bridges for Advanced Networks
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+It depends on the distribution you are using how to configure these,
+below you'll find examples for RHEL/CentOS and Ubuntu.
+
+.. note::
+ The goal is to have two bridges called 'cloudbr0' and 'cloudbr1' after this
+ section. This should be used as a guideline only. The exact configuration
+ will depend on your network layout.
+
+
+Configure RHEL/CentOS for Advanced Networks
+'''''''''''''''''''''''''''''''''''''''''''
+
+The required packages were installed when libvirt was installed, we can
+proceed to configuring the network.
+
+First we configure eth0
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-eth0
+
+Make sure it looks similar to:
+
+.. parsed-literal::
+
+ DEVICE=eth0
+ HWADDR=00:04:xx:xx:xx:xx
+ ONBOOT=yes
+ HOTPLUG=no
+ BOOTPROTO=none
+ TYPE=Ethernet
+ BRIDGE=cloudbr0
+
+We now have to configure the VLAN interfaces:
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-eth1
+
+.. parsed-literal::
+
+ DEVICE=eth1
+ HWADDR=00:04:xx:xx:xx:xx
+ ONBOOT=yes
+ HOTPLUG=no
+ BOOTPROTO=none
+ TYPE=Ethernet
+ BRIDGE=cloudbr1
+
+Now we have the VLAN interfaces configured we can add the bridges on top
+of them.
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-cloudbr0
+
+Now we configure cloudbr0 and include the Management IP of the hypervisor.
+
+.. note::
+ The management IP of the hypervisor doesn't have to be in same subnet/VLAN as the
+ management network, but its quite common.
+
+.. parsed-literal::
+
+ DEVICE=cloudbr0
+ TYPE=Bridge
+ ONBOOT=yes
+ BOOTPROTO=none
+ IPV6INIT=no
+ IPV6_AUTOCONF=no
+ DELAY=5
+ IPADDR=192.168.42.11
+ GATEWAY=192.168.42.1
+ NETMASK=255.255.255.0
+ STP=yes
+
+We configure cloudbr1 as a plain bridge without an IP address
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-cloudbr1
+
+.. parsed-literal::
+
+ DEVICE=cloudbr1
+ TYPE=Bridge
+ ONBOOT=yes
+ BOOTPROTO=none
+ IPV6INIT=no
+ IPV6_AUTOCONF=no
+ DELAY=5
+ STP=yes
+
+With this configuration you should be able to restart the network,
+although a reboot is recommended to see if everything works properly.
+
+.. warning::
+ Make sure you have an alternative way like IPMI or ILO to reach the machine
+ in case you made a configuration error and the network stops functioning!
+
+
+Configure Ubuntu for Advanced Networks
+''''''''''''''''''''''''''''''''''''''
+
+All the required packages were installed when you installed libvirt, so
+we only have to configure the network.
+
+.. parsed-literal::
+
+ $ vi /etc/network/interfaces
+
+Modify the interfaces file to look like this:
+
+.. parsed-literal::
+
+ auto lo
+ iface lo inet loopback
+
+ # The primary network interface
+ auto eth0
+ iface eth0 inet manual
+
+ # The second network interface
+ auto eth1
+ iface eth1 inet manual
+
+ # management network
+ auto cloudbr0
+ iface cloudbr0 inet static
+ bridge_ports eth0
+ bridge_fd 5
+ bridge_stp off
+ bridge_maxwait 1
+ address 192.168.42.11
+ netmask 255.255.255.240
+ gateway 192.168.42.1
+ dns-nameservers 8.8.8.8 8.8.4.4
+ dns-domain lab.example.org
+
+ # guest network
+ auto cloudbr1
+ iface cloudbr1 inet manual
+ bridge_ports eth1
+ bridge_fd 5
+ bridge_stp off
+ bridge_maxwait 1
+
+With this configuration you should be able to restart the network,
+although a reboot is recommended to see if everything works properly.
+
+.. warning::
+ Make sure you have an alternative way like IPMI or ILO to reach the machine
+ in case you made a configuration error and the network stops functioning!
+
+
+Configure the network using OpenVswitch
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. warning::
+ This is a very important section, please make sure you read this thoroughly.
+
+In order to forward traffic to your instances you will need at least two
+bridges: *public* and *private*.
+
+By default these bridges are called *cloudbr0* and *cloudbr1*, but you
+do have to make sure they are available on each hypervisor.
+
+The most important factor is that you keep the configuration consistent
+on all your hypervisors.
+
+
+Preparing
+^^^^^^^^^
+
+To make sure that the native bridge module will not interfere with
+openvswitch the bridge module should be added to the blacklist. See the
+modprobe documentation for your distribution on where to find the
+blacklist. Make sure the module is not loaded either by rebooting or
+executing rmmod bridge before executing next steps.
+
+The network configurations below depend on the ifup-ovs and ifdown-ovs
+scripts which are part of the openvswitch installation. They should be
+installed in /etc/sysconfig/network-scripts/
+
+
+OpenVswitch Network example
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+There are many ways to configure your network. In the Basic networking
+mode you should have two VLANs, one for your private network and one
+for the public network.
+
+We assume that the hypervisor has one NIC (eth0) with three tagged
+VLANs:
+
+#. VLAN 100 for management of the hypervisor
+
+#. VLAN 200 for public network of the instances (cloudbr0)
+
+#. VLAN 300 for private network of the instances (cloudbr1)
+
+On VLAN 100 we give the Hypervisor the IP-Address 192.168.42.11/24 with
+the gateway 192.168.42.1
+
+.. note::
+ The Hypervisor and Management server don't have to be in the same subnet
+
+
+Configuring the network bridges for OpenVswitch
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+It depends on the distribution you are using how to configure these,
+below you'll find examples for RHEL/CentOS.
+
+.. note::
+ The goal is to have three bridges called 'mgmt0', 'cloudbr0' and 'cloudbr1'
+ after this section. This should be used as a guideline only. The exact
+ configuration will depend on your network layout.
+
+
+Configure OpenVswitch
+'''''''''''''''''''''
+
+The network interfaces using OpenVswitch are created using the ovs-vsctl
+command. This command will configure the interfaces and persist them to
+the OpenVswitch database.
+
+First we create a main bridge connected to the eth0 interface. Next we
+create three fake bridges, each connected to a specific vlan tag.
+
+.. parsed-literal::
+
+ # ovs-vsctl add-br cloudbr
+ # ovs-vsctl add-port cloudbr eth0
+ # ovs-vsctl set port cloudbr trunks=100,200,300
+ # ovs-vsctl add-br mgmt0 cloudbr 100
+ # ovs-vsctl add-br cloudbr0 cloudbr 200
+ # ovs-vsctl add-br cloudbr1 cloudbr 300
+
+
+Configure OpenVswitch in RHEL or CentOS
+'''''''''''''''''''''''''''''''''''''''
+
+The required packages were installed when openvswitch and libvirt were
+installed, we can proceed to configuring the network.
+
+First we configure eth0
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-eth0
+
+Make sure it looks similar to:
+
+.. parsed-literal::
+
+ DEVICE=eth0
+ HWADDR=00:04:xx:xx:xx:xx
+ ONBOOT=yes
+ HOTPLUG=no
+ BOOTPROTO=none
+ TYPE=Ethernet
+
+We have to configure the base bridge with the trunk.
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-cloudbr
+
+.. parsed-literal::
+
+ DEVICE=cloudbr
+ ONBOOT=yes
+ HOTPLUG=no
+ BOOTPROTO=none
+ DEVICETYPE=ovs
+ TYPE=OVSBridge
+
+We now have to configure the three VLAN bridges:
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-mgmt0
+
+.. parsed-literal::
+
+ DEVICE=mgmt0
+ ONBOOT=yes
+ HOTPLUG=no
+ BOOTPROTO=static
+ DEVICETYPE=ovs
+ TYPE=OVSBridge
+ IPADDR=192.168.42.11
+ GATEWAY=192.168.42.1
+ NETMASK=255.255.255.0
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-cloudbr0
+
+.. parsed-literal::
+
+ DEVICE=cloudbr0
+ ONBOOT=yes
+ HOTPLUG=no
+ BOOTPROTO=none
+ DEVICETYPE=ovs
+ TYPE=OVSBridge
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-cloudbr1
+
+.. parsed-literal::
+
+ DEVICE=cloudbr1
+ ONBOOT=yes
+ HOTPLUG=no
+ BOOTPROTO=none
+ TYPE=OVSBridge
+ DEVICETYPE=ovs
+
+With this configuration you should be able to restart the network,
+although a reboot is recommended to see if everything works properly.
+
+.. warning::
+ Make sure you have an alternative way like IPMI or ILO to reach the machine
+ in case you made a configuration error and the network stops functioning!
+
+
+
+Configuring the firewall
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+The hypervisor needs to be able to communicate with other hypervisors
+and the management server needs to be able to reach the hypervisor.
+
+In order to do so we have to open the following TCP ports (if you are
+using a firewall):
+
+#. 22 (SSH)
+
+#. 1798
+
+#. 16509, 16514 (libvirt)
+
+#. 5900 - 6100 (VNC consoles)
+
+#. 49152 - 49216 (libvirt live migration)
+
+It depends on the firewall you are using how to open these ports. Below
+you'll find examples how to open these ports in RHEL/CentOS and Ubuntu.
+
+
+Open ports in RHEL/CentOS
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+RHEL and CentOS use iptables for firewalling the system, you can open
+extra ports by executing the following iptable commands:
+
+.. parsed-literal::
+
+ $ iptables -I INPUT -p tcp -m tcp --dport 22 -j ACCEPT
+
+.. parsed-literal::
+
+ $ iptables -I INPUT -p tcp -m tcp --dport 1798 -j ACCEPT
+
+.. parsed-literal::
+
+ $ iptables -I INPUT -p tcp -m tcp --dport 16509 -j ACCEPT
+
+.. parsed-literal::
+
+ $ iptables -I INPUT -p tcp -m tcp --dport 16514 -j ACCEPT
+
+.. parsed-literal::
+
+ $ iptables -I INPUT -p tcp -m tcp --dport 5900:6100 -j ACCEPT
+
+.. parsed-literal::
+
+ $ iptables -I INPUT -p tcp -m tcp --dport 49152:49216 -j ACCEPT
+
+These iptable settings are not persistent accross reboots, we have to
+save them first.
+
+.. parsed-literal::
+
+ $ iptables-save > /etc/sysconfig/iptables
+
+
+Open ports in Ubuntu
+^^^^^^^^^^^^^^^^^^^^
+
+The default firewall under Ubuntu is UFW (Uncomplicated FireWall), which
+is a Python wrapper around iptables.
+
+To open the required ports, execute the following commands:
+
+.. parsed-literal::
+
+ $ ufw allow proto tcp from any to any port 22
+
+.. parsed-literal::
+
+ $ ufw allow proto tcp from any to any port 1798
+
+.. parsed-literal::
+
+ $ ufw allow proto tcp from any to any port 16509
+
+.. parsed-literal::
+
+ $ ufw allow proto tcp from any to any port 16514
+
+.. parsed-literal::
+
+ $ ufw allow proto tcp from any to any port 5900:6100
+
+.. parsed-literal::
+
+ $ ufw allow proto tcp from any to any port 49152:49216
+
+.. note::
+ By default UFW is not enabled on Ubuntu. Executing these commands with the
+ firewall disabled does not enable the firewall.
+
+
+Additional Packages Required for Features
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Secondary Storage Bypass
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+New in 4.11 is the ability to bypass storing a template on secondary storage, and
+instead directly downloading a 'template' from an alternate remote location.
+In order to facilitate this the **Aria2** (https://aria2.github.io/) package must be
+installed on all of your KVM hosts.
+
+As this package often is not available in standard distribution repos, you will need
+to install the package from your preferred source.
+
+Live Migration
+^^^^^^^^^^^^^^
+CloudStack uses the qemu-img to perform live migrations. In CentOS > 6.3, the qemu-img
+supplied by RedHat/CentOS ceased to include a '-s' switch which performs snapshots. The
+'-s' switch has been restored in latest CentOS/RHEL 7.x versions.
+
+In order to be able to perform live migrations on CentOS 6.x (greater than 6.3) you must
+replace your version of qemu-img with one which has been patched to include the '-s'
+switch.
+
+
+Add the host to CloudStack
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The host is now ready to be added to a cluster. This is covered in a
+later section, see :ref:`adding-a-host`. It is
+recommended that you continue to read the documentation before adding
+the host!
+
diff --git a/source/installguide/hypervisor/lxc.rst b/source/installguide/hypervisor/lxc.rst
new file mode 100644
index 0000000..a0b88d7
--- /dev/null
+++ b/source/installguide/hypervisor/lxc.rst
@@ -0,0 +1,670 @@
+.. 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.
+
+
+Host LXC Installation
+---------------------
+
+System Requirements for LXC Hosts
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+LXC requires the Linux kernel cgroups functionality which is available
+starting 2.6.24. Although you are not required to run these
+distributions, the following are recommended:
+
+- CentOS / RHEL: 6.3
+
+- Ubuntu: 12.04(.1)
+
+The main requirement for LXC hypervisors is the libvirt and Qemu
+version. No matter what Linux distribution you are using, make sure the
+following requirements are met:
+
+- libvirt: 1.0.0 or higher
+
+- Qemu/KVM: 1.0 or higher
+
+The default bridge in CloudStack is the Linux native bridge
+implementation (bridge module). CloudStack includes an option to work
+with OpenVswitch, the requirements are listed below
+
+- libvirt: 1.0.0 or higher
+
+- openvswitch: 1.7.1 or higher
+
+In addition, the following hardware requirements apply:
+
+- Within a single cluster, the hosts must be of the same distribution
+ version.
+
+- All hosts within a cluster must be homogenous. The CPUs must be of
+ the same type, count, and feature flags.
+
+- Must support HVM (Intel-VT or AMD-V enabled)
+
+- 64-bit x86 CPU (more cores results in better performance)
+
+- 4 GB of memory
+
+- At least 1 NIC
+
+- When you deploy CloudStack, the hypervisor host must not have any VMs
+ already running
+
+
+LXC Installation Overview
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+LXC does not have any native system VMs, instead KVM will be used to run
+system VMs. This means that your host will need to support both LXC and
+KVM, thus most of the installation and configuration will be identical
+to the KVM installation. The material in this section doesn't duplicate
+KVM installation docs. It provides the CloudStack-specific steps that
+are needed to prepare a KVM host to work with CloudStack.
+
+.. warning::
+ Before continuing, make sure that you have applied the latest updates to
+ your host.
+
+.. warning::
+ It is NOT recommended to run services on this host not controlled by
+ CloudStack.
+
+The procedure for installing an LXC Host is:
+
+#. Prepare the Operating System
+
+#. Install and configure libvirt
+
+#. Configure Security Policies (AppArmor and SELinux)
+
+#. Install and configure the Agent
+
+
+Prepare the Operating System
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The OS of the Host must be prepared to host the CloudStack Agent and run
+KVM instances.
+
+#. Log in to your OS as root.
+
+#. Check for a fully qualified hostname.
+
+ .. parsed-literal::
+
+ $ hostname --fqdn
+
+ This should return a fully qualified hostname such as
+ "kvm1.lab.example.org". If it does not, edit /etc/hosts so that it
+ does.
+
+#. Make sure that the machine can reach the Internet.
+
+ .. parsed-literal::
+
+ $ ping www.cloudstack.org
+
+#. Turn on NTP for time synchronization.
+
+ .. note::
+ NTP is required to synchronize the clocks of the servers in your
+ cloud. Unsynchronized clocks can cause unexpected problems.
+
+ #. Install NTP
+
+ .. parsed-literal::
+
+ $ yum install ntp
+
+ .. parsed-literal::
+
+ $ apt-get install openntpd
+
+#. Repeat all of these steps on every hypervisor host.
+
+
+Install and configure the Agent
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To manage LXC instances on the host CloudStack uses a Agent. This Agent
+communicates with the Management server and controls all the instances
+on the host.
+
+First we start by installing the agent:
+
+In RHEL or CentOS:
+
+.. parsed-literal::
+
+ $ yum install cloudstack-agent
+
+In Ubuntu:
+
+.. parsed-literal::
+
+ $ apt-get install cloudstack-agent
+
+Next step is to update the Agent configuration setttings. The settings
+are in ``/etc/cloudstack/agent/agent.properties``
+
+#. Set the Agent to run in LXC mode:
+
+ .. parsed-literal::
+
+ hypervisor.type=lxc
+
+#. Optional: If you would like to use direct networking (instead of the
+ default bridge networking), configure these lines:
+
+ .. parsed-literal::
+
+ libvirt.vif.driver=com.cloud.hypervisor.kvm.resource.DirectVifDriver
+
+ .. parsed-literal::
+
+ network.direct.source.mode=private
+
+ .. parsed-literal::
+
+ network.direct.device=eth0
+
+The host is now ready to be added to a cluster. This is covered in a
+later section, see :ref:`adding-a-host`. It is
+recommended that you continue to read the documentation before adding
+the host!
+
+
+Install and Configure libvirt
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack uses libvirt for managing virtual machines. Therefore it is
+vital that libvirt is configured correctly. Libvirt is a dependency of
+cloudstack-agent and should already be installed.
+
+#. In order to have live migration working libvirt has to listen for
+ unsecured TCP connections. We also need to turn off libvirts attempt
+ to use Multicast DNS advertising. Both of these settings are in
+ ``/etc/libvirt/libvirtd.conf``
+
+ Set the following parameters:
+
+ .. parsed-literal::
+
+ listen_tls = 0
+
+ .. parsed-literal::
+
+ listen_tcp = 1
+
+ .. parsed-literal::
+
+ tcp_port = "16509"
+
+ .. parsed-literal::
+
+ auth_tcp = "none"
+
+ .. parsed-literal::
+
+ mdns_adv = 0
+
+#. Turning on "listen\_tcp" in libvirtd.conf is not enough, we have to
+ change the parameters as well:
+
+ On RHEL or CentOS modify ``/etc/sysconfig/libvirtd``:
+
+ Uncomment the following line:
+
+ .. parsed-literal::
+
+ #LIBVIRTD_ARGS="--listen"
+
+ On Ubuntu: modify ``/etc/default/libvirt-bin``
+
+ Add "-l" to the following line
+
+ .. parsed-literal::
+
+ libvirtd_opts="-d"
+
+ so it looks like:
+
+ .. parsed-literal::
+
+ libvirtd_opts="-d -l"
+
+#. In order to have the VNC Console work we have to make sure it will
+ bind on 0.0.0.0. We do this by editing ``/etc/libvirt/qemu.conf``
+
+ Make sure this parameter is set:
+
+ .. parsed-literal::
+
+ vnc_listen = "0.0.0.0"
+
+#. Restart libvirt
+
+ In RHEL or CentOS:
+
+ .. parsed-literal::
+
+ $ service libvirtd restart
+
+ In Ubuntu:
+
+ .. parsed-literal::
+
+ $ service libvirt-bin restart
+
+
+Configure the Security Policies
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack does various things which can be blocked by security
+mechanisms like AppArmor and SELinux. These have to be disabled to
+ensure the Agent has all the required permissions.
+
+#. Configure SELinux (RHEL and CentOS)
+
+ #. Check to see whether SELinux is installed on your machine. If not,
+ you can skip this section.
+
+ In RHEL or CentOS, SELinux is installed and enabled by default.
+ You can verify this with:
+
+ .. parsed-literal::
+
+ $ rpm -qa | grep selinux
+
+ #. Set the SELINUX variable in ``/etc/selinux/config`` to
+ "permissive". This ensures that the permissive setting will be
+ maintained after a system reboot.
+
+ In RHEL or CentOS:
+
+ .. parsed-literal::
+
+ $ vi /etc/selinux/config
+
+ Change the following line
+
+ .. parsed-literal::
+
+ SELINUX=enforcing
+
+ to this
+
+ .. parsed-literal::
+
+ SELINUX=permissive
+
+ #. Then set SELinux to permissive starting immediately, without
+ requiring a system reboot.
+
+ .. parsed-literal::
+
+ $ setenforce permissive
+
+#. Configure Apparmor (Ubuntu)
+
+ #. Check to see whether AppArmor is installed on your machine. If
+ not, you can skip this section.
+
+ In Ubuntu AppArmor is installed and enabled by default. You can
+ verify this with:
+
+ .. parsed-literal::
+
+ $ dpkg --list 'apparmor'
+
+ #. Disable the AppArmor profiles for libvirt
+
+ .. parsed-literal::
+
+ $ ln -s /etc/apparmor.d/usr.sbin.libvirtd /etc/apparmor.d/disable/
+
+ .. parsed-literal::
+
+ $ ln -s /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper /etc/apparmor.d/disable/
+
+ .. parsed-literal::
+
+ $ apparmor_parser -R /etc/apparmor.d/usr.sbin.libvirtd
+
+ .. parsed-literal::
+
+ $ apparmor_parser -R /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper
+
+
+Configure the network bridges
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. warning::
+ This is a very important section, please make sure you read this thoroughly.
+
+.. note::
+ This section details how to configure bridges using the native
+ implementation in Linux. Please refer to the next section if you intend to
+ use OpenVswitch
+
+In order to forward traffic to your instances you will need at least two
+bridges: *public* and *private*.
+
+By default these bridges are called *cloudbr0* and *cloudbr1*, but you
+do have to make sure they are available on each hypervisor.
+
+The most important factor is that you keep the configuration consistent
+on all your hypervisors.
+
+
+Network example
+^^^^^^^^^^^^^^^
+
+There are many ways to configure your network. In the Basic networking
+mode you should have two (V)LAN's, one for your private network and one
+for the public network.
+
+We assume that the hypervisor has one NIC (eth0) with three tagged
+VLAN's:
+
+#. VLAN 100 for management of the hypervisor
+
+#. VLAN 200 for public network of the instances (cloudbr0)
+
+#. VLAN 300 for private network of the instances (cloudbr1)
+
+On VLAN 100 we give the Hypervisor the IP-Address 192.168.42.11/24 with
+the gateway 192.168.42.1
+
+.. note::
+ The Hypervisor and Management server don't have to be in the same subnet!
+
+Configuring the network bridges
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+It depends on the distribution you are using how to configure these,
+below you'll find examples for RHEL/CentOS and Ubuntu.
+
+.. note::
+ The goal is to have two bridges called 'cloudbr0' and 'cloudbr1' after this
+ section. This should be used as a guideline only. The exact configuration
+ will depend on your network layout.
+
+
+Configure in RHEL or CentOS
+'''''''''''''''''''''''''''
+
+The required packages were installed when libvirt was installed, we can
+proceed to configuring the network.
+
+First we configure eth0
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-eth0
+
+Make sure it looks similar to:
+
+.. parsed-literal::
+
+ DEVICE=eth0
+ HWADDR=00:04:xx:xx:xx:xx
+ ONBOOT=yes
+ HOTPLUG=no
+ BOOTPROTO=none
+ TYPE=Ethernet
+
+We now have to configure the three VLAN interfaces:
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-eth0.100
+
+.. parsed-literal::
+
+ DEVICE=eth0.100
+ HWADDR=00:04:xx:xx:xx:xx
+ ONBOOT=yes
+ HOTPLUG=no
+ BOOTPROTO=none
+ TYPE=Ethernet
+ VLAN=yes
+ IPADDR=192.168.42.11
+ GATEWAY=192.168.42.1
+ NETMASK=255.255.255.0
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-eth0.200
+
+.. parsed-literal::
+
+ DEVICE=eth0.200
+ HWADDR=00:04:xx:xx:xx:xx
+ ONBOOT=yes
+ HOTPLUG=no
+ BOOTPROTO=none
+ TYPE=Ethernet
+ VLAN=yes
+ BRIDGE=cloudbr0
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-eth0.300
+
+.. parsed-literal::
+
+ DEVICE=eth0.300
+ HWADDR=00:04:xx:xx:xx:xx
+ ONBOOT=yes
+ HOTPLUG=no
+ BOOTPROTO=none
+ TYPE=Ethernet
+ VLAN=yes
+ BRIDGE=cloudbr1
+
+Now we have the VLAN interfaces configured we can add the bridges on top
+of them.
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-cloudbr0
+
+Now we just configure it is a plain bridge without an IP-Address
+
+.. parsed-literal::
+
+ DEVICE=cloudbr0
+ TYPE=Bridge
+ ONBOOT=yes
+ BOOTPROTO=none
+ IPV6INIT=no
+ IPV6_AUTOCONF=no
+ DELAY=5
+ STP=yes
+
+We do the same for cloudbr1
+
+.. parsed-literal::
+
+ $ vi /etc/sysconfig/network-scripts/ifcfg-cloudbr1
+
+.. parsed-literal::
+
+ DEVICE=cloudbr1
+ TYPE=Bridge
+ ONBOOT=yes
+ BOOTPROTO=none
+ IPV6INIT=no
+ IPV6_AUTOCONF=no
+ DELAY=5
+ STP=yes
+
+With this configuration you should be able to restart the network,
+although a reboot is recommended to see if everything works properly.
+
+.. warning::
+ Make sure you have an alternative way like IPMI or ILO to reach the machine
+ in case you made a configuration error and the network stops functioning!
+
+
+Configure in Ubuntu
+'''''''''''''''''''
+
+All the required packages were installed when you installed libvirt, so
+we only have to configure the network.
+
+.. parsed-literal::
+
+ $ vi /etc/network/interfaces
+
+Modify the interfaces file to look like this:
+
+.. parsed-literal::
+
+ auto lo
+ iface lo inet loopback
+
+ # The primary network interface
+ auto eth0.100
+ iface eth0.100 inet static
+ address 192.168.42.11
+ netmask 255.255.255.240
+ gateway 192.168.42.1
+ dns-nameservers 8.8.8.8 8.8.4.4
+ dns-domain lab.example.org
+
+ # Public network
+ auto cloudbr0
+ iface cloudbr0 inet manual
+ bridge_ports eth0.200
+ bridge_fd 5
+ bridge_stp off
+ bridge_maxwait 1
+
+ # Private network
+ auto cloudbr1
+ iface cloudbr1 inet manual
+ bridge_ports eth0.300
+ bridge_fd 5
+ bridge_stp off
+ bridge_maxwait 1
+
+With this configuration you should be able to restart the network,
+although a reboot is recommended to see if everything works properly.
+
+.. warning::
+ Make sure you have an alternative way like IPMI or ILO to reach the machine
+ in case you made a configuration error and the network stops functioning!
+
+
+Configuring the firewall
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+The hypervisor needs to be able to communicate with other hypervisors
+and the management server needs to be able to reach the hypervisor.
+
+In order to do so we have to open the following TCP ports (if you are
+using a firewall):
+
+#. 22 (SSH)
+
+#. 1798
+
+#. 16509 (libvirt)
+
+#. 5900 - 6100 (VNC consoles)
+
+#. 49152 - 49216 (libvirt live migration)
+
+It depends on the firewall you are using how to open these ports. Below
+you'll find examples how to open these ports in RHEL/CentOS and Ubuntu.
+
+
+Open ports in RHEL/CentOS
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+RHEL and CentOS use iptables for firewalling the system, you can open
+extra ports by executing the following iptable commands:
+
+.. parsed-literal::
+
+ $ iptables -I INPUT -p tcp -m tcp --dport 22 -j ACCEPT
+
+.. parsed-literal::
+
+ $ iptables -I INPUT -p tcp -m tcp --dport 1798 -j ACCEPT
+
+.. parsed-literal::
+
+ $ iptables -I INPUT -p tcp -m tcp --dport 16509 -j ACCEPT
+
+.. parsed-literal::
+
+ $ iptables -I INPUT -p tcp -m tcp --dport 5900:6100 -j ACCEPT
+
+.. parsed-literal::
+
+ $ iptables -I INPUT -p tcp -m tcp --dport 49152:49216 -j ACCEPT
+
+These iptable settings are not persistent accross reboots, we have to
+save them first.
+
+.. parsed-literal::
+
+ $ iptables-save > /etc/sysconfig/iptables
+
+
+Open ports in Ubuntu
+^^^^^^^^^^^^^^^^^^^^
+
+The default firewall under Ubuntu is UFW (Uncomplicated FireWall), which
+is a Python wrapper around iptables.
+
+To open the required ports, execute the following commands:
+
+.. parsed-literal::
+
+ $ ufw allow proto tcp from any to any port 22
+
+.. parsed-literal::
+
+ $ ufw allow proto tcp from any to any port 1798
+
+.. parsed-literal::
+
+ $ ufw allow proto tcp from any to any port 16509
+
+.. parsed-literal::
+
+ $ ufw allow proto tcp from any to any port 5900:6100
+
+.. parsed-literal::
+
+ $ ufw allow proto tcp from any to any port 49152:49216
+
+.. note::
+ By default UFW is not enabled on Ubuntu. Executing these commands with the
+ firewall disabled does not enable the firewall.
+
+
+Add the host to CloudStack
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The host is now ready to be added to a cluster. This is covered in a
+later section, see :ref:`adding-a-host`. It is
+recommended that you continue to read the documentation before adding
+the host!
diff --git a/source/installguide/hypervisor/vsphere.rst b/source/installguide/hypervisor/vsphere.rst
new file mode 100644
index 0000000..91a4819
--- /dev/null
+++ b/source/installguide/hypervisor/vsphere.rst
@@ -0,0 +1,1028 @@
+.. 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.
+
+
+Host VMware vSphere Installation
+--------------------------------
+
+If you want to use the VMware vSphere hypervisor to run guest virtual
+machines, install vSphere on the host(s) in your cloud.
+
+
+System Requirements for vSphere Hosts
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+
+Software requirements:
+^^^^^^^^^^^^^^^^^^^^^^
+
+- vSphere and vCenter, versions 4.1, 5.0, 5.1 or 5.5.
+
+ vSphere Standard is recommended. Note however that customers need to
+ consider the CPU constraints in place with vSphere licensing. See
+ `http://www.vmware.com/files/pdf/vsphere\_pricing.pdf
+ <http://www.vmware.com/files/pdf/vsphere_pricing.pdf>`_
+ and discuss with your VMware sales representative.
+
+ vCenter Server Standard is recommended.
+
+- 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.
+
+.. warning::
+ Apply All Necessary Hotfixes. The lack of up-do-date hotfixes can lead to
+ data corruption and lost VMs.
+
+
+Hardware requirements:
+^^^^^^^^^^^^^^^^^^^^^^
+
+- The host must be certified as compatible with vSphere. See the VMware
+ Hardware Compatibility Guide at
+ `http://www.vmware.com/resources/compatibility/search.php
+ <http://www.vmware.com/resources/compatibility/search.php>`_.
+
+- All hosts must be 64-bit and must support HVM (Intel-VT or AMD-V
+ enabled).
+
+- All hosts within a cluster must be homogenous. That means the CPUs
+ must be of the same type, count, and feature flags.
+
+- 64-bit x86 CPU (more cores results in better performance)
+
+- Hardware virtualization support required
+
+- 4 GB of memory
+
+- 36 GB of local disk
+
+- At least 1 NIC
+
+- Statically allocated IP Address
+
+
+vCenter Server requirements:
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+- Processor - 2 CPUs 2.0GHz or higher Intel or AMD x86 processors.
+ Processor requirements may be higher if the database runs on the same
+ machine.
+
+- Memory - 3GB RAM. RAM requirements may be higher if your database
+ runs on the same machine.
+
+- Disk storage - 2GB. Disk requirements may be higher if your database
+ runs on the same machine.
+
+- Microsoft SQL Server 2005 Express disk requirements. The bundled
+ database requires up to 2GB free disk space to decompress the
+ installation archive.
+
+- Networking - 1Gbit or 10Gbit.
+
+For more information, see `"vCenter Server and the vSphere Client Hardware
+Requirements" <http://pubs.vmware.com/vsp40/wwhelp/wwhimpl/js/html/wwhelp.htm#href=install/c_vc_hw.html>`_.
+
+
+Other requirements:
+^^^^^^^^^^^^^^^^^^^
+
+- VMware vCenter Standard Edition 4.1, 5.0, 5.1 or 5.5 must be installed and
+ available to manage the vSphere hosts.
+
+- vCenter must be configured to use the standard port 443 so that it
+ can communicate with the CloudStack Management Server.
+
+- You must re-install VMware ESXi if you are going to re-use a host
+ from a previous install.
+
+- CloudStack requires VMware vSphere 4.1, 5.0, 5.1 or 5.5. VMware vSphere 4.0 is
+ not supported.
+
+- All hosts must be 64-bit and must support HVM (Intel-VT or AMD-V
+ enabled). All hosts within a cluster must be homogeneous. That means
+ the CPUs must be of the same type, count, and feature flags.
+
+- The CloudStack management network must not be configured as a
+ separate virtual network. The CloudStack management network is the
+ same as the vCenter management network, and will inherit its
+ configuration. See :ref:`configure-vcenter-management-network`.
+
+- CloudStack requires ESXi and vCenter. ESX is not supported.
+
+- Ideally all resources used for CloudStack must be used for CloudStack only.
+ CloudStack should not share instance of ESXi or storage with other
+ management consoles. Do not share the same storage volumes that will
+ be used by CloudStack with a different set of ESXi servers that are
+ not managed by CloudStack.
+
+- Put all target ESXi hypervisors in dedicated clusters in a separate Datacenter
+ in vCenter.
+
+- Ideally clusters that will be managed by CloudStack should not contain
+ any other VMs. Do not run the management server or vCenter on
+ the cluster that is designated for CloudStack use. Create a separate
+ cluster for use of CloudStack and make sure that they are no VMs in
+ this cluster.
+
+- All of the required VLANs must be trunked into all network switches that
+ are connected to the ESXi hypervisor hosts. These would include the
+ VLANs for Management, Storage, vMotion, and guest VLANs. The guest
+ VLAN (used in Advanced Networking; see Network Setup) is a contiguous
+ range of VLANs that will be managed by CloudStack.
+
+
+Preparation Checklist for VMware
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+For a smoother installation, gather the following information before you
+start:
+
+- Information listed in :ref:`vcenter-checklist`
+
+- Information listed in :ref:`networking-checklist-for-vmware`
+
+
+.. _vcenter-checklist:
+
+vCenter Checklist
+^^^^^^^^^^^^^^^^^
+
+You will need the following information about vCenter.
+
+.. cssclass:: table-striped table-bordered table-hover
+
+======================== =====================================
+vCenter Requirement Notes
+======================== =====================================
+vCenter User This user must have admin privileges.
+vCenter User Password Password for the above user.
+vCenter Datacenter Name Name of the datacenter.
+vCenter Cluster Name Name of the cluster.
+======================== =====================================
+
+
+.. _networking-checklist-for-vmware:
+
+Networking Checklist for VMware
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+You will need the following information about your VLANs.
+
+.. cssclass:: table-striped table-bordered table-hover
+
+============================ ==========================================================================================
+VLAN Information Notes
+============================ ==========================================================================================
+ESXi VLAN VLAN on which all your ESXi hypervisors reside.
+ESXI VLAN IP Address IP Address Range in the ESXi VLAN. One address per Virtual Router is used from this range.
+ESXi VLAN IP Gateway
+ESXi VLAN Netmask
+Management Server VLAN VLAN on which the CloudStack Management server is installed.
+Public VLAN VLAN for the Public Network.
+Public VLAN Gateway
+Public VLAN Netmask
+Public VLAN IP Address Range Range of Public IP Addresses available for CloudStack use. These
+ addresses will be used for virtual router on CloudStack to route private
+ traffic to external networks.
+VLAN Range for Customer use A contiguous range of non-routable VLANs. One VLAN will be assigned for
+ each customer.
+============================ ==========================================================================================
+
+
+vSphere Installation Steps
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. If you haven't already, you'll need to download and purchase vSphere
+ from the VMware Website
+ (`https://www.vmware.com/tryvmware/index.php?p=vmware-vsphere&lp=1 <https://www.vmware.com/tryvmware/index.php?p=vmware-vsphere&lp=1>`_)
+ and install it by following the VMware vSphere Installation Guide.
+
+#. Following installation, perform the following configuration, which
+ are described in the next few sections:
+
+ .. cssclass:: table-striped table-bordered table-hover
+
+ ====================================================================================================== ===================
+ Required Optional
+ ====================================================================================================== ===================
+ ESXi host setup NIC bonding
+ Configure host physical networking,virtual switch, vCenter Management Network, and extended port range Multipath storage
+ Prepare storage for iSCSI
+ Configure clusters in vCenter and add hosts to them, or add hosts without clusters to vCenter
+ ====================================================================================================== ===================
+
+
+ESXi Host setup
+~~~~~~~~~~~~~~~
+
+All ESXi hosts should have CPU hardware virtualization support enabled in
+the BIOS. Please note hardware virtualization support is not enabled by
+default on most servers.
+
+
+Physical Host Networking
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+You should have a plan for cabling the vSphere hosts. Proper network
+configuration is required before adding a vSphere host to CloudStack. To
+configure an ESXi host, you can use vClient to add it as standalone host
+to vCenter first. Once you see the host appearing in the vCenter
+inventory tree, click the host node in the inventory tree, and navigate
+to the Configuration tab.
+
+|vspherephysicalnetwork.png: vSphere client|
+
+In the host configuration tab, click the "Hardware/Networking" link to
+bring up the networking configuration page as above.
+
+
+Configure Virtual Switch
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+During the initial installation of an ESXi host a default virtual switch
+vSwitch0 is created. You may need to create additional vSwiches depending
+on your required architecture. CloudStack requires all ESXi hosts in the cloud
+to use consistently named virtual switches. If
+you change the default virtual switch name, you will need to configure
+one or more CloudStack configuration variables as well.
+
+
+Separating Traffic
+''''''''''''''''''
+
+CloudStack allows you to configure three separate networks per ESXi host.
+CloudStack identifies these networks by the name of the vSwitch
+they are connected to. The networks for configuration are public (for
+traffic to/from the public internet), guest (for guest-guest traffic),
+and private (for management and usually storage traffic). You can use
+the default virtual switch for all three, or create one or two other
+vSwitches for those traffic types.
+
+If you want to separate traffic in this way you should first create and
+configure vSwitches in vCenter according to the vCenter instructions.
+Take note of the vSwitch names you have used for each traffic type. You
+will configure CloudStack to use these vSwitches.
+
+
+Increasing Ports
+''''''''''''''''
+
+By default a virtual switch on ESXi hosts is created with 56 ports. We
+recommend setting it to 4088, the maximum number of ports allowed. To do
+that, click the "Properties..." link for virtual switch (note this is
+not the Properties link for Networking).
+
+|vsphereincreaseports.png: vSphere client|
+
+In vSwitch properties dialog, select the vSwitch and click Edit. You
+should see the following dialog:
+
+|vspherevswitchproperties.png: vSphere client|
+
+In this dialog, you can change the number of switch ports. After you've
+done that, ESXi hosts are required to reboot in order for the setting to
+take effect.
+
+
+.. _configure-vcenter-management-network:
+
+Configure vCenter Management Network
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+In the vSwitch properties dialog box, you may see a vCenter management
+network. This same network will also be used as the CloudStack
+management network. CloudStack requires the vCenter management network
+to be configured properly. Select the management network item in the
+dialog, then click Edit.
+
+|vspheremgtnetwork.png: vSphere client|
+
+Make sure the following values are set:
+
+- VLAN ID set to the desired ID
+
+- vMotion enabled.
+
+- Management traffic enabled.
+
+If the ESXi hosts have multiple VMKernel ports, and ESXi is not using
+the default value "Management Network" as the management network name,
+you must follow these guidelines to configure the management network
+port group so that CloudStack can find it:
+
+- Use one label for the management network port across all ESXi hosts.
+
+- In the CloudStack UI, go to Configuration - Global Settings and set
+ vmware.management.portgroup to the management network label from the
+ ESXi hosts.
+
+
+Extend Port Range for CloudStack Console Proxy
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+(Applies only to VMware vSphere version 4.x)
+
+You need to extend the range of firewall ports that the console proxy
+works with on the hosts. This is to enable the console proxy to work
+with VMware-based VMs. The default additional port range is 59000-60000.
+To extend the port range, log in to the VMware ESX service console on
+each host and run the following commands:
+
+.. parsed-literal::
+
+ esxcfg-firewall -o 59000-60000,tcp,in,vncextras
+ esxcfg-firewall -o 59000-60000,tcp,out,vncextras
+
+
+Configure NIC Bonding for vSphere
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+NIC bonding on vSphere hosts may be done according to the vSphere
+installation guide.
+
+.. _configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch:
+
+Configuring a vSphere Cluster with Nexus 1000v Virtual Switch
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack supports Cisco Nexus 1000v dvSwitch (Distributed Virtual
+Switch) for virtual network configuration in a VMware vSphere
+environment. This section helps you configure a vSphere cluster with
+Nexus 1000v virtual switch in a VMware vCenter environment. For
+information on creating a vSphere cluster, see
+`"VMware vSphere Installation and Configuration"
+<#vmware-vsphere-installation-and-configuration>`_
+
+
+About Cisco Nexus 1000v Distributed Virtual Switch
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The Cisco Nexus 1000V virtual switch is a software-based virtual machine
+access switch for VMware vSphere environments. It can span multiple
+hosts running VMware ESXi 4.0 and later. A Nexus virtual switch consists
+of two components: the Virtual Supervisor Module (VSM) and the Virtual
+Ethernet Module (VEM). The VSM is a virtual appliance that acts as the
+switch's supervisor. It controls multiple VEMs as a single network
+device. The VSM is installed independent of the VEM and is deployed in
+redundancy mode as pairs or as a standalone appliance. The VEM is
+installed on each VMware ESXi server to provide packet-forwarding
+capability. It provides each virtual machine with dedicated switch
+ports. This VSM-VEM architecture is analogous to a physical Cisco
+switch's supervisor (standalone or configured in high-availability mode)
+and multiple linecards architecture.
+
+Nexus 1000v switch uses vEthernet port profiles to simplify network
+provisioning for virtual machines. There are two types of port profiles:
+Ethernet port profile and vEthernet port profile. The Ethernet port
+profile is applied to the physical uplink ports-the NIC ports of the
+physical NIC adapter on an ESXi server. The vEthernet port profile is
+associated with the virtual NIC (vNIC) that is plumbed on a guest VM on
+the ESXi server. The port profiles help the network administrators
+define network policies which can be reused for new virtual machines.
+The Ethernet port profiles are created on the VSM and are represented as
+port groups on the vCenter server.
+
+
+Prerequisites and Guidelines
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+This section discusses prerequisites and guidelines for using Nexus
+virtual switch in CloudStack. Before configuring Nexus virtual switch,
+ensure that your system meets the following requirements:
+
+- A cluster of servers (ESXi 4.1 or later) is configured in the
+ vCenter.
+
+- Each cluster managed by CloudStack is the only cluster in its vCenter
+ datacenter.
+
+- A Cisco Nexus 1000v virtual switch is installed to serve the
+ datacenter that contains the vCenter cluster. This ensures that
+ CloudStack doesn't have to deal with dynamic migration of virtual
+ adapters or networks across other existing virtual switches. See
+ `Cisco Nexus 1000V Installation and Upgrade Guide
+ <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_5_1/install_upgrade/vsm_vem/guide/n1000v_installupgrade.html>`_
+ for guidelines on how to install the Nexus 1000v VSM and VEM modules.
+
+- The Nexus 1000v VSM is not deployed on a vSphere host that is managed
+ by CloudStack.
+
+- When the maximum number of VEM modules per VSM instance is reached,
+ an additional VSM instance is created before introducing any more
+ ESXi hosts. The limit is 64 VEM modules for each VSM instance.
+
+- CloudStack expects that the Management Network of the ESXi host is
+ configured on the standard vSwitch and searches for it in the
+ standard vSwitch. Therefore, ensure that you do not migrate the
+ management network to Nexus 1000v virtual switch during
+ configuration.
+
+- All information given in :ref:`nexus-vswift-preconf`
+
+
+.. _nexus-vswift-preconf:
+
+Nexus 1000v Virtual Switch Preconfiguration
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Preparation Checklist
+'''''''''''''''''''''
+
+For a smoother configuration of Nexus 1000v switch, gather the following
+information before you start:
+
+- vCenter credentials
+
+- Nexus 1000v VSM IP address
+
+- Nexus 1000v VSM Credentials
+
+- Ethernet port profile names
+
+
+vCenter Credentials Checklist
+'''''''''''''''''''''''''''''
+
+You will need the following information about vCenter:
+
+.. cssclass:: table-striped table-bordered table-hover
+
+============================= ========= =============================================================================
+Nexus vSwitch Requirements Value Notes
+============================= ========= =============================================================================
+vCenter IP The IP address of the vCenter.
+Secure HTTP Port Number 443 Port 443 is configured by default; however, you can change the port if needed.
+vCenter User ID The vCenter user with administrator-level privileges. The vCenter User ID is
+ required when you configure the virtual switch in CloudStack.
+vCenter Password The password for the vCenter user specified above. The password for this
+ vCenter user is required when you configure the switch in CloudStack.
+============================= ========= =============================================================================
+
+
+Network Configuration Checklist
+'''''''''''''''''''''''''''''''
+
+The following information specified in the Nexus Configure Networking
+screen is displayed in the Details tab of the Nexus dvSwitch in the
+CloudStack UI:
+
+**Control Port Group VLAN ID**
+The VLAN ID of the Control Port Group. The control VLAN is used for
+communication between the VSM and the VEMs.
+
+**Management Port Group VLAN ID**
+The VLAN ID of the Management Port Group. The management VLAN corresponds to
+the mgmt0 interface that is used to establish and maintain the connection
+between the VSM and VMware vCenter Server.
+
+**Packet Port Group VLAN ID**
+The VLAN ID of the Packet Port Group. The packet VLAN forwards relevant data
+packets from the VEMs to the VSM.
+
+.. note::
+ The VLANs used for control, packet, and management port groups can be the
+ same.
+
+For more information, see `Cisco Nexus 1000V Getting Started Guide
+<http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_b/getting_started/configuration/guide/n1000v_gsg.pdf>`_.
+
+
+VSM Configuration Checklist
+'''''''''''''''''''''''''''
+
+You will need the following VSM configuration parameters:
+
+**Admin Name and Password**
+The admin name and password to connect to the VSM appliance. You must specify
+these credentials while configuring Nexus virtual switch.
+
+**Management IP Address**
+This is the IP address of the VSM appliance. This is the IP address you
+specify in the virtual switch IP Address field while configuting Nexus virtual
+switch.
+
+**SSL**
+Should be set to Enable.Always enable SSL. SSH is usually enabled by default
+during the VSM installation. However, check whether the SSH connection to the
+VSM is working, without which CloudStack failes to connect to the VSM.
+
+
+Creating a Port Profile
+'''''''''''''''''''''''
+
+- Whether you create a Basic or Advanced zone configuration, ensure
+ that you always create an Ethernet port profile on the VSM after you
+ install it and before you create the zone.
+
+ - The Ethernet port profile created to represent the physical
+ network or networks used by an Advanced zone configuration trunk
+ all the VLANs including guest VLANs, the VLANs that serve the
+ native VLAN, and the packet/control/data/management VLANs of the
+ VSM.
+
+ - The Ethernet port profile created for a Basic zone configuration
+ does not trunk the guest VLANs because the guest VMs do not get
+ their own VLANs provisioned on their network interfaces in a Basic
+ zone.
+
+- An Ethernet port profile configured on the Nexus 1000v virtual switch
+ should not use in its set of system VLANs, or any of the VLANs
+ configured or intended to be configured for use towards VMs or VM
+ resources in the CloudStack environment.
+
+- You do not have to create any vEthernet port profiles – CloudStack
+ does that during VM deployment.
+
+- Ensure that you create required port profiles to be used by
+ CloudStack for different traffic types of CloudStack, such as
+ Management traffic, Guest traffic, Storage traffic, and Public
+ traffic. The physical networks configured during zone creation should
+ have a one-to-one relation with the Ethernet port profiles.
+
+|vmwarenexusportprofile.png: vSphere client|
+
+For information on creating a port profile, see `Cisco Nexus 1000V Port
+Profile Configuration Guide
+<http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_a/port_profile/configuration/guide/n1000v_port_profile.html>`_.
+
+
+Assigning Physical NIC Adapters
+'''''''''''''''''''''''''''''''
+
+Assign ESXi host's physical NIC adapters, which correspond to each
+physical network, to the port profiles. In each ESXi host that is part
+of the vCenter cluster, observe the physical networks assigned to each
+port profile and note down the names of the port profile for future use.
+This mapping information helps you when configuring physical networks
+during the zone configuration on CloudStack. These Ethernet port profile
+names are later specified as VMware Traffic Labels for different traffic
+types when configuring physical networks during the zone configuration.
+For more information on configuring physical networks, see
+:ref:`configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch`.
+
+
+Adding VLAN Ranges
+''''''''''''''''''
+
+Determine the public VLAN, System VLAN, and Guest VLANs to be used by
+the CloudStack. Ensure that you add them to the port profile database.
+Corresponding to each physical network, add the VLAN range to port
+profiles. In the VSM command prompt, run the switchport trunk allowed
+vlan<range> command to add the VLAN ranges to the port profile.
+
+For example:
+
+.. parsed-literal::
+
+ switchport trunk allowed vlan 1,140-147,196-203
+
+In this example, the allowed VLANs added are 1, 140-147, and 196-203
+
+You must also add all the public and private VLANs or VLAN ranges to the
+switch. This range is the VLAN range you specify in your zone.
+
+.. note::
+ Before you run the vlan command, ensure that the configuration mode is
+ enabled in Nexus 1000v virtual switch.
+
+For example:
+
+If you want the VLAN 200 to be used on the switch, run the following
+command:
+
+.. parsed-literal::
+
+ vlan 200
+
+If you want the VLAN range 1350-1750 to be used on the switch, run the
+following command:
+
+.. parsed-literal::
+
+ vlan 1350-1750
+
+Refer to Cisco Nexus 1000V Command Reference of specific product
+version.
+
+
+Enabling Nexus Virtual Switch in CloudStack
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+To make a CloudStack deployment Nexus enabled, you must set the
+vmware.use.nexus.vswitch parameter true by using the Global Settings
+page in the CloudStack UI. Unless this parameter is set to "true" and
+restart the management server, you cannot see any UI options specific to
+Nexus virtual switch, and CloudStack ignores the Nexus virtual switch
+specific parameters specified in the AddTrafficTypeCmd,
+UpdateTrafficTypeCmd, and AddClusterCmd API calls.
+
+Unless the CloudStack global parameter "vmware.use.nexus.vswitch" is set
+to "true", CloudStack by default uses VMware standard vSwitch for
+virtual network infrastructure. In this release, CloudStack doesn’t
+support configuring virtual networks in a deployment with a mix of
+standard vSwitch and Nexus 1000v virtual switch. The deployment can have
+either standard vSwitch or Nexus 1000v virtual switch.
+
+
+Configuring Nexus 1000v Virtual Switch in CloudStack
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+You can configure Nexus dvSwitch by adding the necessary resources while
+the zone is being created.
+
+|vmwarenexusaddcluster.png: vmware nexus add cluster|
+
+After the zone is created, if you want to create an additional cluster
+along with Nexus 1000v virtual switch in the existing zone, use the Add
+Cluster option. For information on creating a cluster, see
+`"Add Cluster: vSphere" <configuration.html#add-cluster-vsphere>`_.
+
+In both these cases, you must specify the following parameters to
+configure Nexus virtual switch:
+
+.. cssclass:: table-striped table-bordered table-hover
+
+========================= =======================================================================================================================
+Parameters Description
+========================= =======================================================================================================================
+Cluster Name Enter the name of the cluster you created in vCenter. For example,"cloud.cluster".
+vCenter Host Enter the host name or the IP address of the vCenter host where you have deployed the Nexus virtual switch.
+vCenter User name Enter the username that CloudStack should use to connect to vCenter. This user must have all administrative privileges.
+vCenter Password Enter the password for the user named above.
+vCenter Datacenter Enter the vCenter datacenter that the cluster is in. For example, "cloud.dc.VM".
+Nexus dvSwitch IP Address The IP address of the VSM component of the Nexus 1000v virtual switch.
+Nexus dvSwitch Username The admin name to connect to the VSM appliance.
+Nexus dvSwitch Password The corresponding password for the admin user specified above.
+========================= =======================================================================================================================
+
+
+Removing Nexus Virtual Switch
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. In the vCenter datacenter that is served by the Nexus virtual switch,
+ ensure that you delete all the hosts in the corresponding cluster.
+
+#. Log in with Admin permissions to the CloudStack administrator UI.
+
+#. In the left navigation bar, select Infrastructure.
+
+#. In the Infrastructure page, click View all under Clusters.
+
+#. Select the cluster where you want to remove the virtual switch.
+
+#. In the dvSwitch tab, click the name of the virtual switch.
+
+#. In the Details page, click Delete Nexus dvSwitch icon.
+ |DeleteButton.png: button to delete dvSwitch|
+
+ Click Yes in the confirmation dialog box.
+
+
+Configuring a VMware Datacenter with VMware Distributed Virtual Switch
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack supports VMware vNetwork Distributed Switch (VDS) for virtual
+network configuration in a VMware vSphere environment. This section
+helps you configure VMware VDS in a CloudStack deployment. Each vCenter
+server instance can support up to 128 VDS instances and each VDS
+instance can manage up to 500 VMware hosts.
+
+
+About VMware Distributed Virtual Switch
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+VMware VDS is an aggregation of host-level virtual switches on a VMware
+vCenter server. VDS abstracts the configuration of individual virtual
+switches that span across a large number of hosts, and enables
+centralized provisioning, administration, and monitoring for your entire
+datacenter from a centralized interface. In effect, a VDS acts as a
+single virtual switch at the datacenter level and manages networking for
+a number of hosts in a datacenter from a centralized VMware vCenter
+server. Each VDS maintains network runtime state for VMs as they move
+across multiple hosts, enabling inline monitoring and centralized
+firewall services. A VDS can be deployed with or without Virtual
+Standard Switch and a Nexus 1000V virtual switch.
+
+
+Prerequisites and Guidelines
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+- VMware VDS is supported only on Public and Guest traffic in
+ CloudStack.
+
+- VMware VDS does not support multiple VDS per traffic type. If a user
+ has many VDS switches, only one can be used for Guest traffic and
+ another one for Public traffic.
+
+- Additional switches of any type can be added for each cluster in the
+ same zone. While adding the clusters with different switch type,
+ traffic labels is overridden at the cluster level.
+
+- Management and Storage network does not support VDS. Therefore, use
+ Standard Switch for these networks.
+
+- When you remove a guest network, the corresponding dvportgroup will
+ not be removed on the vCenter. You must manually delete them on the
+ vCenter.
+
+
+Preparation Checklist
+^^^^^^^^^^^^^^^^^^^^^
+
+For a smoother configuration of VMware VDS, note down the VDS name you
+have added in the datacenter before you start:
+
+|vds-name.png: Name of the dvSwitch as specified in the vCenter.|
+
+Use this VDS name in the following:
+
+- The switch name in the Edit traffic label dialog while configuring a
+ public and guest traffic during zone creation.
+
+ During a zone creation, ensure that you select VMware vNetwork
+ Distributed Virtual Switch when you configure guest and public
+ traffic type.
+
+ |traffic-type.png|
+
+- The Public Traffic vSwitch Type field when you add a VMware
+ VDS-enabled cluster.
+
+- The switch name in the traffic label while updating the switch type
+ in a zone.
+
+Traffic label format in the last case is
+[["Name of vSwitch/dvSwitch/EthernetPortProfile"][,"VLAN ID"[,"vSwitch Type"]]]
+
+The possible values for traffic labels are:
+
+- empty string
+
+- dvSwitch0
+
+- dvSwitch0,200
+
+- dvSwitch1,300,vmwaredvs
+
+- myEthernetPortProfile,,nexusdvs
+
+- dvSwitch0,,vmwaredvs
+
+
+The three fields to fill in are:
+
+- Name of the virtual / distributed virtual switch at vCenter.
+
+ The default value depends on the type of virtual switch:
+
+ **vSwitch0**: If type of virtual switch is VMware vNetwork Standard virtual
+ switch
+
+ **dvSwitch0**: If type of virtual switch is VMware vNetwork Distributed
+ virtual switch
+
+ **epp0**: If type of virtual switch is Cisco Nexus 1000v Distributed
+ virtual switch
+
+- VLAN ID to be used for this traffic wherever applicable.
+
+ This field would be used for only public traffic as of now. In case of
+ guest traffic this field would be ignored and could be left empty for guest
+ traffic. By default empty string would be assumed which translates to
+ untagged VLAN for that specific traffic type.
+
+- Type of virtual switch. Specified as string.
+
+ Possible valid values are vmwaredvs, vmwaresvs, nexusdvs.
+
+ **vmwaresvs**: Represents VMware vNetwork Standard virtual switch
+
+ **vmwaredvs**: Represents VMware vNetwork distributed virtual switch
+
+ **nexusdvs**: Represents Cisco Nexus 1000v distributed virtual switch.
+
+ If nothing specified (left empty), zone-level default virtual switchwould
+ be defaulted, based on the value of global parameter you specify.
+
+ Following are the global configuration parameters:
+
+ **vmware.use.dvswitch**: Set to true to enable any kind (VMware DVS and
+ Cisco Nexus 1000v) of distributed virtual switch in a CloudStack
+ deployment. If set to false, the virtual switch that can be used in that
+ CloudStack deployment is Standard virtual switch.
+
+ **vmware.use.nexus.vswitch**: This parameter is ignored if
+ vmware.use.dvswitch is set to false. Set to true to enable Cisco Nexus
+ 1000v distributed virtual switch in a CloudStack deployment.
+
+
+Enabling Virtual Distributed Switch in CloudStack
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+To make a CloudStack deployment VDS enabled, set the vmware.use.dvswitch
+parameter to true by using the Global Settings page in the CloudStack UI
+and restart the Management Server. Unless you enable the
+vmware.use.dvswitch parameter, you cannot see any UI options specific to
+VDS, and CloudStack ignores the VDS-specific parameters that you
+specify. Additionally, CloudStack uses VDS for virtual network
+infrastructure if the value of vmware.use.dvswitch parameter is true and
+the value of vmware.use.nexus.dvswitch parameter is false. Another
+global parameter that defines VDS configuration is
+vmware.ports.per.dvportgroup. This is the default number of ports per
+VMware dvPortGroup in a VMware environment. Default value is 256. This
+number directly associated with the number of guest network you can
+create.
+
+CloudStack supports orchestration of virtual networks in a deployment
+with a mix of Virtual Distributed Switch, Standard Virtual Switch and
+Nexus 1000v Virtual Switch.
+
+
+Configuring Distributed Virtual Switch in CloudStack
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+You can configure VDS by adding the necessary resources while a zone is
+created.
+
+Alternatively, at the cluster level, you can create an additional
+cluster with VDS enabled in the existing zone. Use the Add Cluster
+option. For information as given in `“Add Cluster: vSphere”
+<configuration.html#add-cluster-vsphere>`_.
+
+In both these cases, you must specify the following parameters to
+configure VDS:
+
+|dvSwitchConfig.png: Configuring dvSwitch|
+
+.. cssclass:: table-striped table-bordered table-hover
+
+================================= ===================================================================================================================
+Parameters Description
+================================= ===================================================================================================================
+Cluster Name Enter the name of the cluster you created in vCenter. For example, "cloudcluster".
+vCenter Host Enter the name or the IP address of the vCenter host where you have deployed the VMware VDS.
+vCenter User name Enter the username that CloudStack should use to connect to vCenter. This user must have all administrative privileges.
+vCenter Password Enter the password for the user named above.
+vCenter Datacenter Enter the vCenter datacenter that the cluster is in. For example, "clouddcVM".
+Override Public Traffic Enable this option to override the zone-wide public traffic for the cluster you are creating.
+Public Traffic vSwitch Type This option is displayed only if you enable the Override Public Traffic option. Select VMware vNetwork Distributed Virtual Switch. If the vmware.use.dvswitch global parameter is true, the default option will be VMware vNetwork Distributed Virtual Switch.
+Public Traffic vSwitch Name Name of virtual switch to be used for the public traffic.
+Override Guest Traffic Enable the option to override the zone-wide guest traffic for the cluster you are creating.
+Guest Traffic vSwitch Type This option is displayed only if you enable the Override Guest Traffic option. Select VMware vNetwork Distributed Virtual Switch. If the vmware.use.dvswitch global parameter is true, the default option will be VMware vNetwork Distributed Virtual Switch.
+Guest Traffic vSwitch Name Name of virtual switch to be used for guest traffic.
+================================= ===================================================================================================================
+
+
+Storage Preparation for vSphere (iSCSI only)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Use of iSCSI requires preparatory work in vCenter. You must add an iSCSI
+target and create an iSCSI datastore.
+
+If you are using NFS, skip this section.
+
+
+Enable iSCSI initiator for ESXi hosts
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+#. In vCenter, go to hosts and Clusters/Configuration, and click Storage
+ Adapters link. You will see:
+
+ |vmwareiscsiinitiator.png: iscsi initiator|
+
+#. Select iSCSI software adapter and click Properties.
+
+ |vmwareiscsiinitiatorproperties.png: iscsi initiator properties|
+
+#. Click the Configure... button.
+
+ |vmwareiscsigeneral.png: iscsi general|
+
+#. Check Enabled to enable the initiator.
+
+#. Click OK to save.
+
+
+Add iSCSI target
+^^^^^^^^^^^^^^^^
+
+Under the properties dialog, add the iSCSI target info:
+
+|vmwareiscsitargetadd.png: iscsi target add|
+
+Repeat these steps for all ESXi hosts in the cluster.
+
+
+Create an iSCSI datastore
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+You should now create a VMFS datastore. Follow these steps to do so:
+
+#. Select Home/Inventory/Datastores.
+
+#. Right click on the datacenter node.
+
+#. Choose Add Datastore... command.
+
+#. Follow the wizard to create a iSCSI datastore.
+
+This procedure should be done on one host in the cluster. It is not
+necessary to do this on all hosts.
+
+|vmwareiscsidatastore.png: iscsi datastore|
+
+
+Multipathing for vSphere (Optional)
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Storage multipathing on vSphere nodes may be done according to the
+vSphere installation guide.
+
+
+Add Hosts or Configure Clusters (vSphere)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Use vCenter to create a vCenter cluster and add your desired hosts to
+the cluster. You will later add the entire cluster to CloudStack. (see
+`“Add Cluster: vSphere” <configuration.html#add-cluster-vsphere>`_).
+
+
+Applying Hotfixes to a VMware vSphere Host
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. Disconnect the VMware vSphere cluster from CloudStack. It should
+ remain disconnected long enough to apply the hotfix on the host.
+
+ #. Log in to the CloudStack UI as root.
+
+ See :ref:`log-in-to-ui`
+
+ #. Navigate to the VMware cluster, click Actions, and select
+ Unmanage.
+
+ #. Watch the cluster status until it shows Unmanaged.
+
+#. Perform the following on each of the ESXi hosts in the cluster:
+
+ #. Move each of the ESXi hosts in the cluster to maintenance mode.
+
+ #. Ensure that all the VMs are migrated to other hosts in that
+ cluster.
+
+ #. If there is only one host in that cluster, shutdown all the VMs
+ and move the host into maintenance mode.
+
+ #. Apply the patch on the ESXi host.
+
+ #. Restart the host if prompted.
+
+ #. Cancel the maintenance mode on the host.
+
+#. Reconnect the cluster to CloudStack:
+
+ #. Log in to the CloudStack UI as root.
+
+ #. Navigate to the VMware cluster, click Actions, and select Manage.
+
+ #. Watch the status to see that all the hosts come up. It might take
+ several minutes for the hosts to come up.
+
+ Alternatively, verify the host state is properly synchronized and
+ updated in the CloudStack database.
+
+
+.. |DeleteButton.png: button to delete dvSwitch| image:: /_static/images/delete-button.png
+.. |vds-name.png: Name of the dvSwitch as specified in the vCenter.| image:: /_static/images/vds-name.png
+.. |traffic-type.png| image:: /_static/images/traffic-type.png
+.. |dvSwitchConfig.png: Configuring dvSwitch| image:: /_static/images/dvswitchconfig.png
+.. |vsphereclient.png: vSphere client| image:: /_static/images/vsphere-client.png
+.. |vspherephysicalnetwork.png: vSphere client| image:: /_static/images/vmware-physical-network.png
+.. |vsphereincreaseports.png: vSphere client| image:: /_static/images/vmware-increase-ports.png
+.. |vspherevswitchproperties.png: vSphere client| image:: /_static/images/vmware-vswitch-properties.png
+.. |vspheremgtnetwork.png: vSphere client| image:: /_static/images/vmware-mgt-network-properties.png
+.. |vmwarenexusportprofile.png: vSphere client| image:: /_static/images/vmware-nexus-port-profile.png
+.. |vmwarenexusaddcluster.png: vmware nexus add cluster| image:: /_static/images/vmware-nexus-add-cluster.png
+.. |vmwareiscsiinitiator.png: iscsi initiator| image:: /_static/images/vmware-iscsi-initiator.png
+.. |vmwareiscsiinitiatorproperties.png: iscsi initiator properties| image:: /_static/images/vmware-iscsi-initiator-properties.png
+.. |vmwareiscsigeneral.png: iscsi general| image:: /_static/images/vmware-iscsi-general.png
+.. |vmwareiscsitargetadd.png: iscsi target add| image:: /_static/images/vmware-iscsi-target-add.png
+.. |vmwareiscsidatastore.png: iscsi datastore| image:: /_static/images/vmware-iscsi-datastore.png
diff --git a/source/installguide/hypervisor/xenserver.rst b/source/installguide/hypervisor/xenserver.rst
new file mode 100644
index 0000000..76112f5
--- /dev/null
+++ b/source/installguide/hypervisor/xenserver.rst
@@ -0,0 +1,816 @@
+.. 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.
+
+
+Host Citrix XenServer Installation
+----------------------------------
+
+If you want to use the Citrix XenServer hypervisor to run guest virtual
+machines, install XenServer 6.0 or XenServer 6.0.2 on the host(s) in
+your cloud. For an initial installation, follow the steps below. If you
+have previously installed XenServer and want to upgrade to another
+version, see :ref:`upgrading-xenserver-version`.
+
+
+System Requirements for XenServer Hosts
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- The host must be certified as compatible with one of the following.
+ See the Citrix Hardware Compatibility Guide:
+ `http://hcl.xensource.com <http://hcl.xensource.com>`_
+
+ - XenServer 5.6 SP2
+ - XenServer 6.0
+ - XenServer 6.0.2
+ - XenServer 6.1.0
+ - XenServer 6.2.0
+ - XenServer 6.5.0
+
+- You must re-install Citrix XenServer if you are going to re-use a
+ host from a previous install.
+
+- Must support HVM (Intel-VT or AMD-V enabled)
+
+- 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.
+
+- All hosts within a cluster must be homogeneous. The CPUs must be of
+ the same type, count, and feature flags.
+
+- Must support HVM (Intel-VT or AMD-V enabled in BIOS)
+
+- 64-bit x86 CPU (more cores results in better performance)
+
+- Hardware virtualization support required
+
+- 4 GB of memory
+
+- 36 GB of local disk
+
+- At least 1 NIC
+
+- Statically allocated IP Address
+
+- When you deploy CloudStack, the hypervisor host must not have any VMs
+ already running
+
+.. warning::
+ The lack of up-to-date hotfixes can lead to data corruption and lost VMs.
+
+
+XenServer Installation Steps
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. From `https://www.citrix.com/English/ss/downloads/
+ <https://www.citrix.com/English/ss/downloads/>`_,
+ download the appropriate version of XenServer for your CloudStack
+ version (see `"System Requirements for XenServer Hosts"
+ <#system-requirements-for-xenserver-hosts>`_). Install it using
+ the Citrix XenServer Installation Guide.
+
+ Older Versions of XenServer:
+
+ Note that you can download the most recent release of XenServer
+ without having a Citrix account. If you wish to download older
+ versions, you will need to create an account and look through the
+ download archives.
+
+
+Configure XenServer dom0 Memory
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Configure the XenServer dom0 settings to allocate more memory to dom0.
+This can enable XenServer to handle larger numbers of virtual machines.
+We recommend 2940 MB of RAM for XenServer dom0. For instructions on how
+to do this, see `http://support.citrix.com/article/CTX126531
+<http://support.citrix.com/article/CTX126531>`_. The article refers to
+XenServer 5.6, but the same information applies to XenServer 6.0.
+
+
+Username and Password
+~~~~~~~~~~~~~~~~~~~~~
+
+All XenServers in a cluster must have the same username and password as
+configured in CloudStack.
+
+
+Time Synchronization
+~~~~~~~~~~~~~~~~~~~~
+
+The host must be set to use NTP. All hosts in a pod must have the same
+time.
+
+#. Install NTP.
+
+ .. parsed-literal::
+
+ # yum install ntp
+
+#. Edit the NTP configuration file to point to your NTP server.
+
+ .. parsed-literal::
+
+ # vi /etc/ntp.conf
+
+ Add one or more server lines in this file with the names of the NTP
+ servers you want to use. For example:
+
+ .. parsed-literal::
+
+ server 0.xenserver.pool.ntp.org
+ server 1.xenserver.pool.ntp.org
+ server 2.xenserver.pool.ntp.org
+ server 3.xenserver.pool.ntp.org
+
+#. Restart the NTP client.
+
+ .. parsed-literal::
+
+ # service ntpd restart
+
+#. Make sure NTP will start again upon reboot.
+
+ .. parsed-literal::
+
+ # chkconfig ntpd on
+
+
+Install CloudStack XenServer Support Package (CSP)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+(Optional)
+
+To enable security groups, elastic load balancing, and elastic IP on
+XenServer, download and install the CloudStack XenServer Support Package
+(CSP). After installing XenServer, perform the following additional
+steps on each XenServer host.
+
+**For XenServer 6.1:**
+
+CSP functionality is already present in XenServer 6.1
+
+#. Run the below command
+
+ .. parsed-literal::
+
+ xe-switch-network-backend bridge
+
+#. update sysctl.conf with the following
+
+ .. parsed-literal::
+
+ net.bridge.bridge-nf-call-iptables = 1
+ net.bridge.bridge-nf-call-ip6tables = 0
+ net.bridge.bridge-nf-call-arptables = 1
+
+ $ sysctl -p /etc/sysctl.conf
+
+
+**For XenServer 6.0.2, 6.0, 5.6 SP2:**
+
+#. Download the CSP software onto the XenServer host from one of the
+ following links:
+
+ For XenServer 6.0.2:
+
+ `http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz
+ <http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz>`_
+
+ For XenServer 5.6 SP2:
+
+ `http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz
+ <http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz>`_
+
+ For XenServer 6.0:
+
+ `http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz
+ <http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz>`_
+
+
+#. Extract the file:
+
+ .. parsed-literal::
+
+ # tar xf xenserver-cloud-supp.tgz
+
+#. Run the following script:
+
+ .. parsed-literal::
+
+ # xe-install-supplemental-pack xenserver-cloud-supp.iso
+
+#. If the XenServer host is part of a zone that uses basic networking,
+ disable Open vSwitch (OVS):
+
+ .. parsed-literal::
+
+ # xe-switch-network-backend bridge
+
+ Restart the host machine when prompted.
+
+The XenServer host is now ready to be added to CloudStack.
+
+
+Primary Storage Setup for XenServer
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack natively supports NFS, iSCSI and local storage. If you are
+using one of these storage types, there is no need to create the
+XenServer Storage Repository ("SR").
+
+If, however, you would like to use storage connected via some other
+technology, such as FiberChannel, you must set up the SR yourself. To do
+so, perform the following steps. If you have your hosts in a XenServer
+pool, perform the steps on the master node. If you are working with a
+single XenServer which is not part of a cluster, perform the steps on
+that XenServer.
+
+#. Connect FiberChannel cable to all hosts in the cluster and to the
+ FiberChannel storage host.
+
+#. Rescan the SCSI bus. Either use the following command or use
+ XenCenter to perform an HBA rescan.
+
+ .. parsed-literal::
+
+ # scsi-rescan
+
+#. Repeat step 2 on every host.
+
+#. Check to be sure you see the new SCSI disk.
+
+ .. parsed-literal::
+
+ # ls /dev/disk/by-id/scsi-360a98000503365344e6f6177615a516b -l
+
+ The output should look like this, although the specific file name
+ will be different (scsi-<scsiID>):
+
+ .. parsed-literal::
+
+ lrwxrwxrwx 1 root root 9 Mar 16 13:47
+ /dev/disk/by-id/scsi-360a98000503365344e6f6177615a516b -> ../../sdc
+
+#. Repeat step 4 on every host.
+
+#. On the storage server, run this command to get a unique ID for the
+ new SR.
+
+ .. parsed-literal::
+
+ # uuidgen
+
+ The output should look like this, although the specific ID will be
+ different:
+
+ .. parsed-literal::
+
+ e6849e96-86c3-4f2c-8fcc-350cc711be3d
+
+#. Create the FiberChannel SR. In name-label, use the unique ID you just
+ generated.
+
+ .. parsed-literal::
+
+ # xe sr-create type=lvmohba shared=true
+ device-config:SCSIid=360a98000503365344e6f6177615a516b
+ name-label="e6849e96-86c3-4f2c-8fcc-350cc711be3d"
+
+ This command returns a unique ID for the SR, like the following
+ example (your ID will be different):
+
+ .. parsed-literal::
+
+ 7a143820-e893-6c6a-236e-472da6ee66bf
+
+#. To create a human-readable description for the SR, use the following
+ command. In uuid, use the SR ID returned by the previous command. In
+ name-description, set whatever friendly text you prefer.
+
+ .. parsed-literal::
+
+ # xe sr-param-set uuid=7a143820-e893-6c6a-236e-472da6ee66bf name-description="Fiber Channel storage repository"
+
+ Make note of the values you will need when you add this storage to
+ CloudStack later (see `"Add Primary Storage"
+ <configuration.html#add-primary-storage>`_). In the Add Primary Storage
+ dialog, in Protocol, you will choose PreSetup. In SR Name-Label, you
+ will enter the name-label you set earlier (in this example,
+ e6849e96-86c3-4f2c-8fcc-350cc711be3d).
+
+#. (Optional) If you want to enable multipath I/O on a FiberChannel SAN,
+ refer to the documentation provided by the SAN vendor.
+
+
+iSCSI Multipath Setup for XenServer (Optional)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When setting up the storage repository on a Citrix XenServer, you can
+enable multipath I/O, which uses redundant physical components to
+provide greater reliability in the connection between the server and the
+SAN. To enable multipathing, use a SAN solution that is supported for
+Citrix servers and follow the procedures in Citrix documentation. The
+following links provide a starting point:
+
+- `http://support.citrix.com/article/CTX118791
+ <http://support.citrix.com/article/CTX118791>`_
+
+- `http://support.citrix.com/article/CTX125403
+ <http://support.citrix.com/article/CTX125403>`_
+
+You can also ask your SAN vendor for advice about setting up your Citrix
+repository for multipathing.
+
+Make note of the values you will need when you add this storage to the
+CloudStack later (see `"Add Primary Storage"
+<configuration.html#add-primary-storage>`_). In the Add Primary Storage
+dialog, in Protocol, you will choose PreSetup. In SR Name-Label, you will
+enter the same name used to create the SR.
+
+If you encounter difficulty, address the support team for the SAN
+provided by your vendor. If they are not able to solve your issue, see
+Contacting Support.
+
+
+Physical Networking Setup for XenServer
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Once XenServer has been installed, you may need to do some additional
+network configuration. At this point in the installation, you should
+have a plan for what NICs the host will have and what traffic each NIC
+will carry. The NICs should be cabled as necessary to implement your
+plan.
+
+If you plan on using NIC bonding, the NICs on all hosts in the cluster
+must be cabled exactly the same. For example, if eth0 is in the private
+bond on one host in a cluster, then eth0 must be in the private bond on
+all hosts in the cluster.
+
+The IP address assigned for the management network interface must be
+static. It can be set on the host itself or obtained via static DHCP.
+
+CloudStack configures network traffic of various types to use different
+NICs or bonds on the XenServer host. You can control this process and
+provide input to the Management Server through the use of XenServer
+network name labels. The name labels are placed on physical interfaces
+or bonds and configured in CloudStack. In some simple cases the name
+labels are not required.
+
+When configuring networks in a XenServer environment, network traffic
+labels must be properly configured to ensure that the virtual interfaces
+are created by CloudStack are bound to the correct physical device. The
+name-label of the XenServer network must match the XenServer traffic
+label specified while creating the CloudStack network. This is set by
+running the following command:
+
+.. parsed-literal::
+
+ xe network-param-set uuid=<network id> name-label=<CloudStack traffic label>
+
+
+Configuring Public Network with a Dedicated NIC for XenServer (Optional)
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+CloudStack supports the use of a second NIC (or bonded pair of NICs,
+described in :ref:`nic-bonding-for-xenserver`) for the public network. If
+bonding is not used, the public network can be on any NIC and can be on
+different NICs on the hosts in a cluster. For example, the public
+network can be on eth0 on node A and eth1 on node B. However, the
+XenServer name-label for the public network must be identical across all
+hosts. The following examples set the network label to "cloud-public".
+After the management server is installed and running you must configure
+it with the name of the chosen network label (e.g. "cloud-public"); this
+is discussed in `"Management Server Installation"
+<installation.html#management-server-installation>`_.
+
+If you are using two NICs bonded together to create a public network,
+see :ref:`nic-bonding-for-xenserver`.
+
+If you are using a single dedicated NIC to provide public network
+access, follow this procedure on each new host that is added to
+CloudStack before adding the host.
+
+#. Run xe network-list and find the public network. This is usually
+ attached to the NIC that is public. Once you find the network make
+ note of its UUID. Call this <UUID-Public>.
+
+#. Run the following command.
+
+ .. parsed-literal::
+
+ # xe network-param-set name-label=cloud-public uuid=<UUID-Public>
+
+
+Configuring Multiple Guest Networks for XenServer (Optional)
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+CloudStack supports the use of multiple guest networks with the
+XenServer hypervisor. Each network is assigned a name-label in
+XenServer. For example, you might have two networks with the labels
+"cloud-guest" and "cloud-guest2". After the management server is
+installed and running, you must add the networks and use these labels so
+that CloudStack is aware of the networks.
+
+Follow this procedure on each new host before adding the host to
+CloudStack:
+
+#. Run xe network-list and find one of the guest networks. Once you find
+ the network make note of its UUID. Call this <UUID-Guest>.
+
+#. Run the following command, substituting your own name-label and uuid
+ values.
+
+ .. parsed-literal::
+
+ # xe network-param-set name-label=<cloud-guestN> uuid=<UUID-Guest>
+
+#. Repeat these steps for each additional guest network, using a
+ different name-label and uuid each time.
+
+
+Separate Storage Network for XenServer (Optional)
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+You can optionally set up a separate storage network. This should be
+done first on the host, before implementing the bonding steps below.
+This can be done using one or two available NICs. With two NICs bonding
+may be done as above. It is the administrator's responsibility to set up
+a separate storage network.
+
+Give the storage network a different name-label than what will be given
+for other networks.
+
+For the separate storage network to work correctly, it must be the only
+interface that can ping the primary storage device's IP address. For
+example, if eth0 is the management network NIC, ping -I eth0 <primary
+storage device IP> must fail. In all deployments, secondary storage
+devices must be pingable from the management network NIC or bond. If a
+secondary storage device has been placed on the storage network, it must
+also be pingable via the storage network NIC or bond on the hosts as
+well.
+
+You can set up two separate storage networks as well. For example, if
+you intend to implement iSCSI multipath, dedicate two non-bonded NICs to
+multipath. Each of the two networks needs a unique name-label.
+
+If no bonding is done, the administrator must set up and name-label the
+separate storage network on all hosts (masters and slaves).
+
+Here is an example to set up eth5 to access a storage network on
+172.16.0.0/24.
+
+.. parsed-literal::
+
+ # xe pif-list host-name-label='hostname' device=eth5
+ uuid(RO): ab0d3dd4-5744-8fae-9693-a022c7a3471d
+ device ( RO): eth5
+ #xe pif-reconfigure-ip DNS=172.16.3.3 gateway=172.16.0.1 IP=172.16.0.55 mode=static netmask=255.255.255.0 uuid=ab0d3dd4-5744-8fae-9693-a022c7a3471d
+
+
+.. _nic-bonding-for-xenserver:
+
+NIC Bonding for XenServer (Optional)
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+XenServer supports Source Level Balancing (SLB) NIC bonding. Two NICs
+can be bonded together to carry public, private, and guest traffic, or
+some combination of these. Separate storage networks are also possible.
+Here are some example supported configurations:
+
+- 2 NICs on private, 2 NICs on public, 2 NICs on storage
+
+- 2 NICs on private, 1 NIC on public, storage uses management network
+
+- 2 NICs on private, 2 NICs on public, storage uses management network
+
+- 1 NIC for private, public, and storage
+
+All NIC bonding is optional.
+
+XenServer expects all nodes in a cluster will have the same network
+cabling and same bonds implemented. In an installation the master will
+be the first host that was added to the cluster and the slave hosts will
+be all subsequent hosts added to the cluster. The bonds present on the
+master set the expectation for hosts added to the cluster later. The
+procedure to set up bonds on the master and slaves are different, and
+are described below. There are several important implications of this:
+
+- You must set bonds on the first host added to a cluster. Then you
+ must use xe commands as below to establish the same bonds in the
+ second and subsequent hosts added to a cluster.
+
+- Slave hosts in a cluster must be cabled exactly the same as the
+ master. For example, if eth0 is in the private bond on the master, it
+ must be in the management network for added slave hosts.
+
+
+Management Network Bonding
+''''''''''''''''''''''''''
+
+The administrator must bond the management network NICs prior to adding
+the host to CloudStack.
+
+
+Creating a Private Bond on the First Host in the Cluster
+''''''''''''''''''''''''''''''''''''''''''''''''''''''''
+
+Use the following steps to create a bond in XenServer. These steps
+should be run on only the first host in a cluster. This example creates
+the cloud-private network with two physical NICs (eth0 and eth1) bonded
+into it.
+
+#. Find the physical NICs that you want to bond together.
+
+ .. parsed-literal::
+
+ # xe pif-list host-name-label='hostname' device=eth0
+ # xe pif-list host-name-label='hostname' device=eth1
+
+ These command shows the eth0 and eth1 NICs and their UUIDs.
+ Substitute the ethX devices of your choice. Call the UUID's returned
+ by the above command slave1-UUID and slave2-UUID.
+
+#. Create a new network for the bond. For example, a new network with
+ name "cloud-private".
+
+ **This label is important. CloudStack looks for a network by a name
+ you configure. You must use the same name-label for all hosts in the
+ cloud for the management network.**
+
+ .. parsed-literal::
+
+ # xe network-create name-label=cloud-private
+ # xe bond-create network-uuid=[uuid of cloud-private created above]
+ pif-uuids=[slave1-uuid],[slave2-uuid]
+
+Now you have a bonded pair that can be recognized by CloudStack as the
+management network.
+
+
+Public Network Bonding
+''''''''''''''''''''''
+
+Bonding can be implemented on a separate, public network. The
+administrator is responsible for creating a bond for the public network
+if that network will be bonded and will be separate from the management
+network.
+
+
+Creating a Public Bond on the First Host in the Cluster
+'''''''''''''''''''''''''''''''''''''''''''''''''''''''
+
+These steps should be run on only the first host in a cluster. This
+example creates the cloud-public network with two physical NICs (eth2
+and eth3) bonded into it.
+
+#. Find the physical NICs that you want to bond together.
+
+ .. parsed-literal::
+
+ # xe pif-list host-name-label='hostname' device=eth2
+ # xe pif-list host-name-label='hostname' device=eth3
+
+ These command shows the eth2 and eth3 NICs and their UUIDs.
+ Substitute the ethX devices of your choice. Call the UUID's returned
+ by the above command slave1-UUID and slave2-UUID.
+
+#. Create a new network for the bond. For example, a new network with
+ name "cloud-public".
+
+ **This label is important. CloudStack looks for a network by a name
+ you configure. You must use the same name-label for all hosts in the
+ cloud for the public network.**
+
+ .. parsed-literal::
+
+ # xe network-create name-label=cloud-public
+ # xe bond-create network-uuid=[uuid of cloud-public created above]
+ pif-uuids=[slave1-uuid],[slave2-uuid]
+
+Now you have a bonded pair that can be recognized by CloudStack as the
+public network.
+
+
+Adding More Hosts to the Cluster
+''''''''''''''''''''''''''''''''
+
+With the bonds (if any) established on the master, you should add
+additional, slave hosts. Run the following command for all additional
+hosts to be added to the cluster. This will cause the host to join the
+master in a single XenServer pool.
+
+.. parsed-literal::
+
+ # xe pool-join master-address=[master IP] master-username=root
+ master-password=[your password]
+
+
+Complete the Bonding Setup Across the Cluster
+'''''''''''''''''''''''''''''''''''''''''''''
+
+With all hosts added to the pool, run the cloud-setup-bond script. This
+script will complete the configuration and set up of the bonds across
+all hosts in the cluster.
+
+#. Copy the script from the Management Server in
+ /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh
+ to the master host and ensure it is executable.
+
+#. Run the script:
+
+ .. parsed-literal::
+
+ # ./cloud-setup-bonding.sh
+
+Now the bonds are set up and configured properly across the cluster.
+
+
+.. _upgrading-xenserver-version:
+
+Upgrading XenServer Versions
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+This section tells how to upgrade XenServer software on CloudStack
+hosts. The actual upgrade is described in XenServer documentation, but
+there are some additional steps you must perform before and after the
+upgrade.
+
+.. note::
+ Be sure the hardware is certified compatible with the new version of
+ XenServer.
+
+To upgrade XenServer:
+
+#. Upgrade the database. On the Management Server node:
+
+ #. Back up the database:
+
+ .. parsed-literal::
+
+ # mysqldump --user=root --databases cloud > cloud.backup.sql
+ # mysqldump --user=root --databases cloud_usage > cloud_usage.backup.sql
+
+ #. You might need to change the OS type settings for VMs running on
+ the upgraded hosts.
+
+ - If you upgraded from XenServer 5.6 GA to XenServer 5.6 SP2,
+ change any VMs that have the OS type CentOS 5.5 (32-bit),
+ Oracle Enterprise Linux 5.5 (32-bit), or Red Hat Enterprise
+ Linux 5.5 (32-bit) to Other Linux (32-bit). Change any VMs that
+ have the 64-bit versions of these same OS types to Other Linux
+ (64-bit).
+
+ - If you upgraded from XenServer 5.6 SP2 to XenServer 6.0.2,
+ change any VMs that have the OS type CentOS 5.6 (32-bit),
+ CentOS 5.7 (32-bit), Oracle Enterprise Linux 5.6 (32-bit),
+ Oracle Enterprise Linux 5.7 (32-bit), Red Hat Enterprise Linux
+ 5.6 (32-bit) , or Red Hat Enterprise Linux 5.7 (32-bit) to
+ Other Linux (32-bit). Change any VMs that have the 64-bit
+ versions of these same OS types to Other Linux (64-bit).
+
+ - If you upgraded from XenServer 5.6 to XenServer 6.0.2, do all
+ of the above.
+
+ #. Restart the Management Server and Usage Server. You only need to
+ do this once for all clusters.
+
+ .. parsed-literal::
+
+ # service cloudstack-management start
+ # service cloudstack-usage start
+
+#. Disconnect the XenServer cluster from CloudStack.
+
+ #. Log in to the CloudStack UI as root.
+
+ #. Navigate to the XenServer cluster, and click Actions – Unmanage.
+
+ #. Watch the cluster status until it shows Unmanaged.
+
+#. Log in to one of the hosts in the cluster, and run this command to
+ clean up the VLAN:
+
+ .. parsed-literal::
+
+ # . /opt/xensource/bin/cloud-clean-vlan.sh
+
+#. Still logged in to the host, run the upgrade preparation script:
+
+ .. parsed-literal::
+
+ # /opt/xensource/bin/cloud-prepare-upgrade.sh
+
+ Troubleshooting: If you see the error "can't eject CD," log in to the
+ VM and umount the CD, then run the script again.
+
+#. Upgrade the XenServer software on all hosts in the cluster. Upgrade
+ the master first.
+
+ #. Live migrate all VMs on this host to other hosts. See the
+ instructions for live migration in the Administrator's Guide.
+
+ Troubleshooting: You might see the following error when you
+ migrate a VM:
+
+ .. parsed-literal::
+
+ [root@xenserver-qa-2-49-4 ~]# xe vm-migrate live=true host=xenserver-qa-2-49-5 vm=i-2-8-VM
+ You attempted an operation on a VM which requires PV drivers to be installed but the drivers were not detected.
+ vm: b6cf79c8-02ee-050b-922f-49583d9f1a14 (i-2-8-VM)
+
+ To solve this issue, run the following:
+
+ .. parsed-literal::
+
+ # /opt/xensource/bin/make_migratable.sh b6cf79c8-02ee-050b-922f-49583d9f1a14
+
+ #. Reboot the host.
+
+ #. Upgrade to the newer version of XenServer. Use the steps in
+ XenServer documentation.
+
+ #. After the upgrade is complete, copy the following files from the
+ management server to this host, in the directory locations shown
+ below:
+
+ .. cssclass:: table-striped table-bordered table-hover
+
+ ================================================================================= =======================================
+ Copy this Management Server file To this location on the XenServer host
+ ================================================================================= =======================================
+ /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/xenserver60/NFSSR.py /opt/xensource/sm/NFSSR.py
+ /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/setupxenserver.sh /opt/xensource/bin/setupxenserver.sh
+ /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/make\_migratable.sh /opt/xensource/bin/make\_migratable.sh
+ /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-clean-vlan.sh /opt/xensource/bin/cloud-clean-vlan.sh
+ ================================================================================= =======================================
+
+ #. Run the following script:
+
+ .. parsed-literal::
+
+ # /opt/xensource/bin/setupxenserver.sh
+
+ Troubleshooting: If you see the following error message, you can
+ safely ignore it.
+
+ .. parsed-literal::
+
+ mv: cannot stat `/etc/cron.daily/logrotate`: No such file or directory
+
+ #. Plug in the storage repositories (physical block devices) to the
+ XenServer host:
+
+ .. parsed-literal::
+
+ # for pbd in `xe pbd-list currently-attached=false| grep ^uuid | awk '{print $NF}'`; do xe pbd-plug uuid=$pbd ; done
+
+ .. note::
+ If you add a host to this XenServer pool, you need to migrate all VMs
+ on this host to other hosts, and eject this host from XenServer pool.
+
+#. Repeat these steps to upgrade every host in the cluster to the same
+ version of XenServer.
+
+#. Run the following command on one host in the XenServer cluster to
+ clean up the host tags:
+
+ .. parsed-literal::
+
+ # for host in $(xe host-list | grep ^uuid | awk '{print $NF}') ; do xe host-param-clear uuid=$host param-name=tags; done;
+
+ .. note::
+ When copying and pasting a command, be sure the command has pasted as
+ a single line before executing. Some document viewers may introduce
+ unwanted line breaks in copied text.
+
+#. Reconnect the XenServer cluster to CloudStack.
+
+ #. Log in to the CloudStack UI as root.
+
+ #. Navigate to the XenServer cluster, and click Actions – Manage.
+
+ #. Watch the status to see that all the hosts come up.
+
+#. After all hosts are up, run the following on one host in the cluster:
+
+ .. parsed-literal::
+
+ # /opt/xensource/bin/cloud-clean-vlan.sh
diff --git a/source/installguide/index.rst b/source/installguide/index.rst
new file mode 100644
index 0000000..01d9012
--- /dev/null
+++ b/source/installguide/index.rst
@@ -0,0 +1,79 @@
+.. 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 Installation Documentation master file, created by
+ sphinx-quickstart on Sat Jan 25 15:15:31 2014.
+ You can adapt this file completely to your liking, but it should at least
+ contain the root `toctree` directive.
+
+|menu_acs_logo|
+
+
+Installation Guide
+==================
+
+This is the Apache CloudStack installation guide
+
+.. toctree::
+
+Building from Source
+--------------------
+.. toctree::
+ :maxdepth: 2
+
+ building_from_source
+
+
+.. _installation:
+
+General Installation
+--------------------
+.. toctree::
+ :maxdepth: 2
+
+ overview/index
+ management-server/index
+
+
+.. _configuration:
+
+Configuration
+-------------
+.. toctree::
+ :maxdepth: 2
+
+ configuration
+
+
+.. _hypervisors:
+
+Hypervisor Setup
+----------------
+.. toctree::
+ :maxdepth: 2
+ :glob:
+
+ hypervisor/*
+
+.. optional:
+
+
+Optional Installation
+---------------------
+.. toctree::
+ :maxdepth: 2
+
+ optional_installation
+ encryption
diff --git a/source/installguide/locale/pot/building_from_source.pot b/source/installguide/locale/pot/building_from_source.pot
new file mode 100644
index 0000000..1433375
--- /dev/null
+++ b/source/installguide/locale/pot/building_from_source.pot
@@ -0,0 +1,433 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../building_from_source.rst:18
+# ef11ea68beec49c5871db512f598d676
+msgid "Building from Source"
+msgstr ""
+
+#: ../../building_from_source.rst:20
+# 2a043bdd667b4d9293f70ad36316281e
+msgid "The official CloudStack release is always in source code form. You will likely be able to find \"convenience binaries,\" the source is the canonical release. In this section, we'll cover acquiring the source release and building that so that you can deploy it using Maven or create Debian packages or RPMs."
+msgstr ""
+
+#: ../../building_from_source.rst:26
+# 34b9935b1b234772875a5632f77cc973
+msgid "Note that building and deploying directly from source is typically not the most efficient way to deploy an IaaS. However, we will cover that method as well as building RPMs or Debian packages for deploying CloudStack."
+msgstr ""
+
+#: ../../building_from_source.rst:31
+# dc09a8fd969d4628811a6127bb066d15
+msgid "The instructions here are likely version-specific. That is, the method for building from source for the 4.0.x series is different from the 4.1.x series."
+msgstr ""
+
+#: ../../building_from_source.rst:35
+# 1122421db6114fc9919baefb86af655a
+msgid "If you are working with a unreleased version of CloudStack, see the INSTALL.md file in the top-level directory of the release."
+msgstr ""
+
+#: ../../building_from_source.rst:40
+# 70eb2ab692764b6dbb6ea174f0062a59
+msgid "Getting the release"
+msgstr ""
+
+#: ../../building_from_source.rst:42
+# 16e7f13a2bf342fd9eff4ec10614bfb7
+msgid "You can download the latest CloudStack release from the `Apache CloudStack project download page <http://cloudstack.apache.org/downloads.html>`_."
+msgstr ""
+
+#: ../../building_from_source.rst:46
+# 66ddf14b21c1450b84222ff24a97c8a1
+msgid "Prior releases are available via archive.apache.org as well. See the downloads page for more information on archived releases."
+msgstr ""
+
+#: ../../building_from_source.rst:49
+# ffcd1760171b4c22aadfbdf0a143c2f3
+msgid "You'll notice several links under the 'Latest release' section. A link to a file ending in ``tar.bz2``, as well as a PGP/GPG signature, MD5, and SHA512 file."
+msgstr ""
+
+#: ../../building_from_source.rst:53
+# 25bd15343d884479bb06e47381b678fd
+msgid "The ``tar.bz2`` file contains the Bzip2-compressed tarball with the source code."
+msgstr ""
+
+#: ../../building_from_source.rst:56
+# 3d236d0dfc154c268fed0612bdd129ce
+msgid "The ``.asc`` file is a detached cryptographic signature that can be used to help verify the authenticity of the release."
+msgstr ""
+
+#: ../../building_from_source.rst:59
+# 6d4f2dc258d643b8b8733a59476db314
+msgid "The ``.md5`` file is an MD5 hash of the release to aid in verify the validity of the release download."
+msgstr ""
+
+#: ../../building_from_source.rst:62
+# 3a3f100d4fce444482fc82808ddc6b88
+msgid "The ``.sha`` file is a SHA512 hash of the release to aid in verify the validity of the release download."
+msgstr ""
+
+#: ../../building_from_source.rst:67
+# 5b9f966ab0404b0895cad4a389bc200c
+msgid "Verifying the downloaded release"
+msgstr ""
+
+#: ../../building_from_source.rst:69
+# db3e51bdf33d4742a685c0d6162f05a4
+msgid "There are a number of mechanisms to check the authenticity and validity of a downloaded release."
+msgstr ""
+
+#: ../../building_from_source.rst:74
+# a41259b8a7754a1d968844b286750d17
+msgid "Getting the KEYS"
+msgstr ""
+
+#: ../../building_from_source.rst:76
+# 070bfe72ade6433292ddf947a78ff960
+msgid "To enable you to verify the GPG signature, you will need to download the `KEYS <http://www.apache.org/dist/cloudstack/KEYS>`_ file."
+msgstr ""
+
+#: ../../building_from_source.rst:79
+# 639635ff8564492fb4965f5da6a4215f
+msgid "You next need to import those keys, which you can do by running:"
+msgstr ""
+
+#: ../../building_from_source.rst:87
+# 7cad52cd29334223a2eb5a524fa31229
+msgid "GPG"
+msgstr ""
+
+#: ../../building_from_source.rst:89
+# 108a752dff73440c9de3ffbca5f64843
+msgid "The CloudStack project provides a detached GPG signature of the release. To check the signature, run the following command:"
+msgstr ""
+
+#: ../../building_from_source.rst:96
+# 7b1992ef9c664f60bed1e3da72b53326
+msgid "If the signature is valid you will see a line of output that contains 'Good signature'."
+msgstr ""
+
+#: ../../building_from_source.rst:101
+# 2f3891019c1c4d879aea2ce4a283292a
+msgid "MD5"
+msgstr ""
+
+#: ../../building_from_source.rst:103
+# ddbbe1736210472d8f2c8d157a51884d
+msgid "In addition to the cryptographic signature, CloudStack has an MD5 checksum that you can use to verify the download matches the release. You can verify this hash by executing the following command:"
+msgstr ""
+
+#: ../../building_from_source.rst:111
+# 9490a741b6b049feb039b5dd8c7bace1
+msgid "If this successfully completes you should see no output. If there is any output from them, then there is a difference between the hash you generated locally and the hash that has been pulled from the server."
+msgstr ""
+
+#: ../../building_from_source.rst:117
+# a34badbd49654f2e9c9040981cdfa1be
+msgid "SHA512"
+msgstr ""
+
+#: ../../building_from_source.rst:119
+# 8137cfe2c2df43c587b7bfed84c0612e
+msgid "In addition to the MD5 hash, the CloudStack project provides a SHA512 cryptographic hash to aid in assurance of the validity of the downloaded release. You can verify this hash by executing the following command:"
+msgstr ""
+
+#: ../../building_from_source.rst:127
+# 45114708d09246febbeee238d2b1e303
+msgid "If this command successfully completes you should see no output. If there is any output from them, then there is a difference between the hash you generated locally and the hash that has been pulled from the server."
+msgstr ""
+
+#: ../../building_from_source.rst:134
+# 48a54f38aeb04d938f6ce37e3ed8b1d3
+msgid "Prerequisites for building Apache CloudStack"
+msgstr ""
+
+#: ../../building_from_source.rst:136
+# 4d1bceb893204853a12377f796db8762
+msgid "There are a number of prerequisites needed to build CloudStack. This document assumes compilation on a Linux system that uses RPMs or DEBs for package management."
+msgstr ""
+
+#: ../../building_from_source.rst:140
+# d618af2b2ace42e1a270c753a9be20e6
+msgid "You will need, at a minimum, the following to compile CloudStack:"
+msgstr ""
+
+#: ../../building_from_source.rst:142
+# 06302615cd204c05bb9ee7c9a463a336
+msgid "Maven (version 3)"
+msgstr ""
+
+#: ../../building_from_source.rst:144
+# 12e01c26b3b343d39e522dbde2704e6f
+msgid "Java (OpenJDK 1.6 or Java 7/OpenJDK 1.7)"
+msgstr ""
+
+#: ../../building_from_source.rst:146
+# fad73fd5cd0d43dba668f37c6d2baaa5
+msgid "Apache Web Services Common Utilities (ws-commons-util)"
+msgstr ""
+
+#: ../../building_from_source.rst:148
+# 3cd08240ad30472e8a18797edea67732
+msgid "MySQL"
+msgstr ""
+
+#: ../../building_from_source.rst:150
+# 34fdc352ce70420ebf3d4c32e0ef790e
+msgid "MySQLdb (provides Python database API)"
+msgstr ""
+
+#: ../../building_from_source.rst:152
+# b94e3afe30b04baa84d114d1cc67e56b
+msgid "Tomcat 6 (not 6.0.35)"
+msgstr ""
+
+#: ../../building_from_source.rst:154
+# 6269e20f8b1248af837e3d75b2d56cf7
+msgid "genisoimage"
+msgstr ""
+
+#: ../../building_from_source.rst:156
+# d43cbcb988fd42e08c351dfdaaa519aa
+msgid "rpmbuild or dpkg-dev"
+msgstr ""
+
+#: ../../building_from_source.rst:160
+# 27d74522549f4b85ac4bcd78e737b72c
+msgid "Extracting source"
+msgstr ""
+
+#: ../../building_from_source.rst:162
+# 25f6064ab9e64561948107df87e2d317
+msgid "Extracting the CloudStack release is relatively simple and can be done with a single command as follows:"
+msgstr ""
+
+#: ../../building_from_source.rst:169
+# 78aa3b8b39704c1f8561b069d0cfcb4d
+msgid "You can now move into the directory:"
+msgstr ""
+
+#: ../../building_from_source.rst:177
+# c46dc00000204d2cb73ae63e116bc55a
+msgid "Building DEB packages"
+msgstr ""
+
+#: ../../building_from_source.rst:179
+# 4b6cce4d00f748ada32203791b19b088
+msgid "In addition to the bootstrap dependencies, you'll also need to install several other dependencies. Note that we recommend using Maven 3, which is not currently available in 12.04.1 LTS. So, you'll also need to add a PPA repository that includes Maven 3. After running the command ``add-apt-repository``, you will be prompted to continue and a GPG key will be added."
+msgstr ""
+
+#: ../../building_from_source.rst:194
+# 283980d16b48466bb2a2d3b17ff1fede
+msgid "While we have defined, and you have presumably already installed the bootstrap prerequisites, there are a number of build time prerequisites that need to be resolved. CloudStack uses maven for dependency resolution. You can resolve the buildtime depdencies for CloudStack by running:"
+msgstr ""
+
+#: ../../building_from_source.rst:204
+# 7e08137b290649cda9b8e9b728ff33aa
+msgid "Now that we have resolved the dependencies we can move on to building CloudStack and packaging them into DEBs by issuing the following command."
+msgstr ""
+
+#: ../../building_from_source.rst:212
+# ec3f8fd379b7417294d5b01ce47f367f
+msgid "This command will build the following debian packages. You should have all of the following:"
+msgstr ""
+
+#: ../../building_from_source.rst:227
+# 8521111f14944fbc8f62bfb2f4cb8a0b
+msgid "Setting up an APT repo"
+msgstr ""
+
+#: ../../building_from_source.rst:229
+# f937d1aff1e74e8d8869d99a5dcf0315
+msgid "After you've created the packages, you'll want to copy them to a system where you can serve the packages over HTTP. You'll create a directory for the packages and then use ``dpkg-scanpackages`` to create ``Packages.gz``, which holds information about the archive structure. Finally, you'll add the repository to your system(s) so you can install the packages using APT."
+msgstr ""
+
+#: ../../building_from_source.rst:236
+# 77189e27fd6648db96421e68ea2197c7
+msgid "The first step is to make sure that you have the **dpkg-dev** package installed. This should have been installed when you pulled in the **debhelper** application previously, but if you're generating ``Packages.gz`` on a different system, be sure that it's installed there as well."
+msgstr ""
+
+#: ../../building_from_source.rst:246
+# ca7c2a636f664075b7104554ed4ea25d
+msgid "The next step is to copy the DEBs to the directory where they can be served over HTTP. We'll use ``/var/www/cloudstack/repo`` in the examples, but change the directory to whatever works for you."
+msgstr ""
+
+#: ../../building_from_source.rst:258
+# 5aed13bc18cc47d0a3d386be28663478
+msgid "You can safely ignore the warning about a missing override file."
+msgstr ""
+
+#: ../../building_from_source.rst:260
+# 2ab43ed9a4ad40339e0b43646ae7e6a7
+msgid "Now you should have all of the DEB packages and ``Packages.gz`` in the ``binary`` directory and available over HTTP. (You may want to use ``wget`` or ``curl`` to test this before moving on to the next step.)"
+msgstr ""
+
+#: ../../building_from_source.rst:266
+# 410e592ce4134e54a0c21c37dc761c1d
+msgid "Configuring your machines to use the APT repository"
+msgstr ""
+
+#: ../../building_from_source.rst:268
+# ec3e958425e048aa8e4fb1916ef372de
+msgid "Now that we have created the repository, you need to configure your machine to make use of the APT repository. You can do this by adding a repository file under ``/etc/apt/sources.list.d``. Use your preferred editor to create ``/etc/apt/sources.list.d/cloudstack.list`` with this line:"
+msgstr ""
+
+#: ../../building_from_source.rst:278
+# affbe297a4444a9e9d87f2bb39672d9f
+msgid "Now that you have the repository info in place, you'll want to run another update so that APT knows where to find the CloudStack packages."
+msgstr ""
+
+#: ../../building_from_source.rst:285
+# 2806875948bd4534b353edcf499fd5af
+msgid "You can now move on to the instructions under Install on Ubuntu."
+msgstr ""
+
+#: ../../building_from_source.rst:289
+# f14be60974c1461e99bd00a8090db43a
+msgid "Building RPMs from Source"
+msgstr ""
+
+#: ../../building_from_source.rst:291
+# 8f87d648db12475a82e931fdba69af9d
+msgid "As mentioned previously in `“Prerequisites for building Apache CloudStack” <#prerequisites-for-building-apache-cloudstack>`_, you will need to install several prerequisites before you can build packages for CloudStack. Here we'll assume you're working with a 64-bit build of CentOS or Red Hat Enterprise Linux."
+msgstr ""
+
+#: ../../building_from_source.rst:305
+# c37ae1838eb34ab694493fa102119691
+msgid "Next, you'll need to install build-time dependencies for CloudStack with Maven. We're using Maven 3, so you'll want to `grab a Maven 3 tarball <http://maven.apache.org/download.cgi>`_ and uncompress it in your home directory (or whatever location you prefer):"
+msgstr ""
+
+#: ../../building_from_source.rst:318
+# afb9d4d455cc4a689b58d254dcd9896d
+msgid "Maven also needs to know where Java is, and expects the JAVA\\_HOME environment variable to be set:"
+msgstr ""
+
+#: ../../building_from_source.rst:325
+# a8eaac2e266d48dabaf04dff48781e01
+msgid "Verify that Maven is installed correctly:"
+msgstr ""
+
+#: ../../building_from_source.rst:331
+# 76c3a8ce403d460bbd79e42edb06fb62
+msgid "You probably want to ensure that your environment variables will survive a logout/reboot. Be sure to update ``~/.bashrc`` with the PATH and JAVA\\_HOME variables."
+msgstr ""
+
+#: ../../building_from_source.rst:335
+# 7e91515caf2d407b8196d2bb067f12f6
+msgid "Building RPMs for CloudStack is fairly simple. Assuming you already have the source downloaded and have uncompressed the tarball into a local directory, you're going to be able to generate packages in just a few minutes."
+msgstr ""
+
+#: ../../building_from_source.rst:341
+# bf6a8f0ff1ab4b5ab8af48ee83cedda3
+msgid "Packaging has Changed. If you've created packages for CloudStack previously, you should be aware that the process has changed considerably since the project has moved to using Apache Maven. Please be sure to follow the steps in this section closely."
+msgstr ""
+
+#: ../../building_from_source.rst:348
+# a058ef55f9d544c59a3d9167d13e55f7
+msgid "Generating RPMS"
+msgstr ""
+
+#: ../../building_from_source.rst:350
+# b30e84d7601d4d81a71bcd33b034f374
+msgid "Now that we have the prerequisites and source, you will cd to the `packaging/centos63/` directory."
+msgstr ""
+
+#: ../../building_from_source.rst:357
+# 9f33b2b9cbfd4211ab425cf8bb35a9d9
+msgid "Generating RPMs is done using the ``package.sh`` script:"
+msgstr ""
+
+#: ../../building_from_source.rst:363
+# b91a6668f8414cfaac447e79705af239
+msgid "That will run for a bit and then place the finished packages in ``dist/rpmbuild/RPMS/x86_64/``."
+msgstr ""
+
+#: ../../building_from_source.rst:366
+# 027abcc96e1144cfbd6511ca4c31b35d
+msgid "You should see the following RPMs in that directory:"
+msgstr ""
+
+#: ../../building_from_source.rst:380
+# fe5a036719b948639b86eb45194cbb45
+msgid "Creating a yum repo"
+msgstr ""
+
+#: ../../building_from_source.rst:382
+# fa6516e0378d40b8b6571d4f92e5cf60
+msgid "While RPMs is a useful packaging format - it's most easily consumed from Yum repositories over a network. The next step is to create a Yum Repo with the finished packages:"
+msgstr ""
+
+#: ../../building_from_source.rst:398
+# 7db0ebdd90574721be216ccf32b72064
+msgid "The files and directories within ``~/tmp/repo`` can now be uploaded to a web server and serve as a yum repository."
+msgstr ""
+
+#: ../../building_from_source.rst:403
+# 34af5e2901ba47ad90a764c39024011a
+msgid "Configuring your systems to use your new yum repository"
+msgstr ""
+
+#: ../../building_from_source.rst:405
+# 3e7e415e4d0f430b8eeb67194f885455
+msgid "Now that your yum repository is populated with RPMs and metadata we need to configure the machines that need to install CloudStack. Create a file named ``/etc/yum.repos.d/cloudstack.repo`` with this information:"
+msgstr ""
+
+#: ../../building_from_source.rst:417
+# 16a2be281d5d4d11bdb334ea963026db
+msgid "Completing this step will allow you to easily install CloudStack on a number of machines across the network."
+msgstr ""
+
+#: ../../building_from_source.rst:422
+# 592481f4523641afa7fb8b6ef7a582c3
+msgid "Building Non-OSS"
+msgstr ""
+
+#: ../../building_from_source.rst:424
+# 056563e7eea94421b05d5fcd09befd25
+msgid "If you need support for the VMware, NetApp, F5, NetScaler, SRX, or any other non-Open Source Software (nonoss) plugins, you'll need to download a few components on your own and follow a slightly different procedure to build from source."
+msgstr ""
+
+#: ../../building_from_source.rst:430
+# f6587f3c5b644126b1ed2229b15c648b
+msgid "Some of the plugins supported by CloudStack cannot be distributed with CloudStack for licensing reasons. In some cases, some of the required libraries/JARs are under a proprietary license. In other cases, the required libraries may be under a license that's not compatible with `Apache's licensing guidelines for third-party products <http://www.apache.org/legal/resolved.html#category-x>`_."
+msgstr ""
+
+#: ../../building_from_source.rst:437
+# bc2bb0c113ac453e9f9b4468b91f1139
+msgid "To build the Non-OSS plugins, you'll need to have the requisite JARs installed under the ``deps`` directory."
+msgstr ""
+
+#: ../../building_from_source.rst:440
+# a59479563c7742e49beb8e5ecb8efba1
+msgid "Because these modules require dependencies that can't be distributed with CloudStack you'll need to download them yourself. Links to the most recent dependencies are listed on the `*How to build CloudStack* <https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack>`_ page on the wiki."
+msgstr ""
+
+#: ../../building_from_source.rst:446
+# d9d9d34be2604c18a3b9107dbf384181
+msgid "You may also need to download `vhd-util <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_, which was removed due to licensing issues. You'll copy vhd-util to the ``scripts/vm/hypervisor/xenserver/`` directory."
+msgstr ""
+
+#: ../../building_from_source.rst:451
+# bfbd7215ff0345f183a7946f620b1368
+msgid "Once you have all the dependencies copied over, you'll be able to build CloudStack with the ``noredist`` option:"
+msgstr ""
+
+#: ../../building_from_source.rst:459
+# 252d45f71b814e409bdd693e44584f8e
+msgid "Once you've built CloudStack with the ``noredist`` profile, you can package it using the `“Building RPMs from Source” <#building-rpms-from-source>`_ or `“Building DEB packages” <#building-deb-packages>`_ instructions."
+msgstr ""
+
diff --git a/source/installguide/locale/pot/choosing_deployment_architecture.pot b/source/installguide/locale/pot/choosing_deployment_architecture.pot
new file mode 100644
index 0000000..7226ee2
--- /dev/null
+++ b/source/installguide/locale/pot/choosing_deployment_architecture.pot
@@ -0,0 +1,511 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../choosing_deployment_architecture.rst:18
+# 2c4ff27205844a38ba74b1ffed7d0d4c
+msgid "Choosing a Deployment Architecture"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:20
+# b26daf37d81247238775fca77b416ae2
+msgid "The architecture used in a deployment will vary depending on the size and purpose of the deployment. This section contains examples of deployment architecture, including a small-scale deployment useful for test and trial deployments and a fully-redundant large-scale setup for production deployments."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:28
+# 2f09e208c05a4a5aa8f3c9f87ed50c25
+msgid "Small-Scale Deployment"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:30
+# 068dcc56cbd24a0083450026b9402fd6
+msgid "|Small-Scale Deployment|"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:32
+# 97e93e20540547229fc5d499cd5d3fc5
+msgid "This diagram illustrates the network architecture of a small-scale CloudStack deployment."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:35
+# d0e9d1cd6d02485fbb7569bbcac7691f
+msgid "A firewall provides a connection to the Internet. The firewall is configured in NAT mode. The firewall forwards HTTP requests and API calls from the Internet to the Management Server. The Management Server resides on the management network."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:40
+# 3a9520fd64a74db8b3fc06b9204f08a2
+msgid "A layer-2 switch connects all physical servers and storage."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:42
+# cd028d62b82f44ffbe0173ee7583fdee
+msgid "A single NFS server functions as both the primary and secondary storage."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:45
+# de231b4108f546bc9a6ce6fc4468768c
+msgid "The Management Server is connected to the management network."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:49
+# 361b0a48cf54455a94238a38750ee7b9
+msgid "Large-Scale Redundant Setup"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:51
+# 38cdbfb68cca4fd8bc4df9bc1ecd694a
+msgid "|Large-Scale Redundant Setup|"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:53
+# 0933dd6019474cfc97b03f67506bc999
+msgid "This diagram illustrates the network architecture of a large-scale CloudStack deployment."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:56
+# e3f81067d12242558eaf4684bb364861
+msgid "A layer-3 switching layer is at the core of the data center. A router redundancy protocol like VRRP should be deployed. Typically high-end core switches also include firewall modules. Separate firewall appliances may also be used if the layer-3 switch does not have integrated firewall capabilities. The firewalls are configured in NAT mode. The firewalls provide the following functions:"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:63
+# a68bb7cb39bd42afa4d9e29f84fa3457
+msgid "Forwards HTTP requests and API calls from the Internet to the Management Server. The Management Server resides on the management network."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:67
+# 69f7f256ee7341c98affe498692cd667
+msgid "When the cloud spans multiple zones, the firewalls should enable site-to-site VPN such that servers in different zones can directly reach each other."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:71
+# b779613fe6004e40bb248aaeb76d8bc3
+msgid "A layer-2 access switch layer is established for each pod. Multiple switches can be stacked to increase port count. In either case, redundant pairs of layer-2 switches should be deployed."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:75
+# 2032fc16630e41529475a4622c4fb9a2
+msgid "The Management Server cluster (including front-end load balancers, Management Server nodes, and the MySQL database) is connected to the management network through a pair of load balancers."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:79
+# cbcfb563ab554774b485b977d456e814
+msgid "Secondary storage servers are connected to the management network."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:81
+# ed99b388e7464d338ce1e290c13e3e7b
+msgid "Each pod contains storage and computing servers. Each storage and computing server should have redundant NICs connected to separate layer-2 access switches."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:87
+# 741500f6260941e79f28d53a5986fc43
+msgid "Separate Storage Network"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:89
+# 1ef36fbcddb24180bf412b41f03bcbc4
+msgid "In the large-scale redundant setup described in the previous section, storage traffic can overload the management network. A separate storage network is optional for deployments. Storage protocols such as iSCSI are sensitive to network delays. A separate storage network ensures guest network traffic contention does not impact storage performance."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:97
+# b813bc439dea4888b8dddbc9122afe9a
+msgid "Multi-Node Management Server"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:99
+# 35591778160a4e25a505e5dcd507198f
+msgid "The CloudStack Management Server is deployed on one or more front-end servers connected to a single MySQL database. Optionally a pair of hardware load balancers distributes requests from the web. A backup management server set may be deployed using MySQL replication at a remote site to add DR capabilities."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:105
+# faff12b3c7c142f59b2a12926ab7c9f7
+msgid "|Multi-Node Management Server|"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:107
+# ee629ff1681e4b38bfddfac64b76c7d6
+msgid "The administrator must decide the following."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:109
+# 3e9822c46e86433cb6d9f4ecbbacda1e
+msgid "Whether or not load balancers will be used."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:111
+# ab341a95aac3496581377672055b241d
+msgid "How many Management Servers will be deployed."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:113
+# 2dbc1c3c22db42958e785984f5ef93e4
+msgid "Whether MySQL replication will be deployed to enable disaster recovery."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:118
+# 4858e0bbf6f14d6b990948aacc6e0b74
+msgid "Multi-Site Deployment"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:120
+# 31bb0ebb88974050a79e6f0aec7c6778
+msgid "The CloudStack platform scales well into multiple sites through the use of zones. The following diagram shows an example of a multi-site deployment."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:124
+# 72c760ffa57b48a0a2ce31a545672acb
+msgid "|Example Of A Multi-Site Deployment|"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:126
+# 3680185677f54baeb03396c0c6e6b91b
+msgid "Data Center 1 houses the primary Management Server as well as zone 1. The MySQL database is replicated in real time to the secondary Management Server installation in Data Center 2."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:130
+# 44f2f283a3dd4992ba843cd1a6ad29b9
+msgid "|Separate Storage Network|"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:132
+# 85a51dc8edc24f37b0483d2b5d46a1dd
+msgid "This diagram illustrates a setup with a separate storage network. Each server has four NICs, two connected to pod-level network switches and two connected to storage network switches."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:136
+# 56c244202346479080d0963357ce6a01
+msgid "There are two ways to configure the storage network:"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:138
+# 774def02c93d4401aa0961c701e2a346
+msgid "Bonded NIC and redundant switches can be deployed for NFS. In NFS deployments, redundant switches and bonded NICs still result in one network (one CIDR block+ default gateway address)."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:142
+# 42c329aa74164a2a91b1cb061a594df0
+msgid "iSCSI can take advantage of two separate storage networks (two CIDR blocks each with its own default gateway). Multipath iSCSI client can failover and load balance between separate storage networks."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:146
+# 709e7b87aca14df39855bc39efbde210
+msgid "|NIC Bonding And Multipath I/O|"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:148
+# b9cd0b7d1c614f24855cf4e9755e9070
+msgid "This diagram illustrates the differences between NIC bonding and Multipath I/O (MPIO). NIC bonding configuration involves only one network. MPIO involves two separate networks."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:154
+# 36df70c98ae746549452fa36e1ca87e3
+msgid "Choosing a Hypervisor"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:156
+# f236302a8db24c13a141a20573581062
+msgid "CloudStack supports many popular hypervisors. Your cloud can consist entirely of hosts running a single hypervisor, or you can use multiple hypervisors. Each cluster of hosts must run the same hypervisor."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:160
+# ebd33f6eb3b64168ac6543a23dac1afd
+msgid "You might already have an installed base of nodes running a particular hypervisor, in which case, your choice of hypervisor has already been made. If you are starting from scratch, you need to decide what hypervisor software best suits your needs. A discussion of the relative advantages of each hypervisor is outside the scope of our documentation. However, it will help you to know which features of each hypervisor are supported by CloudStack. The following table provides this information."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:169
+# 6095a38fe5eb4ce7acbb1c158db98231
+msgid "Feature"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:169
+# 4a7ee7865ca548379bf859592ddb19f8
+msgid "XenServer 6.0.2"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:169
+# 09198080ae1c486ebd9470b6c99b387f
+msgid "vSphere 4.1/5.0"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:169
+# 1870d6331a364df4a087d4f6f3368ab9
+msgid "KVM - RHEL 6.2"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:169
+# d3c9ece508424f81897e3280902508b0
+msgid "Bare Metal"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:171
+# 970a9d80bc134222b3218d026302891b
+msgid "Network Throttling"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:171
+#: ../../choosing_deployment_architecture.rst:171
+#: ../../choosing_deployment_architecture.rst:172
+#: ../../choosing_deployment_architecture.rst:172
+#: ../../choosing_deployment_architecture.rst:173
+#: ../../choosing_deployment_architecture.rst:173
+#: ../../choosing_deployment_architecture.rst:173
+#: ../../choosing_deployment_architecture.rst:174
+#: ../../choosing_deployment_architecture.rst:174
+#: ../../choosing_deployment_architecture.rst:174
+#: ../../choosing_deployment_architecture.rst:175
+#: ../../choosing_deployment_architecture.rst:175
+#: ../../choosing_deployment_architecture.rst:175
+#: ../../choosing_deployment_architecture.rst:175
+#: ../../choosing_deployment_architecture.rst:176
+#: ../../choosing_deployment_architecture.rst:176
+#: ../../choosing_deployment_architecture.rst:177
+#: ../../choosing_deployment_architecture.rst:177
+#: ../../choosing_deployment_architecture.rst:177
+#: ../../choosing_deployment_architecture.rst:180
+#: ../../choosing_deployment_architecture.rst:180
+#: ../../choosing_deployment_architecture.rst:180
+#: ../../choosing_deployment_architecture.rst:181
+#: ../../choosing_deployment_architecture.rst:181
+# 4fec162cda76433cb982cfc313dcdbe6
+# 1f8cc79d716140189e60a08ebf4687bf
+# 91a8ee2ecce64c71b1eecf843f67deed
+# 2989a051bcd34ea987938c8a7e30b013
+# 9cbaf270ddd6408c8101622f74c7b266
+# 12e9d689493a44049c4874afa2dbadd3
+# f9a1370f394c49a8967531ffb6e1b423
+# 91b5581980864170b9693104a2f61d3c
+# c231f1df091e4ceeb60e89845db5f10b
+# 2852be6028ec46659ae8bf5cac551b29
+# 755b64ababd34e04b82a384d357fc6e4
+# 3e558e80e7bc4878b80739772dfb4a06
+# 227928dd0cf1488b873ce21a5b4842d2
+# 6ca963616f6a42098fed6641c7711e35
+# f36be7f0603b44f5aa77a248d3a97e5e
+# 996c7caeb3384d93be1ce49f570cb8ce
+# 5d9e3cabc113463e8b6c3fb75b182456
+# 159c98b022e14645bef4499b7c0c0235
+# f55810d73d0246b38a1495e4af5ec4bc
+# 0867769fdd5046d0832752148daf908d
+# c25243683e1449f0b89ee3d3b1881025
+# 87e8128b3ae84f228c87a33a892a23ec
+# 9fc4d908264143e682ddec06aaafe205
+# 0bb1aaf47c0543659d4e09d9f91cd185
+msgid "Yes"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:171
+#: ../../choosing_deployment_architecture.rst:172
+#: ../../choosing_deployment_architecture.rst:172
+#: ../../choosing_deployment_architecture.rst:178
+#: ../../choosing_deployment_architecture.rst:178
+#: ../../choosing_deployment_architecture.rst:178
+#: ../../choosing_deployment_architecture.rst:179
+#: ../../choosing_deployment_architecture.rst:179
+#: ../../choosing_deployment_architecture.rst:181
+# 3cb5cc62ebb54cae80640aabea621255
+# 86b2047f134d4b8a8af64d25bea97315
+# 5ca5465c16114b58ab0aaaf014969e31
+# fc76b86618fb433780039d59ce9cf302
+# 0cd9cc48eb624d829d99923f98ab2d5f
+# 748e481678464f27b851cb867b2d78b2
+# 1215b1b0f7e44472adcf474168869721
+# db4ae4f299a14dd097a941a94920c9c0
+# c8744cfc965e4794935294c98d6aae14
+msgid "No"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:171
+#: ../../choosing_deployment_architecture.rst:173
+#: ../../choosing_deployment_architecture.rst:174
+#: ../../choosing_deployment_architecture.rst:176
+#: ../../choosing_deployment_architecture.rst:177
+#: ../../choosing_deployment_architecture.rst:178
+#: ../../choosing_deployment_architecture.rst:179
+#: ../../choosing_deployment_architecture.rst:180
+#: ../../choosing_deployment_architecture.rst:181
+# 63afe958cfa44895bc62e896586ee40f
+# 199baf6fe3444dd48443901731e0ad62
+# ece293ab433448bd95772d3de229bcf6
+# fc04754e8df54fd7b280d1e2d9973a9f
+# 258bacf04ab349cc80b6f7d9ec2c0d7b
+# 9d861363c0d54ccb831b9a52f67834f6
+# be8b43bee82341ce8c679239ccd5e71e
+# 89c3130f25d348d1abc3081a0a033720
+# cfcd30df2f204091be6335cf2b116e44
+msgid "N/A"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:172
+# 6f727e19a82c4be4b3d885ee30c3bd5e
+msgid "Security groups in zones that use basic networking"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:173
+# 97e1ffe107c74bd4846cf646d1b9543e
+msgid "iSCSI"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:174
+# 2ea33b37f3de4e91b56a3f97d94654b7
+msgid "FibreChannel"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:175
+# b1c9732e6c15420a87ad6e0dd96052ef
+msgid "Local Disk"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:176
+# 490c55011c344c2cad34b7ed6f88fade
+msgid "HA"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:176
+# 1aa446ba2cf44112bb3b742a8435bc70
+msgid "Yes (Native)"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:177
+# d46bd32966d54085a61343d211a063d1
+msgid "Snapshots of local disk"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:178
+# 954f1dc69e8945f9a3e8d1363d10feb9
+msgid "Local disk as data disk"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:179
+# e31cc2bd3ce340ae9976c8166beb44cb
+msgid "Work load balancing"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:179
+# 9b6952490df5422e8c9dc96b96e06914
+msgid "DRS"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:180
+# 276af5d2a4d94ebdb3319fbbe859a74e
+msgid "Manual live migration of VMs from host to host"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:181
+# a6ffb0bdac29407e86b5edc37f932c8c
+msgid "Conserve management traffic IP address by using link local network to communicate with virtual router"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:186
+# eb354934ad0c4f1e92a9aa56494e083e
+msgid "Best Practices"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:188
+# 42fc8f2d41c548c0b39e0f03816bd496
+msgid "Deploying a cloud is challenging. There are many different technology choices to make, and CloudStack is flexible enough in its configuration that there are many possible ways to combine and configure the chosen technology. This section contains suggestions and requirements about cloud deployments."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:194
+# 68e273347ac34898aaaddc10df7c5d4d
+msgid "These should be treated as suggestions and not absolutes. However, we do encourage anyone planning to build a cloud outside of these guidelines to seek guidance and advice on the project mailing lists."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:200
+# ba21db935b174028b86bb1e6442669d7
+msgid "Process Best Practices"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:202
+# cefb1b21faf04019abc16cccabd19d30
+msgid "A staging system that models the production environment is strongly advised. It is critical if customizations have been applied to CloudStack."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:206
+# ea64ea072f3746d2b3463aafdc14532b
+msgid "Allow adequate time for installation, a beta, and learning the system. Installs with basic networking can be done in hours. Installs with advanced networking usually take several days for the first attempt, with complicated installations taking longer. For a full production system, allow at least 4-8 weeks for a beta to work through all of the integration issues. You can get help from fellow users on the cloudstack-users mailing list."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:216
+# 67f17d3accb24ff48c29830624f9a607
+msgid "Setup Best Practices"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:218
+# 81402254fd3a4dd888d02f4a884a1d0b
+msgid "Each host should be configured to accept connections only from well-known entities such as the CloudStack Management Server or your network monitoring software."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:222
+# 7481cf7faac5484b8339bb8e4d75b6c8
+msgid "Use multiple clusters per pod if you need to achieve a certain switch density."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:225
+# fd7badb077d04065b340d43fd79a4eec
+msgid "Primary storage mountpoints or LUNs should not exceed 6 TB in size. It is better to have multiple smaller primary storage elements per cluster than one large one."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:229
+# 6ed9bc75682247bfbc913cf9df8e21f1
+msgid "When exporting shares on primary storage, avoid data loss by restricting the range of IP addresses that can access the storage. See \"Linux NFS on Local Disks and DAS\" or \"Linux NFS on iSCSI\"."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:233
+# 5e4ab60bb7e7405180895617b9a6efe1
+msgid "NIC bonding is straightforward to implement and provides increased reliability."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:236
+# ff514643a50b4a478172c6dbe1a9befe
+msgid "10G networks are generally recommended for storage access when larger servers that can support relatively more VMs are used."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:239
+# 570bde20d1b84f1ea78c02bab25c0f7d
+msgid "Host capacity should generally be modeled in terms of RAM for the guests. Storage and CPU may be overprovisioned. RAM may not. RAM is usually the limiting factor in capacity designs."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:243
+# 1910d3f68a634d0fb53fdd5f4bde6b8e
+msgid "(XenServer) Configure the XenServer dom0 settings to allocate more memory to dom0. This can enable XenServer to handle larger numbers of virtual machines. We recommend 2940 MB of RAM for XenServer dom0. For instructions on how to do this, see `http://support.citrix.com/article/CTX126531 <http://support.citrix.com/article/CTX126531>`_. The article refers to XenServer 5.6, but the same information applies to XenServer 6.0."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:254
+# c33ddae286b44338ab9b330c918e8e39
+msgid "Maintenance Best Practices"
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:256
+# ae92610bc5164452b9e9527e5f3a8eec
+msgid "Monitor host disk space. Many host failures occur because the host's root disk fills up from logs that were not rotated adequately."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:259
+# 731977493e6d46559ca32f493189b8f4
+msgid "Monitor the total number of VM instances in each cluster, and disable allocation to the cluster if the total is approaching the maximum that the hypervisor can handle. Be sure to leave a safety margin to allow for the possibility of one or more hosts failing, which would increase the VM load on the other hosts as the VMs are redeployed. Consult the documentation for your chosen hypervisor to find the maximum permitted number of VMs per host, then use CloudStack global configuration settings to set this as the default limit. Monitor the VM activity in each cluster and keep the total number of VMs below a safe level that allows for the occasional host failure. For example, if there are N hosts in the cluster, and you want to allow for one host in the cluster to be down at any given time, the total number of VM instances you can permit in the cluster is at most (N-1) \\* (per-host-limit). Once a cluster reaches this number of VMs, use the CloudStack UI to disable allocation to the cluster."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:276
+# edcacc73b0b64b318b84f0f38e00e8d9
+msgid "The lack of up-do-date hotfixes can lead to data corruption and lost VMs."
+msgstr ""
+
+#: ../../choosing_deployment_architecture.rst:278
+# 07e8bf01dab44bb2b1ab4f52a8be4264
+msgid "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."
+msgstr ""
+
diff --git a/source/installguide/locale/pot/configuration.pot b/source/installguide/locale/pot/configuration.pot
new file mode 100644
index 0000000..710eb60
--- /dev/null
+++ b/source/installguide/locale/pot/configuration.pot
@@ -0,0 +1,2550 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../configuration.rst:18
+# 8162e4079fb94ebdb46db436be09b2e4
+msgid "Configuring your CloudStack Installation"
+msgstr ""
+
+#: ../../configuration.rst:20
+# b181cecde5914223835b875145432152
+msgid "This section tells how to add regions, zones, pods, clusters, hosts, storage, and networks to your cloud. If you are unfamiliar with these entities, please begin by looking through `*Cloud Infrastructure Concepts* <http://docs.cloudstack.apache.org/en/latest/concepts.html#cloud-infrastructure-concepts>`_."
+msgstr ""
+
+#: ../../configuration.rst:27
+# 54b40504af90400fa71b9e8b2a0ff779
+msgid "Overview of Provisioning Steps"
+msgstr ""
+
+#: ../../configuration.rst:29
+# 0985357f77e64604b889f263d397930e
+msgid "After the Management Server is installed and running, you can add the compute resources for it to manage. For an overview of how a CloudStack cloud infrastructure is organized, see `“Cloud Infrastructure Overview” <http://docs.cloudstack.apache.org/en/latest/concepts.html#cloud-infrastructure-overview>`_."
+msgstr ""
+
+#: ../../configuration.rst:34
+# c51bc6ff615c4c7b924e0cdabbb11db7
+msgid "To provision the cloud infrastructure, or to scale it up at any time, follow these procedures:"
+msgstr ""
+
+#: ../../configuration.rst:37
+# adf3e4efe0234c6496a1f43d465cd491
+msgid "Define regions (optional). See :ref:`adding-regions`."
+msgstr ""
+
+#: ../../configuration.rst:39
+# 261036fb021e4c5cb2788a51756216ad
+msgid "Add a zone to the region. See :ref:`adding-a-zone`."
+msgstr ""
+
+#: ../../configuration.rst:41
+# dee74c2b0f1a45999f72be907610fd56
+msgid "Add more pods to the zone (optional). See :ref:`adding-a-pod`."
+msgstr ""
+
+#: ../../configuration.rst:43
+# 1196cbbf547c4332aab26253e7429eed
+msgid "Add more clusters to the pod (optional). See :ref:`adding-a-cluster`."
+msgstr ""
+
+#: ../../configuration.rst:45
+# f82489ac595141efaffd718950339e04
+msgid "Add more hosts to the cluster (optional). See :ref:`adding-a-host`."
+msgstr ""
+
+#: ../../configuration.rst:47
+# 4597369285a14d2bbaa5aaeee7043950
+msgid "Add primary storage to the cluster. See :ref:`add-primary-storage`."
+msgstr ""
+
+#: ../../configuration.rst:49
+# d5616551e06641f2bfef5c1aa5ad09b8
+msgid "Add secondary storage to the zone. See :ref:`add-secondary-storage`."
+msgstr ""
+
+#: ../../configuration.rst:51
+# 730a702a42a041f0a604685b09ab09b2
+msgid "Initialize and test the new cloud. See :ref:`initialize-and-test`."
+msgstr ""
+
+#: ../../configuration.rst:53
+# 095a8c4cdac64dd2825fe0ea089804f6
+msgid "When you have finished these steps, you will have a deployment with the following basic structure:"
+msgstr ""
+
+#: ../../configuration.rst:56
+# bdc17df1e28847748e2b0111f5095ab4
+msgid "|provisioning-overview.png: Conceptual overview of a basic deployment|"
+msgstr ""
+
+#: ../../configuration.rst:62
+# bda13ba72d2e4352ad3a1a99d42006c5
+msgid "Adding Regions (optional)"
+msgstr ""
+
+#: ../../configuration.rst:64
+# 5ce04786ce7a453faaa361f1cf6e76e0
+msgid "Grouping your cloud resources into geographic regions is an optional step when provisioning the cloud. For an overview of regions, see `“About Regions” <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-regions>`_."
+msgstr ""
+
+#: ../../configuration.rst:70
+# 43d3ccf2438e462083e530a02e77edc4
+msgid "The First Region: The Default Region"
+msgstr ""
+
+#: ../../configuration.rst:72
+# 3a4d5136ebdf43759e77bd764570aa1f
+msgid "If you do not take action to define regions, then all the zones in your cloud will be automatically grouped into a single default region. This region is assigned the region ID of 1. You can change the name or URL of the default region by displaying the region in the CloudStack UI and clicking the Edit button."
+msgstr ""
+
+#: ../../configuration.rst:80
+# 1b21128d567445d99c07ff46ba4489ff
+msgid "Adding a Region"
+msgstr ""
+
+#: ../../configuration.rst:82
+# 0a5ed06cff2b46419d89cc8a8bdaf915
+msgid "Use these steps to add a second region in addition to the default region."
+msgstr ""
+
+#: ../../configuration.rst:85
+# 0066030160fb4c0aa122d704f26443ad
+msgid "Each region has its own CloudStack instance. Therefore, the first step of creating a new region is to install the Management Server software, on one or more nodes, in the geographic area where you want to set up the new region. Use the steps in the Installation guide. When you come to the step where you set up the database, use the additional command-line flag ``-r <region_id>`` to set a region ID for the new region. The default region is automatically assigned a region ID of 1, so your first additional region might be region 2."
+msgstr ""
+
+#: ../../configuration.rst:98
+# 1d3a3e7282744ac8b1b9fe66fdad230b
+msgid "By the end of the installation procedure, the Management Server should have been started. Be sure that the Management Server installation was successful and complete."
+msgstr ""
+
+#: ../../configuration.rst:102
+# 89e04051a9a648f78a6906817c6298c1
+msgid "Now add the new region to region 1 in CloudStack."
+msgstr ""
+
+#: ../../configuration.rst:104
+# f0bcb3e213ef430881043b8f6b6ec9c2
+msgid "Log in to CloudStack in the first region as root administrator (that is, log in to <region.1.IP.address>:8080/client)."
+msgstr ""
+
+#: ../../configuration.rst:107
+#: ../../configuration.rst:243
+# 719d94ee47d34246b6f101d4ec172902
+# ad4e5a27680944198ef6d847d4bb0192
+msgid "In the left navigation bar, click Regions."
+msgstr ""
+
+#: ../../configuration.rst:109
+# fc94a12b43334f31a8dd65b85b0db964
+msgid "Click Add Region. In the dialog, fill in the following fields:"
+msgstr ""
+
+#: ../../configuration.rst:111
+# 855f2d8079f54a53848390b3e1e85d00
+msgid "ID. A unique identifying number. Use the same number you set in the database during Management Server installation in the new region; for example, 2."
+msgstr ""
+
+#: ../../configuration.rst:115
+# 2dff505d499e42dab8161f715a1c3ba2
+msgid "Name. Give the new region a descriptive name."
+msgstr ""
+
+#: ../../configuration.rst:117
+# 27ad51a0cc564f31b01d1396fd32b638
+msgid "Endpoint. The URL where you can log in to the Management Server in the new region. This has the format <region.2.IP.address>:8080/client."
+msgstr ""
+
+#: ../../configuration.rst:121
+# b3cf11ce84394be6bb0a5cb5c376ce3c
+msgid "Now perform the same procedure in reverse. Log in to region 2, and add region 1."
+msgstr ""
+
+#: ../../configuration.rst:124
+# 602a3773c4814a20a2c30488a1c18f79
+msgid "Copy the account, user, and domain tables from the region 1 database to the region 2 database."
+msgstr ""
+
+#: ../../configuration.rst:127
+#: ../../configuration.rst:202
+# fc4a95280143441fbcc8e6433a301cd1
+# 15839cafaf4f45298afa516f28712b88
+msgid "In the following commands, it is assumed that you have set the root password on the database, which is a CloudStack recommended best practice. Substitute your own MySQL root password."
+msgstr ""
+
+#: ../../configuration.rst:131
+#: ../../configuration.rst:206
+# 5a32436730e4465eb2edc7735a4eaef5
+# 11c4185460654630a87bb504e9c4603c
+msgid "First, run this command to copy the contents of the database:"
+msgstr ""
+
+#: ../../configuration.rst:137
+# 9b75a55461054a1bad3abbe6817b2f65
+msgid "Then run this command to put the data onto the region 2 database:"
+msgstr ""
+
+#: ../../configuration.rst:143
+# 80e5d3db9d2c450a88e53a4be8726923
+msgid "Remove project accounts. Run these commands on the region 2 database:"
+msgstr ""
+
+#: ../../configuration.rst:149
+#: ../../configuration.rst:225
+# 53caa00c3c5145de985c2b13b464b5ae
+# a631ba3cfeb94702915925f0a54f37f9
+msgid "Set the default zone as null:"
+msgstr ""
+
+#: ../../configuration.rst:155
+# 44128fa3ccb44f93a3ec3959b63e55d6
+msgid "Restart the Management Servers in region 2."
+msgstr ""
+
+#: ../../configuration.rst:159
+# b139e5a1fca145a59015dd8b26f2c103
+msgid "Adding Third and Subsequent Regions"
+msgstr ""
+
+#: ../../configuration.rst:161
+# 4b26a84e5c944c01b6cb0bdbf2d96dce
+msgid "To add the third region, and subsequent additional regions, the steps are similar to those for adding the second region. However, you must repeat certain steps additional times for each additional region:"
+msgstr ""
+
+#: ../../configuration.rst:165
+# ffe5c28b1b87436ea5a2f7e84af47bc6
+msgid "Install CloudStack in each additional region. Set the region ID for each region during the database setup step."
+msgstr ""
+
+#: ../../configuration.rst:172
+# bdeafa42b2cc4c2991a4d0d58d70ccbd
+msgid "Once the Management Server is running, add your new region to all existing regions by repeatedly using the Add Region button in the UI. For example, if you were adding region 3:"
+msgstr ""
+
+#: ../../configuration.rst:176
+# aa7dd2e45a4e493bbbc4e9a50428dd39
+msgid "Log in to CloudStack in the first region as root administrator (that is, log in to <region.1.IP.address>:8080/client), and add a region with ID 3, the name of region 3, and the endpoint <region.3.IP.address>:8080/client."
+msgstr ""
+
+#: ../../configuration.rst:181
+# f071890bec3045a6ae288a2c8e906bc8
+msgid "Log in to CloudStack in the second region as root administrator (that is, log in to <region.2.IP.address>:8080/client), and add a region with ID 3, the name of region 3, and the endpoint <region.3.IP.address>:8080/client."
+msgstr ""
+
+#: ../../configuration.rst:186
+# 421cc6da57a94b80997a5ef13cf5acfe
+msgid "Repeat the procedure in reverse to add all existing regions to the new region. For example, for the third region, add the other two existing regions:"
+msgstr ""
+
+#: ../../configuration.rst:190
+# cf1c2389f44d4a86b432cb480580e449
+msgid "Log in to CloudStack in the third region as root administrator (that is, log in to <region.3.IP.address>:8080/client)."
+msgstr ""
+
+#: ../../configuration.rst:193
+# ada88e8be6134f4ebfb9702b645c2504
+msgid "Add a region with ID 1, the name of region 1, and the endpoint <region.1.IP.address>:8080/client."
+msgstr ""
+
+#: ../../configuration.rst:196
+# 9d6d9ac96a174313b0d904d9b1fc65a5
+msgid "Add a region with ID 2, the name of region 2, and the endpoint <region.2.IP.address>:8080/client."
+msgstr ""
+
+#: ../../configuration.rst:199
+# d1c9041bd9774c38982ce11e14463815
+msgid "Copy the account, user, and domain tables from any existing region's database to the new region's database."
+msgstr ""
+
+#: ../../configuration.rst:212
+# 33652ef5006f4edeb7d088b9756b6510
+msgid "Then run this command to put the data onto the new region's database. For example, for region 3:"
+msgstr ""
+
+#: ../../configuration.rst:219
+# 1c3b113d8791401cb0dcdfd3c2fc5a86
+msgid "Remove project accounts. Run these commands on the region 3 database:"
+msgstr ""
+
+#: ../../configuration.rst:231
+# b5ba88de9f22473f84da99081e799f53
+msgid "Restart the Management Servers in the new region."
+msgstr ""
+
+#: ../../configuration.rst:235
+# a9948baaa88f4e959dc8c37b39ddc029
+msgid "Deleting a Region"
+msgstr ""
+
+#: ../../configuration.rst:237
+# 14abc08462004cfda32c9789f06c7b22
+msgid "Log in to each of the other regions, navigate to the one you want to delete, and click Remove Region. For example, to remove the third region in a 3-region cloud:"
+msgstr ""
+
+#: ../../configuration.rst:241
+# 57df6d2d4970438faabdc8614ba6e67a
+msgid "Log in to <region.1.IP.address>:8080/client."
+msgstr ""
+
+#: ../../configuration.rst:245
+# 8028bf784ece4e7daf62cb170b120169
+msgid "Click the name of the region you want to delete."
+msgstr ""
+
+#: ../../configuration.rst:247
+# b2fc750526434ae6a7ced783693b40e4
+msgid "Click the Remove Region button."
+msgstr ""
+
+#: ../../configuration.rst:249
+# 49d26bc1e7244453b51002e2c2ccd48e
+msgid "Repeat these steps for <region.2.IP.address>:8080/client."
+msgstr ""
+
+#: ../../configuration.rst:255
+# dfa99864651448d495ba56e8c8be435e
+msgid "Adding a Zone"
+msgstr ""
+
+#: ../../configuration.rst:257
+# 774412c06e41450181b4ce9c74727ddc
+msgid "When you add a new zone, you will be prompted to configure the zone’s physical network and add the first pod, cluster, host, primary storage, and secondary storage."
+msgstr ""
+
+#: ../../configuration.rst:261
+# 49e4a1629dd0416499eb13760cd38d1b
+msgid "Log in to the CloudStack UI as the root administrator. See `“Log In to the UI” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_."
+msgstr ""
+
+#: ../../configuration.rst:263
+# d6902134301b4889ad289a5806abf1e4
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../configuration.rst:265
+# ade8f3f94c154f1c89537d25e3fd7379
+msgid "On Zones, click View More."
+msgstr ""
+
+#: ../../configuration.rst:267
+# 912e3cd3fe35426abc8c5283086fc5c2
+msgid "Click Add Zone. The zone creation wizard will appear."
+msgstr ""
+
+#: ../../configuration.rst:269
+# c04973210d4243a5a4e97bd2c6e9fe02
+msgid "Choose one of the following network types:"
+msgstr ""
+
+#: ../../configuration.rst:271
+# 28de3b1d237b4562ab0e114352a9d17a
+msgid "**Basic.** For AWS-style networking. Provides a single network where each VM instance is assigned an IP directly from the network. Guest isolation can be provided through layer-3 means such as security groups (IP address source filtering)."
+msgstr ""
+
+#: ../../configuration.rst:276
+# c30938018fd3423d9da33dc59b76f9f5
+msgid "**Advanced.** For more sophisticated network topologies. This network model provides the most flexibility in defining guest networks and providing custom network offerings such as firewall, VPN, or load balancer support."
+msgstr ""
+
+#: ../../configuration.rst:281
+# 03a0589bdc4a49528ac92074d0a70776
+msgid "The rest of the steps differ depending on whether you chose Basic or Advanced. Continue with the steps that apply to you:"
+msgstr ""
+
+#: ../../configuration.rst:284
+# bff1cc1731ca4cdb859052b81a3fa2c8
+msgid "`“Basic Zone Configuration” <#basic-zone-configuration>`_"
+msgstr ""
+
+#: ../../configuration.rst:286
+# 2dd7cac463554ed4bde0647d38500a5f
+msgid "`“Advanced Zone Configuration” <#advanced-zone-configuration>`_"
+msgstr ""
+
+#: ../../configuration.rst:290
+# cb4a637d5ad242448420fd13df8a7e29
+msgid "Basic Zone Configuration"
+msgstr ""
+
+#: ../../configuration.rst:292
+# dffcb46170814a6aaf35cf251f10287a
+msgid "After you select Basic in the Add Zone wizard and click Next, you will be asked to enter the following details. Then click Next."
+msgstr ""
+
+#: ../../configuration.rst:295
+#: ../../configuration.rst:514
+# 28f1173455e549d4ac7adf938a40c70c
+# ecac47e28b5d4834bee99838438a221c
+msgid "**Name.** A name for the zone."
+msgstr ""
+
+#: ../../configuration.rst:297
+#: ../../configuration.rst:516
+# 4fcd0ce95f0b4136934d20a7007a5165
+# 2f1157bfaa2c475985f1902f67db381c
+msgid "**DNS 1 and 2.** These are DNS servers for use by guest VMs in the zone. These DNS servers will be accessed via the public network you will add later. The public IP addresses for the zone must have a route to the DNS server named here."
+msgstr ""
+
+#: ../../configuration.rst:302
+# 4808ff4052234d66ac6543bf631b8b83
+msgid "**Internal DNS 1 and Internal DNS 2.** These are DNS servers for use by system VMs in the zone (these are VMs used by CloudStack itself, such as virtual routers, console proxies, and Secondary Storage VMs.) These DNS servers will be accessed via the management traffic network interface of the System VMs. The private IP address you provide for the pods must have a route to the internal DNS server named here."
+msgstr ""
+
+#: ../../configuration.rst:310
+#: ../../configuration.rst:538
+# 05f039680a9649d59b7c565c57e22f06
+# 21fe556029bb4e01962ab112ac9768f4
+msgid "**Hypervisor.** (Introduced in version 3.0.1) Choose the hypervisor for the first cluster in the zone. You can add clusters with different hypervisors later, after you finish adding the zone."
+msgstr ""
+
+#: ../../configuration.rst:315
+# c00029912e7046949d6766c29a38336e
+msgid "**Network Offering.** Your choice here determines what network services will be available on the network for guest VMs."
+msgstr ""
+
+#: ../../configuration.rst:319
+# e3fe221d9a044cc18fd23016249ec1cc
+msgid "Network Offering"
+msgstr ""
+
+#: ../../configuration.rst:319
+# 0c9256246d864525a6d27a188b8e926d
+msgid "Description"
+msgstr ""
+
+#: ../../configuration.rst:321
+# 17becb3e858a4876942de300eef4c2bf
+msgid "DefaultSharedNetworkOfferingWithSGService"
+msgstr ""
+
+#: ../../configuration.rst:321
+# 6657626819c84e93af54d41c8cc692fe
+msgid "If you want to enable security groups for guest traffic isolation, choose this. (See Using Security Groups to Control Traffic to VMs.)"
+msgstr ""
+
+#: ../../configuration.rst:322
+# af8f6480878642e78421c05628436d07
+msgid "DefaultSharedNetworkOffering"
+msgstr ""
+
+#: ../../configuration.rst:322
+# 4cd8c72bfb834f82bd91743d1ac74e53
+msgid "If you do not need security groups, choose this."
+msgstr ""
+
+#: ../../configuration.rst:323
+# 702d31b78c8146c284f36761d3ae4129
+msgid "DefaultSharedNetscalerEIPandELBNetworkOffering"
+msgstr ""
+
+#: ../../configuration.rst:323
+# 4bd344a4652e48bc956cf57fd1aa5404
+msgid "If you have installed a Citrix NetScaler appliance as part of your zone network, and you will be using its Elastic IP and Elastic Load Balancing features, choose this. With the EIP and ELB features, a basic zone with security groups enabled can offer 1:1 static NAT and load balancing."
+msgstr ""
+
+#: ../../configuration.rst:327
+#: ../../configuration.rst:529
+# 0b90574172fb4e7cbac4151d6526f593
+# 6d30529dd4ac40c19bb562424065502c
+msgid "**Network Domain.** (Optional) If you want to assign a special domain name to the guest VM network, specify the DNS suffix."
+msgstr ""
+
+#: ../../configuration.rst:330
+#: ../../configuration.rst:543
+# 9036e7c5033747d283076f98506ccb51
+# 815323d66e34477eab427c9fdfed1c83
+msgid "**Public.** A public zone is available to all users. A zone that is not public will be assigned to a particular domain. Only users in that domain will be allowed to create guest VMs in this zone."
+msgstr ""
+
+#: ../../configuration.rst:334
+#: ../../configuration.rst:547
+# 21d7ccd878e94405b989441562b0599b
+# a9e870bbb6004173be4bfa18835bcb70
+msgid "Choose which traffic types will be carried by the physical network."
+msgstr ""
+
+#: ../../configuration.rst:336
+# bc24ee0196bb4ef9aab22883c8434456
+msgid "The traffic types are management, public, guest, and storage traffic. For more information about the types, roll over the icons to display their tool tips, or see Basic Zone Network Traffic Types. This screen starts out with some traffic types already assigned. To add more, drag and drop traffic types onto the network. You can also change the network name if desired."
+msgstr ""
+
+#: ../../configuration.rst:343
+# 48f3ce0bb26d4d94963acae89c848fa2
+msgid "Assign a network traffic label to each traffic type on the physical network. These labels must match the labels you have already defined on the hypervisor host. To assign each label, click the Edit button under the traffic type icon. A popup dialog appears where you can type the label, then click OK."
+msgstr ""
+
+#: ../../configuration.rst:349
+#: ../../configuration.rst:568
+# 078e7952b6574b6684e5495207335bec
+# 46d267d97c60451a88ceeeb647987e77
+msgid "These traffic labels will be defined only for the hypervisor selected for the first cluster. For all other hypervisors, the labels can be configured after the zone is created."
+msgstr ""
+
+#: ../../configuration.rst:353
+#: ../../configuration.rst:583
+# 4ee547a64dce4459ae3b5d914984b125
+# 0e5056a8e6fc4f5cb200cda3d7a2525c
+msgid "Click Next."
+msgstr ""
+
+#: ../../configuration.rst:355
+# 0c8ac4ed983c46f4b288584ac8bdf37b
+msgid "(NetScaler only) If you chose the network offering for NetScaler, you have an additional screen to fill out. Provide the requested details to set up the NetScaler, then click Next."
+msgstr ""
+
+#: ../../configuration.rst:359
+# c40cb3f0ffff4013b271dc76dddcf958
+msgid "**IP address.** The NSIP (NetScaler IP) address of the NetScaler device."
+msgstr ""
+
+#: ../../configuration.rst:362
+# 8ea7e4f0a7ef4614b9fbbac8d8fd2d8a
+msgid "**Username/Password.** The authentication credentials to access the device. CloudStack uses these credentials to access the device."
+msgstr ""
+
+#: ../../configuration.rst:366
+# ee173abcc1e54f3d9917adc4936e9b97
+msgid "**Type.** NetScaler device type that is being added. It could be NetScaler VPX, NetScaler MPX, or NetScaler SDX. For a comparison of the types, see About Using a NetScaler Load Balancer."
+msgstr ""
+
+#: ../../configuration.rst:370
+# 8531937f377e40e9b877f0205da08b18
+msgid "**Public interface.** Interface of NetScaler that is configured to be part of the public network."
+msgstr ""
+
+#: ../../configuration.rst:373
+# fa6bf0c0d9d24792afde4c7cfc17a1c3
+msgid "**Private interface.** Interface of NetScaler that is configured to be part of the private network."
+msgstr ""
+
+#: ../../configuration.rst:376
+# badd0cf691644807ad806889ad40db32
+msgid "**Number of retries.** Number of times to attempt a command on the device before considering the operation failed. Default is 2."
+msgstr ""
+
+#: ../../configuration.rst:379
+# 3544f121bc064e29a3a27f191cee9f84
+msgid "**Capacity.** Number of guest networks/accounts that will share this NetScaler device."
+msgstr ""
+
+#: ../../configuration.rst:382
+# 8332d9e920fe463a8dca1db0f77f8583
+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 ""
+
+#: ../../configuration.rst:387
+# 34827b0bfdd34781b875e6887bebfc75
+msgid "(NetScaler only) Configure the IP range for public traffic. The IPs in this range will be used for the static NAT capability which you enabled by selecting the network offering for NetScaler with EIP and ELB. Enter the following details, then click Add. If desired, you can repeat this step to add more IP ranges. When done, click Next."
+msgstr ""
+
+#: ../../configuration.rst:393
+#: ../../configuration.rst:589
+# 635dae2c5e9a4fc78b1708c6ebf80460
+# f179dd4093cc42efbe89a0c52531a934
+msgid "**Gateway.** The gateway in use for these IP addresses."
+msgstr ""
+
+#: ../../configuration.rst:395
+#: ../../configuration.rst:591
+# 7022d1ca2ebb4f0d82e4bd5af7ad38c8
+# ade1edfc41014640bbaf07a8cb6d7a30
+msgid "**Netmask.** The netmask associated with this IP range."
+msgstr ""
+
+#: ../../configuration.rst:397
+#: ../../configuration.rst:593
+# 7bfb9d769b874eed8399dd1dce773692
+# cea91ee2b41f476093dd8e6cb6c464a4
+msgid "**VLAN.** The VLAN that will be used for public traffic."
+msgstr ""
+
+#: ../../configuration.rst:399
+# f13431658b2445c48bca7d494a057961
+msgid "**Start IP/End IP.** A range of IP addresses that are assumed to be accessible from the Internet and will be allocated for access to guest VMs."
+msgstr ""
+
+#: ../../configuration.rst:403
+#: ../../configuration.rst:599
+# c608789049734f06a202678e647078ea
+# cb65d7f39c6d43b5878166ff469a9336
+msgid "In a new zone, CloudStack adds the first pod for you. You can always add more pods later. For an overview of what a pod is, see `“About Pods” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-pods>`_."
+msgstr ""
+
+#: ../../configuration.rst:407
+#: ../../configuration.rst:603
+# 133a33d409fd46a1af933404a8b7cd37
+# ca67116d4f464703befcd3acaf5541fa
+msgid "To configure the first pod, enter the following, then click Next:"
+msgstr ""
+
+#: ../../configuration.rst:409
+#: ../../configuration.rst:605
+# 731b1cd2a3a24733a2509db423e05a3f
+# ef9297fe5b3b4a60a47310045adc4a7d
+msgid "**Pod Name.** A name for the pod."
+msgstr ""
+
+#: ../../configuration.rst:411
+#: ../../configuration.rst:607
+# 06e37281b36442f09653c54f71fd6baa
+# 26c99791b3424045afcfdc3461c2e273
+msgid "**Reserved system gateway.** The gateway for the hosts in that pod."
+msgstr ""
+
+#: ../../configuration.rst:414
+#: ../../configuration.rst:610
+# e043e1605e4740d0b7ae424058ccf656
+# 8668dd9e73bc45b5b4963e201aaa426f
+msgid "**Reserved system netmask.** The network prefix that defines the pod's subnet. Use CIDR notation."
+msgstr ""
+
+#: ../../configuration.rst:417
+#: ../../configuration.rst:790
+# 2d2d591fcc7b4b5f9a841fc3625685e4
+# cf5db04d254d4fdca2d3083d47ed4820
+msgid "**Start/End Reserved System IP.** The IP range in the management network that CloudStack uses to manage various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP. For more information, see System Reserved IP Addresses."
+msgstr ""
+
+#: ../../configuration.rst:422
+# dc5d7a38ccf54de5b4ba93d50d497df8
+msgid "Configure the network for guest traffic. Provide the following, then click Next:"
+msgstr ""
+
+#: ../../configuration.rst:425
+# ec278db6dee347a3b0b7ccd5199fb75e
+msgid "**Guest gateway.** The gateway that the guests should use."
+msgstr ""
+
+#: ../../configuration.rst:427
+# e08dd136c0db40c4919d4e09e251a450
+msgid "**Guest netmask.** The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../configuration.rst:430
+# d7beb7ec370b474688190302620f092d
+msgid "**Guest start IP/End IP.** Enter the first and last IP addresses that define a range that CloudStack can assign to guests."
+msgstr ""
+
+#: ../../configuration.rst:433
+# 21367aec79504bf6b0523f8b8ff518c9
+msgid "We strongly recommend the use of multiple NICs. If multiple NICs are used, they may be in a different subnet."
+msgstr ""
+
+#: ../../configuration.rst:436
+# aae6aaee21bf4878b935bad1cc640b4e
+msgid "If one NIC is used, these IPs should be in the same CIDR as the pod CIDR."
+msgstr ""
+
+#: ../../configuration.rst:439
+# 760580b3523b4418a99099137bb67922
+msgid "In a new pod, CloudStack adds the first cluster for you. You can always add more clusters later. For an overview of what a cluster is, see About Clusters."
+msgstr ""
+
+#: ../../configuration.rst:443
+#: ../../configuration.rst:627
+# 44c7f5931d5e4e35b85d85089a2cf0e2
+# 0b9c98c65d92481ab54bf4e8ed5ba5a8
+msgid "To configure the first cluster, enter the following, then click Next:"
+msgstr ""
+
+#: ../../configuration.rst:445
+# 51c6cb2616384dc2a2fdde4178e35993
+msgid "**Hypervisor.** (Version 3.0.0 only; in 3.0.1, this field is read only) Choose the type of hypervisor software that all hosts in this cluster will run. If you choose VMware, additional fields appear so you can give information about a vSphere cluster. For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. See Add Cluster: vSphere."
+msgstr ""
+
+#: ../../configuration.rst:453
+#: ../../configuration.rst:637
+# 0a1f5e7d557a445fbd943a2375f81ce9
+# 2616a88c400442bc8a9ff5fb9fd7ce49
+msgid "**Cluster name.** Enter a name for the cluster. This can be text of your choosing and is not used by CloudStack."
+msgstr ""
+
+#: ../../configuration.rst:456
+# f215a4cf027b40eea80996afea404e88
+msgid "In a new cluster, CloudStack adds the first host for you. You can always add more hosts later. For an overview of what a host is, see About Hosts."
+msgstr ""
+
+#: ../../configuration.rst:461
+# a4958ea1500c4d65a7ec65554fb9c8f0
+msgid "When you add a hypervisor host to CloudStack, the host must not have any VMs already running."
+msgstr ""
+
+#: ../../configuration.rst:464
+#: ../../configuration.rst:648
+# a7aa2568c3144be19c371ba08be4bf6d
+# 7686b9f224ea40b48d2c4c7b3d64e15b
+msgid "Before you can configure the host, you need to install the hypervisor software on the host. You will need to know which version of the hypervisor software version is supported by CloudStack and what additional configuration is required to ensure the host will work with CloudStack. To find these installation details, see:"
+msgstr ""
+
+#: ../../configuration.rst:470
+# 4866dcbbc18a4c9e96b993ed1e536f29
+msgid "Citrix XenServer Installation and Configuration"
+msgstr ""
+
+#: ../../configuration.rst:472
+#: ../../configuration.rst:656
+# 876393f442894c6389d1edf6e6ebc213
+# 7cbfdd4d4aad40cfbcf4aea9c9fd6ce2
+msgid "VMware vSphere Installation and Configuration"
+msgstr ""
+
+#: ../../configuration.rst:474
+# 93504af6c05b46fcb6ccc59cd48de0d0
+msgid "KVM vSphere Installation and Configuration"
+msgstr ""
+
+#: ../../configuration.rst:476
+#: ../../configuration.rst:660
+# 5e077e29fb7446a6bda46732cc0eb453
+# 2d6f19cf4a334139b27e4f7a94b8bf92
+msgid "To configure the first host, enter the following, then click Next:"
+msgstr ""
+
+#: ../../configuration.rst:478
+#: ../../configuration.rst:662
+# 0e194db1641a4be2ae5d6ed3f2d27575
+# b7727092534b455e924a0b5ddfa9ec69
+msgid "**Host Name.** The DNS name or IP address of the host."
+msgstr ""
+
+#: ../../configuration.rst:480
+# 1af10b11095449a496d9b3304652ba03
+msgid "**Username.** The username is root."
+msgstr ""
+
+#: ../../configuration.rst:482
+#: ../../configuration.rst:666
+# 98f8e09abbc547ca994b5156f2dbcaa6
+# 4623683d93bf4b02a802a809c6786faf
+msgid "**Password.** This is the password for the user named above (from your XenServer or KVM install)."
+msgstr ""
+
+#: ../../configuration.rst:485
+# 258ef7abb2b447ebb6cce1508920d12b
+msgid "**Host Tags.** (Optional) Any labels that you use to categorize hosts for ease of maintenance. For example, you can set this to the cloud's HA tag (set in the ha.tag global configuration parameter) if you want this host to be used only for VMs with the \"high availability\" feature enabled. For more information, see HA-Enabled Virtual Machines as well as HA for Hosts."
+msgstr ""
+
+#: ../../configuration.rst:492
+# 55ee6f53cea246bda767b3f91ed77753
+msgid "In a new cluster, CloudStack adds the first primary storage server for you. You can always add more servers later. For an overview of what primary storage is, see About Primary Storage."
+msgstr ""
+
+#: ../../configuration.rst:496
+#: ../../configuration.rst:682
+# 33955d5773764a229a1faa4ba31636a8
+# f58343456b724277b2179ea70214dd8e
+msgid "To configure the first primary storage server, enter the following, then click Next:"
+msgstr ""
+
+#: ../../configuration.rst:499
+#: ../../configuration.rst:685
+#: ../../configuration.rst:1180
+# 882e651ffb4f487196c12a9ecbd5b66c
+# 02cefa6c9ff44810b682b0420f16e4c3
+# 7b2c3d9c2fa347bbb7ae181ee559419e
+msgid "**Name.** The name of the storage device."
+msgstr ""
+
+#: ../../configuration.rst:501
+# 9108c1607da247cb819f2b3dd2b94186
+msgid "**Protocol.** For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM, choose NFS, SharedMountPoint,CLVM, or RBD. For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. The remaining fields in the screen vary depending on what you choose here."
+msgstr ""
+
+#: ../../configuration.rst:509
+# a95cec57590f4eb9bb5720ab7fb7809c
+msgid "Advanced Zone Configuration"
+msgstr ""
+
+#: ../../configuration.rst:511
+# e9085595c59b47d59920970c045cd7ae
+msgid "After you select Advanced in the Add Zone wizard and click Next, you will be asked to enter the following details. Then click Next."
+msgstr ""
+
+#: ../../configuration.rst:521
+# a584fb17ef794dad83499d140687e136
+msgid "**Internal DNS 1 and Internal DNS 2.** These are DNS servers for use by system VMs in the zone(these are VMs used by CloudStack itself, such as virtual routers, console proxies,and Secondary Storage VMs.) These DNS servers will be accessed via the management traffic network interface of the System VMs. The private IP address you provide for the pods must have a route to the internal DNS server named here."
+msgstr ""
+
+#: ../../configuration.rst:532
+# 7f5a0f00682d4f05af43eb2dcc7c60fb
+msgid "**Guest CIDR.** This is the CIDR that describes the IP addresses in use in the guest virtual networks in this zone. For example, 10.1.1.0/24. As a matter of good practice you should set different CIDRs for different zones. This will make it easier to set up VPNs between networks in different zones."
+msgstr ""
+
+#: ../../configuration.rst:549
+# fbaf58d0ff1649dd8a0f05537743c882
+msgid "The traffic types are management, public, guest, and storage traffic. For more information about the types, roll over the icons to display their tool tips, or see `“Advanced Zone Network Traffic Types” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#advanced-zone-network-traffic-types>`_. This screenstarts out with one network already configured. If you have multiple physical networks, you need to add more. Drag and drop traffic types onto a greyed-out network and it will become active. You can move the traffic icons from one network to another; for example, if the default traffic types shown for Network 1 do not match your actual setup, you can move them down. You can also change the network names if desired."
+msgstr ""
+
+#: ../../configuration.rst:561
+# a1c899d9956d4667a5fa43596d6d8f70
+msgid "(Introduced in version 3.0.1) Assign a network traffic label to each traffic type on each physical network. These labels must match the labels you have already defined on the hypervisor host. To assign each label, click the Edit button under the traffic type icon within each physical network. A popup dialog appears where you can type the label, then click OK."
+msgstr ""
+
+#: ../../configuration.rst:572
+# 805792aff6994e028ce9205047e477f1
+msgid "(VMware only) If you have enabled Nexus dvSwitch in the environment, you must specify the corresponding Ethernet port profile names as network traffic label for each traffic type on the physical network. For more information on Nexus dvSwitch, see Configuring a vSphere Cluster with Nexus 1000v Virtual Switch in the Installation Guide. If you have enabled VMware dvSwitch in the environment, you must specify the corresponding Switch name as network traffic label for each traffic type on the physical network. For more information, see Configuring a VMware Datacenter with VMware Distributed Virtual Switch in the Installation Guide."
+msgstr ""
+
+#: ../../configuration.rst:585
+# 2df839852be644778c41107b53c0eef8
+msgid "Configure the IP range for public Internet traffic. Enter the following details, then click Add. If desired, you can repeat this step to add more public Internet IP ranges. When done, click Next."
+msgstr ""
+
+#: ../../configuration.rst:595
+# 4854b23855194f6a95f455049a970d9c
+msgid "**Start IP/End IP.** A range of IP addresses that are assumed to be accessible from the Internet and will be allocated for access to guest networks."
+msgstr ""
+
+#: ../../configuration.rst:613
+# b27b5e010eb64430b9cc36887f0155ab
+msgid "**Start/End Reserved System IP.** The IP range in the management network that CloudStack uses to manage various system VMs, such as Secondary Storage VMs, Console Proxy VMs, and DHCP. For more information, see `“System Reserved IP Addresses” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#id4>`_."
+msgstr ""
+
+#: ../../configuration.rst:619
+# 6d27295ebf7948e6a7c0b2138ca9fa39
+msgid "Specify a range of VLAN IDs to carry guest traffic for each physical network (see VLAN Allocation Example ), then click Next."
+msgstr ""
+
+#: ../../configuration.rst:622
+# 58ec28ce7043492ab818e135bd5ad764
+msgid "In a new pod, CloudStack adds the first cluster for you. You can always add more clusters later. For an overview of what a cluster is, see `“About Clusters” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-clusters>`_."
+msgstr ""
+
+#: ../../configuration.rst:629
+# c4117492d58e4cc7a95877d4420c0f77
+msgid "**Hypervisor.** (Version 3.0.0 only; in 3.0.1, this field is read only) Choose the type of hypervisor software that all hosts in this cluster will run. If you choose VMware, additional fields appear so you can give information about a vSphere cluster. For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. See Add Cluster: vSphere ."
+msgstr ""
+
+#: ../../configuration.rst:640
+# a33530a965844729a700ddcafd654cab
+msgid "In a new cluster, CloudStack adds the first host for you. You can always add more hosts later. For an overview of what a host is, see `“About Hosts” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-hosts>`_."
+msgstr ""
+
+#: ../../configuration.rst:645
+# 70099c0bbf4c4ab79b74ce130e472676
+msgid "When you deploy CloudStack, the hypervisor host must not have any VMs already running."
+msgstr ""
+
+#: ../../configuration.rst:654
+# 969595946df24f7b9a30efd4829ce89d
+msgid "Citrix XenServer Installation for CloudStack"
+msgstr ""
+
+#: ../../configuration.rst:658
+# 2286f6a6c02c44fca23c04f2d6e05175
+msgid "KVM Installation and Configuration"
+msgstr ""
+
+#: ../../configuration.rst:664
+# 9263f822255744319df0264ecd6cf42b
+msgid "**Username.** Usually root."
+msgstr ""
+
+#: ../../configuration.rst:669
+# 617da6e8e7dc42cc94c5649b11b4f94e
+msgid "**Host Tags.** (Optional) Any labels that you use to categorize hosts for ease of maintenance. For example, you can set to the cloud's HA tag (set in the ha.tag global configuration parameter) if you want this host to be used only for VMs with the \"high availability\" feature enabled. For more information, see HA-Enabled Virtual Machines as well as HA for Hosts, both in the Administration Guide."
+msgstr ""
+
+#: ../../configuration.rst:677
+# d405480d45fa4402a325beac9b7a9b35
+msgid "In a new cluster, CloudStack adds the first primary storage server for you. You can always add more servers later. For an overview of what primary storage is, see `“About Primary Storage” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-primary-storage>`_."
+msgstr ""
+
+#: ../../configuration.rst:687
+# ef6c13fd4cd641ebb3914aa5bcfd4b5e
+msgid "**Protocol.** For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM, choose NFS, SharedMountPoint, CLVM, and RBD. For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. The remaining fields in the screen vary depending on what you choose here."
+msgstr ""
+
+#: ../../configuration.rst:694
+# dbd90d6e53d34d4cad8f2c3a097f5917
+msgid "NFS"
+msgstr ""
+
+#: ../../configuration.rst:694
+#: ../../configuration.rst:702
+#: ../../configuration.rst:713
+# d905c0e524884434bbce1a596ab9e8ae
+# adc6172c6fb94c9e808ea5729ec0015e
+# 9564e49540d445a6a796666072388c85
+msgid "**Server.** The IP address or DNS name of the storage device."
+msgstr ""
+
+#: ../../configuration.rst:696
+#: ../../configuration.rst:757
+# 50bc8991790d4273aa59efd2d73b42f2
+# 8920e004ba914957be0b285c5b9566a0
+msgid "**Path.** The exported path from the server."
+msgstr ""
+
+#: ../../configuration.rst:698
+#: ../../configuration.rst:709
+#: ../../configuration.rst:718
+#: ../../configuration.rst:725
+#: ../../configuration.rst:735
+# 66e08a767e8e407c91c01e0b57c9c4d5
+# b827c64c04014e0ca658487659b87b6e
+# 8f3262da3e114bf5bf62741b9284b984
+# b147800ccb4948659610f3b243d04b72
+# 669620fc4f1a4de9b9b00aeddbf9432a
+msgid "**Tags (optional).** The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings."
+msgstr ""
+
+#: ../../configuration.rst:702
+# fffee6632fb244ef9ee793f9ea6fae65
+msgid "iSCSI"
+msgstr ""
+
+#: ../../configuration.rst:704
+# cab8f091a9bd419abee44664e284f629
+msgid "**Target IQN.** The IQN of the target. For example, iqn.1986-03.com.sun:02:01ec9bb549-1271378984."
+msgstr ""
+
+#: ../../configuration.rst:707
+# 66b75a8b32674947875a04ab9de122c9
+msgid "**Lun.** The LUN number. For example, 3."
+msgstr ""
+
+#: ../../configuration.rst:713
+# 604eb8fc1cff40e5bb3760beef6766f0
+msgid "preSetup"
+msgstr ""
+
+#: ../../configuration.rst:715
+# b99f246bfc974f48933179b70c1d0668
+msgid "**SR Name-Label.** Enter the name-label of the SR that has been set up outside CloudStack."
+msgstr ""
+
+#: ../../configuration.rst:722
+# b1b68aca6c6c4ff2bc13b7e384154ed7
+msgid "SharedMountPoint"
+msgstr ""
+
+#: ../../configuration.rst:722
+# a2563f947f8142b9a8ba024d822e6d8f
+msgid "**Path.** The path on each host that is where this primary storage is mounted. For example, \"/mnt/primary\"."
+msgstr ""
+
+#: ../../configuration.rst:729
+# abbb3c959ada42e28ca5963f413c6f36
+msgid "VMFS"
+msgstr ""
+
+#: ../../configuration.rst:729
+# 4ec550d124a34334868e01b615fd7cf8
+msgid "**Server.** The IP address or DNS name of the vCenter server."
+msgstr ""
+
+#: ../../configuration.rst:731
+# daadb05d2bbb451c921f7924eafc3bba
+msgid "**Path.** A combination of the datacenter name and the datastore name. The format is \"/\" datacenter name \"/\" datastore name. For example, \"/cloud.dc.VM/cluster1datastore\"."
+msgstr ""
+
+#: ../../configuration.rst:741
+#: ../../configuration.rst:1230
+# cc85beb87ff14852b2e9293f8884c708
+# 3c79b79a17014af1bc0392d7137b940b
+msgid "The tag sets on primary storage across clusters in a Zone must be identical. For example, if cluster A provides primary storage that has tags T1 and T2, all other clusters in the Zone must also provide primary storage that has tags T1 and T2."
+msgstr ""
+
+#: ../../configuration.rst:746
+# 77dd355c1a1b48318b9b054f5698f6db
+msgid "In a new zone, CloudStack adds the first secondary storage server for you. For an overview of what secondary storage is, see `“About Secondary Storage” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-secondary-storage>`_."
+msgstr ""
+
+#: ../../configuration.rst:750
+# 9ffcbb5748c44307afcb86b84bef2bd8
+msgid "Before you can fill out this screen, you need to prepare the secondary storage by setting up NFS shares and installing the latest CloudStack System VM template. See Adding Secondary Storage :"
+msgstr ""
+
+#: ../../configuration.rst:754
+# fcc9a36dd6c749198217088bf5381ee2
+msgid "**NFS Server.** The IP address of the server or fully qualified domain name of the server."
+msgstr ""
+
+#: ../../configuration.rst:759
+# d656e3c4d2c14785a91388ffd2a2e0da
+msgid "Click Launch."
+msgstr ""
+
+#: ../../configuration.rst:765
+# e5249101b498485c840bf4c9715351d8
+msgid "Adding a Pod"
+msgstr ""
+
+#: ../../configuration.rst:767
+# 80ce36fa017948b38ec42cdabd458282
+msgid "When you created a new zone, CloudStack adds the first pod for you. You can add more pods at any time using the procedure in this section."
+msgstr ""
+
+#: ../../configuration.rst:770
+# 1a095154f142425dbfdaedb0e4ea3a1b
+msgid "Log in to the CloudStack UI. See `“Log In to the UI” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_."
+msgstr ""
+
+#: ../../configuration.rst:773
+# 4b20a9fd84f2479a9b463179b2c04d3c
+msgid "In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone to which you want to add a pod."
+msgstr ""
+
+#: ../../configuration.rst:776
+# 1ceafce4645345f8984ba3e1f562f435
+msgid "Click the Compute and Storage tab. In the Pods node of the diagram, click View All."
+msgstr ""
+
+#: ../../configuration.rst:779
+# 3c5e8d963225430ca2e31368837c3d6a
+msgid "Click Add Pod."
+msgstr ""
+
+#: ../../configuration.rst:781
+# 8209d5987fa14c1fa7d44d186705d0c9
+msgid "Enter the following details in the dialog."
+msgstr ""
+
+#: ../../configuration.rst:783
+# d3f7f6f5ca814cc3b14a99cd76ae042d
+msgid "**Name.** The name of the pod."
+msgstr ""
+
+#: ../../configuration.rst:785
+# f7c4912b240c487eaa879e309615b020
+msgid "**Gateway.** The gateway for the hosts in that pod."
+msgstr ""
+
+#: ../../configuration.rst:787
+# 914c5b1a1c8c4530999080d4c89912e6
+msgid "**Netmask.** The network prefix that defines the pod's subnet. Use CIDR notation."
+msgstr ""
+
+#: ../../configuration.rst:795
+#: ../../configuration.rst:830
+#: ../../configuration.rst:1235
+# 80f5b85272584772b1caa17474ea4863
+# ba52d2639a9a44a394ac0e6d13cbbfff
+# 35b375637fca46aabc7848985f6ba3da
+msgid "Click OK."
+msgstr ""
+
+#: ../../configuration.rst:801
+# f12f333c032e4bf6b2906a933d4da17e
+msgid "Adding a Cluster"
+msgstr ""
+
+#: ../../configuration.rst:803
+# 77eccc1ced604f3482969b1b37ac94f7
+msgid "You need to tell CloudStack about the hosts that it will manage. Hosts exist inside clusters, so before you begin adding hosts to the cloud, you must add at least one cluster."
+msgstr ""
+
+#: ../../configuration.rst:809
+# 2541d85ea4c64120ba7c1d1bbdb0de54
+msgid "Add Cluster: KVM or XenServer"
+msgstr ""
+
+#: ../../configuration.rst:811
+# a19c5e6d471b43ce9df963073e844a41
+msgid "These steps assume you have already installed the hypervisor on the hosts and logged in to the CloudStack UI."
+msgstr ""
+
+#: ../../configuration.rst:814
+#: ../../configuration.rst:863
+# 0076f4bb3d004b4ba430db294c83e5c6
+# 39ab1bc8c27845f2b2df2deb2c47d959
+msgid "In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the cluster."
+msgstr ""
+
+#: ../../configuration.rst:817
+#: ../../configuration.rst:1162
+# f5468a45f1584146b9c21637e83ead16
+# 709bb466c6b74ab1a145f5edd5aa1cc6
+msgid "Click the Compute tab."
+msgstr ""
+
+#: ../../configuration.rst:819
+# 9c5dcf9e60b74076b98428a9785acffa
+msgid "In the Clusters node of the diagram, click View All."
+msgstr ""
+
+#: ../../configuration.rst:821
+#: ../../configuration.rst:871
+# 4ff74ef29511451d84f51b7112d91396
+# 3b57564e3ea441e2a8ba501a340267ca
+msgid "Click Add Cluster."
+msgstr ""
+
+#: ../../configuration.rst:823
+# 5fe5d5e811774dc483d55f29b28b461c
+msgid "Choose the hypervisor type for this cluster."
+msgstr ""
+
+#: ../../configuration.rst:825
+# 6e00c60f805341cdbfb1583ad80b4c52
+msgid "Choose the pod in which you want to create the cluster."
+msgstr ""
+
+#: ../../configuration.rst:827
+# f214b054a5844ee380b80bc55b6e9123
+msgid "Enter a name for the cluster. This can be text of your choosing and is not used by CloudStack."
+msgstr ""
+
+#: ../../configuration.rst:834
+# 1edfca4aeda94b35b4981b9ea1898063
+msgid "Add Cluster: vSphere"
+msgstr ""
+
+#: ../../configuration.rst:836
+# f22ee86140014d7b9d84b11a6b68a5a2
+msgid "Host management for vSphere is done through a combination of vCenter and the CloudStack admin UI. CloudStack requires that all hosts be in a CloudStack cluster, but the cluster may consist of a single host. As an administrator you must decide if you would like to use clusters of one host or of multiple hosts. Clusters of multiple hosts allow for features like live migration. Clusters also require shared storage such as NFS or iSCSI."
+msgstr ""
+
+#: ../../configuration.rst:844
+# 5f108c515fe845f9b12bb18f429e0ea5
+msgid "For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. Follow these requirements:"
+msgstr ""
+
+#: ../../configuration.rst:848
+# 14090efdfc144ee89b2517b48c3cd083
+msgid "Do not put more than 8 hosts in a vSphere cluster"
+msgstr ""
+
+#: ../../configuration.rst:850
+# 6d06725de8a447bd97bcb18b2abffed6
+msgid "Make sure the hypervisor hosts do not have any VMs already running before you add them to CloudStack."
+msgstr ""
+
+#: ../../configuration.rst:853
+# 71a61ae689b14010a3cb30b15dbb6ab4
+msgid "To add a vSphere cluster to CloudStack:"
+msgstr ""
+
+#: ../../configuration.rst:855
+# 4aa19eb63fce44d992c239dc22b644c1
+msgid "Create the cluster of hosts in vCenter. Follow the vCenter instructions to do this. You will create a cluster that looks something like this in vCenter."
+msgstr ""
+
+#: ../../configuration.rst:859
+# f5002325d11f467ebc09a540ab289dc0
+msgid "|vsphereclient.png: vSphere client|"
+msgstr ""
+
+#: ../../configuration.rst:861
+# 2b550bfb1de24c2491dfb5e097ddfc06
+msgid "Log in to the UI."
+msgstr ""
+
+#: ../../configuration.rst:866
+# 2ebc1409a3524a92806ce241e7ade87c
+msgid "Click the Compute tab, and click View All on Pods. Choose the pod to which you want to add the cluster."
+msgstr ""
+
+#: ../../configuration.rst:869
+# 7ea5c0a4d69542b68fdc461c256fc48d
+msgid "Click View Clusters."
+msgstr ""
+
+#: ../../configuration.rst:873
+# 49994ac34ee547f48952a29df8e41fcb
+msgid "In Hypervisor, choose VMware."
+msgstr ""
+
+#: ../../configuration.rst:875
+# eedcbf466c594bd7b3fd86bfe04241b1
+msgid "Provide the following information in the dialog. The fields below make reference to the values from vCenter."
+msgstr ""
+
+#: ../../configuration.rst:878
+# 89c59dc2d27e4303ae86550eed8821f6
+msgid "|addcluster.png: add a cluster|"
+msgstr ""
+
+#: ../../configuration.rst:880
+# 853a36fa7aba43bb89623403046e9971
+msgid "**Cluster Name**: Enter the name of the cluster you created in vCenter. For example, \"cloud.cluster.2.2.1\""
+msgstr ""
+
+#: ../../configuration.rst:883
+# 80bdf696d0944d3b82144716a5c808b5
+msgid "**vCenter Username**: Enter the username that CloudStack should use to connect to vCenter. This user must have all the administrative privileges."
+msgstr ""
+
+#: ../../configuration.rst:887
+# bea1b4e2088642d5b0b8aac382efa2dd
+msgid "**CPU overcommit ratio**: Enter the CPU overcommit ratio for the cluster. The value you enter determines the CPU consumption of each VM in the selected cluster. By increasing the over-provisioning ratio, more resource capacity will be used. If no value is specified, the value is defaulted to 1, which implies no over-provisioning is done."
+msgstr ""
+
+#: ../../configuration.rst:894
+# 0d13e425b64444619a542ae57d648966
+msgid "**RAM overcommit ratio**: Enter the RAM overcommit ratio for the cluster. The value you enter determines the memory consumption of each VM in the selected cluster. By increasing the over-provisioning ratio, more resource capacity will be used. If no value is specified, the value is defaulted to 1, which implies no over-provisioning is done."
+msgstr ""
+
+#: ../../configuration.rst:901
+# c5e25f8ee3a543a19ffec688a6731589
+msgid "**vCenter Host**: Enter the hostname or IP address of the vCenter server."
+msgstr ""
+
+#: ../../configuration.rst:904
+# 0a0d7a14d3624f1fbfa7507c8e4b35e9
+msgid "**vCenter Password**: Enter the password for the user named above."
+msgstr ""
+
+#: ../../configuration.rst:906
+# 10d54005fb6448748362e84d4f269999
+msgid "**vCenter Datacenter**: Enter the vCenter datacenter that the cluster is in. For example, \"cloud.dc.VM\"."
+msgstr ""
+
+#: ../../configuration.rst:909
+# 286a6873beb04a32af8b8b30acee427c
+msgid "**Override Public Traffic**: Enable this option to override the zone-wide public traffic for the cluster you are creating."
+msgstr ""
+
+#: ../../configuration.rst:912
+# 3a820c902ce946538b1e2514136264dc
+msgid "**Public Traffic vSwitch Type**: This option is displayed only if you enable the Override Public Traffic option. Select a desirable switch. If the vmware.use.dvswitch global parameter is true, the default option will be VMware vNetwork Distributed Virtual Switch."
+msgstr ""
+
+#: ../../configuration.rst:917
+#: ../../configuration.rst:939
+# cee24debf6244e6ab8f2960f82cf02dc
+# 28a4eb955bf748c3a88d2d89ce8c5074
+msgid "If you have enabled Nexus dvSwitch in the environment, the following parameters for dvSwitch configuration are displayed:"
+msgstr ""
+
+#: ../../configuration.rst:920
+#: ../../configuration.rst:942
+# d2da6ea28c614ba38eb47ed7e3077ae0
+# 8e33cb040d534b0fa0d115e687ed7610
+msgid "Nexus dvSwitch IP Address: The IP address of the Nexus VSM appliance."
+msgstr ""
+
+#: ../../configuration.rst:923
+#: ../../configuration.rst:945
+# e80bc1882c6c476fa8900e09c5b863e3
+# df90310163a24464b7c5b02335487fdb
+msgid "Nexus dvSwitch Username: The username required to access the Nexus VSM appliance."
+msgstr ""
+
+#: ../../configuration.rst:926
+#: ../../configuration.rst:948
+# f8aeaf74318541b7b199a22f1215f4db
+# f403066f05f9414a8fef9581e1f63c46
+msgid "Nexus dvSwitch Password: The password associated with the username specified above."
+msgstr ""
+
+#: ../../configuration.rst:929
+# b2c37a024feb4704b1af4daaf9f7d7dc
+msgid "**Override Guest Traffic**: Enable this option to override the zone-wide guest traffic for the cluster you are creating."
+msgstr ""
+
+#: ../../configuration.rst:932
+# 94030e337615408390ee4c90fa68dc1f
+msgid "**Guest Traffic vSwitch Type**: This option is displayed only if you enable the Override Guest Traffic option. Select a desirable switch."
+msgstr ""
+
+#: ../../configuration.rst:936
+# 079f9e30e5664e1a85085b94865eb456
+msgid "If the vmware.use.dvswitch global parameter is true, the default option will be VMware vNetwork Distributed Virtual Switch."
+msgstr ""
+
+#: ../../configuration.rst:951
+# baa8eb555037420bb51856abdd7fe8f2
+msgid "There might be a slight delay while the cluster is provisioned. It will automatically display in the UI."
+msgstr ""
+
+#: ../../configuration.rst:958
+# e1f90b62159d4513baedd2e01440755a
+msgid "Adding a Host"
+msgstr ""
+
+#: ../../configuration.rst:960
+# 0923b6cb19c147c7b758d17ba052cb1f
+msgid "Before adding a host to the CloudStack configuration, you must first install your chosen hypervisor on the host. CloudStack can manage hosts running VMs under a variety of hypervisors."
+msgstr ""
+
+#: ../../configuration.rst:964
+# 5bf89c193bf649468f17106c9cc7dc79
+msgid "The CloudStack Installation Guide provides instructions on how to install each supported hypervisor and configure it for use with CloudStack. See the appropriate section in the Installation Guide for information about which version of your chosen hypervisor is supported, as well as crucial additional steps to configure the hypervisor hosts for use with CloudStack."
+msgstr ""
+
+#: ../../configuration.rst:972
+# ff2e79d3bba8422d8b74b3a78eb133a7
+msgid "Be sure you have performed the additional CloudStack-specific configuration steps described in the hypervisor installation section for your particular hypervisor."
+msgstr ""
+
+#: ../../configuration.rst:976
+# ecd653992432482b93207c1b1d4b1503
+msgid "Now add the hypervisor host to CloudStack. The technique to use varies depending on the hypervisor."
+msgstr ""
+
+#: ../../configuration.rst:979
+# 22d66ee649304664855c3570b38b51c3
+msgid ":ref:`adding-a-host-xenserver-kvm`"
+msgstr ""
+
+#: ../../configuration.rst:981
+# 04cf8556d81441d9915194885f3f28c8
+msgid ":ref:`adding-a-host-vsphere`"
+msgstr ""
+
+#: ../../configuration.rst:987
+# 1d939abd524b4701b1f7ba65cfb70da2
+msgid "Adding a Host (XenServer or KVM)"
+msgstr ""
+
+#: ../../configuration.rst:989
+# af116bf381dc4f9ea38ec2f5625bc8a5
+msgid "XenServer and KVM hosts can be added to a cluster at any time."
+msgstr ""
+
+#: ../../configuration.rst:993
+# e59027be4a9846a9845b33dd15d6649a
+msgid "Requirements for XenServer and KVM Hosts"
+msgstr ""
+
+#: ../../configuration.rst:996
+# e6025f03b3ce477c9d135377a7894528
+msgid "Make sure the hypervisor host does not have any VMs already running before you add it to CloudStack."
+msgstr ""
+
+#: ../../configuration.rst:999
+# a7d22455a14846d98f150dbeeae218f0
+msgid "Configuration requirements:"
+msgstr ""
+
+#: ../../configuration.rst:1001
+# e5160a3fa2ec40919c557a6935f3fe1f
+msgid "Each cluster must contain only hosts with the identical hypervisor."
+msgstr ""
+
+#: ../../configuration.rst:1003
+# cdfb38a316e3459e9e52ea228402b66c
+msgid "For XenServer, do not put more than 8 hosts in a cluster."
+msgstr ""
+
+#: ../../configuration.rst:1005
+# b4a9938b72044be7bd458f16ed719e81
+msgid "For KVM, do not put more than 16 hosts in a cluster."
+msgstr ""
+
+#: ../../configuration.rst:1007
+# 2f1baf980a734a43baf993d791d4d8c5
+msgid "For hardware requirements, see the installation section for your hypervisor in the CloudStack Installation Guide."
+msgstr ""
+
+#: ../../configuration.rst:1012
+# 5b7b02ee375a45adaad6da800cd483c3
+msgid "XenServer Host Additional Requirements"
+msgstr ""
+
+#: ../../configuration.rst:1014
+# 27ea0fe70f034e44a3904e6c7ca6afa4
+msgid "If network bonding is in use, the administrator must cable the new host identically to other hosts in the cluster."
+msgstr ""
+
+#: ../../configuration.rst:1017
+# 05d3932560e04019b3bdb344f870f538
+msgid "For all additional hosts to be added to the cluster, run the following command. This will cause the host to join the master in a XenServer pool."
+msgstr ""
+
+#: ../../configuration.rst:1026
+# 286ea98fd2d747c483da6d96983d5c9f
+msgid "When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text."
+msgstr ""
+
+#: ../../configuration.rst:1030
+# 354fed2a8e2a4333a32b9a35786ca935
+msgid "With all hosts added to the XenServer pool, run the cloud-setup-bond script. This script will complete the configuration and setup of the bonds on the new hosts in the cluster."
+msgstr ""
+
+#: ../../configuration.rst:1034
+# c4cd2afe3b934ce8b2621d0b9e82c2d2
+msgid "Copy the script from the Management Server in /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh to the master host and ensure it is executable."
+msgstr ""
+
+#: ../../configuration.rst:1038
+# 0e532bee249b496b88f2c7475bdf97f8
+msgid "Run the script:"
+msgstr ""
+
+#: ../../configuration.rst:1046
+# e7009690c4b6478ba5f35649f9e09436
+msgid "KVM Host Additional Requirements"
+msgstr ""
+
+#: ../../configuration.rst:1048
+# 37a3fd672bc54d768a466c6ba3dae54f
+msgid "If shared mountpoint storage is in use, the administrator should ensure that the new host has all the same mountpoints (with storage mounted) as the other hosts in the cluster."
+msgstr ""
+
+#: ../../configuration.rst:1052
+# 710951bf6c5a4eed831cc19f7be18c01
+msgid "Make sure the new host has the same network configuration (guest, private, and public network) as other hosts in the cluster."
+msgstr ""
+
+#: ../../configuration.rst:1055
+# 7a50d92cb76b43c68381d14e04aed486
+msgid "If you are using OpenVswitch bridges edit the file agent.properties on the KVM host and set the parameter network.bridge.type to openvswitch before adding the host to CloudStack"
+msgstr ""
+
+#: ../../configuration.rst:1061
+# 332d12a13d1f4216b74187cf129bc664
+msgid "Adding a XenServer or KVM Host"
+msgstr ""
+
+#: ../../configuration.rst:1063
+# cfba9ce6e7f14afebd66671f11feaacf
+msgid "If you have not already done so, install the hypervisor software on the host. You will need to know which version of the hypervisor software version is supported by CloudStack and what additional configuration is required to ensure the host will work with CloudStack. To find these installation details, see the appropriate section for your hypervisor in the CloudStack Installation Guide."
+msgstr ""
+
+#: ../../configuration.rst:1070
+# 377e41a476e54f4c82f0d00d304e2693
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../configuration.rst:1072
+# 7ac765edde2443be9069abb07cd4d0db
+msgid "In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the host."
+msgstr ""
+
+#: ../../configuration.rst:1075
+# a4431e8197e24d1f8565b3bb92bca888
+msgid "Click the Compute tab. In the Clusters node, click View All."
+msgstr ""
+
+#: ../../configuration.rst:1077
+# 362b6eed173f4b5f8f7b38ebe0958336
+msgid "Click the cluster where you want to add the host."
+msgstr ""
+
+#: ../../configuration.rst:1079
+# effdebcf4be849f2962ad4550751244d
+msgid "Click View Hosts."
+msgstr ""
+
+#: ../../configuration.rst:1081
+# 4c39fa71f4fc425abb83949d1b5ed506
+msgid "Click Add Host."
+msgstr ""
+
+#: ../../configuration.rst:1083
+# 5ffcb71d5a1b46ebabc4fcf190e75753
+msgid "Provide the following information."
+msgstr ""
+
+#: ../../configuration.rst:1085
+# 88888fd494694d8d8075b9131573228f
+msgid "Host Name. The DNS name or IP address of the host."
+msgstr ""
+
+#: ../../configuration.rst:1087
+# c26fe06e5a564c628de75c1d4fe93d68
+msgid "Username. Usually root."
+msgstr ""
+
+#: ../../configuration.rst:1089
+# 2b09fc60175b45d5b24a1c0574fc275f
+msgid "Password. This is the password for the user from your XenServer or KVM install)."
+msgstr ""
+
+#: ../../configuration.rst:1092
+# 6b228c164605432b8fbf4c3345a73413
+msgid "Host Tags (Optional). Any labels that you use to categorize hosts for ease of maintenance. For example, you can set to the cloud's HA tag (set in the ha.tag global configuration parameter) if you want this host to be used only for VMs with the \"high availability\" feature enabled. For more information, see HA-Enabled Virtual Machines as well as HA for Hosts."
+msgstr ""
+
+#: ../../configuration.rst:1099
+# 9be1b413f34f45e2871035d35715659a
+msgid "There may be a slight delay while the host is provisioned. It should automatically display in the UI."
+msgstr ""
+
+#: ../../configuration.rst:1102
+# cdc3acb163fc410bbca13f2bd37b0775
+msgid "Repeat for additional hosts."
+msgstr ""
+
+#: ../../configuration.rst:1108
+# fb2b5c33309149d1b6b0d0ac9e73c5fb
+msgid "Adding a Host (vSphere)"
+msgstr ""
+
+#: ../../configuration.rst:1110
+# be6b7ef5fe374f84ac9e6e487404ab78
+msgid "For vSphere servers, we recommend creating the cluster of hosts in vCenter and then adding the entire cluster to CloudStack. See Add Cluster: vSphere."
+msgstr ""
+
+#: ../../configuration.rst:1118
+# 99be6cf56ded43aba5cd4d8e19f0ace3
+msgid "Add Primary Storage"
+msgstr ""
+
+#: ../../configuration.rst:1121
+# 22065a62af1642d3bc3ea2ed32396bac
+msgid "System Requirements for Primary Storage"
+msgstr ""
+
+#: ../../configuration.rst:1123
+# 936b5d62d1b14484a4b62a45ed972c59
+msgid "Hardware requirements:"
+msgstr ""
+
+#: ../../configuration.rst:1125
+# f209dd840aec4701bdad045e39dc292e
+msgid "Any standards-compliant iSCSI, SMB, or NFS server that is supported by the underlying hypervisor."
+msgstr ""
+
+#: ../../configuration.rst:1128
+# e3547549b19e48af957483aebd01db56
+msgid "The storage server should be a machine with a large number of disks. The disks should ideally be managed by a hardware RAID controller."
+msgstr ""
+
+#: ../../configuration.rst:1131
+# c31ea6b6b7bc46d98ae721c07b56b50e
+msgid "Minimum required capacity depends on your needs."
+msgstr ""
+
+#: ../../configuration.rst:1133
+# cdb1be7fc7ea4f5b973a9b1c27463a6d
+msgid "When setting up primary storage, follow these restrictions:"
+msgstr ""
+
+#: ../../configuration.rst:1135
+# 42e4d357c3b747ec85130e77229e624a
+msgid "Primary storage cannot be added until a host has been added to the cluster."
+msgstr ""
+
+#: ../../configuration.rst:1138
+# fc583ad97a214096a21288c09b52d080
+msgid "If you do not provision shared primary storage, you must set the global configuration parameter system.vm.local.storage.required to true, or else you will not be able to start VMs."
+msgstr ""
+
+#: ../../configuration.rst:1144
+# 3533708ed0ae435cb0a572d791d9715e
+msgid "Adding Primary Storage"
+msgstr ""
+
+#: ../../configuration.rst:1146
+# 0fae53d8c0214c6bb4e92841b8ee4a48
+msgid "When you create a new zone, the first primary storage is added as part of that procedure. You can add primary storage servers at any time, such as when adding a new cluster or adding more servers to an existing cluster."
+msgstr ""
+
+#: ../../configuration.rst:1152
+# e015632ceea7426b8ca21a4fc905bb1e
+msgid "When using preallocated storage for primary storage, be sure there is nothing on the storage (ex. you have an empty SAN volume or an empty NFS share). Adding the storage to CloudStack will destroy any existing data."
+msgstr ""
+
+#: ../../configuration.rst:1156
+# 2a0ed458d44e4e95ab93c42eb3a9e935
+msgid "Log in to the CloudStack UI (see `“Log In to the UI” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_)."
+msgstr ""
+
+#: ../../configuration.rst:1158
+# d5b688c69e784146b9ac0e214c8fe44c
+msgid "In the left navigation, choose Infrastructure. In Zones, click View More, then click the zone in which you want to add the primary storage."
+msgstr ""
+
+#: ../../configuration.rst:1164
+# 1cddd71de6ba4353ab0be25462528358
+msgid "In the Primary Storage node of the diagram, click View All."
+msgstr ""
+
+#: ../../configuration.rst:1166
+# d541d83b2a194e519a9ec5df1d98f5b4
+msgid "Click Add Primary Storage."
+msgstr ""
+
+#: ../../configuration.rst:1168
+# 5c4a040452d54b77942c8ddae2c6210f
+msgid "Provide the following information in the dialog. The information required varies depending on your choice in Protocol."
+msgstr ""
+
+#: ../../configuration.rst:1171
+# a693b4b9924b4fa096e546299abb3d47
+msgid "**Scope.** Indicate whether the storage is available to all hosts in the zone or only to hosts in a single cluster."
+msgstr ""
+
+#: ../../configuration.rst:1174
+# a142f32de5b64983965c23101102bdfc
+msgid "**Pod.** (Visible only if you choose Cluster in the Scope field.) The pod for the storage device."
+msgstr ""
+
+#: ../../configuration.rst:1177
+# fc4673c08bee49338a23afc73b035a4f
+msgid "**Cluster.** (Visible only if you choose Cluster in the Scope field.) The cluster for the storage device."
+msgstr ""
+
+#: ../../configuration.rst:1182
+# dd1e29093388466db29061c47fcc2a91
+msgid "**Protocol.** For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM, choose NFS or SharedMountPoint. For vSphere choose either VMFS (iSCSI or FiberChannel) or NFS. For Hyper-V, choose SMB."
+msgstr ""
+
+#: ../../configuration.rst:1187
+# 5b60e8a893084a1abc56eeaee597e47b
+msgid "**Server (for NFS, iSCSI, or PreSetup).** The IP address or DNS name of the storage device."
+msgstr ""
+
+#: ../../configuration.rst:1190
+# b65c77d90f5f418e847f3a93e35cb8f9
+msgid "**Server (for VMFS).** The IP address or DNS name of the vCenter server."
+msgstr ""
+
+#: ../../configuration.rst:1193
+# 363c9c97e53944328628fd2634c615d4
+msgid "**Path (for NFS).** In NFS this is the exported path from the server."
+msgstr ""
+
+#: ../../configuration.rst:1196
+# 56943b019adc4b9f8a0ed93f8cdf51b4
+msgid "**Path (for VMFS).** In vSphere this is a combination of the datacenter name and the datastore name. The format is \"/\" datacenter name \"/\" datastore name. For example, \"/cloud.dc.VM/cluster1datastore\"."
+msgstr ""
+
+#: ../../configuration.rst:1201
+# 2414d9e1191e42bd8fb5c9fdf39bbbd8
+msgid "**Path (for SharedMountPoint).** With KVM this is the path on each host that is where this primary storage is mounted. For example, \"/mnt/primary\"."
+msgstr ""
+
+#: ../../configuration.rst:1205
+# 2517e36ce3a1410ab5c1978f5ac89313
+msgid "**SMB Username** (for SMB/CIFS): Applicable only if you select SMB/CIFS provider. The username of the account which has the necessary permissions to the SMB shares. The user must be part of the Hyper-V administrator group."
+msgstr ""
+
+#: ../../configuration.rst:1210
+# 58a4a5cad3794a3bac1f01f92fd63e80
+msgid "**SMB Password** (for SMB/CIFS): Applicable only if you select SMB/CIFS provider. The password associated with the account."
+msgstr ""
+
+#: ../../configuration.rst:1213
+# 497f1a89318e48a9ad2c06c57111cd9f
+msgid "**SMB Domain**\\ (for SMB/CIFS): Applicable only if you select SMB/CIFS provider. The Active Directory domain that the SMB share is a part of."
+msgstr ""
+
+#: ../../configuration.rst:1217
+# 2cdf053d64574ee1a6b5879f0ef2807d
+msgid "**SR Name-Label (for PreSetup).** Enter the name-label of the SR that has been set up outside CloudStack."
+msgstr ""
+
+#: ../../configuration.rst:1220
+# dd903e9085d84fd8afb2fce49b2357f6
+msgid "**Target IQN (for iSCSI).** In iSCSI this is the IQN of the target. For example, iqn.1986-03.com.sun:02:01ec9bb549-1271378984."
+msgstr ""
+
+#: ../../configuration.rst:1223
+# dd7a4bfc0eea4a3dab03d2bafa973633
+msgid "**Lun # (for iSCSI).** In iSCSI this is the LUN number. For example, 3."
+msgstr ""
+
+#: ../../configuration.rst:1226
+# 9023364ebc994f959f08b6819c1c4ce6
+msgid "**Tags (optional).** The comma-separated list of tags for this storage device. It should be an equivalent set or superset of the tags on your disk offerings.."
+msgstr ""
+
+#: ../../configuration.rst:1239
+# 824ace5e85574e4fb81a6c834d657113
+msgid "Configuring a Storage Plug-in"
+msgstr ""
+
+#: ../../configuration.rst:1242
+# 0bf9f4ce03274fa99551db2eef02d467
+msgid "Primary storage that is based on a custom plug-in (ex. SolidFire) must be added through the CloudStack API (described later in this section). There is no support at this time through the CloudStack UI to add this type of primary storage (although most of its features are available through the CloudStack UI)."
+msgstr ""
+
+#: ../../configuration.rst:1249
+# a1da9fd485b44080b384938a6f55a7bd
+msgid "The SolidFire storage plug-in for CloudStack is part of the standard CloudStack install. There is no additional work required to add this component."
+msgstr ""
+
+#: ../../configuration.rst:1253
+# 891dd35a6f6b4cf184d16023fd87a83b
+msgid "Adding primary storage that is based on the SolidFire plug-in enables CloudStack to provide hard quality-of-service (QoS) guarantees."
+msgstr ""
+
+#: ../../configuration.rst:1256
+# 0218d86dac264ce88dc1b3293defc50a
+msgid "When used with Compute or Disk Offerings, an administrator is able to build an environment in which a root or data disk that a user creates leads to the dynamic creation of a SolidFire volume, which has guaranteed performance. Such a SolidFire volume is associated with one (and only ever one) CloudStack volume, so performance of the CloudStack volume does not vary depending on how heavily other tenants are using the system."
+msgstr ""
+
+#: ../../configuration.rst:1264
+# febca3ed36dc41f0bfe48a3170c1b282
+msgid "The createStoragePool API has been augmented to support plugable storage providers. The following is a list of parameters to use when adding storage to CloudStack that is based on the SolidFire plug-in:"
+msgstr ""
+
+#: ../../configuration.rst:1268
+# 8b10cd104059470bbfbdf014d3db7d1a
+msgid "command=createStoragePool"
+msgstr ""
+
+#: ../../configuration.rst:1270
+# b7c687d8637946898d1be0a46f742a61
+msgid "scope=zone"
+msgstr ""
+
+#: ../../configuration.rst:1272
+# 051d3b0d6e7440218edb1ce012c5ba48
+msgid "zoneId=[your zone id]"
+msgstr ""
+
+#: ../../configuration.rst:1274
+# 43e497e6ee76487cb7ef8d43079af1da
+msgid "name=[name for primary storage]"
+msgstr ""
+
+#: ../../configuration.rst:1276
+# 041976b0584443e5852b0af71eefdb18
+msgid "hypervisor=Any"
+msgstr ""
+
+#: ../../configuration.rst:1278
+# 62f2f914fb8544d5b835ee85bff60f35
+msgid "provider=SolidFire"
+msgstr ""
+
+#: ../../configuration.rst:1280
+# fcf5466edf494d04957dec9bdfa80299
+msgid "capacityIops=[whole number of IOPS from the SAN to give to CloudStack]"
+msgstr ""
+
+#: ../../configuration.rst:1283
+# 7c4387f9055e4517907fb3bce403cfd0
+msgid "capacityBytes=[whole number of bytes from the SAN to give to CloudStack]"
+msgstr ""
+
+#: ../../configuration.rst:1286
+# be0d75f4832646b88d313275708519bf
+msgid "The url parameter is somewhat unique in that its value can contain additional key/value pairs."
+msgstr ""
+
+#: ../../configuration.rst:1289
+# ac8214aa1a4146599e36ab6ab7c8d513
+msgid "url=[key/value pairs detailed below (values are URL encoded; for example, '=' is represented as '%3D')]"
+msgstr ""
+
+#: ../../configuration.rst:1292
+# c35760dbaf9c43e9a3fcba4f07941070
+msgid "MVIP%3D[Management Virtual IP Address] (can be suffixed with :[port number])"
+msgstr ""
+
+#: ../../configuration.rst:1295
+# eec7163645c94befa2b06ef23adf72d1
+msgid "SVIP%3D[Storage Virtual IP Address] (can be suffixed with :[port number])"
+msgstr ""
+
+#: ../../configuration.rst:1298
+# 69688776153943ed92994665eb48f4fb
+msgid "clusterAdminUsername%3D[cluster admin's username]"
+msgstr ""
+
+#: ../../configuration.rst:1300
+# 660c410694f04bb6a9e49b2f10fb19a5
+msgid "clusterAdminPassword%3D[cluster admin's password]"
+msgstr ""
+
+#: ../../configuration.rst:1302
+# 2f276967210246a7ac29632c437fba98
+msgid "clusterDefaultMinIops%3D[Min IOPS (whole number) to set for a volume; used if Min IOPS is not specified by administrator or user]"
+msgstr ""
+
+#: ../../configuration.rst:1305
+# 503ba3b359a54f4e903c183ec3a434dc
+msgid "clusterDefaultMaxIops%3D[Max IOPS (whole number) to set for a volume; used if Max IOPS is not specified by administrator or user]"
+msgstr ""
+
+#: ../../configuration.rst:1308
+# bff592567afe42e79eab78de3a4527e8
+msgid "clusterDefaultBurstIopsPercentOfMaxIops%3D[Burst IOPS is determined by (Min IOPS \\* clusterDefaultBurstIopsPercentOfMaxIops parameter) (can be a decimal value)]"
+msgstr ""
+
+#: ../../configuration.rst:1316
+# 7f326e7c95a643b5b8f3266987762c9f
+msgid "Add Secondary Storage"
+msgstr ""
+
+#: ../../configuration.rst:1319
+# adab0eb1bee64891b05c676c8825b984
+msgid "System Requirements for Secondary Storage"
+msgstr ""
+
+#: ../../configuration.rst:1321
+# 968a6fc6d0b648b9ad73e20f83ba3013
+msgid "NFS storage appliance or Linux NFS server"
+msgstr ""
+
+#: ../../configuration.rst:1323
+# e9b6a1101247444e8248486d4e144757
+msgid "SMB/CIFS (Hyper-V)"
+msgstr ""
+
+#: ../../configuration.rst:1325
+# 31aa6daa1e434c0db6e1ea96877e6fc9
+msgid "(Optional) OpenStack Object Storage (Swift) (see http://swift.openstack.org)"
+msgstr ""
+
+#: ../../configuration.rst:1328
+# 93eb696e8c9a4372a49348a82bba481e
+msgid "100GB minimum capacity"
+msgstr ""
+
+#: ../../configuration.rst:1330
+# 5d6728fa692e41a186cc029252118288
+msgid "A secondary storage device must be located in the same zone as the guest VMs it serves."
+msgstr ""
+
+#: ../../configuration.rst:1333
+# 9e55bb037b5d4b35b720ef57d16556a8
+msgid "Each Secondary Storage server must be available to all hosts in the zone."
+msgstr ""
+
+#: ../../configuration.rst:1338
+# e0c736eae790448ba73388e3c5b2d47f
+msgid "Adding Secondary Storage"
+msgstr ""
+
+#: ../../configuration.rst:1340
+# 6791f9d69f3f4cee83ddb30891d2e653
+msgid "When you create a new zone, the first secondary storage is added as part of that procedure. You can add secondary storage servers at any time to add more servers to an existing zone."
+msgstr ""
+
+#: ../../configuration.rst:1345
+# 4de26231899b4a91a5b618eaf80f76ba
+msgid "Ensure that nothing is stored on the server. Adding the server to CloudStack will destroy any existing data."
+msgstr ""
+
+#: ../../configuration.rst:1348
+# 0f96c75bcfaa4992b32facf1bf9c77ed
+msgid "To prepare for the zone-based Secondary Staging Store, you should have created and mounted an NFS share during Management Server installation. See `“Prepare NFS Shares” <installation.html#prepare-nfs-shares>`_."
+msgstr ""
+
+#: ../../configuration.rst:1353
+# 8b7e2a3c48fc4c57a7d8c5571f9338a3
+msgid "If you are using an Hyper-V host, ensure that you have created a SMB share."
+msgstr ""
+
+#: ../../configuration.rst:1356
+# 48e97ef4b1a54f518c793652ddec6ef8
+msgid "Make sure you prepared the system VM template during Management Server installation. See `“Prepare the System VM Template” <installation.html#prepare-the-system-vm-template>`_."
+msgstr ""
+
+#: ../../configuration.rst:1360
+#: ../../configuration.rst:1418
+# fb775865c0094c848195fc8e5e81dfe0
+# e77ca2fba1984e23a35ca22a521e66f7
+msgid "Log in to the CloudStack UI as root administrator."
+msgstr ""
+
+#: ../../configuration.rst:1362
+#: ../../configuration.rst:1420
+# bf288714744446b487c5d03e8d5c284f
+# 54721a0f604d4c89b7b287778eac8b4a
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../configuration.rst:1364
+#: ../../configuration.rst:1422
+# 802486b1694646e592a9dc6a6e069a21
+# dd93f372389045b9ade68ce6bf035f54
+msgid "In Secondary Storage, click View All."
+msgstr ""
+
+#: ../../configuration.rst:1366
+# 5e56801815014372ae7b840a6124f920
+msgid "Click Add Secondary Storage."
+msgstr ""
+
+#: ../../configuration.rst:1368
+# 5b0960edebc74650950d33271c9f6db6
+msgid "Fill in the following fields:"
+msgstr ""
+
+#: ../../configuration.rst:1370
+# 8bb375e8f43347d8844effcc6cf2a994
+msgid "Name. Give the storage a descriptive name."
+msgstr ""
+
+#: ../../configuration.rst:1372
+# d672a62914804d9e85d1c3055b9bcddf
+msgid "Provider. Choose S3, Swift, NFS, or CIFS then fill in the related fields which appear. The fields will vary depending on the storage provider; for more information, consult the provider's documentation (such as the S3 or Swift website). NFS can be used for zone-based storage, and the others for region-wide storage. For Hyper-V, select SMB/CIFS."
+msgstr ""
+
+#: ../../configuration.rst:1380
+# 085cebda2756421d88eabe0fd1ed189e
+msgid "Heterogeneous Secondary Storage is not supported in Regions. You can use only a single NFS, S3, or Swift account per region."
+msgstr ""
+
+#: ../../configuration.rst:1383
+# 4c63cfbb89234aa9994880b6d7035475
+msgid "Create NFS Secondary Staging Store. This box must always be checked."
+msgstr ""
+
+#: ../../configuration.rst:1387
+# 82935d6da92341a5bc95411b32007c5c
+msgid "Even if the UI allows you to uncheck this box, do not do so. This checkbox and the three fields below it must be filled in. Even when Swift or S3 is used as the secondary storage provider, an NFS staging storage in each zone is still required."
+msgstr ""
+
+#: ../../configuration.rst:1392
+#: ../../configuration.rst:1430
+# 5c87b1fdcb6c46648fb4bfad3fc595e6
+# 96945a3298924faea7c59f3ddc805b91
+msgid "Zone. The zone where the NFS Secondary Staging Store is to be located."
+msgstr ""
+
+#: ../../configuration.rst:1395
+# 3d532bad74854b83840c13235fc5eaf3
+msgid "**SMB Username**: Applicable only if you select SMB/CIFS provider. The username of the account which has the necessary permissions to the SMB shares. The user must be part of the Hyper-V administrator group."
+msgstr ""
+
+#: ../../configuration.rst:1400
+# d11b35aafdad49d09e6595709ab4a869
+msgid "**SMB Password**: Applicable only if you select SMB/CIFS provider. The password associated with the account."
+msgstr ""
+
+#: ../../configuration.rst:1403
+# 0cc268fbd62a46339fc88eceb8dadb38
+msgid "**SMB Domain**: Applicable only if you select SMB/CIFS provider. The Active Directory domain that the SMB share is a part of."
+msgstr ""
+
+#: ../../configuration.rst:1406
+#: ../../configuration.rst:1433
+# b3462457dd174443aa00bc93eaebe853
+# 470e248f89d14eeb8eb098c79f29f52c
+msgid "NFS server. The name of the zone's Secondary Staging Store."
+msgstr ""
+
+#: ../../configuration.rst:1408
+#: ../../configuration.rst:1435
+# adf27bcea0504f11988812eb85a20283
+# 29251115675e4ebd9e95bb8e2be474ec
+msgid "Path. The path to the zone's Secondary Staging Store."
+msgstr ""
+
+#: ../../configuration.rst:1412
+# f1a67ebb7bfc4b9bba233d814a3633e7
+msgid "Adding an NFS Secondary Staging Store for Each Zone"
+msgstr ""
+
+#: ../../configuration.rst:1414
+# 592852d3ff9741b592dfb8c0155bea22
+msgid "Every zone must have at least one NFS store provisioned; multiple NFS servers are allowed per zone. To provision an NFS Staging Store for a zone:"
+msgstr ""
+
+#: ../../configuration.rst:1424
+# 78eec05d08f24414bcb7cd50390349f9
+msgid "In Select View, choose Secondary Staging Store."
+msgstr ""
+
+#: ../../configuration.rst:1426
+# 58099b56975e4d6595fd3021bdba2d25
+msgid "Click the Add NFS Secondary Staging Store button."
+msgstr ""
+
+#: ../../configuration.rst:1428
+# 8d5db72403274211adc4e4ca5885cd63
+msgid "Fill out the dialog box fields, then click OK:"
+msgstr ""
+
+#: ../../configuration.rst:1441
+# b36dbe0441734c5d88e226b8cb6d73ca
+msgid "Initialize and Test"
+msgstr ""
+
+#: ../../configuration.rst:1443
+# f68866b9b3734b33aff7025c4fc36a2b
+msgid "After everything is configured, CloudStack will perform its initialization. This can take 30 minutes or more, depending on the speed of your network. When the initialization has completed successfully, the administrator's Dashboard should be displayed in the CloudStack UI."
+msgstr ""
+
+#: ../../configuration.rst:1448
+# e9f3a393a1774f74b5055f413c96a747
+msgid "Verify that the system is ready. In the left navigation bar, select Templates. Click on the CentOS 5.5 (64bit) no Gui (KVM) template. Check to be sure that the status is \"Download Complete.\" Do not proceed to the next step until this status is displayed."
+msgstr ""
+
+#: ../../configuration.rst:1453
+# 9765684b94244895a421d49deaf567ba
+msgid "Go to the Instances tab, and filter by My Instances."
+msgstr ""
+
+#: ../../configuration.rst:1455
+# 2880f3b150d14b459c557af5ec08546d
+msgid "Click Add Instance and follow the steps in the wizard."
+msgstr ""
+
+#: ../../configuration.rst:1457
+# 2afad971b41d4de4a246ba67d4ae812b
+msgid "Choose the zone you just added."
+msgstr ""
+
+#: ../../configuration.rst:1459
+# 0fc7a9665e7e4723a768ff8dc31cced5
+msgid "In the template selection, choose the template to use in the VM. If this is a fresh installation, likely only the provided CentOS template is available."
+msgstr ""
+
+#: ../../configuration.rst:1463
+# 888d93deca4d435aa3abbc602cd21a5f
+msgid "Select a service offering. Be sure that the hardware you have allows starting the selected service offering."
+msgstr ""
+
+#: ../../configuration.rst:1466
+# c9f44c62d2c042eabda1609a020f52c0
+msgid "In data disk offering, if desired, add another data disk. This is a second volume that will be available to but not mounted in the guest. For example, in Linux on XenServer you will see /dev/xvdb in the guest after rebooting the VM. A reboot is not required if you have a PV-enabled OS kernel in use."
+msgstr ""
+
+#: ../../configuration.rst:1472
+# 1d8ed73580834715bab5475f01fde220
+msgid "In default network, choose the primary network for the guest. In a trial installation, you would have only one option here."
+msgstr ""
+
+#: ../../configuration.rst:1475
+# 7381b9b824f64589ac04f8704896713f
+msgid "Optionally give your VM a name and a group. Use any descriptive text you would like."
+msgstr ""
+
+#: ../../configuration.rst:1478
+# 25155fbd928c415db082ad68cac73582
+msgid "Click Launch VM. Your VM will be created and started. It might take some time to download the template and complete the VM startup. You can watch the VM’s progress in the Instances screen."
+msgstr ""
+
+#: ../../configuration.rst:1483
+# 33d66d1adbea4bb7a5979aac637d27bc
+msgid "To use the VM, click the View Console button. |ConsoleButton.png: button to launch a console|"
+msgstr ""
+
+#: ../../configuration.rst:1486
+# 6b8361d98cfe4efba50da0878b03cbbc
+msgid "For more information about using VMs, including instructions for how to allow incoming network traffic to the VM, start, stop, and delete VMs, and move a VM from one host to another, see Working With Virtual Machines in the Administrator’s Guide."
+msgstr ""
+
+#: ../../configuration.rst:1491
+# 4bbb4febddf9404f9f1bb947098bd130
+msgid "Congratulations! You have successfully completed a CloudStack Installation."
+msgstr ""
+
+#: ../../configuration.rst:1494
+# f80667053e0249a3abd24b4f2b6db3ed
+msgid "If you decide to grow your deployment, you can add more hosts, primary storage, zones, pods, and clusters."
+msgstr ""
+
+#: ../../configuration.rst:1499
+# c560c1abbc0943729e4be7ed366f3f45
+msgid "Configuration Parameters"
+msgstr ""
+
+#: ../../configuration.rst:1502
+# 2a5e0238a6744532890adbf1f51cbfc2
+msgid "About Configuration Parameters"
+msgstr ""
+
+#: ../../configuration.rst:1504
+# 003cadc1a22543e181b420d3216ee3ca
+msgid "CloudStack provides a variety of settings you can use to set limits, configure features, and enable or disable features in the cloud. Once your Management Server is running, you might need to set some of these configuration parameters, depending on what optional features you are setting up. You can set default values at the global level, which will be in effect throughout the cloud unless you override them at a lower level. You can make local settings, which will override the global configuration parameter values, at the level of an account, zone, cluster, or primary storage."
+msgstr ""
+
+#: ../../configuration.rst:1514
+# e6d2272ffdc04a15b3b2e5a0b39a5a6e
+msgid "The documentation for each CloudStack feature should direct you to the names of the applicable parameters. The following table shows a few of the more useful parameters."
+msgstr ""
+
+#: ../../configuration.rst:1519
+#: ../../configuration.rst:1593
+#: ../../configuration.rst:1593
+# 48a9586522fe49a684a986663433d564
+# 92079ae000394a18a79504e41961233c
+# 43f27ae0b01e46e98172965dd387907d
+msgid "Field"
+msgstr ""
+
+#: ../../configuration.rst:1519
+#: ../../configuration.rst:1593
+# 2a703e9880154ddf91d1a384bfe8d684
+# 4dd2b3b2879b471388bcb2004313500a
+msgid "Value"
+msgstr ""
+
+#: ../../configuration.rst:1521
+# a510f43a421343dea533527f4084051d
+msgid "management.network.cidr"
+msgstr ""
+
+#: ../../configuration.rst:1521
+# dccbf6a2a6274bd1befec5e03859ae5d
+msgid "A CIDR that describes the network that the management CIDRs reside on. This variable must be set for deployments that use vSphere. It is recommended to be set for other deployments as well. Example: 192.168.3.0/24."
+msgstr ""
+
+#: ../../configuration.rst:1522
+# b5e4676da208492e872933356f38f626
+msgid "xen.setup.multipath"
+msgstr ""
+
+#: ../../configuration.rst:1522
+# cb8c5e8921894a34868af73e9e9b8a6f
+msgid "For XenServer nodes, this is a true/false variable that instructs CloudStack to enable iSCSI multipath on the XenServer Hosts when they are added. This defaults to false. Set it to true if you would like CloudStack to enable multipath.If this is true for a NFS-based deployment multipath will still be enabled on the XenServer host. However, this does not impact NFS operation and is harmless."
+msgstr ""
+
+#: ../../configuration.rst:1523
+# df8f08a8bb804a5fb28c80c3fa316708
+msgid "secstorage.allowed.internal.sites"
+msgstr ""
+
+#: ../../configuration.rst:1523
+# b415c6a677b249d9ba32483249809b8a
+msgid "This is used to protect your internal network from rogue attempts to download arbitrary files using the template download feature. This is a comma-separated list of CIDRs. If a requested URL matches any of these CIDRs the Secondary Storage VM will use the private network interface to fetch the URL. Other URLs will go through the public interface. We suggest you set this to 1 or 2 hardened internal machines where you keep your templates. For example, set it to 192.168.1.66/32."
+msgstr ""
+
+#: ../../configuration.rst:1524
+# bca7b73b39f34d68bfc7b3a8b02028c9
+msgid "use.local.storage"
+msgstr ""
+
+#: ../../configuration.rst:1524
+# c403da3bca8c422cb0030472d7fdd0dd
+msgid "Determines whether CloudStack will use storage that is local to the Host for data disks, templates, and snapshots. By default CloudStack will not use this storage. You should change this to true if you want to use local storage and you understand the reliability and feature drawbacks to choosing local storage."
+msgstr ""
+
+#: ../../configuration.rst:1525
+# 273f3dc9d0b24674a052d86df2f932f7
+msgid "host"
+msgstr ""
+
+#: ../../configuration.rst:1525
+# 47bba12b42d54d46be9901d1f8cf8ca5
+msgid "This is the IP address of the Management Server. If you are using multiple Management Servers you should enter a load balanced IP address that is reachable via the private network."
+msgstr ""
+
+#: ../../configuration.rst:1526
+# d310c3c87f234eceb4271591bd4d899f
+msgid "default.page.size"
+msgstr ""
+
+#: ../../configuration.rst:1526
+# 3a7b21e756ed4f3284a2a188ca0a0ec1
+msgid "Maximum number of items per page that can be returned by a CloudStack API command. The limit applies at the cloud level and can vary from cloud to cloud. You can override this with a lower value on a particular API call by using the page and pagesize API command parameters. For more information, see the Developer's Guide. Default: 500."
+msgstr ""
+
+#: ../../configuration.rst:1527
+# 8d6b4fb28115479a9cb70f843801f6aa
+msgid "ha.tag"
+msgstr ""
+
+#: ../../configuration.rst:1527
+# cb3deb2df4004607a2e04b50afda2e63
+msgid "The label you want to use throughout the cloud to designate certain hosts as dedicated HA hosts. These hosts will be used only for HA-enabled VMs that are restarting due to the failure of another host. For example, you could set this to ha\\_host. Specify the ha.tag value asa host tag when you add a new host to the cloud."
+msgstr ""
+
+#: ../../configuration.rst:1528
+# 556fde03303d42ffb220b102b2210dfc
+msgid "vmware.vcenter.session.timeout"
+msgstr ""
+
+#: ../../configuration.rst:1528
+# cf142a0831c24cd29e0879d24191c09a
+msgid "Determines the vCenter session timeout value by using this parameter. The default value is 20 minutes. Increase the timeout value to avoid timeout errors in VMware deployments because certain VMware operations take more than 20 minutes."
+msgstr ""
+
+#: ../../configuration.rst:1533
+# 08eca151e89148068e96234ee8efccac
+msgid "Setting Global Configuration Parameters"
+msgstr ""
+
+#: ../../configuration.rst:1535
+# 2a6efc4eeb824e30b5d0a10540c63b55
+msgid "Use the following steps to set global configuration parameters. These values will be the defaults in effect throughout your CloudStack deployment."
+msgstr ""
+
+#: ../../configuration.rst:1539
+#: ../../configuration.rst:1566
+# ac0242e31c474dd29a9b24db5556bf48
+# e7461b5a426d4c808698cd33f7adfccd
+msgid "Log in to the UI as administrator."
+msgstr ""
+
+#: ../../configuration.rst:1541
+# 1b4a8289f9be4367b5464454566ebf4b
+msgid "In the left navigation bar, click Global Settings."
+msgstr ""
+
+#: ../../configuration.rst:1543
+# e82df7307c7f415ab94db7b575b470ce
+msgid "In Select View, choose one of the following:"
+msgstr ""
+
+#: ../../configuration.rst:1545
+# a0142617fa364a99bda590a8e64a934b
+msgid "Global Settings. This displays a list of the parameters with brief descriptions and current values."
+msgstr ""
+
+#: ../../configuration.rst:1548
+# 6047b505f5ab4a81a7fc7b399792b08f
+msgid "Hypervisor Capabilities. This displays a list of hypervisor versions with the maximum number of guests supported for each."
+msgstr ""
+
+#: ../../configuration.rst:1551
+#: ../../configuration.rst:1579
+# 47e638389ccc47d895ad51b8865b67ed
+# 6621f931d1314dcb991dbfed946145d4
+msgid "Use the search box to narrow down the list to those you are interested in."
+msgstr ""
+
+#: ../../configuration.rst:1554
+# 274dfcd501c64b7db7ba5376b4dffe31
+msgid "In the Actions column, click the Edit icon to modify a value. If you are viewing Hypervisor Capabilities, you must click the name of the hypervisor first to display the editing screen."
+msgstr ""
+
+#: ../../configuration.rst:1560
+# c211ee2e26b44d7ebd0c28660e867d35
+msgid "Setting Local Configuration Parameters"
+msgstr ""
+
+#: ../../configuration.rst:1562
+# fce0255430b2475aa263b8ca924cf857
+msgid "Use the following steps to set local configuration parameters for an account, zone, cluster, or primary storage. These values will override the global configuration settings."
+msgstr ""
+
+#: ../../configuration.rst:1568
+# 4d858a0c5a24407ab000370a24eccf0e
+msgid "In the left navigation bar, click Infrastructure or Accounts, depending on where you want to set a value."
+msgstr ""
+
+#: ../../configuration.rst:1571
+# d9cd0d62e3444c7c8fe947bfd1473243
+msgid "Find the name of the particular resource that you want to work with. For example, if you are in Infrastructure, click View All on the Zones, Clusters, or Primary Storage area."
+msgstr ""
+
+#: ../../configuration.rst:1575
+# f33422e144174bf49c2e2e93d9b70b2c
+msgid "Click the name of the resource where you want to set a limit."
+msgstr ""
+
+#: ../../configuration.rst:1577
+# 0c15b68fadd743d5938a20e850c355d7
+msgid "Click the Settings tab."
+msgstr ""
+
+#: ../../configuration.rst:1582
+# fb206dd4787047d6956ce47dace0fd46
+msgid "In the Actions column, click the Edit icon to modify a value."
+msgstr ""
+
+#: ../../configuration.rst:1586
+# e52abd333a034d37b1bb7cba1e32a42b
+msgid "Granular Global Configuration Parameters"
+msgstr ""
+
+#: ../../configuration.rst:1588
+# 20898527299948338ada5e13d94049bb
+msgid "The following global configuration parameters have been made more granular. The parameters are listed under three different scopes: account, cluster, and zone."
+msgstr ""
+
+#: ../../configuration.rst:1595
+#: ../../configuration.rst:1596
+#: ../../configuration.rst:1597
+#: ../../configuration.rst:1598
+# 8df2d6b3d1314a8aae8b1eb457648aff
+# a882525fba6542feb9112de1d3e305e8
+# 65d5144f4743413bb5a8c1757b6f3cef
+# 43b5bc4715d24f18b9bd42535f46cf70
+msgid "account"
+msgstr ""
+
+#: ../../configuration.rst:1595
+# a9df3278553c49a3849dc3e22fe08b2d
+msgid "remote.access.vpn.client.iprange"
+msgstr ""
+
+#: ../../configuration.rst:1595
+# 2c2997c2ad20401da80596c3cc6d70be
+msgid "The range of IPs to be allocated to remotely access the VPN clients. The first IP in the range is used by the VPN server."
+msgstr ""
+
+#: ../../configuration.rst:1596
+# 46f406836e5f47789c7308cbc24461f1
+msgid "allow.public.user.templates"
+msgstr ""
+
+#: ../../configuration.rst:1596
+# 231c392623f04972aab04a526f80765f
+msgid "If false, users will not be able to create public templates."
+msgstr ""
+
+#: ../../configuration.rst:1597
+# 56f5fe2656b14d2ba0b1ad180fd5d5bd
+msgid "use.system.public.ips"
+msgstr ""
+
+#: ../../configuration.rst:1597
+# fb9862501ef4410dae60a5aa8a2ffc1b
+msgid "If true and if an account has one or more dedicated public IP ranges, IPs are acquired from the system pool after all the IPs dedicated to the account have been consumed."
+msgstr ""
+
+#: ../../configuration.rst:1598
+# e7e69d39fefd4be28bfc71ef64d7d997
+msgid "use.system.guest.vlans"
+msgstr ""
+
+#: ../../configuration.rst:1598
+# c001c1a0314e49c2a7b1b3dcfd668036
+msgid "If true and if an account has one or more dedicated guest VLAN ranges, VLANs are allocated from the system pool after all the VLANs dedicated to the account have been consumed."
+msgstr ""
+
+#: ../../configuration.rst:1599
+#: ../../configuration.rst:1600
+#: ../../configuration.rst:1601
+#: ../../configuration.rst:1602
+#: ../../configuration.rst:1603
+#: ../../configuration.rst:1604
+#: ../../configuration.rst:1605
+#: ../../configuration.rst:1607
+#: ../../configuration.rst:1608
+#: ../../configuration.rst:1609
+# 6c8238a6074241b7a25073b38624b975
+# 9647b4f636d242e6b7c8253a4c845cf4
+# db3bde4fcc0c4d8981cde4b9c39ecc90
+# bddc63e51e324877be7710d594e2d149
+# 266ad0b0880c46cbbeac7f7e4e84a5df
+# edfcec1ab75641a487fbfc282f0ad518
+# 054e4713ecb94c12b29863f7f33a85c3
+# 4d2c7029c357490dae1ee56ac89c4269
+# 0e147f13a16a46f7b47a443dd1cd52a9
+# 35235cd387734a709b01e8062eceab67
+msgid "cluster"
+msgstr ""
+
+#: ../../configuration.rst:1599
+# 27e3e5dccb0b42eba3b866f31745c2c4
+msgid "cluster.storage.allocated.capacity.notificationthreshold"
+msgstr ""
+
+#: ../../configuration.rst:1599
+# bb2047027ddf4928a0585e4088ce1f29
+msgid "The percentage, as a value between 0 and 1, of allocated storage utilization above which alerts are sent that the storage is below the threshold."
+msgstr ""
+
+#: ../../configuration.rst:1600
+# cf6962e471014b2e84dc9ff1fb372c82
+msgid "cluster.storage.capacity.notificationthreshold"
+msgstr ""
+
+#: ../../configuration.rst:1600
+# 217cf10ba30b47208d2ed0dab490eb7a
+msgid "The percentage, as a value between 0 and 1, of storage utilization above which alerts are sent that the available storage is below the threshold."
+msgstr ""
+
+#: ../../configuration.rst:1601
+# a802fd66c6ca40ea862ad41ad7784119
+msgid "cluster.cpu.allocated.capacity.notificationthreshold"
+msgstr ""
+
+#: ../../configuration.rst:1601
+# 148d3709a3094f71b1c39d5cc62bdef7
+msgid "The percentage, as a value between 0 and 1, of cpu utilization above which alerts are sent that the available CPU is below the threshold."
+msgstr ""
+
+#: ../../configuration.rst:1602
+# 64f69d16efcb436da37e48eb1da8f50b
+msgid "cluster.memory.allocated.capacity.notificationthreshold"
+msgstr ""
+
+#: ../../configuration.rst:1602
+# 1f20a8d48c184fde84620cea1abfd5df
+msgid "The percentage, as a value between 0 and 1, of memory utilization above which alerts are sent that the available memory is below the threshold."
+msgstr ""
+
+#: ../../configuration.rst:1603
+# d428c8f86cbe464587f88a9ebdbdcff0
+msgid "cluster.cpu.allocated.capacity.disablethreshold"
+msgstr ""
+
+#: ../../configuration.rst:1603
+# 8b66e72376894917b7cdfc704e5be44e
+msgid "The percentage, as a value between 0 and 1, of CPU utilization above which allocators will disable that cluster from further usage. Keep the corresponding notification threshold lower than this value to be notified beforehand."
+msgstr ""
+
+#: ../../configuration.rst:1604
+# 4b250edddaca4cb683468f061af9d819
+msgid "cluster.memory.allocated.capacity.disablethreshold"
+msgstr ""
+
+#: ../../configuration.rst:1604
+# f3b5f79db1cf46e0abbdd19505b30618
+msgid "The percentage, as a value between 0 and 1, of memory utilization above which allocators will disable that cluster from further usage. Keep the corresponding notification threshold lower than this value to be notified beforehand."
+msgstr ""
+
+#: ../../configuration.rst:1605
+# e3d747cbc77546ad928288bc0678580f
+msgid "cpu.overprovisioning.factor"
+msgstr ""
+
+#: ../../configuration.rst:1605
+# cb9a9903057f4089a0f74e7d00af0b09
+msgid "Used for CPU over-provisioning calculation; the available CPU will be the mathematical product of actualCpuCapacity and cpu.overprovisioning.factor."
+msgstr ""
+
+#: ../../configuration.rst:1607
+# 6529835959d14a30a5a02c1dab090203
+msgid "mem.overprovisioning.factor"
+msgstr ""
+
+#: ../../configuration.rst:1607
+# fae6e1ba37794435b586197424421ea0
+msgid "Used for memory over-provisioning calculation."
+msgstr ""
+
+#: ../../configuration.rst:1608
+# fe09a1bfd6994765a0a0686ad370ac69
+msgid "vmware.reserve.cpu"
+msgstr ""
+
+#: ../../configuration.rst:1608
+# 8e7c7caa5bec451783153beae186b804
+msgid "Specify whether or not to reserve CPU when not over-provisioning; In case of CPU over-provisioning, CPU is always reserved."
+msgstr ""
+
+#: ../../configuration.rst:1609
+# d26aa6adac65454ba1ec4fb45c0b5e98
+msgid "vmware.reserve.mem"
+msgstr ""
+
+#: ../../configuration.rst:1609
+# 7fabfb4457fc4f0abf33ffdb09d96f51
+msgid "Specify whether or not to reserve memory when not over-provisioning; In case of memory over-provisioning memory is always reserved."
+msgstr ""
+
+#: ../../configuration.rst:1610
+#: ../../configuration.rst:1612
+#: ../../configuration.rst:1613
+#: ../../configuration.rst:1614
+#: ../../configuration.rst:1615
+#: ../../configuration.rst:1616
+#: ../../configuration.rst:1617
+#: ../../configuration.rst:1618
+#: ../../configuration.rst:1619
+#: ../../configuration.rst:1620
+#: ../../configuration.rst:1621
+# a21b783631704c9b81e3d29fabd9eaff
+# 0806344139bf4b4991de4bd62a3d5ff7
+# e97c440818654e929cb9accc4b0771ee
+# 9d135e71fe5d4eb58e98e8e80401579a
+# 46ed061677414c09b777017b1c2abfc2
+# a0ab2163da2946d686483044d5ca46cd
+# 4647de7d27814699b224fba9a40e5ad2
+# 3ba7ea4a85234737a51cef71da7e07b9
+# 166d0813c0f148288a2803b974241529
+# 95b6358dfd9d45b2a8dbbd2c42531a01
+# 585a49ffc9ad4fbea5f6701f266ee9ec
+msgid "zone"
+msgstr ""
+
+#: ../../configuration.rst:1610
+# 196f60d63c6d46808c9d6bcc2f4c3885
+msgid "pool.storage.allocated.capacity.disablethreshold"
+msgstr ""
+
+#: ../../configuration.rst:1610
+# c04d61f4e28a4f789c84cb900c6cf0a9
+msgid "The percentage, as a value between 0 and 1, of allocated storage utilization above which allocators will disable that pool because the available allocated storage is below the threshold."
+msgstr ""
+
+#: ../../configuration.rst:1612
+# c738bf8adc7443b4ba523dea06552c19
+msgid "pool.storage.capacity.disablethreshold"
+msgstr ""
+
+#: ../../configuration.rst:1612
+# dac4310f42c2420ab725e8ca920ccfa0
+msgid "The percentage, as a value between 0 and 1, of storage utilization above which allocators will disable the pool because the available storage capacity is below the threshold."
+msgstr ""
+
+#: ../../configuration.rst:1613
+# 6edca2b7fcf44a3595a76537c70880f9
+msgid "storage.overprovisioning.factor"
+msgstr ""
+
+#: ../../configuration.rst:1613
+# 8eba02c107c9484093dd79cf0ee65f89
+msgid "Used for storage over-provisioning calculation; available storage will be the mathematical product of actualStorageSize and storage.overprovisioning.factor."
+msgstr ""
+
+#: ../../configuration.rst:1614
+# 9169218f4a2e46e5a8c1c1815238ed9f
+msgid "network.throttling.rate"
+msgstr ""
+
+#: ../../configuration.rst:1614
+# f2cbdfbd49734ffeb7941d05ea8b652b
+msgid "Default data transfer rate in megabits per second allowed in a network."
+msgstr ""
+
+#: ../../configuration.rst:1615
+# ef89e33bf0fd437ea3415cd3d61baba3
+msgid "guest.domain.suffix"
+msgstr ""
+
+#: ../../configuration.rst:1615
+# 30e0fdc26dd1489f86f794370cb4a3ba
+msgid "Default domain name for VMs inside a virtual networks with a router."
+msgstr ""
+
+#: ../../configuration.rst:1616
+# ef39613bc0cf446a9fff88679ae47b0a
+msgid "router.template.xen"
+msgstr ""
+
+#: ../../configuration.rst:1616
+# c419c741cae548769dd227875d563022
+msgid "Name of the default router template on Xenserver."
+msgstr ""
+
+#: ../../configuration.rst:1617
+# 0d23eeec7546470da479531c87189b4d
+msgid "router.template.kvm"
+msgstr ""
+
+#: ../../configuration.rst:1617
+# baf932ce269f42588943f7fdb4ec5234
+msgid "Name of the default router template on KVM."
+msgstr ""
+
+#: ../../configuration.rst:1618
+# 2bc3e93d62f2457c8cbb8bbdcf4cf5ac
+msgid "router.template.vmware"
+msgstr ""
+
+#: ../../configuration.rst:1618
+# 9e6fcedba1f04fdab8a8542ea32d036f
+msgid "Name of the default router template on VMware."
+msgstr ""
+
+#: ../../configuration.rst:1619
+# 82a78e88325744e592b8bee2fce00ea7
+msgid "enable.dynamic.scale.vm"
+msgstr ""
+
+#: ../../configuration.rst:1619
+# 58f5d9335ab549a79f28e17a2c562056
+msgid "Enable or diable dynamically scaling of a VM."
+msgstr ""
+
+#: ../../configuration.rst:1620
+# 0ac19d4f17914e60ab366c0b230b7076
+msgid "use.external.dns"
+msgstr ""
+
+#: ../../configuration.rst:1620
+# 82b4dbaa5fec492986ebfd7d4bf76954
+msgid "Bypass internal DNS, and use the external DNS1 and DNS2"
+msgstr ""
+
+#: ../../configuration.rst:1621
+# c8177a7ac4ea4c07bf0c16f2833e48bf
+msgid "blacklisted.routes"
+msgstr ""
+
+#: ../../configuration.rst:1621
+# d9441a44a1824e80804bbbe62fd7f531
+msgid "Routes that are blacklisted cannot be used for creating static routes for a VPC Private Gateway."
+msgstr ""
+
diff --git a/source/installguide/locale/pot/hypervisor/hyperv.pot b/source/installguide/locale/pot/hypervisor/hyperv.pot
new file mode 100644
index 0000000..f39595b
--- /dev/null
+++ b/source/installguide/locale/pot/hypervisor/hyperv.pot
@@ -0,0 +1,449 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../hypervisor/hyperv.rst:18
+# a5185d38ad2e4f6cbc35116341dccf23
+msgid "Hyper-V Installation and Configuration"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:20
+# d110647269414479b7fb035bfdcdd6f6
+msgid "If you want to use Hyper-V hypervisor to run guest virtual machines, install Hyper-V on the hosts in your cloud. The instructions in this section doesn't duplicate Hyper-V Installation documentation. It provides the CloudStack-specific steps that are needed to prepare a Hyper-V host to work with CloudStack."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:28
+# f65dfc47347b4c348baf2a6336cacf5b
+msgid "System Requirements for Hyper-V Hypervisor Hosts"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:32
+# 7a236efba2054d4ba58d9ecdaaf20a09
+msgid "Supported Operating Systems for Hyper-V Hosts"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:34
+# bcd4ae34d08a497bad4e1b389059ec7d
+msgid "Windows Server 2012 R2 Standard"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:36
+# 680742a637b2491cbe7f3677dca729ba
+msgid "Windows Server 2012 R2 Datacenter"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:38
+# ccbfedc695de4f1fa589f6b2274d49a1
+msgid "Hyper-V 2012 R2"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:42
+# f9d4e4e9531e4e13910e7f9bcf4f6231
+msgid "Minimum System Requirements for Hyper-V Hosts"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:44
+# cd76d4e704da43a2bf46b4a1ca1206a9
+msgid "1.4 GHz 64-bit processor with hardware-assisted virtualization."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:46
+# d66329292d3e4d679ddd534dcb5b56b1
+msgid "800 MB of RAM"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:48
+# c68a1b515138408e8b48078375c35450
+msgid "32 GB of disk space"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:50
+# 1924b40a1ea34af985c514e7e00fcf07
+msgid "Gigabit (10/100/1000baseT) Ethernet adapter"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:54
+# 5b9c638983de4946816feb1dfe06f7a3
+msgid "Supported Storage"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:56
+# 5501dc718ec148a1b106d7eac8e01f89
+msgid "Primary Storage: Server Message Block (SMB) Version 3, Local"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:58
+# d98826167d964496b31bc798ae8ad5a8
+msgid "Secondary Storage: SMB"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:62
+# 51e903e68fa44cc987b6c2ad08dbeb36
+msgid "Preparation Checklist for Hyper-V"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:64
+# 556e9ae21bb747fe83f5e90bf14d165b
+msgid "For a smoother installation, gather the following information before you start:"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:68
+# 5e62ce48e3304d90a1e5f41a3c4bd74c
+msgid "Hyper-V Requiremen ts"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:68
+# d69ee48d947543d6a0b0d9b680e79b99
+msgid "Value"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:68
+# 020b9f3298894f29adbb932ddaefd9e4
+msgid "Description"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:72
+# a4ae60478f084501bf98804259ca31c7
+msgid "Server Roles"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:72
+# 92022baf55eb439499536554f1c93bc6
+msgid "Hyper-V"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:72
+# 85cc74d52bf447b59ad5a8fb8f528075
+msgid "After the Windows Server 2012 R2 installation, ensure that Hyper-V is selected from Server Roles. For more information, see `Installing Hyper-V <http://technet.microsoft.com/en-us/library/ jj134187.aspx#BKMK_Step2>`__."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:78
+# 19d59b3dace14c519959ecfa3f73fbca
+msgid "Share Location"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:78
+# 6de5f24d299b4e90a4266202e2e60a6c
+msgid "New folders in the /Share director y"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:78
+# 81267131a3fc4d27bf3bcfa5702952c3
+msgid "Ensure that folders are created for Primary and Secondary storage. The SMB share and the hosts should be part of the same domain."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:82
+# 22eb1d2d75ef4c2b898ba205496f1923
+msgid "If you are using Windows SMB share, the location of the file share for the Hyper-V deployment will be the new folder created in the \\\\Shares on the selected volume. You can create sub-folders for both PRODUCT Primary and Secondary storage within the share location. When you select the profile for the file shares, ensure that you select SMB Share -Applications. This creates the file shares with settings appropriate for Hyper-V."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:92
+# 4ffc82e6d7e845dfa1b880966b6d4564
+msgid "Domain and Hosts"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:92
+# a9f0efdf8d5a493d82c08b429664d7b1
+msgid "Hosts should be part of the same Active Directory domain."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:95
+# a92cae038f1a46f789f2c08a44dcd92c
+msgid "Hyper-V Users"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:95
+# 97f0324a2e62434a98f3f91e9478e6f4
+msgid "Full control"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:95
+# 0bcab591e0f042dc8574a8c57b363303
+msgid "Full control on the SMB file share."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:98
+# ee9dcfd392f84b7790d3017d9a958d69
+msgid "Virtual Switch"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:98
+# 84b516f8c0844014922eb947cca2b078
+msgid "If you are using Hyper-V 2012 R2, manually create an external virtual switch before adding the host to PRODUCT. If the Hyper-V host is added to the Hyper-V manager, select the host, then click Virtual Switch Manager, then New Virtual Switch. In the External Network, select the desired NIC adapter and click Apply."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:106
+#: ../../hypervisor/hyperv.rst:237
+# 02cd2a7fcf2e4b109e8c6ca41162ea8c
+# 985a36a6ae43480081c0d0b588f48aad
+msgid "If you are using Windows 2012 R2, virtual switch is created automatically."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:109
+# 7c5051f047ec44a491a9a65e006d5f80
+msgid "Virtual Switch Name"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:109
+# cfebf27404b04a1799cecac6f0d87e84
+msgid "Take a note of the name of the virtual switch. You need to specify that when configuring PRODUCT physical network labels."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:113
+# ad1036d7fef9481ca332cd4247790520
+msgid "Hyper-V Domain Users"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:113
+# 4c2560df94de47199684bb4acfd7808b
+msgid "Add the Hyper-V domain users to the Hyper-V Administrators group."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:116
+# 6571afa7b1d446baaebeff5f13b1e3e8
+msgid "A domain user should have full control on the SMB share that is exported for primary and secondary storage."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:120
+# b88a4f4ee49d4182aff6ba298990d862
+msgid "This domain user should be part of the Hyper-V Administrators and Local Administrators group on the Hyper-V hosts that are to be managed by PRODUCT."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:125
+# a99dc8722cb14924894d5b59a0f7a3bb
+msgid "The Hyper-V Agent service runs with the credentials of this domain user account."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:128
+# 39ee910d4ba544e2b28f18e65ac8a889
+msgid "Specify the credential of the domain user while adding a host to PRODUCT so that it can manage it."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:132
+# 2c879cedc51b41c9ac25284b8676b011
+msgid "Specify the credential of the domain user while adding a shared SMB primary or secondary storage."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:136
+#: ../../hypervisor/hyperv.rst:139
+#: ../../hypervisor/hyperv.rst:144
+# a9e85836b0a04d6794af8975a728757c
+# 6cf6d3303dc24afba8c72b0ac1f61aa5
+# 1399d631b8b94a1b935d4e56999a727a
+msgid "Migration"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:136
+# 9b65f73f4def43419096db3143353cdd
+msgid "Migratio n"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:136
+# dc9b9f2328ac4f3ebb5725c452140827
+msgid "Enable Migration."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:139
+# 516666dbd8874b3ca81518e553176a9f
+msgid "Delegati on"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:139
+# af14af2a223b4526acb445f35ff387fe
+msgid "If you want to use Live Migration, enable Delegation. Enable the following services of other hosts participating in Live Migration: CIFS and Microsoft Virtual System Migration Service."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:144
+# a44c5e1eebd24499a9a3c60210231d65
+msgid "Kerberos"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:144
+# dfad3d88e2c44f009ba6a629d2d11e09
+msgid "Enable Kerberos for Live Migration."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:146
+# 8a1e170e190d499ca5cca07a1df60781
+msgid "Network Access Permission for Dial-in"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:146
+# 25fcf66d3708461798a6ccaae50eaf2e
+msgid "Allow access"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:146
+# c278cbf02bda42f8a6dd149a89346803
+msgid "Allow access for Dial-in connections."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:155
+# ee52be753a9f4e339af5f44dbd6ae389
+msgid "Hyper-V Installation Steps"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:157
+# 5e6a34d960324a189dba8dafc3199b3f
+msgid "Download the operating system from `Windows Server 2012 R2 <http://technet.microsoft.com/en-us/windowsserver/hh534429>`_."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:160
+# ffa1994b12b44c7aad4386869fd9fcf3
+msgid "Install it on the host as given in `Install and Deploy Windows Server 2012 R2 <http://technet.microsoft.com/library/hh831620>`_."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:163
+# a13474286278439686c5ee1893cd2bb1
+msgid "Post installation, ensure that you enable Hyper-V role in the server."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:165
+# 7879473d0a8c43d0b28378281f2486d9
+msgid "If no Active Directory domain exists in your deployment, create one and add users to the domain."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:168
+# 470dd82226bd40d19ad39f3ebe2389c2
+msgid "In the Active Directory domain, ensure that all the Hyper-v hosts are added so that all the hosts are part of the domain."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:171
+# da2cd8c727fa4b4bad3c78af98264cb0
+msgid "Add the domain user to the following groups on the Hyper-V host: Hyper-V Administrators and Local Administrators."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:176
+# 4643f2a8b84e4e2ebbe709f5ffe25c84
+msgid "Installing the CloudStack Agent on a Hyper-V Host"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:178
+# 3ab695eb9dee461ea69f8078437525b4
+msgid "The Hyper-V Agent helps CloudStack perform operations on the Hyper-V hosts. This Agent communicates with the Management Server and controls all the instances on the host. Each Hyper-V host must have the Hyper-V Agent installed on it for successful interaction between the host and CloudStack. The Hyper-V Agent runs as a Windows service. Install the Agent on each host using the following steps."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:185
+# 481e02540708427aae673f5e8c5c81c0
+msgid "CloudStack Management Server communicates with Hyper-V Agent by using HTTPS. For secure communication between the Management Server and the host, install a self-signed certificate on port 8250."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:190
+# 79d9ee71e1814e18ae066a37a64ccf0f
+msgid "The Agent installer automatically perform this operation. You have not selected this option during the Agent installation, it can also be done manually as given in step 1."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:194
+# 9e04f652b33b4fdaa6d33622de1f6c16
+msgid "Create and add a self-signed SSL certificate on port 8250:"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:196
+# 71791cb8679f449ea9810f71aea6642a
+msgid "Create A self-signed SSL certificate:"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:202
+# bf728cee5a7a4b65b04ede76db396b30
+msgid "This command creates the self-signed certificate and add that to the certificate store ``LocalMachine\\My``."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:205
+# f464d4439cc44510b140754a2c06e458
+msgid "Add the created certificate to port 8250 for https communication:"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:211
+# 870daf8bb8194bc5872d413d1cdea8a0
+msgid "Thumbprint is the thumbprint of the certificate you created."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:213
+# 43b892a6de7040a1b7465f30523308d8
+msgid "Build the CloudStack Agent for Hyper-V as given in `Building CloudStack Hyper-V Agent <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Creating+Hyperv+Agent+Installer>`__."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:216
+# 947a2a5df4c84a128f9d8fae319c8153
+msgid "As an administrator, run the installer."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:218
+# 19b6346a3cb94ec59710f84565f8f65c
+msgid "Provide the Hyper-V admin credentials when prompted."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:220
+# f254b72c1df64645831780947bef0830
+msgid "When the agent installation is finished, the agent runs as a service on the host machine."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:225
+# 1a5dd8f4c84b4b2aa53baa0f573b51ce
+msgid "Physical Network Configuration for Hyper-V"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:227
+# 380cb814510b419697ab9623d9466f8e
+msgid "You should have a plan for how the hosts will be cabled and which physical NICs will carry what types of traffic. By default, CloudStack will use the device that is used for the default route."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:231
+# d473bf7504d0430ca53e00c7294017bc
+msgid "If you are using Hyper-V 2012 R2, manually create an external virtual switch before adding the host to CloudStack. If the Hyper-V host is added to the Hyper-V manager, select the host, then click Virtual Switch Manager, then New Virtual Switch. In the External Network, select the desired NIC adapter and click Apply."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:242
+# 7f2f77fa086a4dba967596b9382888ed
+msgid "Storage Preparation for Hyper-V (Optional)"
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:244
+# b30ee4d30a1341bc8d882e9053000bd4
+msgid "CloudStack allows administrators to set up shared Primary Storage and Secondary Storage that uses SMB."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:247
+# 4caaf6cc083841b2aeaf487f0f1ec4a0
+msgid "Create a SMB storage and expose it over SMB Version 3."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:249
+# d49322cf1c1d4f8d8c9ceed36c959d0f
+msgid "For more information, see `Deploying Hyper-V over SMB <http://technet.microsoft.com/en-us/library/jj134187.aspx>`_."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:252
+# 9aefadf6e86e499c98acbb5785e98930
+msgid "You can also create and export SMB share using Windows. After the Windows Server 2012 R2 installation, select File and Storage Services from Server Roles to create an SMB file share. For more information, see `Creating an SMB File Share Using Server Manager <http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step3>`_."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:258
+# 484e3791c2844730a548c8da780b2bf4
+msgid "Add the SMB share to the Active Directory domain."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:260
+# 1917261171b047b58051d75066e5fb9a
+msgid "The SMB share and the hosts managed by CloudStack need to be in the same domain. However, the storage should be accessible from the Management Server with the domain user privileges."
+msgstr ""
+
+#: ../../hypervisor/hyperv.rst:264
+# 5c7bf0eee6784b07ba689b0964ebdb37
+msgid "While adding storage to CloudStack, ensure that the correct domain, and credentials are supplied. This user should be able to access the storage from the Management Server."
+msgstr ""
+
diff --git a/source/installguide/locale/pot/hypervisor/kvm.pot b/source/installguide/locale/pot/hypervisor/kvm.pot
new file mode 100644
index 0000000..c40ddd8
--- /dev/null
+++ b/source/installguide/locale/pot/hypervisor/kvm.pot
@@ -0,0 +1,949 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../hypervisor/kvm.rst:18
+# ebeb1b4a092d444ea21ba9ad826adffe
+msgid "KVM Hypervisor Host Installation"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:21
+# 97cb5ce75570443fb1ad7cf720fdab2a
+msgid "System Requirements for KVM Hypervisor Hosts"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:23
+# 9e938eeaf34e4bacb41261551600a15d
+msgid "KVM is included with a variety of Linux-based operating systems. Although you are not required to run these distributions, the following are recommended:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:27
+# 01060377fba240b98bfb3214ded11e8c
+msgid "CentOS / RHEL: 6.3"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:29
+# c65d0ad029984ec697cc18cf30a3cadc
+msgid "Ubuntu: 12.04(.1)"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:31
+# 2c83e5c69a214b408332608c4f0cd35c
+msgid "The main requirement for KVM hypervisors is the libvirt and Qemu version. No matter what Linux distribution you are using, make sure the following requirements are met:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:35
+# 41d119144cb04445888526ae22eaff17
+msgid "libvirt: 0.9.4 or higher"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:37
+# c01a69a6ea624526aed8eb093c9580c7
+msgid "Qemu/KVM: 1.0 or higher"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:39
+# 651ec4f15bf24d0ca383e80951a6ab85
+msgid "The default bridge in CloudStack is the Linux native bridge implementation (bridge module). CloudStack includes an option to work with OpenVswitch, the requirements are listed below"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:43
+# 38d4ca03c8c24e2c9d6cd87e5c0b1d17
+msgid "libvirt: 0.9.11 or higher"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:45
+# 55b8b19e86c9462297d454cf0f32bb13
+msgid "openvswitch: 1.7.1 or higher"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:47
+# 8bb45c3db83e4685a2f5f9b56c255a67
+msgid "In addition, the following hardware requirements apply:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:49
+# a3affcf8d2194e6ca7031037e7498bea
+msgid "Within a single cluster, the hosts must be of the same distribution version."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:52
+# fc001eaf8fb842d7adbbf5bb977be8fd
+msgid "All hosts within a cluster must be homogenous. The CPUs must be of the same type, count, and feature flags."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:55
+# 040002ad5b674b0c821aa9750f44d966
+msgid "Must support HVM (Intel-VT or AMD-V enabled)"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:57
+# 430eb7a34d084edc906c29088ecd022d
+msgid "64-bit x86 CPU (more cores results in better performance)"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:59
+# 7a5ab30337ea4ad3911e07092171034c
+msgid "4 GB of memory"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:61
+# 54804b801477441396a656d1f55ce683
+msgid "At least 1 NIC"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:63
+# 3d590f343f0c40e8a3ead4dd2fe2fa47
+msgid "When you deploy CloudStack, the hypervisor host must not have any VMs already running"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:68
+# 8b68c1fe985341dcb44b491222fc84ad
+msgid "KVM Installation Overview"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:70
+# b9ec75165d5f4c29afccc0e271256a34
+msgid "If you want to use the Linux Kernel Virtual Machine (KVM) hypervisor to run guest virtual machines, install KVM on the host(s) in your cloud. The material in this section doesn't duplicate KVM installation docs. It provides the CloudStack-specific steps that are needed to prepare a KVM host to work with CloudStack."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:77
+# f5be326bc3d74ee58f731bc68b96b0fb
+msgid "Before continuing, make sure that you have applied the latest updates to your host."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:81
+# 4e04ebf1f4b34b6cafaa81b1db7348cb
+msgid "It is NOT recommended to run services on this host not controlled by CloudStack."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:84
+# 05cc9620411849a395036ae746c8c8ab
+msgid "The procedure for installing a KVM Hypervisor Host is:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:86
+#: ../../hypervisor/kvm.rst:96
+# 6021037c1bdc4f11a0e777ddb5074991
+# 2587ced26d8445e89dc4b8dc2392793f
+msgid "Prepare the Operating System"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:88
+# 3e3ad1c9b475475d8c6d84148d8a187b
+msgid "Install and configure libvirt"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:90
+# bfef16f0f0344071beb3918d9b215e58
+msgid "Configure Security Policies (AppArmor and SELinux)"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:92
+#: ../../hypervisor/kvm.rst:139
+# 4343245b910e46b2889fad1a299a3a6d
+# 13ebc121a8db4e73b1da322e022b044e
+msgid "Install and configure the Agent"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:98
+# 0da476eb6feb4293aff700a82bfb838e
+msgid "The OS of the Host must be prepared to host the CloudStack Agent and run KVM instances."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:101
+# bdd309f671e84b25b03a65509e8f6b42
+msgid "Log in to your OS as root."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:103
+# 2994046162c749719c61badf46ac4ad3
+msgid "Check for a fully qualified hostname."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:109
+# 7140e2b27dea40f8b406eb3c53a6926a
+msgid "This should return a fully qualified hostname such as \"kvm1.lab.example.org\". If it does not, edit /etc/hosts so that it does."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:113
+# d097f223788942dca1e0f0e3a835719d
+msgid "Make sure that the machine can reach the Internet."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:119
+# e9e925f675b24298904628fe8d5d3e22
+msgid "Turn on NTP for time synchronization."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:122
+# e0e2735eb1544cbea55afc3efd41e42e
+msgid "NTP is required to synchronize the clocks of the servers in your cloud. Unsynchronized clocks can cause unexpected problems."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:125
+# fd84cef5844c4bb4861e1a723be7b730
+msgid "Install NTP"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:135
+# 43ee16ce469842bdb337c3e50b34061c
+msgid "Repeat all of these steps on every hypervisor host."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:141
+# 5fe0d335c6f646c987b8e7f2c3c9176d
+msgid "To manage KVM instances on the host CloudStack uses a Agent. This Agent communicates with the Management server and controls all the instances on the host."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:145
+# 6e696930e763476fabe3f4eee7ff4119
+msgid "First we start by installing the agent:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:147
+#: ../../hypervisor/kvm.rst:297
+#: ../../hypervisor/kvm.rst:333
+# 707c5512b9c244b29a78dff8a4299a43
+# 1640e85f451b43bf9287ea34e03d19d0
+# 7296990676914572906f8131a2c931ca
+msgid "In RHEL or CentOS:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:153
+#: ../../hypervisor/kvm.rst:303
+# b558c002a308451c962adfba860db12a
+# c6cfcfd744df46039292c75ce9c00344
+msgid "In Ubuntu:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:159
+#: ../../hypervisor/kvm.rst:880
+# 996e7f4699cf4e99812ef4193d0f5522
+# 0066de97fb884b43b6b6e86bdc4a8d19
+msgid "The host is now ready to be added to a cluster. This is covered in a later section, see :ref:`adding-a-host`. It is recommended that you continue to read the documentation before adding the host!"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:166
+# 4896f6ced9d2426d815ed0b39e1f2f4a
+msgid "Configure CPU model for KVM guest (Optional)"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:168
+# 20ff9499c4f34a21932f12ab3ace15d5
+msgid "In additional,the CloudStack Agent allows host administrator to control the guest CPU model which is exposed to KVM instances. By default, the CPU model of KVM instance is likely QEMU Virtual CPU version x.x.x with least CPU features exposed. There are a couple of reasons to specify the CPU model:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:174
+# 6e0e4449f4ec4464a09f85e60e4370ed
+msgid "To maximise performance of instances by exposing new host CPU features to the KVM instances;"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:177
+# c7628f91810a40ccb39bcf8305be59da
+msgid "To ensure a consistent default CPU across all machines,removing reliance of variable QEMU defaults;"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:180
+# c7ea77c20a4345ba96d87413aa516fb5
+msgid "For the most part it will be sufficient for the host administrator to specify the guest CPU config in the per-host configuration file (/etc/cloudstack/agent/agent.properties). This will be achieved by introducing two new configuration parameters:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:190
+# b49256d2460d47f688c7624e3f4e6a72
+msgid "There are three choices to fulfill the cpu model changes:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:192
+# 07a33361eda847d59a1ac15adc6af65f
+msgid "**custom:** you can explicitly specify one of the supported named model in /usr/share/libvirt/cpu\\_map.xml"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:195
+# 6282d4279ada4fb88884fea8fd73cd06
+msgid "**host-model:** libvirt will identify the CPU model in /usr/share/libvirt/cpu\\_map.xml which most closely matches the host, and then request additional CPU flags to complete the match. This should give close to maximum functionality/performance, which maintaining good reliability/compatibility if the guest is migrated to another host with slightly different host CPUs."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:202
+# f8b3348db3b04cfaa45ddadb3e295515
+msgid "**host-passthrough:** libvirt will tell KVM to passthrough the host CPU with no modifications. The difference to host-model, instead of just matching feature flags, every last detail of the host CPU is matched. This gives absolutely best performance, and can be important to some apps which check low level CPU details, but it comes at a cost with respect to migration: the guest can only be migrated to an exactly matching host CPU."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:210
+# 47f1633a109745c68733dbe0a7ba9ce9
+msgid "Here are some examples:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:212
+# d710e6fa4277486c8d61b2f169b7f2b3
+msgid "custom"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:219
+# f5b710b35db840c7affadc4299dae2e5
+msgid "host-model"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:225
+# aecbb45afbe5482aa5532e1d54f55842
+msgid "host-passthrough"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:232
+# fb86e9deb45745bd9fac900c4f7e7ec6
+msgid "host-passthrough may lead to migration failure,if you have this problem, you should use host-model or custom"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:237
+# 00afd93377104391bc056ba2988ad1d5
+msgid "Install and Configure libvirt"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:239
+# ac5f3de595104874aca72f9e3e908bb2
+msgid "CloudStack uses libvirt for managing virtual machines. Therefore it is vital that libvirt is configured correctly. Libvirt is a dependency of cloudstack-agent and should already be installed."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:243
+# ed8dd766459147cbb85ff50d90c4b80e
+msgid "In order to have live migration working libvirt has to listen for unsecured TCP connections. We also need to turn off libvirts attempt to use Multicast DNS advertising. Both of these settings are in ``/etc/libvirt/libvirtd.conf``"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:248
+# 25fdfe15f0fd4e42a8859066fd10be16
+msgid "Set the following parameters:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:270
+# b077d28a7fb14c0da6df9ced98d909bd
+msgid "Turning on \"listen\\_tcp\" in libvirtd.conf is not enough, we have to change the parameters as well:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:273
+# fe5a6a536a154770ac58fbf4ace2ce6e
+msgid "On RHEL or CentOS modify ``/etc/sysconfig/libvirtd``:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:275
+# d50d8ab0ec584f1bbdc8af56f6265ffc
+msgid "Uncomment the following line:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:281
+# 3f26c856207e4381bf305695a8a1b875
+msgid "On Ubuntu: modify ``/etc/default/libvirt-bin``"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:283
+# 6115b7018d9740c4913aacc4a4c661b2
+msgid "Add \"-l\" to the following line"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:289
+# fcea59d4e03647eeaeaa3ac4932357ac
+msgid "so it looks like:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:295
+# a61d4201e47640b197fdfbcd22c10e63
+msgid "Restart libvirt"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:311
+# f5d8d474c64344d19b502d403b56e5ac
+msgid "Configure the Security Policies"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:313
+# a4cdda146bad44b39bbc09b937240984
+msgid "CloudStack does various things which can be blocked by security mechanisms like AppArmor and SELinux. These have to be disabled to ensure the Agent has all the required permissions."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:317
+# 4b7a44bcec124017bf23bc0dd76e7428
+msgid "Configure SELinux (RHEL and CentOS)"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:319
+# fc143c3fe742401a9106eafabea70c57
+msgid "Check to see whether SELinux is installed on your machine. If not, you can skip this section."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:322
+# 2b54567dbb364fddb556f971dd10b551
+msgid "In RHEL or CentOS, SELinux is installed and enabled by default. You can verify this with:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:329
+# 80c7202620bb48148e037b74df42ee70
+msgid "Set the SELINUX variable in ``/etc/selinux/config`` to \"permissive\". This ensures that the permissive setting will be maintained after a system reboot."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:339
+# 4cad5c113a6d40c78b1deced30e96b20
+msgid "Change the following line"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:345
+# c97ebe4c24c3452b87cde950fe2fc4c8
+msgid "to this"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:351
+# 1fe4df6a30c94763bdb8884755fdcdce
+msgid "Then set SELinux to permissive starting immediately, without requiring a system reboot."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:358
+# 0af84eecf2664f6cb9301604df585e10
+msgid "Configure Apparmor (Ubuntu)"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:360
+# fc4f77ded77f4d28afca68609461f0bb
+msgid "Check to see whether AppArmor is installed on your machine. If not, you can skip this section."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:363
+# 04268552313d40f3a6be6f7a36fa99fe
+msgid "In Ubuntu AppArmor is installed and enabled by default. You can verify this with:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:370
+# 6fd96cf6f5224881a383a21dd3963718
+msgid "Disable the AppArmor profiles for libvirt"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:390
+# af0b6b3d14164b38bb854739db62c3f5
+msgid "Configure the network bridges"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:393
+#: ../../hypervisor/kvm.rst:616
+# fa37fe8e08ec4f3a956c501d3aa88019
+# 4fa42c30b73c4240b8836f967070df3a
+msgid "This is a very important section, please make sure you read this thoroughly."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:396
+# 9ec0bad9717b478889252f4b10b4ebf0
+msgid "This section details how to configure bridges using the native implementation in Linux. Please refer to the next section if you intend to use OpenVswitch"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:400
+#: ../../hypervisor/kvm.rst:618
+# f6707b5fbc3f4ea2a4baa8b33756195f
+# bbbbeeb75efc49bbb12e571702c69490
+msgid "In order to forward traffic to your instances you will need at least two bridges: *public* and *private*."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:403
+#: ../../hypervisor/kvm.rst:621
+# 3bcaf96162614d5a990b65c272e2627f
+# 70d93337f9884c43b723d19f188000c6
+msgid "By default these bridges are called *cloudbr0* and *cloudbr1*, but you do have to make sure they are available on each hypervisor."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:406
+#: ../../hypervisor/kvm.rst:624
+# 965691e1a7d742b4a8c0360d6c31e2f6
+# d4d5af0a56be4b0093be521d30e2f4c2
+msgid "The most important factor is that you keep the configuration consistent on all your hypervisors."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:411
+#: ../../hypervisor/kvm.rst:643
+# 8457ada239b24dc388b653310867751e
+# 9e68314d8d8e4f319f85e5d12ec665dc
+msgid "Network example"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:413
+#: ../../hypervisor/kvm.rst:645
+# 4de6b0928811452f9123e93380d47402
+# 49e2abb08c79429e8e2a48cb9f02907d
+msgid "There are many ways to configure your network. In the Basic networking mode you should have two (V)LAN's, one for your private network and one for the public network."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:417
+#: ../../hypervisor/kvm.rst:649
+# 39d4d3c7755c40b5aea4cebdad65af1b
+# c6f350d0cfec4016ac48462e94a09728
+msgid "We assume that the hypervisor has one NIC (eth0) with three tagged VLAN's:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:420
+#: ../../hypervisor/kvm.rst:652
+# e682c9d170fd475da9c2a680bb5099ff
+# d38b80c792834c7c8649626ad41e9300
+msgid "VLAN 100 for management of the hypervisor"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:422
+#: ../../hypervisor/kvm.rst:654
+# d25eda691ed1435c880ed6c76b1fef81
+# 1022b2a4fd5848dda685cfe71fd18690
+msgid "VLAN 200 for public network of the instances (cloudbr0)"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:424
+#: ../../hypervisor/kvm.rst:656
+# e0eff3d36bba429288abf8657deeb28e
+# f3b7f72de0094b6e9210605736fa23c8
+msgid "VLAN 300 for private network of the instances (cloudbr1)"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:426
+#: ../../hypervisor/kvm.rst:658
+# 514a4f72f28c4c58baeea8b592b75c8e
+# 970bdad2851e4d399cdecca76cbbc302
+msgid "On VLAN 100 we give the Hypervisor the IP-Address 192.168.42.11/24 with the gateway 192.168.42.1"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:430
+#: ../../hypervisor/kvm.rst:662
+# 79adcf25d3a54f778ec9459d0384cb62
+# a686fb2b0fd345d2905f28066f0e0638
+msgid "The Hypervisor and Management server don't have to be in the same subnet!"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:434
+#: ../../hypervisor/kvm.rst:666
+# 83141e4d1ee040d3b63247777f709a6d
+# 5ded57bbb4074546af86d97ade2a6269
+msgid "Configuring the network bridges"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:436
+# 660eb10d8f0c4ed399ee7571538e7b6e
+msgid "It depends on the distribution you are using how to configure these, below you'll find examples for RHEL/CentOS and Ubuntu."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:440
+# 89c3fb6c97034c75836101354c78230f
+msgid "The goal is to have two bridges called 'cloudbr0' and 'cloudbr1' after this section. This should be used as a guideline only. The exact configuration will depend on your network layout."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:446
+#: ../../hypervisor/kvm.rst:698
+# 77ee68f2056d43219edea55da8fa4914
+# be99a34a26fd4b958c9fd807e0dd34af
+msgid "Configure in RHEL or CentOS"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:448
+# 300927ecc5b44fc88b3d0354324b833a
+msgid "The required packages were installed when libvirt was installed, we can proceed to configuring the network."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:451
+#: ../../hypervisor/kvm.rst:703
+# 0979f7549d3d40109f7541534976337c
+# c06eae41831f473c95f89897f4086011
+msgid "First we configure eth0"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:457
+#: ../../hypervisor/kvm.rst:709
+# 36f103232df444d4851ddb29018cf8e7
+# 9cc8329e54ac46d4844dba0b2f07de57
+msgid "Make sure it looks similar to:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:468
+# 0a69c047e9904d2fa4430ed750a2a62d
+msgid "We now have to configure the three VLAN interfaces:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:517
+# 121e20a6f2bf43c8b4cb4b59090ad9d5
+msgid "Now we have the VLAN interfaces configured we can add the bridges on top of them."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:524
+# 3199cc44a9af4582a29269e946521a03
+msgid "Now we just configure it is a plain bridge without an IP-Address"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:537
+# 981070114a5a4114bd174bbab7b8879d
+msgid "We do the same for cloudbr1"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:554
+#: ../../hypervisor/kvm.rst:604
+#: ../../hypervisor/kvm.rst:779
+# 9627142b8e984eed84e51f657f8c8241
+# 681bc847b70f47e3ad4630bda2af753a
+# 520007e753694508964c00ca3c481d61
+msgid "With this configuration you should be able to restart the network, although a reboot is recommended to see if everything works properly."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:558
+#: ../../hypervisor/kvm.rst:608
+#: ../../hypervisor/kvm.rst:783
+# 2448b2982d304a79862fe2914c61de64
+# ad16f054466d48dd871757fa669c4df4
+# fa84321526ca43df86de9ecd44cf9461
+msgid "Make sure you have an alternative way like IPMI or ILO to reach the machine in case you made a configuration error and the network stops functioning!"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:563
+# fe3ac0a755274b3a9dddb7d07949ede0
+msgid "Configure in Ubuntu"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:565
+# b098a8a9d90247ab9111fbca07e65fa0
+msgid "All the required packages were installed when you installed libvirt, so we only have to configure the network."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:572
+# 81e2e66c3d79430dbadab3f14cd7d21f
+msgid "Modify the interfaces file to look like this:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:613
+# 48b97fd377be47ce94716c2a129def60
+msgid "Configure the network using OpenVswitch"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:629
+# f755f1c1367b4e49a1a3ea5b0052c263
+msgid "Preparing"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:631
+# 1cd9101e47b3400c8e51f0979708da0d
+msgid "To make sure that the native bridge module will not interfere with openvswitch the bridge module should be added to the blacklist. See the modprobe documentation for your distribution on where to find the blacklist. Make sure the module is not loaded either by rebooting or executing rmmod bridge before executing next steps."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:637
+# 50c9cb6dd4434f198ed2252ec1caa0e4
+msgid "The network configurations below depend on the ifup-ovs and ifdown-ovs scripts which are part of the openvswitch installation. They should be installed in /etc/sysconfig/network-scripts/"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:668
+# 68030dc6b78845d59b796851b9829bdf
+msgid "It depends on the distribution you are using how to configure these, below you'll find examples for RHEL/CentOS."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:672
+# dfc1c63e9eee4272b51c488615bafe37
+msgid "The goal is to have three bridges called 'mgmt0', 'cloudbr0' and 'cloudbr1' after this section. This should be used as a guideline only. The exact configuration will depend on your network layout."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:678
+# c26ca789face40d2a6f9e4779a9d5f95
+msgid "Configure OpenVswitch"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:680
+# 9c03a4fe0070433f867cd736e4f3c8fc
+msgid "The network interfaces using OpenVswitch are created using the ovs-vsctl command. This command will configure the interfaces and persist them to the OpenVswitch database."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:684
+# cdfe3c8fcb434b6783bc0d370d417746
+msgid "First we create a main bridge connected to the eth0 interface. Next we create three fake bridges, each connected to a specific vlan tag."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:700
+# 880d846a8d5b4184a46ae53df77519c2
+msgid "The required packages were installed when openvswitch and libvirt were installed, we can proceed to configuring the network."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:720
+# 1962691daa974f51baaafc174a030561
+msgid "We have to configure the base bridge with the trunk."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:735
+# ff14886892454831bf1869e2433a3d04
+msgid "We now have to configure the three VLAN bridges:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:788
+# c9890b410c3340338a04badf11f3ef7f
+msgid "Configuring the firewall"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:790
+# 10dd274736004147a298a91ec2274c1b
+msgid "The hypervisor needs to be able to communicate with other hypervisors and the management server needs to be able to reach the hypervisor."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:793
+# 7b384a27e3f042949ce580b2ac4cbe02
+msgid "In order to do so we have to open the following TCP ports (if you are using a firewall):"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:796
+# ae053a79c1ef4aa98ebbfa9979dd1dbe
+msgid "22 (SSH)"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:798
+# 68c5bface9c34c46bccfa6f10934745a
+msgid "1798"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:800
+# caf73c191ae44a9694814826ff704533
+msgid "16509 (libvirt)"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:802
+# b41b07df7a30461099d417c16b50b745
+msgid "5900 - 6100 (VNC consoles)"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:804
+# 443df083cb0e49a7a098b6903196471d
+msgid "49152 - 49216 (libvirt live migration)"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:806
+# 087989f68dae411cb79ce11da6c9408d
+msgid "It depends on the firewall you are using how to open these ports. Below you'll find examples how to open these ports in RHEL/CentOS and Ubuntu."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:811
+# 2c327652a9ad4b51b8da0b683a481c88
+msgid "Open ports in RHEL/CentOS"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:813
+# 2c67238eeb0c4181b34a32c059cb47cc
+msgid "RHEL and CentOS use iptables for firewalling the system, you can open extra ports by executing the following iptable commands:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:836
+# f47cb1aac5b0422ea1409fd01b64e2db
+msgid "These iptable settings are not persistent accross reboots, we have to save them first."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:845
+# 8da3ddd17dd24cb8a254b0000f2b336b
+msgid "Open ports in Ubuntu"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:847
+# f59b31a8288b46c8b52ee009069cb2e3
+msgid "The default firewall under Ubuntu is UFW (Uncomplicated FireWall), which is a Python wrapper around iptables."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:850
+# eec901cef5c246699d66ddd141a20525
+msgid "To open the required ports, execute the following commands:"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:873
+# 1e32d61867d64456a033a80cfee8590c
+msgid "By default UFW is not enabled on Ubuntu. Executing these commands with the firewall disabled does not enable the firewall."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:878
+# c72a2dc53e534e2d895ad8057ea4275e
+msgid "Add the host to CloudStack"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:887
+# fcd5e62f095c42fba18d4cbe3326670c
+msgid "Hypervisor Support for Primary Storage"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:889
+# 9439e0974f4043eeae2c168c73f556f9
+msgid "The following table shows storage options and parameters for different hypervisors."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:893
+# 55db4812fcd04f2087654f0e21be25e7
+msgid "Primary Storage Type"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:893
+# 6c7ef9363a364e16a04e878d23b376cd
+msgid "vSphere"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:893
+# 15bb927dd6e5452baba08ee6cd4f6fc6
+msgid "XenServer"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:893
+# b37df2a6784a4006a3e30f6ba3a152e7
+msgid "KVM"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:893
+# fb1d3866f13b4aa19aacc4f30c8109a8
+msgid "Hyper-V"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:895
+# c16b38c01e4c483db9a695a6632b0efc
+msgid "****Format for Disks, Templates, and Snapshots****"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:895
+# de345eec1a6642c1891986bf02de6ba0
+msgid "VMDK"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:895
+#: ../../hypervisor/kvm.rst:895
+# b2a6d313cb904d3694a2f0b3725a5abe
+# 10092f74d840420da35b6fd6ad62897c
+msgid "VHD"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:895
+# 68973e57f36742069e1944c60a5e9d2b
+msgid "QCOW2"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:896
+# 2c4cf6dfb59e4089b98a864d2eed2072
+msgid "**iSCSI support**"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:896
+#: ../../hypervisor/kvm.rst:897
+# 83856e4273e1423fab6ce9e0d1ef763d
+# eff62e1ba15c4299aa34e91768fe41df
+msgid "VMFS"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:896
+# b5f17ceae06e4b3287087f1dd7e66447
+msgid "CLVM"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:896
+#: ../../hypervisor/kvm.rst:897
+# 6fbeac22a7e4426f8288199c5562c19f
+# 06d3800e38854ad1a4c7e5ab1524a5cc
+msgid "Yes, via Shared Mountpoint"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:896
+#: ../../hypervisor/kvm.rst:897
+#: ../../hypervisor/kvm.rst:898
+#: ../../hypervisor/kvm.rst:900
+#: ../../hypervisor/kvm.rst:901
+#: ../../hypervisor/kvm.rst:901
+#: ../../hypervisor/kvm.rst:901
+# af2d92292dc74c1abe3e5be57d4de4de
+# 17923230b7c44ceea8772df6b93a60c7
+# 66d3a2da649747e69d76e2660f83db68
+# 840ad9a22ad645e9aaff9e7fa55d9a5c
+# 64c610239b92429d9192534e52fa9e22
+# 4f751bb0b08e4ef997175c7226f79375
+# aaf3b18e181144bc8aa036fc05b1026e
+msgid "No"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:897
+# 8cf40c3629c54e4dadbda79cd412ea32
+msgid "**Fiber Channel support**"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:897
+# 0b5e9c2691d7495db0a1b19153a02377
+msgid "Yes, via Existing SR"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:898
+# adc9d9dd71c14470a95c7d08135de0dd
+msgid "**NFS support**"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:898
+#: ../../hypervisor/kvm.rst:898
+#: ../../hypervisor/kvm.rst:898
+#: ../../hypervisor/kvm.rst:899
+#: ../../hypervisor/kvm.rst:899
+#: ../../hypervisor/kvm.rst:899
+#: ../../hypervisor/kvm.rst:899
+#: ../../hypervisor/kvm.rst:901
+# ae13c4f842284dab8d25f1f2ef0464d4
+# 2bb33766eba942379a1bd7a229f0c9d3
+# bf75790d687b41a9a2fcc365c05b9b3b
+# 496e32a0a3b2457296ae8edde8e193cf
+# 786d4d9a9c87491999c0d890e5644480
+# bbb64e36851e4f408eece5ed45631e18
+# e7e50588bdea47c3b818586bb0794eec
+# 650dd8bed795460cacca69919ed9d8a3
+msgid "Yes"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:899
+# f601b6265f2e49d580e7e0f6c2207938
+msgid "**Local storage support**"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:900
+# a448b2c9463248a5bbf0e8b12899dafd
+msgid "**Storage over-provisioning**"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:900
+# 5fa8702121894c74a47d11039d9067d9
+msgid "NFS and iSCSI"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:900
+#: ../../hypervisor/kvm.rst:900
+# a8c25f4b466d4e5490d53e22ff3fa4f9
+# 984909a8061340f4a6cd15e77e58780b
+msgid "NFS"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:901
+# 60e22f5e001a46b6950958a9b77c066b
+msgid "**SMB/CIFS**"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:904
+# 1512c02954e2429784f5187cc45a1208
+msgid "XenServer uses a clustered LVM system to store VM images on iSCSI and Fiber Channel volumes and does not support over-provisioning in the hypervisor. The storage server itself, however, can support thin-provisioning. As a result the CloudStack can still support storage over-provisioning by running on thin-provisioned storage volumes."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:910
+# 50dbdfaeac8b4368ab25d9c54267ae1d
+msgid "KVM supports \"Shared Mountpoint\" storage. A shared mountpoint is a file system path local to each server in a given cluster. The path must be the same across all Hosts in the cluster, for example /mnt/primary1. This shared mountpoint is assumed to be a clustered filesystem such as OCFS2. In this case the CloudStack does not attempt to mount or unmount the storage as is done with NFS. The CloudStack requires that the administrator insure that the storage is available"
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:918
+# 3fa95266f86e48d39c7f54a98632534a
+msgid "With NFS storage, CloudStack manages the overprovisioning. In this case the global configuration parameter storage.overprovisioning.factor controls the degree of overprovisioning. This is independent of hypervisor type."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:923
+# d2a34f2d9f4d46759111d884ef353dbf
+msgid "Local storage is an option for primary storage for vSphere, XenServer, and KVM. When the local disk option is enabled, a local disk storage pool is automatically created on each host. To use local storage for the System Virtual Machines (such as the Virtual Router), set system.vm.use.local.storage to true in global configuration."
+msgstr ""
+
+#: ../../hypervisor/kvm.rst:929
+# 5422f4222d5a454babfb7eb7e81822e4
+msgid "CloudStack supports multiple primary storage pools in a Cluster. For example, you could provision 2 NFS servers in primary storage. Or you could provision 1 iSCSI LUN initially and then add a second iSCSI LUN when the first approaches capacity."
+msgstr ""
+
diff --git a/source/installguide/locale/pot/hypervisor/lxc.pot b/source/installguide/locale/pot/hypervisor/lxc.pot
new file mode 100644
index 0000000..81fef09
--- /dev/null
+++ b/source/installguide/locale/pot/hypervisor/lxc.pot
@@ -0,0 +1,621 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../hypervisor/lxc.rst:18
+# 43451b40e15f4f98aff4d4219ca70733
+msgid "LXC Installation and Configuration"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:21
+# 93d6379819944090af5901bb1c1c0d79
+msgid "System Requirements for LXC Hosts"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:23
+# bb261276bb104960bb09b70bc7e46061
+msgid "LXC requires the Linux kernel cgroups functionality which is available starting 2.6.24. Although you are not required to run these distributions, the following are recommended:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:27
+# d68380379bdd49a1891a93478283a52c
+msgid "CentOS / RHEL: 6.3"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:29
+# d13b3427477849a8882c7a2be2c75654
+msgid "Ubuntu: 12.04(.1)"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:31
+# e29f5b26524649c9b046398ff037ce23
+msgid "The main requirement for LXC hypervisors is the libvirt and Qemu version. No matter what Linux distribution you are using, make sure the following requirements are met:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:35
+#: ../../hypervisor/lxc.rst:43
+# 94b1feafb27b4459bed9dd9a2a052c0f
+# baeb40fab6b14df39610ec212fe63108
+msgid "libvirt: 1.0.0 or higher"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:37
+# cad5b5564070411fb6182cd0ad878821
+msgid "Qemu/KVM: 1.0 or higher"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:39
+# 14a04946a13a4d7b967c651ed282a8a1
+msgid "The default bridge in CloudStack is the Linux native bridge implementation (bridge module). CloudStack includes an option to work with OpenVswitch, the requirements are listed below"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:45
+# 50b69be40a954cff921f60a6a771059b
+msgid "openvswitch: 1.7.1 or higher"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:47
+# a1ade5134faf4baf99ac999ab1f26788
+msgid "In addition, the following hardware requirements apply:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:49
+# d15ebc2eead24a9fb2b115ac5127ac1a
+msgid "Within a single cluster, the hosts must be of the same distribution version."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:52
+# 9a162b24f7fd499c9793ac22d8cd360f
+msgid "All hosts within a cluster must be homogenous. The CPUs must be of the same type, count, and feature flags."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:55
+# cd66e1991f8b4d80b5267dda55cec2a8
+msgid "Must support HVM (Intel-VT or AMD-V enabled)"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:57
+# 717b8bb8d1a742d3a0abef21e3f17b90
+msgid "64-bit x86 CPU (more cores results in better performance)"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:59
+# 348214c7e23d48889b3b01488710391f
+msgid "4 GB of memory"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:61
+# 4443612c88374256a08ca5fe5b53af70
+msgid "At least 1 NIC"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:63
+# 1e16cfc2f05e4c219030609a9486327f
+msgid "When you deploy CloudStack, the hypervisor host must not have any VMs already running"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:68
+# 5c575160ed0446838d1cdebcd70cc5b1
+msgid "LXC Installation Overview"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:70
+# f252d45b9213468d9646dc4f539523fa
+msgid "LXC does not have any native system VMs, instead KVM will be used to run system VMs. This means that your host will need to support both LXC and KVM, thus most of the installation and configuration will be identical to the KVM installation. The material in this section doesn't duplicate KVM installation docs. It provides the CloudStack-specific steps that are needed to prepare a KVM host to work with CloudStack."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:78
+# 99cca852be7249bd8ea16dc52a8b405e
+msgid "Before continuing, make sure that you have applied the latest updates to your host."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:82
+# 7a72cc592a1f4a5cb0cacebf3883d960
+msgid "It is NOT recommended to run services on this host not controlled by CloudStack."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:85
+# d6f4000ff3874464bb929b7fb2e49dcc
+msgid "The procedure for installing an LXC Host is:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:87
+#: ../../hypervisor/lxc.rst:97
+# 3957e2eca5b1450fa2cdac31e4c4baa9
+# d3b55c0bf6044446b80d37400ebc93b9
+msgid "Prepare the Operating System"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:89
+# 055e7a4b9b6f40098143553e04e75142
+msgid "Install and configure libvirt"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:91
+# 3d012316e0e548a898752588ad9f8ea6
+msgid "Configure Security Policies (AppArmor and SELinux)"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:93
+#: ../../hypervisor/lxc.rst:140
+# 64413c2cb08e4dc4b057fd257e1e983e
+# 8ef5b6b2388141729517cc4fefd87440
+msgid "Install and configure the Agent"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:99
+# 8466bfaf482d4d6599658d9411867dea
+msgid "The OS of the Host must be prepared to host the CloudStack Agent and run KVM instances."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:102
+# 75c2b7bef1834d809a1804dc83d2e1fa
+msgid "Log in to your OS as root."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:104
+# b9dccd7b46514913be1eb8e7b074ac01
+msgid "Check for a fully qualified hostname."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:110
+# 95a324234f074b9991a1c506af6239c2
+msgid "This should return a fully qualified hostname such as \"kvm1.lab.example.org\". If it does not, edit /etc/hosts so that it does."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:114
+# abcfdb639b3c48e994b3f12ffb1cada1
+msgid "Make sure that the machine can reach the Internet."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:120
+# de73cc85f6bb44e788c9ea8d31d6a6ad
+msgid "Turn on NTP for time synchronization."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:123
+# 9d75eb82ba9f45178754d7a1b28c6a52
+msgid "NTP is required to synchronize the clocks of the servers in your cloud. Unsynchronized clocks can cause unexpected problems."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:126
+# 05286054f8844c638f951a6f8fb5b85e
+msgid "Install NTP"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:136
+# bbe6d187091b41178985da38a664feb3
+msgid "Repeat all of these steps on every hypervisor host."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:142
+# 045c7ecca5a246ff9218024c3f3ae129
+msgid "To manage LXC instances on the host CloudStack uses a Agent. This Agent communicates with the Management server and controls all the instances on the host."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:146
+# c201aad8986d46c891235c1b0db5cd06
+msgid "First we start by installing the agent:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:148
+#: ../../hypervisor/lxc.rst:260
+#: ../../hypervisor/lxc.rst:296
+# 415c53c92754469eb9cc8121af962ecf
+# fb5081e503f74e6995e63f1dd73d384d
+# 67c12bc85b6c4cd28de0f5dfaf696bf0
+msgid "In RHEL or CentOS:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:154
+#: ../../hypervisor/lxc.rst:266
+# d1b500c6b3bb470f8ad07118cc13a0bf
+# 69d3e8a5b14a4d32a55350bfa8b6f12a
+msgid "In Ubuntu:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:160
+# 04df1ba82d804c3e93844dbf7cdd829d
+msgid "Next step is to update the Agent configuration setttings. The settings are in ``/etc/cloudstack/agent/agent.properties``"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:163
+# 3948b221adf748639788b545bdd0e3a7
+msgid "Set the Agent to run in LXC mode:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:169
+# cb52c2209b544fd8a09751340ec83214
+msgid "Optional: If you would like to use direct networking (instead of the default bridge networking), configure these lines:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:184
+#: ../../hypervisor/lxc.rst:667
+# 6d6647d83e8145d28e4220e85924d010
+# c8b990ebe5d445a78252e84e2c4e5652
+msgid "The host is now ready to be added to a cluster. This is covered in a later section, see :ref:`adding-a-host`. It is recommended that you continue to read the documentation before adding the host!"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:191
+# cacd4ea9375c4864a2c9fb041bb4bc7c
+msgid "Install and Configure libvirt"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:193
+# b0f7e7f7680e490eacb65fb0cb1b98c6
+msgid "CloudStack uses libvirt for managing virtual machines. Therefore it is vital that libvirt is configured correctly. Libvirt is a dependency of cloudstack-agent and should already be installed."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:197
+# f54bd7715b5441f687683613bff00956
+msgid "In order to have live migration working libvirt has to listen for unsecured TCP connections. We also need to turn off libvirts attempt to use Multicast DNS advertising. Both of these settings are in ``/etc/libvirt/libvirtd.conf``"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:202
+# 7307dff0578a4767a3b5fa1812366060
+msgid "Set the following parameters:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:224
+# 15b53ac02e8d44e0aa89579320fcdb63
+msgid "Turning on \"listen\\_tcp\" in libvirtd.conf is not enough, we have to change the parameters as well:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:227
+# 48d050262fe84becbb7e6c94efc4dfba
+msgid "On RHEL or CentOS modify ``/etc/sysconfig/libvirtd``:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:229
+# 76e8b6056dc84935aaf0ca036b0155ee
+msgid "Uncomment the following line:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:235
+# f3a3573b89414eb4a4d76ebbe98300d9
+msgid "On Ubuntu: modify ``/etc/default/libvirt-bin``"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:237
+# dd99331d08b34cb7acceb95817539208
+msgid "Add \"-l\" to the following line"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:243
+# 0322d77ee56e454c9351e115b1a8a45d
+msgid "so it looks like:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:249
+# 6334d52ad51a4fc69fc58128e38f2319
+msgid "In order to have the VNC Console work we have to make sure it will bind on 0.0.0.0. We do this by editing ``/etc/libvirt/qemu.conf``"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:252
+# 27259d3d47ab4f929936de05e3d77118
+msgid "Make sure this parameter is set:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:258
+# 314400b666db4e16b3133e7ddb4aa140
+msgid "Restart libvirt"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:274
+# 4d9c0c7846c0455b97268a20ec9eb588
+msgid "Configure the Security Policies"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:276
+# c9864510ba8d4a5183f23a8c14f94563
+msgid "CloudStack does various things which can be blocked by security mechanisms like AppArmor and SELinux. These have to be disabled to ensure the Agent has all the required permissions."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:280
+# 19dce9911cb5468e8ecca028cc3629d0
+msgid "Configure SELinux (RHEL and CentOS)"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:282
+# c7bde8f0637b4bc0b30d695a9148ea26
+msgid "Check to see whether SELinux is installed on your machine. If not, you can skip this section."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:285
+# 4153e72e86e54e569528229e10430c13
+msgid "In RHEL or CentOS, SELinux is installed and enabled by default. You can verify this with:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:292
+# bcc78a8cd2f343dead2d193b7d56bf2e
+msgid "Set the SELINUX variable in ``/etc/selinux/config`` to \"permissive\". This ensures that the permissive setting will be maintained after a system reboot."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:302
+# 43e21420401741e2997b97701eff333e
+msgid "Change the following line"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:308
+# 90ead7a947fc40daabdafad6a1b988fb
+msgid "to this"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:314
+# 3040526ce2ff4279bafd31876dd69d4a
+msgid "Then set SELinux to permissive starting immediately, without requiring a system reboot."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:321
+# 52396bdef51d440f9db42978c93847dc
+msgid "Configure Apparmor (Ubuntu)"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:323
+# 19599a1513614b4f984636e98ee6d2f1
+msgid "Check to see whether AppArmor is installed on your machine. If not, you can skip this section."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:326
+# 7c0035c7f5ec4b07ba0088564f98754e
+msgid "In Ubuntu AppArmor is installed and enabled by default. You can verify this with:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:333
+# 4d576628709d47f38d097a74e45b5aa4
+msgid "Disable the AppArmor profiles for libvirt"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:353
+# 4182b6b7d26b46b99feff257f01b0b19
+msgid "Configure the network bridges"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:356
+# c4f546fe4c1d46b0a68265d339df86ff
+msgid "This is a very important section, please make sure you read this thoroughly."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:359
+# e0a8dbc6e7e9410fa60dd28738b69792
+msgid "This section details how to configure bridges using the native implementation in Linux. Please refer to the next section if you intend to use OpenVswitch"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:363
+# 7dfb485a01f249d39f5527e0c4c36cf9
+msgid "In order to forward traffic to your instances you will need at least two bridges: *public* and *private*."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:366
+# 9948a8e0c4ca41c38a570931fd602edc
+msgid "By default these bridges are called *cloudbr0* and *cloudbr1*, but you do have to make sure they are available on each hypervisor."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:369
+# dcbc1defc34f4793b6b6f08e1434ee90
+msgid "The most important factor is that you keep the configuration consistent on all your hypervisors."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:374
+# bc77d68b01c842caaba9c228953c9c9a
+msgid "Network example"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:376
+# d445133ac7514f30b223a361e185bca3
+msgid "There are many ways to configure your network. In the Basic networking mode you should have two (V)LAN's, one for your private network and one for the public network."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:380
+# 7fcbe3dbd5e24cc78a454b43046db3dc
+msgid "We assume that the hypervisor has one NIC (eth0) with three tagged VLAN's:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:383
+# 79f9905e712d4477ad6f1242de95100a
+msgid "VLAN 100 for management of the hypervisor"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:385
+# ae33b27f9bac420195c64c0770a86cd0
+msgid "VLAN 200 for public network of the instances (cloudbr0)"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:387
+# fa09f2d8754547ca8140ba9117584838
+msgid "VLAN 300 for private network of the instances (cloudbr1)"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:389
+# 6b19d1a474714e77a49083b08d8a70ad
+msgid "On VLAN 100 we give the Hypervisor the IP-Address 192.168.42.11/24 with the gateway 192.168.42.1"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:393
+# 66e4325554bd44839b00ff46222bb488
+msgid "The Hypervisor and Management server don't have to be in the same subnet!"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:396
+# 0c38727f3c5145db8ac92b2df423f9f3
+msgid "Configuring the network bridges"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:398
+# 87f57c9a5f394d4f9d55876ad8bbf7b5
+msgid "It depends on the distribution you are using how to configure these, below you'll find examples for RHEL/CentOS and Ubuntu."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:402
+# 66be5e9df4cc4265a1e9b7b608fe271a
+msgid "The goal is to have two bridges called 'cloudbr0' and 'cloudbr1' after this section. This should be used as a guideline only. The exact configuration will depend on your network layout."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:408
+# 77f72e31b31c4ff48abfeab14d5c4b81
+msgid "Configure in RHEL or CentOS"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:410
+# 5cd8006226944c75823d3fc69513965f
+msgid "The required packages were installed when libvirt was installed, we can proceed to configuring the network."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:413
+# 3c73eb0802d2412eba4716e54ae34079
+msgid "First we configure eth0"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:419
+# 19f74e9662c943b2b0d717aa2d8e80bf
+msgid "Make sure it looks similar to:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:430
+# e751abe2e0124ba9b0f542abd413a2d0
+msgid "We now have to configure the three VLAN interfaces:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:479
+# 821a8f3fb92d431e8be2f46a196c35bb
+msgid "Now we have the VLAN interfaces configured we can add the bridges on top of them."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:486
+# 755eeca19e1e4bd98aff0dd3a0c00845
+msgid "Now we just configure it is a plain bridge without an IP-Address"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:499
+# b04314407fb64b85844b09abb048169b
+msgid "We do the same for cloudbr1"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:516
+#: ../../hypervisor/lxc.rst:566
+# ec7d49c23ca9494d9ae4d1fd87a835cb
+# 3495886017224d39aa2c595d960a7ef1
+msgid "With this configuration you should be able to restart the network, although a reboot is recommended to see if everything works properly."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:520
+#: ../../hypervisor/lxc.rst:570
+# 3b0ccd039c8d42b4a0e5d7b35d533763
+# 16b5ca319946407fb1a833f3f566ad4c
+msgid "Make sure you have an alternative way like IPMI or ILO to reach the machine in case you made a configuration error and the network stops functioning!"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:525
+# 33fce556fd75408baf0d8f252c1c4aa9
+msgid "Configure in Ubuntu"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:527
+# 57356f0b3a6b48878fc6cc570d10d516
+msgid "All the required packages were installed when you installed libvirt, so we only have to configure the network."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:534
+# bde1178e96404b77bb9b9c18c923aa2e
+msgid "Modify the interfaces file to look like this:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:575
+# d5065122bf4a4f5c83dedf6baa1c2306
+msgid "Configuring the firewall"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:577
+# 2749450a561548e3b39d03e1a9af0672
+msgid "The hypervisor needs to be able to communicate with other hypervisors and the management server needs to be able to reach the hypervisor."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:580
+# c76bea5d16c743f88d76b477d69bf172
+msgid "In order to do so we have to open the following TCP ports (if you are using a firewall):"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:583
+# e0a0a271492c47a0b549ec0fa2319108
+msgid "22 (SSH)"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:585
+# 0d0046b470a24b35a6bbbb93e416d8ea
+msgid "1798"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:587
+# 9d1fa0fdb4ef48c0ad4b41556ca20e9d
+msgid "16509 (libvirt)"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:589
+# e5d29bf0b5604b418180606c2d4826e4
+msgid "5900 - 6100 (VNC consoles)"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:591
+# 53bdbd256dd44308a212a48b8de7be9c
+msgid "49152 - 49216 (libvirt live migration)"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:593
+# e1b82341b7f14145ae2b1be829bcdf18
+msgid "It depends on the firewall you are using how to open these ports. Below you'll find examples how to open these ports in RHEL/CentOS and Ubuntu."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:598
+# eadaeb9bb6514298924b9fb479ddb280
+msgid "Open ports in RHEL/CentOS"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:600
+# dbd7938f1a764dfe9159e9eaa1119863
+msgid "RHEL and CentOS use iptables for firewalling the system, you can open extra ports by executing the following iptable commands:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:623
+# d20a63121d8d4a90b51c2e5eb1dc1b8e
+msgid "These iptable settings are not persistent accross reboots, we have to save them first."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:632
+# 43b24147a3aa400f940581bae2f54fb3
+msgid "Open ports in Ubuntu"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:634
+# dbd52c7373bd40008b953dc3d9b13496
+msgid "The default firewall under Ubuntu is UFW (Uncomplicated FireWall), which is a Python wrapper around iptables."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:637
+# 34381e08303c46de9cb9a2ba59cc3026
+msgid "To open the required ports, execute the following commands:"
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:660
+# 36b32007e54b471f951bbd763f7a7d04
+msgid "By default UFW is not enabled on Ubuntu. Executing these commands with the firewall disabled does not enable the firewall."
+msgstr ""
+
+#: ../../hypervisor/lxc.rst:665
+# 1f96f5667281430689c6573d520ffbbc
+msgid "Add the host to CloudStack"
+msgstr ""
+
diff --git a/source/installguide/locale/pot/hypervisor/vsphere.pot b/source/installguide/locale/pot/hypervisor/vsphere.pot
new file mode 100644
index 0000000..2935e3a
--- /dev/null
+++ b/source/installguide/locale/pot/hypervisor/vsphere.pot
@@ -0,0 +1,1681 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../hypervisor/vsphere.rst:18
+# 19b014507cf143c0bfc2d6b2fdbeca56
+msgid "VMware vSphere Installation and Configuration"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:20
+# 87c85380b4b94a7393cc229882265b58
+msgid "If you want to use the VMware vSphere hypervisor to run guest virtual machines, install vSphere on the host(s) in your cloud."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:25
+# 3d2c763f10b74d00ae6672f6d8a6ee22
+msgid "System Requirements for vSphere Hosts"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:29
+# a69a6b7374d64da3a42115a99aad0d8e
+msgid "Software requirements:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:31
+# 817453f34d1d4ce7adcd829ee2c4469e
+msgid "vSphere and vCenter, both version 4.1 or 5.0."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:33
+# 307a9f42a4ba44c4ae53ae2a46440a92
+msgid "vSphere Standard is recommended. Note however that customers need to consider the CPU constraints in place with vSphere licensing. See `http://www.vmware.com/files/pdf/vsphere\\_pricing.pdf <http://www.vmware.com/files/pdf/vsphere_pricing.pdf>`_ and discuss with your VMware sales representative."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:39
+# 0f24943e5a384c2fb7c8d181a5df1d27
+msgid "vCenter Server Standard is recommended."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:41
+# 11cf8def2a0e4ca6b35b4141c27541d3
+msgid "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."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:51
+# 433a750f49e34f96a6568a12d3d5fd74
+msgid "Apply All Necessary Hotfixes. The lack of up-do-date hotfixes can lead to data corruption and lost VMs."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:56
+# cfbe010033704d72879d2e1a83fd3751
+msgid "Hardware requirements:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:58
+# b0649e717356409293c4567e656821af
+msgid "The host must be certified as compatible with vSphere. See the VMware Hardware Compatibility Guide at `http://www.vmware.com/resources/compatibility/search.php <http://www.vmware.com/resources/compatibility/search.php>`_."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:63
+# 7bc3ed3794fb40418371381be3db54c4
+msgid "All hosts must be 64-bit and must support HVM (Intel-VT or AMD-V enabled)."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:66
+# 0a5dabc432dc454396baf7e656897fe6
+msgid "All hosts within a cluster must be homogenous. That means the CPUs must be of the same type, count, and feature flags."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:69
+# 94cea4d65ee249be9661ee4a95356c3d
+msgid "64-bit x86 CPU (more cores results in better performance)"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:71
+# f25b466cb54f42b58faa3675162df14f
+msgid "Hardware virtualization support required"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:73
+# 3eedde6532fd4545af478f114efb0aa6
+msgid "4 GB of memory"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:75
+# 23b705dbe90b4ffda152518b41ce6fee
+msgid "36 GB of local disk"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:77
+# 1e1c717f723448de883b57b168c19a59
+msgid "At least 1 NIC"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:79
+# 3bc46abe138d48eeb9586740ba9e5d00
+msgid "Statically allocated IP Address"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:83
+# adf685e0308e4394aceccfcdb1c3e923
+msgid "vCenter Server requirements:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:85
+# 06ac32e7e8c04f65b302040e55a2a908
+msgid "Processor - 2 CPUs 2.0GHz or higher Intel or AMD x86 processors. Processor requirements may be higher if the database runs on the same machine."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:89
+# 271c70d35c104435b5350721391ffed9
+msgid "Memory - 3GB RAM. RAM requirements may be higher if your database runs on the same machine."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:92
+# 720bf6b73cd1449fb7ae868c3286012c
+msgid "Disk storage - 2GB. Disk requirements may be higher if your database runs on the same machine."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:95
+# 6f4ab896b8f049448d2141390cd6e6cb
+msgid "Microsoft SQL Server 2005 Express disk requirements. The bundled database requires up to 2GB free disk space to decompress the installation archive."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:99
+# 9474159ca7834a10864479073a1bf0d3
+msgid "Networking - 1Gbit or 10Gbit."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:101
+# 38899761f45d434f8c9fb7a5d24ec00e
+msgid "For more information, see `\"vCenter Server and the vSphere Client Hardware Requirements\" <http://pubs.vmware.com/vsp40/wwhelp/wwhimpl/js/html/wwhelp.htm#href=install/c_vc_hw.html>`_."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:106
+# 43340509b56641c28387c6a0b718a9a2
+msgid "Other requirements:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:108
+# c0ca168c59964efc9aa79369ee7a8104
+msgid "VMware vCenter Standard Edition 4.1 or 5.0 must be installed and available to manage the vSphere hosts."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:111
+# 0ba8fe6d64854dac84850796d0c84f0b
+msgid "vCenter must be configured to use the standard port 443 so that it can communicate with the CloudStack Management Server."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:114
+# 311e91fb341e4d30a649ba13d80e2e72
+msgid "You must re-install VMware ESXi if you are going to re-use a host from a previous install."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:117
+# c5dcee58723d4fa1b707fecaede37c0e
+msgid "CloudStack requires VMware vSphere 4.1 or 5.0. VMware vSphere 4.0 is not supported."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:120
+# d988a28be0c94e3b9935e2025d0475d0
+msgid "All hosts must be 64-bit and must support HVM (Intel-VT or AMD-V enabled). All hosts within a cluster must be homogeneous. That means the CPUs must be of the same type, count, and feature flags."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:124
+# f830e27a969e413b831620b0907e346f
+msgid "The CloudStack management network must not be configured as a separate virtual network. The CloudStack management network is the same as the vCenter management network, and will inherit its configuration. See :ref:`configure-vcenter-management-network`."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:129
+# eac2d87ef82b4063864397fe3ac48213
+msgid "CloudStack requires ESXi. ESX is not supported."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:131
+# 397732aa4a884edbab1fec4290fceae4
+msgid "All resources used for CloudStack must be used for CloudStack only. CloudStack cannot share instance of ESXi or storage with other management consoles. Do not share the same storage volumes that will be used by CloudStack with a different set of ESXi servers that are not managed by CloudStack."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:137
+# 483d1d73b54a40d78329af14748fd831
+msgid "Put all target ESXi hypervisors in a cluster in a separate Datacenter in vCenter."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:140
+# 8151eb61ba874bc8a60d05b0c751a321
+msgid "The cluster that will be managed by CloudStack should not contain any VMs. Do not run the management server, vCenter or any other VMs on the cluster that is designated for CloudStack use. Create a separate cluster for use of CloudStack and make sure that they are no VMs in this cluster."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:146
+# 2bcc13091d3947dc9e7801b766452c80
+msgid "All the required VLANS must be trunked into all network switches that are connected to the ESXi hypervisor hosts. These would include the VLANS for Management, Storage, vMotion, and guest VLANs. The guest VLAN (used in Advanced Networking; see Network Setup) is a contiguous range of VLANs that will be managed by CloudStack."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:154
+# 12d708e9230b4cf2a6eec95bc47de138
+msgid "Preparation Checklist for VMware"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:156
+# f9a24ff6b44f49d198fbee57859227b1
+msgid "For a smoother installation, gather the following information before you start:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:159
+# 7c40a197d95543d5b09db63ac46a3ff7
+msgid "Information listed in :ref:`vcenter-checklist`"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:161
+# 985e27ff41074586a10f90781fc9434b
+msgid "Information listed in :ref:`networking-checklist-for-vmware`"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:167
+# 7bbac620f96b4b238ced330b74d07b49
+msgid "vCenter Checklist"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:169
+# 04e3ab33127443328f019f7d08a250d6
+msgid "You will need the following information about vCenter."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:172
+# 230ef95a22cb40c2ac102a9798f69d50
+msgid "vCenter Requirement"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:172
+#: ../../hypervisor/vsphere.rst:189
+#: ../../hypervisor/vsphere.rst:459
+# 52d76ece5b4a44309c219d371f7ddd03
+# 82bd8117216b4dec8f2d3946d40f445c
+# 28ee056cc5ba4ffa9d14464a46e34f3a
+msgid "Notes"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:174
+# e6d6093156eb4c89a795c492963fceed
+msgid "vCenter User"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:174
+# 55d86b0382d0488e9e1392ae0a228a03
+msgid "This user must have admin privileges."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:175
+# 21fb181b5dc444fd8fd758ae9a39ba95
+msgid "vCenter User Password"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:175
+# 6be77420b0d6471a926b242982798b63
+msgid "Password for the above user."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:176
+# 79ba83eb3964471ba6ea6718fde7cb34
+msgid "vCenter Datacenter Name"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:176
+# 2fd0d6ea1f9a4c85b81d4276deb2c9b8
+msgid "Name of the datacenter."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:177
+# 3150bf92a4a347e5aa40a8fe765140b6
+msgid "vCenter Cluster Name"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:177
+# 4da7406ee21a41999d49265263a3d330
+msgid "Name of the cluster."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:184
+# f06da8e5f04e4715a3428b02687006a5
+msgid "Networking Checklist for VMware"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:186
+# 0b5d8b8b8030478490415117b971cc1d
+msgid "You will need the following information about VLAN."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:189
+# d18a8dbf3b5a4e37a6b4a9082e8d9b9a
+msgid "VLAN Information"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:191
+# a18ba1020be54125a1a83ecae1b4a59d
+msgid "ESXi VLAN"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:191
+# 7552379727114564bb1a6005a0bc0b5a
+msgid "VLAN on which all your ESXi hypervisors reside."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:192
+# 94167adee63f4adda49e8511ecf154c2
+msgid "ESXI VLAN IP Address"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:192
+# 96b5d173daa14cb686b8df6e2af6eda3
+msgid "IP Address Range in the ESXi VLAN. One address per Virtual Router is used from this range."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:193
+# 61a0a647d1304c7592fee8b73395ac5e
+msgid "ESXi VLAN IP Gateway"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:194
+# 502e2adfefd54290b787aba3d70a6a3c
+msgid "ESXi VLAN Netmask"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:195
+# 3d862fcd0d14490fb29acd36a2958c5d
+msgid "Management Server VLAN"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:195
+# ce8231bbfb6f4f86b212bfa7912ce3fb
+msgid "VLAN on which the CloudStack Management server is installed."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:196
+# 924ddf7763994ebfbd0a15b603bc22d5
+msgid "Public VLAN"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:196
+# 3f3fdc9789c048b49167a98f52acc5dc
+msgid "VLAN for the Public Network."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:197
+# ee0b4346c9ad482786c589e1947e8ce8
+msgid "Public VLAN Gateway"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:198
+# 093927bfb8494060b58a6be1d37571a3
+msgid "Public VLAN Netmask"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:199
+# 48b1d1223c1942f486b2e81fd85701ba
+msgid "Public VLAN IP Address Range"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:199
+# fafd189f95f0456fa23cbebd9f3ed266
+msgid "Range of Public IP Addresses available for CloudStack use. These addresses will be used for virtual router on CloudStack to route private traffic to external networks."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:202
+# 8eb456b1619c4753be00cf585593cc7e
+msgid "VLAN Range for Customer use"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:202
+# dad2013c354145e5b820dc70ef56e99c
+msgid "A contiguous range of non-routable VLANs. One VLAN will be assigned for each customer."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:208
+# 55066669b6874439b121073b06ac7faa
+msgid "vSphere Installation Steps"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:210
+# 9254e8523b3f4c3aad496a3e1776451f
+msgid "If you haven't already, you'll need to download and purchase vSphere from the VMware Website (`https://www.vmware.com/tryvmware/index.php?p=vmware-vsphere&lp=1 <https://www.vmware.com/tryvmware/index.php?p=vmware-vsphere&lp=1>`_) and install it by following the VMware vSphere Installation Guide."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:215
+# b9235024292f46faacee1b73c71ce9c9
+msgid "Following installation, perform the following configuration, which are described in the next few sections:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:219
+# 10d7af3e4cef499aa1fa230b12ce67e0
+msgid "Required"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:219
+# 906de2717fd64b5c87584e6807af120e
+msgid "Optional"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:221
+# b461abbf9e42401da9600e4666054caa
+msgid "ESXi host setup"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:221
+# a672baaf4ca64f66ba7b0a4aa2b9c820
+msgid "NIC bonding"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:222
+# 15b07c50f2814ef5a9b9fe3e6054c7ef
+msgid "Configure host physical networking,virtual switch, vCenter Management Network, and extended port range"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:222
+# 82afddb1d1534689ac6a034abc9ad969
+msgid "Multipath storage"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:223
+# 908c7c0df32a4091b51fa92198fd58da
+msgid "Prepare storage for iSCSI"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:224
+# a92c6507ae414e5f9a0ec8ff2545209e
+msgid "Configure clusters in vCenter and add hosts to them, or add hosts without clusters to vCenter"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:229
+# a5fd230588934d9a949707390d10c3cd
+msgid "ESXi Host setup"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:231
+# 4560ac7e0a014d70bbfe865d8cd78abd
+msgid "All ESXi hosts should enable CPU hardware virtualization support in BIOS. Please note hardware virtualization support is not enabled by default on most servers."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:237
+# 4ecccb36e87644d3a98414f9f939fdc5
+msgid "Physical Host Networking"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:239
+# 24de9cbfdd0a4277a359684f50fb2ca7
+msgid "You should have a plan for cabling the vSphere hosts. Proper network configuration is required before adding a vSphere host to CloudStack. To configure an ESXi host, you can use vClient to add it as standalone host to vCenter first. Once you see the host appearing in the vCenter inventory tree, click the host node in the inventory tree, and navigate to the Configuration tab."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:246
+# 1221f7c6183a439e9db5dfe5282e491a
+msgid "|vspherephysicalnetwork.png: vSphere client|"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:248
+# 814e620809104bd1bd43c8b8d28445ad
+msgid "In the host configuration tab, click the \"Hardware/Networking\" link to bring up the networking configuration page as above."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:253
+# 6bb1a1da1840400f9cd0ea1a73f0c12a
+msgid "Configure Virtual Switch"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:255
+# b867b4246fc449979584e901e0fac0fb
+msgid "A default virtual switch vSwitch0 is created. CloudStack requires all ESXi hosts in the cloud to use the same set of virtual switch names. If you change the default virtual switch name, you will need to configure one or more CloudStack configuration variables as well."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:262
+# cfa8f6a17984452ba1aabf882f8c3d42
+msgid "Separating Traffic"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:264
+# 69b7df288a684ae0b55024da82f5e8fc
+msgid "CloudStack allows you to use vCenter to configure three separate networks per ESXi host. These networks are identified by the name of the vSwitch they are connected to. The allowed networks for configuration are public (for traffic to/from the public internet), guest (for guest-guest traffic), and private (for management and usually storage traffic). You can use the default virtual switch for all three, or create one or two other vSwitches for those traffic types."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:272
+# bf95ebb6ddf44a5cbf07c996d8a660f3
+msgid "If you want to separate traffic in this way you should first create and configure vSwitches in vCenter according to the vCenter instructions. Take note of the vSwitch names you have used for each traffic type. You will configure CloudStack to use these vSwitches."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:279
+# bc3f5581dea54034ae73ec0a942e180c
+msgid "Increasing Ports"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:281
+# 88f709156fa8484b902282de91c0793f
+msgid "By default a virtual switch on ESXi hosts is created with 56 ports. We recommend setting it to 4088, the maximum number of ports allowed. To do that, click the \"Properties...\" link for virtual switch (note this is not the Properties link for Networking)."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:286
+# 4e01bfffde3c422aa7fcdddc74de892f
+msgid "|vsphereincreaseports.png: vSphere client|"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:288
+# 11994bd16f5a45a383d33894daaa0f53
+msgid "In vSwitch properties dialog, select the vSwitch and click Edit. You should see the following dialog:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:291
+# f64cba4600314bd89382d82cd5d37e5a
+msgid "|vspherevswitchproperties.png: vSphere client|"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:293
+# 5216577220b34c2980dadbd02476e716
+msgid "In this dialog, you can change the number of switch ports. After you've done that, ESXi hosts are required to reboot in order for the setting to take effect."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:301
+# 0ad4145d13e84c828a62f3d1b613dbd3
+msgid "Configure vCenter Management Network"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:303
+# 55856f0ddbed407eae0a6e859a61f73d
+msgid "In the vSwitch properties dialog box, you may see a vCenter management network. This same network will also be used as the CloudStack management network. CloudStack requires the vCenter management network to be configured properly. Select the management network item in the dialog, then click Edit."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:309
+# 07fa2b72b0564cb89199ffcab114a7ee
+msgid "|vspheremgtnetwork.png: vSphere client|"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:311
+# 00017c3e4d5e4506808936e3c52b70fd
+msgid "Make sure the following values are set:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:313
+# 383a238254dd4a109140ddd990c2ced7
+msgid "VLAN ID set to the desired ID"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:315
+# 92318eb7b2c544b08843c50e90bfb36c
+msgid "vMotion enabled."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:317
+# d6f57109f2fa4226a9ff5372703acb79
+msgid "Management traffic enabled."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:319
+# 44d67b07355843239d874a52581251b0
+msgid "If the ESXi hosts have multiple VMKernel ports, and ESXi is not using the default value \"Management Network\" as the management network name, you must follow these guidelines to configure the management network port group so that CloudStack can find it:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:324
+# 9bb53b01739a4056995c0d4a8ca8d472
+msgid "Use one label for the management network port across all ESXi hosts."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:326
+# 9a73da845a73437891672f0ca961eba4
+msgid "In the CloudStack UI, go to Configuration - Global Settings and set vmware.management.portgroup to the management network label from the ESXi hosts."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:332
+# b6695dde2a9e4023ab181aa0b7f43ddf
+msgid "Extend Port Range for CloudStack Console Proxy"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:334
+# 8acd9f9a7fd74d82b305dd73462cb96d
+msgid "(Applies only to VMware vSphere version 4.x)"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:336
+# 3ca5d828266843f981f791b128eaa6a4
+msgid "You need to extend the range of firewall ports that the console proxy works with on the hosts. This is to enable the console proxy to work with VMware-based VMs. The default additional port range is 59000-60000. To extend the port range, log in to the VMware ESX service console on each host and run the following commands:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:349
+# 1f25aa96ef604ce8acd3ae301b49add1
+msgid "Configure NIC Bonding for vSphere"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:351
+# b3ba21794a784430bc2e6d8755c2a5d6
+msgid "NIC bonding on vSphere hosts may be done according to the vSphere installation guide."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:356
+# 57eca85918594e28af92c0453eb88f9e
+msgid "Configuring a vSphere Cluster with Nexus 1000v Virtual Switch"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:358
+# c41be8a6fd7a495a9f3fc72a6f572fc1
+msgid "CloudStack supports Cisco Nexus 1000v dvSwitch (Distributed Virtual Switch) for virtual network configuration in a VMware vSphere environment. This section helps you configure a vSphere cluster with Nexus 1000v virtual switch in a VMware vCenter environment. For information on creating a vSphere cluster, see `\"VMware vSphere Installation and Configuration\" <#vmware-vsphere-installation-and-configuration>`_"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:368
+# fd98cbd7bb554d358747d066d0beb7ec
+msgid "About Cisco Nexus 1000v Distributed Virtual Switch"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:370
+# 59712fc0b9b3480680eab3fc5438d7d6
+msgid "The Cisco Nexus 1000V virtual switch is a software-based virtual machine access switch for VMware vSphere environments. It can span multiple hosts running VMware ESXi 4.0 and later. A Nexus virtual switch consists of two components: the Virtual Supervisor Module (VSM) and the Virtual Ethernet Module (VEM). The VSM is a virtual appliance that acts as the switch's supervisor. It controls multiple VEMs as a single network device. The VSM is installed independent of the VEM and is deployed in redundancy mode as pairs or as a standalone appliance. The VEM is installed on each VMware ESXi server to provide packet-forwarding capability. It provides each virtual machine with dedicated switch ports. This VSM-VEM architecture is analogous to a physical Cisco switch's supervisor (standalone or configured in high-availability mode) and multiple linecards architecture."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:384
+# f739316e27a14ab39ad8ab22ae8e3d33
+msgid "Nexus 1000v switch uses vEthernet port profiles to simplify network provisioning for virtual machines. There are two types of port profiles: Ethernet port profile and vEthernet port profile. The Ethernet port profile is applied to the physical uplink ports-the NIC ports of the physical NIC adapter on an ESXi server. The vEthernet port profile is associated with the virtual NIC (vNIC) that is plumbed on a guest VM on the ESXi server. The port profiles help the network administrators define network policies which can be reused for new virtual machines. The Ethernet port profiles are created on the VSM and are represented as port groups on the vCenter server."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:397
+#: ../../hypervisor/vsphere.rst:715
+# de9fe88270bf4403afa9e22b05f73471
+# 5d365a93c5e949efb76d86e0763cbad3
+msgid "Prerequisites and Guidelines"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:399
+# 7c2f20207c414d7d819f7e0e5d408552
+msgid "This section discusses prerequisites and guidelines for using Nexus virtual switch in CloudStack. Before configuring Nexus virtual switch, ensure that your system meets the following requirements:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:403
+# 6069bf189abd4043952218eb4c6136a7
+msgid "A cluster of servers (ESXi 4.1 or later) is configured in the vCenter."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:406
+# f86fc439aeb543e4a45e2c8bbdfd9510
+msgid "Each cluster managed by CloudStack is the only cluster in its vCenter datacenter."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:409
+# 26d3882e3f964a7ba7e2079ae88133a1
+msgid "A Cisco Nexus 1000v virtual switch is installed to serve the datacenter that contains the vCenter cluster. This ensures that CloudStack doesn't have to deal with dynamic migration of virtual adapters or networks across other existing virtual switches. See `Cisco Nexus 1000V Installation and Upgrade Guide <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_5_1/install_upgrade/vsm_vem/guide/n1000v_installupgrade.html>`_ for guidelines on how to install the Nexus 1000v VSM and VEM modules."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:417
+# 985ff8e2082f419d8d77119acefbfa01
+msgid "The Nexus 1000v VSM is not deployed on a vSphere host that is managed by CloudStack."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:420
+# affd3445b0854e7ab5ffbef4fa7b9db4
+msgid "When the maximum number of VEM modules per VSM instance is reached, an additional VSM instance is created before introducing any more ESXi hosts. The limit is 64 VEM modules for each VSM instance."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:424
+# e95f2908159b4be0820e8620c94c70c5
+msgid "CloudStack expects that the Management Network of the ESXi host is configured on the standard vSwitch and searches for it in the standard vSwitch. Therefore, ensure that you do not migrate the management network to Nexus 1000v virtual switch during configuration."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:430
+# 7f74225fb2604754a58806809f2c65c1
+msgid "All information given in :ref:`nexus-vswift-preconf`"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:436
+# 0ab3b61d4a674fb5ba50354f165cf6e9
+msgid "Nexus 1000v Virtual Switch Preconfiguration"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:439
+#: ../../hypervisor/vsphere.rst:737
+# 2af119d57464425ea16e15da99bba2c2
+# 6067502710ad439c97b2463c8710b803
+msgid "Preparation Checklist"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:441
+# 70d29993a857439d8efb48c089332053
+msgid "For a smoother configuration of Nexus 1000v switch, gather the following information before you start:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:444
+# 12d946312911404db67cdfccc6dcfe14
+msgid "vCenter credentials"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:446
+# 568485eb210d406098935f8d5ab9b909
+msgid "Nexus 1000v VSM IP address"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:448
+# a593926b86d04d3a8de54de3c70a9174
+msgid "Nexus 1000v VSM Credentials"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:450
+# ff2a8c3138eb40fbbb40579586e678bf
+msgid "Ethernet port profile names"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:454
+# 4a63ecb799f24c29a04447e5da4130a5
+msgid "vCenter Credentials Checklist"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:456
+# 12069bcb02154859beac5cf397ecee61
+msgid "You will need the following information about vCenter:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:459
+# b2dc772426244f1f87b143366ecfd94a
+msgid "Nexus vSwitch Requirements"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:459
+# ca1d082b962346c5b7e77314fa8f5339
+msgid "Value"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:461
+# 3e9df2480b0d45c7a1888a94ab74b561
+msgid "vCenter IP"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:461
+# 799d10a2870e4192b304caa3220a3c8c
+msgid "The IP address of the vCenter."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:462
+# 373aace450dd4118b5260a922177871d
+msgid "Secure HTTP Port Number"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:462
+# bf406db42c3b4a0985b822dc6f559fe9
+msgid "443"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:462
+# 78925de645d8445ab775646afbe88bac
+msgid "Port 443 is configured by default; however, you can change the port if needed."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:463
+# 7130dcb862384a349e76cb8cd106e8e2
+msgid "vCenter User ID"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:463
+# 3c850f22d89f4e009b761127783ecdbd
+msgid "The vCenter user with administrator-level privileges. The vCenter User ID is required when you configure the virtual switch in CloudStack."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:465
+#: ../../hypervisor/vsphere.rst:658
+#: ../../hypervisor/vsphere.rst:870
+# 12125993392649a481f3650dc5288a6e
+# 0bd5bef46f9b4c6094ac26305cdfaa3f
+# aa87c00699724716b0aee7487275d581
+msgid "vCenter Password"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:465
+# 0e4340b43fb04f7891cf7c7acc4ec52d
+msgid "The password for the vCenter user specified above. The password for this vCenter user is required when you configure the switch in CloudStack."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:471
+# c78db2020a3c495b810c84656515f5a0
+msgid "Network Configuration Checklist"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:473
+# 8685bc23de794287bde9bc32baf13f10
+msgid "The following information specified in the Nexus Configure Networking screen is displayed in the Details tab of the Nexus dvSwitch in the CloudStack UI:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:477
+# 5ecd7125924d4e3291abfd544471236f
+msgid "**Control Port Group VLAN ID** The VLAN ID of the Control Port Group. The control VLAN is used for communication between the VSM and the VEMs."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:481
+# 5f52a9e500cc4927a981a052e73bac88
+msgid "**Management Port Group VLAN ID** The VLAN ID of the Management Port Group. The management VLAN corresponds to the mgmt0 interface that is used to establish and maintain the connection between the VSM and VMware vCenter Server."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:486
+# 709fb407f7f7478ea5db1f47f795d42e
+msgid "**Packet Port Group VLAN ID** The VLAN ID of the Packet Port Group. The packet VLAN forwards relevant data packets from the VEMs to the VSM."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:491
+# ee94ad5da5e44bd8a01b0a8b8d1f08f7
+msgid "The VLANs used for control, packet, and management port groups can be the same."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:494
+# 1d2af92735dc4899b13bb4fc697442f3
+msgid "For more information, see `Cisco Nexus 1000V Getting Started Guide <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_b/getting_started/configuration/guide/n1000v_gsg.pdf>`_."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:499
+# a9b85e88b0e54ef7bfa6227318fcadd8
+msgid "VSM Configuration Checklist"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:501
+# 409e4da026e84021900be9e9944f3530
+msgid "You will need the following VSM configuration parameters:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:503
+# b2c7beaf3b174e24ae88c155d2eaf8bb
+msgid "**Admin Name and Password** The admin name and password to connect to the VSM appliance. You must specify these credentials while configuring Nexus virtual switch."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:507
+# c42b39990d6e4d0589467d0a4ff5be4c
+msgid "**Management IP Address** This is the IP address of the VSM appliance. This is the IP address you specify in the virtual switch IP Address field while configuting Nexus virtual switch."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:512
+# 26a1722f2c004284958a7d40035272d8
+msgid "**SSL** Should be set to Enable.Always enable SSL. SSH is usually enabled by default during the VSM installation. However, check whether the SSH connection to the VSM is working, without which CloudStack failes to connect to the VSM."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:519
+# 62e601792f00490dbb068dab317eacb1
+msgid "Creating a Port Profile"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:521
+# 4c8ad78e43824c658d06ce2ab03a001f
+msgid "Whether you create a Basic or Advanced zone configuration, ensure that you always create an Ethernet port profile on the VSM after you install it and before you create the zone."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:525
+# 7208a4d7c533445d986522ab1512d4bf
+msgid "The Ethernet port profile created to represent the physical network or networks used by an Advanced zone configuration trunk all the VLANs including guest VLANs, the VLANs that serve the native VLAN, and the packet/control/data/management VLANs of the VSM."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:531
+# a8f769a137704cb5b1e211dbd40311d3
+msgid "The Ethernet port profile created for a Basic zone configuration does not trunk the guest VLANs because the guest VMs do not get their own VLANs provisioned on their network interfaces in a Basic zone."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:536
+# e5eb4252f80244b298e78778099d1fc0
+msgid "An Ethernet port profile configured on the Nexus 1000v virtual switch should not use in its set of system VLANs, or any of the VLANs configured or intended to be configured for use towards VMs or VM resources in the CloudStack environment."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:541
+# d75d1e3b4d5e4861816052de95cd1077
+msgid "You do not have to create any vEthernet port profiles – CloudStack does that during VM deployment."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:544
+# defb84f8c1a843f49799fb10a14be23e
+msgid "Ensure that you create required port profiles to be used by CloudStack for different traffic types of CloudStack, such as Management traffic, Guest traffic, Storage traffic, and Public traffic. The physical networks configured during zone creation should have a one-to-one relation with the Ethernet port profiles."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:550
+# 0e5328f3a23c4e29bfca23e34fcf89e4
+msgid "|vmwarenexusportprofile.png: vSphere client|"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:552
+# 70e2a8e74f5a4a1f9e0541bf48f85614
+msgid "For information on creating a port profile, see `Cisco Nexus 1000V Port Profile Configuration Guide <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_a/port_profile/configuration/guide/n1000v_port_profile.html>`_."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:558
+# 0bf9d88c6b9f41fd886a6707af18171a
+msgid "Assigning Physical NIC Adapters"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:560
+# af30a3508a1749d78432b57d276bbdb3
+msgid "Assign ESXi host's physical NIC adapters, which correspond to each physical network, to the port profiles. In each ESXi host that is part of the vCenter cluster, observe the physical networks assigned to each port profile and note down the names of the port profile for future use. This mapping information helps you when configuring physical networks during the zone configuration on CloudStack. These Ethernet port profile names are later specified as VMware Traffic Labels for different traffic types when configuring physical networks during the zone configuration. For more information on configuring physical networks, see `\"Configuring a vSphere Cluster with Nexus 1000v Virtual Switch\" <#configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch>`_."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:574
+# 4d643ffbee4341e4bb88d373ef58d4cb
+msgid "Adding VLAN Ranges"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:576
+# baf83061abab4c29997a363586a2456f
+msgid "Determine the public VLAN, System VLAN, and Guest VLANs to be used by the CloudStack. Ensure that you add them to the port profile database. Corresponding to each physical network, add the VLAN range to port profiles. In the VSM command prompt, run the switchport trunk allowed vlan<range> command to add the VLAN ranges to the port profile."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:582
+#: ../../hypervisor/vsphere.rst:597
+# a2316a806eeb4659aee14888d7a2fdac
+# 4709d5c62ddc4858afce5f4c10779904
+msgid "For example:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:588
+# b6f0345378ec46c3b728d82ee05d286b
+msgid "In this example, the allowed VLANs added are 1, 140-147, and 196-203"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:590
+# 11887130246943b5831c94500ad2baf5
+msgid "You must also add all the public and private VLANs or VLAN ranges to the switch. This range is the VLAN range you specify in your zone."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:594
+# 330d6aad437046f89b9b68dd7beeb679
+msgid "Before you run the vlan command, ensure that the configuration mode is enabled in Nexus 1000v virtual switch."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:599
+# 22f63b04c60d40dea935e52d90e87e7e
+msgid "If you want the VLAN 200 to be used on the switch, run the following command:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:606
+# ba4c025b07cf4124a3cdd1f31a23eb96
+msgid "If you want the VLAN range 1350-1750 to be used on the switch, run the following command:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:613
+# c199b4ffbd1f477285c999898c2ddd1d
+msgid "Refer to Cisco Nexus 1000V Command Reference of specific product version."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:618
+# fef738594c2b491dba8d52bd4a2af5c6
+msgid "Enabling Nexus Virtual Switch in CloudStack"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:620
+# d5d3e75b340e49b59882b4fd17efbeee
+msgid "To make a CloudStack deployment Nexus enabled, you must set the vmware.use.nexus.vswitch parameter true by using the Global Settings page in the CloudStack UI. Unless this parameter is set to \"true\" and restart the management server, you cannot see any UI options specific to Nexus virtual switch, and CloudStack ignores the Nexus virtual switch specific parameters specified in the AddTrafficTypeCmd, UpdateTrafficTypeCmd, and AddClusterCmd API calls."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:628
+# 66954393333444d693e53f7f88f33806
+msgid "Unless the CloudStack global parameter \"vmware.use.nexus.vswitch\" is set to \"true\", CloudStack by default uses VMware standard vSwitch for virtual network infrastructure. In this release, CloudStack doesn’t support configuring virtual networks in a deployment with a mix of standard vSwitch and Nexus 1000v virtual switch. The deployment can have either standard vSwitch or Nexus 1000v virtual switch."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:637
+# 089aca1a3d354287b5a5f5e3e85a6ac4
+msgid "Configuring Nexus 1000v Virtual Switch in CloudStack"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:639
+# 9a68575001b243859acad74ffa452cb3
+msgid "You can configure Nexus dvSwitch by adding the necessary resources while the zone is being created."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:642
+# 08ba8e10fe624f36bab2f344bcbfdc6d
+msgid "|vmwarenexusaddcluster.png: vmware nexus add cluster|"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:644
+# 5666435e9e184603bfede5e1d03e45c9
+msgid "After the zone is created, if you want to create an additional cluster along with Nexus 1000v virtual switch in the existing zone, use the Add Cluster option. For information on creating a cluster, see `\"Add Cluster: vSphere\" <configuration.html#add-cluster-vsphere>`_."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:649
+# 9f2cbaf16fa54d839d9df5ead1a87d4a
+msgid "In both these cases, you must specify the following parameters to configure Nexus virtual switch:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:653
+# f3eae50b0b494bfe81d9c26c4d91d2f6
+msgid "Parameters"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:653
+# 206d2e47feb14f26af5aa0ba5190283d
+msgid "Description"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:655
+#: ../../hypervisor/vsphere.rst:867
+# f3ce0a1026ad443fb1d31fd83fb6fb89
+# d7c8e2c264fb4986bd9ae232d6bdc8da
+msgid "Cluster Name"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:655
+# ec69a6aaa2e74f97902c75e7e75e9414
+msgid "Enter the name of the cluster you created in vCenter. For example,\"cloud.cluster\"."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:656
+#: ../../hypervisor/vsphere.rst:868
+# c1336620763a40f5912677193b00e7d2
+# 5471d0cfd4dd4a1cad1890577ec16d27
+msgid "vCenter Host"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:656
+# 83d4fc5d91a2434b8dbd5e459e856481
+msgid "Enter the host name or the IP address of the vCenter host where you have deployed the Nexus virtual switch."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:657
+#: ../../hypervisor/vsphere.rst:869
+# a59ea53f5ed34aeeae67a62d22d9ef45
+# 50604ed2276e4b07a2245efe817a0e82
+msgid "vCenter User name"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:657
+#: ../../hypervisor/vsphere.rst:869
+# 15cbe8d043134a98844515d429dc2ce4
+# 3d920505b2f94257aa4fae956cce9e60
+msgid "Enter the username that CloudStack should use to connect to vCenter. This user must have all administrative privileges."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:658
+#: ../../hypervisor/vsphere.rst:870
+# 72ddd267d0934d71807a5b8f29fcc40b
+# 3d09dd4ec9ca450ab9b2843f5fe568f7
+msgid "Enter the password for the user named above."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:659
+#: ../../hypervisor/vsphere.rst:871
+# 3455a7e1a6ed43d9a04ca83e129c5605
+# 89d73f2b5187411dbeca10e98407d28a
+msgid "vCenter Datacenter"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:659
+# b8c64f99941045ba939c00ac64b8577e
+msgid "Enter the vCenter datacenter that the cluster is in. For example, \"cloud.dc.VM\"."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:660
+# 2e1f46464eb742eaa8decef9cc02ee1c
+msgid "Nexus dvSwitch IP Address"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:660
+# 0d935b2ec87d43d8ba91c44f85ab3926
+msgid "The IP address of the VSM component of the Nexus 1000v virtual switch."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:661
+# 506b21479dd245b59972e5235fe090f8
+msgid "Nexus dvSwitch Username"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:661
+# 51d92f490444448b97636510fda22234
+msgid "The admin name to connect to the VSM appliance."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:662
+# d1f48e314d0c4a60b778e89e3e5218c7
+msgid "Nexus dvSwitch Password"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:662
+# 2bf18eee4392452e9e2ce45d3f35ffdf
+msgid "The corresponding password for the admin user specified above."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:667
+# cb27a7f0d42d41a5869093a5664932cc
+msgid "Removing Nexus Virtual Switch"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:669
+# 3661bb5b60a640dfb27da936b1ae3f3f
+msgid "In the vCenter datacenter that is served by the Nexus virtual switch, ensure that you delete all the hosts in the corresponding cluster."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:672
+# 72b8f0831f1840fba93593a47a3cb31d
+msgid "Log in with Admin permissions to the CloudStack administrator UI."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:674
+# a6a80236805f46a289eaf13d946c887a
+msgid "In the left navigation bar, select Infrastructure."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:676
+# bf58c4e0621740cfa25ee56a211059e4
+msgid "In the Infrastructure page, click View all under Clusters."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:678
+# 5e2de301945c4c99a089b6d4ccbb97f5
+msgid "Select the cluster where you want to remove the virtual switch."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:680
+# 8d08ef2d67b24e79a1fd91c3b5c80ac6
+msgid "In the dvSwitch tab, click the name of the virtual switch."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:682
+# e8ab3fb5e03a46a8806229a38548cd5e
+msgid "In the Details page, click Delete Nexus dvSwitch icon. |DeleteButton.png: button to delete dvSwitch|"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:685
+# dab3c1f885254b0d8a52701b537c16a1
+msgid "Click Yes in the confirmation dialog box."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:689
+# 5c6a715aab294507b509f8b2c8510cd1
+msgid "Configuring a VMware Datacenter with VMware Distributed Virtual Switch"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:691
+# 9929cd85206a4959b9c3daabc7fab873
+msgid "CloudStack supports VMware vNetwork Distributed Switch (VDS) for virtual network configuration in a VMware vSphere environment. This section helps you configure VMware VDS in a CloudStack deployment. Each vCenter server instance can support up to 128 VDS instances and each VDS instance can manage up to 500 VMware hosts."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:699
+# 90d5b5ea40d340a18482d06a12eab802
+msgid "About VMware Distributed Virtual Switch"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:701
+# d608c0175d0c4cdda5a1cafa7067caab
+msgid "VMware VDS is an aggregation of host-level virtual switches on a VMware vCenter server. VDS abstracts the configuration of individual virtual switches that span across a large number of hosts, and enables centralized provisioning, administration, and monitoring for your entire datacenter from a centralized interface. In effect, a VDS acts as a single virtual switch at the datacenter level and manages networking for a number of hosts in a datacenter from a centralized VMware vCenter server. Each VDS maintains network runtime state for VMs as they move across multiple hosts, enabling inline monitoring and centralized firewall services. A VDS can be deployed with or without Virtual Standard Switch and a Nexus 1000V virtual switch."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:717
+# f8c27f93dc7c49a0b45ea450643011b8
+msgid "VMware VDS is supported only on Public and Guest traffic in CloudStack."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:720
+# 2451bd65c3414c12b60281d4c965ed9e
+msgid "VMware VDS does not support multiple VDS per traffic type. If a user has many VDS switches, only one can be used for Guest traffic and another one for Public traffic."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:724
+# 1a4762ba91d54eb7b6a18b38c7977b88
+msgid "Additional switches of any type can be added for each cluster in the same zone. While adding the clusters with different switch type, traffic labels is overridden at the cluster level."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:728
+# 698c3a1075c44ad6b44b983353e9c5bd
+msgid "Management and Storage network does not support VDS. Therefore, use Standard Switch for these networks."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:731
+# d0e5f6fb89294c3f992992b8be90c4c3
+msgid "When you remove a guest network, the corresponding dvportgroup will not be removed on the vCenter. You must manually delete them on the vCenter."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:739
+# d9ec908d24a74999a2250196f948e921
+msgid "For a smoother configuration of VMware VDS, note down the VDS name you have added in the datacenter before you start:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:742
+# 0285bb1ef7114be98e589ae304a4aaf4
+msgid "|vds-name.png: Name of the dvSwitch as specified in the vCenter.|"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:744
+# a198446dde7b4bb4b8d32ade0d379e5d
+msgid "Use this VDS name in the following:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:746
+# ce7a25d8824b439e989df3a4ec7d6ef4
+msgid "The switch name in the Edit traffic label dialog while configuring a public and guest traffic during zone creation."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:749
+# 93f0bed990174313b9ae6b524fe267f8
+msgid "During a zone creation, ensure that you select VMware vNetwork Distributed Virtual Switch when you configure guest and public traffic type."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:753
+# 5c1aa18eab3146b6a6f65b96c8deaaca
+msgid "|traffic-type.png|"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:755
+# 990772b4742749958e08c6337b848941
+msgid "The Public Traffic vSwitch Type field when you add a VMware VDS-enabled cluster."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:758
+# 5d9ac3f1d63b462e9501e015548b5af0
+msgid "The switch name in the traffic label while updating the switch type in a zone."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:761
+# 194c1dd122b7499b9058fb68380a5c3b
+msgid "Traffic label format in the last case is [[\"Name of vSwitch/dvSwitch/EthernetPortProfile\"][,\"VLAN ID\"[,\"vSwitch Type\"]]]"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:764
+# d4465ec982c94832ad7802b80686d0d1
+msgid "The possible values for traffic labels are:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:766
+# 83829438bd2d4e5e81d7cea6cfdc2119
+msgid "empty string"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:768
+# 089b868403e34bf385680a0275f453d9
+msgid "dvSwitch0"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:770
+# 8b132cc7e95e45b2927b570ef7790872
+msgid "dvSwitch0,200"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:772
+# f7e7251340ed4d489fd76000a902ab3e
+msgid "dvSwitch1,300,vmwaredvs"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:774
+# ffffef07a554452b989817589b59299f
+msgid "myEthernetPortProfile,,nexusdvs"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:776
+# 374b8ec5b0114570a8bc2db1e26e1432
+msgid "dvSwitch0,,vmwaredvs"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:779
+# e062d1b7e19e4a5ea9cd173bc474c7f9
+msgid "The three fields to fill in are:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:781
+# b665494425f24293b1cbd8c18d88376e
+msgid "Name of the virtual / distributed virtual switch at vCenter."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:783
+# 64772a813ddb414aad487db7177d70d9
+msgid "The default value depends on the type of virtual switch:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:785
+# 0504f575abf04fbab918eb97fc3c23e5
+msgid "**vSwitch0**: If type of virtual switch is VMware vNetwork Standard virtual switch"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:788
+# d037b0c2a7774a86950c4337ccb8c737
+msgid "**dvSwitch0**: If type of virtual switch is VMware vNetwork Distributed virtual switch"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:791
+# b8bb2c95e98643c5a8416c7cacb4ed84
+msgid "**epp0**: If type of virtual switch is Cisco Nexus 1000v Distributed virtual switch"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:794
+# 37bea26e77904c918293b7794b8435fe
+msgid "VLAN ID to be used for this traffic wherever applicable."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:796
+# 74cab27934ab4664a4ef799aaabc26fa
+msgid "This field would be used for only public traffic as of now. In case of guest traffic this field would be ignored and could be left empty for guest traffic. By default empty string would be assumed which translates to untagged VLAN for that specific traffic type."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:801
+# ecac63913296423c96e60c6fcd70b23c
+msgid "Type of virtual switch. Specified as string."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:803
+# 736dcefb710d4eb8ad8ecdafc967ad7b
+msgid "Possible valid values are vmwaredvs, vmwaresvs, nexusdvs."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:805
+# 0ee50e36ae9a42ea93fad5da64772d2a
+msgid "**vmwaresvs**: Represents VMware vNetwork Standard virtual switch"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:807
+# c3412e427322421db59d72ed3a1af1da
+msgid "**vmwaredvs**: Represents VMware vNetwork distributed virtual switch"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:809
+# 86ab94faa29a4292811f32d8ef417a43
+msgid "**nexusdvs**: Represents Cisco Nexus 1000v distributed virtual switch."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:811
+# b6c929f8a3d94c4ba2b89f14d3454074
+msgid "If nothing specified (left empty), zone-level default virtual switchwould be defaulted, based on the value of global parameter you specify."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:814
+# 259ad555197c427b92b871cf9099c6e9
+msgid "Following are the global configuration parameters:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:816
+# ba94337b1d8f418b9b792ff195a188b1
+msgid "**vmware.use.dvswitch**: Set to true to enable any kind (VMware DVS and Cisco Nexus 1000v) of distributed virtual switch in a CloudStack deployment. If set to false, the virtual switch that can be used in that CloudStack deployment is Standard virtual switch."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:821
+# 1f0d3c297b1b44caa71c066007cc1f42
+msgid "**vmware.use.nexus.vswitch**: This parameter is ignored if vmware.use.dvswitch is set to false. Set to true to enable Cisco Nexus 1000v distributed virtual switch in a CloudStack deployment."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:827
+# 118ddca276544558a4e2202c55e634fd
+msgid "Enabling Virtual Distributed Switch in CloudStack"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:829
+# 82143bb642f94e2aa2cac07ffc264086
+msgid "To make a CloudStack deployment VDS enabled, set the vmware.use.dvswitch parameter to true by using the Global Settings page in the CloudStack UI and restart the Management Server. Unless you enable the vmware.use.dvswitch parameter, you cannot see any UI options specific to VDS, and CloudStack ignores the VDS-specific parameters that you specify. Additionally, CloudStack uses VDS for virtual network infrastructure if the value of vmware.use.dvswitch parameter is true and the value of vmware.use.nexus.dvswitch parameter is false. Another global parameter that defines VDS configuration is vmware.ports.per.dvportgroup. This is the default number of ports per VMware dvPortGroup in a VMware environment. Default value is 256. This number directly associated with the number of guest network you can create."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:843
+# 402c2275d5ad4f3797ca2a376401aee2
+msgid "CloudStack supports orchestration of virtual networks in a deployment with a mix of Virtual Distributed Switch, Standard Virtual Switch and Nexus 1000v Virtual Switch."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:849
+# 6811c0b0e8df461d9e2e43e42a23020c
+msgid "Configuring Distributed Virtual Switch in CloudStack"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:851
+# 8c7c27c152754a3496e49f3e867403e7
+msgid "You can configure VDS by adding the necessary resources while a zone is created."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:854
+# 5c9df8759a344053862dcd9c629277cf
+msgid "Alternatively, at the cluster level, you can create an additional cluster with VDS enabled in the existing zone. Use the Add Cluster option. For information as given in `“Add Cluster: vSphere” <configuration.html#add-cluster-vsphere>`_."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:859
+# e0af0a758b7d4f03a1f5a83ae7e53aca
+msgid "In both these cases, you must specify the following parameters to configure VDS:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:862
+# 68137fa71ec145fc8a3dbdc1dde90e0a
+msgid "|dvSwitchConfig.png: Configuring dvSwitch|"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:865
+# c44708acf56642f6bdc0e41399c84ccc
+msgid "Parameters Description"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:867
+# e9d2fae4cc094bf29e7470348646862a
+msgid "Enter the name of the cluster you created in vCenter. For example, \"cloudcluster\"."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:868
+# 2eb58724f9dc40b78cb1261c45a8425a
+msgid "Enter the name or the IP address of the vCenter host where you have deployed the VMware VDS."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:871
+# 64ad16bd9476459999c67afeec2a76cd
+msgid "Enter the vCenter datacenter that the cluster is in. For example, \"clouddcVM\"."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:872
+# 519c5255a7714ab5ae2d130ea2ac0b09
+msgid "Override Public Traffic"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:872
+# 834881d8791d4560ba8fcba7d3478f6d
+msgid "Enable this option to override the zone-wide public traffic for the cluster you are creating."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:873
+# 380dfef8c1844f399f2cbd5c09d3e6ee
+msgid "Public Traffic vSwitch Type"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:873
+# 444137a9e330418b808e55cf02a62e97
+msgid "This option is displayed only if you enable the Override Public Traffic option. Select VMware vNetwork Distributed Virtual Switch. If the vmware.use.dvswitch global parameter is true, the default option will be VMware vNetwork Distributed Virtual Switch."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:874
+# 5396ef53dbdc46828b829c10118c7ca9
+msgid "Public Traffic vSwitch Name"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:874
+# 8d69112f1cb240ed98549493d13e6775
+msgid "Name of virtual switch to be used for the public traffic."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:875
+# 08c372cbcf0c4ae2a6bf96d5b5877d5f
+msgid "Override Guest Traffic"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:875
+# bfb400fd3046492f9c0e679af6725e95
+msgid "Enable the option to override the zone-wide guest traffic for the cluster you are creating."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:876
+# c393048d168a4e74851ea171593bff47
+msgid "Guest Traffic vSwitch Type"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:876
+# 20a6787434c649b8b9804b209e8217d9
+msgid "This option is displayed only if you enable the Override Guest Traffic option. Select VMware vNetwork Distributed Virtual Switch. If the vmware.use.dvswitch global parameter is true, the default option will be VMware vNetwork Distributed Virtual Switch."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:877
+# 8e911ae658a54e38bc94d44bd7360a60
+msgid "Guest Traffic vSwitch Name"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:877
+# e2fef73d36884fc18391b02ba8492fed
+msgid "Name of virtual switch to be used for guest traffic."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:882
+# fdd69bb3d44f4bcd9f56db1a98842617
+msgid "Storage Preparation for vSphere (iSCSI only)"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:884
+# 8617abba6dbc4534ad13b17929bb8816
+msgid "Use of iSCSI requires preparatory work in vCenter. You must add an iSCSI target and create an iSCSI datastore."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:887
+# cd8def1af119474099d424fa51348782
+msgid "If you are using NFS, skip this section."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:891
+# 965c53dfd68549dcb2ff3d7b6f5b8ef6
+msgid "Enable iSCSI initiator for ESXi hosts"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:893
+# f31d653b97a34904bba9418166f4d27f
+msgid "In vCenter, go to hosts and Clusters/Configuration, and click Storage Adapters link. You will see:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:896
+# c2db82b7ad84447c90bc1361acb6fe26
+msgid "|vmwareiscsiinitiator.png: iscsi initiator|"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:898
+# b0f077089acc4b47bc0e81c18ef873bc
+msgid "Select iSCSI software adapter and click Properties."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:900
+# 5ff6af603a254d62a64459f283531878
+msgid "|vmwareiscsiinitiatorproperties.png: iscsi initiator properties|"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:902
+# 4fc6bd69f5a74997a26a8ed8ff4a635d
+msgid "Click the Configure... button."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:904
+# d1a7febad60a4c72a88effb69663d334
+msgid "|vmwareiscsigeneral.png: iscsi general|"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:906
+# b542942a98b04d3fb1009c9cfbeea698
+msgid "Check Enabled to enable the initiator."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:908
+# 426af842784e4c0bb8e14ec9948ff60c
+msgid "Click OK to save."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:912
+# 668e7a8543bd45448ad0db8ae303bfc0
+msgid "Add iSCSI target"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:914
+# 8c293602e55f48578e49ba85c6b7bc72
+msgid "Under the properties dialog, add the iSCSI target info:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:916
+# ca9d056dfd584f658d8c3561ca8e94ac
+msgid "|vmwareiscsitargetadd.png: iscsi target add|"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:918
+# 48e3de1952584a7f83fdb8878b2e3309
+msgid "Repeat these steps for all ESXi hosts in the cluster."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:922
+# 5b7a2a4bd27d4e45ab60e0356f72d8a0
+msgid "Create an iSCSI datastore"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:924
+# 6e4943dc8eb04b0b839ba66174f1a7f7
+msgid "You should now create a VMFS datastore. Follow these steps to do so:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:926
+# 57cc6fe8445d4065b6d918ab122558aa
+msgid "Select Home/Inventory/Datastores."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:928
+# 0c8e6407c16c420c8ab924f07074c3f0
+msgid "Right click on the datacenter node."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:930
+# 33637d5c54c84c10bd4fddce9500d1db
+msgid "Choose Add Datastore... command."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:932
+# 10b59ee6f67f4fe18245206491765fa2
+msgid "Follow the wizard to create a iSCSI datastore."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:934
+# beb1bd72d9054c1aa2929c5f5bb46268
+msgid "This procedure should be done on one host in the cluster. It is not necessary to do this on all hosts."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:937
+# fddbde67076a489fae8ac3a07ba72a4e
+msgid "|vmwareiscsidatastore.png: iscsi datastore|"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:941
+# 720bb6a6678e4d048a7cb2fb20b5f00f
+msgid "Multipathing for vSphere (Optional)"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:943
+# f6110e7830f74e37b59a9ed7e75cc697
+msgid "Storage multipathing on vSphere nodes may be done according to the vSphere installation guide."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:948
+# 90bf6e714b424e1cb0f0727e69bd91bd
+msgid "Add Hosts or Configure Clusters (vSphere)"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:950
+# 34c741b108a3471086a9877f848c219a
+msgid "Use vCenter to create a vCenter cluster and add your desired hosts to the cluster. You will later add the entire cluster to CloudStack. (see `“Add Cluster: vSphere” <configuration.html#add-cluster-vsphere>`_)."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:956
+# e222980c86f646a6b7847d19c943d01e
+msgid "Applying Hotfixes to a VMware vSphere Host"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:958
+# afbce7caade34557b5de0efd81ac8337
+msgid "Disconnect the VMware vSphere cluster from CloudStack. It should remain disconnected long enough to apply the hotfix on the host."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:961
+#: ../../hypervisor/vsphere.rst:989
+# c3e9304bebf74cec95280a42ff6c47bc
+# 93ca13f83e884aa6bc68dca551cd9c85
+msgid "Log in to the CloudStack UI as root."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:963
+# ae093003e8e54de3bd3685570562d010
+msgid "See `“Log In to the UI” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:966
+# ab2de97e73f842718ecd3a5c0517a46f
+msgid "Navigate to the VMware cluster, click Actions, and select Unmanage."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:969
+# 291849fb997541a392eb9c265469db83
+msgid "Watch the cluster status until it shows Unmanaged."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:971
+# d36d95821f7349bdbeb6146d69609d26
+msgid "Perform the following on each of the ESXi hosts in the cluster:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:973
+# 1596207414164387b33d50a83ace4f1d
+msgid "Move each of the ESXi hosts in the cluster to maintenance mode."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:975
+# 0f443a13d2214787aace57dbe095be32
+msgid "Ensure that all the VMs are migrated to other hosts in that cluster."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:978
+# 993a0bfff5d949d79160c8a611af7d45
+msgid "If there is only one host in that cluster, shutdown all the VMs and move the host into maintenance mode."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:981
+# 549ba78fd15b49e081bd0e3212261dc1
+msgid "Apply the patch on the ESXi host."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:983
+# c7418a0d9f414399a6e7b5d7281c5cd5
+msgid "Restart the host if prompted."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:985
+# 7882f2dc5f704ad2a2ae6b6fe2ef0fb0
+msgid "Cancel the maintenance mode on the host."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:987
+# 27eaeff783e845fba9f5550da792fe4d
+msgid "Reconnect the cluster to CloudStack:"
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:991
+# dafd6eb321c643db98f259663c789c70
+msgid "Navigate to the VMware cluster, click Actions, and select Manage."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:993
+# bdbbffe72d294cdbadc09334b9549fdb
+msgid "Watch the status to see that all the hosts come up. It might take several minutes for the hosts to come up."
+msgstr ""
+
+#: ../../hypervisor/vsphere.rst:996
+# 61accad423f64d2b90044cac762efc57
+msgid "Alternatively, verify the host state is properly synchronized and updated in the CloudStack database."
+msgstr ""
+
diff --git a/source/installguide/locale/pot/hypervisor/xenserver.pot b/source/installguide/locale/pot/hypervisor/xenserver.pot
new file mode 100644
index 0000000..7c7a65b
--- /dev/null
+++ b/source/installguide/locale/pot/hypervisor/xenserver.pot
@@ -0,0 +1,944 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../hypervisor/xenserver.rst:18
+# dbca5e0c19df40c290465114f3559dec
+msgid "Citrix XenServer Installation for CloudStack"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:20
+# cd47a83746ac418dbc9077979249b7da
+msgid "If you want to use the Citrix XenServer hypervisor to run guest virtual machines, install XenServer 6.0 or XenServer 6.0.2 on the host(s) in your cloud. For an initial installation, follow the steps below. If you have previously installed XenServer and want to upgrade to another version, see :ref:`upgrading-xenserver-version`."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:28
+# d9ee0495584b4a8298e517da8fdc3057
+msgid "System Requirements for XenServer Hosts"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:30
+# 3d5008ea44354966853d8d381ed7891a
+msgid "The host must be certified as compatible with one of the following. See the Citrix Hardware Compatibility Guide: `http://hcl.xensource.com <http://hcl.xensource.com>`_"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:34
+# 8314770679cb4bc99d30a72aef396428
+msgid "XenServer 5.6 SP2"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:35
+# 24946ee9574b4a6791b00328377a2b5a
+msgid "XenServer 6.0"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:36
+# 7c1b9ee9639c4610aad50db7807788f8
+msgid "XenServer 6.0.2"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:37
+# 9baf931e48934c4c8c54669d292e0f87
+msgid "XenServer 6.1.0"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:38
+# 7ee33d4c2fd7471fafb3a3bcb6352a7e
+msgid "XenServer 6.2.0"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:40
+# 5dee06ed5f2f472f9e0979ddbb241a63
+msgid "You must re-install Citrix XenServer if you are going to re-use a host from a previous install."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:43
+# 80cb092fd1e84cd48850208d4ba0bbf5
+msgid "Must support HVM (Intel-VT or AMD-V enabled)"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:45
+# bab4879deea84fe697e8b924ffd8fb1c
+msgid "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."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:54
+# 7be511b75f274a11877a89c4e5b4442a
+msgid "All hosts within a cluster must be homogeneous. The CPUs must be of the same type, count, and feature flags."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:57
+# f1598069d3724215b893587629e5a745
+msgid "Must support HVM (Intel-VT or AMD-V enabled in BIOS)"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:59
+# 136e934524c54e44a1dc5daa197a36c1
+msgid "64-bit x86 CPU (more cores results in better performance)"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:61
+# a06b5cab48ca4c9d86747442230f0613
+msgid "Hardware virtualization support required"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:63
+# 3d9b7de9d5cb4e629ef6589132428cb0
+msgid "4 GB of memory"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:65
+# e3a33fc842e74c2191c11b46d1e11d6e
+msgid "36 GB of local disk"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:67
+# a7120f278e3a48f7a1957e666d4539fc
+msgid "At least 1 NIC"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:69
+# a2ea178b475547d899a7a72ae1ae9761
+msgid "Statically allocated IP Address"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:71
+# 829b6839c66d461b9f1692bb1a42e0a3
+msgid "When you deploy CloudStack, the hypervisor host must not have any VMs already running"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:75
+# 593acf4d53964830be70c33d03648380
+msgid "The lack of up-do-date hotfixes can lead to data corruption and lost VMs."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:79
+# 10efea9818be4d9fb0c4a1f8128f964e
+msgid "XenServer Installation Steps"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:81
+# a2c7219af86147eeab5c37bd51222363
+msgid "From `https://www.citrix.com/English/ss/downloads/ <https://www.citrix.com/English/ss/downloads/>`_, download the appropriate version of XenServer for your CloudStack version (see `\"System Requirements for XenServer Hosts\" <#system-requirements-for-xenserver-hosts>`_). Install it using the Citrix XenServer Installation Guide."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:88
+# 48628175cf1b4e66a6889e16ec013033
+msgid "Older Versions of XenServer:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:90
+# b9b29c0fa89c4656ab70adbb2a99e673
+msgid "Note that you can download the most recent release of XenServer without having a Citrix account. If you wish to download older versions, you will need to create an account and look through the download archives."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:97
+# 2feb5a48073c4e2e9fe034ed56a4384d
+msgid "Configure XenServer dom0 Memory"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:99
+# 07ce15cab19948cc8331905b67b44d32
+msgid "Configure the XenServer dom0 settings to allocate more memory to dom0. This can enable XenServer to handle larger numbers of virtual machines. We recommend 2940 MB of RAM for XenServer dom0. For instructions on how to do this, see `http://support.citrix.com/article/CTX126531 <http://support.citrix.com/article/CTX126531>`_. The article refers to XenServer 5.6, but the same information applies to XenServer 6.0."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:108
+# 5e0c0f29a1814ea5875442853353fe5e
+msgid "Username and Password"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:110
+# 6f2532ac7db843db93d53f391ae6d733
+msgid "All XenServers in a cluster must have the same username and password as configured in CloudStack."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:115
+# 941b9509be3746249f736aec017baf1f
+msgid "Time Synchronization"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:117
+# 0a006397adbf45fd9e71c3dc58c59a20
+msgid "The host must be set to use NTP. All hosts in a pod must have the same time."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:120
+# 17ff16e49de74a14a14e94a5e972d414
+msgid "Install NTP."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:126
+# 6fa27a22869648db88edf8eed39beca0
+msgid "Edit the NTP configuration file to point to your NTP server."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:132
+# 0536cc30cd854673bfb3aacf080a0fc6
+msgid "Add one or more server lines in this file with the names of the NTP servers you want to use. For example:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:142
+# 8ed85f477b5d41d584b84da677111ac8
+msgid "Restart the NTP client."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:148
+# ed2a3d2d19dc4679bf6153406fa541bd
+msgid "Make sure NTP will start again upon reboot."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:156
+# a8af271b25314a23bb268e7969c44be2
+msgid "Install CloudStack XenServer Support Package (CSP)"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:158
+# 0f869b8baf314029ba6e3249f3f31919
+msgid "(Optional)"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:160
+# ef8e6914984045fe820f2142f5801c32
+msgid "To enable security groups, elastic load balancing, and elastic IP on XenServer, download and install the CloudStack XenServer Support Package (CSP). After installing XenServer, perform the following additional steps on each XenServer host."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:165
+# a8fc4362d3c348039963da1e1f0b41b4
+msgid "**For XenServer 6.1:**"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:167
+# e208ea52210e4bec8f264922573855e2
+msgid "CSP functionality is already present in XenServer 6.1"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:169
+# 378f2f6ca35b4ce4a72152f22948e64d
+msgid "Run the below command"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:175
+# 68eac0ca1dc94b6181a9a3f9e81fa493
+msgid "update sysctl.conf with the following"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:186
+# 69cb332c88bf4c2c82d7ab3b9f7b2799
+msgid "**For XenServer 6.0.2, 6.0, 5.6 SP2:**"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:188
+# 03b2b8ea0626476a8c58d7cc9e4db68e
+msgid "Download the CSP software onto the XenServer host from one of the following links:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:191
+# bd00d11ce1cc45b8a45cef5f93e3d5eb
+msgid "For XenServer 6.0.2:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:193
+# c7d858231a3142109c09bfcc3340078b
+msgid "`http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz>`_"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:196
+# 2cbbc4bcdcdd42d0816a6b2df748a0d6
+msgid "For XenServer 5.6 SP2:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:198
+# beac106ea20e420cae0ca5acb450646b
+msgid "`http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz>`_"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:201
+# 62cd9713906c45dc96254605c7134b11
+msgid "For XenServer 6.0:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:203
+# 998fd323b14c42149cc6633f4df39b83
+msgid "`http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz>`_"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:207
+# 50f6122c6c5e42dbb34f5942e788bd76
+msgid "Extract the file:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:213
+#: ../../hypervisor/xenserver.rst:762
+# afb359e6c1b34048bffed17d2dd50caf
+# d6743dae63394bbfb8c9281a2b807b79
+msgid "Run the following script:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:219
+# acac1637a03046aa8d18547ccc4bca4b
+msgid "If the XenServer host is part of a zone that uses basic networking, disable Open vSwitch (OVS):"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:226
+# 3a99c0b1de854d158eda0ad17722a6a4
+msgid "Restart the host machine when prompted."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:228
+# de44be78fbb74675b797aa1c8d77d5f4
+msgid "The XenServer host is now ready to be added to CloudStack."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:232
+# c7f7f8a7ee21490c87265ac50b0f82fa
+msgid "Primary Storage Setup for XenServer"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:234
+# acb57e34a8e44c068d9bda2fa8784ab6
+msgid "CloudStack natively supports NFS, iSCSI and local storage. If you are using one of these storage types, there is no need to create the XenServer Storage Repository (\"SR\")."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:238
+# 2d42f9931e424e16b90373f6e29342e8
+msgid "If, however, you would like to use storage connected via some other technology, such as FiberChannel, you must set up the SR yourself. To do so, perform the following steps. If you have your hosts in a XenServer pool, perform the steps on the master node. If you are working with a single XenServer which is not part of a cluster, perform the steps on that XenServer."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:245
+# 56d99586bd3a4a558b7bb66ad8d45ca0
+msgid "Connect FiberChannel cable to all hosts in the cluster and to the FiberChannel storage host."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:248
+# 8cd5013ce09d4df3b88eb92833ec5ec8
+msgid "Rescan the SCSI bus. Either use the following command or use XenCenter to perform an HBA rescan."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:255
+# bacd282ff359414aaa9442a987f5c298
+msgid "Repeat step 2 on every host."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:257
+# cd620af66c684a0e89322909e82369f4
+msgid "Check to be sure you see the new SCSI disk."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:263
+# 8318145d9f754f2cba3dc478f5fac2bb
+msgid "The output should look like this, although the specific file name will be different (scsi-<scsiID>):"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:271
+# 1cd57220dc34464b9985019c2bc74209
+msgid "Repeat step 4 on every host."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:273
+# ab7f1cb3586b43148fc804bf9f9a6785
+msgid "On the storage server, run this command to get a unique ID for the new SR."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:280
+# f68f1582ab2645ff91819eb14ea37ebf
+msgid "The output should look like this, although the specific ID will be different:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:287
+# 12c7ee94b650422dac6fa14fc9a7d775
+msgid "Create the FiberChannel SR. In name-label, use the unique ID you just generated."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:296
+# e369b17cd1df40b3aa0cce96c1974a36
+msgid "This command returns a unique ID for the SR, like the following example (your ID will be different):"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:303
+# 23f181a0244c4e4b980acb6e64e29d3b
+msgid "To create a human-readable description for the SR, use the following command. In uuid, use the SR ID returned by the previous command. In name-description, set whatever friendly text you prefer."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:311
+# 4323c9a63c6540b4a16886f29d0a1ec5
+msgid "Make note of the values you will need when you add this storage to CloudStack later (see `\"Add Primary Storage\" <configuration.html#add-primary-storage>`_). In the Add Primary Storage dialog, in Protocol, you will choose PreSetup. In SR Name-Label, you will enter the name-label you set earlier (in this example, e6849e96-86c3-4f2c-8fcc-350cc711be3d)."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:318
+# c99025edebad4540ba6b2b1d9b20ed10
+msgid "(Optional) If you want to enable multipath I/O on a FiberChannel SAN, refer to the documentation provided by the SAN vendor."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:323
+# 32342d3a35f54066ade7572169b52896
+msgid "iSCSI Multipath Setup for XenServer (Optional)"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:325
+# e2cf4ffa587b4372969e274849f484ee
+msgid "When setting up the storage repository on a Citrix XenServer, you can enable multipath I/O, which uses redundant physical components to provide greater reliability in the connection between the server and the SAN. To enable multipathing, use a SAN solution that is supported for Citrix servers and follow the procedures in Citrix documentation. The following links provide a starting point:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:332
+# 3849959c9c354656a9a9daafc5c5dbed
+msgid "`http://support.citrix.com/article/CTX118791 <http://support.citrix.com/article/CTX118791>`_"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:335
+# 8a118ac63a7f41b8b60968177ca6b343
+msgid "`http://support.citrix.com/article/CTX125403 <http://support.citrix.com/article/CTX125403>`_"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:338
+# d3f63182749e40fd86184084f5cc529b
+msgid "You can also ask your SAN vendor for advice about setting up your Citrix repository for multipathing."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:341
+# 11df997f92b94313a59c0deac4d901ee
+msgid "Make note of the values you will need when you add this storage to the CloudStack later (see `\"Add Primary Storage\" <configuration.html#add-primary-storage>`_). In the Add Primary Storage dialog, in Protocol, you will choose PreSetup. In SR Name-Label, you will enter the same name used to create the SR."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:347
+# de3e8779fcb54068a8684c6ae2a20a69
+msgid "If you encounter difficulty, address the support team for the SAN provided by your vendor. If they are not able to solve your issue, see Contacting Support."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:353
+# b62346b563314a04b2892d0d30ebafc9
+msgid "Physical Networking Setup for XenServer"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:355
+# b07a74e5a82a42dfaa85655a392fc5a1
+msgid "Once XenServer has been installed, you may need to do some additional network configuration. At this point in the installation, you should have a plan for what NICs the host will have and what traffic each NIC will carry. The NICs should be cabled as necessary to implement your plan."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:361
+# e67a8a2a93f44a4182d4d83db27837bb
+msgid "If you plan on using NIC bonding, the NICs on all hosts in the cluster must be cabled exactly the same. For example, if eth0 is in the private bond on one host in a cluster, then eth0 must be in the private bond on all hosts in the cluster."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:366
+# c8f114e421254029bfcc786da1e4f069
+msgid "The IP address assigned for the management network interface must be static. It can be set on the host itself or obtained via static DHCP."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:369
+# 4ea2dcd3445945e494146eea4f434ebe
+msgid "CloudStack configures network traffic of various types to use different NICs or bonds on the XenServer host. You can control this process and provide input to the Management Server through the use of XenServer network name labels. The name labels are placed on physical interfaces or bonds and configured in CloudStack. In some simple cases the name labels are not required."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:376
+# d4647179170b4228990c4233187a27f0
+msgid "When configuring networks in a XenServer environment, network traffic labels must be properly configured to ensure that the virtual interfaces are created by CloudStack are bound to the correct physical device. The name-label of the XenServer network must match the XenServer traffic label specified while creating the CloudStack network. This is set by running the following command:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:389
+# c06c60c71a7f4bca8a451f0b7283cfda
+msgid "Configuring Public Network with a Dedicated NIC for XenServer (Optional)"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:391
+# 6e7e724c968a42a3a8b427928f42cb98
+msgid "CloudStack supports the use of a second NIC (or bonded pair of NICs, described in :ref:`nic-bonding-for-xenserver`) for the public network. If bonding is not used, the public network can be on any NIC and can be on different NICs on the hosts in a cluster. For example, the public network can be on eth0 on node A and eth1 on node B. However, the XenServer name-label for the public network must be identical across all hosts. The following examples set the network label to \"cloud-public\". After the management server is installed and running you must configure it with the name of the chosen network label (e.g. \"cloud-public\"); this is discussed in `\"Management Server Installation\" <installation.html#management-server-installation>`_."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:403
+# 0a920576e6984f1684ffa04b4cedee14
+msgid "If you are using two NICs bonded together to create a public network, see :ref:`nic-bonding-for-xenserver`."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:406
+# c29eb136da7f472bb9092308209f4874
+msgid "If you are using a single dedicated NIC to provide public network access, follow this procedure on each new host that is added to CloudStack before adding the host."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:410
+# b6c2fcbca5784ac58cb4d766831c1feb
+msgid "Run xe network-list and find the public network. This is usually attached to the NIC that is public. Once you find the network make note of its UUID. Call this <UUID-Public>."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:414
+# 7771ef8019cf477aab4f4ea6e54dc19f
+msgid "Run the following command."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:422
+# 8b08df411b014c2fb09ab7803d37e385
+msgid "Configuring Multiple Guest Networks for XenServer (Optional)"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:424
+# ae3d74bbbeb6474caa1aabf43ce3350d
+msgid "CloudStack supports the use of multiple guest networks with the XenServer hypervisor. Each network is assigned a name-label in XenServer. For example, you might have two networks with the labels \"cloud-guest\" and \"cloud-guest2\". After the management server is installed and running, you must add the networks and use these labels so that CloudStack is aware of the networks."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:431
+# 445fbda3e6e241b49943d5a3bbae731e
+msgid "Follow this procedure on each new host before adding the host to CloudStack:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:434
+# ad021bb20dfc411ca2a0b4f6c7bb1976
+msgid "Run xe network-list and find one of the guest networks. Once you find the network make note of its UUID. Call this <UUID-Guest>."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:437
+# 5c54bddb03ab41988d164862d3e8ca4a
+msgid "Run the following command, substituting your own name-label and uuid values."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:444
+# 66309bb437094b1d9bbb0774c232de9a
+msgid "Repeat these steps for each additional guest network, using a different name-label and uuid each time."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:449
+# 355487377b08418899e9ec50ac78ae2f
+msgid "Separate Storage Network for XenServer (Optional)"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:451
+# 589c7e9b7fb048aea788093e27195cf2
+msgid "You can optionally set up a separate storage network. This should be done first on the host, before implementing the bonding steps below. This can be done using one or two available NICs. With two NICs bonding may be done as above. It is the administrator's responsibility to set up a separate storage network."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:457
+# 61490e5df97948629bbb83dda64d4aa9
+msgid "Give the storage network a different name-label than what will be given for other networks."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:460
+# 164d8afca329462b9c5943496322bcf0
+msgid "For the separate storage network to work correctly, it must be the only interface that can ping the primary storage device's IP address. For example, if eth0 is the management network NIC, ping -I eth0 <primary storage device IP> must fail. In all deployments, secondary storage devices must be pingable from the management network NIC or bond. If a secondary storage device has been placed on the storage network, it must also be pingable via the storage network NIC or bond on the hosts as well."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:469
+# 90f24bd320174d1fac607e00a9e983f8
+msgid "You can set up two separate storage networks as well. For example, if you intend to implement iSCSI multipath, dedicate two non-bonded NICs to multipath. Each of the two networks needs a unique name-label."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:473
+# 61c2f4816fdb42d5b6cc3c6d2ca18ca8
+msgid "If no bonding is done, the administrator must set up and name-label the separate storage network on all hosts (masters and slaves)."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:476
+# 00dbbb5d1bcd4becb0dec5b47340f83d
+msgid "Here is an example to set up eth5 to access a storage network on 172.16.0.0/24."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:490
+# 185e1a599c604803a54446ba74b35dc9
+msgid "NIC Bonding for XenServer (Optional)"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:492
+# caf6aa9edc614274af0ef31881fe03ca
+msgid "XenServer supports Source Level Balancing (SLB) NIC bonding. Two NICs can be bonded together to carry public, private, and guest traffic, or some combination of these. Separate storage networks are also possible. Here are some example supported configurations:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:497
+# 44d7cdc70d4541e4b8b66e39293c57c5
+msgid "2 NICs on private, 2 NICs on public, 2 NICs on storage"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:499
+# 7dbbc60ca898461991faac0752ccb9b6
+msgid "2 NICs on private, 1 NIC on public, storage uses management network"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:501
+# 933cb0b64cdc4b93b709825c7f872083
+msgid "2 NICs on private, 2 NICs on public, storage uses management network"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:503
+# aa2cdc325ff64d6dbeb15a9db3815249
+msgid "1 NIC for private, public, and storage"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:505
+# a5c691fdc14644f1938a3d7e0616e209
+msgid "All NIC bonding is optional."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:507
+# ce37792754e74070b0880c3c27ca5b6d
+msgid "XenServer expects all nodes in a cluster will have the same network cabling and same bonds implemented. In an installation the master will be the first host that was added to the cluster and the slave hosts will be all subsequent hosts added to the cluster. The bonds present on the master set the expectation for hosts added to the cluster later. The procedure to set up bonds on the master and slaves are different, and are described below. There are several important implications of this:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:515
+# 31e309b5aea94e1982a0745fa2f8d163
+msgid "You must set bonds on the first host added to a cluster. Then you must use xe commands as below to establish the same bonds in the second and subsequent hosts added to a cluster."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:519
+# dc53904a0ade40e8996b6379af74299d
+msgid "Slave hosts in a cluster must be cabled exactly the same as the master. For example, if eth0 is in the private bond on the master, it must be in the management network for added slave hosts."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:525
+# 5a1e3289d6064e239e1ac513d07d53c7
+msgid "Management Network Bonding"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:527
+# d6933d9eedc548ea911d1c03954c8cc8
+msgid "The administrator must bond the management network NICs prior to adding the host to CloudStack."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:532
+# 990edf34545641be9105fff2e790fa8e
+msgid "Creating a Private Bond on the First Host in the Cluster"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:534
+# bef555ea56e644ee824b3211d285a5dc
+msgid "Use the following steps to create a bond in XenServer. These steps should be run on only the first host in a cluster. This example creates the cloud-private network with two physical NICs (eth0 and eth1) bonded into it."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:539
+#: ../../hypervisor/xenserver.rst:583
+# 76d14a97770b48e3b7573b8df3d95987
+# 83ee5c43bfdf49078158dc0ede74e1cb
+msgid "Find the physical NICs that you want to bond together."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:546
+# 19647e91e4064b26bcf46ae5ccdb7654
+msgid "These command shows the eth0 and eth1 NICs and their UUIDs. Substitute the ethX devices of your choice. Call the UUID's returned by the above command slave1-UUID and slave2-UUID."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:550
+# eb485b7e38044135bbafec10517e6fda
+msgid "Create a new network for the bond. For example, a new network with name \"cloud-private\"."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:553
+# 4426249063674de991301445df08c8af
+msgid "**This label is important. CloudStack looks for a network by a name you configure. You must use the same name-label for all hosts in the cloud for the management network.**"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:563
+# 10a8ca3e627f42039cde96aa311c2e24
+msgid "Now you have a bonded pair that can be recognized by CloudStack as the management network."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:568
+# 8237b2020d164e25afdf235b117e0226
+msgid "Public Network Bonding"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:570
+# c0b0ed9d574d4595b6bccb839df5a9d6
+msgid "Bonding can be implemented on a separate, public network. The administrator is responsible for creating a bond for the public network if that network will be bonded and will be separate from the management network."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:577
+# 49b1405549674b47892be73abf90bb90
+msgid "Creating a Public Bond on the First Host in the Cluster"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:579
+# 80ceb8eb4f324fa288b049d1b412d166
+msgid "These steps should be run on only the first host in a cluster. This example creates the cloud-public network with two physical NICs (eth2 and eth3) bonded into it."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:590
+# e9ee4656a26c4e429fa44a19deca4697
+msgid "These command shows the eth2 and eth3 NICs and their UUIDs. Substitute the ethX devices of your choice. Call the UUID's returned by the above command slave1-UUID and slave2-UUID."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:594
+# ecd21d8abed7420cbdb7722f7d3bbcf6
+msgid "Create a new network for the bond. For example, a new network with name \"cloud-public\"."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:597
+# f2ccf39a444949779ea15c87c23f1102
+msgid "**This label is important. CloudStack looks for a network by a name you configure. You must use the same name-label for all hosts in the cloud for the public network.**"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:607
+# c63c4fffe13c41e3857c2d5a7037324d
+msgid "Now you have a bonded pair that can be recognized by CloudStack as the public network."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:612
+# 4571fae00d22423c977f157626730a6b
+msgid "Adding More Hosts to the Cluster"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:614
+# bb7f4bc061df424882aa108cec051dde
+msgid "With the bonds (if any) established on the master, you should add additional, slave hosts. Run the following command for all additional hosts to be added to the cluster. This will cause the host to join the master in a single XenServer pool."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:626
+# 2e3ff343227f43eca63a765a974c4e58
+msgid "Complete the Bonding Setup Across the Cluster"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:628
+# e54d6baf9f4a4630ae0802e0e114130f
+msgid "With all hosts added to the pool, run the cloud-setup-bond script. This script will complete the configuration and set up of the bonds across all hosts in the cluster."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:632
+# 27800d5ec6e44bdcb75245bf193bfda2
+msgid "Copy the script from the Management Server in /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh to the master host and ensure it is executable."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:636
+# ed41f3f65d3f49209bba272a3b1c0922
+msgid "Run the script:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:642
+# 30dd45661f474b9f9d626aa8df7052e5
+msgid "Now the bonds are set up and configured properly across the cluster."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:648
+# 06329e8ef297453d9fbe11b802a02387
+msgid "Upgrading XenServer Versions"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:650
+# 7ae8e3b4c5e745e7b43ab29f5129e0cf
+msgid "This section tells how to upgrade XenServer software on CloudStack hosts. The actual upgrade is described in XenServer documentation, but there are some additional steps you must perform before and after the upgrade."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:656
+# a49d855e0fec4ddfb046814a7a02bc58
+msgid "Be sure the hardware is certified compatible with the new version of XenServer."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:659
+# dee99a5634554dc4b7188ab5c5aedc45
+msgid "To upgrade XenServer:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:661
+# c58f7ac2d954400395df0861156c145b
+msgid "Upgrade the database. On the Management Server node:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:663
+# a680a343ad5b4dc0900df3a60f835ead
+msgid "Back up the database:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:670
+# 22c201339a64428aba4b9ed4256a473e
+msgid "You might need to change the OS type settings for VMs running on the upgraded hosts."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:673
+# b4e5d659dfde45c7bf1279a03e48b5c1
+msgid "If you upgraded from XenServer 5.6 GA to XenServer 5.6 SP2, change any VMs that have the OS type CentOS 5.5 (32-bit), Oracle Enterprise Linux 5.5 (32-bit), or Red Hat Enterprise Linux 5.5 (32-bit) to Other Linux (32-bit). Change any VMs that have the 64-bit versions of these same OS types to Other Linux (64-bit)."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:680
+# 7573f70d77e248e5a4d430bd16631bbe
+msgid "If you upgraded from XenServer 5.6 SP2 to XenServer 6.0.2, change any VMs that have the OS type CentOS 5.6 (32-bit), CentOS 5.7 (32-bit), Oracle Enterprise Linux 5.6 (32-bit), Oracle Enterprise Linux 5.7 (32-bit), Red Hat Enterprise Linux 5.6 (32-bit) , or Red Hat Enterprise Linux 5.7 (32-bit) to Other Linux (32-bit). Change any VMs that have the 64-bit versions of these same OS types to Other Linux (64-bit)."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:688
+# ecee533ad8dd40ecbab222880d5502e4
+msgid "If you upgraded from XenServer 5.6 to XenServer 6.0.2, do all of the above."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:691
+# 92dd0b5b05d349f5b31a218ef5053b51
+msgid "Restart the Management Server and Usage Server. You only need to do this once for all clusters."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:699
+# 609fce92c5004d349ce69313e8b259d1
+msgid "Disconnect the XenServer cluster from CloudStack."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:701
+#: ../../hypervisor/xenserver.rst:803
+# a0e0ba7425e84cc4b3c558e55e6ba6c1
+# 9a532ffafa924e14bfdcd5a3f893f796
+msgid "Log in to the CloudStack UI as root."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:703
+# cfa57057adf34d20ad28ea73d14ef535
+msgid "Navigate to the XenServer cluster, and click Actions – Unmanage."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:705
+# 5d95636b239e4667b4933027c8a99a25
+msgid "Watch the cluster status until it shows Unmanaged."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:707
+# 80449684af9d499095d5d868770d0e7b
+msgid "Log in to one of the hosts in the cluster, and run this command to clean up the VLAN:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:714
+# d785d08cf59f499398b8f029d5186b94
+msgid "Still logged in to the host, run the upgrade preparation script:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:720
+# 31f5837f129648c9a08eca9c059eb78c
+msgid "Troubleshooting: If you see the error \"can't eject CD,\" log in to the VM and umount the CD, then run the script again."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:723
+# 715d2f02ed1c47c589935a7f3b1dafa3
+msgid "Upgrade the XenServer software on all hosts in the cluster. Upgrade the master first."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:726
+# d16b76e393814c10b8ce59d9d571f9a4
+msgid "Live migrate all VMs on this host to other hosts. See the instructions for live migration in the Administrator's Guide."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:729
+# 2abd9a8c661b47fc8eee237cf9108f92
+msgid "Troubleshooting: You might see the following error when you migrate a VM:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:738
+# b23537b0d5f942ccb71f8849c129899d
+msgid "To solve this issue, run the following:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:744
+# d92194b697694bd2b8152cfa36773892
+msgid "Reboot the host."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:746
+# 34903a18372648c9b8b6d06d03d0e02c
+msgid "Upgrade to the newer version of XenServer. Use the steps in XenServer documentation."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:749
+# 573adf7c44514928894306fcf3566a98
+msgid "After the upgrade is complete, copy the following files from the management server to this host, in the directory locations shown below:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:754
+# 18eb28018d324049916e1e1a4b9b1680
+msgid "Copy this Management Server file"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:754
+# 37bd1b6db08741b39cf4840e83ad9279
+msgid "To this location on the XenServer host"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:756
+# 77c4c74d05ee4ed084fecb4d94f0038e
+msgid "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/xenserver60/NFSSR.py"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:756
+# 5d5d441f185b4da39acede52092ab729
+msgid "/opt/xensource/sm/NFSSR.py"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:757
+# b9569d25b25c47589eb352b2f26b96d8
+msgid "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/setupxenserver.sh"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:757
+# 8ccdd7cb7c6d4213ba0d257d2adfcf42
+msgid "/opt/xensource/bin/setupxenserver.sh"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:758
+# 70be8fbba5fe4f9d81dbe6ffe68ca9fa
+msgid "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/make\\_migratable.sh"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:758
+# 9545ac4a5e554ac0856980527ee37e93
+msgid "/opt/xensource/bin/make\\_migratable.sh"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:759
+# d5729618b07f45fa871e57a5cdd5cb11
+msgid "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-clean-vlan.sh"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:759
+# 0af33abd27be47cf9afd563a8049f92f
+msgid "/opt/xensource/bin/cloud-clean-vlan.sh"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:768
+# 57e220ee90da43a18a72c97fb44f4642
+msgid "Troubleshooting: If you see the following error message, you can safely ignore it."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:775
+# 7d8ccf199424413ca7d2c6ace78d8d25
+msgid "Plug in the storage repositories (physical block devices) to the XenServer host:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:783
+# 03e1d3926bc546a5af37036f806b6776
+msgid "If you add a host to this XenServer pool, you need to migrate all VMs on this host to other hosts, and eject this host from XenServer pool."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:786
+# 9e79d6523b9b4c6982d7f0df8b920625
+msgid "Repeat these steps to upgrade every host in the cluster to the same version of XenServer."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:789
+# 0f820c2f7c49419ea8cce858406d9043
+msgid "Run the following command on one host in the XenServer cluster to clean up the host tags:"
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:797
+# 742db1ba5463410a9d82cc3a89bb7199
+msgid "When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:801
+# 5432c32d5f10462dbd868cbbbddc88f4
+msgid "Reconnect the XenServer cluster to CloudStack."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:805
+# 21a80cdb8f254573809173ca433e813e
+msgid "Navigate to the XenServer cluster, and click Actions – Manage."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:807
+# feaf793c4bb243358fe6893a23769add
+msgid "Watch the status to see that all the hosts come up."
+msgstr ""
+
+#: ../../hypervisor/xenserver.rst:809
+# 228283144fa14ff9b751f39e8007043f
+msgid "After all hosts are up, run the following on one host in the cluster:"
+msgstr ""
+
diff --git a/source/installguide/locale/pot/hypervisor_installation.pot b/source/installguide/locale/pot/hypervisor_installation.pot
new file mode 100644
index 0000000..180fcff
--- /dev/null
+++ b/source/installguide/locale/pot/hypervisor_installation.pot
@@ -0,0 +1,4221 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:02-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../hypervisor_installation.rst:17
+# a5b708b1c7f34ebeb40e555178227b10
+msgid "Hypervisor Installation"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:20
+# c97e1fa112814a849f7cd08e8f9d3c1e
+msgid "KVM Hypervisor Host Installation"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:23
+# 106ceeb500c947a88931ac644e73431d
+msgid "System Requirements for KVM Hypervisor Hosts"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:25
+# afa4fe6e1df94ebeb7668c1cabb0ff0c
+msgid "KVM is included with a variety of Linux-based operating systems. Although you are not required to run these distributions, the following are recommended:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:31
+#: ../../hypervisor_installation.rst:3327
+# 34c3bdfde3da4f2d9c34601a86f0afcf
+# a161e18b507540c096810a8ec29ef317
+msgid "CentOS / RHEL: 6.3"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:35
+#: ../../hypervisor_installation.rst:3331
+# 4ffd025eb47e4537b6eb5007d2b80629
+# 57d072c73c204d6e81f858aa46f60667
+msgid "Ubuntu: 12.04(.1)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:37
+# 7decad4017784f2f96f7030e58f6f239
+msgid "The main requirement for KVM hypervisors is the libvirt and Qemu version. No matter what Linux distribution you are using, make sure the following requirements are met:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:43
+# aee585bafb434d2dbe9d2579ab1dcad5
+msgid "libvirt: 0.9.4 or higher"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:47
+#: ../../hypervisor_installation.rst:3343
+# 008a79408bb34d52bf92873b8905dad3
+# 6364b35d5cdd483f87928821946c3f34
+msgid "Qemu/KVM: 1.0 or higher"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:49
+#: ../../hypervisor_installation.rst:3345
+# 4bc408d879ad447baa475bfd0808aa65
+# 3dbbe376cdd24657968196a32f21fda6
+msgid "The default bridge in CloudStack is the Linux native bridge implementation (bridge module). CloudStack includes an option to work with OpenVswitch, the requirements are listed below"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:55
+# 34be33c099374c35aa8784190733b87c
+msgid "libvirt: 0.9.11 or higher"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:59
+#: ../../hypervisor_installation.rst:3355
+# 7d3d628565264bc69adb04e77462b5b0
+# 4b4d3c51f3b746ed96a5bd61749758f4
+msgid "openvswitch: 1.7.1 or higher"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:61
+#: ../../hypervisor_installation.rst:3357
+# 6b26016e861b4aaaba05f3bd8c98f682
+# 1e2e540227304e14b7a8406969608a5e
+msgid "In addition, the following hardware requirements apply:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:65
+#: ../../hypervisor_installation.rst:3361
+# 322d406c43f64403bf5e8acfad80318d
+# 49490f42aa554579a0169795b8fec7cf
+msgid "Within a single cluster, the hosts must be of the same distribution version."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:70
+#: ../../hypervisor_installation.rst:3366
+# 86c9ea55ffec4f399b8e7918b7bb43d0
+# e392215de57d4843958e657b3d6d64c7
+msgid "All hosts within a cluster must be homogenous. The CPUs must be of the same type, count, and feature flags."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:75
+#: ../../hypervisor_installation.rst:1027
+#: ../../hypervisor_installation.rst:3371
+# e6544c9e2bed4d36a8b7bf5e2b040667
+# 405d986c35fd4e35bba0d7ea5664327b
+# b176112062f840bf8e4293cb2b6dd440
+msgid "Must support HVM (Intel-VT or AMD-V enabled)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:79
+#: ../../hypervisor_installation.rst:1051
+#: ../../hypervisor_installation.rst:2263
+#: ../../hypervisor_installation.rst:3375
+# fe8c3dec4f5e48af82d6a1cf4d35c0fa
+# 222e2e6b7d72437fa9d1e291b1abae33
+# b6a567096cf14ce7a86b7cab8cd8a120
+# d2f00762290a412aada0abbdddc35042
+msgid "64-bit x86 CPU (more cores results in better performance)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:83
+#: ../../hypervisor_installation.rst:1059
+#: ../../hypervisor_installation.rst:2271
+#: ../../hypervisor_installation.rst:3379
+# 8a4b47d3dc3a44c584fbd97dcf25a5a0
+# 14006a14fa284ce6ba19f360f889a0bc
+# 6d7b9af582894902a3e1095cfa7f02fe
+# 130dbc2bf67d4a5687f09f35f760a482
+msgid "4 GB of memory"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:87
+#: ../../hypervisor_installation.rst:1067
+#: ../../hypervisor_installation.rst:2279
+#: ../../hypervisor_installation.rst:3383
+# e8bd701c4ef947078dfed764bd5fc6d9
+# 656d673c698d4b118d21cc9362a8e5dd
+# 947d8b3ed1974720a911fdb6b44d4d36
+# a4a079db675c46938452f27bc17e3e68
+msgid "At least 1 NIC"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:91
+#: ../../hypervisor_installation.rst:1075
+#: ../../hypervisor_installation.rst:3387
+# 3444db1dcb1f47258e2772864b74a072
+# 0d176e6f680c42f88456e42ff3bbc75c
+# eaf19bdaaac2446a9eba73346cfb272c
+msgid "When you deploy CloudStack, the hypervisor host must not have any VMs already running"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:95
+# b090156a97514e25ae92874eabc12ebe
+msgid "KVM Installation Overview"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:97
+# 3c994a4c8bb44c3db12d9d1a91d88511
+msgid "If you want to use the Linux Kernel Virtual Machine (KVM) hypervisor to run guest virtual machines, install KVM on the host(s) in your cloud. The material in this section doesn't duplicate KVM installation docs. It provides the CloudStack-specific steps that are needed to prepare a KVM host to work with CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:105
+#: ../../hypervisor_installation.rst:3400
+# 0ae1e0787a0a4b35bb60e6ce2270b93c
+# fbbc0d73551e4738b0780bf7ae39b794
+msgid "Before continuing, make sure that you have applied the latest updates to your host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:109
+#: ../../hypervisor_installation.rst:3402
+# 3f404325440b43e8929f971c948bddd2
+# cdf930cc6f4f48cfbfa886bcea0c6c5c
+msgid "It is NOT recommended to run services on this host not controlled by CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:111
+# b4d910e8d72742e2992a140e0bbb07f9
+msgid "The procedure for installing a KVM Hypervisor Host is:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:115
+#: ../../hypervisor_installation.rst:130
+#: ../../hypervisor_installation.rst:3408
+#: ../../hypervisor_installation.rst:3423
+# f72c15c1878f4826b773a10ca9d09132
+# a5027d0749d5434b8990a4ce07b63190
+# cd85e26dfec64b0e85060beb3e51e135
+# 3f58fd5515bf4d7c95f3972fecc77a0f
+msgid "Prepare the Operating System"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:119
+#: ../../hypervisor_installation.rst:3412
+# 2a8a33c0f29c40b2823be72c0a3ebbb4
+# c6bed6d3e6b248daa4040d12455fe55a
+msgid "Install and configure libvirt"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:123
+#: ../../hypervisor_installation.rst:3416
+# 1642991c8fbd4e90ac67a46c59e515a5
+# a94fc5d5847b4a85b0f6d0ee714b7b1f
+msgid "Configure Security Policies (AppArmor and SELinux)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:127
+#: ../../hypervisor_installation.rst:185
+#: ../../hypervisor_installation.rst:3420
+#: ../../hypervisor_installation.rst:3477
+# 1ed5a01ec0704f2eb18b408abd6cae9c
+# 52a64dac3f794d7d9402c6f757812a16
+# 0bf1c9bf0fa048cdb0bffdde08d78760
+# 0902ea5204d74d8faa9db44b32e93779
+msgid "Install and configure the Agent"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:132
+#: ../../hypervisor_installation.rst:3425
+# 54165d82f02949c887291da9ef9385f7
+# 887757221dec4140950e28424103418d
+msgid "The OS of the Host must be prepared to host the CloudStack Agent and run KVM instances."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:137
+#: ../../hypervisor_installation.rst:3430
+# 3b1313122c04424eb3c0f4dea9099319
+# 209d2e9fe5a54af0a434c6fe42d67c94
+msgid "Log in to your OS as root."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:141
+#: ../../hypervisor_installation.rst:3434
+# faa86bd264934b1b8bab5914670677e8
+# ec55ce15def44bbea72ff6f68842becc
+msgid "Check for a fully qualified hostname."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:147
+#: ../../hypervisor_installation.rst:3440
+# 6e562892fc814c038043db4120089438
+# f775086cc87b40dab6aac8299ca88571
+msgid "This should return a fully qualified hostname such as \"kvm1.lab.example.org\". If it does not, edit /etc/hosts so that it does."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:153
+#: ../../hypervisor_installation.rst:3446
+# e009ff0ecafd4666a742d5af03d2309e
+# f85f5a8126094c72a1740ac354fc6e2f
+msgid "Make sure that the machine can reach the Internet."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:161
+#: ../../hypervisor_installation.rst:3454
+# 56ca23a905364937bac5cf61701e8a09
+# de0710f8ee154254b3d424dc19901a33
+msgid "Turn on NTP for time synchronization."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:165
+#: ../../hypervisor_installation.rst:3457
+# 0d18ab8873cc4b938d65ea7d9503d2f3
+# 2281cb7bd1ab44d0a18d9a382ae614d7
+msgid "NTP is required to synchronize the clocks of the servers in your cloud. Unsynchronized clocks can cause unexpected problems."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:170
+#: ../../hypervisor_installation.rst:3462
+# 65aa5ea952b94cb3bcd5151c59496e4d
+# fb7ee24bb05540f9859ba3b87f03487c
+msgid "Install NTP"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:182
+#: ../../hypervisor_installation.rst:3474
+# e93ea97e77314f19b564fc3d5e981897
+# c859b30acde9440ca4835511741c38ac
+msgid "Repeat all of these steps on every hypervisor host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:187
+# ea49f1e757d443beb13b7434fc7a6337
+msgid "To manage KVM instances on the host CloudStack uses a Agent. This Agent communicates with the Management server and controls all the instances on the host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:191
+#: ../../hypervisor_installation.rst:3483
+# 34eb5632982c49a7ad56d679b8897bad
+# 84ca527264e445eb9b6965300ff5a67a
+msgid "First we start by installing the agent:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:193
+#: ../../hypervisor_installation.rst:361
+#: ../../hypervisor_installation.rst:402
+#: ../../hypervisor_installation.rst:3485
+#: ../../hypervisor_installation.rst:3608
+#: ../../hypervisor_installation.rst:3649
+# d894051a1aa4420482cd5ecf26baf9b9
+# e209192de68d4bdb9b3cb14f77c59b1a
+# 0e50e758e1bd45628f4eee81cae74b1d
+# eb677ec246e749239198c0ef7edd5ff4
+# e2c94bf547f64410916a38d7e7fdd670
+# e86cca2d481a47539eef5083baa6edda
+msgid "In RHEL or CentOS:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:199
+#: ../../hypervisor_installation.rst:367
+#: ../../hypervisor_installation.rst:3491
+#: ../../hypervisor_installation.rst:3614
+# 3b6758b2ccb445b5be94a8dfc7ebd0a2
+# ade0da3eeb2941c49b1186cd22d03202
+# 0f363f2af00f4b159318dab564862baa
+# a14254a637a742dfa6d89b25b9b24656
+msgid "In Ubuntu:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:205
+#: ../../hypervisor_installation.rst:943
+#: ../../hypervisor_installation.rst:3525
+#: ../../hypervisor_installation.rst:4024
+# d096d4acc81e4e60834b9a24af414019
+# 8bd1adc0e2a34211956f1b708f3c9724
+# 1e3a5fd3b85f4bce9244ebdcc0b999ed
+# 78185f32c03c498db18b23abd0426910
+msgid "The host is now ready to be added to a cluster. This is covered in a later section, see :ref:`adding-a-host`. It is recommended that you continue to read the documentation before adding the host!"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:211
+# af1b91fcf7484085b389fb8d502edcd6
+msgid "Configure CPU model for KVM guest (Optional)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:213
+# 7fdc1820edee46fca04097cd36443ade
+msgid "In additional,the CloudStack Agent allows host administrator to control the guest CPU model which is exposed to KVM instances. By default, the CPU model of KVM instance is likely QEMU Virtual CPU version x.x.x with least CPU features exposed. There are a couple of reasons to specify the CPU model:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:221
+# 55671888c52e4644b97eb76e5b37321a
+msgid "To maximise performance of instances by exposing new host CPU features to the KVM instances;"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:226
+# 0076cb899b89481ba3c5032e2156b23a
+msgid "To ensure a consistent default CPU across all machines,removing reliance of variable QEMU defaults;"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:229
+# 06f0cd9e4f7148f2bf5661eb3a4bbb30
+msgid "For the most part it will be sufficient for the host administrator to specify the guest CPU config in the per-host configuration file (/etc/cloudstack/agent/agent.properties). This will be achieved by introducing two new configuration parameters:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:239
+# 1a1c88bead1d4b90b16007da2a8049af
+msgid "There are three choices to fulfill the cpu model changes:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:243
+# 171cebf0991b4c7d82b4254c0b0a6fe7
+msgid "**custom:** you can explicitly specify one of the supported named model in /usr/share/libvirt/cpu\\_map.xml"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:248
+# ef3286604260487387d6ef81752d3ff4
+msgid "**host-model:** libvirt will identify the CPU model in /usr/share/libvirt/cpu\\_map.xml which most closely matches the host, and then request additional CPU flags to complete the match. This should give close to maximum functionality/performance, which maintaining good reliability/compatibility if the guest is migrated to another host with slightly different host CPUs."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:257
+# 80a634dd2c22483fb09655f8c07ff193
+msgid "**host-passthrough:** libvirt will tell KVM to passthrough the host CPU with no modifications. The difference to host-model, instead of just matching feature flags, every last detail of the host CPU is matched. This gives absolutely best performance, and can be important to some apps which check low level CPU details, but it comes at a cost with respect to migration: the guest can only be migrated to an exactly matching host CPU."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:265
+# f58590a9696548528006493b8c7ae197
+msgid "Here are some examples:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:269
+# 42ef165ce6ad4a9e9fa71eb044611a1b
+msgid "custom"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:278
+# 91ceb895db0b4234a51b32614603068e
+msgid "host-model"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:286
+# 9eed04f7453b40529c43301d1de02fb8
+msgid "host-passthrough"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:292
+# dfb22be926364168a84d5cb0b7e44b35
+msgid "host-passthrough may lead to migration failure,if you have this problem,you should use host-model or custom"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:295
+#: ../../hypervisor_installation.rst:3531
+# a5e533a4e79649c2ac3ce750357ee34a
+# 4d3de60d913b41398d75fad799393017
+msgid "Install and Configure libvirt"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:297
+#: ../../hypervisor_installation.rst:3533
+# bf3b3baffb30458eae7af5d56a51a573
+# fd165c09e19c4204af9a194d9e0209fb
+msgid "CloudStack uses libvirt for managing virtual machines. Therefore it is vital that libvirt is configured correctly. Libvirt is a dependency of cloudstack-agent and should already be installed."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:303
+#: ../../hypervisor_installation.rst:3539
+# ff42e0ea9cf64b509d310c0071086352
+# 5b89b062abbe4cc89b7fd10ece8eb9e8
+msgid "In order to have live migration working libvirt has to listen for unsecured TCP connections. We also need to turn off libvirts attempt to use Multicast DNS advertising. Both of these settings are in ``/etc/libvirt/libvirtd.conf``"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:308
+#: ../../hypervisor_installation.rst:3544
+# 9d2c6d97644043c98a8afdfca63ce7ba
+# 62f76e0671a940e38a4ad3785ad3829e
+msgid "Set the following parameters:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:332
+#: ../../hypervisor_installation.rst:3568
+# 7bf432c121e6497e815bce7ac5f768c2
+# 5c250e445c544d819ef81c56946c9817
+msgid "Turning on \"listen\\_tcp\" in libvirtd.conf is not enough, we have to change the parameters as well:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:335
+#: ../../hypervisor_installation.rst:3571
+# dff877a089444785a919c9a4ddc1505b
+# 09f64fb99e4f4746998fccfb45d8ffbe
+msgid "On RHEL or CentOS modify ``/etc/sysconfig/libvirtd``:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:337
+#: ../../hypervisor_installation.rst:3573
+# dc8b92c2767f4d3aa010cafa32e0ffc0
+# 5137041fbceb450dafdafdd8050d781b
+msgid "Uncomment the following line:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:343
+#: ../../hypervisor_installation.rst:3579
+# f8fa69e0aaf0441ebbd5376315dde649
+# 2c026065c68143c7abdc5ca2fc2436ea
+msgid "On Ubuntu: modify ``/etc/default/libvirt-bin``"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:345
+#: ../../hypervisor_installation.rst:3581
+# b1e0a030287c4eb99b535ef0a0e008cd
+# e7c84f512f6b40c5ae74177fcbef4e7b
+msgid "Add \"-l\" to the following line"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:351
+#: ../../hypervisor_installation.rst:3587
+# fb23df2bb85243918f17fce3511a292f
+# 3f9045ba6c8042cd95dbf7cfaf068566
+msgid "so it looks like:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:359
+#: ../../hypervisor_installation.rst:3606
+# e9f3700ad8c545ec9162775958e52903
+# 12a8cf99f91a4bfebfef63061401b984
+msgid "Restart libvirt"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:374
+#: ../../hypervisor_installation.rst:3621
+# 8a64baac6d7643dda067b886a5c80ae3
+# 396a781a4a1d4985aa57fc33ab909171
+msgid "Configure the Security Policies"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:376
+#: ../../hypervisor_installation.rst:3623
+# 071b22fa7fe84b5184dcaee305d367f9
+# ba196eddcd1a4db0b3bc5debca46897c
+msgid "CloudStack does various things which can be blocked by security mechanisms like AppArmor and SELinux. These have to be disabled to ensure the Agent has all the required permissions."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:382
+#: ../../hypervisor_installation.rst:3629
+# 66c0547791744ea9a1bf3f4b86157e56
+# a13c1564e14a40a98d164cdc3bfad868
+msgid "Configure SELinux (RHEL and CentOS)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:386
+#: ../../hypervisor_installation.rst:3633
+# ad5bbcda3fb94378926b1b5e5c49fef5
+# 3bc6b9a75a864efca77472f3a7083402
+msgid "Check to see whether SELinux is installed on your machine. If not, you can skip this section."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:389
+#: ../../hypervisor_installation.rst:3636
+# 186d81a15e7149da89ee20ce59cc48dc
+# 51df5058cd4f43938789667b0444df12
+msgid "In RHEL or CentOS, SELinux is installed and enabled by default. You can verify this with:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:398
+#: ../../hypervisor_installation.rst:3645
+# 5c9517056a764377bd38722748343a49
+# 47aa2dbec53247e09633898939b840d7
+msgid "Set the SELINUX variable in ``/etc/selinux/config`` to \"permissive\". This ensures that the permissive setting will be maintained after a system reboot."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:408
+#: ../../hypervisor_installation.rst:3655
+# 93857dbce0f54cb68f9fda82a8cd692c
+# 34854b97c968469aa89f9b69611024e4
+msgid "Change the following line"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:414
+#: ../../hypervisor_installation.rst:3661
+# 0e1313c89e3b415ebee6bbc8671f120a
+# fb6153f02ea1423088ece2501fda504f
+msgid "to this"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:422
+#: ../../hypervisor_installation.rst:3669
+# 29a646ccf1ad4545bac2923aabe1b97c
+# 80ca6532afc24061b27c23b6118bdf65
+msgid "Then set SELinux to permissive starting immediately, without requiring a system reboot."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:431
+#: ../../hypervisor_installation.rst:3678
+# 5ce95d10c98449d7b6f2c0ac20da948c
+# c3cf4cecfad547a8a307e334e4503f59
+msgid "Configure Apparmor (Ubuntu)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:435
+#: ../../hypervisor_installation.rst:3682
+# 87b92b4c575e4c95813f1e9af3b04d77
+# 07b7d10f1b3e49d8952e5b635b7eca2a
+msgid "Check to see whether AppArmor is installed on your machine. If not, you can skip this section."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:438
+#: ../../hypervisor_installation.rst:3685
+# 50e7a0a081684c489805ccda2c5717d6
+# 491c0892c7ef48b18767fafac079a62b
+msgid "In Ubuntu AppArmor is installed and enabled by default. You can verify this with:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:447
+#: ../../hypervisor_installation.rst:3694
+# 8e560cd81d0544eb8f9bb401145dea8e
+# 26d2ddef7e5f4c29a57ab9455120b3f3
+msgid "Disable the AppArmor profiles for libvirt"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:466
+#: ../../hypervisor_installation.rst:3713
+# 930e8f602c664befbf6c46bcea1cbe7e
+# 5a5ec5e627f84217a2de1c1a9692d83d
+msgid "Configure the network bridges"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:468
+#: ../../hypervisor_installation.rst:680
+#: ../../hypervisor_installation.rst:3715
+# bccb9ebfa523410e95ffbeec12d8b4df
+# c27b62ef62564bce8bbcdebbbc78a2e6
+# eaf1d1b6a92b4d26923b5a26f2d8f6e3
+msgid "This is a very important section, please make sure you read this thoroughly."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:470
+#: ../../hypervisor_installation.rst:3718
+# 37ea1b1181cf4de494d126cdc40a801d
+# 0c2793bb0202408da6ef10e2b99b6eaa
+msgid "This section details how to configure bridges using the native implementation in Linux. Please refer to the next section if you intend to use OpenVswitch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:472
+#: ../../hypervisor_installation.rst:682
+#: ../../hypervisor_installation.rst:3720
+# 2bf55b978c5a475ebcd65da90eb6386a
+# 994c7b0b85ac4fd4957bf9212cb5afbd
+# 40d0ecab11134b1f984bf6d89271cbd4
+msgid "In order to forward traffic to your instances you will need at least two bridges: *public* and *private*."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:475
+#: ../../hypervisor_installation.rst:685
+#: ../../hypervisor_installation.rst:3723
+# 68eec8c1d0fd4c34a086b108e1ba4a0b
+# 9785a42437c44a48932befa909c24f05
+# b2947b2e839f4cf9a79ddafa66b1b8e0
+msgid "By default these bridges are called *cloudbr0* and *cloudbr1*, but you do have to make sure they are available on each hypervisor."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:478
+#: ../../hypervisor_installation.rst:688
+#: ../../hypervisor_installation.rst:3726
+# fd73cf9a6c174db1a1d0a7a7b0febf8f
+# c6b6935f5a0241319a435306ff08f613
+# d7f8015ac99a49b7a8f2bdd03074f25e
+msgid "The most important factor is that you keep the configuration consistent on all your hypervisors."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:482
+#: ../../hypervisor_installation.rst:705
+#: ../../hypervisor_installation.rst:3730
+# aecc917b1cfc4ae0829bf38e71b146a1
+# dcd1dd91023f487bac62a498068bc7d3
+# 61678fddd1354bc299cc7a3f18060a1b
+msgid "Network example"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:484
+#: ../../hypervisor_installation.rst:707
+#: ../../hypervisor_installation.rst:3732
+# fcb6675f3cbf47bd84f39d85c831b62c
+# 6446967b0b204707837f42e08d7b998a
+# 116a752e270144b9ae56210887f4ad80
+msgid "There are many ways to configure your network. In the Basic networking mode you should have two (V)LAN's, one for your private network and one for the public network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:488
+#: ../../hypervisor_installation.rst:711
+#: ../../hypervisor_installation.rst:3736
+# 15d921dedb524980b41aafbd170bec51
+# 7956438fead040698f6cced9c78a2b6c
+# 8eefa91987504ceb9f915423bd9cd7ee
+msgid "We assume that the hypervisor has one NIC (eth0) with three tagged VLAN's:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:493
+#: ../../hypervisor_installation.rst:716
+#: ../../hypervisor_installation.rst:3741
+# 0877467f5181444597ffc59798a984c2
+# e05717e09bf44963b799a357f63d06c0
+# 9c3b52a0f37349628d7e9863b22f7586
+msgid "VLAN 100 for management of the hypervisor"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:497
+#: ../../hypervisor_installation.rst:720
+#: ../../hypervisor_installation.rst:3745
+# d0358c8e6e704280a94d8154520cc512
+# 9d4164a76748495290ea59d97dfde5f0
+# 7db7cbd5fdbd485cab9d24025b7d7812
+msgid "VLAN 200 for public network of the instances (cloudbr0)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:501
+#: ../../hypervisor_installation.rst:724
+#: ../../hypervisor_installation.rst:3749
+# 1f92bbd42f4848b7824c11163deccdce
+# 386e672345ad4798b937956aa78f982d
+# bca715eb0552403c97ecabf386e7ba9c
+msgid "VLAN 300 for private network of the instances (cloudbr1)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:503
+#: ../../hypervisor_installation.rst:726
+#: ../../hypervisor_installation.rst:3751
+# aa94795c65f344c89c206c32fe15d941
+# 48a286c49f7441b19ed5ef3435348d59
+# dc43104aac9543c78fafa5f30dffaa8b
+msgid "On VLAN 100 we give the Hypervisor the IP-Address 192.168.42.11/24 with the gateway 192.168.42.1"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:506
+#: ../../hypervisor_installation.rst:729
+#: ../../hypervisor_installation.rst:3754
+# 6d48a58cd57f46238b8aaf12909c69d1
+# b8bb257a296c4bed98f1dad806ad5ba1
+# 900d19465df34526bfc636edfdb5534c
+msgid "The Hypervisor and Management server don't have to be in the same subnet!"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:509
+#: ../../hypervisor_installation.rst:732
+#: ../../hypervisor_installation.rst:3757
+# c32119ed14d44cb8bc32676656b99910
+# d879c320747d4850b1c5bacdd29a1669
+# 83f2160f524f43cf869a63489a608275
+msgid "Configuring the network bridges"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:511
+#: ../../hypervisor_installation.rst:3759
+# a80e5f8891a44a56affd76a4611c1785
+# c623ed65e9ba45b89f407ce4339a56e1
+msgid "It depends on the distribution you are using how to configure these, below you'll find examples for RHEL/CentOS and Ubuntu."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:514
+#: ../../hypervisor_installation.rst:3762
+# 1bb4087b2e5548119e9075fa05467ff9
+# 1992bd1a538a4e87aff11f08a30811ca
+msgid "The goal is to have two bridges called 'cloudbr0' and 'cloudbr1' after this section. This should be used as a guideline only. The exact configuration will depend on your network layout."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:517
+#: ../../hypervisor_installation.rst:759
+#: ../../hypervisor_installation.rst:3765
+# adab06c881724079959a8ae96aa924d0
+# 4978f5c0d9024cceb5523422d9f6e3c3
+# b5304e1cd17b43d49387c9e1f0dc4600
+msgid "Configure in RHEL or CentOS"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:519
+#: ../../hypervisor_installation.rst:3767
+# 95d2aaf4ea374d68ab231cf69aa771db
+# 6ee3e4cd4ddd42eda7adf6a56c2de197
+msgid "The required packages were installed when libvirt was installed, we can proceed to configuring the network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:522
+#: ../../hypervisor_installation.rst:764
+#: ../../hypervisor_installation.rst:3770
+# 029a729a30a646bb882fa28fc6f4faf5
+# 13fa6771f34e4579bc8dba5e243a4011
+# d8e2cd1aa3de4613894102d0d8dfc562
+msgid "First we configure eth0"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:528
+#: ../../hypervisor_installation.rst:770
+#: ../../hypervisor_installation.rst:3776
+# dfdfd4f9776841959c87e33436d420ff
+# a055bef8a0304bf0827ea85c3116ff08
+# 175ef63f2d0e4d568e5df9298b56ef1f
+msgid "Make sure it looks similar to:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:539
+#: ../../hypervisor_installation.rst:3787
+# aa158cdf890f4a73aa02cee971b29325
+# 937d87800fba4c0c93874a7e1764bf85
+msgid "We now have to configure the three VLAN interfaces:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:588
+#: ../../hypervisor_installation.rst:3836
+# 476469f3cb3a44b0b7782a599edaaf84
+# 9fcd4bb8ee1f4977b938630771b1dab2
+msgid "Now we have the VLAN interfaces configured we can add the bridges on top of them."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:595
+#: ../../hypervisor_installation.rst:3843
+# d77a52bf367046fdbce73058d169f265
+# d2eac1f518d24368b764df3e08aacb22
+msgid "Now we just configure it is a plain bridge without an IP-Address"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:608
+#: ../../hypervisor_installation.rst:3856
+# 0188228d5cff43fc939e85ab6c002118
+# 39f78adfcd624290b0564d41b3447db2
+msgid "We do the same for cloudbr1"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:625
+#: ../../hypervisor_installation.rst:672
+#: ../../hypervisor_installation.rst:840
+#: ../../hypervisor_installation.rst:3873
+#: ../../hypervisor_installation.rst:3920
+# 218608446e8e45528b00bea4c57ebab9
+# f929fa3761b04167bda58c3a6f67cbfa
+# cdec6d4dfc5f4e95a212712a3bc64a61
+# dde4ad6a203a4cd58b6fe12d2f745b30
+# 2210405cea3845758c377fea3f5a3a2e
+msgid "With this configuration you should be able to restart the network, although a reboot is recommended to see if everything works properly."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:628
+#: ../../hypervisor_installation.rst:675
+#: ../../hypervisor_installation.rst:843
+#: ../../hypervisor_installation.rst:3876
+#: ../../hypervisor_installation.rst:3923
+# 9ced5c3d4eeb4f27b12cd0cb9f044a90
+# b88351fb9a7b43b09d7230cb38ae4c58
+# 1f463bc97d1147db85bec0e461319336
+# de08a3e8c75f461ea791f59685988cb5
+# a0974a28a6fa4008ae279ad0685d47f5
+msgid "Make sure you have an alternative way like IPMI or ILO to reach the machine in case you made a configuration error and the network stops functioning!"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:631
+#: ../../hypervisor_installation.rst:3879
+# 17acbbca1f3345849046fa6c4ebed4fc
+# 8cdc0e43e63641789dc4bd075c3d0bc3
+msgid "Configure in Ubuntu"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:633
+#: ../../hypervisor_installation.rst:3881
+# 41f30048a88c4bb993a0d890f181b28d
+# 93e837e2bf274c668eee8f0a619c4a5d
+msgid "All the required packages were installed when you installed libvirt, so we only have to configure the network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:640
+#: ../../hypervisor_installation.rst:3888
+# 01fb8740e0b9423d8b655864775af54e
+# 262554e455a648fabdf442b6e301f259
+msgid "Modify the interfaces file to look like this:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:678
+# e332c16e171f47169b256805eafe7615
+msgid "Configure the network using OpenVswitch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:692
+# aa202fe73fee4c45827aa38313f60aec
+msgid "Preparing"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:694
+# eca14b3123854338ba1f14a14829b739
+msgid "To make sure that the native bridge module will not interfere with openvswitch the bridge module should be added to the blacklist. See the modprobe documentation for your distribution on where to find the blacklist. Make sure the module is not loaded either by rebooting or executing rmmod bridge before executing next steps."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:700
+# bf7a4c48ba2a4e4fa616e9e4415abcc7
+msgid "The network configurations below depend on the ifup-ovs and ifdown-ovs scripts which are part of the openvswitch installation. They should be installed in /etc/sysconfig/network-scripts/"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:734
+# 4d690db0a1544fd29d71656ec0ffcefd
+msgid "It depends on the distribution you are using how to configure these, below you'll find examples for RHEL/CentOS."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:737
+# ee8734ea127c4e8f8b66e5c4dea71bbf
+msgid "The goal is to have three bridges called 'mgmt0', 'cloudbr0' and 'cloudbr1' after this section. This should be used as a guideline only. The exact configuration will depend on your network layout."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:740
+# a74c6627f02043d5be917f12e7d0b263
+msgid "Configure OpenVswitch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:742
+# e34d3c3a549a4b5e90ffd8f8afa33b07
+msgid "The network interfaces using OpenVswitch are created using the ovs-vsctl command. This command will configure the interfaces and persist them to the OpenVswitch database."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:746
+# fc0396cdb2c247b4ba0851d2b478d8c9
+msgid "First we create a main bridge connected to the eth0 interface. Next we create three fake bridges, each connected to a specific vlan tag."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:761
+# 02df0e7f19b4486bbaada2d6b794b9ad
+msgid "The required packages were installed when openvswitch and libvirt were installed, we can proceed to configuring the network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:781
+# afab5f01a1714f0cb60ff9eed2db599d
+msgid "We have to configure the base bridge with the trunk."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:796
+# e104896bad1742b5b84682172fbd9b32
+msgid "We now have to configure the three VLAN bridges:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:846
+#: ../../hypervisor_installation.rst:3926
+# 3564d9d50ea44f139e404791fd72f0af
+# 02fce31af22c4ed5abbd727f13ad05f0
+msgid "Configuring the firewall"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:848
+#: ../../hypervisor_installation.rst:3928
+# 2db1d0f133da4a66a7b2907acedd42a9
+# 5b0f650e2d114047a0415b7ea57f3251
+msgid "The hypervisor needs to be able to communicate with other hypervisors and the management server needs to be able to reach the hypervisor."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:851
+#: ../../hypervisor_installation.rst:3931
+# 935242b052ff490e9ad7270b8ddce890
+# 8c950a2e6b57475fa7752ffa9ed1e5bd
+msgid "In order to do so we have to open the following TCP ports (if you are using a firewall):"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:856
+#: ../../hypervisor_installation.rst:3936
+# cb69e4cdb8684774badfb4574559faa0
+# ae914c26a05444f9837e3ea892d275e2
+msgid "22 (SSH)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:860
+#: ../../hypervisor_installation.rst:3940
+# 3807a267ba4b47248846cb82be68d71e
+# 8d4a188d4a5c42408f9a9da6c952d345
+msgid "1798"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:864
+#: ../../hypervisor_installation.rst:3944
+# 87b8b1e5c9924af5b368bcbb7d2e8148
+# 130a835b7e534e1aad8b66a350c80a9c
+msgid "16509 (libvirt)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:868
+#: ../../hypervisor_installation.rst:3948
+# eb66ea04a90b4b46bd6c5529c74201b7
+# 332c2e7a9cdc40909b84e4bb4a550a92
+msgid "5900 - 6100 (VNC consoles)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:872
+#: ../../hypervisor_installation.rst:3952
+# a65af6b9acbf47a08b1f7222b105fd4f
+# 709185e3e76045d6a3a6d0df2f61efb3
+msgid "49152 - 49216 (libvirt live migration)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:874
+#: ../../hypervisor_installation.rst:3954
+# aa084591023a46ccb4cea81e8cc0baea
+# bc3288c0a792458c9d188c275d27a458
+msgid "It depends on the firewall you are using how to open these ports. Below you'll find examples how to open these ports in RHEL/CentOS and Ubuntu."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:878
+#: ../../hypervisor_installation.rst:3958
+# 7129650cbfc6416d8d015c4a64781ac8
+# 65d598aa7b414f5393a37799d4c2c1a2
+msgid "Open ports in RHEL/CentOS"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:880
+#: ../../hypervisor_installation.rst:3960
+# bb6efe14098442169446a2cfaf0ddfa0
+# e5bb8f2688ff41b98cf556f60758aa87
+msgid "RHEL and CentOS use iptables for firewalling the system, you can open extra ports by executing the following iptable commands:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:903
+#: ../../hypervisor_installation.rst:3983
+# d68286a4499a42d0af59d58cf3307ce8
+# cabb0609f32c4af983aec749c9a3bde6
+msgid "These iptable settings are not persistent accross reboots, we have to save them first."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:911
+#: ../../hypervisor_installation.rst:3991
+# 307b4260b7a74cd392d59bb3418c7eb8
+# a54b92341f454cf3aee68b8a07bd8108
+msgid "Open ports in Ubuntu"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:913
+#: ../../hypervisor_installation.rst:3993
+# 8f7697ea5cda4eeeae5602b276f55313
+# ca6e09ab840f496fa590a392c3c0fcb1
+msgid "The default firewall under Ubuntu is UFW (Uncomplicated FireWall), which is a Python wrapper around iptables."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:916
+#: ../../hypervisor_installation.rst:3996
+# 036e661454dd43b6bcf5724a4cfc8e21
+# 63b5466496e643e5adac39e7c08d34f7
+msgid "To open the required ports, execute the following commands:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:938
+#: ../../hypervisor_installation.rst:4019
+# d199e9f02aa34c2e998aba25484840c8
+# f7ee2acc10334a4bb43bb2cb66688c77
+msgid "By default UFW is not enabled on Ubuntu. Executing these commands with the firewall disabled does not enable the firewall."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:941
+#: ../../hypervisor_installation.rst:4022
+# f6fb4b8f7864465a8e8b2c9c726ec59c
+# 16dd0d2c501d4beea5ff4ef875698cd4
+msgid "Add the host to CloudStack"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:949
+# 870fb106f927434690fac18321ce0e59
+msgid "Hypervisor Support for Primary Storage"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:951
+# 11b373255a32403a97695fb159fd09d9
+msgid "The following table shows storage options and parameters for different hypervisors."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:955
+# 71d9dffcec0844acb2949eb60cea1944
+msgid "Primary Storage Type"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:955
+# 0b37e00477ab432691d060c0c73f3257
+msgid "vSphere"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:955
+# 7129c9b88c17431f9d16cb9947a677a7
+msgid "XenServer"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:955
+# 71094f1d15124724a6a0e6213b1d6daf
+msgid "KVM"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:955
+#: ../../hypervisor_installation.rst:1963
+# 09568b1f16e7426cab559aa9770bb87e
+# cfd57be6b2324793bc6c05ad29e6f751
+msgid "Hyper-V"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:957
+# 7046ca99b00143a18a1ac6585ea583d5
+msgid "****Format for Disks, Templates, and Snapshots****"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:957
+# 5ab36f207b4146588dd7917af86aa5b7
+msgid "VMDK"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:957
+#: ../../hypervisor_installation.rst:957
+# 1d7d1640e1344432b8b4c9f64e6e3de5
+# e52e9c78a0de4ad8960d9ed8d6604e7d
+msgid "VHD"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:957
+# 73411b9629ba423fa63a082dc31e04af
+msgid "QCOW2"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:958
+# e66d4e3fef6549cd950eb5a969eaec5a
+msgid "**iSCSI support**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:958
+#: ../../hypervisor_installation.rst:959
+# 6791f19ffe8c492383fd9e09030fe664
+# 9f409f8d387c4d46becc2b3ee6499050
+msgid "VMFS"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:958
+# 6a8d18eb6310463b8b26ce7341385c5d
+msgid "CLVM"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:958
+#: ../../hypervisor_installation.rst:959
+# 155ee7758b3b41aabd23851828723f07
+# 9b26e9f40b634c0d9829308022399474
+msgid "Yes, via Shared Mountpoint"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:958
+#: ../../hypervisor_installation.rst:959
+#: ../../hypervisor_installation.rst:960
+#: ../../hypervisor_installation.rst:962
+#: ../../hypervisor_installation.rst:963
+#: ../../hypervisor_installation.rst:963
+#: ../../hypervisor_installation.rst:963
+# ebeb1e87b3f440c0a9fa499698356297
+# 0b052a6c7d9a489ba64df2bf64913d0d
+# 3111e9e35d434428bd654afbef6e4661
+# 90ea1419362d4e61bdbbde02d29a56a9
+# 67db36f9276b461a9f2dc0a6c75a84f3
+# 48b9e13cfdf048599e7c03490006ccb4
+# 16b7d2f7dac94f76a225e10445cf619f
+msgid "No"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:959
+# 7d8573527e8a4bfba998b4d3ddf99bb7
+msgid "**Fiber Channel support**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:959
+# 451dcefc9c6c470491dfea9998e24809
+msgid "Yes, via Existing SR"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:960
+# d36f043836cb43d9b60ee86d2ad41f62
+msgid "**NFS support**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:960
+#: ../../hypervisor_installation.rst:960
+#: ../../hypervisor_installation.rst:960
+#: ../../hypervisor_installation.rst:961
+#: ../../hypervisor_installation.rst:961
+#: ../../hypervisor_installation.rst:961
+#: ../../hypervisor_installation.rst:961
+#: ../../hypervisor_installation.rst:963
+# 50ad2c0fcf9644c9a4a7c65f8ddcb5fa
+# b7dc2cbb224a4aa886eb6e569412cc82
+# 80a2fd8cf583437ebb542a1d060a0042
+# d06590ec3fc948149d7dd2172c4f6b06
+# be7e08adfd054b1ba87844c789deb247
+# f29c49b5074b4c57a993f973a89e4c78
+# 54d3e136689647ed8412737ac2ba6b93
+# 140e1d436e5343bf99920962e3cb2fc0
+msgid "Yes"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:961
+# ac8413ce909b4b7395fadd007b26c9ff
+msgid "**Local storage support**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:962
+# 24ab7203b4c943739c6926678f0d0803
+msgid "**Storage over-provisioning**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:962
+# e2e7fabe2be14351b704696cea18fa20
+msgid "NFS and iSCSI"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:962
+#: ../../hypervisor_installation.rst:962
+# 39253a1a6513430b8e09aaf5098c74ef
+# 42778c796f7740bf85e16e509c1496f4
+msgid "NFS"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:963
+# b9588ec4a2be4b1696503c5e85cc3a84
+msgid "**SMB/CIFS**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:966
+# 7644794bf16d47c18ed02b558352bea1
+msgid "XenServer uses a clustered LVM system to store VM images on iSCSI and Fiber Channel volumes and does not support over-provisioning in the hypervisor. The storage server itself, however, can support thin-provisioning. As a result the CloudStack can still support storage over-provisioning by running on thin-provisioned storage volumes."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:972
+# d20bddfa830e48d99978bd5eab502169
+msgid "KVM supports \"Shared Mountpoint\" storage. A shared mountpoint is a file system path local to each server in a given cluster. The path must be the same across all Hosts in the cluster, for example /mnt/primary1. This shared mountpoint is assumed to be a clustered filesystem such as OCFS2. In this case the CloudStack does not attempt to mount or unmount the storage as is done with NFS. The CloudStack requires that the administrator insure that the storage is available"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:980
+# 8cc2529993044886a2edc38f568aa43d
+msgid "With NFS storage, CloudStack manages the overprovisioning. In this case the global configuration parameter storage.overprovisioning.factor controls the degree of overprovisioning. This is independent of hypervisor type."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:985
+# b1c2b65035cd42b5b242d8245827be53
+msgid "Local storage is an option for primary storage for vSphere, XenServer, and KVM. When the local disk option is enabled, a local disk storage pool is automatically created on each host. To use local storage for the System Virtual Machines (such as the Virtual Router), set system.vm.use.local.storage to true in global configuration."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:991
+# 2874ceeecfc747368a0daa2f4b670a8d
+msgid "CloudStack supports multiple primary storage pools in a Cluster. For example, you could provision 2 NFS servers in primary storage. Or you could provision 1 iSCSI LUN initially and then add a second iSCSI LUN when the first approaches capacity."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:997
+# bb8410c437ae4dfc83006d467deab5ee
+msgid "Citrix XenServer Installation for CloudStack"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:999
+# f039a87fd91f4cf5af82b5a0d0e14279
+msgid "If you want to use the Citrix XenServer hypervisor to run guest virtual machines, install XenServer 6.0 or XenServer 6.0.2 on the host(s) in your cloud. For an initial installation, follow the steps below. If you have previously installed XenServer and want to upgrade to another version, see :ref:`upgrading-xenserver-version`."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1006
+# 1393db47eb314f93ac51b5df28608757
+msgid "System Requirements for XenServer Hosts"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1010
+# cee59e8c9fbe4466b998c22c775285aa
+msgid "The host must be certified as compatible with one of the following. See the Citrix Hardware Compatibility Guide: `http://hcl.xensource.com <http://hcl.xensource.com>`_"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1014
+# f3b55d603c69440cac3ff406039da6fa
+msgid "XenServer 5.6 SP2"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1015
+# be0e05f590c548658fc054e3b7c183c4
+msgid "XenServer 6.0"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1016
+# 859b34a50d8a47b98924d9bc9e66bf34
+msgid "XenServer 6.0.2"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1017
+# f62ad598aa04405db735768bcd28f3cb
+msgid "XenServer 6.1.0"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1018
+# 1ef19600bf954890ba8ab95144a9dbe9
+msgid "XenServer 6.2.0"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1022
+# 7f67c993b17a4b25a8b436331132a38b
+msgid "You must re-install Citrix XenServer if you are going to re-use a host from a previous install."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1031
+# 79b4544cf3614dd7a7be4fb67c18c3cc
+msgid "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."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1042
+# 00bde44b482f4ea297f009d4d8544f68
+msgid "All hosts within a cluster must be homogeneous. The CPUs must be of the same type, count, and feature flags."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1047
+# 1cc62dcb812144349e992ef157bc7f1e
+msgid "Must support HVM (Intel-VT or AMD-V enabled in BIOS)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1055
+#: ../../hypervisor_installation.rst:2267
+# 7f48c8f440f3456a9675ec430f73fa14
+# 91c80a6655bf4e15999366adc5579b63
+msgid "Hardware virtualization support required"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1063
+#: ../../hypervisor_installation.rst:2275
+# edf681afdf084f4d95b31b905feef83e
+# b0c94baa01744e5d9a09a5a1a9be638f
+msgid "36 GB of local disk"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1071
+#: ../../hypervisor_installation.rst:2283
+# 2627aa6551664c18b24d53f01d85fdc9
+# 7d643f0e7d854677adf01b1b91684194
+msgid "Statically allocated IP Address"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1078
+# 86b1054dd7df47728888bb09e899e58e
+msgid "The lack of up-do-date hotfixes can lead to data corruption and lost VMs."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1081
+# ffb7f7e0b7d54edd842322b6dbd130bc
+msgid "XenServer Installation Steps"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1085
+# d29bd0f1992445e7bfe899ec7fdcd3bc
+msgid "From `https://www.citrix.com/English/ss/downloads/ <https://www.citrix.com/English/ss/downloads/>`_, download the appropriate version of XenServer for your CloudStack version (see `\"System Requirements for XenServer Hosts\" <#system-requirements-for-xenserver-hosts>`_). Install it using the Citrix XenServer Installation Guide."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1091
+# e4ff84caeefa4cdb9ff96d78ed4795bc
+msgid "Older Versions of XenServer:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1093
+# dfbef4c3b3e74946805482a145c437ea
+msgid "Note that you can download the most recent release of XenServer without having a Citrix account. If you wish to download older versions, you will need to create an account and look through the download archives."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1099
+# a1f3be6636a2457095084a99017c2bef
+msgid "Configure XenServer dom0 Memory"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1101
+# 3d95fa3b3a0e4b1eb92dd506d58da069
+msgid "Configure the XenServer dom0 settings to allocate more memory to dom0. This can enable XenServer to handle larger numbers of virtual machines. We recommend 2940 MB of RAM for XenServer dom0. For instructions on how to do this, see `http://support.citrix.com/article/CTX126531 <http://support.citrix.com/article/CTX126531>`_. The article refers to XenServer 5.6, but the same information applies to XenServer 6.0."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1110
+# 9e46ff13cb284bb9bdfbe4141e984bc3
+msgid "Username and Password"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1112
+# 47b11d036dff42a990eebaab43d6265b
+msgid "All XenServers in a cluster must have the same username and password as configured in CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1116
+# 04e9a76db62743b99541eca7808c3339
+msgid "Time Synchronization"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1118
+# 9fa198ee495f4b84b0bba7fd628e2e92
+msgid "The host must be set to use NTP. All hosts in a pod must have the same time."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1123
+# 4726eec6f10347b99a5e8076a1285988
+msgid "Install NTP."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1131
+# 5682aee95db547028f5e82cd70b046d7
+msgid "Edit the NTP configuration file to point to your NTP server."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1137
+# 1ce6772b97fb4129b0a526a33bfd18fa
+msgid "Add one or more server lines in this file with the names of the NTP servers you want to use. For example:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1149
+# 69791d782a3541ca94d6c4751ec78f1f
+msgid "Restart the NTP client."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1157
+# 3b608298222445408c6e4d00c8b36707
+msgid "Make sure NTP will start again upon reboot."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1165
+# 0fcd0d55ec7049b69a3427a227e67180
+msgid "Install CloudStack XenServer Support Package (CSP)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1167
+# ae16a3a52b0343d8b17bdbe5440015f1
+msgid "(Optional)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1169
+# 030bdd1824914aac90fb1170106765ba
+msgid "To enable security groups, elastic load balancing, and elastic IP on XenServer, download and install the CloudStack XenServer Support Package (CSP). After installing XenServer, perform the following additional steps on each XenServer host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1176
+# 41fcedb714c14a428ca6a9efe5a1d42f
+msgid "Download the CSP software onto the XenServer host from one of the following links:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1179
+# f29bec21956d4917be7874f1b6a4177e
+msgid "For XenServer 6.0.2:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1181
+# 54880e3acb4945b4ae3d3fb251252130
+msgid "`http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz>`_"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1183
+# 4405c659cea34cb2895c0f43693473f1
+msgid "For XenServer 5.6 SP2:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1185
+# b1533b01dec04d8ea37cb07d541d8013
+msgid "`http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz>`_"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1187
+# 994df5c8945149b7b8663a2e603fc847
+msgid "For XenServer 6.0:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1189
+# bc80c4fa363248c292882b511d90808a
+msgid "`http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz>`_"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1193
+# 09db532336c943caa7e4713f7f57deaa
+msgid "Extract the file:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1201
+#: ../../hypervisor_installation.rst:1825
+# 08830377e2e845879acf2acd9cb55ecf
+# aa4d385951184c16a90f45c0c3c5137a
+msgid "Run the following script:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1209
+# 72924509d484445a81886c53211f2d14
+msgid "If the XenServer host is part of a zone that uses basic networking, disable Open vSwitch (OVS):"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1216
+# adb679b9cadf4ab587ebaa643690988a
+msgid "Restart the host machine when prompted."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1218
+# bd826e8c78c04cf2ac613043dd1aa8ef
+msgid "The XenServer host is now ready to be added to CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1221
+# 4d2cc4a9829c43c79dffee9dffb52d68
+msgid "Primary Storage Setup for XenServer"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1223
+# b0cc4d49e6d34d9db259e314792c0177
+msgid "CloudStack natively supports NFS, iSCSI and local storage. If you are using one of these storage types, there is no need to create the XenServer Storage Repository (\"SR\")."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1227
+# a62837dbc9e1484d9a2ec93a3f386570
+msgid "If, however, you would like to use storage connected via some other technology, such as FiberChannel, you must set up the SR yourself. To do so, perform the following steps. If you have your hosts in a XenServer pool, perform the steps on the master node. If you are working with a single XenServer which is not part of a cluster, perform the steps on that XenServer."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1236
+# 81eef0c2ce0249b3a2530d8dd37184b8
+msgid "Connect FiberChannel cable to all hosts in the cluster and to the FiberChannel storage host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1241
+# b7ae02e3677b4008a1be03a37f030f35
+msgid "Rescan the SCSI bus. Either use the following command or use XenCenter to perform an HBA rescan."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1250
+# 0476baafcfbc4751a7b674d69113d59f
+msgid "Repeat step 2 on every host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1254
+# 02f48106fb6144b7b2382f5073d07199
+msgid "Check to be sure you see the new SCSI disk."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1260
+# 37c8fa1fc8f84752a31863e7c7d8120d
+msgid "The output should look like this, although the specific file name will be different (scsi-<scsiID>):"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1270
+# d30a16069dcf439f859e28c39d871bdb
+msgid "Repeat step 4 on every host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1274
+# d057bb9cd0164ff2af5b7b284a2f70bc
+msgid "On the storage server, run this command to get a unique ID for the new SR."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1281
+# 78a081f2a72e4bea8db0fd3c3d5789df
+msgid "The output should look like this, although the specific ID will be different:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1290
+# faf5a8ab93ff4086828b6dc2491f0fd4
+msgid "Create the FiberChannel SR. In name-label, use the unique ID you just generated."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1299
+# c1a12adfd4e246b9ad5592e39b85708c
+msgid "This command returns a unique ID for the SR, like the following example (your ID will be different):"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1308
+# f32c1d33fc9f40779169b42513227c6b
+msgid "To create a human-readable description for the SR, use the following command. In uuid, use the SR ID returned by the previous command. In name-description, set whatever friendly text you prefer."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1316
+# b754f3a8e4df433090a93bb35257fecd
+msgid "Make note of the values you will need when you add this storage to CloudStack later (see `\"Add Primary Storage\" <configuration.html#add-primary-storage>`_). In the Add Primary Storage dialog, in Protocol, you will choose PreSetup. In SR Name-Label, you will enter the name-label you set earlier (in this example, e6849e96-86c3-4f2c-8fcc-350cc711be3d)."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1324
+# bb2c0a059376456fb6bca7407c545e10
+msgid "(Optional) If you want to enable multipath I/O on a FiberChannel SAN, refer to the documentation provided by the SAN vendor."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1328
+# f948cd8634034bd188d213da27d061f1
+msgid "iSCSI Multipath Setup for XenServer (Optional)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1330
+# 2f15691307f84faaade1ec0f85382c0a
+msgid "When setting up the storage repository on a Citrix XenServer, you can enable multipath I/O, which uses redundant physical components to provide greater reliability in the connection between the server and the SAN. To enable multipathing, use a SAN solution that is supported for Citrix servers and follow the procedures in Citrix documentation. The following links provide a starting point:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1339
+# c3e151c53ba543aa9a5c48cd1282a74b
+msgid "`http://support.citrix.com/article/CTX118791 <http://support.citrix.com/article/CTX118791>`_"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1343
+# 341d6153e8204ea697144d7f714fd80d
+msgid "`http://support.citrix.com/article/CTX125403 <http://support.citrix.com/article/CTX125403>`_"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1345
+# d88b03c3c9134875a81d6f6fcda13a65
+msgid "You can also ask your SAN vendor for advice about setting up your Citrix repository for multipathing."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1348
+# 01ad0cb79f9448c48d411af178ff801e
+msgid "Make note of the values you will need when you add this storage to the CloudStack later (see `\"Add Primary Storage\" <configuration.html#add-primary-storage>`_). In the Add Primary Storage dialog, in Protocol, you will choose PreSetup. In SR Name-Label, you will enter the same name used to create the SR."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1353
+# d447c7f93a09485c9104d3e0c6f30ed4
+msgid "If you encounter difficulty, address the support team for the SAN provided by your vendor. If they are not able to solve your issue, see Contacting Support."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1358
+# 3462935ca70247d4ad640ed9fc026627
+msgid "Physical Networking Setup for XenServer"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1360
+# 96146639e1894252a9993fb4085347e3
+msgid "Once XenServer has been installed, you may need to do some additional network configuration. At this point in the installation, you should have a plan for what NICs the host will have and what traffic each NIC will carry. The NICs should be cabled as necessary to implement your plan."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1366
+# f28bb641121f436ca9f8198d73026c0c
+msgid "If you plan on using NIC bonding, the NICs on all hosts in the cluster must be cabled exactly the same. For example, if eth0 is in the private bond on one host in a cluster, then eth0 must be in the private bond on all hosts in the cluster."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1371
+# b85094b7061646f493d481b41f4f5d9b
+msgid "The IP address assigned for the management network interface must be static. It can be set on the host itself or obtained via static DHCP."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1374
+# f4eaab06e1894ba28c9a3ee1c8fd19e2
+msgid "CloudStack configures network traffic of various types to use different NICs or bonds on the XenServer host. You can control this process and provide input to the Management Server through the use of XenServer network name labels. The name labels are placed on physical interfaces or bonds and configured in CloudStack. In some simple cases the name labels are not required."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1381
+# de56a32c98eb4628a39e7d67f51d4762
+msgid "When configuring networks in a XenServer environment, network traffic labels must be properly configured to ensure that the virtual interfaces are created by CloudStack are bound to the correct physical device. The name-label of the XenServer network must match the XenServer traffic label specified while creating the CloudStack network. This is set by running the following command:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1393
+# 615cf9185dd24899b715f67bf68619ce
+msgid "Configuring Public Network with a Dedicated NIC for XenServer (Optional)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1395
+# 3c82b6119dda4300b8573ec15d8e2700
+msgid "CloudStack supports the use of a second NIC (or bonded pair of NICs, described in :ref:`nic-bonding-for-xenserver`) for the public network. If bonding is not used, the public network can be on any NIC and can be on different NICs on the hosts in a cluster. For example, the public network can be on eth0 on node A and eth1 on node B. However, the XenServer name-label for the public network must be identical across all hosts. The following examples set the network label to \"cloud-public\". After the management server is installed and running you must configure it with the name of the chosen network label (e.g. \"cloud-public\"); this is discussed in `\"Management Server Installation\" <installation.html#management-server-installation>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1406
+# 110691d610d44e6abc3b85a434281c45
+msgid "If you are using two NICs bonded together to create a public network, see :ref:`nic-bonding-for-xenserver`."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1409
+# 5eeb0c63f90641ba8ae5b6652fb43ac5
+msgid "If you are using a single dedicated NIC to provide public network access, follow this procedure on each new host that is added to CloudStack before adding the host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1415
+# 06ff995c8cd147ecbee8398ae114eb8f
+msgid "Run xe network-list and find the public network. This is usually attached to the NIC that is public. Once you find the network make note of its UUID. Call this <UUID-Public>."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1421
+# bd31c6c93f934071bb6a514d4b1b50ca
+msgid "Run the following command."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1428
+# d2be307f51684ed299d0d6b382616d08
+msgid "Configuring Multiple Guest Networks for XenServer (Optional)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1430
+# 52d7d8db9ce2409e83475cdad3955a33
+msgid "CloudStack supports the use of multiple guest networks with the XenServer hypervisor. Each network is assigned a name-label in XenServer. For example, you might have two networks with the labels \"cloud-guest\" and \"cloud-guest2\". After the management server is installed and running, you must add the networks and use these labels so that CloudStack is aware of the networks."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1437
+# 8a5be9e0828c4730b3dcb0b852e2220f
+msgid "Follow this procedure on each new host before adding the host to CloudStack:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1442
+# 3634bb596dba4e22b7ea59c50eb2f1ef
+msgid "Run xe network-list and find one of the guest networks. Once you find the network make note of its UUID. Call this <UUID-Guest>."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1447
+# 786c3d9e0de241399b68a3ab7c3069cc
+msgid "Run the following command, substituting your own name-label and uuid values."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1456
+# 562afb7e19cf4d4381e2ec0f140e5e61
+msgid "Repeat these steps for each additional guest network, using a different name-label and uuid each time."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1460
+# 41b48003990c4afdb4b6b8a96f1513cd
+msgid "Separate Storage Network for XenServer (Optional)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1462
+# d1c730db57c24a7da597f35913fe72f0
+msgid "You can optionally set up a separate storage network. This should be done first on the host, before implementing the bonding steps below. This can be done using one or two available NICs. With two NICs bonding may be done as above. It is the administrator's responsibility to set up a separate storage network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1468
+# 5077124054fc4ba3b593435b5bd5b709
+msgid "Give the storage network a different name-label than what will be given for other networks."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1471
+# 2c93ae198ee746f7b38008dc9aaa2b63
+msgid "For the separate storage network to work correctly, it must be the only interface that can ping the primary storage device's IP address. For example, if eth0 is the management network NIC, ping -I eth0 <primary storage device IP> must fail. In all deployments, secondary storage devices must be pingable from the management network NIC or bond. If a secondary storage device has been placed on the storage network, it must also be pingable via the storage network NIC or bond on the hosts as well."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1480
+# 5dc74fbf37884dd1a441515d7ccb3739
+msgid "You can set up two separate storage networks as well. For example, if you intend to implement iSCSI multipath, dedicate two non-bonded NICs to multipath. Each of the two networks needs a unique name-label."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1484
+# 21486bfc4a50447a974137680f2e8750
+msgid "If no bonding is done, the administrator must set up and name-label the separate storage network on all hosts (masters and slaves)."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1487
+# e74b734827c148e4abf67add41daf5fa
+msgid "Here is an example to set up eth5 to access a storage network on 172.16.0.0/24."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1500
+# 4c8478c9b0404061b4f0eb4cf916b145
+msgid "NIC Bonding for XenServer (Optional)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1502
+# dc0584c53b15404da1bd19bd6ee782bf
+msgid "XenServer supports Source Level Balancing (SLB) NIC bonding. Two NICs can be bonded together to carry public, private, and guest traffic, or some combination of these. Separate storage networks are also possible. Here are some example supported configurations:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1509
+# 585023d3f7b24463a959419863701154
+msgid "2 NICs on private, 2 NICs on public, 2 NICs on storage"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1513
+# 85ce9960f5f64e7e81103c42a25c7992
+msgid "2 NICs on private, 1 NIC on public, storage uses management network"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1517
+# 766a18c82a444b0f9940f362c82e2922
+msgid "2 NICs on private, 2 NICs on public, storage uses management network"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1521
+# a559ff80b0a94e9799389702be54cf19
+msgid "1 NIC for private, public, and storage"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1523
+# b92a690f72754add8ee271cf1ba240f1
+msgid "All NIC bonding is optional."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1525
+# 26835cc7c2844c809af0dc5a4cfc4742
+msgid "XenServer expects all nodes in a cluster will have the same network cabling and same bonds implemented. In an installation the master will be the first host that was added to the cluster and the slave hosts will be all subsequent hosts added to the cluster. The bonds present on the master set the expectation for hosts added to the cluster later. The procedure to set up bonds on the master and slaves are different, and are described below. There are several important implications of this:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1535
+# 422eb3cde8234e3a8e6269cdb3548d5a
+msgid "You must set bonds on the first host added to a cluster. Then you must use xe commands as below to establish the same bonds in the second and subsequent hosts added to a cluster."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1541
+# c3572859ed994bf79cccdac0dc036ada
+msgid "Slave hosts in a cluster must be cabled exactly the same as the master. For example, if eth0 is in the private bond on the master, it must be in the management network for added slave hosts."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1546
+# 50715edffb014ce094ecfdcfc1429bc7
+msgid "Management Network Bonding"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1548
+# 355923780aac48ae87b6a24963efcbab
+msgid "The administrator must bond the management network NICs prior to adding the host to CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1552
+# 241a3f2bb47549c1b613bc5468c732d1
+msgid "Creating a Private Bond on the First Host in the Cluster"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1554
+# b0b878648bc34dd3b949b2492db4ebe7
+msgid "Use the following steps to create a bond in XenServer. These steps should be run on only the first host in a cluster. This example creates the cloud-private network with two physical NICs (eth0 and eth1) bonded into it."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1561
+#: ../../hypervisor_installation.rst:1607
+# c818433917984f208742d7624945c715
+# c273eb3061e74432b57d9077c627c6ea
+msgid "Find the physical NICs that you want to bond together."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1568
+# 913da62e00594d7d9256568a0966482a
+msgid "These command shows the eth0 and eth1 NICs and their UUIDs. Substitute the ethX devices of your choice. Call the UUID's returned by the above command slave1-UUID and slave2-UUID."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1574
+# 5f7804ba516044498b79880642b90e2c
+msgid "Create a new network for the bond. For example, a new network with name \"cloud-private\"."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1577
+# d2ccc4ae2a144c8b9d8337cc227fb222
+msgid "**This label is important. CloudStack looks for a network by a name you configure. You must use the same name-label for all hosts in the cloud for the management network.**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1587
+# f3b50a468a3e4e83813f2acba6062bd8
+msgid "Now you have a bonded pair that can be recognized by CloudStack as the management network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1591
+# cf64cccd2bb745bcaaddd7b531fbc539
+msgid "Public Network Bonding"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1593
+# f999c0e7062f47cf9e78cd29a0554039
+msgid "Bonding can be implemented on a separate, public network. The administrator is responsible for creating a bond for the public network if that network will be bonded and will be separate from the management network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1599
+# 0242521ca5b94ecfa005cd45513c5d1f
+msgid "Creating a Public Bond on the First Host in the Cluster"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1601
+# 3582283d68284b5fb85af54cb569eaca
+msgid "These steps should be run on only the first host in a cluster. This example creates the cloud-public network with two physical NICs (eth2 and eth3) bonded into it."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1614
+# 525068448771408183ac84f1a5d006be
+msgid "These command shows the eth2 and eth3 NICs and their UUIDs. Substitute the ethX devices of your choice. Call the UUID's returned by the above command slave1-UUID and slave2-UUID."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1620
+# b9e69c9100564b88b43f6779621e12c4
+msgid "Create a new network for the bond. For example, a new network with name \"cloud-public\"."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1623
+# d4f75d2fc44545eaa191a59720d7ac1c
+msgid "**This label is important. CloudStack looks for a network by a name you configure. You must use the same name-label for all hosts in the cloud for the public network.**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1633
+# f11b8de48bbf4fc6895b7bb33f52a308
+msgid "Now you have a bonded pair that can be recognized by CloudStack as the public network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1637
+# 08c0b83d57f64624a7fa7bb0b057d887
+msgid "Adding More Hosts to the Cluster"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1639
+# 7b998653c91d417d9920cdf8a2b62752
+msgid "With the bonds (if any) established on the master, you should add additional, slave hosts. Run the following command for all additional hosts to be added to the cluster. This will cause the host to join the master in a single XenServer pool."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1650
+# 46fa7303d5604b5aa8d3a61679d51e47
+msgid "Complete the Bonding Setup Across the Cluster"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1652
+# 53dea66729854ace9b2af4bdfc78c1ca
+msgid "With all hosts added to the pool, run the cloud-setup-bond script. This script will complete the configuration and set up of the bonds across all hosts in the cluster."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1658
+# cd69e7cc948c43ffa11698a2390cf986
+msgid "Copy the script from the Management Server in /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh to the master host and ensure it is executable."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1664
+# 3b7ac5520f0e464aa6c2c0dcb9f61233
+msgid "Run the script:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1670
+# 878fb7127a004f419b95241af6bee8ae
+msgid "Now the bonds are set up and configured properly across the cluster."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1675
+# 6b4c5561ec7e4237b7dc17126c581b6a
+msgid "Upgrading XenServer Versions"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1677
+# cfc09c589fb540b0b0a1bec122afd5ff
+msgid "This section tells how to upgrade XenServer software on CloudStack hosts. The actual upgrade is described in XenServer documentation, but there are some additional steps you must perform before and after the upgrade."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1682
+# 2376fd5b927644c8b4b846ad245f3688
+msgid "Be sure the hardware is certified compatible with the new version of XenServer."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1684
+# 942358ec8cfb439aa09b3a2faf54e73c
+msgid "To upgrade XenServer:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1688
+# e1b8b830b03645a7ab9cc4e5d534e1d1
+msgid "Upgrade the database. On the Management Server node:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1692
+# 8b47371c505b4b43a8e836e8d1747528
+msgid "Back up the database:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1701
+# 99f965b30fe24ab8bfff83358a44964e
+msgid "You might need to change the OS type settings for VMs running on the upgraded hosts."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1706
+# ffcbd17272014822acea38cfefd3e547
+msgid "If you upgraded from XenServer 5.6 GA to XenServer 5.6 SP2, change any VMs that have the OS type CentOS 5.5 (32-bit), Oracle Enterprise Linux 5.5 (32-bit), or Red Hat Enterprise Linux 5.5 (32-bit) to Other Linux (32-bit). Change any VMs that have the 64-bit versions of these same OS types to Other Linux (64-bit)."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1715
+# 733596d54def49918fe6659885ae3c7b
+msgid "If you upgraded from XenServer 5.6 SP2 to XenServer 6.0.2, change any VMs that have the OS type CentOS 5.6 (32-bit), CentOS 5.7 (32-bit), Oracle Enterprise Linux 5.6 (32-bit), Oracle Enterprise Linux 5.7 (32-bit), Red Hat Enterprise Linux 5.6 (32-bit) , or Red Hat Enterprise Linux 5.7 (32-bit) to Other Linux (32-bit). Change any VMs that have the 64-bit versions of these same OS types to Other Linux (64-bit)."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1725
+# 14f2e711450e4ff58dd3149c1fdab21d
+msgid "If you upgraded from XenServer 5.6 to XenServer 6.0.2, do all of the above."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1730
+# f2619c1d24c74437a167e2d44d5253c7
+msgid "Restart the Management Server and Usage Server. You only need to do this once for all clusters."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1740
+# fc348fb3fda64c95883a94a886676f1d
+msgid "Disconnect the XenServer cluster from CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1744
+#: ../../hypervisor_installation.rst:1874
+#: ../../hypervisor_installation.rst:3252
+#: ../../hypervisor_installation.rst:3301
+# 7f794481fc044e789630a36cdbfdf41f
+# f65c913be82f4fe09eb132c2c6dc033a
+# ca114347489c453a8cbd54f9520a6500
+# 21a397aa7b7d4f23ad83b33343dc8cd7
+msgid "Log in to the CloudStack UI as root."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1748
+# 7153d29a4b934e7bb7b4150b35a8b3e5
+msgid "Navigate to the XenServer cluster, and click Actions – Unmanage."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1752
+#: ../../hypervisor_installation.rst:3263
+# b860ab2de3c14f0da775023c03a393ed
+# 08c7c9f1bbca4dac9ca9abb2d901954f
+msgid "Watch the cluster status until it shows Unmanaged."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1756
+# f527402053e54831b67ae8daef6083c5
+msgid "Log in to one of the hosts in the cluster, and run this command to clean up the VLAN:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1765
+# b42f28a2c2fb4455a41e6372a470f6a9
+msgid "Still logged in to the host, run the upgrade preparation script:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1771
+# f6179b84964541bb846a719b3663189e
+msgid "Troubleshooting: If you see the error \"can't eject CD,\" log in to the VM and umount the CD, then run the script again."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1776
+# d7a81f24da0d4fd0b589ebfcfcd71784
+msgid "Upgrade the XenServer software on all hosts in the cluster. Upgrade the master first."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1781
+# 11d3dd98878f4fe08f96c16e5df8c6ac
+msgid "Live migrate all VMs on this host to other hosts. See the instructions for live migration in the Administrator's Guide."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1784
+# 1bdb8f184a494eb4969abf3ba696ed19
+msgid "Troubleshooting: You might see the following error when you migrate a VM:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1793
+# 6ad7bdb81aca465a9b5938d726550c76
+msgid "To solve this issue, run the following:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1801
+# 9676fe491f5740eaba74cd4060ed35f4
+msgid "Reboot the host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1805
+# 383661aa66db407a8dd6f313e2acc4f4
+msgid "Upgrade to the newer version of XenServer. Use the steps in XenServer documentation."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1810
+# ef1bce7a4ef44573a6106976c04c4c45
+msgid "After the upgrade is complete, copy the following files from the management server to this host, in the directory locations shown below:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1815
+# 64ccf69ad9eb4dfeb17c080ada99de6f
+msgid "Copy this Management Server file"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1815
+# 32e9ec87a68946b5b2705187b2201880
+msgid "To this location on the XenServer host"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1817
+# d008b2ce2b484b0aa482d6df64c2b74e
+msgid "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/xenserver60/NFSSR.py"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1817
+# e6b5a2e9d2684509ba864a23c275056f
+msgid "/opt/xensource/sm/NFSSR.py"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1818
+# d5f8132be2874a02b0853331d25286ed
+msgid "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/setupxenserver.sh"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1818
+# 2393c9fde5964bcdb21f54931c5cd007
+msgid "/opt/xensource/bin/setupxenserver.sh"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1819
+# 7a478317154146aa933ae7193c133e0a
+msgid "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/make\\_migratable.sh"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1819
+# 36d9f18cee164a5c9551ab66b058f0e5
+msgid "/opt/xensource/bin/make\\_migratable.sh"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1820
+# 5e031eb5f37f4b42a7a0357a9e963dde
+msgid "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-clean-vlan.sh"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1820
+# 12cd3626b3954c23be38e95e7059b7dc
+msgid "/opt/xensource/bin/cloud-clean-vlan.sh"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1831
+# 0b7bb106fe444196ae32f10b125d51bb
+msgid "Troubleshooting: If you see the following error message, you can safely ignore it."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1840
+# 84fc84c6930a40b88488984ff6c9112c
+msgid "Plug in the storage repositories (physical block devices) to the XenServer host:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1847
+# d796a15c920847c7a8251c995526c02d
+msgid "If you add a host to this XenServer pool, you need to migrate all VMs on this host to other hosts, and eject this host from XenServer pool."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1851
+# f9bd9295e2b84bf2879c1ecbc602c44a
+msgid "Repeat these steps to upgrade every host in the cluster to the same version of XenServer."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1856
+# 8e37aa52a47547be82d24895b65f09f4
+msgid "Run the following command on one host in the XenServer cluster to clean up the host tags:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1864
+# 8cf9d53037984028bce163054acb29f2
+msgid "When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1870
+# 3e06a5a1b257415a9ede2507a47d0877
+msgid "Reconnect the XenServer cluster to CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1878
+# 950820df270d40ebb2b49296c30a9a53
+msgid "Navigate to the XenServer cluster, and click Actions – Manage."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1882
+# 662b5d4d23744762922ae112f5e61b84
+msgid "Watch the status to see that all the hosts come up."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1886
+# 1b7befb539434c7db47239456ba7213e
+msgid "After all hosts are up, run the following on one host in the cluster:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1893
+# d3a523f2e69a478bb90498d681b0178b
+msgid "Installing Hyper-V for CloudStack"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1895
+# b93fc39d5763433cb59938b5f75dd607
+msgid "If you want to use Hyper-V hypervisor to run guest virtual machines, install Hyper-V on the hosts in your cloud. The instructions in this section doesn't duplicate Hyper-V Installation documentation. It provides the CloudStack-specific steps that are needed to prepare a Hyper-V host to work with CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1902
+# 2038da390b6848a0b3cc3fedef1a9d2c
+msgid "System Requirements for Hyper-V Hypervisor Hosts"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1905
+# fc724f9178b64868879b74a411d95ef5
+msgid "Supported Operating Systems for Hyper-V Hosts"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1909
+# 1a5519a64e134b1a91a658145276f6ed
+msgid "Windows Server 2012 R2 Standard"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1913
+# ee081eb7e4004f578c7da357ca3b65e2
+msgid "Windows Server 2012 R2 Datacenter"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1917
+# cd21b1eeb72340979622e7783f646d92
+msgid "Hyper-V 2012 R2"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1920
+# 0d65d540ddce44ad8a88d9484e834d25
+msgid "Minimum System Requirements for Hyper-V Hosts"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1924
+# ff261434dbf442899d95fec9961fdf73
+msgid "1.4 GHz 64-bit processor with hardware-assisted virtualization."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1928
+# 8213417edf9244ab8b88ea0831f4c865
+msgid "800 MB of RAM"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1932
+# bf16d06d9e7244b6bbb96e7b56e71357
+msgid "32 GB of disk space"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1936
+# 82c14f0ba5cc44b689942c4b99564fff
+msgid "Gigabit (10/100/1000baseT) Ethernet adapter"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1939
+# 51556185e39644d8a4bf6f8f7afa2861
+msgid "Supported Storage"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1943
+# 5beb17ae25a34423bc3a3e369212ec3f
+msgid "Primary Storage: Server Message Block (SMB) Version 3, Local"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1947
+# 55d3704fad27499b92347d61e7deb72a
+msgid "Secondary Storage: SMB"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1950
+# 703eb2b0e6fc40bcbda49bace0d0fb75
+msgid "Preparation Checklist for Hyper-V"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1952
+#: ../../hypervisor_installation.rst:2388
+# 419613931af84db383a87503c76f013c
+# 487f37bf5b724be48da1842d6f4f189e
+msgid "For a smoother installation, gather the following information before you start:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1955
+# 2c101932aa3e4ca28fdcb6f78b2628f0
+msgid "Hyper-V Requirements"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1957
+#: ../../hypervisor_installation.rst:2715
+# a2108b6906c5463a9d62d10304f6f7c0
+# 7df31f594d084182a124fa1a5963c2e2
+msgid "Value"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1959
+#: ../../hypervisor_installation.rst:2900
+# 8c30f2b9669c4b839800c9fde5954476
+# e536631fc460428f82d0797650809db6
+msgid "Description"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1961
+# 9e31d44efe0d40bc8987a7f1b9a7560a
+msgid "Server Roles"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1965
+# 4de7af81dfc04ce89ecb35699251c666
+msgid "After the Windows Server 2012 R2 installation, ensure that Hyper-V is selected from Server Roles. For more information, see `Installing Hyper-V <http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step2>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1968
+# 644571f95331448f97fe445ae9ee8de9
+msgid "Share Location"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1970
+# 636f796bb2ad45c5a5de2c9166505359
+msgid "New folders in the /Share directory"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1972
+# 2b338e212cc74f149db217553b6b692f
+msgid "Ensure that folders are created for Primary and Secondary storage. The SMB share and the hosts should be part of the same domain."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1975
+# 7a6f754da1ec458ca9eae5c017e0ab52
+msgid "If you are using Windows SMB share, the location of the file share for the Hyper-V deployment will be the new folder created in the \\\\Shares on the selected volume. You can create sub-folders for both CloudStack Primary and Secondary storage within the share location. When you select the profile for the file shares, ensure that you select SMB Share -Applications. This creates the file shares with settings appropriate for Hyper-V."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1983
+# cfec42b2cfec42d7b8ffbd8e69cb8561
+msgid "Domain and Hosts"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1985
+# 40eb688b68184a569a98d100afc12873
+msgid "Hosts should be part of the same Active Directory domain."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1987
+# 6f43f5b3150444fd8d107a12fcebadb0
+msgid "Hyper-V Users"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1989
+# 571279354d664c0c9db4d00e780060ab
+msgid "Full control"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1991
+# d4526dd1a8b24a46b8a12c3188d43a1a
+msgid "Full control on the SMB file share."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1993
+# 3619e03fbf014ba3a55f9a8cbbeeb5b0
+msgid "Virtual Switch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:1995
+#: ../../hypervisor_installation.rst:2166
+# f63f68f216ba4cabb3a183f2539b2134
+# b7c90a0b793c4c48847a27c21d2b64ac
+msgid "If you are using Hyper-V 2012 R2, manually create an external virtual switch before adding the host to CloudStack. If the Hyper-V host is added to the Hyper-V manager, select the host, then click Virtual Switch Manager, then New Virtual Switch. In the External Network, select the desired NIC adapter and click Apply."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2001
+#: ../../hypervisor_installation.rst:2172
+# 6d95d36bac3c4cc899af98614236b0d5
+# 4a0f7c13f957472b93f453ba6e2c6f23
+msgid "If you are using Windows 2012 R2, virtual switch is created automatically."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2004
+# eedd8450f79a4f919ecbd025523beb7a
+msgid "Virtual Switch Name"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2006
+# 705abed5f4e34a2abcdd893c5a585841
+msgid "Take a note of the name of the virtual switch. You need to specify that when configuring CloudStack physical network labels."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2009
+# 96e118a8d6fb4e349ebee12448d428ae
+msgid "Hyper-V Domain Users"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2013
+# 2183c3c5058d46e781cfa2009b5b8cce
+msgid "Add the Hyper-V domain users to the Hyper-V Administrators group."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2017
+# 9f4d174e848040d582531a73056893bd
+msgid "A domain user should have full control on the SMB share that is exported for primary and secondary storage."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2022
+# 99de63ae54c54e0db4b82c316b7e78b2
+msgid "This domain user should be part of the Hyper-V Administrators and Local Administrators group on the Hyper-V hosts that are to be managed by CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2028
+# 720fe08852e24e4b9a6af71ba0163e18
+msgid "The Hyper-V Agent service runs with the credentials of this domain user account."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2033
+# 0eec174a2c2b4b95b04019df219554d5
+msgid "Specify the credential of the domain user while adding a host to CloudStack so that it can manage it."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2038
+# 6ff787bf1b1e4267996f97a752a180da
+msgid "Specify the credential of the domain user while adding a shared SMB primary or secondary storage."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2041
+#: ../../hypervisor_installation.rst:2043
+#: ../../hypervisor_installation.rst:2049
+#: ../../hypervisor_installation.rst:2057
+# 08280d229e5a44209e52e6419ea17724
+# 4af21332db304a9b999b0669c5879f16
+# 171afe1cdf5340aaa079bba3c9efaa37
+# a3ca202c8d9242048feefb736684fcbe
+msgid "Migration"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2045
+# a72a460265644d92b134252e4a8e9ebe
+msgid "Enable Migration."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2047
+# c879e91d8d184c89b88542de1d7530f5
+msgid "For more information, see `Configuring Live Migration <http://technet.microsoft.com/en-us/library/jj134199.aspx>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2051
+# ddeb2003fe114629bfe83180bfd7434b
+msgid "Delegation"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2053
+# e71e2a9eda1e4d77add23d88c3649f26
+msgid "If you want to use Live Migration, enable Delegation. Enable the following services of other hosts participating in Live Migration: CIFS and Microsoft Virtual System Migration Service."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2059
+# d71ba16c4ffa4178b6486c322b550c53
+msgid "Kerberos"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2061
+# 508a39fb29bc4d71b5102e437945f05d
+msgid "Enable Kerberos for Live Migration."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2063
+# 419a33d7988c41c5b9675ff28fbc4f83
+msgid "Network Access Permission for Dial-in"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2065
+# ac2e195eee054de98c1b29c3a4572263
+msgid "Allow access"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2067
+# ccb25d6540064b70906fd1068efdd8ab
+msgid "Allow access for Dial-in connections."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2070
+# a5c5c4383ba54e519a134d29069914d5
+msgid "Hyper-V Installation Steps"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2074
+# 99fb9754d8c345af83eb13fef2ad291d
+msgid "Download the operating system from `Windows Server 2012 R2 <http://technet.microsoft.com/en-us/windowsserver/hh534429>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2078
+# e8f16051cb8e4e6f9930fdd8e88a5125
+msgid "Install it on the host as given in `Install and Deploy Windows Server 2012 R2 <http://technet.microsoft.com/library/hh831620>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2082
+# fe9f3b143dcc4f37858c02e57756925f
+msgid "Post installation, ensure that you enable Hyper-V role in the server."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2086
+# e8768a97fb33405e9e4edadcd6473632
+msgid "If no Active Directory domain exists in your deployment, create one and add users to the domain."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2091
+# 9db1342fa13d4f0b8507c35a17a7a308
+msgid "In the Active Directory domain, ensure that all the Hyper-v hosts are added so that all the hosts are part of the domain."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2096
+# c7e961b111f74d8d9cd8bcb3c74e3ef9
+msgid "Add the domain user to the following groups on the Hyper-V host: Hyper-V Administrators and Local Administrators."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2101
+# 9df5b6c415874cb883224314c9e20535
+msgid "Installing the CloudStack Agent on a Hyper-V Host"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2103
+# 8a5b9b9c5a6749c8a37c402622c2fa74
+msgid "The Hyper-V Agent helps CloudStack perform operations on the Hyper-V hosts. This Agent communicates with the Management Server and controls all the instances on the host. Each Hyper-V host must have the Hyper-V Agent installed on it for successful interaction between the host and CloudStack. The Hyper-V Agent runs as a Windows service. Install the Agent on each host using the following steps."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2110
+# 47de8548d8d141569c4665678df1976c
+msgid "CloudStack Management Server communicates with Hyper-V Agent by using HTTPS. For secure communication between the Management Server and the host, install a self-signed certificate on port 8250."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2115
+# 16689e77021c459b9b2fb8ac046290b9
+msgid "The Agent installer automatically perform this operation. You have not selected this option during the Agent installation, it can also be done manually as given in step 1."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2119
+# 3b0ee4121a5e4bb1ac39974e02a6da46
+msgid "Create and add a self-signed SSL certificate on port 8250:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2123
+# 884ff72564e24ca5b278ddc37b37a0c5
+msgid "Create A self-signed SSL certificate:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2129
+# 4e30082071c043499c064e67980e167e
+msgid "This command creates the self-signed certificate and add that to the certificate store ``LocalMachine\\My``."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2134
+# 1b6139e4fef04fa9a4b68f34f9fb85b3
+msgid "Add the created certificate to port 8250 for https communication:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2140
+# 96581439bebc46468b7bf6846881ea0a
+msgid "Thumbprint is the thumbprint of the certificate you created."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2144
+# 47858b43d7b74ce8afa4368788b0c514
+msgid "Build the CloudStack Agent for Hyper-V as given in `Building CloudStack Hyper-V Agent <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Creating+Hyperv+Agent+Installer>`__."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2150
+# 0aa2346be94a42638e7fc6ea9cdbeb91
+msgid "As an administrator, run the installer."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2154
+# 0d17e4d0f5284921b771f773cb0356fe
+msgid "Provide the Hyper-V admin credentials when prompted."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2156
+# 5d834f623db14558b8eeda52cfe973a4
+msgid "When the agent installation is finished, the agent runs as a service on the host machine."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2160
+# 31461c4200094300b939e83c48affcbf
+msgid "Physical Network Configuration for Hyper-V"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2162
+# 869e4b869e4241038151ead9ffae6ab5
+msgid "You should have a plan for how the hosts will be cabled and which physical NICs will carry what types of traffic. By default, CloudStack will use the device that is used for the default route."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2176
+# b114113246f94742ac60bd1331c5d976
+msgid "Storage Preparation for Hyper-V (Optional)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2178
+# 506240beff9d4e2d9cfa7bc22a95d5f3
+msgid "CloudStack allows administrators to set up shared Primary Storage and Secondary Storage that uses SMB."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2183
+# dd424079b5f94f9581d499ab92498b1a
+msgid "Create a SMB storage and expose it over SMB Version 3."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2185
+# 616667a633f54bcdb3ca3bc0090bf3a9
+msgid "For more information, see `Deploying Hyper-V over SMB <http://technet.microsoft.com/en-us/library/jj134187.aspx>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2187
+# d1f47f8ed99f43008e763770fe26cbfb
+msgid "You can also create and export SMB share using Windows. After the Windows Server 2012 R2 installation, select File and Storage Services from Server Roles to create an SMB file share. For more information, see `Creating an SMB File Share Using Server Manager <http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step3>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2194
+# 719f8c1fe9e0467299d8d1cfeea8f097
+msgid "Add the SMB share to the Active Directory domain."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2196
+# 16b6241ff51c43208f9ac1cdabf59ef1
+msgid "The SMB share and the hosts managed by CloudStack need to be in the same domain. However, the storage should be accessible from the Management Server with the domain user privileges."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2202
+# 079ed026cdb94e58ba4ab2ea29fae3f7
+msgid "While adding storage to CloudStack, ensure that the correct domain, and credentials are supplied. This user should be able to access the storage from the Management Server."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2207
+# 160301917c8340169daad29cbd70f33c
+msgid "VMware vSphere Installation and Configuration"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2209
+# b11df8a743bc40e0985ade1b95bb1552
+msgid "If you want to use the VMware vSphere hypervisor to run guest virtual machines, install vSphere on the host(s) in your cloud."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2213
+# 3d9610f8babc47a180e75af13f6672b9
+msgid "System Requirements for vSphere Hosts"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2216
+# 470fc59fd16240b480948999f7843a6d
+msgid "Software requirements:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2220
+# 9183ed2e4d2a458791ebbe4949777c1e
+msgid "vSphere and vCenter, both version 4.1 or 5.0."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2222
+# 766663a5920b45398c7575a5e9e38ff6
+msgid "vSphere Standard is recommended. Note however that customers need to consider the CPU constraints in place with vSphere licensing. See `http://www.vmware.com/files/pdf/vsphere\\_pricing.pdf <http://www.vmware.com/files/pdf/vsphere_pricing.pdf>`_ and discuss with your VMware sales representative."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2227
+# f1661195861840288269ea1202e9b89e
+msgid "vCenter Server Standard is recommended."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2231
+# 285b4b4fca1a4889a32a95763f40cbe3
+msgid "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."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2240
+# fea907bc006c4462af1e5c66fff27418
+msgid "Apply All Necessary Hotfixes. The lack of up-do-date hotfixes can lead to data corruption and lost VMs."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2243
+# 0e3d7163cdaa45efb1a1de9c1d840c70
+msgid "Hardware requirements:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2247
+# c2829bd33bf44fcb92b5e6aeca93fe3d
+msgid "The host must be certified as compatible with vSphere. See the VMware Hardware Compatibility Guide at `http://www.vmware.com/resources/compatibility/search.php <http://www.vmware.com/resources/compatibility/search.php>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2253
+# 90885bc4493d423b802629ca42671470
+msgid "All hosts must be 64-bit and must support HVM (Intel-VT or AMD-V enabled)."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2258
+# 444698b909b14c1bafa79d28ca6d0e0c
+msgid "All hosts within a cluster must be homogenous. That means the CPUs must be of the same type, count, and feature flags."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2286
+# 026389f5c21248f094a1988283f9ceaa
+msgid "vCenter Server requirements:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2290
+# 898e1faee1144e9b8fb1ae76627f710a
+msgid "Processor - 2 CPUs 2.0GHz or higher Intel or AMD x86 processors. Processor requirements may be higher if the database runs on the same machine."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2296
+# b912675600f2430a96805b275c1f1569
+msgid "Memory - 3GB RAM. RAM requirements may be higher if your database runs on the same machine."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2301
+# ff655342fa17404384b080f9a3991839
+msgid "Disk storage - 2GB. Disk requirements may be higher if your database runs on the same machine."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2306
+# 34c75fcd20d44f5ab2bfaa95be9c7646
+msgid "Microsoft SQL Server 2005 Express disk requirements. The bundled database requires up to 2GB free disk space to decompress the installation archive."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2312
+# 0699f7fd865549849d921d930b9fa7ea
+msgid "Networking - 1Gbit or 10Gbit."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2314
+# cef076dcedee4a24b9b3ec51ef9ee68f
+msgid "For more information, see `\"vCenter Server and the vSphere Client Hardware Requirements\" <http://pubs.vmware.com/vsp40/wwhelp/wwhimpl/js/html/wwhelp.htm#href=install/c_vc_hw.html>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2317
+# 66ca94319c714dc4a9216ea740c56b40
+msgid "Other requirements:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2321
+# c76079dbdb8c48af90c236f2d0baa787
+msgid "VMware vCenter Standard Edition 4.1 or 5.0 must be installed and available to manage the vSphere hosts."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2326
+# 07375471238a4fa0a0f29e14060188ab
+msgid "vCenter must be configured to use the standard port 443 so that it can communicate with the CloudStack Management Server."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2331
+# fa50c73129ea428e839debdffdc10099
+msgid "You must re-install VMware ESXi if you are going to re-use a host from a previous install."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2336
+# 5d54cd6b7cda47869cebff7b876565d1
+msgid "CloudStack requires VMware vSphere 4.1 or 5.0. VMware vSphere 4.0 is not supported."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2341
+# 15bdac339f71483d96232a6684a05f38
+msgid "All hosts must be 64-bit and must support HVM (Intel-VT or AMD-V enabled). All hosts within a cluster must be homogeneous. That means the CPUs must be of the same type, count, and feature flags."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2347
+# 3320ef7bcf874235ad145cfe38f4f21d
+msgid "The CloudStack management network must not be configured as a separate virtual network. The CloudStack management network is the same as the vCenter management network, and will inherit its configuration. See :ref:`configure-vcenter-management-network`."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2354
+# b7b26fdba3ba429a9b554e95c7aea05a
+msgid "CloudStack requires ESXi. ESX is not supported."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2358
+# 807a6a01a8cb40bb9ddafcf3d4f6e055
+msgid "All resources used for CloudStack must be used for CloudStack only. CloudStack cannot share instance of ESXi or storage with other management consoles. Do not share the same storage volumes that will be used by CloudStack with a different set of ESXi servers that are not managed by CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2366
+# 76ba09bd8f5d4ab69dfa682a87e2f2e7
+msgid "Put all target ESXi hypervisors in a cluster in a separate Datacenter in vCenter."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2371
+# 57a49ec20ce243989933f66ba4d87eed
+msgid "The cluster that will be managed by CloudStack should not contain any VMs. Do not run the management server, vCenter or any other VMs on the cluster that is designated for CloudStack use. Create a separate cluster for use of CloudStack and make sure that they are no VMs in this cluster."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2379
+# 6fd4edef52d2463fa27009ad3626e5fa
+msgid "All the required VLANS must be trunked into all network switches that are connected to the ESXi hypervisor hosts. These would include the VLANS for Management, Storage, vMotion, and guest VLANs. The guest VLAN (used in Advanced Networking; see Network Setup) is a contiguous range of VLANs that will be managed by CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2386
+# 5b9b5d9bb49f48c790d3d7975da36b97
+msgid "Preparation Checklist for VMware"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2393
+# 874ada2598f94f90bbb7ea1051a0fc8e
+msgid "Information listed in :ref:`vcenter-checklist`"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2397
+# c8657d9c46a84e94b59a49ebfeceb4cd
+msgid "Information listed in :ref:`networking-checklist-for-vmware`"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2402
+# d25566ef8de84fd9ba474e9c493effb9
+msgid "vCenter Checklist"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2404
+# d47240a593424a1cb059bcc359843fb6
+msgid "You will need the following information about vCenter."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2407
+# ad424c3b64d84058957622e7ccb34e2f
+msgid "vCenter Requirement"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2407
+#: ../../hypervisor_installation.rst:2423
+#: ../../hypervisor_installation.rst:2715
+# aa42ada253634235831462bb3b3a5a5a
+# 6971b4e11acf438191565fdff1f8ce8d
+# bc087c8de60d40f191079b58516386bc
+msgid "Notes"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2409
+# 3615f6d25ad94970828a9bf159bc7a33
+msgid "vCenter User"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2409
+# 9c1c7400557045389a7acb14690f4c62
+msgid "This user must have admin privileges."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2410
+# 7bf8f233cd574453b441875c1fbc344e
+msgid "vCenter User Password"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2410
+# 936bd3768ff3435cb10fa077957eb873
+msgid "Password for the above user."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2411
+# 6fe51d4e1ca14592b03fcae9bf28db36
+msgid "vCenter Datacenter Name"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2411
+# e32c306acc384d02b3d67c109698f082
+msgid "Name of the datacenter."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2412
+# 50068ce776c541ca8a56a9a1475d34ec
+msgid "vCenter Cluster Name"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2412
+# a6bf766a42e04a9185b699474ee058d3
+msgid "Name of the cluster."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2418
+# 8956e9c5f49e48da99562ae0cf8b5697
+msgid "Networking Checklist for VMware"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2420
+# 56e3476f8f4e40fa97acfa540fa0a79a
+msgid "You will need the following information about VLAN."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2423
+# 9cc0357ae70f44829be639ba80443de3
+msgid "VLAN Information"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2425
+# f08b03cbe30347b4bc3ea89dfa2faca6
+msgid "ESXi VLAN"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2425
+# 18957fe16bfc40a18dfba9f47792be6b
+msgid "VLAN on which all your ESXi hypervisors reside."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2426
+# a5c6d87944d44ba8abb37262b7ac9ae1
+msgid "ESXI VLAN IP Address"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2426
+# 3c0852bce08f43928a28be17866c883b
+msgid "IP Address Range in the ESXi VLAN. One address per Virtual Router is used from this range."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2427
+# 788afe1854b74f6480fb9dcb08317b37
+msgid "ESXi VLAN IP Gateway"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2428
+# bacedb178b3f4b95a2644000683e5540
+msgid "ESXi VLAN Netmask"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2429
+# 4d4785e85cef4d06b971d1c0d7e275ad
+msgid "Management Server VLAN"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2429
+# 01e4e85ca9534e50803fe477a0556770
+msgid "VLAN on which the CloudStack Management server is installed."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2430
+# a6572d2d1cc14b38a161ef09f9ba2e72
+msgid "Public VLAN"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2430
+# 0c60da1f668640db9432f89beeebcfdc
+msgid "VLAN for the Public Network."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2431
+# 4525e1b8f6f141ae8d9225392c099184
+msgid "Public VLAN Gateway"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2432
+# 32104578607045e38f78075c77df1e63
+msgid "Public VLAN Netmask"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2433
+# 57123c0a394241c6a639de412ffb9b8f
+msgid "Public VLAN IP Address Range"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2433
+# 932e6245886a44928cf95b929f3e6735
+msgid "Range of Public IP Addresses available for CloudStack use. These addresses will be used for virtual router on CloudStack to route private traffic to external networks."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2436
+# 0200790a79464d739ec724252e076ed3
+msgid "VLAN Range for Customer use"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2436
+# 15e968a010ac44c5ae838310d7b27d7e
+msgid "A contiguous range of non-routable VLANs. One VLAN will be assigned for each customer."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2442
+# bce73cc0c26e46fdb3ad7c900ead3c2e
+msgid "vSphere Installation Steps"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2446
+# 08bd5d58d94f4362976973d3b3c71f1a
+msgid "If you haven't already, you'll need to download and purchase vSphere from the VMware Website (`https://www.vmware.com/tryvmware/index.php?p=vmware-vsphere&lp=1 <https://www.vmware.com/tryvmware/index.php?p=vmware-vsphere&lp=1>`_) and install it by following the VMware vSphere Installation Guide."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2453
+# 2ef333c7f2f54869bbd02d3235194cec
+msgid "Following installation, perform the following configuration, which are described in the next few sections:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2457
+# d396f645a258483aa100dd126802bed6
+msgid "Required"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2457
+# 3a47305e100d4c5ab944fb0fb97c58d3
+msgid "Optional"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2459
+# 99ddd825c54741ec930bc538c64459f0
+msgid "ESXi host setup"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2459
+# 32420a57854f4107b19dc23c22c16b51
+msgid "NIC bonding"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2460
+# 88aad3fa642f4dc29607367b57b8c766
+msgid "Configure host physical networking,virtual switch, vCenter Management Network, and extended port range"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2460
+# 5406679428f94ce0b5ef1336e5ce693a
+msgid "Multipath storage"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2461
+# 7a4bde3b86a141e5bcd9b6627e56b47a
+msgid "Prepare storage for iSCSI"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2462
+# a4f0a1b396ad4b818fcb8fae9d2a3845
+msgid "Configure clusters in vCenter and add hosts to them, or add hosts without clusters to vCenter"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2466
+# 66a1da1529c64722bbe6a32e6a09b81e
+msgid "ESXi Host setup"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2468
+# d2206ae8b8b0405a82421a944b690f6f
+msgid "All ESXi hosts should enable CPU hardware virtualization support in BIOS. Please note hardware virtualization support is not enabled by default on most servers."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2473
+# 823edf72601b46f9b41f1f0331025b0e
+msgid "Physical Host Networking"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2475
+# 65fdae591c2a496aaf6f4432c910b4e6
+msgid "You should have a plan for cabling the vSphere hosts. Proper network configuration is required before adding a vSphere host to CloudStack. To configure an ESXi host, you can use vClient to add it as standalone host to vCenter first. Once you see the host appearing in the vCenter inventory tree, click the host node in the inventory tree, and navigate to the Configuration tab."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2482
+# 08dd99eb935744d5a55a302fd892936d
+msgid "|vspherephysicalnetwork.png: vSphere client|"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2484
+# e80e2656108441bcbec60c3069da6b89
+msgid "In the host configuration tab, click the \"Hardware/Networking\" link to bring up the networking configuration page as above."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2488
+# 3b5704fb76c04adf9b622f63103e009a
+msgid "Configure Virtual Switch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2490
+# d08703f6feb244bd95ae9b14321f374a
+msgid "A default virtual switch vSwitch0 is created. CloudStack requires all ESXi hosts in the cloud to use the same set of virtual switch names. If you change the default virtual switch name, you will need to configure one or more CloudStack configuration variables as well."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2496
+# 2a8a290d8bc24c6e9efe5ebf03605fe1
+msgid "Separating Traffic"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2498
+# 81f6d7108ad046f58db096bb486a7c45
+msgid "CloudStack allows you to use vCenter to configure three separate networks per ESXi host. These networks are identified by the name of the vSwitch they are connected to. The allowed networks for configuration are public (for traffic to/from the public internet), guest (for guest-guest traffic), and private (for management and usually storage traffic). You can use the default virtual switch for all three, or create one or two other vSwitches for those traffic types."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2506
+# e01fb6b864ae4591a6040e3227eb3981
+msgid "If you want to separate traffic in this way you should first create and configure vSwitches in vCenter according to the vCenter instructions. Take note of the vSwitch names you have used for each traffic type. You will configure CloudStack to use these vSwitches."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2512
+# c101a9ffcc8a41ed9d941197df3790d6
+msgid "Increasing Ports"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2514
+# 67408afd6515434a8dc9b58d7b1096c2
+msgid "By default a virtual switch on ESXi hosts is created with 56 ports. We recommend setting it to 4088, the maximum number of ports allowed. To do that, click the \"Properties...\" link for virtual switch (note this is not the Properties link for Networking)."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2519
+# 91a0ee49c11047d69398dc65246ee508
+msgid "|vsphereincreaseports.png: vSphere client|"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2521
+# 1b199b2c7fb64a27867df7bf2aa8ae31
+msgid "In vSwitch properties dialog, select the vSwitch and click Edit. You should see the following dialog:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2524
+# 1553cfe713e84e788e2d8d9138ddc93c
+msgid "|vspherevswitchproperties.png: vSphere client|"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2526
+# 30c0ae1e71ec432faf1aa6694a4de217
+msgid "In this dialog, you can change the number of switch ports. After you've done that, ESXi hosts are required to reboot in order for the setting to take effect."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2533
+# 0ea01f09979f42be9b806229aa47d2c4
+msgid "Configure vCenter Management Network"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2535
+# 116d1ea7700444689448850f261cfded
+msgid "In the vSwitch properties dialog box, you may see a vCenter management network. This same network will also be used as the CloudStack management network. CloudStack requires the vCenter management network to be configured properly. Select the management network item in the dialog, then click Edit."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2541
+# 7ff1766a196f4699991eda06e976010c
+msgid "|vspheremgtnetwork.png: vSphere client|"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2543
+# bac7d94e1edb4ea5806db13d09308ac2
+msgid "Make sure the following values are set:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2547
+# af96ead47c0044bab364251d55a3b39e
+msgid "VLAN ID set to the desired ID"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2551
+# 1d8c4f1ed0514af0a756aec83a565956
+msgid "vMotion enabled."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2555
+# 4d00a385859641e4917ec59ea57048fd
+msgid "Management traffic enabled."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2557
+# 66d1840538c14c96b4d59ff3e61e856a
+msgid "If the ESXi hosts have multiple VMKernel ports, and ESXi is not using the default value \"Management Network\" as the management network name, you must follow these guidelines to configure the management network port group so that CloudStack can find it:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2564
+# fc2b617df8894bd39a8f053b76a2c07c
+msgid "Use one label for the management network port across all ESXi hosts."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2568
+# fd1df578b83c4074ac776d883517aacb
+msgid "In the CloudStack UI, go to Configuration - Global Settings and set vmware.management.portgroup to the management network label from the ESXi hosts."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2573
+# 81513937dabd42b49f17e4ed85786228
+msgid "Extend Port Range for CloudStack Console Proxy"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2575
+# 1a1fc60e2c5144a7ba1e80d0b9efb926
+msgid "(Applies only to VMware vSphere version 4.x)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2577
+# 53fef3ce43cd4997b29df5bdb6832385
+msgid "You need to extend the range of firewall ports that the console proxy works with on the hosts. This is to enable the console proxy to work with VMware-based VMs. The default additional port range is 59000-60000. To extend the port range, log in to the VMware ESX service console on each host and run the following commands:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2589
+# afe1b7c25f5f4cc3946340f3837f839d
+msgid "Configure NIC Bonding for vSphere"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2591
+# 5c37fa38c442475bace70197c0dd9b82
+msgid "NIC bonding on vSphere hosts may be done according to the vSphere installation guide."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2595
+# 5d2db778b8a94adab782e09977ec5ecd
+msgid "Configuring a vSphere Cluster with Nexus 1000v Virtual Switch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2597
+# f36bc73d81314d9f8325fc0986b97ed1
+msgid "CloudStack supports Cisco Nexus 1000v dvSwitch (Distributed Virtual Switch) for virtual network configuration in a VMware vSphere environment. This section helps you configure a vSphere cluster with Nexus 1000v virtual switch in a VMware vCenter environment. For information on creating a vSphere cluster, see `\"VMware vSphere Installation and Configuration\" <#vmware-vsphere-installation-and-configuration>`_"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2605
+# 8cd1db7c783547a2a369cc85671b0ba0
+msgid "About Cisco Nexus 1000v Distributed Virtual Switch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2607
+# 947f78705b1647ff8b04e6efaafcc588
+msgid "The Cisco Nexus 1000V virtual switch is a software-based virtual machine access switch for VMware vSphere environments. It can span multiple hosts running VMware ESXi 4.0 and later. A Nexus virtual switch consists of two components: the Virtual Supervisor Module (VSM) and the Virtual Ethernet Module (VEM). The VSM is a virtual appliance that acts as the switch's supervisor. It controls multiple VEMs as a single network device. The VSM is installed independent of the VEM and is deployed in redundancy mode as pairs or as a standalone appliance. The VEM is installed on each VMware ESXi server to provide packet-forwarding capability. It provides each virtual machine with dedicated switch ports. This VSM-VEM architecture is analogous to a physical Cisco switch's supervisor (standalone or configured in high-availability mode) and multiple linecards architecture."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2621
+# 16d69055a2814aa2b3f82537e3376cbf
+msgid "Nexus 1000v switch uses vEthernet port profiles to simplify network provisioning for virtual machines. There are two types of port profiles: Ethernet port profile and vEthernet port profile. The Ethernet port profile is applied to the physical uplink ports-the NIC ports of the physical NIC adapter on an ESXi server. The vEthernet port profile is associated with the virtual NIC (vNIC) that is plumbed on a guest VM on the ESXi server. The port profiles help the network administrators define network policies which can be reused for new virtual machines. The Ethernet port profiles are created on the VSM and are represented as port groups on the vCenter server."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2633
+#: ../../hypervisor_installation.rst:2973
+# 009d2fffa5a74d6e8aae5724bc65a70b
+# 91b00accca5d4628b0755e4faa99f297
+msgid "Prerequisites and Guidelines"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2635
+# ce47ce0ab3f14e90b733df2c0ccf976c
+msgid "This section discusses prerequisites and guidelines for using Nexus virtual switch in CloudStack. Before configuring Nexus virtual switch, ensure that your system meets the following requirements:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2641
+# 388fab6909d346c29c55cf3802467fdd
+msgid "A cluster of servers (ESXi 4.1 or later) is configured in the vCenter."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2646
+# bb51ba76272e459b82769c8b10669f33
+msgid "Each cluster managed by CloudStack is the only cluster in its vCenter datacenter."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2651
+# ceb54b37abe64691b732b2f56ab9ab63
+msgid "A Cisco Nexus 1000v virtual switch is installed to serve the datacenter that contains the vCenter cluster. This ensures that CloudStack doesn't have to deal with dynamic migration of virtual adapters or networks across other existing virtual switches. See `Cisco Nexus 1000V Installation and Upgrade Guide <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_5_1/install_upgrade/vsm_vem/guide/n1000v_installupgrade.html>`_ for guidelines on how to install the Nexus 1000v VSM and VEM modules."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2661
+# c4b648c345f24f0d93caa617a1e02bf2
+msgid "The Nexus 1000v VSM is not deployed on a vSphere host that is managed by CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2666
+# 9af74a7957b14acf9dea9343a65d4943
+msgid "When the maximum number of VEM modules per VSM instance is reached, an additional VSM instance is created before introducing any more ESXi hosts. The limit is 64 VEM modules for each VSM instance."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2672
+# 39bd095c73454da08cce69cebec4758c
+msgid "CloudStack expects that the Management Network of the ESXi host is configured on the standard vSwitch and searches for it in the standard vSwitch. Therefore, ensure that you do not migrate the management network to Nexus 1000v virtual switch during configuration."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2680
+# caeae4aefa224fe2946967d990a1f653
+msgid "All information given in :ref:`nexus-vswift-preconf`"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2685
+# 079c03e1a1c44b2585e0589bc13ec419
+msgid "Nexus 1000v Virtual Switch Preconfiguration"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2688
+#: ../../hypervisor_installation.rst:3004
+# 441a8321399140988319b96b0ed4a8d3
+# e1e5b967f4b4437dbb584f3d5bb2d0d2
+msgid "Preparation Checklist"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2690
+# a96df263b385459a91eba41537978fec
+msgid "For a smoother configuration of Nexus 1000v switch, gather the following information before you start:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2695
+# 031db7ac24b54428a167d5b7a115d517
+msgid "vCenter credentials"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2699
+# fe90f49382904b8aa51038d5a04a39b7
+msgid "Nexus 1000v VSM IP address"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2703
+# fe0fcf8dfab84007a11117c9ecd6935d
+msgid "Nexus 1000v VSM Credentials"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2707
+# 8cc68bc6d66a435ca7b8ad006683ddb8
+msgid "Ethernet port profile names"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2710
+# 1f929872354448a28565fcce6d00abc7
+msgid "vCenter Credentials Checklist"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2712
+# 8bb7ea505c874ab7b4c1866085d8e700
+msgid "You will need the following information about vCenter:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2715
+# f9ed8bcf6a9f4377b0199b7c80d0bcb5
+msgid "Nexus vSwitch Requirements"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2717
+# c7823fb897be48eea6800becf44337e5
+msgid "vCenter IP"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2717
+# e823090f879940bea3b4b84e7e3ee726
+msgid "The IP address of the vCenter."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2718
+# f0ef18ebb58145568d1a700d6e00b9ef
+msgid "Secure HTTP Port Number"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2718
+# c50252838678465788afb4692dec2d53
+msgid "443"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2718
+# 7a4f9f24e38c433697be3155d918783c
+msgid "Port 443 is configured by default; however, you can change the port if needed."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2719
+# f9b688a1b9244b69a767dc296906d23d
+msgid "vCenter User ID"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2719
+# 5e8d79b6521145388c4acb0517d5b88b
+msgid "The vCenter user with administrator-level privileges. The vCenter User ID is required when you configure the virtual switch in CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2721
+#: ../../hypervisor_installation.rst:2905
+#: ../../hypervisor_installation.rst:3145
+# b881179cb7264cc7abb9f35738264468
+# 6a7716e4718d42a8aa250d486b60691f
+# cbc788e4d5b24d609a80d80085a406e1
+msgid "vCenter Password"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2721
+# 77b0f1f8ba5c480688d7a4645318e29d
+msgid "The password for the vCenter user specified above. The password for this vCenter user is required when you configure the switch in CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2727
+# 8adc4bbec2994f9daf8ad28a283f8f22
+msgid "Network Configuration Checklist"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2729
+# 723fe067d062435dae8004f1fb6111f0
+msgid "The following information specified in the Nexus Configure Networking screen is displayed in the Details tab of the Nexus dvSwitch in the CloudStack UI:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2734
+# 98f99df6ba884d35a1903c0020ff3cf4
+msgid "**Control Port Group VLAN ID**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2734
+# 18759fe2370349c88c9b9eca286d6597
+msgid "The VLAN ID of the Control Port Group. The control VLAN is used for communication between the VSM and the VEMs."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2737
+# c573b97a9ef44290a7ed29c338f0b166
+msgid "**Management Port Group VLAN ID**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2737
+# 89706bc807174ca68e67f578f1665a75
+msgid "The VLAN ID of the Management Port Group. The management VLAN corresponds to the mgmt0 interface that is used to establish and maintain the connection between the VSM and VMware vCenter Server."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2740
+# 05d78f3b91a54226ae7d80ad9b32e5f2
+msgid "**Packet Port Group VLAN ID**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2740
+# efdbd0ef1fcc42379e1eeecc7403ee3c
+msgid "The VLAN ID of the Packet Port Group. The packet VLAN forwards relevant data packets from the VEMs to the VSM."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2742
+# 15475826735146f0abd95387015ba490
+msgid "The VLANs used for control, packet, and management port groups can be the same."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2744
+# e340a47da8624b4b883780b3d2a5a9d9
+msgid "For more information, see `Cisco Nexus 1000V Getting Started Guide <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_b/getting_started/configuration/guide/n1000v_gsg.pdf>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2747
+# da3e2e028d7c450a901bf4831cc1d365
+msgid "VSM Configuration Checklist"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2749
+# 587a4baf238946f48ee6e7bd04fd1b07
+msgid "You will need the following VSM configuration parameters:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2751
+# 5256914261474454b2f9537dd4f2be04
+msgid "**Admin Name and Password**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2752
+# 4fc4d247bb37403eb2789f39d793866b
+msgid "The admin name and password to connect to the VSM appliance. You must specify these credentials while configuring Nexus virtual switch."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2753
+# 5e96418f205547fb8d770ccb7168d497
+msgid "**Management IP Address**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2754
+# 7febd6557b3742e9a3d478672eba6cad
+msgid "This is the IP address of the VSM appliance. This is the IP address you specify in the virtual switch IP Address field while configuting Nexus virtual switch."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2758
+# 2cd219755aca4177a241670f4b4b7872
+msgid "**SSL**"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2756
+# cab1502c5d5d4221873f13e86168b3d3
+msgid "Should be set to Enable.Always enable SSL. SSH is usually enabled by default during the VSM installation. However, check whether the SSH connection to the VSM is working, without which CloudStack failes to connect to the VSM."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2761
+# 747a5560bbed48598ec8fb9ad2739dde
+msgid "Creating a Port Profile"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2765
+# 915567df98f3440f9c869a266292bebf
+msgid "Whether you create a Basic or Advanced zone configuration, ensure that you always create an Ethernet port profile on the VSM after you install it and before you create the zone."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2771
+# f27be294146746dd92354b86a70b9a34
+msgid "The Ethernet port profile created to represent the physical network or networks used by an Advanced zone configuration trunk all the VLANs including guest VLANs, the VLANs that serve the native VLAN, and the packet/control/data/management VLANs of the VSM."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2779
+# 14dcf98b714a4de493d3bd65c53e07b5
+msgid "The Ethernet port profile created for a Basic zone configuration does not trunk the guest VLANs because the guest VMs do not get their own VLANs provisioned on their network interfaces in a Basic zone."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2786
+# acc04f3bc9a547b0919324a8ed1430d4
+msgid "An Ethernet port profile configured on the Nexus 1000v virtual switch should not use in its set of system VLANs, or any of the VLANs configured or intended to be configured for use towards VMs or VM resources in the CloudStack environment."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2793
+# ddaca8ac1441456ebd7e21dcc838b22c
+msgid "You do not have to create any vEthernet port profiles – CloudStack does that during VM deployment."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2798
+# 380f259b08904003bff09f8cbc797634
+msgid "Ensure that you create required port profiles to be used by CloudStack for different traffic types of CloudStack, such as Management traffic, Guest traffic, Storage traffic, and Public traffic. The physical networks configured during zone creation should have a one-to-one relation with the Ethernet port profiles."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2804
+# a082dd98813f48b293e64d2a86f4c8a9
+msgid "|vmwarenexusportprofile.png: vSphere client|"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2806
+# f47a376ee3134e19a877759d2cddeec3
+msgid "For information on creating a port profile, see `Cisco Nexus 1000V Port Profile Configuration Guide <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_a/port_profile/configuration/guide/n1000v_port_profile.html>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2811
+# 7150678d8ad84958ad15325b7e295635
+msgid "Assigning Physical NIC Adapters"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2813
+# 0fcc662360f24246aa89af9504290713
+msgid "Assign ESXi host's physical NIC adapters, which correspond to each physical network, to the port profiles. In each ESXi host that is part of the vCenter cluster, observe the physical networks assigned to each port profile and note down the names of the port profile for future use. This mapping information helps you when configuring physical networks during the zone configuration on CloudStack. These Ethernet port profile names are later specified as VMware Traffic Labels for different traffic types when configuring physical networks during the zone configuration. For more information on configuring physical networks, see `\"Configuring a vSphere Cluster with Nexus 1000v Virtual Switch\" <#configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2825
+# bfdb4a3f2d1d498e8ea20b009ae3b41f
+msgid "Adding VLAN Ranges"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2827
+# ab086d39a6454950a4c821d832b8d0a6
+msgid "Determine the public VLAN, System VLAN, and Guest VLANs to be used by the CloudStack. Ensure that you add them to the port profile database. Corresponding to each physical network, add the VLAN range to port profiles. In the VSM command prompt, run the switchport trunk allowed vlan<range> command to add the VLAN ranges to the port profile."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2833
+#: ../../hypervisor_installation.rst:2846
+# 829a113f6355423c978bf7cca25f0a01
+# f2317ad7ae7148679ecc16cb7353da3b
+msgid "For example:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2839
+# 04401fdeab2f4ee4a97429af971bbd04
+msgid "In this example, the allowed VLANs added are 1, 140-147, and 196-203"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2841
+# c9d7e8243d494833b060ec436ef511f7
+msgid "You must also add all the public and private VLANs or VLAN ranges to the switch. This range is the VLAN range you specify in your zone."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2844
+# 963d8b9051d24f069022dea1d22daf9e
+msgid "Before you run the vlan command, ensure that the configuration mode is enabled in Nexus 1000v virtual switch."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2848
+# 51f537d407aa4bfa944be0d00b48f772
+msgid "If you want the VLAN 200 to be used on the switch, run the following command:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2855
+# cac6cabf1e994fea9fcc690bb4cb85d8
+msgid "If you want the VLAN range 1350-1750 to be used on the switch, run the following command:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2862
+# 2c87fe767ced4157a5a91a878982cd3b
+msgid "Refer to Cisco Nexus 1000V Command Reference of specific product version."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2866
+# e20558d2c83e4921a2ae5a4942fbf6a4
+msgid "Enabling Nexus Virtual Switch in CloudStack"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2868
+# 2f23da65b54842d7a760a7cb75dc5384
+msgid "To make a CloudStack deployment Nexus enabled, you must set the vmware.use.nexus.vswitch parameter true by using the Global Settings page in the CloudStack UI. Unless this parameter is set to \"true\" and restart the management server, you cannot see any UI options specific to Nexus virtual switch, and CloudStack ignores the Nexus virtual switch specific parameters specified in the AddTrafficTypeCmd, UpdateTrafficTypeCmd, and AddClusterCmd API calls."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2876
+# 2a1bbcac40824582944f6987b96e18bd
+msgid "Unless the CloudStack global parameter \"vmware.use.nexus.vswitch\" is set to \"true\", CloudStack by default uses VMware standard vSwitch for virtual network infrastructure. In this release, CloudStack doesn’t support configuring virtual networks in a deployment with a mix of standard vSwitch and Nexus 1000v virtual switch. The deployment can have either standard vSwitch or Nexus 1000v virtual switch."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2884
+# b01aa0230c104b8dbc702f5106681b86
+msgid "Configuring Nexus 1000v Virtual Switch in CloudStack"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2886
+# 55b47a1924834ab9bcf05fc1d5f2830f
+msgid "You can configure Nexus dvSwitch by adding the necessary resources while the zone is being created."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2889
+# ab30cc7f205a4b968f9d107cb9e536fc
+msgid "|vmwarenexusaddcluster.png: vmware nexus add cluster|"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2891
+# 3a6d505f9c0e4e06ad20d61688e9d360
+msgid "After the zone is created, if you want to create an additional cluster along with Nexus 1000v virtual switch in the existing zone, use the Add Cluster option. For information on creating a cluster, see `\"Add Cluster: vSphere\" <configuration.html#add-cluster-vsphere>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2896
+# ea487fd695374472b3cc28afaf8b7935
+msgid "In both these cases, you must specify the following parameters to configure Nexus virtual switch:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2900
+# 2f10aacae6b943778d44f84d722c4c40
+msgid "Parameters"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2902
+#: ../../hypervisor_installation.rst:3142
+# 954a0fcef76244e59ff7157df2ce9236
+# 6c098c5af55c4ef2832ddb1ea22a7756
+msgid "Cluster Name"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2902
+# cba6000d144e4dec8b5a6d503214b04e
+msgid "Enter the name of the cluster you created in vCenter. For example,\"cloud.cluster\"."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2903
+#: ../../hypervisor_installation.rst:3143
+# 5a2734feab1d4c3899f219dc7e0bc047
+# cb1115f5a4e6459f9d59941f73399499
+msgid "vCenter Host"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2903
+# a270577295e947aeb4f510cc1671250b
+msgid "Enter the host name or the IP address of the vCenter host where you have deployed the Nexus virtual switch."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2904
+#: ../../hypervisor_installation.rst:3144
+# 43b78f2519cd43a592186b681bbd758a
+# aca846fafd164bbfafb28f1bc1d23abd
+msgid "vCenter User name"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2904
+#: ../../hypervisor_installation.rst:3144
+# 7a017d72974241b181fa5e3cded99ba7
+# ff313f1172d84c6fb6ecc0ba3c6c01ca
+msgid "Enter the username that CloudStack should use to connect to vCenter. This user must have all administrative privileges."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2905
+#: ../../hypervisor_installation.rst:3145
+# fb40ce7817f34578a3644c0af373813e
+# ba61f2c3473c412c95dbaa2f80ece441
+msgid "Enter the password for the user named above."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2906
+#: ../../hypervisor_installation.rst:3146
+# ab8a34c645a042d69e48fc3f7dc9bd46
+# e15b104af30843118d478ff6a77775a8
+msgid "vCenter Datacenter"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2906
+# d5b61a5f9b5a4a35a74aee094bd31df8
+msgid "Enter the vCenter datacenter that the cluster is in. For example, \"cloud.dc.VM\"."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2907
+# dafa148e3c364171aa16aebbd2a377d6
+msgid "Nexus dvSwitch IP Address"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2907
+# 1f7fcac4b6f54bb9988b6c7b28d765ac
+msgid "The IP address of the VSM component of the Nexus 1000v virtual switch."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2908
+# 00db776b96ea48e0a3eb5546f466392d
+msgid "Nexus dvSwitch Username"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2908
+# 42df2254c26a49ed9a0b25aadf0ace64
+msgid "The admin name to connect to the VSM appliance."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2909
+# ae881d805b02440bab9e62dcf0a807d8
+msgid "Nexus dvSwitch Password"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2909
+# fd192f54264b48918f39207ffb2da278
+msgid "The corresponding password for the admin user specified above."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2914
+# a1357edc605446acb820b979fb132d55
+msgid "Removing Nexus Virtual Switch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2918
+# 09e2100542c640edbdf96af9d9029316
+msgid "In the vCenter datacenter that is served by the Nexus virtual switch, ensure that you delete all the hosts in the corresponding cluster."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2923
+# 141ee7173de14b2da44ea1708fa069f9
+msgid "Log in with Admin permissions to the CloudStack administrator UI."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2927
+# 7eee8789554c4d4393308c741352fa3f
+msgid "In the left navigation bar, select Infrastructure."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2931
+# 89db573e47724516be8db76bc1b1164d
+msgid "In the Infrastructure page, click View all under Clusters."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2935
+# fb174283e4aa42b08b34858e58f6e083
+msgid "Select the cluster where you want to remove the virtual switch."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2939
+# 527fc95732794445bdd79834dcb5a64c
+msgid "In the dvSwitch tab, click the name of the virtual switch."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2943
+# fecadbb783ed4a7fb44b7fefef7c8c51
+msgid "In the Details page, click Delete Nexus dvSwitch icon. |DeleteButton.png: button to delete dvSwitch|"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2946
+# 3110096d69604bf2a4f702eb6e1756bb
+msgid "Click Yes in the confirmation dialog box."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2949
+# 48610fff03ad42cb851d18020b200ba2
+msgid "Configuring a VMware Datacenter with VMware Distributed Virtual Switch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2951
+# b31d6d27a7d849239fde0b1173228bf4
+msgid "CloudStack supports VMware vNetwork Distributed Switch (VDS) for virtual network configuration in a VMware vSphere environment. This section helps you configure VMware VDS in a CloudStack deployment. Each vCenter server instance can support up to 128 VDS instances and each VDS instance can manage up to 500 VMware hosts."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2958
+# be70e6f87324407c9bf757efec52fa28
+msgid "About VMware Distributed Virtual Switch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2960
+# 9e77fcbc39f04ef98d83c991e2f6fe29
+msgid "VMware VDS is an aggregation of host-level virtual switches on a VMware vCenter server. VDS abstracts the configuration of individual virtual switches that span across a large number of hosts, and enables centralized provisioning, administration, and monitoring for your entire datacenter from a centralized interface. In effect, a VDS acts as a single virtual switch at the datacenter level and manages networking for a number of hosts in a datacenter from a centralized VMware vCenter server. Each VDS maintains network runtime state for VMs as they move across multiple hosts, enabling inline monitoring and centralized firewall services. A VDS can be deployed with or without Virtual Standard Switch and a Nexus 1000V virtual switch."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2977
+# 365a2690501340d78bc366fad0eaac7f
+msgid "VMware VDS is supported only on Public and Guest traffic in CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2982
+# db4195c57675402cbf5f2b8cfbf5a452
+msgid "VMware VDS does not support multiple VDS per traffic type. If a user has many VDS switches, only one can be used for Guest traffic and another one for Public traffic."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2988
+# 7ddee82f457e4e40972b79a0f45b6dfc
+msgid "Additional switches of any type can be added for each cluster in the same zone. While adding the clusters with different switch type, traffic labels is overridden at the cluster level."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2994
+# d5aec4e86dcd42178120945c7ffb2ffb
+msgid "Management and Storage network does not support VDS. Therefore, use Standard Switch for these networks."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:2999
+# e246769436bd49aeb25ed0a009f987a1
+msgid "When you remove a guest network, the corresponding dvportgroup will not be removed on the vCenter. You must manually delete them on the vCenter."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3006
+# 54eddf463262482a8c3dad6f5f2ae247
+msgid "For a smoother configuration of VMware VDS, note down the VDS name you have added in the datacenter before you start:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3009
+# 9cc248efd6174d1f95fcb79364dfe324
+msgid "|vds-name.png: Name of the dvSwitch as specified in the vCenter.|"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3011
+# e7d07e6efc854a6f91160737fc2dc730
+msgid "Use this VDS name in the following:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3015
+# 3b63424161524f9da4420d0fd98dcda4
+msgid "The switch name in the Edit traffic label dialog while configuring a public and guest traffic during zone creation."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3018
+# cc1e2b04ea1b412a9180f77ac2930ad1
+msgid "During a zone creation, ensure that you select VMware vNetwork Distributed Virtual Switch when you configure guest and public traffic type."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3022
+# 28c7098972e44723819b9108289414b9
+msgid "|traffic-type.png|"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3026
+# 0d77c0b1eab14dca879d121804431960
+msgid "The Public Traffic vSwitch Type field when you add a VMware VDS-enabled cluster."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3031
+# 929135e8bf4d4f4a97a4db420a38dfd9
+msgid "The switch name in the traffic label while updating the switch type in a zone."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3034
+# 366e9be0e6a0468d952b3f9f3f3306b0
+msgid "Traffic label format in the last case is [[\"Name of vSwitch/dvSwitch/EthernetPortProfile\"][,\"VLAN ID\"[,\"vSwitch Type\"]]]"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3036
+# eaba03f24031461693648bd7a76b3ec6
+msgid "The possible values for traffic labels are:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3040
+# 61df80b370aa491484457725b12a1694
+msgid "empty string"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3044
+# d6793cc7e2eb4556a8cce089bb5fb7ba
+msgid "dvSwitch0"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3048
+# b3f4e9ec50d242d0981bd4164476a989
+msgid "dvSwitch0,200"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3052
+# d1044d22ffaa4efbb6917233f25d33e7
+msgid "dvSwitch1,300,vmwaredvs"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3056
+# fe1f3e03cabb4594be05f4694247828e
+msgid "myEthernetPortProfile,,nexusdvs"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3060
+# b0f992c1c506410f99034c1590b1b36d
+msgid "dvSwitch0,,vmwaredvs"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3063
+# 0643bee72bf9427097e841fa867a1b1d
+msgid "The three fields to fill in are:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3067
+# 4e1d4397308e4b2784978fa2b399204e
+msgid "Name of the virtual / distributed virtual switch at vCenter."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3069
+# 0ea48308f4034803ace1fbce08fa1fd4
+msgid "The default value depends on the type of virtual switch:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3071
+# 06091102df12426db15a2fa2294255cc
+msgid "**vSwitch0**: If type of virtual switch is VMware vNetwork Standard virtual switch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3073
+# 2342c2b4f9554a848bfd6e018bda4ca8
+msgid "**dvSwitch0**: If type of virtual switch is VMware vNetwork Distributed virtual switch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3075
+# fc80358ec4c344b19e3b1396a4fe3f2b
+msgid "**epp0**: If type of virtual switch is Cisco Nexus 1000v Distributed virtual switch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3079
+# f9653fff8e2a4dfe9f57984ea973effd
+msgid "VLAN ID to be used for this traffic wherever applicable."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3081
+# 1f6e646a6ba742bebf304d510d52ec4b
+msgid "This field would be used for only public traffic as of now. In case of guest traffic this field would be ignored and could be left empty for guest traffic. By default empty string would be assumed which translates to untagged VLAN for that specific traffic type."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3085
+# 5b4d56e3828a431fb972d1a30cbb5993
+msgid "Type of virtual switch. Specified as string."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3087
+# 34474cbb49e5499fb1e02724466f1dd4
+msgid "Possible valid values are vmwaredvs, vmwaresvs, nexusdvs."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3089
+# 8178f6130ecb48baaea165ae9e8b0846
+msgid "**vmwaresvs**: Represents VMware vNetwork Standard virtual switch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3091
+# a651a8e73a224d75a56b6c95f2997e8f
+msgid "**vmwaredvs**: Represents VMware vNetwork distributed virtual switch"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3093
+# 6b485445cf314856bf788804ac1279f0
+msgid "**nexusdvs**: Represents Cisco Nexus 1000v distributed virtual switch."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3095
+# 2d56af8dccba48b2b2d17ffd03843c42
+msgid "If nothing specified (left empty), zone-level default virtual switchwould be defaulted, based on the value of global parameter you specify."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3097
+# 3835c2ef7574443589a59537ac4b5ee1
+msgid "Following are the global configuration parameters:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3099
+# 14d738f065094961bd6549867db82e73
+msgid "**vmware.use.dvswitch**: Set to true to enable any kind (VMware DVS and Cisco Nexus 1000v) of distributed virtual switch in a CloudStack deployment. If set to false, the virtual switch that can be used in that CloudStack deployment is Standard virtual switch."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3101
+# ec24241206114feba067a6c3b0ecf676
+msgid "**vmware.use.nexus.vswitch**: This parameter is ignored if vmware.use.dvswitch is set to false. Set to true to enable Cisco Nexus 1000v distributed virtual switch in a CloudStack deployment."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3104
+# e0c3306fd9204cee84716a8bb08ebf9a
+msgid "Enabling Virtual Distributed Switch in CloudStack"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3106
+# 64c49f56242149a085fb175bfd6b2536
+msgid "To make a CloudStack deployment VDS enabled, set the vmware.use.dvswitch parameter to true by using the Global Settings page in the CloudStack UI and restart the Management Server. Unless you enable the vmware.use.dvswitch parameter, you cannot see any UI options specific to VDS, and CloudStack ignores the VDS-specific parameters that you specify. Additionally, CloudStack uses VDS for virtual network infrastructure if the value of vmware.use.dvswitch parameter is true and the value of vmware.use.nexus.dvswitch parameter is false. Another global parameter that defines VDS configuration is vmware.ports.per.dvportgroup. This is the default number of ports per VMware dvPortGroup in a VMware environment. Default value is 256. This number directly associated with the number of guest network you can create."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3120
+# e5f3b06f38324241a2052677a1dad016
+msgid "CloudStack supports orchestration of virtual networks in a deployment with a mix of Virtual Distributed Switch, Standard Virtual Switch and Nexus 1000v Virtual Switch."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3125
+# 37f6094d78df4e1aa3500f2b84650486
+msgid "Configuring Distributed Virtual Switch in CloudStack"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3127
+# 3bc24235a56b49a18dd705133f2de55b
+msgid "You can configure VDS by adding the necessary resources while a zone is created."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3130
+# c3a360b9f4564ac1abb2197484db4e3c
+msgid "Alternatively, at the cluster level, you can create an additional cluster with VDS enabled in the existing zone. Use the Add Cluster option. For information as given in `“Add Cluster: vSphere” <configuration.html#add-cluster-vsphere>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3134
+# 479bfd3ed9a447da942d9b9ac2a2fdc2
+msgid "In both these cases, you must specify the following parameters to configure VDS:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3137
+# ebf6c05366ba437e921f5903665ed973
+msgid "|dvSwitchConfig.png: Configuring dvSwitch|"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3140
+# 09b1c441a46c49469130fa72f3614964
+msgid "Parameters Description"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3142
+# 708394a025b4492ab6e327dc380958e7
+msgid "Enter the name of the cluster you created in vCenter. For example, \"cloudcluster\"."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3143
+# d6c67ed27d304002a729b1628fb70fa0
+msgid "Enter the name or the IP address of the vCenter host where you have deployed the VMware VDS."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3146
+# 683d246203ba4cf8b5fd0d8e85bd640e
+msgid "Enter the vCenter datacenter that the cluster is in. For example, \"clouddcVM\"."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3147
+# 9fb1a295d3cf4ccf86187b7b78cf93b2
+msgid "Override Public Traffic"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3147
+# ea178483ff274a928f854444818454a2
+msgid "Enable this option to override the zone-wide public traffic for the cluster you are creating."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3148
+# 250b987e45194b0b9cb86b6b9fb5e336
+msgid "Public Traffic vSwitch Type"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3148
+# b367523933b940aeaec12800a746a45d
+msgid "This option is displayed only if you enable the Override Public Traffic option. Select VMware vNetwork Distributed Virtual Switch. If the vmware.use.dvswitch global parameter is true, the default option will be VMware vNetwork Distributed Virtual Switch."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3149
+# 29cb482d8776432b8c99b7e4c79cbe12
+msgid "Public Traffic vSwitch Name"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3149
+# 086236537a4f4fc1a5440d11b0fca364
+msgid "Name of virtual switch to be used for the public traffic."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3150
+# 704199c7e7eb4f1398126a60a08794de
+msgid "Override Guest Traffic"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3150
+# 8f90f04bd418418f9eadbd9c926cb76f
+msgid "Enable the option to override the zone-wide guest traffic for the cluster you are creating."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3151
+# 899928be044a48258741946368d91dcb
+msgid "Guest Traffic vSwitch Type"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3151
+# 6ddc80e638ab4ec8a613165199a028b0
+msgid "This option is displayed only if you enable the Override Guest Traffic option. Select VMware vNetwork Distributed Virtual Switch. If the vmware.use.dvswitch global parameter is true, the default option will be VMware vNetwork Distributed Virtual Switch."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3152
+# 5e253936428944ae8e8a5ebfadeea77a
+msgid "Guest Traffic vSwitch Name"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3152
+# 15215df1285d4b2985dfa06f3c8819ea
+msgid "Name of virtual switch to be used for guest traffic."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3157
+# 774f8b0295a24386bce8cafe1f15f999
+msgid "Storage Preparation for vSphere (iSCSI only)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3159
+# ba00d524d9b244f2b911edffa0f8ded8
+msgid "Use of iSCSI requires preparatory work in vCenter. You must add an iSCSI target and create an iSCSI datastore."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3162
+# 8de2dece46ff46c8bac0bbd1e48b778d
+msgid "If you are using NFS, skip this section."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3165
+# fc698c19eb8549ed98ec961c04d753e1
+msgid "Enable iSCSI initiator for ESXi hosts"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3169
+# 34512553af0249bea54fc8b9585cd5fa
+msgid "In vCenter, go to hosts and Clusters/Configuration, and click Storage Adapters link. You will see:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3172
+# 684af7b07b1a459fb4e36ed78a8a83e6
+msgid "|vmwareiscsiinitiator.png: iscsi initiator|"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3176
+# 88e4da9927b54ee1a9a6654aa6d39aa3
+msgid "Select iSCSI software adapter and click Properties."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3178
+# 2e32277888274a049d00699208d7bc97
+msgid "|vmwareiscsiinitiatorproperties.png: iscsi initiator properties|"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3182
+# 8da2aa000a374d80acff80053a7e341f
+msgid "Click the Configure... button."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3184
+# 59b2ef32cfdd4082b497b9cb05555129
+msgid "|vmwareiscsigeneral.png: iscsi general|"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3188
+# e1eceaf44d2644f18076f265f4360592
+msgid "Check Enabled to enable the initiator."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3192
+# e1263727e0d64a2ab200698db27ee1a3
+msgid "Click OK to save."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3195
+# a210655c2dff4ddcb276836b8603412d
+msgid "Add iSCSI target"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3197
+# abb57513fb3244288ea5ce00445f8f28
+msgid "Under the properties dialog, add the iSCSI target info:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3199
+# 4954b59047ab4ba29e2d92e3865b0fda
+msgid "|vmwareiscsitargetadd.png: iscsi target add|"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3201
+# 88ca6dc96bb9499f9d1c7abcaff20aa3
+msgid "Repeat these steps for all ESXi hosts in the cluster."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3204
+# 8bd62c3be43c48d493e98576eefe23f8
+msgid "Create an iSCSI datastore"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3206
+# c548bf48a3674abb83e7b473c8e3f84f
+msgid "You should now create a VMFS datastore. Follow these steps to do so:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3210
+# c518b88e8ecd4da09c536f9d74b508d3
+msgid "Select Home/Inventory/Datastores."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3214
+# cdb74717625a427aa3c4a7ba5f93aee1
+msgid "Right click on the datacenter node."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3218
+# 3d0a816c956442cf8c5b1f81c174ee22
+msgid "Choose Add Datastore... command."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3222
+# 19ad87337cb14cf585faf240d0ee2832
+msgid "Follow the wizard to create a iSCSI datastore."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3224
+# 7948a9ab7759441cbca06015f98026f0
+msgid "This procedure should be done on one host in the cluster. It is not necessary to do this on all hosts."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3227
+# cfb21f6f84204119bd99ba701e71a839
+msgid "|vmwareiscsidatastore.png: iscsi datastore|"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3230
+# 05536385fb5d4f589729735e6a15863a
+msgid "Multipathing for vSphere (Optional)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3232
+# 815ee00c2ff84bffb47b6cab9a634126
+msgid "Storage multipathing on vSphere nodes may be done according to the vSphere installation guide."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3236
+# 58b67a39f15e42eea22e40e779bc98ae
+msgid "Add Hosts or Configure Clusters (vSphere)"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3238
+# 0f8ce9626c69404f8406c300f622fb16
+msgid "Use vCenter to create a vCenter cluster and add your desired hosts to the cluster. You will later add the entire cluster to CloudStack. (see `“Add Cluster: vSphere” <configuration.html#add-cluster-vsphere>`_)."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3243
+# 7e7aadc035da44249de56ae7db92234a
+msgid "Applying Hotfixes to a VMware vSphere Host"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3247
+# 74dba888d905486db0290fbfb7d772f6
+msgid "Disconnect the VMware vSphere cluster from CloudStack. It should remain disconnected long enough to apply the hotfix on the host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3254
+# da103b2f65c547b3ab083fc895aab582
+msgid "See `“Log In to the UI” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3258
+# 7eeb8799b8aa4cc69456b839d9136ad7
+msgid "Navigate to the VMware cluster, click Actions, and select Unmanage."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3267
+# d9e060820ffb4eb4b154fad98fd3ffa6
+msgid "Perform the following on each of the ESXi hosts in the cluster:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3271
+# d9e7f843369e4a78b51521805078baf0
+msgid "Move each of the ESXi hosts in the cluster to maintenance mode."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3275
+# 9bc4f3ee334e40db91a24562dd6845cd
+msgid "Ensure that all the VMs are migrated to other hosts in that cluster."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3280
+# 3ba2bffbc5e84ef3b01cae9d2dde0b71
+msgid "If there is only one host in that cluster, shutdown all the VMs and move the host into maintenance mode."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3285
+# 6f64d848a8d64604844df448df999fe1
+msgid "Apply the patch on the ESXi host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3289
+# 9c8782c75494411594d8b4faff7fbb1d
+msgid "Restart the host if prompted."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3293
+# 25e36bd88cc24b0383e1b00df74727ad
+msgid "Cancel the maintenance mode on the host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3297
+# aaff92bbaee04efbbe1d87fdb627fcbf
+msgid "Reconnect the cluster to CloudStack:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3305
+# da1d669463434dc087c342d31407e02f
+msgid "Navigate to the VMware cluster, click Actions, and select Manage."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3309
+# fdb2ca3517e249e792bc1e09f0dcdf74
+msgid "Watch the status to see that all the hosts come up. It might take several minutes for the hosts to come up."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3312
+# 9cb4b470519146d4993237038291de2a
+msgid "Alternatively, verify the host state is properly synchronized and updated in the CloudStack database."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3316
+# ed31c9f3cf034bde88229da9ab4c4346
+msgid "LXC Installation and Configuration"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3319
+# 8b616c9ac2f844a4a829952baa39a8d0
+msgid "System Requirements for LXC Hosts"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3321
+# 219a7faad8ee431a8c64dfb3c12b2006
+msgid "LXC requires the Linux kernel cgroups functionality which is available starting 2.6.24. Although you are not required to run these distributions, the following are recommended:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3333
+# 5a6c2e85c2114428bfbb1d20f74e4205
+msgid "The main requirement for LXC hypervisors is the libvirt and Qemu version. No matter what Linux distribution you are using, make sure the following requirements are met:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3339
+#: ../../hypervisor_installation.rst:3351
+# d7670075be644f0f80515c081452803e
+# 40888512180848d2809af703d71e45d4
+msgid "libvirt: 1.0.0 or higher"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3391
+# be2989bd0e4c4180acf1abe0c0506e16
+msgid "LXC Installation Overview"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3393
+# 03fc8905df0d492d9aa9667071f355fc
+msgid "LXC does not have any native system VMs, instead KVM will be used to run system VMs. This means that your host will need to support both LXC and KVM, thus most of the installation and configuration will be identical to the KVM installation. The material in this section doesn't duplicate KVM installation docs. It provides the CloudStack-specific steps that are needed to prepare a KVM host to work with CloudStack."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3404
+# 2b1366e9b99546e58720ccf100d16276
+msgid "The procedure for installing an LXC Host is:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3479
+# 84a60e9ea64b44d09cda82651720fefe
+msgid "To manage LXC instances on the host CloudStack uses a Agent. This Agent communicates with the Management server and controls all the instances on the host."
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3497
+# 6e8937e78ff6442db35604533d058b4a
+msgid "Next step is to update the Agent configuration setttings. The settings are in ``/etc/cloudstack/agent/agent.properties``"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3502
+# 7aeff42329424749810bdfb5dd405477
+msgid "Set the Agent to run in LXC mode:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3510
+# ac8184a4dc794aba9e64574610cfe257
+msgid "Optional: If you would like to use direct networking (instead of the default bridge networking), configure these lines:"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3595
+# 195b19dc40204c8b94d2cb8e43198e2e
+msgid "In order to have the VNC Console work we have to make sure it will bind on 0.0.0.0. We do this by editing ``/etc/libvirt/qemu.conf``"
+msgstr ""
+
+#: ../../hypervisor_installation.rst:3598
+# 48827fdb267f46b3be0c06af135ba563
+msgid "Make sure this parameter is set:"
+msgstr ""
+
diff --git a/source/installguide/locale/pot/index.pot b/source/installguide/locale/pot/index.pot
new file mode 100644
index 0000000..c236de2
--- /dev/null
+++ b/source/installguide/locale/pot/index.pot
@@ -0,0 +1,98 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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
+# 982ed5120e594d65bcff280a0398f5af
+msgid "Welcome to CloudStack Installation Documentation"
+msgstr ""
+
+#: ../../index.rst:29
+# 1f1f369df4b645e0bbda82cf077bdbd6
+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:33
+# b3e6055f64164ee0b851226b5573bfb3
+msgid "This is the Apache CloudStack installation guide, for the Documentation home, the administrator guide or the Release-Notes please see:"
+msgstr ""
+
+#: ../../index.rst:36
+# b643ff53ad664a829c30729664d2ad00
+msgid "`Documentation home <http://docs.cloudstack.apache.org>`_"
+msgstr ""
+
+#: ../../index.rst:38
+# 2cf98f8dcdff4610b15031a039d4c5c6
+msgid "`Administration Guide <http://docs.cloudstack.apache.org/projects/cloudstack-administration>`_"
+msgstr ""
+
+#: ../../index.rst:41
+# a98ac35a7f2b4cf9b3090ff68dc12650
+msgid "`Release Notes <http://docs.cloudstack.apache.org/projects/cloudstack-release-notes>`_"
+msgstr ""
+
+#: ../../index.rst:45
+# 86316507b4b44a5a96cfdb3721f97bd4
+msgid "In this guide we first go through some design and architectural choices_ to build your cloud. Then we dive into a single node quick start guide_ to give you a feel for the installation process. The source installation steps_ are given in the follow-on section for people who want to build their own packages. Otherwise you can use the general installation_ which makes use of community maintained package repositories. The rest of the guide goes through the configuration_ of the data-center and the setup of the network_, storage_ and hypervisors_."
+msgstr ""
+
+#: ../../index.rst:60
+# df08cf7ea88245c086043ad57af8e8ac
+msgid "Choosing a Deployment Architecture"
+msgstr ""
+
+#: ../../index.rst:70
+# dbccc2fe994c4999b821643c7bde3eb3
+msgid "Quick Installation Guide"
+msgstr ""
+
+#: ../../index.rst:80
+# a05a3c5a35ca46418756c797e93cdc38
+msgid "Source Installation"
+msgstr ""
+
+#: ../../index.rst:90
+# 42b62bda8da0413d80b6718dab581b66
+msgid "General Installation"
+msgstr ""
+
+#: ../../index.rst:100
+# e9c99f765efc4b4396d3d68516bd9f05
+msgid "Configuration"
+msgstr ""
+
+#: ../../index.rst:110
+# e126703be1d04fb1a536bbecd12daafa
+msgid "Hypervisor Setup"
+msgstr ""
+
+#: ../../index.rst:121
+# 64d7386116784ddfbfaee06209c06377
+msgid "Network Setup"
+msgstr ""
+
+#: ../../index.rst:131
+# ca4526f59f884297b45db3c6d92cd6a6
+msgid "Storage Setup"
+msgstr ""
+
+#: ../../index.rst:139
+# a7129d9d6924487eb5056763f614e703
+msgid "Optional Installation"
+msgstr ""
+
diff --git a/source/installguide/locale/pot/installation.pot b/source/installguide/locale/pot/installation.pot
new file mode 100644
index 0000000..11b4ccf
--- /dev/null
+++ b/source/installguide/locale/pot/installation.pot
@@ -0,0 +1,1224 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../installation.rst:18
+# a4c7e830381745529dad6a0b1d27abc8
+msgid "Installation"
+msgstr ""
+
+#: ../../installation.rst:21
+# 08b24c18afac496395e10054c9cf0e71
+msgid "Who Should Read This"
+msgstr ""
+
+#: ../../installation.rst:23
+# d5a90994aea94deab277060989225b05
+msgid "For those who have already gone through a design phase and planned a more sophisticated deployment, or those who are ready to start scaling up a trial installation. With the following procedures, you can start using the more powerful features of CloudStack, such as advanced VLAN networking, high availability, additional network elements such as load balancers and firewalls, and support for multiple hypervisors including Citrix XenServer, KVM, and VMware vSphere."
+msgstr ""
+
+#: ../../installation.rst:33
+# e7eb83f865c242ae89ad4c8ae65ed988
+msgid "Overview of Installation Steps"
+msgstr ""
+
+#: ../../installation.rst:35
+# fc6cbd3f722e496ca3d7a1716a44bc03
+msgid "For anything more than a simple trial installation, you will need guidance for a variety of configuration choices. It is strongly recommended that you read the following:"
+msgstr ""
+
+#: ../../installation.rst:39
+# 718aecc72e104a2997aba969ae4564c4
+msgid "Choosing a Deployment Architecture"
+msgstr ""
+
+#: ../../installation.rst:41
+# cd6d4bbfdbcb4ae0953b3b36d308c7f5
+msgid "Choosing a Hypervisor: Supported Features"
+msgstr ""
+
+#: ../../installation.rst:43
+# 2a0787f9ba6d4b13ba9574e2a6334c2f
+msgid "Network Setup"
+msgstr ""
+
+#: ../../installation.rst:45
+# f606c83b98e54324a4376e39edcd5e20
+msgid "Storage Setup"
+msgstr ""
+
+#: ../../installation.rst:47
+# 75e8e878e0284aeeb3f52820e7b675eb
+msgid "Best Practices"
+msgstr ""
+
+#: ../../installation.rst:49
+# c1ad793994b9421295f7503b7488274c
+msgid "Make sure you have the required hardware ready. See :ref:`minimum-system-requirements`"
+msgstr ""
+
+#: ../../installation.rst:52
+# f5dba433b73f4e4b985060a388b195f0
+msgid "Install the Management Server (choose single-node or multi-node). See :ref:`adding-a-zone`"
+msgstr ""
+
+#: ../../installation.rst:55
+# 58ea8b1ced9547bfa75c75859ac799cc
+msgid "Log in to the UI. See `*User Interface* <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_"
+msgstr ""
+
+#: ../../installation.rst:58
+# d05317e5c0ee48f6b90a44c8b2fcf367
+msgid "Add a zone. Includes the first pod, cluster, and host. See :ref:`adding-a-host`"
+msgstr ""
+
+#: ../../installation.rst:61
+# b534b474577b4160ba2cd604d9d52532
+msgid "Add more pods (optional). See :ref:`adding-a-pod`"
+msgstr ""
+
+#: ../../installation.rst:63
+# 299d7e46a3df47ac8e42ee1933e4f29a
+msgid "Add more clusters (optional). See :ref:`adding-a-cluster`"
+msgstr ""
+
+#: ../../installation.rst:65
+# dedefe67789b49af8ace78432dfc2868
+msgid "Add more hosts (optional). See :ref:`adding-a-host`"
+msgstr ""
+
+#: ../../installation.rst:67
+# 920aa393f8604a648a3f4303e57d1775
+msgid "Add more primary storage (optional). See :ref:`add-primary-storage`"
+msgstr ""
+
+#: ../../installation.rst:69
+# da3f95f402c24f0aa74c36350d5ec371
+msgid "Add more secondary storage (optional). See :ref:`add-secondary-storage`"
+msgstr ""
+
+#: ../../installation.rst:71
+# 310612dae82445ae8be69f78801a9750
+msgid "Try using the cloud. See :ref:`initialize-and-test`"
+msgstr ""
+
+#: ../../installation.rst:77
+# 482c0b3104aa43dfb72e0a4f853e1463
+msgid "Minimum System Requirements"
+msgstr ""
+
+#: ../../installation.rst:80
+# ea094f27fd264abe88f63697eb32c463
+msgid "Management Server, Database, and Storage System Requirements"
+msgstr ""
+
+#: ../../installation.rst:82
+# 910332017d854085a74ff0715162f1b2
+msgid "The machines that will run the Management Server and MySQL database must meet the following requirements. The same machines can also be used to provide primary and secondary storage, such as via localdisk or NFS. The Management Server may be placed on a virtual machine."
+msgstr ""
+
+#: ../../installation.rst:87
+# 8e4f1eb139534c4ca4d93f7537dd3fa7
+msgid "Operating system:"
+msgstr ""
+
+#: ../../installation.rst:89
+# 29b8ae9600b245fe9c60f040f52adfa5
+msgid "Preferred: CentOS/RHEL 6.3+ or Ubuntu 14.04(.1)"
+msgstr ""
+
+#: ../../installation.rst:91
+#: ../../installation.rst:114
+# 24d4cd50a00945eb98763313d2f65f17
+# 1c5c18472c5644a89e3aecc627b13b6c
+msgid "64-bit x86 CPU (more cores results in better performance)"
+msgstr ""
+
+#: ../../installation.rst:93
+#: ../../installation.rst:118
+# 851608c72118406792e449b1d8c7b83a
+# 4f02c321329446d5815a250b05fe2778
+msgid "4 GB of memory"
+msgstr ""
+
+#: ../../installation.rst:95
+# 4d8ce09b8a0542e892df38be3af682bf
+msgid "250 GB of local disk (more results in better capability; 500 GB recommended)"
+msgstr ""
+
+#: ../../installation.rst:98
+#: ../../installation.rst:122
+# 165ce3c523d64e48b04f71ebd0996dd9
+# 4ab891d3ef9f4fdda64c88a8120a9205
+msgid "At least 1 NIC"
+msgstr ""
+
+#: ../../installation.rst:100
+# 1ada394b4bf74ee5a1152e0e725fd331
+msgid "Statically allocated IP address"
+msgstr ""
+
+#: ../../installation.rst:102
+# 230435b75353467b84290fa91c4c08b8
+msgid "Fully qualified domain name as returned by the hostname command"
+msgstr ""
+
+#: ../../installation.rst:106
+# 69ac02bcef5348719f0240d8836e0006
+msgid "Host/Hypervisor System Requirements"
+msgstr ""
+
+#: ../../installation.rst:108
+# 1820da09a6ae428f9ae4bd3ce16ef3c5
+msgid "The host is where the cloud services run in the form of guest virtual machines. Each host is one machine that meets the following requirements:"
+msgstr ""
+
+#: ../../installation.rst:112
+# 8eecb5d0a6ee40a395e47f52168d5d20
+msgid "Must support HVM (Intel-VT or AMD-V enabled)."
+msgstr ""
+
+#: ../../installation.rst:116
+# c6343d4def954507b56afb34ef637859
+msgid "Hardware virtualization support required"
+msgstr ""
+
+#: ../../installation.rst:120
+# 292a0c2480e44ec4a30cbc5689aa828a
+msgid "36 GB of local disk"
+msgstr ""
+
+#: ../../installation.rst:125
+# 951d1eb038d94e3bac57bdfcc52377af
+msgid "If DHCP is used for hosts, ensure that no conflict occurs between DHCP server used for these hosts and the DHCP router created by CloudStack."
+msgstr ""
+
+#: ../../installation.rst:128
+# 142b536acb8941f29e7b44145c079dfa
+msgid "Latest hotfixes applied to hypervisor software"
+msgstr ""
+
+#: ../../installation.rst:130
+# 9815b650b1b94eba9ad10c4684f5cb0a
+msgid "When you deploy CloudStack, the hypervisor host must not have any VMs already running"
+msgstr ""
+
+#: ../../installation.rst:133
+# 56e1f4ebe58147f5abd5c96844f64bb5
+msgid "All hosts within a cluster must be homogeneous. The CPUs must be of the same type, count, and feature flags."
+msgstr ""
+
+#: ../../installation.rst:136
+# 00933a4ac68a4d19b25c5a6eb58c517e
+msgid "Hosts have additional requirements depending on the hypervisor. See the requirements listed at the top of the Installation section for your chosen hypervisor:"
+msgstr ""
+
+#: ../../installation.rst:141
+# 962bf99b90fa4d2a8edf81295e1df42a
+msgid "Be sure you fulfill the additional hypervisor requirements and installation steps provided in this Guide. Hypervisor hosts must be properly prepared to work with CloudStack. For example, the requirements for XenServer are listed under Citrix XenServer Installation."
+msgstr ""
+
+#: ../../installation.rst:148
+# 124105e82a0647a994481c09b2a6e3fd
+msgid "Configure package repository"
+msgstr ""
+
+#: ../../installation.rst:150
+# cd54d36f52df4a02bd4ee88dbaa9ac5d
+msgid "CloudStack is only distributed from source from the official mirrors. However, members of the CloudStack community may build convenience binaries so that users can install Apache CloudStack without needing to build from source."
+msgstr ""
+
+#: ../../installation.rst:155
+# a904edd1fa324be999f28aad8271c6e3
+msgid "If you didn't follow the steps to build your own packages from source in the sections for `“Building RPMs from Source” <building_from_source.html#building-rpms-from-source>`_ or `“Building DEB packages” <building_from_source.html#building-deb-packages>`_ you may find pre-built DEB and RPM packages for your convenience linked from the `downloads <http://cloudstack.apache.org/downloads.html>`_ page."
+msgstr ""
+
+#: ../../installation.rst:163
+# 2cd5d4a70be54d9fad1ee09ac0a59781
+msgid "These repositories contain both the Management Server and KVM Hypervisor packages."
+msgstr ""
+
+#: ../../installation.rst:168
+# ea53cfd031f54c11b1c35976f3e3ce76
+msgid "DEB package repository"
+msgstr ""
+
+#: ../../installation.rst:170
+# d5c18e89ae43496093da2abe5de613ad
+msgid "You can add a DEB package repository to your apt sources with the following commands. Please note that only packages for Ubuntu 14.04 LTS (trusty) and Ubuntu 16.04 (Xenial)are being built at this time. DISCLAIMER: Ubuntu 12.04 (Precise) is no longer supported."
+msgstr ""
+
+#: ../../installation.rst:174
+# 80c95c86ec504d6ea8771c2c09678dce
+msgid "Use your preferred editor and open (or create) ``/etc/apt/sources.list.d/cloudstack.list``. Add the community provided repository to the file:"
+msgstr ""
+
+#: ../../installation.rst:182
+# 4e809dbba4344fe3bbe0c803b417c4a5
+msgid "We now have to add the public key to the trusted keys."
+msgstr ""
+
+#: ../../installation.rst:188
+# 3308e4a303fa4e109dfe4f012bb673a1
+msgid "Now update your local apt cache."
+msgstr ""
+
+#: ../../installation.rst:194
+# 499fecdd520c470e9e64923350071343
+msgid "Your DEB package repository should now be configured and ready for use."
+msgstr ""
+
+#: ../../installation.rst:198
+# 4201a19d82ec40359482777eca721afe
+msgid "RPM package repository"
+msgstr ""
+
+#: ../../installation.rst:200
+# a8e0ee6a46fe473f84e190a7a84274a9
+msgid "There is a RPM package repository for CloudStack so you can easily install on RHEL based platforms."
+msgstr ""
+
+#: ../../installation.rst:203
+# 0c1bb2bafcf9461ebb5cd59ead93db9f
+msgid "If you're using an RPM-based system, you'll want to add the Yum repository so that you can install CloudStack with Yum."
+msgstr ""
+
+#: ../../installation.rst:206
+# 562991c4185349599619509cfbce173d
+msgid "Yum repository information is found under ``/etc/yum.repos.d``. You'll see several ``.repo`` files in this directory, each one denoting a specific repository."
+msgstr ""
+
+#: ../../installation.rst:210
+# e49d0a5613af49f69d54163f32b5f898
+msgid "To add the CloudStack repository, create ``/etc/yum.repos.d/cloudstack.repo`` and insert the following information."
+msgstr ""
+
+#: ../../installation.rst:222
+# d78ed0190d354e4bac2f1c82b8c21dd9
+msgid "Now you should be able to install CloudStack using Yum."
+msgstr ""
+
+#: ../../installation.rst:226
+# 37094bccdf5f4a6db4dc73588c0d1bc4
+msgid "Management Server Installation"
+msgstr ""
+
+#: ../../installation.rst:229
+# f57b33dd6c14414ab5c880b0b9a0c438
+msgid "Management Server Installation Overview"
+msgstr ""
+
+#: ../../installation.rst:231
+# 5273d79a7d1f4a12ac19c6d2fdff6406
+msgid "This section describes installing the Management Server. There are two slightly different installation flows, depending on how many Management Server nodes will be in your cloud:"
+msgstr ""
+
+#: ../../installation.rst:235
+# e05140db89854adbaa7419d25e9dc6ce
+msgid "A single Management Server node, with MySQL on the same node."
+msgstr ""
+
+#: ../../installation.rst:237
+# 06bdcc369df244f99ad92914eb680347
+msgid "Multiple Management Server nodes, with MySQL on a node separate from the Management Servers."
+msgstr ""
+
+#: ../../installation.rst:240
+# e4b810d71c474f4f98cb64eb346d7404
+msgid "In either case, each machine must meet the system requirements described in System Requirements."
+msgstr ""
+
+#: ../../installation.rst:244
+# 8c6a890d62c94b3c805523d0e55b6b45
+msgid "For the sake of security, be sure the public Internet can not access port 8096 or port 8250 on the Management Server."
+msgstr ""
+
+#: ../../installation.rst:247
+# 346be7547c7f40ac94d3fd4d11d242b8
+msgid "The procedure for installing the Management Server is:"
+msgstr ""
+
+#: ../../installation.rst:249
+#: ../../installation.rst:265
+# f5dab499f03647d4b215ac7dc00d2cc8
+# 1d99cd2343054c51bc38e14ba435eef4
+msgid "Prepare the Operating System"
+msgstr ""
+
+#: ../../installation.rst:251
+# 4eb68311296e426493a33ddad4958fd8
+msgid "(XenServer only) Download and install vhd-util."
+msgstr ""
+
+#: ../../installation.rst:253
+# 55d017a2eb3048f1a6e12d9af9ebdc95
+msgid "Install the First Management Server"
+msgstr ""
+
+#: ../../installation.rst:255
+# be88182cc4d841e884f72dc58d0c597b
+msgid "Install and Configure the MySQL database"
+msgstr ""
+
+#: ../../installation.rst:257
+#: ../../installation.rst:835
+# 4c17f8202a1a463589bea6ccc1e5da82
+# e69fe8462a0d4dfc9884fe69c7555783
+msgid "Prepare NFS Shares"
+msgstr ""
+
+#: ../../installation.rst:259
+# e5c5a79c1bbb41a5a37c13f1bcb2269b
+msgid "Prepare and Start Additional Management Servers (optional)"
+msgstr ""
+
+#: ../../installation.rst:261
+#: ../../installation.rst:1124
+# bb0613b20bae44ec8ea0d6cf3daf54d7
+# 72e55f8870934e6c8f91c0d9a02b53a0
+msgid "Prepare the System VM Template"
+msgstr ""
+
+#: ../../installation.rst:267
+# b185c81663174e87aec00ebea42b6106
+msgid "The OS must be prepared to host the Management Server using the following steps. These steps must be performed on each Management Server node."
+msgstr ""
+
+#: ../../installation.rst:271
+# ad31e2f017254bf4a8bc4b18ed1eb333
+msgid "Log in to your OS as root."
+msgstr ""
+
+#: ../../installation.rst:273
+# f68b5990a29e47a49e5576f3448ae36a
+msgid "Check for a fully qualified hostname."
+msgstr ""
+
+#: ../../installation.rst:279
+# 68c1a1f0f21745aeb403104055ac4fa9
+msgid "This should return a fully qualified hostname such as \"management1.lab.example.org\". If it does not, edit /etc/hosts so that it does."
+msgstr ""
+
+#: ../../installation.rst:283
+# 462aa5bfa1ed4426a0fe8fee25f76011
+msgid "Make sure that the machine can reach the Internet."
+msgstr ""
+
+#: ../../installation.rst:289
+# 5b249851325348f5a05df2a11b1a9605
+msgid "Turn on NTP for time synchronization."
+msgstr ""
+
+#: ../../installation.rst:292
+# e81842c1ee6c4557856769bb6a36922d
+msgid "NTP is required to synchronize the clocks of the servers in your cloud."
+msgstr ""
+
+#: ../../installation.rst:294
+# 1ff32df950c6457084e12020a249a243
+msgid "Install NTP."
+msgstr ""
+
+#: ../../installation.rst:304
+# dbe1f8c7f9d8488598b40da7132bc863
+msgid "Repeat all of these steps on every host where the Management Server will be installed."
+msgstr ""
+
+#: ../../installation.rst:309
+# 332fe2c7d34f46a2b229fc215761f6c4
+msgid "Install the Management Server on the First Host"
+msgstr ""
+
+#: ../../installation.rst:311
+# 8f353218baed48e4be6f9ca53b9c2541
+msgid "The first step in installation, whether you are installing the Management Server on one host or many, is to install the software on a single node."
+msgstr ""
+
+#: ../../installation.rst:316
+# 2a1b09c8c09641489db8c0d49c04ae16
+msgid "If you are planning to install the Management Server on multiple nodes for high availability, do not proceed to the additional nodes yet. That step will come later."
+msgstr ""
+
+#: ../../installation.rst:320
+# 407f24df1ba44541821f28c24576289f
+msgid "The CloudStack Management server can be installed using either RPM or DEB packages. These packages will depend on everything you need to run the Management server."
+msgstr ""
+
+#: ../../installation.rst:326
+# de7dec2f592640af80d9557e78bdc3af
+msgid "Install on CentOS/RHEL"
+msgstr ""
+
+#: ../../installation.rst:328
+# 0f47773dda6d44e5a36844163a8642b9
+msgid "We start by installing the required packages:"
+msgstr ""
+
+#: ../../installation.rst:336
+# d2538978382d4b47b1f84bc381b1009f
+msgid "Install on Ubuntu"
+msgstr ""
+
+#: ../../installation.rst:344
+# 47bc07e11dac4257b9ce54f511342915
+msgid "There is a known bug in the 4.3.0 release. You need to install an additional package by hand:"
+msgstr ""
+
+#: ../../installation.rst:350
+# aef5f1918b994df1a0da2b55407ba85f
+msgid "This bug has been fixed in master and upcoming 4.4 release and will also be fixed in bug fix releases 4.3.x"
+msgstr ""
+
+#: ../../installation.rst:353
+# 7db6de4cc37d43b8acb33c19898ce6f8
+msgid "Downloading vhd-util"
+msgstr ""
+
+#: ../../installation.rst:355
+# 39d5d2480cea49508d2a2589ef174eca
+msgid "This procedure is required only for installations where XenServer is installed on the hypervisor hosts."
+msgstr ""
+
+#: ../../installation.rst:358
+# d212ae279e594ea4a9b82dde3342f509
+msgid "Before setting up the Management Server, download vhd-util from `vhd-util <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_."
+msgstr ""
+
+#: ../../installation.rst:361
+# d4c4d9a792ec46bbacc984b02fa8dd22
+msgid "If the Management Server is RHEL or CentOS, copy vhd-util to `/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver`"
+msgstr ""
+
+#: ../../installation.rst:364
+# dcbc45d4730e482291fc719820a2e074
+msgid "If the Management Server is Ubuntu, copy vhd-util to `/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver`"
+msgstr ""
+
+#: ../../installation.rst:369
+# 3d000babaab44343b6203aec8596c5e6
+msgid "Install the database server"
+msgstr ""
+
+#: ../../installation.rst:371
+# f88a65610c204fafb3a2491316300137
+msgid "The CloudStack management server uses a MySQL database server to store its data. When you are installing the management server on a single node, you can install the MySQL server locally. For an installation that has multiple management server nodes, we assume the MySQL database also runs on a separate node."
+msgstr ""
+
+#: ../../installation.rst:377
+# fde5a5bd27424be7b529dc9a04291fc4
+msgid "CloudStack has been tested with MySQL 5.1 and 5.5. These versions are included in RHEL/CentOS and Ubuntu."
+msgstr ""
+
+#: ../../installation.rst:382
+# bdd992ca70fe4dff8367622ecd75f731
+msgid "Install the Database on the Management Server Node"
+msgstr ""
+
+#: ../../installation.rst:384
+# 7f0fe4eec48240e28d602ad0745156b6
+msgid "This section describes how to install MySQL on the same machine with the Management Server. This technique is intended for a simple deployment that has a single Management Server node. If you have a multi-node Management Server deployment, you will typically use a separate node for MySQL. See :ref:`install-database-on-separate-node`."
+msgstr ""
+
+#: ../../installation.rst:390
+# 9da9fd0e78644a6f90cc13c5f7629147
+msgid "Install MySQL from the package repository of your distribution:"
+msgstr ""
+
+#: ../../installation.rst:400
+# 423988f38bfe4c029c64f905b8083873
+msgid "Open the MySQL configuration file. The configuration file is ``/etc/my.cnf`` or ``/etc/mysql/my.cnf``, depending on your OS."
+msgstr ""
+
+#: ../../installation.rst:403
+# 69b009a70f9d489d86c665723f326565
+msgid "Insert the following lines in the [mysqld] section."
+msgstr ""
+
+#: ../../installation.rst:405
+# 7c240032679b427986b382f408c4d867
+msgid "You can put these lines below the datadir line. The max\\_connections parameter should be set to 350 multiplied by the number of Management Servers you are deploying. This example assumes one Management Server."
+msgstr ""
+
+#: ../../installation.rst:411
+# 462e4aec3ff248dfa67155a3766e4759
+msgid "On Ubuntu, you can also create a file `/etc/mysql/conf.d/cloudstack.cnf` and add these directives there. Don't forget to add [mysqld] on the first line of the file."
+msgstr ""
+
+#: ../../installation.rst:423
+#: ../../installation.rst:617
+# 64fd4122c8bd4334bb74dcb6e90272b9
+# 84765c6978a447f7b510dc7a3e4444bb
+msgid "Start or restart MySQL to put the new configuration into effect."
+msgstr ""
+
+#: ../../installation.rst:425
+#: ../../installation.rst:619
+# 724040c0968d4dff95c8d7be03f4017e
+# 8c620289a7ff44589e7c44bc264acaf1
+msgid "On RHEL/CentOS, MySQL doesn't automatically start after installation. Start it manually."
+msgstr ""
+
+#: ../../installation.rst:432
+#: ../../installation.rst:626
+# caa5b484b77844f0bd0826937ee49bc6
+# 6a9edbbfcf6d4c12a0b49cfb8a7417a2
+msgid "On Ubuntu, restart MySQL."
+msgstr ""
+
+#: ../../installation.rst:438
+#: ../../installation.rst:632
+# f61c8b0000f1424c9f2c13630125db20
+# 81d86aeab96741c4854e00bd76a9d650
+msgid "(CentOS and RHEL only; not required on Ubuntu)"
+msgstr ""
+
+#: ../../installation.rst:441
+# 49d05484300842749affe75f5a57fc78
+msgid "On RHEL and CentOS, MySQL does not set a root password by default. It is very strongly recommended that you set a root password as a security precaution."
+msgstr ""
+
+#: ../../installation.rst:445
+# 35126d196cb44db896a7da2f35f0219c
+msgid "Run the following command to secure your installation. You can answer \"Y\" to all questions."
+msgstr ""
+
+#: ../../installation.rst:452
+# 4c6efd3f31564d4e8c184fa2b19e2370
+msgid "CloudStack can be blocked by security mechanisms, such as SELinux. Disable SELinux to ensure + that the Agent has all the required permissions."
+msgstr ""
+
+#: ../../installation.rst:456
+# c736e2910bf746f29b59b481a266efd5
+msgid "Configure SELinux (RHEL and CentOS):"
+msgstr ""
+
+#: ../../installation.rst:458
+# 8d44b0228538457fb684938443b8a184
+msgid "Check whether SELinux is installed on your machine. If not, you can skip this section."
+msgstr ""
+
+#: ../../installation.rst:461
+# f4dda09e82f14c94b0380640a6a92eaa
+msgid "In RHEL or CentOS, SELinux is installed and enabled by default. You can verify this with:"
+msgstr ""
+
+#: ../../installation.rst:468
+# c9420ac318f6432fb6feb232be65d8cc
+msgid "Set the SELINUX variable in ``/etc/selinux/config`` to \"permissive\". This ensures that the permissive setting will be maintained after a system reboot."
+msgstr ""
+
+#: ../../installation.rst:472
+# 7bf236cb6e324d0b8b23ca6a50acfcdd
+msgid "In RHEL or CentOS:"
+msgstr ""
+
+#: ../../installation.rst:478
+# fe3458a445a247c18078c567d5c3c24c
+msgid "Change the following line"
+msgstr ""
+
+#: ../../installation.rst:484
+# af316e719579454392ce08b885fa3f1c
+msgid "to this:"
+msgstr ""
+
+#: ../../installation.rst:490
+# 348280635d374eeabd020521c3079beb
+msgid "Set SELinux to permissive starting immediately, without requiring a system reboot."
+msgstr ""
+
+#: ../../installation.rst:497
+# 65a33b90a9fc4a7b95bbf4db213365cb
+msgid "Set up the database. The following command creates the \"cloud\" user on the database."
+msgstr ""
+
+#: ../../installation.rst:500
+# aa653b538c1649a4ab4c8182d62d2ae4
+msgid "In dbpassword, specify the password to be assigned to the \"cloud\" user. You can choose to provide no password although that is not recommended."
+msgstr ""
+
+#: ../../installation.rst:504
+# 0fff4e85bcaa43d7a53ddf5f641899a8
+msgid "In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the \"cloud\" user."
+msgstr ""
+
+#: ../../installation.rst:509
+#: ../../installation.rst:683
+# 6e76a4c5d00b40f9a2591a882b9cf7e3
+# 232603c49f9b470fadd4497980b040ea
+msgid "(Optional) For encryption\\_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file. See :ref:`about-password-key-encryption`."
+msgstr ""
+
+#: ../../installation.rst:513
+# c484241ea1734f64b2ee605c25ff4f55
+msgid "(Optional) For management\\_server\\_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See :ref:`about-password-key-encryption`."
+msgstr ""
+
+#: ../../installation.rst:519
+#: ../../installation.rst:693
+# a116bdc1b4f146618c07383056276b2f
+# c84567a232924a2a93426fbde5c68e5c
+msgid "(Optional) For database\\_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value. See :ref:`about-password-key-encryption`."
+msgstr ""
+
+#: ../../installation.rst:525
+#: ../../installation.rst:699
+# d51435b1acbb403ea778782c88c09cd9
+# 3c2f5d31ed014299b6b2ad61d8d02606
+msgid "(Optional) For management\\_server\\_ip, you may explicitly specify cluster management server node IP. If not specified, the local IP address will be used."
+msgstr ""
+
+#: ../../installation.rst:538
+#: ../../installation.rst:712
+# 8781d85265da4df69b6b1161f9981921
+# f3bfbf8b741844379f95923b4b686ba8
+msgid "When this script is finished, you should see a message like “Successfully initialized the database.”"
+msgstr ""
+
+#: ../../installation.rst:542
+# a6cf1c3f7291407581e5da12486d3a20
+msgid "If the script is unable to connect to the MySQL database, check the \"localhost\" loopback address in ``/etc/hosts``. It should be pointing to the IPv4 loopback address \"127.0.0.1\" and not the IPv6 loopback address ``::1``. Alternatively, reconfigure MySQL to bind to the IPv6 loopback interface."
+msgstr ""
+
+#: ../../installation.rst:548
+# 33b221f992cd42cab21181c9205890e7
+msgid "If you are running the KVM hypervisor on the same machine with the Management Server, edit /etc/sudoers and add the following line:"
+msgstr ""
+
+#: ../../installation.rst:555
+# 52aa8c1267b94037ad3d9615231fbca4
+msgid "Now that the database is set up, you can finish configuring the OS for the Management Server. This command will set up iptables, sudoers, and start the Management Server."
+msgstr ""
+
+#: ../../installation.rst:563
+# 08f36fb116e642ba89ca4e2d95dec848
+msgid "You should see the message “CloudStack Management Server setup is done.”"
+msgstr ""
+
+#: ../../installation.rst:570
+# 7d221b73028543c9a2b47b117237997f
+msgid "Install the Database on a Separate Node"
+msgstr ""
+
+#: ../../installation.rst:572
+# eb04195ea5644ab59b8df4dcd32f8d0b
+msgid "This section describes how to install MySQL on a standalone machine, separate from the Management Server. This technique is intended for a deployment that includes several Management Server nodes. If you have a single-node Management Server deployment, you will typically use the same node for MySQL. See `“Install the Database on the Management Server Node” <#install-the-database-on-the-management-server-node>`_."
+msgstr ""
+
+#: ../../installation.rst:580
+# cb57860521b44243b4452bd9da079744
+msgid "The management server doesn't require a specific distribution for the MySQL node. You can use a distribution or Operating System of your choice. Using the same distribution as the management server is recommended, but not required. See `“Management Server, Database, and Storage System Requirements” <#management-server-database-and-storage-system-requirements>`_."
+msgstr ""
+
+#: ../../installation.rst:586
+# 49b51b3e92d447188645fdf39e28feab
+msgid "Install MySQL from the package repository from your distribution:"
+msgstr ""
+
+#: ../../installation.rst:596
+# ae7d0f661888443dbeda2f242e3e4bc3
+msgid "Edit the MySQL configuration (/etc/my.cnf or /etc/mysql/my.cnf, depending on your OS) and insert the following lines in the [mysqld] section. You can put these lines below the datadir line. The max\\_connections parameter should be set to 350 multiplied by the number of Management Servers you are deploying. This example assumes two Management Servers."
+msgstr ""
+
+#: ../../installation.rst:604
+# ea07aaf2f2094827919c3f7f9d1c8115
+msgid "On Ubuntu, you can also create /etc/mysql/conf.d/cloudstack.cnf file and add these directives there. Don't forget to add [mysqld] on the first line of the file."
+msgstr ""
+
+#: ../../installation.rst:635
+# 181c50670cde4667bbbf5930fb3c854b
+msgid "On RHEL and CentOS, MySQL does not set a root password by default. It is very strongly recommended that you set a root password as a security precaution. Run the following command to secure your installation. You can answer \"Y\" to all questions except \"Disallow root login remotely?\". Remote root login is required to set up the databases."
+msgstr ""
+
+#: ../../installation.rst:645
+# 278c2f9ed64442a580cb6c385b7793d6
+msgid "If a firewall is present on the system, open TCP port 3306 so external MySQL connections can be established."
+msgstr ""
+
+#: ../../installation.rst:648
+# 16ce3ea613174067b6edf85fa82a0323
+msgid "On Ubuntu, UFW is the default firewall. Open the port with this command:"
+msgstr ""
+
+#: ../../installation.rst:655
+# 11cda3fbfc934a199874ab207473898e
+msgid "On RHEL/CentOS:"
+msgstr ""
+
+#: ../../installation.rst:657
+# f0b20f4dbb6849c0963c4affbbba6ae9
+msgid "Edit the /etc/sysconfig/iptables file and add the following line at the beginning of the INPUT chain."
+msgstr ""
+
+#: ../../installation.rst:664
+# 0bf0dca831b0441fa3a376a3bcccfb78
+msgid "Now reload the iptables rules."
+msgstr ""
+
+#: ../../installation.rst:670
+# 6513db9f42b8495ca96090e285daa673
+msgid "Return to the root shell on your first Management Server."
+msgstr ""
+
+#: ../../installation.rst:672
+# a2317a3c06f342058c12a67eb8b69383
+msgid "Set up the database. The following command creates the cloud user on the database."
+msgstr ""
+
+#: ../../installation.rst:675
+# 5430f655d0e244fe8921c41ed892882f
+msgid "In dbpassword, specify the password to be assigned to the cloud user. You can choose to provide no password."
+msgstr ""
+
+#: ../../installation.rst:678
+# b10e601516ba4ba8ad5cf0a277d811e2
+msgid "In deploy-as, specify the username and password of the user deploying the database. In the following command, it is assumed the root user is deploying the database and creating the cloud user."
+msgstr ""
+
+#: ../../installation.rst:687
+# 9e82de1fc39e465b8b0b66c224c19483
+msgid "(Optional) For management\\_server\\_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack properties file. Default: password. It is highly recommended that you replace this with a more secure value. See About Password and Key Encryption."
+msgstr ""
+
+#: ../../installation.rst:719
+# 13de6a8d8fe341028c60b6f04beb31b0
+msgid "About Password and Key Encryption"
+msgstr ""
+
+#: ../../installation.rst:721
+# 45fbacb318674ad8b9217f0ca90da414
+msgid "CloudStack stores several sensitive passwords and secret keys that are used to provide security. These values are always automatically encrypted:"
+msgstr ""
+
+#: ../../installation.rst:725
+# 6ad55d0faad740589f3152b45a9670d1
+msgid "Database secret key"
+msgstr ""
+
+#: ../../installation.rst:727
+# e25d10cf49454d89a0301335e4aa2c93
+msgid "Database password"
+msgstr ""
+
+#: ../../installation.rst:729
+# c73f9cf443a745509d548cecae66c1fd
+msgid "SSH keys"
+msgstr ""
+
+#: ../../installation.rst:731
+# d042f272678f4ca3a91d02bf058c6ffc
+msgid "Compute node root password"
+msgstr ""
+
+#: ../../installation.rst:733
+# d70e7fde8c6e4353a2e5a31b6b15a0ff
+msgid "VPN password"
+msgstr ""
+
+#: ../../installation.rst:735
+# a91d0ab04c504168a4f86e9e1cd8f588
+msgid "User API secret key"
+msgstr ""
+
+#: ../../installation.rst:737
+# 7c756f6f0e374ae9a1d2b96c1de9c2a0
+msgid "VNC password"
+msgstr ""
+
+#: ../../installation.rst:739
+# 3ced5a13cc124b328c89685af71bddfc
+msgid "CloudStack uses the Java Simplified Encryption (JASYPT) library. The data values are encrypted and decrypted using a database secret key, which is stored in one of CloudStack’s internal properties files along with the database password. The other encrypted values listed above, such as SSH keys, are in the CloudStack internal database."
+msgstr ""
+
+#: ../../installation.rst:745
+# 024c2c3bfb28412392653a45cfe7debe
+msgid "Of course, the database secret key itself can not be stored in the open – it must be encrypted. How then does CloudStack read it? A second secret key must be provided from an external source during Management Server startup. This key can be provided in one of two ways: loaded from a file or provided by the CloudStack administrator. The CloudStack database has a configuration setting that lets it know which of these methods will be used. If the encryption type is set to \"file,\" the key must be in a file in a known location. If the encryption type is set to \"web,\" the administrator runs the utility com.cloud.utils.crypt.EncryptionSecretKeySender, which relays the key to the Management Server over a known port."
+msgstr ""
+
+#: ../../installation.rst:757
+# 6a3a9b0c66e04e64b4c6d34a4a17bb3b
+msgid "The encryption type, database secret key, and Management Server secret key are set during CloudStack installation. They are all parameters to the CloudStack database setup script (cloudstack-setup-databases). The default values are file, password, and password. It is, of course, highly recommended that you change these to more secure keys."
+msgstr ""
+
+#: ../../installation.rst:765
+# 511008e5d7e640eea756268a06c19eb0
+msgid "Changing the Default Password Encryption"
+msgstr ""
+
+#: ../../installation.rst:767
+# ca4f4a81740849cdb9d61f0a33af6605
+msgid "Passwords are encoded when creating or updating users. CloudStack allows you to determine the default encoding and authentication mechanism for admin and user logins. Two new configurable lists have been introduced—userPasswordEncoders and userAuthenticators. userPasswordEncoders allows you to configure the order of preference for encoding passwords, whereas userAuthenticators allows you to configure the order in which authentication schemes are invoked to validate user passwords."
+msgstr ""
+
+#: ../../installation.rst:776
+# 78d6cb8f6ce74a82accf0327cbc8375d
+msgid "Additionally, the plain text user authenticator has been modified not to convert supplied passwords to their md5 sums before checking them with the database entries. It performs a simple string comparison between retrieved and supplied login passwords instead of comparing the retrieved md5 hash of the stored password against the supplied md5 hash of the password because clients no longer hash the password. The following method determines what encoding scheme is used to encode the password supplied during user creation or modification."
+msgstr ""
+
+#: ../../installation.rst:785
+# f6b78ffccd494c30be0c5efac1ab44a9
+msgid "When a new user is created, the user password is encoded by using the first valid encoder loaded as per the sequence specified in the ``UserPasswordEncoders`` property in the ``ComponentContext.xml`` or ``nonossComponentContext.xml`` files. The order of authentication schemes is determined by the ``UserAuthenticators`` property in the same files. If Non-OSS components, such as VMware environments, are to be deployed, modify the ``UserPasswordEncoders`` and ``UserAuthenticators`` lists in the ``nonossComponentContext.xml`` file, for OSS environments, such as XenServer or KVM, modify the ``ComponentContext.xml`` file. It is recommended to make uniform changes across both the files. When a new authenticator or encoder is added, you can add them to this list. While doing so, ensure that the new authenticator or encoder is specified as a bean in both these files. The administrator can change the ordering of both these properties as preferred to change the order of schemes. Modify the following list properties available in ``client/tomcatconf/nonossComponentContext.xml.in`` or ``client/tomcatconf/componentContext.xml.in`` as applicable, to the desired order:"
+msgstr ""
+
+#: ../../installation.rst:823
+# 2fcac5693d444b38b51c1e5e74dc7110
+msgid "In the above default ordering, SHA256Salt is used first for ``UserPasswordEncoders``. If the module is found and encoding returns a valid value, the encoded password is stored in the user table's password column. If it fails for any reason, the MD5UserAuthenticator will be tried next, and the order continues. For ``UserAuthenticators``, SHA256Salt authentication is tried first. If it succeeds, the user is logged into the Management server. If it fails, md5 is tried next, and attempts continues until any of them succeeds and the user logs in . If none of them works, the user is returned an invalid credential message."
+msgstr ""
+
+#: ../../installation.rst:837
+# 707a625494ae450a987664e845dc1092
+msgid "CloudStack needs a place to keep primary and secondary storage (see Cloud Infrastructure Overview). Both of these can be NFS shares. This section tells how to set up the NFS shares before adding the storage to CloudStack."
+msgstr ""
+
+#: ../../installation.rst:843
+# 0ffaec4550964c9b81b5988488ee74fa
+msgid "NFS is not the only option for primary or secondary storage. For example, you may use Ceph RBD, GlusterFS, iSCSI, and others. The choice of storage system will depend on the choice of hypervisor and whether you are dealing with primary or secondary storage."
+msgstr ""
+
+#: ../../installation.rst:848
+# d636505b4eb949d49b6786e451926f86
+msgid "The requirements for primary and secondary storage are described in:"
+msgstr ""
+
+#: ../../installation.rst:850
+# 4d264009140f4e119313dbaaf55114a5
+msgid "`“About Primary Storage” <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-primary-storage>`_"
+msgstr ""
+
+#: ../../installation.rst:853
+# ed5e2e20e6ca432b95c1e7e204bd4f6a
+msgid "`“About Secondary Storage” <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-secondary-storage>`_"
+msgstr ""
+
+#: ../../installation.rst:856
+# 91c1900704fd4d91b018dd2e441ce1a5
+msgid "A production installation typically uses a separate NFS server. See :ref:`using-a-separage-nfs-server`."
+msgstr ""
+
+#: ../../installation.rst:859
+# 54dae30e742c45e0bab2066517190be8
+msgid "You can also use the Management Server node as the NFS server. This is more typical of a trial installation, but is technically possible in a larger deployment. See :ref:`using-the-management-server-as-the-nfs-server`."
+msgstr ""
+
+#: ../../installation.rst:867
+# feabaaeb53214becbece68200ee0ca7f
+msgid "Using a Separate NFS Server"
+msgstr ""
+
+#: ../../installation.rst:869
+# aeb8dd69baf144c4a1df1c6f07faaec9
+msgid "This section tells how to set up NFS shares for secondary and (optionally) primary storage on an NFS server running on a separate node from the Management Server."
+msgstr ""
+
+#: ../../installation.rst:873
+#: ../../installation.rst:934
+# f25edd950f514c5fb151e7877de7ab99
+# d24aef1ed1ac409589504fe7ef5cdb29
+msgid "The exact commands for the following steps may vary depending on your operating system version."
+msgstr ""
+
+#: ../../installation.rst:877
+# bff14968bd214c0c895eda46fc9c45ff
+msgid "(KVM only) Ensure that no volume is already mounted at your NFS mount point."
+msgstr ""
+
+#: ../../installation.rst:879
+# bd33e779304a4c5a81b690637431ef5b
+msgid "On the storage server, create an NFS share for secondary storage and, if you are using NFS for primary storage as well, create a second NFS share. For example:"
+msgstr ""
+
+#: ../../installation.rst:888
+#: ../../installation.rst:951
+# 0d4f698defbb458b8ffdb5ff3dd584e0
+# ce9561250f074471a254c55f6d07c6c9
+msgid "To configure the new directories as NFS exports, edit /etc/exports. Export the NFS share(s) with rw,async,no\\_root\\_squash,no\\_subtree\\_check. For example:"
+msgstr ""
+
+#: ../../installation.rst:896
+#: ../../installation.rst:959
+# 01cfe9dc640a44f6b99cb2c58b04c173
+# 98487e7ffdaf4dac9f71cb0719b6c684
+msgid "Insert the following line."
+msgstr ""
+
+#: ../../installation.rst:902
+#: ../../installation.rst:965
+# 94ecddfb2f174696aa885e7caf1c7f5f
+# 01225b1fb90847ec8b8b089ef57ef205
+msgid "Export the /export directory."
+msgstr ""
+
+#: ../../installation.rst:908
+# ecf40e05b66948e587495e8c9b46f371
+msgid "On the management server, create a mount point for secondary storage. For example:"
+msgstr ""
+
+#: ../../installation.rst:915
+# 95a0283dd26a46928e258568441e3d29
+msgid "Mount the secondary storage on your Management Server. Replace the example NFS server name and NFS share paths below with your own."
+msgstr ""
+
+#: ../../installation.rst:926
+# 98dfcbe6dbc44fc39d0d5c0f91a45503
+msgid "Using the Management Server as the NFS Server"
+msgstr ""
+
+#: ../../installation.rst:928
+# a4b1c2a1b2bd4729afc842b2675effa2
+msgid "This section tells how to set up NFS shares for primary and secondary storage on the same node with the Management Server. This is more typical of a trial installation, but is technically possible in a larger deployment. It is assumed that you will have less than 16TB of storage on the host."
+msgstr ""
+
+#: ../../installation.rst:937
+# 640cef0f4b154773ae29c9366515551d
+msgid "On RHEL/CentOS systems, you'll need to install the nfs-utils package:"
+msgstr ""
+
+#: ../../installation.rst:943
+# e152db6773384cfb9b5fa8d9849cd959
+msgid "On the Management Server host, create two directories that you will use for primary and secondary storage. For example:"
+msgstr ""
+
+#: ../../installation.rst:971
+# fad7bb568f4f4071b3685bb833739ef0
+msgid "Edit the /etc/sysconfig/nfs file."
+msgstr ""
+
+#: ../../installation.rst:977
+# 19d379a8922248c4bb8e975ab8238b30
+msgid "Uncomment the following lines:"
+msgstr ""
+
+#: ../../installation.rst:988
+# d39f9b7efd104412bb59b14b784ea816
+msgid "Edit the /etc/sysconfig/iptables file."
+msgstr ""
+
+#: ../../installation.rst:994
+# 0c25a4130a4f43aabbf389c386a783c5
+msgid "Add the following lines at the beginning of the INPUT chain, where <NETWORK> is the network that you'll be using:"
+msgstr ""
+
+#: ../../installation.rst:1011
+# 918152dcb1464ec3aa11d25e4df65ac0
+msgid "Run the following commands:"
+msgstr ""
+
+#: ../../installation.rst:1018
+# 8d7934cc7a674dc19677d0cca7b03f94
+msgid "If NFS v4 communication is used between client and server, add your domain to /etc/idmapd.conf on both the hypervisor host and Management Server."
+msgstr ""
+
+#: ../../installation.rst:1026
+# 553ce0f07b7b4689b7b85036357ca826
+msgid "Remove the character # from the beginning of the Domain line in idmapd.conf and replace the value in the file with your own domain. In the example below, the domain is company.com."
+msgstr ""
+
+#: ../../installation.rst:1034
+# 340dd6777da046a397391290dfe94ebb
+msgid "Reboot the Management Server host."
+msgstr ""
+
+#: ../../installation.rst:1036
+# 9b857a533abc42eea805251524f28b97
+msgid "Two NFS shares called /export/primary and /export/secondary are now set up."
+msgstr ""
+
+#: ../../installation.rst:1039
+# 0cf24cf59b9f4a5dbbdb2c51c7775ad5
+msgid "It is recommended that you test to be sure the previous steps have been successful."
+msgstr ""
+
+#: ../../installation.rst:1042
+# cbaa4d9e49e74255b3290e9820d55ef3
+msgid "Log in to the hypervisor host."
+msgstr ""
+
+#: ../../installation.rst:1044
+# 30e95a69d0a94a719e40f41b7a0bd06f
+msgid "Be sure NFS and rpcbind are running. The commands might be different depending on your OS. For example:"
+msgstr ""
+
+#: ../../installation.rst:1055
+# eef0133ebeee4897a60b1e510c32b865
+msgid "Log back in to the hypervisor host and try to mount the /export directories. For example, substitute your own management server name:"
+msgstr ""
+
+#: ../../installation.rst:1070
+# 945ffae66da941eea53781a93218bc1c
+msgid "Prepare and Start Additional Management Servers"
+msgstr ""
+
+#: ../../installation.rst:1072
+# d30a2d1b35064949905881c761a8c32f
+msgid "For your second and subsequent Management Servers, you will install the Management Server software, connect it to the database, and set up the OS for the Management Server."
+msgstr ""
+
+#: ../../installation.rst:1076
+# 386574bc8a1942f1a013e2260e7ec892
+msgid "Perform the steps in `“Prepare the Operating System” <#prepare-the-operating-system>`_ and `“Building RPMs from Source” <building_from_source.html#building-rpms-from-source>`_ or `“Building DEB packages” <building_from_source.html#building-deb-packages>`_ as appropriate."
+msgstr ""
+
+#: ../../installation.rst:1082
+# 9516fb7c54fc446ab76267a90611e209
+msgid "This step is required only for installations where XenServer is installed on the hypervisor hosts."
+msgstr ""
+
+#: ../../installation.rst:1085
+# 60bd480d13124c16b4c8774b8abd5439
+msgid "Download vhd-util from `vhd-util <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_"
+msgstr ""
+
+#: ../../installation.rst:1088
+# 3b0ff1adaf804ec4b60b43307747e306
+msgid "Copy vhd-util to /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver."
+msgstr ""
+
+#: ../../installation.rst:1091
+# 7a0ee162adde4c378073eeafb4a655f2
+msgid "Ensure that necessary services are started and set to start on boot."
+msgstr ""
+
+#: ../../installation.rst:1100
+# 24f30a5c2b9347fabde885434d2e78ed
+msgid "Configure the database client. Note the absence of the --deploy-as argument in this case. (For more details about the arguments to this command, see :ref:`install-database-on-separate-node`.)"
+msgstr ""
+
+#: ../../installation.rst:1108
+# 23d438dc604d4fd8a118a19e36271c4c
+msgid "Configure the OS and start the Management Server:"
+msgstr ""
+
+#: ../../installation.rst:1114
+# fdcd15f0de9849368878cc14f5725df2
+msgid "The Management Server on this node should now be running."
+msgstr ""
+
+#: ../../installation.rst:1116
+# 460f1039702f42858ad204d933e5758a
+msgid "Repeat these steps on each additional Management Server."
+msgstr ""
+
+#: ../../installation.rst:1118
+# c73ab983e4b14d3faa16deaaf4ab7520
+msgid "Be sure to configure a load balancer for the Management Servers. See `“Management Server Load Balancing” <http://docs.cloudstack.apache.org/en/latest/administration_guide.html?highlight=management%20server%20load#management-server-load-balancing>`_."
+msgstr ""
+
+#: ../../installation.rst:1126
+# 85b606d2b0044935b6e9fd3b1af045b3
+msgid "Secondary storage must be seeded with a template that is used for CloudStack system VMs."
+msgstr ""
+
+#: ../../installation.rst:1130
+# 4029e03b5ab24a4a88751a9c1a018ea2
+msgid "When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text."
+msgstr ""
+
+#: ../../installation.rst:1134
+# cbf94fb3cbf14df48bfb47c0dd21af6f
+msgid "On the Management Server, run one or more of the following cloud-install-sys-tmplt commands to retrieve and decompress the system VM template. Run the command for each hypervisor type that you expect end users to run in this Zone."
+msgstr ""
+
+#: ../../installation.rst:1139
+# e7bff9caa9f84e8c848d4d19b0daba94
+msgid "If your secondary storage mount point is not named /mnt/secondary, substitute your own mount point name."
+msgstr ""
+
+#: ../../installation.rst:1142
+# b4aef1ef071f4b71a00b3f645a1a228f
+msgid "If you set the CloudStack database encryption type to \"web\" when you set up the database, you must now add the parameter -s <management-server-secret-key>. See :ref:`about-password-key-encryption`."
+msgstr ""
+
+#: ../../installation.rst:1146
+# 5b51c5731c5740238035e396516eea52
+msgid "This process will require approximately 5 GB of free space on the local file system and up to 30 minutes each time it runs."
+msgstr ""
+
+#: ../../installation.rst:1149
+# fbc4137a3c07458cb016857d765e8e8b
+msgid "For Hyper-V"
+msgstr ""
+
+#: ../../installation.rst:1155
+# 42d30039e33e4a5c89d13a11b25f2545
+msgid "For XenServer:"
+msgstr ""
+
+#: ../../installation.rst:1161
+# 8a428eb947444e7f8a53951d031cfd23
+msgid "For vSphere:"
+msgstr ""
+
+#: ../../installation.rst:1167
+# 4ebe05af6f144d5b92d47b0a04c3669e
+msgid "For KVM:"
+msgstr ""
+
+#: ../../installation.rst:1173
+# 74cd4b53c2a04c45a2eec8761ae5ef2d
+msgid "For LXC:"
+msgstr ""
+
+#: ../../installation.rst:1179
+# 88ddfa6d01ea4de4a01489ecaa5809b1
+msgid "On Ubuntu, use the following path instead:"
+msgstr ""
+
+#: ../../installation.rst:1185
+# f288b19ac3584ac7a502423d40a8558c
+msgid "If you are using a separate NFS server, perform this step. If you are using the Management Server as the NFS server, you MUST NOT perform this step."
+msgstr ""
+
+#: ../../installation.rst:1189
+# 631bd8031bcf47d3a5e8dff1fd222d47
+msgid "When the script has finished, unmount secondary storage and remove the created directory."
+msgstr ""
+
+#: ../../installation.rst:1197
+# 3534852d9cc24d0dbc62b391e336cf0c
+msgid "Repeat these steps for each secondary storage server."
+msgstr ""
+
+#: ../../installation.rst:1201
+# a6cf95cb9f38452bbd3598d0c01df2cc
+msgid "Installation Complete! Next Steps"
+msgstr ""
+
+#: ../../installation.rst:1203
+# 6294cacb33fa4969b3bf3bc985881f83
+msgid "Congratulations! You have now installed CloudStack Management Server and the database it uses to persist system data."
+msgstr ""
+
+#: ../../installation.rst:1206
+# 482158ea55144603a694e07d25bb404b
+msgid "|installation-complete.png: Finished installs with single Management Server and multiple Management Servers|"
+msgstr ""
+
+#: ../../installation.rst:1209
+# bdf25769af294a0ea01aafc7a30ad5c1
+msgid "What should you do next?"
+msgstr ""
+
+#: ../../installation.rst:1211
+# e9e84870ee234e5f960460ac41635237
+msgid "Even without adding any cloud infrastructure, you can run the UI to get a feel for what's offered and how you will interact with CloudStack on an ongoing basis. See Log In to the UI."
+msgstr ""
+
+#: ../../installation.rst:1215
+# f1bed9af0dd54d0dbd297f8615f6d35e
+msgid "When you're ready, add the cloud infrastructure and try running some virtual machines on it, so you can watch how CloudStack manages the infrastructure. See Provision Your Cloud Infrastructure."
+msgstr ""
+
diff --git a/source/installguide/locale/pot/managing_networks.pot b/source/installguide/locale/pot/managing_networks.pot
new file mode 100644
index 0000000..d8ac813
--- /dev/null
+++ b/source/installguide/locale/pot/managing_networks.pot
@@ -0,0 +1,6769 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:02-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../managing_networks.rst:17
+# fc6be4b2a5ef4daab75e0149886b57ab
+msgid "Managing Networks and Traffic"
+msgstr ""
+
+#: ../../managing_networks.rst:19
+# e6e873bbde6b490a93904226a79e35e7
+msgid "In a CloudStack, guest VMs can communicate with each other using shared infrastructure with the security and user perception that the guests have a private LAN. The CloudStack virtual router is the main component providing networking features for guest traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:25
+# 158d9384502741139d4db7ad5d35f129
+msgid "Guest Traffic"
+msgstr ""
+
+#: ../../managing_networks.rst:27
+# 79038a2139e34806a98fb5dd5d6b1380
+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 ""
+
+#: ../../managing_networks.rst:32
+# 23f28e25661d4e449f0498521ff811f4
+msgid "See a typical guest traffic setup given below:"
+msgstr ""
+
+#: ../../managing_networks.rst:34
+# 3e47df0ab4fe4f7994d946a031909210
+msgid "|guest-traffic-setup.png: Depicts a guest traffic setup|"
+msgstr ""
+
+#: ../../managing_networks.rst:36
+# 4ddddc3fc73a4867a25fc49b035a99b7
+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 router. Its eth2 interface is assigned a public IP address for public traffic. If multiple public VLAN is used, the router will have multiple public interfaces."
+msgstr ""
+
+#: ../../managing_networks.rst:47
+# 32df6f633baa46de8a08df89b547bf68
+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 ""
+
+#: ../../managing_networks.rst:52
+# 037184db1823493ab1584e55b5275584
+msgid "Source NAT is automatically configured in the virtual router to forward outbound traffic for all guest VMs"
+msgstr ""
+
+#: ../../managing_networks.rst:56
+# d2daf1fae25745c0a829cd52009d5ac3
+msgid "Networking in a Pod"
+msgstr ""
+
+#: ../../managing_networks.rst:58
+# 3574c26b40ab456e8286506f92bca83c
+msgid "The figure below illustrates network setup within a single pod. The hosts are connected to a pod-level switch. At a minimum, the hosts should have one physical uplink to each switch. Bonded NICs are supported as well. The pod-level switch is a pair of redundant gigabit switches with 10 G uplinks."
+msgstr ""
+
+#: ../../managing_networks.rst:64
+# 35d1da6e0db343f2ae916ce0be527d56
+msgid "|networksinglepod.png: diagram showing logical view of network in a pod|"
+msgstr ""
+
+#: ../../managing_networks.rst:66
+# b7c71c1045954931b9d89bd5843e0306
+msgid "Servers are connected as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:70
+# 09e404c4512e44e59345fa1f14899f3d
+msgid "Storage devices are connected to only the network that carries management traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:75
+# a3a5ebaa022e413da0ffc6bdae7b6465
+msgid "Hosts are connected to networks for both management traffic and public traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:80
+# bd0d953a458e41eea4bf15edbfb12b2a
+msgid "Hosts are also connected to one or more networks carrying guest traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:83
+# 28c5e92ff62f49bba80dace0b3ae2fb0
+msgid "We recommend the use of multiple physical Ethernet cards to implement each network interface as well as redundant switch fabric in order to maximize throughput and improve reliability."
+msgstr ""
+
+#: ../../managing_networks.rst:88
+# d85d232eadb24f49a48d499c5adf81e7
+msgid "Networking in a Zone"
+msgstr ""
+
+#: ../../managing_networks.rst:90
+# 45168de567df49238a394803bce5aacc
+msgid "The following figure illustrates the network setup within a single zone."
+msgstr ""
+
+#: ../../managing_networks.rst:92
+# 29289f73fcf54224bc331c5454378f15
+msgid "|networksetupzone.png: Depicts network setup in a single zone|"
+msgstr ""
+
+#: ../../managing_networks.rst:94
+# df4e8223cc9c4409adf7cc8c71e7a98e
+msgid "A firewall for management traffic operates in the NAT mode. The network typically is assigned IP addresses in the 192.168.0.0/16 Class B private address space. Each pod is assigned IP addresses in the 192.168.\\*.0/24 Class C private address space."
+msgstr ""
+
+#: ../../managing_networks.rst:99
+# 9886368af88c424183304a4eb31ab641
+msgid "Each zone has its own set of public IP addresses. Public IP addresses from different zones do not overlap."
+msgstr ""
+
+#: ../../managing_networks.rst:103
+# e924366efd4241009758e8896b3e6669
+msgid "Basic Zone Physical Network Configuration"
+msgstr ""
+
+#: ../../managing_networks.rst:105
+# 99801fc2693a463386163a5ba924265b
+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 ""
+
+#: ../../managing_networks.rst:111
+# 4794c328db1440609a15296cef16b874
+msgid "Advanced Zone Physical Network Configuration"
+msgstr ""
+
+#: ../../managing_networks.rst:113
+# 627040abff364b5ea8314a3426b65674
+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 ""
+
+#: ../../managing_networks.rst:118
+# 7d82c9b8761a46dda119e356cf26d478
+msgid "Configure Guest Traffic in an Advanced Zone"
+msgstr ""
+
+#: ../../managing_networks.rst:120
+# 1744b57706544187ae3a8c396a505bf1
+msgid "These steps assume you have already logged in to the CloudStack UI. To configure the base guest network:"
+msgstr ""
+
+#: ../../managing_networks.rst:125
+# 5aecf3d836d747a884b554bca3fbb83d
+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 ""
+
+#: ../../managing_networks.rst:130
+#: ../../managing_networks.rst:214
+#: ../../managing_networks.rst:1585
+# 0cbb909f14cb492385ca0848aa144676
+# ae580367a0aa4a1186f4e67538afff94
+# af249bda556241b28af1cd321cc15602
+msgid "Click the Network tab."
+msgstr ""
+
+#: ../../managing_networks.rst:134
+#: ../../managing_networks.rst:218
+#: ../../managing_networks.rst:1589
+# 7c7e182828424070b9c41369469b65f0
+# 2e538d60fc224c08a46491e983daca7e
+# 44ba62fc316b4753a5d2655c5c666a98
+msgid "Click Add guest network."
+msgstr ""
+
+#: ../../managing_networks.rst:136
+# 15e6873aadaf411c83caf85f0a01dd5e
+msgid "The Add guest network window is displayed:"
+msgstr ""
+
+#: ../../managing_networks.rst:138
+# 0d02390e218c427e9a53bf85ca53de51
+msgid "|addguestnetwork.png: Add guest network setup in a single zone|"
+msgstr ""
+
+#: ../../managing_networks.rst:142
+#: ../../managing_networks.rst:4111
+#: ../../managing_networks.rst:4979
+# 0800e2f4123c4dd9a3cf88e6df107406
+# 9e8f926d35dd4062a29482a8ac99cbde
+# 30dd4c879c8f431d96a1941eb88e5443
+msgid "Provide the following information:"
+msgstr ""
+
+#: ../../managing_networks.rst:146
+# 7604500c996c439089ccdde1d7c025b4
+msgid "**Name**. The name of the network. This will be user-visible"
+msgstr ""
+
+#: ../../managing_networks.rst:150
+# 360746c957d54a70bd23064f9714bf87
+msgid "**Display Text**: The description of the network. This will be user-visible"
+msgstr ""
+
+#: ../../managing_networks.rst:155
+# 4c0edf7e62fb438f9f48989672721586
+msgid "**Zone**: The zone in which you are configuring the guest network."
+msgstr ""
+
+#: ../../managing_networks.rst:159
+# d0157a715ff0417e968114b1c345ed05
+msgid "**Network offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network"
+msgstr ""
+
+#: ../../managing_networks.rst:164
+# 8821fdb0e3e34d4eb2d879f89ef8265f
+msgid "**Guest Gateway**: The gateway that the guests should use"
+msgstr ""
+
+#: ../../managing_networks.rst:168
+# 4dc47880e5f541529ad13f5cf0ca522f
+msgid "**Guest Netmask**: The netmask in use on the subnet the guests will use"
+msgstr ""
+
+#: ../../managing_networks.rst:173
+#: ../../managing_networks.rst:870
+#: ../../managing_networks.rst:1242
+#: ../../managing_networks.rst:1419
+#: ../../managing_networks.rst:1742
+#: ../../managing_networks.rst:3064
+#: ../../managing_networks.rst:3578
+#: ../../managing_networks.rst:4209
+#: ../../managing_networks.rst:4245
+#: ../../managing_networks.rst:5015
+#: ../../managing_networks.rst:5106
+#: ../../managing_networks.rst:5352
+#: ../../managing_networks.rst:5394
+#: ../../managing_networks.rst:6843
+# 84368ab7e8384ed2ae5ecece5835bf18
+# 40ef14b296d343928f7b1af29927beba
+# fd54e59b59e34039ba86fdf384b32bb4
+# d595b9b3106b4a93b86dc8def713e6cf
+# 946c5d37563d43f98c6f39734828f252
+# 8969b38d8d954135bd6fd49ba48540a2
+# 96826bee1eba4ea1bbc5592ab0c19d71
+# b886d197d674421586d115da68f6e823
+# 8a1b58cd366c4d22a2a0ef021bf5439a
+# 8873118788c94bcc91cdcb0412e1f3a9
+# 067481ecae7e42a691ed616190af998f
+# 26e33f314996484ab84cff370047c483
+# 7d0cd95d267b472fb4b0dda772ffc2bc
+# 6ada6497acc04627b1750ff39f3e3b89
+msgid "Click OK."
+msgstr ""
+
+#: ../../managing_networks.rst:176
+# 92ed55846f3943a0899c3de25a023050
+msgid "Configure Public Traffic in an Advanced Zone"
+msgstr ""
+
+#: ../../managing_networks.rst:178
+# 915dafcef9e741c2a3aa241af4f416bf
+msgid "In a zone that uses advanced networking, you need to configure at least one range of IP addresses for Internet traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:182
+# 38eed1230b0548409982c02a9e02c83e
+msgid "Configuring a Shared Guest Network"
+msgstr ""
+
+#: ../../managing_networks.rst:186
+#: ../../managing_networks.rst:760
+#: ../../managing_networks.rst:1557
+# 029160365cb44beeabf86951b8cabbac
+# 5709f6a0aa4d4e87afbf1cd833e9b2f3
+# 390b3883b39c4ad585199248f00069c2
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../managing_networks.rst:190
+#: ../../managing_networks.rst:1354
+#: ../../managing_networks.rst:1561
+# 6b9a0641eccf4c888cb21525be4ed4c4
+# 25eb0f7c27f44e2983c3f49702a6d79b
+# 10241f1af1c84aa7a72d15d48b14b3e9
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../managing_networks.rst:194
+#: ../../managing_networks.rst:1565
+# 72ac0f8a684a418aa1a522b990724f3c
+# fcdd5db0bcf7487fb69abb38b182c87c
+msgid "On Zones, click View More."
+msgstr ""
+
+#: ../../managing_networks.rst:198
+#: ../../managing_networks.rst:1569
+# 15ee52a81be94e849e9aebbffd80f86e
+# 572f3b0de37d4cde8ee922ca57357102
+msgid "Click the zone to which you want to add a guest network."
+msgstr ""
+
+#: ../../managing_networks.rst:202
+#: ../../managing_networks.rst:776
+#: ../../managing_networks.rst:898
+#: ../../managing_networks.rst:1573
+# c8621ca1f0014cab8a2df11d16b6e23b
+# b0ac7488089d4de49ab63d4714a358d1
+# 67983bfccffe4126b74f01d74445a757
+# c54cc238e91a40e88ebec6ac9a67c3b9
+msgid "Click the Physical Network tab."
+msgstr ""
+
+#: ../../managing_networks.rst:206
+#: ../../managing_networks.rst:1577
+# 819adbe3002443ac81418804a6524958
+# 4f1ac1f461d24c96aac89732394faeb4
+msgid "Click the physical network you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:210
+#: ../../managing_networks.rst:1581
+# bf5520949d574c33956b419b623300af
+# a5e3c030c17040fd843946f7acd71beb
+msgid "On the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../managing_networks.rst:220
+#: ../../managing_networks.rst:1591
+# 3a1c06a1806443829aced440705c6ebb
+# 035fafb19b594767b275df96c08bffd8
+msgid "The Add guest network window is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:224
+#: ../../managing_networks.rst:806
+#: ../../managing_networks.rst:822
+#: ../../managing_networks.rst:856
+#: ../../managing_networks.rst:916
+#: ../../managing_networks.rst:1218
+#: ../../managing_networks.rst:1391
+#: ../../managing_networks.rst:1595
+#: ../../managing_networks.rst:3095
+#: ../../managing_networks.rst:5061
+#: ../../managing_networks.rst:5485
+#: ../../managing_networks.rst:6237
+#: ../../managing_networks.rst:6629
+# 2f740f3f23ab48a29ae3adbaf94c9a76
+# 342b53e57638424dbd3fc25b5de444cc
+# 81cc7e7f5132410a85166b44099c4efd
+# 433cd273bd454f109daafe4144bedce4
+# fbc94c5a87b34f69a0b7ccd2ec2961b8
+# 49a60cbb39104498a256acb82fa540bc
+# d93b5e9a682247d09575b8fed78e8419
+# 17f3af10510b469ab4fa599fdeca5e84
+# 147594fd9398446a9bffe7aa89aa42ae
+# 9d0d76a77389406aa54c77270247fb68
+# 0d313bd3accd40bba047ccbf1b35d224
+# 3daf7170c2984410906999b0b0fa4f3c
+# 2240e232e86f4b3ca8ab2960be6c573b
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:228
+#: ../../managing_networks.rst:1599
+# 14a5b53bcd874033a8eaa789e7c562d1
+# 2f405f166fd04a0bacf050bb1f4f4250
+msgid "**Name**: The name of the network. This will be visible to the user."
+msgstr ""
+
+#: ../../managing_networks.rst:233
+#: ../../managing_networks.rst:1604
+# 0f8d2c8170fd4b98bf717c87aef34378
+# 7585c82a0ece4f368233e94f9d3dfa64
+msgid "**Description**: The short description of the network that can be displayed to users."
+msgstr ""
+
+#: ../../managing_networks.rst:238
+#: ../../managing_networks.rst:1609
+# 99429451759a40f7ba18b278914e39f0
+# 88da596b302847b090b03d4973e86bfd
+msgid "**VLAN ID**: The unique ID of the VLAN."
+msgstr ""
+
+#: ../../managing_networks.rst:242
+# 00c2912dbf2443aa9b3241c8c5676742
+msgid "**Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr ""
+
+#: ../../managing_networks.rst:247
+#: ../../managing_networks.rst:1621
+# 6d2136a01445425e94f1ff5205af5c28
+# f35050303cac4011bb97763f32382baf
+msgid "**Scope**: The available scopes are Domain, Account, Project, and All."
+msgstr ""
+
+#: ../../managing_networks.rst:252
+#: ../../managing_networks.rst:1626
+# fe3608c2f3b3416aa62072104aa0fa8e
+# 21c43e42d8d34b4c97f8065f32bdae9e
+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 ""
+
+#: ../../managing_networks.rst:260
+#: ../../managing_networks.rst:1634
+# 5703f6a9a2db4216aca3b448df168a2a
+# a98df446d79849acbcf910ae486f9f24
+msgid "**Account**: The account for which the guest network is being created for. You must specify the domain the account belongs to."
+msgstr ""
+
+#: ../../managing_networks.rst:266
+#: ../../managing_networks.rst:1640
+# a1006b86f9414bee862542a9fe33ea89
+# 7431a628570b4f8f941f22c0dbca0d10
+msgid "**Project**: The project for which the guest network is being created for. You must specify the domain the project belongs to."
+msgstr ""
+
+#: ../../managing_networks.rst:272
+#: ../../managing_networks.rst:1646
+# 8b76a654149140adb4fb77dc2eaa7f03
+# 86babff897704393a7a47fac16fdb6da
+msgid "**All**: The guest network is available for all the domains, account, projects within the selected zone."
+msgstr ""
+
+#: ../../managing_networks.rst:277
+#: ../../managing_networks.rst:1651
+# abea434f07f34363afcd9c5acb702a37
+# 1367c8fe48974b6b8fcef96e9154b1f5
+msgid "**Network Offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network."
+msgstr ""
+
+#: ../../managing_networks.rst:283
+#: ../../managing_networks.rst:1657
+# 699e9d5856cb463885a05f687b080247
+# 433ee2c2a4084f46956487e77324431b
+msgid "**Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../managing_networks.rst:287
+#: ../../managing_networks.rst:1661
+# ce51526eaf0744f69498878264436b85
+# 45bbdda7a102498a9f476b2cdb175fd2
+msgid "**Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../managing_networks.rst:291
+#: ../../managing_networks.rst:1665
+# 6dbeaf06a3e14f82aa81cb65f66d29f5
+# 4eec9a4a29fa4d52a6b4337a8a50155c
+msgid "**IP Range**: A range of IP addresses that are accessible from the Internet and are assigned to the guest VMs."
+msgstr ""
+
+#: ../../managing_networks.rst:294
+# 6136c512a7fd43cf949e71c315564e8e
+msgid "If one NIC is used, these IPs should be in the same CIDR in the case of IPv6."
+msgstr ""
+
+#: ../../managing_networks.rst:299
+# 2049d251d6d24864be2401aae7d15eda
+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 ""
+
+#: ../../managing_networks.rst:306
+#: ../../managing_networks.rst:1670
+# 2eb61bdd6e2e4d0fb52eb0f2ab77e5c3
+# eb07ff88c573443cbf65bd9790a02d7e
+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 ""
+
+#: ../../managing_networks.rst:312
+#: ../../managing_networks.rst:1676
+#: ../../managing_networks.rst:3133
+#: ../../managing_networks.rst:3172
+#: ../../managing_networks.rst:4450
+# 01a5c1ddc4284bf7bb918c2924b99144
+# 29e37ee9c31a42b3b19bbd29b62699db
+# 5b8546575cc143e6aa6df3a739ec2dd4
+# c9c0a1842e2243cbbfbdd7bda9f8c173
+# 62ad85eee39c492e951ac8ef8cc0f1de
+msgid "Click OK to confirm."
+msgstr ""
+
+#: ../../managing_networks.rst:315
+# 0ba3f54aff874d7eb78409feb3e574cb
+msgid "Using Multiple Guest Networks"
+msgstr ""
+
+#: ../../managing_networks.rst:317
+# 9ee699c8fe6347568730b54b7737afe5
+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 ""
+
+#: ../../managing_networks.rst:322
+# cb2cfc8f5dd14b6a8d4c568329b1bc9e
+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 ""
+
+#: ../../managing_networks.rst:327
+# 044af5c71d054ac780d922e821f138a2
+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 ""
+
+#: ../../managing_networks.rst:333
+# 0adbfc444f2b4c1db5edbdd5b7d6bbea
+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 ""
+
+#: ../../managing_networks.rst:341
+# b7306772cd68452da7fcba1da1f76cb7
+msgid "Adding an Additional Guest Network"
+msgstr ""
+
+#: ../../managing_networks.rst:345
+#: ../../managing_networks.rst:412
+#: ../../managing_networks.rst:477
+#: ../../managing_networks.rst:508
+#: ../../managing_networks.rst:543
+#: ../../managing_networks.rst:686
+#: ../../managing_networks.rst:1196
+#: ../../managing_networks.rst:1249
+#: ../../managing_networks.rst:1350
+#: ../../managing_networks.rst:1722
+#: ../../managing_networks.rst:1799
+#: ../../managing_networks.rst:2157
+#: ../../managing_networks.rst:3200
+#: ../../managing_networks.rst:3243
+#: ../../managing_networks.rst:3286
+#: ../../managing_networks.rst:3362
+#: ../../managing_networks.rst:3464
+#: ../../managing_networks.rst:3611
+#: ../../managing_networks.rst:3743
+#: ../../managing_networks.rst:4095
+#: ../../managing_networks.rst:4219
+#: ../../managing_networks.rst:4252
+#: ../../managing_networks.rst:4349
+#: ../../managing_networks.rst:4542
+#: ../../managing_networks.rst:4963
+#: ../../managing_networks.rst:5028
+#: ../../managing_networks.rst:5156
+#: ../../managing_networks.rst:5238
+#: ../../managing_networks.rst:5406
+#: ../../managing_networks.rst:5643
+#: ../../managing_networks.rst:5735
+#: ../../managing_networks.rst:5823
+#: ../../managing_networks.rst:5913
+#: ../../managing_networks.rst:6155
+#: ../../managing_networks.rst:6463
+#: ../../managing_networks.rst:6547
+#: ../../managing_networks.rst:6672
+#: ../../managing_networks.rst:6711
+# bbfccf4187ee4d4fbf07e7f4bb88a635
+# 55b4e0f4a10d435781dc67f60c289bcc
+# 448e46420df84abe9fd5e0a98622bd8a
+# 7045e9260e2b41ac88aea79006e38ad5
+# c94a526c0dc04ebba1a701bb33b34bd3
+# 5878e84a00674d17980caa25c5845868
+# 21870457e3e743f78d2afa2427544010
+# c407b2aceffd487888c468b506ec84f2
+# be7946dbd37144e8a9a120d588d4ed8d
+# 57c820671f3e472e80e9758a6875049d
+# 7effce72473246f583a2c6706cf7ae8b
+# 10a47885bc344872bb68acaa38950c56
+# 0e16e2897c2541bdb9a9fe44c7c8c314
+# 69c641cc9e5745699a855b095a3f4234
+# 682913d951a64d7a9672b6c2d8ce61ec
+# b507fdb77c914103931f4382f7e94b6f
+# 69bf185d9530474e9d1e3ac4caccde82
+# 3a12fbb150d4405283cf759bdc0f579c
+# ce1e6561910a4f9b92872de6c4f0fe75
+# 8e6a2cd4f9da4a7da14bd4ff19517c5c
+# 0c0a9fa95a2c4c23affeb329bc18b9cd
+# ba5dc11cd6054bb0842bd0c996926273
+# 0383bb7ab57f403bb4dfdfd3cbe56bad
+# 0ce64e2cda5f451f939117bb581125bb
+# 2e7c7ca911564fd0b55e438fbf85b707
+# 724f938759144bca86466d021cded7cb
+# 3eb23b8ca60f439097e03d61faefe36b
+# a1e4d7e27f0a4bfd89398d6c8e268485
+# 4fdda4830b1d407b8baa1d170ccbd0f5
+# c1fe8cc9534f44f1825f02b028eda7ff
+# 1c6cfb5f62e947c8a05df1bdbca53570
+# 797717e559d24b03951f25f843042245
+# e1e46b9e3b67432eba081e3fa0b0b179
+# 7b6bd9d6ebe042aa817672a63cbdfa37
+# c7d9f6a38d724a9aa8a5caa76ed2d848
+# e6c130b9b73f4034b0e9d9c8a3aaa8dd
+# bdc2624551194b9eadb9cdfdf7403a02
+# c7ca24ebec074700a533736638fefcc0
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../managing_networks.rst:349
+#: ../../managing_networks.rst:553
+#: ../../managing_networks.rst:690
+#: ../../managing_networks.rst:1253
+#: ../../managing_networks.rst:2161
+#: ../../managing_networks.rst:3204
+#: ../../managing_networks.rst:3247
+#: ../../managing_networks.rst:3290
+#: ../../managing_networks.rst:3366
+#: ../../managing_networks.rst:3468
+#: ../../managing_networks.rst:4099
+#: ../../managing_networks.rst:4223
+#: ../../managing_networks.rst:4256
+#: ../../managing_networks.rst:4353
+#: ../../managing_networks.rst:4546
+#: ../../managing_networks.rst:4967
+#: ../../managing_networks.rst:5032
+#: ../../managing_networks.rst:5160
+#: ../../managing_networks.rst:5242
+#: ../../managing_networks.rst:5410
+#: ../../managing_networks.rst:5647
+#: ../../managing_networks.rst:5739
+#: ../../managing_networks.rst:5827
+#: ../../managing_networks.rst:5917
+#: ../../managing_networks.rst:6159
+#: ../../managing_networks.rst:6467
+#: ../../managing_networks.rst:6551
+#: ../../managing_networks.rst:6676
+#: ../../managing_networks.rst:6715
+# 542d2aed321d47bdabd1fca487ffd35e
+# e9aad32ba9934dfabf895d86886307b4
+# a64380da9ffa4f209568917d3e2f7ae6
+# f6467d352c5441f3aac59ff1a7e5751e
+# 489eb5a18ecf487089f92e974e4004b2
+# b77e8c3076474667a41f9c643cfb8921
+# 53f468b814a14dc7bc2846e0bb679713
+# b20083aec91a49e38ba1bd1bbd5ca432
+# cc62da2d87294fe59e75b03eab0b30de
+# 89a49e650a154374ac569bb05b88d91f
+# 230865dbd3c4443cb426bb570ee13485
+# 774f364202474a70b77a8561495b3245
+# 0ad7189c21294ef0b43aba32a8bafb7d
+# 726205f734c447d48af0ecd790bd238a
+# fdade5ad8a554d8897cc4e6c27dbc34e
+# 749f818fe9a349f9bb8cb7538cde74f8
+# b444a52f1dd14725bbd9f33966b9b508
+# bdcf2c42e7064f82ade52bd341621f2e
+# b1f4a91afafd4f6e84df0723ead48206
+# 541424f9e38a42d983bb27f87dcd3225
+# b5e9e12abba44624b3b74fc09e0f77fc
+# f392c162ed3241f09fc16f75065cd789
+# 2cd0df6af7ef4a7f9bad72059870b57b
+# e7d42493086e4c04a6545951d4c1ce5b
+# 3f34c206961e4a239714abc14d945f2c
+# d874094ea72f43988a5a4da919c3aae1
+# 0107854a76984dd18cc4256511f643fb
+# 399088fe7776424c8455730cb62a2f94
+# 9eaf23c1feb144f1b0cd1227b0b9ddd1
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../managing_networks.rst:353
+# ffe816f2fabe4d698bc426a2756acbe6
+msgid "Click Add guest network. Provide the following information:"
+msgstr ""
+
+#: ../../managing_networks.rst:357
+# e493749a1b58441b9f26c0ff3b13b9a7
+msgid "**Name**: The name of the network. This will be user-visible."
+msgstr ""
+
+#: ../../managing_networks.rst:361
+# e6573973726c48d1a6ddd47d98dfc7d4
+msgid "**Display Text**: The description of the network. This will be user-visible."
+msgstr ""
+
+#: ../../managing_networks.rst:366
+# 12ce0885bb7f4c36890123d1bdbd6b6d
+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 ""
+
+#: ../../managing_networks.rst:373
+# 6a5f82ef524445d184e3c139994c446f
+msgid "**Network offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network."
+msgstr ""
+
+#: ../../managing_networks.rst:379
+# d63cb3347919412cb5652d167f3198a0
+msgid "**Guest Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../managing_networks.rst:383
+# 1da6215b19f84083aeac888d2ef3bff1
+msgid "**Guest Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../managing_networks.rst:388
+#: ../../managing_networks.rst:3947
+# 4a768d89236c43fd9f2c33eab727c4e8
+# a127adae4308423cb1caf2db8966bdc4
+msgid "Click Create."
+msgstr ""
+
+#: ../../managing_networks.rst:391
+# 21b37eb5b7fe40bd99e0910a9f2bb75a
+msgid "Reconfiguring Networks in VMs"
+msgstr ""
+
+#: ../../managing_networks.rst:393
+# 476864eb3c9c4bccb394ef84b6e0c94b
+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 ""
+
+#: ../../managing_networks.rst:399
+# 9e97bafcd742424d921d811f3230a213
+msgid "This feature is supported on XenServer, VMware, and KVM hypervisors."
+msgstr ""
+
+#: ../../managing_networks.rst:402
+#: ../../managing_networks.rst:1517
+# f34aa270088a4613b0a44df4357afc8f
+# 8bd7a92ac32d4a2a929c8af17d3fb170
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../managing_networks.rst:404
+# 145ab5ecce044608b4b9656676c6cfc7
+msgid "Ensure that vm-tools are running on guest VMs for adding or removing networks to work on VMware hypervisor."
+msgstr ""
+
+#: ../../managing_networks.rst:408
+# 5a51c1312ebb4557a8603954294917c7
+msgid "Adding a Network"
+msgstr ""
+
+#: ../../managing_networks.rst:416
+#: ../../managing_networks.rst:481
+#: ../../managing_networks.rst:512
+# ecf6574c795f4768b731ef450b7ae607
+# 3b1c880a36ab4788a672d34d01ef6a4c
+# 49f1a64bc600489b90f669ff77ba9059
+msgid "In the left navigation, click Instances."
+msgstr ""
+
+#: ../../managing_networks.rst:420
+#: ../../managing_networks.rst:485
+#: ../../managing_networks.rst:516
+# 338fcbaeb8724ead9106c34112c862d9
+# bca3b4caf62d4663b33417eb7edaf223
+# f31277b33b9e4e2f9793e5a8ca4d7bb5
+msgid "Choose the VM that you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:424
+#: ../../managing_networks.rst:489
+#: ../../managing_networks.rst:520
+# 156d65dc581c4df498395e309bc7cbde
+# e5d8801dfa004ca1b93351677c983d89
+# 469dea7ab2094639b3d9a2299529fc07
+msgid "Click the NICs tab."
+msgstr ""
+
+#: ../../managing_networks.rst:428
+# 1bd7e90630f144b2b08248a827e64b0b
+msgid "Click Add network to VM."
+msgstr ""
+
+#: ../../managing_networks.rst:430
+# 049059a7b43d4efc989e4fcd813e6e1c
+msgid "The Add network to VM dialog is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:434
+# 5c99fc8205ef493dbab49c0599061a45
+msgid "In the drop-down list, select the network that you would like to add this VM to."
+msgstr ""
+
+#: ../../managing_networks.rst:437
+# 901988536d184641ac9d5ecaaee03ee2
+msgid "A new NIC is added for this network. You can view the following details in the NICs page:"
+msgstr ""
+
+#: ../../managing_networks.rst:442
+# 8d071d6df54845d6a56e7d96321dd7e8
+msgid "ID"
+msgstr ""
+
+#: ../../managing_networks.rst:446
+# ba92b68db3fc48ae810bd43616abc87a
+msgid "Network Name"
+msgstr ""
+
+#: ../../managing_networks.rst:450
+# eefe16e33001458591bb721f9e964a32
+msgid "Type"
+msgstr ""
+
+#: ../../managing_networks.rst:454
+#: ../../managing_networks.rst:4332
+#: ../../managing_networks.rst:4458
+# ce7e7d2354fc48ccb97e1c2917007397
+# 35a3d8a7cc444f7289fff5b3f02731e3
+# 906d6bce91f745de9cc8eb362260b17b
+msgid "IP Address"
+msgstr ""
+
+#: ../../managing_networks.rst:458
+#: ../../managing_networks.rst:4462
+# 07c404d90b444084935108a2905f8147
+# aa4cc5b288b14a26b34b3cd819e6be4e
+msgid "Gateway"
+msgstr ""
+
+#: ../../managing_networks.rst:462
+# da3675e2aed24eb681d8601910102496
+msgid "Netmask"
+msgstr ""
+
+#: ../../managing_networks.rst:466
+# 48374307b68a4eff88c1778ea7bd9380
+msgid "Is default"
+msgstr ""
+
+#: ../../managing_networks.rst:470
+# 2777d60a7bf14a35bd37af5f0ac55458
+msgid "CIDR (for IPv6)"
+msgstr ""
+
+#: ../../managing_networks.rst:473
+# 84f9d9b60c4e4ce4a509cad5b0900a5b
+msgid "Removing a Network"
+msgstr ""
+
+#: ../../managing_networks.rst:493
+# 707d137eb0aa4adaa497aff9a413ad06
+msgid "Locate the NIC you want to remove."
+msgstr ""
+
+#: ../../managing_networks.rst:497
+# c2a07f20886b47be83f065291dfee6fb
+msgid "Click Remove NIC button. |remove-nic.png: button to remove a NIC|"
+msgstr ""
+
+#: ../../managing_networks.rst:501
+#: ../../managing_networks.rst:533
+# b23abd4aac6242bdbc3f97acc2666a90
+# 8f8b04c7921a441ba8480683014b9864
+msgid "Click Yes to confirm."
+msgstr ""
+
+#: ../../managing_networks.rst:504
+# 4f9e35dc3f614384a7505c4161fffaac
+msgid "Selecting the Default Network"
+msgstr ""
+
+#: ../../managing_networks.rst:524
+# 40b332e2efca44c092058585a0004200
+msgid "Locate the NIC you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:528
+# 3d3dc6ede8e440efab9778ab27669811
+msgid "Click the Set default NIC button. |set-default-nic.png: button to set a NIC as default one.|"
+msgstr ""
+
+#: ../../managing_networks.rst:536
+# f0c74bc7df3d400bac208e03ca7e454d
+msgid "Changing the Network Offering on a Guest Network"
+msgstr ""
+
+#: ../../managing_networks.rst:538
+# bd0f96f469b24f7cb9efc0e11835fc56
+msgid "A user or administrator can change the network offering that is associated with an existing guest network."
+msgstr ""
+
+#: ../../managing_networks.rst:547
+# 746637ea703149eab979289dea055956
+msgid "If you are changing from a network offering that uses the CloudStack virtual router to one that uses external devices as network service providers, you must first stop all the VMs on the network."
+msgstr ""
+
+#: ../../managing_networks.rst:557
+#: ../../managing_networks.rst:694
+# b06f831436614c7799e92f02062dd02e
+# b2aef771f9cb4102849882e08921deda
+msgid "Click the name of the network you want to modify."
+msgstr ""
+
+#: ../../managing_networks.rst:561
+# 8fe0c8047dd941648bdb27d5c4d46d64
+msgid "In the Details tab, click Edit. |EditButton.png: button to edit a network|"
+msgstr ""
+
+#: ../../managing_networks.rst:566
+# 38ce91cfac534d3d8ce2d2be8ac4d9db
+msgid "In Network Offering, choose the new network offering, then click Apply."
+msgstr ""
+
+#: ../../managing_networks.rst:569
+# 0c9082cd84904f30a842d0296519899f
+msgid "A prompt is displayed asking whether you want to keep the existing CIDR. This is to let you know that if you change the network offering, the CIDR will be affected."
+msgstr ""
+
+#: ../../managing_networks.rst:573
+# 395368811c93495691bd4e308ae0bbc4
+msgid "If you upgrade between virtual router as a provider and an external network device as provider, acknowledge the change of CIDR to continue, so choose Yes."
+msgstr ""
+
+#: ../../managing_networks.rst:579
+# ee09bef0f4f84d41a949984dce97934e
+msgid "Wait for the update to complete. Don’t try to restart VMs until the network change is complete."
+msgstr ""
+
+#: ../../managing_networks.rst:584
+# 7c315c696ed54f5197595376cdd7d0c0
+msgid "If you stopped any VMs, restart them."
+msgstr ""
+
+#: ../../managing_networks.rst:587
+# 92b286db05494a3f9d6591a9f2ccfc6a
+msgid "IP Reservation in Isolated Guest Networks"
+msgstr ""
+
+#: ../../managing_networks.rst:589
+# 67ed578463354e849af5ed40418159aa
+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 ""
+
+#: ../../managing_networks.rst:597
+# d38381f1dad148afb7aeed5ee6e6db41
+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 called Reserved IP Range. When IP reservation is configured, the administrator can add additional VMs or physical servers that are not part of CloudStack to the same network and assign them the Reserved IP addresses. CloudStack guest VMs cannot acquire IPs from the Reserved IP Range."
+msgstr ""
+
+#: ../../managing_networks.rst:611
+# 3031b1a715ff422bad8de1f97adc2db7
+msgid "IP Reservation Considerations"
+msgstr ""
+
+#: ../../managing_networks.rst:613
+# c57c48d3a65e474c89a99952e65a6a40
+msgid "Consider the following before you reserve an IP range for non-CloudStack machines:"
+msgstr ""
+
+#: ../../managing_networks.rst:618
+# 05c140f272754cfb9d21597b9c778fc5
+msgid "IP Reservation is supported only in Isolated networks."
+msgstr ""
+
+#: ../../managing_networks.rst:622
+# f5211c450a014b0a8d335434d84aa391
+msgid "IP Reservation can be applied only when the network is in Implemented state."
+msgstr ""
+
+#: ../../managing_networks.rst:627
+# 6add1277df044450bce332b364de119b
+msgid "No IP Reservation is done by default."
+msgstr ""
+
+#: ../../managing_networks.rst:631
+# 0847da9c049c4c0da2a6eac963931b02
+msgid "Guest VM CIDR you specify must be a subset of the network CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:635
+# 36a9bbd09feb416ca7f9ccca3c54eefb
+msgid "Specify a valid Guest VM CIDR. IP Reservation is applied only if no active IPs exist outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:638
+# 191010bd30424f3aa12cf309a48dcfc4
+msgid "You cannot apply IP Reservation if any VM is alloted with an IP address that is outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:643
+# e4b8dc3735d4441ebf832418538d5833
+msgid "To reset an existing IP Reservation, apply IP reservation by specifying the value of network CIDR in the CIDR field."
+msgstr ""
+
+#: ../../managing_networks.rst:646
+# 8281e4ae0c6a4374b25bfef4f7e74405
+msgid "For example, the following table describes three scenarios of guest network creation:"
+msgstr ""
+
+#: ../../managing_networks.rst:650
+# 9f714ae7b5f346bc87da5182136d41e5
+msgid "Case"
+msgstr ""
+
+#: ../../managing_networks.rst:650
+#: ../../managing_networks.rst:3846
+#: ../../managing_networks.rst:4293
+#: ../../managing_networks.rst:4393
+#: ../../managing_networks.rst:4587
+#: ../../managing_networks.rst:5144
+#: ../../managing_networks.rst:5193
+#: ../../managing_networks.rst:5451
+#: ../../managing_networks.rst:5776
+#: ../../managing_networks.rst:5863
+#: ../../managing_networks.rst:5954
+#: ../../managing_networks.rst:6196
+#: ../../managing_networks.rst:6588
+# 43eb64da7dd14977948b1fd136c81c4f
+# ba69ebf50fa04e628494a63c71ee09be
+# 6e509570aefc4ed58372df0bae71f59e
+# e02ce26c53d447cab48c5987becb6178
+# 372de59b30db4b00a1a4a4503aecb29d
+# 0efc90dc789a42219e0e1821921c3a3b
+# 2f722e4bc54941bf9ac18e34ec89ea21
+# 0f4f84fccf1c4879a9ec6691a4abb447
+# 04c82a1485db4a52a0c4fae3e4018e41
+# 8788d910542844b09ae66506304063dc
+# e65e4e6cdcba4f138e43047ff9d3bed6
+# 23d809b6aa20458dacb898b0e8b4d1da
+# cd520efc8baa4344b57bd33b0fa5254d
+msgid "CIDR"
+msgstr ""
+
+#: ../../managing_networks.rst:650
+# 63125858003344c0b965da2ac922cf02
+msgid "Network CIDR"
+msgstr ""
+
+#: ../../managing_networks.rst:650
+# c3c99ba5184c4c9194605bb04a547f39
+msgid "Reserved IP Range for Non-CloudStack VMs"
+msgstr ""
+
+#: ../../managing_networks.rst:650
+# 0e5c1cae0f4d4f06851e27a50273b95c
+msgid "Description"
+msgstr ""
+
+#: ../../managing_networks.rst:652
+#: ../../managing_networks.rst:5146
+# 2e71a7acd08543168d74d2c0d03e0c39
+# d06565ec0d634d848669aa19d123d59a
+msgid "1"
+msgstr ""
+
+#: ../../managing_networks.rst:652
+#: ../../managing_networks.rst:653
+#: ../../managing_networks.rst:654
+# bd4f28e5c83943d8882e2012659415bf
+# 249137a9387145d0ac514e9000be76cd
+# d7c4b09246fb4bfeb5649c2cf6e23d30
+msgid "10.1.1.0/24"
+msgstr ""
+
+#: ../../managing_networks.rst:652
+#: ../../managing_networks.rst:652
+#: ../../managing_networks.rst:654
+#: ../../managing_networks.rst:654
+# 2f9cc88264fb4285bfa3149ea04b26a5
+# d74122c1ce754a1999acc721dfe12491
+# 3e1cad272521413bb73ebf025861f357
+# c9bd04abf9984e3d82a008b15823df6f
+msgid "None"
+msgstr ""
+
+#: ../../managing_networks.rst:652
+# 672d94082a534891849650884d4c25d0
+msgid "No IP Reservation."
+msgstr ""
+
+#: ../../managing_networks.rst:653
+#: ../../managing_networks.rst:5147
+# 7f31ca61138545d19f53bfea0156930f
+# f11cfcf719bc4813a691abc48eef0c50
+msgid "2"
+msgstr ""
+
+#: ../../managing_networks.rst:653
+# 8e804381dca64c3ab199583ca238a7e8
+msgid "10.1.1.0/26"
+msgstr ""
+
+#: ../../managing_networks.rst:653
+# 042cf084bef6418fa9d8ee1a00593e8a
+msgid "10.1.1.64 to 10.1.1.254"
+msgstr ""
+
+#: ../../managing_networks.rst:653
+# 2094d73c4b004d18b9b1c3be4ac72e10
+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 ""
+
+#: ../../managing_networks.rst:654
+# 769561dd7e454a58b571d069407bc84f
+msgid "3"
+msgstr ""
+
+#: ../../managing_networks.rst:654
+# 99819f9f881049da88cf236d227fbcce
+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 ""
+
+#: ../../managing_networks.rst:659
+# af64fa9a0d594bf6aba58e557fb64ef2
+msgid "Limitations"
+msgstr ""
+
+#: ../../managing_networks.rst:663
+# b133ecb14f0743c5aad172cbec921f69
+msgid "The IP Reservation is not supported if active IPs that are found outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:668
+# 9c8183bbe2aa4950a96b3f707269281c
+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 ""
+
+#: ../../managing_networks.rst:674
+# a6037f7354694b7fa3df7eab35ce68a3
+msgid "Best Practices"
+msgstr ""
+
+#: ../../managing_networks.rst:676
+# 1402bdfed0e642a5bc411cad728d629f
+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 ""
+
+#: ../../managing_networks.rst:682
+# 9d8b936d8d924b3e9610e79cea49d7ed
+msgid "Reserving an IP Range"
+msgstr ""
+
+#: ../../managing_networks.rst:698
+# 43313d5d032c4bc1ae00497086042bf1
+msgid "In the Details tab, click Edit. |edit-icon.png: button to edit a network|"
+msgstr ""
+
+#: ../../managing_networks.rst:701
+# 4b6443793ca64ed7b71e9dacebc772c6
+msgid "The CIDR field changes to editable one."
+msgstr ""
+
+#: ../../managing_networks.rst:705
+# 170900f4419c40d3ae77ba9cee3b6fff
+msgid "In CIDR, specify the Guest VM CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:709
+# 1fccea99506b441bba9fd6fbc76dd995
+msgid "Click Apply."
+msgstr ""
+
+#: ../../managing_networks.rst:711
+# c0734e33a8844d90aac6295573540aee
+msgid "Wait for the update to complete. The Network CIDR and the Reserved IP Range are displayed on the Details page."
+msgstr ""
+
+#: ../../managing_networks.rst:715
+# aad0613e9913469fb756198fc0170632
+msgid "Reserving Public IP Addresses and VLANs for Accounts"
+msgstr ""
+
+#: ../../managing_networks.rst:717
+# 6e44df38576d4f5e99903f26a9db1253
+msgid "CloudStack provides you the ability to reserve a set of public IP addresses and VLANs exclusively for an account. During zone creation, you can continue defining a set of VLANs and multiple public IP ranges. This feature extends the functionality to enable you to dedicate a fixed set of VLANs and guest IP addresses for a tenant."
+msgstr ""
+
+#: ../../managing_networks.rst:723
+# 8da4bb7270e845baa41435d7a8dc2897
+msgid "Note that if an account has consumed all the VLANs and IPs dedicated to it, the account can acquire two more resources from the system. CloudStack provides the root admin with two configuration parameter to modify this default behavior—use.system.public.ips and use.system.guest.vlans. These global parameters enable the root admin to disallow an account from acquiring public IPs and guest VLANs from the system, if the account has dedicated resources and these dedicated resources have all been consumed. Both these configurations are configurable at the account level."
+msgstr ""
+
+#: ../../managing_networks.rst:733
+# 37e6f49f8b53452a8036407ad381ea12
+msgid "This feature provides you the following capabilities:"
+msgstr ""
+
+#: ../../managing_networks.rst:737
+# 671086ca87b14ae28c39b69fd8046953
+msgid "Reserve a VLAN range and public IP address range from an Advanced zone and assign it to an account"
+msgstr ""
+
+#: ../../managing_networks.rst:742
+# 404fcaa9d1b848d2ab247cce5350c281
+msgid "Disassociate a VLAN and public IP address range from an account"
+msgstr ""
+
+#: ../../managing_networks.rst:746
+# bd85bcf3d9394066af54e1e703ae3cf7
+msgid "View the number of public IP addresses allocated to an account"
+msgstr ""
+
+#: ../../managing_networks.rst:750
+# 01799c3a9b364c51b97d539c849d3394
+msgid "Check whether the required range is available and is conforms to account limits."
+msgstr ""
+
+#: ../../managing_networks.rst:753
+# 7716c7ee6e9a4c68bacaaafbba51a78c
+msgid "The maximum IPs per account limit cannot be superseded."
+msgstr ""
+
+#: ../../managing_networks.rst:756
+# 8f2fa2619671428980abde283469e00d
+msgid "Dedicating IP Address Ranges to an Account"
+msgstr ""
+
+#: ../../managing_networks.rst:764
+#: ../../managing_networks.rst:886
+#: ../../managing_networks.rst:2974
+# d7a82a1208db4208961df5b2bda98eb3
+# 3ac411dc4da74e0689c3e931f08d5c59
+# c74ad6e9cbee4ff685cef4af6c1a1c8a
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../managing_networks.rst:768
+#: ../../managing_networks.rst:890
+# ad2d0d358fab46f69cc0e2834d1025b5
+# 06d4cbfaa106459eb58d6d9bb34a92a1
+msgid "In Zones, click View All."
+msgstr ""
+
+#: ../../managing_networks.rst:772
+#: ../../managing_networks.rst:894
+#: ../../managing_networks.rst:2982
+# 04e17439a9d04d8c92bace413127ce77
+# e40c006773b9414cbe8dd42bb69472d4
+# 03828d4d48bf4770bdc2328f34b55100
+msgid "Choose the zone you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:780
+# b2f55880ae154ea5a38880eeeb515690
+msgid "In the Public node of the diagram, click Configure."
+msgstr ""
+
+#: ../../managing_networks.rst:784
+# 790579c6465f4bf88b03caf31b04e907
+msgid "Click the IP Ranges tab."
+msgstr ""
+
+#: ../../managing_networks.rst:786
+# 9136b3e4ca934c23806bbc7ca0ff01e5
+msgid "You can either assign an existing IP range to an account, or create a new IP range and assign to an account."
+msgstr ""
+
+#: ../../managing_networks.rst:791
+# be977158780a4bfca4232fc7d2573dd7
+msgid "To assign an existing IP range to an account, perform the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:795
+# c85643e60bae4ce7a7341f72ed356343
+msgid "Locate the IP range you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:799
+# 8c760073c6e140c98957ae64117cd375
+msgid "Click Add Account |addAccount-icon.png: button to assign an IP range to an account.| button."
+msgstr ""
+
+#: ../../managing_networks.rst:802
+# 5907d0ab73b04589b7fba68c857ad361
+msgid "The Add Account dialog is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:810
+# d84f7b0e62b043939a4656f457f829e7
+msgid "**Account**: The account to which you want to assign the IP address range."
+msgstr ""
+
+#: ../../managing_networks.rst:815
+# 54ea232ef7544939989c85cf78823ab4
+msgid "**Domain**: The domain associated with the account."
+msgstr ""
+
+#: ../../managing_networks.rst:817
+# cac430d036924f38a9290dde3665c841
+msgid "To create a new IP range and assign an account, perform the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:826
+# d50191ed42ad44ee95f6167032a30c65
+msgid "**Gateway**"
+msgstr ""
+
+#: ../../managing_networks.rst:830
+# 13d287dfefa145e3bf443ca11ed78fa2
+msgid "**Netmask**"
+msgstr ""
+
+#: ../../managing_networks.rst:834
+# 2e49c1a58f4a4bfa87d30c1c449df1e3
+msgid "**VLAN**"
+msgstr ""
+
+#: ../../managing_networks.rst:838
+# 8ebc180647e6488db6d7419f0c96d969
+msgid "**Start IP**"
+msgstr ""
+
+#: ../../managing_networks.rst:842
+# 39bbcd6bce9c4acdb1dde4c134d36aee
+msgid "**End IP**"
+msgstr ""
+
+#: ../../managing_networks.rst:846
+# c9ff42e89acd482b839c78ede4bf72a2
+msgid "**Account**: Perform the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:850
+# 4e8c15e78f4040da8818c60242a385f7
+msgid "Click Account."
+msgstr ""
+
+#: ../../managing_networks.rst:852
+# 4d16eeb78e534a4aba7b7c05c335d94a
+msgid "The Add Account page is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:860
+# 4fcbdb024f3c4d0e916309194ccf9796
+msgid "****Account****: The account to which you want to assign an IP address range."
+msgstr ""
+
+#: ../../managing_networks.rst:865
+#: ../../managing_networks.rst:930
+# 5dd4ec70717a455cb3eae0f191b2c338
+# e1b99db893e94523a9c9c6c2dca5e50a
+msgid "****Domain****: The domain associated with the account."
+msgstr ""
+
+#: ../../managing_networks.rst:874
+#: ../../managing_networks.rst:1919
+#: ../../managing_networks.rst:3411
+#: ../../managing_networks.rst:3511
+#: ../../managing_networks.rst:3667
+#: ../../managing_networks.rst:3899
+#: ../../managing_networks.rst:5623
+# 222bcd68057f4097804636cc658bae40
+# 583b09f47740445cae14b167a426c0d5
+# d8184c325cbe4e2989e1772dd91acd0b
+# b8bdf6dd077f48bab5be9a342447e9d8
+# 221e41362cdb48c1b692cef19b0a8218
+# f241bee872c34bcfa7d43b4601e1cb48
+# 95df29e50c984e798847dc985a455395
+msgid "Click Add."
+msgstr ""
+
+#: ../../managing_networks.rst:877
+# 6f5ed4ecaf104ec089964163e1e6884f
+msgid "Dedicating VLAN Ranges to an Account"
+msgstr ""
+
+#: ../../managing_networks.rst:881
+# 1d96f022bb0641f591f869dcdef945de
+msgid "After the CloudStack Management Server is installed, log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../managing_networks.rst:902
+#: ../../managing_networks.rst:1367
+# b7387ff7ac314fabb59c5c8adb95d64c
+# 09557ffae33041df84505184339ead4d
+msgid "In the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../managing_networks.rst:906
+# fcf27305c8cf42bcaea54b6e0d583e74
+msgid "Select the Dedicated VLAN Ranges tab."
+msgstr ""
+
+#: ../../managing_networks.rst:910
+# 67395673dcac45fd95c09509e40ab195
+msgid "Click Dedicate VLAN Range."
+msgstr ""
+
+#: ../../managing_networks.rst:912
+# ab0efa84cce7484aa1483aa86e7458e3
+msgid "The Dedicate VLAN Range dialog is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:920
+# 79112ed3b43d4ac9b8ffd92e5be692f1
+msgid "****VLAN Range****: The VLAN range that you want to assign to an account."
+msgstr ""
+
+#: ../../managing_networks.rst:925
+# a99491d184b347ae9692f3140f8507e1
+msgid "****Account****: The account to which you want to assign the selected VLAN range."
+msgstr ""
+
+#: ../../managing_networks.rst:933
+# fcc09f716f8d4237b77cc161171a4261
+msgid "Configuring Multiple IP Addresses on a Single NIC"
+msgstr ""
+
+#: ../../managing_networks.rst:935
+# a94a3710f1234c97836f59a5a07db667
+msgid "CloudStack provides you the ability to associate multiple private IP addresses per guest VM NIC. In addition to the primary IP, you can assign additional IPs to the guest VM NIC. This feature is supported on all the network configurations—Basic, Advanced, and VPC. Security Groups, Static NAT and Port forwarding services are supported on these additional IPs."
+msgstr ""
+
+#: ../../managing_networks.rst:942
+# 494be8c0259840fb84fb26e96d13a908
+msgid "As always, you can specify an IP from the guest subnet; if not specified, an IP is automatically picked up from the guest VM subnet. You can view the IPs associated with for each guest VM NICs on the UI. You can apply NAT on these additional guest IPs by using network configuration option in the CloudStack UI. You must specify the NIC to which the IP should be associated."
+msgstr ""
+
+#: ../../managing_networks.rst:949
+# 925a5eb75fe04c35bfd19b1ac2f44b7e
+msgid "This feature is supported on XenServer, KVM, and VMware hypervisors. Note that Basic zone security groups are not supported on VMware."
+msgstr ""
+
+#: ../../managing_networks.rst:953
+# 5ac573ae5f4345aeb143a5fcc101524d
+msgid "Use Cases"
+msgstr ""
+
+#: ../../managing_networks.rst:955
+# 872874841bbe414a88684eb2a0045657
+msgid "Some of the use cases are described below:"
+msgstr ""
+
+#: ../../managing_networks.rst:959
+# d5c27060797b4aee9174ebb56ffef918
+msgid "Network devices, such as firewalls and load balancers, generally work best when they have access to multiple IP addresses on the network interface."
+msgstr ""
+
+#: ../../managing_networks.rst:965
+# 24ce123387844169a49487bc30845b7a
+msgid "Moving private IP addresses between interfaces or instances. Applications that are bound to specific IP addresses can be moved between instances."
+msgstr ""
+
+#: ../../managing_networks.rst:971
+# 0c37cb7a4c434f399e9d45b1c2e472e9
+msgid "Hosting multiple SSL Websites on a single instance. You can install multiple SSL certificates on a single instance, each associated with a distinct IP address."
+msgstr ""
+
+#: ../../managing_networks.rst:976
+#: ../../managing_networks.rst:6315
+# d4f7b4962530468a906a498acca4bae2
+# 3da7bf4ad1544749bab36764d2d447ef
+msgid "Guidelines"
+msgstr ""
+
+#: ../../managing_networks.rst:978
+# d6caf12c9309436d9de8f99f9c7543c3
+msgid "To prevent IP conflict, configure different subnets when multiple networks are connected to the same VM."
+msgstr ""
+
+#: ../../managing_networks.rst:982
+# 16aeec8d7d974a11ab5270669432a394
+msgid "Assigning Additional IPs to a VM"
+msgstr ""
+
+#: ../../managing_networks.rst:986
+# 034b4e6e920d4b1b819935e74e2b858c
+msgid "Log in to the CloudStack UI."
+msgstr ""
+
+#: ../../managing_networks.rst:990
+# 6a36c11f314b4a73ae436cedecc70f5e
+msgid "In the left navigation bar, click Instances."
+msgstr ""
+
+#: ../../managing_networks.rst:994
+# a8208d3a66ae4646bb1c56d1ecb10311
+msgid "Click the name of the instance you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:998
+# 3614c5b73e634141848b9ffd09823e34
+msgid "In the Details tab, click NICs."
+msgstr ""
+
+#: ../../managing_networks.rst:1002
+# 9ddaf912d7f64aa791244c3f89f4f87e
+msgid "Click View Secondary IPs."
+msgstr ""
+
+#: ../../managing_networks.rst:1006
+# 41a35e39fad3445a94b912212054ec76
+msgid "Click Acquire New Secondary IP, and click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../managing_networks.rst:1009
+# 966f02979ce94ebfad48594d314843e6
+msgid "You need to configure the IP on the guest VM NIC manually. CloudStack will not automatically configure the acquired IP address on the VM. Ensure that the IP address configuration persist on VM reboot."
+msgstr ""
+
+#: ../../managing_networks.rst:1013
+# 6f93e046959a4ebd9133806cbf00c179
+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 StaticNAT rules."
+msgstr ""
+
+#: ../../managing_networks.rst:1018
+# 584ea105deaf4c149e1f4a22e7c76f9c
+msgid "Port Forwarding and StaticNAT Services Changes"
+msgstr ""
+
+#: ../../managing_networks.rst:1020
+# 66fa989a4cf444159810d5b86fe29d71
+msgid "Because multiple IPs can be associated per NIC, you are allowed to select a desired IP for the Port Forwarding and StaticNAT services. The default is the primary IP. To enable this functionality, an extra optional parameter 'vmguestip' is added to the Port forwarding and StaticNAT APIs (enableStaticNat, createIpForwardingRule) to indicate on what IP address NAT need to be configured. If vmguestip is passed, NAT is configured on the specified private IP of the VM. if not passed, NAT is configured on the primary IP of the VM."
+msgstr ""
+
+#: ../../managing_networks.rst:1030
+# d56668f88c1b4778956f3e78eb0af4f3
+msgid "About Multiple IP Ranges"
+msgstr ""
+
+#: ../../managing_networks.rst:1032
+# a425fadff6f24df8a703773e76e1da84
+msgid "The feature can only be implemented on IPv4 addresses."
+msgstr ""
+
+#: ../../managing_networks.rst:1034
+# 085d7bcb306c4df9b4bcb062fa965779
+msgid "CloudStack provides you with the flexibility to add guest IP ranges from different subnets in Basic zones and security groups-enabled Advanced zones. For security groups-enabled Advanced zones, it implies multiple subnets can be added to the same VLAN. With the addition of this feature, you will be able to add IP address ranges from the same subnet or from a different one when IP address are exhausted. This would in turn allows you to employ higher number of subnets and thus reduce the address management overhead. To support this feature, the capability of ``createVlanIpRange`` API is extended to add IP ranges also from a different subnet."
+msgstr ""
+
+#: ../../managing_networks.rst:1045
+# a916ea5fa2a3442cac9346d464c33b3c
+msgid "Ensure that you manually configure the gateway of the new subnet before adding the IP range. Note that CloudStack supports only one gateway for a subnet; overlapping subnets are not currently supported."
+msgstr ""
+
+#: ../../managing_networks.rst:1049
+# 0cb128b2b4964c4c94d50a7d4f4c113d
+msgid "Use the ``deleteVlanRange`` API to delete IP ranges. This operation fails if an IP from the remove range is in use. If the remove range contains the IP address on which the DHCP server is running, CloudStack acquires a new IP from the same subnet. If no IP is available in the subnet, the remove operation fails."
+msgstr ""
+
+#: ../../managing_networks.rst:1055
+# 5c50556940324ae1a2c2f33b4e3be74c
+msgid "This feature is supported on KVM, xenServer, and VMware hypervisors."
+msgstr ""
+
+#: ../../managing_networks.rst:1058
+# 86f5b04f9bf84ff4a0162e548a43ed45
+msgid "About Elastic IP"
+msgstr ""
+
+#: ../../managing_networks.rst:1060
+# 1abc932ae33e4097ad9d5a7c01466858
+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 is down, the IP address can be reassigned to a new VM in your account."
+msgstr ""
+
+#: ../../managing_networks.rst:1069
+# 6f92b16714d4455c9c0d07422b7a5278
+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 ""
+
+#: ../../managing_networks.rst:1077
+# 1917b806df094374b24b204ab96801f8
+msgid "|eip-ns-basiczone.png: Elastic IP in a NetScaler-enabled Basic Zone.|"
+msgstr ""
+
+#: ../../managing_networks.rst:1079
+# 3b1d323c9feb4e9ba7ca76be6aaad6b2
+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 data center goes through the firewall."
+msgstr ""
+
+#: ../../managing_networks.rst:1088
+# d73486cd06ff42a3b7ae00d650f94b85
+msgid "The EIP work flow is as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:1092
+# c76961037d5e4684aae701d14e8628ef
+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 ""
+
+#: ../../managing_networks.rst:1098
+# 113a0b56fa5c4d588763310f3344c045
+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 ""
+
+#: ../../managing_networks.rst:1103
+# 26464e6616334eba867bfbedcd8b9b32
+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 ""
+
+#: ../../managing_networks.rst:1107
+# c24df2c0e244417bac058ee69288159e
+msgid "This default public IP will be released in two cases:"
+msgstr ""
+
+#: ../../managing_networks.rst:1111
+# e69a190aa6ff4094a1376bbd1a48c806
+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 ""
+
+#: ../../managing_networks.rst:1117
+# ae09bc75005442799a101c13ee164cfe
+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 ""
+
+#: ../../managing_networks.rst:1125
+# 85b2631843ed40888b2ca7fe400962fd
+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 and enable static NAT."
+msgstr ""
+
+#: ../../managing_networks.rst:1134
+# 94a57e6c08fb4beeb2cc92ada6ed0e19
+msgid "For more information on the Associate Public IP option, see the Administration Guide."
+msgstr ""
+
+#: ../../managing_networks.rst:1137
+# 51ff3fc654054203b273f9c148ae18b5
+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 ""
+
+#: ../../managing_networks.rst:1139
+# 83364c7e0dd94f759842ac386a8cac79
+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 ""
+
+#: ../../managing_networks.rst:1144
+# 342239c2715c475b88c10804e3612a51
+msgid "Portable IPs"
+msgstr ""
+
+#: ../../managing_networks.rst:1147
+# dd5fc98d73bc4d75beeb09ce0439d181
+msgid "About Portable IP"
+msgstr ""
+
+#: ../../managing_networks.rst:1149
+# 89820f26aa2645078ccb72b82efc9dfe
+msgid "Portable IPs in CloudStack are region-level pool of IPs, which are elastic in nature, that can be transferred across geographically separated zones. As an administrator, you can provision a pool of portable public IPs at region level and are available for user consumption. The users can acquire portable IPs if admin has provisioned portable IPs at the region level they are part of. These IPs can be use for any service within an advanced zone. You can also use portable IPs for EIP services in basic zones."
+msgstr ""
+
+#: ../../managing_networks.rst:1158
+# bd4cf0b29f8b41b3b03e37f656c52501
+msgid "The salient features of Portable IP are as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:1162
+# 855ab24aced14fa18033b90699abf066
+msgid "IP is statically allocated"
+msgstr ""
+
+#: ../../managing_networks.rst:1166
+# 7e45d53e50814ec584c37135e430715f
+msgid "IP need not be associated with a network"
+msgstr ""
+
+#: ../../managing_networks.rst:1170
+# f4869a8c48e8434ea57e20c6cc65cf55
+msgid "IP association is transferable across networks"
+msgstr ""
+
+#: ../../managing_networks.rst:1174
+# 2f9e4bbd9a5c4a61957b15982551f2e9
+msgid "IP is transferable across both Basic and Advanced zones"
+msgstr ""
+
+#: ../../managing_networks.rst:1178
+# ea6d679d393d4bcfa494249d365ba374
+msgid "IP is transferable across VPC, non-VPC isolated and shared networks"
+msgstr ""
+
+#: ../../managing_networks.rst:1182
+# afa26b14dffe40119ee655d8132db452
+msgid "Portable IP transfer is available only for static NAT."
+msgstr ""
+
+#: ../../managing_networks.rst:1187
+# 671509538e074821aee5d282b4fd3822
+msgid "Before transferring to another network, ensure that no network rules (Firewall, Static NAT, Port Forwarding, and so on) exist on that portable IP."
+msgstr ""
+
+#: ../../managing_networks.rst:1192
+# a10fe6016ca4432d9466323adc5feafa
+msgid "Configuring Portable IPs"
+msgstr ""
+
+#: ../../managing_networks.rst:1200
+# 323070f73d46451b97228b1b4aadaa54
+msgid "In the left navigation, click Regions."
+msgstr ""
+
+#: ../../managing_networks.rst:1204
+# 428125e4de8d4140af2bbdfcd4ecc332
+msgid "Choose the Regions that you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:1208
+# eed1d708ff224966a3d021ab2bc33aa6
+msgid "Click View Portable IP."
+msgstr ""
+
+#: ../../managing_networks.rst:1212
+# abc03c1eb418441fb10a7cf6beb37fea
+msgid "Click Portable IP Range."
+msgstr ""
+
+#: ../../managing_networks.rst:1214
+# 595f33e914024c0a86540527bc370258
+msgid "The Add Portable IP Range window is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:1222
+# ca11f239cc8449a6817014a3adcd61a0
+msgid "**Start IP/ End IP**: A range of IP addresses that are accessible from the Internet and will be allocated to guest VMs. Enter the first and last IP addresses that define a range that CloudStack can assign to guest VMs."
+msgstr ""
+
+#: ../../managing_networks.rst:1229
+# 6c64c167231b40a68bfe26799c8054c3
+msgid "**Gateway**: The gateway in use for the Portable IP addresses you are configuring."
+msgstr ""
+
+#: ../../managing_networks.rst:1234
+# 83455a09e71a4eccb3755e02bd14515c
+msgid "**Netmask**: The netmask associated with the Portable IP range."
+msgstr ""
+
+#: ../../managing_networks.rst:1238
+# 7b8fbceeaf074302abbd838f0e2849bf
+msgid "**VLAN**: The VLAN that will be used for public traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:1245
+# d850eac9d4014f0dab3417fab28601f7
+msgid "Acquiring a Portable IP"
+msgstr ""
+
+#: ../../managing_networks.rst:1257
+#: ../../managing_networks.rst:3208
+#: ../../managing_networks.rst:3251
+#: ../../managing_networks.rst:3294
+#: ../../managing_networks.rst:3370
+# 3262a0725955438a99e78981176d092f
+# 701bcf108f834cdc9c4ea748e804dab0
+# 2859adde9cb44f6e970e1a0651717bed
+# e93c68f572f04989afefcb87f1716ec4
+# 5efad310be724f029a2e40ffd479c432
+msgid "Click the name of the network where you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:1261
+#: ../../managing_networks.rst:2170
+#: ../../managing_networks.rst:3212
+#: ../../managing_networks.rst:3255
+#: ../../managing_networks.rst:3298
+#: ../../managing_networks.rst:3374
+#: ../../managing_networks.rst:3784
+# 305ab6c53fda46d8adf4a49df4f72b73
+# 3186a0f1dbbd4b36afd65ce287083ef4
+# 77cf6faa7c404c33bddce8721952e2e2
+# 6fbd7a5b4b7e4fe684956b795c3516f8
+# 6662b46aca0349ffb4f7db65473cf5a4
+# e6ede01e32f44d8d9eb51185ac8cca93
+# c003065bf88441dc838fb6ff067c1d46
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../managing_networks.rst:1265
+#: ../../managing_networks.rst:3216
+# 3cb9985604264815812c496744d99e7a
+# b3b02650cb5849d29899feb56b041267
+msgid "Click Acquire New IP."
+msgstr ""
+
+#: ../../managing_networks.rst:1267
+#: ../../managing_networks.rst:3218
+# 0fd88d76e0454a0aafadff6be75ab526
+# 25404011fc7044529f48e7fb157f04ed
+msgid "The Acquire New IP window is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:1271
+#: ../../managing_networks.rst:3222
+# ead81d2ea1984be4874b71915d73fe10
+# 6fe5747d6b7547a8918070f73c52cc78
+msgid "Specify whether you want cross-zone IP or not."
+msgstr ""
+
+#: ../../managing_networks.rst:1275
+# d4620b5751e246e48d4c00aca1d4a8f3
+msgid "Click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../managing_networks.rst:1277
+#: ../../managing_networks.rst:3230
+# 99771ddd9716455ba6a961284174f20b
+# 1ff8f2a384d445a8ba816f2443f9a096
+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 ""
+
+#: ../../managing_networks.rst:1282
+# e9a2afafc0df48bcba35924913d45e73
+msgid "Transferring Portable IP"
+msgstr ""
+
+#: ../../managing_networks.rst:1284
+# 65ca926473184157a1cfd41612675661
+msgid "An IP can be transferred from one network to another only if Static NAT is enabled. However, when a portable IP is associated with a network, you can use it for any service in the network."
+msgstr ""
+
+#: ../../managing_networks.rst:1288
+# 8afb23c700a44791bb6a9fa4690d1649
+msgid "To transfer a portable IP across the networks, execute the following API:"
+msgstr ""
+
+#: ../../managing_networks.rst:1295
+# 55a1869308ee4aed849674dc2535b805
+msgid "Replace the UUID with appropriate UUID. For example, if you want to transfer a portable IP to network X and VM Y in a network, execute the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:1304
+# 3afd351582954a49b746d509abba4eac
+msgid "Multiple Subnets in Shared Network"
+msgstr ""
+
+#: ../../managing_networks.rst:1306
+# 9a2eae7b8f84440f90cd0402d4ed0d76
+msgid "CloudStack provides you with the flexibility to add guest IP ranges from different subnets in Basic zones and security groups-enabled Advanced zones. For security groups-enabled Advanced zones, it implies multiple subnets can be added to the same VLAN. With the addition of this feature, you will be able to add IP address ranges from the same subnet or from a different one when IP address are exhausted. This would in turn allows you to employ higher number of subnets and thus reduce the address management overhead. You can delete the IP ranges you have added."
+msgstr ""
+
+#: ../../managing_networks.rst:1317
+#: ../../managing_networks.rst:2885
+#: ../../managing_networks.rst:3426
+# 344b838f0b0841728cb18a682c1962e2
+# ca130580b3e848d59bbd0823702a71ad
+# 9d4bbe7d6b854394bcbb260e68f1226a
+msgid "Prerequisites and Guidelines"
+msgstr ""
+
+#: ../../managing_networks.rst:1321
+# 231696a9da0c47e5be1d4fec098a8b7f
+msgid "This feature can only be implemented:"
+msgstr ""
+
+#: ../../managing_networks.rst:1325
+# e11af27c4f9b4a68aa2b824c8d51ef26
+msgid "on IPv4 addresses"
+msgstr ""
+
+#: ../../managing_networks.rst:1329
+# 89a310c9cc9a4cc0b046da60d4db626f
+msgid "if virtual router is the DHCP provider"
+msgstr ""
+
+#: ../../managing_networks.rst:1333
+# 2f901469d8a547669181457a79ea3825
+msgid "on KVM, xenServer, and VMware hypervisors"
+msgstr ""
+
+#: ../../managing_networks.rst:1337
+# 07ac9be1fbd949109da3f8269a75cd31
+msgid "Manually configure the gateway of the new subnet before adding the IP range."
+msgstr ""
+
+#: ../../managing_networks.rst:1342
+# fd0dee06ed544e709ea404a01e2141a4
+msgid "CloudStack supports only one gateway for a subnet; overlapping subnets are not currently supported"
+msgstr ""
+
+#: ../../managing_networks.rst:1346
+# cfe0f1c81e094655b1cf2158397f8beb
+msgid "Adding Multiple Subnets to a Shared Network"
+msgstr ""
+
+#: ../../managing_networks.rst:1358
+# 2239434247834913b8b23dab3f7f896d
+msgid "On Zones, click View More, then click the zone to which you want to work with.."
+msgstr ""
+
+#: ../../managing_networks.rst:1363
+# 52b4f5c3dc6c4c96a91c21e53b5f6ba7
+msgid "Click Physical Network."
+msgstr ""
+
+#: ../../managing_networks.rst:1371
+# d545de9168774122b8d39fe9b88db0f9
+msgid "Click Networks."
+msgstr ""
+
+#: ../../managing_networks.rst:1375
+# 201b95be96f741419b7a53c915e3da38
+msgid "Select the networks you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:1379
+# b1dafa11c6dd48aaba7215933fc61640
+msgid "Click View IP Ranges."
+msgstr ""
+
+#: ../../managing_networks.rst:1383
+# 962df84772504a178c0760d6862328be
+msgid "Click Add IP Range."
+msgstr ""
+
+#: ../../managing_networks.rst:1385
+# a8c9f66de4e84e56882ecb276ca04e41
+msgid "The Add IP Range dialog is displayed, as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:1387
+# ae7f538d814144019a90e1b0ac6f4a3d
+msgid "|add-ip-range.png: adding an IP range to a network.|"
+msgstr ""
+
+#: ../../managing_networks.rst:1393
+#: ../../managing_networks.rst:5063
+# 0884d274eba74f889ae1c3abffff98dd
+# 03a1c57fd13d4fdb9f6c63ec4afcc907
+msgid "All the fields are mandatory."
+msgstr ""
+
+#: ../../managing_networks.rst:1397
+#: ../../managing_networks.rst:5081
+# 8da5ac3902824555b54847009a765ed7
+# fe107d12592248a982087f39da19a41a
+msgid "**Gateway**: The gateway for the tier you create. Ensure that the gateway is within the Super CIDR range that you specified while creating the VPC, and is not overlapped with the CIDR of any existing tier within the VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:1404
+#: ../../managing_networks.rst:5098
+# d23bd452fc4d46579356f5ede9152d95
+# af646832ee3f44ebaa1213c5db09bb4a
+msgid "**Netmask**: The netmask for the tier you create."
+msgstr ""
+
+#: ../../managing_networks.rst:1406
+#: ../../managing_networks.rst:5100
+# 86f10e90777a4711964d8a8df3a0e45c
+# 04b52f8b675747ee8a9c73e86c123710
+msgid "For example, if the VPC CIDR is 10.0.0.0/16 and the network tier CIDR is 10.0.1.0/24, the gateway of the tier is 10.0.1.1, and the netmask of the tier is 255.255.255.0."
+msgstr ""
+
+#: ../../managing_networks.rst:1412
+# 3bdc377e66c842a4a3f09450a0832e67
+msgid "**Start IP/ End IP**: A range of IP addresses that are accessible from the Internet and will be allocated to guest VMs. Enter the first and last IP addresses that define a range that CloudStack can assign to guest VMs ."
+msgstr ""
+
+#: ../../managing_networks.rst:1422
+# b6a0de7ae6b643a3b425583d43f6163e
+msgid "Isolation in Advanced Zone Using Private VLAN"
+msgstr ""
+
+#: ../../managing_networks.rst:1424
+# 4f75858c33ec4279a864c4b208e29b2b
+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 users’ VMs."
+msgstr ""
+
+#: ../../managing_networks.rst:1435
+# 2b100ae9fa4e4eaea15ed0c9c965697f
+msgid "Isolate VMs in a shared networks by using Private VLANs."
+msgstr ""
+
+#: ../../managing_networks.rst:1439
+# 72cb21f4bdaa4f6c88f7f1253969f497
+msgid "Supported on KVM, XenServer, and VMware hypervisors"
+msgstr ""
+
+#: ../../managing_networks.rst:1443
+# 64e4f6f904e145cc94c88300b2f6f1ec
+msgid "PVLAN-enabled shared network can be a part of multiple networks of a guest VM."
+msgstr ""
+
+#: ../../managing_networks.rst:1447
+# 39b527fd98914ef4ae1f7cd5d5a083c3
+msgid "About Private VLAN"
+msgstr ""
+
+#: ../../managing_networks.rst:1449
+# ffcf29c6500a4e3a897fefd357efafa1
+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 VLAN that is being divided into smaller groups is called Primary, which implies that all VLAN pairs in a private VLAN share the same Primary VLAN. All the secondary VLANs exist only inside the Primary. Each Secondary VLAN has a specific VLAN ID associated to it, which differentiates one sub-domain from another."
+msgstr ""
+
+#: ../../managing_networks.rst:1462
+# dadf77ad95da46d29d655fa1b5c88836
+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 ""
+
+#: ../../managing_networks.rst:1471
+# 338ab35c29694e549d0f63e57cf3ecfc
+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 ""
+
+#: ../../managing_networks.rst:1481
+# 1eb75b61178b4a8da29196b19e0755f1
+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 ""
+
+#: ../../managing_networks.rst:1489
+# 3c344baffb3649a3a99b4762947818ae
+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 communicate among themselves, deploy them in community ports."
+msgstr ""
+
+#: ../../managing_networks.rst:1499
+# a10ac6622d024e57899b845f7e847140
+msgid "For further reading:"
+msgstr ""
+
+#: ../../managing_networks.rst:1503
+# 5efde3c2b6894bd387b0f388d8bdeae3
+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 ""
+
+#: ../../managing_networks.rst:1508
+# 02596ab9a4bd47daaed6a4272e786d9a
+msgid "`Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment <http://tools.ietf.org/html/rfc5517>`__"
+msgstr ""
+
+#: ../../managing_networks.rst:1513
+# 886e828c09384218b5bd4f8cd224d968
+msgid "`Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview (1010691) <http://kb.vmware.com>`__"
+msgstr ""
+
+#: ../../managing_networks.rst:1521
+# 6cb7c445963a491caff15981fe0b4ce4
+msgid "Use a PVLAN supported switch."
+msgstr ""
+
+#: ../../managing_networks.rst:1523
+# f7f97cd16eb24ff588d513c2d34ff289
+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 ""
+
+#: ../../managing_networks.rst:1529
+# 09e5467647fd4eb6af74a6c1cb65b159
+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 ""
+
+#: ../../managing_networks.rst:1537
+# 3eb08525c8114e1fade9c52b44c14c59
+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 ""
+
+#: ../../managing_networks.rst:1544
+# e9c74dd366ef45f1be1d0793986d7f73
+msgid "Configure private VLAN on your physical switches out-of-band."
+msgstr ""
+
+#: ../../managing_networks.rst:1548
+# 2ecc130e165749aba238d52a9a7f2486
+msgid "Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS)."
+msgstr ""
+
+#: ../../managing_networks.rst:1550
+# 030698129200435e9f708d7cb120c98b
+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 ""
+
+#: ../../managing_networks.rst:1553
+# f6a73d4d4c73444dbf0a403921b5aa74
+msgid "Creating a PVLAN-Enabled Guest Network"
+msgstr ""
+
+#: ../../managing_networks.rst:1613
+# 740911b6b7d14c93bb243f861cbde303
+msgid "**Secondary Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr ""
+
+#: ../../managing_networks.rst:1616
+# 33d01a6c72b3484991970c439ebe1b80
+msgid "For the description on Secondary Isolated VLAN, see `Section 15.14.1, “About Private VLAN” <#about-pvlan>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:1679
+# 2c24eb1bc100495989166e76788319c0
+msgid "Security Groups"
+msgstr ""
+
+#: ../../managing_networks.rst:1682
+# d331348078ea4de8a8dc8471c9cc3cce
+msgid "About Security Groups"
+msgstr ""
+
+#: ../../managing_networks.rst:1684
+# f34bf064d0114b288f2f55f17a25f84a
+msgid "Security groups provide a way to isolate traffic to VMs. 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. Security groups are particularly useful in zones that use basic networking, because there is a single guest network for all guest VMs. In advanced zones, security groups are supported only on the KVM hypervisor."
+msgstr ""
+
+#: ../../managing_networks.rst:1693
+# 5e82a09d657a4767acec9f22d782de51
+msgid "In a zone that uses advanced networking, you can instead define multiple guest networks to isolate traffic to VMs."
+msgstr ""
+
+#: ../../managing_networks.rst:1695
+# 79f27644dfcf4cf788bba960a7f3b5bf
+msgid "Each CloudStack account comes with a default security group that denies all inbound traffic and allows all outbound traffic. The default security group can be modified so that all new VMs inherit some other desired set of rules."
+msgstr ""
+
+#: ../../managing_networks.rst:1700
+# baa28941d5194fae811bbd88c61df125
+msgid "Any CloudStack user can set up any number of additional security groups. When a new VM is launched, it is assigned to the default security group unless another user-defined security group is specified. A VM can be a member of any number of security groups. Once a VM is assigned to a security group, it remains in that group for its entire lifetime; you can not move a running VM from one security group to another."
+msgstr ""
+
+#: ../../managing_networks.rst:1707
+# de98d0c1571a4cc18032b6472947663b
+msgid "You can modify a security group by deleting or adding any number of ingress and egress rules. When you do, the new rules apply to all VMs in the group, whether running or stopped."
+msgstr ""
+
+#: ../../managing_networks.rst:1711
+# 6e7dbedd8ee140e1ad567e65c7ff552d
+msgid "If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule."
+msgstr ""
+
+#: ../../managing_networks.rst:1716
+# 50b80901d7c24d66a23e838b0f4293d3
+msgid "Adding a Security Group"
+msgstr ""
+
+#: ../../managing_networks.rst:1718
+# f870c727a4ba4b5fafdca88cc7a4b660
+msgid "A user or administrator can define a new security group."
+msgstr ""
+
+#: ../../managing_networks.rst:1726
+#: ../../managing_networks.rst:1803
+# 2bd568db435b4894a6594bdabb71b71f
+# ec651383a1084a9bb247059b0cb38cc8
+msgid "In the left navigation, choose Network"
+msgstr ""
+
+#: ../../managing_networks.rst:1730
+# 20641ac9b26d48a8a2af8025a38b3550
+msgid "In Select view, choose Security Groups."
+msgstr ""
+
+#: ../../managing_networks.rst:1734
+# 3b8b48dea99749bf821c45bf85f5edce
+msgid "Click Add Security Group."
+msgstr ""
+
+#: ../../managing_networks.rst:1738
+# da5c74165969469d9c2395eaaa3f94e6
+msgid "Provide a name and description."
+msgstr ""
+
+#: ../../managing_networks.rst:1744
+# cebb13c23de64a278615d79e7d92b3bc
+msgid "The new security group appears in the Security Groups Details tab."
+msgstr ""
+
+#: ../../managing_networks.rst:1748
+# b0f1a7c4f9d74d0cbf905c6ce03546b8
+msgid "To make the security group useful, continue to Adding Ingress and Egress Rules to a Security Group."
+msgstr ""
+
+#: ../../managing_networks.rst:1752
+# 0c59765ee0c64629952434a87beb9d81
+msgid "Security Groups in Advanced Zones (KVM Only)"
+msgstr ""
+
+#: ../../managing_networks.rst:1754
+# 33c22ff2d84d4c149fb2a3ba75f8689f
+msgid "CloudStack provides the ability to use security groups to provide isolation between guests on a single shared, zone-wide network in an advanced zone where KVM is the hypervisor. Using security groups in advanced zones rather than multiple VLANs allows a greater range of options for setting up guest isolation in a cloud."
+msgstr ""
+
+#: ../../managing_networks.rst:1760
+# 0d98099524ba4909b604a7399ffc1bd8
+msgid "Limitations: The following are not supported for this feature:"
+msgstr ""
+
+#: ../../managing_networks.rst:1764
+# cfee500d52ad40699096b1a8e4e389c1
+msgid "Two IP ranges with the same VLAN and different gateway or netmask in security group-enabled shared network."
+msgstr ""
+
+#: ../../managing_networks.rst:1769
+# 6246185f1f154f93875963e698243930
+msgid "Two IP ranges with the same VLAN and different gateway or netmask in account-specific shared networks."
+msgstr ""
+
+#: ../../managing_networks.rst:1774
+# 1d7c154fd0c34eaf9711d6ec05f84dee
+msgid "Multiple VLAN ranges in security group-enabled shared network."
+msgstr ""
+
+#: ../../managing_networks.rst:1778
+# d31b3ceda7e84ff09119957ddcbbdf2b
+msgid "Multiple VLAN ranges in account-specific shared networks."
+msgstr ""
+
+#: ../../managing_networks.rst:1780
+# 6eeb1f2182894bc383d39cb1f701fb27
+msgid "Security groups must be enabled in the zone in order for this feature to be used."
+msgstr ""
+
+#: ../../managing_networks.rst:1784
+# d9c879f6880c426dbe5cc14699e86c87
+msgid "Enabling Security Groups"
+msgstr ""
+
+#: ../../managing_networks.rst:1786
+# 6038307bd32f4032b2cf2283627e5084
+msgid "In order for security groups to function in a zone, the security groups feature must first be enabled for the zone. The administrator can do this when creating a new zone, by selecting a network offering that includes security groups. The procedure is described in Basic Zone Configuration in the Advanced Installation Guide. The administrator can not enable security groups for an existing zone, only when creating a new zone."
+msgstr ""
+
+#: ../../managing_networks.rst:1795
+# 9239428930ac475c8787a1fa5c7b5852
+msgid "Adding Ingress and Egress Rules to a Security Group"
+msgstr ""
+
+#: ../../managing_networks.rst:1807
+# 1dabe90dfbf742b1ad863dda6a7370cf
+msgid "In Select view, choose Security Groups, then click the security group you want ."
+msgstr ""
+
+#: ../../managing_networks.rst:1812
+# 14c6cdb0f76f4e5bafb8a8247c89a3f5
+msgid "To add an ingress rule, click the Ingress Rules tab and fill out the following fields to specify what network traffic is allowed into VM instances in this security group. If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule."
+msgstr ""
+
+#: ../../managing_networks.rst:1820
+# dbc6db6a8f164564b90b36fb8600f6c4
+msgid "**Add by CIDR/Account**. Indicate whether the source of the traffic will be defined by IP address (CIDR) or an existing security group in a CloudStack account (Account). Choose Account if you want to allow incoming traffic from all VMs in another security group"
+msgstr ""
+
+#: ../../managing_networks.rst:1828
+# c7404bcf0635456b924a7d4461860444
+msgid "**Protocol**. The networking protocol that sources will use to send traffic to the security group. TCP and UDP are typically used for data exchange and end-user communications. ICMP is typically used to send error messages or network monitoring data."
+msgstr ""
+
+#: ../../managing_networks.rst:1835
+# 553fb9fc05c647d38e4c15f2ccbb5123
+msgid "**Start Port, End Port**. (TCP, UDP only) A range of listening ports that are the destination for the incoming traffic. If you are opening a single port, use the same number in both fields."
+msgstr ""
+
+#: ../../managing_networks.rst:1841
+# f1ac0dd3df2a46ad8b321cc49981a565
+msgid "**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code that will be accepted."
+msgstr ""
+
+#: ../../managing_networks.rst:1846
+# 4b14903d5adb4c9a8301a393218c0fe9
+msgid "**CIDR**. (Add by CIDR only) To accept only traffic from 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 incoming traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr ""
+
+#: ../../managing_networks.rst:1854
+# c1561e01a67747a699e6e8f0b8d265a1
+msgid "**Account, Security Group**. (Add by Account only) To accept only traffic from another security group, enter the CloudStack account and name of a security group that has already been defined in that account. To allow traffic between VMs within the security group you are editing now, enter the same name you used in step 7."
+msgstr ""
+
+#: ../../managing_networks.rst:1860
+# 04916ecc9b4840d8804edbc1bb1bc4f7
+msgid "The following example allows inbound HTTP access from anywhere:"
+msgstr ""
+
+#: ../../managing_networks.rst:1862
+# 10d3ac32eaec4653a69e66dd007f355a
+msgid "|httpaccess.png: allows inbound HTTP access from anywhere|"
+msgstr ""
+
+#: ../../managing_networks.rst:1866
+# f0c00b232e4347b19d537a01dae35eac
+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 security group. If no egress rules are specified, then all traffic will be allowed out. Once egress rules are specified, the following types of traffic are allowed out: traffic specified in egress rules; queries to DNS and DHCP servers; and responses to any traffic that has been allowed in through an ingress rule"
+msgstr ""
+
+#: ../../managing_networks.rst:1877
+# 0e14fad2168c4e78b9fc5a5da9f303f4
+msgid "**Add by CIDR/Account**. Indicate whether the destination of the traffic will be defined by IP address (CIDR) or an existing security group in a CloudStack account (Account). Choose Account if you want to allow outgoing traffic to all VMs in another security group."
+msgstr ""
+
+#: ../../managing_networks.rst:1885
+# 1a02e526bf804681aaddd5d1f0ed1ce9
+msgid "**Protocol**. The networking protocol that VMs will use to send outgoing traffic. TCP and UDP are typically used for data exchange and end-user communications. ICMP is typically used to send error messages or network monitoring data."
+msgstr ""
+
+#: ../../managing_networks.rst:1892
+# b0ec41fcd32641b3944750fc36979e9a
+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 ""
+
+#: ../../managing_networks.rst:1898
+# f1360ae9661b4df29243b766c0bb4aa2
+msgid "**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code that will be sent"
+msgstr ""
+
+#: ../../managing_networks.rst:1903
+# 350a113cb8dd4f31994777cc4fb0bd62
+msgid "**CIDR**. (Add by CIDR only) To send traffic only to 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 ""
+
+#: ../../managing_networks.rst:1911
+# 0a29a66f07214b4db9dde4958f6b9ce8
+msgid "**Account, Security Group**. (Add by Account only) To allow traffic to be sent to another security group, enter the CloudStack account and name of a security group that has already been defined in that account. To allow traffic between VMs within the security group you are editing now, enter its name."
+msgstr ""
+
+#: ../../managing_networks.rst:1922
+# 9703c00d7003480993587ff39b757c8e
+msgid "External Firewalls and Load Balancers"
+msgstr ""
+
+#: ../../managing_networks.rst:1924
+# f80e67cfaf2b4e8ba6fe5e89961f1604
+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 ""
+
+#: ../../managing_networks.rst:1930
+# ae5fe8317334469fadbdb5e10bfb6484
+msgid "About Using a NetScaler Load Balancer"
+msgstr ""
+
+#: ../../managing_networks.rst:1932
+# e93ff8055f5c45e397a20a5eec844c9d
+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 ""
+
+#: ../../managing_networks.rst:1937
+# b35f57f9209f4a39bca7644428cc5471
+msgid "In a Basic zone, load balancing service is supported only if Elastic IP or Elastic LB services are enabled."
+msgstr ""
+
+#: ../../managing_networks.rst:1939
+# 432354c2478043e585e3be569496f81f
+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 device providing EIP/ELB, layer 3 router must have a policy-based routing. A policy-based route must be set up so that all traffic originated from the guest VM's are directed to NetScaler device. This is required to ensure that the outbound traffic from the guest VM's is routed to a public IP by using NAT.For more information on Elastic IP, see `Section 15.11, “About Elastic IP” <#elastic-ip>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:1953
+# c55b5331d1654661ba6a8b891a476d7b
+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 ""
+
+#: ../../managing_networks.rst:1957
+# 820e88370085451ab81b601ac5092dac
+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 ""
+
+#: ../../managing_networks.rst:1962
+# bd46111da3364f82a10dafe9f0493719
+msgid "To install and enable an external load balancer for CloudStack management, see `Section 13.5.4, “External Guest Load Balancer Integration (Optional)” <#external-guest-lb-integration>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:1966
+# 3d1489d6890045afa4bf8363cde00c85
+msgid "The Citrix NetScaler comes in three varieties. The following table summarizes how these variants are treated in CloudStack."
+msgstr ""
+
+#: ../../managing_networks.rst:1970
+# 2927f19bf6bb4d3bb378a8577b25625a
+msgid "NetScaler ADC Type"
+msgstr ""
+
+#: ../../managing_networks.rst:1970
+# 2b1a2bad59464e32bb278dabdccd5e47
+msgid "Description of Capabilities CloudStack Supported Features"
+msgstr ""
+
+#: ../../managing_networks.rst:1972
+# 39c4c063dc7a4318a25731f69953f77f
+msgid "MPX"
+msgstr ""
+
+#: ../../managing_networks.rst:1972
+# ea198bf147554fa7a44f413842a7cf5b
+msgid "Physical appliance. Capable of deep packet inspection. Can act as application firewall and load balancer."
+msgstr ""
+
+#: ../../managing_networks.rst:1972
+# a333a75371ca4e3bbcf547d8ad6f5c02
+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 ""
+
+#: ../../managing_networks.rst:1973
+# 3ed6562f8db44f62838fe4626dfc5b42
+msgid "VPX"
+msgstr ""
+
+#: ../../managing_networks.rst:1973
+# ddd9e04881a14b22854e0d68d62da1fd
+msgid "Virtual appliance. Can run as VM on XenServer, ESXi, and Hyper-V hypervisors. Same functionality as MPX."
+msgstr ""
+
+#: ../../managing_networks.rst:1973
+# 6d6c6be8254042c58f42881bf458f16a
+msgid "Supported on ESXi and XenServer. Same functional support as for MPX. CloudStack will treat VPX and MPX as the same device type."
+msgstr ""
+
+#: ../../managing_networks.rst:1974
+# 5c01f29af8d747a8bd66543d6871ebff
+msgid "SDX"
+msgstr ""
+
+#: ../../managing_networks.rst:1974
+# 242fb2a841c945aa93d42db46483f206
+msgid "Physical appliance. Can create multiple fully isolated VPX instances on a single appliance to support multi-tenant usage"
+msgstr ""
+
+#: ../../managing_networks.rst:1974
+# 18dac2747b4240b4a97a950679f07e9b
+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 ""
+
+#: ../../managing_networks.rst:1978
+# ac9fa52a18d4459aa785bbf9fa582470
+msgid "Configuring SNMP Community String on a RHEL Server"
+msgstr ""
+
+#: ../../managing_networks.rst:1980
+# 3f04d5be0b624710a9353ea54e5f6cd4
+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 ""
+
+#: ../../managing_networks.rst:1986
+# ae292ca0b1c54168812d01ef32f1ab3f
+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 ""
+
+#: ../../managing_networks.rst:1992
+# 6a8596f21b7440bfb1f7c8eb2bfc8628
+msgid "Ensure that you installed SNMP on RedHat. If not, run the following command:"
+msgstr ""
+
+#: ../../managing_networks.rst:2001
+# e86f60a54a14414296b44f545df45ecb
+msgid "Edit the /etc/snmp/snmpd.conf file to allow the SNMP polling from the NetScaler device."
+msgstr ""
+
+#: ../../managing_networks.rst:2006
+# c7ae2f4b80e448589a7324e9160cc098
+msgid "Map the community name into a security name (local and mynetwork, depending on where the request is coming from):"
+msgstr ""
+
+#: ../../managing_networks.rst:2009
+# 82d2e1366fcb407292043214ee132fd0
+msgid "Use a strong password instead of public when you edit the following table."
+msgstr ""
+
+#: ../../managing_networks.rst:2017
+# a60077478293466090acdec3a98361b3
+msgid "Setting to 0.0.0.0 allows all IPs to poll the NetScaler server."
+msgstr ""
+
+#: ../../managing_networks.rst:2021
+# dde16e249ba84f859fe076f1169b118b
+msgid "Map the security names into group names:"
+msgstr ""
+
+#: ../../managing_networks.rst:2033
+# 74b3e712da4d47a3b29ca52d3fe14e7d
+msgid "Create a view to allow the groups to have the permission to:"
+msgstr ""
+
+#: ../../managing_networks.rst:2041
+# d114649652ac478097b5ba7219ecd9b1
+msgid "Grant access with different write permissions to the two groups to the view you created."
+msgstr ""
+
+#: ../../managing_networks.rst:2052
+# 35e6d3349499465981e06188c2545f91
+msgid "Unblock SNMP in iptables."
+msgstr ""
+
+#: ../../managing_networks.rst:2060
+# 06ec2d8329bb44eca854ac9124a54ac2
+msgid "Start the SNMP service:"
+msgstr ""
+
+#: ../../managing_networks.rst:2068
+# 620bd58e847546af8ec5eee6f1df392f
+msgid "Ensure that the SNMP service is started automatically during the system startup:"
+msgstr ""
+
+#: ../../managing_networks.rst:2076
+# 459a59b07c9a487bb876fb3570027f56
+msgid "Initial Setup of External Firewalls and Load Balancers"
+msgstr ""
+
+#: ../../managing_networks.rst:2078
+# bcccbb4ccd2742e988440761c1c97c3d
+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 ""
+
+#: ../../managing_networks.rst:2084
+# b2a4387bb61a40b2a674374748325e75
+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 ""
+
+#: ../../managing_networks.rst:2090
+# 73a0ab4e7e52401893fb6876bddfa3c1
+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 ""
+
+#: ../../managing_networks.rst:2096
+# a91c17a9a27744d590cca5c8ae83e4f3
+msgid "A firewall filter counter that measures the number of bytes of outgoing traffic for the account"
+msgstr ""
+
+#: ../../managing_networks.rst:2099
+# a969e661812f4c76a64517563139bc46
+msgid "The following objects are created on the load balancer:"
+msgstr ""
+
+#: ../../managing_networks.rst:2103
+# 70a41496c1d8446eb94f4846d5f48807
+msgid "A new VLAN that matches the account's provisioned Zone VLAN"
+msgstr ""
+
+#: ../../managing_networks.rst:2107
+# 2c7b27d0b7ba4358879882aecb0f85b2
+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 ""
+
+#: ../../managing_networks.rst:2111
+# f331ea1b60734e7e9cf00688be8a014a
+msgid "Ongoing Configuration of External Firewalls and Load Balancers"
+msgstr ""
+
+#: ../../managing_networks.rst:2113
+# 283a3ee82af240268e7f73eee64568cc
+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 objects:"
+msgstr ""
+
+#: ../../managing_networks.rst:2124
+# 7f37822b183846029b22d982605df64a
+msgid "A static NAT rule that maps the public IP address to the private IP address of a VM."
+msgstr ""
+
+#: ../../managing_networks.rst:2129
+# 04d5cfd64b5a49ca87e10c965ebcbbe8
+msgid "A security policy that allows traffic within the set of protocols and port ranges that are specified."
+msgstr ""
+
+#: ../../managing_networks.rst:2134
+# b32ae655c9424e7aa37228b3b21d1b57
+msgid "A firewall filter counter that measures the number of bytes of incoming traffic to the public IP."
+msgstr ""
+
+#: ../../managing_networks.rst:2137
+# cd8452f768c14fdd8fbd4e7432ae4f05
+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 ""
+
+#: ../../managing_networks.rst:2143
+# ad1eac1dba114d83a1aef1f71f058a04
+msgid "Load Balancer Rules"
+msgstr ""
+
+#: ../../managing_networks.rst:2145
+# 7705d32d38f54ae985f6e0d7cdbe4094
+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 ""
+
+#: ../../managing_networks.rst:2150
+# 711015b6ce824631aa25054b86e45fd5
+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 ""
+
+#: ../../managing_networks.rst:2153
+# b1392c053235469d9db00ff277fe4081
+msgid "Adding a Load Balancer Rule"
+msgstr ""
+
+#: ../../managing_networks.rst:2165
+# a9769f3aee3741018069f035a314faec
+msgid "Click the name of the network where you want to load balance the traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:2174
+#: ../../managing_networks.rst:6224
+#: ../../managing_networks.rst:6616
+# e7820b855f9a4bdc825b874af1ee74ac
+# 57f9df7d52c143248cee80215df6b361
+# f15c85d6dc1d4b1da943709cbeb66d6e
+msgid "Click the IP address for which you want to create the rule, then click the Configuration tab."
+msgstr ""
+
+#: ../../managing_networks.rst:2179
+#: ../../managing_networks.rst:6229
+# 7882de69bd334597b436f05ffb59daa7
+# 8271af5525f04c1399625a2ae00356f3
+msgid "In the Load Balancing node of the diagram, click View All."
+msgstr ""
+
+#: ../../managing_networks.rst:2181
+# 4361d1b583104cc89c442cd88c0522c4
+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 ""
+
+#: ../../managing_networks.rst:2186
+# 4a94254b17ed4ec39f2315e6a888fb5a
+msgid "To do that, select the name of the network, then click Add Load Balancer tab. Continue with `7 <#config-lb>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:2191
+#: ../../managing_networks.rst:3648
+# 9ee5e7cec16645afac9aaaaff13a496c
+# 657c6d30f6814207ba6bd9d39da07f82
+msgid "Fill in the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:2195
+#: ../../managing_networks.rst:6241
+#: ../../managing_networks.rst:6497
+# c407a31e5baa4fad9d35127bff1b7daa
+# d76bf4093eba4a98af63df8739a8e847
+# e45e3c4b92ee4267b003f94314d91095
+msgid "**Name**: A name for the load balancer rule."
+msgstr ""
+
+#: ../../managing_networks.rst:2199
+# 86b0b5a5cb264775a51f8c349e910dbe
+msgid "**Public Port**: The port receiving incoming traffic to be balanced."
+msgstr ""
+
+#: ../../managing_networks.rst:2204
+#: ../../managing_networks.rst:6250
+# 009ab0a02f2749b3875ebca762117055
+# aab69f01a8cb47409f9590eb9521467f
+msgid "**Private Port**: The port that the VMs will use to receive the traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:2209
+# a01e2f1dc4fd49108b0d7ba3e2ae529e
+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 ""
+
+#: ../../managing_networks.rst:2216
+# 997d16371c9e465699db38061283e6b4
+msgid "**Stickiness**: (Optional) Click Configure and choose the algorithm for the stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr ""
+
+#: ../../managing_networks.rst:2222
+# 18519de60f3f473c83ac612b5fad495c
+msgid "**AutoScale**: Click Configure and complete the AutoScale configuration as explained in `Section 15.16.6, “Configuring AutoScale” <#autoscale>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:2228
+# 3908f0ca791a42debbb0585189fb7c1e
+msgid "**Health Check**: (Optional; NetScaler load balancers only) Click Configure and fill in the characteristics of the health check policy. See `Section 15.16.5.3, “Health Checks for Load Balancer Rules” <#health-checks-for-lb-rules>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:2235
+# 2879252f32f34f539751be82bf984014
+msgid "**Ping path (Optional)**: Sequence of destinations to which to send health check queries. Default: / (all)."
+msgstr ""
+
+#: ../../managing_networks.rst:2240
+# a8debc6dcd7145d7afebfc88d610080e
+msgid "**Response time (Optional)**: How long to wait for a response from the health check (2 - 60 seconds). Default: 5 seconds."
+msgstr ""
+
+#: ../../managing_networks.rst:2245
+# 8fc593a6bc1348d28c5ad36ef1ee55b2
+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 ""
+
+#: ../../managing_networks.rst:2252
+# 6d4cfb962ee94044af1572953fdaad0f
+msgid "**Healthy threshold (Optional)**: Number of consecutive health check successes that are required before declaring an instance healthy. Default: 2."
+msgstr ""
+
+#: ../../managing_networks.rst:2258
+# be452bfbd60c44ee89f3cacb209f6879
+msgid "**Unhealthy threshold (Optional)**: Number of consecutive health check failures that are required before declaring an instance unhealthy. Default: 10."
+msgstr ""
+
+#: ../../managing_networks.rst:2264
+# 457c998fe4d6462bab0cb048fd076832
+msgid "Click Add VMs, then select two or more VMs that will divide the load of incoming traffic, and click Apply."
+msgstr ""
+
+#: ../../managing_networks.rst:2267
+# 820fdad3c2f04d08aab271b8010f13fb
+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 ""
+
+#: ../../managing_networks.rst:2271
+# 76399c00e68f42168b802e6ddff1fb49
+msgid "Sticky Session Policies for Load Balancer Rules"
+msgstr ""
+
+#: ../../managing_networks.rst:2273
+# 1b0830c090eb4231b808b590bc10dd15
+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 ""
+
+#: ../../managing_networks.rst:2279
+# 89d324559b614ee8916fe9d09229e529
+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, cookies are used. The cookie generated by the load balancer or application is included in request and response URLs to create persistence. The cookie name can be specified by the administrator or automatically generated. A variety of options are provided to control the exact behavior of cookies, such as how they are generated and whether they are cached."
+msgstr ""
+
+#: ../../managing_networks.rst:2293
+# 8ac187f8411440ac922c801d4fd2171e
+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 ""
+
+#: ../../managing_networks.rst:2298
+# d4666e89faf1441f96dac55fcaa4010f
+msgid "Health Checks for Load Balancer Rules"
+msgstr ""
+
+#: ../../managing_networks.rst:2300
+# ed1c6c49e9804202a2791f6dbf88fead
+msgid "(NetScaler load balancer only; requires NetScaler version 10.0)"
+msgstr ""
+
+#: ../../managing_networks.rst:2302
+# 4e756b5788bb4edbb5189cd1de10fe72
+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 ""
+
+#: ../../managing_networks.rst:2309
+# d4587d4fb2ec4c1782622d46fca4b609
+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 ""
+
+#: ../../managing_networks.rst:2314
+# fada8ec075ce48a3915f6a674da4ecce
+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 with a health check configured, the state will be shown as UP or DOWN in the UI depending on the result of the most recent health check."
+msgstr ""
+
+#: ../../managing_networks.rst:2324
+# 7a1f1e9599b14a929b0eb739ba5b1ed6
+msgid "You can delete or modify existing health check policies."
+msgstr ""
+
+#: ../../managing_networks.rst:2326
+# 242bd90478da46a3874cacc3c3fe8e44
+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 ""
+
+#: ../../managing_networks.rst:2331
+# 50015277b8b2447f9cc7b404b78076ad
+msgid "For details on how to set a health check policy using the UI, see `Section 15.16.5.1, “Adding a Load Balancer Rule” <#add-load-balancer-rule>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:2336
+# 495d9aad900b49139757decdcd3e1fd0
+msgid "Configuring AutoScale"
+msgstr ""
+
+#: ../../managing_networks.rst:2338
+# b63acaedf38e4084922d0ed1738a096c
+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 ""
+
+#: ../../managing_networks.rst:2346
+# 7c16ef30187f4e528f9e696fdb6a13a2
+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 CPU usage is less than 20 percent for 30 minutes."
+msgstr ""
+
+#: ../../managing_networks.rst:2355
+# 80978f0a46614c2388d8939eed46efe8
+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 ""
+
+#: ../../managing_networks.rst:2359
+# 7afb1d7436404cfd95447514fc260dc2
+msgid "AutoScale is supported on NetScaler Release 10 Build 74.4006.e and beyond."
+msgstr ""
+
+#: ../../managing_networks.rst:2361
+# 51240e4bba6843c59ae0708261e1f840
+msgid "**Prerequisites**: Before you configure an AutoScale rule, consider the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:2365
+# 277e8d5e18a44c6a8294bd45157ea092
+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 ""
+
+#: ../../managing_networks.rst:2369
+# 737813324b7c4d178b04393d1999b2bc
+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 ""
+
+#: ../../managing_networks.rst:2373
+# 5143a191f2974e27b72c984bf972c957
+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 ""
+
+#: ../../managing_networks.rst:2380
+# 2fb2c481526e4dacbc3d8658f102c054
+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 `Section 15.16.2, “Configuring SNMP Community String on a RHEL Server” <#configure-snmp-rhel>`__ to configure SNMP on a RHEL machine."
+msgstr ""
+
+#: ../../managing_networks.rst:2392
+# 596a2d14b50c4e298970de7db5c4d19b
+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 ""
+
+#: ../../managing_networks.rst:2400
+# 59583fe0dfc14e2db8bcc23629da18e3
+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 `Updating an AutoScale Configuration <#update-autoscale>`__"
+msgstr ""
+
+#: ../../managing_networks.rst:2407
+# 06073879472f4da9bd08b00591d0cb40
+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 ""
+
+#: ../../managing_networks.rst:2414
+# 019b533b8504424fac6d7aca7a0eef69
+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 ""
+
+#: ../../managing_networks.rst:2419
+# 6cf79ca1b7bb4329a6e3794bd3bb6640
+msgid "**Configuration**: Specify the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:2421
+# 06eb944130db406d86f9d8d4f0f5201f
+msgid "|autoscaleateconfig.png: Configuring AutoScale|"
+msgstr ""
+
+#: ../../managing_networks.rst:2425
+# b20309b302124634a79102396066cfc9
+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 ""
+
+#: ../../managing_networks.rst:2435
+# d1dea3f6825c4703a43d71cdc7414e04
+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 ""
+
+#: ../../managing_networks.rst:2443
+# 977cac13b43548b893cd8d3b9263a434
+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 ""
+
+#: ../../managing_networks.rst:2450
+# 5e6b6bcdd4c24696a9891de65ee28e82
+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 active instance count breaches the Max instance value."
+msgstr ""
+
+#: ../../managing_networks.rst:2454
+# 274bc08434344f26bf553ccdc8e6bbd2
+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 ""
+
+#: ../../managing_networks.rst:2459
+# fa8765ac9c4e4d00b6201068667e656e
+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 ""
+
+#: ../../managing_networks.rst:2464
+# c9355e7ca89d4ccc9d33697630f9c9ce
+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 ""
+
+#: ../../managing_networks.rst:2466
+# 862fa403b3ae4078b2c5fad84f20c904
+msgid "Specify the following scale-up and scale-down policies:"
+msgstr ""
+
+#: ../../managing_networks.rst:2470
+# e1f66b823478416ab7c99e5e853481e1
+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 ""
+
+#: ../../managing_networks.rst:2477
+# de56c7c414204d218c9bea6a7fcf7344
+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 ""
+
+#: ../../managing_networks.rst:2486
+# f5b266cdeebc49f99553c773fbb856ec
+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 ""
+
+#: ../../managing_networks.rst:2492
+# 32828b689ff84e5bb31b059d21354910
+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 ""
+
+#: ../../managing_networks.rst:2498
+# 3cda244cb6b14b7fa2e15a48acb8b16d
+msgid "**Add**: Click Add to add the condition."
+msgstr ""
+
+#: ../../managing_networks.rst:2500
+# 1e835d8f1a6c4e388d57d52753d3a8b8
+msgid "Additionally, if you want to configure the advanced settings, click Show advanced settings, and specify the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:2505
+# 5b7ba989669e4a40afb252e27e1fc081
+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 ""
+
+#: ../../managing_networks.rst:2512
+# 89516f03f6a94946ad2d2947d84e248b
+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 ""
+
+#: ../../managing_networks.rst:2521
+# 8d8f688a8c5f4fc8953fc72bbb6fa60e
+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 ""
+
+#: ../../managing_networks.rst:2529
+# 6fd80b96ba7b43e9986930a454605054
+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 ""
+
+#: ../../managing_networks.rst:2538
+# 29394085111d4034a57c010959b35f52
+msgid "**Disk Offerings**: A predefined set of disk size for primary data storage."
+msgstr ""
+
+#: ../../managing_networks.rst:2543
+# 1f96f023591543e8bd947f88ef3b1050
+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 ""
+
+#: ../../managing_networks.rst:2549
+# 821ca4f7b9eb46fdb6f1e55753fbae4f
+msgid "**SNMP Port**: The port number on which the SNMP agent that run on the provisioned VMs is listening. Default port is 161."
+msgstr ""
+
+#: ../../managing_networks.rst:2554
+# 6383878e27b5486196bb94eda0e78311
+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 ""
+
+#: ../../managing_networks.rst:2561
+# 2d0400bf625c40e5b507fe7a2a386fe3
+msgid "**Apply**: Click Apply to create the AutoScale configuration."
+msgstr ""
+
+#: ../../managing_networks.rst:2563
+# 5571267d05444e769accce5b8bdb476a
+msgid "**Disabling and Enabling an AutoScale Configuration**"
+msgstr ""
+
+#: ../../managing_networks.rst:2565
+# a73ffd802f50465da3992613e2fd33ce
+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 to enable or disable AutoScale.| button."
+msgstr ""
+
+#: ../../managing_networks.rst:2572
+# 93c6d4e3c8c549b6846a3295c5edd0d9
+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 to enable or disable AutoScale.| button."
+msgstr ""
+
+#: ../../managing_networks.rst:2579
+# be28357183b6411393f82cd2c72b5010
+msgid "**Updating an AutoScale Configuration**"
+msgstr ""
+
+#: ../../managing_networks.rst:2581
+# 9773eec58a9e4bb1b7870b150f73375a
+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 ""
+
+#: ../../managing_networks.rst:2586
+# 08d983f7467a4f88b2f0327cb7e70ae6
+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 ""
+
+#: ../../managing_networks.rst:2590
+# 7cbd0d57e0eb44bfa39e96ceb5882808
+msgid "**Runtime Considerations**"
+msgstr ""
+
+#: ../../managing_networks.rst:2594
+# 441f7052cbd94e9da209c4ae56f9188e
+msgid "An administrator should not assign a VM to a load balancing rule which is configured for AutoScale."
+msgstr ""
+
+#: ../../managing_networks.rst:2599
+# f50e274f34b349e4b1a475e82d6b27a0
+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 ""
+
+#: ../../managing_networks.rst:2608
+# 5863fd77df844d8abfc0eb5b54113a9b
+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 ""
+
+#: ../../managing_networks.rst:2615
+# 05ac2f1b191343dfbe9766bc0a12a5eb
+msgid "Global Server Load Balancing Support"
+msgstr ""
+
+#: ../../managing_networks.rst:2617
+# dc875268ac1f420f95d0b8a997b1edac
+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 ""
+
+#: ../../managing_networks.rst:2625
+# df9e3461363043e6aa13a4bf8dc2cf8e
+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 ""
+
+#: ../../managing_networks.rst:2633
+# 66668f01260b42868bfd989b8ec41aec
+msgid "About Global Server Load Balancing"
+msgstr ""
+
+#: ../../managing_networks.rst:2635
+# beef05e70dc142608a052c66fe71bde8
+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 accessing a resource in the event of a failure, or to provide a means of shifting traffic easily to simplify maintenance, or both."
+msgstr ""
+
+#: ../../managing_networks.rst:2646
+# 6f6103c3a53e4f1cb222b9afd2dcb902
+msgid "Components of GSLB"
+msgstr ""
+
+#: ../../managing_networks.rst:2648
+# 8b8a51e12bdd4107865ac3a367c5d94c
+msgid "A typical GSLB environment is comprised of the following components:"
+msgstr ""
+
+#: ../../managing_networks.rst:2652
+# 24d395f518ba4bc6acbde4a7f3524765
+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 ""
+
+#: ../../managing_networks.rst:2662
+# 3adc636819414d66a23bac457844c029
+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 ""
+
+#: ../../managing_networks.rst:2673
+# 7b6395ad205c425b996b1e5add0ff8d5
+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 a FQDN DNS name."
+msgstr ""
+
+#: ../../managing_networks.rst:2684
+# e3e856d634e6456c93aff9131bbe3741
+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 balancing or content switching virtual server, the client sends the request to that virtual server’s VIP address."
+msgstr ""
+
+#: ../../managing_networks.rst:2696
+# c5a7dc8ecc384cbc9122a87ac691fb60
+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 ""
+
+#: ../../managing_networks.rst:2703
+# f5267941251d49dab69cee3c751f2a73
+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 and port."
+msgstr ""
+
+#: ../../managing_networks.rst:2713
+# cc2d753e713a478a81de5da6e6c98ed0
+msgid "How Does GSLB Works in CloudStack?"
+msgstr ""
+
+#: ../../managing_networks.rst:2715
+# c98da292c6334f3ca648a149ebdc8824
+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 xyztelco cloud. For that purpose, they launch two instances each in both the zones: VM1 and VM2 in Zone-1 and VM5 and VM6 in Zone-2. Tenant-A acquires a public IP, IP-1 in Zone-1, and configures a load balancer rule to load balance the traffic between VM1 and VM2 instances. CloudStack orchestrates setting up a virtual server on the LB service provider in Zone-1. Virtual server 1 that is set up on the LB service provider in Zone-1 represents a publicly accessible virtual server that client reaches at IP-1. The client traffic to virtual server 1 at IP-1 will be load balanced across VM1 and VM2 instances."
+msgstr ""
+
+#: ../../managing_networks.rst:2732
+# ffa6856e30584d38a6f24079acff4661
+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 instances. At this point Tenant-A has the service enabled in both the zones, but has no means to set up a disaster recovery plan if one of the zone fails. Additionally, there is no way for Tenant-A to load balance the traffic intelligently to one of the zones based on load, proximity and so on. The cloud administrator of xyztelco provisions a GSLB service provider to both the zones. A GSLB provider is typically an ADC that has the ability to act as an ADNS (Authoritative Domain Name Server) and has the mechanism to monitor health of virtual servers both at local and remote sites. The cloud admin enables GSLB as a service to the tenants that use zones 1 and 2."
+msgstr ""
+
+#: ../../managing_networks.rst:2750
+# 3a73c9ef3d7f4ebeb3911bd3563d8387
+msgid "|gslb.png: GSLB architecture|"
+msgstr ""
+
+#: ../../managing_networks.rst:2752
+# 6e23027e34d34f4a936236b981c7bcf6
+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 start monitoring the health of virtual server 1 and 2 in Zone-1. CloudStack will also orchestrate setting up GSLB virtual server 2 on GSLB service provider at Zone-2. CloudStack will bind virtual server 1 of Zone-1 and virtual server 2 of Zone-2 to GLSB virtual server 2. GSLB virtual server 2 is configured to start monitoring the health of virtual server 1 and 2. CloudStack will bind the domain A.xyztelco.com to both the GSLB virtual server 1 and 2. At this point, Tenant-A service will be globally reachable at A.xyztelco.com. The private DNS server for the domain xyztelcom.com is configured by the admin out-of-band to resolve the domain A.xyztelco.com to the GSLB providers at both the zones, which are configured as ADNS for the domain A.xyztelco.com. A client when sends a DNS request to resolve A.xyztelcom.com, will eventually get DNS delegation to the address of GSLB providers at zone 1 and 2. A client DNS request will be received by the GSLB provider. The GSLB provider, depending on the domain for which it needs to resolve, will pick up the GSLB virtual server associated with the domain. Depending on the health of the virtual servers being load balanced, DNS request for the domain will be resolved to the public IP associated with the selected virtual server."
+msgstr ""
+
+#: ../../managing_networks.rst:2780
+# 3151e8ac0c36496686ae21c2163aa04b
+msgid "Configuring GSLB"
+msgstr ""
+
+#: ../../managing_networks.rst:2782
+# f59f84c71a354830be5b56db8ff8dac9
+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 servers. Finally, bind the domain to the GSLB virtual servers. The GSLB configurations on the two appliances at the two different zones are identical, although each sites load-balancing configuration is specific to that site."
+msgstr ""
+
+#: ../../managing_networks.rst:2794
+# 99bb0093d2e94a7a86b614949e37a273
+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 ""
+
+#: ../../managing_networks.rst:2799
+# 1885a58567b74c5fb1d24b27d68606d1
+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 ""
+
+#: ../../managing_networks.rst:2804
+# 3a7b005c2a8f4371abec8d107ec7567a
+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 ""
+
+#: ../../managing_networks.rst:2810
+# ad1e67d3c4ba4a4dbcc2c9f9f8312a2e
+msgid "Configuring a standard load balancing setup."
+msgstr ""
+
+#: ../../managing_networks.rst:2814
+# cf2cce5b485d4677862f4dfa37cca3e2
+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 ""
+
+#: ../../managing_networks.rst:2820
+# 28a6a8facbb74d048b3446698e7c3a28
+msgid "Configure a GSLB site with site name formed from the domain name details."
+msgstr ""
+
+#: ../../managing_networks.rst:2823
+# 23d7169514304f03b20f0dcdd7d85560
+msgid "Configure a GSLB site with the site name formed from the domain name."
+msgstr ""
+
+#: ../../managing_networks.rst:2826
+# abdfa71791a446fa8c4807a164a963ca
+msgid "As per the example given above, the site names are A.xyztelco.com and B.xyztelco.com."
+msgstr ""
+
+#: ../../managing_networks.rst:2829
+# 0c7009166c264415a54730db14b1aa5d
+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 ""
+
+#: ../../managing_networks.rst:2834
+# c87d7d53d0a94969ada1b51cdefa6a1d
+msgid "Configure a GSLB virtual server."
+msgstr ""
+
+#: ../../managing_networks.rst:2836
+# e8a2089685594e79ad6db6881d235b51
+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 ""
+
+#: ../../managing_networks.rst:2841
+# 418139183cf14fc4bb75d67dbd5675ca
+msgid "Configure a GSLB service for each virtual server."
+msgstr ""
+
+#: ../../managing_networks.rst:2843
+# c3924a1ee80541e59d938ffb33b3b2fe
+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 ""
+
+#: ../../managing_networks.rst:2848
+# 4d37328cd36748f68e4c010cb5530462
+msgid "Bind the GSLB services to the GSLB virtual server."
+msgstr ""
+
+#: ../../managing_networks.rst:2850
+# 0f19756a99664403b711b3b295586263
+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 ""
+
+#: ../../managing_networks.rst:2855
+# 4870e604797d45d6954809f1324494d4
+msgid "Bind domain name to GSLB virtual server. Domain name is obtained from the domain details."
+msgstr ""
+
+#: ../../managing_networks.rst:2858
+# 978097bf4e2743f2a424be8138ae67b8
+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 ""
+
+#: ../../managing_networks.rst:2863
+# 60ee91d3c6484a30807687dd847bc57b
+msgid "In each zone that are participating in GSLB, add GSLB-enabled NetScaler device."
+msgstr ""
+
+#: ../../managing_networks.rst:2866
+# 454bfde53cc944eb8ca917bf70b648df
+msgid "For more information, see `Section 15.17.2.2, “Enabling GSLB in NetScaler” <#enable-glsb-ns>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:2869
+# fd694dfa87e64107ade55d98d13c9dd2
+msgid "As a domain administrator/ user perform the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:2873
+# b2a0dae4dd9f46918c3e14aa88ac0f76
+msgid "Add a GSLB rule on both the sites."
+msgstr ""
+
+#: ../../managing_networks.rst:2875
+# 1284b054b7634c8caf28360652e7aadf
+msgid "See `Section 15.17.2.3, “Adding a GSLB Rule” <#gslb-add>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:2879
+# a4c1035be3ae4ba7ae258d14c19fa1df
+msgid "Assign load balancer rules."
+msgstr ""
+
+#: ../../managing_networks.rst:2881
+# 63a3c42a03374ba783bdd3d8e4c5028e
+msgid "See `Section 15.17.2.4, “Assigning Load Balancing Rules to GSLB” <#assign-lb-gslb>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:2889
+# c09c96f49f1a421389db422ce761a1dc
+msgid "The GSLB functionality is supported both Basic and Advanced zones."
+msgstr ""
+
+#: ../../managing_networks.rst:2893
+# 99047554b3fd432390156996189c06ff
+msgid "GSLB is added as a new network service."
+msgstr ""
+
+#: ../../managing_networks.rst:2897
+# 349a81ed861746768a4a0691ccaeab8f
+msgid "GSLB service provider can be added to a physical network in a zone."
+msgstr ""
+
+#: ../../managing_networks.rst:2901
+# 6ab7794f701a4df59fc243ddc58f0b4d
+msgid "The admin is allowed to enable or disable GSLB functionality at region level."
+msgstr ""
+
+#: ../../managing_networks.rst:2906
+# 3d725c2417e04077a8bd810b305cc12d
+msgid "The admin is allowed to configure a zone as GSLB capable or enabled."
+msgstr ""
+
+#: ../../managing_networks.rst:2908
+# af63547d61ae47bc8806fe8dec44724a
+msgid "A zone shall be considered as GSLB capable only if a GSLB service provider is provisioned in the zone."
+msgstr ""
+
+#: ../../managing_networks.rst:2913
+# bd3583e6473d458e8903768b80ac420d
+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 ""
+
+#: ../../managing_networks.rst:2919
+# d3eae7bb192b4cf5999d1cad4530ce6c
+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 ""
+
+#: ../../managing_networks.rst:2924
+# 722a4c917dfc4316a8a5ee4e1d2473f0
+msgid "The users can load balance traffic across the availability zones in the same region or different regions."
+msgstr ""
+
+#: ../../managing_networks.rst:2929
+# f3e00c0dbac94afaa7fc338683627630
+msgid "The admin can configure DNS name for the entire cloud."
+msgstr ""
+
+#: ../../managing_networks.rst:2933
+# 381667b65f5b41c3ba49502ed236dee2
+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 ""
+
+#: ../../managing_networks.rst:2937
+# c2b3095096774c50860988ec9732c71f
+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 ""
+
+#: ../../managing_networks.rst:2946
+# 9cf64fad7b7949f98496453cb30e3f90
+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 ""
+
+#: ../../managing_networks.rst:2951
+# 2c50d1ce8e39415d907de0a6d851de14
+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 ""
+
+#: ../../managing_networks.rst:2957
+# 29df9cd710bd46a0a9df9f49eb468dd5
+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 ""
+
+#: ../../managing_networks.rst:2961
+# 10872c3a649d420e9f119e3bbed98213
+msgid "Statistics is collected from each GSLB virtual server."
+msgstr ""
+
+#: ../../managing_networks.rst:2964
+# dd79dc700b3743df9f52e687a9db8068
+msgid "Enabling GSLB in NetScaler"
+msgstr ""
+
+#: ../../managing_networks.rst:2966
+# 156a972ed59b40038a4636321d763dae
+msgid "In each zone, add GSLB-enabled NetScaler device for load balancing."
+msgstr ""
+
+#: ../../managing_networks.rst:2970
+# c7e4943746f845df836880e582050b87
+msgid "Log in as administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../managing_networks.rst:2978
+# b9463a89aa57467d83d9432154c10a77
+msgid "In Zones, click View More."
+msgstr ""
+
+#: ../../managing_networks.rst:2986
+# f1595ba6ced742f9bd9ef6be9b4b2e79
+msgid "Click the Physical Network tab, then click the name of the physical network."
+msgstr ""
+
+#: ../../managing_networks.rst:2991
+# 63b81a3cbb9742a5bbe5dd55ba85ecff
+msgid "In the Network Service Providers node of the diagram, click Configure."
+msgstr ""
+
+#: ../../managing_networks.rst:2994
+# 508b40545cbc4132b2cf1e4128540e5e
+msgid "You might have to scroll down to see this."
+msgstr ""
+
+#: ../../managing_networks.rst:2998
+# 53115bf37dda43f8b8f3536dd4dd568b
+msgid "Click NetScaler."
+msgstr ""
+
+#: ../../managing_networks.rst:3002
+# b5b0d0cc48334232a6a56069d7adaa9f
+msgid "Click Add NetScaler device and provide the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:3004
+# ed5c0c0442f9456cb72dbedd1a84e668
+msgid "For NetScaler:"
+msgstr ""
+
+#: ../../managing_networks.rst:3008
+# 538c95af821f4027b75d4dc232db3305
+msgid "**IP Address**: The IP address of the SDX."
+msgstr ""
+
+#: ../../managing_networks.rst:3012
+# f90935d4f5d4451cbfb5cb650901d339
+msgid "**Username/Password**: The authentication credentials to access the device. CloudStack uses these credentials to access the device."
+msgstr ""
+
+#: ../../managing_networks.rst:3018
+# d5079aa5e4a549ada0c3aa62c5f2a6b8
+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 ""
+
+#: ../../managing_networks.rst:3025
+# 927bd20253b24539a81a89816522b622
+msgid "**Public interface**: Interface of device that is configured to be part of the public network."
+msgstr ""
+
+#: ../../managing_networks.rst:3030
+# a9b26fd6edb640ab96c686fb82e63174
+msgid "**Private interface**: Interface of device that is configured to be part of the private network."
+msgstr ""
+
+#: ../../managing_networks.rst:3035
+# f59521a2c8eb45b6b90edf7253c53f3f
+msgid "**GSLB service**: Select this option."
+msgstr ""
+
+#: ../../managing_networks.rst:3039
+# f279e0631abf48efbc96b3cea07c0f7e
+msgid "**GSLB service Public IP**: The public IP address of the NAT translator for a GSLB service that is on a private network."
+msgstr ""
+
+#: ../../managing_networks.rst:3044
+# 06437d72b1314c92865ada3febe44c64
+msgid "**GSLB service Private IP**: The private IP of the GSLB service."
+msgstr ""
+
+#: ../../managing_networks.rst:3048
+# c1696819f3884157a9733431fe8f5347
+msgid "**Number of Retries**. Number of times to attempt a command on the device before considering the operation failed. Default is 2."
+msgstr ""
+
+#: ../../managing_networks.rst:3053
+# 37c94cc408494e18a54ef8e730b7e3d3
+msgid "**Capacity**: The number of networks the device can handle."
+msgstr ""
+
+#: ../../managing_networks.rst:3057
+# 3cf0408da21d4c4080772f511c283988
+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 ""
+
+#: ../../managing_networks.rst:3067
+# 2f16286d06b34cfbb0c778f84f978767
+msgid "Adding a GSLB Rule"
+msgstr ""
+
+#: ../../managing_networks.rst:3071
+#: ../../managing_networks.rst:3140
+# 039473a14f4b4214ba12771983f2fc83
+# f23106a7198949aa85bdb7abe8be1ff4
+msgid "Log in to the CloudStack UI as a domain administrator or user."
+msgstr ""
+
+#: ../../managing_networks.rst:3075
+#: ../../managing_networks.rst:3144
+# f297c9cec43e40e2ab81e6dcf9c29486
+# 6831e687e51f441493ff214593172f42
+msgid "In the left navigation pane, click Region."
+msgstr ""
+
+#: ../../managing_networks.rst:3079
+#: ../../managing_networks.rst:3148
+# 1671ccbb5a484e7cb4675d75434115b1
+# 7ee2d894c2e44271b0b7cf58a1398b29
+msgid "Select the region for which you want to create a GSLB rule."
+msgstr ""
+
+#: ../../managing_networks.rst:3083
+#: ../../managing_networks.rst:3152
+# 6e5c6390b5cb4211962d11c2860e768e
+# 18b5fb7710ae4f039c9f3248fc046b59
+msgid "In the Details tab, click View GSLB."
+msgstr ""
+
+#: ../../managing_networks.rst:3087
+# 3bd105d046e04354911f2b627f21d5dd
+msgid "Click Add GSLB."
+msgstr ""
+
+#: ../../managing_networks.rst:3089
+# 77c33d27873f48b8bb209ab50d2a73ac
+msgid "The Add GSLB page is displayed as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:3091
+# 11522ea2b2de46708f6b45158dfcf5df
+msgid "|gslb-add.png: adding a gslb rule|"
+msgstr ""
+
+#: ../../managing_networks.rst:3099
+# df1dc1cd07d8438d9e684fd70afe8e7a
+msgid "**Name**: Name for the GSLB rule."
+msgstr ""
+
+#: ../../managing_networks.rst:3103
+# 9d0c2f980b4f48f7b7d5153d414e2bc0
+msgid "**Description**: (Optional) A short description of the GSLB rule that can be displayed to users."
+msgstr ""
+
+#: ../../managing_networks.rst:3108
+# bd6458bb4ab147b9b5a5483035bff382
+msgid "**GSLB Domain Name**: A preferred domain name for the service."
+msgstr ""
+
+#: ../../managing_networks.rst:3112
+# 8ea3f203884e47b6a1d8d90fe8125bf0
+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 ""
+
+#: ../../managing_networks.rst:3118
+# 4d8d6961170041cfada0392ecb570560
+msgid "**Service Type**: The transport protocol to use for GSLB. The options are TCP and UDP."
+msgstr ""
+
+#: ../../managing_networks.rst:3123
+# 77dcf4c2f0024309b529be408e435cee
+msgid "**Domain**: (Optional) The domain for which you want to create the GSLB rule."
+msgstr ""
+
+#: ../../managing_networks.rst:3128
+# fcaa38e31d864b25b64102b670470c2c
+msgid "**Account**: (Optional) The account on which you want to apply the GSLB rule."
+msgstr ""
+
+#: ../../managing_networks.rst:3136
+# 76446b2d9e054665bbca7c01ac0559fa
+msgid "Assigning Load Balancing Rules to GSLB"
+msgstr ""
+
+#: ../../managing_networks.rst:3156
+# 1be9eb92d540481b97cd2f99cc3ab9d6
+msgid "Select the desired GSLB."
+msgstr ""
+
+#: ../../managing_networks.rst:3160
+# b437092b9f2a488585dbe73e5068870b
+msgid "Click view assigned load balancing."
+msgstr ""
+
+#: ../../managing_networks.rst:3164
+# eda19bddac444d22aaf6944b81ac6574
+msgid "Click assign more load balancing."
+msgstr ""
+
+#: ../../managing_networks.rst:3168
+# 44acd11aec3d42869b12198753256ae7
+msgid "Select the load balancing rule you have created for the zone."
+msgstr ""
+
+#: ../../managing_networks.rst:3175
+# 77eb5dcff40842b1b2e565776e642fa5
+msgid "Known Limitation"
+msgstr ""
+
+#: ../../managing_networks.rst:3177
+# eee28dc26a8c43daa149baee5774cd3e
+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 ""
+
+#: ../../managing_networks.rst:3182
+# 6ce352ece3ec4e588cb58d78a6a43ab9
+msgid "Guest IP Ranges"
+msgstr ""
+
+#: ../../managing_networks.rst:3184
+# b9ae2154009d4c7c8135987e8ac86e2c
+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 ""
+
+#: ../../managing_networks.rst:3189
+# de46e5574bf54dd68d71bdd2b1dd9a8b
+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 `Section 15.10, “About Multiple IP Ranges” <#multiple-ip-range>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:3196
+# b24a8efdf2824070a8500affcc044a77
+msgid "Acquiring a New IP Address"
+msgstr ""
+
+#: ../../managing_networks.rst:3224
+# 6392b71aa674434c8fea3a1269449799
+msgid "If you want Portable IP click Yes in the confirmation dialog. If you want a normal Public IP click No."
+msgstr ""
+
+#: ../../managing_networks.rst:3227
+# 1b67f1c2681f421e95e01179c36b4c0b
+msgid "For more information on Portable IP, see `Section 15.12, “Portable IPs” <#portable-ip>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:3235
+# 97d72bd6a40a40e7bd59c0c736a8bbdd
+msgid "Releasing an IP Address"
+msgstr ""
+
+#: ../../managing_networks.rst:3237
+# f52a271b737d4215a2e21b2c934efdd4
+msgid "When the last rule for an IP address is removed, you can release that IP address. The IP address still belongs to the VPC; however, it can be picked up for any guest network again."
+msgstr ""
+
+#: ../../managing_networks.rst:3259
+# 656f51251c854bb6a971b2cb29b0d8ef
+msgid "Click the IP address you want to release."
+msgstr ""
+
+#: ../../managing_networks.rst:3263
+# 2572dd822bef4a2f955e7507de6a2171
+msgid "Click the Release IP button. |ReleaseIPButton.png: button to release an IP|"
+msgstr ""
+
+#: ../../managing_networks.rst:3267
+#: ../../managing_networks.rst:3838
+#: ../../managing_networks.rst:4285
+#: ../../managing_networks.rst:4385
+#: ../../managing_networks.rst:4579
+#: ../../managing_networks.rst:5185
+#: ../../managing_networks.rst:5443
+#: ../../managing_networks.rst:5768
+#: ../../managing_networks.rst:5855
+#: ../../managing_networks.rst:5946
+#: ../../managing_networks.rst:6188
+#: ../../managing_networks.rst:6580
+# 5b2ef9957d5c4f35a32f9d7da23e6693
+# 41297f054dbd4ab0a958c0998f5d7ffd
+# 2ab2cc311faf4a23bcbd99703f0f47e1
+# d5758556343045dd918e7f592bbba40e
+# 07b2dc015092473aa0a048a6cc59b7b8
+# 26b03a50edbe4d8bb41144c0cada25e2
+# 127f42037f3448d38c791df3fb08fec1
+# 6e8aef87be834395857821e832eedc81
+# 75e095f3e2b343a2a5ebf18c29c3c74e
+# a4224fe4d3e84991adba7f4f79e22ccd
+# 37046dfed9524c6689ce685c5fe137b8
+# 1491471208484e0794022798a18c6235
+msgid "Static NAT"
+msgstr ""
+
+#: ../../managing_networks.rst:3269
+# 8b9ec9bf10d04ae79f278146e90a9d9b
+msgid "A static NAT rule maps a public IP address to the private IP address of a VM in order to allow Internet traffic into the VM. The public IP address always remains the same, which is why it is called “static” NAT. This section tells how to enable or disable static NAT for a particular IP address."
+msgstr ""
+
+#: ../../managing_networks.rst:3276
+# c431000325b74754a499d98af7351495
+msgid "Enabling or Disabling Static NAT"
+msgstr ""
+
+#: ../../managing_networks.rst:3278
+#: ../../managing_networks.rst:5905
+# b2c066da76814877b47541a473f572fb
+# 3f56828c583c46ad81eaedeff63fb850
+msgid "If port forwarding rules are already in effect for an IP address, you cannot enable static NAT to that IP."
+msgstr ""
+
+#: ../../managing_networks.rst:3281
+#: ../../managing_networks.rst:5908
+# ab68fbb3395e429fa804a3969d8011a5
+# f9f86036dd7b4dd391c93c88952259d1
+msgid "If a guest VM is part of more than one network, static NAT rules will function only if they are defined on the default network."
+msgstr ""
+
+#: ../../managing_networks.rst:3302
+#: ../../managing_networks.rst:3378
+# 3c704e04efc744568700070163b3ca1d
+# fa28626438294e07bd64b0c07f6bb8a2
+msgid "Click the IP address you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:3306
+# 5ad8bdba63064885a50259f19f0a3650
+msgid "Click the Static NAT |EnableNATButton.png: button to enable NAT| button."
+msgstr ""
+
+#: ../../managing_networks.rst:3309
+# 5608c079e4984a898941e97d9040e080
+msgid "The button toggles between Enable and Disable, depending on whether static NAT is currently enabled for the IP address."
+msgstr ""
+
+#: ../../managing_networks.rst:3314
+# c44f31d84d4946bba279c07ffae37af3
+msgid "If you are enabling static NAT, a dialog appears where you can choose the destination VM and click Apply."
+msgstr ""
+
+#: ../../managing_networks.rst:3318
+# 0239068895f846728ff792196d9e8c78
+msgid "IP Forwarding and Firewalling"
+msgstr ""
+
+#: ../../managing_networks.rst:3320
+# 38b50d6982c14a78b97c1004a1d32b97
+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 ""
+
+#: ../../managing_networks.rst:3323
+# 4374970c184442e1bff7de64f1a19a7b
+msgid "To allow outgoing traffic, follow the procedure in `Section 15.22.2, “Egress Firewall Rules in an Advanced Zone” <#egress-firewall-rule>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:3326
+# 4cb1f00da457462d9550d7a7750f2313
+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 ""
+
+#: ../../managing_networks.rst:3335
+# 30b73ffad3e84ae2ac5dcec10260b433
+msgid "Firewall Rules"
+msgstr ""
+
+#: ../../managing_networks.rst:3337
+# 65002cba7c554a759449b2c27f7e9931
+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 ""
+
+#: ../../managing_networks.rst:3343
+# 0eadbb8127ba4f50ad1f3a2ac2b73049
+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 `Section 15.15.2, “Adding a Security Group” <#add-security-group>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:3348
+# 47591452f5c348b7a4836500eaeeb54f
+msgid "In an advanced zone, you can also create egress firewall rules by using the virtual router. For more information, see `Section 15.22.2, “Egress Firewall Rules in an Advanced Zone” <#egress-firewall-rule>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:3352
+# d9b6ac1930d14ffaa3eae10de83b88f2
+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 ""
+
+#: ../../managing_networks.rst:3358
+# 41479731d8d84d99a6aa8925a91d371b
+msgid "To create a firewall rule:"
+msgstr ""
+
+#: ../../managing_networks.rst:3382
+# 379f460faa18445583d749503ad81606
+msgid "Click the Configuration tab and fill in the following values."
+msgstr ""
+
+#: ../../managing_networks.rst:3386
+# 7923d613a47543f2a046a93f3a08a992
+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 ""
+
+#: ../../managing_networks.rst:3393
+# ff573c7c40d94c24a43dc4e21ed8cc30
+msgid "**Protocol**. The communication protocol in use on the opened port(s)."
+msgstr ""
+
+#: ../../managing_networks.rst:3398
+# 14466f1425f9488c824bc5507b812a10
+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 ""
+
+#: ../../managing_networks.rst:3404
+# eff1095b7f204f83bfca43d956620036
+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 ""
+
+#: ../../managing_networks.rst:3414
+# c334f1f90dbf49c4935f21d4c1bb417c
+msgid "Egress Firewall Rules in an Advanced Zone"
+msgstr ""
+
+#: ../../managing_networks.rst:3416
+# 939aa6e067b64d47a83d181a3e4e5527
+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 rules are removed the default policy, Block, is applied."
+msgstr ""
+
+#: ../../managing_networks.rst:3428
+# 7a04d621e9684c64a589eb43631ba804
+msgid "Consider the following scenarios to apply egress firewall rules:"
+msgstr ""
+
+#: ../../managing_networks.rst:3432
+# 774794905f1a490fbaadf61a60da50fc
+msgid "Egress firewall rules are supported on Juniper SRX and virtual router."
+msgstr ""
+
+#: ../../managing_networks.rst:3437
+# 46f8243d01b443d09201acc237d75fc9
+msgid "The egress firewall rules are not supported on shared networks."
+msgstr ""
+
+#: ../../managing_networks.rst:3441
+# f88ff0e199cc453ea42eec0dfc9125b1
+msgid "Allow the egress traffic from specified source CIDR. The Source CIDR is part of guest network CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:3446
+# d8800840b30d44929ddbb3b604c97f02
+msgid "Allow the egress traffic with protocol TCP,UDP,ICMP, or ALL."
+msgstr ""
+
+#: ../../managing_networks.rst:3450
+# 26294a9e847940889657b436b3a4aa23
+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 ""
+
+#: ../../managing_networks.rst:3455
+# c0afd204dff547fb87834d7abc9c1f8e
+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 ""
+
+#: ../../managing_networks.rst:3460
+# 850dd34086424c9ab68601f13834bcd2
+msgid "Configuring an Egress Firewall Rule"
+msgstr ""
+
+#: ../../managing_networks.rst:3472
+# 3615eb46ce214f7d9cbf957a06371666
+msgid "In Select view, choose Guest networks, then click the Guest network you want."
+msgstr ""
+
+#: ../../managing_networks.rst:3477
+# 359f42a9094342b29e083f461a84405b
+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 ""
+
+#: ../../managing_networks.rst:3481
+# f203654bfaa44a6989bda0673da8a470
+msgid "|egress-firewall-rule.png: adding an egress firewall rule|"
+msgstr ""
+
+#: ../../managing_networks.rst:3485
+# e1ee94ade2e54545b51b809a12f729dd
+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 ""
+
+#: ../../managing_networks.rst:3493
+# 142d121ba8884e97abf630ab11c3ba47
+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 ""
+
+#: ../../managing_networks.rst:3500
+# a6aa5a49dfb948f9b0f88c0b723666df
+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 ""
+
+#: ../../managing_networks.rst:3506
+# bdf38163ee3d40d1905ccf2ac8827421
+msgid "**ICMP Type, ICMP Code**: (ICMP only) The type of message and error code that are sent."
+msgstr ""
+
+#: ../../managing_networks.rst:3514
+# 4fd631620dc649139065e335358cbd24
+msgid "Configuring the Default Egress Policy"
+msgstr ""
+
+#: ../../managing_networks.rst:3516
+# 19008ef0cc514c859de0de2daede053c
+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 ""
+
+#: ../../managing_networks.rst:3524
+# 79bc5b57e2f94789bdff8bbfac2ddcfb
+msgid "You have two options: Allow and Deny."
+msgstr ""
+
+#: ../../managing_networks.rst:3527
+# 1224fcbce5c74fe3b947356b896ca579
+msgid "Allow"
+msgstr ""
+
+#: ../../managing_networks.rst:3529
+# e2a646bdb2d74e4db9d2599d28f6235a
+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 ""
+
+#: ../../managing_networks.rst:3536
+#: ../../managing_networks.rst:5146
+#: ../../managing_networks.rst:5147
+# 749247337d834c6c9277066a5d52c328
+# 8779b4214ba9455abd8c51e7029da31a
+# e800ddb4ba3d4858ba5fbf7c30acd2e4
+msgid "Deny"
+msgstr ""
+
+#: ../../managing_networks.rst:3538
+# 3a06b12ffe614d1cab452a989a8f917f
+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 ""
+
+#: ../../managing_networks.rst:3545
+# 6196e56e021042f4a3ebd91573fbbf60
+msgid "This feature is supported only on virtual router and Juniper SRX."
+msgstr ""
+
+#: ../../managing_networks.rst:3549
+# 7bdc8fc3675346f1a13f9c19d80abfd7
+msgid "Create a network offering with your desirable default egress policy:"
+msgstr ""
+
+#: ../../managing_networks.rst:3553
+# 132ba5854a684a0484908e19f74b3d44
+msgid "Log in with admin privileges to the CloudStack UI."
+msgstr ""
+
+#: ../../managing_networks.rst:3557
+# 71eec5bf534f4946b6c4daaf8df613a6
+msgid "In the left navigation bar, click Service Offerings."
+msgstr ""
+
+#: ../../managing_networks.rst:3561
+# 89d1b1ad418a45b087b1a5650dfbb68b
+msgid "In Select Offering, choose Network Offering."
+msgstr ""
+
+#: ../../managing_networks.rst:3565
+#: ../../managing_networks.rst:6072
+#: ../../managing_networks.rst:6376
+# 14b63d7663f845a785bdd4d17da6c813
+# ca405e366b0a4757b0f24381859548f3
+# e9ca1c0eaa53479c9b838d602582aa03
+msgid "Click Add Network Offering."
+msgstr ""
+
+#: ../../managing_networks.rst:3569
+# a3f5cfaea903420c9a12c152a3293b17
+msgid "In the dialog, make necessary choices, including firewall provider."
+msgstr ""
+
+#: ../../managing_networks.rst:3574
+# ce35e9aadd4542cbacf3656f44f89af7
+msgid "In the Default egress policy field, specify the behaviour."
+msgstr ""
+
+#: ../../managing_networks.rst:3582
+# 23199bdde5f24a939b68fb46fd1019fb
+msgid "Create an isolated network by using this network offering."
+msgstr ""
+
+#: ../../managing_networks.rst:3584
+# 2b39e12e5b3d4d39a933c682cc18b149
+msgid "Based on your selection, the network will have the egress public traffic blocked or allowed."
+msgstr ""
+
+#: ../../managing_networks.rst:3588
+# 2e4756b361a14c97a83a29b5f8d1a311
+msgid "Port Forwarding"
+msgstr ""
+
+#: ../../managing_networks.rst:3590
+# a08ae5e9620d44ff84ce14445856b2c3
+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 ""
+
+#: ../../managing_networks.rst:3598
+# 878cdf1503f94e3187e805b44534fed9
+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 ""
+
+#: ../../managing_networks.rst:3603
+# ca75695902264086b479704a64871a64
+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 ""
+
+#: ../../managing_networks.rst:3607
+# 550c9e8578014be1bde72e80f78d199c
+msgid "To set up port forwarding:"
+msgstr ""
+
+#: ../../managing_networks.rst:3615
+# 1579f539fb6d428486e2cb9316570a6b
+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 ""
+
+#: ../../managing_networks.rst:3621
+# baee90c3d614427590853d7141e1ee1b
+msgid "Add one or more VM instances to CloudStack."
+msgstr ""
+
+#: ../../managing_networks.rst:3625
+# aa5921d82f6a429ca3d83e2d9e3991cd
+msgid "In the left navigation bar, click Network."
+msgstr ""
+
+#: ../../managing_networks.rst:3629
+# 6f69e80b5b984c18a3a7652157412174
+msgid "Click the name of the guest network where the VMs are running."
+msgstr ""
+
+#: ../../managing_networks.rst:3633
+# aaa0315049f346cb878ebb96c9c25a9c
+msgid "Choose an existing IP address or acquire a new IP address. See `Section 15.19, “Acquiring a New IP Address” <#acquire-new-ip-address>`__. Click the name of the IP address in the list."
+msgstr ""
+
+#: ../../managing_networks.rst:3640
+# 2b948665b23443059e227f2a987a4af4
+msgid "Click the Configuration tab."
+msgstr ""
+
+#: ../../managing_networks.rst:3644
+#: ../../managing_networks.rst:6621
+# ef12d2f0ebca484fbec9fe3b4ea476ce
+# 86470a41e0e143c8abee911f793f5139
+msgid "In the Port Forwarding node of the diagram, click View All."
+msgstr ""
+
+#: ../../managing_networks.rst:3652
+# 70b067742c7e494faa545e59e67e509f
+msgid "**Public Port**. The port to which public traffic will be addressed on the IP address you acquired in the previous step."
+msgstr ""
+
+#: ../../managing_networks.rst:3657
+# 3c48fdadff09491b8ccdfa491ef23b13
+msgid "**Private Port**. The port on which the instance is listening for forwarded public traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:3662
+# 9b1ee2382ca242bea410d9e0fec0de21
+msgid "**Protocol**. The communication protocol in use between the two ports"
+msgstr ""
+
+#: ../../managing_networks.rst:3670
+# b5fdf68205af49fe949bb74f27cb03ef
+msgid "IP Load Balancing"
+msgstr ""
+
+#: ../../managing_networks.rst:3672
+# f4415093dc35468c97c273710e3fd019
+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 ""
+
+#: ../../managing_networks.rst:3678
+#: ../../managing_networks.rst:6261
+#: ../../managing_networks.rst:6532
+# 9643d81461b54c18b510cec02c55b76a
+# 8ff79894623b4f75ad7b797363bc1802
+# f5133113ba364c81bb4607616c3e51b2
+msgid "Round-robin"
+msgstr ""
+
+#: ../../managing_networks.rst:3682
+# 1599b1d2a49941089fba2c32b3639b28
+msgid "Least connection"
+msgstr ""
+
+#: ../../managing_networks.rst:3686
+# a23492e21cb742b2b97b33f4b5ab151f
+msgid "Source IP"
+msgstr ""
+
+#: ../../managing_networks.rst:3688
+# 728ff8a92c5a4fa4875aff65b6a6e20a
+msgid "This is similar to port forwarding but the destination may be multiple IP addresses."
+msgstr ""
+
+#: ../../managing_networks.rst:3692
+# d5e9852ee80440fe9204fac406dd593d
+msgid "DNS and DHCP"
+msgstr ""
+
+#: ../../managing_networks.rst:3694
+# 0e9e9564f8514da08c6206315a3eaa34
+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 ""
+
+#: ../../managing_networks.rst:3699
+# b8ff527b8b13466885b0c515030f73dd
+msgid "Remote Access VPN"
+msgstr ""
+
+#: ../../managing_networks.rst:3701
+# c381ec096f69422e8176e92e2f15b737
+msgid "CloudStack account owners can create virtual private networks (VPN) to access their virtual machines. If the guest network is instantiated from a network offering that offers the Remote Access VPN service, the virtual router (based on the System VM) is used to provide the service. CloudStack provides a L2TP-over-IPsec-based remote access VPN service to guest virtual networks. Since each network gets its own virtual router, VPNs are not shared across the networks. VPN clients native to Windows, Mac OS X and iOS can be used to connect to the guest networks. The account owner can create and manage users for their VPN. CloudStack does not use its account database for this purpose but uses a separate table. The VPN user database is shared across all the VPNs created by the account owner. All VPN users get access to all VPNs created by the account owner."
+msgstr ""
+
+#: ../../managing_networks.rst:3715
+# 3bb8afa8e0d549448cda76518414eb07
+msgid "Make sure that not all traffic goes through the VPN. That is, the route installed by the VPN should be only for the guest network and not for all traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:3719
+# d295f3aefec94637a6b5ecbd5c09110a
+msgid "**Road Warrior / Remote Access**. Users want to be able to connect securely from a home or office to a private network in the cloud. Typically, the IP address of the connecting client is dynamic and cannot be preconfigured on the VPN server."
+msgstr ""
+
+#: ../../managing_networks.rst:3726
+# dd37e3114c294b4faa1de54929a552f1
+msgid "**Site to Site**. In this scenario, two private subnets are connected over the public Internet with a secure VPN tunnel. The cloud user’s subnet (for example, an office network) is connected through a gateway to the network in the cloud. The address of the user’s gateway must be preconfigured on the VPN server in the cloud. Note that although L2TP-over-IPsec can be used to set up Site-to-Site VPNs, this is not the primary intent of this feature. For more information, see `Section 15.25.5, “Setting Up a Site-to-Site VPN Connection” <#site-to-site-vpn>`__"
+msgstr ""
+
+#: ../../managing_networks.rst:3737
+# bfa322b2a64046429d89460b40d144f0
+msgid "Configuring Remote Access VPN"
+msgstr ""
+
+#: ../../managing_networks.rst:3739
+# 097a6cf2913b4beba6be5431a86de870
+msgid "To set up VPN for the cloud:"
+msgstr ""
+
+#: ../../managing_networks.rst:3747
+# 1fa16e80d9f644edabec5370acdb32bf
+msgid "In the left navigation, click Global Settings."
+msgstr ""
+
+#: ../../managing_networks.rst:3751
+# aa577a63d68e4aec895fe83165f3f782
+msgid "Set the following global configuration parameters."
+msgstr ""
+
+#: ../../managing_networks.rst:3755
+# 0ea3bea3ca8e4aaaaab96eb7cc118fa0
+msgid "remote.access.vpn.client.ip.range – The range of IP addresses to be allocated to remote access VPN clients. The first IP in the range is used by the VPN server."
+msgstr ""
+
+#: ../../managing_networks.rst:3761
+# 9d973a38aa614f53b869f0bdc327f31a
+msgid "remote.access.vpn.psk.length – Length of the IPSec key."
+msgstr ""
+
+#: ../../managing_networks.rst:3765
+# fb498ce174e14f6a9bd79342530814a8
+msgid "remote.access.vpn.user.limit – Maximum number of VPN users per account."
+msgstr ""
+
+#: ../../managing_networks.rst:3768
+# 4dce5f8323054cd7ab088e614da1a9e4
+msgid "To enable VPN for a particular network:"
+msgstr ""
+
+#: ../../managing_networks.rst:3772
+#: ../../managing_networks.rst:3809
+# b675d72fb2994edf9ffb66e7d4a0d9e2
+# b8343075444146c2951287194c670d61
+msgid "Log in as a user or administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../managing_networks.rst:3776
+#: ../../managing_networks.rst:3813
+# 7bfc3800f4454b6d91c8b45e69042d61
+# 8ea70ebbf5844760b522f1a0f75bbb27
+msgid "In the left navigation, click Network."
+msgstr ""
+
+#: ../../managing_networks.rst:3780
+# 0daa9926aa704bf5862add2651c6dcb6
+msgid "Click the name of the network you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:3788
+# 2fa1652bbb944603ad6cbb5d1aad4a5a
+msgid "Click one of the displayed IP address names."
+msgstr ""
+
+#: ../../managing_networks.rst:3792
+# ef6bf9b781754ea18f2335af33284201
+msgid "Click the Enable VPN button. |AttachDiskButton.png: button to attach a volume|"
+msgstr ""
+
+#: ../../managing_networks.rst:3795
+# 2012a33f002143b893c3f7a989397edc
+msgid "The IPsec key is displayed in a popup window."
+msgstr ""
+
+#: ../../managing_networks.rst:3798
+# b28f663cf7724ab9a7f478d438a24394
+msgid "Configuring Remote Access VPN in VPC"
+msgstr ""
+
+#: ../../managing_networks.rst:3800
+# fa00279794274728b49c98337469cbbf
+msgid "On enabling Remote Access VPN on a VPC, any VPN client present outside the VPC can access VMs present in the VPC by using the Remote VPN connection. The VPN client can be present anywhere except inside the VPC on which the user enabled the Remote Access VPN service."
+msgstr ""
+
+#: ../../managing_networks.rst:3805
+# 9995de408c534547bca798eacfc6e29d
+msgid "To enable VPN for a VPC:"
+msgstr ""
+
+#: ../../managing_networks.rst:3817
+#: ../../managing_networks.rst:4260
+#: ../../managing_networks.rst:4357
+#: ../../managing_networks.rst:4550
+#: ../../managing_networks.rst:4971
+#: ../../managing_networks.rst:5036
+#: ../../managing_networks.rst:5164
+#: ../../managing_networks.rst:5246
+#: ../../managing_networks.rst:5414
+#: ../../managing_networks.rst:5651
+#: ../../managing_networks.rst:5743
+#: ../../managing_networks.rst:5831
+#: ../../managing_networks.rst:5921
+#: ../../managing_networks.rst:6163
+#: ../../managing_networks.rst:6471
+#: ../../managing_networks.rst:6555
+#: ../../managing_networks.rst:6680
+#: ../../managing_networks.rst:6719
+# a31affe0adac49f09f3748d0f7ae367e
+# 4af68095a91449e3b8bea9b815da9067
+# dad79a3f32dc40a786d554154bd361b9
+# e38d9555c0c8456ca690fd6cf202b112
+# 821e14755e74419ba72d32bd68d96287
+# 882bbeb316964de78877b7cb3cecc9fc
+# 75cc31bf17e2494fb91a744619c66ee4
+# 1c0efba412354370a1b9f46eaaa0ef7a
+# a5edf42ce9ad47e6a2330279b1398ac1
+# cecf708f7c1043c48169ea6b24e59466
+# 1e27b769cc2540c08fe46fa6ab725699
+# 75db22351660479db8734b0ed18fc894
+# 3a8ef410656041498f008fbe30a414db
+# cfadbb7beee440b5a535959fac59ded7
+# 1efbe4d02aef451a9f809b75fd3a01ae
+# 46c68a38ef0d418b88f703c6038fad39
+# 699be4a90f2b41a0b715d02d5e54e4df
+# 83151a4b19cc4e5489e47c5fa744b5c0
+msgid "In the Select view, select VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:3819
+#: ../../managing_networks.rst:4262
+#: ../../managing_networks.rst:4552
+#: ../../managing_networks.rst:5166
+#: ../../managing_networks.rst:5248
+#: ../../managing_networks.rst:5416
+#: ../../managing_networks.rst:5653
+#: ../../managing_networks.rst:5745
+#: ../../managing_networks.rst:5833
+#: ../../managing_networks.rst:5923
+#: ../../managing_networks.rst:6165
+#: ../../managing_networks.rst:6473
+#: ../../managing_networks.rst:6557
+#: ../../managing_networks.rst:6721
+# 9ae3c14b7e8c402c9c1dce614d4bd2c7
+# e4a77e77230d483db3156f192de9ca5b
+# 8bddf8b867294c708f998bad74efcff6
+# 345034355f8c44c9b7ffc188c0ac9896
+# 568c157061934519a28710ac7dbc349b
+# 47d6e2a72c7f48bcbe8d6ee024c33594
+# 7c289632b014498080a51b30fab9101d
+# f66374dd81f244f6a2f3ed711f4bf948
+# 87c017466f11465ab7cead64d05b5eaf
+# 0c79b640f1da4393b59a0e998560988c
+# d19f27ee89f34a4fb8df870e04257e7f
+# ab679cc378034d79ab6985db72b19b9c
+# 6f1cdf89d13f42f0ab2b5bedcbbd73e6
+# 6005fd24e0d54155a3241c01fe6124e9
+msgid "All the VPCs that you have created for the account is listed in the page."
+msgstr ""
+
+#: ../../managing_networks.rst:3824
+#: ../../managing_networks.rst:5171
+#: ../../managing_networks.rst:5253
+# ca19426a021e4211a1acd3f6a8b16989
+# c182ce3a373542a99217ced2df09ce62
+# 99819c70e71b4f8189fbee678c73a3a5
+msgid "Click the Configure button of the VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:3826
+#: ../../managing_networks.rst:4273
+#: ../../managing_networks.rst:4373
+#: ../../managing_networks.rst:4567
+#: ../../managing_networks.rst:5173
+#: ../../managing_networks.rst:6176
+#: ../../managing_networks.rst:6568
+# 4d3781d769c545d99be97f10a202686a
+# dee16ec55fcf4247845bc5507b0cfd97
+# c307d801b0864d9f96fdcef8b387ce9d
+# bd8619c3aaa0447486c78131f8eb7b14
+# 47f4d3cd60294575ac304752364e0016
+# 96a7d144a4a9461fb5b97370f7f33d41
+# af5676d8c747473d89e78cc8e3892a25
+msgid "For each tier, the following options are displayed:"
+msgstr ""
+
+#: ../../managing_networks.rst:3830
+#: ../../managing_networks.rst:4277
+#: ../../managing_networks.rst:4377
+#: ../../managing_networks.rst:4571
+#: ../../managing_networks.rst:5177
+#: ../../managing_networks.rst:5435
+#: ../../managing_networks.rst:5760
+#: ../../managing_networks.rst:5847
+#: ../../managing_networks.rst:5938
+#: ../../managing_networks.rst:6180
+#: ../../managing_networks.rst:6572
+# e977c7944d7441429e362266f89939b8
+# 5dc3472c6728454999ad5fb3af4f85f7
+# dd1ac38a74e64a408aebd85987d4ca2a
+# 1e64906e22d740f2bbe78adf991135f3
+# 3ab121c1f35c4617914f68af0a25364d
+# 3433f4dcaec546dcae9e778199695765
+# 5747e1b492c54471a0b41977a208232c
+# 1ecff74d45e644809e0f02cb05421be1
+# cbae3a5d141c4cdc83fd6f278d79e79e
+# 41d220172f7c4c1d8553baebb87b3616
+# 7f81c86a21a94b8d8cb340708599235d
+msgid "Internal LB"
+msgstr ""
+
+#: ../../managing_networks.rst:3834
+#: ../../managing_networks.rst:4281
+#: ../../managing_networks.rst:4381
+#: ../../managing_networks.rst:4575
+#: ../../managing_networks.rst:5181
+#: ../../managing_networks.rst:5439
+#: ../../managing_networks.rst:5764
+#: ../../managing_networks.rst:5851
+#: ../../managing_networks.rst:5942
+#: ../../managing_networks.rst:6184
+#: ../../managing_networks.rst:6576
+# 738682e112cb4305a6f74807ed9a15bb
+# 6e5c7436086b4fdda00214facb796e94
+# 17f370caa5ba4969934de8611356c9e5
+# 64c5287f475642419374f2b15f026bab
+# 7e24a426f15048fba793a522a40ef689
+# 2470296892374cf8b1dbbba087f9cc1e
+# b914d7f7af2d4d5c8f763562a1d9e71b
+# 53a27d12607c447980cd9361d9081a86
+# 95adec1d399d4946bedb3a89ca40a486
+# 33c3c72610f7495a8f48211a7823fd4e
+# 72f5b91956d449d4a4a1be58dd85ab17
+msgid "Public LB IP"
+msgstr ""
+
+#: ../../managing_networks.rst:3842
+#: ../../managing_networks.rst:4289
+#: ../../managing_networks.rst:4389
+#: ../../managing_networks.rst:4583
+#: ../../managing_networks.rst:5189
+#: ../../managing_networks.rst:5447
+#: ../../managing_networks.rst:5772
+#: ../../managing_networks.rst:5859
+#: ../../managing_networks.rst:5950
+#: ../../managing_networks.rst:6192
+#: ../../managing_networks.rst:6584
+# 0cb050feaaeb474c926023e60f855b32
+# 11861e54e8724e2fadaca4c4ef5e568e
+# c8e370f0dc4643d293e44f555b923199
+# 0c77f763f1e040f7b80e04b3a37bce24
+# 39a2f9b8856943628ae5927eb7f71c92
+# 2c350c6efc7543d69506721e795eb85f
+# b5d631e4a2024d1fbd4f10d4d0d9064a
+# 952eed7b8185432cae49594fa2f3ec18
+# 7af76e26ead045619c8139e1fead812a
+# b8b0020c6a964034b84a1515f8eeda8b
+# c356254659034481a1dc96d9387f6b9f
+msgid "Virtual Machines"
+msgstr ""
+
+#: ../../managing_networks.rst:3848
+#: ../../managing_networks.rst:4295
+#: ../../managing_networks.rst:4395
+#: ../../managing_networks.rst:4589
+#: ../../managing_networks.rst:5195
+#: ../../managing_networks.rst:5453
+#: ../../managing_networks.rst:5778
+#: ../../managing_networks.rst:5865
+#: ../../managing_networks.rst:5956
+#: ../../managing_networks.rst:6198
+#: ../../managing_networks.rst:6590
+# b89c9f01ccd944b297fff10534973ddc
+# eef1542933fe447b8262890522771d50
+# 5178f0cb1f7c46709c6549e58c7a067a
+# d150a889b3614d81811a9cdc68c5fa66
+# 7ed422ae787a4447960d1e0207cc28dc
+# 5d542e45915b4557b132ba854d60edb6
+# 0fa2b79d145143d880bfdf98bc57f29a
+# b47fda6dfe744ba3853d7a7b7c24b1f6
+# b632ee0308cf4b44b4e44d46a51496e5
+# 3c0bd1aea7ad4d68964f1d4edb118cdd
+# 6a198f55d0a846f3b709af607f86e43e
+msgid "The following router information is displayed:"
+msgstr ""
+
+#: ../../managing_networks.rst:3852
+#: ../../managing_networks.rst:4299
+#: ../../managing_networks.rst:4399
+#: ../../managing_networks.rst:4593
+#: ../../managing_networks.rst:5199
+#: ../../managing_networks.rst:5457
+#: ../../managing_networks.rst:5782
+#: ../../managing_networks.rst:5869
+#: ../../managing_networks.rst:5960
+#: ../../managing_networks.rst:6202
+#: ../../managing_networks.rst:6594
+# a1dbb584fd8b4d4397d374a689f02aa9
+# 0eb728e1fe3c4bf285cd79b34b06d181
+# 8faa54108faa476da673bfb6058b1cc7
+# cb8741bacf1843f0a927b32272bf09cd
+# bae030b0fb4d4ef983ceb14b13495258
+# f3c190c39252412bb8581e07bd6b83aa
+# 2c7b1b5142d1498682193b8ddf312be9
+# d3c687f587e246afae5580f92212b8bf
+# e08e124fc28f4b9387b1f51cdaac7514
+# b64c4d99a2664addbd98a4853da33ffb
+# d46a9ac6036249879d896e722844e95c
+msgid "Private Gateways"
+msgstr ""
+
+#: ../../managing_networks.rst:3856
+#: ../../managing_networks.rst:4303
+#: ../../managing_networks.rst:4403
+#: ../../managing_networks.rst:4597
+#: ../../managing_networks.rst:5203
+#: ../../managing_networks.rst:5461
+#: ../../managing_networks.rst:5786
+#: ../../managing_networks.rst:5873
+#: ../../managing_networks.rst:5964
+#: ../../managing_networks.rst:6206
+#: ../../managing_networks.rst:6598
+# 37d72d2f76774b20a776f60ddc5797d4
+# ea8ad120e00141f783ec53364a03fa37
+# 53b019dc3a224529b82a9a7f37642b0a
+# 174ffd68b1d44ec799357f81eb5c2d25
+# 17bfe0fddda04252a302177c5719e3fe
+# 20a272af5b6d4dee9fc4907b9dd12560
+# 8583a6af04b644e191ff21fcff4f7b8b
+# 4823862431b0480cb61fd62d4b11e87f
+# 8664c330cd684d8595f27db6751ce17c
+# 0cea333fbc5849929e6c0690f226d6a2
+# 9cbdcd3b4ebc4b609e5ba6c56f2d7d5d
+msgid "Public IP Addresses"
+msgstr ""
+
+#: ../../managing_networks.rst:3860
+#: ../../managing_networks.rst:4307
+#: ../../managing_networks.rst:4407
+#: ../../managing_networks.rst:4601
+#: ../../managing_networks.rst:5207
+#: ../../managing_networks.rst:5465
+#: ../../managing_networks.rst:5790
+#: ../../managing_networks.rst:5877
+#: ../../managing_networks.rst:5968
+#: ../../managing_networks.rst:6210
+#: ../../managing_networks.rst:6602
+# b7bc8b8352a74af6b38cc39b1d686153
+# c1878fc16d7b47249752134a9b157b07
+# 8ac22811a0f1450f949764f8ecee4697
+# bde7d8d93cec4b4495105ef97d1f8a35
+# 36b78ef29e834917899c5a7a6ad5ddf4
+# 17f83c3836c64c299d8be56f678dc890
+# bef1f58c45f148ad92c455f3e9d92768
+# d944807c216342baab75254197b930e2
+# 079e9d4527484c839f6f49651f0d6265
+# a9b19cd8a8c44794879d831c50f88b49
+# c9c52762ec514a90a7c5522451754157
+msgid "Site-to-Site VPNs"
+msgstr ""
+
+#: ../../managing_networks.rst:3864
+#: ../../managing_networks.rst:4311
+#: ../../managing_networks.rst:4411
+#: ../../managing_networks.rst:4605
+#: ../../managing_networks.rst:5211
+#: ../../managing_networks.rst:5469
+#: ../../managing_networks.rst:5794
+#: ../../managing_networks.rst:5881
+#: ../../managing_networks.rst:5972
+#: ../../managing_networks.rst:6214
+#: ../../managing_networks.rst:6606
+# 963900352361453a82243e6d229692eb
+# 5e5ead7fdf824603be436cd39c0bd66a
+# 8dd99ffcfe074e1da4fd7aa2c3c78d32
+# 50e7c6af50d847eaa6334a0ece6cd748
+# 00ffbdac5a974718961391e109c231af
+# 56d7689551ad4cce804707382b489ce7
+# da4f7bdfc20746f6a1c7926fada1bf4d
+# 29a0461bac2a4799bcec9c2ab4af689a
+# 1d744b4deebf4f1da4c6a9e318786816
+# de2d02e42e094632be603e8156bdd703
+# 248e40d2acaf4b1a90d4ee955fea9370
+msgid "Network ACL Lists"
+msgstr ""
+
+#: ../../managing_networks.rst:3868
+#: ../../managing_networks.rst:5976
+#: ../../managing_networks.rst:6218
+#: ../../managing_networks.rst:6610
+# f9af791a07354f808cdca900691b32b7
+# 83506da7b26b43c6aac49b3833cad15f
+# 8c42254feeda4c91b2c629f4399e43a9
+# 52bed9f766b34abf852c6fa33e2daf5f
+msgid "In the Router node, select Public IP Addresses."
+msgstr ""
+
+#: ../../managing_networks.rst:3870
+#: ../../managing_networks.rst:5887
+#: ../../managing_networks.rst:5978
+#: ../../managing_networks.rst:6220
+#: ../../managing_networks.rst:6612
+# 145b00e12ee347eb8f5d58bf5d53ed27
+# 4c516df3427c4efe893ef5f2d57e86f4
+# bfeeb4dfe5484e2bbeb371cdef909b3a
+# 64a914a25f0945e1b1477c54b9ddc3b1
+# f6d1237ad0fc42f687f50159ffc308eb
+msgid "The IP Addresses page is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:3874
+# 763f43a3ab6e450284bf8a7e1565147e
+msgid "Click Source NAT IP address."
+msgstr ""
+
+#: ../../managing_networks.rst:3878
+# 3377f8365d824b5cb4828ba4192c7df8
+msgid "Click the Enable VPN button. |vpn-icon.png: button to enable VPN|"
+msgstr ""
+
+#: ../../managing_networks.rst:3880
+# e806264cf83c4fc9bdb76a8963ee8e41
+msgid "Click OK to confirm. The IPsec key is displayed in a pop-up window."
+msgstr ""
+
+#: ../../managing_networks.rst:3882
+# 941f5a62ecb044e1ae914539a331edf8
+msgid "Now, you need to add the VPN users."
+msgstr ""
+
+#: ../../managing_networks.rst:3886
+# ef3bbf0199894b05a9e58396bc91163e
+msgid "Click the Source NAT IP."
+msgstr ""
+
+#: ../../managing_networks.rst:3890
+# 40a450792e5c4aa0b261221e534b235e
+msgid "Select the VPN tab."
+msgstr ""
+
+#: ../../managing_networks.rst:3894
+# da11af4bc3934580904b25becbbe6000
+msgid "Add the username and the corresponding password of the user you wanted to add."
+msgstr ""
+
+#: ../../managing_networks.rst:3903
+# dc788926df844c83bc63fd1ed04b41b5
+msgid "Repeat the same steps to add the VPN users."
+msgstr ""
+
+#: ../../managing_networks.rst:3906
+# 9ee121c5c0434e4cbc3b97ae635890a9
+msgid "Using Remote Access VPN with Windows"
+msgstr ""
+
+#: ../../managing_networks.rst:3908
+# b3edb2c9bcc040aea7a114ca31d0f7d9
+msgid "The procedure to use VPN varies by Windows version. Generally, the user must edit the VPN properties and make sure that the default route is not the VPN. The following steps are for Windows L2TP clients on Windows Vista. The commands should be similar for other Windows versions."
+msgstr ""
+
+#: ../../managing_networks.rst:3915
+# 6ffeddfe41f049ca9722b714502eabfb
+msgid "Log in to the CloudStack UI and click on the source NAT IP for the account. The VPN tab should display the IPsec preshared key. Make a note of this and the source NAT IP. The UI also lists one or more users and their passwords. Choose one of these users, or, if none exists, add a user and password."
+msgstr ""
+
+#: ../../managing_networks.rst:3923
+# 8ca0fcc6fcfd40f28f0c675345fb5f4d
+msgid "On the Windows box, go to Control Panel, then select Network and Sharing center. Click Setup a connection or network."
+msgstr ""
+
+#: ../../managing_networks.rst:3928
+# e26b9786a5c64704989e389fb2bbce0d
+msgid "In the next dialog, select No, create a new connection."
+msgstr ""
+
+#: ../../managing_networks.rst:3932
+# 1c1b2aafb3674ec18a5da699bf60337f
+msgid "In the next dialog, select Use my Internet Connection (VPN)."
+msgstr ""
+
+#: ../../managing_networks.rst:3936
+# 98dfa80786574e6ea33f5b0c24fa4700
+msgid "In the next dialog, enter the source NAT IP from step `1 <#source-nat>`__ and give the connection a name. Check Don't connect now."
+msgstr ""
+
+#: ../../managing_networks.rst:3942
+# 533985edf60848b2a4ebf75ba177c150
+msgid "In the next dialog, enter the user name and password selected in step `1 <#source-nat>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:3951
+# 2207831550714a73a1a41e5283a49cd9
+msgid "Go back to the Control Panel and click Network Connections to see the new connection. The connection is not active yet."
+msgstr ""
+
+#: ../../managing_networks.rst:3956
+# 1e1b6b1d256942c2a129691e49daceaf
+msgid "Right-click the new connection and select Properties. In the Properties dialog, select the Networking tab."
+msgstr ""
+
+#: ../../managing_networks.rst:3961
+# e4ea1219d3634755a9395cae6ab51e7f
+msgid "In Type of VPN, choose L2TP IPsec VPN, then click IPsec settings. Select Use preshared key. Enter the preshared key from step `1 <#source-nat>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:3967
+# 67167335a22243b7988e640a0022857c
+msgid "The connection is ready for activation. Go back to Control Panel -> Network Connections and double-click the created connection."
+msgstr ""
+
+#: ../../managing_networks.rst:3972
+# 109e34abfe6f4522b5c8bc8bc60f2fe0
+msgid "Enter the user name and password from step `1 <#source-nat>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:3975
+# 8c9ad7097eda4b19bb45090e25249724
+msgid "Using Remote Access VPN with Mac OS X"
+msgstr ""
+
+#: ../../managing_networks.rst:3977
+# 5f27e95b14c9475a8f7c56618a1cb515
+msgid "First, be sure you've configured the VPN settings in your CloudStack install. This section is only concerned with connecting via Mac OS X to your VPN."
+msgstr ""
+
+#: ../../managing_networks.rst:3981
+# dc2c20b5eb574ed2adada77dbf270a42
+msgid "Note, these instructions were written on Mac OS X 10.7.5. They may differ slightly in older or newer releases of Mac OS X."
+msgstr ""
+
+#: ../../managing_networks.rst:3986
+# 9c82432ffa134c1ca32ac34f08988c6d
+msgid "On your Mac, open System Preferences and click Network."
+msgstr ""
+
+#: ../../managing_networks.rst:3990
+# 9d97977e9c46436ab9fe30c172722d6b
+msgid "Make sure Send all traffic over VPN connection is not checked."
+msgstr ""
+
+#: ../../managing_networks.rst:3994
+# 63ac91c8dc0e497b80a34dfcae925d4b
+msgid "If your preferences are locked, you'll need to click the lock in the bottom left-hand corner to make any changes and provide your administrator credentials."
+msgstr ""
+
+#: ../../managing_networks.rst:4000
+# 3382a964d3e24d78ac26db4b8bda5128
+msgid "You will need to create a new network entry. Click the plus icon on the bottom left-hand side and you'll see a dialog that says \"Select the interface and enter a name for the new service.\" Select VPN from the Interface drop-down menu, and \"L2TP over IPSec\" for the VPN Type. Enter whatever you like within the \"Service Name\" field."
+msgstr ""
+
+#: ../../managing_networks.rst:4008
+# f99d122e9241423fbdcf6aa83fa0b08f
+msgid "You'll now have a new network interface with the name of whatever you put in the \"Service Name\" field. For the purposes of this example, we'll assume you've named it \"CloudStack.\" Click on that interface and provide the IP address of the interface for your VPN under the Server Address field, and the user name for your VPN under Account Name."
+msgstr ""
+
+#: ../../managing_networks.rst:4017
+# 90453b8ed4bb48a18163cc20cb129995
+msgid "Click Authentication Settings, and add the user's password under User Authentication and enter the pre-shared IPSec key in the Shared Secret field under Machine Authentication. Click OK."
+msgstr ""
+
+#: ../../managing_networks.rst:4023
+# 92408c82c4b04948a05c719bd048fad0
+msgid "You may also want to click the \"Show VPN status in menu bar\" but that's entirely optional."
+msgstr ""
+
+#: ../../managing_networks.rst:4028
+# 8190135a88884eb788e9ce54c71ca84f
+msgid "Now click \"Connect\" and you will be connected to the CloudStack VPN."
+msgstr ""
+
+#: ../../managing_networks.rst:4031
+# ac02eeb882404522aacc0cc8293ad641
+msgid "Setting Up a Site-to-Site VPN Connection"
+msgstr ""
+
+#: ../../managing_networks.rst:4033
+# e204e99f433b4e51a129efbe663d70ef
+msgid "A Site-to-Site VPN connection helps you establish a secure connection from an enterprise datacenter to the cloud infrastructure. This allows users to access the guest VMs by establishing a VPN connection to the virtual router of the account from a device in the datacenter of the enterprise. You can also establish a secure connection between two VPC setups or high availability zones in your environment. Having this facility eliminates the need to establish VPN connections to individual VMs."
+msgstr ""
+
+#: ../../managing_networks.rst:4042
+# 8e29e93424a04c189576052f05b8e717
+msgid "The difference from Remote VPN is that Site-to-site VPNs connects entire networks to each other, for example, connecting a branch office network to a company headquarters network. In a site-to-site VPN, hosts do not have VPN client software; they send and receive normal TCP/IP traffic through a VPN gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:4048
+# 95bbe3e3d5554fb6bc7959c18174607c
+msgid "The supported endpoints on the remote datacenters are:"
+msgstr ""
+
+#: ../../managing_networks.rst:4052
+# 7e357cb1629f467485ba9145a75a81f7
+msgid "Cisco ISR with IOS 12.4 or later"
+msgstr ""
+
+#: ../../managing_networks.rst:4056
+# 854482adf7dd4aa393f38b07756645aa
+msgid "Juniper J-Series routers with JunOS 9.5 or later"
+msgstr ""
+
+#: ../../managing_networks.rst:4060
+# 96648d86950840f89dc81c431d60cfb6
+msgid "CloudStack virtual routers"
+msgstr ""
+
+#: ../../managing_networks.rst:4062
+# 1a74583da3a44bd39eb253120139a932
+msgid "In addition to the specific Cisco and Juniper devices listed above, the expectation is that any Cisco or Juniper device running on the supported operating systems are able to establish VPN connections."
+msgstr ""
+
+#: ../../managing_networks.rst:4064
+# 64b2db355ac04f0f9c59eae16613e881
+msgid "To set up a Site-to-Site VPN connection, perform the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:4068
+# 796a6d7dfb6d46498818110494844639
+msgid "Create a Virtual Private Cloud (VPC)."
+msgstr ""
+
+#: ../../managing_networks.rst:4070
+# 8792529d67f442debcc4278090beb143
+msgid "See `Section 15.27, “Configuring a Virtual Private Cloud” <#configure-vpc>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:4075
+# 2cde96423eaa4b00a89bc8638be81197
+msgid "Create a VPN Customer Gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:4079
+# 24923d7a1f5b4c968069162a997e27e8
+msgid "Create a VPN gateway for the VPC that you created."
+msgstr ""
+
+#: ../../managing_networks.rst:4083
+# de7773aef60648c395206d22ebf8bb2b
+msgid "Create VPN connection from the VPC VPN gateway to the customer VPN gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:4087
+# 44b042e04c484e1aa9425682b124b081
+msgid "Creating and Updating a VPN Customer Gateway"
+msgstr ""
+
+#: ../../managing_networks.rst:4089
+# c2ffba4bbe2d413aab0af270e8b2195f
+msgid "A VPN customer gateway can be connected to only one VPN gateway at a time."
+msgstr ""
+
+#: ../../managing_networks.rst:4091
+# 7b0767f2578b495595801fe8c497c3cd
+msgid "To add a VPN Customer Gateway:"
+msgstr ""
+
+#: ../../managing_networks.rst:4103
+#: ../../managing_networks.rst:4227
+# 78b54d35bae1432b9360ca8210ec82c5
+# d664ef6b19954f3381587a7ed6fc32de
+msgid "In the Select view, select VPN Customer Gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:4107
+# a5c0098ccc8d4b1ca1ae5d86b3d43998
+msgid "Click Add VPN Customer Gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:4109
+# e15f9c41a48247cfb47d45e73ea464a0
+msgid "|addvpncustomergateway.png: adding a customer gateway.|"
+msgstr ""
+
+#: ../../managing_networks.rst:4115
+# 2a792a8dedb2441a823f19c7d482ecf6
+msgid "**Name**: A unique name for the VPN customer gateway you create."
+msgstr ""
+
+#: ../../managing_networks.rst:4119
+# fcab4cadde164668976324bf647c7b59
+msgid "**Gateway**: The IP address for the remote gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:4123
+# d1b2fa29c7dd4b39a5887883d6571ed1
+msgid "**CIDR list**: The guest CIDR list of the remote subnets. Enter a CIDR or a comma-separated list of CIDRs. Ensure that a guest CIDR list is not overlapped with the VPC’s CIDR, or another guest CIDR. The CIDR must be RFC1918-compliant."
+msgstr ""
+
+#: ../../managing_networks.rst:4130
+# 25ad295a35ca425cb4bb391680aad6a3
+msgid "**IPsec Preshared Key**: Preshared keying is a method where the endpoints of the VPN share a secret key. This key value is used to authenticate the customer gateway and the VPC VPN gateway to each other."
+msgstr ""
+
+#: ../../managing_networks.rst:4135
+# 60c393822e29418283ca3ba6907b44c3
+msgid "The IKE peers (VPN end points) authenticate each other by computing and sending a keyed hash of data that includes the Preshared key. If the receiving peer is able to create the same hash independently by using its Preshared key, it knows that both peers must share the same secret, thus authenticating the customer gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:4139
+# cd6c278668824b58a2ffb239404e1012
+msgid "**IKE Encryption**: The Internet Key Exchange (IKE) policy for phase-1. The supported encryption algorithms are AES128, AES192, AES256, and 3DES. Authentication is accomplished through the Preshared Keys."
+msgstr ""
+
+#: ../../managing_networks.rst:4144
+# a3cf2ddfca704791903d9a0ffe07c87c
+msgid "The phase-1 is the first phase in the IKE process. In this initial negotiation phase, the two VPN endpoints agree on the methods to be used to provide security for the underlying IP traffic. The phase-1 authenticates the two VPN gateways to each other, by confirming that the remote gateway has a matching Preshared Key."
+msgstr ""
+
+#: ../../managing_networks.rst:4148
+# dc8ed8cb236e467084228a10a29908e7
+msgid "**IKE Hash**: The IKE hash for phase-1. The supported hash algorithms are SHA1 and MD5."
+msgstr ""
+
+#: ../../managing_networks.rst:4153
+# d119a30b80184f6e988be13f0013017b
+msgid "**IKE DH**: A public-key cryptography protocol which allows two parties to establish a shared secret over an insecure communications channel. The 1536-bit Diffie-Hellman group is used within IKE to establish session keys. The supported options are None, Group-5 (1536-bit) and Group-2 (1024-bit)."
+msgstr ""
+
+#: ../../managing_networks.rst:4161
+# d00e55d3a58247f4902732e8f104989a
+msgid "**ESP Encryption**: Encapsulating Security Payload (ESP) algorithm within phase-2. The supported encryption algorithms are AES128, AES192, AES256, and 3DES."
+msgstr ""
+
+#: ../../managing_networks.rst:4165
+# e29d497cac194439ba539800b8037ff5
+msgid "The phase-2 is the second phase in the IKE process. The purpose of IKE phase-2 is to negotiate IPSec security associations (SA) to set up the IPSec tunnel. In phase-2, new keying material is extracted from the Diffie-Hellman key exchange in phase-1, to provide session keys to use in protecting the VPN data flow."
+msgstr ""
+
+#: ../../managing_networks.rst:4169
+# d2b39ecbc1d44c3d9a6d78c78be321e0
+msgid "**ESP Hash**: Encapsulating Security Payload (ESP) hash for phase-2. Supported hash algorithms are SHA1 and MD5."
+msgstr ""
+
+#: ../../managing_networks.rst:4174
+# 47abcc0c6f134e1797ec70ee5355a74c
+msgid "**Perfect Forward Secrecy**: Perfect Forward Secrecy (or PFS) is the property that ensures that a session key derived from a set of long-term public and private keys will not be compromised. This property enforces a new Diffie-Hellman key exchange. It provides the keying material that has greater key material life and thereby greater resistance to cryptographic attacks. The available options are None, Group-5 (1536-bit) and Group-2 (1024-bit). The security of the key exchanges increase as the DH groups grow larger, as does the time of the exchanges."
+msgstr ""
+
+#: ../../managing_networks.rst:4184
+# e1411a88880e44b88adeaffac1d8ebd0
+msgid "When PFS is turned on, for every negotiation of a new phase-2 SA the two gateways must generate a new set of phase-1 keys. This adds an extra layer of protection that PFS adds, which ensures if the phase-2 SA’s have expired, the keys used for new phase-2 SA’s have not been generated from the current phase-1 keying material."
+msgstr ""
+
+#: ../../managing_networks.rst:4188
+# e61813c0a2954d6283658b02b58d4cb6
+msgid "**IKE Lifetime (seconds)**: The phase-1 lifetime of the security association in seconds. Default is 86400 seconds (1 day). Whenever the time expires, a new phase-1 exchange is performed."
+msgstr ""
+
+#: ../../managing_networks.rst:4194
+# cdae24a26b454b838fa3673a49c43446
+msgid "**ESP Lifetime (seconds)**: The phase-2 lifetime of the security association in seconds. Default is 3600 seconds (1 hour). Whenever the value is exceeded, a re-key is initiated to provide a new IPsec encryption and authentication session keys."
+msgstr ""
+
+#: ../../managing_networks.rst:4201
+# 99c4be56c93142898b61b090661e5295
+msgid "**Dead Peer Detection**: A method to detect an unavailable Internet Key Exchange (IKE) peer. Select this option if you want the virtual router to query the liveliness of its IKE peer at regular intervals. It’s recommended to have the same configuration of DPD on both side of VPN connection."
+msgstr ""
+
+#: ../../managing_networks.rst:4212
+# cbedab3aca3b46d3b729d10282337f33
+msgid "Updating and Removing a VPN Customer Gateway"
+msgstr ""
+
+#: ../../managing_networks.rst:4214
+# 3b6106b5e9714642a65edc3d3b5af11f
+msgid "You can update a customer gateway either with no VPN connection, or related VPN connection is in error state."
+msgstr ""
+
+#: ../../managing_networks.rst:4231
+# 0959bb19a36c4e70a01a974a38e149dc
+msgid "Select the VPN customer gateway you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:4235
+# 32f107b7adf04cf2b7f795ae7aaa81c5
+msgid "To modify the required parameters, click the Edit VPN Customer Gateway button |edit.png: button to edit a VPN customer gateway|"
+msgstr ""
+
+#: ../../managing_networks.rst:4240
+# 37ada8df7369477881326c75d570e61a
+msgid "To remove the VPN customer gateway, click the Delete VPN Customer Gateway button |delete.png: button to remove a VPN customer gateway|"
+msgstr ""
+
+#: ../../managing_networks.rst:4248
+# 3236f66e39e94005b7667ae57885d653
+msgid "Creating a VPN gateway for the VPC"
+msgstr ""
+
+#: ../../managing_networks.rst:4267
+#: ../../managing_networks.rst:4363
+#: ../../managing_networks.rst:4557
+#: ../../managing_networks.rst:5658
+#: ../../managing_networks.rst:5750
+#: ../../managing_networks.rst:5928
+#: ../../managing_networks.rst:6562
+# 511d19b2e3504253b21f8f4fcabd362a
+# e01144a6325b4c608dab9c6379458a12
+# bc8da9bc86e542dda10770fce00c89e1
+# 501e01e53ce94f08a0f3d4fe216da110
+# 703482b61d324ba3890aeb460992e1ce
+# 9c1f460ca2e24825a0292fca00b7d23f
+# d4ac91902c79445aa3e7bbd80a3f6a03
+msgid "Click the Configure button of the VPC to which you want to deploy the VMs."
+msgstr ""
+
+#: ../../managing_networks.rst:4270
+#: ../../managing_networks.rst:4366
+#: ../../managing_networks.rst:4560
+#: ../../managing_networks.rst:5424
+#: ../../managing_networks.rst:5753
+#: ../../managing_networks.rst:5840
+#: ../../managing_networks.rst:5931
+#: ../../managing_networks.rst:6565
+# a65c97cf987e47c9860d773977e19aaa
+# 26d378a616bb4724a0345a027037983e
+# 9ec7e2c78f664ddea4b564bb44ba02f8
+# aa36d7fe59be4f04a4fb82dde257bbd7
+# 4a661989a9a741af84d8dbb14a16d6f0
+# 6e876e1c538f4945ab205b8415e88220
+# a461edb130a14c6cb41075603aee7d8f
+# 6a50c314b64e4c8ba8b1469a2e2c50c4
+msgid "The VPC page is displayed where all the tiers you created are listed in a diagram."
+msgstr ""
+
+#: ../../managing_networks.rst:4315
+#: ../../managing_networks.rst:4415
+#: ../../managing_networks.rst:4609
+# 0655419f6d7d4c40b18bd684d78fc5c2
+# 1b39c01ef614430598699e611dfc623e
+# 7dd952c2ddc347ef976ff0ac7e66de45
+msgid "Select Site-to-Site VPN."
+msgstr ""
+
+#: ../../managing_networks.rst:4317
+# 7b01ec42a0b64f369443a3737b23f0ed
+msgid "If you are creating the VPN gateway for the first time, selecting Site-to-Site VPN prompts you to create a VPN gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:4322
+# 742940cb43e74b209faabb6ea27db456
+msgid "In the confirmation dialog, click Yes to confirm."
+msgstr ""
+
+#: ../../managing_networks.rst:4324
+# 7f7c54fe5bae49bab3b51cf86e863910
+msgid "Within a few moments, the VPN gateway is created. You will be prompted to view the details of the VPN gateway you have created. Click Yes to confirm."
+msgstr ""
+
+#: ../../managing_networks.rst:4328
+# 63a4578cd1dd4ad98122b9149082a8b3
+msgid "The following details are displayed in the VPN Gateway page:"
+msgstr ""
+
+#: ../../managing_networks.rst:4336
+# 1da96b1b044e4d78b49dcb8cc4099ba3
+msgid "Account"
+msgstr ""
+
+#: ../../managing_networks.rst:4340
+# 1c7f84073654461dae36083481c5502c
+msgid "Domain"
+msgstr ""
+
+#: ../../managing_networks.rst:4343
+# 030c20e667e445a5a3e530f0740204bf
+msgid "Creating a VPN Connection"
+msgstr ""
+
+#: ../../managing_networks.rst:4345
+# ac44534c69794320b653ebbb19e635f2
+msgid "CloudStack supports creating up to 8 VPN connections."
+msgstr ""
+
+#: ../../managing_networks.rst:4359
+# f6a9f2333b3b4aaabfdca1da35eaa6de
+msgid "All the VPCs that you create for the account are listed in the page."
+msgstr ""
+
+#: ../../managing_networks.rst:4371
+#: ../../managing_networks.rst:4565
+#: ../../managing_networks.rst:5429
+# adfb4ad12aa243d6ad05463c636503a1
+# 327d040bcabf40599dcf368f22a07853
+# e07568be318548718935c6472cbd9bb0
+msgid "Click the Settings icon."
+msgstr ""
+
+#: ../../managing_networks.rst:4417
+#: ../../managing_networks.rst:4611
+# e03ba2fa9183402c9c8486eb92516980
+# b9a7a824b72047c48214b440c8a54618
+msgid "The Site-to-Site VPN page is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:4421
+#: ../../managing_networks.rst:4615
+# 9389c31ffef740e38608620a80bee1b7
+# 7a249b578800445fbcb0b768547bd1c4
+msgid "From the Select View drop-down, ensure that VPN Connection is selected."
+msgstr ""
+
+#: ../../managing_networks.rst:4426
+# dce19ba002cf49d8af17ad7a380f2606
+msgid "Click Create VPN Connection."
+msgstr ""
+
+#: ../../managing_networks.rst:4428
+# 13474ca5db5a4cec8688a86f4e74350e
+msgid "The Create VPN Connection dialog is displayed:"
+msgstr ""
+
+#: ../../managing_networks.rst:4430
+# bbc62b37255b4285a412fe8fef5cdaf1
+msgid "|createvpnconnection.png: creating a VPN connection to the customer gateway.|"
+msgstr ""
+
+#: ../../managing_networks.rst:4435
+# 25353dbd7d224969878afd9f2f0a3d79
+msgid "Select the desired customer gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:4439
+# b8751b7b869e41e89c732ca0a4e1b09b
+msgid "Select Passive if you want to establish a connection between two VPC virtual routers."
+msgstr ""
+
+#: ../../managing_networks.rst:4442
+# bc97e44ce1cf44878ebb684d36080bb9
+msgid "If you want to establish a connection between two VPC virtual routers, select Passive only on one of the VPC virtual routers, which waits for the other VPC virtual router to initiate the connection. Do not select Passive on the VPC virtual router that initiates the connection."
+msgstr ""
+
+#: ../../managing_networks.rst:4452
+# eadc5a4556aa44f28e4863d1c2d4fecc
+msgid "Within a few moments, the VPN Connection is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:4454
+# 8ed2f646df6a4d75857c6a8fac04e829
+msgid "The following information on the VPN connection is displayed:"
+msgstr ""
+
+#: ../../managing_networks.rst:4466
+# de7d0faafa2448e08a0d2493699c50c7
+msgid "State"
+msgstr ""
+
+#: ../../managing_networks.rst:4470
+# e3764a89a0ce4201889a0fadffcc09d5
+msgid "IPSec Preshared Key"
+msgstr ""
+
+#: ../../managing_networks.rst:4474
+# 8ca0096772074c439e2d9a61b38fd6ef
+msgid "IKE Policy"
+msgstr ""
+
+#: ../../managing_networks.rst:4478
+# 7ec1e33e92c64c29a0c177e54bc2cb9c
+msgid "ESP Policy"
+msgstr ""
+
+#: ../../managing_networks.rst:4481
+# e8af24af3aa041559e70bbc4f134e2a0
+msgid "Site-to-Site VPN Connection Between VPC Networks"
+msgstr ""
+
+#: ../../managing_networks.rst:4483
+# d32d29e70caf4194bc1f7aeb3159a85e
+msgid "CloudStack provides you with the ability to establish a site-to-site VPN connection between CloudStack virtual routers. To achieve that, add a passive mode Site-to-Site VPN. With this functionality, users can deploy applications in multiple Availability Zones or VPCs, which can communicate with each other by using a secure Site-to-Site VPN Tunnel."
+msgstr ""
+
+#: ../../managing_networks.rst:4489
+# aca5c3b83f3948419a10f421e9ebb6d3
+msgid "This feature is supported on all the hypervisors."
+msgstr ""
+
+#: ../../managing_networks.rst:4493
+# be029698755440618c84f5ada6cd0f0d
+msgid "Create two VPCs. For example, VPC A and VPC B."
+msgstr ""
+
+#: ../../managing_networks.rst:4495
+# d849133b3805422b85e8fb4b5c1e843f
+msgid "For more information, see `Section 15.27, “Configuring a Virtual Private Cloud” <#configure-vpc>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:4500
+# baae8ca5cf4c4e53a308274c699e84e4
+msgid "Create VPN gateways on both the VPCs you created."
+msgstr ""
+
+#: ../../managing_networks.rst:4502
+# cf3881f3f2af4d808dd58ae3dd71a648
+msgid "For more information, see `Section 15.25.5.2, “Creating a VPN gateway for the VPC” <#create-vpn-gateway-for-vpc>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:4507
+# 5f6abf3bf9f4445db1b846b5f06d95b7
+msgid "Create VPN customer gateway for both the VPCs."
+msgstr ""
+
+#: ../../managing_networks.rst:4509
+# d3b7adbcc13a4165815edae105d44fc2
+msgid "For more information, see `Section 15.25.5.1, “Creating and Updating a VPN Customer Gateway” <#create-vpn-customer-gateway>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:4514
+# 77919bde060b4e299739c9be53a60eb8
+msgid "Enable a VPN connection on VPC A in passive mode."
+msgstr ""
+
+#: ../../managing_networks.rst:4516
+# 8ea54231bb2249e6ae3e0130c0296796
+msgid "For more information, see `Section 15.25.5.3, “Creating a VPN Connection” <#create-vpn-connection-vpc>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:4519
+# 14ae7f0b268f42b0a79b9c961fe70c75
+msgid "Ensure that the customer gateway is pointed to VPC B. The VPN connection is shown in the Disconnected state."
+msgstr ""
+
+#: ../../managing_networks.rst:4524
+# f7ba3e9df3ac4049801e174c1b181c84
+msgid "Enable a VPN connection on VPC B."
+msgstr ""
+
+#: ../../managing_networks.rst:4526
+# 46b233eee044428188efb7edd2994c18
+msgid "Ensure that the customer gateway is pointed to VPC A. Because virtual router of VPC A, in this case, is in passive mode and is waiting for the virtual router of VPC B to initiate the connection, VPC B virtual router should not be in passive mode."
+msgstr ""
+
+#: ../../managing_networks.rst:4531
+# 017ef29bf6994c348cd076349e7eabaf
+msgid "The VPN connection is shown in the Disconnected state."
+msgstr ""
+
+#: ../../managing_networks.rst:4533
+# 849dd8090fb74fa9a6696467a54e91c4
+msgid "Creating VPN connection on both the VPCs initiates a VPN connection. Wait for few seconds. The default is 30 seconds for both the VPN connections to show the Connected state."
+msgstr ""
+
+#: ../../managing_networks.rst:4538
+# 8fb620a0c32649b8a3ad2e44584f8a13
+msgid "Restarting and Removing a VPN Connection"
+msgstr ""
+
+#: ../../managing_networks.rst:4618
+# 2d31e38ca55b40ac9e8ce765dd0d3692
+msgid "All the VPN connections you created are displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:4622
+# 6aeb5be8241c49548bc0501a9f5b59f0
+msgid "Select the VPN connection you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:4624
+# 410c2e173f9e414dab7470faec1c5598
+msgid "The Details tab is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:4628
+# 0516c8c707dd4a049cc801f1cc68fabb
+msgid "To remove a VPN connection, click the Delete VPN connection button |remove-vpn.png: button to remove a VPN connection|"
+msgstr ""
+
+#: ../../managing_networks.rst:4631
+# d570926d708b453e81da0da78f495cc1
+msgid "To restart a VPN connection, click the Reset VPN connection button present in the Details tab. |reset-vpn.png: button to reset a VPN connection|"
+msgstr ""
+
+#: ../../managing_networks.rst:4636
+# 73e93f585b5947af90ee476b4b71ca25
+msgid "About Inter-VLAN Routing (nTier Apps)"
+msgstr ""
+
+#: ../../managing_networks.rst:4638
+# e1cdf935aea64e868a11d602b20cf6c3
+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 the VMs. In effect, you can segment VMs by means of VLANs into different networks that can host multi-tier applications, such as Web, Application, or Database. Such segmentation by means of VLANs logically separate application VMs for higher security and lower broadcasts, while remaining physically connected to the same device."
+msgstr ""
+
+#: ../../managing_networks.rst:4651
+# 0d404f9da0ba4f8aa58cab4bb8994e7f
+msgid "This feature is supported on XenServer, KVM, and VMware hypervisors."
+msgstr ""
+
+#: ../../managing_networks.rst:4653
+# b48459f15e6a45318c79f097d562ed35
+msgid "The major advantages are:"
+msgstr ""
+
+#: ../../managing_networks.rst:4657
+# 37506050acaf40fda04742118858f794
+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 ""
+
+#: ../../managing_networks.rst:4662
+# 06560c3f129242f0adf92f680f2274df
+msgid "A VLAN allocated for an account cannot be shared between multiple accounts."
+msgstr ""
+
+#: ../../managing_networks.rst:4666
+# 25eee29513534fd4bb12a269333bd787
+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 ""
+
+#: ../../managing_networks.rst:4672
+# 74e4b83e45024768b481877a882eba72
+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 ""
+
+#: ../../managing_networks.rst:4678
+# 8f27053c8ee44c22b62581053f1910b1
+msgid "The administrator can create the following gateways to send to or receive traffic from the VMs:"
+msgstr ""
+
+#: ../../managing_networks.rst:4683
+# 52b5a0ec994b4c8daf1db4d35c2aa504
+msgid "**VPN Gateway**: For more information, see `Section 15.25.5.2, “Creating a VPN gateway for the VPC” <#create-vpn-gateway-for-vpc>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:4689
+# 2e0edcccf95c4a1dbf3c151de2439616
+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 ""
+
+#: ../../managing_networks.rst:4696
+# a659063093e948fcbec68ff5b117678c
+msgid "**Private Gateway**: For more information, see `Section 15.27.5, “Adding a Private Gateway to a VPC” <#add-gateway-vpc>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:4701
+# f7e8baf7e8284cacb10f71e2b87529b9
+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 ""
+
+#: ../../managing_networks.rst:4705
+# 066d3de08ee44a9f8ce5fd196908df8a
+msgid "For example:"
+msgstr ""
+
+#: ../../managing_networks.rst:4709
+# 3b955ae841204566b4939325f181cea5
+msgid "**VLANs and Public Gateway**: For example, an application is deployed in the cloud, and the Web application VMs communicate with the Internet."
+msgstr ""
+
+#: ../../managing_networks.rst:4715
+# 070bb78cb77c45899817353d9d3afe40
+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 ""
+
+#: ../../managing_networks.rst:4722
+# 612fa4a2bba040fabccd21dbc46a3b91
+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 ""
+
+#: ../../managing_networks.rst:4728
+# 754f1b2b5a1b4f92b6ef9530907e259d
+msgid "The following figure shows the possible deployment scenarios of a Inter-VLAN setup:"
+msgstr ""
+
+#: ../../managing_networks.rst:4731
+# 536386b54906472e8b8ddd90dab72f0b
+msgid "|mutltier.png: a multi-tier setup.|"
+msgstr ""
+
+#: ../../managing_networks.rst:4733
+# a610a58c65f0482dbd12dd339ec17888
+msgid "To set up a multi-tier Inter-VLAN deployment, see `Section 15.27, “Configuring a Virtual Private Cloud” <#configure-vpc>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:4737
+# 8c6f5c047656431f9efa0775f05f20e9
+msgid "Configuring a Virtual Private Cloud"
+msgstr ""
+
+#: ../../managing_networks.rst:4740
+# 51dbe5ce31064783a34b81a1169ce257
+msgid "About Virtual Private Clouds"
+msgstr ""
+
+#: ../../managing_networks.rst:4742
+# 36f1958de4dd4cd085e8e06b28b118b3
+msgid "CloudStack Virtual Private Cloud is a private, isolated part of CloudStack. A VPC can have its own virtual network topology that resembles a traditional physical network. You can launch VMs in the virtual network that can have private addresses in the range of your choice, for example: 10.0.0.0/16. You can define network tiers within your VPC network range, which in turn enables you to group similar kinds of instances based on IP address range."
+msgstr ""
+
+#: ../../managing_networks.rst:4750
+# 231f37879fac4621b48e0c39fc46c2f1
+msgid "For example, if a VPC has the private range 10.0.0.0/16, its guest networks can have the network ranges 10.0.1.0/24, 10.0.2.0/24, 10.0.3.0/24, and so on."
+msgstr ""
+
+#: ../../managing_networks.rst:4757
+# b1aa5c2f5259429f9ef169a6f5ca6f97
+msgid "A VPC is comprised of the following network components:"
+msgstr ""
+
+#: ../../managing_networks.rst:4761
+# 81f964d528e6402ba3e1428cddb674bd
+msgid "**VPC**: A VPC acts as a container for multiple isolated networks that can communicate with each other via its virtual router."
+msgstr ""
+
+#: ../../managing_networks.rst:4766
+# c94ea42c1d514b648ea93bc841f47eeb
+msgid "**Network Tiers**: Each tier acts as an isolated network with its own VLANs and CIDR list, where you can place groups of resources, such as VMs. The tiers are segmented by means of VLANs. The NIC of each tier acts as its gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:4773
+# 685738b4e44748a9ac538dfd407f1e6e
+msgid "**Virtual Router**: A virtual router is automatically created and started when you create a VPC. The virtual router connect the tiers and direct traffic among the public gateway, the VPN gateways, and the NAT instances. For each tier, a corresponding NIC and IP exist in the virtual router. The virtual router provides DNS and DHCP services through its IP."
+msgstr ""
+
+#: ../../managing_networks.rst:4782
+# 4ecd641c04c5446da55dc72dd42babb9
+msgid "**Public Gateway**: The traffic to and from the Internet routed to the VPC through the public gateway. In a VPC, the public gateway is not exposed to the end user; therefore, static routes are not support for the public gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:4789
+# 64b40911d3fa4da8bd9fc7c20cd350ed
+msgid "**Private Gateway**: All the traffic to and from a private network routed to the VPC through the private gateway. For more information, see `Section 15.27.5, “Adding a Private Gateway to a VPC” <#add-gateway-vpc>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:4796
+# efdd8a661d1a4f77a361eeefed2f8f82
+msgid "**VPN Gateway**: The VPC side of a VPN connection."
+msgstr ""
+
+#: ../../managing_networks.rst:4800
+# c30d05145eec45938cb3f8a99bf3eabe
+msgid "**Site-to-Site VPN Connection**: A hardware-based VPN connection between your VPC and your datacenter, home network, or co-location facility. For more information, see `Section 15.25.5, “Setting Up a Site-to-Site VPN Connection” <#site-to-site-vpn>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:4807
+# 83a3f96194b24badaa38506d70b11009
+msgid "**Customer Gateway**: The customer side of a VPN Connection. For more information, see `Section 15.25.5.1, “Creating and Updating a VPN Customer Gateway” <#create-vpn-customer-gateway>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:4813
+# cb437b168320462f8765d7949d2c2d1d
+msgid "**NAT Instance**: An instance that provides Port Address Translation for instances to access the Internet via the public gateway. For more information, see `Section 15.27.10, “Enabling or Disabling Static NAT on a VPC” <#enable-disable-static-nat-vpc>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:4820
+# 2dcef6cbbdf64b628e2fb8898dadeac0
+msgid "**Network ACL**: Network ACL is a group of Network ACL items. Network ACL items are nothing but numbered rules that are evaluated in order, starting with the lowest numbered rule. These rules determine whether traffic is allowed in or out of any tier associated with the network ACL. For more information, see `Section 15.27.4, “Configuring Network Access Control List” <#configure-acl>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:4830
+# 8021e62528a3456283a94683c84a5a30
+msgid "In a VPC, the following four basic options of network architectures are present:"
+msgstr ""
+
+#: ../../managing_networks.rst:4835
+# 79c69f1431cf41f992cf738d7291af75
+msgid "VPC with a public gateway only"
+msgstr ""
+
+#: ../../managing_networks.rst:4839
+# 3b7dc9ded7fd4111a027ec9623f8ab3b
+msgid "VPC with public and private gateways"
+msgstr ""
+
+#: ../../managing_networks.rst:4843
+# 840b7b65488a4ddab62c2f20cbc5626b
+msgid "VPC with public and private gateways and site-to-site VPN access"
+msgstr ""
+
+#: ../../managing_networks.rst:4847
+# 7b5faa4272c845e5abe17edbc0486fc9
+msgid "VPC with a private gateway only and site-to-site VPN access"
+msgstr ""
+
+#: ../../managing_networks.rst:4852
+# 51bfc1cebf464c5bbc3d58dba695d58a
+msgid "You can connect your VPC to:"
+msgstr ""
+
+#: ../../managing_networks.rst:4856
+# a47fa88e4c984151aaf4250a0542efbd
+msgid "The Internet through the public gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:4860
+# 75610d2bcbf3457085a4d69186ac178b
+msgid "The corporate datacenter by using a site-to-site VPN connection through the VPN gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:4865
+# 25f83464cf7d423f89842ec7bb5b2427
+msgid "Both the Internet and your corporate datacenter by using both the public gateway and a VPN gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:4871
+# b4a8939012bd4d57becfcf7bf2b208b7
+msgid "Consider the following before you create a VPC:"
+msgstr ""
+
+#: ../../managing_networks.rst:4875
+# 8f4b07dab7f74e4e84325dfa7c3fb31a
+msgid "A VPC, by default, is created in the enabled state."
+msgstr ""
+
+#: ../../managing_networks.rst:4879
+# e0eddf322bcc4f58899c1d0ec98ff3a6
+msgid "A VPC can be created in Advance zone only, and can't belong to more than one zone at a time."
+msgstr ""
+
+#: ../../managing_networks.rst:4884
+# 94e822d9f9f4432183d26a7458ee0a7b
+msgid "The default number of VPCs an account can create is 20. However, you can change it by using the max.account.vpcs global parameter, which controls the maximum number of VPCs an account is allowed to create."
+msgstr ""
+
+#: ../../managing_networks.rst:4890
+# ba83295468c54bd8ac9701b0ac75e1c6
+msgid "The default number of tiers an account can create within a VPC is 3. You can configure this number by using the vpc.max.networks parameter."
+msgstr ""
+
+#: ../../managing_networks.rst:4896
+# b3365ac8ef2d4de2a5bdcdcadcb9df03
+msgid "Each tier should have an unique CIDR in the VPC. Ensure that the tier's CIDR should be within the VPC CIDR range."
+msgstr ""
+
+#: ../../managing_networks.rst:4901
+# 4482ffae03974738b00591ed147ac312
+msgid "A tier belongs to only one VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:4905
+# 33f875bfaa2f449eab177c836ba3e595
+msgid "All network tiers inside the VPC should belong to the same account."
+msgstr ""
+
+#: ../../managing_networks.rst:4909
+# 381f803ea9004045ab58f5d055f536c7
+msgid "When a VPC is created, by default, a SourceNAT IP is allocated to it. The Source NAT IP is released only when the VPC is removed."
+msgstr ""
+
+#: ../../managing_networks.rst:4914
+# 428718bf75c8495b9390710e65fbbdff
+msgid "A public IP can be used for only one purpose at a time. If the IP is a sourceNAT, it cannot be used for StaticNAT or port forwarding."
+msgstr ""
+
+#: ../../managing_networks.rst:4919
+# 38bd1f10ec864e648bba9fae452daf4a
+msgid "The instances can only have a private IP address that you provision. To communicate with the Internet, enable NAT to an instance that you launch in your VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:4925
+# b39e4604f3bd46c9ae5b2bb9ea9b9ed8
+msgid "Only new networks can be added to a VPC. The maximum number of networks per VPC is limited by the value you specify in the vpc.max.networks parameter. The default value is three."
+msgstr ""
+
+#: ../../managing_networks.rst:4931
+# 82f230ac4a4c4454bebda33b860a5144
+msgid "The load balancing service can be supported by only one tier inside the VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:4936
+# 674409f549534664943c157e86b4751f
+msgid "If an IP address is assigned to a tier:"
+msgstr ""
+
+#: ../../managing_networks.rst:4940
+# fff45697eaa74169a43b238c7cb7d850
+msgid "That IP can't be used by more than one tier at a time in the VPC. For example, if you have tiers A and B, and a public IP1, you can create a port forwarding rule by using the IP either for A or B, but not for both."
+msgstr ""
+
+#: ../../managing_networks.rst:4947
+# bb2829ee8fc143579a544bca2b190a12
+msgid "That IP can't be used for StaticNAT, load balancing, or port forwarding rules for another guest network inside the VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:4952
+# f30c68c2eb624318b01d472bc88fb934
+msgid "Remote access VPN is not supported in VPC networks."
+msgstr ""
+
+#: ../../managing_networks.rst:4955
+# 664f092fb65d4f7eb7b57597dc20eee3
+msgid "Adding a Virtual Private Cloud"
+msgstr ""
+
+#: ../../managing_networks.rst:4957
+# d8f0f8db2b2b48b5993868b9be41e740
+msgid "When creating the VPC, you simply provide the zone and a set of IP addresses for the VPC network address space. You specify this set of addresses in the form of a Classless Inter-Domain Routing (CIDR) block."
+msgstr ""
+
+#: ../../managing_networks.rst:4975
+# 68e44a29c9cd46b3814ef56e13a45415
+msgid "Click Add VPC. The Add VPC page is displayed as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:4977
+# 663db894b6d44e05bad28dd1cf0ff9b4
+msgid "|add-vpc.png: adding a vpc.|"
+msgstr ""
+
+#: ../../managing_networks.rst:4983
+# 9b71ee6298ad4ff8b3677dd885a61d39
+msgid "**Name**: A short name for the VPC that you are creating."
+msgstr ""
+
+#: ../../managing_networks.rst:4987
+# 4aa804d3171d4eb8a0a95651b83f5c29
+msgid "**Description**: A brief description of the VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:4991
+# f4eeaac96959486781023464ab4c5c24
+msgid "**Zone**: Choose the zone where you want the VPC to be available."
+msgstr ""
+
+#: ../../managing_networks.rst:4995
+# 990e793a0bc5420baa6b59dd61e90efe
+msgid "**Super CIDR for Guest Networks**: Defines the CIDR range for all the tiers (guest networks) within a VPC. When you create a tier, ensure that its CIDR is within the Super CIDR value you enter. The CIDR must be RFC1918 compliant."
+msgstr ""
+
+#: ../../managing_networks.rst:5002
+# 4af670c01148481cb56fc6fee83bdcb1
+msgid "**DNS domain for Guest Networks**: If you want to assign a special domain name, specify the DNS suffix. This parameter is applied to all the tiers within the VPC. That implies, all the tiers you create in the VPC belong to the same DNS domain. If the parameter is not specified, a DNS domain name is generated automatically."
+msgstr ""
+
+#: ../../managing_networks.rst:5010
+# 990485d745a04f93926573a279396d9b
+msgid "**Public Load Balancer Provider**: You have two options: VPC Virtual Router and Netscaler."
+msgstr ""
+
+#: ../../managing_networks.rst:5018
+# 23e6b6bbbd57448185253c915b8ad5f0
+msgid "Adding Tiers"
+msgstr ""
+
+#: ../../managing_networks.rst:5020
+# ff39814e4cfe42168898bec95c63bd64
+msgid "Tiers are distinct locations within a VPC that act as isolated networks, which do not have access to other tiers by default. Tiers are set up on different VLANs that can communicate with each other by using a virtual router. Tiers provide inexpensive, low latency network connectivity to other tiers within the VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:5038
+#: ../../managing_networks.rst:6682
+# 112dec95edd24541b50be348ca4879f1
+# d6583ef8f25f444f92aa0c16debd9ba7
+msgid "All the VPC that you have created for the account is listed in the page."
+msgstr ""
+
+#: ../../managing_networks.rst:5041
+# 6b489291378641d99c7e3dfc771af3de
+msgid "The end users can see their own VPCs, while root and domain admin can see any VPC they are authorized to see."
+msgstr ""
+
+#: ../../managing_networks.rst:5045
+#: ../../managing_networks.rst:6687
+# 4996cd7a3c8e49ce842db18908305e3e
+# ee5e856c97144914852fcc5b7106e740
+msgid "Click the Configure button of the VPC for which you want to set up tiers."
+msgstr ""
+
+#: ../../managing_networks.rst:5050
+# f345aeb0c14d4ebe9c779e4ef8d45a80
+msgid "Click Create network."
+msgstr ""
+
+#: ../../managing_networks.rst:5052
+# a138378a695c4ffb85e071e4e5668647
+msgid "The Add new tier dialog is displayed, as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:5054
+# 5e067e1a2c184e638b51030209dcd153
+msgid "|add-tier.png: adding a tier to a vpc.|"
+msgstr ""
+
+#: ../../managing_networks.rst:5056
+# 42a84e496afd4a909af40619de500c02
+msgid "If you have already created tiers, the VPC diagram is displayed. Click Create Tier to add a new tier."
+msgstr ""
+
+#: ../../managing_networks.rst:5067
+# 95298a50ccd3433a8ea1f2fed9df787d
+msgid "**Name**: A unique name for the tier you create."
+msgstr ""
+
+#: ../../managing_networks.rst:5071
+# a6969eda2b5e4e61b5520e0c523e7064
+msgid "**Network Offering**: The following default network offerings are listed: Internal LB, DefaultIsolatedNetworkOfferingForVpcNetworksNoLB, DefaultIsolatedNetworkOfferingForVpcNetworks"
+msgstr ""
+
+#: ../../managing_networks.rst:5076
+# 9963ce9168d74acaaf8ab3c9289533c2
+msgid "In a VPC, only one tier can be created by using LB-enabled network offering."
+msgstr ""
+
+#: ../../managing_networks.rst:5088
+# 9a666245953b4d769667d62a479655f8
+msgid "**VLAN**: The VLAN ID for the tier that the root admin creates."
+msgstr ""
+
+#: ../../managing_networks.rst:5090
+# 43718c048f834c0fbbe95d0255e600b2
+msgid "This option is only visible if the network offering you selected is VLAN-enabled."
+msgstr ""
+
+#: ../../managing_networks.rst:5093
+# e984dca5699d49549e497366d7fa6cfa
+msgid "For more information, see the Assigning VLANs to Isolated Networks section in the CloudStack Administration Guide."
+msgstr ""
+
+#: ../../managing_networks.rst:5110
+# fd0893c5f3f244cd959a9e3da04a3244
+msgid "Continue with configuring access control list for the tier."
+msgstr ""
+
+#: ../../managing_networks.rst:5113
+# 9ecb7309fd5044a7b9252ea6777743d3
+msgid "Configuring Network Access Control List"
+msgstr ""
+
+#: ../../managing_networks.rst:5115
+# f8bec17b79944b3c941a1ba25d55f57c
+msgid "Define Network Access Control List (ACL) on the VPC virtual router to control incoming (ingress) and outgoing (egress) traffic between the VPC tiers, and the tiers and Internet. By default, all incoming traffic to the guest networks is blocked and all outgoing traffic from guest networks is allowed, once you add an ACL rule for outgoing traffic, then only outgoing traffic specified in this ACL rule is allowed, the rest is blocked. To open the ports, you must create a new network ACL. The network ACLs can be created for the tiers only if the NetworkACL service is supported."
+msgstr ""
+
+#: ../../managing_networks.rst:5126
+# 883738de9a0f4f9cb19d5381137f41b7
+msgid "About Network ACL Lists"
+msgstr ""
+
+#: ../../managing_networks.rst:5128
+# 0013030c60f54306b754480ec7cd56ee
+msgid "In CloudStack terminology, Network ACL is a group of Network ACL items. Network ACL items are nothing but numbered rules that are evaluated in order, starting with the lowest numbered rule. These rules determine whether traffic is allowed in or out of any tier associated with the network ACL. You need to add the Network ACL items to the Network ACL, then associate the Network ACL with a tier. Network ACL is associated with a VPC and can be assigned to multiple VPC tiers within a VPC. A Tier is associated with a Network ACL at all the times. Each tier can be associated with only one ACL."
+msgstr ""
+
+#: ../../managing_networks.rst:5138
+# cd30ab4ab3de4e19944373cf3ad29ee4
+msgid "The default Network ACL is used when no ACL is associated. Default behavior is all the incoming traffic is blocked and outgoing traffic is allowed from the tiers. Default network ACL cannot be removed or modified. Contents of the default Network ACL is:"
+msgstr ""
+
+#: ../../managing_networks.rst:5144
+# 0ffe15ce91bb46a181dd0f5f4352b037
+msgid "Rule"
+msgstr ""
+
+#: ../../managing_networks.rst:5144
+# fd278173e97b408ab779ea644ba8c05b
+msgid "Protocol"
+msgstr ""
+
+#: ../../managing_networks.rst:5144
+# c8650729b8784c91b63c3256b2a6da0c
+msgid "Traffic type"
+msgstr ""
+
+#: ../../managing_networks.rst:5144
+# 32be36b683c640f6bcb229e524bd7249
+msgid "Action"
+msgstr ""
+
+#: ../../managing_networks.rst:5146
+#: ../../managing_networks.rst:5147
+# e2de15ead8bd422c873fa6c50b4a42a9
+# b05631934bf140be841f32970809a285
+msgid "All"
+msgstr ""
+
+#: ../../managing_networks.rst:5146
+# 8449d6b79ab54e9a9399ccd13ab059ef
+msgid "Ingress"
+msgstr ""
+
+#: ../../managing_networks.rst:5146
+#: ../../managing_networks.rst:5147
+# 1eeb4aa87118496eb955beec9206e674
+# bb21769e9775425ab94a56a56b43cba9
+msgid "0.0.0.0/0"
+msgstr ""
+
+#: ../../managing_networks.rst:5147
+# bd09cdb155ae4f8887094159bb0b7ebc
+msgid "Egress"
+msgstr ""
+
+#: ../../managing_networks.rst:5152
+# d149d46d02694b94a0f6d46db5982fb2
+msgid "Creating ACL Lists"
+msgstr ""
+
+#: ../../managing_networks.rst:5215
+#: ../../managing_networks.rst:5257
+# b101c0f175594179ac9f4f323f335d7d
+# 2154f606bc904937a85a8fc00bbf23b5
+msgid "Select Network ACL Lists."
+msgstr ""
+
+#: ../../managing_networks.rst:5217
+# 517402dccaae4fa1befd493301ea949d
+msgid "The following default rules are displayed in the Network ACLs page: default\\_allow, default\\_deny."
+msgstr ""
+
+#: ../../managing_networks.rst:5222
+# 37dadcca056740d98d2f961f0f2c17b1
+msgid "Click Add ACL Lists, and specify the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:5226
+# ec72127f5c594aa88546a51a9805357b
+msgid "**ACL List Name**: A name for the ACL list."
+msgstr ""
+
+#: ../../managing_networks.rst:5230
+# 4cd0a64154f14244bc624f4c6a44ba55
+msgid "**Description**: A short description of the ACL list that can be displayed to users."
+msgstr ""
+
+#: ../../managing_networks.rst:5234
+# 799d333035784cebbc2ca6c0f6b13302
+msgid "Creating an ACL Rule"
+msgstr ""
+
+#: ../../managing_networks.rst:5259
+# a408d9b21c4d4e77bc436d240b7e2d85
+msgid "In addition to the custom ACL lists you have created, the following default rules are displayed in the Network ACLs page: default\\_allow, default\\_deny."
+msgstr ""
+
+#: ../../managing_networks.rst:5265
+#: ../../managing_networks.rst:5390
+# fc49dc48022a4e5d8e7ede413dce0a42
+# 4d7fc5b5b8474ee9ab87791bb3046cc3
+msgid "Select the desired ACL list."
+msgstr ""
+
+#: ../../managing_networks.rst:5269
+# aa57fa68748b4e6cb1571d8c78b4cb13
+msgid "Select the ACL List Rules tab."
+msgstr ""
+
+#: ../../managing_networks.rst:5271
+# e11ef52e1bd54820a55d90c66c4566b3
+msgid "To add an ACL rule, fill in the following fields to specify what kind of network traffic is allowed in the VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:5276
+# c1b746e2fd69497a9973a9c4dda74961
+msgid "**Rule Number**: The order in which the rules are evaluated."
+msgstr ""
+
+#: ../../managing_networks.rst:5280
+# 755200e08f8b410db152ea927ecdca34
+msgid "**CIDR**: The CIDR acts as the Source CIDR for the Ingress rules, and Destination CIDR for the Egress rules. To accept traffic only from or 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 incoming traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr ""
+
+#: ../../managing_networks.rst:5289
+# 6bbf467d779940e1aab67d2c17766733
+msgid "**Action**: What action to be taken. Allow traffic or block."
+msgstr ""
+
+#: ../../managing_networks.rst:5293
+# 0276a8206f3045e5899fcfef28a96a45
+msgid "**Protocol**: The networking protocol that sources use to send traffic to the tier. 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. All supports all the traffic. Other option is Protocol Number."
+msgstr ""
+
+#: ../../managing_networks.rst:5302
+# 5d95d28eac034c5c916ed60985a61d21
+msgid "**Start Port**, **End Port** (TCP, UDP only): A range of listening ports that are the destination for the incoming traffic. If you are opening a single port, use the same number in both fields."
+msgstr ""
+
+#: ../../managing_networks.rst:5308
+# 08af29136df449deaa80cb9658d340f6
+msgid "**Protocol Number**: The protocol number associated with IPv4 or IPv6. For more information, see `Protocol Numbers <http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xml>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:5314
+# ace82b72ecd94c41acc8598b519e2d14
+msgid "**ICMP Type**, **ICMP Code** (ICMP only): The type of message and error code that will be sent."
+msgstr ""
+
+#: ../../managing_networks.rst:5319
+# 2a8d8f3558b04c418b77c1f1b7e72d85
+msgid "**Traffic Type**: The type of traffic: Incoming or outgoing."
+msgstr ""
+
+#: ../../managing_networks.rst:5323
+# 9e09340a2c044bbdb9ca933949254900
+msgid "Click Add. The ACL rule is added."
+msgstr ""
+
+#: ../../managing_networks.rst:5325
+# 1968e40aada04c1db4e857f65930370d
+msgid "You can edit the tags assigned to the ACL rules and delete the ACL rules you have created. Click the appropriate button in the Details tab."
+msgstr ""
+
+#: ../../managing_networks.rst:5330
+# fff83eb96ab44a699a972bce5ef45a04
+msgid "Creating a Tier with Custom ACL List"
+msgstr ""
+
+#: ../../managing_networks.rst:5334
+#: ../../managing_networks.rst:5359
+# f12e2dba06944099b85dd1ea004364d5
+# e18fc8b196b0486fb6cd03a19e76a01d
+msgid "Create a VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:5338
+#: ../../managing_networks.rst:5371
+# 6e0ed40f7fef470a89d1362b855c619d
+# 4a20f18e2e3f41059234087d027679ce
+msgid "Create a custom ACL list."
+msgstr ""
+
+#: ../../managing_networks.rst:5342
+#: ../../managing_networks.rst:5375
+# b5b4a3b8580a4383b65681e22188b976
+# 54db75d977d64c6d911dbe6f4742e0f2
+msgid "Add ACL rules to the ACL list."
+msgstr ""
+
+#: ../../managing_networks.rst:5346
+#: ../../managing_networks.rst:5363
+# e11c0a6e179d4cbab03f5e4df6b0d34c
+# 22398c60ca484e6f95dd827641a3ebbc
+msgid "Create a tier in the VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:5348
+# 99892b8596be4b2285f7bb8edfb191a2
+msgid "Select the desired ACL list while creating a tier."
+msgstr ""
+
+#: ../../managing_networks.rst:5355
+# 2c486359bfd24312a59e5fd1dd7bc71d
+msgid "Assigning a Custom ACL List to a Tier"
+msgstr ""
+
+#: ../../managing_networks.rst:5367
+# 05e3fc39d3e94c7f829ec8cb6046bc61
+msgid "Associate the tier with the default ACL rule."
+msgstr ""
+
+#: ../../managing_networks.rst:5379
+# 156229b3ab074f9c9a49d3d9c53d6b52
+msgid "Select the tier for which you want to assign the custom ACL."
+msgstr ""
+
+#: ../../managing_networks.rst:5383
+# 33c7f407412544c3bd8dc80b0deb4108
+msgid "Click the Replace ACL List icon. |replace-acl-icon.png: button to replace an ACL list|"
+msgstr ""
+
+#: ../../managing_networks.rst:5386
+# 769a8ffc3b73478994f18f35ad3a4f97
+msgid "The Replace ACL List dialog is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:5397
+# 59b868549d104d3a80e798178bdef667
+msgid "Adding a Private Gateway to a VPC"
+msgstr ""
+
+#: ../../managing_networks.rst:5399
+# 67c51696fdc0490ebeaa99b6e4bfc5bd
+msgid "A private gateway can be added by the root admin only. The VPC private network has 1:1 relationship with the NIC of the physical network. You can configure multiple private gateways to a single VPC. No gateways with duplicated VLAN and IP are allowed in the same data center."
+msgstr ""
+
+#: ../../managing_networks.rst:5421
+# d5835ef9009f4c14873cc04a1210faa0
+msgid "Click the Configure button of the VPC to which you want to configure load balancing rules."
+msgstr ""
+
+#: ../../managing_networks.rst:5431
+#: ../../managing_networks.rst:5756
+#: ../../managing_networks.rst:5843
+# 5efaa5f18c7844a4b06a038676b273df
+# 36ecb777b69f4c269f586a8a44a42c4a
+# 4244a80585044c06abd14959aa47e3f8
+msgid "The following options are displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:5473
+# c0a219ae8fd5473d87a77217b9d95417
+msgid "Select Private Gateways."
+msgstr ""
+
+#: ../../managing_networks.rst:5475
+# 497c5bbf4ce4494b984d67f98954deab
+msgid "The Gateways page is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:5479
+# cdead55635a740399b023f2897b98f59
+msgid "Click Add new gateway:"
+msgstr ""
+
+#: ../../managing_networks.rst:5481
+# 6eb77c1dc83c4cfe938dfc899ea6e662
+msgid "|add-new-gateway-vpc.png: adding a private gateway for the VPC.|"
+msgstr ""
+
+#: ../../managing_networks.rst:5489
+# afb65eddf4dd4dc182850cdc8514f923
+msgid "**Physical Network**: The physical network you have created in the zone."
+msgstr ""
+
+#: ../../managing_networks.rst:5494
+# e7b58bd2dff34b0db44aab8f2c6245b2
+msgid "**IP Address**: The IP address associated with the VPC gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:5498
+# 8129fbaeec504b9b945efb8751c45385
+msgid "**Gateway**: The gateway through which the traffic is routed to and from the VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:5503
+# a4c3555b968349dfa818e2dbdc7c3d53
+msgid "**Netmask**: The netmask associated with the VPC gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:5507
+# 4dce5e993ebf4265bd2bbb586e92c0f3
+msgid "**VLAN**: The VLAN associated with the VPC gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:5511
+# a5003a0c62a64833880757bd344cfde7
+msgid "**Source NAT**: Select this option to enable the source NAT service on the VPC private gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:5514
+# dff3c56b7ec649b589e8eafd8e54c7cb
+msgid "See `Section 15.27.5.1, “Source NAT on Private Gateway” <#sourcenat-private-gateway>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:5519
+# 1ff567af8cf94d3b84320755c4d26a66
+msgid "**ACL**: Controls both ingress and egress traffic on a VPC private gateway. By default, all the traffic is blocked."
+msgstr ""
+
+#: ../../managing_networks.rst:5522
+# 263e367da63e46a9aa8da7d287bc896f
+msgid "See `Section 15.27.5.2, “ACL on Private Gateway” <#acl-private-gateway>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:5525
+# 0072a51b25fc4a4aa66d298ded9a2dde
+msgid "The new gateway appears in the list. You can repeat these steps to add more gateway for this VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:5529
+# 1a944440570641ed8d9890edc77c64c5
+msgid "Source NAT on Private Gateway"
+msgstr ""
+
+#: ../../managing_networks.rst:5531
+# 43aa869828e5461a8a13530f7a2aa2f7
+msgid "You might want to deploy multiple VPCs with the same super CIDR and guest tier CIDR. Therefore, multiple guest VMs from different VPCs can have the same IPs to reach a enterprise data center through the private gateway. In such cases, a NAT service need to be configured on the private gateway to avoid IP conflicts. If Source NAT is enabled, the guest VMs in VPC reaches the enterprise network via private gateway IP address by using the NAT service."
+msgstr ""
+
+#: ../../managing_networks.rst:5539
+# e2714f79ffd947d9bdc572874ffd2c73
+msgid "The Source NAT service on a private gateway can be enabled while adding the private gateway. On deletion of a private gateway, source NAT rules specific to the private gateway are deleted."
+msgstr ""
+
+#: ../../managing_networks.rst:5543
+# ee2bf2c268b940968dd021c6ea6bcf74
+msgid "To enable source NAT on existing private gateways, delete them and create afresh with source NAT."
+msgstr ""
+
+#: ../../managing_networks.rst:5547
+# 8de7fa9065814573b42b74b294a1179f
+msgid "ACL on Private Gateway"
+msgstr ""
+
+#: ../../managing_networks.rst:5549
+# f450e126ceeb4644a55586ad466152c4
+msgid "The traffic on the VPC private gateway is controlled by creating both ingress and egress network ACL rules. The ACLs contains both allow and deny rules. As per the rule, all the ingress traffic to the private gateway interface and all the egress traffic out from the private gateway interface are blocked."
+msgstr ""
+
+#: ../../managing_networks.rst:5555
+# ee6a2bab124748009cd09599eaa13e71
+msgid "You can change this default behaviour while creating a private gateway. Alternatively, you can do the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:5560
+#: ../../managing_networks.rst:5606
+# 21f974b13ca54ebdaeac3568315356d1
+# 6a4b79956d78436989546151b5bd0458
+msgid "In a VPC, identify the Private Gateway you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:5564
+# b8c1c66de4bf4c979f0479ea431d3df0
+msgid "In the Private Gateway page, do either of the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:5568
+# 49b0c682192f4b459125d724b4a1b265
+msgid "Use the Quickview. See `3 <#quickview>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:5572
+# d4a946a973cc49888562b872780d8601
+msgid "Use the Details tab. See `4 <#details-tab>`__ through ."
+msgstr ""
+
+#: ../../managing_networks.rst:5576
+# 19cbd09f46ab46db8404fda0e23cb619
+msgid "In the Quickview of the selected Private Gateway, click Replace ACL, select the ACL rule, then click OK"
+msgstr ""
+
+#: ../../managing_networks.rst:5581
+# afeaf13ba42447798385c602c1c688fe
+msgid "Click the IP address of the Private Gateway you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:5585
+# 20ba5a3f04344df0a86ab32ad173edd6
+msgid "In the Detail tab, click the Replace ACL button. |replace-acl-icon.png: button to replace the default ACL behaviour.|"
+msgstr ""
+
+#: ../../managing_networks.rst:5588
+# 01e0bd4df2fd4ee4a00bcf20bc341c5d
+msgid "The Replace ACL dialog is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:5592
+# 3f32278673d446f0b2c1b958c13ac401
+msgid "select the ACL rule, then click OK."
+msgstr ""
+
+#: ../../managing_networks.rst:5594
+# ae950e90184a491381c91aaff688aa76
+msgid "Wait for few seconds. You can see that the new ACL rule is displayed in the Details page."
+msgstr ""
+
+#: ../../managing_networks.rst:5598
+# 4a0dd026907d41858599558136fffe1a
+msgid "Creating a Static Route"
+msgstr ""
+
+#: ../../managing_networks.rst:5600
+# 5033ea030ac64d85b8313ada101574ec
+msgid "CloudStack enables you to specify routing for the VPN connection you create. You can enter one or CIDR addresses to indicate which traffic is to be routed back to the gateway."
+msgstr ""
+
+#: ../../managing_networks.rst:5610
+# 1659fdcef3844d84ab74183505608fbb
+msgid "In the Private Gateway page, click the IP address of the Private Gateway you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:5615
+# f37c03963d3d47d596b85b8e76efbd71
+msgid "Select the Static Routes tab."
+msgstr ""
+
+#: ../../managing_networks.rst:5619
+# aa7e5e9a6f11421abd3b4aadc2e9b32b
+msgid "Specify the CIDR of destination network."
+msgstr ""
+
+#: ../../managing_networks.rst:5625
+# 2b073a139f15411c9cbd0b3f86c913e9
+msgid "Wait for few seconds until the new route is created."
+msgstr ""
+
+#: ../../managing_networks.rst:5628
+# 7a2e407277964cd18757e610c1197596
+msgid "Blacklisting Routes"
+msgstr ""
+
+#: ../../managing_networks.rst:5630
+# a154d3d5488f418e95dbd3c0ae59a55f
+msgid "CloudStack enables you to block a list of routes so that they are not assigned to any of the VPC private gateways. Specify the list of routes that you want to blacklist in the ``blacklisted.routes`` global parameter. Note that the parameter update affects only new static route creations. If you block an existing static route, it remains intact and continue functioning. You cannot add a static route if the route is blacklisted for the zone."
+msgstr ""
+
+#: ../../managing_networks.rst:5639
+# 7f1bbdc7458942d88e89b8e0af49db0c
+msgid "Deploying VMs to the Tier"
+msgstr ""
+
+#: ../../managing_networks.rst:5661
+# 36fffc19e491403389988483ec7271b0
+msgid "The VPC page is displayed where all the tiers you have created are listed."
+msgstr ""
+
+#: ../../managing_networks.rst:5666
+# 9d8ad54e3d3a46e7b8074cc715920531
+msgid "Click Virtual Machines tab of the tier to which you want to add a VM."
+msgstr ""
+
+#: ../../managing_networks.rst:5668
+# ca8838c20d2845659371f93b881a4100
+msgid "|add-vm-vpc.png: adding a VM to a vpc.|"
+msgstr ""
+
+#: ../../managing_networks.rst:5670
+# e5316d71ef404ddbb0d6dad97ba98577
+msgid "The Add Instance page is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:5672
+# 389b274de3d2499f942685dd7cd1173e
+msgid "Follow the on-screen instruction to add an instance. For information on adding an instance, see the Installation Guide."
+msgstr ""
+
+#: ../../managing_networks.rst:5676
+# 9d028d09d4304fb1bf6cca0baa05eb50
+msgid "Deploying VMs to VPC Tier and Shared Networks"
+msgstr ""
+
+#: ../../managing_networks.rst:5678
+# e4ce910a596b41b488b8bf3c9a703ec5
+msgid "CloudStack allows you deploy VMs on a VPC tier and one or more shared networks. With this feature, VMs deployed in a multi-tier application can receive monitoring services via a shared network provided by a service provider."
+msgstr ""
+
+#: ../../managing_networks.rst:5685
+# 9822028ede334e8d9bcb11d4e0b88a24
+msgid "Log in to the CloudStack UI as an administrator."
+msgstr ""
+
+#: ../../managing_networks.rst:5689
+# 334c3d883bcc40f5a9d18da6406e3541
+msgid "In the left navigation, choose Instances."
+msgstr ""
+
+#: ../../managing_networks.rst:5693
+# 9e4739215b6d4023b17334daf1c299d0
+msgid "Click Add Instance."
+msgstr ""
+
+#: ../../managing_networks.rst:5697
+# f3612ab1c69c4e8bafa16290447c849d
+msgid "Select a zone."
+msgstr ""
+
+#: ../../managing_networks.rst:5701
+# 0d5257aa0f5d42759682d5ec4c687946
+msgid "Select a template or ISO, then follow the steps in the wizard."
+msgstr ""
+
+#: ../../managing_networks.rst:5705
+# 5d53f3f14de94f21a72a57c5427947fa
+msgid "Ensure that the hardware you have allows starting the selected service offering."
+msgstr ""
+
+#: ../../managing_networks.rst:5710
+# c7211e930aea482ebbbea2e443cabd53
+msgid "Under Networks, select the desired networks for the VM you are launching."
+msgstr ""
+
+#: ../../managing_networks.rst:5713
+# 355fc2d3a38e43f4ab08b92f9e8f168f
+msgid "You can deploy a VM to a VPC tier and multiple shared networks."
+msgstr ""
+
+#: ../../managing_networks.rst:5715
+# 50da282764bf41938177acb880c846e1
+msgid "|addvm-tier-sharednw.png: adding a VM to a VPC tier and shared network.|"
+msgstr ""
+
+#: ../../managing_networks.rst:5720
+# 602251fcf69447d880ef52b1e43aaeae
+msgid "Click Next, review the configuration and click Launch."
+msgstr ""
+
+#: ../../managing_networks.rst:5722
+# 7b69703360704281ac542fe8d70b98c6
+msgid "Your VM will be deployed to the selected VPC tier and shared network."
+msgstr ""
+
+#: ../../managing_networks.rst:5725
+# fd34602f4c1a482a8d044b849bdeb44b
+msgid "Acquiring a New IP Address for a VPC"
+msgstr ""
+
+#: ../../managing_networks.rst:5727
+# c73360b50aa543f7a8880e610baa5b75
+msgid "When you acquire an IP address, all IP addresses are allocated to VPC, not to the guest networks within the VPC. The IPs are associated to the guest network only when the first port-forwarding, load balancing, or Static NAT rule is created for the IP or the network. IP can't be associated to more than one network at a time."
+msgstr ""
+
+#: ../../managing_networks.rst:5798
+# a44c55b912fa4df183c07b424282c526
+msgid "Select IP Addresses."
+msgstr ""
+
+#: ../../managing_networks.rst:5800
+# 7068202d5e7748aa89b44e99fd7a8c9b
+msgid "The Public IP Addresses page is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:5804
+# 59806f7394b645268a1deaf02e5c8812
+msgid "Click Acquire New IP, and click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../managing_networks.rst:5806
+# 677531dda31f4fe9ba37d4384c2c5672
+msgid "You are prompted for confirmation because, typically, IP addresses are a limited resource. Within a few moments, the new IP address should appear with the state Allocated. You can now use the IP address in port forwarding, load balancing, and static NAT rules."
+msgstr ""
+
+#: ../../managing_networks.rst:5812
+# 55e43c565ebb41158b1743d98edb1b7c
+msgid "Releasing an IP Address Allocated to a VPC"
+msgstr ""
+
+#: ../../managing_networks.rst:5814
+# bd70ff0598d34b229b01650cabc35f3f
+msgid "The IP address is a limited resource. If you no longer need a particular IP, you can disassociate it from its VPC and return it to the pool of available addresses. An IP address can be released from its tier, only when all the networking ( port forwarding, load balancing, or StaticNAT ) rules are removed for this IP address. The released IP address will still belongs to the same VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:5838
+# db06398461444930b595e0160effde58
+msgid "Click the Configure button of the VPC whose IP you want to release."
+msgstr ""
+
+#: ../../managing_networks.rst:5885
+# d80d6b89f43d4b2491743738838b0245
+msgid "Select Public IP Addresses."
+msgstr ""
+
+#: ../../managing_networks.rst:5891
+# 00cc2e1530394ea2838d7f6061a85693
+msgid "Click the IP you want to release."
+msgstr ""
+
+#: ../../managing_networks.rst:5895
+# 15c38333d5564c94a459bd2e93b987b1
+msgid "In the Details tab, click the Release IP button |release-ip-icon.png: button to release an IP.|"
+msgstr ""
+
+#: ../../managing_networks.rst:5899
+# c6a4439513504b019b9fa932df9926b5
+msgid "Enabling or Disabling Static NAT on a VPC"
+msgstr ""
+
+#: ../../managing_networks.rst:5901
+# 2121940a433d4a7c99fe4fcdc04af8a9
+msgid "A static NAT rule maps a public IP address to the private IP address of a VM in a VPC to allow Internet traffic to it. This section tells how to enable or disable static NAT for a particular IP address in a VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:5934
+# 0603bfddfcae43529259bdadc6652cc7
+msgid "For each tier, the following options are displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:5982
+# d9241814450644c28541d121455ddb44
+msgid "Click the IP you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:5986
+# 17ca1f0f3fac45349f2b7536efe21e90
+msgid "In the Details tab,click the Static NAT button. |enable-disable.png: button to enable Static NAT.| The button toggles between Enable and Disable, depending on whether static NAT is currently enabled for the IP address."
+msgstr ""
+
+#: ../../managing_networks.rst:5993
+# 48ec391c037d4513bbbf0e36c099fbd4
+msgid "If you are enabling static NAT, a dialog appears as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:5995
+# 9e8b3f52b98a4950a87c8525e6c7b27f
+msgid "|select-vmstatic-nat.png: selecting a tier to apply staticNAT.|"
+msgstr ""
+
+#: ../../managing_networks.rst:5999
+# 18f46f5fdcb0449dac6fdfaf2f51ce14
+msgid "Select the tier and the destination VM, then click Apply."
+msgstr ""
+
+#: ../../managing_networks.rst:6002
+# fb5ca551d8c94e579cd6bb1147727ab7
+msgid "Adding Load Balancing Rules on a VPC"
+msgstr ""
+
+#: ../../managing_networks.rst:6004
+# c4883c83508d432bb165cab6bc1de860
+msgid "In a VPC, you can configure two types of load balancing—external LB and internal LB. External LB is nothing but a LB rule created to redirect the traffic received at a public IP of the VPC virtual router. The traffic is load balanced within a tier based on your configuration. Citrix NetScaler and VPC virtual router are supported for external LB. When you use internal LB service, traffic received at a tier is load balanced across different VMs within that tier. For example, traffic reached at Web tier is redirected to another VM in that tier. External load balancing devices are not supported for internal LB. The service is provided by a internal LB VM configured on the target tier."
+msgstr ""
+
+#: ../../managing_networks.rst:6016
+# 274bc30ffbcf44b9ba1abd732541215a
+msgid "Load Balancing Within a Tier (External LB)"
+msgstr ""
+
+#: ../../managing_networks.rst:6018
+# caa659885dfa4cd6904a918177c53c5e
+msgid "A CloudStack user or administrator may create load balancing rules that balance traffic received at a public IP to one or more VMs that belong to a network tier that provides load balancing service in a VPC. A user creates a rule, specifies an algorithm, and assigns the rule to a set of VMs within a tier."
+msgstr ""
+
+#: ../../managing_networks.rst:6025
+# 5c807fdb6ce04f699eb08495407e8d92
+msgid "Enabling NetScaler as the LB Provider on a VPC Tier"
+msgstr ""
+
+#: ../../managing_networks.rst:6029
+# 9cc8f348801d45418744e7f42218d907
+msgid "Add and enable Netscaler VPX in dedicated mode."
+msgstr ""
+
+#: ../../managing_networks.rst:6031
+# ed6339be814f45398c36a2ef4ec785d2
+msgid "Netscaler can be used in a VPC environment only if it is in dedicated mode."
+msgstr ""
+
+#: ../../managing_networks.rst:6036
+# 4662e3fb38414b75bdfa2ae89c5b4d54
+msgid "Create a network offering, as given in `Section 15.27.11.1.2, “Creating a Network Offering for External LB” <#ext-lb-offering>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:6041
+# 648bc307e8724c0c808a7e169d7174af
+msgid "Create a VPC with Netscaler as the Public LB provider."
+msgstr ""
+
+#: ../../managing_networks.rst:6043
+# 6f2968514fa14e198e27a6276559ac66
+msgid "For more information, see `Section 15.27.2, “Adding a Virtual Private Cloud” <#add-vpc>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:6048
+# 34834931a616401fbf2114397a66c17d
+msgid "For the VPC, acquire an IP."
+msgstr ""
+
+#: ../../managing_networks.rst:6052
+# 73121096c9c0491b872f089f4bcd646d
+msgid "Create an external load balancing rule and apply, as given in `Section 15.27.11.1.3, “Creating an External LB Rule” <#ext-lb-vpc>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:6057
+# 2772e2e5e8bc4ff585c238022e2de08d
+msgid "Creating a Network Offering for External LB"
+msgstr ""
+
+#: ../../managing_networks.rst:6059
+# 9321f241035849579eee2b19a8dcd3a7
+msgid "To have external LB support on VPC, create a network offering as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:6064
+#: ../../managing_networks.rst:6368
+# 2aab6b8694d14a2d81304515d063ea70
+# 9547796b012c45c0a0bce3e170167fa4
+msgid "Log in to the CloudStack UI as a user or admin."
+msgstr ""
+
+#: ../../managing_networks.rst:6068
+#: ../../managing_networks.rst:6372
+# 98791665f6d04be48656066993e3c5e0
+# 894f16f3b18145cfad928d595039b36a
+msgid "From the Select Offering drop-down, choose Network Offering."
+msgstr ""
+
+#: ../../managing_networks.rst:6076
+#: ../../managing_networks.rst:6380
+# a4c57841d2274a45a1949e1ba43a5d78
+# e1065316da8a4206a4c9926b89da3869
+msgid "In the dialog, make the following choices:"
+msgstr ""
+
+#: ../../managing_networks.rst:6080
+#: ../../managing_networks.rst:6384
+# 6a3430b8741e423b83efc13c9e7e6e88
+# 236dc341b9214a589a7e812fd2f4c60b
+msgid "**Name**: Any desired name for the network offering."
+msgstr ""
+
+#: ../../managing_networks.rst:6084
+#: ../../managing_networks.rst:6388
+# 76031673ac254ec7bfb535779e98ebb4
+# bccec46599994c2a95a0569047967aa7
+msgid "**Description**: A short description of the offering that can be displayed to users."
+msgstr ""
+
+#: ../../managing_networks.rst:6089
+#: ../../managing_networks.rst:6393
+# 2bab7aa63c61409191de6c7949b17cf4
+# 351d020a9f044f52a3dd389bff437e65
+msgid "**Network Rate**: Allowed data transfer rate in MB per second."
+msgstr ""
+
+#: ../../managing_networks.rst:6093
+#: ../../managing_networks.rst:6397
+# 79ce2fd95ec04bcfa12787a70171f1fb
+# a40a99e105f943e69806fc3e1db63326
+msgid "**Traffic Type**: The type of network traffic that will be carried on the network."
+msgstr ""
+
+#: ../../managing_networks.rst:6098
+#: ../../managing_networks.rst:6402
+# d6c6b623f9f04f3997c8dbd87ee79e96
+# 0a18bda8137545e392cca4356df398f3
+msgid "**Guest Type**: Choose whether the guest network is isolated or shared."
+msgstr ""
+
+#: ../../managing_networks.rst:6103
+#: ../../managing_networks.rst:6407
+# ca6a4c29a1694890b3c2c8ce9114cac1
+# 89df6c51bfee49629ef336a867cc8a40
+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."
+msgstr ""
+
+#: ../../managing_networks.rst:6109
+#: ../../managing_networks.rst:6413
+# e799f2ee1f1942f1a80c328ac3f22ba2
+# d7d42b1bb3754b0786713cf979e06172
+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 `Section 15.27.1, “About Virtual Private Clouds” <#vpc>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:6118
+#: ../../managing_networks.rst:6422
+# c1cb78a9d442425ca2861f09ccb822d0
+# b44e7a69782a468ebc6a1b0b2b58b67a
+msgid "**Specify VLAN**: (Isolated guest networks only) Indicate whether a VLAN should be specified when this offering is used."
+msgstr ""
+
+#: ../../managing_networks.rst:6123
+# 83f03954d4aa40fcb0269bb949898281
+msgid "**Supported Services**: Select Load Balancer. Use Netscaler or VpcVirtualRouter."
+msgstr ""
+
+#: ../../managing_networks.rst:6128
+# 3ecd5594fecf4e7996fc00073a3af317
+msgid "**Load Balancer Type**: Select Public LB from the drop-down."
+msgstr ""
+
+#: ../../managing_networks.rst:6132
+# c780a4651b0540c99bc39f9057d781d5
+msgid "**LB Isolation**: Select Dedicated if Netscaler is used as the external LB provider."
+msgstr ""
+
+#: ../../managing_networks.rst:6137
+#: ../../managing_networks.rst:6436
+# 5a521e9e6e424ed8a6e6e8878254fb05
+# 0e1a57030f0e4d1c9f91421d3bfcf073
+msgid "**System Offering**: Choose the system service offering that you want virtual routers to use in this network."
+msgstr ""
+
+#: ../../managing_networks.rst:6142
+#: ../../managing_networks.rst:6441
+# 3da1b26048d246e8be963accb23a2d59
+# 303be976fe7a41a0a5a3b299ba7d1cc2
+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."
+msgstr ""
+
+#: ../../managing_networks.rst:6148
+#: ../../managing_networks.rst:6447
+# 97f1c8686f464c2a86f667e59bc3613d
+# 21d33f3ed7b842139317fe1ba0d2bad4
+msgid "Click OK and the network offering is created."
+msgstr ""
+
+#: ../../managing_networks.rst:6151
+# b85666bb2b034e90b3623ac0d974bcf8
+msgid "Creating an External LB Rule"
+msgstr ""
+
+#: ../../managing_networks.rst:6170
+# 46a6c7a9c87b4d0b86e5096cf8387352
+msgid "Click the Configure button of the VPC, for which you want to configure load balancing rules."
+msgstr ""
+
+#: ../../managing_networks.rst:6173
+#: ../../managing_networks.rst:6481
+# 04979eda5aad402e9e9ed07b06b83d07
+# 29d52ff8bfd845898927bc69c03ba1cc
+msgid "The VPC page is displayed where all the tiers you created listed in a diagram."
+msgstr ""
+
+#: ../../managing_networks.rst:6233
+#: ../../managing_networks.rst:6625
+# 841ec4a089094a18a44d829fe3992d40
+# d19cbf96b77b4284b01fe504101489d6
+msgid "Select the tier to which you want to apply the rule."
+msgstr ""
+
+#: ../../managing_networks.rst:6245
+# 7de910c468f6402a8dfb73f99ce85bfa
+msgid "**Public Port**: The port that receives the incoming traffic to be balanced."
+msgstr ""
+
+#: ../../managing_networks.rst:6255
+#: ../../managing_networks.rst:6526
+# 0e6242e8303c4f7e81f3bacd632286c4
+# 873adeb9135b4671ac55ba8bb02eefd4
+msgid "**Algorithm**. Choose the load balancing algorithm you want CloudStack to use. CloudStack supports the following well-known algorithms:"
+msgstr ""
+
+#: ../../managing_networks.rst:6265
+#: ../../managing_networks.rst:6536
+# 032bda374e3549389055ef99602dbfde
+# 76d0d6a66f964932a632e62d7f72d63a
+msgid "Least connections"
+msgstr ""
+
+#: ../../managing_networks.rst:6269
+#: ../../managing_networks.rst:6540
+# 0b3a293fff7f42d59c589be7157bf55b
+# a39fd2d8c4994240b02094dbf235ff35
+msgid "Source"
+msgstr ""
+
+#: ../../managing_networks.rst:6273
+# 5ad7247668c740d59840d3cfa7af1ba4
+msgid "**Stickiness**. (Optional) Click Configure and choose the algorithm for the stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr ""
+
+#: ../../managing_networks.rst:6279
+# cf38cdef27f14c3399aa3f98bb975b0e
+msgid "**Add VMs**: Click Add VMs, then select two or more VMs that will divide the load of incoming traffic, and click Apply."
+msgstr ""
+
+#: ../../managing_networks.rst:6282
+# 3125a1633b73432dbbc695b80203f711
+msgid "The new load balancing rule appears in the list. You can repeat these steps to add more load balancing rules for this IP address."
+msgstr ""
+
+#: ../../managing_networks.rst:6286
+# 5cd14774a90e437eb620b313651c9e46
+msgid "Load Balancing Across Tiers"
+msgstr ""
+
+#: ../../managing_networks.rst:6288
+# 070e7b9f10a44c47953a80c046d9c7ca
+msgid "CloudStack supports sharing workload across different tiers within your VPC. Assume that multiple tiers are set up in your environment, such as Web tier and Application tier. Traffic to each tier is balanced on the VPC virtual router on the public side, as explained in `Section 15.27.11, “Adding Load Balancing Rules on a VPC” <#add-loadbalancer-rule-vpc>`__. If you want the traffic coming from the Web tier to the Application tier to be balanced, use the internal load balancing feature offered by CloudStack."
+msgstr ""
+
+#: ../../managing_networks.rst:6298
+# aea9258cc6164c4fb587a9e5d2abc852
+msgid "How Does Internal LB Work in VPC?"
+msgstr ""
+
+#: ../../managing_networks.rst:6300
+# b574228e607e400d88167d7478911df8
+msgid "In this figure, a public LB rule is created for the public IP 72.52.125.10 with public port 80 and private port 81. The LB rule, created on the VPC virtual router, is applied on the traffic coming from the Internet to the VMs on the Web tier. On the Application tier two internal load balancing rules are created. An internal LB rule for the guest IP 10.10.10.4 with load balancer port 23 and instance port 25 is configured on the VM, InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.4 with load balancer port 45 and instance port 46 is configured on the VM, InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.6, with load balancer port 23 and instance port 25 is configured on the VM, InternalLBVM2."
+msgstr ""
+
+#: ../../managing_networks.rst:6312
+# b20f10f2b7d3416f912f26288b95da11
+msgid "|vpc-lb.png: Configuring internal LB for VPC|"
+msgstr ""
+
+#: ../../managing_networks.rst:6319
+# 6e79c970118d4190bf7d22c1773505ce
+msgid "Internal LB and Public LB are mutually exclusive on a tier. If the tier has LB on the public side, then it can't have the Internal LB."
+msgstr ""
+
+#: ../../managing_networks.rst:6324
+# 9cf6652ac2e0445387349beb374bfca7
+msgid "Internal LB is supported just on VPC networks in CloudStack 4.2 release."
+msgstr ""
+
+#: ../../managing_networks.rst:6329
+# a3f5f1fc49464829adf0ebd8e7687692
+msgid "Only Internal LB VM can act as the Internal LB provider in CloudStack 4.2 release."
+msgstr ""
+
+#: ../../managing_networks.rst:6334
+# c91dbb4b255c4a84be104b33811e5332
+msgid "Network upgrade is not supported from the network offering with Internal LB to the network offering with Public LB."
+msgstr ""
+
+#: ../../managing_networks.rst:6339
+# b60834349ed648d8a4366ebd00a7fd65
+msgid "Multiple tiers can have internal LB support in a VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:6343
+# 4fab50597d0941108a4d3bf7f13e9411
+msgid "Only one tier can have Public LB support in a VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:6346
+# d225db5293e846a0afd0f6c7bb5f68a1
+msgid "Enabling Internal LB on a VPC Tier"
+msgstr ""
+
+#: ../../managing_networks.rst:6350
+# 617e9425a2fa474b9764128b07034002
+msgid "Create a network offering, as given in `Section 15.27.11.2.5, “Creating an Internal LB Rule” <#int-lb-vpc>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:6355
+# a890050072ca4d26805f98387f27bd75
+msgid "Create an internal load balancing rule and apply, as given in `Section 15.27.11.2.5, “Creating an Internal LB Rule” <#int-lb-vpc>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:6360
+# a4cfada862734f0f851fce215590886e
+msgid "Creating a Network Offering for Internal LB"
+msgstr ""
+
+#: ../../managing_networks.rst:6362
+# 60f76aac53194ec8bbe6de7b8c5a5554
+msgid "To have internal LB support on VPC, either use the default offering, DefaultIsolatedNetworkOfferingForVpcNetworksWithInternalLB, or create a network offering as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:6427
+# 8a5ea6ec925d452a879ceac5445ab579
+msgid "**Supported Services**: Select Load Balancer. Select ``InternalLbVM`` from the provider list."
+msgstr ""
+
+#: ../../managing_networks.rst:6432
+# c72558354623450a936ce31431ffa69e
+msgid "**Load Balancer Type**: Select Internal LB from the drop-down."
+msgstr ""
+
+#: ../../managing_networks.rst:6450
+# 28147ce50bf14231a07cac69826f2a25
+msgid "Creating an Internal LB Rule"
+msgstr ""
+
+#: ../../managing_networks.rst:6452
+# 2c9c4cae286845808fef134063a6f939
+msgid "When you create the Internal LB rule and applies to a VM, an Internal LB VM, which is responsible for load balancing, is created."
+msgstr ""
+
+#: ../../managing_networks.rst:6455
+# 63b7d6ada9114e90ba29443004bc739f
+msgid "You can view the created Internal LB VM in the Instances page if you navigate to **Infrastructure** > **Zones** > <zone\\_ name> > <physical\\_network\\_name> > **Network Service Providers** > **Internal LB VM**. You can manage the Internal LB VMs as and when required from the location."
+msgstr ""
+
+#: ../../managing_networks.rst:6478
+# d533cda5982f42a2be99e3d3a1d02796
+msgid "Locate the VPC for which you want to configure internal LB, then click Configure."
+msgstr ""
+
+#: ../../managing_networks.rst:6486
+# e737073d23cf4d26aed7c10ce7b46e81
+msgid "Locate the Tier for which you want to configure an internal LB rule, click Internal LB."
+msgstr ""
+
+#: ../../managing_networks.rst:6489
+# 552b8f17dcde42d482e1831b58d076ef
+msgid "In the Internal LB page, click Add Internal LB."
+msgstr ""
+
+#: ../../managing_networks.rst:6493
+# 9e377cd375c349e58911fc49edfdd4b1
+msgid "In the dialog, specify the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:6501
+# 87c629929ba84d5da539e7534a89a8d8
+msgid "**Description**: A short description of the rule that can be displayed to users."
+msgstr ""
+
+#: ../../managing_networks.rst:6506
+# 1827d569d2af4a3eb0a577bec4c3e5eb
+msgid "**Source IP Address**: (Optional) The source IP from which traffic originates. The IP is acquired from the CIDR of that particular tier on which you want to create the Internal LB rule. If not specified, the IP address is automatically allocated from the network CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:6512
+# 4258284b90204dc997577baaaf8755b6
+msgid "For every Source IP, a new Internal LB VM is created for load balancing."
+msgstr ""
+
+#: ../../managing_networks.rst:6517
+# e1da6c68ece14aacb7290072c2e1017e
+msgid "**Source Port**: The port associated with the source IP. Traffic on this port is load balanced."
+msgstr ""
+
+#: ../../managing_networks.rst:6522
+# afdf2a4f86134a9c8f2ee0d103fb268e
+msgid "**Instance Port**: The port of the internal LB VM."
+msgstr ""
+
+#: ../../managing_networks.rst:6543
+# 1bdef81fe9294cffb07d59cdeaf608a9
+msgid "Adding a Port Forwarding Rule on a VPC"
+msgstr ""
+
+#: ../../managing_networks.rst:6633
+# 55d5f9cc7a9440d4be42f12599487ff9
+msgid "**Public Port**: The port to which public traffic will be addressed on the IP address you acquired in the previous step."
+msgstr ""
+
+#: ../../managing_networks.rst:6638
+# f3534c50573843559923c45aa9402af1
+msgid "**Private Port**: The port on which the instance is listening for forwarded public traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:6643
+# d970ed9b90c54a74871fab0e0bb4667b
+msgid "**Protocol**: The communication protocol in use between the two ports."
+msgstr ""
+
+#: ../../managing_networks.rst:6648
+# f0be0d19f4464861827239d149e03744
+msgid "TCP"
+msgstr ""
+
+#: ../../managing_networks.rst:6652
+# 931118f56d6d4e2eb86fa29ac132f2b8
+msgid "UDP"
+msgstr ""
+
+#: ../../managing_networks.rst:6656
+# 6d26f66d36a743d4a1a5505df83da34c
+msgid "**Add VM**: Click Add VM. Select the name of the instance to which this rule applies, and click Apply."
+msgstr ""
+
+#: ../../managing_networks.rst:6659
+# 7eb1b2ffd2df41879c5e85c5c75e60f0
+msgid "You can test the rule by opening an SSH session to the instance."
+msgstr ""
+
+#: ../../managing_networks.rst:6662
+# 2517c53c112c475089bf9a0e6ece949d
+msgid "Removing Tiers"
+msgstr ""
+
+#: ../../managing_networks.rst:6664
+# 987463aa0c9e46e58456fd870cbac52b
+msgid "You can remove a tier from a VPC. A removed tier cannot be revoked. When a tier is removed, only the resources of the tier are expunged. All the network rules (port forwarding, load balancing and staticNAT) and the IP addresses associated to the tier are removed. The IP address still be belonging to the same VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:6690
+# b80a7f96c5e343be988091f48cdc8b13
+msgid "The Configure VPC page is displayed. Locate the tier you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:6695
+# 9d1e0efdd66c408c8b6445ab9ed8f0fa
+msgid "Select the tier you want to remove."
+msgstr ""
+
+#: ../../managing_networks.rst:6699
+# 26cd655882384fdc86510166d3a09cc7
+msgid "In the Network Details tab, click the Delete Network button. |del-tier.png: button to remove a tier|"
+msgstr ""
+
+#: ../../managing_networks.rst:6702
+# dc7484d918fd4185a123c12baf9d26af
+msgid "Click Yes to confirm. Wait for some time for the tier to be removed."
+msgstr ""
+
+#: ../../managing_networks.rst:6705
+# b2b2fa6f474c4923b101aff8c6ebd2ae
+msgid "Editing, Restarting, and Removing a Virtual Private Cloud"
+msgstr ""
+
+#: ../../managing_networks.rst:6707
+# df6ef06698254b2398ed91a15c14dd60
+msgid "Ensure that all the tiers are removed before you remove a VPC."
+msgstr ""
+
+#: ../../managing_networks.rst:6726
+# 27e727fcb09c499cb04cfeb2bd8af5d2
+msgid "Select the VPC you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:6730
+# 896f44f41d94483ba83091028938b4b9
+msgid "In the Details tab, click the Remove VPC button |remove-vpc.png: button to remove a VPC|"
+msgstr ""
+
+#: ../../managing_networks.rst:6733
+# c4dc55536b3041f181e37a5bb1952109
+msgid "You can remove the VPC by also using the remove button in the Quick View."
+msgstr ""
+
+#: ../../managing_networks.rst:6736
+# f6bc412f03bc4dc6a55f90047bdec537
+msgid "You can edit the name and description of a VPC. To do that, select the VPC, then click the Edit button. |edit-icon.png: button to edit a VPC|"
+msgstr ""
+
+#: ../../managing_networks.rst:6740
+# 63357afed0464e21be6f8fa41abd0ec8
+msgid "To restart a VPC, select the VPC, then click the Restart button. |restart-vpc.png: button to restart a VPC|"
+msgstr ""
+
+#: ../../managing_networks.rst:6744
+# 39039829f65e4377a122bf91feb35ada
+msgid "Persistent Networks"
+msgstr ""
+
+#: ../../managing_networks.rst:6746
+# fca381dc00a94a72af9e6fd527b20d45
+msgid "The network that you can provision without having to deploy any VMs on it is called a persistent network. A persistent network can be part of a VPC or a non-VPC environment."
+msgstr ""
+
+#: ../../managing_networks.rst:6750
+# 42c10e563fed417980600322954b333d
+msgid "When you create other types of network, a network is only a database entry until the first VM is created on that network. When the first VM is created, a VLAN ID is assigned and the network is provisioned. Also, when the last VM is destroyed, the VLAN ID is released and the network is no longer available. With the addition of persistent network, you will have the ability to create a network in CloudStack in which physical devices can be deployed without having to run any VMs. Additionally, you can deploy physical devices on that network."
+msgstr ""
+
+#: ../../managing_networks.rst:6759
+# 66f7d3c48a604609a402136b8672bae5
+msgid "One of the advantages of having a persistent network is that you can create a VPC with a tier consisting of only physical devices. For example, you might create a VPC for a three-tier application, deploy VMs for Web and Application tier, and use physical machines for the Database tier. Another use case is that if you are providing services by using physical hardware, you can define the network as persistent and therefore even if all its VMs are destroyed the services will not be discontinued."
+msgstr ""
+
+#: ../../managing_networks.rst:6769
+# c24813594b9c47c386a450613b070d37
+msgid "Persistent Network Considerations"
+msgstr ""
+
+#: ../../managing_networks.rst:6773
+# 9a171e4d62114e3c88fc9881e6a4e32d
+msgid "Persistent network is designed for isolated networks."
+msgstr ""
+
+#: ../../managing_networks.rst:6777
+# f090f131150f456ab0942566d94a17df
+msgid "All default network offerings are non-persistent."
+msgstr ""
+
+#: ../../managing_networks.rst:6781
+# c8335c59614a4bd0ae9163104533304a
+msgid "A network offering cannot be editable because changing it affects the behavior of the existing networks that were created using this network offering."
+msgstr ""
+
+#: ../../managing_networks.rst:6787
+# 23af8e44c8e84feeb39a085848e5709b
+msgid "When you create a guest network, the network offering that you select defines the network persistence. This in turn depends on whether persistent network is enabled in the selected network offering."
+msgstr ""
+
+#: ../../managing_networks.rst:6793
+# ab1ccf831ef74353bde8bfb88e0155ad
+msgid "An existing network can be made persistent by changing its network offering to an offering that has the Persistent option enabled. While setting this property, even if the network has no running VMs, the network is provisioned."
+msgstr ""
+
+#: ../../managing_networks.rst:6800
+# e7bb232da8854652a63fa39c268cc893
+msgid "An existing network can be made non-persistent by changing its network offering to an offering that has the Persistent option disabled. If the network has no running VMs, during the next network garbage collection run the network is shut down."
+msgstr ""
+
+#: ../../managing_networks.rst:6807
+# 02f9973b78fc4f4ea2dbc33c7740fb9f
+msgid "When the last VM on a network is destroyed, the network garbage collector checks if the network offering associated with the network is persistent, and shuts down the network only if it is non-persistent."
+msgstr ""
+
+#: ../../managing_networks.rst:6813
+# fb3cf96c3ec041969d55371e0aaa1d81
+msgid "Creating a Persistent Guest Network"
+msgstr ""
+
+#: ../../managing_networks.rst:6815
+# 19e73163820243d4a6f7fffe91f8ccb3
+msgid "To create a persistent network, perform the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:6819
+# da4bbbbdbd5a46bc9d3cdb51651cf4c1
+msgid "Create a network offering with the Persistent option enabled."
+msgstr ""
+
+#: ../../managing_networks.rst:6821
+# 7036ba30ea924150937e15be22167fde
+msgid "See the Administration Guide."
+msgstr ""
+
+#: ../../managing_networks.rst:6825
+# b531eda7832a4473af382ed8bb02ff2d
+msgid "Select Network from the left navigation pane."
+msgstr ""
+
+#: ../../managing_networks.rst:6829
+# acc08af60a1540af83325f8d84777285
+msgid "Select the guest network that you want to offer this network service to."
+msgstr ""
+
+#: ../../managing_networks.rst:6834
+# f91ae55836074e878e10c2eb152ec6d4
+msgid "Click the Edit button."
+msgstr ""
+
+#: ../../managing_networks.rst:6838
+# 41ffae74d3724190b34bc30fda773ff0
+msgid "From the Network Offering drop-down, select the persistent network offering you have just created."
+msgstr ""
+
diff --git a/source/installguide/locale/pot/network_setup.pot b/source/installguide/locale/pot/network_setup.pot
new file mode 100644
index 0000000..de25f63
--- /dev/null
+++ b/source/installguide/locale/pot/network_setup.pot
@@ -0,0 +1,1703 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../network_setup.rst:18
+# 204e7166d7584bc8800c10730331b91a
+msgid "Network Setup"
+msgstr ""
+
+#: ../../network_setup.rst:20
+# 28fd3f07600a446f8025a77d2f76f083
+msgid "Achieving the correct networking setup is crucial to a successful CloudStack installation. This section contains information to help you make decisions and follow the right procedures to get your network set up correctly."
+msgstr ""
+
+#: ../../network_setup.rst:27
+# 0f171b003d40415f9683899a68f68949
+msgid "Basic and Advanced Networking"
+msgstr ""
+
+#: ../../network_setup.rst:29
+# 188908473c3948279ecec71280711a3b
+msgid "CloudStack provides two styles of networking:."
+msgstr ""
+
+#: ../../network_setup.rst:31
+# d972c75e48ba46ce8b2fd29ba7a548fc
+msgid "**Basic** For AWS-style networking. Provides a single network where guest isolation can be provided through layer-3 means such as security groups (IP address source filtering)."
+msgstr ""
+
+#: ../../network_setup.rst:36
+# 286b58108d5240ab81545392b60577c5
+msgid "**Advanced** For more sophisticated network topologies. This network model provides the most flexibility in defining guest networks, but requires more configuration steps than basic networking."
+msgstr ""
+
+#: ../../network_setup.rst:41
+# ef43036726e14dd092edbbe912848db5
+msgid "Each zone has either basic or advanced networking. Once the choice of networking model for a zone has been made and configured in CloudStack, it can not be changed. A zone is either basic or advanced for its entire lifetime."
+msgstr ""
+
+#: ../../network_setup.rst:46
+# edec4755035e4f65bc0313e508fef22c
+msgid "The following table compares the networking features in the two networking models."
+msgstr ""
+
+#: ../../network_setup.rst:49
+# 1931f079dbf54009a09b730d78cea8ae
+msgid "Networking Feature"
+msgstr ""
+
+#: ../../network_setup.rst:49
+# ddb5e29a533944e79cfacd651a55de04
+msgid "Basic Network"
+msgstr ""
+
+#: ../../network_setup.rst:49
+# 5e5d2126f2b342099f984864fe91699a
+msgid "Advanced Network"
+msgstr ""
+
+#: ../../network_setup.rst:51
+# 2e392d44156a42619a81a1004ebe92a6
+msgid "Number of networks"
+msgstr ""
+
+#: ../../network_setup.rst:51
+# 2c57c568f79e4abf9d0b9731eb3ea05b
+msgid "Single network"
+msgstr ""
+
+#: ../../network_setup.rst:51
+# a0c94e5edb364dc590ac47ed8a4a9104
+msgid "Multiple networks"
+msgstr ""
+
+#: ../../network_setup.rst:52
+# 15454f7e603b41a4bc4e11f248e4988f
+msgid "Firewall type"
+msgstr ""
+
+#: ../../network_setup.rst:52
+#: ../../network_setup.rst:53
+#: ../../network_setup.rst:56
+#: ../../network_setup.rst:57
+# 0f306c3ed8cc40a7b2a90c79c2bc1b21
+# 08a635b95c484902a4c8d6739599e242
+# a9d431ac26934dc0b50f9d2fb90e1057
+# 48d78bd1b5fc4a06b4f3d035a5c93188
+msgid "Physical"
+msgstr ""
+
+#: ../../network_setup.rst:52
+#: ../../network_setup.rst:53
+#: ../../network_setup.rst:56
+#: ../../network_setup.rst:57
+#: ../../network_setup.rst:58
+# 54c51460b59b4787a77fe987aff804e0
+# bf584ce2c901485f917ebdf80d512db2
+# fda7d50fe9df495aa57dc3a69b89ce53
+# 4bcf67ddb65b49cc92e25d48cbeeb7aa
+# 0739b5b91ac0446d977a4641dfcc846e
+msgid "Physical and Virtual"
+msgstr ""
+
+#: ../../network_setup.rst:53
+# 483cde5d650e412799b4b3d95c1a34ff
+msgid "Load balancer"
+msgstr ""
+
+#: ../../network_setup.rst:54
+# 824040016a8e47958d1e7900b0c5bc8f
+msgid "Isolation type"
+msgstr ""
+
+#: ../../network_setup.rst:54
+# eb2562a54a6f41439d2c95bcbe8e93f7
+msgid "Layer 3"
+msgstr ""
+
+#: ../../network_setup.rst:54
+# 8c4ff876b9af4e23a60a18477d9ad2ac
+msgid "Layer 2 and Layer 3"
+msgstr ""
+
+#: ../../network_setup.rst:55
+# 272f31b097a6419b9657d410bc613b29
+msgid "VPN support"
+msgstr ""
+
+#: ../../network_setup.rst:55
+#: ../../network_setup.rst:58
+#: ../../network_setup.rst:855
+# be705df006104fc981cd11ab21dbee41
+# 77c761df6e424c5eaa8fd876956f2fd4
+# 89111394bc904a6688140d3a45239729
+msgid "No"
+msgstr ""
+
+#: ../../network_setup.rst:55
+#: ../../network_setup.rst:59
+#: ../../network_setup.rst:59
+#: ../../network_setup.rst:61
+#: ../../network_setup.rst:61
+#: ../../network_setup.rst:853
+#: ../../network_setup.rst:854
+# 87c00040e2b94a5fb1354724a796ad4e
+# c1bcbed263544b8ba2804541e77b986c
+# 2f87b4b5d55248b68a742abdfcac7411
+# f0fa47c28e75441f8ef8397b8c693fb5
+# 6987985d2d78451b9146580fa5ec7197
+# c235fbc31a63448c9b960c7ccc3745d4
+# f454f4d643734a6283ed71f976c4e65e
+msgid "Yes"
+msgstr ""
+
+#: ../../network_setup.rst:56
+# cde208e3641549ac9fe8b53a042abd65
+msgid "Port forwarding"
+msgstr ""
+
+#: ../../network_setup.rst:57
+# 33d5935021cd4f3ab6e723b0921e6945
+msgid "1:1 NAT"
+msgstr ""
+
+#: ../../network_setup.rst:58
+# 435097d06513454a921a6170741111bb
+msgid "Source NAT"
+msgstr ""
+
+#: ../../network_setup.rst:59
+# 4546413386114726ad887ab1acfc1cba
+msgid "Userdata"
+msgstr ""
+
+#: ../../network_setup.rst:60
+# e6a6cb39df554d4d8490722bb831ef65
+msgid "Network usage monitoring"
+msgstr ""
+
+#: ../../network_setup.rst:60
+# cb68ceaa47fb447d915faa6dc794d39f
+msgid "sFlow / netFlow at physical router"
+msgstr ""
+
+#: ../../network_setup.rst:60
+# 966d9d494a53445b9daf7f7190e39159
+msgid "Hypervisor and Virtual Router"
+msgstr ""
+
+#: ../../network_setup.rst:61
+# 118c5bc124044577ba2fbfe145951209
+msgid "DNS and DHCP"
+msgstr ""
+
+#: ../../network_setup.rst:64
+# 08f4517f5738454f8ee78adefac8efb1
+msgid "The two types of networking may be in use in the same cloud. However, a given zone must use either Basic Networking or Advanced Networking."
+msgstr ""
+
+#: ../../network_setup.rst:67
+# 8caea62e111d4d1b8833f7670c72d8df
+msgid "Different types of network traffic can be segmented on the same physical network. Guest traffic can also be segmented by account. To isolate traffic, you can use separate VLANs. If you are using separate VLANs on a single physical network, make sure the VLAN tags are in separate numerical ranges."
+msgstr ""
+
+#: ../../network_setup.rst:75
+# f4f61d2e2b224b75a03e28cda9e376a8
+msgid "VLAN Allocation Example"
+msgstr ""
+
+#: ../../network_setup.rst:77
+# dad8ccdf2ed74b0e9f0173a0aa08c615
+msgid "VLANs are required for public and guest traffic. The following is an example of a VLAN allocation scheme:"
+msgstr ""
+
+#: ../../network_setup.rst:81
+# d9ac134036354b0ab2421582a57e79c6
+msgid "VLAN IDs"
+msgstr ""
+
+#: ../../network_setup.rst:81
+# e22dc22a2b9449bbb3e9b5fcceafc29b
+msgid "Traffic type"
+msgstr ""
+
+#: ../../network_setup.rst:81
+# 2abc2124719642c6bf6ab370646803bc
+msgid "Scope"
+msgstr ""
+
+#: ../../network_setup.rst:83
+# f3318541895b4a509bfdcfe8f540fcd2
+msgid "less than 500"
+msgstr ""
+
+#: ../../network_setup.rst:83
+# 7f123557b3644b699605f66ed71aaa88
+msgid "Management traffic. Reserved for administrative purposes."
+msgstr ""
+
+#: ../../network_setup.rst:83
+# 8d3f29be0c2341d181217f083f364b66
+msgid "CloudStack software can access this, hypervisors, system VMs."
+msgstr ""
+
+#: ../../network_setup.rst:84
+# ebbb276566564730b2573b1fd1b161a9
+msgid "500-599"
+msgstr ""
+
+#: ../../network_setup.rst:84
+# 125bfc83d5554aaab7fdd32838cce9c9
+msgid "VLAN carrying public traffic."
+msgstr ""
+
+#: ../../network_setup.rst:84
+# d37af8f70e29457a9557e53215e2e96c
+msgid "CloudStack accounts."
+msgstr ""
+
+#: ../../network_setup.rst:85
+# 73133e4e2c86492c8f9817f4981789f8
+msgid "600-799"
+msgstr ""
+
+#: ../../network_setup.rst:85
+#: ../../network_setup.rst:86
+# 20844dcf31fd46558c2f60d7ce91478d
+# 7a38326cb87b46d890e1e444ee7ce9e6
+msgid "VLANs carrying guest traffic."
+msgstr ""
+
+#: ../../network_setup.rst:85
+# b9283c2609ad426ea049d4b4de64a229
+msgid "CloudStack accounts. Account-specific VLAN is chosen from this pool."
+msgstr ""
+
+#: ../../network_setup.rst:86
+# 2434c3ee95244a3e87c4be5df884d38e
+msgid "800-899"
+msgstr ""
+
+#: ../../network_setup.rst:86
+# 55d07caba3264be299f2f188911b20f8
+msgid "CloudStack accounts. Account-specific VLAN chosen by CloudStack admin to assign to that account."
+msgstr ""
+
+#: ../../network_setup.rst:87
+# 916471020e7c48f8a5b214bd1e8b3764
+msgid "900-999"
+msgstr ""
+
+#: ../../network_setup.rst:87
+# 6eb9b2a9c7d541d49840d4b7da813678
+msgid "VLAN carrying guest traffic"
+msgstr ""
+
+#: ../../network_setup.rst:87
+# cbe91fb5fb35471aaf913bf77c8545b3
+msgid "CloudStack accounts. Can be scoped by project, domain, or all accounts."
+msgstr ""
+
+#: ../../network_setup.rst:88
+# 7cd25e560d8e482489ee707255e6a113
+msgid "greater than 1000"
+msgstr ""
+
+#: ../../network_setup.rst:88
+# a732a81098944d88b516c81d48fe1dd6
+msgid "Reserved for future use"
+msgstr ""
+
+#: ../../network_setup.rst:93
+# 9e6124ed88b34569b749356c28e994c5
+msgid "Example Hardware Configuration"
+msgstr ""
+
+#: ../../network_setup.rst:95
+# 2e0e4d4766c94461bf47dbf4b297511c
+msgid "This section contains an example configuration of specific switch models for zone-level layer-3 switching. It assumes VLAN management protocols, such as VTP or GVRP, have been disabled. The example scripts must be changed appropriately if you choose to use VTP or GVRP."
+msgstr ""
+
+#: ../../network_setup.rst:102
+#: ../../network_setup.rst:190
+# e49d362a79214babab229f63b561504f
+# ec1918afa90c431ebc41c83d6622bf67
+msgid "Dell 62xx"
+msgstr ""
+
+#: ../../network_setup.rst:104
+# 7cac328e3f4d41d2912b3d1374983217
+msgid "The following steps show how a Dell 62xx is configured for zone-level layer-3 switching. These steps assume VLAN 201 is used to route untagged private IPs for pod 1, and pod 1’s layer-2 switch is connected to Ethernet port 1/g1."
+msgstr ""
+
+#: ../../network_setup.rst:109
+# f85fd6334b4d42368bd77fd43eab6554
+msgid "The Dell 62xx Series switch supports up to 1024 VLANs."
+msgstr ""
+
+#: ../../network_setup.rst:111
+#: ../../network_setup.rst:195
+# 3a9eadcf6462491b83915415a657e356
+# 4d6fd3d41ba3470c8ffe4bec5ad1626a
+msgid "Configure all the VLANs in the database."
+msgstr ""
+
+#: ../../network_setup.rst:119
+# 3b8ffcd8739f4ebeb2ed2be4eef1ad64
+msgid "Configure Ethernet port 1/g1."
+msgstr ""
+
+#: ../../network_setup.rst:130
+# 3f429d4bc0024cd8bd9e41e305d508d9
+msgid "The statements configure Ethernet port 1/g1 as follows:"
+msgstr ""
+
+#: ../../network_setup.rst:132
+# d34108f02c0b45b093b68a1f5b8766a3
+msgid "VLAN 201 is the native untagged VLAN for port 1/g1."
+msgstr ""
+
+#: ../../network_setup.rst:134
+# cb2aa517977a4582afcedbfaf7b457cc
+msgid "All VLANs (300-999) are passed to all the pod-level layer-2 switches."
+msgstr ""
+
+#: ../../network_setup.rst:138
+#: ../../network_setup.rst:222
+# 5889063b34fa4e5a946573bb352b45c7
+# c48e437e84a44e1281b7228a01cc0c4f
+msgid "Cisco 3750"
+msgstr ""
+
+#: ../../network_setup.rst:140
+# b029ac75d9be4c4d8f41fa45f587b2a7
+msgid "The following steps show how a Cisco 3750 is configured for zone-level layer-3 switching. These steps assume VLAN 201 is used to route untagged private IPs for pod 1, and pod 1’s layer-2 switch is connected to GigabitEthernet1/0/1."
+msgstr ""
+
+#: ../../network_setup.rst:145
+#: ../../network_setup.rst:227
+# 21087caee9cc42529713be381a17944e
+# 77f3004ef9e84e23985c7a992fe12b51
+msgid "Setting VTP mode to transparent allows us to utilize VLAN IDs above 1000. Since we only use VLANs up to 999, vtp transparent mode is not strictly required."
+msgstr ""
+
+#: ../../network_setup.rst:155
+# bc414aaf1d5d49789ab07767a1efc42e
+msgid "Configure GigabitEthernet1/0/1."
+msgstr ""
+
+#: ../../network_setup.rst:165
+# 13695f0fdc2c4258a81d99fb9126b65c
+msgid "The statements configure GigabitEthernet1/0/1 as follows:"
+msgstr ""
+
+#: ../../network_setup.rst:167
+# db9281cf2d474ccb8b73772d174b5061
+msgid "VLAN 201 is the native untagged VLAN for port GigabitEthernet1/0/1."
+msgstr ""
+
+#: ../../network_setup.rst:169
+# 2de38e6352e648758eb5e9d33f7f50b9
+msgid "Cisco passes all VLANs by default. As a result, all VLANs (300-999) are passed to all the pod-level layer-2 switches."
+msgstr ""
+
+#: ../../network_setup.rst:174
+# ecca16ca947244c69af3cda7d8ef906a
+msgid "Layer-2 Switch"
+msgstr ""
+
+#: ../../network_setup.rst:176
+# bd6f1f286da647f0861e42f5c4d5cbd6
+msgid "The layer-2 switch is the access switching layer inside the pod."
+msgstr ""
+
+#: ../../network_setup.rst:178
+# f5aedd9919f44d4d9eea58da5118c865
+msgid "It should trunk all VLANs into every computing host."
+msgstr ""
+
+#: ../../network_setup.rst:180
+# 47960e02b071465188e24cb273c65328
+msgid "It should switch traffic for the management network containing computing and storage hosts. The layer-3 switch will serve as the gateway for the management network."
+msgstr ""
+
+#: ../../network_setup.rst:184
+# b6bfd5be3b83467192f7d4dba3613304
+msgid "The following sections contain example configurations for specific switch models for pod-level layer-2 switching. It assumes VLAN management protocols such as VTP or GVRP have been disabled. The scripts must be changed appropriately if you choose to use VTP or GVRP."
+msgstr ""
+
+#: ../../network_setup.rst:192
+# a9c5170aa3324e03adee54023346ad80
+msgid "The following steps show how a Dell 62xx is configured for pod-level layer-2 switching."
+msgstr ""
+
+#: ../../network_setup.rst:203
+# 476b0c81a6c44098804cc2f6b9c8dfd5
+msgid "VLAN 201 is used to route untagged private IP addresses for pod 1, and pod 1 is connected to this layer-2 switch."
+msgstr ""
+
+#: ../../network_setup.rst:213
+# 22aebc930b7b471394516ed87778ba3c
+msgid "The statements configure all Ethernet ports to function as follows:"
+msgstr ""
+
+#: ../../network_setup.rst:215
+# 01bdebb29d964df18edcf52ee732caa0
+msgid "All ports are configured the same way."
+msgstr ""
+
+#: ../../network_setup.rst:217
+# 42d47d6cc7f148de826545de21dee4c0
+msgid "All VLANs (300-999) are passed through all the ports of the layer-2 switch."
+msgstr ""
+
+#: ../../network_setup.rst:224
+# 5057c158f06e4e439eebde80d1e49d38
+msgid "The following steps show how a Cisco 3750 is configured for pod-level layer-2 switching."
+msgstr ""
+
+#: ../../network_setup.rst:237
+# 97f41001dc4f44e5bf4def9e08be580c
+msgid "Configure all ports to dot1q and set 201 as the native VLAN."
+msgstr ""
+
+#: ../../network_setup.rst:247
+# 5ea9eb52eaea40329b40b32897d7c2f1
+msgid "By default, Cisco passes all VLANs. Cisco switches complain of the native VLAN IDs are different when 2 ports are connected together. That’s why you must specify VLAN 201 as the native VLAN on the layer-2 switch."
+msgstr ""
+
+#: ../../network_setup.rst:254
+# 8b410ff7a036484a89d183ed79f66761
+msgid "Hardware Firewall"
+msgstr ""
+
+#: ../../network_setup.rst:256
+# 149a7357d1b2421c8e62f11be11e4a89
+msgid "All deployments should have a firewall protecting the management server; see Generic Firewall Provisions. Optionally, some deployments may also have a Juniper SRX firewall that will be the default gateway for the guest networks; see `“External Guest Firewall Integration for Juniper SRX (Optional)” <#external-guest-firewall-integration-for-juniper-srx-optional>`_."
+msgstr ""
+
+#: ../../network_setup.rst:263
+# e2f547c68a5549bebcc7c440d52727e8
+msgid "Generic Firewall Provisions"
+msgstr ""
+
+#: ../../network_setup.rst:265
+# 8f3c0247e1254e6c8731076a59b80543
+msgid "The hardware firewall is required to serve two purposes:"
+msgstr ""
+
+#: ../../network_setup.rst:267
+# 4e3d6f474c664d1ea8727ca773c6c317
+msgid "Protect the Management Servers. NAT and port forwarding should be configured to direct traffic from the public Internet to the Management Servers."
+msgstr ""
+
+#: ../../network_setup.rst:271
+# deafcee33c084aea9b10dc89e3c056db
+msgid "Route management network traffic between multiple zones. Site-to-site VPN should be configured between multiple zones."
+msgstr ""
+
+#: ../../network_setup.rst:274
+# 3bf3e1c1628b4e3cbd78d690b7f6da5d
+msgid "To achieve the above purposes you must set up fixed configurations for the firewall. Firewall rules and policies need not change as users are provisioned into the cloud. Any brand of hardware firewall that supports NAT and site-to-site VPN can be used."
+msgstr ""
+
+#: ../../network_setup.rst:281
+# 6bd99eddfc3a460a8e104b8fb62cb5c1
+msgid "External Guest Firewall Integration for Juniper SRX (Optional)"
+msgstr ""
+
+#: ../../network_setup.rst:284
+# 91fc9325ee69495fa969c72724802e81
+msgid "Available only for guests using advanced networking."
+msgstr ""
+
+#: ../../network_setup.rst:286
+# 0dd27c6946794a9cafa7a524eccfffa9
+msgid "CloudStack provides for direct management of the Juniper SRX series of firewalls. This enables CloudStack to establish static NAT mappings from public IPs to guest VMs, and to use the Juniper device in place of the virtual router for firewall services. You can have one or more Juniper SRX per zone. This feature is optional. If Juniper integration is not provisioned, CloudStack will use the virtual router for these services."
+msgstr ""
+
+#: ../../network_setup.rst:293
+# 59a83ba854224a05b873335238575ed2
+msgid "The Juniper SRX can optionally be used in conjunction with an external load balancer. External Network elements can be deployed in a side-by-side or inline configuration."
+msgstr ""
+
+#: ../../network_setup.rst:297
+# 9583a2f6c4bd4bf4a0ef016582e4950e
+msgid "|parallel-mode.png: adding a firewall and load balancer in parallel mode.|"
+msgstr ""
+
+#: ../../network_setup.rst:300
+# 33e495e75ccc4175ac42b392be1f9a25
+msgid "CloudStack requires the Juniper SRX firewall to be configured as follows:"
+msgstr ""
+
+#: ../../network_setup.rst:303
+# 1d1d4d7ab6de4a8985bde992b3d4b3e8
+msgid "Supported SRX software version is 10.3 or higher."
+msgstr ""
+
+#: ../../network_setup.rst:305
+# 6dcbb647db2644fa9a7c43eeb20f382f
+msgid "Install your SRX appliance according to the vendor's instructions."
+msgstr ""
+
+#: ../../network_setup.rst:307
+# 50c53fc1bbaa48ee9e70e7868e5ac785
+msgid "Connect one interface to the management network and one interface to the public network. Alternatively, you can connect the same interface to both networks and a use a VLAN for the public network."
+msgstr ""
+
+#: ../../network_setup.rst:311
+# 0acd20956a3b4ed79e57dd49dd90aa83
+msgid "Make sure \"vlan-tagging\" is enabled on the private interface."
+msgstr ""
+
+#: ../../network_setup.rst:313
+# 043b2c85f7df4eaa8f35f85717d6411e
+msgid "Record the public and private interface names. If you used a VLAN for the public interface, add a \".[VLAN TAG]\" after the interface name. For example, if you are using ge-0/0/3 for your public interface and VLAN tag 301, your public interface name would be \"ge-0/0/3.301\". Your private interface name should always be untagged because the CloudStack software automatically creates tagged logical interfaces."
+msgstr ""
+
+#: ../../network_setup.rst:320
+# d2e6321e2786420589602b57da869135
+msgid "Create a public security zone and a private security zone. By default, these will already exist and will be called \"untrust\" and \"trust\". Add the public interface to the public zone and the private interface to the private zone. Note down the security zone names."
+msgstr ""
+
+#: ../../network_setup.rst:325
+# 9d5330a8656f412aa6986f2bd6a1d05d
+msgid "Make sure there is a security policy from the private zone to the public zone that allows all traffic."
+msgstr ""
+
+#: ../../network_setup.rst:328
+# ed6f7d110d0143b6b94e01737a88c911
+msgid "Note the username and password of the account you want the CloudStack software to log in to when it is programming rules."
+msgstr ""
+
+#: ../../network_setup.rst:331
+# 15d496095b294760b7582dd939c7e2a8
+msgid "Make sure the \"ssh\" and \"xnm-clear-text\" system services are enabled."
+msgstr ""
+
+#: ../../network_setup.rst:333
+# 8e2b9fe66ce24116ae4ebbeea154806a
+msgid "If traffic metering is desired:"
+msgstr ""
+
+#: ../../network_setup.rst:335
+# b63ccbb8b8fd42aba3d987bed558037b
+msgid "Create an incoming firewall filter and an outgoing firewall filter. These filters should be the same names as your public security zone name and private security zone name respectively. The filters should be set to be \"interface-specific\". For example, here is the configuration where the public zone is \"untrust\" and the private zone is \"trust\":"
+msgstr ""
+
+#: ../../network_setup.rst:352
+# b8d90177058440b08f11b6fbd6224400
+msgid "Add the firewall filters to your public interface. For example, a sample configuration output (for public interface ge-0/0/3.0, public security zone untrust, and private security zone trust) is:"
+msgstr ""
+
+#: ../../network_setup.rst:370
+# d0201cdd17164ce8bb8ed40e21ce56ed
+msgid "Make sure all VLANs are brought to the private interface of the SRX."
+msgstr ""
+
+#: ../../network_setup.rst:372
+# 0be4d835f5ec47dfb1cb475ce8185cbd
+msgid "After the CloudStack Management Server is installed, log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../network_setup.rst:375
+#: ../../network_setup.rst:597
+#: ../../network_setup.rst:631
+#: ../../network_setup.rst:790
+# 83eedf55f3c84dd59b6d0031f7e0c5ee
+# 119ea5f9aac34939b712e6bf35fd6b2b
+# 9de5aa399b044a5a86ccc6bd1abe0800
+# e5a613843e514b77a3d7467cdc372e5f
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../network_setup.rst:377
+#: ../../network_setup.rst:599
+#: ../../network_setup.rst:633
+#: ../../network_setup.rst:792
+# c7b8e2f9cbd84c43a23b87769989190b
+# fee6b2759a0a4c8d85973b38457107b9
+# 29aa1bf7a6cc4e779ad52ab4f8d65691
+# 1a6287e3416f438e8e20715084bec873
+msgid "In Zones, click View More."
+msgstr ""
+
+#: ../../network_setup.rst:379
+#: ../../network_setup.rst:601
+#: ../../network_setup.rst:635
+#: ../../network_setup.rst:794
+# 564cfc916b7b4250b8211ac6b03d6830
+# 99ba370aee7e4b14ba26cb13b10849ad
+# 0e2e624457db4fba8b6a9bea3ecc8cd2
+# d36af8233dbf427dbda0f1f6a3b3279d
+msgid "Choose the zone you want to work with."
+msgstr ""
+
+#: ../../network_setup.rst:381
+#: ../../network_setup.rst:796
+# fd783e15448d42eca4b34f6d6c297a80
+# 8b0b666f0e2c4a61b088f7aea345a2c1
+msgid "Click the Network tab."
+msgstr ""
+
+#: ../../network_setup.rst:383
+#: ../../network_setup.rst:798
+# 27d53105db6e439c9ee111db84d2e624
+# cc0180b6815b400c9453c2c6a2b25cef
+msgid "In the Network Service Providers node of the diagram, click Configure. (You might have to scroll down to see this.)"
+msgstr ""
+
+#: ../../network_setup.rst:386
+# c57c2457da7b4b2fab54de32397fb5bb
+msgid "Click SRX."
+msgstr ""
+
+#: ../../network_setup.rst:388
+# c63b5c19989247ce8932e1d0cb37d240
+msgid "Click the Add New SRX button (+) and provide the following:"
+msgstr ""
+
+#: ../../network_setup.rst:390
+#: ../../network_setup.rst:807
+# 8d667d9b05284e6fb6629c3d184f4b12
+# b559300d6e0f48daa0730c40d2cbcf6e
+msgid "IP Address: The IP address of the SRX."
+msgstr ""
+
+#: ../../network_setup.rst:392
+# 5f9a972abd4e41d98ebc2925a9bbffb7
+msgid "Username: The user name of the account on the SRX that CloudStack should use."
+msgstr ""
+
+#: ../../network_setup.rst:395
+#: ../../network_setup.rst:621
+# 9805383a254e4a42b7870c8c3c9fc1fb
+# 9d98c3fcf55b4763826c737462e97833
+msgid "Password: The password of the account."
+msgstr ""
+
+#: ../../network_setup.rst:397
+# 589a2bf5564f4f3dabfc87038ad99528
+msgid "Public Interface. The name of the public interface on the SRX. For example, ge-0/0/2. A \".x\" at the end of the interface indicates the VLAN that is in use."
+msgstr ""
+
+#: ../../network_setup.rst:401
+# a99e76740bd74ea2b9d864e0f2f22d36
+msgid "Private Interface: The name of the private interface on the SRX. For example, ge-0/0/1."
+msgstr ""
+
+#: ../../network_setup.rst:404
+# b141f05518cd45c0bfb4563cae4c1f39
+msgid "Usage Interface: (Optional) Typically, the public interface is used to meter traffic. If you want to use a different interface, specify its name here"
+msgstr ""
+
+#: ../../network_setup.rst:408
+# 06f5547344474c78b06dfceef142803e
+msgid "Number of Retries: The number of times to attempt a command on the SRX before failing. The default value is 2."
+msgstr ""
+
+#: ../../network_setup.rst:411
+# 0e672b9a244d49b981670d6082dcec0e
+msgid "Timeout (seconds): The time to wait for a command on the SRX before considering it failed. Default is 300 seconds."
+msgstr ""
+
+#: ../../network_setup.rst:414
+# fc059aade6b144a4b95d0c8826c39030
+msgid "Public Network: The name of the public network on the SRX. For example, trust."
+msgstr ""
+
+#: ../../network_setup.rst:417
+# a174bebde38f47648a5348b5a7f31b8a
+msgid "Private Network: The name of the private network on the SRX. For example, untrust."
+msgstr ""
+
+#: ../../network_setup.rst:420
+# e8f9887a325f4080a1f065d01ce94eef
+msgid "Capacity: The number of networks the device can handle"
+msgstr ""
+
+#: ../../network_setup.rst:422
+# feca5c1941624366a9ee33104afa1869
+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 ""
+
+#: ../../network_setup.rst:426
+#: ../../network_setup.rst:623
+#: ../../network_setup.rst:661
+#: ../../network_setup.rst:832
+# d87bed8dbd1d4647a4a74b4fde1e2b4e
+# 6e6650d74a0343ef91d48ae3c11dc1e2
+# e3313ae53b0e404c8a5b589979a311b2
+# 6c0d5b7a35c94391936c43610833c8b1
+msgid "Click OK."
+msgstr ""
+
+#: ../../network_setup.rst:428
+# 72e1ae81e175465e801b9a35330c91c7
+msgid "Click Global Settings. Set the parameter external.network.stats.interval to indicate how often you want CloudStack to fetch network usage statistics from the Juniper SRX. If you are not using the SRX to gather network usage statistics, set to 0."
+msgstr ""
+
+#: ../../network_setup.rst:435
+# 5311a929dda944ea92ba1a05fe795f65
+msgid "External Guest Firewall Integration for Cisco VNMC (Optional)"
+msgstr ""
+
+#: ../../network_setup.rst:437
+# 40bbe2d15710459ea8a53a4a3e8be997
+msgid "Cisco Virtual Network Management Center (VNMC) provides centralized multi-device and policy management for Cisco Network Virtual Services. You can integrate Cisco VNMC with CloudStack to leverage the firewall and NAT service offered by ASA 1000v Cloud Firewall. Use it in a Cisco Nexus 1000v dvSwitch-enabled cluster in CloudStack. In such a deployment, you will be able to:"
+msgstr ""
+
+#: ../../network_setup.rst:444
+# 53b820cc9dff42c7b255ab4d8568a19e
+msgid "Configure Cisco ASA 1000v firewalls. You can configure one per guest network."
+msgstr ""
+
+#: ../../network_setup.rst:447
+# 7d55cb00df5b4a49bfb45bc29b87a677
+msgid "Use Cisco ASA 1000v firewalls to create and apply security profiles that contain ACL policy sets for both ingress and egress traffic."
+msgstr ""
+
+#: ../../network_setup.rst:450
+# bbd8e2f953704bfda60d592b7a1c4429
+msgid "Use Cisco ASA 1000v firewalls to create and apply Source NAT, Port Forwarding, and Static NAT policy sets."
+msgstr ""
+
+#: ../../network_setup.rst:453
+# 474d1c74488841138f21f9871e3e7637
+msgid "CloudStack supports Cisco VNMC on Cisco Nexus 1000v dvSwich-enabled VMware hypervisors."
+msgstr ""
+
+#: ../../network_setup.rst:458
+# 42c0de41f2c44491a91b52cf81ed3674
+msgid "Using Cisco ASA 1000v Firewall, Cisco Nexus 1000v dvSwitch, and Cisco VNMC in a Deployment"
+msgstr ""
+
+#: ../../network_setup.rst:461
+# d18809d95a674b9cbe2ffa627eff2786
+msgid "Guidelines"
+msgstr ""
+
+#: ../../network_setup.rst:463
+# f97e1aa6ae6b4d49b5c4c66f95db6400
+msgid "Cisco ASA 1000v firewall is supported only in Isolated Guest Networks."
+msgstr ""
+
+#: ../../network_setup.rst:466
+# 8df62ec4f02c4a4dbb579d02dd3f150a
+msgid "Cisco ASA 1000v firewall is not supported on VPC."
+msgstr ""
+
+#: ../../network_setup.rst:468
+# 7b56777b52384a36ae1bb6733fedafcb
+msgid "Cisco ASA 1000v firewall is not supported for load balancing."
+msgstr ""
+
+#: ../../network_setup.rst:470
+# 237ca442d633476b97185dca9083c955
+msgid "When a guest network is created with Cisco VNMC firewall provider, an additional public IP is acquired along with the Source NAT IP. The Source NAT IP is used for the rules, whereas the additional IP is used to for the ASA outside interface. Ensure that this additional public IP is not released. You can identify this IP as soon as the network is in implemented state and before acquiring any further public IPs. The additional IP is the one that is not marked as Source NAT. You can find the IP used for the ASA outside interface by looking at the Cisco VNMC used in your guest network."
+msgstr ""
+
+#: ../../network_setup.rst:480
+# 71e7c6de8183436aa6c9219b5fe32097
+msgid "Use the public IP address range from a single subnet. You cannot add IP addresses from different subnets."
+msgstr ""
+
+#: ../../network_setup.rst:483
+# 347a68ec09e74810a44472e35d092f64
+msgid "Only one ASA instance per VLAN is allowed because multiple VLANS cannot be trunked to ASA ports. Therefore, you can use only one ASA instance in a guest network."
+msgstr ""
+
+#: ../../network_setup.rst:487
+# 569e13e1167c4a76a6f5134ef65d99e8
+msgid "Only one Cisco VNMC per zone is allowed."
+msgstr ""
+
+#: ../../network_setup.rst:489
+# bb939448a41a44189ebb9d02a40c6b17
+msgid "Supported only in Inline mode deployment with load balancer."
+msgstr ""
+
+#: ../../network_setup.rst:491
+# 877c7cf7a46f4eb1a593397a10187a6a
+msgid "The ASA firewall rule is applicable to all the public IPs in the guest network. Unlike the firewall rules created on virtual router, a rule created on the ASA device is not tied to a specific public IP."
+msgstr ""
+
+#: ../../network_setup.rst:495
+# cf88d5219d574e44bfc0c436912c5391
+msgid "Use a version of Cisco Nexus 1000v dvSwitch that support the vservice command. For example: nexus-1000v.4.2.1.SV1.5.2b.bin"
+msgstr ""
+
+#: ../../network_setup.rst:498
+# 6de75b299213451ea9108722f5431abf
+msgid "Cisco VNMC requires the vservice command to be available on the Nexus switch to create a guest network in CloudStack."
+msgstr ""
+
+#: ../../network_setup.rst:503
+# 39bbc9648cf346ba995bd567cba5a91c
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../network_setup.rst:505
+# c4d87ffce9ee418bb5277196957041d2
+msgid "Configure Cisco Nexus 1000v dvSwitch in a vCenter environment."
+msgstr ""
+
+#: ../../network_setup.rst:507
+# 273055b3e10447eb9f6ee66aa7c56122
+msgid "Create Port profiles for both internal and external network interfaces on Cisco Nexus 1000v dvSwitch. Note down the inside port profile, which needs to be provided while adding the ASA appliance to CloudStack."
+msgstr ""
+
+#: ../../network_setup.rst:512
+# e38227e22a094d63bc1b850e584bf3b9
+msgid "For information on configuration, see `“Configuring a vSphere Cluster with Nexus 1000v Virtual Switch” <hypervisor_installation.html#configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch>`_."
+msgstr ""
+
+#: ../../network_setup.rst:516
+# 55fe45ec845548cbb8a78e36f3c06ec0
+msgid "Deploy and configure Cisco VNMC."
+msgstr ""
+
+#: ../../network_setup.rst:518
+# f746770abf4f45ef945ff3f0a26b584a
+msgid "For more information, see `Installing Cisco Virtual Network Management Center <http://www.cisco.com/en/US/docs/switches/datacenter/vsg/sw/4_2_1_VSG_2_1_1/install_upgrade/guide/b_Cisco_VSG_for_VMware_vSphere_Rel_4_2_1_VSG_2_1_1_and_Cisco_VNMC_Rel_2_1_Installation_and_Upgrade_Guide_chapter_011.html>`_ and `Configuring Cisco Virtual Network Management Center <http://www.cisco.com/en/US/docs/unified_computing/vnmc/sw/1.2/VNMC_GUI_Configuration/b_VNMC_GUI_Configuration_Guide_1_2_chapter_010.html>`_."
+msgstr ""
+
+#: ../../network_setup.rst:524
+# 890a0309246f4e1cb3c358dcb4e98983
+msgid "Register Cisco Nexus 1000v dvSwitch with Cisco VNMC."
+msgstr ""
+
+#: ../../network_setup.rst:526
+# 5d7310375c57493aa147f26420784b38
+msgid "For more information, see `Registering a Cisco Nexus 1000V with Cisco VNMC <http://www.cisco.com/en/US/docs/switches/datacenter/vsg/sw/4_2_1_VSG_1_2/vnmc_and_vsg_qi/guide/vnmc_vsg_install_5register.html#wp1064301>`_."
+msgstr ""
+
+#: ../../network_setup.rst:529
+# 500816abfa7f432d9ed94665ff42315a
+msgid "Create Inside and Outside port profiles in Cisco Nexus 1000v dvSwitch."
+msgstr ""
+
+#: ../../network_setup.rst:531
+# 76cabd3f3582426c8c8810e144eb23f3
+msgid "For more information, see `“Configuring a vSphere Cluster with Nexus 1000v Virtual Switch” <hypervisor_installation.html#configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch>`_."
+msgstr ""
+
+#: ../../network_setup.rst:535
+# ff2dcbffa1b14e5ab64b8c834942483e
+msgid "Deploy and Cisco ASA 1000v appliance."
+msgstr ""
+
+#: ../../network_setup.rst:537
+# 39146f72a8c84d28bc65e5fa9dd4cdb9
+msgid "For more information, see `Setting Up the ASA 1000V Using VNMC <http://www.cisco.com/en/US/docs/security/asa/quick_start/asa1000V/setup_vnmc.html>`_."
+msgstr ""
+
+#: ../../network_setup.rst:540
+# 2165e5de14094930bed61e6b01f0b77a
+msgid "Typically, you create a pool of ASA 1000v appliances and register them with CloudStack."
+msgstr ""
+
+#: ../../network_setup.rst:543
+# 71608798f1724b909bf18251bbcdce75
+msgid "Specify the following while setting up a Cisco ASA 1000v instance:"
+msgstr ""
+
+#: ../../network_setup.rst:545
+# e7347e3b34f14bfdb63251d3628abbdd
+msgid "VNMC host IP."
+msgstr ""
+
+#: ../../network_setup.rst:547
+# 6b0bb824d6ba4c308a4713de3f38b8bb
+msgid "Ensure that you add ASA appliance in VNMC mode."
+msgstr ""
+
+#: ../../network_setup.rst:549
+# 70e3ab12a94645d9b8db4379ed6c40e6
+msgid "Port profiles for the Management and HA network interfaces. This need to be pre-created on Cisco Nexus 1000v dvSwitch."
+msgstr ""
+
+#: ../../network_setup.rst:552
+# c53ff0d84fc941c28feda24f9e7e4eef
+msgid "Internal and external port profiles."
+msgstr ""
+
+#: ../../network_setup.rst:554
+# 45b55744d6e247269c14c32af61e6b04
+msgid "The Management IP for Cisco ASA 1000v appliance. Specify the gateway such that the VNMC IP is reachable."
+msgstr ""
+
+#: ../../network_setup.rst:557
+# 199952960bde4c1d8f20c181417792e5
+msgid "Administrator credentials"
+msgstr ""
+
+#: ../../network_setup.rst:559
+# 93c5f22490074bdc99e81cd94c41d53a
+msgid "VNMC credentials"
+msgstr ""
+
+#: ../../network_setup.rst:561
+# 10dbc0618ab842719aa3772b2e8784fa
+msgid "Register Cisco ASA 1000v with VNMC."
+msgstr ""
+
+#: ../../network_setup.rst:563
+# 5966ea52cf464c80b807747bebbc8460
+msgid "After Cisco ASA 1000v instance is powered on, register VNMC from the ASA console."
+msgstr ""
+
+#: ../../network_setup.rst:568
+# 3a33bfedd41d4a64b21fb24beccb4b22
+msgid "Using Cisco ASA 1000v Services"
+msgstr ""
+
+#: ../../network_setup.rst:570
+# 92702d5dd3bb4e1489e83c77093f1a05
+msgid "Ensure that all the prerequisites are met."
+msgstr ""
+
+#: ../../network_setup.rst:572
+# 1c86dda56f9b4f1d95dd04a56a545eb6
+msgid "See `“Prerequisites” <#prerequisites>`_."
+msgstr ""
+
+#: ../../network_setup.rst:574
+# 2a96e0eac83d460fb53cfd7a57b336a1
+msgid "Add a VNMC instance."
+msgstr ""
+
+#: ../../network_setup.rst:576
+# 7f2786b9a09648eca50126e66e9a1ce9
+msgid "See `“Adding a VNMC Instance” <#adding-a-vnmc-instance>`_."
+msgstr ""
+
+#: ../../network_setup.rst:578
+# 4c83a0155c3a4b9a8c3e224f13a38643
+msgid "Add a ASA 1000v instance."
+msgstr ""
+
+#: ../../network_setup.rst:580
+# df320d40f5224132a3f107b3d70f5a1f
+msgid "See `“Adding an ASA 1000v Instance” <#adding-an-asa-1000v-instance>`_."
+msgstr ""
+
+#: ../../network_setup.rst:582
+# 69e5eb4309584257937bdb75fd4756ab
+msgid "Create a Network Offering and use Cisco VNMC as the service provider for desired services."
+msgstr ""
+
+#: ../../network_setup.rst:585
+# f8bc670f1d1e410d87eb7bebed9dd50b
+msgid "See `“Creating a Network Offering Using Cisco ASA 1000v” <#creating-a-network-offering-using-cisco-asa-1000v>`_."
+msgstr ""
+
+#: ../../network_setup.rst:588
+# b9f4e08c2e4c47038a2651d6e8c45f9a
+msgid "Create an Isolated Guest Network by using the network offering you just created."
+msgstr ""
+
+#: ../../network_setup.rst:593
+# dd9740c27dcd49caa18b1e07599c945d
+msgid "Adding a VNMC Instance"
+msgstr ""
+
+#: ../../network_setup.rst:595
+#: ../../network_setup.rst:629
+#: ../../network_setup.rst:1012
+# c1cfcf6b2714482981a36cdf521b5676
+# b1a384e4258345fcaf5a2c57a062033e
+# fd3b312d35ff4d32b0aeba868015673e
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../network_setup.rst:603
+#: ../../network_setup.rst:637
+# eb09321188c441c584e06b8b6ae6a816
+# fe02f530f0044688a207897b58ff2421
+msgid "Click the Physical Network tab."
+msgstr ""
+
+#: ../../network_setup.rst:605
+#: ../../network_setup.rst:639
+# 758d3cd3abe240e3b4b45b46e4fd7293
+# 3eba5d220d984b70b68217882aa7a82b
+msgid "In the Network Service Providers node of the diagram, click Configure."
+msgstr ""
+
+#: ../../network_setup.rst:608
+#: ../../network_setup.rst:642
+# b2023dfd763a46f2b35bb495d2c6caae
+# 1059ea2b826b4b21b8c818daf678ca46
+msgid "You might have to scroll down to see this."
+msgstr ""
+
+#: ../../network_setup.rst:610
+#: ../../network_setup.rst:644
+# c87503e43e8a4a25a77c4166e02fdef5
+# fdfcc18249374b7c94616ea1de46f8a3
+msgid "Click Cisco VNMC."
+msgstr ""
+
+#: ../../network_setup.rst:612
+# 4f9b7772a8f346af94c367b56c696bff
+msgid "Click View VNMC Devices."
+msgstr ""
+
+#: ../../network_setup.rst:614
+# 473f0d6944a641d293e217e69b575982
+msgid "Click the Add VNMC Device and provide the following:"
+msgstr ""
+
+#: ../../network_setup.rst:616
+# 9d8b2cf61ebf4f0b9d20bde66eb2ada4
+msgid "Host: The IP address of the VNMC instance."
+msgstr ""
+
+#: ../../network_setup.rst:618
+# 3056ecd7f30744acb87118d6b31faf4d
+msgid "Username: The user name of the account on the VNMC instance that CloudStack should use."
+msgstr ""
+
+#: ../../network_setup.rst:627
+# d98ce3e9beba49e3b8be96b27970e903
+msgid "Adding an ASA 1000v Instance"
+msgstr ""
+
+#: ../../network_setup.rst:646
+# d58faf4c65d447f7b1ed654fa6d773ef
+msgid "Click View ASA 1000v."
+msgstr ""
+
+#: ../../network_setup.rst:648
+# 48a7684e388a4a1199086e67b9e06fbf
+msgid "Click the Add CiscoASA1000v Resource and provide the following:"
+msgstr ""
+
+#: ../../network_setup.rst:650
+# 928909e6ab0a423cbdb8e647f25772b2
+msgid "**Host**: The management IP address of the ASA 1000v instance. The IP address is used to connect to ASA 1000V."
+msgstr ""
+
+#: ../../network_setup.rst:653
+# 70321795345648bd9c1da27a348d9622
+msgid "**Inside Port Profile**: The Inside Port Profile configured on Cisco Nexus1000v dvSwitch."
+msgstr ""
+
+#: ../../network_setup.rst:656
+# 32b609836a04453fb6a045d870d7326f
+msgid "**Cluster**: The VMware cluster to which you are adding the ASA 1000v instance."
+msgstr ""
+
+#: ../../network_setup.rst:659
+# cd7f376d7aa849a4a7247501f60ba869
+msgid "Ensure that the cluster is Cisco Nexus 1000v dvSwitch enabled."
+msgstr ""
+
+#: ../../network_setup.rst:665
+# a3980b1ab6084e3db8cd7521a2eedaea
+msgid "Creating a Network Offering Using Cisco ASA 1000v"
+msgstr ""
+
+#: ../../network_setup.rst:667
+# 950a38dbcb1e421a9f535a092c783907
+msgid "To have Cisco ASA 1000v support for a guest network, create a network offering as follows:"
+msgstr ""
+
+#: ../../network_setup.rst:670
+# e92f8d283bd34673bd9c78e81833668e
+msgid "Log in to the CloudStack UI as a user or admin."
+msgstr ""
+
+#: ../../network_setup.rst:672
+# 26660317d6fb41258f3d2b9a406f298d
+msgid "From the Select Offering drop-down, choose Network Offering."
+msgstr ""
+
+#: ../../network_setup.rst:674
+# ddecb14ca4124b1998831a3da0e5db4f
+msgid "Click Add Network Offering."
+msgstr ""
+
+#: ../../network_setup.rst:676
+# dc73890ea66e4303ac2aa89bff57c086
+msgid "In the dialog, make the following choices:"
+msgstr ""
+
+#: ../../network_setup.rst:678
+# 8cc2e100f0cb4ebfbfaf9c9deadcbaba
+msgid "**Name**: Any desired name for the network offering."
+msgstr ""
+
+#: ../../network_setup.rst:680
+# dd1d1924540f4e5dbedd6e9a2218be68
+msgid "**Description**: A short description of the offering that can be displayed to users."
+msgstr ""
+
+#: ../../network_setup.rst:683
+# 26e660fc8ea74ce28ac609f6c584cbd2
+msgid "**Network Rate**: Allowed data transfer rate in MB per second."
+msgstr ""
+
+#: ../../network_setup.rst:685
+# dd894b5b99ef46fa91b4e2548ecbc571
+msgid "**Traffic Type**: The type of network traffic that will be carried on the network."
+msgstr ""
+
+#: ../../network_setup.rst:688
+# eae0966c87144700836fc5e823127d8b
+msgid "**Guest Type**: Choose whether the guest network is isolated or shared."
+msgstr ""
+
+#: ../../network_setup.rst:691
+# e54268df1bbe4a2099f3e8c010a00d9f
+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."
+msgstr ""
+
+#: ../../network_setup.rst:695
+# 4fc96223cb514c21a8ec82d8d753d7c9
+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” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/networking2.html#about-virtual-private-clouds>`_."
+msgstr ""
+
+#: ../../network_setup.rst:702
+# f00fa325f09746919b9d1009245f5015
+msgid "**Specify VLAN**: (Isolated guest networks only) Indicate whether a VLAN should be specified when this offering is used."
+msgstr ""
+
+#: ../../network_setup.rst:705
+# 3d3c6a5287e4473f8185c047e07a1974
+msgid "**Supported Services**: Use Cisco VNMC as the service provider for Firewall, Source NAT, Port Forwarding, and Static NAT to create an Isolated guest network offering."
+msgstr ""
+
+#: ../../network_setup.rst:709
+# bc538b1440fd4510b0825b413a042fee
+msgid "**System Offering**: Choose the system service offering that you want virtual routers to use in this network."
+msgstr ""
+
+#: ../../network_setup.rst:712
+# 26faeb25fa524771be1e615d700372ba
+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."
+msgstr ""
+
+#: ../../network_setup.rst:716
+# 4ef16133df3a464390c7fee43388e910
+msgid "Click OK"
+msgstr ""
+
+#: ../../network_setup.rst:718
+# a7992266e0284c60a8f1095f8f4c12e3
+msgid "The network offering is created."
+msgstr ""
+
+#: ../../network_setup.rst:722
+# a742daa985a44045b5e372c411ffc6c2
+msgid "Reusing ASA 1000v Appliance in new Guest Networks"
+msgstr ""
+
+#: ../../network_setup.rst:724
+# 4a0aa5f289c5495e98a8b4baaaf6a814
+msgid "You can reuse an ASA 1000v appliance in a new guest network after the necessary cleanup. Typically, ASA 1000v is cleaned up when the logical edge firewall is cleaned up in VNMC. If this cleanup does not happen, you need to reset the appliance to its factory settings for use in new guest networks. As part of this, enable SSH on the appliance and store the SSH credentials by registering on VNMC."
+msgstr ""
+
+#: ../../network_setup.rst:731
+# 20ad628b69124229b5574084ade4cb93
+msgid "Open a command line on the ASA appliance:"
+msgstr ""
+
+#: ../../network_setup.rst:733
+# 105a7e29f0ad4898a7c75a9729dede0a
+msgid "Run the following:"
+msgstr ""
+
+#: ../../network_setup.rst:739
+# 6ab19d6d2e0042538cbbeb508cd0749c
+msgid "You are prompted with the following message:"
+msgstr ""
+
+#: ../../network_setup.rst:745
+# f0bc8a73d1ca4c1dbb83304efbb74e39
+msgid "Enter N."
+msgstr ""
+
+#: ../../network_setup.rst:747
+# 8b41e1b3b97942c2834f1d7ac78e9bb1
+msgid "You will get the following confirmation message:"
+msgstr ""
+
+#: ../../network_setup.rst:753
+# dfb5d4fffbb5409db3ce8728237aa0bc
+msgid "Restart the appliance."
+msgstr ""
+
+#: ../../network_setup.rst:755
+# 23cee1ad7b844c61a8902f657c8beb73
+msgid "Register the ASA 1000v appliance with the VNMC:"
+msgstr ""
+
+#: ../../network_setup.rst:765
+# dc2f284a64c245a29344154ada915e58
+msgid "External Guest Load Balancer Integration (Optional)"
+msgstr ""
+
+#: ../../network_setup.rst:767
+# 9d948a00894c4f2fa6895235bd45cd3e
+msgid "CloudStack can optionally use a Citrix NetScaler or BigIP F5 load balancer to provide load balancing services to guests. If this is not enabled, CloudStack will use the software load balancer in the virtual router."
+msgstr ""
+
+#: ../../network_setup.rst:772
+# dabdfbfa1edc4c61a06597ddc02e6d92
+msgid "To install and enable an external load balancer for CloudStack management:"
+msgstr ""
+
+#: ../../network_setup.rst:775
+# f0578c75b13b4167a35650d6618c3b63
+msgid "Set up the appliance according to the vendor's directions."
+msgstr ""
+
+#: ../../network_setup.rst:777
+# acd66698614d49f18d286135e6689c3d
+msgid "Connect it to the networks carrying public traffic and management traffic (these could be the same network)."
+msgstr ""
+
+#: ../../network_setup.rst:780
+# 91c057c2c551461e8a07b2887f28b3fa
+msgid "Record the IP address, username, password, public interface name, and private interface name. The interface names will be something like \"1.1\" or \"1.2\"."
+msgstr ""
+
+#: ../../network_setup.rst:784
+# af8d438df7ea4817814040c1ddc43feb
+msgid "Make sure that the VLANs are trunked to the management network interface."
+msgstr ""
+
+#: ../../network_setup.rst:787
+# 13351032ab9f44cbadb116a21a1d44f3
+msgid "After the CloudStack Management Server is installed, log in as administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../network_setup.rst:801
+# aded9ee3be254e338c7d4e6b7edf7f97
+msgid "Click NetScaler or F5."
+msgstr ""
+
+#: ../../network_setup.rst:803
+# 1ce1bb2fbaf14b22a9dd5c8a16924159
+msgid "Click the Add button (+) and provide the following:"
+msgstr ""
+
+#: ../../network_setup.rst:805
+# a2d8bdc55c3c40028eb64d6e1ae7c16f
+msgid "For NetScaler:"
+msgstr ""
+
+#: ../../network_setup.rst:809
+# 1f6de479819a4db684f63f0307d1dc32
+msgid "Username/Password: The authentication credentials to access the device. CloudStack uses these credentials to access the device."
+msgstr ""
+
+#: ../../network_setup.rst:812
+# 5208277aaa9c4a5a867a0d1fd2ec2854
+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 ""
+
+#: ../../network_setup.rst:817
+# a81a8b45b0364dc28f2b425a8d636be6
+msgid "Public interface: Interface of device that is configured to be part of the public network."
+msgstr ""
+
+#: ../../network_setup.rst:820
+# 88814119e09a4dd0921efaa7b868b7d7
+msgid "Private interface: Interface of device that is configured to be part of the private network."
+msgstr ""
+
+#: ../../network_setup.rst:823
+# a3d9da03a32f413994871acf89781192
+msgid "Number of retries. Number of times to attempt a command on the device before considering the operation failed. Default is 2."
+msgstr ""
+
+#: ../../network_setup.rst:826
+# 9fdbb29c229243e3ae2770682cec2268
+msgid "Capacity: The number of networks the device can handle."
+msgstr ""
+
+#: ../../network_setup.rst:828
+# 746f18e5c26844098f69c70f3531eac4
+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 ""
+
+#: ../../network_setup.rst:834
+# 8d71ee3b3ba24ef2b09f051382c84f02
+msgid "The installation and provisioning of the external load balancer is finished. You can proceed to add VMs and NAT or load balancing rules."
+msgstr ""
+
+#: ../../network_setup.rst:839
+# 168e73c12edc4ddfb7ceadf3950a1441
+msgid "Management Server Load Balancing"
+msgstr ""
+
+#: ../../network_setup.rst:841
+# d1c9832bb0ec4c889904900754150662
+msgid "CloudStack can use a load balancer to provide a virtual IP for multiple Management Servers. The administrator is responsible for creating the load balancer rules for the Management Servers. The application requires persistence or stickiness across multiple sessions. The following chart lists the ports that should be load balanced and whether or not persistence is required."
+msgstr ""
+
+#: ../../network_setup.rst:848
+# 8d59260980c2412d96a8664b0731bd47
+msgid "Even if persistence is not required, enabling it is permitted."
+msgstr ""
+
+#: ../../network_setup.rst:851
+# f4777f724d85477090b55c4396cc6f35
+msgid "Source Port"
+msgstr ""
+
+#: ../../network_setup.rst:851
+# 7d326aaf15ab44afa0cd31c1e3fe5590
+msgid "Destination Port"
+msgstr ""
+
+#: ../../network_setup.rst:851
+# c1da26dd22ac4a4baafe30bd8b745382
+msgid "Protocol"
+msgstr ""
+
+#: ../../network_setup.rst:851
+# b2352632cff44c4db47d589dc77aac90
+msgid "Persistence Required?"
+msgstr ""
+
+#: ../../network_setup.rst:853
+# 4a62a34b37034a728bdbe3708bec46b4
+msgid "80 or 443"
+msgstr ""
+
+#: ../../network_setup.rst:853
+# e53c8ab237804881bcb3014d9b434e24
+msgid "8080 (or 20400 with AJP)"
+msgstr ""
+
+#: ../../network_setup.rst:853
+# 8e55087fd18c478189ed323b50a78e15
+msgid "HTTP (or AJP)"
+msgstr ""
+
+#: ../../network_setup.rst:854
+#: ../../network_setup.rst:854
+# 910dae6e62db4b6c87bcd33fba33a41b
+# 625d27f875424cbca2735e4e71329264
+msgid "8250"
+msgstr ""
+
+#: ../../network_setup.rst:854
+# 58601595abf7493fadec45a9912276d6
+msgid "TCP"
+msgstr ""
+
+#: ../../network_setup.rst:855
+#: ../../network_setup.rst:855
+# 52192943fcd04698aaf9f3033585bc65
+# a4a53f84a8ed45d2bc84a2fef1df06d4
+msgid "8096"
+msgstr ""
+
+#: ../../network_setup.rst:855
+# 2f45fefee5c04295b3ef2346baaefbf5
+msgid "HTTP"
+msgstr ""
+
+#: ../../network_setup.rst:858
+# 56b9fa972912451e936f67a7001a6771
+msgid "In addition to above settings, the administrator is responsible for setting the 'host' global config value from the management server IP to load balancer virtual IP address. If the 'host' value is not set to the VIP for Port 8250 and one of your management servers crashes, the UI is still available but the system VMs will not be able to contact the management server."
+msgstr ""
+
+#: ../../network_setup.rst:867
+# ad76871b34a845f5b9d235414f2306e5
+msgid "Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:870
+# 636bca2e871e41729f5af58bc925cfbd
+msgid "Security Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:872
+# b84e3ab736f74a93915035c25c5732ee
+msgid "The public Internet must not be able to access port 8096 or port 8250 on the Management Server."
+msgstr ""
+
+#: ../../network_setup.rst:877
+# a6a9845e5dae4c1c864c36674244fecc
+msgid "Runtime Internal Communications Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:879
+# 268c7a6bce4541139e2a22fe23738d00
+msgid "The Management Servers communicate with each other to coordinate tasks. This communication uses TCP on ports 8250 and 9090."
+msgstr ""
+
+#: ../../network_setup.rst:882
+# ce28693898e94e9d86c98a6e41acb59e
+msgid "The console proxy VMs connect to all hosts in the zone over the management traffic network. Therefore the management traffic network of any given pod in the zone must have connectivity to the management traffic network of all other pods in the zone."
+msgstr ""
+
+#: ../../network_setup.rst:887
+# 2cc6b18efa544724b94a396ea3f29997
+msgid "The secondary storage VMs and console proxy VMs connect to the Management Server on port 8250. If you are using multiple Management Servers, the load balanced IP address of the Management Servers on port 8250 must be reachable."
+msgstr ""
+
+#: ../../network_setup.rst:894
+# aa5c7cf265704eac9214b589ca5ec409
+msgid "Storage Network Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:896
+# e41b0df94da8462e80b7ef8072966db0
+msgid "The secondary storage NFS export is mounted by the secondary storage VM. Secondary storage traffic goes over the management traffic network, even if there is a separate storage network. Primary storage traffic goes over the storage network, if available. If you choose to place secondary storage NFS servers on the storage network, you must make sure there is a route from the management traffic network to the storage network."
+msgstr ""
+
+#: ../../network_setup.rst:905
+# 319f0bc16b9c43b285b5381f9c1e1641
+msgid "External Firewall Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:907
+# ef03ddf7f4c1473aaffbab8f2ea10b90
+msgid "When external firewall integration is in place, the public IP VLAN must still be trunked to the Hosts. This is required to support the Secondary Storage VM and Console Proxy VM."
+msgstr ""
+
+#: ../../network_setup.rst:913
+# 8f340bd0be4a45cb9a554d08e4940824
+msgid "Advanced Zone Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:915
+# 59155e8fb1be458d919a18044910e40e
+msgid "With Advanced Networking, separate subnets must be used for private and public networks."
+msgstr ""
+
+#: ../../network_setup.rst:920
+# 703fcda90934401caaa25a5f12b77075
+msgid "XenServer Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:922
+# 66fa97319fba4438b1ab49713ba74d45
+msgid "The Management Servers communicate with XenServer hosts on ports 22 (ssh), 80 (HTTP), and 443 (HTTPs)."
+msgstr ""
+
+#: ../../network_setup.rst:927
+# 2a5693ecef9344fc85b357817cb3136c
+msgid "VMware Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:929
+# 825745d3504c4edd9d998f356c622430
+msgid "The Management Server and secondary storage VMs must be able to access vCenter and all ESXi hosts in the zone. To allow the necessary access through the firewall, keep port 443 open."
+msgstr ""
+
+#: ../../network_setup.rst:933
+# e5239c897a2846df832e554fc87473b0
+msgid "The Management Servers communicate with VMware vCenter servers on port 443 (HTTPs)."
+msgstr ""
+
+#: ../../network_setup.rst:936
+# fb344a5b995d40428766c436e513381b
+msgid "The Management Servers communicate with the System VMs on port 3922 (ssh) on the management traffic network."
+msgstr ""
+
+#: ../../network_setup.rst:941
+# 45f7ce4ca7ee48d080ee6ad2646b28da
+msgid "Hyper-V Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:943
+# 468d7be21f9d4bd3847b12047def08d4
+msgid "CloudStack Management Server communicates with Hyper-V Agent by using HTTPS. For secure communication between the Management Server and the Hyper-V host, open port 8250."
+msgstr ""
+
+#: ../../network_setup.rst:949
+# 1a3519c089b44acd951ab261264deb13
+msgid "KVM Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:951
+# b11a692480274211affee6c78a638bf8
+msgid "The Management Servers communicate with KVM hosts on port 22 (ssh)."
+msgstr ""
+
+#: ../../network_setup.rst:955
+# 7586273883f448f7b24cc0138e7970b7
+msgid "LXC Topology Requirements"
+msgstr ""
+
+#: ../../network_setup.rst:957
+# 259d6b031a2c4d2f99a0d64809c8b0a1
+msgid "The Management Servers communicate with LXC hosts on port 22 (ssh)."
+msgstr ""
+
+#: ../../network_setup.rst:961
+# 888d66b82f3446f1af4ee373439875ad
+msgid "Guest Network Usage Integration for Traffic Sentinel"
+msgstr ""
+
+#: ../../network_setup.rst:963
+# 29cc34c6bee74b8d9727b38945612791
+msgid "To collect usage data for a guest network, CloudStack needs to pull the data from an external network statistics collector installed on the network. Metering statistics for guest networks are available through CloudStack’s integration with inMon Traffic Sentinel."
+msgstr ""
+
+#: ../../network_setup.rst:968
+# d397ec50b01f43649a71d382811b5c4e
+msgid "Traffic Sentinel is a network traffic usage data collection package. CloudStack can feed statistics from Traffic Sentinel into its own usage records, providing a basis for billing users of cloud infrastructure. Traffic Sentinel uses the traffic monitoring protocol sFlow. Routers and switches generate sFlow records and provide them for collection by Traffic Sentinel, then CloudStack queries the Traffic Sentinel database to obtain this information"
+msgstr ""
+
+#: ../../network_setup.rst:976
+# 0421d85f71a9457aa65c99fe3edf321e
+msgid "To construct the query, CloudStack determines what guest IPs were in use during the current query interval. This includes both newly assigned IPs and IPs that were assigned in a previous time period and continued to be in use. CloudStack queries Traffic Sentinel for network statistics that apply to these IPs during the time period they remained allocated in CloudStack. The returned data is correlated with the customer account that owned each IP and the timestamps when IPs were assigned and released in order to create billable metering records in CloudStack. When the Usage Server runs, it collects this data."
+msgstr ""
+
+#: ../../network_setup.rst:986
+# 711ce8174a9244d4af0b4fb81578f64b
+msgid "To set up the integration between CloudStack and Traffic Sentinel:"
+msgstr ""
+
+#: ../../network_setup.rst:988
+# 1c2e09dc5c8447d1ba4f95812f28af41
+msgid "On your network infrastructure, install Traffic Sentinel and configure it to gather traffic data. For installation and configuration steps, see inMon documentation at `Traffic Sentinel Documentation <http://inmon.com.>`_."
+msgstr ""
+
+#: ../../network_setup.rst:993
+# 412e3e6834394480af6f9e65fd4aba2d
+msgid "In the Traffic Sentinel UI, configure Traffic Sentinel to accept script querying from guest users. CloudStack will be the guest user performing the remote queries to gather network usage for one or more IP addresses."
+msgstr ""
+
+#: ../../network_setup.rst:998
+# 12a1bbfb3cec4016a739bec145bd8a9c
+msgid "Click File > Users > Access Control > Reports Query, then select Guest from the drop-down list."
+msgstr ""
+
+#: ../../network_setup.rst:1001
+# 99d0d664da654239ad897c4d6eb6b08e
+msgid "On CloudStack, add the Traffic Sentinel host by calling the CloudStack API command addTrafficMonitor. Pass in the URL of the Traffic Sentinel as protocol + host + port (optional); for example, http://10.147.28.100:8080. For the addTrafficMonitor command syntax, see the API Reference at `API Documentation <http://cloudstack.apache.org/docs/api/index.html>`_."
+msgstr ""
+
+#: ../../network_setup.rst:1008
+# 382c1696b18d4f25a2e2b5b7cb142225
+msgid "For information about how to call the CloudStack API, see the Developer’s Guide at `CloudStack API Developer's Guide <http://docs.cloudstack.apache.org/en/latest/index.html#developers>`_."
+msgstr ""
+
+#: ../../network_setup.rst:1014
+# 47106f1a9e0142eb9832c2c332d903bf
+msgid "Select Configuration from the Global Settings page, and set the following:"
+msgstr ""
+
+#: ../../network_setup.rst:1017
+# fc6fdba63ec445fcb4c66fb37e5faef4
+msgid "direct.network.stats.interval: How often you want CloudStack to query Traffic Sentinel."
+msgstr ""
+
+#: ../../network_setup.rst:1022
+# 41cfa755d06741f186da5ae7aacb6cee
+msgid "Setting Zone VLAN and Running VM Maximums"
+msgstr ""
+
+#: ../../network_setup.rst:1024
+# a60e16faaf9041a9b9276598f5ee90f9
+msgid "In the external networking case, every VM in a zone must have a unique guest IP address. There are two variables that you need to consider in determining how to configure CloudStack to support this: how many Zone VLANs do you expect to have and how many VMs do you expect to have running in the Zone at any one time."
+msgstr ""
+
+#: ../../network_setup.rst:1030
+# d9028276c0544666b5e9721eeb5c8816
+msgid "Use the following table to determine how to configure CloudStack for your deployment."
+msgstr ""
+
+#: ../../network_setup.rst:1034
+# 072f26662ea44459b4fa1cf60692e712
+msgid "guest.vlan.bits"
+msgstr ""
+
+#: ../../network_setup.rst:1034
+# a6cb87fc1b2545d1b1ac09e37fd1be97
+msgid "Maximum Running VMs per Zone"
+msgstr ""
+
+#: ../../network_setup.rst:1034
+# 95b101b8c5db46528c0540ff8c64a5cb
+msgid "Maximum Zone VLANs"
+msgstr ""
+
+#: ../../network_setup.rst:1036
+# 67bdc701ec3c4dcf9cd3f5bd5e147554
+msgid "12"
+msgstr ""
+
+#: ../../network_setup.rst:1036
+# c8d94e62ee844b4e92d52b5c6827e058
+msgid "4096"
+msgstr ""
+
+#: ../../network_setup.rst:1036
+# ac4e2d28b54845f1a55c70377f48d5c3
+msgid "4094"
+msgstr ""
+
+#: ../../network_setup.rst:1037
+# 7bbc65e86d0147368c5a3431c20f5ed3
+msgid "11"
+msgstr ""
+
+#: ../../network_setup.rst:1037
+# 01351e134fd445688b9b975e860ff8ac
+msgid "8192"
+msgstr ""
+
+#: ../../network_setup.rst:1037
+# 1487356597e74d80ab906cdf7734c3e1
+msgid "2048"
+msgstr ""
+
+#: ../../network_setup.rst:1038
+#: ../../network_setup.rst:1039
+# 210a77ae5568419ab769fe82ba44a994
+# 066cf48d71dd4eea8015322cc0295f26
+msgid "10"
+msgstr ""
+
+#: ../../network_setup.rst:1038
+# ecffb57711494443b7bd29967fc90284
+msgid "16384"
+msgstr ""
+
+#: ../../network_setup.rst:1038
+# 77f877c5ae0c4cef92f9e8579cb50a8a
+msgid "1024"
+msgstr ""
+
+#: ../../network_setup.rst:1039
+# 7aec5b5262a84030b29ee9b48f82c955
+msgid "32768"
+msgstr ""
+
+#: ../../network_setup.rst:1039
+# bd2fc687ddab4d70beebf9747ba3aa15
+msgid "512"
+msgstr ""
+
+#: ../../network_setup.rst:1042
+# 1735a2a4d8bd40f2a1b021cf8879de91
+msgid "Based on your deployment's needs, choose the appropriate value of guest.vlan.bits. Set it as described in Edit the Global Configuration Settings (Optional) section and restart the Management Server."
+msgstr ""
+
diff --git a/source/installguide/locale/pot/optional_installation.pot b/source/installguide/locale/pot/optional_installation.pot
new file mode 100644
index 0000000..80ec79b
--- /dev/null
+++ b/source/installguide/locale/pot/optional_installation.pot
@@ -0,0 +1,1252 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../optional_installation.rst:18
+# 3ea1be6cb6c044ee88d6bbfe51d5a36f
+msgid "Additional Installation Options"
+msgstr ""
+
+#: ../../optional_installation.rst:20
+# 4be66c8884c44e5c92d33460a6cfbc99
+msgid "The next few sections describe CloudStack features above and beyond the basic deployment options."
+msgstr ""
+
+#: ../../optional_installation.rst:25
+# d620c97521d0471dbe9914ee7961101d
+msgid "Installing the Usage Server (Optional)"
+msgstr ""
+
+#: ../../optional_installation.rst:27
+# eba0c3d4623f4e30a2de16e6e1d3afbe
+msgid "You can optionally install the Usage Server once the Management Server is configured properly. The Usage Server takes data from the events in the system and enables usage-based billing for accounts."
+msgstr ""
+
+#: ../../optional_installation.rst:31
+# 2132611e22ac4180882c9e149411e658
+msgid "When multiple Management Servers are present, the Usage Server may be installed on any number of them. The Usage Servers will coordinate usage processing. A site that is concerned about availability should install Usage Servers on at least two Management Servers."
+msgstr ""
+
+#: ../../optional_installation.rst:38
+# d0a9099047bd453a90fef5ce7d86283b
+msgid "Requirements for Installing the Usage Server"
+msgstr ""
+
+#: ../../optional_installation.rst:40
+# 0443dcade9d44c4ca65794d68927d9ca
+msgid "The Management Server must be running when the Usage Server is installed."
+msgstr ""
+
+#: ../../optional_installation.rst:43
+# 309364cef90c4a6fbf5a8394ac1e35c4
+msgid "The Usage Server must be installed on the same server as a Management Server."
+msgstr ""
+
+#: ../../optional_installation.rst:48
+# a251a7029fa243b691964f23e74a9ed4
+msgid "Steps to Install the Usage Server"
+msgstr ""
+
+#: ../../optional_installation.rst:50
+# 79637a12758d457f9620403344f42b69
+msgid "Run ./install.sh (NOT VALID, NEED CORRECTION)"
+msgstr ""
+
+#: ../../optional_installation.rst:56
+# b47571da344e4965be7a837f8ebe714a
+msgid "You should see a few messages as the installer prepares, followed by a list of choices."
+msgstr ""
+
+#: ../../optional_installation.rst:59
+# 52d83849a75649fbaba2e382ef537b2e
+msgid "Choose \"S\" to install the Usage Server."
+msgstr ""
+
+#: ../../optional_installation.rst:65
+# 1139aed06e7d4d259522f2bf84205698
+msgid "Once installed, start the Usage Server with the following command."
+msgstr ""
+
+#: ../../optional_installation.rst:71
+# f85323259c174815b1da8521f464edda
+msgid "The Administration Guide discusses further configuration of the Usage Server."
+msgstr ""
+
+#: ../../optional_installation.rst:76
+# 62c0216a817941d59e5712145ef98305
+msgid "SSL (Optional)"
+msgstr ""
+
+#: ../../optional_installation.rst:78
+# 1cc339b8bee1425a9342eddde3366517
+msgid "CloudStack provides HTTP access in its default installation. There are a number of technologies and sites which choose to implement SSL. As a result, we have left CloudStack to expose HTTP under the assumption that a site will implement its typical practice."
+msgstr ""
+
+#: ../../optional_installation.rst:83
+# 592c0ac6d2e04347a4dd45ef76eafab0
+msgid "CloudStack uses Tomcat as its servlet container. For sites that would like CloudStack to terminate the SSL session, Tomcat’s SSL access may be enabled. Tomcat SSL configuration is described at http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html."
+msgstr ""
+
+#: ../../optional_installation.rst:90
+# 312c03f93afc4a98a82df1811062af96
+msgid "Database Replication (Optional)"
+msgstr ""
+
+#: ../../optional_installation.rst:92
+# 7862ab06634f4e73aea90b6a69fba6d8
+msgid "CloudStack supports database replication from one MySQL node to another. This is achieved using standard MySQL replication. You may want to do this as insurance against MySQL server or storage loss. MySQL replication is implemented using a master/slave model. The master is the node that the Management Servers are configured to use. The slave is a standby node that receives all write operations from the master and applies them to a local, redundant copy of the database. The following steps are a guide to implementing MySQL replication."
+msgstr ""
+
+#: ../../optional_installation.rst:102
+# b03832e56503442494767e262e0d5266
+msgid "Creating a replica is not a backup solution. You should develop a backup procedure for the MySQL data that is distinct from replication."
+msgstr ""
+
+#: ../../optional_installation.rst:105
+# 8f01c4d5d9e849f7aa21e1fafec88427
+msgid "Ensure that this is a fresh install with no data in the master."
+msgstr ""
+
+#: ../../optional_installation.rst:107
+# 3207c0439bb34ea28e96d4ee62ad1c2e
+msgid "Edit my.cnf on the master and add the following in the [mysqld] section below datadir."
+msgstr ""
+
+#: ../../optional_installation.rst:115
+# 5d1dfef940ab48418d921ea6ab2104d5
+msgid "The server\\_id must be unique with respect to other servers. The recommended way to achieve this is to give the master an ID of 1 and each slave a sequential number greater than 1, so that the servers are numbered 1, 2, 3, etc."
+msgstr ""
+
+#: ../../optional_installation.rst:120
+# 3b36dc410ff54ea89e014b950f48408a
+msgid "Restart the MySQL service. On RHEL/CentOS systems, use:"
+msgstr ""
+
+#: ../../optional_installation.rst:126
+# 3b34254879f64ec58d72150d828d019f
+msgid "On Debian/Ubuntu systems, use:"
+msgstr ""
+
+#: ../../optional_installation.rst:132
+# 37951ede2d454f428070c346ebef21fd
+msgid "Create a replication account on the master and give it privileges. We will use the \"cloud-repl\" user with the password \"password\". This assumes that master and slave run on the 172.16.1.0/24 network."
+msgstr ""
+
+#: ../../optional_installation.rst:144
+# f487c49c63214050912b21eef50fb648
+msgid "Leave the current MySQL session running."
+msgstr ""
+
+#: ../../optional_installation.rst:146
+# 6c09640cbc0342ddb5e30bbdc8e8721e
+msgid "In a new shell start a second MySQL session."
+msgstr ""
+
+#: ../../optional_installation.rst:148
+# 19bf58dc11664a8fbec99bb36a1c660f
+msgid "Retrieve the current position of the database."
+msgstr ""
+
+#: ../../optional_installation.rst:160
+# dc3fedfd512549e9bf54e76e6af57e8a
+msgid "Note the file and the position that are returned by your instance."
+msgstr ""
+
+#: ../../optional_installation.rst:162
+# 8043382dff184852bc33635d21cfd8da
+msgid "Exit from this session."
+msgstr ""
+
+#: ../../optional_installation.rst:164
+# 3448c24480a343129c3e323c59e1d52f
+msgid "Complete the master setup. Returning to your first session on the master, release the locks and exit MySQL."
+msgstr ""
+
+#: ../../optional_installation.rst:171
+# b756f3987b8345d78bb98a1da0cdf5f0
+msgid "Install and configure the slave. On the slave server, run the following commands."
+msgstr ""
+
+#: ../../optional_installation.rst:179
+# ce5052106169447d867315b4ab5acf5c
+msgid "Edit my.cnf and add the following lines in the [mysqld] section below datadir."
+msgstr ""
+
+#: ../../optional_installation.rst:188
+# 32a595c11f6f493f8d97ee7f2eaca7ca
+msgid "Restart MySQL. Use \"mysqld\" on RHEL/CentOS systems:"
+msgstr ""
+
+#: ../../optional_installation.rst:194
+# 86098df7874048268b21ceab1348fc66
+msgid "On Ubuntu/Debian systems use \"mysql.\""
+msgstr ""
+
+#: ../../optional_installation.rst:200
+# cc3fe860c3244bfaabe3d4c4317c7ac8
+msgid "Instruct the slave to connect to and replicate from the master. Replace the IP address, password, log file, and position with the values you have used in the previous steps."
+msgstr ""
+
+#: ../../optional_installation.rst:213
+# 9a9640cbcab74267a00aefe5b61ca112
+msgid "Then start replication on the slave."
+msgstr ""
+
+#: ../../optional_installation.rst:219
+# a561331155b44e14a5a9540ccfaded76
+msgid "Optionally, open port 3306 on the slave as was done on the master earlier."
+msgstr ""
+
+#: ../../optional_installation.rst:222
+# efdf8223dd9a43a8827dd97444acf8e3
+msgid "This is not required for replication to work. But if you choose not to do this, you will need to do it when failover to the replica occurs."
+msgstr ""
+
+#: ../../optional_installation.rst:228
+# d4acbba0ba9b47bdb60497c2f80cf6cc
+msgid "Failover"
+msgstr ""
+
+#: ../../optional_installation.rst:230
+# 4937feeba9e047e3b9665410e5765ce4
+msgid "This will provide for a replicated database that can be used to implement manual failover for the Management Servers. CloudStack failover from one MySQL instance to another is performed by the administrator. In the event of a database failure you should:"
+msgstr ""
+
+#: ../../optional_installation.rst:235
+# e136a63f11d74984968bb1c32c84670f
+msgid "Stop the Management Servers (via service cloudstack-management stop)."
+msgstr ""
+
+#: ../../optional_installation.rst:237
+# df74922f2b5a44b0820337aecbb8703f
+msgid "Change the replica's configuration to be a master and restart it."
+msgstr ""
+
+#: ../../optional_installation.rst:239
+# 2bc5d7c5cd654d7abc5305542ac56d8d
+msgid "Ensure that the replica's port 3306 is open to the Management Servers."
+msgstr ""
+
+#: ../../optional_installation.rst:242
+# cfeac26dd12942b6a98e7598f0f9b130
+msgid "Make a change so that the Management Server uses the new database. The simplest process here is to put the IP address of the new database server into each Management Server's /etc/cloudstack/management/db.properties."
+msgstr ""
+
+#: ../../optional_installation.rst:247
+# b5e8464f1e5f4490bdd8efe683735901
+msgid "Restart the Management Servers:"
+msgstr ""
+
+#: ../../optional_installation.rst:255
+# f83e0c3d61fd423a8768c362173078a1
+msgid "Amazon Web Services Interface"
+msgstr ""
+
+#: ../../optional_installation.rst:258
+# 008a243332da45c681fc9c7358b19aae
+msgid "Amazon Web Services Compatible Interface"
+msgstr ""
+
+#: ../../optional_installation.rst:260
+# a82b49319a584d2bbb2ab85b707dd73e
+msgid "CloudStack can translate Amazon Web Services (AWS) API calls to native CloudStack API calls so that users can continue using existing AWS-compatible tools. This translation service runs as a separate web application in the same tomcat server as the management server of CloudStack, listening on a different port. The Amazon Web Services (AWS) compatible interface provides the EC2 SOAP and Query APIs as well as the S3 REST API."
+msgstr ""
+
+#: ../../optional_installation.rst:269
+# 4099f5d8b5b2469097a3c637c1f56b3b
+msgid "This service was previously enabled by separate software called CloudBridge. It is now fully integrated with the CloudStack management server."
+msgstr ""
+
+#: ../../optional_installation.rst:273
+# ba7cd83fde90433795ad9f0983796c7d
+msgid "The compatible interface for the EC2 Query API and the S3 API are Work In Progress. The S3 compatible API offers a way to store data on the management server file system, it is not an implementation of the S3 backend."
+msgstr ""
+
+#: ../../optional_installation.rst:278
+# 3d6cb62472054f53823064cd7522b0b1
+msgid "Limitations"
+msgstr ""
+
+#: ../../optional_installation.rst:280
+# bd1989968b7a48d08d2c3e9cbe00b826
+msgid "Supported only in zones that use basic networking."
+msgstr ""
+
+#: ../../optional_installation.rst:282
+# af22d4d3ba014e95bbcc09a2a5f63ded
+msgid "Available in fresh installations of CloudStack. Not available through upgrade of previous versions."
+msgstr ""
+
+#: ../../optional_installation.rst:285
+# 89189121ce884387b3055b803759c936
+msgid "Features such as Elastic IP (EIP) and Elastic Load Balancing (ELB) are only available in an infrastructure with a Citrix NetScaler device. Users accessing a Zone with a NetScaler device will need to use a NetScaler-enabled network offering (DefaultSharedNetscalerEIP and ELBNetworkOffering)."
+msgstr ""
+
+#: ../../optional_installation.rst:293
+# 4063d813433749b7a6f88f762f812757
+msgid "Supported API Version"
+msgstr ""
+
+#: ../../optional_installation.rst:295
+# 0c8d9ebd1d4249df82a11f029752c2fe
+msgid "The EC2 interface complies with Amazon's WDSL version dated November 15, 2010, available at `http://ec2.amazonaws.com/doc/2010-11-15/ <http://ec2.amazonaws.com/doc/2010-11-15/>`_."
+msgstr ""
+
+#: ../../optional_installation.rst:299
+# 06a91ca4b45c4bcd8f0dffb5a713eee1
+msgid "The interface is compatible with the EC2 command-line tools *EC2 tools v. 1.3.6230*, which can be downloaded at `http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip <http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip>`_."
+msgstr ""
+
+#: ../../optional_installation.rst:304
+# 345691ffdcae4dde88f8e11a0125cbf2
+msgid "Work is underway to support a more recent version of the EC2 API"
+msgstr ""
+
+#: ../../optional_installation.rst:308
+# a79e19b1e2534aae9054a646ab2ca09e
+msgid "Enabling the EC2 and S3 Compatible Interface"
+msgstr ""
+
+#: ../../optional_installation.rst:310
+# f6d3211b707447119b97c69471f54d9d
+msgid "The software that provides AWS API compatibility is installed along with CloudStack. You must enable the services and perform some setup steps prior to using it."
+msgstr ""
+
+#: ../../optional_installation.rst:314
+# bce3d6459eb347829649d2c27d636958
+msgid "Set the global configuration parameters for each service to true. See `*Setting Global Configuration Parameters* <configuration.html#setting-global-configuration-parameters>`_."
+msgstr ""
+
+#: ../../optional_installation.rst:318
+# 0dc2fe0c2c8445b1924fc574a1c87694
+msgid "Create a set of CloudStack service offerings with names that match the Amazon service offerings. You can do this through the CloudStack UI as described in the Administration Guide."
+msgstr ""
+
+#: ../../optional_installation.rst:323
+# aa33d4563eec476a845286e29c8e36b0
+msgid "Be sure you have included the Amazon default service offering, m1.small. As well as any EC2 instance types that you will use."
+msgstr ""
+
+#: ../../optional_installation.rst:326
+# 096209e388b6481291f88c61c491b459
+msgid "If you did not already do so when you set the configuration parameter in step 1, restart the Management Server."
+msgstr ""
+
+#: ../../optional_installation.rst:333
+# a77f0d9cbc2f47c4b4cc66b9e4019fee
+msgid "The following sections provides details to perform these steps"
+msgstr ""
+
+#: ../../optional_installation.rst:337
+# a08859b425eb4de583eddfd055ab1ff4
+msgid "Enabling the Services"
+msgstr ""
+
+#: ../../optional_installation.rst:339
+# 272886039ce1406aaa5cd62c9d6ef1d1
+msgid "To enable the EC2 and S3 compatible services you need to set the configuration variables *enable.ec2.api* and *enable.s3.api* to true. You do not have to enable both at the same time. Enable the ones you need. This can be done via the CloudStack GUI by going in *Global Settings* or via the API."
+msgstr ""
+
+#: ../../optional_installation.rst:345
+# 7dfc438f80884b509b780ac9f22a60d7
+msgid "The snapshot below shows you how to use the GUI to enable these services"
+msgstr ""
+
+#: ../../optional_installation.rst:347
+# 3f1255dfd7c74bbbaa364bd72050b328
+msgid "|Use the GUI to set the configuration variable to true|"
+msgstr ""
+
+#: ../../optional_installation.rst:349
+# 8039aca5d5ee48928e08b48a66702245
+msgid "Using the CloudStack API, the easiest is to use the so-called integration port on which you can make unauthenticated calls. In Global Settings set the port to 8096 and subsequently call the *updateConfiguration* method. The following urls shows you how:"
+msgstr ""
+
+#: ../../optional_installation.rst:359
+# 5bbf6319aa584463b00106945d4c6402
+msgid "Once you have enabled the services, restart the server."
+msgstr ""
+
+#: ../../optional_installation.rst:363
+# 83493cf546644c91bdf4168470b7038b
+msgid "Creating EC2 Compatible Service Offerings"
+msgstr ""
+
+#: ../../optional_installation.rst:365
+# 45d0f4507650452687adcaf0021cf2ec
+msgid "You will also need to define compute service offerings with names compatible with the `Amazon EC2 instance types <http://aws.amazon.com/ec2/instance-types/>`_ API names (e.g m1.small,m1.large). This can be done via the CloudStack GUI. Go under *Service Offerings* select *Compute offering* and either create a new compute offering or modify an existing one, ensuring that the name matches an EC2 instance type API name. The snapshot below shows you how:"
+msgstr ""
+
+#: ../../optional_installation.rst:373
+# 231dd56b51ee4df98f4d20605e495f73
+msgid "|Use the GUI to set the name of a compute service offering to an EC2 instance type API name.|"
+msgstr ""
+
+#: ../../optional_installation.rst:378
+# a4602805499146c2b996ff100acf74ea
+msgid "Modifying the AWS API Port"
+msgstr ""
+
+#: ../../optional_installation.rst:381
+# dd4eaeaa8fda437b849ad593f49f45b7
+msgid "(Optional) The AWS API listens for requests on port 7080. If you prefer AWS API to listen on another port, you can change it as follows:"
+msgstr ""
+
+#: ../../optional_installation.rst:384
+# 7f4e4df38c7a4fc3a6fa8c6b2e2d3e64
+msgid "Edit the files ``/etc/cloudstack/management/server.xml``, ``/etc/cloudstack/management/server-nonssl.xml``, and ``/etc/cloudstack/management/server-ssl.xml``."
+msgstr ""
+
+#: ../../optional_installation.rst:388
+# b340ed2079834e53a63d34250cd825ca
+msgid "In each file, find the tag <Service name=\"Catalina7080\">. Under this tag, locate <Connector executor=\"tomcatThreadPool-internal\" port= ....<."
+msgstr ""
+
+#: ../../optional_installation.rst:390
+# bccb37ab25b94f20811fce519e8fdc29
+msgid "Change the port to whatever port you want to use, then save the files."
+msgstr ""
+
+#: ../../optional_installation.rst:392
+# 92df4f254d294e9da84bf38af22b9a91
+msgid "Restart the Management Server."
+msgstr ""
+
+#: ../../optional_installation.rst:394
+# e51c7d34c3924425b10a99d64cdfe879
+msgid "If you re-install CloudStack, you will have to re-enable the services and if need be update the port."
+msgstr ""
+
+#: ../../optional_installation.rst:399
+# 88a6174139da4c4186ae97897056f0a3
+msgid "AWS API User Setup"
+msgstr ""
+
+#: ../../optional_installation.rst:401
+# 57e3c2571da94b80b822e13550aadc22
+msgid "In general, users need not be aware that they are using a translation service provided by CloudStack. They only need to send AWS API calls to CloudStack's endpoint, and it will translate the calls to the native CloudStack API. Users of the Amazon EC2 compatible interface will be able to keep their existing EC2 tools and scripts and use them with their CloudStack deployment, by specifying the endpoint of the management server and using the proper user credentials. In order to do this, each user must perform the following configuration steps:"
+msgstr ""
+
+#: ../../optional_installation.rst:410
+# a19dd6485e8648de8c442534a81268dc
+msgid "Generate user credentials."
+msgstr ""
+
+#: ../../optional_installation.rst:412
+# 2dbe2a8f81614418bdfbc25616fdc428
+msgid "Register with the service."
+msgstr ""
+
+#: ../../optional_installation.rst:414
+# badf72cf4c6149aaaab82e77ffd82b50
+msgid "For convenience, set up environment variables for the EC2 SOAP command-line tools."
+msgstr ""
+
+#: ../../optional_installation.rst:419
+# 3b64483d04ad424ea3f6276c6f36ff1f
+msgid "AWS API Command-Line Tools Setup"
+msgstr ""
+
+#: ../../optional_installation.rst:421
+# 8d508d5a0ad04931b410fe2c700ee584
+msgid "To use the EC2 command-line tools, the user must perform these steps:"
+msgstr ""
+
+#: ../../optional_installation.rst:423
+# b99567ebf9e347608ef9aebcd5b73e11
+msgid "Be sure you have the right version of EC2 Tools. The supported version is available at `http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip <http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip>`_."
+msgstr ""
+
+#: ../../optional_installation.rst:427
+# 6dbc6273aacd474d853e027aedae2cb0
+msgid "Set up the EC2 environment variables. This can be done every time you use the service or you can set them up in the proper shell profile. Replace the endpoint (i.e EC2\\_URL) with the proper address of your CloudStack management server and port. In a bash shell do the following."
+msgstr ""
+
+#: ../../optional_installation.rst:442
+# eb3c3fbe05b346ecb25287a99bbb24e0
+msgid "Using Timeouts to Ensure AWS API Command Completion"
+msgstr ""
+
+#: ../../optional_installation.rst:444
+# 12f582bc55294c8babfc63927d334cda
+msgid "The Amazon EC2 command-line tools have a default connection timeout. When used with CloudStack, a longer timeout might be needed for some commands. If you find that commands are not completing due to timeouts, you can specify a custom timeouts. You can add the following optional command-line parameters to any CloudStack-supported EC2 command:"
+msgstr ""
+
+#: ../../optional_installation.rst:450
+# c844003dee644c4f84e195c83fcf9c54
+msgid "Specifies a connection timeout (in seconds)"
+msgstr ""
+
+#: ../../optional_installation.rst:456
+# 02f0dce26c234519b8a54daa305acdd9
+msgid "Specifies a request timeout (in seconds)"
+msgstr ""
+
+#: ../../optional_installation.rst:462
+# 824f8a4bf59c42e8af3125231422fb72
+msgid "Example:"
+msgstr ""
+
+#: ../../optional_installation.rst:469
+# 402a686dcd0c4432b11580f6044c89fb
+msgid "The timeouts optional arguments are not specific to CloudStack."
+msgstr ""
+
+#: ../../optional_installation.rst:473
+# b0e9ee13c44541ce8507ebc579484bf9
+msgid "Supported AWS API Calls"
+msgstr ""
+
+#: ../../optional_installation.rst:475
+# 8795d7b0a5a84d7d9c5c6c7d9457fa31
+msgid "The following Amazon EC2 commands are supported by CloudStack when the AWS API compatible interface is enabled. For a few commands, there are differences between the CloudStack and Amazon EC2 versions, and these differences are noted. The underlying SOAP call for each command is also given, for those who have built tools using those calls."
+msgstr ""
+
+#: ../../optional_installation.rst:481
+# 02d07033ab224197b16e0e3416784ad8
+msgid "Table 1. Elastic IP API mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:484
+#: ../../optional_installation.rst:502
+#: ../../optional_installation.rst:512
+#: ../../optional_installation.rst:528
+#: ../../optional_installation.rst:542
+#: ../../optional_installation.rst:562
+#: ../../optional_installation.rst:572
+#: ../../optional_installation.rst:588
+#: ../../optional_installation.rst:598
+#: ../../optional_installation.rst:616
+#: ../../optional_installation.rst:630
+# e6d8f396041142b2893f507bc4dcbdff
+# 1241bfdc842c4717953802b0343a7291
+# 140c555e4743444ea4c85e764c7cf200
+# b98e30783b7b49e49f7dfd0bf4770bdd
+# 8c84cf9210be42098217140c926d9e4a
+# a09d7172c4ae407bb590e916d8c4583c
+# 016288e54f0746638338d5e4c36ae2d1
+# 6d407b5c8ce4411ab3ca03fe1dfb3f73
+# 58581d2ced5a498f8d9b64e134879fdb
+# 1637dec2b0694af187c5a578dbb36e2f
+# d6d86c36942a4fe3a9719c3bc53d9733
+msgid "EC2 command"
+msgstr ""
+
+#: ../../optional_installation.rst:484
+#: ../../optional_installation.rst:502
+#: ../../optional_installation.rst:512
+#: ../../optional_installation.rst:528
+#: ../../optional_installation.rst:542
+#: ../../optional_installation.rst:562
+#: ../../optional_installation.rst:572
+#: ../../optional_installation.rst:588
+#: ../../optional_installation.rst:598
+#: ../../optional_installation.rst:616
+#: ../../optional_installation.rst:630
+# f329b710ee004161aac04e003d4959e7
+# 3e2771dd49b84cac9a0456674bf6122a
+# f34bafa2d5654005a150adfe0c7b5a79
+# eda190902fda413bb85d43274f6e2698
+# 805e6d29c03d44f18162de41e6340a9b
+# cdf70240f9214f8bbb9126245821d4d7
+# d5c143a174a7449e9fe5effe961a58c1
+# 288ec94c5e4c4da09b6ec91d77ff7068
+# 5400f9aed9dd4a5b83540eee1ec381a1
+# b25d524012d74bfb958f904b19d4420b
+# ea762702b2c9432b80571e0877d76f13
+msgid "SOAP call"
+msgstr ""
+
+#: ../../optional_installation.rst:484
+#: ../../optional_installation.rst:502
+#: ../../optional_installation.rst:512
+#: ../../optional_installation.rst:528
+#: ../../optional_installation.rst:542
+#: ../../optional_installation.rst:562
+#: ../../optional_installation.rst:572
+#: ../../optional_installation.rst:588
+#: ../../optional_installation.rst:598
+#: ../../optional_installation.rst:616
+#: ../../optional_installation.rst:630
+# f99e71d5f94c43b08513a8b56330f4f6
+# 31ac1fa35a2c4abea464bcafc4fc181d
+# 4ff71078fae04f59ab528c8884e872b3
+# 12f8a717b46d4c6b97790eb810851aec
+# 5483f26fc9de4d429006a340fb2c2e3b
+# 487160d7dd2e45e784307da387c69f4b
+# 02684a5cd9ea43f6b9306eca1bdff457
+# b498a15517fb40569a500034444bd875
+# 26f9780627c14d46a9c2da606992d101
+# 4309dd0aa08d4453a2676af2b2baf8ea
+# d0cf4d9b46e04a2093aaa063d28b3944
+msgid "CloudStack API call"
+msgstr ""
+
+#: ../../optional_installation.rst:486
+# 871494b532d14db482bf30a6ee1e728b
+msgid "ec2-allocate-address"
+msgstr ""
+
+#: ../../optional_installation.rst:486
+# a2b89f3a70cb42d1aefe00dff62df484
+msgid "AllocateAddress"
+msgstr ""
+
+#: ../../optional_installation.rst:486
+# b2a6cef1e5f64c7391495daee341c687
+msgid "associateIpAddress"
+msgstr ""
+
+#: ../../optional_installation.rst:488
+# 57f93d082fb843a0bc0e05a317ca1c46
+msgid "ec2-associate-address"
+msgstr ""
+
+#: ../../optional_installation.rst:488
+# 0e3db736706747f783673f0e1bf54a9c
+msgid "AssociateAddress"
+msgstr ""
+
+#: ../../optional_installation.rst:488
+# e1f6f588aaab43b8972851cde4f886be
+msgid "enableStaticNat"
+msgstr ""
+
+#: ../../optional_installation.rst:490
+# 480cffbfdaf942dea2c51f1a89ad8f11
+msgid "ec2-describe-addresses"
+msgstr ""
+
+#: ../../optional_installation.rst:490
+# 06d41125c2ba4b32a531c4153a1d60ee
+msgid "DescribeAddresses"
+msgstr ""
+
+#: ../../optional_installation.rst:490
+# 489c67ac13ab44d6860865e68e4f22a1
+msgid "listPublicIpAddresses"
+msgstr ""
+
+#: ../../optional_installation.rst:492
+# 99f32f9d8ed945cda5d6dabb94b90123
+msgid "ec2-diassociate-address"
+msgstr ""
+
+#: ../../optional_installation.rst:492
+# d3412e0e645f4dc48a2d49b2cc7cc110
+msgid "DisassociateAddress"
+msgstr ""
+
+#: ../../optional_installation.rst:492
+# 76ba5d2d843247f0b9d520075b1180c4
+msgid "disableStaticNat"
+msgstr ""
+
+#: ../../optional_installation.rst:494
+# 9dd57597d99147a99d7a6a1ba653ee54
+msgid "ec2-release-address"
+msgstr ""
+
+#: ../../optional_installation.rst:494
+# a821f696dcca41e69caf9ed34dd5fe08
+msgid "ReleaseAddress"
+msgstr ""
+
+#: ../../optional_installation.rst:494
+# 9dc55b45ecfc4df6870608a6e45e06cb
+msgid "disassociateIpAddress"
+msgstr ""
+
+#: ../../optional_installation.rst:499
+# 4db130ee1b9b47e0901be48dcf4c8112
+msgid "Table 2. Availability Zone API mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:504
+# c5d48090cfa34e38bf20cfb233425898
+msgid "ec2-describe-availability-zones"
+msgstr ""
+
+#: ../../optional_installation.rst:504
+# f86cd21880794cb6b0a7e5b82474220e
+msgid "DescribeAvailabilityZones"
+msgstr ""
+
+#: ../../optional_installation.rst:504
+# ccf5d831cb5048d28034c308da6a97d0
+msgid "listZones"
+msgstr ""
+
+#: ../../optional_installation.rst:509
+# 638f0f43aae0473bae7eafa0d0058383
+msgid "Table 3. Images API mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:514
+# 508b851331d0421dbe112662c609e072
+msgid "ec2-create-image"
+msgstr ""
+
+#: ../../optional_installation.rst:514
+# c4bb3a1d4dce43febc5d85e29a2f071e
+msgid "CreateImage"
+msgstr ""
+
+#: ../../optional_installation.rst:514
+# df1c02038aff4e239a1a05490cabaa2b
+msgid "createTemplate"
+msgstr ""
+
+#: ../../optional_installation.rst:516
+# eea3a24b84074b7bab9177b0f213f89a
+msgid "ec2-deregister"
+msgstr ""
+
+#: ../../optional_installation.rst:516
+# 92dc634143e142c2a068ca963ce3c02a
+msgid "DeregisterImage"
+msgstr ""
+
+#: ../../optional_installation.rst:516
+# eaacea2a72884286b0c663b9e8f0ba20
+msgid "DeleteTemplate"
+msgstr ""
+
+#: ../../optional_installation.rst:518
+# a0153e8b6a0e4465ae12d78be847d550
+msgid "ec2-describe-images"
+msgstr ""
+
+#: ../../optional_installation.rst:518
+# bf82b734bc3f49a3860327460324906e
+msgid "DescribeImages"
+msgstr ""
+
+#: ../../optional_installation.rst:518
+# df9b8d3e1bc649759cf66ddab8ec4f9a
+msgid "listTemplates"
+msgstr ""
+
+#: ../../optional_installation.rst:520
+# af125d1fd7984bf7b33a61009f9f053a
+msgid "ec2-register"
+msgstr ""
+
+#: ../../optional_installation.rst:520
+# 08b7fb7fa77b4fe990717d8c4781a071
+msgid "RegisterImage"
+msgstr ""
+
+#: ../../optional_installation.rst:520
+# 15a7a3101cae420f9a177d36e8a49755
+msgid "registerTemplate"
+msgstr ""
+
+#: ../../optional_installation.rst:525
+# 95f8126f5bde40e7a03ffe5b31cf0d0a
+msgid "Table 4. Image Attributes API mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:530
+# 61ba87df119f43d1ab6e755b2062c70d
+msgid "ec2-describe-image-attribute"
+msgstr ""
+
+#: ../../optional_installation.rst:530
+# 626ce97b2fc84dad9717f1b9f026d026
+msgid "DescribeImageAttribute"
+msgstr ""
+
+#: ../../optional_installation.rst:530
+# 47efdf23036f4569aebc625fd98610c9
+msgid "listTemplatePermissions"
+msgstr ""
+
+#: ../../optional_installation.rst:532
+# 5b76481a1e664c7a80ad64ebc0f2f6c8
+msgid "ec2-modify-image-attribute"
+msgstr ""
+
+#: ../../optional_installation.rst:532
+# c43e186a96384512bd1de4080e7c3c3e
+msgid "ModifyImageAttribute"
+msgstr ""
+
+#: ../../optional_installation.rst:532
+#: ../../optional_installation.rst:534
+# 6772c414652f430385bbd58d7f0330d3
+# 2e19a602fa3a416786d47b835140a477
+msgid "updateTemplatePermissions"
+msgstr ""
+
+#: ../../optional_installation.rst:534
+# bb056d700ca443ea8ac3c41a96c9ca93
+msgid "ec2-reset-image-attribute"
+msgstr ""
+
+#: ../../optional_installation.rst:534
+# 1c5e811d7b4f4b0b97c8794475b0dfe2
+msgid "ResetImageAttribute"
+msgstr ""
+
+#: ../../optional_installation.rst:539
+# 5e99e23dd1d74fdea2908ff0c784644c
+msgid "Table 5. Instances API mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:544
+# 94131fa6fee041b9bb87ed41c1740015
+msgid "ec2-describe-instances"
+msgstr ""
+
+#: ../../optional_installation.rst:544
+# bc77fd6401e34b03808bae2a03dce722
+msgid "DescribeInstances"
+msgstr ""
+
+#: ../../optional_installation.rst:544
+#: ../../optional_installation.rst:564
+# ddd839a8bffb4e9f959c84f328993206
+# 80dab2b652cc4451b7dce841ea4b0c5e
+msgid "listVirtualMachines"
+msgstr ""
+
+#: ../../optional_installation.rst:546
+# f6bbd228de76472786cde350a52afbb0
+msgid "ec2-run-instances"
+msgstr ""
+
+#: ../../optional_installation.rst:546
+# d8f04cea46714aaea1e22767c6045ce1
+msgid "RunInstances"
+msgstr ""
+
+#: ../../optional_installation.rst:546
+# 16bf652c09f14df3bf1f5a28d0be3085
+msgid "deployVirtualMachine"
+msgstr ""
+
+#: ../../optional_installation.rst:548
+# 73c83571850b4fedb95bfce13056d186
+msgid "ec2-reboot-instances"
+msgstr ""
+
+#: ../../optional_installation.rst:548
+# 3f34ad1daf384d3ba3da8b9ff3750ca0
+msgid "RebootInstances"
+msgstr ""
+
+#: ../../optional_installation.rst:548
+# 745cf110441b4dd3b97b9c861365acb2
+msgid "rebootVirtualMachine"
+msgstr ""
+
+#: ../../optional_installation.rst:550
+# 5e8a67083eb74e249170d88c845fa736
+msgid "ec2-start-instances"
+msgstr ""
+
+#: ../../optional_installation.rst:550
+# f2001b78bf654274b213a674f8432d85
+msgid "StartInstances"
+msgstr ""
+
+#: ../../optional_installation.rst:550
+# be06c051916b4c919ed831ab7627d632
+msgid "startVirtualMachine"
+msgstr ""
+
+#: ../../optional_installation.rst:552
+# db6d6153348c4b4f9c934ad1b4cef7e1
+msgid "ec2-stop-instances"
+msgstr ""
+
+#: ../../optional_installation.rst:552
+# 0936209ce89d4a7d80fefed7e7e68bbb
+msgid "StopInstances"
+msgstr ""
+
+#: ../../optional_installation.rst:552
+# aed253e923104237b8f072cb7149f18b
+msgid "stopVirtualMachine"
+msgstr ""
+
+#: ../../optional_installation.rst:554
+# df41eecc274047d7b48459b161966294
+msgid "ec2-terminate-instances"
+msgstr ""
+
+#: ../../optional_installation.rst:554
+# 11abb0a8eda24cf1928e7100664bd7ea
+msgid "TerminateInstances"
+msgstr ""
+
+#: ../../optional_installation.rst:554
+# 8036634c384c48038d0abdc470ffcc4e
+msgid "destroyVirtualMachine"
+msgstr ""
+
+#: ../../optional_installation.rst:559
+# 80edc0db597c4994ac9e79c8b81cc8b5
+msgid "Table 6. Instance Attributes Mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:564
+# 0f4f20fc51ce489ab1980676caf53257
+msgid "ec2-describe-instance-attribute"
+msgstr ""
+
+#: ../../optional_installation.rst:564
+# 4884ab07d7a941abbcf65d35f6956ef7
+msgid "DescribeInstanceAttribute"
+msgstr ""
+
+#: ../../optional_installation.rst:569
+# 3535a243b6944759833817d5812fe907
+msgid "Table 7. Keys Pairs Mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:574
+# a3c003668c19497192a168826e6dd752
+msgid "ec2-add-keypair"
+msgstr ""
+
+#: ../../optional_installation.rst:574
+# fc757057d53e4355b3e39ebde3670cc4
+msgid "CreateKeyPair"
+msgstr ""
+
+#: ../../optional_installation.rst:574
+# 8b21961e21324bfbb5ca8be24c8a33eb
+msgid "createSSHKeyPair"
+msgstr ""
+
+#: ../../optional_installation.rst:576
+# deb02c5e8676453291bbd521ff3bc979
+msgid "ec2-delete-keypair"
+msgstr ""
+
+#: ../../optional_installation.rst:576
+# 4580d729e28940778561e6b64aec68b2
+msgid "DeleteKeyPair"
+msgstr ""
+
+#: ../../optional_installation.rst:576
+# c8fefc1f8ac047f1b825d7069618e3f4
+msgid "deleteSSHKeyPair"
+msgstr ""
+
+#: ../../optional_installation.rst:578
+# fd10ca522a284a17ab0f0772e7eff22c
+msgid "ec2-describe-keypairs"
+msgstr ""
+
+#: ../../optional_installation.rst:578
+# d64506ecf5b94b0fb34a54eb1a533ee9
+msgid "DescribeKeyPairs"
+msgstr ""
+
+#: ../../optional_installation.rst:578
+# 303415d20d3e4881a6441bd09ee7383e
+msgid "listSSHKeyPairs"
+msgstr ""
+
+#: ../../optional_installation.rst:580
+# daa6bca4cda94bb987b8771303321aa0
+msgid "ec2-import-keypair"
+msgstr ""
+
+#: ../../optional_installation.rst:580
+# fcf840900bb646acb715f411c19c1a8c
+msgid "ImportKeyPair"
+msgstr ""
+
+#: ../../optional_installation.rst:580
+# cf7556bc11ad48819c9bc515411fdced
+msgid "registerSSHKeyPair"
+msgstr ""
+
+#: ../../optional_installation.rst:585
+# 27703e9dc9244cd0ad627c2fda749c65
+msgid "Table 8. Passwords API Mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:590
+# 3c333b4280534856a4650d0768a87fe9
+msgid "ec2-get-password"
+msgstr ""
+
+#: ../../optional_installation.rst:590
+# 69df9745e16f4025994bc4a4e7dd8d14
+msgid "GetPasswordData"
+msgstr ""
+
+#: ../../optional_installation.rst:590
+# f1023d3b15164fa781914bc2798f4049
+msgid "getVMPassword"
+msgstr ""
+
+#: ../../optional_installation.rst:595
+# 42d8a55a4cdd4166903ac3f4d0893d34
+msgid "Table 9. Security Groups API Mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:600
+# 9f4ba75822cb44d8a563b7e19dd084cf
+msgid "ec2-authorize"
+msgstr ""
+
+#: ../../optional_installation.rst:600
+# c9b993da1c7344a98757f409d8c43863
+msgid "AuthorizeSecurityGroupIngress"
+msgstr ""
+
+#: ../../optional_installation.rst:600
+# 6700b8b10b56416587800a56a46a321f
+msgid "authorizeSecurityGroupIngress"
+msgstr ""
+
+#: ../../optional_installation.rst:602
+# 08a42b691fe745c4886feccc73ce1adf
+msgid "ec2-add-group"
+msgstr ""
+
+#: ../../optional_installation.rst:602
+# 7264f4cf327e4f1ea917878644005831
+msgid "CreateSecurityGroup"
+msgstr ""
+
+#: ../../optional_installation.rst:602
+# 91777fbf4341415a9685b03a9640482f
+msgid "createSecurityGroup"
+msgstr ""
+
+#: ../../optional_installation.rst:604
+# c3cf61e1d10d4f5989bfd2692699ea35
+msgid "ec2-delete-group"
+msgstr ""
+
+#: ../../optional_installation.rst:604
+# efab4d6e1d1244859fe7cbe9c4f3886e
+msgid "DeleteSecurityGroup"
+msgstr ""
+
+#: ../../optional_installation.rst:604
+# 90d9bc2bd0bc4e01a3c09d3611032dbc
+msgid "deleteSecurityGroup"
+msgstr ""
+
+#: ../../optional_installation.rst:606
+# c72ab39125e241e18dd69018eb4943d2
+msgid "ec2-describe-group"
+msgstr ""
+
+#: ../../optional_installation.rst:606
+# ebf978cf9ead4b63b1e55ca99411cde8
+msgid "DescribeSecurityGroups"
+msgstr ""
+
+#: ../../optional_installation.rst:606
+# ff1b0d61071b4256bbb3c44a6e3db98f
+msgid "listSecurityGroups"
+msgstr ""
+
+#: ../../optional_installation.rst:608
+# c0c1d7836b1247c98a6edd27afe1f758
+msgid "ec2-revoke"
+msgstr ""
+
+#: ../../optional_installation.rst:608
+# e25205aeab6a4a4cb7aed5e9d3cef347
+msgid "RevokeSecurityGroupIngress"
+msgstr ""
+
+#: ../../optional_installation.rst:608
+# 5e02eadf7e81443da07167e7ce261298
+msgid "revokeSecurityGroupIngress"
+msgstr ""
+
+#: ../../optional_installation.rst:613
+# fa94f34dde294a2682b384cbe8ecd23c
+msgid "Table 10. Snapshots API Mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:618
+# ee680af94d4946678427401c45778d24
+msgid "ec2-create-snapshot"
+msgstr ""
+
+#: ../../optional_installation.rst:618
+# 79c2f04343b14b819176d6f4dea40c55
+msgid "CreateSnapshot"
+msgstr ""
+
+#: ../../optional_installation.rst:618
+# 94845f5ef1f54d3c968868fcf99ba1f8
+msgid "createSnapshot"
+msgstr ""
+
+#: ../../optional_installation.rst:620
+# 4987b9a0b58f41bab2d4c04e9e4e5a6e
+msgid "ec2-delete-snapshot"
+msgstr ""
+
+#: ../../optional_installation.rst:620
+# ee365f5503714848886b5594642d29bb
+msgid "DeleteSnapshot"
+msgstr ""
+
+#: ../../optional_installation.rst:620
+# b71dca67624b46f18e4aeba5daf8d3a2
+msgid "deleteSnapshot"
+msgstr ""
+
+#: ../../optional_installation.rst:622
+# 59cca02c7be644da8322ba049074d97f
+msgid "ec2-describe-snapshots"
+msgstr ""
+
+#: ../../optional_installation.rst:622
+# 0aab43a7f50d4a74bdb336efb5f532f3
+msgid "DescribeSnapshots"
+msgstr ""
+
+#: ../../optional_installation.rst:622
+# 36579270e4464f01a3448e680a5a85e2
+msgid "listSnapshots"
+msgstr ""
+
+#: ../../optional_installation.rst:627
+# 5e706e7dce774791a61ca1100cb16fde
+msgid "Table 11. Volumes API Mapping"
+msgstr ""
+
+#: ../../optional_installation.rst:632
+# 97db47b0a0ba4160850802f8a1f1bb90
+msgid "ec2-attach-volume"
+msgstr ""
+
+#: ../../optional_installation.rst:632
+# 3b10700084ac4bf3b26665a5d3ebf318
+msgid "AttachVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:632
+# 5c9f9723721245c8b718bd54cbaece22
+msgid "attachVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:634
+# 72e155b316de4a22a0dc04db2446a000
+msgid "ec2-create-volume"
+msgstr ""
+
+#: ../../optional_installation.rst:634
+# 9104debce3a241239dd215d4e3f2d3be
+msgid "CreateVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:634
+# 556262b0cecd47f2911e5c1c52ce4cd1
+msgid "createVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:636
+# 74ac980aa1474328a197b3d0838ed348
+msgid "ec2-delete-volume"
+msgstr ""
+
+#: ../../optional_installation.rst:636
+# 4ea664000a214abaa22eef86ff955923
+msgid "DeleteVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:636
+# 3292da55a3b246a394511a8f8690f8f8
+msgid "deleteVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:638
+# deceab702d224f7abc2f807131a49f98
+msgid "ec2-describe-volume"
+msgstr ""
+
+#: ../../optional_installation.rst:638
+# 0c209718005c4d14979e9242eef22116
+msgid "DescribeVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:638
+# d0d300c170964f3baef0aff758b9ab73
+msgid "listVolumes"
+msgstr ""
+
+#: ../../optional_installation.rst:640
+# 504e7f75651c40049e25fccbe5fa029f
+msgid "ec2-detach-volume"
+msgstr ""
+
+#: ../../optional_installation.rst:640
+# f9fe5637c3564d93b15edc5988690000
+msgid "DetachVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:640
+# d2d951565edd4f31907d8b2c2f26fd6b
+msgid "detachVolume"
+msgstr ""
+
+#: ../../optional_installation.rst:647
+# 126ae67bf33f461a842b80e8582ee1ad
+msgid "Examples"
+msgstr ""
+
+#: ../../optional_installation.rst:649
+# 13a09d4f957645a1bd8fc9df7c217544
+msgid "There are many tools available to interface with a AWS compatible API. In this section we provide a few examples that users of CloudStack can build upon."
+msgstr ""
+
+#: ../../optional_installation.rst:655
+# fccb92622df74eea927da84d007d391b
+msgid "Boto Examples"
+msgstr ""
+
+#: ../../optional_installation.rst:657
+# 4831cf3fedd840a7b813bc1622eeb277
+msgid "Boto is one of them. It is a Python package available at https://github.com/boto/boto. In this section we provide two examples of Python scripts that use Boto and have been tested with the CloudStack AWS API Interface."
+msgstr ""
+
+#: ../../optional_installation.rst:662
+# e785f67f1fed40108c89dcea285aebea
+msgid "First is an EC2 example. Replace the Access and Secret Keys with your own and update the endpoint."
+msgstr ""
+
+#: ../../optional_installation.rst:665
+# 90ec7328d8c4425ea37b7739fccb8bdb
+msgid "Example 1. An EC2 Boto example"
+msgstr ""
+
+#: ../../optional_installation.rst:703
+# 164cdb8278ff484c80d1a4d08b029bdd
+msgid "Second is an S3 example. The S3 interface in CloudStack is obsolete. If you need an S3 interface you should look at systems like RiakCS, Ceph or GlusterFS. This example is here for completeness and can be adapted to other S3 endpoint."
+msgstr ""
+
+#: ../../optional_installation.rst:705
+# 1bb508e180ae42d19e41fd5eeefcc9f8
+msgid "Example 2. An S3 Boto Example"
+msgstr ""
+
diff --git a/source/installguide/locale/pot/qig.pot b/source/installguide/locale/pot/qig.pot
new file mode 100644
index 0000000..d38faa0
--- /dev/null
+++ b/source/installguide/locale/pot/qig.pot
@@ -0,0 +1,682 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../qig.rst:18
+# 6cd8b0759d274663bfffb589061f6f52
+msgid "Quick Installation Guide for CentOS"
+msgstr ""
+
+#: ../../qig.rst:21
+# 9be60313b8f24a13978f899e18120244
+msgid "Overview"
+msgstr ""
+
+#: ../../qig.rst:24
+# bb54b96eceb4444fa03567f9f31a1368
+msgid "What exactly are we building?"
+msgstr ""
+
+#: ../../qig.rst:26
+# d07669bf21f74381a55f977c98d059e5
+msgid "Infrastructure-as-a-Service (IaaS) clouds can be a complex thing to build, and by definition they have a plethora of options, which often lead to confusion for even experienced admins who are newcomers to building cloud platforms. The goal for this runbook is to provide a straightforward set of instructions to get you up and running with CloudStack with a minimum amount of trouble."
+msgstr ""
+
+#: ../../qig.rst:34
+# 0d4c4b0427014885a465573bca862560
+msgid "High level overview of the process"
+msgstr ""
+
+#: ../../qig.rst:36
+# fe3355f1acbd41399f2a663c90198e9d
+msgid "This runbook will focus on building a CloudStack cloud using KVM with CentOS 6.4 with NFS storage on a flat layer-2 network utilizing layer-3 network isolation (aka Security Groups), and doing it all on a single piece of hardware."
+msgstr ""
+
+#: ../../qig.rst:41
+# 121007f51b094c8aaeac5c49937a5e62
+msgid "KVM, or Kernel-based Virtual Machine is a virtualization technology for the Linux kernel. KVM supports native virtualization atop processors with hardware virtualization extensions."
+msgstr ""
+
+#: ../../qig.rst:45
+# 0e87db8720ee41cfac5448651b99b134
+msgid "Security Groups act as distributed firewalls that control access to a group of virtual machines."
+msgstr ""
+
+#: ../../qig.rst:50
+#: ../../qig.rst:441
+# 605246954ba64e77b704db1e41f70958
+# b19d4cd5e52648039e330c62094e1b90
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../qig.rst:52
+# 9c888fde9935462b91316870b5352356
+msgid "To complete this runbook you'll need the following items:"
+msgstr ""
+
+#: ../../qig.rst:54
+# 7398c338e13940178c516024cdb7624e
+msgid "At least one computer which supports hardware virtualization."
+msgstr ""
+
+#: ../../qig.rst:56
+# 7577f66c21704f93b482ece2df1e02c8
+msgid "The `CentOS 6.4 x86_64 minimal install CD <http://mirrors.kernel.org/centos/6.4/isos/x86_64/CentOS-6.4-x86_64-minimal.iso>`_"
+msgstr ""
+
+#: ../../qig.rst:59
+# 0be94f9998b1434b9a98e5d2eb09a094
+msgid "A /24 network with the gateway being at xxx.xxx.xxx.1, no DHCP should be on this network and none of the computers running CloudStack will have a dynamic address. Again this is done for the sake of simplicity."
+msgstr ""
+
+#: ../../qig.rst:65
+# d42364c803234d79abd4f4e8ef300913
+msgid "Environment"
+msgstr ""
+
+#: ../../qig.rst:67
+# 67d9a987dbb94e83a8686df4283209a6
+msgid "Before you begin , you need to prepare the environment before you install CloudStack. We will go over the steps to prepare now."
+msgstr ""
+
+#: ../../qig.rst:72
+# 744452849b164ae08575b3bbe6199141
+msgid "Operating System"
+msgstr ""
+
+#: ../../qig.rst:74
+# 4365445c8c1c4c36bbee6f9d2b9b0e15
+msgid "Using the CentOS 6.4 x86_64 minimal install ISO, you'll need to install CentOS on your hardware. The defaults will generally be acceptable for this installation."
+msgstr ""
+
+#: ../../qig.rst:78
+# 49109b885f65416db8533ac7b1ad5222
+msgid "Once this installation is complete, you'll want to connect to your freshly installed machine via SSH as the root user. Note that you should not allow root logins in a production environment, so be sure to turn off remote logins once you have finished the installation and configuration."
+msgstr ""
+
+#: ../../qig.rst:87
+# a105d2a14b9645b39773b7f2f43be743
+msgid "Configuring the network"
+msgstr ""
+
+#: ../../qig.rst:89
+# 37ac1900de634e79828d33b848dfbf83
+msgid "By default the network will not come up on your hardware and you will need to configure it to work in your environment. Since we specified that there will be no DHCP server in this environment we will be manually configuring your network interface. We will assume, for the purposes of this exercise, that eth0 is the only network interface that will be connected and used."
+msgstr ""
+
+#: ../../qig.rst:95
+# 1295d8c07ee849fd9b266a0980e0eb03
+msgid "Connecting via the console you should login as root. Check the file /etc/sysconfig/network-scripts/ifcfg-eth0, it will look like this by default:"
+msgstr ""
+
+#: ../../qig.rst:105
+# ffc841b92bbd4994ae1f07ea99b908ac
+msgid "Unfortunately, this configuration will not permit you to connect to the network, and is also unsuitable for our purposes with CloudStack. We want to configure that file so that it specifies the IP address, netmask, etc., as shown in the following example:"
+msgstr ""
+
+#: ../../qig.rst:111
+# feeb899f3fa049019ca4e9cee4cb7d94
+msgid "You should not use the Hardware Address (aka the MAC address) from our example for your configuration. It is network interface specific, so you should keep the address already provided in the HWADDR directive."
+msgstr ""
+
+#: ../../qig.rst:129
+# 39e9cdade6f84cee9efbcac85368b36d
+msgid "IP Addressing - Throughout this document we are assuming that you will have a /24 network for your CloudStack implementation. This can be any RFC 1918 network. However, we are assuming that you will match the machine address that we are using. Thus we may use 172.16.10.2 and because you might be using the 192.168.55.0/24 network you would use 192.168.55.2"
+msgstr ""
+
+#: ../../qig.rst:135
+# 3826ab3ca7e14ea69a7e7083749d4776
+msgid "Now that we have the configuration files properly set up, we need to run a few commands to start up the network:"
+msgstr ""
+
+#: ../../qig.rst:148
+# 7170ae16486348e1940a24d4b4f320bc
+msgid "Hostname"
+msgstr ""
+
+#: ../../qig.rst:150
+# bc70cba9278c435ba8d50ba7f9804861
+msgid "CloudStack requires that the hostname be properly set. If you used the default options in the installation, then your hostname is currently set to localhost.localdomain. To test this we will run:"
+msgstr ""
+
+#: ../../qig.rst:158
+# c0837ecf69a448a6833089b3cb700b74
+msgid "At this point it will likely return:"
+msgstr ""
+
+#: ../../qig.rst:164
+# c0f03d48e4f84cf99a5ae3b5695dd6d4
+msgid "To rectify this situation - we'll set the hostname by editing the /etc/hosts file so that it follows a similar format to this example:"
+msgstr ""
+
+#: ../../qig.rst:173
+# 998941fe58dd4716b4d08c3a0a8b28d7
+msgid "After you've modified that file, go ahead and restart the network using:"
+msgstr ""
+
+#: ../../qig.rst:179
+# d7827b49760a48e696feee0646a10476
+msgid "Now recheck with the hostname --fqdn command and ensure that it returns a FQDN response"
+msgstr ""
+
+#: ../../qig.rst:186
+# 8ef16e261eb24be6bbc94f0183b1ee33
+msgid "SELinux"
+msgstr ""
+
+#: ../../qig.rst:188
+# 24eacbfa30f944b6a49895982406f6ee
+msgid "At the moment, for CloudStack to work properly SELinux must be set to permissive. We want to both configure this for future boots and modify it in the current running system."
+msgstr ""
+
+#: ../../qig.rst:192
+# ba6f0974cd5f4ef896906cfb78819190
+msgid "To configure SELinux to be permissive in the running system we need to run the following command:"
+msgstr ""
+
+#: ../../qig.rst:199
+# 80d187882ef94e018fbc80b3f6cf1657
+msgid "To ensure that it remains in that state we need to configure the file /etc/selinux/config to reflect the permissive state, as shown in this example:"
+msgstr ""
+
+#: ../../qig.rst:219
+# e2dd6bd4d20445af9e40ef1dcfeffc59
+msgid "NTP"
+msgstr ""
+
+#: ../../qig.rst:221
+# 7dcd6b5f047c4747b5663a3ea0a586bb
+msgid "NTP configuration is a necessity for keeping all of the clocks in your cloud servers in sync. However, NTP is not installed by default. So we'll install and and configure NTP at this stage. Installation is accomplished as follows:"
+msgstr ""
+
+#: ../../qig.rst:229
+# dc3f1acb9d75421389f41ab343c99644
+msgid "The actual default configuration is fine for our purposes, so we merely need to enable it and set it to start on boot as follows:"
+msgstr ""
+
+#: ../../qig.rst:241
+# 521e40c294df4b9cb34b11ddbef6c113
+msgid "Configuring the CloudStack Package Repository"
+msgstr ""
+
+#: ../../qig.rst:243
+# b0a49ad7b98149209a251f36c2b42c2e
+msgid "We need to configure the machine to use a CloudStack package repository."
+msgstr ""
+
+#: ../../qig.rst:246
+# ccc1c3b2524242c3b7b2f4646644974f
+msgid "The Apache CloudStack official releases are source code. As such there are no 'official' binaries available. The full installation guide describes how to take the source release and generate RPMs and and yum repository. This guide attempts to keep things as simple as possible, and thus we are using one of the community-provided yum repositories."
+msgstr ""
+
+#: ../../qig.rst:252
+# 839459c6f46e4c4fa3626c7f84a78e14
+msgid "To add the CloudStack repository, create /etc/yum.repos.d/cloudstack.repo and insert the following information."
+msgstr ""
+
+#: ../../qig.rst:265
+# 4a110af8c49c4b398c36065cc45c8f60
+msgid "NFS"
+msgstr ""
+
+#: ../../qig.rst:267
+# 19505af6684e49c794879229d714e4aa
+msgid "Our configuration is going to use NFS for both primary and secondary storage. We are going to go ahead and setup two NFS shares for those purposes. We'll start out by installing nfs-utils."
+msgstr ""
+
+#: ../../qig.rst:275
+# 6cb16ffd970344c3ace837183e3c39ff
+msgid "We now need to configure NFS to serve up two different shares. This is handled comparatively easily in the /etc/exports file. You should ensure that it has the following content:"
+msgstr ""
+
+#: ../../qig.rst:284
+# cc8ef4b76bf64c62b6c5e89b6ee0fcd9
+msgid "You will note that we specified two directories that don't exist (yet) on the system. We'll go ahead and create those directories and set permissions appropriately on them with the following commands:"
+msgstr ""
+
+#: ../../qig.rst:293
+# 518439ba2be945f9a7e3fbab2a21cdbe
+msgid "CentOS 6.x releases use NFSv4 by default. NFSv4 requires that domain setting matches on all clients. In our case, the domain is cloud.priv, so ensure that the domain setting in /etc/idmapd.conf is uncommented and set as follows: Domain = cloud.priv"
+msgstr ""
+
+#: ../../qig.rst:298
+# b485a87031a94a76a3bf754cdb5cefd2
+msgid "Now you'll need uncomment the configuration values in the file /etc/sysconfig/nfs"
+msgstr ""
+
+#: ../../qig.rst:310
+# e876c59eae014aa3baa25c6b7c1401a3
+msgid "Now we need to configure the firewall to permit incoming NFS connections. Edit the file /etc/sysconfig/iptables"
+msgstr ""
+
+#: ../../qig.rst:327
+# d7b296589dc34344af087b4fb44f8a39
+msgid "Now you can restart the iptables service with the following command:"
+msgstr ""
+
+#: ../../qig.rst:333
+# 2174509b3845456db7eab82fa2adba29
+msgid "We now need to configure the nfs service to start on boot and actually start it on the host by executing the following commands:"
+msgstr ""
+
+#: ../../qig.rst:345
+# 3df2c4989e10469ebd9d8e536e5a1d36
+msgid "Management Server Installation"
+msgstr ""
+
+#: ../../qig.rst:347
+# 9a58ef21fdd64508a4a73a7a0a6ca8ab
+msgid "We're going to install the CloudStack management server and surrounding tools."
+msgstr ""
+
+#: ../../qig.rst:351
+# 6ca0e5d18a4f4af287c3a9e04ddadc5d
+msgid "Database Installation and Configuration"
+msgstr ""
+
+#: ../../qig.rst:353
+# 946061f8b1cb4c97b95a950dae96c2e3
+msgid "We'll start with installing MySQL and configuring some options to ensure it runs well with CloudStack."
+msgstr ""
+
+#: ../../qig.rst:356
+# 51eb7503da9a4eb995968d6041b1e2ac
+msgid "Install by running the following command:"
+msgstr ""
+
+#: ../../qig.rst:362
+# 36d9b86e7e3248b784a3dcf59fc552e3
+msgid "With MySQL now installed we need to make a few configuration changes to /etc/my.cnf. Specifically we need to add the following options to the [mysqld] section:"
+msgstr ""
+
+#: ../../qig.rst:374
+# a5c5a266adba4e3290312bca285a9f01
+msgid "Now that MySQL is properly configured we can start it and configure it to start on boot as follows:"
+msgstr ""
+
+#: ../../qig.rst:384
+#: ../../qig.rst:463
+# 1fe575a11b7a4071b4e6a29dcc38cf07
+# 0b4d699f167b42bb9b193792f0bd0725
+msgid "Installation"
+msgstr ""
+
+#: ../../qig.rst:386
+# 48a0def962364fb793fd558db7a83c29
+msgid "We are now going to install the management server. We do that by executing the following command:"
+msgstr ""
+
+#: ../../qig.rst:393
+# ffbb50ab243643e9b5435264bfd61bf7
+msgid "With the application itself installed we can now setup the database, we'll do that with the following command and options:"
+msgstr ""
+
+#: ../../qig.rst:400
+# 59e045efceb0436b8cecf6c9c5eda843
+msgid "When this process is finished, you should see a message like \"CloudStack has successfully initialized the database.\""
+msgstr ""
+
+#: ../../qig.rst:403
+# 5e4571669d1042a1b867fb1b24dbfbdd
+msgid "Now that the database has been created, we can take the final step in setting up the management server by issuing the following command:"
+msgstr ""
+
+#: ../../qig.rst:412
+# 33ce2bfd534f433e8a6cd4f7c6e1c166
+msgid "System Template Setup"
+msgstr ""
+
+#: ../../qig.rst:414
+# 0d95e3d0c71b4c45858b31f77dde036e
+msgid "CloudStack uses a number of system VMs to provide functionality for accessing the console of virtual machines, providing various networking services, and managing various aspects of storage. This step will acquire those system images ready for deployment when we bootstrap your cloud."
+msgstr ""
+
+#: ../../qig.rst:419
+# d3c498d585ab4741bd2c27b0b2084745
+msgid "Now we need to download the system VM template and deploy that to the share we just mounted. The management server includes a script to properly manipulate the system VMs images."
+msgstr ""
+
+#: ../../qig.rst:427
+# 92903e9533534b6fb4148c0635069661
+msgid "That concludes our setup of the management server. We still need to configure CloudStack, but we will do that after we get our hypervisor set up."
+msgstr ""
+
+#: ../../qig.rst:432
+# 7f1393a48e184b35b9bb4a8b95ac1a13
+msgid "KVM Setup and Installation"
+msgstr ""
+
+#: ../../qig.rst:434
+# d098ee902a904e3c8736a2d3464fd49c
+msgid "KVM is the hypervisor we'll be using - we will recover the initial setup which has already been done on the hypervisor host and cover installation of the agent software, you can use the same steps to add additional KVM nodes to your CloudStack environment."
+msgstr ""
+
+#: ../../qig.rst:443
+# e02d098f8e1a4eb081a496f88791dac0
+msgid "We explicitly are using the management server as a compute node as well, which means that we have already performed many of the prerequisite steps when setting up the management server, but we will list them here for clarity. Those steps are:"
+msgstr ""
+
+#: ../../qig.rst:448
+# fdf9d335282f4fe98e99728f3399c1fd
+msgid ":ref:`conf-network`"
+msgstr ""
+
+#: ../../qig.rst:450
+# 445994f799ba4e909ce0c0a186f2f31d
+msgid ":ref:`conf-hostname`"
+msgstr ""
+
+#: ../../qig.rst:452
+# ab93010654414278b9eed8a6c99160e0
+msgid ":ref:`conf-selinux`"
+msgstr ""
+
+#: ../../qig.rst:454
+# fdb31d5daa78457382f913417f11a829
+msgid ":ref:`conf-ntp`"
+msgstr ""
+
+#: ../../qig.rst:456
+# c13c6efacec5485ab038723e8f958003
+msgid ":ref:`qigconf-pkg-repo`"
+msgstr ""
+
+#: ../../qig.rst:458
+# e9a76dadeb804696ac9ac907ed256fbf
+msgid "You shouldn't need to do that for the management server, of course, but any additional hosts will need for you to complete the above steps."
+msgstr ""
+
+#: ../../qig.rst:465
+# adc6a52e07e645149ab0fd5b03cc2e22
+msgid "Installation of the KVM agent is trivial with just a single command, but afterwards we'll need to configure a few things."
+msgstr ""
+
+#: ../../qig.rst:474
+# 9b94ad0de8bc42b6bfed991871ad6c23
+msgid "KVM Configuration"
+msgstr ""
+
+#: ../../qig.rst:476
+# 41d6a9265c8d47f2b9fb9b657cf8dd10
+msgid "We have two different parts of KVM to configure, libvirt, and QEMU."
+msgstr ""
+
+#: ../../qig.rst:480
+# e4f062f561b8411ab57677d08500d1fe
+msgid "QEMU Configuration"
+msgstr ""
+
+#: ../../qig.rst:482
+# 815a9beec20b476d9771e7ef18b8c600
+msgid "KVM configuration is relatively simple at only a single item. We need to edit the QEMU VNC configuration. This is done by editing /etc/libvirt/qemu.conf and ensuring the following line is present and uncommented."
+msgstr ""
+
+#: ../../qig.rst:488
+# 975c5c294f1442bf81c674603302b96d
+msgid "vnc_listen=0.0.0.0"
+msgstr ""
+
+#: ../../qig.rst:492
+# fa6d60015c4f40879deddfeb0aa1faba
+msgid "Libvirt Configuration"
+msgstr ""
+
+#: ../../qig.rst:494
+# 77d8c22ce01a436c86a3356db1be9f2d
+msgid "CloudStack uses libvirt for managing virtual machines. Therefore it is vital that libvirt is configured correctly. Libvirt is a dependency of cloud-agent and should already be installed."
+msgstr ""
+
+#: ../../qig.rst:498
+# 99f2fbc9c2454f3487ad43f84bb08a12
+msgid "In order to have live migration working libvirt has to listen for unsecured TCP connections. We also need to turn off libvirts attempt to use Multicast DNS advertising. Both of these settings are in /etc/libvirt/libvirtd.conf"
+msgstr ""
+
+#: ../../qig.rst:502
+# 9fc492fb10044ee0844b1d25e91f50ee
+msgid "Set the following paramaters:"
+msgstr ""
+
+#: ../../qig.rst:512
+# 95403c520e0647c88d0026cb30086615
+msgid "Turning on \"listen_tcp\" in libvirtd.conf is not enough, we have to change the parameters as well we also need to modify /etc/sysconfig/libvirtd:"
+msgstr ""
+
+#: ../../qig.rst:515
+# d56b9b860fbc4a259d021e12bda7bc3c
+msgid "Uncomment the following line:"
+msgstr ""
+
+#: ../../qig.rst:521
+# 169629893c8f43fa88410c11c1009c5f
+msgid "Restart libvirt"
+msgstr ""
+
+#: ../../qig.rst:529
+# 18f1fb4c4c8a42b386267c081b445d95
+msgid "KVM configuration complete"
+msgstr ""
+
+#: ../../qig.rst:530
+# 03532dcd2b4c4677a2f98e4a0d94594e
+msgid "That concludes our installation and configuration of KVM, and we'll now move to using the CloudStack UI for the actual configuration of our cloud."
+msgstr ""
+
+#: ../../qig.rst:535
+# 952b415ac3874c7f9d04f5e587352ac9
+msgid "Configuration"
+msgstr ""
+
+#: ../../qig.rst:537
+# 523a82da5a444efe823f80fb51e88066
+msgid "As we noted before we will be using security groups to provide isolation and by default that implies that we'll be using a flat layer-2 network. It also means that the simplicity of our setup means that we can use the quick installer."
+msgstr ""
+
+#: ../../qig.rst:544
+# cbed6a65a67b45e6af0fb6ffff271769
+msgid "UI Access"
+msgstr ""
+
+#: ../../qig.rst:546
+# dda96068dfd5400c8163c00981ab2bb8
+msgid "To get access to CloudStack's web interface, merely point your browser to http://172.16.10.2:8080/client The default username is 'admin', and the default password is 'password'. You should see a splash screen that allows you to choose several options for setting up CloudStack. You should choose the Continue with Basic Setup option."
+msgstr ""
+
+#: ../../qig.rst:552
+# bbb1c7f2891a4ec4a83d9d55bcfa3675
+msgid "You should now see a prompt requiring you to change the password for the admin user. Please do so."
+msgstr ""
+
+#: ../../qig.rst:557
+# 3be78f0dce5244e4b9131f8c619ad9a4
+msgid "Setting up a Zone"
+msgstr ""
+
+#: ../../qig.rst:559
+# 0aba2895b7c74bce8a058589e3983a7c
+msgid "A zone is the largest organization entity in CloudStack - and we'll be creating one, this should be the screen that you see in front of you now. And for us there are 5 pieces of information that we need."
+msgstr ""
+
+#: ../../qig.rst:563
+# 678aeb5fe9214685805c844269bc9fb8
+msgid "Name - we will set this to the ever-descriptive 'Zone1' for our cloud."
+msgstr ""
+
+#: ../../qig.rst:565
+# 63f27019f41b44649ba00f8ca77ec852
+msgid "Public DNS 1 - we will set this to '8.8.8.8' for our cloud."
+msgstr ""
+
+#: ../../qig.rst:567
+# b747f07282f845c1b0e23cb76e573616
+msgid "Public DNS 2 - we will set this to '8.8.4.4' for our cloud."
+msgstr ""
+
+#: ../../qig.rst:569
+# b3ccf7d2313948489f913f8c32a9aeb7
+msgid "Internal DNS1 - we will also set this to '8.8.8.8' for our cloud."
+msgstr ""
+
+#: ../../qig.rst:571
+# d9a7755ae183447788f746bd5a20a8ed
+msgid "Internal DNS2 - we will also set this to '8.8.4.4' for our cloud."
+msgstr ""
+
+#: ../../qig.rst:574
+# d29af6bf0c6f453c99632dcde7d46008
+msgid "CloudStack distinguishes between internal and public DNS. Internal DNS is assumed to be capable of resolving internal-only hostnames, such as your NFS server’s DNS name. Public DNS is provided to the guest VMs to resolve public IP addresses. You can enter the same DNS server for both types, but if you do so, you must make sure that both internal and public IP addresses can route to the DNS server. In our specific case we will not use any names for resources internally, and we have indeed them set to look to the same external resource so as to not add a namerserver setup to our list of requirements."
+msgstr ""
+
+#: ../../qig.rst:586
+# d1ccf0a04f8d407f92b076a97ca934aa
+msgid "Pod Configuration"
+msgstr ""
+
+#: ../../qig.rst:588
+# d633c33294f54ed9b55112c0f0f4c4b6
+msgid "Now that we've added a Zone, the next step that comes up is a prompt for information regading a pod. Which is looking for several items."
+msgstr ""
+
+#: ../../qig.rst:591
+# 5d8b827958834106bb8322c4b726e589
+msgid "Name - We'll use Pod1 for our cloud."
+msgstr ""
+
+#: ../../qig.rst:593
+# 213b395a2593404daf151f1a941d4adc
+msgid "Gateway - We'll use 172.16.10.1 as our gateway"
+msgstr ""
+
+#: ../../qig.rst:595
+# f02f613f386b4d1c8b305c1d35c56583
+msgid "Netmask - We'll use 255.255.255.0"
+msgstr ""
+
+#: ../../qig.rst:597
+# 9c5bffa76ac74249ad74e842f6eebf17
+msgid "Start/end reserved system IPs - we will use 172.16.10.10-172.16.10.20"
+msgstr ""
+
+#: ../../qig.rst:599
+# 5cf252fb06404e90931c41694829ed58
+msgid "Guest gateway - We'll use 172.16.10.1"
+msgstr ""
+
+#: ../../qig.rst:601
+# 5f00b4c2472c4db99f0cfaaa62c9a5a2
+msgid "Guest netmask - We'll use 255.255.255.0"
+msgstr ""
+
+#: ../../qig.rst:603
+# 17730085682c4460bcf6fc9b337e1b79
+msgid "Guest start/end IP - We'll use 172.16.10.30-172.16.10.200"
+msgstr ""
+
+#: ../../qig.rst:607
+# 367247fc307a4a82b2ad9e2b711e5619
+msgid "Cluster"
+msgstr ""
+
+#: ../../qig.rst:609
+# 7850cd3533944572afd0e2c12f25a29f
+msgid "Now that we've added a Zone, we need only add a few more items for configuring the cluster."
+msgstr ""
+
+#: ../../qig.rst:612
+# 7001d238c08a4539b6f079919c83370e
+msgid "Name - We'll use Cluster1"
+msgstr ""
+
+#: ../../qig.rst:614
+# b757d57d9ef8406e9cb173ab58d3c2f7
+msgid "Hypervisor - Choose KVM"
+msgstr ""
+
+#: ../../qig.rst:616
+# d2da65ca4fcc49799aa20d81580d1d11
+msgid "You should be prompted to add the first host to your cluster at this point. Only a few bits of information are needed."
+msgstr ""
+
+#: ../../qig.rst:619
+# 3882023bf413443a94edf6abde71aa6d
+msgid "Hostname - we'll use the IP address 172.16.10.2 since we didn't set up a DNS server."
+msgstr ""
+
+#: ../../qig.rst:622
+# d10fbbf3eaeb49159c2e6ccc868e03b1
+msgid "Username - we'll use 'root'"
+msgstr ""
+
+#: ../../qig.rst:624
+# 9c4f5c5877de4ea98bbd1fb9735ecef1
+msgid "Password - enter the operating system password for the root user"
+msgstr ""
+
+#: ../../qig.rst:628
+# 3d5ffbc59d224d41be2df9ba6af77742
+msgid "Primary Storage"
+msgstr ""
+
+#: ../../qig.rst:630
+# 66d0666b459a47c3b5f48d2883046b70
+msgid "With your cluster now setup - you should be prompted for primary storage information. Choose NFS as the storage type and then enter the following values in the fields:"
+msgstr ""
+
+#: ../../qig.rst:634
+# ca283f835167437fb9bc1ef6393ca820
+msgid "Name - We'll use 'Primary1'"
+msgstr ""
+
+#: ../../qig.rst:636
+# fdf29ecc70964523b52e9de67e9413d7
+msgid "Server - We'll be using the IP address 172.16.10.2"
+msgstr ""
+
+#: ../../qig.rst:638
+# 7e622eac227540c9bee2de26c79cb398
+msgid "Path - Well define /primary as the path we are using"
+msgstr ""
+
+#: ../../qig.rst:642
+# 749f44f07ab84067949bed01b90f7371
+msgid "Secondary Storage"
+msgstr ""
+
+#: ../../qig.rst:644
+# 387b9b2ba8bb4d86bbd092c06b307189
+msgid "If this is a new zone, you'll be prompted for secondary storage information - populate it as follows:"
+msgstr ""
+
+#: ../../qig.rst:647
+# b25a138b410441ccabde5dc127832043
+msgid "NFS server - We'll use the IP address 172.16.10.2"
+msgstr ""
+
+#: ../../qig.rst:649
+# 05a433329180429f9aadec69507b153f
+msgid "Path - We'll use /secondary"
+msgstr ""
+
+#: ../../qig.rst:651
+# 5f25228532674a9881e0c4b867cf64a9
+msgid "Now, click Launch and your cloud should begin setup - it may take several minutes depending on your internet connection speed for setup to finalize."
+msgstr ""
+
+#: ../../qig.rst:654
+# bcb5d6bf55794f36bb79ef590164a807
+msgid "That's it, you are done with installation of your Apache CloudStack cloud."
+msgstr ""
+
diff --git a/source/installguide/locale/pot/storage_setup.pot b/source/installguide/locale/pot/storage_setup.pot
new file mode 100644
index 0000000..c70967e
--- /dev/null
+++ b/source/installguide/locale/pot/storage_setup.pot
@@ -0,0 +1,290 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../storage_setup.rst:18
+# d6b2b3302e474c2ca46f28b9bee03734
+msgid "Storage Setup"
+msgstr ""
+
+#: ../../storage_setup.rst:20
+# 7752c36da35f479d9c03995e830ae253
+msgid "CloudStack is designed to work with a wide variety of commodity and enterprise-grade storage. Local disk may be used as well, if supported by the selected hypervisor. Storage type support for guest virtual disks differs based on hypervisor selection."
+msgstr ""
+
+#: ../../storage_setup.rst:26
+# 538f0beb0b4e4e2a9983e312661eb54f
+msgid "Storage Type"
+msgstr ""
+
+#: ../../storage_setup.rst:26
+# 18b92c5cd5074bb4b06534aff95e18c8
+msgid "XenServer"
+msgstr ""
+
+#: ../../storage_setup.rst:26
+# 6ed9b0e44342476a9dbbdbf4e4b917fe
+msgid "vSphere"
+msgstr ""
+
+#: ../../storage_setup.rst:26
+# ac3ca3b0a1c641a3bc1de1a92146eb91
+msgid "KVM"
+msgstr ""
+
+#: ../../storage_setup.rst:28
+# 03e3922684d94f63abcc832e20828d0d
+msgid "NFS"
+msgstr ""
+
+#: ../../storage_setup.rst:28
+#: ../../storage_setup.rst:28
+#: ../../storage_setup.rst:28
+#: ../../storage_setup.rst:29
+#: ../../storage_setup.rst:30
+#: ../../storage_setup.rst:31
+#: ../../storage_setup.rst:31
+#: ../../storage_setup.rst:31
+# 3b99a671b8ab4908aea8b3e783a22b19
+# 5c64989b5d4b4b0e8b086335877bdcf9
+# efa230d191b5477f887a61486039d99e
+# 53b67c59114241cb81ae1f4bcd7bdf26
+# 02d62854fef943e88ea4d32d21e23ffb
+# 0bcd3eeecde3461a98be48e06880b63e
+# 69437bfe66f8494cb9119f1ac4f3751a
+# 02613a70f2594d3bb3d1192ff3e520d5
+msgid "Supported"
+msgstr ""
+
+#: ../../storage_setup.rst:29
+# bc6393ab53db4060bb65171cc25a14b2
+msgid "iSCSI"
+msgstr ""
+
+#: ../../storage_setup.rst:29
+# 5e75eb74e709489cb5160ea8d55c040c
+msgid "Supported via VMFS"
+msgstr ""
+
+#: ../../storage_setup.rst:29
+#: ../../storage_setup.rst:30
+# cae1e3af97e747cf8adf4fc7edd27ea4
+# bcf642ada6354a428f7e09abac6608b5
+msgid "Supported via Clustered Filesystems"
+msgstr ""
+
+#: ../../storage_setup.rst:30
+# 6996e2e99e9048ce97d0e6f5fb931f60
+msgid "Fiber Channel"
+msgstr ""
+
+#: ../../storage_setup.rst:30
+# 019efc65f57148479631b63195d36314
+msgid "Supported via Pre-existing SR"
+msgstr ""
+
+#: ../../storage_setup.rst:31
+# 32746b62e4f8487cb0c808a966bfb210
+msgid "Local Disk"
+msgstr ""
+
+#: ../../storage_setup.rst:34
+# 6e8fd34eb56f4473abecb174650042c8
+msgid "The use of the Cluster Logical Volume Manager (CLVM) for KVM is not officially supported with CloudStack."
+msgstr ""
+
+#: ../../storage_setup.rst:39
+# 052dba62e53b4928a4316a9e7e9a7718
+msgid "Small-Scale Setup"
+msgstr ""
+
+#: ../../storage_setup.rst:41
+# ba74f151dee944c59ecb4711a133a657
+msgid "In a small-scale setup, a single NFS server can function as both primary and secondary storage. The NFS server just needs to export two separate shares, one for primary storage and the other for secondary storage."
+msgstr ""
+
+#: ../../storage_setup.rst:47
+# 115b100b50994f4bbe369e5a89b5081d
+msgid "Secondary Storage"
+msgstr ""
+
+#: ../../storage_setup.rst:49
+# bdbd2ecb612e4c6d833f2a4803d9efc0
+msgid "CloudStack is designed to work with any scalable secondary storage system. The only requirement is the secondary storage system supports the NFS protocol."
+msgstr ""
+
+#: ../../storage_setup.rst:54
+# dd9865baaf564c74b74a86e19447d21b
+msgid "The storage server should be a machine with a large number of disks. The disks should ideally be managed by a hardware RAID controller. Modern hardware RAID controllers support hot plug functionality independent of the operating system so you can replace faulty disks without impacting the running operating system."
+msgstr ""
+
+#: ../../storage_setup.rst:62
+# 81888613f5f6470cb75302dcb4c8dc22
+msgid "Example Configurations"
+msgstr ""
+
+#: ../../storage_setup.rst:64
+# 15dfab7b505743acb78118d48e6a1df0
+msgid "In this section we go through a few examples of how to set up storage to work properly on a few types of NFS and iSCSI storage systems."
+msgstr ""
+
+#: ../../storage_setup.rst:69
+# 800bb50ed8b643849918b01277052e7c
+msgid "Linux NFS on Local Disks and DAS"
+msgstr ""
+
+#: ../../storage_setup.rst:71
+# f2fcb96d0dea4baf8e482525c0dd8245
+msgid "This section describes how to configure an NFS export on a standard Linux installation. The exact commands might vary depending on the operating system version."
+msgstr ""
+
+#: ../../storage_setup.rst:75
+# cf13fcc5fa0b4939a8e8574245d1a1e5
+msgid "Install the RHEL/CentOS distribution on the storage server."
+msgstr ""
+
+#: ../../storage_setup.rst:77
+# 005b8dd262fd4a4388849d5e56b1a54f
+msgid "If the root volume is more than 2 TB in size, create a smaller boot volume to install RHEL/CentOS. A root volume of 20 GB should be sufficient."
+msgstr ""
+
+#: ../../storage_setup.rst:81
+# 217ac8a1620b4bb993b70343ef9cd6ab
+msgid "After the system is installed, create a directory called /export. This can each be a directory in the root partition itself or a mount point for a large disk volume."
+msgstr ""
+
+#: ../../storage_setup.rst:85
+# e51ba40cb56b42aea266a196d1886b28
+msgid "If you have more than 16TB of storage on one host, create multiple EXT3 file systems and multiple NFS exports. Individual EXT3 file systems cannot exceed 16TB."
+msgstr ""
+
+#: ../../storage_setup.rst:89
+# f9ecc678c0a946ada4722e2f84868013
+msgid "After /export directory is created, run the following command to configure it as an NFS export."
+msgstr ""
+
+#: ../../storage_setup.rst:96
+# 166a5ad4eace4ee1acac57e77772e301
+msgid "Adjust the above command to suit your deployment needs."
+msgstr ""
+
+#: ../../storage_setup.rst:98
+# c6efefc3bb214750a1aa110365bfb7c4
+msgid "**Limiting NFS export.** It is highly recommended that you limit the NFS export to a particular subnet by specifying a subnet mask (e.g.,”192.168.1.0/24”). By allowing access from only within the expected cluster, you avoid having non-pool member mount the storage. The limit you place must include the management network(s) and the storage network(s). If the two are the same network then one CIDR is sufficient. If you have a separate storage network you must provide separate CIDR’s for both or one CIDR that is broad enough to span both."
+msgstr ""
+
+#: ../../storage_setup.rst:108
+#: ../../storage_setup.rst:236
+# 2dee02ec08f44c6eb41bbd83267e69b6
+# daffef1e68c1468ca3f7396f5436cf19
+msgid "The following is an example with separate CIDRs:"
+msgstr ""
+
+#: ../../storage_setup.rst:114
+#: ../../storage_setup.rst:242
+# 314c4d57ade04b589bb9cc53855854f0
+# 302894e6d4d8419dadbee7187c9761e3
+msgid "**Removing the async flag.** The async flag improves performance by allowing the NFS server to respond before writes are committed to the disk. Remove the async flag in your mission critical production deployment."
+msgstr ""
+
+#: ../../storage_setup.rst:119
+# fc530cedf53646ef8383509ca79aaf46
+msgid "Run the following command to enable NFS service."
+msgstr ""
+
+#: ../../storage_setup.rst:125
+# 43b62119fea74c9585550f73f8f82558
+msgid "Edit the /etc/sysconfig/nfs file and uncomment the following lines."
+msgstr ""
+
+#: ../../storage_setup.rst:136
+# 1d4f8831fb8f493bbf0d2102a2d94333
+msgid "Edit the /etc/sysconfig/iptables file and add the following lines at the beginning of the INPUT chain."
+msgstr ""
+
+#: ../../storage_setup.rst:153
+# 9b07e0f5f1b4436083b1b95549bd51cc
+msgid "Reboot the server."
+msgstr ""
+
+#: ../../storage_setup.rst:155
+# e020d0f272694579a5ba76a20f504882
+msgid "An NFS share called /export is now set up."
+msgstr ""
+
+#: ../../storage_setup.rst:158
+# 954bd15449384ef982eb066148bede4e
+msgid "When copying and pasting a command, be sure the command has pasted as a single line before executing. Some document viewers may introduce unwanted line breaks in copied text."
+msgstr ""
+
+#: ../../storage_setup.rst:164
+# 57361739f18248a8a389947c9bc2cad2
+msgid "Linux NFS on iSCSI"
+msgstr ""
+
+#: ../../storage_setup.rst:166
+# 2b54e23d9a61475595ca9e0e83867e12
+msgid "Use the following steps to set up a Linux NFS server export on an iSCSI volume. These steps apply to RHEL/CentOS 5 distributions."
+msgstr ""
+
+#: ../../storage_setup.rst:169
+# f1286e7f062d4b9aa981184cc7501688
+msgid "Install iscsiadm."
+msgstr ""
+
+#: ../../storage_setup.rst:178
+# 346450ad74ac4b19964ee166ad4c9d20
+msgid "Discover the iSCSI target."
+msgstr ""
+
+#: ../../storage_setup.rst:184
+#: ../../storage_setup.rst:196
+# 6274d39a5e6845259cc61a75836241fe
+# 78922f43acdd4b6ca556c8c6094a1816
+msgid "For example:"
+msgstr ""
+
+#: ../../storage_setup.rst:190
+# aa60b340ef47437486a5520511933ff9
+msgid "Log in."
+msgstr ""
+
+#: ../../storage_setup.rst:202
+# ee970ba277924184bb6d07662f86710c
+msgid "Discover the SCSI disk. For example:"
+msgstr ""
+
+#: ../../storage_setup.rst:209
+# a27db3a17e254b7f81d044d888ed5d83
+msgid "Format the disk as ext3 and mount the volume."
+msgstr ""
+
+#: ../../storage_setup.rst:217
+# 73c6a94d549942489bcac311f27242ee
+msgid "Add the disk to /etc/fstab to make sure it gets mounted on boot."
+msgstr ""
+
+#: ../../storage_setup.rst:223
+# b401c3dd18284c72bef05b03f96de014
+msgid "Now you can set up /export as an NFS share."
+msgstr ""
+
+#: ../../storage_setup.rst:225
+# ac62ebcca250423f8b0a8c1c4d2ea5f3
+msgid "**Limiting NFS export.** In order to avoid data loss, it is highly recommended that you limit the NFS export to a particular subnet by specifying a subnet mask (e.g.,”192.168.1.0/24”). By allowing access from only within the expected cluster, you avoid having non-pool member mount the storage and inadvertently delete all its data. The limit you place must include the management network(s) and the storage network(s). If the two are the same network then one CIDR is sufficient. If you have a separate storage network you must provide separate CIDRs for both or one CIDR that is broad enough to span both."
+msgstr ""
+
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/building_from_source.mo b/source/installguide/locale/zh_CN/LC_MESSAGES/building_from_source.mo
new file mode 100644
index 0000000..e1816c6
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/building_from_source.mo
Binary files differ
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/building_from_source.po b/source/installguide/locale/zh_CN/LC_MESSAGES/building_from_source.po
new file mode 100644
index 0000000..ce68b1a
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/building_from_source.po
@@ -0,0 +1,582 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: 2014-06-30 09:52+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# ef11ea68beec49c5871db512f598d676
+#: ../../building_from_source.rst:18
+msgid "Building from Source"
+msgstr "从源码编译"
+
+# 2a043bdd667b4d9293f70ad36316281e
+#: ../../building_from_source.rst:20
+msgid ""
+"The official CloudStack release is always in source code form. You will "
+"likely be able to find \"convenience binaries,\" the source is the canonical"
+" release. In this section, we'll cover acquiring the source release and "
+"building that so that you can deploy it using Maven or create Debian "
+"packages or RPMs."
+msgstr "CloudStack官方总是以源代码形式发布。你可以找到 \"方便的二进制文件\"， 这些源都是规范的发布版本。在本节将包括获取和编译发行版源代码，使用Maven、创建Debian或rpm软件包来进行部署。"
+
+# 34b9935b1b234772875a5632f77cc973
+#: ../../building_from_source.rst:26
+msgid ""
+"Note that building and deploying directly from source is typically not the "
+"most efficient way to deploy an IaaS. However, we will cover that method as "
+"well as building RPMs or Debian packages for deploying CloudStack."
+msgstr "请注意，直接从源代码构建和部署一个IaaS通常不是最有效的方式。然而，我们仍将介绍这种方法，就像构建RPMs或Debian软件包来部署CloudStack一样。"
+
+# dc09a8fd969d4628811a6127bb066d15
+#: ../../building_from_source.rst:31
+msgid ""
+"The instructions here are likely version-specific. That is, the method for "
+"building from source for the 4.0.x series is different from the 4.1.x "
+"series."
+msgstr "本节中的指令仅限定于特定的版本。也就是说，从源码编译4.0.x系列和4.1.x系列的方法是不同的。"
+
+# 1122421db6114fc9919baefb86af655a
+#: ../../building_from_source.rst:35
+msgid ""
+"If you are working with a unreleased version of CloudStack, see the "
+"INSTALL.md file in the top-level directory of the release."
+msgstr "如果你正在使用一个非发行版的CloudStack，请查阅该版本主目录下的INSTALL.md文件。"
+
+# 70eb2ab692764b6dbb6ea174f0062a59
+#: ../../building_from_source.rst:40
+msgid "Getting the release"
+msgstr "获得发行版"
+
+# 16e7f13a2bf342fd9eff4ec10614bfb7
+#: ../../building_from_source.rst:42
+msgid ""
+"You can download the latest CloudStack release from the `Apache CloudStack "
+"project download page <http://cloudstack.apache.org/downloads.html>`_."
+msgstr "下载CloudStack最新发行版，可以在 `Apache CloudStack 项目下载页面： <http://cloudstack.apache.org/downloads.html>`_."
+
+# 66ddf14b21c1450b84222ff24a97c8a1
+#: ../../building_from_source.rst:46
+msgid ""
+"Prior releases are available via archive.apache.org as well. See the "
+"downloads page for more information on archived releases."
+msgstr "之前的版本同样可以通过archive.apache.org获得。请参阅下载页面上的存档版本的更多信息。"
+
+# ffcd1760171b4c22aadfbdf0a143c2f3
+#: ../../building_from_source.rst:49
+msgid ""
+"You'll notice several links under the 'Latest release' section. A link to a "
+"file ending in ``tar.bz2``, as well as a PGP/GPG signature, MD5, and SHA512 "
+"file."
+msgstr "你会注意到在'最新发行版'下方有几个链接。一个链接以 ``tar.bz2`` 文件结尾，以及PGP/GPG签名，MD5和ShA512文件。"
+
+# 25bd15343d884479bb06e47381b678fd
+#: ../../building_from_source.rst:53
+msgid ""
+"The ``tar.bz2`` file contains the Bzip2-compressed tarball with the source "
+"code."
+msgstr "``tar.bz2`` 文件包含使用Bzip2压缩的源代码。"
+
+# 3d236d0dfc154c268fed0612bdd129ce
+#: ../../building_from_source.rst:56
+msgid ""
+"The ``.asc`` file is a detached cryptographic signature that can be used to "
+"help verify the authenticity of the release."
+msgstr " ``.asc`` 是一个独立加密签名文件，可以用来帮助验证发行版的真实性。"
+
+# 6d4f2dc258d643b8b8733a59476db314
+#: ../../building_from_source.rst:59
+msgid ""
+"The ``.md5`` file is an MD5 hash of the release to aid in verify the "
+"validity of the release download."
+msgstr " ``.md5`` 是MD5哈希值文件，用于帮助验证下载的发行版是否有效。"
+
+# 3a3f100d4fce444482fc82808ddc6b88
+#: ../../building_from_source.rst:62
+msgid ""
+"The ``.sha`` file is a SHA512 hash of the release to aid in verify the "
+"validity of the release download."
+msgstr " ``.sha`` 是SHA512哈希值文件，用于帮助验证下载的发行版是否有效。"
+
+# 5b9f966ab0404b0895cad4a389bc200c
+#: ../../building_from_source.rst:67
+msgid "Verifying the downloaded release"
+msgstr "验证下载的版本"
+
+# db3e51bdf33d4742a685c0d6162f05a4
+#: ../../building_from_source.rst:69
+msgid ""
+"There are a number of mechanisms to check the authenticity and validity of a"
+" downloaded release."
+msgstr "有很多机制可以检查下载的发行版的真实性和有效性。"
+
+# a41259b8a7754a1d968844b286750d17
+#: ../../building_from_source.rst:74
+msgid "Getting the KEYS"
+msgstr "获取密钥"
+
+# 070bfe72ade6433292ddf947a78ff960
+#: ../../building_from_source.rst:76
+msgid ""
+"To enable you to verify the GPG signature, you will need to download the "
+"`KEYS <http://www.apache.org/dist/cloudstack/KEYS>`_ file."
+msgstr "为了实现GPG签名验证，你需要下载 `密钥 <http://www.apache.org/dist/cloudstack/KEYS>`_ 文件。"
+
+# 639635ff8564492fb4965f5da6a4215f
+#: ../../building_from_source.rst:79
+msgid "You next need to import those keys, which you can do by running:"
+msgstr "下一步需要导入这些密钥，你可以运行如下命令："
+
+# 7cad52cd29334223a2eb5a524fa31229
+#: ../../building_from_source.rst:87
+msgid "GPG"
+msgstr "GPG"
+
+# 108a752dff73440c9de3ffbca5f64843
+#: ../../building_from_source.rst:89
+msgid ""
+"The CloudStack project provides a detached GPG signature of the release. To "
+"check the signature, run the following command:"
+msgstr "CloudStack项目提供了发行版的分离GPG签名。运行如下命令检查签名："
+
+# 7b1992ef9c664f60bed1e3da72b53326
+#: ../../building_from_source.rst:96
+msgid ""
+"If the signature is valid you will see a line of output that contains 'Good "
+"signature'."
+msgstr "如果签名是有效的，你会看到一行包含“Good signature”的信息。"
+
+# 2f3891019c1c4d879aea2ce4a283292a
+#: ../../building_from_source.rst:101
+msgid "MD5"
+msgstr "MD5"
+
+# ddbbe1736210472d8f2c8d157a51884d
+#: ../../building_from_source.rst:103
+msgid ""
+"In addition to the cryptographic signature, CloudStack has an MD5 checksum "
+"that you can use to verify the download matches the release. You can verify "
+"this hash by executing the following command:"
+msgstr "除了加密签名，CloudStack还提供了MD5校验和，用于验证下载的发行版。您可以通过执行下面的命令验证这个哈希值:"
+
+# 9490a741b6b049feb039b5dd8c7bace1
+#: ../../building_from_source.rst:111
+msgid ""
+"If this successfully completes you should see no output. If there is any "
+"output from them, then there is a difference between the hash you generated "
+"locally and the hash that has been pulled from the server."
+msgstr "如果成功完成，你应该看不到任何输出。如果有任何输出，则说明你本地生成的哈希值与服务器上获取的是不同的。"
+
+# a34badbd49654f2e9c9040981cdfa1be
+#: ../../building_from_source.rst:117
+msgid "SHA512"
+msgstr "SHA512"
+
+# 8137cfe2c2df43c587b7bfed84c0612e
+#: ../../building_from_source.rst:119
+msgid ""
+"In addition to the MD5 hash, the CloudStack project provides a SHA512 "
+"cryptographic hash to aid in assurance of the validity of the downloaded "
+"release. You can verify this hash by executing the following command:"
+msgstr "除了MD5校验和，CloudStack还提供了SHA512加密哈希，用于验证下载的发行版。您可以通过执行下面的命令验证这个哈希值:"
+
+# 45114708d09246febbeee238d2b1e303
+#: ../../building_from_source.rst:127
+msgid ""
+"If this command successfully completes you should see no output. If there is"
+" any output from them, then there is a difference between the hash you "
+"generated locally and the hash that has been pulled from the server."
+msgstr "如果命令成功完成，你应该看不到任何输出。如果有任何输出，则说明你本地生成的哈希值与服务器上获取的不同。"
+
+# 48a54f38aeb04d938f6ce37e3ed8b1d3
+#: ../../building_from_source.rst:134
+msgid "Prerequisites for building Apache CloudStack"
+msgstr "编译Apache CloudStack的先决条件"
+
+# 4d1bceb893204853a12377f796db8762
+#: ../../building_from_source.rst:136
+msgid ""
+"There are a number of prerequisites needed to build CloudStack. This "
+"document assumes compilation on a Linux system that uses RPMs or DEBs for "
+"package management."
+msgstr "编译CloudStack所需的先决条件很多，本文假定在Linux系统上编译，使用RPMs或DEBs包管理。"
+
+# d618af2b2ace42e1a270c753a9be20e6
+#: ../../building_from_source.rst:140
+msgid "You will need, at a minimum, the following to compile CloudStack:"
+msgstr "如下是编译CloudStack的最低需求："
+
+# 06302615cd204c05bb9ee7c9a463a336
+#: ../../building_from_source.rst:142
+msgid "Maven (version 3)"
+msgstr "Maven (版本 3)"
+
+# 12e01c26b3b343d39e522dbde2704e6f
+#: ../../building_from_source.rst:144
+msgid "Java (OpenJDK 1.6 or Java 7/OpenJDK 1.7)"
+msgstr "Java (OpenJDK 1.6 或 Java 7/OpenJDK 1.7)"
+
+# fad73fd5cd0d43dba668f37c6d2baaa5
+#: ../../building_from_source.rst:146
+msgid "Apache Web Services Common Utilities (ws-commons-util)"
+msgstr "Apache网页服务器常用工具（ws-commons-util）"
+
+# 3cd08240ad30472e8a18797edea67732
+#: ../../building_from_source.rst:148
+msgid "MySQL"
+msgstr "MySQL"
+
+# 34fdc352ce70420ebf3d4c32e0ef790e
+#: ../../building_from_source.rst:150
+msgid "MySQLdb (provides Python database API)"
+msgstr "MySQLdb (提供python数据库API)"
+
+# b94e3afe30b04baa84d114d1cc67e56b
+#: ../../building_from_source.rst:152
+msgid "Tomcat 6 (not 6.0.35)"
+msgstr "Tomcat 6 (非 6.0.35)"
+
+# 6269e20f8b1248af837e3d75b2d56cf7
+#: ../../building_from_source.rst:154
+msgid "genisoimage"
+msgstr "genisoimage"
+
+# d43cbcb988fd42e08c351dfdaaa519aa
+#: ../../building_from_source.rst:156
+msgid "rpmbuild or dpkg-dev"
+msgstr "rpmbuild 或 dpkg-dev"
+
+# 27d74522549f4b85ac4bcd78e737b72c
+#: ../../building_from_source.rst:160
+msgid "Extracting source"
+msgstr "提取的源代码"
+
+# 25f6064ab9e64561948107df87e2d317
+#: ../../building_from_source.rst:162
+msgid ""
+"Extracting the CloudStack release is relatively simple and can be done with "
+"a single command as follows:"
+msgstr "提取CloudStack发行版源代码相对简单，使用如下命令："
+
+# 78aa3b8b39704c1f8561b069d0cfcb4d
+#: ../../building_from_source.rst:169
+msgid "You can now move into the directory:"
+msgstr "你现在可以进入该目录："
+
+# c46dc00000204d2cb73ae63e116bc55a
+#: ../../building_from_source.rst:177
+msgid "Building DEB packages"
+msgstr "编译DEB包"
+
+# 4b6cce4d00f748ada32203791b19b088
+#: ../../building_from_source.rst:179
+msgid ""
+"In addition to the bootstrap dependencies, you'll also need to install "
+"several other dependencies. Note that we recommend using Maven 3, which is "
+"not currently available in 12.04.1 LTS. So, you'll also need to add a PPA "
+"repository that includes Maven 3. After running the command ``add-apt-"
+"repository``, you will be prompted to continue and a GPG key will be added."
+msgstr "除了引导依赖项，还需要安装几个其他的依赖包。请注意，我们推荐使用的Maven 3，在Ubuntu 12.04.1 LTS目前不支持。所以，还需要添加一个包含Maven 3 的PPA库。运行命令“add-apt-repository”，系统将提示您继续添加GPG密钥后继续。"
+
+# 283980d16b48466bb2a2d3b17ff1fede
+#: ../../building_from_source.rst:194
+msgid ""
+"While we have defined, and you have presumably already installed the "
+"bootstrap prerequisites, there are a number of build time prerequisites that"
+" need to be resolved. CloudStack uses maven for dependency resolution. You "
+"can resolve the buildtime depdencies for CloudStack by running:"
+msgstr "虽然我们做了一些定义，并且可能已经安装了引导的前提条件，但仍有一些在编译时需要解决的先决条件。CloudStack使用Maven进行依赖性解析。您可以通过运行以下命令，来解决编译CloudStack时的依赖性："
+
+# 7e08137b290649cda9b8e9b728ff33aa
+#: ../../building_from_source.rst:204
+msgid ""
+"Now that we have resolved the dependencies we can move on to building "
+"CloudStack and packaging them into DEBs by issuing the following command."
+msgstr "现在我们已经解决了依赖关系，可以使用如下命令编译CloudStack和创建DEB包："
+
+# ec3f8fd379b7417294d5b01ce47f367f
+#: ../../building_from_source.rst:212
+msgid ""
+"This command will build the following debian packages. You should have all "
+"of the following:"
+msgstr "该命令将创建如下debian软件包。应该有如下这些内容:"
+
+# 8521111f14944fbc8f62bfb2f4cb8a0b
+#: ../../building_from_source.rst:227
+msgid "Setting up an APT repo"
+msgstr "设置APT仓库"
+
+# f937d1aff1e74e8d8869d99a5dcf0315
+#: ../../building_from_source.rst:229
+msgid ""
+"After you've created the packages, you'll want to copy them to a system "
+"where you can serve the packages over HTTP. You'll create a directory for "
+"the packages and then use ``dpkg-scanpackages`` to create ``Packages.gz``, "
+"which holds information about the archive structure. Finally, you'll add the"
+" repository to your system(s) so you can install the packages using APT."
+msgstr "软件包创建完成后，你需要将软件包拷贝至可以提供HTTP服务的系统上。创建用于存放软件包的目录，并使用 ``dpkg-scanpackages`` 命令创建包含归档结构信息的 ``Packages.gz`` 文件。在系统中添加这个仓库源，最后使用该APT安装软件包。 "
+
+# 77189e27fd6648db96421e68ea2197c7
+#: ../../building_from_source.rst:236
+msgid ""
+"The first step is to make sure that you have the **dpkg-dev** package "
+"installed. This should have been installed when you pulled in the "
+"**debhelper** application previously, but if you're generating "
+"``Packages.gz`` on a different system, be sure that it's installed there as "
+"well."
+msgstr "第一步是确保你已经安装了 **dpkg-dev** 软件。一般在使用 **debhelper** 程序之前就已经安装了。如果你是在其他系统中生成的 ``Packages.gz`` 文件，请确保它已经被安装。"
+
+# ca7c2a636f664075b7104554ed4ea25d
+#: ../../building_from_source.rst:246
+msgid ""
+"The next step is to copy the DEBs to the directory where they can be served "
+"over HTTP. We'll use ``/var/www/cloudstack/repo`` in the examples, but "
+"change the directory to whatever works for you."
+msgstr "下一步是将DEB文件复制到提供HTTP服务的目录中。在示例中，我们使用 ``/var/www/cloudstack/repo``作为示例 ，你也可以更改为更适合你的目录。"
+
+# 5aed13bc18cc47d0a3d386be28663478
+#: ../../building_from_source.rst:258
+msgid "You can safely ignore the warning about a missing override file."
+msgstr "你可以忽略缺少覆盖文件的警告信息。"
+
+# 2ab43ed9a4ad40339e0b43646ae7e6a7
+#: ../../building_from_source.rst:260
+msgid ""
+"Now you should have all of the DEB packages and ``Packages.gz`` in the "
+"``binary`` directory and available over HTTP. (You may want to use ``wget`` "
+"or ``curl`` to test this before moving on to the next step.)"
+msgstr "现在你应该可以通过HTTP访问 ``binary`` 目录中所有的DEB安装包和 ``Packages.gz`` 文件。(在进行下一步前，你需要使用 ``wget`` 或 ``curl`` 命令测试。)"
+
+# 410e592ce4134e54a0c21c37dc761c1d
+#: ../../building_from_source.rst:266
+msgid "Configuring your machines to use the APT repository"
+msgstr "配置使用APT仓库源的主机"
+
+# ec3e958425e048aa8e4fb1916ef372de
+#: ../../building_from_source.rst:268
+msgid ""
+"Now that we have created the repository, you need to configure your machine "
+"to make use of the APT repository. You can do this by adding a repository "
+"file under ``/etc/apt/sources.list.d``. Use your preferred editor to create "
+"``/etc/apt/sources.list.d/cloudstack.list`` with this line:"
+msgstr "现在,我们已经创建了仓库，然后配置你的服务器来使用APT仓库源。你可以在 ``/etc/apt/sources.list.d`` 目录中添加仓库文件。使用你喜欢的编辑器来创建``/etc/apt/sources.list.d/cloudstack.list`` 文件并加入类似如下信息:"
+
+# affbe297a4444a9e9d87f2bb39672d9f
+#: ../../building_from_source.rst:278
+msgid ""
+"Now that you have the repository info in place, you'll want to run another "
+"update so that APT knows where to find the CloudStack packages."
+msgstr "现在，您已经准备好软件仓库，然后更新以下，使得APT知道从哪里找到CloudStack的软件包。"
+
+# 2806875948bd4534b353edcf499fd5af
+#: ../../building_from_source.rst:285
+msgid "You can now move on to the instructions under Install on Ubuntu."
+msgstr "现在可以翻到在Ubuntu上安装CloudStack的一章去了。"
+
+# f14be60974c1461e99bd00a8090db43a
+#: ../../building_from_source.rst:289
+msgid "Building RPMs from Source"
+msgstr "从源码编译RPM包"
+
+# 8f87d648db12475a82e931fdba69af9d
+#: ../../building_from_source.rst:291
+msgid ""
+"As mentioned previously in `“Prerequisites for building Apache CloudStack” "
+"<#prerequisites-for-building-apache-cloudstack>`_, you will need to install "
+"several prerequisites before you can build packages for CloudStack. Here "
+"we'll assume you're working with a 64-bit build of CentOS or Red Hat "
+"Enterprise Linux."
+msgstr "正如先前 `“编译Apache CloudStack的先决条件 <#prerequisites-for-building-apache-cloudstack>`_所说，在编译CloudStack之前需要安装一些先决条件。这里假设你使用的是64位的CentOS或Red Hat Enterprise Linux."
+
+# c37ae1838eb34ab694493fa102119691
+#: ../../building_from_source.rst:305
+msgid ""
+"Next, you'll need to install build-time dependencies for CloudStack with "
+"Maven. We're using Maven 3, so you'll want to `grab a Maven 3 tarball "
+"<http://maven.apache.org/download.cgi>`_ and uncompress it in your home "
+"directory (or whatever location you prefer):"
+msgstr "接下来，你将需要安装编译CloudStack时依赖的Maven。 使用 Maven 3, 所以你需要 `提取 Maven 3 压缩包 <http://maven.apache.org/download.cgi>`_ 并解压到你的主目录 (或任何你喜欢的目录):"
+
+# afb9d4d455cc4a689b58d254dcd9896d
+#: ../../building_from_source.rst:318
+msgid ""
+"Maven also needs to know where Java is, and expects the JAVA\\_HOME "
+"environment variable to be set:"
+msgstr "Maven还需要知道Java程序路径，和JAVA\\_HOME环境变量输出的设置："
+
+# a8eaac2e266d48dabaf04dff48781e01
+#: ../../building_from_source.rst:325
+msgid "Verify that Maven is installed correctly:"
+msgstr "验证Maven是否被正确安装："
+
+# 76c3a8ce403d460bbd79e42edb06fb62
+#: ../../building_from_source.rst:331
+msgid ""
+"You probably want to ensure that your environment variables will survive a "
+"logout/reboot. Be sure to update ``~/.bashrc`` with the PATH and JAVA\\_HOME"
+" variables."
+msgstr "如果想确保环境变量将在注销或重启后仍保留。一定要更新 ``~/.bashrc`` 中的PATH和JAVA\\_HOME 变量。"
+
+# 7e91515caf2d407b8196d2bb067f12f6
+#: ../../building_from_source.rst:335
+msgid ""
+"Building RPMs for CloudStack is fairly simple. Assuming you already have the"
+" source downloaded and have uncompressed the tarball into a local directory,"
+" you're going to be able to generate packages in just a few minutes."
+msgstr "编译CloudStack的RPM包相当简单。假设你已经下载了源码并解压压缩文件到一个本地目录中，你可以在几分钟之内完成编译。"
+
+# bf6a8f0ff1ab4b5ab8af48ee83cedda3
+#: ../../building_from_source.rst:341
+msgid ""
+"Packaging has Changed. If you've created packages for CloudStack previously,"
+" you should be aware that the process has changed considerably since the "
+"project has moved to using Apache Maven. Please be sure to follow the steps "
+"in this section closely."
+msgstr "打包方式的变化。如果你之前创建过CloudStack软件包，你会意识到自从该项目开始使用Apache Maven，这个步骤发生了很大变化。请一定要密切关注本节中的步骤。"
+
+# a058ef55f9d544c59a3d9167d13e55f7
+#: ../../building_from_source.rst:348
+msgid "Generating RPMS"
+msgstr "生成RPM包"
+
+# b30e84d7601d4d81a71bcd33b034f374
+#: ../../building_from_source.rst:350
+msgid ""
+"Now that we have the prerequisites and source, you will cd to the "
+"`packaging/centos63/` directory."
+msgstr "现在我们已经满足先决条件和源码，然后进入 `packaging/centos63/` 目录。"
+
+# 9f33b2b9cbfd4211ab425cf8bb35a9d9
+#: ../../building_from_source.rst:357
+msgid "Generating RPMs is done using the ``package.sh`` script:"
+msgstr "使用 ``package.sh`` 脚本生成RPM包："
+
+# b91a6668f8414cfaac447e79705af239
+#: ../../building_from_source.rst:363
+msgid ""
+"That will run for a bit and then place the finished packages in "
+"``dist/rpmbuild/RPMS/x86_64/``."
+msgstr "这会需要一些时间，生成的软件包会在 ``dist/rpmbuild/RPMS/x86_64/`` 目录中。"
+
+# 027abcc96e1144cfbd6511ca4c31b35d
+#: ../../building_from_source.rst:366
+msgid "You should see the following RPMs in that directory:"
+msgstr "你应该看到目录中的RPM包："
+
+# fe5a036719b948639b86eb45194cbb45
+#: ../../building_from_source.rst:380
+msgid "Creating a yum repo"
+msgstr "创建yum仓库"
+
+# fa6516e0378d40b8b6571d4f92e5cf60
+#: ../../building_from_source.rst:382
+msgid ""
+"While RPMs is a useful packaging format - it's most easily consumed from Yum"
+" repositories over a network. The next step is to create a Yum Repo with the"
+" finished packages:"
+msgstr "RPMs是一个有用的包装格式 - 通过网络上YUM仓库来使用是非常简单的。下一步是使用这些软件包创建YUM仓库："
+
+# 7db0ebdd90574721be216ccf32b72064
+#: ../../building_from_source.rst:398
+msgid ""
+"The files and directories within ``~/tmp/repo`` can now be uploaded to a web"
+" server and serve as a yum repository."
+msgstr "``~/tmp/repo`` 中的文件和目录现在可以上传到WEB服务器中作为YUM仓库。"
+
+# 34af5e2901ba47ad90a764c39024011a
+#: ../../building_from_source.rst:403
+msgid "Configuring your systems to use your new yum repository"
+msgstr "配置你的系统使用新的yum仓库"
+
+# 3e7e415e4d0f430b8eeb67194f885455
+#: ../../building_from_source.rst:405
+msgid ""
+"Now that your yum repository is populated with RPMs and metadata we need to "
+"configure the machines that need to install CloudStack. Create a file named "
+"``/etc/yum.repos.d/cloudstack.repo`` with this information:"
+msgstr "现在你的yum仓库中拥有了RPM包和元数据，我们为需要安装CloudStack的机器创建一个名为``/etc/yum.repos.d/cloudstack.repo``的文件，内容如下："
+
+# 16a2be281d5d4d11bdb334ea963026db
+#: ../../building_from_source.rst:417
+msgid ""
+"Completing this step will allow you to easily install CloudStack on a number"
+" of machines across the network."
+msgstr "完成这一步，您可以轻松地在整个网络中的机器上安装CloudStack。"
+
+# 592481f4523641afa7fb8b6ef7a582c3
+#: ../../building_from_source.rst:422
+msgid "Building Non-OSS"
+msgstr "编译 Non-OSS"
+
+# 056563e7eea94421b05d5fcd09befd25
+#: ../../building_from_source.rst:424
+msgid ""
+"If you need support for the VMware, NetApp, F5, NetScaler, SRX, or any other"
+" non-Open Source Software (nonoss) plugins, you'll need to download a few "
+"components on your own and follow a slightly different procedure to build "
+"from source."
+msgstr "如果你需要支持VMware，NetAPP，F5，NetScaler，SRX或其他非开源软件(nonoss)插件。你需要下载一些独立的组件并遵循从源代码构建稍微不同的过程。"
+
+# f6587f3c5b644126b1ed2229b15c648b
+#: ../../building_from_source.rst:430
+msgid ""
+"Some of the plugins supported by CloudStack cannot be distributed with "
+"CloudStack for licensing reasons. In some cases, some of the required "
+"libraries/JARs are under a proprietary license. In other cases, the required"
+" libraries may be under a license that's not compatible with `Apache's "
+"licensing guidelines for third-party products "
+"<http://www.apache.org/legal/resolved.html#category-x>`_."
+msgstr "因为许可的问题，一些CloudStack支持的插件不能与CloudStack一起发行。一些原因是，所需要的一些库或JAR文件都有专用的许可。另外一些是因为所需要第三方产品库的许可证不能与Apache的许可相兼容，见`针对第三方产品的Apache许可指南 <http://www.apache.org/legal/resolved.html#category-x>`_."
+
+# bc2bb0c113ac453e9f9b4468b91f1139
+#: ../../building_from_source.rst:437
+msgid ""
+"To build the Non-OSS plugins, you'll need to have the requisite JARs "
+"installed under the ``deps`` directory."
+msgstr "为了编译NON-OSS插件，你需要安装必要的JAR在``deps`` 目录中。"
+
+# a59479563c7742e49beb8e5ecb8efba1
+#: ../../building_from_source.rst:440
+msgid ""
+"Because these modules require dependencies that can't be distributed with "
+"CloudStack you'll need to download them yourself. Links to the most recent "
+"dependencies are listed on the `*How to build CloudStack* "
+"<https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack>`_"
+" page on the wiki."
+msgstr "由于这些模块需要的依赖项不能和CloudStack一起发行，你需要自行下载。最新的依赖项都列在wiki页面中：`*如何编译CloudStack* <https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack>`_"
+
+# d9d9d34be2604c18a3b9107dbf384181
+#: ../../building_from_source.rst:446
+msgid ""
+"You may also need to download `vhd-util "
+"<http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_, which was "
+"removed due to licensing issues. You'll copy vhd-util to the "
+"``scripts/vm/hypervisor/xenserver/`` directory."
+msgstr "你可能还需要下载`vhd-util <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_, 也是由于授权问题而被移除。 复制vhd-util到该目录： ``scripts/vm/hypervisor/xenserver/``."
+
+# bfbd7215ff0345f183a7946f620b1368
+#: ../../building_from_source.rst:451
+msgid ""
+"Once you have all the dependencies copied over, you'll be able to build "
+"CloudStack with the ``noredist`` option:"
+msgstr "一旦你复制过来所有的依赖项，你就可以开始使用 ``noredist`` 选项编译CloudStack了。 "
+
+# 252d45f71b814e409bdd693e44584f8e
+#: ../../building_from_source.rst:459
+msgid ""
+"Once you've built CloudStack with the ``noredist`` profile, you can package "
+"it using the `“Building RPMs from Source” <#building-rpms-from-source>`_ or "
+"`“Building DEB packages” <#building-deb-packages>`_ instructions."
+msgstr "一旦你创建了CloudStack的 ``noredist`` 配置文件，你可以使用 `“从源码编译RPM包” <#building-rpms-from-source>`_ 或 `“编译DEB包” <#building-deb-packages>`_ 指令打包。"
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/choosing_deployment_architecture.mo b/source/installguide/locale/zh_CN/LC_MESSAGES/choosing_deployment_architecture.mo
new file mode 100644
index 0000000..4d15f69
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/choosing_deployment_architecture.mo
Binary files differ
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/choosing_deployment_architecture.po b/source/installguide/locale/zh_CN/LC_MESSAGES/choosing_deployment_architecture.po
new file mode 100644
index 0000000..dd200ff
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/choosing_deployment_architecture.po
@@ -0,0 +1,648 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: 2014-06-30 10:22+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 2c4ff27205844a38ba74b1ffed7d0d4c
+#: ../../choosing_deployment_architecture.rst:18
+msgid "Choosing a Deployment Architecture"
+msgstr "选择部署架构"
+
+# b26daf37d81247238775fca77b416ae2
+#: ../../choosing_deployment_architecture.rst:20
+msgid ""
+"The architecture used in a deployment will vary depending on the size and "
+"purpose of the deployment. This section contains examples of deployment "
+"architecture, including a small-scale deployment useful for test and trial "
+"deployments and a fully-redundant large-scale setup for production "
+"deployments."
+msgstr "部署CloudStack的具体架构会因规模及用途的不同而变化。这一章节会包含一些典型的部署构架：用于测试和试验的小型架构，以及用于生产环境的大型全冗余架构。"
+
+# 2f09e208c05a4a5aa8f3c9f87ed50c25
+#: ../../choosing_deployment_architecture.rst:28
+msgid "Small-Scale Deployment"
+msgstr "小型部署"
+
+# 068dcc56cbd24a0083450026b9402fd6
+#: ../../choosing_deployment_architecture.rst:30
+msgid "|Small-Scale Deployment|"
+msgstr "|Small-Scale Deployment|"
+
+# 97e93e20540547229fc5d499cd5d3fc5
+#: ../../choosing_deployment_architecture.rst:32
+msgid ""
+"This diagram illustrates the network architecture of a small-scale "
+"CloudStack deployment."
+msgstr "这个图演示了CloudStack在小型部署时的网络结构。"
+
+# d0e9d1cd6d02485fbb7569bbcac7691f
+#: ../../choosing_deployment_architecture.rst:35
+msgid ""
+"A firewall provides a connection to the Internet. The firewall is configured"
+" in NAT mode. The firewall forwards HTTP requests and API calls from the "
+"Internet to the Management Server. The Management Server resides on the "
+"management network."
+msgstr "防火墙提供了到Internet的连接.此防火墙被配置成NAT模式，它会将来自Internet的HTTP访问和API调用转发到管理服务器。而管理服务器的网络属于管理网络。"
+
+# 3a9520fd64a74db8b3fc06b9204f08a2
+#: ../../choosing_deployment_architecture.rst:40
+msgid "A layer-2 switch connects all physical servers and storage."
+msgstr "一个二层交换机连接所有的物理服务器和存储服务器。"
+
+# cd028d62b82f44ffbe0173ee7583fdee
+#: ../../choosing_deployment_architecture.rst:42
+msgid ""
+"A single NFS server functions as both the primary and secondary storage."
+msgstr "单一的NFS服务器需要能同时提供主存储和辅助存储。"
+
+# de231b4108f546bc9a6ce6fc4468768c
+#: ../../choosing_deployment_architecture.rst:45
+msgid "The Management Server is connected to the management network."
+msgstr "管理服务器连接至管理网络"
+
+# 361b0a48cf54455a94238a38750ee7b9
+#: ../../choosing_deployment_architecture.rst:49
+msgid "Large-Scale Redundant Setup"
+msgstr "大规模冗余设置"
+
+# 38cdbfb68cca4fd8bc4df9bc1ecd694a
+#: ../../choosing_deployment_architecture.rst:51
+msgid "|Large-Scale Redundant Setup|"
+msgstr "|Large-Scale Redundant Setup|"
+
+# 0933dd6019474cfc97b03f67506bc999
+#: ../../choosing_deployment_architecture.rst:53
+msgid ""
+"This diagram illustrates the network architecture of a large-scale "
+"CloudStack deployment."
+msgstr "这个图演示了CloudStack在大规模部署时的网络结构。"
+
+# e3f81067d12242558eaf4684bb364861
+#: ../../choosing_deployment_architecture.rst:56
+msgid ""
+"A layer-3 switching layer is at the core of the data center. A router "
+"redundancy protocol like VRRP should be deployed. Typically high-end core "
+"switches also include firewall modules. Separate firewall appliances may "
+"also be used if the layer-3 switch does not have integrated firewall "
+"capabilities. The firewalls are configured in NAT mode. The firewalls "
+"provide the following functions:"
+msgstr "三层交换层处于数据机房的核心位置。应该部署类似VRRP的冗余路由协议实现设备热备份。通常，高端的核心交换机上包含防火墙模块。如果三层交换机上没有集成防火墙功能，也可以使用独立防火墙设备。防火墙一般会配置成NAT模式，它能提供如下功能："
+
+# a68bb7cb39bd42afa4d9e29f84fa3457
+#: ../../choosing_deployment_architecture.rst:63
+msgid ""
+"Forwards HTTP requests and API calls from the Internet to the Management "
+"Server. The Management Server resides on the management network."
+msgstr "将来自Internet的HTTP访问和API调用转发到管理节点服务器。管理服务器的网络属于管理网络."
+
+# 69f7f256ee7341c98affe498692cd667
+#: ../../choosing_deployment_architecture.rst:67
+msgid ""
+"When the cloud spans multiple zones, the firewalls should enable site-to-"
+"site VPN such that servers in different zones can directly reach each other."
+msgstr "当云跨越多个区域（Zone）时，防火墙之间应该启用site-to-site VPN，以便让不同区域中的服务器之间可以直接互通。"
+
+# b779613fe6004e40bb248aaeb76d8bc3
+#: ../../choosing_deployment_architecture.rst:71
+msgid ""
+"A layer-2 access switch layer is established for each pod. Multiple switches"
+" can be stacked to increase port count. In either case, redundant pairs of "
+"layer-2 switches should be deployed."
+msgstr "layer-2的接入交换层连接到每个提供点（POD），也可以用多个交换机堆叠来增加端口数量。无论哪种情况下，都应该部署冗余的二层交换机。"
+
+# 2032fc16630e41529475a4622c4fb9a2
+#: ../../choosing_deployment_architecture.rst:75
+msgid ""
+"The Management Server cluster (including front-end load balancers, "
+"Management Server nodes, and the MySQL database) is connected to the "
+"management network through a pair of load balancers."
+msgstr "管理服务器集群(包括前端负载均衡节点，管理节点及MYSQL数据库节点)通过两个负载均衡节点接入管理网络。"
+
+# cbcfb563ab554774b485b977d456e814
+#: ../../choosing_deployment_architecture.rst:79
+msgid "Secondary storage servers are connected to the management network."
+msgstr "辅助存储服务器接入管理网络。"
+
+# ed99b388e7464d338ce1e290c13e3e7b
+#: ../../choosing_deployment_architecture.rst:81
+msgid ""
+"Each pod contains storage and computing servers. Each storage and computing "
+"server should have redundant NICs connected to separate layer-2 access "
+"switches."
+msgstr "每一个机柜提供点（POD）包括存储和计算节点服务器。每一个存储和计算节点服务器都需要有冗余网卡连接到不同的 layer-2 接入交换机上。"
+
+# 741500f6260941e79f28d53a5986fc43
+#: ../../choosing_deployment_architecture.rst:87
+msgid "Separate Storage Network"
+msgstr "独立的存储网络"
+
+# 1ef36fbcddb24180bf412b41f03bcbc4
+#: ../../choosing_deployment_architecture.rst:89
+msgid ""
+"In the large-scale redundant setup described in the previous section, "
+"storage traffic can overload the management network. A separate storage "
+"network is optional for deployments. Storage protocols such as iSCSI are "
+"sensitive to network delays. A separate storage network ensures guest "
+"network traffic contention does not impact storage performance."
+msgstr "在前面章节中，提及了大规模冗余部署，存储的数据流量过大可能使得管理网络过载。部署时可选择将存储网络分离出来。存储协议如iSCSI，对网络延迟非常敏感。独立的存储网络能够使其不受来宾网络流量波动的影响。"
+
+# b813bc439dea4888b8dddbc9122afe9a
+#: ../../choosing_deployment_architecture.rst:97
+msgid "Multi-Node Management Server"
+msgstr "多节点管理服务器"
+
+# 35591778160a4e25a505e5dcd507198f
+#: ../../choosing_deployment_architecture.rst:99
+msgid ""
+"The CloudStack Management Server is deployed on one or more front-end "
+"servers connected to a single MySQL database. Optionally a pair of hardware "
+"load balancers distributes requests from the web. A backup management server"
+" set may be deployed using MySQL replication at a remote site to add DR "
+"capabilities."
+msgstr "CloudStack管理服务器可以部署一个或多个前端服务器并连接单一的MySQL数据库。可视需求使用一对硬件负载均衡对Web请求进行分流。另一备份管理节点可使用远端站点的MySQL复制数据以增加灾难恢复能力。"
+
+# faff12b3c7c142f59b2a12926ab7c9f7
+#: ../../choosing_deployment_architecture.rst:105
+msgid "|Multi-Node Management Server|"
+msgstr "|Multi-Node Management Server|"
+
+# ee629ff1681e4b38bfddfac64b76c7d6
+#: ../../choosing_deployment_architecture.rst:107
+msgid "The administrator must decide the following."
+msgstr "系统管理人员必须决定如下事项："
+
+# 3e9822c46e86433cb6d9f4ecbbacda1e
+#: ../../choosing_deployment_architecture.rst:109
+msgid "Whether or not load balancers will be used."
+msgstr "是否需要使用负载均衡器。"
+
+# ab341a95aac3496581377672055b241d
+#: ../../choosing_deployment_architecture.rst:111
+msgid "How many Management Servers will be deployed."
+msgstr "需要部署多少台管理节点服务器。"
+
+# 2dbc1c3c22db42958e785984f5ef93e4
+#: ../../choosing_deployment_architecture.rst:113
+msgid ""
+"Whether MySQL replication will be deployed to enable disaster recovery."
+msgstr "如何部署MYSQL复制以便启用灾难恢复。"
+
+# 4858e0bbf6f14d6b990948aacc6e0b74
+#: ../../choosing_deployment_architecture.rst:118
+msgid "Multi-Site Deployment"
+msgstr "多站点部署"
+
+# 31bb0ebb88974050a79e6f0aec7c6778
+#: ../../choosing_deployment_architecture.rst:120
+msgid ""
+"The CloudStack platform scales well into multiple sites through the use of "
+"zones. The following diagram shows an example of a multi-site deployment."
+msgstr "运用CloudStack的区域技术可以很容易的将其扩散为多站点模式。下图就显示了一个多站点部署的示例"
+
+# 72c760ffa57b48a0a2ce31a545672acb
+#: ../../choosing_deployment_architecture.rst:124
+msgid "|Example Of A Multi-Site Deployment|"
+msgstr "|Example Of A Multi-Site Deployment|"
+
+# 3680185677f54baeb03396c0c6e6b91b
+#: ../../choosing_deployment_architecture.rst:126
+msgid ""
+"Data Center 1 houses the primary Management Server as well as zone 1. The "
+"MySQL database is replicated in real time to the secondary Management Server"
+" installation in Data Center 2."
+msgstr "在数据中心1内有主管理节点和区域1。MySQL数据库实时复制到数据中心2内的辅助管理节点中。"
+
+# 44f2f283a3dd4992ba843cd1a6ad29b9
+#: ../../choosing_deployment_architecture.rst:130
+msgid "|Separate Storage Network|"
+msgstr "|Separate Storage Network|"
+
+# 85a51dc8edc24f37b0483d2b5d46a1dd
+#: ../../choosing_deployment_architecture.rst:132
+msgid ""
+"This diagram illustrates a setup with a separate storage network. Each "
+"server has four NICs, two connected to pod-level network switches and two "
+"connected to storage network switches."
+msgstr "这个图展示了使用独立存储网络的设计。每一个物理服务器有四块网卡，其中两块连接到提供点级别的交换机，而另外两块网卡连接到用于存储网络的交换机。"
+
+# 56c244202346479080d0963357ce6a01
+#: ../../choosing_deployment_architecture.rst:136
+msgid "There are two ways to configure the storage network:"
+msgstr "有两种方式配置存储网络："
+
+# 774def02c93d4401aa0961c701e2a346
+#: ../../choosing_deployment_architecture.rst:138
+msgid ""
+"Bonded NIC and redundant switches can be deployed for NFS. In NFS "
+"deployments, redundant switches and bonded NICs still result in one network "
+"(one CIDR block+ default gateway address)."
+msgstr "为NFS配置网卡绑定和冗余交换机。在NFS部署中，冗余的交换机和网卡绑定仍然处于同一网络。(同一个CIDR 段 + 默认网关地址)"
+
+# 42c329aa74164a2a91b1cb061a594df0
+#: ../../choosing_deployment_architecture.rst:142
+msgid ""
+"iSCSI can take advantage of two separate storage networks (two CIDR blocks "
+"each with its own default gateway). Multipath iSCSI client can failover and "
+"load balance between separate storage networks."
+msgstr "iSCSI能同时利用两个独立的存储网络(两个拥有各自默认网关的不同CIDR段)。支持iSCSI多路径的客户端能在两个独立的存储网络中实现故障切换和负载均衡。"
+
+# 709e7b87aca14df39855bc39efbde210
+#: ../../choosing_deployment_architecture.rst:146
+msgid "|NIC Bonding And Multipath I/O|"
+msgstr "|NIC Bonding And Multipath I/O|"
+
+# b9cd0b7d1c614f24855cf4e9755e9070
+#: ../../choosing_deployment_architecture.rst:148
+msgid ""
+"This diagram illustrates the differences between NIC bonding and Multipath "
+"I/O (MPIO). NIC bonding configuration involves only one network. MPIO "
+"involves two separate networks."
+msgstr "此图展示了网卡绑定与多路径IO(MPIO)之间的区别，网卡绑定的配置仅涉及一个网段，MPIO涉及两个独立的网段。"
+
+# 36df70c98ae746549452fa36e1ca87e3
+#: ../../choosing_deployment_architecture.rst:154
+msgid "Choosing a Hypervisor"
+msgstr "选择Hypervisor"
+
+# f236302a8db24c13a141a20573581062
+#: ../../choosing_deployment_architecture.rst:156
+msgid ""
+"CloudStack supports many popular hypervisors. Your cloud can consist "
+"entirely of hosts running a single hypervisor, or you can use multiple "
+"hypervisors. Each cluster of hosts must run the same hypervisor."
+msgstr "CloudStack支持多种流行的Hypervisor，你可以在所有的主机上使用一种，也可以使用不同的Hypervisor，但在同一个群集内的主机必须使用相同的Hypervisor。"
+
+# ebd33f6eb3b64168ac6543a23dac1afd
+#: ../../choosing_deployment_architecture.rst:160
+msgid ""
+"You might already have an installed base of nodes running a particular "
+"hypervisor, in which case, your choice of hypervisor has already been made. "
+"If you are starting from scratch, you need to decide what hypervisor "
+"software best suits your needs. A discussion of the relative advantages of "
+"each hypervisor is outside the scope of our documentation. However, it will "
+"help you to know which features of each hypervisor are supported by "
+"CloudStack. The following table provides this information."
+msgstr "你可能已经安装并运行了特定的hypervisor节点，在这种情况下，你的Hypervisor选择已经确定了。如果还处于初步规划阶段，那么就需要决定那种Hypervisor能切合你的需求。各种Hypervisor的利弊讨论不在本文档之列。但无论如何，CloudStack可以支持每种Hypervisor的那些功能的详细信息还是能够帮到你的。下面的表格就提供了这些信息："
+
+# 6095a38fe5eb4ce7acbb1c158db98231
+#: ../../choosing_deployment_architecture.rst:169
+msgid "Feature"
+msgstr "功能特点"
+
+# 4a7ee7865ca548379bf859592ddb19f8
+#: ../../choosing_deployment_architecture.rst:169
+msgid "XenServer 6.0.2"
+msgstr "XenServer 6.0.2"
+
+# 09198080ae1c486ebd9470b6c99b387f
+#: ../../choosing_deployment_architecture.rst:169
+msgid "vSphere 4.1/5.0"
+msgstr "vSphere 4.1/5.0"
+
+# 1870d6331a364df4a087d4f6f3368ab9
+#: ../../choosing_deployment_architecture.rst:169
+msgid "KVM - RHEL 6.2"
+msgstr "KVM - RHEL 6.2"
+
+# d3c9ece508424f81897e3280902508b0
+#: ../../choosing_deployment_architecture.rst:169
+msgid "Bare Metal"
+msgstr "裸设备"
+
+# 970a9d80bc134222b3218d026302891b
+#: ../../choosing_deployment_architecture.rst:171
+msgid "Network Throttling"
+msgstr "网络限速"
+
+# 4fec162cda76433cb982cfc313dcdbe6
+# 1f8cc79d716140189e60a08ebf4687bf
+# 91a8ee2ecce64c71b1eecf843f67deed
+# 2989a051bcd34ea987938c8a7e30b013
+# 9cbaf270ddd6408c8101622f74c7b266
+# 12e9d689493a44049c4874afa2dbadd3
+# f9a1370f394c49a8967531ffb6e1b423
+# 91b5581980864170b9693104a2f61d3c
+# c231f1df091e4ceeb60e89845db5f10b
+# 2852be6028ec46659ae8bf5cac551b29
+# 755b64ababd34e04b82a384d357fc6e4
+# 3e558e80e7bc4878b80739772dfb4a06
+# 227928dd0cf1488b873ce21a5b4842d2
+# 6ca963616f6a42098fed6641c7711e35
+# f36be7f0603b44f5aa77a248d3a97e5e
+# 996c7caeb3384d93be1ce49f570cb8ce
+# 5d9e3cabc113463e8b6c3fb75b182456
+# 159c98b022e14645bef4499b7c0c0235
+# f55810d73d0246b38a1495e4af5ec4bc
+# 0867769fdd5046d0832752148daf908d
+# c25243683e1449f0b89ee3d3b1881025
+# 87e8128b3ae84f228c87a33a892a23ec
+# 9fc4d908264143e682ddec06aaafe205
+# 0bb1aaf47c0543659d4e09d9f91cd185
+#: ../../choosing_deployment_architecture.rst:171
+#: ../../choosing_deployment_architecture.rst:171
+#: ../../choosing_deployment_architecture.rst:172
+#: ../../choosing_deployment_architecture.rst:172
+#: ../../choosing_deployment_architecture.rst:173
+#: ../../choosing_deployment_architecture.rst:173
+#: ../../choosing_deployment_architecture.rst:173
+#: ../../choosing_deployment_architecture.rst:174
+#: ../../choosing_deployment_architecture.rst:174
+#: ../../choosing_deployment_architecture.rst:174
+#: ../../choosing_deployment_architecture.rst:175
+#: ../../choosing_deployment_architecture.rst:175
+#: ../../choosing_deployment_architecture.rst:175
+#: ../../choosing_deployment_architecture.rst:175
+#: ../../choosing_deployment_architecture.rst:176
+#: ../../choosing_deployment_architecture.rst:176
+#: ../../choosing_deployment_architecture.rst:177
+#: ../../choosing_deployment_architecture.rst:177
+#: ../../choosing_deployment_architecture.rst:177
+#: ../../choosing_deployment_architecture.rst:180
+#: ../../choosing_deployment_architecture.rst:180
+#: ../../choosing_deployment_architecture.rst:180
+#: ../../choosing_deployment_architecture.rst:181
+#: ../../choosing_deployment_architecture.rst:181
+msgid "Yes"
+msgstr "是"
+
+# 3cb5cc62ebb54cae80640aabea621255
+# 86b2047f134d4b8a8af64d25bea97315
+# 5ca5465c16114b58ab0aaaf014969e31
+# fc76b86618fb433780039d59ce9cf302
+# 0cd9cc48eb624d829d99923f98ab2d5f
+# 748e481678464f27b851cb867b2d78b2
+# 1215b1b0f7e44472adcf474168869721
+# db4ae4f299a14dd097a941a94920c9c0
+# c8744cfc965e4794935294c98d6aae14
+#: ../../choosing_deployment_architecture.rst:171
+#: ../../choosing_deployment_architecture.rst:172
+#: ../../choosing_deployment_architecture.rst:172
+#: ../../choosing_deployment_architecture.rst:178
+#: ../../choosing_deployment_architecture.rst:178
+#: ../../choosing_deployment_architecture.rst:178
+#: ../../choosing_deployment_architecture.rst:179
+#: ../../choosing_deployment_architecture.rst:179
+#: ../../choosing_deployment_architecture.rst:181
+msgid "No"
+msgstr "否"
+
+# 63afe958cfa44895bc62e896586ee40f
+# 199baf6fe3444dd48443901731e0ad62
+# ece293ab433448bd95772d3de229bcf6
+# fc04754e8df54fd7b280d1e2d9973a9f
+# 258bacf04ab349cc80b6f7d9ec2c0d7b
+# 9d861363c0d54ccb831b9a52f67834f6
+# be8b43bee82341ce8c679239ccd5e71e
+# 89c3130f25d348d1abc3081a0a033720
+# cfcd30df2f204091be6335cf2b116e44
+#: ../../choosing_deployment_architecture.rst:171
+#: ../../choosing_deployment_architecture.rst:173
+#: ../../choosing_deployment_architecture.rst:174
+#: ../../choosing_deployment_architecture.rst:176
+#: ../../choosing_deployment_architecture.rst:177
+#: ../../choosing_deployment_architecture.rst:178
+#: ../../choosing_deployment_architecture.rst:179
+#: ../../choosing_deployment_architecture.rst:180
+#: ../../choosing_deployment_architecture.rst:181
+msgid "N/A"
+msgstr "无"
+
+# 6f727e19a82c4be4b3d885ee30c3bd5e
+#: ../../choosing_deployment_architecture.rst:172
+msgid "Security groups in zones that use basic networking"
+msgstr "在区域内用于基本网络模式的安全组"
+
+# 97e1ffe107c74bd4846cf646d1b9543e
+#: ../../choosing_deployment_architecture.rst:173
+msgid "iSCSI"
+msgstr "iSCSI"
+
+# 2ea33b37f3de4e91b56a3f97d94654b7
+#: ../../choosing_deployment_architecture.rst:174
+msgid "FibreChannel"
+msgstr "光纤通道"
+
+# b1c9732e6c15420a87ad6e0dd96052ef
+#: ../../choosing_deployment_architecture.rst:175
+msgid "Local Disk"
+msgstr "本地磁盘"
+
+# 490c55011c344c2cad34b7ed6f88fade
+#: ../../choosing_deployment_architecture.rst:176
+msgid "HA"
+msgstr "高可用"
+
+# 1aa446ba2cf44112bb3b742a8435bc70
+#: ../../choosing_deployment_architecture.rst:176
+msgid "Yes (Native)"
+msgstr "是（原生）"
+
+# d46bd32966d54085a61343d211a063d1
+#: ../../choosing_deployment_architecture.rst:177
+msgid "Snapshots of local disk"
+msgstr "本地磁盘快照"
+
+# 954f1dc69e8945f9a3e8d1363d10feb9
+#: ../../choosing_deployment_architecture.rst:178
+msgid "Local disk as data disk"
+msgstr "用本地盘作为数据磁盘"
+
+# e31cc2bd3ce340ae9976c8166beb44cb
+#: ../../choosing_deployment_architecture.rst:179
+msgid "Work load balancing"
+msgstr "工作负载均衡"
+
+# 9b6952490df5422e8c9dc96b96e06914
+#: ../../choosing_deployment_architecture.rst:179
+msgid "DRS"
+msgstr "DRS-分布式资源调度"
+
+# 276af5d2a4d94ebdb3319fbbe859a74e
+#: ../../choosing_deployment_architecture.rst:180
+msgid "Manual live migration of VMs from host to host"
+msgstr "手工在主机之间进行虚拟机的热迁移"
+
+# a6ffb0bdac29407e86b5edc37f932c8c
+#: ../../choosing_deployment_architecture.rst:181
+msgid ""
+"Conserve management traffic IP address by using link local network to "
+"communicate with virtual router"
+msgstr "使用本地链路与虚拟路由器（VR）直接通讯来保护管理网络的IP流量"
+
+# eb354934ad0c4f1e92a9aa56494e083e
+#: ../../choosing_deployment_architecture.rst:186
+msgid "Best Practices"
+msgstr "最佳实践"
+
+# 42fc8f2d41c548c0b39e0f03816bd496
+#: ../../choosing_deployment_architecture.rst:188
+msgid ""
+"Deploying a cloud is challenging. There are many different technology "
+"choices to make, and CloudStack is flexible enough in its configuration that"
+" there are many possible ways to combine and configure the chosen "
+"technology. This section contains suggestions and requirements about cloud "
+"deployments."
+msgstr "部署云计算服务是一项挑战。这需要在很多不同的技术之间做出选择，CLOUDSTACK以其配置灵活性可以使用很多种方法将不同的技术进行整合和配置。这个章节包含了一些在云计算部署中的建议及需求。"
+
+# 68e273347ac34898aaaddc10df7c5d4d
+#: ../../choosing_deployment_architecture.rst:194
+msgid ""
+"These should be treated as suggestions and not absolutes. However, we do "
+"encourage anyone planning to build a cloud outside of these guidelines to "
+"seek guidance and advice on the project mailing lists."
+msgstr "这些内容应该被视为建议而不是绝对性的。然而，我们鼓励想要部署云计算的朋友们，除了这些建议内容之外，最好从CLOUDSTACK的项目邮件列表中获取更多建议指南性内容。"
+
+# ba21db935b174028b86bb1e6442669d7
+#: ../../choosing_deployment_architecture.rst:200
+msgid "Process Best Practices"
+msgstr "实施最佳实践"
+
+# cefb1b21faf04019abc16cccabd19d30
+#: ../../choosing_deployment_architecture.rst:202
+msgid ""
+"A staging system that models the production environment is strongly advised."
+" It is critical if customizations have been applied to CloudStack."
+msgstr "强烈建议在系统部署至生产环境之前，有一个完全模拟生产环境的集成系统。对于已经在CloudStack中做了自定义修改的系统来说，更为重要了。"
+
+# ea64ea072f3746d2b3463aafdc14532b
+#: ../../choosing_deployment_architecture.rst:206
+msgid ""
+"Allow adequate time for installation, a beta, and learning the system. "
+"Installs with basic networking can be done in hours. Installs with advanced "
+"networking usually take several days for the first attempt, with complicated"
+" installations taking longer. For a full production system, allow at least "
+"4-8 weeks for a beta to work through all of the integration issues. You can "
+"get help from fellow users on the cloudstack-users mailing list."
+msgstr "应该为安装，学习和测试系统预留充足的时间。简单网络模式的安装可以在几个小时内完成。但首次尝试安装高级网络模式通常需要花费几天的时间，完全安装则需要更长的时间。正式生产环境上线前，通常需要4-8周用以排除集成过程中的问题，你也可从cloudstack-users的邮件列表里得到更多帮助。"
+
+# 67f17d3accb24ff48c29830624f9a607
+#: ../../choosing_deployment_architecture.rst:216
+msgid "Setup Best Practices"
+msgstr "最佳实践安装"
+
+# 81402254fd3a4dd888d02f4a884a1d0b
+#: ../../choosing_deployment_architecture.rst:218
+msgid ""
+"Each host should be configured to accept connections only from well-known "
+"entities such as the CloudStack Management Server or your network monitoring"
+" software."
+msgstr "每一个主机都应该配置为只接受已知设备的连接，如CLOUDSTACK管理节点或相关的网络监控软件。"
+
+# 7481cf7faac5484b8339bb8e4d75b6c8
+#: ../../choosing_deployment_architecture.rst:222
+msgid ""
+"Use multiple clusters per pod if you need to achieve a certain switch "
+"density."
+msgstr "如果需要达到一定的高密度，可以在每个机柜提供点里部署多个集群。"
+
+# fd7badb077d04065b340d43fd79a4eec
+#: ../../choosing_deployment_architecture.rst:225
+msgid ""
+"Primary storage mountpoints or LUNs should not exceed 6 TB in size. It is "
+"better to have multiple smaller primary storage elements per cluster than "
+"one large one."
+msgstr "主存储的挂载点或是LUN不应超过6TB大小。每个集群中使用多个小一些的主存储比只用一个超大主存储的效果要好。"
+
+# 6ed9bc75682247bfbc913cf9df8e21f1
+#: ../../choosing_deployment_architecture.rst:229
+msgid ""
+"When exporting shares on primary storage, avoid data loss by restricting the"
+" range of IP addresses that can access the storage. See \"Linux NFS on Local"
+" Disks and DAS\" or \"Linux NFS on iSCSI\"."
+msgstr "在主存储上输出共享数据时，可用限制访问IP地址的方法避免数据丢失。更多详情，可参考\"Linux NFS on Local Disks and DAS\" \"Linux NFS on iSCSI\"这些章节。 "
+
+# 5e4ab60bb7e7405180895617b9a6efe1
+#: ../../choosing_deployment_architecture.rst:233
+msgid ""
+"NIC bonding is straightforward to implement and provides increased "
+"reliability."
+msgstr "网卡绑定技术可以明显的增加系统的可靠性。"
+
+# ff514643a50b4a478172c6dbe1a9befe
+#: ../../choosing_deployment_architecture.rst:236
+msgid ""
+"10G networks are generally recommended for storage access when larger "
+"servers that can support relatively more VMs are used."
+msgstr "当有大量服务器支持相当多的虚拟机时，推荐在存储访问的网络上采用将10G的带宽。"
+
+# 570bde20d1b84f1ea78c02bab25c0f7d
+#: ../../choosing_deployment_architecture.rst:239
+msgid ""
+"Host capacity should generally be modeled in terms of RAM for the guests. "
+"Storage and CPU may be overprovisioned. RAM may not. RAM is usually the "
+"limiting factor in capacity designs."
+msgstr "主机可创建的虚拟机的能力，主要取决于提供给客户虚拟机的内存。因为主机的存储和CPU均可超配，但内存却基本不可以。所以内存是在系统容量设计时的主要限制因素。"
+
+# 1910d3f68a634d0fb53fdd5f4bde6b8e
+#: ../../choosing_deployment_architecture.rst:243
+msgid ""
+"(XenServer) Configure the XenServer dom0 settings to allocate more memory to"
+" dom0. This can enable XenServer to handle larger numbers of virtual "
+"machines. We recommend 2940 MB of RAM for XenServer dom0. For instructions "
+"on how to do this, see `http://support.citrix.com/article/CTX126531 "
+"<http://support.citrix.com/article/CTX126531>`_. The article refers to "
+"XenServer 5.6, but the same information applies to XenServer 6.0."
+msgstr "(XenServer)可以为Xenserver的dom0分配更多的内存来让其支持更多的虚拟机。我们推荐为dom0设置的内存数值为2940 MB。至于具体操作，可以参见如下URL：`http://support.citrix.com/article/CTX126531 <http://support.citrix.com/article/CTX126531>`_。这篇文章可同时适用于XenServer 5.6和6.0版本。"
+
+# c33ddae286b44338ab9b330c918e8e39
+#: ../../choosing_deployment_architecture.rst:254
+msgid "Maintenance Best Practices"
+msgstr "维护最佳实践"
+
+# ae92610bc5164452b9e9527e5f3a8eec
+#: ../../choosing_deployment_architecture.rst:256
+msgid ""
+"Monitor host disk space. Many host failures occur because the host's root "
+"disk fills up from logs that were not rotated adequately."
+msgstr "监视主机的磁盘空间。很多主机故障的原因都是日志将主机的硬盘空间占满导致的。"
+
+# 731977493e6d46559ca32f493189b8f4
+#: ../../choosing_deployment_architecture.rst:259
+msgid ""
+"Monitor the total number of VM instances in each cluster, and disable "
+"allocation to the cluster if the total is approaching the maximum that the "
+"hypervisor can handle. Be sure to leave a safety margin to allow for the "
+"possibility of one or more hosts failing, which would increase the VM load "
+"on the other hosts as the VMs are redeployed. Consult the documentation for "
+"your chosen hypervisor to find the maximum permitted number of VMs per host,"
+" then use CloudStack global configuration settings to set this as the "
+"default limit. Monitor the VM activity in each cluster and keep the total "
+"number of VMs below a safe level that allows for the occasional host "
+"failure. For example, if there are N hosts in the cluster, and you want to "
+"allow for one host in the cluster to be down at any given time, the total "
+"number of VM instances you can permit in the cluster is at most (N-1) \\* "
+"(per-host-limit). Once a cluster reaches this number of VMs, use the "
+"CloudStack UI to disable allocation to the cluster."
+msgstr "要监控每个集群里的虚拟机总量，如果达到了hypervisor所能承受的最大虚拟机数量时，就要禁止向此集群分配虚机。并且，要确定预留一定的安全迁移容量，以防止群集中有主机故障，这将增大其他主机运行虚拟机压力，就像是重新部署一批虚拟机一样。咨询你选择 hypervisor的文档，找到每台主机所能支持的最大虚拟机数量，并将此数值作为默认限制配置在CLOUDSTACK的全局设置里。监控每个群集中虚拟机的活动，保持虚拟机数量在安全线内，以防止偶然的主机故障。例如：如果集群里有N个主机，如果要让集群中一主机在任意时间停机，那么，此集群最多允许的虚拟机数量值为：(N-1) \\* (每宿主机最大虚拟量数量限值)。一旦达到此数量，必须在CLOUDSTACK的UI里禁止向此群集增加新的虚拟机。"
+
+# edcacc73b0b64b318b84f0f38e00e8d9
+#: ../../choosing_deployment_architecture.rst:276
+msgid ""
+"The lack of up-do-date hotfixes can lead to data corruption and lost VMs."
+msgstr "缺乏最新补丁更新可能会导致数据和虚拟机丢失。"
+
+# 07e8bf01dab44bb2b1ab4f52a8be4264
+#: ../../choosing_deployment_architecture.rst:278
+msgid ""
+"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."
+msgstr "确保安装了所有系统补丁供应商提供的所有系统补丁。请随时关注供应商的技术支持渠道，一旦发布补丁，请尽快打上补丁。CloudStack不会跟踪或提醒你安装这些程序。安装最新的补丁对主机至关重要。虚拟化供应商可能不会对过期的系统提供技术支持。"
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/configuration.mo b/source/installguide/locale/zh_CN/LC_MESSAGES/configuration.mo
new file mode 100644
index 0000000..50ae1e6
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/configuration.mo
Binary files differ
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/configuration.po b/source/installguide/locale/zh_CN/LC_MESSAGES/configuration.po
new file mode 100644
index 0000000..cfa5faf
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/configuration.po
@@ -0,0 +1,3249 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: 2014-06-30 10:23+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 8162e4079fb94ebdb46db436be09b2e4
+#: ../../configuration.rst:18
+msgid "Configuring your CloudStack Installation"
+msgstr "配置CloudStack安装"
+
+# b181cecde5914223835b875145432152
+#: ../../configuration.rst:20
+msgid ""
+"This section tells how to add regions, zones, pods, clusters, hosts, "
+"storage, and networks to your cloud. If you are unfamiliar with these "
+"entities, please begin by looking through `*Cloud Infrastructure Concepts* "
+"<http://docs.cloudstack.apache.org/en/latest/concepts.html#cloud-"
+"infrastructure-concepts>`_."
+msgstr "这一章节的内容将会告诉你如何增加地域，区域，提供点，集群，主机，存储和网络。如果你不熟悉这些概念，可以参阅: `*云基础设施的概念* <http://docs.cloudstack.apache.org/en/latest/concepts.html#cloud-infrastructure-concepts>`_."
+
+# 54b40504af90400fa71b9e8b2a0ff779
+#: ../../configuration.rst:27
+msgid "Overview of Provisioning Steps"
+msgstr "安装步骤概述"
+
+# 0985357f77e64604b889f263d397930e
+#: ../../configuration.rst:29
+msgid ""
+"After the Management Server is installed and running, you can add the "
+"compute resources for it to manage. For an overview of how a CloudStack "
+"cloud infrastructure is organized, see `“Cloud Infrastructure Overview” "
+"<http://docs.cloudstack.apache.org/en/latest/concepts.html#cloud-"
+"infrastructure-overview>`_."
+msgstr "当管理节点服务器安装结束并正常运行之后，你可以开始将计算资源池纳入其管理范围。关于CloudStack云计算系统是如何组织构架的，请参阅：`“Cloud Infrastructure Overview” <http://docs.cloudstack.apache.org/en/latest/concepts.html#cloud-infrastructure-overview>`_."
+
+# c51bc6ff615c4c7b924e0cdabbb11db7
+#: ../../configuration.rst:34
+msgid ""
+"To provision the cloud infrastructure, or to scale it up at any time, follow"
+" these procedures:"
+msgstr "准备云基础架构，或是进行扩展时，请遵从如下步骤："
+
+# adf3e4efe0234c6496a1f43d465cd491
+#: ../../configuration.rst:37
+msgid "Define regions (optional). See :ref:`adding-regions`."
+msgstr "定义地域(可选)，参阅 :ref:`adding-regions`。"
+
+# 261036fb021e4c5cb2788a51756216ad
+#: ../../configuration.rst:39
+msgid "Add a zone to the region. See :ref:`adding-a-zone`."
+msgstr "在地域内增加一个区域，参阅 :ref:`adding-a-zone`。"
+
+# dee74c2b0f1a45999f72be907610fd56
+#: ../../configuration.rst:41
+msgid "Add more pods to the zone (optional). See :ref:`adding-a-pod`."
+msgstr "在区域内增一个机柜提供点(可选)。参阅 :ref:`adding-a-pod`。"
+
+# 1196cbbf547c4332aab26253e7429eed
+#: ../../configuration.rst:43
+msgid "Add more clusters to the pod (optional). See :ref:`adding-a-cluster`."
+msgstr "在提供点内增群集(可选)。参阅 :ref:`adding-a-cluster`。"
+
+# f82489ac595141efaffd718950339e04
+#: ../../configuration.rst:45
+msgid "Add more hosts to the cluster (optional). See :ref:`adding-a-host`."
+msgstr "在群集内增加主机(可选)。参阅 :ref:`adding-a-host`。"
+
+# 4597369285a14d2bbaa5aaeee7043950
+#: ../../configuration.rst:47
+msgid "Add primary storage to the cluster. See :ref:`add-primary-storage`."
+msgstr "为群集增加主存储。参阅 :ref:`add-primary-storage`。"
+
+# d5616551e06641f2bfef5c1aa5ad09b8
+#: ../../configuration.rst:49
+msgid "Add secondary storage to the zone. See :ref:`add-secondary-storage`."
+msgstr "为区域增加辅助存储。参阅 :ref:`add-secondary-storage`。"
+
+# 730a702a42a041f0a604685b09ab09b2
+#: ../../configuration.rst:51
+msgid "Initialize and test the new cloud. See :ref:`initialize-and-test`."
+msgstr "初始化并测试云计算环境。参阅 :ref:`initialize-and-test`。"
+
+# 095a8c4cdac64dd2825fe0ea089804f6
+#: ../../configuration.rst:53
+msgid ""
+"When you have finished these steps, you will have a deployment with the "
+"following basic structure:"
+msgstr "当你完成这些步骤以后, 你将部署如下的一个基本结构:"
+
+# bdc17df1e28847748e2b0111f5095ab4
+#: ../../configuration.rst:56
+msgid "|provisioning-overview.png: Conceptual overview of a basic deployment|"
+msgstr "|provisioning-overview.png: Conceptual overview of a basic deployment|"
+
+# bda13ba72d2e4352ad3a1a99d42006c5
+#: ../../configuration.rst:62
+msgid "Adding Regions (optional)"
+msgstr "增加地域(可选)"
+
+# 5ce04786ce7a453faaa361f1cf6e76e0
+#: ../../configuration.rst:64
+msgid ""
+"Grouping your cloud resources into geographic regions is an optional step "
+"when provisioning the cloud. For an overview of regions, see `“About "
+"Regions” <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-"
+"regions>`_."
+msgstr "在部署云的过程中将云资源按地域组织起来是是一个可选的步骤。关于地域的描述，可以参阅 `“关于地域” <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-regions>`_."
+
+# 43d3ccf2438e462083e530a02e77edc4
+#: ../../configuration.rst:70
+msgid "The First Region: The Default Region"
+msgstr "第一个地域：默认地域"
+
+# 3a4d5136ebdf43759e77bd764570aa1f
+#: ../../configuration.rst:72
+msgid ""
+"If you do not take action to define regions, then all the zones in your "
+"cloud will be automatically grouped into a single default region. This "
+"region is assigned the region ID of 1. You can change the name or URL of the"
+" default region by displaying the region in the CloudStack UI and clicking "
+"the Edit button."
+msgstr "如果你没有执行任何操作来定义地域, 那么云环境中所有的资源域都会组织到一个默认的地域里. 这个地域的ID是1。当然，你可以通过CloudStack的WEB UI来编辑此默认地域的名称和URL网址。"
+
+# 1b21128d567445d99c07ff46ba4489ff
+#: ../../configuration.rst:80
+msgid "Adding a Region"
+msgstr "增加一个地域"
+
+# 0a5ed06cff2b46419d89cc8a8bdaf915
+#: ../../configuration.rst:82
+msgid ""
+"Use these steps to add a second region in addition to the default region."
+msgstr "通过下面的步骤来添加除默认地域外的第二个地域."
+
+# 0066030160fb4c0aa122d704f26443ad
+#: ../../configuration.rst:85
+msgid ""
+"Each region has its own CloudStack instance. Therefore, the first step of "
+"creating a new region is to install the Management Server software, on one "
+"or more nodes, in the geographic area where you want to set up the new "
+"region. Use the steps in the Installation guide. When you come to the step "
+"where you set up the database, use the additional command-line flag ``-r "
+"<region_id>`` to set a region ID for the new region. The default region is "
+"automatically assigned a region ID of 1, so your first additional region "
+"might be region 2."
+msgstr "每一个地域都有专属的CloudStack实例。因此，当你要部署一个新的地域时，首先要做的就是在一个或多个节点上安装管理节点服务器。在按照安装指南安装此节点的数据库时，需要在命令行上加上参数 ``-r <region_id>`` 。默认的地域的region ID为1，故而第一个新增地域的region ID应该为2."
+
+# 1d3a3e7282744ac8b1b9fe66fdad230b
+#: ../../configuration.rst:98
+msgid ""
+"By the end of the installation procedure, the Management Server should have "
+"been started. Be sure that the Management Server installation was successful"
+" and complete."
+msgstr "在安装过程结束后, 管理服务器应该是运行状态. 请确保管理服务器安装完成并正确运行."
+
+# 89e04051a9a648f78a6906817c6298c1
+#: ../../configuration.rst:102
+msgid "Now add the new region to region 1 in CloudStack."
+msgstr "现在，开始在 CloudStack内加入一个新的地域。"
+
+# f0bcb3e213ef430881043b8f6b6ec9c2
+#: ../../configuration.rst:104
+msgid ""
+"Log in to CloudStack in the first region as root administrator (that is, log"
+" in to <region.1.IP.address>:8080/client)."
+msgstr "以系统管理员身份登陆CloudStack的第一个地域(登陆<region.1.IP.address>:8080/client)"
+
+# 719d94ee47d34246b6f101d4ec172902
+# ad4e5a27680944198ef6d847d4bb0192
+#: ../../configuration.rst:107 ../../configuration.rst:243
+msgid "In the left navigation bar, click Regions."
+msgstr "在左边的导航栏中，点击区域（为文档翻译中地域的概念，英文为region，下同）"
+
+# fc94a12b43334f31a8dd65b85b0db964
+#: ../../configuration.rst:109
+msgid "Click Add Region. In the dialog, fill in the following fields:"
+msgstr "点击增加地域，在弹出的对话框里，输入以下字段："
+
+# 855f2d8079f54a53848390b3e1e85d00
+#: ../../configuration.rst:111
+msgid ""
+"ID. A unique identifying number. Use the same number you set in the database"
+" during Management Server installation in the new region; for example, 2."
+msgstr "ID--唯一标识号，这个ID与安装管理服务器过程中，设置数据库时的数字相同；例如ID为2。"
+
+# 2dff505d499e42dab8161f715a1c3ba2
+#: ../../configuration.rst:115
+msgid "Name. Give the new region a descriptive name."
+msgstr "名称--为新的地域提供一个描述性名称。"
+
+# 27ad51a0cc564f31b01d1396fd32b638
+#: ../../configuration.rst:117
+msgid ""
+"Endpoint. The URL where you can log in to the Management Server in the new "
+"region. This has the format <region.2.IP.address>:8080/client."
+msgstr "端点--可以登录到新地域中管理服务器的URL。端点的格式为<region.2.IP.address>:8080/client。"
+
+# b3cf11ce84394be6bb0a5cb5c376ce3c
+#: ../../configuration.rst:121
+msgid ""
+"Now perform the same procedure in reverse. Log in to region 2, and add "
+"region 1."
+msgstr "现在，执行一次相同的操作，在地域2中加入默认地域1."
+
+# 602a3773c4814a20a2c30488a1c18f79
+#: ../../configuration.rst:124
+msgid ""
+"Copy the account, user, and domain tables from the region 1 database to the "
+"region 2 database."
+msgstr "将帐号，用户，域信息数据表从地域1的数据库拷贝到地域2数据库中。"
+
+# fc4a95280143441fbcc8e6433a301cd1
+# 15839cafaf4f45298afa516f28712b88
+#: ../../configuration.rst:127 ../../configuration.rst:202
+msgid ""
+"In the following commands, it is assumed that you have set the root password"
+" on the database, which is a CloudStack recommended best practice. "
+"Substitute your own MySQL root password."
+msgstr "接下来的操作，你需要确保已设置好MYSQL数据库的root用户密码，这也是CloudStack推荐的操作。"
+
+# 5a32436730e4465eb2edc7735a4eaef5
+# 11c4185460654630a87bb504e9c4603c
+#: ../../configuration.rst:131 ../../configuration.rst:206
+msgid "First, run this command to copy the contents of the database:"
+msgstr "首先，运行这个命令拷贝数据库的内容："
+
+# 9b75a55461054a1bad3abbe6817b2f65
+#: ../../configuration.rst:137
+msgid "Then run this command to put the data onto the region 2 database:"
+msgstr "然后，运行这条命令将数据放入地域2的MYSQL数据库："
+
+# 80e5d3db9d2c450a88e53a4be8726923
+#: ../../configuration.rst:143
+msgid "Remove project accounts. Run these commands on the region 2 database:"
+msgstr "删除项目帐户. 在地域2的数据库中运行如下命令:"
+
+# 53caa00c3c5145de985c2b13b464b5ae
+# a631ba3cfeb94702915925f0a54f37f9
+#: ../../configuration.rst:149 ../../configuration.rst:225
+msgid "Set the default zone as null:"
+msgstr "设置默认区域为空白(NULL)："
+
+# 44128fa3ccb44f93a3ec3959b63e55d6
+#: ../../configuration.rst:155
+msgid "Restart the Management Servers in region 2."
+msgstr "重新启动地域2中的管理节点服务。"
+
+# b139e5a1fca145a59015dd8b26f2c103
+#: ../../configuration.rst:159
+msgid "Adding Third and Subsequent Regions"
+msgstr "增加第三个或是更多的地域"
+
+# 4b26a84e5c944c01b6cb0bdbf2d96dce
+#: ../../configuration.rst:161
+msgid ""
+"To add the third region, and subsequent additional regions, the steps are "
+"similar to those for adding the second region. However, you must repeat "
+"certain steps additional times for each additional region:"
+msgstr "增加第三个或是更多地域的操作与增加第二个地域的操作类似，但是，你必须重复这几个特定的操作步骤："
+
+# ffe5c28b1b87436ea5a2f7e84af47bc6
+#: ../../configuration.rst:165
+msgid ""
+"Install CloudStack in each additional region. Set the region ID for each "
+"region during the database setup step."
+msgstr "在每个额外的地域中安装CloudStack管理节点，并在安装数据库时为其设置不同的地域ID（region ID）。"
+
+# bdeafa42b2cc4c2991a4d0d58d70ccbd
+#: ../../configuration.rst:172
+msgid ""
+"Once the Management Server is running, add your new region to all existing "
+"regions by repeatedly using the Add Region button in the UI. For example, if"
+" you were adding region 3:"
+msgstr "一旦新地域的CloudStack管理服务器处于运行状态，在CloudStack WEB UI中使用添加地域按钮增加新的地域。以下以新增地域3作为示例："
+
+# aa7dd2e45a4e493bbbc4e9a50428dd39
+#: ../../configuration.rst:176
+msgid ""
+"Log in to CloudStack in the first region as root administrator (that is, log"
+" in to <region.1.IP.address>:8080/client), and add a region with ID 3, the "
+"name of region 3, and the endpoint <region.3.IP.address>:8080/client."
+msgstr "以系统管理员身份登陆第一个地域的CloudStack(登陆URL：<region.1.IP.address>:8080/client)，在增加地域时，输入地域ID ,名称，端点<region.3.IP.address>:8080/client。"
+
+# f071890bec3045a6ae288a2c8e906bc8
+#: ../../configuration.rst:181
+msgid ""
+"Log in to CloudStack in the second region as root administrator (that is, "
+"log in to <region.2.IP.address>:8080/client), and add a region with ID 3, "
+"the name of region 3, and the endpoint <region.3.IP.address>:8080/client."
+msgstr "以系统管理员身份登陆第二个地域的CloudStack（登陆URL：<region.2.IP.address>:8080/client），在增加地域时，输入地域的ID,名称，端点<region.3.IP.address>:8080/client。"
+
+# 421cc6da57a94b80997a5ef13cf5acfe
+#: ../../configuration.rst:186
+msgid ""
+"Repeat the procedure in reverse to add all existing regions to the new "
+"region. For example, for the third region, add the other two existing "
+"regions:"
+msgstr "在新的地域里，也同样增加所有的已存在的域域，例如，如果新地域是第三个CLOUDSTACK地域，刚需要其WEB UI里增加前两个地域信息："
+
+# cf1c2389f44d4a86b432cb480580e449
+#: ../../configuration.rst:190
+msgid ""
+"Log in to CloudStack in the third region as root administrator (that is, log"
+" in to <region.3.IP.address>:8080/client)."
+msgstr "以系统管理员身份登陆CLOUDSTACK（登陆URL：<region.3.IP.address>:8080/client）。"
+
+# ada88e8be6134f4ebfb9702b645c2504
+#: ../../configuration.rst:193
+msgid ""
+"Add a region with ID 1, the name of region 1, and the endpoint "
+"<region.1.IP.address>:8080/client."
+msgstr "在增加地域的选择里，输入地域1的ID,名称，端口（1,region 1,<region.1.IP.address>:8080/client）"
+
+# 9d6d9ac96a174313b0d904d9b1fc65a5
+#: ../../configuration.rst:196
+msgid ""
+"Add a region with ID 2, the name of region 2, and the endpoint "
+"<region.2.IP.address>:8080/client."
+msgstr "在增加地域的选择里，输入地域2的ID,名称，端口（2,region 2,<region.2.IP.address>:8080/client）"
+
+# d1c9041bd9774c38982ce11e14463815
+#: ../../configuration.rst:199
+msgid ""
+"Copy the account, user, and domain tables from any existing region's "
+"database to the new region's database."
+msgstr "将帐号，用户，域信息数据表从已存在的地域的数据库拷贝到新的地域里。"
+
+# 33652ef5006f4edeb7d088b9756b6510
+#: ../../configuration.rst:212
+msgid ""
+"Then run this command to put the data onto the new region's database. For "
+"example, for region 3:"
+msgstr "然后，运行这个命令将数据库的内容放到新的地域数据库当中去（如地域3）："
+
+# 1c3b113d8791401cb0dcdfd3c2fc5a86
+#: ../../configuration.rst:219
+msgid "Remove project accounts. Run these commands on the region 3 database:"
+msgstr "在地域3上运行这些命令，以便删除项目管理帐号："
+
+# b5ba88de9f22473f84da99081e799f53
+#: ../../configuration.rst:231
+msgid "Restart the Management Servers in the new region."
+msgstr "在新地域里重启CLOUDSTACK管理节点的服务。"
+
+# a9948baaa88f4e959dc8c37b39ddc029
+#: ../../configuration.rst:235
+msgid "Deleting a Region"
+msgstr "删除一个地域"
+
+# 14abc08462004cfda32c9789f06c7b22
+#: ../../configuration.rst:237
+msgid ""
+"Log in to each of the other regions, navigate to the one you want to delete,"
+" and click Remove Region. For example, to remove the third region in a "
+"3-region cloud:"
+msgstr "登陆到CLOUDSTACK的WEB UI，点击区域导航栏，选择你想删除的地域，然后，删除。例如，如果你想删除地域3："
+
+# 57df6d2d4970438faabdc8614ba6e67a
+#: ../../configuration.rst:241
+msgid "Log in to <region.1.IP.address>:8080/client."
+msgstr "登陆：<region.1.IP.address>:8080/client。"
+
+# 8028bf784ece4e7daf62cb170b120169
+#: ../../configuration.rst:245
+msgid "Click the name of the region you want to delete."
+msgstr "选择你想删除的区域。"
+
+# b2fc750526434ae6a7ced783693b40e4
+#: ../../configuration.rst:247
+msgid "Click the Remove Region button."
+msgstr "点击删除区域按钮。"
+
+# 49d26bc1e7244453b51002e2c2ccd48e
+#: ../../configuration.rst:249
+msgid "Repeat these steps for <region.2.IP.address>:8080/client."
+msgstr "在地域2里重复这些步骤：<region.2.IP.address>:8080/client。"
+
+# dfa99864651448d495ba56e8c8be435e
+#: ../../configuration.rst:255
+msgid "Adding a Zone"
+msgstr "增加一个区域"
+
+# 774412c06e41450181b4ce9c74727ddc
+#: ../../configuration.rst:257
+msgid ""
+"When you add a new zone, you will be prompted to configure the zone’s "
+"physical network and add the first pod, cluster, host, primary storage, and "
+"secondary storage."
+msgstr "当你要增加一个新的区域时，你会被提示需要同时配置物理网络以前第一个机柜提供点，集群，宿主机，主存储，二级存储。"
+
+# 49e4a1629dd0416499eb13760cd38d1b
+#: ../../configuration.rst:261
+msgid ""
+"Log in to the CloudStack UI as the root administrator. See `“Log In to the "
+"UI” <http://docs.cloudstack.apache.org/projects/cloudstack-"
+"administration/en/latest/ui.html#log-in-to-the-ui>`_."
+msgstr "以系统管理员身份登陆CloudStack WEB用户界面，参阅 `“登录用户界面” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_."
+
+# d6902134301b4889ad289a5806abf1e4
+#: ../../configuration.rst:263
+msgid "In the left navigation, choose Infrastructure."
+msgstr "在左边的导航，选择基础架构。"
+
+# ade8f3f94c154f1c89537d25e3fd7379
+#: ../../configuration.rst:265
+msgid "On Zones, click View More."
+msgstr "在区域页面，点击查看全部。"
+
+# 912e3cd3fe35426abc8c5283086fc5c2
+#: ../../configuration.rst:267
+msgid "Click Add Zone. The zone creation wizard will appear."
+msgstr "点击添加区域，向导界面就会出现。"
+
+# c04973210d4243a5a4e97bd2c6e9fe02
+#: ../../configuration.rst:269
+msgid "Choose one of the following network types:"
+msgstr "选择一种网络类型："
+
+# 28de3b1d237b4562ab0e114352a9d17a
+#: ../../configuration.rst:271
+msgid ""
+"**Basic.** For AWS-style networking. Provides a single network where each VM"
+" instance is assigned an IP directly from the network. Guest isolation can "
+"be provided through layer-3 means such as security groups (IP address source"
+" filtering)."
+msgstr "**基本.** 类似AWS风格的网络。单一网段，每个VM都得到此网段的一个IP。客户虚拟机之间主要以安全组形式在网络第三层之间实现隔离。（IP地址源过滤）"
+
+# c30938018fd3423d9da33dc59b76f9f5
+#: ../../configuration.rst:276
+msgid ""
+"**Advanced.** For more sophisticated network topologies. This network model "
+"provides the most flexibility in defining guest networks and providing "
+"custom network offerings such as firewall, VPN, or load balancer support."
+msgstr "**高级** 为更复杂的网络拓扑而设计。这种网络模型可以实现更灵活的客户虚拟机网络配置，并且可以提供防火墙，VPN，负载均衡这些高级功能。"
+
+# 03a0589bdc4a49528ac92074d0a70776
+#: ../../configuration.rst:281
+msgid ""
+"The rest of the steps differ depending on whether you chose Basic or "
+"Advanced. Continue with the steps that apply to you:"
+msgstr "根据选择的基本或高级区域的不同步骤会存在差异。选择适合你的步骤继续："
+
+# bff1cc1731ca4cdb859052b81a3fa2c8
+#: ../../configuration.rst:284
+msgid "`“Basic Zone Configuration” <#basic-zone-configuration>`_"
+msgstr "`“配置基本区域” <#basic-zone-configuration>`_"
+
+# 2dd7cac463554ed4bde0647d38500a5f
+#: ../../configuration.rst:286
+msgid "`“Advanced Zone Configuration” <#advanced-zone-configuration>`_"
+msgstr "`“配置高级区域” <#advanced-zone-configuration>`_"
+
+# cb4a637d5ad242448420fd13df8a7e29
+#: ../../configuration.rst:290
+msgid "Basic Zone Configuration"
+msgstr "基本区域配置"
+
+# dffcb46170814a6aaf35cf251f10287a
+#: ../../configuration.rst:292
+msgid ""
+"After you select Basic in the Add Zone wizard and click Next, you will be "
+"asked to enter the following details. Then click Next."
+msgstr "当你选择了基本区域之后，你需要输入以下细节信息，才能进入下一步。"
+
+# 28f1173455e549d4ac7adf938a40c70c
+# ecac47e28b5d4834bee99838438a221c
+#: ../../configuration.rst:295 ../../configuration.rst:514
+msgid "**Name.** A name for the zone."
+msgstr "**名称.** 为这个区域命名"
+
+# 4fcd0ce95f0b4136934d20a7007a5165
+# 2f1157bfaa2c475985f1902f67db381c
+#: ../../configuration.rst:297 ../../configuration.rst:516
+msgid ""
+"**DNS 1 and 2.** These are DNS servers for use by guest VMs in the zone. "
+"These DNS servers will be accessed via the public network you will add "
+"later. The public IP addresses for the zone must have a route to the DNS "
+"server named here."
+msgstr "**DNS 1 和 2.** 这些DNS是提供给区域里的客户虚拟机使用的。这些DNS服务器IP访问是通过随后添加的公网进行的。此区域的公网IP地址必须能够路由到这些DNS服务器。"
+
+# 4808ff4052234d66ac6543bf631b8b83
+#: ../../configuration.rst:302
+msgid ""
+"**Internal DNS 1 and Internal DNS 2.** These are DNS servers for use by "
+"system VMs in the zone (these are VMs used by CloudStack itself, such as "
+"virtual routers, console proxies, and Secondary Storage VMs.) These DNS "
+"servers will be accessed via the management traffic network interface of the"
+" System VMs. The private IP address you provide for the pods must have a "
+"route to the internal DNS server named here."
+msgstr "**内部 DNS 1 和内部 DNS 2.** 区域内的系统虚拟机会用到这些DNS服务器(系统虚拟机是CLOUDSTACK本身会用到的虚拟机如虚拟路由器-VR，控制台代理虚拟机-CPVM，二级存储虚拟机-SSVM)，这些系统虚拟机通过管理网络访问这个DNS服务器。为机柜提供点配置的私有IP地址必须能路由到这些内部DNS服务器。"
+
+# 05f039680a9649d59b7c565c57e22f06
+# 21fe556029bb4e01962ab112ac9768f4
+#: ../../configuration.rst:310 ../../configuration.rst:538
+msgid ""
+"**Hypervisor.** (Introduced in version 3.0.1) Choose the hypervisor for the "
+"first cluster in the zone. You can add clusters with different hypervisors "
+"later, after you finish adding the zone."
+msgstr "**Hypervisor.**(在version 3.0.1介绍过) 需要为区域内的第一个集群选择一种hypervisor。当你完成添加区域的配置之后，也可以为另外的集群配置不同的hypervisor。"
+
+# c00029912e7046949d6766c29a38336e
+#: ../../configuration.rst:315
+msgid ""
+"**Network Offering.** Your choice here determines what network services will"
+" be available on the network for guest VMs."
+msgstr "**网络方案。** 你需要客户虚拟机可用的网络方案及服务"
+
+# e3fe221d9a044cc18fd23016249ec1cc
+#: ../../configuration.rst:319
+msgid "Network Offering"
+msgstr "网络方案"
+
+# 0c9256246d864525a6d27a188b8e926d
+#: ../../configuration.rst:319
+msgid "Description"
+msgstr "描述"
+
+# 17becb3e858a4876942de300eef4c2bf
+#: ../../configuration.rst:321
+msgid "DefaultSharedNetworkOfferingWithSGService"
+msgstr "DefaultSharedNetworkOfferingWithSGService"
+
+# 6657626819c84e93af54d41c8cc692fe
+#: ../../configuration.rst:321
+msgid ""
+"If you want to enable security groups for guest traffic isolation, choose "
+"this. (See Using Security Groups to"
+" Control "
+"Traffic to VMs.)"
+msgstr "如果你希望通过安全组来隔离客户虚拟机流量，选择这个选项。(参看通过安全组隔离虚拟机这一章节。)"
+
+# af8f6480878642e78421c05628436d07
+#: ../../configuration.rst:322
+msgid "DefaultSharedNetworkOffering"
+msgstr "DefaultSharedNetworkOffering"
+
+# 4cd8c72bfb834f82bd91743d1ac74e53
+#: ../../configuration.rst:322
+msgid "If you do not need security groups, choose this."
+msgstr "如果你需要安全组，选择这个选项。"
+
+# 702d31b78c8146c284f36761d3ae4129
+#: ../../configuration.rst:323
+msgid "DefaultSharedNetscalerEIPandELBNetworkOffering"
+msgstr "DefaultSharedNetscalerEIPandELBNetworkOffering"
+
+# 4bd344a4652e48bc956cf57fd1aa5404
+#: ../../configuration.rst:323
+msgid ""
+"If you have installed a Citrix NetScaler appliance as part of your zone "
+"network, and you will be using its Elastic"
+" IP and Elastic Load"
+" Balancing features, choose this. With the EIP and ELB features, a basic "
+"zone with security"
+" groups enabled "
+"can offer 1:1 static NAT and load balancing."
+msgstr "如果，你在CLOUDSTACK内安装了Citrix NetScaler应用，并且你需要Elastic IP和Elastic Load Balancing这些功能的话，选择这个选项。EIP 和ELB技术在安全组启用的情况下，可以提供1：1的NAT映射和负载均衡功能。 "
+
+# 0b90574172fb4e7cbac4151d6526f593
+# 6d30529dd4ac40c19bb562424065502c
+#: ../../configuration.rst:327 ../../configuration.rst:529
+msgid ""
+"**Network Domain.** (Optional) If you want to assign a special domain name "
+"to the guest VM network, specify the DNS suffix."
+msgstr "**网络域** （可选） 如果你想为客户虚机网络定义一个域名，在此处输入后缀名。"
+
+# 9036e7c5033747d283076f98506ccb51
+# 815323d66e34477eab427c9fdfed1c83
+#: ../../configuration.rst:330 ../../configuration.rst:543
+msgid ""
+"**Public.** A public zone is available to all users. A zone that is not "
+"public will be assigned to a particular domain. Only users in that domain "
+"will be allowed to create guest VMs in this zone."
+msgstr "**公有区域.** 一个公有区域可以被所有用户使用。而非公有区域会有一个指定的域名，只有指定域名中的用户才可以在那个区域里创建客户虚拟机。"
+
+# 21d7ccd878e94405b989441562b0599b
+# a9e870bbb6004173be4bfa18835bcb70
+#: ../../configuration.rst:334 ../../configuration.rst:547
+msgid "Choose which traffic types will be carried by the physical network."
+msgstr "选择在物理网络里需要承载的流量类型。"
+
+# bc24ee0196bb4ef9aab22883c8434456
+#: ../../configuration.rst:336
+msgid ""
+"The traffic types are management, public, guest, and storage traffic. For "
+"more information about the types, roll over the icons to display their tool "
+"tips, or see Basic Zone Network Traffic Types. This screen starts out with "
+"some traffic types already assigned. To add more, drag and drop traffic "
+"types onto the network. You can also change the network name if desired."
+msgstr "流量类型分为管理流量，公网流量，来宾客户流量，和存储流量。关于这些流量的更多信息，可以点击相关图标得到一些帮助。这个屏幕显示的是已分配好的流量类型。如果要继续增加，可以拖动相关流量类型到网络里，当然，也可以将网络更改成你认为合适的名字。"
+
+# 48f3ce0bb26d4d94963acae89c848fa2
+#: ../../configuration.rst:343
+msgid ""
+"Assign a network traffic label to each traffic type on the physical network."
+" These labels must match the labels you have already defined on the "
+"hypervisor host. To assign each label, click the Edit button under the "
+"traffic type icon. A popup dialog appears where you can type the label, then"
+" click OK."
+msgstr "为物理网络上承载的每一种CLOUDSTACK网络流量类型赋予一个标签。这些标签必须与你已在宿主机上设置的（网桥）标签名一致。如果要编辑标签，点击流量类型上的编辑按钮，在弹出的对话框中输入相应名称，然后再点击OK即可。"
+
+# 078e7952b6574b6684e5495207335bec
+# 46d267d97c60451a88ceeeb647987e77
+#: ../../configuration.rst:349 ../../configuration.rst:568
+msgid ""
+"These traffic labels will be defined only for the hypervisor selected for "
+"the first cluster. For all other hypervisors, the labels can be configured "
+"after the zone is created."
+msgstr "这些流量类型标签只是定义了区域内的第一个集群的hypervisor。对于其它hypervisor，则这个标签可以在区域创建完成之后配置。"
+
+# 4ee547a64dce4459ae3b5d914984b125
+# 0e5056a8e6fc4f5cb200cda3d7a2525c
+#: ../../configuration.rst:353 ../../configuration.rst:583
+msgid "Click Next."
+msgstr "点击下一步"
+
+# 0c8ac4ed983c46f4b288584ac8bdf37b
+#: ../../configuration.rst:355
+msgid ""
+"(NetScaler only) If you chose the network offering for NetScaler, you have "
+"an additional screen to fill out. Provide the requested details to set up "
+"the NetScaler, then click Next."
+msgstr "(只针对NetScaler) 如果你选择的网络方案是针对NetScaler的，则还要一个额外的选项需要填写。在填写了关于NetScaler的细节信息之后，点击下一步继续。"
+
+# c40cb3f0ffff4013b271dc76dddcf958
+#: ../../configuration.rst:359
+msgid ""
+"**IP address.** The NSIP (NetScaler IP) address of the NetScaler device."
+msgstr "**IP地址.** 针对NetScaler的NSIP（NetScaler的IP地址）。"
+
+# 8ea7e4f0a7ef4614b9fbbac8d8fd2d8a
+#: ../../configuration.rst:362
+msgid ""
+"**Username/Password.** The authentication credentials to access the device. "
+"CloudStack uses these credentials to access the device."
+msgstr "**用户名/密码.** 访问此设备的认证许可。CLOUDSTACK使用这些认证信息访问此设备。"
+
+# ee173abcc1e54f3d9917adc4936e9b97
+#: ../../configuration.rst:366
+msgid ""
+"**Type.** NetScaler device type that is being added. It could be NetScaler "
+"VPX, NetScaler MPX, or NetScaler SDX. For a comparison of the types, see "
+"About Using a NetScaler Load Balancer."
+msgstr "**类型.** 需要添加的NetScaler设备的类型。它必须是NetScaler VPX, NetScaler MPX, or NetScaler SDX当中的一种。至于这三种类型的比较，可以参看NetScaler负载均衡这一章节内容。"
+
+# 8531937f377e40e9b877f0205da08b18
+#: ../../configuration.rst:370
+msgid ""
+"**Public interface.** Interface of NetScaler that is configured to be part "
+"of the public network."
+msgstr "**公网接口.** NetScaler接口配置为公网的一部分。"
+
+# fa6bf0c0d9d24792afde4c7cfc17a1c3
+#: ../../configuration.rst:373
+msgid ""
+"**Private interface.** Interface of NetScaler that is configured to be part "
+"of the private network."
+msgstr "**内网接口** NetScaler接口配置为内网的一部分。"
+
+# badd0cf691644807ad806889ad40db32
+#: ../../configuration.rst:376
+msgid ""
+"**Number of retries.** Number of times to attempt a command on the device "
+"before considering the operation failed. Default is 2."
+msgstr "**重试次数** 认为操作失败前的最大重试次数，默认为2次。"
+
+# 3544f121bc064e29a3a27f191cee9f84
+#: ../../configuration.rst:379
+msgid ""
+"**Capacity.** Number of guest networks/accounts that will share this "
+"NetScaler device."
+msgstr "**容量**，共享NetScaler设备的最大客户网络或帐号的数量。"
+
+# 8332d9e920fe463a8dca1db0f77f8583
+#: ../../configuration.rst:382
+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 "**专用** 当标示为专用之后，则这个设备只为一个帐号使用。当选择专用之后，容量的数值不再可任意设置---明显的，它的数量只能为1."
+
+# 34827b0bfdd34781b875e6887bebfc75
+#: ../../configuration.rst:387
+msgid ""
+"(NetScaler only) Configure the IP range for public traffic. The IPs in this "
+"range will be used for the static NAT capability which you enabled by "
+"selecting the network offering for NetScaler with EIP and ELB. Enter the "
+"following details, then click Add. If desired, you can repeat this step to "
+"add more IP ranges. When done, click Next."
+msgstr "(只针对NetScaler) 设置公网的IP范围。此IP范围用作启用了EIP和ELB技术的网络方案的NAT映射。输入这些细节信息，点击增加。如果有必要，你可以重复输入多个公网IP范围。当这一切完成之后，点击下一步继续。"
+
+# 635dae2c5e9a4fc78b1708c6ebf80460
+# f179dd4093cc42efbe89a0c52531a934
+#: ../../configuration.rst:393 ../../configuration.rst:589
+msgid "**Gateway.** The gateway in use for these IP addresses."
+msgstr "**网关** 为这些IP地址定义网关。"
+
+# 7022d1ca2ebb4f0d82e4bd5af7ad38c8
+# ade1edfc41014640bbaf07a8cb6d7a30
+#: ../../configuration.rst:395 ../../configuration.rst:591
+msgid "**Netmask.** The netmask associated with this IP range."
+msgstr "**子网掩码** 定义这些IP地址的子网掩码。"
+
+# 7bfb9d769b874eed8399dd1dce773692
+# cea91ee2b41f476093dd8e6cb6c464a4
+#: ../../configuration.rst:397 ../../configuration.rst:593
+msgid "**VLAN.** The VLAN that will be used for public traffic."
+msgstr "**VLAN** 公网流量的VLAN号。"
+
+# f13431658b2445c48bca7d494a057961
+#: ../../configuration.rst:399
+msgid ""
+"**Start IP/End IP.** A range of IP addresses that are assumed to be "
+"accessible from the Internet and will be allocated for access to guest VMs."
+msgstr "**开始IP/结束IP.** 定义公网IP范围，这些IP用来访问公网或是从公网访问客户虚拟机。"
+
+# c608789049734f06a202678e647078ea
+# cb65d7f39c6d43b5878166ff469a9336
+#: ../../configuration.rst:403 ../../configuration.rst:599
+msgid ""
+"In a new zone, CloudStack adds the first pod for you. You can always add "
+"more pods later. For an overview of what a pod is, see `“About Pods” "
+"<http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods"
+"#about-pods>`_."
+msgstr "在一个新的区域，CLOUSTACK总是会为你添加第一个机柜提供点。当然，在区域设置完成之后，你可以添加理多的机柜提供点。关于机柜提供点的详细，参看此URL：`“About Pods” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-pods>`_."
+
+# 133a33d409fd46a1af933404a8b7cd37
+# ca67116d4f464703befcd3acaf5541fa
+#: ../../configuration.rst:407 ../../configuration.rst:603
+msgid "To configure the first pod, enter the following, then click Next:"
+msgstr "开始配置第一个机柜提供点，输入以下这些信息，然后点击下一步继续。"
+
+# 731b1cd2a3a24733a2509db423e05a3f
+# ef9297fe5b3b4a60a47310045adc4a7d
+#: ../../configuration.rst:409 ../../configuration.rst:605
+msgid "**Pod Name.** A name for the pod."
+msgstr "**机柜提供点名称** 为此机柜提供点命名。"
+
+# 06e37281b36442f09653c54f71fd6baa
+# 26c99791b3424045afcfdc3461c2e273
+#: ../../configuration.rst:411 ../../configuration.rst:607
+msgid "**Reserved system gateway.** The gateway for the hosts in that pod."
+msgstr "**保留系统的网关** 这个机柜提供点内宿主机的网关。"
+
+# e043e1605e4740d0b7ae424058ccf656
+# 8668dd9e73bc45b5b4963e201aaa426f
+#: ../../configuration.rst:414 ../../configuration.rst:610
+msgid ""
+"**Reserved system netmask.** The network prefix that defines the pod's "
+"subnet. Use CIDR notation."
+msgstr "**保留系统的子网掩码.** 定义此机柜提供点的子网前缀，用CIDR标示。 "
+
+# 2d2d591fcc7b4b5f9a841fc3625685e4
+# cf5db04d254d4fdca2d3083d47ed4820
+#: ../../configuration.rst:417 ../../configuration.rst:790
+msgid ""
+"**Start/End Reserved System IP.** The IP range in the management network "
+"that CloudStack uses to manage various system VMs, such as Secondary Storage"
+" VMs, Console Proxy VMs, and DHCP. For more information, see System Reserved"
+" IP Addresses."
+msgstr "**开始/结束系统保留的IP.** 这些IP地址是CLOUDSTACK给各种管理用的系统虚拟机使用的。如SSVM，CPVM,DHCP（VR）等。如需更多详情，请参看系统保留IP这一章节"
+
+# dc5d7a38ccf54de5b4ba93d50d497df8
+#: ../../configuration.rst:422
+msgid ""
+"Configure the network for guest traffic. Provide the following, then click "
+"Next:"
+msgstr "为客户来宾配置网络，提供好如下信息，然后点击下一步。"
+
+# ec278db6dee347a3b0b7ccd5199fb75e
+#: ../../configuration.rst:425
+msgid "**Guest gateway.** The gateway that the guests should use."
+msgstr "**来宾网关.** 客户来宾虚拟机使用的网关。"
+
+# e08dd136c0db40c4919d4e09e251a450
+#: ../../configuration.rst:427
+msgid ""
+"**Guest netmask.** The netmask in use on the subnet the guests will use."
+msgstr "**来宾子网掩码.** 客户来宾虚拟机使用的子网掩码。"
+
+# d7beb7ec370b474688190302620f092d
+#: ../../configuration.rst:430
+msgid ""
+"**Guest start IP/End IP.** Enter the first and last IP addresses that define"
+" a range that CloudStack can assign to guests."
+msgstr "**客户来宾开始/结束IP.** 输入CLOUDSTACK用来分配给客户来宾使用的起止IP地址。"
+
+# 21367aec79504bf6b0523f8b8ff518c9
+#: ../../configuration.rst:433
+msgid ""
+"We strongly recommend the use of multiple NICs. If multiple NICs are used, "
+"they may be in a different subnet."
+msgstr "我们强烈推荐使用多网卡，因为多网卡就可以配置不同的子网。"
+
+# aae6aaee21bf4878b935bad1cc640b4e
+#: ../../configuration.rst:436
+msgid ""
+"If one NIC is used, these IPs should be in the same CIDR as the pod CIDR."
+msgstr "如果一个网卡已在使用，则这些IP地址的CIDR必须和机柜提供点的CIDR一致。"
+
+# 760580b3523b4418a99099137bb67922
+#: ../../configuration.rst:439
+msgid ""
+"In a new pod, CloudStack adds the first cluster for you. You can always add "
+"more clusters later. For an overview of what a cluster is, see About "
+"Clusters."
+msgstr "在一个新的机柜提供点里，CLOUDSTACK会为你加第一个群集。当然，你也可以以后再添加其它的群集。如果想多了解群集，你可以参看群集的相关章节。"
+
+# 44c7f5931d5e4e35b85d85089a2cf0e2
+# 0b9c98c65d92481ab54bf4e8ed5ba5a8
+#: ../../configuration.rst:443 ../../configuration.rst:627
+msgid "To configure the first cluster, enter the following, then click Next:"
+msgstr "配置第一个群集，输入以下这些信息，然后点击下一步。"
+
+# 51c6cb2616384dc2a2fdde4178e35993
+#: ../../configuration.rst:445
+msgid ""
+"**Hypervisor.** (Version 3.0.0 only; in 3.0.1, this field is read only) "
+"Choose the type of hypervisor software that all hosts in this cluster will "
+"run. If you choose VMware, additional fields appear so you can give "
+"information about a vSphere cluster. For vSphere servers, we recommend "
+"creating the cluster of hosts in vCenter and then adding the entire cluster "
+"to CloudStack. See Add Cluster: vSphere."
+msgstr "**Hypervisor.** (只针对Version 3.0.0;在3.0.1中，这一栏是只读的)选择一种在这个群集中运行的hypervisor。如果你选择宾是VMWARE，则需要提供关于VSPHERE群集的信息。对于VSHPERE服务器，我们建议先在VCENTER里将群集设备好，然后作为群集整体加入CLOUDSTACK。参看Add Cluster: vSphere。"
+
+# 0a1f5e7d557a445fbd943a2375f81ce9
+# 2616a88c400442bc8a9ff5fb9fd7ce49
+#: ../../configuration.rst:453 ../../configuration.rst:637
+msgid ""
+"**Cluster name.** Enter a name for the cluster. This can be text of your "
+"choosing and is not used by CloudStack."
+msgstr "**群集名称.** 你要为此群集提供一个CLOUDSTACK之前没有使用的名称。"
+
+# f215a4cf027b40eea80996afea404e88
+#: ../../configuration.rst:456
+msgid ""
+"In a new cluster, CloudStack adds the first host for you. You can always add"
+" more hosts later. For an overview of what a host is, see About Hosts."
+msgstr "在一个新的群集里，CLOUDSTACK会添加第一个宿主机。当然，之后你可以添加更多的宿主机。关于宿主机的概念，可以参看About Hosts的章节。"
+
+# a4958ea1500c4d65a7ec65554fb9c8f0
+#: ../../configuration.rst:461
+msgid ""
+"When you add a hypervisor host to CloudStack, the host must not have any VMs"
+" already running."
+msgstr "当你往CLOUDSTACK里新增一个hypervisor宿主机时，此宿主机上一定不能有虚拟机在运行（全新的宿主机）。"
+
+# a7aa2568c3144be19c371ba08be4bf6d
+# 7686b9f224ea40b48d2c4c7b3d64e15b
+#: ../../configuration.rst:464 ../../configuration.rst:648
+msgid ""
+"Before you can configure the host, you need to install the hypervisor "
+"software on the host. You will need to know which version of the hypervisor "
+"software version is supported by CloudStack and what additional "
+"configuration is required to ensure the host will work with CloudStack. To "
+"find these installation details, see:"
+msgstr "当你在配置宿主机之后，你需要在宿主机上安装hypervisor软件。你也需要事先了解CLOUDSTACK所能支持的hypervisor种类及版本，以及是否需要额外的配置信息。关于这些配置的详细信息，参看："
+
+# 4866dcbbc18a4c9e96b993ed1e536f29
+#: ../../configuration.rst:470
+msgid "Citrix XenServer Installation and Configuration"
+msgstr "Citrix XenServer安装及配置"
+
+# 876393f442894c6389d1edf6e6ebc213
+# 7cbfdd4d4aad40cfbcf4aea9c9fd6ce2
+#: ../../configuration.rst:472 ../../configuration.rst:656
+msgid "VMware vSphere Installation and Configuration"
+msgstr "VMware vSphere 安装和配置"
+
+# 93504af6c05b46fcb6ccc59cd48de0d0
+#: ../../configuration.rst:474
+msgid "KVM vSphere Installation and Configuration"
+msgstr "KVM vSphere安装及配置"
+
+# 5e077e29fb7446a6bda46732cc0eb453
+# 2d6f19cf4a334139b27e4f7a94b8bf92
+#: ../../configuration.rst:476 ../../configuration.rst:660
+msgid "To configure the first host, enter the following, then click Next:"
+msgstr "配置第一个宿主机，输入以下信息，然后点击下一步："
+
+# 0e194db1641a4be2ae5d6ed3f2d27575
+# b7727092534b455e924a0b5ddfa9ec69
+#: ../../configuration.rst:478 ../../configuration.rst:662
+msgid "**Host Name.** The DNS name or IP address of the host."
+msgstr "**宿主机名称.** 宿主机的IP地址或DNS解析名称。"
+
+# 1af10b11095449a496d9b3304652ba03
+#: ../../configuration.rst:480
+msgid "**Username.** The username is root."
+msgstr "**用户名.** 用户名为root。"
+
+# 98f8e09abbc547ca994b5156f2dbcaa6
+# 4623683d93bf4b02a802a809c6786faf
+#: ../../configuration.rst:482 ../../configuration.rst:666
+msgid ""
+"**Password.** This is the password for the user named above (from your "
+"XenServer or KVM install)."
+msgstr "**密码。** 上面用户名的密码（主要针对XenServer 和 KVM的安装）"
+
+# 258ef7abb2b447ebb6cce1508920d12b
+#: ../../configuration.rst:485
+msgid ""
+"**Host Tags.** (Optional) Any labels that you use to categorize hosts for "
+"ease of maintenance. For example, you can set this to the cloud's HA tag "
+"(set in the ha.tag global configuration parameter) if you want this host to "
+"be used only for VMs with the \"high availability\" feature enabled. For "
+"more information, see HA-Enabled Virtual Machines as well as HA for Hosts."
+msgstr "**主机标签(可选).** 此标签用于将主机分类，以便更好的后期维护。比如，如果你只想此宿主机用于具有HA（high availability）高可用性能的虚拟机，那么，你可以将此宿主机设置为云里相关的HA标签。(参看全局设置参数里的ha.tag)，关于HA的更多信息，请参看HA虚拟机和HA宿主机的相关章节。"
+
+# 55ee6f53cea246bda767b3f91ed77753
+#: ../../configuration.rst:492
+msgid ""
+"In a new cluster, CloudStack adds the first primary storage server for you. "
+"You can always add more servers later. For an overview of what primary "
+"storage is, see About Primary Storage."
+msgstr "在一个新的群集里，CLOUDSTACK会添加第一个主存储。当然，你也可以在随后添加更多的主存储。关于主存储的细节，可以参看相关章节：Primary Storage"
+
+# 33955d5773764a229a1faa4ba31636a8
+# f58343456b724277b2179ea70214dd8e
+#: ../../configuration.rst:496 ../../configuration.rst:682
+msgid ""
+"To configure the first primary storage server, enter the following, then "
+"click Next:"
+msgstr "配置第一个主存储，输入以下信息，然后点击下一步："
+
+# 882e651ffb4f487196c12a9ecbd5b66c
+# 02cefa6c9ff44810b682b0420f16e4c3
+# 7b2c3d9c2fa347bbb7ae181ee559419e
+#: ../../configuration.rst:499 ../../configuration.rst:685
+#: ../../configuration.rst:1180
+msgid "**Name.** The name of the storage device."
+msgstr "**名称** 存储设备的名称"
+
+# 9108c1607da247cb819f2b3dd2b94186
+#: ../../configuration.rst:501
+msgid ""
+"**Protocol.** For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM,"
+" choose NFS, SharedMountPoint,CLVM, or RBD. For vSphere choose either VMFS "
+"(iSCSI or FiberChannel) or NFS. The remaining fields in the screen vary "
+"depending on what you choose here."
+msgstr "**协议** 对于XenServer，选择NFS, iSCSI, 或 PreSetup.对于KVM，选择NFS, SharedMountPoint,CLVM, 或RBD.对于VSPHERE，选择VMFS（iSCSI 或FiberChannel）或NFS。本栏的其它选择依你选项不同而不同。"
+
+# a95cec57590f4eb9bb5720ab7fb7809c
+#: ../../configuration.rst:509
+msgid "Advanced Zone Configuration"
+msgstr "添加高级区域"
+
+# e9085595c59b47d59920970c045cd7ae
+#: ../../configuration.rst:511
+msgid ""
+"After you select Advanced in the Add Zone wizard and click Next, you will be"
+" asked to enter the following details. Then click Next."
+msgstr "当你选择高级区域以后，你需要提供以下信息，然后点击下一步。"
+
+# a584fb17ef794dad83499d140687e136
+#: ../../configuration.rst:521
+msgid ""
+"**Internal DNS 1 and Internal DNS 2.** These are DNS servers for use by "
+"system VMs in the zone(these are VMs used by CloudStack itself, such as "
+"virtual routers, console proxies,and Secondary Storage VMs.) These DNS "
+"servers will be accessed via the management traffic network interface of the"
+" System VMs. The private IP address you provide for the pods must have a "
+"route to the internal DNS server named here."
+msgstr "**内网 DNS 1 和内网 DNS 2.** 区域内的系统虚拟机会用到这些DNS服务器(系统虚拟机是CLOUDSTACK本身会用到的虚拟机如虚拟路由器-VR，控制台代理虚拟机-CPVM，二级存储虚拟机-SSVM)，这些系统虚拟机通过管理网络访问这个DNS服务器。为机柜提供点配置的私有IP地址必须能路由到这些内部DNS服务器。"
+
+# 7f5a0f00682d4f05af43eb2dcc7c60fb
+#: ../../configuration.rst:532
+msgid ""
+"**Guest CIDR.** This is the CIDR that describes the IP addresses in use in "
+"the guest virtual networks in this zone. For example, 10.1.1.0/24. As a "
+"matter of good practice you should set different CIDRs for different zones. "
+"This will make it easier to set up VPNs between networks in different zones."
+msgstr "**客户虚拟机CIDR.** 这个CIDR指的是在这个区域内的虚拟客户机的网络，比如10.1.1.0/24。最好能为不同的区域配置不同的CIDR，因为这样可以更方便的在不同的区域中建立相关的VPN。"
+
+# fbaf58d0ff1649dd8a0f05537743c882
+#: ../../configuration.rst:549
+msgid ""
+"The traffic types are management, public, guest, and storage traffic. For "
+"more information about the types, roll over the icons to display their tool "
+"tips, or see `“Advanced Zone Network Traffic Types” "
+"<http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods"
+"#advanced-zone-network-traffic-types>`_. This screenstarts out with one "
+"network already configured. If you have multiple physical networks, you need"
+" to add more. Drag and drop traffic types onto a greyed-out network and it "
+"will become active. You can move the traffic icons from one network to "
+"another; for example, if the default traffic types shown for Network 1 do "
+"not match your actual setup, you can move them down. You can also change the"
+" network names if desired."
+msgstr ""
+
+# a1c899d9956d4667a5fa43596d6d8f70
+#: ../../configuration.rst:561
+msgid ""
+"(Introduced in version 3.0.1) Assign a network traffic label to each traffic"
+" type on each physical network. These labels must match the labels you have "
+"already defined on the hypervisor host. To assign each label, click the Edit"
+" button under the traffic type icon within each physical network. A popup "
+"dialog appears where you can type the label, then click OK."
+msgstr "(在3.0.1版本中介绍过)为每一种不同的物理网络分配不同的网络流量标签。这些标签必须和你在hypervisor主机中定义的标签一致。更改标签名，可以在每一个物理网络里点击相应的流量标签的编辑按钮，一个对话框会跳出来，输入合适的标签之后，点击下一步。"
+
+# 805792aff6994e028ce9205047e477f1
+#: ../../configuration.rst:572
+msgid ""
+"(VMware only) If you have enabled Nexus dvSwitch in the environment, you "
+"must specify the corresponding Ethernet port profile names as network "
+"traffic label for each traffic type on the physical network. For more "
+"information on Nexus dvSwitch, see Configuring a vSphere Cluster with Nexus "
+"1000v Virtual Switch in the Installation Guide. If you have enabled VMware "
+"dvSwitch in the environment, you must specify the corresponding Switch name "
+"as network traffic label for each traffic type on the physical network. For "
+"more information, see Configuring a VMware Datacenter with VMware "
+"Distributed Virtual Switch in the Installation Guide."
+msgstr "(只针对VMWARE)如果你的环境中有Nexus分布式虚拟交换机(dvSwitch),则必须为每一种物理网络上的流量类型的标签指定为相应的局域网端口配置名称(Ethernet port profile names).关于Nexus dvSwitch更多信息，可以查看安装指南的相关章节。如果你的环境中有VMware的分布式虚拟交换机（dvSwitch），,则必须为每一种物理网络上的流量类型的标签指定为相应的虚拟交换机名称(Switch name)。关于这方面的更多信息，参看安装指南当中的关于VMware Datacenter的相关章节。"
+
+# 2df839852be644778c41107b53c0eef8
+#: ../../configuration.rst:585
+msgid ""
+"Configure the IP range for public Internet traffic. Enter the following "
+"details, then click Add. If desired, you can repeat this step to add more "
+"public Internet IP ranges. When done, click Next."
+msgstr "配置公网IP地址范围，输入以下细节，然后点击添加。如果需要，你可以重复此过程以便添加更多的公网IP地址。当这一切完成之后，点击下一步。"
+
+# 4854b23855194f6a95f455049a970d9c
+#: ../../configuration.rst:595
+msgid ""
+"**Start IP/End IP.** A range of IP addresses that are assumed to be "
+"accessible from the Internet and will be allocated for access to guest "
+"networks."
+msgstr "**开始IP/结束IP.** 为客户机的网络配置一个可供互联网访问进出的IP地址范围。"
+
+# b27b5e010eb64430b9cc36887f0155ab
+#: ../../configuration.rst:613
+msgid ""
+"**Start/End Reserved System IP.** The IP range in the management network "
+"that CloudStack uses to manage various system VMs, such as Secondary Storage"
+" VMs, Console Proxy VMs, and DHCP. For more information, see `“System "
+"Reserved IP Addresses” "
+"<http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#id4>`_."
+msgstr "**开始/结束系统保留的IP.** 这些IP地址是CLOUDSTACK给各种管理用的系统虚拟机使用的。如SSVM，CPVM,DHCP（VR）等。如需更多详情，请参看：`“系统保留IP地址” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#id4>`_."
+
+# 6d27295ebf7948e6a7c0b2138ca9fa39
+#: ../../configuration.rst:619
+msgid ""
+"Specify a range of VLAN IDs to carry guest traffic for each physical network"
+" (see VLAN Allocation Example ), then click Next."
+msgstr "定义每个物理网络上的客户流量的VLAN ID范围(参看 VLAN 分配示例 )，然后点击下一步。"
+
+# 58ec28ce7043492ab818e135bd5ad764
+#: ../../configuration.rst:622
+msgid ""
+"In a new pod, CloudStack adds the first cluster for you. You can always add "
+"more clusters later. For an overview of what a cluster is, see `“About "
+"Clusters” "
+"<http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods"
+"#about-clusters>`_."
+msgstr "在一个新的机柜提供点，CLOUDSTACK会添加第一个群集。当然，随后你可以添加更多的群集。关于什么是群集，参阅 `“关于群集” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-clusters>`_."
+
+# c4117492d58e4cc7a95877d4420c0f77
+#: ../../configuration.rst:629
+msgid ""
+"**Hypervisor.** (Version 3.0.0 only; in 3.0.1, this field is read only) "
+"Choose the type of hypervisor software that all hosts in this cluster will "
+"run. If you choose VMware, additional fields appear so you can give "
+"information about a vSphere cluster. For vSphere servers, we recommend "
+"creating the cluster of hosts in vCenter and then adding the entire cluster "
+"to CloudStack. See Add Cluster: vSphere ."
+msgstr "**Hypervisor.** (只针对Version 3.0.0;在3.0.1中，这一栏是只读的)选择一种在这个群集中运行的hypervisor。如果你选择宾是VMWARE，则需要提供关于VSPHERE群集的信息。对于VSHPERE服务器，我们建议先在VCENTER里将群集设备好，然后作为群集整体加入CLOUDSTACK。参看Add Cluster: vSphere。"
+
+# a33530a965844729a700ddcafd654cab
+#: ../../configuration.rst:640
+msgid ""
+"In a new cluster, CloudStack adds the first host for you. You can always add"
+" more hosts later. For an overview of what a host is, see `“About Hosts” "
+"<http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods"
+"#about-hosts>`_."
+msgstr "在一个新的群集，CLOUDSTACK会添加好第一个宿主机，随后，你也可以自行添加更多的宿主机。关于什么是宿主机，参阅 `“关于主机” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-hosts>`_."
+
+# 70099c0bbf4c4ab79b74ce130e472676
+#: ../../configuration.rst:645
+msgid ""
+"When you deploy CloudStack, the hypervisor host must not have any VMs "
+"already running."
+msgstr "当你开始部署CLOUDSTACK时，hypervisor宿主机必须不能有已在运行的虚拟机。"
+
+# 969595946df24f7b9a30efd4829ce89d
+#: ../../configuration.rst:654
+msgid "Citrix XenServer Installation for CloudStack"
+msgstr "为CloudStack安装Citrix XenServer"
+
+# 2286f6a6c02c44fca23c04f2d6e05175
+#: ../../configuration.rst:658
+msgid "KVM Installation and Configuration"
+msgstr "KVM的安装和配置"
+
+# 9263f822255744319df0264ecd6cf42b
+#: ../../configuration.rst:664
+msgid "**Username.** Usually root."
+msgstr "**用户名.** 通常为root"
+
+# 617da6e8e7dc42cc94c5649b11b4f94e
+#: ../../configuration.rst:669
+msgid ""
+"**Host Tags.** (Optional) Any labels that you use to categorize hosts for "
+"ease of maintenance. For example, you can set to the cloud's HA tag (set in "
+"the ha.tag global configuration parameter) if you want this host to be used "
+"only for VMs with the \"high availability\" feature enabled. For more "
+"information, see HA-Enabled Virtual Machines as well as HA for Hosts, both "
+"in the Administration Guide."
+msgstr "**主机标签.** (可选)此标签用于将主机分类，以便更好的后期维护。比如，如果你只想此宿主机用于具有HA（high availability）高可用性能的虚拟机，那么，你可以将此宿主机设置为云里相关的HA标签。(参看全局设置参数里的ha.tag)，关于HA的更多信息，请参看HA虚拟机和HA宿主机的相关章节。"
+
+# d405480d45fa4402a325beac9b7a9b35
+#: ../../configuration.rst:677
+msgid ""
+"In a new cluster, CloudStack adds the first primary storage server for you. "
+"You can always add more servers later. For an overview of what primary "
+"storage is, see `“About Primary Storage” "
+"<http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods"
+"#about-primary-storage>`_."
+msgstr "在一个新的群集，CLOUDSTACK会添加好第一台主存储服务器，随后，你也可以自行添加更多的存储服务器。关于什么是主存储服务器，参阅 `“关于主存储” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-primary-storage>`_."
+
+# ef6c13fd4cd641ebb3914aa5bcfd4b5e
+#: ../../configuration.rst:687
+msgid ""
+"**Protocol.** For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM,"
+" choose NFS, SharedMountPoint, CLVM, and RBD. For vSphere choose either VMFS"
+" (iSCSI or FiberChannel) or NFS. The remaining fields in the screen vary "
+"depending on what you choose here."
+msgstr "**协议** 对于XenServer，选择NFS, iSCSI, 或 PreSetup.对于KVM，选择NFS, SharedMountPoint,CLVM, 或RBD.对于VSPHERE，选择VMFS（iSCSI 或FiberChannel）或NFS。本栏的其它选择依你选项不同而不同。"
+
+# dbd90d6e53d34d4cad8f2c3a097f5917
+#: ../../configuration.rst:694
+msgid "NFS"
+msgstr "NFS"
+
+# d905c0e524884434bbce1a596ab9e8ae
+# adc6172c6fb94c9e808ea5729ec0015e
+# 9564e49540d445a6a796666072388c85
+#: ../../configuration.rst:694 ../../configuration.rst:702
+#: ../../configuration.rst:713
+msgid "**Server.** The IP address or DNS name of the storage device."
+msgstr "**服务器** 存储设备的IP地址或DNS解析名称。"
+
+# 50bc8991790d4273aa59efd2d73b42f2
+# 8920e004ba914957be0b285c5b9566a0
+#: ../../configuration.rst:696 ../../configuration.rst:757
+msgid "**Path.** The exported path from the server."
+msgstr "**路径.** 服务器输出的存储路径。"
+
+# 66e08a767e8e407c91c01e0b57c9c4d5
+# b827c64c04014e0ca658487659b87b6e
+# 8f3262da3e114bf5bf62741b9284b984
+# b147800ccb4948659610f3b243d04b72
+# 669620fc4f1a4de9b9b00aeddbf9432a
+#: ../../configuration.rst:698 ../../configuration.rst:709
+#: ../../configuration.rst:718 ../../configuration.rst:725
+#: ../../configuration.rst:735
+msgid ""
+"**Tags (optional).** The comma-separated list of tags for this storage "
+"device. It should be an equivalent set or superset of the tags on your disk "
+"offerings."
+msgstr "**标签.** (可选项)以逗号分隔的一系列存储设备的标签。它应该是磁盘方案中标签的等价集合或者父集。"
+
+# fffee6632fb244ef9ee793f9ea6fae65
+#: ../../configuration.rst:702
+msgid "iSCSI"
+msgstr "iSCSI"
+
+# cab8f091a9bd419abee44664e284f629
+#: ../../configuration.rst:704
+msgid ""
+"**Target IQN.** The IQN of the target. For example, "
+"iqn.1986-03.com.sun:02:01ec9bb549-1271378984."
+msgstr "**Target IQN.** ISCSI target的IQN编号，格式如：iqn.1986-03.com.sun:02:01ec9bb549-1271378984。"
+
+# 66b75a8b32674947875a04ab9de122c9
+#: ../../configuration.rst:707
+msgid "**Lun.** The LUN number. For example, 3."
+msgstr "**Lun.** LUN编号。比如：3。"
+
+# 604eb8fc1cff40e5bb3760beef6766f0
+#: ../../configuration.rst:713
+msgid "preSetup"
+msgstr "preSetup"
+
+# b99f246bfc974f48933179b70c1d0668
+#: ../../configuration.rst:715
+msgid ""
+"**SR Name-Label.** Enter the name-label of the SR that has been set up "
+"outside CloudStack."
+msgstr "**SR 名称标签** 输入在CLOUDSTACK外部设置好的SR的名称标签。"
+
+# b1b68aca6c6c4ff2bc13b7e384154ed7
+#: ../../configuration.rst:722
+msgid "SharedMountPoint"
+msgstr "SharedMountPoint"
+
+# a2563f947f8142b9a8ba024d822e6d8f
+#: ../../configuration.rst:722
+msgid ""
+"**Path.** The path on each host that is where this primary storage is "
+"mounted. For example, \"/mnt/primary\"."
+msgstr "**路径.**每一个主机的主存储的挂载路径。格式如 \"/mnt/primary\"。"
+
+# abbb3c959ada42e28ca5963f413c6f36
+#: ../../configuration.rst:729
+msgid "VMFS"
+msgstr "VMFS"
+
+# 4ec550d124a34334868e01b615fd7cf8
+#: ../../configuration.rst:729
+msgid "**Server.** The IP address or DNS name of the vCenter server."
+msgstr "**服务器** vCenter服务器的IP地址或DNS名称。"
+
+# daadb05d2bbb451c921f7924eafc3bba
+#: ../../configuration.rst:731
+msgid ""
+"**Path.** A combination of the datacenter name and the datastore name. The "
+"format is \"/\" datacenter name \"/\" datastore name. For example, "
+"\"/cloud.dc.VM/cluster1datastore\"."
+msgstr "**路径** 这是一个datacenter name 和 datastore name集成在一起的名字。格式如\"/\" datacenter name \"/\" datastore name. 示例： \"/cloud.dc.VM/cluster1datastore\"."
+
+# cc85beb87ff14852b2e9293f8884c708
+# 3c79b79a17014af1bc0392d7137b940b
+#: ../../configuration.rst:741 ../../configuration.rst:1230
+msgid ""
+"The tag sets on primary storage across clusters in a Zone must be identical."
+" For example, if cluster A provides primary storage that has tags T1 and T2,"
+" all other clusters in the Zone must also provide primary storage that has "
+"tags T1 and T2."
+msgstr "在区域的群集中当，主存储的标签都必须是唯一的。比如，如果你在A群集当中提供的主存储的标签为T1和T2，那么，你在同一个区域的另一个群集提供的主存储标签也必须为T1和T2。"
+
+# 77dd355c1a1b48318b9b054f5698f6db
+#: ../../configuration.rst:746
+msgid ""
+"In a new zone, CloudStack adds the first secondary storage server for you. "
+"For an overview of what secondary storage is, see `“About Secondary Storage”"
+" "
+"<http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods"
+"#about-secondary-storage>`_."
+msgstr "在一个新的区域里，CLOUDSTACK会添加第一个二级存储。关于什么是二级存储，请参阅 `“关于辅助存储” <http://docs.cloudstack.apache.org/en/latest/concepts.html?highlight=about%20pods#about-secondary-storage>`_。"
+
+# 9ffcbb5748c44307afcb86b84bef2bd8
+#: ../../configuration.rst:750
+msgid ""
+"Before you can fill out this screen, you need to prepare the secondary "
+"storage by setting up NFS shares and installing the latest CloudStack System"
+" VM template. See Adding Secondary Storage :"
+msgstr "当你在填写这些信息时，你需要准备好二级存储的NFS共享，并且安装好CLOUDSTACK最新的系统虚拟机模板。更多信息，可以查看Adding Secondary Storage :"
+
+# fcc9a36dd6c749198217088bf5381ee2
+#: ../../configuration.rst:754
+msgid ""
+"**NFS Server.** The IP address of the server or fully qualified domain name "
+"of the server."
+msgstr "**NFS服务器** NFS服务器的IP地址或相应域名。"
+
+# d656e3c4d2c14785a91388ffd2a2e0da
+#: ../../configuration.rst:759
+msgid "Click Launch."
+msgstr "点击启动"
+
+# e5249101b498485c840bf4c9715351d8
+#: ../../configuration.rst:765
+msgid "Adding a Pod"
+msgstr "添加一个机柜提供点"
+
+# 80ce36fa017948b38ec42cdabd458282
+#: ../../configuration.rst:767
+msgid ""
+"When you created a new zone, CloudStack adds the first pod for you. You can "
+"add more pods at any time using the procedure in this section."
+msgstr "当你添加一个区域时，CLOUDSTACK会添加第一个机柜提供点。用本章节的办法，你可以随时添加更多的机柜提供点。"
+
+# 1a095154f142425dbfdaedb0e4ea3a1b
+#: ../../configuration.rst:770
+msgid ""
+"Log in to the CloudStack UI. See `“Log In to the UI” "
+"<http://docs.cloudstack.apache.org/projects/cloudstack-"
+"administration/en/latest/ui.html#log-in-to-the-ui>`_."
+msgstr "登陆到CloudStack用户界面。参阅 `“登录用户界面” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_."
+
+# 4b20a9fd84f2479a9b463179b2c04d3c
+#: ../../configuration.rst:773
+msgid ""
+"In the left navigation, choose Infrastructure. In Zones, click View More, "
+"then click the zone to which you want to add a pod."
+msgstr "在左侧的导航栏里，选择基础架构。在区域栏目里，选择查看全部。然后，点击相应的区域以添加新的机柜提供点。"
+
+# 1ceafce4645345f8984ba3e1f562f435
+#: ../../configuration.rst:776
+msgid ""
+"Click the Compute and Storage tab. In the Pods node of the diagram, click "
+"View All."
+msgstr "点击计算和存储标签。在图中的机柜提供点里，点击查看全部。"
+
+# 3c5e8d963225430ca2e31368837c3d6a
+#: ../../configuration.rst:779
+msgid "Click Add Pod."
+msgstr "点击增加提供点。（此处提供点对应于翻译此翻译文档的机柜提供点）"
+
+# 8209d5987fa14c1fa7d44d186705d0c9
+#: ../../configuration.rst:781
+msgid "Enter the following details in the dialog."
+msgstr "在随后的对话栏里，输入以下细节信息。"
+
+# d3f7f6f5ca814cc3b14a99cd76ae042d
+#: ../../configuration.rst:783
+msgid "**Name.** The name of the pod."
+msgstr "**名称** 机柜提供点名称"
+
+# f7c4912b240c487eaa879e309615b020
+#: ../../configuration.rst:785
+msgid "**Gateway.** The gateway for the hosts in that pod."
+msgstr "**网关.** 机柜提供点的网关。"
+
+# 914c5b1a1c8c4530999080d4c89912e6
+#: ../../configuration.rst:787
+msgid ""
+"**Netmask.** The network prefix that defines the pod's subnet. Use CIDR "
+"notation."
+msgstr "**网络** 定义这个提供点的子网络前缀。用CIDR格式。"
+
+# 80f5b85272584772b1caa17474ea4863
+# ba52d2639a9a44a394ac0e6d13cbbfff
+# 35b375637fca46aabc7848985f6ba3da
+#: ../../configuration.rst:795 ../../configuration.rst:830
+#: ../../configuration.rst:1235
+msgid "Click OK."
+msgstr "点击确定。"
+
+# f12f333c032e4bf6b2906a933d4da17e
+#: ../../configuration.rst:801
+msgid "Adding a Cluster"
+msgstr "添加群集"
+
+# 77eccc1ced604f3482969b1b37ac94f7
+#: ../../configuration.rst:803
+msgid ""
+"You need to tell CloudStack about the hosts that it will manage. Hosts exist"
+" inside clusters, so before you begin adding hosts to the cloud, you must "
+"add at least one cluster."
+msgstr "你需要告诉CLOUDSTACK它所能管理的宿主机。宿主机存在于群集内，所以，在为云里添加主机之后，必须先至少存在一个群集。"
+
+# 2541d85ea4c64120ba7c1d1bbdb0de54
+#: ../../configuration.rst:809
+msgid "Add Cluster: KVM or XenServer"
+msgstr "添加群集：KVM 或者 XenServer"
+
+# a19c5e6d471b43ce9df963073e844a41
+#: ../../configuration.rst:811
+msgid ""
+"These steps assume you have already installed the hypervisor on the hosts "
+"and logged in to the CloudStack UI."
+msgstr "这些步骤确保你已在宿主机上安装好hypervisor，并且已登陆CLOUDSTACK的WEB UI。"
+
+# 0076f4bb3d004b4ba430db294c83e5c6
+# 39ab1bc8c27845f2b2df2deb2c47d959
+#: ../../configuration.rst:814 ../../configuration.rst:863
+msgid ""
+"In the left navigation, choose Infrastructure. In Zones, click View More, "
+"then click the zone in which you want to add the cluster."
+msgstr "在左右的导航栏里，点击基础架构。在区域里，点击查看全部。然后点击你想增加群集所在的区域。"
+
+# f5468a45f1584146b9c21637e83ead16
+# 709bb466c6b74ab1a145f5edd5aa1cc6
+#: ../../configuration.rst:817 ../../configuration.rst:1162
+msgid "Click the Compute tab."
+msgstr "点击计算这个标签。"
+
+# 9c5dcf9e60b74076b98428a9785acffa
+#: ../../configuration.rst:819
+msgid "In the Clusters node of the diagram, click View All."
+msgstr "在对话栏的群集里，点击查看全部。"
+
+# 4ff74ef29511451d84f51b7112d91396
+# 3b57564e3ea441e2a8ba501a340267ca
+#: ../../configuration.rst:821 ../../configuration.rst:871
+msgid "Click Add Cluster."
+msgstr "点击增加群集。"
+
+# 5fe5d5e811774dc483d55f29b28b461c
+#: ../../configuration.rst:823
+msgid "Choose the hypervisor type for this cluster."
+msgstr "选择这个群集的hypervisor类型。"
+
+# 6e00c60f805341cdbfb1583ad80b4c52
+#: ../../configuration.rst:825
+msgid "Choose the pod in which you want to create the cluster."
+msgstr "选择你想在哪个机柜提供点增加群集。"
+
+# f214b054a5844ee380b80bc55b6e9123
+#: ../../configuration.rst:827
+msgid ""
+"Enter a name for the cluster. This can be text of your choosing and is not "
+"used by CloudStack."
+msgstr "为群集输入一个名称。这个名称必须为CLOUDSTACK里没有使用的名字。"
+
+# 1edfca4aeda94b35b4981b9ea1898063
+#: ../../configuration.rst:834
+msgid "Add Cluster: vSphere"
+msgstr "添加群集：vSphere"
+
+# f22ee86140014d7b9d84b11a6b68a5a2
+#: ../../configuration.rst:836
+msgid ""
+"Host management for vSphere is done through a combination of vCenter and the"
+" CloudStack admin UI. CloudStack requires that all hosts be in a CloudStack "
+"cluster, but the cluster may consist of a single host. As an administrator "
+"you must decide if you would like to use clusters of one host or of multiple"
+" hosts. Clusters of multiple hosts allow for features like live migration. "
+"Clusters also require shared storage such as NFS or iSCSI."
+msgstr "对于VSPHERE的主机管理是结合VCENTER和CLOUDSTACK WEB UUI管理界面一起完成的。CLOUDSTACK需要所有的主机都在同一个群集里，但群集可能只是由一个主机构成。作为一个管理员，你必须决定到底是使用一个主机一个群集还是多个主机一个群集。多个主机一个群集，可以实现CLOUDSTACK的一些高级功能，如热迁移等。当然，此群集需要有NFS或ISCSI等这个共享存储支持。"
+
+# 5f108c515fe845f9b12bb18f429e0ea5
+#: ../../configuration.rst:844
+msgid ""
+"For vSphere servers, we recommend creating the cluster of hosts in vCenter "
+"and then adding the entire cluster to CloudStack. Follow these requirements:"
+msgstr "对于VSPHERRE服务器，我们推荐的方案是先在VCENTER里建好群集，然后将整个群集加入到CLOUDSTACK群集中。这个群集需要以下条件："
+
+# 14090efdfc144ee89b2517b48c3cd083
+#: ../../configuration.rst:848
+msgid "Do not put more than 8 hosts in a vSphere cluster"
+msgstr "在一个VSPHOERE群集里不要超过8个主机。"
+
+# 6d06725de8a447bd97bcb18b2abffed6
+#: ../../configuration.rst:850
+msgid ""
+"Make sure the hypervisor hosts do not have any VMs already running before "
+"you add them to CloudStack."
+msgstr "确保在你想加入CLOUDSTACK群集前，VSPHERE没有任何虚拟机。"
+
+# 71a61ae689b14010a3cb30b15dbb6ab4
+#: ../../configuration.rst:853
+msgid "To add a vSphere cluster to CloudStack:"
+msgstr "在CLOUDSTACK中添加一个VSHPERE群集："
+
+# 4aa19eb63fce44d992c239dc22b644c1
+#: ../../configuration.rst:855
+msgid ""
+"Create the cluster of hosts in vCenter. Follow the vCenter instructions to "
+"do this. You will create a cluster that looks something like this in "
+"vCenter."
+msgstr "在VCENTER里新建一个群集。请参看VCENTER的相关操作指地完成这一。在VCENTER里建立群集的大致过程如下："
+
+# f5002325d11f467ebc09a540ab289dc0
+#: ../../configuration.rst:859
+msgid "|vsphereclient.png: vSphere client|"
+msgstr "|vsphereclient.png: vSphere client|"
+
+# 2b550bfb1de24c2491dfb5e097ddfc06
+#: ../../configuration.rst:861
+msgid "Log in to the UI."
+msgstr "登陆到UI界面。"
+
+# 2ebc1409a3524a92806ce241e7ade87c
+#: ../../configuration.rst:866
+msgid ""
+"Click the Compute tab, and click View All on Pods. Choose the pod to which "
+"you want to add the cluster."
+msgstr "点击计算标签。在机柜提供点栏里点击查看全部。选择你想添加群集的机柜提供点。"
+
+# 7ea5c0a4d69542b68fdc461c256fc48d
+#: ../../configuration.rst:869
+msgid "Click View Clusters."
+msgstr "点击查看群集。"
+
+# 49994ac34ee547f48952a29df8e41fcb
+#: ../../configuration.rst:873
+msgid "In Hypervisor, choose VMware."
+msgstr "在Hypervisor里，选择VMware。"
+
+# eedcbf466c594bd7b3fd86bfe04241b1
+#: ../../configuration.rst:875
+msgid ""
+"Provide the following information in the dialog. The fields below make "
+"reference to the values from vCenter."
+msgstr "提供界面要求的如下信息。这些信息的值可以参考VCENTER中对应的值。"
+
+# 89c59dc2d27e4303ae86550eed8821f6
+#: ../../configuration.rst:878
+msgid "|addcluster.png: add a cluster|"
+msgstr "|addcluster.png: add a cluster|"
+
+# 853a36fa7aba43bb89623403046e9971
+#: ../../configuration.rst:880
+msgid ""
+"**Cluster Name**: Enter the name of the cluster you created in vCenter. For "
+"example, \"cloud.cluster.2.2.1\""
+msgstr "**群集名称**:输入你在VCENTER中创建的群集名称。比如：\"cloud.cluster.2.2.1\""
+
+# 80bdf696d0944d3b82144716a5c808b5
+#: ../../configuration.rst:883
+msgid ""
+"**vCenter Username**: Enter the username that CloudStack should use to "
+"connect to vCenter. This user must have all the administrative privileges."
+msgstr "**vCenter用户名**:输入CLOUDSTACK连接到VCENTER所用的用户名。这个用户名必须要有所有的管理权限。"
+
+# bea1b4e2088642d5b0b8aac382efa2dd
+#: ../../configuration.rst:887
+msgid ""
+"**CPU overcommit ratio**: Enter the CPU overcommit ratio for the cluster. "
+"The value you enter determines the CPU consumption of each VM in the "
+"selected cluster. By increasing the over-provisioning ratio, more resource "
+"capacity will be used. If no value is specified, the value is defaulted to "
+"1, which implies no over-provisioning is done."
+msgstr "**CPU超配比率**: 输入此群集的CPU超配比率。这个比率值决定了群集内每台虚拟机的CPU耗用比率。增加这个数据，则能使用更多的资源。如果不设置此值的话，默认值为1，这就表示没有使用超配。"
+
+# 0d13e425b64444619a542ae57d648966
+#: ../../configuration.rst:894
+msgid ""
+"**RAM overcommit ratio**: Enter the RAM overcommit ratio for the cluster. "
+"The value you enter determines the memory consumption of each VM in the "
+"selected cluster. By increasing the over-provisioning ratio, more resource "
+"capacity will be used. If no value is specified, the value is defaulted to "
+"1, which implies no over-provisioning is done."
+msgstr "**RAM超配比率**:输入RAM的超配比率。这个比率值决定了群集内每台虚拟机的MEM耗用比率。增加这个数据，则能使用更多的资源。如果不设置此值的话，默认值为1，这就表示没有使用超配。"
+
+# c5e25f8ee3a543a19ffec688a6731589
+#: ../../configuration.rst:901
+msgid ""
+"**vCenter Host**: Enter the hostname or IP address of the vCenter server."
+msgstr "**vCenter主机**: VCENTER的主机的IP地址或主机名。"
+
+# 0a0d7a14d3624f1fbfa7507c8e4b35e9
+#: ../../configuration.rst:904
+msgid "**vCenter Password**: Enter the password for the user named above."
+msgstr "**vCenter密码**: 输入上面用户的密码。"
+
+# 10d54005fb6448748362e84d4f269999
+#: ../../configuration.rst:906
+msgid ""
+"**vCenter Datacenter**: Enter the vCenter datacenter that the cluster is in."
+" For example, \"cloud.dc.VM\"."
+msgstr "**vCenter Datacenter**:输入此群集拥有的vCenter Datacenter名称，比如：\"cloud.dc.VM\"."
+
+# 286a6873beb04a32af8b8b30acee427c
+#: ../../configuration.rst:909
+msgid ""
+"**Override Public Traffic**: Enable this option to override the zone-wide "
+"public traffic for the cluster you are creating."
+msgstr "**重用公共网络流量**:启用这个选项，则可以在区域的范围内重用公共网络流量。"
+
+# 3a820c902ce946538b1e2514136264dc
+#: ../../configuration.rst:912
+msgid ""
+"**Public Traffic vSwitch Type**: This option is displayed only if you enable"
+" the Override Public Traffic option. Select a desirable switch. If the "
+"vmware.use.dvswitch global parameter is true, the default option will be "
+"VMware vNetwork Distributed Virtual Switch."
+msgstr "**公共流量vSwitch类型**: 这个选项只有在你启用了Override Public Traffic之后才会显示出来，你可以选择一种合适的虚拟交换机。如果vmware.use.dvswitch这个全局参数设置为true，则默认选项为VMware vNetwork Distributed Virtual Switch."
+
+# cee24debf6244e6ab8f2960f82cf02dc
+# 28a4eb955bf748c3a88d2d89ce8c5074
+#: ../../configuration.rst:917 ../../configuration.rst:939
+msgid ""
+"If you have enabled Nexus dvSwitch in the environment, the following "
+"parameters for dvSwitch configuration are displayed:"
+msgstr "如果你启用了Nexus dvSwitch，下面关于dvSwitch的数据也需要设置："
+
+# d2da6ea28c614ba38eb47ed7e3077ae0
+# 8e33cb040d534b0fa0d115e687ed7610
+#: ../../configuration.rst:920 ../../configuration.rst:942
+msgid "Nexus dvSwitch IP Address: The IP address of the Nexus VSM appliance."
+msgstr "Nexus dvSwitch IP地址: Nexus VSM的IP地址"
+
+# e80bc1882c6c476fa8900e09c5b863e3
+# df90310163a24464b7c5b02335487fdb
+#: ../../configuration.rst:923 ../../configuration.rst:945
+msgid ""
+"Nexus dvSwitch Username: The username required to access the Nexus VSM "
+"appliance."
+msgstr "Nexus dvSwitch 用户名：具体有 Nexus VSM 权限的用户名。"
+
+# f8aeaf74318541b7b199a22f1215f4db
+# f403066f05f9414a8fef9581e1f63c46
+#: ../../configuration.rst:926 ../../configuration.rst:948
+msgid ""
+"Nexus dvSwitch Password: The password associated with the username specified"
+" above."
+msgstr "Nexus dvSwitch 密码:上面用户名的密码。"
+
+# b2c37a024feb4704b1af4daaf9f7d7dc
+#: ../../configuration.rst:929
+msgid ""
+"**Override Guest Traffic**: Enable this option to override the zone-wide "
+"guest traffic for the cluster you are creating."
+msgstr "**重用客户机流量**:如果选中此项，则会在全区域范围内重用客户机流量。"
+
+# 94030e337615408390ee4c90fa68dc1f
+#: ../../configuration.rst:932
+msgid ""
+"**Guest Traffic vSwitch Type**: This option is displayed only if you enable "
+"the Override Guest Traffic option. Select a desirable switch."
+msgstr "**Guest Traffic vSwitch Type**:只有当the Override Guest Traffic选项启用后才会出现。为此选择一种合适的虚拟交换机类型。"
+
+# 079f9e30e5664e1a85085b94865eb456
+#: ../../configuration.rst:936
+msgid ""
+"If the vmware.use.dvswitch global parameter is true, the default option will"
+" be VMware vNetwork Distributed Virtual Switch."
+msgstr "如果全局参数vmware.use.dvswitch为true，则默认的选项为VMware vNetwork Distributed Virtual Switch。"
+
+# baa8eb555037420bb51856abdd7fe8f2
+#: ../../configuration.rst:951
+msgid ""
+"There might be a slight delay while the cluster is provisioned. It will "
+"automatically display in the UI."
+msgstr "当群集建好之后，会有稍稍的迟延之后，才会有UI里显示出来。"
+
+# e1f90b62159d4513baedd2e01440755a
+#: ../../configuration.rst:958
+msgid "Adding a Host"
+msgstr "添加一个宿主机"
+
+# 0923b6cb19c147c7b758d17ba052cb1f
+#: ../../configuration.rst:960
+msgid ""
+"Before adding a host to the CloudStack configuration, you must first install"
+" your chosen hypervisor on the host. CloudStack can manage hosts running VMs"
+" under a variety of hypervisors."
+msgstr "当你在添加一个新的宿主机之后，你必须先在宿主机上安装一种hypervisor。CLOUDSTACK是可以管理多种hypervisor的。"
+
+# 5bf89c193bf649468f17106c9cc7dc79
+#: ../../configuration.rst:964
+msgid ""
+"The CloudStack Installation Guide provides instructions on how to install "
+"each supported hypervisor and configure it for use with CloudStack. See the "
+"appropriate section in the Installation Guide for information about which "
+"version of your chosen hypervisor is supported, as well as crucial "
+"additional steps to configure the hypervisor hosts for use with CloudStack."
+msgstr "CLOUDSTACK安装指南提供了如何安装配置各种hypervisor的步骤。你可以参考相关章节找到你所使用的hypervisor的安装指南，以及为了加入CLOUDSTACK而需要的额外的配置步骤。"
+
+# ff2e79d3bba8422d8b74b3a78eb133a7
+#: ../../configuration.rst:972
+msgid ""
+"Be sure you have performed the additional CloudStack-specific configuration "
+"steps described in the hypervisor installation section for your particular "
+"hypervisor."
+msgstr "确保你已按CLOUDSTACK的要求，安装并设置好了hypervisor。"
+
+# ecd653992432482b93207c1b1d4b1503
+#: ../../configuration.rst:976
+msgid ""
+"Now add the hypervisor host to CloudStack. The technique to use varies "
+"depending on the hypervisor."
+msgstr "现在，可以添加hypervisor主机到CLOUDSTACK了。具体的添加技巧和过程取决于使选用的hypervisor类型。"
+
+# 22d66ee649304664855c3570b38b51c3
+#: ../../configuration.rst:979
+msgid ":ref:`adding-a-host-xenserver-kvm`"
+msgstr ":ref:`adding-a-host-xenserver-kvm`"
+
+# 04cf8556d81441d9915194885f3f28c8
+#: ../../configuration.rst:981
+msgid ":ref:`adding-a-host-vsphere`"
+msgstr ":ref:`adding-a-host-vsphere`"
+
+# 1d939abd524b4701b1f7ba65cfb70da2
+#: ../../configuration.rst:987
+msgid "Adding a Host (XenServer or KVM)"
+msgstr "添加一个宿主机(XenServer 或KVM)"
+
+# af116bf381dc4f9ea38ec2f5625bc8a5
+#: ../../configuration.rst:989
+msgid "XenServer and KVM hosts can be added to a cluster at any time."
+msgstr "XenServer和KVM可以在任何时间被加入CLOUDSTACK群集。"
+
+# e59027be4a9846a9845b33dd15d6649a
+#: ../../configuration.rst:993
+msgid "Requirements for XenServer and KVM Hosts"
+msgstr " XenServer和KVM宿主机的相关要求"
+
+# e6025f03b3ce477c9d135377a7894528
+#: ../../configuration.rst:996
+msgid ""
+"Make sure the hypervisor host does not have any VMs already running before "
+"you add it to CloudStack."
+msgstr "确保 hypervisor在加入CLOUDSTACK前没有运行任何虚拟机。"
+
+# a7d22455a14846d98f150dbeeae218f0
+#: ../../configuration.rst:999
+msgid "Configuration requirements:"
+msgstr "配置需求："
+
+# e5160a3fa2ec40919c557a6935f3fe1f
+#: ../../configuration.rst:1001
+msgid "Each cluster must contain only hosts with the identical hypervisor."
+msgstr "每一个群集必须包含相同的 hypervisor。"
+
+# cdfb38a316e3459e9e52ea228402b66c
+#: ../../configuration.rst:1003
+msgid "For XenServer, do not put more than 8 hosts in a cluster."
+msgstr "对于 XenServer，群集内不要超过8个主机。"
+
+# b4a9938b72044be7bd458f16ed719e81
+#: ../../configuration.rst:1005
+msgid "For KVM, do not put more than 16 hosts in a cluster."
+msgstr "对于KVM，每一个群集不要超过16个主机。"
+
+# 2f1baf980a734a43baf993d791d4d8c5
+#: ../../configuration.rst:1007
+msgid ""
+"For hardware requirements, see the installation section for your hypervisor "
+"in the CloudStack Installation Guide."
+msgstr "硬件方面的需求，请参看CLOUDSTACK安装指南中关于你具体安装的hypervisor的要求。"
+
+# 5b7b02ee375a45adaad6da800cd483c3
+#: ../../configuration.rst:1012
+msgid "XenServer Host Additional Requirements"
+msgstr "XenServe宿主机的额外要求"
+
+# 27ea0fe70f034e44a3904e6c7ca6afa4
+#: ../../configuration.rst:1014
+msgid ""
+"If network bonding is in use, the administrator must cable the new host "
+"identically to other hosts in the cluster."
+msgstr "如果使用了网卡绑定，管理员必须和群集中其它主机一样连接网线到这个新的主机"
+
+# 05d3932560e04019b3bdb344f870f538
+#: ../../configuration.rst:1017
+msgid ""
+"For all additional hosts to be added to the cluster, run the following "
+"command. This will cause the host to join the master in a XenServer pool."
+msgstr "对于要加入群集的其它主机，运行下面的命令就会将主机加入XenServer计算池内。"
+
+# 286ea98fd2d747c483da6d96983d5c9f
+#: ../../configuration.rst:1026
+msgid ""
+"When copying and pasting a command, be sure the command has pasted as a "
+"single line before executing. Some document viewers may introduce unwanted "
+"line breaks in copied text."
+msgstr "当复制和粘贴命令时，请确保没有多余的换行符，因为一些文档查看器可能会在复制时加上换行符。"
+
+# 354fed2a8e2a4333a32b9a35786ca935
+#: ../../configuration.rst:1030
+msgid ""
+"With all hosts added to the XenServer pool, run the cloud-setup-bond script."
+" This script will complete the configuration and setup of the bonds on the "
+"new hosts in the cluster."
+msgstr "当所有主机都加入XenServer计算池后，运行cloud-setup-bond脚本。这个脚本将会完成配置工作，并且在群集的新主机里设置相关的绑定。"
+
+# c4cd2afe3b934ce8b2621d0b9e82c2d2
+#: ../../configuration.rst:1034
+msgid ""
+"Copy the script from the Management Server in /usr/share/cloudstack-"
+"common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh to the master "
+"host and ensure it is executable."
+msgstr "将管理服务器中/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh拷贝到master主机中并确认该脚本可执行。"
+
+# 0e532bee249b496b88f2c7475bdf97f8
+#: ../../configuration.rst:1038
+msgid "Run the script:"
+msgstr "运行脚本："
+
+# e7009690c4b6478ba5f35649f9e09436
+#: ../../configuration.rst:1046
+msgid "KVM Host Additional Requirements"
+msgstr "KVM主机的额外要求"
+
+# 37a3fd672bc54d768a466c6ba3dae54f
+#: ../../configuration.rst:1048
+msgid ""
+"If shared mountpoint storage is in use, the administrator should ensure that"
+" the new host has all the same mountpoints (with storage mounted) as the "
+"other hosts in the cluster."
+msgstr "如果使用了共享挂载存储，则管理员要确保群集里所有新机方和其它主机一样有相同的存储挂载点。"
+
+# 710951bf6c5a4eed831cc19f7be18c01
+#: ../../configuration.rst:1052
+msgid ""
+"Make sure the new host has the same network configuration (guest, private, "
+"and public network) as other hosts in the cluster."
+msgstr "确保新主机和群集内其它主机有一个的网络设置（客户机，内网，外网网络）。"
+
+# 7a50d92cb76b43c68381d14e04aed486
+#: ../../configuration.rst:1055
+msgid ""
+"If you are using OpenVswitch bridges edit the file agent.properties on the "
+"KVM host and set the parameter network.bridge.type to openvswitch before "
+"adding the host to CloudStack"
+msgstr "如果在CLOUDSTACK中使用了OpenVswitch网桥，则在操作前，需要将KVM计算主机上的agent.properties文件的network.bridge.type参数设置为openvswitch。"
+
+# 332d12a13d1f4216b74187cf129bc664
+#: ../../configuration.rst:1061
+msgid "Adding a XenServer or KVM Host"
+msgstr "添加一个新的XenServer或KVM主机"
+
+# cfba9ce6e7f14afebd66671f11feaacf
+#: ../../configuration.rst:1063
+msgid ""
+"If you have not already done so, install the hypervisor software on the "
+"host. You will need to know which version of the hypervisor software version"
+" is supported by CloudStack and what additional configuration is required to"
+" ensure the host will work with CloudStack. To find these installation "
+"details, see the appropriate section for your hypervisor in the CloudStack "
+"Installation Guide."
+msgstr "如果你还没有这么作，就需要在主机上安装hypervisor软件。你需要知道CLOUDSTACK支持哪些hypervisor，以及主机上还需要哪个特别的配置。可以参看CLOUDSTACK安装指南的相关章节，找到具体的安装信息。"
+
+# 377e41a476e54f4c82f0d00d304e2693
+#: ../../configuration.rst:1070
+msgid "Log in to the CloudStack UI as administrator."
+msgstr "作为管理员登录到CloudStack用户界面。"
+
+# 7ac765edde2443be9069abb07cd4d0db
+#: ../../configuration.rst:1072
+msgid ""
+"In the left navigation, choose Infrastructure. In Zones, click View More, "
+"then click the zone in which you want to add the host."
+msgstr "在左边的导航栏里，点击区域基础架构。在区域里，点击查看全部。然后在相应的区域里添加主机。"
+
+# a4431e8197e24d1f8565b3bb92bca888
+#: ../../configuration.rst:1075
+msgid "Click the Compute tab. In the Clusters node, click View All."
+msgstr "点击计算标签。在群集节点里，点击查看全部。"
+
+# 362b6eed173f4b5f8f7b38ebe0958336
+#: ../../configuration.rst:1077
+msgid "Click the cluster where you want to add the host."
+msgstr "在相应的群集里添加主机。"
+
+# effdebcf4be849f2962ad4550751244d
+#: ../../configuration.rst:1079
+msgid "Click View Hosts."
+msgstr "点击查看主机。（此处主机即可此翻译文档中宿主机的同一概念。）"
+
+# 4c39fa71f4fc425abb83949d1b5ed506
+#: ../../configuration.rst:1081
+msgid "Click Add Host."
+msgstr "点击添加主机"
+
+# 5ffcb71d5a1b46ebabc4fcf190e75753
+#: ../../configuration.rst:1083
+msgid "Provide the following information."
+msgstr "提供主机的如下信息。"
+
+# 88888fd494694d8d8075b9131573228f
+#: ../../configuration.rst:1085
+msgid "Host Name. The DNS name or IP address of the host."
+msgstr "主机名---此主机的IP地址或DNS名称。"
+
+# c26fe06e5a564c628de75c1d4fe93d68
+#: ../../configuration.rst:1087
+msgid "Username. Usually root."
+msgstr "用户名--通常为root用户。"
+
+# 2b09fc60175b45d5b24a1c0574fc275f
+#: ../../configuration.rst:1089
+msgid ""
+"Password. This is the password for the user from your XenServer or KVM "
+"install)."
+msgstr "密码---这通常是指XenServer或KVM安装时设置好的密码。"
+
+# 6b228c164605432b8fbf4c3345a73413
+#: ../../configuration.rst:1092
+msgid ""
+"Host Tags (Optional). Any labels that you use to categorize hosts for ease "
+"of maintenance. For example, you can set to the cloud's HA tag (set in the "
+"ha.tag global configuration parameter) if you want this host to be used only"
+" for VMs with the \"high availability\" feature enabled. For more "
+"information, see HA-Enabled Virtual Machines as well as HA for Hosts."
+msgstr "主机标签(可选)。此标签用于将主机分类，以便更好的后期维护。比如，如果你只想此宿主机用于具有HA（high availability）高可用性能的虚拟机，那么，你可以将此宿主机设置为云里相关的HA标签。(参看全局设置参数里的ha.tag)，关于HA的更多信息，请参看HA虚拟机和HA宿主机的相关章节。"
+
+# 9be1b413f34f45e2871035d35715659a
+#: ../../configuration.rst:1099
+msgid ""
+"There may be a slight delay while the host is provisioned. It should "
+"automatically display in the UI."
+msgstr "在主机添加好之后，可能会有稍稍的延迟才会有WEB UI界面中显示出来。"
+
+# cdc3acb163fc410bbca13f2bd37b0775
+#: ../../configuration.rst:1102
+msgid "Repeat for additional hosts."
+msgstr "在其它宿主机上复杂此操作过程。"
+
+# fb2b5c33309149d1b6b0d0ac9e73c5fb
+#: ../../configuration.rst:1108
+msgid "Adding a Host (vSphere)"
+msgstr "添加一个宿主机(vSphere)"
+
+# be6b7ef5fe374f84ac9e6e487404ab78
+#: ../../configuration.rst:1110
+msgid ""
+"For vSphere servers, we recommend creating the cluster of hosts in vCenter "
+"and then adding the entire cluster to CloudStack. See Add Cluster: vSphere."
+msgstr "对于vSphere主机，我们推荐先在VCENTER里建好群集，然后将整个群集加入CLOUDSTACK。关于如何在VCENTER里添加群集，可以参看VSPHERE的相关内容章节。"
+
+# 99be6cf56ded43aba5cd4d8e19f0ace3
+#: ../../configuration.rst:1118
+msgid "Add Primary Storage"
+msgstr "添加主存储"
+
+# 22065a62af1642d3bc3ea2ed32396bac
+#: ../../configuration.rst:1121
+msgid "System Requirements for Primary Storage"
+msgstr "主存储的系统需求"
+
+# 936b5d62d1b14484a4b62a45ed972c59
+#: ../../configuration.rst:1123
+msgid "Hardware requirements:"
+msgstr "硬件要求："
+
+# f209dd840aec4701bdad045e39dc292e
+#: ../../configuration.rst:1125
+msgid ""
+"Any standards-compliant iSCSI, SMB, or NFS server that is supported by the "
+"underlying hypervisor."
+msgstr "以下的hypervisor都支持标准化的iSCSI, SMB, 或 NFS服务器。"
+
+# e3547549b19e48af957483aebd01db56
+#: ../../configuration.rst:1128
+msgid ""
+"The storage server should be a machine with a large number of disks. The "
+"disks should ideally be managed by a hardware RAID controller."
+msgstr "存储服务器应该配置大容量硬盘，且硬盘配置硬件RAID控制器。"
+
+# c31ea6b6b7bc46d98ae721c07b56b50e
+#: ../../configuration.rst:1131
+msgid "Minimum required capacity depends on your needs."
+msgstr "最小容量取决于你的需求。"
+
+# cdb1be7fc7ea4f5b973a9b1c27463a6d
+#: ../../configuration.rst:1133
+msgid "When setting up primary storage, follow these restrictions:"
+msgstr "当添加主存储时，存在以下这些限制："
+
+# 42e4d357c3b747ec85130e77229e624a
+#: ../../configuration.rst:1135
+msgid ""
+"Primary storage cannot be added until a host has been added to the cluster."
+msgstr "在主机成功加入群集之后才能添加主存储。"
+
+# fc583ad97a214096a21288c09b52d080
+#: ../../configuration.rst:1138
+msgid ""
+"If you do not provision shared primary storage, you must set the global "
+"configuration parameter system.vm.local.storage.required to true, or else "
+"you will not be able to start VMs."
+msgstr "当你没有共享的主存储时，则必须将全局参数的system.vm.local.storage.required设置为true,否则，将不能启动虚拟机。"
+
+# 3533708ed0ae435cb0a572d791d9715e
+#: ../../configuration.rst:1144
+msgid "Adding Primary Storage"
+msgstr "添加主存储"
+
+# 0fae53d8c0214c6bb4e92841b8ee4a48
+#: ../../configuration.rst:1146
+msgid ""
+"When you create a new zone, the first primary storage is added as part of "
+"that procedure. You can add primary storage servers at any time, such as "
+"when adding a new cluster or adding more servers to an existing cluster."
+msgstr "当你添加一个新的区域时，主存储作为操作过程的一个步骤已建好。以后，你也可以随时添加主存储。当在添加新的群集或是添加新的主机时都可以添加主存储。"
+
+# e015632ceea7426b8ca21a4fc905bb1e
+#: ../../configuration.rst:1152
+msgid ""
+"When using preallocated storage for primary storage, be sure there is "
+"nothing on the storage (ex. you have an empty SAN volume or an empty NFS "
+"share). Adding the storage to CloudStack will destroy any existing data."
+msgstr "如果提前准备好了主存储，请确认主存储目录里没有任何数据（比如空的SAN卷或NFS共享目录）。将主存储加入CLOUDSTACK时，会清除主存储里的一切数据。"
+
+# 2a0ed458d44e4e95ab93c42eb3a9e935
+#: ../../configuration.rst:1156
+msgid ""
+"Log in to the CloudStack UI (see `“Log In to the UI” "
+"<http://docs.cloudstack.apache.org/projects/cloudstack-"
+"administration/en/latest/ui.html#log-in-to-the-ui>`_)."
+msgstr "登陆CloudStack用户界面。(参阅 `“Log In to the UI” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_)。"
+
+# d5b688c69e784146b9ac0e214c8fe44c
+#: ../../configuration.rst:1158
+msgid ""
+"In the left navigation, choose Infrastructure. In Zones, click View More, "
+"then click the zone in which you want to add the primary storage."
+msgstr "在左侧导航栏中，点击基础架构，在区域中，点击 查看更多，然后点击你所需要添加主存储的区域名称。"
+
+# 1cddd71de6ba4353ab0be25462528358
+#: ../../configuration.rst:1164
+msgid "In the Primary Storage node of the diagram, click View All."
+msgstr "在结构图的主存储节点上，点击 查看全部。"
+
+# d541d83b2a194e519a9ec5df1d98f5b4
+#: ../../configuration.rst:1166
+msgid "Click Add Primary Storage."
+msgstr "点击 添加主存储"
+
+# 5c4a040452d54b77942c8ddae2c6210f
+#: ../../configuration.rst:1168
+msgid ""
+"Provide the following information in the dialog. The information required "
+"varies depending on your choice in Protocol."
+msgstr "提供弹出对话框中所需要的信息。依据你所选协议的不同，所需的信息会有所不同。"
+
+# a693b4b9924b4fa096e546299abb3d47
+#: ../../configuration.rst:1171
+msgid ""
+"**Scope.** Indicate whether the storage is available to all hosts in the "
+"zone or only to hosts in a single cluster."
+msgstr "**范围.** 表明存储是对区域中的所有主机可用或者是仅对单一集群中的主机可用。"
+
+# a142f32de5b64983965c23101102bdfc
+#: ../../configuration.rst:1174
+msgid ""
+"**Pod.** (Visible only if you choose Cluster in the Scope field.) The pod "
+"for the storage device."
+msgstr "**Pod.** (只有在范围域内选择集群时可见)针对存储设备的Pod。"
+
+# fc4673c08bee49338a23afc73b035a4f
+#: ../../configuration.rst:1177
+msgid ""
+"**Cluster.** (Visible only if you choose Cluster in the Scope field.) The "
+"cluster for the storage device."
+msgstr "**集群.** (只有在范围域内选择集群时可见)针对存储设备的集群"
+
+# dd1e29093388466db29061c47fcc2a91
+#: ../../configuration.rst:1182
+msgid ""
+"**Protocol.** For XenServer, choose either NFS, iSCSI, or PreSetup. For KVM,"
+" choose NFS or SharedMountPoint. For vSphere choose either VMFS (iSCSI or "
+"FiberChannel) or NFS. For Hyper-V, choose SMB."
+msgstr "**协议.** 对XenServer主机而言，可以选择NFS，iSCSI或者PreSetup。对KVM而言，可以选择NFS或者ShareMountPoint。对vSphere而言，可以选择NFS或VMFS（iSCSI或FiberChannel，对Hyper-V而言，选择SMB。"
+
+# 5b60e8a893084a1abc56eeaee597e47b
+#: ../../configuration.rst:1187
+msgid ""
+"**Server (for NFS, iSCSI, or PreSetup).** The IP address or DNS name of the "
+"storage device."
+msgstr "**服务器（针对NFS，iSCSI或PreSetup）** 存储设备的IP地址和DNS"
+
+# b65c77d90f5f418e847f3a93e35cb8f9
+#: ../../configuration.rst:1190
+msgid ""
+"**Server (for VMFS).** The IP address or DNS name of the vCenter server."
+msgstr "**服务器（针对VMFS）.** vCenter 服务器的IP地址和DNS"
+
+# 363c9c97e53944328628fd2634c615d4
+#: ../../configuration.rst:1193
+msgid "**Path (for NFS).** In NFS this is the exported path from the server."
+msgstr "**路径(对NFS).** 对NFS协议，这是从服务器上导出的路径"
+
+# 56943b019adc4b9f8a0ed93f8cdf51b4
+#: ../../configuration.rst:1196
+msgid ""
+"**Path (for VMFS).** In vSphere this is a combination of the datacenter name"
+" and the datastore name. The format is \"/\" datacenter name \"/\" datastore"
+" name. For example, \"/cloud.dc.VM/cluster1datastore\"."
+msgstr "**路径（对VMFS）.** 在vSphere中，这是数据中心名称以及数据存储名称的结合。格式如下：\"/\" 数据中心名称 \"/\" 数据存储名称\"。例如：\"/cloud.dc.VM/cluster1datastore\"."
+
+# 2414d9e1191e42bd8fb5c9fdf39bbbd8
+#: ../../configuration.rst:1201
+msgid ""
+"**Path (for SharedMountPoint).** With KVM this is the path on each host that"
+" is where this primary storage is mounted. For example, \"/mnt/primary\"."
+msgstr "**路径(对SharedMountPoint).** 对KVM而言，这是每一个主机上挂载的主存储的路径。例如：\"/mnt/primary\"."
+
+# 2517e36ce3a1410ab5c1978f5ac89313
+#: ../../configuration.rst:1205
+msgid ""
+"**SMB Username** (for SMB/CIFS): Applicable only if you select SMB/CIFS "
+"provider. The username of the account which has the necessary permissions to"
+" the SMB shares. The user must be part of the Hyper-V administrator group."
+msgstr "**SMB 用户名** (for SMB/CIFS)，仅在选择了 SMB/CIFS时可用。此账户针对SMB拥有必要的权限。用户必须是Hyper-V管理组的成员。"
+
+# 58a4a5cad3794a3bac1f01f92fd63e80
+#: ../../configuration.rst:1210
+msgid ""
+"**SMB Password** (for SMB/CIFS): Applicable only if you select SMB/CIFS "
+"provider. The password associated with the account."
+msgstr "**SMB 密码** (for SMB/CIFS)，仅在选择了 SMB/CIFS时可用。此密码与账户关联。"
+
+# 497f1a89318e48a9ad2c06c57111cd9f
+#: ../../configuration.rst:1213
+msgid ""
+"**SMB Domain**\\ (for SMB/CIFS): Applicable only if you select SMB/CIFS "
+"provider. The Active Directory domain that the SMB share is a part of."
+msgstr "**SMB Domain**\\ (for SMB/CIFS)，仅在选择了 SMB/CIFS时可用。SMB共享的活动目录域"
+
+# 2cdf053d64574ee1a6b5879f0ef2807d
+#: ../../configuration.rst:1217
+msgid ""
+"**SR Name-Label (for PreSetup).** Enter the name-label of the SR that has "
+"been set up outside CloudStack."
+msgstr "**SR标签名(针对PreSetup).** 输入被设为外部CloudStack SR的标签名"
+
+# dd903e9085d84fd8afb2fce49b2357f6
+#: ../../configuration.rst:1220
+msgid ""
+"**Target IQN (for iSCSI).** In iSCSI this is the IQN of the target. For "
+"example, iqn.1986-03.com.sun:02:01ec9bb549-1271378984."
+msgstr "**目标IQN(for iSCSI).** 在iSCSI中，这是目标的IQN。例如，iqn.1986-03.com.sun:02:01ec9bb549-1271378984."
+
+# dd7a4bfc0eea4a3dab03d2bafa973633
+#: ../../configuration.rst:1223
+msgid ""
+"**Lun # (for iSCSI).** In iSCSI this is the LUN number. For example, 3."
+msgstr "**Lun # (for iSCSI).** 在iSCSI中，这是LUN的号码，例如： 3."
+
+# 9023364ebc994f959f08b6819c1c4ce6
+#: ../../configuration.rst:1226
+msgid ""
+"**Tags (optional).** The comma-separated list of tags for this storage "
+"device. It should be an equivalent set or superset of the tags on your disk "
+"offerings.."
+msgstr "**标签(可选).** 对此类存储设备以逗号分隔的标签列表。相当于在你磁盘提供者的标签集合或超集。"
+
+# 824ace5e85574e4fb81a6c834d657113
+#: ../../configuration.rst:1239
+msgid "Configuring a Storage Plug-in"
+msgstr "配置存储插件"
+
+# 0bf9f4ce03274fa99551db2eef02d467
+#: ../../configuration.rst:1242
+msgid ""
+"Primary storage that is based on a custom plug-in (ex. SolidFire) must be "
+"added through the CloudStack API (described later in this section). There is"
+" no support at this time through the CloudStack UI to add this type of "
+"primary storage (although most of its features are available through the "
+"CloudStack UI)."
+msgstr ""
+
+# a1da9fd485b44080b384938a6f55a7bd
+#: ../../configuration.rst:1249
+msgid ""
+"The SolidFire storage plug-in for CloudStack is part of the standard "
+"CloudStack install. There is no additional work required to add this "
+"component."
+msgstr "SolidFire存储插件是CloudStack标准安装的一部分，不需要另做其他准备工作。"
+
+# 891dd35a6f6b4cf184d16023fd87a83b
+#: ../../configuration.rst:1253
+msgid ""
+"Adding primary storage that is based on the SolidFire plug-in enables "
+"CloudStack to provide hard quality-of-service (QoS) guarantees."
+msgstr "基于SolidFire插件添加的主存储能够使CloudStack提供较好的QoS保证。"
+
+# 0218d86dac264ce88dc1b3293defc50a
+#: ../../configuration.rst:1256
+msgid ""
+"When used with Compute or Disk Offerings, an administrator is able to build "
+"an environment in which a root or data disk that a user creates leads to the"
+" dynamic creation of a SolidFire volume, which has guaranteed performance. "
+"Such a SolidFire volume is associated with one (and only ever one) "
+"CloudStack volume, so performance of the CloudStack volume does not vary "
+"depending on how heavily other tenants are using the system."
+msgstr ""
+
+# febca3ed36dc41f0bfe48a3170c1b282
+#: ../../configuration.rst:1264
+msgid ""
+"The createStoragePool API has been augmented to support plugable storage "
+"providers. The following is a list of parameters to use when adding storage "
+"to CloudStack that is based on the SolidFire plug-in:"
+msgstr "创建存储池的API已经被扩展到支持插件式存储供应商。下面给出了当向基于SolidFire插件的CloudStack添加存储时可使用的参数列表。"
+
+# 8b10cd104059470bbfbdf014d3db7d1a
+#: ../../configuration.rst:1268
+msgid "command=createStoragePool"
+msgstr "command=createStoragePool"
+
+# b7c687d8637946898d1be0a46f742a61
+#: ../../configuration.rst:1270
+msgid "scope=zone"
+msgstr "scope=区域"
+
+# 051d3b0d6e7440218edb1ce012c5ba48
+#: ../../configuration.rst:1272
+msgid "zoneId=[your zone id]"
+msgstr "zoneId=【你的区域ID】"
+
+# 43e497e6ee76487cb7ef8d43079af1da
+#: ../../configuration.rst:1274
+msgid "name=[name for primary storage]"
+msgstr "name=【主存储的名称】"
+
+# 041976b0584443e5852b0af71eefdb18
+#: ../../configuration.rst:1276
+msgid "hypervisor=Any"
+msgstr "hypervisor=任意"
+
+# 62f2f914fb8544d5b835ee85bff60f35
+#: ../../configuration.rst:1278
+msgid "provider=SolidFire"
+msgstr "provider=SolidFire"
+
+# fcf5466edf494d04957dec9bdfa80299
+#: ../../configuration.rst:1280
+msgid "capacityIops=[whole number of IOPS from the SAN to give to CloudStack]"
+msgstr "capacityIops=【来自SAN的全部IOPS号】"
+
+# 7c4387f9055e4517907fb3bce403cfd0
+#: ../../configuration.rst:1283
+msgid ""
+"capacityBytes=[whole number of bytes from the SAN to give to CloudStack]"
+msgstr "capacityBytes=【来自SAN的全部字节数】"
+
+# be0d75f4832646b88d313275708519bf
+#: ../../configuration.rst:1286
+msgid ""
+"The url parameter is somewhat unique in that its value can contain "
+"additional key/value pairs."
+msgstr "url参数有时是唯一的，他的值可以包含额外的键值对。"
+
+# ac8214aa1a4146599e36ab6ab7c8d513
+#: ../../configuration.rst:1289
+msgid ""
+"url=[key/value pairs detailed below (values are URL encoded; for example, "
+"'=' is represented as '%3D')]"
+msgstr "url=【键值对下面有详细说明（值由url编码，例如，'='编码后为‘%3D’】"
+
+# c35760dbaf9c43e9a3fcba4f07941070
+#: ../../configuration.rst:1292
+msgid ""
+"MVIP%3D[Management Virtual IP Address] (can be suffixed with :[port number])"
+msgstr "MVIP%3D【管理虚拟IP地址】，后面可以使用端口号"
+
+# eec7163645c94befa2b06ef23adf72d1
+#: ../../configuration.rst:1295
+msgid ""
+"SVIP%3D[Storage Virtual IP Address] (can be suffixed with :[port number])"
+msgstr "SVIP%3D【管理虚拟IP地址】，后面可以使用端口号"
+
+# 69688776153943ed92994665eb48f4fb
+#: ../../configuration.rst:1298
+msgid "clusterAdminUsername%3D[cluster admin's username]"
+msgstr "clusterAdminUsername%3D[集群管理员用户名]"
+
+# 660c410694f04bb6a9e49b2f10fb19a5
+#: ../../configuration.rst:1300
+msgid "clusterAdminPassword%3D[cluster admin's password]"
+msgstr "clusterAdminPassword%3D[集群管理员密码]"
+
+# 2f276967210246a7ac29632c437fba98
+#: ../../configuration.rst:1302
+msgid ""
+"clusterDefaultMinIops%3D[Min IOPS (whole number) to set for a volume; used "
+"if Min IOPS is not specified by administrator or user]"
+msgstr "clusterDefaultMinIops%3D[卷的最小IOPS号，在管理员或用户没有给出此号时使用]"
+
+# 503ba3b359a54f4e903c183ec3a434dc
+#: ../../configuration.rst:1305
+msgid ""
+"clusterDefaultMaxIops%3D[Max IOPS (whole number) to set for a volume; used "
+"if Max IOPS is not specified by administrator or user]"
+msgstr "clusterDefaultMaxIops%3D【卷的最大IOPS号，在管理员或用户没有给出此号时使用】"
+
+# bff592567afe42e79eab78de3a4527e8
+#: ../../configuration.rst:1308
+msgid ""
+"clusterDefaultBurstIopsPercentOfMaxIops%3D[Burst IOPS is determined by (Min "
+"IOPS \\* clusterDefaultBurstIopsPercentOfMaxIops parameter) (can be a "
+"decimal value)]"
+msgstr "clusterDefaultBurstIopsPercentOfMaxIops%3D【最小的IOPS \\* clusterDefaultBurstIopsPercentOfMaxIops 参数，可以是十进值】"
+
+# 7f326e7c95a643b5b8f3266987762c9f
+#: ../../configuration.rst:1316
+msgid "Add Secondary Storage"
+msgstr "添加二级存储"
+
+# adab0eb1bee64891b05c676c8825b984
+#: ../../configuration.rst:1319
+msgid "System Requirements for Secondary Storage"
+msgstr "二级存储的系统需求"
+
+# 968a6fc6d0b648b9ad73e20f83ba3013
+#: ../../configuration.rst:1321
+msgid "NFS storage appliance or Linux NFS server"
+msgstr "二级存储器或Linux NFS服务器"
+
+# e9b6a1101247444e8248486d4e144757
+#: ../../configuration.rst:1323
+msgid "SMB/CIFS (Hyper-V)"
+msgstr "SMB/CIFS (Hyper-V)"
+
+# 31aa6daa1e434c0db6e1ea96877e6fc9
+#: ../../configuration.rst:1325
+msgid ""
+"(Optional) OpenStack Object Storage (Swift) (see http://swift.openstack.org)"
+msgstr "（可选）OpenStack Object Storage (Swift) (参见 http://swift.openstack.org)"
+
+# 93eb696e8c9a4372a49348a82bba481e
+#: ../../configuration.rst:1328
+msgid "100GB minimum capacity"
+msgstr "最少100GB容量"
+
+# 5d6728fa692e41a186cc029252118288
+#: ../../configuration.rst:1330
+msgid ""
+"A secondary storage device must be located in the same zone as the guest VMs"
+" it serves."
+msgstr "二级存储必须与他服务的客户虚拟机在同一个区域。"
+
+# 9e55bb037b5d4b35b720ef57d16556a8
+#: ../../configuration.rst:1333
+msgid ""
+"Each Secondary Storage server must be available to all hosts in the zone."
+msgstr "每一个二级存储服务器必须对区域的所有主机可用。"
+
+# e0c736eae790448ba73388e3c5b2d47f
+#: ../../configuration.rst:1338
+msgid "Adding Secondary Storage"
+msgstr "添加二级存储"
+
+# 6791f9d69f3f4cee83ddb30891d2e653
+#: ../../configuration.rst:1340
+msgid ""
+"When you create a new zone, the first secondary storage is added as part of "
+"that procedure. You can add secondary storage servers at any time to add "
+"more servers to an existing zone."
+msgstr "当你创建一个新的区域时，第一个二级存储作为创建的一部分 。为了添加更多的服务器，你可以随时添加二级存储服务器到已创建的区域中。"
+
+# 4de26231899b4a91a5b618eaf80f76ba
+#: ../../configuration.rst:1345
+msgid ""
+"Ensure that nothing is stored on the server. Adding the server to CloudStack"
+" will destroy any existing data."
+msgstr "确保二级存储服务器上没有存储任何数据。添加服务器到CloudStack时，会损坏服务器上原有已存的数据"
+
+# 0f96c75bcfaa4992b32facf1bf9c77ed
+#: ../../configuration.rst:1348
+msgid ""
+"To prepare for the zone-based Secondary Staging Store, you should have "
+"created and mounted an NFS share during Management Server installation. See "
+"`“Prepare NFS Shares” <installation.html#prepare-nfs-shares>`_."
+msgstr "为了准备区域的二级存储，你应当在管理节点安装时创建并挂载了NFS共享目录。参见 `“准备NFS共享目录” <installation.html#prepare-nfs-shares>`_."
+
+# 8b7e2a3c48fc4c57a7d8c5571f9338a3
+#: ../../configuration.rst:1353
+msgid ""
+"If you are using an Hyper-V host, ensure that you have created a SMB share."
+msgstr "如果你正在使用Hyper-V主机，确保你已经创建了一个SMB共享目录。"
+
+# 48e97ef4b1a54f518c793652ddec6ef8
+#: ../../configuration.rst:1356
+msgid ""
+"Make sure you prepared the system VM template during Management Server "
+"installation. See `“Prepare the System VM Template” <installation.html"
+"#prepare-the-system-vm-template>`_."
+msgstr "确保你在安装管理节点时，准备了系统虚拟机模板，参见 `“准备系统虚拟机模板” <installation.html#prepare-the-system-vm-template>`_."
+
+# fb775865c0094c848195fc8e5e81dfe0
+# e77ca2fba1984e23a35ca22a521e66f7
+#: ../../configuration.rst:1360 ../../configuration.rst:1418
+msgid "Log in to the CloudStack UI as root administrator."
+msgstr "以根管理员身份登录CloudStack界面。"
+
+# bf288714744446b487c5d03e8d5c284f
+# 54721a0f604d4c89b7b287778eac8b4a
+#: ../../configuration.rst:1362 ../../configuration.rst:1420
+msgid "In the left navigation bar, click Infrastructure."
+msgstr "在左侧导航栏中，点击基础架构"
+
+# 802486b1694646e592a9dc6a6e069a21
+# dd93f372389045b9ade68ce6bf035f54
+#: ../../configuration.rst:1364 ../../configuration.rst:1422
+msgid "In Secondary Storage, click View All."
+msgstr "在二级存储中，点击 查看全部。"
+
+# 5e56801815014372ae7b840a6124f920
+#: ../../configuration.rst:1366
+msgid "Click Add Secondary Storage."
+msgstr "点击添加二级存储。"
+
+# 5b0960edebc74650950d33271c9f6db6
+#: ../../configuration.rst:1368
+msgid "Fill in the following fields:"
+msgstr "填写以下内容："
+
+# 8bb375e8f43347d8844effcc6cf2a994
+#: ../../configuration.rst:1370
+msgid "Name. Give the storage a descriptive name."
+msgstr "名称--需要给二级存储一个描述性名称。"
+
+# d672a62914804d9e85d1c3055b9bcddf
+#: ../../configuration.rst:1372
+msgid ""
+"Provider. Choose S3, Swift, NFS, or CIFS then fill in the related fields "
+"which appear. The fields will vary depending on the storage provider; for "
+"more information, consult the provider's documentation (such as the S3 or "
+"Swift website). NFS can be used for zone-based storage, and the others for "
+"region-wide storage. For Hyper-V, select SMB/CIFS."
+msgstr "提供者。选择S3，Swift，NFS或者CIFS。此时会出现需要填写的相关内容。根据提供者的不同，需要的内容会有所不同。要了解更多，可参考提供者文档（如S3或Swift网站）。NFS可用于区域存储，其他的可用于地域存储。对 Hyper-V，选择 SMB/CIFS。"
+
+# 085cebda2756421d88eabe0fd1ed189e
+#: ../../configuration.rst:1380
+msgid ""
+"Heterogeneous Secondary Storage is not supported in Regions. You can use "
+"only a single NFS, S3, or Swift account per region."
+msgstr "地域中不支持多类二级存储共存。每一个地域只能使用NFS，S3或Swift其中的一种。"
+
+# 4c63cfbb89234aa9994880b6d7035475
+#: ../../configuration.rst:1383
+msgid "Create NFS Secondary Staging Store. This box must always be checked."
+msgstr "创建NFS二级暂存区，必须要勾选此项。"
+
+# 82935d6da92341a5bc95411b32007c5c
+#: ../../configuration.rst:1387
+msgid ""
+"Even if the UI allows you to uncheck this box, do not do so. This checkbox "
+"and the three fields below it must be filled in. Even when Swift or S3 is "
+"used as the secondary storage provider, an NFS staging storage in each zone "
+"is still required."
+msgstr "即使UI允许你不勾选此项，也不要这样做。此项以及下面的三项内容是必须要填写的。即使二级存储提供商使用了Swift或S3，在每个区域中NFS暂存区仍是需要的。"
+
+# 5c87b1fdcb6c46648fb4bfad3fc595e6
+# 96945a3298924faea7c59f3ddc805b91
+#: ../../configuration.rst:1392 ../../configuration.rst:1430
+msgid "Zone. The zone where the NFS Secondary Staging Store is to be located."
+msgstr "区域，即二级暂存区所在的区域。"
+
+# 3d532bad74854b83840c13235fc5eaf3
+#: ../../configuration.rst:1395
+msgid ""
+"**SMB Username**: Applicable only if you select SMB/CIFS provider. The "
+"username of the account which has the necessary permissions to the SMB "
+"shares. The user must be part of the Hyper-V administrator group."
+msgstr "**SMB Username**:仅当选择了SMB/CIFS时可用。此账户针对SMB拥有必要的权限。用户必须是Hyper-V管理组的成员。"
+
+# d11b35aafdad49d09e6595709ab4a869
+#: ../../configuration.rst:1400
+msgid ""
+"**SMB Password**: Applicable only if you select SMB/CIFS provider. The "
+"password associated with the account."
+msgstr "**SMB Password**:仅当选择了SMB/CIFS时可用。此密码与账户关联。"
+
+# 0cc268fbd62a46339fc88eceb8dadb38
+#: ../../configuration.rst:1403
+msgid ""
+"**SMB Domain**: Applicable only if you select SMB/CIFS provider. The Active "
+"Directory domain that the SMB share is a part of."
+msgstr "**SMB Domain**:仅当选择了SMB/CIFS时可用。是SMB共享目录活动哉的一部分。"
+
+# b3462457dd174443aa00bc93eaebe853
+# 470e248f89d14eeb8eb098c79f29f52c
+#: ../../configuration.rst:1406 ../../configuration.rst:1433
+msgid "NFS server. The name of the zone's Secondary Staging Store."
+msgstr "NFS服务器。二级暂存区的区域名称。"
+
+# adf27bcea0504f11988812eb85a20283
+# 29251115675e4ebd9e95bb8e2be474ec
+#: ../../configuration.rst:1408 ../../configuration.rst:1435
+msgid "Path. The path to the zone's Secondary Staging Store."
+msgstr "路径。二级暂存区所在区域的路径"
+
+# f1a67ebb7bfc4b9bba233d814a3633e7
+#: ../../configuration.rst:1412
+msgid "Adding an NFS Secondary Staging Store for Each Zone"
+msgstr "为每一个区域添加二级暂存区"
+
+# 592852d3ff9741b592dfb8c0155bea22
+#: ../../configuration.rst:1414
+msgid ""
+"Every zone must have at least one NFS store provisioned; multiple NFS "
+"servers are allowed per zone. To provision an NFS Staging Store for a zone:"
+msgstr "每一个区域至少有一个NFS存储区。每个区域允许存在多个NFS服务器。按以下步骤为区域添加一个二级暂存区"
+
+# 78eec05d08f24414bcb7cd50390349f9
+#: ../../configuration.rst:1424
+msgid "In Select View, choose Secondary Staging Store."
+msgstr "在选择视图中，选择二级暂存区"
+
+# 58099b56975e4d6595fd3021bdba2d25
+#: ../../configuration.rst:1426
+msgid "Click the Add NFS Secondary Staging Store button."
+msgstr "点击添加二级暂存区按钮"
+
+# 8d5db72403274211adc4e4ca5885cd63
+#: ../../configuration.rst:1428
+msgid "Fill out the dialog box fields, then click OK:"
+msgstr "填写对话框中的内容，然后点击确定"
+
+# b36dbe0441734c5d88e226b8cb6d73ca
+#: ../../configuration.rst:1441
+msgid "Initialize and Test"
+msgstr "初始化及测试"
+
+# f68866b9b3734b33aff7025c4fc36a2b
+#: ../../configuration.rst:1443
+msgid ""
+"After everything is configured, CloudStack will perform its initialization. "
+"This can take 30 minutes or more, depending on the speed of your network. "
+"When the initialization has completed successfully, the administrator's "
+"Dashboard should be displayed in the CloudStack UI."
+msgstr "在所有配置完成后，CloudStack会执行初始化。根据网络速度的不同，可能会需要30分钟或更多的时间。当初始化完成后，管理员控制面板会出现在CloudStack的界面中。"
+
+# e9f3a393a1774f74b5055f413c96a747
+#: ../../configuration.rst:1448
+msgid ""
+"Verify that the system is ready. In the left navigation bar, select "
+"Templates. Click on the CentOS 5.5 (64bit) no Gui (KVM) template. Check to "
+"be sure that the status is \"Download Complete.\" Do not proceed to the next"
+" step until this status is displayed."
+msgstr "确保系统已经准备完成。在左侧导航栏中，选择 模板 ，点击CentOS 5.5 (64bit) no Gui (KVM) template，查看其状态是否为 下载完成。在状态没有变成下载完成前，不要继续操作。"
+
+# 9765684b94244895a421d49deaf567ba
+#: ../../configuration.rst:1453
+msgid "Go to the Instances tab, and filter by My Instances."
+msgstr "点击实例标签，筛选我的实例。"
+
+# 2880f3b150d14b459c557af5ec08546d
+#: ../../configuration.rst:1455
+msgid "Click Add Instance and follow the steps in the wizard."
+msgstr "点击添加实例，并完成向导指示的步骤。"
+
+# 2afad971b41d4de4a246ba67d4ae812b
+#: ../../configuration.rst:1457
+msgid "Choose the zone you just added."
+msgstr "选择你刚才添加的区域。"
+
+# 0fc7a9665e7e4723a768ff8dc31cced5
+#: ../../configuration.rst:1459
+msgid ""
+"In the template selection, choose the template to use in the VM. If this is "
+"a fresh installation, likely only the provided CentOS template is available."
+msgstr "在模板选择中，选择在虚拟机中使用的模板。如果是初次安装，可能仅提供了CentOS的模板。"
+
+# 888d93deca4d435aa3abbc602cd21a5f
+#: ../../configuration.rst:1463
+msgid ""
+"Select a service offering. Be sure that the hardware you have allows "
+"starting the selected service offering."
+msgstr "选择服务方案。确保已有的硬件允许你开始选择服务方案。"
+
+# c9f44c62d2c042eabda1609a020f52c0
+#: ../../configuration.rst:1466
+msgid ""
+"In data disk offering, if desired, add another data disk. This is a second "
+"volume that will be available to but not mounted in the guest. For example, "
+"in Linux on XenServer you will see /dev/xvdb in the guest after rebooting "
+"the VM. A reboot is not required if you have a PV-enabled OS kernel in use."
+msgstr "在数据盘方案中，如果可以，添加另一块数据盘。此盘可用，但并未在客户机中挂。例如，基于XenServer的Linux，重启虚拟机后会在/dev/xvdb中看见客户机。如果操作系统内核中使能了PV，重启并不是必要的一步。"
+
+# 1d8ed73580834715bab5475f01fde220
+#: ../../configuration.rst:1472
+msgid ""
+"In default network, choose the primary network for the guest. In a trial "
+"installation, you would have only one option here."
+msgstr "在默认网络中，为客户机选择主网络。在试用安装中，这里可能只有一个选项。"
+
+# 7381b9b824f64589ac04f8704896713f
+#: ../../configuration.rst:1475
+msgid ""
+"Optionally give your VM a name and a group. Use any descriptive text you "
+"would like."
+msgstr "可以给你的虚拟机一个名字或组名，允许使用你喜欢的描述性文字。"
+
+# 25155fbd928c415db082ad68cac73582
+#: ../../configuration.rst:1478
+msgid ""
+"Click Launch VM. Your VM will be created and started. It might take some "
+"time to download the template and complete the VM startup. You can watch the"
+" VM’s progress in the Instances screen."
+msgstr "点击启动虚拟机，你的虚拟机将会被创建并被启动。可能会需要一点时间来下载模板并完成启动。你可以在实例页观察虚拟的过程。"
+
+# 33d66d1adbea4bb7a5979aac637d27bc
+#: ../../configuration.rst:1483
+msgid ""
+"To use the VM, click the View Console button. |ConsoleButton.png: button to "
+"launch a console|"
+msgstr "为了使用虚拟机，点击通讯视图按钮以启动一个通讯窗口. |ConsoleButton.png: button to launch a console|"
+
+# 6b8361d98cfe4efba50da0878b03cbbc
+#: ../../configuration.rst:1486
+msgid ""
+"For more information about using VMs, including instructions for how to "
+"allow incoming network traffic to the VM, start, stop, and delete VMs, and "
+"move a VM from one host to another, see Working With Virtual Machines in the"
+" Administrator’s Guide."
+msgstr "关于使用虚拟机的更多信息，包括如何允许进入虚拟机的网络流量，开始，停止，删除虚拟机以及从一个主机上迁移虚拟，参看管理员手册中的使用虚拟部分。"
+
+# 4bbb4febddf9404f9f1bb947098bd130
+#: ../../configuration.rst:1491
+msgid ""
+"Congratulations! You have successfully completed a CloudStack Installation."
+msgstr "恭喜！你已经完了CloudStack的安装。"
+
+# f80667053e0249a3abd24b4f2b6db3ed
+#: ../../configuration.rst:1494
+msgid ""
+"If you decide to grow your deployment, you can add more hosts, primary "
+"storage, zones, pods, and clusters."
+msgstr "如果决定扩展你的部署，可以增加更多的主机，主存储，区域，资源池以及集群。"
+
+# c560c1abbc0943729e4be7ed366f3f45
+#: ../../configuration.rst:1499
+msgid "Configuration Parameters"
+msgstr "配置参数"
+
+# 2a5e0238a6744532890adbf1f51cbfc2
+#: ../../configuration.rst:1502
+msgid "About Configuration Parameters"
+msgstr "关于配置参数"
+
+# 003cadc1a22543e181b420d3216ee3ca
+#: ../../configuration.rst:1504
+msgid ""
+"CloudStack provides a variety of settings you can use to set limits, "
+"configure features, and enable or disable features in the cloud. Once your "
+"Management Server is running, you might need to set some of these "
+"configuration parameters, depending on what optional features you are "
+"setting up. You can set default values at the global level, which will be in"
+" effect throughout the cloud unless you override them at a lower level. You "
+"can make local settings, which will override the global configuration "
+"parameter values, at the level of an account, zone, cluster, or primary "
+"storage."
+msgstr "CloudStack提供了各类设置，可以用来限制某性配置功能，打开或关闭云中的某些功能。一旦你的管理服务器运行后，你可能需要设置一些参数，依赖于你打开了哪些参数。也可以在全局设置中使用默认值，他们都会在云中全部起作用，除非在低级别配置时配置有错误。你也可以设置局部参数，在账户，区域，集群，主存储级别时，允许覆盖全局配置参数"
+
+# e6d2272ffdc04a15b3b2e5a0b39a5a6e
+#: ../../configuration.rst:1514
+msgid ""
+"The documentation for each CloudStack feature should direct you to the names"
+" of the applicable parameters. The following table shows a few of the more "
+"useful parameters."
+msgstr "每一个CloudStack的功能文档，都会引导你到应用参数名，下表给出了一些更有用的参数。"
+
+# 48a9586522fe49a684a986663433d564
+# 92079ae000394a18a79504e41961233c
+# 43f27ae0b01e46e98172965dd387907d
+#: ../../configuration.rst:1519 ../../configuration.rst:1593
+#: ../../configuration.rst:1593
+msgid "Field"
+msgstr "值域"
+
+# 2a703e9880154ddf91d1a384bfe8d684
+# 4dd2b3b2879b471388bcb2004313500a
+#: ../../configuration.rst:1519 ../../configuration.rst:1593
+msgid "Value"
+msgstr "值"
+
+# a510f43a421343dea533527f4084051d
+#: ../../configuration.rst:1521
+msgid "management.network.cidr"
+msgstr "management.network.cidr"
+
+# dccbf6a2a6274bd1befec5e03859ae5d
+#: ../../configuration.rst:1521
+msgid ""
+"A CIDR that describes the network that the management CIDRs reside on. This"
+" variable must be set for deployments"
+" that use vSphere. It is recommended to be"
+" set for other deployments as well. "
+"Example: 192.168.3.0/24."
+msgstr "CIDR描述了管理存在的CIDR。在使用vSphere部署时，此项必须设置。推荐其他部署时也同样设置。例如：192.168.3.0/24"
+
+# b5e4676da208492e872933356f38f626
+#: ../../configuration.rst:1522
+msgid "xen.setup.multipath"
+msgstr "xen.setup.multipath"
+
+# cb8c5e8921894a34868af73e9e9b8a6f
+#: ../../configuration.rst:1522
+msgid ""
+"For XenServer nodes, this is a true/false variable that instructs CloudStack"
+" to enable iSCSI multipath on the "
+"XenServer Hosts when they are added. This"
+" defaults to false. Set it to "
+"true if you would like CloudStack to enable"
+" multipath.If this is true for a "
+"NFS-based deployment multipath will still be"
+" enabled on the XenServer host. "
+"However, this does not impact NFS operation and"
+" is harmless."
+msgstr "对于XenServer节点，此 是/否 变量指示CloudStack允许XenServer主机的iSCSI的多路径。默认值为否。如果希望CloudStack允许多路径，请置为是。如果值为是，基于NFS部署的XenServer主机允许多路径。当然这不会影响NFS的操作并且没有任何危害。"
+
+# df8f08a8bb804a5fb28c80c3fa316708
+#: ../../configuration.rst:1523
+msgid "secstorage.allowed.internal.sites"
+msgstr "secstorage.allowed.internal.sites"
+
+# b415c6a677b249d9ba32483249809b8a
+#: ../../configuration.rst:1523
+msgid ""
+"This is used to protect your internal network from rogue attempts to "
+"download arbitrary files using the "
+"template download feature. This is a comma-separated"
+" list of CIDRs. If a requested URL "
+"matches any of these CIDRs the Secondary"
+" Storage VM will use the private "
+"network interface to fetch the URL. Other URLs"
+" will go through the public interface. "
+"We suggest you set this to 1 or 2"
+" hardened internal machines where"
+" you keep your templates. For example, set it"
+" to 192.168.1.66/32."
+msgstr "这用来保护内部网络避免通过使用模板下载功能暴力尝试下载文件。可以用逗号分隔多个CIDR。如果需要网址来匹配CIDR，二级存储虚拟机会使用私有网络来获取网址。其他网址则会通过公共接口。建议将其设成1或2个内部用来保存模板的地址，如：192.168.1.66/32"
+
+# bca7b73b39f34d68bfc7b3a8b02028c9
+#: ../../configuration.rst:1524
+msgid "use.local.storage"
+msgstr "use.local.storage"
+
+# c403da3bca8c422cb0030472d7fdd0dd
+#: ../../configuration.rst:1524
+msgid ""
+"Determines whether CloudStack will use storage that is local to the Host for"
+" data disks, templates, and snapshots."
+" By default CloudStack will not use this"
+" storage. You should change this to "
+"true if you want to use local storage and"
+" you understand the reliability and "
+"feature drawbacks to choosing local storage."
+msgstr "用来决定CloudStack是否使用主机本地的存储存放数据盘，模板，快照。CloudStack默认不使用本地存储。如果你想使用本地存储时可设置为是，并且你也知道选择本地存储的可信赖以及随时读取的功能。"
+
+# 273f3dc9d0b24674a052d86df2f932f7
+#: ../../configuration.rst:1525
+msgid "host"
+msgstr "host"
+
+# 47bba12b42d54d46be9901d1f8cf8ca5
+#: ../../configuration.rst:1525
+msgid ""
+"This is the IP address of the Management Server. If you are using multiple"
+" Management Servers you should enter"
+" a load balanced IP address that is"
+" reachable via the private "
+"network."
+msgstr "这是管理服务器的IP地址。如果你部署了多台管理服务器，你应该在这里输入一个内网可以访问到的负载均衡IP地址。"
+
+# d310c3c87f234eceb4271591bd4d899f
+#: ../../configuration.rst:1526
+msgid "default.page.size"
+msgstr "default.page.size"
+
+# 3a7b21e756ed4f3284a2a188ca0a0ec1
+#: ../../configuration.rst:1526
+msgid ""
+"Maximum number of items per page that can be returned by a CloudStack API"
+" command. The limit applies at the "
+"cloud level and can vary from cloud to cloud."
+" You can override this with a lower value"
+" on a particular API call by using the "
+"page and pagesize API command parameters. For more information, see the"
+" Developer's Guide. Default: 500."
+msgstr "通过CloudStack API命令返回每页中显示条目的最大值。在云级别中适用此限制，不同的云之间会有所不同。通过使用page和pagesize参数调用特定的API，将其修改为较小的值。要了解更多，请参阅开发指南。默认值：500"
+
+# 8d6b4fb28115479a9cb70f843801f6aa
+#: ../../configuration.rst:1527
+msgid "ha.tag"
+msgstr "ha.tag"
+
+# cb3deb2df4004607a2e04b50afda2e63
+#: ../../configuration.rst:1527
+msgid ""
+"The label you want to use throughout the cloud to designate certain hosts as"
+" dedicated HA hosts. These hosts will "
+"be used only for HA-enabled VMs that are"
+" restarting due to the failure of "
+"another host. For example, you could set this"
+" to ha\\_host. Specify the ha.tag value "
+"asa host tag when you add a new host to"
+" the cloud."
+msgstr "这个标签标示一个在全云中使用的特定主机，作为专用高可用性主机。被标示的主机仅用作使能的高可用性虚拟机，他们在其他主机失败时启动。例如，在向云中添加一个新主机时可以标明主机的标签为ha.tag，将其设为高可用性主机。"
+
+# 556fde03303d42ffb220b102b2210dfc
+#: ../../configuration.rst:1528
+msgid "vmware.vcenter.session.timeout"
+msgstr "vmware.vcenter.session.timeout"
+
+# cf142a0831c24cd29e0879d24191c09a
+#: ../../configuration.rst:1528
+msgid ""
+"Determines the vCenter session timeout value by using this parameter. The"
+" default value is 20 minutes. "
+"Increase the timeout value to avoid timeout errors"
+" in VMware deployments because certain "
+"VMware operations take more than 20"
+" minutes."
+msgstr "通过使用这个参数来决定虚拟中心连接的失效时间。默认值是20分钟。增大此值，以避免在VMware部署中的错误，因为VMware的操作可能会需要超过20分钟的时间。"
+
+# 08eca151e89148068e96234ee8efccac
+#: ../../configuration.rst:1533
+msgid "Setting Global Configuration Parameters"
+msgstr "设定全局配置参数"
+
+# 2a6efc4eeb824e30b5d0a10540c63b55
+#: ../../configuration.rst:1535
+msgid ""
+"Use the following steps to set global configuration parameters. These values"
+" will be the defaults in effect throughout your CloudStack deployment."
+msgstr "通过以下几步来设定全局配置参数。在整个CloudStack的部署过程，默认值会起作用。"
+
+# ac0242e31c474dd29a9b24db5556bf48
+# e7461b5a426d4c808698cd33f7adfccd
+#: ../../configuration.rst:1539 ../../configuration.rst:1566
+msgid "Log in to the UI as administrator."
+msgstr "以管理员登录界面。"
+
+# 1b4a8289f9be4367b5464454566ebf4b
+#: ../../configuration.rst:1541
+msgid "In the left navigation bar, click Global Settings."
+msgstr "在左侧导航栏中，点击全局设置"
+
+# e82df7307c7f415ab94db7b575b470ce
+#: ../../configuration.rst:1543
+msgid "In Select View, choose one of the following:"
+msgstr "在选择视图中，选择以下一个："
+
+# a0142617fa364a99bda590a8e64a934b
+#: ../../configuration.rst:1545
+msgid ""
+"Global Settings. This displays a list of the parameters with brief "
+"descriptions and current values."
+msgstr "全局设置。这会显示参数值，并附有简单的说明。"
+
+# 6047b505f5ab4a81a7fc7b399792b08f
+#: ../../configuration.rst:1548
+msgid ""
+"Hypervisor Capabilities. This displays a list of hypervisor versions with "
+"the maximum number of guests supported for each."
+msgstr "虚拟化能力。这会显示虚拟化版本以及所支持的最大用户数。"
+
+# 47e638389ccc47d895ad51b8865b67ed
+# 6621f931d1314dcb991dbfed946145d4
+#: ../../configuration.rst:1551 ../../configuration.rst:1579
+msgid ""
+"Use the search box to narrow down the list to those you are interested in."
+msgstr "使用搜索框来缩小你所赶兴趣的内容。"
+
+# 274dfcd501c64b7db7ba5376b4dffe31
+#: ../../configuration.rst:1554
+msgid ""
+"In the Actions column, click the Edit icon to modify a value. If you are "
+"viewing Hypervisor Capabilities, you must click the name of the hypervisor "
+"first to display the editing screen."
+msgstr "在动作栏，点击编辑按钮可修改一个值。如果查看虚拟化能力，必须先点击虚拟化名称以显示编辑页。"
+
+# c211ee2e26b44d7ebd0c28660e867d35
+#: ../../configuration.rst:1560
+msgid "Setting Local Configuration Parameters"
+msgstr "设定全局参数"
+
+# fce0255430b2475aa263b8ca924cf857
+#: ../../configuration.rst:1562
+msgid ""
+"Use the following steps to set local configuration parameters for an "
+"account, zone, cluster, or primary storage. These values will override the "
+"global configuration settings."
+msgstr "使用以下几步来设置本地配置参数，包括账号，区域，集群或主存储。这些值会覆盖全局配置值。"
+
+# 4d858a0c5a24407ab000370a24eccf0e
+#: ../../configuration.rst:1568
+msgid ""
+"In the left navigation bar, click Infrastructure or Accounts, depending on "
+"where you want to set a value."
+msgstr "在左侧导航栏中，点击基础架构或账户，取决于你想设定的内容。"
+
+# d9cd0d62e3444c7c8fe947bfd1473243
+#: ../../configuration.rst:1571
+msgid ""
+"Find the name of the particular resource that you want to work with. For "
+"example, if you are in Infrastructure, click View All on the Zones, "
+"Clusters, or Primary Storage area."
+msgstr "找到你想使用的特定资源的名称。例如，如果你在基础架构中，在区域，集群，主存储上点击查看全部，"
+
+# f33422e144174bf49c2e2e93d9b70b2c
+#: ../../configuration.rst:1575
+msgid "Click the name of the resource where you want to set a limit."
+msgstr "点击你想限定的资源名称。"
+
+# 0c15b68fadd743d5938a20e850c355d7
+#: ../../configuration.rst:1577
+msgid "Click the Settings tab."
+msgstr "点击设定标签"
+
+# fb206dd4787047d6956ce47dace0fd46
+#: ../../configuration.rst:1582
+msgid "In the Actions column, click the Edit icon to modify a value."
+msgstr "在动作栏，点击编辑按钮可修改一个值。"
+
+# e52abd333a034d37b1bb7cba1e32a42b
+#: ../../configuration.rst:1586
+msgid "Granular Global Configuration Parameters"
+msgstr "全局配置参数的精细设置"
+
+# 20898527299948338ada5e13d94049bb
+#: ../../configuration.rst:1588
+msgid ""
+"The following global configuration parameters have been made more granular. "
+"The parameters are listed under three different scopes: account, cluster, "
+"and zone."
+msgstr "以下全局配置参数更加精细。以下列出的参数有三个不同的范围，账户，集群和区域。"
+
+# 8df2d6b3d1314a8aae8b1eb457648aff
+# a882525fba6542feb9112de1d3e305e8
+# 65d5144f4743413bb5a8c1757b6f3cef
+# 43b5bc4715d24f18b9bd42535f46cf70
+#: ../../configuration.rst:1595 ../../configuration.rst:1596
+#: ../../configuration.rst:1597 ../../configuration.rst:1598
+msgid "account"
+msgstr "账户"
+
+# a9df3278553c49a3849dc3e22fe08b2d
+#: ../../configuration.rst:1595
+msgid "remote.access.vpn.client.iprange"
+msgstr "remote.access.vpn.client.iprange"
+
+# 2c2997c2ad20401da80596c3cc6d70be
+#: ../../configuration.rst:1595
+msgid ""
+"The range of IPs to be allocated to remotely access the VPN clients. The "
+"first IP in the range is"
+" "
+"used by the VPN server."
+msgstr "应当给远程访问vpn的客户分配一个ip范围。范围中的第一个ip被vpn 服务器所使用。"
+
+# 46f406836e5f47789c7308cbc24461f1
+#: ../../configuration.rst:1596
+msgid "allow.public.user.templates"
+msgstr "allow.public.user.templates"
+
+# 231c392623f04972aab04a526f80765f
+#: ../../configuration.rst:1596
+msgid "If false, users will not be able to create public templates."
+msgstr "如果值为否，用户将不能创建公共模板。"
+
+# 56f5fe2656b14d2ba0b1ad180fd5d5bd
+#: ../../configuration.rst:1597
+msgid "use.system.public.ips"
+msgstr "use.system.public.ips"
+
+# fb9862501ef4410dae60a5aa8a2ffc1b
+#: ../../configuration.rst:1597
+msgid ""
+"If true and if an account has one or more dedicated public IP ranges, IPs "
+"are"
+" "
+"acquired from the system pool after all the IPs dedicated to the account "
+"have been consumed."
+msgstr "如果值为是，并且如果账户有一个或多个专用的公用ip范围，在账户专用的IP用完以后，可以从系统池中获取ip."
+
+# e7e69d39fefd4be28bfc71ef64d7d997
+#: ../../configuration.rst:1598
+msgid "use.system.guest.vlans"
+msgstr "use.system.guest.vlans"
+
+# c001c1a0314e49c2a7b1b3dcfd668036
+#: ../../configuration.rst:1598
+msgid ""
+"If true and if an account has one or more dedicated guest VLAN ranges, VLANs"
+" are allocated from the"
+" "
+"system pool after all the VLANs dedicated to the account have been consumed."
+msgstr "如果值为是，并且如果账户有一个或多个专用的客户VLAN范围，在账户专用的VLAN用完后，可从系统池中获取VLAN。"
+
+# 6c8238a6074241b7a25073b38624b975
+# 9647b4f636d242e6b7c8253a4c845cf4
+# db3bde4fcc0c4d8981cde4b9c39ecc90
+# bddc63e51e324877be7710d594e2d149
+# 266ad0b0880c46cbbeac7f7e4e84a5df
+# edfcec1ab75641a487fbfc282f0ad518
+# 054e4713ecb94c12b29863f7f33a85c3
+# 4d2c7029c357490dae1ee56ac89c4269
+# 0e147f13a16a46f7b47a443dd1cd52a9
+# 35235cd387734a709b01e8062eceab67
+#: ../../configuration.rst:1599 ../../configuration.rst:1600
+#: ../../configuration.rst:1601 ../../configuration.rst:1602
+#: ../../configuration.rst:1603 ../../configuration.rst:1604
+#: ../../configuration.rst:1605 ../../configuration.rst:1607
+#: ../../configuration.rst:1608 ../../configuration.rst:1609
+msgid "cluster"
+msgstr "集群"
+
+# 27e3e5dccb0b42eba3b866f31745c2c4
+#: ../../configuration.rst:1599
+msgid "cluster.storage.allocated.capacity.notificationthreshold"
+msgstr "cluster.storage.allocated.capacity.notificationthreshold"
+
+# bb2047027ddf4928a0585e4088ce1f29
+#: ../../configuration.rst:1599
+msgid ""
+"The percentage, as a value between 0 and 1, of allocated storage utilization"
+" "
+"above which alerts are sent that the storage is below the threshold."
+msgstr "百分比，其值从0到1，分配存储的利用率超过设定值，系统将会发送警告"
+
+# cf6962e471014b2e84dc9ff1fb372c82
+#: ../../configuration.rst:1600
+msgid "cluster.storage.capacity.notificationthreshold"
+msgstr "cluster.storage.capacity.notificationthreshold"
+
+# 217cf10ba30b47208d2ed0dab490eb7a
+#: ../../configuration.rst:1600
+msgid ""
+"The percentage, as a value between 0 and 1, of storage utilization above "
+"which alerts are sent that the available storage is below"
+" the"
+" threshold."
+msgstr "百分比，其值从0到1，可用存储的比率超过设定值，系统将会发送警告"
+
+# a802fd66c6ca40ea862ad41ad7784119
+#: ../../configuration.rst:1601
+msgid "cluster.cpu.allocated.capacity.notificationthreshold"
+msgstr "cluster.cpu.allocated.capacity.notificationthreshold"
+
+# 148d3709a3094f71b1c39d5cc62bdef7
+#: ../../configuration.rst:1601
+msgid ""
+"The percentage, as a value between 0 and 1, of cpu utilization above which "
+"alerts are sent that the available CPU is below the"
+" "
+"threshold."
+msgstr "百分比，其值从0到1，cpu的使用率超过设定值，系统将会发送警告"
+
+# 64f69d16efcb436da37e48eb1da8f50b
+#: ../../configuration.rst:1602
+msgid "cluster.memory.allocated.capacity.notificationthreshold"
+msgstr "cluster.memory.allocated.capacity.notificationthreshold"
+
+# 1f20a8d48c184fde84620cea1abfd5df
+#: ../../configuration.rst:1602
+msgid ""
+"The percentage, as a value between 0 and 1, of memory utilization above "
+"which alerts are sent that the available memory is below the"
+" "
+"threshold."
+msgstr "百分比，其值从0到1，内存的使用率超过设定值，系统将会发送警告"
+
+# d428c8f86cbe464587f88a9ebdbdcff0
+#: ../../configuration.rst:1603
+msgid "cluster.cpu.allocated.capacity.disablethreshold"
+msgstr "cluster.cpu.allocated.capacity.disablethreshold"
+
+# 8b66e72376894917b7cdfc704e5be44e
+#: ../../configuration.rst:1603
+msgid ""
+"The percentage, as a value between 0 and 1, of CPU utilization above which "
+"allocators will disable that cluster from further usage."
+" Keep"
+" the corresponding notification threshold lower than this value to be "
+"notified beforehand."
+msgstr "百分比，其值从0到1，cpu的使用率超过设定值后，分配器将关闭进一步的使用。设定相应通知限值要低于此值，以便能够被提前通知到。"
+
+# 4b250edddaca4cb683468f061af9d819
+#: ../../configuration.rst:1604
+msgid "cluster.memory.allocated.capacity.disablethreshold"
+msgstr "cluster.memory.allocated.capacity.disablethreshold"
+
+# f3b5f79db1cf46e0abbdd19505b30618
+#: ../../configuration.rst:1604
+msgid ""
+"The percentage, as a value between 0 and 1, of memory utilization above "
+"which allocators will disable that cluster from further"
+" "
+"usage. Keep the corresponding notification threshold lower than this value "
+"to be notified beforehand."
+msgstr "百分比，其值从0到1，内存的使用率超过设定值后，分配器将关闭进一步的使用。设定相应通知限值要低于此值，以便能够被提前通知到。"
+
+# e3d747cbc77546ad928288bc0678580f
+#: ../../configuration.rst:1605
+msgid "cpu.overprovisioning.factor"
+msgstr "cpu.overprovisioning.factor"
+
+# cb9a9903057f4089a0f74e7d00af0b09
+#: ../../configuration.rst:1605
+msgid ""
+"Used for CPU over-provisioning calculation; the available CPU will be the "
+"mathematical product of actualCpuCapacity and cpu.overprovisioning.factor."
+msgstr "用来进行cpu过度提供计算。可利用的cpu是实际cpu容量与cpu过度提供因子的乘积。"
+
+# 6529835959d14a30a5a02c1dab090203
+#: ../../configuration.rst:1607
+msgid "mem.overprovisioning.factor"
+msgstr "mem.overprovisioning.factor"
+
+# fae6e1ba37794435b586197424421ea0
+#: ../../configuration.rst:1607
+msgid "Used for memory over-provisioning calculation."
+msgstr "用来进行内存过度提供计算。"
+
+# fe09a1bfd6994765a0a0686ad370ac69
+#: ../../configuration.rst:1608
+msgid "vmware.reserve.cpu"
+msgstr "vmware.reserve.cpu"
+
+# 8e7c7caa5bec451783153beae186b804
+#: ../../configuration.rst:1608
+msgid ""
+"Specify whether or not to reserve CPU when not over-provisioning; In case of"
+" CPU over-provisioning, CPU is always reserved."
+msgstr "当未过载使用时说明是否预留cpu。防止cpu过载，cpu总是有预留的。"
+
+# d26aa6adac65454ba1ec4fb45c0b5e98
+#: ../../configuration.rst:1609
+msgid "vmware.reserve.mem"
+msgstr "vmware.reserve.mem"
+
+# 7fabfb4457fc4f0abf33ffdb09d96f51
+#: ../../configuration.rst:1609
+msgid ""
+"Specify whether or not to reserve memory when not over-provisioning; In case"
+" of memory over-provisioning memory is always reserved."
+msgstr "当未过载使用时说明是否预留内存。防止内存过载，内存总是有预留的。"
+
+# a21b783631704c9b81e3d29fabd9eaff
+# 0806344139bf4b4991de4bd62a3d5ff7
+# e97c440818654e929cb9accc4b0771ee
+# 9d135e71fe5d4eb58e98e8e80401579a
+# 46ed061677414c09b777017b1c2abfc2
+# a0ab2163da2946d686483044d5ca46cd
+# 4647de7d27814699b224fba9a40e5ad2
+# 3ba7ea4a85234737a51cef71da7e07b9
+# 166d0813c0f148288a2803b974241529
+# 95b6358dfd9d45b2a8dbbd2c42531a01
+# 585a49ffc9ad4fbea5f6701f266ee9ec
+#: ../../configuration.rst:1610 ../../configuration.rst:1612
+#: ../../configuration.rst:1613 ../../configuration.rst:1614
+#: ../../configuration.rst:1615 ../../configuration.rst:1616
+#: ../../configuration.rst:1617 ../../configuration.rst:1618
+#: ../../configuration.rst:1619 ../../configuration.rst:1620
+#: ../../configuration.rst:1621
+msgid "zone"
+msgstr "区域"
+
+# 196f60d63c6d46808c9d6bcc2f4c3885
+#: ../../configuration.rst:1610
+msgid "pool.storage.allocated.capacity.disablethreshold"
+msgstr "pool.storage.allocated.capacity.disablethreshold"
+
+# c04d61f4e28a4f789c84cb900c6cf0a9
+#: ../../configuration.rst:1610
+msgid ""
+"The percentage, as a value between 0 and 1, of allocated storage utilization"
+" above which allocators will disable that pool because the available "
+"allocated storage is below the threshold."
+msgstr "百分比，其值从0到1，已分配存储的使用率超过设定值后，分配器将关闭存储池，因为可用于分配的存储要小于限值。"
+
+# c738bf8adc7443b4ba523dea06552c19
+#: ../../configuration.rst:1612
+msgid "pool.storage.capacity.disablethreshold"
+msgstr "pool.storage.capacity.disablethreshold"
+
+# dac4310f42c2420ab725e8ca920ccfa0
+#: ../../configuration.rst:1612
+msgid ""
+"The percentage, as a value between 0 and 1, of storage utilization above "
+"which allocators will disable the pool because the available"
+" "
+"storage capacity is below the threshold."
+msgstr "百分比，其值从0到1，已分配存储的使用率超过设定值后，分配器将关闭存储池，因为可用于分配的存储要小于限值。"
+
+# 6edca2b7fcf44a3595a76537c70880f9
+#: ../../configuration.rst:1613
+msgid "storage.overprovisioning.factor"
+msgstr "storage.overprovisioning.factor"
+
+# 8eba02c107c9484093dd79cf0ee65f89
+#: ../../configuration.rst:1613
+msgid ""
+"Used for storage over-provisioning calculation; available storage will be "
+"the mathematical product of actualStorageSize and"
+" "
+"storage.overprovisioning.factor."
+msgstr "用来进行存储过载计算，可利用的存储是实际存储容量与存储过载因子的乘积。"
+
+# 9169218f4a2e46e5a8c1c1815238ed9f
+#: ../../configuration.rst:1614
+msgid "network.throttling.rate"
+msgstr "network.throttling.rate"
+
+# f2cbdfbd49734ffeb7941d05ea8b652b
+#: ../../configuration.rst:1614
+msgid ""
+"Default data transfer rate in megabits per second allowed in a network."
+msgstr "在网络中允许的默认每秒传输数据容量，单位MB"
+
+# ef89e33bf0fd437ea3415cd3d61baba3
+#: ../../configuration.rst:1615
+msgid "guest.domain.suffix"
+msgstr "guest.domain.suffix"
+
+# 30e0fdc26dd1489f86f794370cb4a3ba
+#: ../../configuration.rst:1615
+msgid "Default domain name for VMs inside a virtual networks with a router."
+msgstr "在具有路由的虚拟网络中的虚拟机的默认域名"
+
+# ef39613bc0cf446a9fff88679ae47b0a
+#: ../../configuration.rst:1616
+msgid "router.template.xen"
+msgstr "router.template.xen"
+
+# c419c741cae548769dd227875d563022
+#: ../../configuration.rst:1616
+msgid "Name of the default router template on Xenserver."
+msgstr "XenServer的默认路由模板名称"
+
+# 0d23eeec7546470da479531c87189b4d
+#: ../../configuration.rst:1617
+msgid "router.template.kvm"
+msgstr "router.template.kvm"
+
+# baf932ce269f42588943f7fdb4ec5234
+#: ../../configuration.rst:1617
+msgid "Name of the default router template on KVM."
+msgstr "kvm的默认路由模板名称"
+
+# 2bc3e93d62f2457c8cbb8bbdcf4cf5ac
+#: ../../configuration.rst:1618
+msgid "router.template.vmware"
+msgstr "router.template.vmware"
+
+# 9e6fcedba1f04fdab8a8542ea32d036f
+#: ../../configuration.rst:1618
+msgid "Name of the default router template on VMware."
+msgstr "VMware的默认路由模板名称"
+
+# 82a78e88325744e592b8bee2fce00ea7
+#: ../../configuration.rst:1619
+msgid "enable.dynamic.scale.vm"
+msgstr "enable.dynamic.scale.vm"
+
+# 58f5d9335ab549a79f28e17a2c562056
+#: ../../configuration.rst:1619
+msgid "Enable or diable dynamically scaling of a VM."
+msgstr "打开或关闭动态规模虚拟机"
+
+# 0ac19d4f17914e60ab366c0b230b7076
+#: ../../configuration.rst:1620
+msgid "use.external.dns"
+msgstr "use.external.dns"
+
+# 82b4dbaa5fec492986ebfd7d4bf76954
+#: ../../configuration.rst:1620
+msgid "Bypass internal DNS, and use the external DNS1 and DNS2"
+msgstr "忽略内部DNS，使用外部DNS1和DNS2"
+
+# c8177a7ac4ea4c07bf0c16f2833e48bf
+#: ../../configuration.rst:1621
+msgid "blacklisted.routes"
+msgstr "blacklisted.routes"
+
+# d9441a44a1824e80804bbbe62fd7f531
+#: ../../configuration.rst:1621
+msgid ""
+"Routes that are blacklisted cannot be used for creating static routes for a "
+"VPC Private Gateway."
+msgstr "黑名单中的路由不能用于虚拟机的私有网关来创建静态路由"
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/hyperv.mo b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/hyperv.mo
new file mode 100644
index 0000000..3b07133
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/hyperv.mo
Binary files differ
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/hyperv.po b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/hyperv.po
new file mode 100644
index 0000000..58627d2
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/hyperv.po
@@ -0,0 +1,538 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: 2014-06-30 10:26+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# a5185d38ad2e4f6cbc35116341dccf23
+#: ../../hypervisor/hyperv.rst:18
+msgid "Hyper-V Installation and Configuration"
+msgstr ""
+
+# d110647269414479b7fb035bfdcdd6f6
+#: ../../hypervisor/hyperv.rst:20
+msgid ""
+"If you want to use Hyper-V hypervisor to run guest virtual machines, install"
+" Hyper-V on the hosts in your cloud. The instructions in this section "
+"doesn't duplicate Hyper-V Installation documentation. It provides the "
+"CloudStack-specific steps that are needed to prepare a Hyper-V host to work "
+"with CloudStack."
+msgstr "如果你想使用 Hyper-V hypervisor来运行虚拟机，请在你的云环境中安装Hyper-V。本章节指导不会复制Hyper-V安装文档中的内容。它提供了让Hyper-V与CloudStack协同工作的一些特有的步骤。"
+
+# f65dfc47347b4c348baf2a6336cacf5b
+#: ../../hypervisor/hyperv.rst:28
+msgid "System Requirements for Hyper-V Hypervisor Hosts"
+msgstr "Hyper-V主机的系统要求"
+
+# 7a236efba2054d4ba58d9ecdaaf20a09
+#: ../../hypervisor/hyperv.rst:32
+msgid "Supported Operating Systems for Hyper-V Hosts"
+msgstr "Hyper-V主机所支持的操作系统"
+
+# bcd4ae34d08a497bad4e1b389059ec7d
+#: ../../hypervisor/hyperv.rst:34
+msgid "Windows Server 2012 R2 Standard"
+msgstr "Windows Server 2012 R2 Standard"
+
+# 680742a637b2491cbe7f3677dca729ba
+#: ../../hypervisor/hyperv.rst:36
+msgid "Windows Server 2012 R2 Datacenter"
+msgstr "Windows Server 2012 R2 Datacenter"
+
+# ccbfedc695de4f1fa589f6b2274d49a1
+#: ../../hypervisor/hyperv.rst:38
+msgid "Hyper-V 2012 R2"
+msgstr "Hyper-V 2012 R2"
+
+# f9d4e4e9531e4e13910e7f9bcf4f6231
+#: ../../hypervisor/hyperv.rst:42
+msgid "Minimum System Requirements for Hyper-V Hosts"
+msgstr "Hyper-V主机的最低要求"
+
+# cd76d4e704da43a2bf46b4a1ca1206a9
+#: ../../hypervisor/hyperv.rst:44
+msgid "1.4 GHz 64-bit processor with hardware-assisted virtualization."
+msgstr "支持硬件辅助虚拟化的1.4 GHz 64-bit CPU"
+
+# d66329292d3e4d679ddd534dcb5b56b1
+#: ../../hypervisor/hyperv.rst:46
+msgid "800 MB of RAM"
+msgstr "800MB内存"
+
+# c68a1b515138408e8b48078375c35450
+#: ../../hypervisor/hyperv.rst:48
+msgid "32 GB of disk space"
+msgstr "32GB本地磁盘空间"
+
+# 1924b40a1ea34af985c514e7e00fcf07
+#: ../../hypervisor/hyperv.rst:50
+msgid "Gigabit (10/100/1000baseT) Ethernet adapter"
+msgstr "Gigabit (10/100/1000baseT)网卡"
+
+# 5b9c638983de4946816feb1dfe06f7a3
+#: ../../hypervisor/hyperv.rst:54
+msgid "Supported Storage"
+msgstr "支持的存储"
+
+# 5501dc718ec148a1b106d7eac8e01f89
+#: ../../hypervisor/hyperv.rst:56
+msgid "Primary Storage: Server Message Block (SMB) Version 3, Local"
+msgstr "主存储：SMB v3，本地存储"
+
+# d98826167d964496b31bc798ae8ad5a8
+#: ../../hypervisor/hyperv.rst:58
+msgid "Secondary Storage: SMB"
+msgstr "辅助存储：SMB"
+
+# 51e903e68fa44cc987b6c2ad08dbeb36
+#: ../../hypervisor/hyperv.rst:62
+msgid "Preparation Checklist for Hyper-V"
+msgstr "Hyper-V的准备工作清单"
+
+# 556e9ae21bb747fe83f5e90bf14d165b
+#: ../../hypervisor/hyperv.rst:64
+msgid ""
+"For a smoother installation, gather the following information before you "
+"start:"
+msgstr "为了能顺利地安装，在安装之前请收集以下信息："
+
+# 5e62ce48e3304d90a1e5f41a3c4bd74c
+#: ../../hypervisor/hyperv.rst:68
+msgid "Hyper-V Requiremen ts"
+msgstr ""
+
+# d69ee48d947543d6a0b0d9b680e79b99
+#: ../../hypervisor/hyperv.rst:68
+msgid "Value"
+msgstr "值"
+
+# 020b9f3298894f29adbb932ddaefd9e4
+#: ../../hypervisor/hyperv.rst:68
+msgid "Description"
+msgstr "描述"
+
+# a4ae60478f084501bf98804259ca31c7
+#: ../../hypervisor/hyperv.rst:72
+msgid "Server Roles"
+msgstr "服务器角色"
+
+# 92022baf55eb439499536554f1c93bc6
+#: ../../hypervisor/hyperv.rst:72
+msgid "Hyper-V"
+msgstr "Hyper-V"
+
+# 85cc74d52bf447b59ad5a8fb8f528075
+#: ../../hypervisor/hyperv.rst:72
+msgid ""
+"After the Windows Server 2012 R2 installation, ensure that Hyper-V is "
+"selected from Server Roles. For more information, see `Installing Hyper-V "
+"<http://technet.microsoft.com/en-us/library/ jj134187.aspx#BKMK_Step2>`__."
+msgstr ""
+
+# 19d59b3dace14c519959ecfa3f73fbca
+#: ../../hypervisor/hyperv.rst:78
+msgid "Share Location"
+msgstr "共享位置"
+
+# 6de5f24d299b4e90a4266202e2e60a6c
+#: ../../hypervisor/hyperv.rst:78
+msgid "New folders in the /Share director y"
+msgstr ""
+
+# 81267131a3fc4d27bf3bcfa5702952c3
+#: ../../hypervisor/hyperv.rst:78
+msgid ""
+"Ensure that folders are created for Primary and Secondary storage. The SMB "
+"share and the hosts should be part of the same domain."
+msgstr "确保为主存储和辅助存储创建了文件夹。SMB共享和主机应该在同一个域内。"
+
+# 22eb1d2d75ef4c2b898ba205496f1923
+#: ../../hypervisor/hyperv.rst:82
+msgid ""
+"If you are using Windows SMB share, the location of the file share for the "
+"Hyper-V deployment will be the new folder created in the \\\\Shares on the "
+"selected volume. You can create sub-folders for both PRODUCT Primary and "
+"Secondary storage within the share location. When you select the profile for"
+" the file shares, ensure that you select SMB Share -Applications. This "
+"creates the file shares with settings appropriate for Hyper-V."
+msgstr ""
+
+# 4ffc82e6d7e845dfa1b880966b6d4564
+#: ../../hypervisor/hyperv.rst:92
+msgid "Domain and Hosts"
+msgstr "域和主机"
+
+# a9f0efdf8d5a493d82c08b429664d7b1
+#: ../../hypervisor/hyperv.rst:92
+msgid "Hosts should be part of the same Active Directory domain."
+msgstr "主机都应该加入AD域。"
+
+# a92cae038f1a46f789f2c08a44dcd92c
+#: ../../hypervisor/hyperv.rst:95
+msgid "Hyper-V Users"
+msgstr "Hyper-V用户"
+
+# 97f0324a2e62434a98f3f91e9478e6f4
+#: ../../hypervisor/hyperv.rst:95
+msgid "Full control"
+msgstr "完全控制权限"
+
+# 0bcab591e0f042dc8574a8c57b363303
+#: ../../hypervisor/hyperv.rst:95
+msgid "Full control on the SMB file share."
+msgstr "SMB文件共享有完全控制权限"
+
+# ee9dcfd392f84b7790d3017d9a958d69
+#: ../../hypervisor/hyperv.rst:98
+msgid "Virtual Switch"
+msgstr "虚拟交换机"
+
+# 84b516f8c0844014922eb947cca2b078
+#: ../../hypervisor/hyperv.rst:98
+msgid ""
+"If you are using Hyper-V 2012 R2, manually create an external virtual switch"
+" before adding the host to PRODUCT. If the Hyper-V host is added to the "
+"Hyper-V manager, select the host, then click Virtual Switch Manager, then "
+"New Virtual Switch. In the External Network, select the desired NIC adapter "
+"and click Apply."
+msgstr ""
+
+# 02cd2a7fcf2e4b109e8c6ca41162ea8c
+# 985a36a6ae43480081c0d0b588f48aad
+#: ../../hypervisor/hyperv.rst:106 ../../hypervisor/hyperv.rst:237
+msgid ""
+"If you are using Windows 2012 R2, virtual switch is created automatically."
+msgstr "如果使用Windows 2012 R2，虚拟交换机会自动创建。"
+
+# 7c5051f047ec44a491a9a65e006d5f80
+#: ../../hypervisor/hyperv.rst:109
+msgid "Virtual Switch Name"
+msgstr "虚拟交换机名称"
+
+# cfebf27404b04a1799cecac6f0d87e84
+#: ../../hypervisor/hyperv.rst:109
+msgid ""
+"Take a note of the name of the virtual switch. You need to specify that when"
+" configuring PRODUCT physical network labels."
+msgstr ""
+
+# ad1036d7fef9481ca332cd4247790520
+#: ../../hypervisor/hyperv.rst:113
+msgid "Hyper-V Domain Users"
+msgstr "Hyper-V 域用户"
+
+# 4c2560df94de47199684bb4acfd7808b
+#: ../../hypervisor/hyperv.rst:113
+msgid "Add the Hyper-V domain users to the Hyper-V Administrators group."
+msgstr "将Hyper-V域用户添加到Hyper-V管理员组中。"
+
+# 6571afa7b1d446baaebeff5f13b1e3e8
+#: ../../hypervisor/hyperv.rst:116
+msgid ""
+"A domain user should have full control on the SMB share that is exported for"
+" primary and secondary storage."
+msgstr "域用户应该对提供主存储和辅助存储的SMB共享拥有完全控制权限。"
+
+# b88a4f4ee49d4182aff6ba298990d862
+#: ../../hypervisor/hyperv.rst:120
+msgid ""
+"This domain user should be part of the Hyper-V Administrators and Local "
+"Administrators group on the Hyper-V hosts that are to be managed by PRODUCT."
+msgstr ""
+
+# a99dc8722cb14924894d5b59a0f7a3bb
+#: ../../hypervisor/hyperv.rst:125
+msgid ""
+"The Hyper-V Agent service runs with the credentials of this domain user "
+"account."
+msgstr "Hyper-V代理服务使用域用户账号身份运行。"
+
+# 39ee910d4ba544e2b28f18e65ac8a889
+#: ../../hypervisor/hyperv.rst:128
+msgid ""
+"Specify the credential of the domain user while adding a host to PRODUCT so "
+"that it can manage it."
+msgstr ""
+
+# 2c879cedc51b41c9ac25284b8676b011
+#: ../../hypervisor/hyperv.rst:132
+msgid ""
+"Specify the credential of the domain user while adding a shared SMB primary "
+"or secondary storage."
+msgstr "在添加SMB共享的主存储或者辅助存储时请指定域用户凭证。"
+
+# a9e85836b0a04d6794af8975a728757c
+# 6cf6d3303dc24afba8c72b0ac1f61aa5
+# 1399d631b8b94a1b935d4e56999a727a
+#: ../../hypervisor/hyperv.rst:136 ../../hypervisor/hyperv.rst:139
+#: ../../hypervisor/hyperv.rst:144
+msgid "Migration"
+msgstr "迁移"
+
+# 9b65f73f4def43419096db3143353cdd
+#: ../../hypervisor/hyperv.rst:136
+msgid "Migratio n"
+msgstr ""
+
+# dc9b9f2328ac4f3ebb5725c452140827
+#: ../../hypervisor/hyperv.rst:136
+msgid "Enable Migration."
+msgstr "启用迁移。"
+
+# 516666dbd8874b3ca81518e553176a9f
+#: ../../hypervisor/hyperv.rst:139
+msgid "Delegati on"
+msgstr ""
+
+# af14af2a223b4526acb445f35ff387fe
+#: ../../hypervisor/hyperv.rst:139
+msgid ""
+"If you want to use Live Migration, enable Delegation. Enable the following "
+"services of other hosts participating in Live Migration: CIFS and Microsoft "
+"Virtual System Migration Service."
+msgstr "如果想使用在线迁移，请启用指派。请在使用在线迁移的主机上启用下列服务：CIFS和Microsoft Virtual System Migration Service。"
+
+# a44c5e1eebd24499a9a3c60210231d65
+#: ../../hypervisor/hyperv.rst:144
+msgid "Kerberos"
+msgstr "Kerberos"
+
+# dfad3d88e2c44f009ba6a629d2d11e09
+#: ../../hypervisor/hyperv.rst:144
+msgid "Enable Kerberos for Live Migration."
+msgstr "为在线迁移启用Kerberos。"
+
+# 8a1e170e190d499ca5cca07a1df60781
+#: ../../hypervisor/hyperv.rst:146
+msgid "Network Access Permission for Dial-in"
+msgstr "拨号访问网络权限"
+
+# 25fcf66d3708461798a6ccaae50eaf2e
+#: ../../hypervisor/hyperv.rst:146
+msgid "Allow access"
+msgstr "允许访问"
+
+# c278cbf02bda42f8a6dd149a89346803
+#: ../../hypervisor/hyperv.rst:146
+msgid "Allow access for Dial-in connections."
+msgstr "允许拨号连接访问"
+
+# ee52be753a9f4e339af5f44dbd6ae389
+#: ../../hypervisor/hyperv.rst:155
+msgid "Hyper-V Installation Steps"
+msgstr "Hyper-V安装步骤"
+
+# 5e6a34d960324a189dba8dafc3199b3f
+#: ../../hypervisor/hyperv.rst:157
+msgid ""
+"Download the operating system from `Windows Server 2012 R2 "
+"<http://technet.microsoft.com/en-us/windowsserver/hh534429>`_."
+msgstr "下载操作系统 `Windows Server 2012 R2 <http://technet.microsoft.com/en-us/windowsserver/hh534429>`_ 。"
+
+# ffa1994b12b44c7aad4386869fd9fcf3
+#: ../../hypervisor/hyperv.rst:160
+msgid ""
+"Install it on the host as given in `Install and Deploy Windows Server 2012 "
+"R2 <http://technet.microsoft.com/library/hh831620>`_."
+msgstr "按照 `Install and Deploy Windows Server 2012 R2 <http://technet.microsoft.com/library/hh831620>`_ 安装操作系统。"
+
+# a13474286278439686c5ee1893cd2bb1
+#: ../../hypervisor/hyperv.rst:163
+msgid "Post installation, ensure that you enable Hyper-V role in the server."
+msgstr "安装后，请确保安装Hyper-V角色。"
+
+# 7879473d0a8c43d0b28378281f2486d9
+#: ../../hypervisor/hyperv.rst:165
+msgid ""
+"If no Active Directory domain exists in your deployment, create one and add "
+"users to the domain."
+msgstr "如果当前环境中没有使用AD域，请部署AD域并添加域用户。"
+
+# 470dd82226bd40d19ad39f3ebe2389c2
+#: ../../hypervisor/hyperv.rst:168
+msgid ""
+"In the Active Directory domain, ensure that all the Hyper-v hosts are added "
+"so that all the hosts are part of the domain."
+msgstr "如果存在AD域，确保所有的Hyper-V主机都加入了域。"
+
+# da2cd8c727fa4b4bad3c78af98264cb0
+#: ../../hypervisor/hyperv.rst:171
+msgid ""
+"Add the domain user to the following groups on the Hyper-V host: Hyper-V "
+"Administrators and Local Administrators."
+msgstr "添加域用户到下列Hyper-V主机的用户组中： Hyper-V Administrators和Local Administrators。"
+
+# 4643f2a8b84e4e2ebbe709f5ffe25c84
+#: ../../hypervisor/hyperv.rst:176
+msgid "Installing the CloudStack Agent on a Hyper-V Host"
+msgstr "在Hyper-V主机中安装CloudStack代理"
+
+# 3ab695eb9dee461ea69f8078437525b4
+#: ../../hypervisor/hyperv.rst:178
+msgid ""
+"The Hyper-V Agent helps CloudStack perform operations on the Hyper-V hosts. "
+"This Agent communicates with the Management Server and controls all the "
+"instances on the host. Each Hyper-V host must have the Hyper-V Agent "
+"installed on it for successful interaction between the host and CloudStack. "
+"The Hyper-V Agent runs as a Windows service. Install the Agent on each host "
+"using the following steps."
+msgstr "Hyper-V代理帮助CloudStack操作Hyper-V主机。代理与管理服务器通讯并控制主机上的所有实例。为了让主机与CloudStack之间成功的进行交互，每个Hyper-V主机必须安装Hyper-V代理。Hyper-V代理作为Windows的系统服务运行。按照下里的步骤在每台主机上安装Agent。"
+
+# 481e02540708427aae673f5e8c5c81c0
+#: ../../hypervisor/hyperv.rst:185
+msgid ""
+"CloudStack Management Server communicates with Hyper-V Agent by using HTTPS."
+" For secure communication between the Management Server and the host, "
+"install a self-signed certificate on port 8250."
+msgstr "CloudStack管理服务器使用HTTPS与Hyper-V代理通讯。为了使管理服务器与主机之间能够使用加密通讯，请在8250端口上绑定自签名证书。"
+
+# 79d9ee71e1814e18ae066a37a64ccf0f
+#: ../../hypervisor/hyperv.rst:190
+msgid ""
+"The Agent installer automatically perform this operation. You have not "
+"selected this option during the Agent installation, it can also be done "
+"manually as given in step 1."
+msgstr "代理的安装程序会自动执行这个操作。在代理的安装过程中可以不选择该选项，它可以在步骤1中手动操作。"
+
+# 9e04f652b33b4fdaa6d33622de1f6c16
+#: ../../hypervisor/hyperv.rst:194
+msgid "Create and add a self-signed SSL certificate on port 8250:"
+msgstr "为8250端口创建并添加一个自签名证书："
+
+# 71791cb8679f449ea9810f71aea6642a
+#: ../../hypervisor/hyperv.rst:196
+msgid "Create A self-signed SSL certificate:"
+msgstr "创建一个自签名证书："
+
+# bf728cee5a7a4b65b04ede76db396b30
+#: ../../hypervisor/hyperv.rst:202
+msgid ""
+"This command creates the self-signed certificate and add that to the "
+"certificate store ``LocalMachine\\My``."
+msgstr "该命令创建一个自签名证书并将添加到 ``LocalMachine\\My`` 证书区域。"
+
+# f464d4439cc44510b140754a2c06e458
+#: ../../hypervisor/hyperv.rst:205
+msgid "Add the created certificate to port 8250 for https communication:"
+msgstr "将创建好的证书绑定到https通信的8250端口："
+
+# 870daf8bb8194bc5872d413d1cdea8a0
+#: ../../hypervisor/hyperv.rst:211
+msgid "Thumbprint is the thumbprint of the certificate you created."
+msgstr "Thumbprint是你创建证书的指纹。"
+
+# 43b892a6de7040a1b7465f30523308d8
+#: ../../hypervisor/hyperv.rst:213
+msgid ""
+"Build the CloudStack Agent for Hyper-V as given in `Building CloudStack "
+"Hyper-V Agent "
+"<https://cwiki.apache.org/confluence/display/CLOUDSTACK/Creating+Hyperv+Agent+Installer>`__."
+msgstr "按照 `编辑 CloudStack Hyper-V 代理 <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Creating+Hyperv+Agent+Installer>`__编译CloudStack代理程序。"
+
+# 947a2a5df4c84a128f9d8fae319c8153
+#: ../../hypervisor/hyperv.rst:216
+msgid "As an administrator, run the installer."
+msgstr "以管理员权限运行安装。"
+
+# 19b6346a3cb94ec59710f84565f8f65c
+#: ../../hypervisor/hyperv.rst:218
+msgid "Provide the Hyper-V admin credentials when prompted."
+msgstr "在对话框中输入Hyper-V管理员凭证。"
+
+# f254b72c1df64645831780947bef0830
+#: ../../hypervisor/hyperv.rst:220
+msgid ""
+"When the agent installation is finished, the agent runs as a service on the "
+"host machine."
+msgstr "当代理安装完成之后，代理已经作为系统服务启动了。"
+
+# 1a5dd8f4c84b4b2aa53baa0f573b51ce
+#: ../../hypervisor/hyperv.rst:225
+msgid "Physical Network Configuration for Hyper-V"
+msgstr "为Hyper-V配置物理网络"
+
+# 380cb814510b419697ab9623d9466f8e
+#: ../../hypervisor/hyperv.rst:227
+msgid ""
+"You should have a plan for how the hosts will be cabled and which physical "
+"NICs will carry what types of traffic. By default, CloudStack will use the "
+"device that is used for the default route."
+msgstr "需要先对主机连线以及网卡绑定哪种流量做出规划。默认情况下，CloudStack将正在被使用的设备作为默认路由。"
+
+# d473bf7504d0430ca53e00c7294017bc
+#: ../../hypervisor/hyperv.rst:231
+msgid ""
+"If you are using Hyper-V 2012 R2, manually create an external virtual switch"
+" before adding the host to CloudStack. If the Hyper-V host is added to the "
+"Hyper-V manager, select the host, then click Virtual Switch Manager, then "
+"New Virtual Switch. In the External Network, select the desired NIC adapter "
+"and click Apply."
+msgstr "如果你使用Hyper-V 2012 R2，在将主机添加到CloudStack中之前，请手动创建一个外部网络虚拟交换机。如果Hyper-V管理器已经添加了Hyper-V主机，选择该主机，然后点击虚拟交换机管理器，新建虚拟交换机。在外部网络，选择所需的网卡然后点击应用。 "
+
+# 7f2f77fa086a4dba967596b9382888ed
+#: ../../hypervisor/hyperv.rst:242
+msgid "Storage Preparation for Hyper-V (Optional)"
+msgstr "为Hyper-V准备存储（可选）"
+
+# b30ee4d30a1341bc8d882e9053000bd4
+#: ../../hypervisor/hyperv.rst:244
+msgid ""
+"CloudStack allows administrators to set up shared Primary Storage and "
+"Secondary Storage that uses SMB."
+msgstr "CloudStack允许管理员使用SMB共享作为主存储和辅助存储。"
+
+# 4caaf6cc083841b2aeaf487f0f1ec4a0
+#: ../../hypervisor/hyperv.rst:247
+msgid "Create a SMB storage and expose it over SMB Version 3."
+msgstr "创建一个使用SMB v3协议的SMB存储"
+
+# d49322cf1c1d4f8d8c9ceed36c959d0f
+#: ../../hypervisor/hyperv.rst:249
+msgid ""
+"For more information, see `Deploying Hyper-V over SMB "
+"<http://technet.microsoft.com/en-us/library/jj134187.aspx>`_."
+msgstr "更多信息，请参考 `部署基于SMB的Hyper-V <http://technet.microsoft.com/en-us/library/jj134187.aspx>`_."
+
+# 9aefadf6e86e499c98acbb5785e98930
+#: ../../hypervisor/hyperv.rst:252
+msgid ""
+"You can also create and export SMB share using Windows. After the Windows "
+"Server 2012 R2 installation, select File and Storage Services from Server "
+"Roles to create an SMB file share. For more information, see `Creating an "
+"SMB File Share Using Server Manager <http://technet.microsoft.com/en-"
+"us/library/jj134187.aspx#BKMK_Step3>`_."
+msgstr "同样可以使用Windows创建并发布SMB共享。在Windows Server 2012 R2安装完成之后，在服务器角色中选择安装文件和存储服务以便创建SMB文件共享。更多信息，请参考 `通过使用服务器管理器 (SM) 创建 SMB 文件共享系统 <http://technet.microsoft.com/zh-cn/library/jj134187.aspx#BKMK_Step3>`_。"
+
+# 484e3791c2844730a548c8da780b2bf4
+#: ../../hypervisor/hyperv.rst:258
+msgid "Add the SMB share to the Active Directory domain."
+msgstr "在AD域中添加SMB共享。"
+
+# 1917261171b047b58051d75066e5fb9a
+#: ../../hypervisor/hyperv.rst:260
+msgid ""
+"The SMB share and the hosts managed by CloudStack need to be in the same "
+"domain. However, the storage should be accessible from the Management Server"
+" with the domain user privileges."
+msgstr "SMB共享和通过CloudStack管理的主机必须在同一个域内。管理服务器可以使用域用户凭证访问存储。"
+
+# 5c7bf0eee6784b07ba689b0964ebdb37
+#: ../../hypervisor/hyperv.rst:264
+msgid ""
+"While adding storage to CloudStack, ensure that the correct domain, and "
+"credentials are supplied. This user should be able to access the storage "
+"from the Management Server."
+msgstr "在CloudStack中添加存储时，请确保提供的域和凭证是正确的。确保用户可以通过管理服务器访问存储。"
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/kvm.mo b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/kvm.mo
new file mode 100644
index 0000000..701cc85
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/kvm.mo
Binary files differ
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/kvm.po b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/kvm.po
new file mode 100644
index 0000000..def7817
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/kvm.po
@@ -0,0 +1,1095 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: 2014-06-30 10:26+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# ebeb1b4a092d444ea21ba9ad826adffe
+#: ../../hypervisor/kvm.rst:18
+msgid "KVM Hypervisor Host Installation"
+msgstr "KVM Hypervisor主机安装"
+
+# 97cb5ce75570443fb1ad7cf720fdab2a
+#: ../../hypervisor/kvm.rst:21
+msgid "System Requirements for KVM Hypervisor Hosts"
+msgstr "KVM Hypervisor 主机系统要求"
+
+# 9e938eeaf34e4bacb41261551600a15d
+#: ../../hypervisor/kvm.rst:23
+msgid ""
+"KVM is included with a variety of Linux-based operating systems. Although "
+"you are not required to run these distributions, the following are "
+"recommended:"
+msgstr "KVM包含在多种基于Linux的操作系统中。尽管不作要求，但是我们推荐以下发行版："
+
+# 01060377fba240b98bfb3214ded11e8c
+#: ../../hypervisor/kvm.rst:27
+msgid "CentOS / RHEL: 6.3"
+msgstr "CentOS / RHEL: 6.3"
+
+# c65d0ad029984ec697cc18cf30a3cadc
+#: ../../hypervisor/kvm.rst:29
+msgid "Ubuntu: 12.04(.1)"
+msgstr "Ubuntu: 12.04(.1)"
+
+# 2c83e5c69a214b408332608c4f0cd35c
+#: ../../hypervisor/kvm.rst:31
+msgid ""
+"The main requirement for KVM hypervisors is the libvirt and Qemu version. No"
+" matter what Linux distribution you are using, make sure the following "
+"requirements are met:"
+msgstr "KVM hypervisors主要要求在于libvirt和Qemu版本。不管您使用何种Linux版本，请确保满足以下要求："
+
+# 41d119144cb04445888526ae22eaff17
+#: ../../hypervisor/kvm.rst:35
+msgid "libvirt: 0.9.4 or higher"
+msgstr "libvirt: 0.9.4 或更高版本"
+
+# c01a69a6ea624526aed8eb093c9580c7
+#: ../../hypervisor/kvm.rst:37
+msgid "Qemu/KVM: 1.0 or higher"
+msgstr "Qemu/KVM: 1.0 或更高版本"
+
+# 651ec4f15bf24d0ca383e80951a6ab85
+#: ../../hypervisor/kvm.rst:39
+msgid ""
+"The default bridge in CloudStack is the Linux native bridge implementation "
+"(bridge module). CloudStack includes an option to work with OpenVswitch, the"
+" requirements are listed below"
+msgstr "CloudStack中的默认使用Linux本身的桥接(bridge模块)方式实现。也可选择在CloudStack中使用OpenVswitch，具体要求如下："
+
+# 38d4ca03c8c24e2c9d6cd87e5c0b1d17
+#: ../../hypervisor/kvm.rst:43
+msgid "libvirt: 0.9.11 or higher"
+msgstr "libvirt: 0.9.11 或更高版本"
+
+# 55b8b19e86c9462297d454cf0f32bb13
+#: ../../hypervisor/kvm.rst:45
+msgid "openvswitch: 1.7.1 or higher"
+msgstr "openvswitch: 1.7.1或更高版本"
+
+# 8bb45c3db83e4685a2f5f9b56c255a67
+#: ../../hypervisor/kvm.rst:47
+msgid "In addition, the following hardware requirements apply:"
+msgstr "此外，硬件要求如下："
+
+# a3affcf8d2194e6ca7031037e7498bea
+#: ../../hypervisor/kvm.rst:49
+msgid ""
+"Within a single cluster, the hosts must be of the same distribution version."
+msgstr "同一集群中主机必须使用相同版本的Linux系统。"
+
+# fc001eaf8fb842d7adbbf5bb977be8fd
+#: ../../hypervisor/kvm.rst:52
+msgid ""
+"All hosts within a cluster must be homogenous. The CPUs must be of the same "
+"type, count, and feature flags."
+msgstr "同一群集中的所有节点架构必须一致。CPU的型号、数量和功能参数必须相同。"
+
+# 040002ad5b674b0c821aa9750f44d966
+#: ../../hypervisor/kvm.rst:55
+msgid "Must support HVM (Intel-VT or AMD-V enabled)"
+msgstr "必须支持HVM(Intel-VT或者AMD-V)"
+
+# 430eb7a34d084edc906c29088ecd022d
+#: ../../hypervisor/kvm.rst:57
+msgid "64-bit x86 CPU (more cores results in better performance)"
+msgstr "64位x86 CPU(多核性能更佳)"
+
+# 7a5ab30337ea4ad3911e07092171034c
+#: ../../hypervisor/kvm.rst:59
+msgid "4 GB of memory"
+msgstr "4GB 内存"
+
+# 54804b801477441396a656d1f55ce683
+#: ../../hypervisor/kvm.rst:61
+msgid "At least 1 NIC"
+msgstr "至少一块网卡"
+
+# 3d590f343f0c40e8a3ead4dd2fe2fa47
+#: ../../hypervisor/kvm.rst:63
+msgid ""
+"When you deploy CloudStack, the hypervisor host must not have any VMs "
+"already running"
+msgstr "在部署CloudStack时，Hypervisor主机不能运行任何虚拟机"
+
+# 8b68c1fe985341dcb44b491222fc84ad
+#: ../../hypervisor/kvm.rst:68
+msgid "KVM Installation Overview"
+msgstr "KVM安装概述"
+
+# b9ec75165d5f4c29afccc0e271256a34
+#: ../../hypervisor/kvm.rst:70
+msgid ""
+"If you want to use the Linux Kernel Virtual Machine (KVM) hypervisor to run "
+"guest virtual machines, install KVM on the host(s) in your cloud. The "
+"material in this section doesn't duplicate KVM installation docs. It "
+"provides the CloudStack-specific steps that are needed to prepare a KVM host"
+" to work with CloudStack."
+msgstr "如果你想使用 KVM hypervisor来运行虚拟机，请在你的云环境中安装KVM主机。本章节不会复述KVM的安装文档。它提供了KVM主机与CloudStack协同工作所要准备特有的步骤。"
+
+# f5be326bc3d74ee58f731bc68b96b0fb
+#: ../../hypervisor/kvm.rst:77
+msgid ""
+"Before continuing, make sure that you have applied the latest updates to "
+"your host."
+msgstr "在我们开始之前，请确保所有的主机都安装了最新的更新包。"
+
+# 4e04ebf1f4b34b6cafaa81b1db7348cb
+#: ../../hypervisor/kvm.rst:81
+msgid ""
+"It is NOT recommended to run services on this host not controlled by "
+"CloudStack."
+msgstr "不建议在主机中运行与CloudStack无关的服务。"
+
+# 05cc9620411849a395036ae746c8c8ab
+#: ../../hypervisor/kvm.rst:84
+msgid "The procedure for installing a KVM Hypervisor Host is:"
+msgstr "安装KVM主机的过程："
+
+# 6021037c1bdc4f11a0e777ddb5074991
+# 2587ced26d8445e89dc4b8dc2392793f
+#: ../../hypervisor/kvm.rst:86 ../../hypervisor/kvm.rst:96
+msgid "Prepare the Operating System"
+msgstr "准备操作系统"
+
+# 3e3ad1c9b475475d8c6d84148d8a187b
+#: ../../hypervisor/kvm.rst:88
+msgid "Install and configure libvirt"
+msgstr "安装和配置libvirt"
+
+# bfef16f0f0344071beb3918d9b215e58
+#: ../../hypervisor/kvm.rst:90
+msgid "Configure Security Policies (AppArmor and SELinux)"
+msgstr "配置安全策略 (AppArmor 和 SELinux)"
+
+# 4343245b910e46b2889fad1a299a3a6d
+# 13ebc121a8db4e73b1da322e022b044e
+#: ../../hypervisor/kvm.rst:92 ../../hypervisor/kvm.rst:139
+msgid "Install and configure the Agent"
+msgstr "安装和配置Agent"
+
+# 0da476eb6feb4293aff700a82bfb838e
+#: ../../hypervisor/kvm.rst:98
+msgid ""
+"The OS of the Host must be prepared to host the CloudStack Agent and run KVM"
+" instances."
+msgstr "主机的操作系统必须为运行CloudStack Agent和KVM实例做些准备。"
+
+# bdd309f671e84b25b03a65509e8f6b42
+#: ../../hypervisor/kvm.rst:101
+msgid "Log in to your OS as root."
+msgstr "使用root用户登录操作系统。"
+
+# 2994046162c749719c61badf46ac4ad3
+#: ../../hypervisor/kvm.rst:103
+msgid "Check for a fully qualified hostname."
+msgstr "检查FQN完全合格/限定主机名。"
+
+# 7140e2b27dea40f8b406eb3c53a6926a
+#: ../../hypervisor/kvm.rst:109
+msgid ""
+"This should return a fully qualified hostname such as "
+"\"kvm1.lab.example.org\". If it does not, edit /etc/hosts so that it does."
+msgstr "该命令会返回完全合格/限定主机名，例如\"kvm1.lab.example.org\"。如果没有，请编辑 /etc/hosts。"
+
+# d097f223788942dca1e0f0e3a835719d
+#: ../../hypervisor/kvm.rst:113
+msgid "Make sure that the machine can reach the Internet."
+msgstr "确保机器可以连接到互联网."
+
+# e9e925f675b24298904628fe8d5d3e22
+#: ../../hypervisor/kvm.rst:119
+msgid "Turn on NTP for time synchronization."
+msgstr "启用NTP服务以确保时间同步."
+
+# e0e2735eb1544cbea55afc3efd41e42e
+#: ../../hypervisor/kvm.rst:122
+msgid ""
+"NTP is required to synchronize the clocks of the servers in your cloud. "
+"Unsynchronized clocks can cause unexpected problems."
+msgstr "NTP服务用来同步云中的服务器时间。时间不同步会带来意想不到的问题。"
+
+# fd84cef5844c4bb4861e1a723be7b730
+#: ../../hypervisor/kvm.rst:125
+msgid "Install NTP"
+msgstr "安装NTP"
+
+# 43ee16ce469842bdb337c3e50b34061c
+#: ../../hypervisor/kvm.rst:135
+msgid "Repeat all of these steps on every hypervisor host."
+msgstr "在所有主机中重复上述步骤。"
+
+# 5fe0d335c6f646c987b8e7f2c3c9176d
+#: ../../hypervisor/kvm.rst:141
+msgid ""
+"To manage KVM instances on the host CloudStack uses a Agent. This Agent "
+"communicates with the Management server and controls all the instances on "
+"the host."
+msgstr "CloudStack使用Agent来管理KVM实例。Agent与管理服务器通讯并控制主机上所有的虚拟机。"
+
+# 6e696930e763476fabe3f4eee7ff4119
+#: ../../hypervisor/kvm.rst:145
+msgid "First we start by installing the agent:"
+msgstr "首先我们安装Agent："
+
+# 707c5512b9c244b29a78dff8a4299a43
+# 1640e85f451b43bf9287ea34e03d19d0
+# 7296990676914572906f8131a2c931ca
+#: ../../hypervisor/kvm.rst:147 ../../hypervisor/kvm.rst:297
+#: ../../hypervisor/kvm.rst:333
+msgid "In RHEL or CentOS:"
+msgstr "在RHEL/CentOS上:"
+
+# b558c002a308451c962adfba860db12a
+# c6cfcfd744df46039292c75ce9c00344
+#: ../../hypervisor/kvm.rst:153 ../../hypervisor/kvm.rst:303
+msgid "In Ubuntu:"
+msgstr "在Ubuntu上:"
+
+# 996e7f4699cf4e99812ef4193d0f5522
+# 0066de97fb884b43b6b6e86bdc4a8d19
+#: ../../hypervisor/kvm.rst:159 ../../hypervisor/kvm.rst:880
+msgid ""
+"The host is now ready to be added to a cluster. This is covered in a later "
+"section, see :ref:`adding-a-host`. It is recommended that you continue to "
+"read the documentation before adding the host!"
+msgstr "现在主机已经为加入群集做好准备。后面的章节有介绍，请参阅 :ref:`adding-a-host`。强烈建议在添加主机之前阅读此部分内容。"
+
+# 4896f6ced9d2426d815ed0b39e1f2f4a
+#: ../../hypervisor/kvm.rst:166
+msgid "Configure CPU model for KVM guest (Optional)"
+msgstr "配置KVM虚拟机的CPU型号(可选)"
+
+# 20ff9499c4f34a21932f12ab3ace15d5
+#: ../../hypervisor/kvm.rst:168
+msgid ""
+"In additional,the CloudStack Agent allows host administrator to control the "
+"guest CPU model which is exposed to KVM instances. By default, the CPU model"
+" of KVM instance is likely QEMU Virtual CPU version x.x.x with least CPU "
+"features exposed. There are a couple of reasons to specify the CPU model:"
+msgstr "此外，CloudStack Agent允许主机管理员控制KVM实例中的CPU型号。默认情况下，KVM实例的CPU型号为只有少数CPU特性且版本为xxx的QEMU Virtual CPU。指定CPU型号有几个原因："
+
+# 6e0e4449f4ec4464a09f85e60e4370ed
+#: ../../hypervisor/kvm.rst:174
+msgid ""
+"To maximise performance of instances by exposing new host CPU features to "
+"the KVM instances;"
+msgstr "通过主机CPU的特性最大化提升KVM实例的性能；"
+
+# c7628f91810a40ccb39bcf8305be59da
+#: ../../hypervisor/kvm.rst:177
+msgid ""
+"To ensure a consistent default CPU across all machines,removing reliance of "
+"variable QEMU defaults;"
+msgstr "确保所有机器的默认CPU保持一致，消除对QEMU变量的依赖。"
+
+# c7ea77c20a4345ba96d87413aa516fb5
+#: ../../hypervisor/kvm.rst:180
+msgid ""
+"For the most part it will be sufficient for the host administrator to "
+"specify the guest CPU config in the per-host configuration file "
+"(/etc/cloudstack/agent/agent.properties). This will be achieved by "
+"introducing two new configuration parameters:"
+msgstr "在大多数情况下,主机管理员需要每个主机配置文件(/etc/cloudstack/agent/agent.properties)中指定guest虚拟机的CPU配置。这将通过引入两个新的配置参数来实现："
+
+# b49256d2460d47f688c7624e3f4e6a72
+#: ../../hypervisor/kvm.rst:190
+msgid "There are three choices to fulfill the cpu model changes:"
+msgstr "更改CPU型号有三个选择："
+
+# 07a33361eda847d59a1ac15adc6af65f
+#: ../../hypervisor/kvm.rst:192
+msgid ""
+"**custom:** you can explicitly specify one of the supported named model in "
+"/usr/share/libvirt/cpu\\_map.xml"
+msgstr "**custom:** 您可以指定一个在/usr/share/libvirt/cpu\\_map.xml文件中所支持的型号名称。"
+
+# 6282d4279ada4fb88884fea8fd73cd06
+#: ../../hypervisor/kvm.rst:195
+msgid ""
+"**host-model:** libvirt will identify the CPU model in "
+"/usr/share/libvirt/cpu\\_map.xml which most closely matches the host, and "
+"then request additional CPU flags to complete the match. This should give "
+"close to maximum functionality/performance, which maintaining good "
+"reliability/compatibility if the guest is migrated to another host with "
+"slightly different host CPUs."
+msgstr "**host-model:** libvirt可以识别出在/usr/share/libvirt/cpu\\_map.xml中与主机最接近的CPU型号，然后请求其他的CPU flags完成匹配。如果虚拟机迁移到其他CPU稍有不同的主机中，保持好的可靠性/兼容性能提供最多的功能和最大限度提示的性能。"
+
+# f8b3348db3b04cfaa45ddadb3e295515
+#: ../../hypervisor/kvm.rst:202
+msgid ""
+"**host-passthrough:** libvirt will tell KVM to passthrough the host CPU with"
+" no modifications. The difference to host-model, instead of just matching "
+"feature flags, every last detail of the host CPU is matched. This gives "
+"absolutely best performance, and can be important to some apps which check "
+"low level CPU details, but it comes at a cost with respect to migration: the"
+" guest can only be migrated to an exactly matching host CPU."
+msgstr "**host-passthrough:** libvirt 会告诉KVM没有修改过CPU passthrough的主机。与host-model的差别是不仅匹配flags特性，还要匹配CPU的每一个特性。他能提供最好的性能， 同时对一些检查CPU底层特性的应用程序很重要，但这样会带来一些迁移的代价：虚拟机只会迁移到CPU完全匹配的主机上。"
+
+# 47f1633a109745c68733dbe0a7ba9ce9
+#: ../../hypervisor/kvm.rst:210
+msgid "Here are some examples:"
+msgstr "这里有一些示例："
+
+# d710e6fa4277486c8d61b2f169b7f2b3
+#: ../../hypervisor/kvm.rst:212
+msgid "custom"
+msgstr "custom"
+
+# f5b710b35db840c7affadc4299dae2e5
+#: ../../hypervisor/kvm.rst:219
+msgid "host-model"
+msgstr "host-model"
+
+# aecbb45afbe5482aa5532e1d54f55842
+#: ../../hypervisor/kvm.rst:225
+msgid "host-passthrough"
+msgstr "host-passthrough"
+
+# fb86e9deb45745bd9fac900c4f7e7ec6
+#: ../../hypervisor/kvm.rst:232
+msgid ""
+"host-passthrough may lead to migration failure,if you have this problem, you"
+" should use host-model or custom"
+msgstr ""
+
+# 00afd93377104391bc056ba2988ad1d5
+#: ../../hypervisor/kvm.rst:237
+msgid "Install and Configure libvirt"
+msgstr "安装和配置libvirt"
+
+# ac5f3de595104874aca72f9e3e908bb2
+#: ../../hypervisor/kvm.rst:239
+msgid ""
+"CloudStack uses libvirt for managing virtual machines. Therefore it is vital"
+" that libvirt is configured correctly. Libvirt is a dependency of "
+"cloudstack-agent and should already be installed."
+msgstr "CloudStack使用libvirt管理虚拟机。因此正确地配置libvirt至关重要。CloudStack-agent依赖于Libvirt，应提前安装完毕。"
+
+# ed8dd766459147cbb85ff50d90c4b80e
+#: ../../hypervisor/kvm.rst:243
+msgid ""
+"In order to have live migration working libvirt has to listen for unsecured "
+"TCP connections. We also need to turn off libvirts attempt to use Multicast "
+"DNS advertising. Both of these settings are in "
+"``/etc/libvirt/libvirtd.conf``"
+msgstr "为了实现动态迁移libvirt需要监听不可靠的TCP连接。还要关闭libvirts尝试使用组播DNS进行广播。这些都可以在 /etc/libvirt/libvirtd.conf文件中进行配置。"
+
+# 25fdfe15f0fd4e42a8859066fd10be16
+#: ../../hypervisor/kvm.rst:248
+msgid "Set the following parameters:"
+msgstr "设定下列参数："
+
+# b077d28a7fb14c0da6df9ced98d909bd
+#: ../../hypervisor/kvm.rst:270
+msgid ""
+"Turning on \"listen\\_tcp\" in libvirtd.conf is not enough, we have to "
+"change the parameters as well:"
+msgstr "除了在libvirtd.conf中打开\"listen_tcp\"以外，我们还必须修改/etc/sysconfig/libvirtd中的参数:"
+
+# fe5a6a536a154770ac58fbf4ace2ce6e
+#: ../../hypervisor/kvm.rst:273
+msgid "On RHEL or CentOS modify ``/etc/sysconfig/libvirtd``:"
+msgstr "在RHEL或者CentOS中修改 ``/etc/sysconfig/libvirtd``："
+
+# d50d8ab0ec584f1bbdc8af56f6265ffc
+#: ../../hypervisor/kvm.rst:275
+msgid "Uncomment the following line:"
+msgstr "取消如下行的注释："
+
+# 3f26c856207e4381bf305695a8a1b875
+#: ../../hypervisor/kvm.rst:281
+msgid "On Ubuntu: modify ``/etc/default/libvirt-bin``"
+msgstr "在Ubuntu中:修改 ``/etc/default/libvirt-bin`` "
+
+# 6115b7018d9740c4913aacc4a4c661b2
+#: ../../hypervisor/kvm.rst:283
+msgid "Add \"-l\" to the following line"
+msgstr "在下列行添加 \"-l\""
+
+# fcea59d4e03647eeaeaa3ac4932357ac
+#: ../../hypervisor/kvm.rst:289
+msgid "so it looks like:"
+msgstr "如下所示:"
+
+# a61d4201e47640b197fdfbcd22c10e63
+#: ../../hypervisor/kvm.rst:295
+msgid "Restart libvirt"
+msgstr "重启libvirt服务"
+
+# f5d8d474c64344d19b502d403b56e5ac
+#: ../../hypervisor/kvm.rst:311
+msgid "Configure the Security Policies"
+msgstr "配置安全策略"
+
+# a4cdda146bad44b39bbc09b937240984
+#: ../../hypervisor/kvm.rst:313
+msgid ""
+"CloudStack does various things which can be blocked by security mechanisms "
+"like AppArmor and SELinux. These have to be disabled to ensure the Agent has"
+" all the required permissions."
+msgstr "CloudStack的会被例如AppArmor和SELinux的安全机制阻止。必须关闭安全机制并确保 Agent具有所必需的权限。"
+
+# 4b7a44bcec124017bf23bc0dd76e7428
+#: ../../hypervisor/kvm.rst:317
+msgid "Configure SELinux (RHEL and CentOS)"
+msgstr "配置SELinux（RHEL和CentOS）："
+
+# fc143c3fe742401a9106eafabea70c57
+#: ../../hypervisor/kvm.rst:319
+msgid ""
+"Check to see whether SELinux is installed on your machine. If not, you can "
+"skip this section."
+msgstr "检查你的机器是否安装了SELinux。如果没有，请跳过此部分。"
+
+# 2b54567dbb364fddb556f971dd10b551
+#: ../../hypervisor/kvm.rst:322
+msgid ""
+"In RHEL or CentOS, SELinux is installed and enabled by default. You can "
+"verify this with:"
+msgstr "在RHEL或者CentOS中，SELinux是默认安装并启动的。你可以使用如下命令验证："
+
+# 80c7202620bb48148e037b74df42ee70
+#: ../../hypervisor/kvm.rst:329
+msgid ""
+"Set the SELINUX variable in ``/etc/selinux/config`` to \"permissive\". This "
+"ensures that the permissive setting will be maintained after a system "
+"reboot."
+msgstr "在 ``/etc/selinux/config`` 中设置SELINUX变量值为 \"permissive\"。这样能确保对SELinux的设置在系统重启之后依然生效。"
+
+# 4cad5c113a6d40c78b1deced30e96b20
+#: ../../hypervisor/kvm.rst:339
+msgid "Change the following line"
+msgstr "查找如下行"
+
+# c97ebe4c24c3452b87cde950fe2fc4c8
+#: ../../hypervisor/kvm.rst:345
+msgid "to this"
+msgstr "修改为"
+
+# 1fe4df6a30c94763bdb8884755fdcdce
+#: ../../hypervisor/kvm.rst:351
+msgid ""
+"Then set SELinux to permissive starting immediately, without requiring a "
+"system reboot."
+msgstr "然后使SELinux立即运行于permissive模式，无需重新启动系统。"
+
+# 0af84eecf2664f6cb9301604df585e10
+#: ../../hypervisor/kvm.rst:358
+msgid "Configure Apparmor (Ubuntu)"
+msgstr "配置AppArmor(Ubuntu)"
+
+# fc4f77ded77f4d28afca68609461f0bb
+#: ../../hypervisor/kvm.rst:360
+msgid ""
+"Check to see whether AppArmor is installed on your machine. If not, you can "
+"skip this section."
+msgstr "检查你的机器中是否安装了AppArmor。如果没有，请跳过此部分。"
+
+# 04268552313d40f3a6be6f7a36fa99fe
+#: ../../hypervisor/kvm.rst:363
+msgid ""
+"In Ubuntu AppArmor is installed and enabled by default. You can verify this "
+"with:"
+msgstr "Ubuntu中默认安装并启动AppArmor。使用如下命令验证："
+
+# 6fd96cf6f5224881a383a21dd3963718
+#: ../../hypervisor/kvm.rst:370
+msgid "Disable the AppArmor profiles for libvirt"
+msgstr "在AppArmor配置文件中禁用libvirt"
+
+# af0b6b3d14164b38bb854739db62c3f5
+#: ../../hypervisor/kvm.rst:390
+msgid "Configure the network bridges"
+msgstr "配置网络桥接"
+
+# fa37fe8e08ec4f3a956c501d3aa88019
+# 4fa42c30b73c4240b8836f967070df3a
+#: ../../hypervisor/kvm.rst:393 ../../hypervisor/kvm.rst:616
+msgid ""
+"This is a very important section, please make sure you read this thoroughly."
+msgstr "本章节非常重要，请务必彻底理解。"
+
+# 9ec0bad9717b478889252f4b10b4ebf0
+#: ../../hypervisor/kvm.rst:396
+msgid ""
+"This section details how to configure bridges using the native "
+"implementation in Linux. Please refer to the next section if you intend to "
+"use OpenVswitch"
+msgstr "本章节详细介绍了如何使用Linux自带的软件配置桥接网络。如果要使用OpenVswitch，请看下一章节。"
+
+# f6707b5fbc3f4ea2a4baa8b33756195f
+# bbbbeeb75efc49bbb12e571702c69490
+#: ../../hypervisor/kvm.rst:400 ../../hypervisor/kvm.rst:618
+msgid ""
+"In order to forward traffic to your instances you will need at least two "
+"bridges: *public* and *private*."
+msgstr "为了转发流量到实例，至少需要两个桥接网络： *public* 和 *private*。"
+
+# 3bcaf96162614d5a990b65c272e2627f
+# 70d93337f9884c43b723d19f188000c6
+#: ../../hypervisor/kvm.rst:403 ../../hypervisor/kvm.rst:621
+msgid ""
+"By default these bridges are called *cloudbr0* and *cloudbr1*, but you do "
+"have to make sure they are available on each hypervisor."
+msgstr " 默认情况下，这些桥接被称为*cloudbr0*和*cloudbr1*，但必须确保他们在每个hypervisor上都是可用的。"
+
+# 965691e1a7d742b4a8c0360d6c31e2f6
+# d4d5af0a56be4b0093be521d30e2f4c2
+#: ../../hypervisor/kvm.rst:406 ../../hypervisor/kvm.rst:624
+msgid ""
+"The most important factor is that you keep the configuration consistent on "
+"all your hypervisors."
+msgstr "最重要的因素是所有hypervisors上的配置要保持一致。"
+
+# 8457ada239b24dc388b653310867751e
+# 9e68314d8d8e4f319f85e5d12ec665dc
+#: ../../hypervisor/kvm.rst:411 ../../hypervisor/kvm.rst:643
+msgid "Network example"
+msgstr "网络示例"
+
+# 4de6b0928811452f9123e93380d47402
+# 49e2abb08c79429e8e2a48cb9f02907d
+#: ../../hypervisor/kvm.rst:413 ../../hypervisor/kvm.rst:645
+msgid ""
+"There are many ways to configure your network. In the Basic networking mode "
+"you should have two (V)LAN's, one for your private network and one for the "
+"public network."
+msgstr "配置网络有很多方法。在基本网络模式中你应该拥有2个 (V)LAN，一个用于管理网络，一个用于公共网络。"
+
+# 39d4d3c7755c40b5aea4cebdad65af1b
+# c6f350d0cfec4016ac48462e94a09728
+#: ../../hypervisor/kvm.rst:417 ../../hypervisor/kvm.rst:649
+msgid ""
+"We assume that the hypervisor has one NIC (eth0) with three tagged VLAN's:"
+msgstr "假设hypervisor中的网卡(eth0)有3个VLAN标签："
+
+# e682c9d170fd475da9c2a680bb5099ff
+# d38b80c792834c7c8649626ad41e9300
+#: ../../hypervisor/kvm.rst:420 ../../hypervisor/kvm.rst:652
+msgid "VLAN 100 for management of the hypervisor"
+msgstr "VLAN 100 作为hypervisor的管理网络"
+
+# d25eda691ed1435c880ed6c76b1fef81
+# 1022b2a4fd5848dda685cfe71fd18690
+#: ../../hypervisor/kvm.rst:422 ../../hypervisor/kvm.rst:654
+msgid "VLAN 200 for public network of the instances (cloudbr0)"
+msgstr " VLAN 200 作为实例的公共网络 (cloudbr0)"
+
+# e0eff3d36bba429288abf8657deeb28e
+# f3b7f72de0094b6e9210605736fa23c8
+#: ../../hypervisor/kvm.rst:424 ../../hypervisor/kvm.rst:656
+msgid "VLAN 300 for private network of the instances (cloudbr1)"
+msgstr "VLAN 300 作为实例的专用网络 (cloudbr1)"
+
+# 514a4f72f28c4c58baeea8b592b75c8e
+# 970bdad2851e4d399cdecca76cbbc302
+#: ../../hypervisor/kvm.rst:426 ../../hypervisor/kvm.rst:658
+msgid ""
+"On VLAN 100 we give the Hypervisor the IP-Address 192.168.42.11/24 with the "
+"gateway 192.168.42.1"
+msgstr "在VLAN 100 中，配置Hypervisor的IP为 192.168.42.11/24，网关为192.168.42.1"
+
+# 79adcf25d3a54f778ec9459d0384cb62
+# a686fb2b0fd345d2905f28066f0e0638
+#: ../../hypervisor/kvm.rst:430 ../../hypervisor/kvm.rst:662
+msgid ""
+"The Hypervisor and Management server don't have to be in the same subnet!"
+msgstr "Hypervisor与管理服务器不需要在同一个子网！"
+
+# 83141e4d1ee040d3b63247777f709a6d
+# 5ded57bbb4074546af86d97ade2a6269
+#: ../../hypervisor/kvm.rst:434 ../../hypervisor/kvm.rst:666
+msgid "Configuring the network bridges"
+msgstr "配置网络桥接"
+
+# 660eb10d8f0c4ed399ee7571538e7b6e
+#: ../../hypervisor/kvm.rst:436
+msgid ""
+"It depends on the distribution you are using how to configure these, below "
+"you'll find examples for RHEL/CentOS and Ubuntu."
+msgstr "配置方式取决于发行版类型，下面给出RHEL/CentOS和Ubuntu的配置示例。"
+
+# 89c3fb6c97034c75836101354c78230f
+#: ../../hypervisor/kvm.rst:440
+msgid ""
+"The goal is to have two bridges called 'cloudbr0' and 'cloudbr1' after this "
+"section. This should be used as a guideline only. The exact configuration "
+"will depend on your network layout."
+msgstr "本章节的目标是配置两个名为 'cloudbr0'和'cloudbr1'的桥接网络。这仅仅是指导性的，实际情况还要取决于你的网络布局。"
+
+# 77ee68f2056d43219edea55da8fa4914
+# be99a34a26fd4b958c9fd807e0dd34af
+#: ../../hypervisor/kvm.rst:446 ../../hypervisor/kvm.rst:698
+msgid "Configure in RHEL or CentOS"
+msgstr "在RHEL或CentOS中配置："
+
+# 300927ecc5b44fc88b3d0354324b833a
+#: ../../hypervisor/kvm.rst:448
+msgid ""
+"The required packages were installed when libvirt was installed, we can "
+"proceed to configuring the network."
+msgstr "网络桥接所需的软件在安装libvirt时就已被安装，继续配置网络。"
+
+# 0979f7549d3d40109f7541534976337c
+# c06eae41831f473c95f89897f4086011
+#: ../../hypervisor/kvm.rst:451 ../../hypervisor/kvm.rst:703
+msgid "First we configure eth0"
+msgstr "首先配置eth0："
+
+# 36f103232df444d4851ddb29018cf8e7
+# 9cc8329e54ac46d4844dba0b2f07de57
+#: ../../hypervisor/kvm.rst:457 ../../hypervisor/kvm.rst:709
+msgid "Make sure it looks similar to:"
+msgstr "确保内容如下所示："
+
+# 0a69c047e9904d2fa4430ed750a2a62d
+#: ../../hypervisor/kvm.rst:468
+msgid "We now have to configure the three VLAN interfaces:"
+msgstr "现在配置3个VLAN接口："
+
+# 121e20a6f2bf43c8b4cb4b59090ad9d5
+#: ../../hypervisor/kvm.rst:517
+msgid ""
+"Now we have the VLAN interfaces configured we can add the bridges on top of "
+"them."
+msgstr "配置VLAN接口以便能够附加桥接网络。"
+
+# 3199cc44a9af4582a29269e946521a03
+#: ../../hypervisor/kvm.rst:524
+msgid "Now we just configure it is a plain bridge without an IP-Address"
+msgstr "现在只配置一个没有IP的桥接。"
+
+# 981070114a5a4114bd174bbab7b8879d
+#: ../../hypervisor/kvm.rst:537
+msgid "We do the same for cloudbr1"
+msgstr "同样建立cloudbr1"
+
+# 9627142b8e984eed84e51f657f8c8241
+# 681bc847b70f47e3ad4630bda2af753a
+# 520007e753694508964c00ca3c481d61
+#: ../../hypervisor/kvm.rst:554 ../../hypervisor/kvm.rst:604
+#: ../../hypervisor/kvm.rst:779
+msgid ""
+"With this configuration you should be able to restart the network, although "
+"a reboot is recommended to see if everything works properly."
+msgstr "配置完成之后重启网络，通过重启检查一切是否正常。"
+
+# 2448b2982d304a79862fe2914c61de64
+# ad16f054466d48dd871757fa669c4df4
+# fa84321526ca43df86de9ecd44cf9461
+#: ../../hypervisor/kvm.rst:558 ../../hypervisor/kvm.rst:608
+#: ../../hypervisor/kvm.rst:783
+msgid ""
+"Make sure you have an alternative way like IPMI or ILO to reach the machine "
+"in case you made a configuration error and the network stops functioning!"
+msgstr "在发生配置错误和网络故障的时，请确保可以能通过其他方式例如IPMI或ILO连接到服务器。"
+
+# fe3ac0a755274b3a9dddb7d07949ede0
+#: ../../hypervisor/kvm.rst:563
+msgid "Configure in Ubuntu"
+msgstr "在Ubuntu中配置："
+
+# b098a8a9d90247ab9111fbca07e65fa0
+#: ../../hypervisor/kvm.rst:565
+msgid ""
+"All the required packages were installed when you installed libvirt, so we "
+"only have to configure the network."
+msgstr "在安装libvirt时所需的其他软件也会被安装，所以只需配置网络即可。"
+
+# 81e2e66c3d79430dbadab3f14cd7d21f
+#: ../../hypervisor/kvm.rst:572
+msgid "Modify the interfaces file to look like this:"
+msgstr "如下所示修改接口文件："
+
+# 48b97fd377be47ce94716c2a129def60
+#: ../../hypervisor/kvm.rst:613
+msgid "Configure the network using OpenVswitch"
+msgstr "配置使用OpenVswitch网络"
+
+# f755f1c1367b4e49a1a3ea5b0052c263
+#: ../../hypervisor/kvm.rst:629
+msgid "Preparing"
+msgstr "准备"
+
+# 1cd9101e47b3400c8e51f0979708da0d
+#: ../../hypervisor/kvm.rst:631
+msgid ""
+"To make sure that the native bridge module will not interfere with "
+"openvswitch the bridge module should be added to the blacklist. See the "
+"modprobe documentation for your distribution on where to find the blacklist."
+" Make sure the module is not loaded either by rebooting or executing rmmod "
+"bridge before executing next steps."
+msgstr "将系统自带的网络桥接模块加入黑名单，确保该模块不会与openvswitch模块冲突。请参阅你所使用发行版的modprobe文档并找到黑名单。确保该模块不会在重启时自动加载或在下一操作步骤之前卸载该桥接模块。"
+
+# 50c9cb6dd4434f198ed2252ec1caa0e4
+#: ../../hypervisor/kvm.rst:637
+msgid ""
+"The network configurations below depend on the ifup-ovs and ifdown-ovs "
+"scripts which are part of the openvswitch installation. They should be "
+"installed in /etc/sysconfig/network-scripts/"
+msgstr "以下网络配置依赖ifup-ovs和ifdown-ovs脚本，安装openvswitch后会提供该脚本。安装路径为位/etc/sysconfig/network-scripts/。"
+
+# 68030dc6b78845d59b796851b9829bdf
+#: ../../hypervisor/kvm.rst:668
+msgid ""
+"It depends on the distribution you are using how to configure these, below "
+"you'll find examples for RHEL/CentOS."
+msgstr "如何配置这些文件取决于你使用的发行版本，在下面的内容中会提供RHEL/CentOS下的示例。"
+
+# dfc1c63e9eee4272b51c488615bafe37
+#: ../../hypervisor/kvm.rst:672
+msgid ""
+"The goal is to have three bridges called 'mgmt0', 'cloudbr0' and 'cloudbr1' "
+"after this section. This should be used as a guideline only. The exact "
+"configuration will depend on your network layout."
+msgstr "本章节的目标是设置三个名为'mgmt0', 'cloudbr0'和'cloudbr1' 桥接网络。这仅仅是指导性的，实际情况还要取决于你的网络状况。"
+
+# c26ca789face40d2a6f9e4779a9d5f95
+#: ../../hypervisor/kvm.rst:678
+msgid "Configure OpenVswitch"
+msgstr "配置OpenVswitch"
+
+# 9c03a4fe0070433f867cd736e4f3c8fc
+#: ../../hypervisor/kvm.rst:680
+msgid ""
+"The network interfaces using OpenVswitch are created using the ovs-vsctl "
+"command. This command will configure the interfaces and persist them to the "
+"OpenVswitch database."
+msgstr "使用ovs-vsctl命令创建基于OpenVswitch的网络接口。该命令将配置此接口并将信息保存在OpenVswitch数据库中。"
+
+# cdfe3c8fcb434b6783bc0d370d417746
+#: ../../hypervisor/kvm.rst:684
+msgid ""
+"First we create a main bridge connected to the eth0 interface. Next we "
+"create three fake bridges, each connected to a specific vlan tag."
+msgstr "首先我们创建一个连接至eth0接口的主桥接。然后我们创建三个虚拟桥接，每个桥接都连接指定的VLAN。"
+
+# 880d846a8d5b4184a46ae53df77519c2
+#: ../../hypervisor/kvm.rst:700
+msgid ""
+"The required packages were installed when openvswitch and libvirt were "
+"installed, we can proceed to configuring the network."
+msgstr "所需的安装包在安装openvswitch和libvirt的时就已经安装，继续配置网络。"
+
+# 1962691daa974f51baaafc174a030561
+#: ../../hypervisor/kvm.rst:720
+msgid "We have to configure the base bridge with the trunk."
+msgstr "必须将基础桥接配置为trunk模式。"
+
+# ff14886892454831bf1869e2433a3d04
+#: ../../hypervisor/kvm.rst:735
+msgid "We now have to configure the three VLAN bridges:"
+msgstr "现在对三个VLAN桥接进行配置："
+
+# c9890b410c3340338a04badf11f3ef7f
+#: ../../hypervisor/kvm.rst:788
+msgid "Configuring the firewall"
+msgstr "配置防火墙"
+
+# 10dd274736004147a298a91ec2274c1b
+#: ../../hypervisor/kvm.rst:790
+msgid ""
+"The hypervisor needs to be able to communicate with other hypervisors and "
+"the management server needs to be able to reach the hypervisor."
+msgstr "hypervisor之间和hypervisor与管理服务器之间要能够通讯。"
+
+# 7b384a27e3f042949ce580b2ac4cbe02
+#: ../../hypervisor/kvm.rst:793
+msgid ""
+"In order to do so we have to open the following TCP ports (if you are using "
+"a firewall):"
+msgstr "为了达到这个目的，我们需要开通以下TCP端口(如果使用防火墙)："
+
+# ae053a79c1ef4aa98ebbfa9979dd1dbe
+#: ../../hypervisor/kvm.rst:796
+msgid "22 (SSH)"
+msgstr "22 (SSH)"
+
+# 68c5bface9c34c46bccfa6f10934745a
+#: ../../hypervisor/kvm.rst:798
+msgid "1798"
+msgstr "1798"
+
+# caf73c191ae44a9694814826ff704533
+#: ../../hypervisor/kvm.rst:800
+msgid "16509 (libvirt)"
+msgstr "16509 (libvirt)"
+
+# b41b07df7a30461099d417c16b50b745
+#: ../../hypervisor/kvm.rst:802
+msgid "5900 - 6100 (VNC consoles)"
+msgstr "5900 - 6100 (VNC 控制台)"
+
+# 443df083cb0e49a7a098b6903196471d
+#: ../../hypervisor/kvm.rst:804
+msgid "49152 - 49216 (libvirt live migration)"
+msgstr "49152 - 49216 (libvirt在线迁移)"
+
+# 087989f68dae411cb79ce11da6c9408d
+#: ../../hypervisor/kvm.rst:806
+msgid ""
+"It depends on the firewall you are using how to open these ports. Below "
+"you'll find examples how to open these ports in RHEL/CentOS and Ubuntu."
+msgstr "如何打开这些端口取决于你使用的发行版本。在RHEL/CentOS 及Ubuntu中的示例如下。"
+
+# 2c327652a9ad4b51b8da0b683a481c88
+#: ../../hypervisor/kvm.rst:811
+msgid "Open ports in RHEL/CentOS"
+msgstr "在RHEL/CentOS中打开端口"
+
+# 2c67238eeb0c4181b34a32c059cb47cc
+#: ../../hypervisor/kvm.rst:813
+msgid ""
+"RHEL and CentOS use iptables for firewalling the system, you can open extra "
+"ports by executing the following iptable commands:"
+msgstr "RHEL 及 CentOS使用iptables作为防火墙，执行以下iptables命令来开启端口："
+
+# f47cb1aac5b0422ea1409fd01b64e2db
+#: ../../hypervisor/kvm.rst:836
+msgid ""
+"These iptable settings are not persistent accross reboots, we have to save "
+"them first."
+msgstr "这些iptables配置并不会持久保存，重启之后将会消失，我们必须手动保存这些配置。"
+
+# 8da3ddd17dd24cb8a254b0000f2b336b
+#: ../../hypervisor/kvm.rst:845
+msgid "Open ports in Ubuntu"
+msgstr "在Ubuntu中打开端口："
+
+# f59b31a8288b46c8b52ee009069cb2e3
+#: ../../hypervisor/kvm.rst:847
+msgid ""
+"The default firewall under Ubuntu is UFW (Uncomplicated FireWall), which is "
+"a Python wrapper around iptables."
+msgstr "Ubuntu中的默认防火墙是UFW(Uncomplicated FireWall)，使用Python围绕iptables进行包装。"
+
+# eec901cef5c246699d66ddd141a20525
+#: ../../hypervisor/kvm.rst:850
+msgid "To open the required ports, execute the following commands:"
+msgstr "要打开所需端口，请执行以下命令："
+
+# 1e32d61867d64456a033a80cfee8590c
+#: ../../hypervisor/kvm.rst:873
+msgid ""
+"By default UFW is not enabled on Ubuntu. Executing these commands with the "
+"firewall disabled does not enable the firewall."
+msgstr "默认情况下，Ubuntu中并未启用UFW。在关闭情况下执行这些命令并不能启用防火墙。"
+
+# c72a2dc53e534e2d895ad8057ea4275e
+#: ../../hypervisor/kvm.rst:878
+msgid "Add the host to CloudStack"
+msgstr "添加主机到CloudStack"
+
+# fcd5e62f095c42fba18d4cbe3326670c
+#: ../../hypervisor/kvm.rst:887
+msgid "Hypervisor Support for Primary Storage"
+msgstr "Hypervisor对主存储的支持"
+
+# 9439e0974f4043eeae2c168c73f556f9
+#: ../../hypervisor/kvm.rst:889
+msgid ""
+"The following table shows storage options and parameters for different "
+"hypervisors."
+msgstr "下表显示了针对不同Hypervisors的存储选项和参数。"
+
+# 55db4812fcd04f2087654f0e21be25e7
+#: ../../hypervisor/kvm.rst:893
+msgid "Primary Storage Type"
+msgstr "主存储类型"
+
+# 6c7ef9363a364e16a04e878d23b376cd
+#: ../../hypervisor/kvm.rst:893
+msgid "vSphere"
+msgstr "vSphere"
+
+# 15bb927dd6e5452baba08ee6cd4f6fc6
+#: ../../hypervisor/kvm.rst:893
+msgid "XenServer"
+msgstr "XenServer"
+
+# b37df2a6784a4006a3e30f6ba3a152e7
+#: ../../hypervisor/kvm.rst:893
+msgid "KVM"
+msgstr "KVM"
+
+# fb1d3866f13b4aa19aacc4f30c8109a8
+#: ../../hypervisor/kvm.rst:893
+msgid "Hyper-V"
+msgstr "Hyper-V"
+
+# c16b38c01e4c483db9a695a6632b0efc
+#: ../../hypervisor/kvm.rst:895
+msgid "****Format for Disks, Templates, and Snapshots****"
+msgstr "****磁盘、模板和快照的格式****"
+
+# de345eec1a6642c1891986bf02de6ba0
+#: ../../hypervisor/kvm.rst:895
+msgid "VMDK"
+msgstr "VMDK"
+
+# b2a6d313cb904d3694a2f0b3725a5abe
+# 10092f74d840420da35b6fd6ad62897c
+#: ../../hypervisor/kvm.rst:895 ../../hypervisor/kvm.rst:895
+msgid "VHD"
+msgstr "VHD"
+
+# 68973e57f36742069e1944c60a5e9d2b
+#: ../../hypervisor/kvm.rst:895
+msgid "QCOW2"
+msgstr "QCOW2"
+
+# 2c4cf6dfb59e4089b98a864d2eed2072
+#: ../../hypervisor/kvm.rst:896
+msgid "**iSCSI support**"
+msgstr "**支持iSCSI**"
+
+# 83856e4273e1423fab6ce9e0d1ef763d
+# eff62e1ba15c4299aa34e91768fe41df
+#: ../../hypervisor/kvm.rst:896 ../../hypervisor/kvm.rst:897
+msgid "VMFS"
+msgstr "VMFS"
+
+# b5f17ceae06e4b3287087f1dd7e66447
+#: ../../hypervisor/kvm.rst:896
+msgid "CLVM"
+msgstr "CLVM"
+
+# 6fbeac22a7e4426f8288199c5562c19f
+# 06d3800e38854ad1a4c7e5ab1524a5cc
+#: ../../hypervisor/kvm.rst:896 ../../hypervisor/kvm.rst:897
+msgid "Yes, via Shared Mountpoint"
+msgstr "支持，通过Shared Mountpoint"
+
+# af2d92292dc74c1abe3e5be57d4de4de
+# 17923230b7c44ceea8772df6b93a60c7
+# 66d3a2da649747e69d76e2660f83db68
+# 840ad9a22ad645e9aaff9e7fa55d9a5c
+# 64c610239b92429d9192534e52fa9e22
+# 4f751bb0b08e4ef997175c7226f79375
+# aaf3b18e181144bc8aa036fc05b1026e
+#: ../../hypervisor/kvm.rst:896 ../../hypervisor/kvm.rst:897
+#: ../../hypervisor/kvm.rst:898 ../../hypervisor/kvm.rst:900
+#: ../../hypervisor/kvm.rst:901 ../../hypervisor/kvm.rst:901
+#: ../../hypervisor/kvm.rst:901
+msgid "No"
+msgstr "否"
+
+# 8cf40c3629c54e4dadbda79cd412ea32
+#: ../../hypervisor/kvm.rst:897
+msgid "**Fiber Channel support**"
+msgstr "**支持FC**"
+
+# 0b5e9c2691d7495db0a1b19153a02377
+#: ../../hypervisor/kvm.rst:897
+msgid "Yes, via Existing SR"
+msgstr "支持，通过已有的SR"
+
+# adc9d9dd71c14470a95c7d08135de0dd
+#: ../../hypervisor/kvm.rst:898
+msgid "**NFS support**"
+msgstr "**支持NFS**"
+
+# ae13c4f842284dab8d25f1f2ef0464d4
+# 2bb33766eba942379a1bd7a229f0c9d3
+# bf75790d687b41a9a2fcc365c05b9b3b
+# 496e32a0a3b2457296ae8edde8e193cf
+# 786d4d9a9c87491999c0d890e5644480
+# bbb64e36851e4f408eece5ed45631e18
+# e7e50588bdea47c3b818586bb0794eec
+# 650dd8bed795460cacca69919ed9d8a3
+#: ../../hypervisor/kvm.rst:898 ../../hypervisor/kvm.rst:898
+#: ../../hypervisor/kvm.rst:898 ../../hypervisor/kvm.rst:899
+#: ../../hypervisor/kvm.rst:899 ../../hypervisor/kvm.rst:899
+#: ../../hypervisor/kvm.rst:899 ../../hypervisor/kvm.rst:901
+msgid "Yes"
+msgstr "是"
+
+# f601b6265f2e49d580e7e0f6c2207938
+#: ../../hypervisor/kvm.rst:899
+msgid "**Local storage support**"
+msgstr "**支持本地存储**"
+
+# a448b2c9463248a5bbf0e8b12899dafd
+#: ../../hypervisor/kvm.rst:900
+msgid "**Storage over-provisioning**"
+msgstr "**存储超配**"
+
+# 5fa8702121894c74a47d11039d9067d9
+#: ../../hypervisor/kvm.rst:900
+msgid "NFS and iSCSI"
+msgstr "NFS 和 iSCSI"
+
+# a8c25f4b466d4e5490d53e22ff3fa4f9
+# 984909a8061340f4a6cd15e77e58780b
+#: ../../hypervisor/kvm.rst:900 ../../hypervisor/kvm.rst:900
+msgid "NFS"
+msgstr "NFS"
+
+# 60e22f5e001a46b6950958a9b77c066b
+#: ../../hypervisor/kvm.rst:901
+msgid "**SMB/CIFS**"
+msgstr "**SMB/CIFS**"
+
+# 1512c02954e2429784f5187cc45a1208
+#: ../../hypervisor/kvm.rst:904
+msgid ""
+"XenServer uses a clustered LVM system to store VM images on iSCSI and Fiber "
+"Channel volumes and does not support over-provisioning in the hypervisor. "
+"The storage server itself, however, can support thin-provisioning. As a "
+"result the CloudStack can still support storage over-provisioning by running"
+" on thin-provisioned storage volumes."
+msgstr "XenServer通过在iSCSI和FC卷上使用集群化的LVM系统来存储VM镜像，并且不支持存储超配。尽管存储本身支持自动精简配置。不过CloudStack仍然支持在有自动精简配置的存储卷上使用存储超配。"
+
+# 50dbdfaeac8b4368ab25d9c54267ae1d
+#: ../../hypervisor/kvm.rst:910
+msgid ""
+"KVM supports \"Shared Mountpoint\" storage. A shared mountpoint is a file "
+"system path local to each server in a given cluster. The path must be the "
+"same across all Hosts in the cluster, for example /mnt/primary1. This shared"
+" mountpoint is assumed to be a clustered filesystem such as OCFS2. In this "
+"case the CloudStack does not attempt to mount or unmount the storage as is "
+"done with NFS. The CloudStack requires that the administrator insure that "
+"the storage is available"
+msgstr "KVM支持 \"Shared Mountpoint\"存储。Shared Mountpoint是群集中每个服务器本地文件系统中的一个路径。群集所有主机中的该路径必须一致，比如/mnt/primary1。并假设Shared Mountpoint是一个集群文件系统如OCFS2。在这种情况下，CloudStack不会把它当做NFS存储去尝试挂载或卸载。CloudStack需要管理员确保该存储是可用的。"
+
+# 3fa95266f86e48d39c7f54a98632534a
+#: ../../hypervisor/kvm.rst:918
+msgid ""
+"With NFS storage, CloudStack manages the overprovisioning. In this case the "
+"global configuration parameter storage.overprovisioning.factor controls the "
+"degree of overprovisioning. This is independent of hypervisor type."
+msgstr "在NFS存储中，CloudStack管理超配。这种情况下，使用全局配置参数storage.overprovisioning.factor来控制超配的范围。且不受hyperviso类型约束。"
+
+# d2a34f2d9f4d46759111d884ef353dbf
+#: ../../hypervisor/kvm.rst:923
+msgid ""
+"Local storage is an option for primary storage for vSphere, XenServer, and "
+"KVM. When the local disk option is enabled, a local disk storage pool is "
+"automatically created on each host. To use local storage for the System "
+"Virtual Machines (such as the Virtual Router), set "
+"system.vm.use.local.storage to true in global configuration."
+msgstr "在vSphere, XenServer和KVM中，本地存储是一个可选项。当选择了使用本地存储，所有主机会自动创建本地存储池。想要系统虚拟机 (例如虚拟路由器)使用本地存储，请设置全局配置参数system.vm.use.local.storage为true."
+
+# 5422f4222d5a454babfb7eb7e81822e4
+#: ../../hypervisor/kvm.rst:929
+msgid ""
+"CloudStack supports multiple primary storage pools in a Cluster. For "
+"example, you could provision 2 NFS servers in primary storage. Or you could "
+"provision 1 iSCSI LUN initially and then add a second iSCSI LUN when the "
+"first approaches capacity."
+msgstr "CloudStack支持在一个群集内有多个主存储池。比如，使用2个NFS服务器提供主存储。或原有的1个iSCSI LUN达到一定容量时再添加第二个iSCSI LUN。"
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/lxc.mo b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/lxc.mo
new file mode 100644
index 0000000..58b2f8b
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/lxc.mo
Binary files differ
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/lxc.po b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/lxc.po
new file mode 100644
index 0000000..91acbd2
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/lxc.po
@@ -0,0 +1,726 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: 2014-06-30 10:26+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 43451b40e15f4f98aff4d4219ca70733
+#: ../../hypervisor/lxc.rst:18
+msgid "LXC Installation and Configuration"
+msgstr "LXC安装和配置"
+
+# 93d6379819944090af5901bb1c1c0d79
+#: ../../hypervisor/lxc.rst:21
+msgid "System Requirements for LXC Hosts"
+msgstr "LXC主机的系统要求"
+
+# bb261276bb104960bb09b70bc7e46061
+#: ../../hypervisor/lxc.rst:23
+msgid ""
+"LXC requires the Linux kernel cgroups functionality which is available "
+"starting 2.6.24. Although you are not required to run these distributions, "
+"the following are recommended:"
+msgstr "LXC要求Linux kernel 2.6.24开始引入的 cgroups功能。尽管不需要运行所有的发行版，但是建议下列的版本："
+
+# d68380379bdd49a1891a93478283a52c
+#: ../../hypervisor/lxc.rst:27
+msgid "CentOS / RHEL: 6.3"
+msgstr "CentOS / RHEL: 6.3"
+
+# d13b3427477849a8882c7a2be2c75654
+#: ../../hypervisor/lxc.rst:29
+msgid "Ubuntu: 12.04(.1)"
+msgstr "Ubuntu: 12.04(.1)"
+
+# e29f5b26524649c9b046398ff037ce23
+#: ../../hypervisor/lxc.rst:31
+msgid ""
+"The main requirement for LXC hypervisors is the libvirt and Qemu version. No"
+" matter what Linux distribution you are using, make sure the following "
+"requirements are met:"
+msgstr "LXC hypervisor 要求libvirt和Qemu的版本。无论使用哪种Linux发行版，请确保满足以下要求："
+
+# 94b1feafb27b4459bed9dd9a2a052c0f
+# baeb40fab6b14df39610ec212fe63108
+#: ../../hypervisor/lxc.rst:35 ../../hypervisor/lxc.rst:43
+msgid "libvirt: 1.0.0 or higher"
+msgstr "libvirt: 1.0.0或更高"
+
+# cad5b5564070411fb6182cd0ad878821
+#: ../../hypervisor/lxc.rst:37
+msgid "Qemu/KVM: 1.0 or higher"
+msgstr "Qemu/KVM: 1.0 或更高版本"
+
+# 14a04946a13a4d7b967c651ed282a8a1
+#: ../../hypervisor/lxc.rst:39
+msgid ""
+"The default bridge in CloudStack is the Linux native bridge implementation "
+"(bridge module). CloudStack includes an option to work with OpenVswitch, the"
+" requirements are listed below"
+msgstr "CloudStack中的默认使用Linux本身的桥接(bridge模块)方式实现。也可选择在CloudStack中使用OpenVswitch，具体要求如下："
+
+# 50b69be40a954cff921f60a6a771059b
+#: ../../hypervisor/lxc.rst:45
+msgid "openvswitch: 1.7.1 or higher"
+msgstr "openvswitch: 1.7.1或更高版本"
+
+# a1ade5134faf4baf99ac999ab1f26788
+#: ../../hypervisor/lxc.rst:47
+msgid "In addition, the following hardware requirements apply:"
+msgstr "此外，硬件要求如下："
+
+# d15ebc2eead24a9fb2b115ac5127ac1a
+#: ../../hypervisor/lxc.rst:49
+msgid ""
+"Within a single cluster, the hosts must be of the same distribution version."
+msgstr "同一集群中主机必须使用相同版本的Linux系统。"
+
+# 9a162b24f7fd499c9793ac22d8cd360f
+#: ../../hypervisor/lxc.rst:52
+msgid ""
+"All hosts within a cluster must be homogenous. The CPUs must be of the same "
+"type, count, and feature flags."
+msgstr "同一群集中的所有节点架构必须一致。CPU的型号、数量和功能参数必须相同。"
+
+# cd66e1991f8b4d80b5267dda55cec2a8
+#: ../../hypervisor/lxc.rst:55
+msgid "Must support HVM (Intel-VT or AMD-V enabled)"
+msgstr "必须支持HVM(Intel-VT或者AMD-V)"
+
+# 717b8bb8d1a742d3a0abef21e3f17b90
+#: ../../hypervisor/lxc.rst:57
+msgid "64-bit x86 CPU (more cores results in better performance)"
+msgstr "64位x86 CPU(多核性能更佳)"
+
+# 348214c7e23d48889b3b01488710391f
+#: ../../hypervisor/lxc.rst:59
+msgid "4 GB of memory"
+msgstr "4GB 内存"
+
+# 4443612c88374256a08ca5fe5b53af70
+#: ../../hypervisor/lxc.rst:61
+msgid "At least 1 NIC"
+msgstr "至少一块网卡"
+
+# 1e16cfc2f05e4c219030609a9486327f
+#: ../../hypervisor/lxc.rst:63
+msgid ""
+"When you deploy CloudStack, the hypervisor host must not have any VMs "
+"already running"
+msgstr "在部署CloudStack时，Hypervisor主机不能运行任何虚拟机"
+
+# 5c575160ed0446838d1cdebcd70cc5b1
+#: ../../hypervisor/lxc.rst:68
+msgid "LXC Installation Overview"
+msgstr "LXC安装概述"
+
+# f252d45b9213468d9646dc4f539523fa
+#: ../../hypervisor/lxc.rst:70
+msgid ""
+"LXC does not have any native system VMs, instead KVM will be used to run "
+"system VMs. This means that your host will need to support both LXC and KVM,"
+" thus most of the installation and configuration will be identical to the "
+"KVM installation. The material in this section doesn't duplicate KVM "
+"installation docs. It provides the CloudStack-specific steps that are needed"
+" to prepare a KVM host to work with CloudStack."
+msgstr "LXC没有任何本地系统VMs，而KVM需要运行系统VMs。意思为主机需要同时支持LXC和KVM。因此，大部分的安装和配置跟KVM的安装一样。本章节不会复述KVM的安装。这里我们只会给出使KVM与CloudStack协同工作的一些特有的步骤。"
+
+# 99cca852be7249bd8ea16dc52a8b405e
+#: ../../hypervisor/lxc.rst:78
+msgid ""
+"Before continuing, make sure that you have applied the latest updates to "
+"your host."
+msgstr "在我们开始之前，请确保所有的主机都安装了最新的更新包。"
+
+# 7a72cc592a1f4a5cb0cacebf3883d960
+#: ../../hypervisor/lxc.rst:82
+msgid ""
+"It is NOT recommended to run services on this host not controlled by "
+"CloudStack."
+msgstr "不建议在主机中运行与CloudStack无关的服务。"
+
+# d6f4000ff3874464bb929b7fb2e49dcc
+#: ../../hypervisor/lxc.rst:85
+msgid "The procedure for installing an LXC Host is:"
+msgstr "安装LXC主机步骤："
+
+# 3957e2eca5b1450fa2cdac31e4c4baa9
+# d3b55c0bf6044446b80d37400ebc93b9
+#: ../../hypervisor/lxc.rst:87 ../../hypervisor/lxc.rst:97
+msgid "Prepare the Operating System"
+msgstr "准备操作系统"
+
+# 055e7a4b9b6f40098143553e04e75142
+#: ../../hypervisor/lxc.rst:89
+msgid "Install and configure libvirt"
+msgstr "安装和配置libvirt"
+
+# 3d012316e0e548a898752588ad9f8ea6
+#: ../../hypervisor/lxc.rst:91
+msgid "Configure Security Policies (AppArmor and SELinux)"
+msgstr "配置安全策略 (AppArmor 和 SELinux)"
+
+# 64413c2cb08e4dc4b057fd257e1e983e
+# 8ef5b6b2388141729517cc4fefd87440
+#: ../../hypervisor/lxc.rst:93 ../../hypervisor/lxc.rst:140
+msgid "Install and configure the Agent"
+msgstr "安装和配置Agent"
+
+# 8466bfaf482d4d6599658d9411867dea
+#: ../../hypervisor/lxc.rst:99
+msgid ""
+"The OS of the Host must be prepared to host the CloudStack Agent and run KVM"
+" instances."
+msgstr "主机的操作系统必须为运行CloudStack Agent和KVM实例做些准备。"
+
+# 75c2b7bef1834d809a1804dc83d2e1fa
+#: ../../hypervisor/lxc.rst:102
+msgid "Log in to your OS as root."
+msgstr "使用root用户登录操作系统。"
+
+# b9dccd7b46514913be1eb8e7b074ac01
+#: ../../hypervisor/lxc.rst:104
+msgid "Check for a fully qualified hostname."
+msgstr "检查FQN完全合格/限定主机名。"
+
+# 95a324234f074b9991a1c506af6239c2
+#: ../../hypervisor/lxc.rst:110
+msgid ""
+"This should return a fully qualified hostname such as "
+"\"kvm1.lab.example.org\". If it does not, edit /etc/hosts so that it does."
+msgstr "该命令会返回完全合格/限定主机名，例如\"kvm1.lab.example.org\"。如果没有，请编辑 /etc/hosts。"
+
+# abcfdb639b3c48e994b3f12ffb1cada1
+#: ../../hypervisor/lxc.rst:114
+msgid "Make sure that the machine can reach the Internet."
+msgstr "确保机器可以连接到互联网."
+
+# de73cc85f6bb44e788c9ea8d31d6a6ad
+#: ../../hypervisor/lxc.rst:120
+msgid "Turn on NTP for time synchronization."
+msgstr "启用NTP服务以确保时间同步."
+
+# 9d75eb82ba9f45178754d7a1b28c6a52
+#: ../../hypervisor/lxc.rst:123
+msgid ""
+"NTP is required to synchronize the clocks of the servers in your cloud. "
+"Unsynchronized clocks can cause unexpected problems."
+msgstr "NTP服务用来同步云中的服务器时间。时间不同步会带来意想不到的问题。"
+
+# 05286054f8844c638f951a6f8fb5b85e
+#: ../../hypervisor/lxc.rst:126
+msgid "Install NTP"
+msgstr "安装NTP"
+
+# bbe6d187091b41178985da38a664feb3
+#: ../../hypervisor/lxc.rst:136
+msgid "Repeat all of these steps on every hypervisor host."
+msgstr "在所有主机中重复上述步骤。"
+
+# 045c7ecca5a246ff9218024c3f3ae129
+#: ../../hypervisor/lxc.rst:142
+msgid ""
+"To manage LXC instances on the host CloudStack uses a Agent. This Agent "
+"communicates with the Management server and controls all the instances on "
+"the host."
+msgstr "CloudStack使用代理管理LXC实例。管理服务器与代理通信并控制主机中所有实例。"
+
+# c201aad8986d46c891235c1b0db5cd06
+#: ../../hypervisor/lxc.rst:146
+msgid "First we start by installing the agent:"
+msgstr "首先我们安装Agent："
+
+# 415c53c92754469eb9cc8121af962ecf
+# fb5081e503f74e6995e63f1dd73d384d
+# 67c12bc85b6c4cd28de0f5dfaf696bf0
+#: ../../hypervisor/lxc.rst:148 ../../hypervisor/lxc.rst:260
+#: ../../hypervisor/lxc.rst:296
+msgid "In RHEL or CentOS:"
+msgstr "在RHEL/CentOS上:"
+
+# d1b500c6b3bb470f8ad07118cc13a0bf
+# 69d3e8a5b14a4d32a55350bfa8b6f12a
+#: ../../hypervisor/lxc.rst:154 ../../hypervisor/lxc.rst:266
+msgid "In Ubuntu:"
+msgstr "在Ubuntu上:"
+
+# 04df1ba82d804c3e93844dbf7cdd829d
+#: ../../hypervisor/lxc.rst:160
+msgid ""
+"Next step is to update the Agent configuration setttings. The settings are "
+"in ``/etc/cloudstack/agent/agent.properties``"
+msgstr "接下来更新代理配置。在 ``/etc/cloudstack/agent/agent.properties`` 中配置"
+
+# 3948b221adf748639788b545bdd0e3a7
+#: ../../hypervisor/lxc.rst:163
+msgid "Set the Agent to run in LXC mode:"
+msgstr "设置代理运行在LXC模式下："
+
+# cb52c2209b544fd8a09751340ec83214
+#: ../../hypervisor/lxc.rst:169
+msgid ""
+"Optional: If you would like to use direct networking (instead of the default"
+" bridge networking), configure these lines:"
+msgstr "可选项：如果想使用直连网络(代替默认的桥接网络)，配置如下行："
+
+# 6d6647d83e8145d28e4220e85924d010
+# c8b990ebe5d445a78252e84e2c4e5652
+#: ../../hypervisor/lxc.rst:184 ../../hypervisor/lxc.rst:667
+msgid ""
+"The host is now ready to be added to a cluster. This is covered in a later "
+"section, see :ref:`adding-a-host`. It is recommended that you continue to "
+"read the documentation before adding the host!"
+msgstr "现在主机已经为加入群集做好准备。后面的章节有介绍，请参阅 :ref:`adding-a-host`。强烈建议在添加主机之前阅读此部分内容。"
+
+# cacd4ea9375c4864a2c9fb041bb4bc7c
+#: ../../hypervisor/lxc.rst:191
+msgid "Install and Configure libvirt"
+msgstr "安装和配置libvirt"
+
+# b0f7e7f7680e490eacb65fb0cb1b98c6
+#: ../../hypervisor/lxc.rst:193
+msgid ""
+"CloudStack uses libvirt for managing virtual machines. Therefore it is vital"
+" that libvirt is configured correctly. Libvirt is a dependency of "
+"cloudstack-agent and should already be installed."
+msgstr "CloudStack使用libvirt管理虚拟机。因此正确地配置libvirt至关重要。CloudStack-agent依赖于Libvirt，应提前安装完毕。"
+
+# f54bd7715b5441f687683613bff00956
+#: ../../hypervisor/lxc.rst:197
+msgid ""
+"In order to have live migration working libvirt has to listen for unsecured "
+"TCP connections. We also need to turn off libvirts attempt to use Multicast "
+"DNS advertising. Both of these settings are in "
+"``/etc/libvirt/libvirtd.conf``"
+msgstr "为了实现动态迁移libvirt需要监听不可靠的TCP连接。还要关闭libvirts尝试使用组播DNS进行广播。这些都可以在 /etc/libvirt/libvirtd.conf文件中进行配置。"
+
+# 7307dff0578a4767a3b5fa1812366060
+#: ../../hypervisor/lxc.rst:202
+msgid "Set the following parameters:"
+msgstr "设定下列参数："
+
+# 15b53ac02e8d44e0aa89579320fcdb63
+#: ../../hypervisor/lxc.rst:224
+msgid ""
+"Turning on \"listen\\_tcp\" in libvirtd.conf is not enough, we have to "
+"change the parameters as well:"
+msgstr "除了在libvirtd.conf中打开\"listen_tcp\"以外，我们还必须修改/etc/sysconfig/libvirtd中的参数:"
+
+# 48d050262fe84becbb7e6c94efc4dfba
+#: ../../hypervisor/lxc.rst:227
+msgid "On RHEL or CentOS modify ``/etc/sysconfig/libvirtd``:"
+msgstr "在RHEL或者CentOS中修改 ``/etc/sysconfig/libvirtd``："
+
+# 76e8b6056dc84935aaf0ca036b0155ee
+#: ../../hypervisor/lxc.rst:229
+msgid "Uncomment the following line:"
+msgstr "取消如下行的注释："
+
+# f3a3573b89414eb4a4d76ebbe98300d9
+#: ../../hypervisor/lxc.rst:235
+msgid "On Ubuntu: modify ``/etc/default/libvirt-bin``"
+msgstr "在Ubuntu中:修改 ``/etc/default/libvirt-bin`` "
+
+# dd99331d08b34cb7acceb95817539208
+#: ../../hypervisor/lxc.rst:237
+msgid "Add \"-l\" to the following line"
+msgstr "在下列行添加 \"-l\""
+
+# 0322d77ee56e454c9351e115b1a8a45d
+#: ../../hypervisor/lxc.rst:243
+msgid "so it looks like:"
+msgstr "如下所示:"
+
+# 6334d52ad51a4fc69fc58128e38f2319
+#: ../../hypervisor/lxc.rst:249
+msgid ""
+"In order to have the VNC Console work we have to make sure it will bind on "
+"0.0.0.0. We do this by editing ``/etc/libvirt/qemu.conf``"
+msgstr "为了VNC控制台正常工作，必须确保该参数绑定在0.0.0.0上。通过编辑 ``/etc/libvirt/qemu.conf``实现。"
+
+# 27259d3d47ab4f929936de05e3d77118
+#: ../../hypervisor/lxc.rst:252
+msgid "Make sure this parameter is set:"
+msgstr "请确保这个参数配置为："
+
+# 314400b666db4e16b3133e7ddb4aa140
+#: ../../hypervisor/lxc.rst:258
+msgid "Restart libvirt"
+msgstr "重启libvirt服务"
+
+# 4d9c0c7846c0455b97268a20ec9eb588
+#: ../../hypervisor/lxc.rst:274
+msgid "Configure the Security Policies"
+msgstr "配置安全策略"
+
+# c9864510ba8d4a5183f23a8c14f94563
+#: ../../hypervisor/lxc.rst:276
+msgid ""
+"CloudStack does various things which can be blocked by security mechanisms "
+"like AppArmor and SELinux. These have to be disabled to ensure the Agent has"
+" all the required permissions."
+msgstr "CloudStack的会被例如AppArmor和SELinux的安全机制阻止。必须关闭安全机制并确保 Agent具有所必需的权限。"
+
+# 19dce9911cb5468e8ecca028cc3629d0
+#: ../../hypervisor/lxc.rst:280
+msgid "Configure SELinux (RHEL and CentOS)"
+msgstr "配置SELinux（RHEL和CentOS）："
+
+# c7bde8f0637b4bc0b30d695a9148ea26
+#: ../../hypervisor/lxc.rst:282
+msgid ""
+"Check to see whether SELinux is installed on your machine. If not, you can "
+"skip this section."
+msgstr "检查你的机器是否安装了SELinux。如果没有，请跳过此部分。"
+
+# 4153e72e86e54e569528229e10430c13
+#: ../../hypervisor/lxc.rst:285
+msgid ""
+"In RHEL or CentOS, SELinux is installed and enabled by default. You can "
+"verify this with:"
+msgstr "在RHEL或者CentOS中，SELinux是默认安装并启动的。你可以使用如下命令验证："
+
+# bcc78a8cd2f343dead2d193b7d56bf2e
+#: ../../hypervisor/lxc.rst:292
+msgid ""
+"Set the SELINUX variable in ``/etc/selinux/config`` to \"permissive\". This "
+"ensures that the permissive setting will be maintained after a system "
+"reboot."
+msgstr "在 ``/etc/selinux/config`` 中设置SELINUX变量值为 \"permissive\"。这样能确保对SELinux的设置在系统重启之后依然生效。"
+
+# 43e21420401741e2997b97701eff333e
+#: ../../hypervisor/lxc.rst:302
+msgid "Change the following line"
+msgstr "查找如下行"
+
+# 90ead7a947fc40daabdafad6a1b988fb
+#: ../../hypervisor/lxc.rst:308
+msgid "to this"
+msgstr "修改为"
+
+# 3040526ce2ff4279bafd31876dd69d4a
+#: ../../hypervisor/lxc.rst:314
+msgid ""
+"Then set SELinux to permissive starting immediately, without requiring a "
+"system reboot."
+msgstr "然后使SELinux立即运行于permissive模式，无需重新启动系统。"
+
+# 52396bdef51d440f9db42978c93847dc
+#: ../../hypervisor/lxc.rst:321
+msgid "Configure Apparmor (Ubuntu)"
+msgstr "配置AppArmor(Ubuntu)"
+
+# 19599a1513614b4f984636e98ee6d2f1
+#: ../../hypervisor/lxc.rst:323
+msgid ""
+"Check to see whether AppArmor is installed on your machine. If not, you can "
+"skip this section."
+msgstr "检查你的机器中是否安装了AppArmor。如果没有，请跳过此部分。"
+
+# 7c0035c7f5ec4b07ba0088564f98754e
+#: ../../hypervisor/lxc.rst:326
+msgid ""
+"In Ubuntu AppArmor is installed and enabled by default. You can verify this "
+"with:"
+msgstr "Ubuntu中默认安装并启动AppArmor。使用如下命令验证："
+
+# 4d576628709d47f38d097a74e45b5aa4
+#: ../../hypervisor/lxc.rst:333
+msgid "Disable the AppArmor profiles for libvirt"
+msgstr "在AppArmor配置文件中禁用libvirt"
+
+# 4182b6b7d26b46b99feff257f01b0b19
+#: ../../hypervisor/lxc.rst:353
+msgid "Configure the network bridges"
+msgstr "配置网络桥接"
+
+# c4f546fe4c1d46b0a68265d339df86ff
+#: ../../hypervisor/lxc.rst:356
+msgid ""
+"This is a very important section, please make sure you read this thoroughly."
+msgstr "本章节非常重要，请务必彻底理解。"
+
+# e0a8dbc6e7e9410fa60dd28738b69792
+#: ../../hypervisor/lxc.rst:359
+msgid ""
+"This section details how to configure bridges using the native "
+"implementation in Linux. Please refer to the next section if you intend to "
+"use OpenVswitch"
+msgstr "本章节详细介绍了如何使用Linux自带的软件配置桥接网络。如果要使用OpenVswitch，请看下一章节。"
+
+# 7dfb485a01f249d39f5527e0c4c36cf9
+#: ../../hypervisor/lxc.rst:363
+msgid ""
+"In order to forward traffic to your instances you will need at least two "
+"bridges: *public* and *private*."
+msgstr "为了转发流量到实例，至少需要两个桥接网络： *public* 和 *private*。"
+
+# 9948a8e0c4ca41c38a570931fd602edc
+#: ../../hypervisor/lxc.rst:366
+msgid ""
+"By default these bridges are called *cloudbr0* and *cloudbr1*, but you do "
+"have to make sure they are available on each hypervisor."
+msgstr " 默认情况下，这些桥接被称为*cloudbr0*和*cloudbr1*，但必须确保他们在每个hypervisor上都是可用的。"
+
+# dcbc1defc34f4793b6b6f08e1434ee90
+#: ../../hypervisor/lxc.rst:369
+msgid ""
+"The most important factor is that you keep the configuration consistent on "
+"all your hypervisors."
+msgstr "最重要的因素是所有hypervisors上的配置要保持一致。"
+
+# bc77d68b01c842caaba9c228953c9c9a
+#: ../../hypervisor/lxc.rst:374
+msgid "Network example"
+msgstr "网络示例"
+
+# d445133ac7514f30b223a361e185bca3
+#: ../../hypervisor/lxc.rst:376
+msgid ""
+"There are many ways to configure your network. In the Basic networking mode "
+"you should have two (V)LAN's, one for your private network and one for the "
+"public network."
+msgstr "配置网络有很多方法。在基本网络模式中你应该拥有2个 (V)LAN，一个用于管理网络，一个用于公共网络。"
+
+# 7fcbe3dbd5e24cc78a454b43046db3dc
+#: ../../hypervisor/lxc.rst:380
+msgid ""
+"We assume that the hypervisor has one NIC (eth0) with three tagged VLAN's:"
+msgstr "假设hypervisor中的网卡(eth0)有3个VLAN标签："
+
+# 79f9905e712d4477ad6f1242de95100a
+#: ../../hypervisor/lxc.rst:383
+msgid "VLAN 100 for management of the hypervisor"
+msgstr "VLAN 100 作为hypervisor的管理网络"
+
+# ae33b27f9bac420195c64c0770a86cd0
+#: ../../hypervisor/lxc.rst:385
+msgid "VLAN 200 for public network of the instances (cloudbr0)"
+msgstr " VLAN 200 作为实例的公共网络 (cloudbr0)"
+
+# fa09f2d8754547ca8140ba9117584838
+#: ../../hypervisor/lxc.rst:387
+msgid "VLAN 300 for private network of the instances (cloudbr1)"
+msgstr "VLAN 300 作为实例的专用网络 (cloudbr1)"
+
+# 6b19d1a474714e77a49083b08d8a70ad
+#: ../../hypervisor/lxc.rst:389
+msgid ""
+"On VLAN 100 we give the Hypervisor the IP-Address 192.168.42.11/24 with the "
+"gateway 192.168.42.1"
+msgstr "在VLAN 100 中，配置Hypervisor的IP为 192.168.42.11/24，网关为192.168.42.1"
+
+# 66e4325554bd44839b00ff46222bb488
+#: ../../hypervisor/lxc.rst:393
+msgid ""
+"The Hypervisor and Management server don't have to be in the same subnet!"
+msgstr "Hypervisor与管理服务器不需要在同一个子网！"
+
+# 0c38727f3c5145db8ac92b2df423f9f3
+#: ../../hypervisor/lxc.rst:396
+msgid "Configuring the network bridges"
+msgstr "配置网络桥接"
+
+# 87f57c9a5f394d4f9d55876ad8bbf7b5
+#: ../../hypervisor/lxc.rst:398
+msgid ""
+"It depends on the distribution you are using how to configure these, below "
+"you'll find examples for RHEL/CentOS and Ubuntu."
+msgstr "配置方式取决于发行版类型，下面给出RHEL/CentOS和Ubuntu的配置示例。"
+
+# 66be5e9df4cc4265a1e9b7b608fe271a
+#: ../../hypervisor/lxc.rst:402
+msgid ""
+"The goal is to have two bridges called 'cloudbr0' and 'cloudbr1' after this "
+"section. This should be used as a guideline only. The exact configuration "
+"will depend on your network layout."
+msgstr "本章节的目标是配置两个名为 'cloudbr0'和'cloudbr1'的桥接网络。这仅仅是指导性的，实际情况还要取决于你的网络布局。"
+
+# 77f72e31b31c4ff48abfeab14d5c4b81
+#: ../../hypervisor/lxc.rst:408
+msgid "Configure in RHEL or CentOS"
+msgstr "在RHEL或CentOS中配置："
+
+# 5cd8006226944c75823d3fc69513965f
+#: ../../hypervisor/lxc.rst:410
+msgid ""
+"The required packages were installed when libvirt was installed, we can "
+"proceed to configuring the network."
+msgstr "网络桥接所需的软件在安装libvirt时就已被安装，继续配置网络。"
+
+# 3c73eb0802d2412eba4716e54ae34079
+#: ../../hypervisor/lxc.rst:413
+msgid "First we configure eth0"
+msgstr "首先配置eth0："
+
+# 19f74e9662c943b2b0d717aa2d8e80bf
+#: ../../hypervisor/lxc.rst:419
+msgid "Make sure it looks similar to:"
+msgstr "确保内容如下所示："
+
+# e751abe2e0124ba9b0f542abd413a2d0
+#: ../../hypervisor/lxc.rst:430
+msgid "We now have to configure the three VLAN interfaces:"
+msgstr "现在配置3个VLAN接口："
+
+# 821a8f3fb92d431e8be2f46a196c35bb
+#: ../../hypervisor/lxc.rst:479
+msgid ""
+"Now we have the VLAN interfaces configured we can add the bridges on top of "
+"them."
+msgstr "配置VLAN接口以便能够附加桥接网络。"
+
+# 755eeca19e1e4bd98aff0dd3a0c00845
+#: ../../hypervisor/lxc.rst:486
+msgid "Now we just configure it is a plain bridge without an IP-Address"
+msgstr "现在只配置一个没有IP的桥接。"
+
+# b04314407fb64b85844b09abb048169b
+#: ../../hypervisor/lxc.rst:499
+msgid "We do the same for cloudbr1"
+msgstr "同样建立cloudbr1"
+
+# ec7d49c23ca9494d9ae4d1fd87a835cb
+# 3495886017224d39aa2c595d960a7ef1
+#: ../../hypervisor/lxc.rst:516 ../../hypervisor/lxc.rst:566
+msgid ""
+"With this configuration you should be able to restart the network, although "
+"a reboot is recommended to see if everything works properly."
+msgstr "配置完成之后重启网络，通过重启检查一切是否正常。"
+
+# 3b0ccd039c8d42b4a0e5d7b35d533763
+# 16b5ca319946407fb1a833f3f566ad4c
+#: ../../hypervisor/lxc.rst:520 ../../hypervisor/lxc.rst:570
+msgid ""
+"Make sure you have an alternative way like IPMI or ILO to reach the machine "
+"in case you made a configuration error and the network stops functioning!"
+msgstr "在发生配置错误和网络故障的时，请确保可以能通过其他方式例如IPMI或ILO连接到服务器。"
+
+# 33fce556fd75408baf0d8f252c1c4aa9
+#: ../../hypervisor/lxc.rst:525
+msgid "Configure in Ubuntu"
+msgstr "在Ubuntu中配置："
+
+# 57356f0b3a6b48878fc6cc570d10d516
+#: ../../hypervisor/lxc.rst:527
+msgid ""
+"All the required packages were installed when you installed libvirt, so we "
+"only have to configure the network."
+msgstr "在安装libvirt时所需的其他软件也会被安装，所以只需配置网络即可。"
+
+# bde1178e96404b77bb9b9c18c923aa2e
+#: ../../hypervisor/lxc.rst:534
+msgid "Modify the interfaces file to look like this:"
+msgstr "如下所示修改接口文件："
+
+# d5065122bf4a4f5c83dedf6baa1c2306
+#: ../../hypervisor/lxc.rst:575
+msgid "Configuring the firewall"
+msgstr "配置防火墙"
+
+# 2749450a561548e3b39d03e1a9af0672
+#: ../../hypervisor/lxc.rst:577
+msgid ""
+"The hypervisor needs to be able to communicate with other hypervisors and "
+"the management server needs to be able to reach the hypervisor."
+msgstr "hypervisor之间和hypervisor与管理服务器之间要能够通讯。"
+
+# c76bea5d16c743f88d76b477d69bf172
+#: ../../hypervisor/lxc.rst:580
+msgid ""
+"In order to do so we have to open the following TCP ports (if you are using "
+"a firewall):"
+msgstr "为了达到这个目的，我们需要开通以下TCP端口(如果使用防火墙)："
+
+# e0a0a271492c47a0b549ec0fa2319108
+#: ../../hypervisor/lxc.rst:583
+msgid "22 (SSH)"
+msgstr "22 (SSH)"
+
+# 0d0046b470a24b35a6bbbb93e416d8ea
+#: ../../hypervisor/lxc.rst:585
+msgid "1798"
+msgstr "1798"
+
+# 9d1fa0fdb4ef48c0ad4b41556ca20e9d
+#: ../../hypervisor/lxc.rst:587
+msgid "16509 (libvirt)"
+msgstr "16509 (libvirt)"
+
+# e5d29bf0b5604b418180606c2d4826e4
+#: ../../hypervisor/lxc.rst:589
+msgid "5900 - 6100 (VNC consoles)"
+msgstr "5900 - 6100 (VNC 控制台)"
+
+# 53bdbd256dd44308a212a48b8de7be9c
+#: ../../hypervisor/lxc.rst:591
+msgid "49152 - 49216 (libvirt live migration)"
+msgstr "49152 - 49216 (libvirt在线迁移)"
+
+# e1b82341b7f14145ae2b1be829bcdf18
+#: ../../hypervisor/lxc.rst:593
+msgid ""
+"It depends on the firewall you are using how to open these ports. Below "
+"you'll find examples how to open these ports in RHEL/CentOS and Ubuntu."
+msgstr "如何打开这些端口取决于你使用的发行版本。在RHEL/CentOS 及Ubuntu中的示例如下。"
+
+# eadaeb9bb6514298924b9fb479ddb280
+#: ../../hypervisor/lxc.rst:598
+msgid "Open ports in RHEL/CentOS"
+msgstr "在RHEL/CentOS中打开端口"
+
+# dbd7938f1a764dfe9159e9eaa1119863
+#: ../../hypervisor/lxc.rst:600
+msgid ""
+"RHEL and CentOS use iptables for firewalling the system, you can open extra "
+"ports by executing the following iptable commands:"
+msgstr "RHEL 及 CentOS使用iptables作为防火墙，执行以下iptables命令来开启端口："
+
+# d20a63121d8d4a90b51c2e5eb1dc1b8e
+#: ../../hypervisor/lxc.rst:623
+msgid ""
+"These iptable settings are not persistent accross reboots, we have to save "
+"them first."
+msgstr "这些iptables配置并不会持久保存，重启之后将会消失，我们必须手动保存这些配置。"
+
+# 43b24147a3aa400f940581bae2f54fb3
+#: ../../hypervisor/lxc.rst:632
+msgid "Open ports in Ubuntu"
+msgstr "在Ubuntu中打开端口："
+
+# dbd52c7373bd40008b953dc3d9b13496
+#: ../../hypervisor/lxc.rst:634
+msgid ""
+"The default firewall under Ubuntu is UFW (Uncomplicated FireWall), which is "
+"a Python wrapper around iptables."
+msgstr "Ubuntu中的默认防火墙是UFW(Uncomplicated FireWall)，使用Python围绕iptables进行包装。"
+
+# 34381e08303c46de9cb9a2ba59cc3026
+#: ../../hypervisor/lxc.rst:637
+msgid "To open the required ports, execute the following commands:"
+msgstr "要打开所需端口，请执行以下命令："
+
+# 36b32007e54b471f951bbd763f7a7d04
+#: ../../hypervisor/lxc.rst:660
+msgid ""
+"By default UFW is not enabled on Ubuntu. Executing these commands with the "
+"firewall disabled does not enable the firewall."
+msgstr "默认情况下，Ubuntu中并未启用UFW。在关闭情况下执行这些命令并不能启用防火墙。"
+
+# 1f96f5667281430689c6573d520ffbbc
+#: ../../hypervisor/lxc.rst:665
+msgid "Add the host to CloudStack"
+msgstr "添加主机到CloudStack"
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/vsphere.mo b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/vsphere.mo
new file mode 100644
index 0000000..04de3ba
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/vsphere.mo
Binary files differ
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/vsphere.po b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/vsphere.po
new file mode 100644
index 0000000..dd7d536
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/vsphere.po
@@ -0,0 +1,2089 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: 2014-06-30 10:27+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 19b014507cf143c0bfc2d6b2fdbeca56
+#: ../../hypervisor/vsphere.rst:18
+msgid "VMware vSphere Installation and Configuration"
+msgstr "VMware vSphere 安装和配置"
+
+# 87c85380b4b94a7393cc229882265b58
+#: ../../hypervisor/vsphere.rst:20
+msgid ""
+"If you want to use the VMware vSphere hypervisor to run guest virtual "
+"machines, install vSphere on the host(s) in your cloud."
+msgstr "如果计划使用VMware vSphere平台运行虚拟机，请在云中安装vSphere主机。"
+
+# 3d2c763f10b74d00ae6672f6d8a6ee22
+#: ../../hypervisor/vsphere.rst:25
+msgid "System Requirements for vSphere Hosts"
+msgstr "vSphere主机的系统要求"
+
+# a69a6b7374d64da3a42115a99aad0d8e
+#: ../../hypervisor/vsphere.rst:29
+msgid "Software requirements:"
+msgstr "软件要求："
+
+# 817453f34d1d4ce7adcd829ee2c4469e
+#: ../../hypervisor/vsphere.rst:31
+msgid "vSphere and vCenter, both version 4.1 or 5.0."
+msgstr "vSphere和vCenter版本，4.1或5.0。"
+
+# 307a9f42a4ba44c4ae53ae2a46440a92
+#: ../../hypervisor/vsphere.rst:33
+msgid ""
+"vSphere Standard is recommended. Note however that customers need to "
+"consider the CPU constraints in place with vSphere licensing. See "
+"`http://www.vmware.com/files/pdf/vsphere\\_pricing.pdf "
+"<http://www.vmware.com/files/pdf/vsphere_pricing.pdf>`_ and discuss with "
+"your VMware sales representative."
+msgstr "建议使用vSphere标准版。但是VMware用户需要考虑vSphere授权对CPU的限制。请参考 `http://www.vmware.com/files/pdf/vsphere\\_pricing.pdf <http://www.vmware.com/files/pdf/vsphere_pricing.pdf>`_ 并与销售代表讨论。"
+
+# 0f24943e5a384c2fb7c8d181a5df1d27
+#: ../../hypervisor/vsphere.rst:39
+msgid "vCenter Server Standard is recommended."
+msgstr "建议使用vCenter标准版。"
+
+# 11cf8def2a0e4ca6b35b4141c27541d3
+#: ../../hypervisor/vsphere.rst:41
+msgid ""
+"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."
+msgstr "请确保安装了hypervisor供应商发布的所有补丁程序。随时关注供应商支持信息，一旦发布补丁就立即安装。CloudStack不会跟踪或提醒你安装这些补丁。安装最新的补丁程序对主机至关重要。hypervisor供应商可能不会对过期的系统提供技术支持。"
+
+# 433a750f49e34f96a6568a12d3d5fd74
+#: ../../hypervisor/vsphere.rst:51
+msgid ""
+"Apply All Necessary Hotfixes. The lack of up-do-date hotfixes can lead to "
+"data corruption and lost VMs."
+msgstr "安装一切必要的补丁程序。缺乏最新补丁程序可能会导致数据和虚拟机丢失。"
+
+# cfbe010033704d72879d2e1a83fd3751
+#: ../../hypervisor/vsphere.rst:56
+msgid "Hardware requirements:"
+msgstr "硬件要求："
+
+# b0649e717356409293c4567e656821af
+#: ../../hypervisor/vsphere.rst:58
+msgid ""
+"The host must be certified as compatible with vSphere. See the VMware "
+"Hardware Compatibility Guide at "
+"`http://www.vmware.com/resources/compatibility/search.php "
+"<http://www.vmware.com/resources/compatibility/search.php>`_."
+msgstr "主机必须通过vSphere的兼容性认证。请查看VMware硬件兼容性指南 `http://www.vmware.com/resources/compatibility/search.php <http://www.vmware.com/resources/compatibility/search.php>`_."
+
+# 7bc3ed3794fb40418371381be3db54c4
+#: ../../hypervisor/vsphere.rst:63
+msgid ""
+"All hosts must be 64-bit and must support HVM (Intel-VT or AMD-V enabled)."
+msgstr "所有主机必须为64位架构并且支持HVM(启用Intel-VT或AMD-V)。"
+
+# 0a5dabc432dc454396baf7e656897fe6
+#: ../../hypervisor/vsphere.rst:66
+msgid ""
+"All hosts within a cluster must be homogenous. That means the CPUs must be "
+"of the same type, count, and feature flags."
+msgstr "同一群集中的所有节点必须为同一架构。CPU型号、数量和功能参数必须相同。"
+
+# 94cea4d65ee249be9661ee4a95356c3d
+#: ../../hypervisor/vsphere.rst:69
+msgid "64-bit x86 CPU (more cores results in better performance)"
+msgstr "64位x86 CPU(多核性能更佳)"
+
+# f25b466cb54f42b58faa3675162df14f
+#: ../../hypervisor/vsphere.rst:71
+msgid "Hardware virtualization support required"
+msgstr "硬件虚拟化支持"
+
+# 3eedde6532fd4545af478f114efb0aa6
+#: ../../hypervisor/vsphere.rst:73
+msgid "4 GB of memory"
+msgstr "4GB 内存"
+
+# 23b705dbe90b4ffda152518b41ce6fee
+#: ../../hypervisor/vsphere.rst:75
+msgid "36 GB of local disk"
+msgstr "36GB本地磁盘空间"
+
+# 1e1c717f723448de883b57b168c19a59
+#: ../../hypervisor/vsphere.rst:77
+msgid "At least 1 NIC"
+msgstr "至少一块网卡"
+
+# 3bc46abe138d48eeb9586740ba9e5d00
+#: ../../hypervisor/vsphere.rst:79
+msgid "Statically allocated IP Address"
+msgstr "静态分配的IP"
+
+# adf685e0308e4394aceccfcdb1c3e923
+#: ../../hypervisor/vsphere.rst:83
+msgid "vCenter Server requirements:"
+msgstr "vCenter服务器的系统要求："
+
+# 06ac32e7e8c04f65b302040e55a2a908
+#: ../../hypervisor/vsphere.rst:85
+msgid ""
+"Processor - 2 CPUs 2.0GHz or higher Intel or AMD x86 processors. Processor "
+"requirements may be higher if the database runs on the same machine."
+msgstr "处理器 - 2颗2.0GHz的Intel或AMD x86 CPUs， 或更高的处理器。如果数据库跟VC在同一台服务器中，可能会需要更高的处理器。"
+
+# 271c70d35c104435b5350721391ffed9
+#: ../../hypervisor/vsphere.rst:89
+msgid ""
+"Memory - 3GB RAM. RAM requirements may be higher if your database runs on "
+"the same machine."
+msgstr "内存 - 3GB。如果数据库跟VC在同一台服务器中，可能会需要更多内存。"
+
+# 720bf6b73cd1449fb7ae868c3286012c
+#: ../../hypervisor/vsphere.rst:92
+msgid ""
+"Disk storage - 2GB. Disk requirements may be higher if your database runs on"
+" the same machine."
+msgstr "磁盘空间 - 2GB。如果数据库跟VC在同一台服务器中，可能会需要更多的磁盘空间。"
+
+# 6f4ab896b8f049448d2141390cd6e6cb
+#: ../../hypervisor/vsphere.rst:95
+msgid ""
+"Microsoft SQL Server 2005 Express disk requirements. The bundled database "
+"requires up to 2GB free disk space to decompress the installation archive."
+msgstr "Microsoft SQL Server 2005 Express磁盘要求。最多需要 2 GB 的可用磁盘空间解压安装文件。"
+
+# 9474159ca7834a10864479073a1bf0d3
+#: ../../hypervisor/vsphere.rst:99
+msgid "Networking - 1Gbit or 10Gbit."
+msgstr "网络 - 1Gbit或者10Gbit。"
+
+# 38899761f45d434f8c9fb7a5d24ec00e
+#: ../../hypervisor/vsphere.rst:101
+msgid ""
+"For more information, see `\"vCenter Server and the vSphere Client Hardware "
+"Requirements\" "
+"<http://pubs.vmware.com/vsp40/wwhelp/wwhimpl/js/html/wwhelp.htm#href=install/c_vc_hw.html>`_."
+msgstr "更多信息，请参考 `\"vCenter Server 和 vSphere Client 硬件要求\" <http://pubs.vmware.com/vsp40/wwhelp/wwhimpl/js/html/wwhelp.htm#href=install/c_vc_hw.html>`_。"
+
+# 43340509b56641c28387c6a0b718a9a2
+#: ../../hypervisor/vsphere.rst:106
+msgid "Other requirements:"
+msgstr "其他要求："
+
+# c0ca168c59964efc9aa79369ee7a8104
+#: ../../hypervisor/vsphere.rst:108
+msgid ""
+"VMware vCenter Standard Edition 4.1 or 5.0 must be installed and available "
+"to manage the vSphere hosts."
+msgstr "必须安装VMware vCenter Standard 4.1或5.0版本，并且能够管理vSphere主机。"
+
+# 0ba8fe6d64854dac84850796d0c84f0b
+#: ../../hypervisor/vsphere.rst:111
+msgid ""
+"vCenter must be configured to use the standard port 443 so that it can "
+"communicate with the CloudStack Management Server."
+msgstr "必须配置vCenter使用443端口与CloudStack管理服务器通讯。"
+
+# 311e91fb341e4d30a649ba13d80e2e72
+#: ../../hypervisor/vsphere.rst:114
+msgid ""
+"You must re-install VMware ESXi if you are going to re-use a host from a "
+"previous install."
+msgstr "如果你计划利用之前安装的主机，那么必须重新安装VMware ESXi。"
+
+# c5dcee58723d4fa1b707fecaede37c0e
+#: ../../hypervisor/vsphere.rst:117
+msgid ""
+"CloudStack requires VMware vSphere 4.1 or 5.0. VMware vSphere 4.0 is not "
+"supported."
+msgstr "CloudStack要求VMwarevSphere 4.1或者5.0版本，不支持VMware vSphere 4.0版本。"
+
+# d988a28be0c94e3b9935e2025d0475d0
+#: ../../hypervisor/vsphere.rst:120
+msgid ""
+"All hosts must be 64-bit and must support HVM (Intel-VT or AMD-V enabled). "
+"All hosts within a cluster must be homogeneous. That means the CPUs must be "
+"of the same type, count, and feature flags."
+msgstr "所有主机必须为64位架构并且支持HVM(启用Intel-VT或AMD-V)。同一群集中的所有节点必须为同一架构。CPU型号、数量和功能参数必须相同。"
+
+# f830e27a969e413b831620b0907e346f
+#: ../../hypervisor/vsphere.rst:124
+msgid ""
+"The CloudStack management network must not be configured as a separate "
+"virtual network. The CloudStack management network is the same as the "
+"vCenter management network, and will inherit its configuration. See :ref"
+":`configure-vcenter-management-network`."
+msgstr "CloudStack 管理网络不能使用独立的虚拟网络。CloudStack使用vCenter的管理网络，并继承vCenter管理网络的配置。 可参考 :ref:`configure-vcenter-management-network`."
+
+# eac2d87ef82b4063864397fe3ac48213
+#: ../../hypervisor/vsphere.rst:129
+msgid "CloudStack requires ESXi. ESX is not supported."
+msgstr "CloudStack仅支持ESXi，不支持ESX。"
+
+# 397732aa4a884edbab1fec4290fceae4
+#: ../../hypervisor/vsphere.rst:131
+msgid ""
+"All resources used for CloudStack must be used for CloudStack only. "
+"CloudStack cannot share instance of ESXi or storage with other management "
+"consoles. Do not share the same storage volumes that will be used by "
+"CloudStack with a different set of ESXi servers that are not managed by "
+"CloudStack."
+msgstr "所有用于CloudStack的资源只能被CloudStack使用。CloudStack无法与其他管理控制台共享ESXi实例或存储。请不要与其他不受CloudStack管理的ESXi共享同一个存储卷。"
+
+# 483d1d73b54a40d78329af14748fd831
+#: ../../hypervisor/vsphere.rst:137
+msgid ""
+"Put all target ESXi hypervisors in a cluster in a separate Datacenter in "
+"vCenter."
+msgstr "将所有目标ESXi hypervisors加入vCenter中独立数据中心之下的群集。"
+
+# 8151eb61ba874bc8a60d05b0c751a321
+#: ../../hypervisor/vsphere.rst:140
+msgid ""
+"The cluster that will be managed by CloudStack should not contain any VMs. "
+"Do not run the management server, vCenter or any other VMs on the cluster "
+"that is designated for CloudStack use. Create a separate cluster for use of "
+"CloudStack and make sure that they are no VMs in this cluster."
+msgstr "将被CloudStack管理的群集中不应该存在任何VM。且不应该在CloudStack管理的群集中运行任何管理服务器、vCenter或者VM。为CloudStack创建一个独立的群集，并确保群集中不存在VM。"
+
+# 2bcc13091d3947dc9e7801b766452c80
+#: ../../hypervisor/vsphere.rst:146
+msgid ""
+"All the required VLANS must be trunked into all network switches that are "
+"connected to the ESXi hypervisor hosts. These would include the VLANS for "
+"Management, Storage, vMotion, and guest VLANs. The guest VLAN (used in "
+"Advanced Networking; see Network Setup) is a contiguous range of VLANs that "
+"will be managed by CloudStack."
+msgstr "所有必需的vlan必须通过所有网络交换机端口的trunk模式连接到ESXi hypervisor主机。其中包含管理，存储，vMotion和来宾等VLANs。CloudStack管理一段连续的来宾VLANs范围(高级网络；请参阅 网络设置) 。"
+
+# 12d708e9230b4cf2a6eec95bc47de138
+#: ../../hypervisor/vsphere.rst:154
+msgid "Preparation Checklist for VMware"
+msgstr "VMware的准备工作清单"
+
+# f9a24ff6b44f49d198fbee57859227b1
+#: ../../hypervisor/vsphere.rst:156
+msgid ""
+"For a smoother installation, gather the following information before you "
+"start:"
+msgstr "为了能顺利地安装，在安装之前请收集以下信息："
+
+# 7c40a197d95543d5b09db63ac46a3ff7
+#: ../../hypervisor/vsphere.rst:159
+msgid "Information listed in :ref:`vcenter-checklist`"
+msgstr ":ref:`vcenter-checklist` 中列出的信息"
+
+# 985e27ff41074586a10f90781fc9434b
+#: ../../hypervisor/vsphere.rst:161
+msgid "Information listed in :ref:`networking-checklist-for-vmware`"
+msgstr ":ref:`networking-checklist-for-vmware` 中列出的信息"
+
+# 7bbac620f96b4b238ced330b74d07b49
+#: ../../hypervisor/vsphere.rst:167
+msgid "vCenter Checklist"
+msgstr "vCenter检查清单"
+
+# 04e3ab33127443328f019f7d08a250d6
+#: ../../hypervisor/vsphere.rst:169
+msgid "You will need the following information about vCenter."
+msgstr "你需要关于vCenter的下列信息："
+
+# 230ef95a22cb40c2ac102a9798f69d50
+#: ../../hypervisor/vsphere.rst:172
+msgid "vCenter Requirement"
+msgstr "vCenter要求"
+
+# 52d76ece5b4a44309c219d371f7ddd03
+# 82bd8117216b4dec8f2d3946d40f445c
+# 28ee056cc5ba4ffa9d14464a46e34f3a
+#: ../../hypervisor/vsphere.rst:172 ../../hypervisor/vsphere.rst:189
+#: ../../hypervisor/vsphere.rst:459
+msgid "Notes"
+msgstr "备注"
+
+# e6d6093156eb4c89a795c492963fceed
+#: ../../hypervisor/vsphere.rst:174
+msgid "vCenter User"
+msgstr "vCenter用户"
+
+# 55d86b0382d0488e9e1392ae0a228a03
+#: ../../hypervisor/vsphere.rst:174
+msgid "This user must have admin privileges."
+msgstr "用户必须拥有管理员权限。"
+
+# 21fb181b5dc444fd8fd758ae9a39ba95
+#: ../../hypervisor/vsphere.rst:175
+msgid "vCenter User Password"
+msgstr "vCenter用户的密码"
+
+# 6be77420b0d6471a926b242982798b63
+#: ../../hypervisor/vsphere.rst:175
+msgid "Password for the above user."
+msgstr "上述用户的密码。"
+
+# 79ba83eb3964471ba6ea6718fde7cb34
+#: ../../hypervisor/vsphere.rst:176
+msgid "vCenter Datacenter Name"
+msgstr "vCenter数据库名称"
+
+# 2fd0d6ea1f9a4c85b81d4276deb2c9b8
+#: ../../hypervisor/vsphere.rst:176
+msgid "Name of the datacenter."
+msgstr "数据中心名称"
+
+# 3150bf92a4a347e5aa40a8fe765140b6
+#: ../../hypervisor/vsphere.rst:177
+msgid "vCenter Cluster Name"
+msgstr "vCenter群集名称"
+
+# 4da7406ee21a41999d49265263a3d330
+#: ../../hypervisor/vsphere.rst:177
+msgid "Name of the cluster."
+msgstr "群集名称"
+
+# f06da8e5f04e4715a3428b02687006a5
+#: ../../hypervisor/vsphere.rst:184
+msgid "Networking Checklist for VMware"
+msgstr "VMware网络清单"
+
+# 0b5d8b8b8030478490415117b971cc1d
+#: ../../hypervisor/vsphere.rst:186
+msgid "You will need the following information about VLAN."
+msgstr "你需要以下关于VLAN的信息。"
+
+# d18a8dbf3b5a4e37a6b4a9082e8d9b9a
+#: ../../hypervisor/vsphere.rst:189
+msgid "VLAN Information"
+msgstr "VLAN信息"
+
+# a18ba1020be54125a1a83ecae1b4a59d
+#: ../../hypervisor/vsphere.rst:191
+msgid "ESXi VLAN"
+msgstr "ESXi VLAN"
+
+# 7552379727114564bb1a6005a0bc0b5a
+#: ../../hypervisor/vsphere.rst:191
+msgid "VLAN on which all your ESXi hypervisors reside."
+msgstr "全部ESXi hypervisors主机所在的VLAN。"
+
+# 94167adee63f4adda49e8511ecf154c2
+#: ../../hypervisor/vsphere.rst:192
+msgid "ESXI VLAN IP Address"
+msgstr "ESXi VLAN IP地址"
+
+# 96b5d173daa14cb686b8df6e2af6eda3
+#: ../../hypervisor/vsphere.rst:192
+msgid ""
+"IP Address Range in the ESXi VLAN. One address per Virtual Router is used "
+"from this range."
+msgstr "ESXi VLAN的IP地址范围。每个虚拟路由器使用该范围内的一个IP。"
+
+# 61a0a647d1304c7592fee8b73395ac5e
+#: ../../hypervisor/vsphere.rst:193
+msgid "ESXi VLAN IP Gateway"
+msgstr "ESXi VLAN网关IP"
+
+# 502e2adfefd54290b787aba3d70a6a3c
+#: ../../hypervisor/vsphere.rst:194
+msgid "ESXi VLAN Netmask"
+msgstr "ESXi VLAN子网掩码"
+
+# 3d862fcd0d14490fb29acd36a2958c5d
+#: ../../hypervisor/vsphere.rst:195
+msgid "Management Server VLAN"
+msgstr "管理服务器VLAN"
+
+# ce8231bbfb6f4f86b212bfa7912ce3fb
+#: ../../hypervisor/vsphere.rst:195
+msgid "VLAN on which the CloudStack Management server is installed."
+msgstr "CloudStack管理服务器所在的VLAN。"
+
+# 924ddf7763994ebfbd0a15b603bc22d5
+#: ../../hypervisor/vsphere.rst:196
+msgid "Public VLAN"
+msgstr "公共网络VLAN"
+
+# 3f3fdc9789c048b49167a98f52acc5dc
+#: ../../hypervisor/vsphere.rst:196
+msgid "VLAN for the Public Network."
+msgstr "公共网络的VLAN"
+
+# ee0b4346c9ad482786c589e1947e8ce8
+#: ../../hypervisor/vsphere.rst:197
+msgid "Public VLAN Gateway"
+msgstr "公共网络VLAN的网关"
+
+# 093927bfb8494060b58a6be1d37571a3
+#: ../../hypervisor/vsphere.rst:198
+msgid "Public VLAN Netmask"
+msgstr "公共网络VLAN的子网掩码"
+
+# 48b1d1223c1942f486b2e81fd85701ba
+#: ../../hypervisor/vsphere.rst:199
+msgid "Public VLAN IP Address Range"
+msgstr "公共VLAN IP地址范围"
+
+# fafd189f95f0456fa23cbebd9f3ed266
+#: ../../hypervisor/vsphere.rst:199
+msgid ""
+"Range of Public IP Addresses available for CloudStack use. These addresses "
+"will be used for virtual router on CloudStack to route private traffic to "
+"external networks."
+msgstr "CloudStack使用的公共网络IP范围。CloudStack中的虚拟路由器使用这些地址，用于路由专用流量至外部网络。"
+
+# 8eb456b1619c4753be00cf585593cc7e
+#: ../../hypervisor/vsphere.rst:202
+msgid "VLAN Range for Customer use"
+msgstr "客户使用的VLAN范围"
+
+# dad2013c354145e5b820dc70ef56e99c
+#: ../../hypervisor/vsphere.rst:202
+msgid ""
+"A contiguous range of non-routable VLANs. One VLAN will be assigned for each"
+" customer."
+msgstr "连续的不可路由的VLAN范围。每个用户会分配一个VLAN。"
+
+# 55066669b6874439b121073b06ac7faa
+#: ../../hypervisor/vsphere.rst:208
+msgid "vSphere Installation Steps"
+msgstr "vSphere安装步骤"
+
+# 9254e8523b3f4c3aad496a3e1776451f
+#: ../../hypervisor/vsphere.rst:210
+msgid ""
+"If you haven't already, you'll need to download and purchase vSphere from "
+"the VMware Website (`https://www.vmware.com/tryvmware/index.php?p=vmware-"
+"vsphere&lp=1 <https://www.vmware.com/tryvmware/index.php?p=vmware-"
+"vsphere&lp=1>`_) and install it by following the VMware vSphere Installation"
+" Guide."
+msgstr "如果你还没用准备好安装介质，请在VMware网站下载和购买(`https://www.vmware.com/tryvmware/index.php?p=vmware-vsphere&lp=1 <https://www.vmware.com/tryvmware/index.php?p=vmware-vsphere&lp=1>`_)并按照VMware vSphere安装指南安装。"
+
+# b9235024292f46faacee1b73c71ce9c9
+#: ../../hypervisor/vsphere.rst:215
+msgid ""
+"Following installation, perform the following configuration, which are "
+"described in the next few sections:"
+msgstr "安装过程中，执行下面几个章节描述的以下配置："
+
+# 10d7af3e4cef499aa1fa230b12ce67e0
+#: ../../hypervisor/vsphere.rst:219
+msgid "Required"
+msgstr "要求"
+
+# 906de2717fd64b5c87584e6807af120e
+#: ../../hypervisor/vsphere.rst:219
+msgid "Optional"
+msgstr "可选项"
+
+# b461abbf9e42401da9600e4666054caa
+#: ../../hypervisor/vsphere.rst:221
+msgid "ESXi host setup"
+msgstr "ESXi主机安装"
+
+# a672baaf4ca64f66ba7b0a4aa2b9c820
+#: ../../hypervisor/vsphere.rst:221
+msgid "NIC bonding"
+msgstr "网卡绑定"
+
+# 15b07c50f2814ef5a9b9fe3e6054c7ef
+#: ../../hypervisor/vsphere.rst:222
+msgid ""
+"Configure host physical networking,virtual switch, vCenter Management "
+"Network, and extended port range"
+msgstr "配置主机的物理网络，虚拟交换机，vCenter管理网络和扩展的端口范围"
+
+# 82afddb1d1534689ac6a034abc9ad969
+#: ../../hypervisor/vsphere.rst:222
+msgid "Multipath storage"
+msgstr "存储多路径"
+
+# 908c7c0df32a4091b51fa92198fd58da
+#: ../../hypervisor/vsphere.rst:223
+msgid "Prepare storage for iSCSI"
+msgstr "准备iSCSI存储"
+
+# a92c6507ae414e5f9a0ec8ff2545209e
+#: ../../hypervisor/vsphere.rst:224
+msgid ""
+"Configure clusters in vCenter and add hosts to them, or add hosts without "
+"clusters to vCenter"
+msgstr "在vCenter中配置集群并添加主机，或不使用集群，直接在vCenter中添加主机。"
+
+# a5fd230588934d9a949707390d10c3cd
+#: ../../hypervisor/vsphere.rst:229
+msgid "ESXi Host setup"
+msgstr "ESXi主机配置"
+
+# 4560ac7e0a014d70bbfe865d8cd78abd
+#: ../../hypervisor/vsphere.rst:231
+msgid ""
+"All ESXi hosts should enable CPU hardware virtualization support in BIOS. "
+"Please note hardware virtualization support is not enabled by default on "
+"most servers."
+msgstr "所有ESXi主机都应该在BIOS中启用CPU硬件虚拟化支持。请注意，大多数服务器默认不启用该功能。"
+
+# 4ecccb36e87644d3a98414f9f939fdc5
+#: ../../hypervisor/vsphere.rst:237
+msgid "Physical Host Networking"
+msgstr "物理主机网络"
+
+# 24de9cbfdd0a4277a359684f50fb2ca7
+#: ../../hypervisor/vsphere.rst:239
+msgid ""
+"You should have a plan for cabling the vSphere hosts. Proper network "
+"configuration is required before adding a vSphere host to CloudStack. To "
+"configure an ESXi host, you can use vClient to add it as standalone host to "
+"vCenter first. Once you see the host appearing in the vCenter inventory "
+"tree, click the host node in the inventory tree, and navigate to the "
+"Configuration tab."
+msgstr "您应该准备一个vSphere主机连接的规划。将主机添加至CloudStack之前，需要合理地配置网络。要配置ESXi主机，可以先用vClient将它作为独立主机添加到vCenter。当您在vCenter的导航树中看到该主机时，点击它，选择配置页。"
+
+# 1221f7c6183a439e9db5dfe5282e491a
+#: ../../hypervisor/vsphere.rst:246
+msgid "|vspherephysicalnetwork.png: vSphere client|"
+msgstr "|vspherephysicalnetwork.png: vSphere client|"
+
+# 814e620809104bd1bd43c8b8d28445ad
+#: ../../hypervisor/vsphere.rst:248
+msgid ""
+"In the host configuration tab, click the \"Hardware/Networking\" link to "
+"bring up the networking configuration page as above."
+msgstr "在主机的配置标签页中，点击\"硬件/网络\"链接转到上图中的网络配置页。"
+
+# 6bb1a1da1840400f9cd0ea1a73f0c12a
+#: ../../hypervisor/vsphere.rst:253
+msgid "Configure Virtual Switch"
+msgstr "配置虚拟交换机"
+
+# b867b4246fc449979584e901e0fac0fb
+#: ../../hypervisor/vsphere.rst:255
+msgid ""
+"A default virtual switch vSwitch0 is created. CloudStack requires all ESXi "
+"hosts in the cloud to use the same set of virtual switch names. If you "
+"change the default virtual switch name, you will need to configure one or "
+"more CloudStack configuration variables as well."
+msgstr "默认情况下，系统会创建虚拟交换机vSwitch0。CloudStack要求云中所有ESXi主机中的虚拟交换机都使用相同的名字。如果你改变了默认虚拟交换机名称，那么你需要改变一个或多个CloudStack配置。"
+
+# cfa8f6a17984452ba1aabf882f8c3d42
+#: ../../hypervisor/vsphere.rst:262
+msgid "Separating Traffic"
+msgstr "流量隔离"
+
+# 69b7df288a684ae0b55024da82f5e8fc
+#: ../../hypervisor/vsphere.rst:264
+msgid ""
+"CloudStack allows you to use vCenter to configure three separate networks "
+"per ESXi host. These networks are identified by the name of the vSwitch they"
+" are connected to. The allowed networks for configuration are public (for "
+"traffic to/from the public internet), guest (for guest-guest traffic), and "
+"private (for management and usually storage traffic). You can use the "
+"default virtual switch for all three, or create one or two other vSwitches "
+"for those traffic types."
+msgstr "CloudStack允许你使用vCenter为每个ESXi主机配置三个独立的网络。CloudStack通过vSwitch的名称识别网络。允许配置的网络分别为公共网络(与公共互联网之间的流量)，来宾网络(来宾-来宾流量)和管理网络(与管理服务器和存储之间的流量)。您可以设置3种网络使用默认的虚拟交换机，或创建1个/2个其他虚拟交换机来承载这些网络流量。"
+
+# bf95ebb6ddf44a5cbf07c996d8a660f3
+#: ../../hypervisor/vsphere.rst:272
+msgid ""
+"If you want to separate traffic in this way you should first create and "
+"configure vSwitches in vCenter according to the vCenter instructions. Take "
+"note of the vSwitch names you have used for each traffic type. You will "
+"configure CloudStack to use these vSwitches."
+msgstr "如果您想以这样的方式隔离流量，首先应按照vCenter的指南在vCenter中创建并配置虚拟交换机。请记录每种网络使用的虚拟交换机名称。您需要配置CloudStack使用这些虚拟交换机。"
+
+# bc3f5581dea54034ae73ec0a942e180c
+#: ../../hypervisor/vsphere.rst:279
+msgid "Increasing Ports"
+msgstr "增加端口"
+
+# 88f709156fa8484b902282de91c0793f
+#: ../../hypervisor/vsphere.rst:281
+msgid ""
+"By default a virtual switch on ESXi hosts is created with 56 ports. We "
+"recommend setting it to 4088, the maximum number of ports allowed. To do "
+"that, click the \"Properties...\" link for virtual switch (note this is not "
+"the Properties link for Networking)."
+msgstr "ESXi主机的虚拟交换机默认有56个端口。我们建议设为最大允许数4088。要设置该值，请点击虚拟交换机的“属性…”链接(注意，不是网络的属性)。"
+
+# 4e01bfffde3c422aa7fcdddc74de892f
+#: ../../hypervisor/vsphere.rst:286
+msgid "|vsphereincreaseports.png: vSphere client|"
+msgstr "|vsphereincreaseports.png: vSphere client|"
+
+# 11994bd16f5a45a383d33894daaa0f53
+#: ../../hypervisor/vsphere.rst:288
+msgid ""
+"In vSwitch properties dialog, select the vSwitch and click Edit. You should "
+"see the following dialog:"
+msgstr "在vSwitch属性对话框中，选择vSwitch，点击“编辑”，您将看到以下对话框："
+
+# f64cba4600314bd89382d82cd5d37e5a
+#: ../../hypervisor/vsphere.rst:291
+msgid "|vspherevswitchproperties.png: vSphere client|"
+msgstr "|vspherevswitchproperties.png: vSphere client|"
+
+# 5216577220b34c2980dadbd02476e716
+#: ../../hypervisor/vsphere.rst:293
+msgid ""
+"In this dialog, you can change the number of switch ports. After you've done"
+" that, ESXi hosts are required to reboot in order for the setting to take "
+"effect."
+msgstr "在该对话框中，您可以修改端口数量。修改完后，为使配置生效，需要重启ESXi主机。"
+
+# 0ad4145d13e84c828a62f3d1b613dbd3
+#: ../../hypervisor/vsphere.rst:301
+msgid "Configure vCenter Management Network"
+msgstr "配置vCenter管理网络"
+
+# 55856f0ddbed407eae0a6e859a61f73d
+#: ../../hypervisor/vsphere.rst:303
+msgid ""
+"In the vSwitch properties dialog box, you may see a vCenter management "
+"network. This same network will also be used as the CloudStack management "
+"network. CloudStack requires the vCenter management network to be configured"
+" properly. Select the management network item in the dialog, then click "
+"Edit."
+msgstr "在vSwith属性对话框中，您可以看到一个vCenter管理网络。CloudStack的管理网络也使用该网络。CloudStack要求正确配置vCenter的管理网络。在对话框中点击管理网络，然后点击编辑。"
+
+# 07fa2b72b0564cb89199ffcab114a7ee
+#: ../../hypervisor/vsphere.rst:309
+msgid "|vspheremgtnetwork.png: vSphere client|"
+msgstr "|vspheremgtnetwork.png: vSphere client|"
+
+# 00017c3e4d5e4506808936e3c52b70fd
+#: ../../hypervisor/vsphere.rst:311
+msgid "Make sure the following values are set:"
+msgstr "请确保配置以下设置："
+
+# 383a238254dd4a109140ddd990c2ced7
+#: ../../hypervisor/vsphere.rst:313
+msgid "VLAN ID set to the desired ID"
+msgstr "VLAN ID设置为期望的ID"
+
+# 92318eb7b2c544b08843c50e90bfb36c
+#: ../../hypervisor/vsphere.rst:315
+msgid "vMotion enabled."
+msgstr "启用vMotion。"
+
+# d6f57109f2fa4226a9ff5372703acb79
+#: ../../hypervisor/vsphere.rst:317
+msgid "Management traffic enabled."
+msgstr "启用管理流量。"
+
+# 44d67b07355843239d874a52581251b0
+#: ../../hypervisor/vsphere.rst:319
+msgid ""
+"If the ESXi hosts have multiple VMKernel ports, and ESXi is not using the "
+"default value \"Management Network\" as the management network name, you "
+"must follow these guidelines to configure the management network port group "
+"so that CloudStack can find it:"
+msgstr "如果ESXi主机具有多个VMKernel端口，并且ESXi没有使用默认的“Management Network”作为管理网络名称，您必须按照以下指南配置管理网络端口组，以便CloudStack可以发现管理网络。"
+
+# 9bb53b01739a4056995c0d4a8ca8d472
+#: ../../hypervisor/vsphere.rst:324
+msgid "Use one label for the management network port across all ESXi hosts."
+msgstr "在所有ESXi主机上使用同一个管理网络端口组名称。"
+
+# 9a73da845a73437891672f0ca961eba4
+#: ../../hypervisor/vsphere.rst:326
+msgid ""
+"In the CloudStack UI, go to Configuration - Global Settings and set "
+"vmware.management.portgroup to the management network label from the ESXi "
+"hosts."
+msgstr "在CloudStack管理界面中，点击配置-全局设置，修改vmware.management.portgroup为ESXi主机管理网络的标签。"
+
+# b6695dde2a9e4023ab181aa0b7f43ddf
+#: ../../hypervisor/vsphere.rst:332
+msgid "Extend Port Range for CloudStack Console Proxy"
+msgstr "为CloudStack控制台代理扩展端口范围"
+
+# 8acd9f9a7fd74d82b305dd73462cb96d
+#: ../../hypervisor/vsphere.rst:334
+msgid "(Applies only to VMware vSphere version 4.x)"
+msgstr "（仅适用于VMware vSphere 4.x）"
+
+# 3ca5d828266843f981f791b128eaa6a4
+#: ../../hypervisor/vsphere.rst:336
+msgid ""
+"You need to extend the range of firewall ports that the console proxy works "
+"with on the hosts. This is to enable the console proxy to work with VMware-"
+"based VMs. The default additional port range is 59000-60000. To extend the "
+"port range, log in to the VMware ESX service console on each host and run "
+"the following commands:"
+msgstr "为使控制台代理可以和主机一起工作，您需要扩展主机的防火墙端口范围。这是为了使控制台代理可以访问VMware的VM。为扩展端口范围，请登录到每台主机的VMware ESX服务控制台，然后执行以下命令："
+
+# 1f25aa96ef604ce8acd3ae301b49add1
+#: ../../hypervisor/vsphere.rst:349
+msgid "Configure NIC Bonding for vSphere"
+msgstr "配置vSphere的网卡绑定"
+
+# b3ba21794a784430bc2e6d8755c2a5d6
+#: ../../hypervisor/vsphere.rst:351
+msgid ""
+"NIC bonding on vSphere hosts may be done according to the vSphere "
+"installation guide."
+msgstr "vSphere主机的网卡绑定可以按照vSphere安装指南完成。"
+
+# 57eca85918594e28af92c0453eb88f9e
+#: ../../hypervisor/vsphere.rst:356
+msgid "Configuring a vSphere Cluster with Nexus 1000v Virtual Switch"
+msgstr "配置vSphere群集使用Nexus 1000v虚拟交换机"
+
+# c41be8a6fd7a495a9f3fc72a6f572fc1
+#: ../../hypervisor/vsphere.rst:358
+msgid ""
+"CloudStack supports Cisco Nexus 1000v dvSwitch (Distributed Virtual Switch) "
+"for virtual network configuration in a VMware vSphere environment. This "
+"section helps you configure a vSphere cluster with Nexus 1000v virtual "
+"switch in a VMware vCenter environment. For information on creating a "
+"vSphere cluster, see `\"VMware vSphere Installation and Configuration\" "
+"<#vmware-vsphere-installation-and-configuration>`_"
+msgstr "CloudStack支持在VMware vSphere环境中使用Cisco Nexus 1000v dvSwitch (分布式虚拟交换机)。本章节能帮助你配置vSphere群集使用Nexus 1000v虚拟交换机。关于创建vSphere群集的更多信息，请参考 `\"VMware vSphere安装和配置\" <#vmware-vsphere-installation-and-configuration>`_"
+
+# fd98cbd7bb554d358747d066d0beb7ec
+#: ../../hypervisor/vsphere.rst:368
+msgid "About Cisco Nexus 1000v Distributed Virtual Switch"
+msgstr "关于Cisco Nexus 1000v分布式虚拟交换机"
+
+# 59712fc0b9b3480680eab3fc5438d7d6
+#: ../../hypervisor/vsphere.rst:370
+msgid ""
+"The Cisco Nexus 1000V virtual switch is a software-based virtual machine "
+"access switch for VMware vSphere environments. It can span multiple hosts "
+"running VMware ESXi 4.0 and later. A Nexus virtual switch consists of two "
+"components: the Virtual Supervisor Module (VSM) and the Virtual Ethernet "
+"Module (VEM). The VSM is a virtual appliance that acts as the switch's "
+"supervisor. It controls multiple VEMs as a single network device. The VSM is"
+" installed independent of the VEM and is deployed in redundancy mode as "
+"pairs or as a standalone appliance. The VEM is installed on each VMware ESXi"
+" server to provide packet-forwarding capability. It provides each virtual "
+"machine with dedicated switch ports. This VSM-VEM architecture is analogous "
+"to a physical Cisco switch's supervisor (standalone or configured in high-"
+"availability mode) and multiple linecards architecture."
+msgstr "Cisco Nexus 1000V虚拟交换机是一个内置软件程序的虚拟机。它能跨越多个运行VMware ESXi 4.0或更高版本的主机部署。Nexus虚拟交换机包括两个组件：Virtual Supervisor Module (VSM)和 Virtual Ethernet Module (VEM)。VSM是一个管理交换机的虚拟设备。它单独控制多个VEM。VSM安装在每台VMware ESXi服务器当中提供包转发功能。它为每个虚拟机提供单独的交换机接口。VSM-VEM架构与物理交换机的管理机制（单独或者高可用模式）和多线卡架构类似。"
+
+# f739316e27a14ab39ad8ab22ae8e3d33
+#: ../../hypervisor/vsphere.rst:384
+msgid ""
+"Nexus 1000v switch uses vEthernet port profiles to simplify network "
+"provisioning for virtual machines. There are two types of port profiles: "
+"Ethernet port profile and vEthernet port profile. The Ethernet port profile "
+"is applied to the physical uplink ports-the NIC ports of the physical NIC "
+"adapter on an ESXi server. The vEthernet port profile is associated with the"
+" virtual NIC (vNIC) that is plumbed on a guest VM on the ESXi server. The "
+"port profiles help the network administrators define network policies which "
+"can be reused for new virtual machines. The Ethernet port profiles are "
+"created on the VSM and are represented as port groups on the vCenter server."
+msgstr "Nexus 1000v交换机使用vEthernet端口配置文件为虚拟机提供简单的网络。它有两种类型的端口配置文件：Ethernet端口配置文件和vEthernet端口配置文件。Ethernet端口配置文件应用到物理上联端口-ESXi服务器上面的物理网卡的端口。vEthernet端口配置文件关联到ESXi服务器上运行的虚拟机的虚拟网卡。端口配置文件可以帮助网络管理员快速的为其他虚机定义同样的网络策略。VSM创建的Ethernet端口策略在vCenter服务器上显示为端口组。"
+
+# de9fe88270bf4403afa9e22b05f73471
+# 5d365a93c5e949efb76d86e0763cbad3
+#: ../../hypervisor/vsphere.rst:397 ../../hypervisor/vsphere.rst:715
+msgid "Prerequisites and Guidelines"
+msgstr "先决条件和指南"
+
+# 7c2f20207c414d7d819f7e0e5d408552
+#: ../../hypervisor/vsphere.rst:399
+msgid ""
+"This section discusses prerequisites and guidelines for using Nexus virtual "
+"switch in CloudStack. Before configuring Nexus virtual switch, ensure that "
+"your system meets the following requirements:"
+msgstr "本章节探讨了在CloudStack中使用Nexus虚拟交换机的先决条件与指南。在配置Nexus虚拟交换机之前，请确保你的系统符合下列条件："
+
+# 6069bf189abd4043952218eb4c6136a7
+#: ../../hypervisor/vsphere.rst:403
+msgid "A cluster of servers (ESXi 4.1 or later) is configured in the vCenter."
+msgstr "在vCenter中配置ESXi（ESXi 4.1或更高）群集。"
+
+# f86fc439aeb543e4a45e2c8bbdfd9510
+#: ../../hypervisor/vsphere.rst:406
+msgid ""
+"Each cluster managed by CloudStack is the only cluster in its vCenter "
+"datacenter."
+msgstr "CloudStack只能管理存在当前vCenter数据中心管理之下的每一个群集。"
+
+# 26d3882e3f964a7ba7e2079ae88133a1
+#: ../../hypervisor/vsphere.rst:409
+msgid ""
+"A Cisco Nexus 1000v virtual switch is installed to serve the datacenter that"
+" contains the vCenter cluster. This ensures that CloudStack doesn't have to "
+"deal with dynamic migration of virtual adapters or networks across other "
+"existing virtual switches. See `Cisco Nexus 1000V Installation and Upgrade "
+"Guide "
+"<http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_5_1/install_upgrade/vsm_vem/guide/n1000v_installupgrade.html>`_"
+" for guidelines on how to install the Nexus 1000v VSM and VEM modules."
+msgstr "Cisco Nexus 1000v虚拟交换机安装在vCenter数据中心所包含的群集主机。这将确保CloudStack不必处理跨现存虚拟交换机之间的虚拟网卡或网络的动态迁移。如何安装Nexus 1000v VSM和VEM 模块，请参考 `Cisco Nexus 1000V Installation and Upgrade Guide <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_5_1/install_upgrade/vsm_vem/guide/n1000v_installupgrade.html>`_。"
+
+# 985ff8e2082f419d8d77119acefbfa01
+#: ../../hypervisor/vsphere.rst:417
+msgid ""
+"The Nexus 1000v VSM is not deployed on a vSphere host that is managed by "
+"CloudStack."
+msgstr "Nexus 1000v VSM不能部署在由CloudStack管理的vSphere主机上。"
+
+# affd3445b0854e7ab5ffbef4fa7b9db4
+#: ../../hypervisor/vsphere.rst:420
+msgid ""
+"When the maximum number of VEM modules per VSM instance is reached, an "
+"additional VSM instance is created before introducing any more ESXi hosts. "
+"The limit is 64 VEM modules for each VSM instance."
+msgstr "当每个VSM实例的VEM模块达到最大数量时，需要在添加额外的VSM实例之前引入更多的ESXi主机。每个VSM实例的VEM模块数量限制为64个。"
+
+# e95f2908159b4be0820e8620c94c70c5
+#: ../../hypervisor/vsphere.rst:424
+msgid ""
+"CloudStack expects that the Management Network of the ESXi host is "
+"configured on the standard vSwitch and searches for it in the standard "
+"vSwitch. Therefore, ensure that you do not migrate the management network to"
+" Nexus 1000v virtual switch during configuration."
+msgstr "CloudStack期望ESXi主机的管理网络被配置在标准的vSwitch之上并且在标准的vSwitch中搜索该网络。因此，确保在配置期间不要把管理网络迁移到Nexus 1000v上。"
+
+# 7f74225fb2604754a58806809f2c65c1
+#: ../../hypervisor/vsphere.rst:430
+msgid "All information given in :ref:`nexus-vswift-preconf`"
+msgstr "所有信息在ref:`nexus-vswift-preconf`中："
+
+# 0ab3b61d4a674fb5ba50354f165cf6e9
+#: ../../hypervisor/vsphere.rst:436
+msgid "Nexus 1000v Virtual Switch Preconfiguration"
+msgstr "Nexus 1000v虚拟交换机预配置"
+
+# 2af119d57464425ea16e15da99bba2c2
+# 6067502710ad439c97b2463c8710b803
+#: ../../hypervisor/vsphere.rst:439 ../../hypervisor/vsphere.rst:737
+msgid "Preparation Checklist"
+msgstr "准备工作清单"
+
+# 70d29993a857439d8efb48c089332053
+#: ../../hypervisor/vsphere.rst:441
+msgid ""
+"For a smoother configuration of Nexus 1000v switch, gather the following "
+"information before you start:"
+msgstr "要顺利配置 Nexus 1000v交换机，请在开始之前收集下列信息："
+
+# 12d946312911404db67cdfccc6dcfe14
+#: ../../hypervisor/vsphere.rst:444
+msgid "vCenter credentials"
+msgstr "vCenter凭证"
+
+# 568485eb210d406098935f8d5ab9b909
+#: ../../hypervisor/vsphere.rst:446
+msgid "Nexus 1000v VSM IP address"
+msgstr "Nexus 1000v VSM IP地址"
+
+# a593926b86d04d3a8de54de3c70a9174
+#: ../../hypervisor/vsphere.rst:448
+msgid "Nexus 1000v VSM Credentials"
+msgstr "Nexus 1000v VSM 凭证"
+
+# ff2a8c3138eb40fbbb40579586e678bf
+#: ../../hypervisor/vsphere.rst:450
+msgid "Ethernet port profile names"
+msgstr "以太网端口配置文件名称"
+
+# 4a63ecb799f24c29a04447e5da4130a5
+#: ../../hypervisor/vsphere.rst:454
+msgid "vCenter Credentials Checklist"
+msgstr "vCenter凭证清单"
+
+# 12069bcb02154859beac5cf397ecee61
+#: ../../hypervisor/vsphere.rst:456
+msgid "You will need the following information about vCenter:"
+msgstr "需要vCenter以下信息："
+
+# b2dc772426244f1f87b143366ecfd94a
+#: ../../hypervisor/vsphere.rst:459
+msgid "Nexus vSwitch Requirements"
+msgstr "Nexus vSwitch要求"
+
+# ca1d082b962346c5b7e77314fa8f5339
+#: ../../hypervisor/vsphere.rst:459
+msgid "Value"
+msgstr "值"
+
+# 3e9df2480b0d45c7a1888a94ab74b561
+#: ../../hypervisor/vsphere.rst:461
+msgid "vCenter IP"
+msgstr "vCenter IP"
+
+# 799d10a2870e4192b304caa3220a3c8c
+#: ../../hypervisor/vsphere.rst:461
+msgid "The IP address of the vCenter."
+msgstr "vCenter IP地址"
+
+# 373aace450dd4118b5260a922177871d
+#: ../../hypervisor/vsphere.rst:462
+msgid "Secure HTTP Port Number"
+msgstr "HTTPS端口号"
+
+# bf406db42c3b4a0985b822dc6f559fe9
+#: ../../hypervisor/vsphere.rst:462
+msgid "443"
+msgstr "443"
+
+# 78925de645d8445ab775646afbe88bac
+#: ../../hypervisor/vsphere.rst:462
+msgid ""
+"Port 443 is configured by default; however, you can change the port if "
+"needed."
+msgstr "默认配置使用443端口；如果需要，可以更改为其他端口。"
+
+# 7130dcb862384a349e76cb8cd106e8e2
+#: ../../hypervisor/vsphere.rst:463
+msgid "vCenter User ID"
+msgstr "vCenter用户ID"
+
+# 3c850f22d89f4e009b761127783ecdbd
+#: ../../hypervisor/vsphere.rst:463
+msgid ""
+"The vCenter user with administrator-level privileges. The vCenter User ID is"
+" required when you configure the virtual switch in CloudStack."
+msgstr "拥有管理员权限的vCenter用户。在CloudStack中配置虚拟交换时需要提供vCenter用户ID。"
+
+# 12125993392649a481f3650dc5288a6e
+# 0bd5bef46f9b4c6094ac26305cdfaa3f
+# aa87c00699724716b0aee7487275d581
+#: ../../hypervisor/vsphere.rst:465 ../../hypervisor/vsphere.rst:658
+#: ../../hypervisor/vsphere.rst:870
+msgid "vCenter Password"
+msgstr "vCenter 密码"
+
+# 0e4340b43fb04f7891cf7c7acc4ec52d
+#: ../../hypervisor/vsphere.rst:465
+msgid ""
+"The password for the vCenter user specified above. The password for this "
+"vCenter user is required when you configure the switch in CloudStack."
+msgstr "上述vCenter用户的密码。在CloudStack中配置虚拟交换机时需要提供vCenter用户密码。"
+
+# c78db2020a3c495b810c84656515f5a0
+#: ../../hypervisor/vsphere.rst:471
+msgid "Network Configuration Checklist"
+msgstr "网络配置清单"
+
+# 8685bc23de794287bde9bc32baf13f10
+#: ../../hypervisor/vsphere.rst:473
+msgid ""
+"The following information specified in the Nexus Configure Networking screen"
+" is displayed in the Details tab of the Nexus dvSwitch in the CloudStack UI:"
+msgstr "打开CloudStack管理界面，请在Nexus dvSwitchde 详情标签页中的Nexus 配置网络界面指定下列信息："
+
+# 5ecd7125924d4e3291abfd544471236f
+#: ../../hypervisor/vsphere.rst:477
+msgid ""
+"**Control Port Group VLAN ID** The VLAN ID of the Control Port Group. The "
+"control VLAN is used for communication between the VSM and the VEMs."
+msgstr ""
+
+# 5f52a9e500cc4927a981a052e73bac88
+#: ../../hypervisor/vsphere.rst:481
+msgid ""
+"**Management Port Group VLAN ID** The VLAN ID of the Management Port Group. "
+"The management VLAN corresponds to the mgmt0 interface that is used to "
+"establish and maintain the connection between the VSM and VMware vCenter "
+"Server."
+msgstr ""
+
+# 709fb407f7f7478ea5db1f47f795d42e
+#: ../../hypervisor/vsphere.rst:486
+msgid ""
+"**Packet Port Group VLAN ID** The VLAN ID of the Packet Port Group. The "
+"packet VLAN forwards relevant data packets from the VEMs to the VSM."
+msgstr ""
+
+# ee94ad5da5e44bd8a01b0a8b8d1f08f7
+#: ../../hypervisor/vsphere.rst:491
+msgid ""
+"The VLANs used for control, packet, and management port groups can be the "
+"same."
+msgstr "用于控制，数据和管理端口组可以在同一VLAN。"
+
+# 1d2af92735dc4899b13bb4fc697442f3
+#: ../../hypervisor/vsphere.rst:494
+msgid ""
+"For more information, see `Cisco Nexus 1000V Getting Started Guide "
+"<http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_b/getting_started/configuration/guide/n1000v_gsg.pdf>`_."
+msgstr "更多信息，请参考 `Cisco Nexus 1000V 入门指南 <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_b/getting_started/configuration/guide/n1000v_gsg.pdf>`_."
+
+# a9b85e88b0e54ef7bfa6227318fcadd8
+#: ../../hypervisor/vsphere.rst:499
+msgid "VSM Configuration Checklist"
+msgstr "VSM配置清单"
+
+# 409e4da026e84021900be9e9944f3530
+#: ../../hypervisor/vsphere.rst:501
+msgid "You will need the following VSM configuration parameters:"
+msgstr "你需要下列的VSM配置参数："
+
+# b2c7beaf3b174e24ae88c155d2eaf8bb
+#: ../../hypervisor/vsphere.rst:503
+msgid ""
+"**Admin Name and Password** The admin name and password to connect to the "
+"VSM appliance. You must specify these credentials while configuring Nexus "
+"virtual switch."
+msgstr ""
+
+# c42b39990d6e4d0589467d0a4ff5be4c
+#: ../../hypervisor/vsphere.rst:507
+msgid ""
+"**Management IP Address** This is the IP address of the VSM appliance. This "
+"is the IP address you specify in the virtual switch IP Address field while "
+"configuting Nexus virtual switch."
+msgstr ""
+
+# 26a1722f2c004284958a7d40035272d8
+#: ../../hypervisor/vsphere.rst:512
+msgid ""
+"**SSL** Should be set to Enable.Always enable SSL. SSH is usually enabled by"
+" default during the VSM installation. However, check whether the SSH "
+"connection to the VSM is working, without which CloudStack failes to connect"
+" to the VSM."
+msgstr ""
+
+# 62e601792f00490dbb068dab317eacb1
+#: ../../hypervisor/vsphere.rst:519
+msgid "Creating a Port Profile"
+msgstr "创建端口配置文件"
+
+# 4c8ad78e43824c658d06ce2ab03a001f
+#: ../../hypervisor/vsphere.rst:521
+msgid ""
+"Whether you create a Basic or Advanced zone configuration, ensure that you "
+"always create an Ethernet port profile on the VSM after you install it and "
+"before you create the zone."
+msgstr "无论创建简单或者高级区域，确保你总是在安装完VSM之后，创建区域之前，创建一个VSM的Ethernet配置文件。"
+
+# 7208a4d7c533445d986522ab1512d4bf
+#: ../../hypervisor/vsphere.rst:525
+msgid ""
+"The Ethernet port profile created to represent the physical network or "
+"networks used by an Advanced zone configuration trunk all the VLANs "
+"including guest VLANs, the VLANs that serve the native VLAN, and the "
+"packet/control/data/management VLANs of the VSM."
+msgstr "创建Ethernet端口配置文件用于表示物理网络或高级区域配置中trunk所有的VLANs网络，VLANs包括来宾网VLANs，本征VLAN以及VSM的数据/控制/管理VLANs。"
+
+# a8f769a137704cb5b1e211dbd40311d3
+#: ../../hypervisor/vsphere.rst:531
+msgid ""
+"The Ethernet port profile created for a Basic zone configuration does not "
+"trunk the guest VLANs because the guest VMs do not get their own VLANs "
+"provisioned on their network interfaces in a Basic zone."
+msgstr "为基础区域配置的Ethernet端口配置文件不会trunk来宾VLANs，因为在基础区域中，来宾VMs无法通过它们的网络接口获得所属的VLANs。"
+
+# e5eb4252f80244b298e78778099d1fc0
+#: ../../hypervisor/vsphere.rst:536
+msgid ""
+"An Ethernet port profile configured on the Nexus 1000v virtual switch should"
+" not use in its set of system VLANs, or any of the VLANs configured or "
+"intended to be configured for use towards VMs or VM resources in the "
+"CloudStack environment."
+msgstr "在Nexus 1000v虚拟交换机上配置的以太网端口配置文件，不应该使用在它的VLANS系统设置中，或者使用在其他任何VLANS配置以及打算使用在CloudStack环境中的虚拟机或者虚拟机资源的配置。"
+
+# d75d1e3b4d5e4861816052de95cd1077
+#: ../../hypervisor/vsphere.rst:541
+msgid ""
+"You do not have to create any vEthernet port profiles – CloudStack does that"
+" during VM deployment."
+msgstr "你无须创建任何vEthernet端口配置文件-CloudStack会在VM部署期间创建。"
+
+# defb84f8c1a843f49799fb10a14be23e
+#: ../../hypervisor/vsphere.rst:544
+msgid ""
+"Ensure that you create required port profiles to be used by CloudStack for "
+"different traffic types of CloudStack, such as Management traffic, Guest "
+"traffic, Storage traffic, and Public traffic. The physical networks "
+"configured during zone creation should have a one-to-one relation with the "
+"Ethernet port profiles."
+msgstr "请确保你为每种CloudStack流量类型创建了所需的端口配置文件，如管理流量，来宾流量，存储流量和公共流量。在区域创建期间配置的物理网络跟Ethernet应该是一一对应的关系。"
+
+# 0e5328f3a23c4e29bfca23e34fcf89e4
+#: ../../hypervisor/vsphere.rst:550
+msgid "|vmwarenexusportprofile.png: vSphere client|"
+msgstr "|vmwarenexusportprofile.png: vSphere client|"
+
+# 70e2a8e74f5a4a1f9e0541bf48f85614
+#: ../../hypervisor/vsphere.rst:552
+msgid ""
+"For information on creating a port profile, see `Cisco Nexus 1000V Port "
+"Profile Configuration Guide "
+"<http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_a/port_profile/configuration/guide/n1000v_port_profile.html>`_."
+msgstr "关于创建端口配置文件的更多信息，请参考 `Cisco Nexus 1000V 端口配置指南 <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_a/port_profile/configuration/guide/n1000v_port_profile.html>`_。"
+
+# 0bf9d88c6b9f41fd886a6707af18171a
+#: ../../hypervisor/vsphere.rst:558
+msgid "Assigning Physical NIC Adapters"
+msgstr "分配物理网络适配器"
+
+# af30a3508a1749d78432b57d276bbdb3
+#: ../../hypervisor/vsphere.rst:560
+msgid ""
+"Assign ESXi host's physical NIC adapters, which correspond to each physical "
+"network, to the port profiles. In each ESXi host that is part of the vCenter"
+" cluster, observe the physical networks assigned to each port profile and "
+"note down the names of the port profile for future use. This mapping "
+"information helps you when configuring physical networks during the zone "
+"configuration on CloudStack. These Ethernet port profile names are later "
+"specified as VMware Traffic Labels for different traffic types when "
+"configuring physical networks during the zone configuration. For more "
+"information on configuring physical networks, see `\"Configuring a vSphere "
+"Cluster with Nexus 1000v Virtual Switch\" <#configuring-a-vsphere-cluster-"
+"with-nexus-1000v-virtual-switch>`_."
+msgstr "分配ESXi主机上的对应每个物理网络的网卡适配器到端口配置文件。在vCenter群集中的每个ESXi主机上，观察分配到每个端口配置文件的物理网络并记下配置文件的名字。在创建zone期间，当你配置物理网络的时候，这个映射信息能帮助你。这些Ethernet端口配置文件的名字就是随后你在配置zone的时候，配置物理网络时所要输入的不同流量对应的VMware流量标签。配置物理网络所需的更多信息，请参考 `\"Configuring a vSphere Cluster with Nexus 1000v Virtual Switch\" <#configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch>`_。"
+
+# 4d643ffbee4341e4bb88d373ef58d4cb
+#: ../../hypervisor/vsphere.rst:574
+msgid "Adding VLAN Ranges"
+msgstr "添加VLAN范围"
+
+# baf83061abab4c29997a363586a2456f
+#: ../../hypervisor/vsphere.rst:576
+msgid ""
+"Determine the public VLAN, System VLAN, and Guest VLANs to be used by the "
+"CloudStack. Ensure that you add them to the port profile database. "
+"Corresponding to each physical network, add the VLAN range to port profiles."
+" In the VSM command prompt, run the switchport trunk allowed vlan<range> "
+"command to add the VLAN ranges to the port profile."
+msgstr "决定CloudStack所使用的公共VLAN，系统VLAN和来宾VLAN。确保你添加他们到端口配置文件数据库。对应每个物理网络，为端口配置文件添加VLAN范围。在VSM命令提示符下，运行 switchport trunk allowed vlan<range>命令为端口配置文件添加VLAN范围。"
+
+# a2316a806eeb4659aee14888d7a2fdac
+# 4709d5c62ddc4858afce5f4c10779904
+#: ../../hypervisor/vsphere.rst:582 ../../hypervisor/vsphere.rst:597
+msgid "For example:"
+msgstr "例如："
+
+# b6f0345378ec46c3b728d82ee05d286b
+#: ../../hypervisor/vsphere.rst:588
+msgid "In this example, the allowed VLANs added are 1, 140-147, and 196-203"
+msgstr "在这个示例下，添加的VLANs是1,140-147和196-203"
+
+# 11887130246943b5831c94500ad2baf5
+#: ../../hypervisor/vsphere.rst:590
+msgid ""
+"You must also add all the public and private VLANs or VLAN ranges to the "
+"switch. This range is the VLAN range you specify in your zone."
+msgstr "你同样在该交换机中添加所有的公共和管理VLANs或VLAN范围。这个范围是你在区域中指定的VLAN范围。"
+
+# 330d6aad437046f89b9b68dd7beeb679
+#: ../../hypervisor/vsphere.rst:594
+msgid ""
+"Before you run the vlan command, ensure that the configuration mode is "
+"enabled in Nexus 1000v virtual switch."
+msgstr "在你运行vlan命令之前，确保Nexus 1000v虚拟交换机中启用了配置模式。"
+
+# 22f63b04c60d40dea935e52d90e87e7e
+#: ../../hypervisor/vsphere.rst:599
+msgid ""
+"If you want the VLAN 200 to be used on the switch, run the following "
+"command:"
+msgstr "如果你想在交换机中使用VLAN 200，运行下面的命令："
+
+# ba4c025b07cf4124a3cdd1f31a23eb96
+#: ../../hypervisor/vsphere.rst:606
+msgid ""
+"If you want the VLAN range 1350-1750 to be used on the switch, run the "
+"following command:"
+msgstr "如果你想在交换机中使用VLAN范围1350-1750，请运行下面的命令："
+
+# c199b4ffbd1f477285c999898c2ddd1d
+#: ../../hypervisor/vsphere.rst:613
+msgid ""
+"Refer to Cisco Nexus 1000V Command Reference of specific product version."
+msgstr "参考特定产品版本的Cisco Nexus 1000V 命令参考。"
+
+# fef738594c2b491dba8d52bd4a2af5c6
+#: ../../hypervisor/vsphere.rst:618
+msgid "Enabling Nexus Virtual Switch in CloudStack"
+msgstr "在CloudStack中启用Nexus虚拟交换机。"
+
+# d5d3e75b340e49b59882b4fd17efbeee
+#: ../../hypervisor/vsphere.rst:620
+msgid ""
+"To make a CloudStack deployment Nexus enabled, you must set the "
+"vmware.use.nexus.vswitch parameter true by using the Global Settings page in"
+" the CloudStack UI. Unless this parameter is set to \"true\" and restart the"
+" management server, you cannot see any UI options specific to Nexus virtual "
+"switch, and CloudStack ignores the Nexus virtual switch specific parameters "
+"specified in the AddTrafficTypeCmd, UpdateTrafficTypeCmd, and AddClusterCmd "
+"API calls."
+msgstr "为了使CloudStack启用部署Nexus，你必须在CloudStack UI中全局设置页面设置vmware.use.nexus.vswitch参数为true。只有这个参数设置为 \"true\"并且重启了管理服务器，你才可以看见Nexus虚拟交换机的相关页面，CloudStack在AddTrafficTypeCmd, UpdateTrafficTypeCmd和 AddClusterCmd API的调用中会忽略Nexus虚拟交换机的指定参数。"
+
+# 66954393333444d693e53f7f88f33806
+#: ../../hypervisor/vsphere.rst:628
+msgid ""
+"Unless the CloudStack global parameter \"vmware.use.nexus.vswitch\" is set "
+"to \"true\", CloudStack by default uses VMware standard vSwitch for virtual "
+"network infrastructure. In this release, CloudStack doesn’t support "
+"configuring virtual networks in a deployment with a mix of standard vSwitch "
+"and Nexus 1000v virtual switch. The deployment can have either standard "
+"vSwitch or Nexus 1000v virtual switch."
+msgstr "除非CloudStack全局配置中的\"vmware.use.nexus.vswitch\"设置为\"true\"，否则CloudStack会默认使用VMware标准vSwitch。在本版本中，CloudStack不支持在标准vSwitch和Nexus 1000v虚拟交换机的混合环境中配置虚拟网络。只能支持单一的标准vSwitch或Nexus 1000v虚拟交换机部署。"
+
+# 089aca1a3d354287b5a5f5e3e85a6ac4
+#: ../../hypervisor/vsphere.rst:637
+msgid "Configuring Nexus 1000v Virtual Switch in CloudStack"
+msgstr "在CloudStack中配置Nexus 1000v虚拟交换机"
+
+# 9a68575001b243859acad74ffa452cb3
+#: ../../hypervisor/vsphere.rst:639
+msgid ""
+"You can configure Nexus dvSwitch by adding the necessary resources while the"
+" zone is being created."
+msgstr "可以在创建区域时，通过添加必要的资源用于配置Nexus dvSwitch。"
+
+# 08ba8e10fe624f36bab2f344bcbfdc6d
+#: ../../hypervisor/vsphere.rst:642
+msgid "|vmwarenexusaddcluster.png: vmware nexus add cluster|"
+msgstr "|vmwarenexusaddcluster.png: vmware nexus add cluster|"
+
+# 5666435e9e184603bfede5e1d03e45c9
+#: ../../hypervisor/vsphere.rst:644
+msgid ""
+"After the zone is created, if you want to create an additional cluster along"
+" with Nexus 1000v virtual switch in the existing zone, use the Add Cluster "
+"option. For information on creating a cluster, see `\"Add Cluster: vSphere\""
+" <configuration.html#add-cluster-vsphere>`_."
+msgstr "区域创建完成后，如果你想在区域中创建其他同样使用Nexus 1000v虚拟交换机的群集时，使用添加群集选项。关于创建群集的更多信息，请参见 `\"添加群集: vSphere\" <configuration.html#add-cluster-vsphere>`_。"
+
+# 9f2cbaf16fa54d839d9df5ead1a87d4a
+#: ../../hypervisor/vsphere.rst:649
+msgid ""
+"In both these cases, you must specify the following parameters to configure "
+"Nexus virtual switch:"
+msgstr "在所有的情况下，配置Nexus虚拟交换机时必须指定下列参数："
+
+# f3eae50b0b494bfe81d9c26c4d91d2f6
+#: ../../hypervisor/vsphere.rst:653
+msgid "Parameters"
+msgstr "参数"
+
+# 206d2e47feb14f26af5aa0ba5190283d
+#: ../../hypervisor/vsphere.rst:653
+msgid "Description"
+msgstr "描述"
+
+# f3ce0a1026ad443fb1d31fd83fb6fb89
+# d7c8e2c264fb4986bd9ae232d6bdc8da
+#: ../../hypervisor/vsphere.rst:655 ../../hypervisor/vsphere.rst:867
+msgid "Cluster Name"
+msgstr "群集名称"
+
+# ec69a6aaa2e74f97902c75e7e75e9414
+#: ../../hypervisor/vsphere.rst:655
+msgid ""
+"Enter the name of the cluster you created in vCenter. For "
+"example,\"cloud.cluster\"."
+msgstr "输入在vCenter中创建的群集名称。比如，\"cloud.cluster\"。"
+
+# c1336620763a40f5912677193b00e7d2
+# 5471d0cfd4dd4a1cad1890577ec16d27
+#: ../../hypervisor/vsphere.rst:656 ../../hypervisor/vsphere.rst:868
+msgid "vCenter Host"
+msgstr "vCenter 主机"
+
+# 83d4fc5d91a2434b8dbd5e459e856481
+#: ../../hypervisor/vsphere.rst:656
+msgid ""
+"Enter the host name or the IP address of the vCenter host where you have "
+"deployed the Nexus virtual switch."
+msgstr "输入已经部署了Nexus虚拟交换机的vCenter主机名或IP。"
+
+# a59ea53f5ed34aeeae67a62d22d9ef45
+# 50604ed2276e4b07a2245efe817a0e82
+#: ../../hypervisor/vsphere.rst:657 ../../hypervisor/vsphere.rst:869
+msgid "vCenter User name"
+msgstr "vCenter用户名"
+
+# 15cbe8d043134a98844515d429dc2ce4
+# 3d920505b2f94257aa4fae956cce9e60
+#: ../../hypervisor/vsphere.rst:657 ../../hypervisor/vsphere.rst:869
+msgid ""
+"Enter the username that CloudStack should use to connect to vCenter. This "
+"user must have all administrative privileges."
+msgstr "输入CloudStack连接到vCenter所使用的用户名。这个用户必须拥有所有管理员权限。"
+
+# 72ddd267d0934d71807a5b8f29fcc40b
+# 3d09dd4ec9ca450ab9b2843f5fe568f7
+#: ../../hypervisor/vsphere.rst:658 ../../hypervisor/vsphere.rst:870
+msgid "Enter the password for the user named above."
+msgstr "输入上面用户的密码。"
+
+# 3455a7e1a6ed43d9a04ca83e129c5605
+# 89d73f2b5187411dbeca10e98407d28a
+#: ../../hypervisor/vsphere.rst:659 ../../hypervisor/vsphere.rst:871
+msgid "vCenter Datacenter"
+msgstr "vCenter数据中心"
+
+# b8c64f99941045ba939c00ac64b8577e
+#: ../../hypervisor/vsphere.rst:659
+msgid ""
+"Enter the vCenter datacenter that the cluster is in. For example, "
+"\"cloud.dc.VM\"."
+msgstr "输入群集所属的vCenter数据中心名称。比如， \"cloud.dc.VM\"。"
+
+# 2e1f46464eb742eaa8decef9cc02ee1c
+#: ../../hypervisor/vsphere.rst:660
+msgid "Nexus dvSwitch IP Address"
+msgstr "Nexus dvSwitch IP 地址"
+
+# 0d935b2ec87d43d8ba91c44f85ab3926
+#: ../../hypervisor/vsphere.rst:660
+msgid "The IP address of the VSM component of the Nexus 1000v virtual switch."
+msgstr "Nexus 1000v虚拟交换机VSM组件的IP地址。"
+
+# 506b21479dd245b59972e5235fe090f8
+#: ../../hypervisor/vsphere.rst:661
+msgid "Nexus dvSwitch Username"
+msgstr "Nexus dvSwitch 用户名"
+
+# 51d92f490444448b97636510fda22234
+#: ../../hypervisor/vsphere.rst:661
+msgid "The admin name to connect to the VSM appliance."
+msgstr "连接至VSM appliance的admin名称。"
+
+# d1f48e314d0c4a60b778e89e3e5218c7
+#: ../../hypervisor/vsphere.rst:662
+msgid "Nexus dvSwitch Password"
+msgstr "Nexus dvSwitch 密码"
+
+# 2bf18eee4392452e9e2ce45d3f35ffdf
+#: ../../hypervisor/vsphere.rst:662
+msgid "The corresponding password for the admin user specified above."
+msgstr "上面指定的admin用户所对应的密码。"
+
+# cb27a7f0d42d41a5869093a5664932cc
+#: ../../hypervisor/vsphere.rst:667
+msgid "Removing Nexus Virtual Switch"
+msgstr "移除Nexus虚拟交换机"
+
+# 3661bb5b60a640dfb27da936b1ae3f3f
+#: ../../hypervisor/vsphere.rst:669
+msgid ""
+"In the vCenter datacenter that is served by the Nexus virtual switch, ensure"
+" that you delete all the hosts in the corresponding cluster."
+msgstr "在使用了Nexus虚拟交换机的vCenter数据中心中，确认你在对应的群集中删除了所有的主机。"
+
+# 72b8f0831f1840fba93593a47a3cb31d
+#: ../../hypervisor/vsphere.rst:672
+msgid "Log in with Admin permissions to the CloudStack administrator UI."
+msgstr "使用管理员登录到CloudStack管理界面。"
+
+# a6a80236805f46a289eaf13d946c887a
+#: ../../hypervisor/vsphere.rst:674
+msgid "In the left navigation bar, select Infrastructure."
+msgstr "在左侧导航栏中，选择基础架构。"
+
+# bf58c4e0621740cfa25ee56a211059e4
+#: ../../hypervisor/vsphere.rst:676
+msgid "In the Infrastructure page, click View all under Clusters."
+msgstr "在基础架构页面，点击群集中的查看所有。"
+
+# 5e2de301945c4c99a089b6d4ccbb97f5
+#: ../../hypervisor/vsphere.rst:678
+msgid "Select the cluster where you want to remove the virtual switch."
+msgstr "选择你想要移除虚拟交换机的群集。"
+
+# 8d08ef2d67b24e79a1fd91c3b5c80ac6
+#: ../../hypervisor/vsphere.rst:680
+msgid "In the dvSwitch tab, click the name of the virtual switch."
+msgstr "在dvSwitch标签页中，点击虚拟交换机的名字。"
+
+# e8ab3fb5e03a46a8806229a38548cd5e
+#: ../../hypervisor/vsphere.rst:682
+msgid ""
+"In the Details page, click Delete Nexus dvSwitch icon. |DeleteButton.png: "
+"button to delete dvSwitch|"
+msgstr "在详细页面中，点击删除Nexus dvSwitch的图标。 |DeleteButton.png: button to delete dvSwitch|"
+
+# dab3c1f885254b0d8a52701b537c16a1
+#: ../../hypervisor/vsphere.rst:685
+msgid "Click Yes in the confirmation dialog box."
+msgstr "在确认对话框中点击确定。"
+
+# 5c6a715aab294507b509f8b2c8510cd1
+#: ../../hypervisor/vsphere.rst:689
+msgid "Configuring a VMware Datacenter with VMware Distributed Virtual Switch"
+msgstr "配置VMware数据中心使用VMware分布式虚拟交换机"
+
+# 9929cd85206a4959b9c3daabc7fab873
+#: ../../hypervisor/vsphere.rst:691
+msgid ""
+"CloudStack supports VMware vNetwork Distributed Switch (VDS) for virtual "
+"network configuration in a VMware vSphere environment. This section helps "
+"you configure VMware VDS in a CloudStack deployment. Each vCenter server "
+"instance can support up to 128 VDS instances and each VDS instance can "
+"manage up to 500 VMware hosts."
+msgstr "CloudStack支持在VMware vSphere环境中为虚拟网络配置VMware vNetwork分布式交换机（VDS）。本章节能帮助你在CloudStack中配置VMware VDS。每个vCenter服务器实例最多支持128 VDS实例，每个VDS实例最多可以管理500台VMware服务器。"
+
+# 90d5b5ea40d340a18482d06a12eab802
+#: ../../hypervisor/vsphere.rst:699
+msgid "About VMware Distributed Virtual Switch"
+msgstr "关于VMware分布式虚拟交换机"
+
+# d608c0175d0c4cdda5a1cafa7067caab
+#: ../../hypervisor/vsphere.rst:701
+msgid ""
+"VMware VDS is an aggregation of host-level virtual switches on a VMware "
+"vCenter server. VDS abstracts the configuration of individual virtual "
+"switches that span across a large number of hosts, and enables centralized "
+"provisioning, administration, and monitoring for your entire datacenter from"
+" a centralized interface. In effect, a VDS acts as a single virtual switch "
+"at the datacenter level and manages networking for a number of hosts in a "
+"datacenter from a centralized VMware vCenter server. Each VDS maintains "
+"network runtime state for VMs as they move across multiple hosts, enabling "
+"inline monitoring and centralized firewall services. A VDS can be deployed "
+"with or without Virtual Standard Switch and a Nexus 1000V virtual switch."
+msgstr "在VMware vCenter服务器中的VMware VDS聚合主机层面虚拟交换机 。各个主机层面的虚拟交换机被抽象处理成一个在数据中心层面上横跨多个主机的大型 VDS，通过一个集中的接口，使用集中配置、管理、监控你的整个数据中心。实际上，VDS可以看作是数据中心层面中一个整体的虚拟交换机，通过VMware vCenter服务器管理数据中心中大量的主机网络。在虚拟机跨多个主机移动时保持其网络运行时状态，支持嵌入式监控和集中式防火墙服务。VDS能与标准虚拟交换机和 Nexus 1000V虚拟交换机一起部署或者独立部署。"
+
+# f8c27f93dc7c49a0b45ea450643011b8
+#: ../../hypervisor/vsphere.rst:717
+msgid ""
+"VMware VDS is supported only on Public and Guest traffic in CloudStack."
+msgstr "VMware VDS只支持CloudStack中的公共和来宾流量。"
+
+# 2451bd65c3414c12b60281d4c965ed9e
+#: ../../hypervisor/vsphere.rst:720
+msgid ""
+"VMware VDS does not support multiple VDS per traffic type. If a user has "
+"many VDS switches, only one can be used for Guest traffic and another one "
+"for Public traffic."
+msgstr "VMware VDS不支持每种流量类型使用多个VDS。如果一个用户有多个VDS交换机，那么来宾网络和公共网络只能各使用一个VDS。"
+
+# 1a4762ba91d54eb7b6a18b38c7977b88
+#: ../../hypervisor/vsphere.rst:724
+msgid ""
+"Additional switches of any type can be added for each cluster in the same "
+"zone. While adding the clusters with different switch type, traffic labels "
+"is overridden at the cluster level."
+msgstr "在同一个zone中可以为每个群集添加任何类型的交换机。当在群集中添加不同类型的交换机时，流量标签会被群集级别的覆盖。"
+
+# 698c3a1075c44ad6b44b983353e9c5bd
+#: ../../hypervisor/vsphere.rst:728
+msgid ""
+"Management and Storage network does not support VDS. Therefore, use Standard"
+" Switch for these networks."
+msgstr "管理和存储网络不支持使用VDS。因此在这些网络中使用标准交换机。"
+
+# d0e5f6fb89294c3f992992b8be90c4c3
+#: ../../hypervisor/vsphere.rst:731
+msgid ""
+"When you remove a guest network, the corresponding dvportgroup will not be "
+"removed on the vCenter. You must manually delete them on the vCenter."
+msgstr "当你移除来宾网络时，对应vCenter中的dv端口组不会被移除。你必须手动在vCenter中删除。"
+
+# d9ec908d24a74999a2250196f948e921
+#: ../../hypervisor/vsphere.rst:739
+msgid ""
+"For a smoother configuration of VMware VDS, note down the VDS name you have "
+"added in the datacenter before you start:"
+msgstr "为了顺利的配置VMware VDS，在开始之前，请牢记添加到数据中心中的VDS名称："
+
+# 0285bb1ef7114be98e589ae304a4aaf4
+#: ../../hypervisor/vsphere.rst:742
+msgid "|vds-name.png: Name of the dvSwitch as specified in the vCenter.|"
+msgstr "|vds-name.png: Name of the dvSwitch as specified in the vCenter.|"
+
+# a198446dde7b4bb4b8d32ade0d379e5d
+#: ../../hypervisor/vsphere.rst:744
+msgid "Use this VDS name in the following:"
+msgstr "如下需要使用VDS名称："
+
+# ce7a25d8824b439e989df3a4ec7d6ef4
+#: ../../hypervisor/vsphere.rst:746
+msgid ""
+"The switch name in the Edit traffic label dialog while configuring a public "
+"and guest traffic during zone creation."
+msgstr "在创建zone的过程中配置公共网络和来宾网络时，在编辑流量标签对话框中配置交换机名称。"
+
+# 93f0bed990174313b9ae6b524fe267f8
+#: ../../hypervisor/vsphere.rst:749
+msgid ""
+"During a zone creation, ensure that you select VMware vNetwork Distributed "
+"Virtual Switch when you configure guest and public traffic type."
+msgstr "在创建zone的过程中配置来宾网络和公共网络流量类型时，请确保你选择了VMware vNetwork Distributed Virtual Switch。"
+
+# 5c1aa18eab3146b6a6f65b96c8deaaca
+#: ../../hypervisor/vsphere.rst:753
+msgid "|traffic-type.png|"
+msgstr "|traffic-type.png|"
+
+# 990772b4742749958e08c6337b848941
+#: ../../hypervisor/vsphere.rst:755
+msgid ""
+"The Public Traffic vSwitch Type field when you add a VMware VDS-enabled "
+"cluster."
+msgstr "当添加一个启用了VDS的VMware群集时，则显示公共网络流量vSwitch类型区域。"
+
+# 5d9ac3f1d63b462e9501e015548b5af0
+#: ../../hypervisor/vsphere.rst:758
+msgid ""
+"The switch name in the traffic label while updating the switch type in a "
+"zone."
+msgstr "当在zone中更新交换机类型时，流量标签所使用的交换机名称。"
+
+# 194c1dd122b7499b9058fb68380a5c3b
+#: ../../hypervisor/vsphere.rst:761
+msgid ""
+"Traffic label format in the last case is [[\"Name of "
+"vSwitch/dvSwitch/EthernetPortProfile\"][,\"VLAN ID\"[,\"vSwitch Type\"]]]"
+msgstr "在最后一种情况下流量标签格式是[[\"Name of vSwitch/dvSwitch/EthernetPortProfile\"][,\"VLAN ID\"[,\"vSwitch Type\"]]]"
+
+# d4465ec982c94832ad7802b80686d0d1
+#: ../../hypervisor/vsphere.rst:764
+msgid "The possible values for traffic labels are:"
+msgstr "流量标签可以使用如下值："
+
+# 83829438bd2d4e5e81d7cea6cfdc2119
+#: ../../hypervisor/vsphere.rst:766
+msgid "empty string"
+msgstr "空字符串"
+
+# 089b868403e34bf385680a0275f453d9
+#: ../../hypervisor/vsphere.rst:768
+msgid "dvSwitch0"
+msgstr "dvSwitch0"
+
+# 8b132cc7e95e45b2927b570ef7790872
+#: ../../hypervisor/vsphere.rst:770
+msgid "dvSwitch0,200"
+msgstr "dvSwitch0,200"
+
+# f7e7251340ed4d489fd76000a902ab3e
+#: ../../hypervisor/vsphere.rst:772
+msgid "dvSwitch1,300,vmwaredvs"
+msgstr "dvSwitch1,300,vmwaredvs"
+
+# ffffef07a554452b989817589b59299f
+#: ../../hypervisor/vsphere.rst:774
+msgid "myEthernetPortProfile,,nexusdvs"
+msgstr "myEthernetPortProfile,,nexusdvs"
+
+# 374b8ec5b0114570a8bc2db1e26e1432
+#: ../../hypervisor/vsphere.rst:776
+msgid "dvSwitch0,,vmwaredvs"
+msgstr "dvSwitch0,,vmwaredvs"
+
+# e062d1b7e19e4a5ea9cd173bc474c7f9
+#: ../../hypervisor/vsphere.rst:779
+msgid "The three fields to fill in are:"
+msgstr "填写如下区域："
+
+# b665494425f24293b1cbd8c18d88376e
+#: ../../hypervisor/vsphere.rst:781
+msgid "Name of the virtual / distributed virtual switch at vCenter."
+msgstr "vCenter中 虚拟/分布式 虚拟交换机的名称。"
+
+# 64772a813ddb414aad487db7177d70d9
+#: ../../hypervisor/vsphere.rst:783
+msgid "The default value depends on the type of virtual switch:"
+msgstr "默认值取决于虚拟交换机的类型："
+
+# 0504f575abf04fbab918eb97fc3c23e5
+#: ../../hypervisor/vsphere.rst:785
+msgid ""
+"**vSwitch0**: If type of virtual switch is VMware vNetwork Standard virtual "
+"switch"
+msgstr "**vSwitch0**：如果虚拟交换机的类型是VMware vNetwork标准虚拟交换机。"
+
+# d037b0c2a7774a86950c4337ccb8c737
+#: ../../hypervisor/vsphere.rst:788
+msgid ""
+"**dvSwitch0**: If type of virtual switch is VMware vNetwork Distributed "
+"virtual switch"
+msgstr "**dvSwitch0**：如果虚拟交换机类型为VMware vNetwork分布式虚拟交换机"
+
+# b8bb2c95e98643c5a8416c7cacb4ed84
+#: ../../hypervisor/vsphere.rst:791
+msgid ""
+"**epp0**: If type of virtual switch is Cisco Nexus 1000v Distributed virtual"
+" switch"
+msgstr "**epp0**：如果虚拟交换机类型为Cisco Nexus 1000v分布式虚拟交换机"
+
+# 37bea26e77904c918293b7794b8435fe
+#: ../../hypervisor/vsphere.rst:794
+msgid "VLAN ID to be used for this traffic wherever applicable."
+msgstr "任何适用于这个流量的 VLAN ID"
+
+# 74cab27934ab4664a4ef799aaabc26fa
+#: ../../hypervisor/vsphere.rst:796
+msgid ""
+"This field would be used for only public traffic as of now. In case of guest"
+" traffic this field would be ignored and could be left empty for guest "
+"traffic. By default empty string would be assumed which translates to "
+"untagged VLAN for that specific traffic type."
+msgstr "此时，该区域仅用于公共网络流量。来宾网络区域会被忽略并且留空。默认为空字符即假设特定流量类型不填加VLAN标签。"
+
+# ecac63913296423c96e60c6fcd70b23c
+#: ../../hypervisor/vsphere.rst:801
+msgid "Type of virtual switch. Specified as string."
+msgstr "虚拟交换机类型。指定字符串。"
+
+# 736dcefb710d4eb8ad8ecdafc967ad7b
+#: ../../hypervisor/vsphere.rst:803
+msgid "Possible valid values are vmwaredvs, vmwaresvs, nexusdvs."
+msgstr "合理且有效的值为vmwaredvs, vmwaresvs, nexusdvs。"
+
+# 0ee50e36ae9a42ea93fad5da64772d2a
+#: ../../hypervisor/vsphere.rst:805
+msgid "**vmwaresvs**: Represents VMware vNetwork Standard virtual switch"
+msgstr "**vmwaresvs**：表示VMware vNetwork 标准虚拟交换机"
+
+# c3412e427322421db59d72ed3a1af1da
+#: ../../hypervisor/vsphere.rst:807
+msgid "**vmwaredvs**: Represents VMware vNetwork distributed virtual switch"
+msgstr "**vmwaredvs**：表示VMware vNetwork分布式虚拟交换机"
+
+# 86ab94faa29a4292811f32d8ef417a43
+#: ../../hypervisor/vsphere.rst:809
+msgid "**nexusdvs**: Represents Cisco Nexus 1000v distributed virtual switch."
+msgstr "**nexusdvs**：代表Cisco Nexus 1000v分布式虚拟交换机。"
+
+# b6c929f8a3d94c4ba2b89f14d3454074
+#: ../../hypervisor/vsphere.rst:811
+msgid ""
+"If nothing specified (left empty), zone-level default virtual switchwould be"
+" defaulted, based on the value of global parameter you specify."
+msgstr "如果什么都没指定(留空)，基于全局参数指定的值，区域层面默认使用虚拟交换机。"
+
+# 259ad555197c427b92b871cf9099c6e9
+#: ../../hypervisor/vsphere.rst:814
+msgid "Following are the global configuration parameters:"
+msgstr "以下为全局配置参数："
+
+# ba94337b1d8f418b9b792ff195a188b1
+#: ../../hypervisor/vsphere.rst:816
+msgid ""
+"**vmware.use.dvswitch**: Set to true to enable any kind (VMware DVS and "
+"Cisco Nexus 1000v) of distributed virtual switch in a CloudStack deployment."
+" If set to false, the virtual switch that can be used in that CloudStack "
+"deployment is Standard virtual switch."
+msgstr "**vmware.use.dvswitch**：设置为true则是在CloudStack部署时启用任意种类(VMware DVS和Cisco Nexus 1000v) 分布式交换机。如果设置为false，则CloudStack部署时使用的的虚拟交换机是标准虚拟交换机。"
+
+# 1f0d3c297b1b44caa71c066007cc1f42
+#: ../../hypervisor/vsphere.rst:821
+msgid ""
+"**vmware.use.nexus.vswitch**: This parameter is ignored if "
+"vmware.use.dvswitch is set to false. Set to true to enable Cisco Nexus 1000v"
+" distributed virtual switch in a CloudStack deployment."
+msgstr "**vmware.use.nexus.vswitch**：如果vmware.use.dvswitch设置为false，则忽略该参数。设置为true则是部署CloudStack时启用Cisco Nexus 1000v分布式交换机。"
+
+# 118ddca276544558a4e2202c55e634fd
+#: ../../hypervisor/vsphere.rst:827
+msgid "Enabling Virtual Distributed Switch in CloudStack"
+msgstr "在CloudStack中启用分布式虚拟交换机"
+
+# 82143bb642f94e2aa2cac07ffc264086
+#: ../../hypervisor/vsphere.rst:829
+msgid ""
+"To make a CloudStack deployment VDS enabled, set the vmware.use.dvswitch "
+"parameter to true by using the Global Settings page in the CloudStack UI and"
+" restart the Management Server. Unless you enable the vmware.use.dvswitch "
+"parameter, you cannot see any UI options specific to VDS, and CloudStack "
+"ignores the VDS-specific parameters that you specify. Additionally, "
+"CloudStack uses VDS for virtual network infrastructure if the value of "
+"vmware.use.dvswitch parameter is true and the value of "
+"vmware.use.nexus.dvswitch parameter is false. Another global parameter that "
+"defines VDS configuration is vmware.ports.per.dvportgroup. This is the "
+"default number of ports per VMware dvPortGroup in a VMware environment. "
+"Default value is 256. This number directly associated with the number of "
+"guest network you can create."
+msgstr "在部署CloudStack时启用VDS，请在CloudStack管理界面中的全局设置页面中设置vmware.use.dvswitch parameter为true并重启管理服务器。只有启用了vmware.use.dvswitch参数，你才能在管理界面中指定VDS，并且CloudStack会忽略你指定的VDS-specific参数。另外，如果vmware.use.dvswitch参数的值为true且vmware.use.nexus.dvswitch参数的值为false，那么CloudStack中虚拟网络架构使用VDS。另外一个定义VDS配置的全局参数是vmware.ports.per.dvportgroup。它表示在VMware环境里每个VMware dvPortGroup中默认端口数量。默认是256。这个数值直接关系到你创建的来宾网络的数量。"
+
+# 402c2275d5ad4f3797ca2a376401aee2
+#: ../../hypervisor/vsphere.rst:843
+msgid ""
+"CloudStack supports orchestration of virtual networks in a deployment with a"
+" mix of Virtual Distributed Switch, Standard Virtual Switch and Nexus 1000v "
+"Virtual Switch."
+msgstr "CloudStack支持混合部署分布式虚拟交换机、标准虚拟交换机和Nexus 1000v虚拟交换机的虚拟网络。"
+
+# 6811c0b0e8df461d9e2e43e42a23020c
+#: ../../hypervisor/vsphere.rst:849
+msgid "Configuring Distributed Virtual Switch in CloudStack"
+msgstr "在CloudStack中配置分布式虚拟交换机"
+
+# 8c7c27c152754a3496e49f3e867403e7
+#: ../../hypervisor/vsphere.rst:851
+msgid ""
+"You can configure VDS by adding the necessary resources while a zone is "
+"created."
+msgstr "在创建区域时需要添加必要的资源才能配置VDS。"
+
+# 5c9df8759a344053862dcd9c629277cf
+#: ../../hypervisor/vsphere.rst:854
+msgid ""
+"Alternatively, at the cluster level, you can create an additional cluster "
+"with VDS enabled in the existing zone. Use the Add Cluster option. For "
+"information as given in `“Add Cluster: vSphere” <configuration.html#add-"
+"cluster-vsphere>`_."
+msgstr "另外在群集层面，使用添加群集选项，可以在已经存在并启用VDS的区域中创建附加群集。更多信息请参阅 `“添加群集: vSphere” <configuration.html#add-cluster-vsphere>`_."
+
+# e0af0a758b7d4f03a1f5a83ae7e53aca
+#: ../../hypervisor/vsphere.rst:859
+msgid ""
+"In both these cases, you must specify the following parameters to configure "
+"VDS:"
+msgstr "在所有情况下，配置VDS时必须指定下列参数："
+
+# 68137fa71ec145fc8a3dbdc1dde90e0a
+#: ../../hypervisor/vsphere.rst:862
+msgid "|dvSwitchConfig.png: Configuring dvSwitch|"
+msgstr "|dvSwitchConfig.png: Configuring dvSwitch|"
+
+# c44708acf56642f6bdc0e41399c84ccc
+#: ../../hypervisor/vsphere.rst:865
+msgid "Parameters Description"
+msgstr "参数描述"
+
+# e9d2fae4cc094bf29e7470348646862a
+#: ../../hypervisor/vsphere.rst:867
+msgid ""
+"Enter the name of the cluster you created in vCenter. For example, "
+"\"cloudcluster\"."
+msgstr "输入在vCenter中创建的群集名称。比如，\"cloudcluster\"。"
+
+# 2eb58724f9dc40b78cb1261c45a8425a
+#: ../../hypervisor/vsphere.rst:868
+msgid ""
+"Enter the name or the IP address of the vCenter host where you have deployed"
+" the VMware VDS."
+msgstr "输入已经部署VMware VDS的vCenter主机名称或者IP地址。"
+
+# 64ad16bd9476459999c67afeec2a76cd
+#: ../../hypervisor/vsphere.rst:871
+msgid ""
+"Enter the vCenter datacenter that the cluster is in. For example, "
+"\"clouddcVM\"."
+msgstr "输入群集所属的vCenter数据中心名称。比如，\"clouddcVM\"。"
+
+# 519c5255a7714ab5ae2d130ea2ac0b09
+#: ../../hypervisor/vsphere.rst:872
+msgid "Override Public Traffic"
+msgstr "替代公共流量"
+
+# 834881d8791d4560ba8fcba7d3478f6d
+#: ../../hypervisor/vsphere.rst:872
+msgid ""
+"Enable this option to override the zone-wide public traffic for the cluster "
+"you are creating."
+msgstr "启用该选项时，整个区域中群集的公共流量将被替代。"
+
+# 380dfef8c1844f399f2cbd5c09d3e6ee
+#: ../../hypervisor/vsphere.rst:873
+msgid "Public Traffic vSwitch Type"
+msgstr "公共流量虚拟交换机类型"
+
+# 444137a9e330418b808e55cf02a62e97
+#: ../../hypervisor/vsphere.rst:873
+msgid ""
+"This option is displayed only if you enable the Override Public Traffic "
+"option. Select VMware vNetwork Distributed Virtual Switch. If the "
+"vmware.use.dvswitch global parameter is true, the default option will be "
+"VMware vNetwork Distributed Virtual Switch."
+msgstr "在启用替代公共流量时该选项才会显示。选择VMware vNetwork Distributed Virtual Switch。如果全局设置中vmware.use.dvswitch参数为true，则默认选项为VMware vNetwork Distributed Virtual Switch。"
+
+# 5396ef53dbdc46828b829c10118c7ca9
+#: ../../hypervisor/vsphere.rst:874
+msgid "Public Traffic vSwitch Name"
+msgstr "公共流量虚拟交换机名称"
+
+# 8d69112f1cb240ed98549493d13e6775
+#: ../../hypervisor/vsphere.rst:874
+msgid "Name of virtual switch to be used for the public traffic."
+msgstr "用于公共流量的虚拟交换机名称。"
+
+# 08c372cbcf0c4ae2a6bf96d5b5877d5f
+#: ../../hypervisor/vsphere.rst:875
+msgid "Override Guest Traffic"
+msgstr "替代来宾流量"
+
+# bfb400fd3046492f9c0e679af6725e95
+#: ../../hypervisor/vsphere.rst:875
+msgid ""
+"Enable the option to override the zone-wide guest traffic for the cluster "
+"you are creating."
+msgstr "启用该选项时，整个区域中群集的来宾流量将被替代。"
+
+# c393048d168a4e74851ea171593bff47
+#: ../../hypervisor/vsphere.rst:876
+msgid "Guest Traffic vSwitch Type"
+msgstr "来宾流量虚拟交换机类型"
+
+# 20a6787434c649b8b9804b209e8217d9
+#: ../../hypervisor/vsphere.rst:876
+msgid ""
+"This option is displayed only if you enable the Override Guest Traffic "
+"option. Select VMware vNetwork Distributed Virtual Switch. If the "
+"vmware.use.dvswitch global parameter is true, the default option will be "
+"VMware vNetwork Distributed Virtual Switch."
+msgstr "在启用替代来宾流量时该选项才会显示。选择VMware vNetwork Distributed Virtual Switch。如果全局设置中vmware.use.dvswitch参数为true，则默认选项为VMware vNetwork Distributed Virtual Switch。"
+
+# 8e911ae658a54e38bc94d44bd7360a60
+#: ../../hypervisor/vsphere.rst:877
+msgid "Guest Traffic vSwitch Name"
+msgstr "来宾流量虚拟交换机名称"
+
+# e2fef73d36884fc18391b02ba8492fed
+#: ../../hypervisor/vsphere.rst:877
+msgid "Name of virtual switch to be used for guest traffic."
+msgstr "用于宾流量的虚拟交换机名称。"
+
+# fdd69bb3d44f4bcd9f56db1a98842617
+#: ../../hypervisor/vsphere.rst:882
+msgid "Storage Preparation for vSphere (iSCSI only)"
+msgstr "vSphere的存储准备(仅限iSCSI)"
+
+# 8617abba6dbc4534ad13b17929bb8816
+#: ../../hypervisor/vsphere.rst:884
+msgid ""
+"Use of iSCSI requires preparatory work in vCenter. You must add an iSCSI "
+"target and create an iSCSI datastore."
+msgstr "使用iSCSI需要在vCenter中做一些准备工作。您必须添加iSCSI目标并创建iSCSI数据存储。"
+
+# cd8def1af119474099d424fa51348782
+#: ../../hypervisor/vsphere.rst:887
+msgid "If you are using NFS, skip this section."
+msgstr "如果使用NFS，请跳过本章节。"
+
+# 965c53dfd68549dcb2ff3d7b6f5b8ef6
+#: ../../hypervisor/vsphere.rst:891
+msgid "Enable iSCSI initiator for ESXi hosts"
+msgstr "ESXi主机中启用iSCSI启动器"
+
+# f31d653b97a34904bba9418166f4d27f
+#: ../../hypervisor/vsphere.rst:893
+msgid ""
+"In vCenter, go to hosts and Clusters/Configuration, and click Storage "
+"Adapters link. You will see:"
+msgstr "在vCenter中，点击主机/集群的配置，点击存储适配器。您将看到："
+
+# c2db82b7ad84447c90bc1361acb6fe26
+#: ../../hypervisor/vsphere.rst:896
+msgid "|vmwareiscsiinitiator.png: iscsi initiator|"
+msgstr "|vmwareiscsiinitiator.png: iscsi initiator|"
+
+# b0f077089acc4b47bc0e81c18ef873bc
+#: ../../hypervisor/vsphere.rst:898
+msgid "Select iSCSI software adapter and click Properties."
+msgstr "选择iSCSI软件适配器并点击属性。"
+
+# 5ff6af603a254d62a64459f283531878
+#: ../../hypervisor/vsphere.rst:900
+msgid "|vmwareiscsiinitiatorproperties.png: iscsi initiator properties|"
+msgstr "|vmwareiscsiinitiatorproperties.png: iscsi initiator properties|"
+
+# 4fc6bd69f5a74997a26a8ed8ff4a635d
+#: ../../hypervisor/vsphere.rst:902
+msgid "Click the Configure... button."
+msgstr "点击配置...按钮。"
+
+# d1a7febad60a4c72a88effb69663d334
+#: ../../hypervisor/vsphere.rst:904
+msgid "|vmwareiscsigeneral.png: iscsi general|"
+msgstr "|vmwareiscsigeneral.png: iscsi general|"
+
+# b542942a98b04d3fb1009c9cfbeea698
+#: ../../hypervisor/vsphere.rst:906
+msgid "Check Enabled to enable the initiator."
+msgstr "勾选启用以便启用启动器。"
+
+# 426af842784e4c0bb8e14ec9948ff60c
+#: ../../hypervisor/vsphere.rst:908
+msgid "Click OK to save."
+msgstr "点击 确定 保存。"
+
+# 668e7a8543bd45448ad0db8ae303bfc0
+#: ../../hypervisor/vsphere.rst:912
+msgid "Add iSCSI target"
+msgstr "添加iSCSI目标"
+
+# 8c293602e55f48578e49ba85c6b7bc72
+#: ../../hypervisor/vsphere.rst:914
+msgid "Under the properties dialog, add the iSCSI target info:"
+msgstr "在属性对话框中，添加iSCSI目标信息："
+
+# ca9d056dfd584f658d8c3561ca8e94ac
+#: ../../hypervisor/vsphere.rst:916
+msgid "|vmwareiscsitargetadd.png: iscsi target add|"
+msgstr "|vmwareiscsitargetadd.png: iscsi target add|"
+
+# 48e3de1952584a7f83fdb8878b2e3309
+#: ../../hypervisor/vsphere.rst:918
+msgid "Repeat these steps for all ESXi hosts in the cluster."
+msgstr "在集群中所有ESXi主机上重复以上步骤。"
+
+# 5b7a2a4bd27d4e45ab60e0356f72d8a0
+#: ../../hypervisor/vsphere.rst:922
+msgid "Create an iSCSI datastore"
+msgstr "创建iSCSI数据存储"
+
+# 6e4943dc8eb04b0b839ba66174f1a7f7
+#: ../../hypervisor/vsphere.rst:924
+msgid "You should now create a VMFS datastore. Follow these steps to do so:"
+msgstr "现在您应该创建一个VMFS数据存储。请按照以下步骤："
+
+# 57cc6fe8445d4065b6d918ab122558aa
+#: ../../hypervisor/vsphere.rst:926
+msgid "Select Home/Inventory/Datastores."
+msgstr "选择主页/清单/数据存储。"
+
+# 0c8e6407c16c420c8ab924f07074c3f0
+#: ../../hypervisor/vsphere.rst:928
+msgid "Right click on the datacenter node."
+msgstr "右键点击数据中心节点。"
+
+# 33637d5c54c84c10bd4fddce9500d1db
+#: ../../hypervisor/vsphere.rst:930
+msgid "Choose Add Datastore... command."
+msgstr "选择添加数据存储...命令。"
+
+# 10b59ee6f67f4fe18245206491765fa2
+#: ../../hypervisor/vsphere.rst:932
+msgid "Follow the wizard to create a iSCSI datastore."
+msgstr "按照向导创建iSCSI数据存储。"
+
+# beb1bd72d9054c1aa2929c5f5bb46268
+#: ../../hypervisor/vsphere.rst:934
+msgid ""
+"This procedure should be done on one host in the cluster. It is not "
+"necessary to do this on all hosts."
+msgstr "该过程只需要在集群中的一台主机上执行，不需要在所有主机上执行。"
+
+# fddbde67076a489fae8ac3a07ba72a4e
+#: ../../hypervisor/vsphere.rst:937
+msgid "|vmwareiscsidatastore.png: iscsi datastore|"
+msgstr "|vmwareiscsidatastore.png: iscsi datastore|"
+
+# 720bb6a6678e4d048a7cb2fb20b5f00f
+#: ../../hypervisor/vsphere.rst:941
+msgid "Multipathing for vSphere (Optional)"
+msgstr "vSphere多路径(可选)"
+
+# f6110e7830f74e37b59a9ed7e75cc697
+#: ../../hypervisor/vsphere.rst:943
+msgid ""
+"Storage multipathing on vSphere nodes may be done according to the vSphere "
+"installation guide."
+msgstr "vSphere的存储多路径可以根据vSphere的安装文档配置。"
+
+# 90bf6e714b424e1cb0f0727e69bd91bd
+#: ../../hypervisor/vsphere.rst:948
+msgid "Add Hosts or Configure Clusters (vSphere)"
+msgstr "添加主机或配置集群(vSphere)"
+
+# 34c741b108a3471086a9877f848c219a
+#: ../../hypervisor/vsphere.rst:950
+msgid ""
+"Use vCenter to create a vCenter cluster and add your desired hosts to the "
+"cluster. You will later add the entire cluster to CloudStack. (see `“Add "
+"Cluster: vSphere” <configuration.html#add-cluster-vsphere>`_)."
+msgstr "使用vCenter创建集群，向其中添加期望的主机。随后您可以将整个集群加入到Cloudstack中。(参考 `“添加群集: vSphere” <configuration.html#add-cluster-vsphere>`_)。"
+
+# e222980c86f646a6b7847d19c943d01e
+#: ../../hypervisor/vsphere.rst:956
+msgid "Applying Hotfixes to a VMware vSphere Host"
+msgstr "为VMware vSphere主机安装补丁程序"
+
+# afbce7caade34557b5de0efd81ac8337
+#: ../../hypervisor/vsphere.rst:958
+msgid ""
+"Disconnect the VMware vSphere cluster from CloudStack. It should remain "
+"disconnected long enough to apply the hotfix on the host."
+msgstr "在CloudStack中断开与VMware vSphere 群集的连接。应断开足够长的时间以便在主机上安装补丁程序。"
+
+# c3e9304bebf74cec95280a42ff6c47bc
+# 93ca13f83e884aa6bc68dca551cd9c85
+#: ../../hypervisor/vsphere.rst:961 ../../hypervisor/vsphere.rst:989
+msgid "Log in to the CloudStack UI as root."
+msgstr "使用admin账户登录CloudStack管理界面。"
+
+# ae093003e8e54de3bd3685570562d010
+#: ../../hypervisor/vsphere.rst:963
+msgid ""
+"See `“Log In to the UI” <http://docs.cloudstack.apache.org/projects"
+"/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_."
+msgstr "请参考 `“登录用户界面” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_。"
+
+# ab2de97e73f842718ecd3a5c0517a46f
+#: ../../hypervisor/vsphere.rst:966
+msgid "Navigate to the VMware cluster, click Actions, and select Unmanage."
+msgstr "导航至VMware群集，点击操作-取消管理。"
+
+# 291849fb997541a392eb9c265469db83
+#: ../../hypervisor/vsphere.rst:969
+msgid "Watch the cluster status until it shows Unmanaged."
+msgstr "查看群集状态直到显示未受管理。"
+
+# d36d95821f7349bdbeb6146d69609d26
+#: ../../hypervisor/vsphere.rst:971
+msgid "Perform the following on each of the ESXi hosts in the cluster:"
+msgstr "在集群中每个ESXi主机上执行以下操作："
+
+# 1596207414164387b33d50a83ace4f1d
+#: ../../hypervisor/vsphere.rst:973
+msgid "Move each of the ESXi hosts in the cluster to maintenance mode."
+msgstr "将集群中每个ESXi都置为维护模式。"
+
+# 0f443a13d2214787aace57dbe095be32
+#: ../../hypervisor/vsphere.rst:975
+msgid "Ensure that all the VMs are migrated to other hosts in that cluster."
+msgstr "确保所有的VM已经迁移到群集中的其他主机。"
+
+# 993a0bfff5d949d79160c8a611af7d45
+#: ../../hypervisor/vsphere.rst:978
+msgid ""
+"If there is only one host in that cluster, shutdown all the VMs and move the"
+" host into maintenance mode."
+msgstr "如果群集中只有一台主机，关闭所有VMs再将主机置为维护模式。"
+
+# 549ba78fd15b49e081bd0e3212261dc1
+#: ../../hypervisor/vsphere.rst:981
+msgid "Apply the patch on the ESXi host."
+msgstr "在ESXi主机中应用补丁。"
+
+# c7418a0d9f414399a6e7b5d7281c5cd5
+#: ../../hypervisor/vsphere.rst:983
+msgid "Restart the host if prompted."
+msgstr "如果提示重启，请重启主机。"
+
+# 7882f2dc5f704ad2a2ae6b6fe2ef0fb0
+#: ../../hypervisor/vsphere.rst:985
+msgid "Cancel the maintenance mode on the host."
+msgstr "在主机上取消维护模式。"
+
+# 27eaeff783e845fba9f5550da792fe4d
+#: ../../hypervisor/vsphere.rst:987
+msgid "Reconnect the cluster to CloudStack:"
+msgstr "重新连接该集群到CloudStack:"
+
+# dafd6eb321c643db98f259663c789c70
+#: ../../hypervisor/vsphere.rst:991
+msgid "Navigate to the VMware cluster, click Actions, and select Manage."
+msgstr "导航到VMware群集，点击操作-管理。"
+
+# bdbbffe72d294cdbadc09334b9549fdb
+#: ../../hypervisor/vsphere.rst:993
+msgid ""
+"Watch the status to see that all the hosts come up. It might take several "
+"minutes for the hosts to come up."
+msgstr "查看状态以确保所有的主机都恢复正常。所有主机都恢复正常可能需要几分钟时间。"
+
+# 61accad423f64d2b90044cac762efc57
+#: ../../hypervisor/vsphere.rst:996
+msgid ""
+"Alternatively, verify the host state is properly synchronized and updated in"
+" the CloudStack database."
+msgstr "或者，确认主机状态在数据库中得到正确同步和更新。"
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/xenserver.mo b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/xenserver.mo
new file mode 100644
index 0000000..ee1f70e
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/xenserver.mo
Binary files differ
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/xenserver.po b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/xenserver.po
new file mode 100644
index 0000000..d87ecf4
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor/xenserver.po
@@ -0,0 +1,1237 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: 2014-06-30 10:27+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# dbca5e0c19df40c290465114f3559dec
+#: ../../hypervisor/xenserver.rst:18
+msgid "Citrix XenServer Installation for CloudStack"
+msgstr "为CloudStack安装Citrix XenServer"
+
+# cd47a83746ac418dbc9077979249b7da
+#: ../../hypervisor/xenserver.rst:20
+msgid ""
+"If you want to use the Citrix XenServer hypervisor to run guest virtual "
+"machines, install XenServer 6.0 or XenServer 6.0.2 on the host(s) in your "
+"cloud. For an initial installation, follow the steps below. If you have "
+"previously installed XenServer and want to upgrade to another version, see "
+":ref:`upgrading-xenserver-version`."
+msgstr "如果你想用Citrix XenServer作为hypervisor运行虚拟机，安装XenServer 6.0或XenServer 6.0.2版本。你需要按照以下步骤来完成初次安装。如果你想从之前的旧版本升级，请参阅 :ref:`upgrading-xenserver-version`。"
+
+# d9ee0495584b4a8298e517da8fdc3057
+#: ../../hypervisor/xenserver.rst:28
+msgid "System Requirements for XenServer Hosts"
+msgstr "XenServer主机的系统要求"
+
+# 3d5008ea44354966853d8d381ed7891a
+#: ../../hypervisor/xenserver.rst:30
+msgid ""
+"The host must be certified as compatible with one of the following. See the "
+"Citrix Hardware Compatibility Guide: `http://hcl.xensource.com "
+"<http://hcl.xensource.com>`_"
+msgstr "主机必须通过下列任一版本的兼容性认证。请查看Citrix硬件兼容性指导: `http://hcl.xensource.com <http://hcl.xensource.com>`_"
+
+# 8314770679cb4bc99d30a72aef396428
+#: ../../hypervisor/xenserver.rst:34
+msgid "XenServer 5.6 SP2"
+msgstr "XenServer 5.6 SP2"
+
+# 24946ee9574b4a6791b00328377a2b5a
+#: ../../hypervisor/xenserver.rst:35
+msgid "XenServer 6.0"
+msgstr "XenServer 6.0"
+
+# 7c1b9ee9639c4610aad50db7807788f8
+#: ../../hypervisor/xenserver.rst:36
+msgid "XenServer 6.0.2"
+msgstr "XenServer 6.0.2"
+
+# 9baf931e48934c4c8c54669d292e0f87
+#: ../../hypervisor/xenserver.rst:37
+msgid "XenServer 6.1.0"
+msgstr "XenServer 6.1.0"
+
+# 7ee33d4c2fd7471fafb3a3bcb6352a7e
+#: ../../hypervisor/xenserver.rst:38
+msgid "XenServer 6.2.0"
+msgstr "XenServer 6.2.0"
+
+# 5dee06ed5f2f472f9e0979ddbb241a63
+#: ../../hypervisor/xenserver.rst:40
+msgid ""
+"You must re-install Citrix XenServer if you are going to re-use a host from "
+"a previous install."
+msgstr "如果你想使用以前装的某台主机,你必须重新安装Citrix XenServer."
+
+# 80cb092fd1e84cd48850208d4ba0bbf5
+#: ../../hypervisor/xenserver.rst:43
+msgid "Must support HVM (Intel-VT or AMD-V enabled)"
+msgstr "必须支持HVM(Intel-VT或者AMD-V)"
+
+# bab4879deea84fe697e8b924ffd8fb1c
+#: ../../hypervisor/xenserver.rst:45
+msgid ""
+"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."
+msgstr "确保安装了所有系统补丁供应商提供的所有系统补丁。请随时关注供应商的技术支持渠道，一旦发布补丁，请尽快打上补丁。CloudStack不会跟踪或提醒你安装这些程序。安装最新的补丁对主机至关重要。虚拟化供应商可能不会对过期的系统提供技术支持。"
+
+# 7be511b75f274a11877a89c4e5b4442a
+#: ../../hypervisor/xenserver.rst:54
+msgid ""
+"All hosts within a cluster must be homogeneous. The CPUs must be of the same"
+" type, count, and feature flags."
+msgstr "集群中的主机必须是相同架构。CPU的型号、数量和功能参数必须相同。"
+
+# f1598069d3724215b893587629e5a745
+#: ../../hypervisor/xenserver.rst:57
+msgid "Must support HVM (Intel-VT or AMD-V enabled in BIOS)"
+msgstr "必须支持HVM（BIOS中要打开Intel-VT或者AMD-V）"
+
+# 136e934524c54e44a1dc5daa197a36c1
+#: ../../hypervisor/xenserver.rst:59
+msgid "64-bit x86 CPU (more cores results in better performance)"
+msgstr "64位x86 CPU(多核性能更佳)"
+
+# a06b5cab48ca4c9d86747442230f0613
+#: ../../hypervisor/xenserver.rst:61
+msgid "Hardware virtualization support required"
+msgstr "硬件虚拟化支持"
+
+# 3d9b7de9d5cb4e629ef6589132428cb0
+#: ../../hypervisor/xenserver.rst:63
+msgid "4 GB of memory"
+msgstr "4GB 内存"
+
+# e3a33fc842e74c2191c11b46d1e11d6e
+#: ../../hypervisor/xenserver.rst:65
+msgid "36 GB of local disk"
+msgstr "36GB本地磁盘空间"
+
+# a7120f278e3a48f7a1957e666d4539fc
+#: ../../hypervisor/xenserver.rst:67
+msgid "At least 1 NIC"
+msgstr "至少一块网卡"
+
+# a2ea178b475547d899a7a72ae1ae9761
+#: ../../hypervisor/xenserver.rst:69
+msgid "Statically allocated IP Address"
+msgstr "静态分配的IP"
+
+# 829b6839c66d461b9f1692bb1a42e0a3
+#: ../../hypervisor/xenserver.rst:71
+msgid ""
+"When you deploy CloudStack, the hypervisor host must not have any VMs "
+"already running"
+msgstr "在部署CloudStack时，Hypervisor主机不能运行任何虚拟机"
+
+# 593acf4d53964830be70c33d03648380
+#: ../../hypervisor/xenserver.rst:75
+msgid ""
+"The lack of up-do-date hotfixes can lead to data corruption and lost VMs."
+msgstr "缺乏最新补丁更新可能会导致数据和虚拟机丢失。"
+
+# 10efea9818be4d9fb0c4a1f8128f964e
+#: ../../hypervisor/xenserver.rst:79
+msgid "XenServer Installation Steps"
+msgstr "XenServer安装步骤"
+
+# a2c7219af86147eeab5c37bd51222363
+#: ../../hypervisor/xenserver.rst:81
+msgid ""
+"From `https://www.citrix.com/English/ss/downloads/ "
+"<https://www.citrix.com/English/ss/downloads/>`_, download the appropriate "
+"version of XenServer for your CloudStack version (see `\"System Requirements"
+" for XenServer Hosts\" <#system-requirements-for-xenserver-hosts>`_). "
+"Install it using the Citrix XenServer Installation Guide."
+msgstr " 从 `https://www.citrix.com/English/ss/downloads/ <https://www.citrix.com/English/ss/downloads/>`_下载适合CloudStack的XenServer版本 (查看 `\"XenServer主机的系统要求\" <#system-requirements-for-xenserver-hosts>`_)。使用XenServer安装向导安装XenServer。"
+
+# 48628175cf1b4e66a6889e16ec013033
+#: ../../hypervisor/xenserver.rst:88
+msgid "Older Versions of XenServer:"
+msgstr "较旧版本的XenServer："
+
+# b9b29c0fa89c4656ab70adbb2a99e673
+#: ../../hypervisor/xenserver.rst:90
+msgid ""
+"Note that you can download the most recent release of XenServer without "
+"having a Citrix account. If you wish to download older versions, you will "
+"need to create an account and look through the download archives."
+msgstr "下载最新版本的XenServer不需要使用Citrix账户。如果你要下载旧版本的XenServer，你需要注册一个账户。"
+
+# 2feb5a48073c4e2e9fe034ed56a4384d
+#: ../../hypervisor/xenserver.rst:97
+msgid "Configure XenServer dom0 Memory"
+msgstr "配置XenServer dom0内存"
+
+# 07ce15cab19948cc8331905b67b44d32
+#: ../../hypervisor/xenserver.rst:99
+msgid ""
+"Configure the XenServer dom0 settings to allocate more memory to dom0. This "
+"can enable XenServer to handle larger numbers of virtual machines. We "
+"recommend 2940 MB of RAM for XenServer dom0. For instructions on how to do "
+"this, see `http://support.citrix.com/article/CTX126531 "
+"<http://support.citrix.com/article/CTX126531>`_. The article refers to "
+"XenServer 5.6, but the same information applies to XenServer 6.0."
+msgstr "配置XenServer dom0占用更大的内存可以使XenServer运行更多的虚拟机。我们建议修改为2940MB。如何来做这些更改，请看 `http://support.citrix.com/article/CTX126531 <http://support.citrix.com/article/CTX126531>`_。这篇文档是针对XenServer 5.6的，但同样适用于XenServer6.0。"
+
+# 5e0c0f29a1814ea5875442853353fe5e
+#: ../../hypervisor/xenserver.rst:108
+msgid "Username and Password"
+msgstr "用户名和密码"
+
+# 6f2532ac7db843db93d53f391ae6d733
+#: ../../hypervisor/xenserver.rst:110
+msgid ""
+"All XenServers in a cluster must have the same username and password as "
+"configured in CloudStack."
+msgstr "CloudStack中同一群集下的所有XenServer主机必须拥有同样的用户名和密码。"
+
+# 941b9509be3746249f736aec017baf1f
+#: ../../hypervisor/xenserver.rst:115
+msgid "Time Synchronization"
+msgstr "时间同步"
+
+# 0a006397adbf45fd9e71c3dc58c59a20
+#: ../../hypervisor/xenserver.rst:117
+msgid ""
+"The host must be set to use NTP. All hosts in a pod must have the same time."
+msgstr "主机必须配置NTP。同一提供点中的所有主机时间必须相同。"
+
+# 17ff16e49de74a14a14e94a5e972d414
+#: ../../hypervisor/xenserver.rst:120
+msgid "Install NTP."
+msgstr "安装NTP."
+
+# 6fa27a22869648db88edf8eed39beca0
+#: ../../hypervisor/xenserver.rst:126
+msgid "Edit the NTP configuration file to point to your NTP server."
+msgstr "编辑NTP配置文件指定NTP服务器。"
+
+# 0536cc30cd854673bfb3aacf080a0fc6
+#: ../../hypervisor/xenserver.rst:132
+msgid ""
+"Add one or more server lines in this file with the names of the NTP servers "
+"you want to use. For example:"
+msgstr "在文件中添加一行或多行你想使用的服务器地址. 例如:"
+
+# 8ed85f477b5d41d584b84da677111ac8
+#: ../../hypervisor/xenserver.rst:142
+msgid "Restart the NTP client."
+msgstr "重启NTP客户端。"
+
+# ed2a3d2d19dc4679bf6153406fa541bd
+#: ../../hypervisor/xenserver.rst:148
+msgid "Make sure NTP will start again upon reboot."
+msgstr "确保机器重启之后NTP会自动启动。"
+
+# a8af271b25314a23bb268e7969c44be2
+#: ../../hypervisor/xenserver.rst:156
+msgid "Install CloudStack XenServer Support Package (CSP)"
+msgstr "安装 CloudStack XenServer 支持包(CSP)"
+
+# 0f869b8baf314029ba6e3249f3f31919
+#: ../../hypervisor/xenserver.rst:158
+msgid "(Optional)"
+msgstr "(可选)"
+
+# ef8e6914984045fe820f2142f5801c32
+#: ../../hypervisor/xenserver.rst:160
+msgid ""
+"To enable security groups, elastic load balancing, and elastic IP on "
+"XenServer, download and install the CloudStack XenServer Support Package "
+"(CSP). After installing XenServer, perform the following additional steps on"
+" each XenServer host."
+msgstr "要在XenServer上启用安全组、弹性负载均衡和弹性IP，请下载安装CloudStack XenServer支持包(CSP)。安装完XenServer之后，在每台XenServer主机上执行下列步骤。"
+
+# a8fc4362d3c348039963da1e1f0b41b4
+#: ../../hypervisor/xenserver.rst:165
+msgid "**For XenServer 6.1:**"
+msgstr ""
+
+# e208ea52210e4bec8f264922573855e2
+#: ../../hypervisor/xenserver.rst:167
+msgid "CSP functionality is already present in XenServer 6.1"
+msgstr ""
+
+# 378f2f6ca35b4ce4a72152f22948e64d
+#: ../../hypervisor/xenserver.rst:169
+msgid "Run the below command"
+msgstr ""
+
+# 68eac0ca1dc94b6181a9a3f9e81fa493
+#: ../../hypervisor/xenserver.rst:175
+msgid "update sysctl.conf with the following"
+msgstr ""
+
+# 69cb332c88bf4c2c82d7ab3b9f7b2799
+#: ../../hypervisor/xenserver.rst:186
+msgid "**For XenServer 6.0.2, 6.0, 5.6 SP2:**"
+msgstr ""
+
+# 03b2b8ea0626476a8c58d7cc9e4db68e
+#: ../../hypervisor/xenserver.rst:188
+msgid ""
+"Download the CSP software onto the XenServer host from one of the following "
+"links:"
+msgstr "请从下列链接之一下载CSP至XenServer主机："
+
+# bd00d11ce1cc45b8a45cef5f93e3d5eb
+#: ../../hypervisor/xenserver.rst:191
+msgid "For XenServer 6.0.2:"
+msgstr "适用于XenServer 6.0.2："
+
+# c7d858231a3142109c09bfcc3340078b
+#: ../../hypervisor/xenserver.rst:193
+msgid ""
+"`http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz "
+"<http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-"
+"supp.tgz>`_"
+msgstr "`http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz>`_"
+
+# 2cbbc4bcdcdd42d0816a6b2df748a0d6
+#: ../../hypervisor/xenserver.rst:196
+msgid "For XenServer 5.6 SP2:"
+msgstr "适用于XenServer 5.6 SP2:"
+
+# beac106ea20e420cae0ca5acb450646b
+#: ../../hypervisor/xenserver.rst:198
+msgid ""
+"`http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz "
+"<http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz>`_"
+msgstr "`http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz>`_"
+
+# 62cd9713906c45dc96254605c7134b11
+#: ../../hypervisor/xenserver.rst:201
+msgid "For XenServer 6.0:"
+msgstr "适用于XenServer 6.0:"
+
+# 998fd323b14c42149cc6633f4df39b83
+#: ../../hypervisor/xenserver.rst:203
+msgid ""
+"`http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz "
+"<http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz>`_"
+msgstr "`http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz>`_"
+
+# 50f6122c6c5e42dbb34f5942e788bd76
+#: ../../hypervisor/xenserver.rst:207
+msgid "Extract the file:"
+msgstr "解压文件："
+
+# afb359e6c1b34048bffed17d2dd50caf
+# d6743dae63394bbfb8c9281a2b807b79
+#: ../../hypervisor/xenserver.rst:213 ../../hypervisor/xenserver.rst:762
+msgid "Run the following script:"
+msgstr "执行下列脚本："
+
+# acac1637a03046aa8d18547ccc4bca4b
+#: ../../hypervisor/xenserver.rst:219
+msgid ""
+"If the XenServer host is part of a zone that uses basic networking, disable "
+"Open vSwitch (OVS):"
+msgstr "如果XenServer主机所在的区域使用的是基本网络模式 ，请禁用Open vSwitch (OVS):"
+
+# 3a99c0b1de854d158eda0ad17722a6a4
+#: ../../hypervisor/xenserver.rst:226
+msgid "Restart the host machine when prompted."
+msgstr "操作完成之后重启主机。"
+
+# de44be78fbb74675b797aa1c8d77d5f4
+#: ../../hypervisor/xenserver.rst:228
+msgid "The XenServer host is now ready to be added to CloudStack."
+msgstr "现在可以在CloudStack中添加XenServer。"
+
+# c7f7f8a7ee21490c87265ac50b0f82fa
+#: ../../hypervisor/xenserver.rst:232
+msgid "Primary Storage Setup for XenServer"
+msgstr "为XenServer配置主存储"
+
+# acb57e34a8e44c068d9bda2fa8784ab6
+#: ../../hypervisor/xenserver.rst:234
+msgid ""
+"CloudStack natively supports NFS, iSCSI and local storage. If you are using "
+"one of these storage types, there is no need to create the XenServer Storage"
+" Repository (\"SR\")."
+msgstr "CloudStack原生支持NFS，iSCSI和本地存储。如果使用其中的一种存储类型，则不需要创建XenServer存储库(\"SR\")。"
+
+# 2d42f9931e424e16b90373f6e29342e8
+#: ../../hypervisor/xenserver.rst:238
+msgid ""
+"If, however, you would like to use storage connected via some other "
+"technology, such as FiberChannel, you must set up the SR yourself. To do so,"
+" perform the following steps. If you have your hosts in a XenServer pool, "
+"perform the steps on the master node. If you are working with a single "
+"XenServer which is not part of a cluster, perform the steps on that "
+"XenServer."
+msgstr "但是，如果你想使用其他技术的存储，如FC存储，你必须自行设置SR。请按以下步骤操作来设置SR。如果你要设置的主机存在于XenServer池中，请在master主机上执行这些操作。如果是单台节点主机，则在该XenServer主机上操作即可。"
+
+# 56d99586bd3a4a558b7bb66ad8d45ca0
+#: ../../hypervisor/xenserver.rst:245
+msgid ""
+"Connect FiberChannel cable to all hosts in the cluster and to the "
+"FiberChannel storage host."
+msgstr "通过光纤通道将集群中的所有主机连接至光纤存储设备"
+
+# 8cd5013ce09d4df3b88eb92833ec5ec8
+#: ../../hypervisor/xenserver.rst:248
+msgid ""
+"Rescan the SCSI bus. Either use the following command or use XenCenter to "
+"perform an HBA rescan."
+msgstr "重新扫描SCSI总线。使用下列命令或者在XenCenter中使用HBA rescan按钮来完成扫描。"
+
+# bacd282ff359414aaa9442a987f5c298
+#: ../../hypervisor/xenserver.rst:255
+msgid "Repeat step 2 on every host."
+msgstr "在所有主机上重复步骤2."
+
+# cd620af66c684a0e89322909e82369f4
+#: ../../hypervisor/xenserver.rst:257
+msgid "Check to be sure you see the new SCSI disk."
+msgstr "检查确保已经识别到新的SCSI磁盘。"
+
+# 8318145d9f754f2cba3dc478f5fac2bb
+#: ../../hypervisor/xenserver.rst:263
+msgid ""
+"The output should look like this, although the specific file name will be "
+"different (scsi-<scsiID>):"
+msgstr "输出结果如下所示，指定的文件名稍许不同(scsi-<scsiID>):"
+
+# 1cd57220dc34464b9985019c2bc74209
+#: ../../hypervisor/xenserver.rst:271
+msgid "Repeat step 4 on every host."
+msgstr "在所有主机上重复步骤4"
+
+# ab7f1cb3586b43148fc804bf9f9a6785
+#: ../../hypervisor/xenserver.rst:273
+msgid ""
+"On the storage server, run this command to get a unique ID for the new SR."
+msgstr "在存储服务器中，运行下列命令获取新添加SR的唯一ID标识。"
+
+# f68f1582ab2645ff91819eb14ea37ebf
+#: ../../hypervisor/xenserver.rst:280
+msgid ""
+"The output should look like this, although the specific ID will be "
+"different:"
+msgstr "输出结果如下所示，指定的ID不同："
+
+# 12c7ee94b650422dac6fa14fc9a7d775
+#: ../../hypervisor/xenserver.rst:287
+msgid ""
+"Create the FiberChannel SR. In name-label, use the unique ID you just "
+"generated."
+msgstr "创建FC SR 。在name-label中，输入刚才获取的ID。"
+
+# e369b17cd1df40b3aa0cce96c1974a36
+#: ../../hypervisor/xenserver.rst:296
+msgid ""
+"This command returns a unique ID for the SR, like the following example "
+"(your ID will be different):"
+msgstr "这条命令会获取SR的ID，以下面为例（你的UUID不同）："
+
+# 23f181a0244c4e4b980acb6e64e29d3b
+#: ../../hypervisor/xenserver.rst:303
+msgid ""
+"To create a human-readable description for the SR, use the following "
+"command. In uuid, use the SR ID returned by the previous command. In name-"
+"description, set whatever friendly text you prefer."
+msgstr "使用下面的命令为SR创建通俗易懂的描述, uuid参数使用使用之前命令返回的SR ID. 在名称描述中，设置任何你自己喜欢的描述。"
+
+# 4323c9a63c6540b4a16886f29d0a1ec5
+#: ../../hypervisor/xenserver.rst:311
+msgid ""
+"Make note of the values you will need when you add this storage to "
+"CloudStack later (see `\"Add Primary Storage\" <configuration.html#add-"
+"primary-storage>`_). In the Add Primary Storage dialog, in Protocol, you "
+"will choose PreSetup. In SR Name-Label, you will enter the name-label you "
+"set earlier (in this example, e6849e96-86c3-4f2c-8fcc-350cc711be3d)."
+msgstr "记录这些值，之后在CloudStack中添加存储时会用到(查看 `\"添加主存储\" <configuration.html#add-primary-storage>`_)。在添加主存储对话框中的协议一项，选择PreSetup。在SR Name-Label中，输入之前设置的 name-label（在本示例中为e6849e96-86c3-4f2c-8fcc-350cc711be3d）。"
+
+# c99025edebad4540ba6b2b1d9b20ed10
+#: ../../hypervisor/xenserver.rst:318
+msgid ""
+"(Optional) If you want to enable multipath I/O on a FiberChannel SAN, refer "
+"to the documentation provided by the SAN vendor."
+msgstr "(可选)如果想在FC SAN上启用多路径I/O，请参考SAN供应商提供的文档。"
+
+# 32342d3a35f54066ade7572169b52896
+#: ../../hypervisor/xenserver.rst:323
+msgid "iSCSI Multipath Setup for XenServer (Optional)"
+msgstr "XenServer iSCSI多路径设置（可选）"
+
+# e2cf4ffa587b4372969e274849f484ee
+#: ../../hypervisor/xenserver.rst:325
+msgid ""
+"When setting up the storage repository on a Citrix XenServer, you can enable"
+" multipath I/O, which uses redundant physical components to provide greater "
+"reliability in the connection between the server and the SAN. To enable "
+"multipathing, use a SAN solution that is supported for Citrix servers and "
+"follow the procedures in Citrix documentation. The following links provide a"
+" starting point:"
+msgstr "在Citrix XenServer上配置存储库时，你可以启用多路径I/O，它是通过在服务器与SAN设备之间提供冗余的物理组件实现，提供了更高的可靠性。要启用多路径，请使用 XenServer文档中提供的SAN驱动程序。从下面链接开始："
+
+# 3849959c9c354656a9a9daafc5c5dbed
+#: ../../hypervisor/xenserver.rst:332
+msgid ""
+"`http://support.citrix.com/article/CTX118791 "
+"<http://support.citrix.com/article/CTX118791>`_"
+msgstr "`http://support.citrix.com/article/CTX118791 <http://support.citrix.com/article/CTX118791>`_"
+
+# 8a118ac63a7f41b8b60968177ca6b343
+#: ../../hypervisor/xenserver.rst:335
+msgid ""
+"`http://support.citrix.com/article/CTX125403 "
+"<http://support.citrix.com/article/CTX125403>`_"
+msgstr "`http://support.citrix.com/article/CTX125403 <http://support.citrix.com/article/CTX125403>`_"
+
+# d3f63182749e40fd86184084f5cc529b
+#: ../../hypervisor/xenserver.rst:338
+msgid ""
+"You can also ask your SAN vendor for advice about setting up your Citrix "
+"repository for multipathing."
+msgstr "你同样可以咨询SAN提供商提供关于配置Citrix存储库多路径的建议。"
+
+# 11df997f92b94313a59c0deac4d901ee
+#: ../../hypervisor/xenserver.rst:341
+msgid ""
+"Make note of the values you will need when you add this storage to the "
+"CloudStack later (see `\"Add Primary Storage\" <configuration.html#add-"
+"primary-storage>`_). In the Add Primary Storage dialog, in Protocol, you "
+"will choose PreSetup. In SR Name-Label, you will enter the same name used to"
+" create the SR."
+msgstr "记录这些值，之后在CloudStack中添加存储时将会用到(查看 `\"添加主存储\" <configuration.html#add-primary-storage>`_)。在添加主存储对话框中的协议一项，选择PreSetup。在SR Name-Label中，输入之前创建的SR名称。"
+
+# de3e8779fcb54068a8684c6ae2a20a69
+#: ../../hypervisor/xenserver.rst:347
+msgid ""
+"If you encounter difficulty, address the support team for the SAN provided "
+"by your vendor. If they are not able to solve your issue, see Contacting "
+"Support."
+msgstr "如果遇到任何困难, 请通过SAN供应商团队获得支持. 如果仍然无法解决你的问题, 请联系技术支持."
+
+# b62346b563314a04b2892d0d30ebafc9
+#: ../../hypervisor/xenserver.rst:353
+msgid "Physical Networking Setup for XenServer"
+msgstr "XenServer物理网络设置"
+
+# b07a74e5a82a42dfaa85655a392fc5a1
+#: ../../hypervisor/xenserver.rst:355
+msgid ""
+"Once XenServer has been installed, you may need to do some additional "
+"network configuration. At this point in the installation, you should have a "
+"plan for what NICs the host will have and what traffic each NIC will carry. "
+"The NICs should be cabled as necessary to implement your plan."
+msgstr "XenServer安装完成后， 需要对网络做一些额外的设置。此时， 你应该对主机上的网卡及每个网络传输的流量有一个整体规划。网络连接必须满足你的规划."
+
+# e67a8a2a93f44a4182d4d83db27837bb
+#: ../../hypervisor/xenserver.rst:361
+msgid ""
+"If you plan on using NIC bonding, the NICs on all hosts in the cluster must "
+"be cabled exactly the same. For example, if eth0 is in the private bond on "
+"one host in a cluster, then eth0 must be in the private bond on all hosts in"
+" the cluster."
+msgstr "如果你计划使用网卡绑定，那么所有主机上的网卡的连接必须相同。比如，如果群集中的一台主机eth0为专用绑定，那么其他主机上的eth0也必须为专用绑定。"
+
+# c8f114e421254029bfcc786da1e4f069
+#: ../../hypervisor/xenserver.rst:366
+msgid ""
+"The IP address assigned for the management network interface must be static."
+" It can be set on the host itself or obtained via static DHCP."
+msgstr "分配给管理网络的IP必须是静态IP。它可以通过DHCP保留或者在主机上指定。"
+
+# 4ea2dcd3445945e494146eea4f434ebe
+#: ../../hypervisor/xenserver.rst:369
+msgid ""
+"CloudStack configures network traffic of various types to use different NICs"
+" or bonds on the XenServer host. You can control this process and provide "
+"input to the Management Server through the use of XenServer network name "
+"labels. The name labels are placed on physical interfaces or bonds and "
+"configured in CloudStack. In some simple cases the name labels are not "
+"required."
+msgstr "CloudStack使用XenServer上的不同网卡或绑定来配置不同流量类型。你可以在管理服务器上通过输入XenServer适配器标签来控制这些流量。CloudStack中的标签名称就是物理接口或绑定的名称。在简单的网络中，可以不填写标签。"
+
+# d4647179170b4228990c4233187a27f0
+#: ../../hypervisor/xenserver.rst:376
+msgid ""
+"When configuring networks in a XenServer environment, network traffic labels"
+" must be properly configured to ensure that the virtual interfaces are "
+"created by CloudStack are bound to the correct physical device. The name-"
+"label of the XenServer network must match the XenServer traffic label "
+"specified while creating the CloudStack network. This is set by running the "
+"following command:"
+msgstr "在XenServer环境中配置网络时，必须正确的配置网络流量标签，确保CloudStack将虚拟接口绑定到正确的物理设备上。XenServer的网络标签必须与配置CloudStack的网络时指定的XenServer流量标签一致。运行以下命令来设置："
+
+# c06c60c71a7f4bca8a451f0b7283cfda
+#: ../../hypervisor/xenserver.rst:389
+msgid ""
+"Configuring Public Network with a Dedicated NIC for XenServer (Optional)"
+msgstr "使用专用的XenServer网卡来配置公用网络（可选）"
+
+# 6e7e724c968a42a3a8b427928f42cb98
+#: ../../hypervisor/xenserver.rst:391
+msgid ""
+"CloudStack supports the use of a second NIC (or bonded pair of NICs, "
+"described in :ref:`nic-bonding-for-xenserver`) for the public network. If "
+"bonding is not used, the public network can be on any NIC and can be on "
+"different NICs on the hosts in a cluster. For example, the public network "
+"can be on eth0 on node A and eth1 on node B. However, the XenServer name-"
+"label for the public network must be identical across all hosts. The "
+"following examples set the network label to \"cloud-public\". After the "
+"management server is installed and running you must configure it with the "
+"name of the chosen network label (e.g. \"cloud-public\"); this is discussed "
+"in `\"Management Server Installation\" <installation.html#management-server-"
+"installation>`_."
+msgstr "CloudStack支持公共网络使用第二块网卡(或者是2块网卡绑定，在 :ref:`nic-bonding-for-xenserver` 有描述)。如果没有使用绑定，公共网络可以使用群集中不同主机上的不同网卡。比如，公共网络可以使用节点A上的eth0和节点B上的eth1。但是，用于公共网络的名称标签在所有主机上必须一致。举个例子，我们在XenServer上设定了网络标签\"cloud-public\"。在安装完管理服务器之后，你必须使用( \"cloud-public\")作为对应的CloudStack的网络流量标签；这个在 `\"管理服务器的安装\" <installation.html#management-server-installation>`_中有介绍。"
+
+# 0a920576e6984f1684ffa04b4cedee14
+#: ../../hypervisor/xenserver.rst:403
+msgid ""
+"If you are using two NICs bonded together to create a public network, see "
+":ref:`nic-bonding-for-xenserver`."
+msgstr "如果你使用双网卡绑定作为公共网络，请参阅 :ref:`nic-bonding-for-xenserver`。"
+
+# c29eb136da7f472bb9092308209f4874
+#: ../../hypervisor/xenserver.rst:406
+msgid ""
+"If you are using a single dedicated NIC to provide public network access, "
+"follow this procedure on each new host that is added to CloudStack before "
+"adding the host."
+msgstr "如果你指定单网卡作为公共网络，在加入CloudStack环境之前按照下面的流程配置每个主机。"
+
+# b6c2fcbca5784ac58cb4d766831c1feb
+#: ../../hypervisor/xenserver.rst:410
+msgid ""
+"Run xe network-list and find the public network. This is usually attached to"
+" the NIC that is public. Once you find the network make note of its UUID. "
+"Call this <UUID-Public>."
+msgstr "运行xe network-list，查找公共网络。通常它的名字就是public。找到之后记录UUID。可以称之为<UUID-Public>。"
+
+# 7771ef8019cf477aab4f4ea6e54dc19f
+#: ../../hypervisor/xenserver.rst:414
+msgid "Run the following command."
+msgstr "运行以下命令。"
+
+# 8b08df411b014c2fb09ab7803d37e385
+#: ../../hypervisor/xenserver.rst:422
+msgid "Configuring Multiple Guest Networks for XenServer (Optional)"
+msgstr "XenServer配置多个来宾网络(可选)"
+
+# ae3d74bbbeb6474caa1aabf43ce3350d
+#: ../../hypervisor/xenserver.rst:424
+msgid ""
+"CloudStack supports the use of multiple guest networks with the XenServer "
+"hypervisor. Each network is assigned a name-label in XenServer. For example,"
+" you might have two networks with the labels \"cloud-guest\" and \"cloud-"
+"guest2\". After the management server is installed and running, you must add"
+" the networks and use these labels so that CloudStack is aware of the "
+"networks."
+msgstr "CloudStack支持在XenServer上使用多个来宾网络。在XenServer中为每个网络都被分配名称标签。例如，你可能有两个名称分别为\"cloud-guest\"和\"cloud-guest2\"的网络。在配置好管理服务器并且运行后，你必须使用这些标签将这些网络添加到CloudStack中，以便CloudStack能够识别到这些网络。"
+
+# 445fbda3e6e241b49943d5a3bbae731e
+#: ../../hypervisor/xenserver.rst:431
+msgid ""
+"Follow this procedure on each new host before adding the host to CloudStack:"
+msgstr "在将主机添加到CloudStack之前，请在每个新主机上执行以下操作："
+
+# ad021bb20dfc411ca2a0b4f6c7bb1976
+#: ../../hypervisor/xenserver.rst:434
+msgid ""
+"Run xe network-list and find one of the guest networks. Once you find the "
+"network make note of its UUID. Call this <UUID-Guest>."
+msgstr "运行xe network-list，找出来宾网络。并记录UUID。可以称为<UUID-Guest>。"
+
+# 5c54bddb03ab41988d164862d3e8ca4a
+#: ../../hypervisor/xenserver.rst:437
+msgid ""
+"Run the following command, substituting your own name-label and uuid values."
+msgstr "运行下面的命令, 替换你自己的名称标签和UUID."
+
+# 66309bb437094b1d9bbb0774c232de9a
+#: ../../hypervisor/xenserver.rst:444
+msgid ""
+"Repeat these steps for each additional guest network, using a different "
+"name-label and uuid each time."
+msgstr "对每个额外的来宾网络都重复这些步骤，注意每次要使用不同的名称标签和UUID。"
+
+# 355487377b08418899e9ec50ac78ae2f
+#: ../../hypervisor/xenserver.rst:449
+msgid "Separate Storage Network for XenServer (Optional)"
+msgstr "XenServer设置单独的存储网络(可选)"
+
+# 589c7e9b7fb048aea788093e27195cf2
+#: ../../hypervisor/xenserver.rst:451
+msgid ""
+"You can optionally set up a separate storage network. This should be done "
+"first on the host, before implementing the bonding steps below. This can be "
+"done using one or two available NICs. With two NICs bonding may be done as "
+"above. It is the administrator's responsibility to set up a separate storage"
+" network."
+msgstr "在绑定网卡之前，你可以有选择的配置一个独立的存储网络。使用1到2个网卡，上述给出了两块网卡绑定的示例。配置一个独立的存储网络是管理的职责。"
+
+# 61490e5df97948629bbb83dda64d4aa9
+#: ../../hypervisor/xenserver.rst:457
+msgid ""
+"Give the storage network a different name-label than what will be given for "
+"other networks."
+msgstr "为存储网络设置一个与其他网络不同的名称标签。"
+
+# 164d8afca329462b9c5943496322bcf0
+#: ../../hypervisor/xenserver.rst:460
+msgid ""
+"For the separate storage network to work correctly, it must be the only "
+"interface that can ping the primary storage device's IP address. For "
+"example, if eth0 is the management network NIC, ping -I eth0 <primary "
+"storage device IP> must fail. In all deployments, secondary storage devices "
+"must be pingable from the management network NIC or bond. If a secondary "
+"storage device has been placed on the storage network, it must also be "
+"pingable via the storage network NIC or bond on the hosts as well."
+msgstr "让独立的存储网络工作正常，必须可以通过它的接口ping通主存储设备的IP。比如，如果eth0是管理网络的网卡，ping -I eth0 <primary storage device IP>必须是不通的。在所有的部署环境里，通过管理网络必须能ping通辅助存储设备的IP。如果辅助存储设备是在存储网络中，那么通过存储网络同样也要能ping通它。"
+
+# 90f24bd320174d1fac607e00a9e983f8
+#: ../../hypervisor/xenserver.rst:469
+msgid ""
+"You can set up two separate storage networks as well. For example, if you "
+"intend to implement iSCSI multipath, dedicate two non-bonded NICs to "
+"multipath. Each of the two networks needs a unique name-label."
+msgstr "你可以设置两个独立的存储网络。例如，使用两块独立网卡实现iSCSI多路径。当然，两个网络都需要自己的名称标签。"
+
+# 61c2f4816fdb42d5b6cc3c6d2ca18ca8
+#: ../../hypervisor/xenserver.rst:473
+msgid ""
+"If no bonding is done, the administrator must set up and name-label the "
+"separate storage network on all hosts (masters and slaves)."
+msgstr "如果没有做绑定，管理员必须为所有主机上(主、从节点)的存储网络设置名称标签。"
+
+# 00dbbb5d1bcd4becb0dec5b47340f83d
+#: ../../hypervisor/xenserver.rst:476
+msgid ""
+"Here is an example to set up eth5 to access a storage network on "
+"172.16.0.0/24."
+msgstr "此处示例配置eth5访问172.16.0.0/24的存储网络。"
+
+# 185e1a599c604803a54446ba74b35dc9
+#: ../../hypervisor/xenserver.rst:490
+msgid "NIC Bonding for XenServer (Optional)"
+msgstr "XenServer中的网卡绑定（可选）"
+
+# caf6aa9edc614274af0ef31881fe03ca
+#: ../../hypervisor/xenserver.rst:492
+msgid ""
+"XenServer supports Source Level Balancing (SLB) NIC bonding. Two NICs can be"
+" bonded together to carry public, private, and guest traffic, or some "
+"combination of these. Separate storage networks are also possible. Here are "
+"some example supported configurations:"
+msgstr "XenServer支持Source Level Balancing (SLB) NIC绑定。两块网卡可被绑定在一起承载公共网络、管理网络和来宾网络流量，或这些网络的组合。单独的存储网络同样可以。以下是一些配置的示例："
+
+# 44d7cdc70d4541e4b8b66e39293c57c5
+#: ../../hypervisor/xenserver.rst:497
+msgid "2 NICs on private, 2 NICs on public, 2 NICs on storage"
+msgstr "管理网络使用2块网卡，公共网络使用2块网卡，存储网络使用2块网卡"
+
+# 7dbbc60ca898461991faac0752ccb9b6
+#: ../../hypervisor/xenserver.rst:499
+msgid "2 NICs on private, 1 NIC on public, storage uses management network"
+msgstr "管理网络使用2块网卡，公共网络使用1块网卡，存储共用管理网络"
+
+# 933cb0b64cdc4b93b709825c7f872083
+#: ../../hypervisor/xenserver.rst:501
+msgid "2 NICs on private, 2 NICs on public, storage uses management network"
+msgstr "管理网络使用2块网卡，共用网络使用2块网卡，存储共用管理网络"
+
+# aa2cdc325ff64d6dbeb15a9db3815249
+#: ../../hypervisor/xenserver.rst:503
+msgid "1 NIC for private, public, and storage"
+msgstr "管理网络，公共网络，存储网络使用一块网卡"
+
+# a5c691fdc14644f1938a3d7e0616e209
+#: ../../hypervisor/xenserver.rst:505
+msgid "All NIC bonding is optional."
+msgstr "所有的网卡绑定都是可选的"
+
+# ce37792754e74070b0880c3c27ca5b6d
+#: ../../hypervisor/xenserver.rst:507
+msgid ""
+"XenServer expects all nodes in a cluster will have the same network cabling "
+"and same bonds implemented. In an installation the master will be the first "
+"host that was added to the cluster and the slave hosts will be all "
+"subsequent hosts added to the cluster. The bonds present on the master set "
+"the expectation for hosts added to the cluster later. The procedure to set "
+"up bonds on the master and slaves are different, and are described below. "
+"There are several important implications of this:"
+msgstr "XenServer期望群集中所有的节点都拥有相同的网络布线，以及相同的绑定。在安装完成后第一台主机将成为Master，而随后加入到群集中的其他主机都将成为Slave。Master主机上的网卡绑定设置会覆盖其他主机的网络配置。在Master和Slaver上设置网卡绑定的步骤不同，重点包括几个部分："
+
+# 31e309b5aea94e1982a0745fa2f8d163
+#: ../../hypervisor/xenserver.rst:515
+msgid ""
+"You must set bonds on the first host added to a cluster. Then you must use "
+"xe commands as below to establish the same bonds in the second and "
+"subsequent hosts added to a cluster."
+msgstr "必须在添加至群集的第一台主机上设置网卡绑定。然后必须使用如下的xe命令，使第二台和随后添加至该群集的主机上自动配置与Master主机相同的网卡绑定。"
+
+# dc53904a0ade40e8996b6379af74299d
+#: ../../hypervisor/xenserver.rst:519
+msgid ""
+"Slave hosts in a cluster must be cabled exactly the same as the master. For "
+"example, if eth0 is in the private bond on the master, it must be in the "
+"management network for added slave hosts."
+msgstr "群集中的Slave主机必须与Master主机拥有完全相同的布线。例如，如果eth0在群集中的主机上的专用网络绑定中，那么eth0必须在群集中的所有主机上专用网络绑定中。"
+
+# 5a1e3289d6064e239e1ac513d07d53c7
+#: ../../hypervisor/xenserver.rst:525
+msgid "Management Network Bonding"
+msgstr "管理网络绑定"
+
+# d6933d9eedc548ea911d1c03954c8cc8
+#: ../../hypervisor/xenserver.rst:527
+msgid ""
+"The administrator must bond the management network NICs prior to adding the "
+"host to CloudStack."
+msgstr "在将主机添加至CloudStack之前管理员必须绑定管理网络的网卡。"
+
+# 990edf34545641be9105fff2e790fa8e
+#: ../../hypervisor/xenserver.rst:532
+msgid "Creating a Private Bond on the First Host in the Cluster"
+msgstr "在群集的第一台主机中创建专用绑定"
+
+# bef555ea56e644ee824b3211d285a5dc
+#: ../../hypervisor/xenserver.rst:534
+msgid ""
+"Use the following steps to create a bond in XenServer. These steps should be"
+" run on only the first host in a cluster. This example creates the cloud-"
+"private network with two physical NICs (eth0 and eth1) bonded into it."
+msgstr "使用下述步骤在XenServer上创建网卡绑定。这些步骤只在群集中第一台主机上运行即可。本示例为cloud-private网络绑定了两块物理网卡(eth0和eth1)。"
+
+# 76d14a97770b48e3b7573b8df3d95987
+# 83ee5c43bfdf49078158dc0ede74e1cb
+#: ../../hypervisor/xenserver.rst:539 ../../hypervisor/xenserver.rst:583
+msgid "Find the physical NICs that you want to bond together."
+msgstr "找到想要绑定在一起的物理网卡。"
+
+# 19647e91e4064b26bcf46ae5ccdb7654
+#: ../../hypervisor/xenserver.rst:546
+msgid ""
+"These command shows the eth0 and eth1 NICs and their UUIDs. Substitute the "
+"ethX devices of your choice. Call the UUID's returned by the above command "
+"slave1-UUID and slave2-UUID."
+msgstr "如上命令显示了eth0、eth1和对应的UUID。并替换你的网卡编号。上述命令返回的UUID称为slave1-UUID和slave2-UUID。"
+
+# eb485b7e38044135bbafec10517e6fda
+#: ../../hypervisor/xenserver.rst:550
+msgid ""
+"Create a new network for the bond. For example, a new network with name "
+"\"cloud-private\"."
+msgstr "为该绑定创建一个新的网络。例如，一个名为“cloud-public”的新网络。"
+
+# 4426249063674de991301445df08c8af
+#: ../../hypervisor/xenserver.rst:553
+msgid ""
+"**This label is important. CloudStack looks for a network by a name you "
+"configure. You must use the same name-label for all hosts in the cloud for "
+"the management network.**"
+msgstr "**标签非常重要。因为CloudStack根据配置的名称查找网络。必须对云中所有主机的管理网络使用同样的名称标签（name-label）。**"
+
+# 10a8ca3e627f42039cde96aa311c2e24
+#: ../../hypervisor/xenserver.rst:563
+msgid ""
+"Now you have a bonded pair that can be recognized by CloudStack as the "
+"management network."
+msgstr "现在有了可以被CloudStack识别为管理网络的网卡绑定。"
+
+# 8237b2020d164e25afdf235b117e0226
+#: ../../hypervisor/xenserver.rst:568
+msgid "Public Network Bonding"
+msgstr "公共网络网卡绑定"
+
+# c0b0ed9d574d4595b6bccb839df5a9d6
+#: ../../hypervisor/xenserver.rst:570
+msgid ""
+"Bonding can be implemented on a separate, public network. The administrator "
+"is responsible for creating a bond for the public network if that network "
+"will be bonded and will be separate from the management network."
+msgstr "可以在单独的公共网络上执行绑定。管理员可以将使用网卡绑定的公共网络与管理网络区分开。"
+
+# 49b1405549674b47892be73abf90bb90
+#: ../../hypervisor/xenserver.rst:577
+msgid "Creating a Public Bond on the First Host in the Cluster"
+msgstr "在集群的第一台主机上创建公共网络网卡绑定"
+
+# 80ceb8eb4f324fa288b049d1b412d166
+#: ../../hypervisor/xenserver.rst:579
+msgid ""
+"These steps should be run on only the first host in a cluster. This example "
+"creates the cloud-public network with two physical NICs (eth2 and eth3) "
+"bonded into it."
+msgstr "以下步骤仅在群集的第一台主机中运行。本示例为cloud-public绑定了两块物理网卡(eth2和eth3)。"
+
+# e9ee4656a26c4e429fa44a19deca4697
+#: ../../hypervisor/xenserver.rst:590
+msgid ""
+"These command shows the eth2 and eth3 NICs and their UUIDs. Substitute the "
+"ethX devices of your choice. Call the UUID's returned by the above command "
+"slave1-UUID and slave2-UUID."
+msgstr "以上命令显示了eth2、eth3和对应的UUID。替换你的网卡编号。将上述命令返回的UUID称为slave1-UUID和slave2-UUID。"
+
+# ecd21d8abed7420cbdb7722f7d3bbcf6
+#: ../../hypervisor/xenserver.rst:594
+msgid ""
+"Create a new network for the bond. For example, a new network with name "
+"\"cloud-public\"."
+msgstr "为网卡绑定创建一个新的网络。比如，一个名为\"cloud-public\"的新网络。"
+
+# f2ccf39a444949779ea15c87c23f1102
+#: ../../hypervisor/xenserver.rst:597
+msgid ""
+"**This label is important. CloudStack looks for a network by a name you "
+"configure. You must use the same name-label for all hosts in the cloud for "
+"the public network.**"
+msgstr "**该标签非常重要。因为CloudStack根据配置的名称来查找网络。必须对云中所有物理主机的公共网络使用同样的名称标签（name-label）。**"
+
+# c63c4fffe13c41e3857c2d5a7037324d
+#: ../../hypervisor/xenserver.rst:607
+msgid ""
+"Now you have a bonded pair that can be recognized by CloudStack as the "
+"public network."
+msgstr "现在有了被CloudStack识别为公共网络的网卡绑定。"
+
+# 4571fae00d22423c977f157626730a6b
+#: ../../hypervisor/xenserver.rst:612
+msgid "Adding More Hosts to the Cluster"
+msgstr "在群集中添加更多主机"
+
+# bb7f4bc061df424882aa108cec051dde
+#: ../../hypervisor/xenserver.rst:614
+msgid ""
+"With the bonds (if any) established on the master, you should add "
+"additional, slave hosts. Run the following command for all additional hosts "
+"to be added to the cluster. This will cause the host to join the master in a"
+" single XenServer pool."
+msgstr "在master主机添加了(任何)绑定网卡的基础上，可以添加其他的slave主机。对所有添加至群集的其他主机执行下面的命令。他的作用是将这些主机都加入master所在的同一个XenServer池中。"
+
+# 2e3ff343227f43eca63a765a974c4e58
+#: ../../hypervisor/xenserver.rst:626
+msgid "Complete the Bonding Setup Across the Cluster"
+msgstr "完成群集内的绑定设置"
+
+# e54d6baf9f4a4630ae0802e0e114130f
+#: ../../hypervisor/xenserver.rst:628
+msgid ""
+"With all hosts added to the pool, run the cloud-setup-bond script. This "
+"script will complete the configuration and set up of the bonds across all "
+"hosts in the cluster."
+msgstr "所有主机添加至资源池后，运行 cloud-setup-bond脚本。此脚本将配置群集中所有主机的网卡绑定。"
+
+# 27800d5ec6e44bdcb75245bf193bfda2
+#: ../../hypervisor/xenserver.rst:632
+msgid ""
+"Copy the script from the Management Server in /usr/share/cloudstack-"
+"common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh to the master "
+"host and ensure it is executable."
+msgstr "将管理服务器中/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh拷贝到master主机中并确认该脚本可执行。"
+
+# ed41f3f65d3f49209bba272a3b1c0922
+#: ../../hypervisor/xenserver.rst:636
+msgid "Run the script:"
+msgstr "运行脚本："
+
+# 30dd45661f474b9f9d626aa8df7052e5
+#: ../../hypervisor/xenserver.rst:642
+msgid "Now the bonds are set up and configured properly across the cluster."
+msgstr "现在，群集内所有主机的网卡绑定都已配置正确。"
+
+# 06329e8ef297453d9fbe11b802a02387
+#: ../../hypervisor/xenserver.rst:648
+msgid "Upgrading XenServer Versions"
+msgstr "升级XenServer版本"
+
+# 7ae8e3b4c5e745e7b43ab29f5129e0cf
+#: ../../hypervisor/xenserver.rst:650
+msgid ""
+"This section tells how to upgrade XenServer software on CloudStack hosts. "
+"The actual upgrade is described in XenServer documentation, but there are "
+"some additional steps you must perform before and after the upgrade."
+msgstr "本章节介绍了如何升级CloudStack环境中的XenServer。实际升级的操作在XenServer文档中有详细描述，但是在升级前后有些额外的步骤必须执行。"
+
+# a49d855e0fec4ddfb046814a7a02bc58
+#: ../../hypervisor/xenserver.rst:656
+msgid ""
+"Be sure the hardware is certified compatible with the new version of "
+"XenServer."
+msgstr "确保硬件可以被新版本XenServer支持。"
+
+# dee99a5634554dc4b7188ab5c5aedc45
+#: ../../hypervisor/xenserver.rst:659
+msgid "To upgrade XenServer:"
+msgstr "升级XenServer："
+
+# c58f7ac2d954400395df0861156c145b
+#: ../../hypervisor/xenserver.rst:661
+msgid "Upgrade the database. On the Management Server node:"
+msgstr "升级数据库。在管理服务器节点上："
+
+# a680a343ad5b4dc0900df3a60f835ead
+#: ../../hypervisor/xenserver.rst:663
+msgid "Back up the database:"
+msgstr "备份数据库："
+
+# 22c201339a64428aba4b9ed4256a473e
+#: ../../hypervisor/xenserver.rst:670
+msgid ""
+"You might need to change the OS type settings for VMs running on the "
+"upgraded hosts."
+msgstr "需要更改升级后的主机中虚拟机的操作系统类型。"
+
+# b4e5d659dfde45c7bf1279a03e48b5c1
+#: ../../hypervisor/xenserver.rst:673
+msgid ""
+"If you upgraded from XenServer 5.6 GA to XenServer 5.6 SP2, change any VMs "
+"that have the OS type CentOS 5.5 (32-bit), Oracle Enterprise Linux 5.5 "
+"(32-bit), or Red Hat Enterprise Linux 5.5 (32-bit) to Other Linux (32-bit). "
+"Change any VMs that have the 64-bit versions of these same OS types to Other"
+" Linux (64-bit)."
+msgstr "如果是从XenServer 5.6 GA 升级到XenServer 5.6 SP2，更改虚机操作系统类型CentOS 5.5 (32-bit), Oracle Enterprise Linux 5.5 (32-bit)或者Red Hat Enterprise Linux 5.5 (32-bit)为Other Linux (32-bit)。同样这些虚机的64位版本操作系统类型也要改为Other Linux (64-bit)。"
+
+# 7573f70d77e248e5a4d430bd16631bbe
+#: ../../hypervisor/xenserver.rst:680
+msgid ""
+"If you upgraded from XenServer 5.6 SP2 to XenServer 6.0.2, change any VMs "
+"that have the OS type CentOS 5.6 (32-bit), CentOS 5.7 (32-bit), Oracle "
+"Enterprise Linux 5.6 (32-bit), Oracle Enterprise Linux 5.7 (32-bit), Red Hat"
+" Enterprise Linux 5.6 (32-bit) , or Red Hat Enterprise Linux 5.7 (32-bit) to"
+" Other Linux (32-bit). Change any VMs that have the 64-bit versions of these"
+" same OS types to Other Linux (64-bit)."
+msgstr "如果是从XenServer 5.6 SP2升级到XenServer 6.0.2，更改虚拟操作系统类型CentOS 5.6 (32-bit), CentOS 5.7 (32-bit), Oracle Enterprise Linux 5.6 (32-bit), Oracle Enterprise Linux 5.7 (32-bit), Red Hat Enterprise Linux 5.6 (32-bit)或者Red Hat Enterprise Linux 5.7 (32-bit)为Other Linux (32-bit)。同样这些虚机的64位版本操作系统类型也要改为Other Linux (64-bit)。"
+
+# ecee533ad8dd40ecbab222880d5502e4
+#: ../../hypervisor/xenserver.rst:688
+msgid ""
+"If you upgraded from XenServer 5.6 to XenServer 6.0.2, do all of the above."
+msgstr "如果从XenServer 5.6升级到XenServer 6.0.2，需完成以上所有操作。"
+
+# 92dd0b5b05d349f5b31a218ef5053b51
+#: ../../hypervisor/xenserver.rst:691
+msgid ""
+"Restart the Management Server and Usage Server. You only need to do this "
+"once for all clusters."
+msgstr "重启管理服务和Usage服务. 只需为所有的集群做一次这样的操作。"
+
+# 609fce92c5004d349ce69313e8b259d1
+#: ../../hypervisor/xenserver.rst:699
+msgid "Disconnect the XenServer cluster from CloudStack."
+msgstr "在CloudStack中断开XenServer群集连接。"
+
+# a0e0ba7425e84cc4b3c558e55e6ba6c1
+# 9a532ffafa924e14bfdcd5a3f893f796
+#: ../../hypervisor/xenserver.rst:701 ../../hypervisor/xenserver.rst:803
+msgid "Log in to the CloudStack UI as root."
+msgstr "使用admin账户登录CloudStack管理界面。"
+
+# cfa57057adf34d20ad28ea73d14ef535
+#: ../../hypervisor/xenserver.rst:703
+msgid "Navigate to the XenServer cluster, and click Actions – Unmanage."
+msgstr "导航至XenServer群集，点击操作-取消管理。"
+
+# 5d95636b239e4667b4933027c8a99a25
+#: ../../hypervisor/xenserver.rst:705
+msgid "Watch the cluster status until it shows Unmanaged."
+msgstr "查看群集状态直到显示未受管理。"
+
+# 80449684af9d499095d5d868770d0e7b
+#: ../../hypervisor/xenserver.rst:707
+msgid ""
+"Log in to one of the hosts in the cluster, and run this command to clean up "
+"the VLAN:"
+msgstr "登录到群集中的任意一台主机，运行下面的命令清除VLAN信息："
+
+# d785d08cf59f499398b8f029d5186b94
+#: ../../hypervisor/xenserver.rst:714
+msgid "Still logged in to the host, run the upgrade preparation script:"
+msgstr "仍旧在这台已经登录的主机中，运行下面的升级准备脚本："
+
+# 31f5837f129648c9a08eca9c059eb78c
+#: ../../hypervisor/xenserver.rst:720
+msgid ""
+"Troubleshooting: If you see the error \"can't eject CD,\" log in to the VM "
+"and umount the CD, then run the script again."
+msgstr "故障排除：如果看到 \"can't eject CD,\" 错误，请登录到虚拟机将光盘卸载，并重新运行脚本。"
+
+# 715d2f02ed1c47c589935a7f3b1dafa3
+#: ../../hypervisor/xenserver.rst:723
+msgid ""
+"Upgrade the XenServer software on all hosts in the cluster. Upgrade the "
+"master first."
+msgstr "升级群集中所有的XenServer主机。首先升级master节点。"
+
+# d16b76e393814c10b8ce59d9d571f9a4
+#: ../../hypervisor/xenserver.rst:726
+msgid ""
+"Live migrate all VMs on this host to other hosts. See the instructions for "
+"live migration in the Administrator's Guide."
+msgstr "将该主机上的所有虚拟机动态迁移到其他主机。请参照管理指南了解动态迁移指导。"
+
+# 2abd9a8c661b47fc8eee237cf9108f92
+#: ../../hypervisor/xenserver.rst:729
+msgid ""
+"Troubleshooting: You might see the following error when you migrate a VM:"
+msgstr "故障排除：迁移虚拟机时可能会遇到下面的错误："
+
+# b23537b0d5f942ccb71f8849c129899d
+#: ../../hypervisor/xenserver.rst:738
+msgid "To solve this issue, run the following:"
+msgstr "解决这个问题，请运行下面的命令："
+
+# d92194b697694bd2b8152cfa36773892
+#: ../../hypervisor/xenserver.rst:744
+msgid "Reboot the host."
+msgstr "重启主机。"
+
+# 34903a18372648c9b8b6d06d03d0e02c
+#: ../../hypervisor/xenserver.rst:746
+msgid ""
+"Upgrade to the newer version of XenServer. Use the steps in XenServer "
+"documentation."
+msgstr "要升级更新版本的XenServer。请执行XenServer文档中的步骤。"
+
+# 573adf7c44514928894306fcf3566a98
+#: ../../hypervisor/xenserver.rst:749
+msgid ""
+"After the upgrade is complete, copy the following files from the management "
+"server to this host, in the directory locations shown below:"
+msgstr "在升级完成之后，将下列文件从管理服务器复制到这台主机，文件所在路径如下："
+
+# 18eb28018d324049916e1e1a4b9b1680
+#: ../../hypervisor/xenserver.rst:754
+msgid "Copy this Management Server file"
+msgstr "复制管理服务器的文件"
+
+# 37bd1b6db08741b39cf4840e83ad9279
+#: ../../hypervisor/xenserver.rst:754
+msgid "To this location on the XenServer host"
+msgstr "复制到XenServer主机的路径"
+
+# 77c4c74d05ee4ed084fecb4d94f0038e
+#: ../../hypervisor/xenserver.rst:756
+msgid ""
+"/usr/share/cloudstack-"
+"common/scripts/vm/hypervisor/xenserver/xenserver60/NFSSR.py"
+msgstr "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/xenserver60/NFSSR.py"
+
+# 5d5d441f185b4da39acede52092ab729
+#: ../../hypervisor/xenserver.rst:756
+msgid "/opt/xensource/sm/NFSSR.py"
+msgstr "/opt/xensource/sm/NFSSR.py"
+
+# b9569d25b25c47589eb352b2f26b96d8
+#: ../../hypervisor/xenserver.rst:757
+msgid ""
+"/usr/share/cloudstack-"
+"common/scripts/vm/hypervisor/xenserver/setupxenserver.sh"
+msgstr "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/setupxenserver.sh"
+
+# 8ccdd7cb7c6d4213ba0d257d2adfcf42
+#: ../../hypervisor/xenserver.rst:757
+msgid "/opt/xensource/bin/setupxenserver.sh"
+msgstr "/opt/xensource/bin/setupxenserver.sh"
+
+# 70be8fbba5fe4f9d81dbe6ffe68ca9fa
+#: ../../hypervisor/xenserver.rst:758
+msgid ""
+"/usr/share/cloudstack-"
+"common/scripts/vm/hypervisor/xenserver/make\\_migratable.sh"
+msgstr "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/make\\_migratable.sh"
+
+# 9545ac4a5e554ac0856980527ee37e93
+#: ../../hypervisor/xenserver.rst:758
+msgid "/opt/xensource/bin/make\\_migratable.sh"
+msgstr "/opt/xensource/bin/make\\_migratable.sh"
+
+# d5729618b07f45fa871e57a5cdd5cb11
+#: ../../hypervisor/xenserver.rst:759
+msgid ""
+"/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-clean-"
+"vlan.sh"
+msgstr "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-clean-vlan.sh"
+
+# 0af33abd27be47cf9afd563a8049f92f
+#: ../../hypervisor/xenserver.rst:759
+msgid "/opt/xensource/bin/cloud-clean-vlan.sh"
+msgstr "/opt/xensource/bin/cloud-clean-vlan.sh"
+
+# 57e220ee90da43a18a72c97fb44f4642
+#: ../../hypervisor/xenserver.rst:768
+msgid ""
+"Troubleshooting: If you see the following error message, you can safely "
+"ignore it."
+msgstr "故障排除：如果看到下面的错误信息，可以忽略它。"
+
+# 7d8ccf199424413ca7d2c6ace78d8d25
+#: ../../hypervisor/xenserver.rst:775
+msgid ""
+"Plug in the storage repositories (physical block devices) to the XenServer "
+"host:"
+msgstr "将XenServer主机连接至存储库(物理的块设备)："
+
+# 03e1d3926bc546a5af37036f806b6776
+#: ../../hypervisor/xenserver.rst:783
+msgid ""
+"If you add a host to this XenServer pool, you need to migrate all VMs on "
+"this host to other hosts, and eject this host from XenServer pool."
+msgstr "如果添加一台主机到这个XenServer资源池中，你必须将这台主机上的所有的虚机迁移到其他主机，然后将这台主机从原来的XenServer资源池中移除。"
+
+# 9e79d6523b9b4c6982d7f0df8b920625
+#: ../../hypervisor/xenserver.rst:786
+msgid ""
+"Repeat these steps to upgrade every host in the cluster to the same version "
+"of XenServer."
+msgstr "重复这些步骤，将每台主机都升级到相同的XenServer版本。"
+
+# 0f820c2f7c49419ea8cce858406d9043
+#: ../../hypervisor/xenserver.rst:789
+msgid ""
+"Run the following command on one host in the XenServer cluster to clean up "
+"the host tags:"
+msgstr "在XenServer群集中的一台主机上运行下面命令来清除主机标签："
+
+# 742db1ba5463410a9d82cc3a89bb7199
+#: ../../hypervisor/xenserver.rst:797
+msgid ""
+"When copying and pasting a command, be sure the command has pasted as a "
+"single line before executing. Some document viewers may introduce unwanted "
+"line breaks in copied text."
+msgstr "当复制和粘贴命令时，请确保没有多余的换行符，因为一些文档查看器可能会在复制时加上换行符。"
+
+# 5432c32d5f10462dbd868cbbbddc88f4
+#: ../../hypervisor/xenserver.rst:801
+msgid "Reconnect the XenServer cluster to CloudStack."
+msgstr "在CloudStack中重新连接XenServer群集。"
+
+# 21a80cdb8f254573809173ca433e813e
+#: ../../hypervisor/xenserver.rst:805
+msgid "Navigate to the XenServer cluster, and click Actions – Manage."
+msgstr "在XenServer群集导航页中，点击操作-管理。"
+
+# feaf793c4bb243358fe6893a23769add
+#: ../../hypervisor/xenserver.rst:807
+msgid "Watch the status to see that all the hosts come up."
+msgstr "查看状态以确保所有的主机都恢复正常."
+
+# 228283144fa14ff9b751f39e8007043f
+#: ../../hypervisor/xenserver.rst:809
+msgid "After all hosts are up, run the following on one host in the cluster:"
+msgstr "当所有的主机都是运行状态后, 在集群中的一台主机上运行下列的命令:"
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor_installation.mo b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor_installation.mo
new file mode 100644
index 0000000..b101c3a
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor_installation.mo
Binary files differ
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor_installation.po b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor_installation.po
new file mode 100644
index 0000000..dcbb0b5
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/hypervisor_installation.po
@@ -0,0 +1,5173 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:02-0400\n"
+"PO-Revision-Date: 2014-06-30 10:23+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# a5b708b1c7f34ebeb40e555178227b10
+#: ../../hypervisor_installation.rst:17
+msgid "Hypervisor Installation"
+msgstr "Hypervisor安装"
+
+# c97e1fa112814a849f7cd08e8f9d3c1e
+#: ../../hypervisor_installation.rst:20
+msgid "KVM Hypervisor Host Installation"
+msgstr "KVM Hypervisor主机安装"
+
+# 106ceeb500c947a88931ac644e73431d
+#: ../../hypervisor_installation.rst:23
+msgid "System Requirements for KVM Hypervisor Hosts"
+msgstr "KVM Hypervisor 主机系统要求"
+
+# afa4fe6e1df94ebeb7668c1cabb0ff0c
+#: ../../hypervisor_installation.rst:25
+msgid ""
+"KVM is included with a variety of Linux-based operating systems. Although "
+"you are not required to run these distributions, the following are "
+"recommended:"
+msgstr "KVM包含在多种基于Linux的操作系统中。尽管不作要求，但是我们推荐以下发行版："
+
+# 34c3bdfde3da4f2d9c34601a86f0afcf
+# a161e18b507540c096810a8ec29ef317
+#: ../../hypervisor_installation.rst:31 ../../hypervisor_installation.rst:3327
+msgid "CentOS / RHEL: 6.3"
+msgstr "CentOS / RHEL: 6.3"
+
+# 4ffd025eb47e4537b6eb5007d2b80629
+# 57d072c73c204d6e81f858aa46f60667
+#: ../../hypervisor_installation.rst:35 ../../hypervisor_installation.rst:3331
+msgid "Ubuntu: 12.04(.1)"
+msgstr "Ubuntu: 12.04(.1)"
+
+# 7decad4017784f2f96f7030e58f6f239
+#: ../../hypervisor_installation.rst:37
+msgid ""
+"The main requirement for KVM hypervisors is the libvirt and Qemu version. No"
+" matter what Linux distribution you are using, make sure the following "
+"requirements are met:"
+msgstr "KVM hypervisors主要要求在于libvirt和Qemu版本。不管您使用何种Linux版本，请确保满足以下要求："
+
+# aee585bafb434d2dbe9d2579ab1dcad5
+#: ../../hypervisor_installation.rst:43
+msgid "libvirt: 0.9.4 or higher"
+msgstr "libvirt: 0.9.4 或更高版本"
+
+# 008a79408bb34d52bf92873b8905dad3
+# 6364b35d5cdd483f87928821946c3f34
+#: ../../hypervisor_installation.rst:47 ../../hypervisor_installation.rst:3343
+msgid "Qemu/KVM: 1.0 or higher"
+msgstr "Qemu/KVM: 1.0 或更高版本"
+
+# 4bc408d879ad447baa475bfd0808aa65
+# 3dbbe376cdd24657968196a32f21fda6
+#: ../../hypervisor_installation.rst:49 ../../hypervisor_installation.rst:3345
+msgid ""
+"The default bridge in CloudStack is the Linux native bridge implementation "
+"(bridge module). CloudStack includes an option to work with OpenVswitch, the"
+" requirements are listed below"
+msgstr "CloudStack中的默认使用Linux本身的桥接(bridge模块)方式实现。也可选择在CloudStack中使用OpenVswitch，具体要求如下："
+
+# 34be33c099374c35aa8784190733b87c
+#: ../../hypervisor_installation.rst:55
+msgid "libvirt: 0.9.11 or higher"
+msgstr "libvirt: 0.9.11 或更高版本"
+
+# 7d3d628565264bc69adb04e77462b5b0
+# 4b4d3c51f3b746ed96a5bd61749758f4
+#: ../../hypervisor_installation.rst:59 ../../hypervisor_installation.rst:3355
+msgid "openvswitch: 1.7.1 or higher"
+msgstr "openvswitch: 1.7.1或更高版本"
+
+# 6b26016e861b4aaaba05f3bd8c98f682
+# 1e2e540227304e14b7a8406969608a5e
+#: ../../hypervisor_installation.rst:61 ../../hypervisor_installation.rst:3357
+msgid "In addition, the following hardware requirements apply:"
+msgstr "此外，硬件要求如下："
+
+# 322d406c43f64403bf5e8acfad80318d
+# 49490f42aa554579a0169795b8fec7cf
+#: ../../hypervisor_installation.rst:65 ../../hypervisor_installation.rst:3361
+msgid ""
+"Within a single cluster, the hosts must be of the same distribution version."
+msgstr "同一集群中主机必须使用相同版本的Linux系统。"
+
+# 86c9ea55ffec4f399b8e7918b7bb43d0
+# e392215de57d4843958e657b3d6d64c7
+#: ../../hypervisor_installation.rst:70 ../../hypervisor_installation.rst:3366
+msgid ""
+"All hosts within a cluster must be homogenous. The CPUs must be of the same "
+"type, count, and feature flags."
+msgstr "同一群集中的所有节点架构必须一致。CPU的型号、数量和功能参数必须相同。"
+
+# e6544c9e2bed4d36a8b7bf5e2b040667
+# 405d986c35fd4e35bba0d7ea5664327b
+# b176112062f840bf8e4293cb2b6dd440
+#: ../../hypervisor_installation.rst:75 ../../hypervisor_installation.rst:1027
+#: ../../hypervisor_installation.rst:3371
+msgid "Must support HVM (Intel-VT or AMD-V enabled)"
+msgstr "必须支持HVM(Intel-VT或者AMD-V)"
+
+# fe8c3dec4f5e48af82d6a1cf4d35c0fa
+# 222e2e6b7d72437fa9d1e291b1abae33
+# b6a567096cf14ce7a86b7cab8cd8a120
+# d2f00762290a412aada0abbdddc35042
+#: ../../hypervisor_installation.rst:79 ../../hypervisor_installation.rst:1051
+#: ../../hypervisor_installation.rst:2263
+#: ../../hypervisor_installation.rst:3375
+msgid "64-bit x86 CPU (more cores results in better performance)"
+msgstr "64位x86 CPU(多核性能更佳)"
+
+# 8a4b47d3dc3a44c584fbd97dcf25a5a0
+# 14006a14fa284ce6ba19f360f889a0bc
+# 6d7b9af582894902a3e1095cfa7f02fe
+# 130dbc2bf67d4a5687f09f35f760a482
+#: ../../hypervisor_installation.rst:83 ../../hypervisor_installation.rst:1059
+#: ../../hypervisor_installation.rst:2271
+#: ../../hypervisor_installation.rst:3379
+msgid "4 GB of memory"
+msgstr "4GB 内存"
+
+# e8bd701c4ef947078dfed764bd5fc6d9
+# 656d673c698d4b118d21cc9362a8e5dd
+# 947d8b3ed1974720a911fdb6b44d4d36
+# a4a079db675c46938452f27bc17e3e68
+#: ../../hypervisor_installation.rst:87 ../../hypervisor_installation.rst:1067
+#: ../../hypervisor_installation.rst:2279
+#: ../../hypervisor_installation.rst:3383
+msgid "At least 1 NIC"
+msgstr "至少一块网卡"
+
+# 3444db1dcb1f47258e2772864b74a072
+# 0d176e6f680c42f88456e42ff3bbc75c
+# eaf19bdaaac2446a9eba73346cfb272c
+#: ../../hypervisor_installation.rst:91 ../../hypervisor_installation.rst:1075
+#: ../../hypervisor_installation.rst:3387
+msgid ""
+"When you deploy CloudStack, the hypervisor host must not have any VMs "
+"already running"
+msgstr "在部署CloudStack时，Hypervisor主机不能运行任何虚拟机"
+
+# b090156a97514e25ae92874eabc12ebe
+#: ../../hypervisor_installation.rst:95
+msgid "KVM Installation Overview"
+msgstr "KVM安装概述"
+
+# 3c994a4c8bb44c3db12d9d1a91d88511
+#: ../../hypervisor_installation.rst:97
+msgid ""
+"If you want to use the Linux Kernel Virtual Machine (KVM) hypervisor to run "
+"guest virtual machines, install KVM on the host(s) in your cloud. The "
+"material in this section doesn't duplicate KVM installation docs. It "
+"provides the CloudStack-specific steps that are needed to prepare a KVM host"
+" to work with CloudStack."
+msgstr "如果你想使用 KVM hypervisor来运行虚拟机，请在你的云环境中安装KVM主机。本章节不会复述KVM的安装文档。它提供了KVM主机与CloudStack协同工作所要准备特有的步骤。"
+
+# 0ae1e0787a0a4b35bb60e6ce2270b93c
+# fbbc0d73551e4738b0780bf7ae39b794
+#: ../../hypervisor_installation.rst:105
+#: ../../hypervisor_installation.rst:3400
+msgid ""
+"Before continuing, make sure that you have applied the latest updates to "
+"your host."
+msgstr "在我们开始之前，请确保所有的主机都安装了最新的更新包。"
+
+# 3f404325440b43e8929f971c948bddd2
+# cdf930cc6f4f48cfbfa886bcea0c6c5c
+#: ../../hypervisor_installation.rst:109
+#: ../../hypervisor_installation.rst:3402
+msgid ""
+"It is NOT recommended to run services on this host not controlled by "
+"CloudStack."
+msgstr "不建议在主机中运行与CloudStack无关的服务。"
+
+# b4d910e8d72742e2992a140e0bbb07f9
+#: ../../hypervisor_installation.rst:111
+msgid "The procedure for installing a KVM Hypervisor Host is:"
+msgstr "安装KVM主机的过程："
+
+# f72c15c1878f4826b773a10ca9d09132
+# a5027d0749d5434b8990a4ce07b63190
+# cd85e26dfec64b0e85060beb3e51e135
+# 3f58fd5515bf4d7c95f3972fecc77a0f
+#: ../../hypervisor_installation.rst:115 ../../hypervisor_installation.rst:130
+#: ../../hypervisor_installation.rst:3408
+#: ../../hypervisor_installation.rst:3423
+msgid "Prepare the Operating System"
+msgstr "准备操作系统"
+
+# 2a8a33c0f29c40b2823be72c0a3ebbb4
+# c6bed6d3e6b248daa4040d12455fe55a
+#: ../../hypervisor_installation.rst:119
+#: ../../hypervisor_installation.rst:3412
+msgid "Install and configure libvirt"
+msgstr "安装和配置libvirt"
+
+# 1642991c8fbd4e90ac67a46c59e515a5
+# a94fc5d5847b4a85b0f6d0ee714b7b1f
+#: ../../hypervisor_installation.rst:123
+#: ../../hypervisor_installation.rst:3416
+msgid "Configure Security Policies (AppArmor and SELinux)"
+msgstr "配置安全策略 (AppArmor 和 SELinux)"
+
+# 1ed5a01ec0704f2eb18b408abd6cae9c
+# 52a64dac3f794d7d9402c6f757812a16
+# 0bf1c9bf0fa048cdb0bffdde08d78760
+# 0902ea5204d74d8faa9db44b32e93779
+#: ../../hypervisor_installation.rst:127 ../../hypervisor_installation.rst:185
+#: ../../hypervisor_installation.rst:3420
+#: ../../hypervisor_installation.rst:3477
+msgid "Install and configure the Agent"
+msgstr "安装和配置Agent"
+
+# 54165d82f02949c887291da9ef9385f7
+# 887757221dec4140950e28424103418d
+#: ../../hypervisor_installation.rst:132
+#: ../../hypervisor_installation.rst:3425
+msgid ""
+"The OS of the Host must be prepared to host the CloudStack Agent and run KVM"
+" instances."
+msgstr "主机的操作系统必须为运行CloudStack Agent和KVM实例做些准备。"
+
+# 3b1313122c04424eb3c0f4dea9099319
+# 209d2e9fe5a54af0a434c6fe42d67c94
+#: ../../hypervisor_installation.rst:137
+#: ../../hypervisor_installation.rst:3430
+msgid "Log in to your OS as root."
+msgstr "使用root用户登录操作系统。"
+
+# faa86bd264934b1b8bab5914670677e8
+# ec55ce15def44bbea72ff6f68842becc
+#: ../../hypervisor_installation.rst:141
+#: ../../hypervisor_installation.rst:3434
+msgid "Check for a fully qualified hostname."
+msgstr "检查FQN完全合格/限定主机名。"
+
+# 6e562892fc814c038043db4120089438
+# f775086cc87b40dab6aac8299ca88571
+#: ../../hypervisor_installation.rst:147
+#: ../../hypervisor_installation.rst:3440
+msgid ""
+"This should return a fully qualified hostname such as "
+"\"kvm1.lab.example.org\". If it does not, edit /etc/hosts so that it does."
+msgstr "该命令会返回完全合格/限定主机名，例如\"kvm1.lab.example.org\"。如果没有，请编辑 /etc/hosts。"
+
+# e009ff0ecafd4666a742d5af03d2309e
+# f85f5a8126094c72a1740ac354fc6e2f
+#: ../../hypervisor_installation.rst:153
+#: ../../hypervisor_installation.rst:3446
+msgid "Make sure that the machine can reach the Internet."
+msgstr "确保机器可以连接到互联网."
+
+# 56ca23a905364937bac5cf61701e8a09
+# de0710f8ee154254b3d424dc19901a33
+#: ../../hypervisor_installation.rst:161
+#: ../../hypervisor_installation.rst:3454
+msgid "Turn on NTP for time synchronization."
+msgstr "启用NTP服务以确保时间同步."
+
+# 0d18ab8873cc4b938d65ea7d9503d2f3
+# 2281cb7bd1ab44d0a18d9a382ae614d7
+#: ../../hypervisor_installation.rst:165
+#: ../../hypervisor_installation.rst:3457
+msgid ""
+"NTP is required to synchronize the clocks of the servers in your cloud. "
+"Unsynchronized clocks can cause unexpected problems."
+msgstr "NTP服务用来同步云中的服务器时间。时间不同步会带来意想不到的问题。"
+
+# 65aa5ea952b94cb3bcd5151c59496e4d
+# fb7ee24bb05540f9859ba3b87f03487c
+#: ../../hypervisor_installation.rst:170
+#: ../../hypervisor_installation.rst:3462
+msgid "Install NTP"
+msgstr "安装NTP"
+
+# e93ea97e77314f19b564fc3d5e981897
+# c859b30acde9440ca4835511741c38ac
+#: ../../hypervisor_installation.rst:182
+#: ../../hypervisor_installation.rst:3474
+msgid "Repeat all of these steps on every hypervisor host."
+msgstr "在所有主机中重复上述步骤。"
+
+# ea49f1e757d443beb13b7434fc7a6337
+#: ../../hypervisor_installation.rst:187
+msgid ""
+"To manage KVM instances on the host CloudStack uses a Agent. This Agent "
+"communicates with the Management server and controls all the instances on "
+"the host."
+msgstr "CloudStack使用Agent来管理KVM实例。Agent与管理服务器通讯并控制主机上所有的虚拟机。"
+
+# 34eb5632982c49a7ad56d679b8897bad
+# 84ca527264e445eb9b6965300ff5a67a
+#: ../../hypervisor_installation.rst:191
+#: ../../hypervisor_installation.rst:3483
+msgid "First we start by installing the agent:"
+msgstr "首先我们安装Agent："
+
+# d894051a1aa4420482cd5ecf26baf9b9
+# e209192de68d4bdb9b3cb14f77c59b1a
+# 0e50e758e1bd45628f4eee81cae74b1d
+# eb677ec246e749239198c0ef7edd5ff4
+# e2c94bf547f64410916a38d7e7fdd670
+# e86cca2d481a47539eef5083baa6edda
+#: ../../hypervisor_installation.rst:193 ../../hypervisor_installation.rst:361
+#: ../../hypervisor_installation.rst:402
+#: ../../hypervisor_installation.rst:3485
+#: ../../hypervisor_installation.rst:3608
+#: ../../hypervisor_installation.rst:3649
+msgid "In RHEL or CentOS:"
+msgstr "在RHEL/CentOS上:"
+
+# 3b6758b2ccb445b5be94a8dfc7ebd0a2
+# ade0da3eeb2941c49b1186cd22d03202
+# 0f363f2af00f4b159318dab564862baa
+# a14254a637a742dfa6d89b25b9b24656
+#: ../../hypervisor_installation.rst:199 ../../hypervisor_installation.rst:367
+#: ../../hypervisor_installation.rst:3491
+#: ../../hypervisor_installation.rst:3614
+msgid "In Ubuntu:"
+msgstr "在Ubuntu上:"
+
+# d096d4acc81e4e60834b9a24af414019
+# 8bd1adc0e2a34211956f1b708f3c9724
+# 1e3a5fd3b85f4bce9244ebdcc0b999ed
+# 78185f32c03c498db18b23abd0426910
+#: ../../hypervisor_installation.rst:205 ../../hypervisor_installation.rst:943
+#: ../../hypervisor_installation.rst:3525
+#: ../../hypervisor_installation.rst:4024
+msgid ""
+"The host is now ready to be added to a cluster. This is covered in a later "
+"section, see :ref:`adding-a-host`. It is recommended that you continue to "
+"read the documentation before adding the host!"
+msgstr "现在主机已经为加入群集做好准备。后面的章节有介绍，请参阅 :ref:`adding-a-host`。强烈建议在添加主机之前阅读此部分内容。"
+
+# af1b91fcf7484085b389fb8d502edcd6
+#: ../../hypervisor_installation.rst:211
+msgid "Configure CPU model for KVM guest (Optional)"
+msgstr "配置KVM虚拟机的CPU型号(可选)"
+
+# 7fdc1820edee46fca04097cd36443ade
+#: ../../hypervisor_installation.rst:213
+msgid ""
+"In additional,the CloudStack Agent allows host administrator to control the "
+"guest CPU model which is exposed to KVM instances. By default, the CPU model"
+" of KVM instance is likely QEMU Virtual CPU version x.x.x with least CPU "
+"features exposed. There are a couple of reasons to specify the CPU model:"
+msgstr "此外，CloudStack Agent允许主机管理员控制KVM实例中的CPU型号。默认情况下，KVM实例的CPU型号为只有少数CPU特性且版本为xxx的QEMU Virtual CPU。指定CPU型号有几个原因："
+
+# 55671888c52e4644b97eb76e5b37321a
+#: ../../hypervisor_installation.rst:221
+msgid ""
+"To maximise performance of instances by exposing new host CPU features to "
+"the KVM instances;"
+msgstr "通过主机CPU的特性最大化提升KVM实例的性能；"
+
+# 0076cb899b89481ba3c5032e2156b23a
+#: ../../hypervisor_installation.rst:226
+msgid ""
+"To ensure a consistent default CPU across all machines,removing reliance of "
+"variable QEMU defaults;"
+msgstr "确保所有机器的默认CPU保持一致，消除对QEMU变量的依赖。"
+
+# 06f0cd9e4f7148f2bf5661eb3a4bbb30
+#: ../../hypervisor_installation.rst:229
+msgid ""
+"For the most part it will be sufficient for the host administrator to "
+"specify the guest CPU config in the per-host configuration file "
+"(/etc/cloudstack/agent/agent.properties). This will be achieved by "
+"introducing two new configuration parameters:"
+msgstr "在大多数情况下,主机管理员需要每个主机配置文件(/etc/cloudstack/agent/agent.properties)中指定guest虚拟机的CPU配置。这将通过引入两个新的配置参数来实现："
+
+# 1a1c88bead1d4b90b16007da2a8049af
+#: ../../hypervisor_installation.rst:239
+msgid "There are three choices to fulfill the cpu model changes:"
+msgstr "更改CPU型号有三个选择："
+
+# 171cebf0991b4c7d82b4254c0b0a6fe7
+#: ../../hypervisor_installation.rst:243
+msgid ""
+"**custom:** you can explicitly specify one of the supported named model in "
+"/usr/share/libvirt/cpu\\_map.xml"
+msgstr "**custom:** 您可以指定一个在/usr/share/libvirt/cpu\\_map.xml文件中所支持的型号名称。"
+
+# ef3286604260487387d6ef81752d3ff4
+#: ../../hypervisor_installation.rst:248
+msgid ""
+"**host-model:** libvirt will identify the CPU model in "
+"/usr/share/libvirt/cpu\\_map.xml which most closely matches the host, and "
+"then request additional CPU flags to complete the match. This should give "
+"close to maximum functionality/performance, which maintaining good "
+"reliability/compatibility if the guest is migrated to another host with "
+"slightly different host CPUs."
+msgstr "**host-model:** libvirt可以识别出在/usr/share/libvirt/cpu\\_map.xml中与主机最接近的CPU型号，然后请求其他的CPU flags完成匹配。如果虚拟机迁移到其他CPU稍有不同的主机中，保持好的可靠性/兼容性能提供最多的功能和最大限度提示的性能。"
+
+# 80a634dd2c22483fb09655f8c07ff193
+#: ../../hypervisor_installation.rst:257
+msgid ""
+"**host-passthrough:** libvirt will tell KVM to passthrough the host CPU with"
+" no modifications. The difference to host-model, instead of just matching "
+"feature flags, every last detail of the host CPU is matched. This gives "
+"absolutely best performance, and can be important to some apps which check "
+"low level CPU details, but it comes at a cost with respect to migration: the"
+" guest can only be migrated to an exactly matching host CPU."
+msgstr "**host-passthrough:** libvirt 会告诉KVM没有修改过CPU passthrough的主机。与host-model的差别是不仅匹配flags特性，还要匹配CPU的每一个特性。他能提供最好的性能， 同时对一些检查CPU底层特性的应用程序很重要，但这样会带来一些迁移的代价：虚拟机只会迁移到CPU完全匹配的主机上。"
+
+# f58590a9696548528006493b8c7ae197
+#: ../../hypervisor_installation.rst:265
+msgid "Here are some examples:"
+msgstr "这里有一些示例："
+
+# 42ef165ce6ad4a9e9fa71eb044611a1b
+#: ../../hypervisor_installation.rst:269
+msgid "custom"
+msgstr "custom"
+
+# 91ceb895db0b4234a51b32614603068e
+#: ../../hypervisor_installation.rst:278
+msgid "host-model"
+msgstr "host-model"
+
+# 9eed04f7453b40529c43301d1de02fb8
+#: ../../hypervisor_installation.rst:286
+msgid "host-passthrough"
+msgstr "host-passthrough"
+
+# dfb22be926364168a84d5cb0b7e44b35
+#: ../../hypervisor_installation.rst:292
+msgid ""
+"host-passthrough may lead to migration failure,if you have this problem,you "
+"should use host-model or custom"
+msgstr "host-passthrough可能会导致迁移失败，如果你遇到这个问题，你应该使用 host-model或者custom"
+
+# a5e533a4e79649c2ac3ce750357ee34a
+# 4d3de60d913b41398d75fad799393017
+#: ../../hypervisor_installation.rst:295
+#: ../../hypervisor_installation.rst:3531
+msgid "Install and Configure libvirt"
+msgstr "安装和配置libvirt"
+
+# bf3b3baffb30458eae7af5d56a51a573
+# fd165c09e19c4204af9a194d9e0209fb
+#: ../../hypervisor_installation.rst:297
+#: ../../hypervisor_installation.rst:3533
+msgid ""
+"CloudStack uses libvirt for managing virtual machines. Therefore it is vital"
+" that libvirt is configured correctly. Libvirt is a dependency of "
+"cloudstack-agent and should already be installed."
+msgstr "CloudStack使用libvirt管理虚拟机。因此正确地配置libvirt至关重要。CloudStack-agent依赖于Libvirt，应提前安装完毕。"
+
+# ff42e0ea9cf64b509d310c0071086352
+# 5b89b062abbe4cc89b7fd10ece8eb9e8
+#: ../../hypervisor_installation.rst:303
+#: ../../hypervisor_installation.rst:3539
+msgid ""
+"In order to have live migration working libvirt has to listen for unsecured "
+"TCP connections. We also need to turn off libvirts attempt to use Multicast "
+"DNS advertising. Both of these settings are in "
+"``/etc/libvirt/libvirtd.conf``"
+msgstr "为了实现动态迁移libvirt需要监听不可靠的TCP连接。还要关闭libvirts尝试使用组播DNS进行广播。这些都可以在 /etc/libvirt/libvirtd.conf文件中进行配置。"
+
+# 9d2c6d97644043c98a8afdfca63ce7ba
+# 62f76e0671a940e38a4ad3785ad3829e
+#: ../../hypervisor_installation.rst:308
+#: ../../hypervisor_installation.rst:3544
+msgid "Set the following parameters:"
+msgstr "设定下列参数："
+
+# 7bf432c121e6497e815bce7ac5f768c2
+# 5c250e445c544d819ef81c56946c9817
+#: ../../hypervisor_installation.rst:332
+#: ../../hypervisor_installation.rst:3568
+msgid ""
+"Turning on \"listen\\_tcp\" in libvirtd.conf is not enough, we have to "
+"change the parameters as well:"
+msgstr "除了在libvirtd.conf中打开\"listen_tcp\"以外，我们还必须修改/etc/sysconfig/libvirtd中的参数:"
+
+# dff877a089444785a919c9a4ddc1505b
+# 09f64fb99e4f4746998fccfb45d8ffbe
+#: ../../hypervisor_installation.rst:335
+#: ../../hypervisor_installation.rst:3571
+msgid "On RHEL or CentOS modify ``/etc/sysconfig/libvirtd``:"
+msgstr "在RHEL或者CentOS中修改 ``/etc/sysconfig/libvirtd``："
+
+# dc8b92c2767f4d3aa010cafa32e0ffc0
+# 5137041fbceb450dafdafdd8050d781b
+#: ../../hypervisor_installation.rst:337
+#: ../../hypervisor_installation.rst:3573
+msgid "Uncomment the following line:"
+msgstr "取消如下行的注释："
+
+# f8fa69e0aaf0441ebbd5376315dde649
+# 2c026065c68143c7abdc5ca2fc2436ea
+#: ../../hypervisor_installation.rst:343
+#: ../../hypervisor_installation.rst:3579
+msgid "On Ubuntu: modify ``/etc/default/libvirt-bin``"
+msgstr "在Ubuntu中:修改 ``/etc/default/libvirt-bin`` "
+
+# b1e0a030287c4eb99b535ef0a0e008cd
+# e7c84f512f6b40c5ae74177fcbef4e7b
+#: ../../hypervisor_installation.rst:345
+#: ../../hypervisor_installation.rst:3581
+msgid "Add \"-l\" to the following line"
+msgstr "在下列行添加 \"-l\""
+
+# fb23df2bb85243918f17fce3511a292f
+# 3f9045ba6c8042cd95dbf7cfaf068566
+#: ../../hypervisor_installation.rst:351
+#: ../../hypervisor_installation.rst:3587
+msgid "so it looks like:"
+msgstr "如下所示:"
+
+# e9f3700ad8c545ec9162775958e52903
+# 12a8cf99f91a4bfebfef63061401b984
+#: ../../hypervisor_installation.rst:359
+#: ../../hypervisor_installation.rst:3606
+msgid "Restart libvirt"
+msgstr "重启libvirt服务"
+
+# 8a64baac6d7643dda067b886a5c80ae3
+# 396a781a4a1d4985aa57fc33ab909171
+#: ../../hypervisor_installation.rst:374
+#: ../../hypervisor_installation.rst:3621
+msgid "Configure the Security Policies"
+msgstr "配置安全策略"
+
+# 071b22fa7fe84b5184dcaee305d367f9
+# ba196eddcd1a4db0b3bc5debca46897c
+#: ../../hypervisor_installation.rst:376
+#: ../../hypervisor_installation.rst:3623
+msgid ""
+"CloudStack does various things which can be blocked by security mechanisms "
+"like AppArmor and SELinux. These have to be disabled to ensure the Agent has"
+" all the required permissions."
+msgstr "CloudStack的会被例如AppArmor和SELinux的安全机制阻止。必须关闭安全机制并确保 Agent具有所必需的权限。"
+
+# 66c0547791744ea9a1bf3f4b86157e56
+# a13c1564e14a40a98d164cdc3bfad868
+#: ../../hypervisor_installation.rst:382
+#: ../../hypervisor_installation.rst:3629
+msgid "Configure SELinux (RHEL and CentOS)"
+msgstr "配置SELinux（RHEL和CentOS）："
+
+# ad5bbcda3fb94378926b1b5e5c49fef5
+# 3bc6b9a75a864efca77472f3a7083402
+#: ../../hypervisor_installation.rst:386
+#: ../../hypervisor_installation.rst:3633
+msgid ""
+"Check to see whether SELinux is installed on your machine. If not, you can "
+"skip this section."
+msgstr "检查你的机器是否安装了SELinux。如果没有，请跳过此部分。"
+
+# 186d81a15e7149da89ee20ce59cc48dc
+# 51df5058cd4f43938789667b0444df12
+#: ../../hypervisor_installation.rst:389
+#: ../../hypervisor_installation.rst:3636
+msgid ""
+"In RHEL or CentOS, SELinux is installed and enabled by default. You can "
+"verify this with:"
+msgstr "在RHEL或者CentOS中，SELinux是默认安装并启动的。你可以使用如下命令验证："
+
+# 5c9517056a764377bd38722748343a49
+# 47aa2dbec53247e09633898939b840d7
+#: ../../hypervisor_installation.rst:398
+#: ../../hypervisor_installation.rst:3645
+msgid ""
+"Set the SELINUX variable in ``/etc/selinux/config`` to \"permissive\". This "
+"ensures that the permissive setting will be maintained after a system "
+"reboot."
+msgstr "在 ``/etc/selinux/config`` 中设置SELINUX变量值为 \"permissive\"。这样能确保对SELinux的设置在系统重启之后依然生效。"
+
+# 93857dbce0f54cb68f9fda82a8cd692c
+# 34854b97c968469aa89f9b69611024e4
+#: ../../hypervisor_installation.rst:408
+#: ../../hypervisor_installation.rst:3655
+msgid "Change the following line"
+msgstr "查找如下行"
+
+# 0e1313c89e3b415ebee6bbc8671f120a
+# fb6153f02ea1423088ece2501fda504f
+#: ../../hypervisor_installation.rst:414
+#: ../../hypervisor_installation.rst:3661
+msgid "to this"
+msgstr "修改为"
+
+# 29a646ccf1ad4545bac2923aabe1b97c
+# 80ca6532afc24061b27c23b6118bdf65
+#: ../../hypervisor_installation.rst:422
+#: ../../hypervisor_installation.rst:3669
+msgid ""
+"Then set SELinux to permissive starting immediately, without requiring a "
+"system reboot."
+msgstr "然后使SELinux立即运行于permissive模式，无需重新启动系统。"
+
+# 5ce95d10c98449d7b6f2c0ac20da948c
+# c3cf4cecfad547a8a307e334e4503f59
+#: ../../hypervisor_installation.rst:431
+#: ../../hypervisor_installation.rst:3678
+msgid "Configure Apparmor (Ubuntu)"
+msgstr "配置AppArmor(Ubuntu)"
+
+# 87b92b4c575e4c95813f1e9af3b04d77
+# 07b7d10f1b3e49d8952e5b635b7eca2a
+#: ../../hypervisor_installation.rst:435
+#: ../../hypervisor_installation.rst:3682
+msgid ""
+"Check to see whether AppArmor is installed on your machine. If not, you can "
+"skip this section."
+msgstr "检查你的机器中是否安装了AppArmor。如果没有，请跳过此部分。"
+
+# 50e7a0a081684c489805ccda2c5717d6
+# 491c0892c7ef48b18767fafac079a62b
+#: ../../hypervisor_installation.rst:438
+#: ../../hypervisor_installation.rst:3685
+msgid ""
+"In Ubuntu AppArmor is installed and enabled by default. You can verify this "
+"with:"
+msgstr "Ubuntu中默认安装并启动AppArmor。使用如下命令验证："
+
+# 8e560cd81d0544eb8f9bb401145dea8e
+# 26d2ddef7e5f4c29a57ab9455120b3f3
+#: ../../hypervisor_installation.rst:447
+#: ../../hypervisor_installation.rst:3694
+msgid "Disable the AppArmor profiles for libvirt"
+msgstr "在AppArmor配置文件中禁用libvirt"
+
+# 930e8f602c664befbf6c46bcea1cbe7e
+# 5a5ec5e627f84217a2de1c1a9692d83d
+#: ../../hypervisor_installation.rst:466
+#: ../../hypervisor_installation.rst:3713
+msgid "Configure the network bridges"
+msgstr "配置网络桥接"
+
+# bccb9ebfa523410e95ffbeec12d8b4df
+# c27b62ef62564bce8bbcdebbbc78a2e6
+# eaf1d1b6a92b4d26923b5a26f2d8f6e3
+#: ../../hypervisor_installation.rst:468 ../../hypervisor_installation.rst:680
+#: ../../hypervisor_installation.rst:3715
+msgid ""
+"This is a very important section, please make sure you read this thoroughly."
+msgstr "本章节非常重要，请务必彻底理解。"
+
+# 37ea1b1181cf4de494d126cdc40a801d
+# 0c2793bb0202408da6ef10e2b99b6eaa
+#: ../../hypervisor_installation.rst:470
+#: ../../hypervisor_installation.rst:3718
+msgid ""
+"This section details how to configure bridges using the native "
+"implementation in Linux. Please refer to the next section if you intend to "
+"use OpenVswitch"
+msgstr "本章节详细介绍了如何使用Linux自带的软件配置桥接网络。如果要使用OpenVswitch，请看下一章节。"
+
+# 2bf55b978c5a475ebcd65da90eb6386a
+# 994c7b0b85ac4fd4957bf9212cb5afbd
+# 40d0ecab11134b1f984bf6d89271cbd4
+#: ../../hypervisor_installation.rst:472 ../../hypervisor_installation.rst:682
+#: ../../hypervisor_installation.rst:3720
+msgid ""
+"In order to forward traffic to your instances you will need at least two "
+"bridges: *public* and *private*."
+msgstr "为了转发流量到实例，至少需要两个桥接网络： *public* 和 *private*。"
+
+# 68eec8c1d0fd4c34a086b108e1ba4a0b
+# 9785a42437c44a48932befa909c24f05
+# b2947b2e839f4cf9a79ddafa66b1b8e0
+#: ../../hypervisor_installation.rst:475 ../../hypervisor_installation.rst:685
+#: ../../hypervisor_installation.rst:3723
+msgid ""
+"By default these bridges are called *cloudbr0* and *cloudbr1*, but you do "
+"have to make sure they are available on each hypervisor."
+msgstr " 默认情况下，这些桥接被称为*cloudbr0*和*cloudbr1*，但必须确保他们在每个hypervisor上都是可用的。"
+
+# fd73cf9a6c174db1a1d0a7a7b0febf8f
+# c6b6935f5a0241319a435306ff08f613
+# d7f8015ac99a49b7a8f2bdd03074f25e
+#: ../../hypervisor_installation.rst:478 ../../hypervisor_installation.rst:688
+#: ../../hypervisor_installation.rst:3726
+msgid ""
+"The most important factor is that you keep the configuration consistent on "
+"all your hypervisors."
+msgstr "最重要的因素是所有hypervisors上的配置要保持一致。"
+
+# aecc917b1cfc4ae0829bf38e71b146a1
+# dcd1dd91023f487bac62a498068bc7d3
+# 61678fddd1354bc299cc7a3f18060a1b
+#: ../../hypervisor_installation.rst:482 ../../hypervisor_installation.rst:705
+#: ../../hypervisor_installation.rst:3730
+msgid "Network example"
+msgstr "网络示例"
+
+# fcb6675f3cbf47bd84f39d85c831b62c
+# 6446967b0b204707837f42e08d7b998a
+# 116a752e270144b9ae56210887f4ad80
+#: ../../hypervisor_installation.rst:484 ../../hypervisor_installation.rst:707
+#: ../../hypervisor_installation.rst:3732
+msgid ""
+"There are many ways to configure your network. In the Basic networking mode "
+"you should have two (V)LAN's, one for your private network and one for the "
+"public network."
+msgstr "配置网络有很多方法。在基本网络模式中你应该拥有2个 (V)LAN，一个用于管理网络，一个用于公共网络。"
+
+# 15d921dedb524980b41aafbd170bec51
+# 7956438fead040698f6cced9c78a2b6c
+# 8eefa91987504ceb9f915423bd9cd7ee
+#: ../../hypervisor_installation.rst:488 ../../hypervisor_installation.rst:711
+#: ../../hypervisor_installation.rst:3736
+msgid ""
+"We assume that the hypervisor has one NIC (eth0) with three tagged VLAN's:"
+msgstr "假设hypervisor中的网卡(eth0)有3个VLAN标签："
+
+# 0877467f5181444597ffc59798a984c2
+# e05717e09bf44963b799a357f63d06c0
+# 9c3b52a0f37349628d7e9863b22f7586
+#: ../../hypervisor_installation.rst:493 ../../hypervisor_installation.rst:716
+#: ../../hypervisor_installation.rst:3741
+msgid "VLAN 100 for management of the hypervisor"
+msgstr "VLAN 100 作为hypervisor的管理网络"
+
+# d0358c8e6e704280a94d8154520cc512
+# 9d4164a76748495290ea59d97dfde5f0
+# 7db7cbd5fdbd485cab9d24025b7d7812
+#: ../../hypervisor_installation.rst:497 ../../hypervisor_installation.rst:720
+#: ../../hypervisor_installation.rst:3745
+msgid "VLAN 200 for public network of the instances (cloudbr0)"
+msgstr " VLAN 200 作为实例的公共网络 (cloudbr0)"
+
+# 1f92bbd42f4848b7824c11163deccdce
+# 386e672345ad4798b937956aa78f982d
+# bca715eb0552403c97ecabf386e7ba9c
+#: ../../hypervisor_installation.rst:501 ../../hypervisor_installation.rst:724
+#: ../../hypervisor_installation.rst:3749
+msgid "VLAN 300 for private network of the instances (cloudbr1)"
+msgstr "VLAN 300 作为实例的专用网络 (cloudbr1)"
+
+# aa94795c65f344c89c206c32fe15d941
+# 48a286c49f7441b19ed5ef3435348d59
+# dc43104aac9543c78fafa5f30dffaa8b
+#: ../../hypervisor_installation.rst:503 ../../hypervisor_installation.rst:726
+#: ../../hypervisor_installation.rst:3751
+msgid ""
+"On VLAN 100 we give the Hypervisor the IP-Address 192.168.42.11/24 with the "
+"gateway 192.168.42.1"
+msgstr "在VLAN 100 中，配置Hypervisor的IP为 192.168.42.11/24，网关为192.168.42.1"
+
+# 6d48a58cd57f46238b8aaf12909c69d1
+# b8bb257a296c4bed98f1dad806ad5ba1
+# 900d19465df34526bfc636edfdb5534c
+#: ../../hypervisor_installation.rst:506 ../../hypervisor_installation.rst:729
+#: ../../hypervisor_installation.rst:3754
+msgid ""
+"The Hypervisor and Management server don't have to be in the same subnet!"
+msgstr "Hypervisor与管理服务器不需要在同一个子网！"
+
+# c32119ed14d44cb8bc32676656b99910
+# d879c320747d4850b1c5bacdd29a1669
+# 83f2160f524f43cf869a63489a608275
+#: ../../hypervisor_installation.rst:509 ../../hypervisor_installation.rst:732
+#: ../../hypervisor_installation.rst:3757
+msgid "Configuring the network bridges"
+msgstr "配置网络桥接"
+
+# a80e5f8891a44a56affd76a4611c1785
+# c623ed65e9ba45b89f407ce4339a56e1
+#: ../../hypervisor_installation.rst:511
+#: ../../hypervisor_installation.rst:3759
+msgid ""
+"It depends on the distribution you are using how to configure these, below "
+"you'll find examples for RHEL/CentOS and Ubuntu."
+msgstr "配置方式取决于发行版类型，下面给出RHEL/CentOS和Ubuntu的配置示例。"
+
+# 1bb4087b2e5548119e9075fa05467ff9
+# 1992bd1a538a4e87aff11f08a30811ca
+#: ../../hypervisor_installation.rst:514
+#: ../../hypervisor_installation.rst:3762
+msgid ""
+"The goal is to have two bridges called 'cloudbr0' and 'cloudbr1' after this "
+"section. This should be used as a guideline only. The exact configuration "
+"will depend on your network layout."
+msgstr "本章节的目标是配置两个名为 'cloudbr0'和'cloudbr1'的桥接网络。这仅仅是指导性的，实际情况还要取决于你的网络布局。"
+
+# adab06c881724079959a8ae96aa924d0
+# 4978f5c0d9024cceb5523422d9f6e3c3
+# b5304e1cd17b43d49387c9e1f0dc4600
+#: ../../hypervisor_installation.rst:517 ../../hypervisor_installation.rst:759
+#: ../../hypervisor_installation.rst:3765
+msgid "Configure in RHEL or CentOS"
+msgstr "在RHEL或CentOS中配置："
+
+# 95d2aaf4ea374d68ab231cf69aa771db
+# 6ee3e4cd4ddd42eda7adf6a56c2de197
+#: ../../hypervisor_installation.rst:519
+#: ../../hypervisor_installation.rst:3767
+msgid ""
+"The required packages were installed when libvirt was installed, we can "
+"proceed to configuring the network."
+msgstr "网络桥接所需的软件在安装libvirt时就已被安装，继续配置网络。"
+
+# 029a729a30a646bb882fa28fc6f4faf5
+# 13fa6771f34e4579bc8dba5e243a4011
+# d8e2cd1aa3de4613894102d0d8dfc562
+#: ../../hypervisor_installation.rst:522 ../../hypervisor_installation.rst:764
+#: ../../hypervisor_installation.rst:3770
+msgid "First we configure eth0"
+msgstr "首先配置eth0："
+
+# dfdfd4f9776841959c87e33436d420ff
+# a055bef8a0304bf0827ea85c3116ff08
+# 175ef63f2d0e4d568e5df9298b56ef1f
+#: ../../hypervisor_installation.rst:528 ../../hypervisor_installation.rst:770
+#: ../../hypervisor_installation.rst:3776
+msgid "Make sure it looks similar to:"
+msgstr "确保内容如下所示："
+
+# aa158cdf890f4a73aa02cee971b29325
+# 937d87800fba4c0c93874a7e1764bf85
+#: ../../hypervisor_installation.rst:539
+#: ../../hypervisor_installation.rst:3787
+msgid "We now have to configure the three VLAN interfaces:"
+msgstr "现在配置3个VLAN接口："
+
+# 476469f3cb3a44b0b7782a599edaaf84
+# 9fcd4bb8ee1f4977b938630771b1dab2
+#: ../../hypervisor_installation.rst:588
+#: ../../hypervisor_installation.rst:3836
+msgid ""
+"Now we have the VLAN interfaces configured we can add the bridges on top of "
+"them."
+msgstr "配置VLAN接口以便能够附加桥接网络。"
+
+# d77a52bf367046fdbce73058d169f265
+# d2eac1f518d24368b764df3e08aacb22
+#: ../../hypervisor_installation.rst:595
+#: ../../hypervisor_installation.rst:3843
+msgid "Now we just configure it is a plain bridge without an IP-Address"
+msgstr "现在只配置一个没有IP的桥接。"
+
+# 0188228d5cff43fc939e85ab6c002118
+# 39f78adfcd624290b0564d41b3447db2
+#: ../../hypervisor_installation.rst:608
+#: ../../hypervisor_installation.rst:3856
+msgid "We do the same for cloudbr1"
+msgstr "同样建立cloudbr1"
+
+# 218608446e8e45528b00bea4c57ebab9
+# f929fa3761b04167bda58c3a6f67cbfa
+# cdec6d4dfc5f4e95a212712a3bc64a61
+# dde4ad6a203a4cd58b6fe12d2f745b30
+# 2210405cea3845758c377fea3f5a3a2e
+#: ../../hypervisor_installation.rst:625 ../../hypervisor_installation.rst:672
+#: ../../hypervisor_installation.rst:840
+#: ../../hypervisor_installation.rst:3873
+#: ../../hypervisor_installation.rst:3920
+msgid ""
+"With this configuration you should be able to restart the network, although "
+"a reboot is recommended to see if everything works properly."
+msgstr "配置完成之后重启网络，通过重启检查一切是否正常。"
+
+# 9ced5c3d4eeb4f27b12cd0cb9f044a90
+# b88351fb9a7b43b09d7230cb38ae4c58
+# 1f463bc97d1147db85bec0e461319336
+# de08a3e8c75f461ea791f59685988cb5
+# a0974a28a6fa4008ae279ad0685d47f5
+#: ../../hypervisor_installation.rst:628 ../../hypervisor_installation.rst:675
+#: ../../hypervisor_installation.rst:843
+#: ../../hypervisor_installation.rst:3876
+#: ../../hypervisor_installation.rst:3923
+msgid ""
+"Make sure you have an alternative way like IPMI or ILO to reach the machine "
+"in case you made a configuration error and the network stops functioning!"
+msgstr "在发生配置错误和网络故障的时，请确保可以能通过其他方式例如IPMI或ILO连接到服务器。"
+
+# 17acbbca1f3345849046fa6c4ebed4fc
+# 8cdc0e43e63641789dc4bd075c3d0bc3
+#: ../../hypervisor_installation.rst:631
+#: ../../hypervisor_installation.rst:3879
+msgid "Configure in Ubuntu"
+msgstr "在Ubuntu中配置："
+
+# 41f30048a88c4bb993a0d890f181b28d
+# 93e837e2bf274c668eee8f0a619c4a5d
+#: ../../hypervisor_installation.rst:633
+#: ../../hypervisor_installation.rst:3881
+msgid ""
+"All the required packages were installed when you installed libvirt, so we "
+"only have to configure the network."
+msgstr "在安装libvirt时所需的其他软件也会被安装，所以只需配置网络即可。"
+
+# 01fb8740e0b9423d8b655864775af54e
+# 262554e455a648fabdf442b6e301f259
+#: ../../hypervisor_installation.rst:640
+#: ../../hypervisor_installation.rst:3888
+msgid "Modify the interfaces file to look like this:"
+msgstr "如下所示修改接口文件："
+
+# e332c16e171f47169b256805eafe7615
+#: ../../hypervisor_installation.rst:678
+msgid "Configure the network using OpenVswitch"
+msgstr "配置使用OpenVswitch网络"
+
+# aa202fe73fee4c45827aa38313f60aec
+#: ../../hypervisor_installation.rst:692
+msgid "Preparing"
+msgstr "准备"
+
+# eca14b3123854338ba1f14a14829b739
+#: ../../hypervisor_installation.rst:694
+msgid ""
+"To make sure that the native bridge module will not interfere with "
+"openvswitch the bridge module should be added to the blacklist. See the "
+"modprobe documentation for your distribution on where to find the blacklist."
+" Make sure the module is not loaded either by rebooting or executing rmmod "
+"bridge before executing next steps."
+msgstr "将系统自带的网络桥接模块加入黑名单，确保该模块不会与openvswitch模块冲突。请参阅你所使用发行版的modprobe文档并找到黑名单。确保该模块不会在重启时自动加载或在下一操作步骤之前卸载该桥接模块。"
+
+# bf7a4c48ba2a4e4fa616e9e4415abcc7
+#: ../../hypervisor_installation.rst:700
+msgid ""
+"The network configurations below depend on the ifup-ovs and ifdown-ovs "
+"scripts which are part of the openvswitch installation. They should be "
+"installed in /etc/sysconfig/network-scripts/"
+msgstr "以下网络配置依赖ifup-ovs和ifdown-ovs脚本，安装openvswitch后会提供该脚本。安装路径为位/etc/sysconfig/network-scripts/。"
+
+# 4d690db0a1544fd29d71656ec0ffcefd
+#: ../../hypervisor_installation.rst:734
+msgid ""
+"It depends on the distribution you are using how to configure these, below "
+"you'll find examples for RHEL/CentOS."
+msgstr "如何配置这些文件取决于你使用的发行版本，在下面的内容中会提供RHEL/CentOS下的示例。"
+
+# ee8734ea127c4e8f8b66e5c4dea71bbf
+#: ../../hypervisor_installation.rst:737
+msgid ""
+"The goal is to have three bridges called 'mgmt0', 'cloudbr0' and 'cloudbr1' "
+"after this section. This should be used as a guideline only. The exact "
+"configuration will depend on your network layout."
+msgstr "本章节的目标是设置三个名为'mgmt0', 'cloudbr0'和'cloudbr1' 桥接网络。这仅仅是指导性的，实际情况还要取决于你的网络状况。"
+
+# a74c6627f02043d5be917f12e7d0b263
+#: ../../hypervisor_installation.rst:740
+msgid "Configure OpenVswitch"
+msgstr "配置OpenVswitch"
+
+# e34d3c3a549a4b5e90ffd8f8afa33b07
+#: ../../hypervisor_installation.rst:742
+msgid ""
+"The network interfaces using OpenVswitch are created using the ovs-vsctl "
+"command. This command will configure the interfaces and persist them to the "
+"OpenVswitch database."
+msgstr "使用ovs-vsctl命令创建基于OpenVswitch的网络接口。该命令将配置此接口并将信息保存在OpenVswitch数据库中。"
+
+# fc0396cdb2c247b4ba0851d2b478d8c9
+#: ../../hypervisor_installation.rst:746
+msgid ""
+"First we create a main bridge connected to the eth0 interface. Next we "
+"create three fake bridges, each connected to a specific vlan tag."
+msgstr "首先我们创建一个连接至eth0接口的主桥接。然后我们创建三个虚拟桥接，每个桥接都连接指定的VLAN。"
+
+# 02df0e7f19b4486bbaada2d6b794b9ad
+#: ../../hypervisor_installation.rst:761
+msgid ""
+"The required packages were installed when openvswitch and libvirt were "
+"installed, we can proceed to configuring the network."
+msgstr "所需的安装包在安装openvswitch和libvirt的时就已经安装，继续配置网络。"
+
+# afab5f01a1714f0cb60ff9eed2db599d
+#: ../../hypervisor_installation.rst:781
+msgid "We have to configure the base bridge with the trunk."
+msgstr "必须将基础桥接配置为trunk模式。"
+
+# e104896bad1742b5b84682172fbd9b32
+#: ../../hypervisor_installation.rst:796
+msgid "We now have to configure the three VLAN bridges:"
+msgstr "现在对三个VLAN桥接进行配置："
+
+# 3564d9d50ea44f139e404791fd72f0af
+# 02fce31af22c4ed5abbd727f13ad05f0
+#: ../../hypervisor_installation.rst:846
+#: ../../hypervisor_installation.rst:3926
+msgid "Configuring the firewall"
+msgstr "配置防火墙"
+
+# 2db1d0f133da4a66a7b2907acedd42a9
+# 5b0f650e2d114047a0415b7ea57f3251
+#: ../../hypervisor_installation.rst:848
+#: ../../hypervisor_installation.rst:3928
+msgid ""
+"The hypervisor needs to be able to communicate with other hypervisors and "
+"the management server needs to be able to reach the hypervisor."
+msgstr "hypervisor之间和hypervisor与管理服务器之间要能够通讯。"
+
+# 935242b052ff490e9ad7270b8ddce890
+# 8c950a2e6b57475fa7752ffa9ed1e5bd
+#: ../../hypervisor_installation.rst:851
+#: ../../hypervisor_installation.rst:3931
+msgid ""
+"In order to do so we have to open the following TCP ports (if you are using "
+"a firewall):"
+msgstr "为了达到这个目的，我们需要开通以下TCP端口(如果使用防火墙)："
+
+# cb69e4cdb8684774badfb4574559faa0
+# ae914c26a05444f9837e3ea892d275e2
+#: ../../hypervisor_installation.rst:856
+#: ../../hypervisor_installation.rst:3936
+msgid "22 (SSH)"
+msgstr "22 (SSH)"
+
+# 3807a267ba4b47248846cb82be68d71e
+# 8d4a188d4a5c42408f9a9da6c952d345
+#: ../../hypervisor_installation.rst:860
+#: ../../hypervisor_installation.rst:3940
+msgid "1798"
+msgstr "1798"
+
+# 87b8b1e5c9924af5b368bcbb7d2e8148
+# 130a835b7e534e1aad8b66a350c80a9c
+#: ../../hypervisor_installation.rst:864
+#: ../../hypervisor_installation.rst:3944
+msgid "16509 (libvirt)"
+msgstr "16509 (libvirt)"
+
+# eb66ea04a90b4b46bd6c5529c74201b7
+# 332c2e7a9cdc40909b84e4bb4a550a92
+#: ../../hypervisor_installation.rst:868
+#: ../../hypervisor_installation.rst:3948
+msgid "5900 - 6100 (VNC consoles)"
+msgstr "5900 - 6100 (VNC 控制台)"
+
+# a65af6b9acbf47a08b1f7222b105fd4f
+# 709185e3e76045d6a3a6d0df2f61efb3
+#: ../../hypervisor_installation.rst:872
+#: ../../hypervisor_installation.rst:3952
+msgid "49152 - 49216 (libvirt live migration)"
+msgstr "49152 - 49216 (libvirt在线迁移)"
+
+# aa084591023a46ccb4cea81e8cc0baea
+# bc3288c0a792458c9d188c275d27a458
+#: ../../hypervisor_installation.rst:874
+#: ../../hypervisor_installation.rst:3954
+msgid ""
+"It depends on the firewall you are using how to open these ports. Below "
+"you'll find examples how to open these ports in RHEL/CentOS and Ubuntu."
+msgstr "如何打开这些端口取决于你使用的发行版本。在RHEL/CentOS 及Ubuntu中的示例如下。"
+
+# 7129650cbfc6416d8d015c4a64781ac8
+# 65d598aa7b414f5393a37799d4c2c1a2
+#: ../../hypervisor_installation.rst:878
+#: ../../hypervisor_installation.rst:3958
+msgid "Open ports in RHEL/CentOS"
+msgstr "在RHEL/CentOS中打开端口"
+
+# bb6efe14098442169446a2cfaf0ddfa0
+# e5bb8f2688ff41b98cf556f60758aa87
+#: ../../hypervisor_installation.rst:880
+#: ../../hypervisor_installation.rst:3960
+msgid ""
+"RHEL and CentOS use iptables for firewalling the system, you can open extra "
+"ports by executing the following iptable commands:"
+msgstr "RHEL 及 CentOS使用iptables作为防火墙，执行以下iptables命令来开启端口："
+
+# d68286a4499a42d0af59d58cf3307ce8
+# cabb0609f32c4af983aec749c9a3bde6
+#: ../../hypervisor_installation.rst:903
+#: ../../hypervisor_installation.rst:3983
+msgid ""
+"These iptable settings are not persistent accross reboots, we have to save "
+"them first."
+msgstr "这些iptables配置并不会持久保存，重启之后将会消失，我们必须手动保存这些配置。"
+
+# 307b4260b7a74cd392d59bb3418c7eb8
+# a54b92341f454cf3aee68b8a07bd8108
+#: ../../hypervisor_installation.rst:911
+#: ../../hypervisor_installation.rst:3991
+msgid "Open ports in Ubuntu"
+msgstr "在Ubuntu中打开端口："
+
+# 8f7697ea5cda4eeeae5602b276f55313
+# ca6e09ab840f496fa590a392c3c0fcb1
+#: ../../hypervisor_installation.rst:913
+#: ../../hypervisor_installation.rst:3993
+msgid ""
+"The default firewall under Ubuntu is UFW (Uncomplicated FireWall), which is "
+"a Python wrapper around iptables."
+msgstr "Ubuntu中的默认防火墙是UFW(Uncomplicated FireWall)，使用Python围绕iptables进行包装。"
+
+# 036e661454dd43b6bcf5724a4cfc8e21
+# 63b5466496e643e5adac39e7c08d34f7
+#: ../../hypervisor_installation.rst:916
+#: ../../hypervisor_installation.rst:3996
+msgid "To open the required ports, execute the following commands:"
+msgstr "要打开所需端口，请执行以下命令："
+
+# d199e9f02aa34c2e998aba25484840c8
+# f7ee2acc10334a4bb43bb2cb66688c77
+#: ../../hypervisor_installation.rst:938
+#: ../../hypervisor_installation.rst:4019
+msgid ""
+"By default UFW is not enabled on Ubuntu. Executing these commands with the "
+"firewall disabled does not enable the firewall."
+msgstr "默认情况下，Ubuntu中并未启用UFW。在关闭情况下执行这些命令并不能启用防火墙。"
+
+# f6fb4b8f7864465a8e8b2c9c726ec59c
+# 16dd0d2c501d4beea5ff4ef875698cd4
+#: ../../hypervisor_installation.rst:941
+#: ../../hypervisor_installation.rst:4022
+msgid "Add the host to CloudStack"
+msgstr "添加主机到CloudStack"
+
+# 870fb106f927434690fac18321ce0e59
+#: ../../hypervisor_installation.rst:949
+msgid "Hypervisor Support for Primary Storage"
+msgstr "Hypervisor对主存储的支持"
+
+# 11b373255a32403a97695fb159fd09d9
+#: ../../hypervisor_installation.rst:951
+msgid ""
+"The following table shows storage options and parameters for different "
+"hypervisors."
+msgstr "下表显示了针对不同Hypervisors的存储选项和参数。"
+
+# 71d9dffcec0844acb2949eb60cea1944
+#: ../../hypervisor_installation.rst:955
+msgid "Primary Storage Type"
+msgstr "主存储类型"
+
+# 0b37e00477ab432691d060c0c73f3257
+#: ../../hypervisor_installation.rst:955
+msgid "vSphere"
+msgstr "vSphere"
+
+# 7129c9b88c17431f9d16cb9947a677a7
+#: ../../hypervisor_installation.rst:955
+msgid "XenServer"
+msgstr "XenServer"
+
+# 71094f1d15124724a6a0e6213b1d6daf
+#: ../../hypervisor_installation.rst:955
+msgid "KVM"
+msgstr "KVM"
+
+# 09568b1f16e7426cab559aa9770bb87e
+# cfd57be6b2324793bc6c05ad29e6f751
+#: ../../hypervisor_installation.rst:955
+#: ../../hypervisor_installation.rst:1963
+msgid "Hyper-V"
+msgstr "Hyper-V"
+
+# 7046ca99b00143a18a1ac6585ea583d5
+#: ../../hypervisor_installation.rst:957
+msgid "****Format for Disks, Templates, and Snapshots****"
+msgstr "****磁盘、模板和快照的格式****"
+
+# 5ab36f207b4146588dd7917af86aa5b7
+#: ../../hypervisor_installation.rst:957
+msgid "VMDK"
+msgstr "VMDK"
+
+# 1d7d1640e1344432b8b4c9f64e6e3de5
+# e52e9c78a0de4ad8960d9ed8d6604e7d
+#: ../../hypervisor_installation.rst:957 ../../hypervisor_installation.rst:957
+msgid "VHD"
+msgstr "VHD"
+
+# 73411b9629ba423fa63a082dc31e04af
+#: ../../hypervisor_installation.rst:957
+msgid "QCOW2"
+msgstr "QCOW2"
+
+# e66d4e3fef6549cd950eb5a969eaec5a
+#: ../../hypervisor_installation.rst:958
+msgid "**iSCSI support**"
+msgstr "**支持iSCSI**"
+
+# 6791f19ffe8c492383fd9e09030fe664
+# 9f409f8d387c4d46becc2b3ee6499050
+#: ../../hypervisor_installation.rst:958 ../../hypervisor_installation.rst:959
+msgid "VMFS"
+msgstr "VMFS"
+
+# 6a8d18eb6310463b8b26ce7341385c5d
+#: ../../hypervisor_installation.rst:958
+msgid "CLVM"
+msgstr "CLVM"
+
+# 155ee7758b3b41aabd23851828723f07
+# 9b26e9f40b634c0d9829308022399474
+#: ../../hypervisor_installation.rst:958 ../../hypervisor_installation.rst:959
+msgid "Yes, via Shared Mountpoint"
+msgstr "支持，通过Shared Mountpoint"
+
+# ebeb1e87b3f440c0a9fa499698356297
+# 0b052a6c7d9a489ba64df2bf64913d0d
+# 3111e9e35d434428bd654afbef6e4661
+# 90ea1419362d4e61bdbbde02d29a56a9
+# 67db36f9276b461a9f2dc0a6c75a84f3
+# 48b9e13cfdf048599e7c03490006ccb4
+# 16b7d2f7dac94f76a225e10445cf619f
+#: ../../hypervisor_installation.rst:958 ../../hypervisor_installation.rst:959
+#: ../../hypervisor_installation.rst:960 ../../hypervisor_installation.rst:962
+#: ../../hypervisor_installation.rst:963 ../../hypervisor_installation.rst:963
+#: ../../hypervisor_installation.rst:963
+msgid "No"
+msgstr "否"
+
+# 7d8573527e8a4bfba998b4d3ddf99bb7
+#: ../../hypervisor_installation.rst:959
+msgid "**Fiber Channel support**"
+msgstr "**支持FC**"
+
+# 451dcefc9c6c470491dfea9998e24809
+#: ../../hypervisor_installation.rst:959
+msgid "Yes, via Existing SR"
+msgstr "支持，通过已有的SR"
+
+# d36f043836cb43d9b60ee86d2ad41f62
+#: ../../hypervisor_installation.rst:960
+msgid "**NFS support**"
+msgstr "**支持NFS**"
+
+# 50ad2c0fcf9644c9a4a7c65f8ddcb5fa
+# b7dc2cbb224a4aa886eb6e569412cc82
+# 80a2fd8cf583437ebb542a1d060a0042
+# d06590ec3fc948149d7dd2172c4f6b06
+# be7e08adfd054b1ba87844c789deb247
+# f29c49b5074b4c57a993f973a89e4c78
+# 54d3e136689647ed8412737ac2ba6b93
+# 140e1d436e5343bf99920962e3cb2fc0
+#: ../../hypervisor_installation.rst:960 ../../hypervisor_installation.rst:960
+#: ../../hypervisor_installation.rst:960 ../../hypervisor_installation.rst:961
+#: ../../hypervisor_installation.rst:961 ../../hypervisor_installation.rst:961
+#: ../../hypervisor_installation.rst:961 ../../hypervisor_installation.rst:963
+msgid "Yes"
+msgstr "是"
+
+# ac8413ce909b4b7395fadd007b26c9ff
+#: ../../hypervisor_installation.rst:961
+msgid "**Local storage support**"
+msgstr "**支持本地存储**"
+
+# 24ab7203b4c943739c6926678f0d0803
+#: ../../hypervisor_installation.rst:962
+msgid "**Storage over-provisioning**"
+msgstr "**存储超配**"
+
+# e2e7fabe2be14351b704696cea18fa20
+#: ../../hypervisor_installation.rst:962
+msgid "NFS and iSCSI"
+msgstr "NFS 和 iSCSI"
+
+# 39253a1a6513430b8e09aaf5098c74ef
+# 42778c796f7740bf85e16e509c1496f4
+#: ../../hypervisor_installation.rst:962 ../../hypervisor_installation.rst:962
+msgid "NFS"
+msgstr "NFS"
+
+# b9588ec4a2be4b1696503c5e85cc3a84
+#: ../../hypervisor_installation.rst:963
+msgid "**SMB/CIFS**"
+msgstr "**SMB/CIFS**"
+
+# 7644794bf16d47c18ed02b558352bea1
+#: ../../hypervisor_installation.rst:966
+msgid ""
+"XenServer uses a clustered LVM system to store VM images on iSCSI and Fiber "
+"Channel volumes and does not support over-provisioning in the hypervisor. "
+"The storage server itself, however, can support thin-provisioning. As a "
+"result the CloudStack can still support storage over-provisioning by running"
+" on thin-provisioned storage volumes."
+msgstr "XenServer通过在iSCSI和FC卷上使用集群化的LVM系统来存储VM镜像，并且不支持存储超配。尽管存储本身支持自动精简配置。不过CloudStack仍然支持在有自动精简配置的存储卷上使用存储超配。"
+
+# d20bddfa830e48d99978bd5eab502169
+#: ../../hypervisor_installation.rst:972
+msgid ""
+"KVM supports \"Shared Mountpoint\" storage. A shared mountpoint is a file "
+"system path local to each server in a given cluster. The path must be the "
+"same across all Hosts in the cluster, for example /mnt/primary1. This shared"
+" mountpoint is assumed to be a clustered filesystem such as OCFS2. In this "
+"case the CloudStack does not attempt to mount or unmount the storage as is "
+"done with NFS. The CloudStack requires that the administrator insure that "
+"the storage is available"
+msgstr "KVM支持 \"Shared Mountpoint\"存储。Shared Mountpoint是群集中每个服务器本地文件系统中的一个路径。群集所有主机中的该路径必须一致，比如/mnt/primary1。并假设Shared Mountpoint是一个集群文件系统如OCFS2。在这种情况下，CloudStack不会把它当做NFS存储去尝试挂载或卸载。CloudStack需要管理员确保该存储是可用的。"
+
+# 8cc2529993044886a2edc38f568aa43d
+#: ../../hypervisor_installation.rst:980
+msgid ""
+"With NFS storage, CloudStack manages the overprovisioning. In this case the "
+"global configuration parameter storage.overprovisioning.factor controls the "
+"degree of overprovisioning. This is independent of hypervisor type."
+msgstr "在NFS存储中，CloudStack管理超配。这种情况下，使用全局配置参数storage.overprovisioning.factor来控制超配的范围。且不受hyperviso类型约束。"
+
+# b1c2b65035cd42b5b242d8245827be53
+#: ../../hypervisor_installation.rst:985
+msgid ""
+"Local storage is an option for primary storage for vSphere, XenServer, and "
+"KVM. When the local disk option is enabled, a local disk storage pool is "
+"automatically created on each host. To use local storage for the System "
+"Virtual Machines (such as the Virtual Router), set "
+"system.vm.use.local.storage to true in global configuration."
+msgstr "在vSphere, XenServer和KVM中，本地存储是一个可选项。当选择了使用本地存储，所有主机会自动创建本地存储池。想要系统虚拟机 (例如虚拟路由器)使用本地存储，请设置全局配置参数system.vm.use.local.storage为true."
+
+# 2874ceeecfc747368a0daa2f4b670a8d
+#: ../../hypervisor_installation.rst:991
+msgid ""
+"CloudStack supports multiple primary storage pools in a Cluster. For "
+"example, you could provision 2 NFS servers in primary storage. Or you could "
+"provision 1 iSCSI LUN initially and then add a second iSCSI LUN when the "
+"first approaches capacity."
+msgstr "CloudStack支持在一个群集内有多个主存储池。比如，使用2个NFS服务器提供主存储。或原有的1个iSCSI LUN达到一定容量时再添加第二个iSCSI LUN。"
+
+# bb8410c437ae4dfc83006d467deab5ee
+#: ../../hypervisor_installation.rst:997
+msgid "Citrix XenServer Installation for CloudStack"
+msgstr "为CloudStack安装Citrix XenServer"
+
+# f039a87fd91f4cf5af82b5a0d0e14279
+#: ../../hypervisor_installation.rst:999
+msgid ""
+"If you want to use the Citrix XenServer hypervisor to run guest virtual "
+"machines, install XenServer 6.0 or XenServer 6.0.2 on the host(s) in your "
+"cloud. For an initial installation, follow the steps below. If you have "
+"previously installed XenServer and want to upgrade to another version, see "
+":ref:`upgrading-xenserver-version`."
+msgstr "如果你想用Citrix XenServer作为hypervisor运行虚拟机，安装XenServer 6.0或XenServer 6.0.2版本。你需要按照以下步骤来完成初次安装。如果你想从之前的旧版本升级，请参阅 :ref:`upgrading-xenserver-version`。"
+
+# 1393db47eb314f93ac51b5df28608757
+#: ../../hypervisor_installation.rst:1006
+msgid "System Requirements for XenServer Hosts"
+msgstr "XenServer主机的系统要求"
+
+# cee59e8c9fbe4466b998c22c775285aa
+#: ../../hypervisor_installation.rst:1010
+msgid ""
+"The host must be certified as compatible with one of the following. See the "
+"Citrix Hardware Compatibility Guide: `http://hcl.xensource.com "
+"<http://hcl.xensource.com>`_"
+msgstr "主机必须通过下列任一版本的兼容性认证。请查看Citrix硬件兼容性指导: `http://hcl.xensource.com <http://hcl.xensource.com>`_"
+
+# f3b55d603c69440cac3ff406039da6fa
+#: ../../hypervisor_installation.rst:1014
+msgid "XenServer 5.6 SP2"
+msgstr "XenServer 5.6 SP2"
+
+# be0e05f590c548658fc054e3b7c183c4
+#: ../../hypervisor_installation.rst:1015
+msgid "XenServer 6.0"
+msgstr "XenServer 6.0"
+
+# 859b34a50d8a47b98924d9bc9e66bf34
+#: ../../hypervisor_installation.rst:1016
+msgid "XenServer 6.0.2"
+msgstr "XenServer 6.0.2"
+
+# f62ad598aa04405db735768bcd28f3cb
+#: ../../hypervisor_installation.rst:1017
+msgid "XenServer 6.1.0"
+msgstr "XenServer 6.1.0"
+
+# 1ef19600bf954890ba8ab95144a9dbe9
+#: ../../hypervisor_installation.rst:1018
+msgid "XenServer 6.2.0"
+msgstr "XenServer 6.2.0"
+
+# 7f67c993b17a4b25a8b436331132a38b
+#: ../../hypervisor_installation.rst:1022
+msgid ""
+"You must re-install Citrix XenServer if you are going to re-use a host from "
+"a previous install."
+msgstr "如果你想使用以前装的某台主机,你必须重新安装Citrix XenServer."
+
+# 79b4544cf3614dd7a7be4fb67c18c3cc
+#: ../../hypervisor_installation.rst:1031
+msgid ""
+"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."
+msgstr "确保安装了所有系统补丁供应商提供的所有系统补丁。请随时关注供应商的技术支持渠道，一旦发布补丁，请尽快打上补丁。CloudStack不会跟踪或提醒你安装这些程序。安装最新的补丁对主机至关重要。虚拟化供应商可能不会对过期的系统提供技术支持。"
+
+# 00bde44b482f4ea297f009d4d8544f68
+#: ../../hypervisor_installation.rst:1042
+msgid ""
+"All hosts within a cluster must be homogeneous. The CPUs must be of the same"
+" type, count, and feature flags."
+msgstr "集群中的主机必须是相同架构。CPU的型号、数量和功能参数必须相同。"
+
+# 1cc62dcb812144349e992ef157bc7f1e
+#: ../../hypervisor_installation.rst:1047
+msgid "Must support HVM (Intel-VT or AMD-V enabled in BIOS)"
+msgstr "必须支持HVM（BIOS中要打开Intel-VT或者AMD-V）"
+
+# 7f48c8f440f3456a9675ec430f73fa14
+# 91c80a6655bf4e15999366adc5579b63
+#: ../../hypervisor_installation.rst:1055
+#: ../../hypervisor_installation.rst:2267
+msgid "Hardware virtualization support required"
+msgstr "硬件虚拟化支持"
+
+# edf681afdf084f4d95b31b905feef83e
+# b0c94baa01744e5d9a09a5a1a9be638f
+#: ../../hypervisor_installation.rst:1063
+#: ../../hypervisor_installation.rst:2275
+msgid "36 GB of local disk"
+msgstr "36GB本地磁盘空间"
+
+# 2627aa6551664c18b24d53f01d85fdc9
+# 7d643f0e7d854677adf01b1b91684194
+#: ../../hypervisor_installation.rst:1071
+#: ../../hypervisor_installation.rst:2283
+msgid "Statically allocated IP Address"
+msgstr "静态分配的IP"
+
+# 86b1054dd7df47728888bb09e899e58e
+#: ../../hypervisor_installation.rst:1078
+msgid ""
+"The lack of up-do-date hotfixes can lead to data corruption and lost VMs."
+msgstr "缺乏最新补丁更新可能会导致数据和虚拟机丢失。"
+
+# ffb7f7e0b7d54edd842322b6dbd130bc
+#: ../../hypervisor_installation.rst:1081
+msgid "XenServer Installation Steps"
+msgstr "XenServer安装步骤"
+
+# d29bd0f1992445e7bfe899ec7fdcd3bc
+#: ../../hypervisor_installation.rst:1085
+msgid ""
+"From `https://www.citrix.com/English/ss/downloads/ "
+"<https://www.citrix.com/English/ss/downloads/>`_, download the appropriate "
+"version of XenServer for your CloudStack version (see `\"System Requirements"
+" for XenServer Hosts\" <#system-requirements-for-xenserver-hosts>`_). "
+"Install it using the Citrix XenServer Installation Guide."
+msgstr " 从 `https://www.citrix.com/English/ss/downloads/ <https://www.citrix.com/English/ss/downloads/>`_下载适合CloudStack的XenServer版本 (查看 `\"XenServer主机的系统要求\" <#system-requirements-for-xenserver-hosts>`_)。使用XenServer安装向导安装XenServer。"
+
+# e4ff84caeefa4cdb9ff96d78ed4795bc
+#: ../../hypervisor_installation.rst:1091
+msgid "Older Versions of XenServer:"
+msgstr "较旧版本的XenServer："
+
+# dfbef4c3b3e74946805482a145c437ea
+#: ../../hypervisor_installation.rst:1093
+msgid ""
+"Note that you can download the most recent release of XenServer without "
+"having a Citrix account. If you wish to download older versions, you will "
+"need to create an account and look through the download archives."
+msgstr "下载最新版本的XenServer不需要使用Citrix账户。如果你要下载旧版本的XenServer，你需要注册一个账户。"
+
+# a1f3be6636a2457095084a99017c2bef
+#: ../../hypervisor_installation.rst:1099
+msgid "Configure XenServer dom0 Memory"
+msgstr "配置XenServer dom0内存"
+
+# 3d95fa3b3a0e4b1eb92dd506d58da069
+#: ../../hypervisor_installation.rst:1101
+msgid ""
+"Configure the XenServer dom0 settings to allocate more memory to dom0. This "
+"can enable XenServer to handle larger numbers of virtual machines. We "
+"recommend 2940 MB of RAM for XenServer dom0. For instructions on how to do "
+"this, see `http://support.citrix.com/article/CTX126531 "
+"<http://support.citrix.com/article/CTX126531>`_. The article refers to "
+"XenServer 5.6, but the same information applies to XenServer 6.0."
+msgstr "配置XenServer dom0占用更大的内存可以使XenServer运行更多的虚拟机。我们建议修改为2940MB。如何来做这些更改，请看 `http://support.citrix.com/article/CTX126531 <http://support.citrix.com/article/CTX126531>`_。这篇文档是针对XenServer 5.6的，但同样适用于XenServer6.0。"
+
+# 9e46ff13cb284bb9bdfbe4141e984bc3
+#: ../../hypervisor_installation.rst:1110
+msgid "Username and Password"
+msgstr "用户名和密码"
+
+# 47b11d036dff42a990eebaab43d6265b
+#: ../../hypervisor_installation.rst:1112
+msgid ""
+"All XenServers in a cluster must have the same username and password as "
+"configured in CloudStack."
+msgstr "CloudStack中同一群集下的所有XenServer主机必须拥有同样的用户名和密码。"
+
+# 04e9a76db62743b99541eca7808c3339
+#: ../../hypervisor_installation.rst:1116
+msgid "Time Synchronization"
+msgstr "时间同步"
+
+# 9fa198ee495f4b84b0bba7fd628e2e92
+#: ../../hypervisor_installation.rst:1118
+msgid ""
+"The host must be set to use NTP. All hosts in a pod must have the same time."
+msgstr "主机必须配置NTP。同一提供点中的所有主机时间必须相同。"
+
+# 4726eec6f10347b99a5e8076a1285988
+#: ../../hypervisor_installation.rst:1123
+msgid "Install NTP."
+msgstr "安装NTP."
+
+# 5682aee95db547028f5e82cd70b046d7
+#: ../../hypervisor_installation.rst:1131
+msgid "Edit the NTP configuration file to point to your NTP server."
+msgstr "编辑NTP配置文件指定NTP服务器。"
+
+# 1ce6772b97fb4129b0a526a33bfd18fa
+#: ../../hypervisor_installation.rst:1137
+msgid ""
+"Add one or more server lines in this file with the names of the NTP servers "
+"you want to use. For example:"
+msgstr "在文件中添加一行或多行你想使用的服务器地址. 例如:"
+
+# 69791d782a3541ca94d6c4751ec78f1f
+#: ../../hypervisor_installation.rst:1149
+msgid "Restart the NTP client."
+msgstr "重启NTP客户端。"
+
+# 3b608298222445408c6e4d00c8b36707
+#: ../../hypervisor_installation.rst:1157
+msgid "Make sure NTP will start again upon reboot."
+msgstr "确保机器重启之后NTP会自动启动。"
+
+# 0fcd0d55ec7049b69a3427a227e67180
+#: ../../hypervisor_installation.rst:1165
+msgid "Install CloudStack XenServer Support Package (CSP)"
+msgstr "安装 CloudStack XenServer 支持包(CSP)"
+
+# ae16a3a52b0343d8b17bdbe5440015f1
+#: ../../hypervisor_installation.rst:1167
+msgid "(Optional)"
+msgstr "(可选)"
+
+# 030bdd1824914aac90fb1170106765ba
+#: ../../hypervisor_installation.rst:1169
+msgid ""
+"To enable security groups, elastic load balancing, and elastic IP on "
+"XenServer, download and install the CloudStack XenServer Support Package "
+"(CSP). After installing XenServer, perform the following additional steps on"
+" each XenServer host."
+msgstr "要在XenServer上启用安全组、弹性负载均衡和弹性IP，请下载安装CloudStack XenServer支持包(CSP)。安装完XenServer之后，在每台XenServer主机上执行下列步骤。"
+
+# 41fcedb714c14a428ca6a9efe5a1d42f
+#: ../../hypervisor_installation.rst:1176
+msgid ""
+"Download the CSP software onto the XenServer host from one of the following "
+"links:"
+msgstr "请从下列链接之一下载CSP至XenServer主机："
+
+# f29bec21956d4917be7874f1b6a4177e
+#: ../../hypervisor_installation.rst:1179
+msgid "For XenServer 6.0.2:"
+msgstr "适用于XenServer 6.0.2："
+
+# 54880e3acb4945b4ae3d3fb251252130
+#: ../../hypervisor_installation.rst:1181
+msgid ""
+"`http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz "
+"<http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-"
+"supp.tgz>`_"
+msgstr "`http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/3.0.1/XS-6.0.2/xenserver-cloud-supp.tgz>`_"
+
+# 4405c659cea34cb2895c0f43693473f1
+#: ../../hypervisor_installation.rst:1183
+msgid "For XenServer 5.6 SP2:"
+msgstr "适用于XenServer 5.6 SP2:"
+
+# b1533b01dec04d8ea37cb07d541d8013
+#: ../../hypervisor_installation.rst:1185
+msgid ""
+"`http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz "
+"<http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz>`_"
+msgstr "`http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/2.2.0/xenserver-cloud-supp.tgz>`_"
+
+# 994df5c8945149b7b8663a2e603fc847
+#: ../../hypervisor_installation.rst:1187
+msgid "For XenServer 6.0:"
+msgstr "适用于XenServer 6.0:"
+
+# bc80c4fa363248c292882b511d90808a
+#: ../../hypervisor_installation.rst:1189
+msgid ""
+"`http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz "
+"<http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz>`_"
+msgstr "`http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz <http://download.cloud.com/releases/3.0/xenserver-cloud-supp.tgz>`_"
+
+# 09db532336c943caa7e4713f7f57deaa
+#: ../../hypervisor_installation.rst:1193
+msgid "Extract the file:"
+msgstr "解压文件："
+
+# 08830377e2e845879acf2acd9cb55ecf
+# aa4d385951184c16a90f45c0c3c5137a
+#: ../../hypervisor_installation.rst:1201
+#: ../../hypervisor_installation.rst:1825
+msgid "Run the following script:"
+msgstr "执行下列脚本："
+
+# 72924509d484445a81886c53211f2d14
+#: ../../hypervisor_installation.rst:1209
+msgid ""
+"If the XenServer host is part of a zone that uses basic networking, disable "
+"Open vSwitch (OVS):"
+msgstr "如果XenServer主机所在的区域使用的是基本网络模式 ，请禁用Open vSwitch (OVS):"
+
+# adb679b9cadf4ab587ebaa643690988a
+#: ../../hypervisor_installation.rst:1216
+msgid "Restart the host machine when prompted."
+msgstr "操作完成之后重启主机。"
+
+# bd826e8c78c04cf2ac613043dd1aa8ef
+#: ../../hypervisor_installation.rst:1218
+msgid "The XenServer host is now ready to be added to CloudStack."
+msgstr "现在可以在CloudStack中添加XenServer。"
+
+# 4d2cc4a9829c43c79dffee9dffb52d68
+#: ../../hypervisor_installation.rst:1221
+msgid "Primary Storage Setup for XenServer"
+msgstr "为XenServer配置主存储"
+
+# b0cc4d49e6d34d9db259e314792c0177
+#: ../../hypervisor_installation.rst:1223
+msgid ""
+"CloudStack natively supports NFS, iSCSI and local storage. If you are using "
+"one of these storage types, there is no need to create the XenServer Storage"
+" Repository (\"SR\")."
+msgstr "CloudStack原生支持NFS，iSCSI和本地存储。如果使用其中的一种存储类型，则不需要创建XenServer存储库(\"SR\")。"
+
+# a62837dbc9e1484d9a2ec93a3f386570
+#: ../../hypervisor_installation.rst:1227
+msgid ""
+"If, however, you would like to use storage connected via some other "
+"technology, such as FiberChannel, you must set up the SR yourself. To do so,"
+" perform the following steps. If you have your hosts in a XenServer pool, "
+"perform the steps on the master node. If you are working with a single "
+"XenServer which is not part of a cluster, perform the steps on that "
+"XenServer."
+msgstr "但是，如果你想使用其他技术的存储，如FC存储，你必须自行设置SR。请按以下步骤操作来设置SR。如果你要设置的主机存在于XenServer池中，请在master主机上执行这些操作。如果是单台节点主机，则在该XenServer主机上操作即可。"
+
+# 81eef0c2ce0249b3a2530d8dd37184b8
+#: ../../hypervisor_installation.rst:1236
+msgid ""
+"Connect FiberChannel cable to all hosts in the cluster and to the "
+"FiberChannel storage host."
+msgstr "通过光纤通道将集群中的所有主机连接至光纤存储设备"
+
+# b7ae02e3677b4008a1be03a37f030f35
+#: ../../hypervisor_installation.rst:1241
+msgid ""
+"Rescan the SCSI bus. Either use the following command or use XenCenter to "
+"perform an HBA rescan."
+msgstr "重新扫描SCSI总线。使用下列命令或者在XenCenter中使用HBA rescan按钮来完成扫描。"
+
+# 0476baafcfbc4751a7b674d69113d59f
+#: ../../hypervisor_installation.rst:1250
+msgid "Repeat step 2 on every host."
+msgstr "在所有主机上重复步骤2."
+
+# 02f48106fb6144b7b2382f5073d07199
+#: ../../hypervisor_installation.rst:1254
+msgid "Check to be sure you see the new SCSI disk."
+msgstr "检查确保已经识别到新的SCSI磁盘。"
+
+# 37c8fa1fc8f84752a31863e7c7d8120d
+#: ../../hypervisor_installation.rst:1260
+msgid ""
+"The output should look like this, although the specific file name will be "
+"different (scsi-<scsiID>):"
+msgstr "输出结果如下所示，指定的文件名稍许不同(scsi-<scsiID>):"
+
+# d30a16069dcf439f859e28c39d871bdb
+#: ../../hypervisor_installation.rst:1270
+msgid "Repeat step 4 on every host."
+msgstr "在所有主机上重复步骤4"
+
+# d057bb9cd0164ff2af5b7b284a2f70bc
+#: ../../hypervisor_installation.rst:1274
+msgid ""
+"On the storage server, run this command to get a unique ID for the new SR."
+msgstr "在存储服务器中，运行下列命令获取新添加SR的唯一ID标识。"
+
+# 78a081f2a72e4bea8db0fd3c3d5789df
+#: ../../hypervisor_installation.rst:1281
+msgid ""
+"The output should look like this, although the specific ID will be "
+"different:"
+msgstr "输出结果如下所示，指定的ID不同："
+
+# faf5a8ab93ff4086828b6dc2491f0fd4
+#: ../../hypervisor_installation.rst:1290
+msgid ""
+"Create the FiberChannel SR. In name-label, use the unique ID you just "
+"generated."
+msgstr "创建FC SR 。在name-label中，输入刚才获取的ID。"
+
+# c1a12adfd4e246b9ad5592e39b85708c
+#: ../../hypervisor_installation.rst:1299
+msgid ""
+"This command returns a unique ID for the SR, like the following example "
+"(your ID will be different):"
+msgstr "这条命令会获取SR的ID，以下面为例（你的UUID不同）："
+
+# f32c1d33fc9f40779169b42513227c6b
+#: ../../hypervisor_installation.rst:1308
+msgid ""
+"To create a human-readable description for the SR, use the following "
+"command. In uuid, use the SR ID returned by the previous command. In name-"
+"description, set whatever friendly text you prefer."
+msgstr "使用下面的命令为SR创建通俗易懂的描述, uuid参数使用使用之前命令返回的SR ID. 在名称描述中，设置任何你自己喜欢的描述。"
+
+# b754f3a8e4df433090a93bb35257fecd
+#: ../../hypervisor_installation.rst:1316
+msgid ""
+"Make note of the values you will need when you add this storage to "
+"CloudStack later (see `\"Add Primary Storage\" <configuration.html#add-"
+"primary-storage>`_). In the Add Primary Storage dialog, in Protocol, you "
+"will choose PreSetup. In SR Name-Label, you will enter the name-label you "
+"set earlier (in this example, e6849e96-86c3-4f2c-8fcc-350cc711be3d)."
+msgstr "记录这些值，之后在CloudStack中添加存储时会用到(查看 `\"添加主存储\" <configuration.html#add-primary-storage>`_)。在添加主存储对话框中的协议一项，选择PreSetup。在SR Name-Label中，输入之前设置的 name-label（在本示例中为e6849e96-86c3-4f2c-8fcc-350cc711be3d）。"
+
+# bb2c0a059376456fb6bca7407c545e10
+#: ../../hypervisor_installation.rst:1324
+msgid ""
+"(Optional) If you want to enable multipath I/O on a FiberChannel SAN, refer "
+"to the documentation provided by the SAN vendor."
+msgstr "(可选)如果想在FC SAN上启用多路径I/O，请参考SAN供应商提供的文档。"
+
+# f948cd8634034bd188d213da27d061f1
+#: ../../hypervisor_installation.rst:1328
+msgid "iSCSI Multipath Setup for XenServer (Optional)"
+msgstr "XenServer iSCSI多路径设置（可选）"
+
+# 2f15691307f84faaade1ec0f85382c0a
+#: ../../hypervisor_installation.rst:1330
+msgid ""
+"When setting up the storage repository on a Citrix XenServer, you can enable"
+" multipath I/O, which uses redundant physical components to provide greater "
+"reliability in the connection between the server and the SAN. To enable "
+"multipathing, use a SAN solution that is supported for Citrix servers and "
+"follow the procedures in Citrix documentation. The following links provide a"
+" starting point:"
+msgstr "在Citrix XenServer上配置存储库时，你可以启用多路径I/O，它是通过在服务器与SAN设备之间提供冗余的物理组件实现，提供了更高的可靠性。要启用多路径，请使用 XenServer文档中提供的SAN驱动程序。从下面链接开始："
+
+# c3e151c53ba543aa9a5c48cd1282a74b
+#: ../../hypervisor_installation.rst:1339
+msgid ""
+"`http://support.citrix.com/article/CTX118791 "
+"<http://support.citrix.com/article/CTX118791>`_"
+msgstr "`http://support.citrix.com/article/CTX118791 <http://support.citrix.com/article/CTX118791>`_"
+
+# 341d6153e8204ea697144d7f714fd80d
+#: ../../hypervisor_installation.rst:1343
+msgid ""
+"`http://support.citrix.com/article/CTX125403 "
+"<http://support.citrix.com/article/CTX125403>`_"
+msgstr "`http://support.citrix.com/article/CTX125403 <http://support.citrix.com/article/CTX125403>`_"
+
+# d88b03c3c9134875a81d6f6fcda13a65
+#: ../../hypervisor_installation.rst:1345
+msgid ""
+"You can also ask your SAN vendor for advice about setting up your Citrix "
+"repository for multipathing."
+msgstr "你同样可以咨询SAN提供商提供关于配置Citrix存储库多路径的建议。"
+
+# 01ad0cb79f9448c48d411af178ff801e
+#: ../../hypervisor_installation.rst:1348
+msgid ""
+"Make note of the values you will need when you add this storage to the "
+"CloudStack later (see `\"Add Primary Storage\" <configuration.html#add-"
+"primary-storage>`_). In the Add Primary Storage dialog, in Protocol, you "
+"will choose PreSetup. In SR Name-Label, you will enter the same name used to"
+" create the SR."
+msgstr "记录这些值，之后在CloudStack中添加存储时将会用到(查看 `\"添加主存储\" <configuration.html#add-primary-storage>`_)。在添加主存储对话框中的协议一项，选择PreSetup。在SR Name-Label中，输入之前创建的SR名称。"
+
+# d447c7f93a09485c9104d3e0c6f30ed4
+#: ../../hypervisor_installation.rst:1353
+msgid ""
+"If you encounter difficulty, address the support team for the SAN provided "
+"by your vendor. If they are not able to solve your issue, see Contacting "
+"Support."
+msgstr "如果遇到任何困难, 请通过SAN供应商团队获得支持. 如果仍然无法解决你的问题, 请联系技术支持."
+
+# 3462935ca70247d4ad640ed9fc026627
+#: ../../hypervisor_installation.rst:1358
+msgid "Physical Networking Setup for XenServer"
+msgstr "XenServer物理网络设置"
+
+# 96146639e1894252a9993fb4085347e3
+#: ../../hypervisor_installation.rst:1360
+msgid ""
+"Once XenServer has been installed, you may need to do some additional "
+"network configuration. At this point in the installation, you should have a "
+"plan for what NICs the host will have and what traffic each NIC will carry. "
+"The NICs should be cabled as necessary to implement your plan."
+msgstr "XenServer安装完成后， 需要对网络做一些额外的设置。此时， 你应该对主机上的网卡及每个网络传输的流量有一个整体规划。网络连接必须满足你的规划."
+
+# f28bb641121f436ca9f8198d73026c0c
+#: ../../hypervisor_installation.rst:1366
+msgid ""
+"If you plan on using NIC bonding, the NICs on all hosts in the cluster must "
+"be cabled exactly the same. For example, if eth0 is in the private bond on "
+"one host in a cluster, then eth0 must be in the private bond on all hosts in"
+" the cluster."
+msgstr "如果你计划使用网卡绑定，那么所有主机上的网卡的连接必须相同。比如，如果群集中的一台主机eth0为专用绑定，那么其他主机上的eth0也必须为专用绑定。"
+
+# b85094b7061646f493d481b41f4f5d9b
+#: ../../hypervisor_installation.rst:1371
+msgid ""
+"The IP address assigned for the management network interface must be static."
+" It can be set on the host itself or obtained via static DHCP."
+msgstr "分配给管理网络的IP必须是静态IP。它可以通过DHCP保留或者在主机上指定。"
+
+# f4eaab06e1894ba28c9a3ee1c8fd19e2
+#: ../../hypervisor_installation.rst:1374
+msgid ""
+"CloudStack configures network traffic of various types to use different NICs"
+" or bonds on the XenServer host. You can control this process and provide "
+"input to the Management Server through the use of XenServer network name "
+"labels. The name labels are placed on physical interfaces or bonds and "
+"configured in CloudStack. In some simple cases the name labels are not "
+"required."
+msgstr "CloudStack使用XenServer上的不同网卡或绑定来配置不同流量类型。你可以在管理服务器上通过输入XenServer适配器标签来控制这些流量。CloudStack中的标签名称就是物理接口或绑定的名称。在简单的网络中，可以不填写标签。"
+
+# de56a32c98eb4628a39e7d67f51d4762
+#: ../../hypervisor_installation.rst:1381
+msgid ""
+"When configuring networks in a XenServer environment, network traffic labels"
+" must be properly configured to ensure that the virtual interfaces are "
+"created by CloudStack are bound to the correct physical device. The name-"
+"label of the XenServer network must match the XenServer traffic label "
+"specified while creating the CloudStack network. This is set by running the "
+"following command:"
+msgstr "在XenServer环境中配置网络时，必须正确的配置网络流量标签，确保CloudStack将虚拟接口绑定到正确的物理设备上。XenServer的网络标签必须与配置CloudStack的网络时指定的XenServer流量标签一致。运行以下命令来设置："
+
+# 615cf9185dd24899b715f67bf68619ce
+#: ../../hypervisor_installation.rst:1393
+msgid ""
+"Configuring Public Network with a Dedicated NIC for XenServer (Optional)"
+msgstr "使用专用的XenServer网卡来配置公用网络（可选）"
+
+# 3c82b6119dda4300b8573ec15d8e2700
+#: ../../hypervisor_installation.rst:1395
+msgid ""
+"CloudStack supports the use of a second NIC (or bonded pair of NICs, "
+"described in :ref:`nic-bonding-for-xenserver`) for the public network. If "
+"bonding is not used, the public network can be on any NIC and can be on "
+"different NICs on the hosts in a cluster. For example, the public network "
+"can be on eth0 on node A and eth1 on node B. However, the XenServer name-"
+"label for the public network must be identical across all hosts. The "
+"following examples set the network label to \"cloud-public\". After the "
+"management server is installed and running you must configure it with the "
+"name of the chosen network label (e.g. \"cloud-public\"); this is discussed "
+"in `\"Management Server Installation\" <installation.html#management-server-"
+"installation>`_."
+msgstr "CloudStack支持公共网络使用第二块网卡(或者是2块网卡绑定，在 :ref:`nic-bonding-for-xenserver` 有描述)。如果没有使用绑定，公共网络可以使用群集中不同主机上的不同网卡。比如，公共网络可以使用节点A上的eth0和节点B上的eth1。但是，用于公共网络的名称标签在所有主机上必须一致。举个例子，我们在XenServer上设定了网络标签\"cloud-public\"。在安装完管理服务器之后，你必须使用( \"cloud-public\")作为对应的CloudStack的网络流量标签；这个在 `\"管理服务器的安装\" <installation.html#management-server-installation>`_中有介绍。"
+
+# 110691d610d44e6abc3b85a434281c45
+#: ../../hypervisor_installation.rst:1406
+msgid ""
+"If you are using two NICs bonded together to create a public network, see "
+":ref:`nic-bonding-for-xenserver`."
+msgstr "如果你使用双网卡绑定作为公共网络，请参阅 :ref:`nic-bonding-for-xenserver`。"
+
+# 5eeb0c63f90641ba8ae5b6652fb43ac5
+#: ../../hypervisor_installation.rst:1409
+msgid ""
+"If you are using a single dedicated NIC to provide public network access, "
+"follow this procedure on each new host that is added to CloudStack before "
+"adding the host."
+msgstr "如果你指定单网卡作为公共网络，在加入CloudStack环境之前按照下面的流程配置每个主机。"
+
+# 06ff995c8cd147ecbee8398ae114eb8f
+#: ../../hypervisor_installation.rst:1415
+msgid ""
+"Run xe network-list and find the public network. This is usually attached to"
+" the NIC that is public. Once you find the network make note of its UUID. "
+"Call this <UUID-Public>."
+msgstr "运行xe network-list，查找公共网络。通常它的名字就是public。找到之后记录UUID。可以称之为<UUID-Public>。"
+
+# bd31c6c93f934071bb6a514d4b1b50ca
+#: ../../hypervisor_installation.rst:1421
+msgid "Run the following command."
+msgstr "运行以下命令。"
+
+# d2be307f51684ed299d0d6b382616d08
+#: ../../hypervisor_installation.rst:1428
+msgid "Configuring Multiple Guest Networks for XenServer (Optional)"
+msgstr "XenServer配置多个来宾网络(可选)"
+
+# 52d7d8db9ce2409e83475cdad3955a33
+#: ../../hypervisor_installation.rst:1430
+msgid ""
+"CloudStack supports the use of multiple guest networks with the XenServer "
+"hypervisor. Each network is assigned a name-label in XenServer. For example,"
+" you might have two networks with the labels \"cloud-guest\" and \"cloud-"
+"guest2\". After the management server is installed and running, you must add"
+" the networks and use these labels so that CloudStack is aware of the "
+"networks."
+msgstr "CloudStack支持在XenServer上使用多个来宾网络。在XenServer中为每个网络都被分配名称标签。例如，你可能有两个名称分别为\"cloud-guest\"和\"cloud-guest2\"的网络。在配置好管理服务器并且运行后，你必须使用这些标签将这些网络添加到CloudStack中，以便CloudStack能够识别到这些网络。"
+
+# 8a5be9e0828c4730b3dcb0b852e2220f
+#: ../../hypervisor_installation.rst:1437
+msgid ""
+"Follow this procedure on each new host before adding the host to CloudStack:"
+msgstr "在将主机添加到CloudStack之前，请在每个新主机上执行以下操作："
+
+# 3634bb596dba4e22b7ea59c50eb2f1ef
+#: ../../hypervisor_installation.rst:1442
+msgid ""
+"Run xe network-list and find one of the guest networks. Once you find the "
+"network make note of its UUID. Call this <UUID-Guest>."
+msgstr "运行xe network-list，找出来宾网络。并记录UUID。可以称为<UUID-Guest>。"
+
+# 786c3d9e0de241399b68a3ab7c3069cc
+#: ../../hypervisor_installation.rst:1447
+msgid ""
+"Run the following command, substituting your own name-label and uuid values."
+msgstr "运行下面的命令, 替换你自己的名称标签和UUID."
+
+# 562afb7e19cf4d4381e2ec0f140e5e61
+#: ../../hypervisor_installation.rst:1456
+msgid ""
+"Repeat these steps for each additional guest network, using a different "
+"name-label and uuid each time."
+msgstr "对每个额外的来宾网络都重复这些步骤，注意每次要使用不同的名称标签和UUID。"
+
+# 41b48003990c4afdb4b6b8a96f1513cd
+#: ../../hypervisor_installation.rst:1460
+msgid "Separate Storage Network for XenServer (Optional)"
+msgstr "XenServer设置单独的存储网络(可选)"
+
+# d1c730db57c24a7da597f35913fe72f0
+#: ../../hypervisor_installation.rst:1462
+msgid ""
+"You can optionally set up a separate storage network. This should be done "
+"first on the host, before implementing the bonding steps below. This can be "
+"done using one or two available NICs. With two NICs bonding may be done as "
+"above. It is the administrator's responsibility to set up a separate storage"
+" network."
+msgstr "在绑定网卡之前，你可以有选择的配置一个独立的存储网络。使用1到2个网卡，上述给出了两块网卡绑定的示例。配置一个独立的存储网络是管理的职责。"
+
+# 5077124054fc4ba3b593435b5bd5b709
+#: ../../hypervisor_installation.rst:1468
+msgid ""
+"Give the storage network a different name-label than what will be given for "
+"other networks."
+msgstr "为存储网络设置一个与其他网络不同的名称标签。"
+
+# 2c93ae198ee746f7b38008dc9aaa2b63
+#: ../../hypervisor_installation.rst:1471
+msgid ""
+"For the separate storage network to work correctly, it must be the only "
+"interface that can ping the primary storage device's IP address. For "
+"example, if eth0 is the management network NIC, ping -I eth0 <primary "
+"storage device IP> must fail. In all deployments, secondary storage devices "
+"must be pingable from the management network NIC or bond. If a secondary "
+"storage device has been placed on the storage network, it must also be "
+"pingable via the storage network NIC or bond on the hosts as well."
+msgstr "让独立的存储网络工作正常，必须可以通过它的接口ping通主存储设备的IP。比如，如果eth0是管理网络的网卡，ping -I eth0 <primary storage device IP>必须是不通的。在所有的部署环境里，通过管理网络必须能ping通辅助存储设备的IP。如果辅助存储设备是在存储网络中，那么通过存储网络同样也要能ping通它。"
+
+# 5dc74fbf37884dd1a441515d7ccb3739
+#: ../../hypervisor_installation.rst:1480
+msgid ""
+"You can set up two separate storage networks as well. For example, if you "
+"intend to implement iSCSI multipath, dedicate two non-bonded NICs to "
+"multipath. Each of the two networks needs a unique name-label."
+msgstr "你可以设置两个独立的存储网络。例如，使用两块独立网卡实现iSCSI多路径。当然，两个网络都需要自己的名称标签。"
+
+# 21486bfc4a50447a974137680f2e8750
+#: ../../hypervisor_installation.rst:1484
+msgid ""
+"If no bonding is done, the administrator must set up and name-label the "
+"separate storage network on all hosts (masters and slaves)."
+msgstr "如果没有做绑定，管理员必须为所有主机上(主、从节点)的存储网络设置名称标签。"
+
+# e74b734827c148e4abf67add41daf5fa
+#: ../../hypervisor_installation.rst:1487
+msgid ""
+"Here is an example to set up eth5 to access a storage network on "
+"172.16.0.0/24."
+msgstr "此处示例配置eth5访问172.16.0.0/24的存储网络。"
+
+# 4c8478c9b0404061b4f0eb4cf916b145
+#: ../../hypervisor_installation.rst:1500
+msgid "NIC Bonding for XenServer (Optional)"
+msgstr "XenServer中的网卡绑定（可选）"
+
+# dc0584c53b15404da1bd19bd6ee782bf
+#: ../../hypervisor_installation.rst:1502
+msgid ""
+"XenServer supports Source Level Balancing (SLB) NIC bonding. Two NICs can be"
+" bonded together to carry public, private, and guest traffic, or some "
+"combination of these. Separate storage networks are also possible. Here are "
+"some example supported configurations:"
+msgstr "XenServer支持Source Level Balancing (SLB) NIC绑定。两块网卡可被绑定在一起承载公共网络、管理网络和来宾网络流量，或这些网络的组合。单独的存储网络同样可以。以下是一些配置的示例："
+
+# 585023d3f7b24463a959419863701154
+#: ../../hypervisor_installation.rst:1509
+msgid "2 NICs on private, 2 NICs on public, 2 NICs on storage"
+msgstr "管理网络使用2块网卡，公共网络使用2块网卡，存储网络使用2块网卡"
+
+# 85ce9960f5f64e7e81103c42a25c7992
+#: ../../hypervisor_installation.rst:1513
+msgid "2 NICs on private, 1 NIC on public, storage uses management network"
+msgstr "管理网络使用2块网卡，公共网络使用1块网卡，存储共用管理网络"
+
+# 766a18c82a444b0f9940f362c82e2922
+#: ../../hypervisor_installation.rst:1517
+msgid "2 NICs on private, 2 NICs on public, storage uses management network"
+msgstr "管理网络使用2块网卡，共用网络使用2块网卡，存储共用管理网络"
+
+# a559ff80b0a94e9799389702be54cf19
+#: ../../hypervisor_installation.rst:1521
+msgid "1 NIC for private, public, and storage"
+msgstr "管理网络，公共网络，存储网络使用一块网卡"
+
+# b92a690f72754add8ee271cf1ba240f1
+#: ../../hypervisor_installation.rst:1523
+msgid "All NIC bonding is optional."
+msgstr "所有的网卡绑定都是可选的"
+
+# 26835cc7c2844c809af0dc5a4cfc4742
+#: ../../hypervisor_installation.rst:1525
+msgid ""
+"XenServer expects all nodes in a cluster will have the same network cabling "
+"and same bonds implemented. In an installation the master will be the first "
+"host that was added to the cluster and the slave hosts will be all "
+"subsequent hosts added to the cluster. The bonds present on the master set "
+"the expectation for hosts added to the cluster later. The procedure to set "
+"up bonds on the master and slaves are different, and are described below. "
+"There are several important implications of this:"
+msgstr "XenServer期望群集中所有的节点都拥有相同的网络布线，以及相同的绑定。在安装完成后第一台主机将成为Master，而随后加入到群集中的其他主机都将成为Slave。Master主机上的网卡绑定设置会覆盖其他主机的网络配置。在Master和Slaver上设置网卡绑定的步骤不同，重点包括几个部分："
+
+# 422eb3cde8234e3a8e6269cdb3548d5a
+#: ../../hypervisor_installation.rst:1535
+msgid ""
+"You must set bonds on the first host added to a cluster. Then you must use "
+"xe commands as below to establish the same bonds in the second and "
+"subsequent hosts added to a cluster."
+msgstr "必须在添加至群集的第一台主机上设置网卡绑定。然后必须使用如下的xe命令，使第二台和随后添加至该群集的主机上自动配置与Master主机相同的网卡绑定。"
+
+# c3572859ed994bf79cccdac0dc036ada
+#: ../../hypervisor_installation.rst:1541
+msgid ""
+"Slave hosts in a cluster must be cabled exactly the same as the master. For "
+"example, if eth0 is in the private bond on the master, it must be in the "
+"management network for added slave hosts."
+msgstr "群集中的Slave主机必须与Master主机拥有完全相同的布线。例如，如果eth0在群集中的主机上的专用网络绑定中，那么eth0必须在群集中的所有主机上专用网络绑定中。"
+
+# 50715edffb014ce094ecfdcfc1429bc7
+#: ../../hypervisor_installation.rst:1546
+msgid "Management Network Bonding"
+msgstr "管理网络绑定"
+
+# 355923780aac48ae87b6a24963efcbab
+#: ../../hypervisor_installation.rst:1548
+msgid ""
+"The administrator must bond the management network NICs prior to adding the "
+"host to CloudStack."
+msgstr "在将主机添加至CloudStack之前管理员必须绑定管理网络的网卡。"
+
+# 241a3f2bb47549c1b613bc5468c732d1
+#: ../../hypervisor_installation.rst:1552
+msgid "Creating a Private Bond on the First Host in the Cluster"
+msgstr "在群集的第一台主机中创建专用绑定"
+
+# b0b878648bc34dd3b949b2492db4ebe7
+#: ../../hypervisor_installation.rst:1554
+msgid ""
+"Use the following steps to create a bond in XenServer. These steps should be"
+" run on only the first host in a cluster. This example creates the cloud-"
+"private network with two physical NICs (eth0 and eth1) bonded into it."
+msgstr "使用下述步骤在XenServer上创建网卡绑定。这些步骤只在群集中第一台主机上运行即可。本示例为cloud-private网络绑定了两块物理网卡(eth0和eth1)。"
+
+# c818433917984f208742d7624945c715
+# c273eb3061e74432b57d9077c627c6ea
+#: ../../hypervisor_installation.rst:1561
+#: ../../hypervisor_installation.rst:1607
+msgid "Find the physical NICs that you want to bond together."
+msgstr "找到想要绑定在一起的物理网卡。"
+
+# 913da62e00594d7d9256568a0966482a
+#: ../../hypervisor_installation.rst:1568
+msgid ""
+"These command shows the eth0 and eth1 NICs and their UUIDs. Substitute the "
+"ethX devices of your choice. Call the UUID's returned by the above command "
+"slave1-UUID and slave2-UUID."
+msgstr "如上命令显示了eth0、eth1和对应的UUID。并替换你的网卡编号。上述命令返回的UUID称为slave1-UUID和slave2-UUID。"
+
+# 5f7804ba516044498b79880642b90e2c
+#: ../../hypervisor_installation.rst:1574
+msgid ""
+"Create a new network for the bond. For example, a new network with name "
+"\"cloud-private\"."
+msgstr "为该绑定创建一个新的网络。例如，一个名为“cloud-public”的新网络。"
+
+# d2ccc4ae2a144c8b9d8337cc227fb222
+#: ../../hypervisor_installation.rst:1577
+msgid ""
+"**This label is important. CloudStack looks for a network by a name you "
+"configure. You must use the same name-label for all hosts in the cloud for "
+"the management network.**"
+msgstr "**标签非常重要。因为CloudStack根据配置的名称查找网络。必须对云中所有主机的管理网络使用同样的名称标签（name-label）。**"
+
+# f3b50a468a3e4e83813f2acba6062bd8
+#: ../../hypervisor_installation.rst:1587
+msgid ""
+"Now you have a bonded pair that can be recognized by CloudStack as the "
+"management network."
+msgstr "现在有了可以被CloudStack识别为管理网络的网卡绑定。"
+
+# cf64cccd2bb745bcaaddd7b531fbc539
+#: ../../hypervisor_installation.rst:1591
+msgid "Public Network Bonding"
+msgstr "公共网络网卡绑定"
+
+# f999c0e7062f47cf9e78cd29a0554039
+#: ../../hypervisor_installation.rst:1593
+msgid ""
+"Bonding can be implemented on a separate, public network. The administrator "
+"is responsible for creating a bond for the public network if that network "
+"will be bonded and will be separate from the management network."
+msgstr "可以在单独的公共网络上执行绑定。管理员可以将使用网卡绑定的公共网络与管理网络区分开。"
+
+# 0242521ca5b94ecfa005cd45513c5d1f
+#: ../../hypervisor_installation.rst:1599
+msgid "Creating a Public Bond on the First Host in the Cluster"
+msgstr "在集群的第一台主机上创建公共网络网卡绑定"
+
+# 3582283d68284b5fb85af54cb569eaca
+#: ../../hypervisor_installation.rst:1601
+msgid ""
+"These steps should be run on only the first host in a cluster. This example "
+"creates the cloud-public network with two physical NICs (eth2 and eth3) "
+"bonded into it."
+msgstr "以下步骤仅在群集的第一台主机中运行。本示例为cloud-public绑定了两块物理网卡(eth2和eth3)。"
+
+# 525068448771408183ac84f1a5d006be
+#: ../../hypervisor_installation.rst:1614
+msgid ""
+"These command shows the eth2 and eth3 NICs and their UUIDs. Substitute the "
+"ethX devices of your choice. Call the UUID's returned by the above command "
+"slave1-UUID and slave2-UUID."
+msgstr "以上命令显示了eth2、eth3和对应的UUID。替换你的网卡编号。将上述命令返回的UUID称为slave1-UUID和slave2-UUID。"
+
+# b9e69c9100564b88b43f6779621e12c4
+#: ../../hypervisor_installation.rst:1620
+msgid ""
+"Create a new network for the bond. For example, a new network with name "
+"\"cloud-public\"."
+msgstr "为网卡绑定创建一个新的网络。比如，一个名为\"cloud-public\"的新网络。"
+
+# d4f75d2fc44545eaa191a59720d7ac1c
+#: ../../hypervisor_installation.rst:1623
+msgid ""
+"**This label is important. CloudStack looks for a network by a name you "
+"configure. You must use the same name-label for all hosts in the cloud for "
+"the public network.**"
+msgstr "**该标签非常重要。因为CloudStack根据配置的名称来查找网络。必须对云中所有物理主机的公共网络使用同样的名称标签（name-label）。**"
+
+# f11b8de48bbf4fc6895b7bb33f52a308
+#: ../../hypervisor_installation.rst:1633
+msgid ""
+"Now you have a bonded pair that can be recognized by CloudStack as the "
+"public network."
+msgstr "现在有了被CloudStack识别为公共网络的网卡绑定。"
+
+# 08c0b83d57f64624a7fa7bb0b057d887
+#: ../../hypervisor_installation.rst:1637
+msgid "Adding More Hosts to the Cluster"
+msgstr "在群集中添加更多主机"
+
+# 7b998653c91d417d9920cdf8a2b62752
+#: ../../hypervisor_installation.rst:1639
+msgid ""
+"With the bonds (if any) established on the master, you should add "
+"additional, slave hosts. Run the following command for all additional hosts "
+"to be added to the cluster. This will cause the host to join the master in a"
+" single XenServer pool."
+msgstr "在master主机添加了(任何)绑定网卡的基础上，可以添加其他的slave主机。对所有添加至群集的其他主机执行下面的命令。他的作用是将这些主机都加入master所在的同一个XenServer池中。"
+
+# 46fa7303d5604b5aa8d3a61679d51e47
+#: ../../hypervisor_installation.rst:1650
+msgid "Complete the Bonding Setup Across the Cluster"
+msgstr "完成群集内的绑定设置"
+
+# 53dea66729854ace9b2af4bdfc78c1ca
+#: ../../hypervisor_installation.rst:1652
+msgid ""
+"With all hosts added to the pool, run the cloud-setup-bond script. This "
+"script will complete the configuration and set up of the bonds across all "
+"hosts in the cluster."
+msgstr "所有主机添加至资源池后，运行 cloud-setup-bond脚本。此脚本将配置群集中所有主机的网卡绑定。"
+
+# cd69e7cc948c43ffa11698a2390cf986
+#: ../../hypervisor_installation.rst:1658
+msgid ""
+"Copy the script from the Management Server in /usr/share/cloudstack-"
+"common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh to the master "
+"host and ensure it is executable."
+msgstr "将管理服务器中/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-setup-bonding.sh拷贝到master主机中并确认该脚本可执行。"
+
+# 3b7ac5520f0e464aa6c2c0dcb9f61233
+#: ../../hypervisor_installation.rst:1664
+msgid "Run the script:"
+msgstr "运行脚本："
+
+# 878fb7127a004f419b95241af6bee8ae
+#: ../../hypervisor_installation.rst:1670
+msgid "Now the bonds are set up and configured properly across the cluster."
+msgstr "现在，群集内所有主机的网卡绑定都已配置正确。"
+
+# 6b4c5561ec7e4237b7dc17126c581b6a
+#: ../../hypervisor_installation.rst:1675
+msgid "Upgrading XenServer Versions"
+msgstr "升级XenServer版本"
+
+# cfc09c589fb540b0b0a1bec122afd5ff
+#: ../../hypervisor_installation.rst:1677
+msgid ""
+"This section tells how to upgrade XenServer software on CloudStack hosts. "
+"The actual upgrade is described in XenServer documentation, but there are "
+"some additional steps you must perform before and after the upgrade."
+msgstr "本章节介绍了如何升级CloudStack环境中的XenServer。实际升级的操作在XenServer文档中有详细描述，但是在升级前后有些额外的步骤必须执行。"
+
+# 2376fd5b927644c8b4b846ad245f3688
+#: ../../hypervisor_installation.rst:1682
+msgid ""
+"Be sure the hardware is certified compatible with the new version of "
+"XenServer."
+msgstr "确保硬件可以被新版本XenServer支持。"
+
+# 942358ec8cfb439aa09b3a2faf54e73c
+#: ../../hypervisor_installation.rst:1684
+msgid "To upgrade XenServer:"
+msgstr "升级XenServer："
+
+# e1b8b830b03645a7ab9cc4e5d534e1d1
+#: ../../hypervisor_installation.rst:1688
+msgid "Upgrade the database. On the Management Server node:"
+msgstr "升级数据库。在管理服务器节点上："
+
+# 8b47371c505b4b43a8e836e8d1747528
+#: ../../hypervisor_installation.rst:1692
+msgid "Back up the database:"
+msgstr "备份数据库："
+
+# 99f965b30fe24ab8bfff83358a44964e
+#: ../../hypervisor_installation.rst:1701
+msgid ""
+"You might need to change the OS type settings for VMs running on the "
+"upgraded hosts."
+msgstr "需要更改升级后的主机中虚拟机的操作系统类型。"
+
+# ffcbd17272014822acea38cfefd3e547
+#: ../../hypervisor_installation.rst:1706
+msgid ""
+"If you upgraded from XenServer 5.6 GA to XenServer 5.6 SP2, change any VMs "
+"that have the OS type CentOS 5.5 (32-bit), Oracle Enterprise Linux 5.5 "
+"(32-bit), or Red Hat Enterprise Linux 5.5 (32-bit) to Other Linux (32-bit). "
+"Change any VMs that have the 64-bit versions of these same OS types to Other"
+" Linux (64-bit)."
+msgstr "如果是从XenServer 5.6 GA 升级到XenServer 5.6 SP2，更改虚机操作系统类型CentOS 5.5 (32-bit), Oracle Enterprise Linux 5.5 (32-bit)或者Red Hat Enterprise Linux 5.5 (32-bit)为Other Linux (32-bit)。同样这些虚机的64位版本操作系统类型也要改为Other Linux (64-bit)。"
+
+# 733596d54def49918fe6659885ae3c7b
+#: ../../hypervisor_installation.rst:1715
+msgid ""
+"If you upgraded from XenServer 5.6 SP2 to XenServer 6.0.2, change any VMs "
+"that have the OS type CentOS 5.6 (32-bit), CentOS 5.7 (32-bit), Oracle "
+"Enterprise Linux 5.6 (32-bit), Oracle Enterprise Linux 5.7 (32-bit), Red Hat"
+" Enterprise Linux 5.6 (32-bit) , or Red Hat Enterprise Linux 5.7 (32-bit) to"
+" Other Linux (32-bit). Change any VMs that have the 64-bit versions of these"
+" same OS types to Other Linux (64-bit)."
+msgstr "如果是从XenServer 5.6 SP2升级到XenServer 6.0.2，更改虚拟操作系统类型CentOS 5.6 (32-bit), CentOS 5.7 (32-bit), Oracle Enterprise Linux 5.6 (32-bit), Oracle Enterprise Linux 5.7 (32-bit), Red Hat Enterprise Linux 5.6 (32-bit)或者Red Hat Enterprise Linux 5.7 (32-bit)为Other Linux (32-bit)。同样这些虚机的64位版本操作系统类型也要改为Other Linux (64-bit)。"
+
+# 14f2e711450e4ff58dd3149c1fdab21d
+#: ../../hypervisor_installation.rst:1725
+msgid ""
+"If you upgraded from XenServer 5.6 to XenServer 6.0.2, do all of the above."
+msgstr "如果从XenServer 5.6升级到XenServer 6.0.2，需完成以上所有操作。"
+
+# f2619c1d24c74437a167e2d44d5253c7
+#: ../../hypervisor_installation.rst:1730
+msgid ""
+"Restart the Management Server and Usage Server. You only need to do this "
+"once for all clusters."
+msgstr "重启管理服务和Usage服务. 只需为所有的集群做一次这样的操作。"
+
+# fc348fb3fda64c95883a94a886676f1d
+#: ../../hypervisor_installation.rst:1740
+msgid "Disconnect the XenServer cluster from CloudStack."
+msgstr "在CloudStack中断开XenServer群集连接。"
+
+# 7f794481fc044e789630a36cdbfdf41f
+# f65c913be82f4fe09eb132c2c6dc033a
+# ca114347489c453a8cbd54f9520a6500
+# 21a397aa7b7d4f23ad83b33343dc8cd7
+#: ../../hypervisor_installation.rst:1744
+#: ../../hypervisor_installation.rst:1874
+#: ../../hypervisor_installation.rst:3252
+#: ../../hypervisor_installation.rst:3301
+msgid "Log in to the CloudStack UI as root."
+msgstr "使用admin账户登录CloudStack管理界面。"
+
+# 7153d29a4b934e7bb7b4150b35a8b3e5
+#: ../../hypervisor_installation.rst:1748
+msgid "Navigate to the XenServer cluster, and click Actions – Unmanage."
+msgstr "导航至XenServer群集，点击操作-取消管理。"
+
+# b860ab2de3c14f0da775023c03a393ed
+# 08c7c9f1bbca4dac9ca9abb2d901954f
+#: ../../hypervisor_installation.rst:1752
+#: ../../hypervisor_installation.rst:3263
+msgid "Watch the cluster status until it shows Unmanaged."
+msgstr "查看群集状态直到显示未受管理。"
+
+# f527402053e54831b67ae8daef6083c5
+#: ../../hypervisor_installation.rst:1756
+msgid ""
+"Log in to one of the hosts in the cluster, and run this command to clean up "
+"the VLAN:"
+msgstr "登录到群集中的任意一台主机，运行下面的命令清除VLAN信息："
+
+# b42f28a2c2fb4455a41e6372a470f6a9
+#: ../../hypervisor_installation.rst:1765
+msgid "Still logged in to the host, run the upgrade preparation script:"
+msgstr "仍旧在这台已经登录的主机中，运行下面的升级准备脚本："
+
+# f6179b84964541bb846a719b3663189e
+#: ../../hypervisor_installation.rst:1771
+msgid ""
+"Troubleshooting: If you see the error \"can't eject CD,\" log in to the VM "
+"and umount the CD, then run the script again."
+msgstr "故障排除：如果看到 \"can't eject CD,\" 错误，请登录到虚拟机将光盘卸载，并重新运行脚本。"
+
+# d7a81f24da0d4fd0b589ebfcfcd71784
+#: ../../hypervisor_installation.rst:1776
+msgid ""
+"Upgrade the XenServer software on all hosts in the cluster. Upgrade the "
+"master first."
+msgstr "升级群集中所有的XenServer主机。首先升级master节点。"
+
+# 11d3dd98878f4fe08f96c16e5df8c6ac
+#: ../../hypervisor_installation.rst:1781
+msgid ""
+"Live migrate all VMs on this host to other hosts. See the instructions for "
+"live migration in the Administrator's Guide."
+msgstr "将该主机上的所有虚拟机动态迁移到其他主机。请参照管理指南了解动态迁移指导。"
+
+# 1bdb8f184a494eb4969abf3ba696ed19
+#: ../../hypervisor_installation.rst:1784
+msgid ""
+"Troubleshooting: You might see the following error when you migrate a VM:"
+msgstr "故障排除：迁移虚拟机时可能会遇到下面的错误："
+
+# 6ad7bdb81aca465a9b5938d726550c76
+#: ../../hypervisor_installation.rst:1793
+msgid "To solve this issue, run the following:"
+msgstr "解决这个问题，请运行下面的命令："
+
+# 9676fe491f5740eaba74cd4060ed35f4
+#: ../../hypervisor_installation.rst:1801
+msgid "Reboot the host."
+msgstr "重启主机。"
+
+# 383661aa66db407a8dd6f313e2acc4f4
+#: ../../hypervisor_installation.rst:1805
+msgid ""
+"Upgrade to the newer version of XenServer. Use the steps in XenServer "
+"documentation."
+msgstr "要升级更新版本的XenServer。请执行XenServer文档中的步骤。"
+
+# ef1bce7a4ef44573a6106976c04c4c45
+#: ../../hypervisor_installation.rst:1810
+msgid ""
+"After the upgrade is complete, copy the following files from the management "
+"server to this host, in the directory locations shown below:"
+msgstr "在升级完成之后，将下列文件从管理服务器复制到这台主机，文件所在路径如下："
+
+# 64ccf69ad9eb4dfeb17c080ada99de6f
+#: ../../hypervisor_installation.rst:1815
+msgid "Copy this Management Server file"
+msgstr "复制管理服务器的文件"
+
+# 32e9ec87a68946b5b2705187b2201880
+#: ../../hypervisor_installation.rst:1815
+msgid "To this location on the XenServer host"
+msgstr "复制到XenServer主机的路径"
+
+# d008b2ce2b484b0aa482d6df64c2b74e
+#: ../../hypervisor_installation.rst:1817
+msgid ""
+"/usr/share/cloudstack-"
+"common/scripts/vm/hypervisor/xenserver/xenserver60/NFSSR.py"
+msgstr "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/xenserver60/NFSSR.py"
+
+# e6b5a2e9d2684509ba864a23c275056f
+#: ../../hypervisor_installation.rst:1817
+msgid "/opt/xensource/sm/NFSSR.py"
+msgstr "/opt/xensource/sm/NFSSR.py"
+
+# d5f8132be2874a02b0853331d25286ed
+#: ../../hypervisor_installation.rst:1818
+msgid ""
+"/usr/share/cloudstack-"
+"common/scripts/vm/hypervisor/xenserver/setupxenserver.sh"
+msgstr "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/setupxenserver.sh"
+
+# 2393c9fde5964bcdb21f54931c5cd007
+#: ../../hypervisor_installation.rst:1818
+msgid "/opt/xensource/bin/setupxenserver.sh"
+msgstr "/opt/xensource/bin/setupxenserver.sh"
+
+# 7a478317154146aa933ae7193c133e0a
+#: ../../hypervisor_installation.rst:1819
+msgid ""
+"/usr/share/cloudstack-"
+"common/scripts/vm/hypervisor/xenserver/make\\_migratable.sh"
+msgstr "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/make\\_migratable.sh"
+
+# 36d9f18cee164a5c9551ab66b058f0e5
+#: ../../hypervisor_installation.rst:1819
+msgid "/opt/xensource/bin/make\\_migratable.sh"
+msgstr "/opt/xensource/bin/make\\_migratable.sh"
+
+# 5e031eb5f37f4b42a7a0357a9e963dde
+#: ../../hypervisor_installation.rst:1820
+msgid ""
+"/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-clean-"
+"vlan.sh"
+msgstr "/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/cloud-clean-vlan.sh"
+
+# 12cd3626b3954c23be38e95e7059b7dc
+#: ../../hypervisor_installation.rst:1820
+msgid "/opt/xensource/bin/cloud-clean-vlan.sh"
+msgstr "/opt/xensource/bin/cloud-clean-vlan.sh"
+
+# 0b7bb106fe444196ae32f10b125d51bb
+#: ../../hypervisor_installation.rst:1831
+msgid ""
+"Troubleshooting: If you see the following error message, you can safely "
+"ignore it."
+msgstr "故障排除：如果看到下面的错误信息，可以忽略它。"
+
+# 84fc84c6930a40b88488984ff6c9112c
+#: ../../hypervisor_installation.rst:1840
+msgid ""
+"Plug in the storage repositories (physical block devices) to the XenServer "
+"host:"
+msgstr "将XenServer主机连接至存储库(物理的块设备)："
+
+# d796a15c920847c7a8251c995526c02d
+#: ../../hypervisor_installation.rst:1847
+msgid ""
+"If you add a host to this XenServer pool, you need to migrate all VMs on "
+"this host to other hosts, and eject this host from XenServer pool."
+msgstr "如果添加一台主机到这个XenServer资源池中，你必须将这台主机上的所有的虚机迁移到其他主机，然后将这台主机从原来的XenServer资源池中移除。"
+
+# f9bd9295e2b84bf2879c1ecbc602c44a
+#: ../../hypervisor_installation.rst:1851
+msgid ""
+"Repeat these steps to upgrade every host in the cluster to the same version "
+"of XenServer."
+msgstr "重复这些步骤，将每台主机都升级到相同的XenServer版本。"
+
+# 8e37aa52a47547be82d24895b65f09f4
+#: ../../hypervisor_installation.rst:1856
+msgid ""
+"Run the following command on one host in the XenServer cluster to clean up "
+"the host tags:"
+msgstr "在XenServer群集中的一台主机上运行下面命令来清除主机标签："
+
+# 8cf9d53037984028bce163054acb29f2
+#: ../../hypervisor_installation.rst:1864
+msgid ""
+"When copying and pasting a command, be sure the command has pasted as a "
+"single line before executing. Some document viewers may introduce unwanted "
+"line breaks in copied text."
+msgstr "当复制和粘贴命令时，请确保没有多余的换行符，因为一些文档查看器可能会在复制时加上换行符。"
+
+# 3e06a5a1b257415a9ede2507a47d0877
+#: ../../hypervisor_installation.rst:1870
+msgid "Reconnect the XenServer cluster to CloudStack."
+msgstr "在CloudStack中重新连接XenServer群集。"
+
+# 950820df270d40ebb2b49296c30a9a53
+#: ../../hypervisor_installation.rst:1878
+msgid "Navigate to the XenServer cluster, and click Actions – Manage."
+msgstr "在XenServer群集导航页中，点击操作-管理。"
+
+# 662b5d4d23744762922ae112f5e61b84
+#: ../../hypervisor_installation.rst:1882
+msgid "Watch the status to see that all the hosts come up."
+msgstr "查看状态以确保所有的主机都恢复正常."
+
+# 1b7befb539434c7db47239456ba7213e
+#: ../../hypervisor_installation.rst:1886
+msgid "After all hosts are up, run the following on one host in the cluster:"
+msgstr "当所有的主机都是运行状态后, 在集群中的一台主机上运行下列的命令:"
+
+# d3a523f2e69a478bb90498d681b0178b
+#: ../../hypervisor_installation.rst:1893
+msgid "Installing Hyper-V for CloudStack"
+msgstr "为CloudStack安装Hyper-V"
+
+# b93fc39d5763433cb59938b5f75dd607
+#: ../../hypervisor_installation.rst:1895
+msgid ""
+"If you want to use Hyper-V hypervisor to run guest virtual machines, install"
+" Hyper-V on the hosts in your cloud. The instructions in this section "
+"doesn't duplicate Hyper-V Installation documentation. It provides the "
+"CloudStack-specific steps that are needed to prepare a Hyper-V host to work "
+"with CloudStack."
+msgstr "如果你想使用 Hyper-V hypervisor来运行虚拟机，请在你的云环境中安装Hyper-V。本章节指导不会复制Hyper-V安装文档中的内容。它提供了让Hyper-V与CloudStack协同工作的一些特有的步骤。"
+
+# 2038da390b6848a0b3cc3fedef1a9d2c
+#: ../../hypervisor_installation.rst:1902
+msgid "System Requirements for Hyper-V Hypervisor Hosts"
+msgstr "Hyper-V主机的系统要求"
+
+# fc724f9178b64868879b74a411d95ef5
+#: ../../hypervisor_installation.rst:1905
+msgid "Supported Operating Systems for Hyper-V Hosts"
+msgstr "Hyper-V主机所支持的操作系统"
+
+# 1a5519a64e134b1a91a658145276f6ed
+#: ../../hypervisor_installation.rst:1909
+msgid "Windows Server 2012 R2 Standard"
+msgstr "Windows Server 2012 R2 Standard"
+
+# ee081eb7e4004f578c7da357ca3b65e2
+#: ../../hypervisor_installation.rst:1913
+msgid "Windows Server 2012 R2 Datacenter"
+msgstr "Windows Server 2012 R2 Datacenter"
+
+# cd21b1eeb72340979622e7783f646d92
+#: ../../hypervisor_installation.rst:1917
+msgid "Hyper-V 2012 R2"
+msgstr "Hyper-V 2012 R2"
+
+# 0d65d540ddce44ad8a88d9484e834d25
+#: ../../hypervisor_installation.rst:1920
+msgid "Minimum System Requirements for Hyper-V Hosts"
+msgstr "Hyper-V主机的最低要求"
+
+# ff261434dbf442899d95fec9961fdf73
+#: ../../hypervisor_installation.rst:1924
+msgid "1.4 GHz 64-bit processor with hardware-assisted virtualization."
+msgstr "支持硬件辅助虚拟化的1.4 GHz 64-bit CPU"
+
+# 8213417edf9244ab8b88ea0831f4c865
+#: ../../hypervisor_installation.rst:1928
+msgid "800 MB of RAM"
+msgstr "800MB内存"
+
+# bf16d06d9e7244b6bbb96e7b56e71357
+#: ../../hypervisor_installation.rst:1932
+msgid "32 GB of disk space"
+msgstr "32GB本地磁盘空间"
+
+# 82c14f0ba5cc44b689942c4b99564fff
+#: ../../hypervisor_installation.rst:1936
+msgid "Gigabit (10/100/1000baseT) Ethernet adapter"
+msgstr "Gigabit (10/100/1000baseT)网卡"
+
+# 51556185e39644d8a4bf6f8f7afa2861
+#: ../../hypervisor_installation.rst:1939
+msgid "Supported Storage"
+msgstr "支持的存储"
+
+# 5beb17ae25a34423bc3a3e369212ec3f
+#: ../../hypervisor_installation.rst:1943
+msgid "Primary Storage: Server Message Block (SMB) Version 3, Local"
+msgstr "主存储：SMB v3，本地存储"
+
+# 55d3704fad27499b92347d61e7deb72a
+#: ../../hypervisor_installation.rst:1947
+msgid "Secondary Storage: SMB"
+msgstr "辅助存储：SMB"
+
+# 703eb2b0e6fc40bcbda49bace0d0fb75
+#: ../../hypervisor_installation.rst:1950
+msgid "Preparation Checklist for Hyper-V"
+msgstr "Hyper-V的准备工作清单"
+
+# 419613931af84db383a87503c76f013c
+# 487f37bf5b724be48da1842d6f4f189e
+#: ../../hypervisor_installation.rst:1952
+#: ../../hypervisor_installation.rst:2388
+msgid ""
+"For a smoother installation, gather the following information before you "
+"start:"
+msgstr "为了能顺利地安装，在安装之前请收集以下信息："
+
+# 2c101932aa3e4ca28fdcb6f78b2628f0
+#: ../../hypervisor_installation.rst:1955
+msgid "Hyper-V Requirements"
+msgstr "Hyper-V要求"
+
+# a2108b6906c5463a9d62d10304f6f7c0
+# 7df31f594d084182a124fa1a5963c2e2
+#: ../../hypervisor_installation.rst:1957
+#: ../../hypervisor_installation.rst:2715
+msgid "Value"
+msgstr "值"
+
+# 8c30f2b9669c4b839800c9fde5954476
+# e536631fc460428f82d0797650809db6
+#: ../../hypervisor_installation.rst:1959
+#: ../../hypervisor_installation.rst:2900
+msgid "Description"
+msgstr "描述"
+
+# 9e31d44efe0d40bc8987a7f1b9a7560a
+#: ../../hypervisor_installation.rst:1961
+msgid "Server Roles"
+msgstr "服务器角色"
+
+# 4de7af81dfc04ce89ecb35699251c666
+#: ../../hypervisor_installation.rst:1965
+msgid ""
+"After the Windows Server 2012 R2 installation, ensure that Hyper-V is "
+"selected from Server Roles. For more information, see `Installing Hyper-V "
+"<http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step2>`_."
+msgstr "Windows Server 2012 R2安装完成之后，请确保在服务器角色中安装了Hyper-V。更多的信息，请参阅 `安装 Hyper-V <http://technet.microsoft.com/en-us/library/jj134187.aspx#BKMK_Step2>`_."
+
+# 644571f95331448f97fe445ae9ee8de9
+#: ../../hypervisor_installation.rst:1968
+msgid "Share Location"
+msgstr "共享位置"
+
+# 636f796bb2ad45c5a5de2c9166505359
+#: ../../hypervisor_installation.rst:1970
+msgid "New folders in the /Share directory"
+msgstr "在/Share目录下新建文件夹"
+
+# 2b338e212cc74f149db217553b6b692f
+#: ../../hypervisor_installation.rst:1972
+msgid ""
+"Ensure that folders are created for Primary and Secondary storage. The SMB "
+"share and the hosts should be part of the same domain."
+msgstr "确保为主存储和辅助存储创建了文件夹。SMB共享和主机应该在同一个域内。"
+
+# 7a6f754da1ec458ca9eae5c017e0ab52
+#: ../../hypervisor_installation.rst:1975
+msgid ""
+"If you are using Windows SMB share, the location of the file share for the "
+"Hyper-V deployment will be the new folder created in the \\\\Shares on the "
+"selected volume. You can create sub-folders for both CloudStack Primary and "
+"Secondary storage within the share location. When you select the profile for"
+" the file shares, ensure that you select SMB Share -Applications. This "
+"creates the file shares with settings appropriate for Hyper-V."
+msgstr "如果你使用Windows SMB共享，新的文件夹会创建在供Hyper-V使用的文件共享位置\\\\Shares中。你可以在共享位置上创建子文件夹用于CloudStack主存储和辅助存储。当你为文件共享选择配置文件时，请确保你选的是SMB Share -Applications。它会为Hpyer-V创建合适的文件共享。"
+
+# cfec42b2cfec42d7b8ffbd8e69cb8561
+#: ../../hypervisor_installation.rst:1983
+msgid "Domain and Hosts"
+msgstr "域和主机"
+
+# 40eb688b68184a569a98d100afc12873
+#: ../../hypervisor_installation.rst:1985
+msgid "Hosts should be part of the same Active Directory domain."
+msgstr "主机都应该加入AD域。"
+
+# 6f43f5b3150444fd8d107a12fcebadb0
+#: ../../hypervisor_installation.rst:1987
+msgid "Hyper-V Users"
+msgstr "Hyper-V用户"
+
+# 571279354d664c0c9db4d00e780060ab
+#: ../../hypervisor_installation.rst:1989
+msgid "Full control"
+msgstr "完全控制权限"
+
+# d4526dd1a8b24a46b8a12c3188d43a1a
+#: ../../hypervisor_installation.rst:1991
+msgid "Full control on the SMB file share."
+msgstr "SMB文件共享有完全控制权限"
+
+# 3619e03fbf014ba3a55f9a8cbbeeb5b0
+#: ../../hypervisor_installation.rst:1993
+msgid "Virtual Switch"
+msgstr "虚拟交换机"
+
+# f63f68f216ba4cabb3a183f2539b2134
+# b7c90a0b793c4c48847a27c21d2b64ac
+#: ../../hypervisor_installation.rst:1995
+#: ../../hypervisor_installation.rst:2166
+msgid ""
+"If you are using Hyper-V 2012 R2, manually create an external virtual switch"
+" before adding the host to CloudStack. If the Hyper-V host is added to the "
+"Hyper-V manager, select the host, then click Virtual Switch Manager, then "
+"New Virtual Switch. In the External Network, select the desired NIC adapter "
+"and click Apply."
+msgstr "如果你使用Hyper-V 2012 R2，在将主机添加到CloudStack中之前，请手动创建一个外部网络虚拟交换机。如果Hyper-V管理器已经添加了Hyper-V主机，选择该主机，然后点击虚拟交换机管理器，新建虚拟交换机。在外部网络，选择所需的网卡然后点击应用。 "
+
+# 6d95d36bac3c4cc899af98614236b0d5
+# 4a0f7c13f957472b93f453ba6e2c6f23
+#: ../../hypervisor_installation.rst:2001
+#: ../../hypervisor_installation.rst:2172
+msgid ""
+"If you are using Windows 2012 R2, virtual switch is created automatically."
+msgstr "如果使用Windows 2012 R2，虚拟交换机会自动创建。"
+
+# eedd8450f79a4f919ecbd025523beb7a
+#: ../../hypervisor_installation.rst:2004
+msgid "Virtual Switch Name"
+msgstr "虚拟交换机名称"
+
+# 705abed5f4e34a2abcdd893c5a585841
+#: ../../hypervisor_installation.rst:2006
+msgid ""
+"Take a note of the name of the virtual switch. You need to specify that when"
+" configuring CloudStack physical network labels."
+msgstr "记录虚拟交换机的名称。在配置CloudStack物理网络标签时需要用到该名称。"
+
+# 96e118a8d6fb4e349ebee12448d428ae
+#: ../../hypervisor_installation.rst:2009
+msgid "Hyper-V Domain Users"
+msgstr "Hyper-V 域用户"
+
+# 2183c3c5058d46e781cfa2009b5b8cce
+#: ../../hypervisor_installation.rst:2013
+msgid "Add the Hyper-V domain users to the Hyper-V Administrators group."
+msgstr "将Hyper-V域用户添加到Hyper-V管理员组中。"
+
+# 9f4d174e848040d582531a73056893bd
+#: ../../hypervisor_installation.rst:2017
+msgid ""
+"A domain user should have full control on the SMB share that is exported for"
+" primary and secondary storage."
+msgstr "域用户应该对提供主存储和辅助存储的SMB共享拥有完全控制权限。"
+
+# 99de63ae54c54e0db4b82c316b7e78b2
+#: ../../hypervisor_installation.rst:2022
+msgid ""
+"This domain user should be part of the Hyper-V Administrators and Local "
+"Administrators group on the Hyper-V hosts that are to be managed by "
+"CloudStack."
+msgstr "域用户应该属于CloudStack所管理的Hyper-V服务器中Hyper-V管理员组和本地管理员组。"
+
+# 720fe08852e24e4b9a6af71ba0163e18
+#: ../../hypervisor_installation.rst:2028
+msgid ""
+"The Hyper-V Agent service runs with the credentials of this domain user "
+"account."
+msgstr "Hyper-V代理服务使用域用户账号身份运行。"
+
+# 0eec174a2c2b4b95b04019df219554d5
+#: ../../hypervisor_installation.rst:2033
+msgid ""
+"Specify the credential of the domain user while adding a host to CloudStack "
+"so that it can manage it."
+msgstr "在CloudStack中添加主机时请指定域用户凭证，以便CloudStack能够管理主机。"
+
+# 6ff787bf1b1e4267996f97a752a180da
+#: ../../hypervisor_installation.rst:2038
+msgid ""
+"Specify the credential of the domain user while adding a shared SMB primary "
+"or secondary storage."
+msgstr "在添加SMB共享的主存储或者辅助存储时请指定域用户凭证。"
+
+# 08280d229e5a44209e52e6419ea17724
+# 4af21332db304a9b999b0669c5879f16
+# 171afe1cdf5340aaa079bba3c9efaa37
+# a3ca202c8d9242048feefb736684fcbe
+#: ../../hypervisor_installation.rst:2041
+#: ../../hypervisor_installation.rst:2043
+#: ../../hypervisor_installation.rst:2049
+#: ../../hypervisor_installation.rst:2057
+msgid "Migration"
+msgstr "迁移"
+
+# a72a460265644d92b134252e4a8e9ebe
+#: ../../hypervisor_installation.rst:2045
+msgid "Enable Migration."
+msgstr "启用迁移。"
+
+# c879e91d8d184c89b88542de1d7530f5
+#: ../../hypervisor_installation.rst:2047
+msgid ""
+"For more information, see `Configuring Live Migration "
+"<http://technet.microsoft.com/en-us/library/jj134199.aspx>`_."
+msgstr "更多信息，请参考 `配置在线迁移 <http://technet.microsoft.com/en-us/library/jj134199.aspx>`_."
+
+# ddeb2003fe114629bfe83180bfd7434b
+#: ../../hypervisor_installation.rst:2051
+msgid "Delegation"
+msgstr "指派"
+
+# e71e2a9eda1e4d77add23d88c3649f26
+#: ../../hypervisor_installation.rst:2053
+msgid ""
+"If you want to use Live Migration, enable Delegation. Enable the following "
+"services of other hosts participating in Live Migration: CIFS and Microsoft "
+"Virtual System Migration Service."
+msgstr "如果想使用在线迁移，请启用指派。请在使用在线迁移的主机上启用下列服务：CIFS和Microsoft Virtual System Migration Service。"
+
+# d71ba16c4ffa4178b6486c322b550c53
+#: ../../hypervisor_installation.rst:2059
+msgid "Kerberos"
+msgstr "Kerberos"
+
+# 508a39fb29bc4d71b5102e437945f05d
+#: ../../hypervisor_installation.rst:2061
+msgid "Enable Kerberos for Live Migration."
+msgstr "为在线迁移启用Kerberos。"
+
+# 419a33d7988c41c5b9675ff28fbc4f83
+#: ../../hypervisor_installation.rst:2063
+msgid "Network Access Permission for Dial-in"
+msgstr "拨号访问网络权限"
+
+# ac2e195eee054de98c1b29c3a4572263
+#: ../../hypervisor_installation.rst:2065
+msgid "Allow access"
+msgstr "允许访问"
+
+# ccb25d6540064b70906fd1068efdd8ab
+#: ../../hypervisor_installation.rst:2067
+msgid "Allow access for Dial-in connections."
+msgstr "允许拨号连接访问"
+
+# a5c5c4383ba54e519a134d29069914d5
+#: ../../hypervisor_installation.rst:2070
+msgid "Hyper-V Installation Steps"
+msgstr "Hyper-V安装步骤"
+
+# 99fb9754d8c345af83eb13fef2ad291d
+#: ../../hypervisor_installation.rst:2074
+msgid ""
+"Download the operating system from `Windows Server 2012 R2 "
+"<http://technet.microsoft.com/en-us/windowsserver/hh534429>`_."
+msgstr "下载操作系统 `Windows Server 2012 R2 <http://technet.microsoft.com/en-us/windowsserver/hh534429>`_ 。"
+
+# e8f16051cb8e4e6f9930fdd8e88a5125
+#: ../../hypervisor_installation.rst:2078
+msgid ""
+"Install it on the host as given in `Install and Deploy Windows Server 2012 "
+"R2 <http://technet.microsoft.com/library/hh831620>`_."
+msgstr "按照 `Install and Deploy Windows Server 2012 R2 <http://technet.microsoft.com/library/hh831620>`_ 安装操作系统。"
+
+# fe9f3b143dcc4f37858c02e57756925f
+#: ../../hypervisor_installation.rst:2082
+msgid "Post installation, ensure that you enable Hyper-V role in the server."
+msgstr "安装后，请确保安装Hyper-V角色。"
+
+# e8768a97fb33405e9e4edadcd6473632
+#: ../../hypervisor_installation.rst:2086
+msgid ""
+"If no Active Directory domain exists in your deployment, create one and add "
+"users to the domain."
+msgstr "如果当前环境中没有使用AD域，请部署AD域并添加域用户。"
+
+# 9db1342fa13d4f0b8507c35a17a7a308
+#: ../../hypervisor_installation.rst:2091
+msgid ""
+"In the Active Directory domain, ensure that all the Hyper-v hosts are added "
+"so that all the hosts are part of the domain."
+msgstr "如果存在AD域，确保所有的Hyper-V主机都加入了域。"
+
+# c7e961b111f74d8d9cd8bcb3c74e3ef9
+#: ../../hypervisor_installation.rst:2096
+msgid ""
+"Add the domain user to the following groups on the Hyper-V host: Hyper-V "
+"Administrators and Local Administrators."
+msgstr "添加域用户到下列Hyper-V主机的用户组中： Hyper-V Administrators和Local Administrators。"
+
+# 9df5b6c415874cb883224314c9e20535
+#: ../../hypervisor_installation.rst:2101
+msgid "Installing the CloudStack Agent on a Hyper-V Host"
+msgstr "在Hyper-V主机中安装CloudStack代理"
+
+# 8a5b9b9c5a6749c8a37c402622c2fa74
+#: ../../hypervisor_installation.rst:2103
+msgid ""
+"The Hyper-V Agent helps CloudStack perform operations on the Hyper-V hosts. "
+"This Agent communicates with the Management Server and controls all the "
+"instances on the host. Each Hyper-V host must have the Hyper-V Agent "
+"installed on it for successful interaction between the host and CloudStack. "
+"The Hyper-V Agent runs as a Windows service. Install the Agent on each host "
+"using the following steps."
+msgstr "Hyper-V代理帮助CloudStack操作Hyper-V主机。代理与管理服务器通讯并控制主机上的所有实例。为了让主机与CloudStack之间成功的进行交互，每个Hyper-V主机必须安装Hyper-V代理。Hyper-V代理作为Windows的系统服务运行。按照下里的步骤在每台主机上安装Agent。"
+
+# 47de8548d8d141569c4665678df1976c
+#: ../../hypervisor_installation.rst:2110
+msgid ""
+"CloudStack Management Server communicates with Hyper-V Agent by using HTTPS."
+" For secure communication between the Management Server and the host, "
+"install a self-signed certificate on port 8250."
+msgstr "CloudStack管理服务器使用HTTPS与Hyper-V代理通讯。为了使管理服务器与主机之间能够使用加密通讯，请在8250端口上绑定自签名证书。"
+
+# 16689e77021c459b9b2fb8ac046290b9
+#: ../../hypervisor_installation.rst:2115
+msgid ""
+"The Agent installer automatically perform this operation. You have not "
+"selected this option during the Agent installation, it can also be done "
+"manually as given in step 1."
+msgstr "代理的安装程序会自动执行这个操作。在代理的安装过程中可以不选择该选项，它可以在步骤1中手动操作。"
+
+# 3b0ee4121a5e4bb1ac39974e02a6da46
+#: ../../hypervisor_installation.rst:2119
+msgid "Create and add a self-signed SSL certificate on port 8250:"
+msgstr "为8250端口创建并添加一个自签名证书："
+
+# 884ff72564e24ca5b278ddc37b37a0c5
+#: ../../hypervisor_installation.rst:2123
+msgid "Create A self-signed SSL certificate:"
+msgstr "创建一个自签名证书："
+
+# 4e30082071c043499c064e67980e167e
+#: ../../hypervisor_installation.rst:2129
+msgid ""
+"This command creates the self-signed certificate and add that to the "
+"certificate store ``LocalMachine\\My``."
+msgstr "该命令创建一个自签名证书并将添加到 ``LocalMachine\\My`` 证书区域。"
+
+# 1b6139e4fef04fa9a4b68f34f9fb85b3
+#: ../../hypervisor_installation.rst:2134
+msgid "Add the created certificate to port 8250 for https communication:"
+msgstr "将创建好的证书绑定到https通信的8250端口："
+
+# 96581439bebc46468b7bf6846881ea0a
+#: ../../hypervisor_installation.rst:2140
+msgid "Thumbprint is the thumbprint of the certificate you created."
+msgstr "Thumbprint是你创建证书的指纹。"
+
+# 47858b43d7b74ce8afa4368788b0c514
+#: ../../hypervisor_installation.rst:2144
+msgid ""
+"Build the CloudStack Agent for Hyper-V as given in `Building CloudStack "
+"Hyper-V Agent "
+"<https://cwiki.apache.org/confluence/display/CLOUDSTACK/Creating+Hyperv+Agent+Installer>`__."
+msgstr "按照 `编辑 CloudStack Hyper-V 代理 <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Creating+Hyperv+Agent+Installer>`__编译CloudStack代理程序。"
+
+# 0aa2346be94a42638e7fc6ea9cdbeb91
+#: ../../hypervisor_installation.rst:2150
+msgid "As an administrator, run the installer."
+msgstr "以管理员权限运行安装。"
+
+# 0d17e4d0f5284921b771f773cb0356fe
+#: ../../hypervisor_installation.rst:2154
+msgid "Provide the Hyper-V admin credentials when prompted."
+msgstr "在对话框中输入Hyper-V管理员凭证。"
+
+# 5d834f623db14558b8eeda52cfe973a4
+#: ../../hypervisor_installation.rst:2156
+msgid ""
+"When the agent installation is finished, the agent runs as a service on the "
+"host machine."
+msgstr "当代理安装完成之后，代理已经作为系统服务启动了。"
+
+# 31461c4200094300b939e83c48affcbf
+#: ../../hypervisor_installation.rst:2160
+msgid "Physical Network Configuration for Hyper-V"
+msgstr "为Hyper-V配置物理网络"
+
+# 869e4b869e4241038151ead9ffae6ab5
+#: ../../hypervisor_installation.rst:2162
+msgid ""
+"You should have a plan for how the hosts will be cabled and which physical "
+"NICs will carry what types of traffic. By default, CloudStack will use the "
+"device that is used for the default route."
+msgstr "需要先对主机连线以及网卡绑定哪种流量做出规划。默认情况下，CloudStack将正在被使用的设备作为默认路由。"
+
+# b114113246f94742ac60bd1331c5d976
+#: ../../hypervisor_installation.rst:2176
+msgid "Storage Preparation for Hyper-V (Optional)"
+msgstr "为Hyper-V准备存储（可选）"
+
+# 506240beff9d4e2d9cfa7bc22a95d5f3
+#: ../../hypervisor_installation.rst:2178
+msgid ""
+"CloudStack allows administrators to set up shared Primary Storage and "
+"Secondary Storage that uses SMB."
+msgstr "CloudStack允许管理员使用SMB共享作为主存储和辅助存储。"
+
+# dd424079b5f94f9581d499ab92498b1a
+#: ../../hypervisor_installation.rst:2183
+msgid "Create a SMB storage and expose it over SMB Version 3."
+msgstr "创建一个使用SMB v3协议的SMB存储"
+
+# 616667a633f54bcdb3ca3bc0090bf3a9
+#: ../../hypervisor_installation.rst:2185
+msgid ""
+"For more information, see `Deploying Hyper-V over SMB "
+"<http://technet.microsoft.com/en-us/library/jj134187.aspx>`_."
+msgstr "更多信息，请参考 `部署基于SMB的Hyper-V <http://technet.microsoft.com/en-us/library/jj134187.aspx>`_."
+
+# d1f47f8ed99f43008e763770fe26cbfb
+#: ../../hypervisor_installation.rst:2187
+msgid ""
+"You can also create and export SMB share using Windows. After the Windows "
+"Server 2012 R2 installation, select File and Storage Services from Server "
+"Roles to create an SMB file share. For more information, see `Creating an "
+"SMB File Share Using Server Manager <http://technet.microsoft.com/en-"
+"us/library/jj134187.aspx#BKMK_Step3>`_."
+msgstr "同样可以使用Windows创建并发布SMB共享。在Windows Server 2012 R2安装完成之后，在服务器角色中选择安装文件和存储服务以便创建SMB文件共享。更多信息，请参考 `通过使用服务器管理器 (SM) 创建 SMB 文件共享系统 <http://technet.microsoft.com/zh-cn/library/jj134187.aspx#BKMK_Step3>`_。"
+
+# 719f8c1fe9e0467299d8d1cfeea8f097
+#: ../../hypervisor_installation.rst:2194
+msgid "Add the SMB share to the Active Directory domain."
+msgstr "在AD域中添加SMB共享。"
+
+# 16b6241ff51c43208f9ac1cdabf59ef1
+#: ../../hypervisor_installation.rst:2196
+msgid ""
+"The SMB share and the hosts managed by CloudStack need to be in the same "
+"domain. However, the storage should be accessible from the Management Server"
+" with the domain user privileges."
+msgstr "SMB共享和通过CloudStack管理的主机必须在同一个域内。管理服务器可以使用域用户凭证访问存储。"
+
+# 079ed026cdb94e58ba4ab2ea29fae3f7
+#: ../../hypervisor_installation.rst:2202
+msgid ""
+"While adding storage to CloudStack, ensure that the correct domain, and "
+"credentials are supplied. This user should be able to access the storage "
+"from the Management Server."
+msgstr "在CloudStack中添加存储时，请确保提供的域和凭证是正确的。确保用户可以通过管理服务器访问存储。"
+
+# 160301917c8340169daad29cbd70f33c
+#: ../../hypervisor_installation.rst:2207
+msgid "VMware vSphere Installation and Configuration"
+msgstr "VMware vSphere 安装和配置"
+
+# b11df8a743bc40e0985ade1b95bb1552
+#: ../../hypervisor_installation.rst:2209
+msgid ""
+"If you want to use the VMware vSphere hypervisor to run guest virtual "
+"machines, install vSphere on the host(s) in your cloud."
+msgstr "如果计划使用VMware vSphere平台运行虚拟机，请在云中安装vSphere主机。"
+
+# 3d9610f8babc47a180e75af13f6672b9
+#: ../../hypervisor_installation.rst:2213
+msgid "System Requirements for vSphere Hosts"
+msgstr "vSphere主机的系统要求"
+
+# 470fc59fd16240b480948999f7843a6d
+#: ../../hypervisor_installation.rst:2216
+msgid "Software requirements:"
+msgstr "软件要求："
+
+# 9183ed2e4d2a458791ebbe4949777c1e
+#: ../../hypervisor_installation.rst:2220
+msgid "vSphere and vCenter, both version 4.1 or 5.0."
+msgstr "vSphere和vCenter版本，4.1或5.0。"
+
+# 766663a5920b45398c7575a5e9e38ff6
+#: ../../hypervisor_installation.rst:2222
+msgid ""
+"vSphere Standard is recommended. Note however that customers need to "
+"consider the CPU constraints in place with vSphere licensing. See "
+"`http://www.vmware.com/files/pdf/vsphere\\_pricing.pdf "
+"<http://www.vmware.com/files/pdf/vsphere_pricing.pdf>`_ and discuss with "
+"your VMware sales representative."
+msgstr "建议使用vSphere标准版。但是VMware用户需要考虑vSphere授权对CPU的限制。请参考 `http://www.vmware.com/files/pdf/vsphere\\_pricing.pdf <http://www.vmware.com/files/pdf/vsphere_pricing.pdf>`_ 并与销售代表讨论。"
+
+# f1661195861840288269ea1202e9b89e
+#: ../../hypervisor_installation.rst:2227
+msgid "vCenter Server Standard is recommended."
+msgstr "建议使用vCenter标准版。"
+
+# 285b4b4fca1a4889a32a95763f40cbe3
+#: ../../hypervisor_installation.rst:2231
+msgid ""
+"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."
+msgstr "请确保安装了hypervisor供应商发布的所有补丁程序。随时关注供应商支持信息，一旦发布补丁就立即安装。CloudStack不会跟踪或提醒你安装这些补丁。安装最新的补丁程序对主机至关重要。hypervisor供应商可能不会对过期的系统提供技术支持。"
+
+# fea907bc006c4462af1e5c66fff27418
+#: ../../hypervisor_installation.rst:2240
+msgid ""
+"Apply All Necessary Hotfixes. The lack of up-do-date hotfixes can lead to "
+"data corruption and lost VMs."
+msgstr "安装一切必要的补丁程序。缺乏最新补丁程序可能会导致数据和虚拟机丢失。"
+
+# 0e3d7163cdaa45efb1a1de9c1d840c70
+#: ../../hypervisor_installation.rst:2243
+msgid "Hardware requirements:"
+msgstr "硬件要求："
+
+# c2829bd33bf44fcb92b5e6aeca93fe3d
+#: ../../hypervisor_installation.rst:2247
+msgid ""
+"The host must be certified as compatible with vSphere. See the VMware "
+"Hardware Compatibility Guide at "
+"`http://www.vmware.com/resources/compatibility/search.php "
+"<http://www.vmware.com/resources/compatibility/search.php>`_."
+msgstr "主机必须通过vSphere的兼容性认证。请查看VMware硬件兼容性指南 `http://www.vmware.com/resources/compatibility/search.php <http://www.vmware.com/resources/compatibility/search.php>`_."
+
+# 90885bc4493d423b802629ca42671470
+#: ../../hypervisor_installation.rst:2253
+msgid ""
+"All hosts must be 64-bit and must support HVM (Intel-VT or AMD-V enabled)."
+msgstr "所有主机必须为64位架构并且支持HVM(启用Intel-VT或AMD-V)。"
+
+# 444698b909b14c1bafa79d28ca6d0e0c
+#: ../../hypervisor_installation.rst:2258
+msgid ""
+"All hosts within a cluster must be homogenous. That means the CPUs must be "
+"of the same type, count, and feature flags."
+msgstr "同一群集中的所有节点必须为同一架构。CPU型号、数量和功能参数必须相同。"
+
+# 026389f5c21248f094a1988283f9ceaa
+#: ../../hypervisor_installation.rst:2286
+msgid "vCenter Server requirements:"
+msgstr "vCenter服务器的系统要求："
+
+# 898e1faee1144e9b8fb1ae76627f710a
+#: ../../hypervisor_installation.rst:2290
+msgid ""
+"Processor - 2 CPUs 2.0GHz or higher Intel or AMD x86 processors. Processor "
+"requirements may be higher if the database runs on the same machine."
+msgstr "处理器 - 2颗2.0GHz的Intel或AMD x86 CPUs， 或更高的处理器。如果数据库跟VC在同一台服务器中，可能会需要更高的处理器。"
+
+# b912675600f2430a96805b275c1f1569
+#: ../../hypervisor_installation.rst:2296
+msgid ""
+"Memory - 3GB RAM. RAM requirements may be higher if your database runs on "
+"the same machine."
+msgstr "内存 - 3GB。如果数据库跟VC在同一台服务器中，可能会需要更多内存。"
+
+# ff655342fa17404384b080f9a3991839
+#: ../../hypervisor_installation.rst:2301
+msgid ""
+"Disk storage - 2GB. Disk requirements may be higher if your database runs on"
+" the same machine."
+msgstr "磁盘空间 - 2GB。如果数据库跟VC在同一台服务器中，可能会需要更多的磁盘空间。"
+
+# 34c75fcd20d44f5ab2bfaa95be9c7646
+#: ../../hypervisor_installation.rst:2306
+msgid ""
+"Microsoft SQL Server 2005 Express disk requirements. The bundled database "
+"requires up to 2GB free disk space to decompress the installation archive."
+msgstr "Microsoft SQL Server 2005 Express磁盘要求。最多需要 2 GB 的可用磁盘空间解压安装文件。"
+
+# 0699f7fd865549849d921d930b9fa7ea
+#: ../../hypervisor_installation.rst:2312
+msgid "Networking - 1Gbit or 10Gbit."
+msgstr "网络 - 1Gbit或者10Gbit。"
+
+# cef076dcedee4a24b9b3ec51ef9ee68f
+#: ../../hypervisor_installation.rst:2314
+msgid ""
+"For more information, see `\"vCenter Server and the vSphere Client Hardware "
+"Requirements\" "
+"<http://pubs.vmware.com/vsp40/wwhelp/wwhimpl/js/html/wwhelp.htm#href=install/c_vc_hw.html>`_."
+msgstr "更多信息，请参考 `\"vCenter Server 和 vSphere Client 硬件要求\" <http://pubs.vmware.com/vsp40/wwhelp/wwhimpl/js/html/wwhelp.htm#href=install/c_vc_hw.html>`_。"
+
+# 66ca94319c714dc4a9216ea740c56b40
+#: ../../hypervisor_installation.rst:2317
+msgid "Other requirements:"
+msgstr "其他要求："
+
+# c76079dbdb8c48af90c236f2d0baa787
+#: ../../hypervisor_installation.rst:2321
+msgid ""
+"VMware vCenter Standard Edition 4.1 or 5.0 must be installed and available "
+"to manage the vSphere hosts."
+msgstr "必须安装VMware vCenter Standard 4.1或5.0版本，并且能够管理vSphere主机。"
+
+# 07375471238a4fa0a0f29e14060188ab
+#: ../../hypervisor_installation.rst:2326
+msgid ""
+"vCenter must be configured to use the standard port 443 so that it can "
+"communicate with the CloudStack Management Server."
+msgstr "必须配置vCenter使用443端口与CloudStack管理服务器通讯。"
+
+# fa50c73129ea428e839debdffdc10099
+#: ../../hypervisor_installation.rst:2331
+msgid ""
+"You must re-install VMware ESXi if you are going to re-use a host from a "
+"previous install."
+msgstr "如果你计划利用之前安装的主机，那么必须重新安装VMware ESXi。"
+
+# 5d54cd6b7cda47869cebff7b876565d1
+#: ../../hypervisor_installation.rst:2336
+msgid ""
+"CloudStack requires VMware vSphere 4.1 or 5.0. VMware vSphere 4.0 is not "
+"supported."
+msgstr "CloudStack要求VMwarevSphere 4.1或者5.0版本，不支持VMware vSphere 4.0版本。"
+
+# 15bdac339f71483d96232a6684a05f38
+#: ../../hypervisor_installation.rst:2341
+msgid ""
+"All hosts must be 64-bit and must support HVM (Intel-VT or AMD-V enabled). "
+"All hosts within a cluster must be homogeneous. That means the CPUs must be "
+"of the same type, count, and feature flags."
+msgstr "所有主机必须为64位架构并且支持HVM(启用Intel-VT或AMD-V)。同一群集中的所有节点必须为同一架构。CPU型号、数量和功能参数必须相同。"
+
+# 3320ef7bcf874235ad145cfe38f4f21d
+#: ../../hypervisor_installation.rst:2347
+msgid ""
+"The CloudStack management network must not be configured as a separate "
+"virtual network. The CloudStack management network is the same as the "
+"vCenter management network, and will inherit its configuration. See :ref"
+":`configure-vcenter-management-network`."
+msgstr "CloudStack 管理网络不能使用独立的虚拟网络。CloudStack使用vCenter的管理网络，并继承vCenter管理网络的配置。 可参考 :ref:`configure-vcenter-management-network`."
+
+# b7b26fdba3ba429a9b554e95c7aea05a
+#: ../../hypervisor_installation.rst:2354
+msgid "CloudStack requires ESXi. ESX is not supported."
+msgstr "CloudStack仅支持ESXi，不支持ESX。"
+
+# 807a6a01a8cb40bb9ddafcf3d4f6e055
+#: ../../hypervisor_installation.rst:2358
+msgid ""
+"All resources used for CloudStack must be used for CloudStack only. "
+"CloudStack cannot share instance of ESXi or storage with other management "
+"consoles. Do not share the same storage volumes that will be used by "
+"CloudStack with a different set of ESXi servers that are not managed by "
+"CloudStack."
+msgstr "所有用于CloudStack的资源只能被CloudStack使用。CloudStack无法与其他管理控制台共享ESXi实例或存储。请不要与其他不受CloudStack管理的ESXi共享同一个存储卷。"
+
+# 76ba09bd8f5d4ab69dfa682a87e2f2e7
+#: ../../hypervisor_installation.rst:2366
+msgid ""
+"Put all target ESXi hypervisors in a cluster in a separate Datacenter in "
+"vCenter."
+msgstr "将所有目标ESXi hypervisors加入vCenter中独立数据中心之下的群集。"
+
+# 57a49ec20ce243989933f66ba4d87eed
+#: ../../hypervisor_installation.rst:2371
+msgid ""
+"The cluster that will be managed by CloudStack should not contain any VMs. "
+"Do not run the management server, vCenter or any other VMs on the cluster "
+"that is designated for CloudStack use. Create a separate cluster for use of "
+"CloudStack and make sure that they are no VMs in this cluster."
+msgstr "将被CloudStack管理的群集中不应该存在任何VM。且不应该在CloudStack管理的群集中运行任何管理服务器、vCenter或者VM。为CloudStack创建一个独立的群集，并确保群集中不存在VM。"
+
+# 6fd4edef52d2463fa27009ad3626e5fa
+#: ../../hypervisor_installation.rst:2379
+msgid ""
+"All the required VLANS must be trunked into all network switches that are "
+"connected to the ESXi hypervisor hosts. These would include the VLANS for "
+"Management, Storage, vMotion, and guest VLANs. The guest VLAN (used in "
+"Advanced Networking; see Network Setup) is a contiguous range of VLANs that "
+"will be managed by CloudStack."
+msgstr "所有必需的vlan必须通过所有网络交换机端口的trunk模式连接到ESXi hypervisor主机。其中包含管理，存储，vMotion和来宾等VLANs。CloudStack管理一段连续的来宾VLANs范围(高级网络；请参阅 网络设置) 。"
+
+# 5b9b5d9bb49f48c790d3d7975da36b97
+#: ../../hypervisor_installation.rst:2386
+msgid "Preparation Checklist for VMware"
+msgstr "VMware的准备工作清单"
+
+# 874ada2598f94f90bbb7ea1051a0fc8e
+#: ../../hypervisor_installation.rst:2393
+msgid "Information listed in :ref:`vcenter-checklist`"
+msgstr ":ref:`vcenter-checklist` 中列出的信息"
+
+# c8657d9c46a84e94b59a49ebfeceb4cd
+#: ../../hypervisor_installation.rst:2397
+msgid "Information listed in :ref:`networking-checklist-for-vmware`"
+msgstr ":ref:`networking-checklist-for-vmware` 中列出的信息"
+
+# d25566ef8de84fd9ba474e9c493effb9
+#: ../../hypervisor_installation.rst:2402
+msgid "vCenter Checklist"
+msgstr "vCenter检查清单"
+
+# d47240a593424a1cb059bcc359843fb6
+#: ../../hypervisor_installation.rst:2404
+msgid "You will need the following information about vCenter."
+msgstr "你需要关于vCenter的下列信息："
+
+# ad424c3b64d84058957622e7ccb34e2f
+#: ../../hypervisor_installation.rst:2407
+msgid "vCenter Requirement"
+msgstr "vCenter要求"
+
+# aa42ada253634235831462bb3b3a5a5a
+# 6971b4e11acf438191565fdff1f8ce8d
+# bc087c8de60d40f191079b58516386bc
+#: ../../hypervisor_installation.rst:2407
+#: ../../hypervisor_installation.rst:2423
+#: ../../hypervisor_installation.rst:2715
+msgid "Notes"
+msgstr "备注"
+
+# 3615f6d25ad94970828a9bf159bc7a33
+#: ../../hypervisor_installation.rst:2409
+msgid "vCenter User"
+msgstr "vCenter用户"
+
+# 9c1c7400557045389a7acb14690f4c62
+#: ../../hypervisor_installation.rst:2409
+msgid "This user must have admin privileges."
+msgstr "用户必须拥有管理员权限。"
+
+# 7bf8f233cd574453b441875c1fbc344e
+#: ../../hypervisor_installation.rst:2410
+msgid "vCenter User Password"
+msgstr "vCenter用户的密码"
+
+# 936bd3768ff3435cb10fa077957eb873
+#: ../../hypervisor_installation.rst:2410
+msgid "Password for the above user."
+msgstr "上述用户的密码。"
+
+# 6fe51d4e1ca14592b03fcae9bf28db36
+#: ../../hypervisor_installation.rst:2411
+msgid "vCenter Datacenter Name"
+msgstr "vCenter数据库名称"
+
+# e32c306acc384d02b3d67c109698f082
+#: ../../hypervisor_installation.rst:2411
+msgid "Name of the datacenter."
+msgstr "数据中心名称"
+
+# 50068ce776c541ca8a56a9a1475d34ec
+#: ../../hypervisor_installation.rst:2412
+msgid "vCenter Cluster Name"
+msgstr "vCenter群集名称"
+
+# a6bf766a42e04a9185b699474ee058d3
+#: ../../hypervisor_installation.rst:2412
+msgid "Name of the cluster."
+msgstr "群集名称"
+
+# 8956e9c5f49e48da99562ae0cf8b5697
+#: ../../hypervisor_installation.rst:2418
+msgid "Networking Checklist for VMware"
+msgstr "VMware网络清单"
+
+# 56e3476f8f4e40fa97acfa540fa0a79a
+#: ../../hypervisor_installation.rst:2420
+msgid "You will need the following information about VLAN."
+msgstr "你需要以下关于VLAN的信息。"
+
+# 9cc0357ae70f44829be639ba80443de3
+#: ../../hypervisor_installation.rst:2423
+msgid "VLAN Information"
+msgstr "VLAN信息"
+
+# f08b03cbe30347b4bc3ea89dfa2faca6
+#: ../../hypervisor_installation.rst:2425
+msgid "ESXi VLAN"
+msgstr "ESXi VLAN"
+
+# 18957fe16bfc40a18dfba9f47792be6b
+#: ../../hypervisor_installation.rst:2425
+msgid "VLAN on which all your ESXi hypervisors reside."
+msgstr "全部ESXi hypervisors主机所在的VLAN。"
+
+# a5c6d87944d44ba8abb37262b7ac9ae1
+#: ../../hypervisor_installation.rst:2426
+msgid "ESXI VLAN IP Address"
+msgstr "ESXi VLAN IP地址"
+
+# 3c0852bce08f43928a28be17866c883b
+#: ../../hypervisor_installation.rst:2426
+msgid ""
+"IP Address Range in the ESXi VLAN. One address per Virtual Router is used "
+"from this range."
+msgstr "ESXi VLAN的IP地址范围。每个虚拟路由器使用该范围内的一个IP。"
+
+# 788afe1854b74f6480fb9dcb08317b37
+#: ../../hypervisor_installation.rst:2427
+msgid "ESXi VLAN IP Gateway"
+msgstr "ESXi VLAN网关IP"
+
+# bacedb178b3f4b95a2644000683e5540
+#: ../../hypervisor_installation.rst:2428
+msgid "ESXi VLAN Netmask"
+msgstr "ESXi VLAN子网掩码"
+
+# 4d4785e85cef4d06b971d1c0d7e275ad
+#: ../../hypervisor_installation.rst:2429
+msgid "Management Server VLAN"
+msgstr "管理服务器VLAN"
+
+# 01e4e85ca9534e50803fe477a0556770
+#: ../../hypervisor_installation.rst:2429
+msgid "VLAN on which the CloudStack Management server is installed."
+msgstr "CloudStack管理服务器所在的VLAN。"
+
+# a6572d2d1cc14b38a161ef09f9ba2e72
+#: ../../hypervisor_installation.rst:2430
+msgid "Public VLAN"
+msgstr "公共网络VLAN"
+
+# 0c60da1f668640db9432f89beeebcfdc
+#: ../../hypervisor_installation.rst:2430
+msgid "VLAN for the Public Network."
+msgstr "公共网络的VLAN"
+
+# 4525e1b8f6f141ae8d9225392c099184
+#: ../../hypervisor_installation.rst:2431
+msgid "Public VLAN Gateway"
+msgstr "公共网络VLAN的网关"
+
+# 32104578607045e38f78075c77df1e63
+#: ../../hypervisor_installation.rst:2432
+msgid "Public VLAN Netmask"
+msgstr "公共网络VLAN的子网掩码"
+
+# 57123c0a394241c6a639de412ffb9b8f
+#: ../../hypervisor_installation.rst:2433
+msgid "Public VLAN IP Address Range"
+msgstr "公共VLAN IP地址范围"
+
+# 932e6245886a44928cf95b929f3e6735
+#: ../../hypervisor_installation.rst:2433
+msgid ""
+"Range of Public IP Addresses available for CloudStack use. These addresses "
+"will be used for virtual router on CloudStack to route private traffic to "
+"external networks."
+msgstr "CloudStack使用的公共网络IP范围。CloudStack中的虚拟路由器使用这些地址，用于路由专用流量至外部网络。"
+
+# 0200790a79464d739ec724252e076ed3
+#: ../../hypervisor_installation.rst:2436
+msgid "VLAN Range for Customer use"
+msgstr "客户使用的VLAN范围"
+
+# 15e968a010ac44c5ae838310d7b27d7e
+#: ../../hypervisor_installation.rst:2436
+msgid ""
+"A contiguous range of non-routable VLANs. One VLAN will be assigned for each"
+" customer."
+msgstr "连续的不可路由的VLAN范围。每个用户会分配一个VLAN。"
+
+# bce73cc0c26e46fdb3ad7c900ead3c2e
+#: ../../hypervisor_installation.rst:2442
+msgid "vSphere Installation Steps"
+msgstr "vSphere安装步骤"
+
+# 08bd5d58d94f4362976973d3b3c71f1a
+#: ../../hypervisor_installation.rst:2446
+msgid ""
+"If you haven't already, you'll need to download and purchase vSphere from "
+"the VMware Website (`https://www.vmware.com/tryvmware/index.php?p=vmware-"
+"vsphere&lp=1 <https://www.vmware.com/tryvmware/index.php?p=vmware-"
+"vsphere&lp=1>`_) and install it by following the VMware vSphere Installation"
+" Guide."
+msgstr "如果你还没用准备好安装介质，请在VMware网站下载和购买(`https://www.vmware.com/tryvmware/index.php?p=vmware-vsphere&lp=1 <https://www.vmware.com/tryvmware/index.php?p=vmware-vsphere&lp=1>`_)并按照VMware vSphere安装指南安装。"
+
+# 2ef333c7f2f54869bbd02d3235194cec
+#: ../../hypervisor_installation.rst:2453
+msgid ""
+"Following installation, perform the following configuration, which are "
+"described in the next few sections:"
+msgstr "安装过程中，执行下面几个章节描述的以下配置："
+
+# d396f645a258483aa100dd126802bed6
+#: ../../hypervisor_installation.rst:2457
+msgid "Required"
+msgstr "要求"
+
+# 3a47305e100d4c5ab944fb0fb97c58d3
+#: ../../hypervisor_installation.rst:2457
+msgid "Optional"
+msgstr "可选项"
+
+# 99ddd825c54741ec930bc538c64459f0
+#: ../../hypervisor_installation.rst:2459
+msgid "ESXi host setup"
+msgstr "ESXi主机安装"
+
+# 32420a57854f4107b19dc23c22c16b51
+#: ../../hypervisor_installation.rst:2459
+msgid "NIC bonding"
+msgstr "网卡绑定"
+
+# 88aad3fa642f4dc29607367b57b8c766
+#: ../../hypervisor_installation.rst:2460
+msgid ""
+"Configure host physical networking,virtual switch, vCenter Management "
+"Network, and extended port range"
+msgstr "配置主机的物理网络，虚拟交换机，vCenter管理网络和扩展的端口范围"
+
+# 5406679428f94ce0b5ef1336e5ce693a
+#: ../../hypervisor_installation.rst:2460
+msgid "Multipath storage"
+msgstr "存储多路径"
+
+# 7a4bde3b86a141e5bcd9b6627e56b47a
+#: ../../hypervisor_installation.rst:2461
+msgid "Prepare storage for iSCSI"
+msgstr "准备iSCSI存储"
+
+# a4f0a1b396ad4b818fcb8fae9d2a3845
+#: ../../hypervisor_installation.rst:2462
+msgid ""
+"Configure clusters in vCenter and add hosts to them, or add hosts without "
+"clusters to vCenter"
+msgstr "在vCenter中配置集群并添加主机，或不使用集群，直接在vCenter中添加主机。"
+
+# 66a1da1529c64722bbe6a32e6a09b81e
+#: ../../hypervisor_installation.rst:2466
+msgid "ESXi Host setup"
+msgstr "ESXi主机配置"
+
+# d2206ae8b8b0405a82421a944b690f6f
+#: ../../hypervisor_installation.rst:2468
+msgid ""
+"All ESXi hosts should enable CPU hardware virtualization support in BIOS. "
+"Please note hardware virtualization support is not enabled by default on "
+"most servers."
+msgstr "所有ESXi主机都应该在BIOS中启用CPU硬件虚拟化支持。请注意，大多数服务器默认不启用该功能。"
+
+# 823edf72601b46f9b41f1f0331025b0e
+#: ../../hypervisor_installation.rst:2473
+msgid "Physical Host Networking"
+msgstr "物理主机网络"
+
+# 65fdae591c2a496aaf6f4432c910b4e6
+#: ../../hypervisor_installation.rst:2475
+msgid ""
+"You should have a plan for cabling the vSphere hosts. Proper network "
+"configuration is required before adding a vSphere host to CloudStack. To "
+"configure an ESXi host, you can use vClient to add it as standalone host to "
+"vCenter first. Once you see the host appearing in the vCenter inventory "
+"tree, click the host node in the inventory tree, and navigate to the "
+"Configuration tab."
+msgstr "您应该准备一个vSphere主机连接的规划。将主机添加至CloudStack之前，需要合理地配置网络。要配置ESXi主机，可以先用vClient将它作为独立主机添加到vCenter。当您在vCenter的导航树中看到该主机时，点击它，选择配置页。"
+
+# 08dd99eb935744d5a55a302fd892936d
+#: ../../hypervisor_installation.rst:2482
+msgid "|vspherephysicalnetwork.png: vSphere client|"
+msgstr "|vspherephysicalnetwork.png: vSphere client|"
+
+# e80e2656108441bcbec60c3069da6b89
+#: ../../hypervisor_installation.rst:2484
+msgid ""
+"In the host configuration tab, click the \"Hardware/Networking\" link to "
+"bring up the networking configuration page as above."
+msgstr "在主机的配置标签页中，点击\"硬件/网络\"链接转到上图中的网络配置页。"
+
+# 3b5704fb76c04adf9b622f63103e009a
+#: ../../hypervisor_installation.rst:2488
+msgid "Configure Virtual Switch"
+msgstr "配置虚拟交换机"
+
+# d08703f6feb244bd95ae9b14321f374a
+#: ../../hypervisor_installation.rst:2490
+msgid ""
+"A default virtual switch vSwitch0 is created. CloudStack requires all ESXi "
+"hosts in the cloud to use the same set of virtual switch names. If you "
+"change the default virtual switch name, you will need to configure one or "
+"more CloudStack configuration variables as well."
+msgstr "默认情况下，系统会创建虚拟交换机vSwitch0。CloudStack要求云中所有ESXi主机中的虚拟交换机都使用相同的名字。如果你改变了默认虚拟交换机名称，那么你需要改变一个或多个CloudStack配置。"
+
+# 2a8a290d8bc24c6e9efe5ebf03605fe1
+#: ../../hypervisor_installation.rst:2496
+msgid "Separating Traffic"
+msgstr "流量隔离"
+
+# 81f6d7108ad046f58db096bb486a7c45
+#: ../../hypervisor_installation.rst:2498
+msgid ""
+"CloudStack allows you to use vCenter to configure three separate networks "
+"per ESXi host. These networks are identified by the name of the vSwitch they"
+" are connected to. The allowed networks for configuration are public (for "
+"traffic to/from the public internet), guest (for guest-guest traffic), and "
+"private (for management and usually storage traffic). You can use the "
+"default virtual switch for all three, or create one or two other vSwitches "
+"for those traffic types."
+msgstr "CloudStack允许你使用vCenter为每个ESXi主机配置三个独立的网络。CloudStack通过vSwitch的名称识别网络。允许配置的网络分别为公共网络(与公共互联网之间的流量)，来宾网络(来宾-来宾流量)和管理网络(与管理服务器和存储之间的流量)。您可以设置3种网络使用默认的虚拟交换机，或创建1个/2个其他虚拟交换机来承载这些网络流量。"
+
+# e01fb6b864ae4591a6040e3227eb3981
+#: ../../hypervisor_installation.rst:2506
+msgid ""
+"If you want to separate traffic in this way you should first create and "
+"configure vSwitches in vCenter according to the vCenter instructions. Take "
+"note of the vSwitch names you have used for each traffic type. You will "
+"configure CloudStack to use these vSwitches."
+msgstr "如果您想以这样的方式隔离流量，首先应按照vCenter的指南在vCenter中创建并配置虚拟交换机。请记录每种网络使用的虚拟交换机名称。您需要配置CloudStack使用这些虚拟交换机。"
+
+# c101a9ffcc8a41ed9d941197df3790d6
+#: ../../hypervisor_installation.rst:2512
+msgid "Increasing Ports"
+msgstr "增加端口"
+
+# 67408afd6515434a8dc9b58d7b1096c2
+#: ../../hypervisor_installation.rst:2514
+msgid ""
+"By default a virtual switch on ESXi hosts is created with 56 ports. We "
+"recommend setting it to 4088, the maximum number of ports allowed. To do "
+"that, click the \"Properties...\" link for virtual switch (note this is not "
+"the Properties link for Networking)."
+msgstr "ESXi主机的虚拟交换机默认有56个端口。我们建议设为最大允许数4088。要设置该值，请点击虚拟交换机的“属性…”链接(注意，不是网络的属性)。"
+
+# 91a0ee49c11047d69398dc65246ee508
+#: ../../hypervisor_installation.rst:2519
+msgid "|vsphereincreaseports.png: vSphere client|"
+msgstr "|vsphereincreaseports.png: vSphere client|"
+
+# 1b199b2c7fb64a27867df7bf2aa8ae31
+#: ../../hypervisor_installation.rst:2521
+msgid ""
+"In vSwitch properties dialog, select the vSwitch and click Edit. You should "
+"see the following dialog:"
+msgstr "在vSwitch属性对话框中，选择vSwitch，点击“编辑”，您将看到以下对话框："
+
+# 1553cfe713e84e788e2d8d9138ddc93c
+#: ../../hypervisor_installation.rst:2524
+msgid "|vspherevswitchproperties.png: vSphere client|"
+msgstr "|vspherevswitchproperties.png: vSphere client|"
+
+# 30c0ae1e71ec432faf1aa6694a4de217
+#: ../../hypervisor_installation.rst:2526
+msgid ""
+"In this dialog, you can change the number of switch ports. After you've done"
+" that, ESXi hosts are required to reboot in order for the setting to take "
+"effect."
+msgstr "在该对话框中，您可以修改端口数量。修改完后，为使配置生效，需要重启ESXi主机。"
+
+# 0ea01f09979f42be9b806229aa47d2c4
+#: ../../hypervisor_installation.rst:2533
+msgid "Configure vCenter Management Network"
+msgstr "配置vCenter管理网络"
+
+# 116d1ea7700444689448850f261cfded
+#: ../../hypervisor_installation.rst:2535
+msgid ""
+"In the vSwitch properties dialog box, you may see a vCenter management "
+"network. This same network will also be used as the CloudStack management "
+"network. CloudStack requires the vCenter management network to be configured"
+" properly. Select the management network item in the dialog, then click "
+"Edit."
+msgstr "在vSwith属性对话框中，您可以看到一个vCenter管理网络。CloudStack的管理网络也使用该网络。CloudStack要求正确配置vCenter的管理网络。在对话框中点击管理网络，然后点击编辑。"
+
+# 7ff1766a196f4699991eda06e976010c
+#: ../../hypervisor_installation.rst:2541
+msgid "|vspheremgtnetwork.png: vSphere client|"
+msgstr "|vspheremgtnetwork.png: vSphere client|"
+
+# bac7d94e1edb4ea5806db13d09308ac2
+#: ../../hypervisor_installation.rst:2543
+msgid "Make sure the following values are set:"
+msgstr "请确保配置以下设置："
+
+# af96ead47c0044bab364251d55a3b39e
+#: ../../hypervisor_installation.rst:2547
+msgid "VLAN ID set to the desired ID"
+msgstr "VLAN ID设置为期望的ID"
+
+# 1d8c4f1ed0514af0a756aec83a565956
+#: ../../hypervisor_installation.rst:2551
+msgid "vMotion enabled."
+msgstr "启用vMotion。"
+
+# 4d00a385859641e4917ec59ea57048fd
+#: ../../hypervisor_installation.rst:2555
+msgid "Management traffic enabled."
+msgstr "启用管理流量。"
+
+# 66d1840538c14c96b4d59ff3e61e856a
+#: ../../hypervisor_installation.rst:2557
+msgid ""
+"If the ESXi hosts have multiple VMKernel ports, and ESXi is not using the "
+"default value \"Management Network\" as the management network name, you "
+"must follow these guidelines to configure the management network port group "
+"so that CloudStack can find it:"
+msgstr "如果ESXi主机具有多个VMKernel端口，并且ESXi没有使用默认的“Management Network”作为管理网络名称，您必须按照以下指南配置管理网络端口组，以便CloudStack可以发现管理网络。"
+
+# fc2b617df8894bd39a8f053b76a2c07c
+#: ../../hypervisor_installation.rst:2564
+msgid "Use one label for the management network port across all ESXi hosts."
+msgstr "在所有ESXi主机上使用同一个管理网络端口组名称。"
+
+# fd1df578b83c4074ac776d883517aacb
+#: ../../hypervisor_installation.rst:2568
+msgid ""
+"In the CloudStack UI, go to Configuration - Global Settings and set "
+"vmware.management.portgroup to the management network label from the ESXi "
+"hosts."
+msgstr "在CloudStack管理界面中，点击配置-全局设置，修改vmware.management.portgroup为ESXi主机管理网络的标签。"
+
+# 81513937dabd42b49f17e4ed85786228
+#: ../../hypervisor_installation.rst:2573
+msgid "Extend Port Range for CloudStack Console Proxy"
+msgstr "为CloudStack控制台代理扩展端口范围"
+
+# 1a1fc60e2c5144a7ba1e80d0b9efb926
+#: ../../hypervisor_installation.rst:2575
+msgid "(Applies only to VMware vSphere version 4.x)"
+msgstr "（仅适用于VMware vSphere 4.x）"
+
+# 53fef3ce43cd4997b29df5bdb6832385
+#: ../../hypervisor_installation.rst:2577
+msgid ""
+"You need to extend the range of firewall ports that the console proxy works "
+"with on the hosts. This is to enable the console proxy to work with VMware-"
+"based VMs. The default additional port range is 59000-60000. To extend the "
+"port range, log in to the VMware ESX service console on each host and run "
+"the following commands:"
+msgstr "为使控制台代理可以和主机一起工作，您需要扩展主机的防火墙端口范围。这是为了使控制台代理可以访问VMware的VM。为扩展端口范围，请登录到每台主机的VMware ESX服务控制台，然后执行以下命令："
+
+# afe1b7c25f5f4cc3946340f3837f839d
+#: ../../hypervisor_installation.rst:2589
+msgid "Configure NIC Bonding for vSphere"
+msgstr "配置vSphere的网卡绑定"
+
+# 5c37fa38c442475bace70197c0dd9b82
+#: ../../hypervisor_installation.rst:2591
+msgid ""
+"NIC bonding on vSphere hosts may be done according to the vSphere "
+"installation guide."
+msgstr "vSphere主机的网卡绑定可以按照vSphere安装指南完成。"
+
+# 5d2db778b8a94adab782e09977ec5ecd
+#: ../../hypervisor_installation.rst:2595
+msgid "Configuring a vSphere Cluster with Nexus 1000v Virtual Switch"
+msgstr "配置vSphere群集使用Nexus 1000v虚拟交换机"
+
+# f36bc73d81314d9f8325fc0986b97ed1
+#: ../../hypervisor_installation.rst:2597
+msgid ""
+"CloudStack supports Cisco Nexus 1000v dvSwitch (Distributed Virtual Switch) "
+"for virtual network configuration in a VMware vSphere environment. This "
+"section helps you configure a vSphere cluster with Nexus 1000v virtual "
+"switch in a VMware vCenter environment. For information on creating a "
+"vSphere cluster, see `\"VMware vSphere Installation and Configuration\" "
+"<#vmware-vsphere-installation-and-configuration>`_"
+msgstr "CloudStack支持在VMware vSphere环境中使用Cisco Nexus 1000v dvSwitch (分布式虚拟交换机)。本章节能帮助你配置vSphere群集使用Nexus 1000v虚拟交换机。关于创建vSphere群集的更多信息，请参考 `\"VMware vSphere安装和配置\" <#vmware-vsphere-installation-and-configuration>`_"
+
+# 8cd1db7c783547a2a369cc85671b0ba0
+#: ../../hypervisor_installation.rst:2605
+msgid "About Cisco Nexus 1000v Distributed Virtual Switch"
+msgstr "关于Cisco Nexus 1000v分布式虚拟交换机"
+
+# 947f78705b1647ff8b04e6efaafcc588
+#: ../../hypervisor_installation.rst:2607
+msgid ""
+"The Cisco Nexus 1000V virtual switch is a software-based virtual machine "
+"access switch for VMware vSphere environments. It can span multiple hosts "
+"running VMware ESXi 4.0 and later. A Nexus virtual switch consists of two "
+"components: the Virtual Supervisor Module (VSM) and the Virtual Ethernet "
+"Module (VEM). The VSM is a virtual appliance that acts as the switch's "
+"supervisor. It controls multiple VEMs as a single network device. The VSM is"
+" installed independent of the VEM and is deployed in redundancy mode as "
+"pairs or as a standalone appliance. The VEM is installed on each VMware ESXi"
+" server to provide packet-forwarding capability. It provides each virtual "
+"machine with dedicated switch ports. This VSM-VEM architecture is analogous "
+"to a physical Cisco switch's supervisor (standalone or configured in high-"
+"availability mode) and multiple linecards architecture."
+msgstr "Cisco Nexus 1000V虚拟交换机是一个内置软件程序的虚拟机。它能跨越多个运行VMware ESXi 4.0或更高版本的主机部署。Nexus虚拟交换机包括两个组件：Virtual Supervisor Module (VSM)和 Virtual Ethernet Module (VEM)。VSM是一个管理交换机的虚拟设备。它单独控制多个VEM。VSM安装在每台VMware ESXi服务器当中提供包转发功能。它为每个虚拟机提供单独的交换机接口。VSM-VEM架构与物理交换机的管理机制（单独或者高可用模式）和多线卡架构类似。"
+
+# 16d69055a2814aa2b3f82537e3376cbf
+#: ../../hypervisor_installation.rst:2621
+msgid ""
+"Nexus 1000v switch uses vEthernet port profiles to simplify network "
+"provisioning for virtual machines. There are two types of port profiles: "
+"Ethernet port profile and vEthernet port profile. The Ethernet port profile "
+"is applied to the physical uplink ports-the NIC ports of the physical NIC "
+"adapter on an ESXi server. The vEthernet port profile is associated with the"
+" virtual NIC (vNIC) that is plumbed on a guest VM on the ESXi server. The "
+"port profiles help the network administrators define network policies which "
+"can be reused for new virtual machines. The Ethernet port profiles are "
+"created on the VSM and are represented as port groups on the vCenter server."
+msgstr "Nexus 1000v交换机使用vEthernet端口配置文件为虚拟机提供简单的网络。它有两种类型的端口配置文件：Ethernet端口配置文件和vEthernet端口配置文件。Ethernet端口配置文件应用到物理上联端口-ESXi服务器上面的物理网卡的端口。vEthernet端口配置文件关联到ESXi服务器上运行的虚拟机的虚拟网卡。端口配置文件可以帮助网络管理员快速的为其他虚机定义同样的网络策略。VSM创建的Ethernet端口策略在vCenter服务器上显示为端口组。"
+
+# 009d2fffa5a74d6e8aae5724bc65a70b
+# 91b00accca5d4628b0755e4faa99f297
+#: ../../hypervisor_installation.rst:2633
+#: ../../hypervisor_installation.rst:2973
+msgid "Prerequisites and Guidelines"
+msgstr "先决条件和指南"
+
+# ce47ce0ab3f14e90b733df2c0ccf976c
+#: ../../hypervisor_installation.rst:2635
+msgid ""
+"This section discusses prerequisites and guidelines for using Nexus virtual "
+"switch in CloudStack. Before configuring Nexus virtual switch, ensure that "
+"your system meets the following requirements:"
+msgstr "本章节探讨了在CloudStack中使用Nexus虚拟交换机的先决条件与指南。在配置Nexus虚拟交换机之前，请确保你的系统符合下列条件："
+
+# 388fab6909d346c29c55cf3802467fdd
+#: ../../hypervisor_installation.rst:2641
+msgid "A cluster of servers (ESXi 4.1 or later) is configured in the vCenter."
+msgstr "在vCenter中配置ESXi（ESXi 4.1或更高）群集。"
+
+# bb51ba76272e459b82769c8b10669f33
+#: ../../hypervisor_installation.rst:2646
+msgid ""
+"Each cluster managed by CloudStack is the only cluster in its vCenter "
+"datacenter."
+msgstr "CloudStack只能管理存在当前vCenter数据中心管理之下的每一个群集。"
+
+# ceb54b37abe64691b732b2f56ab9ab63
+#: ../../hypervisor_installation.rst:2651
+msgid ""
+"A Cisco Nexus 1000v virtual switch is installed to serve the datacenter that"
+" contains the vCenter cluster. This ensures that CloudStack doesn't have to "
+"deal with dynamic migration of virtual adapters or networks across other "
+"existing virtual switches. See `Cisco Nexus 1000V Installation and Upgrade "
+"Guide "
+"<http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_5_1/install_upgrade/vsm_vem/guide/n1000v_installupgrade.html>`_"
+" for guidelines on how to install the Nexus 1000v VSM and VEM modules."
+msgstr "Cisco Nexus 1000v虚拟交换机安装在vCenter数据中心所包含的群集主机。这将确保CloudStack不必处理跨现存虚拟交换机之间的虚拟网卡或网络的动态迁移。如何安装Nexus 1000v VSM和VEM 模块，请参考 `Cisco Nexus 1000V Installation and Upgrade Guide <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_5_1/install_upgrade/vsm_vem/guide/n1000v_installupgrade.html>`_。"
+
+# c4b648c345f24f0d93caa617a1e02bf2
+#: ../../hypervisor_installation.rst:2661
+msgid ""
+"The Nexus 1000v VSM is not deployed on a vSphere host that is managed by "
+"CloudStack."
+msgstr "Nexus 1000v VSM不能部署在由CloudStack管理的vSphere主机上。"
+
+# 9af74a7957b14acf9dea9343a65d4943
+#: ../../hypervisor_installation.rst:2666
+msgid ""
+"When the maximum number of VEM modules per VSM instance is reached, an "
+"additional VSM instance is created before introducing any more ESXi hosts. "
+"The limit is 64 VEM modules for each VSM instance."
+msgstr "当每个VSM实例的VEM模块达到最大数量时，需要在添加额外的VSM实例之前引入更多的ESXi主机。每个VSM实例的VEM模块数量限制为64个。"
+
+# 39bd095c73454da08cce69cebec4758c
+#: ../../hypervisor_installation.rst:2672
+msgid ""
+"CloudStack expects that the Management Network of the ESXi host is "
+"configured on the standard vSwitch and searches for it in the standard "
+"vSwitch. Therefore, ensure that you do not migrate the management network to"
+" Nexus 1000v virtual switch during configuration."
+msgstr "CloudStack期望ESXi主机的管理网络被配置在标准的vSwitch之上并且在标准的vSwitch中搜索该网络。因此，确保在配置期间不要把管理网络迁移到Nexus 1000v上。"
+
+# caeae4aefa224fe2946967d990a1f653
+#: ../../hypervisor_installation.rst:2680
+msgid "All information given in :ref:`nexus-vswift-preconf`"
+msgstr "所有信息在ref:`nexus-vswift-preconf`中："
+
+# 079c03e1a1c44b2585e0589bc13ec419
+#: ../../hypervisor_installation.rst:2685
+msgid "Nexus 1000v Virtual Switch Preconfiguration"
+msgstr "Nexus 1000v虚拟交换机预配置"
+
+# 441a8321399140988319b96b0ed4a8d3
+# e1e5b967f4b4437dbb584f3d5bb2d0d2
+#: ../../hypervisor_installation.rst:2688
+#: ../../hypervisor_installation.rst:3004
+msgid "Preparation Checklist"
+msgstr "准备工作清单"
+
+# a96df263b385459a91eba41537978fec
+#: ../../hypervisor_installation.rst:2690
+msgid ""
+"For a smoother configuration of Nexus 1000v switch, gather the following "
+"information before you start:"
+msgstr "要顺利配置 Nexus 1000v交换机，请在开始之前收集下列信息："
+
+# 031db7ac24b54428a167d5b7a115d517
+#: ../../hypervisor_installation.rst:2695
+msgid "vCenter credentials"
+msgstr "vCenter凭证"
+
+# fe90f49382904b8aa51038d5a04a39b7
+#: ../../hypervisor_installation.rst:2699
+msgid "Nexus 1000v VSM IP address"
+msgstr "Nexus 1000v VSM IP地址"
+
+# fe0fcf8dfab84007a11117c9ecd6935d
+#: ../../hypervisor_installation.rst:2703
+msgid "Nexus 1000v VSM Credentials"
+msgstr "Nexus 1000v VSM 凭证"
+
+# 8cc68bc6d66a435ca7b8ad006683ddb8
+#: ../../hypervisor_installation.rst:2707
+msgid "Ethernet port profile names"
+msgstr "以太网端口配置文件名称"
+
+# 1f929872354448a28565fcce6d00abc7
+#: ../../hypervisor_installation.rst:2710
+msgid "vCenter Credentials Checklist"
+msgstr "vCenter凭证清单"
+
+# 8bb7ea505c874ab7b4c1866085d8e700
+#: ../../hypervisor_installation.rst:2712
+msgid "You will need the following information about vCenter:"
+msgstr "需要vCenter以下信息："
+
+# f9ed8bcf6a9f4377b0199b7c80d0bcb5
+#: ../../hypervisor_installation.rst:2715
+msgid "Nexus vSwitch Requirements"
+msgstr "Nexus vSwitch要求"
+
+# c7823fb897be48eea6800becf44337e5
+#: ../../hypervisor_installation.rst:2717
+msgid "vCenter IP"
+msgstr "vCenter IP"
+
+# e823090f879940bea3b4b84e7e3ee726
+#: ../../hypervisor_installation.rst:2717
+msgid "The IP address of the vCenter."
+msgstr "vCenter IP地址"
+
+# f0ef18ebb58145568d1a700d6e00b9ef
+#: ../../hypervisor_installation.rst:2718
+msgid "Secure HTTP Port Number"
+msgstr "HTTPS端口号"
+
+# c50252838678465788afb4692dec2d53
+#: ../../hypervisor_installation.rst:2718
+msgid "443"
+msgstr "443"
+
+# 7a4f9f24e38c433697be3155d918783c
+#: ../../hypervisor_installation.rst:2718
+msgid ""
+"Port 443 is configured by default; however, you can change the port if "
+"needed."
+msgstr "默认配置使用443端口；如果需要，可以更改为其他端口。"
+
+# f9b688a1b9244b69a767dc296906d23d
+#: ../../hypervisor_installation.rst:2719
+msgid "vCenter User ID"
+msgstr "vCenter用户ID"
+
+# 5e8d79b6521145388c4acb0517d5b88b
+#: ../../hypervisor_installation.rst:2719
+msgid ""
+"The vCenter user with administrator-level privileges. The vCenter User ID is"
+" required when you configure the virtual switch in CloudStack."
+msgstr "拥有管理员权限的vCenter用户。在CloudStack中配置虚拟交换时需要提供vCenter用户ID。"
+
+# b881179cb7264cc7abb9f35738264468
+# 6a7716e4718d42a8aa250d486b60691f
+# cbc788e4d5b24d609a80d80085a406e1
+#: ../../hypervisor_installation.rst:2721
+#: ../../hypervisor_installation.rst:2905
+#: ../../hypervisor_installation.rst:3145
+msgid "vCenter Password"
+msgstr "vCenter 密码"
+
+# 77b0f1f8ba5c480688d7a4645318e29d
+#: ../../hypervisor_installation.rst:2721
+msgid ""
+"The password for the vCenter user specified above. The password for this "
+"vCenter user is required when you configure the switch in CloudStack."
+msgstr "上述vCenter用户的密码。在CloudStack中配置虚拟交换机时需要提供vCenter用户密码。"
+
+# 8adc4bbec2994f9daf8ad28a283f8f22
+#: ../../hypervisor_installation.rst:2727
+msgid "Network Configuration Checklist"
+msgstr "网络配置清单"
+
+# 723fe067d062435dae8004f1fb6111f0
+#: ../../hypervisor_installation.rst:2729
+msgid ""
+"The following information specified in the Nexus Configure Networking screen"
+" is displayed in the Details tab of the Nexus dvSwitch in the CloudStack UI:"
+msgstr "打开CloudStack管理界面，请在Nexus dvSwitchde 详情标签页中的Nexus 配置网络界面指定下列信息："
+
+# 98f99df6ba884d35a1903c0020ff3cf4
+#: ../../hypervisor_installation.rst:2734
+msgid "**Control Port Group VLAN ID**"
+msgstr "**控制端口组VALN ID**"
+
+# 18759fe2370349c88c9b9eca286d6597
+#: ../../hypervisor_installation.rst:2734
+msgid ""
+"The VLAN ID of the Control Port Group. The control VLAN is used for "
+"communication between the VSM and the VEMs."
+msgstr "控制端口组的VLAN ID。控制VLAN用于VSM与VEM之间通讯。"
+
+# c573b97a9ef44290a7ed29c338f0b166
+#: ../../hypervisor_installation.rst:2737
+msgid "**Management Port Group VLAN ID**"
+msgstr "**管理端口组VLAN ID**"
+
+# 89706bc807174ca68e67f578f1665a75
+#: ../../hypervisor_installation.rst:2737
+msgid ""
+"The VLAN ID of the Management Port Group. The management VLAN corresponds to"
+" the mgmt0 interface that is used to establish and maintain the connection "
+"between the VSM and VMware vCenter Server."
+msgstr "管理端口组的VLAN ID。对应管理VLAN接口mgmt0，用于设置和维护VSM与VMware vCenter服务器之间的连接。"
+
+# 05d78f3b91a54226ae7d80ad9b32e5f2
+#: ../../hypervisor_installation.rst:2740
+msgid "**Packet Port Group VLAN ID**"
+msgstr "**数据端口组VLAN ID**"
+
+# efdbd0ef1fcc42379e1eeecc7403ee3c
+#: ../../hypervisor_installation.rst:2740
+msgid ""
+"The VLAN ID of the Packet Port Group. The packet VLAN forwards relevant data"
+" packets from the VEMs to the VSM."
+msgstr "数据端口组的 VLAN ID。数据VLAN转发从VEM到VSM相关的数据包。"
+
+# 15475826735146f0abd95387015ba490
+#: ../../hypervisor_installation.rst:2742
+msgid ""
+"The VLANs used for control, packet, and management port groups can be the "
+"same."
+msgstr "用于控制，数据和管理端口组可以在同一VLAN。"
+
+# e340a47da8624b4b883780b3d2a5a9d9
+#: ../../hypervisor_installation.rst:2744
+msgid ""
+"For more information, see `Cisco Nexus 1000V Getting Started Guide "
+"<http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_b/getting_started/configuration/guide/n1000v_gsg.pdf>`_."
+msgstr "更多信息，请参考 `Cisco Nexus 1000V 入门指南 <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_b/getting_started/configuration/guide/n1000v_gsg.pdf>`_."
+
+# da3e2e028d7c450a901bf4831cc1d365
+#: ../../hypervisor_installation.rst:2747
+msgid "VSM Configuration Checklist"
+msgstr "VSM配置清单"
+
+# 587a4baf238946f48ee6e7bd04fd1b07
+#: ../../hypervisor_installation.rst:2749
+msgid "You will need the following VSM configuration parameters:"
+msgstr "你需要下列的VSM配置参数："
+
+# 5256914261474454b2f9537dd4f2be04
+#: ../../hypervisor_installation.rst:2751
+msgid "**Admin Name and Password**"
+msgstr "**管理员用户名和密码**"
+
+# 4fc4d247bb37403eb2789f39d793866b
+#: ../../hypervisor_installation.rst:2752
+msgid ""
+"The admin name and password to connect to the VSM appliance. You must "
+"specify these credentials while configuring Nexus virtual switch."
+msgstr "管理员用户名和密码用于连接VSM appliance。当配置Nexus虚拟交换机时，必须指定这些凭证。"
+
+# 5e96418f205547fb8d770ccb7168d497
+#: ../../hypervisor_installation.rst:2753
+msgid "**Management IP Address**"
+msgstr "**管理 IP**"
+
+# 7febd6557b3742e9a3d478672eba6cad
+#: ../../hypervisor_installation.rst:2754
+msgid ""
+"This is the IP address of the VSM appliance. This is the IP address you "
+"specify in the virtual switch IP Address field while configuting Nexus "
+"virtual switch."
+msgstr "VSM appliance的IP地址。 当配置Nexus虚拟交换机时在虚拟交换机的IP地址区域输入的IP地址。"
+
+# 2cd219755aca4177a241670f4b4b7872
+#: ../../hypervisor_installation.rst:2758
+msgid "**SSL**"
+msgstr "**SSL**"
+
+# cab1502c5d5d4221873f13e86168b3d3
+#: ../../hypervisor_installation.rst:2756
+msgid ""
+"Should be set to Enable.Always enable SSL. SSH is usually enabled by default"
+" during the VSM installation. However, check whether the SSH connection to "
+"the VSM is working, without which CloudStack failes to connect to the VSM."
+msgstr "应该设置为启用。总是启用SSL。在VSM安装期间通常会启用SSH功能。尽管如此仍需检查是否能够使用SSH连接到VSM，如果不能无法连接，CloudStack到VSM的连接会失败。"
+
+# 747a5560bbed48598ec8fb9ad2739dde
+#: ../../hypervisor_installation.rst:2761
+msgid "Creating a Port Profile"
+msgstr "创建端口配置文件"
+
+# 915567df98f3440f9c869a266292bebf
+#: ../../hypervisor_installation.rst:2765
+msgid ""
+"Whether you create a Basic or Advanced zone configuration, ensure that you "
+"always create an Ethernet port profile on the VSM after you install it and "
+"before you create the zone."
+msgstr "无论创建简单或者高级区域，确保你总是在安装完VSM之后，创建区域之前，创建一个VSM的Ethernet配置文件。"
+
+# f27be294146746dd92354b86a70b9a34
+#: ../../hypervisor_installation.rst:2771
+msgid ""
+"The Ethernet port profile created to represent the physical network or "
+"networks used by an Advanced zone configuration trunk all the VLANs "
+"including guest VLANs, the VLANs that serve the native VLAN, and the "
+"packet/control/data/management VLANs of the VSM."
+msgstr "创建Ethernet端口配置文件用于表示物理网络或高级区域配置中trunk所有的VLANs网络，VLANs包括来宾网VLANs，本征VLAN以及VSM的数据/控制/管理VLANs。"
+
+# 14dcf98b714a4de493d3bd65c53e07b5
+#: ../../hypervisor_installation.rst:2779
+msgid ""
+"The Ethernet port profile created for a Basic zone configuration does not "
+"trunk the guest VLANs because the guest VMs do not get their own VLANs "
+"provisioned on their network interfaces in a Basic zone."
+msgstr "为基础区域配置的Ethernet端口配置文件不会trunk来宾VLANs，因为在基础区域中，来宾VMs无法通过它们的网络接口获得所属的VLANs。"
+
+# acc04f3bc9a547b0919324a8ed1430d4
+#: ../../hypervisor_installation.rst:2786
+msgid ""
+"An Ethernet port profile configured on the Nexus 1000v virtual switch should"
+" not use in its set of system VLANs, or any of the VLANs configured or "
+"intended to be configured for use towards VMs or VM resources in the "
+"CloudStack environment."
+msgstr "在Nexus 1000v虚拟交换机上配置的以太网端口配置文件，不应该使用在它的VLANS系统设置中，或者使用在其他任何VLANS配置以及打算使用在CloudStack环境中的虚拟机或者虚拟机资源的配置。"
+
+# ddaca8ac1441456ebd7e21dcc838b22c
+#: ../../hypervisor_installation.rst:2793
+msgid ""
+"You do not have to create any vEthernet port profiles – CloudStack does that"
+" during VM deployment."
+msgstr "你无须创建任何vEthernet端口配置文件-CloudStack会在VM部署期间创建。"
+
+# 380f259b08904003bff09f8cbc797634
+#: ../../hypervisor_installation.rst:2798
+msgid ""
+"Ensure that you create required port profiles to be used by CloudStack for "
+"different traffic types of CloudStack, such as Management traffic, Guest "
+"traffic, Storage traffic, and Public traffic. The physical networks "
+"configured during zone creation should have a one-to-one relation with the "
+"Ethernet port profiles."
+msgstr "请确保你为每种CloudStack流量类型创建了所需的端口配置文件，如管理流量，来宾流量，存储流量和公共流量。在区域创建期间配置的物理网络跟Ethernet应该是一一对应的关系。"
+
+# a082dd98813f48b293e64d2a86f4c8a9
+#: ../../hypervisor_installation.rst:2804
+msgid "|vmwarenexusportprofile.png: vSphere client|"
+msgstr "|vmwarenexusportprofile.png: vSphere client|"
+
+# f47a376ee3134e19a877759d2cddeec3
+#: ../../hypervisor_installation.rst:2806
+msgid ""
+"For information on creating a port profile, see `Cisco Nexus 1000V Port "
+"Profile Configuration Guide "
+"<http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_a/port_profile/configuration/guide/n1000v_port_profile.html>`_."
+msgstr "关于创建端口配置文件的更多信息，请参考 `Cisco Nexus 1000V 端口配置指南 <http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4_a/port_profile/configuration/guide/n1000v_port_profile.html>`_。"
+
+# 7150678d8ad84958ad15325b7e295635
+#: ../../hypervisor_installation.rst:2811
+msgid "Assigning Physical NIC Adapters"
+msgstr "分配物理网络适配器"
+
+# 0fcc662360f24246aa89af9504290713
+#: ../../hypervisor_installation.rst:2813
+msgid ""
+"Assign ESXi host's physical NIC adapters, which correspond to each physical "
+"network, to the port profiles. In each ESXi host that is part of the vCenter"
+" cluster, observe the physical networks assigned to each port profile and "
+"note down the names of the port profile for future use. This mapping "
+"information helps you when configuring physical networks during the zone "
+"configuration on CloudStack. These Ethernet port profile names are later "
+"specified as VMware Traffic Labels for different traffic types when "
+"configuring physical networks during the zone configuration. For more "
+"information on configuring physical networks, see `\"Configuring a vSphere "
+"Cluster with Nexus 1000v Virtual Switch\" <#configuring-a-vsphere-cluster-"
+"with-nexus-1000v-virtual-switch>`_."
+msgstr "分配ESXi主机上的对应每个物理网络的网卡适配器到端口配置文件。在vCenter群集中的每个ESXi主机上，观察分配到每个端口配置文件的物理网络并记下配置文件的名字。在创建zone期间，当你配置物理网络的时候，这个映射信息能帮助你。这些Ethernet端口配置文件的名字就是随后你在配置zone的时候，配置物理网络时所要输入的不同流量对应的VMware流量标签。配置物理网络所需的更多信息，请参考 `\"Configuring a vSphere Cluster with Nexus 1000v Virtual Switch\" <#configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch>`_。"
+
+# bfdb4a3f2d1d498e8ea20b009ae3b41f
+#: ../../hypervisor_installation.rst:2825
+msgid "Adding VLAN Ranges"
+msgstr "添加VLAN范围"
+
+# ab086d39a6454950a4c821d832b8d0a6
+#: ../../hypervisor_installation.rst:2827
+msgid ""
+"Determine the public VLAN, System VLAN, and Guest VLANs to be used by the "
+"CloudStack. Ensure that you add them to the port profile database. "
+"Corresponding to each physical network, add the VLAN range to port profiles."
+" In the VSM command prompt, run the switchport trunk allowed vlan<range> "
+"command to add the VLAN ranges to the port profile."
+msgstr "决定CloudStack所使用的公共VLAN，系统VLAN和来宾VLAN。确保你添加他们到端口配置文件数据库。对应每个物理网络，为端口配置文件添加VLAN范围。在VSM命令提示符下，运行 switchport trunk allowed vlan<range>命令为端口配置文件添加VLAN范围。"
+
+# 829a113f6355423c978bf7cca25f0a01
+# f2317ad7ae7148679ecc16cb7353da3b
+#: ../../hypervisor_installation.rst:2833
+#: ../../hypervisor_installation.rst:2846
+msgid "For example:"
+msgstr "例如："
+
+# 04401fdeab2f4ee4a97429af971bbd04
+#: ../../hypervisor_installation.rst:2839
+msgid "In this example, the allowed VLANs added are 1, 140-147, and 196-203"
+msgstr "在这个示例下，添加的VLANs是1,140-147和196-203"
+
+# c9d7e8243d494833b060ec436ef511f7
+#: ../../hypervisor_installation.rst:2841
+msgid ""
+"You must also add all the public and private VLANs or VLAN ranges to the "
+"switch. This range is the VLAN range you specify in your zone."
+msgstr "你同样在该交换机中添加所有的公共和管理VLANs或VLAN范围。这个范围是你在区域中指定的VLAN范围。"
+
+# 963d8b9051d24f069022dea1d22daf9e
+#: ../../hypervisor_installation.rst:2844
+msgid ""
+"Before you run the vlan command, ensure that the configuration mode is "
+"enabled in Nexus 1000v virtual switch."
+msgstr "在你运行vlan命令之前，确保Nexus 1000v虚拟交换机中启用了配置模式。"
+
+# 51f537d407aa4bfa944be0d00b48f772
+#: ../../hypervisor_installation.rst:2848
+msgid ""
+"If you want the VLAN 200 to be used on the switch, run the following "
+"command:"
+msgstr "如果你想在交换机中使用VLAN 200，运行下面的命令："
+
+# cac6cabf1e994fea9fcc690bb4cb85d8
+#: ../../hypervisor_installation.rst:2855
+msgid ""
+"If you want the VLAN range 1350-1750 to be used on the switch, run the "
+"following command:"
+msgstr "如果你想在交换机中使用VLAN范围1350-1750，请运行下面的命令："
+
+# 2c87fe767ced4157a5a91a878982cd3b
+#: ../../hypervisor_installation.rst:2862
+msgid ""
+"Refer to Cisco Nexus 1000V Command Reference of specific product version."
+msgstr "参考特定产品版本的Cisco Nexus 1000V 命令参考。"
+
+# e20558d2c83e4921a2ae5a4942fbf6a4
+#: ../../hypervisor_installation.rst:2866
+msgid "Enabling Nexus Virtual Switch in CloudStack"
+msgstr "在CloudStack中启用Nexus虚拟交换机。"
+
+# 2f23da65b54842d7a760a7cb75dc5384
+#: ../../hypervisor_installation.rst:2868
+msgid ""
+"To make a CloudStack deployment Nexus enabled, you must set the "
+"vmware.use.nexus.vswitch parameter true by using the Global Settings page in"
+" the CloudStack UI. Unless this parameter is set to \"true\" and restart the"
+" management server, you cannot see any UI options specific to Nexus virtual "
+"switch, and CloudStack ignores the Nexus virtual switch specific parameters "
+"specified in the AddTrafficTypeCmd, UpdateTrafficTypeCmd, and AddClusterCmd "
+"API calls."
+msgstr "为了使CloudStack启用部署Nexus，你必须在CloudStack UI中全局设置页面设置vmware.use.nexus.vswitch参数为true。只有这个参数设置为 \"true\"并且重启了管理服务器，你才可以看见Nexus虚拟交换机的相关页面，CloudStack在AddTrafficTypeCmd, UpdateTrafficTypeCmd和 AddClusterCmd API的调用中会忽略Nexus虚拟交换机的指定参数。"
+
+# 2a1bbcac40824582944f6987b96e18bd
+#: ../../hypervisor_installation.rst:2876
+msgid ""
+"Unless the CloudStack global parameter \"vmware.use.nexus.vswitch\" is set "
+"to \"true\", CloudStack by default uses VMware standard vSwitch for virtual "
+"network infrastructure. In this release, CloudStack doesn’t support "
+"configuring virtual networks in a deployment with a mix of standard vSwitch "
+"and Nexus 1000v virtual switch. The deployment can have either standard "
+"vSwitch or Nexus 1000v virtual switch."
+msgstr "除非CloudStack全局配置中的\"vmware.use.nexus.vswitch\"设置为\"true\"，否则CloudStack会默认使用VMware标准vSwitch。在本版本中，CloudStack不支持在标准vSwitch和Nexus 1000v虚拟交换机的混合环境中配置虚拟网络。只能支持单一的标准vSwitch或Nexus 1000v虚拟交换机部署。"
+
+# b01aa0230c104b8dbc702f5106681b86
+#: ../../hypervisor_installation.rst:2884
+msgid "Configuring Nexus 1000v Virtual Switch in CloudStack"
+msgstr "在CloudStack中配置Nexus 1000v虚拟交换机"
+
+# 55b47a1924834ab9bcf05fc1d5f2830f
+#: ../../hypervisor_installation.rst:2886
+msgid ""
+"You can configure Nexus dvSwitch by adding the necessary resources while the"
+" zone is being created."
+msgstr "可以在创建区域时，通过添加必要的资源用于配置Nexus dvSwitch。"
+
+# ab30cc7f205a4b968f9d107cb9e536fc
+#: ../../hypervisor_installation.rst:2889
+msgid "|vmwarenexusaddcluster.png: vmware nexus add cluster|"
+msgstr "|vmwarenexusaddcluster.png: vmware nexus add cluster|"
+
+# 3a6d505f9c0e4e06ad20d61688e9d360
+#: ../../hypervisor_installation.rst:2891
+msgid ""
+"After the zone is created, if you want to create an additional cluster along"
+" with Nexus 1000v virtual switch in the existing zone, use the Add Cluster "
+"option. For information on creating a cluster, see `\"Add Cluster: vSphere\""
+" <configuration.html#add-cluster-vsphere>`_."
+msgstr "区域创建完成后，如果你想在区域中创建其他同样使用Nexus 1000v虚拟交换机的群集时，使用添加群集选项。关于创建群集的更多信息，请参见 `\"添加群集: vSphere\" <configuration.html#add-cluster-vsphere>`_。"
+
+# ea487fd695374472b3cc28afaf8b7935
+#: ../../hypervisor_installation.rst:2896
+msgid ""
+"In both these cases, you must specify the following parameters to configure "
+"Nexus virtual switch:"
+msgstr "在所有的情况下，配置Nexus虚拟交换机时必须指定下列参数："
+
+# 2f10aacae6b943778d44f84d722c4c40
+#: ../../hypervisor_installation.rst:2900
+msgid "Parameters"
+msgstr "参数"
+
+# 954a0fcef76244e59ff7157df2ce9236
+# 6c098c5af55c4ef2832ddb1ea22a7756
+#: ../../hypervisor_installation.rst:2902
+#: ../../hypervisor_installation.rst:3142
+msgid "Cluster Name"
+msgstr "群集名称"
+
+# cba6000d144e4dec8b5a6d503214b04e
+#: ../../hypervisor_installation.rst:2902
+msgid ""
+"Enter the name of the cluster you created in vCenter. For "
+"example,\"cloud.cluster\"."
+msgstr "输入在vCenter中创建的群集名称。比如，\"cloud.cluster\"。"
+
+# 5a2734feab1d4c3899f219dc7e0bc047
+# cb1115f5a4e6459f9d59941f73399499
+#: ../../hypervisor_installation.rst:2903
+#: ../../hypervisor_installation.rst:3143
+msgid "vCenter Host"
+msgstr "vCenter 主机"
+
+# a270577295e947aeb4f510cc1671250b
+#: ../../hypervisor_installation.rst:2903
+msgid ""
+"Enter the host name or the IP address of the vCenter host where you have "
+"deployed the Nexus virtual switch."
+msgstr "输入已经部署了Nexus虚拟交换机的vCenter主机名或IP。"
+
+# 43b78f2519cd43a592186b681bbd758a
+# aca846fafd164bbfafb28f1bc1d23abd
+#: ../../hypervisor_installation.rst:2904
+#: ../../hypervisor_installation.rst:3144
+msgid "vCenter User name"
+msgstr "vCenter用户名"
+
+# 7a017d72974241b181fa5e3cded99ba7
+# ff313f1172d84c6fb6ecc0ba3c6c01ca
+#: ../../hypervisor_installation.rst:2904
+#: ../../hypervisor_installation.rst:3144
+msgid ""
+"Enter the username that CloudStack should use to connect to vCenter. This "
+"user must have all administrative privileges."
+msgstr "输入CloudStack连接到vCenter所使用的用户名。这个用户必须拥有所有管理员权限。"
+
+# fb40ce7817f34578a3644c0af373813e
+# ba61f2c3473c412c95dbaa2f80ece441
+#: ../../hypervisor_installation.rst:2905
+#: ../../hypervisor_installation.rst:3145
+msgid "Enter the password for the user named above."
+msgstr "输入上面用户的密码。"
+
+# ab8a34c645a042d69e48fc3f7dc9bd46
+# e15b104af30843118d478ff6a77775a8
+#: ../../hypervisor_installation.rst:2906
+#: ../../hypervisor_installation.rst:3146
+msgid "vCenter Datacenter"
+msgstr "vCenter数据中心"
+
+# d5b61a5f9b5a4a35a74aee094bd31df8
+#: ../../hypervisor_installation.rst:2906
+msgid ""
+"Enter the vCenter datacenter that the cluster is in. For example, "
+"\"cloud.dc.VM\"."
+msgstr "输入群集所属的vCenter数据中心名称。比如， \"cloud.dc.VM\"。"
+
+# dafa148e3c364171aa16aebbd2a377d6
+#: ../../hypervisor_installation.rst:2907
+msgid "Nexus dvSwitch IP Address"
+msgstr "Nexus dvSwitch IP 地址"
+
+# 1f7fcac4b6f54bb9988b6c7b28d765ac
+#: ../../hypervisor_installation.rst:2907
+msgid "The IP address of the VSM component of the Nexus 1000v virtual switch."
+msgstr "Nexus 1000v虚拟交换机VSM组件的IP地址。"
+
+# 00db776b96ea48e0a3eb5546f466392d
+#: ../../hypervisor_installation.rst:2908
+msgid "Nexus dvSwitch Username"
+msgstr "Nexus dvSwitch 用户名"
+
+# 42df2254c26a49ed9a0b25aadf0ace64
+#: ../../hypervisor_installation.rst:2908
+msgid "The admin name to connect to the VSM appliance."
+msgstr "连接至VSM appliance的admin名称。"
+
+# ae881d805b02440bab9e62dcf0a807d8
+#: ../../hypervisor_installation.rst:2909
+msgid "Nexus dvSwitch Password"
+msgstr "Nexus dvSwitch 密码"
+
+# fd192f54264b48918f39207ffb2da278
+#: ../../hypervisor_installation.rst:2909
+msgid "The corresponding password for the admin user specified above."
+msgstr "上面指定的admin用户所对应的密码。"
+
+# a1357edc605446acb820b979fb132d55
+#: ../../hypervisor_installation.rst:2914
+msgid "Removing Nexus Virtual Switch"
+msgstr "移除Nexus虚拟交换机"
+
+# 09e2100542c640edbdf96af9d9029316
+#: ../../hypervisor_installation.rst:2918
+msgid ""
+"In the vCenter datacenter that is served by the Nexus virtual switch, ensure"
+" that you delete all the hosts in the corresponding cluster."
+msgstr "在使用了Nexus虚拟交换机的vCenter数据中心中，确认你在对应的群集中删除了所有的主机。"
+
+# 141ee7173de14b2da44ea1708fa069f9
+#: ../../hypervisor_installation.rst:2923
+msgid "Log in with Admin permissions to the CloudStack administrator UI."
+msgstr "使用管理员登录到CloudStack管理界面。"
+
+# 7eee8789554c4d4393308c741352fa3f
+#: ../../hypervisor_installation.rst:2927
+msgid "In the left navigation bar, select Infrastructure."
+msgstr "在左侧导航栏中，选择基础架构。"
+
+# 89db573e47724516be8db76bc1b1164d
+#: ../../hypervisor_installation.rst:2931
+msgid "In the Infrastructure page, click View all under Clusters."
+msgstr "在基础架构页面，点击群集中的查看所有。"
+
+# fb174283e4aa42b08b34858e58f6e083
+#: ../../hypervisor_installation.rst:2935
+msgid "Select the cluster where you want to remove the virtual switch."
+msgstr "选择你想要移除虚拟交换机的群集。"
+
+# 527fc95732794445bdd79834dcb5a64c
+#: ../../hypervisor_installation.rst:2939
+msgid "In the dvSwitch tab, click the name of the virtual switch."
+msgstr "在dvSwitch标签页中，点击虚拟交换机的名字。"
+
+# fecadbb783ed4a7fb44b7fefef7c8c51
+#: ../../hypervisor_installation.rst:2943
+msgid ""
+"In the Details page, click Delete Nexus dvSwitch icon. |DeleteButton.png: "
+"button to delete dvSwitch|"
+msgstr "在详细页面中，点击删除Nexus dvSwitch的图标。 |DeleteButton.png: button to delete dvSwitch|"
+
+# 3110096d69604bf2a4f702eb6e1756bb
+#: ../../hypervisor_installation.rst:2946
+msgid "Click Yes in the confirmation dialog box."
+msgstr "在确认对话框中点击确定。"
+
+# 48610fff03ad42cb851d18020b200ba2
+#: ../../hypervisor_installation.rst:2949
+msgid "Configuring a VMware Datacenter with VMware Distributed Virtual Switch"
+msgstr "配置VMware数据中心使用VMware分布式虚拟交换机"
+
+# b31d6d27a7d849239fde0b1173228bf4
+#: ../../hypervisor_installation.rst:2951
+msgid ""
+"CloudStack supports VMware vNetwork Distributed Switch (VDS) for virtual "
+"network configuration in a VMware vSphere environment. This section helps "
+"you configure VMware VDS in a CloudStack deployment. Each vCenter server "
+"instance can support up to 128 VDS instances and each VDS instance can "
+"manage up to 500 VMware hosts."
+msgstr "CloudStack支持在VMware vSphere环境中为虚拟网络配置VMware vNetwork分布式交换机（VDS）。本章节能帮助你在CloudStack中配置VMware VDS。每个vCenter服务器实例最多支持128 VDS实例，每个VDS实例最多可以管理500台VMware服务器。"
+
+# be70e6f87324407c9bf757efec52fa28
+#: ../../hypervisor_installation.rst:2958
+msgid "About VMware Distributed Virtual Switch"
+msgstr "关于VMware分布式虚拟交换机"
+
+# 9e77fcbc39f04ef98d83c991e2f6fe29
+#: ../../hypervisor_installation.rst:2960
+msgid ""
+"VMware VDS is an aggregation of host-level virtual switches on a VMware "
+"vCenter server. VDS abstracts the configuration of individual virtual "
+"switches that span across a large number of hosts, and enables centralized "
+"provisioning, administration, and monitoring for your entire datacenter from"
+" a centralized interface. In effect, a VDS acts as a single virtual switch "
+"at the datacenter level and manages networking for a number of hosts in a "
+"datacenter from a centralized VMware vCenter server. Each VDS maintains "
+"network runtime state for VMs as they move across multiple hosts, enabling "
+"inline monitoring and centralized firewall services. A VDS can be deployed "
+"with or without Virtual Standard Switch and a Nexus 1000V virtual switch."
+msgstr "在VMware vCenter服务器中的VMware VDS聚合主机层面虚拟交换机 。各个主机层面的虚拟交换机被抽象处理成一个在数据中心层面上横跨多个主机的大型 VDS，通过一个集中的接口，使用集中配置、管理、监控你的整个数据中心。实际上，VDS可以看作是数据中心层面中一个整体的虚拟交换机，通过VMware vCenter服务器管理数据中心中大量的主机网络。在虚拟机跨多个主机移动时保持其网络运行时状态，支持嵌入式监控和集中式防火墙服务。VDS能与标准虚拟交换机和 Nexus 1000V虚拟交换机一起部署或者独立部署。"
+
+# 365a2690501340d78bc366fad0eaac7f
+#: ../../hypervisor_installation.rst:2977
+msgid ""
+"VMware VDS is supported only on Public and Guest traffic in CloudStack."
+msgstr "VMware VDS只支持CloudStack中的公共和来宾流量。"
+
+# db4195c57675402cbf5f2b8cfbf5a452
+#: ../../hypervisor_installation.rst:2982
+msgid ""
+"VMware VDS does not support multiple VDS per traffic type. If a user has "
+"many VDS switches, only one can be used for Guest traffic and another one "
+"for Public traffic."
+msgstr "VMware VDS不支持每种流量类型使用多个VDS。如果一个用户有多个VDS交换机，那么来宾网络和公共网络只能各使用一个VDS。"
+
+# 7ddee82f457e4e40972b79a0f45b6dfc
+#: ../../hypervisor_installation.rst:2988
+msgid ""
+"Additional switches of any type can be added for each cluster in the same "
+"zone. While adding the clusters with different switch type, traffic labels "
+"is overridden at the cluster level."
+msgstr "在同一个zone中可以为每个群集添加任何类型的交换机。当在群集中添加不同类型的交换机时，流量标签会被群集级别的覆盖。"
+
+# d5aec4e86dcd42178120945c7ffb2ffb
+#: ../../hypervisor_installation.rst:2994
+msgid ""
+"Management and Storage network does not support VDS. Therefore, use Standard"
+" Switch for these networks."
+msgstr "管理和存储网络不支持使用VDS。因此在这些网络中使用标准交换机。"
+
+# e246769436bd49aeb25ed0a009f987a1
+#: ../../hypervisor_installation.rst:2999
+msgid ""
+"When you remove a guest network, the corresponding dvportgroup will not be "
+"removed on the vCenter. You must manually delete them on the vCenter."
+msgstr "当你移除来宾网络时，对应vCenter中的dv端口组不会被移除。你必须手动在vCenter中删除。"
+
+# 54eddf463262482a8c3dad6f5f2ae247
+#: ../../hypervisor_installation.rst:3006
+msgid ""
+"For a smoother configuration of VMware VDS, note down the VDS name you have "
+"added in the datacenter before you start:"
+msgstr "为了顺利的配置VMware VDS，在开始之前，请牢记添加到数据中心中的VDS名称："
+
+# 9cc248efd6174d1f95fcb79364dfe324
+#: ../../hypervisor_installation.rst:3009
+msgid "|vds-name.png: Name of the dvSwitch as specified in the vCenter.|"
+msgstr "|vds-name.png: Name of the dvSwitch as specified in the vCenter.|"
+
+# e7d07e6efc854a6f91160737fc2dc730
+#: ../../hypervisor_installation.rst:3011
+msgid "Use this VDS name in the following:"
+msgstr "如下需要使用VDS名称："
+
+# 3b63424161524f9da4420d0fd98dcda4
+#: ../../hypervisor_installation.rst:3015
+msgid ""
+"The switch name in the Edit traffic label dialog while configuring a public "
+"and guest traffic during zone creation."
+msgstr "在创建zone的过程中配置公共网络和来宾网络时，在编辑流量标签对话框中配置交换机名称。"
+
+# cc1e2b04ea1b412a9180f77ac2930ad1
+#: ../../hypervisor_installation.rst:3018
+msgid ""
+"During a zone creation, ensure that you select VMware vNetwork Distributed "
+"Virtual Switch when you configure guest and public traffic type."
+msgstr "在创建zone的过程中配置来宾网络和公共网络流量类型时，请确保你选择了VMware vNetwork Distributed Virtual Switch。"
+
+# 28c7098972e44723819b9108289414b9
+#: ../../hypervisor_installation.rst:3022
+msgid "|traffic-type.png|"
+msgstr "|traffic-type.png|"
+
+# 0d77c0b1eab14dca879d121804431960
+#: ../../hypervisor_installation.rst:3026
+msgid ""
+"The Public Traffic vSwitch Type field when you add a VMware VDS-enabled "
+"cluster."
+msgstr "当添加一个启用了VDS的VMware群集时，则显示公共网络流量vSwitch类型区域。"
+
+# 929135e8bf4d4f4a97a4db420a38dfd9
+#: ../../hypervisor_installation.rst:3031
+msgid ""
+"The switch name in the traffic label while updating the switch type in a "
+"zone."
+msgstr "当在zone中更新交换机类型时，流量标签所使用的交换机名称。"
+
+# 366e9be0e6a0468d952b3f9f3f3306b0
+#: ../../hypervisor_installation.rst:3034
+msgid ""
+"Traffic label format in the last case is [[\"Name of "
+"vSwitch/dvSwitch/EthernetPortProfile\"][,\"VLAN ID\"[,\"vSwitch Type\"]]]"
+msgstr "在最后一种情况下流量标签格式是[[\"Name of vSwitch/dvSwitch/EthernetPortProfile\"][,\"VLAN ID\"[,\"vSwitch Type\"]]]"
+
+# eaba03f24031461693648bd7a76b3ec6
+#: ../../hypervisor_installation.rst:3036
+msgid "The possible values for traffic labels are:"
+msgstr "流量标签可以使用如下值："
+
+# 61df80b370aa491484457725b12a1694
+#: ../../hypervisor_installation.rst:3040
+msgid "empty string"
+msgstr "空字符串"
+
+# d6793cc7e2eb4556a8cce089bb5fb7ba
+#: ../../hypervisor_installation.rst:3044
+msgid "dvSwitch0"
+msgstr "dvSwitch0"
+
+# b3f4e9ec50d242d0981bd4164476a989
+#: ../../hypervisor_installation.rst:3048
+msgid "dvSwitch0,200"
+msgstr "dvSwitch0,200"
+
+# d1044d22ffaa4efbb6917233f25d33e7
+#: ../../hypervisor_installation.rst:3052
+msgid "dvSwitch1,300,vmwaredvs"
+msgstr "dvSwitch1,300,vmwaredvs"
+
+# fe1f3e03cabb4594be05f4694247828e
+#: ../../hypervisor_installation.rst:3056
+msgid "myEthernetPortProfile,,nexusdvs"
+msgstr "myEthernetPortProfile,,nexusdvs"
+
+# b0f992c1c506410f99034c1590b1b36d
+#: ../../hypervisor_installation.rst:3060
+msgid "dvSwitch0,,vmwaredvs"
+msgstr "dvSwitch0,,vmwaredvs"
+
+# 0643bee72bf9427097e841fa867a1b1d
+#: ../../hypervisor_installation.rst:3063
+msgid "The three fields to fill in are:"
+msgstr "填写如下区域："
+
+# 4e1d4397308e4b2784978fa2b399204e
+#: ../../hypervisor_installation.rst:3067
+msgid "Name of the virtual / distributed virtual switch at vCenter."
+msgstr "vCenter中 虚拟/分布式 虚拟交换机的名称。"
+
+# 0ea48308f4034803ace1fbce08fa1fd4
+#: ../../hypervisor_installation.rst:3069
+msgid "The default value depends on the type of virtual switch:"
+msgstr "默认值取决于虚拟交换机的类型："
+
+# 06091102df12426db15a2fa2294255cc
+#: ../../hypervisor_installation.rst:3071
+msgid ""
+"**vSwitch0**: If type of virtual switch is VMware vNetwork Standard virtual "
+"switch"
+msgstr "**vSwitch0**：如果虚拟交换机的类型是VMware vNetwork标准虚拟交换机。"
+
+# 2342c2b4f9554a848bfd6e018bda4ca8
+#: ../../hypervisor_installation.rst:3073
+msgid ""
+"**dvSwitch0**: If type of virtual switch is VMware vNetwork Distributed "
+"virtual switch"
+msgstr "**dvSwitch0**：如果虚拟交换机类型为VMware vNetwork分布式虚拟交换机"
+
+# fc80358ec4c344b19e3b1396a4fe3f2b
+#: ../../hypervisor_installation.rst:3075
+msgid ""
+"**epp0**: If type of virtual switch is Cisco Nexus 1000v Distributed virtual"
+" switch"
+msgstr "**epp0**：如果虚拟交换机类型为Cisco Nexus 1000v分布式虚拟交换机"
+
+# f9653fff8e2a4dfe9f57984ea973effd
+#: ../../hypervisor_installation.rst:3079
+msgid "VLAN ID to be used for this traffic wherever applicable."
+msgstr "任何适用于这个流量的 VLAN ID"
+
+# 1f6e646a6ba742bebf304d510d52ec4b
+#: ../../hypervisor_installation.rst:3081
+msgid ""
+"This field would be used for only public traffic as of now. In case of guest"
+" traffic this field would be ignored and could be left empty for guest "
+"traffic. By default empty string would be assumed which translates to "
+"untagged VLAN for that specific traffic type."
+msgstr "此时，该区域仅用于公共网络流量。来宾网络区域会被忽略并且留空。默认为空字符即假设特定流量类型不填加VLAN标签。"
+
+# 5b4d56e3828a431fb972d1a30cbb5993
+#: ../../hypervisor_installation.rst:3085
+msgid "Type of virtual switch. Specified as string."
+msgstr "虚拟交换机类型。指定字符串。"
+
+# 34474cbb49e5499fb1e02724466f1dd4
+#: ../../hypervisor_installation.rst:3087
+msgid "Possible valid values are vmwaredvs, vmwaresvs, nexusdvs."
+msgstr "合理且有效的值为vmwaredvs, vmwaresvs, nexusdvs。"
+
+# 8178f6130ecb48baaea165ae9e8b0846
+#: ../../hypervisor_installation.rst:3089
+msgid "**vmwaresvs**: Represents VMware vNetwork Standard virtual switch"
+msgstr "**vmwaresvs**：表示VMware vNetwork 标准虚拟交换机"
+
+# a651a8e73a224d75a56b6c95f2997e8f
+#: ../../hypervisor_installation.rst:3091
+msgid "**vmwaredvs**: Represents VMware vNetwork distributed virtual switch"
+msgstr "**vmwaredvs**：表示VMware vNetwork分布式虚拟交换机"
+
+# 6b485445cf314856bf788804ac1279f0
+#: ../../hypervisor_installation.rst:3093
+msgid "**nexusdvs**: Represents Cisco Nexus 1000v distributed virtual switch."
+msgstr "**nexusdvs**：代表Cisco Nexus 1000v分布式虚拟交换机。"
+
+# 2d56af8dccba48b2b2d17ffd03843c42
+#: ../../hypervisor_installation.rst:3095
+msgid ""
+"If nothing specified (left empty), zone-level default virtual switchwould be"
+" defaulted, based on the value of global parameter you specify."
+msgstr "如果什么都没指定(留空)，基于全局参数指定的值，区域层面默认使用虚拟交换机。"
+
+# 3835c2ef7574443589a59537ac4b5ee1
+#: ../../hypervisor_installation.rst:3097
+msgid "Following are the global configuration parameters:"
+msgstr "以下为全局配置参数："
+
+# 14d738f065094961bd6549867db82e73
+#: ../../hypervisor_installation.rst:3099
+msgid ""
+"**vmware.use.dvswitch**: Set to true to enable any kind (VMware DVS and "
+"Cisco Nexus 1000v) of distributed virtual switch in a CloudStack deployment."
+" If set to false, the virtual switch that can be used in that CloudStack "
+"deployment is Standard virtual switch."
+msgstr "**vmware.use.dvswitch**：设置为true则是在CloudStack部署时启用任意种类(VMware DVS和Cisco Nexus 1000v) 分布式交换机。如果设置为false，则CloudStack部署时使用的的虚拟交换机是标准虚拟交换机。"
+
+# ec24241206114feba067a6c3b0ecf676
+#: ../../hypervisor_installation.rst:3101
+msgid ""
+"**vmware.use.nexus.vswitch**: This parameter is ignored if "
+"vmware.use.dvswitch is set to false. Set to true to enable Cisco Nexus 1000v"
+" distributed virtual switch in a CloudStack deployment."
+msgstr "**vmware.use.nexus.vswitch**：如果vmware.use.dvswitch设置为false，则忽略该参数。设置为true则是部署CloudStack时启用Cisco Nexus 1000v分布式交换机。"
+
+# e0c3306fd9204cee84716a8bb08ebf9a
+#: ../../hypervisor_installation.rst:3104
+msgid "Enabling Virtual Distributed Switch in CloudStack"
+msgstr "在CloudStack中启用分布式虚拟交换机"
+
+# 64c49f56242149a085fb175bfd6b2536
+#: ../../hypervisor_installation.rst:3106
+msgid ""
+"To make a CloudStack deployment VDS enabled, set the vmware.use.dvswitch "
+"parameter to true by using the Global Settings page in the CloudStack UI and"
+" restart the Management Server. Unless you enable the vmware.use.dvswitch "
+"parameter, you cannot see any UI options specific to VDS, and CloudStack "
+"ignores the VDS-specific parameters that you specify. Additionally, "
+"CloudStack uses VDS for virtual network infrastructure if the value of "
+"vmware.use.dvswitch parameter is true and the value of "
+"vmware.use.nexus.dvswitch parameter is false. Another global parameter that "
+"defines VDS configuration is vmware.ports.per.dvportgroup. This is the "
+"default number of ports per VMware dvPortGroup in a VMware environment. "
+"Default value is 256. This number directly associated with the number of "
+"guest network you can create."
+msgstr "在部署CloudStack时启用VDS，请在CloudStack管理界面中的全局设置页面中设置vmware.use.dvswitch parameter为true并重启管理服务器。只有启用了vmware.use.dvswitch参数，你才能在管理界面中指定VDS，并且CloudStack会忽略你指定的VDS-specific参数。另外，如果vmware.use.dvswitch参数的值为true且vmware.use.nexus.dvswitch参数的值为false，那么CloudStack中虚拟网络架构使用VDS。另外一个定义VDS配置的全局参数是vmware.ports.per.dvportgroup。它表示在VMware环境里每个VMware dvPortGroup中默认端口数量。默认是256。这个数值直接关系到你创建的来宾网络的数量。"
+
+# e5f3b06f38324241a2052677a1dad016
+#: ../../hypervisor_installation.rst:3120
+msgid ""
+"CloudStack supports orchestration of virtual networks in a deployment with a"
+" mix of Virtual Distributed Switch, Standard Virtual Switch and Nexus 1000v "
+"Virtual Switch."
+msgstr "CloudStack支持混合部署分布式虚拟交换机、标准虚拟交换机和Nexus 1000v虚拟交换机的虚拟网络。"
+
+# 37f6094d78df4e1aa3500f2b84650486
+#: ../../hypervisor_installation.rst:3125
+msgid "Configuring Distributed Virtual Switch in CloudStack"
+msgstr "在CloudStack中配置分布式虚拟交换机"
+
+# 3bc24235a56b49a18dd705133f2de55b
+#: ../../hypervisor_installation.rst:3127
+msgid ""
+"You can configure VDS by adding the necessary resources while a zone is "
+"created."
+msgstr "在创建区域时需要添加必要的资源才能配置VDS。"
+
+# c3a360b9f4564ac1abb2197484db4e3c
+#: ../../hypervisor_installation.rst:3130
+msgid ""
+"Alternatively, at the cluster level, you can create an additional cluster "
+"with VDS enabled in the existing zone. Use the Add Cluster option. For "
+"information as given in `“Add Cluster: vSphere” <configuration.html#add-"
+"cluster-vsphere>`_."
+msgstr "另外在群集层面，使用添加群集选项，可以在已经存在并启用VDS的区域中创建附加群集。更多信息请参阅 `“添加群集: vSphere” <configuration.html#add-cluster-vsphere>`_."
+
+# 479bfd3ed9a447da942d9b9ac2a2fdc2
+#: ../../hypervisor_installation.rst:3134
+msgid ""
+"In both these cases, you must specify the following parameters to configure "
+"VDS:"
+msgstr "在所有情况下，配置VDS时必须指定下列参数："
+
+# ebf6c05366ba437e921f5903665ed973
+#: ../../hypervisor_installation.rst:3137
+msgid "|dvSwitchConfig.png: Configuring dvSwitch|"
+msgstr "|dvSwitchConfig.png: Configuring dvSwitch|"
+
+# 09b1c441a46c49469130fa72f3614964
+#: ../../hypervisor_installation.rst:3140
+msgid "Parameters Description"
+msgstr "参数描述"
+
+# 708394a025b4492ab6e327dc380958e7
+#: ../../hypervisor_installation.rst:3142
+msgid ""
+"Enter the name of the cluster you created in vCenter. For example, "
+"\"cloudcluster\"."
+msgstr "输入在vCenter中创建的群集名称。比如，\"cloudcluster\"。"
+
+# d6c67ed27d304002a729b1628fb70fa0
+#: ../../hypervisor_installation.rst:3143
+msgid ""
+"Enter the name or the IP address of the vCenter host where you have deployed"
+" the VMware VDS."
+msgstr "输入已经部署VMware VDS的vCenter主机名称或者IP地址。"
+
+# 683d246203ba4cf8b5fd0d8e85bd640e
+#: ../../hypervisor_installation.rst:3146
+msgid ""
+"Enter the vCenter datacenter that the cluster is in. For example, "
+"\"clouddcVM\"."
+msgstr "输入群集所属的vCenter数据中心名称。比如，\"clouddcVM\"。"
+
+# 9fb1a295d3cf4ccf86187b7b78cf93b2
+#: ../../hypervisor_installation.rst:3147
+msgid "Override Public Traffic"
+msgstr "替代公共流量"
+
+# ea178483ff274a928f854444818454a2
+#: ../../hypervisor_installation.rst:3147
+msgid ""
+"Enable this option to override the zone-wide public traffic for the cluster "
+"you are creating."
+msgstr "启用该选项时，整个区域中群集的公共流量将被替代。"
+
+# 250b987e45194b0b9cb86b6b9fb5e336
+#: ../../hypervisor_installation.rst:3148
+msgid "Public Traffic vSwitch Type"
+msgstr "公共流量虚拟交换机类型"
+
+# b367523933b940aeaec12800a746a45d
+#: ../../hypervisor_installation.rst:3148
+msgid ""
+"This option is displayed only if you enable the Override Public Traffic "
+"option. Select VMware vNetwork Distributed Virtual Switch. If the "
+"vmware.use.dvswitch global parameter is true, the default option will be "
+"VMware vNetwork Distributed Virtual Switch."
+msgstr "在启用替代公共流量时该选项才会显示。选择VMware vNetwork Distributed Virtual Switch。如果全局设置中vmware.use.dvswitch参数为true，则默认选项为VMware vNetwork Distributed Virtual Switch。"
+
+# 29cb482d8776432b8c99b7e4c79cbe12
+#: ../../hypervisor_installation.rst:3149
+msgid "Public Traffic vSwitch Name"
+msgstr "公共流量虚拟交换机名称"
+
+# 086236537a4f4fc1a5440d11b0fca364
+#: ../../hypervisor_installation.rst:3149
+msgid "Name of virtual switch to be used for the public traffic."
+msgstr "用于公共流量的虚拟交换机名称。"
+
+# 704199c7e7eb4f1398126a60a08794de
+#: ../../hypervisor_installation.rst:3150
+msgid "Override Guest Traffic"
+msgstr "替代来宾流量"
+
+# 8f90f04bd418418f9eadbd9c926cb76f
+#: ../../hypervisor_installation.rst:3150
+msgid ""
+"Enable the option to override the zone-wide guest traffic for the cluster "
+"you are creating."
+msgstr "启用该选项时，整个区域中群集的来宾流量将被替代。"
+
+# 899928be044a48258741946368d91dcb
+#: ../../hypervisor_installation.rst:3151
+msgid "Guest Traffic vSwitch Type"
+msgstr "来宾流量虚拟交换机类型"
+
+# 6ddc80e638ab4ec8a613165199a028b0
+#: ../../hypervisor_installation.rst:3151
+msgid ""
+"This option is displayed only if you enable the Override Guest Traffic "
+"option. Select VMware vNetwork Distributed Virtual Switch. If the "
+"vmware.use.dvswitch global parameter is true, the default option will be "
+"VMware vNetwork Distributed Virtual Switch."
+msgstr "在启用替代来宾流量时该选项才会显示。选择VMware vNetwork Distributed Virtual Switch。如果全局设置中vmware.use.dvswitch参数为true，则默认选项为VMware vNetwork Distributed Virtual Switch。"
+
+# 5e253936428944ae8e8a5ebfadeea77a
+#: ../../hypervisor_installation.rst:3152
+msgid "Guest Traffic vSwitch Name"
+msgstr "来宾流量虚拟交换机名称"
+
+# 15215df1285d4b2985dfa06f3c8819ea
+#: ../../hypervisor_installation.rst:3152
+msgid "Name of virtual switch to be used for guest traffic."
+msgstr "用于宾流量的虚拟交换机名称。"
+
+# 774f8b0295a24386bce8cafe1f15f999
+#: ../../hypervisor_installation.rst:3157
+msgid "Storage Preparation for vSphere (iSCSI only)"
+msgstr "vSphere的存储准备(仅限iSCSI)"
+
+# ba00d524d9b244f2b911edffa0f8ded8
+#: ../../hypervisor_installation.rst:3159
+msgid ""
+"Use of iSCSI requires preparatory work in vCenter. You must add an iSCSI "
+"target and create an iSCSI datastore."
+msgstr "使用iSCSI需要在vCenter中做一些准备工作。您必须添加iSCSI目标并创建iSCSI数据存储。"
+
+# 8de2dece46ff46c8bac0bbd1e48b778d
+#: ../../hypervisor_installation.rst:3162
+msgid "If you are using NFS, skip this section."
+msgstr "如果使用NFS，请跳过本章节。"
+
+# fc698c19eb8549ed98ec961c04d753e1
+#: ../../hypervisor_installation.rst:3165
+msgid "Enable iSCSI initiator for ESXi hosts"
+msgstr "ESXi主机中启用iSCSI启动器"
+
+# 34512553af0249bea54fc8b9585cd5fa
+#: ../../hypervisor_installation.rst:3169
+msgid ""
+"In vCenter, go to hosts and Clusters/Configuration, and click Storage "
+"Adapters link. You will see:"
+msgstr "在vCenter中，点击主机/集群的配置，点击存储适配器。您将看到："
+
+# 684af7b07b1a459fb4e36ed78a8a83e6
+#: ../../hypervisor_installation.rst:3172
+msgid "|vmwareiscsiinitiator.png: iscsi initiator|"
+msgstr "|vmwareiscsiinitiator.png: iscsi initiator|"
+
+# 88e4da9927b54ee1a9a6654aa6d39aa3
+#: ../../hypervisor_installation.rst:3176
+msgid "Select iSCSI software adapter and click Properties."
+msgstr "选择iSCSI软件适配器并点击属性。"
+
+# 2e32277888274a049d00699208d7bc97
+#: ../../hypervisor_installation.rst:3178
+msgid "|vmwareiscsiinitiatorproperties.png: iscsi initiator properties|"
+msgstr "|vmwareiscsiinitiatorproperties.png: iscsi initiator properties|"
+
+# 8da2aa000a374d80acff80053a7e341f
+#: ../../hypervisor_installation.rst:3182
+msgid "Click the Configure... button."
+msgstr "点击配置...按钮。"
+
+# 59b2ef32cfdd4082b497b9cb05555129
+#: ../../hypervisor_installation.rst:3184
+msgid "|vmwareiscsigeneral.png: iscsi general|"
+msgstr "|vmwareiscsigeneral.png: iscsi general|"
+
+# e1eceaf44d2644f18076f265f4360592
+#: ../../hypervisor_installation.rst:3188
+msgid "Check Enabled to enable the initiator."
+msgstr "勾选启用以便启用启动器。"
+
+# e1263727e0d64a2ab200698db27ee1a3
+#: ../../hypervisor_installation.rst:3192
+msgid "Click OK to save."
+msgstr "点击 确定 保存。"
+
+# a210655c2dff4ddcb276836b8603412d
+#: ../../hypervisor_installation.rst:3195
+msgid "Add iSCSI target"
+msgstr "添加iSCSI目标"
+
+# abb57513fb3244288ea5ce00445f8f28
+#: ../../hypervisor_installation.rst:3197
+msgid "Under the properties dialog, add the iSCSI target info:"
+msgstr "在属性对话框中，添加iSCSI目标信息："
+
+# 4954b59047ab4ba29e2d92e3865b0fda
+#: ../../hypervisor_installation.rst:3199
+msgid "|vmwareiscsitargetadd.png: iscsi target add|"
+msgstr "|vmwareiscsitargetadd.png: iscsi target add|"
+
+# 88ca6dc96bb9499f9d1c7abcaff20aa3
+#: ../../hypervisor_installation.rst:3201
+msgid "Repeat these steps for all ESXi hosts in the cluster."
+msgstr "在集群中所有ESXi主机上重复以上步骤。"
+
+# 8bd62c3be43c48d493e98576eefe23f8
+#: ../../hypervisor_installation.rst:3204
+msgid "Create an iSCSI datastore"
+msgstr "创建iSCSI数据存储"
+
+# c548bf48a3674abb83e7b473c8e3f84f
+#: ../../hypervisor_installation.rst:3206
+msgid "You should now create a VMFS datastore. Follow these steps to do so:"
+msgstr "现在您应该创建一个VMFS数据存储。请按照以下步骤："
+
+# c518b88e8ecd4da09c536f9d74b508d3
+#: ../../hypervisor_installation.rst:3210
+msgid "Select Home/Inventory/Datastores."
+msgstr "选择主页/清单/数据存储。"
+
+# cdb74717625a427aa3c4a7ba5f93aee1
+#: ../../hypervisor_installation.rst:3214
+msgid "Right click on the datacenter node."
+msgstr "右键点击数据中心节点。"
+
+# 3d0a816c956442cf8c5b1f81c174ee22
+#: ../../hypervisor_installation.rst:3218
+msgid "Choose Add Datastore... command."
+msgstr "选择添加数据存储...命令。"
+
+# 19ad87337cb14cf585faf240d0ee2832
+#: ../../hypervisor_installation.rst:3222
+msgid "Follow the wizard to create a iSCSI datastore."
+msgstr "按照向导创建iSCSI数据存储。"
+
+# 7948a9ab7759441cbca06015f98026f0
+#: ../../hypervisor_installation.rst:3224
+msgid ""
+"This procedure should be done on one host in the cluster. It is not "
+"necessary to do this on all hosts."
+msgstr "该过程只需要在集群中的一台主机上执行，不需要在所有主机上执行。"
+
+# cfb21f6f84204119bd99ba701e71a839
+#: ../../hypervisor_installation.rst:3227
+msgid "|vmwareiscsidatastore.png: iscsi datastore|"
+msgstr "|vmwareiscsidatastore.png: iscsi datastore|"
+
+# 05536385fb5d4f589729735e6a15863a
+#: ../../hypervisor_installation.rst:3230
+msgid "Multipathing for vSphere (Optional)"
+msgstr "vSphere多路径(可选)"
+
+# 815ee00c2ff84bffb47b6cab9a634126
+#: ../../hypervisor_installation.rst:3232
+msgid ""
+"Storage multipathing on vSphere nodes may be done according to the vSphere "
+"installation guide."
+msgstr "vSphere的存储多路径可以根据vSphere的安装文档配置。"
+
+# 58b67a39f15e42eea22e40e779bc98ae
+#: ../../hypervisor_installation.rst:3236
+msgid "Add Hosts or Configure Clusters (vSphere)"
+msgstr "添加主机或配置集群(vSphere)"
+
+# 0f8ce9626c69404f8406c300f622fb16
+#: ../../hypervisor_installation.rst:3238
+msgid ""
+"Use vCenter to create a vCenter cluster and add your desired hosts to the "
+"cluster. You will later add the entire cluster to CloudStack. (see `“Add "
+"Cluster: vSphere” <configuration.html#add-cluster-vsphere>`_)."
+msgstr "使用vCenter创建集群，向其中添加期望的主机。随后您可以将整个集群加入到Cloudstack中。(参考 `“添加群集: vSphere” <configuration.html#add-cluster-vsphere>`_)。"
+
+# 7e7aadc035da44249de56ae7db92234a
+#: ../../hypervisor_installation.rst:3243
+msgid "Applying Hotfixes to a VMware vSphere Host"
+msgstr "为VMware vSphere主机安装补丁程序"
+
+# 74dba888d905486db0290fbfb7d772f6
+#: ../../hypervisor_installation.rst:3247
+msgid ""
+"Disconnect the VMware vSphere cluster from CloudStack. It should remain "
+"disconnected long enough to apply the hotfix on the host."
+msgstr "在CloudStack中断开与VMware vSphere 群集的连接。应断开足够长的时间以便在主机上安装补丁程序。"
+
+# da103b2f65c547b3ab083fc895aab582
+#: ../../hypervisor_installation.rst:3254
+msgid ""
+"See `“Log In to the UI” <http://docs.cloudstack.apache.org/projects"
+"/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_."
+msgstr "请参考 `“登录用户界面” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_。"
+
+# 7eeb8799b8aa4cc69456b839d9136ad7
+#: ../../hypervisor_installation.rst:3258
+msgid "Navigate to the VMware cluster, click Actions, and select Unmanage."
+msgstr "导航至VMware群集，点击操作-取消管理。"
+
+# d9e060820ffb4eb4b154fad98fd3ffa6
+#: ../../hypervisor_installation.rst:3267
+msgid "Perform the following on each of the ESXi hosts in the cluster:"
+msgstr "在集群中每个ESXi主机上执行以下操作："
+
+# d9e7f843369e4a78b51521805078baf0
+#: ../../hypervisor_installation.rst:3271
+msgid "Move each of the ESXi hosts in the cluster to maintenance mode."
+msgstr "将集群中每个ESXi都置为维护模式。"
+
+# 9bc4f3ee334e40db91a24562dd6845cd
+#: ../../hypervisor_installation.rst:3275
+msgid "Ensure that all the VMs are migrated to other hosts in that cluster."
+msgstr "确保所有的VM已经迁移到群集中的其他主机。"
+
+# 3ba2bffbc5e84ef3b01cae9d2dde0b71
+#: ../../hypervisor_installation.rst:3280
+msgid ""
+"If there is only one host in that cluster, shutdown all the VMs and move the"
+" host into maintenance mode."
+msgstr "如果群集中只有一台主机，关闭所有VMs再将主机置为维护模式。"
+
+# 6f64d848a8d64604844df448df999fe1
+#: ../../hypervisor_installation.rst:3285
+msgid "Apply the patch on the ESXi host."
+msgstr "在ESXi主机中应用补丁。"
+
+# 9c8782c75494411594d8b4faff7fbb1d
+#: ../../hypervisor_installation.rst:3289
+msgid "Restart the host if prompted."
+msgstr "如果提示重启，请重启主机。"
+
+# 25e36bd88cc24b0383e1b00df74727ad
+#: ../../hypervisor_installation.rst:3293
+msgid "Cancel the maintenance mode on the host."
+msgstr "在主机上取消维护模式。"
+
+# aaff92bbaee04efbbe1d87fdb627fcbf
+#: ../../hypervisor_installation.rst:3297
+msgid "Reconnect the cluster to CloudStack:"
+msgstr "重新连接该集群到CloudStack:"
+
+# da1d669463434dc087c342d31407e02f
+#: ../../hypervisor_installation.rst:3305
+msgid "Navigate to the VMware cluster, click Actions, and select Manage."
+msgstr "导航到VMware群集，点击操作-管理。"
+
+# fdb2ca3517e249e792bc1e09f0dcdf74
+#: ../../hypervisor_installation.rst:3309
+msgid ""
+"Watch the status to see that all the hosts come up. It might take several "
+"minutes for the hosts to come up."
+msgstr "查看状态以确保所有的主机都恢复正常。所有主机都恢复正常可能需要几分钟时间。"
+
+# 9cb4b470519146d4993237038291de2a
+#: ../../hypervisor_installation.rst:3312
+msgid ""
+"Alternatively, verify the host state is properly synchronized and updated in"
+" the CloudStack database."
+msgstr "或者，确认主机状态在数据库中得到正确同步和更新。"
+
+# ed31c9f3cf034bde88229da9ab4c4346
+#: ../../hypervisor_installation.rst:3316
+msgid "LXC Installation and Configuration"
+msgstr "LXC安装和配置"
+
+# 8b616c9ac2f844a4a829952baa39a8d0
+#: ../../hypervisor_installation.rst:3319
+msgid "System Requirements for LXC Hosts"
+msgstr "LXC主机的系统要求"
+
+# 219a7faad8ee431a8c64dfb3c12b2006
+#: ../../hypervisor_installation.rst:3321
+msgid ""
+"LXC requires the Linux kernel cgroups functionality which is available "
+"starting 2.6.24. Although you are not required to run these distributions, "
+"the following are recommended:"
+msgstr "LXC要求Linux kernel 2.6.24开始引入的 cgroups功能。尽管不需要运行所有的发行版，但是建议下列的版本："
+
+# 5a6c2e85c2114428bfbb1d20f74e4205
+#: ../../hypervisor_installation.rst:3333
+msgid ""
+"The main requirement for LXC hypervisors is the libvirt and Qemu version. No"
+" matter what Linux distribution you are using, make sure the following "
+"requirements are met:"
+msgstr "LXC hypervisor 要求libvirt和Qemu的版本。无论使用哪种Linux发行版，请确保满足以下要求："
+
+# d7670075be644f0f80515c081452803e
+# 40888512180848d2809af703d71e45d4
+#: ../../hypervisor_installation.rst:3339
+#: ../../hypervisor_installation.rst:3351
+msgid "libvirt: 1.0.0 or higher"
+msgstr "libvirt: 1.0.0或更高"
+
+# be2989bd0e4c4180acf1abe0c0506e16
+#: ../../hypervisor_installation.rst:3391
+msgid "LXC Installation Overview"
+msgstr "LXC安装概述"
+
+# 03fc8905df0d492d9aa9667071f355fc
+#: ../../hypervisor_installation.rst:3393
+msgid ""
+"LXC does not have any native system VMs, instead KVM will be used to run "
+"system VMs. This means that your host will need to support both LXC and KVM,"
+" thus most of the installation and configuration will be identical to the "
+"KVM installation. The material in this section doesn't duplicate KVM "
+"installation docs. It provides the CloudStack-specific steps that are needed"
+" to prepare a KVM host to work with CloudStack."
+msgstr "LXC没有任何本地系统VMs，而KVM需要运行系统VMs。意思为主机需要同时支持LXC和KVM。因此，大部分的安装和配置跟KVM的安装一样。本章节不会复述KVM的安装。这里我们只会给出使KVM与CloudStack协同工作的一些特有的步骤。"
+
+# 2b1366e9b99546e58720ccf100d16276
+#: ../../hypervisor_installation.rst:3404
+msgid "The procedure for installing an LXC Host is:"
+msgstr "安装LXC主机步骤："
+
+# 84a60e9ea64b44d09cda82651720fefe
+#: ../../hypervisor_installation.rst:3479
+msgid ""
+"To manage LXC instances on the host CloudStack uses a Agent. This Agent "
+"communicates with the Management server and controls all the instances on "
+"the host."
+msgstr "CloudStack使用代理管理LXC实例。管理服务器与代理通信并控制主机中所有实例。"
+
+# 6e8937e78ff6442db35604533d058b4a
+#: ../../hypervisor_installation.rst:3497
+msgid ""
+"Next step is to update the Agent configuration setttings. The settings are "
+"in ``/etc/cloudstack/agent/agent.properties``"
+msgstr "接下来更新代理配置。在 ``/etc/cloudstack/agent/agent.properties`` 中配置"
+
+# 7aeff42329424749810bdfb5dd405477
+#: ../../hypervisor_installation.rst:3502
+msgid "Set the Agent to run in LXC mode:"
+msgstr "设置代理运行在LXC模式下："
+
+# ac8184a4dc794aba9e64574610cfe257
+#: ../../hypervisor_installation.rst:3510
+msgid ""
+"Optional: If you would like to use direct networking (instead of the default"
+" bridge networking), configure these lines:"
+msgstr "可选项：如果想使用直连网络(代替默认的桥接网络)，配置如下行："
+
+# 195b19dc40204c8b94d2cb8e43198e2e
+#: ../../hypervisor_installation.rst:3595
+msgid ""
+"In order to have the VNC Console work we have to make sure it will bind on "
+"0.0.0.0. We do this by editing ``/etc/libvirt/qemu.conf``"
+msgstr "为了VNC控制台正常工作，必须确保该参数绑定在0.0.0.0上。通过编辑 ``/etc/libvirt/qemu.conf``实现。"
+
+# 48827fdb267f46b3be0c06af135ba563
+#: ../../hypervisor_installation.rst:3598
+msgid "Make sure this parameter is set:"
+msgstr "请确保这个参数配置为："
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/index.mo b/source/installguide/locale/zh_CN/LC_MESSAGES/index.mo
new file mode 100644
index 0000000..9735adf
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/index.mo
Binary files differ
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/index.po b/source/installguide/locale/zh_CN/LC_MESSAGES/index.po
new file mode 100644
index 0000000..2b2e062
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/index.po
@@ -0,0 +1,115 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: 2014-06-30 10:23+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 982ed5120e594d65bcff280a0398f5af
+#: ../../index.rst:23
+msgid "Welcome to CloudStack Installation Documentation"
+msgstr "欢迎阅读CloudStack安装文档"
+
+# 1f1f369df4b645e0bbda82cf077bdbd6
+#: ../../index.rst:29
+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 ""
+
+# b3e6055f64164ee0b851226b5573bfb3
+#: ../../index.rst:33
+msgid ""
+"This is the Apache CloudStack installation guide, for the Documentation "
+"home, the administrator guide or the Release-Notes please see:"
+msgstr ""
+
+# b643ff53ad664a829c30729664d2ad00
+#: ../../index.rst:36
+msgid "`Documentation home <http://docs.cloudstack.apache.org>`_"
+msgstr "`文档 主页 <http://docs.cloudstack.apache.org>`_"
+
+# 2cf98f8dcdff4610b15031a039d4c5c6
+#: ../../index.rst:38
+msgid ""
+"`Administration Guide <http://docs.cloudstack.apache.org/projects"
+"/cloudstack-administration>`_"
+msgstr "`管理指南 <http://docs.cloudstack.apache.org/projects/cloudstack-administration>`_"
+
+# a98ac35a7f2b4cf9b3090ff68dc12650
+#: ../../index.rst:41
+msgid ""
+"`Release Notes <http://docs.cloudstack.apache.org/projects/cloudstack-"
+"release-notes>`_"
+msgstr "`发行说明 <http://docs.cloudstack.apache.org/projects/cloudstack-release-notes>`_"
+
+# 86316507b4b44a5a96cfdb3721f97bd4
+#: ../../index.rst:45
+msgid ""
+"In this guide we first go through some design and architectural choices_ to "
+"build your cloud. Then we dive into a single node quick start guide_ to give"
+" you a feel for the installation process. The source installation steps_ are"
+" given in the follow-on section for people who want to build their own "
+"packages. Otherwise you can use the general installation_ which makes use of"
+" community maintained package repositories. The rest of the guide goes "
+"through the configuration_ of the data-center and the setup of the network_,"
+" storage_ and hypervisors_."
+msgstr ""
+
+# df08cf7ea88245c086043ad57af8e8ac
+#: ../../index.rst:60
+msgid "Choosing a Deployment Architecture"
+msgstr "选择部署架构"
+
+# dbccc2fe994c4999b821643c7bde3eb3
+#: ../../index.rst:70
+msgid "Quick Installation Guide"
+msgstr "快速安装指南"
+
+# a05a3c5a35ca46418756c797e93cdc38
+#: ../../index.rst:80
+msgid "Source Installation"
+msgstr "源码安装"
+
+# 42b62bda8da0413d80b6718dab581b66
+#: ../../index.rst:90
+msgid "General Installation"
+msgstr "常规安装"
+
+# e9c99f765efc4b4396d3d68516bd9f05
+#: ../../index.rst:100
+msgid "Configuration"
+msgstr "配置"
+
+# e126703be1d04fb1a536bbecd12daafa
+#: ../../index.rst:110
+msgid "Hypervisor Setup"
+msgstr ""
+
+# 64d7386116784ddfbfaee06209c06377
+#: ../../index.rst:121
+msgid "Network Setup"
+msgstr "网络设置"
+
+# ca4526f59f884297b45db3c6d92cd6a6
+#: ../../index.rst:131
+msgid "Storage Setup"
+msgstr "存储设置"
+
+# a7129d9d6924487eb5056763f614e703
+#: ../../index.rst:139
+msgid "Optional Installation"
+msgstr "可选安装"
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/installation.mo b/source/installguide/locale/zh_CN/LC_MESSAGES/installation.mo
new file mode 100644
index 0000000..db1ebb6
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/installation.mo
Binary files differ
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/installation.po b/source/installguide/locale/zh_CN/LC_MESSAGES/installation.po
new file mode 100644
index 0000000..7ea4ad0
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/installation.po
@@ -0,0 +1,1592 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: 2014-06-30 10:24+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# a4c7e830381745529dad6a0b1d27abc8
+#: ../../installation.rst:18
+msgid "Installation"
+msgstr "安装"
+
+# 08b24c18afac496395e10054c9cf0e71
+#: ../../installation.rst:21
+msgid "Who Should Read This"
+msgstr "谁应该读本文"
+
+# d5a90994aea94deab277060989225b05
+#: ../../installation.rst:23
+msgid ""
+"For those who have already gone through a design phase and planned a more "
+"sophisticated deployment, or those who are ready to start scaling up a trial"
+" installation. With the following procedures, you can start using the more "
+"powerful features of CloudStack, such as advanced VLAN networking, high "
+"availability, additional network elements such as load balancers and "
+"firewalls, and support for multiple hypervisors including Citrix XenServer, "
+"KVM, and VMware vSphere."
+msgstr "如果您已经完成设计阶段，计划部署一个复杂的云，或是准备对用基础安装向导搭建的试验云进行扩展，请选择此项。在后续过程中，您可以使用CloudStack中更强大的功能，例如高级VLAN网络、高可用、负载均衡器和防火墙等额外网络设备，以及支持Citrix XenServer、KVM、VMware vSphere等多种虚拟化平台。"
+
+# e7eb83f865c242ae89ad4c8ae65ed988
+#: ../../installation.rst:33
+msgid "Overview of Installation Steps"
+msgstr "安装步骤概述"
+
+# fc6cbd3f722e496ca3d7a1716a44bc03
+#: ../../installation.rst:35
+msgid ""
+"For anything more than a simple trial installation, you will need guidance "
+"for a variety of configuration choices. It is strongly recommended that you "
+"read the following:"
+msgstr "对于任何一个简单的实验设备，你将需要一系列的配置选择向导。强烈推荐您阅读以下内容："
+
+# 718aecc72e104a2997aba969ae4564c4
+#: ../../installation.rst:39
+msgid "Choosing a Deployment Architecture"
+msgstr "选择部署架构"
+
+# cd6d4bbfdbcb4ae0953b3b36d308c7f5
+#: ../../installation.rst:41
+msgid "Choosing a Hypervisor: Supported Features"
+msgstr "选择Hypervisor：支持的功能"
+
+# 2a0787f9ba6d4b13ba9574e2a6334c2f
+#: ../../installation.rst:43
+msgid "Network Setup"
+msgstr "网络设置"
+
+# f606c83b98e54324a4376e39edcd5e20
+#: ../../installation.rst:45
+msgid "Storage Setup"
+msgstr "存储设置"
+
+# 75e8e878e0284aeeb3f52820e7b675eb
+#: ../../installation.rst:47
+msgid "Best Practices"
+msgstr "最佳实践"
+
+# c1ad793994b9421295f7503b7488274c
+#: ../../installation.rst:49
+msgid ""
+"Make sure you have the required hardware ready. See :ref:`minimum-system-"
+"requirements`"
+msgstr "确定您已经准备好了所需的硬件。参阅 :ref:`minimum-system-requirements`"
+
+# f5dba433b73f4e4b985060a388b195f0
+#: ../../installation.rst:52
+msgid ""
+"Install the Management Server (choose single-node or multi-node). See "
+":ref:`adding-a-zone`"
+msgstr "安装管理服务器 (选择单节点或多节点)。 参阅 :ref:`adding-a-zone`"
+
+# 58ea8b1ced9547bfa75c75859ac799cc
+#: ../../installation.rst:55
+msgid ""
+"Log in to the UI. See `*User Interface* "
+"<http://docs.cloudstack.apache.org/projects/cloudstack-"
+"administration/en/latest/ui.html#log-in-to-the-ui>`_"
+msgstr "登陆到用户界面。参阅 `*用户界面* <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/ui.html#log-in-to-the-ui>`_"
+
+# d05317e5c0ee48f6b90a44c8b2fcf367
+#: ../../installation.rst:58
+msgid ""
+"Add a zone. Includes the first pod, cluster, and host. See "
+":ref:`adding-a-host`"
+msgstr "添加区域。包含第一个Pod，群集，和主机。参阅 :ref:`adding-a-host`"
+
+# b534b474577b4160ba2cd604d9d52532
+#: ../../installation.rst:61
+msgid "Add more pods (optional). See :ref:`adding-a-pod`"
+msgstr "添加更多的Pod(可选)。参阅 :ref:`adding-a-pod`"
+
+# 299d7e46a3df47ac8e42ee1933e4f29a
+#: ../../installation.rst:63
+msgid "Add more clusters (optional). See :ref:`adding-a-cluster`"
+msgstr "添加更多的群集(可选)。参阅 :ref:`adding-a-cluster`"
+
+# dedefe67789b49af8ace78432dfc2868
+#: ../../installation.rst:65
+msgid "Add more hosts (optional). See :ref:`adding-a-host`"
+msgstr "添加更多的主机(可选)。参阅 :ref:`adding-a-host`"
+
+# 920aa393f8604a648a3f4303e57d1775
+#: ../../installation.rst:67
+msgid "Add more primary storage (optional). See :ref:`add-primary-storage`"
+msgstr "添加更多的主存储(可选)。参阅 :ref:`add-primary-storage`"
+
+# da3f95f402c24f0aa74c36350d5ec371
+#: ../../installation.rst:69
+msgid ""
+"Add more secondary storage (optional). See :ref:`add-secondary-storage`"
+msgstr "添加更多的辅助存储(可选)。参阅 :ref:`add-secondary-storage`"
+
+# 310612dae82445ae8be69f78801a9750
+#: ../../installation.rst:71
+msgid "Try using the cloud. See :ref:`initialize-and-test`"
+msgstr "尝试使用云。参阅： :ref:`initialize-and-test`"
+
+# 482c0b3104aa43dfb72e0a4f853e1463
+#: ../../installation.rst:77
+msgid "Minimum System Requirements"
+msgstr "最低系统需求"
+
+# ea094f27fd264abe88f63697eb32c463
+#: ../../installation.rst:80
+msgid "Management Server, Database, and Storage System Requirements"
+msgstr "管理服务器，数据库和存储系统需求。"
+
+# 910332017d854085a74ff0715162f1b2
+#: ../../installation.rst:82
+msgid ""
+"The machines that will run the Management Server and MySQL database must "
+"meet the following requirements. The same machines can also be used to "
+"provide primary and secondary storage, such as via localdisk or NFS. The "
+"Management Server may be placed on a virtual machine."
+msgstr "运行管理服务器和mysql数据库的机器必须满足以下要求。主存储和辅助存储可以通过本地存储或NFS配置在一台机器上。管理服务器可以安装在虚拟机中。"
+
+# 8e4f1eb139534c4ca4d93f7537dd3fa7
+#: ../../installation.rst:87
+msgid "Operating system:"
+msgstr "操作系统："
+
+# 29b8ae9600b245fe9c60f040f52adfa5
+#: ../../installation.rst:89
+msgid "Preferred: CentOS/RHEL 6.3+ or Ubuntu 12.04(.1)"
+msgstr "推荐：CentOS/RHEL 6.3+ 或 Ubuntu 12.04(.1)"
+
+# 24d4cd50a00945eb98763313d2f65f17
+# 1c5c18472c5644a89e3aecc627b13b6c
+#: ../../installation.rst:91 ../../installation.rst:114
+msgid "64-bit x86 CPU (more cores results in better performance)"
+msgstr "64位x86 CPU(多核性能更佳)"
+
+# 851608c72118406792e449b1d8c7b83a
+# 4f02c321329446d5815a250b05fe2778
+#: ../../installation.rst:93 ../../installation.rst:118
+msgid "4 GB of memory"
+msgstr "4GB 内存"
+
+# 4d8ce09b8a0542e892df38be3af682bf
+#: ../../installation.rst:95
+msgid ""
+"250 GB of local disk (more results in better capability; 500 GB recommended)"
+msgstr "250GB本地硬盘 (更大的容量性能更佳；推荐500GB)"
+
+# 165ce3c523d64e48b04f71ebd0996dd9
+# 4ab891d3ef9f4fdda64c88a8120a9205
+#: ../../installation.rst:98 ../../installation.rst:122
+msgid "At least 1 NIC"
+msgstr "至少一块网卡"
+
+# 1ada394b4bf74ee5a1152e0e725fd331
+#: ../../installation.rst:100
+msgid "Statically allocated IP address"
+msgstr "静态分配的IP地址"
+
+# 230435b75353467b84290fa91c4c08b8
+#: ../../installation.rst:102
+msgid "Fully qualified domain name as returned by the hostname command"
+msgstr "使用hostname命令能返回的完全合格的域名"
+
+# 69ac02bcef5348719f0240d8836e0006
+#: ../../installation.rst:106
+msgid "Host/Hypervisor System Requirements"
+msgstr "主机/Hypervisor系统需求"
+
+# 1820da09a6ae428f9ae4bd3ce16ef3c5
+#: ../../installation.rst:108
+msgid ""
+"The host is where the cloud services run in the form of guest virtual "
+"machines. Each host is one machine that meets the following requirements:"
+msgstr "主机是以虚拟机形式运行云服务。每台主机需满足如下要求："
+
+# 8eecb5d0a6ee40a395e47f52168d5d20
+#: ../../installation.rst:112
+msgid "Must support HVM (Intel-VT or AMD-V enabled)."
+msgstr "必须支持HVM(启用Intel-VT或AMD-V)。"
+
+# c6343d4def954507b56afb34ef637859
+#: ../../installation.rst:116
+msgid "Hardware virtualization support required"
+msgstr "硬件虚拟化支持"
+
+# 292a0c2480e44ec4a30cbc5689aa828a
+#: ../../installation.rst:120
+msgid "36 GB of local disk"
+msgstr "36GB本地磁盘空间"
+
+# 951d1eb038d94e3bac57bdfcc52377af
+#: ../../installation.rst:125
+msgid ""
+"If DHCP is used for hosts, ensure that no conflict occurs between DHCP "
+"server used for these hosts and the DHCP router created by CloudStack."
+msgstr "如果主机使用DHCP，请确保这些主机使用的DHCP服务和CloudStack创建的虚拟路由器提供的DHCP服务不冲突。"
+
+# 142b536acb8941f29e7b44145c079dfa
+#: ../../installation.rst:128
+msgid "Latest hotfixes applied to hypervisor software"
+msgstr "虚拟机软件需打好最新的补丁"
+
+# 9815b650b1b94eba9ad10c4684f5cb0a
+#: ../../installation.rst:130
+msgid ""
+"When you deploy CloudStack, the hypervisor host must not have any VMs "
+"already running"
+msgstr "在部署CloudStack时，Hypervisor主机不能运行任何虚拟机"
+
+# 56e1f4ebe58147f5abd5c96844f64bb5
+#: ../../installation.rst:133
+msgid ""
+"All hosts within a cluster must be homogeneous. The CPUs must be of the same"
+" type, count, and feature flags."
+msgstr "集群中的主机必须是相同架构。CPU的型号、数量和功能参数必须相同。"
+
+# 00933a4ac68a4d19b25c5a6eb58c517e
+#: ../../installation.rst:136
+msgid ""
+"Hosts have additional requirements depending on the hypervisor. See the "
+"requirements listed at the top of the Installation section for your chosen "
+"hypervisor:"
+msgstr "根据所使用虚拟化软件的不同主机可能有另外的需求。详情请查看你所选用虚拟化软件安装部分的需求清单"
+
+# 962bf99b90fa4d2a8edf81295e1df42a
+#: ../../installation.rst:141
+msgid ""
+"Be sure you fulfill the additional hypervisor requirements and installation "
+"steps provided in this Guide. Hypervisor hosts must be properly prepared to "
+"work with CloudStack. For example, the requirements for XenServer are listed"
+" under Citrix XenServer Installation."
+msgstr "如果你按照本指南的步骤并确定你满足了所选用虚拟机软件的 要求。宿主机应该就可以在CloudStack中正常工作了。比如XenServer的要求列表在Citrix XenServer安装部分。"
+
+# 124105e82a0647a994481c09b2a6e3fd
+#: ../../installation.rst:148
+msgid "Configure package repository"
+msgstr "配置包仓库"
+
+# cd54d36f52df4a02bd4ee88dbaa9ac5d
+#: ../../installation.rst:150
+msgid ""
+"CloudStack is only distributed from source from the official mirrors. "
+"However, members of the CloudStack community may build convenience binaries "
+"so that users can install Apache CloudStack without needing to build from "
+"source."
+msgstr "CloudStack是唯一一种源自官方镜像源文件的分布式平台。尽管如此，CloudStack社区的成语可以构建便捷的二进制代码，使用户能够在无需构建源代码的情况下安装Apache CloudStack。"
+
+# a904edd1fa324be999f28aad8271c6e3
+#: ../../installation.rst:155
+msgid ""
+"If you didn't follow the steps to build your own packages from source in the"
+" sections for `“Building RPMs from Source” <building_from_source.html"
+"#building-rpms-from-source>`_ or `“Building DEB packages” "
+"<building_from_source.html#building-deb-packages>`_ you may find pre-built "
+"DEB and RPM packages for your convenience linked from the `downloads "
+"<http://cloudstack.apache.org/downloads.html>`_ page."
+msgstr "如果你不能按照步骤使用源码构建你自己的包 `“从源码编译RPM包” <building_from_source.html#building-rpms-from-source>`_ 或 `“编译DEB包” <building_from_source.html#building-deb-packages>`_ 你会发现预先构建的DEB和RPM包在 `下载 <http://cloudstack.apache.org/downloads.html>`_ 页面."
+
+# 2cd5d4a70be54d9fad1ee09ac0a59781
+#: ../../installation.rst:163
+msgid ""
+"These repositories contain both the Management Server and KVM Hypervisor "
+"packages."
+msgstr "该仓库同时包含管理服务器和KVM Hypervisor的包"
+
+# ea53cfd031f54c11b1c35976f3e3ce76
+#: ../../installation.rst:168
+msgid "DEB package repository"
+msgstr "DEB包库"
+
+# d5c18e89ae43496093da2abe5de613ad
+#: ../../installation.rst:170
+msgid ""
+"You can add a DEB package repository to your apt sources with the following "
+"commands. Please note that only packages for Ubuntu 12.04 LTS (precise) are "
+"being built at this time."
+msgstr "你可以按照以下指令在你的apt源中增加DEB包库。请注意只有来自 Ubuntu 12.04 LTS (precise)的包可以在此时构建。"
+
+# 80c95c86ec504d6ea8771c2c09678dce
+#: ../../installation.rst:174
+msgid ""
+"Use your preferred editor and open (or create) "
+"``/etc/apt/sources.list.d/cloudstack.list``. Add the community provided "
+"repository to the file:"
+msgstr "用你准备好的编辑器打开(或创建) ``/etc/apt/sources.list.d/cloudstack.list``.将社区提供的仓库添加到该文件："
+
+# 4e809dbba4344fe3bbe0c803b417c4a5
+#: ../../installation.rst:182
+msgid "We now have to add the public key to the trusted keys."
+msgstr "我们现在必须添加公钥并信任密钥。"
+
+# 3308e4a303fa4e109dfe4f012bb673a1
+#: ../../installation.rst:188
+msgid "Now update your local apt cache."
+msgstr "现在升级本地的apt缓存"
+
+# 499fecdd520c470e9e64923350071343
+#: ../../installation.rst:194
+msgid ""
+"Your DEB package repository should now be configured and ready for use."
+msgstr "你的DEB包库现在将被配置并准备使用。"
+
+# 4201a19d82ec40359482777eca721afe
+#: ../../installation.rst:198
+msgid "RPM package repository"
+msgstr "RPM 包仓库"
+
+# a8e0ee6a46fe473f84e190a7a84274a9
+#: ../../installation.rst:200
+msgid ""
+"There is a RPM package repository for CloudStack so you can easily install "
+"on RHEL based platforms."
+msgstr "这里有一个CloudStack的RPM包库，所以你可以轻易地安装在RHEL基础平台上。"
+
+# 0c1bb2bafcf9461ebb5cd59ead93db9f
+#: ../../installation.rst:203
+msgid ""
+"If you're using an RPM-based system, you'll want to add the Yum repository "
+"so that you can install CloudStack with Yum."
+msgstr "如果你使用基于RPM的系统，你需要添加Yum库，以便可以用Yum安装CloudStack."
+
+# 562991c4185349599619509cfbce173d
+#: ../../installation.rst:206
+msgid ""
+"Yum repository information is found under ``/etc/yum.repos.d``. You'll see "
+"several ``.repo`` files in this directory, each one denoting a specific "
+"repository."
+msgstr "Yum库信息在``/etc/yum.repos.d``中。你可以看到一些 ``.repo``文件在这个目录中，每个都代表一个特定的仓库。"
+
+# e49d0a5613af49f69d54163f32b5f898
+#: ../../installation.rst:210
+msgid ""
+"To add the CloudStack repository, create "
+"``/etc/yum.repos.d/cloudstack.repo`` and insert the following information."
+msgstr "添加CloudStack库，创建 ``/etc/yum.repos.d/cloudstack.repo``并插入以下信息"
+
+# d78ed0190d354e4bac2f1c82b8c21dd9
+#: ../../installation.rst:222
+msgid "Now you should be able to install CloudStack using Yum."
+msgstr "现在你可以通过Yum安装CloudStack 。"
+
+# 37094bccdf5f4a6db4dc73588c0d1bc4
+#: ../../installation.rst:226
+msgid "Management Server Installation"
+msgstr "管理服务器安装"
+
+# f57b33dd6c14414ab5c880b0b9a0c438
+#: ../../installation.rst:229
+msgid "Management Server Installation Overview"
+msgstr "管理服务器安装概述"
+
+# 5273d79a7d1f4a12ac19c6d2fdff6406
+#: ../../installation.rst:231
+msgid ""
+"This section describes installing the Management Server. There are two "
+"slightly different installation flows, depending on how many Management "
+"Server nodes will be in your cloud:"
+msgstr "本节介绍管理服务器的安装. 根据你云环境中管理服务器节点个数的不同, 安装步骤有两处稍有不同."
+
+# e05140db89854adbaa7419d25e9dc6ce
+#: ../../installation.rst:235
+msgid "A single Management Server node, with MySQL on the same node."
+msgstr "一个单独的管理服务器节点, MySQL也装在这个节点上."
+
+# 06bdcc369df244f99ad92914eb680347
+#: ../../installation.rst:237
+msgid ""
+"Multiple Management Server nodes, with MySQL on a node separate from the "
+"Management Servers."
+msgstr "多个管理服务器节点, MySQL装在与所有管理服务都不相同的节点上."
+
+# e4b810d71c474f4f98cb64eb346d7404
+#: ../../installation.rst:240
+msgid ""
+"In either case, each machine must meet the system requirements described in "
+"System Requirements."
+msgstr "无论哪种方案, 所有系统的要求都要符合系统需求里的描述."
+
+# 8c6a890d62c94b3c805523d0e55b6b45
+#: ../../installation.rst:244
+msgid ""
+"For the sake of security, be sure the public Internet can not access port "
+"8096 or port 8250 on the Management Server."
+msgstr "出于安全的目的，确保公共网络无法访问管理服务器的8096或者8250端口。"
+
+# 346be7547c7f40ac94d3fd4d11d242b8
+#: ../../installation.rst:247
+msgid "The procedure for installing the Management Server is:"
+msgstr "安装管理服务器的步骤:"
+
+# f5dab499f03647d4b215ac7dc00d2cc8
+# 1d99cd2343054c51bc38e14ba435eef4
+#: ../../installation.rst:249 ../../installation.rst:265
+msgid "Prepare the Operating System"
+msgstr "准备操作系统"
+
+# 4eb68311296e426493a33ddad4958fd8
+#: ../../installation.rst:251
+msgid "(XenServer only) Download and install vhd-util."
+msgstr "（仅限XenServer）下载并安装vhd-util."
+
+# 55d017a2eb3048f1a6e12d9af9ebdc95
+#: ../../installation.rst:253
+msgid "Install the First Management Server"
+msgstr "安装第一台管理服务器"
+
+# be88182cc4d841e884f72dc58d0c597b
+#: ../../installation.rst:255
+msgid "Install and Configure the MySQL database"
+msgstr "安装并配置MySQL数据库。"
+
+# 4c17f8202a1a463589bea6ccc1e5da82
+# e69fe8462a0d4dfc9884fe69c7555783
+#: ../../installation.rst:257 ../../installation.rst:835
+msgid "Prepare NFS Shares"
+msgstr "准备NFS共享存储"
+
+# e5c5a79c1bbb41a5a37c13f1bcb2269b
+#: ../../installation.rst:259
+msgid "Prepare and Start Additional Management Servers (optional)"
+msgstr "准备并启动额外的管理服务器(可选)"
+
+# bb0613b20bae44ec8ea0d6cf3daf54d7
+# 72e55f8870934e6c8f91c0d9a02b53a0
+#: ../../installation.rst:261 ../../installation.rst:1124
+msgid "Prepare the System VM Template"
+msgstr "准备系统虚拟机模板"
+
+# b185c81663174e87aec00ebea42b6106
+#: ../../installation.rst:267
+msgid ""
+"The OS must be prepared to host the Management Server using the following "
+"steps. These steps must be performed on each Management Server node."
+msgstr "要在主机上安装管理服务器,需要按下列步骤准备操作系统. 这些步骤必须在每个要安装的管理服务器节点上执行."
+
+# ad31e2f017254bf4a8bc4b18ed1eb333
+#: ../../installation.rst:271
+msgid "Log in to your OS as root."
+msgstr "使用root用户登录操作系统。"
+
+# f68b5990a29e47a49e5576f3448ae36a
+#: ../../installation.rst:273
+msgid "Check for a fully qualified hostname."
+msgstr "检查FQN完全合格/限定主机名。"
+
+# 68c1a1f0f21745aeb403104055ac4fa9
+#: ../../installation.rst:279
+msgid ""
+"This should return a fully qualified hostname such as "
+"\"management1.lab.example.org\". If it does not, edit /etc/hosts so that it "
+"does."
+msgstr "该命令会返回完整主机名，例如\"management1.lab.example.org\"。如果没有，请编辑 /etc/hosts。"
+
+# 462aa5bfa1ed4426a0fe8fee25f76011
+#: ../../installation.rst:283
+msgid "Make sure that the machine can reach the Internet."
+msgstr "确保机器可以连接到互联网."
+
+# 5b249851325348f5a05df2a11b1a9605
+#: ../../installation.rst:289
+msgid "Turn on NTP for time synchronization."
+msgstr "启用NTP服务以确保时间同步."
+
+# e81842c1ee6c4557856769bb6a36922d
+#: ../../installation.rst:292
+msgid ""
+"NTP is required to synchronize the clocks of the servers in your cloud."
+msgstr "NTP服务用来在你的云中同步服务器时钟。"
+
+# 1ff32df950c6457084e12020a249a243
+#: ../../installation.rst:294
+msgid "Install NTP."
+msgstr "安装NTP."
+
+# dbe1f8c7f9d8488598b40da7132bc863
+#: ../../installation.rst:304
+msgid ""
+"Repeat all of these steps on every host where the Management Server will be "
+"installed."
+msgstr "在每一个安装管理服务器的节点上重复所有这些步骤."
+
+# 332fe2c7d34f46a2b229fc215761f6c4
+#: ../../installation.rst:309
+msgid "Install the Management Server on the First Host"
+msgstr "在第一台主机上安装管理服务器"
+
+# 8f353218baed48e4be6f9ca53b9c2541
+#: ../../installation.rst:311
+msgid ""
+"The first step in installation, whether you are installing the Management "
+"Server on one host or many, is to install the software on a single node."
+msgstr "安装的第一步，不论你在一台或多台主机上安装管理服务器，在单个节点上安装这些软件。"
+
+# 2a1b09c8c09641489db8c0d49c04ae16
+#: ../../installation.rst:316
+msgid ""
+"If you are planning to install the Management Server on multiple nodes for "
+"high availability, do not proceed to the additional nodes yet. That step "
+"will come later."
+msgstr "如果你计划为了高可用在多个节点安装管理服务器，目前不要进行添加其他节点，这个会在后面的步骤中进行"
+
+# 407f24df1ba44541821f28c24576289f
+#: ../../installation.rst:320
+msgid ""
+"The CloudStack Management server can be installed using either RPM or DEB "
+"packages. These packages will depend on everything you need to run the "
+"Management server."
+msgstr "CloudStack管理服务器可以用RMP或者DEB包来安装，这些包会依赖运行管理服务器的所有需要的东西。"
+
+# de7dec2f592640af80d9557e78bdc3af
+#: ../../installation.rst:326
+msgid "Install on CentOS/RHEL"
+msgstr "在CentOS/RHEL上安装"
+
+# 0f47773dda6d44e5a36844163a8642b9
+#: ../../installation.rst:328
+msgid "We start by installing the required packages:"
+msgstr "我们开始安装需要的软件包："
+
+# d2538978382d4b47b1f84bc381b1009f
+#: ../../installation.rst:336
+msgid "Install on Ubuntu"
+msgstr "在Ubuntu上安装"
+
+# 47bc07e11dac4257b9ce54f511342915
+#: ../../installation.rst:344
+msgid ""
+"There is a known bug in the 4.3.0 release. You need to install an additional"
+" package by hand:"
+msgstr ""
+
+# aef5f1918b994df1a0da2b55407ba85f
+#: ../../installation.rst:350
+msgid ""
+"This bug has been fixed in master and upcoming 4.4 release and will also be "
+"fixed in bug fix releases 4.3.x"
+msgstr ""
+
+# 7db6de4cc37d43b8acb33c19898ce6f8
+#: ../../installation.rst:353
+msgid "Downloading vhd-util"
+msgstr "下载vhd-util"
+
+# 39d5d2480cea49508d2a2589ef174eca
+#: ../../installation.rst:355
+msgid ""
+"This procedure is required only for installations where XenServer is "
+"installed on the hypervisor hosts."
+msgstr "这个步骤仅适用于安装了XenServer的hypervisor主机。"
+
+# d212ae279e594ea4a9b82dde3342f509
+#: ../../installation.rst:358
+msgid ""
+"Before setting up the Management Server, download vhd-util from `vhd-util "
+"<http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_."
+msgstr "在设置管理服务器前，下载 `vhd-util<http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_."
+
+# d4c4d9a792ec46bbacc984b02fa8dd22
+#: ../../installation.rst:361
+msgid ""
+"If the Management Server is RHEL or CentOS, copy vhd-util to `/usr/share"
+"/cloudstack-common/scripts/vm/hypervisor/xenserver`"
+msgstr "如果管理服务器是RHEL或者是CentOS，复制 vhd-util到`/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver`"
+
+# dcbc45d4730e482291fc719820a2e074
+#: ../../installation.rst:364
+msgid ""
+"If the Management Server is Ubuntu, copy vhd-util to `/usr/share/cloudstack-"
+"common/scripts/vm/hypervisor/xenserver`"
+msgstr "如果管理服务器是Ubuntu系统，复制vhd-util到`/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver`"
+
+# 3d000babaab44343b6203aec8596c5e6
+#: ../../installation.rst:369
+msgid "Install the database server"
+msgstr "安装数据库服务器"
+
+# f88a65610c204fafb3a2491316300137
+#: ../../installation.rst:371
+msgid ""
+"The CloudStack management server uses a MySQL database server to store its "
+"data. When you are installing the management server on a single node, you "
+"can install the MySQL server locally. For an installation that has multiple "
+"management server nodes, we assume the MySQL database also runs on a "
+"separate node."
+msgstr "CloudStack管理服务器使用一个MySQL数据库服务来存储自身数据。当你在一个独立的节点上安装管理服务器，你可以在本地安装MySQL服务器。对于在多重节点上安装，我们假设MySQL也运行在一个已经分隔开的节点上。"
+
+# fde5a5bd27424be7b529dc9a04291fc4
+#: ../../installation.rst:377
+msgid ""
+"CloudStack has been tested with MySQL 5.1 and 5.5. These versions are "
+"included in RHEL/CentOS and Ubuntu."
+msgstr "CloudStack已经在MySQL 5.1和5.5上被测试过。这些平台版本包含RHEL/CentOS和Ubuntu."
+
+# bdd992ca70fe4dff8367622ecd75f731
+#: ../../installation.rst:382
+msgid "Install the Database on the Management Server Node"
+msgstr "在管理服务器节点上安装数据库。"
+
+# 7f0fe4eec48240e28d602ad0745156b6
+#: ../../installation.rst:384
+msgid ""
+"This section describes how to install MySQL on the same machine with the "
+"Management Server. This technique is intended for a simple deployment that "
+"has a single Management Server node. If you have a multi-node Management "
+"Server deployment, you will typically use a separate node for MySQL. See "
+":ref:`install-database-on-separate-node`."
+msgstr "本节将会介绍如何将MySQL与管理服务器安装在同一台机器上. 这种方法是针对只有一个管理服务器的部署. 如果你部署了多台管理服务器节点, 你最好使用单独的一个节点来部署MySQL数据库. 参阅 :ref:`install-database-on-separate-node`."
+
+# 9da9fd0e78644a6f90cc13c5f7629147
+#: ../../installation.rst:390
+msgid "Install MySQL from the package repository of your distribution:"
+msgstr "使用你部署的软件仓库安装MySQL：."
+
+# 423988f38bfe4c029c64f905b8083873
+#: ../../installation.rst:400
+msgid ""
+"Open the MySQL configuration file. The configuration file is ``/etc/my.cnf``"
+" or ``/etc/mysql/my.cnf``, depending on your OS."
+msgstr "编辑MySQL的配置文件 。根据你操作系统的不同, 文件是/etc/my.cnf 或者/etc/mysql/my.cnf."
+
+# 69b009a70f9d489d86c665723f326565
+#: ../../installation.rst:403
+msgid "Insert the following lines in the [mysqld] section."
+msgstr "在[mysqld]区域插入下列行。"
+
+# 7c240032679b427986b382f408c4d867
+#: ../../installation.rst:405
+msgid ""
+"You can put these lines below the datadir line. The max\\_connections "
+"parameter should be set to 350 multiplied by the number of Management "
+"Servers you are deploying. This example assumes one Management Server."
+msgstr "你可以把这几行放在datadir行下. 参数max_connections应该设置为 350 乘以你部署管理服务器节点的个数. 这个示例假定你只部署了一台管理服务器."
+
+# 462e4aec3ff248dfa67155a3766e4759
+#: ../../installation.rst:411
+msgid ""
+"On Ubuntu, you can also create a file `/etc/mysql/conf.d/cloudstack.cnf` and"
+" add these directives there. Don't forget to add [mysqld] on the first line "
+"of the file."
+msgstr "在Ubuntu上，你也可以创建 /etc/mysql/conf.d/cloudstack.cnf文件并在此添加如下目录。不要忘记在文件第一行加[mysqld]。"
+
+# 64fd4122c8bd4334bb74dcb6e90272b9
+# 84765c6978a447f7b510dc7a3e4444bb
+#: ../../installation.rst:423 ../../installation.rst:617
+msgid "Start or restart MySQL to put the new configuration into effect."
+msgstr "启动或者重启MySQL使新的配置生效。"
+
+# 724040c0968d4dff95c8d7be03f4017e
+# 8c620289a7ff44589e7c44bc264acaf1
+#: ../../installation.rst:425 ../../installation.rst:619
+msgid ""
+"On RHEL/CentOS, MySQL doesn't automatically start after installation. Start "
+"it manually."
+msgstr "在RHEL/CentOS上，MySQL在安装完后不会自动启动。手工启动它。"
+
+# caa5b484b77844f0bd0826937ee49bc6
+# 6a9edbbfcf6d4c12a0b49cfb8a7417a2
+#: ../../installation.rst:432 ../../installation.rst:626
+msgid "On Ubuntu, restart MySQL."
+msgstr "在Ubuntu上，重启MySQL."
+
+# f61c8b0000f1424c9f2c13630125db20
+# 81d86aeab96741c4854e00bd76a9d650
+#: ../../installation.rst:438 ../../installation.rst:632
+msgid "(CentOS and RHEL only; not required on Ubuntu)"
+msgstr "(仅限CentOS 和 RHEL平台，对Ubuntu不作要求）"
+
+# 49d05484300842749affe75f5a57fc78
+#: ../../installation.rst:441
+msgid ""
+"On RHEL and CentOS, MySQL does not set a root password by default. It is "
+"very strongly recommended that you set a root password as a security "
+"precaution."
+msgstr "在RHEL和CentOS上, MySQL默认并未设置root用户的密码. 强烈建议您设置超级用户密码作为安全预防措施。"
+
+# 35126d196cb44db896a7da2f35f0219c
+#: ../../installation.rst:445
+msgid ""
+"Run the following command to secure your installation. You can answer \"Y\" "
+"to all questions."
+msgstr "运行以下命令进行安全配置。你可以对所有的问题回答”Y\"。"
+
+# 4c6efd3f31564d4e8c184fa2b19e2370
+#: ../../installation.rst:452
+msgid ""
+"CloudStack can be blocked by security mechanisms, such as SELinux. Disable "
+"SELinux to ensure + that the Agent has all the required permissions."
+msgstr "CloudStack的会被安全机制阻止，例如SELinux。确保关闭SELinux 和 Agent具有所必需的权限。"
+
+# c736e2910bf746f29b59b481a266efd5
+#: ../../installation.rst:456
+msgid "Configure SELinux (RHEL and CentOS):"
+msgstr "配置SELinux(RHEL和CentOS)："
+
+# 8d44b0228538457fb684938443b8a184
+#: ../../installation.rst:458
+msgid ""
+"Check whether SELinux is installed on your machine. If not, you can skip "
+"this section."
+msgstr "检查你的机器是否安装了SELinux。如果没有，请跳过此部分。"
+
+# f4dda09e82f14c94b0380640a6a92eaa
+#: ../../installation.rst:461
+msgid ""
+"In RHEL or CentOS, SELinux is installed and enabled by default. You can "
+"verify this with:"
+msgstr "在RHEL或者CentOS中，SELinux是默认安装并启动的。你可以使用如下命令验证："
+
+# c9420ac318f6432fb6feb232be65d8cc
+#: ../../installation.rst:468
+msgid ""
+"Set the SELINUX variable in ``/etc/selinux/config`` to \"permissive\". This "
+"ensures that the permissive setting will be maintained after a system "
+"reboot."
+msgstr "在 ``/etc/selinux/config`` 中设置SELINUX变量值为 \"permissive\"。这样能确保对SELinux的设置在系统重启之后依然生效。"
+
+# 7bf236cb6e324d0b8b23ca6a50acfcdd
+#: ../../installation.rst:472
+msgid "In RHEL or CentOS:"
+msgstr "在RHEL/CentOS上:"
+
+# fe3458a445a247c18078c567d5c3c24c
+#: ../../installation.rst:478
+msgid "Change the following line"
+msgstr "查找如下行"
+
+# af316e719579454392ce08b885fa3f1c
+#: ../../installation.rst:484
+msgid "to this:"
+msgstr "修改为："
+
+# 348280635d374eeabd020521c3079beb
+#: ../../installation.rst:490
+msgid ""
+"Set SELinux to permissive starting immediately, without requiring a system "
+"reboot."
+msgstr "执行该命令无需系统重启就会将SELinux的运行模式设置为permissive。"
+
+# 65a33b90a9fc4a7b95bbf4db213365cb
+#: ../../installation.rst:497
+msgid ""
+"Set up the database. The following command creates the \"cloud\" user on the"
+" database."
+msgstr "设置数据库. 下列的命令会在数据库中创建\"cloud\"用户."
+
+# aa653b538c1649a4ab4c8182d62d2ae4
+#: ../../installation.rst:500
+msgid ""
+"In dbpassword, specify the password to be assigned to the \"cloud\" user. "
+"You can choose to provide no password although that is not recommended."
+msgstr "dbpassword，为 \"cloud\"的用户设置的密码。你也可以选择不设置密码，尽管并不推荐。"
+
+# 0fff4e85bcaa43d7a53ddf5f641899a8
+#: ../../installation.rst:504
+msgid ""
+"In deploy-as, specify the username and password of the user deploying the "
+"database. In the following command, it is assumed the root user is deploying"
+" the database and creating the \"cloud\" user."
+msgstr "deploy-as, 指定安装数据库的用户名和密码. 在下面的命令中, root用户部署了数据库并创建了cloud用户."
+
+# 6e76a4c5d00b40f9a2591a882b9cf7e3
+# 232603c49f9b470fadd4497980b040ea
+#: ../../installation.rst:509 ../../installation.rst:683
+msgid ""
+"(Optional) For encryption\\_type, use file or web to indicate the technique "
+"used to pass in the database encryption password. Default: file. See :ref"
+":`about-password-key-encryption`."
+msgstr "(可选)encryption_type, 使用file或web来告知数据库通过哪种技术对密码进行加密. 默认是file. 参考 :ref:`about-password-key-encryption`."
+
+# c484241ea1734f64b2ee605c25ff4f55
+#: ../../installation.rst:513
+msgid ""
+"(Optional) For management\\_server\\_key, substitute the default key that is"
+" used to encrypt confidential parameters in the CloudStack properties file. "
+"Default: password. It is highly recommended that you replace this with a "
+"more secure value. See :ref:`about-password-key-encryption`."
+msgstr "(可选)management_server_key，在CloudStack属性文件中使用加密的机密参数替代默认密码。默认为：password。强烈推荐您使用更安全的值替代它。参阅： :ref:`about-password-key-encryption`."
+
+# a116bdc1b4f146618c07383056276b2f
+# c84567a232924a2a93426fbde5c68e5c
+#: ../../installation.rst:519 ../../installation.rst:693
+msgid ""
+"(Optional) For database\\_key, substitute the default key that is used to "
+"encrypt confidential parameters in the CloudStack database. Default: "
+"password. It is highly recommended that you replace this with a more secure "
+"value. See :ref:`about-password-key-encryption`."
+msgstr "(可选)database_key,在CloudStack数据库中使用加密的机密参数替代默认密码。默认为：password。强烈推荐您使用更安全的值替代它。参阅： :ref:`about-password-key-encryption`."
+
+# d51435b1acbb403ea778782c88c09cd9
+# 3c2f5d31ed014299b6b2ad61d8d02606
+#: ../../installation.rst:525 ../../installation.rst:699
+msgid ""
+"(Optional) For management\\_server\\_ip, you may explicitly specify cluster "
+"management server node IP. If not specified, the local IP address will be "
+"used."
+msgstr "(可选)management_server_ip, 你可以明确的指定群集管理服务器的IP。如果不指定，默认使用本机IP。"
+
+# 8781d85265da4df69b6b1161f9981921
+# f3bfbf8b741844379f95923b4b686ba8
+#: ../../installation.rst:538 ../../installation.rst:712
+msgid ""
+"When this script is finished, you should see a message like “Successfully "
+"initialized the database.”"
+msgstr "当脚本完成后，你将会看到类似这样的信息:\"Successfully initialized the database\""
+
+# a6cf1c3f7291407581e5da12486d3a20
+#: ../../installation.rst:542
+msgid ""
+"If the script is unable to connect to the MySQL database, check the "
+"\"localhost\" loopback address in ``/etc/hosts``. It should be pointing to "
+"the IPv4 loopback address \"127.0.0.1\" and not the IPv6 loopback address "
+"``::1``. Alternatively, reconfigure MySQL to bind to the IPv6 loopback "
+"interface."
+msgstr ""
+
+# 33b221f992cd42cab21181c9205890e7
+#: ../../installation.rst:548
+msgid ""
+"If you are running the KVM hypervisor on the same machine with the "
+"Management Server, edit /etc/sudoers and add the following line:"
+msgstr "如果你的KVM Hypervisor和管理服务器在同一台的机器上，编辑 /etc/sudoers并添加以下行："
+
+# 52aa8c1267b94037ad3d9615231fbca4
+#: ../../installation.rst:555
+msgid ""
+"Now that the database is set up, you can finish configuring the OS for the "
+"Management Server. This command will set up iptables, sudoers, and start the"
+" Management Server."
+msgstr "现在数据库已经设置好, 你可以完成管理服务器的设置. 这个命令将会设置iptables, sudoers并启动管理服务."
+
+# 08f36fb116e642ba89ca4e2d95dec848
+#: ../../installation.rst:563
+msgid ""
+"You should see the message “CloudStack Management Server setup is done.”"
+msgstr "你应该看到这样的信息: “Management Server setup is done.”"
+
+# 7d221b73028543c9a2b47b117237997f
+#: ../../installation.rst:570
+msgid "Install the Database on a Separate Node"
+msgstr "在单独的节点上安装数据库。"
+
+# eb04195ea5644ab59b8df4dcd32f8d0b
+#: ../../installation.rst:572
+msgid ""
+"This section describes how to install MySQL on a standalone machine, "
+"separate from the Management Server. This technique is intended for a "
+"deployment that includes several Management Server nodes. If you have a "
+"single-node Management Server deployment, you will typically use the same "
+"node for MySQL. See `“Install the Database on the Management Server Node” "
+"<#install-the-database-on-the-management-server-node>`_."
+msgstr ""
+
+# cb57860521b44243b4452bd9da079744
+#: ../../installation.rst:580
+msgid ""
+"The management server doesn't require a specific distribution for the MySQL "
+"node. You can use a distribution or Operating System of your choice. Using "
+"the same distribution as the management server is recommended, but not "
+"required. See `“Management Server, Database, and Storage System "
+"Requirements” <#management-server-database-and-storage-system-"
+"requirements>`_."
+msgstr "管理服务器不要求为MySQL节点指定特定的分支。你可以选择使用任何一个操作系统的分支。建议与管理服务器使用相同的分支，但不做强制要求。参阅 `“管理服务器, 数据库和存储系统要求” <#management-server-database-and-storage-system-requirements>`_."
+
+# 49b51b3e92d447188645fdf39e28feab
+#: ../../installation.rst:586
+msgid "Install MySQL from the package repository from your distribution:"
+msgstr "使用你部署的软件仓库安装MySQL：."
+
+# ae7d0f661888443dbeda2f242e3e4bc3
+#: ../../installation.rst:596
+msgid ""
+"Edit the MySQL configuration (/etc/my.cnf or /etc/mysql/my.cnf, depending on"
+" your OS) and insert the following lines in the [mysqld] section. You can "
+"put these lines below the datadir line. The max\\_connections parameter "
+"should be set to 350 multiplied by the number of Management Servers you are "
+"deploying. This example assumes two Management Servers."
+msgstr "编辑MySQL的配置文件 (根据你操作系统的不同, 文件为/etc/my.cnf 或者/etc/mysql/my.cnf) 并在 [mysqld] 章节插入下面几行. 你可以把这几行放在datadir行下. 参数max_connections应该设置为 350 乘以你部署管理服务器节点的个数. 这个示例假定你只部署了一台管理服务器."
+
+# ea07aaf2f2094827919c3f7f9d1c8115
+#: ../../installation.rst:604
+msgid ""
+"On Ubuntu, you can also create /etc/mysql/conf.d/cloudstack.cnf file and add"
+" these directives there. Don't forget to add [mysqld] on the first line of "
+"the file."
+msgstr "在Ubuntu上，你也可以创建 /etc/mysql/conf.d/cloudstack.cnf文件并在此添加如下目录。不要忘记在文件第一行加[mysqld]。"
+
+# 181c50670cde4667bbbf5930fb3c854b
+#: ../../installation.rst:635
+msgid ""
+"On RHEL and CentOS, MySQL does not set a root password by default. It is "
+"very strongly recommended that you set a root password as a security "
+"precaution. Run the following command to secure your installation. You can "
+"answer \"Y\" to all questions except \"Disallow root login remotely?\". "
+"Remote root login is required to set up the databases."
+msgstr "在RHEL 和 CentOS上，MySQL默认并未设置root用户的密码。强烈建议您设置超级用户密码作为安全预防措施。运行以下命令进行安全配置。你可以对所有问题回答\"Y\"， \"Disallow root login remotely?\"问题除外。设置数据库需要root远程登录。"
+
+# 278c2f9ed64442a580cb6c385b7793d6
+#: ../../installation.rst:645
+msgid ""
+"If a firewall is present on the system, open TCP port 3306 so external MySQL"
+" connections can be established."
+msgstr "如果系统中存在防火墙，打开TCP的3306端口用于建立MySQL连接。"
+
+# 16ce3ea613174067b6edf85fa82a0323
+#: ../../installation.rst:648
+msgid ""
+"On Ubuntu, UFW is the default firewall. Open the port with this command:"
+msgstr "在Ubuntu上，默认防火墙是UFW。用以下命令打开端口："
+
+# 11cda3fbfc934a199874ab207473898e
+#: ../../installation.rst:655
+msgid "On RHEL/CentOS:"
+msgstr "在RHEL/CentOS上:"
+
+# f0b20f4dbb6849c0963c4affbbba6ae9
+#: ../../installation.rst:657
+msgid ""
+"Edit the /etc/sysconfig/iptables file and add the following line at the "
+"beginning of the INPUT chain."
+msgstr "编辑/etc/sysconfig/iptables文件并在INPUT链中添加下列行。"
+
+# 0bf0dca831b0441fa3a376a3bcccfb78
+#: ../../installation.rst:664
+msgid "Now reload the iptables rules."
+msgstr "现在重新加载iptables规则。"
+
+# 6513db9f42b8495ca96090e285daa673
+#: ../../installation.rst:670
+msgid "Return to the root shell on your first Management Server."
+msgstr "返回到第一个管理服务器root用户的shell中。"
+
+# a2317a3c06f342058c12a67eb8b69383
+#: ../../installation.rst:672
+msgid ""
+"Set up the database. The following command creates the cloud user on the "
+"database."
+msgstr "设置数据库。按照如下命令在数据库中创建cloud用户。"
+
+# 5430f655d0e244fe8921c41ed892882f
+#: ../../installation.rst:675
+msgid ""
+"In dbpassword, specify the password to be assigned to the cloud user. You "
+"can choose to provide no password."
+msgstr "dbpassword，为 \"cloud\"的用户设置的密码。你也可以选择不设置密码。"
+
+# b10e601516ba4ba8ad5cf0a277d811e2
+#: ../../installation.rst:678
+msgid ""
+"In deploy-as, specify the username and password of the user deploying the "
+"database. In the following command, it is assumed the root user is deploying"
+" the database and creating the cloud user."
+msgstr "deploy-as, 指定安装数据库的用户名和密码. 在下面的命令中, root用户部署了数据库并创建了cloud用户."
+
+# 9e82de1fc39e465b8b0b66c224c19483
+#: ../../installation.rst:687
+msgid ""
+"(Optional) For management\\_server\\_key, substitute the default key that is"
+" used to encrypt confidential parameters in the CloudStack properties file. "
+"Default: password. It is highly recommended that you replace this with a "
+"more secure value. See About Password and Key Encryption."
+msgstr "(可选)management_server_key，在CloudStack属性文件中使用加密的机密参数替代默认密码。默认为：password。强烈推荐您使用更安全的值替代它。参阅关于密码和密钥加密。"
+
+# 13de6a8d8fe341028c60b6f04beb31b0
+#: ../../installation.rst:719
+msgid "About Password and Key Encryption"
+msgstr "关于密码和密钥加密"
+
+# 45fbacb318674ad8b9217f0ca90da414
+#: ../../installation.rst:721
+msgid ""
+"CloudStack stores several sensitive passwords and secret keys that are used "
+"to provide security. These values are always automatically encrypted:"
+msgstr "CloudStack存储一些敏感密码和密钥用于提供安全保证。这些值总是自动被加密。"
+
+# 6ad55d0faad740589f3152b45a9670d1
+#: ../../installation.rst:725
+msgid "Database secret key"
+msgstr "数据库密钥"
+
+# e25d10cf49454d89a0301335e4aa2c93
+#: ../../installation.rst:727
+msgid "Database password"
+msgstr "数据库密码"
+
+# c73f9cf443a745509d548cecae66c1fd
+#: ../../installation.rst:729
+msgid "SSH keys"
+msgstr "SSH密钥"
+
+# d042f272678f4ca3a91d02bf058c6ffc
+#: ../../installation.rst:731
+msgid "Compute node root password"
+msgstr "计算节点root密码"
+
+# d70e7fde8c6e4353a2e5a31b6b15a0ff
+#: ../../installation.rst:733
+msgid "VPN password"
+msgstr "VPN密码"
+
+# a91d0ab04c504168a4f86e9e1cd8f588
+#: ../../installation.rst:735
+msgid "User API secret key"
+msgstr "用户API密钥"
+
+# 7c756f6f0e374ae9a1d2b96c1de9c2a0
+#: ../../installation.rst:737
+msgid "VNC password"
+msgstr "VNC密码"
+
+# 3ced5a13cc124b328c89685af71bddfc
+#: ../../installation.rst:739
+msgid ""
+"CloudStack uses the Java Simplified Encryption (JASYPT) library. The data "
+"values are encrypted and decrypted using a database secret key, which is "
+"stored in one of CloudStack’s internal properties files along with the "
+"database password. The other encrypted values listed above, such as SSH "
+"keys, are in the CloudStack internal database."
+msgstr "CloudStack使用java简单的加密库（JASYPT）。数据值加密和解密通过使用一个存储在一个CloudStack带有数据库密码的内部属性文件中的密钥。上述列出的其他加密的值，例如SSH密钥，也在CloudStack内部数据库中。"
+
+# 024c2c3bfb28412392653a45cfe7debe
+#: ../../installation.rst:745
+msgid ""
+"Of course, the database secret key itself can not be stored in the open – it"
+" must be encrypted. How then does CloudStack read it? A second secret key "
+"must be provided from an external source during Management Server startup. "
+"This key can be provided in one of two ways: loaded from a file or provided "
+"by the CloudStack administrator. The CloudStack database has a configuration"
+" setting that lets it know which of these methods will be used. If the "
+"encryption type is set to \"file,\" the key must be in a file in a known "
+"location. If the encryption type is set to \"web,\" the administrator runs "
+"the utility com.cloud.utils.crypt.EncryptionSecretKeySender, which relays "
+"the key to the Management Server over a known port."
+msgstr "当然，数据库密钥本身不是公开存储的-它必须被加密。那么，CloudStack如何阅读它呢？从外部源启动管理服务时必须提供第二个密钥。这个密钥可以提供两种方式中的一种：从文件加载或者由CloudStack的管理员提供。CloudStack数据库中都有一个配置设置使它知道这些方法将被调用。如果加密类型设置为 \"file,\" 密钥 必须存在于文件的已知位置中。如果加密类型设置为 \"web,\" 管理员运行 com.cloud.utils.crypt.EncryptionSecretKeySender工具，which relays the key to the Management Server over a known port."
+
+# 6a3a9b0c66e04e64b4c6d34a4a17bb3b
+#: ../../installation.rst:757
+msgid ""
+"The encryption type, database secret key, and Management Server secret key "
+"are set during CloudStack installation. They are all parameters to the "
+"CloudStack database setup script (cloudstack-setup-databases). The default "
+"values are file, password, and password. It is, of course, highly "
+"recommended that you change these to more secure keys."
+msgstr "加密类型，数据库密钥和管理服务器密钥在CloudStack初始化的过程中设置。它们全部是CloudStack数据库设置脚本的参数（cloud-setup-databases).默认值是file,password和password。当然，强烈建议你修改这些密钥。"
+
+# 511008e5d7e640eea756268a06c19eb0
+#: ../../installation.rst:765
+msgid "Changing the Default Password Encryption"
+msgstr "更改默认密码加密"
+
+# ca4f4a81740849cdb9d61f0a33af6605
+#: ../../installation.rst:767
+msgid ""
+"Passwords are encoded when creating or updating users. CloudStack allows you"
+" to determine the default encoding and authentication mechanism for admin "
+"and user logins. Two new configurable lists have been "
+"introduced—userPasswordEncoders and userAuthenticators. userPasswordEncoders"
+" allows you to configure the order of preference for encoding passwords, "
+"whereas userAuthenticators allows you to configure the order in which "
+"authentication schemes are invoked to validate user passwords."
+msgstr "创建或更新用户密码会被加密。CloudStack允许你定义管理员和用户登录的默认密码和授权机制。这两种配置列表都已经介绍过了—userPasswordEncoders 和 userAuthenticators。userPasswordEncoders允许你配置优先顺序进行密码编码，而userAuthenticators允许你配置的调用身份验证方案来验证用户密码。"
+
+# 78d6cb8f6ce74a82accf0327cbc8375d
+#: ../../installation.rst:776
+msgid ""
+"Additionally, the plain text user authenticator has been modified not to "
+"convert supplied passwords to their md5 sums before checking them with the "
+"database entries. It performs a simple string comparison between retrieved "
+"and supplied login passwords instead of comparing the retrieved md5 hash of "
+"the stored password against the supplied md5 hash of the password because "
+"clients no longer hash the password. The following method determines what "
+"encoding scheme is used to encode the password supplied during user creation"
+" or modification."
+msgstr "此外，纯文本的用户认证方已经修改为:在检查数据库记录之前，不对获取的密码进行md5值校验。仅对提供的登录密码执行检索。 由于客户端不再对密码进行散列（hash），所以不再对比存储的密码散列值和获取的密码的哈希值。下面的方法决定用于用户创建或修改过程中提供的密码进行编码时使用什么编码方案。"
+
+# f6b78ffccd494c30be0c5efac1ab44a9
+#: ../../installation.rst:785
+msgid ""
+"When a new user is created, the user password is encoded by using the first "
+"valid encoder loaded as per the sequence specified in the "
+"``UserPasswordEncoders`` property in the ``ComponentContext.xml`` or "
+"``nonossComponentContext.xml`` files. The order of authentication schemes is"
+" determined by the ``UserAuthenticators`` property in the same files. If "
+"Non-OSS components, such as VMware environments, are to be deployed, modify "
+"the ``UserPasswordEncoders`` and ``UserAuthenticators`` lists in the "
+"``nonossComponentContext.xml`` file, for OSS environments, such as XenServer"
+" or KVM, modify the ``ComponentContext.xml`` file. It is recommended to make"
+" uniform changes across both the files. When a new authenticator or encoder "
+"is added, you can add them to this list. While doing so, ensure that the new"
+" authenticator or encoder is specified as a bean in both these files. The "
+"administrator can change the ordering of both these properties as preferred "
+"to change the order of schemes. Modify the following list properties "
+"available in ``client/tomcatconf/nonossComponentContext.xml.in`` or "
+"``client/tomcatconf/componentContext.xml.in`` as applicable, to the desired "
+"order:"
+msgstr "在创建新用户时,用户密码是按照``ComponentContext.xml`` 或 ``nonossComponentContext.xml`` 文件中 ``UserPasswordEncoders`` 属性中指定的顺序对有效的编码器进行编码。该文件中的 ``UserAuthenticators`` 属性也指定了认证方案的顺序。如果使用了Non-OSS（非开源软件）组件，例如要部署VMware环境，修改 ``nonossComponentContext.xml`` 文件中的 ``UserPasswordEncoders`` 和 ``UserAuthenticators`` 列表。针对OSS（开源软件），例如XenServer和KVM，则修改 ``ComponentContext.xml`` 文件。建议对这两个文件做统一的修改。当添加新的认证器和解释器时，你可以添加至该列表。做的过程中，确保已经在这些文件中指定认证器和解释器。管理员可以更改这两个属性的排序和计划作为首选的排列顺序。如果适用的话，在 ``client/tomcatconf/nonossComponentContext.xml.in`` 或 ``client/tomcatconf/componentContext.xml.in`` 文件中修改下面的列表中可用的属性的顺序："
+
+# 2fcac5693d444b38b51c1e5e74dc7110
+#: ../../installation.rst:823
+msgid ""
+"In the above default ordering, SHA256Salt is used first for "
+"``UserPasswordEncoders``. If the module is found and encoding returns a "
+"valid value, the encoded password is stored in the user table's password "
+"column. If it fails for any reason, the MD5UserAuthenticator will be tried "
+"next, and the order continues. For ``UserAuthenticators``, SHA256Salt "
+"authentication is tried first. If it succeeds, the user is logged into the "
+"Management server. If it fails, md5 is tried next, and attempts continues "
+"until any of them succeeds and the user logs in . If none of them works, the"
+" user is returned an invalid credential message."
+msgstr "在上述排序中，SHA256Salt首次使用 ``UserPasswordEncoders``.如果这个模块已经找到并且编码后返回一个有效值，编码密码存储在用户表密码列中。如果因某些原因失败，接下来将尝试MD5UserAuthenticator，并按照规定继续。对于 ``UserAuthenticators``， SHA256Salt授权首先被使用。如果成功，用户将登陆进入管理服务器。如果失败，下一步将尝试md5,并继续尝试直到成功。如果他们没起作用，用户将返回一个无效的确认信息。"
+
+# 707a625494ae450a987664e845dc1092
+#: ../../installation.rst:837
+msgid ""
+"CloudStack needs a place to keep primary and secondary storage (see Cloud "
+"Infrastructure Overview). Both of these can be NFS shares. This section "
+"tells how to set up the NFS shares before adding the storage to CloudStack."
+msgstr "CloudStack需要主存储和辅助存储空间(参阅 云基础设施概述)。两种存储都可以是NFS共享存储。这节描述如何在CloudStack中添加存储。"
+
+# 0ffaec4550964c9b81b5988488ee74fa
+#: ../../installation.rst:843
+msgid ""
+"NFS is not the only option for primary or secondary storage. For example, "
+"you may use Ceph RBD, GlusterFS, iSCSI, and others. The choice of storage "
+"system will depend on the choice of hypervisor and whether you are dealing "
+"with primary or secondary storage."
+msgstr "NFS并不是主存储和二期存储的唯一选择。例如，您可以使用Ceph RBD、GlusterFS、iSCSI等其它存储。存储系统的选择依赖于虚拟化平台类型以及是用于主存储还是二级存储。"
+
+# d636505b4eb949d49b6786e451926f86
+#: ../../installation.rst:848
+msgid "The requirements for primary and secondary storage are described in:"
+msgstr "主存储和辅助存储的需求描述："
+
+# 4d264009140f4e119313dbaaf55114a5
+#: ../../installation.rst:850
+msgid ""
+"`“About Primary Storage” "
+"<http://docs.cloudstack.apache.org/en/latest/concepts.html#about-primary-"
+"storage>`_"
+msgstr "`“关于主存储” <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-primary-storage>`_"
+
+# ed5e2e20e6ca432b95c1e7e204bd4f6a
+#: ../../installation.rst:853
+msgid ""
+"`“About Secondary Storage” "
+"<http://docs.cloudstack.apache.org/en/latest/concepts.html#about-secondary-"
+"storage>`_"
+msgstr "`“关于辅助存储” <http://docs.cloudstack.apache.org/en/latest/concepts.html#about-secondary-storage>`_。"
+
+# 91c1900704fd4d91b018dd2e441ce1a5
+#: ../../installation.rst:856
+msgid ""
+"A production installation typically uses a separate NFS server. See "
+":ref:`using-a-separage-nfs-server`."
+msgstr "典型地安装使用一个独立的NFS 服务器。参阅 :ref:`using-a-separage-nfs-server`."
+
+# 54dae30e742c45e0bab2066517190be8
+#: ../../installation.rst:859
+msgid ""
+"You can also use the Management Server node as the NFS server. This is more "
+"typical of a trial installation, but is technically possible in a larger "
+"deployment. See :ref:`using-the-management-server-as-the-nfs-server`."
+msgstr "你也可以使用管理服务节点作为NFS服务器。这是更为典型的安装，部署更大的环境在技术上是可行的。参阅 :ref:`using-the-management-server-as-the-nfs-server`."
+
+# feabaaeb53214becbece68200ee0ca7f
+#: ../../installation.rst:867
+msgid "Using a Separate NFS Server"
+msgstr "使用独立的NFS服务器"
+
+# aeb8dd69baf144c4a1df1c6f07faaec9
+#: ../../installation.rst:869
+msgid ""
+"This section tells how to set up NFS shares for secondary and (optionally) "
+"primary storage on an NFS server running on a separate node from the "
+"Management Server."
+msgstr "这一节描述如何在存储系统中为辅助存储和主存储(可选)设置NFS共享，它运行在一个与管理控制服务器不同的独立节点。"
+
+# f25edd950f514c5fb151e7877de7ab99
+# d24aef1ed1ac409589504fe7ef5cdb29
+#: ../../installation.rst:873 ../../installation.rst:934
+msgid ""
+"The exact commands for the following steps may vary depending on your "
+"operating system version."
+msgstr "以下步骤的命令取决于你的操作系统版本。"
+
+# bff14968bd214c0c895eda46fc9c45ff
+#: ../../installation.rst:877
+msgid ""
+"(KVM only) Ensure that no volume is already mounted at your NFS mount point."
+msgstr "(仅KVM)确保没有任何卷被挂载到你的NFS挂载点上。"
+
+# bd33e779304a4c5a81b690637431ef5b
+#: ../../installation.rst:879
+msgid ""
+"On the storage server, create an NFS share for secondary storage and, if you"
+" are using NFS for primary storage as well, create a second NFS share. For "
+"example:"
+msgstr "在存储服务器上，创建一个用于辅助存储的NFS共享，如果同时也用于主存储，则创建2个NFS共享，例如："
+
+# 0d4f698defbb458b8ffdb5ff3dd584e0
+# ce9561250f074471a254c55f6d07c6c9
+#: ../../installation.rst:888 ../../installation.rst:951
+msgid ""
+"To configure the new directories as NFS exports, edit /etc/exports. Export "
+"the NFS share(s) with rw,async,no\\_root\\_squash,no\\_subtree\\_check. For "
+"example:"
+msgstr "配置新的目录作为NFS输出，编辑/etc/exports。使用 rw,async,no_root_squash,no_subtree_check 输出NFS共享目录。例如："
+
+# 01cfe9dc640a44f6b99cb2c58b04c173
+# 98487e7ffdaf4dac9f71cb0719b6c684
+#: ../../installation.rst:896 ../../installation.rst:959
+msgid "Insert the following line."
+msgstr "插入如下行。"
+
+# 94ecddfb2f174696aa885e7caf1c7f5f
+# 01225b1fb90847ec8b8b089ef57ef205
+#: ../../installation.rst:902 ../../installation.rst:965
+msgid "Export the /export directory."
+msgstr "输出/export目录。"
+
+# ecf40e05b66948e587495e8c9b46f371
+#: ../../installation.rst:908
+msgid ""
+"On the management server, create a mount point for secondary storage. For "
+"example:"
+msgstr "在管理服务器上，创建一个辅助存储的挂载点。例如："
+
+# 95a0283dd26a46928e258568441e3d29
+#: ../../installation.rst:915
+msgid ""
+"Mount the secondary storage on your Management Server. Replace the example "
+"NFS server name and NFS share paths below with your own."
+msgstr "在你的管理服务器上挂载辅助存储。更换下面示例中的NFS服务器名称和NFS共享路径为你自己的。"
+
+# 98dfcbe6dbc44fc39d0d5c0f91a45503
+#: ../../installation.rst:926
+msgid "Using the Management Server as the NFS Server"
+msgstr "使用管理服务器作为NFS服务器"
+
+# a4b1c2a1b2bd4729afc842b2675effa2
+#: ../../installation.rst:928
+msgid ""
+"This section tells how to set up NFS shares for primary and secondary "
+"storage on the same node with the Management Server. This is more typical of"
+" a trial installation, but is technically possible in a larger deployment. "
+"It is assumed that you will have less than 16TB of storage on the host."
+msgstr "本节讲述如何在管理服务器节点上设置主存储和辅助存储的NFS共享目录。这是典型的安装部署，但是部署更大的环境在技术上可行的。假设你的主机上拥有少于16TB的存储空间。"
+
+# 640cef0f4b154773ae29c9366515551d
+#: ../../installation.rst:937
+msgid "On RHEL/CentOS systems, you'll need to install the nfs-utils package:"
+msgstr "在 RHEL/CentOS系统上，你需要安装 nfs-utils包："
+
+# e152db6773384cfb9b5fa8d9849cd959
+#: ../../installation.rst:943
+msgid ""
+"On the Management Server host, create two directories that you will use for "
+"primary and secondary storage. For example:"
+msgstr "在管理服务器主机上，创建两个目录用作主存储和辅助存储。例如："
+
+# fad7bb568f4f4071b3685bb833739ef0
+#: ../../installation.rst:971
+msgid "Edit the /etc/sysconfig/nfs file."
+msgstr "编辑/etc/sysconfig/nfs文件。"
+
+# 19d379a8922248c4bb8e975ab8238b30
+#: ../../installation.rst:977
+msgid "Uncomment the following lines:"
+msgstr "取消如下行的注释："
+
+# d39f9b7efd104412bb59b14b784ea816
+#: ../../installation.rst:988
+msgid "Edit the /etc/sysconfig/iptables file."
+msgstr "编辑 /etc/sysconfig/iptables文件。"
+
+# 0c25a4130a4f43aabbf389c386a783c5
+#: ../../installation.rst:994
+msgid ""
+"Add the following lines at the beginning of the INPUT chain, where <NETWORK>"
+" is the network that you'll be using:"
+msgstr "在INPUT链开始处添加如下行， <NETWORK>处为你正在使用的网络："
+
+# 918152dcb1464ec3aa11d25e4df65ac0
+#: ../../installation.rst:1011
+msgid "Run the following commands:"
+msgstr "运行如下命令："
+
+# 8d7934cc7a674dc19677d0cca7b03f94
+#: ../../installation.rst:1018
+msgid ""
+"If NFS v4 communication is used between client and server, add your domain "
+"to /etc/idmapd.conf on both the hypervisor host and Management Server."
+msgstr "如果客户端和服务器之间使用NFS v4进行通讯，在hypervisor主机和管理服务器上的/etc/idmapd.conf文件中添加你的域名。"
+
+# 553ce0f07b7b4689b7b85036357ca826
+#: ../../installation.rst:1026
+msgid ""
+"Remove the character # from the beginning of the Domain line in idmapd.conf "
+"and replace the value in the file with your own domain. In the example "
+"below, the domain is company.com."
+msgstr "从idmapd.conf文件中的Domain开始行移除字符#，并替代文件中的该值为你自己的域名。在下面的示例中，域名为company.com."
+
+# 340dd6777da046a397391290dfe94ebb
+#: ../../installation.rst:1034
+msgid "Reboot the Management Server host."
+msgstr "重启管理服务器主机。"
+
+# 9b857a533abc42eea805251524f28b97
+#: ../../installation.rst:1036
+msgid ""
+"Two NFS shares called /export/primary and /export/secondary are now set up."
+msgstr "两个NFS共享 /export/primary和 /export/secondary已经建立。"
+
+# 0cf24cf59b9f4a5dbbdb2c51c7775ad5
+#: ../../installation.rst:1039
+msgid ""
+"It is recommended that you test to be sure the previous steps have been "
+"successful."
+msgstr "强烈建议您测试以确保之前的步骤已经成功。"
+
+# cbaa4d9e49e74255b3290e9820d55ef3
+#: ../../installation.rst:1042
+msgid "Log in to the hypervisor host."
+msgstr "登陆hypervisor主机。"
+
+# 30e95a69d0a94a719e40f41b7a0bd06f
+#: ../../installation.rst:1044
+msgid ""
+"Be sure NFS and rpcbind are running. The commands might be different "
+"depending on your OS. For example:"
+msgstr "确定NFS和rpcbind正在运行。具体命令可能因您的操作系统而不同。例如："
+
+# eef0133ebeee4897a60b1e510c32b865
+#: ../../installation.rst:1055
+msgid ""
+"Log back in to the hypervisor host and try to mount the /export directories."
+" For example, substitute your own management server name:"
+msgstr "重新登录到hypervisor主机并尝试挂载/export目录。例如，替代你自己的管理服务器名称："
+
+# 945ffae66da941eea53781a93218bc1c
+#: ../../installation.rst:1070
+msgid "Prepare and Start Additional Management Servers"
+msgstr "准备和启动额外的管理服务器。"
+
+# d30a2d1b35064949905881c761a8c32f
+#: ../../installation.rst:1072
+msgid ""
+"For your second and subsequent Management Servers, you will install the "
+"Management Server software, connect it to the database, and set up the OS "
+"for the Management Server."
+msgstr "在你的次级以及以后的管理服务器上，你将安装管理服务器软件，连接到数据库，并启动管理服务器的操作系统。"
+
+# 386574bc8a1942f1a013e2260e7ec892
+#: ../../installation.rst:1076
+msgid ""
+"Perform the steps in `“Prepare the Operating System” <#prepare-the-"
+"operating-system>`_ and `“Building RPMs from Source” "
+"<building_from_source.html#building-rpms-from-source>`_ or `“Building DEB "
+"packages” <building_from_source.html#building-deb-packages>`_ as "
+"appropriate."
+msgstr "执行这些步骤 `“准备操作系统” <#prepare-the-operating-system>`_ 和 `“从源码编译RPM包” <building_from_source.html#building-rpms-from-source>`_ 或 `“编译DEB包” <building_from_source.html#building-deb-packages>`_ 视情况而定."
+
+# 9516fb7c54fc446ab76267a90611e209
+#: ../../installation.rst:1082
+msgid ""
+"This step is required only for installations where XenServer is installed on"
+" the hypervisor hosts."
+msgstr "这个步骤仅适用于安装了XenServer的hypervisor主机。"
+
+# 60bd480d13124c16b4c8774b8abd5439
+#: ../../installation.rst:1085
+msgid ""
+"Download vhd-util from `vhd-util "
+"<http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_"
+msgstr "下载 `vhd-util <http://download.cloud.com.s3.amazonaws.com/tools/vhd-util>`_"
+
+# 3b0ff1adaf804ec4b60b43307747e306
+#: ../../installation.rst:1088
+msgid ""
+"Copy vhd-util to /usr/share/cloudstack-"
+"common/scripts/vm/hypervisor/xenserver."
+msgstr "复制vhd-util到/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver目录下。"
+
+# 7a0ee162adde4c378073eeafb4a655f2
+#: ../../installation.rst:1091
+msgid "Ensure that necessary services are started and set to start on boot."
+msgstr "确保必要的服务已经启动并设置为开机启动。"
+
+# 24f30a5c2b9347fabde885434d2e78ed
+#: ../../installation.rst:1100
+msgid ""
+"Configure the database client. Note the absence of the --deploy-as argument "
+"in this case. (For more details about the arguments to this command, see "
+":ref:`install-database-on-separate-node`.)"
+msgstr "配置数据库客户端。注意不使用 --deploy-as 参数在这种情况下。 (关于该命令参数更详细的信息, 参阅 :ref:`install-database-on-separate-node`.)"
+
+# 23d438dc604d4fd8a118a19e36271c4c
+#: ../../installation.rst:1108
+msgid "Configure the OS and start the Management Server:"
+msgstr "配置操作系统，并启动管理服务："
+
+# fdcd15f0de9849368878cc14f5725df2
+#: ../../installation.rst:1114
+msgid "The Management Server on this node should now be running."
+msgstr "管理服务应该运行在这个节点上。"
+
+# 460f1039702f42858ad204d933e5758a
+#: ../../installation.rst:1116
+msgid "Repeat these steps on each additional Management Server."
+msgstr "在每个额外的管理服务器上重复这些步骤。"
+
+# c73ab983e4b14d3faa16deaaf4ab7520
+#: ../../installation.rst:1118
+msgid ""
+"Be sure to configure a load balancer for the Management Servers. See "
+"`“Management Server Load Balancing” "
+"<http://docs.cloudstack.apache.org/en/latest/administration_guide.html?highlight=management%20server%20load"
+"#management-server-load-balancing>`_."
+msgstr "确保为管理服务器配置负载均衡。参阅： `“管理服务器负载均衡\" <http://docs.cloudstack.apache.org/en/latest/administration_guide.html?highlight=management%20server%20load#management-server-load-balancing>`_."
+
+# 85b606d2b0044935b6e9fd3b1af045b3
+#: ../../installation.rst:1126
+msgid ""
+"Secondary storage must be seeded with a template that is used for CloudStack"
+" system VMs."
+msgstr "辅助存储必须应用一个使用于生成CloudStack中虚拟机系统的模板。"
+
+# 4029e03b5ab24a4a88751a9c1a018ea2
+#: ../../installation.rst:1130
+msgid ""
+"When copying and pasting a command, be sure the command has pasted as a "
+"single line before executing. Some document viewers may introduce unwanted "
+"line breaks in copied text."
+msgstr "当复制和粘贴命令时，请确保没有多余的换行符，因为一些文档查看器可能会在复制时加上换行符。"
+
+# cbf94fb3cbf14df48bfb47c0dd21af6f
+#: ../../installation.rst:1134
+msgid ""
+"On the Management Server, run one or more of the following cloud-install-"
+"sys-tmplt commands to retrieve and decompress the system VM template. Run "
+"the command for each hypervisor type that you expect end users to run in "
+"this Zone."
+msgstr "在管理服务器上，运行一个或多个cloud-install-sys-tmplt命令检索和解压系统虚拟机模版。运行这个命令在每个你希望最终用户在这个区域中运行的hypervisor类型。"
+
+# e7bff9caa9f84e8c848d4d19b0daba94
+#: ../../installation.rst:1139
+msgid ""
+"If your secondary storage mount point is not named /mnt/secondary, "
+"substitute your own mount point name."
+msgstr "如果辅助存储挂点不是 /mnt/secondary，替换你自己的挂载点名称。"
+
+# b4aef1ef071f4b71a00b3f645a1a228f
+#: ../../installation.rst:1142
+msgid ""
+"If you set the CloudStack database encryption type to \"web\" when you set "
+"up the database, you must now add the parameter -s <management-server-"
+"secret-key>. See :ref:`about-password-key-encryption`."
+msgstr "如果在设置数据库时，配置CloudStack数据库加密类型是\"web\"，你现在必须添加参数-s <management-server-secret-key>。参阅 :ref:`about-password-key-encryption`。"
+
+# 5b51c5731c5740238035e396516eea52
+#: ../../installation.rst:1146
+msgid ""
+"This process will require approximately 5 GB of free space on the local file"
+" system and up to 30 minutes each time it runs."
+msgstr "这个过程每次运行30分钟，运行时要求本地文件系统剩余大约5GB的空间。"
+
+# fbc4137a3c07458cb016857d765e8e8b
+#: ../../installation.rst:1149
+msgid "For Hyper-V"
+msgstr "对于Hyper-V:"
+
+# 42d30039e33e4a5c89d13a11b25f2545
+#: ../../installation.rst:1155
+msgid "For XenServer:"
+msgstr "对于XenServer："
+
+# 8a428eb947444e7f8a53951d031cfd23
+#: ../../installation.rst:1161
+msgid "For vSphere:"
+msgstr "对于vSphere:"
+
+# 4ebe05af6f144d5b92d47b0a04c3669e
+#: ../../installation.rst:1167
+msgid "For KVM:"
+msgstr "对于KVM:"
+
+# 74cd4b53c2a04c45a2eec8761ae5ef2d
+#: ../../installation.rst:1173
+msgid "For LXC:"
+msgstr "对于LXC："
+
+# 88ddfa6d01ea4de4a01489ecaa5809b1
+#: ../../installation.rst:1179
+msgid "On Ubuntu, use the following path instead:"
+msgstr "在Ubuntu上，使用如下路径："
+
+# f288b19ac3584ac7a502423d40a8558c
+#: ../../installation.rst:1185
+msgid ""
+"If you are using a separate NFS server, perform this step. If you are using "
+"the Management Server as the NFS server, you MUST NOT perform this step."
+msgstr "如果你使用独立的NFS服务器，执行这一步骤。如果你使用管理服务器作为NFS服务器，你必须确保不执行这一步骤。"
+
+# 631bd8031bcf47d3a5e8dff1fd222d47
+#: ../../installation.rst:1189
+msgid ""
+"When the script has finished, unmount secondary storage and remove the "
+"created directory."
+msgstr "当脚本完成后，卸载辅助存储并移除创建的目录。"
+
+# 3534852d9cc24d0dbc62b391e336cf0c
+#: ../../installation.rst:1197
+msgid "Repeat these steps for each secondary storage server."
+msgstr "在每个辅助存储服务器上重述如下步骤。"
+
+# a6cf95cb9f38452bbd3598d0c01df2cc
+#: ../../installation.rst:1201
+msgid "Installation Complete! Next Steps"
+msgstr "安装完成！下一步"
+
+# 6294cacb33fa4969b3bf3bc985881f83
+#: ../../installation.rst:1203
+msgid ""
+"Congratulations! You have now installed CloudStack Management Server and the"
+" database it uses to persist system data."
+msgstr "恭喜！你现在已经安装好了CloudStack管理服务器和用于持久化系统数据的数据库。"
+
+# 482158ea55144603a694e07d25bb404b
+#: ../../installation.rst:1206
+msgid ""
+"|installation-complete.png: Finished installs with single Management Server "
+"and multiple Management Servers|"
+msgstr "|installation-complete.png: Finished installs with single Management Server and multiple Management Servers|"
+
+# bdf25769af294a0ea01aafc7a30ad5c1
+#: ../../installation.rst:1209
+msgid "What should you do next?"
+msgstr "下面你将做什么？"
+
+# e9e84870ee234e5f960460ac41635237
+#: ../../installation.rst:1211
+msgid ""
+"Even without adding any cloud infrastructure, you can run the UI to get a "
+"feel for what's offered and how you will interact with CloudStack on an "
+"ongoing basis. See Log In to the UI."
+msgstr "即使没有增加任何云的基础设施，你可以运行登陆界面感受其提供的内容并与CloudStack进行持续的交互。参见登陆用户界面"
+
+# f1bed9af0dd54d0dbd297f8615f6d35e
+#: ../../installation.rst:1215
+msgid ""
+"When you're ready, add the cloud infrastructure and try running some virtual"
+" machines on it, so you can watch how CloudStack manages the infrastructure."
+" See Provision Your Cloud Infrastructure."
+msgstr "当你已经准备好了，添加云基础架构和尝试运行一些虚拟机，你将会观察到CloudStack如何管理基础设施。参阅：提供你的云基础设置"
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/managing_networks.mo b/source/installguide/locale/zh_CN/LC_MESSAGES/managing_networks.mo
new file mode 100644
index 0000000..ae12814
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/managing_networks.mo
Binary files differ
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/managing_networks.po b/source/installguide/locale/zh_CN/LC_MESSAGES/managing_networks.po
new file mode 100644
index 0000000..b453da8
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/managing_networks.po
@@ -0,0 +1,8467 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:02-0400\n"
+"PO-Revision-Date: 2014-06-30 10:24+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# fc6be4b2a5ef4daab75e0149886b57ab
+#: ../../managing_networks.rst:17
+msgid "Managing Networks and Traffic"
+msgstr "网络和流量管理"
+
+# e6e873bbde6b490a93904226a79e35e7
+#: ../../managing_networks.rst:19
+msgid ""
+"In a CloudStack, guest VMs can communicate with each other using shared "
+"infrastructure with the security and user perception that the guests have a "
+"private LAN. The CloudStack virtual router is the main component providing "
+"networking features for guest traffic."
+msgstr "在CLOUDSTACK中，客户虚拟机之间可以在共享构架下相互通讯，并且可以在一个私有LAN中实现安全和用户互通。CLOUDSTACK的虚拟路由器是实现客户网络功能的主要组件。"
+
+# 158d9384502741139d4db7ad5d35f129
+#: ../../managing_networks.rst:25
+msgid "Guest Traffic"
+msgstr "来宾流量"
+
+# 79038a2139e34806a98fb5dd5d6b1380
+#: ../../managing_networks.rst:27
+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 "在同一个区域内，客户虚拟机之间可以互访，但在不同的区域内，客户虚拟机之间不可以通过（内网）IP地址互访，而只能通过公网IP路由才可以互连。"
+
+# 23f28e25661d4e449f0498521ff811f4
+#: ../../managing_networks.rst:32
+msgid "See a typical guest traffic setup given below:"
+msgstr "下图是一个典型的来宾流量设置："
+
+# 3e47df0ab4fe4f7994d946a031909210
+#: ../../managing_networks.rst:34
+msgid "|guest-traffic-setup.png: Depicts a guest traffic setup|"
+msgstr "|guest-traffic-setup.png: Depicts a guest traffic setup|"
+
+# 4ddddc3fc73a4867a25fc49b035a99b7
+#: ../../managing_networks.rst:36
+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 router. Its eth2 interface is assigned a"
+" public IP address for public traffic. If multiple public VLAN is used, the "
+"router will have multiple public interfaces."
+msgstr "通常，管理服务会自动为每一个网络建立一个虚拟路由。一个虚拟路由实际上就是运行在物理主机上的一台特殊的虚拟机。每一台在一个独立网络中的虚拟路由有3个网口。如果使用多个公共 VLAN，相应的这台路由器就有多个公共的网口。 它的 eth0 网口是提供客户机通信的网关服务的，它的IP地址是 10.1.1.1。eth1 网口是为系统来配置这个虚拟路由而提供的。eth2 网口被赋予一个公共 IP 地址用来实现外部的公共通信。 同样如果使用了多个公共 VLAN 接入，这台路由器将会拥有多个公共的网口。"
+
+# 32df6f633baa46de8a08df89b547bf68
+#: ../../managing_networks.rst:47
+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 "虚拟路由器提供DHCP功能，能自动的为每一个客户虚拟机在预先定义好的IP范围之内分配IP地址。用户也可以为虚拟机手工配置不同的IP地址。"
+
+# 037184db1823493ab1584e55b5275584
+#: ../../managing_networks.rst:52
+msgid ""
+"Source NAT is automatically configured in the virtual router to forward "
+"outbound traffic for all guest VMs"
+msgstr "Source NAT功能是在虚拟路由里自动配置好的，它可以转发所有来宾虚拟机的外出流量。"
+
+# d2daf1fae25745c0a829cd52009d5ac3
+#: ../../managing_networks.rst:56
+msgid "Networking in a Pod"
+msgstr "一个提供点里的网络"
+
+# 3574c26b40ab456e8286506f92bca83c
+#: ../../managing_networks.rst:58
+msgid ""
+"The figure below illustrates network setup within a single pod. The hosts "
+"are connected to a pod-level switch. At a minimum, the hosts should have one"
+" physical uplink to each switch. Bonded NICs are supported as well. The pod-"
+"level switch is a pair of redundant gigabit switches with 10 G uplinks."
+msgstr "下图演示了一个单提供点的网络配置。主机均连接到提供点层级的交换机。每一个主机至少有一个物理网卡连接到交换机。当然，这种环境也支持网卡绑定。提供点层级的交换机由两个1000M冗余组成，它们通过10G线路上联。"
+
+# 35d1da6e0db343f2ae916ce0be527d56
+#: ../../managing_networks.rst:64
+msgid ""
+"|networksinglepod.png: diagram showing logical view of network in a pod|"
+msgstr "|networksinglepod.png: diagram showing logical view of network in a pod|"
+
+# b7c71c1045954931b9d89bd5843e0306
+#: ../../managing_networks.rst:66
+msgid "Servers are connected as follows:"
+msgstr "服务器以如下形式连接："
+
+# 09e404c4512e44e59345fa1f14899f3d
+#: ../../managing_networks.rst:70
+msgid ""
+"Storage devices are connected to only the network that carries management "
+"traffic."
+msgstr "存储设备只与管理网络连接。"
+
+# a3a5ebaa022e413da0ffc6bdae7b6465
+#: ../../managing_networks.rst:75
+msgid ""
+"Hosts are connected to networks for both management traffic and public "
+"traffic."
+msgstr "主机同时与管理网络和公共网络连接。"
+
+# bd0d953a458e41eea4bf15edbfb12b2a
+#: ../../managing_networks.rst:80
+msgid ""
+"Hosts are also connected to one or more networks carrying guest traffic."
+msgstr "主机也与一个或多个来宾网络连接。"
+
+# 28c5e92ff62f49bba80dace0b3ae2fb0
+#: ../../managing_networks.rst:83
+msgid ""
+"We recommend the use of multiple physical Ethernet cards to implement each "
+"network interface as well as redundant switch fabric in order to maximize "
+"throughput and improve reliability."
+msgstr "我们推荐用多个物理网卡以改进性能，也推荐用冗余的光纤交换机以改进网络可靠性。"
+
+# d85d232eadb24f49a48d499c5adf81e7
+#: ../../managing_networks.rst:88
+msgid "Networking in a Zone"
+msgstr "一个区域里的网络"
+
+# 45168de567df49238a394803bce5aacc
+#: ../../managing_networks.rst:90
+msgid ""
+"The following figure illustrates the network setup within a single zone."
+msgstr "下图说明了一个单一区域内的网络设置。"
+
+# 29289f73fcf54224bc331c5454378f15
+#: ../../managing_networks.rst:92
+msgid "|networksetupzone.png: Depicts network setup in a single zone|"
+msgstr "|networksetupzone.png: Depicts network setup in a single zone|"
+
+# df4e8223cc9c4409adf7cc8c71e7a98e
+#: ../../managing_networks.rst:94
+msgid ""
+"A firewall for management traffic operates in the NAT mode. The network "
+"typically is assigned IP addresses in the 192.168.0.0/16 Class B private "
+"address space. Each pod is assigned IP addresses in the 192.168.\\*.0/24 "
+"Class C private address space."
+msgstr "用于管理通信的防火墙工作在NAT模式。通常是分配给网络中的IP地址192.168.0.0/16 B类私有地址空间。每个机柜（POD）分配的IP地址是192.168.*.0/24 C类私有地址空间。"
+
+# 9886368af88c424183304a4eb31ab641
+#: ../../managing_networks.rst:99
+msgid ""
+"Each zone has its own set of public IP addresses. Public IP addresses from "
+"different zones do not overlap."
+msgstr "每个区域都有自己的一套公网IP地址。来自不同区域的公网IP地址不重叠。"
+
+# e924366efd4241009758e8896b3e6669
+#: ../../managing_networks.rst:103
+msgid "Basic Zone Physical Network Configuration"
+msgstr "基本区域物理网络配置"
+
+# 99801fc2693a463386163a5ba924265b
+#: ../../managing_networks.rst:105
+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 "在一个基本的网络中，物理网络的配置非常直接明了。你只需要配置一个客户网络（虚拟）以承载由客户虚拟机产生的流量。当你首次增加一个区域（Zone）到 CloudStack 中，你通过添加域（Add Zone）页面来设置客户网络（虚拟）。"
+
+# 4794c328db1440609a15296cef16b874
+#: ../../managing_networks.rst:111
+msgid "Advanced Zone Physical Network Configuration"
+msgstr "高级区域物理网络的配置"
+
+# 627040abff364b5ea8314a3426b65674
+#: ../../managing_networks.rst:113
+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 "在使用复杂网络的区域中，你需要告知管理服务器，为了实现隔离不同类型的通讯，物理网络是如何设置的。"
+
+# 7d82c9b8761a46dda119e356cf26d478
+#: ../../managing_networks.rst:118
+msgid "Configure Guest Traffic in an Advanced Zone"
+msgstr "在高级域中设置客户通信"
+
+# 1744b57706544187ae3a8c396a505bf1
+#: ../../managing_networks.rst:120
+msgid ""
+"These steps assume you have already logged in to the CloudStack UI. To "
+"configure the base guest network:"
+msgstr "下面的步骤假定你已经登录进入 CloudStack 的界面。设置基本的客户网络："
+
+# 5aecf3d836d747a884b554bca3fbb83d
+#: ../../managing_networks.rst:125
+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 "在左边的导航栏，选择基础架构。在区域界面点击查看全部，然后点击你要添加网络的区域。"
+
+# 0cbb909f14cb492385ca0848aa144676
+# ae580367a0aa4a1186f4e67538afff94
+# af249bda556241b28af1cd321cc15602
+#: ../../managing_networks.rst:130 ../../managing_networks.rst:214
+#: ../../managing_networks.rst:1585
+msgid "Click the Network tab."
+msgstr "点击网络选项卡。"
+
+# 7c7e182828424070b9c41369469b65f0
+# 2e538d60fc224c08a46491e983daca7e
+# 44ba62fc316b4753a5d2655c5c666a98
+#: ../../managing_networks.rst:134 ../../managing_networks.rst:218
+#: ../../managing_networks.rst:1589
+msgid "Click Add guest network."
+msgstr "点击 添加来宾网络。"
+
+# 15e6873aadaf411c83caf85f0a01dd5e
+#: ../../managing_networks.rst:136
+msgid "The Add guest network window is displayed:"
+msgstr "添加来宾网络窗口显示："
+
+# 0d02390e218c427e9a53bf85ca53de51
+#: ../../managing_networks.rst:138
+msgid "|addguestnetwork.png: Add guest network setup in a single zone|"
+msgstr "|addguestnetwork.png: Add guest network setup in a single zone|"
+
+# 0800e2f4123c4dd9a3cf88e6df107406
+# 9e8f926d35dd4062a29482a8ac99cbde
+# 30dd4c879c8f431d96a1941eb88e5443
+#: ../../managing_networks.rst:142 ../../managing_networks.rst:4111
+#: ../../managing_networks.rst:4979
+msgid "Provide the following information:"
+msgstr "填写以下内容："
+
+# 7604500c996c439089ccdde1d7c025b4
+#: ../../managing_networks.rst:146
+msgid "**Name**. The name of the network. This will be user-visible"
+msgstr "**Name**. 要建立的网络结构的名字。这个是用户可见的"
+
+# 360746c957d54a70bd23064f9714bf87
+#: ../../managing_networks.rst:150
+msgid ""
+"**Display Text**: The description of the network. This will be user-visible"
+msgstr "**Display Text**：网络的描述。用户可见"
+
+# 4c0edf7e62fb438f9f48989672721586
+#: ../../managing_networks.rst:155
+msgid "**Zone**: The zone in which you are configuring the guest network."
+msgstr "**Zone**: 这里的区域是指你要配置客户网络的区域。"
+
+# d0157a715ff0417e968114b1c345ed05
+#: ../../managing_networks.rst:159
+msgid ""
+"**Network offering**: If the administrator has configured multiple network "
+"offerings, select the one you want to use for this network"
+msgstr "**网络提议**: 如果管理员已经配置了多个网络方案，可以选择你需要的那个"
+
+# 8821fdb0e3e34d4eb2d879f89ef8265f
+#: ../../managing_networks.rst:164
+msgid "**Guest Gateway**: The gateway that the guests should use"
+msgstr "**Guest gateway**：虚拟机需要使用的网关"
+
+# 4dc47880e5f541529ad13f5cf0ca522f
+#: ../../managing_networks.rst:168
+msgid ""
+"**Guest Netmask**: The netmask in use on the subnet the guests will use"
+msgstr "**Guest Netmask**：客户虚拟机会使用的子网掩码"
+
+# 84368ab7e8384ed2ae5ecece5835bf18
+# 40ef14b296d343928f7b1af29927beba
+# fd54e59b59e34039ba86fdf384b32bb4
+# d595b9b3106b4a93b86dc8def713e6cf
+# 946c5d37563d43f98c6f39734828f252
+# 8969b38d8d954135bd6fd49ba48540a2
+# 96826bee1eba4ea1bbc5592ab0c19d71
+# b886d197d674421586d115da68f6e823
+# 8a1b58cd366c4d22a2a0ef021bf5439a
+# 8873118788c94bcc91cdcb0412e1f3a9
+# 067481ecae7e42a691ed616190af998f
+# 26e33f314996484ab84cff370047c483
+# 7d0cd95d267b472fb4b0dda772ffc2bc
+# 6ada6497acc04627b1750ff39f3e3b89
+#: ../../managing_networks.rst:173 ../../managing_networks.rst:870
+#: ../../managing_networks.rst:1242 ../../managing_networks.rst:1419
+#: ../../managing_networks.rst:1742 ../../managing_networks.rst:3064
+#: ../../managing_networks.rst:3578 ../../managing_networks.rst:4209
+#: ../../managing_networks.rst:4245 ../../managing_networks.rst:5015
+#: ../../managing_networks.rst:5106 ../../managing_networks.rst:5352
+#: ../../managing_networks.rst:5394 ../../managing_networks.rst:6843
+msgid "Click OK."
+msgstr "点击确定。"
+
+# 92ed55846f3943a0899c3de25a023050
+#: ../../managing_networks.rst:176
+msgid "Configure Public Traffic in an Advanced Zone"
+msgstr "在高级区域中配置公共通信"
+
+# 915dafcef9e741c2a3aa241af4f416bf
+#: ../../managing_networks.rst:178
+msgid ""
+"In a zone that uses advanced networking, you need to configure at least one "
+"range of IP addresses for Internet traffic."
+msgstr "在一个使用高级网络配置的区域中，你需要配置至少一个用于Internet通信的IP地址范围。"
+
+# 38eed1230b0548409982c02a9e02c83e
+#: ../../managing_networks.rst:182
+msgid "Configuring a Shared Guest Network"
+msgstr "配置共享的客户网络"
+
+# 029160365cb44beeabf86951b8cabbac
+# 5709f6a0aa4d4e87afbf1cd833e9b2f3
+# 390b3883b39c4ad585199248f00069c2
+#: ../../managing_networks.rst:186 ../../managing_networks.rst:760
+#: ../../managing_networks.rst:1557
+msgid "Log in to the CloudStack UI as administrator."
+msgstr "作为管理员登录到CloudStack用户界面。"
+
+# 6b9a0641eccf4c888cb21525be4ed4c4
+# 25eb0f7c27f44e2983c3f49702a6d79b
+# 10241f1af1c84aa7a72d15d48b14b3e9
+#: ../../managing_networks.rst:190 ../../managing_networks.rst:1354
+#: ../../managing_networks.rst:1561
+msgid "In the left navigation, choose Infrastructure."
+msgstr "在左边的导航，选择基础架构。"
+
+# 72ac0f8a684a418aa1a522b990724f3c
+# fcdd5db0bcf7487fb69abb38b182c87c
+#: ../../managing_networks.rst:194 ../../managing_networks.rst:1565
+msgid "On Zones, click View More."
+msgstr "在区域页面，点击查看全部。"
+
+# 15ee52a81be94e849e9aebbffd80f86e
+# 572f3b0de37d4cde8ee922ca57357102
+#: ../../managing_networks.rst:198 ../../managing_networks.rst:1569
+msgid "Click the zone to which you want to add a guest network."
+msgstr "选择要添加客户网络的那个区域。"
+
+# c8621ca1f0014cab8a2df11d16b6e23b
+# b0ac7488089d4de49ab63d4714a358d1
+# 67983bfccffe4126b74f01d74445a757
+# c54cc238e91a40e88ebec6ac9a67c3b9
+#: ../../managing_networks.rst:202 ../../managing_networks.rst:776
+#: ../../managing_networks.rst:898 ../../managing_networks.rst:1573
+msgid "Click the Physical Network tab."
+msgstr "点击物理网络标签卡。"
+
+# 819adbe3002443ac81418804a6524958
+# 4f1ac1f461d24c96aac89732394faeb4
+#: ../../managing_networks.rst:206 ../../managing_networks.rst:1577
+msgid "Click the physical network you want to work with."
+msgstr "选择您要操作的物理网络。"
+
+# bf5520949d574c33956b419b623300af
+# a5e3c030c17040fd843946f7acd71beb
+#: ../../managing_networks.rst:210 ../../managing_networks.rst:1581
+msgid "On the Guest node of the diagram, click Configure."
+msgstr "在客户节点界面，点击配置。"
+
+# 3a1c06a1806443829aced440705c6ebb
+# 035fafb19b594767b275df96c08bffd8
+#: ../../managing_networks.rst:220 ../../managing_networks.rst:1591
+msgid "The Add guest network window is displayed."
+msgstr "现实添加客户网络窗口。"
+
+# 2f740f3f23ab48a29ae3adbaf94c9a76
+# 342b53e57638424dbd3fc25b5de444cc
+# 81cc7e7f5132410a85166b44099c4efd
+# 433cd273bd454f109daafe4144bedce4
+# fbc94c5a87b34f69a0b7ccd2ec2961b8
+# 49a60cbb39104498a256acb82fa540bc
+# d93b5e9a682247d09575b8fed78e8419
+# 17f3af10510b469ab4fa599fdeca5e84
+# 147594fd9398446a9bffe7aa89aa42ae
+# 9d0d76a77389406aa54c77270247fb68
+# 0d313bd3accd40bba047ccbf1b35d224
+# 3daf7170c2984410906999b0b0fa4f3c
+# 2240e232e86f4b3ca8ab2960be6c573b
+#: ../../managing_networks.rst:224 ../../managing_networks.rst:806
+#: ../../managing_networks.rst:822 ../../managing_networks.rst:856
+#: ../../managing_networks.rst:916 ../../managing_networks.rst:1218
+#: ../../managing_networks.rst:1391 ../../managing_networks.rst:1595
+#: ../../managing_networks.rst:3095 ../../managing_networks.rst:5061
+#: ../../managing_networks.rst:5485 ../../managing_networks.rst:6237
+#: ../../managing_networks.rst:6629
+msgid "Specify the following:"
+msgstr "指定以下信息："
+
+# 14a5b53bcd874033a8eaa789e7c562d1
+# 2f405f166fd04a0bacf050bb1f4f4250
+#: ../../managing_networks.rst:228 ../../managing_networks.rst:1599
+msgid "**Name**: The name of the network. This will be visible to the user."
+msgstr "**Name**: 要建立的网络的名字。这个是用户可见的"
+
+# 0f8d2c8170fd4b98bf717c87aef34378
+# 7585c82a0ece4f368233e94f9d3dfa64
+#: ../../managing_networks.rst:233 ../../managing_networks.rst:1604
+msgid ""
+"**Description**: The short description of the network that can be displayed "
+"to users."
+msgstr "**描述**: 提供一个简短的方案描述。 "
+
+# 99429451759a40f7ba18b278914e39f0
+# 88da596b302847b090b03d4973e86bfd
+#: ../../managing_networks.rst:238 ../../managing_networks.rst:1609
+msgid "**VLAN ID**: The unique ID of the VLAN."
+msgstr "**VLAN ID**: VLAN 的ID。"
+
+# 00c2912dbf2443aa9b3241c8c5676742
+#: ../../managing_networks.rst:242
+msgid "**Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr "**Isolated VLAN ID**: 二级独立 VLAN 的 ID。"
+
+# 6d2136a01445425e94f1ff5205af5c28
+# f35050303cac4011bb97763f32382baf
+#: ../../managing_networks.rst:247 ../../managing_networks.rst:1621
+msgid "**Scope**: The available scopes are Domain, Account, Project, and All."
+msgstr "**Scope**: 可用的范围，包括域，帐户，项目和其他所以。"
+
+# fe3608c2f3b3416aa62072104aa0fa8e
+# 21c43e42d8d34b4c97f8065f32bdae9e
+#: ../../managing_networks.rst:252 ../../managing_networks.rst:1626
+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 "**Domain**: 域，指定客户网络范围的域。指定域中的网络相对其他域是隔离不可见的。如果指定子域访问，域中的客户网络将在所有的子域中可用。"
+
+# 5703f6a9a2db4216aca3b448df168a2a
+# a98df446d79849acbcf910ae486f9f24
+#: ../../managing_networks.rst:260 ../../managing_networks.rst:1634
+msgid ""
+"**Account**: The account for which the guest network is being created for. "
+"You must specify the domain the account belongs to."
+msgstr "**Account**: 这里的帐户是为建立客户网络所指定的。必须指定域中所属的帐户。"
+
+# a1006b86f9414bee862542a9fe33ea89
+# 7431a628570b4f8f941f22c0dbca0d10
+#: ../../managing_networks.rst:266 ../../managing_networks.rst:1640
+msgid ""
+"**Project**: The project for which the guest network is being created for. "
+"You must specify the domain the project belongs to."
+msgstr "**Project**: 项目是客户网络所建立的项目。必须为这个项目指定域。"
+
+# 8b76a654149140adb4fb77dc2eaa7f03
+# 86babff897704393a7a47fac16fdb6da
+#: ../../managing_networks.rst:272 ../../managing_networks.rst:1646
+msgid ""
+"**All**: The guest network is available for all the domains, account, "
+"projects within the selected zone."
+msgstr "**All**: 选择它，会让客户网络对这个区域（Zone）中的所有域，帐户和项目都可用。"
+
+# abea434f07f34363afcd9c5acb702a37
+# 1367c8fe48974b6b8fcef96e9154b1f5
+#: ../../managing_networks.rst:277 ../../managing_networks.rst:1651
+msgid ""
+"**Network Offering**: If the administrator has configured multiple network "
+"offerings, select the one you want to use for this network."
+msgstr "**网络提议**: 如果管理员已经配置了多个网络方案，可以选择你需要的那个。"
+
+# 699e9d5856cb463885a05f687b080247
+# 433ee2c2a4084f46956487e77324431b
+#: ../../managing_networks.rst:283 ../../managing_networks.rst:1657
+msgid "**Gateway**: The gateway that the guests should use."
+msgstr "**Guest gateway**: 虚拟机需要使用的网关。"
+
+# ce51526eaf0744f69498878264436b85
+# 45bbdda7a102498a9f476b2cdb175fd2
+#: ../../managing_networks.rst:287 ../../managing_networks.rst:1661
+msgid "**Netmask**: The netmask in use on the subnet the guests will use."
+msgstr "**Netmask**: 虚拟机子网要使用的网络掩码。"
+
+# 6dbeaf06a3e14f82aa81cb65f66d29f5
+# 4eec9a4a29fa4d52a6b4337a8a50155c
+#: ../../managing_networks.rst:291 ../../managing_networks.rst:1665
+msgid ""
+"**IP Range**: A range of IP addresses that are accessible from the Internet "
+"and are assigned to the guest VMs."
+msgstr "**IP Range**: 定义公网IP范围，这些IP用来访问公网或是从公网访问客户虚拟机。"
+
+# 6136c512a7fd43cf949e71c315564e8e
+#: ../../managing_networks.rst:294
+msgid ""
+"If one NIC is used, these IPs should be in the same CIDR in the case of "
+"IPv6."
+msgstr "如果使用了网卡，这些IP应该在相同的IPv6的CIDR中。"
+
+# 2049d251d6d24864be2401aae7d15eda
+#: ../../managing_networks.rst:299
+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 "**IPv6 CIDR**: 用于定义网络子网的网络前缀。"
+
+# 2eb61bdd6e2e4d0fb52eb0f2ab77e5c3
+# eb07ff88c573443cbf65bd9790a02d7e
+#: ../../managing_networks.rst:306 ../../managing_networks.rst:1670
+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 "**网络域**: 如果你想为客户虚机网络定义一个域名，在此处输入后缀名。"
+
+# 01a5c1ddc4284bf7bb918c2924b99144
+# 29e37ee9c31a42b3b19bbd29b62699db
+# 5b8546575cc143e6aa6df3a739ec2dd4
+# c9c0a1842e2243cbbfbdd7bda9f8c173
+# 62ad85eee39c492e951ac8ef8cc0f1de
+#: ../../managing_networks.rst:312 ../../managing_networks.rst:1676
+#: ../../managing_networks.rst:3133 ../../managing_networks.rst:3172
+#: ../../managing_networks.rst:4450
+msgid "Click OK to confirm."
+msgstr "点击确定。"
+
+# 0ba3f54aff874d7eb78409feb3e574cb
+#: ../../managing_networks.rst:315
+msgid "Using Multiple Guest Networks"
+msgstr "使用多个来宾网络"
+
+# 9ee699c8fe6347568730b54b7737afe5
+#: ../../managing_networks.rst:317
+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 "在使用高级网络的资源域里, 额外的来宾网络可以在初始安装后任何时间添加. 你还可以通过指定DNS后缀为每个网络自定义关联的域名."
+
+# cb2cfc8f5dd14b6a8d4c568329b1bc9e
+#: ../../managing_networks.rst:322
+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 "一个虚机的网络在其创建时定义. 当一个虚机创建以后, 就不能对其网络添加删除, 即便用户可以进入客户虚机删除指定网卡的IP地址."
+
+# 044af5c71d054ac780d922e821f138a2
+#: ../../managing_networks.rst:327
+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 "每一个虚机只有一个默认的网络. 在这个默认网络里, 虚拟路由器的DHCP响应将设置客户的默认网关. 除了单一,必须的默认网络, 多个非默认的网络也可以添加到客户虚机里. 管理员可以控制哪个网络作为默认的网络."
+
+# 0adbfc444f2b4c1db5edbdd5b7d6bbea
+#: ../../managing_networks.rst:333
+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 "附加的网络可以给所有账户使用或者分配给特定的账户. 对所有账户都可用的网络在整个资源域有效. 任何可以访问这个资源域的用户都可以使用这个网络创建虚机. 这些资源域一级的网络基本不提供客户之间的隔离. 分配给特定帐户的网络提供强制隔离的功能."
+
+# b7306772cd68452da7fcba1da1f76cb7
+#: ../../managing_networks.rst:341
+msgid "Adding an Additional Guest Network"
+msgstr "增添一个虚拟机的网络"
+
+# bbfccf4187ee4d4fbf07e7f4bb88a635
+# 55b4e0f4a10d435781dc67f60c289bcc
+# 448e46420df84abe9fd5e0a98622bd8a
+# 7045e9260e2b41ac88aea79006e38ad5
+# c94a526c0dc04ebba1a701bb33b34bd3
+# 5878e84a00674d17980caa25c5845868
+# 21870457e3e743f78d2afa2427544010
+# c407b2aceffd487888c468b506ec84f2
+# be7946dbd37144e8a9a120d588d4ed8d
+# 57c820671f3e472e80e9758a6875049d
+# 7effce72473246f583a2c6706cf7ae8b
+# 10a47885bc344872bb68acaa38950c56
+# 0e16e2897c2541bdb9a9fe44c7c8c314
+# 69c641cc9e5745699a855b095a3f4234
+# 682913d951a64d7a9672b6c2d8ce61ec
+# b507fdb77c914103931f4382f7e94b6f
+# 69bf185d9530474e9d1e3ac4caccde82
+# 3a12fbb150d4405283cf759bdc0f579c
+# ce1e6561910a4f9b92872de6c4f0fe75
+# 8e6a2cd4f9da4a7da14bd4ff19517c5c
+# 0c0a9fa95a2c4c23affeb329bc18b9cd
+# ba5dc11cd6054bb0842bd0c996926273
+# 0383bb7ab57f403bb4dfdfd3cbe56bad
+# 0ce64e2cda5f451f939117bb581125bb
+# 2e7c7ca911564fd0b55e438fbf85b707
+# 724f938759144bca86466d021cded7cb
+# 3eb23b8ca60f439097e03d61faefe36b
+# a1e4d7e27f0a4bfd89398d6c8e268485
+# 4fdda4830b1d407b8baa1d170ccbd0f5
+# c1fe8cc9534f44f1825f02b028eda7ff
+# 1c6cfb5f62e947c8a05df1bdbca53570
+# 797717e559d24b03951f25f843042245
+# e1e46b9e3b67432eba081e3fa0b0b179
+# 7b6bd9d6ebe042aa817672a63cbdfa37
+# c7d9f6a38d724a9aa8a5caa76ed2d848
+# e6c130b9b73f4034b0e9d9c8a3aaa8dd
+# bdc2624551194b9eadb9cdfdf7403a02
+# c7ca24ebec074700a533736638fefcc0
+#: ../../managing_networks.rst:345 ../../managing_networks.rst:412
+#: ../../managing_networks.rst:477 ../../managing_networks.rst:508
+#: ../../managing_networks.rst:543 ../../managing_networks.rst:686
+#: ../../managing_networks.rst:1196 ../../managing_networks.rst:1249
+#: ../../managing_networks.rst:1350 ../../managing_networks.rst:1722
+#: ../../managing_networks.rst:1799 ../../managing_networks.rst:2157
+#: ../../managing_networks.rst:3200 ../../managing_networks.rst:3243
+#: ../../managing_networks.rst:3286 ../../managing_networks.rst:3362
+#: ../../managing_networks.rst:3464 ../../managing_networks.rst:3611
+#: ../../managing_networks.rst:3743 ../../managing_networks.rst:4095
+#: ../../managing_networks.rst:4219 ../../managing_networks.rst:4252
+#: ../../managing_networks.rst:4349 ../../managing_networks.rst:4542
+#: ../../managing_networks.rst:4963 ../../managing_networks.rst:5028
+#: ../../managing_networks.rst:5156 ../../managing_networks.rst:5238
+#: ../../managing_networks.rst:5406 ../../managing_networks.rst:5643
+#: ../../managing_networks.rst:5735 ../../managing_networks.rst:5823
+#: ../../managing_networks.rst:5913 ../../managing_networks.rst:6155
+#: ../../managing_networks.rst:6463 ../../managing_networks.rst:6547
+#: ../../managing_networks.rst:6672 ../../managing_networks.rst:6711
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr "使用管理员或者终端用户账号登录CloudStack UI。"
+
+# 542d2aed321d47bdabd1fca487ffd35e
+# e9aad32ba9934dfabf895d86886307b4
+# a64380da9ffa4f209568917d3e2f7ae6
+# f6467d352c5441f3aac59ff1a7e5751e
+# 489eb5a18ecf487089f92e974e4004b2
+# b77e8c3076474667a41f9c643cfb8921
+# 53f468b814a14dc7bc2846e0bb679713
+# b20083aec91a49e38ba1bd1bbd5ca432
+# cc62da2d87294fe59e75b03eab0b30de
+# 89a49e650a154374ac569bb05b88d91f
+# 230865dbd3c4443cb426bb570ee13485
+# 774f364202474a70b77a8561495b3245
+# 0ad7189c21294ef0b43aba32a8bafb7d
+# 726205f734c447d48af0ecd790bd238a
+# fdade5ad8a554d8897cc4e6c27dbc34e
+# 749f818fe9a349f9bb8cb7538cde74f8
+# b444a52f1dd14725bbd9f33966b9b508
+# bdcf2c42e7064f82ade52bd341621f2e
+# b1f4a91afafd4f6e84df0723ead48206
+# 541424f9e38a42d983bb27f87dcd3225
+# b5e9e12abba44624b3b74fc09e0f77fc
+# f392c162ed3241f09fc16f75065cd789
+# 2cd0df6af7ef4a7f9bad72059870b57b
+# e7d42493086e4c04a6545951d4c1ce5b
+# 3f34c206961e4a239714abc14d945f2c
+# d874094ea72f43988a5a4da919c3aae1
+# 0107854a76984dd18cc4256511f643fb
+# 399088fe7776424c8455730cb62a2f94
+# 9eaf23c1feb144f1b0cd1227b0b9ddd1
+#: ../../managing_networks.rst:349 ../../managing_networks.rst:553
+#: ../../managing_networks.rst:690 ../../managing_networks.rst:1253
+#: ../../managing_networks.rst:2161 ../../managing_networks.rst:3204
+#: ../../managing_networks.rst:3247 ../../managing_networks.rst:3290
+#: ../../managing_networks.rst:3366 ../../managing_networks.rst:3468
+#: ../../managing_networks.rst:4099 ../../managing_networks.rst:4223
+#: ../../managing_networks.rst:4256 ../../managing_networks.rst:4353
+#: ../../managing_networks.rst:4546 ../../managing_networks.rst:4967
+#: ../../managing_networks.rst:5032 ../../managing_networks.rst:5160
+#: ../../managing_networks.rst:5242 ../../managing_networks.rst:5410
+#: ../../managing_networks.rst:5647 ../../managing_networks.rst:5739
+#: ../../managing_networks.rst:5827 ../../managing_networks.rst:5917
+#: ../../managing_networks.rst:6159 ../../managing_networks.rst:6467
+#: ../../managing_networks.rst:6551 ../../managing_networks.rst:6676
+#: ../../managing_networks.rst:6715
+msgid "In the left navigation, choose Network."
+msgstr "在左侧的导航栏，选择网络。"
+
+# ffe816f2fabe4d698bc426a2756acbe6
+#: ../../managing_networks.rst:353
+msgid "Click Add guest network. Provide the following information:"
+msgstr "地阿基添加来宾网络。提供以下信息："
+
+# e493749a1b58441b9f26c0ff3b13b9a7
+#: ../../managing_networks.rst:357
+msgid "**Name**: The name of the network. This will be user-visible."
+msgstr "**Name**：网络的名称。对于最终用户可见。"
+
+# e6573973726c48d1a6ddd47d98dfc7d4
+#: ../../managing_networks.rst:361
+msgid ""
+"**Display Text**: The description of the network. This will be user-visible."
+msgstr "**Display Text**:网络的描述信息。对于最终用户可见。"
+
+# 12ce0885bb7f4c36890123d1bdbd6b6d
+#: ../../managing_networks.rst:366
+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 "**Zone**：此网络所应用到zone的名称。每个zone都是一个广播域，因此每个zone中的来宾网络都有不同的IP范围。管理员必须为每个zone配置IP范围。"
+
+# 6a5f82ef524445d184e3c139994c446f
+#: ../../managing_networks.rst:373
+msgid ""
+"**Network offering**: If the administrator has configured multiple network "
+"offerings, select the one you want to use for this network."
+msgstr "**Network offering**: 如果管理员已经配置了多个网络，选择一个你想使用的。"
+
+# d63cb3347919412cb5652d167f3198a0
+#: ../../managing_networks.rst:379
+msgid "**Guest Gateway**: The gateway that the guests should use."
+msgstr "**Guest Gateway**: 来宾网络的网关。"
+
+# 1da6215b19f84083aeac888d2ef3bff1
+#: ../../managing_networks.rst:383
+msgid ""
+"**Guest Netmask**: The netmask in use on the subnet the guests will use."
+msgstr "**Guest Netmask**: 来宾网络的子网掩码。"
+
+# 4a768d89236c43fd9f2c33eab727c4e8
+# a127adae4308423cb1caf2db8966bdc4
+#: ../../managing_networks.rst:388 ../../managing_networks.rst:3947
+msgid "Click Create."
+msgstr "点击创建。"
+
+# 21b37eb5b7fe40bd99e0910a9f2bb75a
+#: ../../managing_networks.rst:391
+msgid "Reconfiguring Networks in VMs"
+msgstr "在VMs中重新配置网络"
+
+# 476864eb3c9c4bccb394ef84b6e0c94b
+#: ../../managing_networks.rst:393
+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 "CloudStack能让你在不同网络间移动VMs和重新配置VM的网络。你可以从一个网络中移除一个VM，再将其移动到另一个网络。你同样可以修改虚拟机的默认我拿过来，使用这个功能，混合和传统的服务器负载可以被轻松缓解。"
+
+# 9e97bafcd742424d921d811f3230a213
+#: ../../managing_networks.rst:399
+msgid "This feature is supported on XenServer, VMware, and KVM hypervisors."
+msgstr "XenServer、VMware和KVM hypervisors支持这个特性。"
+
+# f34aa270088a4613b0a44df4357afc8f
+# 8bd7a92ac32d4a2a929c8af17d3fb170
+#: ../../managing_networks.rst:402 ../../managing_networks.rst:1517
+msgid "Prerequisites"
+msgstr "先决条件"
+
+# 145ab5ecce044608b4b9656676c6cfc7
+#: ../../managing_networks.rst:404
+msgid ""
+"Ensure that vm-tools are running on guest VMs for adding or removing "
+"networks to work on VMware hypervisor."
+msgstr "确保虚拟机上安装了vm-tools以便通过VMware hypervisor添加或移除网络。"
+
+# 5a51c1312ebb4557a8603954294917c7
+#: ../../managing_networks.rst:408
+msgid "Adding a Network"
+msgstr "添加网络"
+
+# ecf6574c795f4768b731ef450b7ae607
+# 3b1c880a36ab4788a672d34d01ef6a4c
+# 49f1a64bc600489b90f669ff77ba9059
+#: ../../managing_networks.rst:416 ../../managing_networks.rst:481
+#: ../../managing_networks.rst:512
+msgid "In the left navigation, click Instances."
+msgstr "在左侧的导航菜单中，点击实例。"
+
+# 338fcbaeb8724ead9106c34112c862d9
+# bca3b4caf62d4663b33417eb7edaf223
+# f31277b33b9e4e2f9793e5a8ca4d7bb5
+#: ../../managing_networks.rst:420 ../../managing_networks.rst:485
+#: ../../managing_networks.rst:516
+msgid "Choose the VM that you want to work with."
+msgstr "选择你要处理的VM。"
+
+# 156d65dc581c4df498395e309bc7cbde
+# e5d8801dfa004ca1b93351677c983d89
+# 469dea7ab2094639b3d9a2299529fc07
+#: ../../managing_networks.rst:424 ../../managing_networks.rst:489
+#: ../../managing_networks.rst:520
+msgid "Click the NICs tab."
+msgstr "点击网络适配器标签。"
+
+# 1bd7e90630f144b2b08248a827e64b0b
+#: ../../managing_networks.rst:428
+msgid "Click Add network to VM."
+msgstr "将网络添加到 VM"
+
+# 049059a7b43d4efc989e4fcd813e6e1c
+#: ../../managing_networks.rst:430
+msgid "The Add network to VM dialog is displayed."
+msgstr "显示添加网络对话框。"
+
+# 5c99fc8205ef493dbab49c0599061a45
+#: ../../managing_networks.rst:434
+msgid ""
+"In the drop-down list, select the network that you would like to add this VM"
+" to."
+msgstr "在下拉列表里选择你要添加给VM的网络。"
+
+# 901988536d184641ac9d5ecaaee03ee2
+#: ../../managing_networks.rst:437
+msgid ""
+"A new NIC is added for this network. You can view the following details in "
+"the NICs page:"
+msgstr "这样就为这个网络添加了一个新网卡。你可以在网卡页面查看下列信息："
+
+# 8d071d6df54845d6a56e7d96321dd7e8
+#: ../../managing_networks.rst:442
+msgid "ID"
+msgstr "ID"
+
+# ba92b68db3fc48ae810bd43616abc87a
+#: ../../managing_networks.rst:446
+msgid "Network Name"
+msgstr "网络名称"
+
+# eefe16e33001458591bb721f9e964a32
+#: ../../managing_networks.rst:450
+msgid "Type"
+msgstr "类型"
+
+# ce7e7d2354fc48ccb97e1c2917007397
+# 35a3d8a7cc444f7289fff5b3f02731e3
+# 906d6bce91f745de9cc8eb362260b17b
+#: ../../managing_networks.rst:454 ../../managing_networks.rst:4332
+#: ../../managing_networks.rst:4458
+msgid "IP Address"
+msgstr "IP地址"
+
+# 07c404d90b444084935108a2905f8147
+# aa4cc5b288b14a26b34b3cd819e6be4e
+#: ../../managing_networks.rst:458 ../../managing_networks.rst:4462
+msgid "Gateway"
+msgstr "网关"
+
+# da3675e2aed24eb681d8601910102496
+#: ../../managing_networks.rst:462
+msgid "Netmask"
+msgstr "子网掩码"
+
+# 48374307b68a4eff88c1778ea7bd9380
+#: ../../managing_networks.rst:466
+msgid "Is default"
+msgstr "默认的"
+
+# 2777d60a7bf14a35bd37af5f0ac55458
+#: ../../managing_networks.rst:470
+msgid "CIDR (for IPv6)"
+msgstr "CIDR（IPv6）"
+
+# 84f9d9b60c4e4ce4a509cad5b0900a5b
+#: ../../managing_networks.rst:473
+msgid "Removing a Network"
+msgstr "移除网络"
+
+# 707d137eb0aa4adaa497aff9a413ad06
+#: ../../managing_networks.rst:493
+msgid "Locate the NIC you want to remove."
+msgstr "找到你要移除的网卡上。"
+
+# c2a07f20886b47be83f065291dfee6fb
+#: ../../managing_networks.rst:497
+msgid "Click Remove NIC button. |remove-nic.png: button to remove a NIC|"
+msgstr "点击移除网卡按钮。|remove-nic.png: button to remove a NIC|"
+
+# b23abd4aac6242bdbc3f97acc2666a90
+# 8f8b04c7921a441ba8480683014b9864
+#: ../../managing_networks.rst:501 ../../managing_networks.rst:533
+msgid "Click Yes to confirm."
+msgstr "点击Yes确认。"
+
+# 4f9e35dc3f614384a7505c4161fffaac
+#: ../../managing_networks.rst:504
+msgid "Selecting the Default Network"
+msgstr "选择默认网络"
+
+# 40b332e2efca44c092058585a0004200
+#: ../../managing_networks.rst:524
+msgid "Locate the NIC you want to work with."
+msgstr "找到你想要的网卡。"
+
+# 3d3dc6ede8e440efab9778ab27669811
+#: ../../managing_networks.rst:528
+msgid ""
+"Click the Set default NIC button. |set-default-nic.png: button to set a NIC "
+"as default one.|"
+msgstr "点击设置为默认网卡按钮。|set-default-nic.png: button to set a NIC as default one.|"
+
+# f0c74bc7df3d400bac208e03ca7e454d
+#: ../../managing_networks.rst:536
+msgid "Changing the Network Offering on a Guest Network"
+msgstr "在来宾网络上更改网络方案"
+
+# bd0f96f469b24f7cb9efc0e11835fc56
+#: ../../managing_networks.rst:538
+msgid ""
+"A user or administrator can change the network offering that is associated "
+"with an existing guest network."
+msgstr "用户或者管理员可以更改与之相关的来宾网络的网络方案。"
+
+# 746637ea703149eab979289dea055956
+#: ../../managing_networks.rst:547
+msgid ""
+"If you are changing from a network offering that uses the CloudStack virtual"
+" router to one that uses external devices as network service providers, you "
+"must first stop all the VMs on the network."
+msgstr "如果你将使用CloudStack虚拟路由的一个网络方案改成使用公共网络设备作为网络服务商，那么你必须先关掉该网络中的所有虚机。"
+
+# b06f831436614c7799e92f02062dd02e
+# b2aef771f9cb4102849882e08921deda
+#: ../../managing_networks.rst:557 ../../managing_networks.rst:694
+msgid "Click the name of the network you want to modify."
+msgstr "点击你要修改的网络名称。"
+
+# 8fe0c8047dd941648bdb27d5c4d46d64
+#: ../../managing_networks.rst:561
+msgid ""
+"In the Details tab, click Edit. |EditButton.png: button to edit a network|"
+msgstr "在详细标签页，点击编辑。|EditButton.png: button to edit a network|"
+
+# 38ce91cfac534d3d8ce2d2be8ac4d9db
+#: ../../managing_networks.rst:566
+msgid ""
+"In Network Offering, choose the new network offering, then click Apply."
+msgstr "在网络方案中，选择新的网络方案，然后点击应用。"
+
+# 0c9082cd84904f30a842d0296519899f
+#: ../../managing_networks.rst:569
+msgid ""
+"A prompt is displayed asking whether you want to keep the existing CIDR. "
+"This is to let you know that if you change the network offering, the CIDR "
+"will be affected."
+msgstr "这时会有一个提示问你是否保持已存在的CIDR不变。这是让你了解如果你改变网络了方案，那么CIDR会受到影响。"
+
+# 395368811c93495691bd4e308ae0bbc4
+#: ../../managing_networks.rst:573
+msgid ""
+"If you upgrade between virtual router as a provider and an external network "
+"device as provider, acknowledge the change of CIDR to continue, so choose "
+"Yes."
+msgstr "如果你将虚拟路由升级到外网设备，在看到变更CIDR以继续时，请选择Yes。"
+
+# ee09bef0f4f84d41a949984dce97934e
+#: ../../managing_networks.rst:579
+msgid ""
+"Wait for the update to complete. Don’t try to restart VMs until the network "
+"change is complete."
+msgstr "等待更新完成。在网络变更完成之前不要试图重启VMs。"
+
+# 7c315c696ed54f5197595376cdd7d0c0
+#: ../../managing_networks.rst:584
+msgid "If you stopped any VMs, restart them."
+msgstr "如果你停止了任何VMs，请重启他们。"
+
+# 92b286db05494a3f9d6591a9f2ccfc6a
+#: ../../managing_networks.rst:587
+msgid "IP Reservation in Isolated Guest Networks"
+msgstr "隔离的来宾网络中的预留IP"
+
+# 67ed578463354e849af5ed40418159aa
+#: ../../managing_networks.rst:589
+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 "在隔离的来宾网络中，来宾IP地址空间中的一部分可以被保留下来以供非CloudStack VMs或者物理服务器使用。要真么做，你应该在来宾网络应用状态时依靠指定CIDR来配置一个预留IP地址范围。如果你的客户希望在同一个网络中有非CloudStack控制的VMs或者物理服务器，它们可以共享一部分主要为来宾网络提供的IP地址空间。"
+
+# d38381f1dad148afb7aeed5ee6e6db41
+#: ../../managing_networks.rst:597
+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 called Reserved IP Range. When IP "
+"reservation is configured, the administrator can add additional VMs or "
+"physical servers that are not part of CloudStack to the same network and "
+"assign them the Reserved IP addresses. CloudStack guest VMs cannot acquire "
+"IPs from the Reserved IP Range."
+msgstr "在高级域中，定义一个网络时要给其赋予一个IP地址范围或CIDR。CloudStack虚拟路由器起着DHCP的作用，并通过CIDR来给客户虚拟机分配IP地址。如果为了预留CIDR不用于cloudstack，应当进行说明，即部分IP地址范围或CIDR仅能被DHCP服务分配给在cloudstack中创建的虚拟机。剩下的IP地址被称作预留IP地址范围。当预留的IP被配置时，管理员可以增加额外的虚拟机或并不属于cloudstack的物理服务器到同一个网络，可以将预留的IP地址指定给他们。cloudstack的客户虚拟机不能够从预留的IP地址中获得地址。"
+
+# 3031b1a715ff422bad8de1f97adc2db7
+#: ../../managing_networks.rst:611
+msgid "IP Reservation Considerations"
+msgstr "IP预留事项"
+
+# c57c48d3a65e474c89a99952e65a6a40
+#: ../../managing_networks.rst:613
+msgid ""
+"Consider the following before you reserve an IP range for non-CloudStack "
+"machines:"
+msgstr "在给非cloudstack内的机器预留IP地址时，要考虑以下几个方面："
+
+# 05c140f272754cfb9d21597b9c778fc5
+#: ../../managing_networks.rst:618
+msgid "IP Reservation is supported only in Isolated networks."
+msgstr "IP预留仅在隔离网络内支持"
+
+# f5211c450a014b0a8d335434d84aa391
+#: ../../managing_networks.rst:622
+msgid ""
+"IP Reservation can be applied only when the network is in Implemented state."
+msgstr "仅当网络在实施状态时，IP预留才能被应用。"
+
+# 6add1277df044450bce332b364de119b
+#: ../../managing_networks.rst:627
+msgid "No IP Reservation is done by default."
+msgstr "默认不做IP预留。"
+
+# 0847da9c049c4c0da2a6eac963931b02
+#: ../../managing_networks.rst:631
+msgid "Guest VM CIDR you specify must be a subset of the network CIDR."
+msgstr "指定客户的CIDR必须是网络CIDR的子网。"
+
+# 36a9bbd09feb416ca7f9ccca3c54eefb
+#: ../../managing_networks.rst:635
+msgid ""
+"Specify a valid Guest VM CIDR. IP Reservation is applied only if no active "
+"IPs exist outside the Guest VM CIDR."
+msgstr "指定一个有效的客户虚拟机CIDR。只有不活动的IP在客户虚拟机CIDR存在时，IP预留才能被应用。"
+
+# 191010bd30424f3aa12cf309a48dcfc4
+#: ../../managing_networks.rst:638
+msgid ""
+"You cannot apply IP Reservation if any VM is alloted with an IP address that"
+" is outside the Guest VM CIDR."
+msgstr "如果任一虚拟机被分配了客户虚拟机CIDR之外的IP地址时，IP预留将不能应用。"
+
+# e4b8dc3735d4441ebf832418538d5833
+#: ../../managing_networks.rst:643
+msgid ""
+"To reset an existing IP Reservation, apply IP reservation by specifying the "
+"value of network CIDR in the CIDR field."
+msgstr "为重置一个已存在的IP预留，通过在CIDR框指定CIDR值就可应用IP预留。"
+
+# 8281e4ae0c6a4374b25bfef4f7e74405
+#: ../../managing_networks.rst:646
+msgid ""
+"For example, the following table describes three scenarios of guest network "
+"creation:"
+msgstr "例如，下表描述了客户网络创建的三种情形："
+
+# 9f714ae7b5f346bc87da5182136d41e5
+#: ../../managing_networks.rst:650
+msgid "Case"
+msgstr "案例"
+
+# 43eb64da7dd14977948b1fd136c81c4f
+# ba69ebf50fa04e628494a63c71ee09be
+# 6e509570aefc4ed58372df0bae71f59e
+# e02ce26c53d447cab48c5987becb6178
+# 372de59b30db4b00a1a4a4503aecb29d
+# 0efc90dc789a42219e0e1821921c3a3b
+# 2f722e4bc54941bf9ac18e34ec89ea21
+# 0f4f84fccf1c4879a9ec6691a4abb447
+# 04c82a1485db4a52a0c4fae3e4018e41
+# 8788d910542844b09ae66506304063dc
+# e65e4e6cdcba4f138e43047ff9d3bed6
+# 23d809b6aa20458dacb898b0e8b4d1da
+# cd520efc8baa4344b57bd33b0fa5254d
+#: ../../managing_networks.rst:650 ../../managing_networks.rst:3846
+#: ../../managing_networks.rst:4293 ../../managing_networks.rst:4393
+#: ../../managing_networks.rst:4587 ../../managing_networks.rst:5144
+#: ../../managing_networks.rst:5193 ../../managing_networks.rst:5451
+#: ../../managing_networks.rst:5776 ../../managing_networks.rst:5863
+#: ../../managing_networks.rst:5954 ../../managing_networks.rst:6196
+#: ../../managing_networks.rst:6588
+msgid "CIDR"
+msgstr "CIDR"
+
+# 63125858003344c0b965da2ac922cf02
+#: ../../managing_networks.rst:650
+msgid "Network CIDR"
+msgstr "网络CIDR"
+
+# c3c99ba5184c4c9194605bb04a547f39
+#: ../../managing_networks.rst:650
+msgid "Reserved IP Range for Non-CloudStack VMs"
+msgstr "非cloudstack虚拟机的IP预留范围"
+
+# 0e5c1cae0f4d4f06851e27a50273b95c
+#: ../../managing_networks.rst:650
+msgid "Description"
+msgstr "描述"
+
+# 2e71a7acd08543168d74d2c0d03e0c39
+# d06565ec0d634d848669aa19d123d59a
+#: ../../managing_networks.rst:652 ../../managing_networks.rst:5146
+msgid "1"
+msgstr "1"
+
+# bd4f28e5c83943d8882e2012659415bf
+# 249137a9387145d0ac514e9000be76cd
+# d7c4b09246fb4bfeb5649c2cf6e23d30
+#: ../../managing_networks.rst:652 ../../managing_networks.rst:653
+#: ../../managing_networks.rst:654
+msgid "10.1.1.0/24"
+msgstr "10.1.1.0/24"
+
+# 2f9cc88264fb4285bfa3149ea04b26a5
+# d74122c1ce754a1999acc721dfe12491
+# 3e1cad272521413bb73ebf025861f357
+# c9bd04abf9984e3d82a008b15823df6f
+#: ../../managing_networks.rst:652 ../../managing_networks.rst:652
+#: ../../managing_networks.rst:654 ../../managing_networks.rst:654
+msgid "None"
+msgstr "无"
+
+# 672d94082a534891849650884d4c25d0
+#: ../../managing_networks.rst:652
+msgid "No IP Reservation."
+msgstr "无"
+
+# 7f31ca61138545d19f53bfea0156930f
+# f11cfcf719bc4813a691abc48eef0c50
+#: ../../managing_networks.rst:653 ../../managing_networks.rst:5147
+msgid "2"
+msgstr "2"
+
+# 8e804381dca64c3ab199583ca238a7e8
+#: ../../managing_networks.rst:653
+msgid "10.1.1.0/26"
+msgstr "10.1.1.0/26"
+
+# 042cf084bef6418fa9d8ee1a00593e8a
+#: ../../managing_networks.rst:653
+msgid "10.1.1.64 to 10.1.1.254"
+msgstr "10.1.1.64-10.1.1.254"
+
+# 2094d73c4b004d18b9b1c3be4ac72e10
+#: ../../managing_networks.rst:653
+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 "在界面的CIDR框内输入10.1.1.0/26或通过UpdateNetwork的API配置为guestvmcidr=10.1.1.0/26，进行IP预留配置"
+
+# 769561dd7e454a58b571d069407bc84f
+#: ../../managing_networks.rst:654
+msgid "3"
+msgstr "3"
+
+# 99819f9f881049da88cf236d227fbcce
+#: ../../managing_networks.rst:654
+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 "在界面的CIDR框内输入10.1.1.0/24或通过UpdateNetwork API配置为guestvmcidr=10.1.1.0/24，进行IP预留清除"
+
+# af64fa9a0d594bf6aba58e557fb64ef2
+#: ../../managing_networks.rst:659
+msgid "Limitations"
+msgstr "局限性"
+
+# b133ecb14f0743c5aad172cbec921f69
+#: ../../managing_networks.rst:663
+msgid ""
+"The IP Reservation is not supported if active IPs that are found outside the"
+" Guest VM CIDR."
+msgstr "如果在客户虚拟机CIDR外发现活动的IP地址，IP预留将不被支持。"
+
+# 9c8183bbe2aa4950a96b3f707269281c
+#: ../../managing_networks.rst:668
+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 "在IP预留中，引起CIDR变化的网络升级方案都将无效，如将无外部设备的方案升级到带有外部设备的方案。在新实施的网络中，要重新配置IP预留。"
+
+# a6037f7354694b7fa3df7eab35ce68a3
+#: ../../managing_networks.rst:674
+msgid "Best Practices"
+msgstr "最佳实践"
+
+# 1402bdfed0e642a5bc411cad728d629f
+#: ../../managing_networks.rst:676
+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 "一旦网络状态变为实施，应尽快应用IP预留到客户网络。如果在第一台客户虚拟机部署后应用IP预留，则会在应用IP会有较少的冲突发生。"
+
+# 9d8b936d8d924b3e9610e79cea49d7ed
+#: ../../managing_networks.rst:682
+msgid "Reserving an IP Range"
+msgstr "预留一个IP范围"
+
+# 43313d5d032c4bc1ae00497086042bf1
+#: ../../managing_networks.rst:698
+msgid ""
+"In the Details tab, click Edit. |edit-icon.png: button to edit a network|"
+msgstr "在 详细 页签，点击 编辑 |edit-icon.png: button to edit a network|"
+
+# 4b6443793ca64ed7b71e9dacebc772c6
+#: ../../managing_networks.rst:701
+msgid "The CIDR field changes to editable one."
+msgstr "CIDR框将变为可编辑状态"
+
+# 170900f4419c40d3ae77ba9cee3b6fff
+#: ../../managing_networks.rst:705
+msgid "In CIDR, specify the Guest VM CIDR."
+msgstr "在CIDR框，说明客户虚拟机的CIDR"
+
+# 1fccea99506b441bba9fd6fbc76dd995
+#: ../../managing_networks.rst:709
+msgid "Click Apply."
+msgstr "点击应用"
+
+# c0734e33a8844d90aac6295573540aee
+#: ../../managing_networks.rst:711
+msgid ""
+"Wait for the update to complete. The Network CIDR and the Reserved IP Range "
+"are displayed on the Details page."
+msgstr "等待更新完成。"
+
+# aad0613e9913469fb756198fc0170632
+#: ../../managing_networks.rst:715
+msgid "Reserving Public IP Addresses and VLANs for Accounts"
+msgstr "为账户预留公共IP地址及VLANS"
+
+# 6e44df38576d4f5e99903f26a9db1253
+#: ../../managing_networks.rst:717
+msgid ""
+"CloudStack provides you the ability to reserve a set of public IP addresses "
+"and VLANs exclusively for an account. During zone creation, you can continue"
+" defining a set of VLANs and multiple public IP ranges. This feature extends"
+" the functionality to enable you to dedicate a fixed set of VLANs and guest "
+"IP addresses for a tenant."
+msgstr "CloudStack可以让你能够独立的为账户预留一部分公共IP地址和VLANS。在创建区域阶段，你可以继续定义一部分VLANS以及多个公共IP范围。这种功能扩展特性可以让你能够为客户预留固定的一部分VLAN和客户IP地址"
+
+# 8da4bb7270e845baa41435d7a8dc2897
+#: ../../managing_networks.rst:723
+msgid ""
+"Note that if an account has consumed all the VLANs and IPs dedicated to it, "
+"the account can acquire two more resources from the system. CloudStack "
+"provides the root admin with two configuration parameter to modify this "
+"default behavior—use.system.public.ips and use.system.guest.vlans. These "
+"global parameters enable the root admin to disallow an account from "
+"acquiring public IPs and guest VLANs from the system, if the account has "
+"dedicated resources and these dedicated resources have all been consumed. "
+"Both these configurations are configurable at the account level."
+msgstr "注意，如果一个账户使用了所有分配给他的VLAN和IP，这个账户可以从系统获得二个以上的资源。CloudStack为根管理员提供了二个参数可以进行控制，分别是use.system.public.ips和use.system.guest.vlans。当一个账户分配了资源并且这些资源已经被消耗掉时，这二个全局参数可以使根管理员拒绝此账户从公共IP和来宾VLAN获取资源。二个配置都能在帐户级别进行配置。"
+
+# 37e6f49f8b53452a8036407ad381ea12
+#: ../../managing_networks.rst:733
+msgid "This feature provides you the following capabilities:"
+msgstr "这些特性可提供以下的功能："
+
+# 671086ca87b14ae28c39b69fd8046953
+#: ../../managing_networks.rst:737
+msgid ""
+"Reserve a VLAN range and public IP address range from an Advanced zone and "
+"assign it to an account"
+msgstr "从一个高级区域中预留一个VLAN范围和公共IP地址，并可以将其指定给一个账户。"
+
+# 404fcaa9d1b848d2ab247cce5350c281
+#: ../../managing_networks.rst:742
+msgid "Disassociate a VLAN and public IP address range from an account"
+msgstr "将一个VLAN和IP地址从一个账户解除联系。"
+
+# bd85bcf3d9394066af54e1e703ae3cf7
+#: ../../managing_networks.rst:746
+msgid "View the number of public IP addresses allocated to an account"
+msgstr "查看分配给帐户的公共IP地址。"
+
+# 01799c3a9b364c51b97d539c849d3394
+#: ../../managing_networks.rst:750
+msgid ""
+"Check whether the required range is available and is conforms to account "
+"limits."
+msgstr "检查需要的范围是否可用并且要符合帐户限制。"
+
+# 7716c7ee6e9a4c68bacaaafbba51a78c
+#: ../../managing_networks.rst:753
+msgid "The maximum IPs per account limit cannot be superseded."
+msgstr "不能超过每个账户最大的IP限制数。"
+
+# 8f2fa2619671428980abde283469e00d
+#: ../../managing_networks.rst:756
+msgid "Dedicating IP Address Ranges to an Account"
+msgstr "分配IP地址给一个账户"
+
+# d7a82a1208db4208961df5b2bda98eb3
+# 3ac411dc4da74e0689c3e931f08d5c59
+# c74ad6e9cbee4ff685cef4af6c1a1c8a
+#: ../../managing_networks.rst:764 ../../managing_networks.rst:886
+#: ../../managing_networks.rst:2974
+msgid "In the left navigation bar, click Infrastructure."
+msgstr "在左侧导航栏中，点击基础架构"
+
+# ad2d0d358fab46f69cc0e2834d1025b5
+# 06d4cbfaa106459eb58d6d9bb34a92a1
+#: ../../managing_networks.rst:768 ../../managing_networks.rst:890
+msgid "In Zones, click View All."
+msgstr "在区域中，点击查看全部"
+
+# 04e17439a9d04d8c92bace413127ce77
+# e40c006773b9414cbe8dd42bb69472d4
+# 03828d4d48bf4770bdc2328f34b55100
+#: ../../managing_networks.rst:772 ../../managing_networks.rst:894
+#: ../../managing_networks.rst:2982
+msgid "Choose the zone you want to work with."
+msgstr "选择你要设置的区域。"
+
+# b2f55880ae154ea5a38880eeeb515690
+#: ../../managing_networks.rst:780
+msgid "In the Public node of the diagram, click Configure."
+msgstr "在图的公共节点上，点击配置。"
+
+# 790579c6465f4bf88b03caf31b04e907
+#: ../../managing_networks.rst:784
+msgid "Click the IP Ranges tab."
+msgstr "点击IP范围页签。"
+
+# 9136b3e4ca934c23806bbc7ca0ff01e5
+#: ../../managing_networks.rst:786
+msgid ""
+"You can either assign an existing IP range to an account, or create a new IP"
+" range and assign to an account."
+msgstr "或者指定一个已经的IP范围给帐户，或创建一个新的IP范围并指定给一个帐户。"
+
+# be977158780a4bfca4232fc7d2573dd7
+#: ../../managing_networks.rst:791
+msgid "To assign an existing IP range to an account, perform the following:"
+msgstr "要指定一个已有IP范围给帐户，按以下操作进行"
+
+# c85643e60bae4ce7a7341f72ed356343
+#: ../../managing_networks.rst:795
+msgid "Locate the IP range you want to work with."
+msgstr "确定需要分配的IP范围"
+
+# 8c760073c6e140c98957ae64117cd375
+#: ../../managing_networks.rst:799
+msgid ""
+"Click Add Account |addAccount-icon.png: button to assign an IP range to an "
+"account.| button."
+msgstr "点击 添加帐户 |addAccount-icon.png: button to assign an IP range to an account.| 按钮，"
+
+# 5907d0ab73b04589b7fba68c857ad361
+#: ../../managing_networks.rst:802
+msgid "The Add Account dialog is displayed."
+msgstr "会弹出添加帐户对话框。"
+
+# d84f7b0e62b043939a4656f457f829e7
+#: ../../managing_networks.rst:810
+msgid ""
+"**Account**: The account to which you want to assign the IP address range."
+msgstr "**帐户**: 即需要指定IP地址范围的帐户"
+
+# 54ea232ef7544939989c85cf78823ab4
+#: ../../managing_networks.rst:815
+msgid "**Domain**: The domain associated with the account."
+msgstr "**域**: 与帐户关联的域名"
+
+# cac430d036924f38a9290dde3665c841
+#: ../../managing_networks.rst:817
+msgid "To create a new IP range and assign an account, perform the following:"
+msgstr "要指定一个新的IP范围给帐户，按以下操作进行"
+
+# d50191ed42ad44ee95f6167032a30c65
+#: ../../managing_networks.rst:826
+msgid "**Gateway**"
+msgstr "**网关**"
+
+# 13d287dfefa145e3bf443ca11ed78fa2
+#: ../../managing_networks.rst:830
+msgid "**Netmask**"
+msgstr "**掩码**"
+
+# 2e49c1a58f4a4bfa87d30c1c449df1e3
+#: ../../managing_networks.rst:834
+msgid "**VLAN**"
+msgstr "**VLAN**"
+
+# 8ebc180647e6488db6d7419f0c96d969
+#: ../../managing_networks.rst:838
+msgid "**Start IP**"
+msgstr "**起始IP**"
+
+# 39bbcd6bce9c4acdb1dde4c134d36aee
+#: ../../managing_networks.rst:842
+msgid "**End IP**"
+msgstr "**结束IP**"
+
+# c9ff42e89acd482b839c78ede4bf72a2
+#: ../../managing_networks.rst:846
+msgid "**Account**: Perform the following:"
+msgstr "**帐户**: 按以下操作进行："
+
+# 4e8c15e78f4040da8818c60242a385f7
+#: ../../managing_networks.rst:850
+msgid "Click Account."
+msgstr "点击帐户"
+
+# 4d16eeb78e534a4aba7b7c05c335d94a
+#: ../../managing_networks.rst:852
+msgid "The Add Account page is displayed."
+msgstr "会显示添加帐户页"
+
+# 4fcbdb024f3c4d0e916309194ccf9796
+#: ../../managing_networks.rst:860
+msgid ""
+"****Account****: The account to which you want to assign an IP address "
+"range."
+msgstr "****帐户****: 即需要指定IP地址范围的帐户"
+
+# 5dd4ec70717a455cb3eae0f191b2c338
+# e1b99db893e94523a9c9c6c2dca5e50a
+#: ../../managing_networks.rst:865 ../../managing_networks.rst:930
+msgid "****Domain****: The domain associated with the account."
+msgstr "****域****: 域账号关联的域。"
+
+# 222bcd68057f4097804636cc658bae40
+# 583b09f47740445cae14b167a426c0d5
+# d8184c325cbe4e2989e1772dd91acd0b
+# b8bdf6dd077f48bab5be9a342447e9d8
+# 221e41362cdb48c1b692cef19b0a8218
+# f241bee872c34bcfa7d43b4601e1cb48
+# 95df29e50c984e798847dc985a455395
+#: ../../managing_networks.rst:874 ../../managing_networks.rst:1919
+#: ../../managing_networks.rst:3411 ../../managing_networks.rst:3511
+#: ../../managing_networks.rst:3667 ../../managing_networks.rst:3899
+#: ../../managing_networks.rst:5623
+msgid "Click Add."
+msgstr "点击 添加"
+
+# 6f5ed4ecaf104ec089964163e1e6884f
+#: ../../managing_networks.rst:877
+msgid "Dedicating VLAN Ranges to an Account"
+msgstr "确定需要分配的IP范围"
+
+# 1d96f022bb0641f591f869dcdef945de
+#: ../../managing_networks.rst:881
+msgid ""
+"After the CloudStack Management Server is installed, log in to the "
+"CloudStack UI as administrator."
+msgstr "安装好CloudStack管理端后，使用管理员帐号登录CloudStack用户界面。"
+
+# b7387ff7ac314fabb59c5c8adb95d64c
+# 09557ffae33041df84505184339ead4d
+#: ../../managing_networks.rst:902 ../../managing_networks.rst:1367
+msgid "In the Guest node of the diagram, click Configure."
+msgstr "在图中的来宾节点上，点击配置"
+
+# fcf27305c8cf42bcaea54b6e0d583e74
+#: ../../managing_networks.rst:906
+msgid "Select the Dedicated VLAN Ranges tab."
+msgstr "选择分配VLAN范围页签"
+
+# 67395673dcac45fd95c09509e40ab195
+#: ../../managing_networks.rst:910
+msgid "Click Dedicate VLAN Range."
+msgstr "点击分配VLAN范围"
+
+# ab0efa84cce7484aa1483aa86e7458e3
+#: ../../managing_networks.rst:912
+msgid "The Dedicate VLAN Range dialog is displayed."
+msgstr "会弹出分配VLAN对话框。"
+
+# 79112ed3b43d4ac9b8ffd92e5be692f1
+#: ../../managing_networks.rst:920
+msgid ""
+"****VLAN Range****: The VLAN range that you want to assign to an account."
+msgstr "****VLAN范围****: 即需要指定给帐户的VLAN范围"
+
+# a99491d184b347ae9692f3140f8507e1
+#: ../../managing_networks.rst:925
+msgid ""
+"****Account****: The account to which you want to assign the selected VLAN "
+"range."
+msgstr "****帐户****: 即需要指定选定的VLAN的帐户"
+
+# fcc09f716f8d4237b77cc161171a4261
+#: ../../managing_networks.rst:933
+msgid "Configuring Multiple IP Addresses on a Single NIC"
+msgstr "在单网卡配置多个IP地址"
+
+# a94a3710f1234c97836f59a5a07db667
+#: ../../managing_networks.rst:935
+msgid ""
+"CloudStack provides you the ability to associate multiple private IP "
+"addresses per guest VM NIC. In addition to the primary IP, you can assign "
+"additional IPs to the guest VM NIC. This feature is supported on all the "
+"network configurations—Basic, Advanced, and VPC. Security Groups, Static NAT"
+" and Port forwarding services are supported on these additional IPs."
+msgstr "CloudStack能够让你给每个客户虚拟机网卡配置多个私有IP地址，除主IP地址外，你可以指定额外的IP地址到客户虚拟机网卡。在所有的网络配置中，如基础配置，高级配置，VPC，均支持这一功能。安全组，静态NAT及端口转发服务在额外的IP地址上也都被支持。"
+
+# 494be8c0259840fb84fb26e96d13a908
+#: ../../managing_networks.rst:942
+msgid ""
+"As always, you can specify an IP from the guest subnet; if not specified, an"
+" IP is automatically picked up from the guest VM subnet. You can view the "
+"IPs associated with for each guest VM NICs on the UI. You can apply NAT on "
+"these additional guest IPs by using network configuration option in the "
+"CloudStack UI. You must specify the NIC to which the IP should be "
+"associated."
+msgstr "当然，你也可以从来宾子网中指定一个IP，如果没有指定，将会从来宾虚拟机子网中自动选择一个。可以从UI中查看每一个与来宾虚拟机网卡关联的IP地址。也可以在CloudStack界面中通过网络配置选项在那些额外的来宾虚拟机上应用NAT。但必须指明网卡与哪一个IP关联。"
+
+# 925a5eb75fe04c35bfd19b1ac2f44b7e
+#: ../../managing_networks.rst:949
+msgid ""
+"This feature is supported on XenServer, KVM, and VMware hypervisors. Note "
+"that Basic zone security groups are not supported on VMware."
+msgstr "在XenServer，KVM和VMware虚拟机中，都支持这些功能。注意，VMware不支持基础区域的安全组。"
+
+# 5ac573ae5f4345aeb143a5fcc101524d
+#: ../../managing_networks.rst:953
+msgid "Use Cases"
+msgstr "使用案例"
+
+# 872874841bbe414a88684eb2a0045657
+#: ../../managing_networks.rst:955
+msgid "Some of the use cases are described below:"
+msgstr "一些使用案例见以下描述"
+
+# d5c27060797b4aee9174ebb56ffef918
+#: ../../managing_networks.rst:959
+msgid ""
+"Network devices, such as firewalls and load balancers, generally work best "
+"when they have access to multiple IP addresses on the network interface."
+msgstr "网络设备，如防火墙或负责均衡设备，一般来讲，当他们在网络接口上接入更多的IP地址时，他们能够更好的工作。"
+
+# 24ce123387844169a49487bc30845b7a
+#: ../../managing_networks.rst:965
+msgid ""
+"Moving private IP addresses between interfaces or instances. Applications "
+"that are bound to specific IP addresses can be moved between instances."
+msgstr "在接口和实例中迁移IP地址。绑定到特定IP地址的应用可以在实例中迁移。"
+
+# 0c37cb7a4c434f399e9d45b1c2e472e9
+#: ../../managing_networks.rst:971
+msgid ""
+"Hosting multiple SSL Websites on a single instance. You can install multiple"
+" SSL certificates on a single instance, each associated with a distinct IP "
+"address."
+msgstr "在单个实例上开启多个SSL网站。可以在单个实例上安装多个SSL认证，每一个认证都关联一个单独的IP地址。"
+
+# d4f7b4962530468a906a498acca4bae2
+# 3da7bf4ad1544749bab36764d2d447ef
+#: ../../managing_networks.rst:976 ../../managing_networks.rst:6315
+msgid "Guidelines"
+msgstr "指南"
+
+# d6caf12c9309436d9de8f99f9c7543c3
+#: ../../managing_networks.rst:978
+msgid ""
+"To prevent IP conflict, configure different subnets when multiple networks "
+"are connected to the same VM."
+msgstr "为防止IP冲突，当多个网络连接至同一个虚拟机时，要配置不同的子网。"
+
+# 16aeec8d7d974a11ab5270669432a394
+#: ../../managing_networks.rst:982
+msgid "Assigning Additional IPs to a VM"
+msgstr "指定额外的IP给虚拟机"
+
+# 034b4e6e920d4b1b819935e74e2b858c
+#: ../../managing_networks.rst:986
+msgid "Log in to the CloudStack UI."
+msgstr "登录到CloudStack的界面"
+
+# 6a36c11f314b4a73ae436cedecc70f5e
+#: ../../managing_networks.rst:990
+msgid "In the left navigation bar, click Instances."
+msgstr "在左侧导航栏，点击实例"
+
+# a8208d3a66ae4646bb1c56d1ecb10311
+#: ../../managing_networks.rst:994
+msgid "Click the name of the instance you want to work with."
+msgstr "点击拟配置的实例"
+
+# 3614c5b73e634141848b9ffd09823e34
+#: ../../managing_networks.rst:998
+msgid "In the Details tab, click NICs."
+msgstr "在详细 页签，点击网卡"
+
+# 9ddaf912d7f64aa791244c3f89f4f87e
+#: ../../managing_networks.rst:1002
+msgid "Click View Secondary IPs."
+msgstr "点击查看二级地址"
+
+# 41a35e39fad3445a94b912212054ec76
+#: ../../managing_networks.rst:1006
+msgid ""
+"Click Acquire New Secondary IP, and click Yes in the confirmation dialog."
+msgstr "点击获取新二级IP，在确认对话框点击确定。"
+
+# 966f02979ce94ebfad48594d314843e6
+#: ../../managing_networks.rst:1009
+msgid ""
+"You need to configure the IP on the guest VM NIC manually. CloudStack will "
+"not automatically configure the acquired IP address on the VM. Ensure that "
+"the IP address configuration persist on VM reboot."
+msgstr "需要手动配置来宾虚拟机的网卡。在虚拟机上，CloudStack不会自动配置获取IP。确保在虚拟机重启IP地址配置仍有效。"
+
+# 6f93e046959a4ebd9133806cbf00c179
+#: ../../managing_networks.rst:1013
+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 StaticNAT "
+"rules."
+msgstr "稍等一会，新的IP地址会出现，状态栏为会显示为分配。现在可以在端口转发或静态NAT规则中使用此IP地址了。"
+
+# 584ea105deaf4c149e1f4a22e7c76f9c
+#: ../../managing_networks.rst:1018
+msgid "Port Forwarding and StaticNAT Services Changes"
+msgstr "更改端口转发和静态NAT服务"
+
+# 66fa989a4cf444159810d5b86fe29d71
+#: ../../managing_networks.rst:1020
+msgid ""
+"Because multiple IPs can be associated per NIC, you are allowed to select a "
+"desired IP for the Port Forwarding and StaticNAT services. The default is "
+"the primary IP. To enable this functionality, an extra optional parameter "
+"'vmguestip' is added to the Port forwarding and StaticNAT APIs "
+"(enableStaticNat, createIpForwardingRule) to indicate on what IP address NAT"
+" need to be configured. If vmguestip is passed, NAT is configured on the "
+"specified private IP of the VM. if not passed, NAT is configured on the "
+"primary IP of the VM."
+msgstr "因为每一个网卡都可关联至多IP，CloudStack可以允许为端口转发及静态NAT服务选择一个目标IP。默认为主IP。为开启此功能，另一个可选的配置参数 虚拟机来宾IP 需要被加至端口转发及静态NAT 的API中去（开启静态NAT，创建IP端口转发），以示IP地址NAT需要配置。如果虚拟机来宾IP 没有设置，NAT会配置在虚拟机的私有IP上，如果设置了，NAT会配置在虚拟机的主IP上。"
+
+# d56668f88c1b4778956f3e78eb0af4f3
+#: ../../managing_networks.rst:1030
+msgid "About Multiple IP Ranges"
+msgstr "关于多IP范围"
+
+# a425fadff6f24df8a703773e76e1da84
+#: ../../managing_networks.rst:1032
+msgid "The feature can only be implemented on IPv4 addresses."
+msgstr "这些功能仅能在IPV4的地址是实现。"
+
+# 085d7bcb306c4df9b4bcb062fa965779
+#: ../../managing_networks.rst:1034
+msgid ""
+"CloudStack provides you with the flexibility to add guest IP ranges from "
+"different subnets in Basic zones and security groups-enabled Advanced zones."
+" For security groups-enabled Advanced zones, it implies multiple subnets can"
+" be added to the same VLAN. With the addition of this feature, you will be "
+"able to add IP address ranges from the same subnet or from a different one "
+"when IP address are exhausted. This would in turn allows you to employ "
+"higher number of subnets and thus reduce the address management overhead. To"
+" support this feature, the capability of ``createVlanIpRange`` API is "
+"extended to add IP ranges also from a different subnet."
+msgstr "在基础区域以及高级区域的开启安全组，CloudStack能够让你从不同的子网添加来宾IP范围。对于高级区域的开启安全组，多个子网可被加至同一个VLAN。随着此功能的增加，当IP地址耗尽时，你能够从同一个子网或从不同的子网添加IP范围。这会允许你添加更多的子网，因此减少了了地址管理的问题。为支持这一特性，创建VLANIP范围的API被加以扩展，这样就能从不同的子网添加IP范围"
+
+# a916ea5fa2a3442cac9346d464c33b3c
+#: ../../managing_networks.rst:1045
+msgid ""
+"Ensure that you manually configure the gateway of the new subnet before "
+"adding the IP range. Note that CloudStack supports only one gateway for a "
+"subnet; overlapping subnets are not currently supported."
+msgstr "确实在添加IP范围前，手动配置了子网的网关。注意，CloudStack仅支持一个子网有一个网关。不支持重叠的子网。"
+
+# 0cb128b2b4964c4c94d50a7d4f4c113d
+#: ../../managing_networks.rst:1049
+msgid ""
+"Use the ``deleteVlanRange`` API to delete IP ranges. This operation fails if"
+" an IP from the remove range is in use. If the remove range contains the IP "
+"address on which the DHCP server is running, CloudStack acquires a new IP "
+"from the same subnet. If no IP is available in the subnet, the remove "
+"operation fails."
+msgstr "使用删除VLAN范围的API删除IP范围。如果拟删除的IP在被使用时，此操作会失败。如果删除的范围包含DHCP服务器拟分配的IP地址CloudStack会从同一个子网下获取新的IP。如果在子网内没有可供利用的IP时，删除操作会失败。"
+
+# 5c50556940324ae1a2c2f33b4e3be74c
+#: ../../managing_networks.rst:1055
+msgid "This feature is supported on KVM, xenServer, and VMware hypervisors."
+msgstr "在KVM, xenServer以及VMware虚拟机中，都支持这项功能。 "
+
+# 86f5b04f9bf84ff4a0162e548a43ed45
+#: ../../managing_networks.rst:1058
+msgid "About Elastic IP"
+msgstr "关于弹性IP"
+
+# 1abc932ae33e4097ad9d5a7c01466858
+#: ../../managing_networks.rst:1060
+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 is down, the IP address can be "
+"reassigned to a new VM in your account."
+msgstr "弹性IP（EIP）地址是指与帐户关联的IP地址，能起到静态IP地址的作用。帐户所有者能完全控制隶属于此账户的弹性IP。作为帐户拥有者，你可以从你帐户的EIP池中选择一个IP分配给虚拟机。如果后续需要，你可以继续分配此IP地址给另一个虚拟机。在VM宕机时，此功能特别有用。此IP地址可以重新指定给一个新的虚拟机，而不是取代已经宕机的虚拟机。"
+
+# 6f92b16714d4455c9c0d07422b7a5278
+#: ../../managing_networks.rst:1069
+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 "与公共IP地址一样，弹性IP地址通过使用静态NAT关联至与之相关的私有IP地址。在起用了EIP的基础域中，EIP的服务与静态NAT的服务一一对应。默认的网络方案，默认共享EIP与负载均衡网络方案，在区域部署了NetScaler设备的前提下，能够提供EIP以及ELB网络服务。参见以下更详细的说明。"
+
+# 1917b806df094374b24b204ab96801f8
+#: ../../managing_networks.rst:1077
+msgid "|eip-ns-basiczone.png: Elastic IP in a NetScaler-enabled Basic Zone.|"
+msgstr "|eip-ns-basiczone.png: Elastic IP in a NetScaler-enabled Basic Zone.|"
+
+# 3b1d323c9feb4e9ba7ca76be6aaad6b2
+#: ../../managing_networks.rst:1079
+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 data center goes through the firewall."
+msgstr "在图中，NetScaler设备对CloudStack的实例而言是一个默认的入口或出口，防火墙是剩余数据中心的出口或入口。Netscaler对来宾网络提供负载均衡以及静态NAT的服务。在机架和管理服务器上，来宾流量是不同的子网或VLAN。在数据中心的核心交换机的基础路由策略是通过NetScaler转发公共流量，其他数据中心的流量则通过防火墙。"
+
+# d73486cd06ff42a3b7ae00d650f94b85
+#: ../../managing_networks.rst:1088
+msgid "The EIP work flow is as follows:"
+msgstr "EIP的工作流如下："
+
+# c76961037d5e4684aae701d14e8628ef
+#: ../../managing_networks.rst:1092
+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 "当部署一个用户虚拟机时，会从区域配置的IP中自动获得一个公共IP。这个IP为虚拟机帐户所拥有。"
+
+# 113a0b56fa5c4d588763310f3344c045
+#: ../../managing_networks.rst:1098
+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 "每一个虚拟机都有自己的私有IP。当来客户虚拟机启动时，通过使用在公共IP和私有IP之间的入口网络地址转换（INAT）以及预留地址转换（RNAT），NetScaler设备可以提供静态NAT"
+
+# 26464e6616334eba867bfbedcd8b9b32
+#: ../../managing_networks.rst:1103
+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 "入口网络地址转换（INAT）是NetScaler支持的一类NAT类型，在此类型中，来自公共网络（如Internet)的数据包中的目标IP地址被私有网络中虚拟机的私有地址取代。预留地址转换（RNAT）也是NetScaler支持的一类NAT类型，私有网络中虚拟机产生的数据包中的源IP地址被公共IP地址取代。"
+
+# c24df2c0e244417bac058ee69288159e
+#: ../../managing_networks.rst:1107
+msgid "This default public IP will be released in two cases:"
+msgstr "默认的公共IP在两种情况下会被释放："
+
+# e69a190aa6ff4094a1376bbd1a48c806
+#: ../../managing_networks.rst:1111
+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 "当虚拟机停止时。当虚拟机启动时，可以重新获取一个新的公共IP，并不必须是从公共IP地址池中最初分配的那一个。"
+
+# ae09bc75005442799a101c13ee164cfe
+#: ../../managing_networks.rst:1117
+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 "当用户获取公共IP（弹性IP）时。这些公共IP与帐户相关联，但不与任何私有IP相关。然而，用户可以开启静态NAT将帐户中虚拟机的私有IP与之关联。对应公共IP的静态NAT规则可随时取消。当静态NAT关闭时，会从地址池中分配的一个新的公共IP，并不必须是最初分配的那一个。"
+
+# 85b2631843ed40888b2ca7fe400962fd
+#: ../../managing_networks.rst:1125
+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 and enable static NAT."
+msgstr "对部署而言，公共IP会受限于资源，可以灵活的选择默认不分配公共IP。可以在开启了EIP的基础区域中，通过关联公共IP选项来打开或关闭自动公共IP指定。如果在创建网络方案时，你关闭了自动公共IP指定，则在使用此网络方案部署时，仅会分配一个私有IP给虚拟机。此后，用户虚拟机可以获取一个IP，并可以开启静态NAT。"
+
+# 94a57e6c08fb4beeb2cc92ada6ed0e19
+#: ../../managing_networks.rst:1134
+msgid ""
+"For more information on the Associate Public IP option, see the "
+"Administration Guide."
+msgstr "要了解更多关于关联公共IP的选项，请参考管理员向导。"
+
+# 51ff3fc654054203b273f9c148ae18b5
+#: ../../managing_networks.rst:1137
+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 "设计关联公共IP的功能，仅是为使用用户虚拟机。系统虚拟机仍然默认会获取公共IP和私有IP，与网络配置并不相关。"
+
+# 83364c7e0dd94f759842ac386a8cac79
+#: ../../managing_networks.rst:1139
+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 "在基础区域中，使用默认具有EIP和ELB服务的网络方案来创建共享网络时，仍然会给每一个用户虚拟机分配公共IP。"
+
+# 342239c2715c475b88c10804e3612a51
+#: ../../managing_networks.rst:1144
+msgid "Portable IPs"
+msgstr "端口IP"
+
+# dd5fc98d73bc4d75beeb09ce0439d181
+#: ../../managing_networks.rst:1147
+msgid "About Portable IP"
+msgstr "关于端口IP"
+
+# 89820f26aa2645078ccb72b82efc9dfe
+#: ../../managing_networks.rst:1149
+msgid ""
+"Portable IPs in CloudStack are region-level pool of IPs, which are elastic "
+"in nature, that can be transferred across geographically separated zones. As"
+" an administrator, you can provision a pool of portable public IPs at region"
+" level and are available for user consumption. The users can acquire "
+"portable IPs if admin has provisioned portable IPs at the region level they "
+"are part of. These IPs can be use for any service within an advanced zone. "
+"You can also use portable IPs for EIP services in basic zones."
+msgstr "在CloudStack中，端口IP是地域级的IP地址池，其天然具有弹性，亦即可以在地理隔离的区域中进行转发。作为管理员,可以在地域级提供IP地址池供用户使用。如果在用户所属的地域，其管理员提供了端口IP，用户就可以获取此类IP。在高级区域内，这些IP可用于任一服务。也可以在基础区域中为EIP服务使用端口IP。"
+
+# bd4cf0b29f8b41b3b03e37f656c52501
+#: ../../managing_networks.rst:1158
+msgid "The salient features of Portable IP are as follows:"
+msgstr "端口IP的主要功能如下："
+
+# 855ab24aced14fa18033b90699abf066
+#: ../../managing_networks.rst:1162
+msgid "IP is statically allocated"
+msgstr "IP是静态分配的。"
+
+# 7e45d53e50814ec584c37135e430715f
+#: ../../managing_networks.rst:1166
+msgid "IP need not be associated with a network"
+msgstr "IP与网络无关。"
+
+# f4869a8c48e8434ea57e20c6cc65cf55
+#: ../../managing_networks.rst:1170
+msgid "IP association is transferable across networks"
+msgstr "IP关联是可以通过网络转发的。"
+
+# 2f9e4bbd9a5c4a61957b15982551f2e9
+#: ../../managing_networks.rst:1174
+msgid "IP is transferable across both Basic and Advanced zones"
+msgstr "IP可以在基础区域和高级区域中转发。"
+
+# ea6d679d393d4bcfa494249d365ba374
+#: ../../managing_networks.rst:1178
+msgid "IP is transferable across VPC, non-VPC isolated and shared networks"
+msgstr "IP可通过VPC，非VPC隔离和共享网络进行转发。"
+
+# afa26b14dffe40119ee655d8132db452
+#: ../../managing_networks.rst:1182
+msgid "Portable IP transfer is available only for static NAT."
+msgstr "端口IP转发仅对静态NAT可用。"
+
+# 671509538e074821aee5d282b4fd3822
+#: ../../managing_networks.rst:1187
+msgid ""
+"Before transferring to another network, ensure that no network rules "
+"(Firewall, Static NAT, Port Forwarding, and so on) exist on that portable "
+"IP."
+msgstr "在转发至另一网络前，确保没有网络规则（如防火墙，静态NAT，端口转发等等）不存在于端口IP。"
+
+# a10fe6016ca4432d9466323adc5feafa
+#: ../../managing_networks.rst:1192
+msgid "Configuring Portable IPs"
+msgstr "配置端口IP"
+
+# 323070f73d46451b97228b1b4aadaa54
+#: ../../managing_networks.rst:1200
+msgid "In the left navigation, click Regions."
+msgstr "在左侧导航栏中，点击地域"
+
+# 428125e4de8d4140af2bbdfcd4ecc332
+#: ../../managing_networks.rst:1204
+msgid "Choose the Regions that you want to work with."
+msgstr "选择拟修改的地域。"
+
+# eed1d708ff224966a3d021ab2bc33aa6
+#: ../../managing_networks.rst:1208
+msgid "Click View Portable IP."
+msgstr "点击查看端口IP"
+
+# abc03c1eb418441fb10a7cf6beb37fea
+#: ../../managing_networks.rst:1212
+msgid "Click Portable IP Range."
+msgstr "点击端口IP范围"
+
+# 595f33e914024c0a86540527bc370258
+#: ../../managing_networks.rst:1214
+msgid "The Add Portable IP Range window is displayed."
+msgstr "会出现 添加端口IP范围的窗口"
+
+# ca11f239cc8449a6817014a3adcd61a0
+#: ../../managing_networks.rst:1222
+msgid ""
+"**Start IP/ End IP**: A range of IP addresses that are accessible from the "
+"Internet and will be allocated to guest VMs. Enter the first and last IP "
+"addresses that define a range that CloudStack can assign to guest VMs."
+msgstr "**起始IP/结束IP**: 从Internet可以访问的一个IP地址范围，将会分配给客户虚拟机。输入起始IP以及结束IP，定义CloudStack指定给客户虚拟机的IP范围。"
+
+# 6c64c167231b40a68bfe26799c8054c3
+#: ../../managing_networks.rst:1229
+msgid ""
+"**Gateway**: The gateway in use for the Portable IP addresses you are "
+"configuring."
+msgstr "**网关**: 配置端口IP地址所使用的网关。"
+
+# 83455a09e71a4eccb3755e02bd14515c
+#: ../../managing_networks.rst:1234
+msgid "**Netmask**: The netmask associated with the Portable IP range."
+msgstr "**掩码**: 与端口IP范围关联的掩码。"
+
+# 7b8fbceeaf074302abbd838f0e2849bf
+#: ../../managing_networks.rst:1238
+msgid "**VLAN**: The VLAN that will be used for public traffic."
+msgstr "**VLAN**: 公共流量拟使用的VLAN。"
+
+# d850eac9d4014f0dab3417fab28601f7
+#: ../../managing_networks.rst:1245
+msgid "Acquiring a Portable IP"
+msgstr "获取端口IP。"
+
+# 3262a0725955438a99e78981176d092f
+# 701bcf108f834cdc9c4ea748e804dab0
+# 2859adde9cb44f6e970e1a0651717bed
+# e93c68f572f04989afefcb87f1716ec4
+# 5efad310be724f029a2e40ffd479c432
+#: ../../managing_networks.rst:1257 ../../managing_networks.rst:3208
+#: ../../managing_networks.rst:3251 ../../managing_networks.rst:3294
+#: ../../managing_networks.rst:3370
+msgid "Click the name of the network where you want to work with."
+msgstr "点击拟修改的网络名称。"
+
+# 305ab6c53fda46d8adf4a49df4f72b73
+# 3186a0f1dbbd4b36afd65ce287083ef4
+# 77cf6faa7c404c33bddce8721952e2e2
+# 6fbd7a5b4b7e4fe684956b795c3516f8
+# 6662b46aca0349ffb4f7db65473cf5a4
+# e6ede01e32f44d8d9eb51185ac8cca93
+# c003065bf88441dc838fb6ff067c1d46
+#: ../../managing_networks.rst:1261 ../../managing_networks.rst:2170
+#: ../../managing_networks.rst:3212 ../../managing_networks.rst:3255
+#: ../../managing_networks.rst:3298 ../../managing_networks.rst:3374
+#: ../../managing_networks.rst:3784
+msgid "Click View IP Addresses."
+msgstr "点击查看IP地址。"
+
+# 3cb9985604264815812c496744d99e7a
+# b3b02650cb5849d29899feb56b041267
+#: ../../managing_networks.rst:1265 ../../managing_networks.rst:3216
+msgid "Click Acquire New IP."
+msgstr "点击获取新IP。"
+
+# 0fd88d76e0454a0aafadff6be75ab526
+# 25404011fc7044529f48e7fb157f04ed
+#: ../../managing_networks.rst:1267 ../../managing_networks.rst:3218
+msgid "The Acquire New IP window is displayed."
+msgstr "获取新IP的窗口会出现。"
+
+# ead81d2ea1984be4874b71915d73fe10
+# 6fe5747d6b7547a8918070f73c52cc78
+#: ../../managing_networks.rst:1271 ../../managing_networks.rst:3222
+msgid "Specify whether you want cross-zone IP or not."
+msgstr "说明是否需要IP跨区。"
+
+# d4620b5751e246e48d4c00aca1d4a8f3
+#: ../../managing_networks.rst:1275
+msgid "Click Yes in the confirmation dialog."
+msgstr "在确认对话框中点击确定。"
+
+# 99771ddd9716455ba6a961284174f20b
+# 1ff8f2a384d445a8ba816f2443f9a096
+#: ../../managing_networks.rst:1277 ../../managing_networks.rst:3230
+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 "稍等一会，新的IP地址会出现，状态栏为会显示为分配。现在可以在端口转发或静态NAT规则中使用此IP地址了。"
+
+# e9a2afafc0df48bcba35924913d45e73
+#: ../../managing_networks.rst:1282
+msgid "Transferring Portable IP"
+msgstr "便携式IP"
+
+# 65ca926473184157a1cfd41612675661
+#: ../../managing_networks.rst:1284
+msgid ""
+"An IP can be transferred from one network to another only if Static NAT is "
+"enabled. However, when a portable IP is associated with a network, you can "
+"use it for any service in the network."
+msgstr "IP要从一个网络转换至另一网络的话，只需启用静态NAT。但是，当一个portable IP对应一个网络的时候，你可以在网络中为任何服务使用它 。"
+
+# 8afb23c700a44791bb6a9fa4690d1649
+#: ../../managing_networks.rst:1288
+msgid ""
+"To transfer a portable IP across the networks, execute the following API:"
+msgstr "要跨网络转换一个portable IP，执行下列API："
+
+# 55a1869308ee4aed849674dc2535b805
+#: ../../managing_networks.rst:1295
+msgid ""
+"Replace the UUID with appropriate UUID. For example, if you want to transfer"
+" a portable IP to network X and VM Y in a network, execute the following:"
+msgstr "用正确的UUID替换此处的UUID。比如，如果你想转换一个portable IP至X网络和一个网络中的VM Y，请执行下列操作："
+
+# 3afd351582954a49b746d509abba4eac
+#: ../../managing_networks.rst:1304
+msgid "Multiple Subnets in Shared Network"
+msgstr "共享网络中的多子网"
+
+# 9a2eae7b8f84440f90cd0402d4ed0d76
+#: ../../managing_networks.rst:1306
+msgid ""
+"CloudStack provides you with the flexibility to add guest IP ranges from "
+"different subnets in Basic zones and security groups-enabled Advanced zones."
+" For security groups-enabled Advanced zones, it implies multiple subnets can"
+" be added to the same VLAN. With the addition of this feature, you will be "
+"able to add IP address ranges from the same subnet or from a different one "
+"when IP address are exhausted. This would in turn allows you to employ "
+"higher number of subnets and thus reduce the address management overhead. "
+"You can delete the IP ranges you have added."
+msgstr "CloudStack为你提供了在基本zones和启用了安全组的高级zones不同的子网中灵活的添加来宾IP段功能 。在启用了安全组的高级zones中，这意味着多子网可以被添加到同一个VLAN。这个特性还意味着，当IP地址用尽的时候，你可以从同一个子网或从不同的子网添加IP地址范围。这将允许你使用更多的子网，降低地址管理工作量。你也可以删除已经添加的IP地址范围。"
+
+# 344b838f0b0841728cb18a682c1962e2
+# ca130580b3e848d59bbd0823702a71ad
+# 9d4bbe7d6b854394bcbb260e68f1226a
+#: ../../managing_networks.rst:1317 ../../managing_networks.rst:2885
+#: ../../managing_networks.rst:3426
+msgid "Prerequisites and Guidelines"
+msgstr "先决条件和指南"
+
+# 231696a9da0c47e5be1d4fec098a8b7f
+#: ../../managing_networks.rst:1321
+msgid "This feature can only be implemented:"
+msgstr "这个特性只能被实现在："
+
+# e11af27c4f9b4a68aa2b824c8d51ef26
+#: ../../managing_networks.rst:1325
+msgid "on IPv4 addresses"
+msgstr "IPv4地址"
+
+# 89a310c9cc9a4cc0b046da60d4db626f
+#: ../../managing_networks.rst:1329
+msgid "if virtual router is the DHCP provider"
+msgstr "如果虚拟路由是由DHCP提供的"
+
+# 2f901469d8a547669181457a79ea3825
+#: ../../managing_networks.rst:1333
+msgid "on KVM, xenServer, and VMware hypervisors"
+msgstr "在KVM，XenServer和VMware hypervisors"
+
+# 07ac9be1fbd949109da3f8269a75cd31
+#: ../../managing_networks.rst:1337
+msgid ""
+"Manually configure the gateway of the new subnet before adding the IP range."
+msgstr "在添加IP范围之前，手动配置新子网的网关。"
+
+# fd0dee06ed544e709ea404a01e2141a4
+#: ../../managing_networks.rst:1342
+msgid ""
+"CloudStack supports only one gateway for a subnet; overlapping subnets are "
+"not currently supported"
+msgstr "CloudStack只支持一个子网对应一个网关；交叉子网目前不支持。"
+
+# cfe0f1c81e094655b1cf2158397f8beb
+#: ../../managing_networks.rst:1346
+msgid "Adding Multiple Subnets to a Shared Network"
+msgstr "给共享网络添加多子网"
+
+# 2239434247834913b8b23dab3f7f896d
+#: ../../managing_networks.rst:1358
+msgid ""
+"On Zones, click View More, then click the zone to which you want to work "
+"with.."
+msgstr "在Zones上，点击查看更多，然后点击你要进行操作的zone.."
+
+# 52b4f5c3dc6c4c96a91c21e53b5f6ba7
+#: ../../managing_networks.rst:1363
+msgid "Click Physical Network."
+msgstr "点击物理网络。"
+
+# d545de9168774122b8d39fe9b88db0f9
+#: ../../managing_networks.rst:1371
+msgid "Click Networks."
+msgstr "点击网络。"
+
+# 201b95be96f741419b7a53c915e3da38
+#: ../../managing_networks.rst:1375
+msgid "Select the networks you want to work with."
+msgstr "选择你想要操作的网络。"
+
+# b1dafa11c6dd48aaba7215933fc61640
+#: ../../managing_networks.rst:1379
+msgid "Click View IP Ranges."
+msgstr "点击查看IP范围。"
+
+# 962df84772504a178c0760d6862328be
+#: ../../managing_networks.rst:1383
+msgid "Click Add IP Range."
+msgstr "点击添加IP范围。"
+
+# a8c9f66de4e84e56882ecb276ca04e41
+#: ../../managing_networks.rst:1385
+msgid "The Add IP Range dialog is displayed, as follows:"
+msgstr "显示的添加IP范围对话框如下："
+
+# ae7f538d814144019a90e1b0ac6f4a3d
+#: ../../managing_networks.rst:1387
+msgid "|add-ip-range.png: adding an IP range to a network.|"
+msgstr "|add-ip-range.png: adding an IP range to a network.|"
+
+# 0884d274eba74f889ae1c3abffff98dd
+# 03a1c57fd13d4fdb9f6c63ec4afcc907
+#: ../../managing_networks.rst:1393 ../../managing_networks.rst:5063
+msgid "All the fields are mandatory."
+msgstr "所有的区域必须填写的。"
+
+# 8da5ac3902824555b54847009a765ed7
+# fe107d12592248a982087f39da19a41a
+#: ../../managing_networks.rst:1397 ../../managing_networks.rst:5081
+msgid ""
+"**Gateway**: The gateway for the tier you create. Ensure that the gateway is"
+" within the Super CIDR range that you specified while creating the VPC, and "
+"is not overlapped with the CIDR of any existing tier within the VPC."
+msgstr "**网关**：你创建网络层的网关。确保网关在你创建VPC时指定的超级CIDR范围内，并且不能与已存在VPC的任何网络层的CIDR重叠。"
+
+# d23bd452fc4d46579356f5ede9152d95
+# af646832ee3f44ebaa1213c5db09bb4a
+#: ../../managing_networks.rst:1404 ../../managing_networks.rst:5098
+msgid "**Netmask**: The netmask for the tier you create."
+msgstr "**子网掩码**：你创建的网络层的子网掩码。"
+
+# 86f10e90777a4711964d8a8df3a0e45c
+# 04b52f8b675747ee8a9c73e86c123710
+#: ../../managing_networks.rst:1406 ../../managing_networks.rst:5100
+msgid ""
+"For example, if the VPC CIDR is 10.0.0.0/16 and the network tier CIDR is "
+"10.0.1.0/24, the gateway of the tier is 10.0.1.1, and the netmask of the "
+"tier is 255.255.255.0."
+msgstr "比如，如果VPC CIDR是10.0.0.0/16并且该网络层CIDR是10.0.1.0/24，那么这个网络层的网关是10.0.1.1，子网掩码是255.255.255.0."
+
+# 3bdc377e66c842a4a3f09450a0832e67
+#: ../../managing_networks.rst:1412
+msgid ""
+"**Start IP/ End IP**: A range of IP addresses that are accessible from the "
+"Internet and will be allocated to guest VMs. Enter the first and last IP "
+"addresses that define a range that CloudStack can assign to guest VMs ."
+msgstr "**起始/结束IP**：从互联网获得的和将被分配给来宾VMsIP地址范围。输入第一个和最后一个IP地址，该地址范围定义的是CloudStack能分配给来宾VMs的范围。"
+
+# b6a0de7ae6b643a3b425583d43f6163e
+#: ../../managing_networks.rst:1422
+msgid "Isolation in Advanced Zone Using Private VLAN"
+msgstr "使用Private VLAN隔离高级Zone中的网络"
+
+# 4f75858c33ec4279a864c4b208e29b2b
+#: ../../managing_networks.rst:1424
+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 users’ VMs."
+msgstr "在共享网络中的隔离来宾流量能被Private VLAN（PVLAN）获取。PVLANs提供同一个VLAN里端口间的2层网络隔离。在启用了PVLAN的共享网络，一个用户VM不能到达其他用户VM，但是他们能与DHCP服务器和网关通讯，反过来这样能允许用户去控制网络内部的流量，并且帮助他们像阻止与其他用户VMs通讯一样的去部署无需通讯的多个应用程序。"
+
+# 2b100ae9fa4e4eaea15ed0c9c965697f
+#: ../../managing_networks.rst:1435
+msgid "Isolate VMs in a shared networks by using Private VLANs."
+msgstr "使用PVLAN在共享网络中隔离VMs。"
+
+# 72cb21f4bdaa4f6c88f7f1253969f497
+#: ../../managing_networks.rst:1439
+msgid "Supported on KVM, XenServer, and VMware hypervisors"
+msgstr "在KVM，XenServer和VMware hypervisors中支持"
+
+# 64e4f6f904e145cc94c88300b2f6f1ec
+#: ../../managing_networks.rst:1443
+msgid ""
+"PVLAN-enabled shared network can be a part of multiple networks of a guest "
+"VM."
+msgstr "启用了PVLAN的共享网络可以是来宾VM的多个网络的一部分。"
+
+# 39b527fd98914ef4ae1f7cd5d5a083c3
+#: ../../managing_networks.rst:1447
+msgid "About Private VLAN"
+msgstr "关于Private VLAN"
+
+# ffcf29c6500a4e3a897fefd357efafa1
+#: ../../managing_networks.rst:1449
+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 VLAN that is being divided "
+"into smaller groups is called Primary, which implies that all VLAN pairs in "
+"a private VLAN share the same Primary VLAN. All the secondary VLANs exist "
+"only inside the Primary. Each Secondary VLAN has a specific VLAN ID "
+"associated to it, which differentiates one sub-domain from another."
+msgstr "在以太网交换机中，VLAN是二层网络中的一个主机之间主机能建立直接通讯的广播域 。Private VLAN被设计成一个标准的VLAN的延伸，为了进一步细分逻辑广播域。一个规则的VLAN是单一广播域，但是一个 private VLAN将一个较大的VLAN广播域划分为较小的多个子域。子域表现为一对VLANs：一个主VLAN和一个辅助VLAN。被划分为较小组的原始VLAN叫主，这意味着所有的在private VLAN中的VLAN对共享着同一个主VLAN。所有的辅助VLANs存在与主VLAN中。每个辅助VLAN有一个特定的区别于其他子域VLAN ID。"
+
+# dadf77ad95da46d29d655fa1b5c88836
+#: ../../managing_networks.rst:1462
+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 "在private VLAN中有三种端口类型，它们实质上决定了所包含的主机的流量走势。每组端口都有自己唯一的策略，它能控制配置同一个private VLAN域中连接到端口的主机与其他已连接主机的通讯。使用下面三种端口定义中的一种来配置每个PVLAN对中的主机："
+
+# 338ab35c29694e549d0f63e57cf3ecfc
+#: ../../managing_networks.rst:1471
+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 "**混杂模式（Promiscuous）**：混杂模式的端口能与所有的接口通讯，包括可通讯与隔离属于辅助VLANs的主机端口。在混杂模式中，主机被连接到混在模式端口并且能够直接与主VLAN和辅助VLAN中的资源。典型的连接到混杂模式端口的是路由器，DHCP服务器和其他受信任的设备。"
+
+# 1eb75b61178b4a8da29196b19e0755f1
+#: ../../managing_networks.rst:1481
+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 "**隔离(Isolated)VLANs**: 隔离模式VLAN中的端口不能与其他二层网络中的端口通讯。连接隔离模式端口上的主机只能直接与混杂模式下的资源通讯。如果你的客户设备只访问网关路由器，请将其附加至隔离端口。"
+
+# 3c344baffb3649a3a99b4762947818ae
+#: ../../managing_networks.rst:1489
+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 communicate among themselves, deploy them in "
+"community ports."
+msgstr "**Community VLANs**：中的端口能与其他端口和混杂模式下的端口通讯，但是他们不能与二层网络中的其他community VLAN中的端口通讯。在Community模式下，主机能与同一community中的主机和连接到混杂模式中的主VLAN的主机可以通讯。如果你的客户有两个设备需要与其他客户的设备隔离，但是他们之间又要通讯，请将他们部署至 community 端口。"
+
+# a10ac6622d024e57899b845f7e847140
+#: ../../managing_networks.rst:1499
+msgid "For further reading:"
+msgstr "延伸阅读："
+
+# 5efde3c2b6894bd387b0f388d8bdeae3
+#: ../../managing_networks.rst:1503
+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 "`理解 Private VLANs <http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_25_see/configuration/guide/swpvlan.html#wp1038379>`__"
+
+# 02596ab9a4bd47daaed6a4272e786d9a
+#: ../../managing_networks.rst:1508
+msgid ""
+"`Cisco Systems' Private VLANs: Scalable Security in a Multi-Client "
+"Environment <http://tools.ietf.org/html/rfc5517>`__"
+msgstr "`Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment <http://tools.ietf.org/html/rfc5517>`__"
+
+# 886e828c09384218b5bd4f8cd224d968
+#: ../../managing_networks.rst:1513
+msgid ""
+"`Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview "
+"(1010691) <http://kb.vmware.com>`__"
+msgstr "`Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview (1010691) <http://kb.vmware.com>`__"
+
+# 6cb7c445963a491caff15981fe0b4ce4
+#: ../../managing_networks.rst:1521
+msgid "Use a PVLAN supported switch."
+msgstr "在支持的交换机上使用PVLAN。"
+
+# f7f97cd16eb24ff588d513c2d34ff289
+#: ../../managing_networks.rst:1523
+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 "参考 `Private VLAN Catalyst Switch Support Matrix <http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a0080094830.shtml>`__\\ for more information."
+
+# 09e5467647fd4eb6af74a6c1cb65b159
+#: ../../managing_networks.rst:1529
+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 "将所有能识别PVLAN的二层交换机之间互连，并且其中一个要连至一个路由器。主机连接到的所有端口需配置为trunk模式。打开VLAN管理，主VLAN（公共网络）和隔离的辅助VLAN端口。配置交换机连接到路由器的端口为PVLAN混杂trunk，这样可以为不识别PVLAN的路由器转换一个隔离的VLAN到主VLAN。"
+
+# 3eb08525c8114e1fade9c52b44c14c59
+#: ../../managing_networks.rst:1537
+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 "注意只有Cisco Catalyst 4500有PVLAN混杂trunk模式，可以连接所有普通VLAN和PVLAN到不能识别PVLAN的交换机。其他支持PVLAN的Catalyst交换机，在PVALN对中的每个交换机上使用级联线连接到上联交换机。"
+
+# e9c74dd366ef45f1be1d0793986d7f73
+#: ../../managing_networks.rst:1544
+msgid "Configure private VLAN on your physical switches out-of-band."
+msgstr "在你的物理交换机上使用带外管理配置private VLAN。"
+
+# 2ecc130e165749aba238d52a9a7f2486
+#: ../../managing_networks.rst:1548
+msgid "Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS)."
+msgstr "在XenServer和KVM上使用PVALN之前，请启用Open vSwitch (OVS)。"
+
+# 030698129200435e9f708d7cb120c98b
+#: ../../managing_networks.rst:1550
+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 "XenServer和KVM中的OVS不支持原生的PVLAN。因此，靠修改flow table，CloudStack为XenServer和KVM模拟OVS中的PVLAN。"
+
+# f6a73d4d4c73444dbf0a403921b5aa74
+#: ../../managing_networks.rst:1553
+msgid "Creating a PVLAN-Enabled Guest Network"
+msgstr "配置一个启用了PVLAN的来宾网络"
+
+# 740911b6b7d14c93bb243f861cbde303
+#: ../../managing_networks.rst:1613
+msgid ""
+"**Secondary Isolated VLAN ID**: The unique ID of the Secondary Isolated "
+"VLAN."
+msgstr "**辅助隔离VLAN ID**：辅助隔离VLAN的唯一ID。"
+
+# 33d01a6c72b3484991970c439ebe1b80
+#: ../../managing_networks.rst:1616
+msgid ""
+"For the description on Secondary Isolated VLAN, see `Section 15.14.1, “About"
+" Private VLAN” <#about-pvlan>`__."
+msgstr "更多关于辅助隔离VLAN的描述，请参考 `Section 15.14.1, “关于 Private VLAN” <#about-pvlan>`__."
+
+# 2c24eb1bc100495989166e76788319c0
+#: ../../managing_networks.rst:1679
+msgid "Security Groups"
+msgstr "安全组"
+
+# d331348078ea4de8a8dc8471c9cc3cce
+#: ../../managing_networks.rst:1682
+msgid "About Security Groups"
+msgstr "关于安全组"
+
+# f34bf064d0114b288f2f55f17a25f84a
+#: ../../managing_networks.rst:1684
+msgid ""
+"Security groups provide a way to isolate traffic to VMs. 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. Security groups are particularly useful in zones that use basic "
+"networking, because there is a single guest network for all guest VMs. In "
+"advanced zones, security groups are supported only on the KVM hypervisor."
+msgstr "安全组提供一种方法来隔离VMs流量。一个安全组是一组依照设置名为入口规则和出口规则来过滤他们进出流量的VMs，这些规则依靠与VM通讯的IP地址来过滤网络流量。安全组在使用基础网络的zones中尤为重要，因为这里只有一个来宾网络。在高级zones中，只有KVM hypervisor支持安全组。"
+
+# 5e82a09d657a4767acec9f22d782de51
+#: ../../managing_networks.rst:1693
+msgid ""
+"In a zone that uses advanced networking, you can instead define multiple "
+"guest networks to isolate traffic to VMs."
+msgstr "在一个使用高级网络的zone中，你可以改为定义多个来宾网络隔离流量至VMs。"
+
+# 79f27644dfcf4cf788bba960a7f3b5bf
+#: ../../managing_networks.rst:1695
+msgid ""
+"Each CloudStack account comes with a default security group that denies all "
+"inbound traffic and allows all outbound traffic. The default security group "
+"can be modified so that all new VMs inherit some other desired set of rules."
+msgstr "每个CloudStack账号匹配一个拒绝所有入站流量和允许所有出口流量的默认安全组 。可以编辑默认的安全组以便所有新VMs的策略继承一些的想要的设置。"
+
+# baa28941d5194fae811bbd88c61df125
+#: ../../managing_networks.rst:1700
+msgid ""
+"Any CloudStack user can set up any number of additional security groups. "
+"When a new VM is launched, it is assigned to the default security group "
+"unless another user-defined security group is specified. A VM can be a "
+"member of any number of security groups. Once a VM is assigned to a security"
+" group, it remains in that group for its entire lifetime; you can not move a"
+" running VM from one security group to another."
+msgstr "任何CloudStack用户可以增加任意数量的安全组。当一个新的VM运行起来的时候，它会被添加到默认安全组除非其他用户指定了其他安全组。一个VM可以是任何安全组的成员。一旦VM被添加到一个安全组，它会继承这个组的生命周期；你不能移动一台正在运行的VM到其他安全组。"
+
+# de98d0c1571a4cc18032b6472947663b
+#: ../../managing_networks.rst:1707
+msgid ""
+"You can modify a security group by deleting or adding any number of ingress "
+"and egress rules. When you do, the new rules apply to all VMs in the group, "
+"whether running or stopped."
+msgstr "你可以通过删除或添加任意的入口和出口策略来修改一个安全组。当你这么做的时候，新的策略会应用到组中的所有VMs，无论是运行的还是关机的。"
+
+# 6e7dbedd8ee140e1ad567e65c7ff552d
+#: ../../managing_networks.rst:1711
+msgid ""
+"If no ingress rules are specified, then no traffic will be allowed in, "
+"except for responses to any traffic that has been allowed out through an "
+"egress rule."
+msgstr "如果没有指定入口规则，那么流量会被禁止，除了已经允许通过一个出口规则响应任何流量 。"
+
+# 50b80901d7c24d66a23e838b0f4293d3
+#: ../../managing_networks.rst:1716
+msgid "Adding a Security Group"
+msgstr "添加一个安全组"
+
+# f870c727a4ba4b5fafdca88cc7a4b660
+#: ../../managing_networks.rst:1718
+msgid "A user or administrator can define a new security group."
+msgstr "一个用户或者管理员能定义一个新的安全组。"
+
+# 2bd568db435b4894a6594bdabb71b71f
+# ec651383a1084a9bb247059b0cb38cc8
+#: ../../managing_networks.rst:1726 ../../managing_networks.rst:1803
+msgid "In the left navigation, choose Network"
+msgstr "在左侧的导航栏，选择网络"
+
+# 20641ac9b26d48a8a2af8025a38b3550
+#: ../../managing_networks.rst:1730
+msgid "In Select view, choose Security Groups."
+msgstr "在选择视图中，选择安全组。"
+
+# 3b8b48dea99749bf821c45bf85f5edce
+#: ../../managing_networks.rst:1734
+msgid "Click Add Security Group."
+msgstr "点击添加安全组。"
+
+# da5c74165969469d9c2395eaaa3f94e6
+#: ../../managing_networks.rst:1738
+msgid "Provide a name and description."
+msgstr "提供一个名称和描述。"
+
+# cebb13c23de64a278615d79e7d92b3bc
+#: ../../managing_networks.rst:1744
+msgid "The new security group appears in the Security Groups Details tab."
+msgstr "新的安全组出现在安全组详细信息标签中。"
+
+# b0f1a7c4f9d74d0cbf905c6ce03546b8
+#: ../../managing_networks.rst:1748
+msgid ""
+"To make the security group useful, continue to Adding Ingress and Egress "
+"Rules to a Security Group."
+msgstr "要使安全组生效，继续给这个安全组添加入口和出口策略。"
+
+# 0c59765ee0c64629952434a87beb9d81
+#: ../../managing_networks.rst:1752
+msgid "Security Groups in Advanced Zones (KVM Only)"
+msgstr "高级区域中的安全组（只针对KVM）"
+
+# 33c22ff2d84d4c149fb2a3ba75f8689f
+#: ../../managing_networks.rst:1754
+msgid ""
+"CloudStack provides the ability to use security groups to provide isolation "
+"between guests on a single shared, zone-wide network in an advanced zone "
+"where KVM is the hypervisor. Using security groups in advanced zones rather "
+"than multiple VLANs allows a greater range of options for setting up guest "
+"isolation in a cloud."
+msgstr "以KVM作为虚拟机时，在单共享广域的网络内，CloudStack可以通过安全组来隔离客户。通过使用安全组而不是多VLAN，可以在云中隔离客户时具有更高的灵活性"
+
+# 0d98099524ba4909b604a7399ffc1bd8
+#: ../../managing_networks.rst:1760
+msgid "Limitations: The following are not supported for this feature:"
+msgstr "限制：下列不支持此功能"
+
+# cfee500d52ad40699096b1a8e4e389c1
+#: ../../managing_networks.rst:1764
+msgid ""
+"Two IP ranges with the same VLAN and different gateway or netmask in "
+"security group-enabled shared network."
+msgstr "在开启了安全组的共享网络内，同一VLAN内具有不同网关或掩码的二个IP范围，"
+
+# 6246185f1f154f93875963e698243930
+#: ../../managing_networks.rst:1769
+msgid ""
+"Two IP ranges with the same VLAN and different gateway or netmask in "
+"account-specific shared networks."
+msgstr "在共享网络的特殊帐户内，同一VLAN内具有不同网关或掩码的二个IP范围"
+
+# 1d7c154fd0c34eaf9711d6ec05f84dee
+#: ../../managing_networks.rst:1774
+msgid "Multiple VLAN ranges in security group-enabled shared network."
+msgstr "在开启了安全组共享网络的多VLAN范围"
+
+# d31b3ceda7e84ff09119957ddcbbdf2b
+#: ../../managing_networks.rst:1778
+msgid "Multiple VLAN ranges in account-specific shared networks."
+msgstr "在共享网络的特殊帐户内，多个VLAN范围"
+
+# 6eeb1f2182894bc383d39cb1f701fb27
+#: ../../managing_networks.rst:1780
+msgid ""
+"Security groups must be enabled in the zone in order for this feature to be "
+"used."
+msgstr "为使用此特性，在区域内必须开启安全组"
+
+# d9c879f6880c426dbe5cc14699e86c87
+#: ../../managing_networks.rst:1784
+msgid "Enabling Security Groups"
+msgstr "开启安全组"
+
+# 6038307bd32f4032b2cf2283627e5084
+#: ../../managing_networks.rst:1786
+msgid ""
+"In order for security groups to function in a zone, the security groups "
+"feature must first be enabled for the zone. The administrator can do this "
+"when creating a new zone, by selecting a network offering that includes "
+"security groups. The procedure is described in Basic Zone Configuration in "
+"the Advanced Installation Guide. The administrator can not enable security "
+"groups for an existing zone, only when creating a new zone."
+msgstr "使用安全组功能之前，必须先在Zone中启用安全组功能。系统管理员可以在创建一个新的Zone时，通过选择带‘安全组’功能的网络方案进行启用。在高级安装指南的基本Zone配置中有该过程的详细描述。系统管理员不能对现有Zone启用安全组，只能在新建Zone时启用。"
+
+# 9239428930ac475c8787a1fa5c7b5852
+#: ../../managing_networks.rst:1795
+msgid "Adding Ingress and Egress Rules to a Security Group"
+msgstr "对安全组添加入口出口规则"
+
+# 1dabe90dfbf742b1ad863dda6a7370cf
+#: ../../managing_networks.rst:1807
+msgid ""
+"In Select view, choose Security Groups, then click the security group you "
+"want ."
+msgstr "在选择视图中，选择安全组，然后点击需要的安全组"
+
+# 14c6cdb0f76f4e5bafb8a8247c89a3f5
+#: ../../managing_networks.rst:1812
+msgid ""
+"To add an ingress rule, click the Ingress Rules tab and fill out the "
+"following fields to specify what network traffic is allowed into VM "
+"instances in this security group. If no ingress rules are specified, then no"
+" traffic will be allowed in, except for responses to any traffic that has "
+"been allowed out through an egress rule."
+msgstr "为增加入口规则，点击入口规则并填写相应内容，以说明在此安全组内何种网络流量可以到达虚拟机实例。如果没有说明入口规则，则不会允许流量进入。也就只有出口规允许的流量了。"
+
+# dbc6db6a8f164564b90b36fb8600f6c4
+#: ../../managing_networks.rst:1820
+msgid ""
+"**Add by CIDR/Account**. Indicate whether the source of the traffic will be "
+"defined by IP address (CIDR) or an existing security group in a CloudStack "
+"account (Account). Choose Account if you want to allow incoming traffic from"
+" all VMs in another security group"
+msgstr "**通过CIDR帐户添加**. 表明在CloudStack帐户中是否有CIDR定义的流量来源或是已存在的安全组。如果允许来自另一安全组的所有虚拟机的流量进入，则添加此帐户。"
+
+# c7404bcf0635456b924a7d4461860444
+#: ../../managing_networks.rst:1828
+msgid ""
+"**Protocol**. The networking protocol that sources will use to send traffic "
+"to the security group. TCP and UDP are typically used for data exchange and "
+"end-user communications. ICMP is typically used to send error messages or "
+"network monitoring data."
+msgstr "**协议**. 发送源会使用网络协议来发送流量到安全组。TCP和UDP是典型的二种用来数据交换和终端用户交流的协议。ICMP则用来发送错误信息或网络监控数据"
+
+# 553fb9fc05c647d38e4c15f2ccbb5123
+#: ../../managing_networks.rst:1835
+msgid ""
+"**Start Port, End Port**. (TCP, UDP only) A range of listening ports that "
+"are the destination for the incoming traffic. If you are opening a single "
+"port, use the same number in both fields."
+msgstr "**开始端口，结束端口**. (仅对TCP，UDP)。目的地为进入流量而设的监听端口范围。如果仅开放了单个端口，则在两者的区域中用同一端口。"
+
+# f1ac0dd3df2a46ad8b321cc49981a565
+#: ../../managing_networks.rst:1841
+msgid ""
+"**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code "
+"that will be accepted."
+msgstr "**ICMP类型，ICMP编码**. (仅对ICMP)。接受的信息及错误码的类型。"
+
+# 4b14903d5adb4c9a8301a393218c0fe9
+#: ../../managing_networks.rst:1846
+msgid ""
+"**CIDR**. (Add by CIDR only) To accept only traffic from 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 incoming traffic. For example,"
+" 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr "**CIDR**. (仅通过CIDR添加)。为接受来来自特殊地址块的流量，输入一个CIDR，多个时用逗号隔开。CIDR是进入流量的基础IP地址。例如：192.168.0.0/22，为允许所有CIDR，请设为0.0.0.0/0"
+
+# c1561e01a67747a699e6e8f0b8d265a1
+#: ../../managing_networks.rst:1854
+msgid ""
+"**Account, Security Group**. (Add by Account only) To accept only traffic "
+"from another security group, enter the CloudStack account and name of a "
+"security group that has already been defined in that account. To allow "
+"traffic between VMs within the security group you are editing now, enter the"
+" same name you used in step 7."
+msgstr "**帐户，安全组**. (仅通过帐户添加)。为接受来自另一安全组的流量，输入一个CloudStack帐户和在此帐户中已经定义的安全组的名字。为允许你正在编辑的安全组内虚拟机之间的流量，输入你在第7步使用的相同的名字。"
+
+# 04916ecc9b4840d8804edbc1bb1bc4f7
+#: ../../managing_networks.rst:1860
+msgid "The following example allows inbound HTTP access from anywhere:"
+msgstr "下面这个例子允许内部任何地方的HTTP访问"
+
+# 10d3ac32eaec4653a69e66dd007f355a
+#: ../../managing_networks.rst:1862
+msgid "|httpaccess.png: allows inbound HTTP access from anywhere|"
+msgstr "|httpaccess.png: allows inbound HTTP access from anywhere|"
+
+# f0c00b232e4347b19d537a01dae35eac
+#: ../../managing_networks.rst:1866
+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 security group. If no egress rules are specified, then all"
+" traffic will be allowed out. Once egress rules are specified, the following"
+" types of traffic are allowed out: traffic specified in egress rules; "
+"queries to DNS and DHCP servers; and responses to any traffic that has been "
+"allowed in through an ingress rule"
+msgstr "为添加一个出口规则，点击出口规则并填写以下内容，以说明在此安全组内的虚拟机，被允许哪一类型的流量送出。如果出口规则没有说明，所以的流量都被允许出去一旦进行了说明，则以下流量可以允许出去：在出口规则中进行说明的，查询DNS和DHCP服务器的，响应来自入口规则允许进入的流量的"
+
+# 0e14fad2168c4e78b9fc5a5da9f303f4
+#: ../../managing_networks.rst:1877
+msgid ""
+"**Add by CIDR/Account**. Indicate whether the destination of the traffic "
+"will be defined by IP address (CIDR) or an existing security group in a "
+"CloudStack account (Account). Choose Account if you want to allow outgoing "
+"traffic to all VMs in another security group."
+msgstr "**通过CIDR帐户添加**. 表明流量目的地是否已通过IP地址(CIDR)定义或是CloudStack帐户(Account)内存在的安全组。选择帐户，以允许流量到其安全组内所有虚拟机"
+
+# 1a02e526bf804681aaddd5d1f0ed1ce9
+#: ../../managing_networks.rst:1885
+msgid ""
+"**Protocol**. The networking protocol that VMs will use to send outgoing "
+"traffic. TCP and UDP are typically used for data exchange and end-user "
+"communications. ICMP is typically used to send error messages or network "
+"monitoring data."
+msgstr "**协议**. 虚拟机发送流量需要的协议。TCP和UDP是典型的二种用来数据交换和终端用户交流的协议。ICMP则用来发送错误信息或网络监控数据"
+
+# b0ec41fcd32641b3944750fc36979e9a
+#: ../../managing_networks.rst:1892
+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 "**开始端口，结束端口**. (仅对TCP，UDP) 。目的地为进入流量而设的监听端口范围。如果仅开放了单个端口，则在两者的区域中用同一端口。"
+
+# f1360ae9661b4df29243b766c0bb4aa2
+#: ../../managing_networks.rst:1898
+msgid ""
+"**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code "
+"that will be sent"
+msgstr "**ICMP类型，ICMP编码**. (仅对ICMP) 。信息及错误码的类型。"
+
+# 350a113cb8dd4f31994777cc4fb0bd62
+#: ../../managing_networks.rst:1903
+msgid ""
+"**CIDR**. (Add by CIDR only) To send traffic only to 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 "**CIDR**. (仅通过CIDR添加) 。为接受来来自特殊地址块的流量，输入一个CIDR，多个时用逗号隔开。CIDR是进入流量的基础IP地址。例如：192.168.0.0/22，为允许所有CIDR，请设为0.0.0.0/0"
+
+# 0a29a66f07214b4db9dde4958f6b9ce8
+#: ../../managing_networks.rst:1911
+msgid ""
+"**Account, Security Group**. (Add by Account only) To allow traffic to be "
+"sent to another security group, enter the CloudStack account and name of a "
+"security group that has already been defined in that account. To allow "
+"traffic between VMs within the security group you are editing now, enter its"
+" name."
+msgstr "**帐户，安全组**. (仅通过帐户添加) 。为接受来自另一安全组的流量，输入一个CloudStack帐户和在此帐户中已经定义的安全组的名字。为允许你正在编辑的安全组内虚拟机之间的流量，输入名字。"
+
+# 9703c00d7003480993587ff39b757c8e
+#: ../../managing_networks.rst:1922
+msgid "External Firewalls and Load Balancers"
+msgstr "外部防火墙及负载均衡"
+
+# f80e67cfaf2b4e8ba6fe5e89961f1604
+#: ../../managing_networks.rst:1924
+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 "CloudStack允许通过外部的Jniper SRX 设备和外部NetScaler设备或网关负载均衡设备和负载均衡服务。在此情形下，虚拟机使用SRX作为网关。"
+
+# ae5fe8317334469fadbdb5e10bfb6484
+#: ../../managing_networks.rst:1930
+msgid "About Using a NetScaler Load Balancer"
+msgstr "关于使用NetScaler负载均衡器"
+
+# e93ff8055f5c45e397a20a5eec844c9d
+#: ../../managing_networks.rst:1932
+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 "在区域中，或高级区域使用隔离网络时，CloudStack支持思杰的NetScaler作为外部网络设备元素作为负责均衡。拟通过其他方案提供负载均衡而不是CloudStack的虚拟路由器时，就可以建立一个外部负载均衡器"
+
+# b35f57f9209f4a39bca7644428cc5471
+#: ../../managing_networks.rst:1937
+msgid ""
+"In a Basic zone, load balancing service is supported only if Elastic IP or "
+"Elastic LB services are enabled."
+msgstr "在基础区域中，仅在弹性IP或弹性负载均衡服务开启时，才支持负载均衡服务"
+
+# 432354c2478043e585e3be569496f81f
+#: ../../managing_networks.rst:1939
+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 device providing "
+"EIP/ELB, layer 3 router must have a policy-based routing. A policy-based "
+"route must be set up so that all traffic originated from the guest VM's are "
+"directed to NetScaler device. This is required to ensure that the outbound "
+"traffic from the guest VM's is routed to a public IP by using NAT.For more "
+"information on Elastic IP, see `Section 15.11, “About Elastic IP” <#elastic-"
+"ip>`__."
+msgstr "在基础域中使用NetScaler负载均衡提供EIP或ELB服务时，确保所有的客户虚拟机流量必须通过NetScaler设备进出。当入流量通过NetScaler设备时流量通过使用NAT协议被路由，此NAT协议依赖于公共IP到私有IP的配置。来自客户虚拟机的流量通常要经过3层路由器，为确保出流量通过提供EIP/ELB的NetScaler设备，3层路由器，必须具有基础策略。必有设立一个具有基础策略的路由器可保证所有客户机的流量都能转向NetScaler设备。这也需要确保客户虚拟机的出流量通过使用NAT被路由到公共IP。关于EIP的更多信息，参考 `15.11，“关于弹性IP” <#elastic-ip>`__."
+
+# c55b5331d1654661ba6a8b891a476d7b
+#: ../../managing_networks.rst:1953
+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 "NetScaler可以设置成直通模式。它必须在区域中部署客户虚拟机负载均衡规则之前加入。"
+
+# 820e88370085451ab81b601ac5092dac
+#: ../../managing_networks.rst:1957
+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 "CloudStack中NetScaler的功能作用与CloudStack文档中说明的使用F5 外部负载均衡器的功能作用相同。一点差别就是，F5支持路由域名，而NetScaler无此功能。NetScaler也不可以用作防火墙。"
+
+# bd46111da3364f82a10dafe9f0493719
+#: ../../managing_networks.rst:1962
+msgid ""
+"To install and enable an external load balancer for CloudStack management, "
+"see `Section 13.5.4, “External Guest Load Balancer Integration (Optional)” "
+"<#external-guest-lb-integration>`__."
+msgstr "为方便CloudStack的管理，安装并开启外部负载均衡器，请参考 `章节13.5.4，\"外部客户负载均衡器集成(可选)\"<#external-guest-lb-integration>`__."
+
+# 3d1489d6890045afa4bf8363cde00c85
+#: ../../managing_networks.rst:1966
+msgid ""
+"The Citrix NetScaler comes in three varieties. The following table "
+"summarizes how these variants are treated in CloudStack."
+msgstr "思杰的NetScaler有三种变化，下表总结了在CloudStack中如何处理那些变化。"
+
+# 2927f19bf6bb4d3bb378a8577b25625a
+#: ../../managing_networks.rst:1970
+msgid "NetScaler ADC Type"
+msgstr "NetScaler ADC Type"
+
+# 2b1a2bad59464e32bb278dabdccd5e47
+#: ../../managing_networks.rst:1970
+msgid ""
+"Description of Capabilities CloudStack Supported Features"
+msgstr "CloudStack支持特性的描述"
+
+# 39c4c063dc7a4318a25731f69953f77f
+#: ../../managing_networks.rst:1972
+msgid "MPX"
+msgstr "MPX"
+
+# ea198bf147554fa7a44f413842a7cf5b
+#: ../../managing_networks.rst:1972
+msgid ""
+"Physical appliance. Capable of deep packet inspection. Can act as "
+"application firewall and load balancer."
+msgstr "物理应用。能够进行深度数据包检测。可作为防火墙和负载均衡应用。"
+
+# a333a75371ca4e3bbcf547d8ad6f5c02
+#: ../../managing_networks.rst:1972
+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 "在高级区域中，完全支持负载均衡功能，没有限制。在基础区域中，也提供静态NAT，EIP，ELB功能。"
+
+# 3ed6562f8db44f62838fe4626dfc5b42
+#: ../../managing_networks.rst:1973
+msgid "VPX"
+msgstr "VPX"
+
+# ddd9e04881a14b22854e0d68d62da1fd
+#: ../../managing_networks.rst:1973
+msgid ""
+"Virtual appliance. Can run as VM on XenServer, ESXi, and Hyper-V "
+"hypervisors. Same functionality as MPX."
+msgstr "虚拟应用，可以运行在XenServer，ESXi以及Hyper-V上虚拟机上。与MPX功能相同。"
+
+# 6d6c6be8254042c58f42881bf458f16a
+#: ../../managing_networks.rst:1973
+msgid ""
+"Supported on ESXi and XenServer. Same functional support as for MPX. "
+"CloudStack will treat VPX and MPX as the same device type."
+msgstr "在ESXi和XenServer上支持。对MPX也支持一些功能。CloudStack将VPX和MPX作为同一类型的设备看待。"
+
+# 5c01f29af8d747a8bd66543d6871ebff
+#: ../../managing_networks.rst:1974
+msgid "SDX"
+msgstr "SDX"
+
+# 242fb2a841c945aa93d42db46483f206
+#: ../../managing_networks.rst:1974
+msgid ""
+"Physical appliance. Can create multiple fully isolated VPX instances on a "
+"single appliance to support multi-tenant usage"
+msgstr "物理应用。可以在单个应用上创建多个完全隔离的VPX实例，以支持多客户使用。"
+
+# 18dac2747b4240b4a97a950679f07e9b
+#: ../../managing_networks.rst:1974
+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 "CloudStack会动态分配，配置，管理在SDX上的虚拟机实例的生命周期。分配的实例会自动加入到CloudStack，不需要管理员进行手动配置。一旦一个VPX实例加入到CloudStack，将会认为是ESXi主机上的一个VPX。"
+
+# ac9fa52a18d4459aa785bbf9fa582470
+#: ../../managing_networks.rst:1978
+msgid "Configuring SNMP Community String on a RHEL Server"
+msgstr "在RHEL服务器上配置SNMP社区字符串"
+
+# 3f04d5be0b624710a9353ea54e5f6cd4
+#: ../../managing_networks.rst:1980
+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 "SNMP社区字符串类似于用户ID或用户密码，用来登录网络设备，如路由器。这类字符串随着所有的SNMP请求发送。如果社区字符串正确，设备将反馈相应的字符串若不正确，设备将丢弃请求，不进行处理。"
+
+# ae292ca0b1c54168812d01ef32f1ab3f
+#: ../../managing_networks.rst:1986
+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 "NetScaler设备使用SNMP与虚拟机进行通讯。为保证NetScaler设备与RHEL机器之间安全的通讯，必须安装并配置社区字符串。"
+
+# 6a8596f21b7440bfb1f7c8eb2bfc8628
+#: ../../managing_networks.rst:1992
+msgid ""
+"Ensure that you installed SNMP on RedHat. If not, run the following command:"
+msgstr "确保在RedHat上安装了SNMP，如果没有，执行以下命令:"
+
+# e86f60a54a14414296b44f545df45ecb
+#: ../../managing_networks.rst:2001
+msgid ""
+"Edit the /etc/snmp/snmpd.conf file to allow the SNMP polling from the "
+"NetScaler device."
+msgstr "编辑/etc/snmp/snmpd.conf 文件，以允许来自NetScaler设备的SNMP查询"
+
+# c7ae2f4b80e448589a7324e9160cc098
+#: ../../managing_networks.rst:2006
+msgid ""
+"Map the community name into a security name (local and mynetwork, depending "
+"on where the request is coming from):"
+msgstr "映射社区名到一个安全的名字（本地，我的网络，依赖于其来源）"
+
+# 82d2e1366fcb407292043214ee132fd0
+#: ../../managing_networks.rst:2009
+msgid ""
+"Use a strong password instead of public when you edit the following table."
+msgstr "编辑下表时，使用一个强密码"
+
+# a60077478293466090acdec3a98361b3
+#: ../../managing_networks.rst:2017
+msgid "Setting to 0.0.0.0 allows all IPs to poll the NetScaler server."
+msgstr "设置0.0.0.0以允许所有的IP都可以查询NetScaler设备"
+
+# dde16e249ba84f859fe076f1169b118b
+#: ../../managing_networks.rst:2021
+msgid "Map the security names into group names:"
+msgstr "映射一个安全名到组名"
+
+# 74b3e712da4d47a3b29ca52d3fe14e7d
+#: ../../managing_networks.rst:2033
+msgid "Create a view to allow the groups to have the permission to:"
+msgstr "创建一个视图，以允许组有权限执行："
+
+# d114649652ac478097b5ba7219ecd9b1
+#: ../../managing_networks.rst:2041
+msgid ""
+"Grant access with different write permissions to the two groups to the view "
+"you created."
+msgstr "授权不同的写权限给二个组及你创建的视图"
+
+# 35e6d3349499465981e06188c2545f91
+#: ../../managing_networks.rst:2052
+msgid "Unblock SNMP in iptables."
+msgstr "在iptalbes中解除对SNMP的锁定。"
+
+# 06ec2d8329bb44eca854ac9124a54ac2
+#: ../../managing_networks.rst:2060
+msgid "Start the SNMP service:"
+msgstr "开启SNMP服务："
+
+# 620bd58e847546af8ec5eee6f1df392f
+#: ../../managing_networks.rst:2068
+msgid ""
+"Ensure that the SNMP service is started automatically during the system "
+"startup:"
+msgstr "确保在系统启动时，SNMP服务能够自动启动。"
+
+# 459a59b07c9a487bb876fb3570027f56
+#: ../../managing_networks.rst:2076
+msgid "Initial Setup of External Firewalls and Load Balancers"
+msgstr "初始化安装外部防火墙和负载均衡"
+
+# bcccbb4ccd2742e988440761c1c97c3d
+#: ../../managing_networks.rst:2078
+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 "当为一个新帐户创建一个虚拟机时，CloudStack会设置程序以让外部防火墙和负载均衡与虚拟机共同工作。会在防火墙上创建以下对象："
+
+# b2a4387bb61a40b2a674374748325e75
+#: ../../managing_networks.rst:2084
+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 "一个新的逻辑接口，用以连接帐户的私有VLAN。接口的IP通常是私有帐户私有子网的第一个IP。"
+
+# 73a0ab4e7e52401893fb6876bddfa3c1
+#: ../../managing_networks.rst:2090
+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 "一个源NAT规则转发帐户从私有VLAN到公共网络的的出口流量，使用帐户的公共IP地址作为源地址。"
+
+# a91c17a9a27744d590cca5c8ae83e4f3
+#: ../../managing_networks.rst:2096
+msgid ""
+"A firewall filter counter that measures the number of bytes of outgoing "
+"traffic for the account"
+msgstr "防火墙过滤计数器计量帐户出口流量的字节数"
+
+# a969e661812f4c76a64517563139bc46
+#: ../../managing_networks.rst:2099
+msgid "The following objects are created on the load balancer:"
+msgstr "以下对象会在负载均衡上创建："
+
+# 70a41496c1d8446eb94f4846d5f48807
+#: ../../managing_networks.rst:2103
+msgid "A new VLAN that matches the account's provisioned Zone VLAN"
+msgstr "匹配帐户区域VLAN的私有VLAN。"
+
+# 2c7b27d0b7ba4358879882aecb0f85b2
+#: ../../managing_networks.rst:2107
+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 "一个VLAN的自有IP。经常是帐户私有子网的第二个IP。"
+
+# f331ea1b60734e7e9cf00688be8a014a
+#: ../../managing_networks.rst:2111
+msgid "Ongoing Configuration of External Firewalls and Load Balancers"
+msgstr "继续配置外部防火墙和负载均衡"
+
+# 283a3ee82af240268e7f73eee64568cc
+#: ../../managing_networks.rst:2113
+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 objects:"
+msgstr "增加的用户行为(如设置端口转发)会引起防火墙和负载均衡的程序化。一个用户可以请求增加公共IP地址以及转发使用此公共IP地址的虚拟机接受到的流量。这是通过静态NAT功能完成的，静态NAT将一个公共IP地址映射给一个虚拟机，并指定一组特定协议，开放一组特定端口。当静态NAT建立好之后，CLOUDSTACK会在区域的外部防火墙上通过程序定制如下对象："
+
+# 7f37822b183846029b22d982605df64a
+#: ../../managing_networks.rst:2124
+msgid ""
+"A static NAT rule that maps the public IP address to the private IP address "
+"of a VM."
+msgstr "一条静态NAT规则将虚拟机的私有IP地址映射到公共IP地址。"
+
+# 04d5cfd64b5a49ca87e10c965ebcbbe8
+#: ../../managing_networks.rst:2129
+msgid ""
+"A security policy that allows traffic within the set of protocols and port "
+"ranges that are specified."
+msgstr "一个安全策略可以允许说明的协议和端口范围内的流量通过。"
+
+# b32ae655c9424e7aa37228b3b21d1b57
+#: ../../managing_networks.rst:2134
+msgid ""
+"A firewall filter counter that measures the number of bytes of incoming "
+"traffic to the public IP."
+msgstr "防火墙过滤计数器计量到达此公共IP的流量"
+
+# cd8452f768c14fdd8fbd4e7432ae4f05
+#: ../../managing_networks.rst:2137
+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 "通过源NAT，静态NAT以及负载均衡规则进出的字节数均被计量并保存在每一个外部设备中。按一定的规则对这些数据进行收集，并将其存储在CloudStack的数据库中。"
+
+# ad1eac1dba114d83a1aef1f71f058a04
+#: ../../managing_networks.rst:2143
+msgid "Load Balancer Rules"
+msgstr "负载均衡规则"
+
+# 7705d32d38f54ae985f6e0d7cdbe4094
+#: ../../managing_networks.rst:2145
+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 "一个CloudStack的用户或管理员可以创建负载均衡规则以平衡一个公共IP地址收到的针对一个或多个虚拟机的外部流量。一个用户可以创建一条规则，说明一个算法，并将其指定给一部分虚拟机。"
+
+# 711015b6ce824631aa25054b86e45fd5
+#: ../../managing_networks.rst:2150
+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 "如果你创建了一个负载均衡规则且使用包括外部负载均衡设备的网络服务方案，如包括NetScaler，但随后将网络方案改成使用CloudStack的虚拟路由器，则你必须在虚拟路由器上创建一个防火墙规则，这些防火墙规则与已经设置的负载均衡规则一一对应，只有这样，才能使那些负载均衡规则继续起作用。"
+
+# b1392c053235469d9db00ff277fe4081
+#: ../../managing_networks.rst:2153
+msgid "Adding a Load Balancer Rule"
+msgstr "增加一条负载均衡规则"
+
+# a9769f3aee3741018069f035a314faec
+#: ../../managing_networks.rst:2165
+msgid ""
+"Click the name of the network where you want to load balance the traffic."
+msgstr "点击拟进行负载均衡的网络名称"
+
+# e7820b855f9a4bdc825b874af1ee74ac
+# 57f9df7d52c143248cee80215df6b361
+# f15c85d6dc1d4b1da943709cbeb66d6e
+#: ../../managing_networks.rst:2174 ../../managing_networks.rst:6224
+#: ../../managing_networks.rst:6616
+msgid ""
+"Click the IP address for which you want to create the rule, then click the "
+"Configuration tab."
+msgstr "点击你希望创建规则的IP地址，然后点击配置"
+
+# 7882de69bd334597b436f05ffb59daa7
+# 8271af5525f04c1399625a2ae00356f3
+#: ../../managing_networks.rst:2179 ../../managing_networks.rst:6229
+msgid "In the Load Balancing node of the diagram, click View All."
+msgstr "在图的负载均衡节点点上，点击 查看全部。"
+
+# 4361d1b583104cc89c442cd88c0522c4
+#: ../../managing_networks.rst:2181
+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 "在基础区域中，在不需要或不选择IP的条件下，你可以创建一条负载均衡规则。当你创建负载均衡规则时，CloudStack会内部指定一个IP地址。当规则创建完成时，IP地址会在IP地址页列出来。"
+
+# 4a94254b17ed4ec39f2315e6a888fb5a
+#: ../../managing_networks.rst:2186
+msgid ""
+"To do that, select the name of the network, then click Add Load Balancer "
+"tab. Continue with `7 <#config-lb>`__."
+msgstr "为此，选择网络名称，点击 增加负载均衡。按 `7 <#config-lb>`__ 继续进行配置。"
+
+# 9ee5e7cec16645afac9aaaaff13a496c
+# 657c6d30f6814207ba6bd9d39da07f82
+#: ../../managing_networks.rst:2191 ../../managing_networks.rst:3648
+msgid "Fill in the following:"
+msgstr "填写以下内容："
+
+# c407a31e5baa4fad9d35127bff1b7daa
+# d76bf4093eba4a98af63df8739a8e847
+# e45e3c4b92ee4267b003f94314d91095
+#: ../../managing_networks.rst:2195 ../../managing_networks.rst:6241
+#: ../../managing_networks.rst:6497
+msgid "**Name**: A name for the load balancer rule."
+msgstr "**名称**: 负载均衡规则的名称。"
+
+# 86b0b5a5cb264775a51f8c349e910dbe
+#: ../../managing_networks.rst:2199
+msgid "**Public Port**: The port receiving incoming traffic to be balanced."
+msgstr "**公共端口**: 这个端口接受到负载均衡的进入流量。"
+
+# 009ab0a02f2749b3875ebca762117055
+# aab69f01a8cb47409f9590eb9521467f
+#: ../../managing_networks.rst:2204 ../../managing_networks.rst:6250
+msgid ""
+"**Private Port**: The port that the VMs will use to receive the traffic."
+msgstr "**私有端口**: 虚拟机会使用此端口接收流量。"
+
+# a01e2f1dc4fd49108b0d7ba3e2ae529e
+#: ../../managing_networks.rst:2209
+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 "**算法**: 选择让CloudStack使用的负载均衡算法。CloudStack各类已知的算法，如果不熟悉那些选项，通过goole搜索会发现大量信息。"
+
+# 997d16371c9e465699db38061283e6b4
+#: ../../managing_networks.rst:2216
+msgid ""
+"**Stickiness**: (Optional) Click Configure and choose the algorithm for the "
+"stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr "**粘性**: (可选) 点击配置，为粘性策略选择一个算法。可参见为负载均衡规则制定的粘性会话策略。"
+
+# 18519de60f3f473c83ac612b5fad495c
+#: ../../managing_networks.rst:2222
+msgid ""
+"**AutoScale**: Click Configure and complete the AutoScale configuration as "
+"explained in `Section 15.16.6, “Configuring AutoScale” <#autoscale>`__."
+msgstr "**自动缩放**: 点击配置完成自动缩放配置，在 `章节15.16.6, “配置 AutoScale” <#autoscale>`__."
+
+# 3908f0ca791a42debbb0585189fb7c1e
+#: ../../managing_networks.rst:2228
+msgid ""
+"**Health Check**: (Optional; NetScaler load balancers only) Click Configure "
+"and fill in the characteristics of the health check policy. See `Section "
+"15.16.5.3, “Health Checks for Load Balancer Rules” <#health-checks-for-lb-"
+"rules>`__."
+msgstr "**健康检查**: (可选，只针对NetScaler的负载均衡设备) 点击配置并填写健康检查特性，参见 `章节 15.16.5.3, “负载均衡规则的健康检查” <#health-checks-for-lb-rules>`__."
+
+# 2879252f32f34f539751be82bf984014
+#: ../../managing_networks.rst:2235
+msgid ""
+"**Ping path (Optional)**: Sequence of destinations to which to send health "
+"check queries. Default: / (all)."
+msgstr "**ping 路径(可选)**: 需要发送健康检查的目的地顺序。默认：/ (all)。"
+
+# a8debc6dcd7145d7afebfc88d610080e
+#: ../../managing_networks.rst:2240
+msgid ""
+"**Response time (Optional)**: How long to wait for a response from the "
+"health check (2 - 60 seconds). Default: 5 seconds."
+msgstr "**响应时间(可选)**: 从健康检查返回的响应时间(2-60秒)，默认为5秒。"
+
+# 8fc593a6bc1348d28c5ad36ef1ee55b2
+#: ../../managing_networks.rst:2245
+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 "**间隔时间(可选)**: 健康检查的间隔时间(1秒-5分)）。默认值在全局参数 lbrule\\_health check\\_time\\_interval"
+
+# 6d4cfb962ee94044af1572953fdaad0f
+#: ../../managing_networks.rst:2252
+msgid ""
+"**Healthy threshold (Optional)**: Number of consecutive health check "
+"successes that are required before declaring an instance healthy. Default: "
+"2."
+msgstr "**健康阀值(可选)**: 在声明一个实例健康之前，连续健康检查成功的次数。默认为2."
+
+# be452bfbd60c44ee89f3cacb209f6879
+#: ../../managing_networks.rst:2258
+msgid ""
+"**Unhealthy threshold (Optional)**: Number of consecutive health check "
+"failures that are required before declaring an instance unhealthy. Default: "
+"10."
+msgstr "**不健康阀值(可选)**: 在声音一个实例不健康之前连续健康检查失败的次数。默认为10。"
+
+# 457c998fe4d6462bab0cb048fd076832
+#: ../../managing_networks.rst:2264
+msgid ""
+"Click Add VMs, then select two or more VMs that will divide the load of "
+"incoming traffic, and click Apply."
+msgstr "点击添加虚拟机，选择拟分散进入流量的二个或多个虚拟机，点击应用。"
+
+# 820fdad3c2f04d08aab271b8010f13fb
+#: ../../managing_networks.rst:2267
+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 "在列表中会出现新加的负载均衡规则。可以重复以上步骤以对此IP增加更多的负载均衡规则。"
+
+# 76399c00e68f42168b802e6ddff1fb49
+#: ../../managing_networks.rst:2271
+msgid "Sticky Session Policies for Load Balancer Rules"
+msgstr "为负载均衡规则制定的粘性会话策略。"
+
+# 1b0830c090eb4231b808b590bc10dd15
+#: ../../managing_networks.rst:2273
+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 "粘性会话应用于基于网页的应用中，以确保在用户的会话中，对用户的多种请求持续提供信息。例如，购物者正在向购物车中增加东西，则需要记住到目前为止已买的东西。粘性的概念也指持久发现或维护状态。"
+
+# 89d324559b614ee8916fe9d09229e529
+#: ../../managing_networks.rst:2279
+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, cookies are used. The cookie "
+"generated by the load balancer or application is included in request and "
+"response URLs to create persistence. The cookie name can be specified by the"
+" administrator or automatically generated. A variety of options are provided"
+" to control the exact behavior of cookies, such as how they are generated "
+"and whether they are cached."
+msgstr "在CloudStack中定义的任何负载均衡规则，都可以具有粘性策略。策略有名字，粘性方法以及参数组成。参数是成对的值-名或标志，这些由负载均衡提供商进行定义。粘发现方法可以加载负载均衡设备产生的cookie，应用生产的cookie，或基于源产生的cookie。在基于源的方法中，源IP地址被用来区分用户和定位用户存储的数据。在其他方法中，则使用cookie。由负载均衡或应用产生的cookie，包含在请求或响应的url中，以产生持久性。cookie的名称可以有管理员指定或自动产生。提供了多种选择来准确控制cookie行为。诸如如何产生的以及是否进行缓存。"
+
+# 8ac187f8411440ac922c801d4fd2171e
+#: ../../managing_networks.rst:2293
+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 "对于多数粘性方法变量列表，可以参看CloudStack UI或者调用网络列表，并检查粘性方法支持能力。"
+
+# d4666e89faf1441f96dac55fcaa4010f
+#: ../../managing_networks.rst:2298
+msgid "Health Checks for Load Balancer Rules"
+msgstr "负载均衡规则的健康检查。"
+
+# ed1c6c49e9804202a2791f6dbf88fead
+#: ../../managing_networks.rst:2300
+msgid "(NetScaler load balancer only; requires NetScaler version 10.0)"
+msgstr "（仅对NetScaler负载均衡设备，需要NetScaler版本10.0以上。）"
+
+# 4e756b5788bb4edbb5189cd1de10fe72
+#: ../../managing_networks.rst:2302
+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 "负载均衡应用中的健康检查，能够确保转发需求运行，服务可用。当创建一个负载均衡规则里，你可以指定一个健康检查策略。这是对粘性策略，算法，其他负载均衡设备规则的附加说明。可以为每一条负载均衡设备进行配置。"
+
+# d4587d4fb2ec4c1782622d46fca4b609
+#: ../../managing_networks.rst:2309
+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 "在CloudStackk中的NetScaler负载均衡设备定义的任一负载均衡规则都可以有一条健康检查策略。该策略有ping路径，定义健康或非健康状态的阀值，健康检查频率以及等待超时间隔。"
+
+# fada8ec075ce48a3915f6a674da4ecce
+#: ../../managing_networks.rst:2314
+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 with a health check "
+"configured, the state will be shown as UP or DOWN in the UI depending on the"
+" result of the most recent health check."
+msgstr "当健康检查策略生效时，负载均衡被发现处于非健康状态时，会停止转发到源的任何请求。如果随后资源变为可用，周期性进行的健康检查就会发现，此资源就会再一次被添加至从负载均衡器收到的请求资源池里。任一时刻，最近的健康检查结果会显示在UI中。对绑定了负载均衡规则的虚拟机，且此规则配置了健康检查，依据最近的检查，状态会显示为正常或失败。"
+
+# 7a1f1e9599b14a929b0eb739ba5b1ed6
+#: ../../managing_networks.rst:2324
+msgid "You can delete or modify existing health check policies."
+msgstr "可以删除或修改存在的健康检查策略。"
+
+# 242bd90478da46a3874cacc3c3fe8e44
+#: ../../managing_networks.rst:2326
+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 "为配置默认的健康检查执行频率，通过全局配置参数 healthcheck.update.interval进行设备，默认值是600秒。可以根据需要进行设置此值。"
+
+# 50015277b8b2447f9cc7b404b78076ad
+#: ../../managing_networks.rst:2331
+msgid ""
+"For details on how to set a health check policy using the UI, see `Section "
+"15.16.5.1, “Adding a Load Balancer Rule” <#add-load-balancer-rule>`__."
+msgstr "如何通过UI进行健康检查策略的设置，参阅 `章节 15.16.5.1, “添加负载均衡规则” <#add-load-balancer-rule>`__."
+
+# 495d9aad900b49139757decdcd3e1fd0
+#: ../../managing_networks.rst:2336
+msgid "Configuring AutoScale"
+msgstr "配置自缩放"
+
+# b63acaedf38e4084922d0ed1738a096c
+#: ../../managing_networks.rst:2338
+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 "自缩放允许你能够根据定义的条件进行无缝且自动的增加或减少后端服务或应用虚拟机。当开启自缩放时，可以确保在需求增加时，无缝的增加正在使用虚拟机的数量。因此他会通过关闭未使用的虚拟机或者需要时开启新的虚拟机，从而节省你的计算成本。这些操作，都不需要手动干预。"
+
+# 7c16ef30187f4e528f9e696fdb6a13a2
+#: ../../managing_networks.rst:2346
+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 CPU usage is less than 20 "
+"percent for 30 minutes."
+msgstr "NetScaler的自缩放定义为基于用户定义的条件，无缝的开启或关闭虚拟机。触发扩大或缩小行为的条件从监控服务器cpu的使用率的单一用例到监控服务器响应及cpu使用率的组合用例，各不相同。例如，你可以一个自缩放，能够在CPU使用超过80%持续15分钟时启动一个新的虚拟机，或CPU使用率低于20%持续30分钟时，移除一个虚拟机。"
+
+# 80978f0a46614c2388d8939eed46efe8
+#: ../../managing_networks.rst:2355
+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 "CloudStack使用NetScaler负载均衡器来监控系统健康的各方面，并与CloudStack共同工作以初始化扩大或缩小的行为。"
+
+# 7afb1d7436404cfd95447514fc260dc2
+#: ../../managing_networks.rst:2359
+msgid ""
+"AutoScale is supported on NetScaler Release 10 Build 74.4006.e and beyond."
+msgstr "自缩放在NetScaler发布的10版本以上适用。（Build 74.4006.e 及以上）"
+
+# 51240e4bba6843c59ae0708261e1f840
+#: ../../managing_networks.rst:2361
+msgid ""
+"**Prerequisites**: Before you configure an AutoScale rule, consider the "
+"following:"
+msgstr "预需求：在配置自缩放前，需要考虑以下几点："
+
+# 277e8d5e18a44c6a8294bd45157ea092
+#: ../../managing_networks.rst:2365
+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 "确保在配置自缩放时有必需的模板。当使用模板部署虚拟机并使虚拟机启动时，应用能够起动并运行。"
+
+# 737813324b7c4d178b04393d1999b2bc
+#: ../../managing_networks.rst:2369
+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 "如果应用没有运行，NetScaler设备会认为虚拟机无效并持续无条件的创建虚拟机，直到资源耗尽。"
+
+# 5143a191f2974e27b72c984bf972c957
+#: ../../managing_networks.rst:2373
+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 "部署准备好的模板。确保应用在第一次启动时能够开启并准备好接管流量。观察部署模板需要的时间。在配置自缩放时，要考虑这段时间。"
+
+# 2fb2c481526e4dacbc3d8658f102c054
+#: ../../managing_networks.rst:2380
+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 `Section 15.16.2, “Configuring SNMP Community String on a RHEL "
+"Server” <#configure-snmp-rhel>`__ to configure SNMP on a RHEL machine."
+msgstr "自缩放功能支持SNMP计数，这可以用来定义扩大或缩小的前提条件。为监测SNMP计数，确保SNMP代理已经在创建自缩放虚拟机的模板中安装。通过使用标准SNMP管理器，SNMP操作可以与配置好的社区SNMP和端口一起工作。可参见 `章节 15.16.2, “在RHEL服务器上配置SNMP 团体字符串” <#configure-snmp-rhel>`__在RHEL服务器上配置SNMP团体字符串。"
+
+# 596a2d14b50c4e298970de7db5c4d19b
+#: ../../managing_networks.rst:2392
+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 "确保在全局配置中的结束点地址参数已设置为管理服务器的API地址。例如：http://10.102.102.22:8080/client/api. 在多管理节点的部署中，使用配置在负载均衡器上的虚拟IP地址作为管理服务器集群的IP地址。此外，确保NetScaler设备有读取为提供自缩放而配置的IP地址的权限。"
+
+# 59583fe0dfc14e2db8bcc23629da18e3
+#: ../../managing_networks.rst:2400
+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 `Updating an AutoScale Configuration "
+"<#update-autoscale>`__"
+msgstr "如果更新了endpointe.url，在系统自动负载均衡器规则里，先关闭自缩放功能随后再开启，以应用此更新。。更多信息，参见 `更新 AutoScale Configuration <#update-autoscale>`__"
+
+# 06073879472f4da9bd08b00591d0cb40
+#: ../../managing_networks.rst:2407
+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 "如果为自缩放用户生成了API值和秘钥，确保用户参与的负载均衡器的自缩放功能先关闭，再开启，以应用NetScaler配置的变化。"
+
+# 019b533b8504424fac6d7aca7a0eef69
+#: ../../managing_networks.rst:2414
+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 "在高级区域中，在配置带自缩放的负载均衡规则时，确保至少要有一个虚拟机。在网络中存在一个虚拟机，可保证在配置自缩放时，网络处于使用状态。"
+
+# 6cf79ca1b7bb4329a6e3794bd3bb6640
+#: ../../managing_networks.rst:2419
+msgid "**Configuration**: Specify the following:"
+msgstr "**配置**: 说明如下："
+
+# 06eb944130db406d86f9d8d4f0f5201f
+#: ../../managing_networks.rst:2421
+msgid "|autoscaleateconfig.png: Configuring AutoScale|"
+msgstr "|autoscaleateconfig.png: Configuring AutoScale|"
+
+# b20309b302124634a79102396066cfc9
+#: ../../managing_networks.rst:2425
+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 "**模板**: 模板由基本的操作系统镜像和应用组成。在自缩放动作中，模板用来提供一个应用的新的实例。当从模板部署虚拟机时，虚拟机在管理员不干预的情形下开始从负载均衡器那里接管流量。例如，如果虚拟机部署为WEB服务应用，则虚拟机上的WEB服务器应该在运行，并且连接了数据库，等等。"
+
+# d1dea3f6825c4703a43d71cdc7414e04
+#: ../../managing_networks.rst:2435
+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 "**计算方案**: 一个预定义的虚拟硬件资源集，包括CPU速度，CPU数量，RAM，用户在创建虚拟时可以选择这些。选择一个计算方案作为提供虚拟机实例中自缩放行为的一部分。"
+
+# 977cac13b43548b893cd8d3b9263a434
+#: ../../managing_networks.rst:2443
+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 "**最小实例**: 指定给负载均衡规则活动的虚拟机实例的最小数量，活动的虚拟机实例是开启的应用实例，并服务于流量和负载均衡。这个参数确保负载均衡规则拥有至少一个配置的活动虚拟机实例，并且能够服务于流量。"
+
+# 5e6b6bcdd4c24696a9891de65ee28e82
+#: ../../managing_networks.rst:2450
+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 active instance count breaches the Max"
+" instance value."
+msgstr "如果一个应用程序，比如SAP，它运行在一个VM实例上，但是VM因为某些原因宕机了，那么这个VM没有被算成是Min实例的一部分，并且如果这些活动的VM实例是下面配置的数值，那么自动扩展功能启动一个扩展的动作。同样的，当应用程序实例从宕机的状态恢复了以后，这个应用程序实例会被算为活动实例计数的一部分，并且当活动实例计数超出Max实例数值的时候，自动扩展启动一个缩减动作。"
+
+# 274bc08434344f26bf553ccdc8e6bbd2
+#: ../../managing_networks.rst:2454
+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 "**最大实例数**：最大数量的**应该被指派到**\\ 一条负载均衡策略的活动VM实例。这个参数定义了能被指派到一条负载均衡策略的活动VM实例的上限。"
+
+# fa8765ac9c4e4d00b6201068667e656e
+#: ../../managing_networks.rst:2459
+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 "给最大量实例参数指定一个大的值可能引发大量VM实例的分发，这个过程会导致一个负载均衡策略耗尽账户或者域级别下VM实例指定的限制。"
+
+# c9355e7ca89d4ccc9d33697630f9c9ce
+#: ../../managing_networks.rst:2464
+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 "如果一个应用程序，比如SAP，它运行在一个VM实例上，但是VM因为某些原因宕机了，那么这个VM没有被算成是Max实例的一部分。所以这个情况中为扩展动作分发的VMs数量可能会超过配置的MAX实例数值。一旦这个VMs中的应用程序实例从先前的宕机中恢复的时候，自动扩展功能就会校正Max实例的数值。"
+
+# 862fa403b3ae4078b2c5fad84f20c904
+#: ../../managing_networks.rst:2466
+msgid "Specify the following scale-up and scale-down policies:"
+msgstr "指定下列扩展和缩减的策略："
+
+# e1f66b823478416ab7c99e5e853481e1
+#: ../../managing_networks.rst:2470
+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 "**持续**：持续，以秒为单位，你必须指定条件为true以触发一个扩展动作。这个条件定义的是为了触发一个自动扩展动作，你指定的全部持续值应保持为true。"
+
+# de56c7c414204d218c9bea6a7fcf7344
+#: ../../managing_networks.rst:2477
+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 "**计数器**：性能计数器直接体现了被监视实例的状态。默认情况下，CloudStack提供了4个性能计数器：3个SNMP计数器和1个NetScaler计数器。SNMP计数器是Linux User CPU、Linux System CPU和Linux CPU Idle。NetScaler计数器是ResponseTime。root管理员能够使用CloudStack API给CloudStack添加额外的计数器。"
+
+# f5b266cdeebc49f99553c773fbb856ec
+#: ../../managing_networks.rst:2486
+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 "**运算符**：自动扩展功能支持下列5种关系型运算符：大于、小于、小于或等于、大于或等于和等于。"
+
+# 32828b689ff84e5bb31b059d21354910
+#: ../../managing_networks.rst:2492
+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 "**阈值**：阈值用于计数器。一旦上面计数器中定义的值超出阈值，自动扩展功能会启动扩展或者缩减动作。"
+
+# 3cda244cb6b14b7fa2e15a48acb8b16d
+#: ../../managing_networks.rst:2498
+msgid "**Add**: Click Add to add the condition."
+msgstr "**添加**:：点击添加来添加条件。"
+
+# 1e835d8f1a6c4e388d57d52753d3a8b8
+#: ../../managing_networks.rst:2500
+msgid ""
+"Additionally, if you want to configure the advanced settings, click Show "
+"advanced settings, and specify the following:"
+msgstr "另外，如果你想配置高级设置，点击显示高级设置，接着指定下列参数："
+
+# 5b7ba989669e4a40afb252e27e1fc081
+#: ../../managing_networks.rst:2505
+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 "**轮询间隔**：组合计数器，运算和阈值这几个条件的频率在触发扩展和缩减动作之前都要被评估。默认的轮询间隔是30秒。"
+
+# 89516f03f6a94946ad2d2947d84e248b
+#: ../../managing_networks.rst:2512
+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 "**平静期**：这是自动扩展动作被触发之后的冷静期。这个时间包括完成从模板分发一个VM实例的时间和一个应用程序准备好提供服务的时间。平静期允许机群在发生任何动作之前进入稳定状态。默认值是300秒。"
+
+# 8d8f688a8c5f4fc8953fc72bbb6fa60e
+#: ../../managing_networks.rst:2521
+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 "**VM销毁宽限期**：此宽限期以秒计算，在一个缩减动作运行之后，在VMs被视为缩减动作的一部分从而销毁之前的等待时间。它保证了能够彻底关闭任何服务于被标记为销毁的VM的挂起中的进程或者事务。默认值是120秒。"
+
+# 6fd80b96ba7b43e9986930a454605054
+#: ../../managing_networks.rst:2529
+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 "**安全组**：安全组提供一种方法来隔离VMs流量。一个安全组是一组依照设置名为入口规则和出口规则来过滤他们进出流量的VMs，这些规则依靠与VM通讯的IP地址来过滤网络流量。"
+
+# 29394085111d4034a57c010959b35f52
+#: ../../managing_networks.rst:2538
+msgid ""
+"**Disk Offerings**: A predefined set of disk size for primary data storage."
+msgstr "**磁盘方案**：一组预定义的主数据存储磁盘大小。"
+
+# 1f96f023591543e8bd947f88ef3b1050
+#: ../../managing_networks.rst:2543
+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 "**SNMP 联系**：SNMP 联系字符串被用于NetScaler设备从分发的VM实例中查询已配置的计数器的值。默认是public。"
+
+# 821ca4f7b9eb46fdb6f1e55753fbae4f
+#: ../../managing_networks.rst:2549
+msgid ""
+"**SNMP Port**: The port number on which the SNMP agent that run on the "
+"provisioned VMs is listening. Default port is 161."
+msgstr "**SNMP端口**：运行在已分发的VMs上的SNMP代理端口号。默认的端口是161."
+
+# 6383878e27b5486196bb94eda0e78311
+#: ../../managing_networks.rst:2554
+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 "**用户**：在云中NetScaler设备中用于发起扩展和缩减API调用的用户。如果没有指定选项，那么该用户被配置为自动扩展。指定其他用户名可以覆盖此配置。"
+
+# 2d0400bf625c40e5b507fe7a2a386fe3
+#: ../../managing_networks.rst:2561
+msgid "**Apply**: Click Apply to create the AutoScale configuration."
+msgstr "**应用**：点击应用创建自动扩展配置。"
+
+# 5571267d05444e769accce5b8bdb476a
+#: ../../managing_networks.rst:2563
+msgid "**Disabling and Enabling an AutoScale Configuration**"
+msgstr "**禁止和启用自动扩展配置**"
+
+# a73ffd802f50465da3992613e2fd33ce
+#: ../../managing_networks.rst:2565
+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 to enable or disable AutoScale.| button."
+msgstr "如果你想对一个自动扩展VM实例执行任何维护操作，请禁用自动扩展配置。当自动扩展配置被禁用，扩展和缩减动作不会执行。你可以利用停机时间进行维护活动。要禁用自动扩展配置，点击禁用自动扩展 |EnableDisable.png: button to enable or disable AutoScale.| 按钮。"
+
+# 93c6d4e3c8c549b6846a3295c5edd0d9
+#: ../../managing_networks.rst:2572
+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 to enable or disable AutoScale.| button."
+msgstr "这个按钮是启用和禁止的切换开关，取决于当前是否启用了自动扩展。在执行完维护操作以后，你可以启用回自动扩展配置。要启用，请再次打开自动扩展配置页面，然后点击启用自动扩展 |EnableDisable.png: button to enable or disable AutoScale.| 按钮。"
+
+# be28357183b6411393f82cd2c72b5010
+#: ../../managing_networks.rst:2579
+msgid "**Updating an AutoScale Configuration**"
+msgstr "**更新自动扩展配置**"
+
+# 9773eec58a9e4bb1b7870b150f73375a
+#: ../../managing_networks.rst:2581
+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 "你可以更新各种参数和添加或者删除扩展或缩减策略中的条件。在你更新自动扩展配置之前，请确保你已经通过点击禁止自动扩展按钮禁止了自动扩展负载均衡策略。"
+
+# 08d983f7467a4f88b2f0327cb7e70ae6
+#: ../../managing_networks.rst:2586
+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 "在你修改了所需的自动扩展参数之后，点击应用。要应新的自动扩展策略，再次打开自动扩展配置页面，然后点击启用自动扩展按钮。"
+
+# 7cbd0d57e0eb44bfa39e96ceb5882808
+#: ../../managing_networks.rst:2590
+msgid "**Runtime Considerations**"
+msgstr "**运行时注意事项**"
+
+# 441f7052cbd94e9da209c4ae56f9188e
+#: ../../managing_networks.rst:2594
+msgid ""
+"An administrator should not assign a VM to a load balancing rule which is "
+"configured for AutoScale."
+msgstr "管理员不应该分配VM到配置为AutoScale的负载均衡规则中。"
+
+# f50e274f34b349e4b1a475e82d6b27a0
+#: ../../managing_networks.rst:2599
+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 "在分配虚拟机到一个负载均衡的规则配置完成前如果NetScaler被关闭或重启，则配置的虚拟机不能成为负载均衡规则的一部分。要解决此问题，重命名基于AutoScale配置的虚拟机名称或ID，以便在任何时间点负载平衡规则可以调节该虚拟机。"
+
+# 5863fd77df844d8abfc0eb5b54113a9b
+#: ../../managing_networks.rst:2608
+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 "在自动扩展上下文之外使用API调用，如destroyVM，那么自动扩展下的VM会处于负载均衡配置冲突状态中。虽然VM被负载均衡策略所销毁，但NetScaler仍然会把VM作为一个设备分配一条策略。"
+
+# 05ac2f1b191343dfbe9766bc0a12a5eb
+#: ../../managing_networks.rst:2615
+msgid "Global Server Load Balancing Support"
+msgstr "全局服务器负载均衡 支持"
+
+# dc875268ac1f420f95d0b8a997b1edac
+#: ../../managing_networks.rst:2617
+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 "CLOUDSTACK支持全局服务器负载均衡 (GSLB) 功能以提供可持续的商业运营。GSLB可以在CLOUDSTACK环境中实现资源的无缝迁移。CLOUDSTACK通过集成NetScaler应用交付控制器 (ADC)来提供GSLB功能，ADC可以提供各种各样的GSLB能力，比如灾难恢复，负载均衡。CLOUDSTACK在实现GSLB功能进，使用了DNS重定向技术。"
+
+# df9e3461363043e6aa13a4bf8dc2cf8e
+#: ../../managing_networks.rst:2625
+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 "为了支持这个功能，引进了地域级别的服务和服务提供者。引进了一项新服务“GSLB”作为地域级别的服务。该GSLB服务提供者介绍将提供GSLB服务。目前，CloudStack中NetScaler可作为GSLB提供者。 GSLB功能工作在Active-Active数据中心环境。"
+
+# 66668f01260b42868bfd989b8ec41aec
+#: ../../managing_networks.rst:2633
+msgid "About Global Server Load Balancing"
+msgstr "关于全局服务器负载均衡"
+
+# beef05e70dc142608a052c66fe71bde8
+#: ../../managing_networks.rst:2635
+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 accessing a resource in the event of a "
+"failure, or to provide a means of shifting traffic easily to simplify "
+"maintenance, or both."
+msgstr "全局服务器负载均衡(GSLB)是负载均衡功能的扩展，为了高效的避免停机时间。基于部署的性质，GSLB代表一组技术的集合，用于各种用途，如负载均衡，灾难恢复，性能，和法定义务。使用GSLB，工作负载可以分布在位于不同地理位置的多个数据中心。 GSLB也可以用于在发生故障时访问资源的另一个备用位置，或对流量提供了简易的维护方式，或两者兼得。"
+
+# 6f6103c3a53e4f1cb222b9afd2dcb902
+#: ../../managing_networks.rst:2646
+msgid "Components of GSLB"
+msgstr "GSLB服务组件"
+
+# 8b8a51e12bdd4107865ac3a367c5d94c
+#: ../../managing_networks.rst:2648
+msgid "A typical GSLB environment is comprised of the following components:"
+msgstr "一个典型的GSLB环境由以下服务组件组成："
+
+# 24d395f518ba4bc6acbde4a7f3524765
+#: ../../managing_networks.rst:2652
+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 "**GSLB站点**：在CloudStack专业术语中，GSLB站点表现为映射至数据中心的zones，每个GSLB有多个网络设备。每个GSLB站点由一个位于站点中的NetScaler设备管理。每个NetScaler设备将他管理的站点视为本地站点，并且由其他NetScaler设备管理的站点视为远程站点。在GSLB部署中它是一个中央实体，具体表现为一个名称和一个IP地址。"
+
+# 3adc636819414d66a23bac457844c029
+#: ../../managing_networks.rst:2662
+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 "**GSLB服务**：GSLB服务表现为典型的负载均衡或者内容交换虚拟服务器。在一个GSLB环境中，你可以有本地及远程GSLB服务。本地GSLB服务表现为一个本地负载均衡或者内容交换虚拟服务器。远程GSLB服务是配置在GSLB设置中的其他站点。在每个站点中的GSLB设置里，你可以创建一个本地GSLB服务和任意数量的远程GSLB服务。"
+
+# 7b6395ad205c425b996b1e5add0ff8d5
+#: ../../managing_networks.rst:2673
+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 a FQDN DNS name."
+msgstr "**GSLB虚拟服务器**：GSLB虚拟服务器指的是一个或多个GSLB服务和平衡跨越多个使用CloudStack功能的zones之间VMs的流量。它通过评估配置的GSLB方法或者算法来选择一个GSLB服务发送客户端请求。来自不同zone的一个或多个虚拟服务器被绑定到GSLB虚拟服务器上。GSLB虚拟服务器没有对应的公共IP，只有一个FQDN DNS名称。"
+
+# e3e856d634e6456c93aff9131bbe3741
+#: ../../managing_networks.rst:2684
+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 balancing or content switching virtual "
+"server, the client sends the request to that virtual server’s VIP address."
+msgstr "**负载均衡或内容交换虚拟服务器**：依照Citrix NetScaler的专业术语，一个负载均衡或者内容交换虚拟服务器表现为本地网络上的一个或多个服务器。客户端发送他们的请求至负载均衡或内容交换虚拟服务器IP（VIP）地址，并且由虚拟服务器平衡本地服务器之间的负载。在GSLB虚拟服务器选择了一个基于本地或者远程负载均衡或者内容交换虚拟服务器的GSLB服务之后，客户端发送请求至虚拟服务器的VIP地址。"
+
+# c5a7dc8ecc384cbc9122a87ac691fb60
+#: ../../managing_networks.rst:2696
+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 "**DNS VIPs**：DNS虚拟IP是一个在GSLB服务供应者上的DNS负载均衡虚拟服务器。在有GSLB服务提供者的域中的DNS请求会被发送至一个DNS VIP。"
+
+# f5267941251d49dab69cee3c751f2a73
+#: ../../managing_networks.rst:2703
+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 and port."
+msgstr "**权威DNS**：ADNS(权威域名称服务器)是一个为DNS请求提供真实响应的服务，比如web站点IP地址。在GSLB环境中，一个ADNS服务只响应权威的GSLB服务提供者所在域的DNS请求。当配置了一个ADNS服务，该服务的提供者即拥有该服务IP并且广播它。当你创建一个ADNS服务的时候，NetScaler通过配置的ADNS服务IP和端口响应DNS请求。"
+
+# cc2d753e713a478a81de5da6e6c98ed0
+#: ../../managing_networks.rst:2713
+msgid "How Does GSLB Works in CloudStack?"
+msgstr "在CloudStack中，GSLB的工作原理是什么？"
+
+# c98da292c6334f3ca648a149ebdc8824
+#: ../../managing_networks.rst:2715
+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 xyztelco cloud. For that purpose, they "
+"launch two instances each in both the zones: VM1 and VM2 in Zone-1 and VM5 "
+"and VM6 in Zone-2. Tenant-A acquires a public IP, IP-1 in Zone-1, and "
+"configures a load balancer rule to load balance the traffic between VM1 and "
+"VM2 instances. CloudStack orchestrates setting up a virtual server on the LB"
+" service provider in Zone-1. Virtual server 1 that is set up on the LB "
+"service provider in Zone-1 represents a publicly accessible virtual server "
+"that client reaches at IP-1. The client traffic to virtual server 1 at IP-1 "
+"will be load balanced across VM1 and VM2 instances."
+msgstr "全局服务器负载均衡-GSLB-用于在不同地域的不同独立区域之间管理WEB服务器的访问流量。以下是CLOUDSTACK中提供的GSLB功能图示：EXZTELCO这个组织用CLOUDSTACK在不同的数据中心部署一个公有云，此云环境包括两个区域，Zone-1 和Zone-2。XYZTELCO里有租户A需要部署一个高可用方案。为了达到此目标，他们分别在两个区域里部署了两个虚拟机实例：Zone-1中有VM1和VM2，Zone-2中有VM5和VM6。租户A在Zone-1中得到一个公网IP-IP-1，并且在VM1和VM2之间配置了负载均衡规则。CLOUDSTACK 编排系统在 Zone-1中LB服务上设置了一个虚拟服务器-Virtual server 1 。客户端对-IP-1的访问会到达Virtual server 1，此虚拟服务器再将流量转发到VM1和VM2上进行流量负载均衡。"
+
+# ffa6856e30584d38a6f24079acff4661
+#: ../../managing_networks.rst:2732
+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 instances. At this point Tenant-A "
+"has the service enabled in both the zones, but has no means to set up a "
+"disaster recovery plan if one of the zone fails. Additionally, there is no "
+"way for Tenant-A to load balance the traffic intelligently to one of the "
+"zones based on load, proximity and so on. The cloud administrator of "
+"xyztelco provisions a GSLB service provider to both the zones. A GSLB "
+"provider is typically an ADC that has the ability to act as an ADNS "
+"(Authoritative Domain Name Server) and has the mechanism to monitor health "
+"of virtual servers both at local and remote sites. The cloud admin enables "
+"GSLB as a service to the tenants that use zones 1 and 2."
+msgstr "租户A在Zone-2中得到一个公网IP-IP-2，并且在VM5和VM6之间配置了负载均衡规则。CLOUDSTACK 编排系统在 Zone-2中LB服务上设置了一个虚拟服务器-Virtual server 2 。客户端对-IP-2的访问会到达Virtual server 2，此虚拟服务器再将流量转发到VM5和VM6上进行流量负载均衡。此时，租户A在两个区域里都启用了服务，但是，无法在这种环境下部署灾难恢复计划，也无法更智能在区域内使用负载均衡。要解决这些问题，XYZTELCO云管理员可以在两个区域内启用GSLB服务，一个GSLB服务通常是一个具有ADNS(认证域名服务器)能力的ADC，并且具有监测本地和远程站点健康状况的手段。云管理员可以在ZONE 1和2中为租户启用GSLB服务。"
+
+# 3a73c9ef3d7f4ebeb3911bd3563d8387
+#: ../../managing_networks.rst:2750
+msgid "|gslb.png: GSLB architecture|"
+msgstr "|gslb.png: GSLB architecture|"
+
+# 6e23027e34d34f4a936236b981c7bcf6
+#: ../../managing_networks.rst:2752
+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 start monitoring the health of "
+"virtual server 1 and 2 in Zone-1. CloudStack will also orchestrate setting "
+"up GSLB virtual server 2 on GSLB service provider at Zone-2. CloudStack will"
+" bind virtual server 1 of Zone-1 and virtual server 2 of Zone-2 to GLSB "
+"virtual server 2. GSLB virtual server 2 is configured to start monitoring "
+"the health of virtual server 1 and 2. CloudStack will bind the domain "
+"A.xyztelco.com to both the GSLB virtual server 1 and 2. At this point, "
+"Tenant-A service will be globally reachable at A.xyztelco.com. The private "
+"DNS server for the domain xyztelcom.com is configured by the admin out-of-"
+"band to resolve the domain A.xyztelco.com to the GSLB providers at both the "
+"zones, which are configured as ADNS for the domain A.xyztelco.com. A client "
+"when sends a DNS request to resolve A.xyztelcom.com, will eventually get DNS"
+" delegation to the address of GSLB providers at zone 1 and 2. A client DNS "
+"request will be received by the GSLB provider. The GSLB provider, depending "
+"on the domain for which it needs to resolve, will pick up the GSLB virtual "
+"server associated with the domain. Depending on the health of the virtual "
+"servers being load balanced, DNS request for the domain will be resolved to "
+"the public IP associated with the selected virtual server."
+msgstr "租户- A希望利用由xyztelco cloud提供的GSLB服务。租户-A配置了一个GSLB规则对Zone-1中的虚拟服务器1和Zone-2中的虚拟服务器2提供流量负载均衡。假设域名是A.xyztelco.com 。CloudStack中协调设置GSLB服务提供者Zone-1中的GSLB虚拟服务器1。 CloudStack绑定Zone-1中的虚拟服务器1和Zone-2中的虚拟服务器2到GSLB虚拟服务器1。CloudStack也将协调设置GSLB服务提供者Zone-2中的GSLB虚拟服务器2.CloudStack绑定Zone-1中的虚拟服务器1和Zone-2中的虚拟服务器2到GSLB虚拟服务器2.GSLB虚拟服务器2配置为开始监视虚拟服务器1和2的健康。CloudStack中会绑定域名A.xyztelco.com到GSLB虚拟服务器1和2。在这一点上，租户-A的服务将在全球范围内可达于A.xyztelco.com。域名xyztelcom.com的专用DNS服务器，被管理员配置为外带管理，由两个区域的GSLB提供者对域名A.xyztelco.com提供解析。它将被配置为域名A.xyztelco.com的ADNS。当客户端请求解析A.xyztelcom.com域名时，将最终由DNS指派到GSLB提供者Zone 1 和Zone2。客户DNS请求将被GSLB提供者接获。GSLB提供者，根据需要解析的域名，将获得与域名关联的GSLB虚拟服务器。根据用于负载均衡的虚拟服务器的运行健康状况，域名DNS请求将被解析到所选择关联的虚拟服务器中。"
+
+# 3151e8ac0c36496686ae21c2163aa04b
+#: ../../managing_networks.rst:2780
+msgid "Configuring GSLB"
+msgstr "配置GSLB"
+
+# f59f84c71a354830be5b56db8ff8dac9
+#: ../../managing_networks.rst:2782
+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 servers. Finally, bind the domain to "
+"the GSLB virtual servers. The GSLB configurations on the two appliances at "
+"the two different zones are identical, although each sites load-balancing "
+"configuration is specific to that site."
+msgstr "要配置GSLB的部署，您必须首先为每个区域配置一个标准的负载平衡设置。这使您能够在该地域中每个区域的不同服务器之间进行负载均衡。然后在NetScaler方面，配置您计划添加到每个区域作为权威DNS(ADNS)服务器的两个NetScaler应用。接下来，为每个区域创建GSLB站点、配置GSLB虚拟服务器、创建GSLB服务并绑定GSLB服务到GSLB虚拟服务器中。最后，绑定该域到GSLB虚拟服务器。两个应用的GSLB配置在两个不同区域中是完全相同的，尽管每个网站的负载均衡配置特定于该网站。"
+
+# 99bb0093d2e94a7a86b614949e37a273
+#: ../../managing_networks.rst:2794
+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 "作为云管理员执行以下操作。按照上面给出的例子中，由管理员xyztelco设置GSLB："
+
+# 1885a58567b74c5fb1d24b27d68606d1
+#: ../../managing_networks.rst:2799
+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 "在全局变量 cloud.dns.name中，为您租户云定义DNS名称并供GSLB服务使用。"
+
+# 3a7b005c2a8f4371abec8d107ec7567a
+#: ../../managing_networks.rst:2804
+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 "在NetScaler方面，给出GSLB配置 `配置全局服务器负载均衡 (GSLB) <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-con.html>`__:"
+
+# ad1e67d3c4ba4a4dbcc2c9f9f8312a2e
+#: ../../managing_networks.rst:2810
+msgid "Configuring a standard load balancing setup."
+msgstr "配置一个标准的负载均衡设置。"
+
+# cf2cce5b485d4677862f4dfa37cca3e2
+#: ../../managing_networks.rst:2814
+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 "配置权威DNS，如下解释 `配置权威的DNS服务 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-adns-svc-tsk.html>`__."
+
+# 28a6a8facbb74d048b3446698e7c3a28
+#: ../../managing_networks.rst:2820
+msgid ""
+"Configure a GSLB site with site name formed from the domain name details."
+msgstr "由域名详细信息配置一个GSLB站点和站点名称。"
+
+# 23d7169514304f03b20f0dcdd7d85560
+#: ../../managing_networks.rst:2823
+msgid "Configure a GSLB site with the site name formed from the domain name."
+msgstr "由域名配置一个GSLB站点和站点名称。"
+
+# abdfa71791a446fa8c4807a164a963ca
+#: ../../managing_networks.rst:2826
+msgid ""
+"As per the example given above, the site names are A.xyztelco.com and "
+"B.xyztelco.com."
+msgstr "按照上面给出的例子，站点名称为 A.xyztelco.com 和 B.xyztelco.com"
+
+# 0c7009166c264415a54730db14b1aa5d
+#: ../../managing_networks.rst:2829
+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 "更多信息，请参阅 `配置基本的GSLB站点 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-basic-site-tsk.html>`__."
+
+# c87d7d53d0a94969ada1b51cdefa6a1d
+#: ../../managing_networks.rst:2834
+msgid "Configure a GSLB virtual server."
+msgstr "配置GSLB虚拟服务器。"
+
+# e8a2089685594e79ad6db6881d235b51
+#: ../../managing_networks.rst:2836
+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 "更多信息，请参阅 `配置GSLB虚拟服务器 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-vsvr-tsk.html>`__."
+
+# 418139183cf14fc4bb75d67dbd5675ca
+#: ../../managing_networks.rst:2841
+msgid "Configure a GSLB service for each virtual server."
+msgstr "为每个虚拟服务器配置GSLB服务。"
+
+# c3924a1ee80541e59d938ffb33b3b2fe
+#: ../../managing_networks.rst:2843
+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 "更多信息，请参阅 `配置GSLB服务 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-svc-tsk.html>`__."
+
+# 4d37328cd36748f68e4c010cb5530462
+#: ../../managing_networks.rst:2848
+msgid "Bind the GSLB services to the GSLB virtual server."
+msgstr "绑定GSLB服务到GSLB虚拟服务器。"
+
+# 0f19756a99664403b711b3b295586263
+#: ../../managing_networks.rst:2850
+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 "更多信息，请参阅 `绑定GSLB服务到GSLB虚拟服务器 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-bind-svc-vsvr-tsk.html>`__."
+
+# 4870e604797d45d6954809f1324494d4
+#: ../../managing_networks.rst:2855
+msgid ""
+"Bind domain name to GSLB virtual server. Domain name is obtained from the "
+"domain details."
+msgstr "绑定GSLB域名到GSLB虚拟服务器。从域的详细信息中获得域名。"
+
+# 978097bf4e2743f2a424be8138ae67b8
+#: ../../managing_networks.rst:2858
+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 "更多信息，请参阅 `绑定GSLB域名到GSLB虚拟服务器 <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-bind-dom-vsvr-tsk.html>`__."
+
+# 60ee91d3c6484a30807687dd847bc57b
+#: ../../managing_networks.rst:2863
+msgid ""
+"In each zone that are participating in GSLB, add GSLB-enabled NetScaler "
+"device."
+msgstr "在每个参与GSLB的区域内，添加启用GSLB功能的NetScaler设备。"
+
+# 454bfde53cc944eb8ca917bf70b648df
+#: ../../managing_networks.rst:2866
+msgid ""
+"For more information, see `Section 15.17.2.2, “Enabling GSLB in NetScaler” "
+"<#enable-glsb-ns>`__."
+msgstr "更多信息，请参阅 `章节 15.17.2.2, “在NetScaler中启用GSLB” <#enable-glsb-ns>`__."
+
+# fd694dfa87e64107ade55d98d13c9dd2
+#: ../../managing_networks.rst:2869
+msgid "As a domain administrator/ user perform the following:"
+msgstr "以域管理员/用户执行以下操作："
+
+# b2a0dae4dd9f46918c3e14aa88ac0f76
+#: ../../managing_networks.rst:2873
+msgid "Add a GSLB rule on both the sites."
+msgstr "在两个站点中添加GSLB规则。"
+
+# 1284b054b7634c8caf28360652e7aadf
+#: ../../managing_networks.rst:2875
+msgid "See `Section 15.17.2.3, “Adding a GSLB Rule” <#gslb-add>`__."
+msgstr "参阅 `章节 15.17.2.3, “添加GSLB规则” <#gslb-add>`__."
+
+# a4c1035be3ae4ba7ae258d14c19fa1df
+#: ../../managing_networks.rst:2879
+msgid "Assign load balancer rules."
+msgstr "分配负载均衡规则。"
+
+# 63a3c42a03374ba783bdd3d8e4c5028e
+#: ../../managing_networks.rst:2881
+msgid ""
+"See `Section 15.17.2.4, “Assigning Load Balancing Rules to GSLB” <#assign-"
+"lb-gslb>`__."
+msgstr "参阅 `章节 15.17.2.4, “为GSLB分配负载均衡规则” <#assign-lb-gslb>`__."
+
+# c09c96f49f1a421389db422ce761a1dc
+#: ../../managing_networks.rst:2889
+msgid "The GSLB functionality is supported both Basic and Advanced zones."
+msgstr "GSLB功能支持基本和高级区域。"
+
+# 99047554b3fd432390156996189c06ff
+#: ../../managing_networks.rst:2893
+msgid "GSLB is added as a new network service."
+msgstr "GSLB是新添加的网络服务。"
+
+# 349a81ed861746768a4a0691ccaeab8f
+#: ../../managing_networks.rst:2897
+msgid "GSLB service provider can be added to a physical network in a zone."
+msgstr "GSLB服务提供者可以被添加至区域中的物理网络。"
+
+# 6ab7794f701a4df59fc243ddc58f0b4d
+#: ../../managing_networks.rst:2901
+msgid ""
+"The admin is allowed to enable or disable GSLB functionality at region "
+"level."
+msgstr "管理员允许开启或禁用地域级别的GSLB功能。"
+
+# 3d725c2417e04077a8bd810b305cc12d
+#: ../../managing_networks.rst:2906
+msgid "The admin is allowed to configure a zone as GSLB capable or enabled."
+msgstr "管理员具有启用或配置区域为GSLB的能力"
+
+# af63547d61ae47bc8806fe8dec44724a
+#: ../../managing_networks.rst:2908
+msgid ""
+"A zone shall be considered as GSLB capable only if a GSLB service provider "
+"is provisioned in the zone."
+msgstr "只有在GSLB服务提供者提供的区域中，该区域才被视为有GSLB能力。"
+
+# bd3583e6473d458e8903768b80ac420d
+#: ../../managing_networks.rst:2913
+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 "当用户的VMs部署在启用GSLB功能的多个可用区域中时，他们可以使用GSLB功能在多个区域中将VM的流量进行负载均衡。"
+
+# d3eae7bb192b4cf5999d1cad4530ce6c
+#: ../../managing_networks.rst:2919
+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 "如果管理员在地域中启用了GSLB，用户可以使用GSLB对地狱中的所有区域的VMs进行负载均衡。"
+
+# 722a4c917dfc4316a8a5ee4e1d2473f0
+#: ../../managing_networks.rst:2924
+msgid ""
+"The users can load balance traffic across the availability zones in the same"
+" region or different regions."
+msgstr "用户可以为同一个区域或不同地域间可用的区域流量进行负载均衡。"
+
+# f3e00c0dbac94afaa7fc338683627630
+#: ../../managing_networks.rst:2929
+msgid "The admin can configure DNS name for the entire cloud."
+msgstr "管理员可以为整个云配置DNS名称。"
+
+# 381667b65f5b41c3ba49502ed236dee2
+#: ../../managing_networks.rst:2933
+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 "用户可以为云中的全局负载均衡服务指定一个唯一的名称。所提供名称的域名相当于云的DNS名称。"
+
+# c2b3095096774c50860988ec9732c71f
+#: ../../managing_networks.rst:2937
+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 "用户提供的名称与管理员提供的DNS名称一起为用户的全局负载均衡服务产生一个全局解析的FQDN。例如，如果管理员已经配置xyztelco.com为云中的DNS名称，以及用户为GSLB虚拟服务器指定的名称为'foo'，那么GSLB虚拟服务器的FQDN名称是foo.xyztelco.com。"
+
+# 9cf64fad7b7949f98496453cb30e3f90
+#: ../../managing_networks.rst:2946
+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 "设置GSLB时，用户可以为GSLB跨区域的一部分选择负载均衡方式，例如 round robin。"
+
+# 2c50d1ce8e39415d907de0a6d851de14
+#: ../../managing_networks.rst:2951
+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 "用户应能设置区域级虚拟服务器的权重。负载均衡在分配流量时会考虑该权重。"
+
+# 29df9cd710bd46a0a9df9f49eb468dd5
+#: ../../managing_networks.rst:2957
+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 "该GSLB功能必须支持会话持久性，特定域名的一系列客户端请求被发送到同一个区域中的虚拟服务器上。"
+
+# 10872c3a649d420e9f119e3bbed98213
+#: ../../managing_networks.rst:2961
+msgid "Statistics is collected from each GSLB virtual server."
+msgstr "从每个GSLB虚拟服务器中收集统计数据。"
+
+# dd79dc700b3743df9f52e687a9db8068
+#: ../../managing_networks.rst:2964
+msgid "Enabling GSLB in NetScaler"
+msgstr "开启NetScaler的GSLB"
+
+# 156a972ed59b40038a4636321d763dae
+#: ../../managing_networks.rst:2966
+msgid "In each zone, add GSLB-enabled NetScaler device for load balancing."
+msgstr "在每个区域中，添加启用GSLB的NetScaler设备提供负载均衡。"
+
+# c7e4943746f845df836880e582050b87
+#: ../../managing_networks.rst:2970
+msgid "Log in as administrator to the CloudStack UI."
+msgstr "使用管理员登录到CloudStack管理界面。"
+
+# b9463a89aa57467d83d9432154c10a77
+#: ../../managing_networks.rst:2978
+msgid "In Zones, click View More."
+msgstr "点击区域中的查看更多。"
+
+# f1595ba6ced742f9bd9ef6be9b4b2e79
+#: ../../managing_networks.rst:2986
+msgid ""
+"Click the Physical Network tab, then click the name of the physical network."
+msgstr "点击物理网络选项卡，然后点击物理网络的名称。"
+
+# 63b81a3cbb9742a5bbe5dd55ba85ecff
+#: ../../managing_networks.rst:2991
+msgid "In the Network Service Providers node of the diagram, click Configure."
+msgstr "点击示意图'网络服务提供程序'中的配置"
+
+# 508b40545cbc4132b2cf1e4128540e5e
+#: ../../managing_networks.rst:2994
+msgid "You might have to scroll down to see this."
+msgstr "你可能需要向下滚动才能看到。"
+
+# 53115bf37dda43f8b8f3536dd4dd568b
+#: ../../managing_networks.rst:2998
+msgid "Click NetScaler."
+msgstr "点击NetScaler."
+
+# b5b0d0cc48334232a6a56069d7adaa9f
+#: ../../managing_networks.rst:3002
+msgid "Click Add NetScaler device and provide the following:"
+msgstr "点击添加NetScaler设备并提供如下信息："
+
+# ed5c0c0442f9456cb72dbedd1a84e668
+#: ../../managing_networks.rst:3004
+msgid "For NetScaler:"
+msgstr "对于NetScaler:"
+
+# 538c95af821f4027b75d4dc232db3305
+#: ../../managing_networks.rst:3008
+msgid "**IP Address**: The IP address of the SDX."
+msgstr "**IP地址**: SDX的IP地址。"
+
+# f90935d4f5d4451cbfb5cb650901d339
+#: ../../managing_networks.rst:3012
+msgid ""
+"**Username/Password**: The authentication credentials to access the device. "
+"CloudStack uses these credentials to access the device."
+msgstr "**用户名/密码.** 访问此设备的认证许可。CloudStack使用这些认证信息访问此设备。"
+
+# d5079aa5e4a549ada0c3aa62c5f2a6b8
+#: ../../managing_networks.rst:3018
+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 "**类型**：添加设备的类型。可以是F5 BigIP负载均衡器、NetScaler VPX、NetScaler MPX或 NetScaler SDX等设备。关于NetScaler的类型比较，请参阅CloudStack管理指南。"
+
+# 927bd20253b24539a81a89816522b622
+#: ../../managing_networks.rst:3025
+msgid ""
+"**Public interface**: Interface of device that is configured to be part of "
+"the public network."
+msgstr "**公共接口**: 配置为公共网络部分的设备接口。"
+
+# a9b26fd6edb640ab96c686fb82e63174
+#: ../../managing_networks.rst:3030
+msgid ""
+"**Private interface**: Interface of device that is configured to be part of "
+"the private network."
+msgstr "**专用接口**: 配置为专用网络部分的设备接口。"
+
+# f59521a2c8eb45b6b90edf7253c53f3f
+#: ../../managing_networks.rst:3035
+msgid "**GSLB service**: Select this option."
+msgstr "**GSLB 服务**:选择该选项。"
+
+# f279e0631abf48efbc96b3cea07c0f7e
+#: ../../managing_networks.rst:3039
+msgid ""
+"**GSLB service Public IP**: The public IP address of the NAT translator for "
+"a GSLB service that is on a private network."
+msgstr "**GSLB 服务公共IP**:在专用网络中，为GSLB服务提供NAT转换的公共IP地址。"
+
+# 06437d72b1314c92865ada3febe44c64
+#: ../../managing_networks.rst:3044
+msgid "**GSLB service Private IP**: The private IP of the GSLB service."
+msgstr "**GSLB 服务专用IP**: GSLB服务的专用IP地址。"
+
+# c1696819f3884157a9733431fe8f5347
+#: ../../managing_networks.rst:3048
+msgid ""
+"**Number of Retries**. Number of times to attempt a command on the device "
+"before considering the operation failed. Default is 2."
+msgstr "**重试次数** 尝试控制设备失败时重试的次数，默认为2次。"
+
+# 37c94cc408494e18a54ef8e730b7e3d3
+#: ../../managing_networks.rst:3053
+msgid "**Capacity**: The number of networks the device can handle."
+msgstr "**容量**：该设备能处理的网络数量。"
+
+# 3cf0408da21d4c4080772f511c283988
+#: ../../managing_networks.rst:3057
+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 "**专用**: 当标记为专用后，这个设备只对单个帐号专用。该选项被勾选后，容量选项就没有了实际意义且值会被置为1。"
+
+# 2f16286d06b34cfbb0c778f84f978767
+#: ../../managing_networks.rst:3067
+msgid "Adding a GSLB Rule"
+msgstr "添加 GSLB规则"
+
+# 039473a14f4b4214ba12771983f2fc83
+# f23106a7198949aa85bdb7abe8be1ff4
+#: ../../managing_networks.rst:3071 ../../managing_networks.rst:3140
+msgid "Log in to the CloudStack UI as a domain administrator or user."
+msgstr "使用管理员或者用户账号登录CloudStack UI。"
+
+# f297c9cec43e40e2ab81e6dcf9c29486
+# 6831e687e51f441493ff214593172f42
+#: ../../managing_networks.rst:3075 ../../managing_networks.rst:3144
+msgid "In the left navigation pane, click Region."
+msgstr "在左边的导航栏里，点击区域（为文档翻译中地域的概念，英文为region，下同）"
+
+# 1671ccbb5a484e7cb4675d75434115b1
+# 7ee2d894c2e44271b0b7cf58a1398b29
+#: ../../managing_networks.rst:3079 ../../managing_networks.rst:3148
+msgid "Select the region for which you want to create a GSLB rule."
+msgstr "选择你想创建GSLB规则的地域。"
+
+# 6e5c6390b5cb4211962d11c2860e768e
+# 18b5fb7710ae4f039c9f3248fc046b59
+#: ../../managing_networks.rst:3083 ../../managing_networks.rst:3152
+msgid "In the Details tab, click View GSLB."
+msgstr "在详细选项卡中，点击查看GSLB。"
+
+# 3bd105d046e04354911f2b627f21d5dd
+#: ../../managing_networks.rst:3087
+msgid "Click Add GSLB."
+msgstr "点击添加GSLB。"
+
+# 77c33d27873f48b8bb209ab50d2a73ac
+#: ../../managing_networks.rst:3089
+msgid "The Add GSLB page is displayed as follows:"
+msgstr "添加GSLB页面显示如下："
+
+# 11522ea2b2de46708f6b45158dfcf5df
+#: ../../managing_networks.rst:3091
+msgid "|gslb-add.png: adding a gslb rule|"
+msgstr "|gslb-add.png: adding a gslb rule|"
+
+# df1dc1cd07d8438d9e684fd70afe8e7a
+#: ../../managing_networks.rst:3099
+msgid "**Name**: Name for the GSLB rule."
+msgstr "**名称**: GSLB规则的名称。"
+
+# 9d0c2f980b4f48f7b7d5153d414e2bc0
+#: ../../managing_networks.rst:3103
+msgid ""
+"**Description**: (Optional) A short description of the GSLB rule that can be"
+" displayed to users."
+msgstr "**描述**: (可选)为用户提供一个简短的GSLB规则描述。 "
+
+# bd6458bb4ab147b9b5a5483035bff382
+#: ../../managing_networks.rst:3108
+msgid "**GSLB Domain Name**: A preferred domain name for the service."
+msgstr "**GSLB 域名**: 首选的域名服务。"
+
+# 8ea3f203884e47b6a1d8d90fe8125bf0
+#: ../../managing_networks.rst:3112
+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 "**算法**: (可选) 用于跨区域流量负载均衡的算法。可选项为 Round Robin, Least Connection, 和Proximity."
+
+# 4d8d6961170041cfada0392ecb570560
+#: ../../managing_networks.rst:3118
+msgid ""
+"**Service Type**: The transport protocol to use for GSLB. The options are "
+"TCP and UDP."
+msgstr "**服务类型**: GSLB使用的传输协议。可选项为TCP和UDP。"
+
+# 77dcf4c2f0024309b529be408e435cee
+#: ../../managing_networks.rst:3123
+msgid ""
+"**Domain**: (Optional) The domain for which you want to create the GSLB "
+"rule."
+msgstr "**域**: (可选) 你想要创建GSLB规则的域。"
+
+# fcaa38e31d864b25b64102b670470c2c
+#: ../../managing_networks.rst:3128
+msgid ""
+"**Account**: (Optional) The account on which you want to apply the GSLB "
+"rule."
+msgstr "**账户**: (可选) 应用GSLB规则的账户。"
+
+# 76446b2d9e054665bbca7c01ac0559fa
+#: ../../managing_networks.rst:3136
+msgid "Assigning Load Balancing Rules to GSLB"
+msgstr "为GSLB分配负载均衡规则"
+
+# 1be9eb92d540481b97cd2f99cc3ab9d6
+#: ../../managing_networks.rst:3156
+msgid "Select the desired GSLB."
+msgstr "选择所需的GSLB。"
+
+# b437092b9f2a488585dbe73e5068870b
+#: ../../managing_networks.rst:3160
+msgid "Click view assigned load balancing."
+msgstr "点击已分配的负载均衡视图。"
+
+# eda19bddac444d22aaf6944b81ac6574
+#: ../../managing_networks.rst:3164
+msgid "Click assign more load balancing."
+msgstr "点击分配更多负载平衡"
+
+# 44acd11aec3d42869b12198753256ae7
+#: ../../managing_networks.rst:3168
+msgid "Select the load balancing rule you have created for the zone."
+msgstr "选择你将为区域创建的负载均衡规则。"
+
+# 77eb5dcff40842b1b2e565776e642fa5
+#: ../../managing_networks.rst:3175
+msgid "Known Limitation"
+msgstr "已知的局限性"
+
+# eee28dc26a8c43daa149baee5774cd3e
+#: ../../managing_networks.rst:3177
+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 "目前，CloudStack并不支持跨区域的服务编排。将引入服务的概念和地域服务提供者。"
+
+# 6ce352ece3ec4e588cb58d78a6a43ab9
+#: ../../managing_networks.rst:3182
+msgid "Guest IP Ranges"
+msgstr "来宾IP范围"
+
+# b9ae2154009d4c7c8135987e8ac86e2c
+#: ../../managing_networks.rst:3184
+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 "宾客网络流量的IP是由用户以帐号为基础设置的。这允许用户以在他们的宾客网络和他们的客户端之间开通VPN连接的方式配置他们的网络。"
+
+# de46e5574bf54dd68d71bdd2b1dd9a8b
+#: ../../managing_networks.rst:3189
+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 `Section 15.10, “About Multiple IP Ranges” <#multiple-ip-"
+"range>`__."
+msgstr "存在基本网络和启用安全组的高级网络中的共享网络，你可以灵活的在不同子网中添加多个来宾IP范围。你可以同时添加或移除IP范围。更多信息，请参阅 `章节 15.10, “关于多IP范围” <#multiple-ip-range>`__."
+
+# b24a8efdf2824070a8500affcc044a77
+#: ../../managing_networks.rst:3196
+msgid "Acquiring a New IP Address"
+msgstr "获得一个新的IP地址"
+
+# 6392b71aa674434c8fea3a1269449799
+#: ../../managing_networks.rst:3224
+msgid ""
+"If you want Portable IP click Yes in the confirmation dialog. If you want a "
+"normal Public IP click No."
+msgstr "如果你想作为 Portable IP则在确认窗口中点击Yes，如果你想作为正常的公共IP则点击No。"
+
+# 1b67f1c2681f421e95e01179c36b4c0b
+#: ../../managing_networks.rst:3227
+msgid ""
+"For more information on Portable IP, see `Section 15.12, “Portable IPs” "
+"<#portable-ip>`__."
+msgstr "更多关于 Portable IP的信息，请参阅 `章节 15.12, “Portable IPs” <#portable-ip>`__."
+
+# 97d72bd6a40a40e7bd59c0c736a8bbdd
+#: ../../managing_networks.rst:3235
+msgid "Releasing an IP Address"
+msgstr "释放IP地址"
+
+# f52a271b737d4215a2e21b2c934efdd4
+#: ../../managing_networks.rst:3237
+msgid ""
+"When the last rule for an IP address is removed, you can release that IP "
+"address. The IP address still belongs to the VPC; however, it can be picked "
+"up for any guest network again."
+msgstr "当IP的最后一条规则删除后，您就能够释放该IP。然而，该IP仍属于VPC，无论如何，该IP可以再次被VPC中的来宾网络再次获取。"
+
+# 656f51251c854bb6a971b2cb29b0d8ef
+#: ../../managing_networks.rst:3259
+msgid "Click the IP address you want to release."
+msgstr "点击要释放的IP地址。"
+
+# 2572dd822bef4a2f955e7507de6a2171
+#: ../../managing_networks.rst:3263
+msgid ""
+"Click the Release IP button. |ReleaseIPButton.png: button to release an IP|"
+msgstr "点击释放IP按钮， |ReleaseIPButton.png: button to release an IP|"
+
+# 5b2ef9957d5c4f35a32f9d7da23e6693
+# 41297f054dbd4ab0a958c0998f5d7ffd
+# 2ab2cc311faf4a23bcbd99703f0f47e1
+# d5758556343045dd918e7f592bbba40e
+# 07b2dc015092473aa0a048a6cc59b7b8
+# 26b03a50edbe4d8bb41144c0cada25e2
+# 127f42037f3448d38c791df3fb08fec1
+# 6e8aef87be834395857821e832eedc81
+# 75e095f3e2b343a2a5ebf18c29c3c74e
+# a4224fe4d3e84991adba7f4f79e22ccd
+# 37046dfed9524c6689ce685c5fe137b8
+# 1491471208484e0794022798a18c6235
+#: ../../managing_networks.rst:3267 ../../managing_networks.rst:3838
+#: ../../managing_networks.rst:4285 ../../managing_networks.rst:4385
+#: ../../managing_networks.rst:4579 ../../managing_networks.rst:5185
+#: ../../managing_networks.rst:5443 ../../managing_networks.rst:5768
+#: ../../managing_networks.rst:5855 ../../managing_networks.rst:5946
+#: ../../managing_networks.rst:6188 ../../managing_networks.rst:6580
+msgid "Static NAT"
+msgstr "静态 NAT"
+
+# 8b9ec9bf10d04ae79f278146e90a9d9b
+#: ../../managing_networks.rst:3269
+msgid ""
+"A static NAT rule maps a public IP address to the private IP address of a VM"
+" in order to allow Internet traffic into the VM. The public IP address "
+"always remains the same, which is why it is called “static” NAT. This "
+"section tells how to enable or disable static NAT for a particular IP "
+"address."
+msgstr "一条静态 NAT 规则映射一个公网 IP 地址到一台虚拟机的私网 IP 地址，目的是允许互联网的流量到该虚拟机。 公网 IP 地址总是保持为同一地址，这就是为什么被称为 \"静态\" NAT。 本节描述如何将一个特定的IP地址设为或取消静态NAT。"
+
+# c431000325b74754a499d98af7351495
+#: ../../managing_networks.rst:3276
+msgid "Enabling or Disabling Static NAT"
+msgstr "启用或禁用静态NAT"
+
+# b2c066da76814877b47541a473f572fb
+# 3f56828c583c46ad81eaedeff63fb850
+#: ../../managing_networks.rst:3278 ../../managing_networks.rst:5905
+msgid ""
+"If port forwarding rules are already in effect for an IP address, you cannot"
+" enable static NAT to that IP."
+msgstr "如果该公网IP上已经有端口转发规则，则不允许再启用静态NAT。"
+
+# ab68fbb3395e429fa804a3969d8011a5
+# f9f86036dd7b4dd391c93c88952259d1
+#: ../../managing_networks.rst:3281 ../../managing_networks.rst:5908
+msgid ""
+"If a guest VM is part of more than one network, static NAT rules will "
+"function only if they are defined on the default network."
+msgstr "如果用户VM存在多个网络，则静态NAT规则仅在默认网络上定义时生效。"
+
+# 3c704e04efc744568700070163b3ca1d
+# fa28626438294e07bd64b0c07f6bb8a2
+#: ../../managing_networks.rst:3302 ../../managing_networks.rst:3378
+msgid "Click the IP address you want to work with."
+msgstr "点击你要修改的IP地址"
+
+# 5ad8bdba63064885a50259f19f0a3650
+#: ../../managing_networks.rst:3306
+msgid ""
+"Click the Static NAT |EnableNATButton.png: button to enable NAT| button."
+msgstr "点击静态NAT按钮 |EnableNATButton.png: button to enable NAT|。"
+
+# 5608c079e4984a898941e97d9040e080
+#: ../../managing_networks.rst:3309
+msgid ""
+"The button toggles between Enable and Disable, depending on whether static "
+"NAT is currently enabled for the IP address."
+msgstr "该按钮在启用和禁用之间切换，这取决于IP地址是否已经启用了静态NAT。"
+
+# c44f31d84d4946bba279c07ffae37af3
+#: ../../managing_networks.rst:3314
+msgid ""
+"If you are enabling static NAT, a dialog appears where you can choose the "
+"destination VM and click Apply."
+msgstr "如果是启用静态NAT，会出现一个对话框让您选择目标VM然后点击应用。"
+
+# 0239068895f846728ff792196d9e8c78
+#: ../../managing_networks.rst:3318
+msgid "IP Forwarding and Firewalling"
+msgstr "IP转发及防火墙"
+
+# 38b50d6982c14a78b97c1004a1d32b97
+#: ../../managing_networks.rst:3320
+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 "默认情况下, 所有从公共IP进来的流量都会被拒绝. 所有在来宾网络出去的流量默认也被阻挡。"
+
+# 4374970c184442e1bff7de64f1a19a7b
+#: ../../managing_networks.rst:3323
+msgid ""
+"To allow outgoing traffic, follow the procedure in `Section 15.22.2, “Egress"
+" Firewall Rules in an Advanced Zone” <#egress-firewall-rule>`__."
+msgstr "为了允许外出的流量，遵循 `章节 15.22.2, “高级区域中的外出防火墙规则” <#egress-firewall-rule>`__ 中的步骤。"
+
+# 4cb1f00da457462d9550d7a7750f2313
+#: ../../managing_networks.rst:3326
+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 "为了允许接收到的流量, 用户可以设置一些防火墙规则和/或端口转发规则. 例如, 你可以在公共IP地址上设定防火墙规则来打开一个端口范围, 比如从33到44端口. 然后使用端口转发将流量从这个特定的范围内的端口直接送到指定的用户虚机端口. 例如, 一个端口转发的规则可以将接收的流量从公共IP的33端口到用户虚机私有IP的100端口."
+
+# 30b73ffad3e84ae2ac5dcec10260b433
+#: ../../managing_networks.rst:3335
+msgid "Firewall Rules"
+msgstr "防火墙规则"
+
+# 65002cba7c554a759449b2c27f7e9931
+#: ../../managing_networks.rst:3337
+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 "默认情况下，防火墙拒绝所有流入公共IP的流量。要允许外部流量，你需要制定防火墙规则打开防火墙端口。你可以选择性的制定一个或多个CIDR来过滤来源IP。这在当你只需要允许特定IP请求时会很有用。"
+
+# 0eadbb8127ba4f50ad1f3a2ac2b73049
+#: ../../managing_networks.rst:3343
+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 `Section 15.15.2, “Adding a Security Group” <#add-"
+"security-group>`__."
+msgstr "你不能使用防火墙规则打开弹性IP的端口。当弹性IP处在使用状态时，外部的通过请求将被安全组管理。参阅 `章节 15.15.2, “Adding a Security Group” <#add-security-group>`__."
+
+# 47591452f5c348b7a4836500eaeeb54f
+#: ../../managing_networks.rst:3348
+msgid ""
+"In an advanced zone, you can also create egress firewall rules by using the "
+"virtual router. For more information, see `Section 15.22.2, “Egress Firewall"
+" Rules in an Advanced Zone” <#egress-firewall-rule>`__."
+msgstr "在高级Zone中，您也可以用虚拟路由器来创建外出的防火墙规则。参阅 `章节 15.22.2, “高级区域中的出口防火墙规则” <#egress-firewall-rule>`__."
+
+# d9b6ac1930d14ffaa3eae10de83b88f2
+#: ../../managing_networks.rst:3352
+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 "防火墙规则能在管理服务器的UI中防火墙选项卡里创建，CloudStac安装好以后，这个规则选项卡默认不显示，你需要以管理员身份修改全局变量 firewall.rule.ui.enabled为 \"true\"才能显示。"
+
+# 41479731d8d84d99a6aa8925a91d371b
+#: ../../managing_networks.rst:3358
+msgid "To create a firewall rule:"
+msgstr "创建防火墙规则："
+
+# 379f460faa18445583d749503ad81606
+#: ../../managing_networks.rst:3382
+msgid "Click the Configuration tab and fill in the following values."
+msgstr "点击设置选项卡 填入以下值："
+
+# 7923d613a47543f2a046a93f3a08a992
+#: ../../managing_networks.rst:3386
+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 "**源 CIDR**.(可选)只允许在某个特定地址块的IP流量的话，输入一个CIDR或者一个逗号隔开的CIDR列表。例如：192.168.0.0/22或者192.168.0.0/24,192.168.1.0/24,192.168.2.0/24。留空则为允许所有的CIDR。"
+
+# ff573c7c40d94c24a43dc4e21ed8cc30
+#: ../../managing_networks.rst:3393
+msgid "**Protocol**. The communication protocol in use on the opened port(s)."
+msgstr "**Protocol**: 已打开的端口所使用的通信协议。"
+
+# 14466f1425f9488c824bc5507b812a10
+#: ../../managing_networks.rst:3398
+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 "**起始端口和结束端口**. 你想要在防火墙上开放的端口。如果你只打开单个端口，在两个空格中填入相同的端口号。"
+
+# eff1095b7f204f83bfca43d956620036
+#: ../../managing_networks.rst:3404
+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 "**ICMP 类型和代码**.只有在设置ICMP协议时才会用到。提供需要填写的ICMP协议，ICMP包头的类型和代码。如果你不知道如何填写请参看ICMP文档。（这里推荐一个 http://wenku.baidu.com/view/e235e8ecaeaad1f346933fed.html）"
+
+# c334f1f90dbf49c4935f21d4c1bb417c
+#: ../../managing_networks.rst:3414
+msgid "Egress Firewall Rules in an Advanced Zone"
+msgstr "高级区域中的出口防火墙规则"
+
+# 939aa6e067b64d47a83d181a3e4e5527
+#: ../../managing_networks.rst:3416
+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 rules are removed the default "
+"policy, Block, is applied."
+msgstr "出口流量起源于从专用网络访问公共网络，例如Internet。默认情况下，在默认网络方案中，出口流量被拒绝，所以没有从来宾网络到Internet的出口流量被允许。不过，你可以通过创建出口防火墙规则来控制高级网络中的出口流量。当出口防火墙规则被应用时，规则指定的流量被允许，其余的流量被阻止。当所有的防火墙规则从默认策略中移除，阻止策略再次被应用。"
+
+# 7a04d621e9684c64a589eb43631ba804
+#: ../../managing_networks.rst:3428
+msgid "Consider the following scenarios to apply egress firewall rules:"
+msgstr "应用出口防火墙规则时请思考如下方案："
+
+# 774794905f1a490fbaadf61a60da50fc
+#: ../../managing_networks.rst:3432
+msgid "Egress firewall rules are supported on Juniper SRX and virtual router."
+msgstr "出口防火墙规则在Jniper SRX和虚拟路由器中均支持。"
+
+# 46f8243d01b443d09201acc237d75fc9
+#: ../../managing_networks.rst:3437
+msgid "The egress firewall rules are not supported on shared networks."
+msgstr "共享网络中不支持出口防火墙规则。"
+
+# f88ff0e199cc453ea42eec0dfc9125b1
+#: ../../managing_networks.rst:3441
+msgid ""
+"Allow the egress traffic from specified source CIDR. The Source CIDR is part"
+" of guest network CIDR."
+msgstr "允许特定源CIDR的出口流量。源CIDR是来宾网络CIDR的一部分。"
+
+# d8800840b30d44929ddbb3b604c97f02
+#: ../../managing_networks.rst:3446
+msgid "Allow the egress traffic with protocol TCP,UDP,ICMP, or ALL."
+msgstr "允许出口流量的协议为TCP，UDP,ICMP或ALL。"
+
+# 26294a9e847940889657b436b3a4aa23
+#: ../../managing_networks.rst:3450
+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 "允许出口流量协议和目标端口范围。端口范围需要指定TCP，UDP或ICMP类型和代码。"
+
+# c0afd204dff547fb87834d7abc9c1f8e
+#: ../../managing_networks.rst:3455
+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 "新网络方案的默认策略是允许的，然而升级现有的网络方案后，防火墙服务提供商的出口策略默认将是拒绝。"
+
+# 850dd34086424c9ab68601f13834bcd2
+#: ../../managing_networks.rst:3460
+msgid "Configuring an Egress Firewall Rule"
+msgstr "配置出口防火墙规则"
+
+# 3615eb46ce214f7d9cbf957a06371666
+#: ../../managing_networks.rst:3472
+msgid ""
+"In Select view, choose Guest networks, then click the Guest network you "
+"want."
+msgstr "在选择视图中，选择来宾网络，然后点击需要的来宾网络。"
+
+# 359f42a9094342b29e083f461a84405b
+#: ../../managing_networks.rst:3477
+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 "要添加出口策略，点击出口策略选项卡并填写以下字段指定哪种类型的流量在来宾网络中是被允许从VM中实例发送出的。"
+
+# f203654bfaa44a6989bda0673da8a470
+#: ../../managing_networks.rst:3481
+msgid "|egress-firewall-rule.png: adding an egress firewall rule|"
+msgstr "|egress-firewall-rule.png: adding an egress firewall rule|"
+
+# e1ee94ade2e54545b51b809a12f729dd
+#: ../../managing_networks.rst:3485
+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 "**CIDR**:(仅通过CIDR添加)为接受来来自特殊地址块的流量，输入一个CIDR，多个时用逗号隔开。CIDR是进入流量的基础IP地址。例如：192.168.0.0/22，为允许所有CIDR，请设为0.0.0.0/0"
+
+# 142d121ba8884e97abf630ab11c3ba47
+#: ../../managing_networks.rst:3493
+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 "**协议**: 虚拟机发送流量所使用的网络协议。TCP和UDP通常用于数据交换和用户通讯。ICMP通常用于发送出错信息和网络监控数据。"
+
+# a6aa5a49dfb948f9b0f88c0b723666df
+#: ../../managing_networks.rst:3500
+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 "**开始端口，结束端口**: (仅对TCP，UDP)。目的地为进入流量而设的监听端口范围。如果仅开放了单个端口，则在两者的区域中用同一端口。"
+
+# bdf38163ee3d40d1905ccf2ac8827421
+#: ../../managing_networks.rst:3506
+msgid ""
+"**ICMP Type, ICMP Code**: (ICMP only) The type of message and error code "
+"that are sent."
+msgstr "**ICMP类型**, **ICMP代码** (ICMP only): 信息类型及发送错误的代码。"
+
+# 4fd631620dc649139065e335358cbd24
+#: ../../managing_networks.rst:3514
+msgid "Configuring the Default Egress Policy"
+msgstr "配置默认出口策略"
+
+# 19008ef0cc514c859de0de2daede053c
+#: ../../managing_networks.rst:3516
+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 "通过网络方案配置隔离来宾网络的默认出口策略。通过创建网络方案选项决定来宾网络到公共网络的所有流量在默认策略中是允许或者拒绝。使用该网络方案创建网络。如果没有指定策略，你创建的来宾网络中的所有流量将被允许。"
+
+# 79bc5b57e2f94789bdff8bbfac2ddcfb
+#: ../../managing_networks.rst:3524
+msgid "You have two options: Allow and Deny."
+msgstr "你有两个选择：允许和拒绝。"
+
+# 1224fcbce5c74fe3b947356b896ca579
+#: ../../managing_networks.rst:3527
+msgid "Allow"
+msgstr "允许"
+
+# e2a646bdb2d74e4db9d2599d28f6235a
+#: ../../managing_networks.rst:3529
+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 "如果你选择网络方案为允许，则默认出口流量被允许。无论如何，当配置了来宾网络的出口规则，规则被应用于阻止特定的流量和允许其他的 。如果网络中没有配置出口规则，则出口流量会被放行。"
+
+# 749247337d834c6c9277066a5d52c328
+# 8779b4214ba9455abd8c51e7029da31a
+# e800ddb4ba3d4858ba5fbf7c30acd2e4
+#: ../../managing_networks.rst:3536 ../../managing_networks.rst:5146
+#: ../../managing_networks.rst:5147
+msgid "Deny"
+msgstr "拒绝"
+
+# 3a06b12ffe614d1cab452a989a8f917f
+#: ../../managing_networks.rst:3538
+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 "如果你选择网络方案为拒绝，则来宾网络中的默认出口流量将被阻挡。无论如何，当配置了来宾网络的出口规则，规则被应用于允许特定的流量。当实施来宾网络时，CloudStack为来宾网络添加防火墙出口规则指定默认的出口策略。"
+
+# 6196e56e021042f4a3ebd91573fbbf60
+#: ../../managing_networks.rst:3545
+msgid "This feature is supported only on virtual router and Juniper SRX."
+msgstr "该特定只支持虚拟路由器和Juniper SRX。"
+
+# 7bdc8fc3675346f1a13f9c19d80abfd7
+#: ../../managing_networks.rst:3549
+msgid "Create a network offering with your desirable default egress policy:"
+msgstr "为合适的默认出口策略创建一个网络方案："
+
+# 132ba5854a684a0484908e19f74b3d44
+#: ../../managing_networks.rst:3553
+msgid "Log in with admin privileges to the CloudStack UI."
+msgstr "以管理员权限登录CloudStack用户界面。"
+
+# 71eec5bf534f4946b6c4daaf8df613a6
+#: ../../managing_networks.rst:3557
+msgid "In the left navigation bar, click Service Offerings."
+msgstr "在左侧导航栏中，点击 服务方案。"
+
+# 89d1b1ad418a45b087b1a5650dfbb68b
+#: ../../managing_networks.rst:3561
+msgid "In Select Offering, choose Network Offering."
+msgstr "在选择方案中，选择网络方案。"
+
+# 14b63d7663f845a785bdd4d17da6c813
+# ca405e366b0a4757b0f24381859548f3
+# e9ca1c0eaa53479c9b838d602582aa03
+#: ../../managing_networks.rst:3565 ../../managing_networks.rst:6072
+#: ../../managing_networks.rst:6376
+msgid "Click Add Network Offering."
+msgstr "点击添加网络方案。"
+
+# a3f5cfaea903420c9a12c152a3293b17
+#: ../../managing_networks.rst:3569
+msgid "In the dialog, make necessary choices, including firewall provider."
+msgstr "在对话框中，填写必选项，包括防火墙提供者。"
+
+# ce35e9aadd4542cbacf3656f44f89af7
+#: ../../managing_networks.rst:3574
+msgid "In the Default egress policy field, specify the behaviour."
+msgstr "在默认出口策略选项中，指定行为。"
+
+# 23199bdde5f24a939b68fb46fd1019fb
+#: ../../managing_networks.rst:3582
+msgid "Create an isolated network by using this network offering."
+msgstr "使用网络方案创建隔离网络。"
+
+# 2b39e12e5b3d4d39a933c682cc18b149
+#: ../../managing_networks.rst:3584
+msgid ""
+"Based on your selection, the network will have the egress public traffic "
+"blocked or allowed."
+msgstr "根据你的选择，网络的出口公共流量将被拒绝或允许。"
+
+# 2e4756b361a14c97a83a29b5f8d1a311
+#: ../../managing_networks.rst:3588
+msgid "Port Forwarding"
+msgstr "端口转发"
+
+# a08ae5e9620d44ff84ce14445856b2c3
+#: ../../managing_networks.rst:3590
+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 "一个端口转发服务是一系列转发转发规则的集合。一个端口转发服务随后可以应用于一个或多个来宾虚拟机。来宾虚拟机会根据端口转发规则作相关进入端口的管理。你可以定义一个或多个CIDR来过滤源IP地址。当你只希望特定的IP流量进入时是相当有用的。"
+
+# 878cdf1503f94e3187e805b44534fed9
+#: ../../managing_networks.rst:3598
+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 "一个客户VM可以在任意数量的端口转发服务中。端口转发服务可以不包含客户VM。如果客户VM在多个网络中，则端口转发仅在默认网络中定义时才生效。"
+
+# ca75695902264086b479704a64871a64
+#: ../../managing_networks.rst:3603
+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 "您不能使用端口转发打开弹性IP地址的端口。当使用弹性IP时，外部访问是由安全组控制的。参见安全组。"
+
+# 550c9e8578014be1bde72e80f78d199c
+#: ../../managing_networks.rst:3607
+msgid "To set up port forwarding:"
+msgstr "设置端口转发："
+
+# 1579f539fb6d428486e2cb9316570a6b
+#: ../../managing_networks.rst:3615
+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 "如果还没有，请在 CloudStack中为Zone添加公网IP段。参阅 安装指南中的添加Zone和Pod。"
+
+# baee90c3d614427590853d7141e1ee1b
+#: ../../managing_networks.rst:3621
+msgid "Add one or more VM instances to CloudStack."
+msgstr "在 CloudStack中创建1台或更多VM。"
+
+# aa5921d82f6a429ca3d83e2d9e3991cd
+#: ../../managing_networks.rst:3625
+msgid "In the left navigation bar, click Network."
+msgstr "在左边导航栏，点击网络。"
+
+# 6f69e80b5b984c18a3a7652157412174
+#: ../../managing_networks.rst:3629
+msgid "Click the name of the guest network where the VMs are running."
+msgstr "点击需要操作VM所在的网络名称。"
+
+# aaa0315049f346cb878ebb96c9c25a9c
+#: ../../managing_networks.rst:3633
+msgid ""
+"Choose an existing IP address or acquire a new IP address. See `Section "
+"15.19, “Acquiring a New IP Address” <#acquire-new-ip-address>`__. Click the "
+"name of the IP address in the list."
+msgstr "选择一个已有的IP或者获取一个新的IP地址。参阅 `章节 15.19, “获取新的IP地址” <#acquire-new-ip-address>`__. 点击列表中IP地址的名称。"
+
+# 2b948665b23443059e227f2a987a4af4
+#: ../../managing_networks.rst:3640
+msgid "Click the Configuration tab."
+msgstr "点击配置选项卡。"
+
+# ef12d2f0ebca484fbec9fe3b4ea476ce
+# 86470a41e0e143c8abee911f793f5139
+#: ../../managing_networks.rst:3644 ../../managing_networks.rst:6621
+msgid "In the Port Forwarding node of the diagram, click View All."
+msgstr "在图表的端口转发节点，点击查看所有。"
+
+# 70b067742c7e494faa545e59e67e509f
+#: ../../managing_networks.rst:3652
+msgid ""
+"**Public Port**. The port to which public traffic will be addressed on the "
+"IP address you acquired in the previous step."
+msgstr "**公用端口**:你在之前操作时所获取的供公共流量使用的公用IP地址的端口。 "
+
+# 3c48fdadff09491b8ccdfa491ef23b13
+#: ../../managing_networks.rst:3657
+msgid ""
+"**Private Port**. The port on which the instance is listening for forwarded "
+"public traffic."
+msgstr "**专用端口**: 虚拟机监听转发的公网流量的端口。"
+
+# 9b1ee2382ca242bea410d9e0fec0de21
+#: ../../managing_networks.rst:3662
+msgid "**Protocol**. The communication protocol in use between the two ports"
+msgstr "**Protocol**:两个端口之间使用的通信协议。"
+
+# b5fdf68205af49fe949bb74f27cb03ef
+#: ../../managing_networks.rst:3670
+msgid "IP Load Balancing"
+msgstr "IP负载均衡"
+
+# f4415093dc35468c97c273710e3fd019
+#: ../../managing_networks.rst:3672
+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 "用户可以选择关联同一个公网IP到多个虚拟机。 CloudStack实现了TCP级别的负载平衡器，有以下策略。"
+
+# 9643d81461b54c18b510cec02c55b76a
+# 8ff79894623b4f75ad7b797363bc1802
+# f5133113ba364c81bb4607616c3e51b2
+#: ../../managing_networks.rst:3678 ../../managing_networks.rst:6261
+#: ../../managing_networks.rst:6532
+msgid "Round-robin"
+msgstr "轮询"
+
+# 1599b1d2a49941089fba2c32b3639b28
+#: ../../managing_networks.rst:3682
+msgid "Least connection"
+msgstr "最少连接数"
+
+# a23492e21cb742b2b97b33f4b5ab151f
+#: ../../managing_networks.rst:3686
+msgid "Source IP"
+msgstr "源IP"
+
+# 728ff8a92c5a4fa4875aff65b6a6e20a
+#: ../../managing_networks.rst:3688
+msgid ""
+"This is similar to port forwarding but the destination may be multiple IP "
+"addresses."
+msgstr "这类似于端口转发，但目标可能会有多个IP地址。"
+
+# d5e9852ee80440fe9204fac406dd593d
+#: ../../managing_networks.rst:3692
+msgid "DNS and DHCP"
+msgstr "DNS和DHCP"
+
+# 0e9e9564f8514da08c6206315a3eaa34
+#: ../../managing_networks.rst:3694
+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 "虚拟路由器为来宾提供DNS和DHCP服务。它将DNS请求代理到在可用区域中配置的DNS服务器。"
+
+# b8ff527b8b13466885b0c515030f73dd
+#: ../../managing_networks.rst:3699
+msgid "Remote Access VPN"
+msgstr "远程访问VPN"
+
+# c381ec096f69422e8176e92e2f15b737
+#: ../../managing_networks.rst:3701
+msgid ""
+"CloudStack account owners can create virtual private networks (VPN) to "
+"access their virtual machines. If the guest network is instantiated from a "
+"network offering that offers the Remote Access VPN service, the virtual "
+"router (based on the System VM) is used to provide the service. CloudStack "
+"provides a L2TP-over-IPsec-based remote access VPN service to guest virtual "
+"networks. Since each network gets its own virtual router, VPNs are not "
+"shared across the networks. VPN clients native to Windows, Mac OS X and iOS "
+"can be used to connect to the guest networks. The account owner can create "
+"and manage users for their VPN. CloudStack does not use its account database"
+" for this purpose but uses a separate table. The VPN user database is shared"
+" across all the VPNs created by the account owner. All VPN users get access "
+"to all VPNs created by the account owner."
+msgstr "CloudStack中的账户拥有者可以建立虚拟专用网(VPN)以便访问他们的虚拟机。如果通过网络方案对来宾网络提供远程VPN访问服务的实例化，虚拟路由(基于System VM)将被用于提供服务。CloudStack为来宾虚拟网络提供了一个基于L2TP-over-IPsec-based协议的远程VPN访问服务。因为每个网络有它自己的虚拟路由器，VPNs不能跨网络共享。Windows, Mac OS X和iOS自带的VPN客户端可以用于访问来宾网络。账户拥有者可以建立并管理他们的VPN用户。CloudStack并不为此使用自己的账户数据库，而是使用一个独立的表。VPN用户数据库在同一个账户拥有者建立的VPN网络中被共享。 也就是说，同一个账户拥有者创建的所有VPN可以被它的所有VPN用户访问。"
+
+# 3bb8afa8e0d549448cda76518414eb07
+#: ../../managing_networks.rst:3715
+msgid ""
+"Make sure that not all traffic goes through the VPN. That is, the route "
+"installed by the VPN should be only for the guest network and not for all "
+"traffic."
+msgstr "确保不是所有的网络流量走VPN。也就是说，用于配置VPN的route不是唯一用于该guest network，也不承担全部的网络流量。"
+
+# d295f3aefec94637a6b5ecbd5c09110a
+#: ../../managing_networks.rst:3719
+msgid ""
+"**Road Warrior / Remote Access**. Users want to be able to connect securely "
+"from a home or office to a private network in the cloud. Typically, the IP "
+"address of the connecting client is dynamic and cannot be preconfigured on "
+"the VPN server."
+msgstr "**公路勇士/远程访问**. .用户希望可以安全地从家里或者办公室连接到云里的一个 私有网络。特别是连接的客户端的IP地址是动态决定的，不能预先配置到VPN 服务器上。"
+
+# dd37e3114c294b4faa1de54929a552f1
+#: ../../managing_networks.rst:3726
+msgid ""
+"**Site to Site**. In this scenario, two private subnets are connected over "
+"the public Internet with a secure VPN tunnel. The cloud user’s subnet (for "
+"example, an office network) is connected through a gateway to the network in"
+" the cloud. The address of the user’s gateway must be preconfigured on the "
+"VPN server in the cloud. Note that although L2TP-over-IPsec can be used to "
+"set up Site-to-Site VPNs, this is not the primary intent of this feature. "
+"For more information, see `Section 15.25.5, “Setting Up a Site-to-Site VPN "
+"Connection” <#site-to-site-vpn>`__"
+msgstr "**站点到站点**.在这个场景中，两个私有子网通过公共互联网上的一个安全VPN隧道互联。云用户的子网 (例如：办公室的网络)通过一个网关连接到云中的网络。用户的网关地址必须被预先配置到云的VPN服务器上。注意：通过 L2TP-over-IPsec 协议可以用来配置站点到站点的 VPN，虽然这不是该特性的最初目标。欲了解更多信息，请参阅 `章节 15.25.5, “设置站点到站点VPN连接” <#site-to-site-vpn>`__"
+
+# bfa322b2a64046429d89460b40d144f0
+#: ../../managing_networks.rst:3737
+msgid "Configuring Remote Access VPN"
+msgstr "配置远程访问VPN"
+
+# 097a6cf2913b4beba6be5431a86de870
+#: ../../managing_networks.rst:3739
+msgid "To set up VPN for the cloud:"
+msgstr "为云设置VPN："
+
+# 1fa16e80d9f644edabec5370acdb32bf
+#: ../../managing_networks.rst:3747
+msgid "In the left navigation, click Global Settings."
+msgstr "在左侧导航栏，点击 全局设置"
+
+# aa577a63d68e4aec895fe83165f3f782
+#: ../../managing_networks.rst:3751
+msgid "Set the following global configuration parameters."
+msgstr "设置以下全局配置参数。"
+
+# 0ea3bea3ca8e4aaaaab96eb7cc118fa0
+#: ../../managing_networks.rst:3755
+msgid ""
+"remote.access.vpn.client.ip.range – The range of IP addresses to be "
+"allocated to remote access VPN clients. The first IP in the range is used by"
+" the VPN server."
+msgstr "remote.access.vpn.client.ip.range – 分配给远程访问VPN客户端的IP地址范围。第一个IP被VPN服务器使用。"
+
+# 9d973a38aa614f53b869f0bdc327f31a
+#: ../../managing_networks.rst:3761
+msgid "remote.access.vpn.psk.length – Length of the IPSec key."
+msgstr "remote.access.vpn.psk.length – IPsec密钥长度。"
+
+# fb498ce174e14f6a9bd79342530814a8
+#: ../../managing_networks.rst:3765
+msgid ""
+"remote.access.vpn.user.limit – Maximum number of VPN users per account."
+msgstr "remote.access.vpn.user.limit – 单个账户的最大VPN用户数量。"
+
+# 4dce5f8323054cd7ab088e614da1a9e4
+#: ../../managing_networks.rst:3768
+msgid "To enable VPN for a particular network:"
+msgstr "为特定的网络启用VPN："
+
+# b675d72fb2994edf9ffb66e7d4a0d9e2
+# b8343075444146c2951287194c670d61
+#: ../../managing_networks.rst:3772 ../../managing_networks.rst:3809
+msgid "Log in as a user or administrator to the CloudStack UI."
+msgstr "使用用户或管理员身份登录到CloudStack用户界面。"
+
+# 7bfc3800f4454b6d91c8b45e69042d61
+# 8ea70ebbf5844760b522f1a0f75bbb27
+#: ../../managing_networks.rst:3776 ../../managing_networks.rst:3813
+msgid "In the left navigation, click Network."
+msgstr "在左边导航栏，点击网络。"
+
+# 0daa9926aa704bf5862add2651c6dcb6
+#: ../../managing_networks.rst:3780
+msgid "Click the name of the network you want to work with."
+msgstr "选择你要操作的网络名称"
+
+# 2fa1652bbb944603ad6cbb5d1aad4a5a
+#: ../../managing_networks.rst:3788
+msgid "Click one of the displayed IP address names."
+msgstr "点击一个显示的IP地址名称。"
+
+# ef6bf9b781754ea18f2335af33284201
+#: ../../managing_networks.rst:3792
+msgid ""
+"Click the Enable VPN button. |AttachDiskButton.png: button to attach a "
+"volume|"
+msgstr "点击启用VPN按钮。 |AttachDiskButton.png: button to attach a volume|"
+
+# 2012a33f002143b893c3f7a989397edc
+#: ../../managing_networks.rst:3795
+msgid "The IPsec key is displayed in a popup window."
+msgstr "IPsec密钥将显示在弹出的窗口中。"
+
+# b28f663cf7724ab9a7f478d438a24394
+#: ../../managing_networks.rst:3798
+msgid "Configuring Remote Access VPN in VPC"
+msgstr "为VPC配置远程访问VPN"
+
+# fa00279794274728b49c98337469cbbf
+#: ../../managing_networks.rst:3800
+msgid ""
+"On enabling Remote Access VPN on a VPC, any VPN client present outside the "
+"VPC can access VMs present in the VPC by using the Remote VPN connection. "
+"The VPN client can be present anywhere except inside the VPC on which the "
+"user enabled the Remote Access VPN service."
+msgstr "在VPC中启用远程访问VPN，任何VPC以外的VPN客户端都可以使用远程VPN连接访问VPC中的VM。VPN客户端可以在除了用户启用了远程访问VPN服务的VPC中的任何位置。"
+
+# 9995de408c534547bca798eacfc6e29d
+#: ../../managing_networks.rst:3805
+msgid "To enable VPN for a VPC:"
+msgstr "为VPC开启VPN："
+
+# a31affe0adac49f09f3748d0f7ae367e
+# 4af68095a91449e3b8bea9b815da9067
+# dad79a3f32dc40a786d554154bd361b9
+# e38d9555c0c8456ca690fd6cf202b112
+# 821e14755e74419ba72d32bd68d96287
+# 882bbeb316964de78877b7cb3cecc9fc
+# 75cc31bf17e2494fb91a744619c66ee4
+# 1c0efba412354370a1b9f46eaaa0ef7a
+# a5edf42ce9ad47e6a2330279b1398ac1
+# cecf708f7c1043c48169ea6b24e59466
+# 1e27b769cc2540c08fe46fa6ab725699
+# 75db22351660479db8734b0ed18fc894
+# 3a8ef410656041498f008fbe30a414db
+# cfadbb7beee440b5a535959fac59ded7
+# 1efbe4d02aef451a9f809b75fd3a01ae
+# 46c68a38ef0d418b88f703c6038fad39
+# 699be4a90f2b41a0b715d02d5e54e4df
+# 83151a4b19cc4e5489e47c5fa744b5c0
+#: ../../managing_networks.rst:3817 ../../managing_networks.rst:4260
+#: ../../managing_networks.rst:4357 ../../managing_networks.rst:4550
+#: ../../managing_networks.rst:4971 ../../managing_networks.rst:5036
+#: ../../managing_networks.rst:5164 ../../managing_networks.rst:5246
+#: ../../managing_networks.rst:5414 ../../managing_networks.rst:5651
+#: ../../managing_networks.rst:5743 ../../managing_networks.rst:5831
+#: ../../managing_networks.rst:5921 ../../managing_networks.rst:6163
+#: ../../managing_networks.rst:6471 ../../managing_networks.rst:6555
+#: ../../managing_networks.rst:6680 ../../managing_networks.rst:6719
+msgid "In the Select view, select VPC."
+msgstr "在选择视图中，选择VPC。"
+
+# 9ae3c14b7e8c402c9c1dce614d4bd2c7
+# e4a77e77230d483db3156f192de9ca5b
+# 8bddf8b867294c708f998bad74efcff6
+# 345034355f8c44c9b7ffc188c0ac9896
+# 568c157061934519a28710ac7dbc349b
+# 47d6e2a72c7f48bcbe8d6ee024c33594
+# 7c289632b014498080a51b30fab9101d
+# f66374dd81f244f6a2f3ed711f4bf948
+# 87c017466f11465ab7cead64d05b5eaf
+# 0c79b640f1da4393b59a0e998560988c
+# d19f27ee89f34a4fb8df870e04257e7f
+# ab679cc378034d79ab6985db72b19b9c
+# 6f1cdf89d13f42f0ab2b5bedcbbd73e6
+# 6005fd24e0d54155a3241c01fe6124e9
+#: ../../managing_networks.rst:3819 ../../managing_networks.rst:4262
+#: ../../managing_networks.rst:4552 ../../managing_networks.rst:5166
+#: ../../managing_networks.rst:5248 ../../managing_networks.rst:5416
+#: ../../managing_networks.rst:5653 ../../managing_networks.rst:5745
+#: ../../managing_networks.rst:5833 ../../managing_networks.rst:5923
+#: ../../managing_networks.rst:6165 ../../managing_networks.rst:6473
+#: ../../managing_networks.rst:6557 ../../managing_networks.rst:6721
+msgid ""
+"All the VPCs that you have created for the account is listed in the page."
+msgstr "此帐号创建的所有VPC将显示在页面中。"
+
+# ca19426a021e4211a1acd3f6a8b16989
+# c182ce3a373542a99217ced2df09ce62
+# 99819c70e71b4f8189fbee678c73a3a5
+#: ../../managing_networks.rst:3824 ../../managing_networks.rst:5171
+#: ../../managing_networks.rst:5253
+msgid "Click the Configure button of the VPC."
+msgstr "点击VPC的配置按钮。"
+
+# 4d3781d769c545d99be97f10a202686a
+# dee16ec55fcf4247845bc5507b0cfd97
+# c307d801b0864d9f96fdcef8b387ce9d
+# bd8619c3aaa0447486c78131f8eb7b14
+# 47f4d3cd60294575ac304752364e0016
+# 96a7d144a4a9461fb5b97370f7f33d41
+# af5676d8c747473d89e78cc8e3892a25
+#: ../../managing_networks.rst:3826 ../../managing_networks.rst:4273
+#: ../../managing_networks.rst:4373 ../../managing_networks.rst:4567
+#: ../../managing_networks.rst:5173 ../../managing_networks.rst:6176
+#: ../../managing_networks.rst:6568
+msgid "For each tier, the following options are displayed:"
+msgstr "对于每一个层，会显示以下选项。"
+
+# e977c7944d7441429e362266f89939b8
+# 5dc3472c6728454999ad5fb3af4f85f7
+# dd1ac38a74e64a408aebd85987d4ca2a
+# 1e64906e22d740f2bbe78adf991135f3
+# 3ab121c1f35c4617914f68af0a25364d
+# 3433f4dcaec546dcae9e778199695765
+# 5747e1b492c54471a0b41977a208232c
+# 1ecff74d45e644809e0f02cb05421be1
+# cbae3a5d141c4cdc83fd6f278d79e79e
+# 41d220172f7c4c1d8553baebb87b3616
+# 7f81c86a21a94b8d8cb340708599235d
+#: ../../managing_networks.rst:3830 ../../managing_networks.rst:4277
+#: ../../managing_networks.rst:4377 ../../managing_networks.rst:4571
+#: ../../managing_networks.rst:5177 ../../managing_networks.rst:5435
+#: ../../managing_networks.rst:5760 ../../managing_networks.rst:5847
+#: ../../managing_networks.rst:5938 ../../managing_networks.rst:6180
+#: ../../managing_networks.rst:6572
+msgid "Internal LB"
+msgstr "内部LB"
+
+# 738682e112cb4305a6f74807ed9a15bb
+# 6e5c7436086b4fdda00214facb796e94
+# 17f370caa5ba4969934de8611356c9e5
+# 64c5287f475642419374f2b15f026bab
+# 7e24a426f15048fba793a522a40ef689
+# 2470296892374cf8b1dbbba087f9cc1e
+# b914d7f7af2d4d5c8f763562a1d9e71b
+# 53a27d12607c447980cd9361d9081a86
+# 95adec1d399d4946bedb3a89ca40a486
+# 33c3c72610f7495a8f48211a7823fd4e
+# 72f5b91956d449d4a4a1be58dd85ab17
+#: ../../managing_networks.rst:3834 ../../managing_networks.rst:4281
+#: ../../managing_networks.rst:4381 ../../managing_networks.rst:4575
+#: ../../managing_networks.rst:5181 ../../managing_networks.rst:5439
+#: ../../managing_networks.rst:5764 ../../managing_networks.rst:5851
+#: ../../managing_networks.rst:5942 ../../managing_networks.rst:6184
+#: ../../managing_networks.rst:6576
+msgid "Public LB IP"
+msgstr "公共LB IP"
+
+# 0cb050feaaeb474c926023e60f855b32
+# 11861e54e8724e2fadaca4c4ef5e568e
+# c8e370f0dc4643d293e44f555b923199
+# 0c77f763f1e040f7b80e04b3a37bce24
+# 39a2f9b8856943628ae5927eb7f71c92
+# 2c350c6efc7543d69506721e795eb85f
+# b5d631e4a2024d1fbd4f10d4d0d9064a
+# 952eed7b8185432cae49594fa2f3ec18
+# 7af76e26ead045619c8139e1fead812a
+# b8b0020c6a964034b84a1515f8eeda8b
+# c356254659034481a1dc96d9387f6b9f
+#: ../../managing_networks.rst:3842 ../../managing_networks.rst:4289
+#: ../../managing_networks.rst:4389 ../../managing_networks.rst:4583
+#: ../../managing_networks.rst:5189 ../../managing_networks.rst:5447
+#: ../../managing_networks.rst:5772 ../../managing_networks.rst:5859
+#: ../../managing_networks.rst:5950 ../../managing_networks.rst:6192
+#: ../../managing_networks.rst:6584
+msgid "Virtual Machines"
+msgstr "虚拟机"
+
+# b89c9f01ccd944b297fff10534973ddc
+# eef1542933fe447b8262890522771d50
+# 5178f0cb1f7c46709c6549e58c7a067a
+# d150a889b3614d81811a9cdc68c5fa66
+# 7ed422ae787a4447960d1e0207cc28dc
+# 5d542e45915b4557b132ba854d60edb6
+# 0fa2b79d145143d880bfdf98bc57f29a
+# b47fda6dfe744ba3853d7a7b7c24b1f6
+# b632ee0308cf4b44b4e44d46a51496e5
+# 3c0bd1aea7ad4d68964f1d4edb118cdd
+# 6a198f55d0a846f3b709af607f86e43e
+#: ../../managing_networks.rst:3848 ../../managing_networks.rst:4295
+#: ../../managing_networks.rst:4395 ../../managing_networks.rst:4589
+#: ../../managing_networks.rst:5195 ../../managing_networks.rst:5453
+#: ../../managing_networks.rst:5778 ../../managing_networks.rst:5865
+#: ../../managing_networks.rst:5956 ../../managing_networks.rst:6198
+#: ../../managing_networks.rst:6590
+msgid "The following router information is displayed:"
+msgstr "显示以下路由器信息："
+
+# a1dbb584fd8b4d4397d374a689f02aa9
+# 0eb728e1fe3c4bf285cd79b34b06d181
+# 8faa54108faa476da673bfb6058b1cc7
+# cb8741bacf1843f0a927b32272bf09cd
+# bae030b0fb4d4ef983ceb14b13495258
+# f3c190c39252412bb8581e07bd6b83aa
+# 2c7b1b5142d1498682193b8ddf312be9
+# d3c687f587e246afae5580f92212b8bf
+# e08e124fc28f4b9387b1f51cdaac7514
+# b64c4d99a2664addbd98a4853da33ffb
+# d46a9ac6036249879d896e722844e95c
+#: ../../managing_networks.rst:3852 ../../managing_networks.rst:4299
+#: ../../managing_networks.rst:4399 ../../managing_networks.rst:4593
+#: ../../managing_networks.rst:5199 ../../managing_networks.rst:5457
+#: ../../managing_networks.rst:5782 ../../managing_networks.rst:5869
+#: ../../managing_networks.rst:5960 ../../managing_networks.rst:6202
+#: ../../managing_networks.rst:6594
+msgid "Private Gateways"
+msgstr "专用网关"
+
+# 37d72d2f76774b20a776f60ddc5797d4
+# ea8ad120e00141f783ec53364a03fa37
+# 53b019dc3a224529b82a9a7f37642b0a
+# 174ffd68b1d44ec799357f81eb5c2d25
+# 17bfe0fddda04252a302177c5719e3fe
+# 20a272af5b6d4dee9fc4907b9dd12560
+# 8583a6af04b644e191ff21fcff4f7b8b
+# 4823862431b0480cb61fd62d4b11e87f
+# 8664c330cd684d8595f27db6751ce17c
+# 0cea333fbc5849929e6c0690f226d6a2
+# 9cbdcd3b4ebc4b609e5ba6c56f2d7d5d
+#: ../../managing_networks.rst:3856 ../../managing_networks.rst:4303
+#: ../../managing_networks.rst:4403 ../../managing_networks.rst:4597
+#: ../../managing_networks.rst:5203 ../../managing_networks.rst:5461
+#: ../../managing_networks.rst:5786 ../../managing_networks.rst:5873
+#: ../../managing_networks.rst:5964 ../../managing_networks.rst:6206
+#: ../../managing_networks.rst:6598
+msgid "Public IP Addresses"
+msgstr "公共IP地址"
+
+# b7bc8b8352a74af6b38cc39b1d686153
+# c1878fc16d7b47249752134a9b157b07
+# 8ac22811a0f1450f949764f8ecee4697
+# bde7d8d93cec4b4495105ef97d1f8a35
+# 36b78ef29e834917899c5a7a6ad5ddf4
+# 17f83c3836c64c299d8be56f678dc890
+# bef1f58c45f148ad92c455f3e9d92768
+# d944807c216342baab75254197b930e2
+# 079e9d4527484c839f6f49651f0d6265
+# a9b19cd8a8c44794879d831c50f88b49
+# c9c52762ec514a90a7c5522451754157
+#: ../../managing_networks.rst:3860 ../../managing_networks.rst:4307
+#: ../../managing_networks.rst:4407 ../../managing_networks.rst:4601
+#: ../../managing_networks.rst:5207 ../../managing_networks.rst:5465
+#: ../../managing_networks.rst:5790 ../../managing_networks.rst:5877
+#: ../../managing_networks.rst:5968 ../../managing_networks.rst:6210
+#: ../../managing_networks.rst:6602
+msgid "Site-to-Site VPNs"
+msgstr "站点到站点 VPN"
+
+# 963900352361453a82243e6d229692eb
+# 5e5ead7fdf824603be436cd39c0bd66a
+# 8dd99ffcfe074e1da4fd7aa2c3c78d32
+# 50e7c6af50d847eaa6334a0ece6cd748
+# 00ffbdac5a974718961391e109c231af
+# 56d7689551ad4cce804707382b489ce7
+# da4f7bdfc20746f6a1c7926fada1bf4d
+# 29a0461bac2a4799bcec9c2ab4af689a
+# 1d744b4deebf4f1da4c6a9e318786816
+# de2d02e42e094632be603e8156bdd703
+# 248e40d2acaf4b1a90d4ee955fea9370
+#: ../../managing_networks.rst:3864 ../../managing_networks.rst:4311
+#: ../../managing_networks.rst:4411 ../../managing_networks.rst:4605
+#: ../../managing_networks.rst:5211 ../../managing_networks.rst:5469
+#: ../../managing_networks.rst:5794 ../../managing_networks.rst:5881
+#: ../../managing_networks.rst:5972 ../../managing_networks.rst:6214
+#: ../../managing_networks.rst:6606
+msgid "Network ACL Lists"
+msgstr "网络 ACL列表"
+
+# f9af791a07354f808cdca900691b32b7
+# 83506da7b26b43c6aac49b3833cad15f
+# 8c42254feeda4c91b2c629f4399e43a9
+# 52bed9f766b34abf852c6fa33e2daf5f
+#: ../../managing_networks.rst:3868 ../../managing_networks.rst:5976
+#: ../../managing_networks.rst:6218 ../../managing_networks.rst:6610
+msgid "In the Router node, select Public IP Addresses."
+msgstr "在路由器节点中，选择公共IP地址。"
+
+# 145b00e12ee347eb8f5d58bf5d53ed27
+# 4c516df3427c4efe893ef5f2d57e86f4
+# bfeeb4dfe5484e2bbeb371cdef909b3a
+# 64a914a25f0945e1b1477c54b9ddc3b1
+# f6d1237ad0fc42f687f50159ffc308eb
+#: ../../managing_networks.rst:3870 ../../managing_networks.rst:5887
+#: ../../managing_networks.rst:5978 ../../managing_networks.rst:6220
+#: ../../managing_networks.rst:6612
+msgid "The IP Addresses page is displayed."
+msgstr "系统显示IP地址页面。"
+
+# 763f43a3ab6e450284bf8a7e1565147e
+#: ../../managing_networks.rst:3874
+msgid "Click Source NAT IP address."
+msgstr "点击源NAT IP地址。"
+
+# 3377f8365d824b5cb4828ba4192c7df8
+#: ../../managing_networks.rst:3878
+msgid "Click the Enable VPN button. |vpn-icon.png: button to enable VPN|"
+msgstr "点击启用VPN按钮。 |vpn-icon.png: button to enable VPN|"
+
+# e806264cf83c4fc9bdb76a8963ee8e41
+#: ../../managing_networks.rst:3880
+msgid "Click OK to confirm. The IPsec key is displayed in a pop-up window."
+msgstr "点击OK确认。IPsec密钥将显示在弹出的窗口中。"
+
+# 941f5a62ecb044e1ae914539a331edf8
+#: ../../managing_networks.rst:3882
+msgid "Now, you need to add the VPN users."
+msgstr "现在，需要添加VPN用户。"
+
+# ef3bbf0199894b05a9e58396bc91163e
+#: ../../managing_networks.rst:3886
+msgid "Click the Source NAT IP."
+msgstr "点击源NAT IP。"
+
+# 40a450792e5c4aa0b261221e534b235e
+#: ../../managing_networks.rst:3890
+msgid "Select the VPN tab."
+msgstr "选择VPN选项卡。"
+
+# da11af4bc3934580904b25becbbe6000
+#: ../../managing_networks.rst:3894
+msgid ""
+"Add the username and the corresponding password of the user you wanted to "
+"add."
+msgstr "为你要创建的用户添加用户名和对应的密码。"
+
+# dc788926df844c83bc63fd1ed04b41b5
+#: ../../managing_networks.rst:3903
+msgid "Repeat the same steps to add the VPN users."
+msgstr "重复相同的步骤添加VPN用户。"
+
+# 9ee121c5c0434e4cbc3b97ae635890a9
+#: ../../managing_networks.rst:3906
+msgid "Using Remote Access VPN with Windows"
+msgstr "在Windows系统中使用远程访问VPN"
+
+# b3edb2c9bcc040aea7a114ca31d0f7d9
+#: ../../managing_networks.rst:3908
+msgid ""
+"The procedure to use VPN varies by Windows version. Generally, the user must"
+" edit the VPN properties and make sure that the default route is not the "
+"VPN. The following steps are for Windows L2TP clients on Windows Vista. The "
+"commands should be similar for other Windows versions."
+msgstr "程序使用不同Windows版本的VPN。通常用户必须编辑VPN属性并确保不使用VPN的默认路由。以下步骤使用基于Windows Vista的Windows L2TP客户端。命令应该类似于其他版本的Windows。"
+
+# 6ffeddfe41f049ca9722b714502eabfb
+#: ../../managing_networks.rst:3915
+msgid ""
+"Log in to the CloudStack UI and click on the source NAT IP for the account. "
+"The VPN tab should display the IPsec preshared key. Make a note of this and "
+"the source NAT IP. The UI also lists one or more users and their passwords. "
+"Choose one of these users, or, if none exists, add a user and password."
+msgstr "登录到CloudStack用户界面并点击账户下的源NAT IP。VPN选项卡应该会显示IPsec预共享密钥。记录该密钥和源NAT IP。用户界面同样也列出了一个多或多个用户他们的密码。选择一个用户，或者如果不存在任何用户，则创建一个用户。"
+
+# 8ca0fcc6fcfd40f28f0c675345fb5f4d
+#: ../../managing_networks.rst:3923
+msgid ""
+"On the Windows box, go to Control Panel, then select Network and Sharing "
+"center. Click Setup a connection or network."
+msgstr "在Windows中，进入控制面板，然后选择网络和共享中心，点击设置一个网络连接。"
+
+# e26b9786a5c64704989e389fb2bbce0d
+#: ../../managing_networks.rst:3928
+msgid "In the next dialog, select No, create a new connection."
+msgstr "在下一个对话框中，选择否，创建一个新的连接。"
+
+# 1c1b2aafb3674ec18a5da699bf60337f
+#: ../../managing_networks.rst:3932
+msgid "In the next dialog, select Use my Internet Connection (VPN)."
+msgstr "在下一个对话框中，选择使用我的Internet连接(VPN)."
+
+# 98dfa80786574e6ea33f5b0c24fa4700
+#: ../../managing_networks.rst:3936
+msgid ""
+"In the next dialog, enter the source NAT IP from step `1 <#source-nat>`__ "
+"and give the connection a name. Check Don't connect now."
+msgstr "在下一个对话框中，输入此步骤 `1 <#source-nat>`__ 中的源NAT IP地址并填写连接名称。勾选现在不连接。"
+
+# 533985edf60848b2a4ebf75ba177c150
+#: ../../managing_networks.rst:3942
+msgid ""
+"In the next dialog, enter the user name and password selected in step `1 "
+"<#source-nat>`__."
+msgstr "在下一个对话框中，输入此步骤 `1 <#source-nat>`__中的用户名和密码。"
+
+# 2207831550714a73a1a41e5283a49cd9
+#: ../../managing_networks.rst:3951
+msgid ""
+"Go back to the Control Panel and click Network Connections to see the new "
+"connection. The connection is not active yet."
+msgstr "返回控制面板并点击网络连接查看这个新的连接。但当前连接并不是活动状态。"
+
+# 1e1b6b1d256942c2a129691e49daceaf
+#: ../../managing_networks.rst:3956
+msgid ""
+"Right-click the new connection and select Properties. In the Properties "
+"dialog, select the Networking tab."
+msgstr "在新创建的连接上点击右键并选择属性。在属性对话框中，选择网络选项卡。"
+
+# e4ea1219d3634755a9395cae6ab51e7f
+#: ../../managing_networks.rst:3961
+msgid ""
+"In Type of VPN, choose L2TP IPsec VPN, then click IPsec settings. Select Use"
+" preshared key. Enter the preshared key from step `1 <#source-nat>`__."
+msgstr "在VPN类型中，选择L2TP IPsec VPN,然后点击IPsec设置，选择用户预共享密钥。并输入此步骤`1 <#source-nat>`__中提供的密钥。"
+
+# 67167335a22243b7988e640a0022857c
+#: ../../managing_networks.rst:3967
+msgid ""
+"The connection is ready for activation. Go back to Control Panel -> Network "
+"Connections and double-click the created connection."
+msgstr "该连接已经准备好被激活。返回到控制面板 -> 网络连接，双击创建连接。"
+
+# 109e34abfe6f4522b5c8bc8bc60f2fe0
+#: ../../managing_networks.rst:3972
+msgid "Enter the user name and password from step `1 <#source-nat>`__."
+msgstr "输入此步骤 `1 <#source-nat>`__ 中提供的用户名和密码。"
+
+# 8c9ad7097eda4b19bb45090e25249724
+#: ../../managing_networks.rst:3975
+msgid "Using Remote Access VPN with Mac OS X"
+msgstr "在Mac OS X 中使用远程访问VPN"
+
+# 5f27e95b14c9475a8f7c56618a1cb515
+#: ../../managing_networks.rst:3977
+msgid ""
+"First, be sure you've configured the VPN settings in your CloudStack "
+"install. This section is only concerned with connecting via Mac OS X to your"
+" VPN."
+msgstr "首先，确保在你的CloudStack中已经设置好VPN。本章节仅涉及通过Mac OS X 连接至VPN。"
+
+# dc2c20b5eb574ed2adada77dbf270a42
+#: ../../managing_networks.rst:3981
+msgid ""
+"Note, these instructions were written on Mac OS X 10.7.5. They may differ "
+"slightly in older or newer releases of Mac OS X."
+msgstr "请注意，此指南只基于Mac OS X 10.7.5 。在旧版或新版本的Mac OS X中可能会略有不同。"
+
+# 9c82432ffa134c1ca32ac34f08988c6d
+#: ../../managing_networks.rst:3986
+msgid "On your Mac, open System Preferences and click Network."
+msgstr "在Mac中，打开系统偏好设置然后点击网络。"
+
+# 9d97977e9c46436ab9fe30c172722d6b
+#: ../../managing_networks.rst:3990
+msgid "Make sure Send all traffic over VPN connection is not checked."
+msgstr "确保Send all traffic over VPN connection没有被选定。"
+
+# 63ac91c8dc0e497b80a34dfcae925d4b
+#: ../../managing_networks.rst:3994
+msgid ""
+"If your preferences are locked, you'll need to click the lock in the bottom "
+"left-hand corner to make any changes and provide your administrator "
+"credentials."
+msgstr "如果你的首选项框被锁住，你如果要做些改动需要点击底部左侧的锁按钮，并提供管理员认证。"
+
+# 3382a964d3e24d78ac26db4b8bda5128
+#: ../../managing_networks.rst:4000
+msgid ""
+"You will need to create a new network entry. Click the plus icon on the "
+"bottom left-hand side and you'll see a dialog that says \"Select the "
+"interface and enter a name for the new service.\" Select VPN from the "
+"Interface drop-down menu, and \"L2TP over IPSec\" for the VPN Type. Enter "
+"whatever you like within the \"Service Name\" field."
+msgstr "您将需要创建一个新的网络入口。点击底部左侧的加号图标，你会看到一个对话框，写着“选择接口并输入新服务的名称”。在接口下拉菜单中选择VPN，VPN类型为“基于IPSec的L2TP”。在“服务名称”中输入任何你喜欢的字段。"
+
+# f99d122e9241423fbdcf6aa83fa0b08f
+#: ../../managing_networks.rst:4008
+msgid ""
+"You'll now have a new network interface with the name of whatever you put in"
+" the \"Service Name\" field. For the purposes of this example, we'll assume "
+"you've named it \"CloudStack.\" Click on that interface and provide the IP "
+"address of the interface for your VPN under the Server Address field, and "
+"the user name for your VPN under Account Name."
+msgstr "现在你需要在\"Service Name\" 中填入新的网络接口的名称。对于这个例子，我们假设你已经把它命名为“CloudStack”。点击该接口，并在服务器地址字段中填入提供的VPN IP地址，并在账户名称中填入您的VPN用户名。"
+
+# 90453b8ed4bb48a18163cc20cb129995
+#: ../../managing_networks.rst:4017
+msgid ""
+"Click Authentication Settings, and add the user's password under User "
+"Authentication and enter the pre-shared IPSec key in the Shared Secret field"
+" under Machine Authentication. Click OK."
+msgstr "点击身份验证设置，在机器验证中，用户身份验证下输入用户名和密码，在共享密钥下输入预共享IPsec密钥。点击OK。"
+
+# 92408c82c4b04948a05c719bd048fad0
+#: ../../managing_networks.rst:4023
+msgid ""
+"You may also want to click the \"Show VPN status in menu bar\" but that's "
+"entirely optional."
+msgstr "你也可以点击\"在菜单栏中查看VPN状态\",这完全是可选的操作。"
+
+# 8190135a88884eb788e9ce54c71ca84f
+#: ../../managing_networks.rst:4028
+msgid "Now click \"Connect\" and you will be connected to the CloudStack VPN."
+msgstr "现在点击\"连接\" 你将会连接到CloudStack VPN。"
+
+# ac02eeb882404522aacc0cc8293ad641
+#: ../../managing_networks.rst:4031
+msgid "Setting Up a Site-to-Site VPN Connection"
+msgstr "配置站点到站点的VPN连接"
+
+# e204e99f433b4e51a129efbe663d70ef
+#: ../../managing_networks.rst:4033
+msgid ""
+"A Site-to-Site VPN connection helps you establish a secure connection from "
+"an enterprise datacenter to the cloud infrastructure. This allows users to "
+"access the guest VMs by establishing a VPN connection to the virtual router "
+"of the account from a device in the datacenter of the enterprise. You can "
+"also establish a secure connection between two VPC setups or high "
+"availability zones in your environment. Having this facility eliminates the "
+"need to establish VPN connections to individual VMs."
+msgstr "一个站点到站点的VPN连接可以帮助你建立从云基础架构到企业内部数据中心的安全连接.这就允许一个账户从企业内部数据中心的设备连接到此账户启用VPN连接的虚拟路由器上, 从而通过VPN连接到该账户的虚拟机.你也可以在两个VPC之间或是高可用区域之间建立VPC以加强安全。这样一来，就不需要在虚拟机之间建立VPN连接的必要了。"
+
+# 8e29e93424a04c189576052f05b8e717
+#: ../../managing_networks.rst:4042
+msgid ""
+"The difference from Remote VPN is that Site-to-site VPNs connects entire "
+"networks to each other, for example, connecting a branch office network to a"
+" company headquarters network. In a site-to-site VPN, hosts do not have VPN "
+"client software; they send and receive normal TCP/IP traffic through a VPN "
+"gateway."
+msgstr "与Remote VPN不同，Site-to-site VPNs是将两个网络相互连接。比如，将一个分支办公室的网络与总公司网络互联，Site-to-site VPN的两个主机不需要VPN客户端软件，它们通过VPN网关收发普通的TCP/IP数据包流量 。"
+
+# 95bbe3e3d5554fb6bc7959c18174607c
+#: ../../managing_networks.rst:4048
+msgid "The supported endpoints on the remote datacenters are:"
+msgstr "目前支持的数据中心的终端设备是:"
+
+# 7e357cb1629f467485ba9145a75a81f7
+#: ../../managing_networks.rst:4052
+msgid "Cisco ISR with IOS 12.4 or later"
+msgstr "Cisco ISR IOS 12.4或更新"
+
+# 854482adf7dd4aa393f38b07756645aa
+#: ../../managing_networks.rst:4056
+msgid "Juniper J-Series routers with JunOS 9.5 or later"
+msgstr "Juniper J-系统 路由器 JunOS 9.5 或更新版本"
+
+# 96648d86950840f89dc81c431d60cfb6
+#: ../../managing_networks.rst:4060
+msgid "CloudStack virtual routers"
+msgstr "CloudStack虚拟路由器。"
+
+# 1a74583da3a44bd39eb253120139a932
+#: ../../managing_networks.rst:4062
+msgid ""
+"In addition to the specific Cisco and Juniper devices listed above, the "
+"expectation is that any Cisco or Juniper device running on the supported "
+"operating systems are able to establish VPN connections."
+msgstr "除了上述指定的Cisco和Juniper设备, 所期望的是任何Cisco或Juniper的设备在支持的操作系统上都可以建立VPN连接."
+
+# 64b2db355ac04f0f9c59eae16613e881
+#: ../../managing_networks.rst:4064
+msgid "To set up a Site-to-Site VPN connection, perform the following:"
+msgstr "为了建立站点到站点的VPN连接, 需要执行以下步骤:"
+
+# 796a6d7dfb6d46498818110494844639
+#: ../../managing_networks.rst:4068
+msgid "Create a Virtual Private Cloud (VPC)."
+msgstr "创建一个虚拟私有云(VPC)."
+
+# 8792529d67f442debcc4278090beb143
+#: ../../managing_networks.rst:4070
+msgid ""
+"See `Section 15.27, “Configuring a Virtual Private Cloud” <#configure-"
+"vpc>`__."
+msgstr "更多信息，参看 `章节 15.27, “Configuring a Virtual Private Cloud” <#configure-vpc>`__."
+
+# 2cde96423eaa4b00a89bc8638be81197
+#: ../../managing_networks.rst:4075
+msgid "Create a VPN Customer Gateway."
+msgstr "创建一个VPN客户网关."
+
+# 24923d7a1f5b4c968069162a997e27e8
+#: ../../managing_networks.rst:4079
+msgid "Create a VPN gateway for the VPC that you created."
+msgstr "为你创建的VPC设定一个VPN网关."
+
+# de7773aef60648c395206d22ebf8bb2b
+#: ../../managing_networks.rst:4083
+msgid ""
+"Create VPN connection from the VPC VPN gateway to the customer VPN gateway."
+msgstr "从VPC的VPN网关到客户的VPN网关建立VPN连接."
+
+# 44b042e04c484e1aa9425682b124b081
+#: ../../managing_networks.rst:4087
+msgid "Creating and Updating a VPN Customer Gateway"
+msgstr "创建和更新一个VPN客户网关."
+
+# c2ffba4bbe2d413aab0af270e8b2195f
+#: ../../managing_networks.rst:4089
+msgid ""
+"A VPN customer gateway can be connected to only one VPN gateway at a time."
+msgstr "一个VPN客户网关在同一时间只能连接一个VPN网关。"
+
+# 7b0767f2578b495595801fe8c497c3cd
+#: ../../managing_networks.rst:4091
+msgid "To add a VPN Customer Gateway:"
+msgstr "添加 VPN 客户网关"
+
+# 78b54d35bae1432b9360ca8210ec82c5
+# d664ef6b19954f3381587a7ed6fc32de
+#: ../../managing_networks.rst:4103 ../../managing_networks.rst:4227
+msgid "In the Select view, select VPN Customer Gateway."
+msgstr "在选择视图里，选择VPN客户网关。"
+
+# a5c0098ccc8d4b1ca1ae5d86b3d43998
+#: ../../managing_networks.rst:4107
+msgid "Click Add VPN Customer Gateway."
+msgstr "点击添加 VPN 客户网关。"
+
+# e15f9c41a48247cfb47d45e73ea464a0
+#: ../../managing_networks.rst:4109
+msgid "|addvpncustomergateway.png: adding a customer gateway.|"
+msgstr "|addvpncustomergateway.png: adding a customer gateway.|"
+
+# 2a792a8dedb2441a823f19c7d482ecf6
+#: ../../managing_networks.rst:4115
+msgid "**Name**: A unique name for the VPN customer gateway you create."
+msgstr "**名称**: 你添加的VPN客户网关的一个唯一的名称。"
+
+# fcab4cadde164668976324bf647c7b59
+#: ../../managing_networks.rst:4119
+msgid "**Gateway**: The IP address for the remote gateway."
+msgstr "**IP地址**: 远端网关的IP地址。"
+
+# d1b2fa29c7dd4b39a5887883d6571ed1
+#: ../../managing_networks.rst:4123
+msgid ""
+"**CIDR list**: The guest CIDR list of the remote subnets. Enter a CIDR or a "
+"comma-separated list of CIDRs. Ensure that a guest CIDR list is not "
+"overlapped with the VPC’s CIDR, or another guest CIDR. The CIDR must be "
+"RFC1918-compliant."
+msgstr "**CIDR列表**: 远端客户子网的CIDR。输入一个CIDR或是以逗号分隔的多个CIDR。在确认客户的CIDR和VPC的CIDR或是另一个客户的CIDR不重叠冲突。CIDR的格式必须符合 RFC1918标准。"
+
+# 25ad295a35ca425cb4bb391680aad6a3
+#: ../../managing_networks.rst:4130
+msgid ""
+"**IPsec Preshared Key**: Preshared keying is a method where the endpoints of"
+" the VPN share a secret key. This key value is used to authenticate the "
+"customer gateway and the VPC VPN gateway to each other."
+msgstr "**IPsec预共享密钥**: 预共享密钥在两个端点之间共享同一个密钥。这个密钥用来在客户网关和VPN的VPN网关之间相互认证。"
+
+# 60c393822e29418283ca3ba6907b44c3
+#: ../../managing_networks.rst:4135
+msgid ""
+"The IKE peers (VPN end points) authenticate each other by computing and "
+"sending a keyed hash of data that includes the Preshared key. If the "
+"receiving peer is able to create the same hash independently by using its "
+"Preshared key, it knows that both peers must share the same secret, thus "
+"authenticating the customer gateway."
+msgstr "Internet密钥交换协议（IKE）匹配点 ( VPN 端点 ) 通过计算并发送包含预共享密钥的哈希键值来进行相互验证。如果收接点通过自己的预共享密钥算出同一个键值的话，这就说明两个点是用的同一个密钥，相互之间认证通过，形成匹配。"
+
+# cd6c278668824b58a2ffb239404e1012
+#: ../../managing_networks.rst:4139
+msgid ""
+"**IKE Encryption**: The Internet Key Exchange (IKE) policy for phase-1. The "
+"supported encryption algorithms are AES128, AES192, AES256, and 3DES. "
+"Authentication is accomplished through the Preshared Keys."
+msgstr "**IKE 加密**: Internet密钥交换协议(IKE)第一阶段（phase-1）策略。支持的加密算法包括 AES128, AES192, AES256和3DES.。认证通过预共享密钥完成。"
+
+# a3cf2ddfca704791903d9a0ffe07c87c
+#: ../../managing_networks.rst:4144
+msgid ""
+"The phase-1 is the first phase in the IKE process. In this initial "
+"negotiation phase, the two VPN endpoints agree on the methods to be used to "
+"provide security for the underlying IP traffic. The phase-1 authenticates "
+"the two VPN gateways to each other, by confirming that the remote gateway "
+"has a matching Preshared Key."
+msgstr "phase-1是IKE过程的第一阶段。在这个开始的协商阶段，两个VPN端点在将底层IP流量加密安全的方法上取得一致。第一阶段认证通过的条件是：两个VPN网关之间使用的是同一个预定义密钥。"
+
+# dc8ed8cb236e467084228a10a29908e7
+#: ../../managing_networks.rst:4148
+msgid ""
+"**IKE Hash**: The IKE hash for phase-1. The supported hash algorithms are "
+"SHA1 and MD5."
+msgstr "**IKE 哈希**: IKE第一阶段（ phase-1）哈希散列使用的算法。支持SHA1 和 MD5."
+
+# d119a30b80184f6e988be13f0013017b
+#: ../../managing_networks.rst:4153
+msgid ""
+"**IKE DH**: A public-key cryptography protocol which allows two parties to "
+"establish a shared secret over an insecure communications channel. The "
+"1536-bit Diffie-Hellman group is used within IKE to establish session keys. "
+"The supported options are None, Group-5 (1536-bit) and Group-2 (1024-bit)."
+msgstr "**IKE DH（Diffie-Hellman组）**: IKE的DH加密协议，可以在不安全的连接上确保共享KEY的安全。1536位的DH组用在IKE中用来建立会话KEYS。在这里，支持的选项是 None, Group-5 (1536-bit) 和 Group-2 (1024-bit)."
+
+# d00e55d3a58247f4902732e8f104989a
+#: ../../managing_networks.rst:4161
+msgid ""
+"**ESP Encryption**: Encapsulating Security Payload (ESP) algorithm within "
+"phase-2. The supported encryption algorithms are AES128, AES192, AES256, and"
+" 3DES."
+msgstr "**ESP 加密**: 封装安全有效负荷（Encapsulating Security Payload,ESP）算法是发生在第二阶段(phase-2)。其支持的加密算法包括 AES128, AES192, AES256, 和 3DES。"
+
+# e29d497cac194439ba539800b8037ff5
+#: ../../managing_networks.rst:4165
+msgid ""
+"The phase-2 is the second phase in the IKE process. The purpose of IKE "
+"phase-2 is to negotiate IPSec security associations (SA) to set up the IPSec"
+" tunnel. In phase-2, new keying material is extracted from the Diffie-"
+"Hellman key exchange in phase-1, to provide session keys to use in "
+"protecting the VPN data flow."
+msgstr "phase-2是IKE过程的第二阶段，其目标是协助IPSec安全关联 (SA) 以建立IPSec通道。在 phase-2阶段，会利用 phase-1阶段建立好的DH安全协议方法来交换新的密钥。"
+
+# d2b39ecbc1d44c3d9a6d78c78be321e0
+#: ../../managing_networks.rst:4169
+msgid ""
+"**ESP Hash**: Encapsulating Security Payload (ESP) hash for phase-2. "
+"Supported hash algorithms are SHA1 and MD5."
+msgstr "**ESP哈希散列**:phase-2支持的封装安全有效负荷(Encapsulating Security Payload,ESP)哈希算法包括：SHA1 和MD5."
+
+# 47abcc0c6f134e1797ec70ee5355a74c
+#: ../../managing_networks.rst:4174
+msgid ""
+"**Perfect Forward Secrecy**: Perfect Forward Secrecy (or PFS) is the "
+"property that ensures that a session key derived from a set of long-term "
+"public and private keys will not be compromised. This property enforces a "
+"new Diffie-Hellman key exchange. It provides the keying material that has "
+"greater key material life and thereby greater resistance to cryptographic "
+"attacks. The available options are None, Group-5 (1536-bit) and Group-2 "
+"(1024-bit). The security of the key exchanges increase as the DH groups grow"
+" larger, as does the time of the exchanges."
+msgstr "**Perfect forward secrecy(完全正向保密,PFS) **: PFS的性质是确保来自一组的长期的公共密钥和私人密钥之间的会话密钥不会妥协失效。PFS会促使一组新的DH KEY发生交换。这组新KEY具有更长的生命周期因此可以抵制更强大的功击。DH的可用选项是 None, Group-5 (1536-bit)和 Group-2 (1024-bit). 当新KEY交换之后，DH组会变得更大。"
+
+# e1411a88880e44b88adeaffac1d8ebd0
+#: ../../managing_networks.rst:4184
+msgid ""
+"When PFS is turned on, for every negotiation of a new phase-2 SA the two "
+"gateways must generate a new set of phase-1 keys. This adds an extra layer "
+"of protection that PFS adds, which ensures if the phase-2 SA’s have expired,"
+" the keys used for new phase-2 SA’s have not been generated from the current"
+" phase-1 keying material."
+msgstr "当PFS打开后，两个网关之间的新的phase-2 SA协商都会产生新的phase-1的一组KEY，这就会导致增加一个额外的层。这个层的作用是保证即使phase-2 SA失效过期，其KEY也不会由phase-1生成。"
+
+# e61813c0a2954d6283658b02b58d4cb6
+#: ../../managing_networks.rst:4188
+msgid ""
+"**IKE Lifetime (seconds)**: The phase-1 lifetime of the security association"
+" in seconds. Default is 86400 seconds (1 day). Whenever the time expires, a "
+"new phase-1 exchange is performed."
+msgstr "**IKE 存活期(秒)**: SA的phase-1的存活期。默认是86400 秒 (1 天).当这个时间过了之后，会发生一次新的 phase-1 KEY交换。"
+
+# cdae24a26b454b838fa3673a49c43446
+#: ../../managing_networks.rst:4194
+msgid ""
+"**ESP Lifetime (seconds)**: The phase-2 lifetime of the security association"
+" in seconds. Default is 3600 seconds (1 hour). Whenever the value is "
+"exceeded, a re-key is initiated to provide a new IPsec encryption and "
+"authentication session keys."
+msgstr "**ESP存活期 (秒)**:SA的 phase-2存活期。默认为 3600 秒(1 小时). 当过了这个时间之后，会有一个新的KEY初始化，用来加密和认证 IPsec的会话KEY。"
+
+# 99c4be56c93142898b61b090661e5295
+#: ../../managing_networks.rst:4201
+msgid ""
+"**Dead Peer Detection**: A method to detect an unavailable Internet Key "
+"Exchange (IKE) peer. Select this option if you want the virtual router to "
+"query the liveliness of its IKE peer at regular intervals. It’s recommended "
+"to have the same configuration of DPD on both side of VPN connection."
+msgstr "**死亡匹配点检测**:这是一种检测不可用IKE节点的方法。如果你希望虚拟路由器随时测试IKE节点的存活情况，选择了这个选项。 一般来说，最好在VPN连接的两端都同时配置DPD(Dead Peer Detectio)."
+
+# cbedab3aca3b46d3b729d10282337f33
+#: ../../managing_networks.rst:4212
+msgid "Updating and Removing a VPN Customer Gateway"
+msgstr "更新和删除一个VPN客户网关."
+
+# 3b6106b5e9714642a65edc3d3b5af11f
+#: ../../managing_networks.rst:4214
+msgid ""
+"You can update a customer gateway either with no VPN connection, or related "
+"VPN connection is in error state."
+msgstr "你可以更新一个客户网关：即可以从无到有新建一个VPN，或是将有错误提示的VPN改正。"
+
+# 0959bb19a36c4e70a01a974a38e149dc
+#: ../../managing_networks.rst:4231
+msgid "Select the VPN customer gateway you want to work with."
+msgstr "选择您要操作的客户VPN连接。"
+
+# 32f107b7adf04cf2b7f795ae7aaa81c5
+#: ../../managing_networks.rst:4235
+msgid ""
+"To modify the required parameters, click the Edit VPN Customer Gateway "
+"button |edit.png: button to edit a VPN customer gateway|"
+msgstr "如需要修改一些参数，点击编辑客户VPN网关按钮。|edit.png: button to edit a VPN customer gateway|"
+
+# 37ada8df7369477881326c75d570e61a
+#: ../../managing_networks.rst:4240
+msgid ""
+"To remove the VPN customer gateway, click the Delete VPN Customer Gateway "
+"button |delete.png: button to remove a VPN customer gateway|"
+msgstr "删除一个客户VPN网关，点击删除客户VPN网关按钮。 |delete.png: button to remove a VPN customer gateway|"
+
+# 3236f66e39e94005b7667ae57885d653
+#: ../../managing_networks.rst:4248
+msgid "Creating a VPN gateway for the VPC"
+msgstr "为VPC创建一个VPN网关"
+
+# 511d19b2e3504253b21f8f4fcabd362a
+# e01144a6325b4c608dab9c6379458a12
+# bc8da9bc86e542dda10770fce00c89e1
+# 501e01e53ce94f08a0f3d4fe216da110
+# 703482b61d324ba3890aeb460992e1ce
+# 9c1f460ca2e24825a0292fca00b7d23f
+# d4ac91902c79445aa3e7bbd80a3f6a03
+#: ../../managing_networks.rst:4267 ../../managing_networks.rst:4363
+#: ../../managing_networks.rst:4557 ../../managing_networks.rst:5658
+#: ../../managing_networks.rst:5750 ../../managing_networks.rst:5928
+#: ../../managing_networks.rst:6562
+msgid ""
+"Click the Configure button of the VPC to which you want to deploy the VMs."
+msgstr "点击要部署虚机的VPC的配置按钮。"
+
+# a65c97cf987e47c9860d773977e19aaa
+# 26d378a616bb4724a0345a027037983e
+# 9ec7e2c78f664ddea4b564bb44ba02f8
+# aa36d7fe59be4f04a4fb82dde257bbd7
+# 4a661989a9a741af84d8dbb14a16d6f0
+# 6e876e1c538f4945ab205b8415e88220
+# a461edb130a14c6cb41075603aee7d8f
+# 6a50c314b64e4c8ba8b1469a2e2c50c4
+#: ../../managing_networks.rst:4270 ../../managing_networks.rst:4366
+#: ../../managing_networks.rst:4560 ../../managing_networks.rst:5424
+#: ../../managing_networks.rst:5753 ../../managing_networks.rst:5840
+#: ../../managing_networks.rst:5931 ../../managing_networks.rst:6565
+msgid ""
+"The VPC page is displayed where all the tiers you created are listed in a "
+"diagram."
+msgstr "系统会显示VPC页面，您创建的所有层都列在图中。"
+
+# 0655419f6d7d4c40b18bd684d78fc5c2
+# 1b39c01ef614430598699e611dfc623e
+# 7dd952c2ddc347ef976ff0ac7e66de45
+#: ../../managing_networks.rst:4315 ../../managing_networks.rst:4415
+#: ../../managing_networks.rst:4609
+msgid "Select Site-to-Site VPN."
+msgstr "选择点对点VPN"
+
+# 7b01ec42a0b64f369443a3737b23f0ed
+#: ../../managing_networks.rst:4317
+msgid ""
+"If you are creating the VPN gateway for the first time, selecting Site-to-"
+"Site VPN prompts you to create a VPN gateway."
+msgstr "如果您是第一次创建VPN网关，选择点对点VPN会提示您创建一个VPN网关。"
+
+# 742940cb43e74b209faabb6ea27db456
+#: ../../managing_networks.rst:4322
+msgid "In the confirmation dialog, click Yes to confirm."
+msgstr "在信息确认对话框，点击“是”。"
+
+# 7f7c54fe5bae49bab3b51cf86e863910
+#: ../../managing_networks.rst:4324
+msgid ""
+"Within a few moments, the VPN gateway is created. You will be prompted to "
+"view the details of the VPN gateway you have created. Click Yes to confirm."
+msgstr "过一会儿，VPN网关就创建出来了。系统会提示您查看VPN网关的详细信息，请点击“是”。"
+
+# 63a4578cd1dd4ad98122b9149082a8b3
+#: ../../managing_networks.rst:4328
+msgid "The following details are displayed in the VPN Gateway page:"
+msgstr "VPN网关页面会显示以下详细信息："
+
+# 1da96b1b044e4d78b49dcb8cc4099ba3
+#: ../../managing_networks.rst:4336
+msgid "Account"
+msgstr "帐号"
+
+# 1c7f84073654461dae36083481c5502c
+#: ../../managing_networks.rst:4340
+msgid "Domain"
+msgstr "域名"
+
+# 030c20e667e445a5a3e530f0740204bf
+#: ../../managing_networks.rst:4343
+msgid "Creating a VPN Connection"
+msgstr "新建vpn连接"
+
+# ac44534c69794320b653ebbb19e635f2
+#: ../../managing_networks.rst:4345
+msgid "CloudStack supports creating up to 8 VPN connections."
+msgstr "CloudStack最多支持建立8个VPN连接。"
+
+# f6a9f2333b3b4aaabfdca1da35eaa6de
+#: ../../managing_networks.rst:4359
+msgid "All the VPCs that you create for the account are listed in the page."
+msgstr "页面上列出了该账号下所有的VPC。"
+
+# adfb4ad12aa243d6ad05463c636503a1
+# 327d040bcabf40599dcf368f22a07853
+# e07568be318548718935c6472cbd9bb0
+#: ../../managing_networks.rst:4371 ../../managing_networks.rst:4565
+#: ../../managing_networks.rst:5429
+msgid "Click the Settings icon."
+msgstr "点击设置图标。"
+
+# e03ba2fa9183402c9c8486eb92516980
+# b9a7a824b72047c48214b440c8a54618
+#: ../../managing_networks.rst:4417 ../../managing_networks.rst:4611
+msgid "The Site-to-Site VPN page is displayed."
+msgstr "系统会显示点对点VPN页面。"
+
+# 9389c31ffef740e38608620a80bee1b7
+# 7a249b578800445fbcb0b768547bd1c4
+#: ../../managing_networks.rst:4421 ../../managing_networks.rst:4615
+msgid ""
+"From the Select View drop-down, ensure that VPN Connection is selected."
+msgstr "在选择视图下拉框，请确保选择VPN连接。"
+
+# dce19ba002cf49d8af17ad7a380f2606
+#: ../../managing_networks.rst:4426
+msgid "Click Create VPN Connection."
+msgstr "选择创建vpn连接按钮"
+
+# 13474ca5db5a4cec8688a86f4e74350e
+#: ../../managing_networks.rst:4428
+msgid "The Create VPN Connection dialog is displayed:"
+msgstr "系统会显示创建VPN连接对话框："
+
+# bbc62b37255b4285a412fe8fef5cdaf1
+#: ../../managing_networks.rst:4430
+msgid ""
+"|createvpnconnection.png: creating a VPN connection to the customer "
+"gateway.|"
+msgstr "|createvpnconnection.png: creating a VPN connection to the customer gateway.|"
+
+# 25353dbd7d224969878afd9f2f0a3d79
+#: ../../managing_networks.rst:4435
+msgid "Select the desired customer gateway."
+msgstr "选择想要的用户网关。"
+
+# b8751b7b869e41e89c732ca0a4e1b09b
+#: ../../managing_networks.rst:4439
+msgid ""
+"Select Passive if you want to establish a connection between two VPC virtual"
+" routers."
+msgstr "如果你希望在两个VPC虚拟路由器之间建立连接，选择被动模式。"
+
+# bc97e44ce1cf44878ebb684d36080bb9
+#: ../../managing_networks.rst:4442
+msgid ""
+"If you want to establish a connection between two VPC virtual routers, "
+"select Passive only on one of the VPC virtual routers, which waits for the "
+"other VPC virtual router to initiate the connection. Do not select Passive "
+"on the VPC virtual router that initiates the connection."
+msgstr "如果你希望在两个VPC虚拟路由器之间建立连接，需要等待另一个虚拟路由器来初始化连接，则只有其中一个虚拟器上选择被动模式。在这种情况下，不要在初始化连接的虚拟路由器上选择被动模式。"
+
+# eadc5a4556aa44f28e4863d1c2d4fecc
+#: ../../managing_networks.rst:4452
+msgid "Within a few moments, the VPN Connection is displayed."
+msgstr "过一会儿，系统会显示该VPN连接。"
+
+# 8ed2f646df6a4d75857c6a8fac04e829
+#: ../../managing_networks.rst:4454
+msgid "The following information on the VPN connection is displayed:"
+msgstr "VPN连接信息"
+
+# de7d0faafa2448e08a0d2493699c50c7
+#: ../../managing_networks.rst:4466
+msgid "State"
+msgstr "状态 "
+
+# e3764a89a0ce4201889a0fadffcc09d5
+#: ../../managing_networks.rst:4470
+msgid "IPSec Preshared Key"
+msgstr "IPSec 预共享密钥"
+
+# 8ca0096772074c439e2d9a61b38fd6ef
+#: ../../managing_networks.rst:4474
+msgid "IKE Policy"
+msgstr "IKE策略"
+
+# 7ec1e33e92c64c29a0c177e54bc2cb9c
+#: ../../managing_networks.rst:4478
+msgid "ESP Policy"
+msgstr "ESP策略"
+
+# e8af24af3aa041559e70bbc4f134e2a0
+#: ../../managing_networks.rst:4481
+msgid "Site-to-Site VPN Connection Between VPC Networks"
+msgstr "在VPC网络之间的站点的VPN连接"
+
+# d32d29e70caf4194bc1f7aeb3159a85e
+#: ../../managing_networks.rst:4483
+msgid ""
+"CloudStack provides you with the ability to establish a site-to-site VPN "
+"connection between CloudStack virtual routers. To achieve that, add a "
+"passive mode Site-to-Site VPN. With this functionality, users can deploy "
+"applications in multiple Availability Zones or VPCs, which can communicate "
+"with each other by using a secure Site-to-Site VPN Tunnel."
+msgstr "CloudStack可以在虚拟路由器之间部署站点到站点的VPN连接，这需要添加一个被动模式的站点到站点VPN。有了这个功能之后，用户就可以在多个区域或VPC之间通过安全的VPN通道互联。"
+
+# aca5c3b83f3948419a10f421e9ebb6d3
+#: ../../managing_networks.rst:4489
+msgid "This feature is supported on all the hypervisors."
+msgstr "这个特性支持所有类型的HYPERVISOR."
+
+# be029698755440618c84f5ada6cd0f0d
+#: ../../managing_networks.rst:4493
+msgid "Create two VPCs. For example, VPC A and VPC B."
+msgstr "创建两个VPC。比如，VPC A和VPC B。"
+
+# d849133b3805422b85e8fb4b5c1e843f
+#: ../../managing_networks.rst:4495
+msgid ""
+"For more information, see `Section 15.27, “Configuring a Virtual Private "
+"Cloud” <#configure-vpc>`__."
+msgstr "更多信息，参看 `章节 15.27, “配置虚拟专用云” <#configure-vpc>`__."
+
+# baae8ca5cf4c4e53a308274c699e84e4
+#: ../../managing_networks.rst:4500
+msgid "Create VPN gateways on both the VPCs you created."
+msgstr "在创建的VPC两边都添加VPN网关。"
+
+# cf3881f3f2af4d808dd58ae3dd71a648
+#: ../../managing_networks.rst:4502
+msgid ""
+"For more information, see `Section 15.25.5.2, “Creating a VPN gateway for "
+"the VPC” <#create-vpn-gateway-for-vpc>`__."
+msgstr "更多信息，参看 `章节 15.25.5.2, “为VPC创建VPN网关” <#create-vpn-gateway-for-vpc>`__."
+
+# 5f6abf3bf9f4445db1b846b5f06d95b7
+#: ../../managing_networks.rst:4507
+msgid "Create VPN customer gateway for both the VPCs."
+msgstr "在VPC两边都创建VPN客户网关。"
+
+# d3b7adbcc13a4165815edae105d44fc2
+#: ../../managing_networks.rst:4509
+msgid ""
+"For more information, see `Section 15.25.5.1, “Creating and Updating a VPN "
+"Customer Gateway” <#create-vpn-customer-gateway>`__."
+msgstr "更多信息，参看 `章节 15.25.5.1, “创建或更新 VPN客户网关” <#create-vpn-customer-gateway>`__."
+
+# 77919bde060b4e299739c9be53a60eb8
+#: ../../managing_networks.rst:4514
+msgid "Enable a VPN connection on VPC A in passive mode."
+msgstr "在VPC A这边启用VPN的被动连接模式。"
+
+# 8ea54231bb2249e6ae3e0130c0296796
+#: ../../managing_networks.rst:4516
+msgid ""
+"For more information, see `Section 15.25.5.3, “Creating a VPN Connection” "
+"<#create-vpn-connection-vpc>`__."
+msgstr "更多信息，参看 `章节 15.25.5.3, “创建VPN连接” <#create-vpn-connection-vpc>`__."
+
+# 14ae7f0b268f42b0a79b9c961fe70c75
+#: ../../managing_networks.rst:4519
+msgid ""
+"Ensure that the customer gateway is pointed to VPC B. The VPN connection is "
+"shown in the Disconnected state."
+msgstr "确保客户网关指向VPC B。这个VPN当前显示的是未连接状态。"
+
+# f7ba3e9df3ac4049801e174c1b181c84
+#: ../../managing_networks.rst:4524
+msgid "Enable a VPN connection on VPC B."
+msgstr "在VPC B上启用VPN连接。"
+
+# 46b233eee044428188efb7edd2994c18
+#: ../../managing_networks.rst:4526
+msgid ""
+"Ensure that the customer gateway is pointed to VPC A. Because virtual router"
+" of VPC A, in this case, is in passive mode and is waiting for the virtual "
+"router of VPC B to initiate the connection, VPC B virtual router should not "
+"be in passive mode."
+msgstr "确保客户网关指向VPC A。在这个示例里，因为VPC A的虚拟路由器是处于被动模式且等待着VPC B进行初始化连接，所以VPC B的虚拟路由器不要设置为被动模式。"
+
+# 017ef29bf6994c348cd076349e7eabaf
+#: ../../managing_networks.rst:4531
+msgid "The VPN connection is shown in the Disconnected state."
+msgstr "VPN连接当前显示为未连接状态。"
+
+# 849dd8090fb74fa9a6696467a54e91c4
+#: ../../managing_networks.rst:4533
+msgid ""
+"Creating VPN connection on both the VPCs initiates a VPN connection. Wait "
+"for few seconds. The default is 30 seconds for both the VPN connections to "
+"show the Connected state."
+msgstr "VPC两边的VPN会进行初始化连接。默认为30秒之后，两边VPN都会显示为已连接状态。"
+
+# 8fb620a0c32649b8a3ad2e44584f8a13
+#: ../../managing_networks.rst:4538
+msgid "Restarting and Removing a VPN Connection"
+msgstr "VPN连接的重启和删除"
+
+# 2d31e38ca55b40ac9e8ce765dd0d3692
+#: ../../managing_networks.rst:4618
+msgid "All the VPN connections you created are displayed."
+msgstr "系统会显示创建VPN连接对话框："
+
+# 6aeb5be8241c49548bc0501a9f5b59f0
+#: ../../managing_networks.rst:4622
+msgid "Select the VPN connection you want to work with."
+msgstr "选择您要操作的VPN连接。"
+
+# 410c2e173f9e414dab7470faec1c5598
+#: ../../managing_networks.rst:4624
+msgid "The Details tab is displayed."
+msgstr "系统显示详细信息页。"
+
+# 0516c8c707dd4a049cc801f1cc68fabb
+#: ../../managing_networks.rst:4628
+msgid ""
+"To remove a VPN connection, click the Delete VPN connection button |remove-"
+"vpn.png: button to remove a VPN connection|"
+msgstr "删除一个VPN连接，点击删除VPN连接按钮。 |remove-vpn.png: button to remove a VPN connection|"
+
+# d570926d708b453e81da0da78f495cc1
+#: ../../managing_networks.rst:4631
+msgid ""
+"To restart a VPN connection, click the Reset VPN connection button present "
+"in the Details tab. |reset-vpn.png: button to reset a VPN connection|"
+msgstr "要重启VPN连接，请点击详细信息页的重置VPN连接按钮。 |reset-vpn.png: button to reset a VPN connection|"
+
+# 73e93f585b5947af90ee476b4b71ca25
+#: ../../managing_networks.rst:4636
+msgid "About Inter-VLAN Routing (nTier Apps)"
+msgstr "关于vlan间路由(多层应用)"
+
+# e1cdf935aea64e868a11d602b20cf6c3
+#: ../../managing_networks.rst:4638
+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 the VMs. In effect, "
+"you can segment VMs by means of VLANs into different networks that can host "
+"multi-tier applications, such as Web, Application, or Database. Such "
+"segmentation by means of VLANs logically separate application VMs for higher"
+" security and lower broadcasts, while remaining physically connected to the "
+"same device."
+msgstr "vlan间路由(多层应用)提供了在vlan间通过流量路由的功能。这个特性使你能够j建立私有云(vpc)，独立分割的云，可容纳多层应用程序。这些层被部署在不同的VLAN，可以互相沟通。您提供的VLAN层的创建和部署虚拟机可以在不同的层上。VLAN连接到一个虚拟路由器，这有利于虚拟机之间的通信。实际上，你可以通过不同定义的vlan来分割你的虚拟机到不同网络，以便承担多层应用，如Web，应用程序或数据库的虚拟机。通过VLAN的逻辑上独立的应用程序的虚拟具有较高的安全性和较低的广播，同时任然物理连接到同一设备。"
+
+# 0d404f9da0ba4f8aa58cab4bb8994e7f
+#: ../../managing_networks.rst:4651
+msgid "This feature is supported on XenServer, KVM, and VMware hypervisors."
+msgstr "在 XenServer ,KVM和 VMware hypervisors支持这个特性"
+
+# b48459f15e6a45318c79f097d562ed35
+#: ../../managing_networks.rst:4653
+msgid "The major advantages are:"
+msgstr "主要的优势为："
+
+# 37506050acaf40fda04742118858f794
+#: ../../managing_networks.rst:4657
+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 "管理可以部署一个vlans集，同时运行用户部署虚拟机在这些vlan上。从预先指定的vlan集中随机的为租户分配一个来宾vlan.租户处于同一层的所有vm处于分配给这个租户的来宾vlan."
+
+# 06560c3f129242f0adf92f680f2274df
+#: ../../managing_networks.rst:4662
+msgid ""
+"A VLAN allocated for an account cannot be shared between multiple accounts."
+msgstr "一个租户分配到的vlan不能被多个租户共享"
+
+# 25eee29513534fd4bb12a269333bd787
+#: ../../managing_networks.rst:4666
+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 "管理员允许所有用户创建自己的vpc,并部署应用。这个场景中，租户的虚拟机被部署到改租户的分配到的vlan中"
+
+# 74e4b83e45024768b481877a882eba72
+#: ../../managing_networks.rst:4672
+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 "管理员和用户都可以创建多个vpcs.当第一个虚拟机被部署到该层时候，一个来宾网络nic插入到这个vpc虚拟路由器上"
+
+# 8f27053c8ee44c22b62581053f1910b1
+#: ../../managing_networks.rst:4678
+msgid ""
+"The administrator can create the following gateways to send to or receive "
+"traffic from the VMs:"
+msgstr "管理员创建网关用接受和发送来自vm的流量："
+
+# 52b5a0ec994b4c8daf1db4d35c2aa504
+#: ../../managing_networks.rst:4683
+msgid ""
+"**VPN Gateway**: For more information, see `Section 15.25.5.2, “Creating a "
+"VPN gateway for the VPC” <#create-vpn-gateway-for-vpc>`__."
+msgstr "**VPN网关**: 更多信息，参看 `章节 15.25.5.2, “为VPC创建VPN网关” <#create-vpn-gateway-for-vpc>`__."
+
+# 2e0edcccf95c4a1dbf3c151de2439616
+#: ../../managing_networks.rst:4689
+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 "**公网网关**：当为vpc创建一个虚拟路由器时，这个vpc的公共网关就添加到虚拟路由器当中。公共网关还没有暴露到最终用户。你不允许其列出，也不允许建立任何静态路由。"
+
+# a659063093e948fcbec68ff5b117678c
+#: ../../managing_networks.rst:4696
+msgid ""
+"**Private Gateway**: For more information, see `Section 15.27.5, “Adding a "
+"Private Gateway to a VPC” <#add-gateway-vpc>`__."
+msgstr "**私网网关**: 更多信息，参看 `章节 15.27.5, “为VPC添加专用网关” <#add-gateway-vpc>`__."
+
+# f7e8baf7e8284cacb10f71e2b87529b9
+#: ../../managing_networks.rst:4701
+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 "管理员和用户可以创建各种可能的目的地的网关组合。但是，在部署中每种类型只能有一个网关。"
+
+# 066d3de08ee44a9f8ce5fd196908df8a
+#: ../../managing_networks.rst:4705
+msgid "For example:"
+msgstr "例如："
+
+# 3b955ae841204566b4939325f181cea5
+#: ../../managing_networks.rst:4709
+msgid ""
+"**VLANs and Public Gateway**: For example, an application is deployed in the"
+" cloud, and the Web application VMs communicate with the Internet."
+msgstr "**VLAN和公网网关**: 比如，在云中部署了一个应用，并且这个web应用所在的虚拟机要和因特网通信。"
+
+# 070bb78cb77c45899817353d9d3afe40
+#: ../../managing_networks.rst:4715
+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 "**VLANs, VPN网关和公网网关**: 比如, 云中部署了一个应用;部署这个web应用的虚拟机要和因特网通信; 并且数据库虚拟要个先前提到的设备通信"
+
+# 612fa4a2bba040fabccd21dbc46a3b91
+#: ../../managing_networks.rst:4722
+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 "管理员可以在虚拟路由器定义一个访问控制列表(ACL)用于过滤vlan或者因特网和vlan直接的流量。你可定义基于CIDR,端口范围，协议，类型代码(如果选用ICPM协议)和进出流量的acl"
+
+# 754f1b2b5a1b4f92b6ef9530907e259d
+#: ../../managing_networks.rst:4728
+msgid ""
+"The following figure shows the possible deployment scenarios of a Inter-VLAN"
+" setup:"
+msgstr "下图显示了可能的部署一个VLAN间的场景设置的："
+
+# 536386b54906472e8b8ddd90dab72f0b
+#: ../../managing_networks.rst:4731
+msgid "|mutltier.png: a multi-tier setup.|"
+msgstr "|mutltier.png: a multi-tier setup.|"
+
+# a610a58c65f0482dbd12dd339ec17888
+#: ../../managing_networks.rst:4733
+msgid ""
+"To set up a multi-tier Inter-VLAN deployment, see `Section 15.27, "
+"“Configuring a Virtual Private Cloud” <#configure-vpc>`__."
+msgstr "关于设置一个多层VLAN的信息，参看 `章节 15.27, “配置虚拟专用云” <#configure-vpc>`__."
+
+# 8c6f5c047656431f9efa0775f05f20e9
+#: ../../managing_networks.rst:4737
+msgid "Configuring a Virtual Private Cloud"
+msgstr "配置一个虚拟私有云（VPC）"
+
+# 51dbe5ce31064783a34b81a1169ce257
+#: ../../managing_networks.rst:4740
+msgid "About Virtual Private Clouds"
+msgstr "关于虚拟私有云（VPC）"
+
+# 36f1958de4dd4cd085e8e06b28b118b3
+#: ../../managing_networks.rst:4742
+msgid ""
+"CloudStack Virtual Private Cloud is a private, isolated part of CloudStack. "
+"A VPC can have its own virtual network topology that resembles a traditional"
+" physical network. You can launch VMs in the virtual network that can have "
+"private addresses in the range of your choice, for example: 10.0.0.0/16. You"
+" can define network tiers within your VPC network range, which in turn "
+"enables you to group similar kinds of instances based on IP address range."
+msgstr "CloudStackVPC是CloudStack云中私有并隔离的部分。一个VPC可以使用自己的虚拟网络拓扑来组建传统物理网络。在这个虚拟网络中，您创建的虚机的私网地址可以由您自主选择IP范围，例如10.0.0.0/16。您可以在VPC网络范围内定义多个网络层，这些层可以让你将类似的虚机按IP地址范围分组。"
+
+# 231f37879fac4621b48e0c39fc46c2f1
+#: ../../managing_networks.rst:4750
+msgid ""
+"For example, if a VPC has the private range 10.0.0.0/16, its guest networks "
+"can have the network ranges 10.0.1.0/24, 10.0.2.0/24, 10.0.3.0/24, and so "
+"on."
+msgstr "例如：一个VPC的私有地址范围是10.0.0.0/16，其中的用户网络的地址范围可以分别是10.0.1.0/24、10.0.2.0/24、10.0.3.0/24等等。"
+
+# b1aa5c2f5259429f9ef169a6f5ca6f97
+#: ../../managing_networks.rst:4757
+msgid "A VPC is comprised of the following network components:"
+msgstr "VPC主要由以下网络组件构成："
+
+# 81f964d528e6402ba3e1428cddb674bd
+#: ../../managing_networks.rst:4761
+msgid ""
+"**VPC**: A VPC acts as a container for multiple isolated networks that can "
+"communicate with each other via its virtual router."
+msgstr "**VPC**：一个VPC是多个隔离网络的容器，隔离网络间可以通过VPC的虚拟路由器互通。"
+
+# c94ea42c1d514b648ea93bc841f47eeb
+#: ../../managing_networks.rst:4766
+msgid ""
+"**Network Tiers**: Each tier acts as an isolated network with its own VLANs "
+"and CIDR list, where you can place groups of resources, such as VMs. The "
+"tiers are segmented by means of VLANs. The NIC of each tier acts as its "
+"gateway."
+msgstr "**网络层**：每个层是一个拥有各自VLAN和CIDR的隔离网络。您可以在层内放置VM等各种资源组。层与层之间通过VLAN方式隔离。VPC虚拟路由器在每个层中的网卡是该层的网关。"
+
+# 685738b4e44748a9ac538dfd407f1e6e
+#: ../../managing_networks.rst:4773
+msgid ""
+"**Virtual Router**: A virtual router is automatically created and started "
+"when you create a VPC. The virtual router connect the tiers and direct "
+"traffic among the public gateway, the VPN gateways, and the NAT instances. "
+"For each tier, a corresponding NIC and IP exist in the virtual router. The "
+"virtual router provides DNS and DHCP services through its IP."
+msgstr "**虚拟路由器**：创建VPC时会自动创建并启动一个虚拟路由器。该虚拟路由器连接了各层，并负责各层与公网网关、VPN网关和NAT实例间的网络流量。对于每个层，该虚拟路由器都会有对应的网卡和IP，并通过该IP提供DNS和DHCP服务。"
+
+# 4ecd641c04c5446da55dc72dd42babb9
+#: ../../managing_networks.rst:4782
+msgid ""
+"**Public Gateway**: The traffic to and from the Internet routed to the VPC "
+"through the public gateway. In a VPC, the public gateway is not exposed to "
+"the end user; therefore, static routes are not support for the public "
+"gateway."
+msgstr "**公网网关**：VPC进出互联网的流量会走公网网关。VPC中的公网网关不暴露给最终用户，因此公网网关上不支持静态路由。"
+
+# 64b40911d3fa4da8bd9fc7c20cd350ed
+#: ../../managing_networks.rst:4789
+msgid ""
+"**Private Gateway**: All the traffic to and from a private network routed to"
+" the VPC through the private gateway. For more information, see `Section "
+"15.27.5, “Adding a Private Gateway to a VPC” <#add-gateway-vpc>`__."
+msgstr "**私有网关**：VPC进出某个私有网络的流量通过私有网关。更多信息，请查阅 `章节 15.27.5, “为VPC添加专用网关” <#add-gateway-vpc>`__."
+
+# efdd8a661d1a4f77a361eeefed2f8f82
+#: ../../managing_networks.rst:4796
+msgid "**VPN Gateway**: The VPC side of a VPN connection."
+msgstr "**VPN 网关**：VPN连接的VPC端。"
+
+# c30d05145eec45938cb3f8a99bf3eabe
+#: ../../managing_networks.rst:4800
+msgid ""
+"**Site-to-Site VPN Connection**: A hardware-based VPN connection between "
+"your VPC and your datacenter, home network, or co-location facility. For "
+"more information, see `Section 15.25.5, “Setting Up a Site-to-Site VPN "
+"Connection” <#site-to-site-vpn>`__."
+msgstr "**点对点VPN连接**：您的VPC和您的数据中心、家庭网络、主机托管设施之间基于硬件的VPN连接。更多信息，请查阅 `章节 15.25.5, “设置站点-到-站点 VPN连接” <#site-to-site-vpn>`__."
+
+# 83a3f96194b24badaa38506d70b11009
+#: ../../managing_networks.rst:4807
+msgid ""
+"**Customer Gateway**: The customer side of a VPN Connection. For more "
+"information, see `Section 15.25.5.1, “Creating and Updating a VPN Customer "
+"Gateway” <#create-vpn-customer-gateway>`__."
+msgstr "**客户网关**: 客户这边的VPN连接。更多信息，参看 `章节 15.25.5.1, “创建和更新VPN客户网关” <#create-vpn-customer-gateway>`__."
+
+# cb437b168320462f8765d7949d2c2d1d
+#: ../../managing_networks.rst:4813
+msgid ""
+"**NAT Instance**: An instance that provides Port Address Translation for "
+"instances to access the Internet via the public gateway. For more "
+"information, see `Section 15.27.10, “Enabling or Disabling Static NAT on a "
+"VPC” <#enable-disable-static-nat-vpc>`__."
+msgstr "**NAT实例**:在用户虚机通过公网网关访问公网时，提供端口地址转换的实例。关于更多信息，请查阅 `章节 15.27.10, “在VPC中开启或禁用静态NAT” <#enable-disable-static-nat-vpc>`__."
+
+# 2dcef6cbbdf64b628e2fb8898dadeac0
+#: ../../managing_networks.rst:4820
+msgid ""
+"**Network ACL**: Network ACL is a group of Network ACL items. Network ACL "
+"items are nothing but numbered rules that are evaluated in order, starting "
+"with the lowest numbered rule. These rules determine whether traffic is "
+"allowed in or out of any tier associated with the network ACL. For more "
+"information, see `Section 15.27.4, “Configuring Network Access Control List”"
+" <#configure-acl>`__."
+msgstr "**网络ACL**: 网络ACL是一组网络访问控制列表。这些列表就是一个按顺序编号的规则，执行的时候，从最小的编号开始。这些规则决定了与此ACL关联的各个层的进出流量会被允许或阻止。更多信息，参看 `章节 15.27.4, “配置网络访问控制列表” <#configure-acl>`__."
+
+# 8021e62528a3456283a94683c84a5a30
+#: ../../managing_networks.rst:4830
+msgid ""
+"In a VPC, the following four basic options of network architectures are "
+"present:"
+msgstr "VPC有以下四个基本的网络架构："
+
+# 79c69f1431cf41f992cf738d7291af75
+#: ../../managing_networks.rst:4835
+msgid "VPC with a public gateway only"
+msgstr "只有一个公网网关的VPC"
+
+# 3b7dc9ded7fd4111a027ec9623f8ab3b
+#: ../../managing_networks.rst:4839
+msgid "VPC with public and private gateways"
+msgstr "VPC的公有和私有网关"
+
+# 840b7b65488a4ddab62c2f20cbc5626b
+#: ../../managing_networks.rst:4843
+msgid "VPC with public and private gateways and site-to-site VPN access"
+msgstr "VPC的公有和私有网关以及site-to-site VPN访问"
+
+# 7b5faa4272c845e5abe17edbc0486fc9
+#: ../../managing_networks.rst:4847
+msgid "VPC with a private gateway only and site-to-site VPN access"
+msgstr "只有私有网关的VPC以及site-to-site VPN访问"
+
+# 51bfc1cebf464c5bbc3d58dba695d58a
+#: ../../managing_networks.rst:4852
+msgid "You can connect your VPC to:"
+msgstr "你可以连接你的VPC："
+
+# a47fa88e4c984151aaf4250a0542efbd
+#: ../../managing_networks.rst:4856
+msgid "The Internet through the public gateway."
+msgstr "通过公有网关连接到Internet."
+
+# 75610d2bcbf3457085a4d69186ac178b
+#: ../../managing_networks.rst:4860
+msgid ""
+"The corporate datacenter by using a site-to-site VPN connection through the "
+"VPN gateway."
+msgstr "通过site-to-siteVPN网关连接到相邻数据中心。"
+
+# 25f83464cf7d423f89842ec7bb5b2427
+#: ../../managing_networks.rst:4865
+msgid ""
+"Both the Internet and your corporate datacenter by using both the public "
+"gateway and a VPN gateway."
+msgstr "通过公有和私有VPN网关同时连接到Internet和相邻数据中心。"
+
+# b4a8939012bd4d57becfcf7bf2b208b7
+#: ../../managing_networks.rst:4871
+msgid "Consider the following before you create a VPC:"
+msgstr "在创建VPC之前，确认以下事项："
+
+# 8f4b07dab7f74e4e84325dfa7c3fb31a
+#: ../../managing_networks.rst:4875
+msgid "A VPC, by default, is created in the enabled state."
+msgstr "在创建好VPC之后，其默认处于启用状态。"
+
+# e0eddf322bcc4f58899c1d0ec98ff3a6
+#: ../../managing_networks.rst:4879
+msgid ""
+"A VPC can be created in Advance zone only, and can't belong to more than one"
+" zone at a time."
+msgstr "只能在高级区域中创建VPC，并且VPC只能属于一个区域。"
+
+# 94e822d9f9f4432183d26a7458ee0a7b
+#: ../../managing_networks.rst:4884
+msgid ""
+"The default number of VPCs an account can create is 20. However, you can "
+"change it by using the max.account.vpcs global parameter, which controls the"
+" maximum number of VPCs an account is allowed to create."
+msgstr "默认VPC的数量是20个。如果你需要更多的VPC的话，可以通过修改max.account.vpcs这个全局参数。这个参数是控制创建VPC的最大数量的。"
+
+# ba83295468c54bd8ac9701b0ac75e1c6
+#: ../../managing_networks.rst:4890
+msgid ""
+"The default number of tiers an account can create within a VPC is 3. You can"
+" configure this number by using the vpc.max.networks parameter."
+msgstr "默认一个用户能创建VPC的层数是三层。也可以通过vpc.max.networks这个参数修改。"
+
+# b3365ac8ef2d4de2a5bdcdcadcb9df03
+#: ../../managing_networks.rst:4896
+msgid ""
+"Each tier should have an unique CIDR in the VPC. Ensure that the tier's CIDR"
+" should be within the VPC CIDR range."
+msgstr "VPC中每一层都需要是唯一的CIDR，并且这个CIDR是在VPC的CIDR的范围之内。"
+
+# 4482ffae03974738b00591ed147ac312
+#: ../../managing_networks.rst:4901
+msgid "A tier belongs to only one VPC."
+msgstr "每一层只能属于一个VPC。"
+
+# 33f875bfaa2f449eab177c836ba3e595
+#: ../../managing_networks.rst:4905
+msgid "All network tiers inside the VPC should belong to the same account."
+msgstr "VPC中所有网络层都应属于同一个帐号。"
+
+# 381f803ea9004045ab58f5d055f536c7
+#: ../../managing_networks.rst:4909
+msgid ""
+"When a VPC is created, by default, a SourceNAT IP is allocated to it. The "
+"Source NAT IP is released only when the VPC is removed."
+msgstr "当VPC创建好之后，默认会分配好SourceNAT IP。当此VPC删除之后，SourceNAT IP也会被释放。"
+
+# 428718bf75c8495b9390710e65fbbdff
+#: ../../managing_networks.rst:4914
+msgid ""
+"A public IP can be used for only one purpose at a time. If the IP is a "
+"sourceNAT, it cannot be used for StaticNAT or port forwarding."
+msgstr "一个公网IP只能用一个用途。如果此IP用于SourceNAT作用的话，就不能同时再用作StaticNAT 或端口转发。"
+
+# 38bd1f10ec864e648bba9fae452daf4a
+#: ../../managing_networks.rst:4919
+msgid ""
+"The instances can only have a private IP address that you provision. To "
+"communicate with the Internet, enable NAT to an instance that you launch in "
+"your VPC."
+msgstr "一个实例只能有一个私有IP地址，为了访问Internet,你可以为VPC里的此实例启用NAT功能。"
+
+# b39e4604f3bd46c9ae5b2bb9ea9b9ed8
+#: ../../managing_networks.rst:4925
+msgid ""
+"Only new networks can be added to a VPC. The maximum number of networks per "
+"VPC is limited by the value you specify in the vpc.max.networks parameter. "
+"The default value is three."
+msgstr "只有新的网络才能加入VPC。每一个VPC的最大网络数量由参数vpc.max.networks指定。其默认值为3."
+
+# 82f230ac4a4c4454bebda33b860a5144
+#: ../../managing_networks.rst:4931
+msgid ""
+"The load balancing service can be supported by only one tier inside the VPC."
+msgstr "VPC中只有一层支持负载均衡服务。"
+
+# 674409f549534664943c157e86b4751f
+#: ../../managing_networks.rst:4936
+msgid "If an IP address is assigned to a tier:"
+msgstr "如果一个IP地址被赋予一个网络层："
+
+# fff45697eaa74169a43b238c7cb7d850
+#: ../../managing_networks.rst:4940
+msgid ""
+"That IP can't be used by more than one tier at a time in the VPC. For "
+"example, if you have tiers A and B, and a public IP1, you can create a port "
+"forwarding rule by using the IP either for A or B, but not for both."
+msgstr "那么这个IP就不能在VPC里被另外的层所使用。比如：如果你有A层和B层以及一个公网IP地址，则你可以为A或B创建一个端口转发规则，但不能同时在A和B上创建。"
+
+# bb2829ee8fc143579a544bca2b190a12
+#: ../../managing_networks.rst:4947
+msgid ""
+"That IP can't be used for StaticNAT, load balancing, or port forwarding "
+"rules for another guest network inside the VPC."
+msgstr "那个IP也不能在VPC的其它的客户网络里用作StaticNAT,负载均衡，端口转发规则。"
+
+# f30c68c2eb624318b01d472bc88fb934
+#: ../../managing_networks.rst:4952
+msgid "Remote access VPN is not supported in VPC networks."
+msgstr "VPC网络不支持Remote access VPN。"
+
+# 664f092fb65d4f7eb7b57597dc20eee3
+#: ../../managing_networks.rst:4955
+msgid "Adding a Virtual Private Cloud"
+msgstr "添加一个VPC"
+
+# d8f0f8db2b2b48b5993868b9be41e740
+#: ../../managing_networks.rst:4957
+msgid ""
+"When creating the VPC, you simply provide the zone and a set of IP addresses"
+" for the VPC network address space. You specify this set of addresses in the"
+" form of a Classless Inter-Domain Routing (CIDR) block."
+msgstr "当创建VPC时，你只需要提供区域名和VPC要使用的一组IP地址。这组IP地址是以CIDR块的形式提供。"
+
+# 68e44a29c9cd46b3814ef56e13a45415
+#: ../../managing_networks.rst:4975
+msgid "Click Add VPC. The Add VPC page is displayed as follows:"
+msgstr "点击添加VPC按钮。页面呈现以下："
+
+# 663db894b6d44e05bad28dd1cf0ff9b4
+#: ../../managing_networks.rst:4977
+msgid "|add-vpc.png: adding a vpc.|"
+msgstr "|add-vpc.png: adding a vpc.|"
+
+# 9b71ee6298ad4ff8b3677dd885a61d39
+#: ../../managing_networks.rst:4983
+msgid "**Name**: A short name for the VPC that you are creating."
+msgstr "**名称**: 要创建的VPC的名称。"
+
+# 4aa804d3171d4eb8a0a95651b83f5c29
+#: ../../managing_networks.rst:4987
+msgid "**Description**: A brief description of the VPC."
+msgstr "**描述**: 关于此VPC的简短描述."
+
+# f4eeaac96959486781023464ab4c5c24
+#: ../../managing_networks.rst:4991
+msgid "**Zone**: Choose the zone where you want the VPC to be available."
+msgstr "**区域**: 你希望将此VPN应用在哪个区域中。"
+
+# 990e793a0bc5420baa6b59dd61e90efe
+#: ../../managing_networks.rst:4995
+msgid ""
+"**Super CIDR for Guest Networks**: Defines the CIDR range for all the tiers "
+"(guest networks) within a VPC. When you create a tier, ensure that its CIDR "
+"is within the Super CIDR value you enter. The CIDR must be RFC1918 "
+"compliant."
+msgstr "**客户网络超级CIDR**: 定义一个VPC内所有层（客户网络）的CIDR范围。当你新创建一个层时，这个层的CIDR必须在这个超级CIDR范围之内。CIDR的格式定义必须符合RFC1918。"
+
+# 4af670c01148481cb56fc6fee83bdcb1
+#: ../../managing_networks.rst:5002
+msgid ""
+"**DNS domain for Guest Networks**: If you want to assign a special domain "
+"name, specify the DNS suffix. This parameter is applied to all the tiers "
+"within the VPC. That implies, all the tiers you create in the VPC belong to "
+"the same DNS domain. If the parameter is not specified, a DNS domain name is"
+" generated automatically."
+msgstr "**客户网络的DNS域名**: 如果你需要一个域名，则需要在此指定域名后缀。这个参数会应用到VPC中所有的层中。这表示，VPC中所有的层都属于同一个域。如果没有指定域名，则域名会由系统随机产生。"
+
+# 990485d745a04f93926573a279396d9b
+#: ../../managing_networks.rst:5010
+msgid ""
+"**Public Load Balancer Provider**: You have two options: VPC Virtual Router "
+"and Netscaler."
+msgstr "**公共负载均衡提供者**: 有两个选项：VPC虚拟路由器和 Netscaler。"
+
+# 23e6b6bbbd57448185253c915b8ad5f0
+#: ../../managing_networks.rst:5018
+msgid "Adding Tiers"
+msgstr "添加层"
+
+# ff39814e4cfe42168898bec95c63bd64
+#: ../../managing_networks.rst:5020
+msgid ""
+"Tiers are distinct locations within a VPC that act as isolated networks, "
+"which do not have access to other tiers by default. Tiers are set up on "
+"different VLANs that can communicate with each other by using a virtual "
+"router. Tiers provide inexpensive, low latency network connectivity to other"
+" tiers within the VPC."
+msgstr "层在VPC里起来隔离网络的作用，默认规则是层之间不能互访。不同VLAN之间的层可以通过虚拟机实现连接。层在VPC内部提供一种廉价，低延迟的网络连接。"
+
+# 112dec95edd24541b50be348ca4879f1
+# d6583ef8f25f444f92aa0c16debd9ba7
+#: ../../managing_networks.rst:5038 ../../managing_networks.rst:6682
+msgid ""
+"All the VPC that you have created for the account is listed in the page."
+msgstr "此帐号创建的所有VPC将显示在页面中。"
+
+# 6b489291378641d99c7e3dfc771af3de
+#: ../../managing_networks.rst:5041
+msgid ""
+"The end users can see their own VPCs, while root and domain admin can see "
+"any VPC they are authorized to see."
+msgstr "最终用户能看到他们自己的VPC，系统管理用户和域管理员可以看到所有被授权查看的VPC。"
+
+# 4996cd7a3c8e49ce842db18908305e3e
+# ee5e856c97144914852fcc5b7106e740
+#: ../../managing_networks.rst:5045 ../../managing_networks.rst:6687
+msgid ""
+"Click the Configure button of the VPC for which you want to set up tiers."
+msgstr "在你希望设置层的VPC里，点击配置按钮。"
+
+# f345aeb0c14d4ebe9c779e4ef8d45a80
+#: ../../managing_networks.rst:5050
+msgid "Click Create network."
+msgstr "点击新建网络。"
+
+# a138378a695c4ffb85e071e4e5668647
+#: ../../managing_networks.rst:5052
+msgid "The Add new tier dialog is displayed, as follows:"
+msgstr "然后，添加层的对话界面就会出现。如下："
+
+# 5e067e1a2c184e638b51030209dcd153
+#: ../../managing_networks.rst:5054
+msgid "|add-tier.png: adding a tier to a vpc.|"
+msgstr "|add-tier.png: adding a tier to a vpc.|"
+
+# 42a84e496afd4a909af40619de500c02
+#: ../../managing_networks.rst:5056
+msgid ""
+"If you have already created tiers, the VPC diagram is displayed. Click "
+"Create Tier to add a new tier."
+msgstr "如果你已添加层，VPC界面就会出现。点击添加层可以增加一个新的层。"
+
+# 95298a50ccd3433a8ea1f2fed9df787d
+#: ../../managing_networks.rst:5067
+msgid "**Name**: A unique name for the tier you create."
+msgstr "**名称**: 你添加的层的一个唯一的层名。"
+
+# a6969eda2b5e4e61b5520e0c523e7064
+#: ../../managing_networks.rst:5071
+msgid ""
+"**Network Offering**: The following default network offerings are listed: "
+"Internal LB, DefaultIsolatedNetworkOfferingForVpcNetworksNoLB, "
+"DefaultIsolatedNetworkOfferingForVpcNetworks"
+msgstr "**网络方案**: 默认有以下几种网络方案: Internal LB, DefaultIsolatedNetworkOfferingForVpcNetworksNoLB, DefaultIsolatedNetworkOfferingForVpcNetworks"
+
+# 9963ce9168d74acaaf8ab3c9289533c2
+#: ../../managing_networks.rst:5076
+msgid ""
+"In a VPC, only one tier can be created by using LB-enabled network offering."
+msgstr "在一个VPC中，用LB-enabled network offering只能创建一个层。"
+
+# 9a666245953b4d769667d62a479655f8
+#: ../../managing_networks.rst:5088
+msgid "**VLAN**: The VLAN ID for the tier that the root admin creates."
+msgstr "**VLAN**: 指定系统管理员创建的层的VLAN ID号。"
+
+# 43718c048f834c0fbbe95d0255e600b2
+#: ../../managing_networks.rst:5090
+msgid ""
+"This option is only visible if the network offering you selected is VLAN-"
+"enabled."
+msgstr "这个选项只在你选择的方案在VLAN-enabled的情况下才会显示出来。"
+
+# e984dca5699d49549e497366d7fa6cfa
+#: ../../managing_networks.rst:5093
+msgid ""
+"For more information, see the Assigning VLANs to Isolated Networks section "
+"in the CloudStack Administration Guide."
+msgstr "如需要更多信息，请查看CloudStack管理文档里the Assigning VLANs to Isolated Networks章节。"
+
+# fd0893c5f3f244cd959a9e3da04a3244
+#: ../../managing_networks.rst:5110
+msgid "Continue with configuring access control list for the tier."
+msgstr "继续为层配置访问控制列表。"
+
+# 9ecb7309fd5044a7b9252ea6777743d3
+#: ../../managing_networks.rst:5113
+msgid "Configuring Network Access Control List"
+msgstr "配置网络访问控制列表"
+
+# f8bec17b79944b3c941a1ba25d55f57c
+#: ../../managing_networks.rst:5115
+msgid ""
+"Define Network Access Control List (ACL) on the VPC virtual router to "
+"control incoming (ingress) and outgoing (egress) traffic between the VPC "
+"tiers, and the tiers and Internet. By default, all incoming traffic to the "
+"guest networks is blocked and all outgoing traffic from guest networks is "
+"allowed, once you add an ACL rule for outgoing traffic, then only outgoing "
+"traffic specified in this ACL rule is allowed, the rest is blocked. To open "
+"the ports, you must create a new network ACL. The network ACLs can be "
+"created for the tiers only if the NetworkACL service is supported."
+msgstr "定义网络访问控制列表（ACL），用以在VPC的层之间，或是层与互联网之间控制进出流量。默认情况下，客户网络的所有进入流量被阻止，所有外出流量被允许。一旦在外出流量方向添加了ACL，则只有ACL规则允许的流量可以被允许，其余的外出流量会被阻止。如果要开放其它端口，则需要在新的ACL中明确定义。只有在支持NetworkACL服务的条件下，只能创建层的ACL。"
+
+# 883738de9a0f4f9cb19d5381137f41b7
+#: ../../managing_networks.rst:5126
+msgid "About Network ACL Lists"
+msgstr "关于ACL列表"
+
+# 0013030c60f54306b754480ec7cd56ee
+#: ../../managing_networks.rst:5128
+msgid ""
+"In CloudStack terminology, Network ACL is a group of Network ACL items. "
+"Network ACL items are nothing but numbered rules that are evaluated in "
+"order, starting with the lowest numbered rule. These rules determine whether"
+" traffic is allowed in or out of any tier associated with the network ACL. "
+"You need to add the Network ACL items to the Network ACL, then associate the"
+" Network ACL with a tier. Network ACL is associated with a VPC and can be "
+"assigned to multiple VPC tiers within a VPC. A Tier is associated with a "
+"Network ACL at all the times. Each tier can be associated with only one ACL."
+msgstr "在CloudStack术语中，ACL指的是一组针对网络条目。其按条目规则顺序执行，从最小值开始。这些规则决定了与此ACL关联的层的进出流量是被允许还是阻止。操作的方法是添加一个ACL，然后将这个ACL与层关联。ACL在整个VPC中使用，它可以被关系到一个VPC当中多个层中。一个层能及只能关联到一个ACL中。"
+
+# cd30ab4ab3de4e19944373cf3ad29ee4
+#: ../../managing_networks.rst:5138
+msgid ""
+"The default Network ACL is used when no ACL is associated. Default behavior "
+"is all the incoming traffic is blocked and outgoing traffic is allowed from "
+"the tiers. Default network ACL cannot be removed or modified. Contents of "
+"the default Network ACL is:"
+msgstr "当没有ACL明确关联时，会有一个默认的ACL起作用。默认规则是层中所有进入流量被阻止，所有外出流量被允许默认的ACL不能被删除或修改。默认ACL的内容如下："
+
+# 0ffe15ce91bb46a181dd0f5f4352b037
+#: ../../managing_networks.rst:5144
+msgid "Rule"
+msgstr "规则"
+
+# fd278173e97b408ab779ea644ba8c05b
+#: ../../managing_networks.rst:5144
+msgid "Protocol"
+msgstr "协议"
+
+# c8650729b8784c91b63c3256b2a6da0c
+#: ../../managing_networks.rst:5144
+msgid "Traffic type"
+msgstr "流量类型"
+
+# 32be36b683c640f6bcb229e524bd7249
+#: ../../managing_networks.rst:5144
+msgid "Action"
+msgstr "动作"
+
+# e2de15ead8bd422c873fa6c50b4a42a9
+# b05631934bf140be841f32970809a285
+#: ../../managing_networks.rst:5146 ../../managing_networks.rst:5147
+msgid "All"
+msgstr "所有"
+
+# 8449d6b79ab54e9a9399ccd13ab059ef
+#: ../../managing_networks.rst:5146
+msgid "Ingress"
+msgstr "进入流量"
+
+# 1eeb4aa87118496eb955beec9206e674
+# bb21769e9775425ab94a56a56b43cba9
+#: ../../managing_networks.rst:5146 ../../managing_networks.rst:5147
+msgid "0.0.0.0/0"
+msgstr "0.0.0.0/0"
+
+# bd09cdb155ae4f8887094159bb0b7ebc
+#: ../../managing_networks.rst:5147
+msgid "Egress"
+msgstr "外出流量"
+
+# d149d46d02694b94a0f6d46db5982fb2
+#: ../../managing_networks.rst:5152
+msgid "Creating ACL Lists"
+msgstr "创建ACL列表"
+
+# b101c0f175594179ac9f4f323f335d7d
+# 2154f606bc904937a85a8fc00bbf23b5
+#: ../../managing_networks.rst:5215 ../../managing_networks.rst:5257
+msgid "Select Network ACL Lists."
+msgstr "选择网络ACL列表。"
+
+# 517402dccaae4fa1befd493301ea949d
+#: ../../managing_networks.rst:5217
+msgid ""
+"The following default rules are displayed in the Network ACLs page: "
+"default\\_allow, default\\_deny."
+msgstr "在ACL页面，下面默认规则将会显示出来：default\\_allow, default\\_deny."
+
+# 37dadcca056740d98d2f961f0f2c17b1
+#: ../../managing_networks.rst:5222
+msgid "Click Add ACL Lists, and specify the following:"
+msgstr "点击添加ACL列表，指定以下配置："
+
+# ec72127f5c594aa88546a51a9805357b
+#: ../../managing_networks.rst:5226
+msgid "**ACL List Name**: A name for the ACL list."
+msgstr "**ACL列表名称**: 为ACL列表命名。"
+
+# 4cd0a64154f14244bc624f4c6a44ba55
+#: ../../managing_networks.rst:5230
+msgid ""
+"**Description**: A short description of the ACL list that can be displayed "
+"to users."
+msgstr "**描述**: ACL列表的简短描述。"
+
+# 799d333035784cebbc2ca6c0f6b13302
+#: ../../managing_networks.rst:5234
+msgid "Creating an ACL Rule"
+msgstr "创建一个ACL规则"
+
+# a408d9b21c4d4e77bc436d240b7e2d85
+#: ../../managing_networks.rst:5259
+msgid ""
+"In addition to the custom ACL lists you have created, the following default "
+"rules are displayed in the Network ACLs page: default\\_allow, "
+"default\\_deny."
+msgstr "除了创建的你自定义的ACL列表之后，以下默认ACL规则也会显示在页面中：default\\_allow, default\\_deny."
+
+# fc49dc48022a4e5d8e7ede413dce0a42
+# 4d7fc5b5b8474ee9ab87791bb3046cc3
+#: ../../managing_networks.rst:5265 ../../managing_networks.rst:5390
+msgid "Select the desired ACL list."
+msgstr "选择需要的ACL列表。"
+
+# aa57fa68748b4e6cb1571d8c78b4cb13
+#: ../../managing_networks.rst:5269
+msgid "Select the ACL List Rules tab."
+msgstr "选择ACL规则栏"
+
+# e11ef52e1bd54820a55d90c66c4566b3
+#: ../../managing_networks.rst:5271
+msgid ""
+"To add an ACL rule, fill in the following fields to specify what kind of "
+"network traffic is allowed in the VPC."
+msgstr "为了创建ACL规则，需要在VPC中定义下面哪些网络流量是允许的。"
+
+# c1b746e2fd69497a9973a9c4dda74961
+#: ../../managing_networks.rst:5276
+msgid "**Rule Number**: The order in which the rules are evaluated."
+msgstr "**规则序号**: 规则被执行的顺序。"
+
+# 755200e08f8b410db152ea927ecdca34
+#: ../../managing_networks.rst:5280
+msgid ""
+"**CIDR**: The CIDR acts as the Source CIDR for the Ingress rules, and "
+"Destination CIDR for the Egress rules. To accept traffic only from or 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 incoming "
+"traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr "**CIDR**: 对于进入的规则，CIDR对源地址起作用，对于外出的规则，CIDR对目标地址起作用。如果要定义多个可接受进出流量的特定地址段，需要以逗号分隔各个CIDR。CIDR是进入流量的基IP地址。比如， 192.168.0.0/22. 如要对所有CIDR允许流量, 设置为 0.0.0.0/0."
+
+# 6bbf467d779940e1aab67d2c17766733
+#: ../../managing_networks.rst:5289
+msgid "**Action**: What action to be taken. Allow traffic or block."
+msgstr "**操作**: 定义要进行的操作，允许或阻止。"
+
+# 0276a8206f3045e5899fcfef28a96a45
+#: ../../managing_networks.rst:5293
+msgid ""
+"**Protocol**: The networking protocol that sources use to send traffic to "
+"the tier. 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. All supports all the traffic. Other "
+"option is Protocol Number."
+msgstr "**协议**: 发送到层的源地址的网络协议。最终用户的访问和数据交换通常是用TCP和UDP协议。ICMP协议通常用来发送错误信息或网络监控。ALL表示支持所有协议流量，其它选项是协议编号。"
+
+# 5d95d28eac034c5c916ed60985a61d21
+#: ../../managing_networks.rst:5302
+msgid ""
+"**Start Port**, **End Port** (TCP, UDP only): A range of listening ports "
+"that are the destination for the incoming traffic. If you are opening a "
+"single port, use the same number in both fields."
+msgstr "**起始端口**, **结束端口** (TCP, UDP only):对进入流量，这些端口是指需要监听的目标地址的端口范围。如果你只开放一个端口，则在起始和结束端口里填写同一个端口。"
+
+# 08af29136df449deaa80cb9658d340f6
+#: ../../managing_networks.rst:5308
+msgid ""
+"**Protocol Number**: The protocol number associated with IPv4 or IPv6. For "
+"more information, see `Protocol Numbers <http://www.iana.org/assignments"
+"/protocol-numbers/protocol-numbers.xml>`__."
+msgstr "**协议编号**: 协议编号是与IPV4或IPV6相关联的。更多信息，请参阅 `协议号 <http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xml>`__."
+
+# ace82b72ecd94c41acc8598b519e2d14
+#: ../../managing_networks.rst:5314
+msgid ""
+"**ICMP Type**, **ICMP Code** (ICMP only): The type of message and error code"
+" that will be sent."
+msgstr "**ICMP类型**, **ICMP代码** (ICMP only): 信息类型及发送错误的代码。"
+
+# 2a8d8f3558b04c418b77c1f1b7e72d85
+#: ../../managing_networks.rst:5319
+msgid "**Traffic Type**: The type of traffic: Incoming or outgoing."
+msgstr "**流量类型**: 进出流量的类型。"
+
+# 9e09340a2c044bbdb9ca933949254900
+#: ../../managing_networks.rst:5323
+msgid "Click Add. The ACL rule is added."
+msgstr "点击添加。这个ACL规则就添加好了。"
+
+# 1968e40aada04c1db4e857f65930370d
+#: ../../managing_networks.rst:5325
+msgid ""
+"You can edit the tags assigned to the ACL rules and delete the ACL rules you"
+" have created. Click the appropriate button in the Details tab."
+msgstr "你可以重新编辑ACL标签，或是删除ACL。点击详细信息里的appropriate按钮。"
+
+# fff83eb96ab44a699a972bce5ef45a04
+#: ../../managing_networks.rst:5330
+msgid "Creating a Tier with Custom ACL List"
+msgstr "创建一个具有自定义ACL列表的层。"
+
+# f12e2dba06944099b85dd1ea004364d5
+# e18fc8b196b0486fb6cd03a19e76a01d
+#: ../../managing_networks.rst:5334 ../../managing_networks.rst:5359
+msgid "Create a VPC."
+msgstr "创建一个VPC。"
+
+# 6e0ed40f7fef470a89d1362b855c619d
+# 4a20f18e2e3f41059234087d027679ce
+#: ../../managing_networks.rst:5338 ../../managing_networks.rst:5371
+msgid "Create a custom ACL list."
+msgstr "创建一个自定义ACL列表。"
+
+# b5b4a3b8580a4383b65681e22188b976
+# 54db75d977d64c6d911dbe6f4742e0f2
+#: ../../managing_networks.rst:5342 ../../managing_networks.rst:5375
+msgid "Add ACL rules to the ACL list."
+msgstr "将ACL规则加入ACL列表。"
+
+# e11c0a6e179d4cbab03f5e4df6b0d34c
+# 22398c60ca484e6f95dd827641a3ebbc
+#: ../../managing_networks.rst:5346 ../../managing_networks.rst:5363
+msgid "Create a tier in the VPC."
+msgstr "在VPC里创建一个层。"
+
+# 99892b8596be4b2285f7bb8edfb191a2
+#: ../../managing_networks.rst:5348
+msgid "Select the desired ACL list while creating a tier."
+msgstr "在创建层的过程中选择需要的ACL列表。"
+
+# 2c486359bfd24312a59e5fd1dd7bc71d
+#: ../../managing_networks.rst:5355
+msgid "Assigning a Custom ACL List to a Tier"
+msgstr "将一个自定义的ACL关联到一个层。"
+
+# 05e3fc39d3e94c7f829ec8cb6046bc61
+#: ../../managing_networks.rst:5367
+msgid "Associate the tier with the default ACL rule."
+msgstr "将默认的ACL规则关联到层。"
+
+# 156229b3ab074f9c9a49d3d9c53d6b52
+#: ../../managing_networks.rst:5379
+msgid "Select the tier for which you want to assign the custom ACL."
+msgstr "选中你希望赋予自定义ACL的层。"
+
+# 33c7f407412544c3bd8dc80b0deb4108
+#: ../../managing_networks.rst:5383
+msgid ""
+"Click the Replace ACL List icon. |replace-acl-icon.png: button to replace an"
+" ACL list|"
+msgstr "点击替换ACL图标。|replace-acl-icon.png: button to replace an ACL list|"
+
+# 769a8ffc3b73478994f18f35ad3a4f97
+#: ../../managing_networks.rst:5386
+msgid "The Replace ACL List dialog is displayed."
+msgstr "替换ACL的对话界面将会弹出来。"
+
+# 59b868549d104d3a80e798178bdef667
+#: ../../managing_networks.rst:5397
+msgid "Adding a Private Gateway to a VPC"
+msgstr "在一个VPC里加入私有网关。"
+
+# 67c51696fdc0490ebeaa99b6e4bfc5bd
+#: ../../managing_networks.rst:5399
+msgid ""
+"A private gateway can be added by the root admin only. The VPC private "
+"network has 1:1 relationship with the NIC of the physical network. You can "
+"configure multiple private gateways to a single VPC. No gateways with "
+"duplicated VLAN and IP are allowed in the same data center."
+msgstr "私有网关只能被系统管理员添加。VPC私有网络和物理网络之间是1：1的对应关系。你可以在一个VPC里定义多个私有网关。在同一个数据中心，不允许复制VLAN和IP的网关。"
+
+# d5835ef9009f4c14873cc04a1210faa0
+#: ../../managing_networks.rst:5421
+msgid ""
+"Click the Configure button of the VPC to which you want to configure load "
+"balancing rules."
+msgstr "在你想配置负载均衡的VPC上点击配置按钮。"
+
+# 5efaa5f18c7844a4b06a038676b273df
+# 36ecb777b69f4c269f586a8a44a42c4a
+# 4244a80585044c06abd14959aa47e3f8
+#: ../../managing_networks.rst:5431 ../../managing_networks.rst:5756
+#: ../../managing_networks.rst:5843
+msgid "The following options are displayed."
+msgstr "下面这些选项就会出现。"
+
+# c0a219ae8fd5473d87a77217b9d95417
+#: ../../managing_networks.rst:5473
+msgid "Select Private Gateways."
+msgstr "选择私有网关。"
+
+# 497c5bbf4ce4494b984d67f98954deab
+#: ../../managing_networks.rst:5475
+msgid "The Gateways page is displayed."
+msgstr "网关对话框就会显示出来。"
+
+# cdead55635a740399b023f2897b98f59
+#: ../../managing_networks.rst:5479
+msgid "Click Add new gateway:"
+msgstr "点击添加新网关："
+
+# 6eb77c1dc83c4cfe938dfc899ea6e662
+#: ../../managing_networks.rst:5481
+msgid "|add-new-gateway-vpc.png: adding a private gateway for the VPC.|"
+msgstr "|add-new-gateway-vpc.png: adding a private gateway for the VPC.|"
+
+# afb65eddf4dd4dc182850cdc8514f923
+#: ../../managing_networks.rst:5489
+msgid ""
+"**Physical Network**: The physical network you have created in the zone."
+msgstr "**物理网络**: 此处为你已在区域内建好的物理网络。"
+
+# e7b58bd2dff34b0db44aab8f2c6245b2
+#: ../../managing_networks.rst:5494
+msgid "**IP Address**: The IP address associated with the VPC gateway."
+msgstr "**IP地址**: 关联VPC网关的IP地址。"
+
+# 8129fbaeec504b9b945efb8751c45385
+#: ../../managing_networks.rst:5498
+msgid ""
+"**Gateway**: The gateway through which the traffic is routed to and from the"
+" VPC."
+msgstr "**网关**: 定义进出VPC流量的网关。"
+
+# a4c3555b968349dfa818e2dbdc7c3d53
+#: ../../managing_networks.rst:5503
+msgid "**Netmask**: The netmask associated with the VPC gateway."
+msgstr "**Netmask**: VPC网关的子网掩码。"
+
+# 4dce5e993ebf4265bd2bbb586e92c0f3
+#: ../../managing_networks.rst:5507
+msgid "**VLAN**: The VLAN associated with the VPC gateway."
+msgstr "**VLAN**: VPC网关的VLAN。"
+
+# a5003a0c62a64833880757bd344cfde7
+#: ../../managing_networks.rst:5511
+msgid ""
+"**Source NAT**: Select this option to enable the source NAT service on the "
+"VPC private gateway."
+msgstr "**Source NAT**: 这个选项会启用VPC私有网关的source NAT服务。"
+
+# dff3c56b7ec649b589e8eafd8e54c7cb
+#: ../../managing_networks.rst:5514
+msgid ""
+"See `Section 15.27.5.1, “Source NAT on Private Gateway” <#sourcenat-private-"
+"gateway>`__."
+msgstr "参阅 `章节 15.27.5.1, “专用网关的源NAT” <#sourcenat-private-gateway>`__."
+
+# 1ff567af8cf94d3b84320755c4d26a66
+#: ../../managing_networks.rst:5519
+msgid ""
+"**ACL**: Controls both ingress and egress traffic on a VPC private gateway. "
+"By default, all the traffic is blocked."
+msgstr "**ACL**: 控制VPC私有网关的进出流量，默认情况下，所有流量被阻止。"
+
+# 263e367da63e46a9aa8da7d287bc896f
+#: ../../managing_networks.rst:5522
+msgid ""
+"See `Section 15.27.5.2, “ACL on Private Gateway” <#acl-private-gateway>`__."
+msgstr "参阅 `章节 15.27.5.2, “专用网关的ACL” <#acl-private-gateway>`__."
+
+# 0072a51b25fc4a4aa66d298ded9a2dde
+#: ../../managing_networks.rst:5525
+msgid ""
+"The new gateway appears in the list. You can repeat these steps to add more "
+"gateway for this VPC."
+msgstr "新的网关就会出现在列表中。你可以重复这些步骤为VPC增加更多的网关。"
+
+# 1a944440570641ed8d9890edc77c64c5
+#: ../../managing_networks.rst:5529
+msgid "Source NAT on Private Gateway"
+msgstr "私有网关的Source NAT"
+
+# 43aa869828e5461a8a13530f7a2aa2f7
+#: ../../managing_networks.rst:5531
+msgid ""
+"You might want to deploy multiple VPCs with the same super CIDR and guest "
+"tier CIDR. Therefore, multiple guest VMs from different VPCs can have the "
+"same IPs to reach a enterprise data center through the private gateway. In "
+"such cases, a NAT service need to be configured on the private gateway to "
+"avoid IP conflicts. If Source NAT is enabled, the guest VMs in VPC reaches "
+"the enterprise network via private gateway IP address by using the NAT "
+"service."
+msgstr "你可能希望在同一个超级CIDR和客户层CIDR中部署多个VPC。因此，在一个数据中心，不同VPC中的虚拟机通过私有网络可以拥有相同的IP地址。在这种情况下，就需要在私有网关里配置Source NAT服务以避免IP冲突。如果Source NAT服务启用，VPC中的客户虚拟机使用私有网关IP地址与数据中心其它机器交流。"
+
+# e2714f79ffd947d9bdc572874ffd2c73
+#: ../../managing_networks.rst:5539
+msgid ""
+"The Source NAT service on a private gateway can be enabled while adding the "
+"private gateway. On deletion of a private gateway, source NAT rules specific"
+" to the private gateway are deleted."
+msgstr "Source NAT服务是添加私有网关时启用。如果删除了私有网关，关联到此私有网关的Source NAT规则也会被删除。"
+
+# ee2bf2c268b940968dd021c6ea6bcf74
+#: ../../managing_networks.rst:5543
+msgid ""
+"To enable source NAT on existing private gateways, delete them and create "
+"afresh with source NAT."
+msgstr "如要有已有私有网关中启用Source NAT，需要先删除（私有网关），然后再建一个启用Source NAT的私有网关。"
+
+# 8de7fa9065814573b42b74b294a1179f
+#: ../../managing_networks.rst:5547
+msgid "ACL on Private Gateway"
+msgstr "私有网关的ACL"
+
+# f450e126ceeb4644a55586ad466152c4
+#: ../../managing_networks.rst:5549
+msgid ""
+"The traffic on the VPC private gateway is controlled by creating both "
+"ingress and egress network ACL rules. The ACLs contains both allow and deny "
+"rules. As per the rule, all the ingress traffic to the private gateway "
+"interface and all the egress traffic out from the private gateway interface "
+"are blocked."
+msgstr "VPC私有网关的进出流量是被ACL规则控制的。ACL均包含允许和阻止的规则。在每一条规则中，所有进出私有网关接口的流量是被阻止的。"
+
+# ee6a2bab124748009cd09599eaa13e71
+#: ../../managing_networks.rst:5555
+msgid ""
+"You can change this default behaviour while creating a private gateway. "
+"Alternatively, you can do the following:"
+msgstr "你可以在创建私有网关时，改变这个默认的行为。或者，你也可以按如下方式操作："
+
+# 21f974b13ca54ebdaeac3568315356d1
+# 6a4b79956d78436989546151b5bd0458
+#: ../../managing_networks.rst:5560 ../../managing_networks.rst:5606
+msgid "In a VPC, identify the Private Gateway you want to work with."
+msgstr "在VPC中，验证你想操作的私有网关。"
+
+# b8c1c66de4bf4c979f0479ea431d3df0
+#: ../../managing_networks.rst:5564
+msgid "In the Private Gateway page, do either of the following:"
+msgstr "在私有网关页面，按如下步骤操作："
+
+# 49b0c682192f4b459125d724b4a1b265
+#: ../../managing_networks.rst:5568
+msgid "Use the Quickview. See `3 <#quickview>`__."
+msgstr "使用快速查看视图，参看 `3 <#quickview>`__."
+
+# d4a946a973cc49888562b872780d8601
+#: ../../managing_networks.rst:5572
+msgid "Use the Details tab. See `4 <#details-tab>`__ through ."
+msgstr "使用详细查看栏。参看 `4 <#details-tab>`__ through ."
+
+# 19cbd09f46ab46db8404fda0e23cb619
+#: ../../managing_networks.rst:5576
+msgid ""
+"In the Quickview of the selected Private Gateway, click Replace ACL, select "
+"the ACL rule, then click OK"
+msgstr "在所选择的私有网关的快速查看视图里，点击替换ACL，选中ACL规则，然后点击OK按钮。"
+
+# afeaf13ba42447798385c602c1c688fe
+#: ../../managing_networks.rst:5581
+msgid "Click the IP address of the Private Gateway you want to work with."
+msgstr "点击你需要操作的私有网关的IP地址。"
+
+# 20ba5a3f04344df0a86ab32ad173edd6
+#: ../../managing_networks.rst:5585
+msgid ""
+"In the Detail tab, click the Replace ACL button. |replace-acl-icon.png: "
+"button to replace the default ACL behaviour.|"
+msgstr "在详细查看栏。点击替换ACL按钮。|replace-acl-icon.png: button to replace the default ACL behaviour.|"
+
+# 01e0bd4df2fd4ee4a00bcf20bc341c5d
+#: ../../managing_networks.rst:5588
+msgid "The Replace ACL dialog is displayed."
+msgstr "替换ACL的对话框就会出现。"
+
+# 3f32278673d446f0b2c1b958c13ac401
+#: ../../managing_networks.rst:5592
+msgid "select the ACL rule, then click OK."
+msgstr "选择ACL规则，然后点击OK按钮。"
+
+# ae950e90184a491381c91aaff688aa76
+#: ../../managing_networks.rst:5594
+msgid ""
+"Wait for few seconds. You can see that the new ACL rule is displayed in the "
+"Details page."
+msgstr "稍等片刻。你就会看到新的ACL规则出现在详细页面里了。"
+
+# 4a0dd026907d41858599558136fffe1a
+#: ../../managing_networks.rst:5598
+msgid "Creating a Static Route"
+msgstr "创建一个静态静由。"
+
+# 5033ea030ac64d85b8313ada101574ec
+#: ../../managing_networks.rst:5600
+msgid ""
+"CloudStack enables you to specify routing for the VPN connection you create."
+" You can enter one or CIDR addresses to indicate which traffic is to be "
+"routed back to the gateway."
+msgstr "CloudStack可以让你指定你创建的VPN链接的路由。你可以输入一个或CIDR地址来指定路由返回到网关的具体流量。"
+
+# 1659fdcef3844d84ab74183505608fbb
+#: ../../managing_networks.rst:5610
+msgid ""
+"In the Private Gateway page, click the IP address of the Private Gateway you"
+" want to work with."
+msgstr "在私有网关页面，点击你需要的私有网关的IP地址。"
+
+# f37c03963d3d47d596b85b8e76efbd71
+#: ../../managing_networks.rst:5615
+msgid "Select the Static Routes tab."
+msgstr "选择静态路由栏。"
+
+# aa7e5e9a6f11421abd3b4aadc2e9b32b
+#: ../../managing_networks.rst:5619
+msgid "Specify the CIDR of destination network."
+msgstr "指定目标网络的CIDR。"
+
+# 2b073a139f15411c9cbd0b3f86c913e9
+#: ../../managing_networks.rst:5625
+msgid "Wait for few seconds until the new route is created."
+msgstr "稍等片刻，新的路由就创建好了。"
+
+# 7a2e407277964cd18757e610c1197596
+#: ../../managing_networks.rst:5628
+msgid "Blacklisting Routes"
+msgstr "路由黑名单"
+
+# a154d3d5488f418e95dbd3c0ae59a55f
+#: ../../managing_networks.rst:5630
+msgid ""
+"CloudStack enables you to block a list of routes so that they are not "
+"assigned to any of the VPC private gateways. Specify the list of routes that"
+" you want to blacklist in the ``blacklisted.routes`` global parameter. Note "
+"that the parameter update affects only new static route creations. If you "
+"block an existing static route, it remains intact and continue functioning. "
+"You cannot add a static route if the route is blacklisted for the zone."
+msgstr "CloudStack允许你定义一个路由黑名单，这样它们就不能关联到任何VPC私有网关。你需要在全局参数blacklisted.routes里定义。要注意，此参数只在新路由创建时才会生效。如果你在黑名单里加入了已存在的静态路由，则此静态路由还是会继续起作用。你不能把在路由黑名单里的路由加入到静态路由当中去。"
+
+# 7f1bbdc7458942d88e89b8e0af49db0c
+#: ../../managing_networks.rst:5639
+msgid "Deploying VMs to the Tier"
+msgstr "将虚拟机部署到层。"
+
+# 36fffc19e491403389988483ec7271b0
+#: ../../managing_networks.rst:5661
+msgid ""
+"The VPC page is displayed where all the tiers you have created are listed."
+msgstr "所有创建好的层都会有VPC页面里列出来。"
+
+# 9d8ad54e3d3a46e7b8074cc715920531
+#: ../../managing_networks.rst:5666
+msgid "Click Virtual Machines tab of the tier to which you want to add a VM."
+msgstr "指向你想添加虚拟机的层，点击虚拟机栏。"
+
+# ca8838c20d2845659371f93b881a4100
+#: ../../managing_networks.rst:5668
+msgid "|add-vm-vpc.png: adding a VM to a vpc.|"
+msgstr "|add-vm-vpc.png: adding a VM to a vpc.|"
+
+# e5316d71ef404ddbb0d6dad97ba98577
+#: ../../managing_networks.rst:5670
+msgid "The Add Instance page is displayed."
+msgstr "添加实例的页面就会出现。"
+
+# 389b274de3d2499f942685dd7cd1173e
+#: ../../managing_networks.rst:5672
+msgid ""
+"Follow the on-screen instruction to add an instance. For information on "
+"adding an instance, see the Installation Guide."
+msgstr "按照屏幕所指示的操作加入实例。至于如何添加实例，参照安装指南文档。"
+
+# 9d028d09d4304fb1bf6cca0baa05eb50
+#: ../../managing_networks.rst:5676
+msgid "Deploying VMs to VPC Tier and Shared Networks"
+msgstr "在VPC层中部署虚拟，共享网络。"
+
+# e4ce910a596b41b488b8bf3c9a703ec5
+#: ../../managing_networks.rst:5678
+msgid ""
+"CloudStack allows you deploy VMs on a VPC tier and one or more shared "
+"networks. With this feature, VMs deployed in a multi-tier application can "
+"receive monitoring services via a shared network provided by a service "
+"provider."
+msgstr "CloudStack允许你在VPC层中部署虚拟机和共享网络。有了这个功能，分布在多层当中的虚拟机可以通过共享网络接收到监控服务。"
+
+# 9822028ede334e8d9bcb11d4e0b88a24
+#: ../../managing_networks.rst:5685
+msgid "Log in to the CloudStack UI as an administrator."
+msgstr "用系统管理员登陆到CloudStack UI界面。"
+
+# 334c3d883bcc40f5a9d18da6406e3541
+#: ../../managing_networks.rst:5689
+msgid "In the left navigation, choose Instances."
+msgstr "在左边的导航栏里，选择实例。"
+
+# 9e4739215b6d4023b17334daf1c299d0
+#: ../../managing_networks.rst:5693
+msgid "Click Add Instance."
+msgstr "点击添加实例。"
+
+# f3612ab1c69c4e8bafa16290447c849d
+#: ../../managing_networks.rst:5697
+msgid "Select a zone."
+msgstr "选择一个区域。"
+
+# 0d5257aa0f5d42759682d5ec4c687946
+#: ../../managing_networks.rst:5701
+msgid "Select a template or ISO, then follow the steps in the wizard."
+msgstr "选择一个模板或ISO，按向导步骤操作。 "
+
+# 5d53f3f14de94f21a72a57c5427947fa
+#: ../../managing_networks.rst:5705
+msgid ""
+"Ensure that the hardware you have allows starting the selected service "
+"offering."
+msgstr "请确认你的硬件支持所选择的服务方案。"
+
+# c7211e930aea482ebbbea2e443cabd53
+#: ../../managing_networks.rst:5710
+msgid ""
+"Under Networks, select the desired networks for the VM you are launching."
+msgstr "在网络导航栏，选择你希望虚拟机所在的网络。"
+
+# 355fc2d3a38e43f4ab08b92f9e8f168f
+#: ../../managing_networks.rst:5713
+msgid "You can deploy a VM to a VPC tier and multiple shared networks."
+msgstr "你可以将虚拟机部署在一个拥有多个共享网络的VPC层中。"
+
+# 50da282764bf41938177acb880c846e1
+#: ../../managing_networks.rst:5715
+msgid ""
+"|addvm-tier-sharednw.png: adding a VM to a VPC tier and shared network.|"
+msgstr "|addvm-tier-sharednw.png: adding a VM to a VPC tier and shared network.|"
+
+# 602251fcf69447d880ef52b1e43aaeae
+#: ../../managing_networks.rst:5720
+msgid "Click Next, review the configuration and click Launch."
+msgstr "点击下一步，审看已配置信息，然后点击启动。"
+
+# 7b69703360704281ac542fe8d70b98c6
+#: ../../managing_networks.rst:5722
+msgid "Your VM will be deployed to the selected VPC tier and shared network."
+msgstr "你的这个虚拟机就已被部署到所选择的VPC层和共享网络中。"
+
+# fd34602f4c1a482a8d044b849bdeb44b
+#: ../../managing_networks.rst:5725
+msgid "Acquiring a New IP Address for a VPC"
+msgstr "VPC获取新的IP地址。"
+
+# c73360b50aa543f7a8880e610baa5b75
+#: ../../managing_networks.rst:5727
+msgid ""
+"When you acquire an IP address, all IP addresses are allocated to VPC, not "
+"to the guest networks within the VPC. The IPs are associated to the guest "
+"network only when the first port-forwarding, load balancing, or Static NAT "
+"rule is created for the IP or the network. IP can't be associated to more "
+"than one network at a time."
+msgstr "当获取IP地址时，所有的IP地址会被分配到该VPC，而不是VPC中的用户网络。只有当在IP或用户网络上创建第一个网络规则（端口映射、负载均衡、静态NAT）时，该IP才会关联到用户网络。一个IP不能同时关联一个以上的网络。"
+
+# a44c55b912fa4df183c07b424282c526
+#: ../../managing_networks.rst:5798
+msgid "Select IP Addresses."
+msgstr "选择IP地址。"
+
+# 7068202d5e7748aa89b44e99fd7a8c9b
+#: ../../managing_networks.rst:5800
+msgid "The Public IP Addresses page is displayed."
+msgstr "公网IP地址页面就显示出来。"
+
+# 59806f7394b645268a1deaf02e5c8812
+#: ../../managing_networks.rst:5804
+msgid "Click Acquire New IP, and click Yes in the confirmation dialog."
+msgstr "点击获得一个新IP, 并且在确认的对话框中点击确定."
+
+# 677531dda31f4fe9ba37d4384c2c5672
+#: ../../managing_networks.rst:5806
+msgid ""
+"You are prompted for confirmation because, typically, IP addresses are a "
+"limited resource. Within a few moments, the new IP address should appear "
+"with the state Allocated. You can now use the IP address in port forwarding,"
+" load balancing, and static NAT rules."
+msgstr "因为通常IP地址是有限资源，系统会提示您确认。 在稍等片刻之后，新的IP地址将会出现并且状态是已分配。现在您就可以使用这个IP地址做端口转发、负载均衡或静态NAT。"
+
+# 55e43c565ebb41158b1743d98edb1b7c
+#: ../../managing_networks.rst:5812
+msgid "Releasing an IP Address Allocated to a VPC"
+msgstr "释放VPC分配的IP地址"
+
+# bd70ff0598d34b229b01650cabc35f3f
+#: ../../managing_networks.rst:5814
+msgid ""
+"The IP address is a limited resource. If you no longer need a particular IP,"
+" you can disassociate it from its VPC and return it to the pool of available"
+" addresses. An IP address can be released from its tier, only when all the "
+"networking ( port forwarding, load balancing, or StaticNAT ) rules are "
+"removed for this IP address. The released IP address will still belongs to "
+"the same VPC."
+msgstr "IP地址是有限资源。如果您不再需要某个IP，请解除该IP和VPC的关联，使其返回到可用地址池中。只有当IP上所有的网络规则(端口映射、负载均衡、静态NAT)都删除后，该IP才能从所属层释放。释放的IP仍属于该VPC。"
+
+# db06398461444930b595e0160effde58
+#: ../../managing_networks.rst:5838
+msgid "Click the Configure button of the VPC whose IP you want to release."
+msgstr "点击要释放IP的VPC的配置按钮。"
+
+# d80d6b89f43d4b2491743738838b0245
+#: ../../managing_networks.rst:5885
+msgid "Select Public IP Addresses."
+msgstr "选择公网IP地址。"
+
+# 00cc2e1530394ea2838d7f6061a85693
+#: ../../managing_networks.rst:5891
+msgid "Click the IP you want to release."
+msgstr "点击要释放的IP地址。"
+
+# 15c38333d5564c94a459bd2e93b987b1
+#: ../../managing_networks.rst:5895
+msgid ""
+"In the Details tab, click the Release IP button |release-ip-icon.png: button"
+" to release an IP.|"
+msgstr "在详细查看栏，点击释放IP按钮。 |release-ip-icon.png: button to release an IP.|"
+
+# c6a4439513504b019b9fa932df9926b5
+#: ../../managing_networks.rst:5899
+msgid "Enabling or Disabling Static NAT on a VPC"
+msgstr "VPC中启用或禁用静态NAT"
+
+# 2121940a433d4a7c99fe4fcdc04af8a9
+#: ../../managing_networks.rst:5901
+msgid ""
+"A static NAT rule maps a public IP address to the private IP address of a VM"
+" in a VPC to allow Internet traffic to it. This section tells how to enable "
+"or disable static NAT for a particular IP address in a VPC."
+msgstr "静态NAT规则是将公网IP映射到VPC中虚机的私网IP，以便允许互联网流量访问该虚机。本节描述如何在VPC中启用或禁用某个公网IP地址的静态NAT。"
+
+# 0603bfddfcae43529259bdadc6652cc7
+#: ../../managing_networks.rst:5934
+msgid "For each tier, the following options are displayed."
+msgstr "对于每一个层，会显示以下选项。"
+
+# d9241814450644c28541d121455ddb44
+#: ../../managing_networks.rst:5982
+msgid "Click the IP you want to work with."
+msgstr "点击您要操作的IP。"
+
+# 17ca1f0f3fac45349f2b7536efe21e90
+#: ../../managing_networks.rst:5986
+msgid ""
+"In the Details tab,click the Static NAT button. |enable-disable.png: button "
+"to enable Static NAT.| The button toggles between Enable and Disable, "
+"depending on whether static NAT is currently enabled for the IP address."
+msgstr "在“详细信息”页，点击静态NAT按钮 |enable-disable.png: button to enable Static NAT.| 该按钮会根据公网IP的静态NAT当前状态，在启用和禁用间切换。"
+
+# 48ec391c037d4513bbbf0e36c099fbd4
+#: ../../managing_networks.rst:5993
+msgid "If you are enabling static NAT, a dialog appears as follows:"
+msgstr "如果是启用静态NAT，会显示如下对话框："
+
+# 9e8b3f52b98a4950a87c8525e6c7b27f
+#: ../../managing_networks.rst:5995
+msgid "|select-vmstatic-nat.png: selecting a tier to apply staticNAT.|"
+msgstr "|select-vmstatic-nat.png: selecting a tier to apply staticNAT.|"
+
+# 18f46f5fdcb0449dac6fdfaf2f51ce14
+#: ../../managing_networks.rst:5999
+msgid "Select the tier and the destination VM, then click Apply."
+msgstr "选择层和目标虚机，然后点击“应用”。"
+
+# fb5ca551d8c94e579cd6bb1147727ab7
+#: ../../managing_networks.rst:6002
+msgid "Adding Load Balancing Rules on a VPC"
+msgstr "VPC中添加负载均衡规则"
+
+# c4883c83508d432bb165cab6bc1de860
+#: ../../managing_networks.rst:6004
+msgid ""
+"In a VPC, you can configure two types of load balancing—external LB and "
+"internal LB. External LB is nothing but a LB rule created to redirect the "
+"traffic received at a public IP of the VPC virtual router. The traffic is "
+"load balanced within a tier based on your configuration. Citrix NetScaler "
+"and VPC virtual router are supported for external LB. When you use internal "
+"LB service, traffic received at a tier is load balanced across different VMs"
+" within that tier. For example, traffic reached at Web tier is redirected to"
+" another VM in that tier. External load balancing devices are not supported "
+"for internal LB. The service is provided by a internal LB VM configured on "
+"the target tier."
+msgstr "在VPC中，你可以配置外部或内部负载均衡。外部负载均衡就是将VPC虚拟路由器接收到的公网流量进行转发的规则。这个流量如何在层里进行均衡取决于你的配置。Citrix NetScaler 和 VPC virtual router都支持外部负载均衡。内部均衡是在层内的虚拟之间进行均衡。比如，到达WEB层请求的流量可以转发到此层另外的虚拟机。外部负载均衡设备不支持内部均衡。内部负载均衡的服务是由目标层的内部虚拟机配置后提供支持服务的。"
+
+# 274bc30ffbcf44b9ba1abd732541215a
+#: ../../managing_networks.rst:6016
+msgid "Load Balancing Within a Tier (External LB)"
+msgstr "在层内进行负载均衡(外部负载均衡)"
+
+# caa659885dfa4cd6904a918177c53c5e
+#: ../../managing_networks.rst:6018
+msgid ""
+"A CloudStack user or administrator may create load balancing rules that "
+"balance traffic received at a public IP to one or more VMs that belong to a "
+"network tier that provides load balancing service in a VPC. A user creates a"
+" rule, specifies an algorithm, and assigns the rule to a set of VMs within a"
+" tier."
+msgstr " CloudStack用户或管理员可以创建负载均衡规则。负载均衡规则用于将一个公网IP的流量分担到在VPC提供负载均衡服务的网络层内的一个或多个VM中。用户可以创建规则，指定算法，然后将规则指定到VPC的一套VM中。"
+
+# 5c807fdb6ce04f699eb08495407e8d92
+#: ../../managing_networks.rst:6025
+msgid "Enabling NetScaler as the LB Provider on a VPC Tier"
+msgstr "在VPC层中启用基于NetScaler的负载均衡"
+
+# 9cc8f348801d45418744e7f42218d907
+#: ../../managing_networks.rst:6029
+msgid "Add and enable Netscaler VPX in dedicated mode."
+msgstr "添加并启用 Netscaler VPX独立模块。"
+
+# ed6339be814f45398c36a2ef4ec785d2
+#: ../../managing_networks.rst:6031
+msgid ""
+"Netscaler can be used in a VPC environment only if it is in dedicated mode."
+msgstr "Netscaler只能在独立模块的形式下应用于VPC环境中。"
+
+# 4662e3fb38414b75bdfa2ae89c5b4d54
+#: ../../managing_networks.rst:6036
+msgid ""
+"Create a network offering, as given in `Section 15.27.11.1.2, “Creating a "
+"Network Offering for External LB” <#ext-lb-offering>`__."
+msgstr "创建一个网络方案。参看 `章节 15.27.11.1.2, “为外部LB创建网络方案” <#ext-lb-offering>`__."
+
+# 648bc307e8724c0c808a7e169d7174af
+#: ../../managing_networks.rst:6041
+msgid "Create a VPC with Netscaler as the Public LB provider."
+msgstr "在VPC中创建一个基于Netscaler的公用负载均衡。"
+
+# 6f2968514fa14e198e27a6276559ac66
+#: ../../managing_networks.rst:6043
+msgid ""
+"For more information, see `Section 15.27.2, “Adding a Virtual Private Cloud”"
+" <#add-vpc>`__."
+msgstr "更多信息，参阅 `章节 15.27.2, “添加虚拟专用云” <#add-vpc>`__."
+
+# 34834931a616401fbf2114397a66c17d
+#: ../../managing_networks.rst:6048
+msgid "For the VPC, acquire an IP."
+msgstr "在VPC中获取一个IP地址。"
+
+# 73121096c9c0491b872f089f4bcd646d
+#: ../../managing_networks.rst:6052
+msgid ""
+"Create an external load balancing rule and apply, as given in `Section "
+"15.27.11.1.3, “Creating an External LB Rule” <#ext-lb-vpc>`__."
+msgstr "创建并应用一个外部负载均衡规则。参看 `章节 15.27.11.1.3, “创建外部LB规则” <#ext-lb-vpc>`__."
+
+# 2772e2e5e8bc4ff585c238022e2de08d
+#: ../../managing_networks.rst:6057
+msgid "Creating a Network Offering for External LB"
+msgstr "创建一个外部负载均衡网络方案"
+
+# 9321f241035849579eee2b19a8dcd3a7
+#: ../../managing_networks.rst:6059
+msgid ""
+"To have external LB support on VPC, create a network offering as follows:"
+msgstr "要在VPC中启用外部负载均衡支持，依如下操作建立网络方案："
+
+# 2aab6b8694d14a2d81304515d063ea70
+# 9547796b012c45c0a0bce3e170167fa4
+#: ../../managing_networks.rst:6064 ../../managing_networks.rst:6368
+msgid "Log in to the CloudStack UI as a user or admin."
+msgstr "使用用户或管理员登录到CloudStack用户界面。"
+
+# 98791665f6d04be48656066993e3c5e0
+# 894f16f3b18145cfad928d595039b36a
+#: ../../managing_networks.rst:6068 ../../managing_networks.rst:6372
+msgid "From the Select Offering drop-down, choose Network Offering."
+msgstr "下拉选择方案，选择网络方案："
+
+# a4c57841d2274a45a1949e1ba43a5d78
+# e1065316da8a4206a4c9926b89da3869
+#: ../../managing_networks.rst:6076 ../../managing_networks.rst:6380
+msgid "In the dialog, make the following choices:"
+msgstr "在对话框中，选择如下操作："
+
+# 6a3430b8741e423b83efc13c9e7e6e88
+# 236dc341b9214a589a7e812fd2f4c60b
+#: ../../managing_networks.rst:6080 ../../managing_networks.rst:6384
+msgid "**Name**: Any desired name for the network offering."
+msgstr "**名称**: 任何网络方案的名称。"
+
+# 76031673ac254ec7bfb535779e98ebb4
+# bccec46599994c2a95a0569047967aa7
+#: ../../managing_networks.rst:6084 ../../managing_networks.rst:6388
+msgid ""
+"**Description**: A short description of the offering that can be displayed "
+"to users."
+msgstr "**描述**: 提供一个简短的方案描述。 "
+
+# 2bab7aa63c61409191de6c7949b17cf4
+# 351d020a9f044f52a3dd389bff437e65
+#: ../../managing_networks.rst:6089 ../../managing_networks.rst:6393
+msgid "**Network Rate**: Allowed data transfer rate in MB per second."
+msgstr "**网络速度**: 允许的数据传输速度（MB/秒）。"
+
+# 79ce2fd95ec04bcfa12787a70171f1fb
+# a40a99e105f943e69806fc3e1db63326
+#: ../../managing_networks.rst:6093 ../../managing_networks.rst:6397
+msgid ""
+"**Traffic Type**: The type of network traffic that will be carried on the "
+"network."
+msgstr "**流量类型**: 允许承载的网络流量类型。"
+
+# d6c6b623f9f04f3997c8dbd87ee79e96
+# 0a18bda8137545e392cca4356df398f3
+#: ../../managing_networks.rst:6098 ../../managing_networks.rst:6402
+msgid ""
+"**Guest Type**: Choose whether the guest network is isolated or shared."
+msgstr "**来宾类型**: 选择来宾网络为隔离或共享网络。"
+
+# ca6a4c29a1694890b3c2c8ce9114cac1
+# 89df6c51bfee49629ef336a867cc8a40
+#: ../../managing_networks.rst:6103 ../../managing_networks.rst:6407
+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."
+msgstr "**持续性**: 表明来宾网络是否支持持续性。无需提供任何VM部署的网络，称之为持续性网络。"
+
+# e799f2ee1f1942f1a80c328ac3f22ba2
+# d7d42b1bb3754b0786713cf979e06172
+#: ../../managing_networks.rst:6109 ../../managing_networks.rst:6413
+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 `Section "
+"15.27.1, “About Virtual Private Clouds” <#vpc>`__."
+msgstr "**VPC**: 此选项表明是否在来宾网络中启用VPC。 CloudStack中的虚拟专用云(VPC)是专用、隔离的。 一个VPC可以有一个类似于传统物理网络的虚拟网络拓扑结构。有关的VPC的详细信息，请参阅 `章节 15.27.1, “关于私有专用云” <#vpc>`__."
+
+# c1cb78a9d442425ca2861f09ccb822d0
+# b44e7a69782a468ebc6a1b0b2b58b67a
+#: ../../managing_networks.rst:6118 ../../managing_networks.rst:6422
+msgid ""
+"**Specify VLAN**: (Isolated guest networks only) Indicate whether a VLAN "
+"should be specified when this offering is used."
+msgstr "**指定**: (仅隔离的来宾网络) 表明在使用这个网络方案时，是否指定VLAN。"
+
+# 83f03954d4aa40fcb0269bb949898281
+#: ../../managing_networks.rst:6123
+msgid ""
+"**Supported Services**: Select Load Balancer. Use Netscaler or "
+"VpcVirtualRouter."
+msgstr "**支持服务**:选择负载均衡，使用Netscaler 或 VpcVirtualRouter."
+
+# 3ecd5594fecf4e7996fc00073a3af317
+#: ../../managing_networks.rst:6128
+msgid "**Load Balancer Type**: Select Public LB from the drop-down."
+msgstr "**负载均衡类型**:从下拉列表里选择公用负载均衡。"
+
+# c780a4651b0540c99bc39f9057d781d5
+#: ../../managing_networks.rst:6132
+msgid ""
+"**LB Isolation**: Select Dedicated if Netscaler is used as the external LB "
+"provider."
+msgstr "**负载均衡隔离**: 如果使用Netscale作为外部负载均衡，选择此项进行隔离。"
+
+# 5a521e9e6e424ed8a6e6e8878254fb05
+# 0e1a57030f0e4d1c9f91421d3bfcf073
+#: ../../managing_networks.rst:6137 ../../managing_networks.rst:6436
+msgid ""
+"**System Offering**: Choose the system service offering that you want "
+"virtual routers to use in this network."
+msgstr "**系统方案**: 选择你想在这个网络中使用的虚拟路由器的系统服务方案。"
+
+# 3da1b26048d246e8be963accb23a2d59
+# 303be976fe7a41a0a5a3b299ba7d1cc2
+#: ../../managing_networks.rst:6142 ../../managing_networks.rst:6441
+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."
+msgstr "**保护模式**: 表明是否使用保护模式。在这个模式中，只有网络中第一个虚拟机启动时才分配网络资源。"
+
+# 97f1c8686f464c2a86f667e59bc3613d
+# 21d33f3ed7b842139317fe1ba0d2bad4
+#: ../../managing_networks.rst:6148 ../../managing_networks.rst:6447
+msgid "Click OK and the network offering is created."
+msgstr "点击OK按钮，网络方案就创建好了。"
+
+# b85666bb2b034e90b3623ac0d974bcf8
+#: ../../managing_networks.rst:6151
+msgid "Creating an External LB Rule"
+msgstr "创建一个外部负载均衡规则"
+
+# 46a6c7a9c87b4d0b86e5096cf8387352
+#: ../../managing_networks.rst:6170
+msgid ""
+"Click the Configure button of the VPC, for which you want to configure load "
+"balancing rules."
+msgstr "点击要配置负载均衡规则的VPC的配置按钮。"
+
+# 04979eda5aad402e9e9ed07b06b83d07
+# 29d52ff8bfd845898927bc69c03ba1cc
+#: ../../managing_networks.rst:6173 ../../managing_networks.rst:6481
+msgid ""
+"The VPC page is displayed where all the tiers you created listed in a "
+"diagram."
+msgstr "系统会显示VPC页面，您创建的所有层都列在图中。"
+
+# 841ec4a089094a18a44d829fe3992d40
+# d19cbf96b77b4284b01fe504101489d6
+#: ../../managing_networks.rst:6233 ../../managing_networks.rst:6625
+msgid "Select the tier to which you want to apply the rule."
+msgstr "选择应用规则的层。"
+
+# 7de910c468f6402a8dfb73f99ce85bfa
+#: ../../managing_networks.rst:6245
+msgid ""
+"**Public Port**: The port that receives the incoming traffic to be balanced."
+msgstr "**公网端口**: 接收待负载均衡的流入流量的端口。"
+
+# 0e6242e8303c4f7e81f3bacd632286c4
+# 873adeb9135b4671ac55ba8bb02eefd4
+#: ../../managing_networks.rst:6255 ../../managing_networks.rst:6526
+msgid ""
+"**Algorithm**. Choose the load balancing algorithm you want CloudStack to "
+"use. CloudStack supports the following well-known algorithms:"
+msgstr "**算法**。选择您希望CloudStack 使用的负载均衡算法。CloudStack 支持下列知名的算法："
+
+# 032bda374e3549389055ef99602dbfde
+# 76d0d6a66f964932a632e62d7f72d63a
+#: ../../managing_networks.rst:6265 ../../managing_networks.rst:6536
+msgid "Least connections"
+msgstr "最少连接"
+
+# 0b3a293fff7f42d59c589be7157bf55b
+# a39fd2d8c4994240b02094dbf235ff35
+#: ../../managing_networks.rst:6269 ../../managing_networks.rst:6540
+msgid "Source"
+msgstr "源IP"
+
+# 5ad7247668c740d59840d3cfa7af1ba4
+#: ../../managing_networks.rst:6273
+msgid ""
+"**Stickiness**. (Optional) Click Configure and choose the algorithm for the "
+"stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr "**粘性**. (可选)点击配置，选择粘性策略使用的算法。参见负载均衡规则的粘性会话策略。"
+
+# cf38cdef27f14c3399aa3f98bb975b0e
+#: ../../managing_networks.rst:6279
+msgid ""
+"**Add VMs**: Click Add VMs, then select two or more VMs that will divide the"
+" load of incoming traffic, and click Apply."
+msgstr "点击添加VM，选择两个或更多的VM分担流入的流量，然后点击应用。"
+
+# 3125a1633b73432dbbc695b80203f711
+#: ../../managing_networks.rst:6282
+msgid ""
+"The new load balancing rule appears in the list. You can repeat these steps "
+"to add more load balancing rules for this IP address."
+msgstr "新的负载均衡策略会显示在列表中。您可以重复以上步骤为该IP地址添加更多的负载均衡策略。"
+
+# 5cd14774a90e437eb620b313651c9e46
+#: ../../managing_networks.rst:6286
+msgid "Load Balancing Across Tiers"
+msgstr "跨越层的负载均衡"
+
+# 070e7b9f10a44c47953a80c046d9c7ca
+#: ../../managing_networks.rst:6288
+msgid ""
+"CloudStack supports sharing workload across different tiers within your VPC."
+" Assume that multiple tiers are set up in your environment, such as Web tier"
+" and Application tier. Traffic to each tier is balanced on the VPC virtual "
+"router on the public side, as explained in `Section 15.27.11, “Adding Load "
+"Balancing Rules on a VPC” <#add-loadbalancer-rule-vpc>`__. If you want the "
+"traffic coming from the Web tier to the Application tier to be balanced, use"
+" the internal load balancing feature offered by CloudStack."
+msgstr "CloudStack支持在VPC内不同层之间共享工作负载。这需要先在你的环境里设置好多个层，比如WEB层，应用层。每一个层的流量通过VPC虚拟路由机进行负载均衡。关于这方面的内容，参看 `章节 15.27.11, “在VPC上添加负载均衡规则” <#add-loadbalancer-rule-vpc>`__. 如果你想将WEB层发向应用层的流量进行负载均衡，需要使用Cloudstack的内部负载均衡功能。"
+
+# aea9258cc6164c4fb587a9e5d2abc852
+#: ../../managing_networks.rst:6298
+msgid "How Does Internal LB Work in VPC?"
+msgstr "在VPC中，内部负载均衡是如何工作的呢？"
+
+# b574228e607e400d88167d7478911df8
+#: ../../managing_networks.rst:6300
+msgid ""
+"In this figure, a public LB rule is created for the public IP 72.52.125.10 "
+"with public port 80 and private port 81. The LB rule, created on the VPC "
+"virtual router, is applied on the traffic coming from the Internet to the "
+"VMs on the Web tier. On the Application tier two internal load balancing "
+"rules are created. An internal LB rule for the guest IP 10.10.10.4 with load"
+" balancer port 23 and instance port 25 is configured on the VM, "
+"InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.4 with "
+"load balancer port 45 and instance port 46 is configured on the VM, "
+"InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.6, with "
+"load balancer port 23 and instance port 25 is configured on the VM, "
+"InternalLBVM2."
+msgstr "在这个图中，公网负载均衡规则是这样创建的：公网IP为IP 72.52.125.10，外网端口为80，内网端口为81。VPC的虚拟路由机创建的负载均衡规则将互联网的流量分配到WEB层的各个虚拟机上。在应用层创建了两个内部负载均衡规则。其中一个规则是：客户IP为10.10.10.4的将端口23进行负载分发，实例VM和InternalLBVM1的端口25进行了负载。另一条规则是：客户IP为10.10.10.4的将端口45进行负载分发，实例VM和InternalLBVM1的端口46进行了负载。另一条规则是：客户IP为10.10.10.6的将端口23进行负载分发，实例VM和InternalLBVM1的端口25进行了负载。（两条规则还是三条规则？原文如此，希望图示能明解）"
+
+# b20f10f2b7d3416f912f26288b95da11
+#: ../../managing_networks.rst:6312
+msgid "|vpc-lb.png: Configuring internal LB for VPC|"
+msgstr "|vpc-lb.png: Configuring internal LB for VPC|"
+
+# 6e79c970118d4190bf7d22c1773505ce
+#: ../../managing_networks.rst:6319
+msgid ""
+"Internal LB and Public LB are mutually exclusive on a tier. If the tier has "
+"LB on the public side, then it can't have the Internal LB."
+msgstr "内部和公网负载均衡在一个层里往往是互斥的。如果一个层已应用了公网负载均衡之后，此层就不能再应用内部负载均衡。"
+
+# 9cf6652ac2e0445387349beb374bfca7
+#: ../../managing_networks.rst:6324
+msgid ""
+"Internal LB is supported just on VPC networks in CloudStack 4.2 release."
+msgstr "在 CloudStack 4.2版本中，只有VPC网络支持内部负载均衡。"
+
+# a3f5f1fc49464829adf0ebd8e7687692
+#: ../../managing_networks.rst:6329
+msgid ""
+"Only Internal LB VM can act as the Internal LB provider in CloudStack 4.2 "
+"release."
+msgstr "在CloudStack 4.2 版本中，只有Internal LB VM才能作内部负载均衡的提供方。"
+
+# c91dbb4b255c4a84be104b33811e5332
+#: ../../managing_networks.rst:6334
+msgid ""
+"Network upgrade is not supported from the network offering with Internal LB "
+"to the network offering with Public LB."
+msgstr "将网络方案由内部负载均衡更改为公网负载均衡是不可行的。"
+
+# b60834349ed648d8a4366ebd00a7fd65
+#: ../../managing_networks.rst:6339
+msgid "Multiple tiers can have internal LB support in a VPC."
+msgstr "在VPC中，多层可以应用内部负载均衡。"
+
+# 4fab50597d0941108a4d3bf7f13e9411
+#: ../../managing_networks.rst:6343
+msgid "Only one tier can have Public LB support in a VPC."
+msgstr "在VPC中，只有一层只支持公网负载均衡。"
+
+# d225db5293e846a0afd0f6c7bb5f68a1
+#: ../../managing_networks.rst:6346
+msgid "Enabling Internal LB on a VPC Tier"
+msgstr "在VPC层上启用内部负载均衡功能"
+
+# 617e9425a2fa474b9764128b07034002
+#: ../../managing_networks.rst:6350
+msgid ""
+"Create a network offering, as given in `Section 15.27.11.2.5, “Creating an "
+"Internal LB Rule” <#int-lb-vpc>`__."
+msgstr "创建一个网络方案。参看 `章节 15.27.11.2.5, “创建内部LB规则 <#int-lb-vpc>`__."
+
+# a890050072ca4d26805f98387f27bd75
+#: ../../managing_networks.rst:6355
+msgid ""
+"Create an internal load balancing rule and apply, as given in `Section "
+"15.27.11.2.5, “Creating an Internal LB Rule” <#int-lb-vpc>`__."
+msgstr "创建并应用一个外部负载均衡规则。参看 `章节 15.27.11.2.5, “创建内部LB规则” <#int-lb-vpc>`__."
+
+# a4cfada862734f0f851fce215590886e
+#: ../../managing_networks.rst:6360
+msgid "Creating a Network Offering for Internal LB"
+msgstr "创建一个内部负载均衡网络方案"
+
+# 60f76aac53194ec8bbe6de7b8c5a5554
+#: ../../managing_networks.rst:6362
+msgid ""
+"To have internal LB support on VPC, either use the default offering, "
+"DefaultIsolatedNetworkOfferingForVpcNetworksWithInternalLB, or create a "
+"network offering as follows:"
+msgstr "要在VPC当中使用内部负载均衡，可以使用默认的DefaultIsolatedNetworkOfferingForVpcNetworksWithInternalLB,或按如下操作新建一个网络方案："
+
+# 8a5ea6ec925d452a879ceac5445ab579
+#: ../../managing_networks.rst:6427
+msgid ""
+"**Supported Services**: Select Load Balancer. Select ``InternalLbVM`` from "
+"the provider list."
+msgstr "**支持服务**: 选择负载均衡，从待提供的下拉列表里选择`InternalLbVM。"
+
+# c72558354623450a936ce31431ffa69e
+#: ../../managing_networks.rst:6432
+msgid "**Load Balancer Type**: Select Internal LB from the drop-down."
+msgstr "**负载均衡类型**: 从下拉列表里选择内部负载均衡。"
+
+# 28147ce50bf14231a07cac69826f2a25
+#: ../../managing_networks.rst:6450
+msgid "Creating an Internal LB Rule"
+msgstr "创建一个内部负载均衡规则"
+
+# 2c9c4cae286845808fef134063a6f939
+#: ../../managing_networks.rst:6452
+msgid ""
+"When you create the Internal LB rule and applies to a VM, an Internal LB VM,"
+" which is responsible for load balancing, is created."
+msgstr "当你创建好一个内部负载均衡规则，并将之用于一个虚拟之后，一个内部负载均衡的应用就建立起来了。"
+
+# 63b7d6ada9114e90ba29443004bc739f
+#: ../../managing_networks.rst:6455
+msgid ""
+"You can view the created Internal LB VM in the Instances page if you "
+"navigate to **Infrastructure** > **Zones** > <zone\\_ name> > "
+"<physical\\_network\\_name> > **Network Service Providers** > **Internal LB "
+"VM**. You can manage the Internal LB VMs as and when required from the "
+"location."
+msgstr "你可以在实例页面中查看创建的内部LB VM 按如下导航 **基础构架** > **区域** > <zone\\_ name> > <physical\\_network\\_name> > **网络服务提供** > **内部负载均衡虚拟机**，你就可以看到已创建了内部负载均衡的实例上。也可以在此进行内部负载均衡的管理。"
+
+# d533cda5982f42a2be99e3d3a1d02796
+#: ../../managing_networks.rst:6478
+msgid ""
+"Locate the VPC for which you want to configure internal LB, then click "
+"Configure."
+msgstr "点击要配置内部负载均衡规则的VPC的配置按钮。"
+
+# e737073d23cf4d26aed7c10ce7b46e81
+#: ../../managing_networks.rst:6486
+msgid ""
+"Locate the Tier for which you want to configure an internal LB rule, click "
+"Internal LB."
+msgstr "指向你想配置内部负载均衡的层，点击内部负载均衡。"
+
+# 552b8f17dcde42d482e1831b58d076ef
+#: ../../managing_networks.rst:6489
+msgid "In the Internal LB page, click Add Internal LB."
+msgstr "在 Internal LB页面里，点击添加 Internal LB。"
+
+# 9e377cd375c349e58911fc49edfdd4b1
+#: ../../managing_networks.rst:6493
+msgid "In the dialog, specify the following:"
+msgstr "在对话框里，定义以下内容："
+
+# 87c629929ba84d5da539e7534a89a8d8
+#: ../../managing_networks.rst:6501
+msgid ""
+"**Description**: A short description of the rule that can be displayed to "
+"users."
+msgstr "**描述**: 提供一个简短的规则描述。 "
+
+# 1827d569d2af4a3eb0a577bec4c3e5eb
+#: ../../managing_networks.rst:6506
+msgid ""
+"**Source IP Address**: (Optional) The source IP from which traffic "
+"originates. The IP is acquired from the CIDR of that particular tier on "
+"which you want to create the Internal LB rule. If not specified, the IP "
+"address is automatically allocated from the network CIDR."
+msgstr "**源IP地址**: (可选) 是指产生流量的源IP地址。这个地址是从你创建内部负载均衡的层中的CIDR中获取的。如果没有指定，则系统会自动从CIDR中分配。"
+
+# 4258284b90204dc997577baaaf8755b6
+#: ../../managing_networks.rst:6512
+msgid ""
+"For every Source IP, a new Internal LB VM is created for load balancing."
+msgstr "对于每一个源IP地址，都可以建立一个针对它的内部负载均衡。"
+
+# e1da6c68ece14aacb7290072c2e1017e
+#: ../../managing_networks.rst:6517
+msgid ""
+"**Source Port**: The port associated with the source IP. Traffic on this "
+"port is load balanced."
+msgstr "**源端口**: 与源IP地址关联的端口，此端口上的流量是基于负载均衡的。"
+
+# afdf2a4f86134a9c8f2ee0d103fb268e
+#: ../../managing_networks.rst:6522
+msgid "**Instance Port**: The port of the internal LB VM."
+msgstr "**实例端口**: 内部负载均衡虚拟机的端口。"
+
+# 1bdef81fe9294cffb07d59cdeaf608a9
+#: ../../managing_networks.rst:6543
+msgid "Adding a Port Forwarding Rule on a VPC"
+msgstr "在VPC里添加一个端口转发规则。"
+
+# 55d5f9cc7a9440d4be42f12599487ff9
+#: ../../managing_networks.rst:6633
+msgid ""
+"**Public Port**: The port to which public traffic will be addressed on the "
+"IP address you acquired in the previous step."
+msgstr "**公用端口**: 你在前面操作所获取的供公共流量使用的公用IP地址的端口。 "
+
+# f3534c50573843559923c45aa9402af1
+#: ../../managing_networks.rst:6638
+msgid ""
+"**Private Port**: The port on which the instance is listening for forwarded "
+"public traffic."
+msgstr "**私有端口**: 虚拟机实例将被转发到公共流量的监听端口。"
+
+# d970ed9b90c54a74871fab0e0bb4667b
+#: ../../managing_networks.rst:6643
+msgid "**Protocol**: The communication protocol in use between the two ports."
+msgstr "**Protocol**: 两个端口之间所用的互联协议。"
+
+# f0be0d19f4464861827239d149e03744
+#: ../../managing_networks.rst:6648
+msgid "TCP"
+msgstr "TCP"
+
+# 931118f56d6d4e2eb86fa29ac132f2b8
+#: ../../managing_networks.rst:6652
+msgid "UDP"
+msgstr "UDP"
+
+# 6d26f66d36a743d4a1a5505df83da34c
+#: ../../managing_networks.rst:6656
+msgid ""
+"**Add VM**: Click Add VM. Select the name of the instance to which this rule"
+" applies, and click Apply."
+msgstr "**Add VM**: 点击增加虚拟机，选择你想将此规则应用上的虚拟机，点击应用。"
+
+# 7eb1b2ffd2df41879c5e85c5c75e60f0
+#: ../../managing_networks.rst:6659
+msgid "You can test the rule by opening an SSH session to the instance."
+msgstr "你可以通过SSH连接实例来测试此规则。"
+
+# 2517c53c112c475089bf9a0e6ece949d
+#: ../../managing_networks.rst:6662
+msgid "Removing Tiers"
+msgstr "删除层"
+
+# 987463aa0c9e46e58456fd870cbac52b
+#: ../../managing_networks.rst:6664
+msgid ""
+"You can remove a tier from a VPC. A removed tier cannot be revoked. When a "
+"tier is removed, only the resources of the tier are expunged. All the "
+"network rules (port forwarding, load balancing and staticNAT) and the IP "
+"addresses associated to the tier are removed. The IP address still be "
+"belonging to the same VPC."
+msgstr "你可以从一个VPC中删除一个层。一个被删除的层是不能被擦除的。当一个层被删除后，只有层的资源被删去。所有的网络规则(端口转发，负载均衡，静态NAT)还有关联到此层的IP地址都会删除。但这些IP地址仍然属于这个VPC。"
+
+# b80a7f96c5e343be988091f48cdc8b13
+#: ../../managing_networks.rst:6690
+msgid ""
+"The Configure VPC page is displayed. Locate the tier you want to work with."
+msgstr "配置VPC的页面显示出来了。指向你需要操作的层。"
+
+# 9d1e0efdd66c408c8b6445ab9ed8f0fa
+#: ../../managing_networks.rst:6695
+msgid "Select the tier you want to remove."
+msgstr "选择你想删除的层。"
+
+# 26cd655882384fdc86510166d3a09cc7
+#: ../../managing_networks.rst:6699
+msgid ""
+"In the Network Details tab, click the Delete Network button. |del-tier.png: "
+"button to remove a tier|"
+msgstr "在网络详细栏，点击删除网络按钮。|del-tier.png: button to remove a tier|"
+
+# dc7484d918fd4185a123c12baf9d26af
+#: ../../managing_networks.rst:6702
+msgid "Click Yes to confirm. Wait for some time for the tier to be removed."
+msgstr "点击YES按钮。稍等片片刻，层就会被删除了。"
+
+# b2b2fa6f474c4923b101aff8c6ebd2ae
+#: ../../managing_networks.rst:6705
+msgid "Editing, Restarting, and Removing a Virtual Private Cloud"
+msgstr "编辑，重启，删除VPC。"
+
+# df6ef06698254b2398ed91a15c14dd60
+#: ../../managing_networks.rst:6707
+msgid "Ensure that all the tiers are removed before you remove a VPC."
+msgstr "在删除VPC前，需要先删除所有的层。"
+
+# 27e727fcb09c499cb04cfeb2bd8af5d2
+#: ../../managing_networks.rst:6726
+msgid "Select the VPC you want to work with."
+msgstr "选择你需要的VPC。"
+
+# 896f44f41d94483ba83091028938b4b9
+#: ../../managing_networks.rst:6730
+msgid ""
+"In the Details tab, click the Remove VPC button |remove-vpc.png: button to "
+"remove a VPC|"
+msgstr "在详细栏，点击删除VPC按钮。|remove-vpc.png: button to remove a VPC|"
+
+# c4dc55536b3041f181e37a5bb1952109
+#: ../../managing_networks.rst:6733
+msgid ""
+"You can remove the VPC by also using the remove button in the Quick View."
+msgstr "你也可以在快速查看视图里点击删除按钮进行VPC的删除。"
+
+# f6bc412f03bc4dc6a55f90047bdec537
+#: ../../managing_networks.rst:6736
+msgid ""
+"You can edit the name and description of a VPC. To do that, select the VPC, "
+"then click the Edit button. |edit-icon.png: button to edit a VPC|"
+msgstr "您可以编辑VPC的名称和描述。选择VPC，然后点击编辑按钮。|edit-icon.png: button to edit a VPC|"
+
+# 63357afed0464e21be6f8fa41abd0ec8
+#: ../../managing_networks.rst:6740
+msgid ""
+"To restart a VPC, select the VPC, then click the Restart button. |restart-"
+"vpc.png: button to restart a VPC|"
+msgstr "如果要重启一个VPC，点击重启按钮。|restart-vpc.png: button to restart a VPC|"
+
+# 39039829f65e4377a122bf91feb35ada
+#: ../../managing_networks.rst:6744
+msgid "Persistent Networks"
+msgstr "持久化网络"
+
+# fca381dc00a94a72af9e6fd527b20d45
+#: ../../managing_networks.rst:6746
+msgid ""
+"The network that you can provision without having to deploy any VMs on it is"
+" called a persistent network. A persistent network can be part of a VPC or a"
+" non-VPC environment."
+msgstr "在不部署任何VM的情况下就初始化好的网络称为持久化网络。持久化网络可以是VPC的一部分，也可以不是。"
+
+# 42c10e563fed417980600322954b333d
+#: ../../managing_networks.rst:6750
+msgid ""
+"When you create other types of network, a network is only a database entry "
+"until the first VM is created on that network. When the first VM is created,"
+" a VLAN ID is assigned and the network is provisioned. Also, when the last "
+"VM is destroyed, the VLAN ID is released and the network is no longer "
+"available. With the addition of persistent network, you will have the "
+"ability to create a network in CloudStack in which physical devices can be "
+"deployed without having to run any VMs. Additionally, you can deploy "
+"physical devices on that network."
+msgstr "在您创建其它类型的网络时，在网络中第一台VM创建之前，该网络仅是数据库的一条记录。当第一个VM创建时，网络会指定一个VLAN ID并初始化。同样，当网络中最后一个VM销毁后，VLAN ID会被释放，这样该网络就不再可用。通过使用持久化网络，您就有能力在不部署VM的情况下在&PRODUCT;中创建一个网络用来部署物理设备。而且，您可以在该网络中部署物理设备。"
+
+# 66f7d3c48a604609a402136b8672bae5
+#: ../../managing_networks.rst:6759
+msgid ""
+"One of the advantages of having a persistent network is that you can create "
+"a VPC with a tier consisting of only physical devices. For example, you "
+"might create a VPC for a three-tier application, deploy VMs for Web and "
+"Application tier, and use physical machines for the Database tier. Another "
+"use case is that if you are providing services by using physical hardware, "
+"you can define the network as persistent and therefore even if all its VMs "
+"are destroyed the services will not be discontinued."
+msgstr "使用持久化网络的一个优点是您可以创建具有一个只包含物理设备的层的VPC。例如，您可以为一个三层应用创建一个VPC，在Web层和应用层部署VM，在数据库层使用物理机器。另一个使用场景为如果您使用物理硬件提供网络服务，您可以定义网络为持久化的。这样即便网络中所有VM都销毁了，服务还可以继续提供。"
+
+# c24813594b9c47c386a450613b070d37
+#: ../../managing_networks.rst:6769
+msgid "Persistent Network Considerations"
+msgstr "持久化网络的考虑事项"
+
+# 9a171e4d62114e3c88fc9881e6a4e32d
+#: ../../managing_networks.rst:6773
+msgid "Persistent network is designed for isolated networks."
+msgstr "Persistent网络是为隔离网络而设计的。"
+
+# f090f131150f456ab0942566d94a17df
+#: ../../managing_networks.rst:6777
+msgid "All default network offerings are non-persistent."
+msgstr "所有默认网络方案都不是持久化的。"
+
+# c8335c59614a4bd0ae9163104533304a
+#: ../../managing_networks.rst:6781
+msgid ""
+"A network offering cannot be editable because changing it affects the "
+"behavior of the existing networks that were created using this network "
+"offering."
+msgstr "网络方案的持久化选项不可编辑。因为修改该选项会影响使用该网络方案创建的已有网络的行为。"
+
+# 23af8e44c8e84feeb39a085848e5709b
+#: ../../managing_networks.rst:6787
+msgid ""
+"When you create a guest network, the network offering that you select "
+"defines the network persistence. This in turn depends on whether persistent "
+"network is enabled in the selected network offering."
+msgstr "当您创建客户网络时，您选择的网络方案定义了该网络的持久化。反过来，这依赖于选择的网络方案是否启用持久化网络。"
+
+# ab1ccf831ef74353bde8bfb88e0155ad
+#: ../../managing_networks.rst:6793
+msgid ""
+"An existing network can be made persistent by changing its network offering "
+"to an offering that has the Persistent option enabled. While setting this "
+"property, even if the network has no running VMs, the network is "
+"provisioned."
+msgstr "通过修改使用的网络方案为启用持久化的方案，现有网络可以变为持久化。在设置该属性时，即便网络中没有运行的VM，该网络也会初始化。"
+
+# e7bb232da8854652a63fa39c268cc893
+#: ../../managing_networks.rst:6800
+msgid ""
+"An existing network can be made non-persistent by changing its network "
+"offering to an offering that has the Persistent option disabled. If the "
+"network has no running VMs, during the next network garbage collection run "
+"the network is shut down."
+msgstr "通过修改使用的网络方案为禁用持久化的方案，现有网络可以变为非持久化。如果网络中没有运行的VM，在下次网络垃圾回收运行时，该网络会被关闭。"
+
+# 02f9973b78fc4f4ea2dbc33c7740fb9f
+#: ../../managing_networks.rst:6807
+msgid ""
+"When the last VM on a network is destroyed, the network garbage collector "
+"checks if the network offering associated with the network is persistent, "
+"and shuts down the network only if it is non-persistent."
+msgstr "当网络中最后一台VM销毁时，网络垃圾回收器会检查该网络的网络方案是否为持久化，若不是持久化，则会关闭网络。"
+
+# fb3cf96c3ec041969d55371e0aaa1d81
+#: ../../managing_networks.rst:6813
+msgid "Creating a Persistent Guest Network"
+msgstr "创建一个Persistent客户网络"
+
+# 19e73163820243d4a6f7fffe91f8ccb3
+#: ../../managing_networks.rst:6815
+msgid "To create a persistent network, perform the following:"
+msgstr "要创建一个Persistent网络，请按如下操作："
+
+# da4bbbbdbd5a46bc9d3cdb51651cf4c1
+#: ../../managing_networks.rst:6819
+msgid "Create a network offering with the Persistent option enabled."
+msgstr "创建一个Persistent选项启用的网络方案。"
+
+# 7036ba30ea924150937e15be22167fde
+#: ../../managing_networks.rst:6821
+msgid "See the Administration Guide."
+msgstr "查看管理指南文档。"
+
+# b531eda7832a4473af382ed8bb02ff2d
+#: ../../managing_networks.rst:6825
+msgid "Select Network from the left navigation pane."
+msgstr "从左边的导航栏里选择网络。"
+
+# acc08af60a1540af83325f8d84777285
+#: ../../managing_networks.rst:6829
+msgid ""
+"Select the guest network that you want to offer this network service to."
+msgstr "选择你希望提供此网络方案服务的客户网络。"
+
+# f91ae55836074e878e10c2eb152ec6d4
+#: ../../managing_networks.rst:6834
+msgid "Click the Edit button."
+msgstr "点击编辑按钮。"
+
+# 41ffae74d3724190b34bc30fda773ff0
+#: ../../managing_networks.rst:6838
+msgid ""
+"From the Network Offering drop-down, select the persistent network offering "
+"you have just created."
+msgstr "在网络方案下拉列表里，选择你刚才创建的persistent网络方案。"
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/network_setup.mo b/source/installguide/locale/zh_CN/LC_MESSAGES/network_setup.mo
new file mode 100644
index 0000000..62eeffe
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/network_setup.mo
Binary files differ
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/network_setup.po b/source/installguide/locale/zh_CN/LC_MESSAGES/network_setup.po
new file mode 100644
index 0000000..e2de713
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/network_setup.po
@@ -0,0 +1,2041 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: 2014-06-30 10:24+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 204e7166d7584bc8800c10730331b91a
+#: ../../network_setup.rst:18
+msgid "Network Setup"
+msgstr "网络设置"
+
+# 28fd3f07600a446f8025a77d2f76f083
+#: ../../network_setup.rst:20
+msgid ""
+"Achieving the correct networking setup is crucial to a successful CloudStack"
+" installation. This section contains information to help you make decisions "
+"and follow the right procedures to get your network set up correctly."
+msgstr "正确的网络设置对于CloudStack能否成功安装至关重要。遵循本节包含的信息，指导你搭建正确的网络配置。"
+
+# 0f171b003d40415f9683899a68f68949
+#: ../../network_setup.rst:27
+msgid "Basic and Advanced Networking"
+msgstr "基本和高级网络"
+
+# 188908473c3948279ecec71280711a3b
+#: ../../network_setup.rst:29
+msgid "CloudStack provides two styles of networking:."
+msgstr "CloudStack提供二种网络类型："
+
+# d972c75e48ba46ce8b2fd29ba7a548fc
+#: ../../network_setup.rst:31
+msgid ""
+"**Basic** For AWS-style networking. Provides a single network where guest "
+"isolation can be provided through layer-3 means such as security groups (IP "
+"address source filtering)."
+msgstr ""
+
+# 286b58108d5240ab81545392b60577c5
+#: ../../network_setup.rst:36
+msgid ""
+"**Advanced** For more sophisticated network topologies. This network model "
+"provides the most flexibility in defining guest networks, but requires more "
+"configuration steps than basic networking."
+msgstr ""
+
+# ef43036726e14dd092edbbe912848db5
+#: ../../network_setup.rst:41
+msgid ""
+"Each zone has either basic or advanced networking. Once the choice of "
+"networking model for a zone has been made and configured in CloudStack, it "
+"can not be changed. A zone is either basic or advanced for its entire "
+"lifetime."
+msgstr "每个区域都有基本或高级网络。一个区域的整个生命周期中，不论是基本或高级网络。一旦在CloudStack中选择并配置区域的网络类型，就无法再修改。"
+
+# edec4755035e4f65bc0313e508fef22c
+#: ../../network_setup.rst:46
+msgid ""
+"The following table compares the networking features in the two networking "
+"models."
+msgstr "下表比较了两种网络类型的功能"
+
+# 1931f079dbf54009a09b730d78cea8ae
+#: ../../network_setup.rst:49
+msgid "Networking Feature"
+msgstr "网络功能"
+
+# ddb5e29a533944e79cfacd651a55de04
+#: ../../network_setup.rst:49
+msgid "Basic Network"
+msgstr "基本网络"
+
+# 5e5d2126f2b342099f984864fe91699a
+#: ../../network_setup.rst:49
+msgid "Advanced Network"
+msgstr "高级网络"
+
+# 2e392d44156a42619a81a1004ebe92a6
+#: ../../network_setup.rst:51
+msgid "Number of networks"
+msgstr "网络数量"
+
+# 2c57c568f79e4abf9d0b9731eb3ea05b
+#: ../../network_setup.rst:51
+msgid "Single network"
+msgstr "单一网络"
+
+# a0c94e5edb364dc590ac47ed8a4a9104
+#: ../../network_setup.rst:51
+msgid "Multiple networks"
+msgstr "多种网络"
+
+# 15454f7e603b41a4bc4e11f248e4988f
+#: ../../network_setup.rst:52
+msgid "Firewall type"
+msgstr "防火墙类型"
+
+# 0f306c3ed8cc40a7b2a90c79c2bc1b21
+# 08a635b95c484902a4c8d6739599e242
+# a9d431ac26934dc0b50f9d2fb90e1057
+# 48d78bd1b5fc4a06b4f3d035a5c93188
+#: ../../network_setup.rst:52 ../../network_setup.rst:53
+#: ../../network_setup.rst:56 ../../network_setup.rst:57
+msgid "Physical"
+msgstr "物理"
+
+# 54c51460b59b4787a77fe987aff804e0
+# bf584ce2c901485f917ebdf80d512db2
+# fda7d50fe9df495aa57dc3a69b89ce53
+# 4bcf67ddb65b49cc92e25d48cbeeb7aa
+# 0739b5b91ac0446d977a4641dfcc846e
+#: ../../network_setup.rst:52 ../../network_setup.rst:53
+#: ../../network_setup.rst:56 ../../network_setup.rst:57
+#: ../../network_setup.rst:58
+msgid "Physical and Virtual"
+msgstr "物理和虚拟"
+
+# 483cde5d650e412799b4b3d95c1a34ff
+#: ../../network_setup.rst:53
+msgid "Load balancer"
+msgstr "负载均衡"
+
+# 824040016a8e47958d1e7900b0c5bc8f
+#: ../../network_setup.rst:54
+msgid "Isolation type"
+msgstr "隔离类型"
+
+# eb2562a54a6f41439d2c95bcbe8e93f7
+#: ../../network_setup.rst:54
+msgid "Layer 3"
+msgstr "三层"
+
+# 8c4ff876b9af4e23a60a18477d9ad2ac
+#: ../../network_setup.rst:54
+msgid "Layer 2 and Layer 3"
+msgstr "二层和三层"
+
+# 272f31b097a6419b9657d410bc613b29
+#: ../../network_setup.rst:55
+msgid "VPN support"
+msgstr "VPN支持"
+
+# be705df006104fc981cd11ab21dbee41
+# 77c761df6e424c5eaa8fd876956f2fd4
+# 89111394bc904a6688140d3a45239729
+#: ../../network_setup.rst:55 ../../network_setup.rst:58
+#: ../../network_setup.rst:855
+msgid "No"
+msgstr "否"
+
+# 87c00040e2b94a5fb1354724a796ad4e
+# c1bcbed263544b8ba2804541e77b986c
+# 2f87b4b5d55248b68a742abdfcac7411
+# f0fa47c28e75441f8ef8397b8c693fb5
+# 6987985d2d78451b9146580fa5ec7197
+# c235fbc31a63448c9b960c7ccc3745d4
+# f454f4d643734a6283ed71f976c4e65e
+#: ../../network_setup.rst:55 ../../network_setup.rst:59
+#: ../../network_setup.rst:59 ../../network_setup.rst:61
+#: ../../network_setup.rst:61 ../../network_setup.rst:853
+#: ../../network_setup.rst:854
+msgid "Yes"
+msgstr "是"
+
+# cde208e3641549ac9fe8b53a042abd65
+#: ../../network_setup.rst:56
+msgid "Port forwarding"
+msgstr "端口转发"
+
+# 33d5935021cd4f3ab6e723b0921e6945
+#: ../../network_setup.rst:57
+msgid "1:1 NAT"
+msgstr "1:1 NAT"
+
+# 435097d06513454a921a6170741111bb
+#: ../../network_setup.rst:58
+msgid "Source NAT"
+msgstr "Source NAT"
+
+# 4546413386114726ad887ab1acfc1cba
+#: ../../network_setup.rst:59
+msgid "Userdata"
+msgstr "用户数据"
+
+# e6a6cb39df554d4d8490722bb831ef65
+#: ../../network_setup.rst:60
+msgid "Network usage monitoring"
+msgstr "网络监控"
+
+# cb68ceaa47fb447d915faa6dc794d39f
+#: ../../network_setup.rst:60
+msgid "sFlow / netFlow at physical router"
+msgstr "在物理路由器上：sFlow / netFlow"
+
+# 966d9d494a53445b9daf7f7190e39159
+#: ../../network_setup.rst:60
+msgid "Hypervisor and Virtual Router"
+msgstr "Hypervisor和虚拟路由器"
+
+# 118c5bc124044577ba2fbfe145951209
+#: ../../network_setup.rst:61
+msgid "DNS and DHCP"
+msgstr "DNS和DHCP"
+
+# 08f4517f5738454f8ee78adefac8efb1
+#: ../../network_setup.rst:64
+msgid ""
+"The two types of networking may be in use in the same cloud. However, a "
+"given zone must use either Basic Networking or Advanced Networking."
+msgstr "在一个云中可能会存在二种网络类型。但无论如何，一个给定的区域必须使用基本网络或高级网络。"
+
+# 8caea62e111d4d1b8833f7670c72d8df
+#: ../../network_setup.rst:67
+msgid ""
+"Different types of network traffic can be segmented on the same physical "
+"network. Guest traffic can also be segmented by account. To isolate traffic,"
+" you can use separate VLANs. If you are using separate VLANs on a single "
+"physical network, make sure the VLAN tags are in separate numerical ranges."
+msgstr "单一的物理网络可以被分割不同类型的网络流量。账户也可以分割来宾流量。你可以通过划分VLAN来隔离流量。如果你在物理网络中划分了VLAN，确保VLAN标签的数值在独立范围。"
+
+# f4f61d2e2b224b75a03e28cda9e376a8
+#: ../../network_setup.rst:75
+msgid "VLAN Allocation Example"
+msgstr "VLAN分配示例"
+
+# dad8ccdf2ed74b0e9f0173a0aa08c615
+#: ../../network_setup.rst:77
+msgid ""
+"VLANs are required for public and guest traffic. The following is an example"
+" of a VLAN allocation scheme:"
+msgstr "公共和来宾流量要求使用VLAN，下面是一个VLAN分配的示例："
+
+# d9ac134036354b0ab2421582a57e79c6
+#: ../../network_setup.rst:81
+msgid "VLAN IDs"
+msgstr "VLAN IDs"
+
+# e22dc22a2b9449bbb3e9b5fcceafc29b
+#: ../../network_setup.rst:81
+msgid "Traffic type"
+msgstr "流量类型"
+
+# 2abc2124719642c6bf6ab370646803bc
+#: ../../network_setup.rst:81
+msgid "Scope"
+msgstr "范围"
+
+# f3318541895b4a509bfdcfe8f540fcd2
+#: ../../network_setup.rst:83
+msgid "less than 500"
+msgstr "小于500"
+
+# 7f123557b3644b699605f66ed71aaa88
+#: ../../network_setup.rst:83
+msgid "Management traffic. Reserved for administrative purposes."
+msgstr "管理流量。用于管理目的。"
+
+# 8d3f29be0c2341d181217f083f364b66
+#: ../../network_setup.rst:83
+msgid "CloudStack software can access this, hypervisors, system VMs."
+msgstr "CloudStack，hypervisors，系统VM可以访问。"
+
+# ebbb276566564730b2573b1fd1b161a9
+#: ../../network_setup.rst:84
+msgid "500-599"
+msgstr "500-599"
+
+# 125bfc83d5554aaab7fdd32838cce9c9
+#: ../../network_setup.rst:84
+msgid "VLAN carrying public traffic."
+msgstr "承载公共流量。"
+
+# d37af8f70e29457a9557e53215e2e96c
+#: ../../network_setup.rst:84
+msgid "CloudStack accounts."
+msgstr "CloudStack账户。"
+
+# 73133e4e2c86492c8f9817f4981789f8
+#: ../../network_setup.rst:85
+msgid "600-799"
+msgstr "600-799"
+
+# 20844dcf31fd46558c2f60d7ce91478d
+# 7a38326cb87b46d890e1e444ee7ce9e6
+#: ../../network_setup.rst:85 ../../network_setup.rst:86
+msgid "VLANs carrying guest traffic."
+msgstr "承载来宾流量"
+
+# b9283c2609ad426ea049d4b4de64a229
+#: ../../network_setup.rst:85
+msgid "CloudStack accounts. Account-specific VLAN is chosen from this pool."
+msgstr "CloudStack 账户。 从这个池中选择账户特定的VLAN。"
+
+# 2434c3ee95244a3e87c4be5df884d38e
+#: ../../network_setup.rst:86
+msgid "800-899"
+msgstr "800-899"
+
+# 55d07caba3264be299f2f188911b20f8
+#: ../../network_setup.rst:86
+msgid ""
+"CloudStack accounts. Account-specific VLAN chosen by CloudStack admin to "
+"assign to that account."
+msgstr "CloudStack 账户。CloudStack管理员为账户指定特定的VLAN。"
+
+# 916471020e7c48f8a5b214bd1e8b3764
+#: ../../network_setup.rst:87
+msgid "900-999"
+msgstr "900-999"
+
+# 6eb9b2a9c7d541d49840d4b7da813678
+#: ../../network_setup.rst:87
+msgid "VLAN carrying guest traffic"
+msgstr "承载来宾流量"
+
+# cbe91fb5fb35471aaf913bf77c8545b3
+#: ../../network_setup.rst:87
+msgid ""
+"CloudStack accounts. Can be scoped by project, domain, or all accounts."
+msgstr "CloudStack 账户。可作为项目、域或所有账户的作用域。"
+
+# 7cd25e560d8e482489ee707255e6a113
+#: ../../network_setup.rst:88
+msgid "greater than 1000"
+msgstr "大于1000"
+
+# a732a81098944d88b516c81d48fe1dd6
+#: ../../network_setup.rst:88
+msgid "Reserved for future use"
+msgstr "保留为将来使用"
+
+# 9e6124ed88b34569b749356c28e994c5
+#: ../../network_setup.rst:93
+msgid "Example Hardware Configuration"
+msgstr "硬件配置示例"
+
+# 2e0e4d4766c94461bf47dbf4b297511c
+#: ../../network_setup.rst:95
+msgid ""
+"This section contains an example configuration of specific switch models for"
+" zone-level layer-3 switching. It assumes VLAN management protocols, such as"
+" VTP or GVRP, have been disabled. The example scripts must be changed "
+"appropriately if you choose to use VTP or GVRP."
+msgstr "本节包含了一个特定交换机型号的示例配置，作为区域级别的三层交换。它假设VLAN管理协议，例如VTP、GVRP等已经被禁用。如果你正在使用VTP或GVRP，那么你必须适当的修改示例脚本。"
+
+# e49d362a79214babab229f63b561504f
+# ec1918afa90c431ebc41c83d6622bf67
+#: ../../network_setup.rst:102 ../../network_setup.rst:190
+msgid "Dell 62xx"
+msgstr "Dell 62xx"
+
+# 7cac328e3f4d41d2912b3d1374983217
+#: ../../network_setup.rst:104
+msgid ""
+"The following steps show how a Dell 62xx is configured for zone-level "
+"layer-3 switching. These steps assume VLAN 201 is used to route untagged "
+"private IPs for pod 1, and pod 1’s layer-2 switch is connected to Ethernet "
+"port 1/g1."
+msgstr "以下步骤显示如何配置区域级别的三层交换机Dell 62xx。这些步骤假设VLAN。201用于Pod1中未标记的私有IP线路。并且Pod1中的二层交换机已经连接到GigabitEthernet1/0/1端口。"
+
+# f85fd6334b4d42368bd77fd43eab6554
+#: ../../network_setup.rst:109
+msgid "The Dell 62xx Series switch supports up to 1024 VLANs."
+msgstr "DELL 62xx系列交换机最大支持1024个VLAN。"
+
+# 3a9eadcf6462491b83915415a657e356
+# 4d6fd3d41ba3470c8ffe4bec5ad1626a
+#: ../../network_setup.rst:111 ../../network_setup.rst:195
+msgid "Configure all the VLANs in the database."
+msgstr "在VLAN数据库模式配置VLAN。"
+
+# 3b8ffcd8739f4ebeb2ed2be4eef1ad64
+#: ../../network_setup.rst:119
+msgid "Configure Ethernet port 1/g1."
+msgstr "配置端口1/g1。"
+
+# 3f429d4bc0024cd8bd9e41e305d508d9
+#: ../../network_setup.rst:130
+msgid "The statements configure Ethernet port 1/g1 as follows:"
+msgstr "端口1/g1的配置说明："
+
+# d34108f02c0b45b093b68a1f5b8766a3
+#: ../../network_setup.rst:132
+msgid "VLAN 201 is the native untagged VLAN for port 1/g1."
+msgstr "端口1/g1的本征VLAN为201（属于VLAN201）."
+
+# cb2aa517977a4582afcedbfaf7b457cc
+#: ../../network_setup.rst:134
+msgid "All VLANs (300-999) are passed to all the pod-level layer-2 switches."
+msgstr "在Pod级别的二层交换机中允许所有VLAN（300-999）流量通过。"
+
+# 5889063b34fa4e5a946573bb352b45c7
+# c48e437e84a44e1281b7228a01cc0c4f
+#: ../../network_setup.rst:138 ../../network_setup.rst:222
+msgid "Cisco 3750"
+msgstr "Cisco 3750"
+
+# b029ac75d9be4c4d8f41fa45f587b2a7
+#: ../../network_setup.rst:140
+msgid ""
+"The following steps show how a Cisco 3750 is configured for zone-level "
+"layer-3 switching. These steps assume VLAN 201 is used to route untagged "
+"private IPs for pod 1, and pod 1’s layer-2 switch is connected to "
+"GigabitEthernet1/0/1."
+msgstr "以下步骤显示如何配置Cisco 3750作为区域级别的三层交换机。这些步骤假设VLAN 201用于Pod1中未标记的私有IP线路。并且Pod1中的二层交换机已经连接到GigabitEthernet1/0/1端口。"
+
+# 21087caee9cc42529713be381a17944e
+# 77f3004ef9e84e23985c7a992fe12b51
+#: ../../network_setup.rst:145 ../../network_setup.rst:227
+msgid ""
+"Setting VTP mode to transparent allows us to utilize VLAN IDs above 1000. "
+"Since we only use VLANs up to 999, vtp transparent mode is not strictly "
+"required."
+msgstr "设置VTP为透明模式，以便我们使用超过1000的VLAN。虽然我们只用到999，但VTP透明模式并不做严格要求。"
+
+# bc414aaf1d5d49789ab07767a1efc42e
+#: ../../network_setup.rst:155
+msgid "Configure GigabitEthernet1/0/1."
+msgstr "配置GigabitEthernet1/0/1。"
+
+# 13695f0fdc2c4258a81d99fb9126b65c
+#: ../../network_setup.rst:165
+msgid "The statements configure GigabitEthernet1/0/1 as follows:"
+msgstr "端口GigabitEthernet1/g1的配置说明："
+
+# db9281cf2d474ccb8b73772d174b5061
+#: ../../network_setup.rst:167
+msgid "VLAN 201 is the native untagged VLAN for port GigabitEthernet1/0/1."
+msgstr "端口1/g1的本征VLAN为201（属于VLAN201）."
+
+# 2de38e6352e648758eb5e9d33f7f50b9
+#: ../../network_setup.rst:169
+msgid ""
+"Cisco passes all VLANs by default. As a result, all VLANs (300-999) are "
+"passed to all the pod-level layer-2 switches."
+msgstr "Cisco默认允许所有VLAN，因此，VLAN（300-999）都被允许并访问所有的Pod级别的二层交换机。"
+
+# ecca16ca947244c69af3cda7d8ef906a
+#: ../../network_setup.rst:174
+msgid "Layer-2 Switch"
+msgstr "二层交换"
+
+# bd6f1f286da647f0861e42f5c4d5cbd6
+#: ../../network_setup.rst:176
+msgid "The layer-2 switch is the access switching layer inside the pod."
+msgstr "在Pod中的二层交换机提供接入层功能"
+
+# f5aedd9919f44d4d9eea58da5118c865
+#: ../../network_setup.rst:178
+msgid "It should trunk all VLANs into every computing host."
+msgstr "它通过trunk连接所有VLANS中的计算主机。"
+
+# 47960e02b071465188e24cb273c65328
+#: ../../network_setup.rst:180
+msgid ""
+"It should switch traffic for the management network containing computing and"
+" storage hosts. The layer-3 switch will serve as the gateway for the "
+"management network."
+msgstr "它为管理网络提供包含计算和存储主机的流量交换。三层交换机将作为这个管理网络的网关"
+
+# b6bfd5be3b83467192f7d4dba3613304
+#: ../../network_setup.rst:184
+msgid ""
+"The following sections contain example configurations for specific switch "
+"models for pod-level layer-2 switching. It assumes VLAN management protocols"
+" such as VTP or GVRP have been disabled. The scripts must be changed "
+"appropriately if you choose to use VTP or GVRP."
+msgstr "本节包含了一个特定交换机型号的示例配置，作为Pod级别的二层交换机。它假设VLAN管理协议，例如VTP、GVRP等已经被禁用。如果你正在使用VTP或GVRP，那么你必须适当的修改示例脚本。"
+
+# a9c5170aa3324e03adee54023346ad80
+#: ../../network_setup.rst:192
+msgid ""
+"The following steps show how a Dell 62xx is configured for pod-level layer-2"
+" switching."
+msgstr "以下步骤将演示如何配置Dell 62xx作为Pod级别的二层交换机。"
+
+# 476b0c81a6c44098804cc2f6b9c8dfd5
+#: ../../network_setup.rst:203
+msgid ""
+"VLAN 201 is used to route untagged private IP addresses for pod 1, and pod 1"
+" is connected to this layer-2 switch."
+msgstr "VLAN201用于Pod1中未标记的私有IP线路。并且Pod1已经连接到该二层交换机。"
+
+# 22aebc930b7b471394516ed87778ba3c
+#: ../../network_setup.rst:213
+msgid "The statements configure all Ethernet ports to function as follows:"
+msgstr "所有的以太网端口功能配置说明："
+
+# 01bdebb29d964df18edcf52ee732caa0
+#: ../../network_setup.rst:215
+msgid "All ports are configured the same way."
+msgstr "所有端口配置相同"
+
+# 42d47d6cc7f148de826545de21dee4c0
+#: ../../network_setup.rst:217
+msgid ""
+"All VLANs (300-999) are passed through all the ports of the layer-2 switch."
+msgstr "二层交换机的所有端口都允许VLAN（300-999）通过。"
+
+# 5057c158f06e4e439eebde80d1e49d38
+#: ../../network_setup.rst:224
+msgid ""
+"The following steps show how a Cisco 3750 is configured for pod-level "
+"layer-2 switching."
+msgstr "以下步骤将演示如何配置cisco 3750作为Pod级别的二层交换机"
+
+# 97f41001dc4f44e5bf4def9e08be580c
+#: ../../network_setup.rst:237
+msgid "Configure all ports to dot1q and set 201 as the native VLAN."
+msgstr "配置所有的端口使用dot1q协议，并设置201为本征VLAN。"
+
+# 5ea9eb52eaea40329b40b32897d7c2f1
+#: ../../network_setup.rst:247
+msgid ""
+"By default, Cisco passes all VLANs. Cisco switches complain of the native "
+"VLAN IDs are different when 2 ports are connected together. That’s why you "
+"must specify VLAN 201 as the native VLAN on the layer-2 switch."
+msgstr "默认情况下，Cisco允许所有VLAN通过。如果本征VLAN ID不相同的2个端口连接在一起时，Cisco交换机提出控诉。这就是为什么必须指定VLAN 201为二交换机的本征VLAN。"
+
+# 8b410ff7a036484a89d183ed79f66761
+#: ../../network_setup.rst:254
+msgid "Hardware Firewall"
+msgstr "硬件防火墙"
+
+# 149a7357d1b2421c8e62f11be11e4a89
+#: ../../network_setup.rst:256
+msgid ""
+"All deployments should have a firewall protecting the management server; see"
+" Generic Firewall Provisions. Optionally, some deployments may also have a "
+"Juniper SRX firewall that will be the default gateway for the guest "
+"networks; see `“External Guest Firewall Integration for Juniper SRX "
+"(Optional)” <#external-guest-firewall-integration-for-juniper-srx-"
+"optional>`_."
+msgstr "所有部署都应该有一个防火墙保护管理服务器；查看防火墙的一般规定。 根据情况不同，一些部署也可能用到Juniper SRX防火墙作为来宾网络的默认网关； 参阅 `“集成外部来宾防火墙Juniper SRX （可选）” <#external-guest-firewall-integration-for-juniper-srx-optional>`_."
+
+# e2f547c68a5549bebcc7c440d52727e8
+#: ../../network_setup.rst:263
+msgid "Generic Firewall Provisions"
+msgstr "防火墙的一般规定"
+
+# 8f3c0247e1254e6c8731076a59b80543
+#: ../../network_setup.rst:265
+msgid "The hardware firewall is required to serve two purposes:"
+msgstr "硬件防火墙必需服务于两个目的："
+
+# 4e3d6f474c664d1ea8727ca773c6c317
+#: ../../network_setup.rst:267
+msgid ""
+"Protect the Management Servers. NAT and port forwarding should be configured"
+" to direct traffic from the public Internet to the Management Servers."
+msgstr "保护管理服务器。"
+
+# deafcee33c084aea9b10dc89e3c056db
+#: ../../network_setup.rst:271
+msgid ""
+"Route management network traffic between multiple zones. Site-to-site VPN "
+"should be configured between multiple zones."
+msgstr "路由多个区域之间的管理网络流量。站点到站点 VPN应该在多个区域之间配置。"
+
+# 3bf3e1c1628b4e3cbd78d690b7f6da5d
+#: ../../network_setup.rst:274
+msgid ""
+"To achieve the above purposes you must set up fixed configurations for the "
+"firewall. Firewall rules and policies need not change as users are "
+"provisioned into the cloud. Any brand of hardware firewall that supports NAT"
+" and site-to-site VPN can be used."
+msgstr "为了达到上述目的，你必须设置固定配置的防火墙。用户被配置到云中，不需要改变防火墙规则和策略。任何支持NAT和站点到站点VPN的硬件防火墙，不论品牌，都可以使用。"
+
+# 6bd99eddfc3a460a8e104b8fb62cb5c1
+#: ../../network_setup.rst:281
+msgid "External Guest Firewall Integration for Juniper SRX (Optional)"
+msgstr "集成外部来宾防火墙Juniper SRX（可选）"
+
+# 91fc9325ee69495fa969c72724802e81
+#: ../../network_setup.rst:284
+msgid "Available only for guests using advanced networking."
+msgstr "客户使用高级网络时才有效。"
+
+# 0dd27c6946794a9cafa7a524eccfffa9
+#: ../../network_setup.rst:286
+msgid ""
+"CloudStack provides for direct management of the Juniper SRX series of "
+"firewalls. This enables CloudStack to establish static NAT mappings from "
+"public IPs to guest VMs, and to use the Juniper device in place of the "
+"virtual router for firewall services. You can have one or more Juniper SRX "
+"per zone. This feature is optional. If Juniper integration is not "
+"provisioned, CloudStack will use the virtual router for these services."
+msgstr "CloudStack中提供了对Juniper SRX系列防火墙的直接管理。这使得CloudStack能建立公共IP到客户虚拟机的静态NAT映射，并利用Juniper设备替代虚拟路由器提供防火墙服务。每个区域中可以有一个或多个Juniper SRX设备。这个特性是可选的。如果不提供Juniper设备集成，CloudStack会使用虚拟路由器提供这些服务。"
+
+# 59a83ba854224a05b873335238575ed2
+#: ../../network_setup.rst:293
+msgid ""
+"The Juniper SRX can optionally be used in conjunction with an external load "
+"balancer. External Network elements can be deployed in a side-by-side or "
+"inline configuration."
+msgstr "Juniper SRX可以和任意的外部负载均衡器一起使用。外部网络元素可以部署为并排或内联结构。"
+
+# 9583a2f6c4bd4bf4a0ef016582e4950e
+#: ../../network_setup.rst:297
+msgid ""
+"|parallel-mode.png: adding a firewall and load balancer in parallel mode.|"
+msgstr "|parallel-mode.png: adding a firewall and load balancer in parallel mode.|"
+
+# 33e495e75ccc4175ac42b392be1f9a25
+#: ../../network_setup.rst:300
+msgid ""
+"CloudStack requires the Juniper SRX firewall to be configured as follows:"
+msgstr "CloudStack要求按照如下信息配置Juniper SRX防火墙："
+
+# 1d1d4d7ab6de4a8985bde992b3d4b3e8
+#: ../../network_setup.rst:303
+msgid "Supported SRX software version is 10.3 or higher."
+msgstr "支持SRX软件版本为10.3或者更高。"
+
+# 6dcbb647db2644fa9a7c43eeb20f382f
+#: ../../network_setup.rst:305
+msgid "Install your SRX appliance according to the vendor's instructions."
+msgstr "根据供应商提供的说明书安装你的SRX设备。"
+
+# 50c53fc1bbaa48ee9e70e7868e5ac785
+#: ../../network_setup.rst:307
+msgid ""
+"Connect one interface to the management network and one interface to the "
+"public network. Alternatively, you can connect the same interface to both "
+"networks and a use a VLAN for the public network."
+msgstr "分别使用两个接口连接管理和公共网络，或者，你可以使用同一个接口来连接这两个网络，但需要为公共网络设置一个VLAN。"
+
+# 0acd20956a3b4ed79e57dd49dd90aa83
+#: ../../network_setup.rst:311
+msgid "Make sure \"vlan-tagging\" is enabled on the private interface."
+msgstr "确保在专有接口上开启了 \"vlan-tagging\" 。"
+
+# 043b2c85f7df4eaa8f35f85717d6411e
+#: ../../network_setup.rst:313
+msgid ""
+"Record the public and private interface names. If you used a VLAN for the "
+"public interface, add a \".[VLAN TAG]\" after the interface name. For "
+"example, if you are using ge-0/0/3 for your public interface and VLAN tag "
+"301, your public interface name would be \"ge-0/0/3.301\". Your private "
+"interface name should always be untagged because the CloudStack software "
+"automatically creates tagged logical interfaces."
+msgstr "记录公共和专用接口名称。如果你在公共接口中使用了VLAN，应该在接口名称后面添加一个\".[VLAN TAG]\"。例如，如果你使用 ge-0/0/3 作为公共接口并且VLAN 标签为301。那么你的公共接口名称应为\"ge-0/0/3.301\"。你的专用接口应始终不添加任何标签，因为CloudStack会自动在逻辑接口上添加标签。"
+
+# d2e6321e2786420589602b57da869135
+#: ../../network_setup.rst:320
+msgid ""
+"Create a public security zone and a private security zone. By default, these"
+" will already exist and will be called \"untrust\" and \"trust\". Add the "
+"public interface to the public zone and the private interface to the private"
+" zone. Note down the security zone names."
+msgstr "创建公共安全区域和专用安全区域。默认情况下，这些已经存在并分别称为\"untrust\" 和 \"trust\"。为公共区域添加公共接口和为专用区域添加专用接口。并记录下安全区域名称。"
+
+# 9d5330a8656f412aa6986f2bd6a1d05d
+#: ../../network_setup.rst:325
+msgid ""
+"Make sure there is a security policy from the private zone to the public "
+"zone that allows all traffic."
+msgstr "确保专用区域到公共区域的安全策略允许所有流量通过。"
+
+# ed6f7d110d0143b6b94e01737a88c911
+#: ../../network_setup.rst:328
+msgid ""
+"Note the username and password of the account you want the CloudStack "
+"software to log in to when it is programming rules."
+msgstr "请注意CloudStack登录所用账户的用户名和密码符合编程规则。"
+
+# 15d496095b294760b7582dd939c7e2a8
+#: ../../network_setup.rst:331
+msgid "Make sure the \"ssh\" and \"xnm-clear-text\" system services are enabled."
+msgstr "确保已经开启 \"ssh\" 和 \"xnm-clear-text\" 等系统服务。"
+
+# 8e2b9fe66ce24116ae4ebbeea154806a
+#: ../../network_setup.rst:333
+msgid "If traffic metering is desired:"
+msgstr "如果需要统计流量："
+
+# b63ccbb8b8fd42aba3d987bed558037b
+#: ../../network_setup.rst:335
+msgid ""
+"Create an incoming firewall filter and an outgoing firewall filter. These "
+"filters should be the same names as your public security zone name and "
+"private security zone name respectively. The filters should be set to be "
+"\"interface-specific\". For example, here is the configuration where the "
+"public zone is \"untrust\" and the private zone is \"trust\":"
+msgstr "创建传入的防火墙过滤和传出的防火墙过滤。这些策略应该有相同的名称分别作为你的公共安全区域名称和专用安全区域名称。过滤应该设置到 \"特定接口\"。 例如，在这个配置中公共区域是 \"untrust\"，专用区域是 \"trust\": "
+
+# b8d90177058440b08f11b6fbd6224400
+#: ../../network_setup.rst:352
+msgid ""
+"Add the firewall filters to your public interface. For example, a sample "
+"configuration output (for public interface ge-0/0/3.0, public security zone "
+"untrust, and private security zone trust) is:"
+msgstr "在你的公共接口添加防火墙过滤。例如，一个示例配置（ge-0/0/3.0为公共接口，untrust为公共安全区域，trust为专用安全区域）"
+
+# d0201cdd17164ce8bb8ed40e21ce56ed
+#: ../../network_setup.rst:370
+msgid "Make sure all VLANs are brought to the private interface of the SRX."
+msgstr "确保SRX中的专用接口允许所有VLAN通过。"
+
+# 0be4d835f5ec47dfb1cb475ce8185cbd
+#: ../../network_setup.rst:372
+msgid ""
+"After the CloudStack Management Server is installed, log in to the "
+"CloudStack UI as administrator."
+msgstr "安装好CloudStack管理端后，使用管理员帐号登录CloudStack用户界面。"
+
+# 83eedf55f3c84dd59b6d0031f7e0c5ee
+# 119ea5f9aac34939b712e6bf35fd6b2b
+# 9de5aa399b044a5a86ccc6bd1abe0800
+# e5a613843e514b77a3d7467cdc372e5f
+#: ../../network_setup.rst:375 ../../network_setup.rst:597
+#: ../../network_setup.rst:631 ../../network_setup.rst:790
+msgid "In the left navigation bar, click Infrastructure."
+msgstr "在左侧导航栏中，点击基础架构"
+
+# c7b8e2f9cbd84c43a23b87769989190b
+# fee6b2759a0a4c8d85973b38457107b9
+# 29aa1bf7a6cc4e779ad52ab4f8d65691
+# 1a6287e3416f438e8e20715084bec873
+#: ../../network_setup.rst:377 ../../network_setup.rst:599
+#: ../../network_setup.rst:633 ../../network_setup.rst:792
+msgid "In Zones, click View More."
+msgstr "点击区域中的查看更多。"
+
+# 564cfc916b7b4250b8211ac6b03d6830
+# 99ba370aee7e4b14ba26cb13b10849ad
+# 0e2e624457db4fba8b6a9bea3ecc8cd2
+# d36af8233dbf427dbda0f1f6a3b3279d
+#: ../../network_setup.rst:379 ../../network_setup.rst:601
+#: ../../network_setup.rst:635 ../../network_setup.rst:794
+msgid "Choose the zone you want to work with."
+msgstr "选择你要设置的区域。"
+
+# fd783e15448d42eca4b34f6d6c297a80
+# 8b0b666f0e2c4a61b088f7aea345a2c1
+#: ../../network_setup.rst:381 ../../network_setup.rst:796
+msgid "Click the Network tab."
+msgstr "点击网络选项卡。"
+
+# 27d53105db6e439c9ee111db84d2e624
+# cc0180b6815b400c9453c2c6a2b25cef
+#: ../../network_setup.rst:383 ../../network_setup.rst:798
+msgid ""
+"In the Network Service Providers node of the diagram, click Configure. (You "
+"might have to scroll down to see this.)"
+msgstr "点击示意图网络服务提供程序中的配置（你可能需要向下滚动才能看到）。"
+
+# c57c2457da7b4b2fab54de32397fb5bb
+#: ../../network_setup.rst:386
+msgid "Click SRX."
+msgstr "点击SRX。"
+
+# c63b5c19989247ce8932e1d0cb37d240
+#: ../../network_setup.rst:388
+msgid "Click the Add New SRX button (+) and provide the following:"
+msgstr "点击（+）按钮添加一个新的SRX，并提供如下信息："
+
+# 8d667d9b05284e6fb6629c3d184f4b12
+# b559300d6e0f48daa0730c40d2cbcf6e
+#: ../../network_setup.rst:390 ../../network_setup.rst:807
+msgid "IP Address: The IP address of the SRX."
+msgstr "IP地址：SRX设备的IP地址。"
+
+# 5f9a972abd4e41d98ebc2925a9bbffb7
+#: ../../network_setup.rst:392
+msgid ""
+"Username: The user name of the account on the SRX that CloudStack should "
+"use."
+msgstr "用户名：CloudStack需要使用SRX设备中的账户。"
+
+# 9805383a254e4a42b7870c8c3c9fc1fb
+# 9d98c3fcf55b4763826c737462e97833
+#: ../../network_setup.rst:395 ../../network_setup.rst:621
+msgid "Password: The password of the account."
+msgstr "密码：该账户的密码。"
+
+# 589a2bf5564f4f3dabfc87038ad99528
+#: ../../network_setup.rst:397
+msgid ""
+"Public Interface. The name of the public interface on the SRX. For example, "
+"ge-0/0/2. A \".x\" at the end of the interface indicates the VLAN that is in"
+" use."
+msgstr "公共接口：SRX中的公共接口名称。例如，ge-0/0/2。 最后一个 \".x\" 表示该VLAN正在使用这个接口。"
+
+# a99e76740bd74ea2b9d864e0f2f22d36
+#: ../../network_setup.rst:401
+msgid ""
+"Private Interface: The name of the private interface on the SRX. For "
+"example, ge-0/0/1."
+msgstr "专用接口: SRX中的专用接口名称。例如, ge-0/0/1。"
+
+# b141f05518cd45c0bfb4563cae4c1f39
+#: ../../network_setup.rst:404
+msgid ""
+"Usage Interface: (Optional) Typically, the public interface is used to meter"
+" traffic. If you want to use a different interface, specify its name here"
+msgstr "Usage Interface: (可选) 通常情况下，公共接口用来统计流量。如果你想使用其他的接口，则在此处修改。"
+
+# 06f5547344474c78b06dfceef142803e
+#: ../../network_setup.rst:408
+msgid ""
+"Number of Retries: The number of times to attempt a command on the SRX "
+"before failing. The default value is 2."
+msgstr "重试次数：尝试控制SRX设备失败时重试的次数。默认值是2。"
+
+# 0e672b9a244d49b981670d6082dcec0e
+#: ../../network_setup.rst:411
+msgid ""
+"Timeout (seconds): The time to wait for a command on the SRX before "
+"considering it failed. Default is 300 seconds."
+msgstr "超时(秒): 尝试控制SRX设备失败时的重试间隔。默认为300秒。"
+
+# fc059aade6b144a4b95d0c8826c39030
+#: ../../network_setup.rst:414
+msgid ""
+"Public Network: The name of the public network on the SRX. For example, "
+"trust."
+msgstr "公共网络: SRX中公共网络的名字。 例，trust。 "
+
+# a174bebde38f47648a5348b5a7f31b8a
+#: ../../network_setup.rst:417
+msgid ""
+"Private Network: The name of the private network on the SRX. For example, "
+"untrust."
+msgstr "专用网络：SRX中专用网络的名字。 例如，untrust。"
+
+# e8f9887a325f4080a1f065d01ce94eef
+#: ../../network_setup.rst:420
+msgid "Capacity: The number of networks the device can handle"
+msgstr "容量：该设备能处理的网络数量。"
+
+# feca5c1941624366a9ee33104afa1869
+#: ../../network_setup.rst:422
+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 "专用: 当标记为专用后，这个设备只对单个帐号专用。该选项被勾选后，容量选项就没有了实际意义且值会被置为1。"
+
+# d87bed8dbd1d4647a4a74b4fde1e2b4e
+# 6e6650d74a0343ef91d48ae3c11dc1e2
+# e3313ae53b0e404c8a5b589979a311b2
+# 6c0d5b7a35c94391936c43610833c8b1
+#: ../../network_setup.rst:426 ../../network_setup.rst:623
+#: ../../network_setup.rst:661 ../../network_setup.rst:832
+msgid "Click OK."
+msgstr "点击确定。"
+
+# 72e1ae81e175465e801b9a35330c91c7
+#: ../../network_setup.rst:428
+msgid ""
+"Click Global Settings. Set the parameter external.network.stats.interval to "
+"indicate how often you want CloudStack to fetch network usage statistics "
+"from the Juniper SRX. If you are not using the SRX to gather network usage "
+"statistics, set to 0."
+msgstr "点击全局设置。设置external.network.stats.interval参数，指定CloudStack从Juniper SRX收集网络使用情况的时间间隔。如果你不使用SRX统计网络使用情况，即设置为0."
+
+# 5311a929dda944ea92ba1a05fe795f65
+#: ../../network_setup.rst:435
+msgid "External Guest Firewall Integration for Cisco VNMC (Optional)"
+msgstr "整合Cisco VNMC和外部来宾防火墙（可选）"
+
+# 40bbe2d15710459ea8a53a4a3e8be997
+#: ../../network_setup.rst:437
+msgid ""
+"Cisco Virtual Network Management Center (VNMC) provides centralized multi-"
+"device and policy management for Cisco Network Virtual Services. You can "
+"integrate Cisco VNMC with CloudStack to leverage the firewall and NAT "
+"service offered by ASA 1000v Cloud Firewall. Use it in a Cisco Nexus 1000v "
+"dvSwitch-enabled cluster in CloudStack. In such a deployment, you will be "
+"able to:"
+msgstr "Cisco虚拟网络管理中心（VNMC）为Cisco网络虚拟服务提供集中式多设备和策略管理。您可以通过整合Cisco VNMC和CloudStack使用ASA 1000v云防火墙提供防火墙和NAT服务。在开启了Cisco Nexus 1000v分布式虚拟交换机功能的CloudStack群集中。这样部署，您将可以："
+
+# 53b820cc9dff42c7b255ab4d8568a19e
+#: ../../network_setup.rst:444
+msgid ""
+"Configure Cisco ASA 1000v firewalls. You can configure one per guest "
+"network."
+msgstr "配置Cisco ASA 1000v防火墙，你可以为每个来宾创建一个网络。"
+
+# 7d55cb00df5b4a49bfb45bc29b87a677
+#: ../../network_setup.rst:447
+msgid ""
+"Use Cisco ASA 1000v firewalls to create and apply security profiles that "
+"contain ACL policy sets for both ingress and egress traffic."
+msgstr "使用思科ASA 1000v防火墙创建和应用安全配置，包含入口和出口流量的ACL策略集。"
+
+# bbd8e2f953704bfda60d592b7a1c4429
+#: ../../network_setup.rst:450
+msgid ""
+"Use Cisco ASA 1000v firewalls to create and apply Source NAT, Port "
+"Forwarding, and Static NAT policy sets."
+msgstr "使用Cisco ASA 1000v防火墙创建和应用源地址NAT，端口转发，静态NAT策略集。"
+
+# 474d1c74488841138f21f9871e3e7637
+#: ../../network_setup.rst:453
+msgid ""
+"CloudStack supports Cisco VNMC on Cisco Nexus 1000v dvSwich-enabled VMware "
+"hypervisors."
+msgstr "CloudStack对于Cisco VNMC的支持基于开启了Cisco Nexus 1000v分布式虚拟交换机功能的VMware虚拟化管理平台。"
+
+# 42c0de41f2c44491a91b52cf81ed3674
+#: ../../network_setup.rst:458
+msgid ""
+"Using Cisco ASA 1000v Firewall, Cisco Nexus 1000v dvSwitch, and Cisco VNMC "
+"in a Deployment"
+msgstr "部署使用Cisco ASA 1000v防火墙，Cisco Nexus 1000v分布式虚拟交换机和Cisco VNMC。"
+
+# d18809d95a674b9cbe2ffa627eff2786
+#: ../../network_setup.rst:461
+msgid "Guidelines"
+msgstr "指南"
+
+# f97e1aa6ae6b4d49b5c4c66f95db6400
+#: ../../network_setup.rst:463
+msgid "Cisco ASA 1000v firewall is supported only in Isolated Guest Networks."
+msgstr "Cisco ASA 1000v防火墙仅支持隔离的来宾网络。"
+
+# 8df62ec4f02c4a4dbb579d02dd3f150a
+#: ../../network_setup.rst:466
+msgid "Cisco ASA 1000v firewall is not supported on VPC."
+msgstr "Cisco ASA 1000v不支持VPC。"
+
+# 7b56777b52384a36ae1bb6733fedafcb
+#: ../../network_setup.rst:468
+msgid "Cisco ASA 1000v firewall is not supported for load balancing."
+msgstr "Cisco ASA 1000v不支持负载均衡。"
+
+# 237ca442d633476b97185dca9083c955
+#: ../../network_setup.rst:470
+msgid ""
+"When a guest network is created with Cisco VNMC firewall provider, an "
+"additional public IP is acquired along with the Source NAT IP. The Source "
+"NAT IP is used for the rules, whereas the additional IP is used to for the "
+"ASA outside interface. Ensure that this additional public IP is not "
+"released. You can identify this IP as soon as the network is in implemented "
+"state and before acquiring any further public IPs. The additional IP is the "
+"one that is not marked as Source NAT. You can find the IP used for the ASA "
+"outside interface by looking at the Cisco VNMC used in your guest network."
+msgstr "当使用Cisco VNMC防火墙创建的来宾网络时，一个额外的公共IP和SNAT IP一起被获取。SNAT IP用于规则，而额外的IP用于ASA外部接口。确保这一额外的公共IP不会被释放。你可以在网络一旦处在执行状态和获取其他公共IP之前确定这个IP。这个额外的IP没有被标识为SNAT。在你的来宾网络中可以通过Cisco VNMC来查找ASA外部接口的IP地址。"
+
+# 71e7c6de8183436aa6c9219b5fe32097
+#: ../../network_setup.rst:480
+msgid ""
+"Use the public IP address range from a single subnet. You cannot add IP "
+"addresses from different subnets."
+msgstr "使用单一网络中的公共IP地址段。不能添加不同网段的IP地址。"
+
+# 347a68ec09e74810a44472e35d092f64
+#: ../../network_setup.rst:483
+msgid ""
+"Only one ASA instance per VLAN is allowed because multiple VLANS cannot be "
+"trunked to ASA ports. Therefore, you can use only one ASA instance in a "
+"guest network."
+msgstr "每个VLAN中只允许一个ASA实例。因为ASA端口不支持多VLAN的trunk模式。因此，一个来宾网络中只能有一个ASA实例。"
+
+# 569e13e1167c4a76a6f5134ef65d99e8
+#: ../../network_setup.rst:487
+msgid "Only one Cisco VNMC per zone is allowed."
+msgstr "每个区域中，只允许一个Cisco VNMC."
+
+# bb939448a41a44189ebb9d02a40c6b17
+#: ../../network_setup.rst:489
+msgid "Supported only in Inline mode deployment with load balancer."
+msgstr "只支持在Inline模式下部署负载均衡器。"
+
+# 877c7cf7a46f4eb1a593397a10187a6a
+#: ../../network_setup.rst:491
+msgid ""
+"The ASA firewall rule is applicable to all the public IPs in the guest "
+"network. Unlike the firewall rules created on virtual router, a rule created"
+" on the ASA device is not tied to a specific public IP."
+msgstr "ASA防火墙策略适用于来宾网络中所有的公共IP地址。不同于虚拟路由器创建的防火墙规则，ASA设备创建的规则不绑定特定的公共IP地址。"
+
+# cf88d5219d574e44bfc0c436912c5391
+#: ../../network_setup.rst:495
+msgid ""
+"Use a version of Cisco Nexus 1000v dvSwitch that support the vservice "
+"command. For example: nexus-1000v.4.2.1.SV1.5.2b.bin"
+msgstr "使用一个支持vservice命令的Cisco Nexus 1000v分布式虚拟交换机版本。例如：nexus-1000v.4.2.1.SV1.5.2b.bin"
+
+# 6de75b299213451ea9108722f5431abf
+#: ../../network_setup.rst:498
+msgid ""
+"Cisco VNMC requires the vservice command to be available on the Nexus switch"
+" to create a guest network in CloudStack."
+msgstr "使用Cisco VNMC在CloudStack中创建来宾网络，要求vservice命令在Nexus交换机中是可用的。"
+
+# 39bbc9648cf346ba995bd567cba5a91c
+#: ../../network_setup.rst:503
+msgid "Prerequisites"
+msgstr "先决条件"
+
+# c4d87ffce9ee418bb5277196957041d2
+#: ../../network_setup.rst:505
+msgid "Configure Cisco Nexus 1000v dvSwitch in a vCenter environment."
+msgstr "在vCenter环境中配置Cisco Nexus 1000v分布式交换机。"
+
+# 273055b3e10447eb9f6ee66aa7c56122
+#: ../../network_setup.rst:507
+msgid ""
+"Create Port profiles for both internal and external network interfaces on "
+"Cisco Nexus 1000v dvSwitch. Note down the inside port profile, which needs "
+"to be provided while adding the ASA appliance to CloudStack."
+msgstr "在Cisco Nexus 1000v 分布式虚拟交换机中创建两个（内部和外部）网络接口的端口配置文件。记录下内部端口配置，在CloudStack中添加ASA设备时需要提供。"
+
+# e38227e22a094d63bc1b850e584bf3b9
+#: ../../network_setup.rst:512
+msgid ""
+"For information on configuration, see `“Configuring a vSphere Cluster with "
+"Nexus 1000v Virtual Switch” <hypervisor_installation.html#configuring-a"
+"-vsphere-cluster-with-nexus-1000v-virtual-switch>`_."
+msgstr "更多配置信息，请查阅 `“配置vSphere群集和Nexus 1000v 虚拟交换机” <hypervisor_installation.html#configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch>`_."
+
+# 55fe45ec845548cbb8a78e36f3c06ec0
+#: ../../network_setup.rst:516
+msgid "Deploy and configure Cisco VNMC."
+msgstr "部署和配置Cisco VNMC。"
+
+# f746770abf4f45ef945ff3f0a26b584a
+#: ../../network_setup.rst:518
+msgid ""
+"For more information, see `Installing Cisco Virtual Network Management "
+"Center "
+"<http://www.cisco.com/en/US/docs/switches/datacenter/vsg/sw/4_2_1_VSG_2_1_1/install_upgrade/guide/b_Cisco_VSG_for_VMware_vSphere_Rel_4_2_1_VSG_2_1_1_and_Cisco_VNMC_Rel_2_1_Installation_and_Upgrade_Guide_chapter_011.html>`_"
+" and `Configuring Cisco Virtual Network Management Center "
+"<http://www.cisco.com/en/US/docs/unified_computing/vnmc/sw/1.2/VNMC_GUI_Configuration/b_VNMC_GUI_Configuration_Guide_1_2_chapter_010.html>`_."
+msgstr "更多信息，请查阅 `安装Cisco虚拟网络管理中心 <http://www.cisco.com/en/US/docs/switches/datacenter/vsg/sw/4_2_1_VSG_2_1_1/install_upgrade/guide/b_Cisco_VSG_for_VMware_vSphere_Rel_4_2_1_VSG_2_1_1_and_Cisco_VNMC_Rel_2_1_Installation_and_Upgrade_Guide_chapter_011.html>`_ 和 `配置Cisco虚拟网络管理中心 <http://www.cisco.com/en/US/docs/unified_computing/vnmc/sw/1.2/VNMC_GUI_Configuration/b_VNMC_GUI_Configuration_Guide_1_2_chapter_010.html>`_."
+
+# 890a0309246f4e1cb3c358dcb4e98983
+#: ../../network_setup.rst:524
+msgid "Register Cisco Nexus 1000v dvSwitch with Cisco VNMC."
+msgstr "注册Cisco Nexus 1000v分布式交换机到Cisco VNMC。"
+
+# 5d7310375c57493aa147f26420784b38
+#: ../../network_setup.rst:526
+msgid ""
+"For more information, see `Registering a Cisco Nexus 1000V with Cisco VNMC "
+"<http://www.cisco.com/en/US/docs/switches/datacenter/vsg/sw/4_2_1_VSG_1_2/vnmc_and_vsg_qi/guide/vnmc_vsg_install_5register.html#wp1064301>`_."
+msgstr "更多信息，请查阅 `注册Cisco Nexus 1000V 和Cisco VNMC <http://www.cisco.com/en/US/docs/switches/datacenter/vsg/sw/4_2_1_VSG_1_2/vnmc_and_vsg_qi/guide/vnmc_vsg_install_5register.html#wp1064301>`_."
+
+# 500816abfa7f432d9ed94665ff42315a
+#: ../../network_setup.rst:529
+msgid "Create Inside and Outside port profiles in Cisco Nexus 1000v dvSwitch."
+msgstr "在Cisco Nexus 1000v分布式交换机中创建内部和外部端口配置文件。"
+
+# 76cabd3f3582426c8c8810e144eb23f3
+#: ../../network_setup.rst:531
+msgid ""
+"For more information, see `“Configuring a vSphere Cluster with Nexus 1000v "
+"Virtual Switch” <hypervisor_installation.html#configuring-a-vsphere-cluster-"
+"with-nexus-1000v-virtual-switch>`_."
+msgstr "更多信息，请查阅 `“配置vSphere群集和Nexus 1000v 虚拟交换机” <hypervisor_installation.html#configuring-a-vsphere-cluster-with-nexus-1000v-virtual-switch>`_."
+
+# ff2dcbffa1b14e5ab64b8c834942483e
+#: ../../network_setup.rst:535
+msgid "Deploy and Cisco ASA 1000v appliance."
+msgstr "部署Cisco ASA 1000v设备。"
+
+# 39146f72a8c84d28bc65e5fa9dd4cdb9
+#: ../../network_setup.rst:537
+msgid ""
+"For more information, see `Setting Up the ASA 1000V Using VNMC "
+"<http://www.cisco.com/en/US/docs/security/asa/quick_start/asa1000V/setup_vnmc.html>`_."
+msgstr "更多信息，请查阅 `使用VNMC设置ASA 1000V <http://www.cisco.com/en/US/docs/security/asa/quick_start/asa1000V/setup_vnmc.html>`_."
+
+# 2165e5de14094930bed61e6b01f0b77a
+#: ../../network_setup.rst:540
+msgid ""
+"Typically, you create a pool of ASA 1000v appliances and register them with "
+"CloudStack."
+msgstr "通常情况下，你可以创建一个ASA 1000v设备池通过CloudStack来注册他们。"
+
+# 71608798f1724b909bf18251bbcdce75
+#: ../../network_setup.rst:543
+msgid "Specify the following while setting up a Cisco ASA 1000v instance:"
+msgstr "设置Cisco ASA 1000v设备需指定如下信息："
+
+# e7347e3b34f14bfdb63251d3628abbdd
+#: ../../network_setup.rst:545
+msgid "VNMC host IP."
+msgstr "VNMC主机IP。"
+
+# 6b0bb824d6ba4c308a4713de3f38b8bb
+#: ../../network_setup.rst:547
+msgid "Ensure that you add ASA appliance in VNMC mode."
+msgstr "确保你在VNMC模式中添加ASA设备。"
+
+# 70e3ab12a94645d9b8db4379ed6c40e6
+#: ../../network_setup.rst:549
+msgid ""
+"Port profiles for the Management and HA network interfaces. This need to be "
+"pre-created on Cisco Nexus 1000v dvSwitch."
+msgstr "需要预先在Cisco Nexus 1000v分布式虚拟交换机中创建用于管理和高可用的网络接口配置文件。"
+
+# c53ff0d84fc941c28feda24f9e7e4eef
+#: ../../network_setup.rst:552
+msgid "Internal and external port profiles."
+msgstr "内部和外部端口配置文件"
+
+# 45b55744d6e247269c14c32af61e6b04
+#: ../../network_setup.rst:554
+msgid ""
+"The Management IP for Cisco ASA 1000v appliance. Specify the gateway such "
+"that the VNMC IP is reachable."
+msgstr "Cisco ASA 1000v设备的管理IP。指定网关确保到VNMC IP是可达的。"
+
+# 199952960bde4c1d8f20c181417792e5
+#: ../../network_setup.rst:557
+msgid "Administrator credentials"
+msgstr "管理员证书"
+
+# 93c5f22490074bdc99e81cd94c41d53a
+#: ../../network_setup.rst:559
+msgid "VNMC credentials"
+msgstr "VNMC证书"
+
+# 10dbc0618ab842719aa3772b2e8784fa
+#: ../../network_setup.rst:561
+msgid "Register Cisco ASA 1000v with VNMC."
+msgstr "注册Cisco ASA 1000v到VNMC。"
+
+# 5966ea52cf464c80b807747bebbc8460
+#: ../../network_setup.rst:563
+msgid ""
+"After Cisco ASA 1000v instance is powered on, register VNMC from the ASA "
+"console."
+msgstr "打开Cisco ASA 1000v实例电源后，通过ASA控制台注册VNMC。"
+
+# 3a33bfedd41d4a64b21fb24beccb4b22
+#: ../../network_setup.rst:568
+msgid "Using Cisco ASA 1000v Services"
+msgstr "使用Cisco ASA 1000v服务"
+
+# 92702d5dd3bb4e1489e83c77093f1a05
+#: ../../network_setup.rst:570
+msgid "Ensure that all the prerequisites are met."
+msgstr "确保满足所有的先决条件。"
+
+# 1c86dda56f9b4f1d95dd04a56a545eb6
+#: ../../network_setup.rst:572
+msgid "See `“Prerequisites” <#prerequisites>`_."
+msgstr "参阅 `“先决条件” <#prerequisites>`_."
+
+# 2a96e0eac83d460fb53cfd7a57b336a1
+#: ../../network_setup.rst:574
+msgid "Add a VNMC instance."
+msgstr "添加 VNMC 实例。"
+
+# 7f2786b9a09648eca50126e66e9a1ce9
+#: ../../network_setup.rst:576
+msgid "See `“Adding a VNMC Instance” <#adding-a-vnmc-instance>`_."
+msgstr "参阅 `“添加 VNMC 实例” <#adding-a-vnmc-instance>`_."
+
+# 4c83a0155c3a4b9a8c3e224f13a38643
+#: ../../network_setup.rst:578
+msgid "Add a ASA 1000v instance."
+msgstr "添加 ASA 1000v 实例。"
+
+# df320d40f5224132a3f107b3d70f5a1f
+#: ../../network_setup.rst:580
+msgid "See `“Adding an ASA 1000v Instance” <#adding-an-asa-1000v-instance>`_."
+msgstr "参阅 `“添加 ASA 1000v 实例” <#adding-an-asa-1000v-instance>`_."
+
+# 69e5eb4309584257937bdb75fd4756ab
+#: ../../network_setup.rst:582
+msgid ""
+"Create a Network Offering and use Cisco VNMC as the service provider for "
+"desired services."
+msgstr "创建一个网络方案，使用Cisco VNMC提供你期望的服务。"
+
+# f8bc670f1d1e410d87eb7bebed9dd50b
+#: ../../network_setup.rst:585
+msgid ""
+"See `“Creating a Network Offering Using Cisco ASA 1000v” <#creating-a"
+"-network-offering-using-cisco-asa-1000v>`_."
+msgstr "参阅 `“使用Cisco ASA 1000v创建一个网络方案” <#creating-a-network-offering-using-cisco-asa-1000v>`_."
+
+# b9f4e08c2e4c47038a2651d6e8c45f9a
+#: ../../network_setup.rst:588
+msgid ""
+"Create an Isolated Guest Network by using the network offering you just "
+"created."
+msgstr "使用你刚创建的网络方案，创建一个隔离的来宾网络。"
+
+# dd9740c27dcd49caa18b1e07599c945d
+#: ../../network_setup.rst:593
+msgid "Adding a VNMC Instance"
+msgstr "添加 VNMC 实例"
+
+# c1cfcf6b2714482981a36cdf521b5676
+# b1a384e4258345fcaf5a2c57a062033e
+# fd3b312d35ff4d32b0aeba868015673e
+#: ../../network_setup.rst:595 ../../network_setup.rst:629
+#: ../../network_setup.rst:1012
+msgid "Log in to the CloudStack UI as administrator."
+msgstr "作为管理员登录到CloudStack用户界面。"
+
+# eb09321188c441c584e06b8b6ae6a816
+# fe02f530f0044688a207897b58ff2421
+#: ../../network_setup.rst:603 ../../network_setup.rst:637
+msgid "Click the Physical Network tab."
+msgstr "点击物理网络标签卡。"
+
+# 758d3cd3abe240e3b4b45b46e4fd7293
+# 3eba5d220d984b70b68217882aa7a82b
+#: ../../network_setup.rst:605 ../../network_setup.rst:639
+msgid "In the Network Service Providers node of the diagram, click Configure."
+msgstr "点击示意图'网络服务提供程序'中的配置"
+
+# b2023dfd763a46f2b35bb495d2c6caae
+# 1059ea2b826b4b21b8c818daf678ca46
+#: ../../network_setup.rst:608 ../../network_setup.rst:642
+msgid "You might have to scroll down to see this."
+msgstr "你可能需要向下滚动才能看到。"
+
+# c87503e43e8a4a25a77c4166e02fdef5
+# fdfcc18249374b7c94616ea1de46f8a3
+#: ../../network_setup.rst:610 ../../network_setup.rst:644
+msgid "Click Cisco VNMC."
+msgstr "点击Cisco VNMC"
+
+# 4f9b7772a8f346af94c367b56c696bff
+#: ../../network_setup.rst:612
+msgid "Click View VNMC Devices."
+msgstr "点击查看VNMC设备。"
+
+# 473f0d6944a641d293e217e69b575982
+#: ../../network_setup.rst:614
+msgid "Click the Add VNMC Device and provide the following:"
+msgstr "点击添加VNMC设备并提供如下信息："
+
+# 9d8b2cf61ebf4f0b9d20bde66eb2ada4
+#: ../../network_setup.rst:616
+msgid "Host: The IP address of the VNMC instance."
+msgstr "主机：VNMC实例的IP地址。"
+
+# 3056ecd7f30744acb87118d6b31faf4d
+#: ../../network_setup.rst:618
+msgid ""
+"Username: The user name of the account on the VNMC instance that CloudStack "
+"should use."
+msgstr "用户名：CloudStack需要使用VNMC实例中的账户"
+
+# d98ce3e9beba49e3b8be96b27970e903
+#: ../../network_setup.rst:627
+msgid "Adding an ASA 1000v Instance"
+msgstr "添加 ASA 1000v 实例"
+
+# d58faf4c65d447f7b1ed654fa6d773ef
+#: ../../network_setup.rst:646
+msgid "Click View ASA 1000v."
+msgstr "点击查看ASA 1000v。"
+
+# 48a7684e388a4a1199086e67b9e06fbf
+#: ../../network_setup.rst:648
+msgid "Click the Add CiscoASA1000v Resource and provide the following:"
+msgstr "点击添加Cisco ASA 1000v资源并提供如下信息："
+
+# 928909e6ab0a423cbdb8e647f25772b2
+#: ../../network_setup.rst:650
+msgid ""
+"**Host**: The management IP address of the ASA 1000v instance. The IP "
+"address is used to connect to ASA 1000V."
+msgstr "**主机**: ASA 1000v实例的管理地址。该IP地址用来连接ASA 1000V。"
+
+# 70321795345648bd9c1da27a348d9622
+#: ../../network_setup.rst:653
+msgid ""
+"**Inside Port Profile**: The Inside Port Profile configured on Cisco "
+"Nexus1000v dvSwitch."
+msgstr "**内部端口配置文件**: 在Cisco Nexus1000v分布式虚拟交换机中配置内部端口。"
+
+# 32b609836a04453fb6a045d870d7326f
+#: ../../network_setup.rst:656
+msgid ""
+"**Cluster**: The VMware cluster to which you are adding the ASA 1000v "
+"instance."
+msgstr "**群集**: 你正在添加ASA 1000v实例所在的VMware群集。"
+
+# cd7f376d7aa849a4a7247501f60ba869
+#: ../../network_setup.rst:659
+msgid "Ensure that the cluster is Cisco Nexus 1000v dvSwitch enabled."
+msgstr "确保在群集中启用了Cisco Nexus 1000v分布式虚拟交换机。"
+
+# a3980b1ab6084e3db8cd7521a2eedaea
+#: ../../network_setup.rst:665
+msgid "Creating a Network Offering Using Cisco ASA 1000v"
+msgstr "使用Cisco ASA 1000v创建一个网络方案"
+
+# 950a38dbcb1e421a9f535a092c783907
+#: ../../network_setup.rst:667
+msgid ""
+"To have Cisco ASA 1000v support for a guest network, create a network "
+"offering as follows:"
+msgstr "要来宾网络支持Cisco ASA 1000v，按照如下信息添加网络方案："
+
+# e92f8d283bd34673bd9c78e81833668e
+#: ../../network_setup.rst:670
+msgid "Log in to the CloudStack UI as a user or admin."
+msgstr "使用用户或管理员登录到CloudStack用户界面。"
+
+# 26660317d6fb41258f3d2b9a406f298d
+#: ../../network_setup.rst:672
+msgid "From the Select Offering drop-down, choose Network Offering."
+msgstr "下拉选择方案，选择网络方案："
+
+# ddecb14ca4124b1998831a3da0e5db4f
+#: ../../network_setup.rst:674
+msgid "Click Add Network Offering."
+msgstr "点击添加网络方案。"
+
+# dc73890ea66e4303ac2aa89bff57c086
+#: ../../network_setup.rst:676
+msgid "In the dialog, make the following choices:"
+msgstr "在对话框中，选择如下操作："
+
+# 8cc2e100f0cb4ebfbfaf9c9deadcbaba
+#: ../../network_setup.rst:678
+msgid "**Name**: Any desired name for the network offering."
+msgstr "**名称**: 任何网络方案的名称。"
+
+# dd1d1924540f4e5dbedd6e9a2218be68
+#: ../../network_setup.rst:680
+msgid ""
+"**Description**: A short description of the offering that can be displayed "
+"to users."
+msgstr "**描述**: 提供一个简短的方案描述。 "
+
+# 26e660fc8ea74ce28ac609f6c584cbd2
+#: ../../network_setup.rst:683
+msgid "**Network Rate**: Allowed data transfer rate in MB per second."
+msgstr "**网络速度**: 允许的数据传输速度（MB/秒）。"
+
+# dd894b5b99ef46fa91b4e2548ecbc571
+#: ../../network_setup.rst:685
+msgid ""
+"**Traffic Type**: The type of network traffic that will be carried on the "
+"network."
+msgstr "**流量类型**: 允许承载的网络流量类型。"
+
+# eae0966c87144700836fc5e823127d8b
+#: ../../network_setup.rst:688
+msgid ""
+"**Guest Type**: Choose whether the guest network is isolated or shared."
+msgstr "**来宾类型**: 选择来宾网络为隔离或共享网络。"
+
+# e54268df1bbe4a2099f3e8c010a00d9f
+#: ../../network_setup.rst:691
+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."
+msgstr "**持续性**: 表明来宾网络是否支持持续性。无需提供任何VM部署的网络，称之为持续性网络。"
+
+# 4fc96223cb514c21a8ec82d8d753d7c9
+#: ../../network_setup.rst:695
+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” <http://docs.cloudstack.apache.org/projects"
+"/cloudstack-administration/en/latest/networking2.html#about-virtual-private-"
+"clouds>`_."
+msgstr "**VPC**: 此选项表明是否在来宾网络中启用VPC。 CloudStack中的虚拟专用云(VPC)是专用、隔离的。 一个VPC可以有一个类似于传统物理网络的虚拟网络拓扑结构。有关的VPC的详细信息，请参阅 `“关于虚拟专用云” <http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/latest/networking2.html#about-virtual-private-clouds>`_."
+
+# f00fa325f09746919b9d1009245f5015
+#: ../../network_setup.rst:702
+msgid ""
+"**Specify VLAN**: (Isolated guest networks only) Indicate whether a VLAN "
+"should be specified when this offering is used."
+msgstr "**指定**: (仅隔离的来宾网络) 表明在使用这个网络方案时，是否指定VLAN。"
+
+# 3d3c6a5287e4473f8185c047e07a1974
+#: ../../network_setup.rst:705
+msgid ""
+"**Supported Services**: Use Cisco VNMC as the service provider for Firewall,"
+" Source NAT, Port Forwarding, and Static NAT to create an Isolated guest "
+"network offering."
+msgstr "**支持的服务**: 使用Cisco VNMC作为服务提供者针对隔离的来宾网络方案提供Firewall, Source NAT, Port Forwarding, 和Static NAT服务。"
+
+# bc538b1440fd4510b0825b413a042fee
+#: ../../network_setup.rst:709
+msgid ""
+"**System Offering**: Choose the system service offering that you want "
+"virtual routers to use in this network."
+msgstr "**系统方案**: 选择你想在这个网络中使用的虚拟路由器的系统服务方案。"
+
+# 26faeb25fa524771be1e615d700372ba
+#: ../../network_setup.rst:712
+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."
+msgstr "**保护模式**: 表明是否使用保护模式。在这个模式中，只有网络中第一个虚拟机启动时才分配网络资源。"
+
+# 4ef16133df3a464390c7fee43388e910
+#: ../../network_setup.rst:716
+msgid "Click OK"
+msgstr "点击确定"
+
+# a7992266e0284c60a8f1095f8f4c12e3
+#: ../../network_setup.rst:718
+msgid "The network offering is created."
+msgstr "已经创建网络方案。"
+
+# a742daa985a44045b5e372c411ffc6c2
+#: ../../network_setup.rst:722
+msgid "Reusing ASA 1000v Appliance in new Guest Networks"
+msgstr "在新的来宾网络中重复使用ASA 1000v设备"
+
+# 4a0aa5f289c5495e98a8b4baaaf6a814
+#: ../../network_setup.rst:724
+msgid ""
+"You can reuse an ASA 1000v appliance in a new guest network after the "
+"necessary cleanup. Typically, ASA 1000v is cleaned up when the logical edge "
+"firewall is cleaned up in VNMC. If this cleanup does not happen, you need to"
+" reset the appliance to its factory settings for use in new guest networks. "
+"As part of this, enable SSH on the appliance and store the SSH credentials "
+"by registering on VNMC."
+msgstr "您可以在做了必要的清理后重新在新的来宾网络中使用ASA 1000v设备。通常情况下，ASA 1000v is cleaned up when the logical edge firewall is cleaned up in VNMC。如果清理动作没有发生，你需要将设备恢复到出厂设置，才能在新的来宾网络中使用。作为其中的一部分，需要在设备上启用ssh并通过向VNMC注册存储SSH凭证。"
+
+# 20ad628b69124229b5574084ade4cb93
+#: ../../network_setup.rst:731
+msgid "Open a command line on the ASA appliance:"
+msgstr "打开ASA设备的命令行："
+
+# 105a7e29f0ad4898a7c75a9729dede0a
+#: ../../network_setup.rst:733
+msgid "Run the following:"
+msgstr "运行如下命令："
+
+# 6ab19d6d2e0042538cbbeb508cd0749c
+#: ../../network_setup.rst:739
+msgid "You are prompted with the following message:"
+msgstr "提示您如下信息："
+
+# f0bc8a73d1ca4c1dbb83304efbb74e39
+#: ../../network_setup.rst:745
+msgid "Enter N."
+msgstr "输入N。"
+
+# 8b41e1b3b97942c2834f1d7ac78e9bb1
+#: ../../network_setup.rst:747
+msgid "You will get the following confirmation message:"
+msgstr "你会得到如下确认信息："
+
+# dfb5d4fffbb5409db3ce8728237aa0bc
+#: ../../network_setup.rst:753
+msgid "Restart the appliance."
+msgstr "重启设备。"
+
+# 23cee1ad7b844c61a8902f657c8beb73
+#: ../../network_setup.rst:755
+msgid "Register the ASA 1000v appliance with the VNMC:"
+msgstr "注册ASA 1000v设备到VNMC："
+
+# dc2f284a64c245a29344154ada915e58
+#: ../../network_setup.rst:765
+msgid "External Guest Load Balancer Integration (Optional)"
+msgstr "整合外部来宾负载均衡（可选）"
+
+# 9d948a00894c4f2fa6895235bd45cd3e
+#: ../../network_setup.rst:767
+msgid ""
+"CloudStack can optionally use a Citrix NetScaler or BigIP F5 load balancer "
+"to provide load balancing services to guests. If this is not enabled, "
+"CloudStack will use the software load balancer in the virtual router."
+msgstr "CloudStack可以使用Citrix NetScaler或BigIP F5负载均衡器为客户提供负载平衡服务。如果未启用,CloudStack将使用虚拟路由器中的软件负载平衡。"
+
+# dabdfbfa1edc4c61a06597ddc02e6d92
+#: ../../network_setup.rst:772
+msgid ""
+"To install and enable an external load balancer for CloudStack management:"
+msgstr "在CloudStack管理端中安装和启用外部负载均衡："
+
+# f0578c75b13b4167a35650d6618c3b63
+#: ../../network_setup.rst:775
+msgid "Set up the appliance according to the vendor's directions."
+msgstr "根据供应商提供的说明书安装你的设备。"
+
+# acd66698614d49f18d286135e6689c3d
+#: ../../network_setup.rst:777
+msgid ""
+"Connect it to the networks carrying public traffic and management traffic "
+"(these could be the same network)."
+msgstr "连接到承载公共流量和管理流量的网络（可以是同一个网络）。"
+
+# 91c057c2c551461e8a07b2887f28b3fa
+#: ../../network_setup.rst:780
+msgid ""
+"Record the IP address, username, password, public interface name, and "
+"private interface name. The interface names will be something like \"1.1\" "
+"or \"1.2\"."
+msgstr "记录IP地址、用户名、密码、公共接口名称和专用接口名称。接口名称类似 \"1.1\" 或 \"1.2\"。"
+
+# af8d438df7ea4817814040c1ddc43feb
+#: ../../network_setup.rst:784
+msgid ""
+"Make sure that the VLANs are trunked to the management network interface."
+msgstr "确保VLAN可以通过trunk到管理网络接口。"
+
+# 13351032ab9f44cbadb116a21a1d44f3
+#: ../../network_setup.rst:787
+msgid ""
+"After the CloudStack Management Server is installed, log in as administrator"
+" to the CloudStack UI."
+msgstr "安装好CloudStack管理端后，使用管理员帐号登录CloudStack用户界面。"
+
+# aded9ee3be254e338c7d4e6b7edf7f97
+#: ../../network_setup.rst:801
+msgid "Click NetScaler or F5."
+msgstr "点击NetScaler或F5."
+
+# 1ce1bb2fbaf14b22a9dd5c8a16924159
+#: ../../network_setup.rst:803
+msgid "Click the Add button (+) and provide the following:"
+msgstr "点击（+）添加按钮并提供如下信息："
+
+# a2d8bdc55c3c40028eb64d6e1ae7c16f
+#: ../../network_setup.rst:805
+msgid "For NetScaler:"
+msgstr "对于NetScaler:"
+
+# 1f6de479819a4db684f63f0307d1dc32
+#: ../../network_setup.rst:809
+msgid ""
+"Username/Password: The authentication credentials to access the device. "
+"CloudStack uses these credentials to access the device."
+msgstr "用户名/密码：访问设备的身份验证凭证。CloudStack使用这些凭证来访问设备。"
+
+# 5208277aaa9c4a5a867a0d1fd2ec2854
+#: ../../network_setup.rst:812
+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 "类型：添加设备的类型。可以是F5 BigIP负载均衡器、NetScaler VPX、NetScaler MPX或 NetScaler SDX等设备。关于NetScaler的类型比较，请参阅CloudStack管理指南。"
+
+# a81a8b45b0364dc28f2b425a8d636be6
+#: ../../network_setup.rst:817
+msgid ""
+"Public interface: Interface of device that is configured to be part of the "
+"public network."
+msgstr "公共接口: 配置为公共网络部分的设备接口。"
+
+# 88814119e09a4dd0921efaa7b868b7d7
+#: ../../network_setup.rst:820
+msgid ""
+"Private interface: Interface of device that is configured to be part of the "
+"private network."
+msgstr "专用接口: 配置为专用网络部分的设备接口。"
+
+# a3d9da03a32f413994871acf89781192
+#: ../../network_setup.rst:823
+msgid ""
+"Number of retries. Number of times to attempt a command on the device before"
+" considering the operation failed. Default is 2."
+msgstr "重试次数：尝试控制设备失败时重试的次数。默认值是2"
+
+# 9fdbb29c229243e3ae2770682cec2268
+#: ../../network_setup.rst:826
+msgid "Capacity: The number of networks the device can handle."
+msgstr "容量：该设备能处理的网络数量。"
+
+# 746f18e5c26844098f69c70f3531eac4
+#: ../../network_setup.rst:828
+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 "专用: 当标记为专用后，这个设备只对单个帐号专用。该选项被勾选后，容量选项就没有了实际意义且值会被置为1。"
+
+# 8d71ee3b3ba24ef2b09f051382c84f02
+#: ../../network_setup.rst:834
+msgid ""
+"The installation and provisioning of the external load balancer is finished."
+" You can proceed to add VMs and NAT or load balancing rules."
+msgstr "外部负载平衡器的安装和配置完成后，你就可以开始添加虚拟机和NAT或负载均衡规则。"
+
+# 168e73c12edc4ddfb7ceadf3950a1441
+#: ../../network_setup.rst:839
+msgid "Management Server Load Balancing"
+msgstr "管理服务器负载均衡"
+
+# d1c9832bb0ec4c889904900754150662
+#: ../../network_setup.rst:841
+msgid ""
+"CloudStack can use a load balancer to provide a virtual IP for multiple "
+"Management Servers. The administrator is responsible for creating the load "
+"balancer rules for the Management Servers. The application requires "
+"persistence or stickiness across multiple sessions. The following chart "
+"lists the ports that should be load balanced and whether or not persistence "
+"is required."
+msgstr "CloudStack可以使用负载均衡器为多管理服务器提供一个虚拟IP。管理员负责创建管理服务器的负载均衡规则。应用程序需要跨多个持久性或stickiness的会话。下表列出了需要进行负载平衡的端口和是否有持久性要求。"
+
+# 8d59260980c2412d96a8664b0731bd47
+#: ../../network_setup.rst:848
+msgid "Even if persistence is not required, enabling it is permitted."
+msgstr "即使不需要持久性，也使它是允许的。"
+
+# f4777f724d85477090b55c4396cc6f35
+#: ../../network_setup.rst:851
+msgid "Source Port"
+msgstr "源端口"
+
+# 7d326aaf15ab44afa0cd31c1e3fe5590
+#: ../../network_setup.rst:851
+msgid "Destination Port"
+msgstr "目标端口"
+
+# c1da26dd22ac4a4baafe30bd8b745382
+#: ../../network_setup.rst:851
+msgid "Protocol"
+msgstr "协议"
+
+# b2352632cff44c4db47d589dc77aac90
+#: ../../network_setup.rst:851
+msgid "Persistence Required?"
+msgstr "持续请求"
+
+# 4a62a34b37034a728bdbe3708bec46b4
+#: ../../network_setup.rst:853
+msgid "80 or 443"
+msgstr "80或者443"
+
+# e53c8ab237804881bcb3014d9b434e24
+#: ../../network_setup.rst:853
+msgid "8080 (or 20400 with AJP)"
+msgstr "8080 (或者 20400 with AJP)"
+
+# 8e55087fd18c478189ed323b50a78e15
+#: ../../network_setup.rst:853
+msgid "HTTP (or AJP)"
+msgstr "HTTP (或者AJP)"
+
+# 910dae6e62db4b6c87bcd33fba33a41b
+# 625d27f875424cbca2735e4e71329264
+#: ../../network_setup.rst:854 ../../network_setup.rst:854
+msgid "8250"
+msgstr "8250"
+
+# 58601595abf7493fadec45a9912276d6
+#: ../../network_setup.rst:854
+msgid "TCP"
+msgstr "TCP"
+
+# 52192943fcd04698aaf9f3033585bc65
+# a4a53f84a8ed45d2bc84a2fef1df06d4
+#: ../../network_setup.rst:855 ../../network_setup.rst:855
+msgid "8096"
+msgstr "8096"
+
+# 2f45fefee5c04295b3ef2346baaefbf5
+#: ../../network_setup.rst:855
+msgid "HTTP"
+msgstr "HTTP"
+
+# 56b9fa972912451e936f67a7001a6771
+#: ../../network_setup.rst:858
+msgid ""
+"In addition to above settings, the administrator is responsible for setting "
+"the 'host' global config value from the management server IP to load "
+"balancer virtual IP address. If the 'host' value is not set to the VIP for "
+"Port 8250 and one of your management servers crashes, the UI is still "
+"available but the system VMs will not be able to contact the management "
+"server."
+msgstr "除了上面的设置，管理员还负责设置‘host’全局配置值，由管理服务器IP地址更改为负载均衡虚拟IP地址。如果‘host’值未设置为VIP的8250端口并且一台管理服务器崩溃时，用户界面依旧可用，但系统虚拟机将无法与管理服务器联系。"
+
+# ad76871b34a845f5b9d235414f2306e5
+#: ../../network_setup.rst:867
+msgid "Topology Requirements"
+msgstr "拓扑结构要求"
+
+# 636bca2e871e41729f5af58bc925cfbd
+#: ../../network_setup.rst:870
+msgid "Security Requirements"
+msgstr "安全需求"
+
+# b84e3ab736f74a93915035c25c5732ee
+#: ../../network_setup.rst:872
+msgid ""
+"The public Internet must not be able to access port 8096 or port 8250 on the"
+" Management Server."
+msgstr "公共互联网必须不能访问管理服务器的8096和8250端口。"
+
+# a6a9845e5dae4c1c864c36674244fecc
+#: ../../network_setup.rst:877
+msgid "Runtime Internal Communications Requirements"
+msgstr "运行时内部通信需求"
+
+# 268c7a6bce4541139e2a22fe23738d00
+#: ../../network_setup.rst:879
+msgid ""
+"The Management Servers communicate with each other to coordinate tasks. This"
+" communication uses TCP on ports 8250 and 9090."
+msgstr "管理服务器需要跟其他主机进行任务协调。该通信使用TCP协议的8250和9090端口。"
+
+# ce28693898e94e9d86c98a6e41acb59e
+#: ../../network_setup.rst:882
+msgid ""
+"The console proxy VMs connect to all hosts in the zone over the management "
+"traffic network. Therefore the management traffic network of any given pod "
+"in the zone must have connectivity to the management traffic network of all "
+"other pods in the zone."
+msgstr "CPVM跟区域中的所有主机通过管理网络通信。因此区域中任何一个Pod都必须能通过管理网络连接到其他Pod。"
+
+# 2cc6b18efa544724b94a396ea3f29997
+#: ../../network_setup.rst:887
+msgid ""
+"The secondary storage VMs and console proxy VMs connect to the Management "
+"Server on port 8250. If you are using multiple Management Servers, the load "
+"balanced IP address of the Management Servers on port 8250 must be "
+"reachable."
+msgstr "SSVM和CPVM通过8250端口与管理服务器联系。如果你使用了多个管理服务器，确保负载均衡器IP地址到管理服务器的8250端口是可达的。"
+
+# aa5c7cf265704eac9214b589ca5ec409
+#: ../../network_setup.rst:894
+msgid "Storage Network Topology Requirements"
+msgstr "存储网络拓扑要求"
+
+# e41b0df94da8462e80b7ef8072966db0
+#: ../../network_setup.rst:896
+msgid ""
+"The secondary storage NFS export is mounted by the secondary storage VM. "
+"Secondary storage traffic goes over the management traffic network, even if "
+"there is a separate storage network. Primary storage traffic goes over the "
+"storage network, if available. If you choose to place secondary storage NFS "
+"servers on the storage network, you must make sure there is a route from the"
+" management traffic network to the storage network."
+msgstr "SSVM需要挂载辅助存储中的NFS共享目录。即使有一个单独的存储网络，辅助存储的流量也会通过管理网络。如果存储网络可用，主存储的流量会通过存储网络。如果你选择辅助存储也使用存储网络，你必须确保有一条从管理网络到存储网络的路由。"
+
+# 319f0bc16b9c43b285b5381f9c1e1641
+#: ../../network_setup.rst:905
+msgid "External Firewall Topology Requirements"
+msgstr "外部防火墙拓扑要求"
+
+# ef03ddf7f4c1473aaffbab8f2ea10b90
+#: ../../network_setup.rst:907
+msgid ""
+"When external firewall integration is in place, the public IP VLAN must "
+"still be trunked to the Hosts. This is required to support the Secondary "
+"Storage VM and Console Proxy VM."
+msgstr "如果整合了外部防火墙设备，公共IP的VLAN必须通过trunk到达主机。这是支持SSVM和CPVM必须满足的。"
+
+# 8f340bd0be4a45cb9a554d08e4940824
+#: ../../network_setup.rst:913
+msgid "Advanced Zone Topology Requirements"
+msgstr "高级区域拓扑要求"
+
+# 59155e8fb1be458d919a18044910e40e
+#: ../../network_setup.rst:915
+msgid ""
+"With Advanced Networking, separate subnets must be used for private and "
+"public networks."
+msgstr "使用高级网络，专用和公共网络必须分离子网。"
+
+# 703fcda90934401caaa25a5f12b77075
+#: ../../network_setup.rst:920
+msgid "XenServer Topology Requirements"
+msgstr "XenServer拓扑要求"
+
+# 66fa97319fba4438b1ab49713ba74d45
+#: ../../network_setup.rst:922
+msgid ""
+"The Management Servers communicate with XenServer hosts on ports 22 (ssh), "
+"80 (HTTP), and 443 (HTTPs)."
+msgstr "管理服务器与XenServer服务器通过22（ssh）、80（http）和443（https）端口通信。"
+
+# 2a5693ecef9344fc85b357817cb3136c
+#: ../../network_setup.rst:927
+msgid "VMware Topology Requirements"
+msgstr "VMware拓扑要求"
+
+# 825745d3504c4edd9d998f356c622430
+#: ../../network_setup.rst:929
+msgid ""
+"The Management Server and secondary storage VMs must be able to access "
+"vCenter and all ESXi hosts in the zone. To allow the necessary access "
+"through the firewall, keep port 443 open."
+msgstr "管理服务器和SSVM必须能够访问区域中的vCenter和所有的ESXi主机。必须保证在防火墙中允许443端口。"
+
+# e5239c897a2846df832e554fc87473b0
+#: ../../network_setup.rst:933
+msgid ""
+"The Management Servers communicate with VMware vCenter servers on port 443 "
+"(HTTPs)."
+msgstr "管理服务器与VMware vCenter服务器通过443（https）端口通信。"
+
+# fb344a5b995d40428766c436e513381b
+#: ../../network_setup.rst:936
+msgid ""
+"The Management Servers communicate with the System VMs on port 3922 (ssh) on"
+" the management traffic network."
+msgstr "管理服务器与系统VM使用管理网络通过3922（ssh）端口通信。"
+
+# 45f7ce4ca7ee48d080ee6ad2646b28da
+#: ../../network_setup.rst:941
+msgid "Hyper-V Topology Requirements"
+msgstr "Hyper-V拓扑要求"
+
+# 468d7be21f9d4bd3847b12047def08d4
+#: ../../network_setup.rst:943
+msgid ""
+"CloudStack Management Server communicates with Hyper-V Agent by using HTTPS."
+" For secure communication between the Management Server and the Hyper-V "
+"host, open port 8250."
+msgstr "CloudStack管理服务器通过https与Hyper-V代理通信。管理服务器与Hyper-V主机之间的安全通信端口为8250。"
+
+# 1a3519c089b44acd951ab261264deb13
+#: ../../network_setup.rst:949
+msgid "KVM Topology Requirements"
+msgstr "KVM拓扑要求"
+
+# b11a692480274211affee6c78a638bf8
+#: ../../network_setup.rst:951
+msgid "The Management Servers communicate with KVM hosts on port 22 (ssh)."
+msgstr "管理服务器与KVM主机通过22（ssh）端口通信。"
+
+# 7586273883f448f7b24cc0138e7970b7
+#: ../../network_setup.rst:955
+msgid "LXC Topology Requirements"
+msgstr "LXC拓扑要求"
+
+# 259d6b031a2c4d2f99a0d64809c8b0a1
+#: ../../network_setup.rst:957
+msgid "The Management Servers communicate with LXC hosts on port 22 (ssh)."
+msgstr "管理服务器与LXC主机通过22（ssh）端口通信。"
+
+# 888d66b82f3446f1af4ee373439875ad
+#: ../../network_setup.rst:961
+msgid "Guest Network Usage Integration for Traffic Sentinel"
+msgstr "通过流量哨兵整合来宾网络使用情况"
+
+# 29cc34c6bee74b8d9727b38945612791
+#: ../../network_setup.rst:963
+msgid ""
+"To collect usage data for a guest network, CloudStack needs to pull the data"
+" from an external network statistics collector installed on the network. "
+"Metering statistics for guest networks are available through CloudStack’s "
+"integration with inMon Traffic Sentinel."
+msgstr "为了在来宾网络中收集网络数据，CloudStack需要从网络中安装的外部网络数据收集器中提取。并通过整合CloudStack和inMon流量哨兵实现来宾网络的数据统计。"
+
+# d397ec50b01f43649a71d382811b5c4e
+#: ../../network_setup.rst:968
+msgid ""
+"Traffic Sentinel is a network traffic usage data collection package. "
+"CloudStack can feed statistics from Traffic Sentinel into its own usage "
+"records, providing a basis for billing users of cloud infrastructure. "
+"Traffic Sentinel uses the traffic monitoring protocol sFlow. Routers and "
+"switches generate sFlow records and provide them for collection by Traffic "
+"Sentinel, then CloudStack queries the Traffic Sentinel database to obtain "
+"this information"
+msgstr "网络哨兵是一个收集网络流量使用数据的套件。CloudStack可以将流量哨兵中的信息统计到自己的使用记录中,为云基础架构的计费用户提供了依据。流量哨兵使用的流量监控协议为sFlow。路由器和交换机将生成的sFlow记录提供给流量哨兵，然后CloudStack通过查询流量哨兵的数据库来获取这些信息。"
+
+# 0421d85f71a9457aa65c99fe3edf321e
+#: ../../network_setup.rst:976
+msgid ""
+"To construct the query, CloudStack determines what guest IPs were in use "
+"during the current query interval. This includes both newly assigned IPs and"
+" IPs that were assigned in a previous time period and continued to be in "
+"use. CloudStack queries Traffic Sentinel for network statistics that apply "
+"to these IPs during the time period they remained allocated in CloudStack. "
+"The returned data is correlated with the customer account that owned each IP"
+" and the timestamps when IPs were assigned and released in order to create "
+"billable metering records in CloudStack. When the Usage Server runs, it "
+"collects this data."
+msgstr "为了构建查询，CloudStack确定了当前来宾IP的查询时间间隔。这既包含新分配的IP地址，也包含之前已被分配并且在继续使用的IP地址。CloudStack查询流量哨兵，在分配的时间段内这些IP的网络统计信息。返回的数据是账户每个IP地址被分配和释放的时间戳，以便在CloudStack中为每个账户创建计费记录。当使用服务运行时便会收集这些数据"
+
+# 711ce8174a9244d4af0b4fb81578f64b
+#: ../../network_setup.rst:986
+msgid "To set up the integration between CloudStack and Traffic Sentinel:"
+msgstr "配置整合CloudStack和流量哨兵："
+
+# 1c2e09dc5c8447d1ba4f95812f28af41
+#: ../../network_setup.rst:988
+msgid ""
+"On your network infrastructure, install Traffic Sentinel and configure it to"
+" gather traffic data. For installation and configuration steps, see inMon "
+"documentation at `Traffic Sentinel Documentation <http://inmon.com.>`_."
+msgstr "在网络基础设施中，安装和配置流量哨兵收集流量数据。 关于安装和配置步骤，请查阅inMon `流量哨兵文档 <http://inmon.com.>`_."
+
+# 412e3e6834394480af6f9e65fd4aba2d
+#: ../../network_setup.rst:993
+msgid ""
+"In the Traffic Sentinel UI, configure Traffic Sentinel to accept script "
+"querying from guest users. CloudStack will be the guest user performing the "
+"remote queries to gather network usage for one or more IP addresses."
+msgstr "在流量哨兵用户界面中，配置流量哨兵允许来宾用户使用脚本查询。CloudStack将通过执行远程查询为来宾用户的一个或多个IP和收集网络使用情况。"
+
+# 12a1bbfb3cec4016a739bec145bd8a9c
+#: ../../network_setup.rst:998
+msgid ""
+"Click File > Users > Access Control > Reports Query, then select Guest from "
+"the drop-down list."
+msgstr "点击 File > Users > Access Control > Reports Query, 然后从下拉列表中选择来宾。"
+
+# 99d0d664da654239ad897c4d6eb6b08e
+#: ../../network_setup.rst:1001
+msgid ""
+"On CloudStack, add the Traffic Sentinel host by calling the CloudStack API "
+"command addTrafficMonitor. Pass in the URL of the Traffic Sentinel as "
+"protocol + host + port (optional); for example, http://10.147.28.100:8080. "
+"For the addTrafficMonitor command syntax, see the API Reference at `API "
+"Documentation <http://cloudstack.apache.org/docs/api/index.html>`_."
+msgstr "在CloudStack中，使用API中的addTrafficMonitor命令添加流量哨兵主机。传入的流量哨兵URL类似于protocol + host + port (可选)；例如， http://10.147.28.100:8080。 关于addTrafficMonitor命令用法，请参阅API文档 `API Documentation <http://cloudstack.apache.org/docs/api/index.html>`_."
+
+# 382c1696b18d4f25a2e2b5b7cb142225
+#: ../../network_setup.rst:1008
+msgid ""
+"For information about how to call the CloudStack API, see the Developer’s "
+"Guide at `CloudStack API Developer's Guide "
+"<http://docs.cloudstack.apache.org/en/latest/index.html#developers>`_."
+msgstr "关于如何调用CloudStack API，请参阅 `CloudStack API 开发指南 <http://docs.cloudstack.apache.org/en/latest/index.html#developers>`_。"
+
+# 47106f1a9e0142eb9832c2c332d903bf
+#: ../../network_setup.rst:1014
+msgid ""
+"Select Configuration from the Global Settings page, and set the following:"
+msgstr "在全局设置页面中，查找如下参数进行设置："
+
+# fc6fdba63ec445fcb4c66fb37e5faef4
+#: ../../network_setup.rst:1017
+msgid ""
+"direct.network.stats.interval: How often you want CloudStack to query "
+"Traffic Sentinel."
+msgstr "direct.network.stats.interval: 你希望CloudStack多久收集一次流量数据。"
+
+# 41cfa755d06741f186da5ae7aacb6cee
+#: ../../network_setup.rst:1022
+msgid "Setting Zone VLAN and Running VM Maximums"
+msgstr "设置区域中VLAN和虚拟机的最大值"
+
+# a60e16faaf9041a9b9276598f5ee90f9
+#: ../../network_setup.rst:1024
+msgid ""
+"In the external networking case, every VM in a zone must have a unique guest"
+" IP address. There are two variables that you need to consider in "
+"determining how to configure CloudStack to support this: how many Zone VLANs"
+" do you expect to have and how many VMs do you expect to have running in the"
+" Zone at any one time."
+msgstr "在外部网络情况下，每个虚拟机都必须有独立的来宾IP地址。这里有两个参数你需要考虑如何在CloudStack中进行配置：在同一时刻，你希望区域中有多少VLAN和多少虚拟机在运行。"
+
+# d9028276c0544666b5e9721eeb5c8816
+#: ../../network_setup.rst:1030
+msgid ""
+"Use the following table to determine how to configure CloudStack for your "
+"deployment."
+msgstr "使用如下表格来确定如何在CloudStack部署时修改配置。"
+
+# 072f26662ea44459b4fa1cf60692e712
+#: ../../network_setup.rst:1034
+msgid "guest.vlan.bits"
+msgstr "guest.vlan.bits"
+
+# a6cb87fc1b2545d1b1ac09e37fd1be97
+#: ../../network_setup.rst:1034
+msgid "Maximum Running VMs per Zone"
+msgstr "单个区域运行虚拟机的最大值"
+
+# 95b101b8c5db46528c0540ff8c64a5cb
+#: ../../network_setup.rst:1034
+msgid "Maximum Zone VLANs"
+msgstr "区域中VLAN的最大值"
+
+# 67bdc701ec3c4dcf9cd3f5bd5e147554
+#: ../../network_setup.rst:1036
+msgid "12"
+msgstr "12"
+
+# c8d94e62ee844b4e92d52b5c6827e058
+#: ../../network_setup.rst:1036
+msgid "4096"
+msgstr "4096"
+
+# ac4e2d28b54845f1a55c70377f48d5c3
+#: ../../network_setup.rst:1036
+msgid "4094"
+msgstr "4094"
+
+# 7bbc65e86d0147368c5a3431c20f5ed3
+#: ../../network_setup.rst:1037
+msgid "11"
+msgstr "11"
+
+# 01351e134fd445688b9b975e860ff8ac
+#: ../../network_setup.rst:1037
+msgid "8192"
+msgstr "8192"
+
+# 1487356597e74d80ab906cdf7734c3e1
+#: ../../network_setup.rst:1037
+msgid "2048"
+msgstr "2048"
+
+# 210a77ae5568419ab769fe82ba44a994
+# 066cf48d71dd4eea8015322cc0295f26
+#: ../../network_setup.rst:1038 ../../network_setup.rst:1039
+msgid "10"
+msgstr "10"
+
+# ecffb57711494443b7bd29967fc90284
+#: ../../network_setup.rst:1038
+msgid "16384"
+msgstr "16384"
+
+# 77f877c5ae0c4cef92f9e8579cb50a8a
+#: ../../network_setup.rst:1038
+msgid "1024"
+msgstr "1024"
+
+# 7aec5b5262a84030b29ee9b48f82c955
+#: ../../network_setup.rst:1039
+msgid "32768"
+msgstr "32768"
+
+# bd2fc687ddab4d70beebf9747ba3aa15
+#: ../../network_setup.rst:1039
+msgid "512"
+msgstr "512"
+
+# 1735a2a4d8bd40f2a1b021cf8879de91
+#: ../../network_setup.rst:1042
+msgid ""
+"Based on your deployment's needs, choose the appropriate value of "
+"guest.vlan.bits. Set it as described in Edit the Global Configuration "
+"Settings (Optional) section and restart the Management Server."
+msgstr "基于部署的需求，选择合适的guest.vlan.bits参数值。在全局配置设置中编辑该参数，并重启管理服务。"
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/optional_installation.mo b/source/installguide/locale/zh_CN/LC_MESSAGES/optional_installation.mo
new file mode 100644
index 0000000..db8a7db
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/optional_installation.mo
Binary files differ
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/optional_installation.po b/source/installguide/locale/zh_CN/LC_MESSAGES/optional_installation.po
new file mode 100644
index 0000000..9fbad9c
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/optional_installation.po
@@ -0,0 +1,1404 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: 2014-06-30 10:25+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 3ea1be6cb6c044ee88d6bbfe51d5a36f
+#: ../../optional_installation.rst:18
+msgid "Additional Installation Options"
+msgstr "附加安装选项"
+
+# 4be66c8884c44e5c92d33460a6cfbc99
+#: ../../optional_installation.rst:20
+msgid ""
+"The next few sections describe CloudStack features above and beyond the "
+"basic deployment options."
+msgstr "除了基本的部署选项之外，接下来的几节将描述CloudStack的特性。"
+
+# d620c97521d0471dbe9914ee7961101d
+#: ../../optional_installation.rst:25
+msgid "Installing the Usage Server (Optional)"
+msgstr "安装Usage服务（可选）"
+
+# eba0c3d4623f4e30a2de16e6e1d3afbe
+#: ../../optional_installation.rst:27
+msgid ""
+"You can optionally install the Usage Server once the Management Server is "
+"configured properly. The Usage Server takes data from the events in the "
+"system and enables usage-based billing for accounts."
+msgstr "管理服务器配置完毕后，你可以选择安装Usage服务器。Usage服务器从系统事件中提取数据，便于对账户进行使用计费。"
+
+# 2132611e22ac4180882c9e149411e658
+#: ../../optional_installation.rst:31
+msgid ""
+"When multiple Management Servers are present, the Usage Server may be "
+"installed on any number of them. The Usage Servers will coordinate usage "
+"processing. A site that is concerned about availability should install Usage"
+" Servers on at least two Management Servers."
+msgstr "当存在多台管理服务器时，可以选择在它们上面安装任意数量的Usage服务器。Usage服务器会协调处理。考虑到高可用性，所以最少在两台管理服务器中安装Usage服务器。"
+
+# d0a9099047bd453a90fef5ce7d86283b
+#: ../../optional_installation.rst:38
+msgid "Requirements for Installing the Usage Server"
+msgstr "安装Usage服务器的要求"
+
+# 0443dcade9d44c4ca65794d68927d9ca
+#: ../../optional_installation.rst:40
+msgid ""
+"The Management Server must be running when the Usage Server is installed."
+msgstr "Usage服务器安装时，管理服务器必须在运行状态。"
+
+# 309364cef90c4a6fbf5a8394ac1e35c4
+#: ../../optional_installation.rst:43
+msgid ""
+"The Usage Server must be installed on the same server as a Management "
+"Server."
+msgstr "Usage服务器必须与管理服务器安装在同一台服务器中。"
+
+# a251a7029fa243b691964f23e74a9ed4
+#: ../../optional_installation.rst:48
+msgid "Steps to Install the Usage Server"
+msgstr "安装Usage服务器的步骤"
+
+# 79637a12758d457f9620403344f42b69
+#: ../../optional_installation.rst:50
+msgid "Run ./install.sh (NOT VALID, NEED CORRECTION)"
+msgstr "运行 ./install.sh (这是旧版本的安装方法，目前应通过yum命令安装usage的RPM包，此处文档应修改。)"
+
+# b47571da344e4965be7a837f8ebe714a
+#: ../../optional_installation.rst:56
+msgid ""
+"You should see a few messages as the installer prepares, followed by a list "
+"of choices."
+msgstr "你会看到几条安装准备时的消息，紧接着是一个选择列表。"
+
+# 52d83849a75649fbaba2e382ef537b2e
+#: ../../optional_installation.rst:59
+msgid "Choose \"S\" to install the Usage Server."
+msgstr "选择 \"S\" 安装使用服务器。"
+
+# 1139aed06e7d4d259522f2bf84205698
+#: ../../optional_installation.rst:65
+msgid "Once installed, start the Usage Server with the following command."
+msgstr "安装成功后，使用如下命令启动Usage服务器。"
+
+# f85323259c174815b1da8521f464edda
+#: ../../optional_installation.rst:71
+msgid ""
+"The Administration Guide discusses further configuration of the Usage "
+"Server."
+msgstr "管理指南中会进一步讨论Usage服务器的配置。"
+
+# 62c0216a817941d59e5712145ef98305
+#: ../../optional_installation.rst:76
+msgid "SSL (Optional)"
+msgstr "SSL (可选)"
+
+# 1cc339b8bee1425a9342eddde3366517
+#: ../../optional_installation.rst:78
+msgid ""
+"CloudStack provides HTTP access in its default installation. There are a "
+"number of technologies and sites which choose to implement SSL. As a result,"
+" we have left CloudStack to expose HTTP under the assumption that a site "
+"will implement its typical practice."
+msgstr "CloudStack默认提供HTTP的访问方式。有许多的技术和网站选择使用SSL。因此，我们先抛下CloudStack所使用的HTTP，假设站点使用SSL是一个典型实践。"
+
+# 592c0ac6d2e04347a4dd45ef76eafab0
+#: ../../optional_installation.rst:83
+msgid ""
+"CloudStack uses Tomcat as its servlet container. For sites that would like "
+"CloudStack to terminate the SSL session, Tomcat’s SSL access may be enabled."
+" Tomcat SSL configuration is described at "
+"http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html."
+msgstr "CloudStack使用Tomcat作为服务容器。由于CloudStack网站中断SSL会话，可能会开启Tomcatde的SSL访问。Tomcat的SSL配置描述请查阅： http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html."
+
+# 312c03f93afc4a98a82df1811062af96
+#: ../../optional_installation.rst:90
+msgid "Database Replication (Optional)"
+msgstr "数据库复制（可选）"
+
+# 7862ab06634f4e73aea90b6a69fba6d8
+#: ../../optional_installation.rst:92
+msgid ""
+"CloudStack supports database replication from one MySQL node to another. "
+"This is achieved using standard MySQL replication. You may want to do this "
+"as insurance against MySQL server or storage loss. MySQL replication is "
+"implemented using a master/slave model. The master is the node that the "
+"Management Servers are configured to use. The slave is a standby node that "
+"receives all write operations from the master and applies them to a local, "
+"redundant copy of the database. The following steps are a guide to "
+"implementing MySQL replication."
+msgstr "CloudStack支持MySQL节点间的数据库复制。这个通过标准的MySQL复制功能来实现。你这样做可能希望防止MySQL服务器或者存储损坏。MySQL复制使用master/slave的模型。master节点是直接为管理服务器所使用。slave节点为备用，接收来自master节点的所有写操作，并将它应用于本地冗余数据库。以下是实施数据库复制的步骤。"
+
+# b03832e56503442494767e262e0d5266
+#: ../../optional_installation.rst:102
+msgid ""
+"Creating a replica is not a backup solution. You should develop a backup "
+"procedure for the MySQL data that is distinct from replication."
+msgstr "创建复制并不等同于备份策略，你需要另外开发一个有别于复制的MySQL数据的备份机制。"
+
+# 8f01c4d5d9e849f7aa21e1fafec88427
+#: ../../optional_installation.rst:105
+msgid "Ensure that this is a fresh install with no data in the master."
+msgstr "确保这是一个全新安装且没有数据的master数据库节点。"
+
+# 3207c0439bb34ea28e96d4ee62ad1c2e
+#: ../../optional_installation.rst:107
+msgid ""
+"Edit my.cnf on the master and add the following in the [mysqld] section "
+"below datadir."
+msgstr "编辑master数据库的my.cnf，在[mysqld]的datadir下增加如下部分。"
+
+# 5d1dfef940ab48418d921ea6ab2104d5
+#: ../../optional_installation.rst:115
+msgid ""
+"The server\\_id must be unique with respect to other servers. The "
+"recommended way to achieve this is to give the master an ID of 1 and each "
+"slave a sequential number greater than 1, so that the servers are numbered "
+"1, 2, 3, etc."
+msgstr "考虑到其他的服务器，服务器id必须是唯一的。推荐的方式是将master的ID设置为1，后续的每个slave节点序号大于1，使得所有服务器编号如：1，2，3等。"
+
+# 3b36dc410ff54ea89e014b950f48408a
+#: ../../optional_installation.rst:120
+msgid "Restart the MySQL service. On RHEL/CentOS systems, use:"
+msgstr "重启MySQL服务。如果是RHEL/CentOS系统，命令为："
+
+# 3b34254879f64ec58d72150d828d019f
+#: ../../optional_installation.rst:126
+msgid "On Debian/Ubuntu systems, use:"
+msgstr "如果是Debian/Ubuntu系统，命令为："
+
+# 37951ede2d454f428070c346ebef21fd
+#: ../../optional_installation.rst:132
+msgid ""
+"Create a replication account on the master and give it privileges. We will "
+"use the \"cloud-repl\" user with the password \"password\". This assumes "
+"that master and slave run on the 172.16.1.0/24 network."
+msgstr "在master上创建一个用于复制的账户，并赋予权限。我们创建用户\"cloud-repl\"，密码为\"password\"。假设master和slave都运行在172.16.1.0/24网段。"
+
+# f487c49c63214050912b21eef50fb648
+#: ../../optional_installation.rst:144
+msgid "Leave the current MySQL session running."
+msgstr "离开当前正在运行的MySQL会话。"
+
+# 6c09640cbc0342ddb5e30bbdc8e8721e
+#: ../../optional_installation.rst:146
+msgid "In a new shell start a second MySQL session."
+msgstr "在新的shell中打开第二个MySQL会话。"
+
+# 19bf58dc11664a8fbec99bb36a1c660f
+#: ../../optional_installation.rst:148
+msgid "Retrieve the current position of the database."
+msgstr "检索当前数据库的位置点。"
+
+# dc3fedfd512549e9bf54e76e6af57e8a
+#: ../../optional_installation.rst:160
+msgid "Note the file and the position that are returned by your instance."
+msgstr "注意你数据库实例所返回的文件及位置点。"
+
+# 8043382dff184852bc33635d21cfd8da
+#: ../../optional_installation.rst:162
+msgid "Exit from this session."
+msgstr "退出该会话。"
+
+# 3448c24480a343129c3e323c59e1d52f
+#: ../../optional_installation.rst:164
+msgid ""
+"Complete the master setup. Returning to your first session on the master, "
+"release the locks and exit MySQL."
+msgstr "完成master安装。返回到master的第一个会话，取消锁定并退出MySQL。"
+
+# b756f3987b8345d78bb98a1da0cdf5f0
+#: ../../optional_installation.rst:171
+msgid ""
+"Install and configure the slave. On the slave server, run the following "
+"commands."
+msgstr "安装并配置slave节点。在slave服务器上，运行如下命令。"
+
+# ce5052106169447d867315b4ab5acf5c
+#: ../../optional_installation.rst:179
+msgid ""
+"Edit my.cnf and add the following lines in the [mysqld] section below "
+"datadir."
+msgstr "编辑my.cnf，在[mysqld]的datadir下增加如下部分。"
+
+# 32a595c11f6f493f8d97ee7f2eaca7ca
+#: ../../optional_installation.rst:188
+msgid "Restart MySQL. Use \"mysqld\" on RHEL/CentOS systems:"
+msgstr "重启MySQL。对于RHEL/CentOS系统，使用\"mysqld\""
+
+# 86098df7874048268b21ceab1348fc66
+#: ../../optional_installation.rst:194
+msgid "On Ubuntu/Debian systems use \"mysql.\""
+msgstr "对于Ubuntu/Debian系统，使用\"mysql.\""
+
+# cc3fe860c3244bfaabe3d4c4317c7ac8
+#: ../../optional_installation.rst:200
+msgid ""
+"Instruct the slave to connect to and replicate from the master. Replace the "
+"IP address, password, log file, and position with the values you have used "
+"in the previous steps."
+msgstr "引导slave连接master并进行复制。使用上面步骤中得到数据来替换IP地址，密码，日志文件，以及位置点。"
+
+# 9a9640cbcab74267a00aefe5b61ca112
+#: ../../optional_installation.rst:213
+msgid "Then start replication on the slave."
+msgstr "在slave上启动复制功能。"
+
+# a561331155b44e14a5a9540ccfaded76
+#: ../../optional_installation.rst:219
+msgid ""
+"Optionally, open port 3306 on the slave as was done on the master earlier."
+msgstr "在slave上可能需要开启3306端口，就像之前在master上所做的一样。"
+
+# efdf8223dd9a43a8827dd97444acf8e3
+#: ../../optional_installation.rst:222
+msgid ""
+"This is not required for replication to work. But if you choose not to do "
+"this, you will need to do it when failover to the replica occurs."
+msgstr "这对复制来说不是必须的。但如果没有做，当需要进行数据库切换时，你仍然需要去做。"
+
+# d4acbba0ba9b47bdb60497c2f80cf6cc
+#: ../../optional_installation.rst:228
+msgid "Failover"
+msgstr "故障切换"
+
+# 4937feeba9e047e3b9665410e5765ce4
+#: ../../optional_installation.rst:230
+msgid ""
+"This will provide for a replicated database that can be used to implement "
+"manual failover for the Management Servers. CloudStack failover from one "
+"MySQL instance to another is performed by the administrator. In the event of"
+" a database failure you should:"
+msgstr "这将为管理服务器提供一个复制的数据库，用于实现手动故障切换。管理员将CloudStack从一个故障MySQL实例切换到另一个。当数据库失效发生时，你应该："
+
+# e136a63f11d74984968bb1c32c84670f
+#: ../../optional_installation.rst:235
+msgid "Stop the Management Servers (via service cloudstack-management stop)."
+msgstr "停止管理服务器（通过命令：service cloudstack-management stop）"
+
+# df74922f2b5a44b0820337aecbb8703f
+#: ../../optional_installation.rst:237
+msgid "Change the replica's configuration to be a master and restart it."
+msgstr "将数据库的复本服务器修改为master并重启"
+
+# 2bc5d7c5cd654d7abc5305542ac56d8d
+#: ../../optional_installation.rst:239
+msgid "Ensure that the replica's port 3306 is open to the Management Servers."
+msgstr "确保数据库的副本服务器的3306端口开放给管理服务器。"
+
+# cfeac26dd12942b6a98e7598f0f9b130
+#: ../../optional_installation.rst:242
+msgid ""
+"Make a change so that the Management Server uses the new database. The "
+"simplest process here is to put the IP address of the new database server "
+"into each Management Server's /etc/cloudstack/management/db.properties."
+msgstr "更改使得管理服务器使用这个新的数据库。最简单的操作是在管理服务器的/etc/cloudstack/management/db.properties文件中写入新的数据库IP地址。"
+
+# b5e8464f1e5f4490bdd8efe683735901
+#: ../../optional_installation.rst:247
+msgid "Restart the Management Servers:"
+msgstr "重启管理服务器："
+
+# f83e0c3d61fd423a8768c362173078a1
+#: ../../optional_installation.rst:255
+msgid "Amazon Web Services Interface"
+msgstr "Amazon Web Services 接口"
+
+# 008a243332da45c681fc9c7358b19aae
+#: ../../optional_installation.rst:258
+msgid "Amazon Web Services Compatible Interface"
+msgstr "Amazon Web Services 兼容接口"
+
+# a82b49319a584d2bbb2ab85b707dd73e
+#: ../../optional_installation.rst:260
+msgid ""
+"CloudStack can translate Amazon Web Services (AWS) API calls to native "
+"CloudStack API calls so that users can continue using existing AWS-"
+"compatible tools. This translation service runs as a separate web "
+"application in the same tomcat server as the management server of "
+"CloudStack, listening on a different port. The Amazon Web Services (AWS) "
+"compatible interface provides the EC2 SOAP and Query APIs as well as the S3 "
+"REST API."
+msgstr "CloudStack可将AWS API调用转换为CloudStack本地调用，使得用户可以继续使用已有的AWS兼容工具。这个转换服务作为单独的web应用，就像在tomcat上的CloudStack管理服务一样，只是监听不同的端口。AWS兼容接口除了提供S3 REST API外，还提供EC2 SOAP和Query APIs。"
+
+# 4099f5d8b5b2469097a3c637c1f56b3b
+#: ../../optional_installation.rst:269
+msgid ""
+"This service was previously enabled by separate software called CloudBridge."
+" It is now fully integrated with the CloudStack management server."
+msgstr "这项服务，之前是由CloudBridge独立软件实现的。现在已经完全集成到CloudStack管理服务中。"
+
+# ba7cd83fde90433795ad9f0983796c7d
+#: ../../optional_installation.rst:273
+msgid ""
+"The compatible interface for the EC2 Query API and the S3 API are Work In "
+"Progress. The S3 compatible API offers a way to store data on the management"
+" server file system, it is not an implementation of the S3 backend."
+msgstr ""
+
+# 3d6cb62472054f53823064cd7522b0b1
+#: ../../optional_installation.rst:278
+msgid "Limitations"
+msgstr "局限性"
+
+# bd1989968b7a48d08d2c3e9cbe00b826
+#: ../../optional_installation.rst:280
+msgid "Supported only in zones that use basic networking."
+msgstr "只支持使用基本网络的zone。"
+
+# af22d4d3ba014e95bbcc09a2a5f63ded
+#: ../../optional_installation.rst:282
+msgid ""
+"Available in fresh installations of CloudStack. Not available through "
+"upgrade of previous versions."
+msgstr "仅对全新安装的CloudStack可用。通过旧版本升级的不可用。"
+
+# 89189121ce884387b3055b803759c936
+#: ../../optional_installation.rst:285
+msgid ""
+"Features such as Elastic IP (EIP) and Elastic Load Balancing (ELB) are only "
+"available in an infrastructure with a Citrix NetScaler device. Users "
+"accessing a Zone with a NetScaler device will need to use a NetScaler-"
+"enabled network offering (DefaultSharedNetscalerEIP and ELBNetworkOffering)."
+msgstr "如弹性IP(EIP)和弹性负载均衡(ELB)这些特性，仅对有Citrix NetScaler设备的架构可用。用户接入有NetScaler设备的zone时，需要使用NetScaler-enabled网络方案（DefaultSharedNetscalerEIP和ELBNetworkOffering）。"
+
+# 4063d813433749b7a6f88f762f812757
+#: ../../optional_installation.rst:293
+msgid "Supported API Version"
+msgstr "支持的API版本"
+
+# 0c8d9ebd1d4249df82a11f029752c2fe
+#: ../../optional_installation.rst:295
+msgid ""
+"The EC2 interface complies with Amazon's WDSL version dated November 15, "
+"2010, available at `http://ec2.amazonaws.com/doc/2010-11-15/ "
+"<http://ec2.amazonaws.com/doc/2010-11-15/>`_."
+msgstr "遵守亚马逊WDSL版本的EC2接口将于2010-11-15过期。可在 `http://ec2.amazonaws.com/doc/2010-11-15/ <http://ec2.amazonaws.com/doc/2010-11-15/>`获取。"
+
+# 06a91ca4b45c4bcd8f0dffb5a713eee1
+#: ../../optional_installation.rst:299
+msgid ""
+"The interface is compatible with the EC2 command-line tools *EC2 tools v. "
+"1.3.6230*, which can be downloaded at "
+"`http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip "
+"<http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip>`_."
+msgstr "接口与EC2命令行工具*EC2 tools v.1.3.6230*是兼容的。可在 `http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip <http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip>`_."
+
+# 345691ffdcae4dde88f8e11a0125cbf2
+#: ../../optional_installation.rst:304
+msgid "Work is underway to support a more recent version of the EC2 API"
+msgstr "支持更新版本的EC2 API的工作正在进行"
+
+# a79e19b1e2534aae9054a646ab2ca09e
+#: ../../optional_installation.rst:308
+msgid "Enabling the EC2 and S3 Compatible Interface"
+msgstr "使能EC2和S3兼容接口"
+
+# f6d3211b707447119b97c69471f54d9d
+#: ../../optional_installation.rst:310
+msgid ""
+"The software that provides AWS API compatibility is installed along with "
+"CloudStack. You must enable the services and perform some setup steps prior "
+"to using it."
+msgstr "提供AWS API兼容性的软件随CloudStack一起安装。在使用之前，你必须使能服务并操作一些安装步骤。"
+
+# bce3d6459eb347829649d2c27d636958
+#: ../../optional_installation.rst:314
+msgid ""
+"Set the global configuration parameters for each service to true. See "
+"`*Setting Global Configuration Parameters* <configuration.html#setting-"
+"global-configuration-parameters>`_."
+msgstr "将全局配置参数中的每项服务设置为true。详看 `*Setting Global Configuration Parameters* <configuration.html#setting-global-configuration-parameters>`_."
+
+# 0dc2fe0c2c8445b1924fc574a1c87694
+#: ../../optional_installation.rst:318
+msgid ""
+"Create a set of CloudStack service offerings with names that match the "
+"Amazon service offerings. You can do this through the CloudStack UI as "
+"described in the Administration Guide."
+msgstr "创建一组匹配亚马逊服务方案的名称。这个可以按照管理员操作手册在CloudStack界面上进行操作。"
+
+# aa33d4563eec476a845286e29c8e36b0
+#: ../../optional_installation.rst:323
+msgid ""
+"Be sure you have included the Amazon default service offering, m1.small. As "
+"well as any EC2 instance types that you will use."
+msgstr "除了可能使用的EC2实例类型，确保已包含亚马逊默认服务方案，m1.small。"
+
+# 096209e388b6481291f88c61c491b459
+#: ../../optional_installation.rst:326
+msgid ""
+"If you did not already do so when you set the configuration parameter in "
+"step 1, restart the Management Server."
+msgstr "如果按照步骤1设置了配置参数后，没有重启，那么重启管理服务器。"
+
+# a77f0d9cbc2f47c4b4cc66b9e4019fee
+#: ../../optional_installation.rst:333
+msgid "The following sections provides details to perform these steps"
+msgstr "以下内容提供了这些步骤的细节"
+
+# a08859b425eb4de583eddfd055ab1ff4
+#: ../../optional_installation.rst:337
+msgid "Enabling the Services"
+msgstr "开启服务"
+
+# 272886039ce1406aaa5cd62c9d6ef1d1
+#: ../../optional_installation.rst:339
+msgid ""
+"To enable the EC2 and S3 compatible services you need to set the "
+"configuration variables *enable.ec2.api* and *enable.s3.api* to true. You do"
+" not have to enable both at the same time. Enable the ones you need. This "
+"can be done via the CloudStack GUI by going in *Global Settings* or via the "
+"API."
+msgstr "为了使能EC2和S3兼容服务，你需要将 *enable.ec2.api *和 *enable.s3.api* 的值设置为true。以使能你所需要的服务。这个可以在CloudStack的界面上的*Global Settings*或者API来实现。"
+
+# 7dfc438f80884b509b780ac9f22a60d7
+#: ../../optional_installation.rst:345
+msgid ""
+"The snapshot below shows you how to use the GUI to enable these services"
+msgstr "下面的截图展示如何通过GUI使能这些服务。"
+
+# 3f1255dfd7c74bbbaa364bd72050b328
+#: ../../optional_installation.rst:347
+msgid "|Use the GUI to set the configuration variable to true|"
+msgstr "|Use the GUI to set the configuration variable to true|"
+
+# 8039aca5d5ee48928e08b48a66702245
+#: ../../optional_installation.rst:349
+msgid ""
+"Using the CloudStack API, the easiest is to use the so-called integration "
+"port on which you can make unauthenticated calls. In Global Settings set the"
+" port to 8096 and subsequently call the *updateConfiguration* method. The "
+"following urls shows you how:"
+msgstr "使用CloudStack API最简单的方法是使用集成接口，这个接口可以使用无验证调用。在全局设置中将这个接口设置为8096，然后调用 *updateConfiguration* 。下面的URL展示如何使用。"
+
+# 5bbf6319aa584463b00106945d4c6402
+#: ../../optional_installation.rst:359
+msgid "Once you have enabled the services, restart the server."
+msgstr "一旦使能这些服务，重启服务器。"
+
+# 83493cf546644c91bdf4168470b7038b
+#: ../../optional_installation.rst:363
+msgid "Creating EC2 Compatible Service Offerings"
+msgstr "创建EC2兼容服务方案"
+
+# 45d0f4507650452687adcaf0021cf2ec
+#: ../../optional_installation.rst:365
+msgid ""
+"You will also need to define compute service offerings with names compatible"
+" with the `Amazon EC2 instance types <http://aws.amazon.com/ec2/instance-"
+"types/>`_ API names (e.g m1.small,m1.large). This can be done via the "
+"CloudStack GUI. Go under *Service Offerings* select *Compute offering* and "
+"either create a new compute offering or modify an existing one, ensuring "
+"that the name matches an EC2 instance type API name. The snapshot below "
+"shows you how:"
+msgstr "可以定义兼容 `Amazon EC2实例类型 <http://aws.amazon.com/ec2/instance-types/>` API名称的计算服务方案。(例如m1.small,m1.large)，这个可以通过CloudStack界面进行操作。在 *Service Offerings* 中选择 *Compute offering* ，创建一个新的计算方案或者修改已存在的皆可。确保名称与EC2实例类型API名称匹配。下面的截图将展示如何操作。"
+
+# 231dd56b51ee4df98f4d20605e495f73
+#: ../../optional_installation.rst:373
+msgid ""
+"|Use the GUI to set the name of a compute service offering to an EC2 "
+"instance type API name.|"
+msgstr "|Use the GUI to set the name of a compute service offering to an EC2 instance type API name.|"
+
+# a4602805499146c2b996ff100acf74ea
+#: ../../optional_installation.rst:378
+msgid "Modifying the AWS API Port"
+msgstr "修改AWS API端口"
+
+# dd4eaeaa8fda437b849ad593f49f45b7
+#: ../../optional_installation.rst:381
+msgid ""
+"(Optional) The AWS API listens for requests on port 7080. If you prefer AWS "
+"API to listen on another port, you can change it as follows:"
+msgstr "（可选）AWS API在端口7080监听请求。如果你希望监听另外的端口，可通过如下步骤修改："
+
+# 7f4e4df38c7a4fc3a6fa8c6b2e2d3e64
+#: ../../optional_installation.rst:384
+msgid ""
+"Edit the files ``/etc/cloudstack/management/server.xml``, "
+"``/etc/cloudstack/management/server-nonssl.xml``, and "
+"``/etc/cloudstack/management/server-ssl.xml``."
+msgstr "编辑文件 ``/etc/cloudstack/management/server.xml`` , ``/etc/cloudstack/management/server-nonssl.xml`` , ``/etc/cloudstack/management/server-ssl.xml` `."
+
+# b340ed2079834e53a63d34250cd825ca
+#: ../../optional_installation.rst:388
+msgid ""
+"In each file, find the tag <Service name=\"Catalina7080\">. Under this tag, "
+"locate <Connector executor=\"tomcatThreadPool-internal\" port= ....<."
+msgstr "在每个文件中找出<Service name=\"Catalina7080\">的标签，在这个标签下，定位到<Connector executor=\"tomcatThreadPool-internal\" port= ....<"
+
+# bccb37ab25b94f20811fce519e8fdc29
+#: ../../optional_installation.rst:390
+msgid "Change the port to whatever port you want to use, then save the files."
+msgstr "将这个端口改为你想用的任何端口，并保存文件。"
+
+# 92df4f254d294e9da84bf38af22b9a91
+#: ../../optional_installation.rst:392
+msgid "Restart the Management Server."
+msgstr "重启管理服务器。"
+
+# e51c7d34c3924425b10a99d64cdfe879
+#: ../../optional_installation.rst:394
+msgid ""
+"If you re-install CloudStack, you will have to re-enable the services and if"
+" need be update the port."
+msgstr "如果你重装CloudStack，你需要重新使能服务并更新端口。"
+
+# 88a6174139da4c4186ae97897056f0a3
+#: ../../optional_installation.rst:399
+msgid "AWS API User Setup"
+msgstr "AWS API用户安装"
+
+# 57e3c2571da94b80b822e13550aadc22
+#: ../../optional_installation.rst:401
+msgid ""
+"In general, users need not be aware that they are using a translation "
+"service provided by CloudStack. They only need to send AWS API calls to "
+"CloudStack's endpoint, and it will translate the calls to the native "
+"CloudStack API. Users of the Amazon EC2 compatible interface will be able to"
+" keep their existing EC2 tools and scripts and use them with their "
+"CloudStack deployment, by specifying the endpoint of the management server "
+"and using the proper user credentials. In order to do this, each user must "
+"perform the following configuration steps:"
+msgstr "总的来说，用户不需要察觉CloudStack所提供的翻译服务。只需将AWS API调用发送到CloudStack端，然后被转换为CloudStack API。Amazon EC2兼容接口用户可继续使用已有的EC2工具和脚本，并通过指定管理服务器的端及合适的用户证书，将它们用于CloudStack部署。为此，用户需要进行如下步骤的操作："
+
+# a19dd6485e8648de8c442534a81268dc
+#: ../../optional_installation.rst:410
+msgid "Generate user credentials."
+msgstr "生成用户证书"
+
+# 2dbe2a8f81614418bdfbc25616fdc428
+#: ../../optional_installation.rst:412
+msgid "Register with the service."
+msgstr "向服务注册。"
+
+# badf72cf4c6149aaaab82e77ffd82b50
+#: ../../optional_installation.rst:414
+msgid ""
+"For convenience, set up environment variables for the EC2 SOAP command-line "
+"tools."
+msgstr "为了方便，设置关于EC2 SOAP命令行工具的环境变量。"
+
+# 3b64483d04ad424ea3f6276c6f36ff1f
+#: ../../optional_installation.rst:419
+msgid "AWS API Command-Line Tools Setup"
+msgstr "AWS API命令行工具安装"
+
+# 8d508d5a0ad04931b410fe2c700ee584
+#: ../../optional_installation.rst:421
+msgid "To use the EC2 command-line tools, the user must perform these steps:"
+msgstr "为了使用EC2命令行工具，用户需要操作以下步骤："
+
+# b99567ebf9e347608ef9aebcd5b73e11
+#: ../../optional_installation.rst:423
+msgid ""
+"Be sure you have the right version of EC2 Tools. The supported version is "
+"available at `http://s3.amazonaws.com/ec2-downloads/ec2-api-"
+"tools-1.3-62308.zip <http://s3.amazonaws.com/ec2-downloads/ec2-api-"
+"tools-1.3-62308.zip>`_."
+msgstr "确定你具有正确版本的EC2工具。所支持的版本可以在 `http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip <http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip>`_获取。"
+
+# 6dbc6273aacd474d853e027aedae2cb0
+#: ../../optional_installation.rst:427
+msgid ""
+"Set up the EC2 environment variables. This can be done every time you use "
+"the service or you can set them up in the proper shell profile. Replace the "
+"endpoint (i.e EC2\\_URL) with the proper address of your CloudStack "
+"management server and port. In a bash shell do the following."
+msgstr "设置EC2环境变量。可在每次使用服务时设置或者写入合适的shell profile文件中。将端（如EC2\\_URL）替换为合适的CloudStack管理服务器地址和端口。可在bash文件中做如下操作。"
+
+# eb3c3fbe05b346ecb25287a99bbb24e0
+#: ../../optional_installation.rst:442
+msgid "Using Timeouts to Ensure AWS API Command Completion"
+msgstr "使用超时设定确保AWS API命令完成"
+
+# 12f582bc55294c8babfc63927d334cda
+#: ../../optional_installation.rst:444
+msgid ""
+"The Amazon EC2 command-line tools have a default connection timeout. When "
+"used with CloudStack, a longer timeout might be needed for some commands. If"
+" you find that commands are not completing due to timeouts, you can specify "
+"a custom timeouts. You can add the following optional command-line "
+"parameters to any CloudStack-supported EC2 command:"
+msgstr "Amazon EC2命令行工具有默认的连接超时。在CloudStack中使用时，某些命令可能需要更长的超时。如果你发现命令在超时的时间内未完成，你可以指定用户定制超时。你可以将下面的可选命令行参数添加到任何支持CloudStack的EC2命令。"
+
+# c844003dee644c4f84e195c83fcf9c54
+#: ../../optional_installation.rst:450
+msgid "Specifies a connection timeout (in seconds)"
+msgstr "指定连接超时（秒）"
+
+# 02f0dce26c234519b8a54daa305acdd9
+#: ../../optional_installation.rst:456
+msgid "Specifies a request timeout (in seconds)"
+msgstr "指定请求超时（秒）"
+
+# 824f8a4bf59c42e8af3125231422fb72
+#: ../../optional_installation.rst:462
+msgid "Example:"
+msgstr "例如："
+
+# 402a686dcd0c4432b11580f6044c89fb
+#: ../../optional_installation.rst:469
+msgid "The timeouts optional arguments are not specific to CloudStack."
+msgstr "CloudStack中的超时可选参数并非特定"
+
+# b0e9ee13c44541ce8507ebc579484bf9
+#: ../../optional_installation.rst:473
+msgid "Supported AWS API Calls"
+msgstr "支持AWS API调用"
+
+# 8795d7b0a5a84d7d9c5c6c7d9457fa31
+#: ../../optional_installation.rst:475
+msgid ""
+"The following Amazon EC2 commands are supported by CloudStack when the AWS "
+"API compatible interface is enabled. For a few commands, there are "
+"differences between the CloudStack and Amazon EC2 versions, and these "
+"differences are noted. The underlying SOAP call for each command is also "
+"given, for those who have built tools using those calls."
+msgstr "AWS API接口被使能后，CloudStack可支持下面的Amazon EC2命令。对于少数命令，CloudStack与Amazon EC2版本间有一些差异，差异已被标识。对于使用SOAP调用建立工具的用户，与之相关的命令也已给出。"
+
+# 02d07033ab224197b16e0e3416784ad8
+#: ../../optional_installation.rst:481
+msgid "Table 1. Elastic IP API mapping"
+msgstr "表 1.弹性IP API对应表"
+
+# e6d8f396041142b2893f507bc4dcbdff
+# 1241bfdc842c4717953802b0343a7291
+# 140c555e4743444ea4c85e764c7cf200
+# b98e30783b7b49e49f7dfd0bf4770bdd
+# 8c84cf9210be42098217140c926d9e4a
+# a09d7172c4ae407bb590e916d8c4583c
+# 016288e54f0746638338d5e4c36ae2d1
+# 6d407b5c8ce4411ab3ca03fe1dfb3f73
+# 58581d2ced5a498f8d9b64e134879fdb
+# 1637dec2b0694af187c5a578dbb36e2f
+# d6d86c36942a4fe3a9719c3bc53d9733
+#: ../../optional_installation.rst:484 ../../optional_installation.rst:502
+#: ../../optional_installation.rst:512 ../../optional_installation.rst:528
+#: ../../optional_installation.rst:542 ../../optional_installation.rst:562
+#: ../../optional_installation.rst:572 ../../optional_installation.rst:588
+#: ../../optional_installation.rst:598 ../../optional_installation.rst:616
+#: ../../optional_installation.rst:630
+msgid "EC2 command"
+msgstr "EC2命令"
+
+# f329b710ee004161aac04e003d4959e7
+# 3e2771dd49b84cac9a0456674bf6122a
+# f34bafa2d5654005a150adfe0c7b5a79
+# eda190902fda413bb85d43274f6e2698
+# 805e6d29c03d44f18162de41e6340a9b
+# cdf70240f9214f8bbb9126245821d4d7
+# d5c143a174a7449e9fe5effe961a58c1
+# 288ec94c5e4c4da09b6ec91d77ff7068
+# 5400f9aed9dd4a5b83540eee1ec381a1
+# b25d524012d74bfb958f904b19d4420b
+# ea762702b2c9432b80571e0877d76f13
+#: ../../optional_installation.rst:484 ../../optional_installation.rst:502
+#: ../../optional_installation.rst:512 ../../optional_installation.rst:528
+#: ../../optional_installation.rst:542 ../../optional_installation.rst:562
+#: ../../optional_installation.rst:572 ../../optional_installation.rst:588
+#: ../../optional_installation.rst:598 ../../optional_installation.rst:616
+#: ../../optional_installation.rst:630
+msgid "SOAP call"
+msgstr "SOAP调用"
+
+# f99e71d5f94c43b08513a8b56330f4f6
+# 31ac1fa35a2c4abea464bcafc4fc181d
+# 4ff71078fae04f59ab528c8884e872b3
+# 12f8a717b46d4c6b97790eb810851aec
+# 5483f26fc9de4d429006a340fb2c2e3b
+# 487160d7dd2e45e784307da387c69f4b
+# 02684a5cd9ea43f6b9306eca1bdff457
+# b498a15517fb40569a500034444bd875
+# 26f9780627c14d46a9c2da606992d101
+# 4309dd0aa08d4453a2676af2b2baf8ea
+# d0cf4d9b46e04a2093aaa063d28b3944
+#: ../../optional_installation.rst:484 ../../optional_installation.rst:502
+#: ../../optional_installation.rst:512 ../../optional_installation.rst:528
+#: ../../optional_installation.rst:542 ../../optional_installation.rst:562
+#: ../../optional_installation.rst:572 ../../optional_installation.rst:588
+#: ../../optional_installation.rst:598 ../../optional_installation.rst:616
+#: ../../optional_installation.rst:630
+msgid "CloudStack API call"
+msgstr "CloudStack API调用"
+
+# 871494b532d14db482bf30a6ee1e728b
+#: ../../optional_installation.rst:486
+msgid "ec2-allocate-address"
+msgstr "ec2-allocate-address"
+
+# a2b89f3a70cb42d1aefe00dff62df484
+#: ../../optional_installation.rst:486
+msgid "AllocateAddress"
+msgstr "AllocateAddress"
+
+# b2a6cef1e5f64c7391495daee341c687
+#: ../../optional_installation.rst:486
+msgid "associateIpAddress"
+msgstr "associateIpAddress"
+
+# 57f93d082fb843a0bc0e05a317ca1c46
+#: ../../optional_installation.rst:488
+msgid "ec2-associate-address"
+msgstr "ec2-associate-address"
+
+# 0e3db736706747f783673f0e1bf54a9c
+#: ../../optional_installation.rst:488
+msgid "AssociateAddress"
+msgstr "AssociateAddress"
+
+# e1f6f588aaab43b8972851cde4f886be
+#: ../../optional_installation.rst:488
+msgid "enableStaticNat"
+msgstr "enableStaticNat"
+
+# 480cffbfdaf942dea2c51f1a89ad8f11
+#: ../../optional_installation.rst:490
+msgid "ec2-describe-addresses"
+msgstr "ec2-describe-addresses"
+
+# 06d41125c2ba4b32a531c4153a1d60ee
+#: ../../optional_installation.rst:490
+msgid "DescribeAddresses"
+msgstr "DescribeAddresses"
+
+# 489c67ac13ab44d6860865e68e4f22a1
+#: ../../optional_installation.rst:490
+msgid "listPublicIpAddresses"
+msgstr "listPublicIpAddresses"
+
+# 99f32f9d8ed945cda5d6dabb94b90123
+#: ../../optional_installation.rst:492
+msgid "ec2-diassociate-address"
+msgstr "ec2-diassociate-address"
+
+# d3412e0e645f4dc48a2d49b2cc7cc110
+#: ../../optional_installation.rst:492
+msgid "DisassociateAddress"
+msgstr "DisassociateAddress"
+
+# 76ba5d2d843247f0b9d520075b1180c4
+#: ../../optional_installation.rst:492
+msgid "disableStaticNat"
+msgstr "disableStaticNat"
+
+# 9dd57597d99147a99d7a6a1ba653ee54
+#: ../../optional_installation.rst:494
+msgid "ec2-release-address"
+msgstr "ec2-release-address"
+
+# a821f696dcca41e69caf9ed34dd5fe08
+#: ../../optional_installation.rst:494
+msgid "ReleaseAddress"
+msgstr "ReleaseAddress"
+
+# 9dc55b45ecfc4df6870608a6e45e06cb
+#: ../../optional_installation.rst:494
+msgid "disassociateIpAddress"
+msgstr "disassociateIpAddress"
+
+# 4db130ee1b9b47e0901be48dcf4c8112
+#: ../../optional_installation.rst:499
+msgid "Table 2. Availability Zone API mapping"
+msgstr "表 2.可用Zone API对应表"
+
+# c5d48090cfa34e38bf20cfb233425898
+#: ../../optional_installation.rst:504
+msgid "ec2-describe-availability-zones"
+msgstr "ec2-describe-availability-zones"
+
+# f86cd21880794cb6b0a7e5b82474220e
+#: ../../optional_installation.rst:504
+msgid "DescribeAvailabilityZones"
+msgstr "DescribeAvailabilityZones"
+
+# ccf5d831cb5048d28034c308da6a97d0
+#: ../../optional_installation.rst:504
+msgid "listZones"
+msgstr "listZones"
+
+# 638f0f43aae0473bae7eafa0d0058383
+#: ../../optional_installation.rst:509
+msgid "Table 3. Images API mapping"
+msgstr "表 3.镜像API对应表"
+
+# 508b851331d0421dbe112662c609e072
+#: ../../optional_installation.rst:514
+msgid "ec2-create-image"
+msgstr "ec2-create-image"
+
+# c4bb3a1d4dce43febc5d85e29a2f071e
+#: ../../optional_installation.rst:514
+msgid "CreateImage"
+msgstr "CreateImage"
+
+# df1c02038aff4e239a1a05490cabaa2b
+#: ../../optional_installation.rst:514
+msgid "createTemplate"
+msgstr "createTemplate"
+
+# eea3a24b84074b7bab9177b0f213f89a
+#: ../../optional_installation.rst:516
+msgid "ec2-deregister"
+msgstr "ec2-deregister"
+
+# 92dc634143e142c2a068ca963ce3c02a
+#: ../../optional_installation.rst:516
+msgid "DeregisterImage"
+msgstr "DeregisterImage"
+
+# eaacea2a72884286b0c663b9e8f0ba20
+#: ../../optional_installation.rst:516
+msgid "DeleteTemplate"
+msgstr "DeleteTemplate"
+
+# a0153e8b6a0e4465ae12d78be847d550
+#: ../../optional_installation.rst:518
+msgid "ec2-describe-images"
+msgstr "ec2-describe-images"
+
+# bf82b734bc3f49a3860327460324906e
+#: ../../optional_installation.rst:518
+msgid "DescribeImages"
+msgstr "DescribeImages"
+
+# df9b8d3e1bc649759cf66ddab8ec4f9a
+#: ../../optional_installation.rst:518
+msgid "listTemplates"
+msgstr "listTemplates"
+
+# af125d1fd7984bf7b33a61009f9f053a
+#: ../../optional_installation.rst:520
+msgid "ec2-register"
+msgstr "ec2-register"
+
+# 08b7fb7fa77b4fe990717d8c4781a071
+#: ../../optional_installation.rst:520
+msgid "RegisterImage"
+msgstr "RegisterImage"
+
+# 15a7a3101cae420f9a177d36e8a49755
+#: ../../optional_installation.rst:520
+msgid "registerTemplate"
+msgstr "registerTemplate"
+
+# 95f8126f5bde40e7a03ffe5b31cf0d0a
+#: ../../optional_installation.rst:525
+msgid "Table 4. Image Attributes API mapping"
+msgstr "表 4.镜像属性API对应表"
+
+# 61ba87df119f43d1ab6e755b2062c70d
+#: ../../optional_installation.rst:530
+msgid "ec2-describe-image-attribute"
+msgstr "ec2-describe-image-attribute"
+
+# 626ce97b2fc84dad9717f1b9f026d026
+#: ../../optional_installation.rst:530
+msgid "DescribeImageAttribute"
+msgstr "DescribeImageAttribute"
+
+# 47efdf23036f4569aebc625fd98610c9
+#: ../../optional_installation.rst:530
+msgid "listTemplatePermissions"
+msgstr "listTemplatePermissions"
+
+# 5b76481a1e664c7a80ad64ebc0f2f6c8
+#: ../../optional_installation.rst:532
+msgid "ec2-modify-image-attribute"
+msgstr "ec2-modify-image-attribute"
+
+# c43e186a96384512bd1de4080e7c3c3e
+#: ../../optional_installation.rst:532
+msgid "ModifyImageAttribute"
+msgstr "ModifyImageAttribute"
+
+# 6772c414652f430385bbd58d7f0330d3
+# 2e19a602fa3a416786d47b835140a477
+#: ../../optional_installation.rst:532 ../../optional_installation.rst:534
+msgid "updateTemplatePermissions"
+msgstr "updateTemplatePermissions"
+
+# bb056d700ca443ea8ac3c41a96c9ca93
+#: ../../optional_installation.rst:534
+msgid "ec2-reset-image-attribute"
+msgstr "ec2-reset-image-attribute"
+
+# 1c5e811d7b4f4b0b97c8794475b0dfe2
+#: ../../optional_installation.rst:534
+msgid "ResetImageAttribute"
+msgstr "ResetImageAttribute"
+
+# 5e99e23dd1d74fdea2908ff0c784644c
+#: ../../optional_installation.rst:539
+msgid "Table 5. Instances API mapping"
+msgstr "表 5.实例API对应表"
+
+# 94131fa6fee041b9bb87ed41c1740015
+#: ../../optional_installation.rst:544
+msgid "ec2-describe-instances"
+msgstr "ec2-describe-instances"
+
+# bc77fd6401e34b03808bae2a03dce722
+#: ../../optional_installation.rst:544
+msgid "DescribeInstances"
+msgstr "DescribeInstances"
+
+# ddd839a8bffb4e9f959c84f328993206
+# 80dab2b652cc4451b7dce841ea4b0c5e
+#: ../../optional_installation.rst:544 ../../optional_installation.rst:564
+msgid "listVirtualMachines"
+msgstr "listVirtualMachines"
+
+# f6bbd228de76472786cde350a52afbb0
+#: ../../optional_installation.rst:546
+msgid "ec2-run-instances"
+msgstr "ec2-run-instances"
+
+# d8f04cea46714aaea1e22767c6045ce1
+#: ../../optional_installation.rst:546
+msgid "RunInstances"
+msgstr "RunInstances"
+
+# 16bf652c09f14df3bf1f5a28d0be3085
+#: ../../optional_installation.rst:546
+msgid "deployVirtualMachine"
+msgstr "deployVirtualMachine"
+
+# 73c83571850b4fedb95bfce13056d186
+#: ../../optional_installation.rst:548
+msgid "ec2-reboot-instances"
+msgstr "ec2-reboot-instances"
+
+# 3f34ad1daf384d3ba3da8b9ff3750ca0
+#: ../../optional_installation.rst:548
+msgid "RebootInstances"
+msgstr "RebootInstances"
+
+# 745cf110441b4dd3b97b9c861365acb2
+#: ../../optional_installation.rst:548
+msgid "rebootVirtualMachine"
+msgstr "rebootVirtualMachine"
+
+# 5e8a67083eb74e249170d88c845fa736
+#: ../../optional_installation.rst:550
+msgid "ec2-start-instances"
+msgstr "ec2-start-instances"
+
+# f2001b78bf654274b213a674f8432d85
+#: ../../optional_installation.rst:550
+msgid "StartInstances"
+msgstr "StartInstances"
+
+# be06c051916b4c919ed831ab7627d632
+#: ../../optional_installation.rst:550
+msgid "startVirtualMachine"
+msgstr "startVirtualMachine"
+
+# db6d6153348c4b4f9c934ad1b4cef7e1
+#: ../../optional_installation.rst:552
+msgid "ec2-stop-instances"
+msgstr "ec2-stop-instances"
+
+# 0936209ce89d4a7d80fefed7e7e68bbb
+#: ../../optional_installation.rst:552
+msgid "StopInstances"
+msgstr "StopInstances"
+
+# aed253e923104237b8f072cb7149f18b
+#: ../../optional_installation.rst:552
+msgid "stopVirtualMachine"
+msgstr "stopVirtualMachine"
+
+# df41eecc274047d7b48459b161966294
+#: ../../optional_installation.rst:554
+msgid "ec2-terminate-instances"
+msgstr "ec2-terminate-instances"
+
+# 11abb0a8eda24cf1928e7100664bd7ea
+#: ../../optional_installation.rst:554
+msgid "TerminateInstances"
+msgstr "TerminateInstances"
+
+# 8036634c384c48038d0abdc470ffcc4e
+#: ../../optional_installation.rst:554
+msgid "destroyVirtualMachine"
+msgstr "destroyVirtualMachine"
+
+# 80edc0db597c4994ac9e79c8b81cc8b5
+#: ../../optional_installation.rst:559
+msgid "Table 6. Instance Attributes Mapping"
+msgstr "表 6 实例属性对应表"
+
+# 0f4f20fc51ce489ab1980676caf53257
+#: ../../optional_installation.rst:564
+msgid "ec2-describe-instance-attribute"
+msgstr "ec2-describe-instance-attribute"
+
+# 4884ab07d7a941abbcf65d35f6956ef7
+#: ../../optional_installation.rst:564
+msgid "DescribeInstanceAttribute"
+msgstr "DescribeInstanceAttribute"
+
+# 3535a243b6944759833817d5812fe907
+#: ../../optional_installation.rst:569
+msgid "Table 7. Keys Pairs Mapping"
+msgstr "表 7 密钥对应表"
+
+# a3c003668c19497192a168826e6dd752
+#: ../../optional_installation.rst:574
+msgid "ec2-add-keypair"
+msgstr "ec2-add-keypair"
+
+# fc757057d53e4355b3e39ebde3670cc4
+#: ../../optional_installation.rst:574
+msgid "CreateKeyPair"
+msgstr "CreateKeyPair"
+
+# 8b21961e21324bfbb5ca8be24c8a33eb
+#: ../../optional_installation.rst:574
+msgid "createSSHKeyPair"
+msgstr "createSSHKeyPair"
+
+# deb02c5e8676453291bbd521ff3bc979
+#: ../../optional_installation.rst:576
+msgid "ec2-delete-keypair"
+msgstr "ec2-delete-keypair"
+
+# 4580d729e28940778561e6b64aec68b2
+#: ../../optional_installation.rst:576
+msgid "DeleteKeyPair"
+msgstr "DeleteKeyPair"
+
+# c8fefc1f8ac047f1b825d7069618e3f4
+#: ../../optional_installation.rst:576
+msgid "deleteSSHKeyPair"
+msgstr "deleteSSHKeyPair"
+
+# fd10ca522a284a17ab0f0772e7eff22c
+#: ../../optional_installation.rst:578
+msgid "ec2-describe-keypairs"
+msgstr "ec2-describe-keypairs"
+
+# d64506ecf5b94b0fb34a54eb1a533ee9
+#: ../../optional_installation.rst:578
+msgid "DescribeKeyPairs"
+msgstr "DescribeKeyPairs"
+
+# 303415d20d3e4881a6441bd09ee7383e
+#: ../../optional_installation.rst:578
+msgid "listSSHKeyPairs"
+msgstr "listSSHKeyPairs"
+
+# daa6bca4cda94bb987b8771303321aa0
+#: ../../optional_installation.rst:580
+msgid "ec2-import-keypair"
+msgstr "ec2-import-keypair"
+
+# fcf840900bb646acb715f411c19c1a8c
+#: ../../optional_installation.rst:580
+msgid "ImportKeyPair"
+msgstr "ImportKeyPair"
+
+# cf7556bc11ad48819c9bc515411fdced
+#: ../../optional_installation.rst:580
+msgid "registerSSHKeyPair"
+msgstr "registerSSHKeyPair"
+
+# 27703e9dc9244cd0ad627c2fda749c65
+#: ../../optional_installation.rst:585
+msgid "Table 8. Passwords API Mapping"
+msgstr "表 8.密码API对应表"
+
+# 3c333b4280534856a4650d0768a87fe9
+#: ../../optional_installation.rst:590
+msgid "ec2-get-password"
+msgstr "ec2-get-password"
+
+# 69df9745e16f4025994bc4a4e7dd8d14
+#: ../../optional_installation.rst:590
+msgid "GetPasswordData"
+msgstr "GetPasswordData"
+
+# f1023d3b15164fa781914bc2798f4049
+#: ../../optional_installation.rst:590
+msgid "getVMPassword"
+msgstr "getVMPassword"
+
+# 42d8a55a4cdd4166903ac3f4d0893d34
+#: ../../optional_installation.rst:595
+msgid "Table 9. Security Groups API Mapping"
+msgstr "表 9.安全组API对应表"
+
+# 9f4ba75822cb44d8a563b7e19dd084cf
+#: ../../optional_installation.rst:600
+msgid "ec2-authorize"
+msgstr "ec2-authorize"
+
+# c9b993da1c7344a98757f409d8c43863
+#: ../../optional_installation.rst:600
+msgid "AuthorizeSecurityGroupIngress"
+msgstr "AuthorizeSecurityGroupIngress"
+
+# 6700b8b10b56416587800a56a46a321f
+#: ../../optional_installation.rst:600
+msgid "authorizeSecurityGroupIngress"
+msgstr "authorizeSecurityGroupIngress"
+
+# 08a42b691fe745c4886feccc73ce1adf
+#: ../../optional_installation.rst:602
+msgid "ec2-add-group"
+msgstr "ec2-add-group"
+
+# 7264f4cf327e4f1ea917878644005831
+#: ../../optional_installation.rst:602
+msgid "CreateSecurityGroup"
+msgstr "CreateSecurityGroup"
+
+# 91777fbf4341415a9685b03a9640482f
+#: ../../optional_installation.rst:602
+msgid "createSecurityGroup"
+msgstr "createSecurityGroup"
+
+# c3cf61e1d10d4f5989bfd2692699ea35
+#: ../../optional_installation.rst:604
+msgid "ec2-delete-group"
+msgstr "ec2-delete-group"
+
+# efab4d6e1d1244859fe7cbe9c4f3886e
+#: ../../optional_installation.rst:604
+msgid "DeleteSecurityGroup"
+msgstr "DeleteSecurityGroup"
+
+# 90d9bc2bd0bc4e01a3c09d3611032dbc
+#: ../../optional_installation.rst:604
+msgid "deleteSecurityGroup"
+msgstr "deleteSecurityGroup"
+
+# c72ab39125e241e18dd69018eb4943d2
+#: ../../optional_installation.rst:606
+msgid "ec2-describe-group"
+msgstr "ec2-describe-group"
+
+# ebf978cf9ead4b63b1e55ca99411cde8
+#: ../../optional_installation.rst:606
+msgid "DescribeSecurityGroups"
+msgstr "DescribeSecurityGroups"
+
+# ff1b0d61071b4256bbb3c44a6e3db98f
+#: ../../optional_installation.rst:606
+msgid "listSecurityGroups"
+msgstr "listSecurityGroups"
+
+# c0c1d7836b1247c98a6edd27afe1f758
+#: ../../optional_installation.rst:608
+msgid "ec2-revoke"
+msgstr "ec2-revoke"
+
+# e25205aeab6a4a4cb7aed5e9d3cef347
+#: ../../optional_installation.rst:608
+msgid "RevokeSecurityGroupIngress"
+msgstr "RevokeSecurityGroupIngress"
+
+# 5e02eadf7e81443da07167e7ce261298
+#: ../../optional_installation.rst:608
+msgid "revokeSecurityGroupIngress"
+msgstr "revokeSecurityGroupIngress"
+
+# fa94f34dde294a2682b384cbe8ecd23c
+#: ../../optional_installation.rst:613
+msgid "Table 10. Snapshots API Mapping"
+msgstr "表 10.快照API对应表"
+
+# ee680af94d4946678427401c45778d24
+#: ../../optional_installation.rst:618
+msgid "ec2-create-snapshot"
+msgstr "ec2-create-snapshot"
+
+# 79c2f04343b14b819176d6f4dea40c55
+#: ../../optional_installation.rst:618
+msgid "CreateSnapshot"
+msgstr "CreateSnapshot"
+
+# 94845f5ef1f54d3c968868fcf99ba1f8
+#: ../../optional_installation.rst:618
+msgid "createSnapshot"
+msgstr "createSnapshot"
+
+# 4987b9a0b58f41bab2d4c04e9e4e5a6e
+#: ../../optional_installation.rst:620
+msgid "ec2-delete-snapshot"
+msgstr "ec2-delete-snapshot"
+
+# ee365f5503714848886b5594642d29bb
+#: ../../optional_installation.rst:620
+msgid "DeleteSnapshot"
+msgstr "DeleteSnapshot"
+
+# b71dca67624b46f18e4aeba5daf8d3a2
+#: ../../optional_installation.rst:620
+msgid "deleteSnapshot"
+msgstr "deleteSnapshot"
+
+# 59cca02c7be644da8322ba049074d97f
+#: ../../optional_installation.rst:622
+msgid "ec2-describe-snapshots"
+msgstr "ec2-describe-snapshots"
+
+# 0aab43a7f50d4a74bdb336efb5f532f3
+#: ../../optional_installation.rst:622
+msgid "DescribeSnapshots"
+msgstr "DescribeSnapshots"
+
+# 36579270e4464f01a3448e680a5a85e2
+#: ../../optional_installation.rst:622
+msgid "listSnapshots"
+msgstr "listSnapshots"
+
+# 5e706e7dce774791a61ca1100cb16fde
+#: ../../optional_installation.rst:627
+msgid "Table 11. Volumes API Mapping"
+msgstr "表 11.卷API对应表"
+
+# 97db47b0a0ba4160850802f8a1f1bb90
+#: ../../optional_installation.rst:632
+msgid "ec2-attach-volume"
+msgstr "ec2-attach-volume"
+
+# 3b10700084ac4bf3b26665a5d3ebf318
+#: ../../optional_installation.rst:632
+msgid "AttachVolume"
+msgstr "AttachVolume"
+
+# 5c9f9723721245c8b718bd54cbaece22
+#: ../../optional_installation.rst:632
+msgid "attachVolume"
+msgstr "attachVolume"
+
+# 72e155b316de4a22a0dc04db2446a000
+#: ../../optional_installation.rst:634
+msgid "ec2-create-volume"
+msgstr "ec2-create-volume"
+
+# 9104debce3a241239dd215d4e3f2d3be
+#: ../../optional_installation.rst:634
+msgid "CreateVolume"
+msgstr "CreateVolume"
+
+# 556262b0cecd47f2911e5c1c52ce4cd1
+#: ../../optional_installation.rst:634
+msgid "createVolume"
+msgstr "createVolume"
+
+# 74ac980aa1474328a197b3d0838ed348
+#: ../../optional_installation.rst:636
+msgid "ec2-delete-volume"
+msgstr "ec2-delete-volume"
+
+# 4ea664000a214abaa22eef86ff955923
+#: ../../optional_installation.rst:636
+msgid "DeleteVolume"
+msgstr "DeleteVolume"
+
+# 3292da55a3b246a394511a8f8690f8f8
+#: ../../optional_installation.rst:636
+msgid "deleteVolume"
+msgstr "deleteVolume"
+
+# deceab702d224f7abc2f807131a49f98
+#: ../../optional_installation.rst:638
+msgid "ec2-describe-volume"
+msgstr "ec2-describe-volume"
+
+# 0c209718005c4d14979e9242eef22116
+#: ../../optional_installation.rst:638
+msgid "DescribeVolume"
+msgstr "DescribeVolume"
+
+# d0d300c170964f3baef0aff758b9ab73
+#: ../../optional_installation.rst:638
+msgid "listVolumes"
+msgstr "listVolumes"
+
+# 504e7f75651c40049e25fccbe5fa029f
+#: ../../optional_installation.rst:640
+msgid "ec2-detach-volume"
+msgstr "ec2-detach-volume"
+
+# f9fe5637c3564d93b15edc5988690000
+#: ../../optional_installation.rst:640
+msgid "DetachVolume"
+msgstr "DetachVolume"
+
+# d2d951565edd4f31907d8b2c2f26fd6b
+#: ../../optional_installation.rst:640
+msgid "detachVolume"
+msgstr "detachVolume"
+
+# 126ae67bf33f461a842b80e8582ee1ad
+#: ../../optional_installation.rst:647
+msgid "Examples"
+msgstr "示例"
+
+# 13a09d4f957645a1bd8fc9df7c217544
+#: ../../optional_installation.rst:649
+msgid ""
+"There are many tools available to interface with a AWS compatible API. In "
+"this section we provide a few examples that users of CloudStack can build "
+"upon."
+msgstr "有很多工具可以提供接入AWS兼容API。本节中将提供CloudStack用户一些使用用例。"
+
+# fccb92622df74eea927da84d007d391b
+#: ../../optional_installation.rst:655
+msgid "Boto Examples"
+msgstr "Boto示例"
+
+# 4831cf3fedd840a7b813bc1622eeb277
+#: ../../optional_installation.rst:657
+msgid ""
+"Boto is one of them. It is a Python package available at "
+"https://github.com/boto/boto. In this section we provide two examples of "
+"Python scripts that use Boto and have been tested with the CloudStack AWS "
+"API Interface."
+msgstr "Boto是其中一个。Python包可以在 https://github.com/boto/boto 获取。本节中提供两个使用Boto并已被CloudStack AWS API接口测试过的Python脚本示例。"
+
+# e785f67f1fed40108c89dcea285aebea
+#: ../../optional_installation.rst:662
+msgid ""
+"First is an EC2 example. Replace the Access and Secret Keys with your own "
+"and update the endpoint."
+msgstr "第一个是EC2示例，将访问和加密密钥改成你自己的，并更新端。"
+
+# 90ec7328d8c4425ea37b7739fccb8bdb
+#: ../../optional_installation.rst:665
+msgid "Example 1. An EC2 Boto example"
+msgstr "示例1.EC2 Boto示例"
+
+# 164cdb8278ff484c80d1a4d08b029bdd
+#: ../../optional_installation.rst:703
+msgid ""
+"Second is an S3 example. The S3 interface in CloudStack is obsolete. If you "
+"need an S3 interface you should look at systems like RiakCS, Ceph or "
+"GlusterFS. This example is here for completeness and can be adapted to other"
+" S3 endpoint."
+msgstr "第二个是S3示例。S3接口在CloudStack中已被废弃。如果要使用，需要考察下RiakCS，Ceph或者GlusterFS系统。这个示例已完成并可用于其他S3端。"
+
+# 1bb508e180ae42d19e41fd5eeefcc9f8
+#: ../../optional_installation.rst:705
+msgid "Example 2. An S3 Boto Example"
+msgstr "示例2.S3 Boto示例"
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/qig.mo b/source/installguide/locale/zh_CN/LC_MESSAGES/qig.mo
new file mode 100644
index 0000000..8347e14
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/qig.mo
Binary files differ
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/qig.po b/source/installguide/locale/zh_CN/LC_MESSAGES/qig.po
new file mode 100644
index 0000000..5289ea2
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/qig.po
@@ -0,0 +1,872 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: 2014-06-30 10:25+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 6cd8b0759d274663bfffb589061f6f52
+#: ../../qig.rst:18
+msgid "Quick Installation Guide for CentOS"
+msgstr "基于CentOS的快速安装指南"
+
+# 9be60313b8f24a13978f899e18120244
+#: ../../qig.rst:21
+msgid "Overview"
+msgstr "概述"
+
+# bb54b96eceb4444fa03567f9f31a1368
+#: ../../qig.rst:24
+msgid "What exactly are we building?"
+msgstr "我们真正要构建什么？"
+
+# d07669bf21f74381a55f977c98d059e5
+#: ../../qig.rst:26
+msgid ""
+"Infrastructure-as-a-Service (IaaS) clouds can be a complex thing to build, "
+"and by definition they have a plethora of options, which often lead to "
+"confusion for even experienced admins who are newcomers to building cloud "
+"platforms. The goal for this runbook is to provide a straightforward set of "
+"instructions to get you up and running with CloudStack with a minimum amount"
+" of trouble."
+msgstr "构建基础架构即服务(IaaS)云是一个很复杂的工作，它定义了过多的选项，甚至新接触云平台的管理员都很容易混乱。此篇操作手册的目的就是为减少安装CloudStack时所发生的问题并提供最直接的帮助。"
+
+# 0d4c4b0427014885a465573bca862560
+#: ../../qig.rst:34
+msgid "High level overview of the process"
+msgstr "整体过程概述"
+
+# fe3355f1acbd41399f2a663c90198e9d
+#: ../../qig.rst:36
+msgid ""
+"This runbook will focus on building a CloudStack cloud using KVM with CentOS"
+" 6.4 with NFS storage on a flat layer-2 network utilizing layer-3 network "
+"isolation (aka Security Groups), and doing it all on a single piece of "
+"hardware."
+msgstr "该操作手册将重点介绍如何搭建Cloudstack云平台: 使用CentOS 6.4作为KVM和NFS存储主机，部署于扁平二层网络并使用三层网络隔离(安全组), 所有资源集中于一台物理主机"
+
+# 121007f51b094c8aaeac5c49937a5e62
+#: ../../qig.rst:41
+msgid ""
+"KVM, or Kernel-based Virtual Machine is a virtualization technology for the "
+"Linux kernel. KVM supports native virtualization atop processors with "
+"hardware virtualization extensions."
+msgstr "KVM或Kernel-based Virtual Machine是一种基于LInux内核的虚拟化技术。KVM支持本地虚拟化，主机的CPU处理器需支持硬件虚拟化扩展。"
+
+# 0e87db8720ee41cfac5448651b99b134
+#: ../../qig.rst:45
+msgid ""
+"Security Groups act as distributed firewalls that control access to a group "
+"of virtual machines."
+msgstr "安全组起到类似分布式防火墙的作用，它可以对一组虚拟机进行访问控制。"
+
+# 605246954ba64e77b704db1e41f70958
+# b19d4cd5e52648039e330c62094e1b90
+#: ../../qig.rst:50 ../../qig.rst:441
+msgid "Prerequisites"
+msgstr "先决条件"
+
+# 9c888fde9935462b91316870b5352356
+#: ../../qig.rst:52
+msgid "To complete this runbook you'll need the following items:"
+msgstr "完成此操作手册你需要如下条件："
+
+# 7398c338e13940178c516024cdb7624e
+#: ../../qig.rst:54
+msgid "At least one computer which supports hardware virtualization."
+msgstr "至少一台支持硬件虚拟化的主机。"
+
+# 7577f66c21704f93b482ece2df1e02c8
+#: ../../qig.rst:56
+msgid ""
+"The `CentOS 6.4 x86_64 minimal install CD "
+"<http://mirrors.kernel.org/centos/6.4/isos/x86_64/CentOS-6.4-x86_64-minimal.iso>`_"
+msgstr "`\"CentOS 6.4 x86_64 minimal install CD\" <http://mirrors.kernel.org/centos/6.4/isos/x86_64/CentOS-6.4-x86_64-minimal.iso>`_"
+
+# 0be94f9998b1434b9a98e5d2eb09a094
+#: ../../qig.rst:59
+msgid ""
+"A /24 network with the gateway being at xxx.xxx.xxx.1, no DHCP should be on "
+"this network and none of the computers running CloudStack will have a "
+"dynamic address. Again this is done for the sake of simplicity."
+msgstr "一个C类(/24)网络，网关为 xxx.xxx.xxx.1，网络中不能存在DHCP服务器，所有运行Cloudstack的主机需使用静态IP地址。"
+
+# d42364c803234d79abd4f4e8ef300913
+#: ../../qig.rst:65
+msgid "Environment"
+msgstr "环境"
+
+# 67d9a987dbb94e83a8686df4283209a6
+#: ../../qig.rst:67
+msgid ""
+"Before you begin , you need to prepare the environment before you install "
+"CloudStack. We will go over the steps to prepare now."
+msgstr "首先，需要先准备要Cloudstack的安装环境，以下将详细描述准备步骤。"
+
+# 744452849b164ae08575b3bbe6199141
+#: ../../qig.rst:72
+msgid "Operating System"
+msgstr "操作系统"
+
+# 4365445c8c1c4c36bbee6f9d2b9b0e15
+#: ../../qig.rst:74
+msgid ""
+"Using the CentOS 6.4 x86_64 minimal install ISO, you'll need to install "
+"CentOS on your hardware. The defaults will generally be acceptable for this "
+"installation."
+msgstr "使用 CentOS 6.4 x86_64 minimal install 镜像，在物理主机上安装CentOS，安装过程中接受使用默认选项。"
+
+# 49109b885f65416db8533ac7b1ad5222
+#: ../../qig.rst:78
+msgid ""
+"Once this installation is complete, you'll want to connect to your freshly "
+"installed machine via SSH as the root user. Note that you should not allow "
+"root logins in a production environment, so be sure to turn off remote "
+"logins once you have finished the installation and configuration."
+msgstr "当安装完成后，需要以root身份通过SSH连接新安装的主机，注意不要以root账户登录生产环境，请在完成安装和配置后关闭远程登录。"
+
+# a105d2a14b9645b39773b7f2f43be743
+#: ../../qig.rst:87
+msgid "Configuring the network"
+msgstr "网络配置"
+
+# 37ac1900de634e79828d33b848dfbf83
+#: ../../qig.rst:89
+msgid ""
+"By default the network will not come up on your hardware and you will need "
+"to configure it to work in your environment. Since we specified that there "
+"will be no DHCP server in this environment we will be manually configuring "
+"your network interface. We will assume, for the purposes of this exercise, "
+"that eth0 is the only network interface that will be connected and used."
+msgstr "默认情况下新安装的机器并未启用网络，您需要根据实际环境进行配置。由于网络中不存在DHCP服务器，您需要手工配置网络接口。为了实现快速简化安装的目标，这里假定主机上只有eth0一个网络接口。"
+
+# 1295d8c07ee849fd9b266a0980e0eb03
+#: ../../qig.rst:95
+msgid ""
+"Connecting via the console you should login as root. Check the file "
+"/etc/sysconfig/network-scripts/ifcfg-eth0, it will look like this by "
+"default:"
+msgstr "使用root用户登录本地控制台。检查文件 /etc/sysconfig/network-scripts/ifcfg-eth0，默认情况，其内容如下所示："
+
+# ffc841b92bbd4994ae1f07ea99b908ac
+#: ../../qig.rst:105
+msgid ""
+"Unfortunately, this configuration will not permit you to connect to the "
+"network, and is also unsuitable for our purposes with CloudStack. We want to"
+" configure that file so that it specifies the IP address, netmask, etc., as "
+"shown in the following example:"
+msgstr "但是根据以上配置您无法连接到网络，对于Cloudstack也同样不适合；您需修改配置文件，指定IP地址，网络掩码等信息，如下例所示："
+
+# feeb899f3fa049019ca4e9cee4cb7d94
+#: ../../qig.rst:111
+msgid ""
+"You should not use the Hardware Address (aka the MAC address) from our "
+"example for your configuration. It is network interface specific, so you "
+"should keep the address already provided in the HWADDR directive."
+msgstr "注意，不要在你的配置中使用示例中的Hardware地址(也叫MAC地址)。该地址为网络接口所特有的，请保留你配置文件中已经提供的HWADDR字段。"
+
+# 39e9cdade6f84cee9efbcac85368b36d
+#: ../../qig.rst:129
+msgid ""
+"IP Addressing - Throughout this document we are assuming that you will have "
+"a /24 network for your CloudStack implementation. This can be any RFC 1918 "
+"network. However, we are assuming that you will match the machine address "
+"that we are using. Thus we may use 172.16.10.2 and because you might be "
+"using the 192.168.55.0/24 network you would use 192.168.55.2"
+msgstr ""
+
+# 3826ab3ca7e14ea69a7e7083749d4776
+#: ../../qig.rst:135
+msgid ""
+"Now that we have the configuration files properly set up, we need to run a "
+"few commands to start up the network:"
+msgstr "配置文件准备完毕后，需要运行命令启动网络。"
+
+# 7170ae16486348e1940a24d4b4f320bc
+#: ../../qig.rst:148
+msgid "Hostname"
+msgstr "主机名"
+
+# bc70cba9278c435ba8d50ba7f9804861
+#: ../../qig.rst:150
+msgid ""
+"CloudStack requires that the hostname be properly set. If you used the "
+"default options in the installation, then your hostname is currently set to "
+"localhost.localdomain. To test this we will run:"
+msgstr "Cloudstack要求正确设置主机名，如果安装时您接受了默认选项，主机名为localhost.localdomain，输入如下命令可以进行验证"
+
+# c0837ecf69a448a6833089b3cb700b74
+#: ../../qig.rst:158
+msgid "At this point it will likely return:"
+msgstr "在此处将返回："
+
+# c0f03d48e4f84cf99a5ae3b5695dd6d4
+#: ../../qig.rst:164
+msgid ""
+"To rectify this situation - we'll set the hostname by editing the /etc/hosts"
+" file so that it follows a similar format to this example:"
+msgstr "为了纠正这个问题，需设置主机名，通过编辑/etc/hosts 文件，将其更改为类似如下内容："
+
+# 998941fe58dd4716b4d08c3a0a8b28d7
+#: ../../qig.rst:173
+msgid ""
+"After you've modified that file, go ahead and restart the network using:"
+msgstr "更改配置文件后，重启网络服务："
+
+# d7827b49760a48e696feee0646a10476
+#: ../../qig.rst:179
+msgid ""
+"Now recheck with the hostname --fqdn command and ensure that it returns a "
+"FQDN response"
+msgstr "通过hostname --fqdn命令重新检查主机名，并确认返回了正确的FQDN"
+
+# 8ef16e261eb24be6bbc94f0183b1ee33
+#: ../../qig.rst:186
+msgid "SELinux"
+msgstr "SELinux"
+
+# 24eacbfa30f944b6a49895982406f6ee
+#: ../../qig.rst:188
+msgid ""
+"At the moment, for CloudStack to work properly SELinux must be set to "
+"permissive. We want to both configure this for future boots and modify it in"
+" the current running system."
+msgstr "当前的CloudStack需要将SELinux设置为permissive才能正常工作，您需要改变当前配置，同时将该配置持久化，使其在主机重启后仍然生效。"
+
+# ba6f0974cd5f4ef896906cfb78819190
+#: ../../qig.rst:192
+msgid ""
+"To configure SELinux to be permissive in the running system we need to run "
+"the following command:"
+msgstr "在系统运行状态下将SELinux配置为permissive需执行如下命令："
+
+# 80d187882ef94e018fbc80b3f6cf1657
+#: ../../qig.rst:199
+msgid ""
+"To ensure that it remains in that state we need to configure the file "
+"/etc/selinux/config to reflect the permissive state, as shown in this "
+"example:"
+msgstr "为确保其持久生效需更改配置文件/etc/selinux/config，设置为permissive，如下例所示："
+
+# e2dd6bd4d20445af9e40ef1dcfeffc59
+#: ../../qig.rst:219
+msgid "NTP"
+msgstr "NTP"
+
+# 7dcd6b5f047c4747b5663a3ea0a586bb
+#: ../../qig.rst:221
+msgid ""
+"NTP configuration is a necessity for keeping all of the clocks in your cloud"
+" servers in sync. However, NTP is not installed by default. So we'll install"
+" and and configure NTP at this stage. Installation is accomplished as "
+"follows:"
+msgstr "为了同步云平台中主机的时间，需要配置NTP，但NTP默认没有安装。因此需要先安装NTP，然后进行配置。通过以下命令进行安装："
+
+# dc3f1acb9d75421389f41ab343c99644
+#: ../../qig.rst:229
+msgid ""
+"The actual default configuration is fine for our purposes, so we merely need"
+" to enable it and set it to start on boot as follows:"
+msgstr "实际上默认配置项即可满足的需求，仅需启用NTP并设置为开机启动，如下所示："
+
+# 521e40c294df4b9cb34b11ddbef6c113
+#: ../../qig.rst:241
+msgid "Configuring the CloudStack Package Repository"
+msgstr "配置ClouStack软件库"
+
+# b0a49ad7b98149209a251f36c2b42c2e
+#: ../../qig.rst:243
+msgid ""
+"We need to configure the machine to use a CloudStack package repository."
+msgstr "配置主机使用CloudStack软件库。"
+
+# ccc1c3b2524242c3b7b2f4646644974f
+#: ../../qig.rst:246
+msgid ""
+"The Apache CloudStack official releases are source code. As such there are "
+"no 'official' binaries available. The full installation guide describes how "
+"to take the source release and generate RPMs and and yum repository. This "
+"guide attempts to keep things as simple as possible, and thus we are using "
+"one of the community-provided yum repositories."
+msgstr "Apache CloudStack官方发布源代码。因此没有可用的“官方”安装文件。完整的安装指南介绍了如何获取源代码，以及制作RPM包和yum软件库。本指南尽可能简化这些操作，所以直接使用社区提供的yum软件库。"
+
+# 839459c6f46e4c4fa3626c7f84a78e14
+#: ../../qig.rst:252
+msgid ""
+"To add the CloudStack repository, create /etc/yum.repos.d/cloudstack.repo "
+"and insert the following information."
+msgstr "添加CloudStack软件仓库，创建/etc/yum.repos.d/cloudstack.repo文件，并添加如下信息。"
+
+# 4a110af8c49c4b398c36065cc45c8f60
+#: ../../qig.rst:265
+msgid "NFS"
+msgstr "NFS"
+
+# 19505af6684e49c794879229d714e4aa
+#: ../../qig.rst:267
+msgid ""
+"Our configuration is going to use NFS for both primary and secondary "
+"storage. We are going to go ahead and setup two NFS shares for those "
+"purposes. We'll start out by installing nfs-utils."
+msgstr "本文档将配置的环境使用NFS做为主存储和辅助存储，需配置两个NFS共享目录，在此之前需先安装nfs-utils："
+
+# 6cb16ffd970344c3ace837183e3c39ff
+#: ../../qig.rst:275
+msgid ""
+"We now need to configure NFS to serve up two different shares. This is "
+"handled comparatively easily in the /etc/exports file. You should ensure "
+"that it has the following content:"
+msgstr "接下来需配置NFS提供两个不同的挂载点。通过编辑/etc/exports文件即可简单实现。确保这个文件中包含下面内容："
+
+# cc8ef4b76bf64c62b6c5e89b6ee0fcd9
+#: ../../qig.rst:284
+msgid ""
+"You will note that we specified two directories that don't exist (yet) on "
+"the system. We'll go ahead and create those directories and set permissions "
+"appropriately on them with the following commands:"
+msgstr "注意配置文件中指定了系统中两个并不存在的目录，下面需要创建这些目录并设置合适的权限，对应的命令如下所示："
+
+# 518439ba2be945f9a7e3fbab2a21cdbe
+#: ../../qig.rst:293
+msgid ""
+"CentOS 6.x releases use NFSv4 by default. NFSv4 requires that domain setting"
+" matches on all clients. In our case, the domain is cloud.priv, so ensure "
+"that the domain setting in /etc/idmapd.conf is uncommented and set as "
+"follows: Domain = cloud.priv"
+msgstr "CentOS 6.x 版本默认使用NFSv4，NFSv4要求所有客户端的域设置匹配，这里以设置cloud.priv为例，请确保文件/etc/idmapd.conf中的域设置没有被注释掉，并设置为以下内容："
+
+# b485a87031a94a76a3bf754cdb5cefd2
+#: ../../qig.rst:298
+msgid ""
+"Now you'll need uncomment the configuration values in the file "
+"/etc/sysconfig/nfs"
+msgstr "在/etc/sysconfig/nfs文件中取消如下选项的注释："
+
+# e876c59eae014aa3baa25c6b7c1401a3
+#: ../../qig.rst:310
+msgid ""
+"Now we need to configure the firewall to permit incoming NFS connections. "
+"Edit the file /etc/sysconfig/iptables"
+msgstr "接下来还需配置防火墙策略，允许NFS客户端访问。编辑文件/etc/sysconfig/iptables"
+
+# d7b296589dc34344af087b4fb44f8a39
+#: ../../qig.rst:327
+msgid "Now you can restart the iptables service with the following command:"
+msgstr "通过以下命令重新启动iptables服务："
+
+# 2174509b3845456db7eab82fa2adba29
+#: ../../qig.rst:333
+msgid ""
+"We now need to configure the nfs service to start on boot and actually start"
+" it on the host by executing the following commands:"
+msgstr "最后需要配置NFS服务为开机自启动，执行如下命令："
+
+# 3df2c4989e10469ebd9d8e536e5a1d36
+#: ../../qig.rst:345
+msgid "Management Server Installation"
+msgstr "管理服务器安装"
+
+# 9a58ef21fdd64508a4a73a7a0a6ca8ab
+#: ../../qig.rst:347
+msgid ""
+"We're going to install the CloudStack management server and surrounding "
+"tools."
+msgstr "接下来进行CloudStack管理节点和相关工具的安装。"
+
+# 6ca0e5d18a4f4af287c3a9e04ddadc5d
+#: ../../qig.rst:351
+msgid "Database Installation and Configuration"
+msgstr "数据库安装和配置"
+
+# 946061f8b1cb4c97b95a950dae96c2e3
+#: ../../qig.rst:353
+msgid ""
+"We'll start with installing MySQL and configuring some options to ensure it "
+"runs well with CloudStack."
+msgstr "首先安装MySQL，并对它进行配置，以确保CloudStack运行正常。"
+
+# 51eb7503da9a4eb995968d6041b1e2ac
+#: ../../qig.rst:356
+msgid "Install by running the following command:"
+msgstr "运行如下命令安装："
+
+# 36d9b86e7e3248b784a3dcf59fc552e3
+#: ../../qig.rst:362
+msgid ""
+"With MySQL now installed we need to make a few configuration changes to "
+"/etc/my.cnf. Specifically we need to add the following options to the "
+"[mysqld] section:"
+msgstr "MySQL安装完成后，需更改其配置文件/etc/my.cnf。在[mysqld]下添加下列参数："
+
+# a5c5a266adba4e3290312bca285a9f01
+#: ../../qig.rst:374
+msgid ""
+"Now that MySQL is properly configured we can start it and configure it to "
+"start on boot as follows:"
+msgstr "正确配置MySQL后，启动它并配置为开机自启动："
+
+# 1fe575a11b7a4071b4e6a29dcc38cf07
+# 0b4d699f167b42bb9b193792f0bd0725
+#: ../../qig.rst:384 ../../qig.rst:463
+msgid "Installation"
+msgstr "安装"
+
+# 48a0def962364fb793fd558db7a83c29
+#: ../../qig.rst:386
+msgid ""
+"We are now going to install the management server. We do that by executing "
+"the following command:"
+msgstr "现在将要开始安装管理服务器。执行以下命令："
+
+# ffbb50ab243643e9b5435264bfd61bf7
+#: ../../qig.rst:393
+msgid ""
+"With the application itself installed we can now setup the database, we'll "
+"do that with the following command and options:"
+msgstr "在程序执行完毕后，需初始化数据库，通过如下命令和选项完成："
+
+# 59e045efceb0436b8cecf6c9c5eda843
+#: ../../qig.rst:400
+msgid ""
+"When this process is finished, you should see a message like \"CloudStack "
+"has successfully initialized the database.\""
+msgstr "当该过程结束后，您应该可以看到类似信息：\"CloudStack has successfully initialized the database.\"。"
+
+# 5e4571669d1042a1b867fb1b24dbfbdd
+#: ../../qig.rst:403
+msgid ""
+"Now that the database has been created, we can take the final step in "
+"setting up the management server by issuing the following command:"
+msgstr "数据库创建后，最后一步是配置管理服务器，执行如下命令："
+
+# 33ce2bfd534f433e8a6cd4f7c6e1c166
+#: ../../qig.rst:412
+msgid "System Template Setup"
+msgstr "上传系统模板"
+
+# 0d95e3d0c71b4c45858b31f77dde036e
+#: ../../qig.rst:414
+msgid ""
+"CloudStack uses a number of system VMs to provide functionality for "
+"accessing the console of virtual machines, providing various networking "
+"services, and managing various aspects of storage. This step will acquire "
+"those system images ready for deployment when we bootstrap your cloud."
+msgstr "CloudStack通过一系列系统虚拟机提供功能，如访问虚拟机控制台，如提供各类网络服务，以及管理辅助存储的中的各类资源。该步骤会获取系统虚拟机模板，用于云平台引导后系统虚拟机的部署。"
+
+# d3c498d585ab4741bd2c27b0b2084745
+#: ../../qig.rst:419
+msgid ""
+"Now we need to download the system VM template and deploy that to the share "
+"we just mounted. The management server includes a script to properly "
+"manipulate the system VMs images."
+msgstr "然后需要下载系统虚拟机模板，并把这些模板部署于刚才创建的辅助存储中；管理服务器包含一个脚本可以正确的操作这些系统虚拟机模板："
+
+# 92903e9533534b6fb4148c0635069661
+#: ../../qig.rst:427
+msgid ""
+"That concludes our setup of the management server. We still need to "
+"configure CloudStack, but we will do that after we get our hypervisor set "
+"up."
+msgstr "以上是管理服务器的安装和配置过程；在配置CloudStack之前，仍需配置hypervisor。"
+
+# 7f1393a48e184b35b9bb4a8b95ac1a13
+#: ../../qig.rst:432
+msgid "KVM Setup and Installation"
+msgstr "KVM配置和安装"
+
+# d098ee902a904e3c8736a2d3464fd49c
+#: ../../qig.rst:434
+msgid ""
+"KVM is the hypervisor we'll be using - we will recover the initial setup "
+"which has already been done on the hypervisor host and cover installation of"
+" the agent software, you can use the same steps to add additional KVM nodes "
+"to your CloudStack environment."
+msgstr "本文档使用KVM作为hypervisor，下文将回顾最如何配置hypervisor主机，其中大部分配置工作已在配置管理节点时完成；接下来描述如何安装agent。您可以应用相同的步骤添加额外的KVM节点到CloudStack环境中。"
+
+# e02d098f8e1a4eb081a496f88791dac0
+#: ../../qig.rst:443
+msgid ""
+"We explicitly are using the management server as a compute node as well, "
+"which means that we have already performed many of the prerequisite steps "
+"when setting up the management server, but we will list them here for "
+"clarity. Those steps are:"
+msgstr "本文档描述的环境使用管理服务器同时作为计算节点，这意味着很多先决步骤已经在搭建管理服务器时完成；但为了清晰起见，仍然列出相关步骤："
+
+# fdf9d335282f4fe98e99728f3399c1fd
+#: ../../qig.rst:448
+msgid ":ref:`conf-network`"
+msgstr ":ref:`conf-network`"
+
+# 445994f799ba4e909ce0c0a186f2f31d
+#: ../../qig.rst:450
+msgid ":ref:`conf-hostname`"
+msgstr ":ref:`conf-hostname`"
+
+# ab93010654414278b9eed8a6c99160e0
+#: ../../qig.rst:452
+msgid ":ref:`conf-selinux`"
+msgstr ":ref:`conf-selinux`"
+
+# fdb31d5daa78457382f913417f11a829
+#: ../../qig.rst:454
+msgid ":ref:`conf-ntp`"
+msgstr ":ref:`conf-ntp`"
+
+# c13c6efacec5485ab038723e8f958003
+#: ../../qig.rst:456
+msgid ":ref:`qigconf-pkg-repo`"
+msgstr ":ref:`qigconf-pkg-repo`"
+
+# e9a76dadeb804696ac9ac907ed256fbf
+#: ../../qig.rst:458
+msgid ""
+"You shouldn't need to do that for the management server, of course, but any "
+"additional hosts will need for you to complete the above steps."
+msgstr "你不需要在管理节点上执行这些操作，当然，如果您需要添加额外的主机以上步骤仍然需要执行。"
+
+# adc6a52e07e645149ab0fd5b03cc2e22
+#: ../../qig.rst:465
+msgid ""
+"Installation of the KVM agent is trivial with just a single command, but "
+"afterwards we'll need to configure a few things."
+msgstr "安装KVM代理仅仅需要一条简单的命令，但之后我们需要进行一些配置。"
+
+# 9b94ad0de8bc42b6bfed991871ad6c23
+#: ../../qig.rst:474
+msgid "KVM Configuration"
+msgstr "配置KVM"
+
+# 41d6a9265c8d47f2b9fb9b657cf8dd10
+#: ../../qig.rst:476
+msgid "We have two different parts of KVM to configure, libvirt, and QEMU."
+msgstr "KVM中我们有两部分需要进行配置, libvirt和QEMU."
+
+# e4f062f561b8411ab57677d08500d1fe
+#: ../../qig.rst:480
+msgid "QEMU Configuration"
+msgstr "配置QEMU"
+
+# 815a9beec20b476d9771e7ef18b8c600
+#: ../../qig.rst:482
+msgid ""
+"KVM configuration is relatively simple at only a single item. We need to "
+"edit the QEMU VNC configuration. This is done by editing "
+"/etc/libvirt/qemu.conf and ensuring the following line is present and "
+"uncommented."
+msgstr "KVM的配置项相对简单，仅需配置一项。编辑QEMU VNC配置文件/etc/libvirt/qemu.conf并取消如下行的注释。"
+
+# 975c5c294f1442bf81c674603302b96d
+#: ../../qig.rst:488
+msgid "vnc_listen=0.0.0.0"
+msgstr "vnc_listen=0.0.0.0"
+
+# fa6d60015c4f40879deddfeb0aa1faba
+#: ../../qig.rst:492
+msgid "Libvirt Configuration"
+msgstr "配置Libvirt"
+
+# 77d8c22ce01a436c86a3356db1be9f2d
+#: ../../qig.rst:494
+msgid ""
+"CloudStack uses libvirt for managing virtual machines. Therefore it is vital"
+" that libvirt is configured correctly. Libvirt is a dependency of cloud-"
+"agent and should already be installed."
+msgstr "CloudStack使用libvirt管理虚拟机。因此正确的配置libvirt至关重要。Libvirt属于cloudstack-agent的依赖组件，应提前安装好。"
+
+# 99f2fbc9c2454f3487ad43f84bb08a12
+#: ../../qig.rst:498
+msgid ""
+"In order to have live migration working libvirt has to listen for unsecured "
+"TCP connections. We also need to turn off libvirts attempt to use Multicast "
+"DNS advertising. Both of these settings are in /etc/libvirt/libvirtd.conf"
+msgstr "为了实现动态迁移，libvirt需要监听使用非加密的TCP连接。还需要关闭libvirts尝试使用组播DNS进行广播。这些都是在 /etc/libvirt/libvirtd.conf文件中进行配置。"
+
+# 9fc492fb10044ee0844b1d25e91f50ee
+#: ../../qig.rst:502
+msgid "Set the following paramaters:"
+msgstr "设置下列参数："
+
+# 95403c520e0647c88d0026cb30086615
+#: ../../qig.rst:512
+msgid ""
+"Turning on \"listen_tcp\" in libvirtd.conf is not enough, we have to change "
+"the parameters as well we also need to modify /etc/sysconfig/libvirtd:"
+msgstr "仅仅在libvirtd.conf中启用\"listen_tcp\"还不够，我们还必须修改/etc/sysconfig/libvirtd中的参数:"
+
+# d56b9b860fbc4a259d021e12bda7bc3c
+#: ../../qig.rst:515
+msgid "Uncomment the following line:"
+msgstr "取消如下行的注释："
+
+# 169629893c8f43fa88410c11c1009c5f
+#: ../../qig.rst:521
+msgid "Restart libvirt"
+msgstr "重启libvirt服务"
+
+# 18f1fb4c4c8a42b386267c081b445d95
+#: ../../qig.rst:529
+msgid "KVM configuration complete"
+msgstr "KVM配置完成"
+
+# 03532dcd2b4c4677a2f98e4a0d94594e
+#: ../../qig.rst:530
+msgid ""
+"That concludes our installation and configuration of KVM, and we'll now move"
+" to using the CloudStack UI for the actual configuration of our cloud."
+msgstr "以上内容是针对KVM的安装和配置，下面将介绍如何使用CloudStack用户界面配置云平台。"
+
+# 952b415ac3874c7f9d04f5e587352ac9
+#: ../../qig.rst:535
+msgid "Configuration"
+msgstr "配置"
+
+# 523a82da5a444efe823f80fb51e88066
+#: ../../qig.rst:537
+msgid ""
+"As we noted before we will be using security groups to provide isolation and"
+" by default that implies that we'll be using a flat layer-2 network. It also"
+" means that the simplicity of our setup means that we can use the quick "
+"installer."
+msgstr "如上文所述，该手册所描述的环境将使用安全组提供网络隔离，这意味着您的安装环境仅需要一个扁平的二层网络，同样意味着较为简单的配置和快速的安装。"
+
+# cbed6a65a67b45e6af0fb6ffff271769
+#: ../../qig.rst:544
+msgid "UI Access"
+msgstr "访问用户界面"
+
+# dda96068dfd5400c8163c00981ab2bb8
+#: ../../qig.rst:546
+msgid ""
+"To get access to CloudStack's web interface, merely point your browser to "
+"http://172.16.10.2:8080/client The default username is 'admin', and the "
+"default password is 'password'. You should see a splash screen that allows "
+"you to choose several options for setting up CloudStack. You should choose "
+"the Continue with Basic Setup option."
+msgstr "要访问CloudStack的WEB界面，仅需在浏览器访问 http://172.16.10.2:8080/client ，使用默认用户'admin'和密码'password'来登录。第一次登录可以看到欢迎界面，提供两个选项设置CloudStack。请选择继续执行基本配置安装。"
+
+# bbb1c7f2891a4ec4a83d9d55bcfa3675
+#: ../../qig.rst:552
+msgid ""
+"You should now see a prompt requiring you to change the password for the "
+"admin user. Please do so."
+msgstr "此时您会看到提示，要求为admin用户更改密码，请更新密码后继续。"
+
+# 3be78f0dce5244e4b9131f8c619ad9a4
+#: ../../qig.rst:557
+msgid "Setting up a Zone"
+msgstr "配置区域"
+
+# 0aba2895b7c74bce8a058589e3983a7c
+#: ../../qig.rst:559
+msgid ""
+"A zone is the largest organization entity in CloudStack - and we'll be "
+"creating one, this should be the screen that you see in front of you now. "
+"And for us there are 5 pieces of information that we need."
+msgstr "区域是Cloudstack中最大的组织单位，下面将要讲述如何创建，此时屏幕中显示的是区域添加页面，这里需要您提供5部分信。"
+
+# 678aeb5fe9214685805c844269bc9fb8
+#: ../../qig.rst:563
+msgid "Name - we will set this to the ever-descriptive 'Zone1' for our cloud."
+msgstr "名称 - 提供描述性的名称，这里以\"Zone1\"为例"
+
+# 63f27019f41b44649ba00f8ca77ec852
+#: ../../qig.rst:565
+msgid "Public DNS 1 - we will set this to '8.8.8.8' for our cloud."
+msgstr "公共DNS1 - 我们输入8.8.8.8。"
+
+# b747f07282f845c1b0e23cb76e573616
+#: ../../qig.rst:567
+msgid "Public DNS 2 - we will set this to '8.8.4.4' for our cloud."
+msgstr "公共DNS 2 - 我们输入8.8.4.4。"
+
+# b3ccf7d2313948489f913f8c32a9aeb7
+#: ../../qig.rst:569
+msgid "Internal DNS1 - we will also set this to '8.8.8.8' for our cloud."
+msgstr "内部DNS 1 - 我们同样输入8.8.8.8。"
+
+# d9a7755ae183447788f746bd5a20a8ed
+#: ../../qig.rst:571
+msgid "Internal DNS2 - we will also set this to '8.8.4.4' for our cloud."
+msgstr "内部DNS 2 - 我们同样输入8.8.4.4。"
+
+# d29af6bf0c6f453c99632dcde7d46008
+#: ../../qig.rst:574
+msgid ""
+"CloudStack distinguishes between internal and public DNS. Internal DNS is "
+"assumed to be capable of resolving internal-only hostnames, such as your NFS"
+" server’s DNS name. Public DNS is provided to the guest VMs to resolve "
+"public IP addresses. You can enter the same DNS server for both types, but "
+"if you do so, you must make sure that both internal and public IP addresses "
+"can route to the DNS server. In our specific case we will not use any names "
+"for resources internally, and we have indeed them set to look to the same "
+"external resource so as to not add a namerserver setup to our list of "
+"requirements."
+msgstr "CloudStack分为内部和公共DNS。内部DNS只负责解析内部主机名，比如NFS服务器的DNS名称。公共DNS为虚拟机提供公共IP地址解析。你可以指定同一个DNS服务器，但如果这样做，你必须确保内部和公共IP地址都能路由到该DNS服务器。在我们的案例中对内部资源不使用DNS名称，因此这里将其设置为与外部DNS一致用以简化安装，从而不必为此再安装一台DNS服务器。"
+
+# d1ccf0a04f8d407f92b076a97ca934aa
+#: ../../qig.rst:586
+msgid "Pod Configuration"
+msgstr "配置提供点"
+
+# d633c33294f54ed9b55112c0f0f4c4b6
+#: ../../qig.rst:588
+msgid ""
+"Now that we've added a Zone, the next step that comes up is a prompt for "
+"information regading a pod. Which is looking for several items."
+msgstr "到这里我们已经添加了一个区域，下一步会显示添加提供点所需信息："
+
+# 5d8b827958834106bb8322c4b726e589
+#: ../../qig.rst:591
+msgid "Name - We'll use Pod1 for our cloud."
+msgstr "提供点名称 - 使用Pod1"
+
+# 213b395a2593404daf151f1a941d4adc
+#: ../../qig.rst:593
+msgid "Gateway - We'll use 172.16.10.1 as our gateway"
+msgstr "网关 - 使用172.16.10.1作为网关"
+
+# f02f613f386b4d1c8b305c1d35c56583
+#: ../../qig.rst:595
+msgid "Netmask - We'll use 255.255.255.0"
+msgstr "子网掩码 - 使用255.255.255.0"
+
+# 9c5bffa76ac74249ad74e842f6eebf17
+#: ../../qig.rst:597
+msgid "Start/end reserved system IPs - we will use 172.16.10.10-172.16.10.20"
+msgstr "系统预留 起始/结束 IP - 使用172.16.10.10-172.16.10.20"
+
+# 5cf252fb06404e90931c41694829ed58
+#: ../../qig.rst:599
+msgid "Guest gateway - We'll use 172.16.10.1"
+msgstr "来宾网络网关 - 使用172.16.10.1"
+
+# 5f00b4c2472c4db99f0cfaaa62c9a5a2
+#: ../../qig.rst:601
+msgid "Guest netmask - We'll use 255.255.255.0"
+msgstr "来宾网络掩码 - 使用255.255.255.0"
+
+# 17730085682c4460bcf6fc9b337e1b79
+#: ../../qig.rst:603
+msgid "Guest start/end IP - We'll use 172.16.10.30-172.16.10.200"
+msgstr "来宾网络 起始/结束IP - 使用172.16.10.30-172.16.10.200"
+
+# 367247fc307a4a82b2ad9e2b711e5619
+#: ../../qig.rst:607
+msgid "Cluster"
+msgstr "群集"
+
+# 7850cd3533944572afd0e2c12f25a29f
+#: ../../qig.rst:609
+msgid ""
+"Now that we've added a Zone, we need only add a few more items for "
+"configuring the cluster."
+msgstr "添加区域后，仅需再为配置群集提供如下信息。"
+
+# 7001d238c08a4539b6f079919c83370e
+#: ../../qig.rst:612
+msgid "Name - We'll use Cluster1"
+msgstr "群集名称 - 使用Cluster1"
+
+# b757d57d9ef8406e9cb173ab58d3c2f7
+#: ../../qig.rst:614
+msgid "Hypervisor - Choose KVM"
+msgstr "Hypervisor - 选择KVM"
+
+# d2da65ca4fcc49799aa20d81580d1d11
+#: ../../qig.rst:616
+msgid ""
+"You should be prompted to add the first host to your cluster at this point. "
+"Only a few bits of information are needed."
+msgstr "此时向导会提示您为集群添加第一台主机，需提供如下信息："
+
+# 3882023bf413443a94edf6abde71aa6d
+#: ../../qig.rst:619
+msgid ""
+"Hostname - we'll use the IP address 172.16.10.2 since we didn't set up a DNS"
+" server."
+msgstr "主机名 - 由于没有设置DNS服务器，所以这里输入主机IP地址 172.16.10.2。"
+
+# d10fbbf3eaeb49159c2e6ccc868e03b1
+#: ../../qig.rst:622
+msgid "Username - we'll use 'root'"
+msgstr "用户名 - 我们使用root"
+
+# 9c4f5c5877de4ea98bbd1fb9735ecef1
+#: ../../qig.rst:624
+msgid "Password - enter the operating system password for the root user"
+msgstr "密码 - 输入root用户的密码"
+
+# 3d5ffbc59d224d41be2df9ba6af77742
+#: ../../qig.rst:628
+msgid "Primary Storage"
+msgstr "主存储"
+
+# 66d0666b459a47c3b5f48d2883046b70
+#: ../../qig.rst:630
+msgid ""
+"With your cluster now setup - you should be prompted for primary storage "
+"information. Choose NFS as the storage type and then enter the following "
+"values in the fields:"
+msgstr "在配置群集时，按提示输入主存储的信息。选择NFS作为存储类型，并在如下区域中输入相应的值："
+
+# ca283f835167437fb9bc1ef6393ca820
+#: ../../qig.rst:634
+msgid "Name - We'll use 'Primary1'"
+msgstr "名称 - 使用 'Primary1'"
+
+# fdf29ecc70964523b52e9de67e9413d7
+#: ../../qig.rst:636
+msgid "Server - We'll be using the IP address 172.16.10.2"
+msgstr "服务器 - 使用的IP地址为 172.16.10.2"
+
+# 7e622eac227540c9bee2de26c79cb398
+#: ../../qig.rst:638
+msgid "Path - Well define /primary as the path we are using"
+msgstr "路径 - 使用之前定义的 /primary"
+
+# 749f44f07ab84067949bed01b90f7371
+#: ../../qig.rst:642
+msgid "Secondary Storage"
+msgstr "辅助存储"
+
+# 387b9b2ba8bb4d86bbd092c06b307189
+#: ../../qig.rst:644
+msgid ""
+"If this is a new zone, you'll be prompted for secondary storage information "
+"- populate it as follows:"
+msgstr "如果添加的是一个新的区域，您需提供辅助存储相关信息 - 如下所示："
+
+# b25a138b410441ccabde5dc127832043
+#: ../../qig.rst:647
+msgid "NFS server - We'll use the IP address 172.16.10.2"
+msgstr "NFS服务器 - 使用的IP地址为 172.16.10.2"
+
+# 05a433329180429f9aadec69507b153f
+#: ../../qig.rst:649
+msgid "Path - We'll use /secondary"
+msgstr "路径 - 输入 /secondary "
+
+# 5f25228532674a9881e0c4b867cf64a9
+#: ../../qig.rst:651
+msgid ""
+"Now, click Launch and your cloud should begin setup - it may take several "
+"minutes depending on your internet connection speed for setup to finalize."
+msgstr "现在，点击启动开始配置云-完成安装所需的时间取决于你的网络速度。"
+
+# bcb5d6bf55794f36bb79ef590164a807
+#: ../../qig.rst:654
+msgid ""
+"That's it, you are done with installation of your Apache CloudStack cloud."
+msgstr "到这里，你的Apache CloudStack云就已经安装完成了。"
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/storage_setup.mo b/source/installguide/locale/zh_CN/LC_MESSAGES/storage_setup.mo
new file mode 100644
index 0000000..a29da09
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/storage_setup.mo
Binary files differ
diff --git a/source/installguide/locale/zh_CN/LC_MESSAGES/storage_setup.po b/source/installguide/locale/zh_CN/LC_MESSAGES/storage_setup.po
new file mode 100644
index 0000000..93c4767
--- /dev/null
+++ b/source/installguide/locale/zh_CN/LC_MESSAGES/storage_setup.po
@@ -0,0 +1,341 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 11:42+0200\n"
+"PO-Revision-Date: 2014-06-30 10:25+0000\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: Chinese (China) (http://www.transifex.com/projects/p/apache-cloudstack-installation-rtd/language/zh_CN/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: zh_CN\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# d6b2b3302e474c2ca46f28b9bee03734
+#: ../../storage_setup.rst:18
+msgid "Storage Setup"
+msgstr "存储设置"
+
+# 7752c36da35f479d9c03995e830ae253
+#: ../../storage_setup.rst:20
+msgid ""
+"CloudStack is designed to work with a wide variety of commodity and "
+"enterprise-grade storage. Local disk may be used as well, if supported by "
+"the selected hypervisor. Storage type support for guest virtual disks "
+"differs based on hypervisor selection."
+msgstr "CloudStack被设计为可以支持广泛的商业级和企业级存储设备。如果所选的hypervisor支持，也可以使用本地存储。 所支持的虚拟磁盘类型取决于不同的hypervisor。"
+
+# 538f0beb0b4e4e2a9983e312661eb54f
+#: ../../storage_setup.rst:26
+msgid "Storage Type"
+msgstr "存储类型"
+
+# 18b92c5cd5074bb4b06534aff95e18c8
+#: ../../storage_setup.rst:26
+msgid "XenServer"
+msgstr "XenServer"
+
+# 6ed9b0e44342476a9dbbdbf4e4b917fe
+#: ../../storage_setup.rst:26
+msgid "vSphere"
+msgstr "vSphere"
+
+# ac3ca3b0a1c641a3bc1de1a92146eb91
+#: ../../storage_setup.rst:26
+msgid "KVM"
+msgstr "KVM"
+
+# 03e3922684d94f63abcc832e20828d0d
+#: ../../storage_setup.rst:28
+msgid "NFS"
+msgstr "NFS"
+
+# 3b99a671b8ab4908aea8b3e783a22b19
+# 5c64989b5d4b4b0e8b086335877bdcf9
+# efa230d191b5477f887a61486039d99e
+# 53b67c59114241cb81ae1f4bcd7bdf26
+# 02d62854fef943e88ea4d32d21e23ffb
+# 0bcd3eeecde3461a98be48e06880b63e
+# 69437bfe66f8494cb9119f1ac4f3751a
+# 02613a70f2594d3bb3d1192ff3e520d5
+#: ../../storage_setup.rst:28 ../../storage_setup.rst:28
+#: ../../storage_setup.rst:28 ../../storage_setup.rst:29
+#: ../../storage_setup.rst:30 ../../storage_setup.rst:31
+#: ../../storage_setup.rst:31 ../../storage_setup.rst:31
+msgid "Supported"
+msgstr "支持"
+
+# bc6393ab53db4060bb65171cc25a14b2
+#: ../../storage_setup.rst:29
+msgid "iSCSI"
+msgstr "iSCSI"
+
+# 5e75eb74e709489cb5160ea8d55c040c
+#: ../../storage_setup.rst:29
+msgid "Supported via VMFS"
+msgstr "通过VMFS支持"
+
+# cae1e3af97e747cf8adf4fc7edd27ea4
+# bcf642ada6354a428f7e09abac6608b5
+#: ../../storage_setup.rst:29 ../../storage_setup.rst:30
+msgid "Supported via Clustered Filesystems"
+msgstr "通过集群文件系统支持"
+
+# 6996e2e99e9048ce97d0e6f5fb931f60
+#: ../../storage_setup.rst:30
+msgid "Fiber Channel"
+msgstr "Fiber Channel"
+
+# 019efc65f57148479631b63195d36314
+#: ../../storage_setup.rst:30
+msgid "Supported via Pre-existing SR"
+msgstr "通过Pre-existing SR支持"
+
+# 32746b62e4f8487cb0c808a966bfb210
+#: ../../storage_setup.rst:31
+msgid "Local Disk"
+msgstr "本地磁盘"
+
+# 6e8fd34eb56f4473abecb174650042c8
+#: ../../storage_setup.rst:34
+msgid ""
+"The use of the Cluster Logical Volume Manager (CLVM) for KVM is not "
+"officially supported with CloudStack."
+msgstr "针对KVM使用集群逻辑卷管理器(CLVM)，不受CloudStack官方支持。"
+
+# 052dba62e53b4928a4316a9e7e9a7718
+#: ../../storage_setup.rst:39
+msgid "Small-Scale Setup"
+msgstr "小规模设置"
+
+# ba74f151dee944c59ecb4711a133a657
+#: ../../storage_setup.rst:41
+msgid ""
+"In a small-scale setup, a single NFS server can function as both primary and"
+" secondary storage. The NFS server just needs to export two separate shares,"
+" one for primary storage and the other for secondary storage."
+msgstr "在小规模设置中，一个NFS服务器可以同时作为主存储和辅助存储。只需要NFS服务器有两个独立的共享目录，一个用于主存储，另一个用于辅助存储。"
+
+# 115b100b50994f4bbe369e5a89b5081d
+#: ../../storage_setup.rst:47
+msgid "Secondary Storage"
+msgstr "辅助存储"
+
+# bdbd2ecb612e4c6d833f2a4803d9efc0
+#: ../../storage_setup.rst:49
+msgid ""
+"CloudStack is designed to work with any scalable secondary storage system. "
+"The only requirement is the secondary storage system supports the NFS "
+"protocol."
+msgstr "CloudStack被设计为支持多种可扩展的辅助存储系统。唯一的要求就是辅助存储系统支持NFS协议。"
+
+# dd9865baaf564c74b74a86e19447d21b
+#: ../../storage_setup.rst:54
+msgid ""
+"The storage server should be a machine with a large number of disks. The "
+"disks should ideally be managed by a hardware RAID controller. Modern "
+"hardware RAID controllers support hot plug functionality independent of the "
+"operating system so you can replace faulty disks without impacting the "
+"running operating system."
+msgstr ""
+
+# 81888613f5f6470cb75302dcb4c8dc22
+#: ../../storage_setup.rst:62
+msgid "Example Configurations"
+msgstr "配置实例"
+
+# 15dfab7b505743acb78118d48e6a1df0
+#: ../../storage_setup.rst:64
+msgid ""
+"In this section we go through a few examples of how to set up storage to "
+"work properly on a few types of NFS and iSCSI storage systems."
+msgstr "在本节中我们将通过几个实例说明，如何设置存储并使NFS和iSCSI存储系统正常工作。"
+
+# 800bb50ed8b643849918b01277052e7c
+#: ../../storage_setup.rst:69
+msgid "Linux NFS on Local Disks and DAS"
+msgstr "基于本地硬盘和DAS的NFS服务"
+
+# f2fcb96d0dea4baf8e482525c0dd8245
+#: ../../storage_setup.rst:71
+msgid ""
+"This section describes how to configure an NFS export on a standard Linux "
+"installation. The exact commands might vary depending on the operating "
+"system version."
+msgstr "本节描述如何在一个标准的Linux系统中配置NFS输出。具体的命令取决于操作系统版本。"
+
+# cf13fcc5fa0b4939a8e8574245d1a1e5
+#: ../../storage_setup.rst:75
+msgid "Install the RHEL/CentOS distribution on the storage server."
+msgstr "在存储服务器上安装RHEL/CentOS 发行版"
+
+# 005b8dd262fd4a4388849d5e56b1a54f
+#: ../../storage_setup.rst:77
+msgid ""
+"If the root volume is more than 2 TB in size, create a smaller boot volume "
+"to install RHEL/CentOS. A root volume of 20 GB should be sufficient."
+msgstr "如果根卷的大小超过2TB，创建一个小点的启动卷用于安装RHEL/CentOS，根分区保留20GB就足够了。"
+
+# 217ac8a1620b4bb993b70343ef9cd6ab
+#: ../../storage_setup.rst:81
+msgid ""
+"After the system is installed, create a directory called /export. This can "
+"each be a directory in the root partition itself or a mount point for a "
+"large disk volume."
+msgstr "系统安装好以后，创建一个名为 /export的目录。可以在根分区下创建，或者挂载一个较大的磁盘卷。"
+
+# e51ba40cb56b42aea266a196d1886b28
+#: ../../storage_setup.rst:85
+msgid ""
+"If you have more than 16TB of storage on one host, create multiple EXT3 file"
+" systems and multiple NFS exports. Individual EXT3 file systems cannot "
+"exceed 16TB."
+msgstr "如果你在一台主机上有超过16TB的存储空间， 则创建多个EXT3文件系统和多个NFS输出，单个EXT3文件系统不能超过16TB。 "
+
+# f9ecc678c0a946ada4722e2f84868013
+#: ../../storage_setup.rst:89
+msgid ""
+"After /export directory is created, run the following command to configure "
+"it as an NFS export."
+msgstr "/export目录创建后，运行如下命令配置NFS输出。"
+
+# 166a5ad4eace4ee1acac57e77772e301
+#: ../../storage_setup.rst:96
+msgid "Adjust the above command to suit your deployment needs."
+msgstr "根据你的部署需求，调整如上参数。"
+
+# c6efefc3bb214750a1aa110365bfb7c4
+#: ../../storage_setup.rst:98
+msgid ""
+"**Limiting NFS export.** It is highly recommended that you limit the NFS "
+"export to a particular subnet by specifying a subnet mask "
+"(e.g.,”192.168.1.0/24”). By allowing access from only within the expected "
+"cluster, you avoid having non-pool member mount the storage. The limit you "
+"place must include the management network(s) and the storage network(s). If "
+"the two are the same network then one CIDR is sufficient. If you have a "
+"separate storage network you must provide separate CIDR’s for both or one "
+"CIDR that is broad enough to span both."
+msgstr "**限制NFS输出.** 强烈建议通过指定子网掩码来限制NFS访问权限，（例如“192.168.1.0/24”）。只允许规定的集群才能访问， 避免非集群成员访问。 且管理网络和存储网络必须能够访问；如果2个网络相同，那么一个CIDR就足够了。 如果你是单独的存储网络那么必须提供独立的CIDR或者一个足够大的CIDR可以包含它们2个。"
+
+# 2dee02ec08f44c6eb41bbd83267e69b6
+# daffef1e68c1468ca3f7396f5436cf19
+#: ../../storage_setup.rst:108 ../../storage_setup.rst:236
+msgid "The following is an example with separate CIDRs:"
+msgstr "下面是一个分隔的CIDRs的示例："
+
+# 314c4d57ade04b589bb9cc53855854f0
+# 302894e6d4d8419dadbee7187c9761e3
+#: ../../storage_setup.rst:114 ../../storage_setup.rst:242
+msgid ""
+"**Removing the async flag.** The async flag improves performance by allowing"
+" the NFS server to respond before writes are committed to the disk. Remove "
+"the async flag in your mission critical production deployment."
+msgstr "**移除async异步标记.** 标志允许NFS服务器在提交并写入磁盘操作前就先返回相应，来提高性能。请在关键生产部署中移除异步标志。"
+
+# fc530cedf53646ef8383509ca79aaf46
+#: ../../storage_setup.rst:119
+msgid "Run the following command to enable NFS service."
+msgstr "运行下面的命令启动NFS服务。"
+
+# 43b62119fea74c9585550f73f8f82558
+#: ../../storage_setup.rst:125
+msgid "Edit the /etc/sysconfig/nfs file and uncomment the following lines."
+msgstr "编辑/etc/sysconfig/nfs，并取消如下行的注释。"
+
+# 1d4f8831fb8f493bbf0d2102a2d94333
+#: ../../storage_setup.rst:136
+msgid ""
+"Edit the /etc/sysconfig/iptables file and add the following lines at the "
+"beginning of the INPUT chain."
+msgstr "编辑/etc/sysconfig/iptables，添加如下行的记录到INPUT链的开始部分。"
+
+# 9b07e0f5f1b4436083b1b95549bd51cc
+#: ../../storage_setup.rst:153
+msgid "Reboot the server."
+msgstr "重启服务"
+
+# e020d0f272694579a5ba76a20f504882
+#: ../../storage_setup.rst:155
+msgid "An NFS share called /export is now set up."
+msgstr "NFS共享目录/export已经被创建"
+
+# 954bd15449384ef982eb066148bede4e
+#: ../../storage_setup.rst:158
+msgid ""
+"When copying and pasting a command, be sure the command has pasted as a "
+"single line before executing. Some document viewers may introduce unwanted "
+"line breaks in copied text."
+msgstr "当复制和粘贴命令时，请确保没有多余的换行符，因为一些文档查看器可能会在复制时加上换行符。"
+
+# 57361739f18248a8a389947c9bc2cad2
+#: ../../storage_setup.rst:164
+msgid "Linux NFS on iSCSI"
+msgstr "基于iSCSI的NFS服务"
+
+# 2b54e23d9a61475595ca9e0e83867e12
+#: ../../storage_setup.rst:166
+msgid ""
+"Use the following steps to set up a Linux NFS server export on an iSCSI "
+"volume. These steps apply to RHEL/CentOS 5 distributions."
+msgstr "使用以下步骤创建基于iSCSI卷的NFS服务。这些步骤适用于RHEL/CentOS 5发行版。"
+
+# f1286e7f062d4b9aa981184cc7501688
+#: ../../storage_setup.rst:169
+msgid "Install iscsiadm."
+msgstr "安装iscsiadm。"
+
+# 346450ad74ac4b19964ee166ad4c9d20
+#: ../../storage_setup.rst:178
+msgid "Discover the iSCSI target."
+msgstr "发现ISCSI target。"
+
+# 6274d39a5e6845259cc61a75836241fe
+# 78922f43acdd4b6ca556c8c6094a1816
+#: ../../storage_setup.rst:184 ../../storage_setup.rst:196
+msgid "For example:"
+msgstr "例如："
+
+# aa60b340ef47437486a5520511933ff9
+#: ../../storage_setup.rst:190
+msgid "Log in."
+msgstr "登录"
+
+# ee970ba277924184bb6d07662f86710c
+#: ../../storage_setup.rst:202
+msgid "Discover the SCSI disk. For example:"
+msgstr "发现SCSI磁盘，例如："
+
+# a27db3a17e254b7f81d044d888ed5d83
+#: ../../storage_setup.rst:209
+msgid "Format the disk as ext3 and mount the volume."
+msgstr "格式化磁盘为ext3类型并挂载卷。"
+
+# 73c6a94d549942489bcac311f27242ee
+#: ../../storage_setup.rst:217
+msgid "Add the disk to /etc/fstab to make sure it gets mounted on boot."
+msgstr "添加磁盘到/etc/fstab并确保在启动时能被挂载。"
+
+# b401c3dd18284c72bef05b03f96de014
+#: ../../storage_setup.rst:223
+msgid "Now you can set up /export as an NFS share."
+msgstr "现在你可以建立/export共享目录"
+
+# ac62ebcca250423f8b0a8c1c4d2ea5f3
+#: ../../storage_setup.rst:225
+msgid ""
+"**Limiting NFS export.** In order to avoid data loss, it is highly "
+"recommended that you limit the NFS export to a particular subnet by "
+"specifying a subnet mask (e.g.,”192.168.1.0/24”). By allowing access from "
+"only within the expected cluster, you avoid having non-pool member mount the"
+" storage and inadvertently delete all its data. The limit you place must "
+"include the management network(s) and the storage network(s). If the two are"
+" the same network then one CIDR is sufficient. If you have a separate "
+"storage network you must provide separate CIDRs for both or one CIDR that is"
+" broad enough to span both."
+msgstr "**限制NFS输出.** 强烈建议通过特定的子网和掩码限制NFS访问权限(例如”192.168.1.0/24”)， 只允许规定的集群才能访问， 避免非集群成员访问并非故意的情况下删除所有数据。 且管理网络和存储网络必须能够访问；如果2个网络相同，那么一个CIDR就足够了。 如果你是单独的存储网络那么必须提供独立的CIDR或者一个足够大的CIDR可以包含它们2个。"
diff --git a/source/installguide/management-server/_database.rst b/source/installguide/management-server/_database.rst
new file mode 100644
index 0000000..9ec6600
--- /dev/null
+++ b/source/installguide/management-server/_database.rst
@@ -0,0 +1,377 @@
+.. 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.
+
+Install the database server
+---------------------------
+
+The CloudStack management server uses a MySQL database server to store
+its data. When you are installing the management server on a single
+node, you can install the MySQL server locally. For an installation that
+has multiple management server nodes, we assume the MySQL database also
+runs on a separate node.
+
+CloudStack has been tested with MySQL 5.1 and 5.5. These versions are
+included in RHEL/CentOS and Ubuntu.
+
+
+Install the Database on the Management Server Node
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+This section describes how to install MySQL on the same machine with the
+Management Server. This technique is intended for a simple deployment
+that has a single Management Server node. If you have a multi-node
+Management Server deployment, you will typically use a separate node for
+MySQL. See :ref:`install-database-on-separate-node`.
+
+#. Install MySQL from the package repository of your distribution:
+
+ .. parsed-literal::
+
+ yum install mysql-server
+
+ .. parsed-literal::
+
+ sudo apt-get install mysql-server
+
+#. Open the MySQL configuration file. The configuration file is
+ ``/etc/my.cnf`` or ``/etc/mysql/my.cnf``, depending on your OS.
+
+ Insert the following lines in the ``[mysqld]`` section.
+
+ You can put these lines below the datadir line. The max\_connections
+ parameter should be set to 350 multiplied by the number of Management
+ Servers you are deploying. This example assumes one Management
+ Server.
+
+ .. parsed-literal::
+
+ innodb_rollback_on_timeout=1
+ innodb_lock_wait_timeout=600
+ max_connections=350
+ log-bin=mysql-bin
+ binlog-format = 'ROW'
+
+ .. note::
+ You can also create a file ``/etc/mysql/conf.d/cloudstack.cnf``
+ and add these directives there. Don't forget to add ``[mysqld]`` on the
+ first line of the file.
+
+
+
+#. Start or restart MySQL to put the new configuration into effect.
+
+ On RHEL/CentOS, MySQL doesn't automatically start after installation.
+ Start it manually.
+
+ .. parsed-literal::
+
+ service mysqld start
+
+ On Ubuntu, restart MySQL.
+
+ .. parsed-literal::
+
+ sudo service mysql restart
+
+#. (CentOS and RHEL only; not required on Ubuntu)
+
+ .. warning::
+ On RHEL and CentOS, MySQL does not set a root password by default. It is
+ very strongly recommended that you set a root password as a security
+ precaution.
+
+ Run the following command to secure your installation. You can answer "Y"
+ to all questions.
+
+ .. parsed-literal::
+
+ mysql_secure_installation
+
+#. CloudStack can be blocked by security mechanisms, such as SELinux.
+ Disable SELinux to ensure + that the Agent has all the required
+ permissions.
+
+ Configure SELinux (RHEL and CentOS):
+
+ #. Check whether SELinux is installed on your machine. If not, you
+ can skip this section.
+
+ In RHEL or CentOS, SELinux is installed and enabled by default.
+ You can verify this with:
+
+ .. parsed-literal::
+
+ rpm -qa | grep selinux
+
+ #. Set the SELINUX variable in ``/etc/selinux/config`` to
+ "permissive". This ensures that the permissive setting will be
+ maintained after a system reboot.
+
+ In RHEL or CentOS:
+
+ .. parsed-literal::
+
+ vi /etc/selinux/config
+
+ Change the following line
+
+ .. parsed-literal::
+
+ SELINUX=enforcing
+
+ to this:
+
+ .. parsed-literal::
+
+ SELINUX=permissive
+
+ #. Set SELinux to permissive starting immediately, without requiring
+ a system reboot.
+
+ .. parsed-literal::
+
+ setenforce permissive
+
+#. Set up the database. The following command creates the "cloud" user
+ on the database.
+
+ .. parsed-literal::
+
+ cloudstack-setup-databases cloud:<dbpassword>@localhost \
+ --deploy-as=root:<password> \
+ -e <encryption_type> \
+ -m <management_server_key> \
+ -k <database_key> \
+ -i <management_server_ip>
+
+ - In dbpassword, specify the password to be assigned to the "cloud"
+ user. You can choose to provide no password although that is not
+ recommended.
+
+ - In deploy-as, specify the username and password of the user
+ deploying the database. In the following command, it is assumed
+ the root user is deploying the database and creating the "cloud"
+ user.
+
+ - (Optional) For encryption\_type, use file or web to indicate the
+ technique used to pass in the database encryption password.
+ Default: file. See :ref:`about-password-key-encryption`.
+
+ - (Optional) For management\_server\_key, substitute the default key
+ that is used to encrypt confidential parameters in the CloudStack
+ properties file. Default: password. It is highly recommended that
+ you replace this with a more secure value. See
+ :ref:`about-password-key-encryption`.
+
+ - (Optional) For database\_key, substitute the default key that is
+ used to encrypt confidential parameters in the CloudStack
+ database. Default: password. It is highly recommended that you
+ replace this with a more secure value. See
+ :ref:`about-password-key-encryption`.
+
+ - (Optional) For management\_server\_ip, you may explicitly specify
+ cluster management server node IP. If not specified, the local IP
+ address will be used.
+
+
+ When this script is finished, you should see a message like
+ “Successfully initialized the database.”
+
+ .. note::
+ If the script is unable to connect to the MySQL database, check the
+ "localhost" loopback address in ``/etc/hosts``. It should be pointing to
+ the IPv4 loopback address "127.0.0.1" and not the IPv6 loopback address
+ ``::1``. Alternatively, reconfigure MySQL to bind to the IPv6 loopback
+ interface.
+
+#. If you are running the KVM hypervisor on the same machine with the
+ Management Server, edit /etc/sudoers and add the following line:
+
+ .. parsed-literal::
+
+ Defaults:cloud !requiretty
+
+#. Now that the database is set up, you can finish configuring the OS
+ for the Management Server. This command will set up iptables,
+ sudoers, and start the Management Server.
+
+ .. parsed-literal::
+
+ cloudstack-setup-management
+
+ You should get the output message “CloudStack Management Server setup is
+ done.”
+ If the servlet container is Tomcat7 the argument --tomcat7 must be used.
+
+
+.. _install-database-on-separate-node:
+
+Install the Database on a Separate Node
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+This section describes how to install MySQL on a standalone machine,
+separate from the Management Server. This technique is intended for a
+deployment that includes several Management Server nodes. If you have a
+single-node Management Server deployment, you will typically use the
+same node for MySQL. See `“Install the Database on the Management Server Node”
+<#install-the-database-on-the-management-server-node>`_.
+
+.. note::
+ The management server doesn't require a specific distribution for the MySQL
+ node. You can use a distribution or Operating System of your choice. Using
+ the same distribution as the management server is recommended, but not
+ required. See `“Management Server, Database, and Storage System Requirements”
+ <#management-server-database-and-storage-system-requirements>`_.
+
+#. Install MySQL from the package repository from your distribution:
+
+ .. parsed-literal::
+
+ yum install mysql-server
+
+ .. parsed-literal::
+
+ sudo apt-get install mysql-server
+
+#. Edit the MySQL configuration (/etc/my.cnf or /etc/mysql/my.cnf,
+ depending on your OS) and insert the following lines in the [mysqld]
+ section. You can put these lines below the datadir line. The
+ max\_connections parameter should be set to 350 multiplied by the
+ number of Management Servers you are deploying. This example assumes
+ two Management Servers.
+
+ .. note::
+ On Ubuntu, you can also create /etc/mysql/conf.d/cloudstack.cnf file and
+ add these directives there. Don't forget to add [mysqld] on the first
+ line of the file.
+
+ .. parsed-literal::
+
+ innodb_rollback_on_timeout=1
+ innodb_lock_wait_timeout=600
+ max_connections=700
+ log-bin=mysql-bin
+ binlog-format = 'ROW'
+ bind-address = 0.0.0.0
+
+#. Start or restart MySQL to put the new configuration into effect.
+
+ On RHEL/CentOS, MySQL doesn't automatically start after installation.
+ Start it manually.
+
+ .. parsed-literal::
+
+ service mysqld start
+
+ On Ubuntu, restart MySQL.
+
+ .. parsed-literal::
+
+ sudo service mysql restart
+
+#. (CentOS and RHEL only; not required on Ubuntu)
+
+ .. warning::
+ On RHEL and CentOS, MySQL does not set a root password by default. It is
+ very strongly recommended that you set a root password as a security
+ precaution. Run the following command to secure your installation. You
+ can answer "Y" to all questions except "Disallow root login remotely?".
+ Remote root login is required to set up the databases.
+
+ .. parsed-literal::
+
+ mysql_secure_installation
+
+#. If a firewall is present on the system, open TCP port 3306 so
+ external MySQL connections can be established.
+
+ On Ubuntu, UFW is the default firewall. Open the port with this
+ command:
+
+ .. parsed-literal::
+
+ ufw allow mysql
+
+ On RHEL/CentOS:
+
+ #. Edit the /etc/sysconfig/iptables file and add the following line
+ at the beginning of the INPUT chain.
+
+ .. parsed-literal::
+
+ -A INPUT -p tcp --dport 3306 -j ACCEPT
+
+ #. Now reload the iptables rules.
+
+ .. parsed-literal::
+
+ service iptables restart
+
+#. Return to the root shell on your first Management Server.
+
+#. Set up the database. The following command creates the cloud user on
+ the database.
+
+ - In dbpassword, specify the password to be assigned to the cloud
+ user. You can choose to provide no password.
+
+ - In deploy-as, specify the username and password of the user
+ deploying the database. In the following command, it is assumed
+ the root user is deploying the database and creating the cloud
+ user.
+
+ - (Optional) For encryption\_type, use file or web to indicate the
+ technique used to pass in the database encryption password.
+ Default: file. See :ref:`about-password-key-encryption`.
+
+ - (Optional) For management\_server\_key, substitute the default key
+ that is used to encrypt confidential parameters in the CloudStack
+ properties file. Default: password. It is highly recommended that
+ you replace this with a more secure value. See About Password and
+ Key Encryption.
+
+ - (Optional) For database\_key, substitute the default key that is
+ used to encrypt confidential parameters in the CloudStack
+ database. Default: password. It is highly recommended that you
+ replace this with a more secure value. See
+ :ref:`about-password-key-encryption`.
+
+ - (Optional) For management\_server\_ip, you may explicitly specify
+ cluster management server node IP. If not specified, the local IP
+ address will be used.
+
+ .. parsed-literal::
+
+ cloudstack-setup-databases cloud:<dbpassword>@<ip address mysql server> \
+ --deploy-as=root:<password> \
+ -e <encryption_type> \
+ -m <management_server_key> \
+ -k <database_key> \
+ -i <management_server_ip>
+
+ When this script is finished, you should see a message like
+ “Successfully initialized the database.”
+
+#. Now that the database is set up, you can finish configuring the OS
+ for the Management Server. This command will set up iptables,
+ sudoers, and start the Management Server.
+
+ .. parsed-literal::
+
+ cloudstack-setup-management
+
+ You should get the output message “CloudStack Management Server setup is
+ done.”
+
diff --git a/source/installguide/management-server/_nfs.rst b/source/installguide/management-server/_nfs.rst
new file mode 100644
index 0000000..98df3cb
--- /dev/null
+++ b/source/installguide/management-server/_nfs.rst
@@ -0,0 +1,248 @@
+.. 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.
+
+.. _prepare-nfs-shares:
+
+Prepare NFS Shares
+------------------
+
+CloudStack needs a place to keep primary and secondary storage (see
+Cloud Infrastructure Overview). Both of these can be NFS shares. This
+section tells how to set up the NFS shares before adding the storage to
+CloudStack.
+
+.. note::
+ NFS is not the only option for primary or secondary storage. For example,
+ you may use Ceph RBD, GlusterFS, iSCSI, and others. The choice of storage
+ system will depend on the choice of hypervisor and whether you are dealing
+ with primary or secondary storage.
+
+The requirements for primary and secondary storage are described in:
+
+- :ref:`about-primary-storage`
+
+- :ref:`about-secondary-storage`
+
+A production installation typically uses a separate NFS server.
+See :ref:`using-a-separage-nfs-server`.
+
+You can also use the Management Server node as the NFS server. This is
+more typical of a trial installation, but is technically possible in a
+larger deployment. See :ref:`using-the-management-server-as-the-nfs-server`.
+
+
+.. _using-a-separage-nfs-server:
+
+Using a Separate NFS Server
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+This section tells how to set up NFS shares for secondary and
+(optionally) primary storage on an NFS server running on a separate node
+from the Management Server.
+
+The exact commands for the following steps may vary depending on your
+operating system version.
+
+.. warning::
+ (KVM only) Ensure that no volume is already mounted at your NFS mount point.
+
+#. On the storage server, create an NFS share for secondary storage and,
+ if you are using NFS for primary storage as well, create a second NFS
+ share. For example:
+
+ .. parsed-literal::
+
+ mkdir -p /export/primary
+ mkdir -p /export/secondary
+
+#. To configure the new directories as NFS exports, edit /etc/exports.
+ Export the NFS share(s) with
+ rw,async,no\_root\_squash,no\_subtree\_check. For example:
+
+ .. parsed-literal::
+
+ vi /etc/exports
+
+ Insert the following line.
+
+ .. parsed-literal::
+
+ /export \*(rw,async,no_root_squash,no_subtree_check)
+
+#. Export the /export directory.
+
+ .. parsed-literal::
+
+ exportfs -a
+
+#. On the management server, create a mount point for secondary storage.
+ For example:
+
+ .. parsed-literal::
+
+ mkdir -p /mnt/secondary
+
+#. Mount the secondary storage on your Management Server. Replace the
+ example NFS server name and NFS share paths below with your own.
+
+ .. parsed-literal::
+
+ mount -t nfs nfsservername:/export/secondary /mnt/secondary
+
+
+.. _using-the-management-server-as-the-nfs-server:
+
+Using the Management Server as the NFS Server
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+This section tells how to set up NFS shares for primary and secondary
+storage on the same node with the Management Server. This is more
+typical of a trial installation, but is technically possible in a larger
+deployment. It is assumed that you will have less than 16TB of storage
+on the host.
+
+The exact commands for the following steps may vary depending on your
+operating system version.
+
+#. On RHEL/CentOS systems, you'll need to install the nfs-utils package:
+
+ .. parsed-literal::
+
+ yum install nfs-utils
+
+#. On the Management Server host, create two directories that you will
+ use for primary and secondary storage. For example:
+
+ .. parsed-literal::
+
+ mkdir -p /export/primary
+ mkdir -p /export/secondary
+
+#. To configure the new directories as NFS exports, edit /etc/exports.
+ Export the NFS share(s) with
+ rw,async,no\_root\_squash,no\_subtree\_check. For example:
+
+ .. parsed-literal::
+
+ vi /etc/exports
+
+ Insert the following line.
+
+ .. parsed-literal::
+
+ /export \*(rw,async,no_root_squash,no_subtree_check)
+
+#. Export the /export directory.
+
+ .. parsed-literal::
+
+ exportfs -a
+
+#. Edit the /etc/sysconfig/nfs file.
+
+ .. parsed-literal::
+
+ vi /etc/sysconfig/nfs
+
+ Uncomment the following lines:
+
+ .. parsed-literal::
+
+ LOCKD_TCPPORT=32803
+ LOCKD_UDPPORT=32769
+ MOUNTD_PORT=892
+ RQUOTAD_PORT=875
+ STATD_PORT=662
+ STATD_OUTGOING_PORT=2020
+
+#. Edit the /etc/sysconfig/iptables file.
+
+ .. parsed-literal::
+
+ vi /etc/sysconfig/iptables
+
+ Add the following lines at the beginning of the INPUT chain, where
+ <NETWORK> is the network that you'll be using:
+
+ .. parsed-literal::
+
+ -A INPUT -s <NETWORK> -m state --state NEW -p udp --dport 111 -j ACCEPT
+ -A INPUT -s <NETWORK> -m state --state NEW -p tcp --dport 111 -j ACCEPT
+ -A INPUT -s <NETWORK> -m state --state NEW -p tcp --dport 2049 -j ACCEPT
+ -A INPUT -s <NETWORK> -m state --state NEW -p tcp --dport 32803 -j ACCEPT
+ -A INPUT -s <NETWORK> -m state --state NEW -p udp --dport 32769 -j ACCEPT
+ -A INPUT -s <NETWORK> -m state --state NEW -p tcp --dport 892 -j ACCEPT
+ -A INPUT -s <NETWORK> -m state --state NEW -p udp --dport 892 -j ACCEPT
+ -A INPUT -s <NETWORK> -m state --state NEW -p tcp --dport 875 -j ACCEPT
+ -A INPUT -s <NETWORK> -m state --state NEW -p udp --dport 875 -j ACCEPT
+ -A INPUT -s <NETWORK> -m state --state NEW -p tcp --dport 662 -j ACCEPT
+ -A INPUT -s <NETWORK> -m state --state NEW -p udp --dport 662 -j ACCEPT
+
+#. Run the following commands:
+
+ .. parsed-literal::
+
+ service iptables restart
+ service iptables save
+
+#. If NFS v4 communication is used between client and server, add your
+ domain to /etc/idmapd.conf on both the hypervisor host and Management
+ Server.
+
+ .. parsed-literal::
+
+ vi /etc/idmapd.conf
+
+ Remove the character # from the beginning of the Domain line in
+ idmapd.conf and replace the value in the file with your own domain.
+ In the example below, the domain is company.com.
+
+ .. parsed-literal::
+
+ Domain = company.com
+
+#. Reboot the Management Server host.
+
+ Two NFS shares called /export/primary and /export/secondary are now
+ set up.
+
+#. It is recommended that you test to be sure the previous steps have
+ been successful.
+
+ #. Log in to the hypervisor host.
+
+ #. Be sure NFS and rpcbind are running. The commands might be
+ different depending on your OS. For example:
+
+ .. parsed-literal::
+
+ service rpcbind start
+ service nfs start
+ chkconfig nfs on
+ chkconfig rpcbind on
+ reboot
+
+ #. Log back in to the hypervisor host and try to mount the /export
+ directories. For example, substitute your own management server
+ name:
+
+ .. parsed-literal::
+
+ mkdir /primary
+ mount -t nfs <management-server-name>:/export/primary
+ umount /primary
+ mkdir /secondary
+ mount -t nfs <management-server-name>:/export/secondary
+ umount /secondary
diff --git a/source/installguide/management-server/_pkg_install.rst b/source/installguide/management-server/_pkg_install.rst
new file mode 100644
index 0000000..ad2bc40
--- /dev/null
+++ b/source/installguide/management-server/_pkg_install.rst
@@ -0,0 +1,49 @@
+.. 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.
+
+Install the Management Server on the First Host
+-----------------------------------------------
+
+The first step in installation, whether you are installing the
+Management Server on one host or many, is to install the software on a
+single node.
+
+.. note::
+ If you are planning to install the Management Server on multiple nodes for
+ high availability, do not proceed to the additional nodes yet. That step
+ will come later.
+
+The CloudStack Management server can be installed using either RPM or
+DEB packages. These packages will depend on everything you need to run
+the Management server.
+
+.. include:: _pkg_repo.rst
+
+
+Install on CentOS/RHEL
+^^^^^^^^^^^^^^^^^^^^^^
+
+.. parsed-literal::
+
+ yum install cloudstack-management
+
+
+Install on Ubuntu
+^^^^^^^^^^^^^^^^^
+
+.. parsed-literal::
+
+ sudo apt-get install cloudstack-management
+
diff --git a/source/installguide/management-server/_pkg_repo.rst b/source/installguide/management-server/_pkg_repo.rst
new file mode 100644
index 0000000..755b715
--- /dev/null
+++ b/source/installguide/management-server/_pkg_repo.rst
@@ -0,0 +1,93 @@
+.. 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.
+
+Configure package repository
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+CloudStack is only distributed from source from the official mirrors.
+However, members of the CloudStack community may build convenience
+binaries so that users can install Apache CloudStack without needing to
+build from source.
+
+If you didn't follow the steps to build your own packages from source in
+the sections for `“Building RPMs from Source”
+<../building_from_source.html#building-rpms-from-source>`_ or
+`“Building DEB packages” <../building_from_source.html#building-deb-packages>`_
+you may find pre-built DEB and RPM packages for your convenience linked from
+the `downloads <http://cloudstack.apache.org/downloads.html>`_ page.
+
+.. note::
+ These repositories contain both the Management Server and KVM Hypervisor
+ packages.
+
+RPM package repository
+~~~~~~~~~~~~~~~~~~~~~~
+
+There is a RPM package repository for CloudStack so you can easily
+install on RHEL based platforms.
+
+If you're using an RPM-based system, you'll want to add the Yum
+repository so that you can install CloudStack with Yum.
+
+Yum repository information is found under ``/etc/yum.repos.d``. You'll
+see several ``.repo`` files in this directory, each one denoting a
+specific repository.
+
+To add the CloudStack repository, create
+``/etc/yum.repos.d/cloudstack.repo`` and insert the following
+information.
+
+.. parsed-literal::
+
+ [cloudstack]
+ name=cloudstack
+ baseurl=http://download.cloudstack.org/centos/$releasever/|version|/
+ enabled=1
+ gpgcheck=0
+
+
+Now you should now be able to install CloudStack using Yum.
+
+
+DEB package repository
+~~~~~~~~~~~~~~~~~~~~~~
+
+You can add a DEB package repository to your apt sources with the
+following commands. Please note that only packages for Ubuntu 14.04 LTS
+(Trusty) and Ubuntu 16.04 (Xenial) are being built at this time. DISCLAIMER: Ubuntu 12.04 (Precise) is no longer supported.
+
+Use your preferred editor and open (or create)
+``/etc/apt/sources.list.d/cloudstack.list``. Add the community provided
+repository to the file:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu trusty |version|
+
+We now have to add the public key to the trusted keys.
+
+.. parsed-literal::
+
+ sudo wget -O - http://download.cloudstack.org/release.asc|apt-key add -
+
+Now update your local apt cache.
+
+.. parsed-literal::
+
+ sudo apt-get update
+
+Your DEB package repository should now be configured and ready for use.
+
+
diff --git a/source/installguide/management-server/_prerequisite.rst b/source/installguide/management-server/_prerequisite.rst
new file mode 100644
index 0000000..e5cb264
--- /dev/null
+++ b/source/installguide/management-server/_prerequisite.rst
@@ -0,0 +1,94 @@
+.. 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.
+
+Overview
+--------
+
+This section describes installing the Management Server. There are two
+slightly different installation flows, depending on how many Management
+Server nodes will be in your cloud:
+
+- A single Management Server node, with MySQL on the same node.
+
+- Multiple Management Server nodes, with MySQL on a node separate from
+ the Management Servers.
+
+In either case, each machine must meet the system requirements described
+in :ref:`minimum-system-requirements`.
+
+.. warning::
+ For the sake of security, be sure the public Internet can not access port
+ 8096 or port 8250 on the Management Server.
+
+The procedure for installing the Management Server is:
+
+#. Prepare the Operating System
+
+#. (XenServer only) Download and install vhd-util.
+
+#. Install the First Management Server
+
+#. Install and Configure the MySQL database
+
+#. Prepare NFS Shares
+
+#. Prepare and Start Additional Management Servers (optional)
+
+#. Prepare the System VM Template
+
+
+Prepare the Operating System
+----------------------------
+
+The OS must be prepared to host the Management Server using the
+following steps. These steps must be performed on each Management Server
+node.
+
+#. Log in to your OS as root.
+
+#. Check for a fully qualified hostname.
+
+ .. parsed-literal::
+
+ hostname --fqdn
+
+ This should return a fully qualified hostname such as
+ "management1.lab.example.org". If it does not, edit /etc/hosts so
+ that it does.
+
+#. Make sure that the machine can reach the Internet.
+
+ .. parsed-literal::
+
+ ping cloudstack.apache.org
+
+#. Turn on NTP for time synchronization.
+
+ .. note::
+ NTP is required to synchronize the clocks of the servers in your cloud.
+
+ Install NTP.
+
+ .. parsed-literal::
+
+ yum install ntp
+
+ .. parsed-literal::
+
+ sudo apt-get install openntpd
+
+#. Repeat all of these steps on every host where the Management Server
+ will be installed.
+
diff --git a/source/installguide/management-server/_second_mgt.rst b/source/installguide/management-server/_second_mgt.rst
new file mode 100644
index 0000000..46285de
--- /dev/null
+++ b/source/installguide/management-server/_second_mgt.rst
@@ -0,0 +1,70 @@
+.. 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.
+
+Additional Management Servers
+-----------------------------
+
+For your second and subsequent Management Servers, you will install the
+Management Server software, connect it to the database, and set up the
+OS for the Management Server.
+
+#. Perform the steps in `“Prepare the Operating System”
+ <#prepare-the-operating-system>`_ and `“Building RPMs from Source”
+ <building_from_source.html#building-rpms-from-source>`_ or
+ `“Building DEB packages”
+ <building_from_source.html#building-deb-packages>`_ as appropriate.
+
+#. This step is required only for installations where XenServer is
+ installed on the hypervisor hosts.
+
+ Download vhd-util from
+ `vhd-util <http://download.cloudstack.org/tools/vhd-util>`_
+
+ Copy vhd-util to
+ ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``.
+
+#. Ensure that necessary services are started and set to start on boot.
+
+ .. parsed-literal::
+
+ service rpcbind start
+ service nfs start
+ chkconfig nfs on
+ chkconfig rpcbind on
+
+#. Configure the database client. Note the absence of the --deploy-as
+ argument in this case. (For more details about the arguments to this
+ command, see :ref:`install-database-on-separate-node`.)
+
+ .. parsed-literal::
+
+ cloudstack-setup-databases cloud:dbpassword@dbhost \
+ -e encryption_type \
+ -m management_server_key \
+ -k database_key \
+ -i management_server_ip
+
+#. Configure the OS and start the Management Server:
+
+ .. parsed-literal::
+
+ cloudstack-setup-management
+
+ The Management Server on this node should now be running.
+ If the servlet container is Tomcat7 the argument --tomcat7 must be used.
+
+#. Repeat these steps on each additional Management Server.
+
+#. Be sure to configure a load balancer for the Management Servers. See :ref:`management-server-load-balancing`
diff --git a/source/installguide/management-server/_systemvm.rst b/source/installguide/management-server/_systemvm.rst
new file mode 100644
index 0000000..9bbb197
--- /dev/null
+++ b/source/installguide/management-server/_systemvm.rst
@@ -0,0 +1,120 @@
+.. 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.
+
+Prepare the System VM Template
+------------------------------
+
+Secondary storage must be seeded with a template that is used for
+CloudStack system VMs.
+
+.. note::
+ When copying and pasting a command, be sure the command has pasted as a
+ single line before executing. Some document viewers may introduce unwanted
+ line breaks in copied text.
+
+#. On the Management Server, run one or more of the following
+ ``cloud-install-sys-tmplt`` commands to retrieve and decompress the
+ system VM template. Run the command for each hypervisor type that you
+ expect end users to run in this Zone.
+
+ If your secondary storage mount point is not named ``/mnt/secondary``,
+ substitute your own mount point name.
+
+ If you set the CloudStack database encryption type to "web" when you
+ set up the database, you must now add the parameter ``-s
+ <management-server-secret-key>``. See :ref:`about-password-key-encryption`.
+
+ This process will require approximately 5 GB of free space on the
+ local file system and up to 30 minutes each time it runs.
+
+ * For Hyper-V
+
+ .. parsed-literal::
+
+ /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt \
+ -m /mnt/secondary \
+ -u http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-hyperv.vhd.zip \
+ -h hyperv \
+ -s <optional-management-server-secret-key> \
+ -F
+
+ * For XenServer:
+
+ .. parsed-literal::
+
+ /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt \
+ -m /mnt/secondary \
+ -u http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-xen.vhd.bz2 \
+ -h xenserver \
+ -s <optional-management-server-secret-key> \
+ -F
+
+ * For vSphere:
+
+ .. parsed-literal::
+
+ /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt \
+ -m /mnt/secondary \
+ -u http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-vmware.ova \
+ -h vmware \
+ -s <optional-management-server-secret-key> \
+ -F
+
+ * For KVM:
+
+ .. parsed-literal::
+
+ /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt \
+ -m /mnt/secondary \
+ -u http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2 \
+ -h kvm \
+ -s <optional-management-server-secret-key> \
+ -F
+
+ * For LXC:
+
+ .. parsed-literal::
+
+ /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt \
+ -m /mnt/secondary \
+ -u http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2 \
+ -h lxc \
+ -s <optional-management-server-secret-key> \
+ -F
+
+ * For OVM3:
+
+ .. parsed-literal::
+
+ /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt \
+ -m /mnt/secondary \
+ -u http://download.cloudstack.org/systemvm/4.11/systemvmtemplate-4.11.0-ovm.raw.bz2 \
+ -h ovm3 \
+ -s <optional-management-server-secret-key> \
+ -F
+
+#. If you are using a separate NFS server, perform this step. If you are
+ using the Management Server as the NFS server, you MUST NOT perform
+ this step.
+
+ When the script has finished, unmount secondary storage and remove
+ the created directory.
+
+ .. parsed-literal::
+
+ umount /mnt/secondary
+ rmdir /mnt/secondary
+
+#. Repeat these steps for each secondary storage server.
diff --git a/source/installguide/management-server/_vhd-util.rst b/source/installguide/management-server/_vhd-util.rst
new file mode 100644
index 0000000..20c6af6
--- /dev/null
+++ b/source/installguide/management-server/_vhd-util.rst
@@ -0,0 +1,26 @@
+.. 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.
+
+Downloading vhd-util
+--------------------
+
+This procedure is required only for installations where XenServer is
+installed on the hypervisor hosts.
+
+Before setting up the Management Server, download
+`vhd-util <http://download.cloudstack.org/tools/vhd-util>`_ from
+http://download.cloudstack.org/tools/vhd-util.
+and copy it into ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``
+of the Management Server.
\ No newline at end of file
diff --git a/source/installguide/management-server/index.rst b/source/installguide/management-server/index.rst
new file mode 100644
index 0000000..c6a2532
--- /dev/null
+++ b/source/installguide/management-server/index.rst
@@ -0,0 +1,56 @@
+.. 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.
+
+.. _install-mgt:
+
+Management Server Installation
+==============================
+
+.. include:: _prerequisite.rst
+
+.. include:: _pkg_install.rst
+
+.. include:: _vhd-util.rst
+
+.. include:: _database.rst
+
+.. include:: _nfs.rst
+
+.. include:: _second_mgt.rst
+
+.. include:: _systemvm.rst
+
+
+Installation Complete! Next Steps
+---------------------------------
+
+Congratulations! You have now installed CloudStack Management Server and
+the database it uses to persist system data.
+
+|installation-complete.png: Finished installs with single Management
+Server and multiple Management Servers|
+
+What should you do next?
+
+- Even without adding any cloud infrastructure, you can run the UI to
+ get a feel for what's offered and how you will interact with
+ CloudStack on an ongoing basis. See Log In to the UI.
+
+- When you're ready, add the cloud infrastructure and try running some
+ virtual machines on it, so you can watch how CloudStack manages the
+ infrastructure. See Provision Your Cloud Infrastructure.
+
+
+.. |installation-complete.png: Finished installs with single Management Server and multiple Management Servers| image:: /_static/images/installation-complete.png
diff --git a/source/installguide/optional_installation.rst b/source/installguide/optional_installation.rst
new file mode 100644
index 0000000..d352f06
--- /dev/null
+++ b/source/installguide/optional_installation.rst
@@ -0,0 +1,804 @@
+.. 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.
+
+
+Additional Installation Options
+===============================
+
+The next few sections describe CloudStack features above and beyond the
+basic deployment options.
+
+
+Installing the Usage Server (Optional)
+--------------------------------------
+
+You can optionally install the Usage Server once the Management Server
+is configured properly. The Usage Server takes data from the events in
+the system and enables usage-based billing for accounts.
+
+When multiple Management Servers are present, the Usage Server may be
+installed on any number of them. The Usage Servers will coordinate usage
+processing. A site that is concerned about availability should install
+Usage Servers on at least two Management Servers.
+
+
+Requirements for Installing the Usage Server
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+- The Management Server must be running when the Usage Server is
+ installed.
+
+- The Usage Server must be installed on the same server as a Management
+ Server.
+
+
+Steps to Install the Usage Server
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+#. Package repository should already being configured. Refer to
+ `Configure Package Repository <http://cloudstack-installation.readthedocs.org/en/latest/installation.html#configure-package-repository>`_
+
+#. Install package cloudstack-usage
+
+ On RHEL/CentOS systems, use:
+
+ .. parsed-literal::
+
+ # yum install cloudstack-usage
+
+ On Debian/Ubuntu systems, use:
+
+ .. parsed-literal::
+
+ # apt-get install cloudstack-usage
+
+#. Once installed, start the Usage Server with the following command.
+
+ .. parsed-literal::
+
+ # service cloudstack-usage start
+
+#. Enable the service at boot
+
+ On RHEL/CentOS systems, use:
+
+ .. parsed-literal::
+
+ # chkconfig cloudstack-usage on
+
+ On Debian/Ubuntu systems, use:
+
+ .. parsed-literal::
+
+ # update-rc.d cloudstack-usage defaults
+
+:ref:`working-with-usage` discusses further configuration of the Usage
+Server.
+
+
+SSL (Optional)
+--------------
+
+CloudStack provides HTTP access in its default installation. There are a
+number of technologies and sites which choose to implement SSL. As a
+result, we have left CloudStack to expose HTTP under the assumption that
+a site will implement its typical practice.
+
+CloudStack uses Tomcat as its servlet container. For sites that would
+like CloudStack to terminate the SSL session, Tomcat’s SSL access may be
+enabled. Tomcat SSL configuration is described at
+http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html.
+
+
+Database Replication (Optional)
+-------------------------------
+
+CloudStack supports database replication from one MySQL node to another.
+This is achieved using standard MySQL replication. You may want to do
+this as insurance against MySQL server or storage loss. MySQL
+replication is implemented using a master/slave model. The master is the
+node that the Management Servers are configured to use. The slave is a
+standby node that receives all write operations from the master and
+applies them to a local, redundant copy of the database. The following
+steps are a guide to implementing MySQL replication.
+
+.. note::
+ Creating a replica is not a backup solution. You should develop a backup
+ procedure for the MySQL data that is distinct from replication.
+
+#. Ensure that this is a fresh install with no data in the master.
+
+#. Edit my.cnf on the master and add the following in the [mysqld]
+ section below datadir.
+
+ .. parsed-literal::
+
+ log_bin=mysql-bin
+ server_id=1
+
+ The server\_id must be unique with respect to other servers. The
+ recommended way to achieve this is to give the master an ID of 1 and
+ each slave a sequential number greater than 1, so that the servers
+ are numbered 1, 2, 3, etc.
+
+#. Restart the MySQL service. On RHEL/CentOS systems, use:
+
+ .. parsed-literal::
+
+ # service mysqld restart
+
+ On Debian/Ubuntu systems, use:
+
+ .. parsed-literal::
+
+ # service mysql restart
+
+#. Create a replication account on the master and give it privileges. We
+ will use the "cloud-repl" user with the password "password". This
+ assumes that master and slave run on the 172.16.1.0/24 network.
+
+ .. sourcecode: bash
+
+ # mysql -u root
+ mysql> create user 'cloud-repl'@'172.16.1.%' identified by 'password';
+ mysql> grant replication slave on *.* TO 'cloud-repl'@'172.16.1.%';
+ mysql> flush privileges;
+ mysql> flush tables with read lock;
+
+#. Leave the current MySQL session running.
+
+#. In a new shell start a second MySQL session.
+
+#. Retrieve the current position of the database.
+
+ .. parsed-literal::
+
+ # mysql -u root
+ mysql> show master status;
+ +------------------+----------+--------------+------------------+
+ | File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+ +------------------+----------+--------------+------------------+
+ | mysql-bin.000001 | 412 | | |
+ +------------------+----------+--------------+------------------+
+
+#. Note the file and the position that are returned by your instance.
+
+#. Exit from this session.
+
+#. Complete the master setup. Returning to your first session on the
+ master, release the locks and exit MySQL.
+
+ .. parsed-literal::
+
+ mysql> unlock tables;
+
+#. Install and configure the slave. On the slave server, run the
+ following commands.
+
+ .. parsed-literal::
+
+ # yum install mysql-server
+ # chkconfig mysqld on
+
+#. Edit my.cnf and add the following lines in the [mysqld] section below
+ datadir.
+
+ .. parsed-literal::
+
+ server_id=2
+ innodb_rollback_on_timeout=1
+ innodb_lock_wait_timeout=600
+
+#. Restart MySQL. Use "mysqld" on RHEL/CentOS systems:
+
+ .. parsed-literal::
+
+ # service mysqld restart
+
+ On Ubuntu/Debian systems use "mysql."
+
+ .. parsed-literal::
+
+ # service mysql restart
+
+#. Instruct the slave to connect to and replicate from the master.
+ Replace the IP address, password, log file, and position with the
+ values you have used in the previous steps.
+
+ .. parsed-literal::
+
+ mysql> change master to
+ -> master_host='172.16.1.217',
+ -> master_user='cloud-repl',
+ -> master_password='password',
+ -> master_log_file='mysql-bin.000001',
+ -> master_log_pos=412;
+
+#. Then start replication on the slave.
+
+ .. parsed-literal::
+
+ mysql> start slave;
+
+#. Optionally, open port 3306 on the slave as was done on the master
+ earlier.
+
+ This is not required for replication to work. But if you choose not
+ to do this, you will need to do it when failover to the replica
+ occurs.
+
+
+Failover
+~~~~~~~~
+
+This will provide for a replicated database that can be used to
+implement manual failover for the Management Servers. CloudStack
+failover from one MySQL instance to another is performed by the
+administrator. In the event of a database failure you should:
+
+#. Stop the Management Servers (via service cloudstack-management stop).
+
+#. Change the replica's configuration to be a master and restart it.
+
+#. Ensure that the replica's port 3306 is open to the Management
+ Servers.
+
+#. Make a change so that the Management Server uses the new database.
+ The simplest process here is to put the IP address of the new
+ database server into each Management Server's
+ /etc/cloudstack/management/db.properties.
+
+#. Restart the Management Servers:
+
+ .. parsed-literal::
+
+ # service cloudstack-management start
+
+
+Amazon Web Services Interface
+-----------------------------
+
+Amazon Web Services Compatible Interface
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack can translate Amazon Web Services (AWS) API calls to native
+CloudStack API calls so that users can continue using existing
+AWS-compatible tools. This translation service runs as a separate web
+application in the same tomcat server as the management server of
+CloudStack, listening on a different port. The Amazon Web Services (AWS)
+compatible interface provides the EC2 SOAP and Query APIs as well as the
+S3 REST API.
+
+.. note::
+ This service was previously enabled by separate software called CloudBridge.
+ It is now fully integrated with the CloudStack management server.
+
+.. warning::
+ The compatible interface for the EC2 Query API and the S3 API are Work In
+ Progress. The S3 compatible API offers a way to store data on the
+ management server file system, it is not an implementation of the S3
+ backend.
+
+Limitations
+
+- Supported only in zones that use basic networking.
+
+- Available in fresh installations of CloudStack. Not available through
+ upgrade of previous versions.
+
+- Features such as Elastic IP (EIP) and Elastic Load Balancing (ELB)
+ are only available in an infrastructure with a Citrix NetScaler
+ device. Users accessing a Zone with a NetScaler device will need to
+ use a NetScaler-enabled network offering (DefaultSharedNetscalerEIP
+ and ELBNetworkOffering).
+
+
+Supported API Version
+~~~~~~~~~~~~~~~~~~~~~
+
+- The EC2 interface complies with Amazon's WDSL version dated November
+ 15, 2010, available at `http://ec2.amazonaws.com/doc/2010-11-15/
+ <http://ec2.amazonaws.com/doc/2010-11-15/>`_.
+
+- The interface is compatible with the EC2 command-line tools *EC2
+ tools v. 1.3.6230*, which can be downloaded at
+ `http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip <http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip>`_.
+
+.. note::
+ Work is underway to support a more recent version of the EC2 API
+
+
+Enabling the EC2 and S3 Compatible Interface
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The software that provides AWS API compatibility is installed along with
+CloudStack. You must enable the services and perform some setup steps
+prior to using it.
+
+#. Set the global configuration parameters for each service to true. See
+ `*Setting Global Configuration Parameters*
+ <configuration.html#setting-global-configuration-parameters>`_.
+
+#. Create a set of CloudStack service offerings with names that match
+ the Amazon service offerings. You can do this through the CloudStack
+ UI as described in the Administration Guide.
+
+ .. warning::
+ Be sure you have included the Amazon default service offering, m1.small.
+ As well as any EC2 instance types that you will use.
+
+#. If you did not already do so when you set the configuration parameter
+ in step 1, restart the Management Server.
+
+ .. parsed-literal::
+
+ # service cloudstack-management restart
+
+The following sections provides details to perform these steps
+
+
+Enabling the Services
+^^^^^^^^^^^^^^^^^^^^^
+
+To enable the EC2 and S3 compatible services you need to set the
+configuration variables *enable.ec2.api* and *enable.s3.api* to true.
+You do not have to enable both at the same time. Enable the ones you
+need. This can be done via the CloudStack GUI by going in *Global
+Settings* or via the API.
+
+The snapshot below shows you how to use the GUI to enable these services
+
+|Use the GUI to set the configuration variable to true|
+
+Using the CloudStack API, the easiest is to use the so-called
+integration port on which you can make unauthenticated calls. In Global
+Settings set the port to 8096 and subsequently call the
+*updateConfiguration* method. The following urls shows you how:
+
+.. parsed-literal::
+
+ http://localhost:8096/client/api?command=updateConfiguration&name=enable.ec2.api&value=true
+ http://localhost:8096/client/api?command=updateConfiguration&name=enable.ec2.api&value=true
+
+Once you have enabled the services, restart the server.
+
+
+Creating EC2 Compatible Service Offerings
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+You will also need to define compute service offerings with names
+compatible with the `Amazon EC2 instance
+types <http://aws.amazon.com/ec2/instance-types/>`_ API names (e.g
+m1.small,m1.large). This can be done via the CloudStack GUI. Go under
+*Service Offerings* select *Compute offering* and either create a new
+compute offering or modify an existing one, ensuring that the name
+matches an EC2 instance type API name. The snapshot below shows you how:
+
+|Use the GUI to set the name of a compute service offering to an EC2
+instance type API name.|
+
+
+Modifying the AWS API Port
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. note::
+ (Optional) The AWS API listens for requests on port 7080. If you prefer AWS
+ API to listen on another port, you can change it as follows:
+
+ #. Edit the files ``/etc/cloudstack/management/server.xml``,
+ ``/etc/cloudstack/management/server-nonssl.xml``, and
+ ``/etc/cloudstack/management/server-ssl.xml``.
+
+ #. In each file, find the tag <Service name="Catalina7080">. Under this tag, locate <Connector executor="tomcatThreadPool-internal" port= ....<.
+
+ #. Change the port to whatever port you want to use, then save the files.
+
+ #. Restart the Management Server.
+
+If you re-install CloudStack, you will have to re-enable the services
+and if need be update the port.
+
+
+AWS API User Setup
+~~~~~~~~~~~~~~~~~~
+
+In general, users need not be aware that they are using a translation
+service provided by CloudStack. They only need to send AWS API calls to
+CloudStack's endpoint, and it will translate the calls to the native
+CloudStack API. Users of the Amazon EC2 compatible interface will be
+able to keep their existing EC2 tools and scripts and use them with
+their CloudStack deployment, by specifying the endpoint of the
+management server and using the proper user credentials. In order to do
+this, each user must perform the following configuration steps:
+
+- Generate user credentials.
+
+- Register with the service.
+
+- For convenience, set up environment variables for the EC2 SOAP
+ command-line tools.
+
+
+AWS API Command-Line Tools Setup
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To use the EC2 command-line tools, the user must perform these steps:
+
+#. Be sure you have the right version of EC2 Tools. The supported
+ version is available at
+ `http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip <http://s3.amazonaws.com/ec2-downloads/ec2-api-tools-1.3-62308.zip>`_.
+
+#. Set up the EC2 environment variables. This can be done every time you
+ use the service or you can set them up in the proper shell profile.
+ Replace the endpoint (i.e EC2\_URL) with the proper address of your
+ CloudStack management server and port. In a bash shell do the
+ following.
+
+.. parsed-literal::
+
+ $ export EC2_CERT=/path/to/cert.pem
+ $ export EC2_PRIVATE_KEY=/path/to/private_key.pem
+ $ export EC2_URL=http://localhost:7080/awsapi
+ $ export EC2_HOME=/path/to/EC2_tools_directory
+
+
+Using Timeouts to Ensure AWS API Command Completion
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The Amazon EC2 command-line tools have a default connection timeout.
+When used with CloudStack, a longer timeout might be needed for some
+commands. If you find that commands are not completing due to timeouts,
+you can specify a custom timeouts. You can add the following optional
+command-line parameters to any CloudStack-supported EC2 command:
+
+Specifies a connection timeout (in seconds)
+
+.. parsed-literal::
+
+ --connection-timeout TIMEOUT
+
+Specifies a request timeout (in seconds)
+
+.. parsed-literal::
+
+ --request-timeout TIMEOUT
+
+Example:
+
+.. parsed-literal::
+
+ ec2-run-instances 2 –z us-test1 –n 1-3 --connection-timeout 120 --request-timeout 120
+
+.. note::
+ The timeouts optional arguments are not specific to CloudStack.
+
+
+Supported AWS API Calls
+~~~~~~~~~~~~~~~~~~~~~~~
+
+The following Amazon EC2 commands are supported by CloudStack when the
+AWS API compatible interface is enabled. For a few commands, there are
+differences between the CloudStack and Amazon EC2 versions, and these
+differences are noted. The underlying SOAP call for each command is also
+given, for those who have built tools using those calls.
+
+Table 1. Elastic IP API mapping
+
+.. cssclass:: table-striped table-bordered table-hover
+
++---------------------------+-----------------------+-------------------------+
+| EC2 command | SOAP call | CloudStack API call |
++===========================+=======================+=========================+
+| ec2-allocate-address | AllocateAddress | associateIpAddress |
++---------------------------+-----------------------+-------------------------+
+| ec2-associate-address | AssociateAddress | enableStaticNat |
++---------------------------+-----------------------+-------------------------+
+| ec2-describe-addresses | DescribeAddresses | listPublicIpAddresses |
++---------------------------+-----------------------+-------------------------+
+| ec2-diassociate-address | DisassociateAddress | disableStaticNat |
++---------------------------+-----------------------+-------------------------+
+| ec2-release-address | ReleaseAddress | disassociateIpAddress |
++---------------------------+-----------------------+-------------------------+
+
+|
+
+Table 2. Availability Zone API mapping
+
+.. cssclass:: table-striped table-bordered table-hover
+
++-----------------------------------+-----------------------------+-----------------------+
+| EC2 command | SOAP call | CloudStack API call |
++===================================+=============================+=======================+
+| ec2-describe-availability-zones | DescribeAvailabilityZones | listZones |
++-----------------------------------+-----------------------------+-----------------------+
+
+|
+
+Table 3. Images API mapping
+
+.. cssclass:: table-striped table-bordered table-hover
+
++-----------------------+-------------------+-----------------------+
+| EC2 command | SOAP call | CloudStack API call |
++=======================+===================+=======================+
+| ec2-create-image | CreateImage | createTemplate |
++-----------------------+-------------------+-----------------------+
+| ec2-deregister | DeregisterImage | DeleteTemplate |
++-----------------------+-------------------+-----------------------+
+| ec2-describe-images | DescribeImages | listTemplates |
++-----------------------+-------------------+-----------------------+
+| ec2-register | RegisterImage | registerTemplate |
++-----------------------+-------------------+-----------------------+
+
+|
+
+Table 4. Image Attributes API mapping
+
+.. cssclass:: table-striped table-bordered table-hover
+
++--------------------------------+--------------------------+-----------------------------+
+| EC2 command | SOAP call | CloudStack API call |
++================================+==========================+=============================+
+| ec2-describe-image-attribute | DescribeImageAttribute | listTemplatePermissions |
++--------------------------------+--------------------------+-----------------------------+
+| ec2-modify-image-attribute | ModifyImageAttribute | updateTemplatePermissions |
++--------------------------------+--------------------------+-----------------------------+
+| ec2-reset-image-attribute | ResetImageAttribute | updateTemplatePermissions |
++--------------------------------+--------------------------+-----------------------------+
+
+|
+
+Table 5. Instances API mapping
+
+.. cssclass:: table-striped table-bordered table-hover
+
++---------------------------+----------------------+-------------------------+
+| EC2 command | SOAP call | CloudStack API call |
++===========================+======================+=========================+
+| ec2-describe-instances | DescribeInstances | listVirtualMachines |
++---------------------------+----------------------+-------------------------+
+| ec2-run-instances | RunInstances | deployVirtualMachine |
++---------------------------+----------------------+-------------------------+
+| ec2-reboot-instances | RebootInstances | rebootVirtualMachine |
++---------------------------+----------------------+-------------------------+
+| ec2-start-instances | StartInstances | startVirtualMachine |
++---------------------------+----------------------+-------------------------+
+| ec2-stop-instances | StopInstances | stopVirtualMachine |
++---------------------------+----------------------+-------------------------+
+| ec2-terminate-instances | TerminateInstances | destroyVirtualMachine |
++---------------------------+----------------------+-------------------------+
+
+|
+
+Table 6. Instance Attributes Mapping
+
+.. cssclass:: table-striped table-bordered table-hover
+
++-----------------------------------+-----------------------------+-----------------------+
+| EC2 command | SOAP call | CloudStack API call |
++===================================+=============================+=======================+
+| ec2-describe-instance-attribute | DescribeInstanceAttribute | listVirtualMachines |
++-----------------------------------+-----------------------------+-----------------------+
+
+|
+
+Table 7. Keys Pairs Mapping
+
+.. cssclass:: table-striped table-bordered table-hover
+
++-------------------------+--------------------+-----------------------+
+| EC2 command | SOAP call | CloudStack API call |
++=========================+====================+=======================+
+| ec2-add-keypair | CreateKeyPair | createSSHKeyPair |
++-------------------------+--------------------+-----------------------+
+| ec2-delete-keypair | DeleteKeyPair | deleteSSHKeyPair |
++-------------------------+--------------------+-----------------------+
+| ec2-describe-keypairs | DescribeKeyPairs | listSSHKeyPairs |
++-------------------------+--------------------+-----------------------+
+| ec2-import-keypair | ImportKeyPair | registerSSHKeyPair |
++-------------------------+--------------------+-----------------------+
+
+|
+
+Table 8. Passwords API Mapping
+
+.. cssclass:: table-striped table-bordered table-hover
+
++--------------------+-------------------+-----------------------+
+| EC2 command | SOAP call | CloudStack API call |
++====================+===================+=======================+
+| ec2-get-password | GetPasswordData | getVMPassword |
++--------------------+-------------------+-----------------------+
+
+|
+
+Table 9. Security Groups API Mapping
+
+.. cssclass:: table-striped table-bordered table-hover
+
++----------------------+---------------------------------+---------------------------------+
+| EC2 command | SOAP call | CloudStack API call |
++======================+=================================+=================================+
+| ec2-authorize | AuthorizeSecurityGroupIngress | authorizeSecurityGroupIngress |
++----------------------+---------------------------------+---------------------------------+
+| ec2-add-group | CreateSecurityGroup | createSecurityGroup |
++----------------------+---------------------------------+---------------------------------+
+| ec2-delete-group | DeleteSecurityGroup | deleteSecurityGroup |
++----------------------+---------------------------------+---------------------------------+
+| ec2-describe-group | DescribeSecurityGroups | listSecurityGroups |
++----------------------+---------------------------------+---------------------------------+
+| ec2-revoke | RevokeSecurityGroupIngress | revokeSecurityGroupIngress |
++----------------------+---------------------------------+---------------------------------+
+
+|
+
+Table 10. Snapshots API Mapping
+
+.. cssclass:: table-striped table-bordered table-hover
+
++--------------------------+---------------------+-----------------------+
+| EC2 command | SOAP call | CloudStack API call |
++==========================+=====================+=======================+
+| ec2-create-snapshot | CreateSnapshot | createSnapshot |
++--------------------------+---------------------+-----------------------+
+| ec2-delete-snapshot | DeleteSnapshot | deleteSnapshot |
++--------------------------+---------------------+-----------------------+
+| ec2-describe-snapshots | DescribeSnapshots | listSnapshots |
++--------------------------+---------------------+-----------------------+
+
+|
+
+Table 11. Volumes API Mapping
+
+.. cssclass:: table-striped table-bordered table-hover
+
++-----------------------+------------------+-----------------------+
+| EC2 command | SOAP call | CloudStack API call |
++=======================+==================+=======================+
+| ec2-attach-volume | AttachVolume | attachVolume |
++-----------------------+------------------+-----------------------+
+| ec2-create-volume | CreateVolume | createVolume |
++-----------------------+------------------+-----------------------+
+| ec2-delete-volume | DeleteVolume | deleteVolume |
++-----------------------+------------------+-----------------------+
+| ec2-describe-volume | DescribeVolume | listVolumes |
++-----------------------+------------------+-----------------------+
+| ec2-detach-volume | DetachVolume | detachVolume |
++-----------------------+------------------+-----------------------+
+
+|
+
+
+Examples
+~~~~~~~~
+
+There are many tools available to interface with a AWS compatible API.
+In this section we provide a few examples that users of CloudStack can
+build upon.
+
+
+Boto Examples
+^^^^^^^^^^^^^^
+
+Boto is one of them. It is a Python package available at
+https://github.com/boto/boto. In this section we provide two examples of
+Python scripts that use Boto and have been tested with the CloudStack
+AWS API Interface.
+
+First is an EC2 example. Replace the Access and Secret Keys with your
+own and update the endpoint.
+
+Example 1. An EC2 Boto example
+
+.. sourcecode:: python
+
+ #!/usr/bin/env python
+
+ import sys
+ import os
+ import boto
+ import boto.ec2
+
+ region = boto.ec2.regioninfo.RegionInfo(name="ROOT",endpoint="localhost")
+ apikey='GwNnpUPrO6KgIdZu01z_ZhhZnKjtSdRwuYd4DvpzvFpyxGMvrzno2q05MB0ViBoFYtdqKd'
+ secretkey='t4eXLEYWw7chBhDlaKf38adCMSHx_wlds6JfSx3z9fSpSOm0AbP9Moj0oGIzy2LSC8iw'
+
+ def main():
+ '''Establish connection to EC2 cloud'''
+ conn = boto.connect_ec2(aws_access_key_id=apikey,
+ aws_secret_access_key=secretkey,
+ is_secure=False,
+ region=region,
+ port=7080,
+ path="/awsapi",
+ api_version="2010-11-15")
+
+ '''Get list of images that I own'''
+ images = conn.get_all_images()
+ print images
+ myimage = images[0]
+ '''Pick an instance type'''
+ vm_type='m1.small'
+ reservation = myimage.run(instance_type=vm_type,security_groups=['default'])
+
+ if __name__ == '__main__':
+ main()
+
+|
+
+Second is an S3 example. The S3 interface in CloudStack is obsolete. If you need an S3 interface you should look at systems like RiakCS, Ceph or GlusterFS. This example is here for completeness and can be adapted to other S3 endpoint.
+
+Example 2. An S3 Boto Example
+
+.. sourcecode:: python
+
+ #!/usr/bin/env python
+
+ import sys
+ import os
+ from boto.s3.key import Key
+ from boto.s3.connection import S3Connection
+ from boto.s3.connection import OrdinaryCallingFormat
+
+ apikey='ChOw-pwdcCFy6fpeyv6kUaR0NnhzmG3tE7HLN2z3OB_s-ogF5HjZtN4rnzKnq2UjtnHeg_yLA5gOw'
+ secretkey='IMY8R7CJQiSGFk4cHwfXXN3DUFXz07cCiU80eM3MCmfLs7kusgyOfm0g9qzXRXhoAPCH-IRxXc3w'
+
+ cf=OrdinaryCallingFormat()
+
+ def main():
+ '''Establish connection to S3 service'''
+ conn = S3Connection(aws_access_key_id=apikey,aws_secret_access_key=secretkey, \
+ is_secure=False, \
+ host='localhost', \
+ port=7080, \
+ calling_format=cf, \
+ path="/awsapi/rest/AmazonS3")
+
+ try:
+ bucket=conn.create_bucket('cloudstack')
+ k = Key(bucket)
+ k.key = 'test'
+ try:
+ k.set_contents_from_filename('/Users/runseb/Desktop/s3cs.py')
+ except:
+ print 'could not write file'
+ pass
+ except:
+ bucket = conn.get_bucket('cloudstack')
+ k = Key(bucket)
+ k.key = 'test'
+ try:
+ k.get_contents_to_filename('/Users/runseb/Desktop/foobar')
+ except:
+ print 'Could not get file'
+ pass
+
+ try:
+ bucket1=conn.create_bucket('teststring')
+ k=Key(bucket1)
+ k.key('foobar')
+ k.set_contents_from_string('This is my silly test')
+ except:
+ bucket1=conn.get_bucket('teststring')
+ k = Key(bucket1)
+ k.key='foobar'
+ k.get_contents_as_string()
+
+ if __name__ == '__main__':
+ main()
+
+
+.. |Use the GUI to set the configuration variable to true| image:: /_static/images/ec2-s3-configuration.png
+.. |Use the GUI to set the name of a compute service offering to an EC2 instance type API name.| image:: /_static/images/compute-service-offerings.png
diff --git a/source/installguide/overview/_overview.rst b/source/installguide/overview/_overview.rst
new file mode 100644
index 0000000..3ba81af
--- /dev/null
+++ b/source/installguide/overview/_overview.rst
@@ -0,0 +1,67 @@
+.. 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.
+
+Introduction
+------------
+
+Who Should Read This
+^^^^^^^^^^^^^^^^^^^^
+
+For those who have already gone through a design phase and planned a
+more sophisticated deployment, or those who are ready to start scaling
+up a trial installation. With the following procedures, you can start
+using the more powerful features of CloudStack, such as advanced VLAN
+networking, high availability, additional network elements such as load
+balancers and firewalls, and support for multiple hypervisors including
+Citrix XenServer, KVM, and VMware vSphere.
+
+
+Installation Steps
+^^^^^^^^^^^^^^^^^^
+
+For anything more than a simple trial installation, you will need
+guidance for a variety of configuration choices. It is strongly
+recommended that you read the following:
+
+- Choosing a Deployment Architecture
+- Choosing a Hypervisor: Supported Features
+- Network Setup
+- Storage Setup
+- Best Practices
+
+
+#. Make sure you have the required hardware ready.
+ See :ref:`minimum-system-requirements`
+
+#. Install the Management Server (choose single-node or multi-node).
+ See :ref:`install-mgt`
+
+#. Configure your cloud. See :ref:`Configuring_your_CloudStack_Installation`
+
+ #. Using CloudStack UI. See `*User Interface* :ref:`log-in-to-ui`
+
+ #. Add a zone. Includes the first pod, cluster, and host. See :ref:`adding-a-zone`
+
+ #. Add more pods (optional). See :ref:`adding-a-pod`
+
+ #. Add more clusters (optional). See :ref:`adding-a-cluster`
+
+ #. Add more hosts (optional). See :ref:`adding-a-host`
+
+ #. Add more primary storage (optional). See :ref:`add-primary-storage`
+
+ #. Add more secondary storage (optional). See :ref:`add-secondary-storage`
+
+#. Try using the cloud. See :ref:`initialize-and-test`
diff --git a/source/installguide/overview/_requirements.rst b/source/installguide/overview/_requirements.rst
new file mode 100644
index 0000000..1531462
--- /dev/null
+++ b/source/installguide/overview/_requirements.rst
@@ -0,0 +1,83 @@
+.. 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.
+
+.. _minimum-system-requirements:
+
+Minimum System Requirements
+---------------------------
+
+
+Management Server, Database, and Storage System Requirements
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The machines that will run the Management Server and MySQL database must
+meet the following requirements. The same machines can also be used to
+provide primary and secondary storage, such as via localdisk or NFS. The
+Management Server may be placed on a virtual machine.
+
+- Operating system:
+
+ - Preferred: CentOS/RHEL 7.2+, CentOS/RHEL 6.8+ or Ubuntu 14.04(.2) or higher
+
+- 64-bit x86 CPU (more cores results in better performance)
+
+- 4 GB of memory
+
+- 250 GB of local disk (more results in better capability; 500 GB
+ recommended)
+
+- At least 1 NIC
+
+- Statically allocated IP address
+
+- Fully qualified domain name as returned by the hostname command
+
+
+Host/Hypervisor System Requirements
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The host is where the cloud services run in the form of guest virtual
+machines. Each host is one machine that meets the following
+requirements:
+
+- Must support HVM (Intel-VT or AMD-V enabled).
+
+- 64-bit x86 CPU (more cores results in better performance)
+
+- Hardware virtualization support required
+
+- 4 GB of memory
+
+- 36 GB of local disk
+
+- At least 1 NIC
+
+- Latest hotfixes applied to hypervisor software
+
+- When you deploy CloudStack, the hypervisor host must not have any VMs
+ already running
+
+- All hosts within a cluster must be homogeneous. The CPUs must be of
+ the same type, count, and feature flags.
+
+Hosts have additional requirements depending on the hypervisor. See the
+requirements listed at the top of the Installation section for your
+chosen hypervisor:
+
+.. warning::
+ Be sure you fulfill the additional hypervisor requirements and installation
+ steps provided in this Guide. Hypervisor hosts must be properly prepared to
+ work with CloudStack. For example, the requirements for XenServer are
+ listed under Citrix XenServer Installation.
diff --git a/source/installguide/overview/index.rst b/source/installguide/overview/index.rst
new file mode 100644
index 0000000..c14d487
--- /dev/null
+++ b/source/installguide/overview/index.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.
+
+Installation overview
+==============================
+
+.. contents::
+ :local:
+ :backlinks: top
+
+.. include:: _overview.rst
+
+.. include:: _requirements.rst
+
+
+Package Repository
+------------------
+
+CloudStack is only distributed from source from the official Apache mirrors.
+However, members of the CloudStack community may build convenience
+binaries so that users can install Apache CloudStack without needing to
+build from source.
+
+If you didn't follow the steps to build your own packages from source in
+the sections for `“Building RPMs from Source”
+<../building_from_source.html#building-rpms-from-source>`_ or
+`“Building DEB packages” <../building_from_source.html#building-deb-packages>`_
+you may find pre-built DEB and RPM packages for your convenience linked from
+the `downloads <http://cloudstack.apache.org/downloads.html>`_ page.
+
+.. note::
+ These repositories contain both the Management Server and KVM Hypervisor
+ packages.
+
diff --git a/source/plugins/cloudian-connector.rst b/source/plugins/cloudian-connector.rst
new file mode 100644
index 0000000..58bb170
--- /dev/null
+++ b/source/plugins/cloudian-connector.rst
@@ -0,0 +1,473 @@
+.. 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 Cloudian Connector Plugin
+=============================
+
+Introduction to the Cloudian Connector Plugin
+---------------------------------------------
+
+The Cloudian (HyperStore) Connector is a native CloudStack plugin that allow
+integration between Apache CloudStack and Cloudian Management Console (CMC). The
+Connector integrates Cloudian S3 Storage into the CloudStack Management GUI and
+allows administrators to easily give their CloudStack users access to and manage
+their own S3 storage areas.
+
+Compatibilty
+~~~~~~~~~~~~
+
+The following table shows the compatiblity of Cloudian Connector with CloudStack.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++---------------------+----------------------+-------------------------+
+| Connector Version | CloudStack version | Cloudian Compatibility |
++=====================+======================+=========================+
+| 4.9_6.2-1 | 4.9 | Version 6.2 and onwards |
++---------------------+----------------------+-------------------------+
+| 4.11+ | 4.11+ | Version 6.2 and onwards |
++---------------------+----------------------+-------------------------+
+
+Table: Support Matrix
+
+.. note::
+ Starting CloudStack 4.11, the Connector will be part of the CloudStack
+ release and will not need to be externally installed.
+
+Connector Overview
+------------------
+
+Single-Sign-On Integration
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The connector plugin adds a Cloudian Storage button to the CloudStack UI. This
+button is available for all users on the bottom left of the menu.
+
+.. figure:: /_static/images/cloudian-tab.png
+ :align: center
+ :alt: a screenshot of an enabled Cloudian Connector
+
+When a user clicks this button, a new window or tab (depending on the web
+browser preferences) is opened for the HyperStore CMC GUI. The CloudStack user
+is automatically logged in to CMC as the correctly mapped HyperStore user using
+Single-Sign-On (SSO).
+
+With the connector enabled, when the user clicks ‘Log Out’ in the CloudStack UI
+this first logs the user out of CloudStack and then redirects the page to log
+out any logged-in Cloudian user out of CMC GUI and finally redirects the page to
+the CloudStack login page.
+
+Single-Sign-On is a technique where CloudStack and HyperStore are configured to
+trust each other. This is achieved by configuring both HyperStore and the
+CloudStack connector with the same SSO Shared Key. The CloudStack connector
+creates a special login URL for CMC which it signs using this shared key. Upon
+receiving the special signed login URL, CMC validates the request by comparing
+the signature to its own copy of the shared key and the user is automatically
+logged in.
+
+User Mapping and Provisioning/De-provisioning
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack domains are mapped to Cloudian Groups. CloudStack accounts within
+those domains are mapped to Cloudian users. The Cloudian user and group are
+created on demand if it doesn’t already exist when the CloudStack user accesses
+CMC through the Cloudian Storage button. When accounts and domains are created
+or removed in CloudStack, they automatically create or remove users or groups in
+CMC.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++---------------------+----------------------------+
+| CloudStack Entity | Equivalent Cloudian Entity |
++=====================+============================+
+| Account | User |
++---------------------+----------------------------+
+| Domain | Group |
++---------------------+----------------------------+
+
+Table: Mapping Between Cloudian and CloudStack
+
+.. note::
+ Adding groups or users directly through Cloudian does not add
+ corresponding CloudStack Domains or Accounts. The integration is driven
+ completely from the CloudStack side.
+
+Special Admin User Mapping
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The special CloudStack admin is are mapped to a special HyperStore Admin user
+account which defaults to the user id admin. As the admin user on HyperStore is
+configurable, there is a configuration option to control this mapping. This
+mapping dictates which HyperStore user is automatically logged in using SSO when
+the CloudStack admin user clicks "Cloudian Storage".
+
+.. note::
+ The Cloudian Admin user default is called admin. Older versions of
+ Cloudian used to use admin@cloudian.com.
+
+DNS Resolution Requirements
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The CloudStack Management Server will need to be access the Cloudian admin
+service. The Cloudian admin service is commonly run on the same nodes as your
+Cloudian S3 servers. The admin service is used to provision and deprovision
+Cloudian users and groups automatically by CloudStack.
+
+Additionally, your CloudStack users will need to be able to resolve your CMC
+server hostname on their desktops so that they can access CMC.
+
+Example domain names that should resolve:
+
+.. cssclass:: table-striped table-bordered table-hover
+
++---------------------+----------------------+------------------------------+
+| Resolvable Name | Required By | Description |
++=====================+======================+==============================+
+| mgmt.abc-cloud.com | User's browser | CloudStack Management Server |
++---------------------+----------------------+------------------------------+
+| cmc.abc-cloud.com | User's browser | Cloudian CMC |
++---------------------+----------------------+------------------------------+
+| admin.abc-cloud.com | Management Server | Cloudian Admin Server |
++---------------------+----------------------+------------------------------+
+
+Table: DNS Name Resolution Example
+
+
+Configuring the Cloudian Connector
+----------------------------------
+
+Prerequisites
+~~~~~~~~~~~~~
+
+Cloudian ships with SSO disabled by default. You will need to enable it on each
+CMC server. Additionally, you will need to choose a unique SSO shared key that
+you will also configure in the CloudStack connector further below.
+
+Edit Puppet config to enable SSO on all CMC servers:
+
+ ::
+
+ # vi /etc/cloudian-[version]-puppet/modules/cmc/templates/mts-ui.properties.erb
+ sso.enabled=true
+ sso.shared.key=YourSecretKeyHere
+
+
+.. note::
+ Once configured in Puppet, you should roll out out to each CMC server and
+ restart CMC services. Please refer to the HyperStore documentation for how to
+ do this.
+
+Connector Configuration
+~~~~~~~~~~~~~~~~~~~~~~~
+
+The main way to configure, enable and disable the connector is using the
+CloudStack global setting. The global settings provide an easy way to configure
+the connector and synchronize setting across multiple management server(s). The
+following global setting can be accessed and changed using the CloudStack UI:
+
+.. cssclass:: table-striped table-bordered table-hover
+
++------------------------------+------------------------------------------------+
+| Global Setting | Description |
++==============================+================================================+
+| cloudian.connector.enabled | Setting to enable/disable the plugin |
++------------------------------+------------------------------------------------+
+| cloudian.admin.host | The Cloudian admin server host |
++------------------------------+------------------------------------------------+
+| cloudian.admin.port | The Cloudian admin server port, usually 19443 |
+| | (https) or 18081 (http) |
++------------------------------+------------------------------------------------+
+| cloudian.admin.protocol | The Cloudian admin server protocol, http/https |
++------------------------------+------------------------------------------------+
+| cloudian.validate.ssl | Whether to validate SSL certificate of Cloudian|
+| | admin service while making API calls |
++------------------------------+------------------------------------------------+
+| cloudian.admin.user | Basic auth user name for Cloudian admin server |
++------------------------------+------------------------------------------------+
+| cloudian.admin.password | Basic auth password for Cloudian admin server |
++------------------------------+------------------------------------------------+
+| cloudian.api.request.timeout | The admin API request timeout in seconds |
++------------------------------+------------------------------------------------+
+| cloudian.cmc.admin.user | The user id of the CMC admin that maps to |
+| | CloudStack admin user |
++------------------------------+------------------------------------------------+
+| cloudian.cmc.host | The Cloudian Management Console hostname |
++------------------------------+------------------------------------------------+
+| cloudian.cmc.port | The Cloudian Management Console port |
++------------------------------+------------------------------------------------+
+| cloudian.cmc.protocol | The Cloudian Management Console protocol |
++------------------------------+------------------------------------------------+
+| cloudian.sso.key | The shared secret as configured in Cloudian CMC|
++------------------------------+------------------------------------------------+
+
+Table: Cloudian Connector Global Settings
+
+.. note::
+ Change in only ‘cloudian.connector.enabled’ setting requires restarting of
+ all the CloudStack management server(s), rest of the setting can be changed
+ dynamically without requiring to restart the CloudStack management server(s).
+
+Enabling the Cloudian Connector
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The Cloudian Connector comes disabled by default, enabling the connector is the
+last step. You should have already configured the Cloudian Connector global
+settings. To enable the connector, ensure that the global setting
+"cloudian.connector.enabled" is set to true. Finally, restart each of the
+management server(s) to reload and enable the connector.
+
+For example, here is how you can restart the CloudStack management server
+installed on CentOS7:
+
+ ::
+
+ # systemctl restart cloudstack-management
+
+
+Troubleshooting
+~~~~~~~~~~~~~~~~
+
+Most of the trouble you may run into will be configuration related.
+
+There are a few things which can go wrong for SSO. Here are the most common
+problems and things to check:
+
+- Does the global settings cloudian.cmc.admin.user point to the correct Cloudian
+ (admin) user?
+
+- Is SSO configured and enabled on Cloudian HyperStore CMC?
+
+- Check for errors in the CMC log file.
+
+- Are both CloudStack and HyperStore CMC configured with the same cloudian.sso.key?
+
+- Check the /var/log/cloudstack/management/management-server.log file and
+ search for errors relating to SSO.
+
+- Try access the CMC host directly from the problem users host using the
+ configured cloudian.cmc.host, cloudian.cmc.port and cloudian.cmc.protocol
+ configured in the CloudStack global settings.
+
+- If you log out of the management server and log in again, does the Cloudian
+ Storage button work?
+
+
+Adding/Deleting Domains or Accounts fails: These operations use the Cloudian
+Admin Server. It's likely that something has changed with the connection or the
+admin server is down. Check list:
+
+- Is the admin server alive and listening?
+
+- Try access the admin server host directly from the problem users host using
+ the configured cloudian.admin.host, cloudian.admin.port and
+ cloudian.admin.protocol configured in the CloudStack global settings. Check the
+ configured auth settings cloudian.admin.user and cloudian.admin.password.
+
+- If you’re experiencing timeout issues, trying changing the API timeout value
+ defined in cloudian.api.request.timeout global setting.
+
+- Look for errors in the admin log file /var/log/cloudian/cloudian-admin.log.
+
+
+------------
+
+
+Cloudian as CloudStack Secondary Storage
+----------------------------------------
+
+This section is a supplementary guide for CloudStack and describes how to
+configure CloudStack to use Cloudian HyperStore as Secondary Storage. Please
+also review CloudStack’s documentation (Getting Started Guide) for configuring
+and using S3 as Secondary Storage.
+
+CloudStack, as of version 4.2.1, can utilize Cloudian HyperStore as S3 Secondary
+Storage out of the box. There is no need for any modifications or to install any
+connectors. Secondary Storage is used to store ISOs, Templates, Snapshots and
+Volumes.
+
+.. note::
+ CloudStack still requires an NFS Secondary Storage Staging Server with is
+ mentioned in the requirements below.
+
+Requirements:
+
+- CloudStack 4.5+ (installed/configured and running)
+- Cloudian HyperStore 5.0 or greater (installed/configured and running)
+
+NFS Secondary Storage Staging Server Requirement
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The use of S3 as Secondary Storage for CloudStack also requires an NFS server.
+The NFS server is required because the various hypervisors cannot yet talk
+directly to S3 but instead talk through the standard file system API. As such,
+CloudStack requires an NFS staging server which the Hypervisors use to read and
+write data from/to. The NFS storage requirements for the staging server are
+small however as space is only required while objects are staged (moving)
+between the S3 server and the VMs.
+
+
+DNS Name Resolution Requirement
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+All CloudStack Management Servers, system VMs and customer VMs (if required)
+must be able to resolve your S3 bucket names. Usually, if you already have
+Cloudian installed and running in your environment, this is already working.
+At a minimum the following names should resolve to the correct IP addresses
+using the DNS server that your Management Server and System VMs are using.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++---------------------+------------------------------+
+| Example Name | DNS Name Types |
++=====================+==============================+
+| s3.mycloud.com | Cloudian S3 Endpoint |
++---------------------+------------------------------+
+| sec.s3.mycloud.com | Bucket for Secondary Storage |
++---------------------+------------------------------+
+| s3-admin.mycloud.com| Cloudian Admin Server |
++---------------------+------------------------------+
+
+Table: Example Domain Names that should Resolve on CloudStack Servers
+
+Adding Cloudian as CloudStack Secondary Storage
+-----------------------------------------------
+
+Setup a Cloudian User and Bucket for Secondary Storage
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+S3 Secondary Storage stores the CloudStack templates, snapshots etc in a
+dedicated S3 Bucket. To properly configure CloudStack you will need to know the
+S3 Bucket name and how to access your S3 Server (the S3 endpoint, access key and
+secret key).
+
+Below, we will create a dedicated Cloudian user and a dedicated bucket which we
+will assign for use as Secondary Storage.
+
+Create a dedicated user/group:
+
+- Login to the Cloudian Management Console (CMC) as the Cloudian admin user.
+
+- Create a new group called cloudstack. Any group name is ok.
+
+- Create a new user called cloudstack in the cloudstack group. Any user name is ok.
+
+
+Create a dedicated bucket:
+
+- Login to CMC as the cloudstack user created above.
+
+- Create a bucket called secondary. Any bucket name will do.
+
+- On the top menu bar on the right hand side, use the drop down menu under your
+ user name to select Security Credentials and copy and paste your Access and
+ Secret Keys to a note for later use. CloudStack will need these when you attach
+ Cloudian as Secondary Storage in a later step below.
+
+Open Up Access to your S3 Network from Secondary Storage
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If your S3 server is on a different network to your Secondary Storage VM, you
+will need to open up access to the S3 network. This also allows users to
+download templates from their S3 object store areas.
+
+.. figure:: /_static/images/cloudian-ss_globalopt.png
+ :align: center
+ :alt: a screenshot of changing global settings
+
+.. note::
+ Editing the Global Settings requires you to restart the management server(s).
+
+Add an NFS Secondary Storage Staging Server
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+As mentioned previously, S3 Secondary Storage currently requires the use of an
+NFS Secondary Staging Server. Add NFS Secondary Storage Staging Server:
+
+- Login to CloudStack Management Server as the admin user.
+
+- Navigate to Infrastructure → Secondary Storage.
+
+- Click Select View and select Secondary Staging Store.
+
+- Click Add Secondary Staging Store.
+
+- Configure the zone, server and path for your desired secondary staging store.
+ For example nfs.mycloud.com and /export/staging.
+
+.. figure:: /_static/images/cloudian-s3_ss_cache.png
+ :align: center
+ :alt: a screenshot of adding secondary staging store
+
+Attach Cloudian as Secondary Storage
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack supports using either S3 or NFS as Secondary Storage but not both.
+The below instructions assume you are not using Secondary Storage on NFS and
+that you can delete it to add the S3 storage.
+
+.. note::
+ Already using NFS for Secondary Storage with CloudStack? You need to migrate
+ your Secondary Storage. Refer to CloudStack’s instructions for migrating
+ existing NFS Secondary Storage to an S3 object storage. CloudStack 4.5 onwards
+ supports migrating data via special commands which are described in the Getting
+ Started Guide in a section titled Upgrading from NFS to Object Storage.
+
+Adding S3 Secondary Storage:
+
+- Login to CloudStack Management Server as the admin user.
+
+- Navigate to Infrastructure → Secondary Storage.
+
+- If it exists, select and delete any existing NFS Secondary Storage server
+ setting. NOTE: Do not do this if you want to migrate existing NFS secondary
+ storage to S3. Instead, see warning above.
+
+- Click the Add Secondary Storage button. This will open up a pop-up form which
+ you can fill out similarly to below.
+
+.. figure:: /_static/images/cloudian-s3_ss_config.png
+ :align: center
+ :alt: a screenshot of configuring S3 secondary storage
+
+.. note::
+ CloudStack doesn’t currently allow you to re-edit the S3 configuration so take
+ time to double check what you enter. If you make a mistake the only options
+ currently are either a) delete and recreate the storage or b) directly edit the
+ entry in the database.
+
+When you have finished adding Cloudian as Secondary Storage in the previous
+steps, CloudStack will populate the new secondary storage with the system and
+default templates. This can take some time do download as the templates are
+quite big.
+
+.. note::
+ You can check if the system template and the default template have properly
+ downloaded to the new secondary storage by navigating to Templates, selecting a
+ template, clicking on the Zones tab and checking its Status is Ready 100%
+ Downloaded.
+
+.. note::
+ Should you continue to have problems, sometimes it is necessary to restart
+ the Secondary Storage VM. You can do this by navigating to Infrastructure,
+ System VMs, selecting and rebooting the Secondary Storage VM.
+
+CloudStack should now ready to use Cloudian HyperStore for S3 Secondary Storage.
+
+Revision History
+----------------
+
+- Fri Oct 6 2017 Rohit Yadav rohit.yadav@shapeblue.com Documentation
+ created for 4.11.0 version of the Cloudian Connector Plugin
diff --git a/source/plugins/index.rst b/source/plugins/index.rst
new file mode 100644
index 0000000..167e3d2
--- /dev/null
+++ b/source/plugins/index.rst
@@ -0,0 +1,40 @@
+.. 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 Installation Documentation master file, created by
+ sphinx-quickstart on Sat Jan 25 15:15:31 2014.
+ You can adapt this file completely to your liking, but it should at least
+ contain the root `toctree` directive.
+
+|menu_acs_logo|
+
+
+Plugins Guide
+=============
+
+
+This is the Apache CloudStack Plugins guide. This section gives information for those wishing to develop CloudStack either contributing to the CloudStack core software or writing external plugins
+
+.. toctree::
+ :maxdepth: 2
+
+ cloudian-connector
+ nicira-plugin
+ nuage-plugin
+ vxlan
+ ovs-plugin
+ ipv6
+ quota
+
diff --git a/source/plugins/ipv6.rst b/source/plugins/ipv6.rst
new file mode 100644
index 0000000..ce22360
--- /dev/null
+++ b/source/plugins/ipv6.rst
@@ -0,0 +1,199 @@
+.. 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.
+
+
+IPv6 Support in CloudStack
+===========================
+
+CloudStack supports Internet Protocol version 6 (IPv6), the recent
+version of the Internet Protocol (IP) that defines routing the network
+traffic. IPv6 uses a 128-bit address that exponentially expands the
+current address space that is available to the users. IPv6 addresses
+consist of eight groups of four hexadecimal digits separated by colons,
+for example, 5001:0dt8:83a3:1012:1000:8s2e:0870:7454. CloudStack
+supports IPv6 for public IPs in shared networks. With IPv6 support, VMs
+in shared networks can obtain both IPv4 and IPv6 addresses from the DHCP
+server. You can deploy VMs either in a IPv6 or IPv4 network, or in a
+dual network environment. If IPv6 network is used, the VM generates a
+link-local IPv6 address by itself, and receives a stateful IPv6 address
+from the DHCPv6 server.
+
+IPv6 is supported only on KVM and XenServer hypervisors. The IPv6
+support is only an experimental feature.
+
+Here's the sequence of events when IPv6 is used:
+
+#. The administrator creates an IPv6 shared network in an advanced zone.
+
+#. The user deploys a VM in an IPv6 shared network.
+
+#. The user VM generates an IPv6 link local address by itself, and gets
+ an IPv6 global or site local address through DHCPv6.
+
+
+Prerequisites and Guidelines
+----------------------------
+
+Consider the following:
+
+- CIDR size must be 64 for IPv6 networks.
+
+- The DHCP client of the guest VMs should support generating DUID based
+ on Link-layer Address (DUID- LL). DUID-LL derives from the MAC
+ address of guest VMs, and therefore the user VM can be identified by
+ using DUID. See `Dynamic Host Configuration Protocol for
+ IPv6 <http://tools.ietf.org/html/rfc3315>`__\ for more information.
+
+- The gateway of the guest network generates Router Advisement and
+ Response messages to Router Solicitation. The M (Managed Address
+ Configuration) flag of Router Advisement should enable stateful IP
+ address configuration. Set the M flag to where the end nodes receive
+ their IPv6 addresses from the DHCPv6 server as opposed to the router
+ or switch.
+
+ .. note::
+ The M flag is the 1-bit Managed Address Configuration flag for Router
+ Advisement. When set, Dynamic Host Configuration Protocol (DHCPv6) is
+ available for address configuration in addition to any IPs set by
+ using stateless address auto-configuration.
+
+- Use the System VM template exclusively designed to support IPv6.
+ Download the System VM template from
+ `http://download.cloudstack.org/systemvm/
+ <http://download.cloudstack.org/systemvm/>`__.
+
+- The concept of Default Network applies to IPv6 networks. However,
+ unlike IPv4 CloudStack does not control the routing information of
+ IPv6 in shared network; the choice of Default Network will not affect
+ the routing in the user VM.
+
+- In a multiple shared network, the default route is set by the rack
+ router, rather than the DHCP server, which is out of CloudStack
+ control. Therefore, in order for the user VM to get only the default
+ route from the default NIC, modify the configuration of the user VM,
+ and set non-default NIC's ``accept_ra`` to 0 explicitly. The
+ ``accept_ra`` parameter accepts Router Advertisements and
+ auto-configure ``/proc/sys/net/ipv6/conf/interface`` with received
+ data.
+
+
+Limitations of IPv6 in CloudStack
+---------------------------------
+
+The following are not yet supported:
+
+#. Security groups
+
+#. Userdata and metadata
+
+#. Passwords
+
+
+Guest VM Configuration for DHCPv6
+---------------------------------
+
+For the guest VMs to get IPv6 address, run dhclient command manually on
+each of the VMs. Use DUID-LL to set up dhclient.
+
+.. note::
+ The IPv6 address is lost when a VM is stopped and started. Therefore,
+ use the same procedure to get an IPv6 address when a VM is stopped and
+ started.
+
+#. Set up dhclient by using DUID-LL.
+
+ Perform the following for DHCP Client 4.2 and above:
+
+ #. Run the following command on the selected VM to get the dhcpv6
+ offer from VR:
+
+ .. parsed-literal::
+
+ dhclient -6 -D LL <dev>
+
+ Perform the following for DHCP Client 4.1:
+
+ #. Open the following to the dhclient configuration file:
+
+ .. parsed-literal::
+
+ vi /etc/dhcp/dhclient.conf
+
+ #. Add the following to the dhclient configuration file:
+
+ .. parsed-literal::
+
+ send dhcp6.client-id = concat(00:03:00, hardware);
+
+#. Get IPv6 address from DHCP server as part of the system or network
+ restart.
+
+ Based on the operating systems, perform the following:
+
+ On CentOS 6.2:
+
+ #. Open the Ethernet interface configuration file:
+
+ .. parsed-literal::
+
+ vi /etc/sysconfig/network-scripts/ifcfg-eth0
+
+ The ``ifcfg-eth0`` file controls the first NIC in a system.
+
+ #. Make the necessary configuration changes, as given below:
+
+ .. parsed-literal::
+
+ DEVICE=eth0
+ HWADDR=06:A0:F0:00:00:38
+ NM_CONTROLLED=no
+ ONBOOT=yes
+ BOOTPROTO=dhcp6
+ TYPE=Ethernet
+ USERCTL=no
+ PEERDNS=yes
+ IPV6INIT=yes
+ DHCPV6C=yes
+
+ #. Open the following:
+
+ .. parsed-literal::
+
+ vi /etc/sysconfig/network
+
+ #. Make the necessary configuration changes, as given below:
+
+ .. parsed-literal::
+
+ NETWORKING=yes
+ HOSTNAME=centos62mgmt.lab.vmops.com
+ NETWORKING_IPV6=yes
+ IPV6_AUTOCONF=no
+
+ On Ubuntu 12.10
+
+ #. Open the following:
+
+ .. parsed-literal::
+
+ etc/network/interfaces:
+
+ #. Make the necessary configuration changes, as given below:
+
+ .. parsed-literal::
+
+ iface eth0 inet6 dhcp
+ autoconf 0
+ accept_ra 1
diff --git a/source/plugins/midonet.rst b/source/plugins/midonet.rst
new file mode 100644
index 0000000..fab489e
--- /dev/null
+++ b/source/plugins/midonet.rst
@@ -0,0 +1,168 @@
+.. 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 MidoNet Plugin
+==================
+
+Introduction to the MidoNet Plugin
+----------------------------------
+
+The MidoNet plugin allows CloudStack to use the MidoNet virtualized
+networking solution as a provider for CloudStack networks and services. For
+more information on MidoNet and how it works, see
+http://www.midokura.com/midonet/.
+
+
+Features of the MidoNet Plugin
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. note::
+ In CloudStack 4.2.0 only the KVM hypervisor is supported for use in
+ combination with MidoNet.
+
+In CloudStack release 4.2.0 this plugin supports several services in the
+Advanced Isolated network mode.
+
+When tenants create new isolated layer 3 networks, instead of spinning
+up extra Virtual Router VMs, the relevant L3 elements (routers etc) are
+created in the MidoNet virtual topology by making the appropriate calls
+to the MidoNet API. Instead of using VLANs, isolation is provided by
+MidoNet.
+
+Aside from the above service (Connectivity), several extra features are
+supported in the 4.2.0 release:
+
+- DHCP
+
+- Firewall (ingress)
+
+- Source NAT
+
+- Static NAT
+
+- Port Forwarding
+
+The plugin has been tested with MidoNet version 12.12. (Caddo).
+
+
+Using the MidoNet Plugin
+------------------------
+
+Prerequisites
+~~~~~~~~~~~~~
+
+In order to use the MidoNet plugin, the compute hosts must be running
+the MidoNet Agent, and the MidoNet API server must be available. Please
+consult the MidoNet User Guide for more information. The following
+section describes the CloudStack side setup.
+
+#. CloudStack needs to have at least one physical network with the
+ isolation method set to "MIDO". This network should be enabled for
+ the Guest and Public traffic types.
+
+#. Next, we need to set the following CloudStack settings under "Global
+ Settings" in the UI:
+
+ .. cssclass:: table-striped table-bordered table-hover
+
+ +-----------------------------+------------------------------------------------------------------------+--------------------------------------------+
+ | Setting Name | Description | Example |
+ +=============================+========================================================================+============================================+
+ | midonet.apiserver.address | Specify the address at which the Midonet API server can be contacted | http://192.168.1.144:8081/midolmanj-mgmt |
+ +-----------------------------+------------------------------------------------------------------------+--------------------------------------------+
+ | midonet.providerrouter.id | Specifies the UUID of the Midonet provider router | d7c5e6a3-e2f4-426b-b728-b7ce6a0448e5 |
+ +-----------------------------+------------------------------------------------------------------------+--------------------------------------------+
+
+ Table: CloudStack settings
+
+#. We also want MidoNet to take care of public traffic, so in
+ *componentContext.xml* we need to replace this line:
+
+ ::
+
+ <bean id="PublicNetworkGuru" class="com.cloud.network.guru.PublicNetworkGuru">
+
+
+ With this:
+
+ ::
+
+ <bean id="PublicNetworkGuru" class="com.cloud.network.guru.MidoNetPublicNetworkGuru">
+
+
+.. note::
+ On the compute host, MidoNet takes advantage of per-traffic type VIF
+ driver support in CloudStack KVM.
+
+ In agent.properties, we set the following to make MidoNet take care
+ of Guest and Public traffic:
+
+ ::
+
+ libvirt.vif.driver.Guest=com.cloud.network.resource.MidoNetVifDriver
+ libvirt.vif.driver.Public=com.cloud.network.resource.MidoNetVifDriver
+
+ This is explained further in MidoNet User Guide.
+
+
+Enabling the MidoNet service provider via the UI
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To allow CloudStack to use the MidoNet Plugin the network service provider
+needs to be enabled on the physical network.
+
+The steps to enable via the UI are as follows:
+
+#. In the left navbar, click Infrastructure
+
+#. In Zones, click View All
+
+#. Click the name of the Zone on which you are setting up MidoNet
+
+#. Click the Physical Network tab
+
+#. Click the Name of the Network on which you are setting up MidoNet
+
+#. Click Configure on the Network Service Providers box
+
+#. Click on the name MidoNet
+
+#. Click the Enable Provider button in the Network tab
+
+
+Enabling the MidoNet service provider via the API
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To enable via the API, use the following API calls:
+
+*addNetworkServiceProvider*
+
+- name = "MidoNet"
+
+- physicalnetworkid = <the uuid of the physical network>
+
+*updateNetworkServiceProvider*
+
+- id = <the provider uuid returned by the previous call>
+
+- state = "Enabled"
+
+
+Revision History
+----------------
+
+0-0 Wed Mar 13 2013 Dave Cahill dcahill@midokura.com Documentation
+created for 4.2.0 version of the MidoNet Plugin
diff --git a/source/plugins/nicira-plugin.rst b/source/plugins/nicira-plugin.rst
new file mode 100644
index 0000000..2fa447b
--- /dev/null
+++ b/source/plugins/nicira-plugin.rst
@@ -0,0 +1,402 @@
+.. 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 Nicira NVP Plugin
+=====================
+
+Introduction to the Nicira NVP Plugin
+-------------------------------------
+
+The Nicira NVP plugin adds Nicira NVP as one of the available SDN
+implementations in CloudStack. With the plugin an exisiting Nicira NVP
+setup can be used by CloudStack to implement isolated guest networks and
+to provide additional services like routing and NAT.
+
+
+Features of the Nicira NVP Plugin
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The following table lists the CloudStack network services provided by
+the Nicira NVP Plugin.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++----------------------+----------------------+---------------+
+| Network Service | CloudStack version | NVP version |
++======================+======================+===============+
+| Virtual Networking | >= 4.0 | >= 2.2.1 |
++----------------------+----------------------+---------------+
+| Source NAT | >= 4.1 | >= 3.0.1 |
++----------------------+----------------------+---------------+
+| Static NAT | >= 4.1 | >= 3.0.1 |
++----------------------+----------------------+---------------+
+| Port Forwarding | >= 4.1 | >= 3.0.1 |
++----------------------+----------------------+---------------+
+
+Table: Supported Services
+
+.. note::
+ The Virtual Networking service was originally called 'Connectivity'
+ in CloudStack 4.0
+
+The following hypervisors are supported by the Nicira NVP Plugin.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++--------------+----------------------+
+| Hypervisor | CloudStack version |
++==============+======================+
+| XenServer | >= 4.0 |
++--------------+----------------------+
+| KVM | >= 4.1 |
++--------------+----------------------+
+
+Table: Supported Hypervisors
+
+.. note::
+ Please refer to the Nicira NVP configuration guide on how to prepare
+ the hypervisors for Nicira NVP integration.
+
+
+Configuring the Nicira NVP Plugin
+---------------------------------
+
+Prerequisites
+~~~~~~~~~~~~~
+
+Before enabling the Nicira NVP plugin the NVP Controller needs to be
+configured. Please review the NVP User Guide on how to do that.
+
+Make sure you have the following information ready:
+
+- The IP address of the NVP Controller
+
+- The username to access the API
+
+- The password to access the API
+
+- The UUID of the Transport Zone that contains the hypervisors in this
+ Zone
+
+- The UUID of the Gateway Service used to provide router and NAT
+ services.
+
+
+.. note::
+ The gateway service uuid is optional and is used for Layer 3
+ services only (SourceNat, StaticNat and PortForwarding)
+
+
+Zone Configuration
+~~~~~~~~~~~~~~~~~~
+
+CloudStack needs to have at least one physical network with the isolation
+method set to "STT". This network should be enabled for the Guest
+traffic type.
+
+.. note::
+ The Guest traffic type should be configured with the traffic label
+ that matches the name of the Integration Bridge on the hypervisor.
+ See the Nicira NVP User Guide for more details on how to set this up
+ in XenServer or KVM.
+
+.. figure:: /_static/images/nvp-physical-network-stt.png
+ :align: center
+ :alt: a screenshot of a physical network with the STT isolation type
+
+
+Enabling the service provider
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The Nicira NVP provider is disabled by default. Navigate to the "Network
+Service Providers" configuration of the physical network with the STT
+isolation type. Navigate to the Nicira NVP provider and press the
+"Enable Provider" button.
+
+.. note::
+ CloudStack 4.0 does not have the UI interface to configure the
+ Nicira NVP plugin. Configuration needs to be done using the API
+ directly.
+
+.. figure:: /_static/images/nvp-physical-network-stt.png
+ :align: center
+ :alt: a screenshot of an enabled Nicira NVP provider
+
+
+Device Management
+~~~~~~~~~~~~~~~~~
+
+In CloudStack a Nicira NVP setup is considered a "device" that can be added
+and removed from a physical network. To complete the configuration of
+the Nicira NVP plugin a device needs to be added to the physical
+network. Press the "Add NVP Controller" button on the provider panel and
+enter the configuration details.
+
+.. figure:: /_static/images/nvp-physical-network-stt.png
+ :align: center
+ :alt: a screenshot of the device configuration popup.
+
+
+Network Offerings
+~~~~~~~~~~~~~~~~~
+
+Using the Nicira NVP plugin requires a network offering with Virtual
+Networking enabled and configured to use the NiciraNvp element. Typical
+use cases combine services from the Virtual Router appliance and the
+Nicira NVP plugin.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++----------------------+-----------------+
+| Service | Provider |
++======================+=================+
+| VPN | VirtualRouter |
++----------------------+-----------------+
+| DHCP | VirtualRouter |
++----------------------+-----------------+
+| DNS | VirtualRouter |
++----------------------+-----------------+
+| Firewall | VirtualRouter |
++----------------------+-----------------+
+| Load Balancer | VirtualRouter |
++----------------------+-----------------+
+| User Data | VirtualRouter |
++----------------------+-----------------+
+| Source NAT | VirtualRouter |
++----------------------+-----------------+
+| Static NAT | VirtualRouter |
++----------------------+-----------------+
+| Post Forwarding | VirtualRouter |
++----------------------+-----------------+
+| Virtual Networking | NiciraNVP |
++----------------------+-----------------+
+
+Table: Isolated network offering with regular services from the Virtual
+Router.
+
+.. figure:: /_static/images/nvp-physical-network-stt.png
+ :align: center
+ :alt: a screenshot of a network offering.
+
+
+.. note::
+ The tag in the network offering should be set to the name of the
+ physical network with the NVP provider.
+
+Isolated network with network services. The virtual router is still
+required to provide network services like dns and dhcp.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++----------------------+-----------------+
+| Service | Provider |
++======================+=================+
+| DHCP | VirtualRouter |
++----------------------+-----------------+
+| DNS | VirtualRouter |
++----------------------+-----------------+
+| User Data | VirtualRouter |
++----------------------+-----------------+
+| Source NAT | NiciraNVP |
++----------------------+-----------------+
+| Static NAT | NiciraNVP |
++----------------------+-----------------+
+| Post Forwarding | NiciraNVP |
++----------------------+-----------------+
+| Virtual Networking | NiciraNVP |
++----------------------+-----------------+
+
+Table: Isolated network offering with network services
+
+
+Using the Nicira NVP plugin with VPC
+------------------------------------
+
+Supported VPC features
+~~~~~~~~~~~~~~~~~~~~~~
+
+The Nicira NVP plugin supports CloudStack VPC to a certain extent. Starting
+with CloudStack version 4.1 VPCs can be deployed using NVP isolated
+networks.
+
+It is not possible to use a Nicira NVP Logical Router for as a VPC
+Router
+
+It is not possible to connect a private gateway using a Nicira NVP
+Logical Switch
+
+
+VPC Offering with Nicira NVP
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To allow a VPC to use the Nicira NVP plugin to provision networks, a new
+VPC offering needs to be created which allows the Virtual Networking
+service to be implemented by NiciraNVP.
+
+This is not currently possible with the UI. The API does provide the
+proper calls to create a VPC offering with Virtual Networking enabled.
+However due to a limitation in the 4.1 API it is not possible to select
+the provider for this network service. To configure the VPC offering
+with the NiciraNVP provider edit the database table
+'vpc\_offering\_service\_map' and change the provider to NiciraNvp for
+the service 'Connectivity'
+
+It is also possible to update the default VPC offering by adding a row
+to the 'vpc\_offering\_service\_map' with service 'Connectivity' and
+provider 'NiciraNvp'
+
+.. figure:: /_static/images/nvp-physical-network-stt.png
+ :align: center
+ :alt: a screenshot of the mysql table.
+
+
+.. note::
+ When creating a new VPC offering please note that the UI does not
+ allow you to select a VPC offering yet. The VPC needs to be created
+ using the API with the offering UUID.
+
+
+VPC Network Offerings
+~~~~~~~~~~~~~~~~~~~~~
+
+The VPC needs specific network offerings with the VPC flag enabled.
+Otherwise these network offerings are identical to regular network
+offerings. To allow VPC networks with a Nicira NVP isolated network the
+offerings need to support the Virtual Networking service with the
+NiciraNVP provider.
+
+In a typical configuration two network offerings need to be created. One
+with the loadbalancing service enabled and one without loadbalancing.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++----------------------+--------------------+
+| Service | Provider |
++======================+====================+
+| VPN | VpcVirtualRouter |
++----------------------+--------------------+
+| DHCP | VpcVirtualRouter |
++----------------------+--------------------+
+| DNS | VpcVirtualRouter |
++----------------------+--------------------+
+| Load Balancer | VpcVirtualRouter |
++----------------------+--------------------+
+| User Data | VpcVirtualRouter |
++----------------------+--------------------+
+| Source NAT | VpcVirtualRouter |
++----------------------+--------------------+
+| Static NAT | VpcVirtualRouter |
++----------------------+--------------------+
+| Post Forwarding | VpcVirtualRouter |
++----------------------+--------------------+
+| NetworkACL | VpcVirtualRouter |
++----------------------+--------------------+
+| Virtual Networking | NiciraNVP |
++----------------------+--------------------+
+
+Table: VPC Network Offering with Loadbalancing
+
+
+Troubleshooting the Nicira NVP Plugin
+-------------------------------------
+
+UUID References
+~~~~~~~~~~~~~~~
+
+The plugin maintains several references in the CloudStack database to items
+created on the NVP Controller.
+
+Every guest network that is created will have its broadcast type set to
+Lswitch and if the network is in state "Implemented", the broadcast URI
+will have the UUID of the Logical Switch that was created for this
+network on the NVP Controller.
+
+The Nics that are connected to one of the Logical Switches will have
+their Logical Switch Port UUID listed in the nicira\_nvp\_nic\_map table
+
+.. note::
+ All devices created on the NVP Controller will have a tag set to
+ domain-account of the owner of the network, this string can be used
+ to search for items in the NVP Controller.
+
+
+Database tables
+~~~~~~~~~~~~~~~
+
+The following tables are added to the cloud database for the Nicira NVP
+Plugin
+
+.. cssclass:: table-striped table-bordered table-hover
+
++---------------------+--------------------------------------------------------------+
+| id | auto incrementing id |
++---------------------+--------------------------------------------------------------+
+| logicalswitch | uuid of the logical switch this port is connected to |
++---------------------+--------------------------------------------------------------+
+| logicalswitchport | uuid of the logical switch port for this nic |
++---------------------+--------------------------------------------------------------+
+| nic | the CloudStack uuid for this nic, reference to the nics table|
++---------------------+--------------------------------------------------------------+
+
+Table: nicira\_nvp\_nic\_map
+
+.. cssclass:: table-striped table-bordered table-hover
+
++-------------------------+-------------------------------------------------------------+
+| id | auto incrementing id |
++-------------------------+-------------------------------------------------------------+
+| uuid | UUID identifying this device |
++-------------------------+-------------------------------------------------------------+
+| physical\_network\_id | the physical network this device is configured on |
++-------------------------+-------------------------------------------------------------+
+| provider\_name | NiciraNVP |
++-------------------------+-------------------------------------------------------------+
+| device\_name | display name for this device |
++-------------------------+-------------------------------------------------------------+
+| host\_id | reference to the host table with the device configuration |
++-------------------------+-------------------------------------------------------------+
+
+Table: external\_nicira\_nvp\_devices
+
+.. cssclass:: table-striped table-bordered table-hover
+
++-----------------------+----------------------------------------------+
+| id | auto incrementing id |
++-----------------------+----------------------------------------------+
+| logicalrouter\_uuid | uuid of the logical router |
++-----------------------+----------------------------------------------+
+| network\_id | id of the network this router is linked to |
++-----------------------+----------------------------------------------+
+
+Table: nicira\_nvp\_router\_map
+
+.. note::
+ nicira\_nvp\_router\_map is only available in CloudStack 4.1 and above
+
+
+Revision History
+----------------
+
+0-0 Wed Oct 03 2012 Hugo Trippaers hugo@apache.org Documentation created
+for 4.0.0-incubating version of the NVP Plugin 1-0 Wed May 22 2013 Hugo
+Trippaers hugo@apache.org Documentation updated for CloudStack 4.1.0
+
+
+.. | nvp-physical-network-stt.png: a screenshot of a physical network with the STT isolation type | image:: ./images/nvp-physical-network-stt.png
+.. | nvp-physical-network-stt.png: a screenshot of an enabled Nicira NVP provider | image:: ./images/nvp-enable-provider.png
+.. | nvp-physical-network-stt.png: a screenshot of the device configuration popup. | image:: ./images/nvp-add-controller.png
+.. | nvp-physical-network-stt.png: a screenshot of a network offering. | image:: ./images/nvp-network-offering.png
+.. | nvp-physical-network-stt.png: a screenshot of the mysql table. | image:: ./images/nvp-vpc-offering-edit.png
diff --git a/source/plugins/nuage-plugin.rst b/source/plugins/nuage-plugin.rst
new file mode 100644
index 0000000..38eda79
--- /dev/null
+++ b/source/plugins/nuage-plugin.rst
@@ -0,0 +1,513 @@
+.. 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 Nuage VSP Plugin
+====================
+
+
+Introduction
+------------
+
+The Nuage VSP Plugin is the Nuage Networks SDN
+implementation in CloudStack, which integrates with Nuage Networks
+Virtualized Services Platform (VSP).
+The plugin can be used by CloudStack to leverage the scalability and rich features of advanced SDN being provided by the Nuage VSP SDN Platform and to implement:
+
+* Isolated Guest Networks
+* Virtual Private Clouds (VPC)
+* Shared Networks
+
+For more information about Nuage Networks, visit www.nuagenetworks.net.
+
+Supported Features
+~~~~~~~~~~~~~~~~~~
+
+The following table lists the supported Network services in a CloudStack deployment with NuageVsp being the Connectivity/Virtual Networking provider, with their providers and supported CloudStack versions.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++---------------------------+---------------------------+---------------------------+---------------------------+
+| Network Service | Isolated Networks | VPCs | Shared Networks |
++===========================+===========================+===========================+===========================+
+| Virtual Networking | NuageVsp (>=4.5) | NuageVsp (>=4.5) | NuageVsp (>=4.10) |
++---------------------------+---------------------------+---------------------------+---------------------------+
+| Dhcp | NuageVsp (>=4.5) | NuageVsp (>=4.5) | NuageVsp (>=4.10) |
++---------------------------+---------------------------+---------------------------+---------------------------+
+| SourceNat | NuageVsp (>=4.10) | NuageVsp (>=4.10) | N/A |
++---------------------------+---------------------------+---------------------------+---------------------------+
+| StaticNat | NuageVsp (>=4.5) | NuageVsp (>=4.5) | N/A |
++---------------------------+---------------------------+---------------------------+---------------------------+
+| Firewall | NuageVsp (>=4.5) | N/A | N/A |
++---------------------------+---------------------------+---------------------------+---------------------------+
+| NetworkACL | N/A | NuageVsp (>=4.5) | N/A |
++---------------------------+---------------------------+---------------------------+---------------------------+
+| UserData | VirtualRouter (>=4.5) | VpcVirtualRouter (>=4.5) | VirtualRouter (>=4.10) |
++---------------------------+---------------------------+---------------------------+---------------------------+
+| Dns | VirtualRouter (>=4.10) | VpcVirtualRouter (>=4.10) | N/A |
++---------------------------+---------------------------+---------------------------+---------------------------+
+| Internal Lb | N/A | InternalLbVm (>=4.9) | N/A |
++---------------------------+---------------------------+---------------------------+---------------------------+
+
+Table: Supported Network Services
+
+.. note::
+ The Virtual Networking service was originally called 'Connectivity'
+ in CloudStack 4.0
+
+Supported Hypervisors
+~~~~~~~~~~~~~~~~~~~~~
+
+The following hypervisors are supported by the Nuage VSP Plugin, with their supported CloudStack versions.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++----------------------+----------------------+
+| Hypervisor | CloudStack version |
++======================+======================+
+| KVM 7.x | >= 4.5 |
++----------------------+----------------------+
+| VMware ESXi 5.5 | >= 4.5 |
++----------------------+----------------------+
+| VMware ESXi 6.0 | >= 4.9 |
++----------------------+----------------------+
+
+Table: Supported Hypervisors
+
+Supported Nuage VSP SDN Platform Versions
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The following Nuage VSP SDN Platform versions are supported by the Nuage VSP Plugin, with their supported CloudStack versions.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++----------------------+----------------------+
+| Nuage VSP version | CloudStack version |
++======================+======================+
+| Nuage VSP v3.2 | >= 4.5 |
++----------------------+----------------------+
+| Nuage VSP v4.0 | >= 4.10 |
++----------------------+----------------------+
+
+Table: Supported Nuage VSP SDN Platform Versions
+
+
+Configuring The Nuage VSP Plugin
+--------------------------------
+
+Prerequisites
+~~~~~~~~~~~~~
+
+Before enabling and using the Nuage VSP Plugin with CloudStack.
+
+1. Verify that the CloudStack deployment (hypervisors) and Nuage VSP SDN Platform version you intend to use is being supported.
+
+.. Note:: Only the release notes for Nuage VSP contain the most up-to-date information on different supported versions. Please check them to verify that the information in this document is up-to-date.
+
+2. Prepare and configure the hypervisors for CloudStack integration with Nuage VSP SDN Platform.
+
+.. note::
+ Please refer to the Nuage VSP Install Guide on how to prepare the hypervisors for Nuage VSP SDN Platform integration.
+
+Required Nuage VSD Configuration
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When configuring Nuage VSP as the network service provider in a CloudStack Zone, a CSP user must be added in Nuage VSD, and this user must be added to the CMS group. See `Enable Nuage VSP Network Service Provider`_.
+
+.. note::
+ Nuage VSD is the programmable policy and analytics engine of the Nuage VSP SDN Platform with which the Nuage VSP Plugin interacts.
+
+Zone Configuration
+~~~~~~~~~~~~~~~~~~
+
+Select VSP Isolation Method
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The Nuage VSP solution is NOT supported in Basic zone provisioning mode.
+
+1. When adding a zone, the CloudStack administrator should select **Advanced** mode in the zone wizard.
+2. When laying out the physical network configuration during zone provisioning, the **Guest** network traffic should be put in a separate physical network of its own.
+3. This physical network carrying the **Guest** traffic should have **VSP** as the **Isolation Method**.
+
+.. figure:: /_static/images/nuage_vsp_isolation_method_setting.png
+
+ Setting Isolation Method to VSP
+
+Update Traffic Labels
+~~~~~~~~~~~~~~~~~~~~~
+
+**Guest Traffic Type**
+
+Select **Edit** on the **Guest** traffic type panel and update the Traffic Label:
+
+- For KVM, use **alubr0** as the **KVM Traffic Label**.
+
+.. figure:: /_static/images/nuage_kvm_traffic_label.jpg
+
+ Specifying the Traffic Type in KVM
+
+- For VMware ESXi, use the switch name used by **dVRS** for guest networking as the **vSwitch Name**, leave the **VLAN ID** field blank, and select **VMware vNetwork Distributed Switch** in the **vSwitch Type** drop down field.
+
+.. figure:: /_static/images/nuage_vmware_traffic_label.jpg
+
+ Specifying the Traffic Type in VMware ESXi
+
+Enable Nuage VSP Network Service Provider
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Nuage VSP must be added and enabled as a Network Service Provider in the CloudStack Zone before it can be used.
+
+:Step 1: Select **Infrastructure > Zone > [zone name] > Physical Network 2 > Configure Network Service Providers > Nuage Vsp > +**, which brings up the **Add Nuage Virtualized Services Directory (VSD)** panel.
+
+:Step 2: Enter the Nuage VSD **Host Name**, **Username** and **Password** that was previously created.
+
+:Step 3: Specify the Nuage VSD API version by entering the API version in the appropriate field (format: ``v4_0``).
+
+:Step 4: *EITHER* Add **Nuage VSD** by clicking the **OK** button,
+
+ *OR* use Nuage VSP API calls to configure Nuage VSP as a Network Service Provider in the CloudStack Zone; see `Configure Nuage VSP API`_ in the Appendix of this document.
+
+.. figure:: /_static/images/nuage_vsd_device_add.png
+
+ Adding Nuage VSD as the Network Service Provider
+
+:Step 5: Go to **Infrastructure > Zones > [zone name] > Physical Network 2 > Network Service Providers > Nuage Vsp > Devices > Details** tab as shown in the figure "Enabling Nuage VSP Network Service Provider" below. This indicates the state of Nuage VSP Network Service Provider. Enable Nuage VSP Network Service Provider by clicking **Enable**.
+
+.. figure:: /_static/images/nuage_vsp_nsp_enable.png
+
+ Enabling Nuage VSP Network Service Provider
+
+:Step 6: (Optional) View the Nuage VSP Network Service Provider status on the list of Network Service Providers on the **Infrastructure > Zones > [zone name] > Physical Network 2 > Network Service Providers** page;
+
+.. figure:: /_static/images/nuage_vsp_nsp_status.png
+
+ Viewing Network Service Providers Status
+
+
+Using The Nuage VSP Plugin
+--------------------------
+
+Network Offerings
+~~~~~~~~~~~~~~~~~
+
+There are three types of Network Offerings that can be created:
+
+- If Isolated Networks are required, then create a **Isolated** guest type network offering for use with Isolated Networks.
+- If VPC deployments are required, then create a new **Isolated** guest type network offering for such deployments.
+- If Shared Networks are required, then create a new **Shared** guest type network offering for use with Shared Networks.
+
+.. note::
+ **Per Zone** MUST always be selected as the **Supported Source NAT type** when **Source NAT** service is being provided by **NuageVsp**.
+
+Create and Enable Isolated Network Offering
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+1. Select **Service Offerings > Select Offering: Network Offerings > Add network offering**, which brings up the **Add network offering**.
+
+2. In the **Add network offering** panel, add a **Name** and a **Description** to the network offering. Select **Isolated** as the **Guest Type**. In the **Supported Services** field select services and providers that are supported by the Nuage VSP Plugin for Isolated Networks, see `Supported Features`_ at the beginning of this document.
+
+.. figure:: /_static/images/nuage_iso_net_off.png
+
+ Creating Isolated Network Offering
+
+3. Click the **OK** button to create the network offering.
+
+4. After the network offering has been successfully created, enable it from the **Service Offerings - Network Offerings** list.
+
+Create and Enable VPC Network Offering
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+1. Select **Service Offerings > Select Offering: Network Offerings > Add network offering**, which brings up the **Add network offering**.
+
+2. In the **Add network offering** panel, add a **Name** and a **Description** to the network offering. Select **Isolated** as the **Guest Type**. Select the **VPC** field. In the **Supported Services** field select services and providers that are supported by the Nuage VSP Plugin for VPCs, see `Supported Features`_ at the beginning of this document.
+
+.. figure:: /_static/images/nuage_vpc_net_off.png
+
+ Creating VPC Network Offering
+
+3. Click the **OK** button to create the network offering.
+
+4. After the network offering has been successfully created, enable it from the **Service Offerings - Network Offerings** list.
+
+Create and Enable Shared Network Offering
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+1. Select **Service Offerings > Select Offering: Network Offerings > Add network offering**, which brings up the **Add network offering**.
+
+2. In the **Add network offering** panel, add a **Name** and a **Description** to the network offering. Select **Shared** as the **Guest Type**. In the **Supported Services** field select services and providers that are supported by the Nuage VSP Plugin for Shared Networks, see `Supported Features`_ at the beginning of this document.
+
+.. figure:: /_static/images/nuage_sha_net_off.png
+
+ Creating Shared Network Offering
+
+.. note::
+ Selecting the **Supporting Public Access** field in the Shared Network offering enables Public/Internet access to the VMs in the Shared Network.
+
+3. Click the **OK** button to create the network offering.
+
+4. After the network offering has been successfully created, enable it from the **Service Offerings - Network Offerings** list.
+
+VPC Offerings
+~~~~~~~~~~~~~
+
+Pre-created and Enabled Nuage VSP VPC Offering
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+A VPC offering by the name **Nuage VSP VPC Offering** is pre-created and enabled in the list of **Service Offerings - VPC Offerings** (Select **Service Offerings > Select Offering: VPC Offerings**) which contains all the services and providers that are supported by the Nuage VSP Plugin for VPCs.
+
+.. figure:: /_static/images/nuage_vsp_vpc_off.png
+
+ Pre-created and Enabled Nuage VSP VPC Offering
+
+(Optional) Create and Enable VPC Offering
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+1. Select **Service Offerings > Select Offering: VPC Offerings > Add VPC Offering**, which brings up the **Add VPC Offering**.
+
+2. In the **Add VPC Offering** panel, add a **Name** and a **Description** to the network offering. In the **Supported Services** field select services and providers that are supported by the Nuage VSP Plugin for VPCs, see `Supported Features`_ at the beginning of this document.
+
+.. figure:: /_static/images/nuage_vpc_off.png
+
+ Creating VPC Offering
+
+3. Click the **OK** button to create the VPC Offering.
+
+4. After the VPC Offering has been successfully created, enable it from the **Service Offerings - VPC Offerings** list.
+
+
+Dedicated Features Provided by The Nuage VSP Plugin
+---------------------------------------------------
+
+Nuage VSP Domain Template Feature Support for CloudStack
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+All the constructs (parameters and abstractions) defined in a Nuage VSD domain template can be made available to domain instances (i.e. networks) created in CloudStack. To do this, configure the Nuage VSP Plugin to use a pre-created Nuage VSD domain template when instantiating domains (i.e. creating networks). Networks created in CloudStack will then use domain instances created from the domain template.
+
+Typical use-cases are:
+
+* The basic ACLs on the top and bottom that bracket or 'contain' the end-user's ACLs.
+* Leakable domains/GRT Leaking (Nuage VSP feature).
+
+To configure a Nuage VSP domain template for use by CloudStack, use the Nuage VSD Architect (VSP's GUI) to create a domain template and configure it in the following CloudStack global settings.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++-------------------------------------------+---------+------------------------------------------------------------------------------------------+---------------------------------+
+| Parameter | Type | Explanation | Supported CloudStack versions |
++===========================================+=========+==========================================================================================+=================================+
+| nuagevsp.isolatedntwk.domaintemplate.name | String | Name of the Nuage VSP domain template to use for creating domains for isolated networks | >= 4.5 |
++-------------------------------------------+---------+------------------------------------------------------------------------------------------+---------------------------------+
+| nuagevsp.vpc.domaintemplate.name | String | Name of the Nuage VSP domain template to use for creating the domain for VPCs | >= 4.5 |
++-------------------------------------------+---------+------------------------------------------------------------------------------------------+---------------------------------+
+| nuagevsp.sharedntwk.domaintemplate.id | UUID | UUID of the Nuage VSP domain template to use for creating the domain for Shared Networks | >= 4.10 |
++-------------------------------------------+---------+------------------------------------------------------------------------------------------+---------------------------------+
+
+Table: CloudStack Global Settings For Configuring Nuage VSP Domain Template Feature
+
+Nuage VSP Source NAT via the Underlay Feature Support For CloudStack
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Supported CloudStack versions: >= 4.10
+
+CloudStack provides Source NAT service to enable guest VMs to send traffic out to the Internet without requiring a Static NAT IP (public IP) assigned to the VM. The Source NAT service must be enabled as part of the network offering used for creating the guest network. When a network is created using this network offering, the first public IP from the assigned public IP range is automatically acquired as the Source NAT IP for the network. All VMs attached to this network then use that Source NAT IP to send traffic to the Internet.
+
+The Nuage VSP Plugin for CloudStack supports CloudStack's native Source NAT service and enhances it by restricting to a minimum the number of public IP addresses assigned to any given tenant. This is achieved by not allocating a Source NAT IP for every network that is created.
+
+The Source NAT service that Nuage VSP calls the Port Address Translation (PAT) feature uses the hypervisor IP as the Source NAT IP address for all VMs in the hypervisor that need to send traffic out to the Internet. Configure this during Nuage VSP installation using the instructions given in the Nuage VSP Install Guide.
+
+This feature is supported for both VPCs and Isolated Networks. In the case of VPCs, Source NAT is applied at the Nuage VSP domain level, therefore there is no customization on the individual VPC network (tier) level.
+
+All VPCs and Isolated networks that are created from a Nuage VSP Source NAT-enabled network offering have this feature enabled automatically. An example Nuage VSP Source NAT-enabled network offering is shown in the figure "Nuage VSP Source NAT-enabled Network Offering" below.
+
+.. figure:: /_static/images/nuage_source_nat_net_off.png
+
+ Nuage VSP Source NAT-enabled Network Offering
+
+Nuage VSP Static NAT via the Underlay Feature Support For CloudStack
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Supported CloudStack versions: >= 4.10
+
+Static NAT is supported in Nuage VSP as FIP (Floating IP). Prior to Nuage VSP v3.2, FIP in Nuage VSP required a VXLAN GW/PE to be present in the data center. In Nuage VSP v3.2 and above FIP is supported via the underlay, which removes the requirement for a GW/PE in the DC.
+
+For the Static NAT without GW/PE feature to be operational in the CloudStack plugin, FIP in Nuage VSP must be configured to use the underlay. This operation takes place during Nuage VSP installation; instructions can be found in the Nuage VSP Install Guide.
+
+A new API called ``nuageunderlayvlaniprange`` has been introduced to enable/disable Static NAT via the Underlay feature support for CloudStack public IP ranges being used for Static NAT service. This API specifies whether the FIP to underlay support is required for the corresponding FIP subnet in Nuage VSD since there is no GW/PE in the data center. When the ``nuageunderlayvlaniprange`` API has been enabled/disabled for a public IP range and Static NAT is enabled on at-least one of its Public IPs, the plugin creates the corresponding shared FIP subnet in Nuage VSD using the ``sharednetworkresources`` API with the underlay flag set accordingly. The ``nuageunderlayvlaniprange`` API usage is shown in the figure "nuageunderlayvlaniprange API Usage" below.
+
+.. figure:: /_static/images/nuage_underlay_api_usage.png
+
+ nuageunderlayvlaniprange API Usage
+
+By default, the Nuage VSP Plugin creates the corresponding shared FIP subnet in Nuage VSD with the underlay flag set to false (disabled). There is no support for the ``nuageunderlayvlaniprange`` API from the CloudStack UI.
+
+.. note::
+ Enabling/disabling the ``nuageunderlayvlaniprange`` API for CloudStack public IP ranges is supported only before the Nuage VSP plugin creates the corresponding shared FIP subnet in Nuage VSD. After a shared FIP subnet is created in Nuage VSD, its underlay flag cannot be changed. To change the underlay flag for a given shared FIP subnet, delete the Public vLanIPRange, recreate it and enable/disable the ``nuageunderlayvlaniprange`` API for it.
+
+
+Running The Nuage VSP Plugin Specific Marvin Tests
+--------------------------------------------------
+
+The Nuage VSP Plugin specific Marvin tests can be found under the directory test/integration/plugins/nuagevsp/ in the cloudstack tree.
+
+Here is the list of required Python packages and dependencies to run The Nuage VSP Plugin specific Marvin tests:
+
+- marvin
+- vspk
+- libVSD
+- pyyaml
+- netaddr
+- futures
+
+.. note::
+ vspk is a Python SDK for Nuage VSP's VSD and libVSD is a library that wraps vspk package, which are open sourced and can be found at https://github.com/nuagenetworks.
+
+Here is an example nosetests command to run The Nuage VSP Plugin specific Marvin tests:
+
+::
+
+ nosetests --with-marvin --marvin-config=path-to-marvin-config-file/nuage_marvin.cfg path-to-marvin-tests/test/integration/plugins/nuagevsp/test_nuage_vsp.py
+
+.. note::
+ For an example Marvin config file (i.e. nuage_marvin.cfg) required to run The Nuage VSP Plugin specific Marvin tests, refer `Nuage VSP Marvin Config File Format`_ in the Appendix of this document.
+
+
+Appendix
+--------
+
+Configure Nuage VSP API
+~~~~~~~~~~~~~~~~~~~~~~~
+
+To configure Nuage VSP as a Network Service Provider in the CloudStack Zone.
+
+1. Add Nuage VSP as a Network Service Provider in the Physical Network 2:
+
+::
+
+ cloudmonkey add networkserviceprovider name=NuageVsp physicalnetworkid=<physicalNetwork2Id>
+
+2. Add the Nuage VSD as a Nuage VSP Device in the Physical Network 2:
+
+::
+
+ cloudmonkey add nuagevspdevice physicalnetworkid=<physicalNetwork2Id> hostname=<hostnameOfNuageVsp> username=<usernameOfNuageVspUser> password=<passwordOfNuageVspUser> port=<portUsedByNuageVsp> apiversion=<apiVersionOfNuageVsp> retrycount=<nrOfRetriesOnFailure> retryinterval=<intervalBetweenRetries>
+
+
+Nuage VSP Marvin Config File Format
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Format for the Marvin config file required to run The Nuage VSP Plugin specific Marvin tests.
+
+::
+
+ {
+ "zones": [
+ {
+ "name": "ZONE1NAME",
+ "physical_networks": [
+ {
+ "name": "Physical Network 1",
+ "isolationmethods": [
+ "VLAN"
+ ]
+ },
+ {
+ "name": "Physical Network 2",
+ "isolationmethods": [
+ "VSP"
+ ],
+ "providers": [
+ {
+ "name": "NuageVsp",
+ "devices": [
+ {
+ "username": "VSDUSERNAME",
+ "retryinterval": "60",
+ "hostname": "VSDSERVER",
+ "apiversion": "VSDVERSION",
+ "retrycount": "4",
+ "password": "VSDUSERPASSWORD",
+ "port": VSDPORT
+ }
+ ]
+ }
+ ]
+ }
+ ],
+ "dcInternetConnectivityInfo" : {
+ "available": "INTERNETAVAILABLE",
+ "httpProxy": "HTTPPROXY",
+ "httpsProxy": "HTTPSPROXY"
+ }
+ },
+ {
+ "name": "ZONE2NAME",
+ "physical_networks": [
+ {
+ "name": "Physical Network 1",
+ "isolationmethods": [
+ "VLAN"
+ ]
+ },
+ {
+ "name": "Physical Network 2",
+ "isolationmethods": [
+ "VSP"
+ ],
+ "providers": [
+ {
+ "name": "NuageVsp",
+ "devices": [
+ {
+ "username": "VSDUSERNAME",
+ "retryinterval": "60",
+ "hostname": "VSDSERVER",
+ "apiversion": "VSDVERSION",
+ "retrycount": "4",
+ "password": "VSDUSERPASSWORD",
+ "port": VSDPORT
+ }
+ ]
+ }
+ ]
+ }
+ ],
+ "dcInternetConnectivityInfo" : {
+ "available": "INTERNETAVAILABLE",
+ "httpProxy": "HTTPPROXY",
+ "httpsProxy": "HTTPSPROXY"
+ }
+ }
+ ],
+ "dbSvr": {
+ "dbSvr": "DBSERVER",
+ "passwd": "DBPASSWORD",
+ "db": "cloud",
+ "port": 3306,
+ "user": "DBUSERNAME"
+ },
+ "logger":
+ {
+ "LogFolderPath": "/tmp/LOGFOLDERNAME"
+ },
+ "mgtSvr": [
+ {
+ "mgtSvrIp": "MGNTSERVERIP",
+ "port": 8096,
+ "user": "MGNTUSERNAME",
+ "passwd": "MGNTPASSWORD"
+ }
+ ]
+ }
+
diff --git a/source/plugins/ovs-plugin.rst b/source/plugins/ovs-plugin.rst
new file mode 100644
index 0000000..59936fa
--- /dev/null
+++ b/source/plugins/ovs-plugin.rst
@@ -0,0 +1,274 @@
+.. 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 OVS Plugin
+==============
+
+Introduction to the OVS Plugin
+------------------------------
+
+The OVS plugin is the native SDN
+implementations in CloudStack, using GRE isolation method. The plugin can be
+used by CloudStack to implement isolated guest networks and to provide
+additional services like NAT, port forwarding and load balancing.
+
+
+Features of the OVS Plugin
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The following table lists the CloudStack network services provided by
+the OVS Plugin.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++----------------------+----------------------+
+| Network Service | CloudStack version |
++======================+======================+
+| Virtual Networking | >= 4.0 |
++----------------------+----------------------+
+| Static NAT | >= 4.3 |
++----------------------+----------------------+
+| Port Forwarding | >= 4.3 |
++----------------------+----------------------+
+| Load Balancing | >= 4.3 |
++----------------------+----------------------+
+
+Table: Supported Services
+
+.. note::
+ The Virtual Networking service was originally called 'Connectivity'
+ in CloudStack 4.0
+
+The following hypervisors are supported by the OVS Plugin.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++--------------+----------------------+
+| Hypervisor | CloudStack version |
++==============+======================+
+| XenServer | >= 4.0 |
++--------------+----------------------+
+| KVM | >= 4.3 |
++--------------+----------------------+
+
+Table: Supported Hypervisors
+
+
+Configuring the OVS Plugin
+--------------------------
+
+Prerequisites
+~~~~~~~~~~~~~
+
+Before enabling the OVS plugin the hypervisor needs to be install OpenvSwitch.
+Default, XenServer has already installed OpenvSwitch. However, you must
+install OpenvSwitch manually on KVM. CentOS 6.4 and OpenvSwitch 1.10 are
+recommended.
+
+KVM hypervisor:
+
+- CentOS 6.4 is recommended.
+
+- To make sure that the native bridge module will not interfere with
+ openvSwitch the bridge module should be added to the blacklist. See the
+ modprobe documentation for your distribution on where to find the blacklist.
+ Make sure the module is not loaded either by rebooting or executing rmmod
+ bridge before executing next steps.
+
+
+Zone Configuration
+~~~~~~~~~~~~~~~~~~
+
+CloudStack needs to have at least one physical network with the isolation
+method set to “GRE”. This network should be enabled for the Guest
+traffic type.
+
+.. note::
+ With KVM, the traffic type should be configured with the traffic label
+ that matches the name of the Integration Bridge on the hypervisor. For
+ example, you should set the traffic label as following:
+
+ - Management & Storage traffic: cloudbr0
+
+ - Guest & Public traffic: cloudbr1
+ See KVM networking configuration guide for more detail.
+
+
+.. figure:: /_static/images/ovs-physical-network-gre.png
+ :align: center
+ :alt: a screenshot of a physical network with the GRE isolation type
+
+
+Agent Configuration
+~~~~~~~~~~~~~~~~~~~
+
+.. note::
+ Only for KVM hypervisor
+
+- Configure network interfaces:
+
+ ::
+
+ /etc/sysconfig/network-scripts/ifcfg-eth0
+ DEVICE=eth0
+ BOOTPROTO=none
+ IPV6INIT=no
+ NM_CONTROLLED=no
+ ONBOOT=yes
+ TYPE=OVSPort
+ DEVICETYPE=ovs
+ OVS_BRIDGE=cloudbr0
+
+ /etc/sysconfig/network-scripts/ifcfg-eth1
+ DEVICE=eth1
+ BOOTPROTO=none
+ IPV6INIT=no
+ NM_CONTROLLED=no
+ ONBOOT=yes
+ TYPE=OVSPort
+ DEVICETYPE=ovs
+ OVS_BRIDGE=cloudbr1
+
+ /etc/sysconfig/network-scripts/ifcfg-cloudbr0
+ DEVICE=cloudbr0
+ ONBOOT=yes
+ DEVICETYPE=ovs
+ TYPE=OVSBridge
+ BOOTPROTO=static
+ IPADDR=172.16.10.10
+ GATEWAY=172.16.10.1
+ NETMASK=255.255.255.0
+ HOTPLUG=no
+
+ /etc/sysconfig/network-scripts/ifcfg-cloudbr1
+ DEVICE=cloudbr1
+ ONBOOT=yes
+ DEVICETYPE=ovs
+ TYPE=OVSBridge
+ BOOTPROTO=none
+ HOTPLUG=no
+
+ /etc/sysconfig/network
+ NETWORKING=yes
+ HOSTNAME=testkvm1
+ GATEWAY=172.10.10.1
+
+- Edit /etc/cloudstack/agent/agent.properties
+
+ ::
+
+ network.bridge.type=openvswitch
+ libvirt.vif.driver=com.cloud.hypervisor.kvm.resource.OvsVifDriver
+
+
+Enabling the service provider
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The OVS provider is disabled by default. Navigate to the "Network
+Service Providers" configuration of the physical network with the GRE
+isolation type. Navigate to the OVS provider and press the
+"Enable Provider" button.
+
+.. figure:: /_static/images/ovs-physical-network-gre-enable.png
+ :align: center
+ :alt: a screenshot of an enabled OVS provider
+
+
+Network Offerings
+~~~~~~~~~~~~~~~~~
+
+Using the OVS plugin requires a network offering with Virtual
+Networking enabled and configured to use the OVS element. Typical
+use cases combine services from the Virtual Router appliance and the
+OVS plugin.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++----------------------+-----------------+
+| Service | Provider |
++======================+=================+
+| VPN | VirtualRouter |
++----------------------+-----------------+
+| DHCP | VirtualRouter |
++----------------------+-----------------+
+| DNS | VirtualRouter |
++----------------------+-----------------+
+| Firewall | VirtualRouter |
++----------------------+-----------------+
+| Load Balancer | OVS |
++----------------------+-----------------+
+| User Data | VirtualRouter |
++----------------------+-----------------+
+| Source NAT | VirtualRouter |
++----------------------+-----------------+
+| Static NAT | OVS |
++----------------------+-----------------+
+| Post Forwarding | OVS |
++----------------------+-----------------+
+| Virtual Networking | OVS |
++----------------------+-----------------+
+
+Table: Isolated network offering with regular services from the Virtual
+Router.
+
+.. figure:: /_static/images/ovs-network-offering.png
+ :align: center
+ :alt: a screenshot of a network offering.
+
+
+.. note::
+ The tag in the network offering should be set to the name of the
+ physical network with the OVS provider.
+
+Isolated network with network services. The virtual router is still
+required to provide network services like dns and dhcp.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++----------------------+-----------------+
+| Service | Provider |
++======================+=================+
+| DHCP | VirtualRouter |
++----------------------+-----------------+
+| DNS | VirtualRouter |
++----------------------+-----------------+
+| User Data | VirtualRouter |
++----------------------+-----------------+
+| Source NAT | VirtualRouter |
++----------------------+-----------------+
+| Static NAT | OVS |
++----------------------+-----------------+
+| Post Forwarding | OVS |
++----------------------+-----------------+
+| Load Balancing | OVS |
++----------------------+-----------------+
+| Virtual Networking | OVS |
++----------------------+-----------------+
+
+Table: Isolated network offering with network services
+
+
+Using the OVS plugin with VPC
+-----------------------------
+
+OVS plugin does not work with VPC at that time
+
+
+Revision History
+----------------
+
+0-0 Mon Dec 2 2013 Nguyen Anh Tu tuna@apache.org Documentation
+created for 4.3.0 version of the OVS Plugin
diff --git a/source/plugins/quota.rst b/source/plugins/quota.rst
new file mode 100644
index 0000000..2c6bd5e
--- /dev/null
+++ b/source/plugins/quota.rst
@@ -0,0 +1,189 @@
+.. 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.
+
+
+Quota Plugin
+=============
+
+Quota service, while allowing for scalability, will make sure that the cloud is
+not exploited by attacks, careless use and program errors. To address this
+problem, employ the quota-enforcement service that allows resource
+usage within certain bounds as defined by policies and available quotas for
+various entities. Quota service extends the functionality of usage server to
+provide a measurement for the resources used by the accounts and domains using a
+common unit referred to as cloud currency in this document. It can be configured
+to ensure that your usage won’t exceed the budget allocated to accounts/domain
+in cloud currency. It will let user know how much of the cloud resources he is
+using. It will help the cloud admins, if they want, to ensure that a user does
+not go beyond his allocated quota. Per usage cycle if an account is found to be
+exceeding its quota then it is locked. Locking an account means that it will not
+be able to initiate a new resource allocation request, whether it is more
+storage or an additional ip. To unlock an account you need to add more credit to it.
+In case you want the locking to be disabled on global or on account scope those
+provisions are also provided. Needless to say quota service as well as any action
+on the account is configurable.
+
+Enabling the Quota Service
+----------------------------
+
+Before installing and configuring the quota service you need to make sure that
+the Usage Server has been installed. This requires extra steps beyond just
+installing the CloudStack software. See Installing the Usage Server (Optional)
+in the Advanced Installation Guide.
+
+#. enable.usage.server: Set to true to enable usage server.
+
+The quota plugin is disabled by default. To enable it goto Global Settings and
+set the following global configuration to true:
+
+#. quota.enable.service
+
+By default Quota service does not lock the accounts that have exceeded the quota
+usage. To enable quota service to lock accounts set the following global
+configuration to true:
+
+#. quota.enable.enforcement
+
+The other configurations that are there for quota service are as:
+
+#. quota.currency.symbol : The symbol that is used before any currency
+ figure in various quota forms and reports.
+#. quota.usage.smtp.host: Quota SMTP host for sending quota alerts.
+#. quota.usage.smtp.port: Quota SMTP port.
+#. quota.usage.smtp.user: Quota SMTP user.
+#. quota.usage.smtp.password: Quota SMTP password.
+#. quota.usage.smtp.sender: Quota SMTP alert sender email address.
+#. quota.usage.smtp.useAuth: If true, use secure SMTP authentication when sending emails.
+#. quota.usage.smtp.connection.timeout: Quota SMTP server connection timeout duration.
+
+There are several configuration variables that are inherited from usage server,
+these are listed below:
+
+#. usage.aggregation.timezone
+
+All these are described in details in Usage Server documentation.
+
+Restart the Management Server and the Usage Server to enable the set configuration
+values.
+
+.. code:: bash
+
+ service cloudstack-management restart
+ service cloudstack-usage restart
+
+Once the quota service is running it will calculate the quota balance for each account.
+The quota usage is calculated as per the quota tariff provided by the site administrator.
+
+
+Quota Tariff
+-------------
+
+The following table shows all quota types for which you can specify tariff.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++------------------+-----------------------------------+--------------------------+
+| Type ID | Type Name | Tariff Description |
+| | | |
++==================+===================================+==========================+
+| 1 | RUNNING\_VM | One month of running |
+| | | Compute-Month |
++------------------+-----------------------------------+--------------------------+
+| 2 | ALLOCATED\_VM | One month of allocated |
+| | | VM |
++------------------+-----------------------------------+--------------------------+
+| 3 | IP\_ADDRESS | Quota for a month of |
+| | | allocated IP |
++------------------+-----------------------------------+--------------------------+
+| 4 | NETWORK\_BYTES\_SENT | Quota for 1GB bytes sent |
++------------------+-----------------------------------+--------------------------+
+| 5 | NETWORK\_BYTES\_RECEIVED | Quota for 1GB bytes sent |
++------------------+-----------------------------------+--------------------------+
+| 6 | VOLUME | Quota for 1 GB of |
+| | | Volume use for a month |
++------------------+-----------------------------------+--------------------------+
+| 7 | TEMPLATE | Quota for 1 GB of |
+| | | Template use for a month |
++------------------+-----------------------------------+--------------------------+
+| 8 | ISO | Quota for 1 GB of |
+| | | ISO use for a month |
++------------------+-----------------------------------+--------------------------+
+| 9 | SNAPSHOT | Quota for 1 GB of |
+| | | SNAPSHOT use for a month |
++------------------+-----------------------------------+--------------------------+
+| 11 | LOAD\_BALANCER\_POLICY | Quota for load balancer |
+| | | policy month |
++------------------+-----------------------------------+--------------------------+
+| 12 | PORT\_FORWARDING\_RULE | Quota for port forwarding|
+| | | policy month |
++------------------+-----------------------------------+--------------------------+
+| 13 | NETWORK\_OFFERING | Quota for network |
+| | | Offering for a month |
++------------------+-----------------------------------+--------------------------+
+| 14 | VPN\_USERS | Quota for VPN usage |
+| | | for a month |
++------------------+-----------------------------------+--------------------------+
+| 15 | CPU\_CLOCK\_RATE | The tariff for using |
+| | | 1 CPU i100 MHz clock |
++------------------+-----------------------------------+--------------------------+
+| 16 | CPU\_NUMBER | The quota tariff for |
+| | | using 1 virtual CPU. |
++------------------+-----------------------------------+--------------------------+
+| 17 | MEMORY | The quota tariff for |
+| | | using 1MB RAM size. |
++------------------+-----------------------------------+--------------------------+
+
+The quota tariff can be listed using listQuotaTariff API.
+
+quotaTariff: Lists all quota tariff plans
+
+The tariff for each of the above can be set by using the updateQuotaTariff API.
+
+Quota Credits
+-------------
+
+The quota credit (quotaCredit) API lets you add or remove quota currency credits to
+an account. With this API you can also control the quota enforcement policy at
+account level. This will enable you to have some accounts where the quota policy is
+not enforced. The overall quota enforcement is controlled by the quota.enable.enforcement
+global setting.
+
+In addition to above the quota API lets you can fine tune the alert generation by specifying
+the quota threshold for each account. If not explictly stated, the threshold is taken as 80%
+of the last deposit.
+
+Quota Balance
+--------------
+
+Quota balance API states the start balance and end balance(optional) from a start date
+to end date (optional).
+
+Quota Statement
+----------------
+
+Quota statement for a period consist of the quota usage under various quota types for
+the given period from a start date to an end date.
+
+Quota Monthly Statement
+------------------------
+
+Quota service emails the monthly quota statement for the last month at the beginning of
+each month. For this service to work properly you need to ensure that the usage server
+is running.
+
+Quota Alert Management
+-----------------------
+
+Quota module also provides APIs to customize various email templates that are used to
+alert account owners about quota going down below threshold and quota getting over.
+
+
+All the above functionality is also available via quota UI plugin.
diff --git a/source/plugins/vxlan.rst b/source/plugins/vxlan.rst
new file mode 100644
index 0000000..98dd120
--- /dev/null
+++ b/source/plugins/vxlan.rst
@@ -0,0 +1,428 @@
+.. 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 VXLAN Plugin
+================
+
+System Requirements for VXLAN
+-----------------------------
+
+In PRODUCT 4.X.0, this plugin only supports the KVM hypervisor with the
+standard linux bridge.
+
+The following table lists the requirements for the hypervisor.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++----------------+-----------------------------------------------+----------------------------------------------------------------------------------------------------------------+
+| Item | Requirement | Note |
++================+===============================================+================================================================================================================+
+| Hypervisor | KVM | OvsVifDriver is not supported by this plugin in PRODUCT 4.X, use BridgeVifDriver (default). |
++----------------+-----------------------------------------------+----------------------------------------------------------------------------------------------------------------+
+| Linux kernel | version >= 3.7, VXLAN kernel module enabled | It is recommended to use kernel >=3.9, since Linux kernel categorizes the VXLAN driver as experimental <3.9. |
++----------------+-----------------------------------------------+----------------------------------------------------------------------------------------------------------------+
+| iproute2 | matches kernel version | |
++----------------+-----------------------------------------------+----------------------------------------------------------------------------------------------------------------+
+
+Table: Hypervisor Requirement for VXLAN
+
+
+Linux Distributions that meet the requirements
+----------------------------------------------
+
+The following table lists distributions which meet requirements.
+
+.. cssclass:: table-striped table-bordered table-hover
+
++----------------+-------------------+-------------------------------------------+----------------------------------------------------------------+
+| Distribution | Release Version | Kernel Version (Date confirmed) | Note |
++================+===================+===========================================+================================================================+
+| Ubuntu | 13.04 | 3.8.0 (2013/07/23) | |
++----------------+-------------------+-------------------------------------------+----------------------------------------------------------------+
+| Fedora | >= 17 | 3.9.10 (2013/07/23) | Latest kernel packages are available in "update" repository. |
++----------------+-------------------+-------------------------------------------+----------------------------------------------------------------+
+| CentOS | >= 6.5 | 2.6.32-431.3.1.el6.x86\_64 (2014/01/21) | |
++----------------+-------------------+-------------------------------------------+----------------------------------------------------------------+
+
+Table: List of Linux distributions which meet the hypervisor
+requirements
+
+
+Check the capability of your system
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To check the capability of your system, execute the following commands.
+
+::
+
+ $ sudo modprobe vxlan && echo $?
+ # Confirm the output is "0".
+ # If it's non-0 value or error message, your kernel doesn't have VXLAN kernel module.
+
+ $ ip link add type vxlan help
+ # Confirm the output is usage of the command and that it's for VXLAN.
+ # If it's not, your iproute2 utility doesn't support VXLAN.
+
+
+Important note on MTU size
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When new vxlan interfaces are created, kernel will obtain current MTU size of the physical interface (ethX or the bridge)
+and then create vxlan interface/bridge that are exactly 50 bytes smaller than the MTU on physical interface/bridge.
+This means that in order to support default MTU size of 1500 bytes inside VM, your vxlan interface/bridge must also
+have MTU of 1500 bytes, meaning that your physical interface/bridge must have MTU of at least 1550 bytes.
+In order to configure "jumbo frames" you can i.e. make physical interface/bridge with 9000 bytes MTU, then all the vxlan
+interfaces will be created with MTU of 8950 bytes, and then MTU size inside VM can be set to 8950 bytes.
+
+Important note on max number of multicast groups (and thus VXLAN interfaces)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Default value of "net.ipv4.igmp_max_memberships" (cat /proc/sys/net/ipv4/igmp_max_memberships) is "20", which means that host can be joined to max 20 multicast groups (attach max 20 multicast IPs on the host).
+Since all VXLAN (VTEP) interfaces provisioned on host are multicast-based (belong to certain multicast group, and thus has it's own multicast IP that is used as VTEP), this means that you can not provision more than 20 (working) VXLAN interfaces per host.
+On Linux kernel 3.x you actually can provision more than 20, but ARP request will silently fail and cause client's networking problems
+On Linux kernel 4.x you can NOT provision (start) more than 20 VXLAN interfaces and error message "No buffer space available" can be observed in Cloudstack Agent logs after provisioning required bridges and VXLAN interfaces.
+Increase needed parameter to sane value (i.e. 100 or 200) as required.
+If you need to operate more than 20 VMs from different client's network, this change above is required.
+
+Advanced: Build kernel and iproute2
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Even if your system doesn't support VXLAN, you can compile the kernel
+and iproute2 by yourself. The following procedure is an example for
+CentOS 6.4.
+
+
+Build kernel
+^^^^^^^^^^^^
+
+::
+
+ $ sudo yum groupinstall "Development Tools"
+ $ sudo yum install ncurses-devel hmaccalc zlib-devel binutils-devel elfutils-libelf-devel bc
+
+ $ KERNEL_VERSION=3.10.4
+ # Declare the kernel version you want to build.
+
+ $ wget https://www.kernel.org/pub/linux/kernel/v3.x/linux-${KERNEL_VERSION}.tar.xz
+ $ tar xvf linux-${KERNEL_VERSION}.tar.xz
+ $ cd linux-${KERNEL_VERSION}
+ $ cp /boot/config-`uname -r` .config
+ $ make oldconfig
+ # You may keep hitting enter and choose the default.
+
+ $ make menuconfig
+ # Dig into "Device Drivers" -> "Network device support",
+ # then select "Virtual eXtensible Local Area Network (VXLAN)" and hit space.
+ # Make sure it indicates "<M>" (build as module), then Save and Exit.
+
+ # You may also want to check "IPv4 NAT" and its child nodes in "IP: Netfilter Configuration"
+ # and "IPv6 NAT" and its child nodes in "IPv6: Netfilter Configuration".
+ # In 3.10.4, you can find the options in
+ # "Networking support" -> "Networking options"
+ # -> "Network packet filtering framework (Netfilter)".
+
+ $ make # -j N
+ # You may use -j N option to make the build process parallel and faster,
+ # generally N = 1 + (cores your machine have).
+
+ $ sudo make modules_install
+ $ sudo make install
+ # You would get an error like "ERROR: modinfo: could not find module XXXX" here.
+ # This happens mainly due to config structure changes between kernel versions.
+ # You can ignore this error, until you find you need the kernel module.
+ # If you feel uneasy, you can go back to make menuconfig,
+ # find module XXXX by using '/' key, enable the module, build and install the kernel again.
+
+ $ sudo vi /etc/grub.conf
+ # Make sure the new kernel isn't set as the default and the timeout is long enough,
+ # so you can select the new kernel during boot process.
+ # It's not a good idea to set the new kernel as the default until you confirm the kernel works fine.
+
+ $ sudo reboot
+ # Select the new kernel during the boot process.
+
+
+Build iproute2
+^^^^^^^^^^^^^^
+
+::
+
+ $ sudo yum install db4-devel
+
+ $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git
+ $ cd iproute2
+ $ git tag
+ # Find the version that matches the kernel.
+ # If you built kernel 3.10.4 as above, it would be v3.10.0.
+
+ $ git checkout v3.10.0
+ $ ./configure
+ $ make # -j N
+ $ sudo make install
+
+
+.. note:: Please use rebuild kernel and tools at your own risk.
+
+
+Configure PRODUCT to use VXLAN Plugin
+-------------------------------------
+
+Configure hypervisor
+~~~~~~~~~~~~~~~~~~~~
+
+Configure hypervisor: KVM
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+In addition to "KVM Hypervisor Host Installation" in "PRODUCT
+Installation Guide", you have to configure the following item on the
+host.
+
+
+Create bridge interface with IPv4 address
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+This plugin requires an IPv4 address on the KVM host to terminate and
+originate VXLAN traffic. The address should be assinged to a physical
+interface or a bridge interface bound to a physical interface. Both a
+private address or a public address are fine for the purpose. It is not
+required to be in the same subnet for all hypervisors in a zone, but
+they should be able to reach each other via IP multicast with UDP/8472
+port. A name of a physical interface or a name of a bridge interface
+bound to a physical interface can be used as a traffic label. Physical
+interface name fits for almost all cases, but if physical interface name
+differs per host, you may use a bridge to set a same name. If you would
+like to use a bridge name as a traffic label, you may create a bridge in
+this way.
+
+Let ``cloudbr1`` be the bridge interface for the instances' private
+network.
+
+
+Configure in RHEL or CentOS
+'''''''''''''''''''''''''''
+
+When you configured the ``cloudbr1`` interface as below,
+
+::
+
+ $ sudo vi /etc/sysconfig/network-scripts/ifcfg-cloudbr1
+
+::
+
+ DEVICE=cloudbr1
+ TYPE=Bridge
+ ONBOOT=yes
+ BOOTPROTO=none
+ IPV6INIT=no
+ IPV6_AUTOCONF=no
+ DELAY=5
+ STP=yes
+
+you would change the configuration similar to below.
+
+::
+
+ DEVICE=cloudbr1
+ TYPE=Bridge
+ ONBOOT=yes
+ BOOTPROTO=static
+ IPADDR=192.0.2.X
+ NETMASK=255.255.255.0
+ IPV6INIT=no
+ IPV6_AUTOCONF=no
+ DELAY=5
+ STP=yes
+
+
+Configure in Ubuntu
+'''''''''''''''''''
+
+When you configured ``cloudbr1`` as below,
+
+::
+
+ $ sudo vi /etc/network/interfaces
+
+::
+
+ auto lo
+ iface lo inet loopback
+
+ # The primary network interface
+ auto eth0.100
+ iface eth0.100 inet static
+ address 192.168.42.11
+ netmask 255.255.255.240
+ gateway 192.168.42.1
+ dns-nameservers 8.8.8.8 8.8.4.4
+ dns-domain lab.example.org
+
+ # Public network
+ auto cloudbr0
+ iface cloudbr0 inet manual
+ bridge_ports eth0.200
+ bridge_fd 5
+ bridge_stp off
+ bridge_maxwait 1
+
+ # Private network
+ auto cloudbr1
+ iface cloudbr1 inet manual
+ bridge_ports eth0.300
+ bridge_fd 5
+ bridge_stp off
+ bridge_maxwait 1
+
+you would change the configuration similar to below.
+
+::
+
+ auto lo
+ iface lo inet loopback
+
+ # The primary network interface
+ auto eth0.100
+ iface eth0.100 inet static
+ address 192.168.42.11
+ netmask 255.255.255.240
+ gateway 192.168.42.1
+ dns-nameservers 8.8.8.8 8.8.4.4
+ dns-domain lab.example.org
+
+ # Public network
+ auto cloudbr0
+ iface cloudbr0 inet manual
+ bridge_ports eth0.200
+ bridge_fd 5
+ bridge_stp off
+ bridge_maxwait 1
+
+ # Private network
+ auto cloudbr1
+ iface cloudbr1 inet static
+ addres 192.0.2.X
+ netmask 255.255.255.0
+ bridge_ports eth0.300
+ bridge_fd 5
+ bridge_stp off
+ bridge_maxwait 1
+
+
+Configure iptables to pass XVLAN packets
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Since VXLAN uses UDP packet to forward encapsulated the L2 frames,
+UDP/8472 port must be opened.
+
+
+Configure in RHEL or CentOS
+'''''''''''''''''''''''''''
+
+RHEL and CentOS use iptables for firewalling the system, you can open
+extra ports by executing the following iptable commands:
+
+::
+
+ $ sudo iptables -I INPUT -p udp -m udp --dport 8472 -j ACCEPT
+
+
+These iptable settings are not persistent accross reboots, we have to
+save them first.
+
+::
+
+ $ sudo iptables-save > /etc/sysconfig/iptables
+
+
+With this configuration you should be able to restart the network,
+although a reboot is recommended to see if everything works properly.
+
+::
+
+ $ sudo service network restart
+ $ sudo reboot
+
+
+.. warning::
+ Make sure you have an alternative way like IPMI or ILO to reach the machine
+ in case you made a configuration error and the network stops functioning!
+
+
+Configure in Ubuntu
+'''''''''''''''''''
+
+The default firewall under Ubuntu is UFW (Uncomplicated FireWall), which
+is a Python wrapper around iptables.
+
+To open the required ports, execute the following commands:
+
+::
+
+ $ sudo ufw allow proto udp from any to any port 8472
+
+.. note::
+ By default UFW is not enabled on Ubuntu. Executing these commands with the
+ firewall disabled does not enable the firewall.
+
+With this configuration you should be able to restart the network,
+although a reboot is recommended to see if everything works properly.
+
+::
+
+ $ sudo service networking restart
+ $ sudo reboot
+
+.. warning::
+ Make sure you have an alternative way like IPMI or ILO to reach the machine
+ in case you made a configuration error and the network stops functioning!
+
+
+Setup zone using VXLAN
+~~~~~~~~~~~~~~~~~~~~~~
+
+In almost all parts of zone setup, you can just follow the advanced zone
+setup istruction in "PRODUCT Installation Guide" to use this plugin. It
+is not required to add a network element nor to reconfigure the network
+offering. The only thing you have to do is configure the physical
+network to use VXLAN as the isolation method for Guest Network.
+
+
+Configure the physical network
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. figure:: /_static/images/vxlan-physicalnetwork.png
+
+CloudStack needs to have one physical network for Guest Traffic with the
+isolation method set to "VXLAN".
+
+.. figure:: /_static/images/vxlan-trafficlabel.png
+
+Guest Network traffic label should be the name of the physical interface
+or the name of the bridge interface and the bridge interface and they
+should have an IPv4 address. See ? for details.
+
+
+Configure the guest traffic
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. figure:: /_static/images/vxlan-vniconfig.png
+
+Specify a range of VNIs you would like to use for carrying guest network
+traffic.
+
+.. warning::
+ VNI must be unique per zone and no duplicate VNIs can exist in the zone.
+ Exercise care when designing your VNI allocation policy.
diff --git a/source/quickinstallationguide/qig.rst b/source/quickinstallationguide/qig.rst
new file mode 100644
index 0000000..a45962b
--- /dev/null
+++ b/source/quickinstallationguide/qig.rst
@@ -0,0 +1,695 @@
+.. 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.
+
+
+Quick Installation Guide
+========================
+
+Overview
+--------
+
+What exactly are we building?
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Infrastructure-as-a-Service (IaaS) clouds can be a complex thing to build, and
+by definition they have a plethora of options, which often lead to confusion
+for even experienced admins who are newcomers to building cloud platforms. The
+goal for this runbook is to provide a straightforward set of instructions to
+get you up and running with CloudStack with a minimum amount of trouble.
+
+
+High level overview of the process
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+This runbook will focus on building a CloudStack cloud using KVM on CentOS
+6.8 with NFS storage on a flat layer-2 network utilizing layer-3 network
+isolation (aka Security Groups), and doing it all on a single piece of
+hardware.
+
+KVM, or Kernel-based Virtual Machine is a virtualization technology for the
+Linux kernel. KVM supports native virtualization atop processors with hardware
+virtualization extensions.
+
+Security Groups act as distributed firewalls that control access to a group of
+virtual machines.
+
+
+Prerequisites
+~~~~~~~~~~~~~
+
+To complete this runbook you'll need the following items:
+
+#. At least one computer which supports and has enabled hardware virtualization.
+
+#. The `CentOS 6.8 x86_64 minimal install CD
+ <http://mirrors.kernel.org/centos/6/isos/x86_64/>`_
+
+#. A /24 network with the gateway being at xxx.xxx.xxx.1, no DHCP should be on
+ this network and none of the computers running CloudStack will have a
+ dynamic address. Again this is done for the sake of simplicity.
+
+
+Environment
+-----------
+
+Before you begin , you need to prepare the environment before you install
+CloudStack. We will go over the steps to prepare now.
+
+
+Operating System
+~~~~~~~~~~~~~~~~
+
+Using the CentOS 6.8 x86_64 minimal install ISO, you'll need to install CentOS 6
+on your hardware. The defaults will generally be acceptable for this
+installation.
+
+Once this installation is complete, you'll want to connect to your freshly
+installed machine via SSH as the root user. Note that you should not allow
+root logins in a production environment, so be sure to turn off remote logins
+once you have finished the installation and configuration.
+
+
+.. _conf-network:
+
+Configuring the network
+^^^^^^^^^^^^^^^^^^^^^^^
+
+By default the network will not come up on your hardware and you will need to
+configure it to work in your environment. Since we specified that there will
+be no DHCP server in this environment we will be manually configuring your
+network interface. We will assume, for the purposes of this exercise, that
+eth0 is the only network interface that will be connected and used.
+
+Connecting via the console you should login as root. Check the file
+/etc/sysconfig/network-scripts/ifcfg-eth0, it will look like this by default:
+
+::
+
+ DEVICE="eth0"
+ HWADDR="52:54:00:B9:A6:C0"
+ NM_CONTROLLED="yes"
+ ONBOOT="no"
+
+Unfortunately, this configuration will not permit you to connect to the
+network, and is also unsuitable for our purposes with CloudStack. We want to
+configure that file so that it specifies the IP address, netmask, etc., as
+shown in the following example:
+
+.. note::
+ You should not use the Hardware Address (aka the MAC address) from our
+ example for your configuration. It is network interface specific, so you
+ should keep the address already provided in the HWADDR directive.
+
+::
+
+ DEVICE=eth0
+ HWADDR=52:54:00:B9:A6:C0
+ NM_CONTROLLED=no
+ ONBOOT=yes
+ BOOTPROTO=none
+ IPADDR=172.16.10.2
+ NETMASK=255.255.255.0
+ GATEWAY=172.16.10.1
+ DNS1=8.8.8.8
+ DNS2=8.8.4.4
+
+.. note::
+ IP Addressing - Throughout this document we are assuming that you will have
+ a /24 network for your CloudStack implementation. This can be any RFC 1918
+ network. However, we are assuming that you will match the machine address
+ that we are using. Thus we may use 172.16.10.2 and because you might be
+ using the 192.168.55.0/24 network you would use 192.168.55.2
+
+Now that we have the configuration files properly set up, we need to run a few
+commands to start up the network:
+
+.. parsed-literal::
+
+ # chkconfig network on
+
+ # service network start
+
+
+.. _conf-hostname:
+
+Hostname
+^^^^^^^^
+
+CloudStack requires that the hostname be properly set. If you used the default
+options in the installation, then your hostname is currently set to
+localhost.localdomain. To test this we will run:
+
+.. parsed-literal::
+
+ # hostname --fqdn
+
+At this point it will likely return:
+
+.. parsed-literal::
+
+ localhost
+
+To rectify this situation - we'll set the hostname by editing the /etc/hosts
+file so that it follows a similar format to this example:
+
+.. parsed-literal::
+
+ 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
+ ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
+ 172.16.10.2 srvr1.cloud.priv
+
+After you've modified that file, go ahead and restart the network using:
+
+.. parsed-literal::
+
+ # service network restart
+
+Now recheck with the hostname --fqdn command and ensure that it returns a FQDN
+response
+
+
+.. _conf-selinux:
+
+SELinux
+^^^^^^^
+
+At the moment, for CloudStack to work properly SELinux must be set to
+permissive. We want to both configure this for future boots and modify it in
+the current running system.
+
+To configure SELinux to be permissive in the running system we need to run the
+following command:
+
+.. parsed-literal::
+
+ # setenforce 0
+
+To ensure that it remains in that state we need to configure the file
+/etc/selinux/config to reflect the permissive state, as shown in this example:
+
+.. parsed-literal::
+
+ # This file controls the state of SELinux on the system.
+ # SELINUX= can take one of these three values:
+ # enforcing - SELinux security policy is enforced.
+ # permissive - SELinux prints warnings instead of enforcing.
+ # disabled - No SELinux policy is loaded.
+ SELINUX=permissive
+ # SELINUXTYPE= can take one of these two values:
+ # targeted - Targeted processes are protected,
+ # mls - Multi Level Security protection.
+ SELINUXTYPE=targeted
+
+
+.. _conf-ntp:
+
+NTP
+^^^
+
+NTP configuration is a necessity for keeping all of the clocks in your cloud
+servers in sync. However, NTP is not installed by default. So we'll install
+and and configure NTP at this stage. Installation is accomplished as follows:
+
+.. parsed-literal::
+
+ # yum -y install ntp
+
+The actual default configuration is fine for our purposes, so we merely need
+to enable it and set it to start on boot as follows:
+
+.. parsed-literal::
+
+ # chkconfig ntpd on
+ # service ntpd start
+
+
+.. _qigconf-pkg-repo:
+
+Configuring the CloudStack Package Repository
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+We need to configure the machine to use a CloudStack package repository.
+
+.. note::
+ The Apache CloudStack official releases are source code. As such there are
+ no 'official' binaries available. The full installation guide describes how
+ to take the source release and generate RPMs and and yum repository. This
+ guide attempts to keep things as simple as possible, and thus we are using
+ one of the community-provided yum repositories.
+
+To add the CloudStack repository, create /etc/yum.repos.d/cloudstack.repo and
+insert the following information.
+
+::
+
+ [cloudstack]
+ name=cloudstack
+ baseurl=http://download.cloudstack.org/centos/6/|version|/
+ enabled=1
+ gpgcheck=0
+
+
+NFS
+~~~
+
+Our configuration is going to use NFS for both primary and secondary storage.
+We are going to go ahead and setup two NFS shares for those purposes. We'll
+start out by installing nfs-utils.
+
+.. parsed-literal::
+
+ # yum -y install nfs-utils
+
+We now need to configure NFS to serve up two different shares. This is handled
+comparatively easily in the /etc/exports file. You should ensure that it has
+the following content:
+
+.. parsed-literal::
+
+ /export/secondary \*(rw,async,no_root_squash,no_subtree_check)
+ /export/primary \*(rw,async,no_root_squash,no_subtree_check)
+
+You will note that we specified two directories that don't exist (yet) on the
+system. We'll go ahead and create those directories and set permissions
+appropriately on them with the following commands:
+
+.. parsed-literal::
+
+ # mkdir -p /export/primary
+ # mkdir /export/secondary
+
+CentOS 6.x releases use NFSv4 by default. NFSv4 requires that domain setting
+matches on all clients. In our case, the domain is cloud.priv, so ensure that
+the domain setting in /etc/idmapd.conf is uncommented and set as follows:
+Domain = cloud.priv
+
+Now you'll need uncomment the configuration values in the file
+/etc/sysconfig/nfs
+
+.. parsed-literal::
+
+ LOCKD_TCPPORT=32803
+ LOCKD_UDPPORT=32769
+ MOUNTD_PORT=892
+ RQUOTAD_PORT=875
+ STATD_PORT=662
+ STATD_OUTGOING_PORT=2020
+
+Now we need to configure the firewall to permit incoming NFS connections.
+Edit the file /etc/sysconfig/iptables
+
+.. parsed-literal::
+
+ -A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 111 -j ACCEPT
+ -A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 111 -j ACCEPT
+ -A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 2049 -j ACCEPT
+ -A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 32803 -j ACCEPT
+ -A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 32769 -j ACCEPT
+ -A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 892 -j ACCEPT
+ -A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 892 -j ACCEPT
+ -A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 875 -j ACCEPT
+ -A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 875 -j ACCEPT
+ -A INPUT -s 172.16.10.0/24 -m state --state NEW -p tcp --dport 662 -j ACCEPT
+ -A INPUT -s 172.16.10.0/24 -m state --state NEW -p udp --dport 662 -j ACCEPT
+
+Now you can restart the iptables service with the following command:
+
+.. parsed-literal::
+
+ # service iptables restart
+
+We now need to configure the nfs service to start on boot and actually start
+it on the host by executing the following commands:
+
+.. parsed-literal::
+
+ # service rpcbind start
+ # service nfs start
+ # chkconfig rpcbind on
+ # chkconfig nfs on
+
+
+Management Server Installation
+------------------------------
+
+We're going to install the CloudStack management server and surrounding tools.
+
+
+Database Installation and Configuration
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+We'll start with installing MySQL and configuring some options to ensure it
+runs well with CloudStack.
+
+Install by running the following command:
+
+.. parsed-literal::
+
+ # yum -y install mysql-server
+
+With MySQL now installed we need to make a few configuration changes to
+/etc/my.cnf. Specifically we need to add the following options to the [mysqld]
+section:
+
+::
+
+ innodb_rollback_on_timeout=1
+ innodb_lock_wait_timeout=600
+ max_connections=350
+ log-bin=mysql-bin
+ binlog-format = 'ROW'
+
+Now that MySQL is properly configured we can start it and configure it to
+start on boot as follows:
+
+.. parsed-literal::
+
+ # service mysqld start
+ # chkconfig mysqld on
+
+
+MySQL connector Installation
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Install Python MySQL connector using the official MySQL packages repository.
+Create the file ``/etc/yum.repos.d/mysql.repo`` with the following content:
+
+.. parsed-literal::
+
+ [mysql-connectors-community]
+ name=MySQL Community connectors
+ baseurl=http://repo.mysql.com/yum/mysql-connectors-community/el/$releasever/$basearch/
+ enabled=1
+ gpgcheck=1
+
+Import GPG public key from MySQL:
+
+.. parsed-literal::
+
+ rpm --import http://repo.mysql.com/RPM-GPG-KEY-mysql
+
+Install mysql-connector
+
+.. parsed-literal::
+
+ yum install mysql-connector-python
+
+
+Installation
+~~~~~~~~~~~~
+
+We are now going to install the management server. We do that by executing the
+following command:
+
+.. parsed-literal::
+
+ # yum -y install cloudstack-management
+
+With the application itself installed we can now setup the database, we'll do
+that with the following command and options:
+
+.. parsed-literal::
+
+ # cloudstack-setup-databases cloud:password@localhost --deploy-as=root
+
+When this process is finished, you should see a message like "CloudStack has
+successfully initialized the database."
+
+Now that the database has been created, we can take the final step in setting
+up the management server by issuing the following command:
+
+.. parsed-literal::
+
+ # cloudstack-setup-management
+
+If the servlet container is Tomcat7 the argument --tomcat7 must be used.
+
+
+System Template Setup
+~~~~~~~~~~~~~~~~~~~~~
+
+CloudStack uses a number of system VMs to provide functionality for accessing
+the console of virtual machines, providing various networking services, and
+managing various aspects of storage. This step will acquire those system
+images ready for deployment when we bootstrap your cloud.
+
+Now we need to download the system VM template and deploy that to the share we
+just mounted. The management server includes a script to properly manipulate
+the system VMs images.
+
+.. parsed-literal::
+
+ /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt \
+ -m /export/secondary \
+ -u http://download.cloudstack.org/systemvm/4.6/systemvm64template-4.6.0-kvm.qcow2.bz2 \
+ -h kvm -F
+
+
+That concludes our setup of the management server. We still need to configure
+CloudStack, but we will do that after we get our hypervisor set up.
+
+
+KVM Setup and Installation
+--------------------------
+
+KVM is the hypervisor we'll be using - we will recover the initial setup which
+has already been done on the hypervisor host and cover installation of the
+agent software, you can use the same steps to add additional KVM nodes to your
+CloudStack environment.
+
+
+Prerequisites
+~~~~~~~~~~~~~
+
+We explicitly are using the management server as a compute node as well, which
+means that we have already performed many of the prerequisite steps when
+setting up the management server, but we will list them here for clarity.
+Those steps are:
+
+:ref:`conf-network`
+
+:ref:`conf-hostname`
+
+:ref:`conf-selinux`
+
+:ref:`conf-ntp`
+
+:ref:`qigconf-pkg-repo`
+
+You shouldn't need to do that for the management server, of course, but any
+additional hosts will need for you to complete the above steps.
+
+
+Installation
+~~~~~~~~~~~~
+
+Installation of the KVM agent is trivial with just a single command, but
+afterwards we'll need to configure a few things.
+
+.. parsed-literal::
+
+ # yum -y install cloudstack-agent
+
+
+KVM Configuration
+~~~~~~~~~~~~~~~~~~~~
+
+We have two different parts of KVM to configure, libvirt, and QEMU.
+
+
+QEMU Configuration
+^^^^^^^^^^^^^^^^^^^
+
+KVM configuration is relatively simple at only a single item. We need to edit
+the QEMU VNC configuration. This is done by editing /etc/libvirt/qemu.conf and
+ensuring the following line is present and uncommented.
+
+::
+
+ vnc_listen=0.0.0.0
+
+
+Libvirt Configuration
+^^^^^^^^^^^^^^^^^^^^^^^
+
+CloudStack uses libvirt for managing virtual machines. Therefore it is vital
+that libvirt is configured correctly. Libvirt is a dependency of cloud-agent
+and should already be installed.
+
+#. In order to have live migration working libvirt has to listen for unsecured
+ TCP connections. We also need to turn off libvirts attempt to use Multicast
+ DNS advertising. Both of these settings are in /etc/libvirt/libvirtd.conf
+
+ Set the following paramaters:
+
+ ::
+
+ listen_tls = 0
+ listen_tcp = 1
+ tcp_port = "16059"
+ auth_tcp = "none"
+ mdns_adv = 0
+
+#. Turning on "listen_tcp" in libvirtd.conf is not enough, we have to change
+ the parameters as well we also need to modify /etc/sysconfig/libvirtd:
+
+ Uncomment the following line:
+
+ ::
+
+ #LIBVIRTD_ARGS="--listen"
+
+#. Restart libvirt
+
+ .. parsed-literal::
+
+ # service libvirtd restart
+
+
+KVM configuration complete
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+For the sake of completeness you should check if KVM is running OK on your machine:
+ .. parsed-literal::
+
+ # lsmod | grep kvm
+ kvm_intel 55496 0
+ kvm 337772 1 kvm_intel
+
+That concludes our installation and configuration of KVM, and we'll now move
+to using the CloudStack UI for the actual configuration of our cloud.
+
+
+Configuration
+-------------
+
+As we noted before we will be using security groups to provide isolation and
+by default that implies that we'll be using a flat layer-2 network. It also
+means that the simplicity of our setup means that we can use the quick
+installer.
+
+
+UI Access
+~~~~~~~~~
+
+To get access to CloudStack's web interface, merely point your browser to
+http://172.16.10.2:8080/client The default username is 'admin', and the
+default password is 'password'. You should see a splash screen that allows you
+to choose several options for setting up CloudStack. You should choose the
+Continue with Basic Setup option.
+
+You should now see a prompt requiring you to change the password for the admin
+user. Please do so.
+
+
+Setting up a Zone
+~~~~~~~~~~~~~~~~~
+
+A zone is the largest organization entity in CloudStack - and we'll be
+creating one, this should be the screen that you see in front of you now. And
+for us there are 5 pieces of information that we need.
+
+#. Name - we will set this to the ever-descriptive 'Zone1' for our cloud.
+
+#. Public DNS 1 - we will set this to ``8.8.8.8`` for our cloud.
+
+#. Public DNS 2 - we will set this to ``8.8.4.4`` for our cloud.
+
+#. Internal DNS1 - we will also set this to ``8.8.8.8`` for our cloud.
+
+#. Internal DNS2 - we will also set this to ``8.8.4.4`` for our cloud.
+
+.. note::
+ CloudStack distinguishes between internal and public DNS. Internal DNS is
+ assumed to be capable of resolving internal-only hostnames, such as your
+ NFS server’s DNS name. Public DNS is provided to the guest VMs to resolve
+ public IP addresses. You can enter the same DNS server for both types, but
+ if you do so, you must make sure that both internal and public IP addresses
+ can route to the DNS server. In our specific case we will not use any names
+ for resources internally, and we have indeed them set to look to the same
+ external resource so as to not add a namerserver setup to our list of
+ requirements.
+
+
+Pod Configuration
+~~~~~~~~~~~~~~~~~
+
+Now that we've added a Zone, the next step that comes up is a prompt for
+information regading a pod. Which is looking for several items.
+
+#. Name - We'll use ``Pod1`` for our cloud.
+
+#. Gateway - We'll use ``172.16.10.1`` as our gateway
+
+#. Netmask - We'll use ``255.255.255.0``
+
+#. Start/end reserved system IPs - we will use ``172.16.10.10-172.16.10.20``
+
+#. Guest gateway - We'll use ``172.16.10.1``
+
+#. Guest netmask - We'll use ``255.255.255.0``
+
+#. Guest start/end IP - We'll use ``172.16.10.30-172.16.10.200``
+
+
+Cluster
+~~~~~~~
+
+Now that we've added a Zone, we need only add a few more items for configuring
+the cluster.
+
+#. Name - We'll use ``Cluster1``
+
+#. Hypervisor - Choose ``KVM``
+
+You should be prompted to add the first host to your cluster at this point.
+Only a few bits of information are needed.
+
+#. Hostname - we'll use the IP address ``172.16.10.2`` since we didn't set up a
+ DNS server.
+
+#. Username - we'll use ``root``
+
+#. Password - enter the operating system password for the root user
+
+
+Primary Storage
+^^^^^^^^^^^^^^^
+
+With your cluster now setup - you should be prompted for primary storage
+information. Choose NFS as the storage type and then enter the following
+values in the fields:
+
+#. Name - We'll use ``Primary1``
+
+#. Server - We'll be using the IP address ``172.16.10.2``
+
+#. Path - Well define ``/export/primary`` as the path we are using
+
+
+Secondary Storage
+^^^^^^^^^^^^^^^^^
+
+If this is a new zone, you'll be prompted for secondary storage information -
+populate it as follows:
+
+#. NFS server - We'll use the IP address ``172.16.10.2``
+
+#. Path - We'll use ``/export/secondary``
+
+Now, click Launch and your cloud should begin setup - it may take several
+minutes depending on your internet connection speed for setup to finalize.
+
+That's it, you are done with installation of your Apache CloudStack cloud.
+
diff --git a/source/releasenotes/about.rst b/source/releasenotes/about.rst
new file mode 100644
index 0000000..0a9cad5
--- /dev/null
+++ b/source/releasenotes/about.rst
@@ -0,0 +1,84 @@
+.. 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.
+
+
+What's New in |release|
+=======================
+
+What's New in 4.11.1.0
+----------------------
+
+The new |release| version is a |version| maintainance release containing over 140
+fixes and improvements on the 4.11.0.0 release.
+
+These include the speeding up of virtual router deployments and fixes for corner cases
+effecting the new config drive and L2 features and some hypervisor specific fixes to improve compatibility
+with current hypervisor versions including the XCP-ng fork of XenServer.
+
+What's New in 4.11.0.0
+----------------------
+
+Version 4.11.0.0 included more than 400 commits, 220 pull requests that fixes
+more than 250 issues since the last release. Version 4.11.0.0 was a large
+release that was worked on for 8 months.
+
+A LOT changed in this release, so this is not a complete list, but here is a
+quick summary of some of the changes:
+
+* Support for XenServer 7.1, 7.2, 7.3 and 7.4, and support for XCP-ng 7.4.
+* Improved support for VMware 6.5.
+* Host-HA framework and HA-provider for KVM hosts with and NFS as primary storage, and a new background polling task manager.
+* Secure agents communication: new certificate authority framework and a default built-in root CA provider.
+* New network type - L2.
+* CloudStack metrics exporter for Prometheus.
+* Cloudian Hyperstore connector for CloudStack.
+* Annotation feature for CloudStack entities such as hosts.
+* Separation of volume snapshot creation on primary storage and backing operation on secondary storage.
+* Limit admin access from specified CIDRs.
+* Expansion of Management IP Range.
+* Dedication of public IPs to SSVM and CPVM.
+* Support for separate subnet for SSVM and CPVM.
+* Bypass secondary storage template copy/transfer for KVM.
+* Support for multi-disk OVA template for VMware.
+* Storage overprovisioning for local storage.
+* LDAP mapping with domain scope, and mapping of LDAP group to an account.
+* Move user across accounts.
+* Managed storage enhancements.
+* Extend config drive support for user data, metadata, and password (Nuage Networks).
+* Extra DHCP options support (Nuage Networks).
+* Nuage VSP 5.0 support and caching of NuageVsp ID's.
+* Nuage domain template selection per VPC and support for network migration.
+* Support for watchdog timer to KVM Instances.
+* Support for Secondary IPv6 Addresses and Subnets.
+* IPv6 Prefix Delegation support in basic networking.
+* Ability to specific MAC address while deploying VM or adding a NIC to a VM.
+* VMware dvSwitch security policies configuration in network offering
+* Allow more than 7 NICs to be added to a VMware VM.
+* Network rate usage for guest offering for VRs.
+* Usage metrics for VM snapshot on primary storage.
+* Enable Netscaler inline mode.
+* NCC integration in CloudStack.
+* The retirement of the Midonet network plugin.
+* Several UI Improvements.
+* Embedded Jetty and improved CloudStack management server configuration.
+* Improved support for Java 8 for building artifacts/modules, packaging, and in
+ the systemvm template.
+* A faster console proxy startup and service availability.
+* A new Debian 9 based smaller systemvm template that patches systemvm without
+ requiring reboot.
+* Several optimizations and improvements to the virtual router including better
+ support for redundant virtual routers and strongswan provided s2s and remote
+ access vpn.
+
diff --git a/source/releasenotes/api-changes.rst b/source/releasenotes/api-changes.rst
new file mode 100644
index 0000000..b666b39
--- /dev/null
+++ b/source/releasenotes/api-changes.rst
@@ -0,0 +1,1009 @@
+.. 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.
+
+
+API Changes Introduced in |release|
+===================================
+
+For the complete list of API commands and params consult the `CloudStack Apidocs`_.
+
+
+New API Commands
+----------------
+
+.. cssclass:: table-striped table-bordered table-hover
+
++---------------------------------------------+--------------------------------------------------------------------------------+
+| Name | Description |
++=============================================+================================================================================+
+| ``provisionCertificate`` | Issues and propagates client certificate on a connected host/agent using |
+| | configured CA plugin |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listElastistorPool`` | Lists the pools of elastistor |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``deleteServicePackageOffering`` | Delete Service Package |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listAnnotations`` | Lists annotations. |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``enableHAForZone`` | Enables HA for a zone |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``enableHAForCluster`` | Enables HA cluster-wide |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listNuageVspDomainTemplates`` | Lists Nuage VSP domain templates |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listElastistorInterface`` | Lists the network Interfaces of elastistor |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``stopNetScalerVpx`` | Stops a NetScalervm. |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``disableHAForZone`` | Disables HA for a zone |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``revokeCertificate`` | Revokes certificate using configured CA plugin |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updateSiocInfo`` | Update SIOC info |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``cloudianSsoLogin`` | Generates single-sign-on login url for logged-in CloudStack user to access the |
+| | Cloudian Management Console |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``issueCertificate`` | Issues a client certificate using configured or provided CA plugin |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listNetscalerControlCenter`` | list control center |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listCAProviders`` | Lists available certificate authority providers in CloudStack |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``acquirePodIpAddress`` | Allocates IP addresses in respective Pod of a Zone |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``deleteManagementNetworkIpRange`` | Deletes a management network IP range. This action is only allowed when no IPs |
+| | in this range are allocated. |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``addAnnotation`` | add an annotation. |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``deployNetscalerVpx`` | Creates new NS Vpx |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listElastistorVolume`` | Lists the volumes of elastistor |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``cloudianIsEnabled`` | Checks if the Cloudian Connector is enabled |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listNuageVspGlobalDomainTemplate`` | Lists Nuage VSP domain templates |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listHostHAResources`` | Lists host HA resources |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``enableHAForHost`` | Enables HA for a host |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``registerNetscalerServicePackage`` | Registers NCC Service Package |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listHostHAProviders`` | Lists HA providers |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listCaCertificate`` | Lists the CA public certificate(s) as support by the configured/provided CA |
+| | plugin |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``migrateVPC`` | moves a vpc to another physical network |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``configureHAForHost`` | Configures HA for a host |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listRegisteredServicePackages`` | lists registered service packages |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``disableHAForCluster`` | Disables HA cluster-wide |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``linkAccountToLdap`` | link a cloudstack account to a group or OU in ldap |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``associateNuageVspDomainTemplate`` | associate a vpc with a domain template |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``moveUser`` | Moves a user to another account |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``disableHAForHost`` | Disables HA for a host |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``deleteNetscalerControlCenter`` | Delete Netscaler Control Center |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``migrateNetwork`` | moves a network to another physical network |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``uploadTemplateDirectDownloadCertificate`` | Upload a certificate for HTTPS direct template download on KVM hosts |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``registerNetscalerControlCenter`` | Adds a netscaler control center device |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``createManagementNetworkIpRange`` | Creates a Management network IP range. |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``removeAnnotation`` | remove an annotation. |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``releasePodIpAddress`` | Releases a Pod IP back to the Pod |
++---------------------------------------------+--------------------------------------------------------------------------------+
+
+
+Parameters Changed API Commands
+-------------------------------
+
+.. cssclass:: table-striped table-bordered table-hover
+
++---------------------------------------------+--------------------------------------------------------------------------------+
+| Name | Description |
++=============================================+================================================================================+
+| ``createPod`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``forsystemvms`` |
+| | - ``vlanid`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``copyIso`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``childtemplates`` |
+| | - ``directdownload`` |
+| | - ``parenttemplateid`` |
+| | - ``physicalsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listHosts`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``annotation`` |
+| | - ``hostha`` |
+| | - ``lastannotated`` |
+| | - ``username`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updateStoragePool`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``allocatediops`` |
+| | - ``provider`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``rebootSystemVm`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``guestvlan`` |
+| | - ``publicvlan`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listNetworks`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``externalid`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updateResourceLimit`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``resourcetypename`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updateHost`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``annotation`` (optional) |
+| | |
+| | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``annotation`` |
+| | - ``hostha`` |
+| | - ``lastannotated`` |
+| | - ``username`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``uploadVolume`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``clusterid`` |
+| | - ``clustername`` |
+| | - ``physicalsize`` |
+| | - ``podid`` |
+| | - ``podname`` |
+| | - ``utilization`` |
+| | - ``virtualsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``destroySystemVm`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``guestvlan`` |
+| | - ``publicvlan`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``scaleSystemVm`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``guestvlan`` |
+| | - ``publicvlan`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listLdapConfigurations`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``domainid`` (optional) |
+| | |
+| | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``domainid`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listTemplates`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``parenttemplateid`` (optional) |
+| | |
+| | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``childtemplates`` |
+| | - ``directdownload`` |
+| | - ``parenttemplateid`` |
+| | - ``physicalsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``createLoadBalancerRule`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``zonename`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updateNetworkOffering`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``tags`` (optional) |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``stopSystemVm`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``guestvlan`` |
+| | - ``publicvlan`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``createNetworkOffering`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``forvpc`` (optional) |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listVolumesMetrics`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``clusterid`` (optional) |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listSslCerts`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``name`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listPods`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``forsystemvms`` |
+| | - ``vlanid`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listSnapshots`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``virtualsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listConfigurations`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``domainid`` (optional) |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listSystemVms`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``guestvlan`` |
+| | - ``publicvlan`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``detachVolume`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``clusterid`` |
+| | - ``clustername`` |
+| | - ``physicalsize`` |
+| | - ``podid`` |
+| | - ``podname`` |
+| | - ``utilization`` |
+| | - ``virtualsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``changeServiceForSystemVm`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``guestvlan`` |
+| | - ``publicvlan`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``createSnapshot`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``asyncbackup`` (optional) |
+| | |
+| | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``virtualsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listNics`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``extradhcpoption`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``createSnapshotFromVMSnapshot`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``virtualsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listStoragePools`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``allocatediops`` |
+| | - ``provider`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``addNicToVirtualMachine`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``dhcpoptions`` (optional) |
+| | - ``macaddress`` (optional) |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listExternalLoadBalancers`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``annotation`` |
+| | - ``hostha`` |
+| | - ``lastannotated`` |
+| | - ``username`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updateIso`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``childtemplates`` |
+| | - ``directdownload`` |
+| | - ``parenttemplateid`` |
+| | - ``physicalsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``prepareTemplate`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``childtemplates`` |
+| | - ``directdownload`` |
+| | - ``parenttemplateid`` |
+| | - ``physicalsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``copyTemplate`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``childtemplates`` |
+| | - ``directdownload`` |
+| | - ``parenttemplateid`` |
+| | - ``physicalsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listNiciraNvpDeviceNetworks`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``externalid`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``resizeVolume`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``clusterid`` |
+| | - ``clustername`` |
+| | - ``physicalsize`` |
+| | - ``podid`` |
+| | - ``podname`` |
+| | - ``utilization`` |
+| | - ``virtualsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updateTemplate`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``childtemplates`` |
+| | - ``directdownload`` |
+| | - ``parenttemplateid`` |
+| | - ``physicalsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``createVlanIpRange`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``forsystemvms`` (optional) |
+| | |
+| | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``forsystemvms`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listPaloAltoFirewallNetworks`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``externalid`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``deleteLdapConfiguration`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``domainid`` (optional) |
+| | - ``port`` (optional) |
+| | |
+| | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``domainid`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updateVolume`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``clusterid`` |
+| | - ``clustername`` |
+| | - ``physicalsize`` |
+| | - ``podid`` |
+| | - ``podname`` |
+| | - ``utilization`` |
+| | - ``virtualsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updateVirtualMachine`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``dhcpoptionsnetworklist`` (optional) |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listDomains`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``details`` (optional) |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updateNetwork`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``externalid`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``deleteTemplate`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``forced`` (optional) |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``createTemplate`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``childtemplates`` |
+| | - ``directdownload`` |
+| | - ``parenttemplateid`` |
+| | - ``physicalsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updatePortForwardingRule`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``privateendport`` (optional) |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``linkDomainToLdap`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``ldapdomain`` (required) |
+| | |
+| | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``ldapdomain`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listSrxFirewallNetworks`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``externalid`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``prepareHostForMaintenance`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``annotation`` |
+| | - ``hostha`` |
+| | - ``lastannotated`` |
+| | - ``username`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``registerIso`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``directdownload`` (optional) |
+| | |
+| | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``childtemplates`` |
+| | - ``directdownload`` |
+| | - ``parenttemplateid`` |
+| | - ``physicalsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``deployVirtualMachine`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``datadiskofferinglist`` (optional) |
+| | - ``dhcpoptionsnetworklist`` (optional) |
+| | - ``macaddress`` (optional) |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listVlanIpRanges`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``forsystemvms`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``cancelHostMaintenance`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``annotation`` |
+| | - ``hostha`` |
+| | - ``lastannotated`` |
+| | - ``username`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listVolumes`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``clusterid`` (optional) |
+| | |
+| | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``clusterid`` |
+| | - ``clustername`` |
+| | - ``physicalsize`` |
+| | - ``podid`` |
+| | - ``podname`` |
+| | - ``utilization`` |
+| | - ``virtualsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``lockUser`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``usersource`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``createNetwork`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``bypassvlanoverlapcheck`` (optional) |
+| | - ``externalid`` (optional) |
+| | |
+| | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``externalid`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updateUser`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``usersource`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``addHost`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``annotation`` |
+| | - ``hostha`` |
+| | - ``lastannotated`` |
+| | - ``username`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``attachVolume`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``clusterid`` |
+| | - ``clustername`` |
+| | - ``physicalsize`` |
+| | - ``podid`` |
+| | - ``podname`` |
+| | - ``utilization`` |
+| | - ``virtualsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listUsers`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``usersource`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listResourceLimits`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``resourcetypename`` (optional) |
+| | |
+| | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``resourcetypename`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``disableUser`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``usersource`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listIsos`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``childtemplates`` |
+| | - ``directdownload`` |
+| | - ``parenttemplateid`` |
+| | - ``physicalsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listNetscalerLoadBalancerNetworks`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``externalid`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``startSystemVm`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``guestvlan`` |
+| | - ``publicvlan`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``migrateVolume`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``clusterid`` |
+| | - ``clustername`` |
+| | - ``physicalsize`` |
+| | - ``podid`` |
+| | - ``podname`` |
+| | - ``utilization`` |
+| | - ``virtualsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listEvents`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``startid`` (optional) |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``addLdapConfiguration`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``domainid`` (optional) |
+| | |
+| | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``domainid`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updateConfiguration`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``domainid`` (optional) |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``dedicatePublicIpRange`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``forsystemvms`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``revertSnapshot`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``virtualsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``migrateSystemVm`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``guestvlan`` |
+| | - ``publicvlan`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updateResourceCount`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``resourcetypename`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listBrocadeVcsDeviceNetworks`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``externalid`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listUsageRecords`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``includetags`` (optional) |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``enableUser`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``usersource`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``registerTemplate`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``directdownload`` (optional) |
+| | |
+| | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``childtemplates`` |
+| | - ``directdownload`` |
+| | - ``parenttemplateid`` |
+| | - ``physicalsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``createStoragePool`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``allocatediops`` |
+| | - ``provider`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``findStoragePoolsForMigration`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``allocatediops`` |
+| | - ``provider`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``createVolume`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``clusterid`` |
+| | - ``clustername`` |
+| | - ``physicalsize`` |
+| | - ``podid`` |
+| | - ``podname`` |
+| | - ``utilization`` |
+| | - ``virtualsize`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listF5LoadBalancerNetworks`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``externalid`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updatePod`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``forsystemvms`` |
+| | - ``vlanid`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``enableStorageMaintenance`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``allocatediops`` |
+| | - ``provider`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``createUser`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``usersource`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updateRolePermission`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``permission`` (optional) |
+| | - ``ruleid`` (optional) |
+| | |
+| | *Changed Parameters:* |
+| | |
+| | - ``ruleorder`` was 'required' and is now 'optional' |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``cancelStorageMaintenance`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``allocatediops`` |
+| | - ``provider`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``updateLoadBalancerRule`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``protocol`` (optional) |
+| | |
+| | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``zonename`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``reconnectHost`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``annotation`` |
+| | - ``hostha`` |
+| | - ``lastannotated`` |
+| | - ``username`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``getUser`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``usersource`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listLoadBalancerRules`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``zonename`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``uploadSslCert`` | **Request:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``name`` (required) |
+| | |
+| | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``name`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``addBaremetalHost`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``annotation`` |
+| | - ``hostha`` |
+| | - ``lastannotated`` |
+| | - ``username`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+| ``listCapacity`` | **Response:** |
+| | |
+| | *New Parameters:* |
+| | |
+| | - ``capacityallocated`` |
+| | - ``name`` |
+| | |
++---------------------------------------------+--------------------------------------------------------------------------------+
+
diff --git a/source/releasenotes/compat.rst b/source/releasenotes/compat.rst
new file mode 100644
index 0000000..d134391
--- /dev/null
+++ b/source/releasenotes/compat.rst
@@ -0,0 +1,113 @@
+.. 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.
+
+Compatibility Matrix
+====================
+
+Supported OS Versions for Management Server
+-------------------------------------------
+
+This section lists the operating systems that are supported for running
+CloudStack Management Server. Note that specific versions of the
+operating systems are tested, so compatibility with CentOS 6.3 may not
+indicate compatibility with CentOS 6.2, 6.1 and so on.
+
+- RHEL versions 6.3, 6.5, 6.6 and 7.0
+- CentOS versions 6.8, 7
+- Ubuntu 14.04, 16.04, 17.04 LTS
+
+Software Requirements
+~~~~~~~~~~~~~~~~~~~~~
+
+- Java JRE 1.8
+- MySQL 5.6, 5.7 (RHEL 7)
+- MySQL 5.1 (RHEL 6.x)
+
+Supported Hypervisor Versions
+-----------------------------
+
+CloudStack supports three hypervisor families, XenServer with XAPI, KVM,
+and VMware with vSphere.
+
+- CentOS 6.2+, 7.0+ with KVM
+- Ubuntu 14.04LTS, 16.04LTS, 18.04LTS with KVM
+- Red Hat Enterprise Linux 6.2 with KVM
+- XenServer versions 6.1, 6.2 SP1, 6.5, 7.0, 7.1, 7.2 with latest hotfixes, XCP-ng 7.4
+
+ .. note:: It is now required to enable HA on the XenServer pool in order to recover from a pool-master failure. Please refer to the `XenServer documentation <http://docs.vmd.citrix.com/XenServer/6.5.0/1.0/en_gb/>`_.
+
+- VMware versions 5.0 Update 3, 5.1 Update 3, 5.5 Update 3b, 6.0 Update 2, and 6.5 GA
+- LXC Host Containers on RHEL 7
+- Windows Server 2012 R2 (with Hyper-V Role enabled)
+- Hyper-V 2012 R2
+- Oracle VM 3.0+
+- Bare metal hosts are supported, which have no hypervisor. These hosts
+ can run the following operating systems:
+
+ - RHEL or CentOS, v6.2 or 6.3
+
+ .. note:: Use libvirt version 0.9.10 for CentOS 6.3
+
+ - Fedora 17
+ - Ubuntu 12.04
+
+For more information, see the Hypervisor Compatibility Matrix in the
+`CloudStack Installation Guide`_.
+
+
+Supported External Devices
+--------------------------
+
+- Netscaler VPX and MPX versions 9.3, 10.1e and 10.5
+- Netscaler SDX version 9.3, 10.1e and 10.5
+- SRX (Model srx100b) versions 10.3 to 10.4 R7.5
+- F5 11.X
+- Force 10 Switch version S4810 for Baremetal Advanced Networks
+
+
+Supported Browsers
+------------------
+
+The CloudStack Web-based UI should be compatible with any modern
+browser, but it's possible that some browsers will not render portions
+of the UI reliably, depending on their support of Web standards. For
+best results, one of the following browsers recommended:
+
+- Firefox version 31 or later
+
+- Google Chrome version 36.0+
+
+- Safari 6+
+
+Notice Of Management OSes and Hypervisors to be Deprecated
+----------------------------------------------------------
+
+The following hypervisors will no longer be tested from the first release AFTER
+1st June 2018. And will be removed from the CloudStack codebase from the first
+release after 1st November 2018.
+
+- XenServer 6.2
+- XenServer 6.5
+- vSphere 5.0
+- vSphere 5.1
+
+The following hypervisors will no longer be tested from the first release AFTER
+1st February 2019. And will be removed from the CloudStack codebase from the first
+release after 1st July 2019.
+
+- vSphere 5.5
+
+Please see `CloudStack Wiki <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Hypervisor+and+Management+Server+OS+EOL+Dates>`_
+for details.
diff --git a/source/releasenotes/fixed_issues.rst b/source/releasenotes/fixed_issues.rst
new file mode 100644
index 0000000..6ae16b1
--- /dev/null
+++ b/source/releasenotes/fixed_issues.rst
@@ -0,0 +1,1700 @@
+.. 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.
+
+
+
+Issues Fixed in |release|
+=========================
+
+Apache CloudStack uses `Jira <https://issues.apache.org/jira/browse/CLOUDSTACK>`_
+to track its issues and `Github <https://github.com/apache/cloudstack/pulls>`_ for
+pull requests. All new features and bugs for |version| have been merged through
+Github pull requests. A subset of these changes are tracked in Jira, which have a
+standard naming convention of "CLOUDSTACK-NNNN" where "NNNN" is the issue number.
+
+
+Issues Fixed in 4.11.1.0
+------------------------
+
+.. cssclass:: table-striped table-bordered table-hover
+
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| Branches | Github | Jira | Type | Priority | Description |
++=========================+==========+====================+===============+==========+============================================================+
+| 4.11 | `#2712`_ | | | | reuse ip for non redundant VPC |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2714`_ | | | | send unsupported answer only when applicable |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2715`_ | | | | smoketest: Fix test_vm_life_cycle secure migration tests |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2493`_ | CLOUDSTACK-10326_ | Bug | Major | Prevent hosts fall into Maintenance when there are running |
+| | | | | | VMs on it |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2716`_ | | | | configdrive: make fewer mountpoints on hosts |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2681`_ | | | | Source NAT option on Private Gateway |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2670`_ | | | | Removing an old, unused NetApp plug-in |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2710`_ | | | | comply with api key constraint |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2699`_ | | | | remove old config artifacts from update path |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2705`_ | CLOUDSTACK-10381_ | Bug | Blocker | [ConfigDrive] Password is missing after reset password |
+| | | | | | sequence |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2704`_ | | | | ui: fix create VPC dialog box failure when zone is SG |
+| | | | | | enabled |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2693`_ | | | | Fix to enable Advanced zones with Security groups and |
+| | | | | | VXLAN isolation type |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2697`_ | | | | agent: Avoid sudo, renew certificates assuming root |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2686`_ | | | | Fixes #2685: broken SXM support |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2696`_ | | | | Fix LibvirtStorageAdaptor.java |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2683`_ | | | | Add default L2 network offerings |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2694`_ | | | | Do not send conserve mode param on L2 network offering |
+| | | | | | creation from the UI |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2688`_ | CLOUDSTACK-10382_ | Bug | Major | [ConfigDrive] cloud-get-vm-data-configdrive.in is |
+| | | | | | incorrect |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2672`_ | CLOUDSTACK-10377_ | Bug | Major | Nuage VSP regression fails in NetworksWithCleanup test |
+| | | | | | since introduction of fix for CLOUDSTACK-9114 in ACS |
+| | | | | | 4.11&master |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2674`_ | | | | Create unit test cases for 'ConfigDriveBuilder' class |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2673`_ | | | | Fix test_configdrive.py and test_nuage_configdrive |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2676`_ | | | | Fix two typos (from uanble to unable). |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2669`_ | | | | conditional template filter |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2664`_ | | | | revert dedicate vlan code removal |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2663`_ | | | | server: Calculate fresh capacity per VM |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2667`_ | CLOUDSTACK-10375_ | Bug | Minor | Do not create |
+| | | | | | DefaultNuageVspSharedNetworkOfferingWithSGService |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2661`_ | | | | Make uploadSslCert a POST request instead of a GET |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2639`_ | CLOUDSTACK-10276_ | Bug | Major | View volumes from primary storage not working when storage |
+| | | | | | UUID is not a UUID |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2653`_ | | | | Generate MAC address if the MAC in command |
+| | | | | | addNicToVirtualMachine is invalid |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2656`_ | | | | Only perform certain actions here with managed storage if |
+| | | | | | the VM is s? |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2651`_ | CLOUDSTACK-10290_ | Bug | Major | Config drive - only supported for secondary storage |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2473`_ | CLOUDSTACK-10309_ | Improvement | Minor | VMs with HA enabled, power back on if shutdown from guest |
+| | | | | | OS |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2655`_ | | | | Handle Ceph. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2630`_ | | | | Host Affinity plugin |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2652`_ | | | | Fix register iso in all zones |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2629`_ | | | | Fix primary storage count when deleting volumes |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2638`_ | | | | agent: Fixes #2633 don't wait for pending tasks on |
+| | | | | | reconnection |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2645`_ | | | | config-drive: use hostname of VM instance of internal VM |
+| | | | | | id |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2646`_ | | | | Don't skip tests while packaging Centos7 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2635`_ | | | | router: Fixes #2544 run passwd server on dhcpserver IP on |
+| | | | | | rVR |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2634`_ | CLOUDSTACK-9184_ | Bug | Major | [VMware] vmware.ports.per.dvportgroup global setting is |
+| | | | | | not useful from vCenter 5.0 onwards |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2508`_ | CLOUDSTACK-9114_ | Improvement | Major | restartnetwork with cleanup should not update/restart both |
+| | | | | | routers at once |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2584`_ | | | | Enhance and cleanup DatabaseUpgradeChecker |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2600`_ | CLOUDSTACK-10362_ | Improvement | Major | Inconsistent method names |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2627`_ | | | | Catch error in packagin script and fail the build |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2615`_ | | | | config-drive: support user data on L2 networks |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2632`_ | | | | listostypes: Fixes #2529 return boolean than string in |
+| | | | | | response |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2621`_ | | | | Backports for 4.11 branch |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2619`_ | | | | Remove "self-injection" of AccountManagerImpl |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2607`_ | | | | Allow changing disk offering of VMs' root volume during |
+| | | | | | volume migration |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2626`_ | | | | bionic: allow Ubuntu 18.04 to be added as KVM host |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2623`_ | | | | fixes #2611 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2628`_ | | | | Create upgrade path from 4.9.3.1 to 4.11.1.0 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2612`_ | | | | [migrateVolume API method] Filter disk offerings based on |
+| | | | | | target storage pool selected |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1940`_ | CLOUDSTACK-9781_ | Bug | Major | ACS records ID in events tables instead of UUID. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2608`_ | | | | API: move ostypeid from DB id to DB uuid |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.9* | `#2471`_ | CLOUDSTACK-10311_ | Improvement | Major | Agent Log Rotate variable replace bug |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2606`_ | | | | When creating a new account (via domain admin) it is |
+| | | | | | possible to select ?root admin? as the role for the new |
+| | | | | | user |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2601`_ | CLOUDSTACK-10364_ | Improvement | Major | Inconsiste "setXXX" method names. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2599`_ | CLOUDSTACK-10363_ | Improvement | Major | Inconsistent "getXXX" and "listXXX" method names. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2598`_ | CLOUDSTACK-10360_ | Improvement | Major | Inconsistent method name |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2605`_ | | | | xenserver: Add support for XS 7.3, 7.4 and XCP-ng 7.4 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2428`_ | CLOUDSTACK-10253_ | Bug | Minor | JSON response returns boolean as string |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2536`_ | | | | fix typo c&p bug in externalId feature UI |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2486`_ | CLOUDSTACK-10323_ | Improvement | Major | Change disk offering when volume is migrated to different |
+| | | | | | type of storage pool. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2422`_ | CLOUDSTACK-10254_ | Improvement | Major | Require checkstyle to verify package names against |
+| | | | | | directory structure |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2566`_ | CLOUDSTACK-10288_ | Bug | Major | Config drive - Usedata corruption when gzipped |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2573`_ | CLOUDSTACK-10356_ | Bug | Major | Fix Some Potential NPE |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2412`_ | CLOUDSTACK-9677_ | Improvement | Major | Swift Storage Policy support for Secondary Storage |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2594`_ | | | | Remove 'NetworkManagerTestComponentLibrary' empty class |
+| | | | | | and related configurations |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2597`_ | | | | UpdateUserCmd: apiSecretKey refers to itself |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2498`_ | CLOUDSTACK-10327_ | Bug | Critical | SSO fails with error "Session Expired", except for root |
+| | | | | | admin |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2591`_ | CLOUDSTACK-10359_ | Improvement | Major | Inconsistent method names |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2590`_ | | | | network: Fix security groups for CentOS |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2582`_ | | | | cs-45to411-ugrade-fix: database errors during upgrade to |
+| | | | | | 4.11 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2577`_ | | | | Prevent NPE if guest OS mapping is missing while |
+| | | | | | prioritizing hosts |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2579`_ | | | | router: fix routing table for marked packets |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2589`_ | | | | Remove packaging job from pull request template |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2588`_ | | | | capacity: remove unused threadpool |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2505`_ | CLOUDSTACK-10333_ | Improvement | Major | Secure VM Live migration for KVM |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2580`_ | CLOUDSTACK-10357_ | Improvement | Minor | Log messages that do not match with their method function |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2587`_ | | | | Remove empty VPN test class |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2586`_ | | | | Use double quotes with 'RROUTER' variable in "common.sh" |
+| | | | | | script |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2576`_ | | | | Fix Python code checkstyle execute by |
+| | | | | | "systemvm\test\runtests.sh" |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2562`_ | | | | consoleproxy: use consoleproxy.domain for non-ssl enable |
+| | | | | | env |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2554`_ | | | | agent: Add logging to libvirt qemu hook and cleanup |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2511`_ | CLOUDSTACK-10344_ | Bug | Major | Sometimes a bug happens when moving ACL rules (changing |
+| | | | | | their order with drag and drop) |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2572`_ | | | | Remove 'todb' in favor of 'encodeURIComponent'. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2553`_ | | | | Update inconsistent debugging info in catch block |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2499`_ | | | | Updates to capacity management |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2570`_ | | | | Improve README |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2568`_ | | | | Log command output in CsHelper.execute command |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2559`_ | | | | Upgrade path 4.11 through 4.11.1 to 4.12 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2567`_ | | | | [Vmware] Fix for OVF parsing error |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2563`_ | CLOUDSTACK-10304_ | Bug | Major | SystemVM - Apache Web Server Version Number Information |
+| | | | | | Disclosure |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2555`_ | | | | Remove 'md5Hashed' variable from Javascript. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2390`_ | CLOUDSTACK-10214_ | Bug | Major | Unable to remove local primary storage |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2564`_ | | | | [Docs] Fix URL error from installation instructions |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2557`_ | | | | Add "Fixes: number" to PR template for auto-closing issues |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2404`_ | CLOUDSTACK-10230_ | Bug | Critical | User is able to change to ?Guest OS type? that has been |
+| | | | | | removed |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2550`_ | | | | debian: Use only `-l` for libvirtd default file on debian |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2560`_ | | | | ui: Make zonal dashboard larger |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2401`_ | CLOUDSTACK-10226_ | Bug | Major | CloudStack is not importing Local storage properly |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2462`_ | CLOUDSTACK-10301_ | Bug | Major | Allow updating the network ACL list name and Description |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2490`_ | | | | Create database upgrade from 4.11.0.0 to 4.11.1.0 & VMWare |
+| | | | | | version to OS mappings |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2538`_ | | | | Remove deprecated tomcat configuration file instead of |
+| | | | | | moving it |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2517`_ | | | | manual mapped ldap fix |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2552`_ | | | | debian: remove old usage jars during upgrade |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2535`_ | | | | Create an easy way to enable Java remote Debug for ACS |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2526`_ | | | | add issue template for github issues |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2522`_ | | | | indicate scope of tests in checklist |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2519`_ | CLOUDSTACK-10287_ | Bug | Major | Make el7 rpms to depend on OpenJDK8 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2520`_ | | | | make Broadcast- and IsolationURI visible to admin |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2515`_ | | | | Fix Successfully typo |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2414`_ | CLOUDSTACK-10241_ | Bug | Major | Duplicated file SRs being created in XenServer pools |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2512`_ | | | | Only use the host if its Resource State is Enabled. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2492`_ | | | | Fix the name of the column used to hold IPv4 range in |
+| | | | | | 'vlan' table. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2496`_ | CLOUDSTACK-10332_ | Enhancement | Major | Users are not able to change/edit the protocol of an ACL |
+| | | | | | rule |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2449`_ | CLOUDSTACK-10278_ | Bug | Major | Adding a SQL table column is not Idempotent |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2510`_ | CLOUDSTACK-10334_ | Improvement | Major | Inadequate information for handling catch clauses |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2506`_ | CLOUDSTACK-10341_ | Task | Major | Systemvmtemplate 4.11 changes |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2513`_ | CLOUDSTACK-10227_ | Bug | Blocker | Stabilization fixes for master/4.11 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2465`_ | CLOUDSTACK-10232_ | Enhancement | Major | SystemVMs and VR to run as HVM on XenServer |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2438`_ | CLOUDSTACK-10307_ | Improvement | Minor | Remove unused things from HostDaoImpl |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2507`_ | CLOUDSTACK-10319_ | Bug | Major | Prefer TLSv1.2 and deprecate TLS 1.0/1.1 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2397`_ | CLOUDSTACK-10221_ | Improvement | Major | Allow specification of IPv6 details when creating Basic |
+| | | | | | Network |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2481`_ | CLOUDSTACK-10320_ | Bug | Major | Invalid pair for response object breaking response parsing |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2468`_ | CLOUDSTACK-10341_ | Task | Major | Systemvmtemplate 4.11 changes |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2504`_ | CLOUDSTACK-10340_ | Task | Major | Add setter in vminstancevo |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2497`_ | CLOUDSTACK-10331_ | Bug | Minor | Error 404 for /client/scripts/vm_snapshots.js |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2408`_ | CLOUDSTACK-10231_ | Bug | Major | Asserted fixes for Direct Download on KVM |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2494`_ | CLOUDSTACK-10329_ | Enhancement | Major | Button in ACL rules page to export all rules as a CSV file |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2495`_ | | | | Fix typo in Packaging script |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2489`_ | CLOUDSTACK-10330_ | Improvement | Major | Introduce a standard PULL REQUEST template |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2491`_ | | | | Fix "agent-lb" project |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2469`_ | CLOUDSTACK-10132_ | Improvement | Major | Extend Multiple Management Servers Support for agents to |
+| | | | | | allow sorting algorithms |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2458`_ | CLOUDSTACK-10296_ | Bug | Major | Fix timestamp difference in heartbeat script for rVRs |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2433`_ | CLOUDSTACK-10268_ | Improvement | Minor | Fix and enhance package script |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2387`_ | CLOUDSTACK-8855_ | Bug | Major | Improve Error Message for Host Alert State |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2482`_ | CLOUDSTACK-10321_ | Bug | Major | CPU Cap for KVM |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2483`_ | CLOUDSTACK-10303_ | Improvement | Major | refactor plugins/nuagevsp tests to run from its own |
+| | | | | | test_data.py file |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2442`_ | CLOUDSTACK-10147_ | Bug | Major | Disabled Xenserver cluster can still deploy VMs |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2484`_ | | | | createNetworkACL: number has the wrong doc |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2475`_ | CLOUDSTACK-10314_ | Improvement | Minor | Add Text-Field to each ACL Rule |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2485`_ | | | | Bump the version of Debian net-installer to 9.4.0 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2480`_ | CLOUDSTACK-10319_ | Bug | Major | Prefer TLSv1.2 and deprecate TLS 1.0/1.1 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2470`_ | CLOUDSTACK-10197_ | Bug | Major | XenServer 7.1: Cannot mount xentool iso from cloudstack |
+| | | | | | on VMs |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2476`_ | CLOUDSTACK-10317_ | Bug | Minor | In case of multiple-public ips, snat fails to work for |
+| | | | | | addtional public nics/network for guest traffic |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2425`_ | CLOUDSTACK-10240_ | Improvement | Major | ACS cannot migrate a volume from local to shared storage |
+| | | | | | (for XenServer) |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2448`_ | CLOUDSTACK-10274_ | Bug | Major | L2 network refused to be designed on VXLAN physical |
+| | | | | | network |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2478`_ | CLOUDSTACK-10318_ | Bug | Major | Bug on sorting ACL rules list in chrome |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2437`_ | CLOUDSTACK-10257_ | Improvement | Minor | Create template/volume does not allow to specify HVM |
+| | | | | | requirement |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2439`_ | CLOUDSTACK-10259_ | Bug | Minor | Missing float part of secondary storage data when |
+| | | | | | calculating secondary storage usage in listAccounts |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2392`_ | | | | dateutil: constistency of tzdate input and output |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2463`_ | CLOUDSTACK-10302_ | Task | Major | Create database path upgrade from 4.11.0.0 to 4.12.0.0 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2464`_ | CLOUDSTACK-10299_ | Bug | Minor | Network listing return error in project mode |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2244`_ | CLOUDSTACK-10054_ | Bug | Major | Volume download times out in 3600 seconds |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2467`_ | CLOUDSTACK-10306_ | Bug | Minor | Update vmware dependency vim jar to 6.5 version |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2460`_ | CLOUDSTACK-10298_ | Bug | Major | Recreation of an earlier deleted Nuage managed isolated or |
+| | | | | | vpc tier network fails |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2466`_ | CLOUDSTACK-10305_ | Bug | Major | Rare race condition in KVM migration |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2443`_ | CLOUDSTACK-9338_ | Bug | Major | updateResourceCount not accounting resources of VMs with |
+| | | | | | custom service offering |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2451`_ | CLOUDSTACK-10284_ | Bug | Major | Creating a snapshot from VM Snapshot generates error if |
+| | | | | | hypervisor is not KVM. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2454`_ | CLOUDSTACK-10283_ | Bug | Major | Use sudo to execute keystore setup/import for kvm agents, |
+| | | | | | and fail on keystore setup failures |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2457`_ | CLOUDSTACK-10295_ | Improvement | Major | Marvin: add support for password-enabled templates |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2456`_ | CLOUDSTACK-10293_ | Bug | Major | Single view network ACL rules listing |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2402`_ | CLOUDSTACK-10128_ | Bug | Critical | Template from snapshot not merging vhd files |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2432`_ | CLOUDSTACK-10294_ | Improvement | Major | Updated code-styling and improvements to security_group.py |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2450`_ | CLOUDSTACK-10282_ | Bug | Major | SystemVM - filrewall rules incorrect |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2452`_ | CLOUDSTACK-10285_ | Bug | Critical | 4.10.0.0 users face upgrade issues when upgrading to |
+| | | | | | 4.11.0.0 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2441`_ | CLOUDSTACK-10261_ | Bug | Critical | Nuage: Multinic: Libvirt nuage-extenstion metadata |
+| | | | | | contains only one interface. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2420`_ | CLOUDSTACK-10247_ | Bug | Major | L2 network not shared on projects |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2424`_ | CLOUDSTACK-10251_ | Bug | Major | HTTPS downloader for Direct Download templates failure |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2421`_ | CLOUDSTACK-10243_ | Bug | Major | Updating metadata might hang on VR on "ip rule show" |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2406`_ | CLOUDSTACK-9663_ | Improvement | Trivial | updateRole should return updated role as json |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2445`_ | CLOUDSTACK-10218_ | Bug | Major | forced network update to a nuage network offering with vr |
+| | | | | | fails with IllegalArgumentException |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2444`_ | CLOUDSTACK-10269_ | Bug | Major | Allow deletion of roles without causing concurrent |
+| | | | | | exception |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2405`_ | CLOUDSTACK-10146_ | Bug | Major | Bypass Secondary Storage for KVM templates |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2398`_ | CLOUDSTACK-10222_ | Bug | Major | Clean previous snaphosts from primary storage when taking |
+| | | | | | new one |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2431`_ | CLOUDSTACK-10225_ | Improvement | Major | Deprecate com.cloud.utils.StringUtils |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+
+.. _`#2712`: https://github.com/apache/cloudstack/pull/2712
+.. _`#2714`: https://github.com/apache/cloudstack/pull/2714
+.. _`#2715`: https://github.com/apache/cloudstack/pull/2715
+.. _`#2493`: https://github.com/apache/cloudstack/pull/2493
+.. _CLOUDSTACK-10326: https://issues.apache.org/jira/browse/CLOUDSTACK-10326
+.. _`#2716`: https://github.com/apache/cloudstack/pull/2716
+.. _`#2681`: https://github.com/apache/cloudstack/pull/2681
+.. _`#2670`: https://github.com/apache/cloudstack/pull/2670
+.. _`#2710`: https://github.com/apache/cloudstack/pull/2710
+.. _`#2706`: https://github.com/apache/cloudstack/pull/2706
+.. _`#2699`: https://github.com/apache/cloudstack/pull/2699
+.. _`#2705`: https://github.com/apache/cloudstack/pull/2705
+.. _CLOUDSTACK-10381: https://issues.apache.org/jira/browse/CLOUDSTACK-10381
+.. _`#2704`: https://github.com/apache/cloudstack/pull/2704
+.. _`#2693`: https://github.com/apache/cloudstack/pull/2693
+.. _`#2697`: https://github.com/apache/cloudstack/pull/2697
+.. _`#2686`: https://github.com/apache/cloudstack/pull/2686
+.. _`#2696`: https://github.com/apache/cloudstack/pull/2696
+.. _`#2683`: https://github.com/apache/cloudstack/pull/2683
+.. _`#2694`: https://github.com/apache/cloudstack/pull/2694
+.. _`#2688`: https://github.com/apache/cloudstack/pull/2688
+.. _CLOUDSTACK-10382: https://issues.apache.org/jira/browse/CLOUDSTACK-10382
+.. _`#2672`: https://github.com/apache/cloudstack/pull/2672
+.. _CLOUDSTACK-10377: https://issues.apache.org/jira/browse/CLOUDSTACK-10377
+.. _`#2674`: https://github.com/apache/cloudstack/pull/2674
+.. _`#2673`: https://github.com/apache/cloudstack/pull/2673
+.. _`#2676`: https://github.com/apache/cloudstack/pull/2676
+.. _`#2669`: https://github.com/apache/cloudstack/pull/2669
+.. _`#2669`: https://github.com/apache/cloudstack/pull/2669
+.. _`#2664`: https://github.com/apache/cloudstack/pull/2664
+.. _`#2663`: https://github.com/apache/cloudstack/pull/2663
+.. _`#2667`: https://github.com/apache/cloudstack/pull/2667
+.. _CLOUDSTACK-10375: https://issues.apache.org/jira/browse/CLOUDSTACK-10375
+.. _`#2661`: https://github.com/apache/cloudstack/pull/2661
+.. _`#2639`: https://github.com/apache/cloudstack/pull/2639
+.. _CLOUDSTACK-10276: https://issues.apache.org/jira/browse/CLOUDSTACK-10276
+.. _`#2653`: https://github.com/apache/cloudstack/pull/2653
+.. _`#2656`: https://github.com/apache/cloudstack/pull/2656
+.. _`#2651`: https://github.com/apache/cloudstack/pull/2651
+.. _CLOUDSTACK-10290: https://issues.apache.org/jira/browse/CLOUDSTACK-10290
+.. _`#2651`: https://github.com/apache/cloudstack/pull/2651
+.. _CLOUDSTACK-10290: https://issues.apache.org/jira/browse/CLOUDSTACK-10290
+.. _`#2473`: https://github.com/apache/cloudstack/pull/2473
+.. _CLOUDSTACK-10309: https://issues.apache.org/jira/browse/CLOUDSTACK-10309
+.. _`#2473`: https://github.com/apache/cloudstack/pull/2473
+.. _CLOUDSTACK-10309: https://issues.apache.org/jira/browse/CLOUDSTACK-10309
+.. _`#2655`: https://github.com/apache/cloudstack/pull/2655
+.. _`#2630`: https://github.com/apache/cloudstack/pull/2630
+.. _`#2652`: https://github.com/apache/cloudstack/pull/2652
+.. _`#2629`: https://github.com/apache/cloudstack/pull/2629
+.. _`#2638`: https://github.com/apache/cloudstack/pull/2638
+.. _`#2638`: https://github.com/apache/cloudstack/pull/2638
+.. _`#2645`: https://github.com/apache/cloudstack/pull/2645
+.. _`#2645`: https://github.com/apache/cloudstack/pull/2645
+.. _`#2646`: https://github.com/apache/cloudstack/pull/2646
+.. _`#2635`: https://github.com/apache/cloudstack/pull/2635
+.. _`#2635`: https://github.com/apache/cloudstack/pull/2635
+.. _`#2634`: https://github.com/apache/cloudstack/pull/2634
+.. _CLOUDSTACK-9184: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
+.. _`#2634`: https://github.com/apache/cloudstack/pull/2634
+.. _CLOUDSTACK-9184: https://issues.apache.org/jira/browse/CLOUDSTACK-9184
+.. _`#2508`: https://github.com/apache/cloudstack/pull/2508
+.. _CLOUDSTACK-9114: https://issues.apache.org/jira/browse/CLOUDSTACK-9114
+.. _`#2508`: https://github.com/apache/cloudstack/pull/2508
+.. _CLOUDSTACK-9114: https://issues.apache.org/jira/browse/CLOUDSTACK-9114
+.. _`#2584`: https://github.com/apache/cloudstack/pull/2584
+.. _`#2600`: https://github.com/apache/cloudstack/pull/2600
+.. _CLOUDSTACK-10362: https://issues.apache.org/jira/browse/CLOUDSTACK-10362
+.. _`#2627`: https://github.com/apache/cloudstack/pull/2627
+.. _`#2615`: https://github.com/apache/cloudstack/pull/2615
+.. _`#2632`: https://github.com/apache/cloudstack/pull/2632
+.. _`#2621`: https://github.com/apache/cloudstack/pull/2621
+.. _`#2619`: https://github.com/apache/cloudstack/pull/2619
+.. _`#2607`: https://github.com/apache/cloudstack/pull/2607
+.. _`#2626`: https://github.com/apache/cloudstack/pull/2626
+.. _`#2623`: https://github.com/apache/cloudstack/pull/2623
+.. _`#2628`: https://github.com/apache/cloudstack/pull/2628
+.. _`#2628`: https://github.com/apache/cloudstack/pull/2628
+.. _`#2612`: https://github.com/apache/cloudstack/pull/2612
+.. _`#1940`: https://github.com/apache/cloudstack/pull/1940
+.. _CLOUDSTACK-9781: https://issues.apache.org/jira/browse/CLOUDSTACK-9781
+.. _`#2608`: https://github.com/apache/cloudstack/pull/2608
+.. _`#2574`: https://github.com/apache/cloudstack/pull/2574
+.. _`#2471`: https://github.com/apache/cloudstack/pull/2471
+.. _CLOUDSTACK-10311: https://issues.apache.org/jira/browse/CLOUDSTACK-10311
+.. _`#2606`: https://github.com/apache/cloudstack/pull/2606
+.. _`#2601`: https://github.com/apache/cloudstack/pull/2601
+.. _CLOUDSTACK-10364: https://issues.apache.org/jira/browse/CLOUDSTACK-10364
+.. _`#2599`: https://github.com/apache/cloudstack/pull/2599
+.. _CLOUDSTACK-10363: https://issues.apache.org/jira/browse/CLOUDSTACK-10363
+.. _`#2598`: https://github.com/apache/cloudstack/pull/2598
+.. _CLOUDSTACK-10360: https://issues.apache.org/jira/browse/CLOUDSTACK-10360
+.. _`#2605`: https://github.com/apache/cloudstack/pull/2605
+.. _`#2428`: https://github.com/apache/cloudstack/pull/2428
+.. _CLOUDSTACK-10253: https://issues.apache.org/jira/browse/CLOUDSTACK-10253
+.. _`#2536`: https://github.com/apache/cloudstack/pull/2536
+.. _`#2486`: https://github.com/apache/cloudstack/pull/2486
+.. _CLOUDSTACK-10323: https://issues.apache.org/jira/browse/CLOUDSTACK-10323
+.. _`#2422`: https://github.com/apache/cloudstack/pull/2422
+.. _CLOUDSTACK-10254: https://issues.apache.org/jira/browse/CLOUDSTACK-10254
+.. _`#2566`: https://github.com/apache/cloudstack/pull/2566
+.. _CLOUDSTACK-10288: https://issues.apache.org/jira/browse/CLOUDSTACK-10288
+.. _`#2573`: https://github.com/apache/cloudstack/pull/2573
+.. _CLOUDSTACK-10356: https://issues.apache.org/jira/browse/CLOUDSTACK-10356
+.. _`#2412`: https://github.com/apache/cloudstack/pull/2412
+.. _CLOUDSTACK-9677: https://issues.apache.org/jira/browse/CLOUDSTACK-9677
+.. _`#2594`: https://github.com/apache/cloudstack/pull/2594
+.. _`#2597`: https://github.com/apache/cloudstack/pull/2597
+.. _`#2498`: https://github.com/apache/cloudstack/pull/2498
+.. _CLOUDSTACK-10327: https://issues.apache.org/jira/browse/CLOUDSTACK-10327
+.. _`#2591`: https://github.com/apache/cloudstack/pull/2591
+.. _CLOUDSTACK-10359: https://issues.apache.org/jira/browse/CLOUDSTACK-10359
+.. _`#2590`: https://github.com/apache/cloudstack/pull/2590
+.. _`#2582`: https://github.com/apache/cloudstack/pull/2582
+.. _`#2577`: https://github.com/apache/cloudstack/pull/2577
+.. _`#2579`: https://github.com/apache/cloudstack/pull/2579
+.. _`#2589`: https://github.com/apache/cloudstack/pull/2589
+.. _`#2588`: https://github.com/apache/cloudstack/pull/2588
+.. _`#2505`: https://github.com/apache/cloudstack/pull/2505
+.. _CLOUDSTACK-10333: https://issues.apache.org/jira/browse/CLOUDSTACK-10333
+.. _`#2580`: https://github.com/apache/cloudstack/pull/2580
+.. _CLOUDSTACK-10357: https://issues.apache.org/jira/browse/CLOUDSTACK-10357
+.. _`#2587`: https://github.com/apache/cloudstack/pull/2587
+.. _`#2586`: https://github.com/apache/cloudstack/pull/2586
+.. _`#2576`: https://github.com/apache/cloudstack/pull/2576
+.. _`#2562`: https://github.com/apache/cloudstack/pull/2562
+.. _`#2554`: https://github.com/apache/cloudstack/pull/2554
+.. _`#2511`: https://github.com/apache/cloudstack/pull/2511
+.. _CLOUDSTACK-10344: https://issues.apache.org/jira/browse/CLOUDSTACK-10344
+.. _`#2572`: https://github.com/apache/cloudstack/pull/2572
+.. _`#2553`: https://github.com/apache/cloudstack/pull/2553
+.. _`#2499`: https://github.com/apache/cloudstack/pull/2499
+.. _`#2570`: https://github.com/apache/cloudstack/pull/2570
+.. _`#2568`: https://github.com/apache/cloudstack/pull/2568
+.. _`#2559`: https://github.com/apache/cloudstack/pull/2559
+.. _`#2567`: https://github.com/apache/cloudstack/pull/2567
+.. _`#2563`: https://github.com/apache/cloudstack/pull/2563
+.. _CLOUDSTACK-10304: https://issues.apache.org/jira/browse/CLOUDSTACK-10304
+.. _`#2555`: https://github.com/apache/cloudstack/pull/2555
+.. _`#2390`: https://github.com/apache/cloudstack/pull/2390
+.. _CLOUDSTACK-10214: https://issues.apache.org/jira/browse/CLOUDSTACK-10214
+.. _`#2564`: https://github.com/apache/cloudstack/pull/2564
+.. _`#2557`: https://github.com/apache/cloudstack/pull/2557
+.. _`#2404`: https://github.com/apache/cloudstack/pull/2404
+.. _CLOUDSTACK-10230: https://issues.apache.org/jira/browse/CLOUDSTACK-10230
+.. _`#2550`: https://github.com/apache/cloudstack/pull/2550
+.. _`#2560`: https://github.com/apache/cloudstack/pull/2560
+.. _`#2401`: https://github.com/apache/cloudstack/pull/2401
+.. _CLOUDSTACK-10226: https://issues.apache.org/jira/browse/CLOUDSTACK-10226
+.. _`#2462`: https://github.com/apache/cloudstack/pull/2462
+.. _CLOUDSTACK-10301: https://issues.apache.org/jira/browse/CLOUDSTACK-10301
+.. _`#2490`: https://github.com/apache/cloudstack/pull/2490
+.. _`#2538`: https://github.com/apache/cloudstack/pull/2538
+.. _`#2517`: https://github.com/apache/cloudstack/pull/2517
+.. _`#2552`: https://github.com/apache/cloudstack/pull/2552
+.. _`#2535`: https://github.com/apache/cloudstack/pull/2535
+.. _`#2526`: https://github.com/apache/cloudstack/pull/2526
+.. _`#2522`: https://github.com/apache/cloudstack/pull/2522
+.. _`#2519`: https://github.com/apache/cloudstack/pull/2519
+.. _CLOUDSTACK-10287: https://issues.apache.org/jira/browse/CLOUDSTACK-10287
+.. _`#2520`: https://github.com/apache/cloudstack/pull/2520
+.. _`#2515`: https://github.com/apache/cloudstack/pull/2515
+.. _`#2414`: https://github.com/apache/cloudstack/pull/2414
+.. _CLOUDSTACK-10241: https://issues.apache.org/jira/browse/CLOUDSTACK-10241
+.. _`#2512`: https://github.com/apache/cloudstack/pull/2512
+.. _`#2492`: https://github.com/apache/cloudstack/pull/2492
+.. _`#2496`: https://github.com/apache/cloudstack/pull/2496
+.. _CLOUDSTACK-10332: https://issues.apache.org/jira/browse/CLOUDSTACK-10332
+.. _`#2449`: https://github.com/apache/cloudstack/pull/2449
+.. _CLOUDSTACK-10278: https://issues.apache.org/jira/browse/CLOUDSTACK-10278
+.. _`#2510`: https://github.com/apache/cloudstack/pull/2510
+.. _CLOUDSTACK-10334: https://issues.apache.org/jira/browse/CLOUDSTACK-10334
+.. _`#2506`: https://github.com/apache/cloudstack/pull/2506
+.. _CLOUDSTACK-10341: https://issues.apache.org/jira/browse/CLOUDSTACK-10341
+.. _`#2506`: https://github.com/apache/cloudstack/pull/2506
+.. _CLOUDSTACK-10341: https://issues.apache.org/jira/browse/CLOUDSTACK-10341
+.. _`#2513`: https://github.com/apache/cloudstack/pull/2513
+.. _CLOUDSTACK-10227: https://issues.apache.org/jira/browse/CLOUDSTACK-10227
+.. _`#2513`: https://github.com/apache/cloudstack/pull/2513
+.. _CLOUDSTACK-10227: https://issues.apache.org/jira/browse/CLOUDSTACK-10227
+.. _`#2465`: https://github.com/apache/cloudstack/pull/2465
+.. _CLOUDSTACK-10232: https://issues.apache.org/jira/browse/CLOUDSTACK-10232
+.. _`#2438`: https://github.com/apache/cloudstack/pull/2438
+.. _CLOUDSTACK-10307: https://issues.apache.org/jira/browse/CLOUDSTACK-10307
+.. _`#2465`: https://github.com/apache/cloudstack/pull/2465
+.. _CLOUDSTACK-10232: https://issues.apache.org/jira/browse/CLOUDSTACK-10232
+.. _`#2507`: https://github.com/apache/cloudstack/pull/2507
+.. _CLOUDSTACK-10319: https://issues.apache.org/jira/browse/CLOUDSTACK-10319
+.. _`#2507`: https://github.com/apache/cloudstack/pull/2507
+.. _CLOUDSTACK-10319: https://issues.apache.org/jira/browse/CLOUDSTACK-10319
+.. _`#2397`: https://github.com/apache/cloudstack/pull/2397
+.. _CLOUDSTACK-10221: https://issues.apache.org/jira/browse/CLOUDSTACK-10221
+.. _`#2481`: https://github.com/apache/cloudstack/pull/2481
+.. _CLOUDSTACK-10320: https://issues.apache.org/jira/browse/CLOUDSTACK-10320
+.. _`#2468`: https://github.com/apache/cloudstack/pull/2468
+.. _CLOUDSTACK-10341: https://issues.apache.org/jira/browse/CLOUDSTACK-10341
+.. _`#2504`: https://github.com/apache/cloudstack/pull/2504
+.. _CLOUDSTACK-10340: https://issues.apache.org/jira/browse/CLOUDSTACK-10340
+.. _`#2497`: https://github.com/apache/cloudstack/pull/2497
+.. _CLOUDSTACK-10331: https://issues.apache.org/jira/browse/CLOUDSTACK-10331
+.. _`#2408`: https://github.com/apache/cloudstack/pull/2408
+.. _CLOUDSTACK-10231: https://issues.apache.org/jira/browse/CLOUDSTACK-10231
+.. _`#2494`: https://github.com/apache/cloudstack/pull/2494
+.. _CLOUDSTACK-10329: https://issues.apache.org/jira/browse/CLOUDSTACK-10329
+.. _`#2495`: https://github.com/apache/cloudstack/pull/2495
+.. _`#2489`: https://github.com/apache/cloudstack/pull/2489
+.. _CLOUDSTACK-10330: https://issues.apache.org/jira/browse/CLOUDSTACK-10330
+.. _`#2491`: https://github.com/apache/cloudstack/pull/2491
+.. _`#2469`: https://github.com/apache/cloudstack/pull/2469
+.. _CLOUDSTACK-10132: https://issues.apache.org/jira/browse/CLOUDSTACK-10132
+.. _`#2458`: https://github.com/apache/cloudstack/pull/2458
+.. _CLOUDSTACK-10296: https://issues.apache.org/jira/browse/CLOUDSTACK-10296
+.. _`#2433`: https://github.com/apache/cloudstack/pull/2433
+.. _CLOUDSTACK-10268: https://issues.apache.org/jira/browse/CLOUDSTACK-10268
+.. _`#2387`: https://github.com/apache/cloudstack/pull/2387
+.. _CLOUDSTACK-8855: https://issues.apache.org/jira/browse/CLOUDSTACK-8855
+.. _`#2482`: https://github.com/apache/cloudstack/pull/2482
+.. _CLOUDSTACK-10321: https://issues.apache.org/jira/browse/CLOUDSTACK-10321
+.. _`#2483`: https://github.com/apache/cloudstack/pull/2483
+.. _CLOUDSTACK-10303: https://issues.apache.org/jira/browse/CLOUDSTACK-10303
+.. _`#2442`: https://github.com/apache/cloudstack/pull/2442
+.. _CLOUDSTACK-10147: https://issues.apache.org/jira/browse/CLOUDSTACK-10147
+.. _`#2484`: https://github.com/apache/cloudstack/pull/2484
+.. _`#2475`: https://github.com/apache/cloudstack/pull/2475
+.. _CLOUDSTACK-10314: https://issues.apache.org/jira/browse/CLOUDSTACK-10314
+.. _`#2485`: https://github.com/apache/cloudstack/pull/2485
+.. _`#2480`: https://github.com/apache/cloudstack/pull/2480
+.. _CLOUDSTACK-10319: https://issues.apache.org/jira/browse/CLOUDSTACK-10319
+.. _`#2470`: https://github.com/apache/cloudstack/pull/2470
+.. _CLOUDSTACK-10197: https://issues.apache.org/jira/browse/CLOUDSTACK-10197
+.. _`#2476`: https://github.com/apache/cloudstack/pull/2476
+.. _CLOUDSTACK-10317: https://issues.apache.org/jira/browse/CLOUDSTACK-10317
+.. _`#2425`: https://github.com/apache/cloudstack/pull/2425
+.. _CLOUDSTACK-10240: https://issues.apache.org/jira/browse/CLOUDSTACK-10240
+.. _`#2448`: https://github.com/apache/cloudstack/pull/2448
+.. _CLOUDSTACK-10274: https://issues.apache.org/jira/browse/CLOUDSTACK-10274
+.. _`#2478`: https://github.com/apache/cloudstack/pull/2478
+.. _CLOUDSTACK-10318: https://issues.apache.org/jira/browse/CLOUDSTACK-10318
+.. _`#2437`: https://github.com/apache/cloudstack/pull/2437
+.. _CLOUDSTACK-10257: https://issues.apache.org/jira/browse/CLOUDSTACK-10257
+.. _`#2439`: https://github.com/apache/cloudstack/pull/2439
+.. _CLOUDSTACK-10259: https://issues.apache.org/jira/browse/CLOUDSTACK-10259
+.. _`#2392`: https://github.com/apache/cloudstack/pull/2392
+.. _`#2463`: https://github.com/apache/cloudstack/pull/2463
+.. _CLOUDSTACK-10302: https://issues.apache.org/jira/browse/CLOUDSTACK-10302
+.. _`#2464`: https://github.com/apache/cloudstack/pull/2464
+.. _CLOUDSTACK-10299: https://issues.apache.org/jira/browse/CLOUDSTACK-10299
+.. _`#2244`: https://github.com/apache/cloudstack/pull/2244
+.. _CLOUDSTACK-10054: https://issues.apache.org/jira/browse/CLOUDSTACK-10054
+.. _`#2467`: https://github.com/apache/cloudstack/pull/2467
+.. _CLOUDSTACK-10306: https://issues.apache.org/jira/browse/CLOUDSTACK-10306
+.. _`#2460`: https://github.com/apache/cloudstack/pull/2460
+.. _CLOUDSTACK-10298: https://issues.apache.org/jira/browse/CLOUDSTACK-10298
+.. _`#2466`: https://github.com/apache/cloudstack/pull/2466
+.. _CLOUDSTACK-10305: https://issues.apache.org/jira/browse/CLOUDSTACK-10305
+.. _`#2443`: https://github.com/apache/cloudstack/pull/2443
+.. _CLOUDSTACK-9338: https://issues.apache.org/jira/browse/CLOUDSTACK-9338
+.. _`#2451`: https://github.com/apache/cloudstack/pull/2451
+.. _CLOUDSTACK-10284: https://issues.apache.org/jira/browse/CLOUDSTACK-10284
+.. _`#2454`: https://github.com/apache/cloudstack/pull/2454
+.. _CLOUDSTACK-10283: https://issues.apache.org/jira/browse/CLOUDSTACK-10283
+.. _`#2457`: https://github.com/apache/cloudstack/pull/2457
+.. _CLOUDSTACK-10295: https://issues.apache.org/jira/browse/CLOUDSTACK-10295
+.. _`#2456`: https://github.com/apache/cloudstack/pull/2456
+.. _CLOUDSTACK-10293: https://issues.apache.org/jira/browse/CLOUDSTACK-10293
+.. _`#2402`: https://github.com/apache/cloudstack/pull/2402
+.. _CLOUDSTACK-10128: https://issues.apache.org/jira/browse/CLOUDSTACK-10128
+.. _`#2432`: https://github.com/apache/cloudstack/pull/2432
+.. _CLOUDSTACK-10294: https://issues.apache.org/jira/browse/CLOUDSTACK-10294
+.. _`#2450`: https://github.com/apache/cloudstack/pull/2450
+.. _CLOUDSTACK-10282: https://issues.apache.org/jira/browse/CLOUDSTACK-10282
+.. _`#2452`: https://github.com/apache/cloudstack/pull/2452
+.. _CLOUDSTACK-10285: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
+.. _`#2441`: https://github.com/apache/cloudstack/pull/2441
+.. _CLOUDSTACK-10261: https://issues.apache.org/jira/browse/CLOUDSTACK-10261
+.. _`#2420`: https://github.com/apache/cloudstack/pull/2420
+.. _CLOUDSTACK-10247: https://issues.apache.org/jira/browse/CLOUDSTACK-10247
+.. _`#2424`: https://github.com/apache/cloudstack/pull/2424
+.. _CLOUDSTACK-10251: https://issues.apache.org/jira/browse/CLOUDSTACK-10251
+.. _`#2421`: https://github.com/apache/cloudstack/pull/2421
+.. _CLOUDSTACK-10243: https://issues.apache.org/jira/browse/CLOUDSTACK-10243
+.. _`#2406`: https://github.com/apache/cloudstack/pull/2406
+.. _CLOUDSTACK-9663: https://issues.apache.org/jira/browse/CLOUDSTACK-9663
+.. _`#2445`: https://github.com/apache/cloudstack/pull/2445
+.. _CLOUDSTACK-10218: https://issues.apache.org/jira/browse/CLOUDSTACK-10218
+.. _`#2444`: https://github.com/apache/cloudstack/pull/2444
+.. _CLOUDSTACK-10269: https://issues.apache.org/jira/browse/CLOUDSTACK-10269
+.. _`#2405`: https://github.com/apache/cloudstack/pull/2405
+.. _CLOUDSTACK-10146: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
+.. _`#2398`: https://github.com/apache/cloudstack/pull/2398
+.. _CLOUDSTACK-10222: https://issues.apache.org/jira/browse/CLOUDSTACK-10222
+.. _`#2431`: https://github.com/apache/cloudstack/pull/2431
+.. _CLOUDSTACK-10225: https://issues.apache.org/jira/browse/CLOUDSTACK-10225
+
+Issues Fixed in 4.11.0.0
+------------------------
+
+.. cssclass:: table-striped table-bordered table-hover
+
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| Branches | Github | Jira | Type | Priority | Description |
++=========================+==========+====================+===============+==========+============================================================+
+| 4.11 | `#2097`_ | CLOUDSTACK-9813_ | New Feature | Major | Use configdrive for userdata, metadata & password |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2146`_ | CLOUDSTACK-4757_ | New Feature | Minor | Support OVA files with multiple disks for templates |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2394`_ | CLOUDSTACK-10109_ | New Feature | Major | Enable dedication of public IPs to SSVM and CPVM |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2295`_ | CLOUDSTACK-10109_ | New Feature | Major | Enable dedication of public IPs to SSVM and CPVM |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2381`_ | CLOUDSTACK-10117_ | New Feature | Major | LDAP mapping on domain level |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2368`_ | CLOUDSTACK-10126_ | New Feature | Major | Separate Subnet for CPVM and SSVM |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2046`_ | CLOUDSTACK-7958_ | New Feature | Minor | Limit user login to specific subnets |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2374`_ | CLOUDSTACK-10024_ | New Feature | Major | Physical Networking Migration |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2301`_ | CLOUDSTACK-10121_ | New Feature | Major | move user API |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2360`_ | CLOUDSTACK-10189_ | New Feature | Major | Support for "VSD managed" networks with Nuage Networks |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2281`_ | CLOUDSTACK-10102_ | New Feature | Major | New Network Type (L2) |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2048`_ | CLOUDSTACK-9880_ | New Feature | Major | Expansion of Management IP Range. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2294`_ | CLOUDSTACK-10039_ | New Feature | Major | Adding IOPS/GB offering |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2356`_ | CLOUDSTACK-8313_ | New Feature | Major | Local Storage overprovisioning should be possible |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2028`_ | CLOUDSTACK-9853_ | New Feature | Major | IPv6 Prefix Delegation support in Basic Networking |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1981`_ | CLOUDSTACK-9806_ | New Feature | Major | Nuage domain template selection per VPC |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2325`_ | CLOUDSTACK-9998_ | New Feature | Major | CloudStack exporter for Prometheus |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2284`_ | CLOUDSTACK-10103_ | New Feature | Major | Cloudian Connector for CloudStack |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2297`_ | CLOUDSTACK-9957_ | New Feature | Major | Annotations on entities |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2181`_ | CLOUDSTACK-9957_ | New Feature | Major | Annotations on entities |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2286`_ | CLOUDSTACK-9993_ | New Feature | Major | Secure Agent Communications |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2287`_ | CLOUDSTACK-9998_ | New Feature | Major | CloudStack exporter for Prometheus |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2278`_ | CLOUDSTACK-9993_ | New Feature | Major | Secure Agent Communications |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1707`_ | CLOUDSTACK-9397_ | New Feature | Major | Add Watchdog timer to KVM Instances |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2143`_ | CLOUDSTACK-9949_ | New Feature | Minor | add ability to specify mac address when |
+| | | | | | deployVirtualMachine or addNicToVirtualMachine is called |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2256`_ | CLOUDSTACK-9782_ | New Feature | Major | Host HA |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2239`_ | CLOUDSTACK-9993_ | New Feature | Major | Secure Agent Communications |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2222`_ | CLOUDSTACK-10022_ | New Feature | Minor | Allow domain admin to create and delete subdomains |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2026`_ | CLOUDSTACK-9861_ | New Feature | Major | Expire VM snapshots after configured duration |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2218`_ | CLOUDSTACK-9782_ | New Feature | Major | Host HA |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11* | `#2407`_ | CLOUDSTACK-10227_ | Bug | Blocker | Stabilization fixes for master/4.11 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2403`_ | CLOUDSTACK-10227_ | Bug | Blocker | Stabilization fixes for master/4.11 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2396`_ | CLOUDSTACK-10220_ | Bug | Major | IPv4 NIC alias is not added on Virtual Router in Basic |
+| | | | | | Networking when NIC has IPv6 address |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2362`_ | CLOUDSTACK-10188_ | Bug | Major | Resource Accounting for primary storage is Broken |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2393`_ | CLOUDSTACK-10217_ | Bug | Major | When IPv4 address of Instance is updated DHCP data is not |
+| | | | | | cleared on VR |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2388`_ | CLOUDSTACK-10212_ | Bug | Major | Changing IPv4 Address of NIC in Basic Networking does not |
+| | | | | | update the gateway |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2379`_ | CLOUDSTACK-10146_ | Bug | Major | Bypass Secondary Storage for KVM templates |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2391`_ | CLOUDSTACK-10215_ | Bug | Major | Excessive log4j debug level in CPVM, SSVM could lead to FS |
+| | | | | | overflow |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2139`_ | CLOUDSTACK-9921_ | Bug | Major | NPE when garbage collector is running |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2088`_ | CLOUDSTACK-9892_ | Bug | Critical | Primary storage resource check is broken when using root |
+| | | | | | disk size override to deploy VM |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2365`_ | CLOUDSTACK-10197_ | Bug | Major | XenServer 7.1: Cannot mount xentool iso from cloudstack |
+| | | | | | on VMs |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2073`_ | CLOUDSTACK-9896_ | Bug | Minor | ListDedicatedXXX doesn't respect pagination |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2386`_ | CLOUDSTACK-9632_ | Bug | Major | Upgrade bountycastle to 1.55+ |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2315`_ | CLOUDSTACK-9025_ | Bug | Critical | Unable to deploy VM instance from template if template |
+| | | | | | spin from linked clone snapshot |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2274`_ | CLOUDSTACK-10096_ | Bug | Major | Can't reset api.integration.port and |
+| | | | | | usage.sanity.check.interval back to null |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2282`_ | CLOUDSTACK-10104_ | Bug | Major | Optimize database transactions in ListDomain API to |
+| | | | | | improve performance |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2385`_ | CLOUDSTACK-10211_ | Bug | Major | test_nuage_public_sharednetwork_userdata fails due to |
+| | | | | | errortext changed |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2260`_ | CLOUDSTACK-10065_ | Bug | Major | Optimize SQL queries in listTemplate API to improve |
+| | | | | | performance. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1740`_ | CLOUDSTACK-9572_ | Bug | Major | Snapshot on primary storage not cleaned up after Storage |
+| | | | | | migration |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2104`_ | CLOUDSTACK-9908_ | Bug | Major | Primary Storage allocated capacity goes very high after VM |
+| | | | | | snapshot |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2378`_ | CLOUDSTACK-10205_ | Bug | Major | LinkDomainToLdap returns internal id |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1773`_ | CLOUDSTACK-9607_ | Bug | Major | Preventing template deletion when template is in use. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2149`_ | CLOUDSTACK-9932_ | Bug | Major | Snapshot is getting deleted while volume creation from the |
+| | | | | | snapshot is in progress |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2156`_ | CLOUDSTACK-9971_ | Bug | Minor | Bugfix/listaccounts parameter consistency |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2373`_ | CLOUDSTACK-10202_ | Bug | Major | createSnapshotPolicy API create multiple entries in DB for |
+| | | | | | same volume. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2344`_ | CLOUDSTACK-10163_ | Bug | Major | Component tests health check |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1760`_ | CLOUDSTACK-9593_ | Bug | Major | User data check is inconsistent with python |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2352`_ | CLOUDSTACK-10175_ | Bug | Major | Listing VPCs with a domain account and project id -1 |
+| | | | | | returns all the VPCs in the syste |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2347`_ | CLOUDSTACK-10166_ | Bug | Minor | Cannot add a tag to a NetworkACL (rule not list) in CS |
+| | | | | | with a user in a project or in an account |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2375`_ | CLOUDSTACK-9456_ | Bug | Major | Migrate master to use Java8 and Spring4 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2211`_ | CLOUDSTACK-10013_ | Bug | Major | Migrate to Debian9 systemvmtemplate |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.9* | `#2304`_ | CLOUDSTACK-10127_ | Bug | Critical | 4.9 / 4.10 KVM + openvswitch + vpc + static nat / |
+| | | | | | secondary ip on eth2 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2208`_ | CLOUDSTACK-9542_ | Bug | Major | listNics API does not return data as per API documentation |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2351`_ | CLOUDSTACK-10173_ | Bug | Major | Guest/Public nics on VR should pick network rate from |
+| | | | | | network offering |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2370`_ | CLOUDSTACK-9595_ | Bug | Major | Transactions are not getting retried in case of database |
+| | | | | | deadlock errors |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2366`_ | CLOUDSTACK-10168_ | Bug | Major | VR duplicate entries in /etc/hosts when reusing VM name |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2042`_ | CLOUDSTACK-9875_ | Bug | Major | Unable to re-apply Explicit dedication to VM |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2364`_ | CLOUDSTACK-10195_ | Bug | Minor | CloudStack MySQL HA problem -- No database selected |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2361`_ | CLOUDSTACK-10190_ | Bug | Major | Duplicate public VLAN for two different admin accounts. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2247`_ | CLOUDSTACK-10012_ | Bug | Major | Migrate to Embedded Jetty based mgmt server |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1964`_ | CLOUDSTACK-9800_ | Bug | Major | Enable inline mode for NetScaler device |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1762`_ | CLOUDSTACK-9595_ | Bug | Major | Transactions are not getting retried in case of database |
+| | | | | | deadlock errors |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2308`_ | CLOUDSTACK-8908_ | Bug | Major | After copying the template charging for that template is |
+| | | | | | stopped |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2354`_ | CLOUDSTACK-10176_ | Bug | Major | VM Start Api Job returns success for failed Job |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2353`_ | CLOUDSTACK-9986_ | Bug | Major | Consider overcommit ratios with total/threshold values in |
+| | | | | | Metrics View |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2358`_ | CLOUDSTACK-9736_ | Bug | Minor | Incoherent validation and error message when you change |
+| | | | | | the vm.password.length configuration parameter |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2326`_ | CLOUDSTACK-10184_ | Bug | Major | Re-work method QuotaResponseBuilderImpl.startOfNextDay and |
+| | | | | | its test cases |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2267`_ | CLOUDSTACK-10077_ | Bug | Major | Allow account to use the same site-2-site VPN gateway with |
+| | | | | | different configs for several VPCs |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2337`_ | CLOUDSTACK-10157_ | Bug | Major | Wrong notification while migration |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2355`_ | CLOUDSTACK-10177_ | Bug | Major | NPE when programming Security Groups with KVM |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2349`_ | CLOUDSTACK-10070_ | Bug | Major | Extend travis run to include more component tests |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2312`_ | CLOUDSTACK-7793_ | Bug | Critical | [Snapshots]Create Snaphot with "quiesce" option set to |
+| | | | | | true fails with "InvalidParameterValueException: can't |
+| | | | | | handle quiescevm equal true for volume snapshot" |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2345`_ | CLOUDSTACK-10164_ | Bug | Blocker | UI - not able to create a VPC |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2263`_ | CLOUDSTACK-10070_ | Bug | Major | Extend travis run to include more component tests |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2342`_ | CLOUDSTACK-9586_ | Bug | Critical | When using local storage with Xenserver prepareTemplate |
+| | | | | | does not work with multiple primary store |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2124`_ | CLOUDSTACK-9432_ | Bug | Critical | Dedicate Cluster to Domain always creates an affinity |
+| | | | | | group owned by the root domain |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2322`_ | CLOUDSTACK-10140_ | Bug | Critical | When template is created from snapshot template.properties |
+| | | | | | are corrupted |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2335`_ | CLOUDSTACK-10154_ | Bug | Major | test failures in smoketest |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2341`_ | CLOUDSTACK-10160_ | Bug | Major | KVM VirtIO-SCSI not defined properly in Libvirt XML |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2321`_ | CLOUDSTACK-10138_ | Bug | Major | Load br_netfilter in security_group management script |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2334`_ | CLOUDSTACK-10152_ | Bug | Major | egress destination cidr with 0.0.0.0/0 is failing |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2310`_ | CLOUDSTACK-10133_ | Bug | Major | Local storage overprovisioning for ext file system |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2303`_ | CLOUDSTACK-10123_ | Bug | Major | VmWork job gets deleted before the parent job had time to |
+| | | | | | fetch its result |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2329`_ | CLOUDSTACK-10012_ | Bug | Major | Migrate to Embedded Jetty based mgmt server |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2327`_ | CLOUDSTACK-10129_ | Bug | Trivial | Show instances attached to a network/VR via navigation |
+| | | | | | from VRs->instances |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2313`_ | CLOUDSTACK-10135_ | Bug | Major | ACL rules order is not maintained for ACL_OUTBOUND in VPC |
+| | | | | | VR |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2316`_ | CLOUDSTACK-10137_ | Bug | Major | Re-installation fails for cloudstack-management |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2157`_ | CLOUDSTACK-9961_ | Bug | Major | Accept domain name for gateway while creating |
+| | | | | | Vpncustomergateway |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2306`_ | CLOUDSTACK-10129_ | Bug | Trivial | Show instances attached to a network/VR via navigation |
+| | | | | | from VRs->instances |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2273`_ | CLOUDSTACK-10090_ | Bug | Major | createPortForwardingRule api call accepts 'halt' as |
+| | | | | | Protocol which Stops VR |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2240`_ | CLOUDSTACK-10051_ | Bug | Major | Mouse Scrolling is not working in instance VM console |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2291`_ | CLOUDSTACK-10111_ | Bug | Minor | Fix validation for parameter "vm.password.length" |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2302`_ | CLOUDSTACK-10122_ | Bug | Major | Unrelated error message |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2250`_ | CLOUDSTACK-10057_ | Bug | Major | ListNetworkOfferingsCmd does not return the correct count |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2268`_ | CLOUDSTACK-10081_ | Bug | Major | CloudUtils getDevInfo function only checks for KVM |
+| | | | | | bridgePort and not OVS |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2293`_ | CLOUDSTACK-10047_ | Bug | Major | DVSwitch improvements |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2288`_ | CLOUDSTACK-10107_ | Bug | Major | VMware VM fails to start if it has more than 7 nics |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2257`_ | CLOUDSTACK-10060_ | Bug | Minor | ListUsage API always displays the Virtual size as '0' for |
+| | | | | | Usage type=9 (snapshot) |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2246`_ | CLOUDSTACK-10046_ | Bug | Major | checksum is not verified during registerTemplate |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2074`_ | CLOUDSTACK-9899_ | Bug | Major | allow download without checking first for MS behind |
+| | | | | | firewall |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2279`_ | CLOUDSTACK-9584_ | Bug | Major | Increase component tests coverage in Travis run |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2277`_ | CLOUDSTACK-10099_ | Bug | Major | GUI invokes migrateVirtualMachine instead of |
+| | | | | | migrateVirtualMachineWithVolume |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2269`_ | CLOUDSTACK-10083_ | Bug | Minor | SSH keys are not created when starting from maintenance |
+| | | | | | mode |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#876`_ | CLOUDSTACK-8865_ | Bug | Major | Adding SR doesn't create Storage_pool_host_ref entry for |
+| | | | | | disabled host |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1252`_ | CLOUDSTACK-9182_ | Bug | Major | Some running VMs turned off on manual migration when auto |
+| | | | | | migration failed while host preparing for maintenance |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2153`_ | CLOUDSTACK-9956_ | Bug | Major | File search on the vmware datastore may select wrong file |
+| | | | | | if there are multiple files with same name |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2078`_ | CLOUDSTACK-9902_ | Bug | Minor | consoleproxy.sslEnabled global config variable is not |
+| | | | | | present in default install |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2252`_ | CLOUDSTACK-10067_ | Bug | Major | Fix a case where a user 'ro' or 'roo' exists on the system |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2248`_ | CLOUDSTACK-10056_ | Bug | Minor | Cannot specify root disk controller when creating VM |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2243`_ | CLOUDSTACK-10019_ | Bug | Major | template.properties has hardcoded id |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2261`_ | CLOUDSTACK-10068_ | Bug | Major | smoketest/test_iso.py reports assertion failure |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2054`_ | CLOUDSTACK-9886_ | Bug | Major | After restarting cloudstack-management , It takes time to |
+| | | | | | connect hosts |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#955`_ | CLOUDSTACK-8969_ | Bug | Major | VPN customer gateway can't be registered with hostname |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.9* | `#2262`_ | CLOUDSTACK-10069_ | Bug | Major | During release add sha512 suffix to sha 512 checksum/file |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2253`_ | CLOUDSTACK-10061_ | Bug | Major | When starting a VM, make sure it has the correct volume |
+| | | | | | access group |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2254`_ | CLOUDSTACK-10058_ | Bug | Major | Error while opening the Settings tab in Secondary storage |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1733`_ | CLOUDSTACK-9563_ | Bug | Major | ExtractTemplate returns malformed URL after migrating NFS |
+| | | | | | to s3 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2188`_ | CLOUDSTACK-10004_ | Bug | Major | On deletion, Vmware volume snapshots are left behind with |
+| | | | | | message 'the snapshot has child, can't delete it on the |
+| | | | | | storage' |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#914`_ | CLOUDSTACK-8939_ | Bug | Major | VM Snapshot size with memory is not correctly calculated |
+| | | | | | in cloud.usage_event (XenServer) |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1985`_ | CLOUDSTACK-9812_ | Bug | Major | Update "updatePortForwardingRule" pi to include additional |
+| | | | | | parameter to update the end port in case of port range |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2224`_ | CLOUDSTACK-10032_ | Bug | Major | Database entries for templates created from snapshots |
+| | | | | | disappear after management-server service restart |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2109`_ | CLOUDSTACK-9922_ | Bug | Major | Unable to use 8081 port for Load balancing |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2216`_ | CLOUDSTACK-10027_ | Bug | Minor | Repeating the same list for Internal LB in VPC |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2174`_ | CLOUDSTACK-9996_ | Bug | Major | bug in network resource that juniper srx firewall |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2186`_ | CLOUDSTACK-10002_ | Bug | Major | Restart network with cleanup spawns Redundant Routers(In |
+| | | | | | Default Network Offering) |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1246`_ | CLOUDSTACK-9165_ | Bug | Major | unable to use reserved IP range in a network for external |
+| | | | | | VMs |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.9* | `#2241`_ | CLOUDSTACK-10052_ | Bug | Major | Upgrading to 4.9.2 causes confusion/issues around dynamic |
+| | | | | | roles usage |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2221`_ | CLOUDSTACK-10030_ | Bug | Minor | Public IPs assgined to the VPC are not reacheable from |
+| | | | | | inside VPC |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2154`_ | CLOUDSTACK-9967_ | Bug | Major | [VPC] static nat on additional public subnet ip is not |
+| | | | | | working. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1878`_ | CLOUDSTACK-9717_ | Bug | Major | [VMware] RVRs have mismatching MAC addresses for extra |
+| | | | | | public NICs |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2013`_ | CLOUDSTACK-9734_ | Bug | Major | Destroy VM Fails sometimes |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2159`_ | CLOUDSTACK-9964_ | Bug | Critical | Snapahots are getting deleted if VM is assigned to another |
+| | | | | | user |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2163`_ | CLOUDSTACK-9939_ | Bug | Major | Volumes stuck in Creating state while restarting the |
+| | | | | | Management Server when the volume creation is in progress |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1919`_ | CLOUDSTACK-9763_ | Bug | Major | vpc: can not ssh to instance after vpc restart |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2215`_ | CLOUDSTACK-10026_ | Bug | Major | Page for Internal LB VM stucking while loading |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2180`_ | CLOUDSTACK-9999_ | Bug | Major | vpc tiers do not work if vpc has more than 8 tiers |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2223`_ | CLOUDSTACK-10031_ | Bug | Major | change default configuration for |
+| | | | | | router.aggregation.command.each.timeout from 3 to 600 |
+| | | | | | seconds. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2182`_ | CLOUDSTACK-10000_ | Bug | Major | Remote access vpn user does not work if user password |
+| | | | | | contains '#' |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.9* | `#2233`_ | CLOUDSTACK-10042_ | Bug | Major | UI doesn't show ICMP Type and Code for Security Group |
+| | | | | | rules |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2228`_ | CLOUDSTACK-10036_ | Bug | Major | Decrease timeout of failing unit test |
+| | | | | | HypervisorUtilsTest.java |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1774`_ | CLOUDSTACK-9608_ | Bug | Major | Errored State and Abandoned state Templates are not |
+| | | | | | displayed on UI |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2144`_ | CLOUDSTACK-9955_ | Bug | Minor | Featured Templates/Iso's created by Root/admin user are |
+| | | | | | not visible to Domain Admin users |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.9* | `#1966`_ | CLOUDSTACK-9801_ | Bug | Critical | IPSec VPN does not work after vRouter reboot or recreate |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.9* | `#2220`_ | CLOUDSTACK-9708_ | Bug | Major | Router deployment failed due to two threads start VR |
+| | | | | | simultaneosuly |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1912`_ | CLOUDSTACK-9749_ | Bug | Critical | cloudstack master vpc_internal_lb feature is broken as |
+| | | | | | port 8080 is in use by password server on lb VM |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2138`_ | CLOUDSTACK-9944_ | Bug | Major | In clustered Management Server, Sometimes hosts stays in |
+| | | | | | disconnected state. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#883`_ | CLOUDSTACK-8906_ | Bug | Major | /var/log/cloud/ doesn't get logrotated on xenserver |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2119`_ | CLOUDSTACK-9925_ | Bug | Minor | Quota: fix tariff description for memory. Tariff value is |
+| | | | | | for 1MB of RAM used per month (not hour). |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2145`_ | CLOUDSTACK-9697_ | Bug | Major | Better error message on UI user if tries to shrink the VM |
+| | | | | | ROOT volume size |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2137`_ | CLOUDSTACK-9950_ | Bug | Major | listUsageRecords doesnt return required fields |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2008`_ | CLOUDSTACK-9840_ | Bug | Major | Datetime format of snapshot events is inconsistent with |
+| | | | | | other events |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2142`_ | CLOUDSTACK-9954_ | Bug | Major | Unable to create service offering with networkrate=0 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2171`_ | CLOUDSTACK-9990_ | Bug | Minor | Account name is giving null in event tab after successful |
+| | | | | | creation of account |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.9* | `#1925`_ | CLOUDSTACK-9751_ | Bug | Major | if a public IP is assigned to a VM when VR is in starting |
+| | | | | | state, it does not get applied to the vport in Nuage VSD |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.9* | `#1798`_ | CLOUDSTACK-9631_ | Bug | Major | updateVMAffinityGroup must require one of the list |
+| | | | | | parameter |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.9* | `#2201`_ | CLOUDSTACK-10016_ | Bug | Major | VPC VR doesn't respond to DNS requests from remote access |
+| | | | | | vpn clients |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1959`_ | CLOUDSTACK-9786_ | Bug | Major | API reference guide entry for associateIpAddress needs a |
+| | | | | | fix |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.9* | `#1933`_ | CLOUDSTACK-9569_ | Bug | Critical | VR on shared network not starting on KVM |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2298`_ | CLOUDSTACK-9620_ | Improvement | Major | Improvements for Managed Storage |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2152`_ | CLOUDSTACK-10229_ | Improvement | Trivial | SSVM logging improvement when using Swift as |
+| | | | | | secondary-storage |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2389`_ | CLOUDSTACK-10213_ | Improvement | Major | Allow specify SSH key lengh |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2292`_ | CLOUDSTACK-10108_ | Improvement | Minor | ConfigKey based approach for reading 'ping' configuaration |
+| | | | | | for Management Server |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2384`_ | CLOUDSTACK-10210_ | Improvement | Trivial | remove test file |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1554`_ | CLOUDSTACK-9602_ | Improvement | Major | Add resource type name in response |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2035`_ | CLOUDSTACK-9867_ | Improvement | Major | VM snapshots - not charged for the primary storage they |
+| | | | | | use up |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1934`_ | CLOUDSTACK-9772_ | Improvement | Major | Perform HEAD request to retrieve header information |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2348`_ | CLOUDSTACK-10196_ | Improvement | Minor | Remove ejb-api 3.0 dependency |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2184`_ | CLOUDSTACK-10003_ | Improvement | Major | automatic configure juniper srx/vsrx nat loopback |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2332`_ | CLOUDSTACK-10156_ | Improvement | Minor | Fix Coverity new problems CID(1349987, 1349986, 1347248) |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2219`_ | CLOUDSTACK-9989_ | Improvement | Major | Extend smoketests suite |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2005`_ | CLOUDSTACK-9450_ | Improvement | Major | Network Offering for VPC based on DB flag |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2242`_ | CLOUDSTACK-9958_ | Improvement | Major | Include tags of resources in listUsageRecords API |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2158`_ | CLOUDSTACK-9972_ | Improvement | Major | Enhance listVolume API to include physical size and |
+| | | | | | utilization. |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2004`_ | CLOUDSTACK-9832_ | Improvement | Major | Do not assign public IP NIC to the VPC VR when the VPC |
+| | | | | | offering does not contain VpcVirtualRouter as a SourceNat |
+| | | | | | provider |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2238`_ | CLOUDSTACK-10053_ | Improvement | Major | Performance improvement: Caching of external id's |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2296`_ | CLOUDSTACK-10007_ | Improvement | Major | Isolation methods are hard coded enum, replace by registry |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2280`_ | CLOUDSTACK-10101_ | Improvement | Major | Present the full domain name when listing user's domains |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2285`_ | CLOUDSTACK-9859_ | Improvement | Major | Retirement of midonet plugin (final removal ticket) |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2266`_ | CLOUDSTACK-10073_ | Improvement | Trivial | KVM host RAM overprovisioning |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2249`_ | CLOUDSTACK-10007_ | Improvement | Major | Isolation methods are hard coded enum, replace by registry |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1443`_ | CLOUDSTACK-9314_ | Improvement | Trivial | Remove unused code from XenServerStorageProcessor and |
+| | | | | | change methods access level |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2044`_ | CLOUDSTACK-9877_ | Improvement | Major | remove fully cloned deleted templates from primary storage |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2101`_ | CLOUDSTACK-9915_ | Improvement | Major | ListSnapshots API does not provide virtual size |
+| | | | | | information of the snapshots |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2123`_ | CLOUDSTACK-9914_ | Improvement | Trivial | Alter quota_tariff to support currency values up to 5 |
+| | | | | | decimal places |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1936`_ | CLOUDSTACK-9773_ | Improvement | Major | Don't break API output with non-printable characters |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2236`_ | CLOUDSTACK-10044_ | Improvement | Major | Update rule permission of a role permission |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2193`_ | CLOUDSTACK-10007_ | Improvement | Major | Isolation methods are hard coded enum, replace by registry |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2130`_ | CLOUDSTACK-8961_ | Improvement | Major | Making the VPN user management more intutive |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2200`_ | CLOUDSTACK-10015_ | Improvement | Minor | Return storage provider with call to list storage pools |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2350`_ | | | | Cloudstack 10170 - fixes resource tags security bugs and |
+| | | | | | adds account tags support |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2383`_ | | | | "isdynamicallyscalable" Field to UpdateTemplate Response |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2045`_ | | | | Fix snmptrap alert bug |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2258`_ | | | | Cloudstack 10064: Secondary storage Usage for |
+| | | | | | uploadedVolume is not collected |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1637`_ | | | | Command route not available on CentOS 7 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2367`_ | | | | Fix ACL_INBOUND/OUTBOUND rules for PrivateGateway |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2371`_ | | | | README: Happy Holidays, may the cloud be with you in 2018! |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1437`_ | | | | removed unused HypervDummyResourceBase class |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2346`_ | | | | Add XenServer 7.1 and 7.2 interoperablility |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2359`_ | | | | doc: replace virutal by virtual (typo) |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2324`_ | | | | Remove annotation and "depends-on" declaration not needed |
+| | | | | | at cloud-engine-storage-image |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1723`_ | | | | Fix GroupBy (+ having) condition and tests |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2307`_ | | | | packging: Raise compat mode to 9 |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2245`_ | | | | increased jetty timeout |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2235`_ | | | | repo has moved |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2039`_ | | | | rbd: Use libvirt to create new volumes and not rados-java |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.9* | `#2094`_ | | | | Agent logrotation |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.9* | `#2212`_ | | | | appliance: fix progress version in Gemfile |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2205`_ | | | | Add NULL checks for various objects in SolidFire |
+| | | | | | integration test API |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1784`_ | | | | CS-505: Marvin test to check VR internal DNS Service |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#1655`_ | | | | Fix ajaxviewer.js to solve console on Firefox |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.11 | `#2175`_ | | | | 4.10 to 4.11 upgrade path |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+| 4.10* | `#2176`_ | | | | Travis: use oraclejdk8 for 4.10+ |
++-------------------------+----------+--------------------+---------------+----------+------------------------------------------------------------+
+
+.. _`#2407`: https://github.com/apache/cloudstack/pull/2407
+.. _CLOUDSTACK-10227: https://issues.apache.org/jira/browse/CLOUDSTACK-10227
+.. _`#2403`: https://github.com/apache/cloudstack/pull/2403
+.. _`#2298`: https://github.com/apache/cloudstack/pull/2298
+.. _CLOUDSTACK-9620: https://issues.apache.org/jira/browse/CLOUDSTACK-9620
+.. _`#2396`: https://github.com/apache/cloudstack/pull/2396
+.. _CLOUDSTACK-10220: https://issues.apache.org/jira/browse/CLOUDSTACK-10220
+.. _`#2152`: https://github.com/apache/cloudstack/pull/2152
+.. _CLOUDSTACK-10229: https://issues.apache.org/jira/browse/CLOUDSTACK-10229
+.. _`#2097`: https://github.com/apache/cloudstack/pull/2097
+.. _CLOUDSTACK-9813: https://issues.apache.org/jira/browse/CLOUDSTACK-9813
+.. _`#2362`: https://github.com/apache/cloudstack/pull/2362
+.. _CLOUDSTACK-10188: https://issues.apache.org/jira/browse/CLOUDSTACK-10188
+.. _`#2146`: https://github.com/apache/cloudstack/pull/2146
+.. _CLOUDSTACK-4757: https://issues.apache.org/jira/browse/CLOUDSTACK-4757
+.. _`#2394`: https://github.com/apache/cloudstack/pull/2394
+.. _CLOUDSTACK-10109: https://issues.apache.org/jira/browse/CLOUDSTACK-10109
+.. _`#2393`: https://github.com/apache/cloudstack/pull/2393
+.. _CLOUDSTACK-10217: https://issues.apache.org/jira/browse/CLOUDSTACK-10217
+.. _`#2350`: https://github.com/apache/cloudstack/pull/2350
+.. _`#2388`: https://github.com/apache/cloudstack/pull/2388
+.. _CLOUDSTACK-10212: https://issues.apache.org/jira/browse/CLOUDSTACK-10212
+.. _`#2379`: https://github.com/apache/cloudstack/pull/2379
+.. _CLOUDSTACK-10146: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
+.. _`#2389`: https://github.com/apache/cloudstack/pull/2389
+.. _CLOUDSTACK-10213: https://issues.apache.org/jira/browse/CLOUDSTACK-10213
+.. _`#2391`: https://github.com/apache/cloudstack/pull/2391
+.. _CLOUDSTACK-10215: https://issues.apache.org/jira/browse/CLOUDSTACK-10215
+.. _`#2139`: https://github.com/apache/cloudstack/pull/2139
+.. _CLOUDSTACK-9921: https://issues.apache.org/jira/browse/CLOUDSTACK-9921
+.. _`#2088`: https://github.com/apache/cloudstack/pull/2088
+.. _CLOUDSTACK-9892: https://issues.apache.org/jira/browse/CLOUDSTACK-9892
+.. _`#2365`: https://github.com/apache/cloudstack/pull/2365
+.. _CLOUDSTACK-10197: https://issues.apache.org/jira/browse/CLOUDSTACK-10197
+.. _`#2073`: https://github.com/apache/cloudstack/pull/2073
+.. _CLOUDSTACK-9896: https://issues.apache.org/jira/browse/CLOUDSTACK-9896
+.. _`#2386`: https://github.com/apache/cloudstack/pull/2386
+.. _CLOUDSTACK-9632: https://issues.apache.org/jira/browse/CLOUDSTACK-9632
+.. _`#2295`: https://github.com/apache/cloudstack/pull/2295
+.. _`#2381`: https://github.com/apache/cloudstack/pull/2381
+.. _CLOUDSTACK-10117: https://issues.apache.org/jira/browse/CLOUDSTACK-10117
+.. _`#2315`: https://github.com/apache/cloudstack/pull/2315
+.. _CLOUDSTACK-9025: https://issues.apache.org/jira/browse/CLOUDSTACK-9025
+.. _`#2274`: https://github.com/apache/cloudstack/pull/2274
+.. _CLOUDSTACK-10096: https://issues.apache.org/jira/browse/CLOUDSTACK-10096
+.. _`#2282`: https://github.com/apache/cloudstack/pull/2282
+.. _CLOUDSTACK-10104: https://issues.apache.org/jira/browse/CLOUDSTACK-10104
+.. _`#2368`: https://github.com/apache/cloudstack/pull/2368
+.. _CLOUDSTACK-10126: https://issues.apache.org/jira/browse/CLOUDSTACK-10126
+.. _`#2385`: https://github.com/apache/cloudstack/pull/2385
+.. _CLOUDSTACK-10211: https://issues.apache.org/jira/browse/CLOUDSTACK-10211
+.. _`#2260`: https://github.com/apache/cloudstack/pull/2260
+.. _CLOUDSTACK-10065: https://issues.apache.org/jira/browse/CLOUDSTACK-10065
+.. _`#2292`: https://github.com/apache/cloudstack/pull/2292
+.. _CLOUDSTACK-10108: https://issues.apache.org/jira/browse/CLOUDSTACK-10108
+.. _`#1740`: https://github.com/apache/cloudstack/pull/1740
+.. _CLOUDSTACK-9572: https://issues.apache.org/jira/browse/CLOUDSTACK-9572
+.. _`#2104`: https://github.com/apache/cloudstack/pull/2104
+.. _CLOUDSTACK-9908: https://issues.apache.org/jira/browse/CLOUDSTACK-9908
+.. _`#2384`: https://github.com/apache/cloudstack/pull/2384
+.. _CLOUDSTACK-10210: https://issues.apache.org/jira/browse/CLOUDSTACK-10210
+.. _`#2378`: https://github.com/apache/cloudstack/pull/2378
+.. _CLOUDSTACK-10205: https://issues.apache.org/jira/browse/CLOUDSTACK-10205
+.. _`#2383`: https://github.com/apache/cloudstack/pull/2383
+.. _`#1773`: https://github.com/apache/cloudstack/pull/1773
+.. _CLOUDSTACK-9607: https://issues.apache.org/jira/browse/CLOUDSTACK-9607
+.. _`#2046`: https://github.com/apache/cloudstack/pull/2046
+.. _CLOUDSTACK-7958: https://issues.apache.org/jira/browse/CLOUDSTACK-7958
+.. _`#2149`: https://github.com/apache/cloudstack/pull/2149
+.. _CLOUDSTACK-9932: https://issues.apache.org/jira/browse/CLOUDSTACK-9932
+.. _`#2156`: https://github.com/apache/cloudstack/pull/2156
+.. _CLOUDSTACK-9971: https://issues.apache.org/jira/browse/CLOUDSTACK-9971
+.. _`#2374`: https://github.com/apache/cloudstack/pull/2374
+.. _CLOUDSTACK-10024: https://issues.apache.org/jira/browse/CLOUDSTACK-10024
+.. _`#2373`: https://github.com/apache/cloudstack/pull/2373
+.. _CLOUDSTACK-10202: https://issues.apache.org/jira/browse/CLOUDSTACK-10202
+.. _`#2344`: https://github.com/apache/cloudstack/pull/2344
+.. _CLOUDSTACK-10163: https://issues.apache.org/jira/browse/CLOUDSTACK-10163
+.. _`#2301`: https://github.com/apache/cloudstack/pull/2301
+.. _CLOUDSTACK-10121: https://issues.apache.org/jira/browse/CLOUDSTACK-10121
+.. _`#1554`: https://github.com/apache/cloudstack/pull/1554
+.. _CLOUDSTACK-9602: https://issues.apache.org/jira/browse/CLOUDSTACK-9602
+.. _`#1760`: https://github.com/apache/cloudstack/pull/1760
+.. _CLOUDSTACK-9593: https://issues.apache.org/jira/browse/CLOUDSTACK-9593
+.. _`#2035`: https://github.com/apache/cloudstack/pull/2035
+.. _CLOUDSTACK-9867: https://issues.apache.org/jira/browse/CLOUDSTACK-9867
+.. _`#2360`: https://github.com/apache/cloudstack/pull/2360
+.. _CLOUDSTACK-10189: https://issues.apache.org/jira/browse/CLOUDSTACK-10189
+.. _`#2352`: https://github.com/apache/cloudstack/pull/2352
+.. _CLOUDSTACK-10175: https://issues.apache.org/jira/browse/CLOUDSTACK-10175
+.. _`#2045`: https://github.com/apache/cloudstack/pull/2045
+.. _`#1934`: https://github.com/apache/cloudstack/pull/1934
+.. _CLOUDSTACK-9772: https://issues.apache.org/jira/browse/CLOUDSTACK-9772
+.. _`#2258`: https://github.com/apache/cloudstack/pull/2258
+.. _`#2347`: https://github.com/apache/cloudstack/pull/2347
+.. _CLOUDSTACK-10166: https://issues.apache.org/jira/browse/CLOUDSTACK-10166
+.. _`#2375`: https://github.com/apache/cloudstack/pull/2375
+.. _CLOUDSTACK-9456: https://issues.apache.org/jira/browse/CLOUDSTACK-9456
+.. _`#2211`: https://github.com/apache/cloudstack/pull/2211
+.. _CLOUDSTACK-10013: https://issues.apache.org/jira/browse/CLOUDSTACK-10013
+.. _`#1637`: https://github.com/apache/cloudstack/pull/1637
+.. _`#2304`: https://github.com/apache/cloudstack/pull/2304
+.. _CLOUDSTACK-10127: https://issues.apache.org/jira/browse/CLOUDSTACK-10127
+.. _`#2208`: https://github.com/apache/cloudstack/pull/2208
+.. _CLOUDSTACK-9542: https://issues.apache.org/jira/browse/CLOUDSTACK-9542
+.. _`#2351`: https://github.com/apache/cloudstack/pull/2351
+.. _CLOUDSTACK-10173: https://issues.apache.org/jira/browse/CLOUDSTACK-10173
+.. _`#2367`: https://github.com/apache/cloudstack/pull/2367
+.. _`#2370`: https://github.com/apache/cloudstack/pull/2370
+.. _CLOUDSTACK-9595: https://issues.apache.org/jira/browse/CLOUDSTACK-9595
+.. _`#2366`: https://github.com/apache/cloudstack/pull/2366
+.. _CLOUDSTACK-10168: https://issues.apache.org/jira/browse/CLOUDSTACK-10168
+.. _`#2371`: https://github.com/apache/cloudstack/pull/2371
+.. _`#2042`: https://github.com/apache/cloudstack/pull/2042
+.. _CLOUDSTACK-9875: https://issues.apache.org/jira/browse/CLOUDSTACK-9875
+.. _`#2281`: https://github.com/apache/cloudstack/pull/2281
+.. _CLOUDSTACK-10102: https://issues.apache.org/jira/browse/CLOUDSTACK-10102
+.. _`#2048`: https://github.com/apache/cloudstack/pull/2048
+.. _CLOUDSTACK-9880: https://issues.apache.org/jira/browse/CLOUDSTACK-9880
+.. _`#2364`: https://github.com/apache/cloudstack/pull/2364
+.. _CLOUDSTACK-10195: https://issues.apache.org/jira/browse/CLOUDSTACK-10195
+.. _`#2361`: https://github.com/apache/cloudstack/pull/2361
+.. _CLOUDSTACK-10190: https://issues.apache.org/jira/browse/CLOUDSTACK-10190
+.. _`#1437`: https://github.com/apache/cloudstack/pull/1437
+.. _`#2247`: https://github.com/apache/cloudstack/pull/2247
+.. _CLOUDSTACK-10012: https://issues.apache.org/jira/browse/CLOUDSTACK-10012
+.. _`#1964`: https://github.com/apache/cloudstack/pull/1964
+.. _CLOUDSTACK-9800: https://issues.apache.org/jira/browse/CLOUDSTACK-9800
+.. _`#1762`: https://github.com/apache/cloudstack/pull/1762
+.. _`#2348`: https://github.com/apache/cloudstack/pull/2348
+.. _CLOUDSTACK-10196: https://issues.apache.org/jira/browse/CLOUDSTACK-10196
+.. _`#2184`: https://github.com/apache/cloudstack/pull/2184
+.. _CLOUDSTACK-10003: https://issues.apache.org/jira/browse/CLOUDSTACK-10003
+.. _`#2308`: https://github.com/apache/cloudstack/pull/2308
+.. _CLOUDSTACK-8908: https://issues.apache.org/jira/browse/CLOUDSTACK-8908
+.. _`#2294`: https://github.com/apache/cloudstack/pull/2294
+.. _CLOUDSTACK-10039: https://issues.apache.org/jira/browse/CLOUDSTACK-10039
+.. _`#2346`: https://github.com/apache/cloudstack/pull/2346
+.. _`#2354`: https://github.com/apache/cloudstack/pull/2354
+.. _CLOUDSTACK-10176: https://issues.apache.org/jira/browse/CLOUDSTACK-10176
+.. _`#2353`: https://github.com/apache/cloudstack/pull/2353
+.. _CLOUDSTACK-9986: https://issues.apache.org/jira/browse/CLOUDSTACK-9986
+.. _`#2359`: https://github.com/apache/cloudstack/pull/2359
+.. _`#2356`: https://github.com/apache/cloudstack/pull/2356
+.. _CLOUDSTACK-8313: https://issues.apache.org/jira/browse/CLOUDSTACK-8313
+.. _`#2358`: https://github.com/apache/cloudstack/pull/2358
+.. _CLOUDSTACK-9736: https://issues.apache.org/jira/browse/CLOUDSTACK-9736
+.. _`#2326`: https://github.com/apache/cloudstack/pull/2326
+.. _CLOUDSTACK-10184: https://issues.apache.org/jira/browse/CLOUDSTACK-10184
+.. _`#2267`: https://github.com/apache/cloudstack/pull/2267
+.. _CLOUDSTACK-10077: https://issues.apache.org/jira/browse/CLOUDSTACK-10077
+.. _`#2337`: https://github.com/apache/cloudstack/pull/2337
+.. _CLOUDSTACK-10157: https://issues.apache.org/jira/browse/CLOUDSTACK-10157
+.. _`#2355`: https://github.com/apache/cloudstack/pull/2355
+.. _CLOUDSTACK-10177: https://issues.apache.org/jira/browse/CLOUDSTACK-10177
+.. _`#2349`: https://github.com/apache/cloudstack/pull/2349
+.. _CLOUDSTACK-10070: https://issues.apache.org/jira/browse/CLOUDSTACK-10070
+.. _`#2312`: https://github.com/apache/cloudstack/pull/2312
+.. _CLOUDSTACK-7793: https://issues.apache.org/jira/browse/CLOUDSTACK-7793
+.. _`#2345`: https://github.com/apache/cloudstack/pull/2345
+.. _CLOUDSTACK-10164: https://issues.apache.org/jira/browse/CLOUDSTACK-10164
+.. _`#2263`: https://github.com/apache/cloudstack/pull/2263
+.. _`#2342`: https://github.com/apache/cloudstack/pull/2342
+.. _CLOUDSTACK-9586: https://issues.apache.org/jira/browse/CLOUDSTACK-9586
+.. _`#2124`: https://github.com/apache/cloudstack/pull/2124
+.. _CLOUDSTACK-9432: https://issues.apache.org/jira/browse/CLOUDSTACK-9432
+.. _`#2322`: https://github.com/apache/cloudstack/pull/2322
+.. _CLOUDSTACK-10140: https://issues.apache.org/jira/browse/CLOUDSTACK-10140
+.. _`#2335`: https://github.com/apache/cloudstack/pull/2335
+.. _CLOUDSTACK-10154: https://issues.apache.org/jira/browse/CLOUDSTACK-10154
+.. _`#2341`: https://github.com/apache/cloudstack/pull/2341
+.. _CLOUDSTACK-10160: https://issues.apache.org/jira/browse/CLOUDSTACK-10160
+.. _`#2321`: https://github.com/apache/cloudstack/pull/2321
+.. _CLOUDSTACK-10138: https://issues.apache.org/jira/browse/CLOUDSTACK-10138
+.. _`#2334`: https://github.com/apache/cloudstack/pull/2334
+.. _CLOUDSTACK-10152: https://issues.apache.org/jira/browse/CLOUDSTACK-10152
+.. _`#2332`: https://github.com/apache/cloudstack/pull/2332
+.. _CLOUDSTACK-10156: https://issues.apache.org/jira/browse/CLOUDSTACK-10156
+.. _`#2028`: https://github.com/apache/cloudstack/pull/2028
+.. _CLOUDSTACK-9853: https://issues.apache.org/jira/browse/CLOUDSTACK-9853
+.. _`#2310`: https://github.com/apache/cloudstack/pull/2310
+.. _CLOUDSTACK-10133: https://issues.apache.org/jira/browse/CLOUDSTACK-10133
+.. _`#2219`: https://github.com/apache/cloudstack/pull/2219
+.. _CLOUDSTACK-9989: https://issues.apache.org/jira/browse/CLOUDSTACK-9989
+.. _`#2303`: https://github.com/apache/cloudstack/pull/2303
+.. _CLOUDSTACK-10123: https://issues.apache.org/jira/browse/CLOUDSTACK-10123
+.. _`#2329`: https://github.com/apache/cloudstack/pull/2329
+.. _`#1981`: https://github.com/apache/cloudstack/pull/1981
+.. _CLOUDSTACK-9806: https://issues.apache.org/jira/browse/CLOUDSTACK-9806
+.. _`#2324`: https://github.com/apache/cloudstack/pull/2324
+.. _`#2005`: https://github.com/apache/cloudstack/pull/2005
+.. _CLOUDSTACK-9450: https://issues.apache.org/jira/browse/CLOUDSTACK-9450
+.. _`#2327`: https://github.com/apache/cloudstack/pull/2327
+.. _CLOUDSTACK-10129: https://issues.apache.org/jira/browse/CLOUDSTACK-10129
+.. _`#2325`: https://github.com/apache/cloudstack/pull/2325
+.. _CLOUDSTACK-9998: https://issues.apache.org/jira/browse/CLOUDSTACK-9998
+.. _`#2313`: https://github.com/apache/cloudstack/pull/2313
+.. _CLOUDSTACK-10135: https://issues.apache.org/jira/browse/CLOUDSTACK-10135
+.. _`#2316`: https://github.com/apache/cloudstack/pull/2316
+.. _CLOUDSTACK-10137: https://issues.apache.org/jira/browse/CLOUDSTACK-10137
+.. _`#2157`: https://github.com/apache/cloudstack/pull/2157
+.. _CLOUDSTACK-9961: https://issues.apache.org/jira/browse/CLOUDSTACK-9961
+.. _`#1723`: https://github.com/apache/cloudstack/pull/1723
+.. _`#2306`: https://github.com/apache/cloudstack/pull/2306
+.. _`#2273`: https://github.com/apache/cloudstack/pull/2273
+.. _CLOUDSTACK-10090: https://issues.apache.org/jira/browse/CLOUDSTACK-10090
+.. _`#2242`: https://github.com/apache/cloudstack/pull/2242
+.. _CLOUDSTACK-9958: https://issues.apache.org/jira/browse/CLOUDSTACK-9958
+.. _`#2307`: https://github.com/apache/cloudstack/pull/2307
+.. _`#2240`: https://github.com/apache/cloudstack/pull/2240
+.. _CLOUDSTACK-10051: https://issues.apache.org/jira/browse/CLOUDSTACK-10051
+.. _`#2158`: https://github.com/apache/cloudstack/pull/2158
+.. _CLOUDSTACK-9972: https://issues.apache.org/jira/browse/CLOUDSTACK-9972
+.. _`#2291`: https://github.com/apache/cloudstack/pull/2291
+.. _CLOUDSTACK-10111: https://issues.apache.org/jira/browse/CLOUDSTACK-10111
+.. _`#2302`: https://github.com/apache/cloudstack/pull/2302
+.. _CLOUDSTACK-10122: https://issues.apache.org/jira/browse/CLOUDSTACK-10122
+.. _`#2004`: https://github.com/apache/cloudstack/pull/2004
+.. _CLOUDSTACK-9832: https://issues.apache.org/jira/browse/CLOUDSTACK-9832
+.. _`#2238`: https://github.com/apache/cloudstack/pull/2238
+.. _CLOUDSTACK-10053: https://issues.apache.org/jira/browse/CLOUDSTACK-10053
+.. _`#2250`: https://github.com/apache/cloudstack/pull/2250
+.. _CLOUDSTACK-10057: https://issues.apache.org/jira/browse/CLOUDSTACK-10057
+.. _`#2268`: https://github.com/apache/cloudstack/pull/2268
+.. _CLOUDSTACK-10081: https://issues.apache.org/jira/browse/CLOUDSTACK-10081
+.. _`#2293`: https://github.com/apache/cloudstack/pull/2293
+.. _CLOUDSTACK-10047: https://issues.apache.org/jira/browse/CLOUDSTACK-10047
+.. _`#2284`: https://github.com/apache/cloudstack/pull/2284
+.. _CLOUDSTACK-10103: https://issues.apache.org/jira/browse/CLOUDSTACK-10103
+.. _`#2288`: https://github.com/apache/cloudstack/pull/2288
+.. _CLOUDSTACK-10107: https://issues.apache.org/jira/browse/CLOUDSTACK-10107
+.. _`#2297`: https://github.com/apache/cloudstack/pull/2297
+.. _CLOUDSTACK-9957: https://issues.apache.org/jira/browse/CLOUDSTACK-9957
+.. _`#2296`: https://github.com/apache/cloudstack/pull/2296
+.. _CLOUDSTACK-10007: https://issues.apache.org/jira/browse/CLOUDSTACK-10007
+.. _`#2181`: https://github.com/apache/cloudstack/pull/2181
+.. _`#2257`: https://github.com/apache/cloudstack/pull/2257
+.. _CLOUDSTACK-10060: https://issues.apache.org/jira/browse/CLOUDSTACK-10060
+.. _`#2286`: https://github.com/apache/cloudstack/pull/2286
+.. _CLOUDSTACK-9993: https://issues.apache.org/jira/browse/CLOUDSTACK-9993
+.. _`#2287`: https://github.com/apache/cloudstack/pull/2287
+.. _`#2246`: https://github.com/apache/cloudstack/pull/2246
+.. _CLOUDSTACK-10046: https://issues.apache.org/jira/browse/CLOUDSTACK-10046
+.. _`#2074`: https://github.com/apache/cloudstack/pull/2074
+.. _CLOUDSTACK-9899: https://issues.apache.org/jira/browse/CLOUDSTACK-9899
+.. _`#2280`: https://github.com/apache/cloudstack/pull/2280
+.. _CLOUDSTACK-10101: https://issues.apache.org/jira/browse/CLOUDSTACK-10101
+.. _`#2285`: https://github.com/apache/cloudstack/pull/2285
+.. _CLOUDSTACK-9859: https://issues.apache.org/jira/browse/CLOUDSTACK-9859
+.. _`#2278`: https://github.com/apache/cloudstack/pull/2278
+.. _`#2279`: https://github.com/apache/cloudstack/pull/2279
+.. _CLOUDSTACK-9584: https://issues.apache.org/jira/browse/CLOUDSTACK-9584
+.. _`#2277`: https://github.com/apache/cloudstack/pull/2277
+.. _CLOUDSTACK-10099: https://issues.apache.org/jira/browse/CLOUDSTACK-10099
+.. _`#2266`: https://github.com/apache/cloudstack/pull/2266
+.. _CLOUDSTACK-10073: https://issues.apache.org/jira/browse/CLOUDSTACK-10073
+.. _`#2249`: https://github.com/apache/cloudstack/pull/2249
+.. _`#1707`: https://github.com/apache/cloudstack/pull/1707
+.. _CLOUDSTACK-9397: https://issues.apache.org/jira/browse/CLOUDSTACK-9397
+.. _`#2269`: https://github.com/apache/cloudstack/pull/2269
+.. _CLOUDSTACK-10083: https://issues.apache.org/jira/browse/CLOUDSTACK-10083
+.. _`#876`: https://github.com/apache/cloudstack/pull/876
+.. _CLOUDSTACK-8865: https://issues.apache.org/jira/browse/CLOUDSTACK-8865
+.. _`#1252`: https://github.com/apache/cloudstack/pull/1252
+.. _CLOUDSTACK-9182: https://issues.apache.org/jira/browse/CLOUDSTACK-9182
+.. _`#2153`: https://github.com/apache/cloudstack/pull/2153
+.. _CLOUDSTACK-9956: https://issues.apache.org/jira/browse/CLOUDSTACK-9956
+.. _`#2078`: https://github.com/apache/cloudstack/pull/2078
+.. _CLOUDSTACK-9902: https://issues.apache.org/jira/browse/CLOUDSTACK-9902
+.. _`#2252`: https://github.com/apache/cloudstack/pull/2252
+.. _CLOUDSTACK-10067: https://issues.apache.org/jira/browse/CLOUDSTACK-10067
+.. _`#2143`: https://github.com/apache/cloudstack/pull/2143
+.. _CLOUDSTACK-9949: https://issues.apache.org/jira/browse/CLOUDSTACK-9949
+.. _`#2248`: https://github.com/apache/cloudstack/pull/2248
+.. _CLOUDSTACK-10056: https://issues.apache.org/jira/browse/CLOUDSTACK-10056
+.. _`#2243`: https://github.com/apache/cloudstack/pull/2243
+.. _CLOUDSTACK-10019: https://issues.apache.org/jira/browse/CLOUDSTACK-10019
+.. _`#2261`: https://github.com/apache/cloudstack/pull/2261
+.. _CLOUDSTACK-10068: https://issues.apache.org/jira/browse/CLOUDSTACK-10068
+.. _`#2054`: https://github.com/apache/cloudstack/pull/2054
+.. _CLOUDSTACK-9886: https://issues.apache.org/jira/browse/CLOUDSTACK-9886
+.. _`#955`: https://github.com/apache/cloudstack/pull/955
+.. _CLOUDSTACK-8969: https://issues.apache.org/jira/browse/CLOUDSTACK-8969
+.. _`#2262`: https://github.com/apache/cloudstack/pull/2262
+.. _CLOUDSTACK-10069: https://issues.apache.org/jira/browse/CLOUDSTACK-10069
+.. _`#2256`: https://github.com/apache/cloudstack/pull/2256
+.. _CLOUDSTACK-9782: https://issues.apache.org/jira/browse/CLOUDSTACK-9782
+.. _`#2253`: https://github.com/apache/cloudstack/pull/2253
+.. _CLOUDSTACK-10061: https://issues.apache.org/jira/browse/CLOUDSTACK-10061
+.. _`#2254`: https://github.com/apache/cloudstack/pull/2254
+.. _CLOUDSTACK-10058: https://issues.apache.org/jira/browse/CLOUDSTACK-10058
+.. _`#1733`: https://github.com/apache/cloudstack/pull/1733
+.. _CLOUDSTACK-9563: https://issues.apache.org/jira/browse/CLOUDSTACK-9563
+.. _`#2188`: https://github.com/apache/cloudstack/pull/2188
+.. _CLOUDSTACK-10004: https://issues.apache.org/jira/browse/CLOUDSTACK-10004
+.. _`#914`: https://github.com/apache/cloudstack/pull/914
+.. _CLOUDSTACK-8939: https://issues.apache.org/jira/browse/CLOUDSTACK-8939
+.. _`#1985`: https://github.com/apache/cloudstack/pull/1985
+.. _CLOUDSTACK-9812: https://issues.apache.org/jira/browse/CLOUDSTACK-9812
+.. _`#2224`: https://github.com/apache/cloudstack/pull/2224
+.. _CLOUDSTACK-10032: https://issues.apache.org/jira/browse/CLOUDSTACK-10032
+.. _`#1443`: https://github.com/apache/cloudstack/pull/1443
+.. _CLOUDSTACK-9314: https://issues.apache.org/jira/browse/CLOUDSTACK-9314
+.. _`#2109`: https://github.com/apache/cloudstack/pull/2109
+.. _CLOUDSTACK-9922: https://issues.apache.org/jira/browse/CLOUDSTACK-9922
+.. _`#2216`: https://github.com/apache/cloudstack/pull/2216
+.. _CLOUDSTACK-10027: https://issues.apache.org/jira/browse/CLOUDSTACK-10027
+.. _`#2245`: https://github.com/apache/cloudstack/pull/2245
+.. _`#2239`: https://github.com/apache/cloudstack/pull/2239
+.. _`#2044`: https://github.com/apache/cloudstack/pull/2044
+.. _CLOUDSTACK-9877: https://issues.apache.org/jira/browse/CLOUDSTACK-9877
+.. _`#2174`: https://github.com/apache/cloudstack/pull/2174
+.. _CLOUDSTACK-9996: https://issues.apache.org/jira/browse/CLOUDSTACK-9996
+.. _`#2101`: https://github.com/apache/cloudstack/pull/2101
+.. _CLOUDSTACK-9915: https://issues.apache.org/jira/browse/CLOUDSTACK-9915
+.. _`#2123`: https://github.com/apache/cloudstack/pull/2123
+.. _CLOUDSTACK-9914: https://issues.apache.org/jira/browse/CLOUDSTACK-9914
+.. _`#2186`: https://github.com/apache/cloudstack/pull/2186
+.. _CLOUDSTACK-10002: https://issues.apache.org/jira/browse/CLOUDSTACK-10002
+.. _`#1246`: https://github.com/apache/cloudstack/pull/1246
+.. _CLOUDSTACK-9165: https://issues.apache.org/jira/browse/CLOUDSTACK-9165
+.. _`#2241`: https://github.com/apache/cloudstack/pull/2241
+.. _CLOUDSTACK-10052: https://issues.apache.org/jira/browse/CLOUDSTACK-10052
+.. _`#2222`: https://github.com/apache/cloudstack/pull/2222
+.. _CLOUDSTACK-10022: https://issues.apache.org/jira/browse/CLOUDSTACK-10022
+.. _`#2221`: https://github.com/apache/cloudstack/pull/2221
+.. _CLOUDSTACK-10030: https://issues.apache.org/jira/browse/CLOUDSTACK-10030
+.. _`#2154`: https://github.com/apache/cloudstack/pull/2154
+.. _CLOUDSTACK-9967: https://issues.apache.org/jira/browse/CLOUDSTACK-9967
+.. _`#1878`: https://github.com/apache/cloudstack/pull/1878
+.. _CLOUDSTACK-9717: https://issues.apache.org/jira/browse/CLOUDSTACK-9717
+.. _`#2013`: https://github.com/apache/cloudstack/pull/2013
+.. _CLOUDSTACK-9734: https://issues.apache.org/jira/browse/CLOUDSTACK-9734
+.. _`#2159`: https://github.com/apache/cloudstack/pull/2159
+.. _CLOUDSTACK-9964: https://issues.apache.org/jira/browse/CLOUDSTACK-9964
+.. _`#2163`: https://github.com/apache/cloudstack/pull/2163
+.. _CLOUDSTACK-9939: https://issues.apache.org/jira/browse/CLOUDSTACK-9939
+.. _`#1919`: https://github.com/apache/cloudstack/pull/1919
+.. _CLOUDSTACK-9763: https://issues.apache.org/jira/browse/CLOUDSTACK-9763
+.. _`#1936`: https://github.com/apache/cloudstack/pull/1936
+.. _CLOUDSTACK-9773: https://issues.apache.org/jira/browse/CLOUDSTACK-9773
+.. _`#2223`: https://github.com/apache/cloudstack/pull/2223
+.. _CLOUDSTACK-10031: https://issues.apache.org/jira/browse/CLOUDSTACK-10031
+.. _`#2215`: https://github.com/apache/cloudstack/pull/2215
+.. _CLOUDSTACK-10026: https://issues.apache.org/jira/browse/CLOUDSTACK-10026
+.. _`#2180`: https://github.com/apache/cloudstack/pull/2180
+.. _CLOUDSTACK-9999: https://issues.apache.org/jira/browse/CLOUDSTACK-9999
+.. _`#2236`: https://github.com/apache/cloudstack/pull/2236
+.. _CLOUDSTACK-10044: https://issues.apache.org/jira/browse/CLOUDSTACK-10044
+.. _`#2235`: https://github.com/apache/cloudstack/pull/2235
+.. _`#2182`: https://github.com/apache/cloudstack/pull/2182
+.. _CLOUDSTACK-10000: https://issues.apache.org/jira/browse/CLOUDSTACK-10000
+.. _`#2233`: https://github.com/apache/cloudstack/pull/2233
+.. _CLOUDSTACK-10042: https://issues.apache.org/jira/browse/CLOUDSTACK-10042
+.. _`#2228`: https://github.com/apache/cloudstack/pull/2228
+.. _CLOUDSTACK-10036: https://issues.apache.org/jira/browse/CLOUDSTACK-10036
+.. _`#2026`: https://github.com/apache/cloudstack/pull/2026
+.. _CLOUDSTACK-9861: https://issues.apache.org/jira/browse/CLOUDSTACK-9861
+.. _`#1774`: https://github.com/apache/cloudstack/pull/1774
+.. _CLOUDSTACK-9608: https://issues.apache.org/jira/browse/CLOUDSTACK-9608
+.. _`#2039`: https://github.com/apache/cloudstack/pull/2039
+.. _`#2144`: https://github.com/apache/cloudstack/pull/2144
+.. _CLOUDSTACK-9955: https://issues.apache.org/jira/browse/CLOUDSTACK-9955
+.. _`#1966`: https://github.com/apache/cloudstack/pull/1966
+.. _CLOUDSTACK-9801: https://issues.apache.org/jira/browse/CLOUDSTACK-9801
+.. _`#2220`: https://github.com/apache/cloudstack/pull/2220
+.. _CLOUDSTACK-9708: https://issues.apache.org/jira/browse/CLOUDSTACK-9708
+.. _`#1912`: https://github.com/apache/cloudstack/pull/1912
+.. _CLOUDSTACK-9749: https://issues.apache.org/jira/browse/CLOUDSTACK-9749
+.. _`#2138`: https://github.com/apache/cloudstack/pull/2138
+.. _CLOUDSTACK-9944: https://issues.apache.org/jira/browse/CLOUDSTACK-9944
+.. _`#2193`: https://github.com/apache/cloudstack/pull/2193
+.. _`#2218`: https://github.com/apache/cloudstack/pull/2218
+.. _`#883`: https://github.com/apache/cloudstack/pull/883
+.. _CLOUDSTACK-8906: https://issues.apache.org/jira/browse/CLOUDSTACK-8906
+.. _`#2119`: https://github.com/apache/cloudstack/pull/2119
+.. _CLOUDSTACK-9925: https://issues.apache.org/jira/browse/CLOUDSTACK-9925
+.. _`#2145`: https://github.com/apache/cloudstack/pull/2145
+.. _CLOUDSTACK-9697: https://issues.apache.org/jira/browse/CLOUDSTACK-9697
+.. _`#2137`: https://github.com/apache/cloudstack/pull/2137
+.. _CLOUDSTACK-9950: https://issues.apache.org/jira/browse/CLOUDSTACK-9950
+.. _`#2008`: https://github.com/apache/cloudstack/pull/2008
+.. _CLOUDSTACK-9840: https://issues.apache.org/jira/browse/CLOUDSTACK-9840
+.. _`#2094`: https://github.com/apache/cloudstack/pull/2094
+.. _`#2142`: https://github.com/apache/cloudstack/pull/2142
+.. _CLOUDSTACK-9954: https://issues.apache.org/jira/browse/CLOUDSTACK-9954
+.. _`#2130`: https://github.com/apache/cloudstack/pull/2130
+.. _CLOUDSTACK-8961: https://issues.apache.org/jira/browse/CLOUDSTACK-8961
+.. _`#2212`: https://github.com/apache/cloudstack/pull/2212
+.. _`#2171`: https://github.com/apache/cloudstack/pull/2171
+.. _CLOUDSTACK-9990: https://issues.apache.org/jira/browse/CLOUDSTACK-9990
+.. _`#2205`: https://github.com/apache/cloudstack/pull/2205
+.. _`#1925`: https://github.com/apache/cloudstack/pull/1925
+.. _CLOUDSTACK-9751: https://issues.apache.org/jira/browse/CLOUDSTACK-9751
+.. _`#1798`: https://github.com/apache/cloudstack/pull/1798
+.. _CLOUDSTACK-9631: https://issues.apache.org/jira/browse/CLOUDSTACK-9631
+.. _`#2201`: https://github.com/apache/cloudstack/pull/2201
+.. _CLOUDSTACK-10016: https://issues.apache.org/jira/browse/CLOUDSTACK-10016
+.. _`#1784`: https://github.com/apache/cloudstack/pull/1784
+.. _`#2200`: https://github.com/apache/cloudstack/pull/2200
+.. _CLOUDSTACK-10015: https://issues.apache.org/jira/browse/CLOUDSTACK-10015
+.. _`#1655`: https://github.com/apache/cloudstack/pull/1655
+.. _`#1959`: https://github.com/apache/cloudstack/pull/1959
+.. _CLOUDSTACK-9786: https://issues.apache.org/jira/browse/CLOUDSTACK-9786
+.. _`#1933`: https://github.com/apache/cloudstack/pull/1933
+.. _CLOUDSTACK-9569: https://issues.apache.org/jira/browse/CLOUDSTACK-9569
+.. _`#2175`: https://github.com/apache/cloudstack/pull/2175
+.. _`#2176`: https://github.com/apache/cloudstack/pull/2176
diff --git a/source/releasenotes/index.rst b/source/releasenotes/index.rst
new file mode 100644
index 0000000..e39e62f
--- /dev/null
+++ b/source/releasenotes/index.rst
@@ -0,0 +1,65 @@
+.. 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 Release Notes documentation master file, created by
+ sphinx-quickstart on Fri Feb 7 16:00:59 2014.
+ You can adapt this file completely to your liking, but it should at least
+ contain the root `toctree` directive.
+
+|menu_acs_logo|
+
+
+Release Notes
+=============
+
+
+This document contains information specific to this release of CloudStack,
+including upgrade instructions from prior releases, new features added to
+CloudStack, API changes, and issues fixed in the release. For installation
+instructions, please see the `CloudStack Installation Guide`_. For usage and
+administration instructions, please see the `CloudStack Administrator's Guide`_.
+
+
+Contents:
+
+.. toctree::
+ :maxdepth: 2
+
+ about
+
+
+.. toctree::
+ :maxdepth: 2
+
+ fixed_issues
+
+
+.. toctree::
+ :maxdepth: 2
+
+ compat
+
+
+.. toctree::
+ :maxdepth: 2
+
+ api-changes
+
+
+.. toctree::
+ :maxdepth: 2
+
+ known_issues
+
diff --git a/source/releasenotes/known_issues.rst b/source/releasenotes/known_issues.rst
new file mode 100644
index 0000000..c832bbc
--- /dev/null
+++ b/source/releasenotes/known_issues.rst
@@ -0,0 +1,363 @@
+.. 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.
+
+Known Issues in |version|
+=========================
+
+Apache CloudStack uses `Jira
+<https://issues.apache.org/jira/browse/CLOUDSTACK>`_ to track its issues. All
+new features and bugs for |version| have been tracked in Jira, and have a
+standard naming convention of "CLOUDSTACK-NNNN" where "NNNN" is the issue
+number.
+
+For the list of known issues, see `Known Issues in
+<https://issues.apache.org/jira/issues/?filter=12338176>`_ |version|.
+
+.. cssclass:: table-striped table-bordered table-hover
+
+========================================================================== ===================================================================================
+Bug ID Description
+========================================================================== ===================================================================================
+`CLOUDSTACK-8862 <https://issues.apache.org/jira/browse/CLOUDSTACK-8862>`_ Issuing multiple attach-volume commands simultaneously can be problematic...
+`CLOUDSTACK-9734 <https://issues.apache.org/jira/browse/CLOUDSTACK-9734>`_ VM Expunge Fails sometimes...
+`CLOUDSTACK-9712 <https://issues.apache.org/jira/browse/CLOUDSTACK-9712>`_ Establishing Remote access VPN is failing due to mismatch of preshared secrets ...
+`CLOUDSTACK-9363 <https://issues.apache.org/jira/browse/CLOUDSTACK-9363>`_ Can't start a Xen HVM vm when more than 2 volumes attached...
+`CLOUDSTACK-9692 <https://issues.apache.org/jira/browse/CLOUDSTACK-9692>`_ Reset password service is not running on Redundant virtual routers....
+`CLOUDSTACK-9653 <https://issues.apache.org/jira/browse/CLOUDSTACK-9653>`_ listCapacity API shows incorrect output when sortBy=usage option is added...
+`CLOUDSTACK-9675 <https://issues.apache.org/jira/browse/CLOUDSTACK-9675>`_ Cloudstack Metrics: Miscellaneous bug fixes...
+`CLOUDSTACK-9727 <https://issues.apache.org/jira/browse/CLOUDSTACK-9727>`_ Password reset discrepancy in RVR when one of the Router is not in Running state...
+`CLOUDSTACK-9726 <https://issues.apache.org/jira/browse/CLOUDSTACK-9726>`_ state of the rvr dose not change to update failed when updating rvrs in sequence...
+`CLOUDSTACK-9668 <https://issues.apache.org/jira/browse/CLOUDSTACK-9668>`_ disksizeallocated of PrimaryStorage is different from the total size of a volume...
+`CLOUDSTACK-9694 <https://issues.apache.org/jira/browse/CLOUDSTACK-9694>`_ Unable to limit the Public IPs in VPC...
+`CLOUDSTACK-9716 <https://issues.apache.org/jira/browse/CLOUDSTACK-9716>`_ baremetal:rvr:vm deployment gets stuck in starting state (waiting for notificati...
+`CLOUDSTACK-9701 <https://issues.apache.org/jira/browse/CLOUDSTACK-9701>`_ When host is disabled/removed, capacity_state for local storage in op_host_capac...
+`CLOUDSTACK-9569 <https://issues.apache.org/jira/browse/CLOUDSTACK-9569>`_ VR on shared network not starting on KVM...
+`CLOUDSTACK-8284 <https://issues.apache.org/jira/browse/CLOUDSTACK-8284>`_ Primary_storage vlaue is not updating in resource_count table after VM deletion...
+`CLOUDSTACK-9697 <https://issues.apache.org/jira/browse/CLOUDSTACK-9697>`_ Better error message user if tries to shrink the VM ROOT volume size...
+`CLOUDSTACK-9693 <https://issues.apache.org/jira/browse/CLOUDSTACK-9693>`_ Cluster status of an unmanaged cluster still shows enabled...
+`CLOUDSTACK-9687 <https://issues.apache.org/jira/browse/CLOUDSTACK-9687>`_ disksizeallocated of PrimaryStorage is different from the total size of a volume...
+`CLOUDSTACK-9560 <https://issues.apache.org/jira/browse/CLOUDSTACK-9560>`_ Root volume of deleted VM left unremoved...
+`CLOUDSTACK-9559 <https://issues.apache.org/jira/browse/CLOUDSTACK-9559>`_ Deleting zone without deleting the secondary storage under the zone should not b...
+`CLOUDSTACK-8896 <https://issues.apache.org/jira/browse/CLOUDSTACK-8896>`_ Allocated percentage of storage can go beyond 100%...
+`CLOUDSTACK-9664 <https://issues.apache.org/jira/browse/CLOUDSTACK-9664>`_ updateRole: type can not be changed...
+`CLOUDSTACK-9672 <https://issues.apache.org/jira/browse/CLOUDSTACK-9672>`_ MySQL HA doesn't work...
+`CLOUDSTACK-9667 <https://issues.apache.org/jira/browse/CLOUDSTACK-9667>`_ Enable resourcecount.check.interval by default...
+`CLOUDSTACK-9666 <https://issues.apache.org/jira/browse/CLOUDSTACK-9666>`_ Add configuration validation for the config drive global settings...
+`CLOUDSTACK-9665 <https://issues.apache.org/jira/browse/CLOUDSTACK-9665>`_ List hosts api dose not report correct cpu and memory usage...
+`CLOUDSTACK-9628 <https://issues.apache.org/jira/browse/CLOUDSTACK-9628>`_ Fix Template Size in Swift as Secondary Storage...
+`CLOUDSTACK-9626 <https://issues.apache.org/jira/browse/CLOUDSTACK-9626>`_ Instance fails to start after unsuccesful compute offering upgrade....
+`CLOUDSTACK-9647 <https://issues.apache.org/jira/browse/CLOUDSTACK-9647>`_ NIC adapter type becomes e1000 , even after changing the global parameter "vmwar...
+`CLOUDSTACK-9500 <https://issues.apache.org/jira/browse/CLOUDSTACK-9500>`_ VR configuration not clean properly after Public IP release...
+`CLOUDSTACK-9175 <https://issues.apache.org/jira/browse/CLOUDSTACK-9175>`_ [VMware DRS] Adding new host to DRS cluster does not participate in load balanci...
+`CLOUDSTACK-9651 <https://issues.apache.org/jira/browse/CLOUDSTACK-9651>`_ Fix Docker image build of simulator, marvin and management-server....
+`CLOUDSTACK-9589 <https://issues.apache.org/jira/browse/CLOUDSTACK-9589>`_ vmName entries from host_details table for the VM's whose state is Expunging sho...
+`CLOUDSTACK-8849 <https://issues.apache.org/jira/browse/CLOUDSTACK-8849>`_ Usage job should stop usage generation in case of any exception...
+`CLOUDSTACK-9558 <https://issues.apache.org/jira/browse/CLOUDSTACK-9558>`_ Cleanup the snapshots on the primary storage of Xenserver after VM/Volume is exp...
+`CLOUDSTACK-9637 <https://issues.apache.org/jira/browse/CLOUDSTACK-9637>`_ Template create from snapshot does not populate vm_template_details...
+`CLOUDSTACK-9627 <https://issues.apache.org/jira/browse/CLOUDSTACK-9627>`_ Template Doens't get sync when using Swift as Secondary Storage...
+`CLOUDSTACK-9546 <https://issues.apache.org/jira/browse/CLOUDSTACK-9546>`_ X-Forwarded-For Headers Not Applied for HTTP Traffic in haproxy...
+`CLOUDSTACK-9586 <https://issues.apache.org/jira/browse/CLOUDSTACK-9586>`_ When using local storage with Xenserver prepareTemplate does not work with multi...
+`CLOUDSTACK-9635 <https://issues.apache.org/jira/browse/CLOUDSTACK-9635>`_ fix test_privategw_acl.py...
+`CLOUDSTACK-8939 <https://issues.apache.org/jira/browse/CLOUDSTACK-8939>`_ VM Snapshot size with memory is not correctly calculated in cloud.usage_event (X...
+`CLOUDSTACK-9182 <https://issues.apache.org/jira/browse/CLOUDSTACK-9182>`_ Some running VMs turned off on manual migration when auto migration failed while...
+`CLOUDSTACK-9638 <https://issues.apache.org/jira/browse/CLOUDSTACK-9638>`_ Problems caused when inputting double-byte numbers for custom compute offerings...
+`CLOUDSTACK-9640 <https://issues.apache.org/jira/browse/CLOUDSTACK-9640>`_ In KVM SSVM and CPVM may use the old cmdline data, if we fail to fetch the new c...
+`CLOUDSTACK-9641 <https://issues.apache.org/jira/browse/CLOUDSTACK-9641>`_ In KVM SSVM and CPVM may use the old cmdline data, if we fail to fetch the new c...
+`CLOUDSTACK-9642 <https://issues.apache.org/jira/browse/CLOUDSTACK-9642>`_ API documentation: getVirtualMachineUserData is in the wrong command category 'U...
+`CLOUDSTACK-9634 <https://issues.apache.org/jira/browse/CLOUDSTACK-9634>`_ fix marvin test test_router_dhcp_opts failure...
+`CLOUDSTACK-9184 <https://issues.apache.org/jira/browse/CLOUDSTACK-9184>`_ [VMware] vmware.ports.per.dvportgroup global setting is not useful from vCenter ...
+`CLOUDSTACK-9595 <https://issues.apache.org/jira/browse/CLOUDSTACK-9595>`_ Transactions are not getting retried in case of database deadlock errors...
+`CLOUDSTACK-9538 <https://issues.apache.org/jira/browse/CLOUDSTACK-9538>`_ Deleting Snapshot From Primary Storage Fails on RBD Storage if you already delet...
+`CLOUDSTACK-9317 <https://issues.apache.org/jira/browse/CLOUDSTACK-9317>`_ Disabling static NAT on many IPs can leave wrong IPs on the router...
+`CLOUDSTACK-9593 <https://issues.apache.org/jira/browse/CLOUDSTACK-9593>`_ User data check is inconsistent with python...
+`CLOUDSTACK-9598 <https://issues.apache.org/jira/browse/CLOUDSTACK-9598>`_ wrong defaut gateway in guest VM with nics in isolated and a shared network...
+`CLOUDSTACK-9614 <https://issues.apache.org/jira/browse/CLOUDSTACK-9614>`_ Attaching Volume to VM incorrectly checks resource limits...
+`CLOUDSTACK-9572 <https://issues.apache.org/jira/browse/CLOUDSTACK-9572>`_ Snapshot on primary storage not cleaned up after Storage migration...
+`CLOUDSTACK-9280 <https://issues.apache.org/jira/browse/CLOUDSTACK-9280>`_ System VM volumes cannot be deleted when there are no system VMs...
+`CLOUDSTACK-8781 <https://issues.apache.org/jira/browse/CLOUDSTACK-8781>`_ Superfluous field during VPC creation...
+`CLOUDSTACK-9498 <https://issues.apache.org/jira/browse/CLOUDSTACK-9498>`_ VR CsFile search utility methods fail when search string has char...
+`CLOUDSTACK-9503 <https://issues.apache.org/jira/browse/CLOUDSTACK-9503>`_ The router script times out resulting in failure of deployment...
+`CLOUDSTACK-9356 <https://issues.apache.org/jira/browse/CLOUDSTACK-9356>`_ VPC add VPN User fails same error as CLOUDSTACK-8927...
+`CLOUDSTACK-9017 <https://issues.apache.org/jira/browse/CLOUDSTACK-9017>`_ VPC VR DHCP broken for multihomed guest VMs...
+`CLOUDSTACK-9585 <https://issues.apache.org/jira/browse/CLOUDSTACK-9585>`_ UI doesn't give an option to select the xentools version for non ROOT users...
+`CLOUDSTACK-9417 <https://issues.apache.org/jira/browse/CLOUDSTACK-9417>`_ Usage module refactoring...
+`CLOUDSTACK-9555 <https://issues.apache.org/jira/browse/CLOUDSTACK-9555>`_ when a template is deleted and then copied over again , it is still marked as Re...
+`CLOUDSTACK-9592 <https://issues.apache.org/jira/browse/CLOUDSTACK-9592>`_ Empty responses from site to site connection status are not handled propertly...
+`CLOUDSTACK-9601 <https://issues.apache.org/jira/browse/CLOUDSTACK-9601>`_ Database upgrade algorithm is incorrect...
+`CLOUDSTACK-9596 <https://issues.apache.org/jira/browse/CLOUDSTACK-9596>`_ migrateVirtualMachine API does not respect affinity group assignment...
+`CLOUDSTACK-9578 <https://issues.apache.org/jira/browse/CLOUDSTACK-9578>`_ 6 out of 12 internal Lb rules were added to internal LB with same source ip duri...
+`CLOUDSTACK-9557 <https://issues.apache.org/jira/browse/CLOUDSTACK-9557>`_ Deploy from VMsnapshot fails with exception if source template is removed or mad...
+`CLOUDSTACK-9370 <https://issues.apache.org/jira/browse/CLOUDSTACK-9370>`_ Failed to create VPC: Unable to start VPC VR (VM DomainRouter) due to error in ...
+`CLOUDSTACK-9591 <https://issues.apache.org/jira/browse/CLOUDSTACK-9591>`_ VMware dvSwitch Requires a Dummy, Standard vSwitch...
+`CLOUDSTACK-9405 <https://issues.apache.org/jira/browse/CLOUDSTACK-9405>`_ listDomains API call takes an extremely long time to respond...
+`CLOUDSTACK-8288 <https://issues.apache.org/jira/browse/CLOUDSTACK-8288>`_ Deleting Instance deletes unrelated snapshots...
+`CLOUDSTACK-9577 <https://issues.apache.org/jira/browse/CLOUDSTACK-9577>`_ NPE whle deleting internal LB rules concurrently...
+`CLOUDSTACK-9579 <https://issues.apache.org/jira/browse/CLOUDSTACK-9579>`_ Internal lb vm display page stuck in loading not showing any vms...
+`CLOUDSTACK-9580 <https://issues.apache.org/jira/browse/CLOUDSTACK-9580>`_ Unexpected exception while deleting vms concurrently...
+`CLOUDSTACK-9581 <https://issues.apache.org/jira/browse/CLOUDSTACK-9581>`_ Error in logs while concurrently creating 100 vms...
+`CLOUDSTACK-9582 <https://issues.apache.org/jira/browse/CLOUDSTACK-9582>`_ Null pointer exceptions while deleting network concurrently...
+`CLOUDSTACK-9576 <https://issues.apache.org/jira/browse/CLOUDSTACK-9576>`_ Nuage VSP Plugin : NPE while creating vpctier with wrong domain template name...
+`CLOUDSTACK-9552 <https://issues.apache.org/jira/browse/CLOUDSTACK-9552>`_ KVM Security Groups do not allow DNS over TCP egress...
+`CLOUDSTACK-9575 <https://issues.apache.org/jira/browse/CLOUDSTACK-9575>`_ ACS 4.9 + VMware/ESXi 6.0: Sometimes VRs are failing to fully come up into runni...
+`CLOUDSTACK-9226 <https://issues.apache.org/jira/browse/CLOUDSTACK-9226>`_ Wrong number of sockets reported...
+`CLOUDSTACK-9553 <https://issues.apache.org/jira/browse/CLOUDSTACK-9553>`_ Usage event is not getting recorded for snapshots in a specific scenario...
+`CLOUDSTACK-9554 <https://issues.apache.org/jira/browse/CLOUDSTACK-9554>`_ Juniper Contrail plug-in is publishing events to wrong message bus...
+`CLOUDSTACK-9551 <https://issues.apache.org/jira/browse/CLOUDSTACK-9551>`_ Pull KVM agent's tmp folder usage within its own folder structure...
+`CLOUDSTACK-9571 <https://issues.apache.org/jira/browse/CLOUDSTACK-9571>`_ Management server should fence itself when there are recoverable DB errors OR wh...
+`CLOUDSTACK-7827 <https://issues.apache.org/jira/browse/CLOUDSTACK-7827>`_ storage migration timeout, loss of data...
+`CLOUDSTACK-9514 <https://issues.apache.org/jira/browse/CLOUDSTACK-9514>`_ MarvinTests: some host credentials are hardcoded, make them to be picked up from...
+`CLOUDSTACK-9533 <https://issues.apache.org/jira/browse/CLOUDSTACK-9533>`_ gateway of public IP is not handled correctly when parsing the cmd_line.json to ...
+`CLOUDSTACK-9529 <https://issues.apache.org/jira/browse/CLOUDSTACK-9529>`_ Marvin Tests do not clean up properly...
+`CLOUDSTACK-9357 <https://issues.apache.org/jira/browse/CLOUDSTACK-9357>`_ DHCP DNS option is incorrect for Redundant Router config...
+`CLOUDSTACK-9547 <https://issues.apache.org/jira/browse/CLOUDSTACK-9547>`_ ACS 4.9 + VMware: Unable to remove one of the NICs of a multi-nic guest VM...
+`CLOUDSTACK-9474 <https://issues.apache.org/jira/browse/CLOUDSTACK-9474>`_ When attaching a pool to an instance the askingSize parameter of pool checker is...
+`CLOUDSTACK-9542 <https://issues.apache.org/jira/browse/CLOUDSTACK-9542>`_ listNics API does not return data as per API documentation...
+`CLOUDSTACK-9528 <https://issues.apache.org/jira/browse/CLOUDSTACK-9528>`_ SSVM Downloads (built-in) template multiple times...
+`CLOUDSTACK-9541 <https://issues.apache.org/jira/browse/CLOUDSTACK-9541>`_ redundant VPC VR: issues when master and backup switch happens on failover...
+`CLOUDSTACK-9540 <https://issues.apache.org/jira/browse/CLOUDSTACK-9540>`_ createPrivateGateway create private network does not create proper VLAN network ...
+`CLOUDSTACK-9413 <https://issues.apache.org/jira/browse/CLOUDSTACK-9413>`_ VmIpFetchTask NullPointerException...
+`CLOUDSTACK-9537 <https://issues.apache.org/jira/browse/CLOUDSTACK-9537>`_ cloudstack can only get network data of eth0 in the xenserver host ...
+`CLOUDSTACK-9536 <https://issues.apache.org/jira/browse/CLOUDSTACK-9536>`_ PVLAN: DhcpPvlanRules command bieng sent before processing finalize start comman...
+`CLOUDSTACK-9518 <https://issues.apache.org/jira/browse/CLOUDSTACK-9518>`_ test_01_test_vm_volume_snapshot Smoke Test Fails...
+`CLOUDSTACK-9521 <https://issues.apache.org/jira/browse/CLOUDSTACK-9521>`_ Multiple Failures in the test_vpc_vpn Smoke Test Suite...
+`CLOUDSTACK-9520 <https://issues.apache.org/jira/browse/CLOUDSTACK-9520>`_ test_01_primary_storage_iscsi Smoke Test Fails...
+`CLOUDSTACK-9519 <https://issues.apache.org/jira/browse/CLOUDSTACK-9519>`_ test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true Smoke Test Failure...
+`CLOUDSTACK-9512 <https://issues.apache.org/jira/browse/CLOUDSTACK-9512>`_ listTemplates ids returns all templates instead of the requested ones...
+`CLOUDSTACK-9508 <https://issues.apache.org/jira/browse/CLOUDSTACK-9508>`_ Change Script and SshHelper to use Duration instead of long timeout....
+`CLOUDSTACK-9318 <https://issues.apache.org/jira/browse/CLOUDSTACK-9318>`_ test_privategw_acl is failing intermittently....
+`CLOUDSTACK-9475 <https://issues.apache.org/jira/browse/CLOUDSTACK-9475>`_ Attaching to PVLAN on VMware dvSwtich fails on VR reboot...
+`CLOUDSTACK-9490 <https://issues.apache.org/jira/browse/CLOUDSTACK-9490>`_ Cant shrink data volume...
+`CLOUDSTACK-9483 <https://issues.apache.org/jira/browse/CLOUDSTACK-9483>`_ In developers.html there is a html </br> tag displayed as a plain text ...
+`CLOUDSTACK-9371 <https://issues.apache.org/jira/browse/CLOUDSTACK-9371>`_ Regular user cannot resize volume...
+`CLOUDSTACK-8398 <https://issues.apache.org/jira/browse/CLOUDSTACK-8398>`_ Changing compute offering checks account quota instead of project quota...
+`CLOUDSTACK-9473 <https://issues.apache.org/jira/browse/CLOUDSTACK-9473>`_ Storage pool checker is ignored on resize and migrate volume....
+`CLOUDSTACK-9472 <https://issues.apache.org/jira/browse/CLOUDSTACK-9472>`_ Taking snapshot on a large VMware volume times out...
+`CLOUDSTACK-9471 <https://issues.apache.org/jira/browse/CLOUDSTACK-9471>`_ Cross cluster migration did not kick in when HA is enabled and Host goes down...
+`CLOUDSTACK-8937 <https://issues.apache.org/jira/browse/CLOUDSTACK-8937>`_ Xenserver - VM migration with storage fails in a clustered management server set...
+`CLOUDSTACK-9144 <https://issues.apache.org/jira/browse/CLOUDSTACK-9144>`_ VMware in Basic Zone: VR never leaves the "Starting" state...
+`CLOUDSTACK-9454 <https://issues.apache.org/jira/browse/CLOUDSTACK-9454>`_ cloudstack-agent logs rotation outdated...
+`CLOUDSTACK-9407 <https://issues.apache.org/jira/browse/CLOUDSTACK-9407>`_ vm_network_map table doesnt get cleaned up properly...
+`CLOUDSTACK-9225 <https://issues.apache.org/jira/browse/CLOUDSTACK-9225>`_ Isolation in Advanced Zone using PVLANs ...
+`CLOUDSTACK-9431 <https://issues.apache.org/jira/browse/CLOUDSTACK-9431>`_ Network usage stats from VR in VPC are wrong after upgrading to ACS 4.7...
+`CLOUDSTACK-9433 <https://issues.apache.org/jira/browse/CLOUDSTACK-9433>`_ Change of VM compute offering with additional storage tags not allowed...
+`CLOUDSTACK-9439 <https://issues.apache.org/jira/browse/CLOUDSTACK-9439>`_ Domain admins can and must create service and disk offerings withouts storage an...
+`CLOUDSTACK-9434 <https://issues.apache.org/jira/browse/CLOUDSTACK-9434>`_ NPE on attempting account/domain cleanup automation...
+`CLOUDSTACK-9341 <https://issues.apache.org/jira/browse/CLOUDSTACK-9341>`_ Cannot upload volume when using Swift as secondary storage...
+`CLOUDSTACK-9206 <https://issues.apache.org/jira/browse/CLOUDSTACK-9206>`_ Input issue on change service offering in Custom...
+`CLOUDSTACK-9432 <https://issues.apache.org/jira/browse/CLOUDSTACK-9432>`_ Dedicate Cluster to Domain always creates an affinity group owned by the root do...
+`CLOUDSTACK-9367 <https://issues.apache.org/jira/browse/CLOUDSTACK-9367>`_ Unable to start a HVM VM with more than 2 volumes attached using XenServer 6.5 ...
+`CLOUDSTACK-9227 <https://issues.apache.org/jira/browse/CLOUDSTACK-9227>`_ service cloudstack-management stop returns [failed] due to log4j:WARN No appende...
+`CLOUDSTACK-9427 <https://issues.apache.org/jira/browse/CLOUDSTACK-9427>`_ Sudo in wrong place when adding APT repository key...
+`CLOUDSTACK-9425 <https://issues.apache.org/jira/browse/CLOUDSTACK-9425>`_ Storage statistics shown on CloudStack Primary storage is different from the sta...
+`CLOUDSTACK-9426 <https://issues.apache.org/jira/browse/CLOUDSTACK-9426>`_ CloudStack does not re-scan for new LUNs for an iSCSI based storage on KVM host...
+`CLOUDSTACK-9385 <https://issues.apache.org/jira/browse/CLOUDSTACK-9385>`_ Password Server is not running on RvR...
+`CLOUDSTACK-9421 <https://issues.apache.org/jira/browse/CLOUDSTACK-9421>`_ Cannot add Instance...
+`CLOUDSTACK-9419 <https://issues.apache.org/jira/browse/CLOUDSTACK-9419>`_ network_domain is a optional param while creating network, still createIpAlias.s...
+`CLOUDSTACK-9412 <https://issues.apache.org/jira/browse/CLOUDSTACK-9412>`_ NullPointerException in CapacityManagerImpl...
+`CLOUDSTACK-8921 <https://issues.apache.org/jira/browse/CLOUDSTACK-8921>`_ snapshot_store_ref table should store actual size of back snapshot in secondary ...
+`CLOUDSTACK-9411 <https://issues.apache.org/jira/browse/CLOUDSTACK-9411>`_ Resize Root Volume UI Element Not Visible By Domain Admins or Users...
+`CLOUDSTACK-8922 <https://issues.apache.org/jira/browse/CLOUDSTACK-8922>`_ Unable to delete IP tag...
+`CLOUDSTACK-9253 <https://issues.apache.org/jira/browse/CLOUDSTACK-9253>`_ docker cloudstack simulator "ImportError: No module named marvin" when try to cr...
+`CLOUDSTACK-8944 <https://issues.apache.org/jira/browse/CLOUDSTACK-8944>`_ Template download possible from new secondary storages before the download is 10...
+`CLOUDSTACK-9394 <https://issues.apache.org/jira/browse/CLOUDSTACK-9394>`_ HttpTemplateDownloader Causes Hanging Connections...
+`CLOUDSTACK-9393 <https://issues.apache.org/jira/browse/CLOUDSTACK-9393>`_ Wrong information returned for CheckS2SVpnConnectionsCommand when more than one ...
+`CLOUDSTACK-9392 <https://issues.apache.org/jira/browse/CLOUDSTACK-9392>`_ Networks with redundant network offerings can be implemented with standalone vir...
+`CLOUDSTACK-9390 <https://issues.apache.org/jira/browse/CLOUDSTACK-9390>`_ Dettaching data volume from a running vm created with root and data disk fails...
+`CLOUDSTACK-9384 <https://issues.apache.org/jira/browse/CLOUDSTACK-9384>`_ AutoScalling without netscaller problem...
+`CLOUDSTACK-9381 <https://issues.apache.org/jira/browse/CLOUDSTACK-9381>`_ updateVmNicIp doesn't update the gateway on NIC if the new IP is from a differen...
+`CLOUDSTACK-8237 <https://issues.apache.org/jira/browse/CLOUDSTACK-8237>`_ add nic with instance throw java.lang.NullPointerException ...
+`CLOUDSTACK-8584 <https://issues.apache.org/jira/browse/CLOUDSTACK-8584>`_ Management Server does not start - "cluster node IP should be valid local addres...
+`CLOUDSTACK-9338 <https://issues.apache.org/jira/browse/CLOUDSTACK-9338>`_ listAccount returns 0 for cputotal and memorytotal if VMs are using a ComputeOff...
+`CLOUDSTACK-9112 <https://issues.apache.org/jira/browse/CLOUDSTACK-9112>`_ deployVM thread is holding the global lock on network longer and cause delays an...
+`CLOUDSTACK-8855 <https://issues.apache.org/jira/browse/CLOUDSTACK-8855>`_ Improve Error Message for Host Alert State...
+`CLOUDSTACK-9372 <https://issues.apache.org/jira/browse/CLOUDSTACK-9372>`_ Cannot create PPTP VPN from guest instance to endpoint outside of the cloud...
+`CLOUDSTACK-9360 <https://issues.apache.org/jira/browse/CLOUDSTACK-9360>`_ Set guest password not working with redundant routers...
+`CLOUDSTACK-9224 <https://issues.apache.org/jira/browse/CLOUDSTACK-9224>`_ XenServer local storage added multiple times...
+`CLOUDSTACK-9346 <https://issues.apache.org/jira/browse/CLOUDSTACK-9346>`_ Password server on VR is not working correctly when using a custom network offer...
+`CLOUDSTACK-9189 <https://issues.apache.org/jira/browse/CLOUDSTACK-9189>`_ rVPC ACL doesn't recover after cleaning up through the NetworkGarbageCollector...
+`CLOUDSTACK-9094 <https://issues.apache.org/jira/browse/CLOUDSTACK-9094>`_ Multiple threads are being used to collect the stats from the same VR...
+`CLOUDSTACK-8775 <https://issues.apache.org/jira/browse/CLOUDSTACK-8775>`_ [HyperV]NPE while attaching Local storage volume to instance whose root volume i...
+`CLOUDSTACK-8787 <https://issues.apache.org/jira/browse/CLOUDSTACK-8787>`_ Network Update from Standalone VR offering to RVR offering is failing with Runti...
+`CLOUDSTACK-8877 <https://issues.apache.org/jira/browse/CLOUDSTACK-8877>`_ Show error msg on VPN user add failure....
+`CLOUDSTACK-8912 <https://issues.apache.org/jira/browse/CLOUDSTACK-8912>`_ listGuestOsMapping doesn't list by id or ostypeid....
+`CLOUDSTACK-8918 <https://issues.apache.org/jira/browse/CLOUDSTACK-8918>`_ [Install] Db Error after install - Unknown column 'iso_id1' in 'field list'...
+`CLOUDSTACK-8929 <https://issues.apache.org/jira/browse/CLOUDSTACK-8929>`_ The list of VMs that can be assigned to a load balancer rule is not updated afte...
+`CLOUDSTACK-9035 <https://issues.apache.org/jira/browse/CLOUDSTACK-9035>`_ [rVR] Password file is stored only with Master when we Reset Password on the VM...
+`CLOUDSTACK-9176 <https://issues.apache.org/jira/browse/CLOUDSTACK-9176>`_ VMware: Shared datastore is accidentally picked up as a local datastore...
+`CLOUDSTACK-9330 <https://issues.apache.org/jira/browse/CLOUDSTACK-9330>`_ Cloudstack creates a malformed meta-data file for baremetal instances...
+`CLOUDSTACK-9329 <https://issues.apache.org/jira/browse/CLOUDSTACK-9329>`_ cloud-set-guest-password doesn't work on CentOS 7...
+`CLOUDSTACK-9079 <https://issues.apache.org/jira/browse/CLOUDSTACK-9079>`_ ipsec service is not running after restarting virtual router...
+`CLOUDSTACK-9316 <https://issues.apache.org/jira/browse/CLOUDSTACK-9316>`_ Problem to install in CentOS7 4.8...
+`CLOUDSTACK-9311 <https://issues.apache.org/jira/browse/CLOUDSTACK-9311>`_ User cant resize VM root disk for XenServer...
+`CLOUDSTACK-9312 <https://issues.apache.org/jira/browse/CLOUDSTACK-9312>`_ Duplicate instance IPs addresses...
+`CLOUDSTACK-9310 <https://issues.apache.org/jira/browse/CLOUDSTACK-9310>`_ vpn user creation throwing error , but showing entry for the same user in VR con...
+`CLOUDSTACK-9309 <https://issues.apache.org/jira/browse/CLOUDSTACK-9309>`_ Adding primary storage pool (basic rbd/DefaultPrimary) doesn't work if the rados...
+`CLOUDSTACK-9307 <https://issues.apache.org/jira/browse/CLOUDSTACK-9307>`_ You can't mix two different linux distributions in a (KVM) Cluster...
+`CLOUDSTACK-9303 <https://issues.apache.org/jira/browse/CLOUDSTACK-9303>`_ Cloudstack can't connect to CEPH with "/" in the user pw...
+`CLOUDSTACK-8845 <https://issues.apache.org/jira/browse/CLOUDSTACK-8845>`_ list snapshot without id is failing with Unable to determine the storage pool of...
+`CLOUDSTACK-8977 <https://issues.apache.org/jira/browse/CLOUDSTACK-8977>`_ cloudstack UI creates a session for users not yet logged in...
+`CLOUDSTACK-9295 <https://issues.apache.org/jira/browse/CLOUDSTACK-9295>`_ EGRESS left on ACCEPT on isolated network...
+`CLOUDSTACK-9292 <https://issues.apache.org/jira/browse/CLOUDSTACK-9292>`_ Failed to create snapshot with Swift on KVM...
+`CLOUDSTACK-9286 <https://issues.apache.org/jira/browse/CLOUDSTACK-9286>`_ Delete Domain not working: Failed to clean up domain resources and sub domains, ...
+`CLOUDSTACK-9284 <https://issues.apache.org/jira/browse/CLOUDSTACK-9284>`_ CloudStack usage service tries to get access to "cloud.event_usage" table only v...
+`CLOUDSTACK-7857 <https://issues.apache.org/jira/browse/CLOUDSTACK-7857>`_ CitrixResourceBase wrongly calculates total memory on hosts with a lot of memory...
+`CLOUDSTACK-9258 <https://issues.apache.org/jira/browse/CLOUDSTACK-9258>`_ listDomains API fails with NPE when getVolumeTotal is null...
+`CLOUDSTACK-9247 <https://issues.apache.org/jira/browse/CLOUDSTACK-9247>`_ Templates go into "Not Ready" state after restarting manangement server with Swi...
+`CLOUDSTACK-9232 <https://issues.apache.org/jira/browse/CLOUDSTACK-9232>`_ Usage data does not reflect changes of VM parameters...
+`CLOUDSTACK-9212 <https://issues.apache.org/jira/browse/CLOUDSTACK-9212>`_ Cannot Connect to VPN with Public IP on Windows 7 L2TP IPSEC VPN Client...
+`CLOUDSTACK-9243 <https://issues.apache.org/jira/browse/CLOUDSTACK-9243>`_ createVlanIpRange API unusable because forced to used DB IDs...
+`CLOUDSTACK-9234 <https://issues.apache.org/jira/browse/CLOUDSTACK-9234>`_ Problem increasing value of vm.password.length global parameter...
+`CLOUDSTACK-8966 <https://issues.apache.org/jira/browse/CLOUDSTACK-8966>`_ listCapacity produces wrong result for CAPACITY_TYPE_MEMORY and CAPACITY_TYPE_CP...
+`CLOUDSTACK-6448 <https://issues.apache.org/jira/browse/CLOUDSTACK-6448>`_ VPC router won't be created when a private gateway is defined. ...
+`CLOUDSTACK-9193 <https://issues.apache.org/jira/browse/CLOUDSTACK-9193>`_ Once password has been fetched, the state does not get updated to "saved_passwor...
+`CLOUDSTACK-9191 <https://issues.apache.org/jira/browse/CLOUDSTACK-9191>`_ ACS 4.6 Custom Offer Signature mismatch "ERROR : "unable to verify user credenti...
+`CLOUDSTACK-9190 <https://issues.apache.org/jira/browse/CLOUDSTACK-9190>`_ ACs is falling to identify the version of pure Xen hypervisor + XAPI hosts....
+`CLOUDSTACK-8806 <https://issues.apache.org/jira/browse/CLOUDSTACK-8806>`_ Powered off VM's not showing up in WebUI...
+`CLOUDSTACK-9170 <https://issues.apache.org/jira/browse/CLOUDSTACK-9170>`_ Register template in UI does not show zones in dropdown listbox...
+`CLOUDSTACK-9173 <https://issues.apache.org/jira/browse/CLOUDSTACK-9173>`_ new Quota plugins: CPU Used column is CPU Free column...
+`CLOUDSTACK-9171 <https://issues.apache.org/jira/browse/CLOUDSTACK-9171>`_ Templates registered with CrossZones have no zone name listed...
+`CLOUDSTACK-9169 <https://issues.apache.org/jira/browse/CLOUDSTACK-9169>`_ createNetwork API call takes a long time when ispersistent=True...
+`CLOUDSTACK-9141 <https://issues.apache.org/jira/browse/CLOUDSTACK-9141>`_ Userdata is not validated for valid base64...
+`CLOUDSTACK-9167 <https://issues.apache.org/jira/browse/CLOUDSTACK-9167>`_ Restore VM - Missing action events for started and completed states...
+`CLOUDSTACK-9090 <https://issues.apache.org/jira/browse/CLOUDSTACK-9090>`_ Cannot delete zone if it was used and not all elements were cleanly removed...
+`CLOUDSTACK-8936 <https://issues.apache.org/jira/browse/CLOUDSTACK-8936>`_ wrong values from network.throttling.rate / vm.network.throttling.rate...
+`CLOUDSTACK-9096 <https://issues.apache.org/jira/browse/CLOUDSTACK-9096>`_ Deleted projects cannot be billed...
+`CLOUDSTACK-9061 <https://issues.apache.org/jira/browse/CLOUDSTACK-9061>`_ cannot deploy Instance when using Swift as Secondary Storage...
+`CLOUDSTACK-9089 <https://issues.apache.org/jira/browse/CLOUDSTACK-9089>`_ Static route added to VPC Private Gateway doesn't become active...
+`CLOUDSTACK-9085 <https://issues.apache.org/jira/browse/CLOUDSTACK-9085>`_ Creation of a instance on a Guest Network with Secondary VLAN fail...
+`CLOUDSTACK-8807 <https://issues.apache.org/jira/browse/CLOUDSTACK-8807>`_ Cloudstack WebUI sometimes bothers about the selected project, sometimes not...
+`CLOUDSTACK-9036 <https://issues.apache.org/jira/browse/CLOUDSTACK-9036>`_ IPV6 CIDR not recognized (Parser BUG)...
+`CLOUDSTACK-9057 <https://issues.apache.org/jira/browse/CLOUDSTACK-9057>`_ upgrade to 4.6 requires 4.5 templates...
+`CLOUDSTACK-9059 <https://issues.apache.org/jira/browse/CLOUDSTACK-9059>`_ Snapshot on S3 fails when delta is zero...
+`CLOUDSTACK-9060 <https://issues.apache.org/jira/browse/CLOUDSTACK-9060>`_ Create volume / template from S3 snapshot fails...
+`CLOUDSTACK-7375 <https://issues.apache.org/jira/browse/CLOUDSTACK-7375>`_ [UI] RBD not available under list of protocols for primary storage during zone c...
+`CLOUDSTACK-9028 <https://issues.apache.org/jira/browse/CLOUDSTACK-9028>`_ GloboDNS doen´t work with "Shared Networks"...
+`CLOUDSTACK-8902 <https://issues.apache.org/jira/browse/CLOUDSTACK-8902>`_ Restart Network fails in EIP/ELB zone...
+`CLOUDSTACK-8994 <https://issues.apache.org/jira/browse/CLOUDSTACK-8994>`_ Activity of the password server isn't logged....
+`CLOUDSTACK-8889 <https://issues.apache.org/jira/browse/CLOUDSTACK-8889>`_ Primary Storage count for an account does not decrease when a Data Disk is delet...
+`CLOUDSTACK-8982 <https://issues.apache.org/jira/browse/CLOUDSTACK-8982>`_ Disk Offering properties do no show the domain which are included in...
+`CLOUDSTACK-8724 <https://issues.apache.org/jira/browse/CLOUDSTACK-8724>`_ Multiple IP's on management server break patchviasocket.pl...
+`CLOUDSTACK-8945 <https://issues.apache.org/jira/browse/CLOUDSTACK-8945>`_ rp_filter=1 not set on VPC private gateway initially, but is set after restart o...
+`CLOUDSTACK-8942 <https://issues.apache.org/jira/browse/CLOUDSTACK-8942>`_ snapshot of root drives failing...
+`CLOUDSTACK-8938 <https://issues.apache.org/jira/browse/CLOUDSTACK-8938>`_ Assigning portforward in Isolated "Offering for Isolated networks with Source Na...
+`CLOUDSTACK-8914 <https://issues.apache.org/jira/browse/CLOUDSTACK-8914>`_ cannot delete pod, NPE...
+`CLOUDSTACK-8909 <https://issues.apache.org/jira/browse/CLOUDSTACK-8909>`_ Web Console not working with Hyper-V Windows Server 2012 R2...
+`CLOUDSTACK-8771 <https://issues.apache.org/jira/browse/CLOUDSTACK-8771>`_ [Automation]Volume migration between pools times out in ACS, but the migration c...
+`CLOUDSTACK-8782 <https://issues.apache.org/jira/browse/CLOUDSTACK-8782>`_ If pagesize is greater than default.page.size in API call, and default.page.size...
+`CLOUDSTACK-8846 <https://issues.apache.org/jira/browse/CLOUDSTACK-8846>`_ Performance issue in GUI - API command listVirtualMachines ...
+`CLOUDSTACK-8839 <https://issues.apache.org/jira/browse/CLOUDSTACK-8839>`_ close concurrent ip disable static nat commands for virtual router will cause so...
+`CLOUDSTACK-8831 <https://issues.apache.org/jira/browse/CLOUDSTACK-8831>`_ Powered off VM's are not removed from ESXi Host when putting the Host in Mainten...
+`CLOUDSTACK-7853 <https://issues.apache.org/jira/browse/CLOUDSTACK-7853>`_ Hosts that are temporary Disconnected and get behind on ping (PingTimeout) turn ...
+`CLOUDSTACK-8747 <https://issues.apache.org/jira/browse/CLOUDSTACK-8747>`_ The agent doesn't reconnect if there are stopped VMs...
+`CLOUDSTACK-8809 <https://issues.apache.org/jira/browse/CLOUDSTACK-8809>`_ Secondary Storage does not clean-up after time-out...
+`CLOUDSTACK-8796 <https://issues.apache.org/jira/browse/CLOUDSTACK-8796>`_ the api calll linkdomaintoldap should fail if admin is given and an account isnt...
+`CLOUDSTACK-7591 <https://issues.apache.org/jira/browse/CLOUDSTACK-7591>`_ Dynamic scaling doesn't work in CloudStack 4.4 with vmware...
+`CLOUDSTACK-8437 <https://issues.apache.org/jira/browse/CLOUDSTACK-8437>`_ Automation: test_04_create_multiple_networks_with_lb_1_network_offering - Fails...
+`CLOUDSTACK-8732 <https://issues.apache.org/jira/browse/CLOUDSTACK-8732>`_ Unable to resize RBD volume: "Cannot determine resize type from pool type RBD"...
+`CLOUDSTACK-8631 <https://issues.apache.org/jira/browse/CLOUDSTACK-8631>`_ [Automation]fixing test/integration/component/test_ss_max_limits.py...
+`CLOUDSTACK-8142 <https://issues.apache.org/jira/browse/CLOUDSTACK-8142>`_ [Hyper-V] While creating system vms attach systemvm.iso directly from sec storag...
+`CLOUDSTACK-8448 <https://issues.apache.org/jira/browse/CLOUDSTACK-8448>`_ Attach volume - throws an exception, preferably should give a proper error on UI...
+`CLOUDSTACK-8770 <https://issues.apache.org/jira/browse/CLOUDSTACK-8770>`_ [HyperV]Proper Message should be displayed when snapshot fails on Hyper-V...
+`CLOUDSTACK-8768 <https://issues.apache.org/jira/browse/CLOUDSTACK-8768>`_ [HyperV]Migrating volume from cluster wide storage to Zone wide storage or vicev...
+`CLOUDSTACK-7839 <https://issues.apache.org/jira/browse/CLOUDSTACK-7839>`_ Unable to live migrate an instance to another host in a cluster from which the t...
+`CLOUDSTACK-7364 <https://issues.apache.org/jira/browse/CLOUDSTACK-7364>`_ NetScaler won't create the Public VLAN and Bind the IP to it...
+`CLOUDSTACK-7618 <https://issues.apache.org/jira/browse/CLOUDSTACK-7618>`_ Baremetal - AddHost() API docs should include parameters - cpunumber,cpuspeed,me...
+`CLOUDSTACK-8389 <https://issues.apache.org/jira/browse/CLOUDSTACK-8389>`_ Volume to Template Conversion Broken...
+`CLOUDSTACK-8442 <https://issues.apache.org/jira/browse/CLOUDSTACK-8442>`_ [VMWARE] VM Cannot be powered on after restoreVirtualMachine ...
+`CLOUDSTACK-8699 <https://issues.apache.org/jira/browse/CLOUDSTACK-8699>`_ Extra acquired public ip is assigned to wrong eth device...
+`CLOUDSTACK-8694 <https://issues.apache.org/jira/browse/CLOUDSTACK-8694>`_ monitorServices.py is not running as a cron job in VR...
+`CLOUDSTACK-8691 <https://issues.apache.org/jira/browse/CLOUDSTACK-8691>`_ deployVirtualMachine should not error when userdata is provided if at least one ...
+`CLOUDSTACK-8328 <https://issues.apache.org/jira/browse/CLOUDSTACK-8328>`_ NPE while deleteing instance which has custom compute offering...
+`CLOUDSTACK-8695 <https://issues.apache.org/jira/browse/CLOUDSTACK-8695>`_ Dashboard Alerts for VR Service failures does not contain the service's name...
+`CLOUDSTACK-8684 <https://issues.apache.org/jira/browse/CLOUDSTACK-8684>`_ Upgrade from 4.3.1 to 4.5.1 does not update resource for existing XenServer 6.0....
+`CLOUDSTACK-8680 <https://issues.apache.org/jira/browse/CLOUDSTACK-8680>`_ problem parsing RabbitMQ events...
+`CLOUDSTACK-8679 <https://issues.apache.org/jira/browse/CLOUDSTACK-8679>`_ Changes to RabbitMQ events notification framework not documented anywhere...
+`CLOUDSTACK-8674 <https://issues.apache.org/jira/browse/CLOUDSTACK-8674>`_ Custom ISO with reboot --eject in kickstart does not get detached at reboot...
+`CLOUDSTACK-8670 <https://issues.apache.org/jira/browse/CLOUDSTACK-8670>`_ Delay in VM's console...
+`CLOUDSTACK-8657 <https://issues.apache.org/jira/browse/CLOUDSTACK-8657>`_ java.awt.HeadlessException exception in console proxy on mouse clicks in XenServ...
+`CLOUDSTACK-8639 <https://issues.apache.org/jira/browse/CLOUDSTACK-8639>`_ fixing calculation mistakes in component/test_ss_domain_limits.py...
+`CLOUDSTACK-8588 <https://issues.apache.org/jira/browse/CLOUDSTACK-8588>`_ Remove redundant skip test for LXC ...
+`CLOUDSTACK-8556 <https://issues.apache.org/jira/browse/CLOUDSTACK-8556>`_ Unable to delete attached volume in cleanup...
+`CLOUDSTACK-8549 <https://issues.apache.org/jira/browse/CLOUDSTACK-8549>`_ Update assert statements in testpath_disable_enable_zone.py testpath ...
+`CLOUDSTACK-8626 <https://issues.apache.org/jira/browse/CLOUDSTACK-8626>`_ [Automation]fixing test/integration/component/test_ps_max_limits.py for lxc hyp...
+`CLOUDSTACK-8627 <https://issues.apache.org/jira/browse/CLOUDSTACK-8627>`_ Unable to remove IP from NIC....
+`CLOUDSTACK-8620 <https://issues.apache.org/jira/browse/CLOUDSTACK-8620>`_ [Automation-lxc]skip test cases if rbd storage is not available in lxc setup ...
+`CLOUDSTACK-8158 <https://issues.apache.org/jira/browse/CLOUDSTACK-8158>`_ After the host reboots, the system will run out vm management IP, no matter how ...
+`CLOUDSTACK-8583 <https://issues.apache.org/jira/browse/CLOUDSTACK-8583>`_ [Automation]fixing issue related to script test/integration/component/test_stop...
+`CLOUDSTACK-8619 <https://issues.apache.org/jira/browse/CLOUDSTACK-8619>`_ Adding secondary IP address results in error...
+`CLOUDSTACK-8618 <https://issues.apache.org/jira/browse/CLOUDSTACK-8618>`_ Name or displaytext can not be same across different templates...
+`CLOUDSTACK-8614 <https://issues.apache.org/jira/browse/CLOUDSTACK-8614>`_ Usage records have no valid records for migrated volumes...
+`CLOUDSTACK-8577 <https://issues.apache.org/jira/browse/CLOUDSTACK-8577>`_ [Automation] fixing script test/integration/component/maint/testpath_disable_en...
+`CLOUDSTACK-8587 <https://issues.apache.org/jira/browse/CLOUDSTACK-8587>`_ Storage migration issue on secondary storage...
+`CLOUDSTACK-8578 <https://issues.apache.org/jira/browse/CLOUDSTACK-8578>`_ listVirtualMachines does not return deleted machines when zone is specified...
+`CLOUDSTACK-8574 <https://issues.apache.org/jira/browse/CLOUDSTACK-8574>`_ Skip testcases including data disk creation for LXC if storagePool type is not R...
+`CLOUDSTACK-8576 <https://issues.apache.org/jira/browse/CLOUDSTACK-8576>`_ Skip tests as snapshots and template are not supported on LXc...
+`CLOUDSTACK-8572 <https://issues.apache.org/jira/browse/CLOUDSTACK-8572>`_ Unable to deploy VM as no storage pool found in UP state in setup...
+`CLOUDSTACK-8555 <https://issues.apache.org/jira/browse/CLOUDSTACK-8555>`_ Skip testcase for HyperV as it doesn't support volume resize operationa...
+`CLOUDSTACK-8201 <https://issues.apache.org/jira/browse/CLOUDSTACK-8201>`_ KVM Snapshot to Template to New Instance is not working...
+`CLOUDSTACK-8148 <https://issues.apache.org/jira/browse/CLOUDSTACK-8148>`_ dvSwitch Broken with java.lang.NumberFormatException...
+`CLOUDSTACK-8558 <https://issues.apache.org/jira/browse/CLOUDSTACK-8558>`_ KVM snapshots are failing at Ubuntu 14.04 LTS...
+`CLOUDSTACK-8557 <https://issues.apache.org/jira/browse/CLOUDSTACK-8557>`_ Issue while starting Clound-Manager...
+`CLOUDSTACK-8553 <https://issues.apache.org/jira/browse/CLOUDSTACK-8553>`_ Unable to launch VM from template because of permission issue...
+`CLOUDSTACK-8550 <https://issues.apache.org/jira/browse/CLOUDSTACK-8550>`_ Attempt to delete already deleted VM...
+`CLOUDSTACK-8547 <https://issues.apache.org/jira/browse/CLOUDSTACK-8547>`_ Modify hypervisor check in testpath_snapshot_hardning.py testpath...
+`CLOUDSTACK-8552 <https://issues.apache.org/jira/browse/CLOUDSTACK-8552>`_ Update test_concurrent_snapshots_limits.py asesrt statement...
+`CLOUDSTACK-8544 <https://issues.apache.org/jira/browse/CLOUDSTACK-8544>`_ IP Stuck in Releasing State Prevents VM Create...
+`CLOUDSTACK-8532 <https://issues.apache.org/jira/browse/CLOUDSTACK-8532>`_ Modification in setupClass to skip testcases rather than throwing exception...
+`CLOUDSTACK-8533 <https://issues.apache.org/jira/browse/CLOUDSTACK-8533>`_ Local variable accessed as a class variable...
+`CLOUDSTACK-8354 <https://issues.apache.org/jira/browse/CLOUDSTACK-8354>`_ [VMware] restoreVirtualMachine should forcefully power off VM...
+`CLOUDSTACK-8519 <https://issues.apache.org/jira/browse/CLOUDSTACK-8519>`_ SystemVMs do not connect to MS running on Java 8...
+`CLOUDSTACK-8451 <https://issues.apache.org/jira/browse/CLOUDSTACK-8451>`_ Static Nat show wrong remote IP in VM behind VPC...
+`CLOUDSTACK-8470 <https://issues.apache.org/jira/browse/CLOUDSTACK-8470>`_ Available Primary Storage Capacity Displayed Incorrectly after Upgrade to ACS 4....
+`CLOUDSTACK-7907 <https://issues.apache.org/jira/browse/CLOUDSTACK-7907>`_ UI heavily broken...
+`CLOUDSTACK-8469 <https://issues.apache.org/jira/browse/CLOUDSTACK-8469>`_ wrong global config mount.parent - /var/lib/cloud/mnt ...
+`CLOUDSTACK-8446 <https://issues.apache.org/jira/browse/CLOUDSTACK-8446>`_ VM reboot operation should make sure there's a VR running...
+`CLOUDSTACK-8436 <https://issues.apache.org/jira/browse/CLOUDSTACK-8436>`_ Computing offering with High avaliability does not work properly....
+`CLOUDSTACK-8435 <https://issues.apache.org/jira/browse/CLOUDSTACK-8435>`_ When the ssvm agent restarts, every template generated from a VM snapshot disapp...
+`CLOUDSTACK-8434 <https://issues.apache.org/jira/browse/CLOUDSTACK-8434>`_ tag filtering hanging on returning values for listVirtualMachines...
+`CLOUDSTACK-8408 <https://issues.apache.org/jira/browse/CLOUDSTACK-8408>`_ unused i18n keys...
+`CLOUDSTACK-8173 <https://issues.apache.org/jira/browse/CLOUDSTACK-8173>`_ listCapacity api call returns less response tags than expected...
+`CLOUDSTACK-8371 <https://issues.apache.org/jira/browse/CLOUDSTACK-8371>`_ Unable to Delete VPC After configuring site-to-site VPN...
+`CLOUDSTACK-8370 <https://issues.apache.org/jira/browse/CLOUDSTACK-8370>`_ volume download link will not be deleted...
+`CLOUDSTACK-8358 <https://issues.apache.org/jira/browse/CLOUDSTACK-8358>`_ Cloudstack 4.4.2 Error adding devcloud host IOException scp error: Invalid locat...
+`CLOUDSTACK-8281 <https://issues.apache.org/jira/browse/CLOUDSTACK-8281>`_ VPN Gateway don't create when create Site-to-Site VPN...
+`CLOUDSTACK-8297 <https://issues.apache.org/jira/browse/CLOUDSTACK-8297>`_ vnc listen address...
+`CLOUDSTACK-8228 <https://issues.apache.org/jira/browse/CLOUDSTACK-8228>`_ Allow adding hosts from different subnets in same POD...
+`CLOUDSTACK-8260 <https://issues.apache.org/jira/browse/CLOUDSTACK-8260>`_ listLBStickinessPolicies with lbruleid as argument gives empty return...
+`CLOUDSTACK-8242 <https://issues.apache.org/jira/browse/CLOUDSTACK-8242>`_ Cloudstack install Hosts for vmware...
+`CLOUDSTACK-7449 <https://issues.apache.org/jira/browse/CLOUDSTACK-7449>`_ "CloudRuntimeException: Can not see storage pool" after trying to add a new host...
+`CLOUDSTACK-8202 <https://issues.apache.org/jira/browse/CLOUDSTACK-8202>`_ Templates /IOS items order list is not persistent...
+`CLOUDSTACK-8199 <https://issues.apache.org/jira/browse/CLOUDSTACK-8199>`_ Incorrect size when volumes and templates created from image snapshots...
+`CLOUDSTACK-8189 <https://issues.apache.org/jira/browse/CLOUDSTACK-8189>`_ security group can't enable...
+`CLOUDSTACK-7640 <https://issues.apache.org/jira/browse/CLOUDSTACK-7640>`_ Failed to delete template that failed to download...
+`CLOUDSTACK-8185 <https://issues.apache.org/jira/browse/CLOUDSTACK-8185>`_ GUI and failed async commands issue...
+`CLOUDSTACK-7365 <https://issues.apache.org/jira/browse/CLOUDSTACK-7365>`_ Upgrading without proper systemvm template corrupt cloudstack management server...
+`CLOUDSTACK-8092 <https://issues.apache.org/jira/browse/CLOUDSTACK-8092>`_ Unable to start instance due to failed to configure ip alias on the router as a ...
+`CLOUDSTACK-8073 <https://issues.apache.org/jira/browse/CLOUDSTACK-8073>`_ listNetworkACLItem does not return cidrs...
+`CLOUDSTACK-8004 <https://issues.apache.org/jira/browse/CLOUDSTACK-8004>`_ Xenserver Thin Provisioning...
+`CLOUDSTACK-7789 <https://issues.apache.org/jira/browse/CLOUDSTACK-7789>`_ I was updated from version 4.4.0 of Apache CloudStack to 4.4.1. It does not work...
+`CLOUDSTACK-7988 <https://issues.apache.org/jira/browse/CLOUDSTACK-7988>`_ Template status is empty while the template is creating....
+`CLOUDSTACK-7936 <https://issues.apache.org/jira/browse/CLOUDSTACK-7936>`_ System VM's are getting stuck in starting mode after Hypervisor reboot...
+`CLOUDSTACK-7858 <https://issues.apache.org/jira/browse/CLOUDSTACK-7858>`_ Implement separate network throttling rate on VR's Public NIC...
+`CLOUDSTACK-7342 <https://issues.apache.org/jira/browse/CLOUDSTACK-7342>`_ Fail to delete template while using Swift as Secondary Storage...
+`CLOUDSTACK-7782 <https://issues.apache.org/jira/browse/CLOUDSTACK-7782>`_ The 4.4.1 web UI is missing "Acquire new IP address" buton in NIC section...
+`CLOUDSTACK-7819 <https://issues.apache.org/jira/browse/CLOUDSTACK-7819>`_ Cannot add tags to project...
+`CLOUDSTACK-7813 <https://issues.apache.org/jira/browse/CLOUDSTACK-7813>`_ Management server is stuck after upgrade from 4.4.0 to 4.4.1...
+`CLOUDSTACK-7751 <https://issues.apache.org/jira/browse/CLOUDSTACK-7751>`_ Autoscaling without netscaler...
+`CLOUDSTACK-7750 <https://issues.apache.org/jira/browse/CLOUDSTACK-7750>`_ Xen server can not mount secondary CIFS storage...
+`CLOUDSTACK-7578 <https://issues.apache.org/jira/browse/CLOUDSTACK-7578>`_ XenServerInvestigator should do better investigation in case of OVS or other net...
+`CLOUDSTACK-7406 <https://issues.apache.org/jira/browse/CLOUDSTACK-7406>`_ Templates using Swift provider reports physical size, and not the virtual size i...
+`CLOUDSTACK-7443 <https://issues.apache.org/jira/browse/CLOUDSTACK-7443>`_ Cannot launch SSVMs when using Swift as Secondary Storage...
+========================================================================== ===================================================================================
diff --git a/source/releasenotes/locale/ja/LC_MESSAGES/about.mo b/source/releasenotes/locale/ja/LC_MESSAGES/about.mo
new file mode 100644
index 0000000..ad03993
--- /dev/null
+++ b/source/releasenotes/locale/ja/LC_MESSAGES/about.mo
Binary files differ
diff --git a/source/releasenotes/locale/ja/LC_MESSAGES/about.po b/source/releasenotes/locale/ja/LC_MESSAGES/about.po
new file mode 100644
index 0000000..c9c8b14
--- /dev/null
+++ b/source/releasenotes/locale/ja/LC_MESSAGES/about.po
@@ -0,0 +1,5927 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-05 14:09+0100\n"
+"PO-Revision-Date: 2014-03-31 15:24+0000\n"
+"Last-Translator: sebgoa <runseb@gmail.com>\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/apache-cloudstack-release-notes-rtd/language/ja/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# b576289212e54cb78ed684eec3888a03
+#: ../../source/about.rst:17
+msgid "About this new Release"
+msgstr ""
+
+# 041aef7b56634ca9a8a96f43278fd527
+#: ../../source/about.rst:20
+msgid "What's New in 4.3"
+msgstr ""
+
+# 5322a08e2b494ae5a2c82cedea3b0aa0
+#: ../../source/about.rst:22
+msgid "CloudStack 4.3 includes the following new features."
+msgstr ""
+
+# 0876950b77c54beb85b983fba4496c00
+#: ../../source/about.rst:25
+msgid "Optional 64-Bit System VM Template Support"
+msgstr ""
+
+# 8a2fed0a4b384e9796539817da67c958
+#: ../../source/about.rst:27
+msgid ""
+"CloudStack now provides 64-bit templates for System VMs. With this support, "
+"you will be able to upgrade virtual routers in a zone. The following "
+"parameters have been introduced for the same purpose:"
+msgstr ""
+
+# 0e4e9594c53b4bea9dd780826bd0dc71
+#: ../../source/about.rst:33
+msgid "XenServer: *``router.template.xen``*"
+msgstr ""
+
+# c0af61a617114caaacf0279264dd5d06
+#: ../../source/about.rst:37
+msgid "KVM: *``router.template.kvm``*"
+msgstr ""
+
+# aecc6c0e4a1b49168f343801d8dca3bc
+#: ../../source/about.rst:41
+msgid "VMware:"
+msgstr ""
+
+# d789a68734994ebc8f66901df1928395
+#: ../../source/about.rst:45
+msgid "Hyper-V:"
+msgstr ""
+
+# 804fdc472af9432c944dee3247993077
+#: ../../source/about.rst:48
+msgid "Hyper-V Support"
+msgstr ""
+
+# f6a1d0157418482682ff112c79fcdbfe
+#: ../../source/about.rst:50
+msgid ""
+"CloudStack 4.3 Beta rolls out support for Hyper-V hosts. For Hyper-V, "
+"CloudStack supports SMB-based storage. If you want to run guest VMs on "
+"Hyper-V hosts, install CloudStack Agents on each Hyper-V hosts. Before you "
+"use Hyper-V, review the following list of supported and non-supported "
+"features. For detailed instruction, see Hyper-V Quick Start Guide. You can "
+"also see the chapter Installing Hyper-V for CloudStack in the CloudStack 4.3"
+" Beta Installation Guide."
+msgstr ""
+
+# ae6a53cb206b40709b96496ce5339299
+# c925adb80f424f86b1b6959684d54557
+#: ../../source/about.rst:59 ../../source/about.rst:464
+msgid "Supported Functionalities"
+msgstr ""
+
+# 990d715fb8674f01bbcaebb0115054c4
+#: ../../source/about.rst:63
+msgid "VM Compute"
+msgstr ""
+
+# 2a0b668f5247485089f03b43af2181c3
+#: ../../source/about.rst:67
+msgid "All the VM operations, except VM Snapshots"
+msgstr ""
+
+# 3719b2fe0b304f4ba6d0b415d18e6bb0
+#: ../../source/about.rst:71
+msgid "Live Migration"
+msgstr ""
+
+# 99f7bd2be18c45b4855770b451d9e050
+#: ../../source/about.rst:75
+msgid "Service Offerings (Scale up on stopped VMs)"
+msgstr ""
+
+# 8f66257200c9407dbd52fe9d68335066
+#: ../../source/about.rst:79
+msgid "Console access"
+msgstr ""
+
+# 9d4bf9710ada4aac82890f17f7f298c0
+#: ../../source/about.rst:83
+msgid "SSH key and reseting SSH key"
+msgstr ""
+
+# d3345ccf5ce14feaa4522ee03767a823
+#: ../../source/about.rst:87
+msgid "Upload and download templates, volumes, and ISO"
+msgstr ""
+
+# e21aa429f0494d6a9e9f53ef6490a793
+#: ../../source/about.rst:91
+msgid "Create VMs from template and ISO"
+msgstr ""
+
+# b2ead7a50034443da581e170c420f9ee
+#: ../../source/about.rst:95
+msgid "Create template from volume"
+msgstr ""
+
+# d3c4bc7304be4bceb9fcc8e936802d14
+#: ../../source/about.rst:99
+msgid "Attach and detach VMs from ISO and password-enabled template"
+msgstr ""
+
+# 22d0290679bf4859bd4ba5a60a76be0a
+#: ../../source/about.rst:103
+msgid "Copy template across zone"
+msgstr ""
+
+# 12fce5e639a646158f1dc86dfa7e398b
+#: ../../source/about.rst:107
+msgid "Storage"
+msgstr "ストレージ"
+
+# 6998aae328cd44ec81dea862ddbc8b88
+#: ../../source/about.rst:111
+msgid "Primary Storage (SMB and Local)"
+msgstr ""
+
+# 253bb3aed0054525a1e099b0f8848ec5
+#: ../../source/about.rst:115
+msgid "Root and data volumes on Local and SMB"
+msgstr ""
+
+# 1ea502369b144d039b4cee2719180070
+#: ../../source/about.rst:119
+msgid "Add, delete, attach, detach volumes (one or more volumes per VM)"
+msgstr ""
+
+# e63f3da3d4d74e868da51084b5898669
+#: ../../source/about.rst:123
+msgid "Single and multiple secondary storage (SMB)"
+msgstr ""
+
+# b026291779464da3801d90e1ddde3180
+#: ../../source/about.rst:127
+msgid "Network"
+msgstr "ネットワーク"
+
+# 23e7c8c98c714ed9b36b1d580e4fd189
+#: ../../source/about.rst:131
+msgid "VLANs (Isolated and Shared)"
+msgstr ""
+
+# db1efe7f26f84702beb0ebf9818ef009
+#: ../../source/about.rst:135
+msgid ""
+"All VR services: DNS, DHCP, SourceNAT, LB, PF, Firewall, StaticNAT, "
+"Userdata, and VPN"
+msgstr ""
+
+# c2bec305654e46c4962358cbdcabe7ee
+#: ../../source/about.rst:140
+msgid ""
+"External device support for both Isolated and Shared networks: Netscaler, "
+"SRX, F5"
+msgstr ""
+
+# 5bc7bcbbd7c94278a9c2c37e621693c1
+#: ../../source/about.rst:145
+msgid "Multiple physical networks"
+msgstr ""
+
+# 1c66959656f743a9a898e8f91dd1e092
+#: ../../source/about.rst:149
+msgid "Dedicated IP range, Public VLANs (to account)"
+msgstr ""
+
+# e5de14ce5630418eba740fa64ca72222
+#: ../../source/about.rst:153
+msgid "Network Offering upgrades and updates"
+msgstr ""
+
+# fdedc1322fe04400a7a95f10bcb99360
+#: ../../source/about.rst:157
+msgid "L4-L7 services in Shared network"
+msgstr ""
+
+# 5317a9412d78466497242974410d41ac
+#: ../../source/about.rst:161
+msgid "Multiple IP ranges and portable IPs"
+msgstr ""
+
+# 4f4164dbe6c04dbeb4b36dfc7b21d25d
+#: ../../source/about.rst:165
+msgid "Host and Storage in maintenance mode"
+msgstr ""
+
+# 1365192c943749548531638c71236d33
+# 4254094b77ad4fccb1d0f27cf30751f1
+#: ../../source/about.rst:168 ../../source/about.rst:491
+msgid "Unsupported Functionalities"
+msgstr ""
+
+# d84bc7b2af5a4cc9b5a4f16fdd148f62
+#: ../../source/about.rst:172
+msgid "Affinity an Anti-Affinity Groups"
+msgstr ""
+
+# c287c4b058c64dcab9d2718477baa0cb
+#: ../../source/about.rst:176
+msgid "Network throttling"
+msgstr ""
+
+# 83063443f6784e209519f3606cc66dff
+#: ../../source/about.rst:180
+msgid "Security groups (Advanced Zone)"
+msgstr ""
+
+# ba3e8a31c31f45b1867b519b1eabb57b
+#: ../../source/about.rst:184
+msgid "IPv6"
+msgstr ""
+
+# d693896fbf4f43b696c1c6bbf627bed3
+#: ../../source/about.rst:188
+msgid "Snapshot: VM and disk"
+msgstr ""
+
+# ff65a2c3e280456981dedd6e461ad5ca
+#: ../../source/about.rst:192
+msgid "PVLAN"
+msgstr ""
+
+# e561849c04c944f8be5a80462ef529e7
+#: ../../source/about.rst:196
+msgid "VPC"
+msgstr "VPC"
+
+# 8274ec6f81de48a7bbdf53bc6db095ed
+#: ../../source/about.rst:200
+msgid "HA of guest VMs"
+msgstr ""
+
+# ba9d79afc26446789bd9270bc1a81915
+#: ../../source/about.rst:204
+msgid "Redundant VR"
+msgstr ""
+
+# 9aa73675588647adabf4ccf233816078
+#: ../../source/about.rst:208
+msgid "Object Store"
+msgstr ""
+
+# 3b87930b1ae2464188590c091bdc9178
+#: ../../source/about.rst:212
+msgid "Mixed hypervisor zone"
+msgstr ""
+
+# 961e37f6a03b43b19b88d6fe12894f12
+#: ../../source/about.rst:216
+msgid "Zone-wide Primary storage"
+msgstr ""
+
+# fcd982c075794659a78690617fad2b1c
+#: ../../source/about.rst:220
+msgid "NIC bonding"
+msgstr ""
+
+# 15429ecd44af40f8acc23d7ce5dad298
+#: ../../source/about.rst:223
+msgid "Enhanced Upgrade for Virtual Routers"
+msgstr ""
+
+# 2e7606316a0d4c4893ef33579783da9c
+#: ../../source/about.rst:225
+msgid ""
+"Upgrading VRs is made flexible. The CloudStack administrators will be able "
+"to control the sequence of the VR upgrades. The sequencing is based on "
+"Infrastructure hierarchy, such as by Cluster, Pod, or Zone, and "
+"Administrative hierarchy, such as by Tenant or Domain. This implies, for "
+"example, that you will have the flexibility to upgrade a VR in a specified "
+"zone. As an administrator, you can also determine when a particular VR can "
+"be upgraded within a specified upgrade interval. Additionally, upgrade "
+"operation is enhanced to increase the upgrade speed by allowing as many "
+"upgrade operations in parallel as possible. During the entire duration of "
+"the upgrade, users cannot launch new services or make changes to an existing"
+" service."
+msgstr ""
+
+# cb50052d577e48138bf33eee32615b7f
+#: ../../source/about.rst:237
+msgid ""
+"To support this feature, a new API, upgradeRouterTemplate, has been "
+"introduced."
+msgstr ""
+
+# 21c4e473dda443e59b2fefad539b0c8f
+#: ../../source/about.rst:240
+msgid ""
+"The detailed instruction is provided in the CloudStack 4.3 Beta "
+"Administration Guide. See section 17.5.5. Enhanced Upgrade for Virtual "
+"Routers."
+msgstr ""
+
+# 4acc8687c449489681ef672832a82bcf
+#: ../../source/about.rst:245
+msgid "Service Monitoring Tool for Virtual Router"
+msgstr ""
+
+# c35b1d53a9d04786934783c6e80af816
+#: ../../source/about.rst:247
+msgid ""
+"Various services running on the CloudStack virtual routers can be monitored "
+"by using a Service Monitoring tool. The tool ensures that services are "
+"successfully running until CloudStack deliberately disables them. If a "
+"service goes down, the tool automatically performs a restart, and if that "
+"does not help bringing up the service, an alert as well as an event is "
+"generated indicating the failure."
+msgstr ""
+
+# fb1814861a52422aa3a1709ed6bd203f
+#: ../../source/about.rst:254
+msgid "The following services are monitored in a VR:"
+msgstr ""
+
+# ba9f7906e3fc407bb578f3e382709e7f
+#: ../../source/about.rst:258
+msgid "DNS"
+msgstr "DNS"
+
+# f106a0ddd91d4a79b85ab48bda92d0b3
+#: ../../source/about.rst:262
+msgid "HA Proxy"
+msgstr ""
+
+# 6bb83f65a4ce438f93386e4cc4d40cc0
+#: ../../source/about.rst:266
+msgid "SSH"
+msgstr ""
+
+# 45474236a1a64471a70a589c10bea027
+#: ../../source/about.rst:270
+msgid "Apache Web Server"
+msgstr ""
+
+# eb9628d7ce8442358f6d52cd48261b62
+#: ../../source/about.rst:272
+msgid "Only the services with daemons are monitored."
+msgstr ""
+
+# 2e5f0bb910be497c8994d25c1f4c000e
+#: ../../source/about.rst:274
+msgid "The following networks are supported:"
+msgstr ""
+
+# aeb04ecf0871477eb3fee51a9dd3eee7
+#: ../../source/about.rst:278
+msgid "Isolated Networks"
+msgstr ""
+
+# 76cc16ee246f4ff59c883f2420897e97
+#: ../../source/about.rst:282
+msgid "Shared Networks in both Advanced and Basic zone"
+msgstr ""
+
+# 9e28655074d246bb9d632f8407063fba
+#: ../../source/about.rst:284
+msgid ""
+"This feature is supported on the following hypervisors: XenServer, VMware, "
+"and KVM."
+msgstr ""
+
+# fd19cabcc1e146ce9a22d1d867f71bd9
+#: ../../source/about.rst:287
+msgid ""
+"The detailed instruction is provided in the CloudStack 4.3 Beta "
+"Administration Guide. See section 17.5.4. Service Monitoring Tool for "
+"Virtual Router."
+msgstr ""
+
+# 3a5da1b1b0824bf4848ea8198d940340
+#: ../../source/about.rst:292
+msgid "Custom Compute Offering"
+msgstr ""
+
+# 0795f8fac93045b89432c223e7dc8ee6
+#: ../../source/about.rst:294
+msgid ""
+"CloudStack provides you the flexibility to specify the desired values for "
+"the number of CPU, CPU speed, and memory while deploying a VM. The admin "
+"creates a Compute Offering by marking it as custom, and as an user, you will"
+" be able to customize this dynamic Compute Offering by specifying the "
+"memory, CPU and root disk at the time of VM creation or upgrade."
+msgstr ""
+
+# 240037ae25e84b6dab9400693c1e78ec
+#: ../../source/about.rst:301
+msgid ""
+"Custom Compute Offering is same as the normal Compute Offering except that "
+"the values of the dynamic parameters will be set to zeros in the given set "
+"of templates. Use this offering to deploy VM by specifying custom values for"
+" the dynamic parameters. Memory, CPU and number of CPUs are considered as "
+"dynamic parameters. Dynamic Compute Offerings can be used in following "
+"cases: deploying a VM, changing the compute offering of a stopped VM and "
+"running VMs, which is nothing but scaling up. To support this feature a new "
+"field, Custom, has been added to the Create Compute Offering page. If the "
+"Custom field is checked, the end-user will be able to create a custom "
+"Compute Offering by filling in the desired values for number of CPU, CPU "
+"speed, and memory."
+msgstr ""
+
+# e2d137d524e24f469e752a7c2f65f843
+#: ../../source/about.rst:314
+msgid "Remote Access VPN for VPC"
+msgstr ""
+
+# b489cdff4c624a9db86a57f457aa9057
+#: ../../source/about.rst:316
+msgid ""
+"Support for Remote access VPN in Isolated networks is now extended to VPC "
+"networks. Remote users will now be able to initiate a VPN connection to a "
+"VPC network. To enable this feature, enable VPN in the Source NAT IP of the "
+"VPC."
+msgstr ""
+
+# 88f5e250dfb04917af3d0b1d6e9e9340
+#: ../../source/about.rst:322
+msgid "Site to Site VPN Connection Between VPC Networks"
+msgstr ""
+
+# 18f849f54ac64bbf8d259746cc0855ff
+#: ../../source/about.rst:324
+msgid ""
+"CloudStack provides you with the ability to establish a site-to-site VPN "
+"connection between CloudStack virtual routers. With this functionality, "
+"users can deploy applications in multiple Availability Zones or VPCs, which "
+"can communicate with each other by using a secure Site-to-Site VPN Tunnel. "
+"Creating a typical Site to Site VPN connection between VPC networks involves"
+" the following:"
+msgstr ""
+
+# f657e6953d9c4ef98bb39ea6ed87d1c8
+#: ../../source/about.rst:333
+msgid "Create two VPCs. For example, VPC A and VPC B."
+msgstr ""
+
+# 31428bba2d1448a5b612c098d2369e34
+#: ../../source/about.rst:337
+msgid "Create VPN gateways on both the VPCs you created."
+msgstr ""
+
+# 43bb7911eae7460d8e708229a8579828
+#: ../../source/about.rst:341
+msgid "Create VPN customer gateway for both the VPCs."
+msgstr ""
+
+# 0a108eb37c714915aadf7cf4935d4688
+#: ../../source/about.rst:345
+msgid "Enable a VPN connection on VPC A in passive mode."
+msgstr ""
+
+# b9a11deaee284017a5c91fdb6c49e471
+#: ../../source/about.rst:347
+msgid ""
+"Ensure that the customer gateway is pointed to VPC B. The VPN connection is "
+"shown in the Disconnected state."
+msgstr ""
+
+# 19dd039bfb6946cab2e77ee83a2f84ee
+#: ../../source/about.rst:352
+msgid "Enable a VPN connection on VPC B."
+msgstr ""
+
+# 40c6521c2b2142c5be66812d44651174
+#: ../../source/about.rst:354
+msgid ""
+"Ensure that the customer gateway is pointed to VPC A. Because virtual router"
+" of VPC A, in this case, is in passive mode and is waiting for the virtual "
+"router of VPC B to initiate the connection. The virtual router of VPC B "
+"should not be in passive mode."
+msgstr ""
+
+# 46ce45d1e33d4f16b911774604c439e5
+#: ../../source/about.rst:359
+msgid "The VPN connection is shown in the Disconnected state."
+msgstr ""
+
+# 2ca835abbdca4b6eba929ddc53f00a74
+#: ../../source/about.rst:361
+msgid ""
+"Creating VPN connection on both the VPCs initiates a VPN connection. Wait "
+"for few seconds. The default is 30 seconds for both the VPN connections to "
+"show the Connected state."
+msgstr ""
+
+# e75896e1324e4a42bbc33a809ef3e353
+#: ../../source/about.rst:366
+msgid "Reporting CPU Sockets"
+msgstr ""
+
+# 60ec77345ae64d8d93f836564151f93b
+#: ../../source/about.rst:368
+msgid ""
+"CloudStack now provides an additional infrastructure statistics for CPU "
+"sockets managed by CloudStack, which in turn reflects the size of the cloud."
+" The Infrastructure tab has a new tab for sockets. The Socket page will give"
+" you the number of hosts an sockets used for each hypervisor type. This "
+"feature is not supported in versions prior to XenServer 6.2."
+msgstr ""
+
+# 8b04c3237e0b437ab6a3cd6dae59b7be
+#: ../../source/about.rst:375
+msgid "Database High Availability"
+msgstr ""
+
+# c2838bb4743343c4ab32c6f638bbd473
+#: ../../source/about.rst:377
+msgid ""
+"To help ensure high availability of the databases that store the internal "
+"data for CloudStack, you can set up database replication. This covers both "
+"the main CloudStack database and the Usage database. Replication is achieved"
+" using the MySQL connector parameters and two-way replication. Tested with "
+"MySQL 5.1 and 5.5. Database replication in CloudStack is provided using the "
+"MySQL replication capabilities. The steps to set up replication can be found"
+" in the MySQL documentation."
+msgstr ""
+
+# 23624a964f744aedad828b991665e2ce
+#: ../../source/about.rst:386
+msgid "LDAP User Provisioning"
+msgstr ""
+
+# 331bf7324ec445c9b20a8454cf28e5fd
+#: ../../source/about.rst:388
+msgid ""
+"LDAP user provisioning has been enhanced by allowing user import from the "
+"configured LDAP servers. You will be able to add multiple LDAP servers and "
+"selectively import LDAP users. You can o filter by group name and import all"
+" the users within a group. After they have been imported to CloudStack, in "
+"contrast to manually adding them in previous releases, users are allowed to "
+"directly log in to CloudStack by using the LDAP credentials."
+msgstr ""
+
+# f5fc680f4b394266bc18e8381d0f1f0d
+#: ../../source/about.rst:397
+msgid "Migrating NFS Secondary Storage to Object Store"
+msgstr ""
+
+# 74028d4c65944efb97e7bfec95297291
+#: ../../source/about.rst:399
+msgid ""
+"In an existing zone that is using NFS for secondary storage, you can upgrade"
+" the zone to use a region-wide object storage without causing downtime. The "
+"existing NFS storage in the zone will be converted to an NFS Staging Store. "
+"After migration, the data that was on the NFS storage remains there. "
+"CloudStack does not provide a way to automatically migrate all data to the "
+"new object storage. The data remaining on the old NFS storage will remain "
+"accessible for read and delete operations only. Newly created snapshots and "
+"templates will be placed in the newly configured object storage."
+msgstr ""
+
+# 058ab0339375451eaafdfcc096005b74
+#: ../../source/about.rst:410
+msgid "VXLAN Plugin Support"
+msgstr ""
+
+# 30e405f84714447884791227096846a9
+#: ../../source/about.rst:412
+msgid ""
+"The VXLAN plugin adds VXLAN as one of the guest network isolation methods in"
+" CloudStack. This plugin enables more than 4096 isolated guest networks in a"
+" Zone, with almost the same usability as VLAN isolation. This plugin "
+"provides no network services. Use virtual router for network services. This "
+"plugin is supported on KVM hypervisors."
+msgstr ""
+
+# dc14ae091f8240a88fdd3342b54c709b
+#: ../../source/about.rst:419
+msgid "Contrail Network Plugin Support"
+msgstr ""
+
+# ed60d48cbddb4d018c53ced482827b14
+#: ../../source/about.rst:421
+msgid ""
+"The Contrail virtual network controller is an open source project that "
+"provides an overlay implementation of network virtualization that is "
+"interoperable with network devices that support existing network "
+"virtualization standards. Support for the Contrail plugin has been added to "
+"CloudStack to provide NAT services to the XenServer hosts. The plugin "
+"supports isolated networks, Static NAT implemented by the VRouter dataplane,"
+" and Source NAT implemented by using a virtual appliance with full NAT "
+"functionality."
+msgstr ""
+
+# 99bf061d28ff4ea8b56dc48abb3915e2
+#: ../../source/about.rst:431
+msgid "Publishing Alert Using the Web ROOT Admin API"
+msgstr ""
+
+# db2ad5c2cb8f43cf84fad3f44cc3f3f9
+#: ../../source/about.rst:433
+msgid ""
+"In previous releases of CloudStack code alerts are generated for CloudStack "
+"services (Usage service) only if they run on the same host as the Management"
+" Server. A new API has been introduced in 4.3, which can be used by the "
+"following services to generate and publish. The services need not be running"
+" on the same host where the Management Server is running."
+msgstr ""
+
+# 665e5482649c40069213ee90d7f4feb1
+#: ../../source/about.rst:442
+msgid "Any new services added to CloudStack."
+msgstr ""
+
+# 2b827219a7c34ad0b6dc5791b65783e0
+#: ../../source/about.rst:446
+msgid "Usage service when run on a separate storage host."
+msgstr ""
+
+# f507ed910d114f6e90e0b5bb23861338
+#: ../../source/about.rst:450
+msgid "Console Proxy and Secondary Storage VM services."
+msgstr ""
+
+# f5b1ab53601944fc85ed83607af9828c
+#: ../../source/about.rst:452
+msgid ""
+"The main advantage of this feature is that the third party systems "
+"integrating with CloudStack will be able to utilize the Alert notification "
+"system publish alerts."
+msgstr ""
+
+# 34cdd6907b05476bab75c2b115f5533c
+#: ../../source/about.rst:457
+msgid "Support for Palo Alto Firewall Service"
+msgstr ""
+
+# 4f1cf6a0c3f242a9829c6fdfe67fdc02
+#: ../../source/about.rst:459
+msgid ""
+"CloudStack supports Palo Alto firewall services. Use the Create Network "
+"Offering dialog to create an offering which has the Palo Alto firewall "
+"services. What is not supported and not supported are given below:"
+msgstr ""
+
+# 52a82b3f2ab64e659f88517461771327
+#: ../../source/about.rst:468
+msgid "Advanced Network"
+msgstr ""
+
+# 13439ff6bc0046229ab0ad9115378aab
+#: ../../source/about.rst:472
+msgid "Parallel deployment with hardware Load balancer"
+msgstr ""
+
+# fcc0e851073f47c094f34865eca68e04
+#: ../../source/about.rst:476
+msgid "Virtual Palo Alto firewall."
+msgstr ""
+
+# 47f70e3d39704a888c679ed51c394fc1
+#: ../../source/about.rst:480
+msgid "Communication layer with Palo Alto APIs."
+msgstr ""
+
+# 1df4648228184b9c8400e1777a713b53
+#: ../../source/about.rst:484
+msgid "Mapping of CloudStack APIs to corresponding Palo Alto APIs."
+msgstr ""
+
+# 2e0b41f6e1434a0f86ee143da29f5334
+#: ../../source/about.rst:488
+msgid "Connectivity status of the firewall service on the CloudStack UI."
+msgstr ""
+
+# 66ab3b2d85c8461e9f6fd9743602a092
+#: ../../source/about.rst:495
+msgid "Inline deployment with hardware Load balancer"
+msgstr ""
+
+# 4323bbdbf12049538df46b6e62f679f2
+#: ../../source/about.rst:499
+msgid "Firewall between VLANs within an advanced network"
+msgstr ""
+
+# 0ab363d048474009ad3e44c2477d96b1
+#: ../../source/about.rst:503
+msgid "Firewall between VM instances"
+msgstr ""
+
+# 69922eb6f88249c2a1dbedd6dfe07f29
+#: ../../source/about.rst:505
+msgid ""
+"For more information, see `Palo Alto Firewall Integration "
+"<https://cwiki.apache.org/confluence/display/CLOUDSTACK/Palo+Alto+Firewall+Integration>`__."
+msgstr ""
+
+# 160529cf6dd04d9c8425fc5a412bf663
+#: ../../source/about.rst:509
+msgid "Root Volume Metering"
+msgstr ""
+
+# 57e7c64781b94df9ae9f15762ba55bc5
+#: ../../source/about.rst:511
+msgid ""
+"CloudStack supports recording usage events as per the dynamically assigned "
+"resources. Usage events are registered when a VM is created from dynamic "
+"service offering, and the values of parameters, such as CPU, speed, RAM are "
+"recorded. If VM is deployed by using template and dynamic root disk size is "
+"mentioned, the same value is recorded in the usage event."
+msgstr ""
+
+# c1f66f4c3bcf472ea617423ea52cb810
+#: ../../source/about.rst:519
+msgid "Support for SSL Termination"
+msgstr ""
+
+# 7749d124b6644556bd3a63077e67061e
+#: ../../source/about.rst:521
+msgid ""
+"SSL Offloading allows load balancers to handle encryption and decryption of "
+"HTTP(s) traffic giving plain text HTTP to the back end servers freeing them "
+"from the resource intensive task of handling encryption and decryption. "
+"Supported for Citrix NetScaler."
+msgstr ""
+
+# 490936156baf4f4ba40bad5b2221c2e9
+#: ../../source/about.rst:527
+msgid "Support for Pluggable VM Snapshots"
+msgstr ""
+
+# 828973faf95349c18f17384f083aafd1
+#: ../../source/about.rst:529
+msgid ""
+"CloudStack implements a plugin to integrate a third-party storage provider. "
+"Third party storage providers can integrate with CloudStack to provide "
+"either primary storage or secondary storage. The user enables a storage "
+"plugin through the UI. A new dialog box choice is offered to select the "
+"storage provider. Depending on which provider is selected, additional input "
+"fields may appear so that the user can provide the additional details "
+"required by that provider, such as a user name and password for a third-"
+"party storage account."
+msgstr ""
+
+# 6cbc29938aab4a04a48fa4b658c07e12
+#: ../../source/about.rst:539
+msgid "Enhanced CloudStack UI"
+msgstr ""
+
+# 69867013f6ff439fbdaea9046df092f9
+#: ../../source/about.rst:541
+msgid ""
+"A complete UI makeover is implemented to enhance the usability and user "
+"experience in modern browsers. The visual look-and-feel has been changed for"
+" the Header, Navigation, Buttons, text fields, drop-downs, tables and so on."
+" Consistent color themes has been introduced to match with the Apache "
+"branding."
+msgstr ""
+
+# e0c1d3a4dff54cd29a1fde49db79ba44
+#: ../../source/about.rst:547
+msgid "The current UI flow remains the same."
+msgstr ""
+
+# 8a9111236af743469d0f01c8f1c02daa
+#: ../../source/about.rst:550
+msgid "Issues Fixed in 4.3.0"
+msgstr ""
+
+# edb7bea4958c44ed83296e9b8937e67a
+# 936db570e1784d7e942c5cc73564f7e8
+#: ../../source/about.rst:552 ../../source/about.rst:727
+msgid ""
+"Apache CloudStack uses `Jira "
+"<https://issues.apache.org/jira/browse/CLOUDSTACK>`__ to track its issues. "
+"All new features and bugs for 4.3 have been tracked in Jira, and have a "
+"standard naming convention of \"CLOUDSTACK-NNNN\" where \"NNNN\" is the "
+"issue number."
+msgstr ""
+
+# b948cc1f76a943a4b819da6d75e0e02a
+#: ../../source/about.rst:555
+msgid ""
+"For the list of issues fixed, see `Issues Fixed in 4.3 "
+"<https://issues.apache.org/jira/issues/?filter=12326161>`__."
+msgstr ""
+
+# dc2cafa99fd94368b2b85b22934e57ae
+# 6f3bbaf12ebe4e389f4c5d690538551a
+#: ../../source/about.rst:559 ../../source/about.rst:734
+msgid "Bug ID"
+msgstr ""
+
+# 8d1125706d604c378cf3452f646c1b75
+# af767f946b1347dbbce5a5a9ad2407cb
+#: ../../source/about.rst:559 ../../source/about.rst:734
+msgid "Description"
+msgstr "説明"
+
+# b3c560a66bcd42b5bf60b8464ce65e1e
+#: ../../source/about.rst:561
+msgid ""
+"`CLOUDSTACK-6103 <https://issues.apache.org/jira/browse/CLOUDSTACK-6103>`_"
+msgstr ""
+
+# 60ad9b5a7cb64632b0c95187e3731446
+#: ../../source/about.rst:561
+msgid "vms with isos attached don't migrate..."
+msgstr ""
+
+# 20872e6668c044e8a38dc23103c2fe1d
+#: ../../source/about.rst:562
+msgid ""
+"`CLOUDSTACK-6089 <https://issues.apache.org/jira/browse/CLOUDSTACK-6089>`_"
+msgstr ""
+
+# 5f24746917154bd9becf37fa2ebbbf4c
+#: ../../source/about.rst:562
+msgid "resource tags show up in multiples..."
+msgstr ""
+
+# 2969ae4a020b4e89955194318fda0fc0
+#: ../../source/about.rst:563
+msgid ""
+"`CLOUDSTACK-6046 <https://issues.apache.org/jira/browse/CLOUDSTACK-6046>`_"
+msgstr ""
+
+# eb94c9151f1940279f52e10913ee8bb4
+#: ../../source/about.rst:563
+msgid ""
+"CreateVolume from snapshot is failing with S3 as secondary storage and zone-"
+"wide..."
+msgstr ""
+
+# 3fff64589a7d42ca8055ea36e01a4884
+#: ../../source/about.rst:564
+msgid ""
+"`CLOUDSTACK-6040 <https://issues.apache.org/jira/browse/CLOUDSTACK-6040>`_"
+msgstr ""
+
+# 9e5931f448b949f9a826817301799eab
+#: ../../source/about.rst:564
+msgid "Failed to configure PF on vm secondary ip for shared network..."
+msgstr ""
+
+# 1590eb52696e442ea08b5735209b54be
+#: ../../source/about.rst:565
+msgid ""
+"`CLOUDSTACK-6007 <https://issues.apache.org/jira/browse/CLOUDSTACK-6007>`_"
+msgstr ""
+
+# 7f0ee23c76394aa3b0090a46ba3379f9
+#: ../../source/about.rst:565
+msgid "[VMware] RestoreVM API fails with NPE..."
+msgstr ""
+
+# ac80ffe92d0d4317a94bd8b01acd2312
+#: ../../source/about.rst:566
+msgid ""
+"`CLOUDSTACK-5986 <https://issues.apache.org/jira/browse/CLOUDSTACK-5986>`_"
+msgstr ""
+
+# b70b2bb0f7f54c38a4b59f5d2774e522
+#: ../../source/about.rst:566
+msgid ""
+"dnsmasq racy condition result in dnsmasq failed to handout IP address..."
+msgstr ""
+
+# 7a8bfa08a17548618f90bc7ba426bafd
+#: ../../source/about.rst:567
+msgid ""
+"`CLOUDSTACK-5971 <https://issues.apache.org/jira/browse/CLOUDSTACK-5971>`_"
+msgstr ""
+
+# 75b75eb5703b475eb4b39507eceda5ce
+#: ../../source/about.rst:567
+msgid "Templates created from a snapshots can't be copied to other zones..."
+msgstr ""
+
+# 9d4b1863eb3e4cca956ab8afa343b44c
+#: ../../source/about.rst:568
+msgid ""
+"`CLOUDSTACK-5960 <https://issues.apache.org/jira/browse/CLOUDSTACK-5960>`_"
+msgstr ""
+
+# 35a2fd2cbd2f4803ab2c6619669b941f
+#: ../../source/about.rst:568
+msgid ""
+"Domain admin or user cannot register a template using S3/Swift object "
+"store..."
+msgstr ""
+
+# 3ec65f14592547faaf8b9585e212f904
+#: ../../source/about.rst:569
+msgid ""
+"`CLOUDSTACK-5922 <https://issues.apache.org/jira/browse/CLOUDSTACK-5922>`_"
+msgstr ""
+
+# 64bacb27a8274bfe87ba48b6c442cda6
+#: ../../source/about.rst:569
+msgid "Incorrect handling RHEL guests ..."
+msgstr ""
+
+# d573ea887741418395b23a3088560c26
+#: ../../source/about.rst:570
+msgid ""
+"`CLOUDSTACK-5921 <https://issues.apache.org/jira/browse/CLOUDSTACK-5921>`_"
+msgstr ""
+
+# 21f626a6874c4b0e82ebbd1e08ef6cbc
+#: ../../source/about.rst:570
+msgid "S3 security key is stored in DB unencrypted..."
+msgstr ""
+
+# 013caae5f40c44c19cff4eae1047025b
+#: ../../source/about.rst:571
+msgid ""
+"`CLOUDSTACK-5903 <https://issues.apache.org/jira/browse/CLOUDSTACK-5903>`_"
+msgstr ""
+
+# 11372c63ca934240abbc4bd7f46fabb8
+#: ../../source/about.rst:571
+msgid "CLONE - OVA files exist for templates created from volumes..."
+msgstr ""
+
+# 95eaa5b600394575b72ce84f1bf79773
+#: ../../source/about.rst:572
+msgid ""
+"`CLOUDSTACK-5895 <https://issues.apache.org/jira/browse/CLOUDSTACK-5895>`_"
+msgstr ""
+
+# 54311c1a2a5d4074ab3ddbebd805c1e9
+#: ../../source/about.rst:572
+msgid ""
+"CreateVolumeFromSnapshot can fail in a multiple pod environment with tagged "
+"stor..."
+msgstr ""
+
+# 7995568a728943bf914af11f559a23d5
+#: ../../source/about.rst:573
+msgid ""
+"`CLOUDSTACK-5886 <https://issues.apache.org/jira/browse/CLOUDSTACK-5886>`_"
+msgstr ""
+
+# fa51e778d56946a5a0f698f9ce3a8355
+#: ../../source/about.rst:573
+msgid "4.2.1 upgrade fails on acl migration..."
+msgstr ""
+
+# f65f098cb13b4ad7bf6b300e36c8634c
+#: ../../source/about.rst:574
+msgid ""
+"`CLOUDSTACK-5877 <https://issues.apache.org/jira/browse/CLOUDSTACK-5877>`_"
+msgstr ""
+
+# 4bda684192f543c1a3261925ac7fd778
+#: ../../source/about.rst:574
+msgid "listTemplates does not sort based on sort_key..."
+msgstr ""
+
+# 2561e890c4af48d7bff25009e8be8e78
+#: ../../source/about.rst:575
+msgid ""
+"`CLOUDSTACK-5875 <https://issues.apache.org/jira/browse/CLOUDSTACK-5875>`_"
+msgstr ""
+
+# e0b0fc87fc4a4d36b23eae1524ece1d5
+#: ../../source/about.rst:575
+msgid "No templates in simulator run..."
+msgstr ""
+
+# 93552171f0dd407caee4ffa27125d13a
+#: ../../source/about.rst:576
+msgid ""
+"`CLOUDSTACK-5864 <https://issues.apache.org/jira/browse/CLOUDSTACK-5864>`_"
+msgstr ""
+
+# fd0da60db85d445ab32de0ff25b52e23
+#: ../../source/about.rst:576
+msgid "Simulator profile broken ..."
+msgstr ""
+
+# a2f90a6fe1784bf0b333d459d84f9f4e
+#: ../../source/about.rst:577
+msgid ""
+"`CLOUDSTACK-5813 <https://issues.apache.org/jira/browse/CLOUDSTACK-5813>`_"
+msgstr ""
+
+# 2969c5d4941a4964bef59c9e35f79a6b
+#: ../../source/about.rst:577
+msgid ""
+"With S3 as secondary storage, snapshot taken in one zone cannot be used to "
+"creat..."
+msgstr ""
+
+# bd8ddd2ee2604f1989dfddb1fd3e5690
+#: ../../source/about.rst:578
+msgid ""
+"`CLOUDSTACK-5723 <https://issues.apache.org/jira/browse/CLOUDSTACK-5723>`_"
+msgstr ""
+
+# 51d46a1458154066a9db40277cbb3a8a
+#: ../../source/about.rst:578
+msgid "Malfunction agent may block future SSL connection to the server..."
+msgstr ""
+
+# 84772a0b67b7462d878f4c45cee5d6c7
+#: ../../source/about.rst:579
+msgid ""
+"`CLOUDSTACK-5704 <https://issues.apache.org/jira/browse/CLOUDSTACK-5704>`_"
+msgstr ""
+
+# 5cd5aef611824dcab41292dfc1868e1c
+#: ../../source/about.rst:579
+msgid "OVA files exist for templates created from volumes..."
+msgstr ""
+
+# 39b22027316c4e2590a87bd8445a3ec8
+#: ../../source/about.rst:580
+msgid ""
+"`CLOUDSTACK-5701 <https://issues.apache.org/jira/browse/CLOUDSTACK-5701>`_"
+msgstr ""
+
+# b47788afd6c84b78b75d9df79b0356a7
+#: ../../source/about.rst:580
+msgid "size column is not getting updated in snapshot_store_ref table...."
+msgstr ""
+
+# 6507a2db556f4f10af283fbd0c653507
+#: ../../source/about.rst:581
+msgid ""
+"`CLOUDSTACK-5666 <https://issues.apache.org/jira/browse/CLOUDSTACK-5666>`_"
+msgstr ""
+
+# fd33a6e0c759429cabac88ad679fed3f
+#: ../../source/about.rst:581
+msgid "Cant remove a nic when a vm is in the Stopped state ..."
+msgstr ""
+
+# df2dffc8b41149b9ae91c736b3167d4b
+#: ../../source/about.rst:582
+msgid ""
+"`CLOUDSTACK-5661 <https://issues.apache.org/jira/browse/CLOUDSTACK-5661>`_"
+msgstr ""
+
+# deb50800f21042faa3496ce106be4da3
+#: ../../source/about.rst:582
+msgid ""
+"[VMware] DetachIsoCmd succeeds even though cdrom is locked by VM as cdrom is"
+" mou..."
+msgstr ""
+
+# 1ec5e73f57af4813b2676b9182b41365
+#: ../../source/about.rst:583
+msgid ""
+"`CLOUDSTACK-5653 <https://issues.apache.org/jira/browse/CLOUDSTACK-5653>`_"
+msgstr ""
+
+# c23f25dc96224a10a1e3643549fad689
+#: ../../source/about.rst:583
+msgid ""
+"S3 object store as Secondary Storage, the template created from different "
+"zone i..."
+msgstr ""
+
+# fd895562ee3043289906b0530817d6ee
+#: ../../source/about.rst:584
+msgid ""
+"`CLOUDSTACK-5613 <https://issues.apache.org/jira/browse/CLOUDSTACK-5613>`_"
+msgstr ""
+
+# 126d72ade2e440fca675e315a84c3356
+#: ../../source/about.rst:584
+msgid "CloudStack 4.2.0 - Usage server is running but tables remain empty..."
+msgstr ""
+
+# 3e010bd06edf4cde914fb226e5d53669
+#: ../../source/about.rst:585
+msgid ""
+"`CLOUDSTACK-5608 <https://issues.apache.org/jira/browse/CLOUDSTACK-5608>`_"
+msgstr ""
+
+# 2f981d66bf5249fba995d224509f5801
+#: ../../source/about.rst:585
+msgid ""
+"HyperV Builtin and System vm template entries missing in 4.3 upgrade "
+"setup..."
+msgstr ""
+
+# 3befdc8910aa4e629b9beff787d723a7
+#: ../../source/about.rst:586
+msgid ""
+"`CLOUDSTACK-5534 <https://issues.apache.org/jira/browse/CLOUDSTACK-5534>`_"
+msgstr ""
+
+# ee69a4436e084b50b3ac4d2d892cfd4b
+#: ../../source/about.rst:586
+msgid "MySQL exception raised when searching for users with keyword..."
+msgstr ""
+
+# 204e779344434bf49b4990da0e0b5ae7
+#: ../../source/about.rst:587
+msgid ""
+"`CLOUDSTACK-5533 <https://issues.apache.org/jira/browse/CLOUDSTACK-5533>`_"
+msgstr ""
+
+# bfcafcab103145d4bc2308df6538b97f
+#: ../../source/about.rst:587
+msgid ""
+"Virtual router in shared network does respond to DNS even when no DNS "
+"service is..."
+msgstr ""
+
+# 224a56ae47aa4e7f967b83cf56a9ae00
+#: ../../source/about.rst:588
+msgid ""
+"`CLOUDSTACK-5532 <https://issues.apache.org/jira/browse/CLOUDSTACK-5532>`_"
+msgstr ""
+
+# 56c70a2b75544a7482348c3a3ca3c4e4
+#: ../../source/about.rst:588
+msgid "Long tag values are not readable within the UI..."
+msgstr ""
+
+# 59cd0224ac764c7e91fe5ca45e365618
+#: ../../source/about.rst:589
+msgid ""
+"`CLOUDSTACK-5519 <https://issues.apache.org/jira/browse/CLOUDSTACK-5519>`_"
+msgstr ""
+
+# 7497b1ecef6e4aa78d5fc1945d1552e6
+#: ../../source/about.rst:589
+msgid ""
+"[VMWARE] Cancel vCenter tasks if the task invoked by CloudStack failes with "
+"time..."
+msgstr ""
+
+# 84eecbc8809c4204945afd28051d6075
+#: ../../source/about.rst:590
+msgid ""
+"`CLOUDSTACK-5517 <https://issues.apache.org/jira/browse/CLOUDSTACK-5517>`_"
+msgstr ""
+
+# 1770b7849bdf4f5d9cf17dd123595ea0
+#: ../../source/about.rst:590
+msgid "NPE observed during \"release portable IPs\" as part of account cleanup..."
+msgstr ""
+
+# 6cf798c00fae47038554efc5ad560015
+#: ../../source/about.rst:591
+msgid ""
+"`CLOUDSTACK-5514 <https://issues.apache.org/jira/browse/CLOUDSTACK-5514>`_"
+msgstr ""
+
+# a1a26f07a1274e1f937292bd447f35e3
+#: ../../source/about.rst:591
+msgid "Response of listAccounts API call includes removed users..."
+msgstr ""
+
+# 4055fb97d2ae41dba3e487b614a92113
+#: ../../source/about.rst:592
+msgid ""
+"`CLOUDSTACK-5513 <https://issues.apache.org/jira/browse/CLOUDSTACK-5513>`_"
+msgstr ""
+
+# 0c69091ed0e24c219ea7c3dfa20ac561
+#: ../../source/about.rst:592
+msgid "VM can't start after creating snapshot from it (CS4.2 + VMware 5.1)..."
+msgstr ""
+
+# 3a69c0084f3b42d2a76bbecea47de6df
+#: ../../source/about.rst:593
+msgid ""
+"`CLOUDSTACK-5481 <https://issues.apache.org/jira/browse/CLOUDSTACK-5481>`_"
+msgstr ""
+
+# 471db3db35e04972bff608e3efab2c83
+#: ../../source/about.rst:593
+msgid "Regular User is unable to use \"Add Isolated Network\" Button on the UI..."
+msgstr ""
+
+# 5215fb218db64494809cabf08f864147
+#: ../../source/about.rst:594
+msgid ""
+"`CLOUDSTACK-5466 <https://issues.apache.org/jira/browse/CLOUDSTACK-5466>`_"
+msgstr ""
+
+# 52c053355ae24c43b3eec6b4568b66ca
+#: ../../source/about.rst:594
+msgid "removeIpFromNic not working properly..."
+msgstr ""
+
+# 787d3ea9522f4d7db790f56c00642a65
+#: ../../source/about.rst:595
+msgid ""
+"`CLOUDSTACK-5453 <https://issues.apache.org/jira/browse/CLOUDSTACK-5453>`_"
+msgstr ""
+
+# 9a39d357304442b98b4dad13e46a429c
+#: ../../source/about.rst:595
+msgid "Site-to-site VPN connection status monitoring is broken in KVM..."
+msgstr ""
+
+# bdc0c48b41554b6ab91402d766016e96
+#: ../../source/about.rst:596
+msgid ""
+"`CLOUDSTACK-5431 <https://issues.apache.org/jira/browse/CLOUDSTACK-5431>`_"
+msgstr ""
+
+# d2aa88a55c9f40dab4fd0a702d59883a
+#: ../../source/about.rst:596
+msgid "permit 'http' as service type for GSLB rule..."
+msgstr ""
+
+# cfd5c3da8c8f4569bd44afb26bac058d
+#: ../../source/about.rst:597
+msgid ""
+"`CLOUDSTACK-5428 <https://issues.apache.org/jira/browse/CLOUDSTACK-5428>`_"
+msgstr ""
+
+# 9b38642a1eb145a28ff6bdc0fb01abe8
+#: ../../source/about.rst:597
+msgid ""
+"support NetScaler to be configured exclusively for GSLB service and not used"
+" for..."
+msgstr ""
+
+# 92ffb1c72f6f4c989c847a3d159b2b6d
+#: ../../source/about.rst:598
+msgid ""
+"`CLOUDSTACK-5426 <https://issues.apache.org/jira/browse/CLOUDSTACK-5426>`_"
+msgstr ""
+
+# 785d11d1b4b74c3c8a9cab733bcb1c6f
+#: ../../source/about.rst:598
+msgid ""
+"Cannot deploy instance having multiple volumes that use different storage "
+"tags f..."
+msgstr ""
+
+# 365fd10374254b4ba4ae8b1b9f64a797
+#: ../../source/about.rst:599
+msgid ""
+"`CLOUDSTACK-5422 <https://issues.apache.org/jira/browse/CLOUDSTACK-5422>`_"
+msgstr ""
+
+# f96e4bb29ea247e69fc942db8a0d5db7
+#: ../../source/about.rst:599
+msgid "Changing XenServer Tools Version 6.1 + doesnt work ..."
+msgstr ""
+
+# 6cb5ca7d32d14a1d9f13d0697874da07
+#: ../../source/about.rst:600
+msgid ""
+"`CLOUDSTACK-5417 <https://issues.apache.org/jira/browse/CLOUDSTACK-5417>`_"
+msgstr ""
+
+# df9d2495dbaa457db9ddce1bca1308ea
+#: ../../source/about.rst:600
+msgid ""
+"On network restart for external devices egress rules configured with old "
+"CIDR..."
+msgstr ""
+
+# 8ab00ac30e094f938ccf295d0dc184f9
+#: ../../source/about.rst:601
+msgid ""
+"`CLOUDSTACK-5416 <https://issues.apache.org/jira/browse/CLOUDSTACK-5416>`_"
+msgstr ""
+
+# df28d08e10114f5a8e5ce0d8ce609f37
+#: ../../source/about.rst:601
+msgid "[VMware] Not able to add seventh disk to VM in an upgraded setup..."
+msgstr ""
+
+# 66150c3309a54123aeb1174fe926903e
+#: ../../source/about.rst:602
+msgid ""
+"`CLOUDSTACK-5404 <https://issues.apache.org/jira/browse/CLOUDSTACK-5404>`_"
+msgstr ""
+
+# dc30931a10f44f958e4dab4a8f26af4b
+#: ../../source/about.rst:602
+msgid ""
+"Network usages (bytes sent/received) are saved in the wrong timezone..."
+msgstr ""
+
+# 05cf80b1a9e1451eb2cd825cac620c0c
+#: ../../source/about.rst:603
+msgid ""
+"`CLOUDSTACK-5401 <https://issues.apache.org/jira/browse/CLOUDSTACK-5401>`_"
+msgstr ""
+
+# 477a4f6910be4a8c9609fb522f89c655
+#: ../../source/about.rst:603
+msgid ""
+"VM migration during host maintenance fails if "
+"pool.storage.capacity.disablethres..."
+msgstr ""
+
+# 9bedfe8d327840ba8d5d3df0578dab36
+#: ../../source/about.rst:604
+msgid ""
+"`CLOUDSTACK-5391 <https://issues.apache.org/jira/browse/CLOUDSTACK-5391>`_"
+msgstr ""
+
+# d1918d6b593c45b4a769dc3eca90364f
+#: ../../source/about.rst:604
+msgid ""
+"Change service offering of a stopped vm and then starting it should check "
+"host c..."
+msgstr ""
+
+# 8cc263da77dc48048502764c176974f2
+#: ../../source/about.rst:605
+msgid ""
+"`CLOUDSTACK-5355 <https://issues.apache.org/jira/browse/CLOUDSTACK-5355>`_"
+msgstr ""
+
+# c94679b661e6408893eb76bdaba36221
+#: ../../source/about.rst:605
+msgid "addImageStore should not log password in clear text in the log..."
+msgstr ""
+
+# c4333272ddc04f51b83cf83496cdd50c
+#: ../../source/about.rst:606
+msgid ""
+"`CLOUDSTACK-5354 <https://issues.apache.org/jira/browse/CLOUDSTACK-5354>`_"
+msgstr ""
+
+# 531fe50313bd49ccbf95f0c3df7ac098
+#: ../../source/about.rst:606
+msgid "CLONE - UI - normal users are not allowed to edit their own iso..."
+msgstr ""
+
+# 10366a1f27134ab49045a5939ed34cc8
+#: ../../source/about.rst:607
+msgid ""
+"`CLOUDSTACK-5352 <https://issues.apache.org/jira/browse/CLOUDSTACK-5352>`_"
+msgstr ""
+
+# 7ff3df608e5c4b76bddd875446178da9
+#: ../../source/about.rst:607
+msgid "CPU cap calculated incorrectly for VMs on XenServer hosts..."
+msgstr ""
+
+# 8def818865644b468ff9af6d6eb751dd
+#: ../../source/about.rst:608
+msgid ""
+"`CLOUDSTACK-5332 <https://issues.apache.org/jira/browse/CLOUDSTACK-5332>`_"
+msgstr ""
+
+# f868f359bc3d46aabbe334e1ad95a584
+#: ../../source/about.rst:608
+msgid "Network offering don't use new system offering for router..."
+msgstr ""
+
+# 37a6e73a71834a49b653090c8e2ce161
+#: ../../source/about.rst:609
+msgid ""
+"`CLOUDSTACK-5303 <https://issues.apache.org/jira/browse/CLOUDSTACK-5303>`_"
+msgstr ""
+
+# 0a663b1b99d94382ada269bd9b93e2b6
+#: ../../source/about.rst:609
+msgid ""
+"\"snapshot\" count and \"secondary_storage\" count are not correct in "
+"resource_coun..."
+msgstr ""
+
+# 0bb8849ac8ce4c9eab76ab9ff94f6eb7
+#: ../../source/about.rst:610
+msgid ""
+"`CLOUDSTACK-5302 <https://issues.apache.org/jira/browse/CLOUDSTACK-5302>`_"
+msgstr ""
+
+# e9b30caa38064a7aa10f72c00a54c52b
+#: ../../source/about.rst:610
+msgid "listHosts API response - value of cpuallocated is always 0%..."
+msgstr ""
+
+# c8e381f6b0cb440d8b61c78dc449cd29
+#: ../../source/about.rst:611
+msgid ""
+"`CLOUDSTACK-5299 <https://issues.apache.org/jira/browse/CLOUDSTACK-5299>`_"
+msgstr ""
+
+# 1c1c5f7e616a400caa4bc59b4cbbc14c
+#: ../../source/about.rst:611
+msgid "Can not get hypervisor type for volumes..."
+msgstr ""
+
+# 19425611d0264d0a8e7a5c6523dea2da
+#: ../../source/about.rst:612
+msgid ""
+"`CLOUDSTACK-5293 <https://issues.apache.org/jira/browse/CLOUDSTACK-5293>`_"
+msgstr ""
+
+# 252a6ef04eae41aba3ef59cf2fd55f87
+#: ../../source/about.rst:612
+msgid ""
+"Error while collecting vm disk stats from hosts if iso is attached to vm..."
+msgstr ""
+
+# 6965e373a81042f9a9af73a92dd627fb
+#: ../../source/about.rst:613
+msgid ""
+"`CLOUDSTACK-5285 <https://issues.apache.org/jira/browse/CLOUDSTACK-5285>`_"
+msgstr ""
+
+# 09e08756611440839a311b2d3fb774d9
+#: ../../source/about.rst:613
+msgid "Correct the API command description for removeIpFromNic..."
+msgstr ""
+
+# c765565cafc943cc86a873694ce66cb9
+#: ../../source/about.rst:614
+msgid ""
+"`CLOUDSTACK-5261 <https://issues.apache.org/jira/browse/CLOUDSTACK-5261>`_"
+msgstr ""
+
+# f83b311847994b95bb23f9bfe2e6ffc1
+#: ../../source/about.rst:614
+msgid "Ability to publish Alerts via CS Root API..."
+msgstr ""
+
+# c1f2ddad98214ea0b53d6a3903ecb350
+#: ../../source/about.rst:615
+msgid ""
+"`CLOUDSTACK-5260 <https://issues.apache.org/jira/browse/CLOUDSTACK-5260>`_"
+msgstr ""
+
+# 798b013ee93f408789382110fce51778
+#: ../../source/about.rst:615
+msgid "Vmware 5.1 Deploy Template Error : Read Timeout..."
+msgstr ""
+
+# e0608e327ca84eda935169365fd535d5
+#: ../../source/about.rst:616
+msgid ""
+"`CLOUDSTACK-5228 <https://issues.apache.org/jira/browse/CLOUDSTACK-5228>`_"
+msgstr ""
+
+# 4385c25da5c341a19a0b7a7f634cf6f1
+#: ../../source/about.rst:616
+msgid ""
+"[API] [EIP/ELB enabled Zone] Need to display EIP address as \"Public IP "
+"Address\" ..."
+msgstr ""
+
+# 65bc7d76ad4345b9b1f46dd44a2e867f
+#: ../../source/about.rst:617
+msgid ""
+"`CLOUDSTACK-5227 <https://issues.apache.org/jira/browse/CLOUDSTACK-5227>`_"
+msgstr ""
+
+# 356fc4cc94ad4000b83f7e65d2e008c9
+#: ../../source/about.rst:617
+msgid "Cannot pass Japanese characters as parameter values to API..."
+msgstr ""
+
+# 8db4754695944bfe9e329296ac80bcd8
+#: ../../source/about.rst:618
+msgid ""
+"`CLOUDSTACK-5218 <https://issues.apache.org/jira/browse/CLOUDSTACK-5218>`_"
+msgstr ""
+
+# ae0b81b811a84cf7a4eecc734f061df9
+#: ../../source/about.rst:618
+msgid ""
+"CLONE - [Doc] Make VMware vCenter session timeout value configurable...."
+msgstr ""
+
+# 9b93a94c174b4089ae64219475781428
+#: ../../source/about.rst:619
+msgid ""
+"`CLOUDSTACK-5199 <https://issues.apache.org/jira/browse/CLOUDSTACK-5199>`_"
+msgstr ""
+
+# 6ab3889236d7416fa815a6825d3bff5c
+#: ../../source/about.rst:619
+msgid ""
+"Cannot restart VM after taking a VM snapshot of an existing VM or reverting "
+"a VM..."
+msgstr ""
+
+# 26aa3abc88c6468898df5d9fb38f3570
+#: ../../source/about.rst:620
+msgid ""
+"`CLOUDSTACK-5141 <https://issues.apache.org/jira/browse/CLOUDSTACK-5141>`_"
+msgstr ""
+
+# b26d24381fc54173b48b37dd1163d779
+#: ../../source/about.rst:620
+msgid ""
+"[Automation] Router deployment failed due to failure in SavePasswordCommand,"
+" obs..."
+msgstr ""
+
+# e2d5d651311543bea190e1ad6b018d62
+#: ../../source/about.rst:621
+msgid ""
+"`CLOUDSTACK-5140 <https://issues.apache.org/jira/browse/CLOUDSTACK-5140>`_"
+msgstr ""
+
+# d0f86a6e0cf344f6b651d4550e44c1e3
+#: ../../source/about.rst:621
+msgid ""
+"A stopped vm cant start after disable threshold has been reached on the "
+"storage ..."
+msgstr ""
+
+# e3ad276c6e7f48ec9f2cbf0e647a15d5
+#: ../../source/about.rst:622
+msgid ""
+"`CLOUDSTACK-5138 <https://issues.apache.org/jira/browse/CLOUDSTACK-5138>`_"
+msgstr ""
+
+# 10841b65c88a4dd0aa89d4dee8eca6c6
+#: ../../source/about.rst:622
+msgid "[Automation] NPE while create template from snapshot..."
+msgstr ""
+
+# 86779fef657742789a83db76e4f35613
+#: ../../source/about.rst:623
+msgid ""
+"`CLOUDSTACK-5122 <https://issues.apache.org/jira/browse/CLOUDSTACK-5122>`_"
+msgstr ""
+
+# 1bb27372472b4c01b39fd736d536f7d3
+#: ../../source/about.rst:623
+msgid ""
+"[VMware] System VMs are getting recreated with old template after upgrading "
+"to 4..."
+msgstr ""
+
+# 290b6c8dba5340f6800b7e62b8b02faf
+#: ../../source/about.rst:624
+msgid ""
+"`CLOUDSTACK-5105 <https://issues.apache.org/jira/browse/CLOUDSTACK-5105>`_"
+msgstr ""
+
+# b0cf2b62404a4fcaae9f7e3e6157b3cb
+#: ../../source/about.rst:624
+msgid "Template/ISO download fails cause the object to disappear from UI..."
+msgstr ""
+
+# 065e55629e6f43fa8f985b5aa2eee3d0
+#: ../../source/about.rst:625
+msgid ""
+"`CLOUDSTACK-5098 <https://issues.apache.org/jira/browse/CLOUDSTACK-5098>`_"
+msgstr ""
+
+# afb576415a9e49628133a72e1c5a5182
+#: ../../source/about.rst:625
+msgid ""
+"[UI] Zone view is showing \"Add VMware Datacenter\" button even though zone "
+"is alr..."
+msgstr ""
+
+# af71183c79eb44aca10e1a61e369c1dc
+#: ../../source/about.rst:626
+msgid ""
+"`CLOUDSTACK-5092 <https://issues.apache.org/jira/browse/CLOUDSTACK-5092>`_"
+msgstr ""
+
+# d7b8970346074c11956828f012538721
+#: ../../source/about.rst:626
+msgid ""
+"[Automation] [BVT] Failed to copy template and ISO between zones in xen ..."
+msgstr ""
+
+# 004c1f58b369468aadf01d00d08d4778
+#: ../../source/about.rst:627
+msgid ""
+"`CLOUDSTACK-5076 <https://issues.apache.org/jira/browse/CLOUDSTACK-5076>`_"
+msgstr ""
+
+# 1e532b576ee34201b4f5c2d9ae8e18ea
+#: ../../source/about.rst:627
+msgid "(Upgrade) reboot VM failed after bridge name change..."
+msgstr ""
+
+# bd115062edf44791a9f01372999f5db0
+#: ../../source/about.rst:628
+msgid ""
+"`CLOUDSTACK-5069 <https://issues.apache.org/jira/browse/CLOUDSTACK-5069>`_"
+msgstr ""
+
+# 201a29d9cbd64bddac6272d6cc4edf5e
+#: ../../source/about.rst:628
+msgid "Make VMware vCenter session timeout value configurable...."
+msgstr ""
+
+# 873b01cf76a34e23807c12cf4029e712
+#: ../../source/about.rst:629
+msgid ""
+"`CLOUDSTACK-5066 <https://issues.apache.org/jira/browse/CLOUDSTACK-5066>`_"
+msgstr ""
+
+# 4df823c4757d4c73a89b70da9eaaf208
+#: ../../source/about.rst:629
+msgid "Existed remote access VPN got dropped when adding new VPN users..."
+msgstr ""
+
+# c8c1e8ef17d941b19257cd795098d730
+#: ../../source/about.rst:630
+msgid ""
+"`CLOUDSTACK-5062 <https://issues.apache.org/jira/browse/CLOUDSTACK-5062>`_"
+msgstr ""
+
+# 3060b3b742bc43e5b2db246945778900
+#: ../../source/about.rst:630
+msgid ""
+"Deleting Load Balancing Rule fails when generating usage events are "
+"enabled..."
+msgstr ""
+
+# 94ff72e916b6406ba3fdccc90b74a998
+#: ../../source/about.rst:631
+msgid ""
+"`CLOUDSTACK-5054 <https://issues.apache.org/jira/browse/CLOUDSTACK-5054>`_"
+msgstr ""
+
+# 5469eeb03bd24ea7be6dddeb7941ce70
+#: ../../source/about.rst:631
+msgid ""
+"vm migration involving storage migration on vmware fails with exception \" "
+"The ob..."
+msgstr ""
+
+# 31e5de517da3422fad6f9d176db1405e
+#: ../../source/about.rst:632
+msgid ""
+"`CLOUDSTACK-5053 <https://issues.apache.org/jira/browse/CLOUDSTACK-5053>`_"
+msgstr ""
+
+# f4ead44a795e4f63b93568a1ef2dbe23
+#: ../../source/about.rst:632
+msgid ""
+"No Qemu-KVM module dependency error message is displayed (if not "
+"present)while i..."
+msgstr ""
+
+# f194e896bf65498f9e770ceea800eb47
+#: ../../source/about.rst:633
+msgid ""
+"`CLOUDSTACK-5042 <https://issues.apache.org/jira/browse/CLOUDSTACK-5042>`_"
+msgstr ""
+
+# b3db8dde60ec4d43a23cb3193b83671d
+#: ../../source/about.rst:633
+msgid "(Upgrade) Exception when stop VM after upgrade..."
+msgstr ""
+
+# e320d3d15e8742b281b9430647682a46
+#: ../../source/about.rst:634
+msgid ""
+"`CLOUDSTACK-5029 <https://issues.apache.org/jira/browse/CLOUDSTACK-5029>`_"
+msgstr ""
+
+# 9b78735e219647ecb6e4121874923ba0
+#: ../../source/about.rst:634
+msgid "cloud-bugtool isn't in release package like release notes say..."
+msgstr ""
+
+# f73a527a09a641e0a89bcb5dd5df6a70
+#: ../../source/about.rst:635
+msgid ""
+"`CLOUDSTACK-5025 <https://issues.apache.org/jira/browse/CLOUDSTACK-5025>`_"
+msgstr ""
+
+# 4f35f586f1014ead82ae5ece2c6160d4
+#: ../../source/about.rst:635
+msgid "display_volume field is set to false by default for VolumeVO object..."
+msgstr ""
+
+# bd6bad68bd8644068e464b0ca9940501
+#: ../../source/about.rst:636
+msgid ""
+"`CLOUDSTACK-5024 <https://issues.apache.org/jira/browse/CLOUDSTACK-5024>`_"
+msgstr ""
+
+# 743628c9d47b446899bc219665414d48
+#: ../../source/about.rst:636
+msgid "listVolumes: add support to list by storage pool (for admin only)..."
+msgstr ""
+
+# 1c6cd0cd3bd34f75b304f705189eee5b
+#: ../../source/about.rst:637
+msgid ""
+"`CLOUDSTACK-5017 <https://issues.apache.org/jira/browse/CLOUDSTACK-5017>`_"
+msgstr ""
+
+# 21e6d0344e384e93af60eedc1c95d025
+#: ../../source/about.rst:637
+msgid ""
+"If SSVM is unavailable DownloadCommands will be routed to mgmt server..."
+msgstr ""
+
+# 106e4d150fca46548a921121b8552ebf
+#: ../../source/about.rst:638
+msgid ""
+"`CLOUDSTACK-5014 <https://issues.apache.org/jira/browse/CLOUDSTACK-5014>`_"
+msgstr ""
+
+# c1c06cbc7b7c45c8af3faf073aa4c991
+#: ../../source/about.rst:638
+msgid "vmware:deployVM with data disk failed with exception..."
+msgstr ""
+
+# e7d63ff16c2046458443bc10404cdf5c
+#: ../../source/about.rst:639
+msgid ""
+"`CLOUDSTACK-5012 <https://issues.apache.org/jira/browse/CLOUDSTACK-5012>`_"
+msgstr ""
+
+# d873cf938a3c4588b1ad22cb38d966e6
+#: ../../source/about.rst:639
+msgid ""
+"Bad data inserted into physical network labels for Zone Create Wizard using "
+"VMWa..."
+msgstr ""
+
+# 44f0b675b80844d78bd1b0cf4c2602f1
+#: ../../source/about.rst:640
+msgid ""
+"`CLOUDSTACK-5008 <https://issues.apache.org/jira/browse/CLOUDSTACK-5008>`_"
+msgstr ""
+
+# 520d0a23384c43ad9ba8b114ba00bec0
+#: ../../source/about.rst:640
+msgid ""
+"[VMWARE]Failed to start the VM after performing Cold Migration of Volume to "
+"Seco..."
+msgstr ""
+
+# 0dc8152d6730441486a5927b0a420f45
+#: ../../source/about.rst:641
+msgid ""
+"`CLOUDSTACK-5002 <https://issues.apache.org/jira/browse/CLOUDSTACK-5002>`_"
+msgstr ""
+
+# 053453e3b3504bbfaedf20c4bb0e2ffa
+#: ../../source/about.rst:641
+msgid ""
+"unable to destroy vm ;VM destroy failed in Stop i-2-59-VM Command due to You"
+" gav..."
+msgstr ""
+
+# 0c1534937df04783863c12c8ea9fd5af
+#: ../../source/about.rst:642
+msgid ""
+"`CLOUDSTACK-4998 <https://issues.apache.org/jira/browse/CLOUDSTACK-4998>`_"
+msgstr ""
+
+# 44ca48de62084240bf964891f8d91084
+#: ../../source/about.rst:642
+msgid ""
+"assignVirtualMachine API has wrong response string, causing Cloudmonkey to "
+"crash..."
+msgstr ""
+
+# b165202bd702464f9c0062410600b217
+#: ../../source/about.rst:643
+msgid ""
+"`CLOUDSTACK-4997 <https://issues.apache.org/jira/browse/CLOUDSTACK-4997>`_"
+msgstr ""
+
+# 751efa544bfe4144a946b354e8d1b7fc
+#: ../../source/about.rst:643
+msgid "OVS integration is broken..."
+msgstr ""
+
+# 3365f820f0154735848cc957377d28db
+#: ../../source/about.rst:644
+msgid ""
+"`CLOUDSTACK-4973 <https://issues.apache.org/jira/browse/CLOUDSTACK-4973>`_"
+msgstr ""
+
+# 43b720ee34574961ba2a783388b3ee85
+#: ../../source/about.rst:644
+msgid ""
+"CLONE - Specified keyboard language is not showing as default in consoleView"
+" pas..."
+msgstr ""
+
+# 76841734ecc640bb96fd7680b1563078
+#: ../../source/about.rst:645
+msgid ""
+"`CLOUDSTACK-4943 <https://issues.apache.org/jira/browse/CLOUDSTACK-4943>`_"
+msgstr ""
+
+# 9ca6bd3e17964e12866d455d9ebebf14
+#: ../../source/about.rst:645
+msgid "Can't create cluster in CS 4.2..."
+msgstr ""
+
+# bd705a1009d94e85bc3bbc92e3571883
+#: ../../source/about.rst:646
+msgid ""
+"`CLOUDSTACK-4941 <https://issues.apache.org/jira/browse/CLOUDSTACK-4941>`_"
+msgstr ""
+
+# f219f7b41bef495783c016384eba1f70
+#: ../../source/about.rst:646
+msgid "CLONE - Allocation capacity of a cluster during HA..."
+msgstr ""
+
+# 0bf7140f09e34bf39cdf16a8dba7e8aa
+#: ../../source/about.rst:647
+msgid ""
+"`CLOUDSTACK-4935 <https://issues.apache.org/jira/browse/CLOUDSTACK-4935>`_"
+msgstr ""
+
+# b54751f9c5f346159ded2322cd083c12
+#: ../../source/about.rst:647
+msgid ""
+"Adding same network to VM multiple times resulting in failure, No new NIC is"
+" gen..."
+msgstr ""
+
+# 288ede58b88f4a44a62e84d0564ef548
+#: ../../source/about.rst:648
+msgid ""
+"`CLOUDSTACK-4931 <https://issues.apache.org/jira/browse/CLOUDSTACK-4931>`_"
+msgstr ""
+
+# 9cd3def4e5c4459bb8b037ce49201bbe
+#: ../../source/about.rst:648
+msgid "observed NPE with new system vm template..."
+msgstr ""
+
+# 40df03649369499a82facb5b80d76d15
+#: ../../source/about.rst:649
+msgid ""
+"`CLOUDSTACK-4913 <https://issues.apache.org/jira/browse/CLOUDSTACK-4913>`_"
+msgstr ""
+
+# 50063d38e7044b28bc202bcad30ef60d
+#: ../../source/about.rst:649
+msgid "Disable security group for bridge mode non-security group zone..."
+msgstr ""
+
+# 4d60c977aee442c0828040726b5b5cb9
+#: ../../source/about.rst:650
+msgid ""
+"`CLOUDSTACK-4904 <https://issues.apache.org/jira/browse/CLOUDSTACK-4904>`_"
+msgstr ""
+
+# f2c08b23f8514bb4a654e0e131c7bfdb
+#: ../../source/about.rst:650
+msgid "Unable to see a derieved template if the parent template is deleted..."
+msgstr ""
+
+# 94fe5dbb1fbf486f967848000ef334e3
+#: ../../source/about.rst:651
+msgid ""
+"`CLOUDSTACK-4886 <https://issues.apache.org/jira/browse/CLOUDSTACK-4886>`_"
+msgstr ""
+
+# 48e094d65c2d4db8bc0b1af394b47e9b
+#: ../../source/about.rst:651
+msgid "cloud-setup-databases not escaping password in shell commands..."
+msgstr ""
+
+# a7bd797ba5374738bd101205b9520bba
+#: ../../source/about.rst:652
+msgid ""
+"`CLOUDSTACK-4875 <https://issues.apache.org/jira/browse/CLOUDSTACK-4875>`_"
+msgstr ""
+
+# efbb305d0d4244bb8e8270e48c238675
+#: ../../source/about.rst:652
+msgid "VMWARE: vCenter 5.5 - SYSTEM VM: Unable to create deployment for VM..."
+msgstr ""
+
+# 3db2f47d361945629fc4133855dbe711
+#: ../../source/about.rst:653
+msgid ""
+"`CLOUDSTACK-4861 <https://issues.apache.org/jira/browse/CLOUDSTACK-4861>`_"
+msgstr ""
+
+# a1dca318726a483790923516842f006f
+#: ../../source/about.rst:653
+msgid ""
+"[VMware] If Guest traffic spans across multiple physical networks, selection"
+" of ..."
+msgstr ""
+
+# f07f072323bc4da1a3998c97b752446f
+#: ../../source/about.rst:654
+msgid ""
+"`CLOUDSTACK-4860 <https://issues.apache.org/jira/browse/CLOUDSTACK-4860>`_"
+msgstr ""
+
+# 3331a070c17641b9baa8eba24f39e027
+#: ../../source/about.rst:654
+msgid ""
+"[VMware] Vcenter 5.5 ESXi 5.5 hosts SSVM CPVM fail to come up to running "
+"state..."
+msgstr ""
+
+# b1a22187b1a34e2f9f7c3ed20f9549cd
+#: ../../source/about.rst:655
+msgid ""
+"`CLOUDSTACK-4856 <https://issues.apache.org/jira/browse/CLOUDSTACK-4856>`_"
+msgstr ""
+
+# 0d860e5e5465443ab5cbc279941f4799
+#: ../../source/about.rst:655
+msgid "Optimize on the # of control commands sent by MS to HV host..."
+msgstr ""
+
+# 1986f7ca366147eea5655d40ecc3b04b
+#: ../../source/about.rst:656
+msgid ""
+"`CLOUDSTACK-4855 <https://issues.apache.org/jira/browse/CLOUDSTACK-4855>`_"
+msgstr ""
+
+# d8b6b377887a49078a87d4934cb0c5b2
+#: ../../source/about.rst:656
+msgid ""
+"Throttle based on the # of outstanding requests to the directly managed HV "
+"host ..."
+msgstr ""
+
+# ace6d729c9a347039689dbfb671a7db2
+#: ../../source/about.rst:657
+msgid ""
+"`CLOUDSTACK-4852 <https://issues.apache.org/jira/browse/CLOUDSTACK-4852>`_"
+msgstr ""
+
+# a7c7f58008064196b9ef81802d190912
+#: ../../source/about.rst:657
+msgid ""
+"Since upgrade to 4.2 only users at the zone-attached domain level can "
+"manipulate..."
+msgstr ""
+
+# 3ef2e904b3724f25946444b875b33ca8
+#: ../../source/about.rst:658
+msgid ""
+"`CLOUDSTACK-4850 <https://issues.apache.org/jira/browse/CLOUDSTACK-4850>`_"
+msgstr ""
+
+# 396d89f57f094a9eb05780f82aca46c2
+#: ../../source/about.rst:658
+msgid "[UCS] using template instead of cloning profile..."
+msgstr ""
+
+# 97e99c8db0ab47518e8244339fc79ea2
+#: ../../source/about.rst:659
+msgid ""
+"`CLOUDSTACK-4831 <https://issues.apache.org/jira/browse/CLOUDSTACK-4831>`_"
+msgstr ""
+
+# e8705ef095a743af8d34cee3c08c9d4b
+#: ../../source/about.rst:659
+msgid ""
+"Ability for root admin or domain admin to create a network for another user "
+"unde..."
+msgstr ""
+
+# 0a8853feef814405ab4fdeababe07f8f
+#: ../../source/about.rst:660
+msgid ""
+"`CLOUDSTACK-4830 <https://issues.apache.org/jira/browse/CLOUDSTACK-4830>`_"
+msgstr ""
+
+# 7686478ec62442f4954e65c222a76857
+#: ../../source/about.rst:660
+msgid "Allow creation of users and accounts by domain admin in UI..."
+msgstr ""
+
+# 89ec38d9ea2f4efaa90577169d767f25
+#: ../../source/about.rst:661
+msgid ""
+"`CLOUDSTACK-4826 <https://issues.apache.org/jira/browse/CLOUDSTACK-4826>`_"
+msgstr ""
+
+# 5a6f5d6b27b143caab84daa377d5f3b3
+#: ../../source/about.rst:661
+msgid "System VMs fail to start..."
+msgstr ""
+
+# a1ca9f02ab344945ba6826cad7b62387
+#: ../../source/about.rst:662
+msgid ""
+"`CLOUDSTACK-4820 <https://issues.apache.org/jira/browse/CLOUDSTACK-4820>`_"
+msgstr ""
+
+# 42b23f5cd1ff4f2fb82095c17098de86
+#: ../../source/about.rst:662
+msgid "TestVPCNetworkGc.test_01_wait_network_gc netacls are not cleared..."
+msgstr ""
+
+# 1f715d85fe7d4a3993ce6c2ac3103db7
+#: ../../source/about.rst:663
+msgid ""
+"`CLOUDSTACK-4810 <https://issues.apache.org/jira/browse/CLOUDSTACK-4810>`_"
+msgstr ""
+
+# 3020a6c5bcf247dca12e7bc04bd35fac
+#: ../../source/about.rst:663
+msgid ""
+"Enable hypervisor snapshots for CloudStack-managed storage (for XenServer "
+"and VM..."
+msgstr ""
+
+# c19348ffa02841ff9aaf5826c143e3c4
+#: ../../source/about.rst:664
+msgid ""
+"`CLOUDSTACK-4768 <https://issues.apache.org/jira/browse/CLOUDSTACK-4768>`_"
+msgstr ""
+
+# 985b19a402434e738b68be045aa7735f
+#: ../../source/about.rst:664
+msgid ""
+"[Automation] Race condition; delete the template and create VM at same time;"
+" dep..."
+msgstr ""
+
+# 7da707f12aae4f58a0a9bfd20d56c022
+#: ../../source/about.rst:665
+msgid ""
+"`CLOUDSTACK-4750 <https://issues.apache.org/jira/browse/CLOUDSTACK-4750>`_"
+msgstr ""
+
+# f86c4137fc674be28ec489ceacde4c6b
+#: ../../source/about.rst:665
+msgid ""
+"bond.VLAN mapping in iptables FORWARD chain not created consistently..."
+msgstr ""
+
+# 0eac77f58b024384b9b2323da9b461ef
+#: ../../source/about.rst:666
+msgid ""
+"`CLOUDSTACK-4741 <https://issues.apache.org/jira/browse/CLOUDSTACK-4741>`_"
+msgstr ""
+
+# cd3a4178a7aa4f34a1fc5f9efd23430b
+#: ../../source/about.rst:666
+msgid "URL of ImageStore not in proper format for XenServer..."
+msgstr ""
+
+# 32f7a75fd1684a58834d560355aee533
+#: ../../source/about.rst:667
+msgid ""
+"`CLOUDSTACK-4740 <https://issues.apache.org/jira/browse/CLOUDSTACK-4740>`_"
+msgstr ""
+
+# e173fab183e54f7f8d0946f1d5a364dc
+#: ../../source/about.rst:667
+msgid "Some vSphere VMs are shutdown when ACS is restarted..."
+msgstr ""
+
+# 11e7e9a029b14a1d90e21afa855d50b7
+#: ../../source/about.rst:668
+msgid ""
+"`CLOUDSTACK-4734 <https://issues.apache.org/jira/browse/CLOUDSTACK-4734>`_"
+msgstr ""
+
+# 928bafc602cc4e249b5c35ecde4de613
+#: ../../source/about.rst:668
+msgid ""
+"Creating snapshot from ROOT volume fails with error message - \"Failed to "
+"create ..."
+msgstr ""
+
+# 7890167612e34986a8e34f16d16c3606
+#: ../../source/about.rst:669
+msgid ""
+"`CLOUDSTACK-4724 <https://issues.apache.org/jira/browse/CLOUDSTACK-4724>`_"
+msgstr ""
+
+# cf6deee2da574a29bc246387eb220994
+#: ../../source/about.rst:669
+msgid ""
+"[Vmware] Deploy VM in designated cluster fail if there is only zone wide "
+"primary..."
+msgstr ""
+
+# 0af44808879744438424b87023a63d52
+#: ../../source/about.rst:670
+msgid ""
+"`CLOUDSTACK-4697 <https://issues.apache.org/jira/browse/CLOUDSTACK-4697>`_"
+msgstr ""
+
+# 73c11d2899994de499f0400ef1f79ba4
+#: ../../source/about.rst:670
+msgid ""
+"Not able to delete Primary storage when there are no hosts in the "
+"cluster...."
+msgstr ""
+
+# 145d8ef8f20643519e9b5f9630fc9ef5
+#: ../../source/about.rst:671
+msgid ""
+"`CLOUDSTACK-4676 <https://issues.apache.org/jira/browse/CLOUDSTACK-4676>`_"
+msgstr ""
+
+# 03a27d5dbde94757992a9d62174efe57
+#: ../../source/about.rst:671
+msgid ""
+"[Baremetal] baremetal hostename should not be fixed in kickstart file ..."
+msgstr ""
+
+# 0f7ecdc731b84b5ca9dfea4f744bd6b3
+#: ../../source/about.rst:672
+msgid ""
+"`CLOUDSTACK-4670 <https://issues.apache.org/jira/browse/CLOUDSTACK-4670>`_"
+msgstr ""
+
+# cde3cf5c56a44c6aae3cf4a14dc8429b
+#: ../../source/about.rst:672
+msgid "[Baremetal] Cloudplatform BareMetal installation guide for CP 4.2..."
+msgstr ""
+
+# 667abdf5e91e4ec694f358065cb7280c
+#: ../../source/about.rst:673
+msgid ""
+"`CLOUDSTACK-4631 <https://issues.apache.org/jira/browse/CLOUDSTACK-4631>`_"
+msgstr ""
+
+# b5f413db87f640449e1903245c3857c4
+#: ../../source/about.rst:673
+msgid ""
+"[Automation] Failed to create snapshot from volume due to storage pool "
+"missing e..."
+msgstr ""
+
+# 4697ac3b30f046fdba4ce9d4272aa9f7
+#: ../../source/about.rst:674
+msgid ""
+"`CLOUDSTACK-4620 <https://issues.apache.org/jira/browse/CLOUDSTACK-4620>`_"
+msgstr ""
+
+# 62fd40c677994ea1b9ea6d365ceae37c
+#: ../../source/about.rst:674
+msgid ""
+"Vm failed to start on the host on which it was running due to not having "
+"enough ..."
+msgstr ""
+
+# 4fd407a308b943a3ba4af67369a57a50
+#: ../../source/about.rst:675
+msgid ""
+"`CLOUDSTACK-4616 <https://issues.apache.org/jira/browse/CLOUDSTACK-4616>`_"
+msgstr ""
+
+# c92db2b2b0094f998358a3f938959952
+#: ../../source/about.rst:675
+msgid ""
+"When system Vms fail to start when host is down , link local Ip addresses "
+"do no..."
+msgstr ""
+
+# 3334341e3f95462cb70d4fcbb799008c
+#: ../../source/about.rst:676
+msgid ""
+"`CLOUDSTACK-4598 <https://issues.apache.org/jira/browse/CLOUDSTACK-4598>`_"
+msgstr ""
+
+# c16926ef451a4382bd6ea85b24a251bf
+#: ../../source/about.rst:676
+msgid ""
+"[Performance Testing] High delays during deployVM - both network delay and "
+"deplo..."
+msgstr ""
+
+# 5cf4f9326a044b60a18beba4c8c91602
+#: ../../source/about.rst:677
+msgid ""
+"`CLOUDSTACK-4597 <https://issues.apache.org/jira/browse/CLOUDSTACK-4597>`_"
+msgstr ""
+
+# f0754bc0e8024924a616f859fdd59b45
+#: ../../source/about.rst:677
+msgid ""
+"Complete Exceptions are getting displayed in the UI where there is an "
+"operationa..."
+msgstr ""
+
+# 453666aace0245fb83d2fdabde741f64
+#: ../../source/about.rst:678
+msgid ""
+"`CLOUDSTACK-4594 <https://issues.apache.org/jira/browse/CLOUDSTACK-4594>`_"
+msgstr ""
+
+# 9bd53a36b8d94a91a1509bf32ff3e25b
+#: ../../source/about.rst:678
+msgid ""
+"[VMWARE] [Upgrade] Failed to revert VM Snapshot which were created before "
+"Live S..."
+msgstr ""
+
+# 37d2c89b7b294dfdac3a085d20b1e243
+#: ../../source/about.rst:679
+msgid ""
+"`CLOUDSTACK-4588 <https://issues.apache.org/jira/browse/CLOUDSTACK-4588>`_"
+msgstr ""
+
+# 4695e57fb34641619f4965dc2afbeb35
+#: ../../source/about.rst:679
+msgid ""
+"[Automation][Vmware] VM deployment failed while creating Volume with NPE..."
+msgstr ""
+
+# 157a709278454369926e2f89e06b5c06
+#: ../../source/about.rst:680
+msgid ""
+"`CLOUDSTACK-4577 <https://issues.apache.org/jira/browse/CLOUDSTACK-4577>`_"
+msgstr ""
+
+# 69ccd745c5034e23badd4c4ba0529666
+#: ../../source/about.rst:680
+msgid ""
+"VMWare:Volumes: Unexpected exception while executing "
+"org.apache.cloudstack.api.c..."
+msgstr ""
+
+# 88d9b768bf67453ca27bf4674329f967
+#: ../../source/about.rst:681
+msgid ""
+"`CLOUDSTACK-4543 <https://issues.apache.org/jira/browse/CLOUDSTACK-4543>`_"
+msgstr ""
+
+# 3b12eb6e07a14ba4b437559435b4dad3
+#: ../../source/about.rst:681
+msgid ""
+"[Automation] Failed to configure VPC router then reported as deployment "
+"failure..."
+msgstr ""
+
+# 039b646e54644a698b30d4784869c907
+#: ../../source/about.rst:682
+msgid ""
+"`CLOUDSTACK-4542 <https://issues.apache.org/jira/browse/CLOUDSTACK-4542>`_"
+msgstr ""
+
+# 5472eb10e3c04f25aac3e83c3b833098
+#: ../../source/about.rst:682
+msgid ""
+"[Automation] Failed to apply DHCP entry in VR and deployment failed ..."
+msgstr ""
+
+# 56636f214ab94b2b9364cceee5564aa8
+#: ../../source/about.rst:683
+msgid ""
+"`CLOUDSTACK-4540 <https://issues.apache.org/jira/browse/CLOUDSTACK-4540>`_"
+msgstr ""
+
+# 1b92aed958b74d3e8a344c3837210a94
+#: ../../source/about.rst:683
+msgid ""
+"[Automation] Parallel deployment - Vmware - When deploying 30 parallel Vms ,"
+" 16 ..."
+msgstr ""
+
+# c534c6651c3a4b67a36ddd1d12b53f5a
+#: ../../source/about.rst:684
+msgid ""
+"`CLOUDSTACK-4506 <https://issues.apache.org/jira/browse/CLOUDSTACK-4506>`_"
+msgstr ""
+
+# 32a72acd3c9e4ca18bd5e21fc5d4d498
+#: ../../source/about.rst:684
+msgid ""
+"In a mixed hypervisor setup, destroying a VM whose host has been removed, "
+"throws..."
+msgstr ""
+
+# 2574475ed4894b169cc616c9757df7e1
+#: ../../source/about.rst:685
+msgid ""
+"`CLOUDSTACK-4504 <https://issues.apache.org/jira/browse/CLOUDSTACK-4504>`_"
+msgstr ""
+
+# 17ac9f41f94a4787a88e46048541f978
+#: ../../source/about.rst:685
+msgid "VM creation Is failing using the Ubuntu ISO with Xen 6.1 and 6.2..."
+msgstr ""
+
+# 071f6e25a6c24726a4501ec4d4fbdca8
+#: ../../source/about.rst:686
+msgid ""
+"`CLOUDSTACK-4450 <https://issues.apache.org/jira/browse/CLOUDSTACK-4450>`_"
+msgstr ""
+
+# 67f3965b26c540a5aaf5b473ad14bf55
+#: ../../source/about.rst:686
+msgid "Possibility of /tmp/xapilog filling up the Root disk on Xenserver ..."
+msgstr ""
+
+# 1e5e0138da8e4740aad1606105615d30
+#: ../../source/about.rst:687
+msgid ""
+"`CLOUDSTACK-4445 <https://issues.apache.org/jira/browse/CLOUDSTACK-4445>`_"
+msgstr ""
+
+# d40e66393a4e472e845030576d929b82
+#: ../../source/about.rst:687
+msgid ""
+"[UI]Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter "
+"with ..."
+msgstr ""
+
+# 049082d03a484ee89ed5a8e31c70ee8d
+#: ../../source/about.rst:688
+msgid ""
+"`CLOUDSTACK-4428 <https://issues.apache.org/jira/browse/CLOUDSTACK-4428>`_"
+msgstr ""
+
+# 5e95e0dafbc641159675b77a29255830
+#: ../../source/about.rst:688
+msgid ""
+"[UI] \"kvm.snapshot.enabled\" flag should be taken to account only when "
+"snapshot i..."
+msgstr ""
+
+# db4b5894acab4aeaae4abc6cf7ec2c8f
+#: ../../source/about.rst:689
+msgid ""
+"`CLOUDSTACK-4402 <https://issues.apache.org/jira/browse/CLOUDSTACK-4402>`_"
+msgstr ""
+
+# cff757b824084cdbb5d13ef7d93660b0
+#: ../../source/about.rst:689
+msgid ""
+"[deleteStoragePool] There is no way to delete Primary storage if the last "
+"host w..."
+msgstr ""
+
+# 358bc13d832d4f5e9efa9bcf1b029e90
+#: ../../source/about.rst:690
+msgid ""
+"`CLOUDSTACK-4371 <https://issues.apache.org/jira/browse/CLOUDSTACK-4371>`_"
+msgstr ""
+
+# bb406cad9cad4129bd7290537cbf34e9
+#: ../../source/about.rst:690
+msgid ""
+"[Performance Testing] Basic zone with 20K Hosts, management server restart "
+"leave..."
+msgstr ""
+
+# 8496515c969c4f51a90d03791bde0dd6
+#: ../../source/about.rst:691
+msgid ""
+"`CLOUDSTACK-4263 <https://issues.apache.org/jira/browse/CLOUDSTACK-4263>`_"
+msgstr ""
+
+# 3a6d44ecf59d4ddb8ccdeaf1e4c53aaf
+#: ../../source/about.rst:691
+msgid ""
+"Unable to get git number in maven-jgit-buildnumber-plugin, while build "
+"cloudstac..."
+msgstr ""
+
+# f1b45e7268e44b1c87ad2ee9bcedb6d8
+#: ../../source/about.rst:692
+msgid ""
+"`CLOUDSTACK-4207 <https://issues.apache.org/jira/browse/CLOUDSTACK-4207>`_"
+msgstr ""
+
+# 77c10218109d4e149359c2e0b3567172
+#: ../../source/about.rst:692
+msgid ""
+"[upgrade] Exception observed after upgrade \"jsonParseException: The "
+"JsonDeserial..."
+msgstr ""
+
+# cd44625942934af58f400507be510739
+#: ../../source/about.rst:693
+msgid ""
+"`CLOUDSTACK-4061 <https://issues.apache.org/jira/browse/CLOUDSTACK-4061>`_"
+msgstr ""
+
+# 357916ee164e428294530f5987c8a187
+#: ../../source/about.rst:693
+msgid "UI issue with Japanese localized ui..."
+msgstr ""
+
+# 22bbd529bca24b96bd07ffa0f9b8c787
+#: ../../source/about.rst:694
+msgid ""
+"`CLOUDSTACK-3806 <https://issues.apache.org/jira/browse/CLOUDSTACK-3806>`_"
+msgstr ""
+
+# 369f0e717ad34af7abf2ab4e56f5ddfa
+#: ../../source/about.rst:694
+msgid "OS Preference can not be set..."
+msgstr ""
+
+# 7d083ac7ff4649d48dc85c2b918c2ea5
+#: ../../source/about.rst:695
+msgid ""
+"`CLOUDSTACK-3664 <https://issues.apache.org/jira/browse/CLOUDSTACK-3664>`_"
+msgstr ""
+
+# 1742af2678b74066a7a7fb5fd44a40c1
+#: ../../source/about.rst:695
+msgid ""
+"scaling up vms is not considering parameter "
+"\"cluster.(memory/cpu).allocated.cap..."
+msgstr ""
+
+# bbc5466710ca4998b4ae768b26f7ba45
+#: ../../source/about.rst:696
+msgid ""
+"`CLOUDSTACK-3627 <https://issues.apache.org/jira/browse/CLOUDSTACK-3627>`_"
+msgstr ""
+
+# cf1d52b8df914a52b25911c0b30c04ec
+#: ../../source/about.rst:696
+msgid ""
+"Public IP interface(eth2) is not getting confugured with Redundant VR (State"
+" = F..."
+msgstr ""
+
+# 1a30502e895d418f87d3de62eaecbe9c
+#: ../../source/about.rst:697
+msgid ""
+"`CLOUDSTACK-3577 <https://issues.apache.org/jira/browse/CLOUDSTACK-3577>`_"
+msgstr ""
+
+# e409cf02dfa94762afdd935586293d34
+#: ../../source/about.rst:697
+msgid "NPE while downloading the template to secondary storage ..."
+msgstr ""
+
+# e88aaa831b5040e9b3fdc9638df27812
+#: ../../source/about.rst:698
+msgid ""
+"`CLOUDSTACK-3561 <https://issues.apache.org/jira/browse/CLOUDSTACK-3561>`_"
+msgstr ""
+
+# c5143675c68841e3a9728daed8909738
+#: ../../source/about.rst:698
+msgid ""
+"When inputting the nfs server in secondary storage, if once it's required, "
+"it al..."
+msgstr ""
+
+# b1b2aeef4f8242299a4f6a3a4ea96e78
+#: ../../source/about.rst:699
+msgid ""
+"`CLOUDSTACK-3364 <https://issues.apache.org/jira/browse/CLOUDSTACK-3364>`_"
+msgstr ""
+
+# 4ad750e7dbb047b8b07ed0dcd818bf1c
+#: ../../source/about.rst:699
+msgid "normal users are not allowed to edit their own iso..."
+msgstr ""
+
+# c83f08aa21e445a2a809095652291596
+#: ../../source/about.rst:700
+msgid ""
+"`CLOUDSTACK-3266 <https://issues.apache.org/jira/browse/CLOUDSTACK-3266>`_"
+msgstr ""
+
+# 5d607746c3044e5898a739e273c53dbf
+#: ../../source/about.rst:700
+msgid "[UI] Failed to delete Anti affinitygroup for the first time ..."
+msgstr ""
+
+# 6c5fb4e3cb8d41efabd53ea9d4875113
+#: ../../source/about.rst:701
+msgid ""
+"`CLOUDSTACK-3252 <https://issues.apache.org/jira/browse/CLOUDSTACK-3252>`_"
+msgstr ""
+
+# 7e7fbee9c3bf454aa1035e4a5cbd6069
+#: ../../source/about.rst:701
+msgid ""
+"An instance deployed using explicit or implicit dedication doesn't generate "
+"a us..."
+msgstr ""
+
+# cd30639f36b143979e1c9e621d907e93
+#: ../../source/about.rst:702
+msgid ""
+"`CLOUDSTACK-3247 <https://issues.apache.org/jira/browse/CLOUDSTACK-3247>`_"
+msgstr ""
+
+# 54ea50df69504905a0de6b0d8e1fbb04
+#: ../../source/about.rst:702
+msgid "Removing a Disconnected Host throws a NoTransitionException..."
+msgstr ""
+
+# a92ec174b7e04766888f105eeac567e4
+#: ../../source/about.rst:703
+msgid ""
+"`CLOUDSTACK-3156 <https://issues.apache.org/jira/browse/CLOUDSTACK-3156>`_"
+msgstr ""
+
+# 5ee8331a5eac4e2da77a48f437946769
+#: ../../source/about.rst:703
+msgid ""
+"needs proper message for failing Add nic command when vmware tools is not "
+"instal..."
+msgstr ""
+
+# 25ca28a795fc4b8c96b23838bbfa1c4c
+#: ../../source/about.rst:704
+msgid ""
+"`CLOUDSTACK-3067 <https://issues.apache.org/jira/browse/CLOUDSTACK-3067>`_"
+msgstr ""
+
+# 3936325267264d2c8fcad752f36a5d52
+#: ../../source/about.rst:704
+msgid ""
+"UI for Dedicating POD/Cluster/Host is misleading Icons should be changed...."
+msgstr ""
+
+# 0467a816c7bf4cae98e8592cc05fb416
+#: ../../source/about.rst:705
+msgid ""
+"`CLOUDSTACK-3027 <https://issues.apache.org/jira/browse/CLOUDSTACK-3027>`_"
+msgstr ""
+
+# db28767273df46f5a44fd6a3e3cafbe1
+#: ../../source/about.rst:705
+msgid ""
+"Object_Store_Refactor - Uploaded template S3 content-type is not "
+"appropriate...."
+msgstr ""
+
+# d33375b70acd478e94cd8a2de29e1823
+#: ../../source/about.rst:706
+msgid ""
+"`CLOUDSTACK-2895 <https://issues.apache.org/jira/browse/CLOUDSTACK-2895>`_"
+msgstr ""
+
+# b467c19429b64bfb968265590c68fec4
+#: ../../source/about.rst:706
+msgid "Can't start a VM with 3 volumes attached [VMWare]..."
+msgstr ""
+
+# 458fbbd7b8d74e15b3a60d5bc4c68294
+#: ../../source/about.rst:707
+msgid ""
+"`CLOUDSTACK-2766 <https://issues.apache.org/jira/browse/CLOUDSTACK-2766>`_"
+msgstr ""
+
+# 1d13f52a0b524f0fb7bccf62a88bb6ac
+#: ../../source/about.rst:707
+msgid ""
+"[VPC] [UI] Firewall service should not be enabled for acquired public IPs in"
+" VPC..."
+msgstr ""
+
+# 67dc347e005942029fa6e4a3f0f53cfc
+#: ../../source/about.rst:708
+msgid ""
+"`CLOUDSTACK-2687 <https://issues.apache.org/jira/browse/CLOUDSTACK-2687>`_"
+msgstr ""
+
+# 659cd98957394947a9b9d1a0d50b9cb5
+#: ../../source/about.rst:708
+msgid "NPE with deploy VM when there are no resources available ..."
+msgstr ""
+
+# 7c071cb5d5c3491194406655ce442ee4
+#: ../../source/about.rst:709
+msgid ""
+"`CLOUDSTACK-2570 <https://issues.apache.org/jira/browse/CLOUDSTACK-2570>`_"
+msgstr ""
+
+# c618bcf561424423b3e8ed9513991856
+#: ../../source/about.rst:709
+msgid "[UI]Resource Name is mentioned twice with view VNMC devices ..."
+msgstr ""
+
+# bc176885c1f44074a7f06cc967923073
+#: ../../source/about.rst:710
+msgid ""
+"`CLOUDSTACK-2562 <https://issues.apache.org/jira/browse/CLOUDSTACK-2562>`_"
+msgstr ""
+
+# 77896d6ccbae452a8ea30d2b88e2854f
+#: ../../source/about.rst:710
+msgid ""
+"[VMWARE] As per the code, currently CloudStack fails to program PF/NAT/LB "
+"rules ..."
+msgstr ""
+
+# c64206bc17404ddb85d30956a73a9851
+#: ../../source/about.rst:711
+msgid ""
+"`CLOUDSTACK-2428 <https://issues.apache.org/jira/browse/CLOUDSTACK-2428>`_"
+msgstr ""
+
+# 15c21a5396e7428b928fd0ad2dec879a
+#: ../../source/about.rst:711
+msgid ""
+"HA - When the master host is disconnected , the host status contines to "
+"remain i..."
+msgstr ""
+
+# c1e0bb3d6cd14f7cad809f89124ec29f
+#: ../../source/about.rst:712
+msgid ""
+"`CLOUDSTACK-2414 <https://issues.apache.org/jira/browse/CLOUDSTACK-2414>`_"
+msgstr ""
+
+# 2462b5477c724f3ab1860d4b0d648bf9
+#: ../../source/about.rst:712
+msgid "NPE while deleting Cisco VNMC provider..."
+msgstr ""
+
+# bbcc4c4c254649548a9b7017ffd5f54b
+#: ../../source/about.rst:713
+msgid ""
+"`CLOUDSTACK-2396 <https://issues.apache.org/jira/browse/CLOUDSTACK-2396>`_"
+msgstr ""
+
+# ab8b5846107641e6bd4794c71072af44
+#: ../../source/about.rst:713
+msgid ""
+"PVLAN - Should not be allowed to create multiple networks with same Vlan "
+"associ..."
+msgstr ""
+
+# c26425b5adf5400b982c3b0f11222b65
+#: ../../source/about.rst:714
+msgid ""
+"`CLOUDSTACK-2199 <https://issues.apache.org/jira/browse/CLOUDSTACK-2199>`_"
+msgstr ""
+
+# 0e2dcf9c5d19426e91f38d78a01f6134
+#: ../../source/about.rst:714
+msgid ""
+"ID parameter of UpdateConfiguration API should be changed to a different "
+"name..."
+msgstr ""
+
+# 7da963c6455a4725be0a34b50f6af338
+#: ../../source/about.rst:715
+msgid ""
+"`CLOUDSTACK-2141 <https://issues.apache.org/jira/browse/CLOUDSTACK-2141>`_"
+msgstr ""
+
+# af2de82c111640f29d8b72b4cd715f2b
+#: ../../source/about.rst:715
+msgid ""
+"During HA process , dead lock is detected - Caused by: "
+"com.mysql.jdbc.exception..."
+msgstr ""
+
+# 71832ade3b2541e1a3a3f609916a3e09
+#: ../../source/about.rst:716
+msgid ""
+"`CLOUDSTACK-1970 <https://issues.apache.org/jira/browse/CLOUDSTACK-1970>`_"
+msgstr ""
+
+# 5eec0dac3c8e42cf8b35868520332856
+#: ../../source/about.rst:716
+msgid "Ubuntu - \"cloudstack-setup-management\" not available in \"/usr/bin\"..."
+msgstr ""
+
+# 00c3e308c6904047b8cbc487f0957c66
+#: ../../source/about.rst:717
+msgid ""
+"`CLOUDSTACK-1889 <https://issues.apache.org/jira/browse/CLOUDSTACK-1889>`_"
+msgstr ""
+
+# 46653b8619e94ee2b8fd443df5747252
+#: ../../source/about.rst:717
+msgid ""
+"[UI] Consumed Resource usage details are not available for all the "
+"resources..."
+msgstr ""
+
+# 435bd9414777490f963054f53dbfa732
+#: ../../source/about.rst:718
+msgid ""
+"`CLOUDSTACK-1868 <https://issues.apache.org/jira/browse/CLOUDSTACK-1868>`_"
+msgstr ""
+
+# ac34caaa2aa7456eb62b1153d3571437
+#: ../../source/about.rst:718
+msgid "GetVmStatsCommand throws NullPointerException with VMWare..."
+msgstr ""
+
+# ab08172d39bc4c8bb9ab7cfa91000aad
+#: ../../source/about.rst:719
+msgid ""
+"`CLOUDSTACK-1762 <https://issues.apache.org/jira/browse/CLOUDSTACK-1762>`_"
+msgstr ""
+
+# fa3918f4d12f4481b74feccf226c23a4
+#: ../../source/about.rst:719
+msgid ""
+"[MultipleIpsToNic] addIpToNic should not let network id or broadcast to be "
+"assig..."
+msgstr ""
+
+# a509940809894b098bf385cc0a1da0f9
+#: ../../source/about.rst:720
+msgid ""
+"`CLOUDSTACK-1637 <https://issues.apache.org/jira/browse/CLOUDSTACK-1637>`_"
+msgstr ""
+
+# 963e03e004924de6a0ad38347e175932
+#: ../../source/about.rst:720
+msgid "LDAP:UI related issues..."
+msgstr ""
+
+# 0c3a1e330c8845ffb89d50ea264e8bed
+#: ../../source/about.rst:725
+msgid "Known Issues in 4.3.0"
+msgstr ""
+
+# d49bf145822b4f7dbef86a3a9d10e73b
+#: ../../source/about.rst:730
+msgid ""
+"For the list of known issues, see `Known Issues in 4.3 "
+"<https://issues.apache.org/jira/issues/?filter=12326162>`__."
+msgstr ""
+
+# 9366049c09cd445383d5d3ff85fcfb48
+#: ../../source/about.rst:736
+msgid ""
+"`CLOUDSTACK-4787 <https://issues.apache.org/jira/browse/CLOUDSTACK-4787>`_"
+msgstr ""
+
+# 8f4aeece6e1949989637c4efb79361b7
+#: ../../source/about.rst:736
+msgid "Allow selection of scsi controller type in vSphere..."
+msgstr ""
+
+# 5e4334fb180140568515e19db4fb5645
+#: ../../source/about.rst:737
+msgid ""
+"`CLOUDSTACK-6024 <https://issues.apache.org/jira/browse/CLOUDSTACK-6024>`_"
+msgstr ""
+
+# 8602cd20a2354d4f91c8d2d0707183bb
+#: ../../source/about.rst:737
+msgid ""
+"template copy to primary storage uses a random source secstorage from any "
+"zone..."
+msgstr ""
+
+# f965b5e733914160b9ba6fe86889ab33
+#: ../../source/about.rst:738
+msgid ""
+"`CLOUDSTACK-4912 <https://issues.apache.org/jira/browse/CLOUDSTACK-4912>`_"
+msgstr ""
+
+# a1bf258b622a402ea444b5919c2ada89
+#: ../../source/about.rst:738
+msgid "API docs are missing some APIs..."
+msgstr ""
+
+# f4d27c0e199746149129573d2409e273
+#: ../../source/about.rst:739
+msgid ""
+"`CLOUDSTACK-5124 <https://issues.apache.org/jira/browse/CLOUDSTACK-5124>`_"
+msgstr ""
+
+# 59001f906d4145838d36157c00a43716
+#: ../../source/about.rst:739
+msgid ""
+"Simulator: Virtual Router fails to start because of improper version "
+"returned by..."
+msgstr ""
+
+# 03066b547eb54b3e9a813a9491f53014
+#: ../../source/about.rst:740
+msgid ""
+"`CLOUDSTACK-5262 <https://issues.apache.org/jira/browse/CLOUDSTACK-5262>`_"
+msgstr ""
+
+# 61588455ea394b2aa5b2afd63c36fdf1
+#: ../../source/about.rst:740
+msgid ""
+"Few of the snapshot creation from ROOT volume fails when there are "
+"concurrent s..."
+msgstr ""
+
+# db7a1464b27641759dda869318e2d66a
+#: ../../source/about.rst:741
+msgid ""
+"`CLOUDSTACK-5356 <https://issues.apache.org/jira/browse/CLOUDSTACK-5356>`_"
+msgstr ""
+
+# 6e5a774deda34f439d5151cca1613c90
+#: ../../source/about.rst:741
+msgid ""
+"Xenserver - Failed to create snapshot when secondary store was made "
+"unavaibale f..."
+msgstr ""
+
+# b169a6830c64467a81a216b7c91bda40
+#: ../../source/about.rst:742
+msgid ""
+"`CLOUDSTACK-5357 <https://issues.apache.org/jira/browse/CLOUDSTACK-5357>`_"
+msgstr ""
+
+# 639986b439614db69e1d2e284d807ef5
+#: ../../source/about.rst:742
+msgid ""
+"Xenserver - Failed to create snapshot due to \"unable to destroy task(com.xe"
+" nsou..."
+msgstr ""
+
+# a91d75be88df483796e1289a7e3c7a9e
+#: ../../source/about.rst:743
+msgid ""
+"`CLOUDSTACK-5358 <https://issues.apache.org/jira/browse/CLOUDSTACK-5358>`_"
+msgstr ""
+
+# 87905fa46444475494cafe06a0178dcd
+#: ../../source/about.rst:743
+msgid "API: synchronization on the object is broken..."
+msgstr ""
+
+# c7d0b0c97c5d4bbdbad1c314d11c0089
+#: ../../source/about.rst:744
+msgid ""
+"`CLOUDSTACK-5372 <https://issues.apache.org/jira/browse/CLOUDSTACK-5372>`_"
+msgstr ""
+
+# 7882d7ff87ce46f081e356266833e989
+#: ../../source/about.rst:744
+msgid ""
+"Xenserver - SR not being recreated when the Primary storage is brought down "
+"and ..."
+msgstr ""
+
+# aea6fd27cdd94067b91a6baa77f0e78d
+#: ../../source/about.rst:745
+msgid ""
+"`CLOUDSTACK-5429 <https://issues.apache.org/jira/browse/CLOUDSTACK-5429>`_"
+msgstr ""
+
+# 6ca255d358d74a50a6e1635ce01c4c44
+#: ../../source/about.rst:745
+msgid ""
+"KVM - Primary store down/Network Failure - Hosts attempt to reboot becasue "
+"of pr..."
+msgstr ""
+
+# 62580c63110445e6b3e09b759fd56529
+#: ../../source/about.rst:746
+msgid ""
+"`CLOUDSTACK-5452 <https://issues.apache.org/jira/browse/CLOUDSTACK-5452>`_"
+msgstr ""
+
+# 4b181d14ded84b0987e71ad7a35d2efa
+#: ../../source/about.rst:746
+msgid ""
+"KVM - Agent is not able to connect back if management server was restarted "
+"when ..."
+msgstr ""
+
+# 96d8d6353aed48399f7193a12ceaa1d3
+#: ../../source/about.rst:747
+msgid ""
+"`CLOUDSTACK-5469 <https://issues.apache.org/jira/browse/CLOUDSTACK-5469>`_"
+msgstr ""
+
+# ccaa41bf6df4493bb14aa484e0269e59
+#: ../../source/about.rst:747
+msgid ""
+"Snapshot creation fails with following exception - \"Failed to backup "
+"snapshot: q..."
+msgstr ""
+
+# f13914ea540540dc8b1cb2811ab717f8
+#: ../../source/about.rst:748
+msgid ""
+"`CLOUDSTACK-5485 <https://issues.apache.org/jira/browse/CLOUDSTACK-5485>`_"
+msgstr ""
+
+# ed7ee25313b34426a38202561e527859
+#: ../../source/about.rst:748
+msgid ""
+"Vmware - Whe 10 hourly snapshots are scheduled at the same time , we see "
+"only 5 ..."
+msgstr ""
+
+# 9c0601c9e7734b3593c81d6e3396b073
+#: ../../source/about.rst:749
+msgid ""
+"`CLOUDSTACK-5494 <https://issues.apache.org/jira/browse/CLOUDSTACK-5494>`_"
+msgstr ""
+
+# 016b4e349c89418fa43c2cfa53759562
+#: ../../source/about.rst:749
+msgid "the dns resolver servers on the VRs are open to the world..."
+msgstr ""
+
+# 272abcf1004f4d209efcc245feca90b0
+#: ../../source/about.rst:750
+msgid ""
+"`CLOUDSTACK-5499 <https://issues.apache.org/jira/browse/CLOUDSTACK-5499>`_"
+msgstr ""
+
+# e1ae770626f24c2788147ebac0d4092d
+#: ../../source/about.rst:750
+msgid ""
+"Vmware -When nfs was down for about 12 hours and then brought back up again"
+" , s..."
+msgstr ""
+
+# a7a4a00d0a5f4879a9c07b323a76de7b
+#: ../../source/about.rst:751
+msgid ""
+"`CLOUDSTACK-5501 <https://issues.apache.org/jira/browse/CLOUDSTACK-5501>`_"
+msgstr ""
+
+# d0029106dc174d67bcb58ff30405375a
+#: ../../source/about.rst:751
+msgid ""
+"Unable to create more than one vpnConnection per vpn customer gateway..."
+msgstr ""
+
+# 4d36f1778bcd42e8a63a7de46295da9c
+#: ../../source/about.rst:752
+msgid ""
+"`CLOUDSTACK-5582 <https://issues.apache.org/jira/browse/CLOUDSTACK-5582>`_"
+msgstr ""
+
+# 074eb077241a471bbaa787ec57a6d5fc
+#: ../../source/about.rst:752
+msgid ""
+"kvm - HA is not triggered when host is powered down since the host gets into"
+" \"Di..."
+msgstr ""
+
+# 11e36e96a0e9432d97e85bdcae499039
+#: ../../source/about.rst:753
+msgid ""
+"`CLOUDSTACK-5746 <https://issues.apache.org/jira/browse/CLOUDSTACK-5746>`_"
+msgstr ""
+
+# e29f0b375c4e48cf82bfb437e6616cd0
+#: ../../source/about.rst:753
+msgid "[HyperV]Can't access vm console from IE browser..."
+msgstr ""
+
+# 0fa77f8beda54ce0a337ae8879c42f23
+#: ../../source/about.rst:754
+msgid ""
+"`CLOUDSTACK-5806 <https://issues.apache.org/jira/browse/CLOUDSTACK-5806>`_"
+msgstr ""
+
+# b80d04f5490d492aac1b9934e3fd3294
+#: ../../source/about.rst:754
+msgid "Storage types other than NFS/VMFS can't overprovision..."
+msgstr ""
+
+# 2853d64408e04d3eb896ed972c38abd0
+#: ../../source/about.rst:755
+msgid ""
+"`CLOUDSTACK-5818 <https://issues.apache.org/jira/browse/CLOUDSTACK-5818>`_"
+msgstr ""
+
+# 99081480a4ef41b6b485d636882ee694
+#: ../../source/about.rst:755
+msgid ""
+"[Hyper-v]Agent status of the System VMs is not updated during Host "
+"disconnect..."
+msgstr ""
+
+# 434b86def9994569910c09996b8d278f
+#: ../../source/about.rst:756
+msgid ""
+"`CLOUDSTACK-5825 <https://issues.apache.org/jira/browse/CLOUDSTACK-5825>`_"
+msgstr ""
+
+# 9dfa20e5f2f14461afb9244de60120c0
+#: ../../source/about.rst:756
+msgid "Create snapshot API always returns success..."
+msgstr ""
+
+# d9bb41e319ed4634aa76e4ed027b26a5
+#: ../../source/about.rst:757
+msgid ""
+"`CLOUDSTACK-5882 <https://issues.apache.org/jira/browse/CLOUDSTACK-5882>`_"
+msgstr ""
+
+# 0624959c7b944f2597d55d6e5d83672e
+#: ../../source/about.rst:757
+msgid "UI has different fonts and font sizes..."
+msgstr ""
+
+# 16861eac1095422a8364dbcf40e80951
+#: ../../source/about.rst:758
+msgid ""
+"`CLOUDSTACK-5899 <https://issues.apache.org/jira/browse/CLOUDSTACK-5899>`_"
+msgstr ""
+
+# 19c21bee456e483499bf251830708f61
+#: ../../source/about.rst:758
+msgid ""
+"Contrail:MS: Exceptions in MS logs on a fresh install, syncDomain "
+"java.lang.Nul..."
+msgstr ""
+
+# a904c1e9f7ac4cc5ae6f113b3dd1a8e7
+#: ../../source/about.rst:759
+msgid ""
+"`CLOUDSTACK-5928 <https://issues.apache.org/jira/browse/CLOUDSTACK-5928>`_"
+msgstr ""
+
+# e5d40dceeaca4d9199780829785762c2
+#: ../../source/about.rst:759
+msgid ""
+"[VM Sync] - Vmware - When a Vm is \"suspended\" from outside of CloudStack ,"
+" this ..."
+msgstr ""
+
+# cb709ada209f452791d9f0d642c0aa74
+#: ../../source/about.rst:760
+msgid ""
+"`CLOUDSTACK-5929 <https://issues.apache.org/jira/browse/CLOUDSTACK-5929>`_"
+msgstr ""
+
+# 1ac61e7f25724ab8bb94a59ab49e207a
+#: ../../source/about.rst:760
+msgid ""
+"[VM Sync] - Vmware - Even when starting Vm fails, startVirtualMachine async "
+"job ..."
+msgstr ""
+
+# 9f92e99b84c84965982641964e138eb2
+#: ../../source/about.rst:761
+msgid ""
+"`CLOUDSTACK-5961 <https://issues.apache.org/jira/browse/CLOUDSTACK-5961>`_"
+msgstr ""
+
+# d35722d202414d76a3bcbf24200b1117
+#: ../../source/about.rst:761
+msgid "CLONE - API: synchronization on the object is broken..."
+msgstr ""
+
+# 00a0213f26594b95b9a9017d9dae6570
+#: ../../source/about.rst:762
+msgid ""
+"`CLOUDSTACK-6050 <https://issues.apache.org/jira/browse/CLOUDSTACK-6050>`_"
+msgstr ""
+
+# 45f672667c7d4b6c918f227f43f52c91
+#: ../../source/about.rst:762
+msgid "A limitations on min-max on CPU/RAM for a dynamic offering ..."
+msgstr ""
+
+# 6365b06a722d4c96ae245cbee93ed394
+#: ../../source/about.rst:763
+msgid ""
+"`CLOUDSTACK-6051 <https://issues.apache.org/jira/browse/CLOUDSTACK-6051>`_"
+msgstr ""
+
+# 3a190cc12bfe44e4b53e6e035f3c117e
+#: ../../source/about.rst:763
+msgid ""
+"VR Rolling upgrade: Make the numbers of Routers parallely being upgraded as "
+"conf..."
+msgstr ""
+
+# a25ebfc86f2841f19ac5cc04d3dde867
+#: ../../source/about.rst:764
+msgid ""
+"`CLOUDSTACK-6063 <https://issues.apache.org/jira/browse/CLOUDSTACK-6063>`_"
+msgstr ""
+
+# f12e5b103586477ea4c4c4d1994cf44e
+#: ../../source/about.rst:764
+msgid ""
+"CLONE - Non windows instances are created on XenServer with a vcpu-max above"
+" sup..."
+msgstr ""
+
+# 4f9e0035a6b44f5d92b00503a47655b0
+#: ../../source/about.rst:765
+msgid ""
+"`CLOUDSTACK-6065 <https://issues.apache.org/jira/browse/CLOUDSTACK-6065>`_"
+msgstr ""
+
+# 6b71991d62c44dd0bde9b4a9fbd0c5fb
+#: ../../source/about.rst:765
+msgid "No HA for shutdown VM..."
+msgstr ""
+
+# 425db0f637ed4915afa530fcc3375ed4
+#: ../../source/about.rst:766
+msgid ""
+"`CLOUDSTACK-6079 <https://issues.apache.org/jira/browse/CLOUDSTACK-6079>`_"
+msgstr ""
+
+# d2f5c21ec6f542b08638f6669400297d
+#: ../../source/about.rst:766
+msgid ""
+"a broadcast type of a public network is affected by another physical "
+"network's i..."
+msgstr ""
+
+# ab87957eba284769b16e2f313d52fb73
+#: ../../source/about.rst:767
+msgid "`CLOUDSTACK-77 <https://issues.apache.org/jira/browse/CLOUDSTACK-77>`_"
+msgstr ""
+
+# 58e41ab8179b4b9782269462459007da
+#: ../../source/about.rst:767
+msgid "console proxy display issues..."
+msgstr ""
+
+# 8db0e533f7cd4cfcab081bf4bc00f742
+#: ../../source/about.rst:768
+msgid ""
+"`CLOUDSTACK-107 <https://issues.apache.org/jira/browse/CLOUDSTACK-107>`_"
+msgstr ""
+
+# 30415dcf674a4e8aae51521111db2666
+#: ../../source/about.rst:768
+msgid ""
+"Network domain guest suffix is not getting programmed as part of hostnames "
+"on Gu..."
+msgstr ""
+
+# 0478485b947a42d893c510be01d98ecf
+#: ../../source/about.rst:769
+msgid ""
+"`CLOUDSTACK-237 <https://issues.apache.org/jira/browse/CLOUDSTACK-237>`_"
+msgstr ""
+
+# 71b1b10c10114813847cf99866792d9e
+#: ../../source/about.rst:769
+msgid ""
+"StopVMCommand reported success in spite of failing to stop a VM which got "
+"stuck ..."
+msgstr ""
+
+# 1136090c600443d19756782e8d7818ca
+#: ../../source/about.rst:770
+msgid ""
+"`CLOUDSTACK-238 <https://issues.apache.org/jira/browse/CLOUDSTACK-238>`_"
+msgstr ""
+
+# f0f5e9f088734e87b56c111932fbb7dd
+#: ../../source/about.rst:770
+msgid "vpn:fail to connect to vpnserver using non-sourceNAT IP..."
+msgstr ""
+
+# 942ec655385b4572a2d114289ea139e3
+#: ../../source/about.rst:771
+msgid ""
+"`CLOUDSTACK-252 <https://issues.apache.org/jira/browse/CLOUDSTACK-252>`_"
+msgstr ""
+
+# 7485de1c33634d6e83be7b5071b36494
+#: ../../source/about.rst:771
+msgid ""
+"UpdateNetwork Operation on a guest network that is currently using Virtual "
+"Route..."
+msgstr ""
+
+# 3dafae3e04bf4f4f9f60119b05e19fa4
+#: ../../source/about.rst:772
+msgid ""
+"`CLOUDSTACK-255 <https://issues.apache.org/jira/browse/CLOUDSTACK-255>`_"
+msgstr ""
+
+# 12c7e710aa264aae858df1d2f23aa4b4
+#: ../../source/about.rst:772
+msgid ""
+"Null pointer exception while creating portforwarding rule after performing "
+"Updat..."
+msgstr ""
+
+# 3b8c83c736c5459fbf7eb523af102016
+#: ../../source/about.rst:773
+msgid ""
+"`CLOUDSTACK-317 <https://issues.apache.org/jira/browse/CLOUDSTACK-317>`_"
+msgstr ""
+
+# 993dc0a2fb404658869813b95da84503
+#: ../../source/about.rst:773
+msgid "get xcp 1.5 into an advanced network zone..."
+msgstr ""
+
+# e47c93e7c1f942d7b05c707e5d541587
+#: ../../source/about.rst:774
+msgid ""
+"`CLOUDSTACK-375 <https://issues.apache.org/jira/browse/CLOUDSTACK-375>`_"
+msgstr ""
+
+# b37d48fbcffa459ca04e8ef145b73afd
+#: ../../source/about.rst:774
+msgid ""
+"Unable to delete physical network - because there are other networks "
+"attached..."
+msgstr ""
+
+# 4af711936fee4c988e113d781befa5cb
+#: ../../source/about.rst:775
+msgid ""
+"`CLOUDSTACK-425 <https://issues.apache.org/jira/browse/CLOUDSTACK-425>`_"
+msgstr ""
+
+# 393010e91cff45e3a01cd9f1e91fef89
+#: ../../source/about.rst:775
+msgid "Check image type is qcow2 before actually installing..."
+msgstr ""
+
+# 34e77b0e2b3241709397cd2790f01ade
+#: ../../source/about.rst:776
+msgid ""
+"`CLOUDSTACK-992 <https://issues.apache.org/jira/browse/CLOUDSTACK-992>`_"
+msgstr ""
+
+# 966a5c0fa5e3493fa34da35be918c192
+#: ../../source/about.rst:776
+msgid "Template creations dies after 2h for no reason..."
+msgstr ""
+
+# 98af046f690c46b38720f7d61a8b0f1d
+#: ../../source/about.rst:777
+msgid ""
+"`CLOUDSTACK-1007 <https://issues.apache.org/jira/browse/CLOUDSTACK-1007>`_"
+msgstr ""
+
+# d7b482d0c9624fc78beeaa15f5c127b5
+#: ../../source/about.rst:777
+msgid ""
+"Not able to delete Shared network because of not being able to stop the "
+"router...."
+msgstr ""
+
+# 86304829cdb74cafac6f27e592dc3a5e
+#: ../../source/about.rst:778
+msgid ""
+"`CLOUDSTACK-1091 <https://issues.apache.org/jira/browse/CLOUDSTACK-1091>`_"
+msgstr ""
+
+# 79b006800d5b4773a79bc902f5181ade
+#: ../../source/about.rst:778
+msgid "Fix API server's parsing mechanism for POST requests..."
+msgstr ""
+
+# b9fee6af60f0460095dbe2e830e303ab
+#: ../../source/about.rst:779
+msgid ""
+"`CLOUDSTACK-1092 <https://issues.apache.org/jira/browse/CLOUDSTACK-1092>`_"
+msgstr ""
+
+# 1c7f9eabb70044efb0095a5ab168ad14
+#: ../../source/about.rst:779
+msgid "Fix API Server's parsing mechanism to parse GET request as multimap..."
+msgstr ""
+
+# 5c8b082a719b4ea190d97f9454d05cf1
+#: ../../source/about.rst:780
+msgid ""
+"`CLOUDSTACK-1309 <https://issues.apache.org/jira/browse/CLOUDSTACK-1309>`_"
+msgstr ""
+
+# 559f925366694f0b89250fb27f32252f
+#: ../../source/about.rst:780
+msgid "Large guest subnets downgrade performance..."
+msgstr ""
+
+# 5f09bbec09ec4d3385a78688bdc27c53
+#: ../../source/about.rst:781
+msgid ""
+"`CLOUDSTACK-1389 <https://issues.apache.org/jira/browse/CLOUDSTACK-1389>`_"
+msgstr ""
+
+# 54ac55f5877b4fe581e6db4a65028984
+#: ../../source/about.rst:781
+msgid "Interactive Password Prompts during Management Server Startup..."
+msgstr ""
+
+# 5bce4bad1fba4599bfa6d89c78408789
+#: ../../source/about.rst:782
+msgid ""
+"`CLOUDSTACK-1413 <https://issues.apache.org/jira/browse/CLOUDSTACK-1413>`_"
+msgstr ""
+
+# 96a2b2ec34734bf7ac5d5cdaaf74598e
+#: ../../source/about.rst:782
+msgid ""
+"Need something to concretely identify the version of the code in a "
+"particular bu..."
+msgstr ""
+
+# 0d69c0bd10494513a62d811f6e46d372
+#: ../../source/about.rst:783
+msgid ""
+"`CLOUDSTACK-1527 <https://issues.apache.org/jira/browse/CLOUDSTACK-1527>`_"
+msgstr ""
+
+# bf2038111b4540a0b3d454d47c7b495e
+#: ../../source/about.rst:783
+msgid ""
+"Non-fatal POSTIN scriptlet failure in rpm package cloudstack-"
+"management-4.2.0-SN..."
+msgstr ""
+
+# 3fb20b2036564c1fa19718e401ea7e83
+#: ../../source/about.rst:784
+msgid ""
+"`CLOUDSTACK-1717 <https://issues.apache.org/jira/browse/CLOUDSTACK-1717>`_"
+msgstr ""
+
+# 66b9fd5c669949f28ba4638fd8a1ad5f
+#: ../../source/about.rst:784
+msgid ""
+"AWS Regions - Local region entry that gets added by default should not "
+"include \"..."
+msgstr ""
+
+# 9f7e62b1e16f4ed88d7e06a1725bc1c8
+#: ../../source/about.rst:785
+msgid ""
+"`CLOUDSTACK-1885 <https://issues.apache.org/jira/browse/CLOUDSTACK-1885>`_"
+msgstr ""
+
+# 1291d9e7d55f4db68ea3774192f71614
+#: ../../source/about.rst:785
+msgid "Broken testcases in 4.1..."
+msgstr ""
+
+# ccec471c679e418abd739c1c91ead940
+#: ../../source/about.rst:786
+msgid ""
+"`CLOUDSTACK-1990 <https://issues.apache.org/jira/browse/CLOUDSTACK-1990>`_"
+msgstr ""
+
+# ed34d5ff52e649e4bd6f2d925cc5949b
+#: ../../source/about.rst:786
+msgid "Docs: Update \"Choosing a Hypervisor\" feature matrix with new info..."
+msgstr ""
+
+# 35938d7b4f394c97babe38ce2952e5b4
+#: ../../source/about.rst:787
+msgid ""
+"`CLOUDSTACK-2004 <https://issues.apache.org/jira/browse/CLOUDSTACK-2004>`_"
+msgstr ""
+
+# f0263264fe1c40de9d674a91656bbdf5
+#: ../../source/about.rst:787
+msgid ""
+"IPV6 - UI - Router details page - NICs tab - Guest traffic type does not "
+"displa..."
+msgstr ""
+
+# de60a69d430a410e8bc57691c7e9e619
+#: ../../source/about.rst:788
+msgid ""
+"`CLOUDSTACK-2009 <https://issues.apache.org/jira/browse/CLOUDSTACK-2009>`_"
+msgstr ""
+
+# 6567c71b940444929ac6185fe5bb21a6
+#: ../../source/about.rst:788
+msgid ""
+"IPV6 - listNetwork() command does not return ip6dns1 and ip6dns2 entries...."
+msgstr ""
+
+# 22c97b1b399c4edbbf740a5c69fda2fb
+#: ../../source/about.rst:789
+msgid ""
+"`CLOUDSTACK-2022 <https://issues.apache.org/jira/browse/CLOUDSTACK-2022>`_"
+msgstr ""
+
+# 3fea24a0775c43cf95dccc0964b92813
+#: ../../source/about.rst:789
+msgid ""
+"IPV6 - ListRouter() should return guestip6address parameter similar to "
+"guestaddr..."
+msgstr ""
+
+# 0ed5b14f0cd74aada5e8ba7d6d3a52cd
+#: ../../source/about.rst:790
+msgid ""
+"`CLOUDSTACK-2023 <https://issues.apache.org/jira/browse/CLOUDSTACK-2023>`_"
+msgstr ""
+
+# bc0faed231f8441982734fa1a09de47d
+#: ../../source/about.rst:790
+msgid ""
+"IPV6 - Dashboard View - System wide Capacity for Shared Network IPs does not"
+" inc..."
+msgstr ""
+
+# fa7dcf3381784c058080b779c7dad0eb
+#: ../../source/about.rst:791
+msgid ""
+"`CLOUDSTACK-2026 <https://issues.apache.org/jira/browse/CLOUDSTACK-2026>`_"
+msgstr ""
+
+# 8d920ff504164433a5cb8d14b28b20f3
+#: ../../source/about.rst:791
+msgid ""
+"IPV6 - UI - Provide the ability to turn off all the IPV6 parameters by using"
+" a g..."
+msgstr ""
+
+# 793844374b9a4717af4e3a96efc78646
+#: ../../source/about.rst:792
+msgid ""
+"`CLOUDSTACK-2099 <https://issues.apache.org/jira/browse/CLOUDSTACK-2099>`_"
+msgstr ""
+
+# ee4a3ac2203c445ab4c40c86bb151e00
+#: ../../source/about.rst:792
+msgid ""
+"Not able to add a host after a failed attempt to add the host to a wrong "
+"cluster..."
+msgstr ""
+
+# ab446ac6458242128fdee362ba605323
+#: ../../source/about.rst:793
+msgid ""
+"`CLOUDSTACK-2112 <https://issues.apache.org/jira/browse/CLOUDSTACK-2112>`_"
+msgstr ""
+
+# 5d41a79c37984b4aa387d67f332aecea
+#: ../../source/about.rst:793
+msgid ""
+"VM went in stopped state after live migration failed while vmscaleup..."
+msgstr ""
+
+# fcb182c9bf924f4f853a7063df6c72fe
+#: ../../source/about.rst:794
+msgid ""
+"`CLOUDSTACK-2191 <https://issues.apache.org/jira/browse/CLOUDSTACK-2191>`_"
+msgstr ""
+
+# 7c79e43a414c41c78f5a9c4edbad126d
+#: ../../source/about.rst:794
+msgid "sanity tests for \"EIP : Optional public IP\" changes ..."
+msgstr ""
+
+# dd24fc75a09e42b689b41a385c5b1fcb
+#: ../../source/about.rst:795
+msgid ""
+"`CLOUDSTACK-2291 <https://issues.apache.org/jira/browse/CLOUDSTACK-2291>`_"
+msgstr ""
+
+# d0ad039c438f49f0b9c19c61ad06491f
+#: ../../source/about.rst:795
+msgid "[BasicZone-XenServer] NPE while trying DeleteNetworkCmd..."
+msgstr ""
+
+# 1cd9814861e94fe0b12bba775d9ccf0c
+#: ../../source/about.rst:796
+msgid ""
+"`CLOUDSTACK-2293 <https://issues.apache.org/jira/browse/CLOUDSTACK-2293>`_"
+msgstr ""
+
+# d6d7e68458b34ace9167b0faaac4ab7a
+#: ../../source/about.rst:796
+msgid ""
+"[BasicZone-XenServer] DeletePhysicalNetworkCmd is not deleting the external "
+"devi..."
+msgstr ""
+
+# 18827dbf664d49208a18c18850a873b2
+#: ../../source/about.rst:797
+msgid ""
+"`CLOUDSTACK-2412 <https://issues.apache.org/jira/browse/CLOUDSTACK-2412>`_"
+msgstr ""
+
+# 38571b8b919d4bbfb91db330b39bb3be
+#: ../../source/about.rst:797
+msgid ""
+"[UI]Disable CiscoVnmc provider for PF/SourceNat/StaticNAT/Firewall dropdown "
+"list..."
+msgstr ""
+
+# ec84d91d357c45958e085d92b444cc27
+#: ../../source/about.rst:798
+msgid ""
+"`CLOUDSTACK-2418 <https://issues.apache.org/jira/browse/CLOUDSTACK-2418>`_"
+msgstr ""
+
+# 2a694e0fae5f464995bacd104ed7e193
+#: ../../source/about.rst:798
+msgid "[GSLB] NPE while removing the GSLB enabled Netscaler device..."
+msgstr ""
+
+# 51a98d1f52684b31a511fb501b9763d4
+#: ../../source/about.rst:799
+msgid ""
+"`CLOUDSTACK-2471 <https://issues.apache.org/jira/browse/CLOUDSTACK-2471>`_"
+msgstr ""
+
+# 31313e3102a543f8b28ddd44d0962e8e
+#: ../../source/about.rst:799
+msgid ""
+"test_host_high_availability.py refers to non-existent library method "
+"wait_for_vm..."
+msgstr ""
+
+# ada6fc26d9624177be27b1c639f95f84
+#: ../../source/about.rst:800
+msgid ""
+"`CLOUDSTACK-2501 <https://issues.apache.org/jira/browse/CLOUDSTACK-2501>`_"
+msgstr ""
+
+# 124c3850029149ab96dc7947c674eddd
+#: ../../source/about.rst:800
+msgid "Scalevm - Need to take care of upgraded vms..."
+msgstr ""
+
+# 1aae5d9479fe40478d8cacdbc0e587ff
+#: ../../source/about.rst:801
+msgid ""
+"`CLOUDSTACK-2790 <https://issues.apache.org/jira/browse/CLOUDSTACK-2790>`_"
+msgstr ""
+
+# 4ed9bf78e0704a0d8d93f6058c104a7a
+#: ../../source/about.rst:801
+msgid ""
+"AWSAPI: packaging includes all .class files bloating size of the RPM..."
+msgstr ""
+
+# 5f5c0509b8f146d08c9c9a76f2156c52
+#: ../../source/about.rst:802
+msgid ""
+"`CLOUDSTACK-2795 <https://issues.apache.org/jira/browse/CLOUDSTACK-2795>`_"
+msgstr ""
+
+# 7e9640a68f5247a99469683531916949
+#: ../../source/about.rst:802
+msgid "Create template failed..."
+msgstr ""
+
+# 2849f81c404843a8a81855096a962d69
+#: ../../source/about.rst:803
+msgid ""
+"`CLOUDSTACK-2845 <https://issues.apache.org/jira/browse/CLOUDSTACK-2845>`_"
+msgstr ""
+
+# dcdfe224c84442a3b2b41bff5da1d588
+#: ../../source/about.rst:803
+msgid ""
+"[DB upgrade] [ExternalLoadBalancer NetworkUsage] Duplicate entries in the "
+"databa..."
+msgstr ""
+
+# 98217b63240548688393be2e88a4f377
+#: ../../source/about.rst:804
+msgid ""
+"`CLOUDSTACK-2853 <https://issues.apache.org/jira/browse/CLOUDSTACK-2853>`_"
+msgstr ""
+
+# c6bd19a7a73f4e4abf00dc6a7cde162d
+#: ../../source/about.rst:804
+msgid ""
+"Cloudstack copies xenserver scripts while adding host even the server is KVM"
+" hos..."
+msgstr ""
+
+# 941394cdf67944659f3889c78f57f9f8
+#: ../../source/about.rst:805
+msgid ""
+"`CLOUDSTACK-2860 <https://issues.apache.org/jira/browse/CLOUDSTACK-2860>`_"
+msgstr ""
+
+# 1628ad0620cd49e9924a86968ad1ee4f
+#: ../../source/about.rst:805
+msgid "Add new host into VMWare Cluster failed..."
+msgstr ""
+
+# 39c55e252fa041eb82425bb91a7b3c76
+#: ../../source/about.rst:806
+msgid ""
+"`CLOUDSTACK-2910 <https://issues.apache.org/jira/browse/CLOUDSTACK-2910>`_"
+msgstr ""
+
+# a529078d75fa46cca5b9cb18ce79b52e
+#: ../../source/about.rst:806
+msgid "SC: Ctrl combinated with >. is not working of SC IME..."
+msgstr ""
+
+# bf922c06163b4b50864a6a3959455269
+#: ../../source/about.rst:807
+msgid ""
+"`CLOUDSTACK-2911 <https://issues.apache.org/jira/browse/CLOUDSTACK-2911>`_"
+msgstr ""
+
+# 0aaf8d4c57c2465ba91c081c21e2b55a
+#: ../../source/about.rst:807
+msgid ""
+"KO: Key translation fails for KO keyboard Right Alt, Han/Eng, Hanja keys..."
+msgstr ""
+
+# 3597495e5a5a4f57aa03ba72c8567952
+#: ../../source/about.rst:808
+msgid ""
+"`CLOUDSTACK-2919 <https://issues.apache.org/jira/browse/CLOUDSTACK-2919>`_"
+msgstr ""
+
+# 573fb7c3a40a4c928742e4ecf3387082
+#: ../../source/about.rst:808
+msgid ""
+"Snapshot cannot be saved to full Secondary Storage, but doesn't utilize "
+"other Se..."
+msgstr ""
+
+# cffb645f459945fd9dc9c0e49fa44321
+#: ../../source/about.rst:809
+msgid ""
+"`CLOUDSTACK-3066 <https://issues.apache.org/jira/browse/CLOUDSTACK-3066>`_"
+msgstr ""
+
+# d0f03d5f754e4379b06b3c6de68648c7
+#: ../../source/about.rst:809
+msgid ""
+"No Error message is popped up on UI when a dedicated resource is dedicated "
+"to an..."
+msgstr ""
+
+# 38f4839bebaf467d9783473f01c3a3e5
+#: ../../source/about.rst:810
+msgid ""
+"`CLOUDSTACK-3095 <https://issues.apache.org/jira/browse/CLOUDSTACK-3095>`_"
+msgstr ""
+
+# 3f91537181d94b4dbfa476a7c9677bbc
+#: ../../source/about.rst:810
+msgid ""
+"[UI][API]Able to add multiple tier networks to a deployed VM using “Add "
+"network”..."
+msgstr ""
+
+# f833d338561d4217a15544dc75cc6b02
+#: ../../source/about.rst:811
+msgid ""
+"`CLOUDSTACK-3111 <https://issues.apache.org/jira/browse/CLOUDSTACK-3111>`_"
+msgstr ""
+
+# 7dee5d8b690a4da594074a0b219f0cc0
+#: ../../source/about.rst:811
+msgid ""
+"[UI] Storage tab is not showing the Hypervisor column as 'KVM' if the "
+"(root/data..."
+msgstr ""
+
+# 7e42206866834b8f8e7615d4f1cb75f5
+#: ../../source/about.rst:812
+msgid ""
+"`CLOUDSTACK-3186 <https://issues.apache.org/jira/browse/CLOUDSTACK-3186>`_"
+msgstr ""
+
+# 54509d0dcf424af3b376d59b7b255803
+#: ../../source/about.rst:812
+msgid "Duplicate entries in /etc/hosts file on VR after reboot..."
+msgstr ""
+
+# 3132607cd3184dafa2f1802146401959
+#: ../../source/about.rst:813
+msgid ""
+"`CLOUDSTACK-3195 <https://issues.apache.org/jira/browse/CLOUDSTACK-3195>`_"
+msgstr ""
+
+# 910ba9121d5a4d6185e8e62c3514e80d
+#: ../../source/about.rst:813
+msgid ""
+"cannot view/delete forward rules if underlying/target VM is destroyed "
+"first..."
+msgstr ""
+
+# 18f973b769534e44b4a2c229e624c531
+#: ../../source/about.rst:814
+msgid ""
+"`CLOUDSTACK-3197 <https://issues.apache.org/jira/browse/CLOUDSTACK-3197>`_"
+msgstr ""
+
+# 86d337d71d914114a22e739ee0c1158e
+#: ../../source/about.rst:814
+msgid ""
+"UI: NTier: User is required to scroll down every single time to \"Create "
+"Network\"..."
+msgstr ""
+
+# 4e861db64f9e45f59cabd7fcc9fa0679
+#: ../../source/about.rst:815
+msgid ""
+"`CLOUDSTACK-3212 <https://issues.apache.org/jira/browse/CLOUDSTACK-3212>`_"
+msgstr ""
+
+# 01f3a22662734ac99f60c35f61f812c8
+#: ../../source/about.rst:815
+msgid ""
+"[Advanced_With_SG]View IP Address Range in Default Guest Network page does "
+"not s..."
+msgstr ""
+
+# 8a12acc4d4e74781853e2f2f7e94d136
+#: ../../source/about.rst:816
+msgid ""
+"`CLOUDSTACK-3272 <https://issues.apache.org/jira/browse/CLOUDSTACK-3272>`_"
+msgstr ""
+
+# 9c878c581cba4e42bd48bd458616b333
+#: ../../source/about.rst:816
+msgid ""
+"EventBus: add global config parameters to specify which category of events "
+"are p..."
+msgstr ""
+
+# 72289cd2085e4587bbbc496e737cf9c8
+#: ../../source/about.rst:817
+msgid ""
+"`CLOUDSTACK-3338 <https://issues.apache.org/jira/browse/CLOUDSTACK-3338>`_"
+msgstr ""
+
+# 92f151a159234c019aace4e06369ca4d
+#: ../../source/about.rst:817
+msgid ""
+"Please provide an icon for \"assignVMs\" action in internal LB rule "
+"detailView..."
+msgstr ""
+
+# 403c32dcb0eb46b7af0496a7cd7e21f4
+#: ../../source/about.rst:818
+msgid ""
+"`CLOUDSTACK-3518 <https://issues.apache.org/jira/browse/CLOUDSTACK-3518>`_"
+msgstr ""
+
+# 7196bf7321fd43f8a5b4d39509c4109b
+#: ../../source/about.rst:818
+msgid ""
+"G11n: JA,SC: Un translation issue occurred on the strings of different UI "
+"Specif..."
+msgstr ""
+
+# 8d9ee211b3104f17b274b327ec5dc980
+#: ../../source/about.rst:819
+msgid ""
+"`CLOUDSTACK-3519 <https://issues.apache.org/jira/browse/CLOUDSTACK-3519>`_"
+msgstr ""
+
+# d9cfa91d52844c64904ed2cc4c633721
+#: ../../source/about.rst:819
+msgid ""
+"G11n: JA,SC: Un translation issue occurred on the strings of different "
+"dropdown ..."
+msgstr ""
+
+# df83d462a87d480f8e46736fadda2b18
+#: ../../source/about.rst:820
+msgid ""
+"`CLOUDSTACK-3520 <https://issues.apache.org/jira/browse/CLOUDSTACK-3520>`_"
+msgstr ""
+
+# 035600ab16804b1e9b933b1f2d7ad00f
+#: ../../source/about.rst:820
+msgid ""
+"G11n: JA,SC: Un translation issue occurred on the strings of different "
+"error/war..."
+msgstr ""
+
+# 21bb0266af484d74acf892a71d15fa86
+#: ../../source/about.rst:821
+msgid ""
+"`CLOUDSTACK-3521 <https://issues.apache.org/jira/browse/CLOUDSTACK-3521>`_"
+msgstr ""
+
+# 941512cad6df40518857e8fa2290a2bc
+#: ../../source/about.rst:821
+msgid ""
+"G11n: JA,SC: Un translation issue occurred on the strings of different "
+"tooltips...."
+msgstr ""
+
+# 82333b9ab8e64c56ae2d5d0bc794ee7c
+#: ../../source/about.rst:822
+msgid ""
+"`CLOUDSTACK-3522 <https://issues.apache.org/jira/browse/CLOUDSTACK-3522>`_"
+msgstr ""
+
+# a079a80c68f1484fb8207064327734fa
+#: ../../source/about.rst:822
+msgid ""
+"G11n: JA,SC: Un translation issue occurred on the strings of different "
+"buttons. ..."
+msgstr ""
+
+# 6e1237e4228b47d98248ea0e2f5511d8
+#: ../../source/about.rst:823
+msgid ""
+"`CLOUDSTACK-3523 <https://issues.apache.org/jira/browse/CLOUDSTACK-3523>`_"
+msgstr ""
+
+# 19e2371eee164cbd88a8d983ae0d4001
+#: ../../source/about.rst:823
+msgid ""
+"G11n: JA,SC: Un translation issue occurred on the strings of different popup"
+" mes..."
+msgstr ""
+
+# 723e9a7dbd3646bca15415a0ea508339
+#: ../../source/about.rst:824
+msgid ""
+"`CLOUDSTACK-3528 <https://issues.apache.org/jira/browse/CLOUDSTACK-3528>`_"
+msgstr ""
+
+# 0f57c235ba8244f48d3feb9aa69a525d
+#: ../../source/about.rst:824
+msgid ""
+"[UI]list calls are in the processing state forever with invalid name "
+"provided wi..."
+msgstr ""
+
+# 9e6a31684c0946c6819d1ac93c7dc867
+#: ../../source/about.rst:825
+msgid ""
+"`CLOUDSTACK-3579 <https://issues.apache.org/jira/browse/CLOUDSTACK-3579>`_"
+msgstr ""
+
+# 957e7bbdd41f4c078a53c649480bdd59
+#: ../../source/about.rst:825
+msgid ""
+"[DOC]CLONE - Physical Netwok traffic label update requires Management Server"
+" res..."
+msgstr ""
+
+# 7beeaf7483a14fcbb7969f9656e29b87
+#: ../../source/about.rst:826
+msgid ""
+"`CLOUDSTACK-3607 <https://issues.apache.org/jira/browse/CLOUDSTACK-3607>`_"
+msgstr ""
+
+# 66e98209f17d4a7d99f8002440b48b7e
+#: ../../source/about.rst:826
+msgid ""
+"\"guest_os_hypervisor\" table has values that are not registered in "
+"\"guest_os\" tab..."
+msgstr ""
+
+# 40656611fac94cfd82af00b0b0ea88ba
+#: ../../source/about.rst:827
+msgid ""
+"`CLOUDSTACK-3608 <https://issues.apache.org/jira/browse/CLOUDSTACK-3608>`_"
+msgstr ""
+
+# edf5f359c7a7442b9f291ad17799e056
+#: ../../source/about.rst:827
+msgid ""
+"\"guest_os_hypervisor\" table has repeated mappings of hypervisor and guest "
+"OS..."
+msgstr ""
+
+# 823d2fdb78514741a54d1f6a306aff86
+#: ../../source/about.rst:828
+msgid ""
+"`CLOUDSTACK-3656 <https://issues.apache.org/jira/browse/CLOUDSTACK-3656>`_"
+msgstr ""
+
+# d6105677e00a496d90c6dbc60a033134
+#: ../../source/about.rst:828
+msgid "lots of cloud-management should be changed to cloudstack-management..."
+msgstr ""
+
+# 4fb3155e8cbb4039915ed049a588de0f
+#: ../../source/about.rst:829
+msgid ""
+"`CLOUDSTACK-3788 <https://issues.apache.org/jira/browse/CLOUDSTACK-3788>`_"
+msgstr ""
+
+# 9174fad66e2942f19a41bd96ec2d5735
+#: ../../source/about.rst:829
+msgid "[KVM] Weekly Snapshot got stuck in \"Allocated State\"..."
+msgstr ""
+
+# f64b400ca17e4ffcb981e28b2d16c401
+#: ../../source/about.rst:830
+msgid ""
+"`CLOUDSTACK-3813 <https://issues.apache.org/jira/browse/CLOUDSTACK-3813>`_"
+msgstr ""
+
+# 4b1a6edaa6e94ec2bf5dab3e40938dd3
+#: ../../source/about.rst:830
+msgid ""
+"\"Service.provider.create\" event doesnt mention about the Service Provider "
+"in the..."
+msgstr ""
+
+# 70306e8bf5d949419e3f741d054cc8b8
+#: ../../source/about.rst:831
+msgid ""
+"`CLOUDSTACK-3880 <https://issues.apache.org/jira/browse/CLOUDSTACK-3880>`_"
+msgstr ""
+
+# d61367a71c5943549a60e9d4118fe201
+#: ../../source/about.rst:831
+msgid ""
+"/sbin/poweroff et al or ACPID initiated shutdown does not stop "
+"cloudstack-[usage..."
+msgstr ""
+
+# 11ac67a35df9435981b41ab866d4b9a1
+#: ../../source/about.rst:832
+msgid ""
+"`CLOUDSTACK-3952 <https://issues.apache.org/jira/browse/CLOUDSTACK-3952>`_"
+msgstr ""
+
+# 1181e2c183fe41d49e7b39f6e8e39167
+#: ../../source/about.rst:832
+msgid "Persist VR nic details in DB for additional public ranges..."
+msgstr ""
+
+# 28323cb78e7043bb910e56ae18986eda
+#: ../../source/about.rst:833
+msgid ""
+"`CLOUDSTACK-3973 <https://issues.apache.org/jira/browse/CLOUDSTACK-3973>`_"
+msgstr ""
+
+# a361a2dfcaf34fc19278258986905ecb
+#: ../../source/about.rst:833
+msgid ""
+"[GSLB] [LOGS Message] Improving logs messages for GSLB rule configuration..."
+msgstr ""
+
+# 25a2fe3aa3c44e88889d7ad5e3a15d09
+#: ../../source/about.rst:834
+msgid ""
+"`CLOUDSTACK-4016 <https://issues.apache.org/jira/browse/CLOUDSTACK-4016>`_"
+msgstr ""
+
+# 2624bd1fa06149e1ab3ebee7cce9e5be
+#: ../../source/about.rst:834
+msgid ""
+"[PortableIP] [VPC] listPublicIpAddresses lists the portable IP that was "
+"already ..."
+msgstr ""
+
+# d5156db04f4f4323ad6c08d0786fedda
+#: ../../source/about.rst:835
+msgid ""
+"`CLOUDSTACK-4139 <https://issues.apache.org/jira/browse/CLOUDSTACK-4139>`_"
+msgstr ""
+
+# b0326517fda54a2ebbd4a2677d78bac8
+#: ../../source/about.rst:835
+msgid ""
+"[VMWARE]Failed to resize the volumes which are created from snapshot of root"
+" vol..."
+msgstr ""
+
+# cf818b4df01842b3bd34c10ba0e3b6ae
+#: ../../source/about.rst:836
+msgid ""
+"`CLOUDSTACK-4475 <https://issues.apache.org/jira/browse/CLOUDSTACK-4475>`_"
+msgstr ""
+
+# 3624388961d54af49e2f6e55983d9f1f
+#: ../../source/about.rst:836
+msgid ""
+"[ZWPS] attaching an uploaded volume to a VM is always going to first primary"
+" sto..."
+msgstr ""
+
+# eed17a595cd84ec7a2a2b789a453e165
+#: ../../source/about.rst:837
+msgid ""
+"`CLOUDSTACK-4517 <https://issues.apache.org/jira/browse/CLOUDSTACK-4517>`_"
+msgstr ""
+
+# 5ddc4269a1674a9892ec7351ea9c189e
+#: ../../source/about.rst:837
+msgid ""
+"[upgrade][Vmware]Deployment of VM using centos 6.2 template registered "
+"before up..."
+msgstr ""
+
+# a65b69bed9874f82a5a5af9cc50a7cf8
+#: ../../source/about.rst:838
+msgid ""
+"`CLOUDSTACK-4536 <https://issues.apache.org/jira/browse/CLOUDSTACK-4536>`_"
+msgstr ""
+
+# 9e11de582e1b42b484d1855773bf716c
+#: ../../source/about.rst:838
+msgid ""
+"[object_store_refactor] Inconsistency in volume store location on secondary "
+"stor..."
+msgstr ""
+
+# 42a358f00373446b89e38ed05ae69cfc
+#: ../../source/about.rst:839
+msgid ""
+"`CLOUDSTACK-4568 <https://issues.apache.org/jira/browse/CLOUDSTACK-4568>`_"
+msgstr ""
+
+# e3ee2e1894e242e7a343552132de43d1
+#: ../../source/about.rst:839
+msgid "Need to add this to the release note of 4.2..."
+msgstr ""
+
+# bac89d2d04174dd191a8314b3b880cd5
+#: ../../source/about.rst:840
+msgid ""
+"`CLOUDSTACK-4587 <https://issues.apache.org/jira/browse/CLOUDSTACK-4587>`_"
+msgstr ""
+
+# 7fe14f2df06142d482e795802b1324f3
+#: ../../source/about.rst:840
+msgid ""
+"VM is failing to deploy on a Legacy zone after adding zone wide primary "
+"storage ..."
+msgstr ""
+
+# 627c74c2b2654daebee6dd087aa79133
+#: ../../source/about.rst:841
+msgid ""
+"`CLOUDSTACK-4644 <https://issues.apache.org/jira/browse/CLOUDSTACK-4644>`_"
+msgstr ""
+
+# d83e6413ba8447b8b1f1c35f16bcfcf3
+#: ../../source/about.rst:841
+msgid ""
+"Tool Tip information is not provided for the new fields which are added in "
+"4.2 (..."
+msgstr ""
+
+# 10f0c2c75a7e4724b423a9d6a740d9c3
+#: ../../source/about.rst:842
+msgid ""
+"`CLOUDSTACK-4789 <https://issues.apache.org/jira/browse/CLOUDSTACK-4789>`_"
+msgstr ""
+
+# bd54ce87a1e04392b95f08d939398f1a
+#: ../../source/about.rst:842
+msgid "Fix ResourceMetaDataManagerTest..."
+msgstr ""
+
+# 3716b08f45af446b9ee8056501301496
+#: ../../source/about.rst:843
+msgid ""
+"`CLOUDSTACK-4906 <https://issues.apache.org/jira/browse/CLOUDSTACK-4906>`_"
+msgstr ""
+
+# ded1612281a146918eea296e62e64d63
+#: ../../source/about.rst:843
+msgid "add netaddr to marvin dependency list..."
+msgstr ""
+
+# 5c7270e40c244205ac9302ace72f3a8d
+#: ../../source/about.rst:844
+msgid ""
+"`CLOUDSTACK-4918 <https://issues.apache.org/jira/browse/CLOUDSTACK-4918>`_"
+msgstr ""
+
+# d609afa506d64a69bfc12fba1d3b0e5d
+#: ../../source/about.rst:844
+msgid ""
+"VR can not be LB service provider without requiring to be source nat service"
+" pro..."
+msgstr ""
+
+# 0435d07d6cf4481882befe3bebbd0f05
+#: ../../source/about.rst:845
+msgid ""
+"`CLOUDSTACK-4951 <https://issues.apache.org/jira/browse/CLOUDSTACK-4951>`_"
+msgstr ""
+
+# cf340658226f4dd59d6dd35853d8665f
+#: ../../source/about.rst:845
+msgid "[event framework] Action events do not have UUID ..."
+msgstr ""
+
+# 82523dbe7b4a4575b37dc9aab88703ea
+#: ../../source/about.rst:846
+msgid ""
+"`CLOUDSTACK-4987 <https://issues.apache.org/jira/browse/CLOUDSTACK-4987>`_"
+msgstr ""
+
+# 13590e87501042c183865087ef0537eb
+#: ../../source/about.rst:846
+msgid ""
+"Able to add isolated network belonging to an account to a virtual machine "
+"belong..."
+msgstr ""
+
+# 91d8657d742b4323a260612029a6e357
+#: ../../source/about.rst:847
+msgid ""
+"`CLOUDSTACK-5043 <https://issues.apache.org/jira/browse/CLOUDSTACK-5043>`_"
+msgstr ""
+
+# 83a54dc712f442b49d1536331971227a
+#: ../../source/about.rst:847
+msgid "[DOC] Page number missing and words truncated in PDFs since 4.1.1..."
+msgstr ""
+
+# e91f93f9cfd34e818634c2138626d0f7
+#: ../../source/about.rst:848
+msgid ""
+"`CLOUDSTACK-5044 <https://issues.apache.org/jira/browse/CLOUDSTACK-5044>`_"
+msgstr ""
+
+# a7f4247852384d7ead204cf3b9c5da65
+#: ../../source/about.rst:848
+msgid "Configuration Framework Issue..."
+msgstr ""
+
+# dc1b03fb9b8d4e8a8f2ea2264045d16d
+#: ../../source/about.rst:849
+msgid ""
+"`CLOUDSTACK-5090 <https://issues.apache.org/jira/browse/CLOUDSTACK-5090>`_"
+msgstr ""
+
+# cc31e740ab6b4277be3264b277dedabf
+#: ../../source/about.rst:849
+msgid ""
+"Anti-Affinity: VM fails to start on a cluster belonging to a different "
+"pod...."
+msgstr ""
+
+# 7fb4c69a7f014fbe82e1afab257c866a
+#: ../../source/about.rst:850
+msgid ""
+"`CLOUDSTACK-5157 <https://issues.apache.org/jira/browse/CLOUDSTACK-5157>`_"
+msgstr ""
+
+# 0e9fad22147c4d188fd0fd859bf644bc
+#: ../../source/about.rst:850
+msgid ""
+"Loadbalancer Response should include stickiness, health check and ssl certs "
+"info..."
+msgstr ""
+
+# 81c348ffbbc94b00982f2aa7cd60890d
+#: ../../source/about.rst:851
+msgid ""
+"`CLOUDSTACK-5243 <https://issues.apache.org/jira/browse/CLOUDSTACK-5243>`_"
+msgstr ""
+
+# b369951a791b468488d788750a4e8aa8
+#: ../../source/about.rst:851
+msgid "SSVM responds with timestamp..."
+msgstr ""
+
+# 3a3909f9b93846e583178e77eeb60846
+#: ../../source/about.rst:852
+msgid ""
+"`CLOUDSTACK-5251 <https://issues.apache.org/jira/browse/CLOUDSTACK-5251>`_"
+msgstr ""
+
+# f08d19d6dda84a0d87706ddefb5b5e13
+#: ../../source/about.rst:852
+msgid ""
+"No Error message is displayed when nonexistent NFS secondary storage is "
+"added t..."
+msgstr ""
+
+# f6a5cd73f61f4e51ad5a0c9e5584dbc6
+#: ../../source/about.rst:853
+msgid ""
+"`CLOUDSTACK-5296 <https://issues.apache.org/jira/browse/CLOUDSTACK-5296>`_"
+msgstr ""
+
+# c4d451b646714ed7ae70539f56ca1a78
+#: ../../source/about.rst:853
+msgid "Add certificate chain support for NS..."
+msgstr ""
+
+# 17f24203bf114fab81b7fc9d31296637
+#: ../../source/about.rst:854
+msgid ""
+"`CLOUDSTACK-5307 <https://issues.apache.org/jira/browse/CLOUDSTACK-5307>`_"
+msgstr ""
+
+# 7d65dfb82afb4488b4b7bc47bed733fb
+#: ../../source/about.rst:854
+msgid "Same router is listed twice in router view of project..."
+msgstr ""
+
+# 193439c0e2e84fe8a4365388555d6258
+#: ../../source/about.rst:855
+msgid ""
+"`CLOUDSTACK-5324 <https://issues.apache.org/jira/browse/CLOUDSTACK-5324>`_"
+msgstr ""
+
+# 68936b04d2a6471ca555c69ab20f2af0
+#: ../../source/about.rst:855
+msgid ""
+"error message not proper when start VM fails because router reuires "
+"upgrade..."
+msgstr ""
+
+# 1f9b3473dfd8462e9b8fd44cc7c34487
+#: ../../source/about.rst:856
+msgid ""
+"`CLOUDSTACK-5342 <https://issues.apache.org/jira/browse/CLOUDSTACK-5342>`_"
+msgstr ""
+
+# ba178fa888b4488f8400ae6ff189959e
+#: ../../source/about.rst:856
+msgid "[Automation] Add NIC to virtual machine fails in KVM..."
+msgstr ""
+
+# 728d0536749a47dd9d8b6ff0c0ca1faf
+#: ../../source/about.rst:857
+msgid ""
+"`CLOUDSTACK-5359 <https://issues.apache.org/jira/browse/CLOUDSTACK-5359>`_"
+msgstr ""
+
+# 95c9a5d03b79423583edb6f57a96054a
+#: ../../source/about.rst:857
+msgid ""
+"Failed to add second VMWARE cluster on a standard vSwitch enabled zone when "
+"vCen..."
+msgstr ""
+
+# a566c5a89be64fbe85b51d43a2b4675c
+#: ../../source/about.rst:858
+msgid ""
+"`CLOUDSTACK-5373 <https://issues.apache.org/jira/browse/CLOUDSTACK-5373>`_"
+msgstr ""
+
+# a60c27d282604c91b078217b4fa11ab8
+#: ../../source/about.rst:858
+msgid "Web UI (non-English) is corrupted by text expansion..."
+msgstr ""
+
+# 39e8b0911c204eaf9b81d81ef87fcdfc
+#: ../../source/about.rst:859
+msgid ""
+"`CLOUDSTACK-5395 <https://issues.apache.org/jira/browse/CLOUDSTACK-5395>`_"
+msgstr ""
+
+# 5871613463894a71b654a8b495ec19dc
+#: ../../source/about.rst:859
+msgid ""
+"When backup snapshot fails becasue of backup.snapshot.wait time exceeding , "
+"the ..."
+msgstr ""
+
+# e5e3d2540a88469497dd4aea4fa1b13b
+#: ../../source/about.rst:860
+msgid ""
+"`CLOUDSTACK-5410 <https://issues.apache.org/jira/browse/CLOUDSTACK-5410>`_"
+msgstr ""
+
+# bb57393dec544993bdcfc2e142a4546a
+#: ../../source/about.rst:860
+msgid "Changes for tracking logs using jobid is missing in 4.3..."
+msgstr ""
+
+# f856f42384944b1a8811d1c728d13062
+#: ../../source/about.rst:861
+msgid ""
+"`CLOUDSTACK-5445 <https://issues.apache.org/jira/browse/CLOUDSTACK-5445>`_"
+msgstr ""
+
+# 88435730129a4c4baad8f056f840a058
+#: ../../source/about.rst:861
+msgid "DeleteImageStoreCmd does not use storage plugins to delete storage..."
+msgstr ""
+
+# 5613fc02af644d8b92ed4590ed26f0ea
+#: ../../source/about.rst:862
+msgid ""
+"`CLOUDSTACK-5446 <https://issues.apache.org/jira/browse/CLOUDSTACK-5446>`_"
+msgstr ""
+
+# 96a91d3d3e8d40f9a399b6903884b104
+#: ../../source/about.rst:862
+msgid ""
+"KVM-Secondary Store down-Even after secondary store is brought back up after"
+" bei..."
+msgstr ""
+
+# 4e16958e96fd4b938bfe66c84cf22a8b
+#: ../../source/about.rst:863
+msgid ""
+"`CLOUDSTACK-5463 <https://issues.apache.org/jira/browse/CLOUDSTACK-5463>`_"
+msgstr ""
+
+# 624d8a235086448688b864236accf06e
+#: ../../source/about.rst:863
+msgid "Hyper-V does not report stopped VMs..."
+msgstr ""
+
+# 416fe11a99c645bc8264cdd691d79b53
+#: ../../source/about.rst:864
+msgid ""
+"`CLOUDSTACK-5474 <https://issues.apache.org/jira/browse/CLOUDSTACK-5474>`_"
+msgstr ""
+
+# 6625af56068442ab8097eb138aac18eb
+#: ../../source/about.rst:864
+msgid ""
+"EventBus: RabbitMQ provider expects password to be stored in plain text...."
+msgstr ""
+
+# 64b73b515923418596a64ac98e0e7a0a
+#: ../../source/about.rst:865
+msgid ""
+"`CLOUDSTACK-5475 <https://issues.apache.org/jira/browse/CLOUDSTACK-5475>`_"
+msgstr ""
+
+# 21783847544046bd9ea9c93f04d4f61a
+#: ../../source/about.rst:865
+msgid ""
+"cluster.cpu/(memory).allocated.capacity.disablethreshold is getting "
+"displayed mu..."
+msgstr ""
+
+# 54c52ae2b93f4ef893401ca37514447c
+#: ../../source/about.rst:866
+msgid ""
+"`CLOUDSTACK-5479 <https://issues.apache.org/jira/browse/CLOUDSTACK-5479>`_"
+msgstr ""
+
+# bb342afe327640d2b237bdd0289f94db
+#: ../../source/about.rst:866
+msgid ""
+"Upgrading service offering of stopped vm should release the reserved "
+"capacity of..."
+msgstr ""
+
+# d046e0f9eec9447b819802a246626b24
+#: ../../source/about.rst:867
+msgid ""
+"`CLOUDSTACK-5482 <https://issues.apache.org/jira/browse/CLOUDSTACK-5482>`_"
+msgstr ""
+
+# 9a00471a35354d9fa26f18d260deafa4
+#: ../../source/about.rst:867
+msgid ""
+"Vmware - When nfs was down for about 1 hour , when snapshots were in "
+"progress , ..."
+msgstr ""
+
+# 3b8323aba4a74e2eac2ea540ff313102
+#: ../../source/about.rst:868
+msgid ""
+"`CLOUDSTACK-5488 <https://issues.apache.org/jira/browse/CLOUDSTACK-5488>`_"
+msgstr ""
+
+# bd0384b318af4d34bafa6b7819777dc3
+#: ../../source/about.rst:868
+msgid ""
+"KVM:agent is still in stopped state even after host recovered from sudddent "
+"powe..."
+msgstr ""
+
+# bd5fc0c9c94b415183ca576d0c7a925e
+#: ../../source/about.rst:869
+msgid ""
+"`CLOUDSTACK-5504 <https://issues.apache.org/jira/browse/CLOUDSTACK-5504>`_"
+msgstr ""
+
+# 5dc82178373345ecaa20a4ee2c0e0396
+#: ../../source/about.rst:869
+msgid ""
+"Vmware-Primary store unavailable for 10 mts - All snapshot tasks reported "
+"failur..."
+msgstr ""
+
+# 7297df0aba5f4338bdf8b43c1201789b
+#: ../../source/about.rst:870
+msgid ""
+"`CLOUDSTACK-5512 <https://issues.apache.org/jira/browse/CLOUDSTACK-5512>`_"
+msgstr ""
+
+# 24ed8f480cd0491aaa65fd0db5523a6c
+#: ../../source/about.rst:870
+msgid ""
+"template format name checking is crude and doesn't work with advanced "
+"URLs..."
+msgstr ""
+
+# e1c75c252cc0409fa2e4e3651b18faad
+#: ../../source/about.rst:871
+msgid ""
+"`CLOUDSTACK-5536 <https://issues.apache.org/jira/browse/CLOUDSTACK-5536>`_"
+msgstr ""
+
+# 59560ce9ab304397ac8289ab38b1ff15
+#: ../../source/about.rst:871
+msgid ""
+"Restarting cloudstack service with template download in progress creates "
+"redunda..."
+msgstr ""
+
+# 30a0c7b88bf24f809b1dbd0820bc92a0
+#: ../../source/about.rst:872
+msgid ""
+"`CLOUDSTACK-5546 <https://issues.apache.org/jira/browse/CLOUDSTACK-5546>`_"
+msgstr ""
+
+# 749e0a2d95424c2f8d4c635b21bbaf27
+#: ../../source/about.rst:872
+msgid "Extra tab for adding rules displayed for non-elb networks..."
+msgstr ""
+
+# f40bf3e0be3a4ee1b73252a0aa103027
+#: ../../source/about.rst:873
+msgid ""
+"`CLOUDSTACK-5550 <https://issues.apache.org/jira/browse/CLOUDSTACK-5550>`_"
+msgstr ""
+
+# 72c05501758c4320bda5ab7e102c6942
+#: ../../source/about.rst:873
+msgid "UI - Api key and secret key not fully visible in user detail view...."
+msgstr ""
+
+# 52e58fd9dee44fe8959ffd9ac2f63893
+#: ../../source/about.rst:874
+msgid ""
+"`CLOUDSTACK-5561 <https://issues.apache.org/jira/browse/CLOUDSTACK-5561>`_"
+msgstr ""
+
+# a93eb88abebc4a32b9593305d9138a2a
+#: ../../source/about.rst:874
+msgid "support of multiple nics for VR running in HyperV..."
+msgstr ""
+
+# b237a2ea48dc475facdfffa7f1ef5a8b
+#: ../../source/about.rst:875
+msgid ""
+"`CLOUDSTACK-5563 <https://issues.apache.org/jira/browse/CLOUDSTACK-5563>`_"
+msgstr ""
+
+# 3fdfd4e6cbb04986aea0792d77775482
+#: ../../source/about.rst:875
+msgid "path field is set to null in volumes table ..."
+msgstr ""
+
+# 4f67d4f6c79d4400b14c5a23475bf6e8
+#: ../../source/about.rst:876
+msgid ""
+"`CLOUDSTACK-5576 <https://issues.apache.org/jira/browse/CLOUDSTACK-5576>`_"
+msgstr ""
+
+# b2597bb2adc64d02a7d154873d9fe394
+#: ../../source/about.rst:876
+msgid ""
+"RemoteVPNonVPC : Label needs to be changed to \"Enable Remote Access "
+"VPN\"..."
+msgstr ""
+
+# aa8b32e0b03e4932b2b9b5408fd7e34b
+#: ../../source/about.rst:877
+msgid ""
+"`CLOUDSTACK-5583 <https://issues.apache.org/jira/browse/CLOUDSTACK-5583>`_"
+msgstr ""
+
+# 95f46eaf28c44d6eb55b48db40175cab
+#: ../../source/about.rst:877
+msgid ""
+"vmopsSnapshot plug-in (XenServer) does not return an error when it should..."
+msgstr ""
+
+# 4096cb6d70a446d5a75364034b35cbae
+#: ../../source/about.rst:878
+msgid ""
+"`CLOUDSTACK-5600 <https://issues.apache.org/jira/browse/CLOUDSTACK-5600>`_"
+msgstr ""
+
+# 56a25ad0e47b487595223949df219d77
+#: ../../source/about.rst:878
+msgid ""
+"Xenserver - After HA , CPVM's disk is corrupted resulting in CPVM being "
+"stuck in..."
+msgstr ""
+
+# 4422a2550393446aadcf3566bfeb529b
+#: ../../source/about.rst:879
+msgid ""
+"`CLOUDSTACK-5616 <https://issues.apache.org/jira/browse/CLOUDSTACK-5616>`_"
+msgstr ""
+
+# 503356c6579848508844126696d8f8f7
+#: ../../source/about.rst:879
+msgid ""
+"[DBHA]:There is no way to know to which DB is the CS writing in the case of "
+"DBHA..."
+msgstr ""
+
+# 9e90b6202eea4acd89fe42fe9c4cb645
+#: ../../source/about.rst:880
+msgid ""
+"`CLOUDSTACK-5632 <https://issues.apache.org/jira/browse/CLOUDSTACK-5632>`_"
+msgstr ""
+
+# e3237f8e610b4a0eae7c54f0b726c91f
+#: ../../source/about.rst:880
+msgid ""
+"[Automation] XenServer - Template deletion fails with error \"Please specify"
+" a te..."
+msgstr ""
+
+# 6cf6d3fa8bba4e92bc9e92457b2255a5
+#: ../../source/about.rst:881
+msgid ""
+"`CLOUDSTACK-5645 <https://issues.apache.org/jira/browse/CLOUDSTACK-5645>`_"
+msgstr ""
+
+# b6270bd700634ffa8cc763edcfe41978
+#: ../../source/about.rst:881
+msgid ""
+"Agent manager doesn't need to be aware of vms and their relationship to "
+"resource..."
+msgstr ""
+
+# 3c3ad906781d4d7eb90e7a0ac4bfe78b
+#: ../../source/about.rst:882
+msgid ""
+"`CLOUDSTACK-5673 <https://issues.apache.org/jira/browse/CLOUDSTACK-5673>`_"
+msgstr ""
+
+# f49c861d702b4d0bbd22b30026798d12
+#: ../../source/about.rst:882
+msgid ""
+"[Hyper-V] Default IP address never configured on eth0 with default CentOS "
+"templa..."
+msgstr ""
+
+# a77ccae93fb240e4a299a9d5fb73cac1
+#: ../../source/about.rst:883
+msgid ""
+"`CLOUDSTACK-5685 <https://issues.apache.org/jira/browse/CLOUDSTACK-5685>`_"
+msgstr ""
+
+# e366f576f3d84e0a8ac9911d821cd60f
+#: ../../source/about.rst:883
+msgid ""
+"[Vmsync] - When VR is rebooted outside of cloudstack , there is no change in"
+" sta..."
+msgstr ""
+
+# 06998b79062b4c16bb1586460fa7cd0c
+#: ../../source/about.rst:884
+msgid ""
+"`CLOUDSTACK-5700 <https://issues.apache.org/jira/browse/CLOUDSTACK-5700>`_"
+msgstr ""
+
+# 1df0f7424f63415b882665736fedf388
+#: ../../source/about.rst:884
+msgid "[Vmsync] - kvm- \"paused\" state of Vm is not synced to CS...."
+msgstr ""
+
+# 0b5b01b4a3594d7f99e0e18fc151886e
+#: ../../source/about.rst:885
+msgid ""
+"`CLOUDSTACK-5719 <https://issues.apache.org/jira/browse/CLOUDSTACK-5719>`_"
+msgstr ""
+
+# db94d6fce45942f98f2bd5650af19912
+#: ../../source/about.rst:885
+msgid ""
+"[UI] Not listing shared network offerings tagged on second physical "
+"network..."
+msgstr ""
+
+# db3c140e162944b9b925691a5f5f165c
+#: ../../source/about.rst:886
+msgid ""
+"`CLOUDSTACK-5724 <https://issues.apache.org/jira/browse/CLOUDSTACK-5724>`_"
+msgstr ""
+
+# ba56251e49954f0eb4c7092a2c1441c5
+#: ../../source/about.rst:886
+msgid ""
+"Console Proxy View - when using ctl c , errors seen on the console proxy "
+"view...."
+msgstr ""
+
+# 82e782ed6c7747728ecf0dcbe9151870
+#: ../../source/about.rst:887
+msgid ""
+"`CLOUDSTACK-5743 <https://issues.apache.org/jira/browse/CLOUDSTACK-5743>`_"
+msgstr ""
+
+# 8f3791cf1de843338d1843291860a9d9
+#: ../../source/about.rst:887
+msgid ""
+"Download ROOT Volume when the VM is in stopped state is failing with "
+"\"Forbidden..."
+msgstr ""
+
+# aea2f8353f8e4488af01cfc49ddb48e4
+#: ../../source/about.rst:888
+msgid ""
+"`CLOUDSTACK-5744 <https://issues.apache.org/jira/browse/CLOUDSTACK-5744>`_"
+msgstr ""
+
+# 36cce736e0ce4968b53c8de3e67807d8
+#: ../../source/about.rst:888
+msgid ""
+"[Hyper-v] White screen on console window when more than two console sessions"
+" are..."
+msgstr ""
+
+# 94c9d86e67544498b08cdd8416046442
+#: ../../source/about.rst:889
+msgid ""
+"`CLOUDSTACK-5753 <https://issues.apache.org/jira/browse/CLOUDSTACK-5753>`_"
+msgstr ""
+
+# 02a9ed3fef294e9db4fd6900485b1961
+#: ../../source/about.rst:889
+msgid ""
+"[Hyper-v] ConsoleProxyLoadReportCommand does not honor the default value of "
+"cons..."
+msgstr ""
+
+# 88a6ed8122da496b8a15ece9b1498aaf
+#: ../../source/about.rst:890
+msgid ""
+"`CLOUDSTACK-5762 <https://issues.apache.org/jira/browse/CLOUDSTACK-5762>`_"
+msgstr ""
+
+# 1bb3479127b947a89f8c923a0c6e1bcb
+#: ../../source/about.rst:890
+msgid ""
+"[dynamic compute offerings]UI change required for select compute offerinngs"
+" in ..."
+msgstr ""
+
+# 4462bf458b894524833e0d8bcba45a17
+#: ../../source/about.rst:891
+msgid ""
+"`CLOUDSTACK-5785 <https://issues.apache.org/jira/browse/CLOUDSTACK-5785>`_"
+msgstr ""
+
+# 5069ef72c09e46ad8084b82c03fc8c56
+#: ../../source/about.rst:891
+msgid "VM display name cell not updated upon detaching volume from VM..."
+msgstr ""
+
+# db8ae3f440cf4455b2f02327015d1c4a
+#: ../../source/about.rst:892
+msgid ""
+"`CLOUDSTACK-5794 <https://issues.apache.org/jira/browse/CLOUDSTACK-5794>`_"
+msgstr ""
+
+# c232b4e8b81346c1a93cf0012934f468
+#: ../../source/about.rst:892
+msgid ""
+"[Hyper-v] Specify username and domain name together in the username field "
+"while ..."
+msgstr ""
+
+# 8ae3c469336b4ec6965d854eff822684
+#: ../../source/about.rst:893
+msgid ""
+"`CLOUDSTACK-5798 <https://issues.apache.org/jira/browse/CLOUDSTACK-5798>`_"
+msgstr ""
+
+# 22a0516940a644939b1737f0cd8dcd35
+#: ../../source/about.rst:893
+msgid ""
+"While attaching a disk to WIN2012 VM with xencenter tools installed got "
+"error as..."
+msgstr ""
+
+# 43dd1a41dd4e44239b2e478ffded4694
+#: ../../source/about.rst:894
+msgid ""
+"`CLOUDSTACK-5800 <https://issues.apache.org/jira/browse/CLOUDSTACK-5800>`_"
+msgstr ""
+
+# a2f85d50eee44372bc2bcf806cca17e9
+#: ../../source/about.rst:894
+msgid ""
+"While creating a VM from template (which is created based on existing newly "
+"crea..."
+msgstr ""
+
+# 915cf844a6854358bf6e861350b1479c
+#: ../../source/about.rst:895
+msgid ""
+"`CLOUDSTACK-5807 <https://issues.apache.org/jira/browse/CLOUDSTACK-5807>`_"
+msgstr ""
+
+# 0897ce4abcbb4033859f0449e928125c
+#: ../../source/about.rst:895
+msgid "Problem with shared datastore in VMware cluster with only one host..."
+msgstr ""
+
+# 6765a9fd4b0c4db79eb10d7a4dc133b5
+#: ../../source/about.rst:896
+msgid ""
+"`CLOUDSTACK-5809 <https://issues.apache.org/jira/browse/CLOUDSTACK-5809>`_"
+msgstr ""
+
+# 464ec622e70243ffbc5db1f14e156619
+#: ../../source/about.rst:896
+msgid ""
+"Not able to deploy Vm becasue of crossing pool.storage.allocate "
+"d.capacity.disab..."
+msgstr ""
+
+# 4bccd233b1d849ceba642ed120606dec
+#: ../../source/about.rst:897
+msgid ""
+"`CLOUDSTACK-5822 <https://issues.apache.org/jira/browse/CLOUDSTACK-5822>`_"
+msgstr ""
+
+# c54904d46b724fd091d64354e6dafccd
+#: ../../source/about.rst:897
+msgid "ssh keypairs are removed after rebooting vm..."
+msgstr ""
+
+# 08557c1b20a94ee18bde7c1f7a406b42
+#: ../../source/about.rst:898
+msgid ""
+"`CLOUDSTACK-5834 <https://issues.apache.org/jira/browse/CLOUDSTACK-5834>`_"
+msgstr ""
+
+# 01af65e60d524900bf08a1d70ea42909
+#: ../../source/about.rst:898
+msgid ""
+"[upgrade]Error while collecting disk stats from : You gave an invalid object"
+" ref..."
+msgstr ""
+
+# b5574ef4bb82434786636036da92a5f8
+#: ../../source/about.rst:899
+msgid ""
+"`CLOUDSTACK-5836 <https://issues.apache.org/jira/browse/CLOUDSTACK-5836>`_"
+msgstr ""
+
+# 99faa2cf0c4942818e491b207c78e448
+#: ../../source/about.rst:899
+msgid ""
+"When tried to reverting back to (disk attached)quiesced vm snapshot, got "
+"error a..."
+msgstr ""
+
+# 42dd7cded1c846f397c9bc3f0985396d
+#: ../../source/about.rst:900
+msgid ""
+"`CLOUDSTACK-5843 <https://issues.apache.org/jira/browse/CLOUDSTACK-5843>`_"
+msgstr ""
+
+# 9c70b4b9b84442258aca13062148eebf
+#: ../../source/about.rst:900
+msgid ""
+"registering templates/isos should be either async or changed to non-"
+"blocking..."
+msgstr ""
+
+# 557610d31c2648778eb586d3c355c51c
+#: ../../source/about.rst:901
+msgid ""
+"`CLOUDSTACK-5845 <https://issues.apache.org/jira/browse/CLOUDSTACK-5845>`_"
+msgstr ""
+
+# f76b8a93412140778a09313a2e392d85
+#: ../../source/about.rst:901
+msgid ""
+"[doc] Document Heterogeneous Secondary Storage Not Supported in Region..."
+msgstr ""
+
+# 11001f7cefc544abac72c8bcf221d2d1
+#: ../../source/about.rst:902
+msgid ""
+"`CLOUDSTACK-5847 <https://issues.apache.org/jira/browse/CLOUDSTACK-5847>`_"
+msgstr ""
+
+# aa11b3c98b494677ad279807b1fc16dd
+#: ../../source/about.rst:902
+msgid ""
+"[Hyper-V] [doc] Document creation of external vswitch for Hyper-V 2012 R2 "
+"(unlik..."
+msgstr ""
+
+# 49f6b506e48043d9bf28b1dcccf52cdb
+#: ../../source/about.rst:903
+msgid ""
+"`CLOUDSTACK-5855 <https://issues.apache.org/jira/browse/CLOUDSTACK-5855>`_"
+msgstr ""
+
+# 676f457929c74bcc83ebb6f37c4a72c9
+#: ../../source/about.rst:903
+msgid ""
+"Contrail: Slave compute host restarts when the master compute host is "
+"changed to..."
+msgstr ""
+
+# d71c8b73113d48659a5e52ebc701bfda
+#: ../../source/about.rst:904
+msgid ""
+"`CLOUDSTACK-5862 <https://issues.apache.org/jira/browse/CLOUDSTACK-5862>`_"
+msgstr ""
+
+# ec0d4184509843598a6b566774cf1bb1
+#: ../../source/about.rst:904
+msgid ""
+"Template life cycle needs to be changed based on references of existing VMs "
+"to t..."
+msgstr ""
+
+# 7069f2c006ad4dd7b8ddd65885f32eb6
+#: ../../source/about.rst:905
+msgid ""
+"`CLOUDSTACK-5866 <https://issues.apache.org/jira/browse/CLOUDSTACK-5866>`_"
+msgstr ""
+
+# 332622ca747448a9b638712083439222
+#: ../../source/about.rst:905
+msgid "Remove maven profile used to configure zone..."
+msgstr ""
+
+# e51f3dcbc6ad473ab41bf22cf33e9af6
+#: ../../source/about.rst:906
+msgid ""
+"`CLOUDSTACK-5876 <https://issues.apache.org/jira/browse/CLOUDSTACK-5876>`_"
+msgstr ""
+
+# 073abbbb04284c9f942e87a688fc2086
+#: ../../source/about.rst:906
+msgid ""
+"Contrail: After vrouter restart agent doesnt have info about the Network..."
+msgstr ""
+
+# af92fe91418d4306988f665712ee4fa8
+#: ../../source/about.rst:907
+msgid ""
+"`CLOUDSTACK-5879 <https://issues.apache.org/jira/browse/CLOUDSTACK-5879>`_"
+msgstr ""
+
+# 12bc62b3dffb44f79ad5d84740d311f0
+#: ../../source/about.rst:907
+msgid ""
+"Document on how to use RabbitMq event bus with spring modularisation done in"
+" 4.3..."
+msgstr ""
+
+# 86d3efe5f7fd4d30889a92587432df20
+#: ../../source/about.rst:908
+msgid ""
+"`CLOUDSTACK-5897 <https://issues.apache.org/jira/browse/CLOUDSTACK-5897>`_"
+msgstr ""
+
+# 6b138f81eac4489183c7080180eb46b9
+#: ../../source/about.rst:908
+msgid "Remove OVM in add cluster drop down list..."
+msgstr ""
+
+# 83d9adac0ad34fad8b8a2d44642f2ef6
+#: ../../source/about.rst:909
+msgid ""
+"`CLOUDSTACK-5907 <https://issues.apache.org/jira/browse/CLOUDSTACK-5907>`_"
+msgstr ""
+
+# 673551c263a64a458cc645ced6619bbf
+#: ../../source/about.rst:909
+msgid "KVM/CLVM volumes are shown as Ovm hypervisor..."
+msgstr ""
+
+# f0935a17a83b44e8a14d5b629230c171
+#: ../../source/about.rst:910
+msgid ""
+"`CLOUDSTACK-5908 <https://issues.apache.org/jira/browse/CLOUDSTACK-5908>`_"
+msgstr ""
+
+# cf6c3725ca244469ba5b19dc5577c630
+#: ../../source/about.rst:910
+msgid "Fail to add VXLAN network to instance..."
+msgstr ""
+
+# b0b635e252684125a14d7e15dcd59902
+#: ../../source/about.rst:911
+msgid ""
+"`CLOUDSTACK-5910 <https://issues.apache.org/jira/browse/CLOUDSTACK-5910>`_"
+msgstr ""
+
+# 58450a277eeb406fa6c30acabe92d166
+#: ../../source/about.rst:911
+msgid "mark the LDAP user as imported from LDAP..."
+msgstr ""
+
+# af6ef2f4abdd4741909ee24de85933f8
+#: ../../source/about.rst:912
+msgid ""
+"`CLOUDSTACK-5920 <https://issues.apache.org/jira/browse/CLOUDSTACK-5920>`_"
+msgstr ""
+
+# ce45e6f1e80b4cc3b61fd9b686297610
+#: ../../source/about.rst:912
+msgid "CloudStack IAM Plugin feature..."
+msgstr ""
+
+# e8ffcbe7cdf84907b6185e6ffca4ba01
+#: ../../source/about.rst:913
+msgid ""
+"`CLOUDSTACK-5926 <https://issues.apache.org/jira/browse/CLOUDSTACK-5926>`_"
+msgstr ""
+
+# d48cd789b41c4728a9dcc41f475f286e
+#: ../../source/about.rst:913
+msgid "[Doc] Create 4.3 Release Notes..."
+msgstr ""
+
+# e0d5e76950f34c538fe229e39417360f
+#: ../../source/about.rst:914
+msgid ""
+"`CLOUDSTACK-5931 <https://issues.apache.org/jira/browse/CLOUDSTACK-5931>`_"
+msgstr ""
+
+# 90cc9eb2416f4026b198f7ebc9796f49
+#: ../../source/about.rst:914
+msgid "Hyper-V agent does not release logon handle..."
+msgstr ""
+
+# e5507b4683aa4807b841e8e1546de3c6
+#: ../../source/about.rst:915
+msgid ""
+"`CLOUDSTACK-5932 <https://issues.apache.org/jira/browse/CLOUDSTACK-5932>`_"
+msgstr ""
+
+# 6569531c2301433db4def28a6271e669
+#: ../../source/about.rst:915
+msgid ""
+"SystemVM scripts: the iso download urls need updating as current ones are "
+"obsole..."
+msgstr ""
+
+# e8814954b4ee4b6db3d8be53977b4aca
+#: ../../source/about.rst:916
+msgid ""
+"`CLOUDSTACK-5933 <https://issues.apache.org/jira/browse/CLOUDSTACK-5933>`_"
+msgstr ""
+
+# 5ce5bc961b344c7da43172ffac8a2253
+# 8ab076108bf845b8b8d4da4a4c85aee9
+# d9c1f79d30b04159a65aa5d42e1ecba3
+#: ../../source/about.rst:916 ../../source/about.rst:917
+#: ../../source/about.rst:918
+msgid "Problem with VMware snapshot when datastore has a space in its name..."
+msgstr ""
+
+# bb833b720da84718b19e2af7067edfd0
+#: ../../source/about.rst:917
+msgid ""
+"`CLOUDSTACK-5934 <https://issues.apache.org/jira/browse/CLOUDSTACK-5934>`_"
+msgstr ""
+
+# 85739de24903447faf3b0030fb46b943
+#: ../../source/about.rst:918
+msgid ""
+"`CLOUDSTACK-5935 <https://issues.apache.org/jira/browse/CLOUDSTACK-5935>`_"
+msgstr ""
+
+# e0bc47e0f8694fdc85fa6dc8ee1bbe3c
+#: ../../source/about.rst:919
+msgid ""
+"`CLOUDSTACK-5947 <https://issues.apache.org/jira/browse/CLOUDSTACK-5947>`_"
+msgstr ""
+
+# f2281071edbc412c82d3970f6253ba60
+#: ../../source/about.rst:919
+msgid "Exception for getRootDir.. NFSStorage when running with Simulator..."
+msgstr ""
+
+# 3abd5466824844ff86a35499da50b2fd
+#: ../../source/about.rst:920
+msgid ""
+"`CLOUDSTACK-5951 <https://issues.apache.org/jira/browse/CLOUDSTACK-5951>`_"
+msgstr ""
+
+# 3c41283de3eb4514b7d09dfda960030d
+#: ../../source/about.rst:920
+msgid "Fix base.py for Dynamic compute offerings..."
+msgstr ""
+
+# 44ccddcb447c4ddbb3e68119bf807c3a
+#: ../../source/about.rst:921
+msgid ""
+"`CLOUDSTACK-5954 <https://issues.apache.org/jira/browse/CLOUDSTACK-5954>`_"
+msgstr ""
+
+# edf36e9ef5494869a23f559b1e9de0c1
+#: ../../source/about.rst:921
+msgid "update-ssl.png missing from docs..."
+msgstr ""
+
+# 810e7eb9bd154b61acd8aeef915cf762
+#: ../../source/about.rst:922
+msgid ""
+"`CLOUDSTACK-5955 <https://issues.apache.org/jira/browse/CLOUDSTACK-5955>`_"
+msgstr ""
+
+# 8c00a4c01ed64a1e8d8433e03912a88c
+#: ../../source/about.rst:922
+msgid "vm stuck in migrating if mgmt server is restarted..."
+msgstr ""
+
+# fc4396ab18374d5592ce88fcf816c49a
+#: ../../source/about.rst:923
+msgid ""
+"`CLOUDSTACK-5962 <https://issues.apache.org/jira/browse/CLOUDSTACK-5962>`_"
+msgstr ""
+
+# 6f0989d4b6ac44078841675417a8bb84
+#: ../../source/about.rst:923
+msgid ""
+"Value of Global parameter \"custom.diskoffering.size.min\" is not reflected "
+"in UI ..."
+msgstr ""
+
+# 81aa4406e0f5476d84e4322a63a0a99e
+#: ../../source/about.rst:924
+msgid ""
+"`CLOUDSTACK-5972 <https://issues.apache.org/jira/browse/CLOUDSTACK-5972>`_"
+msgstr ""
+
+# d04402ca216d4b11859b53357ed8c6b1
+#: ../../source/about.rst:924
+msgid "[DOC] Service monitoring enable/disable from global setting..."
+msgstr ""
+
+# cbeeb934235046539974f28b2881a7fa
+#: ../../source/about.rst:925
+msgid ""
+"`CLOUDSTACK-5976 <https://issues.apache.org/jira/browse/CLOUDSTACK-5976>`_"
+msgstr ""
+
+# f93bd455107d4154afa2fefa764f37f1
+#: ../../source/about.rst:925
+msgid ""
+"[upgrade]Typo in \"ssh_keypairs\" table's foreign key constraints on the "
+"Upgraded ..."
+msgstr ""
+
+# db65963bc9b84ceea6627adb7d3cd8d0
+#: ../../source/about.rst:926
+msgid ""
+"`CLOUDSTACK-5982 <https://issues.apache.org/jira/browse/CLOUDSTACK-5982>`_"
+msgstr ""
+
+# 64662e57b5ff48f4bc2fbfd59b59f192
+#: ../../source/about.rst:926
+msgid "Fix response name for assign and unassign cert from lb..."
+msgstr ""
+
+# 6ae5d3809aa0448badc6e227607e10c3
+#: ../../source/about.rst:927
+msgid ""
+"`CLOUDSTACK-5984 <https://issues.apache.org/jira/browse/CLOUDSTACK-5984>`_"
+msgstr ""
+
+# 28c77a358f7b4e47af7d139884cf09d3
+#: ../../source/about.rst:927
+msgid "addvmwaredc API call is not documented ..."
+msgstr ""
+
+# fe5633aa4b02454d83cd7cfcc2654bd1
+#: ../../source/about.rst:928
+msgid ""
+"`CLOUDSTACK-5990 <https://issues.apache.org/jira/browse/CLOUDSTACK-5990>`_"
+msgstr ""
+
+# e5fd89285b494c0db3e14c75c4b16565
+#: ../../source/about.rst:928
+msgid "[UI]: search by username while importing ldap users..."
+msgstr ""
+
+# 35842deb54f9451e8056a1d3261fb279
+#: ../../source/about.rst:929
+msgid ""
+"`CLOUDSTACK-5991 <https://issues.apache.org/jira/browse/CLOUDSTACK-5991>`_"
+msgstr ""
+
+# 194b2ee3ce804e3db87132f3f72efe93
+#: ../../source/about.rst:929
+msgid "[UI]Infinite scrolling should be enabled to the Ldap user add page..."
+msgstr ""
+
+# e7e0289989fc4f838a776baab7d6dfcf
+#: ../../source/about.rst:930
+msgid ""
+"`CLOUDSTACK-5992 <https://issues.apache.org/jira/browse/CLOUDSTACK-5992>`_"
+msgstr ""
+
+# 1289a464c7ef4a4f9213bb57498c2f63
+#: ../../source/about.rst:930
+msgid ""
+"[Upgrade] default values of configuraiton parameters in configuration table "
+"are ..."
+msgstr ""
+
+# af62f0ef9596472c8f7f6b5c72205d1d
+#: ../../source/about.rst:931
+msgid ""
+"`CLOUDSTACK-6032 <https://issues.apache.org/jira/browse/CLOUDSTACK-6032>`_"
+msgstr ""
+
+# 461160a486b844b4861d12b3b539d16a
+#: ../../source/about.rst:931
+msgid ""
+"[VmScaleup]service offering id is not getting changed in usage_vm_instance "
+"table..."
+msgstr ""
+
+# dea36e7d08aa4791b6418f852095c302
+#: ../../source/about.rst:932
+msgid ""
+"`CLOUDSTACK-6043 <https://issues.apache.org/jira/browse/CLOUDSTACK-6043>`_"
+msgstr ""
+
+# c098010713234572aaa92f97fb50df6a
+#: ../../source/about.rst:932
+msgid "VMware detaching volume fails if volume has snapshots..."
+msgstr ""
+
+# b43004dda81e4014a5f0763b3ee3ccd5
+#: ../../source/about.rst:933
+msgid ""
+"`CLOUDSTACK-6053 <https://issues.apache.org/jira/browse/CLOUDSTACK-6053>`_"
+msgstr ""
+
+# 462dde74d1a9466db759fb7520cc6794
+#: ../../source/about.rst:933
+msgid ""
+"While adding smb as primary or secondary the password should be uri "
+"encoded..."
+msgstr ""
+
+# 130598f509cb4eee834a16fe019e32ce
+#: ../../source/about.rst:934
+msgid ""
+"`CLOUDSTACK-6069 <https://issues.apache.org/jira/browse/CLOUDSTACK-6069>`_"
+msgstr ""
+
+# e90b4abd6a3043ed92c18f1bcccaf187
+#: ../../source/about.rst:934
+msgid "can't create privatgateway with vlan in a mixed network env..."
+msgstr ""
+
+# c4a32d58a29d4fc7969d992d4eb62fc9
+#: ../../source/about.rst:935
+msgid ""
+"`CLOUDSTACK-6072 <https://issues.apache.org/jira/browse/CLOUDSTACK-6072>`_"
+msgstr ""
+
+# e0e697959a864d77b79d5d86d1055894
+#: ../../source/about.rst:935
+msgid "vxlan networks not deallocating vnet ids..."
+msgstr ""
+
+# 2d01c25ad91a45cfbc6ad94aeba751de
+#: ../../source/about.rst:936
+msgid ""
+"`CLOUDSTACK-6075 <https://issues.apache.org/jira/browse/CLOUDSTACK-6075>`_"
+msgstr ""
+
+# 077f40b21a1d451da0b6551b396c2510
+#: ../../source/about.rst:936
+msgid "Increase the ram size for router service offering ..."
+msgstr ""
+
+# f71815f13a6f45048b3d93d7464ecc56
+#: ../../source/about.rst:937
+msgid ""
+"`CLOUDSTACK-124 <https://issues.apache.org/jira/browse/CLOUDSTACK-124>`_"
+msgstr ""
+
+# c403f649f6e94e6aa9fee5cb3ba8b1f9
+#: ../../source/about.rst:937
+msgid "NetworkGarbageCollector not cleaning up networks..."
+msgstr ""
+
+# bd976b9749144511a462c66dad141024
+#: ../../source/about.rst:938
+msgid ""
+"`CLOUDSTACK-231 <https://issues.apache.org/jira/browse/CLOUDSTACK-231>`_"
+msgstr ""
+
+# 7bcf2f588f364099b9aff15a97023e5b
+#: ../../source/about.rst:938
+msgid "Tag creation using special charecters ..."
+msgstr ""
+
+# deeef16b849e4d88a9ef7604e90787d4
+#: ../../source/about.rst:939
+msgid ""
+"`CLOUDSTACK-245 <https://issues.apache.org/jira/browse/CLOUDSTACK-245>`_"
+msgstr ""
+
+# 309c606e25524114b7b6800f14cf3c62
+#: ../../source/about.rst:939
+msgid "VPC ACLs are not stored and programmed consistently..."
+msgstr ""
+
+# 3ade068351834e9daea921cc0d5b1900
+#: ../../source/about.rst:940
+msgid ""
+"`CLOUDSTACK-270 <https://issues.apache.org/jira/browse/CLOUDSTACK-270>`_"
+msgstr ""
+
+# aa86fba63b3e4abda4df67eb7f18479b
+#: ../../source/about.rst:940
+msgid ""
+"Ui should not ask for a vlan range if the physical network isolation type is"
+" not..."
+msgstr ""
+
+# 6cdf64027f814affbfff2e16fff1497c
+#: ../../source/about.rst:941
+msgid ""
+"`CLOUDSTACK-300 <https://issues.apache.org/jira/browse/CLOUDSTACK-300>`_"
+msgstr ""
+
+# aa45f6e4f69c458481b07efd241e4f4e
+#: ../../source/about.rst:941
+msgid ""
+"Creation of compute offering allow combination of local storage + HA..."
+msgstr ""
+
+# 3535aeb0b68d4e8093e3ca9fa8545c8b
+#: ../../source/about.rst:942
+msgid ""
+"`CLOUDSTACK-310 <https://issues.apache.org/jira/browse/CLOUDSTACK-310>`_"
+msgstr ""
+
+# 20e7178656a3404e99304ca26d79de54
+#: ../../source/about.rst:942
+msgid "Failed to add host - Plugin error..."
+msgstr ""
+
+# adc4e3f488d449d0bb08a00d806c92ad
+#: ../../source/about.rst:943
+msgid ""
+"`CLOUDSTACK-315 <https://issues.apache.org/jira/browse/CLOUDSTACK-315>`_"
+msgstr ""
+
+# fe201a77da2d42bb8b290befa6cd7c61
+#: ../../source/about.rst:943
+msgid "Infrastructure view does not show capacity values..."
+msgstr ""
+
+# 3b73db7445e84726a621e55792a78640
+#: ../../source/about.rst:944
+msgid ""
+"`CLOUDSTACK-338 <https://issues.apache.org/jira/browse/CLOUDSTACK-338>`_"
+msgstr ""
+
+# d6cdf18645f241dc8d65a825419ce13f
+#: ../../source/about.rst:944
+msgid ""
+"Unique Names of Disk and Service Offerings in the database are prefixed with"
+" \"Cl..."
+msgstr ""
+
+# cc5ad682b94943928cb11127c683165d
+#: ../../source/about.rst:945
+msgid ""
+"`CLOUDSTACK-458 <https://issues.apache.org/jira/browse/CLOUDSTACK-458>`_"
+msgstr ""
+
+# 2c496074b8014416a60d15b6524a3c7d
+#: ../../source/about.rst:945
+msgid ""
+"xen:snapshots:Storage gc fail to clean the failed snapshot images from "
+"secondary..."
+msgstr ""
+
+# 470819855835494bb3e4b42a63762a75
+#: ../../source/about.rst:946
+msgid ""
+"`CLOUDSTACK-469 <https://issues.apache.org/jira/browse/CLOUDSTACK-469>`_"
+msgstr ""
+
+# e483a4ddc85e48b5b874ce49a0d4348a
+#: ../../source/about.rst:946
+msgid "CloudStack Documentation Landing Page has Alignment Issues..."
+msgstr ""
+
+# 8701a51097fb42cc81f778db547df9a5
+#: ../../source/about.rst:947
+msgid ""
+"`CLOUDSTACK-963 <https://issues.apache.org/jira/browse/CLOUDSTACK-963>`_"
+msgstr ""
+
+# 557c83dc7d364bc380050720275c491e
+#: ../../source/about.rst:947
+msgid ""
+"[cloud.utils.AnnotationHelper] class java.lang.Stringdoes not have a Table "
+"anno..."
+msgstr ""
+
+# 3de2d5b341cd4beeafa8ded446f144a1
+#: ../../source/about.rst:948
+msgid ""
+"`CLOUDSTACK-969 <https://issues.apache.org/jira/browse/CLOUDSTACK-969>`_"
+msgstr ""
+
+# 87b4adb2c73f4094a8b1e269a812c256
+#: ../../source/about.rst:948
+msgid ""
+"api: zone response lists vlan in it as \"vlan range of zone\" but the vlan "
+"belongs..."
+msgstr ""
+
+# 9682bf3f823f48808f399d0833c9c972
+#: ../../source/about.rst:949
+msgid ""
+"`CLOUDSTACK-1306 <https://issues.apache.org/jira/browse/CLOUDSTACK-1306>`_"
+msgstr ""
+
+# dcfc2e8792b34560bf771f465e6b5f1e
+#: ../../source/about.rst:949
+msgid ""
+"Better Error message when trying to deploy Vm by passing static Ipv4 "
+"addresses t..."
+msgstr ""
+
+# 292c51d2256f4b3cb4057ca48f853a16
+#: ../../source/about.rst:950
+msgid ""
+"`CLOUDSTACK-1432 <https://issues.apache.org/jira/browse/CLOUDSTACK-1432>`_"
+msgstr ""
+
+# 640c5559b1f848caa902512ff84b49a3
+#: ../../source/about.rst:950
+msgid "[UI] Inconsistent field names in \"Add Cluster\" dialog..."
+msgstr ""
+
+# deff00442eaf41578758a8fc6a91bc1b
+#: ../../source/about.rst:951
+msgid ""
+"`CLOUDSTACK-1471 <https://issues.apache.org/jira/browse/CLOUDSTACK-1471>`_"
+msgstr ""
+
+# e748278ea8b940809ac2c41d84709fad
+#: ../../source/about.rst:951
+msgid ""
+"Pop up window for host details/(host related operation) are not properly "
+"alligne..."
+msgstr ""
+
+# 1e1a52cced9d4fb5ae3ff2cf45118355
+#: ../../source/about.rst:952
+msgid ""
+"`CLOUDSTACK-1524 <https://issues.apache.org/jira/browse/CLOUDSTACK-1524>`_"
+msgstr ""
+
+# e1642948629845c285e6bca3af5389f9
+#: ../../source/about.rst:952
+msgid "\"White-box\" effect changes when changing value in combo box..."
+msgstr ""
+
+# 20421a8e6fb6417aafeec944e379178a
+#: ../../source/about.rst:953
+msgid ""
+"`CLOUDSTACK-1725 <https://issues.apache.org/jira/browse/CLOUDSTACK-1725>`_"
+msgstr ""
+
+# e99f7cdb2e00432385ba84a45882f52c
+#: ../../source/about.rst:953
+msgid "publican update_pot might overwrite license headers ..."
+msgstr ""
+
+# 57290580090b4de896d2ae244646b4b9
+#: ../../source/about.rst:954
+msgid ""
+"`CLOUDSTACK-1932 <https://issues.apache.org/jira/browse/CLOUDSTACK-1932>`_"
+msgstr ""
+
+# 948fa91e719a4fe29cbfa654eb39e96a
+#: ../../source/about.rst:954
+msgid ""
+"AutoScale UI documentation doesn't mention the option appears only for "
+"NetScaler..."
+msgstr ""
+
+# 99aaec54cc06481c9695a66e3c1f294b
+#: ../../source/about.rst:955
+msgid ""
+"`CLOUDSTACK-2000 <https://issues.apache.org/jira/browse/CLOUDSTACK-2000>`_"
+msgstr ""
+
+# 3d09b02f8e3f48f3b8fb0c0f54410139
+#: ../../source/about.rst:955
+msgid ""
+"CS4.1 Installation document - cloud-install-sys-tmplt command documented in "
+"wron..."
+msgstr ""
+
+# c1575fc372284702b88bec3821c72aa4
+#: ../../source/about.rst:956
+msgid ""
+"`CLOUDSTACK-2213 <https://issues.apache.org/jira/browse/CLOUDSTACK-2213>`_"
+msgstr ""
+
+# 16faf7c244484832911649754c6837a5
+#: ../../source/about.rst:956
+msgid "russian language select failure..."
+msgstr ""
+
+# 2cbc226b25a94c9685846bb61135b12a
+#: ../../source/about.rst:957
+msgid ""
+"`CLOUDSTACK-2345 <https://issues.apache.org/jira/browse/CLOUDSTACK-2345>`_"
+msgstr ""
+
+# 2833085d6922422986409770a070a809
+#: ../../source/about.rst:957
+msgid ""
+"[GSLB] deleting GSLB rules is not cleaning server info from GSLB device..."
+msgstr ""
+
+# 2614a9255d324ea4a6c8521e2da7c308
+#: ../../source/about.rst:958
+msgid ""
+"`CLOUDSTACK-2436 <https://issues.apache.org/jira/browse/CLOUDSTACK-2436>`_"
+msgstr ""
+
+# 735e7ca609f841db97fd9f95b1fa1594
+#: ../../source/about.rst:958
+msgid ""
+"Message \"You do not have any affinity groups. Please continue to the next "
+"step.\"..."
+msgstr ""
+
+# ae80ec401946455f87aaccb915d341dc
+#: ../../source/about.rst:959
+msgid ""
+"`CLOUDSTACK-2439 <https://issues.apache.org/jira/browse/CLOUDSTACK-2439>`_"
+msgstr ""
+
+# 1dd9ac498c52472a9168dcfc733dd3ca
+#: ../../source/about.rst:959
+msgid ""
+"\"Domain\" field under login page should be mandatory for the non root "
+"accounts...."
+msgstr ""
+
+# 32895ca41f6e4343a317aadd68190b71
+#: ../../source/about.rst:960
+msgid ""
+"`CLOUDSTACK-2449 <https://issues.apache.org/jira/browse/CLOUDSTACK-2449>`_"
+msgstr ""
+
+# f0595b5791524cc5ac68ceb9312451eb
+#: ../../source/about.rst:960
+msgid ""
+"Dropdown menu for action button scaleup System VM shows all service offering"
+" inc..."
+msgstr ""
+
+# 98fa68df36d64851b63eb662e8db7502
+#: ../../source/about.rst:961
+msgid ""
+"`CLOUDSTACK-2453 <https://issues.apache.org/jira/browse/CLOUDSTACK-2453>`_"
+msgstr ""
+
+# c03e069aadcf4337a206b0bfbf2ea65e
+#: ../../source/about.rst:961
+msgid ""
+"Select view dropdown under \"Network\" is listing the options in the absence"
+" of ad..."
+msgstr ""
+
+# 006f2919c94944668a59100431fd6d2f
+#: ../../source/about.rst:962
+msgid ""
+"`CLOUDSTACK-2464 <https://issues.apache.org/jira/browse/CLOUDSTACK-2464>`_"
+msgstr ""
+
+# fc200e7396e2473c8b3b16936cc3ca2e
+#: ../../source/about.rst:962
+msgid "[GSLB][UI] \"Add GSLB\" wizard doesn't prompt for \"PersistenceType\"..."
+msgstr ""
+
+# 07042e6c5b1347bca94f1246aa648969
+#: ../../source/about.rst:963
+msgid ""
+"`CLOUDSTACK-2533 <https://issues.apache.org/jira/browse/CLOUDSTACK-2533>`_"
+msgstr ""
+
+# ed2e9e8e46524fe59dcb5711469a8b10
+#: ../../source/about.rst:963
+msgid ""
+"Add Network to VM dialog should only show those network in the dropdown "
+"which ar..."
+msgstr ""
+
+# 18e1dc3644244d13a77cf9bc1db5af7d
+#: ../../source/about.rst:964
+msgid ""
+"`CLOUDSTACK-2535 <https://issues.apache.org/jira/browse/CLOUDSTACK-2535>`_"
+msgstr ""
+
+# 5750f72b3c094f7fb43f4f160b4bed53
+#: ../../source/about.rst:964
+msgid ""
+"Cleanup port-profiles that gets created on Nexus switch as part of network "
+"clean..."
+msgstr ""
+
+# 7c534d9056ee424b95d5c6f17b7b4506
+#: ../../source/about.rst:965
+msgid ""
+"`CLOUDSTACK-2559 <https://issues.apache.org/jira/browse/CLOUDSTACK-2559>`_"
+msgstr ""
+
+# 091a5c75671d4441b91c623b05129f14
+#: ../../source/about.rst:965
+msgid ""
+"[UI]Resource Name should not be present in UI as it is not available in "
+"listASA1..."
+msgstr ""
+
+# 1e567fca109b4b349a7c2c6c8284ba11
+#: ../../source/about.rst:966
+msgid ""
+"`CLOUDSTACK-2605 <https://issues.apache.org/jira/browse/CLOUDSTACK-2605>`_"
+msgstr ""
+
+# f4334ef1f3f44acc87bf1003f0d6567a
+#: ../../source/about.rst:966
+msgid ""
+"Add Network to VM Command button should not be displayed for VMs belonging "
+"to B..."
+msgstr ""
+
+# 08bd353b6429441f9b90c69b1251d4da
+#: ../../source/about.rst:967
+msgid ""
+"`CLOUDSTACK-2697 <https://issues.apache.org/jira/browse/CLOUDSTACK-2697>`_"
+msgstr ""
+
+# 2bc76e4035cb441abfd5d6d1b1f608b6
+#: ../../source/about.rst:967
+msgid ""
+"cluster id in alert message is null {alertType:: 1 // dataCenterId:: 1 // "
+"podId:..."
+msgstr ""
+
+# 04ef32f9ef79467e8f69750fd720ffb1
+#: ../../source/about.rst:968
+msgid ""
+"`CLOUDSTACK-2714 <https://issues.apache.org/jira/browse/CLOUDSTACK-2714>`_"
+msgstr ""
+
+# d7f48ef417104458a850899d7081dac2
+#: ../../source/about.rst:968
+msgid "Setting tab should not be visible for user accounts ..."
+msgstr ""
+
+# 67847a92b9bf4060bdb04270e6739a1f
+#: ../../source/about.rst:969
+msgid ""
+"`CLOUDSTACK-2951 <https://issues.apache.org/jira/browse/CLOUDSTACK-2951>`_"
+msgstr ""
+
+# bd9915a7a5064c1cbbedff49c46a74b1
+#: ../../source/about.rst:969
+msgid ""
+"[UI][Mixed-Zone-Management] during \"add Instance\" wizard, listTemplates "
+"API is n..."
+msgstr ""
+
+# 39d2c4a20daf4f468c049514cee70006
+#: ../../source/about.rst:970
+msgid ""
+"`CLOUDSTACK-2993 <https://issues.apache.org/jira/browse/CLOUDSTACK-2993>`_"
+msgstr ""
+
+# 0e21629701ff4572ab3334c0d8992d31
+#: ../../source/about.rst:970
+msgid ""
+"[PortableIPRange] remove some of the unused columns if they are not required"
+" fro..."
+msgstr ""
+
+# 79fd650e0ffc4ec38fe40b80e402d26f
+#: ../../source/about.rst:971
+msgid ""
+"`CLOUDSTACK-3025 <https://issues.apache.org/jira/browse/CLOUDSTACK-3025>`_"
+msgstr ""
+
+# 4cbd966303574dc48701d6228f09fcf6
+#: ../../source/about.rst:971
+msgid ""
+"The page and pagesize parameters are not working in ListCfgsByCmds with "
+"zoneid s..."
+msgstr ""
+
+# df05b3b006284f0a998517594080bc76
+#: ../../source/about.rst:972
+msgid ""
+"`CLOUDSTACK-3063 <https://issues.apache.org/jira/browse/CLOUDSTACK-3063>`_"
+msgstr ""
+
+# 32f5d4b07a0b4656a1d273225600663e
+#: ../../source/about.rst:972
+msgid ""
+"[UI]Dedicating a host to non-root domain which has instances of other "
+"domain(ro..."
+msgstr ""
+
+# 7d1845ed384b44c18be7d08556c94053
+#: ../../source/about.rst:973
+msgid ""
+"`CLOUDSTACK-3101 <https://issues.apache.org/jira/browse/CLOUDSTACK-3101>`_"
+msgstr ""
+
+# 7c613c75b4b5498bbc3847eba9e9c43f
+#: ../../source/about.rst:973
+msgid "[DR] list* APIs are not working based on the display* flags ..."
+msgstr ""
+
+# 20624242deaa47ff823797c8f8797a63
+#: ../../source/about.rst:974
+msgid ""
+"`CLOUDSTACK-3225 <https://issues.apache.org/jira/browse/CLOUDSTACK-3225>`_"
+msgstr ""
+
+# 4ae5d16975ce4612ae8a2f674247e2f5
+#: ../../source/about.rst:974
+msgid ""
+"Multiple NPEs when cloudstack-management service is restarted with "
+"incomplete ta..."
+msgstr ""
+
+# 44f6905ab2784817840f2f4414ecd19b
+#: ../../source/about.rst:975
+msgid ""
+"`CLOUDSTACK-3265 <https://issues.apache.org/jira/browse/CLOUDSTACK-3265>`_"
+msgstr ""
+
+# f1e4d8bc2b2a46e0bd431e84d51e6e7e
+#: ../../source/about.rst:975
+msgid ""
+"[Health Check for NS LB]Failure to create a lb health check policy returns a"
+" API..."
+msgstr ""
+
+# d3b589ac76f3462e95f825dbb318b709
+#: ../../source/about.rst:976
+msgid ""
+"`CLOUDSTACK-3325 <https://issues.apache.org/jira/browse/CLOUDSTACK-3325>`_"
+msgstr ""
+
+# 2a9d3d66cd434e44a27c322e53ab82d3
+#: ../../source/about.rst:976
+msgid ""
+"[UI] [GSLB]: add text box to specify weight for each load balancer "
+"participating..."
+msgstr ""
+
+# 2dde3723f50f4ce086fec6e9ae7e2087
+#: ../../source/about.rst:977
+msgid ""
+"`CLOUDSTACK-3406 <https://issues.apache.org/jira/browse/CLOUDSTACK-3406>`_"
+msgstr ""
+
+# 8f43f91478884ca78b65a209b950054a
+#: ../../source/about.rst:977
+msgid ""
+"UI: ZWPS: Zone wizard: Primary storage creation failed after \"fix error\" "
+"in \"add..."
+msgstr ""
+
+# 35aaf061f97244a6b8fadc7abddb2b83
+#: ../../source/about.rst:978
+msgid ""
+"`CLOUDSTACK-3477 <https://issues.apache.org/jira/browse/CLOUDSTACK-3477>`_"
+msgstr ""
+
+# 8bb57ac4b9664575823aec6390cda227
+#: ../../source/about.rst:978
+msgid ""
+"resizeDataVolume doesn't return proper error message when trying to shrink "
+"volum..."
+msgstr ""
+
+# 942cd355d2d44b458b643bab82c1677f
+#: ../../source/about.rst:979
+msgid ""
+"`CLOUDSTACK-3553 <https://issues.apache.org/jira/browse/CLOUDSTACK-3553>`_"
+msgstr ""
+
+# a7251e773cda429ea03553182a677ec5
+#: ../../source/about.rst:979
+msgid ""
+"[UI]UI remains in the processing state forever when it failed to delete "
+"primary ..."
+msgstr ""
+
+# d4b126c917364b0d96635b21b4665181
+#: ../../source/about.rst:980
+msgid ""
+"`CLOUDSTACK-3671 <https://issues.apache.org/jira/browse/CLOUDSTACK-3671>`_"
+msgstr ""
+
+# 98869aecb40548f38fd4300bae9b7843
+#: ../../source/about.rst:980
+msgid ""
+"Set Host, Management Network and Storage Network Properly when there are "
+"multipl..."
+msgstr ""
+
+# 01f0168d82aa4ce190ce8dd84044233a
+#: ../../source/about.rst:981
+msgid ""
+"`CLOUDSTACK-3815 <https://issues.apache.org/jira/browse/CLOUDSTACK-3815>`_"
+msgstr ""
+
+# 4d9fd9b9356e4b03a21abb5217544bfc
+#: ../../source/about.rst:981
+msgid ""
+"\"SNAPSHOT.CREATE\" event's states are not registered on the events table "
+"..."
+msgstr ""
+
+# c2b82a82bc0a416295cd4b08283dd316
+#: ../../source/about.rst:982
+msgid ""
+"`CLOUDSTACK-3895 <https://issues.apache.org/jira/browse/CLOUDSTACK-3895>`_"
+msgstr ""
+
+# 489b344704d842a0b930eca4c9e91f1e
+#: ../../source/about.rst:982
+msgid ""
+"VM Migration across VMWARE clusters which are added with different "
+"switches(Stan..."
+msgstr ""
+
+# a1d81d2e8e54459f81fc0d2625d1832c
+#: ../../source/about.rst:983
+msgid ""
+"`CLOUDSTACK-3896 <https://issues.apache.org/jira/browse/CLOUDSTACK-3896>`_"
+msgstr ""
+
+# 3ca6c4fa7a7e4025a32b5020c325a53b
+#: ../../source/about.rst:983
+msgid ""
+"[PrimaryStorage] deleteStoragePool is not kicking GC for the downloaded "
+"system v..."
+msgstr ""
+
+# 43f0b1ea52fe4fe7a4e2484e506825d6
+#: ../../source/about.rst:984
+msgid ""
+"`CLOUDSTACK-3994 <https://issues.apache.org/jira/browse/CLOUDSTACK-3994>`_"
+msgstr ""
+
+# 5a53b655b1cf4cfea3b90038ddd68633
+#: ../../source/about.rst:984
+msgid ""
+"Wrong error notification is generated when Primary storage (Cluster wide) is"
+" add..."
+msgstr ""
+
+# 574bcc875b064c8e8746bd1a7be27501
+#: ../../source/about.rst:985
+msgid ""
+"`CLOUDSTACK-3995 <https://issues.apache.org/jira/browse/CLOUDSTACK-3995>`_"
+msgstr ""
+
+# 1f9fc290435941328c2109f013d7bdff
+#: ../../source/about.rst:985
+msgid ""
+"No error notification is generated when Primary storage (Zonelevel) is added"
+" wit..."
+msgstr ""
+
+# cb0553897b3c465294130e89bdd4ac58
+#: ../../source/about.rst:986
+msgid ""
+"`CLOUDSTACK-4071 <https://issues.apache.org/jira/browse/CLOUDSTACK-4071>`_"
+msgstr ""
+
+# 2862ac7599114679a6f24de95002f064
+#: ../../source/about.rst:986
+msgid ""
+"[UI] - Word 'Default' is misspelled in descripiton of integration.api.port "
+"under..."
+msgstr ""
+
+# 54ccd314834a46cba8eef1688ecd52b7
+#: ../../source/about.rst:987
+msgid ""
+"`CLOUDSTACK-4183 <https://issues.apache.org/jira/browse/CLOUDSTACK-4183>`_"
+msgstr ""
+
+# aa96ab063bb44952a00f0c47f50207d3
+#: ../../source/about.rst:987
+msgid "[Non-Contiguous VLAN] Typos Appear in an Error Message..."
+msgstr ""
+
+# b09e463e41164a34af3f3bfd49d70912
+#: ../../source/about.rst:988
+msgid ""
+"`CLOUDSTACK-5033 <https://issues.apache.org/jira/browse/CLOUDSTACK-5033>`_"
+msgstr ""
+
+# 08432d28368c40d6addee09bbf581362
+#: ../../source/about.rst:988
+msgid ""
+"ipaddress in management-server.log and api.log are wrong if management "
+"servers i..."
+msgstr ""
+
+# bb40967dfec04fd6a29b3d43b737fafb
+#: ../../source/about.rst:989
+msgid ""
+"`CLOUDSTACK-5309 <https://issues.apache.org/jira/browse/CLOUDSTACK-5309>`_"
+msgstr ""
+
+# f31f90451b8647f2a4287ddb1e87119a
+#: ../../source/about.rst:989
+msgid ""
+"version number and requires upgrade fields are not displayed for routers "
+"when na..."
+msgstr ""
+
+# 431ee2aba7624021949605ee211083c1
+#: ../../source/about.rst:990
+msgid ""
+"`CLOUDSTACK-5383 <https://issues.apache.org/jira/browse/CLOUDSTACK-5383>`_"
+msgstr ""
+
+# e5e9449373fe4fd8901fcd3ee8cef900
+#: ../../source/about.rst:990
+msgid ""
+"Multiselect actions are not reset when a multiselect action is performed..."
+msgstr ""
+
+# e6d4b228f9fd4558b9dc9200add0230e
+#: ../../source/about.rst:991
+msgid ""
+"`CLOUDSTACK-5524 <https://issues.apache.org/jira/browse/CLOUDSTACK-5524>`_"
+msgstr ""
+
+# 33c8cf3f1c6f4fe68174c66381159fc4
+#: ../../source/about.rst:991
+msgid ""
+"[UI]\"root disk size\" field should be removed from the add instance wizard "
+"since ..."
+msgstr ""
+
+# 3a22f8b6a45f4d4fb1f6d5b358d86c9e
+#: ../../source/about.rst:992
+msgid ""
+"`CLOUDSTACK-5824 <https://issues.apache.org/jira/browse/CLOUDSTACK-5824>`_"
+msgstr ""
+
+# cbcd7cd35944493eaf6ed41b06a803b3
+#: ../../source/about.rst:992
+msgid "Delete snapshot UI always success..."
+msgstr ""
+
+# 965f0ea7a2a5482792dba13663078468
+#: ../../source/about.rst:993
+msgid ""
+"`CLOUDSTACK-5885 <https://issues.apache.org/jira/browse/CLOUDSTACK-5885>`_"
+msgstr ""
+
+# f2ea70862fde430e84db8e1b15a6e569
+#: ../../source/about.rst:993
+msgid ""
+"When process receives error, loading overlay on listView element does not "
+"disapp..."
+msgstr ""
+
+# 90a3667d15824f4f90d372d017c45a62
+#: ../../source/about.rst:994
+msgid ""
+"`CLOUDSTACK-5912 <https://issues.apache.org/jira/browse/CLOUDSTACK-5912>`_"
+msgstr ""
+
+# 3cd58ef1d295445f85bafb2d0b6bc2ae
+#: ../../source/about.rst:994
+msgid ""
+"WARN [c.c.h.v.m.HttpNfcLeaseMO] (Thread-28:null) Unexpected exception..."
+msgstr ""
+
+# a1d998b4aa3d43d5adc9d7a61c9fc67f
+#: ../../source/about.rst:995
+msgid ""
+"`CLOUDSTACK-5522 <https://issues.apache.org/jira/browse/CLOUDSTACK-5522>`_"
+msgstr ""
+
+# 738108b3afbd4e4faf7952a781b1727e
+#: ../../source/about.rst:995
+msgid "Need of one more column i.e., \"Name\" at Home>Storage - Snapshots..."
+msgstr ""
+
+# b3b8c82a8e9f48a3badc0431e365dbb5
+#: ../../source/about.rst:996
+msgid ""
+"`CLOUDSTACK-5904 <https://issues.apache.org/jira/browse/CLOUDSTACK-5904>`_"
+msgstr ""
+
+# 8af03a70536b413b945116dd54cc0433
+#: ../../source/about.rst:996
+msgid "Small UI bug..."
+msgstr ""
diff --git a/source/releasenotes/locale/ja/LC_MESSAGES/api-changes.mo b/source/releasenotes/locale/ja/LC_MESSAGES/api-changes.mo
new file mode 100644
index 0000000..ad03993
--- /dev/null
+++ b/source/releasenotes/locale/ja/LC_MESSAGES/api-changes.mo
Binary files differ
diff --git a/source/releasenotes/locale/ja/LC_MESSAGES/api-changes.po b/source/releasenotes/locale/ja/LC_MESSAGES/api-changes.po
new file mode 100644
index 0000000..67c63c3
--- /dev/null
+++ b/source/releasenotes/locale/ja/LC_MESSAGES/api-changes.po
@@ -0,0 +1,270 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-05 14:09+0100\n"
+"PO-Revision-Date: 2014-03-31 15:24+0000\n"
+"Last-Translator: sebgoa <runseb@gmail.com>\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/apache-cloudstack-release-notes-rtd/language/ja/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# d9094117b9964d349a7faf2e57c9e3e4
+#: ../../source/api-changes.rst:17
+msgid "API Changes Introduced in 4.3"
+msgstr ""
+
+# b12ab6bdaa534a33917a061983581f3d
+#: ../../source/api-changes.rst:20
+msgid "Hyper-V"
+msgstr ""
+
+# 5aefde4b6f004c51945b0044d3740217
+# 5b056d9023be4a86ab05195dcfdaca95
+# 11210537ee5147e59056c56b59e42f08
+# a810ec26333c4a3f9d700c3b81485296
+# 9d26f67529d64c698626ee8dc9c400d8
+#: ../../source/api-changes.rst:23 ../../source/api-changes.rst:34
+#: ../../source/api-changes.rst:46 ../../source/api-changes.rst:61
+#: ../../source/api-changes.rst:85
+msgid "API"
+msgstr ""
+
+# 99bd0d75ced643cb80cb4ec4299c35b3
+# f8bd81df2af8470b9990f9897b493d71
+# ccf6333be50b4c05bc93bbae46a92439
+# ddbf27df21c648a28eb25e9d7eff816f
+# 5b062ec9909a408891111c5f7bed4cc1
+#: ../../source/api-changes.rst:23 ../../source/api-changes.rst:34
+#: ../../source/api-changes.rst:46 ../../source/api-changes.rst:61
+#: ../../source/api-changes.rst:85
+msgid "Description"
+msgstr "説明"
+
+# 365a2382c8444d81b8f280e3a681dd69
+#: ../../source/api-changes.rst:25
+msgid "addPrimaryStorage"
+msgstr ""
+
+# 6edcdba9172a4af5b7219da22dd43f75
+# 19400171550b4ef0a53f052b64df6877
+#: ../../source/api-changes.rst:25 ../../source/api-changes.rst:27
+msgid "To this existing API, the following field has been added: smb"
+msgstr ""
+
+# 827fbd70c10347729fb8c779b0b47b0a
+#: ../../source/api-changes.rst:27
+msgid "addImageStore"
+msgstr ""
+
+# 43782ead911e421ca6adb962a7c77dfd
+#: ../../source/api-changes.rst:31
+msgid "Reporting CPU Sockets"
+msgstr ""
+
+# e5ab7c9d1f94448eac6d593130aa05b9
+#: ../../source/api-changes.rst:36
+msgid "listhost"
+msgstr ""
+
+# 45ac5fb2b2c24e7b8187531b170e411f
+#: ../../source/api-changes.rst:36
+msgid ""
+"To this existing API, the following request parameter has been added: "
+"hypervisor."
+msgstr ""
+
+# 05c23488f1864eaaa96b7c997ec9f949
+#: ../../source/api-changes.rst:39
+msgid "The new response parameter added is: cpusockets"
+msgstr ""
+
+# 32af8e6f5a6a4ae2a48b4d533da1f219
+#: ../../source/api-changes.rst:43
+msgid "Publishing Alerts Using the Web ROOT Admin API"
+msgstr ""
+
+# 0372a1c85ea74e5d846c667a271c9562
+#: ../../source/api-changes.rst:48
+msgid "generateAlert"
+msgstr ""
+
+# 32f8078ad6cf4ce4b2bc6bd829054359
+#: ../../source/api-changes.rst:48
+msgid ""
+"A new API has been added to generate and publish alerts for usage services. "
+"The usage services can be installed on a different host or the same host "
+"where the Management Server is running. This API is available only to the "
+"Root Admin."
+msgstr ""
+
+# 0598acaf5d4541a48f2abef70d0c2a97
+#: ../../source/api-changes.rst:53
+msgid "listAlerts"
+msgstr ""
+
+# 66573b271ddd4dcebe751b1dd443d7d6
+#: ../../source/api-changes.rst:53
+msgid ""
+"To this existing API, a new response parameter has been added: name. An "
+"alert can be searched on the basis of alert name."
+msgstr ""
+
+# 057d779d43db49b083cebe754abc8653
+#: ../../source/api-changes.rst:58
+msgid "Dynamic Compute Offering"
+msgstr ""
+
+# 23dbcf83d85544d6a77f7cee9d20a495
+#: ../../source/api-changes.rst:63
+msgid "DeployVM"
+msgstr ""
+
+# b3a16a57e3444e9eb9b133e1c7aae502
+# 0c1b450d88ee41a29d3940fb4dbe446e
+# 5af7afdab9124e4ab6ab30535e91cfca
+# 47210117aa364a6fa3f3fe116994fd9d
+# 8ddafba6eab243e3a9f3c40cafc47506
+#: ../../source/api-changes.rst:63 ../../source/api-changes.rst:66
+#: ../../source/api-changes.rst:69 ../../source/api-changes.rst:73
+#: ../../source/api-changes.rst:76
+msgid ""
+"To this existing API, the following request parameter has been added: "
+"details."
+msgstr ""
+
+# 697e61df898e41468a4bb34915c0a2c5
+#: ../../source/api-changes.rst:66
+msgid "ScaleVM"
+msgstr ""
+
+# deb002fc84ca4df181cbcf23666cfeee
+#: ../../source/api-changes.rst:69
+msgid "ScaleSystemVM"
+msgstr ""
+
+# 8eba0c13bb83496cb7f98a4e8d9ab6fc
+#: ../../source/api-changes.rst:73
+msgid "UpgradeVM"
+msgstr ""
+
+# 77f58f648f6b4cc7ba29e1483185c1d8
+#: ../../source/api-changes.rst:76
+msgid "UpgradeSystemVM"
+msgstr ""
+
+# ba68c7e577064f13b98947ef5477eb20
+#: ../../source/api-changes.rst:82
+msgid "Enhanced Upgrade for Virtual Routers"
+msgstr ""
+
+# 84fb8face38d49189fec55cbc8b5dce1
+#: ../../source/api-changes.rst:87
+msgid "upgradeRouterTemplate"
+msgstr ""
+
+# 79fe85f7d8804dccb880a1608b426cdd
+#: ../../source/api-changes.rst:87
+msgid "This is a new API which has been added in this release."
+msgstr ""
+
+# fbbbb874ceab4379a5172a20af2e61fe
+#: ../../source/api-changes.rst:89
+msgid "The following are the request parameters:"
+msgstr ""
+
+# 65599f3691cf4130a9806c3d5ad95120
+#: ../../source/api-changes.rst:91
+msgid "id: Upgrade the specified VR"
+msgstr ""
+
+# fc78e916a3b7421b9c4c97e6684da339
+#: ../../source/api-changes.rst:93
+msgid "zone\\_id : Upgrade the VRs in the specified zone."
+msgstr ""
+
+# 8a8c04a211af421587e828e9922fbfb7
+#: ../../source/api-changes.rst:95
+msgid "pod\\_id : Upgrade the VRs in the specified pod."
+msgstr ""
+
+# 80cbde982e394ef6a0e347e9ab6332e0
+#: ../../source/api-changes.rst:97
+msgid "cluster\\_id : Upgrade the VRs in the specified cluster."
+msgstr ""
+
+# 5a8aa0e5cc3941c894873dc6c6425acd
+#: ../../source/api-changes.rst:99
+msgid "domain\\_id : Upgrade the VRs belonging to the specified domain."
+msgstr ""
+
+# d91d1a80b9d34a70b28fcc1785f7328c
+#: ../../source/api-changes.rst:102
+msgid "account\\_id : Upgrade the VRs belonging to the specified account."
+msgstr ""
+
+# 638ab1630ae8470cb15bbbbb045a6260
+#: ../../source/api-changes.rst:106
+msgid "listRouters"
+msgstr ""
+
+# 4fe7967e4fd445c682ddea876504ca8c
+#: ../../source/api-changes.rst:106
+msgid ""
+"For this existing API, the following request parameters has been added:"
+msgstr ""
+
+# e301f86659fa42e4a51f4a7999592c53
+#: ../../source/api-changes.rst:109
+msgid "version: Lists routers by specified version."
+msgstr ""
+
+# 86f961243ddc49dd88459e0ff937132d
+#: ../../source/api-changes.rst:111
+msgid "zone\\_id : lists routers in specified zone."
+msgstr ""
+
+# 3cf021b43806427992de1d916bb4b3ba
+#: ../../source/api-changes.rst:113
+msgid "pod\\_id : Lists routers in the specified pod."
+msgstr ""
+
+# 285dde45b78a44a682ce3c68f5c74bbc
+#: ../../source/api-changes.rst:115
+msgid "cluster\\_id : Lists routers in the specified cluster."
+msgstr ""
+
+# 063f3aa2737340dba9d8093fdda068d7
+#: ../../source/api-changes.rst:117
+msgid "domain\\_id : Lists routers owned by specified domain."
+msgstr ""
+
+# f08534c64c0e4cf4a756b327179d92ba
+#: ../../source/api-changes.rst:119
+msgid "account: Lists routers owned by specified account."
+msgstr ""
+
+# 28e790d3d2074de488c9a83d654e75be
+#: ../../source/api-changes.rst:121
+msgid "The following response parameters has been added:"
+msgstr ""
+
+# e3472c1cbe7b4ed884ea7122265172bb
+#: ../../source/api-changes.rst:123
+msgid "version : (String) The router version. For example, 4.3.0."
+msgstr ""
+
+# 3609a98e83f947cb983ed97c651cd607
+#: ../../source/api-changes.rst:125
+msgid ""
+"requiresupgrade: (Boolean) The flag to indicate if the router template "
+"requires an upgrade."
+msgstr ""
diff --git a/source/releasenotes/locale/ja/LC_MESSAGES/compat.mo b/source/releasenotes/locale/ja/LC_MESSAGES/compat.mo
new file mode 100644
index 0000000..ad03993
--- /dev/null
+++ b/source/releasenotes/locale/ja/LC_MESSAGES/compat.mo
Binary files differ
diff --git a/source/releasenotes/locale/ja/LC_MESSAGES/compat.po b/source/releasenotes/locale/ja/LC_MESSAGES/compat.po
new file mode 100644
index 0000000..51895b1
--- /dev/null
+++ b/source/releasenotes/locale/ja/LC_MESSAGES/compat.po
@@ -0,0 +1,192 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-05 14:09+0100\n"
+"PO-Revision-Date: 2014-03-31 12:58+0000\n"
+"Last-Translator: sebgoa <runseb@gmail.com>\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/apache-cloudstack-release-notes-rtd/language/ja/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# db2da739b7a34d9bb5a1576dc1042204
+#: ../../source/compat.rst:17
+msgid "Compatibility Matrix"
+msgstr ""
+
+# c7acf31a9adf453fbc640c154ab269ee
+#: ../../source/compat.rst:20
+msgid "Supported OS Versions for Management Server"
+msgstr ""
+
+# e99c2e0451784e1cbff91e3c5c7bd689
+#: ../../source/compat.rst:22
+msgid ""
+"This section lists the operating systems that are supported for running "
+"CloudStack Management Server. Note that specific versions of the operating "
+"systems are tested, so compatibility with CentOS 6.3 may not indicate "
+"compatibility with CentOS 6.2, 6.1 and so on."
+msgstr ""
+
+# cf915523898f4abf983568b8cec84018
+#: ../../source/compat.rst:29
+msgid "RHEL versions 5.5, 6.2, 6.3, and 6.4"
+msgstr ""
+
+# 5683129179f747809a6716b37511fadf
+#: ../../source/compat.rst:33
+msgid "CentOS versions 6.3, and 6.4"
+msgstr ""
+
+# 91f4ff90b38c41d098678a134d694f51
+#: ../../source/compat.rst:37
+msgid "Ubuntu 12.04 LTS"
+msgstr ""
+
+# fb119d6e242e44868a8fa98413ec8d19
+#: ../../source/compat.rst:40
+msgid "Supported Hypervisor Versions"
+msgstr ""
+
+# dba2f41a378848b98ea1f4a9e4172113
+#: ../../source/compat.rst:42
+msgid ""
+"CloudStack supports three hypervisor families, XenServer with XAPI, KVM, and"
+" VMware with vSphere."
+msgstr ""
+
+# 3a0e082d30544c959a9c0b9e00991268
+#: ../../source/compat.rst:47
+msgid "Windows Server 2012 R2 (with Hyper-V Role enabled)"
+msgstr ""
+
+# 7614dfa9d7be4029913713efa375f856
+#: ../../source/compat.rst:51
+msgid "Hyper-V 2012 R2"
+msgstr ""
+
+# c46e689be4d24f9483eac04951615e93
+#: ../../source/compat.rst:55
+msgid "CentOS 6.2 with KVM"
+msgstr ""
+
+# d9bfa6c2911747a3aff66374d976d4e5
+#: ../../source/compat.rst:59
+msgid "Red Hat Enterprise Linux 6.2 with KVM"
+msgstr ""
+
+# a285a4f39e6f4e19aa08a9dd7e42c01a
+#: ../../source/compat.rst:63
+msgid "XenServer 6.0.2 (with Hotfix)"
+msgstr ""
+
+# dbcd5f4102ff4929b9aff04cc5350b41
+#: ../../source/compat.rst:67
+msgid "XenServer versions 6.1 and 6.2 SPI with latest hotfixes"
+msgstr ""
+
+# d6992bb8033e488988bc1f5236e513e1
+#: ../../source/compat.rst:71
+msgid "VMware versions 5.0, 5.1, and 5.5"
+msgstr ""
+
+# 12b79b83746f4c3bae71bf682e4d2f66
+#: ../../source/compat.rst:75
+msgid ""
+"Bare metal hosts are supported, which have no hypervisor. These hosts can "
+"run the following operating systems:"
+msgstr ""
+
+# 99717374baab44fca244b8c5d0f60f41
+#: ../../source/compat.rst:80
+msgid "RHEL or CentOS, v6.2 or 6.3"
+msgstr ""
+
+# 673c1eb4b2da40b3bd0c7865984fc1c6
+#: ../../source/compat.rst:82
+msgid "Use libvirt version 0.9.10 for CentOS 6.3"
+msgstr ""
+
+# 096ea4c057e0422cb91394032a6a22cf
+#: ../../source/compat.rst:86
+msgid "Fedora 17"
+msgstr ""
+
+# 4105889816dc4de2a016eb065383c49f
+#: ../../source/compat.rst:90
+msgid "Ubuntu 12.04"
+msgstr ""
+
+# b35052cb1655413bbf28d27a20ad0d49
+#: ../../source/compat.rst:92
+msgid ""
+"For more information, see the Hypervisor Compatibility Matrix in the "
+"CloudStack Installation Guide."
+msgstr ""
+
+# 0260f6594d3e4252bf08ff981d0a4d64
+#: ../../source/compat.rst:96
+msgid "Supported External Devices"
+msgstr ""
+
+# ba52dc4c032e49159af61327073557d2
+#: ../../source/compat.rst:100
+msgid "Netscaler VPX and MPX versions 9.3 and 10.e"
+msgstr ""
+
+# f9d4904e3edc4771ab5e2878587a39e1
+#: ../../source/compat.rst:104
+msgid "Netscaler SDX version 9.3"
+msgstr ""
+
+# 65cfdd4398524ff18e124aa27536fc04
+#: ../../source/compat.rst:108
+msgid "SRX (Model srx100b) versions 10.3 or higher"
+msgstr ""
+
+# ddaaa8237d914d99b8d667eaab49dd1c
+#: ../../source/compat.rst:112
+msgid "F5 10.1.0 (Build 3341.1084)"
+msgstr ""
+
+# ecc485f44e94497cb9ec57b64e6f8014
+#: ../../source/compat.rst:115
+msgid "Supported Browsers"
+msgstr ""
+
+# d895545db5e94734ad95d4d44354c002
+#: ../../source/compat.rst:117
+msgid ""
+"The CloudStack Web-based UI should be compatible with any modern browser, "
+"but it's possible that some browsers will not render portions of the UI "
+"reliably, depending on their support of Web standards. For best results, one"
+" of the following browsers recommended:"
+msgstr ""
+
+# 31f5d283ce004769846983ab0679138f
+#: ../../source/compat.rst:124
+msgid "Internet Explorer versions 10 and 11"
+msgstr ""
+
+# fdd3e5088bb34225b7fca3a19f38b69f
+#: ../../source/compat.rst:128
+msgid "Firefox version 26 or lower"
+msgstr ""
+
+# 5566cd6dd73b43759233def2e8beb178
+#: ../../source/compat.rst:132
+msgid "Google Chrome version 31"
+msgstr ""
+
+# 13b039b1a4fa4d33a686254acfd5b75d
+#: ../../source/compat.rst:136
+msgid "Safari 5"
+msgstr ""
diff --git a/source/releasenotes/locale/ja/LC_MESSAGES/index.mo b/source/releasenotes/locale/ja/LC_MESSAGES/index.mo
new file mode 100644
index 0000000..3570fba
--- /dev/null
+++ b/source/releasenotes/locale/ja/LC_MESSAGES/index.mo
Binary files differ
diff --git a/source/releasenotes/locale/ja/LC_MESSAGES/index.po b/source/releasenotes/locale/ja/LC_MESSAGES/index.po
new file mode 100644
index 0000000..9512a65
--- /dev/null
+++ b/source/releasenotes/locale/ja/LC_MESSAGES/index.po
@@ -0,0 +1,52 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+#
+# Translators:
+# sebgoa <runseb@gmail.com>, 2014
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-05 14:09+0100\n"
+"PO-Revision-Date: 2014-03-31 18:33+0000\n"
+"Last-Translator: sebgoa <runseb@gmail.com>\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/apache-cloudstack-release-notes-rtd/language/ja/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 208f4a89b044435a92aea7c8b4300a6a
+#: ../../source/index.rst:22
+msgid "Welcome to Apache CloudStack Release Notes"
+msgstr "Apache CloudStack リリースノートへようこそ"
+
+# 3419fa4841bb4c5b8a97aa893918cd10
+#: ../../source/index.rst:24
+msgid ""
+"This section describes the operating systems, browsers, and hypervisors that"
+" have been newly tested and certified compatible with CloudStack 4.3. Most "
+"earlier OS and hypervisor versions are also still supported for use with 4.3"
+" It might work well on other platforms, but the platforms listed below are "
+"the ones that are specifically tested against and are more likely to be able"
+" to help troubleshoot if you run into any issues."
+msgstr "この章では CloudStack 4.3 で新しくテストされ保証されているオペレーティングシステム、ブラウザ、ハイパーバイザーに関して記述しています。これまでの OS や ハイパーバイザーのバージョンの多くは引き続き 4.3 でサポートされ他のプラットフォームより安定して動作するでしょう。しかし以下に示されているプラットフォームは注力してテストされており何らかの問題が発生した際にトラブルシューティングを支援する可能性が高いものです。"
+
+# 5556135be49b4842a8386379fc3f66e4
+#: ../../source/index.rst:32
+msgid ""
+"This document contains information specific to this release of CloudStack, "
+"including upgrade instructions from prior releases, new features added to "
+"CloudStack, API changes, and issues fixed in the release. For installation "
+"instructions, please see the `Installation Guide <http://cloudstack-"
+"installation.readthedocs.org/en/latest/>`__. For usage and administration "
+"instructions, please see the `CloudStack Administrator's Guide <http"
+"://cloudstack-administration.readthedocs.org/en/latest/>`__."
+msgstr "このドキュメントは本 CloudStack リリースの特定情報を含んでおり、以前のバージョンからのアップグレード方法、CloudStack に追加された新機能、API の変更点、修正された問題が含まれます。インストール方法に関しては `インストールガイド <http://cloudstack-installation.readthedocs.org/en/latest/>`__. を参照してください。使い方と管理方法に関しては `CloudStack 管理者ガイド <http://cloudstack-administration.readthedocs.org/en/latest/>`__. を参照してください。"
+
+# a0536e5ac6e44bf2a3fb53a10aaac844
+#: ../../source/index.rst:38
+msgid "Contents:"
+msgstr "コンテンツ:"
diff --git a/source/releasenotes/locale/ja/LC_MESSAGES/rnotes.mo b/source/releasenotes/locale/ja/LC_MESSAGES/rnotes.mo
new file mode 100644
index 0000000..ad03993
--- /dev/null
+++ b/source/releasenotes/locale/ja/LC_MESSAGES/rnotes.mo
Binary files differ
diff --git a/source/releasenotes/locale/ja/LC_MESSAGES/rnotes.po b/source/releasenotes/locale/ja/LC_MESSAGES/rnotes.po
new file mode 100644
index 0000000..e53f851
--- /dev/null
+++ b/source/releasenotes/locale/ja/LC_MESSAGES/rnotes.po
@@ -0,0 +1,2600 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-05 14:09+0100\n"
+"PO-Revision-Date: 2014-03-31 15:24+0000\n"
+"Last-Translator: sebgoa <runseb@gmail.com>\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/apache-cloudstack-release-notes-rtd/language/ja/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 42d678eb2285488da05dc3cd6c263f02
+#: ../../source/rnotes.rst:18
+msgid "Upgrade Instructions for 4.3"
+msgstr ""
+
+# 41b628d034ee4fce9241de5ef66a7f6b
+#: ../../source/rnotes.rst:20
+msgid ""
+"This section contains upgrade instructions from prior versions of CloudStack"
+" to Apache CloudStack 4.3. We include instructions on upgrading to Apache "
+"CloudStack from pre-Apache versions of Citrix CloudStack (last version prior"
+" to Apache is 3.0.2) and from the releases made while CloudStack was in the "
+"Apache Incubator."
+msgstr ""
+
+# 6212699679f1434586e45ee4fd3827bc
+#: ../../source/rnotes.rst:26
+msgid ""
+"If you run into any issues during upgrades, please feel free to ask "
+"questions on users@cloudstack.apache.org or dev@cloudstack.apache.org."
+msgstr ""
+
+# 89e3526f428349e7bd2e3a6e07058278
+#: ../../source/rnotes.rst:30
+msgid "Upgrade from 4.2.0 to 4.3"
+msgstr ""
+
+# 8bbac42e272243b29532cab877c5b8bc
+#: ../../source/rnotes.rst:32
+msgid "This section will guide you from CloudStack 4.2 to CloudStack 4.3."
+msgstr ""
+
+# bb34709f92104ec98d45d233b9e44f06
+# e1b99036c1f94563a24d6d8d2cd82412
+# 2abaa3bf4c6c4910937c92ac89c2ee8c
+#: ../../source/rnotes.rst:34 ../../source/rnotes.rst:663
+#: ../../source/rnotes.rst:1197
+msgid "Any steps that are hypervisor-specific will be called out with a note."
+msgstr ""
+
+# 6b7c5646356f4d0fba9a8ba16c431a57
+# b7be4c0d68ee4cc2b0df2f511407fc6c
+# 56932859eab846ee8bde43bf4a39aaa0
+#: ../../source/rnotes.rst:36 ../../source/rnotes.rst:665
+#: ../../source/rnotes.rst:1201
+msgid ""
+"We recommend reading through this section once or twice before beginning "
+"your upgrade procedure, and working through it on a test system before "
+"working on a production system."
+msgstr ""
+
+# 505986b902774ceca679cfdbf2e13cce
+# 558231d5963c4b189228e328173557e4
+# 60afca54b4ef4d508b68b4186424a682
+# d501a610dcc94573a2e9c92aac6d9a00
+#: ../../source/rnotes.rst:40 ../../source/rnotes.rst:678
+#: ../../source/rnotes.rst:1223 ../../source/rnotes.rst:1641
+msgid ""
+"The following upgrade instructions should be performed regardless of "
+"hypervisor type."
+msgstr ""
+
+# 3a8581a1b3584a41b31a5c70b36d8020
+#: ../../source/rnotes.rst:46
+msgid ""
+"While running the existing 4.2.0 system, log in to the UI as root "
+"administrator."
+msgstr ""
+
+# dead12c2e5c54084b6fbba84c753c00a
+# 94bfbc9d533d4dd2abaa51ea8c274320
+# c651b785c87e463da7426af0a270417b
+# 6ae408a97d4c41e394b95b8859ea6969
+# 0a41d5ac486f4713a9d3efa71202bfb1
+#: ../../source/rnotes.rst:51 ../../source/rnotes.rst:687
+#: ../../source/rnotes.rst:1232 ../../source/rnotes.rst:1650
+#: ../../source/rnotes.rst:2475
+msgid "In the left navigation bar, click Templates."
+msgstr ""
+
+# 1b425d8481a34191926e9c1035f818c5
+# b5df3d99c2644a7b894dce754153c9ab
+# 69da380f577f46a3ab8f6e4f5cdec9f2
+# 5d01f7180135414d9affc57d6b8b3584
+# 4cd4c23255c54b12bd800870cd1c6fd8
+#: ../../source/rnotes.rst:55 ../../source/rnotes.rst:691
+#: ../../source/rnotes.rst:1236 ../../source/rnotes.rst:1654
+#: ../../source/rnotes.rst:2479
+msgid "In Select view, click Templates."
+msgstr ""
+
+# eb18c047f67d4bfe846ad7843047244b
+# 1af75b9c5972487488b73a0eec220d7d
+# 644051fde9ab49dba735cfe6f0a77f38
+# afc364dcc0be4e0796690a0a72680998
+# c2534c7e344a4a81a634d8666543d1eb
+#: ../../source/rnotes.rst:59 ../../source/rnotes.rst:695
+#: ../../source/rnotes.rst:1240 ../../source/rnotes.rst:1658
+#: ../../source/rnotes.rst:2483
+msgid "Click Register template."
+msgstr ""
+
+# f958c175bf8f4edfb68f850080032003
+# 57ba4c7f0ba24b1f8099281573aa01c2
+# c56adc75ca1d411587542598779ae293
+# a804e8c72fa84801bb4a68550f112e53
+# a19821955fdf4128b23a8bab0f787a1d
+#: ../../source/rnotes.rst:61 ../../source/rnotes.rst:697
+#: ../../source/rnotes.rst:1242 ../../source/rnotes.rst:1660
+#: ../../source/rnotes.rst:2485
+msgid "The Register template dialog box is displayed."
+msgstr ""
+
+# 5c05e1912faf49c58b6b71e38915a8b1
+# c2ff2045faca4ca0854a6378f7dbf05e
+# 74adacefbc094e0da36da3afece913f4
+# 6b719f75b2ec44c4a954cef0fad48b25
+#: ../../source/rnotes.rst:65 ../../source/rnotes.rst:701
+#: ../../source/rnotes.rst:1246 ../../source/rnotes.rst:1664
+msgid ""
+"In the Register template dialog box, specify the following values (do not "
+"change these):"
+msgstr ""
+
+# 008bbb4c8ab2489d997f3fac9bd8dd3e
+# b6de8b708b154b379af5a94da6953d30
+# d25fd8cdb35342d5b76d3af23ec8b3d0
+# 70d66ffed2864e94964b8bd40b257176
+# 63d69aaddcac4e519cb72d2b914359f3
+#: ../../source/rnotes.rst:69 ../../source/rnotes.rst:705
+#: ../../source/rnotes.rst:1250 ../../source/rnotes.rst:1668
+#: ../../source/rnotes.rst:2493
+msgid "Hypervisor"
+msgstr "ハイパーバイザー"
+
+# d1781bdac5cb40e684a6888e8eb052fd
+# a861163d98014b449c8b501efb2812ce
+# 1c3c49173dff4c07a6ae2d2febf1ab37
+# 9134492ad9f5407781bc408bb9494aa6
+# b89357f04fcd4549959d20bcb82b6800
+#: ../../source/rnotes.rst:69 ../../source/rnotes.rst:705
+#: ../../source/rnotes.rst:1250 ../../source/rnotes.rst:1668
+#: ../../source/rnotes.rst:2493
+msgid "Description"
+msgstr "説明"
+
+# 85616c2b776642458b6b074f0955b7ec
+# 390402007d6748c1bfbc48a03eb1ff4a
+# 16b265fc693d40059afb1a0557c5b1b0
+# c23d316b1adb4a10aa4506f6df8d7695
+# 0a964e1ec1434396b92cf81ca7da353a
+#: ../../source/rnotes.rst:71 ../../source/rnotes.rst:707
+#: ../../source/rnotes.rst:1252 ../../source/rnotes.rst:1670
+#: ../../source/rnotes.rst:2495
+msgid "XenServer"
+msgstr ""
+
+# d46f926f5a5e454589899b93b4c51eeb
+# f202c480c879466e84a2bc7ee2ef8eb1
+# 70bc5eec456146758139bfeafcd6c254
+# 2d50b6b5c36f4415af39d1007d8035f4
+# 3e50d8b797504a0c9250d43fc8be49e2
+#: ../../source/rnotes.rst:71 ../../source/rnotes.rst:707
+#: ../../source/rnotes.rst:1252 ../../source/rnotes.rst:1670
+#: ../../source/rnotes.rst:2495
+msgid "Name: systemvm-xenserver-4.3"
+msgstr ""
+
+# 60087b2d154f4132b46f52086e5ef029
+# b05063dc53a542889111c74ddf820fc8
+# e4ee3f30d36348b79761563c511fcc53
+# 2f2a7a9e5b99483787ad9929b2ee2e19
+# 015ea9102fe34d138c41765527102de1
+#: ../../source/rnotes.rst:73 ../../source/rnotes.rst:709
+#: ../../source/rnotes.rst:1254 ../../source/rnotes.rst:1672
+#: ../../source/rnotes.rst:2497
+msgid "Description: systemvm-xenserver-4.3"
+msgstr ""
+
+# aab4e46f0f074fd494f398a0f2376690
+# 6f3059ed5a924af1a6af9888de9f60f8
+# f1cfa864cc48446da7d15b78d13e8cec
+# b0d327bfcfb748ddb9a3b12e65dfdbca
+# 78393b0f0b05474fbda4d5e95cc7bbdf
+#: ../../source/rnotes.rst:75 ../../source/rnotes.rst:711
+#: ../../source/rnotes.rst:1256 ../../source/rnotes.rst:1674
+#: ../../source/rnotes.rst:2499
+msgid ""
+"URL: http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14"
+"-master-xen.vhd.bz2"
+msgstr ""
+
+# d439e558d2494c82ba35d4b7d5141ac8
+# 351e1644cbf84a30af80410ba146f523
+# 0d02e5117823415d95d11bb0f9dec178
+# 9c9085c2e247415a9ee61fb1f0c2e7a1
+# 6323bb49cb9d4386b9e3636b89975a1e
+# ce606edd6e0043e483827424308e9eae
+# b9857085067e474680eeb7dd3e26ba6e
+# 0b639ca277014c348ca0ef447d5ad81b
+# 0d4ddf72a2884ac680c470c5e4f80dd5
+# 730c0e58fb4f495bb028b139240c2c82
+# 5b27e86a9ca742e598279f8564c13c56
+# fcc6a47719614722975ba2ba45768c4f
+#: ../../source/rnotes.rst:78 ../../source/rnotes.rst:103
+#: ../../source/rnotes.rst:128 ../../source/rnotes.rst:714
+#: ../../source/rnotes.rst:739 ../../source/rnotes.rst:764
+#: ../../source/rnotes.rst:1259 ../../source/rnotes.rst:1284
+#: ../../source/rnotes.rst:1309 ../../source/rnotes.rst:2502
+#: ../../source/rnotes.rst:2527 ../../source/rnotes.rst:2552
+msgid "Zone: Choose the zone where this hypervisor is used"
+msgstr ""
+
+# 838318c9d31645ae99bd3e79e18940e0
+# 89d8cd6fc1f74356ac886e43bc4187b9
+# 27b2a7a43fae446c926fc8bbecd5d7f1
+# 9ba791b12686435eb446164e4517f7ac
+# 24c021d0aac94240bbe06b215175b4c9
+#: ../../source/rnotes.rst:80 ../../source/rnotes.rst:716
+#: ../../source/rnotes.rst:1261 ../../source/rnotes.rst:1680
+#: ../../source/rnotes.rst:2504
+msgid "Hypervisor: XenServer"
+msgstr ""
+
+# d69de9c666aa46f992dea502e19b70a9
+# 893acc0852ac4e70b8530c3e6660c855
+# 25d54017a01647eca16c41b394917469
+# 99d94266a0a540348c29e7ddca07f3a4
+# d302f3b8b27c44dd896488739bd364d7
+#: ../../source/rnotes.rst:82 ../../source/rnotes.rst:718
+#: ../../source/rnotes.rst:1263 ../../source/rnotes.rst:1682
+#: ../../source/rnotes.rst:2506
+msgid "Format: VHD"
+msgstr ""
+
+# 4b6a013e94f2406396f926647afd9372
+# ecc1aa91806f4aef9673429da7c08880
+# 3b131d605d6c4ceebf36d0629e200f6e
+# c85c58df68cd489abeb977c3e68019c7
+# 49d9c0788b314116a9ccb36c5733b3a9
+# 1ca463f215ec4f3b84128380c4a05890
+# cade67e03efc472fa6e133c9640a306d
+# 4e5b73a422da4d40bd312e4b135c3f74
+# a321a8102e2a46b3a77d89daca362cb9
+# 2c86881fb2194b039886df7a968c6fdd
+# 67974420a6e6499d99cfec0a4eacf00c
+# 805a3f0bd7f2442e9686ff640c8549d3
+# 67256469d5de4d358947f1fdd2068ea7
+# ad16207a4d3b4f3782eac427c7b47f61
+# e54a1866e7f44b69a9ac67a5c8737d9f
+#: ../../source/rnotes.rst:84 ../../source/rnotes.rst:109
+#: ../../source/rnotes.rst:134 ../../source/rnotes.rst:720
+#: ../../source/rnotes.rst:745 ../../source/rnotes.rst:770
+#: ../../source/rnotes.rst:1265 ../../source/rnotes.rst:1290
+#: ../../source/rnotes.rst:1315 ../../source/rnotes.rst:1684
+#: ../../source/rnotes.rst:1710 ../../source/rnotes.rst:1736
+#: ../../source/rnotes.rst:2508 ../../source/rnotes.rst:2533
+#: ../../source/rnotes.rst:2558
+msgid ""
+"OS Type: Debian GNU/Linux 7.0 (64-bit) (or the highest Debian release number"
+" available in the dropdown)"
+msgstr ""
+
+# 6cd60538b91c4ca5bc7535ddf246faff
+# 5ddafdb9f3134b599e1817da2e457ddd
+# 356e260a95954844b66ec5df22cd0772
+# bf9acaffb00444edb70986d08b54eb95
+# 8a92f91fd6c34944af0588a8c0778a3d
+# c06527d037c44b8eb7978e30e850be1e
+# 940bef4e5d9540f191979e277d89e7c2
+# f164d0f782ec4d21a99b07420e0b0956
+# 1bf3285c07c2470f981c3091069c3844
+# 84232d240a6244029ddb76715ad99792
+# 8aa46285358b4a2cb083a76342d12f2d
+# f2ee96c3a9d14c41a0fec175098732c9
+# 44052173c6294a59afc5ff05ac365a2c
+# ed71f8f74e9d44388bc335e25c5e266c
+# 5c35014e67244638806bcbc59a5a8e99
+#: ../../source/rnotes.rst:88 ../../source/rnotes.rst:113
+#: ../../source/rnotes.rst:138 ../../source/rnotes.rst:724
+#: ../../source/rnotes.rst:749 ../../source/rnotes.rst:774
+#: ../../source/rnotes.rst:1269 ../../source/rnotes.rst:1294
+#: ../../source/rnotes.rst:1319 ../../source/rnotes.rst:1688
+#: ../../source/rnotes.rst:1714 ../../source/rnotes.rst:1740
+#: ../../source/rnotes.rst:2512 ../../source/rnotes.rst:2537
+#: ../../source/rnotes.rst:2562
+msgid "Extractable: no"
+msgstr ""
+
+# c610924f4de5446c86e8cf570a23ec59
+# f7e0fbc65cb44ec9b685cc665d535123
+# 6b3fe309850a4b7c9ac5c1d5d6821f38
+# 1d3cb70b0c4142c78ba821a0ee011f78
+# fc2911c8b6bb4849b7925489c9ae2a01
+# b211fe77f3b3422b83580c73840ce837
+# ccdeca12ad42483f832b6c5636b06d42
+# 34c794f2b5d9429884c5d5279c21d9e6
+# 90cc0c25be9a46c29323f9ad2c1f4454
+# 094de1f60c2a489f9fd7c7303adbb05c
+# 8eeb67728c8145fd89aa217a2d7096ca
+# ae18a78f3b63424a8a270f64abe4f297
+# e89815bd8daf4980a3c32701ca3c3593
+# bf7a491dc39b418caa3c7784c57f1d87
+# 4968cdbc67bf4f46b02e432ee7ed9025
+#: ../../source/rnotes.rst:90 ../../source/rnotes.rst:115
+#: ../../source/rnotes.rst:140 ../../source/rnotes.rst:726
+#: ../../source/rnotes.rst:751 ../../source/rnotes.rst:776
+#: ../../source/rnotes.rst:1271 ../../source/rnotes.rst:1296
+#: ../../source/rnotes.rst:1321 ../../source/rnotes.rst:1690
+#: ../../source/rnotes.rst:1716 ../../source/rnotes.rst:1742
+#: ../../source/rnotes.rst:2514 ../../source/rnotes.rst:2539
+#: ../../source/rnotes.rst:2564
+msgid "Password Enabled: no"
+msgstr ""
+
+# d6152128090641c8a551f7042fd18c6b
+# 762f5dec3e704bd8998af37e07921d72
+# 3336b3b2a5f44f03aa571c6f2a8e4165
+# 437c7bc51da84b8789b8bb404791f285
+# 8144ecbdaa224a31b211841bcd3fccb1
+# f04444c7107142249b3cd0632f799c32
+# 96ec3fa5df8742788bf8fa4f8972014f
+# 972a8dfca90b433088bf3d63e7c15939
+# 8038d59b9d754d27a13c188e4c8bad3e
+# 831638958e1741bfb19b4f4cf7432ce3
+# bc44062b6198465899b9a11ca85491aa
+# decb386fa81b401982b49671d7184a34
+# e358075912924d02b0b06fd7f5ad5dd9
+# 673458355d034ed0bd3eb1b9375f4b85
+# 476237cedab440c586788be1d6df2f5d
+#: ../../source/rnotes.rst:92 ../../source/rnotes.rst:117
+#: ../../source/rnotes.rst:142 ../../source/rnotes.rst:728
+#: ../../source/rnotes.rst:753 ../../source/rnotes.rst:778
+#: ../../source/rnotes.rst:1273 ../../source/rnotes.rst:1298
+#: ../../source/rnotes.rst:1323 ../../source/rnotes.rst:1692
+#: ../../source/rnotes.rst:1718 ../../source/rnotes.rst:1744
+#: ../../source/rnotes.rst:2516 ../../source/rnotes.rst:2541
+#: ../../source/rnotes.rst:2566
+msgid "Public: no"
+msgstr ""
+
+# b51fe881ba9e4e88af3f1a8661d3a404
+# 5e2ef5de96b54b2ba6c4a5021d63ed04
+# 68b4d45fd6db489393c8216607ae4973
+# f0e3f79f0c474ff7a02a627ad5fd3e01
+# b52b0917a65d4458b247ace2ec5974d0
+# eb8782d77531425abe596b14aa3ca8b7
+# 946fa41fee4b4f1d8dc7d7be82013fe8
+# 1ebb133a1b9e4d639f9a8bf3f0617a6a
+# 661c21e32c514f79a4f81f0357e125d8
+# 390461162ef446769dffda2d6b0acbe5
+# 4e995dea789045949fb42600ad9ade03
+# 61a2fb46acd34449942ec665442fb311
+# 32c1401f85fe44199f8bc0ad300a6b61
+# 24c2ef0a6929479cad3441c1d0909176
+# 7929dd67193e4a06afaa845ea7786ae5
+#: ../../source/rnotes.rst:94 ../../source/rnotes.rst:119
+#: ../../source/rnotes.rst:144 ../../source/rnotes.rst:730
+#: ../../source/rnotes.rst:755 ../../source/rnotes.rst:780
+#: ../../source/rnotes.rst:1275 ../../source/rnotes.rst:1300
+#: ../../source/rnotes.rst:1325 ../../source/rnotes.rst:1694
+#: ../../source/rnotes.rst:1720 ../../source/rnotes.rst:1746
+#: ../../source/rnotes.rst:2518 ../../source/rnotes.rst:2543
+#: ../../source/rnotes.rst:2568
+msgid "Featured: no"
+msgstr ""
+
+# 11882b63ef7a4207989d951b3bb0aa7e
+# f7e6ba6ca99e489cafa9e01826c00694
+# bc092dbc933f4a7a860a9cbdeecaac4c
+# ed43f33f14554bfbb225108a681122a7
+# 3f801c529ea544f38628bf1cdd48fc8f
+#: ../../source/rnotes.rst:96 ../../source/rnotes.rst:732
+#: ../../source/rnotes.rst:1277 ../../source/rnotes.rst:1696
+#: ../../source/rnotes.rst:2520
+msgid "KVM"
+msgstr ""
+
+# 8e80783043a140f2b20e8402b4f220a5
+# 65d65d30eeed44899982886ca191f56f
+# c5764e41dac2435c816a427dc218d49b
+# 5d87a38451e14cd79f91ce9b5d97b65f
+# a2a697b6834f4bd88f5388964e56cace
+#: ../../source/rnotes.rst:96 ../../source/rnotes.rst:732
+#: ../../source/rnotes.rst:1277 ../../source/rnotes.rst:1696
+#: ../../source/rnotes.rst:2520
+msgid "Name: systemvm-kvm-4.3"
+msgstr ""
+
+# dd9acd3e777b43b7be90baa619188718
+# f447dba905de4318b415de8adca145a7
+# 1bdbe2601bba4382afef6d603f5f6924
+# 9ecd547930b3472bb042e1b836f9055c
+# e41898b69f6f4312804f9e8edb6800be
+#: ../../source/rnotes.rst:98 ../../source/rnotes.rst:734
+#: ../../source/rnotes.rst:1279 ../../source/rnotes.rst:1698
+#: ../../source/rnotes.rst:2522
+msgid "Description: systemvm-kvm-4.3"
+msgstr ""
+
+# 18112d67045a4826a21324e45043c1f3
+# 9d7818ae080e4b6980b33c55edcd3ee1
+# 048a5c6ac93648a7b149fa2723ec3beb
+# 565c06cb13304129ba04c27978dfc8d8
+# b8cf8c952bf14f4fb5f7cf084d11aa98
+#: ../../source/rnotes.rst:100 ../../source/rnotes.rst:736
+#: ../../source/rnotes.rst:1281 ../../source/rnotes.rst:1700
+#: ../../source/rnotes.rst:2524
+msgid ""
+"URL: http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14"
+"-master-kvm.qcow2.bz2"
+msgstr ""
+
+# b823ddc9d9f54579be8a164f1949daba
+# f0f674de683c45fb8ce275d210bcebab
+# ac4620c3578b415989d0fb5c0a7f4a73
+# 4d0c71801b434a328dede28902babdc2
+# ed682ff3eca04e2d830b5f51069f5c84
+#: ../../source/rnotes.rst:105 ../../source/rnotes.rst:741
+#: ../../source/rnotes.rst:1286 ../../source/rnotes.rst:1706
+#: ../../source/rnotes.rst:2529
+msgid "Hypervisor: KVM"
+msgstr ""
+
+# e60ebf3c4ba14a35a525462a3101d310
+# 5955b72117514bb783eca575e0523ffb
+# 1c02fe8f1e744fd49394aae64ee5e641
+# 16bb7ae5db4948848078473e7381acd9
+# 27e2c08b6e184428a34365ede87022a7
+#: ../../source/rnotes.rst:107 ../../source/rnotes.rst:743
+#: ../../source/rnotes.rst:1288 ../../source/rnotes.rst:1708
+#: ../../source/rnotes.rst:2531
+msgid "Format: QCOW2"
+msgstr ""
+
+# 2ab69eec46fa4d5fa6e3c5a948936a2a
+# e81be8f0c17e4f2ea26367a9e8a19b54
+# 64b557c5c2ec4e158743408500e1435f
+# d1d572a3c2794d58b48e885153e29199
+# e6e24a4ae6054a6ca04673a1ab1ace8c
+#: ../../source/rnotes.rst:121 ../../source/rnotes.rst:757
+#: ../../source/rnotes.rst:1302 ../../source/rnotes.rst:1722
+#: ../../source/rnotes.rst:2545
+msgid "VMware"
+msgstr ""
+
+# 5c7c14896c464e89a40ed46ec9f1badc
+# 8daf63b1e5de487dbfb052b1b1b5b52b
+# 3accf7c3794c4d089081b73e16c957fc
+# 12f83ab21c4040d8baff0e3c021cfc96
+# 9a9f6bbe66bc485ca94003e7b451ddf7
+#: ../../source/rnotes.rst:121 ../../source/rnotes.rst:757
+#: ../../source/rnotes.rst:1302 ../../source/rnotes.rst:1722
+#: ../../source/rnotes.rst:2545
+msgid "Name: systemvm-vmware-4.3"
+msgstr ""
+
+# 92780e97400449fdbbf2ef0bd374b1cb
+# 22948f9a1e0f43b98635627529b72279
+# cdb07852eb024ada85739a45b8b2fb31
+# 681aad54f06945aab0f6686a28b37aea
+# 026be4dcadd44f8eb288449ea7c5bb71
+#: ../../source/rnotes.rst:123 ../../source/rnotes.rst:759
+#: ../../source/rnotes.rst:1304 ../../source/rnotes.rst:1724
+#: ../../source/rnotes.rst:2547
+msgid "Description: systemvm-vmware-4.3"
+msgstr ""
+
+# 9edb2b100d91490993b3139d7695b2a8
+# b68299a5d4374958b34b758386cc85cd
+# d96632db3762451da83bea92b5586509
+# 03002181282749228c393ace2ca1ab28
+# dfcba25531e24b87a8081fe1761c585c
+#: ../../source/rnotes.rst:125 ../../source/rnotes.rst:761
+#: ../../source/rnotes.rst:1306 ../../source/rnotes.rst:1726
+#: ../../source/rnotes.rst:2549
+msgid ""
+"URL: http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14"
+"-master-vmware.ova"
+msgstr ""
+
+# 2739f087399644a286227208c62d16f2
+# 27ee5363cc7645c0974a787822cc2731
+# c04dae621a60468f89942bdf35214aa7
+# 4410929e67ae4b9a8ccde344ee6635a6
+# 0b0ae4d5aaf4402688e03b8cbce733b6
+#: ../../source/rnotes.rst:130 ../../source/rnotes.rst:766
+#: ../../source/rnotes.rst:1311 ../../source/rnotes.rst:1732
+#: ../../source/rnotes.rst:2554
+msgid "Hypervisor: VMware"
+msgstr ""
+
+# 7c525c40349d426da8d4edb0fad6a3a1
+# 43f012151a5a4dca828b7ac5686d17f6
+# c5a8185466a3403ca88731b04acb0640
+# bb4c9e98ec2740ec84c4a6966efc02ff
+# f61eaa2f59c7479fa85cfbb35196f2ee
+#: ../../source/rnotes.rst:132 ../../source/rnotes.rst:768
+#: ../../source/rnotes.rst:1313 ../../source/rnotes.rst:1734
+#: ../../source/rnotes.rst:2556
+msgid "Format: OVA"
+msgstr ""
+
+# cc7b963a69ea4b88aeeedb09e5be332d
+# f03e04a6fc68422c9e99141bb72c1a8e
+# c03b65c705f64cfc98d04f6597064847
+#: ../../source/rnotes.rst:149 ../../source/rnotes.rst:671
+#: ../../source/rnotes.rst:1207
+msgid ""
+"Most users of CloudStack manage the installation and upgrades of CloudStack "
+"with one of Linux's predominant package systems, RPM or APT. This guide "
+"assumes you'll be using RPM and Yum (for Red Hat Enterprise Linux or "
+"CentOS), or APT and Debian packages (for Ubuntu)."
+msgstr ""
+
+# 723a52379d254df48e67493131d59a6e
+#: ../../source/rnotes.rst:156
+msgid ""
+"Create RPM or Debian packages (as appropriate) and a repository from the 4.3"
+" source, or check the Apache CloudStack downloads page at "
+"`http://cloudstack.apache.org/downloads.html "
+"<http://cloudstack.apache.org/downloads.html>`__ for package repositories "
+"supplied by community members. You will need them for step `9 <#upgrade-deb-"
+"packages-4.3>`__ or step `12 <#upgrade-rpm-packages-4.3>`__."
+msgstr ""
+
+# f34250896ef542fda4fd42546a65a5d4
+# 030a350e5cd2436297a5a4519df23e0d
+# 957e3d9727b24f8eb2ee7f45c9b76863
+#: ../../source/rnotes.rst:163 ../../source/rnotes.rst:793
+#: ../../source/rnotes.rst:1219
+msgid ""
+"Instructions for creating packages from the CloudStack source are in the "
+"`Installation Guide <http://cloudstack.apache.org/docs/en-US/index.html>`__."
+msgstr ""
+
+# 42052b8c68a6456ab40cacbc15103d1f
+# d5e34b3f6dd043978b90d0583a16c946
+# 0dd8514fea1f4e97bf0dc98ca9fd66b2
+#: ../../source/rnotes.rst:169 ../../source/rnotes.rst:799
+#: ../../source/rnotes.rst:1331
+msgid ""
+"Stop your management server or servers. Run this on all management server "
+"hosts:"
+msgstr ""
+
+# d5ae2a32ec9d4814b44cdff2aaf4ec3a
+# 0ae0988de33b418ab302b9b1185708c2
+# cb9a9840e38d4c94bedf6bd6f8ceb590
+#: ../../source/rnotes.rst:178 ../../source/rnotes.rst:808
+#: ../../source/rnotes.rst:1340
+msgid ""
+"If you are running a usage server or usage servers, stop those as well:"
+msgstr ""
+
+# 770393d964b04d53b7ccc6412a5b3c6a
+# c5e8ca3e3527463aa2cbdb2240ed1bbf
+# e889a951d681486388064f4f31e91989
+#: ../../source/rnotes.rst:187 ../../source/rnotes.rst:817
+#: ../../source/rnotes.rst:1349
+msgid ""
+"Make a backup of your MySQL database. If you run into any issues or need to "
+"roll back the upgrade, this will assist in debugging or restoring your "
+"existing environment. You'll be prompted for your password."
+msgstr ""
+
+# f9fbf2fee0e64639ad8782f8303ddf7b
+#: ../../source/rnotes.rst:198
+msgid "Perform the following to verify the artifacts:"
+msgstr ""
+
+# e63dfd2fe1084bacb083d72eb5db8371
+#: ../../source/rnotes.rst:202
+msgid "(optional) Install GPG keys if needed:"
+msgstr ""
+
+# af9567066dc845fdb1ec7366b444120f
+#: ../../source/rnotes.rst:210
+msgid "Import the GPG keys stored in the source distribution's KEYS file"
+msgstr ""
+
+# 049005cfc12041f8b1e292490c30f4c4
+#: ../../source/rnotes.rst:216
+msgid ""
+"Alternatively, download the signing keys, the IDs found in the KEYS file, "
+"individually by using a keyserver."
+msgstr ""
+
+# a3097e42d1084f048a59d85830de53d3
+#: ../../source/rnotes.rst:219
+msgid "For example:"
+msgstr ""
+
+# d2b32a530b2a4cd796599dd23a5f1221
+#: ../../source/rnotes.rst:227
+msgid "Verify signatures and hash files:"
+msgstr ""
+
+# 1564e50432084d9d98e98a456444e4c9
+#: ../../source/rnotes.rst:235
+msgid ""
+"Each of these commands should return no output. Any output from them implies"
+" that there is a difference between the hash you generated locally and the "
+"hash that has been pulled from the server."
+msgstr ""
+
+# 8f767747ab0a4c8dbd0e1198c243bff0
+#: ../../source/rnotes.rst:242
+msgid "Get the commit hash from the VOTE email."
+msgstr ""
+
+# f35ea10fc96a44de830d0206391f8969
+#: ../../source/rnotes.rst:244
+msgid ""
+"For example: ``4cd60f3d1683a3445c3248f48ae064fb573db2a1``. The value changes"
+" between releases."
+msgstr ""
+
+# 6c23307830ae47e6b2dd297e55ad9bc3
+#: ../../source/rnotes.rst:249
+msgid "Create two new temporary directories:"
+msgstr ""
+
+# 15ea8b909be7467686ff82c62dcb1e74
+#: ../../source/rnotes.rst:258
+msgid "Check out the 4.3 branch:"
+msgstr ""
+
+# 6e12f6014678491393792d02fc13ac58
+#: ../../source/rnotes.rst:268
+msgid "Unpack the release artifact:"
+msgstr ""
+
+# 0e59c95dfb4e49a380b57fc8d78dd5ab
+#: ../../source/rnotes.rst:277
+msgid ""
+"Compare the contents of the release artifact with the contents pulled from "
+"the repo:"
+msgstr ""
+
+# 2d63c16b73194f3bbe52bb8bbce5c656
+#: ../../source/rnotes.rst:284
+msgid "Ensure that content is the same."
+msgstr ""
+
+# ba868de916d1458aaf74f2ceaed20269
+#: ../../source/rnotes.rst:288
+msgid "Verify the Code License Headers:"
+msgstr ""
+
+# 70de015831004787afd4554bf5d06815
+#: ../../source/rnotes.rst:295
+msgid ""
+"The build fails if any non-compliant files are present that are not "
+"specifically excluded from the ASF license header requirement. You can "
+"optionally review the target/rat.txt file after the run completes. Passing "
+"the build implies that RAT certifies that the files are compliant and this "
+"test is passed."
+msgstr ""
+
+# e5a4e1d35a774619b436bcf6e9be9222
+# dd7ca70744e14d20861895d26f347a5d
+#: ../../source/rnotes.rst:303 ../../source/rnotes.rst:828
+msgid ""
+"(KVM Only) If primary storage of type local storage is in use, the path for "
+"this storage needs to be verified to ensure it passes new validation. Check "
+"local storage by querying the cloud.storage\\_pool table:"
+msgstr ""
+
+# 15205eb55014464fb0a975958c7f2d5a
+# 895acb18e41a45fabf1ab6bf500e2152
+#: ../../source/rnotes.rst:312 ../../source/rnotes.rst:837
+msgid ""
+"If local storage paths are found to have a trailing forward slash, remove "
+"it:"
+msgstr ""
+
+# bc2246bf393547aabcf817be27dc60c7
+#: ../../source/rnotes.rst:321
+msgid ""
+"If you are using Ubuntu, follow this procedure to upgrade your packages. If "
+"not, skip to step `12 <#upgrade-rpm-packages-4.3>`__."
+msgstr ""
+
+# b59040bf9a744dbf82ee0fd68cd8c137
+# 5a90c117d3be4bd2bf7438b0a446a878
+# 1683f96797754542a758f642d4f4fae1
+# 8027b164288e47328241d47cb193a0a7
+# 71ef1804ff0c40ca91afd6189a4e564d
+#: ../../source/rnotes.rst:324 ../../source/rnotes.rst:851
+#: ../../source/rnotes.rst:1408 ../../source/rnotes.rst:1850
+#: ../../source/rnotes.rst:2680
+msgid ""
+"**Community Packages:** This section assumes you're using the community "
+"supplied packages for CloudStack. If you've created your own packages and "
+"APT repository, substitute your own URL for the ones used in these examples."
+msgstr ""
+
+# 56b9d98656664482be98c200f1856254
+# 19351e795331422c98e4a905875390e3
+# 74c4b1459a144077aeb0c9f63951ca2f
+# 231674bdf08047fea592149bf4f4ddb8
+# 0a42937bde294e2091dac1a3a0b86a52
+#: ../../source/rnotes.rst:328 ../../source/rnotes.rst:855
+#: ../../source/rnotes.rst:1412 ../../source/rnotes.rst:1854
+#: ../../source/rnotes.rst:2684
+msgid ""
+"The first order of business will be to change the sources list for each "
+"system with CloudStack packages. This means all management servers, and any "
+"hosts that have the KVM agent. (No changes should be necessary for hosts "
+"that are running VMware or Xen.)"
+msgstr ""
+
+# 5d189abeac584f7f8553e4d41c9965d6
+# 84e85d30c2dd40edbca568d9e419cad0
+# a157030034164bfbb32f6259e6ae759b
+# 9143325723c04e8dbe1773d7762b6ada
+# 5f8137d1d4784df2842e703d772e9d8c
+#: ../../source/rnotes.rst:333 ../../source/rnotes.rst:860
+#: ../../source/rnotes.rst:1417 ../../source/rnotes.rst:1859
+#: ../../source/rnotes.rst:2689
+msgid ""
+"Start by opening ``/etc/apt/sources.list.d/cloudstack.list`` on any systems "
+"that have CloudStack packages installed."
+msgstr ""
+
+# c11b9c6bf46e4ceeb988a252e4a6f44e
+# 66acc455c74e4b60a8a973b187e8db0f
+# 77e3b00fd01a4461b6b56a739374c223
+# 2aa42c46e3d84198bfe64eccc145ab97
+# 59d99fc5fa3e4fe89dded04722ba49bb
+#: ../../source/rnotes.rst:336 ../../source/rnotes.rst:863
+#: ../../source/rnotes.rst:1420 ../../source/rnotes.rst:1862
+#: ../../source/rnotes.rst:2692
+msgid "This file should have one line, which contains:"
+msgstr ""
+
+# 0315b6db253046839da27e9afd21dac8
+# 31b497170b494959b37f944a08fcedd4
+# 43e35965702d4a6f914fe60b4db32d55
+# 236ee7a215514b2f8aaca32f6fc0eb34
+# f95f05a212424cf5bc5d5c55b3e585eb
+#: ../../source/rnotes.rst:342 ../../source/rnotes.rst:869
+#: ../../source/rnotes.rst:1426 ../../source/rnotes.rst:1868
+#: ../../source/rnotes.rst:2698
+msgid "We'll change it to point to the new package repository:"
+msgstr ""
+
+# fe18287ca92649d994652022a0a389fe
+# 7ef37ac6e8b04b51b22655148ee43880
+# b6fdfa285ff04ecd8c6a8d70aca45711
+# b773059057dc4b7a8fdd18420c7aff6b
+# 3344b7380cd54082872676747d07b745
+# 19d0366892ff4b1198fa32bd69859746
+# e2d8d36e8860452a9c23b62f39fd3330
+#: ../../source/rnotes.rst:348 ../../source/rnotes.rst:561
+#: ../../source/rnotes.rst:875 ../../source/rnotes.rst:1093
+#: ../../source/rnotes.rst:1547 ../../source/rnotes.rst:1874
+#: ../../source/rnotes.rst:2819
+msgid ""
+"If you're using your own package repository, change this line to read as "
+"appropriate for your 4.3 repository."
+msgstr ""
+
+# 11d93d2eff9c46d8ad99acb75658a9d0
+# f33a797d7e5a4cb68d5f85f94b785dba
+# d2a25e4c47e8400cba504f5918c6374c
+# 498e43c4b60e42b5a6e92ee3f3fc8423
+# 1fab03282141473daab0aaa3c229441a
+#: ../../source/rnotes.rst:353 ../../source/rnotes.rst:880
+#: ../../source/rnotes.rst:1437 ../../source/rnotes.rst:1879
+#: ../../source/rnotes.rst:2709
+msgid "Now update your apt package list:"
+msgstr ""
+
+# 039423ac897546afa8394f0dc3762981
+# 98851837e2c7438fbb9dd33756aef5c6
+# 198ef0103fda4b0eb4c0bae19000f845
+# b2b659bca4774c74b9b3daf1f509726f
+# 04034e3390cb43938e79c05191907c58
+#: ../../source/rnotes.rst:361 ../../source/rnotes.rst:888
+#: ../../source/rnotes.rst:1445 ../../source/rnotes.rst:1887
+#: ../../source/rnotes.rst:2717
+msgid ""
+"Now that you have the repository configured, it's time to install the "
+"``cloudstack-management`` package. This will pull in any other dependencies "
+"you need."
+msgstr ""
+
+# 71dbbbaa4b0545df97bedc9c6d71c5a8
+# dea91b1d5e664521ae9fe2a0c8c2e92d
+# 8188541359f342f78e5cf9d60d972549
+# 46f51ea2d101426d95c74c17f3dc5cde
+#: ../../source/rnotes.rst:371 ../../source/rnotes.rst:898
+#: ../../source/rnotes.rst:1455 ../../source/rnotes.rst:1897
+msgid "You will need to manually install the ``cloudstack-agent`` package:"
+msgstr ""
+
+# 1ef7dae76e35474393b92874cbb36532
+# 739b3c30b2e04fc398bfd6859b4815fc
+# 209b0d0315264225ab5c6168301135d4
+# 8a235d41942341f3bf47878b970aa03d
+# 513550d9f3f34fdeb7c07f9b2e7afcf3
+#: ../../source/rnotes.rst:378 ../../source/rnotes.rst:905
+#: ../../source/rnotes.rst:1462 ../../source/rnotes.rst:1904
+#: ../../source/rnotes.rst:2734
+msgid ""
+"During the installation of ``cloudstack-agent``, APT will copy your "
+"``agent.properties``, ``log4j-cloud.xml``, and ``environment.properties`` "
+"from ``/etc/cloud/agent`` to ``/etc/cloudstack/agent``."
+msgstr ""
+
+# 9701bd815cf148148208dc7b91302f40
+# a8ae754b5fd04a13a867fc2d3c187ce0
+# 085a733706c546dba0f059578892c4a7
+# a728a0e4c92b44fbba5d0b45d114950d
+# 13448224ffa74fc094bfe11a9115fbfa
+#: ../../source/rnotes.rst:381 ../../source/rnotes.rst:910
+#: ../../source/rnotes.rst:1467 ../../source/rnotes.rst:1909
+#: ../../source/rnotes.rst:2739
+msgid "When prompted whether you wish to keep your configuration, say Yes."
+msgstr ""
+
+# af79487ad81341af8144cc2106099f23
+# 73131961a6d2466ba2717ecee3cdf920
+# 9d016ec139344e6186aa43b71c983a76
+# c9409b4b169746b096a8c48a2d7d1ce2
+# 4dd1829a8065410880bea2c97a9b2fa0
+# 32b52f92d69d4c089d800cd10017471f
+# 4dae2cb96e99419d95c76ea7e705ca00
+# c6f1d3d341e84dd0a7ceddce6c604363
+# 83e25244a86f44339113b774652c1bbf
+# dad75aecbba8407e901a4322bb1eec9f
+#: ../../source/rnotes.rst:386 ../../source/rnotes.rst:586
+#: ../../source/rnotes.rst:915 ../../source/rnotes.rst:1118
+#: ../../source/rnotes.rst:1472 ../../source/rnotes.rst:1577
+#: ../../source/rnotes.rst:1914 ../../source/rnotes.rst:2019
+#: ../../source/rnotes.rst:2744 ../../source/rnotes.rst:2849
+msgid ""
+"Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a "
+"line that reads:"
+msgstr ""
+
+# 48202ecf3c764be3afe78387c441645d
+# a8b296466110468da08acfa6cc535135
+# 0e27905c523846a5b404e94b239aa343
+# f463a9539cd6440fae0efe92c14e90f1
+# e910c345f581438da404660d14d56c36
+# 4e51e4f9328545d6bf02d7de41f3d787
+# 70428b7ab64442af9fd0fac15dca01f7
+# d0451a72b44d4a609356f0537372b57f
+# fd3ad945ef1a48958c77d9e5b5aa0055
+# 9b43bdb2b8664c22a2e2b69038d81093
+#: ../../source/rnotes.rst:394 ../../source/rnotes.rst:594
+#: ../../source/rnotes.rst:923 ../../source/rnotes.rst:1126
+#: ../../source/rnotes.rst:1480 ../../source/rnotes.rst:1585
+#: ../../source/rnotes.rst:1922 ../../source/rnotes.rst:2027
+#: ../../source/rnotes.rst:2752 ../../source/rnotes.rst:2857
+msgid "If not, add the line."
+msgstr ""
+
+# 042c9c6d0f13426387a84291fc291952
+# 03fb714adf8a48aa9d99aabcae5a1610
+# 6351d0f660b14dc499fbf3e875658080
+# 43b1707916e74b7784e3b08a2c6ed881
+# 8f76d80899b34f7ca30adb493f085fef
+# 8efc5c39fdd64533957cc3941da4e1b4
+# 5cfeecd7389e4866acfb4440d0d1c020
+# dae7b83474684e2bb0a24a4589826983
+# e182686d199f4cd6b8e3691430995278
+# b031852eec1a450da4b42dc1c66d7b69
+#: ../../source/rnotes.rst:398 ../../source/rnotes.rst:598
+#: ../../source/rnotes.rst:927 ../../source/rnotes.rst:1130
+#: ../../source/rnotes.rst:1484 ../../source/rnotes.rst:1589
+#: ../../source/rnotes.rst:1926 ../../source/rnotes.rst:2031
+#: ../../source/rnotes.rst:2756 ../../source/rnotes.rst:2861
+msgid "Restart the agent:"
+msgstr ""
+
+# 6081bbfdf7d24c4b8b9ab07614b56273
+# 7c211e87de09465bb5a539ebd4a01754
+#: ../../source/rnotes.rst:408 ../../source/rnotes.rst:937
+msgid ""
+"(VMware only) Additional steps are required for each VMware cluster. These "
+"steps will not affect running guests in the cloud. These steps are required "
+"only for clouds using VMware clusters:"
+msgstr ""
+
+# 34f20e5a1a254983baf1a289562457cc
+# b65cec52a81d40248b4f640d3c356aaa
+#: ../../source/rnotes.rst:414 ../../source/rnotes.rst:943
+msgid "Stop the Management Server:"
+msgstr ""
+
+# 7f9596344d6b4824b56b3e9254bbc16c
+# 36ca6513825a4e8d923a5838a123b0f7
+#: ../../source/rnotes.rst:422 ../../source/rnotes.rst:951
+msgid "Generate the encrypted equivalent of your vCenter password:"
+msgstr ""
+
+# efb6ab9a82e7426e84f110c176a707f6
+# 2198298a7a6842dfb8afd2735968909d
+#: ../../source/rnotes.rst:428 ../../source/rnotes.rst:957
+msgid ""
+"Store the output from this step, we need to add this in cluster\\_details "
+"table and vmware\\_data\\_center tables in place of the plain text password"
+msgstr ""
+
+# 99acd44b40a34912a76fde6eccc9e0a2
+# ed1e34bd9d12479088c430270a20c80e
+#: ../../source/rnotes.rst:434 ../../source/rnotes.rst:963
+msgid ""
+"Find the ID of the row of cluster\\_details table that you have to update:"
+msgstr ""
+
+# 8f3bd3ed0592477f8ceea7930a008d38
+# 631c4f13cefc4c5b94e6f10a94ebfba1
+#: ../../source/rnotes.rst:447 ../../source/rnotes.rst:976
+msgid "Update the plain text password with the encrypted one"
+msgstr ""
+
+# e1f63620a0904624a050970144760d41
+# ba1a7b976ab7471da8f4ae5cc6acc69c
+# 8d017dc5b3614e3786fd14c3f098dd4f
+# 62427dddea394f98a9eac0cb913f80c1
+#: ../../source/rnotes.rst:455 ../../source/rnotes.rst:480
+#: ../../source/rnotes.rst:984 ../../source/rnotes.rst:1009
+msgid "Confirm that the table is updated:"
+msgstr ""
+
+# 2f577273146045c4855666e8069007e6
+# 5a358193fff4466ca2d1afab27a439c3
+#: ../../source/rnotes.rst:463 ../../source/rnotes.rst:992
+msgid ""
+"Find the ID of the correct row of vmware\\_data\\_center that you want to "
+"update"
+msgstr ""
+
+# 44774239c7124aeea278ffd8a1e0ce41
+# 49d7985782fe41b284a9f659a0b07c1c
+#: ../../source/rnotes.rst:472 ../../source/rnotes.rst:1001
+msgid "update the plain text password with the encrypted one:"
+msgstr ""
+
+# 56448a6a49a4408386be85dab4b2315f
+# 1aacd1189d6b4ab7ba4daa2c32937c9a
+#: ../../source/rnotes.rst:488 ../../source/rnotes.rst:1017
+msgid "Start the CloudStack Management server"
+msgstr ""
+
+# b2f224ce5298470e91f2b8d31135cd1e
+# c5bf1bb0d38e4fa5aa1253aaa4abd1a7
+#: ../../source/rnotes.rst:496 ../../source/rnotes.rst:1025
+msgid ""
+"(KVM only) Additional steps are required for each KVM host. These steps will"
+" not affect running guests in the cloud. These steps are required only for "
+"clouds using KVM as hosts and only on the KVM hosts."
+msgstr ""
+
+# f4d538249e0345cab4b0b811c939cb00
+# d50828a7a95f4604b0fa2213975047a5
+#: ../../source/rnotes.rst:503 ../../source/rnotes.rst:1032
+msgid "Configure the CloudStack yum repository as detailed above."
+msgstr ""
+
+# f06d2d146d724032b87cb4226d6fac93
+# 351c9808bd414461b803718057d20224
+# 85cb78aba52f4a3583b5d5faf5143640
+# 4136fdbd755442ddbe031d3bc309e73c
+#: ../../source/rnotes.rst:507 ../../source/rnotes.rst:1036
+#: ../../source/rnotes.rst:2138 ../../source/rnotes.rst:3053
+msgid "Stop the running agent."
+msgstr ""
+
+# 1cb7133384b5402cb2cf14632153c4cd
+# 64a138d932f747c98f6efcb0c8ca0346
+#: ../../source/rnotes.rst:515 ../../source/rnotes.rst:1044
+msgid "Update the agent software."
+msgstr ""
+
+# 9efa8f702b9145af9ec5fdfa36823bbb
+# 9312871613354beb9803f1d746527094
+# 8fba178c912e43a193d037247d356a6d
+# 8d9b6d1f39c14466a3fe4569b44a8595
+#: ../../source/rnotes.rst:523 ../../source/rnotes.rst:1052
+#: ../../source/rnotes.rst:2189 ../../source/rnotes.rst:3111
+msgid "Start the agent."
+msgstr ""
+
+# f86632e46670495698f5d20c200fdd69
+#: ../../source/rnotes.rst:531
+msgid ""
+"If you are using CentOS or RHEL, follow this procedure to upgrade your "
+"packages. If not, skip to step `14 <#restart-system-vms-4.3>`__."
+msgstr ""
+
+# f4329c69f54b476da773a8c35a08e778
+# 85e264dbc7dd4ed19606e6dfa79f9a16
+# 11da3a3cb2d54cdca41f7622006bfbce
+# 4306b36338c846fd8bac053165a33cbf
+# ad1b98990fb64bb3b57c3296a7ea607d
+#: ../../source/rnotes.rst:534 ../../source/rnotes.rst:1066
+#: ../../source/rnotes.rst:1521 ../../source/rnotes.rst:1963
+#: ../../source/rnotes.rst:2793
+msgid ""
+"**Community Packages:** This section assumes you're using the community "
+"supplied packages for CloudStack. If you've created your own packages and "
+"yum repository, substitute your own URL for the ones used in these examples."
+msgstr ""
+
+# 6d6ebc753fba484eb9204b6781fda970
+# e742839c52f640f0a426c73a4fd018df
+#: ../../source/rnotes.rst:538 ../../source/rnotes.rst:1070
+msgid ""
+"The first order of business will be to change the yum repository for each "
+"system with CloudStack packages. This means all management servers, and any "
+"hosts that have the KVM agent."
+msgstr ""
+
+# 3ffbf1503681481e95b4c336a25564e0
+# d9ec84ef6bac453591c608d69295622e
+#: ../../source/rnotes.rst:542 ../../source/rnotes.rst:1074
+msgid ""
+"(No changes should be necessary for hosts that are running VMware or Xen.)"
+msgstr ""
+
+# e894df58f47f40edb96c40339871544b
+# bd819c73ef4845019e7cb1e100c664fe
+# 7fa2b208cd6e45a28e45fd0e3f51b7c3
+# eba94a5371074f1fb589564435926056
+# 1884cef709f34a88abecec2bf3833c3a
+#: ../../source/rnotes.rst:545 ../../source/rnotes.rst:1077
+#: ../../source/rnotes.rst:1531 ../../source/rnotes.rst:1973
+#: ../../source/rnotes.rst:2803
+msgid ""
+"Start by opening ``/etc/yum.repos.d/cloudstack.repo`` on any systems that "
+"have CloudStack packages installed."
+msgstr ""
+
+# ac7e0cad1d17428e896f935bd5c5b384
+# dcbce38317ba4e89b9ef6d2db7c802b2
+# 467cc3a4a560458f9b054f2e58d20ee4
+# 16512f5b43624e84979e9af514a36ab3
+# 707eba890aa945709aa0459269af8308
+#: ../../source/rnotes.rst:548 ../../source/rnotes.rst:1080
+#: ../../source/rnotes.rst:1534 ../../source/rnotes.rst:1976
+#: ../../source/rnotes.rst:2806
+msgid "This file should have content similar to the following:"
+msgstr ""
+
+# babaf567e6f5404483ed6ee0bf637444
+#: ../../source/rnotes.rst:558
+msgid ""
+"If you are using the community provided package repository, change the base "
+"url to http://cloudstack.apt-get.eu/rhel/4.3/"
+msgstr ""
+
+# d89b9a5996ce4f0f9ac0c3e436719fb5
+# b1cfb2c096db48ba93d8b2f09c56031b
+#: ../../source/rnotes.rst:566 ../../source/rnotes.rst:1098
+msgid ""
+"Now that you have the repository configured, it's time to install the "
+"``cloudstack-management`` package by upgrading the older ``cloudstack-"
+"management`` package."
+msgstr ""
+
+# 65f51f39a8bf4fcf8083f0342a056bc5
+# 1a05c4de3f944f14a407be8137766bc0
+# beb8ff931b2a4d8c98c73a4fa8ac4204
+# d74cc786e6214deea323b8028f08a467
+# 83a307beac844266953b7bbed75a7d6e
+#: ../../source/rnotes.rst:576 ../../source/rnotes.rst:1108
+#: ../../source/rnotes.rst:1562 ../../source/rnotes.rst:2004
+#: ../../source/rnotes.rst:2834
+msgid ""
+"For KVM hosts, you will need to upgrade the ``cloud-agent`` package, "
+"similarly installing the new version as ``cloudstack-agent``."
+msgstr ""
+
+# c40af3663afc4704b56545eddb37609c
+# a4c37669c6fd442882bf4165eff9dc21
+#: ../../source/rnotes.rst:608 ../../source/rnotes.rst:1140
+msgid "Now it's time to restart the management server"
+msgstr ""
+
+# ebc23ee9a8fe452a94e969a3b3ed3797
+# bb9d6984a87e48d1a5ffc67450096bb8
+#: ../../source/rnotes.rst:616 ../../source/rnotes.rst:1148
+msgid ""
+"Once you've upgraded the packages on your management servers, you'll need to"
+" restart the system VMs. Ensure that the admin port is set to 8096 by using "
+"the \"integration.api.port\" global parameter. This port is used by the "
+"cloud-sysvmadm script at the end of the upgrade procedure. For information "
+"about how to set this parameter, see \"Setting Global Configuration "
+"Parameters\" in the Installation Guide. Changing this parameter will require"
+" management server restart. Also make sure port 8096 is open in your local "
+"host firewall to do this."
+msgstr ""
+
+# e87299dd3d554c7e805ebe052b4921cb
+# c4d82271ad904af8a92a1ae13e75bf2f
+# b8019db7253342c791c16841737a94c3
+#: ../../source/rnotes.rst:625 ../../source/rnotes.rst:1157
+#: ../../source/rnotes.rst:1603
+msgid ""
+"There is a script that will do this for you, all you need to do is run the "
+"script and supply the IP address for your MySQL instance and your MySQL "
+"credentials:"
+msgstr ""
+
+# 00030e4dafd740129590b1781499186e
+# f68656ca3312479db2afefff67e1bdd6
+# 9cb6b77dd29243c79031b6bd19da51ff
+#: ../../source/rnotes.rst:633 ../../source/rnotes.rst:1165
+#: ../../source/rnotes.rst:1611
+msgid ""
+"You can monitor the log for progress. The process of restarting the system "
+"VMs can take an hour or more."
+msgstr ""
+
+# bccf889f462e49b4b1bb423c1e88b5c8
+# 1ac4420efcdc492f9fb919b61307b42a
+# 5dcddcbb73614aa4af06e592c9348913
+#: ../../source/rnotes.rst:640 ../../source/rnotes.rst:1172
+#: ../../source/rnotes.rst:1618
+msgid "The output to ``sysvm.log`` will look something like this:"
+msgstr ""
+
+# 42227647c4b4492d83c87f97545d5390
+# 8a3282874711468dbaacf5fb628280bf
+#: ../../source/rnotes.rst:653 ../../source/rnotes.rst:1187
+msgid ""
+"**For Xen Hosts: Copy vhd-utils:** This step is only for CloudStack installs"
+" that are using Xen hosts."
+msgstr ""
+
+# 973fb456e9984a6b88e6e3c4df1b77dd
+# a399a1e3318245928b48752177f60df6
+# 7b800cae60f54399a1b3ca872c19412e
+#: ../../source/rnotes.rst:655 ../../source/rnotes.rst:1189
+#: ../../source/rnotes.rst:1631
+msgid ""
+"Copy the file ``vhd-utils`` to ``/usr/share/cloudstack-"
+"common/scripts/vm/hypervisor/xenserver``."
+msgstr ""
+
+# 0c4cb838a9a9481a8d93a180dcc079f8
+#: ../../source/rnotes.rst:659
+msgid "Upgrade from 4.1.x to 4.3"
+msgstr ""
+
+# 68c72fe017a24b6faaa07d9f4d650e5b
+#: ../../source/rnotes.rst:661
+msgid ""
+"This section will guide you from CloudStack 4.1.x versions to CloudStack "
+"4.3."
+msgstr ""
+
+# ab0415d71764422e9cc4345bc744c67f
+#: ../../source/rnotes.rst:682
+msgid ""
+"While running the existing 4.1.x system, log in to the UI as root "
+"administrator."
+msgstr ""
+
+# 5d21f203ae88464ba82a2bb5644b39c6
+#: ../../source/rnotes.rst:786
+msgid ""
+"Create RPM or Debian packages (as appropriate) and a repository from the "
+"4.2.1 source, or check the Apache CloudStack downloads page at "
+"`http://cloudstack.apache.org/downloads.html "
+"<http://cloudstack.apache.org/downloads.html>`__ for package repositories "
+"supplied by community members. You will need them for step `8 <#upgrade-deb-"
+"packages-41to42>`__ or step `11 <#upgrade-rpm-packages-41to42>`__."
+msgstr ""
+
+# 55cd20754528476498956b7167b4dd64
+#: ../../source/rnotes.rst:846
+msgid ""
+"If you are using Ubuntu, follow this procedure to upgrade your packages. If "
+"not, skip to step `11 <#upgrade-rpm-packages-41to42>`__."
+msgstr ""
+
+# ca81934545a041b387b565f0c0413aad
+#: ../../source/rnotes.rst:1060
+msgid ""
+"If you are using CentOS or RHEL, follow this procedure to upgrade your "
+"packages. If not, skip to step `13 <#restart-system-vms-41to42>`__."
+msgstr ""
+
+# ade8209fbda64faba8a63c157b288803
+#: ../../source/rnotes.rst:1090
+msgid ""
+"If you are using the community provided package repository, change the base "
+"url to http://cloudstack.apt-get.eu/rhel/4.2/"
+msgstr ""
+
+# d9130ccbfe84403ab6625f9dfdcab053
+#: ../../source/rnotes.rst:1193
+msgid "Upgrade from 4.0.x to 4.3"
+msgstr ""
+
+# bd7f93faa1db403fa9dd6896441f6009
+#: ../../source/rnotes.rst:1195
+msgid ""
+"This section will guide you from CloudStack 4.0.x versions to CloudStack "
+"4.3."
+msgstr ""
+
+# 72900bd6795d4323b06ce5e775e4281d
+#: ../../source/rnotes.rst:1199
+msgid ""
+"**Package Structure Changes:** The package structure for CloudStack has "
+"changed significantly since the 4.0.x releases. If you've compiled your own "
+"packages, you'll notice that the package names and the number of packages "
+"has changed. This is *not* a bug. However, this *does* mean that the "
+"procedure is not as simple as an ``apt-get upgrade`` or ``yum update``, so "
+"please follow this section carefully."
+msgstr ""
+
+# 9925093a67ba46d4a82afe4983cde3d6
+#: ../../source/rnotes.rst:1212
+msgid ""
+"Create RPM or Debian packages (as appropriate) and a repository from the "
+"4.1.0 source, or check the Apache CloudStack downloads page at "
+"`http://cloudstack.apache.org/downloads.html "
+"<http://cloudstack.apache.org/downloads.html>`__ for package repositories "
+"supplied by community members. You will need them for step `9 <#upgrade-deb-"
+"packages-40to41>`__ or step `10 <#upgrade-rpm-packages-40to41>`__."
+msgstr ""
+
+# e0355ef90969449aa728622612f70057
+#: ../../source/rnotes.rst:1227
+msgid ""
+"While running the existing 4.0.0 system, log in to the UI as root "
+"administrator."
+msgstr ""
+
+# 524983e688224bf18c091cba0ce6ba2c
+#: ../../source/rnotes.rst:1360
+msgid ""
+"Whether you're upgrading a Red Hat/CentOS based system or Ubuntu based "
+"system, you're going to need to stop the CloudStack management server before"
+" proceeding."
+msgstr ""
+
+# c4bb349458c3436aa5064c8348a804cb
+#: ../../source/rnotes.rst:1370
+msgid ""
+"If you have made changes to ``/etc/cloud/management/components.xml``, you'll"
+" need to carry these over manually to the new file, "
+"``/etc/cloudstack/management/componentContext.xml``. This is not done "
+"automatically. (If you're unsure, we recommend making a backup of the "
+"original ``components.xml`` to be on the safe side."
+msgstr ""
+
+# 91d1e1359bf54d59b1b810b6935a20fa
+# 70de4e87d0024a18b3298a6ed81193fb
+#: ../../source/rnotes.rst:1378 ../../source/rnotes.rst:2078
+msgid ""
+"After upgrading to 4.3, API clients are expected to send plain text "
+"passwords for login and user creation, instead of MD5 hash. Incase, api "
+"client changes are not acceptable, following changes are to be made for "
+"backward compatibility:"
+msgstr ""
+
+# 6738c1d868b146448f8933886adfa669
+#: ../../source/rnotes.rst:1383
+msgid ""
+"Modify componentsContext.xml, and make PlainTextUserAuthenticator as the "
+"default authenticator (1st entry in the userAuthenticators adapter list is "
+"default)"
+msgstr ""
+
+# f8b44cf359d148f4b91aab1902dd8495
+#: ../../source/rnotes.rst:1400
+msgid ""
+"PlainTextUserAuthenticator works the same way MD5UserAuthenticator worked "
+"prior to 4.3."
+msgstr ""
+
+# b79f73b2986e4326b50f4543b60a80eb
+#: ../../source/rnotes.rst:1405
+msgid ""
+"If you are using Ubuntu, follow this procedure to upgrade your packages. If "
+"not, skip to step `10 <#upgrade-rpm-packages-40to41>`__."
+msgstr ""
+
+# b5c3c9cedf64481396311fb07233e58b
+#: ../../source/rnotes.rst:1432
+msgid ""
+"If you're using your own package repository, change this line to read as "
+"appropriate for your 4.1.0 repository."
+msgstr ""
+
+# 0eaa898254a64902b5c567db1298842f
+# b871c8f1d0a84e2e861c12292bc46977
+# 8081e0b4d2f64021944ed4638d2d0226
+#: ../../source/rnotes.rst:1494 ../../source/rnotes.rst:1936
+#: ../../source/rnotes.rst:2766
+msgid ""
+"During the upgrade, ``log4j-cloud.xml`` was simply copied over, so the logs "
+"will continue to be added to ``/var/log/cloud/agent/agent.log``. There's "
+"nothing *wrong* with this, but if you prefer to be consistent, you can "
+"change this by copying over the sample configuration file:"
+msgstr ""
+
+# f8f1c5326e634caca24199a666ee0792
+# 81564ab5762b44eda70a58cda80022d2
+# eed567da89fd4e0eb4d3ae5a48a726d6
+#: ../../source/rnotes.rst:1508 ../../source/rnotes.rst:1950
+#: ../../source/rnotes.rst:2780
+msgid ""
+"Once the agent is running, you can uninstall the old cloud-\\* packages from"
+" your system:"
+msgstr ""
+
+# 68ef47a188cb4ef89974f80e71de5475
+#: ../../source/rnotes.rst:1517
+msgid ""
+"If you are using CentOS or RHEL, follow this procedure to upgrade your "
+"packages. If not, skip to step `11 <#restart-system-vms-40to41>`__."
+msgstr ""
+
+# a2c27f6a615f432f92bbf1522037096e
+# 78492d493d8a47c482846c2e22f8a67e
+# eda4705004e144ef847024d20f666082
+#: ../../source/rnotes.rst:1525 ../../source/rnotes.rst:1967
+#: ../../source/rnotes.rst:2797
+msgid ""
+"The first order of business will be to change the yum repository for each "
+"system with CloudStack packages. This means all management servers, and any "
+"hosts that have the KVM agent. (No changes should be necessary for hosts "
+"that are running VMware or Xen.)"
+msgstr ""
+
+# 50534c980d8f486280114b8ca158a788
+#: ../../source/rnotes.rst:1544
+msgid ""
+"If you are using the community provided package repository, change the "
+"baseurl to http://cloudstack.apt-get.eu/rhel/4.1/"
+msgstr ""
+
+# 7ddaef2707504d33bb47147835052b82
+# cf3028e1960b447f901c681d9adc50ad
+# 16364561824242ae97931f392f26b118
+#: ../../source/rnotes.rst:1552 ../../source/rnotes.rst:1994
+#: ../../source/rnotes.rst:2824
+msgid ""
+"Now that you have the repository configured, it's time to install the "
+"``cloudstack-management`` package by upgrading the older ``cloud-client`` "
+"package."
+msgstr ""
+
+# 3b35fa76dd24499599dc04b6fb44d0dc
+# 43cc60efd03844569f473a2ff71e4dfe
+# f4638220dedf413d8516450e9ac81e50
+#: ../../source/rnotes.rst:1570 ../../source/rnotes.rst:2012
+#: ../../source/rnotes.rst:2842
+msgid ""
+"During the installation of ``cloudstack-agent``, the RPM will copy your "
+"``agent.properties``, ``log4j-cloud.xml``, and ``environment.properties`` "
+"from ``/etc/cloud/agent`` to ``/etc/cloudstack/agent``."
+msgstr ""
+
+# 61bde7141a654f528c9308eb8aea7ba9
+#: ../../source/rnotes.rst:1599
+msgid ""
+"Once you've upgraded the packages on your management servers, you'll need to"
+" restart the system VMs. Make sure port 8096 is open in your local host "
+"firewall to do this."
+msgstr ""
+
+# 93c8bb7ab89b4303b1ebaa9983b03b6c
+#: ../../source/rnotes.rst:1629
+msgid ""
+"*For Xen Hosts: Copy vhd-utils:** This step is only for CloudStack installs "
+"that are using Xen hosts."
+msgstr ""
+
+# 59b97f43649345cfbe2049be86d9c389
+#: ../../source/rnotes.rst:1635
+msgid "Upgrade from 3.0.x to 4.3"
+msgstr ""
+
+# 5e32327fa74d40f182eefac57ec8e916
+#: ../../source/rnotes.rst:1637
+msgid ""
+"This section will guide you from Citrix CloudStack 3.0.x to Apache "
+"CloudStack 4.3. Sections that are hypervisor-specific will be called out "
+"with a note."
+msgstr ""
+
+# 1e472e681f1744d2a30240396cb0f661
+#: ../../source/rnotes.rst:1645
+msgid ""
+"While running the existing 3.0.x system, log in to the UI as root "
+"administrator."
+msgstr ""
+
+# c598b4573abc40ef8cb1f8ff3f8ba1b4
+# 287bba7730ba467ab67c78556c15abc0
+# 50c89d21fbe341c0bc10c00240d82caf
+#: ../../source/rnotes.rst:1677 ../../source/rnotes.rst:1703
+#: ../../source/rnotes.rst:1729
+msgid "Zone: Choose the zone where this hypervisor is used used"
+msgstr ""
+
+# 45960608e6c94d5d9d95ee664a2ce3d2
+#: ../../source/rnotes.rst:1751
+msgid ""
+"Watch the screen to be sure that the template downloads successfully and "
+"enters the READY state. Do not proceed until this is successful."
+msgstr ""
+
+# 369af9370c2e41dca9f4bfaf0f1519ab
+# a8d838ac79c247a4afd1a5950dd416b2
+#: ../../source/rnotes.rst:1757 ../../source/rnotes.rst:2587
+msgid ""
+"(KVM on RHEL 6.0/6.1 only) If your existing CloudStack deployment includes "
+"one or more clusters of KVM hosts running RHEL 6.0 or RHEL 6.1, perform the "
+"following:"
+msgstr ""
+
+# f185884dbe5143e4ba60c4a1cc8e7227
+# 4b69e99638574f33ba5cc56e6d049b75
+#: ../../source/rnotes.rst:1763 ../../source/rnotes.rst:2593
+msgid ""
+"Ensure that you upgrade the operating system version on those hosts before "
+"upgrading CloudStack"
+msgstr ""
+
+# f6b49bea48cd44a78ba1ba39ce1d62c9
+# fa9c3347ce1d4ca99fa94db744a028aa
+#: ../../source/rnotes.rst:1766 ../../source/rnotes.rst:2596
+msgid ""
+"To do that, change the yum repository for each system with CloudStack "
+"packages, that implies that all the Management Servers and any hosts that "
+"have the KVM agent."
+msgstr ""
+
+# e3cffd2be44544da877c3ee50b05232c
+# f25e1a97111848df9ad153e4bd8b7ae4
+#: ../../source/rnotes.rst:1772 ../../source/rnotes.rst:2602
+msgid ""
+"Open ``/etc/yum.repos.d/cloudstack.repo`` on any systems that have "
+"CloudStack packages installed."
+msgstr ""
+
+# 30309403085a4433baa9037014c18d72
+# 1eb4b5dfd9ba4c4eb0cc3b4516056dc7
+#: ../../source/rnotes.rst:1777 ../../source/rnotes.rst:2607
+msgid "Edit as follows:"
+msgstr ""
+
+# 6d41dd815dd64a108dd55bdfcea801aa
+# 8015ca898771446d8c032203cb37154f
+#: ../../source/rnotes.rst:1792 ../../source/rnotes.rst:2622
+msgid ""
+"If you are using the community provided package repository, change the "
+"baseurl to http:// cloudstack.apt-get.eu/rhel/4.2/"
+msgstr ""
+
+# f9d19fa077d9497abf70c710a81f4db6
+# 83164b94d94849a68fc3b8dc68a2a054
+#: ../../source/rnotes.rst:1795 ../../source/rnotes.rst:2625
+msgid ""
+"If you are using your own package repository, change this line to read as "
+"appropriate for your 4.2.0 repository."
+msgstr ""
+
+# 37e87120204c4aa9b575d43425c2db54
+# 43ef10811cdb46c8ad19cd456586fbf8
+#: ../../source/rnotes.rst:1800 ../../source/rnotes.rst:2630
+msgid ""
+"Now that you have the repository configured, upgrade the host operating "
+"system from RHEL 6.0 to 6.3:"
+msgstr ""
+
+# 5e5c81225020442e83c240f9c770f4a1
+# dbd504a399f4491591cc84dbe61e67f5
+#: ../../source/rnotes.rst:1809 ../../source/rnotes.rst:2639
+msgid "Stop all Usage Servers if running. Run this on all Usage Server hosts."
+msgstr ""
+
+# 5e48ffe2e97c4830906dbd90fcd3ef5d
+# c455c85393ef42f4a9c1528886c3e09f
+#: ../../source/rnotes.rst:1818 ../../source/rnotes.rst:2648
+msgid "Stop the Management Servers. Run this on all Management Server hosts."
+msgstr ""
+
+# 6969d11093b8440988a59fa1dff6be6e
+# 9c4f5494faa54226bfeea797c0d3bcdf
+#: ../../source/rnotes.rst:1826 ../../source/rnotes.rst:2656
+msgid ""
+"On the MySQL master, take a backup of the MySQL databases. We recommend "
+"performing this step even in test upgrades. If there is an issue, this will "
+"assist with debugging."
+msgstr ""
+
+# 825da40bc5314b5a8b130e89ad1a9a5c
+# 72fb79e016be496fa214442911ce060c
+#: ../../source/rnotes.rst:1830 ../../source/rnotes.rst:2660
+msgid ""
+"In the following commands, it is assumed that you have set the root password"
+" on the database, which is a CloudStack recommended best practice. "
+"Substitute your own MySQL root password."
+msgstr ""
+
+# 26589f96a49f4066bd0ab2a72a1f7317
+# 16d0068c27204a0faa66b905d52befe0
+#: ../../source/rnotes.rst:1841 ../../source/rnotes.rst:2671
+msgid ""
+"Either build RPM/DEB packages as detailed in the Installation Guide, or use "
+"one of the community provided yum/apt repositories to gain access to the "
+"CloudStack binaries."
+msgstr ""
+
+# f056a426534b49afbd1365f026fe2d2b
+#: ../../source/rnotes.rst:1847
+msgid ""
+"If you are using Ubuntu, follow this procedure to upgrade your packages. If "
+"not, skip to step `8 <#upgrade-rpm-packages-302>`__."
+msgstr ""
+
+# 84016fd7d3884343b978b2fd6c708da7
+#: ../../source/rnotes.rst:1959
+msgid ""
+"If you are using CentOS or RHEL, follow this procedure to upgrade your "
+"packages. If not, skip to step `9 <#correct-components-xml-302>`__."
+msgstr ""
+
+# 6cebde363347471d9ddc60b659269ddb
+# 269ad8a52be048a9a1fdbccb09243abb
+#: ../../source/rnotes.rst:1986 ../../source/rnotes.rst:2816
+msgid ""
+"If you are using the community provided package repository, change the "
+"baseurl to http://cloudstack.apt-get.eu/rhel/4.2/"
+msgstr ""
+
+# e6d488cc033942d08f511b1af789458b
+# 90df2c6c84c146b0b44da5df81753bb6
+#: ../../source/rnotes.rst:1989 ../../source/rnotes.rst:2704
+msgid ""
+"If you're using your own package repository, change this line to read as "
+"appropriate for your 4.2.0 repository."
+msgstr ""
+
+# eb96e4c8fee5460c87b905716ccb7e42
+#: ../../source/rnotes.rst:2041
+msgid ""
+"If you have made changes to your copy of "
+"``/etc/cloud/management/components.xml`` the changes will be preserved in "
+"the upgrade. However, you need to do the following steps to place these "
+"changes in a new version of the file which is compatible with version 4.2.0."
+msgstr ""
+
+# aefa34afaad7414d8c78efbb8e62e94c
+#: ../../source/rnotes.rst:2049
+msgid ""
+"Make a backup copy of ``/etc/cloud/management/components.xml``. For example:"
+msgstr ""
+
+# a89a3722670e4031b416e5940ecff4f6
+# 4b5606edfece4d73a061033c44291198
+#: ../../source/rnotes.rst:2058 ../../source/rnotes.rst:2895
+msgid ""
+"Copy ``/etc/cloud/management/components.xml.rpmnew`` to create a new "
+"``/etc/cloud/management/components.xml``:"
+msgstr ""
+
+# 28450742b3f54afc970bb28dc3cb8c55
+#: ../../source/rnotes.rst:2067
+msgid ""
+"Merge your changes from the backup file into the new ``components.xml``."
+msgstr ""
+
+# 602debbc4519432cb9eb5cd657212990
+#: ../../source/rnotes.rst:2074
+msgid ""
+"If you have more than one management server node, repeat the upgrade steps "
+"on each node."
+msgstr ""
+
+# c3a3f8aab28945a38940615c4aa7c674
+# ae12189a99b14d70b751a1a0ad5e8e78
+#: ../../source/rnotes.rst:2083 ../../source/rnotes.rst:2918
+msgid ""
+"Modify componentContext.xml, and make PlainTextUserAuthenticator as the "
+"default authenticator (1st entry in the userAuthenticators adapter list is "
+"default)"
+msgstr ""
+
+# db4b5e693294450689d29e7b397a66e1
+#: ../../source/rnotes.rst:2100
+msgid ""
+"PlainTextUserAuthenticator works the same way MD5UserAuthenticator worked "
+"prior to 4.3"
+msgstr ""
+
+# 5431071dd41c473d9eefccc4845ef2ad
+# 754d5fda4f9443cba5574bf18d1c2299
+#: ../../source/rnotes.rst:2105 ../../source/rnotes.rst:3017
+msgid ""
+"Start the first Management Server. Do not start any other Management Server "
+"nodes yet."
+msgstr ""
+
+# 5ca91f223ce34c07831f7c5423255427
+#: ../../source/rnotes.rst:2112
+msgid ""
+"Wait until the databases are upgraded. Ensure that the database upgrade is "
+"complete. After confirmation, start the other Management Servers one at a "
+"time by running the same command on each node."
+msgstr ""
+
+# 17144f244bcc4d5ba9f0274e3e20dd93
+#: ../../source/rnotes.rst:2116
+msgid ""
+"Failing to restart the Management Server indicates a problem in the upgrade."
+" Having the Management Server restarted without any issues indicates that "
+"the upgrade is successfully completed."
+msgstr ""
+
+# 5e74545331a7449fb38c9b4562ef3a4b
+# 1059ad4546844e30a69e255db2aada33
+#: ../../source/rnotes.rst:2120 ../../source/rnotes.rst:3031
+msgid ""
+"Start all Usage Servers (if they were running on your previous version). "
+"Perform this on each Usage Server host."
+msgstr ""
+
+# c6c743684c67470bb2e60153d066d39f
+#: ../../source/rnotes.rst:2123
+msgid "``# service cloudstack-usage start``"
+msgstr ""
+
+# 494054707df24576ac8b9a414f1a75b1
+#: ../../source/rnotes.rst:2127
+msgid ""
+"Additional steps are required for each KVM host. These steps will not affect"
+" running guests in the cloud. These steps are required only for clouds using"
+" KVM as hosts and only on the KVM hosts."
+msgstr ""
+
+# b80fdea5eb3f43ef82d8f401098353b5
+#: ../../source/rnotes.rst:2133
+msgid ""
+"Configure a yum or apt repository containing the CloudStack packages as "
+"outlined in the Installation Guide."
+msgstr ""
+
+# 5278fa99d8d4485fb30e42c9411a12f2
+#: ../../source/rnotes.rst:2140
+msgid "``# service cloud-agent stop``"
+msgstr ""
+
+# 3c3fe8b7b19e44cba7a79327a4a72112
+#: ../../source/rnotes.rst:2144
+msgid ""
+"Update the agent software with one of the following command sets as "
+"appropriate for your environment."
+msgstr ""
+
+# f03c00458dfd4309b653b7dd9267b42f
+#: ../../source/rnotes.rst:2147
+msgid "``# yum update cloud-*``"
+msgstr ""
+
+# 3675fb43e8734dd49422ab4b442080b1
+#: ../../source/rnotes.rst:2149
+msgid "``# apt-get update``"
+msgstr ""
+
+# c2bd6eec94fd4fd9ad4aab9c609893cc
+#: ../../source/rnotes.rst:2151
+msgid "``# apt-get upgrade cloud-*``"
+msgstr ""
+
+# c0c4fb3a314d4413b307c50a48ae1228
+#: ../../source/rnotes.rst:2155
+msgid ""
+"Edit ``/etc/cloudstack/agent/agent.properties`` to change the resource "
+"parameter from "
+"\"com.cloud.agent.resource.computing.LibvirtComputingResource\" to "
+"\"com.cloud.hypervisor.kvm.resource.LibvirtComputingResource\"."
+msgstr ""
+
+# 83835a68fb204ae89d6b2f7a6ee8aee8
+# b0e1a8285a0147c98f7193cb947e882f
+#: ../../source/rnotes.rst:2162 ../../source/rnotes.rst:3084
+msgid ""
+"Upgrade all the existing bridge names to new bridge names by running this "
+"script:"
+msgstr ""
+
+# d8fdc08185fc413c805ee17b4372bb1f
+# 56421fb2994141eda8d7a9bc86903b3d
+#: ../../source/rnotes.rst:2171 ../../source/rnotes.rst:3093
+msgid "Install a libvirt hook with the following commands:"
+msgstr ""
+
+# 6c0677df0917467dbf0927ad53c70859
+# 14f18389b7ad431cad97054748e80d01
+#: ../../source/rnotes.rst:2181 ../../source/rnotes.rst:3103
+msgid "Restart libvirtd."
+msgstr ""
+
+# 59e801d0ff0e42e9b908096e9b5a2062
+# 3bb319ee2e3f43719b09beb5f4d34eaa
+#: ../../source/rnotes.rst:2197 ../../source/rnotes.rst:3119
+msgid ""
+"When the Management Server is up and running, log in to the CloudStack UI "
+"and restart the virtual router for proper functioning of all the features."
+msgstr ""
+
+# 20f728fcbbd9438086424d593e216d79
+#: ../../source/rnotes.rst:2203
+msgid ""
+"Log in to the CloudStack UI as administrator, and check the status of the "
+"hosts. All hosts should come to Up state (except those that you know to be "
+"offline). You may need to wait 20 or 30 minutes, depending on the number of "
+"hosts."
+msgstr ""
+
+# 241d2aa9891f408790433893448b144f
+#: ../../source/rnotes.rst:2208
+msgid ""
+"Troubleshooting: If login fails, clear your browser cache and reload the "
+"page."
+msgstr ""
+
+# 43b500c7cce54508bdaeb5e51fc1a33b
+#: ../../source/rnotes.rst:2210
+msgid "Do not proceed to the next step until the hosts show in Up state."
+msgstr ""
+
+# cfa256927ea946a88f88826d49bfa779
+#: ../../source/rnotes.rst:2214
+msgid "If you are upgrading from 3.0.x, perform the following:"
+msgstr ""
+
+# 5124cdeeb6af42268826554aa614f454
+#: ../../source/rnotes.rst:2218
+msgid ""
+"Ensure that the admin port is set to 8096 by using the "
+"\"integration.api.port\" global parameter."
+msgstr ""
+
+# 0411036b58574b94ab1ed659570c295c
+#: ../../source/rnotes.rst:2221
+msgid ""
+"This port is used by the cloud-sysvmadm script at the end of the upgrade "
+"procedure. For information about how to set this parameter, see \"Setting "
+"Global Configuration Parameters\" in the Installation Guide."
+msgstr ""
+
+# 176d29df7a7c40b7bc206569b6219a6a
+#: ../../source/rnotes.rst:2228
+msgid "Restart the Management Server."
+msgstr ""
+
+# 5566efe7e7024e038d8e10e4668e527d
+#: ../../source/rnotes.rst:2230
+msgid ""
+"If you don't want the admin port to remain open, you can set it to null "
+"after the upgrade is done and restart the management server."
+msgstr ""
+
+# b12a8c95a4684dc980a18b97519d555b
+#: ../../source/rnotes.rst:2234
+msgid ""
+"Run the ``cloudstack-sysvmadm`` script to stop, then start, all Secondary "
+"Storage VMs, Console Proxy VMs, and virtual routers. Run the script once on "
+"each management server. Substitute your own IP address of the MySQL "
+"instance, the MySQL user to connect as, and the password to use for that "
+"user. In addition to those parameters, provide the ``-c`` and ``-r`` "
+"arguments. For example:"
+msgstr ""
+
+# f3a9c0911690431ba39dd6d5d29cbcb5
+#: ../../source/rnotes.rst:2241
+msgid ""
+"``# nohup cloudstack-sysvmadm -d 192.168.1.5 -u cloud -p password -c -r > "
+"sysvm.log 2>&1 &``"
+msgstr ""
+
+# 5cdd5748449243d6b6854c3569b11961
+#: ../../source/rnotes.rst:2243
+msgid "``# tail -f sysvm.log``"
+msgstr ""
+
+# c6c35f1a472746a5b280f5243f7ca483
+# ea4304f6924c4fb8ae65904191b11ad4
+#: ../../source/rnotes.rst:2245 ../../source/rnotes.rst:3150
+msgid ""
+"This might take up to an hour or more to run, depending on the number of "
+"accounts in the system."
+msgstr ""
+
+# 4bbd312624104a61ae9c776827d49ed6
+#: ../../source/rnotes.rst:2250
+msgid ""
+"If needed, upgrade all Citrix XenServer hypervisor hosts in your cloud to a "
+"version supported by CloudStack 4.3. The supported versions are XenServer "
+"5.6 SP2 and 6.0.2. Instructions for upgrade can be found in the CloudStack "
+"4.3 Installation Guide under \"Upgrading XenServer Versions.\""
+msgstr ""
+
+# 61e3d7fc35a64e39a1c0126e30aa9f36
+#: ../../source/rnotes.rst:2258
+msgid ""
+"Now apply the XenServer hotfix XS602E003 (and any other needed hotfixes) to "
+"XenServer v6.0.2 hypervisor hosts."
+msgstr ""
+
+# 2b43c0fdef414981a2c74e337540748d
+# 66ecdcd2c3d347329b52cbc5d9c18143
+#: ../../source/rnotes.rst:2263 ../../source/rnotes.rst:3236
+msgid "Disconnect the XenServer cluster from CloudStack."
+msgstr ""
+
+# b4f42bd432054b93a4e458abeb8be1b3
+# 9fbe25aec0cb4dd6b085da9b2db82f2b
+#: ../../source/rnotes.rst:2265 ../../source/rnotes.rst:3238
+msgid ""
+"In the left navigation bar of the CloudStack UI, select Infrastructure. "
+"Under Clusters, click View All. Select the XenServer cluster and click "
+"Actions - Unmanage."
+msgstr ""
+
+# 0a388b8fae49416e8c12288175689189
+# 8d4ecaddee81413aaa9ac9fb0eef3260
+#: ../../source/rnotes.rst:2269 ../../source/rnotes.rst:3242
+msgid ""
+"This may fail if there are hosts not in one of the states Up, Down, "
+"Disconnected, or Alert. You may need to fix that before unmanaging this "
+"cluster."
+msgstr ""
+
+# be4bab92baa048a1a64dbcaf3979f1b8
+# b5e3cd4c03914aceb35590d6b2c02390
+#: ../../source/rnotes.rst:2273 ../../source/rnotes.rst:3246
+msgid ""
+"Wait until the status of the cluster has reached Unmanaged. Use the "
+"CloudStack UI to check on the status. When the cluster is in the unmanaged "
+"state, there is no connection to the hosts in the cluster."
+msgstr ""
+
+# 701d735a313646168e9258e68406bd59
+# 3852ebac77a44424a5d3d220ab53ad7f
+#: ../../source/rnotes.rst:2280 ../../source/rnotes.rst:3253
+msgid "To clean up the VLAN, log in to one XenServer host and run:"
+msgstr ""
+
+# 7aef1179327b48fb9d239fb9abb53494
+#: ../../source/rnotes.rst:2282
+msgid "``/opt/xensource/bin/cloud-clean-vlan.sh``"
+msgstr ""
+
+# 16a41fb12fb348b2aef8eef44201dc09
+#: ../../source/rnotes.rst:2286
+msgid ""
+"Now prepare the upgrade by running the following on one XenServer host:"
+msgstr ""
+
+# 2e5c5805788d4619be1bd88edd6d0f8b
+#: ../../source/rnotes.rst:2289
+msgid "``/opt/xensource/bin/cloud-prepare-upgrade.sh``"
+msgstr ""
+
+# f9486dd60039428eb666ccb36df33df2
+#: ../../source/rnotes.rst:2291
+msgid ""
+"If you see a message like \"can't eject CD\", log in to the VM and unmount "
+"the CD, then run this script again."
+msgstr ""
+
+# 1b90ef07720649ef8be857a6b8613995
+#: ../../source/rnotes.rst:2296
+msgid ""
+"Upload the hotfix to the XenServer hosts. Always start with the Xen pool "
+"master, then the slaves. Using your favorite file copy utility (e.g. "
+"WinSCP), copy the hotfixes to the host. Place them in a temporary folder "
+"such as /tmp."
+msgstr ""
+
+# 95579949c0c0468f9fb5a886c0de0067
+# b9c190b4fd614d0596e6cf2a21762978
+#: ../../source/rnotes.rst:2301 ../../source/rnotes.rst:3278
+msgid "On the Xen pool master, upload the hotfix with this command:"
+msgstr ""
+
+# 79193bd7beb24dad8e02baea8f8fc9e1
+#: ../../source/rnotes.rst:2303
+msgid "``xe patch-upload file-name=XS602E003.xsupdate``"
+msgstr ""
+
+# cd7814430ea74a93a70c8f47170bd22d
+# b14b4d4a191a482bb52ea5f049bceac4
+#: ../../source/rnotes.rst:2305 ../../source/rnotes.rst:3284
+msgid ""
+"Make a note of the output from this command, which is a UUID for the hotfix "
+"file. You'll need it in another step later."
+msgstr ""
+
+# eebe6b8f5f8a4a0c8070cb916408f131
+# d73f4217d05a41aeae87769a8d70aaf7
+#: ../../source/rnotes.rst:2308 ../../source/rnotes.rst:3287
+msgid ""
+"(Optional) If you are applying other hotfixes as well, you can repeat the "
+"commands in this section with the appropriate hotfix number. For example, "
+"XS602E004.xsupdate."
+msgstr ""
+
+# 2463a45ebed644d98aa875979171a856
+# ea165db83e0543f3bb9bf43ee31f1b1f
+#: ../../source/rnotes.rst:2312 ../../source/rnotes.rst:3291
+msgid ""
+"Manually live migrate all VMs on this host to another host. First, get a "
+"list of the VMs on this host:"
+msgstr ""
+
+# 097871715cba4ed3a1430cfd45bf432e
+#: ../../source/rnotes.rst:2315
+msgid "``# xe vm-list``"
+msgstr ""
+
+# 91a6615ab8044e81816572579377c718
+# 2fecd03a5f7c4b69ad918cffe23ee336
+#: ../../source/rnotes.rst:2317 ../../source/rnotes.rst:3298
+msgid ""
+"Then use this command to migrate each VM. Replace the example host name and "
+"VM name with your own:"
+msgstr ""
+
+# ed5ae637635a478da7def0f58b94eb48
+#: ../../source/rnotes.rst:2320
+msgid "``# xe vm-migrate live=true host=host-name`` vm=\\ *``VM-name``*"
+msgstr ""
+
+# cdcae2f3667941289d57e72fed7dfa95
+# 1204a1f920a54d19951f8fc3b0ca2d3f
+#: ../../source/rnotes.rst:2322 ../../source/rnotes.rst:3305
+msgid ""
+"**Troubleshooting:** If you see a message like \"You attempted an operation "
+"on a VM which requires PV drivers to be installed but the drivers were not "
+"detected,\" run: ``/opt/xensource/bin/make_migratable.sh b6cf79c8-02ee-050b-"
+"922f-49583d9f1a14``."
+msgstr ""
+
+# 3de97a19518c446c9c3c24206b1891f4
+# dc7e8ff7538740fd8931578db081c519
+#: ../../source/rnotes.rst:2326 ../../source/rnotes.rst:3309
+msgid "Apply the hotfix. First, get the UUID of this host:"
+msgstr ""
+
+# 438b1e95684647569c3783ca16ce0605
+# 6a54b573120547b9b5079d7edb53f67d
+#: ../../source/rnotes.rst:2332 ../../source/rnotes.rst:3313
+msgid ""
+"Then use the following command to apply the hotfix. Replace the example host"
+" UUID with the current host ID, and replace the hotfix UUID with the output "
+"from the patch-upload command you ran on this machine earlier. You can also "
+"get the hotfix UUID by running xe patch-list."
+msgstr ""
+
+# c8ec6b43de33435d85c0053b0105b112
+# 4637156a9b74469299c17305a87ac225
+#: ../../source/rnotes.rst:2344 ../../source/rnotes.rst:3323
+msgid ""
+"Copy the following files from the CloudStack Management Server to the host."
+msgstr ""
+
+# 8bab7909084144539d7f3f0d96f5410d
+# f0830d516fe8489a8e14f4cc87d3bd0b
+#: ../../source/rnotes.rst:2349 ../../source/rnotes.rst:3327
+msgid "Copy from here..."
+msgstr ""
+
+# d661c3f6488e4437bcad12807e868ba6
+# c65616039e844df49a2c66a9e72fab4d
+#: ../../source/rnotes.rst:2349 ../../source/rnotes.rst:3327
+msgid "...to here"
+msgstr ""
+
+# 5d2066c046d54230a20ba472410c9cca
+#: ../../source/rnotes.rst:2351
+msgid ""
+"/usr/lib64/cloud/common /scripts/vm/hypervisor/ xenserver/xenserver60/N "
+"FSSR.py"
+msgstr ""
+
+# 1782bbb0a4484bfda837b67ed08637f5
+#: ../../source/rnotes.rst:2351
+msgid "/opt/xensource/sm/NFSSR.py"
+msgstr ""
+
+# 9083b6c4d0a84550b56d29048de163fd
+#: ../../source/rnotes.rst:2356
+msgid ""
+"/usr/lib64/cloud/common /scripts/vm/hypervisor/ xenserver/setupxenserve r.sh"
+msgstr ""
+
+# cc60a777fdb84763928959eac1413256
+#: ../../source/rnotes.rst:2356
+msgid "/opt/xensource/bin/setupxenserver.sh"
+msgstr ""
+
+# 7f602a64a7384f1faeeb3cd3cb6906c8
+#: ../../source/rnotes.rst:2361
+msgid ""
+"/usr/lib64/cloud/common /scripts/vm/hypervisor/ xenserver/make\\_migrata "
+"ble.sh"
+msgstr ""
+
+# fd8304dd4b4745048ca492d792e96336
+#: ../../source/rnotes.rst:2361
+msgid "/opt/xensource/bin/make\\_migratable.sh"
+msgstr ""
+
+# 1189f098e11e4821b8dd6002d4701b37
+# 0b20faf71a1d4b488f695e1121d2fce8
+#: ../../source/rnotes.rst:2370 ../../source/rnotes.rst:3347
+msgid ""
+"(Only for hotfixes XS602E005 and XS602E007) You need to apply a new Cloud "
+"Support Pack."
+msgstr ""
+
+# 51314060eb4e4274a94556cf66d7b8f5
+# 6f0e38b936c146a88f18f01bd79fb137
+#: ../../source/rnotes.rst:2375 ../../source/rnotes.rst:3352
+msgid ""
+"Download the CSP software onto the XenServer host from one of the following "
+"links:"
+msgstr ""
+
+# 7960ce9d01764dca84c420221f5ac947
+# 2b5b6fb5241d45ca94ee8aee0c067700
+#: ../../source/rnotes.rst:2378 ../../source/rnotes.rst:3355
+msgid ""
+"For hotfix XS602E005: "
+"`http://coltrane.eng.hq.xensource.com/release/XenServer-6.x/XS-6.0.2/hotfixes/XS602E005/56710"
+"/xe-phase-2/xenserver-cloud-supp.tgz "
+"<http://coltrane.eng.hq.xensource.com/release/XenServer-6.x/XS-6.0.2/hotfixes/XS602E005/56710"
+"/xe-phase-2/xenserver-cloud-supp.tgz>`__"
+msgstr ""
+
+# 93f404dfecb845f7a295abed79cd2bdc
+# 1e9987f14ee140caab3cd9ac80fb3d70
+#: ../../source/rnotes.rst:2381 ../../source/rnotes.rst:3358
+msgid ""
+"For hotfix XS602E007: "
+"`http://coltrane.eng.hq.xensource.com/release/XenServer-6.x/XS-6.0.2/hotfixes/XS602E007/57824"
+"/xe-phase-2/xenserver-cloud-supp.tgz "
+"<http://coltrane.eng.hq.xensource.com/release/XenServer-6.x/XS-6.0.2/hotfixes/XS602E007/57824"
+"/xe-phase-2/xenserver-cloud-supp.tgz>`__"
+msgstr ""
+
+# 5487658881254252bc032a418bc9d211
+# d5d3595872834a30b69f2a97f934a6b6
+#: ../../source/rnotes.rst:2386 ../../source/rnotes.rst:3363
+msgid "Extract the file:"
+msgstr ""
+
+# 10aadbef588b4906aa4411610fff2b38
+# 41fba79ec98c4ba9bb33a5ece8089e84
+#: ../../source/rnotes.rst:2394 ../../source/rnotes.rst:3369
+msgid "Run the following script:"
+msgstr ""
+
+# 304c43ec19654d4facc909cee84b878e
+# 6f36c01dad0c4038b06f62939ceb97c4
+#: ../../source/rnotes.rst:2402 ../../source/rnotes.rst:3375
+msgid ""
+"If the XenServer host is part of a zone that uses basic networking, disable "
+"Open vSwitch (OVS):"
+msgstr ""
+
+# 196938b763f24a729f0d5fc34034cf8d
+# 97f83d0655ca49899c2f7b23cf07100d
+#: ../../source/rnotes.rst:2411 ../../source/rnotes.rst:3382
+msgid "Reboot this XenServer host."
+msgstr ""
+
+# 2b44592533884e89a228bd0a5f8e8a24
+# c82ea223be1d4b64adaed5f89d77845f
+# ba507e290ab84df6bee757006448475b
+# 723c48dca8094e9da7624f83d2ac56c7
+#: ../../source/rnotes.rst:2415 ../../source/rnotes.rst:2425
+#: ../../source/rnotes.rst:3386 ../../source/rnotes.rst:3394
+msgid "Run the following:"
+msgstr ""
+
+# 60d0028a822d4455a2ef0e71a774fc89
+# 3c2b4eb2c1a34738a8fee6a813020cc8
+#: ../../source/rnotes.rst:2421 ../../source/rnotes.rst:3390
+msgid ""
+"If the message \"mv: cannot stat \\`/etc/cron.daily/logrotate': No such file"
+" or directory\" appears, you can safely ignore it."
+msgstr ""
+
+# e365729bdd0a43d98ca4aa6df76a080a
+# 292dce1c5566443db1f36434502cbe40
+#: ../../source/rnotes.rst:2433 ../../source/rnotes.rst:3402
+msgid ""
+"On each slave host in the Xen pool, repeat these steps, starting from "
+"\"manually live migrate VMs.\""
+msgstr ""
+
+# 53aa4ba520af4d32a111c7bdd061c7f6
+#: ../../source/rnotes.rst:2436
+msgid ""
+"**Troubleshooting Tip:** If passwords which you know to be valid appear not "
+"to work after upgrade, or other UI issues are seen, try clearing your "
+"browser cache and reloading the UI page."
+msgstr ""
+
+# 82f67a0f08f74ea0b372cfc3d9798cff
+#: ../../source/rnotes.rst:2439
+msgid "Upgrade from 2.2.14 to 4.3"
+msgstr ""
+
+# 8dd5152530dc4c448bc7ca2147bb3f58
+#: ../../source/rnotes.rst:2443
+msgid ""
+"Ensure that you query your IPaddress usage records and process them; for "
+"example, issue invoices for any usage that you have not yet billed users "
+"for."
+msgstr ""
+
+# 08a3e11c4ac84d15a5539ea1a29e5540
+#: ../../source/rnotes.rst:2447
+msgid ""
+"Starting in 3.0.2, the usage record format for IP addresses is the same as "
+"the rest of the usage types. Instead of a single record with the assignment "
+"and release dates, separate records are generated per aggregation period "
+"with start and end dates. After upgrading to 4.3, any existing IP address "
+"usage records in the old format will no longer be available."
+msgstr ""
+
+# 82d3912ade2e4425b10822ef75644184
+#: ../../source/rnotes.rst:2456
+msgid ""
+"If you are using version 2.2.0 - 2.2.13, first upgrade to 2.2.14 by using "
+"the instructions in the `2.2.14 Release Notes "
+"<http://download.cloud.com/releases/2.2.0/CloudStack2.2.14ReleaseNotes.pdf>`__."
+msgstr ""
+
+# 43af6a2f821148dc933817dda7004642
+#: ../../source/rnotes.rst:2460
+msgid ""
+"**KVM Hosts:** If KVM hypervisor is used in your cloud, be sure you "
+"completed the step to insert a valid username and password into the "
+"host\\_details table on each KVM node as described in the 2.2.14 Release "
+"Notes. This step is critical, as the database will be encrypted after the "
+"upgrade to 4.3."
+msgstr ""
+
+# 165a6cb6d6d14af88d88b0b78f71157f
+#: ../../source/rnotes.rst:2464
+msgid ""
+"While running the 2.2.14 system, log in to the UI as root administrator."
+msgstr ""
+
+# 1f8e9d1a6daa49ee9369d371b139cfd1
+#: ../../source/rnotes.rst:2469
+msgid ""
+"Using the UI, add a new System VM template for each hypervisor type that is "
+"used in your cloud. In each zone, add a system VM template for each "
+"hypervisor used in that zone"
+msgstr ""
+
+# 61df5a92c7374826b61d112059dfcf30
+#: ../../source/rnotes.rst:2489
+msgid ""
+"In the Register template dialog box, specify the following values depending "
+"on the hypervisor type (do not change these):"
+msgstr ""
+
+# cf7180ae32be4c09baac3d08c8d8592f
+#: ../../source/rnotes.rst:2575
+msgid ""
+"Watch the screen to be sure that the template downloads successfully and "
+"enters the READY state. Do not proceed until this is successful"
+msgstr ""
+
+# abd7c11dce0748e393edeabe2b1a3c88
+#: ../../source/rnotes.rst:2580
+msgid ""
+"**WARNING**: If you use more than one type of hypervisor in your cloud, be "
+"sure you have repeated these steps to download the system VM template for "
+"each hypervisor type. Otherwise, the upgrade will fail."
+msgstr ""
+
+# 944b4efebb274b4b9168b8c9bc07cd2d
+#: ../../source/rnotes.rst:2677
+msgid ""
+"If you are using Ubuntu, follow this procedure to upgrade your packages. If "
+"not, skip to step `13 <#upgrade-rpm-packages-22>`__."
+msgstr ""
+
+# 5621f0bde6ef435598eb9f26e3dad529
+#: ../../source/rnotes.rst:2727
+msgid ""
+"On KVM hosts, you will need to manually install the ``cloudstack-agent`` "
+"package:"
+msgstr ""
+
+# 203132db7f3948499d31bb3eb0057291
+#: ../../source/rnotes.rst:2789
+msgid ""
+"If you are using CentOS or RHEL, follow this procedure to upgrade your "
+"packages. If not, skip to step `14 <#correct-components-xml-22>`__."
+msgstr ""
+
+# 690f899c6bd24183860a840ddf554d44
+#: ../../source/rnotes.rst:2871
+msgid ""
+"If you have made changes to your existing copy of the file components.xml in"
+" your previous-version CloudStack installation, the changes will be "
+"preserved in the upgrade. However, you need to do the following steps to "
+"place these changes in a new version of the file which is compatible with "
+"version 4.0.0-incubating."
+msgstr ""
+
+# b2fef2e295cf40a6b3777a62e5e8dd89
+#: ../../source/rnotes.rst:2877
+msgid ""
+"How will you know whether you need to do this? If the upgrade output in the "
+"previous step included a message like the following, then some custom "
+"content was found in your old components.xml, and you need to merge the two "
+"files:"
+msgstr ""
+
+# 28092dbc6a1e4c8b8b40af19e0361a7a
+#: ../../source/rnotes.rst:2886
+msgid ""
+"Make a backup copy of your ``/etc/cloud/management/components.xml`` file. "
+"For example:"
+msgstr ""
+
+# ce76e70e3d0d4085b429224f3c46f5f0
+#: ../../source/rnotes.rst:2904
+msgid ""
+"Merge your changes from the backup file into the new components.xml file."
+msgstr ""
+
+# 5d31708084ea431cb32c6de017984b9d
+#: ../../source/rnotes.rst:2913
+msgid ""
+"After upgrading to 4.3, API clients are expected to send plain text "
+"passwords for login and user creation, instead of MD5 hash. If API client "
+"changes are not acceptable, following changes are to be made for backward "
+"compatibility:"
+msgstr ""
+
+# 3e13a458fcec46348d78d6a05c0a73f2
+#: ../../source/rnotes.rst:2936
+msgid ""
+"PlainTextUserAuthenticator works the same way MD5UserAuthenticator worked "
+"prior to 4.2."
+msgstr ""
+
+# 977e0462a4514e8290c4f6efb24ffbc6
+#: ../../source/rnotes.rst:2941
+msgid ""
+"If you have made changes to your existing copy of the "
+"``/etc/cloud/management/db.properties`` file in your previous-version "
+"CloudStack installation, the changes will be preserved in the upgrade. "
+"However, you need to do the following steps to place these changes in a new "
+"version of the file which is compatible with this version."
+msgstr ""
+
+# 6f3fecf7bee440819bd35439052e7134
+#: ../../source/rnotes.rst:2950
+msgid ""
+"Make a backup copy of your file ``/etc/cloud/management/db.properties``. For"
+" example:"
+msgstr ""
+
+# 1e4702a05d304ef4a3d18a310670413b
+#: ../../source/rnotes.rst:2959
+msgid ""
+"Copy ``/etc/cloud/management/db.properties.rpmnew`` to create a new "
+"``/etc/cloud/management/db.properties``:"
+msgstr ""
+
+# 2a689fd4c8b34f159bbccda75eea3b44
+#: ../../source/rnotes.rst:2968
+msgid ""
+"Merge your changes from the backup file into the new db.properties file."
+msgstr ""
+
+# 14c9f00e13384fe7818635db57ddebbe
+#: ../../source/rnotes.rst:2977
+msgid ""
+"On the management server node, run the following command. It is recommended "
+"that you use the command-line flags to provide your own encryption keys. See"
+" Password and Key Encryption in the Installation Guide."
+msgstr ""
+
+# 3f168b18c27443dd875c5adeb55a85a0
+#: ../../source/rnotes.rst:2986
+msgid ""
+"When used without arguments, as in the following example, the default "
+"encryption type and keys will be used:"
+msgstr ""
+
+# 33bee02a88e14c6f8726562c1066932f
+#: ../../source/rnotes.rst:2991
+msgid ""
+"(Optional) For encryption\\_type, use file or web to indicate the technique "
+"used to pass in the database encryption password. Default: file."
+msgstr ""
+
+# da3a05583c554e95a25b01ea4b2fab78
+#: ../../source/rnotes.rst:2997
+msgid ""
+"(Optional) For management\\_server\\_key, substitute the default key that is"
+" used to encrypt confidential parameters in the properties file. Default: "
+"password. It is highly recommended that you replace this with a more secure "
+"value"
+msgstr ""
+
+# d47187c0a6934275b49e5f7142bf2a49
+#: ../../source/rnotes.rst:3004
+msgid ""
+"(Optional) For database\\_key, substitute the default key that is used to "
+"encrypt confidential parameters in the CloudStack database. Default: "
+"password. It is highly recommended that you replace this with a more secure "
+"value."
+msgstr ""
+
+# a1b1f1666d0e4e5fa004939d7cb65ebb
+#: ../../source/rnotes.rst:3011
+msgid ""
+"Repeat steps 10 - 14 on every management server node. If you provided your "
+"own encryption key in step 14, use the same key on all other management "
+"servers."
+msgstr ""
+
+# d2b6a61b4d4c4ea4ac31966205b494e9
+#: ../../source/rnotes.rst:3024
+msgid ""
+"Wait until the databases are upgraded. Ensure that the database upgrade is "
+"complete. You should see a message like \"Complete! Done.\" After "
+"confirmation, start the other Management Servers one at a time by running "
+"the same command on each node."
+msgstr ""
+
+# d3aa8aeaac984b868f7bb6203777068c
+#: ../../source/rnotes.rst:3040
+msgid "(KVM only) Perform the following additional steps on each KVM host."
+msgstr ""
+
+# 7f58ac6f2a6546e984b291d14708aecd
+#: ../../source/rnotes.rst:3042
+msgid ""
+"These steps will not affect running guests in the cloud. These steps are "
+"required only for clouds using KVM as hosts and only on the KVM hosts."
+msgstr ""
+
+# a40f34aedd354e19b622dba6af947dc9
+#: ../../source/rnotes.rst:3048
+msgid ""
+"Configure your CloudStack package repositories as outlined in the "
+"Installation Guide"
+msgstr ""
+
+# 60b6f718e10b44b2932fe47305402e68
+#: ../../source/rnotes.rst:3061
+msgid ""
+"Update the agent software with one of the following command sets as "
+"appropriate."
+msgstr ""
+
+# d1c9b23bfd3047b3af0434ee9d2f4b81
+#: ../../source/rnotes.rst:3075
+msgid ""
+"Copy the contents of the ``agent.properties`` file to the new "
+"``agent.properties`` file by using the following command"
+msgstr ""
+
+# f29b1de1f5784d40a03f632bee5da0c8
+#: ../../source/rnotes.rst:3125
+msgid ""
+"Log in to the CloudStack UI as admin, and check the status of the hosts. All"
+" hosts should come to Up state (except those that you know to be offline). "
+"You may need to wait 20 or 30 minutes, depending on the number of hosts."
+msgstr ""
+
+# 5d312c8c705f4c878ea150dab52c575d
+#: ../../source/rnotes.rst:3130
+msgid ""
+"Do not proceed to the next step until the hosts show in the Up state. If the"
+" hosts do not come to the Up state, contact support."
+msgstr ""
+
+# 25837b241e564dd7a200dc22ed3e929b
+#: ../../source/rnotes.rst:3135
+msgid ""
+"Run the following script to stop, then start, all Secondary Storage VMs, "
+"Console Proxy VMs, and virtual routers."
+msgstr ""
+
+# ac2edfb7c37b4bf994275e773d12c5c4
+#: ../../source/rnotes.rst:3140
+msgid ""
+"Run the command once on one management server. Substitute your own IP "
+"address of the MySQL instance, the MySQL user to connect as, and the "
+"password to use for that user. In addition to those parameters, provide the "
+"\"-c\" and \"-r\" arguments. For example:"
+msgstr ""
+
+# 62fdd3c67b9b4b9cb1c6ecce251c6b5a
+#: ../../source/rnotes.rst:3155
+msgid ""
+"After the script terminates, check the log to verify correct execution:"
+msgstr ""
+
+# 47faf7f70b334ae98f3f1c7a670a311f
+#: ../../source/rnotes.rst:3162
+msgid "The content should be like the following:"
+msgstr ""
+
+# cf26992fc5ea49f8a46b7c97db3db2db
+#: ../../source/rnotes.rst:3175
+msgid ""
+"If you would like additional confirmation that the new system VM templates "
+"were correctly applied when these system VMs were rebooted, SSH into the "
+"System VM and check the version."
+msgstr ""
+
+# d907b5857e874ddb9e2685400bdaa324
+#: ../../source/rnotes.rst:3179
+msgid "Use one of the following techniques, depending on the hypervisor."
+msgstr ""
+
+# 47eeb152f7354386a945820cf565dd7d
+#: ../../source/rnotes.rst:3181
+msgid "**XenServer or KVM:**"
+msgstr ""
+
+# 4845c8f916aa46c8b0afb4d65839827a
+#: ../../source/rnotes.rst:3183
+msgid ""
+"SSH in by using the link local IP address of the system VM. For example, in "
+"the command below, substitute your own path to the private key used to log "
+"in to the system VM and your own link local IP."
+msgstr ""
+
+# fd4e4c86a1e44bb184899f9b2f2a2215
+#: ../../source/rnotes.rst:3188
+msgid ""
+"Run the following commands on the XenServer or KVM host on which the system "
+"VM is present:"
+msgstr ""
+
+# 9fb15734392e492db8eec3bfd8db8456
+# 3d3c3fffab7445d18c30fce3880b7b1c
+#: ../../source/rnotes.rst:3196 ../../source/rnotes.rst:3215
+msgid "The output should be like the following:"
+msgstr ""
+
+# 6c25de5d57584107bb52f4b83298476e
+#: ../../source/rnotes.rst:3202
+msgid "**ESXi:**"
+msgstr ""
+
+# 1c5098a14ab44e28bbc70f3c2c27f1b8
+#: ../../source/rnotes.rst:3204
+msgid ""
+"SSH in using the private IP address of the system VM. For example, in the "
+"command below, substitute your own path to the private key used to log in to"
+" the system VM and your own private IP."
+msgstr ""
+
+# 1ea48fa0ab9a49cd99f56b64aeeff8cf
+#: ../../source/rnotes.rst:3208
+msgid "Run the following commands on the Management Server:"
+msgstr ""
+
+# 2de578dee3164dc9b979d4322ff158fe
+#: ../../source/rnotes.rst:3223
+msgid ""
+"If needed, upgrade all Citrix XenServer hypervisor hosts in your cloud to a "
+"version supported by CloudStack 4.0.0-incubating. The supported versions are"
+" XenServer 5.6 SP2 and 6.0.2. Instructions for upgrade can be found in the "
+"CloudStack 4.0.0-incubating Installation Guide."
+msgstr ""
+
+# 78d0d9395c604a4c805ddfec475f15bb
+#: ../../source/rnotes.rst:3231
+msgid ""
+"Apply the XenServer hotfix XS602E003 (and any other needed hotfixes) to "
+"XenServer v6.0.2 hypervisor hosts."
+msgstr ""
+
+# aaa65cee9a6f430bac41e5738591839d
+#: ../../source/rnotes.rst:3261
+msgid "Prepare the upgrade by running the following on one XenServer host:"
+msgstr ""
+
+# 7d50c3d8799447ff89c8c364eb70731d
+#: ../../source/rnotes.rst:3268
+msgid ""
+"If you see a message like \"can't eject CD\", log in to the VM and umount "
+"the CD, then run this script again."
+msgstr ""
+
+# 933303f89e9f4fdbb4693a289c7f28cb
+#: ../../source/rnotes.rst:3273
+msgid ""
+"Upload the hotfix to the XenServer hosts. Always start with the Xen pool "
+"master, then the slaves. Using your favorite file copy utility (e.g. "
+"WinSCP), copy the hotfixes to the host. Place them in a temporary folder "
+"such as /root or /tmp."
+msgstr ""
+
+# be996cb933684ad28c8d1a0fc11b51f3
+#: ../../source/rnotes.rst:3311
+msgid "``# xe host-list``"
+msgstr ""
+
+# 8b48b679d3034863a0cf33f4243733e0
+#: ../../source/rnotes.rst:3319
+msgid "``xe patch-apply host-uuid=host-uuid`` uuid=\\ *``hotfix-uuid``*"
+msgstr ""
+
+# fba81dae9aa141759a651c9681d452ca
+#: ../../source/rnotes.rst:3329
+msgid ""
+"``/usr/share/cloudstack -common/scripts/vm/hype rvisor/xenserver/xenser "
+"ver60/NFSSR.py``"
+msgstr ""
+
+# f17727fee8de4422b1854899f586b480
+#: ../../source/rnotes.rst:3329
+msgid "``/opt/xensource/sm/NFSSR.py``"
+msgstr ""
+
+# 8b641d51a32547f6bacbfdf2b6a2bf14
+#: ../../source/rnotes.rst:3334
+msgid ""
+"``/usr/share/cloudstack -common/scripts/vm/hype rvisor/xenserver/setupx "
+"enserver.sh``"
+msgstr ""
+
+# e5244c3c204643cbac950d4ef0a3e6c7
+# 15d387013eea4eb2b0bb7d051beed7ad
+#: ../../source/rnotes.rst:3334 ../../source/rnotes.rst:3388
+msgid "``/opt/xensource/bin/setupxenserver.sh``"
+msgstr ""
+
+# 46501ce5ab894a74ada10967a82596af
+#: ../../source/rnotes.rst:3339
+msgid ""
+"``/usr/lib64/cloudstack -common/scripts/vm/hype rvisor/xenserver/make_m "
+"igratable.sh``"
+msgstr ""
+
+# ae866867817d4b3aa8dee6324cad801d
+#: ../../source/rnotes.rst:3339
+msgid "``/opt/xensource/bin/make_migratable.sh``"
+msgstr ""
+
+# d1c878ddd25d437b89be1fe7935981a0
+#: ../../source/rnotes.rst:3365
+msgid "``# tar xf xenserver-cloud-supp.tgz``"
+msgstr ""
+
+# be55bf39cd3b47ae95be10e364d38068
+#: ../../source/rnotes.rst:3371
+msgid "``# xe-install-supplemental-pack xenserver-cloud-supp.iso``"
+msgstr ""
+
+# 511effdc9d26448290f575384afe0676
+#: ../../source/rnotes.rst:3378
+msgid "``# xe-switch-network-backend bridge``"
+msgstr ""
diff --git a/source/releasenotes/locale/pot/.doctrees/about.doctree b/source/releasenotes/locale/pot/.doctrees/about.doctree
new file mode 100644
index 0000000..3d92a96
--- /dev/null
+++ b/source/releasenotes/locale/pot/.doctrees/about.doctree
Binary files differ
diff --git a/source/releasenotes/locale/pot/.doctrees/api-changes.doctree b/source/releasenotes/locale/pot/.doctrees/api-changes.doctree
new file mode 100644
index 0000000..07a5469
--- /dev/null
+++ b/source/releasenotes/locale/pot/.doctrees/api-changes.doctree
Binary files differ
diff --git a/source/releasenotes/locale/pot/.doctrees/compat.doctree b/source/releasenotes/locale/pot/.doctrees/compat.doctree
new file mode 100644
index 0000000..a567b00
--- /dev/null
+++ b/source/releasenotes/locale/pot/.doctrees/compat.doctree
Binary files differ
diff --git a/source/releasenotes/locale/pot/.doctrees/environment.pickle b/source/releasenotes/locale/pot/.doctrees/environment.pickle
new file mode 100644
index 0000000..d5e1b2a
--- /dev/null
+++ b/source/releasenotes/locale/pot/.doctrees/environment.pickle
Binary files differ
diff --git a/source/releasenotes/locale/pot/.doctrees/index.doctree b/source/releasenotes/locale/pot/.doctrees/index.doctree
new file mode 100644
index 0000000..0b3e9dd
--- /dev/null
+++ b/source/releasenotes/locale/pot/.doctrees/index.doctree
Binary files differ
diff --git a/source/releasenotes/locale/pot/.doctrees/rnotes.doctree b/source/releasenotes/locale/pot/.doctrees/rnotes.doctree
new file mode 100644
index 0000000..0d6e200
--- /dev/null
+++ b/source/releasenotes/locale/pot/.doctrees/rnotes.doctree
Binary files differ
diff --git a/source/releasenotes/locale/pot/about.pot b/source/releasenotes/locale/pot/about.pot
new file mode 100644
index 0000000..37253ca
--- /dev/null
+++ b/source/releasenotes/locale/pot/about.pot
@@ -0,0 +1,4903 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 10:50-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../about.rst:17
+# bdb91b47a91143f1a9fbaaf76b791a2f
+msgid "About this new Release"
+msgstr ""
+
+#: ../../about.rst:20
+# 09ea19a83f3c45fbb713eecff4f4479a
+msgid "What's New in 4.3"
+msgstr ""
+
+#: ../../about.rst:22
+# a7450e3fb9a743108c319a9af9fe1b80
+msgid "CloudStack 4.3 includes the following new features."
+msgstr ""
+
+#: ../../about.rst:25
+# de565510abed48d8af44eb5fdb96baa6
+msgid "Optional 64-Bit System VM Template Support"
+msgstr ""
+
+#: ../../about.rst:27
+# 048e4ce62ed244bba8e86b18d88f3a34
+msgid "CloudStack now provides 64-bit templates for System VMs. With this support, you will be able to upgrade virtual routers in a zone. The following parameters have been introduced for the same purpose:"
+msgstr ""
+
+#: ../../about.rst:33
+# 3ff7bc12fd3a40168e34b0756ea6a56d
+msgid "XenServer: *``router.template.xen``*"
+msgstr ""
+
+#: ../../about.rst:37
+# 0f83f7b6fbfe4d9d83c9434fe623902f
+msgid "KVM: *``router.template.kvm``*"
+msgstr ""
+
+#: ../../about.rst:41
+# 2f7e453939514853b250feb502b7b5e4
+msgid "VMware:"
+msgstr ""
+
+#: ../../about.rst:45
+# 788a74eec57b416b98f7fe353645942d
+msgid "Hyper-V:"
+msgstr ""
+
+#: ../../about.rst:48
+# bf5c467f2c6942ed83e6d9bd84f1b336
+msgid "Hyper-V Support"
+msgstr ""
+
+#: ../../about.rst:50
+# a68a0a054365438c8cf07088b31c3f67
+msgid "CloudStack 4.3 rolls out support for Hyper-V hosts. For Hyper-V, CloudStack supports SMB-based storage. If you want to run guest VMs on Hyper-V hosts, install CloudStack Agents on each Hyper-V hosts. Before you use Hyper-V, review the following list of supported and non-supported features. For detailed instruction, see Hyper-V Quick Start Guide. You can also see the chapter Installing Hyper-V for CloudStack in the CloudStack 4.3 Installation Guide."
+msgstr ""
+
+#: ../../about.rst:59
+# f42fefd9b0704bbd8914c2fc900378e5
+msgid "Supported Functionalities on Hyper-V"
+msgstr ""
+
+#: ../../about.rst:63
+# 8a08c075dad842ae989d94c62ee4c170
+msgid "VM Compute"
+msgstr ""
+
+#: ../../about.rst:67
+# 4a23fdd07b4545a8a2471b9e7858afb0
+msgid "All the VM operations, except VM Snapshots"
+msgstr ""
+
+#: ../../about.rst:71
+# 0853f620548b45c58c3f661681d49db6
+msgid "Live Migration"
+msgstr ""
+
+#: ../../about.rst:75
+# 7f73d6bfa5414af29f7bd70a2f166f2a
+msgid "Service Offerings (Scale up on stopped VMs)"
+msgstr ""
+
+#: ../../about.rst:79
+# 2901e1e3a3ee4f318bee5841071d11f4
+msgid "Console access"
+msgstr ""
+
+#: ../../about.rst:83
+# e9f0cf1c36e34061a4430368430f8b7e
+msgid "SSH key and reseting SSH key"
+msgstr ""
+
+#: ../../about.rst:87
+# 61f557f1ec2841b3b5b64dded25a56ba
+msgid "Upload and download templates, volumes, and ISO"
+msgstr ""
+
+#: ../../about.rst:91
+# c07f2d55f8364cd8b0050aa4d3d54382
+msgid "Create VMs from template and ISO"
+msgstr ""
+
+#: ../../about.rst:95
+# f9b15aeb193941e79220d19f3dce562e
+msgid "Create template from volume"
+msgstr ""
+
+#: ../../about.rst:99
+# 8ccfe45c544e4c638d9f4a12b6436cd9
+msgid "Attach and detach VMs from ISO and password-enabled template"
+msgstr ""
+
+#: ../../about.rst:103
+# d387c492ad4a4f27ae58eab3f0f892a3
+msgid "Copy template across zone"
+msgstr ""
+
+#: ../../about.rst:107
+# cc1d8aed652142ca8d18086e70eccad4
+msgid "Storage"
+msgstr ""
+
+#: ../../about.rst:111
+# 0991d5f6fea746e1b06907ae0bb63f74
+msgid "Primary Storage (SMB and Local)"
+msgstr ""
+
+#: ../../about.rst:115
+# ebc4eb92938f4a3f9061c8321002678d
+msgid "Root and data volumes on Local and SMB"
+msgstr ""
+
+#: ../../about.rst:119
+# 9c6c606883c340a88101911897eb1ac5
+msgid "Add, delete, attach, detach volumes (one or more volumes per VM)"
+msgstr ""
+
+#: ../../about.rst:123
+# 932392fdf2984fe7a875e41f9de7de60
+msgid "Single and multiple secondary storage (SMB)"
+msgstr ""
+
+#: ../../about.rst:127
+# f7cc1aa8312e47ef9e0b9f2046dc6f12
+msgid "Network"
+msgstr ""
+
+#: ../../about.rst:131
+# b13ad43288b34c5398b4fd4904be20dc
+msgid "VLANs (Isolated and Shared)"
+msgstr ""
+
+#: ../../about.rst:135
+# 874f9b3d2c9e4b4f8fb45f9baee22bfe
+msgid "All VR services: DNS, DHCP, SourceNAT, LB, PF, Firewall, StaticNAT, Userdata, and VPN"
+msgstr ""
+
+#: ../../about.rst:140
+# 09421e4ea4d148e68b8d1e37a762586f
+msgid "External device support for both Isolated and Shared networks: Netscaler, SRX, F5"
+msgstr ""
+
+#: ../../about.rst:145
+# d07e8aa630494fa7938a2cf213bd9991
+msgid "Multiple physical networks"
+msgstr ""
+
+#: ../../about.rst:149
+# d100215a6752462ea07718f52c810c16
+msgid "Dedicated IP range, Public VLANs (to account)"
+msgstr ""
+
+#: ../../about.rst:153
+# 0a27b6bb4a754d9e993d9562c77a4ff7
+msgid "Network Offering upgrades and updates"
+msgstr ""
+
+#: ../../about.rst:157
+# 9c4055c13dcd4ca8926e5a28c1b8ab50
+msgid "L4-L7 services in Shared network"
+msgstr ""
+
+#: ../../about.rst:161
+# aa7a95d118364e49979f5adbcb3b0d39
+msgid "Multiple IP ranges and portable IPs"
+msgstr ""
+
+#: ../../about.rst:165
+# 5669e604b4b64897aa6b5ed794b76f5c
+msgid "Host and Storage in maintenance mode"
+msgstr ""
+
+#: ../../about.rst:168
+# fafdc4c1cbd7484b9f05f44fe7260546
+msgid "Unsupported Functionalities on Hyper-V"
+msgstr ""
+
+#: ../../about.rst:172
+# 9126bf9e82bc45e499dc89df7fc0a0f6
+msgid "Affinity an Anti-Affinity Groups"
+msgstr ""
+
+#: ../../about.rst:176
+# 546d2df63ef44bd590e7adcbb31589d7
+msgid "Network throttling"
+msgstr ""
+
+#: ../../about.rst:180
+# 0f4fe83217294fdfb3c4c04617eadef1
+msgid "Security groups (Advanced Zone)"
+msgstr ""
+
+#: ../../about.rst:184
+# 03d2119aa0234ee693ad12ab0d2d118a
+msgid "IPv6"
+msgstr ""
+
+#: ../../about.rst:188
+# d8f2d2b85d76482995ae6d639cc00f3c
+msgid "Snapshot: VM and disk"
+msgstr ""
+
+#: ../../about.rst:192
+# 52ea53b1bd254148bc10e6d3cca67a40
+msgid "PVLAN"
+msgstr ""
+
+#: ../../about.rst:196
+# 7eea4c2b16d94da0bec010bdd4499b75
+msgid "VPC"
+msgstr ""
+
+#: ../../about.rst:200
+# 0ca54967dd9542c2ad230764eec58cb4
+msgid "HA of guest VMs"
+msgstr ""
+
+#: ../../about.rst:204
+# ebfed36bc2b14ce2aaba7818affa537f
+msgid "Redundant VR"
+msgstr ""
+
+#: ../../about.rst:208
+# 18a3cf7e8d6349fab3e8accbd101ea23
+msgid "Object Store"
+msgstr ""
+
+#: ../../about.rst:212
+# 9ec4ba65baa94d5b8771ce1920e78f4e
+msgid "Mixed hypervisor zone"
+msgstr ""
+
+#: ../../about.rst:216
+# 287a5e396359407d97733e009c86b208
+msgid "Zone-wide Primary storage"
+msgstr ""
+
+#: ../../about.rst:220
+# dbebd6f68c114cc98c2feda96bda8339
+msgid "NIC bonding"
+msgstr ""
+
+#: ../../about.rst:223
+# 1219852e8e6d45d29136897552f0a79e
+msgid "Enhanced Upgrade for Virtual Routers"
+msgstr ""
+
+#: ../../about.rst:225
+# b3c22859d0dd4066b256bbe41f847bc4
+msgid "Upgrading VRs is made flexible. The CloudStack administrators will be able to control the sequence of the VR upgrades. The sequencing is based on Infrastructure hierarchy, such as by Cluster, Pod, or Zone, and Administrative hierarchy, such as by Tenant or Domain. This implies, for example, that you will have the flexibility to upgrade a VR in a specified zone. As an administrator, you can also determine when a particular VR can be upgraded within a specified upgrade interval. Additionally, upgrade operation is enhanced to increase the upgrade speed by allowing as many upgrade operations in parallel as possible. During the entire duration of the upgrade, users cannot launch new services or make changes to an existing service."
+msgstr ""
+
+#: ../../about.rst:237
+# 40bdf0a308c2489bb98e96a62d75e548
+msgid "To support this feature, a new API, upgradeRouterTemplate, has been introduced."
+msgstr ""
+
+#: ../../about.rst:240
+# d37f3bc214424defab5f024e87d6f9e9
+msgid "The detailed instruction is provided in the CloudStack 4.3 Administration Guide. See section 17.5.5. Enhanced Upgrade for Virtual Routers."
+msgstr ""
+
+#: ../../about.rst:244
+# 1978f680828e42a6a20bf3259d22a92e
+msgid "Service Monitoring Tool for Virtual Router"
+msgstr ""
+
+#: ../../about.rst:246
+# a4902af1b3fd4bb0ab166c3d3f9feeb1
+msgid "Various services running on the CloudStack virtual routers can be monitored by using a Service Monitoring tool. The tool ensures that services are successfully running until CloudStack deliberately disables them. If a service goes down, the tool automatically performs a restart, and if that does not help bringing up the service, an alert as well as an event is generated indicating the failure."
+msgstr ""
+
+#: ../../about.rst:253
+# 667326bf4c7f4e58865496ef24d6f564
+msgid "The following services are monitored in a VR:"
+msgstr ""
+
+#: ../../about.rst:257
+# 024d834f741b41bebab0bdcecdf5d5e1
+msgid "DNS"
+msgstr ""
+
+#: ../../about.rst:261
+# ff61c6894d1f44528fb0cfaee5973892
+msgid "HA Proxy"
+msgstr ""
+
+#: ../../about.rst:265
+# 7292e272f40f42efa8b4a31dd617fcc4
+msgid "SSH"
+msgstr ""
+
+#: ../../about.rst:269
+# f8d9969dc6d543c4806e00250dcdc745
+msgid "Apache Web Server"
+msgstr ""
+
+#: ../../about.rst:271
+# 2dcd9edec1a04f5d879c7a2b5356f1df
+msgid "Only the services with daemons are monitored."
+msgstr ""
+
+#: ../../about.rst:273
+# 8e45915127fd4804a98e10f181e8c8c3
+msgid "The following networks are supported:"
+msgstr ""
+
+#: ../../about.rst:277
+# 85dab6977a0742da917c0892ea590cf9
+msgid "Isolated Networks"
+msgstr ""
+
+#: ../../about.rst:281
+# f171266ce0c248d2910f9f10eaab6565
+msgid "Shared Networks in both Advanced and Basic zone"
+msgstr ""
+
+#: ../../about.rst:283
+# c6bc2910647143b29bce7ea3161423c1
+msgid "This feature is supported on the following hypervisors: XenServer, VMware, and KVM."
+msgstr ""
+
+#: ../../about.rst:286
+# aeaf1c1efba14b47ab9c6dd048ac9991
+msgid "The detailed instruction is provided in the CloudStack 4.3 Administration Guide. See section 17.5.4. Service Monitoring Tool for Virtual Router."
+msgstr ""
+
+#: ../../about.rst:290
+# e765090bf54a460ca6a394879a4846dd
+msgid "Custom Compute Offering"
+msgstr ""
+
+#: ../../about.rst:292
+# c58cbd0661224b5aaba9862a0f2aa92d
+msgid "CloudStack provides you the flexibility to specify the desired values for the number of CPU, CPU speed, and memory while deploying a VM. The admin creates a Compute Offering by marking it as custom, and as an user, you will be able to customize this dynamic Compute Offering by specifying the memory, CPU and root disk at the time of VM creation or upgrade."
+msgstr ""
+
+#: ../../about.rst:299
+# 3fddca4fb9da49ad86402020e89a2f67
+msgid "Custom Compute Offering is same as the normal Compute Offering except that the values of the dynamic parameters will be set to zeros in the given set of templates. Use this offering to deploy VM by specifying custom values for the dynamic parameters. Memory, CPU and number of CPUs are considered as dynamic parameters. Dynamic Compute Offerings can be used in following cases: deploying a VM, changing the compute offering of a stopped VM and running VMs, which is nothing but scaling up. To support this feature a new field, Custom, has been added to the Create Compute Offering page. If the Custom field is checked, the end-user will be able to create a custom Compute Offering by filling in the desired values for number of CPU, CPU speed, and memory."
+msgstr ""
+
+#: ../../about.rst:312
+# c45fbc9d5812419d8e5659b31d9a3701
+msgid "Remote Access VPN for VPC"
+msgstr ""
+
+#: ../../about.rst:314
+# 3a53541d7f42456aaa3fbf0e9f0d580b
+msgid "Support for Remote access VPN in Isolated networks is now extended to VPC networks. Remote users will now be able to initiate a VPN connection to a VPC network. To enable this feature, enable VPN in the Source NAT IP of the VPC."
+msgstr ""
+
+#: ../../about.rst:320
+# 951c3222d442439fb978cd6154b138f1
+msgid "Site to Site VPN Connection Between VPC Networks"
+msgstr ""
+
+#: ../../about.rst:322
+# 6a62ba77cd734a75b07d944e8a858de2
+msgid "CloudStack provides you with the ability to establish a site-to-site VPN connection between CloudStack virtual routers. With this functionality, users can deploy applications in multiple Availability Zones or VPCs, which can communicate with each other by using a secure Site-to-Site VPN Tunnel. Creating a typical Site to Site VPN connection between VPC networks involves the following:"
+msgstr ""
+
+#: ../../about.rst:331
+# 32395b38487f4fb1af795d6cac8d420a
+msgid "Create two VPCs. For example, VPC A and VPC B."
+msgstr ""
+
+#: ../../about.rst:335
+# 6c1e1dbd31244723b14cd116e34cffbb
+msgid "Create VPN gateways on both the VPCs you created."
+msgstr ""
+
+#: ../../about.rst:339
+# 29cbe5a50cf245608e0cec45c87e90f9
+msgid "Create VPN customer gateway for both the VPCs."
+msgstr ""
+
+#: ../../about.rst:343
+# 6a8a8359c0974163b9dd4016bfee540e
+msgid "Enable a VPN connection on VPC A in passive mode."
+msgstr ""
+
+#: ../../about.rst:345
+# 4615ac14561345f1943cce5fdd745216
+msgid "Ensure that the customer gateway is pointed to VPC B. The VPN connection is shown in the Disconnected state."
+msgstr ""
+
+#: ../../about.rst:350
+# ac948a0813e74cefbba1495ce1d94a01
+msgid "Enable a VPN connection on VPC B."
+msgstr ""
+
+#: ../../about.rst:352
+# cc7322058e944ab2b238719fbd79390a
+msgid "Ensure that the customer gateway is pointed to VPC A. Because virtual router of VPC A, in this case, is in passive mode and is waiting for the virtual router of VPC B to initiate the connection. The virtual router of VPC B should not be in passive mode."
+msgstr ""
+
+#: ../../about.rst:357
+# 92ba5b7586c349e6b946c1d46be6fb2d
+msgid "The VPN connection is shown in the Disconnected state."
+msgstr ""
+
+#: ../../about.rst:359
+# 1fa6614237044be1b758972b7f138f61
+msgid "Creating VPN connection on both the VPCs initiates a VPN connection. Wait for few seconds. The default is 30 seconds for both the VPN connections to show the Connected state."
+msgstr ""
+
+#: ../../about.rst:364
+# 7f80e1e445fc4471be85c99f9a63fae1
+msgid "Reporting CPU Sockets"
+msgstr ""
+
+#: ../../about.rst:366
+# 8cdc324e21274d65bb9c00645c27eedc
+msgid "CloudStack now provides an additional infrastructure statistics for CPU sockets managed by CloudStack, which in turn reflects the size of the cloud. The Infrastructure tab has a new tab for sockets. The Socket page will give you the number of hosts an sockets used for each hypervisor type. This feature is not supported in versions prior to XenServer 6.2."
+msgstr ""
+
+#: ../../about.rst:373
+# 3b300053085f4c51865c61cee31b9c86
+msgid "Database High Availability"
+msgstr ""
+
+#: ../../about.rst:375
+# 2d55be3748744201aecff258124d7a84
+msgid "To help ensure high availability of the databases that store the internal data for CloudStack, you can set up database replication. This covers both the main CloudStack database and the Usage database. Replication is achieved using the MySQL connector parameters and two-way replication. Tested with MySQL 5.1 and 5.5. Database replication in CloudStack is provided using the MySQL replication capabilities. The steps to set up replication can be found in the MySQL documentation."
+msgstr ""
+
+#: ../../about.rst:384
+# ff5e8279823b47249d289b0f66b569c6
+msgid "LDAP User Provisioning"
+msgstr ""
+
+#: ../../about.rst:386
+# 3ce8e3c638fe4a5da87bf86da7c0eb78
+msgid "LDAP user provisioning has been enhanced by allowing user import from the configured LDAP servers. You will be able to add multiple LDAP servers and selectively import LDAP users. You can o filter by group name and import all the users within a group. After they have been imported to CloudStack, in contrast to manually adding them in previous releases, users are allowed to directly log in to CloudStack by using the LDAP credentials."
+msgstr ""
+
+#: ../../about.rst:395
+# 3536819d2546433fb18b893f551a10c9
+msgid "Migrating NFS Secondary Storage to Object Store"
+msgstr ""
+
+#: ../../about.rst:397
+# b6682b07f6e948b499fdd7d6fe164d92
+msgid "In an existing zone that is using NFS for secondary storage, you can upgrade the zone to use a region-wide object storage without causing downtime. The existing NFS storage in the zone will be converted to an NFS Staging Store. After migration, the data that was on the NFS storage remains there. CloudStack does not provide a way to automatically migrate all data to the new object storage. The data remaining on the old NFS storage will remain accessible for read and delete operations only. Newly created snapshots and templates will be placed in the newly configured object storage."
+msgstr ""
+
+#: ../../about.rst:408
+# e2059568a2df4bd5823a5b7f17d09451
+msgid "VXLAN Plugin Support"
+msgstr ""
+
+#: ../../about.rst:410
+# 1e4361812f7d4a5aa2ac245baace915f
+msgid "The VXLAN plugin adds VXLAN as one of the guest network isolation methods in CloudStack. This plugin enables more than 4096 isolated guest networks in a Zone, with almost the same usability as VLAN isolation. This plugin provides no network services. Use virtual router for network services. This plugin is supported on KVM hypervisors."
+msgstr ""
+
+#: ../../about.rst:417
+# d5b76aea4bbb47b38bdd2659da294eed
+msgid "Contrail Network Plugin Support"
+msgstr ""
+
+#: ../../about.rst:419
+# d6f33ea8933841f98efa3b797425049e
+msgid "The Contrail virtual network controller is an open source project that provides an overlay implementation of network virtualization that is interoperable with network devices that support existing network virtualization standards. Support for the Contrail plugin has been added to CloudStack to provide NAT services to the XenServer hosts. The plugin supports isolated networks, Static NAT implemented by the VRouter dataplane, and Source NAT implemented by using a virtual appliance with full NAT functionality."
+msgstr ""
+
+#: ../../about.rst:429
+# 3f923c411f0246ddb382b9bb3b20fb63
+msgid "Publishing Alert Using the Web ROOT Admin API"
+msgstr ""
+
+#: ../../about.rst:431
+# 3866fb1f0a18405198edcc6ab7bf458f
+msgid "In previous releases of CloudStack code alerts are generated for CloudStack services (Usage service) only if they run on the same host as the Management Server. A new API has been introduced in 4.3, which can be used by the following services to generate and publish. The services need not be running on the same host where the Management Server is running."
+msgstr ""
+
+#: ../../about.rst:440
+# 8410cc0152774785aa48177c60589ab7
+msgid "Any new services added to CloudStack."
+msgstr ""
+
+#: ../../about.rst:444
+# 2aac9dee470c48fcb30e45594d822e46
+msgid "Usage service when run on a separate storage host."
+msgstr ""
+
+#: ../../about.rst:448
+# 8301f6de87114eed8372e75dc7d59c01
+msgid "Console Proxy and Secondary Storage VM services."
+msgstr ""
+
+#: ../../about.rst:450
+# 20d5528dcc9a40ba86ec266cc41fe9dd
+msgid "The main advantage of this feature is that the third party systems integrating with CloudStack will be able to utilize the Alert notification system publish alerts."
+msgstr ""
+
+#: ../../about.rst:455
+# 7219cbc180f64a2b84a6532d69e2c13f
+msgid "Support for Palo Alto Firewall Service"
+msgstr ""
+
+#: ../../about.rst:457
+# d8a2ab915328485b9e95aed7718895a4
+msgid "CloudStack supports Palo Alto firewall services. Use the Create Network Offering dialog to create an offering which has the Palo Alto firewall services. What is not supported and not supported are given below:"
+msgstr ""
+
+#: ../../about.rst:462
+# 5ab19452ad294aa0806ad47fa2098aa5
+msgid "Supported Functionalities"
+msgstr ""
+
+#: ../../about.rst:466
+# 645c0421480840e9b6980b1f944f8795
+msgid "Advanced Network"
+msgstr ""
+
+#: ../../about.rst:470
+# c934ca9385b04727a43ab39071588b72
+msgid "Parallel deployment with hardware Load balancer"
+msgstr ""
+
+#: ../../about.rst:474
+# 6447c3aa0d3143a7b4a3891d0f352ef5
+msgid "Virtual Palo Alto firewall."
+msgstr ""
+
+#: ../../about.rst:478
+# c63825cf282044879a8196691680be29
+msgid "Communication layer with Palo Alto APIs."
+msgstr ""
+
+#: ../../about.rst:482
+# 8d42e63976974e58b7f330f3578a2aef
+msgid "Mapping of CloudStack APIs to corresponding Palo Alto APIs."
+msgstr ""
+
+#: ../../about.rst:486
+# 37177f839d2741ef96c21c7f4767ac31
+msgid "Connectivity status of the firewall service on the CloudStack UI."
+msgstr ""
+
+#: ../../about.rst:489
+# 9e019a8a7e544690a3ee5874ec53f2e4
+msgid "Unsupported Functionalities"
+msgstr ""
+
+#: ../../about.rst:493
+# dfc850c506da4331992314cc0926b8c2
+msgid "Inline deployment with hardware Load balancer"
+msgstr ""
+
+#: ../../about.rst:497
+# decfb6946f324fe6b1594ba57d060e25
+msgid "Firewall between VLANs within an advanced network"
+msgstr ""
+
+#: ../../about.rst:501
+# 2c9f38f5cbe243208141b854a0892bee
+msgid "Firewall between VM instances"
+msgstr ""
+
+#: ../../about.rst:503
+# 289436a898b443cda15f4015c790ce78
+msgid "For more information, see `Palo Alto Firewall Integration <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Palo+Alto+Firewall+Integration>`__."
+msgstr ""
+
+#: ../../about.rst:507
+# 677b559b98014a0ca9160b277b871fd9
+msgid "Root Volume Metering"
+msgstr ""
+
+#: ../../about.rst:509
+# b0a9b0c2ced04a849783e40601c1c455
+msgid "CloudStack supports recording usage events as per the dynamically assigned resources. Usage events are registered when a VM is created from dynamic service offering, and the values of parameters, such as CPU, speed, RAM are recorded. If VM is deployed by using template and dynamic root disk size is mentioned, the same value is recorded in the usage event."
+msgstr ""
+
+#: ../../about.rst:517
+# c50214ba81b249a595f65e7546f35f8c
+msgid "Support for SSL Termination"
+msgstr ""
+
+#: ../../about.rst:519
+# 7671dd6babb446dca44a477d3e09f8f5
+msgid "SSL Offloading allows load balancers to handle encryption and decryption of HTTP(s) traffic giving plain text HTTP to the back end servers freeing them from the resource intensive task of handling encryption and decryption. Supported for Citrix NetScaler."
+msgstr ""
+
+#: ../../about.rst:525
+# a657b31bba0d477381342a4169e672a8
+msgid "Support for Pluggable VM Snapshots"
+msgstr ""
+
+#: ../../about.rst:527
+# 97c95ed5aa4648bab662e6f3a68ca4c7
+msgid "CloudStack implements a plugin to integrate a third-party storage provider. Third party storage providers can integrate with CloudStack to provide either primary storage or secondary storage. The user enables a storage plugin through the UI. A new dialog box choice is offered to select the storage provider. Depending on which provider is selected, additional input fields may appear so that the user can provide the additional details required by that provider, such as a user name and password for a third-party storage account."
+msgstr ""
+
+#: ../../about.rst:537
+# 613dd9e315124de1873cca35dd5d16b9
+msgid "Enhanced CloudStack UI"
+msgstr ""
+
+#: ../../about.rst:539
+# e96027034f66405aa2305070f44d66e7
+msgid "A complete UI makeover is implemented to enhance the usability and user experience in modern browsers. The visual look-and-feel has been changed for the Header, Navigation, Buttons, text fields, drop-downs, tables and so on. Consistent color themes has been introduced to match with the Apache branding."
+msgstr ""
+
+#: ../../about.rst:545
+# 0c948052a4214991b7464682f517292d
+msgid "The current UI flow remains the same."
+msgstr ""
+
+#: ../../about.rst:548
+# 079640b7b7b64cd39436ad9200c35f48
+msgid "Depreciation of realhostip.com DNS and SSL certificate"
+msgstr ""
+
+#: ../../about.rst:549
+# a04ae7e6daff4b42a2724df6a1b224d8
+msgid "The realhostip.com dynamic DNS resolution service is being retired this summer. In advance of that, CloudStack 4.3 no longer uses realhostip.com DNS domains or SSL certificates to encrypt Console Proxy or file copy communications."
+msgstr ""
+
+#: ../../about.rst:555
+# 1ab3e4e99a8342078cde95b5a5edba35
+msgid "Issues Fixed in 4.3.0"
+msgstr ""
+
+#: ../../about.rst:557
+#: ../../about.rst:732
+# 952dc9ec1db44f2d83a142ae895eb79b
+# b659d6162a3e49bfab48e1304597c5c1
+msgid "Apache CloudStack uses `Jira <https://issues.apache.org/jira/browse/CLOUDSTACK>`__ to track its issues. All new features and bugs for 4.3 have been tracked in Jira, and have a standard naming convention of \"CLOUDSTACK-NNNN\" where \"NNNN\" is the issue number."
+msgstr ""
+
+#: ../../about.rst:560
+# e477344cc35049a28eb3809f6f6b4a70
+msgid "For the list of issues fixed, see `Issues Fixed in 4.3 <https://issues.apache.org/jira/issues/?filter=12326161>`__."
+msgstr ""
+
+#: ../../about.rst:564
+#: ../../about.rst:739
+# 19c393aa43644c4490205799f532afe1
+# f19ac9d2986d450c8fef7d562c66ca50
+msgid "Bug ID"
+msgstr ""
+
+#: ../../about.rst:564
+#: ../../about.rst:739
+# 24a0954d4ea547449bdcfd807a54c2c7
+# cddb8801a6e64717b905df373c4dde4d
+msgid "Description"
+msgstr ""
+
+#: ../../about.rst:566
+# a43fa93540ee49e28a672d3f5bcc387a
+msgid "`CLOUDSTACK-6103 <https://issues.apache.org/jira/browse/CLOUDSTACK-6103>`_"
+msgstr ""
+
+#: ../../about.rst:566
+# 172a3e260cc043038020f4dceb7d5a0c
+msgid "vms with isos attached don't migrate..."
+msgstr ""
+
+#: ../../about.rst:567
+# aad0e8086ae546b8a875996d93b928c5
+msgid "`CLOUDSTACK-6089 <https://issues.apache.org/jira/browse/CLOUDSTACK-6089>`_"
+msgstr ""
+
+#: ../../about.rst:567
+# 4ff487a8cd9f41688c7249ebc52abe3b
+msgid "resource tags show up in multiples..."
+msgstr ""
+
+#: ../../about.rst:568
+# 92e3feccfc9f4657bdecbd3b99b54d45
+msgid "`CLOUDSTACK-6046 <https://issues.apache.org/jira/browse/CLOUDSTACK-6046>`_"
+msgstr ""
+
+#: ../../about.rst:568
+# e137bb96bac543349f0016165abe9bc3
+msgid "CreateVolume from snapshot is failing with S3 as secondary storage and zone-wide..."
+msgstr ""
+
+#: ../../about.rst:569
+# 27d6b9e3aab54128a4f0aad5c984f3b0
+msgid "`CLOUDSTACK-6040 <https://issues.apache.org/jira/browse/CLOUDSTACK-6040>`_"
+msgstr ""
+
+#: ../../about.rst:569
+# cccd886a01824191afea0e7730507e27
+msgid "Failed to configure PF on vm secondary ip for shared network..."
+msgstr ""
+
+#: ../../about.rst:570
+# 85eb969880864b4d9cef31eb992935c3
+msgid "`CLOUDSTACK-6007 <https://issues.apache.org/jira/browse/CLOUDSTACK-6007>`_"
+msgstr ""
+
+#: ../../about.rst:570
+# f613c25ec8e34d1a9eaad46ce27933e8
+msgid "[VMware] RestoreVM API fails with NPE..."
+msgstr ""
+
+#: ../../about.rst:571
+# fd7f4037eceb48d2b0b81c6513e3208b
+msgid "`CLOUDSTACK-5986 <https://issues.apache.org/jira/browse/CLOUDSTACK-5986>`_"
+msgstr ""
+
+#: ../../about.rst:571
+# f6112b6f33c74c498637f7599dacd888
+msgid "dnsmasq racy condition result in dnsmasq failed to handout IP address..."
+msgstr ""
+
+#: ../../about.rst:572
+# 848d35efab59400d907ff4c154ad7db3
+msgid "`CLOUDSTACK-5971 <https://issues.apache.org/jira/browse/CLOUDSTACK-5971>`_"
+msgstr ""
+
+#: ../../about.rst:572
+# 9165b730c684401bb0d160785380a8e9
+msgid "Templates created from a snapshots can't be copied to other zones..."
+msgstr ""
+
+#: ../../about.rst:573
+# 2fd9b8e5e39e4420a4c49090c6000892
+msgid "`CLOUDSTACK-5960 <https://issues.apache.org/jira/browse/CLOUDSTACK-5960>`_"
+msgstr ""
+
+#: ../../about.rst:573
+# af22070e3f9a4fd38055612952644a67
+msgid "Domain admin or user cannot register a template using S3/Swift object store..."
+msgstr ""
+
+#: ../../about.rst:574
+# 8397aeab15e044a8b1b6c72c46f83c25
+msgid "`CLOUDSTACK-5922 <https://issues.apache.org/jira/browse/CLOUDSTACK-5922>`_"
+msgstr ""
+
+#: ../../about.rst:574
+# 930ae632e9514c60bed68a9d53ea1ffb
+msgid "Incorrect handling RHEL guests ..."
+msgstr ""
+
+#: ../../about.rst:575
+# ee730af6c476432cb966506d5a88c89e
+msgid "`CLOUDSTACK-5921 <https://issues.apache.org/jira/browse/CLOUDSTACK-5921>`_"
+msgstr ""
+
+#: ../../about.rst:575
+# dee97e2e870f433096e88d01b05c8e62
+msgid "S3 security key is stored in DB unencrypted..."
+msgstr ""
+
+#: ../../about.rst:576
+# 93ad54e6b1d44a3ab0ccdb3cdff12008
+msgid "`CLOUDSTACK-5903 <https://issues.apache.org/jira/browse/CLOUDSTACK-5903>`_"
+msgstr ""
+
+#: ../../about.rst:576
+# e7ba5c879e744a6ba1d69aabc6a24b64
+msgid "CLONE - OVA files exist for templates created from volumes..."
+msgstr ""
+
+#: ../../about.rst:577
+# c5fe040ebfea4cc3b072eec9b743d6de
+msgid "`CLOUDSTACK-5895 <https://issues.apache.org/jira/browse/CLOUDSTACK-5895>`_"
+msgstr ""
+
+#: ../../about.rst:577
+# 7a316a57ea2e41babc33969f4bfc7b5f
+msgid "CreateVolumeFromSnapshot can fail in a multiple pod environment with tagged stor..."
+msgstr ""
+
+#: ../../about.rst:578
+# 9ebb40a97a2d4b458e1c47b982d14802
+msgid "`CLOUDSTACK-5886 <https://issues.apache.org/jira/browse/CLOUDSTACK-5886>`_"
+msgstr ""
+
+#: ../../about.rst:578
+# 728849191fa0442ba1e79ecf2cba0e10
+msgid "4.2.1 upgrade fails on acl migration..."
+msgstr ""
+
+#: ../../about.rst:579
+# 0e2dfb62b791451eb9ef455be4556257
+msgid "`CLOUDSTACK-5877 <https://issues.apache.org/jira/browse/CLOUDSTACK-5877>`_"
+msgstr ""
+
+#: ../../about.rst:579
+# 3941c0f94cf54e16b4b88c9b584450ab
+msgid "listTemplates does not sort based on sort_key..."
+msgstr ""
+
+#: ../../about.rst:580
+# 596cb956d35b42b2b11fb2445190a0f6
+msgid "`CLOUDSTACK-5875 <https://issues.apache.org/jira/browse/CLOUDSTACK-5875>`_"
+msgstr ""
+
+#: ../../about.rst:580
+# 9afc247c85e64b7bb689a6944739c737
+msgid "No templates in simulator run..."
+msgstr ""
+
+#: ../../about.rst:581
+# 8a070062759545ac924e81915e5c2fb6
+msgid "`CLOUDSTACK-5864 <https://issues.apache.org/jira/browse/CLOUDSTACK-5864>`_"
+msgstr ""
+
+#: ../../about.rst:581
+# 1daa9aac7b264d57ad7801634f30e516
+msgid "Simulator profile broken ..."
+msgstr ""
+
+#: ../../about.rst:582
+# fab087d4848847879dbc1a09b3a65350
+msgid "`CLOUDSTACK-5813 <https://issues.apache.org/jira/browse/CLOUDSTACK-5813>`_"
+msgstr ""
+
+#: ../../about.rst:582
+# 84929748e059490d91860839cbf5f368
+msgid "With S3 as secondary storage, snapshot taken in one zone cannot be used to creat..."
+msgstr ""
+
+#: ../../about.rst:583
+# 873ec58c448c4bc2b3576ecbfe08fe91
+msgid "`CLOUDSTACK-5723 <https://issues.apache.org/jira/browse/CLOUDSTACK-5723>`_"
+msgstr ""
+
+#: ../../about.rst:583
+# f4ab3c42228f469893405062f75837e7
+msgid "Malfunction agent may block future SSL connection to the server..."
+msgstr ""
+
+#: ../../about.rst:584
+# c7ba7e92feec492b96e76195ecee04d0
+msgid "`CLOUDSTACK-5704 <https://issues.apache.org/jira/browse/CLOUDSTACK-5704>`_"
+msgstr ""
+
+#: ../../about.rst:584
+# 0fd950ccfcf148d781d426eb7f99bde9
+msgid "OVA files exist for templates created from volumes..."
+msgstr ""
+
+#: ../../about.rst:585
+# eddc8a46975945a38c1801c2e9ab0078
+msgid "`CLOUDSTACK-5701 <https://issues.apache.org/jira/browse/CLOUDSTACK-5701>`_"
+msgstr ""
+
+#: ../../about.rst:585
+# e54362e110fe41b385fe444e37aa537a
+msgid "size column is not getting updated in snapshot_store_ref table...."
+msgstr ""
+
+#: ../../about.rst:586
+# 0cd9023c1b8a4681b3b70500efaaa55f
+msgid "`CLOUDSTACK-5666 <https://issues.apache.org/jira/browse/CLOUDSTACK-5666>`_"
+msgstr ""
+
+#: ../../about.rst:586
+# dd77df5602ab47a9a24ef7c717bf9d85
+msgid "Cant remove a nic when a vm is in the Stopped state ..."
+msgstr ""
+
+#: ../../about.rst:587
+# 32a8651ac0b340f7855db6d56a5ccee8
+msgid "`CLOUDSTACK-5661 <https://issues.apache.org/jira/browse/CLOUDSTACK-5661>`_"
+msgstr ""
+
+#: ../../about.rst:587
+# 06b0a669cac447b5863820f66808bb7d
+msgid "[VMware] DetachIsoCmd succeeds even though cdrom is locked by VM as cdrom is mou..."
+msgstr ""
+
+#: ../../about.rst:588
+# a7a0c5068a634d4c915bb24cded1c94e
+msgid "`CLOUDSTACK-5653 <https://issues.apache.org/jira/browse/CLOUDSTACK-5653>`_"
+msgstr ""
+
+#: ../../about.rst:588
+# e6dff212b59a48faa951040a6712829e
+msgid "S3 object store as Secondary Storage, the template created from different zone i..."
+msgstr ""
+
+#: ../../about.rst:589
+# 8ed057a05d0b4840b00ce1e2bb4cbc15
+msgid "`CLOUDSTACK-5613 <https://issues.apache.org/jira/browse/CLOUDSTACK-5613>`_"
+msgstr ""
+
+#: ../../about.rst:589
+# 91c47fd5727f4964b9c2ed0a04c103db
+msgid "CloudStack 4.2.0 - Usage server is running but tables remain empty..."
+msgstr ""
+
+#: ../../about.rst:590
+# b110177bebcd4addb8b09bc5c3bd76b6
+msgid "`CLOUDSTACK-5608 <https://issues.apache.org/jira/browse/CLOUDSTACK-5608>`_"
+msgstr ""
+
+#: ../../about.rst:590
+# ebdfe4750fee42c0915b3990ec49c4f7
+msgid "HyperV Builtin and System vm template entries missing in 4.3 upgrade setup..."
+msgstr ""
+
+#: ../../about.rst:591
+# 409d294a556c4d4bb401a5df0493e0ef
+msgid "`CLOUDSTACK-5534 <https://issues.apache.org/jira/browse/CLOUDSTACK-5534>`_"
+msgstr ""
+
+#: ../../about.rst:591
+# 60a31acf9894466995a20b662749ed46
+msgid "MySQL exception raised when searching for users with keyword..."
+msgstr ""
+
+#: ../../about.rst:592
+# 71047f1716d3425696c0b255eca912b8
+msgid "`CLOUDSTACK-5533 <https://issues.apache.org/jira/browse/CLOUDSTACK-5533>`_"
+msgstr ""
+
+#: ../../about.rst:592
+# e3ccfbc9c09449819b1141a9078951d7
+msgid "Virtual router in shared network does respond to DNS even when no DNS service is..."
+msgstr ""
+
+#: ../../about.rst:593
+# b01fb15aaba740058f3a7d9552395cb0
+msgid "`CLOUDSTACK-5532 <https://issues.apache.org/jira/browse/CLOUDSTACK-5532>`_"
+msgstr ""
+
+#: ../../about.rst:593
+# 13eebd1cd2d14980a7f9f4135a355027
+msgid "Long tag values are not readable within the UI..."
+msgstr ""
+
+#: ../../about.rst:594
+# 0a3611c289324c9d9977b5e331ecd62c
+msgid "`CLOUDSTACK-5519 <https://issues.apache.org/jira/browse/CLOUDSTACK-5519>`_"
+msgstr ""
+
+#: ../../about.rst:594
+# ff5c9f0f0d034143be802c76448ed125
+msgid "[VMWARE] Cancel vCenter tasks if the task invoked by CloudStack failes with time..."
+msgstr ""
+
+#: ../../about.rst:595
+# 4e5be5d95e474f3d9fe576232e89d9c4
+msgid "`CLOUDSTACK-5517 <https://issues.apache.org/jira/browse/CLOUDSTACK-5517>`_"
+msgstr ""
+
+#: ../../about.rst:595
+# e5b76e0e3f6f457d8c70d29198fd3108
+msgid "NPE observed during \"release portable IPs\" as part of account cleanup..."
+msgstr ""
+
+#: ../../about.rst:596
+# 3f1c335388784560bc5ed7d7c9a8f281
+msgid "`CLOUDSTACK-5514 <https://issues.apache.org/jira/browse/CLOUDSTACK-5514>`_"
+msgstr ""
+
+#: ../../about.rst:596
+# ccffa519c73c42a79caf211baf574b29
+msgid "Response of listAccounts API call includes removed users..."
+msgstr ""
+
+#: ../../about.rst:597
+# d105f33710e9422d85cd8764e79f49cd
+msgid "`CLOUDSTACK-5513 <https://issues.apache.org/jira/browse/CLOUDSTACK-5513>`_"
+msgstr ""
+
+#: ../../about.rst:597
+# 585199f3e2194cf7ba8a1888d15a786f
+msgid "VM can't start after creating snapshot from it (CS4.2 + VMware 5.1)..."
+msgstr ""
+
+#: ../../about.rst:598
+# beb21f35d213432cb471c4e2fe8bd524
+msgid "`CLOUDSTACK-5481 <https://issues.apache.org/jira/browse/CLOUDSTACK-5481>`_"
+msgstr ""
+
+#: ../../about.rst:598
+# d7f6cbe2070b49078c83beb74e462183
+msgid "Regular User is unable to use \"Add Isolated Network\" Button on the UI..."
+msgstr ""
+
+#: ../../about.rst:599
+# aef0f1b14c53491da7b807dc7144fe0c
+msgid "`CLOUDSTACK-5466 <https://issues.apache.org/jira/browse/CLOUDSTACK-5466>`_"
+msgstr ""
+
+#: ../../about.rst:599
+# 94b636446b3747a784cfe9532d4d300f
+msgid "removeIpFromNic not working properly..."
+msgstr ""
+
+#: ../../about.rst:600
+# 958fa48f21c04a51855c5d0659cf1190
+msgid "`CLOUDSTACK-5453 <https://issues.apache.org/jira/browse/CLOUDSTACK-5453>`_"
+msgstr ""
+
+#: ../../about.rst:600
+# 1c76166e9b6543dca3fbf26468a1187b
+msgid "Site-to-site VPN connection status monitoring is broken in KVM..."
+msgstr ""
+
+#: ../../about.rst:601
+# 8cd304a426924ea7a8aa03637330f80a
+msgid "`CLOUDSTACK-5431 <https://issues.apache.org/jira/browse/CLOUDSTACK-5431>`_"
+msgstr ""
+
+#: ../../about.rst:601
+# 9d5df4e7abbb4e13a2b04d683139fc85
+msgid "permit 'http' as service type for GSLB rule..."
+msgstr ""
+
+#: ../../about.rst:602
+# 164e76cd04014c1dac9d0656fe55333c
+msgid "`CLOUDSTACK-5428 <https://issues.apache.org/jira/browse/CLOUDSTACK-5428>`_"
+msgstr ""
+
+#: ../../about.rst:602
+# b26407e9f7904625a9358bc18cf908b0
+msgid "support NetScaler to be configured exclusively for GSLB service and not used for..."
+msgstr ""
+
+#: ../../about.rst:603
+# e855f3e23fce4ca2be395b8c7483f375
+msgid "`CLOUDSTACK-5426 <https://issues.apache.org/jira/browse/CLOUDSTACK-5426>`_"
+msgstr ""
+
+#: ../../about.rst:603
+# 5cbdc97a57a64da29bdd377ebb7923e6
+msgid "Cannot deploy instance having multiple volumes that use different storage tags f..."
+msgstr ""
+
+#: ../../about.rst:604
+# 6eb9a9c3ebfa4afbb9ee54872b06cbd4
+msgid "`CLOUDSTACK-5422 <https://issues.apache.org/jira/browse/CLOUDSTACK-5422>`_"
+msgstr ""
+
+#: ../../about.rst:604
+# 86740bf59c384d9da4395fc768d6fa75
+msgid "Changing XenServer Tools Version 6.1 + doesnt work ..."
+msgstr ""
+
+#: ../../about.rst:605
+# 9a28c24991924f808b75427dd664ef99
+msgid "`CLOUDSTACK-5417 <https://issues.apache.org/jira/browse/CLOUDSTACK-5417>`_"
+msgstr ""
+
+#: ../../about.rst:605
+# 47e1a9eafa9d44cdae779b6658bb1e48
+msgid "On network restart for external devices egress rules configured with old CIDR..."
+msgstr ""
+
+#: ../../about.rst:606
+# 40c7825d2c1348cd9d0d7b39746a08e9
+msgid "`CLOUDSTACK-5416 <https://issues.apache.org/jira/browse/CLOUDSTACK-5416>`_"
+msgstr ""
+
+#: ../../about.rst:606
+# 64c9bb755c454b8fa55863203ca25b0d
+msgid "[VMware] Not able to add seventh disk to VM in an upgraded setup..."
+msgstr ""
+
+#: ../../about.rst:607
+# a6c82beb23e84bb0990e58c667423fcd
+msgid "`CLOUDSTACK-5404 <https://issues.apache.org/jira/browse/CLOUDSTACK-5404>`_"
+msgstr ""
+
+#: ../../about.rst:607
+# 0dc8297ef30b4defbd669083e14e83e0
+msgid "Network usages (bytes sent/received) are saved in the wrong timezone..."
+msgstr ""
+
+#: ../../about.rst:608
+# 1c1abad42a6248609d07bca0db8e973e
+msgid "`CLOUDSTACK-5401 <https://issues.apache.org/jira/browse/CLOUDSTACK-5401>`_"
+msgstr ""
+
+#: ../../about.rst:608
+# c156cd7b21e640c4860bf028420d26c5
+msgid "VM migration during host maintenance fails if pool.storage.capacity.disablethres..."
+msgstr ""
+
+#: ../../about.rst:609
+# 74df6416b8d24e18bf0e42f285ddbcad
+msgid "`CLOUDSTACK-5391 <https://issues.apache.org/jira/browse/CLOUDSTACK-5391>`_"
+msgstr ""
+
+#: ../../about.rst:609
+# c6136e978f5343dbaeb51262df64c7f8
+msgid "Change service offering of a stopped vm and then starting it should check host c..."
+msgstr ""
+
+#: ../../about.rst:610
+# 160fa3d6876b4b67866b179389f08144
+msgid "`CLOUDSTACK-5355 <https://issues.apache.org/jira/browse/CLOUDSTACK-5355>`_"
+msgstr ""
+
+#: ../../about.rst:610
+# 3892afea22cf432ab5251b6111d9ccce
+msgid "addImageStore should not log password in clear text in the log..."
+msgstr ""
+
+#: ../../about.rst:611
+# fec037aa605441058b452eae5f75c02d
+msgid "`CLOUDSTACK-5354 <https://issues.apache.org/jira/browse/CLOUDSTACK-5354>`_"
+msgstr ""
+
+#: ../../about.rst:611
+# f79bf3459deb495292ce27588f86b9b3
+msgid "CLONE - UI - normal users are not allowed to edit their own iso..."
+msgstr ""
+
+#: ../../about.rst:612
+# bcd983fb1b99452f8f416b46290de8cb
+msgid "`CLOUDSTACK-5352 <https://issues.apache.org/jira/browse/CLOUDSTACK-5352>`_"
+msgstr ""
+
+#: ../../about.rst:612
+# 350e7ff63c9b429f9424b556e21ad566
+msgid "CPU cap calculated incorrectly for VMs on XenServer hosts..."
+msgstr ""
+
+#: ../../about.rst:613
+# 7b1fc63cee124b35822ec3eb8fc7f6af
+msgid "`CLOUDSTACK-5332 <https://issues.apache.org/jira/browse/CLOUDSTACK-5332>`_"
+msgstr ""
+
+#: ../../about.rst:613
+# feb3d1322a1241cc9eb08917cd4743be
+msgid "Network offering don't use new system offering for router..."
+msgstr ""
+
+#: ../../about.rst:614
+# 1a2119ed5e8248f19652bef8401fd0e6
+msgid "`CLOUDSTACK-5303 <https://issues.apache.org/jira/browse/CLOUDSTACK-5303>`_"
+msgstr ""
+
+#: ../../about.rst:614
+# 5afc8932f7494cb4a20358ef8fff503b
+msgid "\"snapshot\" count and \"secondary_storage\" count are not correct in resource_coun..."
+msgstr ""
+
+#: ../../about.rst:615
+# 2affca7697264ca19bac046fd526e064
+msgid "`CLOUDSTACK-5302 <https://issues.apache.org/jira/browse/CLOUDSTACK-5302>`_"
+msgstr ""
+
+#: ../../about.rst:615
+# 877ffb2b03974c0ba79f53c413f1eafb
+msgid "listHosts API response - value of cpuallocated is always 0%..."
+msgstr ""
+
+#: ../../about.rst:616
+# 8ccbb840f7664ac4ba5113134c738df7
+msgid "`CLOUDSTACK-5299 <https://issues.apache.org/jira/browse/CLOUDSTACK-5299>`_"
+msgstr ""
+
+#: ../../about.rst:616
+# 5a90aac42d5a481d8da1ef7de0512938
+msgid "Can not get hypervisor type for volumes..."
+msgstr ""
+
+#: ../../about.rst:617
+# 66a67bf63cee4915bdd5d4d611e60139
+msgid "`CLOUDSTACK-5293 <https://issues.apache.org/jira/browse/CLOUDSTACK-5293>`_"
+msgstr ""
+
+#: ../../about.rst:617
+# a0f8e5038019429888fb26ff53c118e6
+msgid "Error while collecting vm disk stats from hosts if iso is attached to vm..."
+msgstr ""
+
+#: ../../about.rst:618
+# 07c42615e51548f69f8c30439d921d17
+msgid "`CLOUDSTACK-5285 <https://issues.apache.org/jira/browse/CLOUDSTACK-5285>`_"
+msgstr ""
+
+#: ../../about.rst:618
+# 8ff7ce2ceaf24e1e983ba48c88965524
+msgid "Correct the API command description for removeIpFromNic..."
+msgstr ""
+
+#: ../../about.rst:619
+# 9513c8669b24496290525568709a9ef4
+msgid "`CLOUDSTACK-5261 <https://issues.apache.org/jira/browse/CLOUDSTACK-5261>`_"
+msgstr ""
+
+#: ../../about.rst:619
+# d57c730aacac4bf786480d0efe5d6457
+msgid "Ability to publish Alerts via CS Root API..."
+msgstr ""
+
+#: ../../about.rst:620
+# e1a8f1ff555e406a9509a94434de8f82
+msgid "`CLOUDSTACK-5260 <https://issues.apache.org/jira/browse/CLOUDSTACK-5260>`_"
+msgstr ""
+
+#: ../../about.rst:620
+# 4664a6293efc4d7c814b9b4e9bc5d4c1
+msgid "Vmware 5.1 Deploy Template Error : Read Timeout..."
+msgstr ""
+
+#: ../../about.rst:621
+# 291a2a8b016b43d599c1bcf9b8d43dfa
+msgid "`CLOUDSTACK-5228 <https://issues.apache.org/jira/browse/CLOUDSTACK-5228>`_"
+msgstr ""
+
+#: ../../about.rst:621
+# 592e7ee58ff44ca696e5ef93df69756c
+msgid "[API] [EIP/ELB enabled Zone] Need to display EIP address as \"Public IP Address\" ..."
+msgstr ""
+
+#: ../../about.rst:622
+# 9b9c697badbd497ca85bbc500ebb72c5
+msgid "`CLOUDSTACK-5227 <https://issues.apache.org/jira/browse/CLOUDSTACK-5227>`_"
+msgstr ""
+
+#: ../../about.rst:622
+# 46bccacdbe06484aa0199e60e40300e9
+msgid "Cannot pass Japanese characters as parameter values to API..."
+msgstr ""
+
+#: ../../about.rst:623
+# e0e1c93ad5e64a79a45ab35053f01cfb
+msgid "`CLOUDSTACK-5218 <https://issues.apache.org/jira/browse/CLOUDSTACK-5218>`_"
+msgstr ""
+
+#: ../../about.rst:623
+# 81e81b34f1a344af9009ad60222702d1
+msgid "CLONE - [Doc] Make VMware vCenter session timeout value configurable...."
+msgstr ""
+
+#: ../../about.rst:624
+# bab494bd96fb44988e3d25277cccd030
+msgid "`CLOUDSTACK-5199 <https://issues.apache.org/jira/browse/CLOUDSTACK-5199>`_"
+msgstr ""
+
+#: ../../about.rst:624
+# def3f3a51fdf4b1b92c987286f59359f
+msgid "Cannot restart VM after taking a VM snapshot of an existing VM or reverting a VM..."
+msgstr ""
+
+#: ../../about.rst:625
+# a79b0cd2aff14097aa1ad07d0dd422aa
+msgid "`CLOUDSTACK-5141 <https://issues.apache.org/jira/browse/CLOUDSTACK-5141>`_"
+msgstr ""
+
+#: ../../about.rst:625
+# 8c8141ffce9e439bab4f678e9168b296
+msgid "[Automation] Router deployment failed due to failure in SavePasswordCommand, obs..."
+msgstr ""
+
+#: ../../about.rst:626
+# c75a8334357d4a83b752de6a11b2b4d7
+msgid "`CLOUDSTACK-5140 <https://issues.apache.org/jira/browse/CLOUDSTACK-5140>`_"
+msgstr ""
+
+#: ../../about.rst:626
+# d6831610409f4f188790c6d92247cb75
+msgid "A stopped vm cant start after disable threshold has been reached on the storage ..."
+msgstr ""
+
+#: ../../about.rst:627
+# 22cd66d5db22485fb325534c02440206
+msgid "`CLOUDSTACK-5138 <https://issues.apache.org/jira/browse/CLOUDSTACK-5138>`_"
+msgstr ""
+
+#: ../../about.rst:627
+# 4938e30eac0c48f2a122d345be81fcd9
+msgid "[Automation] NPE while create template from snapshot..."
+msgstr ""
+
+#: ../../about.rst:628
+# b20682c52bdf4288bed892d203f99526
+msgid "`CLOUDSTACK-5122 <https://issues.apache.org/jira/browse/CLOUDSTACK-5122>`_"
+msgstr ""
+
+#: ../../about.rst:628
+# 58cf214ec9d64115a3b85e9b3ab8ce36
+msgid "[VMware] System VMs are getting recreated with old template after upgrading to 4..."
+msgstr ""
+
+#: ../../about.rst:629
+# c043a910005e4cfea0bc16a8d9d06a9e
+msgid "`CLOUDSTACK-5105 <https://issues.apache.org/jira/browse/CLOUDSTACK-5105>`_"
+msgstr ""
+
+#: ../../about.rst:629
+# 17735be3e8194a42ae5cd0528fdbb019
+msgid "Template/ISO download fails cause the object to disappear from UI..."
+msgstr ""
+
+#: ../../about.rst:630
+# 09a4f78d472b43eda0644678d5c8c7d3
+msgid "`CLOUDSTACK-5098 <https://issues.apache.org/jira/browse/CLOUDSTACK-5098>`_"
+msgstr ""
+
+#: ../../about.rst:630
+# 7d7cca26788f4dd79f3cbd31e523e0b5
+msgid "[UI] Zone view is showing \"Add VMware Datacenter\" button even though zone is alr..."
+msgstr ""
+
+#: ../../about.rst:631
+# eb8ff0c3bda34421949b4667650cc1d5
+msgid "`CLOUDSTACK-5092 <https://issues.apache.org/jira/browse/CLOUDSTACK-5092>`_"
+msgstr ""
+
+#: ../../about.rst:631
+# 56d5e2c4ab894c55b42e20e05d149623
+msgid "[Automation] [BVT] Failed to copy template and ISO between zones in xen ..."
+msgstr ""
+
+#: ../../about.rst:632
+# b45bd9b4a8cf47d987a26dfe370ca028
+msgid "`CLOUDSTACK-5076 <https://issues.apache.org/jira/browse/CLOUDSTACK-5076>`_"
+msgstr ""
+
+#: ../../about.rst:632
+# 5835754aee834dc69fb7792ffdb7f3f8
+msgid "(Upgrade) reboot VM failed after bridge name change..."
+msgstr ""
+
+#: ../../about.rst:633
+# 23e18a9f4e944601a546ed29c964e216
+msgid "`CLOUDSTACK-5069 <https://issues.apache.org/jira/browse/CLOUDSTACK-5069>`_"
+msgstr ""
+
+#: ../../about.rst:633
+# af479331ce47410f98142b3d0648003c
+msgid "Make VMware vCenter session timeout value configurable...."
+msgstr ""
+
+#: ../../about.rst:634
+# 7aa387b30a3a475fa0411f488558ef4e
+msgid "`CLOUDSTACK-5066 <https://issues.apache.org/jira/browse/CLOUDSTACK-5066>`_"
+msgstr ""
+
+#: ../../about.rst:634
+# 44c96673b9494513930cd45d01464ccb
+msgid "Existed remote access VPN got dropped when adding new VPN users..."
+msgstr ""
+
+#: ../../about.rst:635
+# 116d66a48fd949439363507aca8310c3
+msgid "`CLOUDSTACK-5062 <https://issues.apache.org/jira/browse/CLOUDSTACK-5062>`_"
+msgstr ""
+
+#: ../../about.rst:635
+# c9d4decce149472da2241e905e1e55b8
+msgid "Deleting Load Balancing Rule fails when generating usage events are enabled..."
+msgstr ""
+
+#: ../../about.rst:636
+# 40095f5a91ab4d589f03f2f97f8f6c01
+msgid "`CLOUDSTACK-5054 <https://issues.apache.org/jira/browse/CLOUDSTACK-5054>`_"
+msgstr ""
+
+#: ../../about.rst:636
+# 43e2ed9dd8d1465db3bbb4ac659d8a44
+msgid "vm migration involving storage migration on vmware fails with exception \" The ob..."
+msgstr ""
+
+#: ../../about.rst:637
+# 79281854b68042959a44e49cb47e9068
+msgid "`CLOUDSTACK-5053 <https://issues.apache.org/jira/browse/CLOUDSTACK-5053>`_"
+msgstr ""
+
+#: ../../about.rst:637
+# d7b0c91ea5b84f67b0d1b8fa9c37b990
+msgid "No Qemu-KVM module dependency error message is displayed (if not present)while i..."
+msgstr ""
+
+#: ../../about.rst:638
+# 62a2b6949fe04d868cdb00cb753807ed
+msgid "`CLOUDSTACK-5042 <https://issues.apache.org/jira/browse/CLOUDSTACK-5042>`_"
+msgstr ""
+
+#: ../../about.rst:638
+# cd471cd674ba4b1990f5aa1ddb730ce5
+msgid "(Upgrade) Exception when stop VM after upgrade..."
+msgstr ""
+
+#: ../../about.rst:639
+# b5e9203fefc244c4b44ebba45ec12810
+msgid "`CLOUDSTACK-5029 <https://issues.apache.org/jira/browse/CLOUDSTACK-5029>`_"
+msgstr ""
+
+#: ../../about.rst:639
+# 39d6712e5e4b462183c0a37bf83065bd
+msgid "cloud-bugtool isn't in release package like release notes say..."
+msgstr ""
+
+#: ../../about.rst:640
+# cfd17a3c83424354a101243f1cf7bdc5
+msgid "`CLOUDSTACK-5025 <https://issues.apache.org/jira/browse/CLOUDSTACK-5025>`_"
+msgstr ""
+
+#: ../../about.rst:640
+# c787224cdecb4277a63f59419ade0354
+msgid "display_volume field is set to false by default for VolumeVO object..."
+msgstr ""
+
+#: ../../about.rst:641
+# e0db5d5193714503baaa63774c7883e7
+msgid "`CLOUDSTACK-5024 <https://issues.apache.org/jira/browse/CLOUDSTACK-5024>`_"
+msgstr ""
+
+#: ../../about.rst:641
+# 91985f80c06c4cafaf06c903a93cc7e8
+msgid "listVolumes: add support to list by storage pool (for admin only)..."
+msgstr ""
+
+#: ../../about.rst:642
+# b54e2b69fcf843548bcced086afdb8bb
+msgid "`CLOUDSTACK-5017 <https://issues.apache.org/jira/browse/CLOUDSTACK-5017>`_"
+msgstr ""
+
+#: ../../about.rst:642
+# 89f7cd3a438d498b8a9f547d29ba7da5
+msgid "If SSVM is unavailable DownloadCommands will be routed to mgmt server..."
+msgstr ""
+
+#: ../../about.rst:643
+# 13f38290069340c3a6960c8ace0fe864
+msgid "`CLOUDSTACK-5014 <https://issues.apache.org/jira/browse/CLOUDSTACK-5014>`_"
+msgstr ""
+
+#: ../../about.rst:643
+# 160f63d96c684fca9c79411f55054495
+msgid "vmware:deployVM with data disk failed with exception..."
+msgstr ""
+
+#: ../../about.rst:644
+# ecbb035c4ac349f1807dbd7c1f2b0ae3
+msgid "`CLOUDSTACK-5012 <https://issues.apache.org/jira/browse/CLOUDSTACK-5012>`_"
+msgstr ""
+
+#: ../../about.rst:644
+# 92d0c1c705a34bee9025d5f9c031c65d
+msgid "Bad data inserted into physical network labels for Zone Create Wizard using VMWa..."
+msgstr ""
+
+#: ../../about.rst:645
+# fc1711cc578a49b4bff7216747d1cd04
+msgid "`CLOUDSTACK-5008 <https://issues.apache.org/jira/browse/CLOUDSTACK-5008>`_"
+msgstr ""
+
+#: ../../about.rst:645
+# 79f4077e5ee548a9ab492510295a7187
+msgid "[VMWARE]Failed to start the VM after performing Cold Migration of Volume to Seco..."
+msgstr ""
+
+#: ../../about.rst:646
+# 5a205aae19e94a9595b247e2a2ea81d0
+msgid "`CLOUDSTACK-5002 <https://issues.apache.org/jira/browse/CLOUDSTACK-5002>`_"
+msgstr ""
+
+#: ../../about.rst:646
+# dce91c56d5c44611b1285a73c56bb875
+msgid "unable to destroy vm ;VM destroy failed in Stop i-2-59-VM Command due to You gav..."
+msgstr ""
+
+#: ../../about.rst:647
+# a9151f89758f4052ad1fda7a5ebec833
+msgid "`CLOUDSTACK-4998 <https://issues.apache.org/jira/browse/CLOUDSTACK-4998>`_"
+msgstr ""
+
+#: ../../about.rst:647
+# 23bb79a059e64a7bbd90af2216252f4c
+msgid "assignVirtualMachine API has wrong response string, causing Cloudmonkey to crash..."
+msgstr ""
+
+#: ../../about.rst:648
+# 1eee91dd1f4d4d13913b5499427b15da
+msgid "`CLOUDSTACK-4997 <https://issues.apache.org/jira/browse/CLOUDSTACK-4997>`_"
+msgstr ""
+
+#: ../../about.rst:648
+# b89d57e09f8c4c609b4f093c8af12eea
+msgid "OVS integration is broken..."
+msgstr ""
+
+#: ../../about.rst:649
+# 7ded99c897cc4af0b3e1664b8dfa87b2
+msgid "`CLOUDSTACK-4973 <https://issues.apache.org/jira/browse/CLOUDSTACK-4973>`_"
+msgstr ""
+
+#: ../../about.rst:649
+# 8c7263e10a3b4e0c915ef7848c025420
+msgid "CLONE - Specified keyboard language is not showing as default in consoleView pas..."
+msgstr ""
+
+#: ../../about.rst:650
+# 7dd970bb14874c4e880c05f61d69e120
+msgid "`CLOUDSTACK-4943 <https://issues.apache.org/jira/browse/CLOUDSTACK-4943>`_"
+msgstr ""
+
+#: ../../about.rst:650
+# ac3a0db207af47a082e2e8747cbad0e5
+msgid "Can't create cluster in CS 4.2..."
+msgstr ""
+
+#: ../../about.rst:651
+# fe4e42bf8a4a4c87bf1dbdf3d892352f
+msgid "`CLOUDSTACK-4941 <https://issues.apache.org/jira/browse/CLOUDSTACK-4941>`_"
+msgstr ""
+
+#: ../../about.rst:651
+# dfde391f57bc4705b0b09a46710393d3
+msgid "CLONE - Allocation capacity of a cluster during HA..."
+msgstr ""
+
+#: ../../about.rst:652
+# a69b885ec9174c529a710902645c2413
+msgid "`CLOUDSTACK-4935 <https://issues.apache.org/jira/browse/CLOUDSTACK-4935>`_"
+msgstr ""
+
+#: ../../about.rst:652
+# 76627021c06443dd8cd7cb4934c106f8
+msgid "Adding same network to VM multiple times resulting in failure, No new NIC is gen..."
+msgstr ""
+
+#: ../../about.rst:653
+# a1a864a7fc3f4738928e049dc639ac07
+msgid "`CLOUDSTACK-4931 <https://issues.apache.org/jira/browse/CLOUDSTACK-4931>`_"
+msgstr ""
+
+#: ../../about.rst:653
+# fed2e7496c794dbd8c4c5d953aa12b03
+msgid "observed NPE with new system vm template..."
+msgstr ""
+
+#: ../../about.rst:654
+# d83c883ef59d4e86b8bfd7317b2f9029
+msgid "`CLOUDSTACK-4913 <https://issues.apache.org/jira/browse/CLOUDSTACK-4913>`_"
+msgstr ""
+
+#: ../../about.rst:654
+# f43873d002164e958d8d498fbaec3341
+msgid "Disable security group for bridge mode non-security group zone..."
+msgstr ""
+
+#: ../../about.rst:655
+# c1a803ba102645349754b4400a8295cc
+msgid "`CLOUDSTACK-4904 <https://issues.apache.org/jira/browse/CLOUDSTACK-4904>`_"
+msgstr ""
+
+#: ../../about.rst:655
+# 061044bfcf674f22a7093620e8d16199
+msgid "Unable to see a derieved template if the parent template is deleted..."
+msgstr ""
+
+#: ../../about.rst:656
+# dedc905ddb864b2f89addf62aef0384d
+msgid "`CLOUDSTACK-4886 <https://issues.apache.org/jira/browse/CLOUDSTACK-4886>`_"
+msgstr ""
+
+#: ../../about.rst:656
+# 6e42fe77fa004d7d8329793f97675540
+msgid "cloud-setup-databases not escaping password in shell commands..."
+msgstr ""
+
+#: ../../about.rst:657
+# fa155cfb42d6462098798b1d5d59b458
+msgid "`CLOUDSTACK-4875 <https://issues.apache.org/jira/browse/CLOUDSTACK-4875>`_"
+msgstr ""
+
+#: ../../about.rst:657
+# 747a8fe507a64ab4ae3ca8f6cfd5993a
+msgid "VMWARE: vCenter 5.5 - SYSTEM VM: Unable to create deployment for VM..."
+msgstr ""
+
+#: ../../about.rst:658
+# 1ad6c1a18ac74f9ca5d950d6ed1d5c0c
+msgid "`CLOUDSTACK-4861 <https://issues.apache.org/jira/browse/CLOUDSTACK-4861>`_"
+msgstr ""
+
+#: ../../about.rst:658
+# 8957176fd07f4c109ea7b0357952fa7b
+msgid "[VMware] If Guest traffic spans across multiple physical networks, selection of ..."
+msgstr ""
+
+#: ../../about.rst:659
+# b5ac3a6c76204ad8a9a7268080c64b49
+msgid "`CLOUDSTACK-4860 <https://issues.apache.org/jira/browse/CLOUDSTACK-4860>`_"
+msgstr ""
+
+#: ../../about.rst:659
+# 37976257934d4487a958e85fa50fc551
+msgid "[VMware] Vcenter 5.5 ESXi 5.5 hosts SSVM CPVM fail to come up to running state..."
+msgstr ""
+
+#: ../../about.rst:660
+# 9cd4d3f685e348f18b8ddf5a934beb28
+msgid "`CLOUDSTACK-4856 <https://issues.apache.org/jira/browse/CLOUDSTACK-4856>`_"
+msgstr ""
+
+#: ../../about.rst:660
+# dc59e549f9c34f5a8460bc55ae67373a
+msgid "Optimize on the # of control commands sent by MS to HV host..."
+msgstr ""
+
+#: ../../about.rst:661
+# 3281238e366244ecb0123297babe660d
+msgid "`CLOUDSTACK-4855 <https://issues.apache.org/jira/browse/CLOUDSTACK-4855>`_"
+msgstr ""
+
+#: ../../about.rst:661
+# 5b4cb016bbae46cb8ff1f3960e6fe0eb
+msgid "Throttle based on the # of outstanding requests to the directly managed HV host ..."
+msgstr ""
+
+#: ../../about.rst:662
+# 42c1986e9f884f6f96efa3330e265dcb
+msgid "`CLOUDSTACK-4852 <https://issues.apache.org/jira/browse/CLOUDSTACK-4852>`_"
+msgstr ""
+
+#: ../../about.rst:662
+# 846be2c7a49f4ae98c1a5b73753cf314
+msgid "Since upgrade to 4.2 only users at the zone-attached domain level can manipulate..."
+msgstr ""
+
+#: ../../about.rst:663
+# 8efb802f4abb4fd48f3f1a19de4aee1e
+msgid "`CLOUDSTACK-4850 <https://issues.apache.org/jira/browse/CLOUDSTACK-4850>`_"
+msgstr ""
+
+#: ../../about.rst:663
+# 5d6b3617c7cb42caa0f701e2e0d38c9e
+msgid "[UCS] using template instead of cloning profile..."
+msgstr ""
+
+#: ../../about.rst:664
+# ab31d5d84b62429dafcbda5ee27859c8
+msgid "`CLOUDSTACK-4831 <https://issues.apache.org/jira/browse/CLOUDSTACK-4831>`_"
+msgstr ""
+
+#: ../../about.rst:664
+# baa83e0f5592429fab4491fad2feb22d
+msgid "Ability for root admin or domain admin to create a network for another user unde..."
+msgstr ""
+
+#: ../../about.rst:665
+# b52b06c6a83646acb6ea1335dd553575
+msgid "`CLOUDSTACK-4830 <https://issues.apache.org/jira/browse/CLOUDSTACK-4830>`_"
+msgstr ""
+
+#: ../../about.rst:665
+# b3f3aee5e5b546c58758169b9ff5c403
+msgid "Allow creation of users and accounts by domain admin in UI..."
+msgstr ""
+
+#: ../../about.rst:666
+# 501a3df6f8e34585b221b1824f047cf1
+msgid "`CLOUDSTACK-4826 <https://issues.apache.org/jira/browse/CLOUDSTACK-4826>`_"
+msgstr ""
+
+#: ../../about.rst:666
+# 189a999bb37b4295958ec024dd7afe19
+msgid "System VMs fail to start..."
+msgstr ""
+
+#: ../../about.rst:667
+# 10f645984ad841c39f942c5541cedb98
+msgid "`CLOUDSTACK-4820 <https://issues.apache.org/jira/browse/CLOUDSTACK-4820>`_"
+msgstr ""
+
+#: ../../about.rst:667
+# cacfcadb7e134c47b6901e101aa71b5f
+msgid "TestVPCNetworkGc.test_01_wait_network_gc netacls are not cleared..."
+msgstr ""
+
+#: ../../about.rst:668
+# 15dc2294ec194ca19884e5f157c54fe4
+msgid "`CLOUDSTACK-4810 <https://issues.apache.org/jira/browse/CLOUDSTACK-4810>`_"
+msgstr ""
+
+#: ../../about.rst:668
+# e333ec5a2a7a4b45a850be2353e42047
+msgid "Enable hypervisor snapshots for CloudStack-managed storage (for XenServer and VM..."
+msgstr ""
+
+#: ../../about.rst:669
+# 48a67622fecd4d56b212eb303217fc29
+msgid "`CLOUDSTACK-4768 <https://issues.apache.org/jira/browse/CLOUDSTACK-4768>`_"
+msgstr ""
+
+#: ../../about.rst:669
+# 750a2810c8b2410caeb179cfdac55331
+msgid "[Automation] Race condition; delete the template and create VM at same time; dep..."
+msgstr ""
+
+#: ../../about.rst:670
+# 211fab9e0d464b588efc4bc6634cd1d7
+msgid "`CLOUDSTACK-4750 <https://issues.apache.org/jira/browse/CLOUDSTACK-4750>`_"
+msgstr ""
+
+#: ../../about.rst:670
+# 8bd6ea66876d4598baa7750dff3a1d3c
+msgid "bond.VLAN mapping in iptables FORWARD chain not created consistently..."
+msgstr ""
+
+#: ../../about.rst:671
+# b639c092953d427ea6530d446dfef07a
+msgid "`CLOUDSTACK-4741 <https://issues.apache.org/jira/browse/CLOUDSTACK-4741>`_"
+msgstr ""
+
+#: ../../about.rst:671
+# 68accc5e76514ef1afeda698a37297ff
+msgid "URL of ImageStore not in proper format for XenServer..."
+msgstr ""
+
+#: ../../about.rst:672
+# 5e8fa3a2ac5d40858b372f0bc4fa8f75
+msgid "`CLOUDSTACK-4740 <https://issues.apache.org/jira/browse/CLOUDSTACK-4740>`_"
+msgstr ""
+
+#: ../../about.rst:672
+# b1f99f7d418642e59644fd4d3c8271a9
+msgid "Some vSphere VMs are shutdown when ACS is restarted..."
+msgstr ""
+
+#: ../../about.rst:673
+# c0e2c47fc85a4c9bb76c4943232f8cfa
+msgid "`CLOUDSTACK-4734 <https://issues.apache.org/jira/browse/CLOUDSTACK-4734>`_"
+msgstr ""
+
+#: ../../about.rst:673
+# 5bf24b93956741eab2801030d5f9841a
+msgid "Creating snapshot from ROOT volume fails with error message - \"Failed to create ..."
+msgstr ""
+
+#: ../../about.rst:674
+# bed7503a00e44110b452dbbf35f399a0
+msgid "`CLOUDSTACK-4724 <https://issues.apache.org/jira/browse/CLOUDSTACK-4724>`_"
+msgstr ""
+
+#: ../../about.rst:674
+# 5d6a1b1bce914e9fba42fa56ca653d74
+msgid "[Vmware] Deploy VM in designated cluster fail if there is only zone wide primary..."
+msgstr ""
+
+#: ../../about.rst:675
+# ada11e5aff404aecabf02b03254c391f
+msgid "`CLOUDSTACK-4697 <https://issues.apache.org/jira/browse/CLOUDSTACK-4697>`_"
+msgstr ""
+
+#: ../../about.rst:675
+# 0a0f8cf524124393992aefaa1c4742ed
+msgid "Not able to delete Primary storage when there are no hosts in the cluster...."
+msgstr ""
+
+#: ../../about.rst:676
+# b2fcbe8c396a4306893bddc2a4d0570e
+msgid "`CLOUDSTACK-4676 <https://issues.apache.org/jira/browse/CLOUDSTACK-4676>`_"
+msgstr ""
+
+#: ../../about.rst:676
+# ac575161189240a1acd5dcf501c06e2f
+msgid "[Baremetal] baremetal hostename should not be fixed in kickstart file ..."
+msgstr ""
+
+#: ../../about.rst:677
+# 54e3f264d08642b6b1fb45681e846b36
+msgid "`CLOUDSTACK-4670 <https://issues.apache.org/jira/browse/CLOUDSTACK-4670>`_"
+msgstr ""
+
+#: ../../about.rst:677
+# 5ecae9795b55428b9c96b3fb7288b939
+msgid "[Baremetal] Cloudplatform BareMetal installation guide for CP 4.2..."
+msgstr ""
+
+#: ../../about.rst:678
+# 126fd296bbe3499198ccdf95aedbc428
+msgid "`CLOUDSTACK-4631 <https://issues.apache.org/jira/browse/CLOUDSTACK-4631>`_"
+msgstr ""
+
+#: ../../about.rst:678
+# 46a50fc4b36446fc9f631831185fb301
+msgid "[Automation] Failed to create snapshot from volume due to storage pool missing e..."
+msgstr ""
+
+#: ../../about.rst:679
+# 379803428c4b40a99d75f9c8ef15f7c7
+msgid "`CLOUDSTACK-4620 <https://issues.apache.org/jira/browse/CLOUDSTACK-4620>`_"
+msgstr ""
+
+#: ../../about.rst:679
+# b8558b1ab0904e8eba3bb334e0eed8fd
+msgid "Vm failed to start on the host on which it was running due to not having enough ..."
+msgstr ""
+
+#: ../../about.rst:680
+# 6fbab8fd7917498d9db231ce8dc2b583
+msgid "`CLOUDSTACK-4616 <https://issues.apache.org/jira/browse/CLOUDSTACK-4616>`_"
+msgstr ""
+
+#: ../../about.rst:680
+# 2185171c4e8a42bc8de280d9aa31805c
+msgid "When system Vms fail to start when host is down , link local Ip addresses do no..."
+msgstr ""
+
+#: ../../about.rst:681
+# 227ffaee42f144d89bb6d7b32bdf03da
+msgid "`CLOUDSTACK-4598 <https://issues.apache.org/jira/browse/CLOUDSTACK-4598>`_"
+msgstr ""
+
+#: ../../about.rst:681
+# 90e454f8ca38449fa4cb287df0cc8e49
+msgid "[Performance Testing] High delays during deployVM - both network delay and deplo..."
+msgstr ""
+
+#: ../../about.rst:682
+# 3bc452f5797d4fb6926eb4cdfdcaafb1
+msgid "`CLOUDSTACK-4597 <https://issues.apache.org/jira/browse/CLOUDSTACK-4597>`_"
+msgstr ""
+
+#: ../../about.rst:682
+# 9c2214fa5635486b859b99215792fcb4
+msgid "Complete Exceptions are getting displayed in the UI where there is an operationa..."
+msgstr ""
+
+#: ../../about.rst:683
+# 39bc028e76114cdf93712edd47d7ba4a
+msgid "`CLOUDSTACK-4594 <https://issues.apache.org/jira/browse/CLOUDSTACK-4594>`_"
+msgstr ""
+
+#: ../../about.rst:683
+# 7fda7fc93c994e63ab06f9107c77e380
+msgid "[VMWARE] [Upgrade] Failed to revert VM Snapshot which were created before Live S..."
+msgstr ""
+
+#: ../../about.rst:684
+# ce278c39e77745e38df99861dc659544
+msgid "`CLOUDSTACK-4588 <https://issues.apache.org/jira/browse/CLOUDSTACK-4588>`_"
+msgstr ""
+
+#: ../../about.rst:684
+# da095652365841459d93cad09d8ff503
+msgid "[Automation][Vmware] VM deployment failed while creating Volume with NPE..."
+msgstr ""
+
+#: ../../about.rst:685
+# 91ae778c89884cae9473ca921fd31448
+msgid "`CLOUDSTACK-4577 <https://issues.apache.org/jira/browse/CLOUDSTACK-4577>`_"
+msgstr ""
+
+#: ../../about.rst:685
+# d026461c2bf7472f809e4890eebaa2e3
+msgid "VMWare:Volumes: Unexpected exception while executing org.apache.cloudstack.api.c..."
+msgstr ""
+
+#: ../../about.rst:686
+# 1d9f253b59e346a0bad4cfef82be0b91
+msgid "`CLOUDSTACK-4543 <https://issues.apache.org/jira/browse/CLOUDSTACK-4543>`_"
+msgstr ""
+
+#: ../../about.rst:686
+# ee92d2c68ebe4efc8b5cb5be24d06b1b
+msgid "[Automation] Failed to configure VPC router then reported as deployment failure..."
+msgstr ""
+
+#: ../../about.rst:687
+# c980a7ff009242b4b767febc23a2bc29
+msgid "`CLOUDSTACK-4542 <https://issues.apache.org/jira/browse/CLOUDSTACK-4542>`_"
+msgstr ""
+
+#: ../../about.rst:687
+# 41554cf693464f1195755a0ade34141a
+msgid "[Automation] Failed to apply DHCP entry in VR and deployment failed ..."
+msgstr ""
+
+#: ../../about.rst:688
+# 47713c22f8a049c5b2a8ab20c89217c8
+msgid "`CLOUDSTACK-4540 <https://issues.apache.org/jira/browse/CLOUDSTACK-4540>`_"
+msgstr ""
+
+#: ../../about.rst:688
+# 5bd94401fa6847eb8c4f65347ed0eeba
+msgid "[Automation] Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 ..."
+msgstr ""
+
+#: ../../about.rst:689
+# cc0aabdbe28b4d41bf04dda2de5eb39c
+msgid "`CLOUDSTACK-4506 <https://issues.apache.org/jira/browse/CLOUDSTACK-4506>`_"
+msgstr ""
+
+#: ../../about.rst:689
+# 42e3822ed11340979a3879ae3186d3f1
+msgid "In a mixed hypervisor setup, destroying a VM whose host has been removed, throws..."
+msgstr ""
+
+#: ../../about.rst:690
+# 8790d47690d549a593aab8cf0e77a252
+msgid "`CLOUDSTACK-4504 <https://issues.apache.org/jira/browse/CLOUDSTACK-4504>`_"
+msgstr ""
+
+#: ../../about.rst:690
+# fd070f755db54e6ca07f29e3ea78ef08
+msgid "VM creation Is failing using the Ubuntu ISO with Xen 6.1 and 6.2..."
+msgstr ""
+
+#: ../../about.rst:691
+# d383c2b9c5e34965b121e3158bc1c9c6
+msgid "`CLOUDSTACK-4450 <https://issues.apache.org/jira/browse/CLOUDSTACK-4450>`_"
+msgstr ""
+
+#: ../../about.rst:691
+# ffe8f57646ef484abc43c7cd361322d4
+msgid "Possibility of /tmp/xapilog filling up the Root disk on Xenserver ..."
+msgstr ""
+
+#: ../../about.rst:692
+# dc5aa1576b0c44e7b5b3ded245bbd6cc
+msgid "`CLOUDSTACK-4445 <https://issues.apache.org/jira/browse/CLOUDSTACK-4445>`_"
+msgstr ""
+
+#: ../../about.rst:692
+# 221dca1539a34554aa084f746d51092c
+msgid "[UI]Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter with ..."
+msgstr ""
+
+#: ../../about.rst:693
+# 05118ddccdf445b5b5edf7344fcd15bb
+msgid "`CLOUDSTACK-4428 <https://issues.apache.org/jira/browse/CLOUDSTACK-4428>`_"
+msgstr ""
+
+#: ../../about.rst:693
+# 77e2ad14b0e54ba482807ec425427645
+msgid "[UI] \"kvm.snapshot.enabled\" flag should be taken to account only when snapshot i..."
+msgstr ""
+
+#: ../../about.rst:694
+# 26b76fe5303649a790ccff43b2c5049f
+msgid "`CLOUDSTACK-4402 <https://issues.apache.org/jira/browse/CLOUDSTACK-4402>`_"
+msgstr ""
+
+#: ../../about.rst:694
+# fe3d5f63a647476c872fd01cf0df19f6
+msgid "[deleteStoragePool] There is no way to delete Primary storage if the last host w..."
+msgstr ""
+
+#: ../../about.rst:695
+# ceb6c277f41143bbb0a1386d5e67013d
+msgid "`CLOUDSTACK-4371 <https://issues.apache.org/jira/browse/CLOUDSTACK-4371>`_"
+msgstr ""
+
+#: ../../about.rst:695
+# f687a03296794550ad49fc92158a9f12
+msgid "[Performance Testing] Basic zone with 20K Hosts, management server restart leave..."
+msgstr ""
+
+#: ../../about.rst:696
+# 11c7794de35044839d3f2258fd73c169
+msgid "`CLOUDSTACK-4263 <https://issues.apache.org/jira/browse/CLOUDSTACK-4263>`_"
+msgstr ""
+
+#: ../../about.rst:696
+# 38b5aeb8acea45e4b64478d6ea6f131e
+msgid "Unable to get git number in maven-jgit-buildnumber-plugin, while build cloudstac..."
+msgstr ""
+
+#: ../../about.rst:697
+# 104b1472320740099883671f2dada31f
+msgid "`CLOUDSTACK-4207 <https://issues.apache.org/jira/browse/CLOUDSTACK-4207>`_"
+msgstr ""
+
+#: ../../about.rst:697
+# 2c9fa169dda640c5a91151935e4330c6
+msgid "[upgrade] Exception observed after upgrade \"jsonParseException: The JsonDeserial..."
+msgstr ""
+
+#: ../../about.rst:698
+# b7503f18923249908d856bc6f328313f
+msgid "`CLOUDSTACK-4061 <https://issues.apache.org/jira/browse/CLOUDSTACK-4061>`_"
+msgstr ""
+
+#: ../../about.rst:698
+# f3af02dae63d4a31bf577266a237d17d
+msgid "UI issue with Japanese localized ui..."
+msgstr ""
+
+#: ../../about.rst:699
+# 5fcd77799e5541bfabddc934a5881b2e
+msgid "`CLOUDSTACK-3806 <https://issues.apache.org/jira/browse/CLOUDSTACK-3806>`_"
+msgstr ""
+
+#: ../../about.rst:699
+# c43319742c0b440d98dda32a5ac2e488
+msgid "OS Preference can not be set..."
+msgstr ""
+
+#: ../../about.rst:700
+# 36bb50dd8a82450b85aea34ec194a3f3
+msgid "`CLOUDSTACK-3664 <https://issues.apache.org/jira/browse/CLOUDSTACK-3664>`_"
+msgstr ""
+
+#: ../../about.rst:700
+# 642b60faf5f246f285267341127b885b
+msgid "scaling up vms is not considering parameter \"cluster.(memory/cpu).allocated.cap..."
+msgstr ""
+
+#: ../../about.rst:701
+# 0cdfd6782a2a42349352de16b1b14d71
+msgid "`CLOUDSTACK-3627 <https://issues.apache.org/jira/browse/CLOUDSTACK-3627>`_"
+msgstr ""
+
+#: ../../about.rst:701
+# 21702dbb9dfc4d31ad95e5e10b83f8a3
+msgid "Public IP interface(eth2) is not getting confugured with Redundant VR (State = F..."
+msgstr ""
+
+#: ../../about.rst:702
+# 86a6e2f6bb0b4c8b96b2fcb8fb032bdb
+msgid "`CLOUDSTACK-3577 <https://issues.apache.org/jira/browse/CLOUDSTACK-3577>`_"
+msgstr ""
+
+#: ../../about.rst:702
+# 85214d0fa632436d8bfeec4da56ac5e4
+msgid "NPE while downloading the template to secondary storage ..."
+msgstr ""
+
+#: ../../about.rst:703
+# 44810451a0644dc68049333d6e74d170
+msgid "`CLOUDSTACK-3561 <https://issues.apache.org/jira/browse/CLOUDSTACK-3561>`_"
+msgstr ""
+
+#: ../../about.rst:703
+# b75310718e66407587d5c43022fa426e
+msgid "When inputting the nfs server in secondary storage, if once it's required, it al..."
+msgstr ""
+
+#: ../../about.rst:704
+# 13465793b3a943c5a9b6bab068d81298
+msgid "`CLOUDSTACK-3364 <https://issues.apache.org/jira/browse/CLOUDSTACK-3364>`_"
+msgstr ""
+
+#: ../../about.rst:704
+# e951699e241d45bc93be24331efebfe5
+msgid "normal users are not allowed to edit their own iso..."
+msgstr ""
+
+#: ../../about.rst:705
+# 8d83e620d6314c1985c3902a9e1f5b5e
+msgid "`CLOUDSTACK-3266 <https://issues.apache.org/jira/browse/CLOUDSTACK-3266>`_"
+msgstr ""
+
+#: ../../about.rst:705
+# 817aae70948640a39786c8eedc403117
+msgid "[UI] Failed to delete Anti affinitygroup for the first time ..."
+msgstr ""
+
+#: ../../about.rst:706
+# c4c3cbb8586249dca78844b418a347c9
+msgid "`CLOUDSTACK-3252 <https://issues.apache.org/jira/browse/CLOUDSTACK-3252>`_"
+msgstr ""
+
+#: ../../about.rst:706
+# d577dce295e7485e9fe076b1e90fecbe
+msgid "An instance deployed using explicit or implicit dedication doesn't generate a us..."
+msgstr ""
+
+#: ../../about.rst:707
+# e9ebded05b404650a0b91a896ee98046
+msgid "`CLOUDSTACK-3247 <https://issues.apache.org/jira/browse/CLOUDSTACK-3247>`_"
+msgstr ""
+
+#: ../../about.rst:707
+# d9ed05f351ab43efa8484648b34711c7
+msgid "Removing a Disconnected Host throws a NoTransitionException..."
+msgstr ""
+
+#: ../../about.rst:708
+# ebc5535f7dda48c18844a74453e6ae04
+msgid "`CLOUDSTACK-3156 <https://issues.apache.org/jira/browse/CLOUDSTACK-3156>`_"
+msgstr ""
+
+#: ../../about.rst:708
+# 2f7c49bb04cb464592521404a6b645b9
+msgid "needs proper message for failing Add nic command when vmware tools is not instal..."
+msgstr ""
+
+#: ../../about.rst:709
+# e589ed802033435d9e06e6d3451ad4ec
+msgid "`CLOUDSTACK-3067 <https://issues.apache.org/jira/browse/CLOUDSTACK-3067>`_"
+msgstr ""
+
+#: ../../about.rst:709
+# c10c09d9e06b422ea42deff9455b7fc4
+msgid "UI for Dedicating POD/Cluster/Host is misleading Icons should be changed...."
+msgstr ""
+
+#: ../../about.rst:710
+# 1776639960384d91be367c192b193f6e
+msgid "`CLOUDSTACK-3027 <https://issues.apache.org/jira/browse/CLOUDSTACK-3027>`_"
+msgstr ""
+
+#: ../../about.rst:710
+# 73e13ff98b4243b9a20b50ee3e376b9f
+msgid "Object_Store_Refactor - Uploaded template S3 content-type is not appropriate...."
+msgstr ""
+
+#: ../../about.rst:711
+# db9ce076437d4ead84b15545ca7f2527
+msgid "`CLOUDSTACK-2895 <https://issues.apache.org/jira/browse/CLOUDSTACK-2895>`_"
+msgstr ""
+
+#: ../../about.rst:711
+# f3ceed3d135a409baff6c790cc95f0bd
+msgid "Can't start a VM with 3 volumes attached [VMWare]..."
+msgstr ""
+
+#: ../../about.rst:712
+# 82dbd781079744aea51f36c468acf383
+msgid "`CLOUDSTACK-2766 <https://issues.apache.org/jira/browse/CLOUDSTACK-2766>`_"
+msgstr ""
+
+#: ../../about.rst:712
+# 4f6db1729af84eac8239cc4010256df9
+msgid "[VPC] [UI] Firewall service should not be enabled for acquired public IPs in VPC..."
+msgstr ""
+
+#: ../../about.rst:713
+# fc408e4e115344aca26337d032f3fe57
+msgid "`CLOUDSTACK-2687 <https://issues.apache.org/jira/browse/CLOUDSTACK-2687>`_"
+msgstr ""
+
+#: ../../about.rst:713
+# 68662c997bd44c23a4752e827db60032
+msgid "NPE with deploy VM when there are no resources available ..."
+msgstr ""
+
+#: ../../about.rst:714
+# 71ae7842ee464e1e922a222d4d70912f
+msgid "`CLOUDSTACK-2570 <https://issues.apache.org/jira/browse/CLOUDSTACK-2570>`_"
+msgstr ""
+
+#: ../../about.rst:714
+# ac9a0771b87d475cb7be48ffedf997d5
+msgid "[UI]Resource Name is mentioned twice with view VNMC devices ..."
+msgstr ""
+
+#: ../../about.rst:715
+# be29600cb4514dfca86f48d41023e49f
+msgid "`CLOUDSTACK-2562 <https://issues.apache.org/jira/browse/CLOUDSTACK-2562>`_"
+msgstr ""
+
+#: ../../about.rst:715
+# 07bc018e1bbc44d9b62178dd206268cf
+msgid "[VMWARE] As per the code, currently CloudStack fails to program PF/NAT/LB rules ..."
+msgstr ""
+
+#: ../../about.rst:716
+# 61203c44c9c644f4adb7afab63a6681a
+msgid "`CLOUDSTACK-2428 <https://issues.apache.org/jira/browse/CLOUDSTACK-2428>`_"
+msgstr ""
+
+#: ../../about.rst:716
+# c06bebf8a33649ed8131f4b65a442741
+msgid "HA - When the master host is disconnected , the host status contines to remain i..."
+msgstr ""
+
+#: ../../about.rst:717
+# 355721da958a498d8ba4b92a004344db
+msgid "`CLOUDSTACK-2414 <https://issues.apache.org/jira/browse/CLOUDSTACK-2414>`_"
+msgstr ""
+
+#: ../../about.rst:717
+# 88df2cdc4cfa47468edc9b0011db7298
+msgid "NPE while deleting Cisco VNMC provider..."
+msgstr ""
+
+#: ../../about.rst:718
+# ca232c6f2a22456986598e306b91d4db
+msgid "`CLOUDSTACK-2396 <https://issues.apache.org/jira/browse/CLOUDSTACK-2396>`_"
+msgstr ""
+
+#: ../../about.rst:718
+# cfb458af8afc43d8a66b6121cc628293
+msgid "PVLAN - Should not be allowed to create multiple networks with same Vlan associ..."
+msgstr ""
+
+#: ../../about.rst:719
+# 585c07df2d5448dcba290de9f271688e
+msgid "`CLOUDSTACK-2199 <https://issues.apache.org/jira/browse/CLOUDSTACK-2199>`_"
+msgstr ""
+
+#: ../../about.rst:719
+# 17e0b4ecc6f1404f9e14a5f686051b7d
+msgid "ID parameter of UpdateConfiguration API should be changed to a different name..."
+msgstr ""
+
+#: ../../about.rst:720
+# 01ea2848fe344d31955cd85d1658efd8
+msgid "`CLOUDSTACK-2141 <https://issues.apache.org/jira/browse/CLOUDSTACK-2141>`_"
+msgstr ""
+
+#: ../../about.rst:720
+# 4dddbbae9d0840a8ad81a2468c62ba78
+msgid "During HA process , dead lock is detected - Caused by: com.mysql.jdbc.exception..."
+msgstr ""
+
+#: ../../about.rst:721
+# f18c12a93f9c4e3e9851653bcfc49b3e
+msgid "`CLOUDSTACK-1970 <https://issues.apache.org/jira/browse/CLOUDSTACK-1970>`_"
+msgstr ""
+
+#: ../../about.rst:721
+# 8ccc99672b1649e9bfaded6c83b00565
+msgid "Ubuntu - \"cloudstack-setup-management\" not available in \"/usr/bin\"..."
+msgstr ""
+
+#: ../../about.rst:722
+# d8920306f36140cba685be0ae0163462
+msgid "`CLOUDSTACK-1889 <https://issues.apache.org/jira/browse/CLOUDSTACK-1889>`_"
+msgstr ""
+
+#: ../../about.rst:722
+# 67849ec4e4cb4e53b9c45a4dac238292
+msgid "[UI] Consumed Resource usage details are not available for all the resources..."
+msgstr ""
+
+#: ../../about.rst:723
+# ab09a0e8aa764bcaa79200afda6dc05d
+msgid "`CLOUDSTACK-1868 <https://issues.apache.org/jira/browse/CLOUDSTACK-1868>`_"
+msgstr ""
+
+#: ../../about.rst:723
+# 6f9698df0b334e868d1afb282f4ab87a
+msgid "GetVmStatsCommand throws NullPointerException with VMWare..."
+msgstr ""
+
+#: ../../about.rst:724
+# 71081f32c5394fa7b58478869ef588fc
+msgid "`CLOUDSTACK-1762 <https://issues.apache.org/jira/browse/CLOUDSTACK-1762>`_"
+msgstr ""
+
+#: ../../about.rst:724
+# 23d1ec5f650849cb995595f6e6023eb9
+msgid "[MultipleIpsToNic] addIpToNic should not let network id or broadcast to be assig..."
+msgstr ""
+
+#: ../../about.rst:725
+# 19fcef90d9ca435e8221328b24e3aab4
+msgid "`CLOUDSTACK-1637 <https://issues.apache.org/jira/browse/CLOUDSTACK-1637>`_"
+msgstr ""
+
+#: ../../about.rst:725
+# a43129b0cd404f2e82d7c5f8347dd8b3
+msgid "LDAP:UI related issues..."
+msgstr ""
+
+#: ../../about.rst:730
+# 71c836e363854cf5b492fd061ccc190d
+msgid "Known Issues in 4.3.0"
+msgstr ""
+
+#: ../../about.rst:735
+# 1b16efacb0eb4285a3fe990c9faf5236
+msgid "For the list of known issues, see `Known Issues in 4.3 <https://issues.apache.org/jira/issues/?filter=12326162>`__."
+msgstr ""
+
+#: ../../about.rst:741
+# 31d47b582cf145fc8e4492a8b291f116
+msgid "`CLOUDSTACK-4787 <https://issues.apache.org/jira/browse/CLOUDSTACK-4787>`_"
+msgstr ""
+
+#: ../../about.rst:741
+# ef129fa6cb3146b1857507d7c5b584d5
+msgid "Allow selection of scsi controller type in vSphere..."
+msgstr ""
+
+#: ../../about.rst:742
+# 50ebe7aaa9984a51b4e50d70c9d2e276
+msgid "`CLOUDSTACK-6024 <https://issues.apache.org/jira/browse/CLOUDSTACK-6024>`_"
+msgstr ""
+
+#: ../../about.rst:742
+# b4a2aa9ac51b4b519f45e8eb31b6f78a
+msgid "template copy to primary storage uses a random source secstorage from any zone..."
+msgstr ""
+
+#: ../../about.rst:743
+# 87963880d9f34d4c97086171a79a5bb5
+msgid "`CLOUDSTACK-4912 <https://issues.apache.org/jira/browse/CLOUDSTACK-4912>`_"
+msgstr ""
+
+#: ../../about.rst:743
+# 5a6f5883d7ad40abbf0a376104ccfe46
+msgid "API docs are missing some APIs..."
+msgstr ""
+
+#: ../../about.rst:744
+# 03b51226028342628f8903906b987f83
+msgid "`CLOUDSTACK-5124 <https://issues.apache.org/jira/browse/CLOUDSTACK-5124>`_"
+msgstr ""
+
+#: ../../about.rst:744
+# b776d2a67285407ab2e5fb605d18dcaa
+msgid "Simulator: Virtual Router fails to start because of improper version returned by..."
+msgstr ""
+
+#: ../../about.rst:745
+# f57fb57c3bd746adb96f77d30648dbe3
+msgid "`CLOUDSTACK-5262 <https://issues.apache.org/jira/browse/CLOUDSTACK-5262>`_"
+msgstr ""
+
+#: ../../about.rst:745
+# 5c72ef3cabcc4a76ab04ed7f1629d305
+msgid "Few of the snapshot creation from ROOT volume fails when there are concurrent s..."
+msgstr ""
+
+#: ../../about.rst:746
+# 865cad9874bd49d995f3835cdecb595d
+msgid "`CLOUDSTACK-5356 <https://issues.apache.org/jira/browse/CLOUDSTACK-5356>`_"
+msgstr ""
+
+#: ../../about.rst:746
+# b1e9e358f4d445b58cbf4f657528529c
+msgid "Xenserver - Failed to create snapshot when secondary store was made unavaibale f..."
+msgstr ""
+
+#: ../../about.rst:747
+# c726e0ed500e495192a32edb5f10f224
+msgid "`CLOUDSTACK-5357 <https://issues.apache.org/jira/browse/CLOUDSTACK-5357>`_"
+msgstr ""
+
+#: ../../about.rst:747
+# cb17e1a2a4c1497493142c62b294c29d
+msgid "Xenserver - Failed to create snapshot due to \"unable to destroy task(com.xe nsou..."
+msgstr ""
+
+#: ../../about.rst:748
+# 36992a81b47943f29ffb24dfca04b284
+msgid "`CLOUDSTACK-5358 <https://issues.apache.org/jira/browse/CLOUDSTACK-5358>`_"
+msgstr ""
+
+#: ../../about.rst:748
+# 809afb2c1a5a4e8e834545fdecd809e0
+msgid "API: synchronization on the object is broken..."
+msgstr ""
+
+#: ../../about.rst:749
+# e9ba91dc614643a6b8f4ad800d78b8d5
+msgid "`CLOUDSTACK-5372 <https://issues.apache.org/jira/browse/CLOUDSTACK-5372>`_"
+msgstr ""
+
+#: ../../about.rst:749
+# a12de4d7e892479d9b85f53620897771
+msgid "Xenserver - SR not being recreated when the Primary storage is brought down and ..."
+msgstr ""
+
+#: ../../about.rst:750
+# 242006f64cba438995e2a4751cc8074c
+msgid "`CLOUDSTACK-5429 <https://issues.apache.org/jira/browse/CLOUDSTACK-5429>`_"
+msgstr ""
+
+#: ../../about.rst:750
+# d44d2dfe655b4b60aacd9383de18bf54
+msgid "KVM - Primary store down/Network Failure - Hosts attempt to reboot becasue of pr..."
+msgstr ""
+
+#: ../../about.rst:751
+# 5a67b815905b45faa0786948f1f40a16
+msgid "`CLOUDSTACK-5452 <https://issues.apache.org/jira/browse/CLOUDSTACK-5452>`_"
+msgstr ""
+
+#: ../../about.rst:751
+# 07aad5722c294ceca2d20ff07b9b3d55
+msgid "KVM - Agent is not able to connect back if management server was restarted when ..."
+msgstr ""
+
+#: ../../about.rst:752
+# c469ca03b2d441cf9f2b89a9ad0fd256
+msgid "`CLOUDSTACK-5469 <https://issues.apache.org/jira/browse/CLOUDSTACK-5469>`_"
+msgstr ""
+
+#: ../../about.rst:752
+# 5fc31df43299472b90b99fd450381f27
+msgid "Snapshot creation fails with following exception - \"Failed to backup snapshot: q..."
+msgstr ""
+
+#: ../../about.rst:753
+# ee69b35e9a104e15af05fed03f16bfd6
+msgid "`CLOUDSTACK-5485 <https://issues.apache.org/jira/browse/CLOUDSTACK-5485>`_"
+msgstr ""
+
+#: ../../about.rst:753
+# 6c11592ff2d042b39f286026a49b57fa
+msgid "Vmware - Whe 10 hourly snapshots are scheduled at the same time , we see only 5 ..."
+msgstr ""
+
+#: ../../about.rst:754
+# 812196063f1e4c48b18e33d9e082fdd5
+msgid "`CLOUDSTACK-5494 <https://issues.apache.org/jira/browse/CLOUDSTACK-5494>`_"
+msgstr ""
+
+#: ../../about.rst:754
+# 8634a982a6a241608c9c0041c466b319
+msgid "the dns resolver servers on the VRs are open to the world..."
+msgstr ""
+
+#: ../../about.rst:755
+# 495c1be268f445c1b8d4818f81b9a3e2
+msgid "`CLOUDSTACK-5499 <https://issues.apache.org/jira/browse/CLOUDSTACK-5499>`_"
+msgstr ""
+
+#: ../../about.rst:755
+# 33cbbaaae77946e7a820cdc7d3a2a40a
+msgid "Vmware -When nfs was down for about 12 hours and then brought back up again , s..."
+msgstr ""
+
+#: ../../about.rst:756
+# 9dbd38304a7246adbccd0c72b9fffbef
+msgid "`CLOUDSTACK-5501 <https://issues.apache.org/jira/browse/CLOUDSTACK-5501>`_"
+msgstr ""
+
+#: ../../about.rst:756
+# fd1a637684f64104b0306facc294dd5c
+msgid "Unable to create more than one vpnConnection per vpn customer gateway..."
+msgstr ""
+
+#: ../../about.rst:757
+# 8c0d9bb0c8434e33b618102c0d54d14f
+msgid "`CLOUDSTACK-5582 <https://issues.apache.org/jira/browse/CLOUDSTACK-5582>`_"
+msgstr ""
+
+#: ../../about.rst:757
+# 7b80352fe2c74d488a4f1e2464276657
+msgid "kvm - HA is not triggered when host is powered down since the host gets into \"Di..."
+msgstr ""
+
+#: ../../about.rst:758
+# 783f8812c4484c618f51d34b26c7a473
+msgid "`CLOUDSTACK-5746 <https://issues.apache.org/jira/browse/CLOUDSTACK-5746>`_"
+msgstr ""
+
+#: ../../about.rst:758
+# 36954ba31b6b46ef9cd2e53529f59f8b
+msgid "[HyperV]Can't access vm console from IE browser..."
+msgstr ""
+
+#: ../../about.rst:759
+# 0553b5764c5548f096edcec2ede64189
+msgid "`CLOUDSTACK-5806 <https://issues.apache.org/jira/browse/CLOUDSTACK-5806>`_"
+msgstr ""
+
+#: ../../about.rst:759
+# e3358df3595e46f89d0e9e178040e051
+msgid "Storage types other than NFS/VMFS can't overprovision..."
+msgstr ""
+
+#: ../../about.rst:760
+# d7ee8f91e0274d89a09eb32b2a3fe162
+msgid "`CLOUDSTACK-5818 <https://issues.apache.org/jira/browse/CLOUDSTACK-5818>`_"
+msgstr ""
+
+#: ../../about.rst:760
+# c4afd7c1057b4a02a51318811dd0604f
+msgid "[Hyper-v]Agent status of the System VMs is not updated during Host disconnect..."
+msgstr ""
+
+#: ../../about.rst:761
+# 677a4b4cd4a04c63a7ab351992c54168
+msgid "`CLOUDSTACK-5825 <https://issues.apache.org/jira/browse/CLOUDSTACK-5825>`_"
+msgstr ""
+
+#: ../../about.rst:761
+# e87b7183c08d4bd9a79801ea0bb14a4a
+msgid "Create snapshot API always returns success..."
+msgstr ""
+
+#: ../../about.rst:762
+# 72e75f9805fd435b9ccd058b65bd54b4
+msgid "`CLOUDSTACK-5882 <https://issues.apache.org/jira/browse/CLOUDSTACK-5882>`_"
+msgstr ""
+
+#: ../../about.rst:762
+# 19fd2a4d5ae64d869733b5e0338c4ff1
+msgid "UI has different fonts and font sizes..."
+msgstr ""
+
+#: ../../about.rst:763
+# 247f7ef2aa90421694ad2b6c90f47332
+msgid "`CLOUDSTACK-5899 <https://issues.apache.org/jira/browse/CLOUDSTACK-5899>`_"
+msgstr ""
+
+#: ../../about.rst:763
+# 16fd252ccb144331b12e9bcd4c31b313
+msgid "Contrail:MS: Exceptions in MS logs on a fresh install, syncDomain java.lang.Nul..."
+msgstr ""
+
+#: ../../about.rst:764
+# 4ee5ee9fdfd94d5c88540dfb3886aa40
+msgid "`CLOUDSTACK-5928 <https://issues.apache.org/jira/browse/CLOUDSTACK-5928>`_"
+msgstr ""
+
+#: ../../about.rst:764
+# 292cea71244743b88b5e16bcb8925980
+msgid "[VM Sync] - Vmware - When a Vm is \"suspended\" from outside of CloudStack , this ..."
+msgstr ""
+
+#: ../../about.rst:765
+# 5ef4783f7eeb40c9bacacb4919ca82d0
+msgid "`CLOUDSTACK-5929 <https://issues.apache.org/jira/browse/CLOUDSTACK-5929>`_"
+msgstr ""
+
+#: ../../about.rst:765
+# d2f17d37363c4cc7b2851b114418ce92
+msgid "[VM Sync] - Vmware - Even when starting Vm fails, startVirtualMachine async job ..."
+msgstr ""
+
+#: ../../about.rst:766
+# 76fd33bc1154489d975d3abe31affcbf
+msgid "`CLOUDSTACK-5961 <https://issues.apache.org/jira/browse/CLOUDSTACK-5961>`_"
+msgstr ""
+
+#: ../../about.rst:766
+# eb3e836316be4139853918f4ffb63f5d
+msgid "CLONE - API: synchronization on the object is broken..."
+msgstr ""
+
+#: ../../about.rst:767
+# 25ce75c7373d4ca38c31e02205c65ec0
+msgid "`CLOUDSTACK-6050 <https://issues.apache.org/jira/browse/CLOUDSTACK-6050>`_"
+msgstr ""
+
+#: ../../about.rst:767
+# b8ccec7515b84034957aebe65d722c06
+msgid "A limitations on min-max on CPU/RAM for a dynamic offering ..."
+msgstr ""
+
+#: ../../about.rst:768
+# edb163afa7a7435b951c440f1eb8adaa
+msgid "`CLOUDSTACK-6051 <https://issues.apache.org/jira/browse/CLOUDSTACK-6051>`_"
+msgstr ""
+
+#: ../../about.rst:768
+# 3979450b6d8a45adb4a307a9f78e6d1d
+msgid "VR Rolling upgrade: Make the numbers of Routers parallely being upgraded as conf..."
+msgstr ""
+
+#: ../../about.rst:769
+# 0add0d8647da48d98e1f752ad5e5ebd8
+msgid "`CLOUDSTACK-6063 <https://issues.apache.org/jira/browse/CLOUDSTACK-6063>`_"
+msgstr ""
+
+#: ../../about.rst:769
+# 3e818949eac24ce6a0d3d2a030e78bb7
+msgid "CLONE - Non windows instances are created on XenServer with a vcpu-max above sup..."
+msgstr ""
+
+#: ../../about.rst:770
+# 720f854db96746c5a47da9f9ca9bb92a
+msgid "`CLOUDSTACK-6065 <https://issues.apache.org/jira/browse/CLOUDSTACK-6065>`_"
+msgstr ""
+
+#: ../../about.rst:770
+# 50f80b81c959495bb215a273eb93476b
+msgid "No HA for shutdown VM..."
+msgstr ""
+
+#: ../../about.rst:771
+# 34c7e3458c7c49c19e4573ea105a6967
+msgid "`CLOUDSTACK-6079 <https://issues.apache.org/jira/browse/CLOUDSTACK-6079>`_"
+msgstr ""
+
+#: ../../about.rst:771
+# 2f08609fa26b4764868788499ef7e020
+msgid "a broadcast type of a public network is affected by another physical network's i..."
+msgstr ""
+
+#: ../../about.rst:772
+# 3e8bba76ffb3402f854a35dcdd022d8f
+msgid "`CLOUDSTACK-77 <https://issues.apache.org/jira/browse/CLOUDSTACK-77>`_"
+msgstr ""
+
+#: ../../about.rst:772
+# 0f4c1b5bcfc14ab48ca576b42e6493af
+msgid "console proxy display issues..."
+msgstr ""
+
+#: ../../about.rst:773
+# 3365fe9795b34909870583163db215f6
+msgid "`CLOUDSTACK-107 <https://issues.apache.org/jira/browse/CLOUDSTACK-107>`_"
+msgstr ""
+
+#: ../../about.rst:773
+# 486188c703b64696806a1a86bfaf8188
+msgid "Network domain guest suffix is not getting programmed as part of hostnames on Gu..."
+msgstr ""
+
+#: ../../about.rst:774
+# 994f5cbe376840d2ae02fa5953409ed4
+msgid "`CLOUDSTACK-237 <https://issues.apache.org/jira/browse/CLOUDSTACK-237>`_"
+msgstr ""
+
+#: ../../about.rst:774
+# c73ee41ff6a643bb9db3648b8008b46c
+msgid "StopVMCommand reported success in spite of failing to stop a VM which got stuck ..."
+msgstr ""
+
+#: ../../about.rst:775
+# 83494e97fca7463885f04bb064098114
+msgid "`CLOUDSTACK-238 <https://issues.apache.org/jira/browse/CLOUDSTACK-238>`_"
+msgstr ""
+
+#: ../../about.rst:775
+# 1d5f73907f4f40fca7062368bc77acf3
+msgid "vpn:fail to connect to vpnserver using non-sourceNAT IP..."
+msgstr ""
+
+#: ../../about.rst:776
+# 8b883cfbd306436eb833afa800881c9b
+msgid "`CLOUDSTACK-252 <https://issues.apache.org/jira/browse/CLOUDSTACK-252>`_"
+msgstr ""
+
+#: ../../about.rst:776
+# 661901dc6f95475c99a173229d502de9
+msgid "UpdateNetwork Operation on a guest network that is currently using Virtual Route..."
+msgstr ""
+
+#: ../../about.rst:777
+# 88cead594e484ee89ffb6a431087da73
+msgid "`CLOUDSTACK-255 <https://issues.apache.org/jira/browse/CLOUDSTACK-255>`_"
+msgstr ""
+
+#: ../../about.rst:777
+# 953fe31bcf574f6da002fb0eda9829b0
+msgid "Null pointer exception while creating portforwarding rule after performing Updat..."
+msgstr ""
+
+#: ../../about.rst:778
+# d04f44859ed84287b2bbb0f5a2a02fd4
+msgid "`CLOUDSTACK-317 <https://issues.apache.org/jira/browse/CLOUDSTACK-317>`_"
+msgstr ""
+
+#: ../../about.rst:778
+# 9e1e272cd50c4c83ab11fc0068786418
+msgid "get xcp 1.5 into an advanced network zone..."
+msgstr ""
+
+#: ../../about.rst:779
+# bb6eee8040694156baa0f1cd892cfaa2
+msgid "`CLOUDSTACK-375 <https://issues.apache.org/jira/browse/CLOUDSTACK-375>`_"
+msgstr ""
+
+#: ../../about.rst:779
+# fdf3e49a3cb44de28cfeea786a577df3
+msgid "Unable to delete physical network - because there are other networks attached..."
+msgstr ""
+
+#: ../../about.rst:780
+# a1acc70725b24b1e8b2ddab9bd5f0f92
+msgid "`CLOUDSTACK-425 <https://issues.apache.org/jira/browse/CLOUDSTACK-425>`_"
+msgstr ""
+
+#: ../../about.rst:780
+# 2d04ce4728174183b509e742f7071363
+msgid "Check image type is qcow2 before actually installing..."
+msgstr ""
+
+#: ../../about.rst:781
+# d6ecb5b847b141468224a8b22b441114
+msgid "`CLOUDSTACK-992 <https://issues.apache.org/jira/browse/CLOUDSTACK-992>`_"
+msgstr ""
+
+#: ../../about.rst:781
+# daeacb38cd054fd6adfc01a375a85f4d
+msgid "Template creations dies after 2h for no reason..."
+msgstr ""
+
+#: ../../about.rst:782
+# 38316ccdc679458e8c4b44503d897aa3
+msgid "`CLOUDSTACK-1007 <https://issues.apache.org/jira/browse/CLOUDSTACK-1007>`_"
+msgstr ""
+
+#: ../../about.rst:782
+# 61e6cf53ab794c55875f4862b57a3e85
+msgid "Not able to delete Shared network because of not being able to stop the router...."
+msgstr ""
+
+#: ../../about.rst:783
+# c7f801984bf74320b773fe0ad72c3a08
+msgid "`CLOUDSTACK-1091 <https://issues.apache.org/jira/browse/CLOUDSTACK-1091>`_"
+msgstr ""
+
+#: ../../about.rst:783
+# 5d93525d930c49a68eacc663e993da2b
+msgid "Fix API server's parsing mechanism for POST requests..."
+msgstr ""
+
+#: ../../about.rst:784
+# cdd49d3ca6d14a83ae2d4efd2458de9c
+msgid "`CLOUDSTACK-1092 <https://issues.apache.org/jira/browse/CLOUDSTACK-1092>`_"
+msgstr ""
+
+#: ../../about.rst:784
+# 878923cf4ccf40bfb78945d5a54c7226
+msgid "Fix API Server's parsing mechanism to parse GET request as multimap..."
+msgstr ""
+
+#: ../../about.rst:785
+# d9c36379acf9481eaa72f886e2d85d04
+msgid "`CLOUDSTACK-1309 <https://issues.apache.org/jira/browse/CLOUDSTACK-1309>`_"
+msgstr ""
+
+#: ../../about.rst:785
+# 33df291795b74b03ad9bab5e09db2801
+msgid "Large guest subnets downgrade performance..."
+msgstr ""
+
+#: ../../about.rst:786
+# 6fd8714ddad04fc7aefb4b95240c313f
+msgid "`CLOUDSTACK-1389 <https://issues.apache.org/jira/browse/CLOUDSTACK-1389>`_"
+msgstr ""
+
+#: ../../about.rst:786
+# d9197701267548ae99ea1aeaf1c10a18
+msgid "Interactive Password Prompts during Management Server Startup..."
+msgstr ""
+
+#: ../../about.rst:787
+# a4910348aa8546fc81ca2976dcf5ae70
+msgid "`CLOUDSTACK-1413 <https://issues.apache.org/jira/browse/CLOUDSTACK-1413>`_"
+msgstr ""
+
+#: ../../about.rst:787
+# a55911b4455e4dac80c71f3a74ce3f07
+msgid "Need something to concretely identify the version of the code in a particular bu..."
+msgstr ""
+
+#: ../../about.rst:788
+# e1c49f8c562445719ba551cb19c8bddc
+msgid "`CLOUDSTACK-1527 <https://issues.apache.org/jira/browse/CLOUDSTACK-1527>`_"
+msgstr ""
+
+#: ../../about.rst:788
+# 0228182ddaf24ea7a63474da106be626
+msgid "Non-fatal POSTIN scriptlet failure in rpm package cloudstack-management-4.2.0-SN..."
+msgstr ""
+
+#: ../../about.rst:789
+# 864cd6c21f814c459a9a3f0d18ea9500
+msgid "`CLOUDSTACK-1717 <https://issues.apache.org/jira/browse/CLOUDSTACK-1717>`_"
+msgstr ""
+
+#: ../../about.rst:789
+# 1a0044e05ad7401aa9b78b5a82a38192
+msgid "AWS Regions - Local region entry that gets added by default should not include \"..."
+msgstr ""
+
+#: ../../about.rst:790
+# e8cd251bcc6d4c379f0736aa46129bbe
+msgid "`CLOUDSTACK-1885 <https://issues.apache.org/jira/browse/CLOUDSTACK-1885>`_"
+msgstr ""
+
+#: ../../about.rst:790
+# 694628719d7145628aedbc499609a966
+msgid "Broken testcases in 4.1..."
+msgstr ""
+
+#: ../../about.rst:791
+# 7515997e2a7f413f80d330d8a0e0fa9e
+msgid "`CLOUDSTACK-1990 <https://issues.apache.org/jira/browse/CLOUDSTACK-1990>`_"
+msgstr ""
+
+#: ../../about.rst:791
+# cb1d24a891854529a3ec234b0d44e143
+msgid "Docs: Update \"Choosing a Hypervisor\" feature matrix with new info..."
+msgstr ""
+
+#: ../../about.rst:792
+# 0e015d29cbf1478fb5d4362bd9c9a49c
+msgid "`CLOUDSTACK-2004 <https://issues.apache.org/jira/browse/CLOUDSTACK-2004>`_"
+msgstr ""
+
+#: ../../about.rst:792
+# 8ead7e56bda24b15b373057319d52ec0
+msgid "IPV6 - UI - Router details page - NICs tab - Guest traffic type does not displa..."
+msgstr ""
+
+#: ../../about.rst:793
+# 182bad5646834f53a01d33b9a1024a67
+msgid "`CLOUDSTACK-2009 <https://issues.apache.org/jira/browse/CLOUDSTACK-2009>`_"
+msgstr ""
+
+#: ../../about.rst:793
+# d2bcbe2e6d66493aab159ea738344281
+msgid "IPV6 - listNetwork() command does not return ip6dns1 and ip6dns2 entries...."
+msgstr ""
+
+#: ../../about.rst:794
+# 8bdf10c82eb6496d8fbbd4e18f864519
+msgid "`CLOUDSTACK-2022 <https://issues.apache.org/jira/browse/CLOUDSTACK-2022>`_"
+msgstr ""
+
+#: ../../about.rst:794
+# 281659dd94f447ab89811c990e83746e
+msgid "IPV6 - ListRouter() should return guestip6address parameter similar to guestaddr..."
+msgstr ""
+
+#: ../../about.rst:795
+# 1e8b51b1d53a454a8ca390a0297a01dd
+msgid "`CLOUDSTACK-2023 <https://issues.apache.org/jira/browse/CLOUDSTACK-2023>`_"
+msgstr ""
+
+#: ../../about.rst:795
+# b10aa54c02b043838ee7d2c646017e85
+msgid "IPV6 - Dashboard View - System wide Capacity for Shared Network IPs does not inc..."
+msgstr ""
+
+#: ../../about.rst:796
+# 22f167a09c0c4e0f9f59b8a68f2ee654
+msgid "`CLOUDSTACK-2026 <https://issues.apache.org/jira/browse/CLOUDSTACK-2026>`_"
+msgstr ""
+
+#: ../../about.rst:796
+# 009ae683f400491fb6b1488a79994f26
+msgid "IPV6 - UI - Provide the ability to turn off all the IPV6 parameters by using a g..."
+msgstr ""
+
+#: ../../about.rst:797
+# cb6a5a34bfd341669546708c9119f3d5
+msgid "`CLOUDSTACK-2099 <https://issues.apache.org/jira/browse/CLOUDSTACK-2099>`_"
+msgstr ""
+
+#: ../../about.rst:797
+# 9f2cc504258748d182ed67ac3081057c
+msgid "Not able to add a host after a failed attempt to add the host to a wrong cluster..."
+msgstr ""
+
+#: ../../about.rst:798
+# 3f141bf7fe7445f19888de01c3aa6ba5
+msgid "`CLOUDSTACK-2112 <https://issues.apache.org/jira/browse/CLOUDSTACK-2112>`_"
+msgstr ""
+
+#: ../../about.rst:798
+# f6f310af0449450d87cdd0a210fdb0de
+msgid "VM went in stopped state after live migration failed while vmscaleup..."
+msgstr ""
+
+#: ../../about.rst:799
+# d3d65c8d21b84f9d8c30ff44d359665a
+msgid "`CLOUDSTACK-2191 <https://issues.apache.org/jira/browse/CLOUDSTACK-2191>`_"
+msgstr ""
+
+#: ../../about.rst:799
+# b718e77dad2d4d70b5ccdf6481a0f2e2
+msgid "sanity tests for \"EIP : Optional public IP\" changes ..."
+msgstr ""
+
+#: ../../about.rst:800
+# 0c16e6776c314ce19cb0b493768ee7da
+msgid "`CLOUDSTACK-2291 <https://issues.apache.org/jira/browse/CLOUDSTACK-2291>`_"
+msgstr ""
+
+#: ../../about.rst:800
+# 5369f4749beb456180f8567cc47c0a64
+msgid "[BasicZone-XenServer] NPE while trying DeleteNetworkCmd..."
+msgstr ""
+
+#: ../../about.rst:801
+# cfbcaf313e0040ada9c9ae72834c0456
+msgid "`CLOUDSTACK-2293 <https://issues.apache.org/jira/browse/CLOUDSTACK-2293>`_"
+msgstr ""
+
+#: ../../about.rst:801
+# fe6538720b324d7fa3bd6ee56bb415db
+msgid "[BasicZone-XenServer] DeletePhysicalNetworkCmd is not deleting the external devi..."
+msgstr ""
+
+#: ../../about.rst:802
+# 19ce524dca9b4b5fbebe8c77e6dc485d
+msgid "`CLOUDSTACK-2412 <https://issues.apache.org/jira/browse/CLOUDSTACK-2412>`_"
+msgstr ""
+
+#: ../../about.rst:802
+# e690d342afc54f69a90ab070bb65b3b1
+msgid "[UI]Disable CiscoVnmc provider for PF/SourceNat/StaticNAT/Firewall dropdown list..."
+msgstr ""
+
+#: ../../about.rst:803
+# ad9cf8f340b34dfe99003df89c673bde
+msgid "`CLOUDSTACK-2418 <https://issues.apache.org/jira/browse/CLOUDSTACK-2418>`_"
+msgstr ""
+
+#: ../../about.rst:803
+# a084e2d66028435e808e334df768f7b1
+msgid "[GSLB] NPE while removing the GSLB enabled Netscaler device..."
+msgstr ""
+
+#: ../../about.rst:804
+# a7edeaba8ea5402091f7ac2d5746244a
+msgid "`CLOUDSTACK-2471 <https://issues.apache.org/jira/browse/CLOUDSTACK-2471>`_"
+msgstr ""
+
+#: ../../about.rst:804
+# 55fe809fb167495bb2dff8be76b93a0a
+msgid "test_host_high_availability.py refers to non-existent library method wait_for_vm..."
+msgstr ""
+
+#: ../../about.rst:805
+# cc41be7d4b0a4b93a6e967d08c5828ab
+msgid "`CLOUDSTACK-2501 <https://issues.apache.org/jira/browse/CLOUDSTACK-2501>`_"
+msgstr ""
+
+#: ../../about.rst:805
+# fc6042d3a4124e0fb977723466b9b649
+msgid "Scalevm - Need to take care of upgraded vms..."
+msgstr ""
+
+#: ../../about.rst:806
+# fbf8b9d297254a44af85b4ad0842ed76
+msgid "`CLOUDSTACK-2790 <https://issues.apache.org/jira/browse/CLOUDSTACK-2790>`_"
+msgstr ""
+
+#: ../../about.rst:806
+# ff03767769eb44ecb3a56532519d227a
+msgid "AWSAPI: packaging includes all .class files bloating size of the RPM..."
+msgstr ""
+
+#: ../../about.rst:807
+# c19f028510d04cc28bfcc5b751d5e3d2
+msgid "`CLOUDSTACK-2795 <https://issues.apache.org/jira/browse/CLOUDSTACK-2795>`_"
+msgstr ""
+
+#: ../../about.rst:807
+# c6229aa4fa8e4d8eb9c3721fdd4ebefa
+msgid "Create template failed..."
+msgstr ""
+
+#: ../../about.rst:808
+# cf5c8f8d78d446059ec5f4f3fed761eb
+msgid "`CLOUDSTACK-2845 <https://issues.apache.org/jira/browse/CLOUDSTACK-2845>`_"
+msgstr ""
+
+#: ../../about.rst:808
+# 37593b03408f427aa7de5a29a3748a9f
+msgid "[DB upgrade] [ExternalLoadBalancer NetworkUsage] Duplicate entries in the databa..."
+msgstr ""
+
+#: ../../about.rst:809
+# c020d1432c6d4c4fb0e6f6b4e5cd1bc4
+msgid "`CLOUDSTACK-2853 <https://issues.apache.org/jira/browse/CLOUDSTACK-2853>`_"
+msgstr ""
+
+#: ../../about.rst:809
+# 4f1e62857eb24e02bcb12508a788902d
+msgid "Cloudstack copies xenserver scripts while adding host even the server is KVM hos..."
+msgstr ""
+
+#: ../../about.rst:810
+# 1f3a582d8a534e73bf6e5c5b2955fb42
+msgid "`CLOUDSTACK-2860 <https://issues.apache.org/jira/browse/CLOUDSTACK-2860>`_"
+msgstr ""
+
+#: ../../about.rst:810
+# d520cc0ec5e94254a5e872f670506b50
+msgid "Add new host into VMWare Cluster failed..."
+msgstr ""
+
+#: ../../about.rst:811
+# cf603d42174143a788458e386ef792e6
+msgid "`CLOUDSTACK-2910 <https://issues.apache.org/jira/browse/CLOUDSTACK-2910>`_"
+msgstr ""
+
+#: ../../about.rst:811
+# c4f453abc31c4760b0de34cd22a0a842
+msgid "SC: Ctrl combinated with >. is not working of SC IME..."
+msgstr ""
+
+#: ../../about.rst:812
+# 57433b88f491415d8a3b3a0557e62e90
+msgid "`CLOUDSTACK-2911 <https://issues.apache.org/jira/browse/CLOUDSTACK-2911>`_"
+msgstr ""
+
+#: ../../about.rst:812
+# c2891aaa96d045f59fdc65bf0ec4c6b6
+msgid "KO: Key translation fails for KO keyboard Right Alt, Han/Eng, Hanja keys..."
+msgstr ""
+
+#: ../../about.rst:813
+# 20c6aa92e5e64bfdbbba9b9873593e6a
+msgid "`CLOUDSTACK-2919 <https://issues.apache.org/jira/browse/CLOUDSTACK-2919>`_"
+msgstr ""
+
+#: ../../about.rst:813
+# 730d2192fd4c480a9ba6ae4dc725c6f7
+msgid "Snapshot cannot be saved to full Secondary Storage, but doesn't utilize other Se..."
+msgstr ""
+
+#: ../../about.rst:814
+# fd7d4be76aad4992a084ee3c9b87316a
+msgid "`CLOUDSTACK-3066 <https://issues.apache.org/jira/browse/CLOUDSTACK-3066>`_"
+msgstr ""
+
+#: ../../about.rst:814
+# a7da0f1a26c54809b0d5050d00edba7c
+msgid "No Error message is popped up on UI when a dedicated resource is dedicated to an..."
+msgstr ""
+
+#: ../../about.rst:815
+# 19fee5eea48c419591b66b59ff3ca932
+msgid "`CLOUDSTACK-3095 <https://issues.apache.org/jira/browse/CLOUDSTACK-3095>`_"
+msgstr ""
+
+#: ../../about.rst:815
+# ad934f739e5b48aaa189bb5006e06667
+msgid "[UI][API]Able to add multiple tier networks to a deployed VM using “Add network”..."
+msgstr ""
+
+#: ../../about.rst:816
+# 1685d66996f24e2c9ac9749ada0c337b
+msgid "`CLOUDSTACK-3111 <https://issues.apache.org/jira/browse/CLOUDSTACK-3111>`_"
+msgstr ""
+
+#: ../../about.rst:816
+# 90300713d7a94be9b4a53a3cbeaf9fb3
+msgid "[UI] Storage tab is not showing the Hypervisor column as 'KVM' if the (root/data..."
+msgstr ""
+
+#: ../../about.rst:817
+# ffd4f821bc2943d2930d9af2c49845de
+msgid "`CLOUDSTACK-3186 <https://issues.apache.org/jira/browse/CLOUDSTACK-3186>`_"
+msgstr ""
+
+#: ../../about.rst:817
+# 40c67476c65141a384d19d5e91ebe8e2
+msgid "Duplicate entries in /etc/hosts file on VR after reboot..."
+msgstr ""
+
+#: ../../about.rst:818
+# 86a63899c98d4540b236af83fc53bcd8
+msgid "`CLOUDSTACK-3195 <https://issues.apache.org/jira/browse/CLOUDSTACK-3195>`_"
+msgstr ""
+
+#: ../../about.rst:818
+# a5d3b451f9e74a57994918f6196c038d
+msgid "cannot view/delete forward rules if underlying/target VM is destroyed first..."
+msgstr ""
+
+#: ../../about.rst:819
+# 6316b885181e4a6db59dd7a61d848af6
+msgid "`CLOUDSTACK-3197 <https://issues.apache.org/jira/browse/CLOUDSTACK-3197>`_"
+msgstr ""
+
+#: ../../about.rst:819
+# 9a68d9f3dded4c1fb613689212157f70
+msgid "UI: NTier: User is required to scroll down every single time to \"Create Network\"..."
+msgstr ""
+
+#: ../../about.rst:820
+# 37f216e52aa64ea3b056df50d30772dd
+msgid "`CLOUDSTACK-3212 <https://issues.apache.org/jira/browse/CLOUDSTACK-3212>`_"
+msgstr ""
+
+#: ../../about.rst:820
+# a03c118709644f8a873dd08ae8d2ecab
+msgid "[Advanced_With_SG]View IP Address Range in Default Guest Network page does not s..."
+msgstr ""
+
+#: ../../about.rst:821
+# 91d455d686d74e8a84d45acd20e37a38
+msgid "`CLOUDSTACK-3272 <https://issues.apache.org/jira/browse/CLOUDSTACK-3272>`_"
+msgstr ""
+
+#: ../../about.rst:821
+# 7d38aaa3e47c41f48e72a98ff6af02ac
+msgid "EventBus: add global config parameters to specify which category of events are p..."
+msgstr ""
+
+#: ../../about.rst:822
+# 99ae405f44074d508e663c61adc5e2fe
+msgid "`CLOUDSTACK-3338 <https://issues.apache.org/jira/browse/CLOUDSTACK-3338>`_"
+msgstr ""
+
+#: ../../about.rst:822
+# 2d4b8aba24aa42c48845921942823f32
+msgid "Please provide an icon for \"assignVMs\" action in internal LB rule detailView..."
+msgstr ""
+
+#: ../../about.rst:823
+# 24213f8f87694830a5969b7396aba336
+msgid "`CLOUDSTACK-3518 <https://issues.apache.org/jira/browse/CLOUDSTACK-3518>`_"
+msgstr ""
+
+#: ../../about.rst:823
+# 345de226be3d4fbfbb1fdc2c36df5b57
+msgid "G11n: JA,SC: Un translation issue occurred on the strings of different UI Specif..."
+msgstr ""
+
+#: ../../about.rst:824
+# 0cad2b157e0643d4b095f8e42ede3653
+msgid "`CLOUDSTACK-3519 <https://issues.apache.org/jira/browse/CLOUDSTACK-3519>`_"
+msgstr ""
+
+#: ../../about.rst:824
+# 10b012d926f74eeaaaef9f5d4472b2e8
+msgid "G11n: JA,SC: Un translation issue occurred on the strings of different dropdown ..."
+msgstr ""
+
+#: ../../about.rst:825
+# 6e4117836bd54627983b90ccb4fd972e
+msgid "`CLOUDSTACK-3520 <https://issues.apache.org/jira/browse/CLOUDSTACK-3520>`_"
+msgstr ""
+
+#: ../../about.rst:825
+# 77e8bb8d4eeb46c8b7e8bbe4235146b3
+msgid "G11n: JA,SC: Un translation issue occurred on the strings of different error/war..."
+msgstr ""
+
+#: ../../about.rst:826
+# 69e17113af284510bbdfe40df0585a2d
+msgid "`CLOUDSTACK-3521 <https://issues.apache.org/jira/browse/CLOUDSTACK-3521>`_"
+msgstr ""
+
+#: ../../about.rst:826
+# 1e1fea07835f4dcebeefc56a4449f575
+msgid "G11n: JA,SC: Un translation issue occurred on the strings of different tooltips...."
+msgstr ""
+
+#: ../../about.rst:827
+# 1d2d8b90f2764934b1dd1cd1fce29339
+msgid "`CLOUDSTACK-3522 <https://issues.apache.org/jira/browse/CLOUDSTACK-3522>`_"
+msgstr ""
+
+#: ../../about.rst:827
+# ca84e356f6e84a6da02cb9d318143ad8
+msgid "G11n: JA,SC: Un translation issue occurred on the strings of different buttons. ..."
+msgstr ""
+
+#: ../../about.rst:828
+# 01b9bc53bfd24beca70b3526031dbff7
+msgid "`CLOUDSTACK-3523 <https://issues.apache.org/jira/browse/CLOUDSTACK-3523>`_"
+msgstr ""
+
+#: ../../about.rst:828
+# 283fcc12a9264505b50208d8bf7d2a49
+msgid "G11n: JA,SC: Un translation issue occurred on the strings of different popup mes..."
+msgstr ""
+
+#: ../../about.rst:829
+# d727ab1d9cdd4390830b55c9e82a72c5
+msgid "`CLOUDSTACK-3528 <https://issues.apache.org/jira/browse/CLOUDSTACK-3528>`_"
+msgstr ""
+
+#: ../../about.rst:829
+# 0ddbdc2d48364a249bb650bcaf5bbab4
+msgid "[UI]list calls are in the processing state forever with invalid name provided wi..."
+msgstr ""
+
+#: ../../about.rst:830
+# e37353944bf54b4a85b99168017481d7
+msgid "`CLOUDSTACK-3579 <https://issues.apache.org/jira/browse/CLOUDSTACK-3579>`_"
+msgstr ""
+
+#: ../../about.rst:830
+# 29097d5077f441acb224dc0abe0531f2
+msgid "[DOC]CLONE - Physical Netwok traffic label update requires Management Server res..."
+msgstr ""
+
+#: ../../about.rst:831
+# 8068a0f7fb314d09890588a269e6fbda
+msgid "`CLOUDSTACK-3607 <https://issues.apache.org/jira/browse/CLOUDSTACK-3607>`_"
+msgstr ""
+
+#: ../../about.rst:831
+# 0c66c8aa620d4276a766aabedf6d27ef
+msgid "\"guest_os_hypervisor\" table has values that are not registered in \"guest_os\" tab..."
+msgstr ""
+
+#: ../../about.rst:832
+# 9b30b8f208624d7fb47de5f9c27d766a
+msgid "`CLOUDSTACK-3608 <https://issues.apache.org/jira/browse/CLOUDSTACK-3608>`_"
+msgstr ""
+
+#: ../../about.rst:832
+# a9abe6215c9a4ffb9c2ad532d94f5af6
+msgid "\"guest_os_hypervisor\" table has repeated mappings of hypervisor and guest OS..."
+msgstr ""
+
+#: ../../about.rst:833
+# 91dda0b77dd7409dbfaee7af5bfd4735
+msgid "`CLOUDSTACK-3656 <https://issues.apache.org/jira/browse/CLOUDSTACK-3656>`_"
+msgstr ""
+
+#: ../../about.rst:833
+# 6fac99ff12f44703800ef69bbd326ade
+msgid "lots of cloud-management should be changed to cloudstack-management..."
+msgstr ""
+
+#: ../../about.rst:834
+# 3c5649e1ab4c47e98e0e3c1fb5c42f85
+msgid "`CLOUDSTACK-3788 <https://issues.apache.org/jira/browse/CLOUDSTACK-3788>`_"
+msgstr ""
+
+#: ../../about.rst:834
+# 23bcc323dd9f4499b4b990f6b60e23de
+msgid "[KVM] Weekly Snapshot got stuck in \"Allocated State\"..."
+msgstr ""
+
+#: ../../about.rst:835
+# bf66b9022ae745eeae6dd0d830e04e4b
+msgid "`CLOUDSTACK-3813 <https://issues.apache.org/jira/browse/CLOUDSTACK-3813>`_"
+msgstr ""
+
+#: ../../about.rst:835
+# 565bddce4d1a4e5c9989fc4713209422
+msgid "\"Service.provider.create\" event doesnt mention about the Service Provider in the..."
+msgstr ""
+
+#: ../../about.rst:836
+# 5909690d894e4af98b88348330eaf80c
+msgid "`CLOUDSTACK-3880 <https://issues.apache.org/jira/browse/CLOUDSTACK-3880>`_"
+msgstr ""
+
+#: ../../about.rst:836
+# 92f4394bbccc4d73a7abf4986b7aef09
+msgid "/sbin/poweroff et al or ACPID initiated shutdown does not stop cloudstack-[usage..."
+msgstr ""
+
+#: ../../about.rst:837
+# af5f6c67184c43d69be0f8a84c3da845
+msgid "`CLOUDSTACK-3952 <https://issues.apache.org/jira/browse/CLOUDSTACK-3952>`_"
+msgstr ""
+
+#: ../../about.rst:837
+# 8f858d9cad2f40c88d8d2f5af1e32c6b
+msgid "Persist VR nic details in DB for additional public ranges..."
+msgstr ""
+
+#: ../../about.rst:838
+# d476952f126c4e0da77c036b61493842
+msgid "`CLOUDSTACK-3973 <https://issues.apache.org/jira/browse/CLOUDSTACK-3973>`_"
+msgstr ""
+
+#: ../../about.rst:838
+# 7699c9364349442f9b4f367fe0cc5406
+msgid "[GSLB] [LOGS Message] Improving logs messages for GSLB rule configuration..."
+msgstr ""
+
+#: ../../about.rst:839
+# db8c9e75bf7148cc912ab4272aefb08e
+msgid "`CLOUDSTACK-4016 <https://issues.apache.org/jira/browse/CLOUDSTACK-4016>`_"
+msgstr ""
+
+#: ../../about.rst:839
+# cf07892fab0e409587c77f182580f130
+msgid "[PortableIP] [VPC] listPublicIpAddresses lists the portable IP that was already ..."
+msgstr ""
+
+#: ../../about.rst:840
+# 8b9b04e7723c4229a66a7451ee9149fa
+msgid "`CLOUDSTACK-4139 <https://issues.apache.org/jira/browse/CLOUDSTACK-4139>`_"
+msgstr ""
+
+#: ../../about.rst:840
+# abdf622f1de14176894c2458dd68a5a5
+msgid "[VMWARE]Failed to resize the volumes which are created from snapshot of root vol..."
+msgstr ""
+
+#: ../../about.rst:841
+# 13c094402d2b473b8748820532360c82
+msgid "`CLOUDSTACK-4475 <https://issues.apache.org/jira/browse/CLOUDSTACK-4475>`_"
+msgstr ""
+
+#: ../../about.rst:841
+# d75b21c14d854c718eb7baa5ae577e57
+msgid "[ZWPS] attaching an uploaded volume to a VM is always going to first primary sto..."
+msgstr ""
+
+#: ../../about.rst:842
+# 963c1f4a34fa48e482e68ecfaf50fb0f
+msgid "`CLOUDSTACK-4517 <https://issues.apache.org/jira/browse/CLOUDSTACK-4517>`_"
+msgstr ""
+
+#: ../../about.rst:842
+# 05f689495c3e468b9616d4a552b6041a
+msgid "[upgrade][Vmware]Deployment of VM using centos 6.2 template registered before up..."
+msgstr ""
+
+#: ../../about.rst:843
+# d79bc70df3164ff498dd037943a1c7d7
+msgid "`CLOUDSTACK-4536 <https://issues.apache.org/jira/browse/CLOUDSTACK-4536>`_"
+msgstr ""
+
+#: ../../about.rst:843
+# 2c3c317a8b7641d4b7411985a2d77a7b
+msgid "[object_store_refactor] Inconsistency in volume store location on secondary stor..."
+msgstr ""
+
+#: ../../about.rst:844
+# 4815b5eae689480abd0b6b7fe91ec576
+msgid "`CLOUDSTACK-4568 <https://issues.apache.org/jira/browse/CLOUDSTACK-4568>`_"
+msgstr ""
+
+#: ../../about.rst:844
+# 0d644eebf87f4ed3974a233caa1875e8
+msgid "Need to add this to the release note of 4.2..."
+msgstr ""
+
+#: ../../about.rst:845
+# 4ed6d4de0686413d897b5d5bc1e47bf4
+msgid "`CLOUDSTACK-4587 <https://issues.apache.org/jira/browse/CLOUDSTACK-4587>`_"
+msgstr ""
+
+#: ../../about.rst:845
+# c6d1314a3416461ca735639c482cff75
+msgid "VM is failing to deploy on a Legacy zone after adding zone wide primary storage ..."
+msgstr ""
+
+#: ../../about.rst:846
+# d8e2c85fe6084953b0cd57ca1432252a
+msgid "`CLOUDSTACK-4644 <https://issues.apache.org/jira/browse/CLOUDSTACK-4644>`_"
+msgstr ""
+
+#: ../../about.rst:846
+# 91e0978f03174df9a0ce716746467e3e
+msgid "Tool Tip information is not provided for the new fields which are added in 4.2 (..."
+msgstr ""
+
+#: ../../about.rst:847
+# e353f5b9bce741fe9283b7fdbc4deb2d
+msgid "`CLOUDSTACK-4789 <https://issues.apache.org/jira/browse/CLOUDSTACK-4789>`_"
+msgstr ""
+
+#: ../../about.rst:847
+# b50cb97705294024b308c11f9ae725dc
+msgid "Fix ResourceMetaDataManagerTest..."
+msgstr ""
+
+#: ../../about.rst:848
+# f59060ae188240b0a5d2f26715489d57
+msgid "`CLOUDSTACK-4906 <https://issues.apache.org/jira/browse/CLOUDSTACK-4906>`_"
+msgstr ""
+
+#: ../../about.rst:848
+# 3f4c63f3409141339cbbc807ce029e12
+msgid "add netaddr to marvin dependency list..."
+msgstr ""
+
+#: ../../about.rst:849
+# 3ae875a8bd9b4099955b237366e34a36
+msgid "`CLOUDSTACK-4918 <https://issues.apache.org/jira/browse/CLOUDSTACK-4918>`_"
+msgstr ""
+
+#: ../../about.rst:849
+# f2fabf4d452845cb95c65f6182800a84
+msgid "VR can not be LB service provider without requiring to be source nat service pro..."
+msgstr ""
+
+#: ../../about.rst:850
+# 9401d4a09ea74a9ab860bf262eb09b0f
+msgid "`CLOUDSTACK-4951 <https://issues.apache.org/jira/browse/CLOUDSTACK-4951>`_"
+msgstr ""
+
+#: ../../about.rst:850
+# 6551a1ac300749d59dcff44e00aa4916
+msgid "[event framework] Action events do not have UUID ..."
+msgstr ""
+
+#: ../../about.rst:851
+# a3fca57fd51343fa9ef3d4895f877e2a
+msgid "`CLOUDSTACK-4987 <https://issues.apache.org/jira/browse/CLOUDSTACK-4987>`_"
+msgstr ""
+
+#: ../../about.rst:851
+# 1b9b350d3957469c9a768c94875ac1ea
+msgid "Able to add isolated network belonging to an account to a virtual machine belong..."
+msgstr ""
+
+#: ../../about.rst:852
+# 90ae3294042f4d0597f0efdd0730c5ad
+msgid "`CLOUDSTACK-5043 <https://issues.apache.org/jira/browse/CLOUDSTACK-5043>`_"
+msgstr ""
+
+#: ../../about.rst:852
+# 5af46297d4384855b7abd846b9067ba0
+msgid "[DOC] Page number missing and words truncated in PDFs since 4.1.1..."
+msgstr ""
+
+#: ../../about.rst:853
+# ec7562dd46d849bca09658dc943e540e
+msgid "`CLOUDSTACK-5044 <https://issues.apache.org/jira/browse/CLOUDSTACK-5044>`_"
+msgstr ""
+
+#: ../../about.rst:853
+# bd1e5dee91b042c38ef5a4158faf96ad
+msgid "Configuration Framework Issue..."
+msgstr ""
+
+#: ../../about.rst:854
+# 538f943df0004e81a22d5df035e09d51
+msgid "`CLOUDSTACK-5090 <https://issues.apache.org/jira/browse/CLOUDSTACK-5090>`_"
+msgstr ""
+
+#: ../../about.rst:854
+# 59f356260ca64980873ea42bcd645f41
+msgid "Anti-Affinity: VM fails to start on a cluster belonging to a different pod...."
+msgstr ""
+
+#: ../../about.rst:855
+# b546e94e9dde4baeb145a43938a9cd10
+msgid "`CLOUDSTACK-5157 <https://issues.apache.org/jira/browse/CLOUDSTACK-5157>`_"
+msgstr ""
+
+#: ../../about.rst:855
+# 2646dfaae349447ca25494693e0462a8
+msgid "Loadbalancer Response should include stickiness, health check and ssl certs info..."
+msgstr ""
+
+#: ../../about.rst:856
+# 6a05087655c44bff937a2124f49369b1
+msgid "`CLOUDSTACK-5243 <https://issues.apache.org/jira/browse/CLOUDSTACK-5243>`_"
+msgstr ""
+
+#: ../../about.rst:856
+# 74a8e6f41c7f45e089dc569457615115
+msgid "SSVM responds with timestamp..."
+msgstr ""
+
+#: ../../about.rst:857
+# 912b281864744e47ad4f479d19241f4a
+msgid "`CLOUDSTACK-5251 <https://issues.apache.org/jira/browse/CLOUDSTACK-5251>`_"
+msgstr ""
+
+#: ../../about.rst:857
+# 37eb832c9bb74af4b0cdae2afcfda41f
+msgid "No Error message is displayed when nonexistent NFS secondary storage is added t..."
+msgstr ""
+
+#: ../../about.rst:858
+# d66f80edf66146fba90143a9e484d542
+msgid "`CLOUDSTACK-5296 <https://issues.apache.org/jira/browse/CLOUDSTACK-5296>`_"
+msgstr ""
+
+#: ../../about.rst:858
+# 384f8cbdf3654fa2a9eb680df54dd5db
+msgid "Add certificate chain support for NS..."
+msgstr ""
+
+#: ../../about.rst:859
+# 0d998bd399984a29862cb44b71fcbf96
+msgid "`CLOUDSTACK-5307 <https://issues.apache.org/jira/browse/CLOUDSTACK-5307>`_"
+msgstr ""
+
+#: ../../about.rst:859
+# c49d878f41984cd78db12c9fcf070c95
+msgid "Same router is listed twice in router view of project..."
+msgstr ""
+
+#: ../../about.rst:860
+# 71665a82fbc141a6b01d1195697bb70b
+msgid "`CLOUDSTACK-5324 <https://issues.apache.org/jira/browse/CLOUDSTACK-5324>`_"
+msgstr ""
+
+#: ../../about.rst:860
+# d69f8f89c7df449588dae87cd97d1db3
+msgid "error message not proper when start VM fails because router reuires upgrade..."
+msgstr ""
+
+#: ../../about.rst:861
+# 63e3490bdbfe48dbb9bdda4817820de1
+msgid "`CLOUDSTACK-5342 <https://issues.apache.org/jira/browse/CLOUDSTACK-5342>`_"
+msgstr ""
+
+#: ../../about.rst:861
+# f57d012692bb4c758f3c308260279825
+msgid "[Automation] Add NIC to virtual machine fails in KVM..."
+msgstr ""
+
+#: ../../about.rst:862
+# 854279263dcc4bedbcfdca929874c649
+msgid "`CLOUDSTACK-5359 <https://issues.apache.org/jira/browse/CLOUDSTACK-5359>`_"
+msgstr ""
+
+#: ../../about.rst:862
+# 647abcdf85a14baaba9aed0902868228
+msgid "Failed to add second VMWARE cluster on a standard vSwitch enabled zone when vCen..."
+msgstr ""
+
+#: ../../about.rst:863
+# 18efbd385eca4042bcef93617ac7cfe8
+msgid "`CLOUDSTACK-5373 <https://issues.apache.org/jira/browse/CLOUDSTACK-5373>`_"
+msgstr ""
+
+#: ../../about.rst:863
+# 9271346879e54d97be130f4728cbafeb
+msgid "Web UI (non-English) is corrupted by text expansion..."
+msgstr ""
+
+#: ../../about.rst:864
+# 780d56f9e92f4cc2ba1aa64bb09cbe83
+msgid "`CLOUDSTACK-5395 <https://issues.apache.org/jira/browse/CLOUDSTACK-5395>`_"
+msgstr ""
+
+#: ../../about.rst:864
+# ad882c1bb8f0458f99d80ce32f2583f1
+msgid "When backup snapshot fails becasue of backup.snapshot.wait time exceeding , the ..."
+msgstr ""
+
+#: ../../about.rst:865
+# c7aef46fb8da442d878cdfe4a257324e
+msgid "`CLOUDSTACK-5410 <https://issues.apache.org/jira/browse/CLOUDSTACK-5410>`_"
+msgstr ""
+
+#: ../../about.rst:865
+# ff02b9c29cdf4a668a0f907fe938d4a9
+msgid "Changes for tracking logs using jobid is missing in 4.3..."
+msgstr ""
+
+#: ../../about.rst:866
+# a4a3473f1ace4015b9339ba63e271bce
+msgid "`CLOUDSTACK-5445 <https://issues.apache.org/jira/browse/CLOUDSTACK-5445>`_"
+msgstr ""
+
+#: ../../about.rst:866
+# 186b08ec8c3540e7aacbbda556a2c2a0
+msgid "DeleteImageStoreCmd does not use storage plugins to delete storage..."
+msgstr ""
+
+#: ../../about.rst:867
+# 40a5c6bb376349dea617c8c68dd955b3
+msgid "`CLOUDSTACK-5446 <https://issues.apache.org/jira/browse/CLOUDSTACK-5446>`_"
+msgstr ""
+
+#: ../../about.rst:867
+# 3c0a1722a6cd4281918c4ef6acc1a6a2
+msgid "KVM-Secondary Store down-Even after secondary store is brought back up after bei..."
+msgstr ""
+
+#: ../../about.rst:868
+# 19936917d18f4c77aaaad9e27e2310d9
+msgid "`CLOUDSTACK-5463 <https://issues.apache.org/jira/browse/CLOUDSTACK-5463>`_"
+msgstr ""
+
+#: ../../about.rst:868
+# ba8cbe65e4594d899fe24e54ae8b5992
+msgid "Hyper-V does not report stopped VMs..."
+msgstr ""
+
+#: ../../about.rst:869
+# 27f903e78a1e4230b29219c4ec66fe0d
+msgid "`CLOUDSTACK-5474 <https://issues.apache.org/jira/browse/CLOUDSTACK-5474>`_"
+msgstr ""
+
+#: ../../about.rst:869
+# b91a29a477054ec79e256c6a0fbb1ec3
+msgid "EventBus: RabbitMQ provider expects password to be stored in plain text...."
+msgstr ""
+
+#: ../../about.rst:870
+# 6982699ba50f4148a796aa00770ec36d
+msgid "`CLOUDSTACK-5475 <https://issues.apache.org/jira/browse/CLOUDSTACK-5475>`_"
+msgstr ""
+
+#: ../../about.rst:870
+# ee289fc9554d4907a9b7f6db1c055723
+msgid "cluster.cpu/(memory).allocated.capacity.disablethreshold is getting displayed mu..."
+msgstr ""
+
+#: ../../about.rst:871
+# bca6052a6e7e4389acbc8d0733971f61
+msgid "`CLOUDSTACK-5479 <https://issues.apache.org/jira/browse/CLOUDSTACK-5479>`_"
+msgstr ""
+
+#: ../../about.rst:871
+# 3b3df00c077a4ff183fbb31913209048
+msgid "Upgrading service offering of stopped vm should release the reserved capacity of..."
+msgstr ""
+
+#: ../../about.rst:872
+# c2c37fd269c848c696fd09f301f8ddde
+msgid "`CLOUDSTACK-5482 <https://issues.apache.org/jira/browse/CLOUDSTACK-5482>`_"
+msgstr ""
+
+#: ../../about.rst:872
+# 664f6ca3453948a0a2563e0d533babe6
+msgid "Vmware - When nfs was down for about 1 hour , when snapshots were in progress , ..."
+msgstr ""
+
+#: ../../about.rst:873
+# f5034cfaedc848bdaca9750fe15dbd26
+msgid "`CLOUDSTACK-5488 <https://issues.apache.org/jira/browse/CLOUDSTACK-5488>`_"
+msgstr ""
+
+#: ../../about.rst:873
+# a7dec60810d14854b7976d8efbb9a90b
+msgid "KVM:agent is still in stopped state even after host recovered from sudddent powe..."
+msgstr ""
+
+#: ../../about.rst:874
+# 3bb93b7ac2de4fed9677b7368e741971
+msgid "`CLOUDSTACK-5504 <https://issues.apache.org/jira/browse/CLOUDSTACK-5504>`_"
+msgstr ""
+
+#: ../../about.rst:874
+# 557f1ef5197b4a9ebbfa0a10d2744ffb
+msgid "Vmware-Primary store unavailable for 10 mts - All snapshot tasks reported failur..."
+msgstr ""
+
+#: ../../about.rst:875
+# 5ae6f7889af34ae083506fa75e899a67
+msgid "`CLOUDSTACK-5512 <https://issues.apache.org/jira/browse/CLOUDSTACK-5512>`_"
+msgstr ""
+
+#: ../../about.rst:875
+# 185288f7676b451691fe79f60cabb4ea
+msgid "template format name checking is crude and doesn't work with advanced URLs..."
+msgstr ""
+
+#: ../../about.rst:876
+# 99d37e013d50405a8b7e8c3fbe6bd1b8
+msgid "`CLOUDSTACK-5536 <https://issues.apache.org/jira/browse/CLOUDSTACK-5536>`_"
+msgstr ""
+
+#: ../../about.rst:876
+# 3313cc51b9c54b3ea48d14ba8da7fd5a
+msgid "Restarting cloudstack service with template download in progress creates redunda..."
+msgstr ""
+
+#: ../../about.rst:877
+# 6fc2b9f9f0cd4244b6cae357df2648c1
+msgid "`CLOUDSTACK-5546 <https://issues.apache.org/jira/browse/CLOUDSTACK-5546>`_"
+msgstr ""
+
+#: ../../about.rst:877
+# ad995e32134d42538c1ea2e43b381f39
+msgid "Extra tab for adding rules displayed for non-elb networks..."
+msgstr ""
+
+#: ../../about.rst:878
+# a54dbaac63214de8a33c2afb52bdeb22
+msgid "`CLOUDSTACK-5550 <https://issues.apache.org/jira/browse/CLOUDSTACK-5550>`_"
+msgstr ""
+
+#: ../../about.rst:878
+# 88355285abd84916851924fca618a14f
+msgid "UI - Api key and secret key not fully visible in user detail view...."
+msgstr ""
+
+#: ../../about.rst:879
+# 115fded8d9b14ae888df6d309ed00928
+msgid "`CLOUDSTACK-5561 <https://issues.apache.org/jira/browse/CLOUDSTACK-5561>`_"
+msgstr ""
+
+#: ../../about.rst:879
+# 7d3829818296496e96133bb776f55ced
+msgid "support of multiple nics for VR running in HyperV..."
+msgstr ""
+
+#: ../../about.rst:880
+# 5d53268c0d8649dd8fd8451e90bb2bbe
+msgid "`CLOUDSTACK-5563 <https://issues.apache.org/jira/browse/CLOUDSTACK-5563>`_"
+msgstr ""
+
+#: ../../about.rst:880
+# ace3df46440647d5855140e8dd8dc0e4
+msgid "path field is set to null in volumes table ..."
+msgstr ""
+
+#: ../../about.rst:881
+# a4c069ad32674f6eaaabb01ca26e7113
+msgid "`CLOUDSTACK-5576 <https://issues.apache.org/jira/browse/CLOUDSTACK-5576>`_"
+msgstr ""
+
+#: ../../about.rst:881
+# 29da54590cab44809148bf8c2e05d3ff
+msgid "RemoteVPNonVPC : Label needs to be changed to \"Enable Remote Access VPN\"..."
+msgstr ""
+
+#: ../../about.rst:882
+# 1c6be0b1e1c545c8aab7cf4c395ee39a
+msgid "`CLOUDSTACK-5583 <https://issues.apache.org/jira/browse/CLOUDSTACK-5583>`_"
+msgstr ""
+
+#: ../../about.rst:882
+# e58f05d86e0a4f419ace651927d24418
+msgid "vmopsSnapshot plug-in (XenServer) does not return an error when it should..."
+msgstr ""
+
+#: ../../about.rst:883
+# cbed0572c6e7432a86db4deb1ac862a1
+msgid "`CLOUDSTACK-5600 <https://issues.apache.org/jira/browse/CLOUDSTACK-5600>`_"
+msgstr ""
+
+#: ../../about.rst:883
+# f1979a44524844f2be872644261781d8
+msgid "Xenserver - After HA , CPVM's disk is corrupted resulting in CPVM being stuck in..."
+msgstr ""
+
+#: ../../about.rst:884
+# 0ab0fd8ed1bb438794ce77987189a38d
+msgid "`CLOUDSTACK-5616 <https://issues.apache.org/jira/browse/CLOUDSTACK-5616>`_"
+msgstr ""
+
+#: ../../about.rst:884
+# 66ca2c3ae557455a8e0bd6fc1cf71461
+msgid "[DBHA]:There is no way to know to which DB is the CS writing in the case of DBHA..."
+msgstr ""
+
+#: ../../about.rst:885
+# d7afa33b29a9481b81da8e9979c9fe99
+msgid "`CLOUDSTACK-5632 <https://issues.apache.org/jira/browse/CLOUDSTACK-5632>`_"
+msgstr ""
+
+#: ../../about.rst:885
+# 1fb27092752e48ebae6b13be3236cc36
+msgid "[Automation] XenServer - Template deletion fails with error \"Please specify a te..."
+msgstr ""
+
+#: ../../about.rst:886
+# 8faf542b4f8d49268ad3f077a273d0ea
+msgid "`CLOUDSTACK-5645 <https://issues.apache.org/jira/browse/CLOUDSTACK-5645>`_"
+msgstr ""
+
+#: ../../about.rst:886
+# 50778e9a2d4a4bcbbc88640e9166df7b
+msgid "Agent manager doesn't need to be aware of vms and their relationship to resource..."
+msgstr ""
+
+#: ../../about.rst:887
+# 18b251fdf12941b08ae9f51e40ad63b5
+msgid "`CLOUDSTACK-5673 <https://issues.apache.org/jira/browse/CLOUDSTACK-5673>`_"
+msgstr ""
+
+#: ../../about.rst:887
+# 37828a256ee04f84bef64abc33e23445
+msgid "[Hyper-V] Default IP address never configured on eth0 with default CentOS templa..."
+msgstr ""
+
+#: ../../about.rst:888
+# a1a62c2a7c7140d893ac132834fa2ac3
+msgid "`CLOUDSTACK-5685 <https://issues.apache.org/jira/browse/CLOUDSTACK-5685>`_"
+msgstr ""
+
+#: ../../about.rst:888
+# ef5d0499d90b4aa1ac23c4c2ed84ad54
+msgid "[Vmsync] - When VR is rebooted outside of cloudstack , there is no change in sta..."
+msgstr ""
+
+#: ../../about.rst:889
+# 05dfaa9b48b74d5ea1cd1e1465e47a37
+msgid "`CLOUDSTACK-5700 <https://issues.apache.org/jira/browse/CLOUDSTACK-5700>`_"
+msgstr ""
+
+#: ../../about.rst:889
+# ae47fe867c8c4bebbf91f2089da3de2c
+msgid "[Vmsync] - kvm- \"paused\" state of Vm is not synced to CS...."
+msgstr ""
+
+#: ../../about.rst:890
+# f5f9d1b9f7eb44a8a12525d5876edaf6
+msgid "`CLOUDSTACK-5719 <https://issues.apache.org/jira/browse/CLOUDSTACK-5719>`_"
+msgstr ""
+
+#: ../../about.rst:890
+# f4a44a6bee7a4174904606768d1b5317
+msgid "[UI] Not listing shared network offerings tagged on second physical network..."
+msgstr ""
+
+#: ../../about.rst:891
+# 6ce899d61b7c48d7a5672becc9c54d4e
+msgid "`CLOUDSTACK-5724 <https://issues.apache.org/jira/browse/CLOUDSTACK-5724>`_"
+msgstr ""
+
+#: ../../about.rst:891
+# 700f101ab73145708d1ba9a04087c56d
+msgid "Console Proxy View - when using ctl c , errors seen on the console proxy view...."
+msgstr ""
+
+#: ../../about.rst:892
+# ff9918b62f6a4a64ba52cca3f79d88b4
+msgid "`CLOUDSTACK-5743 <https://issues.apache.org/jira/browse/CLOUDSTACK-5743>`_"
+msgstr ""
+
+#: ../../about.rst:892
+# 98cbe0a9a1e8430897abd0b9af2db194
+msgid "Download ROOT Volume when the VM is in stopped state is failing with \"Forbidden..."
+msgstr ""
+
+#: ../../about.rst:893
+# d0cf5147264a41baa87388c9783ee790
+msgid "`CLOUDSTACK-5744 <https://issues.apache.org/jira/browse/CLOUDSTACK-5744>`_"
+msgstr ""
+
+#: ../../about.rst:893
+# 0f713dfd8c3c4df69483c843804baab2
+msgid "[Hyper-v] White screen on console window when more than two console sessions are..."
+msgstr ""
+
+#: ../../about.rst:894
+# 5aafc3f652cf44d692c4e1645a8bf3d4
+msgid "`CLOUDSTACK-5753 <https://issues.apache.org/jira/browse/CLOUDSTACK-5753>`_"
+msgstr ""
+
+#: ../../about.rst:894
+# 42cd0b6e37ad4404bdb40e46486fed21
+msgid "[Hyper-v] ConsoleProxyLoadReportCommand does not honor the default value of cons..."
+msgstr ""
+
+#: ../../about.rst:895
+# 5b013ab075a44ee6a6b3e33a2bae8f61
+msgid "`CLOUDSTACK-5762 <https://issues.apache.org/jira/browse/CLOUDSTACK-5762>`_"
+msgstr ""
+
+#: ../../about.rst:895
+# b0cbc6e65abd4f33a804cd00a9b9c695
+msgid "[dynamic compute offerings]UI change required for select compute offerinngs in ..."
+msgstr ""
+
+#: ../../about.rst:896
+# a634cee299e04a14b89a67fd6a94125c
+msgid "`CLOUDSTACK-5785 <https://issues.apache.org/jira/browse/CLOUDSTACK-5785>`_"
+msgstr ""
+
+#: ../../about.rst:896
+# f250b3550ce9466a9b47ac297dcea0c4
+msgid "VM display name cell not updated upon detaching volume from VM..."
+msgstr ""
+
+#: ../../about.rst:897
+# 57ad55a4e61647a0882bc09169fd6817
+msgid "`CLOUDSTACK-5794 <https://issues.apache.org/jira/browse/CLOUDSTACK-5794>`_"
+msgstr ""
+
+#: ../../about.rst:897
+# 58ad5190ba254101aecd3d7a72a35438
+msgid "[Hyper-v] Specify username and domain name together in the username field while ..."
+msgstr ""
+
+#: ../../about.rst:898
+# ebd16484f41f49ae8baf3ae988aece7e
+msgid "`CLOUDSTACK-5798 <https://issues.apache.org/jira/browse/CLOUDSTACK-5798>`_"
+msgstr ""
+
+#: ../../about.rst:898
+# 7a0969b4f07a49f7b7c462a014c2c8af
+msgid "While attaching a disk to WIN2012 VM with xencenter tools installed got error as..."
+msgstr ""
+
+#: ../../about.rst:899
+# 8e0ee4b7c893491baa02e0e3e93e8e16
+msgid "`CLOUDSTACK-5800 <https://issues.apache.org/jira/browse/CLOUDSTACK-5800>`_"
+msgstr ""
+
+#: ../../about.rst:899
+# 0ed8e78455684cdc8a491ed802c6965f
+msgid "While creating a VM from template (which is created based on existing newly crea..."
+msgstr ""
+
+#: ../../about.rst:900
+# 12d7be57f3964c8ea7f8764a8b5542e1
+msgid "`CLOUDSTACK-5807 <https://issues.apache.org/jira/browse/CLOUDSTACK-5807>`_"
+msgstr ""
+
+#: ../../about.rst:900
+# 1250e3a50d13426193f19f2eb26d8234
+msgid "Problem with shared datastore in VMware cluster with only one host..."
+msgstr ""
+
+#: ../../about.rst:901
+# 69f827f9a93e490dbd9e6f2741f2cbc5
+msgid "`CLOUDSTACK-5809 <https://issues.apache.org/jira/browse/CLOUDSTACK-5809>`_"
+msgstr ""
+
+#: ../../about.rst:901
+# 9074e58f0309446e8db7614d7e5e5127
+msgid "Not able to deploy Vm becasue of crossing pool.storage.allocate d.capacity.disab..."
+msgstr ""
+
+#: ../../about.rst:902
+# 286bdc5b6ef849dd8db6b248ee7d6f60
+msgid "`CLOUDSTACK-5822 <https://issues.apache.org/jira/browse/CLOUDSTACK-5822>`_"
+msgstr ""
+
+#: ../../about.rst:902
+# d289cc546c5e4df4ad53f642e8874469
+msgid "ssh keypairs are removed after rebooting vm..."
+msgstr ""
+
+#: ../../about.rst:903
+# 664f265b4db244e3b0c56c3095902135
+msgid "`CLOUDSTACK-5834 <https://issues.apache.org/jira/browse/CLOUDSTACK-5834>`_"
+msgstr ""
+
+#: ../../about.rst:903
+# 667f15f64c964fa2bac4bba9015e4084
+msgid "[upgrade]Error while collecting disk stats from : You gave an invalid object ref..."
+msgstr ""
+
+#: ../../about.rst:904
+# 786d10393be74d629c641bc4b38faf42
+msgid "`CLOUDSTACK-5836 <https://issues.apache.org/jira/browse/CLOUDSTACK-5836>`_"
+msgstr ""
+
+#: ../../about.rst:904
+# 7bc6019b2e7848dea5578204eaa13518
+msgid "When tried to reverting back to (disk attached)quiesced vm snapshot, got error a..."
+msgstr ""
+
+#: ../../about.rst:905
+# d7f0463020c34e5e834a238760a0f9e4
+msgid "`CLOUDSTACK-5843 <https://issues.apache.org/jira/browse/CLOUDSTACK-5843>`_"
+msgstr ""
+
+#: ../../about.rst:905
+# af63ab512388436084ef9a5e5e26cdc8
+msgid "registering templates/isos should be either async or changed to non-blocking..."
+msgstr ""
+
+#: ../../about.rst:906
+# cb9d311cd97a46f0916d2556e653472d
+msgid "`CLOUDSTACK-5845 <https://issues.apache.org/jira/browse/CLOUDSTACK-5845>`_"
+msgstr ""
+
+#: ../../about.rst:906
+# 05f37dcc77404e77b8c79111c57c9d36
+msgid "[doc] Document Heterogeneous Secondary Storage Not Supported in Region..."
+msgstr ""
+
+#: ../../about.rst:907
+# c293d49d6ee14f3691333a1fcc1d9cae
+msgid "`CLOUDSTACK-5847 <https://issues.apache.org/jira/browse/CLOUDSTACK-5847>`_"
+msgstr ""
+
+#: ../../about.rst:907
+# 6c44f7c2f2f24344bd8bdfa3b418dd4c
+msgid "[Hyper-V] [doc] Document creation of external vswitch for Hyper-V 2012 R2 (unlik..."
+msgstr ""
+
+#: ../../about.rst:908
+# bb970630a4c340cfab239c5db76d5673
+msgid "`CLOUDSTACK-5855 <https://issues.apache.org/jira/browse/CLOUDSTACK-5855>`_"
+msgstr ""
+
+#: ../../about.rst:908
+# e13098ccaa854d3390abfce0d6b31ab9
+msgid "Contrail: Slave compute host restarts when the master compute host is changed to..."
+msgstr ""
+
+#: ../../about.rst:909
+# 928b3d2337e943518c6970f197a7d678
+msgid "`CLOUDSTACK-5862 <https://issues.apache.org/jira/browse/CLOUDSTACK-5862>`_"
+msgstr ""
+
+#: ../../about.rst:909
+# 53ef125446914ddb909aed2609ec7675
+msgid "Template life cycle needs to be changed based on references of existing VMs to t..."
+msgstr ""
+
+#: ../../about.rst:910
+# a799fb1c163f495bb4b930f6407dd4c0
+msgid "`CLOUDSTACK-5866 <https://issues.apache.org/jira/browse/CLOUDSTACK-5866>`_"
+msgstr ""
+
+#: ../../about.rst:910
+# 3c604dcccc1547b981102ad43574b2ea
+msgid "Remove maven profile used to configure zone..."
+msgstr ""
+
+#: ../../about.rst:911
+# 2f2b6f0b3b5b44dd85e12acc6c23ef50
+msgid "`CLOUDSTACK-5876 <https://issues.apache.org/jira/browse/CLOUDSTACK-5876>`_"
+msgstr ""
+
+#: ../../about.rst:911
+# 8b6ef5cbb54a4ce5b0467f0011c7c1f1
+msgid "Contrail: After vrouter restart agent doesnt have info about the Network..."
+msgstr ""
+
+#: ../../about.rst:912
+# 893995e98cc7440ea0dba88aaa379dd0
+msgid "`CLOUDSTACK-5879 <https://issues.apache.org/jira/browse/CLOUDSTACK-5879>`_"
+msgstr ""
+
+#: ../../about.rst:912
+# 6571f89c2aae4158bbd1b99c772c38f5
+msgid "Document on how to use RabbitMq event bus with spring modularisation done in 4.3..."
+msgstr ""
+
+#: ../../about.rst:913
+# cc8c7cf6a4d94119bf49f81944e920d0
+msgid "`CLOUDSTACK-5897 <https://issues.apache.org/jira/browse/CLOUDSTACK-5897>`_"
+msgstr ""
+
+#: ../../about.rst:913
+# 403d2f7b85104696a671c5b93e8ea8bb
+msgid "Remove OVM in add cluster drop down list..."
+msgstr ""
+
+#: ../../about.rst:914
+# 2c4e82e8705045c080699b97100bedb1
+msgid "`CLOUDSTACK-5907 <https://issues.apache.org/jira/browse/CLOUDSTACK-5907>`_"
+msgstr ""
+
+#: ../../about.rst:914
+# f034b4782a2b43f3bb70c3310b99162b
+msgid "KVM/CLVM volumes are shown as Ovm hypervisor..."
+msgstr ""
+
+#: ../../about.rst:915
+# 9334e89d22934a17943a95a1a6d5e76d
+msgid "`CLOUDSTACK-5908 <https://issues.apache.org/jira/browse/CLOUDSTACK-5908>`_"
+msgstr ""
+
+#: ../../about.rst:915
+# 534e0c90b9384a20978f7e71bdb28087
+msgid "Fail to add VXLAN network to instance..."
+msgstr ""
+
+#: ../../about.rst:916
+# 7abee3bb9e2f426d8c64026e38aead1a
+msgid "`CLOUDSTACK-5910 <https://issues.apache.org/jira/browse/CLOUDSTACK-5910>`_"
+msgstr ""
+
+#: ../../about.rst:916
+# 949aa883624c49ec947c8f6043726b82
+msgid "mark the LDAP user as imported from LDAP..."
+msgstr ""
+
+#: ../../about.rst:917
+# ddb914164d494cb389f441f8cdde6e6c
+msgid "`CLOUDSTACK-5920 <https://issues.apache.org/jira/browse/CLOUDSTACK-5920>`_"
+msgstr ""
+
+#: ../../about.rst:917
+# c7c78875c79c41b6a408653ff602283e
+msgid "CloudStack IAM Plugin feature..."
+msgstr ""
+
+#: ../../about.rst:918
+# 8e519430e75d485a994dae2492b983f0
+msgid "`CLOUDSTACK-5926 <https://issues.apache.org/jira/browse/CLOUDSTACK-5926>`_"
+msgstr ""
+
+#: ../../about.rst:918
+# f40042d45fa045c69feac8f0d56523e9
+msgid "[Doc] Create 4.3 Release Notes..."
+msgstr ""
+
+#: ../../about.rst:919
+# 01274b0e8eb0455488738fe326b2ca4a
+msgid "`CLOUDSTACK-5931 <https://issues.apache.org/jira/browse/CLOUDSTACK-5931>`_"
+msgstr ""
+
+#: ../../about.rst:919
+# 2ad43a29eb2446c19054d4f4de8a412d
+msgid "Hyper-V agent does not release logon handle..."
+msgstr ""
+
+#: ../../about.rst:920
+# 7574c7a322544be1b263bb3ec5592bf0
+msgid "`CLOUDSTACK-5932 <https://issues.apache.org/jira/browse/CLOUDSTACK-5932>`_"
+msgstr ""
+
+#: ../../about.rst:920
+# 8959ea6a86f14c44b75082b5cf4a5504
+msgid "SystemVM scripts: the iso download urls need updating as current ones are obsole..."
+msgstr ""
+
+#: ../../about.rst:921
+# 9ba0283e6f494ab9a79dd828a4f01f72
+msgid "`CLOUDSTACK-5933 <https://issues.apache.org/jira/browse/CLOUDSTACK-5933>`_"
+msgstr ""
+
+#: ../../about.rst:921
+#: ../../about.rst:922
+#: ../../about.rst:923
+# 4386f9854460410f99be0fbf30839be2
+# c01f1d82b0b34f4f8e65a923f537f52c
+# ee091b1541c5408892806e573ea04f96
+msgid "Problem with VMware snapshot when datastore has a space in its name..."
+msgstr ""
+
+#: ../../about.rst:922
+# 29f18f2027654c7195ad40575c511e42
+msgid "`CLOUDSTACK-5934 <https://issues.apache.org/jira/browse/CLOUDSTACK-5934>`_"
+msgstr ""
+
+#: ../../about.rst:923
+# 2803afd9715643d9993f1bc6d35b48ea
+msgid "`CLOUDSTACK-5935 <https://issues.apache.org/jira/browse/CLOUDSTACK-5935>`_"
+msgstr ""
+
+#: ../../about.rst:924
+# 16e9afd202824f61b74b88fcd119ac31
+msgid "`CLOUDSTACK-5947 <https://issues.apache.org/jira/browse/CLOUDSTACK-5947>`_"
+msgstr ""
+
+#: ../../about.rst:924
+# eaefc26ccb71465b9dd709c1363ce884
+msgid "Exception for getRootDir.. NFSStorage when running with Simulator..."
+msgstr ""
+
+#: ../../about.rst:925
+# 33be46514ef34269bf6bf799e7a0a600
+msgid "`CLOUDSTACK-5951 <https://issues.apache.org/jira/browse/CLOUDSTACK-5951>`_"
+msgstr ""
+
+#: ../../about.rst:925
+# 04ebebcb83874e32b89e4f558668fdfc
+msgid "Fix base.py for Dynamic compute offerings..."
+msgstr ""
+
+#: ../../about.rst:926
+# 3603844f426d4800b2674bcc3b9b0ecf
+msgid "`CLOUDSTACK-5954 <https://issues.apache.org/jira/browse/CLOUDSTACK-5954>`_"
+msgstr ""
+
+#: ../../about.rst:926
+# 2543950ffe334bd7af6428c70e2b0bc1
+msgid "update-ssl.png missing from docs..."
+msgstr ""
+
+#: ../../about.rst:927
+# fe22a557e4a54a8db459927cbb92059e
+msgid "`CLOUDSTACK-5955 <https://issues.apache.org/jira/browse/CLOUDSTACK-5955>`_"
+msgstr ""
+
+#: ../../about.rst:927
+# 45fbb0c1ae664a41be751b48dea38610
+msgid "vm stuck in migrating if mgmt server is restarted..."
+msgstr ""
+
+#: ../../about.rst:928
+# 8da42368a75849949db98ccf97555530
+msgid "`CLOUDSTACK-5962 <https://issues.apache.org/jira/browse/CLOUDSTACK-5962>`_"
+msgstr ""
+
+#: ../../about.rst:928
+# fc01cb9dba774bf89888043588232727
+msgid "Value of Global parameter \"custom.diskoffering.size.min\" is not reflected in UI ..."
+msgstr ""
+
+#: ../../about.rst:929
+# 4b6f466a4e8643b9860fa0ded9ccac27
+msgid "`CLOUDSTACK-5972 <https://issues.apache.org/jira/browse/CLOUDSTACK-5972>`_"
+msgstr ""
+
+#: ../../about.rst:929
+# ee4e8088a3294f549933b776bd47f7ca
+msgid "[DOC] Service monitoring enable/disable from global setting..."
+msgstr ""
+
+#: ../../about.rst:930
+# b7080df2863f4a02ada36a7669fcafb3
+msgid "`CLOUDSTACK-5976 <https://issues.apache.org/jira/browse/CLOUDSTACK-5976>`_"
+msgstr ""
+
+#: ../../about.rst:930
+# 28f272835ca8486f8c0891e5bcf8f2dd
+msgid "[upgrade]Typo in \"ssh_keypairs\" table's foreign key constraints on the Upgraded ..."
+msgstr ""
+
+#: ../../about.rst:931
+# 9714620e8faf422e9fa107751abe5e3b
+msgid "`CLOUDSTACK-5982 <https://issues.apache.org/jira/browse/CLOUDSTACK-5982>`_"
+msgstr ""
+
+#: ../../about.rst:931
+# 2fc8a368b6f6459d872d5d634ba665da
+msgid "Fix response name for assign and unassign cert from lb..."
+msgstr ""
+
+#: ../../about.rst:932
+# f4acaba44ed241d6a8074c671b3512bd
+msgid "`CLOUDSTACK-5984 <https://issues.apache.org/jira/browse/CLOUDSTACK-5984>`_"
+msgstr ""
+
+#: ../../about.rst:932
+# 7362786c6c33486ea7a8946e592e3ca6
+msgid "addvmwaredc API call is not documented ..."
+msgstr ""
+
+#: ../../about.rst:933
+# 2429317d3e594bd39f9a9fcb598d8c04
+msgid "`CLOUDSTACK-5990 <https://issues.apache.org/jira/browse/CLOUDSTACK-5990>`_"
+msgstr ""
+
+#: ../../about.rst:933
+# 0c384ea6026045b1978af48b16642089
+msgid "[UI]: search by username while importing ldap users..."
+msgstr ""
+
+#: ../../about.rst:934
+# 78e319ed865c4e0fa5dc3f7ed5de0d13
+msgid "`CLOUDSTACK-5991 <https://issues.apache.org/jira/browse/CLOUDSTACK-5991>`_"
+msgstr ""
+
+#: ../../about.rst:934
+# 6ff88586054e4c1d82b6e99db1f9ba80
+msgid "[UI]Infinite scrolling should be enabled to the Ldap user add page..."
+msgstr ""
+
+#: ../../about.rst:935
+# f96e43ac77f04ecfb3dc785d65882fd3
+msgid "`CLOUDSTACK-5992 <https://issues.apache.org/jira/browse/CLOUDSTACK-5992>`_"
+msgstr ""
+
+#: ../../about.rst:935
+# c14aa9269b9d441397bfe8e512f12311
+msgid "[Upgrade] default values of configuraiton parameters in configuration table are ..."
+msgstr ""
+
+#: ../../about.rst:936
+# 115e1a722aec40dea274c772d85f8282
+msgid "`CLOUDSTACK-6032 <https://issues.apache.org/jira/browse/CLOUDSTACK-6032>`_"
+msgstr ""
+
+#: ../../about.rst:936
+# 04d499a0e71b4bcfb0d6e3ac86c4dff9
+msgid "[VmScaleup]service offering id is not getting changed in usage_vm_instance table..."
+msgstr ""
+
+#: ../../about.rst:937
+# bfaa76d737784b5f95c018f977157aac
+msgid "`CLOUDSTACK-6043 <https://issues.apache.org/jira/browse/CLOUDSTACK-6043>`_"
+msgstr ""
+
+#: ../../about.rst:937
+# ccc1bf14d57044fcbb50a3ac110729a4
+msgid "VMware detaching volume fails if volume has snapshots..."
+msgstr ""
+
+#: ../../about.rst:938
+# 9aa2b12288f1420aaff1cfc0743f8da9
+msgid "`CLOUDSTACK-6053 <https://issues.apache.org/jira/browse/CLOUDSTACK-6053>`_"
+msgstr ""
+
+#: ../../about.rst:938
+# 0d09a8008b58494cb60ebe19ca52393a
+msgid "While adding smb as primary or secondary the password should be uri encoded..."
+msgstr ""
+
+#: ../../about.rst:939
+# ea7673542e854e8b8b711ff94908a370
+msgid "`CLOUDSTACK-6069 <https://issues.apache.org/jira/browse/CLOUDSTACK-6069>`_"
+msgstr ""
+
+#: ../../about.rst:939
+# 747f609fab1f4c7ab98cf17ac0fee78b
+msgid "can't create privatgateway with vlan in a mixed network env..."
+msgstr ""
+
+#: ../../about.rst:940
+# 326fdaf624be4f64bf070a7c3e06a679
+msgid "`CLOUDSTACK-6072 <https://issues.apache.org/jira/browse/CLOUDSTACK-6072>`_"
+msgstr ""
+
+#: ../../about.rst:940
+# 2d55d9b75a474be4a4b7d5e5211819c6
+msgid "vxlan networks not deallocating vnet ids..."
+msgstr ""
+
+#: ../../about.rst:941
+# ff1b141db0744c36a592d1d91ed693b4
+msgid "`CLOUDSTACK-6075 <https://issues.apache.org/jira/browse/CLOUDSTACK-6075>`_"
+msgstr ""
+
+#: ../../about.rst:941
+# 9275c6fbfa4144458d09a323ddb8bae2
+msgid "Increase the ram size for router service offering ..."
+msgstr ""
+
+#: ../../about.rst:942
+# 99d3af9b1e5e4a058a7ae118be123d1e
+msgid "`CLOUDSTACK-124 <https://issues.apache.org/jira/browse/CLOUDSTACK-124>`_"
+msgstr ""
+
+#: ../../about.rst:942
+# 8b32bfa08c0b46d6aef684e18497b33d
+msgid "NetworkGarbageCollector not cleaning up networks..."
+msgstr ""
+
+#: ../../about.rst:943
+# c7b26358582f4b899243737fd06f4f37
+msgid "`CLOUDSTACK-231 <https://issues.apache.org/jira/browse/CLOUDSTACK-231>`_"
+msgstr ""
+
+#: ../../about.rst:943
+# 7708223f4e4448b789b13ce1051e7600
+msgid "Tag creation using special charecters ..."
+msgstr ""
+
+#: ../../about.rst:944
+# b1bfdf6469a148aeb6acf9f7d59c9822
+msgid "`CLOUDSTACK-245 <https://issues.apache.org/jira/browse/CLOUDSTACK-245>`_"
+msgstr ""
+
+#: ../../about.rst:944
+# 9646ba76ef4042be82d7fa965b4b4d52
+msgid "VPC ACLs are not stored and programmed consistently..."
+msgstr ""
+
+#: ../../about.rst:945
+# b5967ba18bb7411284a3490e7441a8ac
+msgid "`CLOUDSTACK-270 <https://issues.apache.org/jira/browse/CLOUDSTACK-270>`_"
+msgstr ""
+
+#: ../../about.rst:945
+# cfbf880966d54900827f3b15c49cb007
+msgid "Ui should not ask for a vlan range if the physical network isolation type is not..."
+msgstr ""
+
+#: ../../about.rst:946
+# 8dd70cedd961486b891f7e9f84e26355
+msgid "`CLOUDSTACK-300 <https://issues.apache.org/jira/browse/CLOUDSTACK-300>`_"
+msgstr ""
+
+#: ../../about.rst:946
+# e9a0c1d5e2464610827b27e605893f3c
+msgid "Creation of compute offering allow combination of local storage + HA..."
+msgstr ""
+
+#: ../../about.rst:947
+# c314d5cd2be1492494cc4e4ea1154d0a
+msgid "`CLOUDSTACK-310 <https://issues.apache.org/jira/browse/CLOUDSTACK-310>`_"
+msgstr ""
+
+#: ../../about.rst:947
+# dc667412a14d4fc69fc4b8ed16fe2bab
+msgid "Failed to add host - Plugin error..."
+msgstr ""
+
+#: ../../about.rst:948
+# 48d31a39636440bea18cce416c33fbb1
+msgid "`CLOUDSTACK-315 <https://issues.apache.org/jira/browse/CLOUDSTACK-315>`_"
+msgstr ""
+
+#: ../../about.rst:948
+# ae220428d8694c7fb40b3a5761b7fa63
+msgid "Infrastructure view does not show capacity values..."
+msgstr ""
+
+#: ../../about.rst:949
+# 5ede82ec7e3d49d091dc2d17da781c46
+msgid "`CLOUDSTACK-338 <https://issues.apache.org/jira/browse/CLOUDSTACK-338>`_"
+msgstr ""
+
+#: ../../about.rst:949
+# 07a190ee55074d1d819ebabc319c3e68
+msgid "Unique Names of Disk and Service Offerings in the database are prefixed with \"Cl..."
+msgstr ""
+
+#: ../../about.rst:950
+# ae36f1b0f52d44399375157f009f074b
+msgid "`CLOUDSTACK-458 <https://issues.apache.org/jira/browse/CLOUDSTACK-458>`_"
+msgstr ""
+
+#: ../../about.rst:950
+# d2f66c59719448bfaa2ce410d66f8988
+msgid "xen:snapshots:Storage gc fail to clean the failed snapshot images from secondary..."
+msgstr ""
+
+#: ../../about.rst:951
+# 47ae8a9bb8f6481cbd5e3cf677f76b58
+msgid "`CLOUDSTACK-469 <https://issues.apache.org/jira/browse/CLOUDSTACK-469>`_"
+msgstr ""
+
+#: ../../about.rst:951
+# 75fd3eb386254a40a083e972fa4d9a6e
+msgid "CloudStack Documentation Landing Page has Alignment Issues..."
+msgstr ""
+
+#: ../../about.rst:952
+# 806acce787f84760abfb775a59d638ad
+msgid "`CLOUDSTACK-963 <https://issues.apache.org/jira/browse/CLOUDSTACK-963>`_"
+msgstr ""
+
+#: ../../about.rst:952
+# 12fff80d2a504c49bbbd22824bdace67
+msgid "[cloud.utils.AnnotationHelper] class java.lang.Stringdoes not have a Table anno..."
+msgstr ""
+
+#: ../../about.rst:953
+# de17f1a800814328b23a1e708d2b1d52
+msgid "`CLOUDSTACK-969 <https://issues.apache.org/jira/browse/CLOUDSTACK-969>`_"
+msgstr ""
+
+#: ../../about.rst:953
+# 2d464e8f68a74405b04341a4a2d4adb8
+msgid "api: zone response lists vlan in it as \"vlan range of zone\" but the vlan belongs..."
+msgstr ""
+
+#: ../../about.rst:954
+# f1c3403f8032419e829ccd4f66929b52
+msgid "`CLOUDSTACK-1306 <https://issues.apache.org/jira/browse/CLOUDSTACK-1306>`_"
+msgstr ""
+
+#: ../../about.rst:954
+# dfc0360381c84cfaa6bc712e47d656e3
+msgid "Better Error message when trying to deploy Vm by passing static Ipv4 addresses t..."
+msgstr ""
+
+#: ../../about.rst:955
+# dd3b26e637654719bb43bdc9c4951b4b
+msgid "`CLOUDSTACK-1432 <https://issues.apache.org/jira/browse/CLOUDSTACK-1432>`_"
+msgstr ""
+
+#: ../../about.rst:955
+# 121ae86f157948aca5c4968ee689fdff
+msgid "[UI] Inconsistent field names in \"Add Cluster\" dialog..."
+msgstr ""
+
+#: ../../about.rst:956
+# edb4df0f0696493b89d2bbb6cc1cb883
+msgid "`CLOUDSTACK-1471 <https://issues.apache.org/jira/browse/CLOUDSTACK-1471>`_"
+msgstr ""
+
+#: ../../about.rst:956
+# 675b3aabed6342f89a73e1b339e1307d
+msgid "Pop up window for host details/(host related operation) are not properly alligne..."
+msgstr ""
+
+#: ../../about.rst:957
+# 1cde4cfe8a714ee09c622f4f55535fb6
+msgid "`CLOUDSTACK-1524 <https://issues.apache.org/jira/browse/CLOUDSTACK-1524>`_"
+msgstr ""
+
+#: ../../about.rst:957
+# 53711da9789c471c9c4ccddec57bfd73
+msgid "\"White-box\" effect changes when changing value in combo box..."
+msgstr ""
+
+#: ../../about.rst:958
+# c8b98ae00ee74a8fb6482e1d34e1e202
+msgid "`CLOUDSTACK-1725 <https://issues.apache.org/jira/browse/CLOUDSTACK-1725>`_"
+msgstr ""
+
+#: ../../about.rst:958
+# 04d1ceedb4cf4fd587951c61447daadd
+msgid "publican update_pot might overwrite license headers ..."
+msgstr ""
+
+#: ../../about.rst:959
+# 8a851e230e3e42be884bc41ebca07328
+msgid "`CLOUDSTACK-1932 <https://issues.apache.org/jira/browse/CLOUDSTACK-1932>`_"
+msgstr ""
+
+#: ../../about.rst:959
+# e8da1950cdbf43ce91092026157cd9aa
+msgid "AutoScale UI documentation doesn't mention the option appears only for NetScaler..."
+msgstr ""
+
+#: ../../about.rst:960
+# f57d54cd7d08437ab637326258386606
+msgid "`CLOUDSTACK-2000 <https://issues.apache.org/jira/browse/CLOUDSTACK-2000>`_"
+msgstr ""
+
+#: ../../about.rst:960
+# a2971c5c19f245b2884b505f192fcf00
+msgid "CS4.1 Installation document - cloud-install-sys-tmplt command documented in wron..."
+msgstr ""
+
+#: ../../about.rst:961
+# ef26a2d622594a9f8ae10db60449a3a9
+msgid "`CLOUDSTACK-2213 <https://issues.apache.org/jira/browse/CLOUDSTACK-2213>`_"
+msgstr ""
+
+#: ../../about.rst:961
+# c6f808586258497dbb707d2e7e55cf79
+msgid "russian language select failure..."
+msgstr ""
+
+#: ../../about.rst:962
+# 5b524111ffd5492f878176c4e14f4372
+msgid "`CLOUDSTACK-2345 <https://issues.apache.org/jira/browse/CLOUDSTACK-2345>`_"
+msgstr ""
+
+#: ../../about.rst:962
+# 999211c7bc964a1583b5570055024ce2
+msgid "[GSLB] deleting GSLB rules is not cleaning server info from GSLB device..."
+msgstr ""
+
+#: ../../about.rst:963
+# d9b8c98f542a4b1981d8d347f6aa9590
+msgid "`CLOUDSTACK-2436 <https://issues.apache.org/jira/browse/CLOUDSTACK-2436>`_"
+msgstr ""
+
+#: ../../about.rst:963
+# d4e2678c414e41d0b481b115b9c0f6ad
+msgid "Message \"You do not have any affinity groups. Please continue to the next step.\"..."
+msgstr ""
+
+#: ../../about.rst:964
+# 5ae6ab9b375f4c7bb3589a8050f99194
+msgid "`CLOUDSTACK-2439 <https://issues.apache.org/jira/browse/CLOUDSTACK-2439>`_"
+msgstr ""
+
+#: ../../about.rst:964
+# 87c6a77f806e447ab440b72510b524d8
+msgid "\"Domain\" field under login page should be mandatory for the non root accounts...."
+msgstr ""
+
+#: ../../about.rst:965
+# 02b4ebd93f48469899a2d01cda5705c5
+msgid "`CLOUDSTACK-2449 <https://issues.apache.org/jira/browse/CLOUDSTACK-2449>`_"
+msgstr ""
+
+#: ../../about.rst:965
+# 23efd36a35834b908f1e7a70a28b1633
+msgid "Dropdown menu for action button scaleup System VM shows all service offering inc..."
+msgstr ""
+
+#: ../../about.rst:966
+# 94c82b371e014e7db572a651a1d5a824
+msgid "`CLOUDSTACK-2453 <https://issues.apache.org/jira/browse/CLOUDSTACK-2453>`_"
+msgstr ""
+
+#: ../../about.rst:966
+# 51034807cd4e4520ba084944db0e4554
+msgid "Select view dropdown under \"Network\" is listing the options in the absence of ad..."
+msgstr ""
+
+#: ../../about.rst:967
+# b0f18de078274cd285d7efe5a03e5a4b
+msgid "`CLOUDSTACK-2464 <https://issues.apache.org/jira/browse/CLOUDSTACK-2464>`_"
+msgstr ""
+
+#: ../../about.rst:967
+# 4bcccc8e991e484886d3f5fb30acc412
+msgid "[GSLB][UI] \"Add GSLB\" wizard doesn't prompt for \"PersistenceType\"..."
+msgstr ""
+
+#: ../../about.rst:968
+# 0433e6fc645d4d8fa034ce5b0bf63ce6
+msgid "`CLOUDSTACK-2533 <https://issues.apache.org/jira/browse/CLOUDSTACK-2533>`_"
+msgstr ""
+
+#: ../../about.rst:968
+# aa4c2b01e0c04f75863646c8609878f5
+msgid "Add Network to VM dialog should only show those network in the dropdown which ar..."
+msgstr ""
+
+#: ../../about.rst:969
+# 3cd97e91d6a1494eb443dd53eac4aa64
+msgid "`CLOUDSTACK-2535 <https://issues.apache.org/jira/browse/CLOUDSTACK-2535>`_"
+msgstr ""
+
+#: ../../about.rst:969
+# 0101c1f722244acaa1ba52f563626d08
+msgid "Cleanup port-profiles that gets created on Nexus switch as part of network clean..."
+msgstr ""
+
+#: ../../about.rst:970
+# 37c4a36817b449e9972b80ad060501e5
+msgid "`CLOUDSTACK-2559 <https://issues.apache.org/jira/browse/CLOUDSTACK-2559>`_"
+msgstr ""
+
+#: ../../about.rst:970
+# da49f93acbc0417eb9d4a91a39995de6
+msgid "[UI]Resource Name should not be present in UI as it is not available in listASA1..."
+msgstr ""
+
+#: ../../about.rst:971
+# 9126137d611b484eb865a2c06479b140
+msgid "`CLOUDSTACK-2605 <https://issues.apache.org/jira/browse/CLOUDSTACK-2605>`_"
+msgstr ""
+
+#: ../../about.rst:971
+# 20a378f44363495daf91c485585537ed
+msgid "Add Network to VM Command button should not be displayed for VMs belonging to B..."
+msgstr ""
+
+#: ../../about.rst:972
+# 71c4c344ffdc4e958ec6f5f7eb89de43
+msgid "`CLOUDSTACK-2697 <https://issues.apache.org/jira/browse/CLOUDSTACK-2697>`_"
+msgstr ""
+
+#: ../../about.rst:972
+# 087ec5baecbd46b8846e00bc1da9f9a8
+msgid "cluster id in alert message is null {alertType:: 1 // dataCenterId:: 1 // podId:..."
+msgstr ""
+
+#: ../../about.rst:973
+# 4e8a9f82abd7415f92b69d5f019956d9
+msgid "`CLOUDSTACK-2714 <https://issues.apache.org/jira/browse/CLOUDSTACK-2714>`_"
+msgstr ""
+
+#: ../../about.rst:973
+# b9a8751bb231427d85be7a486e346356
+msgid "Setting tab should not be visible for user accounts ..."
+msgstr ""
+
+#: ../../about.rst:974
+# 7b464c32172d4ed098b0ce969b998693
+msgid "`CLOUDSTACK-2951 <https://issues.apache.org/jira/browse/CLOUDSTACK-2951>`_"
+msgstr ""
+
+#: ../../about.rst:974
+# e98639016fea473b8b49ca4284a11d10
+msgid "[UI][Mixed-Zone-Management] during \"add Instance\" wizard, listTemplates API is n..."
+msgstr ""
+
+#: ../../about.rst:975
+# 4d48945fe87b49b6a8ae81013698783e
+msgid "`CLOUDSTACK-2993 <https://issues.apache.org/jira/browse/CLOUDSTACK-2993>`_"
+msgstr ""
+
+#: ../../about.rst:975
+# 8d80e722daef45178724195a133b6709
+msgid "[PortableIPRange] remove some of the unused columns if they are not required fro..."
+msgstr ""
+
+#: ../../about.rst:976
+# 54ac3fa8558842c398ccdc38f1ced838
+msgid "`CLOUDSTACK-3025 <https://issues.apache.org/jira/browse/CLOUDSTACK-3025>`_"
+msgstr ""
+
+#: ../../about.rst:976
+# b7b3e51f968948999a7c60937b897275
+msgid "The page and pagesize parameters are not working in ListCfgsByCmds with zoneid s..."
+msgstr ""
+
+#: ../../about.rst:977
+# dd940c1b0f9a409c8915a129da92f71f
+msgid "`CLOUDSTACK-3063 <https://issues.apache.org/jira/browse/CLOUDSTACK-3063>`_"
+msgstr ""
+
+#: ../../about.rst:977
+# 0bc901711ad14ab8833396c81147cca4
+msgid "[UI]Dedicating a host to non-root domain which has instances of other domain(ro..."
+msgstr ""
+
+#: ../../about.rst:978
+# ac414d5911ce41269d2fefab50309adc
+msgid "`CLOUDSTACK-3101 <https://issues.apache.org/jira/browse/CLOUDSTACK-3101>`_"
+msgstr ""
+
+#: ../../about.rst:978
+# 3eba9b21c31641a781a0c4ddb2bc01a5
+msgid "[DR] list* APIs are not working based on the display* flags ..."
+msgstr ""
+
+#: ../../about.rst:979
+# f7478719c1de492aa2cf09123878a13d
+msgid "`CLOUDSTACK-3225 <https://issues.apache.org/jira/browse/CLOUDSTACK-3225>`_"
+msgstr ""
+
+#: ../../about.rst:979
+# 5256cc0bd9364f87893c336a74f84eb7
+msgid "Multiple NPEs when cloudstack-management service is restarted with incomplete ta..."
+msgstr ""
+
+#: ../../about.rst:980
+# 5cfa9678dc1e43d59b38335ad8f91b4b
+msgid "`CLOUDSTACK-3265 <https://issues.apache.org/jira/browse/CLOUDSTACK-3265>`_"
+msgstr ""
+
+#: ../../about.rst:980
+# e9452d8251b643a4b03bce41674f4808
+msgid "[Health Check for NS LB]Failure to create a lb health check policy returns a API..."
+msgstr ""
+
+#: ../../about.rst:981
+# be48a8cbb5e349f89e66aadcaa541ef0
+msgid "`CLOUDSTACK-3325 <https://issues.apache.org/jira/browse/CLOUDSTACK-3325>`_"
+msgstr ""
+
+#: ../../about.rst:981
+# 230ac59306494ea39197506b81def3eb
+msgid "[UI] [GSLB]: add text box to specify weight for each load balancer participating..."
+msgstr ""
+
+#: ../../about.rst:982
+# 2705c0569cab4d6b90594a92ec65bf31
+msgid "`CLOUDSTACK-3406 <https://issues.apache.org/jira/browse/CLOUDSTACK-3406>`_"
+msgstr ""
+
+#: ../../about.rst:982
+# a8db221ce45a462aa6c2e05bc2d2eb7f
+msgid "UI: ZWPS: Zone wizard: Primary storage creation failed after \"fix error\" in \"add..."
+msgstr ""
+
+#: ../../about.rst:983
+# cf74cfd96dad473fb014d18a35250300
+msgid "`CLOUDSTACK-3477 <https://issues.apache.org/jira/browse/CLOUDSTACK-3477>`_"
+msgstr ""
+
+#: ../../about.rst:983
+# 0fefc1717380441c884cfaaf701079a9
+msgid "resizeDataVolume doesn't return proper error message when trying to shrink volum..."
+msgstr ""
+
+#: ../../about.rst:984
+# d45364bf4020433a913170368f609aab
+msgid "`CLOUDSTACK-3553 <https://issues.apache.org/jira/browse/CLOUDSTACK-3553>`_"
+msgstr ""
+
+#: ../../about.rst:984
+# 184036e307fd4f178ececf263bca2e80
+msgid "[UI]UI remains in the processing state forever when it failed to delete primary ..."
+msgstr ""
+
+#: ../../about.rst:985
+# c83f20fc84834a368caa9314832e54c2
+msgid "`CLOUDSTACK-3671 <https://issues.apache.org/jira/browse/CLOUDSTACK-3671>`_"
+msgstr ""
+
+#: ../../about.rst:985
+# 6c9eb98bd694461dba8f878670819297
+msgid "Set Host, Management Network and Storage Network Properly when there are multipl..."
+msgstr ""
+
+#: ../../about.rst:986
+# 8371c5905f8f4e5bac7ba985216659a3
+msgid "`CLOUDSTACK-3815 <https://issues.apache.org/jira/browse/CLOUDSTACK-3815>`_"
+msgstr ""
+
+#: ../../about.rst:986
+# f7cd0dc26cf648d3bdb020562cea6331
+msgid "\"SNAPSHOT.CREATE\" event's states are not registered on the events table ..."
+msgstr ""
+
+#: ../../about.rst:987
+# 8ed515eec0e24857853cbf89a631c552
+msgid "`CLOUDSTACK-3895 <https://issues.apache.org/jira/browse/CLOUDSTACK-3895>`_"
+msgstr ""
+
+#: ../../about.rst:987
+# ca4f125698734ec2a5122e644275964e
+msgid "VM Migration across VMWARE clusters which are added with different switches(Stan..."
+msgstr ""
+
+#: ../../about.rst:988
+# 85e8ff947d084dd7854ab375d940dd59
+msgid "`CLOUDSTACK-3896 <https://issues.apache.org/jira/browse/CLOUDSTACK-3896>`_"
+msgstr ""
+
+#: ../../about.rst:988
+# bb7ceed6e27445e4b714a9b97059137f
+msgid "[PrimaryStorage] deleteStoragePool is not kicking GC for the downloaded system v..."
+msgstr ""
+
+#: ../../about.rst:989
+# 80946f9e1d0e403980f58aa5f38cc72b
+msgid "`CLOUDSTACK-3994 <https://issues.apache.org/jira/browse/CLOUDSTACK-3994>`_"
+msgstr ""
+
+#: ../../about.rst:989
+# d2eb7ba4d45f47e5b811bf87a2265439
+msgid "Wrong error notification is generated when Primary storage (Cluster wide) is add..."
+msgstr ""
+
+#: ../../about.rst:990
+# 36ecfa62f5374e4997c2097a2e5fded0
+msgid "`CLOUDSTACK-3995 <https://issues.apache.org/jira/browse/CLOUDSTACK-3995>`_"
+msgstr ""
+
+#: ../../about.rst:990
+# bad0ef8ab93941b79b098112471e1747
+msgid "No error notification is generated when Primary storage (Zonelevel) is added wit..."
+msgstr ""
+
+#: ../../about.rst:991
+# 3a6ea2da46bf4583b7e963b661b54ae6
+msgid "`CLOUDSTACK-4071 <https://issues.apache.org/jira/browse/CLOUDSTACK-4071>`_"
+msgstr ""
+
+#: ../../about.rst:991
+# 1ce38dc6184444e086d00b9b1fd04f99
+msgid "[UI] - Word 'Default' is misspelled in descripiton of integration.api.port under..."
+msgstr ""
+
+#: ../../about.rst:992
+# c0007d2c93044bf99b095370c615cd21
+msgid "`CLOUDSTACK-4183 <https://issues.apache.org/jira/browse/CLOUDSTACK-4183>`_"
+msgstr ""
+
+#: ../../about.rst:992
+# 2ed3c6d02b474efdbb1ce654717060cd
+msgid "[Non-Contiguous VLAN] Typos Appear in an Error Message..."
+msgstr ""
+
+#: ../../about.rst:993
+# 9b70ea321e5b4f1686c2c85c6effa7f9
+msgid "`CLOUDSTACK-5033 <https://issues.apache.org/jira/browse/CLOUDSTACK-5033>`_"
+msgstr ""
+
+#: ../../about.rst:993
+# a4955022f36b4cf5b266a6b2375b9c00
+msgid "ipaddress in management-server.log and api.log are wrong if management servers i..."
+msgstr ""
+
+#: ../../about.rst:994
+# b206de9da37d4f21b9fdf71ea84ed410
+msgid "`CLOUDSTACK-5309 <https://issues.apache.org/jira/browse/CLOUDSTACK-5309>`_"
+msgstr ""
+
+#: ../../about.rst:994
+# 636eb801e14e4cb99089f40959d90aac
+msgid "version number and requires upgrade fields are not displayed for routers when na..."
+msgstr ""
+
+#: ../../about.rst:995
+# 1e0b3de7dabd42efb0f8e58b0fdfe23a
+msgid "`CLOUDSTACK-5383 <https://issues.apache.org/jira/browse/CLOUDSTACK-5383>`_"
+msgstr ""
+
+#: ../../about.rst:995
+# 73fcaca57140407c8792a19a593bf46a
+msgid "Multiselect actions are not reset when a multiselect action is performed..."
+msgstr ""
+
+#: ../../about.rst:996
+# e2c36d9ee109437787c7f790163e29fc
+msgid "`CLOUDSTACK-5524 <https://issues.apache.org/jira/browse/CLOUDSTACK-5524>`_"
+msgstr ""
+
+#: ../../about.rst:996
+# dd855f85311343258dc38de841f135a5
+msgid "[UI]\"root disk size\" field should be removed from the add instance wizard since ..."
+msgstr ""
+
+#: ../../about.rst:997
+# 73ee1275ea204ae79c6c82b8906c5bb5
+msgid "`CLOUDSTACK-5824 <https://issues.apache.org/jira/browse/CLOUDSTACK-5824>`_"
+msgstr ""
+
+#: ../../about.rst:997
+# 26bef1d1e89546788c6a884da12ce926
+msgid "Delete snapshot UI always success..."
+msgstr ""
+
+#: ../../about.rst:998
+# 056dbd72918245b09d116ea105d79278
+msgid "`CLOUDSTACK-5885 <https://issues.apache.org/jira/browse/CLOUDSTACK-5885>`_"
+msgstr ""
+
+#: ../../about.rst:998
+# e3f62bba080b450b9f164f5b0847f14c
+msgid "When process receives error, loading overlay on listView element does not disapp..."
+msgstr ""
+
+#: ../../about.rst:999
+# f7ca472d1e224ce79149f204a00048b8
+msgid "`CLOUDSTACK-5912 <https://issues.apache.org/jira/browse/CLOUDSTACK-5912>`_"
+msgstr ""
+
+#: ../../about.rst:999
+# 0f15765758da4cad8200f0decb588c1c
+msgid "WARN [c.c.h.v.m.HttpNfcLeaseMO] (Thread-28:null) Unexpected exception..."
+msgstr ""
+
+#: ../../about.rst:1000
+# c1f7f973391041c3b69f90eae30ce69d
+msgid "`CLOUDSTACK-5522 <https://issues.apache.org/jira/browse/CLOUDSTACK-5522>`_"
+msgstr ""
+
+#: ../../about.rst:1000
+# 5cd7fcc7c9ba4472afab041350028c5f
+msgid "Need of one more column i.e., \"Name\" at Home>Storage - Snapshots..."
+msgstr ""
+
+#: ../../about.rst:1001
+# ebdb64c792754bd795a01b47c7c04262
+msgid "`CLOUDSTACK-5904 <https://issues.apache.org/jira/browse/CLOUDSTACK-5904>`_"
+msgstr ""
+
+#: ../../about.rst:1001
+# 209d812fb98b48c8b9efb9602b2a75b8
+msgid "Small UI bug..."
+msgstr ""
+
diff --git a/source/releasenotes/locale/pot/api-changes.pot b/source/releasenotes/locale/pot/api-changes.pot
new file mode 100644
index 0000000..99b23aa
--- /dev/null
+++ b/source/releasenotes/locale/pot/api-changes.pot
@@ -0,0 +1,264 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 10:50-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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-changes.rst:17
+# ba3c427d54514fcbb45333056ddac76e
+msgid "API Changes Introduced in 4.3"
+msgstr ""
+
+#: ../../api-changes.rst:20
+# ac0cebd35d5147bfa3289ae8831108dc
+msgid "Hyper-V"
+msgstr ""
+
+#: ../../api-changes.rst:23
+#: ../../api-changes.rst:34
+#: ../../api-changes.rst:46
+#: ../../api-changes.rst:61
+#: ../../api-changes.rst:85
+# 955a92c6c2ff437eaa1b01299be0a430
+# 3fb690a5662046aea3941f9782a3003f
+# 4133920bc75849b496db274486745470
+# f084afe1d38443bcad6f69b21bdc9a4e
+# 3793b324cc7446ecae1de674c9e36250
+msgid "API"
+msgstr ""
+
+#: ../../api-changes.rst:23
+#: ../../api-changes.rst:34
+#: ../../api-changes.rst:46
+#: ../../api-changes.rst:61
+#: ../../api-changes.rst:85
+# 21d5370f36d345bc894fc1200e4081f9
+# c623048b8bf94859b0b097f12ee74713
+# aa321543f351469aa8bf9f4c69570632
+# b4620725124f4ca39d0801d26ba75523
+# a69e132cf53544b792e5f1353e2c76bb
+msgid "Description"
+msgstr ""
+
+#: ../../api-changes.rst:25
+# f84c6a42fdca46cead1e193c01ea0f36
+msgid "addPrimaryStorage"
+msgstr ""
+
+#: ../../api-changes.rst:25
+#: ../../api-changes.rst:27
+# b7b1569caab44ee194d04cfa2f093cd7
+# d96dec8d2ed94fcfa19ee61b6bf47ea4
+msgid "To this existing API, the following field has been added: smb"
+msgstr ""
+
+#: ../../api-changes.rst:27
+# 7e113e5e8d4a433ba8e474ad294bf3a6
+msgid "addImageStore"
+msgstr ""
+
+#: ../../api-changes.rst:31
+# ea6f6b8d8bea4bfb8611e410aa23b03b
+msgid "Reporting CPU Sockets"
+msgstr ""
+
+#: ../../api-changes.rst:36
+# d4e484335c9a41bdb56d8b41199bea68
+msgid "listhost"
+msgstr ""
+
+#: ../../api-changes.rst:36
+# 969d419ca1104937baa79b79992ae9c3
+msgid "To this existing API, the following request parameter has been added: hypervisor."
+msgstr ""
+
+#: ../../api-changes.rst:39
+# 428ae0b866d7410894881bb74ea18644
+msgid "The new response parameter added is: cpusockets"
+msgstr ""
+
+#: ../../api-changes.rst:43
+# 7b4b0cd175c84154970c81e7cdc7b3a9
+msgid "Publishing Alerts Using the Web ROOT Admin API"
+msgstr ""
+
+#: ../../api-changes.rst:48
+# 8802e94706de4386a95d3cc54757287d
+msgid "generateAlert"
+msgstr ""
+
+#: ../../api-changes.rst:48
+# 7afd7ac1a4374ddfade68ae4b7145077
+msgid "A new API has been added to generate and publish alerts for usage services. The usage services can be installed on a different host or the same host where the Management Server is running. This API is available only to the Root Admin."
+msgstr ""
+
+#: ../../api-changes.rst:53
+# 688d56d7e36344789602041c66ee2eb9
+msgid "listAlerts"
+msgstr ""
+
+#: ../../api-changes.rst:53
+# 719e52a73f9c4c65b1307d517d862602
+msgid "To this existing API, a new response parameter has been added: name. An alert can be searched on the basis of alert name."
+msgstr ""
+
+#: ../../api-changes.rst:58
+# d77837111f134448a932b10f2311b330
+msgid "Dynamic Compute Offering"
+msgstr ""
+
+#: ../../api-changes.rst:63
+# ae3bac83e3ba4ab4955af55be5412bcf
+msgid "DeployVM"
+msgstr ""
+
+#: ../../api-changes.rst:63
+#: ../../api-changes.rst:66
+#: ../../api-changes.rst:69
+#: ../../api-changes.rst:73
+#: ../../api-changes.rst:76
+# 1ea304c847ba4faf98010b8982060897
+# 3e9cbab447274b4f8f7b16468d5b3154
+# cef25de8237949318623399efa3525ae
+# 991f9597f76140d09457d911571620f4
+# de469f85256d4cb1942213fdc0b7a0de
+msgid "To this existing API, the following request parameter has been added: details."
+msgstr ""
+
+#: ../../api-changes.rst:66
+# 895d5daaa7774843ad94df397c9249d3
+msgid "ScaleVM"
+msgstr ""
+
+#: ../../api-changes.rst:69
+# 763e4875a4704cb9aeae3c5ef36e62bf
+msgid "ScaleSystemVM"
+msgstr ""
+
+#: ../../api-changes.rst:73
+# aca413becd874b3e94e98dbfb5841368
+msgid "UpgradeVM"
+msgstr ""
+
+#: ../../api-changes.rst:76
+# b63a6cb0827644ec8d8ff4162f7eb843
+msgid "UpgradeSystemVM"
+msgstr ""
+
+#: ../../api-changes.rst:82
+# 04d15e5183ab475885ff23f884a7dbbe
+msgid "Enhanced Upgrade for Virtual Routers"
+msgstr ""
+
+#: ../../api-changes.rst:87
+# 9f3806d0d16c41699e0215c2c130abda
+msgid "upgradeRouterTemplate"
+msgstr ""
+
+#: ../../api-changes.rst:87
+# c6ec881a8a154d5ba133c8fd5f74d7da
+msgid "This is a new API which has been added in this release."
+msgstr ""
+
+#: ../../api-changes.rst:89
+# befa20db57a74be8a359230be1af24ce
+msgid "The following are the request parameters:"
+msgstr ""
+
+#: ../../api-changes.rst:91
+# 6f699977277045c79e59ec79cab3b502
+msgid "id: Upgrade the specified VR"
+msgstr ""
+
+#: ../../api-changes.rst:93
+# b74ed7f780cf4c22b3e53e23a5cb8e1f
+msgid "zone\\_id : Upgrade the VRs in the specified zone."
+msgstr ""
+
+#: ../../api-changes.rst:95
+# be1c0c2053f1482796bede31d6f34259
+msgid "pod\\_id : Upgrade the VRs in the specified pod."
+msgstr ""
+
+#: ../../api-changes.rst:97
+# 52429b1c63df4c6396485c3faacfaffc
+msgid "cluster\\_id : Upgrade the VRs in the specified cluster."
+msgstr ""
+
+#: ../../api-changes.rst:99
+# 3e38ba91cf38452fbfd372fd80ac1570
+msgid "domain\\_id : Upgrade the VRs belonging to the specified domain."
+msgstr ""
+
+#: ../../api-changes.rst:102
+# e963e6310c1f4c1ebf55d701b9ab3dc9
+msgid "account\\_id : Upgrade the VRs belonging to the specified account."
+msgstr ""
+
+#: ../../api-changes.rst:106
+# 5de6819e7d1e44b7ae295686d139ff4c
+msgid "listRouters"
+msgstr ""
+
+#: ../../api-changes.rst:106
+# 4adb9f6a1e194f599eb100d4630f6147
+msgid "For this existing API, the following request parameters has been added:"
+msgstr ""
+
+#: ../../api-changes.rst:109
+# 6777db6a54104f2487b901226f296040
+msgid "version: Lists routers by specified version."
+msgstr ""
+
+#: ../../api-changes.rst:111
+# b1f9333e4c6a4ab3adb13836ac2cc5a2
+msgid "zone\\_id : lists routers in specified zone."
+msgstr ""
+
+#: ../../api-changes.rst:113
+# f9966a08aeb440de936e8767c3f57049
+msgid "pod\\_id : Lists routers in the specified pod."
+msgstr ""
+
+#: ../../api-changes.rst:115
+# 63feeeb27fc746ebbb4b24247c3a6e90
+msgid "cluster\\_id : Lists routers in the specified cluster."
+msgstr ""
+
+#: ../../api-changes.rst:117
+# d0f7cd6a28ed4a90999cd86dea6f3c4f
+msgid "domain\\_id : Lists routers owned by specified domain."
+msgstr ""
+
+#: ../../api-changes.rst:119
+# 791fa005ad454dccbea24b78ba0f89d9
+msgid "account: Lists routers owned by specified account."
+msgstr ""
+
+#: ../../api-changes.rst:121
+# 83e77c83dc4d42f4b140f2b1f0a8e0b4
+msgid "The following response parameters has been added:"
+msgstr ""
+
+#: ../../api-changes.rst:123
+# 1172e9fa8e9c4d259cd76493bc7b6c79
+msgid "version : (String) The router version. For example, 4.3.0."
+msgstr ""
+
+#: ../../api-changes.rst:125
+# ae72e022d08344519e876a7f109ec5a0
+msgid "requiresupgrade: (Boolean) The flag to indicate if the router template requires an upgrade."
+msgstr ""
+
diff --git a/source/releasenotes/locale/pot/compat.pot b/source/releasenotes/locale/pot/compat.pot
new file mode 100644
index 0000000..e3e2037
--- /dev/null
+++ b/source/releasenotes/locale/pot/compat.pot
@@ -0,0 +1,178 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 10:50-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../compat.rst:17
+# 7dcdc4217c22473a81ac668b21647b37
+msgid "Compatibility Matrix"
+msgstr ""
+
+#: ../../compat.rst:20
+# 8d4b52f9b66d448b9a69ab17165262a0
+msgid "Supported OS Versions for Management Server"
+msgstr ""
+
+#: ../../compat.rst:22
+# 0ae4756c5d53482ca9345cb559fd81ed
+msgid "This section lists the operating systems that are supported for running CloudStack Management Server. Note that specific versions of the operating systems are tested, so compatibility with CentOS 6.3 may not indicate compatibility with CentOS 6.2, 6.1 and so on."
+msgstr ""
+
+#: ../../compat.rst:29
+# 0ea47e988e0b4b05a09b11c13865f105
+msgid "RHEL versions 5.5, 6.2, 6.3, and 6.4"
+msgstr ""
+
+#: ../../compat.rst:33
+# c33bff6adc4341f5843ad17cd93ad74a
+msgid "CentOS versions 6.3, and 6.4"
+msgstr ""
+
+#: ../../compat.rst:37
+# e158c85352234b2b8fcb1348693fc4bd
+msgid "Ubuntu 12.04 LTS"
+msgstr ""
+
+#: ../../compat.rst:40
+# 9e37962eae2943649f2adb63d92cee5e
+msgid "Supported Hypervisor Versions"
+msgstr ""
+
+#: ../../compat.rst:42
+# 1816866bc94a42b485496d310764cfd1
+msgid "CloudStack supports three hypervisor families, XenServer with XAPI, KVM, and VMware with vSphere."
+msgstr ""
+
+#: ../../compat.rst:47
+# fca8daf72ca94ba6b5b9e318e7138d92
+msgid "Windows Server 2012 R2 (with Hyper-V Role enabled)"
+msgstr ""
+
+#: ../../compat.rst:51
+# 523e97bb92534e7a8ed52ad24b2fec3a
+msgid "Hyper-V 2012 R2"
+msgstr ""
+
+#: ../../compat.rst:55
+# 731596ff7ace498086168e86a25404f6
+msgid "CentOS 6.2 with KVM"
+msgstr ""
+
+#: ../../compat.rst:59
+# 960c87f799574ed89dfae43d8cf51363
+msgid "Red Hat Enterprise Linux 6.2 with KVM"
+msgstr ""
+
+#: ../../compat.rst:63
+# 8006ba4927364513ba27467d64f04930
+msgid "XenServer 6.0.2 (with Hotfix)"
+msgstr ""
+
+#: ../../compat.rst:67
+# 8ebbef6847bb4d5292b6fb06e7360d04
+msgid "XenServer versions 6.1 and 6.2 SPI with latest hotfixes"
+msgstr ""
+
+#: ../../compat.rst:71
+# 4f2624b282df44c6bc750bffab900897
+msgid "VMware versions 5.0, 5.1, and 5.5"
+msgstr ""
+
+#: ../../compat.rst:75
+# a569cbfdefd14cb59f8bc1300d03a55a
+msgid "Bare metal hosts are supported, which have no hypervisor. These hosts can run the following operating systems:"
+msgstr ""
+
+#: ../../compat.rst:80
+# 8a615763e58c42beaaa685396a01ec76
+msgid "RHEL or CentOS, v6.2 or 6.3"
+msgstr ""
+
+#: ../../compat.rst:82
+# 652796f466944c76bbb2d46ad1c8b9ba
+msgid "Use libvirt version 0.9.10 for CentOS 6.3"
+msgstr ""
+
+#: ../../compat.rst:86
+# eebaea9300d3459da093f63732a176f6
+msgid "Fedora 17"
+msgstr ""
+
+#: ../../compat.rst:90
+# 99834b9a6c884d93b63e0860fe563fee
+msgid "Ubuntu 12.04"
+msgstr ""
+
+#: ../../compat.rst:92
+# e2141af52dfb4b98875d035e5b1a3e73
+msgid "For more information, see the Hypervisor Compatibility Matrix in the CloudStack Installation Guide."
+msgstr ""
+
+#: ../../compat.rst:96
+# 5552b7e5a3af40029b60fb85a52f0502
+msgid "Supported External Devices"
+msgstr ""
+
+#: ../../compat.rst:100
+# eb219ee7b9f045b8bd8c22cec06e6263
+msgid "Netscaler VPX and MPX versions 9.3 and 10.e"
+msgstr ""
+
+#: ../../compat.rst:104
+# 718d33d0f5654995834a3216a78fed28
+msgid "Netscaler SDX version 9.3"
+msgstr ""
+
+#: ../../compat.rst:108
+# 3cfc8160c41c42fb81ff964f23558e77
+msgid "SRX (Model srx100b) versions 10.3 or higher"
+msgstr ""
+
+#: ../../compat.rst:112
+# 321b963dfd42471ea19cdde2c11d217d
+msgid "F5 10.1.0 (Build 3341.1084)"
+msgstr ""
+
+#: ../../compat.rst:115
+# abdd765edd9445d2ba6b0f20a180754e
+msgid "Supported Browsers"
+msgstr ""
+
+#: ../../compat.rst:117
+# f104084e36f7417e9f8acc08e5e266f6
+msgid "The CloudStack Web-based UI should be compatible with any modern browser, but it's possible that some browsers will not render portions of the UI reliably, depending on their support of Web standards. For best results, one of the following browsers recommended:"
+msgstr ""
+
+#: ../../compat.rst:124
+# fb3a357088db4d04994c6ac2257df6ac
+msgid "Internet Explorer versions 10 and 11"
+msgstr ""
+
+#: ../../compat.rst:128
+# 3a1e6ffa3b4e42a9ac6c5ac93ee69739
+msgid "Firefox version 26 or lower"
+msgstr ""
+
+#: ../../compat.rst:132
+# 2e628ae20f68407086f328f8b8f8d50f
+msgid "Google Chrome version 31"
+msgstr ""
+
+#: ../../compat.rst:136
+# 25919615c96d4fcdadc243cd8780eabd
+msgid "Safari 5"
+msgstr ""
+
diff --git a/source/releasenotes/locale/pot/index.pot b/source/releasenotes/locale/pot/index.pot
new file mode 100644
index 0000000..70c8e25
--- /dev/null
+++ b/source/releasenotes/locale/pot/index.pot
@@ -0,0 +1,38 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 10:50-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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:22
+# 7d5bf8f1976649478c6426b1d3aef1d5
+msgid "Welcome to Apache CloudStack Release Notes"
+msgstr ""
+
+#: ../../index.rst:24
+# c1a368cd41964089b29311f960268dd8
+msgid "This section describes the operating systems, browsers, and hypervisors that have been newly tested and certified compatible with CloudStack 4.3. Most earlier OS and hypervisor versions are also still supported for use with 4.3 It might work well on other platforms, but the platforms listed below are the ones that are specifically tested against and are more likely to be able to help troubleshoot if you run into any issues."
+msgstr ""
+
+#: ../../index.rst:32
+# 598272357f4545e0a3698227daf4d4c5
+msgid "This document contains information specific to this release of CloudStack, including upgrade instructions from prior releases, new features added to CloudStack, API changes, and issues fixed in the release. For installation instructions, please see the `Installation Guide <http://cloudstack-installation.readthedocs.org/en/latest/>`__. For usage and administration instructions, please see the `CloudStack Administrator's Guide <http://cloudstack-administration.readthedocs.org/en/latest/>`__."
+msgstr ""
+
+#: ../../index.rst:38
+# 742b63f90051452a841b8b2bb2e0a8c6
+msgid "Contents:"
+msgstr ""
+
diff --git a/source/releasenotes/locale/pot/rnotes.pot b/source/releasenotes/locale/pot/rnotes.pot
new file mode 100644
index 0000000..e1f188b
--- /dev/null
+++ b/source/releasenotes/locale/pot/rnotes.pot
@@ -0,0 +1,2328 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 10:50-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../rnotes.rst:18
+# 54c7454410d84e6594ce715ce80428db
+msgid "Upgrade Instructions for 4.3"
+msgstr ""
+
+#: ../../rnotes.rst:20
+# 57d91f3b7f514ea5b4ce6c7dc9fae484
+msgid "This section contains upgrade instructions from prior versions of CloudStack to Apache CloudStack 4.3. We include instructions on upgrading to Apache CloudStack from pre-Apache versions of Citrix CloudStack (last version prior to Apache is 3.0.2) and from the releases made while CloudStack was in the Apache Incubator."
+msgstr ""
+
+#: ../../rnotes.rst:26
+# 763e012b1cbb4dbfb8b2c1a5defd86e1
+msgid "If you run into any issues during upgrades, please feel free to ask questions on users@cloudstack.apache.org or dev@cloudstack.apache.org."
+msgstr ""
+
+#: ../../rnotes.rst:30
+# f592714fe95442b58f46cbd186ab8d6b
+msgid "Upgrade from 4.2.0 to 4.3"
+msgstr ""
+
+#: ../../rnotes.rst:32
+# 917061081ce244cfa8e2220092d88b74
+msgid "This section will guide you from CloudStack 4.2 to CloudStack 4.3."
+msgstr ""
+
+#: ../../rnotes.rst:34
+#: ../../rnotes.rst:663
+#: ../../rnotes.rst:1197
+# 839670a6c8404e6689c28e22e9beb7e9
+# eece6c1c6b404f65a19955ad53a17a69
+# fd68172c2b124becb308ed2d888b75ed
+msgid "Any steps that are hypervisor-specific will be called out with a note."
+msgstr ""
+
+#: ../../rnotes.rst:36
+#: ../../rnotes.rst:665
+#: ../../rnotes.rst:1201
+# 20506c6042314b5997698ca5ecdd32bc
+# ecf5f433d7864bbb85a84b2eb594e262
+# 94af5eeae7374a17bad1d4de092723a3
+msgid "We recommend reading through this section once or twice before beginning your upgrade procedure, and working through it on a test system before working on a production system."
+msgstr ""
+
+#: ../../rnotes.rst:40
+#: ../../rnotes.rst:678
+#: ../../rnotes.rst:1223
+#: ../../rnotes.rst:1641
+# 610f07ad15974e7196b2525a32b7b5cb
+# c073d7072a1d448c9fccf973192b0c97
+# 2fc30d45bf6e431caa140fc3a8b608bf
+# 7e7237f14b174ac09084ae1b9298408e
+msgid "The following upgrade instructions should be performed regardless of hypervisor type."
+msgstr ""
+
+#: ../../rnotes.rst:46
+# 1a94b234a76c4ec3b5c85c9c69a4c5a3
+msgid "While running the existing 4.2.0 system, log in to the UI as root administrator."
+msgstr ""
+
+#: ../../rnotes.rst:51
+#: ../../rnotes.rst:687
+#: ../../rnotes.rst:1232
+#: ../../rnotes.rst:1650
+#: ../../rnotes.rst:2475
+# 87a195264f014fafbcacf225ee49b60b
+# 9fed87b0bb5a4d09aae99a02c1846689
+# 26927a7715d34d0d953e701f900ea4d9
+# d9bc4a3467a74b24b867b1a0a1caa7b5
+# e0ec5d46b97d44609764fd49dfb9543b
+msgid "In the left navigation bar, click Templates."
+msgstr ""
+
+#: ../../rnotes.rst:55
+#: ../../rnotes.rst:691
+#: ../../rnotes.rst:1236
+#: ../../rnotes.rst:1654
+#: ../../rnotes.rst:2479
+# 1460b4b9bc9f4b49897d8176ba4c18ea
+# ef1a66d85b964c02aad6e5bd7c9ff223
+# 4dc49fa62d6d41fda5ed15c69fe7d8ce
+# bfbcb45f64c84379a00a8c3e2cd4c6d0
+# 52dfafc4d6154db8a3d96e9451d751ca
+msgid "In Select view, click Templates."
+msgstr ""
+
+#: ../../rnotes.rst:59
+#: ../../rnotes.rst:695
+#: ../../rnotes.rst:1240
+#: ../../rnotes.rst:1658
+#: ../../rnotes.rst:2483
+# 7422067820c0448cb4f6415687b58ac9
+# fe2c9ff7bfa8453988c921b9e9e682e0
+# 1343f352d25b4016aa3f66b7395fdaeb
+# 6c9273ba79ab4c6c8ac374c1672f97b2
+# c6f38fb928704fa2811d411adbc16c44
+msgid "Click Register template."
+msgstr ""
+
+#: ../../rnotes.rst:61
+#: ../../rnotes.rst:697
+#: ../../rnotes.rst:1242
+#: ../../rnotes.rst:1660
+#: ../../rnotes.rst:2485
+# a76ecceb7ec74ea4bfb386b62103e7c3
+# 2e43da4879e5413980b0cbb4d1f72f81
+# b2c82fcc5b3e4b53b9b5b10b1f4e7b66
+# 8e701b724e54456b8ca1bbde10ae0401
+# fb7761768b634b5c9769ccc234f069d9
+msgid "The Register template dialog box is displayed."
+msgstr ""
+
+#: ../../rnotes.rst:65
+#: ../../rnotes.rst:701
+#: ../../rnotes.rst:1246
+#: ../../rnotes.rst:1664
+# 70b55ffc5f74419793e312019de9e564
+# 48518d425e5541379999468368d93944
+# faf7207893bc422098f1acb0f300245a
+# ca10148af6ed40148fd770eb5e279113
+msgid "In the Register template dialog box, specify the following values (do not change these):"
+msgstr ""
+
+#: ../../rnotes.rst:69
+#: ../../rnotes.rst:705
+#: ../../rnotes.rst:1250
+#: ../../rnotes.rst:1668
+#: ../../rnotes.rst:2493
+# fabaedd3a17741db9feaeaa9c362fb37
+# 07cdc119bb174abb9a6ba0908f42d98f
+# f84be91d03154ebba60ac0c21f123a4a
+# 0819fc5670a64cf985899d81eb6a0567
+# 0e0ef055e40148309d6b33f6f508fa0f
+msgid "Hypervisor"
+msgstr ""
+
+#: ../../rnotes.rst:69
+#: ../../rnotes.rst:705
+#: ../../rnotes.rst:1250
+#: ../../rnotes.rst:1668
+#: ../../rnotes.rst:2493
+# eecd155317fc4913af9ae17e5402fe0c
+# 44d451689de54435904df3eaed15c6f0
+# 39b27bcf07f94071befcc1805711deff
+# cf9d17e8177c4e93b9b67992e280ebfb
+# 29e46943e1444141a1114eeb88507893
+msgid "Description"
+msgstr ""
+
+#: ../../rnotes.rst:71
+#: ../../rnotes.rst:707
+#: ../../rnotes.rst:1252
+#: ../../rnotes.rst:1670
+#: ../../rnotes.rst:2495
+# d6afb75336f342f8a534be42065089fb
+# 532f8ff8909f456498a09b740bc4a771
+# cd57f897975941b9a72908e8980d3609
+# 8f2eff0c8c144754a71c6873c05fba77
+# a8a2066ef613402c92453d5557b1dfa8
+msgid "XenServer"
+msgstr ""
+
+#: ../../rnotes.rst:71
+#: ../../rnotes.rst:707
+#: ../../rnotes.rst:1252
+#: ../../rnotes.rst:1670
+#: ../../rnotes.rst:2495
+# 66f56c4c29964dc49d7849ae35f3ab41
+# 7354275f76ea42ddbcbec977ce04e605
+# 0d818adb6a2348e2a937d92162fb0d0a
+# bcf8b47f0fcd4c6c8df2eafcfa8a21bb
+# 04ff051f045c499b8ea2548a36c479ec
+msgid "Name: systemvm-xenserver-4.3"
+msgstr ""
+
+#: ../../rnotes.rst:73
+#: ../../rnotes.rst:709
+#: ../../rnotes.rst:1254
+#: ../../rnotes.rst:1672
+#: ../../rnotes.rst:2497
+# e653b05ef987495caf72f468b9f54088
+# 3ca05005c9484802aecfc51a71bad016
+# 343199a366194ae78ed699ba83825f21
+# 294c5a83fc154fdbaf0d85b5abb030c5
+# 44946d65c4c04a47a814c55aa2a4b2bd
+msgid "Description: systemvm-xenserver-4.3"
+msgstr ""
+
+#: ../../rnotes.rst:75
+#: ../../rnotes.rst:711
+#: ../../rnotes.rst:1256
+#: ../../rnotes.rst:1674
+#: ../../rnotes.rst:2499
+# a609d90e7d4c4bddbcb80a207c11a286
+# 66757efe5c6d40e1bac66e579369d368
+# a8b209e329fc41ce94ec334acd8dc4d0
+# a26c20ade808412ab062e4a910efcde5
+# bfaf491e156c4f9ab1e381a756900595
+msgid "URL: http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2"
+msgstr ""
+
+#: ../../rnotes.rst:78
+#: ../../rnotes.rst:103
+#: ../../rnotes.rst:128
+#: ../../rnotes.rst:714
+#: ../../rnotes.rst:739
+#: ../../rnotes.rst:764
+#: ../../rnotes.rst:1259
+#: ../../rnotes.rst:1284
+#: ../../rnotes.rst:1309
+#: ../../rnotes.rst:2502
+#: ../../rnotes.rst:2527
+#: ../../rnotes.rst:2552
+# de0fafc107fc49c3b6fbc36f8269f090
+# 8bbba7f914b9462899eadab5fe99a500
+# 90b1c14925764bcbb4fc5e37088cd019
+# 884e767f38e24dbd999a0e83acfe468d
+# cbb58b1d17dc4f689b54373fa72b56e7
+# a24107e19f334b0da5cd948e622d448a
+# 996bbb0c2d144c38b152e314f7a23232
+# e671eff0f36044eba588d538993a548c
+# f0aaee12a6f44476868b96b6fdd3c531
+# 2ca4ffa3c1f84c688eae9e77e09776b0
+# 5fa3f47e5f6547f1b37eaee9850f64ab
+# 80c606b15f08401f8f6a8f6cc92f506b
+msgid "Zone: Choose the zone where this hypervisor is used"
+msgstr ""
+
+#: ../../rnotes.rst:80
+#: ../../rnotes.rst:716
+#: ../../rnotes.rst:1261
+#: ../../rnotes.rst:1680
+#: ../../rnotes.rst:2504
+# fe7c9476f0514b018ce17653e4dfaf14
+# c341ba5d6d934a4c992e1f6acd331f62
+# 5b42af014a774e8d8dd54fdb8c23b303
+# 24a87f94fef44351a659f98f77747f4b
+# a6d3e78bba8f4bfcb966bee2e13cca0e
+msgid "Hypervisor: XenServer"
+msgstr ""
+
+#: ../../rnotes.rst:82
+#: ../../rnotes.rst:718
+#: ../../rnotes.rst:1263
+#: ../../rnotes.rst:1682
+#: ../../rnotes.rst:2506
+# 5554e0e0df47402c8cd7f4755b3d4868
+# 320573028f954ab98f16747898be6dc8
+# 42f4d9b411d84a60adc6ce2dd653d983
+# 56f769b429e049d89ca64fcde83dc0be
+# 22416e0f3d004d2688284421f68774c8
+msgid "Format: VHD"
+msgstr ""
+
+#: ../../rnotes.rst:84
+#: ../../rnotes.rst:109
+#: ../../rnotes.rst:134
+#: ../../rnotes.rst:720
+#: ../../rnotes.rst:745
+#: ../../rnotes.rst:770
+#: ../../rnotes.rst:1265
+#: ../../rnotes.rst:1290
+#: ../../rnotes.rst:1315
+#: ../../rnotes.rst:1684
+#: ../../rnotes.rst:1710
+#: ../../rnotes.rst:1736
+#: ../../rnotes.rst:2508
+#: ../../rnotes.rst:2533
+#: ../../rnotes.rst:2558
+# d1a09ebff7224e33ac7d506a813c135f
+# abad9407f6e940e182e25fe5a5bcc559
+# 24176593f87f48f3b1063c0bf4757d1a
+# 846d087370894ec997db899976c581ec
+# 77363b11bf8f45b2860fed0d89aded2c
+# 87f8d2767140463aad639149799f4b10
+# 53567f0780b140fc863f010767a1dd88
+# 8a62a060568e47108413074103342e9e
+# 255ae8f7fc4c4621871ce7dcdce1d8b5
+# e8b04e914e324ca292e1b7becd10526b
+# c5bc63756ae84c8eb56cc8bdbca0d4de
+# 0c94f10a791340a5969ed518669ef764
+# b9db27fc2ea046e89a7224f72a43b9bf
+# c42e4c649a594537b29df5cd32e4a9c6
+# 9b64303f1ab940228ad6ffa21b4b3708
+msgid "OS Type: Debian GNU/Linux 7.0 (64-bit) (or the highest Debian release number available in the dropdown)"
+msgstr ""
+
+#: ../../rnotes.rst:88
+#: ../../rnotes.rst:113
+#: ../../rnotes.rst:138
+#: ../../rnotes.rst:724
+#: ../../rnotes.rst:749
+#: ../../rnotes.rst:774
+#: ../../rnotes.rst:1269
+#: ../../rnotes.rst:1294
+#: ../../rnotes.rst:1319
+#: ../../rnotes.rst:1688
+#: ../../rnotes.rst:1714
+#: ../../rnotes.rst:1740
+#: ../../rnotes.rst:2512
+#: ../../rnotes.rst:2537
+#: ../../rnotes.rst:2562
+# 479ec153cf7744a58bf6baa44fe1c619
+# 24b8f48035d84b72a8f4c47323576ccf
+# a84fcb89af764c63bb3a034947720e7d
+# d271b9fb4ffe43e59fc78422db066959
+# 5f82c03996db4438b51606755ef7bdc5
+# 46df05a15ea14b3392b3033307cbdb7d
+# 780997a25ad34ba7a2fe4891411d9670
+# 504456709066415990989c9449524e06
+# 5f1f75483716496e9c99153f6c86ebfb
+# 333f78edb2754dffa05428377545ba64
+# 18d2f94dabae4361a399160cdaf8672a
+# e40c9d0e1f9348ec9dd645bdeb26c737
+# 85b52cf2fc2d43ba8e09c8956fe779c7
+# dada2cde337c4f53aa3c90663118bf9a
+# ab2f69b4810d40329f27aa52562da282
+msgid "Extractable: no"
+msgstr ""
+
+#: ../../rnotes.rst:90
+#: ../../rnotes.rst:115
+#: ../../rnotes.rst:140
+#: ../../rnotes.rst:726
+#: ../../rnotes.rst:751
+#: ../../rnotes.rst:776
+#: ../../rnotes.rst:1271
+#: ../../rnotes.rst:1296
+#: ../../rnotes.rst:1321
+#: ../../rnotes.rst:1690
+#: ../../rnotes.rst:1716
+#: ../../rnotes.rst:1742
+#: ../../rnotes.rst:2514
+#: ../../rnotes.rst:2539
+#: ../../rnotes.rst:2564
+# 32ec5ca5289e4f129ed8b9aeeb8ee595
+# 73d0634d1dc64dd4b73bfa7bc87ddd56
+# 30bbf2f539ef468c84d4915726ea4201
+# 22ed7912f287421993ea7305350b7be2
+# d4173d6cf7194f87b55b66cf62bdd149
+# 995aba5ec4c842a59e7a614550ebbc5e
+# 248d5aa2dc504fa8a76b5d555bab3d04
+# c7b4241023184c6982c36aa1e36b2416
+# e5be91f0f616411eaa9f1867b25ebe84
+# 5512ab3950c04d088703fd29f2480061
+# 18d0087fe2ba4ca39d320698ff00ef8d
+# 42128b849be24efea31e76b92f424fb5
+# e5130ebea45a4a5e8e72f57854852840
+# 2212dca5cb964150966626b0d26163c6
+# c58f8deb9dbd4b6980e3f74dce83bf63
+msgid "Password Enabled: no"
+msgstr ""
+
+#: ../../rnotes.rst:92
+#: ../../rnotes.rst:117
+#: ../../rnotes.rst:142
+#: ../../rnotes.rst:728
+#: ../../rnotes.rst:753
+#: ../../rnotes.rst:778
+#: ../../rnotes.rst:1273
+#: ../../rnotes.rst:1298
+#: ../../rnotes.rst:1323
+#: ../../rnotes.rst:1692
+#: ../../rnotes.rst:1718
+#: ../../rnotes.rst:1744
+#: ../../rnotes.rst:2516
+#: ../../rnotes.rst:2541
+#: ../../rnotes.rst:2566
+# 2389803696f546b487bef7ed63fe9cf1
+# 031bd5b6d8fd4537a63882344d81462d
+# dd86b4c235cb4eb08ab8931433e394b6
+# 26c77b27863a499385e36d338318feff
+# 045ba7ada091465782397d1524eee5e7
+# a0dc2127e843432b87c88f649301c454
+# ff5b8fd2272d4dd192d2bb6574a6d457
+# 79921a08ae2e43b59d6807a4af32cfff
+# 418158fbc34b40d9861b178b0a409a2f
+# a7777a2783f142a8842bf36186dbf842
+# 86936dadb1ea48259f5872e8cc7bb683
+# 0807bf02f2ff4b0d9922ff2c24f40154
+# bab7722e44e14d88b3e1ebe4a534bf42
+# 0c66fa015dbc42b5b24b9bb46c721441
+# 76c1d0c642a449cf8e8c3c0a62833df4
+msgid "Public: no"
+msgstr ""
+
+#: ../../rnotes.rst:94
+#: ../../rnotes.rst:119
+#: ../../rnotes.rst:144
+#: ../../rnotes.rst:730
+#: ../../rnotes.rst:755
+#: ../../rnotes.rst:780
+#: ../../rnotes.rst:1275
+#: ../../rnotes.rst:1300
+#: ../../rnotes.rst:1325
+#: ../../rnotes.rst:1694
+#: ../../rnotes.rst:1720
+#: ../../rnotes.rst:1746
+#: ../../rnotes.rst:2518
+#: ../../rnotes.rst:2543
+#: ../../rnotes.rst:2568
+# 4c17b6e131e142cfaa3d305806fd7523
+# dbdd68d63a144465981a1b5d53bf2598
+# a6053a4500e043a39a12d95a50afc4e1
+# 9bf7ce3a64cf4686b21fa34bd30f2bf7
+# d568aaf2c5ff400e8d47fb031ee99220
+# 20f48bc71cb547d89b7bb0fcae240414
+# 47850a9184a347e488fceb137b451c7d
+# 9932a3d73a08419d98e74cdb5091123a
+# 340e155b466a4f9abcadd9018298d165
+# 6f33f6462cc44834b05ae27a00c57970
+# a8ab610725ec45be8a19282146c5f392
+# cb798e1bb4e74be2902a55efaa50560f
+# cf257a5fe2a347a9ba4dfdef870079de
+# 8de20e3c772c4faeb7e9fb6f046277c6
+# db6be797a2414885abe44cd6bbb78e6a
+msgid "Featured: no"
+msgstr ""
+
+#: ../../rnotes.rst:96
+#: ../../rnotes.rst:732
+#: ../../rnotes.rst:1277
+#: ../../rnotes.rst:1696
+#: ../../rnotes.rst:2520
+# db00d07c960741289aee5f8142d2e368
+# f5748f546a024355a3f198d2f629b90d
+# 5b2c304631934350a0ea7f67fe4416a5
+# 92273fee3e894b5fbe410ad5a579b1c6
+# 74e6eb6c9150498988fbc79ee254c3f0
+msgid "KVM"
+msgstr ""
+
+#: ../../rnotes.rst:96
+#: ../../rnotes.rst:732
+#: ../../rnotes.rst:1277
+#: ../../rnotes.rst:1696
+#: ../../rnotes.rst:2520
+# c37736f0a31b446fbc7a6841614cf71c
+# 0f316cbb0b5f470eb6de77a262ac6753
+# cd161a821ed644ae8ee5784e026676de
+# ac775fa72e52423c8c5598eb94481650
+# 9bc64751dd5740a0a32fd3a5ddc6a333
+msgid "Name: systemvm-kvm-4.3"
+msgstr ""
+
+#: ../../rnotes.rst:98
+#: ../../rnotes.rst:734
+#: ../../rnotes.rst:1279
+#: ../../rnotes.rst:1698
+#: ../../rnotes.rst:2522
+# a656549bdd5247f9afc62d5fc8274746
+# 2f025a6a9fb1499d988c0ce4cad3269d
+# 0735ca296d0b405fbd2edb3fde6e4dd9
+# 7982d040783d48eeb0f082ec3a964eec
+# b676371c6d9048558d21532594e0b739
+msgid "Description: systemvm-kvm-4.3"
+msgstr ""
+
+#: ../../rnotes.rst:100
+#: ../../rnotes.rst:736
+#: ../../rnotes.rst:1281
+#: ../../rnotes.rst:1700
+#: ../../rnotes.rst:2524
+# e34e7276eb9b415ea037b17c9551cad6
+# 1109b770c4fa4291afc17e19e29b9707
+# b11d6d74b8e340d2af1246f535bed9e1
+# 9ded492ee518410f88bfa49eab1e31b8
+# 3fb14024946f4d70b472ccc0fa7b876a
+msgid "URL: http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-kvm.qcow2.bz2"
+msgstr ""
+
+#: ../../rnotes.rst:105
+#: ../../rnotes.rst:741
+#: ../../rnotes.rst:1286
+#: ../../rnotes.rst:1706
+#: ../../rnotes.rst:2529
+# 62e429365b8f4214a44101104a4e2559
+# c2e845dfc5c94eb18daa21878999de42
+# 4bfbb7a1589642c09758deb322b60cfd
+# b877f732e57e45d2ae9d2ea7df035d6f
+# c9eb933ce083414a9edd3435e48eba2b
+msgid "Hypervisor: KVM"
+msgstr ""
+
+#: ../../rnotes.rst:107
+#: ../../rnotes.rst:743
+#: ../../rnotes.rst:1288
+#: ../../rnotes.rst:1708
+#: ../../rnotes.rst:2531
+# 069d369782c24899a2e100b375f13280
+# 77946a1996684db89326b05e56f5fe99
+# 828baee68962477484111e334b362b88
+# 30f5abf4b9154e52b8c19bb6939b7a83
+# 5a1a142d0a5d4b5cbcb82d8807818791
+msgid "Format: QCOW2"
+msgstr ""
+
+#: ../../rnotes.rst:121
+#: ../../rnotes.rst:757
+#: ../../rnotes.rst:1302
+#: ../../rnotes.rst:1722
+#: ../../rnotes.rst:2545
+# c2993bf4a5114311bed8d66a9c476908
+# cff8a056b7134da0a3029ebe635b0be9
+# 75461d4a82934e86b29790b58fd37d0e
+# 407967fd891d4b618ee98fffd9e0d946
+# 6ddde7782a414cc69f3738e33d31b902
+msgid "VMware"
+msgstr ""
+
+#: ../../rnotes.rst:121
+#: ../../rnotes.rst:757
+#: ../../rnotes.rst:1302
+#: ../../rnotes.rst:1722
+#: ../../rnotes.rst:2545
+# 4bc55164d5d741c7b5be740b658e0787
+# e3ed715b7f1346e9b612535f6dfaf40b
+# 6c2c442ff345425c8869b1d9d5d3acc0
+# 69588a28ba4347fcb68c87c646fb60ee
+# f661a12fd1cc426182904a4bc75345c8
+msgid "Name: systemvm-vmware-4.3"
+msgstr ""
+
+#: ../../rnotes.rst:123
+#: ../../rnotes.rst:759
+#: ../../rnotes.rst:1304
+#: ../../rnotes.rst:1724
+#: ../../rnotes.rst:2547
+# 4c8ebe8a548a4f9b9ccd79045e484d1f
+# 5564146be1f44426bb7ff011cd79da6b
+# 2bcaf70553fe41b49bfd3d520eb87cf2
+# 69cfec227db440c78ffebe965f718f51
+# 737c7f2c4bc14508a4c7f6ada8848b86
+msgid "Description: systemvm-vmware-4.3"
+msgstr ""
+
+#: ../../rnotes.rst:125
+#: ../../rnotes.rst:761
+#: ../../rnotes.rst:1306
+#: ../../rnotes.rst:1726
+#: ../../rnotes.rst:2549
+# 929b6fcb9fa04616afcefbd762fd270b
+# 45594193b7824f4faf2b49ed811292e1
+# c5214485e9114e2eb71127c7d7de6965
+# 0c755ceff7c547348ff3a27a613ef83a
+# a56695f39bb84f899e7915122a3c430a
+msgid "URL: http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-vmware.ova"
+msgstr ""
+
+#: ../../rnotes.rst:130
+#: ../../rnotes.rst:766
+#: ../../rnotes.rst:1311
+#: ../../rnotes.rst:1732
+#: ../../rnotes.rst:2554
+# fdce1fd6cf214aa1a80d576a2896b896
+# 16b1ece80c5b47d087926ef28030fa24
+# bf8ca53871274fa692c6d6d79c44e724
+# 01a8c28c4a0d4be19d066f6b1ca9bfb4
+# cdb023985a824671b495895401467244
+msgid "Hypervisor: VMware"
+msgstr ""
+
+#: ../../rnotes.rst:132
+#: ../../rnotes.rst:768
+#: ../../rnotes.rst:1313
+#: ../../rnotes.rst:1734
+#: ../../rnotes.rst:2556
+# f5ab7fa232ba4adb9aff39fe88823e75
+# 68828f3174144a2ba64fc023ce8c45f6
+# 84231abe4e084779850b6e0fd3b05ed5
+# e045e6e4e8f5494b8df360e658fdd16e
+# f8413cb707bd478ab0917c42fe20305a
+msgid "Format: OVA"
+msgstr ""
+
+#: ../../rnotes.rst:149
+#: ../../rnotes.rst:671
+#: ../../rnotes.rst:1207
+# 3d8594f701ce4339a128d828a3d45262
+# 5573cc224cad4c6083abb76bb0562de4
+# 37d7d78c63444bd5aff131eb3e13263e
+msgid "Most users of CloudStack manage the installation and upgrades of CloudStack with one of Linux's predominant package systems, RPM or APT. This guide assumes you'll be using RPM and Yum (for Red Hat Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu)."
+msgstr ""
+
+#: ../../rnotes.rst:156
+# 88aa12a47aa945f39be9bca36470030a
+msgid "Create RPM or Debian packages (as appropriate) and a repository from the 4.3 source, or check the Apache CloudStack downloads page at `http://cloudstack.apache.org/downloads.html <http://cloudstack.apache.org/downloads.html>`__ for package repositories supplied by community members. You will need them for step `9 <#upgrade-deb-packages-4.3>`__ or step `12 <#upgrade-rpm-packages-4.3>`__."
+msgstr ""
+
+#: ../../rnotes.rst:163
+#: ../../rnotes.rst:793
+#: ../../rnotes.rst:1219
+# fe1460adc2c44e3d80206f28f58cb501
+# 6010af120d70477ca3ad2427739f816f
+# be1c3c65497244fdaec1d9ffd92245f2
+msgid "Instructions for creating packages from the CloudStack source are in the `Installation Guide <http://cloudstack.apache.org/docs/en-US/index.html>`__."
+msgstr ""
+
+#: ../../rnotes.rst:169
+#: ../../rnotes.rst:799
+#: ../../rnotes.rst:1331
+# 9fb806b610304e06a27290e8b4e45d46
+# a62f49eead134ffaa2c3867d0392d355
+# 76b2f9c139b746f387ab004817e72ade
+msgid "Stop your management server or servers. Run this on all management server hosts:"
+msgstr ""
+
+#: ../../rnotes.rst:178
+#: ../../rnotes.rst:808
+#: ../../rnotes.rst:1340
+# 61ec24c202454102af5231204abf54e8
+# d94754cfaa1845009234f1fd07ad1abe
+# 5fe3320b47d3420e8284aecdc344ae98
+msgid "If you are running a usage server or usage servers, stop those as well:"
+msgstr ""
+
+#: ../../rnotes.rst:187
+#: ../../rnotes.rst:817
+#: ../../rnotes.rst:1349
+# 3dae9ac1b9544013bab74070b4aba392
+# 35aaf48e64de4120920294e0e644043b
+# 41167be41fe5441b9a775b581b54a6ea
+msgid "Make a backup of your MySQL database. If you run into any issues or need to roll back the upgrade, this will assist in debugging or restoring your existing environment. You'll be prompted for your password."
+msgstr ""
+
+#: ../../rnotes.rst:198
+# a832f169886e4d90a4bcc7546e99fb92
+msgid "Perform the following to verify the artifacts:"
+msgstr ""
+
+#: ../../rnotes.rst:202
+# 8fc29aba93244f9c85d92598c8895eec
+msgid "(optional) Install GPG keys if needed:"
+msgstr ""
+
+#: ../../rnotes.rst:210
+# 9c5cb5834dda446888da19f515871371
+msgid "Import the GPG keys stored in the source distribution's KEYS file"
+msgstr ""
+
+#: ../../rnotes.rst:216
+# 5e1c33e0d9b840f7baf9a010ce8ac584
+msgid "Alternatively, download the signing keys, the IDs found in the KEYS file, individually by using a keyserver."
+msgstr ""
+
+#: ../../rnotes.rst:219
+# 4ca3f7ea5fcf43d5b1ff77d4d2ca7344
+msgid "For example:"
+msgstr ""
+
+#: ../../rnotes.rst:227
+# 0d8d050411314507a7666a445ac8ee8c
+msgid "Verify signatures and hash files:"
+msgstr ""
+
+#: ../../rnotes.rst:235
+# b7794f596fe7409f861b2e3ae506bf12
+msgid "Each of these commands should return no output. Any output from them implies that there is a difference between the hash you generated locally and the hash that has been pulled from the server."
+msgstr ""
+
+#: ../../rnotes.rst:242
+# b33428839e5047f587d2980dab1d0400
+msgid "Get the commit hash from the VOTE email."
+msgstr ""
+
+#: ../../rnotes.rst:244
+# 6ca9e5088bcd4ff5b75cafd02e137b5b
+msgid "For example: ``4cd60f3d1683a3445c3248f48ae064fb573db2a1``. The value changes between releases."
+msgstr ""
+
+#: ../../rnotes.rst:249
+# 590a8aafe28348c298754e9256f72562
+msgid "Create two new temporary directories:"
+msgstr ""
+
+#: ../../rnotes.rst:258
+# fca2c85f4dd146a19014af8fb2337d08
+msgid "Check out the 4.3 branch:"
+msgstr ""
+
+#: ../../rnotes.rst:268
+# 497f648b84504e92a92ea26c04fb938c
+msgid "Unpack the release artifact:"
+msgstr ""
+
+#: ../../rnotes.rst:277
+# cfb84a84e1d846868e5e793d17e63295
+msgid "Compare the contents of the release artifact with the contents pulled from the repo:"
+msgstr ""
+
+#: ../../rnotes.rst:284
+# b74361dc65ff43d09fcbccab8fd8f22f
+msgid "Ensure that content is the same."
+msgstr ""
+
+#: ../../rnotes.rst:288
+# de5a514cdf5e45ec9e0c83602693f1a9
+msgid "Verify the Code License Headers:"
+msgstr ""
+
+#: ../../rnotes.rst:295
+# a08623e0592740adbefb044fffe43b80
+msgid "The build fails if any non-compliant files are present that are not specifically excluded from the ASF license header requirement. You can optionally review the target/rat.txt file after the run completes. Passing the build implies that RAT certifies that the files are compliant and this test is passed."
+msgstr ""
+
+#: ../../rnotes.rst:303
+#: ../../rnotes.rst:828
+# c05c67cb91ff4c4fb0830a15517c28e6
+# f879c0c2a45a42dfb0cbae8b0c6c723c
+msgid "(KVM Only) If primary storage of type local storage is in use, the path for this storage needs to be verified to ensure it passes new validation. Check local storage by querying the cloud.storage\\_pool table:"
+msgstr ""
+
+#: ../../rnotes.rst:312
+#: ../../rnotes.rst:837
+# f5faf75092944799abb54b8ff3a93aac
+# 0abfe7d9828549a4874a4d76bd74099b
+msgid "If local storage paths are found to have a trailing forward slash, remove it:"
+msgstr ""
+
+#: ../../rnotes.rst:321
+# 6b58c38ec36b43359f8df7a4e28d0ba8
+msgid "If you are using Ubuntu, follow this procedure to upgrade your packages. If not, skip to step `12 <#upgrade-rpm-packages-4.3>`__."
+msgstr ""
+
+#: ../../rnotes.rst:324
+#: ../../rnotes.rst:851
+#: ../../rnotes.rst:1408
+#: ../../rnotes.rst:1850
+#: ../../rnotes.rst:2680
+# a6b983d16c564e14a40c2219f254d185
+# 8192ffa8b36d4fe39ccf4a48ff19b805
+# cd79a60a33fa4a5099611ad000aa40a8
+# 808e6e5841394a90b82e39738f25e8ea
+# 16a5425eb3264f878d16075d65a84e75
+msgid "**Community Packages:** This section assumes you're using the community supplied packages for CloudStack. If you've created your own packages and APT repository, substitute your own URL for the ones used in these examples."
+msgstr ""
+
+#: ../../rnotes.rst:328
+#: ../../rnotes.rst:855
+#: ../../rnotes.rst:1412
+#: ../../rnotes.rst:1854
+#: ../../rnotes.rst:2684
+# e5511d82d7dd4a2086af894d4f3a66e7
+# f071f4d226434279935f3b2d3bbf0b94
+# b1de12ae7c1d4bcbbfd6751e7905c3fc
+# 5abb5d0722c14a99a381043de09e787c
+# c13e0c45e1ac477f93c1e509f8b7a3ed
+msgid "The first order of business will be to change the sources list for each system with CloudStack packages. This means all management servers, and any hosts that have the KVM agent. (No changes should be necessary for hosts that are running VMware or Xen.)"
+msgstr ""
+
+#: ../../rnotes.rst:333
+#: ../../rnotes.rst:860
+#: ../../rnotes.rst:1417
+#: ../../rnotes.rst:1859
+#: ../../rnotes.rst:2689
+# a958c2917bbf4e76bef951b82eaa948d
+# c6a2774a444d4731920dea30f603dab4
+# 5ba4911d0da74773afb9c2eddc851cd7
+# e319c10bde3c4c3081b19a676e612403
+# 74bc1bcada174e589a3decdfa5139e8e
+msgid "Start by opening ``/etc/apt/sources.list.d/cloudstack.list`` on any systems that have CloudStack packages installed."
+msgstr ""
+
+#: ../../rnotes.rst:336
+#: ../../rnotes.rst:863
+#: ../../rnotes.rst:1420
+#: ../../rnotes.rst:1862
+#: ../../rnotes.rst:2692
+# 52594ffb3e3b49dd973c9b71d574ed06
+# 15c32c5835094010913b0a0640ee2d45
+# b9c9af9596fd4c2b9859e01f5b7d7cb4
+# 5f46c399178e4ac79d7bdee13c360ef0
+# 4e99197def0348688a462fd4f6e4360b
+msgid "This file should have one line, which contains:"
+msgstr ""
+
+#: ../../rnotes.rst:342
+#: ../../rnotes.rst:869
+#: ../../rnotes.rst:1426
+#: ../../rnotes.rst:1868
+#: ../../rnotes.rst:2698
+# 06e5ec0807804d29a708de00c61b5777
+# ba0fc909e0cc4f6da0d20c7bbcf4056a
+# 4e99f6d067da4893997e3948525b964d
+# e8a04410ba684e0885652b5f0d4cf114
+# a1830e7e3f1c4716a2ecebf346b0b746
+msgid "We'll change it to point to the new package repository:"
+msgstr ""
+
+#: ../../rnotes.rst:348
+#: ../../rnotes.rst:561
+#: ../../rnotes.rst:875
+#: ../../rnotes.rst:1093
+#: ../../rnotes.rst:1547
+#: ../../rnotes.rst:1874
+#: ../../rnotes.rst:2819
+# fe91d09f17b048528bb381f857027531
+# d6a1773e0b28473fb2e55fcea1768f9e
+# 0bc0c855315f41ed857d4e617cd628e1
+# 9e8f2d39ef1a4bc9aa61655baf391a87
+# be264602baaa42a29744eed1658e59b3
+# adb92ccbe36d49a1aacce6228a0d89f7
+# b7dccba865e34824851ab5b3c19b64fd
+msgid "If you're using your own package repository, change this line to read as appropriate for your 4.3 repository."
+msgstr ""
+
+#: ../../rnotes.rst:353
+#: ../../rnotes.rst:880
+#: ../../rnotes.rst:1437
+#: ../../rnotes.rst:1879
+#: ../../rnotes.rst:2709
+# af318502921348f6a28ee215a56caa91
+# e907284d5a7a4629980c3d2c27945fe4
+# 8658aafa6489403f9951530d92103573
+# bdada53d85954149ab6b22c802022d21
+# a9e8b1b691c044a78ccc5cc7d1aa88a8
+msgid "Now update your apt package list:"
+msgstr ""
+
+#: ../../rnotes.rst:361
+#: ../../rnotes.rst:888
+#: ../../rnotes.rst:1445
+#: ../../rnotes.rst:1887
+#: ../../rnotes.rst:2717
+# b3e9469c25964af1846bada191e04ec4
+# 3b6338f090944644a9bc88994718d676
+# 84c3a21811cb4055b3f6a878e5e32ba1
+# c4bc202140ed4c2294ba47ef898cc33d
+# bced4ccb43214bc9944417aa960ad820
+msgid "Now that you have the repository configured, it's time to install the ``cloudstack-management`` package. This will pull in any other dependencies you need."
+msgstr ""
+
+#: ../../rnotes.rst:371
+#: ../../rnotes.rst:898
+#: ../../rnotes.rst:1455
+#: ../../rnotes.rst:1897
+# de1a9ec4bd5045c79dbdfc029370bea8
+# e6282c1fac50417387b20ba58a7886d5
+# d71ec2e87e9b48a6bc842c92910f623c
+# 29ab25bcc03343cf8436a1f7d2de0dd1
+msgid "You will need to manually install the ``cloudstack-agent`` package:"
+msgstr ""
+
+#: ../../rnotes.rst:378
+#: ../../rnotes.rst:905
+#: ../../rnotes.rst:1462
+#: ../../rnotes.rst:1904
+#: ../../rnotes.rst:2734
+# 7720a75dd93347c2b3881f7e34fc9ab4
+# 909dfb569c204270b7a4f4a229249de2
+# ebed114157c0496b86ebb471bd0df7fd
+# 53463349bedd4f09bad1425cae191821
+# 10cb1cfc5923438286b42a21e6b707aa
+msgid "During the installation of ``cloudstack-agent``, APT will copy your ``agent.properties``, ``log4j-cloud.xml``, and ``environment.properties`` from ``/etc/cloud/agent`` to ``/etc/cloudstack/agent``."
+msgstr ""
+
+#: ../../rnotes.rst:381
+#: ../../rnotes.rst:910
+#: ../../rnotes.rst:1467
+#: ../../rnotes.rst:1909
+#: ../../rnotes.rst:2739
+# 31c195a6e6aa49b199138992bfdc5c4c
+# 294c1b73507d4a138d0cffa807bc6aa5
+# e15fb33c81924d908ba2e5287be51de6
+# 450c72d1f9394fa18db5038e8bbccfcb
+# 8c9593f4a88d4016880d243cc85121bb
+msgid "When prompted whether you wish to keep your configuration, say Yes."
+msgstr ""
+
+#: ../../rnotes.rst:386
+#: ../../rnotes.rst:586
+#: ../../rnotes.rst:915
+#: ../../rnotes.rst:1118
+#: ../../rnotes.rst:1472
+#: ../../rnotes.rst:1577
+#: ../../rnotes.rst:1914
+#: ../../rnotes.rst:2019
+#: ../../rnotes.rst:2744
+#: ../../rnotes.rst:2849
+# 013b94409f95418e8897098e07a8d8bf
+# c7368db7d4a04ff1bc743c2f6184e685
+# 6c1a1db1129440a093d08072e24a883a
+# edefd647ee6947bfa9544f7ef98c6635
+# e82fc4a9717d40c6aec52f82d1d48c76
+# f99deecf9e7540f385fb4dfe580aeaa4
+# 5c0aa24881e7433da978c0519e7c5c12
+# c30d30b25c2a4524ae83838dffe52c60
+# f78700edcf7242e7866cd95f7f5d5255
+# e21ee87582d24075bfa8c7a8798e2193
+msgid "Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a line that reads:"
+msgstr ""
+
+#: ../../rnotes.rst:394
+#: ../../rnotes.rst:594
+#: ../../rnotes.rst:923
+#: ../../rnotes.rst:1126
+#: ../../rnotes.rst:1480
+#: ../../rnotes.rst:1585
+#: ../../rnotes.rst:1922
+#: ../../rnotes.rst:2027
+#: ../../rnotes.rst:2752
+#: ../../rnotes.rst:2857
+# 700f1c7b1a1049b8806f24a991406dee
+# 31ddbf40c7364e6d8622368dfead1a6c
+# b1c49dadf53e44db985e7def1c40f6f3
+# fb5ed344bc15491d9afbe48f3c54ab11
+# bd8c2be8aba142e39d3f763290b746b2
+# 9be24a50e7014e7ba502e5143445a584
+# 3158944a76d0492795f68eeb63f917e2
+# 246b5d6355294df0a4fc27ebc6e9ba8d
+# 62e1898bf0c2477fa6db149294f84efe
+# e0882954603e4da58c47686f7edb5096
+msgid "If not, add the line."
+msgstr ""
+
+#: ../../rnotes.rst:398
+#: ../../rnotes.rst:598
+#: ../../rnotes.rst:927
+#: ../../rnotes.rst:1130
+#: ../../rnotes.rst:1484
+#: ../../rnotes.rst:1589
+#: ../../rnotes.rst:1926
+#: ../../rnotes.rst:2031
+#: ../../rnotes.rst:2756
+#: ../../rnotes.rst:2861
+# 519de95f4a6f4f4593be8696649527a1
+# 23f0e056534c4ed6a418e70b8c95f99c
+# de193ddaadfc4c8e9dce765f2b72b674
+# 53ed305891e244388ab9a01cd353db41
+# a52346ad05fb49558efcac30a6ef4bab
+# 098daad3fe4b4b8a9442aab380db3c0f
+# ab71fb2b93b14fdfa86405bce6f128d5
+# c4fd879586a54a70a06dc06345db0220
+# 296868aa390e48b9833c5a07ddb80d9f
+# 583276a529844a7f8932e434c87e9c5f
+msgid "Restart the agent:"
+msgstr ""
+
+#: ../../rnotes.rst:408
+#: ../../rnotes.rst:937
+# 328d335035544cd1b6d5c1e32ddd2cd8
+# 631312e403e7449bbfe0ff961a939d20
+msgid "(VMware only) Additional steps are required for each VMware cluster. These steps will not affect running guests in the cloud. These steps are required only for clouds using VMware clusters:"
+msgstr ""
+
+#: ../../rnotes.rst:414
+#: ../../rnotes.rst:943
+# 3fd9107b9e704f9aa78462e82c53f962
+# f7622a76f2344e98ac49eb7b609ad6ec
+msgid "Stop the Management Server:"
+msgstr ""
+
+#: ../../rnotes.rst:422
+#: ../../rnotes.rst:951
+# f8ea8b67844c4d0b9d8d68da74958172
+# 78afdf4037214084a10ece106b4c493c
+msgid "Generate the encrypted equivalent of your vCenter password:"
+msgstr ""
+
+#: ../../rnotes.rst:428
+#: ../../rnotes.rst:957
+# ca82244cd0144fdf8e467c7b20afecaa
+# e4d65748d3144b70af2b8af91965c2b6
+msgid "Store the output from this step, we need to add this in cluster\\_details table and vmware\\_data\\_center tables in place of the plain text password"
+msgstr ""
+
+#: ../../rnotes.rst:434
+#: ../../rnotes.rst:963
+# 52ac28e16f264f0a979beb36d04b6ea8
+# 76c0eac4b9264ae1b3a6c07e0dd3b7ed
+msgid "Find the ID of the row of cluster\\_details table that you have to update:"
+msgstr ""
+
+#: ../../rnotes.rst:447
+#: ../../rnotes.rst:976
+# ab863aa53ec843caab4beb5e2f9c23d7
+# 438c5f0d709a407796e492d3e6a40587
+msgid "Update the plain text password with the encrypted one"
+msgstr ""
+
+#: ../../rnotes.rst:455
+#: ../../rnotes.rst:480
+#: ../../rnotes.rst:984
+#: ../../rnotes.rst:1009
+# 00b91c75cfdb47f2bddb79ad7570dc7e
+# 052499a889174eab91eb38879532eb57
+# d8740e201c9740148a64849ac8cd1a77
+# fa98627cf81343728fc22b61fbb1e82f
+msgid "Confirm that the table is updated:"
+msgstr ""
+
+#: ../../rnotes.rst:463
+#: ../../rnotes.rst:992
+# a3edd50f595c40bd82f3e3ba0acf8b6b
+# 2ea24676dae145bcbb18392065c3ba1a
+msgid "Find the ID of the correct row of vmware\\_data\\_center that you want to update"
+msgstr ""
+
+#: ../../rnotes.rst:472
+#: ../../rnotes.rst:1001
+# 4798580a87cf4186b0d95247bd67707c
+# 300ad8d0623b469ab95ad20e7577a2a2
+msgid "update the plain text password with the encrypted one:"
+msgstr ""
+
+#: ../../rnotes.rst:488
+#: ../../rnotes.rst:1017
+# 74ed75c564e94d359e17dd134a934edf
+# 54cc6717a8d74582b9f2383dfffb8c0b
+msgid "Start the CloudStack Management server"
+msgstr ""
+
+#: ../../rnotes.rst:496
+#: ../../rnotes.rst:1025
+# e5763429fd714c748dc111bd9d7498a4
+# f42087fb226f4fd1912cfcebda96844e
+msgid "(KVM only) Additional steps are required for each KVM host. These steps will not affect running guests in the cloud. These steps are required only for clouds using KVM as hosts and only on the KVM hosts."
+msgstr ""
+
+#: ../../rnotes.rst:503
+#: ../../rnotes.rst:1032
+# a9b1166d4fdc4f7bbaee34ed69d84685
+# 26df2ece28b0403e83734879189c0a28
+msgid "Configure the CloudStack yum repository as detailed above."
+msgstr ""
+
+#: ../../rnotes.rst:507
+#: ../../rnotes.rst:1036
+#: ../../rnotes.rst:2138
+#: ../../rnotes.rst:3053
+# 91fcb4e5d87a4758bb495df7a566eef9
+# d3b457f5c84b4d7fa94e18a2f094eec3
+# 6f6fbd8df62a470daf0529b8cbf7c575
+# 298db92eabbf4892b82b467d5946f9dd
+msgid "Stop the running agent."
+msgstr ""
+
+#: ../../rnotes.rst:515
+#: ../../rnotes.rst:1044
+# 761fcbfc3fb344d680081c493d38f542
+# 530303b4348245678bd1be14a384140e
+msgid "Update the agent software."
+msgstr ""
+
+#: ../../rnotes.rst:523
+#: ../../rnotes.rst:1052
+#: ../../rnotes.rst:2189
+#: ../../rnotes.rst:3111
+# 51aaef13bf80479e95adac061e600381
+# be13ad0cba844fd691c8141e07838472
+# f81edce8c2794070919839b648553619
+# fc468199e0df4362841e9d745cd875e4
+msgid "Start the agent."
+msgstr ""
+
+#: ../../rnotes.rst:531
+# 54e588c53c4a4a55823879f37ea6b7e9
+msgid "If you are using CentOS or RHEL, follow this procedure to upgrade your packages. If not, skip to step `14 <#restart-system-vms-4.3>`__."
+msgstr ""
+
+#: ../../rnotes.rst:534
+#: ../../rnotes.rst:1066
+#: ../../rnotes.rst:1521
+#: ../../rnotes.rst:1963
+#: ../../rnotes.rst:2793
+# ac689aa24a284a2185768cd88ff9c873
+# 09301068b69c43e985ae0e3134e12b3e
+# 70fe9e2a05b5402e9a10a00a46e61cad
+# 20b091f734b74c1386d19886179685e7
+# 4b2d56d79c4d42528cbdf98f3c70bac3
+msgid "**Community Packages:** This section assumes you're using the community supplied packages for CloudStack. If you've created your own packages and yum repository, substitute your own URL for the ones used in these examples."
+msgstr ""
+
+#: ../../rnotes.rst:538
+#: ../../rnotes.rst:1070
+# 4e7a8145ac1949d7909e5ea4abdf5325
+# 3f3368fc99844d03b8ee9b83e6f595c7
+msgid "The first order of business will be to change the yum repository for each system with CloudStack packages. This means all management servers, and any hosts that have the KVM agent."
+msgstr ""
+
+#: ../../rnotes.rst:542
+#: ../../rnotes.rst:1074
+# 313646a070e746c19f661db22c3b0595
+# 27ee7f6888fc4cf290d970b4e226dff7
+msgid "(No changes should be necessary for hosts that are running VMware or Xen.)"
+msgstr ""
+
+#: ../../rnotes.rst:545
+#: ../../rnotes.rst:1077
+#: ../../rnotes.rst:1531
+#: ../../rnotes.rst:1973
+#: ../../rnotes.rst:2803
+# ea83c71a4ec44c0d855b5228e4ae375a
+# 513cb1b4523644ffb91d714743211614
+# 0d4a968ce5da475c9c3ec65194a77d45
+# 2c09bae6e7d8426a9cb7e8e1e027cb77
+# c519b2cfa95d4d19af2c939c49a891ca
+msgid "Start by opening ``/etc/yum.repos.d/cloudstack.repo`` on any systems that have CloudStack packages installed."
+msgstr ""
+
+#: ../../rnotes.rst:548
+#: ../../rnotes.rst:1080
+#: ../../rnotes.rst:1534
+#: ../../rnotes.rst:1976
+#: ../../rnotes.rst:2806
+# 2bfac7c63bc04900acf82a034c5947cb
+# 96d47cf378704b7aa603e9a54ac7cbd2
+# 70431912242f430eaf34fa8177791654
+# 548512344fb04bb9b25b12f48dfb0dc2
+# f88bab91a8b74ec8b864ffc5be1f574d
+msgid "This file should have content similar to the following:"
+msgstr ""
+
+#: ../../rnotes.rst:558
+# bb244ec41ca44d3c9fa015bd5cf87c71
+msgid "If you are using the community provided package repository, change the base url to http://cloudstack.apt-get.eu/rhel/4.3/"
+msgstr ""
+
+#: ../../rnotes.rst:566
+#: ../../rnotes.rst:1098
+# 5ec2b4f2ba7e406eaa7106ed76e5cc27
+# 836f4777f360464fb8c1651f14a4d182
+msgid "Now that you have the repository configured, it's time to install the ``cloudstack-management`` package by upgrading the older ``cloudstack-management`` package."
+msgstr ""
+
+#: ../../rnotes.rst:576
+#: ../../rnotes.rst:1108
+#: ../../rnotes.rst:1562
+#: ../../rnotes.rst:2004
+#: ../../rnotes.rst:2834
+# 60e7d2e7d8ff489784980e8e2123403f
+# 06d70371a9ea4fcf99318f48a2328ba7
+# f3cf77bb966d470fb3f4e8002f9f3285
+# c7a6700f971b43ddaa177f83a72e4c2c
+# 2e5faaf8a299443e8d5fd3898dfe873d
+msgid "For KVM hosts, you will need to upgrade the ``cloud-agent`` package, similarly installing the new version as ``cloudstack-agent``."
+msgstr ""
+
+#: ../../rnotes.rst:608
+#: ../../rnotes.rst:1140
+# 32e28ad2e92d41d0994468f556882e5c
+# 6d17ed0451cc4413a12e072380279737
+msgid "Now it's time to restart the management server"
+msgstr ""
+
+#: ../../rnotes.rst:616
+#: ../../rnotes.rst:1148
+# ae37a02856d74de5b7e9566104f0bbe7
+# 17651c70cd9c47e2a30cc8b2bdd1b243
+msgid "Once you've upgraded the packages on your management servers, you'll need to restart the system VMs. Ensure that the admin port is set to 8096 by using the \"integration.api.port\" global parameter. This port is used by the cloud-sysvmadm script at the end of the upgrade procedure. For information about how to set this parameter, see \"Setting Global Configuration Parameters\" in the Installation Guide. Changing this parameter will require management server restart. Also make sure port 8096 is open in your local host firewall to do this."
+msgstr ""
+
+#: ../../rnotes.rst:625
+#: ../../rnotes.rst:1157
+#: ../../rnotes.rst:1603
+# 5d2b5c4a4596478eabaf1f2d0adde94a
+# b7c4ad22a18a4be2906e119ae2214bfa
+# 4e468a10b85547dc86a9e9651ceddce9
+msgid "There is a script that will do this for you, all you need to do is run the script and supply the IP address for your MySQL instance and your MySQL credentials:"
+msgstr ""
+
+#: ../../rnotes.rst:633
+#: ../../rnotes.rst:1165
+#: ../../rnotes.rst:1611
+# 4c1c9abb463849148162a0efe944f2d1
+# 6f9068ec81f044d290d07272beb3d974
+# 793af338a6664b6ba129266632045bd4
+msgid "You can monitor the log for progress. The process of restarting the system VMs can take an hour or more."
+msgstr ""
+
+#: ../../rnotes.rst:640
+#: ../../rnotes.rst:1172
+#: ../../rnotes.rst:1618
+# 1e8ce2c7d6af4bbe932f49718456417b
+# 7211600043044817bb217c8d55db6337
+# a99ea4e3fcaa4334a470dc2ecac3b0ed
+msgid "The output to ``sysvm.log`` will look something like this:"
+msgstr ""
+
+#: ../../rnotes.rst:653
+#: ../../rnotes.rst:1187
+# f602f2b3f15447aba0f04fba9caec6fe
+# 52598e6b74c64e3ca72fed00f69355f5
+msgid "**For Xen Hosts: Copy vhd-utils:** This step is only for CloudStack installs that are using Xen hosts."
+msgstr ""
+
+#: ../../rnotes.rst:655
+#: ../../rnotes.rst:1189
+#: ../../rnotes.rst:1631
+# b38a22207b6143bf9def98306932020c
+# 2b4d5dfa48c140d0a0e5f74c0688136b
+# bc97f715272e48a5a112bc3c400044f4
+msgid "Copy the file ``vhd-utils`` to ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``."
+msgstr ""
+
+#: ../../rnotes.rst:659
+# 6bc2e068727042f1b0825066b191470b
+msgid "Upgrade from 4.1.x to 4.3"
+msgstr ""
+
+#: ../../rnotes.rst:661
+# cd05670352b2496695cee82731e1ffd2
+msgid "This section will guide you from CloudStack 4.1.x versions to CloudStack 4.3."
+msgstr ""
+
+#: ../../rnotes.rst:682
+# fced6cae9fe646eb918bda5491f6f75e
+msgid "While running the existing 4.1.x system, log in to the UI as root administrator."
+msgstr ""
+
+#: ../../rnotes.rst:786
+# 1d425573a29d4265a26faeb32cdbd6e7
+msgid "Create RPM or Debian packages (as appropriate) and a repository from the 4.2.1 source, or check the Apache CloudStack downloads page at `http://cloudstack.apache.org/downloads.html <http://cloudstack.apache.org/downloads.html>`__ for package repositories supplied by community members. You will need them for step `8 <#upgrade-deb-packages-41to42>`__ or step `11 <#upgrade-rpm-packages-41to42>`__."
+msgstr ""
+
+#: ../../rnotes.rst:846
+# f4c7884a790a478eb3d9776f3f20e60e
+msgid "If you are using Ubuntu, follow this procedure to upgrade your packages. If not, skip to step `11 <#upgrade-rpm-packages-41to42>`__."
+msgstr ""
+
+#: ../../rnotes.rst:1060
+# 4d83b8a9f5c141e99d1236bb9173d405
+msgid "If you are using CentOS or RHEL, follow this procedure to upgrade your packages. If not, skip to step `13 <#restart-system-vms-41to42>`__."
+msgstr ""
+
+#: ../../rnotes.rst:1090
+# 310caf1a8fe84f8aa11b00f4fc748fa3
+msgid "If you are using the community provided package repository, change the base url to http://cloudstack.apt-get.eu/rhel/4.2/"
+msgstr ""
+
+#: ../../rnotes.rst:1193
+# 87865b78f90840bf81c79ad5693e44f1
+msgid "Upgrade from 4.0.x to 4.3"
+msgstr ""
+
+#: ../../rnotes.rst:1195
+# dcc03feb1c6343a481529d8e99584e31
+msgid "This section will guide you from CloudStack 4.0.x versions to CloudStack 4.3."
+msgstr ""
+
+#: ../../rnotes.rst:1199
+# b937d64b11fa482a8ef65369068951d7
+msgid "**Package Structure Changes:** The package structure for CloudStack has changed significantly since the 4.0.x releases. If you've compiled your own packages, you'll notice that the package names and the number of packages has changed. This is *not* a bug. However, this *does* mean that the procedure is not as simple as an ``apt-get upgrade`` or ``yum update``, so please follow this section carefully."
+msgstr ""
+
+#: ../../rnotes.rst:1212
+# 82a38fa66d5f405fb43868a559fd3be7
+msgid "Create RPM or Debian packages (as appropriate) and a repository from the 4.1.0 source, or check the Apache CloudStack downloads page at `http://cloudstack.apache.org/downloads.html <http://cloudstack.apache.org/downloads.html>`__ for package repositories supplied by community members. You will need them for step `9 <#upgrade-deb-packages-40to41>`__ or step `10 <#upgrade-rpm-packages-40to41>`__."
+msgstr ""
+
+#: ../../rnotes.rst:1227
+# b69cf695d3a547d5ae0b4c58c7fb38b0
+msgid "While running the existing 4.0.0 system, log in to the UI as root administrator."
+msgstr ""
+
+#: ../../rnotes.rst:1360
+# decdfc8d25a44aec8b0d7248429e30ee
+msgid "Whether you're upgrading a Red Hat/CentOS based system or Ubuntu based system, you're going to need to stop the CloudStack management server before proceeding."
+msgstr ""
+
+#: ../../rnotes.rst:1370
+# f2c485a660324ae4b21cda5e01d76f60
+msgid "If you have made changes to ``/etc/cloud/management/components.xml``, you'll need to carry these over manually to the new file, ``/etc/cloudstack/management/componentContext.xml``. This is not done automatically. (If you're unsure, we recommend making a backup of the original ``components.xml`` to be on the safe side."
+msgstr ""
+
+#: ../../rnotes.rst:1378
+#: ../../rnotes.rst:2078
+# a2d67a43640845bb9f9b4944a7771ddf
+# 3f90e26e9881440ca7016620bfe8826a
+msgid "After upgrading to 4.3, API clients are expected to send plain text passwords for login and user creation, instead of MD5 hash. Incase, api client changes are not acceptable, following changes are to be made for backward compatibility:"
+msgstr ""
+
+#: ../../rnotes.rst:1383
+# cfa3495575d648dba32738e703dfcb9a
+msgid "Modify componentsContext.xml, and make PlainTextUserAuthenticator as the default authenticator (1st entry in the userAuthenticators adapter list is default)"
+msgstr ""
+
+#: ../../rnotes.rst:1400
+# c3bc0360bcc44217a96b9982cb901933
+msgid "PlainTextUserAuthenticator works the same way MD5UserAuthenticator worked prior to 4.3."
+msgstr ""
+
+#: ../../rnotes.rst:1405
+# d5f1eac6893c4ffc8ac4742182e5eb3c
+msgid "If you are using Ubuntu, follow this procedure to upgrade your packages. If not, skip to step `10 <#upgrade-rpm-packages-40to41>`__."
+msgstr ""
+
+#: ../../rnotes.rst:1432
+# 5f17c031f249452a860b528ea147b261
+msgid "If you're using your own package repository, change this line to read as appropriate for your 4.1.0 repository."
+msgstr ""
+
+#: ../../rnotes.rst:1494
+#: ../../rnotes.rst:1936
+#: ../../rnotes.rst:2766
+# df2e794712da48a3b74b1e8ab3132d7c
+# 3e6d6d7a7d674b0590ecd5840b8f1de4
+# b3d517b1d8cd4d2d912c2522b608b33d
+msgid "During the upgrade, ``log4j-cloud.xml`` was simply copied over, so the logs will continue to be added to ``/var/log/cloud/agent/agent.log``. There's nothing *wrong* with this, but if you prefer to be consistent, you can change this by copying over the sample configuration file:"
+msgstr ""
+
+#: ../../rnotes.rst:1508
+#: ../../rnotes.rst:1950
+#: ../../rnotes.rst:2780
+# 1aa1fe091d6b44b6a502e4fa15fa5844
+# 6ac1e77aad1a4198b0461498be05c91c
+# 149a0aac879c4ff8999e9bbfcc9ce20e
+msgid "Once the agent is running, you can uninstall the old cloud-\\* packages from your system:"
+msgstr ""
+
+#: ../../rnotes.rst:1517
+# 7a0c9bd9683444ac90d759ed23c5e473
+msgid "If you are using CentOS or RHEL, follow this procedure to upgrade your packages. If not, skip to step `11 <#restart-system-vms-40to41>`__."
+msgstr ""
+
+#: ../../rnotes.rst:1525
+#: ../../rnotes.rst:1967
+#: ../../rnotes.rst:2797
+# 8f6623ff2c0c4f5386f112569ec959c1
+# 07168fbf9db442d1b8711818e63325d8
+# 9d0279dcf38241d49908aa63cae11f2d
+msgid "The first order of business will be to change the yum repository for each system with CloudStack packages. This means all management servers, and any hosts that have the KVM agent. (No changes should be necessary for hosts that are running VMware or Xen.)"
+msgstr ""
+
+#: ../../rnotes.rst:1544
+# 515ed73456d24d2789fbccf5ec679d68
+msgid "If you are using the community provided package repository, change the baseurl to http://cloudstack.apt-get.eu/rhel/4.1/"
+msgstr ""
+
+#: ../../rnotes.rst:1552
+#: ../../rnotes.rst:1994
+#: ../../rnotes.rst:2824
+# 5bfa9979f3a241219f9294919127e4a7
+# 641797aa883846e78664b464498cf0d7
+# f72fc5000d104f4f9d49c6217613f418
+msgid "Now that you have the repository configured, it's time to install the ``cloudstack-management`` package by upgrading the older ``cloud-client`` package."
+msgstr ""
+
+#: ../../rnotes.rst:1570
+#: ../../rnotes.rst:2012
+#: ../../rnotes.rst:2842
+# fd5be6d36cc14d59b7702c0ea4c6d4cb
+# 29d70a286063432d888332981c528fc8
+# 876b961c8f9d414daa75266fa0eceeae
+msgid "During the installation of ``cloudstack-agent``, the RPM will copy your ``agent.properties``, ``log4j-cloud.xml``, and ``environment.properties`` from ``/etc/cloud/agent`` to ``/etc/cloudstack/agent``."
+msgstr ""
+
+#: ../../rnotes.rst:1599
+# 55b9c7a21be24615986ce044cf855196
+msgid "Once you've upgraded the packages on your management servers, you'll need to restart the system VMs. Make sure port 8096 is open in your local host firewall to do this."
+msgstr ""
+
+#: ../../rnotes.rst:1629
+# 41d50bc3ff714f16b97527c2044e9291
+msgid "*For Xen Hosts: Copy vhd-utils:** This step is only for CloudStack installs that are using Xen hosts."
+msgstr ""
+
+#: ../../rnotes.rst:1635
+# 19db5d49a0c541a19aaba789a6ac0bb4
+msgid "Upgrade from 3.0.x to 4.3"
+msgstr ""
+
+#: ../../rnotes.rst:1637
+# f1069c86fe0b488e8833596e29166bc2
+msgid "This section will guide you from Citrix CloudStack 3.0.x to Apache CloudStack 4.3. Sections that are hypervisor-specific will be called out with a note."
+msgstr ""
+
+#: ../../rnotes.rst:1645
+# 07fa0747696746e89054a00dfefc0ee8
+msgid "While running the existing 3.0.x system, log in to the UI as root administrator."
+msgstr ""
+
+#: ../../rnotes.rst:1677
+#: ../../rnotes.rst:1703
+#: ../../rnotes.rst:1729
+# b935ab26de7c48c8b31fe129107e4dc9
+# fb1f274e485146dcbb4711cdbf24e0af
+# 1202a4283afc4b568d2af0d3fa8759ef
+msgid "Zone: Choose the zone where this hypervisor is used used"
+msgstr ""
+
+#: ../../rnotes.rst:1751
+# 0c6257995da4416a8fb34f633e5623bb
+msgid "Watch the screen to be sure that the template downloads successfully and enters the READY state. Do not proceed until this is successful."
+msgstr ""
+
+#: ../../rnotes.rst:1757
+#: ../../rnotes.rst:2587
+# 9636c195c8884db58b8daeb21f226604
+# 0f30cf93febd40afb5045d7d1c1c0e71
+msgid "(KVM on RHEL 6.0/6.1 only) If your existing CloudStack deployment includes one or more clusters of KVM hosts running RHEL 6.0 or RHEL 6.1, perform the following:"
+msgstr ""
+
+#: ../../rnotes.rst:1763
+#: ../../rnotes.rst:2593
+# 9aea9022e50d4058b2daef62655b4cae
+# 5d5aceb1eb87437491f476aadb526a3f
+msgid "Ensure that you upgrade the operating system version on those hosts before upgrading CloudStack"
+msgstr ""
+
+#: ../../rnotes.rst:1766
+#: ../../rnotes.rst:2596
+# a1780e7a08bd417e9fc82f515181b464
+# 9115728a006e40acac5a3878feaaa87f
+msgid "To do that, change the yum repository for each system with CloudStack packages, that implies that all the Management Servers and any hosts that have the KVM agent."
+msgstr ""
+
+#: ../../rnotes.rst:1772
+#: ../../rnotes.rst:2602
+# 507ef992b28f4439b57a0d6cb5a362a6
+# 3fc9066c3e1c421dbc2d25b8115c558d
+msgid "Open ``/etc/yum.repos.d/cloudstack.repo`` on any systems that have CloudStack packages installed."
+msgstr ""
+
+#: ../../rnotes.rst:1777
+#: ../../rnotes.rst:2607
+# 195a497b8a0a4ed98e65b5ad132ea523
+# 735cce9dcf334ce7a4e084171554bb7e
+msgid "Edit as follows:"
+msgstr ""
+
+#: ../../rnotes.rst:1792
+#: ../../rnotes.rst:2622
+# 643ae9711e784a95b11fe23e8f3bab60
+# 78a133fee9ae49499025cae7d85b8e91
+msgid "If you are using the community provided package repository, change the baseurl to http:// cloudstack.apt-get.eu/rhel/4.2/"
+msgstr ""
+
+#: ../../rnotes.rst:1795
+#: ../../rnotes.rst:2625
+# daba49b2374c43029a8ebf5c33c1d11a
+# 97fbb9d0ad194f5487c0b3177535f2cc
+msgid "If you are using your own package repository, change this line to read as appropriate for your 4.2.0 repository."
+msgstr ""
+
+#: ../../rnotes.rst:1800
+#: ../../rnotes.rst:2630
+# 748793b598834ac184e4bcb1c768233b
+# cb06d38747e04dbaa8e6a83ba343d50e
+msgid "Now that you have the repository configured, upgrade the host operating system from RHEL 6.0 to 6.3:"
+msgstr ""
+
+#: ../../rnotes.rst:1809
+#: ../../rnotes.rst:2639
+# 29c161c76fed483c872a009d255ac138
+# ff6b709a9dd64c64873f8cd8ef7ab770
+msgid "Stop all Usage Servers if running. Run this on all Usage Server hosts."
+msgstr ""
+
+#: ../../rnotes.rst:1818
+#: ../../rnotes.rst:2648
+# 79db674b90bc41aead755812aa5039c0
+# db5339d420e24d98a980fd13f28d8406
+msgid "Stop the Management Servers. Run this on all Management Server hosts."
+msgstr ""
+
+#: ../../rnotes.rst:1826
+#: ../../rnotes.rst:2656
+# bda05cf21e784a1cbc68f3bbef5bcf32
+# d35c3cd591f547888c10e4a335ab6d70
+msgid "On the MySQL master, take a backup of the MySQL databases. We recommend performing this step even in test upgrades. If there is an issue, this will assist with debugging."
+msgstr ""
+
+#: ../../rnotes.rst:1830
+#: ../../rnotes.rst:2660
+# 8e66828458b3471cb74246724863bdf9
+# 58c3902fdb1d4fae99f90cc451ff89c3
+msgid "In the following commands, it is assumed that you have set the root password on the database, which is a CloudStack recommended best practice. Substitute your own MySQL root password."
+msgstr ""
+
+#: ../../rnotes.rst:1841
+#: ../../rnotes.rst:2671
+# d44cad1eb8984acb9208854228e2a846
+# 18fd82555bdc4e5788c7c0d0436a7c9a
+msgid "Either build RPM/DEB packages as detailed in the Installation Guide, or use one of the community provided yum/apt repositories to gain access to the CloudStack binaries."
+msgstr ""
+
+#: ../../rnotes.rst:1847
+# f921fbc7667149a5a087a95fa26e9c1a
+msgid "If you are using Ubuntu, follow this procedure to upgrade your packages. If not, skip to step `8 <#upgrade-rpm-packages-302>`__."
+msgstr ""
+
+#: ../../rnotes.rst:1959
+# 76b5ee76c1f942b79bc51a4c4e3f6a49
+msgid "If you are using CentOS or RHEL, follow this procedure to upgrade your packages. If not, skip to step `9 <#correct-components-xml-302>`__."
+msgstr ""
+
+#: ../../rnotes.rst:1986
+#: ../../rnotes.rst:2816
+# 38fba8ece8fd4ad584f423e11488adc8
+# 0f2c08e6b61a46978a84509dff72ba7e
+msgid "If you are using the community provided package repository, change the baseurl to http://cloudstack.apt-get.eu/rhel/4.2/"
+msgstr ""
+
+#: ../../rnotes.rst:1989
+#: ../../rnotes.rst:2704
+# 3f607a6dcca84c09ae958564227b8a8a
+# 4876bde4e7ae4591ae6196a3341a8e26
+msgid "If you're using your own package repository, change this line to read as appropriate for your 4.2.0 repository."
+msgstr ""
+
+#: ../../rnotes.rst:2041
+# 3a925891334944b098b5d9075953d97f
+msgid "If you have made changes to your copy of ``/etc/cloud/management/components.xml`` the changes will be preserved in the upgrade. However, you need to do the following steps to place these changes in a new version of the file which is compatible with version 4.2.0."
+msgstr ""
+
+#: ../../rnotes.rst:2049
+# e8cff9d1c7e9444f9d63bcc404493f10
+msgid "Make a backup copy of ``/etc/cloud/management/components.xml``. For example:"
+msgstr ""
+
+#: ../../rnotes.rst:2058
+#: ../../rnotes.rst:2895
+# 8dffce70c30e4aa1b6f60d0738b4fc47
+# 3ed3e63d34724c40862cf7a7dda28c08
+msgid "Copy ``/etc/cloud/management/components.xml.rpmnew`` to create a new ``/etc/cloud/management/components.xml``:"
+msgstr ""
+
+#: ../../rnotes.rst:2067
+# 818ffe1a86194b00a953a20a7660f1ee
+msgid "Merge your changes from the backup file into the new ``components.xml``."
+msgstr ""
+
+#: ../../rnotes.rst:2074
+# 5136061e008944349c17c0a4812f59e0
+msgid "If you have more than one management server node, repeat the upgrade steps on each node."
+msgstr ""
+
+#: ../../rnotes.rst:2083
+#: ../../rnotes.rst:2918
+# 62b7e9bfa03b4cdf8bf6f606369e16a4
+# 540f75422d9346028fb00d354ad199f8
+msgid "Modify componentContext.xml, and make PlainTextUserAuthenticator as the default authenticator (1st entry in the userAuthenticators adapter list is default)"
+msgstr ""
+
+#: ../../rnotes.rst:2100
+# 4f45fbfb75af42e78c4433516c861913
+msgid "PlainTextUserAuthenticator works the same way MD5UserAuthenticator worked prior to 4.3"
+msgstr ""
+
+#: ../../rnotes.rst:2105
+#: ../../rnotes.rst:3017
+# f14640101f524df8b61c04c5802a0f90
+# 5b07020940544308aca9e8ead134c5de
+msgid "Start the first Management Server. Do not start any other Management Server nodes yet."
+msgstr ""
+
+#: ../../rnotes.rst:2112
+# 3130f813f1794a6688ab5f84a05c2eae
+msgid "Wait until the databases are upgraded. Ensure that the database upgrade is complete. After confirmation, start the other Management Servers one at a time by running the same command on each node."
+msgstr ""
+
+#: ../../rnotes.rst:2116
+# e6be4a6abd82409daa72e51bd5505d3b
+msgid "Failing to restart the Management Server indicates a problem in the upgrade. Having the Management Server restarted without any issues indicates that the upgrade is successfully completed."
+msgstr ""
+
+#: ../../rnotes.rst:2120
+#: ../../rnotes.rst:3031
+# b700cadf10414664ad30403b1d734a27
+# 0d68ecc612954ca98e26cd764e2c338b
+msgid "Start all Usage Servers (if they were running on your previous version). Perform this on each Usage Server host."
+msgstr ""
+
+#: ../../rnotes.rst:2123
+# 962f098bf0944d4e9506d9f8da308f11
+msgid "``# service cloudstack-usage start``"
+msgstr ""
+
+#: ../../rnotes.rst:2127
+# eba4690f9619425baa4d7585ce906dbf
+msgid "Additional steps are required for each KVM host. These steps will not affect running guests in the cloud. These steps are required only for clouds using KVM as hosts and only on the KVM hosts."
+msgstr ""
+
+#: ../../rnotes.rst:2133
+# 88374faf9f7242f6800c1497e39974d3
+msgid "Configure a yum or apt repository containing the CloudStack packages as outlined in the Installation Guide."
+msgstr ""
+
+#: ../../rnotes.rst:2140
+# 95e544424f9c4f2e9c0fe114340d1aca
+msgid "``# service cloud-agent stop``"
+msgstr ""
+
+#: ../../rnotes.rst:2144
+# 1532763bd0b844ef99f8b0a414832b62
+msgid "Update the agent software with one of the following command sets as appropriate for your environment."
+msgstr ""
+
+#: ../../rnotes.rst:2147
+# ef4b3ed3bffa49e8b3239246f44a472f
+msgid "``# yum update cloud-*``"
+msgstr ""
+
+#: ../../rnotes.rst:2149
+# 8827d2ee4e4c4a5691a358bbe2d44487
+msgid "``# apt-get update``"
+msgstr ""
+
+#: ../../rnotes.rst:2151
+# 4b3a2d9d972c4a4fbf3e3ac52b909d96
+msgid "``# apt-get upgrade cloud-*``"
+msgstr ""
+
+#: ../../rnotes.rst:2155
+# 2fc0c723022d4ec18381a57e629decbe
+msgid "Edit ``/etc/cloudstack/agent/agent.properties`` to change the resource parameter from \"com.cloud.agent.resource.computing.LibvirtComputingResource\" to \"com.cloud.hypervisor.kvm.resource.LibvirtComputingResource\"."
+msgstr ""
+
+#: ../../rnotes.rst:2162
+#: ../../rnotes.rst:3084
+# ecc4df90301c40bdba7ec9c7489bbf45
+# 086e6aa91006413ab8d5a95e39199f4d
+msgid "Upgrade all the existing bridge names to new bridge names by running this script:"
+msgstr ""
+
+#: ../../rnotes.rst:2171
+#: ../../rnotes.rst:3093
+# e9e301e2d3dc463494b6b6bad654fc8d
+# cf012cbefe924ffaa2dcd6e80eebeba9
+msgid "Install a libvirt hook with the following commands:"
+msgstr ""
+
+#: ../../rnotes.rst:2181
+#: ../../rnotes.rst:3103
+# 782564b3f86d43e8990c24382940cddd
+# faeab88588a949ba948729ad64112abf
+msgid "Restart libvirtd."
+msgstr ""
+
+#: ../../rnotes.rst:2197
+#: ../../rnotes.rst:3119
+# 8b96e3f8824d453691b596afcf04c1f1
+# cd1171e11a1b4a8783ff18d68e9150b4
+msgid "When the Management Server is up and running, log in to the CloudStack UI and restart the virtual router for proper functioning of all the features."
+msgstr ""
+
+#: ../../rnotes.rst:2203
+# 98cb545fbff346118931eaaa14fd6a4d
+msgid "Log in to the CloudStack UI as administrator, and check the status of the hosts. All hosts should come to Up state (except those that you know to be offline). You may need to wait 20 or 30 minutes, depending on the number of hosts."
+msgstr ""
+
+#: ../../rnotes.rst:2208
+# ea845784382c45babdbe93fc92a064cb
+msgid "Troubleshooting: If login fails, clear your browser cache and reload the page."
+msgstr ""
+
+#: ../../rnotes.rst:2210
+# a64cb15160f849f9aa8b559ddf1bd7ef
+msgid "Do not proceed to the next step until the hosts show in Up state."
+msgstr ""
+
+#: ../../rnotes.rst:2214
+# adb1c4abcc30453ebcbbca49a1e1b66b
+msgid "If you are upgrading from 3.0.x, perform the following:"
+msgstr ""
+
+#: ../../rnotes.rst:2218
+# e7b0f35d0e1c451f830784f6ae6c0cc7
+msgid "Ensure that the admin port is set to 8096 by using the \"integration.api.port\" global parameter."
+msgstr ""
+
+#: ../../rnotes.rst:2221
+# 408081aa0c764b198f931f4854ab35c0
+msgid "This port is used by the cloud-sysvmadm script at the end of the upgrade procedure. For information about how to set this parameter, see \"Setting Global Configuration Parameters\" in the Installation Guide."
+msgstr ""
+
+#: ../../rnotes.rst:2228
+# 25c5ff1ef6b9441097aa6b059f802f87
+msgid "Restart the Management Server."
+msgstr ""
+
+#: ../../rnotes.rst:2230
+# 1835094467c94d71a7a9aa3ddbffb17c
+msgid "If you don't want the admin port to remain open, you can set it to null after the upgrade is done and restart the management server."
+msgstr ""
+
+#: ../../rnotes.rst:2234
+# 799314b8a15a41b589f078b7daf5dc8c
+msgid "Run the ``cloudstack-sysvmadm`` script to stop, then start, all Secondary Storage VMs, Console Proxy VMs, and virtual routers. Run the script once on each management server. Substitute your own IP address of the MySQL instance, the MySQL user to connect as, and the password to use for that user. In addition to those parameters, provide the ``-c`` and ``-r`` arguments. For example:"
+msgstr ""
+
+#: ../../rnotes.rst:2241
+# 7a3141a8401a42a4872b988c04647e50
+msgid "``# nohup cloudstack-sysvmadm -d 192.168.1.5 -u cloud -p password -c -r > sysvm.log 2>&1 &``"
+msgstr ""
+
+#: ../../rnotes.rst:2243
+# 9807ea9a9d344fa0b0f21a1fce18d952
+msgid "``# tail -f sysvm.log``"
+msgstr ""
+
+#: ../../rnotes.rst:2245
+#: ../../rnotes.rst:3150
+# 34044aff323d44e69fdd811e5a344cf8
+# 292a8d8e24e74cddb150524a71d44997
+msgid "This might take up to an hour or more to run, depending on the number of accounts in the system."
+msgstr ""
+
+#: ../../rnotes.rst:2250
+# 04316862c59449639b26eb55d2c6c2fc
+msgid "If needed, upgrade all Citrix XenServer hypervisor hosts in your cloud to a version supported by CloudStack 4.3. The supported versions are XenServer 5.6 SP2 and 6.0.2. Instructions for upgrade can be found in the CloudStack 4.3 Installation Guide under \"Upgrading XenServer Versions.\""
+msgstr ""
+
+#: ../../rnotes.rst:2258
+# 38e445189b2c4853996d4b3f592a9693
+msgid "Now apply the XenServer hotfix XS602E003 (and any other needed hotfixes) to XenServer v6.0.2 hypervisor hosts."
+msgstr ""
+
+#: ../../rnotes.rst:2263
+#: ../../rnotes.rst:3236
+# 69583363c53344c9a5b461c1077a571c
+# 097ee691746942e0800bfc1cb07a7983
+msgid "Disconnect the XenServer cluster from CloudStack."
+msgstr ""
+
+#: ../../rnotes.rst:2265
+#: ../../rnotes.rst:3238
+# 767c1a5a8d144ba09defeffef7faeda6
+# fc75a38ab89842c0b4ac387dd92520b6
+msgid "In the left navigation bar of the CloudStack UI, select Infrastructure. Under Clusters, click View All. Select the XenServer cluster and click Actions - Unmanage."
+msgstr ""
+
+#: ../../rnotes.rst:2269
+#: ../../rnotes.rst:3242
+# 06d83535407e41f3be6839d7649e8966
+# 678a50801a10408b98fe76ae32cf8b4b
+msgid "This may fail if there are hosts not in one of the states Up, Down, Disconnected, or Alert. You may need to fix that before unmanaging this cluster."
+msgstr ""
+
+#: ../../rnotes.rst:2273
+#: ../../rnotes.rst:3246
+# 64997a1d38bb46c58c5365e1309412e7
+# b0be1ec3117c4e04825eb6d77a336554
+msgid "Wait until the status of the cluster has reached Unmanaged. Use the CloudStack UI to check on the status. When the cluster is in the unmanaged state, there is no connection to the hosts in the cluster."
+msgstr ""
+
+#: ../../rnotes.rst:2280
+#: ../../rnotes.rst:3253
+# 4832dc8f53df42cbb8aadca835cf4b04
+# 3200e9a4df5a4b66a0cd9031c101286e
+msgid "To clean up the VLAN, log in to one XenServer host and run:"
+msgstr ""
+
+#: ../../rnotes.rst:2282
+# 76e8c2612409448592919b545f0f0309
+msgid "``/opt/xensource/bin/cloud-clean-vlan.sh``"
+msgstr ""
+
+#: ../../rnotes.rst:2286
+# d99a958c8c534070bd10c4efacf38fd9
+msgid "Now prepare the upgrade by running the following on one XenServer host:"
+msgstr ""
+
+#: ../../rnotes.rst:2289
+# d38d1cef21254e62849dffb3bfb47867
+msgid "``/opt/xensource/bin/cloud-prepare-upgrade.sh``"
+msgstr ""
+
+#: ../../rnotes.rst:2291
+# 517e10dd9f56496cae62e554097f8cb6
+msgid "If you see a message like \"can't eject CD\", log in to the VM and unmount the CD, then run this script again."
+msgstr ""
+
+#: ../../rnotes.rst:2296
+# 1dbd633d13a444ca8b8afb25a559294a
+msgid "Upload the hotfix to the XenServer hosts. Always start with the Xen pool master, then the slaves. Using your favorite file copy utility (e.g. WinSCP), copy the hotfixes to the host. Place them in a temporary folder such as /tmp."
+msgstr ""
+
+#: ../../rnotes.rst:2301
+#: ../../rnotes.rst:3278
+# f754e93a062b45bb9fb2cca2c83db68a
+# 6ca0af40b8ed47a6a54b3d5da7418472
+msgid "On the Xen pool master, upload the hotfix with this command:"
+msgstr ""
+
+#: ../../rnotes.rst:2303
+# e3db416d75c14207b9cabf916d47957d
+msgid "``xe patch-upload file-name=XS602E003.xsupdate``"
+msgstr ""
+
+#: ../../rnotes.rst:2305
+#: ../../rnotes.rst:3284
+# b63d979455244643bb200351d2243333
+# a7ddaa8b75f84373babe61c17194cc6f
+msgid "Make a note of the output from this command, which is a UUID for the hotfix file. You'll need it in another step later."
+msgstr ""
+
+#: ../../rnotes.rst:2308
+#: ../../rnotes.rst:3287
+# f5f4b3681fee4ce0a5989f592c27f321
+# 4c0b4359005b4939b87bdf98f56ddfaf
+msgid "(Optional) If you are applying other hotfixes as well, you can repeat the commands in this section with the appropriate hotfix number. For example, XS602E004.xsupdate."
+msgstr ""
+
+#: ../../rnotes.rst:2312
+#: ../../rnotes.rst:3291
+# b9ec3718777d426d9db60baf9343700f
+# ffc6b344024e46b5865e67a6281f6822
+msgid "Manually live migrate all VMs on this host to another host. First, get a list of the VMs on this host:"
+msgstr ""
+
+#: ../../rnotes.rst:2315
+# 331d0088f2dc4f3aabf28db1387b68b9
+msgid "``# xe vm-list``"
+msgstr ""
+
+#: ../../rnotes.rst:2317
+#: ../../rnotes.rst:3298
+# bbe943847b1347e58edf0eab4a1d9d79
+# 162db05d17d2431d8468e31154318a22
+msgid "Then use this command to migrate each VM. Replace the example host name and VM name with your own:"
+msgstr ""
+
+#: ../../rnotes.rst:2320
+# d261a0ceae664341b94f5a2be6b9a1a0
+msgid "``# xe vm-migrate live=true host=host-name`` vm=\\ *``VM-name``*"
+msgstr ""
+
+#: ../../rnotes.rst:2322
+#: ../../rnotes.rst:3305
+# 5fbea663a35a4ec28956f372a83490e0
+# e7f75116ea124d079497ff44c73d5328
+msgid "**Troubleshooting:** If you see a message like \"You attempted an operation on a VM which requires PV drivers to be installed but the drivers were not detected,\" run: ``/opt/xensource/bin/make_migratable.sh b6cf79c8-02ee-050b-922f-49583d9f1a14``."
+msgstr ""
+
+#: ../../rnotes.rst:2326
+#: ../../rnotes.rst:3309
+# 0cc26f65fa1c45bfa75fe01f25a366c4
+# 5154615b30294fe28801002bae9295dc
+msgid "Apply the hotfix. First, get the UUID of this host:"
+msgstr ""
+
+#: ../../rnotes.rst:2332
+#: ../../rnotes.rst:3313
+# ec6c8fc14acc44939ce7fb3602c28bfa
+# 4139ce0f7c2344f19a5ea41635ea5d93
+msgid "Then use the following command to apply the hotfix. Replace the example host UUID with the current host ID, and replace the hotfix UUID with the output from the patch-upload command you ran on this machine earlier. You can also get the hotfix UUID by running xe patch-list."
+msgstr ""
+
+#: ../../rnotes.rst:2344
+#: ../../rnotes.rst:3323
+# 3568f9bafc8d4d8ab736796446df9797
+# fc8405849a8842a596c978e732b51cd7
+msgid "Copy the following files from the CloudStack Management Server to the host."
+msgstr ""
+
+#: ../../rnotes.rst:2349
+#: ../../rnotes.rst:3327
+# 43ca4b954df446c3848428042f956e5f
+# f71543bdc41c4196ab1e6d54f072f671
+msgid "Copy from here..."
+msgstr ""
+
+#: ../../rnotes.rst:2349
+#: ../../rnotes.rst:3327
+# 033a8945e6a64e9f87e885bfd3425e08
+# 5ebbadd0ed1c49c3b330fbe518b381e4
+msgid "...to here"
+msgstr ""
+
+#: ../../rnotes.rst:2351
+# 7d904ffbc0d9419fb938d82ba8615913
+msgid "/usr/lib64/cloud/common /scripts/vm/hypervisor/ xenserver/xenserver60/N FSSR.py"
+msgstr ""
+
+#: ../../rnotes.rst:2351
+# 1fa8227e1e834e688c46517f5ed648f7
+msgid "/opt/xensource/sm/NFSSR.py"
+msgstr ""
+
+#: ../../rnotes.rst:2356
+# 8b00a47eb29f4658b97ce82f6ef6b42c
+msgid "/usr/lib64/cloud/common /scripts/vm/hypervisor/ xenserver/setupxenserve r.sh"
+msgstr ""
+
+#: ../../rnotes.rst:2356
+# a304f18ed3fb4841829ce7d70a770e63
+msgid "/opt/xensource/bin/setupxenserver.sh"
+msgstr ""
+
+#: ../../rnotes.rst:2361
+# 7e8fdbf45336439f930a3ac144ca6cc3
+msgid "/usr/lib64/cloud/common /scripts/vm/hypervisor/ xenserver/make\\_migrata ble.sh"
+msgstr ""
+
+#: ../../rnotes.rst:2361
+# 1860fb18826648f1bf66769b659e1fdc
+msgid "/opt/xensource/bin/make\\_migratable.sh"
+msgstr ""
+
+#: ../../rnotes.rst:2370
+#: ../../rnotes.rst:3347
+# a3173d96b6f54aefbdb48752db9828ae
+# 9f01e46081614585a340d3eaaa18daf6
+msgid "(Only for hotfixes XS602E005 and XS602E007) You need to apply a new Cloud Support Pack."
+msgstr ""
+
+#: ../../rnotes.rst:2375
+#: ../../rnotes.rst:3352
+# 7993d80e1552436eb3aae46eb696927e
+# 265e07a4a0ea4b1c8dc01f70233bd936
+msgid "Download the CSP software onto the XenServer host from one of the following links:"
+msgstr ""
+
+#: ../../rnotes.rst:2378
+#: ../../rnotes.rst:3355
+# 8bf41b466c9c4f57b54840fd3ae80e77
+# 17b702c3fc5e40608ce8c6ec4ac6f975
+msgid "For hotfix XS602E005: `http://coltrane.eng.hq.xensource.com/release/XenServer-6.x/XS-6.0.2/hotfixes/XS602E005/56710/xe-phase-2/xenserver-cloud-supp.tgz <http://coltrane.eng.hq.xensource.com/release/XenServer-6.x/XS-6.0.2/hotfixes/XS602E005/56710/xe-phase-2/xenserver-cloud-supp.tgz>`__"
+msgstr ""
+
+#: ../../rnotes.rst:2381
+#: ../../rnotes.rst:3358
+# 6055011a1e474ae5a461738f114fd422
+# 9411b91bb9e44792bf8bb84138bdd2a6
+msgid "For hotfix XS602E007: `http://coltrane.eng.hq.xensource.com/release/XenServer-6.x/XS-6.0.2/hotfixes/XS602E007/57824/xe-phase-2/xenserver-cloud-supp.tgz <http://coltrane.eng.hq.xensource.com/release/XenServer-6.x/XS-6.0.2/hotfixes/XS602E007/57824/xe-phase-2/xenserver-cloud-supp.tgz>`__"
+msgstr ""
+
+#: ../../rnotes.rst:2386
+#: ../../rnotes.rst:3363
+# 0fadc25cecb44b32ad197b10f2eca0d8
+# cf407c2830ac47f492d64717d3501356
+msgid "Extract the file:"
+msgstr ""
+
+#: ../../rnotes.rst:2394
+#: ../../rnotes.rst:3369
+# 58c54753c0214293a8661dda5b2f0cba
+# 959bb01c0f3545008d2d84e4aa00a854
+msgid "Run the following script:"
+msgstr ""
+
+#: ../../rnotes.rst:2402
+#: ../../rnotes.rst:3375
+# 38f4aeff350a4fb4bd8d37e140dc694c
+# 9ea6d227be6742468d0ab1a68cc3f00a
+msgid "If the XenServer host is part of a zone that uses basic networking, disable Open vSwitch (OVS):"
+msgstr ""
+
+#: ../../rnotes.rst:2411
+#: ../../rnotes.rst:3382
+# aa7bb4ea4d0941bc8140111dbb8af091
+# a6640f09a1894e6597632d1dce45fed6
+msgid "Reboot this XenServer host."
+msgstr ""
+
+#: ../../rnotes.rst:2415
+#: ../../rnotes.rst:2425
+#: ../../rnotes.rst:3386
+#: ../../rnotes.rst:3394
+# baa1e6147c854b659e178a302e991f3b
+# 7dcf051dfcf74e2d993f7e3995bc7bec
+# f64177cb003044a1bbbb2a319e2f8b84
+# 1bc5465fb7384879a27b3c605f34b2bf
+msgid "Run the following:"
+msgstr ""
+
+#: ../../rnotes.rst:2421
+#: ../../rnotes.rst:3390
+# d236387f6cae4016885806bbf7abdf02
+# 87036bcab733448f95f0ba794ce12506
+msgid "If the message \"mv: cannot stat \\`/etc/cron.daily/logrotate': No such file or directory\" appears, you can safely ignore it."
+msgstr ""
+
+#: ../../rnotes.rst:2433
+#: ../../rnotes.rst:3402
+# 897e2e4a95984933b9a64f63be27747d
+# 83c27089bfe946598169ee4c6e34c066
+msgid "On each slave host in the Xen pool, repeat these steps, starting from \"manually live migrate VMs.\""
+msgstr ""
+
+#: ../../rnotes.rst:2436
+# 2d1ff5d4bbd641a99083f6f5761692c3
+msgid "**Troubleshooting Tip:** If passwords which you know to be valid appear not to work after upgrade, or other UI issues are seen, try clearing your browser cache and reloading the UI page."
+msgstr ""
+
+#: ../../rnotes.rst:2439
+# 82790ea01a2e453292fd3c0f5b3aeb5a
+msgid "Upgrade from 2.2.14 to 4.3"
+msgstr ""
+
+#: ../../rnotes.rst:2443
+# 6728458389e8472db11d804a01fef76e
+msgid "Ensure that you query your IPaddress usage records and process them; for example, issue invoices for any usage that you have not yet billed users for."
+msgstr ""
+
+#: ../../rnotes.rst:2447
+# 50e27594ab444c7b9abf820d92391cc4
+msgid "Starting in 3.0.2, the usage record format for IP addresses is the same as the rest of the usage types. Instead of a single record with the assignment and release dates, separate records are generated per aggregation period with start and end dates. After upgrading to 4.3, any existing IP address usage records in the old format will no longer be available."
+msgstr ""
+
+#: ../../rnotes.rst:2456
+# 0f112aff5e3a40229d261d3025697c2a
+msgid "If you are using version 2.2.0 - 2.2.13, first upgrade to 2.2.14 by using the instructions in the `2.2.14 Release Notes <http://download.cloud.com/releases/2.2.0/CloudStack2.2.14ReleaseNotes.pdf>`__."
+msgstr ""
+
+#: ../../rnotes.rst:2460
+# 36b91bca26364212b55e0431b9ef3c50
+msgid "**KVM Hosts:** If KVM hypervisor is used in your cloud, be sure you completed the step to insert a valid username and password into the host\\_details table on each KVM node as described in the 2.2.14 Release Notes. This step is critical, as the database will be encrypted after the upgrade to 4.3."
+msgstr ""
+
+#: ../../rnotes.rst:2464
+# e632bad81d304b5db94858d58117436e
+msgid "While running the 2.2.14 system, log in to the UI as root administrator."
+msgstr ""
+
+#: ../../rnotes.rst:2469
+# cfa10b7552cc46f5b525a62659daf633
+msgid "Using the UI, add a new System VM template for each hypervisor type that is used in your cloud. In each zone, add a system VM template for each hypervisor used in that zone"
+msgstr ""
+
+#: ../../rnotes.rst:2489
+# 7953d86b0a724e9dbdae1b45e20ee5f0
+msgid "In the Register template dialog box, specify the following values depending on the hypervisor type (do not change these):"
+msgstr ""
+
+#: ../../rnotes.rst:2575
+# e73c6f280a964e9ab53e8222dd07d15c
+msgid "Watch the screen to be sure that the template downloads successfully and enters the READY state. Do not proceed until this is successful"
+msgstr ""
+
+#: ../../rnotes.rst:2580
+# 043250aad638485091b1ad7d4904d976
+msgid "**WARNING**: If you use more than one type of hypervisor in your cloud, be sure you have repeated these steps to download the system VM template for each hypervisor type. Otherwise, the upgrade will fail."
+msgstr ""
+
+#: ../../rnotes.rst:2677
+# 9372e38792a84c4d9bfb8155f65bcc6f
+msgid "If you are using Ubuntu, follow this procedure to upgrade your packages. If not, skip to step `13 <#upgrade-rpm-packages-22>`__."
+msgstr ""
+
+#: ../../rnotes.rst:2727
+# 7f39a2e90aef41da83b417f972663e92
+msgid "On KVM hosts, you will need to manually install the ``cloudstack-agent`` package:"
+msgstr ""
+
+#: ../../rnotes.rst:2789
+# 13cfb58fe8ee46bb80e2f551a1135ed8
+msgid "If you are using CentOS or RHEL, follow this procedure to upgrade your packages. If not, skip to step `14 <#correct-components-xml-22>`__."
+msgstr ""
+
+#: ../../rnotes.rst:2871
+# 0432fc0914754107ac9754d391f54297
+msgid "If you have made changes to your existing copy of the file components.xml in your previous-version CloudStack installation, the changes will be preserved in the upgrade. However, you need to do the following steps to place these changes in a new version of the file which is compatible with version 4.0.0-incubating."
+msgstr ""
+
+#: ../../rnotes.rst:2877
+# 7ba721c652e94aadb385c5898dc894ed
+msgid "How will you know whether you need to do this? If the upgrade output in the previous step included a message like the following, then some custom content was found in your old components.xml, and you need to merge the two files:"
+msgstr ""
+
+#: ../../rnotes.rst:2886
+# 71dc951ca5664bf087d4f9212bc11e16
+msgid "Make a backup copy of your ``/etc/cloud/management/components.xml`` file. For example:"
+msgstr ""
+
+#: ../../rnotes.rst:2904
+# 5201132a543646bf84dc219e48173483
+msgid "Merge your changes from the backup file into the new components.xml file."
+msgstr ""
+
+#: ../../rnotes.rst:2913
+# ad4f895c83a84caf9ab707f7338c373e
+msgid "After upgrading to 4.3, API clients are expected to send plain text passwords for login and user creation, instead of MD5 hash. If API client changes are not acceptable, following changes are to be made for backward compatibility:"
+msgstr ""
+
+#: ../../rnotes.rst:2936
+# 1b3777b6ac2f49f0ae518824ae49679f
+msgid "PlainTextUserAuthenticator works the same way MD5UserAuthenticator worked prior to 4.2."
+msgstr ""
+
+#: ../../rnotes.rst:2941
+# 4221f77c756443ce9ab754de8ec65d66
+msgid "If you have made changes to your existing copy of the ``/etc/cloud/management/db.properties`` file in your previous-version CloudStack installation, the changes will be preserved in the upgrade. However, you need to do the following steps to place these changes in a new version of the file which is compatible with this version."
+msgstr ""
+
+#: ../../rnotes.rst:2950
+# b3daf8da6b434814840365b1fa239b76
+msgid "Make a backup copy of your file ``/etc/cloud/management/db.properties``. For example:"
+msgstr ""
+
+#: ../../rnotes.rst:2959
+# 50f2571bc6ae44eb9fa538ab20f55834
+msgid "Copy ``/etc/cloud/management/db.properties.rpmnew`` to create a new ``/etc/cloud/management/db.properties``:"
+msgstr ""
+
+#: ../../rnotes.rst:2968
+# 82dac835ce744fa2843e8fd4f00d725f
+msgid "Merge your changes from the backup file into the new db.properties file."
+msgstr ""
+
+#: ../../rnotes.rst:2977
+# 823c919ee94a4ea995fb5b6acb1789e2
+msgid "On the management server node, run the following command. It is recommended that you use the command-line flags to provide your own encryption keys. See Password and Key Encryption in the Installation Guide."
+msgstr ""
+
+#: ../../rnotes.rst:2986
+# 3183fd7f9fc64c1da805d400cef1a448
+msgid "When used without arguments, as in the following example, the default encryption type and keys will be used:"
+msgstr ""
+
+#: ../../rnotes.rst:2991
+# db7fda651fdf4edbbb55d79666f5de0a
+msgid "(Optional) For encryption\\_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file."
+msgstr ""
+
+#: ../../rnotes.rst:2997
+# 1686fdd4b329427998f940269214b95e
+msgid "(Optional) For management\\_server\\_key, substitute the default key that is used to encrypt confidential parameters in the properties file. Default: password. It is highly recommended that you replace this with a more secure value"
+msgstr ""
+
+#: ../../rnotes.rst:3004
+# 53b58c1927814bafa5a8d851cf83f127
+msgid "(Optional) For database\\_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value."
+msgstr ""
+
+#: ../../rnotes.rst:3011
+# 62edafd0b35a480382433052c36a483a
+msgid "Repeat steps 10 - 14 on every management server node. If you provided your own encryption key in step 14, use the same key on all other management servers."
+msgstr ""
+
+#: ../../rnotes.rst:3024
+# ceadabc924b2492b89494d0e3665c19b
+msgid "Wait until the databases are upgraded. Ensure that the database upgrade is complete. You should see a message like \"Complete! Done.\" After confirmation, start the other Management Servers one at a time by running the same command on each node."
+msgstr ""
+
+#: ../../rnotes.rst:3040
+# 45eba2e4a54f4843b0e27e9c42f1dbf2
+msgid "(KVM only) Perform the following additional steps on each KVM host."
+msgstr ""
+
+#: ../../rnotes.rst:3042
+# dac62cccc4d74aa489a543c5660e35c9
+msgid "These steps will not affect running guests in the cloud. These steps are required only for clouds using KVM as hosts and only on the KVM hosts."
+msgstr ""
+
+#: ../../rnotes.rst:3048
+# c435bb7040ed46ed92c3d29c2fefc4ae
+msgid "Configure your CloudStack package repositories as outlined in the Installation Guide"
+msgstr ""
+
+#: ../../rnotes.rst:3061
+# b107265977d2498f8ef4131c0c86a1ed
+msgid "Update the agent software with one of the following command sets as appropriate."
+msgstr ""
+
+#: ../../rnotes.rst:3075
+# ae15ee20e0da4240a42ecb0ad283ba86
+msgid "Copy the contents of the ``agent.properties`` file to the new ``agent.properties`` file by using the following command"
+msgstr ""
+
+#: ../../rnotes.rst:3125
+# 8bb30e012222481888026129c2f7e555
+msgid "Log in to the CloudStack UI as admin, and check the status of the hosts. All hosts should come to Up state (except those that you know to be offline). You may need to wait 20 or 30 minutes, depending on the number of hosts."
+msgstr ""
+
+#: ../../rnotes.rst:3130
+# 9ee45f8da2654c7f88973bb87d6bb717
+msgid "Do not proceed to the next step until the hosts show in the Up state. If the hosts do not come to the Up state, contact support."
+msgstr ""
+
+#: ../../rnotes.rst:3135
+# fa850967858f47febfc91997ac25f725
+msgid "Run the following script to stop, then start, all Secondary Storage VMs, Console Proxy VMs, and virtual routers."
+msgstr ""
+
+#: ../../rnotes.rst:3140
+# 15eef6c66bb94d56b1109582896c36ec
+msgid "Run the command once on one management server. Substitute your own IP address of the MySQL instance, the MySQL user to connect as, and the password to use for that user. In addition to those parameters, provide the \"-c\" and \"-r\" arguments. For example:"
+msgstr ""
+
+#: ../../rnotes.rst:3155
+# d1283b650aa04aceac0fb1cc712af280
+msgid "After the script terminates, check the log to verify correct execution:"
+msgstr ""
+
+#: ../../rnotes.rst:3162
+# 9590559e0ef845399718b5b37e87d91a
+msgid "The content should be like the following:"
+msgstr ""
+
+#: ../../rnotes.rst:3175
+# 2ec40ea9c93549bb843191d9b8b2fce9
+msgid "If you would like additional confirmation that the new system VM templates were correctly applied when these system VMs were rebooted, SSH into the System VM and check the version."
+msgstr ""
+
+#: ../../rnotes.rst:3179
+# fd02ccf0a24145788a58ba23ef308968
+msgid "Use one of the following techniques, depending on the hypervisor."
+msgstr ""
+
+#: ../../rnotes.rst:3181
+# 2df764619b4b495981cb99842ea38f1a
+msgid "**XenServer or KVM:**"
+msgstr ""
+
+#: ../../rnotes.rst:3183
+# 68efcc3b46484b4b808e5a39b49d73a1
+msgid "SSH in by using the link local IP address of the system VM. For example, in the command below, substitute your own path to the private key used to log in to the system VM and your own link local IP."
+msgstr ""
+
+#: ../../rnotes.rst:3188
+# fd4b333286e5478d97c06160278544ca
+msgid "Run the following commands on the XenServer or KVM host on which the system VM is present:"
+msgstr ""
+
+#: ../../rnotes.rst:3196
+#: ../../rnotes.rst:3215
+# d020aa4087674068b0b854c5f95de59a
+# 9d87110c8bca44f28b610e5dd11c2b31
+msgid "The output should be like the following:"
+msgstr ""
+
+#: ../../rnotes.rst:3202
+# 253faad325424be09decb709919d5f28
+msgid "**ESXi:**"
+msgstr ""
+
+#: ../../rnotes.rst:3204
+# 7f9fa5dd30cb405bbb4e900045e4e9c4
+msgid "SSH in using the private IP address of the system VM. For example, in the command below, substitute your own path to the private key used to log in to the system VM and your own private IP."
+msgstr ""
+
+#: ../../rnotes.rst:3208
+# f71cc5b4b18f4b888cf90797987621fd
+msgid "Run the following commands on the Management Server:"
+msgstr ""
+
+#: ../../rnotes.rst:3223
+# 05d0ba7090a3476ca03dba20a21ba759
+msgid "If needed, upgrade all Citrix XenServer hypervisor hosts in your cloud to a version supported by CloudStack 4.0.0-incubating. The supported versions are XenServer 5.6 SP2 and 6.0.2. Instructions for upgrade can be found in the CloudStack 4.0.0-incubating Installation Guide."
+msgstr ""
+
+#: ../../rnotes.rst:3231
+# f40400badcaf4fcf9390c849d29a7800
+msgid "Apply the XenServer hotfix XS602E003 (and any other needed hotfixes) to XenServer v6.0.2 hypervisor hosts."
+msgstr ""
+
+#: ../../rnotes.rst:3261
+# 36cbfcfda1a2480e948ce702f432449e
+msgid "Prepare the upgrade by running the following on one XenServer host:"
+msgstr ""
+
+#: ../../rnotes.rst:3268
+# 3fd5250f54864755a9d4fb5274f1b731
+msgid "If you see a message like \"can't eject CD\", log in to the VM and umount the CD, then run this script again."
+msgstr ""
+
+#: ../../rnotes.rst:3273
+# d39f60ad6d3b479ca5f80e075fcb7336
+msgid "Upload the hotfix to the XenServer hosts. Always start with the Xen pool master, then the slaves. Using your favorite file copy utility (e.g. WinSCP), copy the hotfixes to the host. Place them in a temporary folder such as /root or /tmp."
+msgstr ""
+
+#: ../../rnotes.rst:3311
+# 2ea6ac411b414c97a5d700d01a73c88f
+msgid "``# xe host-list``"
+msgstr ""
+
+#: ../../rnotes.rst:3319
+# 8dd945f518ec4ae49e9d99c221aa8800
+msgid "``xe patch-apply host-uuid=host-uuid`` uuid=\\ *``hotfix-uuid``*"
+msgstr ""
+
+#: ../../rnotes.rst:3329
+# 774cb9a979354f4eb768e85ed3b33252
+msgid "``/usr/share/cloudstack -common/scripts/vm/hype rvisor/xenserver/xenser ver60/NFSSR.py``"
+msgstr ""
+
+#: ../../rnotes.rst:3329
+# eab01b95f0be46da97675955e962ee01
+msgid "``/opt/xensource/sm/NFSSR.py``"
+msgstr ""
+
+#: ../../rnotes.rst:3334
+# 9e059b42b8344fcfb27f1ba2f9d5e069
+msgid "``/usr/share/cloudstack -common/scripts/vm/hype rvisor/xenserver/setupx enserver.sh``"
+msgstr ""
+
+#: ../../rnotes.rst:3334
+#: ../../rnotes.rst:3388
+# 6a8dcdfe83e649fb80bcb75c4cdca85f
+# 1368764a6dec4fb49e23adb8fbda6b0d
+msgid "``/opt/xensource/bin/setupxenserver.sh``"
+msgstr ""
+
+#: ../../rnotes.rst:3339
+# 736582523a6b4710a62c8f0a03053ac6
+msgid "``/usr/lib64/cloudstack -common/scripts/vm/hype rvisor/xenserver/make_m igratable.sh``"
+msgstr ""
+
+#: ../../rnotes.rst:3339
+# c04d43d5d16d44c0a133aa8ebae5891f
+msgid "``/opt/xensource/bin/make_migratable.sh``"
+msgstr ""
+
+#: ../../rnotes.rst:3365
+# c25347962eed49c6a57d0832a0e9aec1
+msgid "``# tar xf xenserver-cloud-supp.tgz``"
+msgstr ""
+
+#: ../../rnotes.rst:3371
+# c5ac8fb53ab04e90957992eb9c5be8ac
+msgid "``# xe-install-supplemental-pack xenserver-cloud-supp.iso``"
+msgstr ""
+
+#: ../../rnotes.rst:3378
+# 2a0c09f664a44e9f866660c47094ab1a
+msgid "``# xe-switch-network-backend bridge``"
+msgstr ""
+
diff --git a/source/upgrading/index.rst b/source/upgrading/index.rst
new file mode 100644
index 0000000..041f3b8
--- /dev/null
+++ b/source/upgrading/index.rst
@@ -0,0 +1,54 @@
+.. 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 Release Notes documentation master file, created by
+ sphinx-quickstart on Fri Feb 7 16:00:59 2014.
+ You can adapt this file completely to your liking, but it should at least
+ contain the root `toctree` directive.
+
+|menu_acs_logo|
+
+
+Upgrading CloudStack
+====================
+
+
+This document contains the instructions for upgrading CloudStack from prior releases, to the current
+release. Please read through all sections carefully before starting.
+
+.. note::
+ For information on the API changes and issues fixed in this release, please see the Release Notes section of the documentation
+
+
+Contents:
+
+.. toctree::
+ :maxdepth: 1
+
+ upgrade/upgrade-4.11
+ upgrade/upgrade-4.10
+ upgrade/upgrade-4.9
+ upgrade/upgrade-4.8
+ upgrade/upgrade-4.7
+ upgrade/upgrade-4.6
+ upgrade/upgrade-4.5
+ upgrade/upgrade-4.4
+ upgrade/upgrade-4.3
+.. upgrade/upgrade-4.2
+.. upgrade/upgrade-4.1
+.. upgrade/upgrade-4.0
+.. upgrade/upgrade-3.0.x
+.. upgrade/upgrade-2.2.14
+ upgrade/valid_source
diff --git a/source/upgrading/locale/ja/LC_MESSAGES/about.mo b/source/upgrading/locale/ja/LC_MESSAGES/about.mo
new file mode 100644
index 0000000..ad03993
--- /dev/null
+++ b/source/upgrading/locale/ja/LC_MESSAGES/about.mo
Binary files differ
diff --git a/source/upgrading/locale/ja/LC_MESSAGES/about.po b/source/upgrading/locale/ja/LC_MESSAGES/about.po
new file mode 100644
index 0000000..c9c8b14
--- /dev/null
+++ b/source/upgrading/locale/ja/LC_MESSAGES/about.po
@@ -0,0 +1,5927 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-05 14:09+0100\n"
+"PO-Revision-Date: 2014-03-31 15:24+0000\n"
+"Last-Translator: sebgoa <runseb@gmail.com>\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/apache-cloudstack-release-notes-rtd/language/ja/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# b576289212e54cb78ed684eec3888a03
+#: ../../source/about.rst:17
+msgid "About this new Release"
+msgstr ""
+
+# 041aef7b56634ca9a8a96f43278fd527
+#: ../../source/about.rst:20
+msgid "What's New in 4.3"
+msgstr ""
+
+# 5322a08e2b494ae5a2c82cedea3b0aa0
+#: ../../source/about.rst:22
+msgid "CloudStack 4.3 includes the following new features."
+msgstr ""
+
+# 0876950b77c54beb85b983fba4496c00
+#: ../../source/about.rst:25
+msgid "Optional 64-Bit System VM Template Support"
+msgstr ""
+
+# 8a2fed0a4b384e9796539817da67c958
+#: ../../source/about.rst:27
+msgid ""
+"CloudStack now provides 64-bit templates for System VMs. With this support, "
+"you will be able to upgrade virtual routers in a zone. The following "
+"parameters have been introduced for the same purpose:"
+msgstr ""
+
+# 0e4e9594c53b4bea9dd780826bd0dc71
+#: ../../source/about.rst:33
+msgid "XenServer: *``router.template.xen``*"
+msgstr ""
+
+# c0af61a617114caaacf0279264dd5d06
+#: ../../source/about.rst:37
+msgid "KVM: *``router.template.kvm``*"
+msgstr ""
+
+# aecc6c0e4a1b49168f343801d8dca3bc
+#: ../../source/about.rst:41
+msgid "VMware:"
+msgstr ""
+
+# d789a68734994ebc8f66901df1928395
+#: ../../source/about.rst:45
+msgid "Hyper-V:"
+msgstr ""
+
+# 804fdc472af9432c944dee3247993077
+#: ../../source/about.rst:48
+msgid "Hyper-V Support"
+msgstr ""
+
+# f6a1d0157418482682ff112c79fcdbfe
+#: ../../source/about.rst:50
+msgid ""
+"CloudStack 4.3 Beta rolls out support for Hyper-V hosts. For Hyper-V, "
+"CloudStack supports SMB-based storage. If you want to run guest VMs on "
+"Hyper-V hosts, install CloudStack Agents on each Hyper-V hosts. Before you "
+"use Hyper-V, review the following list of supported and non-supported "
+"features. For detailed instruction, see Hyper-V Quick Start Guide. You can "
+"also see the chapter Installing Hyper-V for CloudStack in the CloudStack 4.3"
+" Beta Installation Guide."
+msgstr ""
+
+# ae6a53cb206b40709b96496ce5339299
+# c925adb80f424f86b1b6959684d54557
+#: ../../source/about.rst:59 ../../source/about.rst:464
+msgid "Supported Functionalities"
+msgstr ""
+
+# 990d715fb8674f01bbcaebb0115054c4
+#: ../../source/about.rst:63
+msgid "VM Compute"
+msgstr ""
+
+# 2a0b668f5247485089f03b43af2181c3
+#: ../../source/about.rst:67
+msgid "All the VM operations, except VM Snapshots"
+msgstr ""
+
+# 3719b2fe0b304f4ba6d0b415d18e6bb0
+#: ../../source/about.rst:71
+msgid "Live Migration"
+msgstr ""
+
+# 99f7bd2be18c45b4855770b451d9e050
+#: ../../source/about.rst:75
+msgid "Service Offerings (Scale up on stopped VMs)"
+msgstr ""
+
+# 8f66257200c9407dbd52fe9d68335066
+#: ../../source/about.rst:79
+msgid "Console access"
+msgstr ""
+
+# 9d4bf9710ada4aac82890f17f7f298c0
+#: ../../source/about.rst:83
+msgid "SSH key and reseting SSH key"
+msgstr ""
+
+# d3345ccf5ce14feaa4522ee03767a823
+#: ../../source/about.rst:87
+msgid "Upload and download templates, volumes, and ISO"
+msgstr ""
+
+# e21aa429f0494d6a9e9f53ef6490a793
+#: ../../source/about.rst:91
+msgid "Create VMs from template and ISO"
+msgstr ""
+
+# b2ead7a50034443da581e170c420f9ee
+#: ../../source/about.rst:95
+msgid "Create template from volume"
+msgstr ""
+
+# d3c4bc7304be4bceb9fcc8e936802d14
+#: ../../source/about.rst:99
+msgid "Attach and detach VMs from ISO and password-enabled template"
+msgstr ""
+
+# 22d0290679bf4859bd4ba5a60a76be0a
+#: ../../source/about.rst:103
+msgid "Copy template across zone"
+msgstr ""
+
+# 12fce5e639a646158f1dc86dfa7e398b
+#: ../../source/about.rst:107
+msgid "Storage"
+msgstr "ストレージ"
+
+# 6998aae328cd44ec81dea862ddbc8b88
+#: ../../source/about.rst:111
+msgid "Primary Storage (SMB and Local)"
+msgstr ""
+
+# 253bb3aed0054525a1e099b0f8848ec5
+#: ../../source/about.rst:115
+msgid "Root and data volumes on Local and SMB"
+msgstr ""
+
+# 1ea502369b144d039b4cee2719180070
+#: ../../source/about.rst:119
+msgid "Add, delete, attach, detach volumes (one or more volumes per VM)"
+msgstr ""
+
+# e63f3da3d4d74e868da51084b5898669
+#: ../../source/about.rst:123
+msgid "Single and multiple secondary storage (SMB)"
+msgstr ""
+
+# b026291779464da3801d90e1ddde3180
+#: ../../source/about.rst:127
+msgid "Network"
+msgstr "ネットワーク"
+
+# 23e7c8c98c714ed9b36b1d580e4fd189
+#: ../../source/about.rst:131
+msgid "VLANs (Isolated and Shared)"
+msgstr ""
+
+# db1efe7f26f84702beb0ebf9818ef009
+#: ../../source/about.rst:135
+msgid ""
+"All VR services: DNS, DHCP, SourceNAT, LB, PF, Firewall, StaticNAT, "
+"Userdata, and VPN"
+msgstr ""
+
+# c2bec305654e46c4962358cbdcabe7ee
+#: ../../source/about.rst:140
+msgid ""
+"External device support for both Isolated and Shared networks: Netscaler, "
+"SRX, F5"
+msgstr ""
+
+# 5bc7bcbbd7c94278a9c2c37e621693c1
+#: ../../source/about.rst:145
+msgid "Multiple physical networks"
+msgstr ""
+
+# 1c66959656f743a9a898e8f91dd1e092
+#: ../../source/about.rst:149
+msgid "Dedicated IP range, Public VLANs (to account)"
+msgstr ""
+
+# e5de14ce5630418eba740fa64ca72222
+#: ../../source/about.rst:153
+msgid "Network Offering upgrades and updates"
+msgstr ""
+
+# fdedc1322fe04400a7a95f10bcb99360
+#: ../../source/about.rst:157
+msgid "L4-L7 services in Shared network"
+msgstr ""
+
+# 5317a9412d78466497242974410d41ac
+#: ../../source/about.rst:161
+msgid "Multiple IP ranges and portable IPs"
+msgstr ""
+
+# 4f4164dbe6c04dbeb4b36dfc7b21d25d
+#: ../../source/about.rst:165
+msgid "Host and Storage in maintenance mode"
+msgstr ""
+
+# 1365192c943749548531638c71236d33
+# 4254094b77ad4fccb1d0f27cf30751f1
+#: ../../source/about.rst:168 ../../source/about.rst:491
+msgid "Unsupported Functionalities"
+msgstr ""
+
+# d84bc7b2af5a4cc9b5a4f16fdd148f62
+#: ../../source/about.rst:172
+msgid "Affinity an Anti-Affinity Groups"
+msgstr ""
+
+# c287c4b058c64dcab9d2718477baa0cb
+#: ../../source/about.rst:176
+msgid "Network throttling"
+msgstr ""
+
+# 83063443f6784e209519f3606cc66dff
+#: ../../source/about.rst:180
+msgid "Security groups (Advanced Zone)"
+msgstr ""
+
+# ba3e8a31c31f45b1867b519b1eabb57b
+#: ../../source/about.rst:184
+msgid "IPv6"
+msgstr ""
+
+# d693896fbf4f43b696c1c6bbf627bed3
+#: ../../source/about.rst:188
+msgid "Snapshot: VM and disk"
+msgstr ""
+
+# ff65a2c3e280456981dedd6e461ad5ca
+#: ../../source/about.rst:192
+msgid "PVLAN"
+msgstr ""
+
+# e561849c04c944f8be5a80462ef529e7
+#: ../../source/about.rst:196
+msgid "VPC"
+msgstr "VPC"
+
+# 8274ec6f81de48a7bbdf53bc6db095ed
+#: ../../source/about.rst:200
+msgid "HA of guest VMs"
+msgstr ""
+
+# ba9d79afc26446789bd9270bc1a81915
+#: ../../source/about.rst:204
+msgid "Redundant VR"
+msgstr ""
+
+# 9aa73675588647adabf4ccf233816078
+#: ../../source/about.rst:208
+msgid "Object Store"
+msgstr ""
+
+# 3b87930b1ae2464188590c091bdc9178
+#: ../../source/about.rst:212
+msgid "Mixed hypervisor zone"
+msgstr ""
+
+# 961e37f6a03b43b19b88d6fe12894f12
+#: ../../source/about.rst:216
+msgid "Zone-wide Primary storage"
+msgstr ""
+
+# fcd982c075794659a78690617fad2b1c
+#: ../../source/about.rst:220
+msgid "NIC bonding"
+msgstr ""
+
+# 15429ecd44af40f8acc23d7ce5dad298
+#: ../../source/about.rst:223
+msgid "Enhanced Upgrade for Virtual Routers"
+msgstr ""
+
+# 2e7606316a0d4c4893ef33579783da9c
+#: ../../source/about.rst:225
+msgid ""
+"Upgrading VRs is made flexible. The CloudStack administrators will be able "
+"to control the sequence of the VR upgrades. The sequencing is based on "
+"Infrastructure hierarchy, such as by Cluster, Pod, or Zone, and "
+"Administrative hierarchy, such as by Tenant or Domain. This implies, for "
+"example, that you will have the flexibility to upgrade a VR in a specified "
+"zone. As an administrator, you can also determine when a particular VR can "
+"be upgraded within a specified upgrade interval. Additionally, upgrade "
+"operation is enhanced to increase the upgrade speed by allowing as many "
+"upgrade operations in parallel as possible. During the entire duration of "
+"the upgrade, users cannot launch new services or make changes to an existing"
+" service."
+msgstr ""
+
+# cb50052d577e48138bf33eee32615b7f
+#: ../../source/about.rst:237
+msgid ""
+"To support this feature, a new API, upgradeRouterTemplate, has been "
+"introduced."
+msgstr ""
+
+# 21c4e473dda443e59b2fefad539b0c8f
+#: ../../source/about.rst:240
+msgid ""
+"The detailed instruction is provided in the CloudStack 4.3 Beta "
+"Administration Guide. See section 17.5.5. Enhanced Upgrade for Virtual "
+"Routers."
+msgstr ""
+
+# 4acc8687c449489681ef672832a82bcf
+#: ../../source/about.rst:245
+msgid "Service Monitoring Tool for Virtual Router"
+msgstr ""
+
+# c35b1d53a9d04786934783c6e80af816
+#: ../../source/about.rst:247
+msgid ""
+"Various services running on the CloudStack virtual routers can be monitored "
+"by using a Service Monitoring tool. The tool ensures that services are "
+"successfully running until CloudStack deliberately disables them. If a "
+"service goes down, the tool automatically performs a restart, and if that "
+"does not help bringing up the service, an alert as well as an event is "
+"generated indicating the failure."
+msgstr ""
+
+# fb1814861a52422aa3a1709ed6bd203f
+#: ../../source/about.rst:254
+msgid "The following services are monitored in a VR:"
+msgstr ""
+
+# ba9f7906e3fc407bb578f3e382709e7f
+#: ../../source/about.rst:258
+msgid "DNS"
+msgstr "DNS"
+
+# f106a0ddd91d4a79b85ab48bda92d0b3
+#: ../../source/about.rst:262
+msgid "HA Proxy"
+msgstr ""
+
+# 6bb83f65a4ce438f93386e4cc4d40cc0
+#: ../../source/about.rst:266
+msgid "SSH"
+msgstr ""
+
+# 45474236a1a64471a70a589c10bea027
+#: ../../source/about.rst:270
+msgid "Apache Web Server"
+msgstr ""
+
+# eb9628d7ce8442358f6d52cd48261b62
+#: ../../source/about.rst:272
+msgid "Only the services with daemons are monitored."
+msgstr ""
+
+# 2e5f0bb910be497c8994d25c1f4c000e
+#: ../../source/about.rst:274
+msgid "The following networks are supported:"
+msgstr ""
+
+# aeb04ecf0871477eb3fee51a9dd3eee7
+#: ../../source/about.rst:278
+msgid "Isolated Networks"
+msgstr ""
+
+# 76cc16ee246f4ff59c883f2420897e97
+#: ../../source/about.rst:282
+msgid "Shared Networks in both Advanced and Basic zone"
+msgstr ""
+
+# 9e28655074d246bb9d632f8407063fba
+#: ../../source/about.rst:284
+msgid ""
+"This feature is supported on the following hypervisors: XenServer, VMware, "
+"and KVM."
+msgstr ""
+
+# fd19cabcc1e146ce9a22d1d867f71bd9
+#: ../../source/about.rst:287
+msgid ""
+"The detailed instruction is provided in the CloudStack 4.3 Beta "
+"Administration Guide. See section 17.5.4. Service Monitoring Tool for "
+"Virtual Router."
+msgstr ""
+
+# 3a5da1b1b0824bf4848ea8198d940340
+#: ../../source/about.rst:292
+msgid "Custom Compute Offering"
+msgstr ""
+
+# 0795f8fac93045b89432c223e7dc8ee6
+#: ../../source/about.rst:294
+msgid ""
+"CloudStack provides you the flexibility to specify the desired values for "
+"the number of CPU, CPU speed, and memory while deploying a VM. The admin "
+"creates a Compute Offering by marking it as custom, and as an user, you will"
+" be able to customize this dynamic Compute Offering by specifying the "
+"memory, CPU and root disk at the time of VM creation or upgrade."
+msgstr ""
+
+# 240037ae25e84b6dab9400693c1e78ec
+#: ../../source/about.rst:301
+msgid ""
+"Custom Compute Offering is same as the normal Compute Offering except that "
+"the values of the dynamic parameters will be set to zeros in the given set "
+"of templates. Use this offering to deploy VM by specifying custom values for"
+" the dynamic parameters. Memory, CPU and number of CPUs are considered as "
+"dynamic parameters. Dynamic Compute Offerings can be used in following "
+"cases: deploying a VM, changing the compute offering of a stopped VM and "
+"running VMs, which is nothing but scaling up. To support this feature a new "
+"field, Custom, has been added to the Create Compute Offering page. If the "
+"Custom field is checked, the end-user will be able to create a custom "
+"Compute Offering by filling in the desired values for number of CPU, CPU "
+"speed, and memory."
+msgstr ""
+
+# e2d137d524e24f469e752a7c2f65f843
+#: ../../source/about.rst:314
+msgid "Remote Access VPN for VPC"
+msgstr ""
+
+# b489cdff4c624a9db86a57f457aa9057
+#: ../../source/about.rst:316
+msgid ""
+"Support for Remote access VPN in Isolated networks is now extended to VPC "
+"networks. Remote users will now be able to initiate a VPN connection to a "
+"VPC network. To enable this feature, enable VPN in the Source NAT IP of the "
+"VPC."
+msgstr ""
+
+# 88f5e250dfb04917af3d0b1d6e9e9340
+#: ../../source/about.rst:322
+msgid "Site to Site VPN Connection Between VPC Networks"
+msgstr ""
+
+# 18f849f54ac64bbf8d259746cc0855ff
+#: ../../source/about.rst:324
+msgid ""
+"CloudStack provides you with the ability to establish a site-to-site VPN "
+"connection between CloudStack virtual routers. With this functionality, "
+"users can deploy applications in multiple Availability Zones or VPCs, which "
+"can communicate with each other by using a secure Site-to-Site VPN Tunnel. "
+"Creating a typical Site to Site VPN connection between VPC networks involves"
+" the following:"
+msgstr ""
+
+# f657e6953d9c4ef98bb39ea6ed87d1c8
+#: ../../source/about.rst:333
+msgid "Create two VPCs. For example, VPC A and VPC B."
+msgstr ""
+
+# 31428bba2d1448a5b612c098d2369e34
+#: ../../source/about.rst:337
+msgid "Create VPN gateways on both the VPCs you created."
+msgstr ""
+
+# 43bb7911eae7460d8e708229a8579828
+#: ../../source/about.rst:341
+msgid "Create VPN customer gateway for both the VPCs."
+msgstr ""
+
+# 0a108eb37c714915aadf7cf4935d4688
+#: ../../source/about.rst:345
+msgid "Enable a VPN connection on VPC A in passive mode."
+msgstr ""
+
+# b9a11deaee284017a5c91fdb6c49e471
+#: ../../source/about.rst:347
+msgid ""
+"Ensure that the customer gateway is pointed to VPC B. The VPN connection is "
+"shown in the Disconnected state."
+msgstr ""
+
+# 19dd039bfb6946cab2e77ee83a2f84ee
+#: ../../source/about.rst:352
+msgid "Enable a VPN connection on VPC B."
+msgstr ""
+
+# 40c6521c2b2142c5be66812d44651174
+#: ../../source/about.rst:354
+msgid ""
+"Ensure that the customer gateway is pointed to VPC A. Because virtual router"
+" of VPC A, in this case, is in passive mode and is waiting for the virtual "
+"router of VPC B to initiate the connection. The virtual router of VPC B "
+"should not be in passive mode."
+msgstr ""
+
+# 46ce45d1e33d4f16b911774604c439e5
+#: ../../source/about.rst:359
+msgid "The VPN connection is shown in the Disconnected state."
+msgstr ""
+
+# 2ca835abbdca4b6eba929ddc53f00a74
+#: ../../source/about.rst:361
+msgid ""
+"Creating VPN connection on both the VPCs initiates a VPN connection. Wait "
+"for few seconds. The default is 30 seconds for both the VPN connections to "
+"show the Connected state."
+msgstr ""
+
+# e75896e1324e4a42bbc33a809ef3e353
+#: ../../source/about.rst:366
+msgid "Reporting CPU Sockets"
+msgstr ""
+
+# 60ec77345ae64d8d93f836564151f93b
+#: ../../source/about.rst:368
+msgid ""
+"CloudStack now provides an additional infrastructure statistics for CPU "
+"sockets managed by CloudStack, which in turn reflects the size of the cloud."
+" The Infrastructure tab has a new tab for sockets. The Socket page will give"
+" you the number of hosts an sockets used for each hypervisor type. This "
+"feature is not supported in versions prior to XenServer 6.2."
+msgstr ""
+
+# 8b04c3237e0b437ab6a3cd6dae59b7be
+#: ../../source/about.rst:375
+msgid "Database High Availability"
+msgstr ""
+
+# c2838bb4743343c4ab32c6f638bbd473
+#: ../../source/about.rst:377
+msgid ""
+"To help ensure high availability of the databases that store the internal "
+"data for CloudStack, you can set up database replication. This covers both "
+"the main CloudStack database and the Usage database. Replication is achieved"
+" using the MySQL connector parameters and two-way replication. Tested with "
+"MySQL 5.1 and 5.5. Database replication in CloudStack is provided using the "
+"MySQL replication capabilities. The steps to set up replication can be found"
+" in the MySQL documentation."
+msgstr ""
+
+# 23624a964f744aedad828b991665e2ce
+#: ../../source/about.rst:386
+msgid "LDAP User Provisioning"
+msgstr ""
+
+# 331bf7324ec445c9b20a8454cf28e5fd
+#: ../../source/about.rst:388
+msgid ""
+"LDAP user provisioning has been enhanced by allowing user import from the "
+"configured LDAP servers. You will be able to add multiple LDAP servers and "
+"selectively import LDAP users. You can o filter by group name and import all"
+" the users within a group. After they have been imported to CloudStack, in "
+"contrast to manually adding them in previous releases, users are allowed to "
+"directly log in to CloudStack by using the LDAP credentials."
+msgstr ""
+
+# f5fc680f4b394266bc18e8381d0f1f0d
+#: ../../source/about.rst:397
+msgid "Migrating NFS Secondary Storage to Object Store"
+msgstr ""
+
+# 74028d4c65944efb97e7bfec95297291
+#: ../../source/about.rst:399
+msgid ""
+"In an existing zone that is using NFS for secondary storage, you can upgrade"
+" the zone to use a region-wide object storage without causing downtime. The "
+"existing NFS storage in the zone will be converted to an NFS Staging Store. "
+"After migration, the data that was on the NFS storage remains there. "
+"CloudStack does not provide a way to automatically migrate all data to the "
+"new object storage. The data remaining on the old NFS storage will remain "
+"accessible for read and delete operations only. Newly created snapshots and "
+"templates will be placed in the newly configured object storage."
+msgstr ""
+
+# 058ab0339375451eaafdfcc096005b74
+#: ../../source/about.rst:410
+msgid "VXLAN Plugin Support"
+msgstr ""
+
+# 30e405f84714447884791227096846a9
+#: ../../source/about.rst:412
+msgid ""
+"The VXLAN plugin adds VXLAN as one of the guest network isolation methods in"
+" CloudStack. This plugin enables more than 4096 isolated guest networks in a"
+" Zone, with almost the same usability as VLAN isolation. This plugin "
+"provides no network services. Use virtual router for network services. This "
+"plugin is supported on KVM hypervisors."
+msgstr ""
+
+# dc14ae091f8240a88fdd3342b54c709b
+#: ../../source/about.rst:419
+msgid "Contrail Network Plugin Support"
+msgstr ""
+
+# ed60d48cbddb4d018c53ced482827b14
+#: ../../source/about.rst:421
+msgid ""
+"The Contrail virtual network controller is an open source project that "
+"provides an overlay implementation of network virtualization that is "
+"interoperable with network devices that support existing network "
+"virtualization standards. Support for the Contrail plugin has been added to "
+"CloudStack to provide NAT services to the XenServer hosts. The plugin "
+"supports isolated networks, Static NAT implemented by the VRouter dataplane,"
+" and Source NAT implemented by using a virtual appliance with full NAT "
+"functionality."
+msgstr ""
+
+# 99bf061d28ff4ea8b56dc48abb3915e2
+#: ../../source/about.rst:431
+msgid "Publishing Alert Using the Web ROOT Admin API"
+msgstr ""
+
+# db2ad5c2cb8f43cf84fad3f44cc3f3f9
+#: ../../source/about.rst:433
+msgid ""
+"In previous releases of CloudStack code alerts are generated for CloudStack "
+"services (Usage service) only if they run on the same host as the Management"
+" Server. A new API has been introduced in 4.3, which can be used by the "
+"following services to generate and publish. The services need not be running"
+" on the same host where the Management Server is running."
+msgstr ""
+
+# 665e5482649c40069213ee90d7f4feb1
+#: ../../source/about.rst:442
+msgid "Any new services added to CloudStack."
+msgstr ""
+
+# 2b827219a7c34ad0b6dc5791b65783e0
+#: ../../source/about.rst:446
+msgid "Usage service when run on a separate storage host."
+msgstr ""
+
+# f507ed910d114f6e90e0b5bb23861338
+#: ../../source/about.rst:450
+msgid "Console Proxy and Secondary Storage VM services."
+msgstr ""
+
+# f5b1ab53601944fc85ed83607af9828c
+#: ../../source/about.rst:452
+msgid ""
+"The main advantage of this feature is that the third party systems "
+"integrating with CloudStack will be able to utilize the Alert notification "
+"system publish alerts."
+msgstr ""
+
+# 34cdd6907b05476bab75c2b115f5533c
+#: ../../source/about.rst:457
+msgid "Support for Palo Alto Firewall Service"
+msgstr ""
+
+# 4f1cf6a0c3f242a9829c6fdfe67fdc02
+#: ../../source/about.rst:459
+msgid ""
+"CloudStack supports Palo Alto firewall services. Use the Create Network "
+"Offering dialog to create an offering which has the Palo Alto firewall "
+"services. What is not supported and not supported are given below:"
+msgstr ""
+
+# 52a82b3f2ab64e659f88517461771327
+#: ../../source/about.rst:468
+msgid "Advanced Network"
+msgstr ""
+
+# 13439ff6bc0046229ab0ad9115378aab
+#: ../../source/about.rst:472
+msgid "Parallel deployment with hardware Load balancer"
+msgstr ""
+
+# fcc0e851073f47c094f34865eca68e04
+#: ../../source/about.rst:476
+msgid "Virtual Palo Alto firewall."
+msgstr ""
+
+# 47f70e3d39704a888c679ed51c394fc1
+#: ../../source/about.rst:480
+msgid "Communication layer with Palo Alto APIs."
+msgstr ""
+
+# 1df4648228184b9c8400e1777a713b53
+#: ../../source/about.rst:484
+msgid "Mapping of CloudStack APIs to corresponding Palo Alto APIs."
+msgstr ""
+
+# 2e0b41f6e1434a0f86ee143da29f5334
+#: ../../source/about.rst:488
+msgid "Connectivity status of the firewall service on the CloudStack UI."
+msgstr ""
+
+# 66ab3b2d85c8461e9f6fd9743602a092
+#: ../../source/about.rst:495
+msgid "Inline deployment with hardware Load balancer"
+msgstr ""
+
+# 4323bbdbf12049538df46b6e62f679f2
+#: ../../source/about.rst:499
+msgid "Firewall between VLANs within an advanced network"
+msgstr ""
+
+# 0ab363d048474009ad3e44c2477d96b1
+#: ../../source/about.rst:503
+msgid "Firewall between VM instances"
+msgstr ""
+
+# 69922eb6f88249c2a1dbedd6dfe07f29
+#: ../../source/about.rst:505
+msgid ""
+"For more information, see `Palo Alto Firewall Integration "
+"<https://cwiki.apache.org/confluence/display/CLOUDSTACK/Palo+Alto+Firewall+Integration>`__."
+msgstr ""
+
+# 160529cf6dd04d9c8425fc5a412bf663
+#: ../../source/about.rst:509
+msgid "Root Volume Metering"
+msgstr ""
+
+# 57e7c64781b94df9ae9f15762ba55bc5
+#: ../../source/about.rst:511
+msgid ""
+"CloudStack supports recording usage events as per the dynamically assigned "
+"resources. Usage events are registered when a VM is created from dynamic "
+"service offering, and the values of parameters, such as CPU, speed, RAM are "
+"recorded. If VM is deployed by using template and dynamic root disk size is "
+"mentioned, the same value is recorded in the usage event."
+msgstr ""
+
+# c1f66f4c3bcf472ea617423ea52cb810
+#: ../../source/about.rst:519
+msgid "Support for SSL Termination"
+msgstr ""
+
+# 7749d124b6644556bd3a63077e67061e
+#: ../../source/about.rst:521
+msgid ""
+"SSL Offloading allows load balancers to handle encryption and decryption of "
+"HTTP(s) traffic giving plain text HTTP to the back end servers freeing them "
+"from the resource intensive task of handling encryption and decryption. "
+"Supported for Citrix NetScaler."
+msgstr ""
+
+# 490936156baf4f4ba40bad5b2221c2e9
+#: ../../source/about.rst:527
+msgid "Support for Pluggable VM Snapshots"
+msgstr ""
+
+# 828973faf95349c18f17384f083aafd1
+#: ../../source/about.rst:529
+msgid ""
+"CloudStack implements a plugin to integrate a third-party storage provider. "
+"Third party storage providers can integrate with CloudStack to provide "
+"either primary storage or secondary storage. The user enables a storage "
+"plugin through the UI. A new dialog box choice is offered to select the "
+"storage provider. Depending on which provider is selected, additional input "
+"fields may appear so that the user can provide the additional details "
+"required by that provider, such as a user name and password for a third-"
+"party storage account."
+msgstr ""
+
+# 6cbc29938aab4a04a48fa4b658c07e12
+#: ../../source/about.rst:539
+msgid "Enhanced CloudStack UI"
+msgstr ""
+
+# 69867013f6ff439fbdaea9046df092f9
+#: ../../source/about.rst:541
+msgid ""
+"A complete UI makeover is implemented to enhance the usability and user "
+"experience in modern browsers. The visual look-and-feel has been changed for"
+" the Header, Navigation, Buttons, text fields, drop-downs, tables and so on."
+" Consistent color themes has been introduced to match with the Apache "
+"branding."
+msgstr ""
+
+# e0c1d3a4dff54cd29a1fde49db79ba44
+#: ../../source/about.rst:547
+msgid "The current UI flow remains the same."
+msgstr ""
+
+# 8a9111236af743469d0f01c8f1c02daa
+#: ../../source/about.rst:550
+msgid "Issues Fixed in 4.3.0"
+msgstr ""
+
+# edb7bea4958c44ed83296e9b8937e67a
+# 936db570e1784d7e942c5cc73564f7e8
+#: ../../source/about.rst:552 ../../source/about.rst:727
+msgid ""
+"Apache CloudStack uses `Jira "
+"<https://issues.apache.org/jira/browse/CLOUDSTACK>`__ to track its issues. "
+"All new features and bugs for 4.3 have been tracked in Jira, and have a "
+"standard naming convention of \"CLOUDSTACK-NNNN\" where \"NNNN\" is the "
+"issue number."
+msgstr ""
+
+# b948cc1f76a943a4b819da6d75e0e02a
+#: ../../source/about.rst:555
+msgid ""
+"For the list of issues fixed, see `Issues Fixed in 4.3 "
+"<https://issues.apache.org/jira/issues/?filter=12326161>`__."
+msgstr ""
+
+# dc2cafa99fd94368b2b85b22934e57ae
+# 6f3bbaf12ebe4e389f4c5d690538551a
+#: ../../source/about.rst:559 ../../source/about.rst:734
+msgid "Bug ID"
+msgstr ""
+
+# 8d1125706d604c378cf3452f646c1b75
+# af767f946b1347dbbce5a5a9ad2407cb
+#: ../../source/about.rst:559 ../../source/about.rst:734
+msgid "Description"
+msgstr "説明"
+
+# b3c560a66bcd42b5bf60b8464ce65e1e
+#: ../../source/about.rst:561
+msgid ""
+"`CLOUDSTACK-6103 <https://issues.apache.org/jira/browse/CLOUDSTACK-6103>`_"
+msgstr ""
+
+# 60ad9b5a7cb64632b0c95187e3731446
+#: ../../source/about.rst:561
+msgid "vms with isos attached don't migrate..."
+msgstr ""
+
+# 20872e6668c044e8a38dc23103c2fe1d
+#: ../../source/about.rst:562
+msgid ""
+"`CLOUDSTACK-6089 <https://issues.apache.org/jira/browse/CLOUDSTACK-6089>`_"
+msgstr ""
+
+# 5f24746917154bd9becf37fa2ebbbf4c
+#: ../../source/about.rst:562
+msgid "resource tags show up in multiples..."
+msgstr ""
+
+# 2969ae4a020b4e89955194318fda0fc0
+#: ../../source/about.rst:563
+msgid ""
+"`CLOUDSTACK-6046 <https://issues.apache.org/jira/browse/CLOUDSTACK-6046>`_"
+msgstr ""
+
+# eb94c9151f1940279f52e10913ee8bb4
+#: ../../source/about.rst:563
+msgid ""
+"CreateVolume from snapshot is failing with S3 as secondary storage and zone-"
+"wide..."
+msgstr ""
+
+# 3fff64589a7d42ca8055ea36e01a4884
+#: ../../source/about.rst:564
+msgid ""
+"`CLOUDSTACK-6040 <https://issues.apache.org/jira/browse/CLOUDSTACK-6040>`_"
+msgstr ""
+
+# 9e5931f448b949f9a826817301799eab
+#: ../../source/about.rst:564
+msgid "Failed to configure PF on vm secondary ip for shared network..."
+msgstr ""
+
+# 1590eb52696e442ea08b5735209b54be
+#: ../../source/about.rst:565
+msgid ""
+"`CLOUDSTACK-6007 <https://issues.apache.org/jira/browse/CLOUDSTACK-6007>`_"
+msgstr ""
+
+# 7f0ee23c76394aa3b0090a46ba3379f9
+#: ../../source/about.rst:565
+msgid "[VMware] RestoreVM API fails with NPE..."
+msgstr ""
+
+# ac80ffe92d0d4317a94bd8b01acd2312
+#: ../../source/about.rst:566
+msgid ""
+"`CLOUDSTACK-5986 <https://issues.apache.org/jira/browse/CLOUDSTACK-5986>`_"
+msgstr ""
+
+# b70b2bb0f7f54c38a4b59f5d2774e522
+#: ../../source/about.rst:566
+msgid ""
+"dnsmasq racy condition result in dnsmasq failed to handout IP address..."
+msgstr ""
+
+# 7a8bfa08a17548618f90bc7ba426bafd
+#: ../../source/about.rst:567
+msgid ""
+"`CLOUDSTACK-5971 <https://issues.apache.org/jira/browse/CLOUDSTACK-5971>`_"
+msgstr ""
+
+# 75b75eb5703b475eb4b39507eceda5ce
+#: ../../source/about.rst:567
+msgid "Templates created from a snapshots can't be copied to other zones..."
+msgstr ""
+
+# 9d4b1863eb3e4cca956ab8afa343b44c
+#: ../../source/about.rst:568
+msgid ""
+"`CLOUDSTACK-5960 <https://issues.apache.org/jira/browse/CLOUDSTACK-5960>`_"
+msgstr ""
+
+# 35a2fd2cbd2f4803ab2c6619669b941f
+#: ../../source/about.rst:568
+msgid ""
+"Domain admin or user cannot register a template using S3/Swift object "
+"store..."
+msgstr ""
+
+# 3ec65f14592547faaf8b9585e212f904
+#: ../../source/about.rst:569
+msgid ""
+"`CLOUDSTACK-5922 <https://issues.apache.org/jira/browse/CLOUDSTACK-5922>`_"
+msgstr ""
+
+# 64bacb27a8274bfe87ba48b6c442cda6
+#: ../../source/about.rst:569
+msgid "Incorrect handling RHEL guests ..."
+msgstr ""
+
+# d573ea887741418395b23a3088560c26
+#: ../../source/about.rst:570
+msgid ""
+"`CLOUDSTACK-5921 <https://issues.apache.org/jira/browse/CLOUDSTACK-5921>`_"
+msgstr ""
+
+# 21f626a6874c4b0e82ebbd1e08ef6cbc
+#: ../../source/about.rst:570
+msgid "S3 security key is stored in DB unencrypted..."
+msgstr ""
+
+# 013caae5f40c44c19cff4eae1047025b
+#: ../../source/about.rst:571
+msgid ""
+"`CLOUDSTACK-5903 <https://issues.apache.org/jira/browse/CLOUDSTACK-5903>`_"
+msgstr ""
+
+# 11372c63ca934240abbc4bd7f46fabb8
+#: ../../source/about.rst:571
+msgid "CLONE - OVA files exist for templates created from volumes..."
+msgstr ""
+
+# 95eaa5b600394575b72ce84f1bf79773
+#: ../../source/about.rst:572
+msgid ""
+"`CLOUDSTACK-5895 <https://issues.apache.org/jira/browse/CLOUDSTACK-5895>`_"
+msgstr ""
+
+# 54311c1a2a5d4074ab3ddbebd805c1e9
+#: ../../source/about.rst:572
+msgid ""
+"CreateVolumeFromSnapshot can fail in a multiple pod environment with tagged "
+"stor..."
+msgstr ""
+
+# 7995568a728943bf914af11f559a23d5
+#: ../../source/about.rst:573
+msgid ""
+"`CLOUDSTACK-5886 <https://issues.apache.org/jira/browse/CLOUDSTACK-5886>`_"
+msgstr ""
+
+# fa51e778d56946a5a0f698f9ce3a8355
+#: ../../source/about.rst:573
+msgid "4.2.1 upgrade fails on acl migration..."
+msgstr ""
+
+# f65f098cb13b4ad7bf6b300e36c8634c
+#: ../../source/about.rst:574
+msgid ""
+"`CLOUDSTACK-5877 <https://issues.apache.org/jira/browse/CLOUDSTACK-5877>`_"
+msgstr ""
+
+# 4bda684192f543c1a3261925ac7fd778
+#: ../../source/about.rst:574
+msgid "listTemplates does not sort based on sort_key..."
+msgstr ""
+
+# 2561e890c4af48d7bff25009e8be8e78
+#: ../../source/about.rst:575
+msgid ""
+"`CLOUDSTACK-5875 <https://issues.apache.org/jira/browse/CLOUDSTACK-5875>`_"
+msgstr ""
+
+# e0b0fc87fc4a4d36b23eae1524ece1d5
+#: ../../source/about.rst:575
+msgid "No templates in simulator run..."
+msgstr ""
+
+# 93552171f0dd407caee4ffa27125d13a
+#: ../../source/about.rst:576
+msgid ""
+"`CLOUDSTACK-5864 <https://issues.apache.org/jira/browse/CLOUDSTACK-5864>`_"
+msgstr ""
+
+# fd0da60db85d445ab32de0ff25b52e23
+#: ../../source/about.rst:576
+msgid "Simulator profile broken ..."
+msgstr ""
+
+# a2f90a6fe1784bf0b333d459d84f9f4e
+#: ../../source/about.rst:577
+msgid ""
+"`CLOUDSTACK-5813 <https://issues.apache.org/jira/browse/CLOUDSTACK-5813>`_"
+msgstr ""
+
+# 2969c5d4941a4964bef59c9e35f79a6b
+#: ../../source/about.rst:577
+msgid ""
+"With S3 as secondary storage, snapshot taken in one zone cannot be used to "
+"creat..."
+msgstr ""
+
+# bd8ddd2ee2604f1989dfddb1fd3e5690
+#: ../../source/about.rst:578
+msgid ""
+"`CLOUDSTACK-5723 <https://issues.apache.org/jira/browse/CLOUDSTACK-5723>`_"
+msgstr ""
+
+# 51d46a1458154066a9db40277cbb3a8a
+#: ../../source/about.rst:578
+msgid "Malfunction agent may block future SSL connection to the server..."
+msgstr ""
+
+# 84772a0b67b7462d878f4c45cee5d6c7
+#: ../../source/about.rst:579
+msgid ""
+"`CLOUDSTACK-5704 <https://issues.apache.org/jira/browse/CLOUDSTACK-5704>`_"
+msgstr ""
+
+# 5cd5aef611824dcab41292dfc1868e1c
+#: ../../source/about.rst:579
+msgid "OVA files exist for templates created from volumes..."
+msgstr ""
+
+# 39b22027316c4e2590a87bd8445a3ec8
+#: ../../source/about.rst:580
+msgid ""
+"`CLOUDSTACK-5701 <https://issues.apache.org/jira/browse/CLOUDSTACK-5701>`_"
+msgstr ""
+
+# b47788afd6c84b78b75d9df79b0356a7
+#: ../../source/about.rst:580
+msgid "size column is not getting updated in snapshot_store_ref table...."
+msgstr ""
+
+# 6507a2db556f4f10af283fbd0c653507
+#: ../../source/about.rst:581
+msgid ""
+"`CLOUDSTACK-5666 <https://issues.apache.org/jira/browse/CLOUDSTACK-5666>`_"
+msgstr ""
+
+# fd33a6e0c759429cabac88ad679fed3f
+#: ../../source/about.rst:581
+msgid "Cant remove a nic when a vm is in the Stopped state ..."
+msgstr ""
+
+# df2dffc8b41149b9ae91c736b3167d4b
+#: ../../source/about.rst:582
+msgid ""
+"`CLOUDSTACK-5661 <https://issues.apache.org/jira/browse/CLOUDSTACK-5661>`_"
+msgstr ""
+
+# deb50800f21042faa3496ce106be4da3
+#: ../../source/about.rst:582
+msgid ""
+"[VMware] DetachIsoCmd succeeds even though cdrom is locked by VM as cdrom is"
+" mou..."
+msgstr ""
+
+# 1ec5e73f57af4813b2676b9182b41365
+#: ../../source/about.rst:583
+msgid ""
+"`CLOUDSTACK-5653 <https://issues.apache.org/jira/browse/CLOUDSTACK-5653>`_"
+msgstr ""
+
+# c23f25dc96224a10a1e3643549fad689
+#: ../../source/about.rst:583
+msgid ""
+"S3 object store as Secondary Storage, the template created from different "
+"zone i..."
+msgstr ""
+
+# fd895562ee3043289906b0530817d6ee
+#: ../../source/about.rst:584
+msgid ""
+"`CLOUDSTACK-5613 <https://issues.apache.org/jira/browse/CLOUDSTACK-5613>`_"
+msgstr ""
+
+# 126d72ade2e440fca675e315a84c3356
+#: ../../source/about.rst:584
+msgid "CloudStack 4.2.0 - Usage server is running but tables remain empty..."
+msgstr ""
+
+# 3e010bd06edf4cde914fb226e5d53669
+#: ../../source/about.rst:585
+msgid ""
+"`CLOUDSTACK-5608 <https://issues.apache.org/jira/browse/CLOUDSTACK-5608>`_"
+msgstr ""
+
+# 2f981d66bf5249fba995d224509f5801
+#: ../../source/about.rst:585
+msgid ""
+"HyperV Builtin and System vm template entries missing in 4.3 upgrade "
+"setup..."
+msgstr ""
+
+# 3befdc8910aa4e629b9beff787d723a7
+#: ../../source/about.rst:586
+msgid ""
+"`CLOUDSTACK-5534 <https://issues.apache.org/jira/browse/CLOUDSTACK-5534>`_"
+msgstr ""
+
+# ee69a4436e084b50b3ac4d2d892cfd4b
+#: ../../source/about.rst:586
+msgid "MySQL exception raised when searching for users with keyword..."
+msgstr ""
+
+# 204e779344434bf49b4990da0e0b5ae7
+#: ../../source/about.rst:587
+msgid ""
+"`CLOUDSTACK-5533 <https://issues.apache.org/jira/browse/CLOUDSTACK-5533>`_"
+msgstr ""
+
+# bfcafcab103145d4bc2308df6538b97f
+#: ../../source/about.rst:587
+msgid ""
+"Virtual router in shared network does respond to DNS even when no DNS "
+"service is..."
+msgstr ""
+
+# 224a56ae47aa4e7f967b83cf56a9ae00
+#: ../../source/about.rst:588
+msgid ""
+"`CLOUDSTACK-5532 <https://issues.apache.org/jira/browse/CLOUDSTACK-5532>`_"
+msgstr ""
+
+# 56c70a2b75544a7482348c3a3ca3c4e4
+#: ../../source/about.rst:588
+msgid "Long tag values are not readable within the UI..."
+msgstr ""
+
+# 59cd0224ac764c7e91fe5ca45e365618
+#: ../../source/about.rst:589
+msgid ""
+"`CLOUDSTACK-5519 <https://issues.apache.org/jira/browse/CLOUDSTACK-5519>`_"
+msgstr ""
+
+# 7497b1ecef6e4aa78d5fc1945d1552e6
+#: ../../source/about.rst:589
+msgid ""
+"[VMWARE] Cancel vCenter tasks if the task invoked by CloudStack failes with "
+"time..."
+msgstr ""
+
+# 84eecbc8809c4204945afd28051d6075
+#: ../../source/about.rst:590
+msgid ""
+"`CLOUDSTACK-5517 <https://issues.apache.org/jira/browse/CLOUDSTACK-5517>`_"
+msgstr ""
+
+# 1770b7849bdf4f5d9cf17dd123595ea0
+#: ../../source/about.rst:590
+msgid "NPE observed during \"release portable IPs\" as part of account cleanup..."
+msgstr ""
+
+# 6cf798c00fae47038554efc5ad560015
+#: ../../source/about.rst:591
+msgid ""
+"`CLOUDSTACK-5514 <https://issues.apache.org/jira/browse/CLOUDSTACK-5514>`_"
+msgstr ""
+
+# a1a26f07a1274e1f937292bd447f35e3
+#: ../../source/about.rst:591
+msgid "Response of listAccounts API call includes removed users..."
+msgstr ""
+
+# 4055fb97d2ae41dba3e487b614a92113
+#: ../../source/about.rst:592
+msgid ""
+"`CLOUDSTACK-5513 <https://issues.apache.org/jira/browse/CLOUDSTACK-5513>`_"
+msgstr ""
+
+# 0c69091ed0e24c219ea7c3dfa20ac561
+#: ../../source/about.rst:592
+msgid "VM can't start after creating snapshot from it (CS4.2 + VMware 5.1)..."
+msgstr ""
+
+# 3a69c0084f3b42d2a76bbecea47de6df
+#: ../../source/about.rst:593
+msgid ""
+"`CLOUDSTACK-5481 <https://issues.apache.org/jira/browse/CLOUDSTACK-5481>`_"
+msgstr ""
+
+# 471db3db35e04972bff608e3efab2c83
+#: ../../source/about.rst:593
+msgid "Regular User is unable to use \"Add Isolated Network\" Button on the UI..."
+msgstr ""
+
+# 5215fb218db64494809cabf08f864147
+#: ../../source/about.rst:594
+msgid ""
+"`CLOUDSTACK-5466 <https://issues.apache.org/jira/browse/CLOUDSTACK-5466>`_"
+msgstr ""
+
+# 52c053355ae24c43b3eec6b4568b66ca
+#: ../../source/about.rst:594
+msgid "removeIpFromNic not working properly..."
+msgstr ""
+
+# 787d3ea9522f4d7db790f56c00642a65
+#: ../../source/about.rst:595
+msgid ""
+"`CLOUDSTACK-5453 <https://issues.apache.org/jira/browse/CLOUDSTACK-5453>`_"
+msgstr ""
+
+# 9a39d357304442b98b4dad13e46a429c
+#: ../../source/about.rst:595
+msgid "Site-to-site VPN connection status monitoring is broken in KVM..."
+msgstr ""
+
+# bdc0c48b41554b6ab91402d766016e96
+#: ../../source/about.rst:596
+msgid ""
+"`CLOUDSTACK-5431 <https://issues.apache.org/jira/browse/CLOUDSTACK-5431>`_"
+msgstr ""
+
+# d2aa88a55c9f40dab4fd0a702d59883a
+#: ../../source/about.rst:596
+msgid "permit 'http' as service type for GSLB rule..."
+msgstr ""
+
+# cfd5c3da8c8f4569bd44afb26bac058d
+#: ../../source/about.rst:597
+msgid ""
+"`CLOUDSTACK-5428 <https://issues.apache.org/jira/browse/CLOUDSTACK-5428>`_"
+msgstr ""
+
+# 9b38642a1eb145a28ff6bdc0fb01abe8
+#: ../../source/about.rst:597
+msgid ""
+"support NetScaler to be configured exclusively for GSLB service and not used"
+" for..."
+msgstr ""
+
+# 92ffb1c72f6f4c989c847a3d159b2b6d
+#: ../../source/about.rst:598
+msgid ""
+"`CLOUDSTACK-5426 <https://issues.apache.org/jira/browse/CLOUDSTACK-5426>`_"
+msgstr ""
+
+# 785d11d1b4b74c3c8a9cab733bcb1c6f
+#: ../../source/about.rst:598
+msgid ""
+"Cannot deploy instance having multiple volumes that use different storage "
+"tags f..."
+msgstr ""
+
+# 365fd10374254b4ba4ae8b1b9f64a797
+#: ../../source/about.rst:599
+msgid ""
+"`CLOUDSTACK-5422 <https://issues.apache.org/jira/browse/CLOUDSTACK-5422>`_"
+msgstr ""
+
+# f96e4bb29ea247e69fc942db8a0d5db7
+#: ../../source/about.rst:599
+msgid "Changing XenServer Tools Version 6.1 + doesnt work ..."
+msgstr ""
+
+# 6cb5ca7d32d14a1d9f13d0697874da07
+#: ../../source/about.rst:600
+msgid ""
+"`CLOUDSTACK-5417 <https://issues.apache.org/jira/browse/CLOUDSTACK-5417>`_"
+msgstr ""
+
+# df9d2495dbaa457db9ddce1bca1308ea
+#: ../../source/about.rst:600
+msgid ""
+"On network restart for external devices egress rules configured with old "
+"CIDR..."
+msgstr ""
+
+# 8ab00ac30e094f938ccf295d0dc184f9
+#: ../../source/about.rst:601
+msgid ""
+"`CLOUDSTACK-5416 <https://issues.apache.org/jira/browse/CLOUDSTACK-5416>`_"
+msgstr ""
+
+# df28d08e10114f5a8e5ce0d8ce609f37
+#: ../../source/about.rst:601
+msgid "[VMware] Not able to add seventh disk to VM in an upgraded setup..."
+msgstr ""
+
+# 66150c3309a54123aeb1174fe926903e
+#: ../../source/about.rst:602
+msgid ""
+"`CLOUDSTACK-5404 <https://issues.apache.org/jira/browse/CLOUDSTACK-5404>`_"
+msgstr ""
+
+# dc30931a10f44f958e4dab4a8f26af4b
+#: ../../source/about.rst:602
+msgid ""
+"Network usages (bytes sent/received) are saved in the wrong timezone..."
+msgstr ""
+
+# 05cf80b1a9e1451eb2cd825cac620c0c
+#: ../../source/about.rst:603
+msgid ""
+"`CLOUDSTACK-5401 <https://issues.apache.org/jira/browse/CLOUDSTACK-5401>`_"
+msgstr ""
+
+# 477a4f6910be4a8c9609fb522f89c655
+#: ../../source/about.rst:603
+msgid ""
+"VM migration during host maintenance fails if "
+"pool.storage.capacity.disablethres..."
+msgstr ""
+
+# 9bedfe8d327840ba8d5d3df0578dab36
+#: ../../source/about.rst:604
+msgid ""
+"`CLOUDSTACK-5391 <https://issues.apache.org/jira/browse/CLOUDSTACK-5391>`_"
+msgstr ""
+
+# d1918d6b593c45b4a769dc3eca90364f
+#: ../../source/about.rst:604
+msgid ""
+"Change service offering of a stopped vm and then starting it should check "
+"host c..."
+msgstr ""
+
+# 8cc263da77dc48048502764c176974f2
+#: ../../source/about.rst:605
+msgid ""
+"`CLOUDSTACK-5355 <https://issues.apache.org/jira/browse/CLOUDSTACK-5355>`_"
+msgstr ""
+
+# c94679b661e6408893eb76bdaba36221
+#: ../../source/about.rst:605
+msgid "addImageStore should not log password in clear text in the log..."
+msgstr ""
+
+# c4333272ddc04f51b83cf83496cdd50c
+#: ../../source/about.rst:606
+msgid ""
+"`CLOUDSTACK-5354 <https://issues.apache.org/jira/browse/CLOUDSTACK-5354>`_"
+msgstr ""
+
+# 531fe50313bd49ccbf95f0c3df7ac098
+#: ../../source/about.rst:606
+msgid "CLONE - UI - normal users are not allowed to edit their own iso..."
+msgstr ""
+
+# 10366a1f27134ab49045a5939ed34cc8
+#: ../../source/about.rst:607
+msgid ""
+"`CLOUDSTACK-5352 <https://issues.apache.org/jira/browse/CLOUDSTACK-5352>`_"
+msgstr ""
+
+# 7ff3df608e5c4b76bddd875446178da9
+#: ../../source/about.rst:607
+msgid "CPU cap calculated incorrectly for VMs on XenServer hosts..."
+msgstr ""
+
+# 8def818865644b468ff9af6d6eb751dd
+#: ../../source/about.rst:608
+msgid ""
+"`CLOUDSTACK-5332 <https://issues.apache.org/jira/browse/CLOUDSTACK-5332>`_"
+msgstr ""
+
+# f868f359bc3d46aabbe334e1ad95a584
+#: ../../source/about.rst:608
+msgid "Network offering don't use new system offering for router..."
+msgstr ""
+
+# 37a6e73a71834a49b653090c8e2ce161
+#: ../../source/about.rst:609
+msgid ""
+"`CLOUDSTACK-5303 <https://issues.apache.org/jira/browse/CLOUDSTACK-5303>`_"
+msgstr ""
+
+# 0a663b1b99d94382ada269bd9b93e2b6
+#: ../../source/about.rst:609
+msgid ""
+"\"snapshot\" count and \"secondary_storage\" count are not correct in "
+"resource_coun..."
+msgstr ""
+
+# 0bb8849ac8ce4c9eab76ab9ff94f6eb7
+#: ../../source/about.rst:610
+msgid ""
+"`CLOUDSTACK-5302 <https://issues.apache.org/jira/browse/CLOUDSTACK-5302>`_"
+msgstr ""
+
+# e9b30caa38064a7aa10f72c00a54c52b
+#: ../../source/about.rst:610
+msgid "listHosts API response - value of cpuallocated is always 0%..."
+msgstr ""
+
+# c8e381f6b0cb440d8b61c78dc449cd29
+#: ../../source/about.rst:611
+msgid ""
+"`CLOUDSTACK-5299 <https://issues.apache.org/jira/browse/CLOUDSTACK-5299>`_"
+msgstr ""
+
+# 1c1c5f7e616a400caa4bc59b4cbbc14c
+#: ../../source/about.rst:611
+msgid "Can not get hypervisor type for volumes..."
+msgstr ""
+
+# 19425611d0264d0a8e7a5c6523dea2da
+#: ../../source/about.rst:612
+msgid ""
+"`CLOUDSTACK-5293 <https://issues.apache.org/jira/browse/CLOUDSTACK-5293>`_"
+msgstr ""
+
+# 252a6ef04eae41aba3ef59cf2fd55f87
+#: ../../source/about.rst:612
+msgid ""
+"Error while collecting vm disk stats from hosts if iso is attached to vm..."
+msgstr ""
+
+# 6965e373a81042f9a9af73a92dd627fb
+#: ../../source/about.rst:613
+msgid ""
+"`CLOUDSTACK-5285 <https://issues.apache.org/jira/browse/CLOUDSTACK-5285>`_"
+msgstr ""
+
+# 09e08756611440839a311b2d3fb774d9
+#: ../../source/about.rst:613
+msgid "Correct the API command description for removeIpFromNic..."
+msgstr ""
+
+# c765565cafc943cc86a873694ce66cb9
+#: ../../source/about.rst:614
+msgid ""
+"`CLOUDSTACK-5261 <https://issues.apache.org/jira/browse/CLOUDSTACK-5261>`_"
+msgstr ""
+
+# f83b311847994b95bb23f9bfe2e6ffc1
+#: ../../source/about.rst:614
+msgid "Ability to publish Alerts via CS Root API..."
+msgstr ""
+
+# c1f2ddad98214ea0b53d6a3903ecb350
+#: ../../source/about.rst:615
+msgid ""
+"`CLOUDSTACK-5260 <https://issues.apache.org/jira/browse/CLOUDSTACK-5260>`_"
+msgstr ""
+
+# 798b013ee93f408789382110fce51778
+#: ../../source/about.rst:615
+msgid "Vmware 5.1 Deploy Template Error : Read Timeout..."
+msgstr ""
+
+# e0608e327ca84eda935169365fd535d5
+#: ../../source/about.rst:616
+msgid ""
+"`CLOUDSTACK-5228 <https://issues.apache.org/jira/browse/CLOUDSTACK-5228>`_"
+msgstr ""
+
+# 4385c25da5c341a19a0b7a7f634cf6f1
+#: ../../source/about.rst:616
+msgid ""
+"[API] [EIP/ELB enabled Zone] Need to display EIP address as \"Public IP "
+"Address\" ..."
+msgstr ""
+
+# 65bc7d76ad4345b9b1f46dd44a2e867f
+#: ../../source/about.rst:617
+msgid ""
+"`CLOUDSTACK-5227 <https://issues.apache.org/jira/browse/CLOUDSTACK-5227>`_"
+msgstr ""
+
+# 356fc4cc94ad4000b83f7e65d2e008c9
+#: ../../source/about.rst:617
+msgid "Cannot pass Japanese characters as parameter values to API..."
+msgstr ""
+
+# 8db4754695944bfe9e329296ac80bcd8
+#: ../../source/about.rst:618
+msgid ""
+"`CLOUDSTACK-5218 <https://issues.apache.org/jira/browse/CLOUDSTACK-5218>`_"
+msgstr ""
+
+# ae0b81b811a84cf7a4eecc734f061df9
+#: ../../source/about.rst:618
+msgid ""
+"CLONE - [Doc] Make VMware vCenter session timeout value configurable...."
+msgstr ""
+
+# 9b93a94c174b4089ae64219475781428
+#: ../../source/about.rst:619
+msgid ""
+"`CLOUDSTACK-5199 <https://issues.apache.org/jira/browse/CLOUDSTACK-5199>`_"
+msgstr ""
+
+# 6ab3889236d7416fa815a6825d3bff5c
+#: ../../source/about.rst:619
+msgid ""
+"Cannot restart VM after taking a VM snapshot of an existing VM or reverting "
+"a VM..."
+msgstr ""
+
+# 26aa3abc88c6468898df5d9fb38f3570
+#: ../../source/about.rst:620
+msgid ""
+"`CLOUDSTACK-5141 <https://issues.apache.org/jira/browse/CLOUDSTACK-5141>`_"
+msgstr ""
+
+# b26d24381fc54173b48b37dd1163d779
+#: ../../source/about.rst:620
+msgid ""
+"[Automation] Router deployment failed due to failure in SavePasswordCommand,"
+" obs..."
+msgstr ""
+
+# e2d5d651311543bea190e1ad6b018d62
+#: ../../source/about.rst:621
+msgid ""
+"`CLOUDSTACK-5140 <https://issues.apache.org/jira/browse/CLOUDSTACK-5140>`_"
+msgstr ""
+
+# d0f86a6e0cf344f6b651d4550e44c1e3
+#: ../../source/about.rst:621
+msgid ""
+"A stopped vm cant start after disable threshold has been reached on the "
+"storage ..."
+msgstr ""
+
+# e3ad276c6e7f48ec9f2cbf0e647a15d5
+#: ../../source/about.rst:622
+msgid ""
+"`CLOUDSTACK-5138 <https://issues.apache.org/jira/browse/CLOUDSTACK-5138>`_"
+msgstr ""
+
+# 10841b65c88a4dd0aa89d4dee8eca6c6
+#: ../../source/about.rst:622
+msgid "[Automation] NPE while create template from snapshot..."
+msgstr ""
+
+# 86779fef657742789a83db76e4f35613
+#: ../../source/about.rst:623
+msgid ""
+"`CLOUDSTACK-5122 <https://issues.apache.org/jira/browse/CLOUDSTACK-5122>`_"
+msgstr ""
+
+# 1bb27372472b4c01b39fd736d536f7d3
+#: ../../source/about.rst:623
+msgid ""
+"[VMware] System VMs are getting recreated with old template after upgrading "
+"to 4..."
+msgstr ""
+
+# 290b6c8dba5340f6800b7e62b8b02faf
+#: ../../source/about.rst:624
+msgid ""
+"`CLOUDSTACK-5105 <https://issues.apache.org/jira/browse/CLOUDSTACK-5105>`_"
+msgstr ""
+
+# b0cf2b62404a4fcaae9f7e3e6157b3cb
+#: ../../source/about.rst:624
+msgid "Template/ISO download fails cause the object to disappear from UI..."
+msgstr ""
+
+# 065e55629e6f43fa8f985b5aa2eee3d0
+#: ../../source/about.rst:625
+msgid ""
+"`CLOUDSTACK-5098 <https://issues.apache.org/jira/browse/CLOUDSTACK-5098>`_"
+msgstr ""
+
+# afb576415a9e49628133a72e1c5a5182
+#: ../../source/about.rst:625
+msgid ""
+"[UI] Zone view is showing \"Add VMware Datacenter\" button even though zone "
+"is alr..."
+msgstr ""
+
+# af71183c79eb44aca10e1a61e369c1dc
+#: ../../source/about.rst:626
+msgid ""
+"`CLOUDSTACK-5092 <https://issues.apache.org/jira/browse/CLOUDSTACK-5092>`_"
+msgstr ""
+
+# d7b8970346074c11956828f012538721
+#: ../../source/about.rst:626
+msgid ""
+"[Automation] [BVT] Failed to copy template and ISO between zones in xen ..."
+msgstr ""
+
+# 004c1f58b369468aadf01d00d08d4778
+#: ../../source/about.rst:627
+msgid ""
+"`CLOUDSTACK-5076 <https://issues.apache.org/jira/browse/CLOUDSTACK-5076>`_"
+msgstr ""
+
+# 1e532b576ee34201b4f5c2d9ae8e18ea
+#: ../../source/about.rst:627
+msgid "(Upgrade) reboot VM failed after bridge name change..."
+msgstr ""
+
+# bd115062edf44791a9f01372999f5db0
+#: ../../source/about.rst:628
+msgid ""
+"`CLOUDSTACK-5069 <https://issues.apache.org/jira/browse/CLOUDSTACK-5069>`_"
+msgstr ""
+
+# 201a29d9cbd64bddac6272d6cc4edf5e
+#: ../../source/about.rst:628
+msgid "Make VMware vCenter session timeout value configurable...."
+msgstr ""
+
+# 873b01cf76a34e23807c12cf4029e712
+#: ../../source/about.rst:629
+msgid ""
+"`CLOUDSTACK-5066 <https://issues.apache.org/jira/browse/CLOUDSTACK-5066>`_"
+msgstr ""
+
+# 4df823c4757d4c73a89b70da9eaaf208
+#: ../../source/about.rst:629
+msgid "Existed remote access VPN got dropped when adding new VPN users..."
+msgstr ""
+
+# c8c1e8ef17d941b19257cd795098d730
+#: ../../source/about.rst:630
+msgid ""
+"`CLOUDSTACK-5062 <https://issues.apache.org/jira/browse/CLOUDSTACK-5062>`_"
+msgstr ""
+
+# 3060b3b742bc43e5b2db246945778900
+#: ../../source/about.rst:630
+msgid ""
+"Deleting Load Balancing Rule fails when generating usage events are "
+"enabled..."
+msgstr ""
+
+# 94ff72e916b6406ba3fdccc90b74a998
+#: ../../source/about.rst:631
+msgid ""
+"`CLOUDSTACK-5054 <https://issues.apache.org/jira/browse/CLOUDSTACK-5054>`_"
+msgstr ""
+
+# 5469eeb03bd24ea7be6dddeb7941ce70
+#: ../../source/about.rst:631
+msgid ""
+"vm migration involving storage migration on vmware fails with exception \" "
+"The ob..."
+msgstr ""
+
+# 31e5de517da3422fad6f9d176db1405e
+#: ../../source/about.rst:632
+msgid ""
+"`CLOUDSTACK-5053 <https://issues.apache.org/jira/browse/CLOUDSTACK-5053>`_"
+msgstr ""
+
+# f4ead44a795e4f63b93568a1ef2dbe23
+#: ../../source/about.rst:632
+msgid ""
+"No Qemu-KVM module dependency error message is displayed (if not "
+"present)while i..."
+msgstr ""
+
+# f194e896bf65498f9e770ceea800eb47
+#: ../../source/about.rst:633
+msgid ""
+"`CLOUDSTACK-5042 <https://issues.apache.org/jira/browse/CLOUDSTACK-5042>`_"
+msgstr ""
+
+# b3db8dde60ec4d43a23cb3193b83671d
+#: ../../source/about.rst:633
+msgid "(Upgrade) Exception when stop VM after upgrade..."
+msgstr ""
+
+# e320d3d15e8742b281b9430647682a46
+#: ../../source/about.rst:634
+msgid ""
+"`CLOUDSTACK-5029 <https://issues.apache.org/jira/browse/CLOUDSTACK-5029>`_"
+msgstr ""
+
+# 9b78735e219647ecb6e4121874923ba0
+#: ../../source/about.rst:634
+msgid "cloud-bugtool isn't in release package like release notes say..."
+msgstr ""
+
+# f73a527a09a641e0a89bcb5dd5df6a70
+#: ../../source/about.rst:635
+msgid ""
+"`CLOUDSTACK-5025 <https://issues.apache.org/jira/browse/CLOUDSTACK-5025>`_"
+msgstr ""
+
+# 4f35f586f1014ead82ae5ece2c6160d4
+#: ../../source/about.rst:635
+msgid "display_volume field is set to false by default for VolumeVO object..."
+msgstr ""
+
+# bd6bad68bd8644068e464b0ca9940501
+#: ../../source/about.rst:636
+msgid ""
+"`CLOUDSTACK-5024 <https://issues.apache.org/jira/browse/CLOUDSTACK-5024>`_"
+msgstr ""
+
+# 743628c9d47b446899bc219665414d48
+#: ../../source/about.rst:636
+msgid "listVolumes: add support to list by storage pool (for admin only)..."
+msgstr ""
+
+# 1c6cd0cd3bd34f75b304f705189eee5b
+#: ../../source/about.rst:637
+msgid ""
+"`CLOUDSTACK-5017 <https://issues.apache.org/jira/browse/CLOUDSTACK-5017>`_"
+msgstr ""
+
+# 21e6d0344e384e93af60eedc1c95d025
+#: ../../source/about.rst:637
+msgid ""
+"If SSVM is unavailable DownloadCommands will be routed to mgmt server..."
+msgstr ""
+
+# 106e4d150fca46548a921121b8552ebf
+#: ../../source/about.rst:638
+msgid ""
+"`CLOUDSTACK-5014 <https://issues.apache.org/jira/browse/CLOUDSTACK-5014>`_"
+msgstr ""
+
+# c1c06cbc7b7c45c8af3faf073aa4c991
+#: ../../source/about.rst:638
+msgid "vmware:deployVM with data disk failed with exception..."
+msgstr ""
+
+# e7d63ff16c2046458443bc10404cdf5c
+#: ../../source/about.rst:639
+msgid ""
+"`CLOUDSTACK-5012 <https://issues.apache.org/jira/browse/CLOUDSTACK-5012>`_"
+msgstr ""
+
+# d873cf938a3c4588b1ad22cb38d966e6
+#: ../../source/about.rst:639
+msgid ""
+"Bad data inserted into physical network labels for Zone Create Wizard using "
+"VMWa..."
+msgstr ""
+
+# 44f0b675b80844d78bd1b0cf4c2602f1
+#: ../../source/about.rst:640
+msgid ""
+"`CLOUDSTACK-5008 <https://issues.apache.org/jira/browse/CLOUDSTACK-5008>`_"
+msgstr ""
+
+# 520d0a23384c43ad9ba8b114ba00bec0
+#: ../../source/about.rst:640
+msgid ""
+"[VMWARE]Failed to start the VM after performing Cold Migration of Volume to "
+"Seco..."
+msgstr ""
+
+# 0dc8152d6730441486a5927b0a420f45
+#: ../../source/about.rst:641
+msgid ""
+"`CLOUDSTACK-5002 <https://issues.apache.org/jira/browse/CLOUDSTACK-5002>`_"
+msgstr ""
+
+# 053453e3b3504bbfaedf20c4bb0e2ffa
+#: ../../source/about.rst:641
+msgid ""
+"unable to destroy vm ;VM destroy failed in Stop i-2-59-VM Command due to You"
+" gav..."
+msgstr ""
+
+# 0c1534937df04783863c12c8ea9fd5af
+#: ../../source/about.rst:642
+msgid ""
+"`CLOUDSTACK-4998 <https://issues.apache.org/jira/browse/CLOUDSTACK-4998>`_"
+msgstr ""
+
+# 44ca48de62084240bf964891f8d91084
+#: ../../source/about.rst:642
+msgid ""
+"assignVirtualMachine API has wrong response string, causing Cloudmonkey to "
+"crash..."
+msgstr ""
+
+# b165202bd702464f9c0062410600b217
+#: ../../source/about.rst:643
+msgid ""
+"`CLOUDSTACK-4997 <https://issues.apache.org/jira/browse/CLOUDSTACK-4997>`_"
+msgstr ""
+
+# 751efa544bfe4144a946b354e8d1b7fc
+#: ../../source/about.rst:643
+msgid "OVS integration is broken..."
+msgstr ""
+
+# 3365f820f0154735848cc957377d28db
+#: ../../source/about.rst:644
+msgid ""
+"`CLOUDSTACK-4973 <https://issues.apache.org/jira/browse/CLOUDSTACK-4973>`_"
+msgstr ""
+
+# 43b720ee34574961ba2a783388b3ee85
+#: ../../source/about.rst:644
+msgid ""
+"CLONE - Specified keyboard language is not showing as default in consoleView"
+" pas..."
+msgstr ""
+
+# 76841734ecc640bb96fd7680b1563078
+#: ../../source/about.rst:645
+msgid ""
+"`CLOUDSTACK-4943 <https://issues.apache.org/jira/browse/CLOUDSTACK-4943>`_"
+msgstr ""
+
+# 9ca6bd3e17964e12866d455d9ebebf14
+#: ../../source/about.rst:645
+msgid "Can't create cluster in CS 4.2..."
+msgstr ""
+
+# bd705a1009d94e85bc3bbc92e3571883
+#: ../../source/about.rst:646
+msgid ""
+"`CLOUDSTACK-4941 <https://issues.apache.org/jira/browse/CLOUDSTACK-4941>`_"
+msgstr ""
+
+# f219f7b41bef495783c016384eba1f70
+#: ../../source/about.rst:646
+msgid "CLONE - Allocation capacity of a cluster during HA..."
+msgstr ""
+
+# 0bf7140f09e34bf39cdf16a8dba7e8aa
+#: ../../source/about.rst:647
+msgid ""
+"`CLOUDSTACK-4935 <https://issues.apache.org/jira/browse/CLOUDSTACK-4935>`_"
+msgstr ""
+
+# b54751f9c5f346159ded2322cd083c12
+#: ../../source/about.rst:647
+msgid ""
+"Adding same network to VM multiple times resulting in failure, No new NIC is"
+" gen..."
+msgstr ""
+
+# 288ede58b88f4a44a62e84d0564ef548
+#: ../../source/about.rst:648
+msgid ""
+"`CLOUDSTACK-4931 <https://issues.apache.org/jira/browse/CLOUDSTACK-4931>`_"
+msgstr ""
+
+# 9cd3def4e5c4459bb8b037ce49201bbe
+#: ../../source/about.rst:648
+msgid "observed NPE with new system vm template..."
+msgstr ""
+
+# 40df03649369499a82facb5b80d76d15
+#: ../../source/about.rst:649
+msgid ""
+"`CLOUDSTACK-4913 <https://issues.apache.org/jira/browse/CLOUDSTACK-4913>`_"
+msgstr ""
+
+# 50063d38e7044b28bc202bcad30ef60d
+#: ../../source/about.rst:649
+msgid "Disable security group for bridge mode non-security group zone..."
+msgstr ""
+
+# 4d60c977aee442c0828040726b5b5cb9
+#: ../../source/about.rst:650
+msgid ""
+"`CLOUDSTACK-4904 <https://issues.apache.org/jira/browse/CLOUDSTACK-4904>`_"
+msgstr ""
+
+# f2c08b23f8514bb4a654e0e131c7bfdb
+#: ../../source/about.rst:650
+msgid "Unable to see a derieved template if the parent template is deleted..."
+msgstr ""
+
+# 94fe5dbb1fbf486f967848000ef334e3
+#: ../../source/about.rst:651
+msgid ""
+"`CLOUDSTACK-4886 <https://issues.apache.org/jira/browse/CLOUDSTACK-4886>`_"
+msgstr ""
+
+# 48e094d65c2d4db8bc0b1af394b47e9b
+#: ../../source/about.rst:651
+msgid "cloud-setup-databases not escaping password in shell commands..."
+msgstr ""
+
+# a7bd797ba5374738bd101205b9520bba
+#: ../../source/about.rst:652
+msgid ""
+"`CLOUDSTACK-4875 <https://issues.apache.org/jira/browse/CLOUDSTACK-4875>`_"
+msgstr ""
+
+# efbb305d0d4244bb8e8270e48c238675
+#: ../../source/about.rst:652
+msgid "VMWARE: vCenter 5.5 - SYSTEM VM: Unable to create deployment for VM..."
+msgstr ""
+
+# 3db2f47d361945629fc4133855dbe711
+#: ../../source/about.rst:653
+msgid ""
+"`CLOUDSTACK-4861 <https://issues.apache.org/jira/browse/CLOUDSTACK-4861>`_"
+msgstr ""
+
+# a1dca318726a483790923516842f006f
+#: ../../source/about.rst:653
+msgid ""
+"[VMware] If Guest traffic spans across multiple physical networks, selection"
+" of ..."
+msgstr ""
+
+# f07f072323bc4da1a3998c97b752446f
+#: ../../source/about.rst:654
+msgid ""
+"`CLOUDSTACK-4860 <https://issues.apache.org/jira/browse/CLOUDSTACK-4860>`_"
+msgstr ""
+
+# 3331a070c17641b9baa8eba24f39e027
+#: ../../source/about.rst:654
+msgid ""
+"[VMware] Vcenter 5.5 ESXi 5.5 hosts SSVM CPVM fail to come up to running "
+"state..."
+msgstr ""
+
+# b1a22187b1a34e2f9f7c3ed20f9549cd
+#: ../../source/about.rst:655
+msgid ""
+"`CLOUDSTACK-4856 <https://issues.apache.org/jira/browse/CLOUDSTACK-4856>`_"
+msgstr ""
+
+# 0d860e5e5465443ab5cbc279941f4799
+#: ../../source/about.rst:655
+msgid "Optimize on the # of control commands sent by MS to HV host..."
+msgstr ""
+
+# 1986f7ca366147eea5655d40ecc3b04b
+#: ../../source/about.rst:656
+msgid ""
+"`CLOUDSTACK-4855 <https://issues.apache.org/jira/browse/CLOUDSTACK-4855>`_"
+msgstr ""
+
+# d8b6b377887a49078a87d4934cb0c5b2
+#: ../../source/about.rst:656
+msgid ""
+"Throttle based on the # of outstanding requests to the directly managed HV "
+"host ..."
+msgstr ""
+
+# ace6d729c9a347039689dbfb671a7db2
+#: ../../source/about.rst:657
+msgid ""
+"`CLOUDSTACK-4852 <https://issues.apache.org/jira/browse/CLOUDSTACK-4852>`_"
+msgstr ""
+
+# a7c7f58008064196b9ef81802d190912
+#: ../../source/about.rst:657
+msgid ""
+"Since upgrade to 4.2 only users at the zone-attached domain level can "
+"manipulate..."
+msgstr ""
+
+# 3ef2e904b3724f25946444b875b33ca8
+#: ../../source/about.rst:658
+msgid ""
+"`CLOUDSTACK-4850 <https://issues.apache.org/jira/browse/CLOUDSTACK-4850>`_"
+msgstr ""
+
+# 396d89f57f094a9eb05780f82aca46c2
+#: ../../source/about.rst:658
+msgid "[UCS] using template instead of cloning profile..."
+msgstr ""
+
+# 97e99c8db0ab47518e8244339fc79ea2
+#: ../../source/about.rst:659
+msgid ""
+"`CLOUDSTACK-4831 <https://issues.apache.org/jira/browse/CLOUDSTACK-4831>`_"
+msgstr ""
+
+# e8705ef095a743af8d34cee3c08c9d4b
+#: ../../source/about.rst:659
+msgid ""
+"Ability for root admin or domain admin to create a network for another user "
+"unde..."
+msgstr ""
+
+# 0a8853feef814405ab4fdeababe07f8f
+#: ../../source/about.rst:660
+msgid ""
+"`CLOUDSTACK-4830 <https://issues.apache.org/jira/browse/CLOUDSTACK-4830>`_"
+msgstr ""
+
+# 7686478ec62442f4954e65c222a76857
+#: ../../source/about.rst:660
+msgid "Allow creation of users and accounts by domain admin in UI..."
+msgstr ""
+
+# 89ec38d9ea2f4efaa90577169d767f25
+#: ../../source/about.rst:661
+msgid ""
+"`CLOUDSTACK-4826 <https://issues.apache.org/jira/browse/CLOUDSTACK-4826>`_"
+msgstr ""
+
+# 5a6f5d6b27b143caab84daa377d5f3b3
+#: ../../source/about.rst:661
+msgid "System VMs fail to start..."
+msgstr ""
+
+# a1ca9f02ab344945ba6826cad7b62387
+#: ../../source/about.rst:662
+msgid ""
+"`CLOUDSTACK-4820 <https://issues.apache.org/jira/browse/CLOUDSTACK-4820>`_"
+msgstr ""
+
+# 42b23f5cd1ff4f2fb82095c17098de86
+#: ../../source/about.rst:662
+msgid "TestVPCNetworkGc.test_01_wait_network_gc netacls are not cleared..."
+msgstr ""
+
+# 1f715d85fe7d4a3993ce6c2ac3103db7
+#: ../../source/about.rst:663
+msgid ""
+"`CLOUDSTACK-4810 <https://issues.apache.org/jira/browse/CLOUDSTACK-4810>`_"
+msgstr ""
+
+# 3020a6c5bcf247dca12e7bc04bd35fac
+#: ../../source/about.rst:663
+msgid ""
+"Enable hypervisor snapshots for CloudStack-managed storage (for XenServer "
+"and VM..."
+msgstr ""
+
+# c19348ffa02841ff9aaf5826c143e3c4
+#: ../../source/about.rst:664
+msgid ""
+"`CLOUDSTACK-4768 <https://issues.apache.org/jira/browse/CLOUDSTACK-4768>`_"
+msgstr ""
+
+# 985b19a402434e738b68be045aa7735f
+#: ../../source/about.rst:664
+msgid ""
+"[Automation] Race condition; delete the template and create VM at same time;"
+" dep..."
+msgstr ""
+
+# 7da707f12aae4f58a0a9bfd20d56c022
+#: ../../source/about.rst:665
+msgid ""
+"`CLOUDSTACK-4750 <https://issues.apache.org/jira/browse/CLOUDSTACK-4750>`_"
+msgstr ""
+
+# f86c4137fc674be28ec489ceacde4c6b
+#: ../../source/about.rst:665
+msgid ""
+"bond.VLAN mapping in iptables FORWARD chain not created consistently..."
+msgstr ""
+
+# 0eac77f58b024384b9b2323da9b461ef
+#: ../../source/about.rst:666
+msgid ""
+"`CLOUDSTACK-4741 <https://issues.apache.org/jira/browse/CLOUDSTACK-4741>`_"
+msgstr ""
+
+# cd3a4178a7aa4f34a1fc5f9efd23430b
+#: ../../source/about.rst:666
+msgid "URL of ImageStore not in proper format for XenServer..."
+msgstr ""
+
+# 32f7a75fd1684a58834d560355aee533
+#: ../../source/about.rst:667
+msgid ""
+"`CLOUDSTACK-4740 <https://issues.apache.org/jira/browse/CLOUDSTACK-4740>`_"
+msgstr ""
+
+# e173fab183e54f7f8d0946f1d5a364dc
+#: ../../source/about.rst:667
+msgid "Some vSphere VMs are shutdown when ACS is restarted..."
+msgstr ""
+
+# 11e7e9a029b14a1d90e21afa855d50b7
+#: ../../source/about.rst:668
+msgid ""
+"`CLOUDSTACK-4734 <https://issues.apache.org/jira/browse/CLOUDSTACK-4734>`_"
+msgstr ""
+
+# 928bafc602cc4e249b5c35ecde4de613
+#: ../../source/about.rst:668
+msgid ""
+"Creating snapshot from ROOT volume fails with error message - \"Failed to "
+"create ..."
+msgstr ""
+
+# 7890167612e34986a8e34f16d16c3606
+#: ../../source/about.rst:669
+msgid ""
+"`CLOUDSTACK-4724 <https://issues.apache.org/jira/browse/CLOUDSTACK-4724>`_"
+msgstr ""
+
+# cf6deee2da574a29bc246387eb220994
+#: ../../source/about.rst:669
+msgid ""
+"[Vmware] Deploy VM in designated cluster fail if there is only zone wide "
+"primary..."
+msgstr ""
+
+# 0af44808879744438424b87023a63d52
+#: ../../source/about.rst:670
+msgid ""
+"`CLOUDSTACK-4697 <https://issues.apache.org/jira/browse/CLOUDSTACK-4697>`_"
+msgstr ""
+
+# 73c11d2899994de499f0400ef1f79ba4
+#: ../../source/about.rst:670
+msgid ""
+"Not able to delete Primary storage when there are no hosts in the "
+"cluster...."
+msgstr ""
+
+# 145d8ef8f20643519e9b5f9630fc9ef5
+#: ../../source/about.rst:671
+msgid ""
+"`CLOUDSTACK-4676 <https://issues.apache.org/jira/browse/CLOUDSTACK-4676>`_"
+msgstr ""
+
+# 03a27d5dbde94757992a9d62174efe57
+#: ../../source/about.rst:671
+msgid ""
+"[Baremetal] baremetal hostename should not be fixed in kickstart file ..."
+msgstr ""
+
+# 0f7ecdc731b84b5ca9dfea4f744bd6b3
+#: ../../source/about.rst:672
+msgid ""
+"`CLOUDSTACK-4670 <https://issues.apache.org/jira/browse/CLOUDSTACK-4670>`_"
+msgstr ""
+
+# cde3cf5c56a44c6aae3cf4a14dc8429b
+#: ../../source/about.rst:672
+msgid "[Baremetal] Cloudplatform BareMetal installation guide for CP 4.2..."
+msgstr ""
+
+# 667abdf5e91e4ec694f358065cb7280c
+#: ../../source/about.rst:673
+msgid ""
+"`CLOUDSTACK-4631 <https://issues.apache.org/jira/browse/CLOUDSTACK-4631>`_"
+msgstr ""
+
+# b5f413db87f640449e1903245c3857c4
+#: ../../source/about.rst:673
+msgid ""
+"[Automation] Failed to create snapshot from volume due to storage pool "
+"missing e..."
+msgstr ""
+
+# 4697ac3b30f046fdba4ce9d4272aa9f7
+#: ../../source/about.rst:674
+msgid ""
+"`CLOUDSTACK-4620 <https://issues.apache.org/jira/browse/CLOUDSTACK-4620>`_"
+msgstr ""
+
+# 62fd40c677994ea1b9ea6d365ceae37c
+#: ../../source/about.rst:674
+msgid ""
+"Vm failed to start on the host on which it was running due to not having "
+"enough ..."
+msgstr ""
+
+# 4fd407a308b943a3ba4af67369a57a50
+#: ../../source/about.rst:675
+msgid ""
+"`CLOUDSTACK-4616 <https://issues.apache.org/jira/browse/CLOUDSTACK-4616>`_"
+msgstr ""
+
+# c92db2b2b0094f998358a3f938959952
+#: ../../source/about.rst:675
+msgid ""
+"When system Vms fail to start when host is down , link local Ip addresses "
+"do no..."
+msgstr ""
+
+# 3334341e3f95462cb70d4fcbb799008c
+#: ../../source/about.rst:676
+msgid ""
+"`CLOUDSTACK-4598 <https://issues.apache.org/jira/browse/CLOUDSTACK-4598>`_"
+msgstr ""
+
+# c16926ef451a4382bd6ea85b24a251bf
+#: ../../source/about.rst:676
+msgid ""
+"[Performance Testing] High delays during deployVM - both network delay and "
+"deplo..."
+msgstr ""
+
+# 5cf4f9326a044b60a18beba4c8c91602
+#: ../../source/about.rst:677
+msgid ""
+"`CLOUDSTACK-4597 <https://issues.apache.org/jira/browse/CLOUDSTACK-4597>`_"
+msgstr ""
+
+# f0754bc0e8024924a616f859fdd59b45
+#: ../../source/about.rst:677
+msgid ""
+"Complete Exceptions are getting displayed in the UI where there is an "
+"operationa..."
+msgstr ""
+
+# 453666aace0245fb83d2fdabde741f64
+#: ../../source/about.rst:678
+msgid ""
+"`CLOUDSTACK-4594 <https://issues.apache.org/jira/browse/CLOUDSTACK-4594>`_"
+msgstr ""
+
+# 9bd53a36b8d94a91a1509bf32ff3e25b
+#: ../../source/about.rst:678
+msgid ""
+"[VMWARE] [Upgrade] Failed to revert VM Snapshot which were created before "
+"Live S..."
+msgstr ""
+
+# 37d2c89b7b294dfdac3a085d20b1e243
+#: ../../source/about.rst:679
+msgid ""
+"`CLOUDSTACK-4588 <https://issues.apache.org/jira/browse/CLOUDSTACK-4588>`_"
+msgstr ""
+
+# 4695e57fb34641619f4965dc2afbeb35
+#: ../../source/about.rst:679
+msgid ""
+"[Automation][Vmware] VM deployment failed while creating Volume with NPE..."
+msgstr ""
+
+# 157a709278454369926e2f89e06b5c06
+#: ../../source/about.rst:680
+msgid ""
+"`CLOUDSTACK-4577 <https://issues.apache.org/jira/browse/CLOUDSTACK-4577>`_"
+msgstr ""
+
+# 69ccd745c5034e23badd4c4ba0529666
+#: ../../source/about.rst:680
+msgid ""
+"VMWare:Volumes: Unexpected exception while executing "
+"org.apache.cloudstack.api.c..."
+msgstr ""
+
+# 88d9b768bf67453ca27bf4674329f967
+#: ../../source/about.rst:681
+msgid ""
+"`CLOUDSTACK-4543 <https://issues.apache.org/jira/browse/CLOUDSTACK-4543>`_"
+msgstr ""
+
+# 3b12eb6e07a14ba4b437559435b4dad3
+#: ../../source/about.rst:681
+msgid ""
+"[Automation] Failed to configure VPC router then reported as deployment "
+"failure..."
+msgstr ""
+
+# 039b646e54644a698b30d4784869c907
+#: ../../source/about.rst:682
+msgid ""
+"`CLOUDSTACK-4542 <https://issues.apache.org/jira/browse/CLOUDSTACK-4542>`_"
+msgstr ""
+
+# 5472eb10e3c04f25aac3e83c3b833098
+#: ../../source/about.rst:682
+msgid ""
+"[Automation] Failed to apply DHCP entry in VR and deployment failed ..."
+msgstr ""
+
+# 56636f214ab94b2b9364cceee5564aa8
+#: ../../source/about.rst:683
+msgid ""
+"`CLOUDSTACK-4540 <https://issues.apache.org/jira/browse/CLOUDSTACK-4540>`_"
+msgstr ""
+
+# 1b92aed958b74d3e8a344c3837210a94
+#: ../../source/about.rst:683
+msgid ""
+"[Automation] Parallel deployment - Vmware - When deploying 30 parallel Vms ,"
+" 16 ..."
+msgstr ""
+
+# c534c6651c3a4b67a36ddd1d12b53f5a
+#: ../../source/about.rst:684
+msgid ""
+"`CLOUDSTACK-4506 <https://issues.apache.org/jira/browse/CLOUDSTACK-4506>`_"
+msgstr ""
+
+# 32a72acd3c9e4ca18bd5e21fc5d4d498
+#: ../../source/about.rst:684
+msgid ""
+"In a mixed hypervisor setup, destroying a VM whose host has been removed, "
+"throws..."
+msgstr ""
+
+# 2574475ed4894b169cc616c9757df7e1
+#: ../../source/about.rst:685
+msgid ""
+"`CLOUDSTACK-4504 <https://issues.apache.org/jira/browse/CLOUDSTACK-4504>`_"
+msgstr ""
+
+# 17ac9f41f94a4787a88e46048541f978
+#: ../../source/about.rst:685
+msgid "VM creation Is failing using the Ubuntu ISO with Xen 6.1 and 6.2..."
+msgstr ""
+
+# 071f6e25a6c24726a4501ec4d4fbdca8
+#: ../../source/about.rst:686
+msgid ""
+"`CLOUDSTACK-4450 <https://issues.apache.org/jira/browse/CLOUDSTACK-4450>`_"
+msgstr ""
+
+# 67f3965b26c540a5aaf5b473ad14bf55
+#: ../../source/about.rst:686
+msgid "Possibility of /tmp/xapilog filling up the Root disk on Xenserver ..."
+msgstr ""
+
+# 1e5e0138da8e4740aad1606105615d30
+#: ../../source/about.rst:687
+msgid ""
+"`CLOUDSTACK-4445 <https://issues.apache.org/jira/browse/CLOUDSTACK-4445>`_"
+msgstr ""
+
+# d40e66393a4e472e845030576d929b82
+#: ../../source/about.rst:687
+msgid ""
+"[UI]Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter "
+"with ..."
+msgstr ""
+
+# 049082d03a484ee89ed5a8e31c70ee8d
+#: ../../source/about.rst:688
+msgid ""
+"`CLOUDSTACK-4428 <https://issues.apache.org/jira/browse/CLOUDSTACK-4428>`_"
+msgstr ""
+
+# 5e95e0dafbc641159675b77a29255830
+#: ../../source/about.rst:688
+msgid ""
+"[UI] \"kvm.snapshot.enabled\" flag should be taken to account only when "
+"snapshot i..."
+msgstr ""
+
+# db4b5894acab4aeaae4abc6cf7ec2c8f
+#: ../../source/about.rst:689
+msgid ""
+"`CLOUDSTACK-4402 <https://issues.apache.org/jira/browse/CLOUDSTACK-4402>`_"
+msgstr ""
+
+# cff757b824084cdbb5d13ef7d93660b0
+#: ../../source/about.rst:689
+msgid ""
+"[deleteStoragePool] There is no way to delete Primary storage if the last "
+"host w..."
+msgstr ""
+
+# 358bc13d832d4f5e9efa9bcf1b029e90
+#: ../../source/about.rst:690
+msgid ""
+"`CLOUDSTACK-4371 <https://issues.apache.org/jira/browse/CLOUDSTACK-4371>`_"
+msgstr ""
+
+# bb406cad9cad4129bd7290537cbf34e9
+#: ../../source/about.rst:690
+msgid ""
+"[Performance Testing] Basic zone with 20K Hosts, management server restart "
+"leave..."
+msgstr ""
+
+# 8496515c969c4f51a90d03791bde0dd6
+#: ../../source/about.rst:691
+msgid ""
+"`CLOUDSTACK-4263 <https://issues.apache.org/jira/browse/CLOUDSTACK-4263>`_"
+msgstr ""
+
+# 3a6d44ecf59d4ddb8ccdeaf1e4c53aaf
+#: ../../source/about.rst:691
+msgid ""
+"Unable to get git number in maven-jgit-buildnumber-plugin, while build "
+"cloudstac..."
+msgstr ""
+
+# f1b45e7268e44b1c87ad2ee9bcedb6d8
+#: ../../source/about.rst:692
+msgid ""
+"`CLOUDSTACK-4207 <https://issues.apache.org/jira/browse/CLOUDSTACK-4207>`_"
+msgstr ""
+
+# 77c10218109d4e149359c2e0b3567172
+#: ../../source/about.rst:692
+msgid ""
+"[upgrade] Exception observed after upgrade \"jsonParseException: The "
+"JsonDeserial..."
+msgstr ""
+
+# cd44625942934af58f400507be510739
+#: ../../source/about.rst:693
+msgid ""
+"`CLOUDSTACK-4061 <https://issues.apache.org/jira/browse/CLOUDSTACK-4061>`_"
+msgstr ""
+
+# 357916ee164e428294530f5987c8a187
+#: ../../source/about.rst:693
+msgid "UI issue with Japanese localized ui..."
+msgstr ""
+
+# 22bbd529bca24b96bd07ffa0f9b8c787
+#: ../../source/about.rst:694
+msgid ""
+"`CLOUDSTACK-3806 <https://issues.apache.org/jira/browse/CLOUDSTACK-3806>`_"
+msgstr ""
+
+# 369f0e717ad34af7abf2ab4e56f5ddfa
+#: ../../source/about.rst:694
+msgid "OS Preference can not be set..."
+msgstr ""
+
+# 7d083ac7ff4649d48dc85c2b918c2ea5
+#: ../../source/about.rst:695
+msgid ""
+"`CLOUDSTACK-3664 <https://issues.apache.org/jira/browse/CLOUDSTACK-3664>`_"
+msgstr ""
+
+# 1742af2678b74066a7a7fb5fd44a40c1
+#: ../../source/about.rst:695
+msgid ""
+"scaling up vms is not considering parameter "
+"\"cluster.(memory/cpu).allocated.cap..."
+msgstr ""
+
+# bbc5466710ca4998b4ae768b26f7ba45
+#: ../../source/about.rst:696
+msgid ""
+"`CLOUDSTACK-3627 <https://issues.apache.org/jira/browse/CLOUDSTACK-3627>`_"
+msgstr ""
+
+# cf1d52b8df914a52b25911c0b30c04ec
+#: ../../source/about.rst:696
+msgid ""
+"Public IP interface(eth2) is not getting confugured with Redundant VR (State"
+" = F..."
+msgstr ""
+
+# 1a30502e895d418f87d3de62eaecbe9c
+#: ../../source/about.rst:697
+msgid ""
+"`CLOUDSTACK-3577 <https://issues.apache.org/jira/browse/CLOUDSTACK-3577>`_"
+msgstr ""
+
+# e409cf02dfa94762afdd935586293d34
+#: ../../source/about.rst:697
+msgid "NPE while downloading the template to secondary storage ..."
+msgstr ""
+
+# e88aaa831b5040e9b3fdc9638df27812
+#: ../../source/about.rst:698
+msgid ""
+"`CLOUDSTACK-3561 <https://issues.apache.org/jira/browse/CLOUDSTACK-3561>`_"
+msgstr ""
+
+# c5143675c68841e3a9728daed8909738
+#: ../../source/about.rst:698
+msgid ""
+"When inputting the nfs server in secondary storage, if once it's required, "
+"it al..."
+msgstr ""
+
+# b1b2aeef4f8242299a4f6a3a4ea96e78
+#: ../../source/about.rst:699
+msgid ""
+"`CLOUDSTACK-3364 <https://issues.apache.org/jira/browse/CLOUDSTACK-3364>`_"
+msgstr ""
+
+# 4ad750e7dbb047b8b07ed0dcd818bf1c
+#: ../../source/about.rst:699
+msgid "normal users are not allowed to edit their own iso..."
+msgstr ""
+
+# c83f08aa21e445a2a809095652291596
+#: ../../source/about.rst:700
+msgid ""
+"`CLOUDSTACK-3266 <https://issues.apache.org/jira/browse/CLOUDSTACK-3266>`_"
+msgstr ""
+
+# 5d607746c3044e5898a739e273c53dbf
+#: ../../source/about.rst:700
+msgid "[UI] Failed to delete Anti affinitygroup for the first time ..."
+msgstr ""
+
+# 6c5fb4e3cb8d41efabd53ea9d4875113
+#: ../../source/about.rst:701
+msgid ""
+"`CLOUDSTACK-3252 <https://issues.apache.org/jira/browse/CLOUDSTACK-3252>`_"
+msgstr ""
+
+# 7e7fbee9c3bf454aa1035e4a5cbd6069
+#: ../../source/about.rst:701
+msgid ""
+"An instance deployed using explicit or implicit dedication doesn't generate "
+"a us..."
+msgstr ""
+
+# cd30639f36b143979e1c9e621d907e93
+#: ../../source/about.rst:702
+msgid ""
+"`CLOUDSTACK-3247 <https://issues.apache.org/jira/browse/CLOUDSTACK-3247>`_"
+msgstr ""
+
+# 54ea50df69504905a0de6b0d8e1fbb04
+#: ../../source/about.rst:702
+msgid "Removing a Disconnected Host throws a NoTransitionException..."
+msgstr ""
+
+# a92ec174b7e04766888f105eeac567e4
+#: ../../source/about.rst:703
+msgid ""
+"`CLOUDSTACK-3156 <https://issues.apache.org/jira/browse/CLOUDSTACK-3156>`_"
+msgstr ""
+
+# 5ee8331a5eac4e2da77a48f437946769
+#: ../../source/about.rst:703
+msgid ""
+"needs proper message for failing Add nic command when vmware tools is not "
+"instal..."
+msgstr ""
+
+# 25ca28a795fc4b8c96b23838bbfa1c4c
+#: ../../source/about.rst:704
+msgid ""
+"`CLOUDSTACK-3067 <https://issues.apache.org/jira/browse/CLOUDSTACK-3067>`_"
+msgstr ""
+
+# 3936325267264d2c8fcad752f36a5d52
+#: ../../source/about.rst:704
+msgid ""
+"UI for Dedicating POD/Cluster/Host is misleading Icons should be changed...."
+msgstr ""
+
+# 0467a816c7bf4cae98e8592cc05fb416
+#: ../../source/about.rst:705
+msgid ""
+"`CLOUDSTACK-3027 <https://issues.apache.org/jira/browse/CLOUDSTACK-3027>`_"
+msgstr ""
+
+# db28767273df46f5a44fd6a3e3cafbe1
+#: ../../source/about.rst:705
+msgid ""
+"Object_Store_Refactor - Uploaded template S3 content-type is not "
+"appropriate...."
+msgstr ""
+
+# d33375b70acd478e94cd8a2de29e1823
+#: ../../source/about.rst:706
+msgid ""
+"`CLOUDSTACK-2895 <https://issues.apache.org/jira/browse/CLOUDSTACK-2895>`_"
+msgstr ""
+
+# b467c19429b64bfb968265590c68fec4
+#: ../../source/about.rst:706
+msgid "Can't start a VM with 3 volumes attached [VMWare]..."
+msgstr ""
+
+# 458fbbd7b8d74e15b3a60d5bc4c68294
+#: ../../source/about.rst:707
+msgid ""
+"`CLOUDSTACK-2766 <https://issues.apache.org/jira/browse/CLOUDSTACK-2766>`_"
+msgstr ""
+
+# 1d13f52a0b524f0fb7bccf62a88bb6ac
+#: ../../source/about.rst:707
+msgid ""
+"[VPC] [UI] Firewall service should not be enabled for acquired public IPs in"
+" VPC..."
+msgstr ""
+
+# 67dc347e005942029fa6e4a3f0f53cfc
+#: ../../source/about.rst:708
+msgid ""
+"`CLOUDSTACK-2687 <https://issues.apache.org/jira/browse/CLOUDSTACK-2687>`_"
+msgstr ""
+
+# 659cd98957394947a9b9d1a0d50b9cb5
+#: ../../source/about.rst:708
+msgid "NPE with deploy VM when there are no resources available ..."
+msgstr ""
+
+# 7c071cb5d5c3491194406655ce442ee4
+#: ../../source/about.rst:709
+msgid ""
+"`CLOUDSTACK-2570 <https://issues.apache.org/jira/browse/CLOUDSTACK-2570>`_"
+msgstr ""
+
+# c618bcf561424423b3e8ed9513991856
+#: ../../source/about.rst:709
+msgid "[UI]Resource Name is mentioned twice with view VNMC devices ..."
+msgstr ""
+
+# bc176885c1f44074a7f06cc967923073
+#: ../../source/about.rst:710
+msgid ""
+"`CLOUDSTACK-2562 <https://issues.apache.org/jira/browse/CLOUDSTACK-2562>`_"
+msgstr ""
+
+# 77896d6ccbae452a8ea30d2b88e2854f
+#: ../../source/about.rst:710
+msgid ""
+"[VMWARE] As per the code, currently CloudStack fails to program PF/NAT/LB "
+"rules ..."
+msgstr ""
+
+# c64206bc17404ddb85d30956a73a9851
+#: ../../source/about.rst:711
+msgid ""
+"`CLOUDSTACK-2428 <https://issues.apache.org/jira/browse/CLOUDSTACK-2428>`_"
+msgstr ""
+
+# 15c21a5396e7428b928fd0ad2dec879a
+#: ../../source/about.rst:711
+msgid ""
+"HA - When the master host is disconnected , the host status contines to "
+"remain i..."
+msgstr ""
+
+# c1e0bb3d6cd14f7cad809f89124ec29f
+#: ../../source/about.rst:712
+msgid ""
+"`CLOUDSTACK-2414 <https://issues.apache.org/jira/browse/CLOUDSTACK-2414>`_"
+msgstr ""
+
+# 2462b5477c724f3ab1860d4b0d648bf9
+#: ../../source/about.rst:712
+msgid "NPE while deleting Cisco VNMC provider..."
+msgstr ""
+
+# bbcc4c4c254649548a9b7017ffd5f54b
+#: ../../source/about.rst:713
+msgid ""
+"`CLOUDSTACK-2396 <https://issues.apache.org/jira/browse/CLOUDSTACK-2396>`_"
+msgstr ""
+
+# ab8b5846107641e6bd4794c71072af44
+#: ../../source/about.rst:713
+msgid ""
+"PVLAN - Should not be allowed to create multiple networks with same Vlan "
+"associ..."
+msgstr ""
+
+# c26425b5adf5400b982c3b0f11222b65
+#: ../../source/about.rst:714
+msgid ""
+"`CLOUDSTACK-2199 <https://issues.apache.org/jira/browse/CLOUDSTACK-2199>`_"
+msgstr ""
+
+# 0e2dcf9c5d19426e91f38d78a01f6134
+#: ../../source/about.rst:714
+msgid ""
+"ID parameter of UpdateConfiguration API should be changed to a different "
+"name..."
+msgstr ""
+
+# 7da963c6455a4725be0a34b50f6af338
+#: ../../source/about.rst:715
+msgid ""
+"`CLOUDSTACK-2141 <https://issues.apache.org/jira/browse/CLOUDSTACK-2141>`_"
+msgstr ""
+
+# af2de82c111640f29d8b72b4cd715f2b
+#: ../../source/about.rst:715
+msgid ""
+"During HA process , dead lock is detected - Caused by: "
+"com.mysql.jdbc.exception..."
+msgstr ""
+
+# 71832ade3b2541e1a3a3f609916a3e09
+#: ../../source/about.rst:716
+msgid ""
+"`CLOUDSTACK-1970 <https://issues.apache.org/jira/browse/CLOUDSTACK-1970>`_"
+msgstr ""
+
+# 5eec0dac3c8e42cf8b35868520332856
+#: ../../source/about.rst:716
+msgid "Ubuntu - \"cloudstack-setup-management\" not available in \"/usr/bin\"..."
+msgstr ""
+
+# 00c3e308c6904047b8cbc487f0957c66
+#: ../../source/about.rst:717
+msgid ""
+"`CLOUDSTACK-1889 <https://issues.apache.org/jira/browse/CLOUDSTACK-1889>`_"
+msgstr ""
+
+# 46653b8619e94ee2b8fd443df5747252
+#: ../../source/about.rst:717
+msgid ""
+"[UI] Consumed Resource usage details are not available for all the "
+"resources..."
+msgstr ""
+
+# 435bd9414777490f963054f53dbfa732
+#: ../../source/about.rst:718
+msgid ""
+"`CLOUDSTACK-1868 <https://issues.apache.org/jira/browse/CLOUDSTACK-1868>`_"
+msgstr ""
+
+# ac34caaa2aa7456eb62b1153d3571437
+#: ../../source/about.rst:718
+msgid "GetVmStatsCommand throws NullPointerException with VMWare..."
+msgstr ""
+
+# ab08172d39bc4c8bb9ab7cfa91000aad
+#: ../../source/about.rst:719
+msgid ""
+"`CLOUDSTACK-1762 <https://issues.apache.org/jira/browse/CLOUDSTACK-1762>`_"
+msgstr ""
+
+# fa3918f4d12f4481b74feccf226c23a4
+#: ../../source/about.rst:719
+msgid ""
+"[MultipleIpsToNic] addIpToNic should not let network id or broadcast to be "
+"assig..."
+msgstr ""
+
+# a509940809894b098bf385cc0a1da0f9
+#: ../../source/about.rst:720
+msgid ""
+"`CLOUDSTACK-1637 <https://issues.apache.org/jira/browse/CLOUDSTACK-1637>`_"
+msgstr ""
+
+# 963e03e004924de6a0ad38347e175932
+#: ../../source/about.rst:720
+msgid "LDAP:UI related issues..."
+msgstr ""
+
+# 0c3a1e330c8845ffb89d50ea264e8bed
+#: ../../source/about.rst:725
+msgid "Known Issues in 4.3.0"
+msgstr ""
+
+# d49bf145822b4f7dbef86a3a9d10e73b
+#: ../../source/about.rst:730
+msgid ""
+"For the list of known issues, see `Known Issues in 4.3 "
+"<https://issues.apache.org/jira/issues/?filter=12326162>`__."
+msgstr ""
+
+# 9366049c09cd445383d5d3ff85fcfb48
+#: ../../source/about.rst:736
+msgid ""
+"`CLOUDSTACK-4787 <https://issues.apache.org/jira/browse/CLOUDSTACK-4787>`_"
+msgstr ""
+
+# 8f4aeece6e1949989637c4efb79361b7
+#: ../../source/about.rst:736
+msgid "Allow selection of scsi controller type in vSphere..."
+msgstr ""
+
+# 5e4334fb180140568515e19db4fb5645
+#: ../../source/about.rst:737
+msgid ""
+"`CLOUDSTACK-6024 <https://issues.apache.org/jira/browse/CLOUDSTACK-6024>`_"
+msgstr ""
+
+# 8602cd20a2354d4f91c8d2d0707183bb
+#: ../../source/about.rst:737
+msgid ""
+"template copy to primary storage uses a random source secstorage from any "
+"zone..."
+msgstr ""
+
+# f965b5e733914160b9ba6fe86889ab33
+#: ../../source/about.rst:738
+msgid ""
+"`CLOUDSTACK-4912 <https://issues.apache.org/jira/browse/CLOUDSTACK-4912>`_"
+msgstr ""
+
+# a1bf258b622a402ea444b5919c2ada89
+#: ../../source/about.rst:738
+msgid "API docs are missing some APIs..."
+msgstr ""
+
+# f4d27c0e199746149129573d2409e273
+#: ../../source/about.rst:739
+msgid ""
+"`CLOUDSTACK-5124 <https://issues.apache.org/jira/browse/CLOUDSTACK-5124>`_"
+msgstr ""
+
+# 59001f906d4145838d36157c00a43716
+#: ../../source/about.rst:739
+msgid ""
+"Simulator: Virtual Router fails to start because of improper version "
+"returned by..."
+msgstr ""
+
+# 03066b547eb54b3e9a813a9491f53014
+#: ../../source/about.rst:740
+msgid ""
+"`CLOUDSTACK-5262 <https://issues.apache.org/jira/browse/CLOUDSTACK-5262>`_"
+msgstr ""
+
+# 61588455ea394b2aa5b2afd63c36fdf1
+#: ../../source/about.rst:740
+msgid ""
+"Few of the snapshot creation from ROOT volume fails when there are "
+"concurrent s..."
+msgstr ""
+
+# db7a1464b27641759dda869318e2d66a
+#: ../../source/about.rst:741
+msgid ""
+"`CLOUDSTACK-5356 <https://issues.apache.org/jira/browse/CLOUDSTACK-5356>`_"
+msgstr ""
+
+# 6e5a774deda34f439d5151cca1613c90
+#: ../../source/about.rst:741
+msgid ""
+"Xenserver - Failed to create snapshot when secondary store was made "
+"unavaibale f..."
+msgstr ""
+
+# b169a6830c64467a81a216b7c91bda40
+#: ../../source/about.rst:742
+msgid ""
+"`CLOUDSTACK-5357 <https://issues.apache.org/jira/browse/CLOUDSTACK-5357>`_"
+msgstr ""
+
+# 639986b439614db69e1d2e284d807ef5
+#: ../../source/about.rst:742
+msgid ""
+"Xenserver - Failed to create snapshot due to \"unable to destroy task(com.xe"
+" nsou..."
+msgstr ""
+
+# a91d75be88df483796e1289a7e3c7a9e
+#: ../../source/about.rst:743
+msgid ""
+"`CLOUDSTACK-5358 <https://issues.apache.org/jira/browse/CLOUDSTACK-5358>`_"
+msgstr ""
+
+# 87905fa46444475494cafe06a0178dcd
+#: ../../source/about.rst:743
+msgid "API: synchronization on the object is broken..."
+msgstr ""
+
+# c7d0b0c97c5d4bbdbad1c314d11c0089
+#: ../../source/about.rst:744
+msgid ""
+"`CLOUDSTACK-5372 <https://issues.apache.org/jira/browse/CLOUDSTACK-5372>`_"
+msgstr ""
+
+# 7882d7ff87ce46f081e356266833e989
+#: ../../source/about.rst:744
+msgid ""
+"Xenserver - SR not being recreated when the Primary storage is brought down "
+"and ..."
+msgstr ""
+
+# aea6fd27cdd94067b91a6baa77f0e78d
+#: ../../source/about.rst:745
+msgid ""
+"`CLOUDSTACK-5429 <https://issues.apache.org/jira/browse/CLOUDSTACK-5429>`_"
+msgstr ""
+
+# 6ca255d358d74a50a6e1635ce01c4c44
+#: ../../source/about.rst:745
+msgid ""
+"KVM - Primary store down/Network Failure - Hosts attempt to reboot becasue "
+"of pr..."
+msgstr ""
+
+# 62580c63110445e6b3e09b759fd56529
+#: ../../source/about.rst:746
+msgid ""
+"`CLOUDSTACK-5452 <https://issues.apache.org/jira/browse/CLOUDSTACK-5452>`_"
+msgstr ""
+
+# 4b181d14ded84b0987e71ad7a35d2efa
+#: ../../source/about.rst:746
+msgid ""
+"KVM - Agent is not able to connect back if management server was restarted "
+"when ..."
+msgstr ""
+
+# 96d8d6353aed48399f7193a12ceaa1d3
+#: ../../source/about.rst:747
+msgid ""
+"`CLOUDSTACK-5469 <https://issues.apache.org/jira/browse/CLOUDSTACK-5469>`_"
+msgstr ""
+
+# ccaa41bf6df4493bb14aa484e0269e59
+#: ../../source/about.rst:747
+msgid ""
+"Snapshot creation fails with following exception - \"Failed to backup "
+"snapshot: q..."
+msgstr ""
+
+# f13914ea540540dc8b1cb2811ab717f8
+#: ../../source/about.rst:748
+msgid ""
+"`CLOUDSTACK-5485 <https://issues.apache.org/jira/browse/CLOUDSTACK-5485>`_"
+msgstr ""
+
+# ed7ee25313b34426a38202561e527859
+#: ../../source/about.rst:748
+msgid ""
+"Vmware - Whe 10 hourly snapshots are scheduled at the same time , we see "
+"only 5 ..."
+msgstr ""
+
+# 9c0601c9e7734b3593c81d6e3396b073
+#: ../../source/about.rst:749
+msgid ""
+"`CLOUDSTACK-5494 <https://issues.apache.org/jira/browse/CLOUDSTACK-5494>`_"
+msgstr ""
+
+# 016b4e349c89418fa43c2cfa53759562
+#: ../../source/about.rst:749
+msgid "the dns resolver servers on the VRs are open to the world..."
+msgstr ""
+
+# 272abcf1004f4d209efcc245feca90b0
+#: ../../source/about.rst:750
+msgid ""
+"`CLOUDSTACK-5499 <https://issues.apache.org/jira/browse/CLOUDSTACK-5499>`_"
+msgstr ""
+
+# e1ae770626f24c2788147ebac0d4092d
+#: ../../source/about.rst:750
+msgid ""
+"Vmware -When nfs was down for about 12 hours and then brought back up again"
+" , s..."
+msgstr ""
+
+# a7a4a00d0a5f4879a9c07b323a76de7b
+#: ../../source/about.rst:751
+msgid ""
+"`CLOUDSTACK-5501 <https://issues.apache.org/jira/browse/CLOUDSTACK-5501>`_"
+msgstr ""
+
+# d0029106dc174d67bcb58ff30405375a
+#: ../../source/about.rst:751
+msgid ""
+"Unable to create more than one vpnConnection per vpn customer gateway..."
+msgstr ""
+
+# 4d36f1778bcd42e8a63a7de46295da9c
+#: ../../source/about.rst:752
+msgid ""
+"`CLOUDSTACK-5582 <https://issues.apache.org/jira/browse/CLOUDSTACK-5582>`_"
+msgstr ""
+
+# 074eb077241a471bbaa787ec57a6d5fc
+#: ../../source/about.rst:752
+msgid ""
+"kvm - HA is not triggered when host is powered down since the host gets into"
+" \"Di..."
+msgstr ""
+
+# 11e36e96a0e9432d97e85bdcae499039
+#: ../../source/about.rst:753
+msgid ""
+"`CLOUDSTACK-5746 <https://issues.apache.org/jira/browse/CLOUDSTACK-5746>`_"
+msgstr ""
+
+# e29f0b375c4e48cf82bfb437e6616cd0
+#: ../../source/about.rst:753
+msgid "[HyperV]Can't access vm console from IE browser..."
+msgstr ""
+
+# 0fa77f8beda54ce0a337ae8879c42f23
+#: ../../source/about.rst:754
+msgid ""
+"`CLOUDSTACK-5806 <https://issues.apache.org/jira/browse/CLOUDSTACK-5806>`_"
+msgstr ""
+
+# b80d04f5490d492aac1b9934e3fd3294
+#: ../../source/about.rst:754
+msgid "Storage types other than NFS/VMFS can't overprovision..."
+msgstr ""
+
+# 2853d64408e04d3eb896ed972c38abd0
+#: ../../source/about.rst:755
+msgid ""
+"`CLOUDSTACK-5818 <https://issues.apache.org/jira/browse/CLOUDSTACK-5818>`_"
+msgstr ""
+
+# 99081480a4ef41b6b485d636882ee694
+#: ../../source/about.rst:755
+msgid ""
+"[Hyper-v]Agent status of the System VMs is not updated during Host "
+"disconnect..."
+msgstr ""
+
+# 434b86def9994569910c09996b8d278f
+#: ../../source/about.rst:756
+msgid ""
+"`CLOUDSTACK-5825 <https://issues.apache.org/jira/browse/CLOUDSTACK-5825>`_"
+msgstr ""
+
+# 9dfa20e5f2f14461afb9244de60120c0
+#: ../../source/about.rst:756
+msgid "Create snapshot API always returns success..."
+msgstr ""
+
+# d9bb41e319ed4634aa76e4ed027b26a5
+#: ../../source/about.rst:757
+msgid ""
+"`CLOUDSTACK-5882 <https://issues.apache.org/jira/browse/CLOUDSTACK-5882>`_"
+msgstr ""
+
+# 0624959c7b944f2597d55d6e5d83672e
+#: ../../source/about.rst:757
+msgid "UI has different fonts and font sizes..."
+msgstr ""
+
+# 16861eac1095422a8364dbcf40e80951
+#: ../../source/about.rst:758
+msgid ""
+"`CLOUDSTACK-5899 <https://issues.apache.org/jira/browse/CLOUDSTACK-5899>`_"
+msgstr ""
+
+# 19c21bee456e483499bf251830708f61
+#: ../../source/about.rst:758
+msgid ""
+"Contrail:MS: Exceptions in MS logs on a fresh install, syncDomain "
+"java.lang.Nul..."
+msgstr ""
+
+# a904c1e9f7ac4cc5ae6f113b3dd1a8e7
+#: ../../source/about.rst:759
+msgid ""
+"`CLOUDSTACK-5928 <https://issues.apache.org/jira/browse/CLOUDSTACK-5928>`_"
+msgstr ""
+
+# e5d40dceeaca4d9199780829785762c2
+#: ../../source/about.rst:759
+msgid ""
+"[VM Sync] - Vmware - When a Vm is \"suspended\" from outside of CloudStack ,"
+" this ..."
+msgstr ""
+
+# cb709ada209f452791d9f0d642c0aa74
+#: ../../source/about.rst:760
+msgid ""
+"`CLOUDSTACK-5929 <https://issues.apache.org/jira/browse/CLOUDSTACK-5929>`_"
+msgstr ""
+
+# 1ac61e7f25724ab8bb94a59ab49e207a
+#: ../../source/about.rst:760
+msgid ""
+"[VM Sync] - Vmware - Even when starting Vm fails, startVirtualMachine async "
+"job ..."
+msgstr ""
+
+# 9f92e99b84c84965982641964e138eb2
+#: ../../source/about.rst:761
+msgid ""
+"`CLOUDSTACK-5961 <https://issues.apache.org/jira/browse/CLOUDSTACK-5961>`_"
+msgstr ""
+
+# d35722d202414d76a3bcbf24200b1117
+#: ../../source/about.rst:761
+msgid "CLONE - API: synchronization on the object is broken..."
+msgstr ""
+
+# 00a0213f26594b95b9a9017d9dae6570
+#: ../../source/about.rst:762
+msgid ""
+"`CLOUDSTACK-6050 <https://issues.apache.org/jira/browse/CLOUDSTACK-6050>`_"
+msgstr ""
+
+# 45f672667c7d4b6c918f227f43f52c91
+#: ../../source/about.rst:762
+msgid "A limitations on min-max on CPU/RAM for a dynamic offering ..."
+msgstr ""
+
+# 6365b06a722d4c96ae245cbee93ed394
+#: ../../source/about.rst:763
+msgid ""
+"`CLOUDSTACK-6051 <https://issues.apache.org/jira/browse/CLOUDSTACK-6051>`_"
+msgstr ""
+
+# 3a190cc12bfe44e4b53e6e035f3c117e
+#: ../../source/about.rst:763
+msgid ""
+"VR Rolling upgrade: Make the numbers of Routers parallely being upgraded as "
+"conf..."
+msgstr ""
+
+# a25ebfc86f2841f19ac5cc04d3dde867
+#: ../../source/about.rst:764
+msgid ""
+"`CLOUDSTACK-6063 <https://issues.apache.org/jira/browse/CLOUDSTACK-6063>`_"
+msgstr ""
+
+# f12e5b103586477ea4c4c4d1994cf44e
+#: ../../source/about.rst:764
+msgid ""
+"CLONE - Non windows instances are created on XenServer with a vcpu-max above"
+" sup..."
+msgstr ""
+
+# 4f9e0035a6b44f5d92b00503a47655b0
+#: ../../source/about.rst:765
+msgid ""
+"`CLOUDSTACK-6065 <https://issues.apache.org/jira/browse/CLOUDSTACK-6065>`_"
+msgstr ""
+
+# 6b71991d62c44dd0bde9b4a9fbd0c5fb
+#: ../../source/about.rst:765
+msgid "No HA for shutdown VM..."
+msgstr ""
+
+# 425db0f637ed4915afa530fcc3375ed4
+#: ../../source/about.rst:766
+msgid ""
+"`CLOUDSTACK-6079 <https://issues.apache.org/jira/browse/CLOUDSTACK-6079>`_"
+msgstr ""
+
+# d2f5c21ec6f542b08638f6669400297d
+#: ../../source/about.rst:766
+msgid ""
+"a broadcast type of a public network is affected by another physical "
+"network's i..."
+msgstr ""
+
+# ab87957eba284769b16e2f313d52fb73
+#: ../../source/about.rst:767
+msgid "`CLOUDSTACK-77 <https://issues.apache.org/jira/browse/CLOUDSTACK-77>`_"
+msgstr ""
+
+# 58e41ab8179b4b9782269462459007da
+#: ../../source/about.rst:767
+msgid "console proxy display issues..."
+msgstr ""
+
+# 8db0e533f7cd4cfcab081bf4bc00f742
+#: ../../source/about.rst:768
+msgid ""
+"`CLOUDSTACK-107 <https://issues.apache.org/jira/browse/CLOUDSTACK-107>`_"
+msgstr ""
+
+# 30415dcf674a4e8aae51521111db2666
+#: ../../source/about.rst:768
+msgid ""
+"Network domain guest suffix is not getting programmed as part of hostnames "
+"on Gu..."
+msgstr ""
+
+# 0478485b947a42d893c510be01d98ecf
+#: ../../source/about.rst:769
+msgid ""
+"`CLOUDSTACK-237 <https://issues.apache.org/jira/browse/CLOUDSTACK-237>`_"
+msgstr ""
+
+# 71b1b10c10114813847cf99866792d9e
+#: ../../source/about.rst:769
+msgid ""
+"StopVMCommand reported success in spite of failing to stop a VM which got "
+"stuck ..."
+msgstr ""
+
+# 1136090c600443d19756782e8d7818ca
+#: ../../source/about.rst:770
+msgid ""
+"`CLOUDSTACK-238 <https://issues.apache.org/jira/browse/CLOUDSTACK-238>`_"
+msgstr ""
+
+# f0f5e9f088734e87b56c111932fbb7dd
+#: ../../source/about.rst:770
+msgid "vpn:fail to connect to vpnserver using non-sourceNAT IP..."
+msgstr ""
+
+# 942ec655385b4572a2d114289ea139e3
+#: ../../source/about.rst:771
+msgid ""
+"`CLOUDSTACK-252 <https://issues.apache.org/jira/browse/CLOUDSTACK-252>`_"
+msgstr ""
+
+# 7485de1c33634d6e83be7b5071b36494
+#: ../../source/about.rst:771
+msgid ""
+"UpdateNetwork Operation on a guest network that is currently using Virtual "
+"Route..."
+msgstr ""
+
+# 3dafae3e04bf4f4f9f60119b05e19fa4
+#: ../../source/about.rst:772
+msgid ""
+"`CLOUDSTACK-255 <https://issues.apache.org/jira/browse/CLOUDSTACK-255>`_"
+msgstr ""
+
+# 12c7e710aa264aae858df1d2f23aa4b4
+#: ../../source/about.rst:772
+msgid ""
+"Null pointer exception while creating portforwarding rule after performing "
+"Updat..."
+msgstr ""
+
+# 3b8c83c736c5459fbf7eb523af102016
+#: ../../source/about.rst:773
+msgid ""
+"`CLOUDSTACK-317 <https://issues.apache.org/jira/browse/CLOUDSTACK-317>`_"
+msgstr ""
+
+# 993dc0a2fb404658869813b95da84503
+#: ../../source/about.rst:773
+msgid "get xcp 1.5 into an advanced network zone..."
+msgstr ""
+
+# e47c93e7c1f942d7b05c707e5d541587
+#: ../../source/about.rst:774
+msgid ""
+"`CLOUDSTACK-375 <https://issues.apache.org/jira/browse/CLOUDSTACK-375>`_"
+msgstr ""
+
+# b37d48fbcffa459ca04e8ef145b73afd
+#: ../../source/about.rst:774
+msgid ""
+"Unable to delete physical network - because there are other networks "
+"attached..."
+msgstr ""
+
+# 4af711936fee4c988e113d781befa5cb
+#: ../../source/about.rst:775
+msgid ""
+"`CLOUDSTACK-425 <https://issues.apache.org/jira/browse/CLOUDSTACK-425>`_"
+msgstr ""
+
+# 393010e91cff45e3a01cd9f1e91fef89
+#: ../../source/about.rst:775
+msgid "Check image type is qcow2 before actually installing..."
+msgstr ""
+
+# 34e77b0e2b3241709397cd2790f01ade
+#: ../../source/about.rst:776
+msgid ""
+"`CLOUDSTACK-992 <https://issues.apache.org/jira/browse/CLOUDSTACK-992>`_"
+msgstr ""
+
+# 966a5c0fa5e3493fa34da35be918c192
+#: ../../source/about.rst:776
+msgid "Template creations dies after 2h for no reason..."
+msgstr ""
+
+# 98af046f690c46b38720f7d61a8b0f1d
+#: ../../source/about.rst:777
+msgid ""
+"`CLOUDSTACK-1007 <https://issues.apache.org/jira/browse/CLOUDSTACK-1007>`_"
+msgstr ""
+
+# d7b482d0c9624fc78beeaa15f5c127b5
+#: ../../source/about.rst:777
+msgid ""
+"Not able to delete Shared network because of not being able to stop the "
+"router...."
+msgstr ""
+
+# 86304829cdb74cafac6f27e592dc3a5e
+#: ../../source/about.rst:778
+msgid ""
+"`CLOUDSTACK-1091 <https://issues.apache.org/jira/browse/CLOUDSTACK-1091>`_"
+msgstr ""
+
+# 79b006800d5b4773a79bc902f5181ade
+#: ../../source/about.rst:778
+msgid "Fix API server's parsing mechanism for POST requests..."
+msgstr ""
+
+# b9fee6af60f0460095dbe2e830e303ab
+#: ../../source/about.rst:779
+msgid ""
+"`CLOUDSTACK-1092 <https://issues.apache.org/jira/browse/CLOUDSTACK-1092>`_"
+msgstr ""
+
+# 1c7f9eabb70044efb0095a5ab168ad14
+#: ../../source/about.rst:779
+msgid "Fix API Server's parsing mechanism to parse GET request as multimap..."
+msgstr ""
+
+# 5c8b082a719b4ea190d97f9454d05cf1
+#: ../../source/about.rst:780
+msgid ""
+"`CLOUDSTACK-1309 <https://issues.apache.org/jira/browse/CLOUDSTACK-1309>`_"
+msgstr ""
+
+# 559f925366694f0b89250fb27f32252f
+#: ../../source/about.rst:780
+msgid "Large guest subnets downgrade performance..."
+msgstr ""
+
+# 5f09bbec09ec4d3385a78688bdc27c53
+#: ../../source/about.rst:781
+msgid ""
+"`CLOUDSTACK-1389 <https://issues.apache.org/jira/browse/CLOUDSTACK-1389>`_"
+msgstr ""
+
+# 54ac55f5877b4fe581e6db4a65028984
+#: ../../source/about.rst:781
+msgid "Interactive Password Prompts during Management Server Startup..."
+msgstr ""
+
+# 5bce4bad1fba4599bfa6d89c78408789
+#: ../../source/about.rst:782
+msgid ""
+"`CLOUDSTACK-1413 <https://issues.apache.org/jira/browse/CLOUDSTACK-1413>`_"
+msgstr ""
+
+# 96a2b2ec34734bf7ac5d5cdaaf74598e
+#: ../../source/about.rst:782
+msgid ""
+"Need something to concretely identify the version of the code in a "
+"particular bu..."
+msgstr ""
+
+# 0d69c0bd10494513a62d811f6e46d372
+#: ../../source/about.rst:783
+msgid ""
+"`CLOUDSTACK-1527 <https://issues.apache.org/jira/browse/CLOUDSTACK-1527>`_"
+msgstr ""
+
+# bf2038111b4540a0b3d454d47c7b495e
+#: ../../source/about.rst:783
+msgid ""
+"Non-fatal POSTIN scriptlet failure in rpm package cloudstack-"
+"management-4.2.0-SN..."
+msgstr ""
+
+# 3fb20b2036564c1fa19718e401ea7e83
+#: ../../source/about.rst:784
+msgid ""
+"`CLOUDSTACK-1717 <https://issues.apache.org/jira/browse/CLOUDSTACK-1717>`_"
+msgstr ""
+
+# 66b9fd5c669949f28ba4638fd8a1ad5f
+#: ../../source/about.rst:784
+msgid ""
+"AWS Regions - Local region entry that gets added by default should not "
+"include \"..."
+msgstr ""
+
+# 9f7e62b1e16f4ed88d7e06a1725bc1c8
+#: ../../source/about.rst:785
+msgid ""
+"`CLOUDSTACK-1885 <https://issues.apache.org/jira/browse/CLOUDSTACK-1885>`_"
+msgstr ""
+
+# 1291d9e7d55f4db68ea3774192f71614
+#: ../../source/about.rst:785
+msgid "Broken testcases in 4.1..."
+msgstr ""
+
+# ccec471c679e418abd739c1c91ead940
+#: ../../source/about.rst:786
+msgid ""
+"`CLOUDSTACK-1990 <https://issues.apache.org/jira/browse/CLOUDSTACK-1990>`_"
+msgstr ""
+
+# ed34d5ff52e649e4bd6f2d925cc5949b
+#: ../../source/about.rst:786
+msgid "Docs: Update \"Choosing a Hypervisor\" feature matrix with new info..."
+msgstr ""
+
+# 35938d7b4f394c97babe38ce2952e5b4
+#: ../../source/about.rst:787
+msgid ""
+"`CLOUDSTACK-2004 <https://issues.apache.org/jira/browse/CLOUDSTACK-2004>`_"
+msgstr ""
+
+# f0263264fe1c40de9d674a91656bbdf5
+#: ../../source/about.rst:787
+msgid ""
+"IPV6 - UI - Router details page - NICs tab - Guest traffic type does not "
+"displa..."
+msgstr ""
+
+# de60a69d430a410e8bc57691c7e9e619
+#: ../../source/about.rst:788
+msgid ""
+"`CLOUDSTACK-2009 <https://issues.apache.org/jira/browse/CLOUDSTACK-2009>`_"
+msgstr ""
+
+# 6567c71b940444929ac6185fe5bb21a6
+#: ../../source/about.rst:788
+msgid ""
+"IPV6 - listNetwork() command does not return ip6dns1 and ip6dns2 entries...."
+msgstr ""
+
+# 22c97b1b399c4edbbf740a5c69fda2fb
+#: ../../source/about.rst:789
+msgid ""
+"`CLOUDSTACK-2022 <https://issues.apache.org/jira/browse/CLOUDSTACK-2022>`_"
+msgstr ""
+
+# 3fea24a0775c43cf95dccc0964b92813
+#: ../../source/about.rst:789
+msgid ""
+"IPV6 - ListRouter() should return guestip6address parameter similar to "
+"guestaddr..."
+msgstr ""
+
+# 0ed5b14f0cd74aada5e8ba7d6d3a52cd
+#: ../../source/about.rst:790
+msgid ""
+"`CLOUDSTACK-2023 <https://issues.apache.org/jira/browse/CLOUDSTACK-2023>`_"
+msgstr ""
+
+# bc0faed231f8441982734fa1a09de47d
+#: ../../source/about.rst:790
+msgid ""
+"IPV6 - Dashboard View - System wide Capacity for Shared Network IPs does not"
+" inc..."
+msgstr ""
+
+# fa7dcf3381784c058080b779c7dad0eb
+#: ../../source/about.rst:791
+msgid ""
+"`CLOUDSTACK-2026 <https://issues.apache.org/jira/browse/CLOUDSTACK-2026>`_"
+msgstr ""
+
+# 8d920ff504164433a5cb8d14b28b20f3
+#: ../../source/about.rst:791
+msgid ""
+"IPV6 - UI - Provide the ability to turn off all the IPV6 parameters by using"
+" a g..."
+msgstr ""
+
+# 793844374b9a4717af4e3a96efc78646
+#: ../../source/about.rst:792
+msgid ""
+"`CLOUDSTACK-2099 <https://issues.apache.org/jira/browse/CLOUDSTACK-2099>`_"
+msgstr ""
+
+# ee4a3ac2203c445ab4c40c86bb151e00
+#: ../../source/about.rst:792
+msgid ""
+"Not able to add a host after a failed attempt to add the host to a wrong "
+"cluster..."
+msgstr ""
+
+# ab446ac6458242128fdee362ba605323
+#: ../../source/about.rst:793
+msgid ""
+"`CLOUDSTACK-2112 <https://issues.apache.org/jira/browse/CLOUDSTACK-2112>`_"
+msgstr ""
+
+# 5d41a79c37984b4aa387d67f332aecea
+#: ../../source/about.rst:793
+msgid ""
+"VM went in stopped state after live migration failed while vmscaleup..."
+msgstr ""
+
+# fcb182c9bf924f4f853a7063df6c72fe
+#: ../../source/about.rst:794
+msgid ""
+"`CLOUDSTACK-2191 <https://issues.apache.org/jira/browse/CLOUDSTACK-2191>`_"
+msgstr ""
+
+# 7c79e43a414c41c78f5a9c4edbad126d
+#: ../../source/about.rst:794
+msgid "sanity tests for \"EIP : Optional public IP\" changes ..."
+msgstr ""
+
+# dd24fc75a09e42b689b41a385c5b1fcb
+#: ../../source/about.rst:795
+msgid ""
+"`CLOUDSTACK-2291 <https://issues.apache.org/jira/browse/CLOUDSTACK-2291>`_"
+msgstr ""
+
+# d0ad039c438f49f0b9c19c61ad06491f
+#: ../../source/about.rst:795
+msgid "[BasicZone-XenServer] NPE while trying DeleteNetworkCmd..."
+msgstr ""
+
+# 1cd9814861e94fe0b12bba775d9ccf0c
+#: ../../source/about.rst:796
+msgid ""
+"`CLOUDSTACK-2293 <https://issues.apache.org/jira/browse/CLOUDSTACK-2293>`_"
+msgstr ""
+
+# d6d7e68458b34ace9167b0faaac4ab7a
+#: ../../source/about.rst:796
+msgid ""
+"[BasicZone-XenServer] DeletePhysicalNetworkCmd is not deleting the external "
+"devi..."
+msgstr ""
+
+# 18827dbf664d49208a18c18850a873b2
+#: ../../source/about.rst:797
+msgid ""
+"`CLOUDSTACK-2412 <https://issues.apache.org/jira/browse/CLOUDSTACK-2412>`_"
+msgstr ""
+
+# 38571b8b919d4bbfb91db330b39bb3be
+#: ../../source/about.rst:797
+msgid ""
+"[UI]Disable CiscoVnmc provider for PF/SourceNat/StaticNAT/Firewall dropdown "
+"list..."
+msgstr ""
+
+# ec84d91d357c45958e085d92b444cc27
+#: ../../source/about.rst:798
+msgid ""
+"`CLOUDSTACK-2418 <https://issues.apache.org/jira/browse/CLOUDSTACK-2418>`_"
+msgstr ""
+
+# 2a694e0fae5f464995bacd104ed7e193
+#: ../../source/about.rst:798
+msgid "[GSLB] NPE while removing the GSLB enabled Netscaler device..."
+msgstr ""
+
+# 51a98d1f52684b31a511fb501b9763d4
+#: ../../source/about.rst:799
+msgid ""
+"`CLOUDSTACK-2471 <https://issues.apache.org/jira/browse/CLOUDSTACK-2471>`_"
+msgstr ""
+
+# 31313e3102a543f8b28ddd44d0962e8e
+#: ../../source/about.rst:799
+msgid ""
+"test_host_high_availability.py refers to non-existent library method "
+"wait_for_vm..."
+msgstr ""
+
+# ada6fc26d9624177be27b1c639f95f84
+#: ../../source/about.rst:800
+msgid ""
+"`CLOUDSTACK-2501 <https://issues.apache.org/jira/browse/CLOUDSTACK-2501>`_"
+msgstr ""
+
+# 124c3850029149ab96dc7947c674eddd
+#: ../../source/about.rst:800
+msgid "Scalevm - Need to take care of upgraded vms..."
+msgstr ""
+
+# 1aae5d9479fe40478d8cacdbc0e587ff
+#: ../../source/about.rst:801
+msgid ""
+"`CLOUDSTACK-2790 <https://issues.apache.org/jira/browse/CLOUDSTACK-2790>`_"
+msgstr ""
+
+# 4ed9bf78e0704a0d8d93f6058c104a7a
+#: ../../source/about.rst:801
+msgid ""
+"AWSAPI: packaging includes all .class files bloating size of the RPM..."
+msgstr ""
+
+# 5f5c0509b8f146d08c9c9a76f2156c52
+#: ../../source/about.rst:802
+msgid ""
+"`CLOUDSTACK-2795 <https://issues.apache.org/jira/browse/CLOUDSTACK-2795>`_"
+msgstr ""
+
+# 7e9640a68f5247a99469683531916949
+#: ../../source/about.rst:802
+msgid "Create template failed..."
+msgstr ""
+
+# 2849f81c404843a8a81855096a962d69
+#: ../../source/about.rst:803
+msgid ""
+"`CLOUDSTACK-2845 <https://issues.apache.org/jira/browse/CLOUDSTACK-2845>`_"
+msgstr ""
+
+# dcdfe224c84442a3b2b41bff5da1d588
+#: ../../source/about.rst:803
+msgid ""
+"[DB upgrade] [ExternalLoadBalancer NetworkUsage] Duplicate entries in the "
+"databa..."
+msgstr ""
+
+# 98217b63240548688393be2e88a4f377
+#: ../../source/about.rst:804
+msgid ""
+"`CLOUDSTACK-2853 <https://issues.apache.org/jira/browse/CLOUDSTACK-2853>`_"
+msgstr ""
+
+# c6bd19a7a73f4e4abf00dc6a7cde162d
+#: ../../source/about.rst:804
+msgid ""
+"Cloudstack copies xenserver scripts while adding host even the server is KVM"
+" hos..."
+msgstr ""
+
+# 941394cdf67944659f3889c78f57f9f8
+#: ../../source/about.rst:805
+msgid ""
+"`CLOUDSTACK-2860 <https://issues.apache.org/jira/browse/CLOUDSTACK-2860>`_"
+msgstr ""
+
+# 1628ad0620cd49e9924a86968ad1ee4f
+#: ../../source/about.rst:805
+msgid "Add new host into VMWare Cluster failed..."
+msgstr ""
+
+# 39c55e252fa041eb82425bb91a7b3c76
+#: ../../source/about.rst:806
+msgid ""
+"`CLOUDSTACK-2910 <https://issues.apache.org/jira/browse/CLOUDSTACK-2910>`_"
+msgstr ""
+
+# a529078d75fa46cca5b9cb18ce79b52e
+#: ../../source/about.rst:806
+msgid "SC: Ctrl combinated with >. is not working of SC IME..."
+msgstr ""
+
+# bf922c06163b4b50864a6a3959455269
+#: ../../source/about.rst:807
+msgid ""
+"`CLOUDSTACK-2911 <https://issues.apache.org/jira/browse/CLOUDSTACK-2911>`_"
+msgstr ""
+
+# 0aaf8d4c57c2465ba91c081c21e2b55a
+#: ../../source/about.rst:807
+msgid ""
+"KO: Key translation fails for KO keyboard Right Alt, Han/Eng, Hanja keys..."
+msgstr ""
+
+# 3597495e5a5a4f57aa03ba72c8567952
+#: ../../source/about.rst:808
+msgid ""
+"`CLOUDSTACK-2919 <https://issues.apache.org/jira/browse/CLOUDSTACK-2919>`_"
+msgstr ""
+
+# 573fb7c3a40a4c928742e4ecf3387082
+#: ../../source/about.rst:808
+msgid ""
+"Snapshot cannot be saved to full Secondary Storage, but doesn't utilize "
+"other Se..."
+msgstr ""
+
+# cffb645f459945fd9dc9c0e49fa44321
+#: ../../source/about.rst:809
+msgid ""
+"`CLOUDSTACK-3066 <https://issues.apache.org/jira/browse/CLOUDSTACK-3066>`_"
+msgstr ""
+
+# d0f03d5f754e4379b06b3c6de68648c7
+#: ../../source/about.rst:809
+msgid ""
+"No Error message is popped up on UI when a dedicated resource is dedicated "
+"to an..."
+msgstr ""
+
+# 38f4839bebaf467d9783473f01c3a3e5
+#: ../../source/about.rst:810
+msgid ""
+"`CLOUDSTACK-3095 <https://issues.apache.org/jira/browse/CLOUDSTACK-3095>`_"
+msgstr ""
+
+# 3f91537181d94b4dbfa476a7c9677bbc
+#: ../../source/about.rst:810
+msgid ""
+"[UI][API]Able to add multiple tier networks to a deployed VM using “Add "
+"network”..."
+msgstr ""
+
+# f833d338561d4217a15544dc75cc6b02
+#: ../../source/about.rst:811
+msgid ""
+"`CLOUDSTACK-3111 <https://issues.apache.org/jira/browse/CLOUDSTACK-3111>`_"
+msgstr ""
+
+# 7dee5d8b690a4da594074a0b219f0cc0
+#: ../../source/about.rst:811
+msgid ""
+"[UI] Storage tab is not showing the Hypervisor column as 'KVM' if the "
+"(root/data..."
+msgstr ""
+
+# 7e42206866834b8f8e7615d4f1cb75f5
+#: ../../source/about.rst:812
+msgid ""
+"`CLOUDSTACK-3186 <https://issues.apache.org/jira/browse/CLOUDSTACK-3186>`_"
+msgstr ""
+
+# 54509d0dcf424af3b376d59b7b255803
+#: ../../source/about.rst:812
+msgid "Duplicate entries in /etc/hosts file on VR after reboot..."
+msgstr ""
+
+# 3132607cd3184dafa2f1802146401959
+#: ../../source/about.rst:813
+msgid ""
+"`CLOUDSTACK-3195 <https://issues.apache.org/jira/browse/CLOUDSTACK-3195>`_"
+msgstr ""
+
+# 910ba9121d5a4d6185e8e62c3514e80d
+#: ../../source/about.rst:813
+msgid ""
+"cannot view/delete forward rules if underlying/target VM is destroyed "
+"first..."
+msgstr ""
+
+# 18f973b769534e44b4a2c229e624c531
+#: ../../source/about.rst:814
+msgid ""
+"`CLOUDSTACK-3197 <https://issues.apache.org/jira/browse/CLOUDSTACK-3197>`_"
+msgstr ""
+
+# 86d337d71d914114a22e739ee0c1158e
+#: ../../source/about.rst:814
+msgid ""
+"UI: NTier: User is required to scroll down every single time to \"Create "
+"Network\"..."
+msgstr ""
+
+# 4e861db64f9e45f59cabd7fcc9fa0679
+#: ../../source/about.rst:815
+msgid ""
+"`CLOUDSTACK-3212 <https://issues.apache.org/jira/browse/CLOUDSTACK-3212>`_"
+msgstr ""
+
+# 01f3a22662734ac99f60c35f61f812c8
+#: ../../source/about.rst:815
+msgid ""
+"[Advanced_With_SG]View IP Address Range in Default Guest Network page does "
+"not s..."
+msgstr ""
+
+# 8a12acc4d4e74781853e2f2f7e94d136
+#: ../../source/about.rst:816
+msgid ""
+"`CLOUDSTACK-3272 <https://issues.apache.org/jira/browse/CLOUDSTACK-3272>`_"
+msgstr ""
+
+# 9c878c581cba4e42bd48bd458616b333
+#: ../../source/about.rst:816
+msgid ""
+"EventBus: add global config parameters to specify which category of events "
+"are p..."
+msgstr ""
+
+# 72289cd2085e4587bbbc496e737cf9c8
+#: ../../source/about.rst:817
+msgid ""
+"`CLOUDSTACK-3338 <https://issues.apache.org/jira/browse/CLOUDSTACK-3338>`_"
+msgstr ""
+
+# 92f151a159234c019aace4e06369ca4d
+#: ../../source/about.rst:817
+msgid ""
+"Please provide an icon for \"assignVMs\" action in internal LB rule "
+"detailView..."
+msgstr ""
+
+# 403c32dcb0eb46b7af0496a7cd7e21f4
+#: ../../source/about.rst:818
+msgid ""
+"`CLOUDSTACK-3518 <https://issues.apache.org/jira/browse/CLOUDSTACK-3518>`_"
+msgstr ""
+
+# 7196bf7321fd43f8a5b4d39509c4109b
+#: ../../source/about.rst:818
+msgid ""
+"G11n: JA,SC: Un translation issue occurred on the strings of different UI "
+"Specif..."
+msgstr ""
+
+# 8d9ee211b3104f17b274b327ec5dc980
+#: ../../source/about.rst:819
+msgid ""
+"`CLOUDSTACK-3519 <https://issues.apache.org/jira/browse/CLOUDSTACK-3519>`_"
+msgstr ""
+
+# d9cfa91d52844c64904ed2cc4c633721
+#: ../../source/about.rst:819
+msgid ""
+"G11n: JA,SC: Un translation issue occurred on the strings of different "
+"dropdown ..."
+msgstr ""
+
+# df83d462a87d480f8e46736fadda2b18
+#: ../../source/about.rst:820
+msgid ""
+"`CLOUDSTACK-3520 <https://issues.apache.org/jira/browse/CLOUDSTACK-3520>`_"
+msgstr ""
+
+# 035600ab16804b1e9b933b1f2d7ad00f
+#: ../../source/about.rst:820
+msgid ""
+"G11n: JA,SC: Un translation issue occurred on the strings of different "
+"error/war..."
+msgstr ""
+
+# 21bb0266af484d74acf892a71d15fa86
+#: ../../source/about.rst:821
+msgid ""
+"`CLOUDSTACK-3521 <https://issues.apache.org/jira/browse/CLOUDSTACK-3521>`_"
+msgstr ""
+
+# 941512cad6df40518857e8fa2290a2bc
+#: ../../source/about.rst:821
+msgid ""
+"G11n: JA,SC: Un translation issue occurred on the strings of different "
+"tooltips...."
+msgstr ""
+
+# 82333b9ab8e64c56ae2d5d0bc794ee7c
+#: ../../source/about.rst:822
+msgid ""
+"`CLOUDSTACK-3522 <https://issues.apache.org/jira/browse/CLOUDSTACK-3522>`_"
+msgstr ""
+
+# a079a80c68f1484fb8207064327734fa
+#: ../../source/about.rst:822
+msgid ""
+"G11n: JA,SC: Un translation issue occurred on the strings of different "
+"buttons. ..."
+msgstr ""
+
+# 6e1237e4228b47d98248ea0e2f5511d8
+#: ../../source/about.rst:823
+msgid ""
+"`CLOUDSTACK-3523 <https://issues.apache.org/jira/browse/CLOUDSTACK-3523>`_"
+msgstr ""
+
+# 19e2371eee164cbd88a8d983ae0d4001
+#: ../../source/about.rst:823
+msgid ""
+"G11n: JA,SC: Un translation issue occurred on the strings of different popup"
+" mes..."
+msgstr ""
+
+# 723e9a7dbd3646bca15415a0ea508339
+#: ../../source/about.rst:824
+msgid ""
+"`CLOUDSTACK-3528 <https://issues.apache.org/jira/browse/CLOUDSTACK-3528>`_"
+msgstr ""
+
+# 0f57c235ba8244f48d3feb9aa69a525d
+#: ../../source/about.rst:824
+msgid ""
+"[UI]list calls are in the processing state forever with invalid name "
+"provided wi..."
+msgstr ""
+
+# 9e6a31684c0946c6819d1ac93c7dc867
+#: ../../source/about.rst:825
+msgid ""
+"`CLOUDSTACK-3579 <https://issues.apache.org/jira/browse/CLOUDSTACK-3579>`_"
+msgstr ""
+
+# 957e7bbdd41f4c078a53c649480bdd59
+#: ../../source/about.rst:825
+msgid ""
+"[DOC]CLONE - Physical Netwok traffic label update requires Management Server"
+" res..."
+msgstr ""
+
+# 7beeaf7483a14fcbb7969f9656e29b87
+#: ../../source/about.rst:826
+msgid ""
+"`CLOUDSTACK-3607 <https://issues.apache.org/jira/browse/CLOUDSTACK-3607>`_"
+msgstr ""
+
+# 66e98209f17d4a7d99f8002440b48b7e
+#: ../../source/about.rst:826
+msgid ""
+"\"guest_os_hypervisor\" table has values that are not registered in "
+"\"guest_os\" tab..."
+msgstr ""
+
+# 40656611fac94cfd82af00b0b0ea88ba
+#: ../../source/about.rst:827
+msgid ""
+"`CLOUDSTACK-3608 <https://issues.apache.org/jira/browse/CLOUDSTACK-3608>`_"
+msgstr ""
+
+# edf5f359c7a7442b9f291ad17799e056
+#: ../../source/about.rst:827
+msgid ""
+"\"guest_os_hypervisor\" table has repeated mappings of hypervisor and guest "
+"OS..."
+msgstr ""
+
+# 823d2fdb78514741a54d1f6a306aff86
+#: ../../source/about.rst:828
+msgid ""
+"`CLOUDSTACK-3656 <https://issues.apache.org/jira/browse/CLOUDSTACK-3656>`_"
+msgstr ""
+
+# d6105677e00a496d90c6dbc60a033134
+#: ../../source/about.rst:828
+msgid "lots of cloud-management should be changed to cloudstack-management..."
+msgstr ""
+
+# 4fb3155e8cbb4039915ed049a588de0f
+#: ../../source/about.rst:829
+msgid ""
+"`CLOUDSTACK-3788 <https://issues.apache.org/jira/browse/CLOUDSTACK-3788>`_"
+msgstr ""
+
+# 9174fad66e2942f19a41bd96ec2d5735
+#: ../../source/about.rst:829
+msgid "[KVM] Weekly Snapshot got stuck in \"Allocated State\"..."
+msgstr ""
+
+# f64b400ca17e4ffcb981e28b2d16c401
+#: ../../source/about.rst:830
+msgid ""
+"`CLOUDSTACK-3813 <https://issues.apache.org/jira/browse/CLOUDSTACK-3813>`_"
+msgstr ""
+
+# 4b1a6edaa6e94ec2bf5dab3e40938dd3
+#: ../../source/about.rst:830
+msgid ""
+"\"Service.provider.create\" event doesnt mention about the Service Provider "
+"in the..."
+msgstr ""
+
+# 70306e8bf5d949419e3f741d054cc8b8
+#: ../../source/about.rst:831
+msgid ""
+"`CLOUDSTACK-3880 <https://issues.apache.org/jira/browse/CLOUDSTACK-3880>`_"
+msgstr ""
+
+# d61367a71c5943549a60e9d4118fe201
+#: ../../source/about.rst:831
+msgid ""
+"/sbin/poweroff et al or ACPID initiated shutdown does not stop "
+"cloudstack-[usage..."
+msgstr ""
+
+# 11ac67a35df9435981b41ab866d4b9a1
+#: ../../source/about.rst:832
+msgid ""
+"`CLOUDSTACK-3952 <https://issues.apache.org/jira/browse/CLOUDSTACK-3952>`_"
+msgstr ""
+
+# 1181e2c183fe41d49e7b39f6e8e39167
+#: ../../source/about.rst:832
+msgid "Persist VR nic details in DB for additional public ranges..."
+msgstr ""
+
+# 28323cb78e7043bb910e56ae18986eda
+#: ../../source/about.rst:833
+msgid ""
+"`CLOUDSTACK-3973 <https://issues.apache.org/jira/browse/CLOUDSTACK-3973>`_"
+msgstr ""
+
+# a361a2dfcaf34fc19278258986905ecb
+#: ../../source/about.rst:833
+msgid ""
+"[GSLB] [LOGS Message] Improving logs messages for GSLB rule configuration..."
+msgstr ""
+
+# 25a2fe3aa3c44e88889d7ad5e3a15d09
+#: ../../source/about.rst:834
+msgid ""
+"`CLOUDSTACK-4016 <https://issues.apache.org/jira/browse/CLOUDSTACK-4016>`_"
+msgstr ""
+
+# 2624bd1fa06149e1ab3ebee7cce9e5be
+#: ../../source/about.rst:834
+msgid ""
+"[PortableIP] [VPC] listPublicIpAddresses lists the portable IP that was "
+"already ..."
+msgstr ""
+
+# d5156db04f4f4323ad6c08d0786fedda
+#: ../../source/about.rst:835
+msgid ""
+"`CLOUDSTACK-4139 <https://issues.apache.org/jira/browse/CLOUDSTACK-4139>`_"
+msgstr ""
+
+# b0326517fda54a2ebbd4a2677d78bac8
+#: ../../source/about.rst:835
+msgid ""
+"[VMWARE]Failed to resize the volumes which are created from snapshot of root"
+" vol..."
+msgstr ""
+
+# cf818b4df01842b3bd34c10ba0e3b6ae
+#: ../../source/about.rst:836
+msgid ""
+"`CLOUDSTACK-4475 <https://issues.apache.org/jira/browse/CLOUDSTACK-4475>`_"
+msgstr ""
+
+# 3624388961d54af49e2f6e55983d9f1f
+#: ../../source/about.rst:836
+msgid ""
+"[ZWPS] attaching an uploaded volume to a VM is always going to first primary"
+" sto..."
+msgstr ""
+
+# eed17a595cd84ec7a2a2b789a453e165
+#: ../../source/about.rst:837
+msgid ""
+"`CLOUDSTACK-4517 <https://issues.apache.org/jira/browse/CLOUDSTACK-4517>`_"
+msgstr ""
+
+# 5ddc4269a1674a9892ec7351ea9c189e
+#: ../../source/about.rst:837
+msgid ""
+"[upgrade][Vmware]Deployment of VM using centos 6.2 template registered "
+"before up..."
+msgstr ""
+
+# a65b69bed9874f82a5a5af9cc50a7cf8
+#: ../../source/about.rst:838
+msgid ""
+"`CLOUDSTACK-4536 <https://issues.apache.org/jira/browse/CLOUDSTACK-4536>`_"
+msgstr ""
+
+# 9e11de582e1b42b484d1855773bf716c
+#: ../../source/about.rst:838
+msgid ""
+"[object_store_refactor] Inconsistency in volume store location on secondary "
+"stor..."
+msgstr ""
+
+# 42a358f00373446b89e38ed05ae69cfc
+#: ../../source/about.rst:839
+msgid ""
+"`CLOUDSTACK-4568 <https://issues.apache.org/jira/browse/CLOUDSTACK-4568>`_"
+msgstr ""
+
+# e3ee2e1894e242e7a343552132de43d1
+#: ../../source/about.rst:839
+msgid "Need to add this to the release note of 4.2..."
+msgstr ""
+
+# bac89d2d04174dd191a8314b3b880cd5
+#: ../../source/about.rst:840
+msgid ""
+"`CLOUDSTACK-4587 <https://issues.apache.org/jira/browse/CLOUDSTACK-4587>`_"
+msgstr ""
+
+# 7fe14f2df06142d482e795802b1324f3
+#: ../../source/about.rst:840
+msgid ""
+"VM is failing to deploy on a Legacy zone after adding zone wide primary "
+"storage ..."
+msgstr ""
+
+# 627c74c2b2654daebee6dd087aa79133
+#: ../../source/about.rst:841
+msgid ""
+"`CLOUDSTACK-4644 <https://issues.apache.org/jira/browse/CLOUDSTACK-4644>`_"
+msgstr ""
+
+# d83e6413ba8447b8b1f1c35f16bcfcf3
+#: ../../source/about.rst:841
+msgid ""
+"Tool Tip information is not provided for the new fields which are added in "
+"4.2 (..."
+msgstr ""
+
+# 10f0c2c75a7e4724b423a9d6a740d9c3
+#: ../../source/about.rst:842
+msgid ""
+"`CLOUDSTACK-4789 <https://issues.apache.org/jira/browse/CLOUDSTACK-4789>`_"
+msgstr ""
+
+# bd54ce87a1e04392b95f08d939398f1a
+#: ../../source/about.rst:842
+msgid "Fix ResourceMetaDataManagerTest..."
+msgstr ""
+
+# 3716b08f45af446b9ee8056501301496
+#: ../../source/about.rst:843
+msgid ""
+"`CLOUDSTACK-4906 <https://issues.apache.org/jira/browse/CLOUDSTACK-4906>`_"
+msgstr ""
+
+# ded1612281a146918eea296e62e64d63
+#: ../../source/about.rst:843
+msgid "add netaddr to marvin dependency list..."
+msgstr ""
+
+# 5c7270e40c244205ac9302ace72f3a8d
+#: ../../source/about.rst:844
+msgid ""
+"`CLOUDSTACK-4918 <https://issues.apache.org/jira/browse/CLOUDSTACK-4918>`_"
+msgstr ""
+
+# d609afa506d64a69bfc12fba1d3b0e5d
+#: ../../source/about.rst:844
+msgid ""
+"VR can not be LB service provider without requiring to be source nat service"
+" pro..."
+msgstr ""
+
+# 0435d07d6cf4481882befe3bebbd0f05
+#: ../../source/about.rst:845
+msgid ""
+"`CLOUDSTACK-4951 <https://issues.apache.org/jira/browse/CLOUDSTACK-4951>`_"
+msgstr ""
+
+# cf340658226f4dd59d6dd35853d8665f
+#: ../../source/about.rst:845
+msgid "[event framework] Action events do not have UUID ..."
+msgstr ""
+
+# 82523dbe7b4a4575b37dc9aab88703ea
+#: ../../source/about.rst:846
+msgid ""
+"`CLOUDSTACK-4987 <https://issues.apache.org/jira/browse/CLOUDSTACK-4987>`_"
+msgstr ""
+
+# 13590e87501042c183865087ef0537eb
+#: ../../source/about.rst:846
+msgid ""
+"Able to add isolated network belonging to an account to a virtual machine "
+"belong..."
+msgstr ""
+
+# 91d8657d742b4323a260612029a6e357
+#: ../../source/about.rst:847
+msgid ""
+"`CLOUDSTACK-5043 <https://issues.apache.org/jira/browse/CLOUDSTACK-5043>`_"
+msgstr ""
+
+# 83a54dc712f442b49d1536331971227a
+#: ../../source/about.rst:847
+msgid "[DOC] Page number missing and words truncated in PDFs since 4.1.1..."
+msgstr ""
+
+# e91f93f9cfd34e818634c2138626d0f7
+#: ../../source/about.rst:848
+msgid ""
+"`CLOUDSTACK-5044 <https://issues.apache.org/jira/browse/CLOUDSTACK-5044>`_"
+msgstr ""
+
+# a7f4247852384d7ead204cf3b9c5da65
+#: ../../source/about.rst:848
+msgid "Configuration Framework Issue..."
+msgstr ""
+
+# dc1b03fb9b8d4e8a8f2ea2264045d16d
+#: ../../source/about.rst:849
+msgid ""
+"`CLOUDSTACK-5090 <https://issues.apache.org/jira/browse/CLOUDSTACK-5090>`_"
+msgstr ""
+
+# cc31e740ab6b4277be3264b277dedabf
+#: ../../source/about.rst:849
+msgid ""
+"Anti-Affinity: VM fails to start on a cluster belonging to a different "
+"pod...."
+msgstr ""
+
+# 7fb4c69a7f014fbe82e1afab257c866a
+#: ../../source/about.rst:850
+msgid ""
+"`CLOUDSTACK-5157 <https://issues.apache.org/jira/browse/CLOUDSTACK-5157>`_"
+msgstr ""
+
+# 0e9fad22147c4d188fd0fd859bf644bc
+#: ../../source/about.rst:850
+msgid ""
+"Loadbalancer Response should include stickiness, health check and ssl certs "
+"info..."
+msgstr ""
+
+# 81c348ffbbc94b00982f2aa7cd60890d
+#: ../../source/about.rst:851
+msgid ""
+"`CLOUDSTACK-5243 <https://issues.apache.org/jira/browse/CLOUDSTACK-5243>`_"
+msgstr ""
+
+# b369951a791b468488d788750a4e8aa8
+#: ../../source/about.rst:851
+msgid "SSVM responds with timestamp..."
+msgstr ""
+
+# 3a3909f9b93846e583178e77eeb60846
+#: ../../source/about.rst:852
+msgid ""
+"`CLOUDSTACK-5251 <https://issues.apache.org/jira/browse/CLOUDSTACK-5251>`_"
+msgstr ""
+
+# f08d19d6dda84a0d87706ddefb5b5e13
+#: ../../source/about.rst:852
+msgid ""
+"No Error message is displayed when nonexistent NFS secondary storage is "
+"added t..."
+msgstr ""
+
+# f6a5cd73f61f4e51ad5a0c9e5584dbc6
+#: ../../source/about.rst:853
+msgid ""
+"`CLOUDSTACK-5296 <https://issues.apache.org/jira/browse/CLOUDSTACK-5296>`_"
+msgstr ""
+
+# c4d451b646714ed7ae70539f56ca1a78
+#: ../../source/about.rst:853
+msgid "Add certificate chain support for NS..."
+msgstr ""
+
+# 17f24203bf114fab81b7fc9d31296637
+#: ../../source/about.rst:854
+msgid ""
+"`CLOUDSTACK-5307 <https://issues.apache.org/jira/browse/CLOUDSTACK-5307>`_"
+msgstr ""
+
+# 7d65dfb82afb4488b4b7bc47bed733fb
+#: ../../source/about.rst:854
+msgid "Same router is listed twice in router view of project..."
+msgstr ""
+
+# 193439c0e2e84fe8a4365388555d6258
+#: ../../source/about.rst:855
+msgid ""
+"`CLOUDSTACK-5324 <https://issues.apache.org/jira/browse/CLOUDSTACK-5324>`_"
+msgstr ""
+
+# 68936b04d2a6471ca555c69ab20f2af0
+#: ../../source/about.rst:855
+msgid ""
+"error message not proper when start VM fails because router reuires "
+"upgrade..."
+msgstr ""
+
+# 1f9b3473dfd8462e9b8fd44cc7c34487
+#: ../../source/about.rst:856
+msgid ""
+"`CLOUDSTACK-5342 <https://issues.apache.org/jira/browse/CLOUDSTACK-5342>`_"
+msgstr ""
+
+# ba178fa888b4488f8400ae6ff189959e
+#: ../../source/about.rst:856
+msgid "[Automation] Add NIC to virtual machine fails in KVM..."
+msgstr ""
+
+# 728d0536749a47dd9d8b6ff0c0ca1faf
+#: ../../source/about.rst:857
+msgid ""
+"`CLOUDSTACK-5359 <https://issues.apache.org/jira/browse/CLOUDSTACK-5359>`_"
+msgstr ""
+
+# 95c9a5d03b79423583edb6f57a96054a
+#: ../../source/about.rst:857
+msgid ""
+"Failed to add second VMWARE cluster on a standard vSwitch enabled zone when "
+"vCen..."
+msgstr ""
+
+# a566c5a89be64fbe85b51d43a2b4675c
+#: ../../source/about.rst:858
+msgid ""
+"`CLOUDSTACK-5373 <https://issues.apache.org/jira/browse/CLOUDSTACK-5373>`_"
+msgstr ""
+
+# a60c27d282604c91b078217b4fa11ab8
+#: ../../source/about.rst:858
+msgid "Web UI (non-English) is corrupted by text expansion..."
+msgstr ""
+
+# 39e8b0911c204eaf9b81d81ef87fcdfc
+#: ../../source/about.rst:859
+msgid ""
+"`CLOUDSTACK-5395 <https://issues.apache.org/jira/browse/CLOUDSTACK-5395>`_"
+msgstr ""
+
+# 5871613463894a71b654a8b495ec19dc
+#: ../../source/about.rst:859
+msgid ""
+"When backup snapshot fails becasue of backup.snapshot.wait time exceeding , "
+"the ..."
+msgstr ""
+
+# e5e3d2540a88469497dd4aea4fa1b13b
+#: ../../source/about.rst:860
+msgid ""
+"`CLOUDSTACK-5410 <https://issues.apache.org/jira/browse/CLOUDSTACK-5410>`_"
+msgstr ""
+
+# bb57393dec544993bdcfc2e142a4546a
+#: ../../source/about.rst:860
+msgid "Changes for tracking logs using jobid is missing in 4.3..."
+msgstr ""
+
+# f856f42384944b1a8811d1c728d13062
+#: ../../source/about.rst:861
+msgid ""
+"`CLOUDSTACK-5445 <https://issues.apache.org/jira/browse/CLOUDSTACK-5445>`_"
+msgstr ""
+
+# 88435730129a4c4baad8f056f840a058
+#: ../../source/about.rst:861
+msgid "DeleteImageStoreCmd does not use storage plugins to delete storage..."
+msgstr ""
+
+# 5613fc02af644d8b92ed4590ed26f0ea
+#: ../../source/about.rst:862
+msgid ""
+"`CLOUDSTACK-5446 <https://issues.apache.org/jira/browse/CLOUDSTACK-5446>`_"
+msgstr ""
+
+# 96a91d3d3e8d40f9a399b6903884b104
+#: ../../source/about.rst:862
+msgid ""
+"KVM-Secondary Store down-Even after secondary store is brought back up after"
+" bei..."
+msgstr ""
+
+# 4e16958e96fd4b938bfe66c84cf22a8b
+#: ../../source/about.rst:863
+msgid ""
+"`CLOUDSTACK-5463 <https://issues.apache.org/jira/browse/CLOUDSTACK-5463>`_"
+msgstr ""
+
+# 624d8a235086448688b864236accf06e
+#: ../../source/about.rst:863
+msgid "Hyper-V does not report stopped VMs..."
+msgstr ""
+
+# 416fe11a99c645bc8264cdd691d79b53
+#: ../../source/about.rst:864
+msgid ""
+"`CLOUDSTACK-5474 <https://issues.apache.org/jira/browse/CLOUDSTACK-5474>`_"
+msgstr ""
+
+# 6625af56068442ab8097eb138aac18eb
+#: ../../source/about.rst:864
+msgid ""
+"EventBus: RabbitMQ provider expects password to be stored in plain text...."
+msgstr ""
+
+# 64b73b515923418596a64ac98e0e7a0a
+#: ../../source/about.rst:865
+msgid ""
+"`CLOUDSTACK-5475 <https://issues.apache.org/jira/browse/CLOUDSTACK-5475>`_"
+msgstr ""
+
+# 21783847544046bd9ea9c93f04d4f61a
+#: ../../source/about.rst:865
+msgid ""
+"cluster.cpu/(memory).allocated.capacity.disablethreshold is getting "
+"displayed mu..."
+msgstr ""
+
+# 54c52ae2b93f4ef893401ca37514447c
+#: ../../source/about.rst:866
+msgid ""
+"`CLOUDSTACK-5479 <https://issues.apache.org/jira/browse/CLOUDSTACK-5479>`_"
+msgstr ""
+
+# bb342afe327640d2b237bdd0289f94db
+#: ../../source/about.rst:866
+msgid ""
+"Upgrading service offering of stopped vm should release the reserved "
+"capacity of..."
+msgstr ""
+
+# d046e0f9eec9447b819802a246626b24
+#: ../../source/about.rst:867
+msgid ""
+"`CLOUDSTACK-5482 <https://issues.apache.org/jira/browse/CLOUDSTACK-5482>`_"
+msgstr ""
+
+# 9a00471a35354d9fa26f18d260deafa4
+#: ../../source/about.rst:867
+msgid ""
+"Vmware - When nfs was down for about 1 hour , when snapshots were in "
+"progress , ..."
+msgstr ""
+
+# 3b8323aba4a74e2eac2ea540ff313102
+#: ../../source/about.rst:868
+msgid ""
+"`CLOUDSTACK-5488 <https://issues.apache.org/jira/browse/CLOUDSTACK-5488>`_"
+msgstr ""
+
+# bd0384b318af4d34bafa6b7819777dc3
+#: ../../source/about.rst:868
+msgid ""
+"KVM:agent is still in stopped state even after host recovered from sudddent "
+"powe..."
+msgstr ""
+
+# bd5fc0c9c94b415183ca576d0c7a925e
+#: ../../source/about.rst:869
+msgid ""
+"`CLOUDSTACK-5504 <https://issues.apache.org/jira/browse/CLOUDSTACK-5504>`_"
+msgstr ""
+
+# 5dc82178373345ecaa20a4ee2c0e0396
+#: ../../source/about.rst:869
+msgid ""
+"Vmware-Primary store unavailable for 10 mts - All snapshot tasks reported "
+"failur..."
+msgstr ""
+
+# 7297df0aba5f4338bdf8b43c1201789b
+#: ../../source/about.rst:870
+msgid ""
+"`CLOUDSTACK-5512 <https://issues.apache.org/jira/browse/CLOUDSTACK-5512>`_"
+msgstr ""
+
+# 24ed8f480cd0491aaa65fd0db5523a6c
+#: ../../source/about.rst:870
+msgid ""
+"template format name checking is crude and doesn't work with advanced "
+"URLs..."
+msgstr ""
+
+# e1c75c252cc0409fa2e4e3651b18faad
+#: ../../source/about.rst:871
+msgid ""
+"`CLOUDSTACK-5536 <https://issues.apache.org/jira/browse/CLOUDSTACK-5536>`_"
+msgstr ""
+
+# 59560ce9ab304397ac8289ab38b1ff15
+#: ../../source/about.rst:871
+msgid ""
+"Restarting cloudstack service with template download in progress creates "
+"redunda..."
+msgstr ""
+
+# 30a0c7b88bf24f809b1dbd0820bc92a0
+#: ../../source/about.rst:872
+msgid ""
+"`CLOUDSTACK-5546 <https://issues.apache.org/jira/browse/CLOUDSTACK-5546>`_"
+msgstr ""
+
+# 749e0a2d95424c2f8d4c635b21bbaf27
+#: ../../source/about.rst:872
+msgid "Extra tab for adding rules displayed for non-elb networks..."
+msgstr ""
+
+# f40bf3e0be3a4ee1b73252a0aa103027
+#: ../../source/about.rst:873
+msgid ""
+"`CLOUDSTACK-5550 <https://issues.apache.org/jira/browse/CLOUDSTACK-5550>`_"
+msgstr ""
+
+# 72c05501758c4320bda5ab7e102c6942
+#: ../../source/about.rst:873
+msgid "UI - Api key and secret key not fully visible in user detail view...."
+msgstr ""
+
+# 52e58fd9dee44fe8959ffd9ac2f63893
+#: ../../source/about.rst:874
+msgid ""
+"`CLOUDSTACK-5561 <https://issues.apache.org/jira/browse/CLOUDSTACK-5561>`_"
+msgstr ""
+
+# a93eb88abebc4a32b9593305d9138a2a
+#: ../../source/about.rst:874
+msgid "support of multiple nics for VR running in HyperV..."
+msgstr ""
+
+# b237a2ea48dc475facdfffa7f1ef5a8b
+#: ../../source/about.rst:875
+msgid ""
+"`CLOUDSTACK-5563 <https://issues.apache.org/jira/browse/CLOUDSTACK-5563>`_"
+msgstr ""
+
+# 3fdfd4e6cbb04986aea0792d77775482
+#: ../../source/about.rst:875
+msgid "path field is set to null in volumes table ..."
+msgstr ""
+
+# 4f67d4f6c79d4400b14c5a23475bf6e8
+#: ../../source/about.rst:876
+msgid ""
+"`CLOUDSTACK-5576 <https://issues.apache.org/jira/browse/CLOUDSTACK-5576>`_"
+msgstr ""
+
+# b2597bb2adc64d02a7d154873d9fe394
+#: ../../source/about.rst:876
+msgid ""
+"RemoteVPNonVPC : Label needs to be changed to \"Enable Remote Access "
+"VPN\"..."
+msgstr ""
+
+# aa8b32e0b03e4932b2b9b5408fd7e34b
+#: ../../source/about.rst:877
+msgid ""
+"`CLOUDSTACK-5583 <https://issues.apache.org/jira/browse/CLOUDSTACK-5583>`_"
+msgstr ""
+
+# 95f46eaf28c44d6eb55b48db40175cab
+#: ../../source/about.rst:877
+msgid ""
+"vmopsSnapshot plug-in (XenServer) does not return an error when it should..."
+msgstr ""
+
+# 4096cb6d70a446d5a75364034b35cbae
+#: ../../source/about.rst:878
+msgid ""
+"`CLOUDSTACK-5600 <https://issues.apache.org/jira/browse/CLOUDSTACK-5600>`_"
+msgstr ""
+
+# 56a25ad0e47b487595223949df219d77
+#: ../../source/about.rst:878
+msgid ""
+"Xenserver - After HA , CPVM's disk is corrupted resulting in CPVM being "
+"stuck in..."
+msgstr ""
+
+# 4422a2550393446aadcf3566bfeb529b
+#: ../../source/about.rst:879
+msgid ""
+"`CLOUDSTACK-5616 <https://issues.apache.org/jira/browse/CLOUDSTACK-5616>`_"
+msgstr ""
+
+# 503356c6579848508844126696d8f8f7
+#: ../../source/about.rst:879
+msgid ""
+"[DBHA]:There is no way to know to which DB is the CS writing in the case of "
+"DBHA..."
+msgstr ""
+
+# 9e90b6202eea4acd89fe42fe9c4cb645
+#: ../../source/about.rst:880
+msgid ""
+"`CLOUDSTACK-5632 <https://issues.apache.org/jira/browse/CLOUDSTACK-5632>`_"
+msgstr ""
+
+# e3237f8e610b4a0eae7c54f0b726c91f
+#: ../../source/about.rst:880
+msgid ""
+"[Automation] XenServer - Template deletion fails with error \"Please specify"
+" a te..."
+msgstr ""
+
+# 6cf6d3fa8bba4e92bc9e92457b2255a5
+#: ../../source/about.rst:881
+msgid ""
+"`CLOUDSTACK-5645 <https://issues.apache.org/jira/browse/CLOUDSTACK-5645>`_"
+msgstr ""
+
+# b6270bd700634ffa8cc763edcfe41978
+#: ../../source/about.rst:881
+msgid ""
+"Agent manager doesn't need to be aware of vms and their relationship to "
+"resource..."
+msgstr ""
+
+# 3c3ad906781d4d7eb90e7a0ac4bfe78b
+#: ../../source/about.rst:882
+msgid ""
+"`CLOUDSTACK-5673 <https://issues.apache.org/jira/browse/CLOUDSTACK-5673>`_"
+msgstr ""
+
+# f49c861d702b4d0bbd22b30026798d12
+#: ../../source/about.rst:882
+msgid ""
+"[Hyper-V] Default IP address never configured on eth0 with default CentOS "
+"templa..."
+msgstr ""
+
+# a77ccae93fb240e4a299a9d5fb73cac1
+#: ../../source/about.rst:883
+msgid ""
+"`CLOUDSTACK-5685 <https://issues.apache.org/jira/browse/CLOUDSTACK-5685>`_"
+msgstr ""
+
+# e366f576f3d84e0a8ac9911d821cd60f
+#: ../../source/about.rst:883
+msgid ""
+"[Vmsync] - When VR is rebooted outside of cloudstack , there is no change in"
+" sta..."
+msgstr ""
+
+# 06998b79062b4c16bb1586460fa7cd0c
+#: ../../source/about.rst:884
+msgid ""
+"`CLOUDSTACK-5700 <https://issues.apache.org/jira/browse/CLOUDSTACK-5700>`_"
+msgstr ""
+
+# 1df0f7424f63415b882665736fedf388
+#: ../../source/about.rst:884
+msgid "[Vmsync] - kvm- \"paused\" state of Vm is not synced to CS...."
+msgstr ""
+
+# 0b5b01b4a3594d7f99e0e18fc151886e
+#: ../../source/about.rst:885
+msgid ""
+"`CLOUDSTACK-5719 <https://issues.apache.org/jira/browse/CLOUDSTACK-5719>`_"
+msgstr ""
+
+# db94d6fce45942f98f2bd5650af19912
+#: ../../source/about.rst:885
+msgid ""
+"[UI] Not listing shared network offerings tagged on second physical "
+"network..."
+msgstr ""
+
+# db3c140e162944b9b925691a5f5f165c
+#: ../../source/about.rst:886
+msgid ""
+"`CLOUDSTACK-5724 <https://issues.apache.org/jira/browse/CLOUDSTACK-5724>`_"
+msgstr ""
+
+# ba56251e49954f0eb4c7092a2c1441c5
+#: ../../source/about.rst:886
+msgid ""
+"Console Proxy View - when using ctl c , errors seen on the console proxy "
+"view...."
+msgstr ""
+
+# 82e782ed6c7747728ecf0dcbe9151870
+#: ../../source/about.rst:887
+msgid ""
+"`CLOUDSTACK-5743 <https://issues.apache.org/jira/browse/CLOUDSTACK-5743>`_"
+msgstr ""
+
+# 8f3791cf1de843338d1843291860a9d9
+#: ../../source/about.rst:887
+msgid ""
+"Download ROOT Volume when the VM is in stopped state is failing with "
+"\"Forbidden..."
+msgstr ""
+
+# aea2f8353f8e4488af01cfc49ddb48e4
+#: ../../source/about.rst:888
+msgid ""
+"`CLOUDSTACK-5744 <https://issues.apache.org/jira/browse/CLOUDSTACK-5744>`_"
+msgstr ""
+
+# 36cce736e0ce4968b53c8de3e67807d8
+#: ../../source/about.rst:888
+msgid ""
+"[Hyper-v] White screen on console window when more than two console sessions"
+" are..."
+msgstr ""
+
+# 94c9d86e67544498b08cdd8416046442
+#: ../../source/about.rst:889
+msgid ""
+"`CLOUDSTACK-5753 <https://issues.apache.org/jira/browse/CLOUDSTACK-5753>`_"
+msgstr ""
+
+# 02a9ed3fef294e9db4fd6900485b1961
+#: ../../source/about.rst:889
+msgid ""
+"[Hyper-v] ConsoleProxyLoadReportCommand does not honor the default value of "
+"cons..."
+msgstr ""
+
+# 88a6ed8122da496b8a15ece9b1498aaf
+#: ../../source/about.rst:890
+msgid ""
+"`CLOUDSTACK-5762 <https://issues.apache.org/jira/browse/CLOUDSTACK-5762>`_"
+msgstr ""
+
+# 1bb3479127b947a89f8c923a0c6e1bcb
+#: ../../source/about.rst:890
+msgid ""
+"[dynamic compute offerings]UI change required for select compute offerinngs"
+" in ..."
+msgstr ""
+
+# 4462bf458b894524833e0d8bcba45a17
+#: ../../source/about.rst:891
+msgid ""
+"`CLOUDSTACK-5785 <https://issues.apache.org/jira/browse/CLOUDSTACK-5785>`_"
+msgstr ""
+
+# 5069ef72c09e46ad8084b82c03fc8c56
+#: ../../source/about.rst:891
+msgid "VM display name cell not updated upon detaching volume from VM..."
+msgstr ""
+
+# db8ae3f440cf4455b2f02327015d1c4a
+#: ../../source/about.rst:892
+msgid ""
+"`CLOUDSTACK-5794 <https://issues.apache.org/jira/browse/CLOUDSTACK-5794>`_"
+msgstr ""
+
+# c232b4e8b81346c1a93cf0012934f468
+#: ../../source/about.rst:892
+msgid ""
+"[Hyper-v] Specify username and domain name together in the username field "
+"while ..."
+msgstr ""
+
+# 8ae3c469336b4ec6965d854eff822684
+#: ../../source/about.rst:893
+msgid ""
+"`CLOUDSTACK-5798 <https://issues.apache.org/jira/browse/CLOUDSTACK-5798>`_"
+msgstr ""
+
+# 22a0516940a644939b1737f0cd8dcd35
+#: ../../source/about.rst:893
+msgid ""
+"While attaching a disk to WIN2012 VM with xencenter tools installed got "
+"error as..."
+msgstr ""
+
+# 43dd1a41dd4e44239b2e478ffded4694
+#: ../../source/about.rst:894
+msgid ""
+"`CLOUDSTACK-5800 <https://issues.apache.org/jira/browse/CLOUDSTACK-5800>`_"
+msgstr ""
+
+# a2f85d50eee44372bc2bcf806cca17e9
+#: ../../source/about.rst:894
+msgid ""
+"While creating a VM from template (which is created based on existing newly "
+"crea..."
+msgstr ""
+
+# 915cf844a6854358bf6e861350b1479c
+#: ../../source/about.rst:895
+msgid ""
+"`CLOUDSTACK-5807 <https://issues.apache.org/jira/browse/CLOUDSTACK-5807>`_"
+msgstr ""
+
+# 0897ce4abcbb4033859f0449e928125c
+#: ../../source/about.rst:895
+msgid "Problem with shared datastore in VMware cluster with only one host..."
+msgstr ""
+
+# 6765a9fd4b0c4db79eb10d7a4dc133b5
+#: ../../source/about.rst:896
+msgid ""
+"`CLOUDSTACK-5809 <https://issues.apache.org/jira/browse/CLOUDSTACK-5809>`_"
+msgstr ""
+
+# 464ec622e70243ffbc5db1f14e156619
+#: ../../source/about.rst:896
+msgid ""
+"Not able to deploy Vm becasue of crossing pool.storage.allocate "
+"d.capacity.disab..."
+msgstr ""
+
+# 4bccd233b1d849ceba642ed120606dec
+#: ../../source/about.rst:897
+msgid ""
+"`CLOUDSTACK-5822 <https://issues.apache.org/jira/browse/CLOUDSTACK-5822>`_"
+msgstr ""
+
+# c54904d46b724fd091d64354e6dafccd
+#: ../../source/about.rst:897
+msgid "ssh keypairs are removed after rebooting vm..."
+msgstr ""
+
+# 08557c1b20a94ee18bde7c1f7a406b42
+#: ../../source/about.rst:898
+msgid ""
+"`CLOUDSTACK-5834 <https://issues.apache.org/jira/browse/CLOUDSTACK-5834>`_"
+msgstr ""
+
+# 01af65e60d524900bf08a1d70ea42909
+#: ../../source/about.rst:898
+msgid ""
+"[upgrade]Error while collecting disk stats from : You gave an invalid object"
+" ref..."
+msgstr ""
+
+# b5574ef4bb82434786636036da92a5f8
+#: ../../source/about.rst:899
+msgid ""
+"`CLOUDSTACK-5836 <https://issues.apache.org/jira/browse/CLOUDSTACK-5836>`_"
+msgstr ""
+
+# 99faa2cf0c4942818e491b207c78e448
+#: ../../source/about.rst:899
+msgid ""
+"When tried to reverting back to (disk attached)quiesced vm snapshot, got "
+"error a..."
+msgstr ""
+
+# 42dd7cded1c846f397c9bc3f0985396d
+#: ../../source/about.rst:900
+msgid ""
+"`CLOUDSTACK-5843 <https://issues.apache.org/jira/browse/CLOUDSTACK-5843>`_"
+msgstr ""
+
+# 9c70b4b9b84442258aca13062148eebf
+#: ../../source/about.rst:900
+msgid ""
+"registering templates/isos should be either async or changed to non-"
+"blocking..."
+msgstr ""
+
+# 557610d31c2648778eb586d3c355c51c
+#: ../../source/about.rst:901
+msgid ""
+"`CLOUDSTACK-5845 <https://issues.apache.org/jira/browse/CLOUDSTACK-5845>`_"
+msgstr ""
+
+# f76b8a93412140778a09313a2e392d85
+#: ../../source/about.rst:901
+msgid ""
+"[doc] Document Heterogeneous Secondary Storage Not Supported in Region..."
+msgstr ""
+
+# 11001f7cefc544abac72c8bcf221d2d1
+#: ../../source/about.rst:902
+msgid ""
+"`CLOUDSTACK-5847 <https://issues.apache.org/jira/browse/CLOUDSTACK-5847>`_"
+msgstr ""
+
+# aa11b3c98b494677ad279807b1fc16dd
+#: ../../source/about.rst:902
+msgid ""
+"[Hyper-V] [doc] Document creation of external vswitch for Hyper-V 2012 R2 "
+"(unlik..."
+msgstr ""
+
+# 49f6b506e48043d9bf28b1dcccf52cdb
+#: ../../source/about.rst:903
+msgid ""
+"`CLOUDSTACK-5855 <https://issues.apache.org/jira/browse/CLOUDSTACK-5855>`_"
+msgstr ""
+
+# 676f457929c74bcc83ebb6f37c4a72c9
+#: ../../source/about.rst:903
+msgid ""
+"Contrail: Slave compute host restarts when the master compute host is "
+"changed to..."
+msgstr ""
+
+# d71c8b73113d48659a5e52ebc701bfda
+#: ../../source/about.rst:904
+msgid ""
+"`CLOUDSTACK-5862 <https://issues.apache.org/jira/browse/CLOUDSTACK-5862>`_"
+msgstr ""
+
+# ec0d4184509843598a6b566774cf1bb1
+#: ../../source/about.rst:904
+msgid ""
+"Template life cycle needs to be changed based on references of existing VMs "
+"to t..."
+msgstr ""
+
+# 7069f2c006ad4dd7b8ddd65885f32eb6
+#: ../../source/about.rst:905
+msgid ""
+"`CLOUDSTACK-5866 <https://issues.apache.org/jira/browse/CLOUDSTACK-5866>`_"
+msgstr ""
+
+# 332622ca747448a9b638712083439222
+#: ../../source/about.rst:905
+msgid "Remove maven profile used to configure zone..."
+msgstr ""
+
+# e51f3dcbc6ad473ab41bf22cf33e9af6
+#: ../../source/about.rst:906
+msgid ""
+"`CLOUDSTACK-5876 <https://issues.apache.org/jira/browse/CLOUDSTACK-5876>`_"
+msgstr ""
+
+# 073abbbb04284c9f942e87a688fc2086
+#: ../../source/about.rst:906
+msgid ""
+"Contrail: After vrouter restart agent doesnt have info about the Network..."
+msgstr ""
+
+# af92fe91418d4306988f665712ee4fa8
+#: ../../source/about.rst:907
+msgid ""
+"`CLOUDSTACK-5879 <https://issues.apache.org/jira/browse/CLOUDSTACK-5879>`_"
+msgstr ""
+
+# 12bc62b3dffb44f79ad5d84740d311f0
+#: ../../source/about.rst:907
+msgid ""
+"Document on how to use RabbitMq event bus with spring modularisation done in"
+" 4.3..."
+msgstr ""
+
+# 86d3efe5f7fd4d30889a92587432df20
+#: ../../source/about.rst:908
+msgid ""
+"`CLOUDSTACK-5897 <https://issues.apache.org/jira/browse/CLOUDSTACK-5897>`_"
+msgstr ""
+
+# 6b138f81eac4489183c7080180eb46b9
+#: ../../source/about.rst:908
+msgid "Remove OVM in add cluster drop down list..."
+msgstr ""
+
+# 83d9adac0ad34fad8b8a2d44642f2ef6
+#: ../../source/about.rst:909
+msgid ""
+"`CLOUDSTACK-5907 <https://issues.apache.org/jira/browse/CLOUDSTACK-5907>`_"
+msgstr ""
+
+# 673551c263a64a458cc645ced6619bbf
+#: ../../source/about.rst:909
+msgid "KVM/CLVM volumes are shown as Ovm hypervisor..."
+msgstr ""
+
+# f0935a17a83b44e8a14d5b629230c171
+#: ../../source/about.rst:910
+msgid ""
+"`CLOUDSTACK-5908 <https://issues.apache.org/jira/browse/CLOUDSTACK-5908>`_"
+msgstr ""
+
+# cf6c3725ca244469ba5b19dc5577c630
+#: ../../source/about.rst:910
+msgid "Fail to add VXLAN network to instance..."
+msgstr ""
+
+# b0b635e252684125a14d7e15dcd59902
+#: ../../source/about.rst:911
+msgid ""
+"`CLOUDSTACK-5910 <https://issues.apache.org/jira/browse/CLOUDSTACK-5910>`_"
+msgstr ""
+
+# 58450a277eeb406fa6c30acabe92d166
+#: ../../source/about.rst:911
+msgid "mark the LDAP user as imported from LDAP..."
+msgstr ""
+
+# af6ef2f4abdd4741909ee24de85933f8
+#: ../../source/about.rst:912
+msgid ""
+"`CLOUDSTACK-5920 <https://issues.apache.org/jira/browse/CLOUDSTACK-5920>`_"
+msgstr ""
+
+# ce45e6f1e80b4cc3b61fd9b686297610
+#: ../../source/about.rst:912
+msgid "CloudStack IAM Plugin feature..."
+msgstr ""
+
+# e8ffcbe7cdf84907b6185e6ffca4ba01
+#: ../../source/about.rst:913
+msgid ""
+"`CLOUDSTACK-5926 <https://issues.apache.org/jira/browse/CLOUDSTACK-5926>`_"
+msgstr ""
+
+# d48cd789b41c4728a9dcc41f475f286e
+#: ../../source/about.rst:913
+msgid "[Doc] Create 4.3 Release Notes..."
+msgstr ""
+
+# e0d5e76950f34c538fe229e39417360f
+#: ../../source/about.rst:914
+msgid ""
+"`CLOUDSTACK-5931 <https://issues.apache.org/jira/browse/CLOUDSTACK-5931>`_"
+msgstr ""
+
+# 90cc9eb2416f4026b198f7ebc9796f49
+#: ../../source/about.rst:914
+msgid "Hyper-V agent does not release logon handle..."
+msgstr ""
+
+# e5507b4683aa4807b841e8e1546de3c6
+#: ../../source/about.rst:915
+msgid ""
+"`CLOUDSTACK-5932 <https://issues.apache.org/jira/browse/CLOUDSTACK-5932>`_"
+msgstr ""
+
+# 6569531c2301433db4def28a6271e669
+#: ../../source/about.rst:915
+msgid ""
+"SystemVM scripts: the iso download urls need updating as current ones are "
+"obsole..."
+msgstr ""
+
+# e8814954b4ee4b6db3d8be53977b4aca
+#: ../../source/about.rst:916
+msgid ""
+"`CLOUDSTACK-5933 <https://issues.apache.org/jira/browse/CLOUDSTACK-5933>`_"
+msgstr ""
+
+# 5ce5bc961b344c7da43172ffac8a2253
+# 8ab076108bf845b8b8d4da4a4c85aee9
+# d9c1f79d30b04159a65aa5d42e1ecba3
+#: ../../source/about.rst:916 ../../source/about.rst:917
+#: ../../source/about.rst:918
+msgid "Problem with VMware snapshot when datastore has a space in its name..."
+msgstr ""
+
+# bb833b720da84718b19e2af7067edfd0
+#: ../../source/about.rst:917
+msgid ""
+"`CLOUDSTACK-5934 <https://issues.apache.org/jira/browse/CLOUDSTACK-5934>`_"
+msgstr ""
+
+# 85739de24903447faf3b0030fb46b943
+#: ../../source/about.rst:918
+msgid ""
+"`CLOUDSTACK-5935 <https://issues.apache.org/jira/browse/CLOUDSTACK-5935>`_"
+msgstr ""
+
+# e0bc47e0f8694fdc85fa6dc8ee1bbe3c
+#: ../../source/about.rst:919
+msgid ""
+"`CLOUDSTACK-5947 <https://issues.apache.org/jira/browse/CLOUDSTACK-5947>`_"
+msgstr ""
+
+# f2281071edbc412c82d3970f6253ba60
+#: ../../source/about.rst:919
+msgid "Exception for getRootDir.. NFSStorage when running with Simulator..."
+msgstr ""
+
+# 3abd5466824844ff86a35499da50b2fd
+#: ../../source/about.rst:920
+msgid ""
+"`CLOUDSTACK-5951 <https://issues.apache.org/jira/browse/CLOUDSTACK-5951>`_"
+msgstr ""
+
+# 3c41283de3eb4514b7d09dfda960030d
+#: ../../source/about.rst:920
+msgid "Fix base.py for Dynamic compute offerings..."
+msgstr ""
+
+# 44ccddcb447c4ddbb3e68119bf807c3a
+#: ../../source/about.rst:921
+msgid ""
+"`CLOUDSTACK-5954 <https://issues.apache.org/jira/browse/CLOUDSTACK-5954>`_"
+msgstr ""
+
+# edf36e9ef5494869a23f559b1e9de0c1
+#: ../../source/about.rst:921
+msgid "update-ssl.png missing from docs..."
+msgstr ""
+
+# 810e7eb9bd154b61acd8aeef915cf762
+#: ../../source/about.rst:922
+msgid ""
+"`CLOUDSTACK-5955 <https://issues.apache.org/jira/browse/CLOUDSTACK-5955>`_"
+msgstr ""
+
+# 8c00a4c01ed64a1e8d8433e03912a88c
+#: ../../source/about.rst:922
+msgid "vm stuck in migrating if mgmt server is restarted..."
+msgstr ""
+
+# fc4396ab18374d5592ce88fcf816c49a
+#: ../../source/about.rst:923
+msgid ""
+"`CLOUDSTACK-5962 <https://issues.apache.org/jira/browse/CLOUDSTACK-5962>`_"
+msgstr ""
+
+# 6f0989d4b6ac44078841675417a8bb84
+#: ../../source/about.rst:923
+msgid ""
+"Value of Global parameter \"custom.diskoffering.size.min\" is not reflected "
+"in UI ..."
+msgstr ""
+
+# 81aa4406e0f5476d84e4322a63a0a99e
+#: ../../source/about.rst:924
+msgid ""
+"`CLOUDSTACK-5972 <https://issues.apache.org/jira/browse/CLOUDSTACK-5972>`_"
+msgstr ""
+
+# d04402ca216d4b11859b53357ed8c6b1
+#: ../../source/about.rst:924
+msgid "[DOC] Service monitoring enable/disable from global setting..."
+msgstr ""
+
+# cbeeb934235046539974f28b2881a7fa
+#: ../../source/about.rst:925
+msgid ""
+"`CLOUDSTACK-5976 <https://issues.apache.org/jira/browse/CLOUDSTACK-5976>`_"
+msgstr ""
+
+# f93bd455107d4154afa2fefa764f37f1
+#: ../../source/about.rst:925
+msgid ""
+"[upgrade]Typo in \"ssh_keypairs\" table's foreign key constraints on the "
+"Upgraded ..."
+msgstr ""
+
+# db65963bc9b84ceea6627adb7d3cd8d0
+#: ../../source/about.rst:926
+msgid ""
+"`CLOUDSTACK-5982 <https://issues.apache.org/jira/browse/CLOUDSTACK-5982>`_"
+msgstr ""
+
+# 64662e57b5ff48f4bc2fbfd59b59f192
+#: ../../source/about.rst:926
+msgid "Fix response name for assign and unassign cert from lb..."
+msgstr ""
+
+# 6ae5d3809aa0448badc6e227607e10c3
+#: ../../source/about.rst:927
+msgid ""
+"`CLOUDSTACK-5984 <https://issues.apache.org/jira/browse/CLOUDSTACK-5984>`_"
+msgstr ""
+
+# 28c77a358f7b4e47af7d139884cf09d3
+#: ../../source/about.rst:927
+msgid "addvmwaredc API call is not documented ..."
+msgstr ""
+
+# fe5633aa4b02454d83cd7cfcc2654bd1
+#: ../../source/about.rst:928
+msgid ""
+"`CLOUDSTACK-5990 <https://issues.apache.org/jira/browse/CLOUDSTACK-5990>`_"
+msgstr ""
+
+# e5fd89285b494c0db3e14c75c4b16565
+#: ../../source/about.rst:928
+msgid "[UI]: search by username while importing ldap users..."
+msgstr ""
+
+# 35842deb54f9451e8056a1d3261fb279
+#: ../../source/about.rst:929
+msgid ""
+"`CLOUDSTACK-5991 <https://issues.apache.org/jira/browse/CLOUDSTACK-5991>`_"
+msgstr ""
+
+# 194b2ee3ce804e3db87132f3f72efe93
+#: ../../source/about.rst:929
+msgid "[UI]Infinite scrolling should be enabled to the Ldap user add page..."
+msgstr ""
+
+# e7e0289989fc4f838a776baab7d6dfcf
+#: ../../source/about.rst:930
+msgid ""
+"`CLOUDSTACK-5992 <https://issues.apache.org/jira/browse/CLOUDSTACK-5992>`_"
+msgstr ""
+
+# 1289a464c7ef4a4f9213bb57498c2f63
+#: ../../source/about.rst:930
+msgid ""
+"[Upgrade] default values of configuraiton parameters in configuration table "
+"are ..."
+msgstr ""
+
+# af62f0ef9596472c8f7f6b5c72205d1d
+#: ../../source/about.rst:931
+msgid ""
+"`CLOUDSTACK-6032 <https://issues.apache.org/jira/browse/CLOUDSTACK-6032>`_"
+msgstr ""
+
+# 461160a486b844b4861d12b3b539d16a
+#: ../../source/about.rst:931
+msgid ""
+"[VmScaleup]service offering id is not getting changed in usage_vm_instance "
+"table..."
+msgstr ""
+
+# dea36e7d08aa4791b6418f852095c302
+#: ../../source/about.rst:932
+msgid ""
+"`CLOUDSTACK-6043 <https://issues.apache.org/jira/browse/CLOUDSTACK-6043>`_"
+msgstr ""
+
+# c098010713234572aaa92f97fb50df6a
+#: ../../source/about.rst:932
+msgid "VMware detaching volume fails if volume has snapshots..."
+msgstr ""
+
+# b43004dda81e4014a5f0763b3ee3ccd5
+#: ../../source/about.rst:933
+msgid ""
+"`CLOUDSTACK-6053 <https://issues.apache.org/jira/browse/CLOUDSTACK-6053>`_"
+msgstr ""
+
+# 462dde74d1a9466db759fb7520cc6794
+#: ../../source/about.rst:933
+msgid ""
+"While adding smb as primary or secondary the password should be uri "
+"encoded..."
+msgstr ""
+
+# 130598f509cb4eee834a16fe019e32ce
+#: ../../source/about.rst:934
+msgid ""
+"`CLOUDSTACK-6069 <https://issues.apache.org/jira/browse/CLOUDSTACK-6069>`_"
+msgstr ""
+
+# e90b4abd6a3043ed92c18f1bcccaf187
+#: ../../source/about.rst:934
+msgid "can't create privatgateway with vlan in a mixed network env..."
+msgstr ""
+
+# c4a32d58a29d4fc7969d992d4eb62fc9
+#: ../../source/about.rst:935
+msgid ""
+"`CLOUDSTACK-6072 <https://issues.apache.org/jira/browse/CLOUDSTACK-6072>`_"
+msgstr ""
+
+# e0e697959a864d77b79d5d86d1055894
+#: ../../source/about.rst:935
+msgid "vxlan networks not deallocating vnet ids..."
+msgstr ""
+
+# 2d01c25ad91a45cfbc6ad94aeba751de
+#: ../../source/about.rst:936
+msgid ""
+"`CLOUDSTACK-6075 <https://issues.apache.org/jira/browse/CLOUDSTACK-6075>`_"
+msgstr ""
+
+# 077f40b21a1d451da0b6551b396c2510
+#: ../../source/about.rst:936
+msgid "Increase the ram size for router service offering ..."
+msgstr ""
+
+# f71815f13a6f45048b3d93d7464ecc56
+#: ../../source/about.rst:937
+msgid ""
+"`CLOUDSTACK-124 <https://issues.apache.org/jira/browse/CLOUDSTACK-124>`_"
+msgstr ""
+
+# c403f649f6e94e6aa9fee5cb3ba8b1f9
+#: ../../source/about.rst:937
+msgid "NetworkGarbageCollector not cleaning up networks..."
+msgstr ""
+
+# bd976b9749144511a462c66dad141024
+#: ../../source/about.rst:938
+msgid ""
+"`CLOUDSTACK-231 <https://issues.apache.org/jira/browse/CLOUDSTACK-231>`_"
+msgstr ""
+
+# 7bcf2f588f364099b9aff15a97023e5b
+#: ../../source/about.rst:938
+msgid "Tag creation using special charecters ..."
+msgstr ""
+
+# deeef16b849e4d88a9ef7604e90787d4
+#: ../../source/about.rst:939
+msgid ""
+"`CLOUDSTACK-245 <https://issues.apache.org/jira/browse/CLOUDSTACK-245>`_"
+msgstr ""
+
+# 309c606e25524114b7b6800f14cf3c62
+#: ../../source/about.rst:939
+msgid "VPC ACLs are not stored and programmed consistently..."
+msgstr ""
+
+# 3ade068351834e9daea921cc0d5b1900
+#: ../../source/about.rst:940
+msgid ""
+"`CLOUDSTACK-270 <https://issues.apache.org/jira/browse/CLOUDSTACK-270>`_"
+msgstr ""
+
+# aa86fba63b3e4abda4df67eb7f18479b
+#: ../../source/about.rst:940
+msgid ""
+"Ui should not ask for a vlan range if the physical network isolation type is"
+" not..."
+msgstr ""
+
+# 6cdf64027f814affbfff2e16fff1497c
+#: ../../source/about.rst:941
+msgid ""
+"`CLOUDSTACK-300 <https://issues.apache.org/jira/browse/CLOUDSTACK-300>`_"
+msgstr ""
+
+# aa45f6e4f69c458481b07efd241e4f4e
+#: ../../source/about.rst:941
+msgid ""
+"Creation of compute offering allow combination of local storage + HA..."
+msgstr ""
+
+# 3535aeb0b68d4e8093e3ca9fa8545c8b
+#: ../../source/about.rst:942
+msgid ""
+"`CLOUDSTACK-310 <https://issues.apache.org/jira/browse/CLOUDSTACK-310>`_"
+msgstr ""
+
+# 20e7178656a3404e99304ca26d79de54
+#: ../../source/about.rst:942
+msgid "Failed to add host - Plugin error..."
+msgstr ""
+
+# adc4e3f488d449d0bb08a00d806c92ad
+#: ../../source/about.rst:943
+msgid ""
+"`CLOUDSTACK-315 <https://issues.apache.org/jira/browse/CLOUDSTACK-315>`_"
+msgstr ""
+
+# fe201a77da2d42bb8b290befa6cd7c61
+#: ../../source/about.rst:943
+msgid "Infrastructure view does not show capacity values..."
+msgstr ""
+
+# 3b73db7445e84726a621e55792a78640
+#: ../../source/about.rst:944
+msgid ""
+"`CLOUDSTACK-338 <https://issues.apache.org/jira/browse/CLOUDSTACK-338>`_"
+msgstr ""
+
+# d6cdf18645f241dc8d65a825419ce13f
+#: ../../source/about.rst:944
+msgid ""
+"Unique Names of Disk and Service Offerings in the database are prefixed with"
+" \"Cl..."
+msgstr ""
+
+# cc5ad682b94943928cb11127c683165d
+#: ../../source/about.rst:945
+msgid ""
+"`CLOUDSTACK-458 <https://issues.apache.org/jira/browse/CLOUDSTACK-458>`_"
+msgstr ""
+
+# 2c496074b8014416a60d15b6524a3c7d
+#: ../../source/about.rst:945
+msgid ""
+"xen:snapshots:Storage gc fail to clean the failed snapshot images from "
+"secondary..."
+msgstr ""
+
+# 470819855835494bb3e4b42a63762a75
+#: ../../source/about.rst:946
+msgid ""
+"`CLOUDSTACK-469 <https://issues.apache.org/jira/browse/CLOUDSTACK-469>`_"
+msgstr ""
+
+# e483a4ddc85e48b5b874ce49a0d4348a
+#: ../../source/about.rst:946
+msgid "CloudStack Documentation Landing Page has Alignment Issues..."
+msgstr ""
+
+# 8701a51097fb42cc81f778db547df9a5
+#: ../../source/about.rst:947
+msgid ""
+"`CLOUDSTACK-963 <https://issues.apache.org/jira/browse/CLOUDSTACK-963>`_"
+msgstr ""
+
+# 557c83dc7d364bc380050720275c491e
+#: ../../source/about.rst:947
+msgid ""
+"[cloud.utils.AnnotationHelper] class java.lang.Stringdoes not have a Table "
+"anno..."
+msgstr ""
+
+# 3de2d5b341cd4beeafa8ded446f144a1
+#: ../../source/about.rst:948
+msgid ""
+"`CLOUDSTACK-969 <https://issues.apache.org/jira/browse/CLOUDSTACK-969>`_"
+msgstr ""
+
+# 87b4adb2c73f4094a8b1e269a812c256
+#: ../../source/about.rst:948
+msgid ""
+"api: zone response lists vlan in it as \"vlan range of zone\" but the vlan "
+"belongs..."
+msgstr ""
+
+# 9682bf3f823f48808f399d0833c9c972
+#: ../../source/about.rst:949
+msgid ""
+"`CLOUDSTACK-1306 <https://issues.apache.org/jira/browse/CLOUDSTACK-1306>`_"
+msgstr ""
+
+# dcfc2e8792b34560bf771f465e6b5f1e
+#: ../../source/about.rst:949
+msgid ""
+"Better Error message when trying to deploy Vm by passing static Ipv4 "
+"addresses t..."
+msgstr ""
+
+# 292c51d2256f4b3cb4057ca48f853a16
+#: ../../source/about.rst:950
+msgid ""
+"`CLOUDSTACK-1432 <https://issues.apache.org/jira/browse/CLOUDSTACK-1432>`_"
+msgstr ""
+
+# 640c5559b1f848caa902512ff84b49a3
+#: ../../source/about.rst:950
+msgid "[UI] Inconsistent field names in \"Add Cluster\" dialog..."
+msgstr ""
+
+# deff00442eaf41578758a8fc6a91bc1b
+#: ../../source/about.rst:951
+msgid ""
+"`CLOUDSTACK-1471 <https://issues.apache.org/jira/browse/CLOUDSTACK-1471>`_"
+msgstr ""
+
+# e748278ea8b940809ac2c41d84709fad
+#: ../../source/about.rst:951
+msgid ""
+"Pop up window for host details/(host related operation) are not properly "
+"alligne..."
+msgstr ""
+
+# 1e1a52cced9d4fb5ae3ff2cf45118355
+#: ../../source/about.rst:952
+msgid ""
+"`CLOUDSTACK-1524 <https://issues.apache.org/jira/browse/CLOUDSTACK-1524>`_"
+msgstr ""
+
+# e1642948629845c285e6bca3af5389f9
+#: ../../source/about.rst:952
+msgid "\"White-box\" effect changes when changing value in combo box..."
+msgstr ""
+
+# 20421a8e6fb6417aafeec944e379178a
+#: ../../source/about.rst:953
+msgid ""
+"`CLOUDSTACK-1725 <https://issues.apache.org/jira/browse/CLOUDSTACK-1725>`_"
+msgstr ""
+
+# e99f7cdb2e00432385ba84a45882f52c
+#: ../../source/about.rst:953
+msgid "publican update_pot might overwrite license headers ..."
+msgstr ""
+
+# 57290580090b4de896d2ae244646b4b9
+#: ../../source/about.rst:954
+msgid ""
+"`CLOUDSTACK-1932 <https://issues.apache.org/jira/browse/CLOUDSTACK-1932>`_"
+msgstr ""
+
+# 948fa91e719a4fe29cbfa654eb39e96a
+#: ../../source/about.rst:954
+msgid ""
+"AutoScale UI documentation doesn't mention the option appears only for "
+"NetScaler..."
+msgstr ""
+
+# 99aaec54cc06481c9695a66e3c1f294b
+#: ../../source/about.rst:955
+msgid ""
+"`CLOUDSTACK-2000 <https://issues.apache.org/jira/browse/CLOUDSTACK-2000>`_"
+msgstr ""
+
+# 3d09b02f8e3f48f3b8fb0c0f54410139
+#: ../../source/about.rst:955
+msgid ""
+"CS4.1 Installation document - cloud-install-sys-tmplt command documented in "
+"wron..."
+msgstr ""
+
+# c1575fc372284702b88bec3821c72aa4
+#: ../../source/about.rst:956
+msgid ""
+"`CLOUDSTACK-2213 <https://issues.apache.org/jira/browse/CLOUDSTACK-2213>`_"
+msgstr ""
+
+# 16faf7c244484832911649754c6837a5
+#: ../../source/about.rst:956
+msgid "russian language select failure..."
+msgstr ""
+
+# 2cbc226b25a94c9685846bb61135b12a
+#: ../../source/about.rst:957
+msgid ""
+"`CLOUDSTACK-2345 <https://issues.apache.org/jira/browse/CLOUDSTACK-2345>`_"
+msgstr ""
+
+# 2833085d6922422986409770a070a809
+#: ../../source/about.rst:957
+msgid ""
+"[GSLB] deleting GSLB rules is not cleaning server info from GSLB device..."
+msgstr ""
+
+# 2614a9255d324ea4a6c8521e2da7c308
+#: ../../source/about.rst:958
+msgid ""
+"`CLOUDSTACK-2436 <https://issues.apache.org/jira/browse/CLOUDSTACK-2436>`_"
+msgstr ""
+
+# 735e7ca609f841db97fd9f95b1fa1594
+#: ../../source/about.rst:958
+msgid ""
+"Message \"You do not have any affinity groups. Please continue to the next "
+"step.\"..."
+msgstr ""
+
+# ae80ec401946455f87aaccb915d341dc
+#: ../../source/about.rst:959
+msgid ""
+"`CLOUDSTACK-2439 <https://issues.apache.org/jira/browse/CLOUDSTACK-2439>`_"
+msgstr ""
+
+# 1dd9ac498c52472a9168dcfc733dd3ca
+#: ../../source/about.rst:959
+msgid ""
+"\"Domain\" field under login page should be mandatory for the non root "
+"accounts...."
+msgstr ""
+
+# 32895ca41f6e4343a317aadd68190b71
+#: ../../source/about.rst:960
+msgid ""
+"`CLOUDSTACK-2449 <https://issues.apache.org/jira/browse/CLOUDSTACK-2449>`_"
+msgstr ""
+
+# f0595b5791524cc5ac68ceb9312451eb
+#: ../../source/about.rst:960
+msgid ""
+"Dropdown menu for action button scaleup System VM shows all service offering"
+" inc..."
+msgstr ""
+
+# 98fa68df36d64851b63eb662e8db7502
+#: ../../source/about.rst:961
+msgid ""
+"`CLOUDSTACK-2453 <https://issues.apache.org/jira/browse/CLOUDSTACK-2453>`_"
+msgstr ""
+
+# c03e069aadcf4337a206b0bfbf2ea65e
+#: ../../source/about.rst:961
+msgid ""
+"Select view dropdown under \"Network\" is listing the options in the absence"
+" of ad..."
+msgstr ""
+
+# 006f2919c94944668a59100431fd6d2f
+#: ../../source/about.rst:962
+msgid ""
+"`CLOUDSTACK-2464 <https://issues.apache.org/jira/browse/CLOUDSTACK-2464>`_"
+msgstr ""
+
+# fc200e7396e2473c8b3b16936cc3ca2e
+#: ../../source/about.rst:962
+msgid "[GSLB][UI] \"Add GSLB\" wizard doesn't prompt for \"PersistenceType\"..."
+msgstr ""
+
+# 07042e6c5b1347bca94f1246aa648969
+#: ../../source/about.rst:963
+msgid ""
+"`CLOUDSTACK-2533 <https://issues.apache.org/jira/browse/CLOUDSTACK-2533>`_"
+msgstr ""
+
+# ed2e9e8e46524fe59dcb5711469a8b10
+#: ../../source/about.rst:963
+msgid ""
+"Add Network to VM dialog should only show those network in the dropdown "
+"which ar..."
+msgstr ""
+
+# 18e1dc3644244d13a77cf9bc1db5af7d
+#: ../../source/about.rst:964
+msgid ""
+"`CLOUDSTACK-2535 <https://issues.apache.org/jira/browse/CLOUDSTACK-2535>`_"
+msgstr ""
+
+# 5750f72b3c094f7fb43f4f160b4bed53
+#: ../../source/about.rst:964
+msgid ""
+"Cleanup port-profiles that gets created on Nexus switch as part of network "
+"clean..."
+msgstr ""
+
+# 7c534d9056ee424b95d5c6f17b7b4506
+#: ../../source/about.rst:965
+msgid ""
+"`CLOUDSTACK-2559 <https://issues.apache.org/jira/browse/CLOUDSTACK-2559>`_"
+msgstr ""
+
+# 091a5c75671d4441b91c623b05129f14
+#: ../../source/about.rst:965
+msgid ""
+"[UI]Resource Name should not be present in UI as it is not available in "
+"listASA1..."
+msgstr ""
+
+# 1e567fca109b4b349a7c2c6c8284ba11
+#: ../../source/about.rst:966
+msgid ""
+"`CLOUDSTACK-2605 <https://issues.apache.org/jira/browse/CLOUDSTACK-2605>`_"
+msgstr ""
+
+# f4334ef1f3f44acc87bf1003f0d6567a
+#: ../../source/about.rst:966
+msgid ""
+"Add Network to VM Command button should not be displayed for VMs belonging "
+"to B..."
+msgstr ""
+
+# 08bd353b6429441f9b90c69b1251d4da
+#: ../../source/about.rst:967
+msgid ""
+"`CLOUDSTACK-2697 <https://issues.apache.org/jira/browse/CLOUDSTACK-2697>`_"
+msgstr ""
+
+# 2bc76e4035cb441abfd5d6d1b1f608b6
+#: ../../source/about.rst:967
+msgid ""
+"cluster id in alert message is null {alertType:: 1 // dataCenterId:: 1 // "
+"podId:..."
+msgstr ""
+
+# 04ef32f9ef79467e8f69750fd720ffb1
+#: ../../source/about.rst:968
+msgid ""
+"`CLOUDSTACK-2714 <https://issues.apache.org/jira/browse/CLOUDSTACK-2714>`_"
+msgstr ""
+
+# d7f48ef417104458a850899d7081dac2
+#: ../../source/about.rst:968
+msgid "Setting tab should not be visible for user accounts ..."
+msgstr ""
+
+# 67847a92b9bf4060bdb04270e6739a1f
+#: ../../source/about.rst:969
+msgid ""
+"`CLOUDSTACK-2951 <https://issues.apache.org/jira/browse/CLOUDSTACK-2951>`_"
+msgstr ""
+
+# bd9915a7a5064c1cbbedff49c46a74b1
+#: ../../source/about.rst:969
+msgid ""
+"[UI][Mixed-Zone-Management] during \"add Instance\" wizard, listTemplates "
+"API is n..."
+msgstr ""
+
+# 39d2c4a20daf4f468c049514cee70006
+#: ../../source/about.rst:970
+msgid ""
+"`CLOUDSTACK-2993 <https://issues.apache.org/jira/browse/CLOUDSTACK-2993>`_"
+msgstr ""
+
+# 0e21629701ff4572ab3334c0d8992d31
+#: ../../source/about.rst:970
+msgid ""
+"[PortableIPRange] remove some of the unused columns if they are not required"
+" fro..."
+msgstr ""
+
+# 79fd650e0ffc4ec38fe40b80e402d26f
+#: ../../source/about.rst:971
+msgid ""
+"`CLOUDSTACK-3025 <https://issues.apache.org/jira/browse/CLOUDSTACK-3025>`_"
+msgstr ""
+
+# 4cbd966303574dc48701d6228f09fcf6
+#: ../../source/about.rst:971
+msgid ""
+"The page and pagesize parameters are not working in ListCfgsByCmds with "
+"zoneid s..."
+msgstr ""
+
+# df05b3b006284f0a998517594080bc76
+#: ../../source/about.rst:972
+msgid ""
+"`CLOUDSTACK-3063 <https://issues.apache.org/jira/browse/CLOUDSTACK-3063>`_"
+msgstr ""
+
+# 32f5d4b07a0b4656a1d273225600663e
+#: ../../source/about.rst:972
+msgid ""
+"[UI]Dedicating a host to non-root domain which has instances of other "
+"domain(ro..."
+msgstr ""
+
+# 7d1845ed384b44c18be7d08556c94053
+#: ../../source/about.rst:973
+msgid ""
+"`CLOUDSTACK-3101 <https://issues.apache.org/jira/browse/CLOUDSTACK-3101>`_"
+msgstr ""
+
+# 7c613c75b4b5498bbc3847eba9e9c43f
+#: ../../source/about.rst:973
+msgid "[DR] list* APIs are not working based on the display* flags ..."
+msgstr ""
+
+# 20624242deaa47ff823797c8f8797a63
+#: ../../source/about.rst:974
+msgid ""
+"`CLOUDSTACK-3225 <https://issues.apache.org/jira/browse/CLOUDSTACK-3225>`_"
+msgstr ""
+
+# 4ae5d16975ce4612ae8a2f674247e2f5
+#: ../../source/about.rst:974
+msgid ""
+"Multiple NPEs when cloudstack-management service is restarted with "
+"incomplete ta..."
+msgstr ""
+
+# 44f6905ab2784817840f2f4414ecd19b
+#: ../../source/about.rst:975
+msgid ""
+"`CLOUDSTACK-3265 <https://issues.apache.org/jira/browse/CLOUDSTACK-3265>`_"
+msgstr ""
+
+# f1e4d8bc2b2a46e0bd431e84d51e6e7e
+#: ../../source/about.rst:975
+msgid ""
+"[Health Check for NS LB]Failure to create a lb health check policy returns a"
+" API..."
+msgstr ""
+
+# d3b589ac76f3462e95f825dbb318b709
+#: ../../source/about.rst:976
+msgid ""
+"`CLOUDSTACK-3325 <https://issues.apache.org/jira/browse/CLOUDSTACK-3325>`_"
+msgstr ""
+
+# 2a9d3d66cd434e44a27c322e53ab82d3
+#: ../../source/about.rst:976
+msgid ""
+"[UI] [GSLB]: add text box to specify weight for each load balancer "
+"participating..."
+msgstr ""
+
+# 2dde3723f50f4ce086fec6e9ae7e2087
+#: ../../source/about.rst:977
+msgid ""
+"`CLOUDSTACK-3406 <https://issues.apache.org/jira/browse/CLOUDSTACK-3406>`_"
+msgstr ""
+
+# 8f43f91478884ca78b65a209b950054a
+#: ../../source/about.rst:977
+msgid ""
+"UI: ZWPS: Zone wizard: Primary storage creation failed after \"fix error\" "
+"in \"add..."
+msgstr ""
+
+# 35aaf061f97244a6b8fadc7abddb2b83
+#: ../../source/about.rst:978
+msgid ""
+"`CLOUDSTACK-3477 <https://issues.apache.org/jira/browse/CLOUDSTACK-3477>`_"
+msgstr ""
+
+# 8bb57ac4b9664575823aec6390cda227
+#: ../../source/about.rst:978
+msgid ""
+"resizeDataVolume doesn't return proper error message when trying to shrink "
+"volum..."
+msgstr ""
+
+# 942cd355d2d44b458b643bab82c1677f
+#: ../../source/about.rst:979
+msgid ""
+"`CLOUDSTACK-3553 <https://issues.apache.org/jira/browse/CLOUDSTACK-3553>`_"
+msgstr ""
+
+# a7251e773cda429ea03553182a677ec5
+#: ../../source/about.rst:979
+msgid ""
+"[UI]UI remains in the processing state forever when it failed to delete "
+"primary ..."
+msgstr ""
+
+# d4b126c917364b0d96635b21b4665181
+#: ../../source/about.rst:980
+msgid ""
+"`CLOUDSTACK-3671 <https://issues.apache.org/jira/browse/CLOUDSTACK-3671>`_"
+msgstr ""
+
+# 98869aecb40548f38fd4300bae9b7843
+#: ../../source/about.rst:980
+msgid ""
+"Set Host, Management Network and Storage Network Properly when there are "
+"multipl..."
+msgstr ""
+
+# 01f0168d82aa4ce190ce8dd84044233a
+#: ../../source/about.rst:981
+msgid ""
+"`CLOUDSTACK-3815 <https://issues.apache.org/jira/browse/CLOUDSTACK-3815>`_"
+msgstr ""
+
+# 4d9fd9b9356e4b03a21abb5217544bfc
+#: ../../source/about.rst:981
+msgid ""
+"\"SNAPSHOT.CREATE\" event's states are not registered on the events table "
+"..."
+msgstr ""
+
+# c2b82a82bc0a416295cd4b08283dd316
+#: ../../source/about.rst:982
+msgid ""
+"`CLOUDSTACK-3895 <https://issues.apache.org/jira/browse/CLOUDSTACK-3895>`_"
+msgstr ""
+
+# 489b344704d842a0b930eca4c9e91f1e
+#: ../../source/about.rst:982
+msgid ""
+"VM Migration across VMWARE clusters which are added with different "
+"switches(Stan..."
+msgstr ""
+
+# a1d81d2e8e54459f81fc0d2625d1832c
+#: ../../source/about.rst:983
+msgid ""
+"`CLOUDSTACK-3896 <https://issues.apache.org/jira/browse/CLOUDSTACK-3896>`_"
+msgstr ""
+
+# 3ca6c4fa7a7e4025a32b5020c325a53b
+#: ../../source/about.rst:983
+msgid ""
+"[PrimaryStorage] deleteStoragePool is not kicking GC for the downloaded "
+"system v..."
+msgstr ""
+
+# 43f0b1ea52fe4fe7a4e2484e506825d6
+#: ../../source/about.rst:984
+msgid ""
+"`CLOUDSTACK-3994 <https://issues.apache.org/jira/browse/CLOUDSTACK-3994>`_"
+msgstr ""
+
+# 5a53b655b1cf4cfea3b90038ddd68633
+#: ../../source/about.rst:984
+msgid ""
+"Wrong error notification is generated when Primary storage (Cluster wide) is"
+" add..."
+msgstr ""
+
+# 574bcc875b064c8e8746bd1a7be27501
+#: ../../source/about.rst:985
+msgid ""
+"`CLOUDSTACK-3995 <https://issues.apache.org/jira/browse/CLOUDSTACK-3995>`_"
+msgstr ""
+
+# 1f9fc290435941328c2109f013d7bdff
+#: ../../source/about.rst:985
+msgid ""
+"No error notification is generated when Primary storage (Zonelevel) is added"
+" wit..."
+msgstr ""
+
+# cb0553897b3c465294130e89bdd4ac58
+#: ../../source/about.rst:986
+msgid ""
+"`CLOUDSTACK-4071 <https://issues.apache.org/jira/browse/CLOUDSTACK-4071>`_"
+msgstr ""
+
+# 2862ac7599114679a6f24de95002f064
+#: ../../source/about.rst:986
+msgid ""
+"[UI] - Word 'Default' is misspelled in descripiton of integration.api.port "
+"under..."
+msgstr ""
+
+# 54ccd314834a46cba8eef1688ecd52b7
+#: ../../source/about.rst:987
+msgid ""
+"`CLOUDSTACK-4183 <https://issues.apache.org/jira/browse/CLOUDSTACK-4183>`_"
+msgstr ""
+
+# aa96ab063bb44952a00f0c47f50207d3
+#: ../../source/about.rst:987
+msgid "[Non-Contiguous VLAN] Typos Appear in an Error Message..."
+msgstr ""
+
+# b09e463e41164a34af3f3bfd49d70912
+#: ../../source/about.rst:988
+msgid ""
+"`CLOUDSTACK-5033 <https://issues.apache.org/jira/browse/CLOUDSTACK-5033>`_"
+msgstr ""
+
+# 08432d28368c40d6addee09bbf581362
+#: ../../source/about.rst:988
+msgid ""
+"ipaddress in management-server.log and api.log are wrong if management "
+"servers i..."
+msgstr ""
+
+# bb40967dfec04fd6a29b3d43b737fafb
+#: ../../source/about.rst:989
+msgid ""
+"`CLOUDSTACK-5309 <https://issues.apache.org/jira/browse/CLOUDSTACK-5309>`_"
+msgstr ""
+
+# f31f90451b8647f2a4287ddb1e87119a
+#: ../../source/about.rst:989
+msgid ""
+"version number and requires upgrade fields are not displayed for routers "
+"when na..."
+msgstr ""
+
+# 431ee2aba7624021949605ee211083c1
+#: ../../source/about.rst:990
+msgid ""
+"`CLOUDSTACK-5383 <https://issues.apache.org/jira/browse/CLOUDSTACK-5383>`_"
+msgstr ""
+
+# e5e9449373fe4fd8901fcd3ee8cef900
+#: ../../source/about.rst:990
+msgid ""
+"Multiselect actions are not reset when a multiselect action is performed..."
+msgstr ""
+
+# e6d4b228f9fd4558b9dc9200add0230e
+#: ../../source/about.rst:991
+msgid ""
+"`CLOUDSTACK-5524 <https://issues.apache.org/jira/browse/CLOUDSTACK-5524>`_"
+msgstr ""
+
+# 33c8cf3f1c6f4fe68174c66381159fc4
+#: ../../source/about.rst:991
+msgid ""
+"[UI]\"root disk size\" field should be removed from the add instance wizard "
+"since ..."
+msgstr ""
+
+# 3a22f8b6a45f4d4fb1f6d5b358d86c9e
+#: ../../source/about.rst:992
+msgid ""
+"`CLOUDSTACK-5824 <https://issues.apache.org/jira/browse/CLOUDSTACK-5824>`_"
+msgstr ""
+
+# cbcd7cd35944493eaf6ed41b06a803b3
+#: ../../source/about.rst:992
+msgid "Delete snapshot UI always success..."
+msgstr ""
+
+# 965f0ea7a2a5482792dba13663078468
+#: ../../source/about.rst:993
+msgid ""
+"`CLOUDSTACK-5885 <https://issues.apache.org/jira/browse/CLOUDSTACK-5885>`_"
+msgstr ""
+
+# f2ea70862fde430e84db8e1b15a6e569
+#: ../../source/about.rst:993
+msgid ""
+"When process receives error, loading overlay on listView element does not "
+"disapp..."
+msgstr ""
+
+# 90a3667d15824f4f90d372d017c45a62
+#: ../../source/about.rst:994
+msgid ""
+"`CLOUDSTACK-5912 <https://issues.apache.org/jira/browse/CLOUDSTACK-5912>`_"
+msgstr ""
+
+# 3cd58ef1d295445f85bafb2d0b6bc2ae
+#: ../../source/about.rst:994
+msgid ""
+"WARN [c.c.h.v.m.HttpNfcLeaseMO] (Thread-28:null) Unexpected exception..."
+msgstr ""
+
+# a1d998b4aa3d43d5adc9d7a61c9fc67f
+#: ../../source/about.rst:995
+msgid ""
+"`CLOUDSTACK-5522 <https://issues.apache.org/jira/browse/CLOUDSTACK-5522>`_"
+msgstr ""
+
+# 738108b3afbd4e4faf7952a781b1727e
+#: ../../source/about.rst:995
+msgid "Need of one more column i.e., \"Name\" at Home>Storage - Snapshots..."
+msgstr ""
+
+# b3b8c82a8e9f48a3badc0431e365dbb5
+#: ../../source/about.rst:996
+msgid ""
+"`CLOUDSTACK-5904 <https://issues.apache.org/jira/browse/CLOUDSTACK-5904>`_"
+msgstr ""
+
+# 8af03a70536b413b945116dd54cc0433
+#: ../../source/about.rst:996
+msgid "Small UI bug..."
+msgstr ""
diff --git a/source/upgrading/locale/ja/LC_MESSAGES/api-changes.mo b/source/upgrading/locale/ja/LC_MESSAGES/api-changes.mo
new file mode 100644
index 0000000..ad03993
--- /dev/null
+++ b/source/upgrading/locale/ja/LC_MESSAGES/api-changes.mo
Binary files differ
diff --git a/source/upgrading/locale/ja/LC_MESSAGES/api-changes.po b/source/upgrading/locale/ja/LC_MESSAGES/api-changes.po
new file mode 100644
index 0000000..67c63c3
--- /dev/null
+++ b/source/upgrading/locale/ja/LC_MESSAGES/api-changes.po
@@ -0,0 +1,270 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-05 14:09+0100\n"
+"PO-Revision-Date: 2014-03-31 15:24+0000\n"
+"Last-Translator: sebgoa <runseb@gmail.com>\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/apache-cloudstack-release-notes-rtd/language/ja/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# d9094117b9964d349a7faf2e57c9e3e4
+#: ../../source/api-changes.rst:17
+msgid "API Changes Introduced in 4.3"
+msgstr ""
+
+# b12ab6bdaa534a33917a061983581f3d
+#: ../../source/api-changes.rst:20
+msgid "Hyper-V"
+msgstr ""
+
+# 5aefde4b6f004c51945b0044d3740217
+# 5b056d9023be4a86ab05195dcfdaca95
+# 11210537ee5147e59056c56b59e42f08
+# a810ec26333c4a3f9d700c3b81485296
+# 9d26f67529d64c698626ee8dc9c400d8
+#: ../../source/api-changes.rst:23 ../../source/api-changes.rst:34
+#: ../../source/api-changes.rst:46 ../../source/api-changes.rst:61
+#: ../../source/api-changes.rst:85
+msgid "API"
+msgstr ""
+
+# 99bd0d75ced643cb80cb4ec4299c35b3
+# f8bd81df2af8470b9990f9897b493d71
+# ccf6333be50b4c05bc93bbae46a92439
+# ddbf27df21c648a28eb25e9d7eff816f
+# 5b062ec9909a408891111c5f7bed4cc1
+#: ../../source/api-changes.rst:23 ../../source/api-changes.rst:34
+#: ../../source/api-changes.rst:46 ../../source/api-changes.rst:61
+#: ../../source/api-changes.rst:85
+msgid "Description"
+msgstr "説明"
+
+# 365a2382c8444d81b8f280e3a681dd69
+#: ../../source/api-changes.rst:25
+msgid "addPrimaryStorage"
+msgstr ""
+
+# 6edcdba9172a4af5b7219da22dd43f75
+# 19400171550b4ef0a53f052b64df6877
+#: ../../source/api-changes.rst:25 ../../source/api-changes.rst:27
+msgid "To this existing API, the following field has been added: smb"
+msgstr ""
+
+# 827fbd70c10347729fb8c779b0b47b0a
+#: ../../source/api-changes.rst:27
+msgid "addImageStore"
+msgstr ""
+
+# 43782ead911e421ca6adb962a7c77dfd
+#: ../../source/api-changes.rst:31
+msgid "Reporting CPU Sockets"
+msgstr ""
+
+# e5ab7c9d1f94448eac6d593130aa05b9
+#: ../../source/api-changes.rst:36
+msgid "listhost"
+msgstr ""
+
+# 45ac5fb2b2c24e7b8187531b170e411f
+#: ../../source/api-changes.rst:36
+msgid ""
+"To this existing API, the following request parameter has been added: "
+"hypervisor."
+msgstr ""
+
+# 05c23488f1864eaaa96b7c997ec9f949
+#: ../../source/api-changes.rst:39
+msgid "The new response parameter added is: cpusockets"
+msgstr ""
+
+# 32af8e6f5a6a4ae2a48b4d533da1f219
+#: ../../source/api-changes.rst:43
+msgid "Publishing Alerts Using the Web ROOT Admin API"
+msgstr ""
+
+# 0372a1c85ea74e5d846c667a271c9562
+#: ../../source/api-changes.rst:48
+msgid "generateAlert"
+msgstr ""
+
+# 32f8078ad6cf4ce4b2bc6bd829054359
+#: ../../source/api-changes.rst:48
+msgid ""
+"A new API has been added to generate and publish alerts for usage services. "
+"The usage services can be installed on a different host or the same host "
+"where the Management Server is running. This API is available only to the "
+"Root Admin."
+msgstr ""
+
+# 0598acaf5d4541a48f2abef70d0c2a97
+#: ../../source/api-changes.rst:53
+msgid "listAlerts"
+msgstr ""
+
+# 66573b271ddd4dcebe751b1dd443d7d6
+#: ../../source/api-changes.rst:53
+msgid ""
+"To this existing API, a new response parameter has been added: name. An "
+"alert can be searched on the basis of alert name."
+msgstr ""
+
+# 057d779d43db49b083cebe754abc8653
+#: ../../source/api-changes.rst:58
+msgid "Dynamic Compute Offering"
+msgstr ""
+
+# 23dbcf83d85544d6a77f7cee9d20a495
+#: ../../source/api-changes.rst:63
+msgid "DeployVM"
+msgstr ""
+
+# b3a16a57e3444e9eb9b133e1c7aae502
+# 0c1b450d88ee41a29d3940fb4dbe446e
+# 5af7afdab9124e4ab6ab30535e91cfca
+# 47210117aa364a6fa3f3fe116994fd9d
+# 8ddafba6eab243e3a9f3c40cafc47506
+#: ../../source/api-changes.rst:63 ../../source/api-changes.rst:66
+#: ../../source/api-changes.rst:69 ../../source/api-changes.rst:73
+#: ../../source/api-changes.rst:76
+msgid ""
+"To this existing API, the following request parameter has been added: "
+"details."
+msgstr ""
+
+# 697e61df898e41468a4bb34915c0a2c5
+#: ../../source/api-changes.rst:66
+msgid "ScaleVM"
+msgstr ""
+
+# deb002fc84ca4df181cbcf23666cfeee
+#: ../../source/api-changes.rst:69
+msgid "ScaleSystemVM"
+msgstr ""
+
+# 8eba0c13bb83496cb7f98a4e8d9ab6fc
+#: ../../source/api-changes.rst:73
+msgid "UpgradeVM"
+msgstr ""
+
+# 77f58f648f6b4cc7ba29e1483185c1d8
+#: ../../source/api-changes.rst:76
+msgid "UpgradeSystemVM"
+msgstr ""
+
+# ba68c7e577064f13b98947ef5477eb20
+#: ../../source/api-changes.rst:82
+msgid "Enhanced Upgrade for Virtual Routers"
+msgstr ""
+
+# 84fb8face38d49189fec55cbc8b5dce1
+#: ../../source/api-changes.rst:87
+msgid "upgradeRouterTemplate"
+msgstr ""
+
+# 79fe85f7d8804dccb880a1608b426cdd
+#: ../../source/api-changes.rst:87
+msgid "This is a new API which has been added in this release."
+msgstr ""
+
+# fbbbb874ceab4379a5172a20af2e61fe
+#: ../../source/api-changes.rst:89
+msgid "The following are the request parameters:"
+msgstr ""
+
+# 65599f3691cf4130a9806c3d5ad95120
+#: ../../source/api-changes.rst:91
+msgid "id: Upgrade the specified VR"
+msgstr ""
+
+# fc78e916a3b7421b9c4c97e6684da339
+#: ../../source/api-changes.rst:93
+msgid "zone\\_id : Upgrade the VRs in the specified zone."
+msgstr ""
+
+# 8a8c04a211af421587e828e9922fbfb7
+#: ../../source/api-changes.rst:95
+msgid "pod\\_id : Upgrade the VRs in the specified pod."
+msgstr ""
+
+# 80cbde982e394ef6a0e347e9ab6332e0
+#: ../../source/api-changes.rst:97
+msgid "cluster\\_id : Upgrade the VRs in the specified cluster."
+msgstr ""
+
+# 5a8aa0e5cc3941c894873dc6c6425acd
+#: ../../source/api-changes.rst:99
+msgid "domain\\_id : Upgrade the VRs belonging to the specified domain."
+msgstr ""
+
+# d91d1a80b9d34a70b28fcc1785f7328c
+#: ../../source/api-changes.rst:102
+msgid "account\\_id : Upgrade the VRs belonging to the specified account."
+msgstr ""
+
+# 638ab1630ae8470cb15bbbbb045a6260
+#: ../../source/api-changes.rst:106
+msgid "listRouters"
+msgstr ""
+
+# 4fe7967e4fd445c682ddea876504ca8c
+#: ../../source/api-changes.rst:106
+msgid ""
+"For this existing API, the following request parameters has been added:"
+msgstr ""
+
+# e301f86659fa42e4a51f4a7999592c53
+#: ../../source/api-changes.rst:109
+msgid "version: Lists routers by specified version."
+msgstr ""
+
+# 86f961243ddc49dd88459e0ff937132d
+#: ../../source/api-changes.rst:111
+msgid "zone\\_id : lists routers in specified zone."
+msgstr ""
+
+# 3cf021b43806427992de1d916bb4b3ba
+#: ../../source/api-changes.rst:113
+msgid "pod\\_id : Lists routers in the specified pod."
+msgstr ""
+
+# 285dde45b78a44a682ce3c68f5c74bbc
+#: ../../source/api-changes.rst:115
+msgid "cluster\\_id : Lists routers in the specified cluster."
+msgstr ""
+
+# 063f3aa2737340dba9d8093fdda068d7
+#: ../../source/api-changes.rst:117
+msgid "domain\\_id : Lists routers owned by specified domain."
+msgstr ""
+
+# f08534c64c0e4cf4a756b327179d92ba
+#: ../../source/api-changes.rst:119
+msgid "account: Lists routers owned by specified account."
+msgstr ""
+
+# 28e790d3d2074de488c9a83d654e75be
+#: ../../source/api-changes.rst:121
+msgid "The following response parameters has been added:"
+msgstr ""
+
+# e3472c1cbe7b4ed884ea7122265172bb
+#: ../../source/api-changes.rst:123
+msgid "version : (String) The router version. For example, 4.3.0."
+msgstr ""
+
+# 3609a98e83f947cb983ed97c651cd607
+#: ../../source/api-changes.rst:125
+msgid ""
+"requiresupgrade: (Boolean) The flag to indicate if the router template "
+"requires an upgrade."
+msgstr ""
diff --git a/source/upgrading/locale/ja/LC_MESSAGES/compat.mo b/source/upgrading/locale/ja/LC_MESSAGES/compat.mo
new file mode 100644
index 0000000..ad03993
--- /dev/null
+++ b/source/upgrading/locale/ja/LC_MESSAGES/compat.mo
Binary files differ
diff --git a/source/upgrading/locale/ja/LC_MESSAGES/compat.po b/source/upgrading/locale/ja/LC_MESSAGES/compat.po
new file mode 100644
index 0000000..51895b1
--- /dev/null
+++ b/source/upgrading/locale/ja/LC_MESSAGES/compat.po
@@ -0,0 +1,192 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-05 14:09+0100\n"
+"PO-Revision-Date: 2014-03-31 12:58+0000\n"
+"Last-Translator: sebgoa <runseb@gmail.com>\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/apache-cloudstack-release-notes-rtd/language/ja/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# db2da739b7a34d9bb5a1576dc1042204
+#: ../../source/compat.rst:17
+msgid "Compatibility Matrix"
+msgstr ""
+
+# c7acf31a9adf453fbc640c154ab269ee
+#: ../../source/compat.rst:20
+msgid "Supported OS Versions for Management Server"
+msgstr ""
+
+# e99c2e0451784e1cbff91e3c5c7bd689
+#: ../../source/compat.rst:22
+msgid ""
+"This section lists the operating systems that are supported for running "
+"CloudStack Management Server. Note that specific versions of the operating "
+"systems are tested, so compatibility with CentOS 6.3 may not indicate "
+"compatibility with CentOS 6.2, 6.1 and so on."
+msgstr ""
+
+# cf915523898f4abf983568b8cec84018
+#: ../../source/compat.rst:29
+msgid "RHEL versions 5.5, 6.2, 6.3, and 6.4"
+msgstr ""
+
+# 5683129179f747809a6716b37511fadf
+#: ../../source/compat.rst:33
+msgid "CentOS versions 6.3, and 6.4"
+msgstr ""
+
+# 91f4ff90b38c41d098678a134d694f51
+#: ../../source/compat.rst:37
+msgid "Ubuntu 12.04 LTS"
+msgstr ""
+
+# fb119d6e242e44868a8fa98413ec8d19
+#: ../../source/compat.rst:40
+msgid "Supported Hypervisor Versions"
+msgstr ""
+
+# dba2f41a378848b98ea1f4a9e4172113
+#: ../../source/compat.rst:42
+msgid ""
+"CloudStack supports three hypervisor families, XenServer with XAPI, KVM, and"
+" VMware with vSphere."
+msgstr ""
+
+# 3a0e082d30544c959a9c0b9e00991268
+#: ../../source/compat.rst:47
+msgid "Windows Server 2012 R2 (with Hyper-V Role enabled)"
+msgstr ""
+
+# 7614dfa9d7be4029913713efa375f856
+#: ../../source/compat.rst:51
+msgid "Hyper-V 2012 R2"
+msgstr ""
+
+# c46e689be4d24f9483eac04951615e93
+#: ../../source/compat.rst:55
+msgid "CentOS 6.2 with KVM"
+msgstr ""
+
+# d9bfa6c2911747a3aff66374d976d4e5
+#: ../../source/compat.rst:59
+msgid "Red Hat Enterprise Linux 6.2 with KVM"
+msgstr ""
+
+# a285a4f39e6f4e19aa08a9dd7e42c01a
+#: ../../source/compat.rst:63
+msgid "XenServer 6.0.2 (with Hotfix)"
+msgstr ""
+
+# dbcd5f4102ff4929b9aff04cc5350b41
+#: ../../source/compat.rst:67
+msgid "XenServer versions 6.1 and 6.2 SPI with latest hotfixes"
+msgstr ""
+
+# d6992bb8033e488988bc1f5236e513e1
+#: ../../source/compat.rst:71
+msgid "VMware versions 5.0, 5.1, and 5.5"
+msgstr ""
+
+# 12b79b83746f4c3bae71bf682e4d2f66
+#: ../../source/compat.rst:75
+msgid ""
+"Bare metal hosts are supported, which have no hypervisor. These hosts can "
+"run the following operating systems:"
+msgstr ""
+
+# 99717374baab44fca244b8c5d0f60f41
+#: ../../source/compat.rst:80
+msgid "RHEL or CentOS, v6.2 or 6.3"
+msgstr ""
+
+# 673c1eb4b2da40b3bd0c7865984fc1c6
+#: ../../source/compat.rst:82
+msgid "Use libvirt version 0.9.10 for CentOS 6.3"
+msgstr ""
+
+# 096ea4c057e0422cb91394032a6a22cf
+#: ../../source/compat.rst:86
+msgid "Fedora 17"
+msgstr ""
+
+# 4105889816dc4de2a016eb065383c49f
+#: ../../source/compat.rst:90
+msgid "Ubuntu 12.04"
+msgstr ""
+
+# b35052cb1655413bbf28d27a20ad0d49
+#: ../../source/compat.rst:92
+msgid ""
+"For more information, see the Hypervisor Compatibility Matrix in the "
+"CloudStack Installation Guide."
+msgstr ""
+
+# 0260f6594d3e4252bf08ff981d0a4d64
+#: ../../source/compat.rst:96
+msgid "Supported External Devices"
+msgstr ""
+
+# ba52dc4c032e49159af61327073557d2
+#: ../../source/compat.rst:100
+msgid "Netscaler VPX and MPX versions 9.3 and 10.e"
+msgstr ""
+
+# f9d4904e3edc4771ab5e2878587a39e1
+#: ../../source/compat.rst:104
+msgid "Netscaler SDX version 9.3"
+msgstr ""
+
+# 65cfdd4398524ff18e124aa27536fc04
+#: ../../source/compat.rst:108
+msgid "SRX (Model srx100b) versions 10.3 or higher"
+msgstr ""
+
+# ddaaa8237d914d99b8d667eaab49dd1c
+#: ../../source/compat.rst:112
+msgid "F5 10.1.0 (Build 3341.1084)"
+msgstr ""
+
+# ecc485f44e94497cb9ec57b64e6f8014
+#: ../../source/compat.rst:115
+msgid "Supported Browsers"
+msgstr ""
+
+# d895545db5e94734ad95d4d44354c002
+#: ../../source/compat.rst:117
+msgid ""
+"The CloudStack Web-based UI should be compatible with any modern browser, "
+"but it's possible that some browsers will not render portions of the UI "
+"reliably, depending on their support of Web standards. For best results, one"
+" of the following browsers recommended:"
+msgstr ""
+
+# 31f5d283ce004769846983ab0679138f
+#: ../../source/compat.rst:124
+msgid "Internet Explorer versions 10 and 11"
+msgstr ""
+
+# fdd3e5088bb34225b7fca3a19f38b69f
+#: ../../source/compat.rst:128
+msgid "Firefox version 26 or lower"
+msgstr ""
+
+# 5566cd6dd73b43759233def2e8beb178
+#: ../../source/compat.rst:132
+msgid "Google Chrome version 31"
+msgstr ""
+
+# 13b039b1a4fa4d33a686254acfd5b75d
+#: ../../source/compat.rst:136
+msgid "Safari 5"
+msgstr ""
diff --git a/source/upgrading/locale/ja/LC_MESSAGES/index.mo b/source/upgrading/locale/ja/LC_MESSAGES/index.mo
new file mode 100644
index 0000000..3570fba
--- /dev/null
+++ b/source/upgrading/locale/ja/LC_MESSAGES/index.mo
Binary files differ
diff --git a/source/upgrading/locale/ja/LC_MESSAGES/index.po b/source/upgrading/locale/ja/LC_MESSAGES/index.po
new file mode 100644
index 0000000..9512a65
--- /dev/null
+++ b/source/upgrading/locale/ja/LC_MESSAGES/index.po
@@ -0,0 +1,52 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+#
+# Translators:
+# sebgoa <runseb@gmail.com>, 2014
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-05 14:09+0100\n"
+"PO-Revision-Date: 2014-03-31 18:33+0000\n"
+"Last-Translator: sebgoa <runseb@gmail.com>\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/apache-cloudstack-release-notes-rtd/language/ja/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 208f4a89b044435a92aea7c8b4300a6a
+#: ../../source/index.rst:22
+msgid "Welcome to Apache CloudStack Release Notes"
+msgstr "Apache CloudStack リリースノートへようこそ"
+
+# 3419fa4841bb4c5b8a97aa893918cd10
+#: ../../source/index.rst:24
+msgid ""
+"This section describes the operating systems, browsers, and hypervisors that"
+" have been newly tested and certified compatible with CloudStack 4.3. Most "
+"earlier OS and hypervisor versions are also still supported for use with 4.3"
+" It might work well on other platforms, but the platforms listed below are "
+"the ones that are specifically tested against and are more likely to be able"
+" to help troubleshoot if you run into any issues."
+msgstr "この章では CloudStack 4.3 で新しくテストされ保証されているオペレーティングシステム、ブラウザ、ハイパーバイザーに関して記述しています。これまでの OS や ハイパーバイザーのバージョンの多くは引き続き 4.3 でサポートされ他のプラットフォームより安定して動作するでしょう。しかし以下に示されているプラットフォームは注力してテストされており何らかの問題が発生した際にトラブルシューティングを支援する可能性が高いものです。"
+
+# 5556135be49b4842a8386379fc3f66e4
+#: ../../source/index.rst:32
+msgid ""
+"This document contains information specific to this release of CloudStack, "
+"including upgrade instructions from prior releases, new features added to "
+"CloudStack, API changes, and issues fixed in the release. For installation "
+"instructions, please see the `Installation Guide <http://cloudstack-"
+"installation.readthedocs.org/en/latest/>`__. For usage and administration "
+"instructions, please see the `CloudStack Administrator's Guide <http"
+"://cloudstack-administration.readthedocs.org/en/latest/>`__."
+msgstr "このドキュメントは本 CloudStack リリースの特定情報を含んでおり、以前のバージョンからのアップグレード方法、CloudStack に追加された新機能、API の変更点、修正された問題が含まれます。インストール方法に関しては `インストールガイド <http://cloudstack-installation.readthedocs.org/en/latest/>`__. を参照してください。使い方と管理方法に関しては `CloudStack 管理者ガイド <http://cloudstack-administration.readthedocs.org/en/latest/>`__. を参照してください。"
+
+# a0536e5ac6e44bf2a3fb53a10aaac844
+#: ../../source/index.rst:38
+msgid "Contents:"
+msgstr "コンテンツ:"
diff --git a/source/upgrading/locale/ja/LC_MESSAGES/rnotes.mo b/source/upgrading/locale/ja/LC_MESSAGES/rnotes.mo
new file mode 100644
index 0000000..ad03993
--- /dev/null
+++ b/source/upgrading/locale/ja/LC_MESSAGES/rnotes.mo
Binary files differ
diff --git a/source/upgrading/locale/ja/LC_MESSAGES/rnotes.po b/source/upgrading/locale/ja/LC_MESSAGES/rnotes.po
new file mode 100644
index 0000000..e53f851
--- /dev/null
+++ b/source/upgrading/locale/ja/LC_MESSAGES/rnotes.po
@@ -0,0 +1,2600 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+#
+# Translators:
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes RTD\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-05 14:09+0100\n"
+"PO-Revision-Date: 2014-03-31 15:24+0000\n"
+"Last-Translator: sebgoa <runseb@gmail.com>\n"
+"Language-Team: Japanese (http://www.transifex.com/projects/p/apache-cloudstack-release-notes-rtd/language/ja/)\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Language: ja\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
+
+# 42d678eb2285488da05dc3cd6c263f02
+#: ../../source/rnotes.rst:18
+msgid "Upgrade Instructions for 4.3"
+msgstr ""
+
+# 41b628d034ee4fce9241de5ef66a7f6b
+#: ../../source/rnotes.rst:20
+msgid ""
+"This section contains upgrade instructions from prior versions of CloudStack"
+" to Apache CloudStack 4.3. We include instructions on upgrading to Apache "
+"CloudStack from pre-Apache versions of Citrix CloudStack (last version prior"
+" to Apache is 3.0.2) and from the releases made while CloudStack was in the "
+"Apache Incubator."
+msgstr ""
+
+# 6212699679f1434586e45ee4fd3827bc
+#: ../../source/rnotes.rst:26
+msgid ""
+"If you run into any issues during upgrades, please feel free to ask "
+"questions on users@cloudstack.apache.org or dev@cloudstack.apache.org."
+msgstr ""
+
+# 89e3526f428349e7bd2e3a6e07058278
+#: ../../source/rnotes.rst:30
+msgid "Upgrade from 4.2.0 to 4.3"
+msgstr ""
+
+# 8bbac42e272243b29532cab877c5b8bc
+#: ../../source/rnotes.rst:32
+msgid "This section will guide you from CloudStack 4.2 to CloudStack 4.3."
+msgstr ""
+
+# bb34709f92104ec98d45d233b9e44f06
+# e1b99036c1f94563a24d6d8d2cd82412
+# 2abaa3bf4c6c4910937c92ac89c2ee8c
+#: ../../source/rnotes.rst:34 ../../source/rnotes.rst:663
+#: ../../source/rnotes.rst:1197
+msgid "Any steps that are hypervisor-specific will be called out with a note."
+msgstr ""
+
+# 6b7c5646356f4d0fba9a8ba16c431a57
+# b7be4c0d68ee4cc2b0df2f511407fc6c
+# 56932859eab846ee8bde43bf4a39aaa0
+#: ../../source/rnotes.rst:36 ../../source/rnotes.rst:665
+#: ../../source/rnotes.rst:1201
+msgid ""
+"We recommend reading through this section once or twice before beginning "
+"your upgrade procedure, and working through it on a test system before "
+"working on a production system."
+msgstr ""
+
+# 505986b902774ceca679cfdbf2e13cce
+# 558231d5963c4b189228e328173557e4
+# 60afca54b4ef4d508b68b4186424a682
+# d501a610dcc94573a2e9c92aac6d9a00
+#: ../../source/rnotes.rst:40 ../../source/rnotes.rst:678
+#: ../../source/rnotes.rst:1223 ../../source/rnotes.rst:1641
+msgid ""
+"The following upgrade instructions should be performed regardless of "
+"hypervisor type."
+msgstr ""
+
+# 3a8581a1b3584a41b31a5c70b36d8020
+#: ../../source/rnotes.rst:46
+msgid ""
+"While running the existing 4.2.0 system, log in to the UI as root "
+"administrator."
+msgstr ""
+
+# dead12c2e5c54084b6fbba84c753c00a
+# 94bfbc9d533d4dd2abaa51ea8c274320
+# c651b785c87e463da7426af0a270417b
+# 6ae408a97d4c41e394b95b8859ea6969
+# 0a41d5ac486f4713a9d3efa71202bfb1
+#: ../../source/rnotes.rst:51 ../../source/rnotes.rst:687
+#: ../../source/rnotes.rst:1232 ../../source/rnotes.rst:1650
+#: ../../source/rnotes.rst:2475
+msgid "In the left navigation bar, click Templates."
+msgstr ""
+
+# 1b425d8481a34191926e9c1035f818c5
+# b5df3d99c2644a7b894dce754153c9ab
+# 69da380f577f46a3ab8f6e4f5cdec9f2
+# 5d01f7180135414d9affc57d6b8b3584
+# 4cd4c23255c54b12bd800870cd1c6fd8
+#: ../../source/rnotes.rst:55 ../../source/rnotes.rst:691
+#: ../../source/rnotes.rst:1236 ../../source/rnotes.rst:1654
+#: ../../source/rnotes.rst:2479
+msgid "In Select view, click Templates."
+msgstr ""
+
+# eb18c047f67d4bfe846ad7843047244b
+# 1af75b9c5972487488b73a0eec220d7d
+# 644051fde9ab49dba735cfe6f0a77f38
+# afc364dcc0be4e0796690a0a72680998
+# c2534c7e344a4a81a634d8666543d1eb
+#: ../../source/rnotes.rst:59 ../../source/rnotes.rst:695
+#: ../../source/rnotes.rst:1240 ../../source/rnotes.rst:1658
+#: ../../source/rnotes.rst:2483
+msgid "Click Register template."
+msgstr ""
+
+# f958c175bf8f4edfb68f850080032003
+# 57ba4c7f0ba24b1f8099281573aa01c2
+# c56adc75ca1d411587542598779ae293
+# a804e8c72fa84801bb4a68550f112e53
+# a19821955fdf4128b23a8bab0f787a1d
+#: ../../source/rnotes.rst:61 ../../source/rnotes.rst:697
+#: ../../source/rnotes.rst:1242 ../../source/rnotes.rst:1660
+#: ../../source/rnotes.rst:2485
+msgid "The Register template dialog box is displayed."
+msgstr ""
+
+# 5c05e1912faf49c58b6b71e38915a8b1
+# c2ff2045faca4ca0854a6378f7dbf05e
+# 74adacefbc094e0da36da3afece913f4
+# 6b719f75b2ec44c4a954cef0fad48b25
+#: ../../source/rnotes.rst:65 ../../source/rnotes.rst:701
+#: ../../source/rnotes.rst:1246 ../../source/rnotes.rst:1664
+msgid ""
+"In the Register template dialog box, specify the following values (do not "
+"change these):"
+msgstr ""
+
+# 008bbb4c8ab2489d997f3fac9bd8dd3e
+# b6de8b708b154b379af5a94da6953d30
+# d25fd8cdb35342d5b76d3af23ec8b3d0
+# 70d66ffed2864e94964b8bd40b257176
+# 63d69aaddcac4e519cb72d2b914359f3
+#: ../../source/rnotes.rst:69 ../../source/rnotes.rst:705
+#: ../../source/rnotes.rst:1250 ../../source/rnotes.rst:1668
+#: ../../source/rnotes.rst:2493
+msgid "Hypervisor"
+msgstr "ハイパーバイザー"
+
+# d1781bdac5cb40e684a6888e8eb052fd
+# a861163d98014b449c8b501efb2812ce
+# 1c3c49173dff4c07a6ae2d2febf1ab37
+# 9134492ad9f5407781bc408bb9494aa6
+# b89357f04fcd4549959d20bcb82b6800
+#: ../../source/rnotes.rst:69 ../../source/rnotes.rst:705
+#: ../../source/rnotes.rst:1250 ../../source/rnotes.rst:1668
+#: ../../source/rnotes.rst:2493
+msgid "Description"
+msgstr "説明"
+
+# 85616c2b776642458b6b074f0955b7ec
+# 390402007d6748c1bfbc48a03eb1ff4a
+# 16b265fc693d40059afb1a0557c5b1b0
+# c23d316b1adb4a10aa4506f6df8d7695
+# 0a964e1ec1434396b92cf81ca7da353a
+#: ../../source/rnotes.rst:71 ../../source/rnotes.rst:707
+#: ../../source/rnotes.rst:1252 ../../source/rnotes.rst:1670
+#: ../../source/rnotes.rst:2495
+msgid "XenServer"
+msgstr ""
+
+# d46f926f5a5e454589899b93b4c51eeb
+# f202c480c879466e84a2bc7ee2ef8eb1
+# 70bc5eec456146758139bfeafcd6c254
+# 2d50b6b5c36f4415af39d1007d8035f4
+# 3e50d8b797504a0c9250d43fc8be49e2
+#: ../../source/rnotes.rst:71 ../../source/rnotes.rst:707
+#: ../../source/rnotes.rst:1252 ../../source/rnotes.rst:1670
+#: ../../source/rnotes.rst:2495
+msgid "Name: systemvm-xenserver-4.3"
+msgstr ""
+
+# 60087b2d154f4132b46f52086e5ef029
+# b05063dc53a542889111c74ddf820fc8
+# e4ee3f30d36348b79761563c511fcc53
+# 2f2a7a9e5b99483787ad9929b2ee2e19
+# 015ea9102fe34d138c41765527102de1
+#: ../../source/rnotes.rst:73 ../../source/rnotes.rst:709
+#: ../../source/rnotes.rst:1254 ../../source/rnotes.rst:1672
+#: ../../source/rnotes.rst:2497
+msgid "Description: systemvm-xenserver-4.3"
+msgstr ""
+
+# aab4e46f0f074fd494f398a0f2376690
+# 6f3059ed5a924af1a6af9888de9f60f8
+# f1cfa864cc48446da7d15b78d13e8cec
+# b0d327bfcfb748ddb9a3b12e65dfdbca
+# 78393b0f0b05474fbda4d5e95cc7bbdf
+#: ../../source/rnotes.rst:75 ../../source/rnotes.rst:711
+#: ../../source/rnotes.rst:1256 ../../source/rnotes.rst:1674
+#: ../../source/rnotes.rst:2499
+msgid ""
+"URL: http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14"
+"-master-xen.vhd.bz2"
+msgstr ""
+
+# d439e558d2494c82ba35d4b7d5141ac8
+# 351e1644cbf84a30af80410ba146f523
+# 0d02e5117823415d95d11bb0f9dec178
+# 9c9085c2e247415a9ee61fb1f0c2e7a1
+# 6323bb49cb9d4386b9e3636b89975a1e
+# ce606edd6e0043e483827424308e9eae
+# b9857085067e474680eeb7dd3e26ba6e
+# 0b639ca277014c348ca0ef447d5ad81b
+# 0d4ddf72a2884ac680c470c5e4f80dd5
+# 730c0e58fb4f495bb028b139240c2c82
+# 5b27e86a9ca742e598279f8564c13c56
+# fcc6a47719614722975ba2ba45768c4f
+#: ../../source/rnotes.rst:78 ../../source/rnotes.rst:103
+#: ../../source/rnotes.rst:128 ../../source/rnotes.rst:714
+#: ../../source/rnotes.rst:739 ../../source/rnotes.rst:764
+#: ../../source/rnotes.rst:1259 ../../source/rnotes.rst:1284
+#: ../../source/rnotes.rst:1309 ../../source/rnotes.rst:2502
+#: ../../source/rnotes.rst:2527 ../../source/rnotes.rst:2552
+msgid "Zone: Choose the zone where this hypervisor is used"
+msgstr ""
+
+# 838318c9d31645ae99bd3e79e18940e0
+# 89d8cd6fc1f74356ac886e43bc4187b9
+# 27b2a7a43fae446c926fc8bbecd5d7f1
+# 9ba791b12686435eb446164e4517f7ac
+# 24c021d0aac94240bbe06b215175b4c9
+#: ../../source/rnotes.rst:80 ../../source/rnotes.rst:716
+#: ../../source/rnotes.rst:1261 ../../source/rnotes.rst:1680
+#: ../../source/rnotes.rst:2504
+msgid "Hypervisor: XenServer"
+msgstr ""
+
+# d69de9c666aa46f992dea502e19b70a9
+# 893acc0852ac4e70b8530c3e6660c855
+# 25d54017a01647eca16c41b394917469
+# 99d94266a0a540348c29e7ddca07f3a4
+# d302f3b8b27c44dd896488739bd364d7
+#: ../../source/rnotes.rst:82 ../../source/rnotes.rst:718
+#: ../../source/rnotes.rst:1263 ../../source/rnotes.rst:1682
+#: ../../source/rnotes.rst:2506
+msgid "Format: VHD"
+msgstr ""
+
+# 4b6a013e94f2406396f926647afd9372
+# ecc1aa91806f4aef9673429da7c08880
+# 3b131d605d6c4ceebf36d0629e200f6e
+# c85c58df68cd489abeb977c3e68019c7
+# 49d9c0788b314116a9ccb36c5733b3a9
+# 1ca463f215ec4f3b84128380c4a05890
+# cade67e03efc472fa6e133c9640a306d
+# 4e5b73a422da4d40bd312e4b135c3f74
+# a321a8102e2a46b3a77d89daca362cb9
+# 2c86881fb2194b039886df7a968c6fdd
+# 67974420a6e6499d99cfec0a4eacf00c
+# 805a3f0bd7f2442e9686ff640c8549d3
+# 67256469d5de4d358947f1fdd2068ea7
+# ad16207a4d3b4f3782eac427c7b47f61
+# e54a1866e7f44b69a9ac67a5c8737d9f
+#: ../../source/rnotes.rst:84 ../../source/rnotes.rst:109
+#: ../../source/rnotes.rst:134 ../../source/rnotes.rst:720
+#: ../../source/rnotes.rst:745 ../../source/rnotes.rst:770
+#: ../../source/rnotes.rst:1265 ../../source/rnotes.rst:1290
+#: ../../source/rnotes.rst:1315 ../../source/rnotes.rst:1684
+#: ../../source/rnotes.rst:1710 ../../source/rnotes.rst:1736
+#: ../../source/rnotes.rst:2508 ../../source/rnotes.rst:2533
+#: ../../source/rnotes.rst:2558
+msgid ""
+"OS Type: Debian GNU/Linux 7.0 (64-bit) (or the highest Debian release number"
+" available in the dropdown)"
+msgstr ""
+
+# 6cd60538b91c4ca5bc7535ddf246faff
+# 5ddafdb9f3134b599e1817da2e457ddd
+# 356e260a95954844b66ec5df22cd0772
+# bf9acaffb00444edb70986d08b54eb95
+# 8a92f91fd6c34944af0588a8c0778a3d
+# c06527d037c44b8eb7978e30e850be1e
+# 940bef4e5d9540f191979e277d89e7c2
+# f164d0f782ec4d21a99b07420e0b0956
+# 1bf3285c07c2470f981c3091069c3844
+# 84232d240a6244029ddb76715ad99792
+# 8aa46285358b4a2cb083a76342d12f2d
+# f2ee96c3a9d14c41a0fec175098732c9
+# 44052173c6294a59afc5ff05ac365a2c
+# ed71f8f74e9d44388bc335e25c5e266c
+# 5c35014e67244638806bcbc59a5a8e99
+#: ../../source/rnotes.rst:88 ../../source/rnotes.rst:113
+#: ../../source/rnotes.rst:138 ../../source/rnotes.rst:724
+#: ../../source/rnotes.rst:749 ../../source/rnotes.rst:774
+#: ../../source/rnotes.rst:1269 ../../source/rnotes.rst:1294
+#: ../../source/rnotes.rst:1319 ../../source/rnotes.rst:1688
+#: ../../source/rnotes.rst:1714 ../../source/rnotes.rst:1740
+#: ../../source/rnotes.rst:2512 ../../source/rnotes.rst:2537
+#: ../../source/rnotes.rst:2562
+msgid "Extractable: no"
+msgstr ""
+
+# c610924f4de5446c86e8cf570a23ec59
+# f7e0fbc65cb44ec9b685cc665d535123
+# 6b3fe309850a4b7c9ac5c1d5d6821f38
+# 1d3cb70b0c4142c78ba821a0ee011f78
+# fc2911c8b6bb4849b7925489c9ae2a01
+# b211fe77f3b3422b83580c73840ce837
+# ccdeca12ad42483f832b6c5636b06d42
+# 34c794f2b5d9429884c5d5279c21d9e6
+# 90cc0c25be9a46c29323f9ad2c1f4454
+# 094de1f60c2a489f9fd7c7303adbb05c
+# 8eeb67728c8145fd89aa217a2d7096ca
+# ae18a78f3b63424a8a270f64abe4f297
+# e89815bd8daf4980a3c32701ca3c3593
+# bf7a491dc39b418caa3c7784c57f1d87
+# 4968cdbc67bf4f46b02e432ee7ed9025
+#: ../../source/rnotes.rst:90 ../../source/rnotes.rst:115
+#: ../../source/rnotes.rst:140 ../../source/rnotes.rst:726
+#: ../../source/rnotes.rst:751 ../../source/rnotes.rst:776
+#: ../../source/rnotes.rst:1271 ../../source/rnotes.rst:1296
+#: ../../source/rnotes.rst:1321 ../../source/rnotes.rst:1690
+#: ../../source/rnotes.rst:1716 ../../source/rnotes.rst:1742
+#: ../../source/rnotes.rst:2514 ../../source/rnotes.rst:2539
+#: ../../source/rnotes.rst:2564
+msgid "Password Enabled: no"
+msgstr ""
+
+# d6152128090641c8a551f7042fd18c6b
+# 762f5dec3e704bd8998af37e07921d72
+# 3336b3b2a5f44f03aa571c6f2a8e4165
+# 437c7bc51da84b8789b8bb404791f285
+# 8144ecbdaa224a31b211841bcd3fccb1
+# f04444c7107142249b3cd0632f799c32
+# 96ec3fa5df8742788bf8fa4f8972014f
+# 972a8dfca90b433088bf3d63e7c15939
+# 8038d59b9d754d27a13c188e4c8bad3e
+# 831638958e1741bfb19b4f4cf7432ce3
+# bc44062b6198465899b9a11ca85491aa
+# decb386fa81b401982b49671d7184a34
+# e358075912924d02b0b06fd7f5ad5dd9
+# 673458355d034ed0bd3eb1b9375f4b85
+# 476237cedab440c586788be1d6df2f5d
+#: ../../source/rnotes.rst:92 ../../source/rnotes.rst:117
+#: ../../source/rnotes.rst:142 ../../source/rnotes.rst:728
+#: ../../source/rnotes.rst:753 ../../source/rnotes.rst:778
+#: ../../source/rnotes.rst:1273 ../../source/rnotes.rst:1298
+#: ../../source/rnotes.rst:1323 ../../source/rnotes.rst:1692
+#: ../../source/rnotes.rst:1718 ../../source/rnotes.rst:1744
+#: ../../source/rnotes.rst:2516 ../../source/rnotes.rst:2541
+#: ../../source/rnotes.rst:2566
+msgid "Public: no"
+msgstr ""
+
+# b51fe881ba9e4e88af3f1a8661d3a404
+# 5e2ef5de96b54b2ba6c4a5021d63ed04
+# 68b4d45fd6db489393c8216607ae4973
+# f0e3f79f0c474ff7a02a627ad5fd3e01
+# b52b0917a65d4458b247ace2ec5974d0
+# eb8782d77531425abe596b14aa3ca8b7
+# 946fa41fee4b4f1d8dc7d7be82013fe8
+# 1ebb133a1b9e4d639f9a8bf3f0617a6a
+# 661c21e32c514f79a4f81f0357e125d8
+# 390461162ef446769dffda2d6b0acbe5
+# 4e995dea789045949fb42600ad9ade03
+# 61a2fb46acd34449942ec665442fb311
+# 32c1401f85fe44199f8bc0ad300a6b61
+# 24c2ef0a6929479cad3441c1d0909176
+# 7929dd67193e4a06afaa845ea7786ae5
+#: ../../source/rnotes.rst:94 ../../source/rnotes.rst:119
+#: ../../source/rnotes.rst:144 ../../source/rnotes.rst:730
+#: ../../source/rnotes.rst:755 ../../source/rnotes.rst:780
+#: ../../source/rnotes.rst:1275 ../../source/rnotes.rst:1300
+#: ../../source/rnotes.rst:1325 ../../source/rnotes.rst:1694
+#: ../../source/rnotes.rst:1720 ../../source/rnotes.rst:1746
+#: ../../source/rnotes.rst:2518 ../../source/rnotes.rst:2543
+#: ../../source/rnotes.rst:2568
+msgid "Featured: no"
+msgstr ""
+
+# 11882b63ef7a4207989d951b3bb0aa7e
+# f7e6ba6ca99e489cafa9e01826c00694
+# bc092dbc933f4a7a860a9cbdeecaac4c
+# ed43f33f14554bfbb225108a681122a7
+# 3f801c529ea544f38628bf1cdd48fc8f
+#: ../../source/rnotes.rst:96 ../../source/rnotes.rst:732
+#: ../../source/rnotes.rst:1277 ../../source/rnotes.rst:1696
+#: ../../source/rnotes.rst:2520
+msgid "KVM"
+msgstr ""
+
+# 8e80783043a140f2b20e8402b4f220a5
+# 65d65d30eeed44899982886ca191f56f
+# c5764e41dac2435c816a427dc218d49b
+# 5d87a38451e14cd79f91ce9b5d97b65f
+# a2a697b6834f4bd88f5388964e56cace
+#: ../../source/rnotes.rst:96 ../../source/rnotes.rst:732
+#: ../../source/rnotes.rst:1277 ../../source/rnotes.rst:1696
+#: ../../source/rnotes.rst:2520
+msgid "Name: systemvm-kvm-4.3"
+msgstr ""
+
+# dd9acd3e777b43b7be90baa619188718
+# f447dba905de4318b415de8adca145a7
+# 1bdbe2601bba4382afef6d603f5f6924
+# 9ecd547930b3472bb042e1b836f9055c
+# e41898b69f6f4312804f9e8edb6800be
+#: ../../source/rnotes.rst:98 ../../source/rnotes.rst:734
+#: ../../source/rnotes.rst:1279 ../../source/rnotes.rst:1698
+#: ../../source/rnotes.rst:2522
+msgid "Description: systemvm-kvm-4.3"
+msgstr ""
+
+# 18112d67045a4826a21324e45043c1f3
+# 9d7818ae080e4b6980b33c55edcd3ee1
+# 048a5c6ac93648a7b149fa2723ec3beb
+# 565c06cb13304129ba04c27978dfc8d8
+# b8cf8c952bf14f4fb5f7cf084d11aa98
+#: ../../source/rnotes.rst:100 ../../source/rnotes.rst:736
+#: ../../source/rnotes.rst:1281 ../../source/rnotes.rst:1700
+#: ../../source/rnotes.rst:2524
+msgid ""
+"URL: http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14"
+"-master-kvm.qcow2.bz2"
+msgstr ""
+
+# b823ddc9d9f54579be8a164f1949daba
+# f0f674de683c45fb8ce275d210bcebab
+# ac4620c3578b415989d0fb5c0a7f4a73
+# 4d0c71801b434a328dede28902babdc2
+# ed682ff3eca04e2d830b5f51069f5c84
+#: ../../source/rnotes.rst:105 ../../source/rnotes.rst:741
+#: ../../source/rnotes.rst:1286 ../../source/rnotes.rst:1706
+#: ../../source/rnotes.rst:2529
+msgid "Hypervisor: KVM"
+msgstr ""
+
+# e60ebf3c4ba14a35a525462a3101d310
+# 5955b72117514bb783eca575e0523ffb
+# 1c02fe8f1e744fd49394aae64ee5e641
+# 16bb7ae5db4948848078473e7381acd9
+# 27e2c08b6e184428a34365ede87022a7
+#: ../../source/rnotes.rst:107 ../../source/rnotes.rst:743
+#: ../../source/rnotes.rst:1288 ../../source/rnotes.rst:1708
+#: ../../source/rnotes.rst:2531
+msgid "Format: QCOW2"
+msgstr ""
+
+# 2ab69eec46fa4d5fa6e3c5a948936a2a
+# e81be8f0c17e4f2ea26367a9e8a19b54
+# 64b557c5c2ec4e158743408500e1435f
+# d1d572a3c2794d58b48e885153e29199
+# e6e24a4ae6054a6ca04673a1ab1ace8c
+#: ../../source/rnotes.rst:121 ../../source/rnotes.rst:757
+#: ../../source/rnotes.rst:1302 ../../source/rnotes.rst:1722
+#: ../../source/rnotes.rst:2545
+msgid "VMware"
+msgstr ""
+
+# 5c7c14896c464e89a40ed46ec9f1badc
+# 8daf63b1e5de487dbfb052b1b1b5b52b
+# 3accf7c3794c4d089081b73e16c957fc
+# 12f83ab21c4040d8baff0e3c021cfc96
+# 9a9f6bbe66bc485ca94003e7b451ddf7
+#: ../../source/rnotes.rst:121 ../../source/rnotes.rst:757
+#: ../../source/rnotes.rst:1302 ../../source/rnotes.rst:1722
+#: ../../source/rnotes.rst:2545
+msgid "Name: systemvm-vmware-4.3"
+msgstr ""
+
+# 92780e97400449fdbbf2ef0bd374b1cb
+# 22948f9a1e0f43b98635627529b72279
+# cdb07852eb024ada85739a45b8b2fb31
+# 681aad54f06945aab0f6686a28b37aea
+# 026be4dcadd44f8eb288449ea7c5bb71
+#: ../../source/rnotes.rst:123 ../../source/rnotes.rst:759
+#: ../../source/rnotes.rst:1304 ../../source/rnotes.rst:1724
+#: ../../source/rnotes.rst:2547
+msgid "Description: systemvm-vmware-4.3"
+msgstr ""
+
+# 9edb2b100d91490993b3139d7695b2a8
+# b68299a5d4374958b34b758386cc85cd
+# d96632db3762451da83bea92b5586509
+# 03002181282749228c393ace2ca1ab28
+# dfcba25531e24b87a8081fe1761c585c
+#: ../../source/rnotes.rst:125 ../../source/rnotes.rst:761
+#: ../../source/rnotes.rst:1306 ../../source/rnotes.rst:1726
+#: ../../source/rnotes.rst:2549
+msgid ""
+"URL: http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14"
+"-master-vmware.ova"
+msgstr ""
+
+# 2739f087399644a286227208c62d16f2
+# 27ee5363cc7645c0974a787822cc2731
+# c04dae621a60468f89942bdf35214aa7
+# 4410929e67ae4b9a8ccde344ee6635a6
+# 0b0ae4d5aaf4402688e03b8cbce733b6
+#: ../../source/rnotes.rst:130 ../../source/rnotes.rst:766
+#: ../../source/rnotes.rst:1311 ../../source/rnotes.rst:1732
+#: ../../source/rnotes.rst:2554
+msgid "Hypervisor: VMware"
+msgstr ""
+
+# 7c525c40349d426da8d4edb0fad6a3a1
+# 43f012151a5a4dca828b7ac5686d17f6
+# c5a8185466a3403ca88731b04acb0640
+# bb4c9e98ec2740ec84c4a6966efc02ff
+# f61eaa2f59c7479fa85cfbb35196f2ee
+#: ../../source/rnotes.rst:132 ../../source/rnotes.rst:768
+#: ../../source/rnotes.rst:1313 ../../source/rnotes.rst:1734
+#: ../../source/rnotes.rst:2556
+msgid "Format: OVA"
+msgstr ""
+
+# cc7b963a69ea4b88aeeedb09e5be332d
+# f03e04a6fc68422c9e99141bb72c1a8e
+# c03b65c705f64cfc98d04f6597064847
+#: ../../source/rnotes.rst:149 ../../source/rnotes.rst:671
+#: ../../source/rnotes.rst:1207
+msgid ""
+"Most users of CloudStack manage the installation and upgrades of CloudStack "
+"with one of Linux's predominant package systems, RPM or APT. This guide "
+"assumes you'll be using RPM and Yum (for Red Hat Enterprise Linux or "
+"CentOS), or APT and Debian packages (for Ubuntu)."
+msgstr ""
+
+# 723a52379d254df48e67493131d59a6e
+#: ../../source/rnotes.rst:156
+msgid ""
+"Create RPM or Debian packages (as appropriate) and a repository from the 4.3"
+" source, or check the Apache CloudStack downloads page at "
+"`http://cloudstack.apache.org/downloads.html "
+"<http://cloudstack.apache.org/downloads.html>`__ for package repositories "
+"supplied by community members. You will need them for step `9 <#upgrade-deb-"
+"packages-4.3>`__ or step `12 <#upgrade-rpm-packages-4.3>`__."
+msgstr ""
+
+# f34250896ef542fda4fd42546a65a5d4
+# 030a350e5cd2436297a5a4519df23e0d
+# 957e3d9727b24f8eb2ee7f45c9b76863
+#: ../../source/rnotes.rst:163 ../../source/rnotes.rst:793
+#: ../../source/rnotes.rst:1219
+msgid ""
+"Instructions for creating packages from the CloudStack source are in the "
+"`Installation Guide <http://cloudstack.apache.org/docs/en-US/index.html>`__."
+msgstr ""
+
+# 42052b8c68a6456ab40cacbc15103d1f
+# d5e34b3f6dd043978b90d0583a16c946
+# 0dd8514fea1f4e97bf0dc98ca9fd66b2
+#: ../../source/rnotes.rst:169 ../../source/rnotes.rst:799
+#: ../../source/rnotes.rst:1331
+msgid ""
+"Stop your management server or servers. Run this on all management server "
+"hosts:"
+msgstr ""
+
+# d5ae2a32ec9d4814b44cdff2aaf4ec3a
+# 0ae0988de33b418ab302b9b1185708c2
+# cb9a9840e38d4c94bedf6bd6f8ceb590
+#: ../../source/rnotes.rst:178 ../../source/rnotes.rst:808
+#: ../../source/rnotes.rst:1340
+msgid ""
+"If you are running a usage server or usage servers, stop those as well:"
+msgstr ""
+
+# 770393d964b04d53b7ccc6412a5b3c6a
+# c5e8ca3e3527463aa2cbdb2240ed1bbf
+# e889a951d681486388064f4f31e91989
+#: ../../source/rnotes.rst:187 ../../source/rnotes.rst:817
+#: ../../source/rnotes.rst:1349
+msgid ""
+"Make a backup of your MySQL database. If you run into any issues or need to "
+"roll back the upgrade, this will assist in debugging or restoring your "
+"existing environment. You'll be prompted for your password."
+msgstr ""
+
+# f9fbf2fee0e64639ad8782f8303ddf7b
+#: ../../source/rnotes.rst:198
+msgid "Perform the following to verify the artifacts:"
+msgstr ""
+
+# e63dfd2fe1084bacb083d72eb5db8371
+#: ../../source/rnotes.rst:202
+msgid "(optional) Install GPG keys if needed:"
+msgstr ""
+
+# af9567066dc845fdb1ec7366b444120f
+#: ../../source/rnotes.rst:210
+msgid "Import the GPG keys stored in the source distribution's KEYS file"
+msgstr ""
+
+# 049005cfc12041f8b1e292490c30f4c4
+#: ../../source/rnotes.rst:216
+msgid ""
+"Alternatively, download the signing keys, the IDs found in the KEYS file, "
+"individually by using a keyserver."
+msgstr ""
+
+# a3097e42d1084f048a59d85830de53d3
+#: ../../source/rnotes.rst:219
+msgid "For example:"
+msgstr ""
+
+# d2b32a530b2a4cd796599dd23a5f1221
+#: ../../source/rnotes.rst:227
+msgid "Verify signatures and hash files:"
+msgstr ""
+
+# 1564e50432084d9d98e98a456444e4c9
+#: ../../source/rnotes.rst:235
+msgid ""
+"Each of these commands should return no output. Any output from them implies"
+" that there is a difference between the hash you generated locally and the "
+"hash that has been pulled from the server."
+msgstr ""
+
+# 8f767747ab0a4c8dbd0e1198c243bff0
+#: ../../source/rnotes.rst:242
+msgid "Get the commit hash from the VOTE email."
+msgstr ""
+
+# f35ea10fc96a44de830d0206391f8969
+#: ../../source/rnotes.rst:244
+msgid ""
+"For example: ``4cd60f3d1683a3445c3248f48ae064fb573db2a1``. The value changes"
+" between releases."
+msgstr ""
+
+# 6c23307830ae47e6b2dd297e55ad9bc3
+#: ../../source/rnotes.rst:249
+msgid "Create two new temporary directories:"
+msgstr ""
+
+# 15ea8b909be7467686ff82c62dcb1e74
+#: ../../source/rnotes.rst:258
+msgid "Check out the 4.3 branch:"
+msgstr ""
+
+# 6e12f6014678491393792d02fc13ac58
+#: ../../source/rnotes.rst:268
+msgid "Unpack the release artifact:"
+msgstr ""
+
+# 0e59c95dfb4e49a380b57fc8d78dd5ab
+#: ../../source/rnotes.rst:277
+msgid ""
+"Compare the contents of the release artifact with the contents pulled from "
+"the repo:"
+msgstr ""
+
+# 2d63c16b73194f3bbe52bb8bbce5c656
+#: ../../source/rnotes.rst:284
+msgid "Ensure that content is the same."
+msgstr ""
+
+# ba868de916d1458aaf74f2ceaed20269
+#: ../../source/rnotes.rst:288
+msgid "Verify the Code License Headers:"
+msgstr ""
+
+# 70de015831004787afd4554bf5d06815
+#: ../../source/rnotes.rst:295
+msgid ""
+"The build fails if any non-compliant files are present that are not "
+"specifically excluded from the ASF license header requirement. You can "
+"optionally review the target/rat.txt file after the run completes. Passing "
+"the build implies that RAT certifies that the files are compliant and this "
+"test is passed."
+msgstr ""
+
+# e5a4e1d35a774619b436bcf6e9be9222
+# dd7ca70744e14d20861895d26f347a5d
+#: ../../source/rnotes.rst:303 ../../source/rnotes.rst:828
+msgid ""
+"(KVM Only) If primary storage of type local storage is in use, the path for "
+"this storage needs to be verified to ensure it passes new validation. Check "
+"local storage by querying the cloud.storage\\_pool table:"
+msgstr ""
+
+# 15205eb55014464fb0a975958c7f2d5a
+# 895acb18e41a45fabf1ab6bf500e2152
+#: ../../source/rnotes.rst:312 ../../source/rnotes.rst:837
+msgid ""
+"If local storage paths are found to have a trailing forward slash, remove "
+"it:"
+msgstr ""
+
+# bc2246bf393547aabcf817be27dc60c7
+#: ../../source/rnotes.rst:321
+msgid ""
+"If you are using Ubuntu, follow this procedure to upgrade your packages. If "
+"not, skip to step `12 <#upgrade-rpm-packages-4.3>`__."
+msgstr ""
+
+# b59040bf9a744dbf82ee0fd68cd8c137
+# 5a90c117d3be4bd2bf7438b0a446a878
+# 1683f96797754542a758f642d4f4fae1
+# 8027b164288e47328241d47cb193a0a7
+# 71ef1804ff0c40ca91afd6189a4e564d
+#: ../../source/rnotes.rst:324 ../../source/rnotes.rst:851
+#: ../../source/rnotes.rst:1408 ../../source/rnotes.rst:1850
+#: ../../source/rnotes.rst:2680
+msgid ""
+"**Community Packages:** This section assumes you're using the community "
+"supplied packages for CloudStack. If you've created your own packages and "
+"APT repository, substitute your own URL for the ones used in these examples."
+msgstr ""
+
+# 56b9d98656664482be98c200f1856254
+# 19351e795331422c98e4a905875390e3
+# 74c4b1459a144077aeb0c9f63951ca2f
+# 231674bdf08047fea592149bf4f4ddb8
+# 0a42937bde294e2091dac1a3a0b86a52
+#: ../../source/rnotes.rst:328 ../../source/rnotes.rst:855
+#: ../../source/rnotes.rst:1412 ../../source/rnotes.rst:1854
+#: ../../source/rnotes.rst:2684
+msgid ""
+"The first order of business will be to change the sources list for each "
+"system with CloudStack packages. This means all management servers, and any "
+"hosts that have the KVM agent. (No changes should be necessary for hosts "
+"that are running VMware or Xen.)"
+msgstr ""
+
+# 5d189abeac584f7f8553e4d41c9965d6
+# 84e85d30c2dd40edbca568d9e419cad0
+# a157030034164bfbb32f6259e6ae759b
+# 9143325723c04e8dbe1773d7762b6ada
+# 5f8137d1d4784df2842e703d772e9d8c
+#: ../../source/rnotes.rst:333 ../../source/rnotes.rst:860
+#: ../../source/rnotes.rst:1417 ../../source/rnotes.rst:1859
+#: ../../source/rnotes.rst:2689
+msgid ""
+"Start by opening ``/etc/apt/sources.list.d/cloudstack.list`` on any systems "
+"that have CloudStack packages installed."
+msgstr ""
+
+# c11b9c6bf46e4ceeb988a252e4a6f44e
+# 66acc455c74e4b60a8a973b187e8db0f
+# 77e3b00fd01a4461b6b56a739374c223
+# 2aa42c46e3d84198bfe64eccc145ab97
+# 59d99fc5fa3e4fe89dded04722ba49bb
+#: ../../source/rnotes.rst:336 ../../source/rnotes.rst:863
+#: ../../source/rnotes.rst:1420 ../../source/rnotes.rst:1862
+#: ../../source/rnotes.rst:2692
+msgid "This file should have one line, which contains:"
+msgstr ""
+
+# 0315b6db253046839da27e9afd21dac8
+# 31b497170b494959b37f944a08fcedd4
+# 43e35965702d4a6f914fe60b4db32d55
+# 236ee7a215514b2f8aaca32f6fc0eb34
+# f95f05a212424cf5bc5d5c55b3e585eb
+#: ../../source/rnotes.rst:342 ../../source/rnotes.rst:869
+#: ../../source/rnotes.rst:1426 ../../source/rnotes.rst:1868
+#: ../../source/rnotes.rst:2698
+msgid "We'll change it to point to the new package repository:"
+msgstr ""
+
+# fe18287ca92649d994652022a0a389fe
+# 7ef37ac6e8b04b51b22655148ee43880
+# b6fdfa285ff04ecd8c6a8d70aca45711
+# b773059057dc4b7a8fdd18420c7aff6b
+# 3344b7380cd54082872676747d07b745
+# 19d0366892ff4b1198fa32bd69859746
+# e2d8d36e8860452a9c23b62f39fd3330
+#: ../../source/rnotes.rst:348 ../../source/rnotes.rst:561
+#: ../../source/rnotes.rst:875 ../../source/rnotes.rst:1093
+#: ../../source/rnotes.rst:1547 ../../source/rnotes.rst:1874
+#: ../../source/rnotes.rst:2819
+msgid ""
+"If you're using your own package repository, change this line to read as "
+"appropriate for your 4.3 repository."
+msgstr ""
+
+# 11d93d2eff9c46d8ad99acb75658a9d0
+# f33a797d7e5a4cb68d5f85f94b785dba
+# d2a25e4c47e8400cba504f5918c6374c
+# 498e43c4b60e42b5a6e92ee3f3fc8423
+# 1fab03282141473daab0aaa3c229441a
+#: ../../source/rnotes.rst:353 ../../source/rnotes.rst:880
+#: ../../source/rnotes.rst:1437 ../../source/rnotes.rst:1879
+#: ../../source/rnotes.rst:2709
+msgid "Now update your apt package list:"
+msgstr ""
+
+# 039423ac897546afa8394f0dc3762981
+# 98851837e2c7438fbb9dd33756aef5c6
+# 198ef0103fda4b0eb4c0bae19000f845
+# b2b659bca4774c74b9b3daf1f509726f
+# 04034e3390cb43938e79c05191907c58
+#: ../../source/rnotes.rst:361 ../../source/rnotes.rst:888
+#: ../../source/rnotes.rst:1445 ../../source/rnotes.rst:1887
+#: ../../source/rnotes.rst:2717
+msgid ""
+"Now that you have the repository configured, it's time to install the "
+"``cloudstack-management`` package. This will pull in any other dependencies "
+"you need."
+msgstr ""
+
+# 71dbbbaa4b0545df97bedc9c6d71c5a8
+# dea91b1d5e664521ae9fe2a0c8c2e92d
+# 8188541359f342f78e5cf9d60d972549
+# 46f51ea2d101426d95c74c17f3dc5cde
+#: ../../source/rnotes.rst:371 ../../source/rnotes.rst:898
+#: ../../source/rnotes.rst:1455 ../../source/rnotes.rst:1897
+msgid "You will need to manually install the ``cloudstack-agent`` package:"
+msgstr ""
+
+# 1ef7dae76e35474393b92874cbb36532
+# 739b3c30b2e04fc398bfd6859b4815fc
+# 209b0d0315264225ab5c6168301135d4
+# 8a235d41942341f3bf47878b970aa03d
+# 513550d9f3f34fdeb7c07f9b2e7afcf3
+#: ../../source/rnotes.rst:378 ../../source/rnotes.rst:905
+#: ../../source/rnotes.rst:1462 ../../source/rnotes.rst:1904
+#: ../../source/rnotes.rst:2734
+msgid ""
+"During the installation of ``cloudstack-agent``, APT will copy your "
+"``agent.properties``, ``log4j-cloud.xml``, and ``environment.properties`` "
+"from ``/etc/cloud/agent`` to ``/etc/cloudstack/agent``."
+msgstr ""
+
+# 9701bd815cf148148208dc7b91302f40
+# a8ae754b5fd04a13a867fc2d3c187ce0
+# 085a733706c546dba0f059578892c4a7
+# a728a0e4c92b44fbba5d0b45d114950d
+# 13448224ffa74fc094bfe11a9115fbfa
+#: ../../source/rnotes.rst:381 ../../source/rnotes.rst:910
+#: ../../source/rnotes.rst:1467 ../../source/rnotes.rst:1909
+#: ../../source/rnotes.rst:2739
+msgid "When prompted whether you wish to keep your configuration, say Yes."
+msgstr ""
+
+# af79487ad81341af8144cc2106099f23
+# 73131961a6d2466ba2717ecee3cdf920
+# 9d016ec139344e6186aa43b71c983a76
+# c9409b4b169746b096a8c48a2d7d1ce2
+# 4dd1829a8065410880bea2c97a9b2fa0
+# 32b52f92d69d4c089d800cd10017471f
+# 4dae2cb96e99419d95c76ea7e705ca00
+# c6f1d3d341e84dd0a7ceddce6c604363
+# 83e25244a86f44339113b774652c1bbf
+# dad75aecbba8407e901a4322bb1eec9f
+#: ../../source/rnotes.rst:386 ../../source/rnotes.rst:586
+#: ../../source/rnotes.rst:915 ../../source/rnotes.rst:1118
+#: ../../source/rnotes.rst:1472 ../../source/rnotes.rst:1577
+#: ../../source/rnotes.rst:1914 ../../source/rnotes.rst:2019
+#: ../../source/rnotes.rst:2744 ../../source/rnotes.rst:2849
+msgid ""
+"Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a "
+"line that reads:"
+msgstr ""
+
+# 48202ecf3c764be3afe78387c441645d
+# a8b296466110468da08acfa6cc535135
+# 0e27905c523846a5b404e94b239aa343
+# f463a9539cd6440fae0efe92c14e90f1
+# e910c345f581438da404660d14d56c36
+# 4e51e4f9328545d6bf02d7de41f3d787
+# 70428b7ab64442af9fd0fac15dca01f7
+# d0451a72b44d4a609356f0537372b57f
+# fd3ad945ef1a48958c77d9e5b5aa0055
+# 9b43bdb2b8664c22a2e2b69038d81093
+#: ../../source/rnotes.rst:394 ../../source/rnotes.rst:594
+#: ../../source/rnotes.rst:923 ../../source/rnotes.rst:1126
+#: ../../source/rnotes.rst:1480 ../../source/rnotes.rst:1585
+#: ../../source/rnotes.rst:1922 ../../source/rnotes.rst:2027
+#: ../../source/rnotes.rst:2752 ../../source/rnotes.rst:2857
+msgid "If not, add the line."
+msgstr ""
+
+# 042c9c6d0f13426387a84291fc291952
+# 03fb714adf8a48aa9d99aabcae5a1610
+# 6351d0f660b14dc499fbf3e875658080
+# 43b1707916e74b7784e3b08a2c6ed881
+# 8f76d80899b34f7ca30adb493f085fef
+# 8efc5c39fdd64533957cc3941da4e1b4
+# 5cfeecd7389e4866acfb4440d0d1c020
+# dae7b83474684e2bb0a24a4589826983
+# e182686d199f4cd6b8e3691430995278
+# b031852eec1a450da4b42dc1c66d7b69
+#: ../../source/rnotes.rst:398 ../../source/rnotes.rst:598
+#: ../../source/rnotes.rst:927 ../../source/rnotes.rst:1130
+#: ../../source/rnotes.rst:1484 ../../source/rnotes.rst:1589
+#: ../../source/rnotes.rst:1926 ../../source/rnotes.rst:2031
+#: ../../source/rnotes.rst:2756 ../../source/rnotes.rst:2861
+msgid "Restart the agent:"
+msgstr ""
+
+# 6081bbfdf7d24c4b8b9ab07614b56273
+# 7c211e87de09465bb5a539ebd4a01754
+#: ../../source/rnotes.rst:408 ../../source/rnotes.rst:937
+msgid ""
+"(VMware only) Additional steps are required for each VMware cluster. These "
+"steps will not affect running guests in the cloud. These steps are required "
+"only for clouds using VMware clusters:"
+msgstr ""
+
+# 34f20e5a1a254983baf1a289562457cc
+# b65cec52a81d40248b4f640d3c356aaa
+#: ../../source/rnotes.rst:414 ../../source/rnotes.rst:943
+msgid "Stop the Management Server:"
+msgstr ""
+
+# 7f9596344d6b4824b56b3e9254bbc16c
+# 36ca6513825a4e8d923a5838a123b0f7
+#: ../../source/rnotes.rst:422 ../../source/rnotes.rst:951
+msgid "Generate the encrypted equivalent of your vCenter password:"
+msgstr ""
+
+# efb6ab9a82e7426e84f110c176a707f6
+# 2198298a7a6842dfb8afd2735968909d
+#: ../../source/rnotes.rst:428 ../../source/rnotes.rst:957
+msgid ""
+"Store the output from this step, we need to add this in cluster\\_details "
+"table and vmware\\_data\\_center tables in place of the plain text password"
+msgstr ""
+
+# 99acd44b40a34912a76fde6eccc9e0a2
+# ed1e34bd9d12479088c430270a20c80e
+#: ../../source/rnotes.rst:434 ../../source/rnotes.rst:963
+msgid ""
+"Find the ID of the row of cluster\\_details table that you have to update:"
+msgstr ""
+
+# 8f3bd3ed0592477f8ceea7930a008d38
+# 631c4f13cefc4c5b94e6f10a94ebfba1
+#: ../../source/rnotes.rst:447 ../../source/rnotes.rst:976
+msgid "Update the plain text password with the encrypted one"
+msgstr ""
+
+# e1f63620a0904624a050970144760d41
+# ba1a7b976ab7471da8f4ae5cc6acc69c
+# 8d017dc5b3614e3786fd14c3f098dd4f
+# 62427dddea394f98a9eac0cb913f80c1
+#: ../../source/rnotes.rst:455 ../../source/rnotes.rst:480
+#: ../../source/rnotes.rst:984 ../../source/rnotes.rst:1009
+msgid "Confirm that the table is updated:"
+msgstr ""
+
+# 2f577273146045c4855666e8069007e6
+# 5a358193fff4466ca2d1afab27a439c3
+#: ../../source/rnotes.rst:463 ../../source/rnotes.rst:992
+msgid ""
+"Find the ID of the correct row of vmware\\_data\\_center that you want to "
+"update"
+msgstr ""
+
+# 44774239c7124aeea278ffd8a1e0ce41
+# 49d7985782fe41b284a9f659a0b07c1c
+#: ../../source/rnotes.rst:472 ../../source/rnotes.rst:1001
+msgid "update the plain text password with the encrypted one:"
+msgstr ""
+
+# 56448a6a49a4408386be85dab4b2315f
+# 1aacd1189d6b4ab7ba4daa2c32937c9a
+#: ../../source/rnotes.rst:488 ../../source/rnotes.rst:1017
+msgid "Start the CloudStack Management server"
+msgstr ""
+
+# b2f224ce5298470e91f2b8d31135cd1e
+# c5bf1bb0d38e4fa5aa1253aaa4abd1a7
+#: ../../source/rnotes.rst:496 ../../source/rnotes.rst:1025
+msgid ""
+"(KVM only) Additional steps are required for each KVM host. These steps will"
+" not affect running guests in the cloud. These steps are required only for "
+"clouds using KVM as hosts and only on the KVM hosts."
+msgstr ""
+
+# f4d538249e0345cab4b0b811c939cb00
+# d50828a7a95f4604b0fa2213975047a5
+#: ../../source/rnotes.rst:503 ../../source/rnotes.rst:1032
+msgid "Configure the CloudStack yum repository as detailed above."
+msgstr ""
+
+# f06d2d146d724032b87cb4226d6fac93
+# 351c9808bd414461b803718057d20224
+# 85cb78aba52f4a3583b5d5faf5143640
+# 4136fdbd755442ddbe031d3bc309e73c
+#: ../../source/rnotes.rst:507 ../../source/rnotes.rst:1036
+#: ../../source/rnotes.rst:2138 ../../source/rnotes.rst:3053
+msgid "Stop the running agent."
+msgstr ""
+
+# 1cb7133384b5402cb2cf14632153c4cd
+# 64a138d932f747c98f6efcb0c8ca0346
+#: ../../source/rnotes.rst:515 ../../source/rnotes.rst:1044
+msgid "Update the agent software."
+msgstr ""
+
+# 9efa8f702b9145af9ec5fdfa36823bbb
+# 9312871613354beb9803f1d746527094
+# 8fba178c912e43a193d037247d356a6d
+# 8d9b6d1f39c14466a3fe4569b44a8595
+#: ../../source/rnotes.rst:523 ../../source/rnotes.rst:1052
+#: ../../source/rnotes.rst:2189 ../../source/rnotes.rst:3111
+msgid "Start the agent."
+msgstr ""
+
+# f86632e46670495698f5d20c200fdd69
+#: ../../source/rnotes.rst:531
+msgid ""
+"If you are using CentOS or RHEL, follow this procedure to upgrade your "
+"packages. If not, skip to step `14 <#restart-system-vms-4.3>`__."
+msgstr ""
+
+# f4329c69f54b476da773a8c35a08e778
+# 85e264dbc7dd4ed19606e6dfa79f9a16
+# 11da3a3cb2d54cdca41f7622006bfbce
+# 4306b36338c846fd8bac053165a33cbf
+# ad1b98990fb64bb3b57c3296a7ea607d
+#: ../../source/rnotes.rst:534 ../../source/rnotes.rst:1066
+#: ../../source/rnotes.rst:1521 ../../source/rnotes.rst:1963
+#: ../../source/rnotes.rst:2793
+msgid ""
+"**Community Packages:** This section assumes you're using the community "
+"supplied packages for CloudStack. If you've created your own packages and "
+"yum repository, substitute your own URL for the ones used in these examples."
+msgstr ""
+
+# 6d6ebc753fba484eb9204b6781fda970
+# e742839c52f640f0a426c73a4fd018df
+#: ../../source/rnotes.rst:538 ../../source/rnotes.rst:1070
+msgid ""
+"The first order of business will be to change the yum repository for each "
+"system with CloudStack packages. This means all management servers, and any "
+"hosts that have the KVM agent."
+msgstr ""
+
+# 3ffbf1503681481e95b4c336a25564e0
+# d9ec84ef6bac453591c608d69295622e
+#: ../../source/rnotes.rst:542 ../../source/rnotes.rst:1074
+msgid ""
+"(No changes should be necessary for hosts that are running VMware or Xen.)"
+msgstr ""
+
+# e894df58f47f40edb96c40339871544b
+# bd819c73ef4845019e7cb1e100c664fe
+# 7fa2b208cd6e45a28e45fd0e3f51b7c3
+# eba94a5371074f1fb589564435926056
+# 1884cef709f34a88abecec2bf3833c3a
+#: ../../source/rnotes.rst:545 ../../source/rnotes.rst:1077
+#: ../../source/rnotes.rst:1531 ../../source/rnotes.rst:1973
+#: ../../source/rnotes.rst:2803
+msgid ""
+"Start by opening ``/etc/yum.repos.d/cloudstack.repo`` on any systems that "
+"have CloudStack packages installed."
+msgstr ""
+
+# ac7e0cad1d17428e896f935bd5c5b384
+# dcbce38317ba4e89b9ef6d2db7c802b2
+# 467cc3a4a560458f9b054f2e58d20ee4
+# 16512f5b43624e84979e9af514a36ab3
+# 707eba890aa945709aa0459269af8308
+#: ../../source/rnotes.rst:548 ../../source/rnotes.rst:1080
+#: ../../source/rnotes.rst:1534 ../../source/rnotes.rst:1976
+#: ../../source/rnotes.rst:2806
+msgid "This file should have content similar to the following:"
+msgstr ""
+
+# babaf567e6f5404483ed6ee0bf637444
+#: ../../source/rnotes.rst:558
+msgid ""
+"If you are using the community provided package repository, change the base "
+"url to http://cloudstack.apt-get.eu/rhel/4.3/"
+msgstr ""
+
+# d89b9a5996ce4f0f9ac0c3e436719fb5
+# b1cfb2c096db48ba93d8b2f09c56031b
+#: ../../source/rnotes.rst:566 ../../source/rnotes.rst:1098
+msgid ""
+"Now that you have the repository configured, it's time to install the "
+"``cloudstack-management`` package by upgrading the older ``cloudstack-"
+"management`` package."
+msgstr ""
+
+# 65f51f39a8bf4fcf8083f0342a056bc5
+# 1a05c4de3f944f14a407be8137766bc0
+# beb8ff931b2a4d8c98c73a4fa8ac4204
+# d74cc786e6214deea323b8028f08a467
+# 83a307beac844266953b7bbed75a7d6e
+#: ../../source/rnotes.rst:576 ../../source/rnotes.rst:1108
+#: ../../source/rnotes.rst:1562 ../../source/rnotes.rst:2004
+#: ../../source/rnotes.rst:2834
+msgid ""
+"For KVM hosts, you will need to upgrade the ``cloud-agent`` package, "
+"similarly installing the new version as ``cloudstack-agent``."
+msgstr ""
+
+# c40af3663afc4704b56545eddb37609c
+# a4c37669c6fd442882bf4165eff9dc21
+#: ../../source/rnotes.rst:608 ../../source/rnotes.rst:1140
+msgid "Now it's time to restart the management server"
+msgstr ""
+
+# ebc23ee9a8fe452a94e969a3b3ed3797
+# bb9d6984a87e48d1a5ffc67450096bb8
+#: ../../source/rnotes.rst:616 ../../source/rnotes.rst:1148
+msgid ""
+"Once you've upgraded the packages on your management servers, you'll need to"
+" restart the system VMs. Ensure that the admin port is set to 8096 by using "
+"the \"integration.api.port\" global parameter. This port is used by the "
+"cloud-sysvmadm script at the end of the upgrade procedure. For information "
+"about how to set this parameter, see \"Setting Global Configuration "
+"Parameters\" in the Installation Guide. Changing this parameter will require"
+" management server restart. Also make sure port 8096 is open in your local "
+"host firewall to do this."
+msgstr ""
+
+# e87299dd3d554c7e805ebe052b4921cb
+# c4d82271ad904af8a92a1ae13e75bf2f
+# b8019db7253342c791c16841737a94c3
+#: ../../source/rnotes.rst:625 ../../source/rnotes.rst:1157
+#: ../../source/rnotes.rst:1603
+msgid ""
+"There is a script that will do this for you, all you need to do is run the "
+"script and supply the IP address for your MySQL instance and your MySQL "
+"credentials:"
+msgstr ""
+
+# 00030e4dafd740129590b1781499186e
+# f68656ca3312479db2afefff67e1bdd6
+# 9cb6b77dd29243c79031b6bd19da51ff
+#: ../../source/rnotes.rst:633 ../../source/rnotes.rst:1165
+#: ../../source/rnotes.rst:1611
+msgid ""
+"You can monitor the log for progress. The process of restarting the system "
+"VMs can take an hour or more."
+msgstr ""
+
+# bccf889f462e49b4b1bb423c1e88b5c8
+# 1ac4420efcdc492f9fb919b61307b42a
+# 5dcddcbb73614aa4af06e592c9348913
+#: ../../source/rnotes.rst:640 ../../source/rnotes.rst:1172
+#: ../../source/rnotes.rst:1618
+msgid "The output to ``sysvm.log`` will look something like this:"
+msgstr ""
+
+# 42227647c4b4492d83c87f97545d5390
+# 8a3282874711468dbaacf5fb628280bf
+#: ../../source/rnotes.rst:653 ../../source/rnotes.rst:1187
+msgid ""
+"**For Xen Hosts: Copy vhd-utils:** This step is only for CloudStack installs"
+" that are using Xen hosts."
+msgstr ""
+
+# 973fb456e9984a6b88e6e3c4df1b77dd
+# a399a1e3318245928b48752177f60df6
+# 7b800cae60f54399a1b3ca872c19412e
+#: ../../source/rnotes.rst:655 ../../source/rnotes.rst:1189
+#: ../../source/rnotes.rst:1631
+msgid ""
+"Copy the file ``vhd-utils`` to ``/usr/share/cloudstack-"
+"common/scripts/vm/hypervisor/xenserver``."
+msgstr ""
+
+# 0c4cb838a9a9481a8d93a180dcc079f8
+#: ../../source/rnotes.rst:659
+msgid "Upgrade from 4.1.x to 4.3"
+msgstr ""
+
+# 68c72fe017a24b6faaa07d9f4d650e5b
+#: ../../source/rnotes.rst:661
+msgid ""
+"This section will guide you from CloudStack 4.1.x versions to CloudStack "
+"4.3."
+msgstr ""
+
+# ab0415d71764422e9cc4345bc744c67f
+#: ../../source/rnotes.rst:682
+msgid ""
+"While running the existing 4.1.x system, log in to the UI as root "
+"administrator."
+msgstr ""
+
+# 5d21f203ae88464ba82a2bb5644b39c6
+#: ../../source/rnotes.rst:786
+msgid ""
+"Create RPM or Debian packages (as appropriate) and a repository from the "
+"4.2.1 source, or check the Apache CloudStack downloads page at "
+"`http://cloudstack.apache.org/downloads.html "
+"<http://cloudstack.apache.org/downloads.html>`__ for package repositories "
+"supplied by community members. You will need them for step `8 <#upgrade-deb-"
+"packages-41to42>`__ or step `11 <#upgrade-rpm-packages-41to42>`__."
+msgstr ""
+
+# 55cd20754528476498956b7167b4dd64
+#: ../../source/rnotes.rst:846
+msgid ""
+"If you are using Ubuntu, follow this procedure to upgrade your packages. If "
+"not, skip to step `11 <#upgrade-rpm-packages-41to42>`__."
+msgstr ""
+
+# ca81934545a041b387b565f0c0413aad
+#: ../../source/rnotes.rst:1060
+msgid ""
+"If you are using CentOS or RHEL, follow this procedure to upgrade your "
+"packages. If not, skip to step `13 <#restart-system-vms-41to42>`__."
+msgstr ""
+
+# ade8209fbda64faba8a63c157b288803
+#: ../../source/rnotes.rst:1090
+msgid ""
+"If you are using the community provided package repository, change the base "
+"url to http://cloudstack.apt-get.eu/rhel/4.2/"
+msgstr ""
+
+# d9130ccbfe84403ab6625f9dfdcab053
+#: ../../source/rnotes.rst:1193
+msgid "Upgrade from 4.0.x to 4.3"
+msgstr ""
+
+# bd7f93faa1db403fa9dd6896441f6009
+#: ../../source/rnotes.rst:1195
+msgid ""
+"This section will guide you from CloudStack 4.0.x versions to CloudStack "
+"4.3."
+msgstr ""
+
+# 72900bd6795d4323b06ce5e775e4281d
+#: ../../source/rnotes.rst:1199
+msgid ""
+"**Package Structure Changes:** The package structure for CloudStack has "
+"changed significantly since the 4.0.x releases. If you've compiled your own "
+"packages, you'll notice that the package names and the number of packages "
+"has changed. This is *not* a bug. However, this *does* mean that the "
+"procedure is not as simple as an ``apt-get upgrade`` or ``yum update``, so "
+"please follow this section carefully."
+msgstr ""
+
+# 9925093a67ba46d4a82afe4983cde3d6
+#: ../../source/rnotes.rst:1212
+msgid ""
+"Create RPM or Debian packages (as appropriate) and a repository from the "
+"4.1.0 source, or check the Apache CloudStack downloads page at "
+"`http://cloudstack.apache.org/downloads.html "
+"<http://cloudstack.apache.org/downloads.html>`__ for package repositories "
+"supplied by community members. You will need them for step `9 <#upgrade-deb-"
+"packages-40to41>`__ or step `10 <#upgrade-rpm-packages-40to41>`__."
+msgstr ""
+
+# e0355ef90969449aa728622612f70057
+#: ../../source/rnotes.rst:1227
+msgid ""
+"While running the existing 4.0.0 system, log in to the UI as root "
+"administrator."
+msgstr ""
+
+# 524983e688224bf18c091cba0ce6ba2c
+#: ../../source/rnotes.rst:1360
+msgid ""
+"Whether you're upgrading a Red Hat/CentOS based system or Ubuntu based "
+"system, you're going to need to stop the CloudStack management server before"
+" proceeding."
+msgstr ""
+
+# c4bb349458c3436aa5064c8348a804cb
+#: ../../source/rnotes.rst:1370
+msgid ""
+"If you have made changes to ``/etc/cloud/management/components.xml``, you'll"
+" need to carry these over manually to the new file, "
+"``/etc/cloudstack/management/componentContext.xml``. This is not done "
+"automatically. (If you're unsure, we recommend making a backup of the "
+"original ``components.xml`` to be on the safe side."
+msgstr ""
+
+# 91d1e1359bf54d59b1b810b6935a20fa
+# 70de4e87d0024a18b3298a6ed81193fb
+#: ../../source/rnotes.rst:1378 ../../source/rnotes.rst:2078
+msgid ""
+"After upgrading to 4.3, API clients are expected to send plain text "
+"passwords for login and user creation, instead of MD5 hash. Incase, api "
+"client changes are not acceptable, following changes are to be made for "
+"backward compatibility:"
+msgstr ""
+
+# 6738c1d868b146448f8933886adfa669
+#: ../../source/rnotes.rst:1383
+msgid ""
+"Modify componentsContext.xml, and make PlainTextUserAuthenticator as the "
+"default authenticator (1st entry in the userAuthenticators adapter list is "
+"default)"
+msgstr ""
+
+# f8b44cf359d148f4b91aab1902dd8495
+#: ../../source/rnotes.rst:1400
+msgid ""
+"PlainTextUserAuthenticator works the same way MD5UserAuthenticator worked "
+"prior to 4.3."
+msgstr ""
+
+# b79f73b2986e4326b50f4543b60a80eb
+#: ../../source/rnotes.rst:1405
+msgid ""
+"If you are using Ubuntu, follow this procedure to upgrade your packages. If "
+"not, skip to step `10 <#upgrade-rpm-packages-40to41>`__."
+msgstr ""
+
+# b5c3c9cedf64481396311fb07233e58b
+#: ../../source/rnotes.rst:1432
+msgid ""
+"If you're using your own package repository, change this line to read as "
+"appropriate for your 4.1.0 repository."
+msgstr ""
+
+# 0eaa898254a64902b5c567db1298842f
+# b871c8f1d0a84e2e861c12292bc46977
+# 8081e0b4d2f64021944ed4638d2d0226
+#: ../../source/rnotes.rst:1494 ../../source/rnotes.rst:1936
+#: ../../source/rnotes.rst:2766
+msgid ""
+"During the upgrade, ``log4j-cloud.xml`` was simply copied over, so the logs "
+"will continue to be added to ``/var/log/cloud/agent/agent.log``. There's "
+"nothing *wrong* with this, but if you prefer to be consistent, you can "
+"change this by copying over the sample configuration file:"
+msgstr ""
+
+# f8f1c5326e634caca24199a666ee0792
+# 81564ab5762b44eda70a58cda80022d2
+# eed567da89fd4e0eb4d3ae5a48a726d6
+#: ../../source/rnotes.rst:1508 ../../source/rnotes.rst:1950
+#: ../../source/rnotes.rst:2780
+msgid ""
+"Once the agent is running, you can uninstall the old cloud-\\* packages from"
+" your system:"
+msgstr ""
+
+# 68ef47a188cb4ef89974f80e71de5475
+#: ../../source/rnotes.rst:1517
+msgid ""
+"If you are using CentOS or RHEL, follow this procedure to upgrade your "
+"packages. If not, skip to step `11 <#restart-system-vms-40to41>`__."
+msgstr ""
+
+# a2c27f6a615f432f92bbf1522037096e
+# 78492d493d8a47c482846c2e22f8a67e
+# eda4705004e144ef847024d20f666082
+#: ../../source/rnotes.rst:1525 ../../source/rnotes.rst:1967
+#: ../../source/rnotes.rst:2797
+msgid ""
+"The first order of business will be to change the yum repository for each "
+"system with CloudStack packages. This means all management servers, and any "
+"hosts that have the KVM agent. (No changes should be necessary for hosts "
+"that are running VMware or Xen.)"
+msgstr ""
+
+# 50534c980d8f486280114b8ca158a788
+#: ../../source/rnotes.rst:1544
+msgid ""
+"If you are using the community provided package repository, change the "
+"baseurl to http://cloudstack.apt-get.eu/rhel/4.1/"
+msgstr ""
+
+# 7ddaef2707504d33bb47147835052b82
+# cf3028e1960b447f901c681d9adc50ad
+# 16364561824242ae97931f392f26b118
+#: ../../source/rnotes.rst:1552 ../../source/rnotes.rst:1994
+#: ../../source/rnotes.rst:2824
+msgid ""
+"Now that you have the repository configured, it's time to install the "
+"``cloudstack-management`` package by upgrading the older ``cloud-client`` "
+"package."
+msgstr ""
+
+# 3b35fa76dd24499599dc04b6fb44d0dc
+# 43cc60efd03844569f473a2ff71e4dfe
+# f4638220dedf413d8516450e9ac81e50
+#: ../../source/rnotes.rst:1570 ../../source/rnotes.rst:2012
+#: ../../source/rnotes.rst:2842
+msgid ""
+"During the installation of ``cloudstack-agent``, the RPM will copy your "
+"``agent.properties``, ``log4j-cloud.xml``, and ``environment.properties`` "
+"from ``/etc/cloud/agent`` to ``/etc/cloudstack/agent``."
+msgstr ""
+
+# 61bde7141a654f528c9308eb8aea7ba9
+#: ../../source/rnotes.rst:1599
+msgid ""
+"Once you've upgraded the packages on your management servers, you'll need to"
+" restart the system VMs. Make sure port 8096 is open in your local host "
+"firewall to do this."
+msgstr ""
+
+# 93c8bb7ab89b4303b1ebaa9983b03b6c
+#: ../../source/rnotes.rst:1629
+msgid ""
+"*For Xen Hosts: Copy vhd-utils:** This step is only for CloudStack installs "
+"that are using Xen hosts."
+msgstr ""
+
+# 59b97f43649345cfbe2049be86d9c389
+#: ../../source/rnotes.rst:1635
+msgid "Upgrade from 3.0.x to 4.3"
+msgstr ""
+
+# 5e32327fa74d40f182eefac57ec8e916
+#: ../../source/rnotes.rst:1637
+msgid ""
+"This section will guide you from Citrix CloudStack 3.0.x to Apache "
+"CloudStack 4.3. Sections that are hypervisor-specific will be called out "
+"with a note."
+msgstr ""
+
+# 1e472e681f1744d2a30240396cb0f661
+#: ../../source/rnotes.rst:1645
+msgid ""
+"While running the existing 3.0.x system, log in to the UI as root "
+"administrator."
+msgstr ""
+
+# c598b4573abc40ef8cb1f8ff3f8ba1b4
+# 287bba7730ba467ab67c78556c15abc0
+# 50c89d21fbe341c0bc10c00240d82caf
+#: ../../source/rnotes.rst:1677 ../../source/rnotes.rst:1703
+#: ../../source/rnotes.rst:1729
+msgid "Zone: Choose the zone where this hypervisor is used used"
+msgstr ""
+
+# 45960608e6c94d5d9d95ee664a2ce3d2
+#: ../../source/rnotes.rst:1751
+msgid ""
+"Watch the screen to be sure that the template downloads successfully and "
+"enters the READY state. Do not proceed until this is successful."
+msgstr ""
+
+# 369af9370c2e41dca9f4bfaf0f1519ab
+# a8d838ac79c247a4afd1a5950dd416b2
+#: ../../source/rnotes.rst:1757 ../../source/rnotes.rst:2587
+msgid ""
+"(KVM on RHEL 6.0/6.1 only) If your existing CloudStack deployment includes "
+"one or more clusters of KVM hosts running RHEL 6.0 or RHEL 6.1, perform the "
+"following:"
+msgstr ""
+
+# f185884dbe5143e4ba60c4a1cc8e7227
+# 4b69e99638574f33ba5cc56e6d049b75
+#: ../../source/rnotes.rst:1763 ../../source/rnotes.rst:2593
+msgid ""
+"Ensure that you upgrade the operating system version on those hosts before "
+"upgrading CloudStack"
+msgstr ""
+
+# f6b49bea48cd44a78ba1ba39ce1d62c9
+# fa9c3347ce1d4ca99fa94db744a028aa
+#: ../../source/rnotes.rst:1766 ../../source/rnotes.rst:2596
+msgid ""
+"To do that, change the yum repository for each system with CloudStack "
+"packages, that implies that all the Management Servers and any hosts that "
+"have the KVM agent."
+msgstr ""
+
+# e3cffd2be44544da877c3ee50b05232c
+# f25e1a97111848df9ad153e4bd8b7ae4
+#: ../../source/rnotes.rst:1772 ../../source/rnotes.rst:2602
+msgid ""
+"Open ``/etc/yum.repos.d/cloudstack.repo`` on any systems that have "
+"CloudStack packages installed."
+msgstr ""
+
+# 30309403085a4433baa9037014c18d72
+# 1eb4b5dfd9ba4c4eb0cc3b4516056dc7
+#: ../../source/rnotes.rst:1777 ../../source/rnotes.rst:2607
+msgid "Edit as follows:"
+msgstr ""
+
+# 6d41dd815dd64a108dd55bdfcea801aa
+# 8015ca898771446d8c032203cb37154f
+#: ../../source/rnotes.rst:1792 ../../source/rnotes.rst:2622
+msgid ""
+"If you are using the community provided package repository, change the "
+"baseurl to http:// cloudstack.apt-get.eu/rhel/4.2/"
+msgstr ""
+
+# f9d19fa077d9497abf70c710a81f4db6
+# 83164b94d94849a68fc3b8dc68a2a054
+#: ../../source/rnotes.rst:1795 ../../source/rnotes.rst:2625
+msgid ""
+"If you are using your own package repository, change this line to read as "
+"appropriate for your 4.2.0 repository."
+msgstr ""
+
+# 37e87120204c4aa9b575d43425c2db54
+# 43ef10811cdb46c8ad19cd456586fbf8
+#: ../../source/rnotes.rst:1800 ../../source/rnotes.rst:2630
+msgid ""
+"Now that you have the repository configured, upgrade the host operating "
+"system from RHEL 6.0 to 6.3:"
+msgstr ""
+
+# 5e5c81225020442e83c240f9c770f4a1
+# dbd504a399f4491591cc84dbe61e67f5
+#: ../../source/rnotes.rst:1809 ../../source/rnotes.rst:2639
+msgid "Stop all Usage Servers if running. Run this on all Usage Server hosts."
+msgstr ""
+
+# 5e48ffe2e97c4830906dbd90fcd3ef5d
+# c455c85393ef42f4a9c1528886c3e09f
+#: ../../source/rnotes.rst:1818 ../../source/rnotes.rst:2648
+msgid "Stop the Management Servers. Run this on all Management Server hosts."
+msgstr ""
+
+# 6969d11093b8440988a59fa1dff6be6e
+# 9c4f5494faa54226bfeea797c0d3bcdf
+#: ../../source/rnotes.rst:1826 ../../source/rnotes.rst:2656
+msgid ""
+"On the MySQL master, take a backup of the MySQL databases. We recommend "
+"performing this step even in test upgrades. If there is an issue, this will "
+"assist with debugging."
+msgstr ""
+
+# 825da40bc5314b5a8b130e89ad1a9a5c
+# 72fb79e016be496fa214442911ce060c
+#: ../../source/rnotes.rst:1830 ../../source/rnotes.rst:2660
+msgid ""
+"In the following commands, it is assumed that you have set the root password"
+" on the database, which is a CloudStack recommended best practice. "
+"Substitute your own MySQL root password."
+msgstr ""
+
+# 26589f96a49f4066bd0ab2a72a1f7317
+# 16d0068c27204a0faa66b905d52befe0
+#: ../../source/rnotes.rst:1841 ../../source/rnotes.rst:2671
+msgid ""
+"Either build RPM/DEB packages as detailed in the Installation Guide, or use "
+"one of the community provided yum/apt repositories to gain access to the "
+"CloudStack binaries."
+msgstr ""
+
+# f056a426534b49afbd1365f026fe2d2b
+#: ../../source/rnotes.rst:1847
+msgid ""
+"If you are using Ubuntu, follow this procedure to upgrade your packages. If "
+"not, skip to step `8 <#upgrade-rpm-packages-302>`__."
+msgstr ""
+
+# 84016fd7d3884343b978b2fd6c708da7
+#: ../../source/rnotes.rst:1959
+msgid ""
+"If you are using CentOS or RHEL, follow this procedure to upgrade your "
+"packages. If not, skip to step `9 <#correct-components-xml-302>`__."
+msgstr ""
+
+# 6cebde363347471d9ddc60b659269ddb
+# 269ad8a52be048a9a1fdbccb09243abb
+#: ../../source/rnotes.rst:1986 ../../source/rnotes.rst:2816
+msgid ""
+"If you are using the community provided package repository, change the "
+"baseurl to http://cloudstack.apt-get.eu/rhel/4.2/"
+msgstr ""
+
+# e6d488cc033942d08f511b1af789458b
+# 90df2c6c84c146b0b44da5df81753bb6
+#: ../../source/rnotes.rst:1989 ../../source/rnotes.rst:2704
+msgid ""
+"If you're using your own package repository, change this line to read as "
+"appropriate for your 4.2.0 repository."
+msgstr ""
+
+# eb96e4c8fee5460c87b905716ccb7e42
+#: ../../source/rnotes.rst:2041
+msgid ""
+"If you have made changes to your copy of "
+"``/etc/cloud/management/components.xml`` the changes will be preserved in "
+"the upgrade. However, you need to do the following steps to place these "
+"changes in a new version of the file which is compatible with version 4.2.0."
+msgstr ""
+
+# aefa34afaad7414d8c78efbb8e62e94c
+#: ../../source/rnotes.rst:2049
+msgid ""
+"Make a backup copy of ``/etc/cloud/management/components.xml``. For example:"
+msgstr ""
+
+# a89a3722670e4031b416e5940ecff4f6
+# 4b5606edfece4d73a061033c44291198
+#: ../../source/rnotes.rst:2058 ../../source/rnotes.rst:2895
+msgid ""
+"Copy ``/etc/cloud/management/components.xml.rpmnew`` to create a new "
+"``/etc/cloud/management/components.xml``:"
+msgstr ""
+
+# 28450742b3f54afc970bb28dc3cb8c55
+#: ../../source/rnotes.rst:2067
+msgid ""
+"Merge your changes from the backup file into the new ``components.xml``."
+msgstr ""
+
+# 602debbc4519432cb9eb5cd657212990
+#: ../../source/rnotes.rst:2074
+msgid ""
+"If you have more than one management server node, repeat the upgrade steps "
+"on each node."
+msgstr ""
+
+# c3a3f8aab28945a38940615c4aa7c674
+# ae12189a99b14d70b751a1a0ad5e8e78
+#: ../../source/rnotes.rst:2083 ../../source/rnotes.rst:2918
+msgid ""
+"Modify componentContext.xml, and make PlainTextUserAuthenticator as the "
+"default authenticator (1st entry in the userAuthenticators adapter list is "
+"default)"
+msgstr ""
+
+# db4b5e693294450689d29e7b397a66e1
+#: ../../source/rnotes.rst:2100
+msgid ""
+"PlainTextUserAuthenticator works the same way MD5UserAuthenticator worked "
+"prior to 4.3"
+msgstr ""
+
+# 5431071dd41c473d9eefccc4845ef2ad
+# 754d5fda4f9443cba5574bf18d1c2299
+#: ../../source/rnotes.rst:2105 ../../source/rnotes.rst:3017
+msgid ""
+"Start the first Management Server. Do not start any other Management Server "
+"nodes yet."
+msgstr ""
+
+# 5ca91f223ce34c07831f7c5423255427
+#: ../../source/rnotes.rst:2112
+msgid ""
+"Wait until the databases are upgraded. Ensure that the database upgrade is "
+"complete. After confirmation, start the other Management Servers one at a "
+"time by running the same command on each node."
+msgstr ""
+
+# 17144f244bcc4d5ba9f0274e3e20dd93
+#: ../../source/rnotes.rst:2116
+msgid ""
+"Failing to restart the Management Server indicates a problem in the upgrade."
+" Having the Management Server restarted without any issues indicates that "
+"the upgrade is successfully completed."
+msgstr ""
+
+# 5e74545331a7449fb38c9b4562ef3a4b
+# 1059ad4546844e30a69e255db2aada33
+#: ../../source/rnotes.rst:2120 ../../source/rnotes.rst:3031
+msgid ""
+"Start all Usage Servers (if they were running on your previous version). "
+"Perform this on each Usage Server host."
+msgstr ""
+
+# c6c743684c67470bb2e60153d066d39f
+#: ../../source/rnotes.rst:2123
+msgid "``# service cloudstack-usage start``"
+msgstr ""
+
+# 494054707df24576ac8b9a414f1a75b1
+#: ../../source/rnotes.rst:2127
+msgid ""
+"Additional steps are required for each KVM host. These steps will not affect"
+" running guests in the cloud. These steps are required only for clouds using"
+" KVM as hosts and only on the KVM hosts."
+msgstr ""
+
+# b80fdea5eb3f43ef82d8f401098353b5
+#: ../../source/rnotes.rst:2133
+msgid ""
+"Configure a yum or apt repository containing the CloudStack packages as "
+"outlined in the Installation Guide."
+msgstr ""
+
+# 5278fa99d8d4485fb30e42c9411a12f2
+#: ../../source/rnotes.rst:2140
+msgid "``# service cloud-agent stop``"
+msgstr ""
+
+# 3c3fe8b7b19e44cba7a79327a4a72112
+#: ../../source/rnotes.rst:2144
+msgid ""
+"Update the agent software with one of the following command sets as "
+"appropriate for your environment."
+msgstr ""
+
+# f03c00458dfd4309b653b7dd9267b42f
+#: ../../source/rnotes.rst:2147
+msgid "``# yum update cloud-*``"
+msgstr ""
+
+# 3675fb43e8734dd49422ab4b442080b1
+#: ../../source/rnotes.rst:2149
+msgid "``# apt-get update``"
+msgstr ""
+
+# c2bd6eec94fd4fd9ad4aab9c609893cc
+#: ../../source/rnotes.rst:2151
+msgid "``# apt-get upgrade cloud-*``"
+msgstr ""
+
+# c0c4fb3a314d4413b307c50a48ae1228
+#: ../../source/rnotes.rst:2155
+msgid ""
+"Edit ``/etc/cloudstack/agent/agent.properties`` to change the resource "
+"parameter from "
+"\"com.cloud.agent.resource.computing.LibvirtComputingResource\" to "
+"\"com.cloud.hypervisor.kvm.resource.LibvirtComputingResource\"."
+msgstr ""
+
+# 83835a68fb204ae89d6b2f7a6ee8aee8
+# b0e1a8285a0147c98f7193cb947e882f
+#: ../../source/rnotes.rst:2162 ../../source/rnotes.rst:3084
+msgid ""
+"Upgrade all the existing bridge names to new bridge names by running this "
+"script:"
+msgstr ""
+
+# d8fdc08185fc413c805ee17b4372bb1f
+# 56421fb2994141eda8d7a9bc86903b3d
+#: ../../source/rnotes.rst:2171 ../../source/rnotes.rst:3093
+msgid "Install a libvirt hook with the following commands:"
+msgstr ""
+
+# 6c0677df0917467dbf0927ad53c70859
+# 14f18389b7ad431cad97054748e80d01
+#: ../../source/rnotes.rst:2181 ../../source/rnotes.rst:3103
+msgid "Restart libvirtd."
+msgstr ""
+
+# 59e801d0ff0e42e9b908096e9b5a2062
+# 3bb319ee2e3f43719b09beb5f4d34eaa
+#: ../../source/rnotes.rst:2197 ../../source/rnotes.rst:3119
+msgid ""
+"When the Management Server is up and running, log in to the CloudStack UI "
+"and restart the virtual router for proper functioning of all the features."
+msgstr ""
+
+# 20f728fcbbd9438086424d593e216d79
+#: ../../source/rnotes.rst:2203
+msgid ""
+"Log in to the CloudStack UI as administrator, and check the status of the "
+"hosts. All hosts should come to Up state (except those that you know to be "
+"offline). You may need to wait 20 or 30 minutes, depending on the number of "
+"hosts."
+msgstr ""
+
+# 241d2aa9891f408790433893448b144f
+#: ../../source/rnotes.rst:2208
+msgid ""
+"Troubleshooting: If login fails, clear your browser cache and reload the "
+"page."
+msgstr ""
+
+# 43b500c7cce54508bdaeb5e51fc1a33b
+#: ../../source/rnotes.rst:2210
+msgid "Do not proceed to the next step until the hosts show in Up state."
+msgstr ""
+
+# cfa256927ea946a88f88826d49bfa779
+#: ../../source/rnotes.rst:2214
+msgid "If you are upgrading from 3.0.x, perform the following:"
+msgstr ""
+
+# 5124cdeeb6af42268826554aa614f454
+#: ../../source/rnotes.rst:2218
+msgid ""
+"Ensure that the admin port is set to 8096 by using the "
+"\"integration.api.port\" global parameter."
+msgstr ""
+
+# 0411036b58574b94ab1ed659570c295c
+#: ../../source/rnotes.rst:2221
+msgid ""
+"This port is used by the cloud-sysvmadm script at the end of the upgrade "
+"procedure. For information about how to set this parameter, see \"Setting "
+"Global Configuration Parameters\" in the Installation Guide."
+msgstr ""
+
+# 176d29df7a7c40b7bc206569b6219a6a
+#: ../../source/rnotes.rst:2228
+msgid "Restart the Management Server."
+msgstr ""
+
+# 5566efe7e7024e038d8e10e4668e527d
+#: ../../source/rnotes.rst:2230
+msgid ""
+"If you don't want the admin port to remain open, you can set it to null "
+"after the upgrade is done and restart the management server."
+msgstr ""
+
+# b12a8c95a4684dc980a18b97519d555b
+#: ../../source/rnotes.rst:2234
+msgid ""
+"Run the ``cloudstack-sysvmadm`` script to stop, then start, all Secondary "
+"Storage VMs, Console Proxy VMs, and virtual routers. Run the script once on "
+"each management server. Substitute your own IP address of the MySQL "
+"instance, the MySQL user to connect as, and the password to use for that "
+"user. In addition to those parameters, provide the ``-c`` and ``-r`` "
+"arguments. For example:"
+msgstr ""
+
+# f3a9c0911690431ba39dd6d5d29cbcb5
+#: ../../source/rnotes.rst:2241
+msgid ""
+"``# nohup cloudstack-sysvmadm -d 192.168.1.5 -u cloud -p password -c -r > "
+"sysvm.log 2>&1 &``"
+msgstr ""
+
+# 5cdd5748449243d6b6854c3569b11961
+#: ../../source/rnotes.rst:2243
+msgid "``# tail -f sysvm.log``"
+msgstr ""
+
+# c6c35f1a472746a5b280f5243f7ca483
+# ea4304f6924c4fb8ae65904191b11ad4
+#: ../../source/rnotes.rst:2245 ../../source/rnotes.rst:3150
+msgid ""
+"This might take up to an hour or more to run, depending on the number of "
+"accounts in the system."
+msgstr ""
+
+# 4bbd312624104a61ae9c776827d49ed6
+#: ../../source/rnotes.rst:2250
+msgid ""
+"If needed, upgrade all Citrix XenServer hypervisor hosts in your cloud to a "
+"version supported by CloudStack 4.3. The supported versions are XenServer "
+"5.6 SP2 and 6.0.2. Instructions for upgrade can be found in the CloudStack "
+"4.3 Installation Guide under \"Upgrading XenServer Versions.\""
+msgstr ""
+
+# 61e3d7fc35a64e39a1c0126e30aa9f36
+#: ../../source/rnotes.rst:2258
+msgid ""
+"Now apply the XenServer hotfix XS602E003 (and any other needed hotfixes) to "
+"XenServer v6.0.2 hypervisor hosts."
+msgstr ""
+
+# 2b43c0fdef414981a2c74e337540748d
+# 66ecdcd2c3d347329b52cbc5d9c18143
+#: ../../source/rnotes.rst:2263 ../../source/rnotes.rst:3236
+msgid "Disconnect the XenServer cluster from CloudStack."
+msgstr ""
+
+# b4f42bd432054b93a4e458abeb8be1b3
+# 9fbe25aec0cb4dd6b085da9b2db82f2b
+#: ../../source/rnotes.rst:2265 ../../source/rnotes.rst:3238
+msgid ""
+"In the left navigation bar of the CloudStack UI, select Infrastructure. "
+"Under Clusters, click View All. Select the XenServer cluster and click "
+"Actions - Unmanage."
+msgstr ""
+
+# 0a388b8fae49416e8c12288175689189
+# 8d4ecaddee81413aaa9ac9fb0eef3260
+#: ../../source/rnotes.rst:2269 ../../source/rnotes.rst:3242
+msgid ""
+"This may fail if there are hosts not in one of the states Up, Down, "
+"Disconnected, or Alert. You may need to fix that before unmanaging this "
+"cluster."
+msgstr ""
+
+# be4bab92baa048a1a64dbcaf3979f1b8
+# b5e3cd4c03914aceb35590d6b2c02390
+#: ../../source/rnotes.rst:2273 ../../source/rnotes.rst:3246
+msgid ""
+"Wait until the status of the cluster has reached Unmanaged. Use the "
+"CloudStack UI to check on the status. When the cluster is in the unmanaged "
+"state, there is no connection to the hosts in the cluster."
+msgstr ""
+
+# 701d735a313646168e9258e68406bd59
+# 3852ebac77a44424a5d3d220ab53ad7f
+#: ../../source/rnotes.rst:2280 ../../source/rnotes.rst:3253
+msgid "To clean up the VLAN, log in to one XenServer host and run:"
+msgstr ""
+
+# 7aef1179327b48fb9d239fb9abb53494
+#: ../../source/rnotes.rst:2282
+msgid "``/opt/xensource/bin/cloud-clean-vlan.sh``"
+msgstr ""
+
+# 16a41fb12fb348b2aef8eef44201dc09
+#: ../../source/rnotes.rst:2286
+msgid ""
+"Now prepare the upgrade by running the following on one XenServer host:"
+msgstr ""
+
+# 2e5c5805788d4619be1bd88edd6d0f8b
+#: ../../source/rnotes.rst:2289
+msgid "``/opt/xensource/bin/cloud-prepare-upgrade.sh``"
+msgstr ""
+
+# f9486dd60039428eb666ccb36df33df2
+#: ../../source/rnotes.rst:2291
+msgid ""
+"If you see a message like \"can't eject CD\", log in to the VM and unmount "
+"the CD, then run this script again."
+msgstr ""
+
+# 1b90ef07720649ef8be857a6b8613995
+#: ../../source/rnotes.rst:2296
+msgid ""
+"Upload the hotfix to the XenServer hosts. Always start with the Xen pool "
+"master, then the slaves. Using your favorite file copy utility (e.g. "
+"WinSCP), copy the hotfixes to the host. Place them in a temporary folder "
+"such as /tmp."
+msgstr ""
+
+# 95579949c0c0468f9fb5a886c0de0067
+# b9c190b4fd614d0596e6cf2a21762978
+#: ../../source/rnotes.rst:2301 ../../source/rnotes.rst:3278
+msgid "On the Xen pool master, upload the hotfix with this command:"
+msgstr ""
+
+# 79193bd7beb24dad8e02baea8f8fc9e1
+#: ../../source/rnotes.rst:2303
+msgid "``xe patch-upload file-name=XS602E003.xsupdate``"
+msgstr ""
+
+# cd7814430ea74a93a70c8f47170bd22d
+# b14b4d4a191a482bb52ea5f049bceac4
+#: ../../source/rnotes.rst:2305 ../../source/rnotes.rst:3284
+msgid ""
+"Make a note of the output from this command, which is a UUID for the hotfix "
+"file. You'll need it in another step later."
+msgstr ""
+
+# eebe6b8f5f8a4a0c8070cb916408f131
+# d73f4217d05a41aeae87769a8d70aaf7
+#: ../../source/rnotes.rst:2308 ../../source/rnotes.rst:3287
+msgid ""
+"(Optional) If you are applying other hotfixes as well, you can repeat the "
+"commands in this section with the appropriate hotfix number. For example, "
+"XS602E004.xsupdate."
+msgstr ""
+
+# 2463a45ebed644d98aa875979171a856
+# ea165db83e0543f3bb9bf43ee31f1b1f
+#: ../../source/rnotes.rst:2312 ../../source/rnotes.rst:3291
+msgid ""
+"Manually live migrate all VMs on this host to another host. First, get a "
+"list of the VMs on this host:"
+msgstr ""
+
+# 097871715cba4ed3a1430cfd45bf432e
+#: ../../source/rnotes.rst:2315
+msgid "``# xe vm-list``"
+msgstr ""
+
+# 91a6615ab8044e81816572579377c718
+# 2fecd03a5f7c4b69ad918cffe23ee336
+#: ../../source/rnotes.rst:2317 ../../source/rnotes.rst:3298
+msgid ""
+"Then use this command to migrate each VM. Replace the example host name and "
+"VM name with your own:"
+msgstr ""
+
+# ed5ae637635a478da7def0f58b94eb48
+#: ../../source/rnotes.rst:2320
+msgid "``# xe vm-migrate live=true host=host-name`` vm=\\ *``VM-name``*"
+msgstr ""
+
+# cdcae2f3667941289d57e72fed7dfa95
+# 1204a1f920a54d19951f8fc3b0ca2d3f
+#: ../../source/rnotes.rst:2322 ../../source/rnotes.rst:3305
+msgid ""
+"**Troubleshooting:** If you see a message like \"You attempted an operation "
+"on a VM which requires PV drivers to be installed but the drivers were not "
+"detected,\" run: ``/opt/xensource/bin/make_migratable.sh b6cf79c8-02ee-050b-"
+"922f-49583d9f1a14``."
+msgstr ""
+
+# 3de97a19518c446c9c3c24206b1891f4
+# dc7e8ff7538740fd8931578db081c519
+#: ../../source/rnotes.rst:2326 ../../source/rnotes.rst:3309
+msgid "Apply the hotfix. First, get the UUID of this host:"
+msgstr ""
+
+# 438b1e95684647569c3783ca16ce0605
+# 6a54b573120547b9b5079d7edb53f67d
+#: ../../source/rnotes.rst:2332 ../../source/rnotes.rst:3313
+msgid ""
+"Then use the following command to apply the hotfix. Replace the example host"
+" UUID with the current host ID, and replace the hotfix UUID with the output "
+"from the patch-upload command you ran on this machine earlier. You can also "
+"get the hotfix UUID by running xe patch-list."
+msgstr ""
+
+# c8ec6b43de33435d85c0053b0105b112
+# 4637156a9b74469299c17305a87ac225
+#: ../../source/rnotes.rst:2344 ../../source/rnotes.rst:3323
+msgid ""
+"Copy the following files from the CloudStack Management Server to the host."
+msgstr ""
+
+# 8bab7909084144539d7f3f0d96f5410d
+# f0830d516fe8489a8e14f4cc87d3bd0b
+#: ../../source/rnotes.rst:2349 ../../source/rnotes.rst:3327
+msgid "Copy from here..."
+msgstr ""
+
+# d661c3f6488e4437bcad12807e868ba6
+# c65616039e844df49a2c66a9e72fab4d
+#: ../../source/rnotes.rst:2349 ../../source/rnotes.rst:3327
+msgid "...to here"
+msgstr ""
+
+# 5d2066c046d54230a20ba472410c9cca
+#: ../../source/rnotes.rst:2351
+msgid ""
+"/usr/lib64/cloud/common /scripts/vm/hypervisor/ xenserver/xenserver60/N "
+"FSSR.py"
+msgstr ""
+
+# 1782bbb0a4484bfda837b67ed08637f5
+#: ../../source/rnotes.rst:2351
+msgid "/opt/xensource/sm/NFSSR.py"
+msgstr ""
+
+# 9083b6c4d0a84550b56d29048de163fd
+#: ../../source/rnotes.rst:2356
+msgid ""
+"/usr/lib64/cloud/common /scripts/vm/hypervisor/ xenserver/setupxenserve r.sh"
+msgstr ""
+
+# cc60a777fdb84763928959eac1413256
+#: ../../source/rnotes.rst:2356
+msgid "/opt/xensource/bin/setupxenserver.sh"
+msgstr ""
+
+# 7f602a64a7384f1faeeb3cd3cb6906c8
+#: ../../source/rnotes.rst:2361
+msgid ""
+"/usr/lib64/cloud/common /scripts/vm/hypervisor/ xenserver/make\\_migrata "
+"ble.sh"
+msgstr ""
+
+# fd8304dd4b4745048ca492d792e96336
+#: ../../source/rnotes.rst:2361
+msgid "/opt/xensource/bin/make\\_migratable.sh"
+msgstr ""
+
+# 1189f098e11e4821b8dd6002d4701b37
+# 0b20faf71a1d4b488f695e1121d2fce8
+#: ../../source/rnotes.rst:2370 ../../source/rnotes.rst:3347
+msgid ""
+"(Only for hotfixes XS602E005 and XS602E007) You need to apply a new Cloud "
+"Support Pack."
+msgstr ""
+
+# 51314060eb4e4274a94556cf66d7b8f5
+# 6f0e38b936c146a88f18f01bd79fb137
+#: ../../source/rnotes.rst:2375 ../../source/rnotes.rst:3352
+msgid ""
+"Download the CSP software onto the XenServer host from one of the following "
+"links:"
+msgstr ""
+
+# 7960ce9d01764dca84c420221f5ac947
+# 2b5b6fb5241d45ca94ee8aee0c067700
+#: ../../source/rnotes.rst:2378 ../../source/rnotes.rst:3355
+msgid ""
+"For hotfix XS602E005: "
+"`http://coltrane.eng.hq.xensource.com/release/XenServer-6.x/XS-6.0.2/hotfixes/XS602E005/56710"
+"/xe-phase-2/xenserver-cloud-supp.tgz "
+"<http://coltrane.eng.hq.xensource.com/release/XenServer-6.x/XS-6.0.2/hotfixes/XS602E005/56710"
+"/xe-phase-2/xenserver-cloud-supp.tgz>`__"
+msgstr ""
+
+# 93f404dfecb845f7a295abed79cd2bdc
+# 1e9987f14ee140caab3cd9ac80fb3d70
+#: ../../source/rnotes.rst:2381 ../../source/rnotes.rst:3358
+msgid ""
+"For hotfix XS602E007: "
+"`http://coltrane.eng.hq.xensource.com/release/XenServer-6.x/XS-6.0.2/hotfixes/XS602E007/57824"
+"/xe-phase-2/xenserver-cloud-supp.tgz "
+"<http://coltrane.eng.hq.xensource.com/release/XenServer-6.x/XS-6.0.2/hotfixes/XS602E007/57824"
+"/xe-phase-2/xenserver-cloud-supp.tgz>`__"
+msgstr ""
+
+# 5487658881254252bc032a418bc9d211
+# d5d3595872834a30b69f2a97f934a6b6
+#: ../../source/rnotes.rst:2386 ../../source/rnotes.rst:3363
+msgid "Extract the file:"
+msgstr ""
+
+# 10aadbef588b4906aa4411610fff2b38
+# 41fba79ec98c4ba9bb33a5ece8089e84
+#: ../../source/rnotes.rst:2394 ../../source/rnotes.rst:3369
+msgid "Run the following script:"
+msgstr ""
+
+# 304c43ec19654d4facc909cee84b878e
+# 6f36c01dad0c4038b06f62939ceb97c4
+#: ../../source/rnotes.rst:2402 ../../source/rnotes.rst:3375
+msgid ""
+"If the XenServer host is part of a zone that uses basic networking, disable "
+"Open vSwitch (OVS):"
+msgstr ""
+
+# 196938b763f24a729f0d5fc34034cf8d
+# 97f83d0655ca49899c2f7b23cf07100d
+#: ../../source/rnotes.rst:2411 ../../source/rnotes.rst:3382
+msgid "Reboot this XenServer host."
+msgstr ""
+
+# 2b44592533884e89a228bd0a5f8e8a24
+# c82ea223be1d4b64adaed5f89d77845f
+# ba507e290ab84df6bee757006448475b
+# 723c48dca8094e9da7624f83d2ac56c7
+#: ../../source/rnotes.rst:2415 ../../source/rnotes.rst:2425
+#: ../../source/rnotes.rst:3386 ../../source/rnotes.rst:3394
+msgid "Run the following:"
+msgstr ""
+
+# 60d0028a822d4455a2ef0e71a774fc89
+# 3c2b4eb2c1a34738a8fee6a813020cc8
+#: ../../source/rnotes.rst:2421 ../../source/rnotes.rst:3390
+msgid ""
+"If the message \"mv: cannot stat \\`/etc/cron.daily/logrotate': No such file"
+" or directory\" appears, you can safely ignore it."
+msgstr ""
+
+# e365729bdd0a43d98ca4aa6df76a080a
+# 292dce1c5566443db1f36434502cbe40
+#: ../../source/rnotes.rst:2433 ../../source/rnotes.rst:3402
+msgid ""
+"On each slave host in the Xen pool, repeat these steps, starting from "
+"\"manually live migrate VMs.\""
+msgstr ""
+
+# 53aa4ba520af4d32a111c7bdd061c7f6
+#: ../../source/rnotes.rst:2436
+msgid ""
+"**Troubleshooting Tip:** If passwords which you know to be valid appear not "
+"to work after upgrade, or other UI issues are seen, try clearing your "
+"browser cache and reloading the UI page."
+msgstr ""
+
+# 82f67a0f08f74ea0b372cfc3d9798cff
+#: ../../source/rnotes.rst:2439
+msgid "Upgrade from 2.2.14 to 4.3"
+msgstr ""
+
+# 8dd5152530dc4c448bc7ca2147bb3f58
+#: ../../source/rnotes.rst:2443
+msgid ""
+"Ensure that you query your IPaddress usage records and process them; for "
+"example, issue invoices for any usage that you have not yet billed users "
+"for."
+msgstr ""
+
+# 08a3e11c4ac84d15a5539ea1a29e5540
+#: ../../source/rnotes.rst:2447
+msgid ""
+"Starting in 3.0.2, the usage record format for IP addresses is the same as "
+"the rest of the usage types. Instead of a single record with the assignment "
+"and release dates, separate records are generated per aggregation period "
+"with start and end dates. After upgrading to 4.3, any existing IP address "
+"usage records in the old format will no longer be available."
+msgstr ""
+
+# 82d3912ade2e4425b10822ef75644184
+#: ../../source/rnotes.rst:2456
+msgid ""
+"If you are using version 2.2.0 - 2.2.13, first upgrade to 2.2.14 by using "
+"the instructions in the `2.2.14 Release Notes "
+"<http://download.cloud.com/releases/2.2.0/CloudStack2.2.14ReleaseNotes.pdf>`__."
+msgstr ""
+
+# 43af6a2f821148dc933817dda7004642
+#: ../../source/rnotes.rst:2460
+msgid ""
+"**KVM Hosts:** If KVM hypervisor is used in your cloud, be sure you "
+"completed the step to insert a valid username and password into the "
+"host\\_details table on each KVM node as described in the 2.2.14 Release "
+"Notes. This step is critical, as the database will be encrypted after the "
+"upgrade to 4.3."
+msgstr ""
+
+# 165a6cb6d6d14af88d88b0b78f71157f
+#: ../../source/rnotes.rst:2464
+msgid ""
+"While running the 2.2.14 system, log in to the UI as root administrator."
+msgstr ""
+
+# 1f8e9d1a6daa49ee9369d371b139cfd1
+#: ../../source/rnotes.rst:2469
+msgid ""
+"Using the UI, add a new System VM template for each hypervisor type that is "
+"used in your cloud. In each zone, add a system VM template for each "
+"hypervisor used in that zone"
+msgstr ""
+
+# 61df5a92c7374826b61d112059dfcf30
+#: ../../source/rnotes.rst:2489
+msgid ""
+"In the Register template dialog box, specify the following values depending "
+"on the hypervisor type (do not change these):"
+msgstr ""
+
+# cf7180ae32be4c09baac3d08c8d8592f
+#: ../../source/rnotes.rst:2575
+msgid ""
+"Watch the screen to be sure that the template downloads successfully and "
+"enters the READY state. Do not proceed until this is successful"
+msgstr ""
+
+# abd7c11dce0748e393edeabe2b1a3c88
+#: ../../source/rnotes.rst:2580
+msgid ""
+"**WARNING**: If you use more than one type of hypervisor in your cloud, be "
+"sure you have repeated these steps to download the system VM template for "
+"each hypervisor type. Otherwise, the upgrade will fail."
+msgstr ""
+
+# 944b4efebb274b4b9168b8c9bc07cd2d
+#: ../../source/rnotes.rst:2677
+msgid ""
+"If you are using Ubuntu, follow this procedure to upgrade your packages. If "
+"not, skip to step `13 <#upgrade-rpm-packages-22>`__."
+msgstr ""
+
+# 5621f0bde6ef435598eb9f26e3dad529
+#: ../../source/rnotes.rst:2727
+msgid ""
+"On KVM hosts, you will need to manually install the ``cloudstack-agent`` "
+"package:"
+msgstr ""
+
+# 203132db7f3948499d31bb3eb0057291
+#: ../../source/rnotes.rst:2789
+msgid ""
+"If you are using CentOS or RHEL, follow this procedure to upgrade your "
+"packages. If not, skip to step `14 <#correct-components-xml-22>`__."
+msgstr ""
+
+# 690f899c6bd24183860a840ddf554d44
+#: ../../source/rnotes.rst:2871
+msgid ""
+"If you have made changes to your existing copy of the file components.xml in"
+" your previous-version CloudStack installation, the changes will be "
+"preserved in the upgrade. However, you need to do the following steps to "
+"place these changes in a new version of the file which is compatible with "
+"version 4.0.0-incubating."
+msgstr ""
+
+# b2fef2e295cf40a6b3777a62e5e8dd89
+#: ../../source/rnotes.rst:2877
+msgid ""
+"How will you know whether you need to do this? If the upgrade output in the "
+"previous step included a message like the following, then some custom "
+"content was found in your old components.xml, and you need to merge the two "
+"files:"
+msgstr ""
+
+# 28092dbc6a1e4c8b8b40af19e0361a7a
+#: ../../source/rnotes.rst:2886
+msgid ""
+"Make a backup copy of your ``/etc/cloud/management/components.xml`` file. "
+"For example:"
+msgstr ""
+
+# ce76e70e3d0d4085b429224f3c46f5f0
+#: ../../source/rnotes.rst:2904
+msgid ""
+"Merge your changes from the backup file into the new components.xml file."
+msgstr ""
+
+# 5d31708084ea431cb32c6de017984b9d
+#: ../../source/rnotes.rst:2913
+msgid ""
+"After upgrading to 4.3, API clients are expected to send plain text "
+"passwords for login and user creation, instead of MD5 hash. If API client "
+"changes are not acceptable, following changes are to be made for backward "
+"compatibility:"
+msgstr ""
+
+# 3e13a458fcec46348d78d6a05c0a73f2
+#: ../../source/rnotes.rst:2936
+msgid ""
+"PlainTextUserAuthenticator works the same way MD5UserAuthenticator worked "
+"prior to 4.2."
+msgstr ""
+
+# 977e0462a4514e8290c4f6efb24ffbc6
+#: ../../source/rnotes.rst:2941
+msgid ""
+"If you have made changes to your existing copy of the "
+"``/etc/cloud/management/db.properties`` file in your previous-version "
+"CloudStack installation, the changes will be preserved in the upgrade. "
+"However, you need to do the following steps to place these changes in a new "
+"version of the file which is compatible with this version."
+msgstr ""
+
+# 6f3fecf7bee440819bd35439052e7134
+#: ../../source/rnotes.rst:2950
+msgid ""
+"Make a backup copy of your file ``/etc/cloud/management/db.properties``. For"
+" example:"
+msgstr ""
+
+# 1e4702a05d304ef4a3d18a310670413b
+#: ../../source/rnotes.rst:2959
+msgid ""
+"Copy ``/etc/cloud/management/db.properties.rpmnew`` to create a new "
+"``/etc/cloud/management/db.properties``:"
+msgstr ""
+
+# 2a689fd4c8b34f159bbccda75eea3b44
+#: ../../source/rnotes.rst:2968
+msgid ""
+"Merge your changes from the backup file into the new db.properties file."
+msgstr ""
+
+# 14c9f00e13384fe7818635db57ddebbe
+#: ../../source/rnotes.rst:2977
+msgid ""
+"On the management server node, run the following command. It is recommended "
+"that you use the command-line flags to provide your own encryption keys. See"
+" Password and Key Encryption in the Installation Guide."
+msgstr ""
+
+# 3f168b18c27443dd875c5adeb55a85a0
+#: ../../source/rnotes.rst:2986
+msgid ""
+"When used without arguments, as in the following example, the default "
+"encryption type and keys will be used:"
+msgstr ""
+
+# 33bee02a88e14c6f8726562c1066932f
+#: ../../source/rnotes.rst:2991
+msgid ""
+"(Optional) For encryption\\_type, use file or web to indicate the technique "
+"used to pass in the database encryption password. Default: file."
+msgstr ""
+
+# da3a05583c554e95a25b01ea4b2fab78
+#: ../../source/rnotes.rst:2997
+msgid ""
+"(Optional) For management\\_server\\_key, substitute the default key that is"
+" used to encrypt confidential parameters in the properties file. Default: "
+"password. It is highly recommended that you replace this with a more secure "
+"value"
+msgstr ""
+
+# d47187c0a6934275b49e5f7142bf2a49
+#: ../../source/rnotes.rst:3004
+msgid ""
+"(Optional) For database\\_key, substitute the default key that is used to "
+"encrypt confidential parameters in the CloudStack database. Default: "
+"password. It is highly recommended that you replace this with a more secure "
+"value."
+msgstr ""
+
+# a1b1f1666d0e4e5fa004939d7cb65ebb
+#: ../../source/rnotes.rst:3011
+msgid ""
+"Repeat steps 10 - 14 on every management server node. If you provided your "
+"own encryption key in step 14, use the same key on all other management "
+"servers."
+msgstr ""
+
+# d2b6a61b4d4c4ea4ac31966205b494e9
+#: ../../source/rnotes.rst:3024
+msgid ""
+"Wait until the databases are upgraded. Ensure that the database upgrade is "
+"complete. You should see a message like \"Complete! Done.\" After "
+"confirmation, start the other Management Servers one at a time by running "
+"the same command on each node."
+msgstr ""
+
+# d3aa8aeaac984b868f7bb6203777068c
+#: ../../source/rnotes.rst:3040
+msgid "(KVM only) Perform the following additional steps on each KVM host."
+msgstr ""
+
+# 7f58ac6f2a6546e984b291d14708aecd
+#: ../../source/rnotes.rst:3042
+msgid ""
+"These steps will not affect running guests in the cloud. These steps are "
+"required only for clouds using KVM as hosts and only on the KVM hosts."
+msgstr ""
+
+# a40f34aedd354e19b622dba6af947dc9
+#: ../../source/rnotes.rst:3048
+msgid ""
+"Configure your CloudStack package repositories as outlined in the "
+"Installation Guide"
+msgstr ""
+
+# 60b6f718e10b44b2932fe47305402e68
+#: ../../source/rnotes.rst:3061
+msgid ""
+"Update the agent software with one of the following command sets as "
+"appropriate."
+msgstr ""
+
+# d1c9b23bfd3047b3af0434ee9d2f4b81
+#: ../../source/rnotes.rst:3075
+msgid ""
+"Copy the contents of the ``agent.properties`` file to the new "
+"``agent.properties`` file by using the following command"
+msgstr ""
+
+# f29b1de1f5784d40a03f632bee5da0c8
+#: ../../source/rnotes.rst:3125
+msgid ""
+"Log in to the CloudStack UI as admin, and check the status of the hosts. All"
+" hosts should come to Up state (except those that you know to be offline). "
+"You may need to wait 20 or 30 minutes, depending on the number of hosts."
+msgstr ""
+
+# 5d312c8c705f4c878ea150dab52c575d
+#: ../../source/rnotes.rst:3130
+msgid ""
+"Do not proceed to the next step until the hosts show in the Up state. If the"
+" hosts do not come to the Up state, contact support."
+msgstr ""
+
+# 25837b241e564dd7a200dc22ed3e929b
+#: ../../source/rnotes.rst:3135
+msgid ""
+"Run the following script to stop, then start, all Secondary Storage VMs, "
+"Console Proxy VMs, and virtual routers."
+msgstr ""
+
+# ac2edfb7c37b4bf994275e773d12c5c4
+#: ../../source/rnotes.rst:3140
+msgid ""
+"Run the command once on one management server. Substitute your own IP "
+"address of the MySQL instance, the MySQL user to connect as, and the "
+"password to use for that user. In addition to those parameters, provide the "
+"\"-c\" and \"-r\" arguments. For example:"
+msgstr ""
+
+# 62fdd3c67b9b4b9cb1c6ecce251c6b5a
+#: ../../source/rnotes.rst:3155
+msgid ""
+"After the script terminates, check the log to verify correct execution:"
+msgstr ""
+
+# 47faf7f70b334ae98f3f1c7a670a311f
+#: ../../source/rnotes.rst:3162
+msgid "The content should be like the following:"
+msgstr ""
+
+# cf26992fc5ea49f8a46b7c97db3db2db
+#: ../../source/rnotes.rst:3175
+msgid ""
+"If you would like additional confirmation that the new system VM templates "
+"were correctly applied when these system VMs were rebooted, SSH into the "
+"System VM and check the version."
+msgstr ""
+
+# d907b5857e874ddb9e2685400bdaa324
+#: ../../source/rnotes.rst:3179
+msgid "Use one of the following techniques, depending on the hypervisor."
+msgstr ""
+
+# 47eeb152f7354386a945820cf565dd7d
+#: ../../source/rnotes.rst:3181
+msgid "**XenServer or KVM:**"
+msgstr ""
+
+# 4845c8f916aa46c8b0afb4d65839827a
+#: ../../source/rnotes.rst:3183
+msgid ""
+"SSH in by using the link local IP address of the system VM. For example, in "
+"the command below, substitute your own path to the private key used to log "
+"in to the system VM and your own link local IP."
+msgstr ""
+
+# fd4e4c86a1e44bb184899f9b2f2a2215
+#: ../../source/rnotes.rst:3188
+msgid ""
+"Run the following commands on the XenServer or KVM host on which the system "
+"VM is present:"
+msgstr ""
+
+# 9fb15734392e492db8eec3bfd8db8456
+# 3d3c3fffab7445d18c30fce3880b7b1c
+#: ../../source/rnotes.rst:3196 ../../source/rnotes.rst:3215
+msgid "The output should be like the following:"
+msgstr ""
+
+# 6c25de5d57584107bb52f4b83298476e
+#: ../../source/rnotes.rst:3202
+msgid "**ESXi:**"
+msgstr ""
+
+# 1c5098a14ab44e28bbc70f3c2c27f1b8
+#: ../../source/rnotes.rst:3204
+msgid ""
+"SSH in using the private IP address of the system VM. For example, in the "
+"command below, substitute your own path to the private key used to log in to"
+" the system VM and your own private IP."
+msgstr ""
+
+# 1ea48fa0ab9a49cd99f56b64aeeff8cf
+#: ../../source/rnotes.rst:3208
+msgid "Run the following commands on the Management Server:"
+msgstr ""
+
+# 2de578dee3164dc9b979d4322ff158fe
+#: ../../source/rnotes.rst:3223
+msgid ""
+"If needed, upgrade all Citrix XenServer hypervisor hosts in your cloud to a "
+"version supported by CloudStack 4.0.0-incubating. The supported versions are"
+" XenServer 5.6 SP2 and 6.0.2. Instructions for upgrade can be found in the "
+"CloudStack 4.0.0-incubating Installation Guide."
+msgstr ""
+
+# 78d0d9395c604a4c805ddfec475f15bb
+#: ../../source/rnotes.rst:3231
+msgid ""
+"Apply the XenServer hotfix XS602E003 (and any other needed hotfixes) to "
+"XenServer v6.0.2 hypervisor hosts."
+msgstr ""
+
+# aaa65cee9a6f430bac41e5738591839d
+#: ../../source/rnotes.rst:3261
+msgid "Prepare the upgrade by running the following on one XenServer host:"
+msgstr ""
+
+# 7d50c3d8799447ff89c8c364eb70731d
+#: ../../source/rnotes.rst:3268
+msgid ""
+"If you see a message like \"can't eject CD\", log in to the VM and umount "
+"the CD, then run this script again."
+msgstr ""
+
+# 933303f89e9f4fdbb4693a289c7f28cb
+#: ../../source/rnotes.rst:3273
+msgid ""
+"Upload the hotfix to the XenServer hosts. Always start with the Xen pool "
+"master, then the slaves. Using your favorite file copy utility (e.g. "
+"WinSCP), copy the hotfixes to the host. Place them in a temporary folder "
+"such as /root or /tmp."
+msgstr ""
+
+# be996cb933684ad28c8d1a0fc11b51f3
+#: ../../source/rnotes.rst:3311
+msgid "``# xe host-list``"
+msgstr ""
+
+# 8b48b679d3034863a0cf33f4243733e0
+#: ../../source/rnotes.rst:3319
+msgid "``xe patch-apply host-uuid=host-uuid`` uuid=\\ *``hotfix-uuid``*"
+msgstr ""
+
+# fba81dae9aa141759a651c9681d452ca
+#: ../../source/rnotes.rst:3329
+msgid ""
+"``/usr/share/cloudstack -common/scripts/vm/hype rvisor/xenserver/xenser "
+"ver60/NFSSR.py``"
+msgstr ""
+
+# f17727fee8de4422b1854899f586b480
+#: ../../source/rnotes.rst:3329
+msgid "``/opt/xensource/sm/NFSSR.py``"
+msgstr ""
+
+# 8b641d51a32547f6bacbfdf2b6a2bf14
+#: ../../source/rnotes.rst:3334
+msgid ""
+"``/usr/share/cloudstack -common/scripts/vm/hype rvisor/xenserver/setupx "
+"enserver.sh``"
+msgstr ""
+
+# e5244c3c204643cbac950d4ef0a3e6c7
+# 15d387013eea4eb2b0bb7d051beed7ad
+#: ../../source/rnotes.rst:3334 ../../source/rnotes.rst:3388
+msgid "``/opt/xensource/bin/setupxenserver.sh``"
+msgstr ""
+
+# 46501ce5ab894a74ada10967a82596af
+#: ../../source/rnotes.rst:3339
+msgid ""
+"``/usr/lib64/cloudstack -common/scripts/vm/hype rvisor/xenserver/make_m "
+"igratable.sh``"
+msgstr ""
+
+# ae866867817d4b3aa8dee6324cad801d
+#: ../../source/rnotes.rst:3339
+msgid "``/opt/xensource/bin/make_migratable.sh``"
+msgstr ""
+
+# d1c878ddd25d437b89be1fe7935981a0
+#: ../../source/rnotes.rst:3365
+msgid "``# tar xf xenserver-cloud-supp.tgz``"
+msgstr ""
+
+# be55bf39cd3b47ae95be10e364d38068
+#: ../../source/rnotes.rst:3371
+msgid "``# xe-install-supplemental-pack xenserver-cloud-supp.iso``"
+msgstr ""
+
+# 511effdc9d26448290f575384afe0676
+#: ../../source/rnotes.rst:3378
+msgid "``# xe-switch-network-backend bridge``"
+msgstr ""
diff --git a/source/upgrading/locale/pot/.doctrees/about.doctree b/source/upgrading/locale/pot/.doctrees/about.doctree
new file mode 100644
index 0000000..3d92a96
--- /dev/null
+++ b/source/upgrading/locale/pot/.doctrees/about.doctree
Binary files differ
diff --git a/source/upgrading/locale/pot/.doctrees/api-changes.doctree b/source/upgrading/locale/pot/.doctrees/api-changes.doctree
new file mode 100644
index 0000000..07a5469
--- /dev/null
+++ b/source/upgrading/locale/pot/.doctrees/api-changes.doctree
Binary files differ
diff --git a/source/upgrading/locale/pot/.doctrees/compat.doctree b/source/upgrading/locale/pot/.doctrees/compat.doctree
new file mode 100644
index 0000000..a567b00
--- /dev/null
+++ b/source/upgrading/locale/pot/.doctrees/compat.doctree
Binary files differ
diff --git a/source/upgrading/locale/pot/.doctrees/environment.pickle b/source/upgrading/locale/pot/.doctrees/environment.pickle
new file mode 100644
index 0000000..d5e1b2a
--- /dev/null
+++ b/source/upgrading/locale/pot/.doctrees/environment.pickle
Binary files differ
diff --git a/source/upgrading/locale/pot/.doctrees/index.doctree b/source/upgrading/locale/pot/.doctrees/index.doctree
new file mode 100644
index 0000000..0b3e9dd
--- /dev/null
+++ b/source/upgrading/locale/pot/.doctrees/index.doctree
Binary files differ
diff --git a/source/upgrading/locale/pot/.doctrees/rnotes.doctree b/source/upgrading/locale/pot/.doctrees/rnotes.doctree
new file mode 100644
index 0000000..0d6e200
--- /dev/null
+++ b/source/upgrading/locale/pot/.doctrees/rnotes.doctree
Binary files differ
diff --git a/source/upgrading/locale/pot/about.pot b/source/upgrading/locale/pot/about.pot
new file mode 100644
index 0000000..37253ca
--- /dev/null
+++ b/source/upgrading/locale/pot/about.pot
@@ -0,0 +1,4903 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 10:50-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../about.rst:17
+# bdb91b47a91143f1a9fbaaf76b791a2f
+msgid "About this new Release"
+msgstr ""
+
+#: ../../about.rst:20
+# 09ea19a83f3c45fbb713eecff4f4479a
+msgid "What's New in 4.3"
+msgstr ""
+
+#: ../../about.rst:22
+# a7450e3fb9a743108c319a9af9fe1b80
+msgid "CloudStack 4.3 includes the following new features."
+msgstr ""
+
+#: ../../about.rst:25
+# de565510abed48d8af44eb5fdb96baa6
+msgid "Optional 64-Bit System VM Template Support"
+msgstr ""
+
+#: ../../about.rst:27
+# 048e4ce62ed244bba8e86b18d88f3a34
+msgid "CloudStack now provides 64-bit templates for System VMs. With this support, you will be able to upgrade virtual routers in a zone. The following parameters have been introduced for the same purpose:"
+msgstr ""
+
+#: ../../about.rst:33
+# 3ff7bc12fd3a40168e34b0756ea6a56d
+msgid "XenServer: *``router.template.xen``*"
+msgstr ""
+
+#: ../../about.rst:37
+# 0f83f7b6fbfe4d9d83c9434fe623902f
+msgid "KVM: *``router.template.kvm``*"
+msgstr ""
+
+#: ../../about.rst:41
+# 2f7e453939514853b250feb502b7b5e4
+msgid "VMware:"
+msgstr ""
+
+#: ../../about.rst:45
+# 788a74eec57b416b98f7fe353645942d
+msgid "Hyper-V:"
+msgstr ""
+
+#: ../../about.rst:48
+# bf5c467f2c6942ed83e6d9bd84f1b336
+msgid "Hyper-V Support"
+msgstr ""
+
+#: ../../about.rst:50
+# a68a0a054365438c8cf07088b31c3f67
+msgid "CloudStack 4.3 rolls out support for Hyper-V hosts. For Hyper-V, CloudStack supports SMB-based storage. If you want to run guest VMs on Hyper-V hosts, install CloudStack Agents on each Hyper-V hosts. Before you use Hyper-V, review the following list of supported and non-supported features. For detailed instruction, see Hyper-V Quick Start Guide. You can also see the chapter Installing Hyper-V for CloudStack in the CloudStack 4.3 Installation Guide."
+msgstr ""
+
+#: ../../about.rst:59
+# f42fefd9b0704bbd8914c2fc900378e5
+msgid "Supported Functionalities on Hyper-V"
+msgstr ""
+
+#: ../../about.rst:63
+# 8a08c075dad842ae989d94c62ee4c170
+msgid "VM Compute"
+msgstr ""
+
+#: ../../about.rst:67
+# 4a23fdd07b4545a8a2471b9e7858afb0
+msgid "All the VM operations, except VM Snapshots"
+msgstr ""
+
+#: ../../about.rst:71
+# 0853f620548b45c58c3f661681d49db6
+msgid "Live Migration"
+msgstr ""
+
+#: ../../about.rst:75
+# 7f73d6bfa5414af29f7bd70a2f166f2a
+msgid "Service Offerings (Scale up on stopped VMs)"
+msgstr ""
+
+#: ../../about.rst:79
+# 2901e1e3a3ee4f318bee5841071d11f4
+msgid "Console access"
+msgstr ""
+
+#: ../../about.rst:83
+# e9f0cf1c36e34061a4430368430f8b7e
+msgid "SSH key and reseting SSH key"
+msgstr ""
+
+#: ../../about.rst:87
+# 61f557f1ec2841b3b5b64dded25a56ba
+msgid "Upload and download templates, volumes, and ISO"
+msgstr ""
+
+#: ../../about.rst:91
+# c07f2d55f8364cd8b0050aa4d3d54382
+msgid "Create VMs from template and ISO"
+msgstr ""
+
+#: ../../about.rst:95
+# f9b15aeb193941e79220d19f3dce562e
+msgid "Create template from volume"
+msgstr ""
+
+#: ../../about.rst:99
+# 8ccfe45c544e4c638d9f4a12b6436cd9
+msgid "Attach and detach VMs from ISO and password-enabled template"
+msgstr ""
+
+#: ../../about.rst:103
+# d387c492ad4a4f27ae58eab3f0f892a3
+msgid "Copy template across zone"
+msgstr ""
+
+#: ../../about.rst:107
+# cc1d8aed652142ca8d18086e70eccad4
+msgid "Storage"
+msgstr ""
+
+#: ../../about.rst:111
+# 0991d5f6fea746e1b06907ae0bb63f74
+msgid "Primary Storage (SMB and Local)"
+msgstr ""
+
+#: ../../about.rst:115
+# ebc4eb92938f4a3f9061c8321002678d
+msgid "Root and data volumes on Local and SMB"
+msgstr ""
+
+#: ../../about.rst:119
+# 9c6c606883c340a88101911897eb1ac5
+msgid "Add, delete, attach, detach volumes (one or more volumes per VM)"
+msgstr ""
+
+#: ../../about.rst:123
+# 932392fdf2984fe7a875e41f9de7de60
+msgid "Single and multiple secondary storage (SMB)"
+msgstr ""
+
+#: ../../about.rst:127
+# f7cc1aa8312e47ef9e0b9f2046dc6f12
+msgid "Network"
+msgstr ""
+
+#: ../../about.rst:131
+# b13ad43288b34c5398b4fd4904be20dc
+msgid "VLANs (Isolated and Shared)"
+msgstr ""
+
+#: ../../about.rst:135
+# 874f9b3d2c9e4b4f8fb45f9baee22bfe
+msgid "All VR services: DNS, DHCP, SourceNAT, LB, PF, Firewall, StaticNAT, Userdata, and VPN"
+msgstr ""
+
+#: ../../about.rst:140
+# 09421e4ea4d148e68b8d1e37a762586f
+msgid "External device support for both Isolated and Shared networks: Netscaler, SRX, F5"
+msgstr ""
+
+#: ../../about.rst:145
+# d07e8aa630494fa7938a2cf213bd9991
+msgid "Multiple physical networks"
+msgstr ""
+
+#: ../../about.rst:149
+# d100215a6752462ea07718f52c810c16
+msgid "Dedicated IP range, Public VLANs (to account)"
+msgstr ""
+
+#: ../../about.rst:153
+# 0a27b6bb4a754d9e993d9562c77a4ff7
+msgid "Network Offering upgrades and updates"
+msgstr ""
+
+#: ../../about.rst:157
+# 9c4055c13dcd4ca8926e5a28c1b8ab50
+msgid "L4-L7 services in Shared network"
+msgstr ""
+
+#: ../../about.rst:161
+# aa7a95d118364e49979f5adbcb3b0d39
+msgid "Multiple IP ranges and portable IPs"
+msgstr ""
+
+#: ../../about.rst:165
+# 5669e604b4b64897aa6b5ed794b76f5c
+msgid "Host and Storage in maintenance mode"
+msgstr ""
+
+#: ../../about.rst:168
+# fafdc4c1cbd7484b9f05f44fe7260546
+msgid "Unsupported Functionalities on Hyper-V"
+msgstr ""
+
+#: ../../about.rst:172
+# 9126bf9e82bc45e499dc89df7fc0a0f6
+msgid "Affinity an Anti-Affinity Groups"
+msgstr ""
+
+#: ../../about.rst:176
+# 546d2df63ef44bd590e7adcbb31589d7
+msgid "Network throttling"
+msgstr ""
+
+#: ../../about.rst:180
+# 0f4fe83217294fdfb3c4c04617eadef1
+msgid "Security groups (Advanced Zone)"
+msgstr ""
+
+#: ../../about.rst:184
+# 03d2119aa0234ee693ad12ab0d2d118a
+msgid "IPv6"
+msgstr ""
+
+#: ../../about.rst:188
+# d8f2d2b85d76482995ae6d639cc00f3c
+msgid "Snapshot: VM and disk"
+msgstr ""
+
+#: ../../about.rst:192
+# 52ea53b1bd254148bc10e6d3cca67a40
+msgid "PVLAN"
+msgstr ""
+
+#: ../../about.rst:196
+# 7eea4c2b16d94da0bec010bdd4499b75
+msgid "VPC"
+msgstr ""
+
+#: ../../about.rst:200
+# 0ca54967dd9542c2ad230764eec58cb4
+msgid "HA of guest VMs"
+msgstr ""
+
+#: ../../about.rst:204
+# ebfed36bc2b14ce2aaba7818affa537f
+msgid "Redundant VR"
+msgstr ""
+
+#: ../../about.rst:208
+# 18a3cf7e8d6349fab3e8accbd101ea23
+msgid "Object Store"
+msgstr ""
+
+#: ../../about.rst:212
+# 9ec4ba65baa94d5b8771ce1920e78f4e
+msgid "Mixed hypervisor zone"
+msgstr ""
+
+#: ../../about.rst:216
+# 287a5e396359407d97733e009c86b208
+msgid "Zone-wide Primary storage"
+msgstr ""
+
+#: ../../about.rst:220
+# dbebd6f68c114cc98c2feda96bda8339
+msgid "NIC bonding"
+msgstr ""
+
+#: ../../about.rst:223
+# 1219852e8e6d45d29136897552f0a79e
+msgid "Enhanced Upgrade for Virtual Routers"
+msgstr ""
+
+#: ../../about.rst:225
+# b3c22859d0dd4066b256bbe41f847bc4
+msgid "Upgrading VRs is made flexible. The CloudStack administrators will be able to control the sequence of the VR upgrades. The sequencing is based on Infrastructure hierarchy, such as by Cluster, Pod, or Zone, and Administrative hierarchy, such as by Tenant or Domain. This implies, for example, that you will have the flexibility to upgrade a VR in a specified zone. As an administrator, you can also determine when a particular VR can be upgraded within a specified upgrade interval. Additionally, upgrade operation is enhanced to increase the upgrade speed by allowing as many upgrade operations in parallel as possible. During the entire duration of the upgrade, users cannot launch new services or make changes to an existing service."
+msgstr ""
+
+#: ../../about.rst:237
+# 40bdf0a308c2489bb98e96a62d75e548
+msgid "To support this feature, a new API, upgradeRouterTemplate, has been introduced."
+msgstr ""
+
+#: ../../about.rst:240
+# d37f3bc214424defab5f024e87d6f9e9
+msgid "The detailed instruction is provided in the CloudStack 4.3 Administration Guide. See section 17.5.5. Enhanced Upgrade for Virtual Routers."
+msgstr ""
+
+#: ../../about.rst:244
+# 1978f680828e42a6a20bf3259d22a92e
+msgid "Service Monitoring Tool for Virtual Router"
+msgstr ""
+
+#: ../../about.rst:246
+# a4902af1b3fd4bb0ab166c3d3f9feeb1
+msgid "Various services running on the CloudStack virtual routers can be monitored by using a Service Monitoring tool. The tool ensures that services are successfully running until CloudStack deliberately disables them. If a service goes down, the tool automatically performs a restart, and if that does not help bringing up the service, an alert as well as an event is generated indicating the failure."
+msgstr ""
+
+#: ../../about.rst:253
+# 667326bf4c7f4e58865496ef24d6f564
+msgid "The following services are monitored in a VR:"
+msgstr ""
+
+#: ../../about.rst:257
+# 024d834f741b41bebab0bdcecdf5d5e1
+msgid "DNS"
+msgstr ""
+
+#: ../../about.rst:261
+# ff61c6894d1f44528fb0cfaee5973892
+msgid "HA Proxy"
+msgstr ""
+
+#: ../../about.rst:265
+# 7292e272f40f42efa8b4a31dd617fcc4
+msgid "SSH"
+msgstr ""
+
+#: ../../about.rst:269
+# f8d9969dc6d543c4806e00250dcdc745
+msgid "Apache Web Server"
+msgstr ""
+
+#: ../../about.rst:271
+# 2dcd9edec1a04f5d879c7a2b5356f1df
+msgid "Only the services with daemons are monitored."
+msgstr ""
+
+#: ../../about.rst:273
+# 8e45915127fd4804a98e10f181e8c8c3
+msgid "The following networks are supported:"
+msgstr ""
+
+#: ../../about.rst:277
+# 85dab6977a0742da917c0892ea590cf9
+msgid "Isolated Networks"
+msgstr ""
+
+#: ../../about.rst:281
+# f171266ce0c248d2910f9f10eaab6565
+msgid "Shared Networks in both Advanced and Basic zone"
+msgstr ""
+
+#: ../../about.rst:283
+# c6bc2910647143b29bce7ea3161423c1
+msgid "This feature is supported on the following hypervisors: XenServer, VMware, and KVM."
+msgstr ""
+
+#: ../../about.rst:286
+# aeaf1c1efba14b47ab9c6dd048ac9991
+msgid "The detailed instruction is provided in the CloudStack 4.3 Administration Guide. See section 17.5.4. Service Monitoring Tool for Virtual Router."
+msgstr ""
+
+#: ../../about.rst:290
+# e765090bf54a460ca6a394879a4846dd
+msgid "Custom Compute Offering"
+msgstr ""
+
+#: ../../about.rst:292
+# c58cbd0661224b5aaba9862a0f2aa92d
+msgid "CloudStack provides you the flexibility to specify the desired values for the number of CPU, CPU speed, and memory while deploying a VM. The admin creates a Compute Offering by marking it as custom, and as an user, you will be able to customize this dynamic Compute Offering by specifying the memory, CPU and root disk at the time of VM creation or upgrade."
+msgstr ""
+
+#: ../../about.rst:299
+# 3fddca4fb9da49ad86402020e89a2f67
+msgid "Custom Compute Offering is same as the normal Compute Offering except that the values of the dynamic parameters will be set to zeros in the given set of templates. Use this offering to deploy VM by specifying custom values for the dynamic parameters. Memory, CPU and number of CPUs are considered as dynamic parameters. Dynamic Compute Offerings can be used in following cases: deploying a VM, changing the compute offering of a stopped VM and running VMs, which is nothing but scaling up. To support this feature a new field, Custom, has been added to the Create Compute Offering page. If the Custom field is checked, the end-user will be able to create a custom Compute Offering by filling in the desired values for number of CPU, CPU speed, and memory."
+msgstr ""
+
+#: ../../about.rst:312
+# c45fbc9d5812419d8e5659b31d9a3701
+msgid "Remote Access VPN for VPC"
+msgstr ""
+
+#: ../../about.rst:314
+# 3a53541d7f42456aaa3fbf0e9f0d580b
+msgid "Support for Remote access VPN in Isolated networks is now extended to VPC networks. Remote users will now be able to initiate a VPN connection to a VPC network. To enable this feature, enable VPN in the Source NAT IP of the VPC."
+msgstr ""
+
+#: ../../about.rst:320
+# 951c3222d442439fb978cd6154b138f1
+msgid "Site to Site VPN Connection Between VPC Networks"
+msgstr ""
+
+#: ../../about.rst:322
+# 6a62ba77cd734a75b07d944e8a858de2
+msgid "CloudStack provides you with the ability to establish a site-to-site VPN connection between CloudStack virtual routers. With this functionality, users can deploy applications in multiple Availability Zones or VPCs, which can communicate with each other by using a secure Site-to-Site VPN Tunnel. Creating a typical Site to Site VPN connection between VPC networks involves the following:"
+msgstr ""
+
+#: ../../about.rst:331
+# 32395b38487f4fb1af795d6cac8d420a
+msgid "Create two VPCs. For example, VPC A and VPC B."
+msgstr ""
+
+#: ../../about.rst:335
+# 6c1e1dbd31244723b14cd116e34cffbb
+msgid "Create VPN gateways on both the VPCs you created."
+msgstr ""
+
+#: ../../about.rst:339
+# 29cbe5a50cf245608e0cec45c87e90f9
+msgid "Create VPN customer gateway for both the VPCs."
+msgstr ""
+
+#: ../../about.rst:343
+# 6a8a8359c0974163b9dd4016bfee540e
+msgid "Enable a VPN connection on VPC A in passive mode."
+msgstr ""
+
+#: ../../about.rst:345
+# 4615ac14561345f1943cce5fdd745216
+msgid "Ensure that the customer gateway is pointed to VPC B. The VPN connection is shown in the Disconnected state."
+msgstr ""
+
+#: ../../about.rst:350
+# ac948a0813e74cefbba1495ce1d94a01
+msgid "Enable a VPN connection on VPC B."
+msgstr ""
+
+#: ../../about.rst:352
+# cc7322058e944ab2b238719fbd79390a
+msgid "Ensure that the customer gateway is pointed to VPC A. Because virtual router of VPC A, in this case, is in passive mode and is waiting for the virtual router of VPC B to initiate the connection. The virtual router of VPC B should not be in passive mode."
+msgstr ""
+
+#: ../../about.rst:357
+# 92ba5b7586c349e6b946c1d46be6fb2d
+msgid "The VPN connection is shown in the Disconnected state."
+msgstr ""
+
+#: ../../about.rst:359
+# 1fa6614237044be1b758972b7f138f61
+msgid "Creating VPN connection on both the VPCs initiates a VPN connection. Wait for few seconds. The default is 30 seconds for both the VPN connections to show the Connected state."
+msgstr ""
+
+#: ../../about.rst:364
+# 7f80e1e445fc4471be85c99f9a63fae1
+msgid "Reporting CPU Sockets"
+msgstr ""
+
+#: ../../about.rst:366
+# 8cdc324e21274d65bb9c00645c27eedc
+msgid "CloudStack now provides an additional infrastructure statistics for CPU sockets managed by CloudStack, which in turn reflects the size of the cloud. The Infrastructure tab has a new tab for sockets. The Socket page will give you the number of hosts an sockets used for each hypervisor type. This feature is not supported in versions prior to XenServer 6.2."
+msgstr ""
+
+#: ../../about.rst:373
+# 3b300053085f4c51865c61cee31b9c86
+msgid "Database High Availability"
+msgstr ""
+
+#: ../../about.rst:375
+# 2d55be3748744201aecff258124d7a84
+msgid "To help ensure high availability of the databases that store the internal data for CloudStack, you can set up database replication. This covers both the main CloudStack database and the Usage database. Replication is achieved using the MySQL connector parameters and two-way replication. Tested with MySQL 5.1 and 5.5. Database replication in CloudStack is provided using the MySQL replication capabilities. The steps to set up replication can be found in the MySQL documentation."
+msgstr ""
+
+#: ../../about.rst:384
+# ff5e8279823b47249d289b0f66b569c6
+msgid "LDAP User Provisioning"
+msgstr ""
+
+#: ../../about.rst:386
+# 3ce8e3c638fe4a5da87bf86da7c0eb78
+msgid "LDAP user provisioning has been enhanced by allowing user import from the configured LDAP servers. You will be able to add multiple LDAP servers and selectively import LDAP users. You can o filter by group name and import all the users within a group. After they have been imported to CloudStack, in contrast to manually adding them in previous releases, users are allowed to directly log in to CloudStack by using the LDAP credentials."
+msgstr ""
+
+#: ../../about.rst:395
+# 3536819d2546433fb18b893f551a10c9
+msgid "Migrating NFS Secondary Storage to Object Store"
+msgstr ""
+
+#: ../../about.rst:397
+# b6682b07f6e948b499fdd7d6fe164d92
+msgid "In an existing zone that is using NFS for secondary storage, you can upgrade the zone to use a region-wide object storage without causing downtime. The existing NFS storage in the zone will be converted to an NFS Staging Store. After migration, the data that was on the NFS storage remains there. CloudStack does not provide a way to automatically migrate all data to the new object storage. The data remaining on the old NFS storage will remain accessible for read and delete operations only. Newly created snapshots and templates will be placed in the newly configured object storage."
+msgstr ""
+
+#: ../../about.rst:408
+# e2059568a2df4bd5823a5b7f17d09451
+msgid "VXLAN Plugin Support"
+msgstr ""
+
+#: ../../about.rst:410
+# 1e4361812f7d4a5aa2ac245baace915f
+msgid "The VXLAN plugin adds VXLAN as one of the guest network isolation methods in CloudStack. This plugin enables more than 4096 isolated guest networks in a Zone, with almost the same usability as VLAN isolation. This plugin provides no network services. Use virtual router for network services. This plugin is supported on KVM hypervisors."
+msgstr ""
+
+#: ../../about.rst:417
+# d5b76aea4bbb47b38bdd2659da294eed
+msgid "Contrail Network Plugin Support"
+msgstr ""
+
+#: ../../about.rst:419
+# d6f33ea8933841f98efa3b797425049e
+msgid "The Contrail virtual network controller is an open source project that provides an overlay implementation of network virtualization that is interoperable with network devices that support existing network virtualization standards. Support for the Contrail plugin has been added to CloudStack to provide NAT services to the XenServer hosts. The plugin supports isolated networks, Static NAT implemented by the VRouter dataplane, and Source NAT implemented by using a virtual appliance with full NAT functionality."
+msgstr ""
+
+#: ../../about.rst:429
+# 3f923c411f0246ddb382b9bb3b20fb63
+msgid "Publishing Alert Using the Web ROOT Admin API"
+msgstr ""
+
+#: ../../about.rst:431
+# 3866fb1f0a18405198edcc6ab7bf458f
+msgid "In previous releases of CloudStack code alerts are generated for CloudStack services (Usage service) only if they run on the same host as the Management Server. A new API has been introduced in 4.3, which can be used by the following services to generate and publish. The services need not be running on the same host where the Management Server is running."
+msgstr ""
+
+#: ../../about.rst:440
+# 8410cc0152774785aa48177c60589ab7
+msgid "Any new services added to CloudStack."
+msgstr ""
+
+#: ../../about.rst:444
+# 2aac9dee470c48fcb30e45594d822e46
+msgid "Usage service when run on a separate storage host."
+msgstr ""
+
+#: ../../about.rst:448
+# 8301f6de87114eed8372e75dc7d59c01
+msgid "Console Proxy and Secondary Storage VM services."
+msgstr ""
+
+#: ../../about.rst:450
+# 20d5528dcc9a40ba86ec266cc41fe9dd
+msgid "The main advantage of this feature is that the third party systems integrating with CloudStack will be able to utilize the Alert notification system publish alerts."
+msgstr ""
+
+#: ../../about.rst:455
+# 7219cbc180f64a2b84a6532d69e2c13f
+msgid "Support for Palo Alto Firewall Service"
+msgstr ""
+
+#: ../../about.rst:457
+# d8a2ab915328485b9e95aed7718895a4
+msgid "CloudStack supports Palo Alto firewall services. Use the Create Network Offering dialog to create an offering which has the Palo Alto firewall services. What is not supported and not supported are given below:"
+msgstr ""
+
+#: ../../about.rst:462
+# 5ab19452ad294aa0806ad47fa2098aa5
+msgid "Supported Functionalities"
+msgstr ""
+
+#: ../../about.rst:466
+# 645c0421480840e9b6980b1f944f8795
+msgid "Advanced Network"
+msgstr ""
+
+#: ../../about.rst:470
+# c934ca9385b04727a43ab39071588b72
+msgid "Parallel deployment with hardware Load balancer"
+msgstr ""
+
+#: ../../about.rst:474
+# 6447c3aa0d3143a7b4a3891d0f352ef5
+msgid "Virtual Palo Alto firewall."
+msgstr ""
+
+#: ../../about.rst:478
+# c63825cf282044879a8196691680be29
+msgid "Communication layer with Palo Alto APIs."
+msgstr ""
+
+#: ../../about.rst:482
+# 8d42e63976974e58b7f330f3578a2aef
+msgid "Mapping of CloudStack APIs to corresponding Palo Alto APIs."
+msgstr ""
+
+#: ../../about.rst:486
+# 37177f839d2741ef96c21c7f4767ac31
+msgid "Connectivity status of the firewall service on the CloudStack UI."
+msgstr ""
+
+#: ../../about.rst:489
+# 9e019a8a7e544690a3ee5874ec53f2e4
+msgid "Unsupported Functionalities"
+msgstr ""
+
+#: ../../about.rst:493
+# dfc850c506da4331992314cc0926b8c2
+msgid "Inline deployment with hardware Load balancer"
+msgstr ""
+
+#: ../../about.rst:497
+# decfb6946f324fe6b1594ba57d060e25
+msgid "Firewall between VLANs within an advanced network"
+msgstr ""
+
+#: ../../about.rst:501
+# 2c9f38f5cbe243208141b854a0892bee
+msgid "Firewall between VM instances"
+msgstr ""
+
+#: ../../about.rst:503
+# 289436a898b443cda15f4015c790ce78
+msgid "For more information, see `Palo Alto Firewall Integration <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Palo+Alto+Firewall+Integration>`__."
+msgstr ""
+
+#: ../../about.rst:507
+# 677b559b98014a0ca9160b277b871fd9
+msgid "Root Volume Metering"
+msgstr ""
+
+#: ../../about.rst:509
+# b0a9b0c2ced04a849783e40601c1c455
+msgid "CloudStack supports recording usage events as per the dynamically assigned resources. Usage events are registered when a VM is created from dynamic service offering, and the values of parameters, such as CPU, speed, RAM are recorded. If VM is deployed by using template and dynamic root disk size is mentioned, the same value is recorded in the usage event."
+msgstr ""
+
+#: ../../about.rst:517
+# c50214ba81b249a595f65e7546f35f8c
+msgid "Support for SSL Termination"
+msgstr ""
+
+#: ../../about.rst:519
+# 7671dd6babb446dca44a477d3e09f8f5
+msgid "SSL Offloading allows load balancers to handle encryption and decryption of HTTP(s) traffic giving plain text HTTP to the back end servers freeing them from the resource intensive task of handling encryption and decryption. Supported for Citrix NetScaler."
+msgstr ""
+
+#: ../../about.rst:525
+# a657b31bba0d477381342a4169e672a8
+msgid "Support for Pluggable VM Snapshots"
+msgstr ""
+
+#: ../../about.rst:527
+# 97c95ed5aa4648bab662e6f3a68ca4c7
+msgid "CloudStack implements a plugin to integrate a third-party storage provider. Third party storage providers can integrate with CloudStack to provide either primary storage or secondary storage. The user enables a storage plugin through the UI. A new dialog box choice is offered to select the storage provider. Depending on which provider is selected, additional input fields may appear so that the user can provide the additional details required by that provider, such as a user name and password for a third-party storage account."
+msgstr ""
+
+#: ../../about.rst:537
+# 613dd9e315124de1873cca35dd5d16b9
+msgid "Enhanced CloudStack UI"
+msgstr ""
+
+#: ../../about.rst:539
+# e96027034f66405aa2305070f44d66e7
+msgid "A complete UI makeover is implemented to enhance the usability and user experience in modern browsers. The visual look-and-feel has been changed for the Header, Navigation, Buttons, text fields, drop-downs, tables and so on. Consistent color themes has been introduced to match with the Apache branding."
+msgstr ""
+
+#: ../../about.rst:545
+# 0c948052a4214991b7464682f517292d
+msgid "The current UI flow remains the same."
+msgstr ""
+
+#: ../../about.rst:548
+# 079640b7b7b64cd39436ad9200c35f48
+msgid "Depreciation of realhostip.com DNS and SSL certificate"
+msgstr ""
+
+#: ../../about.rst:549
+# a04ae7e6daff4b42a2724df6a1b224d8
+msgid "The realhostip.com dynamic DNS resolution service is being retired this summer. In advance of that, CloudStack 4.3 no longer uses realhostip.com DNS domains or SSL certificates to encrypt Console Proxy or file copy communications."
+msgstr ""
+
+#: ../../about.rst:555
+# 1ab3e4e99a8342078cde95b5a5edba35
+msgid "Issues Fixed in 4.3.0"
+msgstr ""
+
+#: ../../about.rst:557
+#: ../../about.rst:732
+# 952dc9ec1db44f2d83a142ae895eb79b
+# b659d6162a3e49bfab48e1304597c5c1
+msgid "Apache CloudStack uses `Jira <https://issues.apache.org/jira/browse/CLOUDSTACK>`__ to track its issues. All new features and bugs for 4.3 have been tracked in Jira, and have a standard naming convention of \"CLOUDSTACK-NNNN\" where \"NNNN\" is the issue number."
+msgstr ""
+
+#: ../../about.rst:560
+# e477344cc35049a28eb3809f6f6b4a70
+msgid "For the list of issues fixed, see `Issues Fixed in 4.3 <https://issues.apache.org/jira/issues/?filter=12326161>`__."
+msgstr ""
+
+#: ../../about.rst:564
+#: ../../about.rst:739
+# 19c393aa43644c4490205799f532afe1
+# f19ac9d2986d450c8fef7d562c66ca50
+msgid "Bug ID"
+msgstr ""
+
+#: ../../about.rst:564
+#: ../../about.rst:739
+# 24a0954d4ea547449bdcfd807a54c2c7
+# cddb8801a6e64717b905df373c4dde4d
+msgid "Description"
+msgstr ""
+
+#: ../../about.rst:566
+# a43fa93540ee49e28a672d3f5bcc387a
+msgid "`CLOUDSTACK-6103 <https://issues.apache.org/jira/browse/CLOUDSTACK-6103>`_"
+msgstr ""
+
+#: ../../about.rst:566
+# 172a3e260cc043038020f4dceb7d5a0c
+msgid "vms with isos attached don't migrate..."
+msgstr ""
+
+#: ../../about.rst:567
+# aad0e8086ae546b8a875996d93b928c5
+msgid "`CLOUDSTACK-6089 <https://issues.apache.org/jira/browse/CLOUDSTACK-6089>`_"
+msgstr ""
+
+#: ../../about.rst:567
+# 4ff487a8cd9f41688c7249ebc52abe3b
+msgid "resource tags show up in multiples..."
+msgstr ""
+
+#: ../../about.rst:568
+# 92e3feccfc9f4657bdecbd3b99b54d45
+msgid "`CLOUDSTACK-6046 <https://issues.apache.org/jira/browse/CLOUDSTACK-6046>`_"
+msgstr ""
+
+#: ../../about.rst:568
+# e137bb96bac543349f0016165abe9bc3
+msgid "CreateVolume from snapshot is failing with S3 as secondary storage and zone-wide..."
+msgstr ""
+
+#: ../../about.rst:569
+# 27d6b9e3aab54128a4f0aad5c984f3b0
+msgid "`CLOUDSTACK-6040 <https://issues.apache.org/jira/browse/CLOUDSTACK-6040>`_"
+msgstr ""
+
+#: ../../about.rst:569
+# cccd886a01824191afea0e7730507e27
+msgid "Failed to configure PF on vm secondary ip for shared network..."
+msgstr ""
+
+#: ../../about.rst:570
+# 85eb969880864b4d9cef31eb992935c3
+msgid "`CLOUDSTACK-6007 <https://issues.apache.org/jira/browse/CLOUDSTACK-6007>`_"
+msgstr ""
+
+#: ../../about.rst:570
+# f613c25ec8e34d1a9eaad46ce27933e8
+msgid "[VMware] RestoreVM API fails with NPE..."
+msgstr ""
+
+#: ../../about.rst:571
+# fd7f4037eceb48d2b0b81c6513e3208b
+msgid "`CLOUDSTACK-5986 <https://issues.apache.org/jira/browse/CLOUDSTACK-5986>`_"
+msgstr ""
+
+#: ../../about.rst:571
+# f6112b6f33c74c498637f7599dacd888
+msgid "dnsmasq racy condition result in dnsmasq failed to handout IP address..."
+msgstr ""
+
+#: ../../about.rst:572
+# 848d35efab59400d907ff4c154ad7db3
+msgid "`CLOUDSTACK-5971 <https://issues.apache.org/jira/browse/CLOUDSTACK-5971>`_"
+msgstr ""
+
+#: ../../about.rst:572
+# 9165b730c684401bb0d160785380a8e9
+msgid "Templates created from a snapshots can't be copied to other zones..."
+msgstr ""
+
+#: ../../about.rst:573
+# 2fd9b8e5e39e4420a4c49090c6000892
+msgid "`CLOUDSTACK-5960 <https://issues.apache.org/jira/browse/CLOUDSTACK-5960>`_"
+msgstr ""
+
+#: ../../about.rst:573
+# af22070e3f9a4fd38055612952644a67
+msgid "Domain admin or user cannot register a template using S3/Swift object store..."
+msgstr ""
+
+#: ../../about.rst:574
+# 8397aeab15e044a8b1b6c72c46f83c25
+msgid "`CLOUDSTACK-5922 <https://issues.apache.org/jira/browse/CLOUDSTACK-5922>`_"
+msgstr ""
+
+#: ../../about.rst:574
+# 930ae632e9514c60bed68a9d53ea1ffb
+msgid "Incorrect handling RHEL guests ..."
+msgstr ""
+
+#: ../../about.rst:575
+# ee730af6c476432cb966506d5a88c89e
+msgid "`CLOUDSTACK-5921 <https://issues.apache.org/jira/browse/CLOUDSTACK-5921>`_"
+msgstr ""
+
+#: ../../about.rst:575
+# dee97e2e870f433096e88d01b05c8e62
+msgid "S3 security key is stored in DB unencrypted..."
+msgstr ""
+
+#: ../../about.rst:576
+# 93ad54e6b1d44a3ab0ccdb3cdff12008
+msgid "`CLOUDSTACK-5903 <https://issues.apache.org/jira/browse/CLOUDSTACK-5903>`_"
+msgstr ""
+
+#: ../../about.rst:576
+# e7ba5c879e744a6ba1d69aabc6a24b64
+msgid "CLONE - OVA files exist for templates created from volumes..."
+msgstr ""
+
+#: ../../about.rst:577
+# c5fe040ebfea4cc3b072eec9b743d6de
+msgid "`CLOUDSTACK-5895 <https://issues.apache.org/jira/browse/CLOUDSTACK-5895>`_"
+msgstr ""
+
+#: ../../about.rst:577
+# 7a316a57ea2e41babc33969f4bfc7b5f
+msgid "CreateVolumeFromSnapshot can fail in a multiple pod environment with tagged stor..."
+msgstr ""
+
+#: ../../about.rst:578
+# 9ebb40a97a2d4b458e1c47b982d14802
+msgid "`CLOUDSTACK-5886 <https://issues.apache.org/jira/browse/CLOUDSTACK-5886>`_"
+msgstr ""
+
+#: ../../about.rst:578
+# 728849191fa0442ba1e79ecf2cba0e10
+msgid "4.2.1 upgrade fails on acl migration..."
+msgstr ""
+
+#: ../../about.rst:579
+# 0e2dfb62b791451eb9ef455be4556257
+msgid "`CLOUDSTACK-5877 <https://issues.apache.org/jira/browse/CLOUDSTACK-5877>`_"
+msgstr ""
+
+#: ../../about.rst:579
+# 3941c0f94cf54e16b4b88c9b584450ab
+msgid "listTemplates does not sort based on sort_key..."
+msgstr ""
+
+#: ../../about.rst:580
+# 596cb956d35b42b2b11fb2445190a0f6
+msgid "`CLOUDSTACK-5875 <https://issues.apache.org/jira/browse/CLOUDSTACK-5875>`_"
+msgstr ""
+
+#: ../../about.rst:580
+# 9afc247c85e64b7bb689a6944739c737
+msgid "No templates in simulator run..."
+msgstr ""
+
+#: ../../about.rst:581
+# 8a070062759545ac924e81915e5c2fb6
+msgid "`CLOUDSTACK-5864 <https://issues.apache.org/jira/browse/CLOUDSTACK-5864>`_"
+msgstr ""
+
+#: ../../about.rst:581
+# 1daa9aac7b264d57ad7801634f30e516
+msgid "Simulator profile broken ..."
+msgstr ""
+
+#: ../../about.rst:582
+# fab087d4848847879dbc1a09b3a65350
+msgid "`CLOUDSTACK-5813 <https://issues.apache.org/jira/browse/CLOUDSTACK-5813>`_"
+msgstr ""
+
+#: ../../about.rst:582
+# 84929748e059490d91860839cbf5f368
+msgid "With S3 as secondary storage, snapshot taken in one zone cannot be used to creat..."
+msgstr ""
+
+#: ../../about.rst:583
+# 873ec58c448c4bc2b3576ecbfe08fe91
+msgid "`CLOUDSTACK-5723 <https://issues.apache.org/jira/browse/CLOUDSTACK-5723>`_"
+msgstr ""
+
+#: ../../about.rst:583
+# f4ab3c42228f469893405062f75837e7
+msgid "Malfunction agent may block future SSL connection to the server..."
+msgstr ""
+
+#: ../../about.rst:584
+# c7ba7e92feec492b96e76195ecee04d0
+msgid "`CLOUDSTACK-5704 <https://issues.apache.org/jira/browse/CLOUDSTACK-5704>`_"
+msgstr ""
+
+#: ../../about.rst:584
+# 0fd950ccfcf148d781d426eb7f99bde9
+msgid "OVA files exist for templates created from volumes..."
+msgstr ""
+
+#: ../../about.rst:585
+# eddc8a46975945a38c1801c2e9ab0078
+msgid "`CLOUDSTACK-5701 <https://issues.apache.org/jira/browse/CLOUDSTACK-5701>`_"
+msgstr ""
+
+#: ../../about.rst:585
+# e54362e110fe41b385fe444e37aa537a
+msgid "size column is not getting updated in snapshot_store_ref table...."
+msgstr ""
+
+#: ../../about.rst:586
+# 0cd9023c1b8a4681b3b70500efaaa55f
+msgid "`CLOUDSTACK-5666 <https://issues.apache.org/jira/browse/CLOUDSTACK-5666>`_"
+msgstr ""
+
+#: ../../about.rst:586
+# dd77df5602ab47a9a24ef7c717bf9d85
+msgid "Cant remove a nic when a vm is in the Stopped state ..."
+msgstr ""
+
+#: ../../about.rst:587
+# 32a8651ac0b340f7855db6d56a5ccee8
+msgid "`CLOUDSTACK-5661 <https://issues.apache.org/jira/browse/CLOUDSTACK-5661>`_"
+msgstr ""
+
+#: ../../about.rst:587
+# 06b0a669cac447b5863820f66808bb7d
+msgid "[VMware] DetachIsoCmd succeeds even though cdrom is locked by VM as cdrom is mou..."
+msgstr ""
+
+#: ../../about.rst:588
+# a7a0c5068a634d4c915bb24cded1c94e
+msgid "`CLOUDSTACK-5653 <https://issues.apache.org/jira/browse/CLOUDSTACK-5653>`_"
+msgstr ""
+
+#: ../../about.rst:588
+# e6dff212b59a48faa951040a6712829e
+msgid "S3 object store as Secondary Storage, the template created from different zone i..."
+msgstr ""
+
+#: ../../about.rst:589
+# 8ed057a05d0b4840b00ce1e2bb4cbc15
+msgid "`CLOUDSTACK-5613 <https://issues.apache.org/jira/browse/CLOUDSTACK-5613>`_"
+msgstr ""
+
+#: ../../about.rst:589
+# 91c47fd5727f4964b9c2ed0a04c103db
+msgid "CloudStack 4.2.0 - Usage server is running but tables remain empty..."
+msgstr ""
+
+#: ../../about.rst:590
+# b110177bebcd4addb8b09bc5c3bd76b6
+msgid "`CLOUDSTACK-5608 <https://issues.apache.org/jira/browse/CLOUDSTACK-5608>`_"
+msgstr ""
+
+#: ../../about.rst:590
+# ebdfe4750fee42c0915b3990ec49c4f7
+msgid "HyperV Builtin and System vm template entries missing in 4.3 upgrade setup..."
+msgstr ""
+
+#: ../../about.rst:591
+# 409d294a556c4d4bb401a5df0493e0ef
+msgid "`CLOUDSTACK-5534 <https://issues.apache.org/jira/browse/CLOUDSTACK-5534>`_"
+msgstr ""
+
+#: ../../about.rst:591
+# 60a31acf9894466995a20b662749ed46
+msgid "MySQL exception raised when searching for users with keyword..."
+msgstr ""
+
+#: ../../about.rst:592
+# 71047f1716d3425696c0b255eca912b8
+msgid "`CLOUDSTACK-5533 <https://issues.apache.org/jira/browse/CLOUDSTACK-5533>`_"
+msgstr ""
+
+#: ../../about.rst:592
+# e3ccfbc9c09449819b1141a9078951d7
+msgid "Virtual router in shared network does respond to DNS even when no DNS service is..."
+msgstr ""
+
+#: ../../about.rst:593
+# b01fb15aaba740058f3a7d9552395cb0
+msgid "`CLOUDSTACK-5532 <https://issues.apache.org/jira/browse/CLOUDSTACK-5532>`_"
+msgstr ""
+
+#: ../../about.rst:593
+# 13eebd1cd2d14980a7f9f4135a355027
+msgid "Long tag values are not readable within the UI..."
+msgstr ""
+
+#: ../../about.rst:594
+# 0a3611c289324c9d9977b5e331ecd62c
+msgid "`CLOUDSTACK-5519 <https://issues.apache.org/jira/browse/CLOUDSTACK-5519>`_"
+msgstr ""
+
+#: ../../about.rst:594
+# ff5c9f0f0d034143be802c76448ed125
+msgid "[VMWARE] Cancel vCenter tasks if the task invoked by CloudStack failes with time..."
+msgstr ""
+
+#: ../../about.rst:595
+# 4e5be5d95e474f3d9fe576232e89d9c4
+msgid "`CLOUDSTACK-5517 <https://issues.apache.org/jira/browse/CLOUDSTACK-5517>`_"
+msgstr ""
+
+#: ../../about.rst:595
+# e5b76e0e3f6f457d8c70d29198fd3108
+msgid "NPE observed during \"release portable IPs\" as part of account cleanup..."
+msgstr ""
+
+#: ../../about.rst:596
+# 3f1c335388784560bc5ed7d7c9a8f281
+msgid "`CLOUDSTACK-5514 <https://issues.apache.org/jira/browse/CLOUDSTACK-5514>`_"
+msgstr ""
+
+#: ../../about.rst:596
+# ccffa519c73c42a79caf211baf574b29
+msgid "Response of listAccounts API call includes removed users..."
+msgstr ""
+
+#: ../../about.rst:597
+# d105f33710e9422d85cd8764e79f49cd
+msgid "`CLOUDSTACK-5513 <https://issues.apache.org/jira/browse/CLOUDSTACK-5513>`_"
+msgstr ""
+
+#: ../../about.rst:597
+# 585199f3e2194cf7ba8a1888d15a786f
+msgid "VM can't start after creating snapshot from it (CS4.2 + VMware 5.1)..."
+msgstr ""
+
+#: ../../about.rst:598
+# beb21f35d213432cb471c4e2fe8bd524
+msgid "`CLOUDSTACK-5481 <https://issues.apache.org/jira/browse/CLOUDSTACK-5481>`_"
+msgstr ""
+
+#: ../../about.rst:598
+# d7f6cbe2070b49078c83beb74e462183
+msgid "Regular User is unable to use \"Add Isolated Network\" Button on the UI..."
+msgstr ""
+
+#: ../../about.rst:599
+# aef0f1b14c53491da7b807dc7144fe0c
+msgid "`CLOUDSTACK-5466 <https://issues.apache.org/jira/browse/CLOUDSTACK-5466>`_"
+msgstr ""
+
+#: ../../about.rst:599
+# 94b636446b3747a784cfe9532d4d300f
+msgid "removeIpFromNic not working properly..."
+msgstr ""
+
+#: ../../about.rst:600
+# 958fa48f21c04a51855c5d0659cf1190
+msgid "`CLOUDSTACK-5453 <https://issues.apache.org/jira/browse/CLOUDSTACK-5453>`_"
+msgstr ""
+
+#: ../../about.rst:600
+# 1c76166e9b6543dca3fbf26468a1187b
+msgid "Site-to-site VPN connection status monitoring is broken in KVM..."
+msgstr ""
+
+#: ../../about.rst:601
+# 8cd304a426924ea7a8aa03637330f80a
+msgid "`CLOUDSTACK-5431 <https://issues.apache.org/jira/browse/CLOUDSTACK-5431>`_"
+msgstr ""
+
+#: ../../about.rst:601
+# 9d5df4e7abbb4e13a2b04d683139fc85
+msgid "permit 'http' as service type for GSLB rule..."
+msgstr ""
+
+#: ../../about.rst:602
+# 164e76cd04014c1dac9d0656fe55333c
+msgid "`CLOUDSTACK-5428 <https://issues.apache.org/jira/browse/CLOUDSTACK-5428>`_"
+msgstr ""
+
+#: ../../about.rst:602
+# b26407e9f7904625a9358bc18cf908b0
+msgid "support NetScaler to be configured exclusively for GSLB service and not used for..."
+msgstr ""
+
+#: ../../about.rst:603
+# e855f3e23fce4ca2be395b8c7483f375
+msgid "`CLOUDSTACK-5426 <https://issues.apache.org/jira/browse/CLOUDSTACK-5426>`_"
+msgstr ""
+
+#: ../../about.rst:603
+# 5cbdc97a57a64da29bdd377ebb7923e6
+msgid "Cannot deploy instance having multiple volumes that use different storage tags f..."
+msgstr ""
+
+#: ../../about.rst:604
+# 6eb9a9c3ebfa4afbb9ee54872b06cbd4
+msgid "`CLOUDSTACK-5422 <https://issues.apache.org/jira/browse/CLOUDSTACK-5422>`_"
+msgstr ""
+
+#: ../../about.rst:604
+# 86740bf59c384d9da4395fc768d6fa75
+msgid "Changing XenServer Tools Version 6.1 + doesnt work ..."
+msgstr ""
+
+#: ../../about.rst:605
+# 9a28c24991924f808b75427dd664ef99
+msgid "`CLOUDSTACK-5417 <https://issues.apache.org/jira/browse/CLOUDSTACK-5417>`_"
+msgstr ""
+
+#: ../../about.rst:605
+# 47e1a9eafa9d44cdae779b6658bb1e48
+msgid "On network restart for external devices egress rules configured with old CIDR..."
+msgstr ""
+
+#: ../../about.rst:606
+# 40c7825d2c1348cd9d0d7b39746a08e9
+msgid "`CLOUDSTACK-5416 <https://issues.apache.org/jira/browse/CLOUDSTACK-5416>`_"
+msgstr ""
+
+#: ../../about.rst:606
+# 64c9bb755c454b8fa55863203ca25b0d
+msgid "[VMware] Not able to add seventh disk to VM in an upgraded setup..."
+msgstr ""
+
+#: ../../about.rst:607
+# a6c82beb23e84bb0990e58c667423fcd
+msgid "`CLOUDSTACK-5404 <https://issues.apache.org/jira/browse/CLOUDSTACK-5404>`_"
+msgstr ""
+
+#: ../../about.rst:607
+# 0dc8297ef30b4defbd669083e14e83e0
+msgid "Network usages (bytes sent/received) are saved in the wrong timezone..."
+msgstr ""
+
+#: ../../about.rst:608
+# 1c1abad42a6248609d07bca0db8e973e
+msgid "`CLOUDSTACK-5401 <https://issues.apache.org/jira/browse/CLOUDSTACK-5401>`_"
+msgstr ""
+
+#: ../../about.rst:608
+# c156cd7b21e640c4860bf028420d26c5
+msgid "VM migration during host maintenance fails if pool.storage.capacity.disablethres..."
+msgstr ""
+
+#: ../../about.rst:609
+# 74df6416b8d24e18bf0e42f285ddbcad
+msgid "`CLOUDSTACK-5391 <https://issues.apache.org/jira/browse/CLOUDSTACK-5391>`_"
+msgstr ""
+
+#: ../../about.rst:609
+# c6136e978f5343dbaeb51262df64c7f8
+msgid "Change service offering of a stopped vm and then starting it should check host c..."
+msgstr ""
+
+#: ../../about.rst:610
+# 160fa3d6876b4b67866b179389f08144
+msgid "`CLOUDSTACK-5355 <https://issues.apache.org/jira/browse/CLOUDSTACK-5355>`_"
+msgstr ""
+
+#: ../../about.rst:610
+# 3892afea22cf432ab5251b6111d9ccce
+msgid "addImageStore should not log password in clear text in the log..."
+msgstr ""
+
+#: ../../about.rst:611
+# fec037aa605441058b452eae5f75c02d
+msgid "`CLOUDSTACK-5354 <https://issues.apache.org/jira/browse/CLOUDSTACK-5354>`_"
+msgstr ""
+
+#: ../../about.rst:611
+# f79bf3459deb495292ce27588f86b9b3
+msgid "CLONE - UI - normal users are not allowed to edit their own iso..."
+msgstr ""
+
+#: ../../about.rst:612
+# bcd983fb1b99452f8f416b46290de8cb
+msgid "`CLOUDSTACK-5352 <https://issues.apache.org/jira/browse/CLOUDSTACK-5352>`_"
+msgstr ""
+
+#: ../../about.rst:612
+# 350e7ff63c9b429f9424b556e21ad566
+msgid "CPU cap calculated incorrectly for VMs on XenServer hosts..."
+msgstr ""
+
+#: ../../about.rst:613
+# 7b1fc63cee124b35822ec3eb8fc7f6af
+msgid "`CLOUDSTACK-5332 <https://issues.apache.org/jira/browse/CLOUDSTACK-5332>`_"
+msgstr ""
+
+#: ../../about.rst:613
+# feb3d1322a1241cc9eb08917cd4743be
+msgid "Network offering don't use new system offering for router..."
+msgstr ""
+
+#: ../../about.rst:614
+# 1a2119ed5e8248f19652bef8401fd0e6
+msgid "`CLOUDSTACK-5303 <https://issues.apache.org/jira/browse/CLOUDSTACK-5303>`_"
+msgstr ""
+
+#: ../../about.rst:614
+# 5afc8932f7494cb4a20358ef8fff503b
+msgid "\"snapshot\" count and \"secondary_storage\" count are not correct in resource_coun..."
+msgstr ""
+
+#: ../../about.rst:615
+# 2affca7697264ca19bac046fd526e064
+msgid "`CLOUDSTACK-5302 <https://issues.apache.org/jira/browse/CLOUDSTACK-5302>`_"
+msgstr ""
+
+#: ../../about.rst:615
+# 877ffb2b03974c0ba79f53c413f1eafb
+msgid "listHosts API response - value of cpuallocated is always 0%..."
+msgstr ""
+
+#: ../../about.rst:616
+# 8ccbb840f7664ac4ba5113134c738df7
+msgid "`CLOUDSTACK-5299 <https://issues.apache.org/jira/browse/CLOUDSTACK-5299>`_"
+msgstr ""
+
+#: ../../about.rst:616
+# 5a90aac42d5a481d8da1ef7de0512938
+msgid "Can not get hypervisor type for volumes..."
+msgstr ""
+
+#: ../../about.rst:617
+# 66a67bf63cee4915bdd5d4d611e60139
+msgid "`CLOUDSTACK-5293 <https://issues.apache.org/jira/browse/CLOUDSTACK-5293>`_"
+msgstr ""
+
+#: ../../about.rst:617
+# a0f8e5038019429888fb26ff53c118e6
+msgid "Error while collecting vm disk stats from hosts if iso is attached to vm..."
+msgstr ""
+
+#: ../../about.rst:618
+# 07c42615e51548f69f8c30439d921d17
+msgid "`CLOUDSTACK-5285 <https://issues.apache.org/jira/browse/CLOUDSTACK-5285>`_"
+msgstr ""
+
+#: ../../about.rst:618
+# 8ff7ce2ceaf24e1e983ba48c88965524
+msgid "Correct the API command description for removeIpFromNic..."
+msgstr ""
+
+#: ../../about.rst:619
+# 9513c8669b24496290525568709a9ef4
+msgid "`CLOUDSTACK-5261 <https://issues.apache.org/jira/browse/CLOUDSTACK-5261>`_"
+msgstr ""
+
+#: ../../about.rst:619
+# d57c730aacac4bf786480d0efe5d6457
+msgid "Ability to publish Alerts via CS Root API..."
+msgstr ""
+
+#: ../../about.rst:620
+# e1a8f1ff555e406a9509a94434de8f82
+msgid "`CLOUDSTACK-5260 <https://issues.apache.org/jira/browse/CLOUDSTACK-5260>`_"
+msgstr ""
+
+#: ../../about.rst:620
+# 4664a6293efc4d7c814b9b4e9bc5d4c1
+msgid "Vmware 5.1 Deploy Template Error : Read Timeout..."
+msgstr ""
+
+#: ../../about.rst:621
+# 291a2a8b016b43d599c1bcf9b8d43dfa
+msgid "`CLOUDSTACK-5228 <https://issues.apache.org/jira/browse/CLOUDSTACK-5228>`_"
+msgstr ""
+
+#: ../../about.rst:621
+# 592e7ee58ff44ca696e5ef93df69756c
+msgid "[API] [EIP/ELB enabled Zone] Need to display EIP address as \"Public IP Address\" ..."
+msgstr ""
+
+#: ../../about.rst:622
+# 9b9c697badbd497ca85bbc500ebb72c5
+msgid "`CLOUDSTACK-5227 <https://issues.apache.org/jira/browse/CLOUDSTACK-5227>`_"
+msgstr ""
+
+#: ../../about.rst:622
+# 46bccacdbe06484aa0199e60e40300e9
+msgid "Cannot pass Japanese characters as parameter values to API..."
+msgstr ""
+
+#: ../../about.rst:623
+# e0e1c93ad5e64a79a45ab35053f01cfb
+msgid "`CLOUDSTACK-5218 <https://issues.apache.org/jira/browse/CLOUDSTACK-5218>`_"
+msgstr ""
+
+#: ../../about.rst:623
+# 81e81b34f1a344af9009ad60222702d1
+msgid "CLONE - [Doc] Make VMware vCenter session timeout value configurable...."
+msgstr ""
+
+#: ../../about.rst:624
+# bab494bd96fb44988e3d25277cccd030
+msgid "`CLOUDSTACK-5199 <https://issues.apache.org/jira/browse/CLOUDSTACK-5199>`_"
+msgstr ""
+
+#: ../../about.rst:624
+# def3f3a51fdf4b1b92c987286f59359f
+msgid "Cannot restart VM after taking a VM snapshot of an existing VM or reverting a VM..."
+msgstr ""
+
+#: ../../about.rst:625
+# a79b0cd2aff14097aa1ad07d0dd422aa
+msgid "`CLOUDSTACK-5141 <https://issues.apache.org/jira/browse/CLOUDSTACK-5141>`_"
+msgstr ""
+
+#: ../../about.rst:625
+# 8c8141ffce9e439bab4f678e9168b296
+msgid "[Automation] Router deployment failed due to failure in SavePasswordCommand, obs..."
+msgstr ""
+
+#: ../../about.rst:626
+# c75a8334357d4a83b752de6a11b2b4d7
+msgid "`CLOUDSTACK-5140 <https://issues.apache.org/jira/browse/CLOUDSTACK-5140>`_"
+msgstr ""
+
+#: ../../about.rst:626
+# d6831610409f4f188790c6d92247cb75
+msgid "A stopped vm cant start after disable threshold has been reached on the storage ..."
+msgstr ""
+
+#: ../../about.rst:627
+# 22cd66d5db22485fb325534c02440206
+msgid "`CLOUDSTACK-5138 <https://issues.apache.org/jira/browse/CLOUDSTACK-5138>`_"
+msgstr ""
+
+#: ../../about.rst:627
+# 4938e30eac0c48f2a122d345be81fcd9
+msgid "[Automation] NPE while create template from snapshot..."
+msgstr ""
+
+#: ../../about.rst:628
+# b20682c52bdf4288bed892d203f99526
+msgid "`CLOUDSTACK-5122 <https://issues.apache.org/jira/browse/CLOUDSTACK-5122>`_"
+msgstr ""
+
+#: ../../about.rst:628
+# 58cf214ec9d64115a3b85e9b3ab8ce36
+msgid "[VMware] System VMs are getting recreated with old template after upgrading to 4..."
+msgstr ""
+
+#: ../../about.rst:629
+# c043a910005e4cfea0bc16a8d9d06a9e
+msgid "`CLOUDSTACK-5105 <https://issues.apache.org/jira/browse/CLOUDSTACK-5105>`_"
+msgstr ""
+
+#: ../../about.rst:629
+# 17735be3e8194a42ae5cd0528fdbb019
+msgid "Template/ISO download fails cause the object to disappear from UI..."
+msgstr ""
+
+#: ../../about.rst:630
+# 09a4f78d472b43eda0644678d5c8c7d3
+msgid "`CLOUDSTACK-5098 <https://issues.apache.org/jira/browse/CLOUDSTACK-5098>`_"
+msgstr ""
+
+#: ../../about.rst:630
+# 7d7cca26788f4dd79f3cbd31e523e0b5
+msgid "[UI] Zone view is showing \"Add VMware Datacenter\" button even though zone is alr..."
+msgstr ""
+
+#: ../../about.rst:631
+# eb8ff0c3bda34421949b4667650cc1d5
+msgid "`CLOUDSTACK-5092 <https://issues.apache.org/jira/browse/CLOUDSTACK-5092>`_"
+msgstr ""
+
+#: ../../about.rst:631
+# 56d5e2c4ab894c55b42e20e05d149623
+msgid "[Automation] [BVT] Failed to copy template and ISO between zones in xen ..."
+msgstr ""
+
+#: ../../about.rst:632
+# b45bd9b4a8cf47d987a26dfe370ca028
+msgid "`CLOUDSTACK-5076 <https://issues.apache.org/jira/browse/CLOUDSTACK-5076>`_"
+msgstr ""
+
+#: ../../about.rst:632
+# 5835754aee834dc69fb7792ffdb7f3f8
+msgid "(Upgrade) reboot VM failed after bridge name change..."
+msgstr ""
+
+#: ../../about.rst:633
+# 23e18a9f4e944601a546ed29c964e216
+msgid "`CLOUDSTACK-5069 <https://issues.apache.org/jira/browse/CLOUDSTACK-5069>`_"
+msgstr ""
+
+#: ../../about.rst:633
+# af479331ce47410f98142b3d0648003c
+msgid "Make VMware vCenter session timeout value configurable...."
+msgstr ""
+
+#: ../../about.rst:634
+# 7aa387b30a3a475fa0411f488558ef4e
+msgid "`CLOUDSTACK-5066 <https://issues.apache.org/jira/browse/CLOUDSTACK-5066>`_"
+msgstr ""
+
+#: ../../about.rst:634
+# 44c96673b9494513930cd45d01464ccb
+msgid "Existed remote access VPN got dropped when adding new VPN users..."
+msgstr ""
+
+#: ../../about.rst:635
+# 116d66a48fd949439363507aca8310c3
+msgid "`CLOUDSTACK-5062 <https://issues.apache.org/jira/browse/CLOUDSTACK-5062>`_"
+msgstr ""
+
+#: ../../about.rst:635
+# c9d4decce149472da2241e905e1e55b8
+msgid "Deleting Load Balancing Rule fails when generating usage events are enabled..."
+msgstr ""
+
+#: ../../about.rst:636
+# 40095f5a91ab4d589f03f2f97f8f6c01
+msgid "`CLOUDSTACK-5054 <https://issues.apache.org/jira/browse/CLOUDSTACK-5054>`_"
+msgstr ""
+
+#: ../../about.rst:636
+# 43e2ed9dd8d1465db3bbb4ac659d8a44
+msgid "vm migration involving storage migration on vmware fails with exception \" The ob..."
+msgstr ""
+
+#: ../../about.rst:637
+# 79281854b68042959a44e49cb47e9068
+msgid "`CLOUDSTACK-5053 <https://issues.apache.org/jira/browse/CLOUDSTACK-5053>`_"
+msgstr ""
+
+#: ../../about.rst:637
+# d7b0c91ea5b84f67b0d1b8fa9c37b990
+msgid "No Qemu-KVM module dependency error message is displayed (if not present)while i..."
+msgstr ""
+
+#: ../../about.rst:638
+# 62a2b6949fe04d868cdb00cb753807ed
+msgid "`CLOUDSTACK-5042 <https://issues.apache.org/jira/browse/CLOUDSTACK-5042>`_"
+msgstr ""
+
+#: ../../about.rst:638
+# cd471cd674ba4b1990f5aa1ddb730ce5
+msgid "(Upgrade) Exception when stop VM after upgrade..."
+msgstr ""
+
+#: ../../about.rst:639
+# b5e9203fefc244c4b44ebba45ec12810
+msgid "`CLOUDSTACK-5029 <https://issues.apache.org/jira/browse/CLOUDSTACK-5029>`_"
+msgstr ""
+
+#: ../../about.rst:639
+# 39d6712e5e4b462183c0a37bf83065bd
+msgid "cloud-bugtool isn't in release package like release notes say..."
+msgstr ""
+
+#: ../../about.rst:640
+# cfd17a3c83424354a101243f1cf7bdc5
+msgid "`CLOUDSTACK-5025 <https://issues.apache.org/jira/browse/CLOUDSTACK-5025>`_"
+msgstr ""
+
+#: ../../about.rst:640
+# c787224cdecb4277a63f59419ade0354
+msgid "display_volume field is set to false by default for VolumeVO object..."
+msgstr ""
+
+#: ../../about.rst:641
+# e0db5d5193714503baaa63774c7883e7
+msgid "`CLOUDSTACK-5024 <https://issues.apache.org/jira/browse/CLOUDSTACK-5024>`_"
+msgstr ""
+
+#: ../../about.rst:641
+# 91985f80c06c4cafaf06c903a93cc7e8
+msgid "listVolumes: add support to list by storage pool (for admin only)..."
+msgstr ""
+
+#: ../../about.rst:642
+# b54e2b69fcf843548bcced086afdb8bb
+msgid "`CLOUDSTACK-5017 <https://issues.apache.org/jira/browse/CLOUDSTACK-5017>`_"
+msgstr ""
+
+#: ../../about.rst:642
+# 89f7cd3a438d498b8a9f547d29ba7da5
+msgid "If SSVM is unavailable DownloadCommands will be routed to mgmt server..."
+msgstr ""
+
+#: ../../about.rst:643
+# 13f38290069340c3a6960c8ace0fe864
+msgid "`CLOUDSTACK-5014 <https://issues.apache.org/jira/browse/CLOUDSTACK-5014>`_"
+msgstr ""
+
+#: ../../about.rst:643
+# 160f63d96c684fca9c79411f55054495
+msgid "vmware:deployVM with data disk failed with exception..."
+msgstr ""
+
+#: ../../about.rst:644
+# ecbb035c4ac349f1807dbd7c1f2b0ae3
+msgid "`CLOUDSTACK-5012 <https://issues.apache.org/jira/browse/CLOUDSTACK-5012>`_"
+msgstr ""
+
+#: ../../about.rst:644
+# 92d0c1c705a34bee9025d5f9c031c65d
+msgid "Bad data inserted into physical network labels for Zone Create Wizard using VMWa..."
+msgstr ""
+
+#: ../../about.rst:645
+# fc1711cc578a49b4bff7216747d1cd04
+msgid "`CLOUDSTACK-5008 <https://issues.apache.org/jira/browse/CLOUDSTACK-5008>`_"
+msgstr ""
+
+#: ../../about.rst:645
+# 79f4077e5ee548a9ab492510295a7187
+msgid "[VMWARE]Failed to start the VM after performing Cold Migration of Volume to Seco..."
+msgstr ""
+
+#: ../../about.rst:646
+# 5a205aae19e94a9595b247e2a2ea81d0
+msgid "`CLOUDSTACK-5002 <https://issues.apache.org/jira/browse/CLOUDSTACK-5002>`_"
+msgstr ""
+
+#: ../../about.rst:646
+# dce91c56d5c44611b1285a73c56bb875
+msgid "unable to destroy vm ;VM destroy failed in Stop i-2-59-VM Command due to You gav..."
+msgstr ""
+
+#: ../../about.rst:647
+# a9151f89758f4052ad1fda7a5ebec833
+msgid "`CLOUDSTACK-4998 <https://issues.apache.org/jira/browse/CLOUDSTACK-4998>`_"
+msgstr ""
+
+#: ../../about.rst:647
+# 23bb79a059e64a7bbd90af2216252f4c
+msgid "assignVirtualMachine API has wrong response string, causing Cloudmonkey to crash..."
+msgstr ""
+
+#: ../../about.rst:648
+# 1eee91dd1f4d4d13913b5499427b15da
+msgid "`CLOUDSTACK-4997 <https://issues.apache.org/jira/browse/CLOUDSTACK-4997>`_"
+msgstr ""
+
+#: ../../about.rst:648
+# b89d57e09f8c4c609b4f093c8af12eea
+msgid "OVS integration is broken..."
+msgstr ""
+
+#: ../../about.rst:649
+# 7ded99c897cc4af0b3e1664b8dfa87b2
+msgid "`CLOUDSTACK-4973 <https://issues.apache.org/jira/browse/CLOUDSTACK-4973>`_"
+msgstr ""
+
+#: ../../about.rst:649
+# 8c7263e10a3b4e0c915ef7848c025420
+msgid "CLONE - Specified keyboard language is not showing as default in consoleView pas..."
+msgstr ""
+
+#: ../../about.rst:650
+# 7dd970bb14874c4e880c05f61d69e120
+msgid "`CLOUDSTACK-4943 <https://issues.apache.org/jira/browse/CLOUDSTACK-4943>`_"
+msgstr ""
+
+#: ../../about.rst:650
+# ac3a0db207af47a082e2e8747cbad0e5
+msgid "Can't create cluster in CS 4.2..."
+msgstr ""
+
+#: ../../about.rst:651
+# fe4e42bf8a4a4c87bf1dbdf3d892352f
+msgid "`CLOUDSTACK-4941 <https://issues.apache.org/jira/browse/CLOUDSTACK-4941>`_"
+msgstr ""
+
+#: ../../about.rst:651
+# dfde391f57bc4705b0b09a46710393d3
+msgid "CLONE - Allocation capacity of a cluster during HA..."
+msgstr ""
+
+#: ../../about.rst:652
+# a69b885ec9174c529a710902645c2413
+msgid "`CLOUDSTACK-4935 <https://issues.apache.org/jira/browse/CLOUDSTACK-4935>`_"
+msgstr ""
+
+#: ../../about.rst:652
+# 76627021c06443dd8cd7cb4934c106f8
+msgid "Adding same network to VM multiple times resulting in failure, No new NIC is gen..."
+msgstr ""
+
+#: ../../about.rst:653
+# a1a864a7fc3f4738928e049dc639ac07
+msgid "`CLOUDSTACK-4931 <https://issues.apache.org/jira/browse/CLOUDSTACK-4931>`_"
+msgstr ""
+
+#: ../../about.rst:653
+# fed2e7496c794dbd8c4c5d953aa12b03
+msgid "observed NPE with new system vm template..."
+msgstr ""
+
+#: ../../about.rst:654
+# d83c883ef59d4e86b8bfd7317b2f9029
+msgid "`CLOUDSTACK-4913 <https://issues.apache.org/jira/browse/CLOUDSTACK-4913>`_"
+msgstr ""
+
+#: ../../about.rst:654
+# f43873d002164e958d8d498fbaec3341
+msgid "Disable security group for bridge mode non-security group zone..."
+msgstr ""
+
+#: ../../about.rst:655
+# c1a803ba102645349754b4400a8295cc
+msgid "`CLOUDSTACK-4904 <https://issues.apache.org/jira/browse/CLOUDSTACK-4904>`_"
+msgstr ""
+
+#: ../../about.rst:655
+# 061044bfcf674f22a7093620e8d16199
+msgid "Unable to see a derieved template if the parent template is deleted..."
+msgstr ""
+
+#: ../../about.rst:656
+# dedc905ddb864b2f89addf62aef0384d
+msgid "`CLOUDSTACK-4886 <https://issues.apache.org/jira/browse/CLOUDSTACK-4886>`_"
+msgstr ""
+
+#: ../../about.rst:656
+# 6e42fe77fa004d7d8329793f97675540
+msgid "cloud-setup-databases not escaping password in shell commands..."
+msgstr ""
+
+#: ../../about.rst:657
+# fa155cfb42d6462098798b1d5d59b458
+msgid "`CLOUDSTACK-4875 <https://issues.apache.org/jira/browse/CLOUDSTACK-4875>`_"
+msgstr ""
+
+#: ../../about.rst:657
+# 747a8fe507a64ab4ae3ca8f6cfd5993a
+msgid "VMWARE: vCenter 5.5 - SYSTEM VM: Unable to create deployment for VM..."
+msgstr ""
+
+#: ../../about.rst:658
+# 1ad6c1a18ac74f9ca5d950d6ed1d5c0c
+msgid "`CLOUDSTACK-4861 <https://issues.apache.org/jira/browse/CLOUDSTACK-4861>`_"
+msgstr ""
+
+#: ../../about.rst:658
+# 8957176fd07f4c109ea7b0357952fa7b
+msgid "[VMware] If Guest traffic spans across multiple physical networks, selection of ..."
+msgstr ""
+
+#: ../../about.rst:659
+# b5ac3a6c76204ad8a9a7268080c64b49
+msgid "`CLOUDSTACK-4860 <https://issues.apache.org/jira/browse/CLOUDSTACK-4860>`_"
+msgstr ""
+
+#: ../../about.rst:659
+# 37976257934d4487a958e85fa50fc551
+msgid "[VMware] Vcenter 5.5 ESXi 5.5 hosts SSVM CPVM fail to come up to running state..."
+msgstr ""
+
+#: ../../about.rst:660
+# 9cd4d3f685e348f18b8ddf5a934beb28
+msgid "`CLOUDSTACK-4856 <https://issues.apache.org/jira/browse/CLOUDSTACK-4856>`_"
+msgstr ""
+
+#: ../../about.rst:660
+# dc59e549f9c34f5a8460bc55ae67373a
+msgid "Optimize on the # of control commands sent by MS to HV host..."
+msgstr ""
+
+#: ../../about.rst:661
+# 3281238e366244ecb0123297babe660d
+msgid "`CLOUDSTACK-4855 <https://issues.apache.org/jira/browse/CLOUDSTACK-4855>`_"
+msgstr ""
+
+#: ../../about.rst:661
+# 5b4cb016bbae46cb8ff1f3960e6fe0eb
+msgid "Throttle based on the # of outstanding requests to the directly managed HV host ..."
+msgstr ""
+
+#: ../../about.rst:662
+# 42c1986e9f884f6f96efa3330e265dcb
+msgid "`CLOUDSTACK-4852 <https://issues.apache.org/jira/browse/CLOUDSTACK-4852>`_"
+msgstr ""
+
+#: ../../about.rst:662
+# 846be2c7a49f4ae98c1a5b73753cf314
+msgid "Since upgrade to 4.2 only users at the zone-attached domain level can manipulate..."
+msgstr ""
+
+#: ../../about.rst:663
+# 8efb802f4abb4fd48f3f1a19de4aee1e
+msgid "`CLOUDSTACK-4850 <https://issues.apache.org/jira/browse/CLOUDSTACK-4850>`_"
+msgstr ""
+
+#: ../../about.rst:663
+# 5d6b3617c7cb42caa0f701e2e0d38c9e
+msgid "[UCS] using template instead of cloning profile..."
+msgstr ""
+
+#: ../../about.rst:664
+# ab31d5d84b62429dafcbda5ee27859c8
+msgid "`CLOUDSTACK-4831 <https://issues.apache.org/jira/browse/CLOUDSTACK-4831>`_"
+msgstr ""
+
+#: ../../about.rst:664
+# baa83e0f5592429fab4491fad2feb22d
+msgid "Ability for root admin or domain admin to create a network for another user unde..."
+msgstr ""
+
+#: ../../about.rst:665
+# b52b06c6a83646acb6ea1335dd553575
+msgid "`CLOUDSTACK-4830 <https://issues.apache.org/jira/browse/CLOUDSTACK-4830>`_"
+msgstr ""
+
+#: ../../about.rst:665
+# b3f3aee5e5b546c58758169b9ff5c403
+msgid "Allow creation of users and accounts by domain admin in UI..."
+msgstr ""
+
+#: ../../about.rst:666
+# 501a3df6f8e34585b221b1824f047cf1
+msgid "`CLOUDSTACK-4826 <https://issues.apache.org/jira/browse/CLOUDSTACK-4826>`_"
+msgstr ""
+
+#: ../../about.rst:666
+# 189a999bb37b4295958ec024dd7afe19
+msgid "System VMs fail to start..."
+msgstr ""
+
+#: ../../about.rst:667
+# 10f645984ad841c39f942c5541cedb98
+msgid "`CLOUDSTACK-4820 <https://issues.apache.org/jira/browse/CLOUDSTACK-4820>`_"
+msgstr ""
+
+#: ../../about.rst:667
+# cacfcadb7e134c47b6901e101aa71b5f
+msgid "TestVPCNetworkGc.test_01_wait_network_gc netacls are not cleared..."
+msgstr ""
+
+#: ../../about.rst:668
+# 15dc2294ec194ca19884e5f157c54fe4
+msgid "`CLOUDSTACK-4810 <https://issues.apache.org/jira/browse/CLOUDSTACK-4810>`_"
+msgstr ""
+
+#: ../../about.rst:668
+# e333ec5a2a7a4b45a850be2353e42047
+msgid "Enable hypervisor snapshots for CloudStack-managed storage (for XenServer and VM..."
+msgstr ""
+
+#: ../../about.rst:669
+# 48a67622fecd4d56b212eb303217fc29
+msgid "`CLOUDSTACK-4768 <https://issues.apache.org/jira/browse/CLOUDSTACK-4768>`_"
+msgstr ""
+
+#: ../../about.rst:669
+# 750a2810c8b2410caeb179cfdac55331
+msgid "[Automation] Race condition; delete the template and create VM at same time; dep..."
+msgstr ""
+
+#: ../../about.rst:670
+# 211fab9e0d464b588efc4bc6634cd1d7
+msgid "`CLOUDSTACK-4750 <https://issues.apache.org/jira/browse/CLOUDSTACK-4750>`_"
+msgstr ""
+
+#: ../../about.rst:670
+# 8bd6ea66876d4598baa7750dff3a1d3c
+msgid "bond.VLAN mapping in iptables FORWARD chain not created consistently..."
+msgstr ""
+
+#: ../../about.rst:671
+# b639c092953d427ea6530d446dfef07a
+msgid "`CLOUDSTACK-4741 <https://issues.apache.org/jira/browse/CLOUDSTACK-4741>`_"
+msgstr ""
+
+#: ../../about.rst:671
+# 68accc5e76514ef1afeda698a37297ff
+msgid "URL of ImageStore not in proper format for XenServer..."
+msgstr ""
+
+#: ../../about.rst:672
+# 5e8fa3a2ac5d40858b372f0bc4fa8f75
+msgid "`CLOUDSTACK-4740 <https://issues.apache.org/jira/browse/CLOUDSTACK-4740>`_"
+msgstr ""
+
+#: ../../about.rst:672
+# b1f99f7d418642e59644fd4d3c8271a9
+msgid "Some vSphere VMs are shutdown when ACS is restarted..."
+msgstr ""
+
+#: ../../about.rst:673
+# c0e2c47fc85a4c9bb76c4943232f8cfa
+msgid "`CLOUDSTACK-4734 <https://issues.apache.org/jira/browse/CLOUDSTACK-4734>`_"
+msgstr ""
+
+#: ../../about.rst:673
+# 5bf24b93956741eab2801030d5f9841a
+msgid "Creating snapshot from ROOT volume fails with error message - \"Failed to create ..."
+msgstr ""
+
+#: ../../about.rst:674
+# bed7503a00e44110b452dbbf35f399a0
+msgid "`CLOUDSTACK-4724 <https://issues.apache.org/jira/browse/CLOUDSTACK-4724>`_"
+msgstr ""
+
+#: ../../about.rst:674
+# 5d6a1b1bce914e9fba42fa56ca653d74
+msgid "[Vmware] Deploy VM in designated cluster fail if there is only zone wide primary..."
+msgstr ""
+
+#: ../../about.rst:675
+# ada11e5aff404aecabf02b03254c391f
+msgid "`CLOUDSTACK-4697 <https://issues.apache.org/jira/browse/CLOUDSTACK-4697>`_"
+msgstr ""
+
+#: ../../about.rst:675
+# 0a0f8cf524124393992aefaa1c4742ed
+msgid "Not able to delete Primary storage when there are no hosts in the cluster...."
+msgstr ""
+
+#: ../../about.rst:676
+# b2fcbe8c396a4306893bddc2a4d0570e
+msgid "`CLOUDSTACK-4676 <https://issues.apache.org/jira/browse/CLOUDSTACK-4676>`_"
+msgstr ""
+
+#: ../../about.rst:676
+# ac575161189240a1acd5dcf501c06e2f
+msgid "[Baremetal] baremetal hostename should not be fixed in kickstart file ..."
+msgstr ""
+
+#: ../../about.rst:677
+# 54e3f264d08642b6b1fb45681e846b36
+msgid "`CLOUDSTACK-4670 <https://issues.apache.org/jira/browse/CLOUDSTACK-4670>`_"
+msgstr ""
+
+#: ../../about.rst:677
+# 5ecae9795b55428b9c96b3fb7288b939
+msgid "[Baremetal] Cloudplatform BareMetal installation guide for CP 4.2..."
+msgstr ""
+
+#: ../../about.rst:678
+# 126fd296bbe3499198ccdf95aedbc428
+msgid "`CLOUDSTACK-4631 <https://issues.apache.org/jira/browse/CLOUDSTACK-4631>`_"
+msgstr ""
+
+#: ../../about.rst:678
+# 46a50fc4b36446fc9f631831185fb301
+msgid "[Automation] Failed to create snapshot from volume due to storage pool missing e..."
+msgstr ""
+
+#: ../../about.rst:679
+# 379803428c4b40a99d75f9c8ef15f7c7
+msgid "`CLOUDSTACK-4620 <https://issues.apache.org/jira/browse/CLOUDSTACK-4620>`_"
+msgstr ""
+
+#: ../../about.rst:679
+# b8558b1ab0904e8eba3bb334e0eed8fd
+msgid "Vm failed to start on the host on which it was running due to not having enough ..."
+msgstr ""
+
+#: ../../about.rst:680
+# 6fbab8fd7917498d9db231ce8dc2b583
+msgid "`CLOUDSTACK-4616 <https://issues.apache.org/jira/browse/CLOUDSTACK-4616>`_"
+msgstr ""
+
+#: ../../about.rst:680
+# 2185171c4e8a42bc8de280d9aa31805c
+msgid "When system Vms fail to start when host is down , link local Ip addresses do no..."
+msgstr ""
+
+#: ../../about.rst:681
+# 227ffaee42f144d89bb6d7b32bdf03da
+msgid "`CLOUDSTACK-4598 <https://issues.apache.org/jira/browse/CLOUDSTACK-4598>`_"
+msgstr ""
+
+#: ../../about.rst:681
+# 90e454f8ca38449fa4cb287df0cc8e49
+msgid "[Performance Testing] High delays during deployVM - both network delay and deplo..."
+msgstr ""
+
+#: ../../about.rst:682
+# 3bc452f5797d4fb6926eb4cdfdcaafb1
+msgid "`CLOUDSTACK-4597 <https://issues.apache.org/jira/browse/CLOUDSTACK-4597>`_"
+msgstr ""
+
+#: ../../about.rst:682
+# 9c2214fa5635486b859b99215792fcb4
+msgid "Complete Exceptions are getting displayed in the UI where there is an operationa..."
+msgstr ""
+
+#: ../../about.rst:683
+# 39bc028e76114cdf93712edd47d7ba4a
+msgid "`CLOUDSTACK-4594 <https://issues.apache.org/jira/browse/CLOUDSTACK-4594>`_"
+msgstr ""
+
+#: ../../about.rst:683
+# 7fda7fc93c994e63ab06f9107c77e380
+msgid "[VMWARE] [Upgrade] Failed to revert VM Snapshot which were created before Live S..."
+msgstr ""
+
+#: ../../about.rst:684
+# ce278c39e77745e38df99861dc659544
+msgid "`CLOUDSTACK-4588 <https://issues.apache.org/jira/browse/CLOUDSTACK-4588>`_"
+msgstr ""
+
+#: ../../about.rst:684
+# da095652365841459d93cad09d8ff503
+msgid "[Automation][Vmware] VM deployment failed while creating Volume with NPE..."
+msgstr ""
+
+#: ../../about.rst:685
+# 91ae778c89884cae9473ca921fd31448
+msgid "`CLOUDSTACK-4577 <https://issues.apache.org/jira/browse/CLOUDSTACK-4577>`_"
+msgstr ""
+
+#: ../../about.rst:685
+# d026461c2bf7472f809e4890eebaa2e3
+msgid "VMWare:Volumes: Unexpected exception while executing org.apache.cloudstack.api.c..."
+msgstr ""
+
+#: ../../about.rst:686
+# 1d9f253b59e346a0bad4cfef82be0b91
+msgid "`CLOUDSTACK-4543 <https://issues.apache.org/jira/browse/CLOUDSTACK-4543>`_"
+msgstr ""
+
+#: ../../about.rst:686
+# ee92d2c68ebe4efc8b5cb5be24d06b1b
+msgid "[Automation] Failed to configure VPC router then reported as deployment failure..."
+msgstr ""
+
+#: ../../about.rst:687
+# c980a7ff009242b4b767febc23a2bc29
+msgid "`CLOUDSTACK-4542 <https://issues.apache.org/jira/browse/CLOUDSTACK-4542>`_"
+msgstr ""
+
+#: ../../about.rst:687
+# 41554cf693464f1195755a0ade34141a
+msgid "[Automation] Failed to apply DHCP entry in VR and deployment failed ..."
+msgstr ""
+
+#: ../../about.rst:688
+# 47713c22f8a049c5b2a8ab20c89217c8
+msgid "`CLOUDSTACK-4540 <https://issues.apache.org/jira/browse/CLOUDSTACK-4540>`_"
+msgstr ""
+
+#: ../../about.rst:688
+# 5bd94401fa6847eb8c4f65347ed0eeba
+msgid "[Automation] Parallel deployment - Vmware - When deploying 30 parallel Vms , 16 ..."
+msgstr ""
+
+#: ../../about.rst:689
+# cc0aabdbe28b4d41bf04dda2de5eb39c
+msgid "`CLOUDSTACK-4506 <https://issues.apache.org/jira/browse/CLOUDSTACK-4506>`_"
+msgstr ""
+
+#: ../../about.rst:689
+# 42e3822ed11340979a3879ae3186d3f1
+msgid "In a mixed hypervisor setup, destroying a VM whose host has been removed, throws..."
+msgstr ""
+
+#: ../../about.rst:690
+# 8790d47690d549a593aab8cf0e77a252
+msgid "`CLOUDSTACK-4504 <https://issues.apache.org/jira/browse/CLOUDSTACK-4504>`_"
+msgstr ""
+
+#: ../../about.rst:690
+# fd070f755db54e6ca07f29e3ea78ef08
+msgid "VM creation Is failing using the Ubuntu ISO with Xen 6.1 and 6.2..."
+msgstr ""
+
+#: ../../about.rst:691
+# d383c2b9c5e34965b121e3158bc1c9c6
+msgid "`CLOUDSTACK-4450 <https://issues.apache.org/jira/browse/CLOUDSTACK-4450>`_"
+msgstr ""
+
+#: ../../about.rst:691
+# ffe8f57646ef484abc43c7cd361322d4
+msgid "Possibility of /tmp/xapilog filling up the Root disk on Xenserver ..."
+msgstr ""
+
+#: ../../about.rst:692
+# dc5aa1576b0c44e7b5b3ded245bbd6cc
+msgid "`CLOUDSTACK-4445 <https://issues.apache.org/jira/browse/CLOUDSTACK-4445>`_"
+msgstr ""
+
+#: ../../about.rst:692
+# 221dca1539a34554aa084f746d51092c
+msgid "[UI]Edit Icon is used for Dedicate host / Add or Remove VMWARE Datacenter with ..."
+msgstr ""
+
+#: ../../about.rst:693
+# 05118ddccdf445b5b5edf7344fcd15bb
+msgid "`CLOUDSTACK-4428 <https://issues.apache.org/jira/browse/CLOUDSTACK-4428>`_"
+msgstr ""
+
+#: ../../about.rst:693
+# 77e2ad14b0e54ba482807ec425427645
+msgid "[UI] \"kvm.snapshot.enabled\" flag should be taken to account only when snapshot i..."
+msgstr ""
+
+#: ../../about.rst:694
+# 26b76fe5303649a790ccff43b2c5049f
+msgid "`CLOUDSTACK-4402 <https://issues.apache.org/jira/browse/CLOUDSTACK-4402>`_"
+msgstr ""
+
+#: ../../about.rst:694
+# fe3d5f63a647476c872fd01cf0df19f6
+msgid "[deleteStoragePool] There is no way to delete Primary storage if the last host w..."
+msgstr ""
+
+#: ../../about.rst:695
+# ceb6c277f41143bbb0a1386d5e67013d
+msgid "`CLOUDSTACK-4371 <https://issues.apache.org/jira/browse/CLOUDSTACK-4371>`_"
+msgstr ""
+
+#: ../../about.rst:695
+# f687a03296794550ad49fc92158a9f12
+msgid "[Performance Testing] Basic zone with 20K Hosts, management server restart leave..."
+msgstr ""
+
+#: ../../about.rst:696
+# 11c7794de35044839d3f2258fd73c169
+msgid "`CLOUDSTACK-4263 <https://issues.apache.org/jira/browse/CLOUDSTACK-4263>`_"
+msgstr ""
+
+#: ../../about.rst:696
+# 38b5aeb8acea45e4b64478d6ea6f131e
+msgid "Unable to get git number in maven-jgit-buildnumber-plugin, while build cloudstac..."
+msgstr ""
+
+#: ../../about.rst:697
+# 104b1472320740099883671f2dada31f
+msgid "`CLOUDSTACK-4207 <https://issues.apache.org/jira/browse/CLOUDSTACK-4207>`_"
+msgstr ""
+
+#: ../../about.rst:697
+# 2c9fa169dda640c5a91151935e4330c6
+msgid "[upgrade] Exception observed after upgrade \"jsonParseException: The JsonDeserial..."
+msgstr ""
+
+#: ../../about.rst:698
+# b7503f18923249908d856bc6f328313f
+msgid "`CLOUDSTACK-4061 <https://issues.apache.org/jira/browse/CLOUDSTACK-4061>`_"
+msgstr ""
+
+#: ../../about.rst:698
+# f3af02dae63d4a31bf577266a237d17d
+msgid "UI issue with Japanese localized ui..."
+msgstr ""
+
+#: ../../about.rst:699
+# 5fcd77799e5541bfabddc934a5881b2e
+msgid "`CLOUDSTACK-3806 <https://issues.apache.org/jira/browse/CLOUDSTACK-3806>`_"
+msgstr ""
+
+#: ../../about.rst:699
+# c43319742c0b440d98dda32a5ac2e488
+msgid "OS Preference can not be set..."
+msgstr ""
+
+#: ../../about.rst:700
+# 36bb50dd8a82450b85aea34ec194a3f3
+msgid "`CLOUDSTACK-3664 <https://issues.apache.org/jira/browse/CLOUDSTACK-3664>`_"
+msgstr ""
+
+#: ../../about.rst:700
+# 642b60faf5f246f285267341127b885b
+msgid "scaling up vms is not considering parameter \"cluster.(memory/cpu).allocated.cap..."
+msgstr ""
+
+#: ../../about.rst:701
+# 0cdfd6782a2a42349352de16b1b14d71
+msgid "`CLOUDSTACK-3627 <https://issues.apache.org/jira/browse/CLOUDSTACK-3627>`_"
+msgstr ""
+
+#: ../../about.rst:701
+# 21702dbb9dfc4d31ad95e5e10b83f8a3
+msgid "Public IP interface(eth2) is not getting confugured with Redundant VR (State = F..."
+msgstr ""
+
+#: ../../about.rst:702
+# 86a6e2f6bb0b4c8b96b2fcb8fb032bdb
+msgid "`CLOUDSTACK-3577 <https://issues.apache.org/jira/browse/CLOUDSTACK-3577>`_"
+msgstr ""
+
+#: ../../about.rst:702
+# 85214d0fa632436d8bfeec4da56ac5e4
+msgid "NPE while downloading the template to secondary storage ..."
+msgstr ""
+
+#: ../../about.rst:703
+# 44810451a0644dc68049333d6e74d170
+msgid "`CLOUDSTACK-3561 <https://issues.apache.org/jira/browse/CLOUDSTACK-3561>`_"
+msgstr ""
+
+#: ../../about.rst:703
+# b75310718e66407587d5c43022fa426e
+msgid "When inputting the nfs server in secondary storage, if once it's required, it al..."
+msgstr ""
+
+#: ../../about.rst:704
+# 13465793b3a943c5a9b6bab068d81298
+msgid "`CLOUDSTACK-3364 <https://issues.apache.org/jira/browse/CLOUDSTACK-3364>`_"
+msgstr ""
+
+#: ../../about.rst:704
+# e951699e241d45bc93be24331efebfe5
+msgid "normal users are not allowed to edit their own iso..."
+msgstr ""
+
+#: ../../about.rst:705
+# 8d83e620d6314c1985c3902a9e1f5b5e
+msgid "`CLOUDSTACK-3266 <https://issues.apache.org/jira/browse/CLOUDSTACK-3266>`_"
+msgstr ""
+
+#: ../../about.rst:705
+# 817aae70948640a39786c8eedc403117
+msgid "[UI] Failed to delete Anti affinitygroup for the first time ..."
+msgstr ""
+
+#: ../../about.rst:706
+# c4c3cbb8586249dca78844b418a347c9
+msgid "`CLOUDSTACK-3252 <https://issues.apache.org/jira/browse/CLOUDSTACK-3252>`_"
+msgstr ""
+
+#: ../../about.rst:706
+# d577dce295e7485e9fe076b1e90fecbe
+msgid "An instance deployed using explicit or implicit dedication doesn't generate a us..."
+msgstr ""
+
+#: ../../about.rst:707
+# e9ebded05b404650a0b91a896ee98046
+msgid "`CLOUDSTACK-3247 <https://issues.apache.org/jira/browse/CLOUDSTACK-3247>`_"
+msgstr ""
+
+#: ../../about.rst:707
+# d9ed05f351ab43efa8484648b34711c7
+msgid "Removing a Disconnected Host throws a NoTransitionException..."
+msgstr ""
+
+#: ../../about.rst:708
+# ebc5535f7dda48c18844a74453e6ae04
+msgid "`CLOUDSTACK-3156 <https://issues.apache.org/jira/browse/CLOUDSTACK-3156>`_"
+msgstr ""
+
+#: ../../about.rst:708
+# 2f7c49bb04cb464592521404a6b645b9
+msgid "needs proper message for failing Add nic command when vmware tools is not instal..."
+msgstr ""
+
+#: ../../about.rst:709
+# e589ed802033435d9e06e6d3451ad4ec
+msgid "`CLOUDSTACK-3067 <https://issues.apache.org/jira/browse/CLOUDSTACK-3067>`_"
+msgstr ""
+
+#: ../../about.rst:709
+# c10c09d9e06b422ea42deff9455b7fc4
+msgid "UI for Dedicating POD/Cluster/Host is misleading Icons should be changed...."
+msgstr ""
+
+#: ../../about.rst:710
+# 1776639960384d91be367c192b193f6e
+msgid "`CLOUDSTACK-3027 <https://issues.apache.org/jira/browse/CLOUDSTACK-3027>`_"
+msgstr ""
+
+#: ../../about.rst:710
+# 73e13ff98b4243b9a20b50ee3e376b9f
+msgid "Object_Store_Refactor - Uploaded template S3 content-type is not appropriate...."
+msgstr ""
+
+#: ../../about.rst:711
+# db9ce076437d4ead84b15545ca7f2527
+msgid "`CLOUDSTACK-2895 <https://issues.apache.org/jira/browse/CLOUDSTACK-2895>`_"
+msgstr ""
+
+#: ../../about.rst:711
+# f3ceed3d135a409baff6c790cc95f0bd
+msgid "Can't start a VM with 3 volumes attached [VMWare]..."
+msgstr ""
+
+#: ../../about.rst:712
+# 82dbd781079744aea51f36c468acf383
+msgid "`CLOUDSTACK-2766 <https://issues.apache.org/jira/browse/CLOUDSTACK-2766>`_"
+msgstr ""
+
+#: ../../about.rst:712
+# 4f6db1729af84eac8239cc4010256df9
+msgid "[VPC] [UI] Firewall service should not be enabled for acquired public IPs in VPC..."
+msgstr ""
+
+#: ../../about.rst:713
+# fc408e4e115344aca26337d032f3fe57
+msgid "`CLOUDSTACK-2687 <https://issues.apache.org/jira/browse/CLOUDSTACK-2687>`_"
+msgstr ""
+
+#: ../../about.rst:713
+# 68662c997bd44c23a4752e827db60032
+msgid "NPE with deploy VM when there are no resources available ..."
+msgstr ""
+
+#: ../../about.rst:714
+# 71ae7842ee464e1e922a222d4d70912f
+msgid "`CLOUDSTACK-2570 <https://issues.apache.org/jira/browse/CLOUDSTACK-2570>`_"
+msgstr ""
+
+#: ../../about.rst:714
+# ac9a0771b87d475cb7be48ffedf997d5
+msgid "[UI]Resource Name is mentioned twice with view VNMC devices ..."
+msgstr ""
+
+#: ../../about.rst:715
+# be29600cb4514dfca86f48d41023e49f
+msgid "`CLOUDSTACK-2562 <https://issues.apache.org/jira/browse/CLOUDSTACK-2562>`_"
+msgstr ""
+
+#: ../../about.rst:715
+# 07bc018e1bbc44d9b62178dd206268cf
+msgid "[VMWARE] As per the code, currently CloudStack fails to program PF/NAT/LB rules ..."
+msgstr ""
+
+#: ../../about.rst:716
+# 61203c44c9c644f4adb7afab63a6681a
+msgid "`CLOUDSTACK-2428 <https://issues.apache.org/jira/browse/CLOUDSTACK-2428>`_"
+msgstr ""
+
+#: ../../about.rst:716
+# c06bebf8a33649ed8131f4b65a442741
+msgid "HA - When the master host is disconnected , the host status contines to remain i..."
+msgstr ""
+
+#: ../../about.rst:717
+# 355721da958a498d8ba4b92a004344db
+msgid "`CLOUDSTACK-2414 <https://issues.apache.org/jira/browse/CLOUDSTACK-2414>`_"
+msgstr ""
+
+#: ../../about.rst:717
+# 88df2cdc4cfa47468edc9b0011db7298
+msgid "NPE while deleting Cisco VNMC provider..."
+msgstr ""
+
+#: ../../about.rst:718
+# ca232c6f2a22456986598e306b91d4db
+msgid "`CLOUDSTACK-2396 <https://issues.apache.org/jira/browse/CLOUDSTACK-2396>`_"
+msgstr ""
+
+#: ../../about.rst:718
+# cfb458af8afc43d8a66b6121cc628293
+msgid "PVLAN - Should not be allowed to create multiple networks with same Vlan associ..."
+msgstr ""
+
+#: ../../about.rst:719
+# 585c07df2d5448dcba290de9f271688e
+msgid "`CLOUDSTACK-2199 <https://issues.apache.org/jira/browse/CLOUDSTACK-2199>`_"
+msgstr ""
+
+#: ../../about.rst:719
+# 17e0b4ecc6f1404f9e14a5f686051b7d
+msgid "ID parameter of UpdateConfiguration API should be changed to a different name..."
+msgstr ""
+
+#: ../../about.rst:720
+# 01ea2848fe344d31955cd85d1658efd8
+msgid "`CLOUDSTACK-2141 <https://issues.apache.org/jira/browse/CLOUDSTACK-2141>`_"
+msgstr ""
+
+#: ../../about.rst:720
+# 4dddbbae9d0840a8ad81a2468c62ba78
+msgid "During HA process , dead lock is detected - Caused by: com.mysql.jdbc.exception..."
+msgstr ""
+
+#: ../../about.rst:721
+# f18c12a93f9c4e3e9851653bcfc49b3e
+msgid "`CLOUDSTACK-1970 <https://issues.apache.org/jira/browse/CLOUDSTACK-1970>`_"
+msgstr ""
+
+#: ../../about.rst:721
+# 8ccc99672b1649e9bfaded6c83b00565
+msgid "Ubuntu - \"cloudstack-setup-management\" not available in \"/usr/bin\"..."
+msgstr ""
+
+#: ../../about.rst:722
+# d8920306f36140cba685be0ae0163462
+msgid "`CLOUDSTACK-1889 <https://issues.apache.org/jira/browse/CLOUDSTACK-1889>`_"
+msgstr ""
+
+#: ../../about.rst:722
+# 67849ec4e4cb4e53b9c45a4dac238292
+msgid "[UI] Consumed Resource usage details are not available for all the resources..."
+msgstr ""
+
+#: ../../about.rst:723
+# ab09a0e8aa764bcaa79200afda6dc05d
+msgid "`CLOUDSTACK-1868 <https://issues.apache.org/jira/browse/CLOUDSTACK-1868>`_"
+msgstr ""
+
+#: ../../about.rst:723
+# 6f9698df0b334e868d1afb282f4ab87a
+msgid "GetVmStatsCommand throws NullPointerException with VMWare..."
+msgstr ""
+
+#: ../../about.rst:724
+# 71081f32c5394fa7b58478869ef588fc
+msgid "`CLOUDSTACK-1762 <https://issues.apache.org/jira/browse/CLOUDSTACK-1762>`_"
+msgstr ""
+
+#: ../../about.rst:724
+# 23d1ec5f650849cb995595f6e6023eb9
+msgid "[MultipleIpsToNic] addIpToNic should not let network id or broadcast to be assig..."
+msgstr ""
+
+#: ../../about.rst:725
+# 19fcef90d9ca435e8221328b24e3aab4
+msgid "`CLOUDSTACK-1637 <https://issues.apache.org/jira/browse/CLOUDSTACK-1637>`_"
+msgstr ""
+
+#: ../../about.rst:725
+# a43129b0cd404f2e82d7c5f8347dd8b3
+msgid "LDAP:UI related issues..."
+msgstr ""
+
+#: ../../about.rst:730
+# 71c836e363854cf5b492fd061ccc190d
+msgid "Known Issues in 4.3.0"
+msgstr ""
+
+#: ../../about.rst:735
+# 1b16efacb0eb4285a3fe990c9faf5236
+msgid "For the list of known issues, see `Known Issues in 4.3 <https://issues.apache.org/jira/issues/?filter=12326162>`__."
+msgstr ""
+
+#: ../../about.rst:741
+# 31d47b582cf145fc8e4492a8b291f116
+msgid "`CLOUDSTACK-4787 <https://issues.apache.org/jira/browse/CLOUDSTACK-4787>`_"
+msgstr ""
+
+#: ../../about.rst:741
+# ef129fa6cb3146b1857507d7c5b584d5
+msgid "Allow selection of scsi controller type in vSphere..."
+msgstr ""
+
+#: ../../about.rst:742
+# 50ebe7aaa9984a51b4e50d70c9d2e276
+msgid "`CLOUDSTACK-6024 <https://issues.apache.org/jira/browse/CLOUDSTACK-6024>`_"
+msgstr ""
+
+#: ../../about.rst:742
+# b4a2aa9ac51b4b519f45e8eb31b6f78a
+msgid "template copy to primary storage uses a random source secstorage from any zone..."
+msgstr ""
+
+#: ../../about.rst:743
+# 87963880d9f34d4c97086171a79a5bb5
+msgid "`CLOUDSTACK-4912 <https://issues.apache.org/jira/browse/CLOUDSTACK-4912>`_"
+msgstr ""
+
+#: ../../about.rst:743
+# 5a6f5883d7ad40abbf0a376104ccfe46
+msgid "API docs are missing some APIs..."
+msgstr ""
+
+#: ../../about.rst:744
+# 03b51226028342628f8903906b987f83
+msgid "`CLOUDSTACK-5124 <https://issues.apache.org/jira/browse/CLOUDSTACK-5124>`_"
+msgstr ""
+
+#: ../../about.rst:744
+# b776d2a67285407ab2e5fb605d18dcaa
+msgid "Simulator: Virtual Router fails to start because of improper version returned by..."
+msgstr ""
+
+#: ../../about.rst:745
+# f57fb57c3bd746adb96f77d30648dbe3
+msgid "`CLOUDSTACK-5262 <https://issues.apache.org/jira/browse/CLOUDSTACK-5262>`_"
+msgstr ""
+
+#: ../../about.rst:745
+# 5c72ef3cabcc4a76ab04ed7f1629d305
+msgid "Few of the snapshot creation from ROOT volume fails when there are concurrent s..."
+msgstr ""
+
+#: ../../about.rst:746
+# 865cad9874bd49d995f3835cdecb595d
+msgid "`CLOUDSTACK-5356 <https://issues.apache.org/jira/browse/CLOUDSTACK-5356>`_"
+msgstr ""
+
+#: ../../about.rst:746
+# b1e9e358f4d445b58cbf4f657528529c
+msgid "Xenserver - Failed to create snapshot when secondary store was made unavaibale f..."
+msgstr ""
+
+#: ../../about.rst:747
+# c726e0ed500e495192a32edb5f10f224
+msgid "`CLOUDSTACK-5357 <https://issues.apache.org/jira/browse/CLOUDSTACK-5357>`_"
+msgstr ""
+
+#: ../../about.rst:747
+# cb17e1a2a4c1497493142c62b294c29d
+msgid "Xenserver - Failed to create snapshot due to \"unable to destroy task(com.xe nsou..."
+msgstr ""
+
+#: ../../about.rst:748
+# 36992a81b47943f29ffb24dfca04b284
+msgid "`CLOUDSTACK-5358 <https://issues.apache.org/jira/browse/CLOUDSTACK-5358>`_"
+msgstr ""
+
+#: ../../about.rst:748
+# 809afb2c1a5a4e8e834545fdecd809e0
+msgid "API: synchronization on the object is broken..."
+msgstr ""
+
+#: ../../about.rst:749
+# e9ba91dc614643a6b8f4ad800d78b8d5
+msgid "`CLOUDSTACK-5372 <https://issues.apache.org/jira/browse/CLOUDSTACK-5372>`_"
+msgstr ""
+
+#: ../../about.rst:749
+# a12de4d7e892479d9b85f53620897771
+msgid "Xenserver - SR not being recreated when the Primary storage is brought down and ..."
+msgstr ""
+
+#: ../../about.rst:750
+# 242006f64cba438995e2a4751cc8074c
+msgid "`CLOUDSTACK-5429 <https://issues.apache.org/jira/browse/CLOUDSTACK-5429>`_"
+msgstr ""
+
+#: ../../about.rst:750
+# d44d2dfe655b4b60aacd9383de18bf54
+msgid "KVM - Primary store down/Network Failure - Hosts attempt to reboot becasue of pr..."
+msgstr ""
+
+#: ../../about.rst:751
+# 5a67b815905b45faa0786948f1f40a16
+msgid "`CLOUDSTACK-5452 <https://issues.apache.org/jira/browse/CLOUDSTACK-5452>`_"
+msgstr ""
+
+#: ../../about.rst:751
+# 07aad5722c294ceca2d20ff07b9b3d55
+msgid "KVM - Agent is not able to connect back if management server was restarted when ..."
+msgstr ""
+
+#: ../../about.rst:752
+# c469ca03b2d441cf9f2b89a9ad0fd256
+msgid "`CLOUDSTACK-5469 <https://issues.apache.org/jira/browse/CLOUDSTACK-5469>`_"
+msgstr ""
+
+#: ../../about.rst:752
+# 5fc31df43299472b90b99fd450381f27
+msgid "Snapshot creation fails with following exception - \"Failed to backup snapshot: q..."
+msgstr ""
+
+#: ../../about.rst:753
+# ee69b35e9a104e15af05fed03f16bfd6
+msgid "`CLOUDSTACK-5485 <https://issues.apache.org/jira/browse/CLOUDSTACK-5485>`_"
+msgstr ""
+
+#: ../../about.rst:753
+# 6c11592ff2d042b39f286026a49b57fa
+msgid "Vmware - Whe 10 hourly snapshots are scheduled at the same time , we see only 5 ..."
+msgstr ""
+
+#: ../../about.rst:754
+# 812196063f1e4c48b18e33d9e082fdd5
+msgid "`CLOUDSTACK-5494 <https://issues.apache.org/jira/browse/CLOUDSTACK-5494>`_"
+msgstr ""
+
+#: ../../about.rst:754
+# 8634a982a6a241608c9c0041c466b319
+msgid "the dns resolver servers on the VRs are open to the world..."
+msgstr ""
+
+#: ../../about.rst:755
+# 495c1be268f445c1b8d4818f81b9a3e2
+msgid "`CLOUDSTACK-5499 <https://issues.apache.org/jira/browse/CLOUDSTACK-5499>`_"
+msgstr ""
+
+#: ../../about.rst:755
+# 33cbbaaae77946e7a820cdc7d3a2a40a
+msgid "Vmware -When nfs was down for about 12 hours and then brought back up again , s..."
+msgstr ""
+
+#: ../../about.rst:756
+# 9dbd38304a7246adbccd0c72b9fffbef
+msgid "`CLOUDSTACK-5501 <https://issues.apache.org/jira/browse/CLOUDSTACK-5501>`_"
+msgstr ""
+
+#: ../../about.rst:756
+# fd1a637684f64104b0306facc294dd5c
+msgid "Unable to create more than one vpnConnection per vpn customer gateway..."
+msgstr ""
+
+#: ../../about.rst:757
+# 8c0d9bb0c8434e33b618102c0d54d14f
+msgid "`CLOUDSTACK-5582 <https://issues.apache.org/jira/browse/CLOUDSTACK-5582>`_"
+msgstr ""
+
+#: ../../about.rst:757
+# 7b80352fe2c74d488a4f1e2464276657
+msgid "kvm - HA is not triggered when host is powered down since the host gets into \"Di..."
+msgstr ""
+
+#: ../../about.rst:758
+# 783f8812c4484c618f51d34b26c7a473
+msgid "`CLOUDSTACK-5746 <https://issues.apache.org/jira/browse/CLOUDSTACK-5746>`_"
+msgstr ""
+
+#: ../../about.rst:758
+# 36954ba31b6b46ef9cd2e53529f59f8b
+msgid "[HyperV]Can't access vm console from IE browser..."
+msgstr ""
+
+#: ../../about.rst:759
+# 0553b5764c5548f096edcec2ede64189
+msgid "`CLOUDSTACK-5806 <https://issues.apache.org/jira/browse/CLOUDSTACK-5806>`_"
+msgstr ""
+
+#: ../../about.rst:759
+# e3358df3595e46f89d0e9e178040e051
+msgid "Storage types other than NFS/VMFS can't overprovision..."
+msgstr ""
+
+#: ../../about.rst:760
+# d7ee8f91e0274d89a09eb32b2a3fe162
+msgid "`CLOUDSTACK-5818 <https://issues.apache.org/jira/browse/CLOUDSTACK-5818>`_"
+msgstr ""
+
+#: ../../about.rst:760
+# c4afd7c1057b4a02a51318811dd0604f
+msgid "[Hyper-v]Agent status of the System VMs is not updated during Host disconnect..."
+msgstr ""
+
+#: ../../about.rst:761
+# 677a4b4cd4a04c63a7ab351992c54168
+msgid "`CLOUDSTACK-5825 <https://issues.apache.org/jira/browse/CLOUDSTACK-5825>`_"
+msgstr ""
+
+#: ../../about.rst:761
+# e87b7183c08d4bd9a79801ea0bb14a4a
+msgid "Create snapshot API always returns success..."
+msgstr ""
+
+#: ../../about.rst:762
+# 72e75f9805fd435b9ccd058b65bd54b4
+msgid "`CLOUDSTACK-5882 <https://issues.apache.org/jira/browse/CLOUDSTACK-5882>`_"
+msgstr ""
+
+#: ../../about.rst:762
+# 19fd2a4d5ae64d869733b5e0338c4ff1
+msgid "UI has different fonts and font sizes..."
+msgstr ""
+
+#: ../../about.rst:763
+# 247f7ef2aa90421694ad2b6c90f47332
+msgid "`CLOUDSTACK-5899 <https://issues.apache.org/jira/browse/CLOUDSTACK-5899>`_"
+msgstr ""
+
+#: ../../about.rst:763
+# 16fd252ccb144331b12e9bcd4c31b313
+msgid "Contrail:MS: Exceptions in MS logs on a fresh install, syncDomain java.lang.Nul..."
+msgstr ""
+
+#: ../../about.rst:764
+# 4ee5ee9fdfd94d5c88540dfb3886aa40
+msgid "`CLOUDSTACK-5928 <https://issues.apache.org/jira/browse/CLOUDSTACK-5928>`_"
+msgstr ""
+
+#: ../../about.rst:764
+# 292cea71244743b88b5e16bcb8925980
+msgid "[VM Sync] - Vmware - When a Vm is \"suspended\" from outside of CloudStack , this ..."
+msgstr ""
+
+#: ../../about.rst:765
+# 5ef4783f7eeb40c9bacacb4919ca82d0
+msgid "`CLOUDSTACK-5929 <https://issues.apache.org/jira/browse/CLOUDSTACK-5929>`_"
+msgstr ""
+
+#: ../../about.rst:765
+# d2f17d37363c4cc7b2851b114418ce92
+msgid "[VM Sync] - Vmware - Even when starting Vm fails, startVirtualMachine async job ..."
+msgstr ""
+
+#: ../../about.rst:766
+# 76fd33bc1154489d975d3abe31affcbf
+msgid "`CLOUDSTACK-5961 <https://issues.apache.org/jira/browse/CLOUDSTACK-5961>`_"
+msgstr ""
+
+#: ../../about.rst:766
+# eb3e836316be4139853918f4ffb63f5d
+msgid "CLONE - API: synchronization on the object is broken..."
+msgstr ""
+
+#: ../../about.rst:767
+# 25ce75c7373d4ca38c31e02205c65ec0
+msgid "`CLOUDSTACK-6050 <https://issues.apache.org/jira/browse/CLOUDSTACK-6050>`_"
+msgstr ""
+
+#: ../../about.rst:767
+# b8ccec7515b84034957aebe65d722c06
+msgid "A limitations on min-max on CPU/RAM for a dynamic offering ..."
+msgstr ""
+
+#: ../../about.rst:768
+# edb163afa7a7435b951c440f1eb8adaa
+msgid "`CLOUDSTACK-6051 <https://issues.apache.org/jira/browse/CLOUDSTACK-6051>`_"
+msgstr ""
+
+#: ../../about.rst:768
+# 3979450b6d8a45adb4a307a9f78e6d1d
+msgid "VR Rolling upgrade: Make the numbers of Routers parallely being upgraded as conf..."
+msgstr ""
+
+#: ../../about.rst:769
+# 0add0d8647da48d98e1f752ad5e5ebd8
+msgid "`CLOUDSTACK-6063 <https://issues.apache.org/jira/browse/CLOUDSTACK-6063>`_"
+msgstr ""
+
+#: ../../about.rst:769
+# 3e818949eac24ce6a0d3d2a030e78bb7
+msgid "CLONE - Non windows instances are created on XenServer with a vcpu-max above sup..."
+msgstr ""
+
+#: ../../about.rst:770
+# 720f854db96746c5a47da9f9ca9bb92a
+msgid "`CLOUDSTACK-6065 <https://issues.apache.org/jira/browse/CLOUDSTACK-6065>`_"
+msgstr ""
+
+#: ../../about.rst:770
+# 50f80b81c959495bb215a273eb93476b
+msgid "No HA for shutdown VM..."
+msgstr ""
+
+#: ../../about.rst:771
+# 34c7e3458c7c49c19e4573ea105a6967
+msgid "`CLOUDSTACK-6079 <https://issues.apache.org/jira/browse/CLOUDSTACK-6079>`_"
+msgstr ""
+
+#: ../../about.rst:771
+# 2f08609fa26b4764868788499ef7e020
+msgid "a broadcast type of a public network is affected by another physical network's i..."
+msgstr ""
+
+#: ../../about.rst:772
+# 3e8bba76ffb3402f854a35dcdd022d8f
+msgid "`CLOUDSTACK-77 <https://issues.apache.org/jira/browse/CLOUDSTACK-77>`_"
+msgstr ""
+
+#: ../../about.rst:772
+# 0f4c1b5bcfc14ab48ca576b42e6493af
+msgid "console proxy display issues..."
+msgstr ""
+
+#: ../../about.rst:773
+# 3365fe9795b34909870583163db215f6
+msgid "`CLOUDSTACK-107 <https://issues.apache.org/jira/browse/CLOUDSTACK-107>`_"
+msgstr ""
+
+#: ../../about.rst:773
+# 486188c703b64696806a1a86bfaf8188
+msgid "Network domain guest suffix is not getting programmed as part of hostnames on Gu..."
+msgstr ""
+
+#: ../../about.rst:774
+# 994f5cbe376840d2ae02fa5953409ed4
+msgid "`CLOUDSTACK-237 <https://issues.apache.org/jira/browse/CLOUDSTACK-237>`_"
+msgstr ""
+
+#: ../../about.rst:774
+# c73ee41ff6a643bb9db3648b8008b46c
+msgid "StopVMCommand reported success in spite of failing to stop a VM which got stuck ..."
+msgstr ""
+
+#: ../../about.rst:775
+# 83494e97fca7463885f04bb064098114
+msgid "`CLOUDSTACK-238 <https://issues.apache.org/jira/browse/CLOUDSTACK-238>`_"
+msgstr ""
+
+#: ../../about.rst:775
+# 1d5f73907f4f40fca7062368bc77acf3
+msgid "vpn:fail to connect to vpnserver using non-sourceNAT IP..."
+msgstr ""
+
+#: ../../about.rst:776
+# 8b883cfbd306436eb833afa800881c9b
+msgid "`CLOUDSTACK-252 <https://issues.apache.org/jira/browse/CLOUDSTACK-252>`_"
+msgstr ""
+
+#: ../../about.rst:776
+# 661901dc6f95475c99a173229d502de9
+msgid "UpdateNetwork Operation on a guest network that is currently using Virtual Route..."
+msgstr ""
+
+#: ../../about.rst:777
+# 88cead594e484ee89ffb6a431087da73
+msgid "`CLOUDSTACK-255 <https://issues.apache.org/jira/browse/CLOUDSTACK-255>`_"
+msgstr ""
+
+#: ../../about.rst:777
+# 953fe31bcf574f6da002fb0eda9829b0
+msgid "Null pointer exception while creating portforwarding rule after performing Updat..."
+msgstr ""
+
+#: ../../about.rst:778
+# d04f44859ed84287b2bbb0f5a2a02fd4
+msgid "`CLOUDSTACK-317 <https://issues.apache.org/jira/browse/CLOUDSTACK-317>`_"
+msgstr ""
+
+#: ../../about.rst:778
+# 9e1e272cd50c4c83ab11fc0068786418
+msgid "get xcp 1.5 into an advanced network zone..."
+msgstr ""
+
+#: ../../about.rst:779
+# bb6eee8040694156baa0f1cd892cfaa2
+msgid "`CLOUDSTACK-375 <https://issues.apache.org/jira/browse/CLOUDSTACK-375>`_"
+msgstr ""
+
+#: ../../about.rst:779
+# fdf3e49a3cb44de28cfeea786a577df3
+msgid "Unable to delete physical network - because there are other networks attached..."
+msgstr ""
+
+#: ../../about.rst:780
+# a1acc70725b24b1e8b2ddab9bd5f0f92
+msgid "`CLOUDSTACK-425 <https://issues.apache.org/jira/browse/CLOUDSTACK-425>`_"
+msgstr ""
+
+#: ../../about.rst:780
+# 2d04ce4728174183b509e742f7071363
+msgid "Check image type is qcow2 before actually installing..."
+msgstr ""
+
+#: ../../about.rst:781
+# d6ecb5b847b141468224a8b22b441114
+msgid "`CLOUDSTACK-992 <https://issues.apache.org/jira/browse/CLOUDSTACK-992>`_"
+msgstr ""
+
+#: ../../about.rst:781
+# daeacb38cd054fd6adfc01a375a85f4d
+msgid "Template creations dies after 2h for no reason..."
+msgstr ""
+
+#: ../../about.rst:782
+# 38316ccdc679458e8c4b44503d897aa3
+msgid "`CLOUDSTACK-1007 <https://issues.apache.org/jira/browse/CLOUDSTACK-1007>`_"
+msgstr ""
+
+#: ../../about.rst:782
+# 61e6cf53ab794c55875f4862b57a3e85
+msgid "Not able to delete Shared network because of not being able to stop the router...."
+msgstr ""
+
+#: ../../about.rst:783
+# c7f801984bf74320b773fe0ad72c3a08
+msgid "`CLOUDSTACK-1091 <https://issues.apache.org/jira/browse/CLOUDSTACK-1091>`_"
+msgstr ""
+
+#: ../../about.rst:783
+# 5d93525d930c49a68eacc663e993da2b
+msgid "Fix API server's parsing mechanism for POST requests..."
+msgstr ""
+
+#: ../../about.rst:784
+# cdd49d3ca6d14a83ae2d4efd2458de9c
+msgid "`CLOUDSTACK-1092 <https://issues.apache.org/jira/browse/CLOUDSTACK-1092>`_"
+msgstr ""
+
+#: ../../about.rst:784
+# 878923cf4ccf40bfb78945d5a54c7226
+msgid "Fix API Server's parsing mechanism to parse GET request as multimap..."
+msgstr ""
+
+#: ../../about.rst:785
+# d9c36379acf9481eaa72f886e2d85d04
+msgid "`CLOUDSTACK-1309 <https://issues.apache.org/jira/browse/CLOUDSTACK-1309>`_"
+msgstr ""
+
+#: ../../about.rst:785
+# 33df291795b74b03ad9bab5e09db2801
+msgid "Large guest subnets downgrade performance..."
+msgstr ""
+
+#: ../../about.rst:786
+# 6fd8714ddad04fc7aefb4b95240c313f
+msgid "`CLOUDSTACK-1389 <https://issues.apache.org/jira/browse/CLOUDSTACK-1389>`_"
+msgstr ""
+
+#: ../../about.rst:786
+# d9197701267548ae99ea1aeaf1c10a18
+msgid "Interactive Password Prompts during Management Server Startup..."
+msgstr ""
+
+#: ../../about.rst:787
+# a4910348aa8546fc81ca2976dcf5ae70
+msgid "`CLOUDSTACK-1413 <https://issues.apache.org/jira/browse/CLOUDSTACK-1413>`_"
+msgstr ""
+
+#: ../../about.rst:787
+# a55911b4455e4dac80c71f3a74ce3f07
+msgid "Need something to concretely identify the version of the code in a particular bu..."
+msgstr ""
+
+#: ../../about.rst:788
+# e1c49f8c562445719ba551cb19c8bddc
+msgid "`CLOUDSTACK-1527 <https://issues.apache.org/jira/browse/CLOUDSTACK-1527>`_"
+msgstr ""
+
+#: ../../about.rst:788
+# 0228182ddaf24ea7a63474da106be626
+msgid "Non-fatal POSTIN scriptlet failure in rpm package cloudstack-management-4.2.0-SN..."
+msgstr ""
+
+#: ../../about.rst:789
+# 864cd6c21f814c459a9a3f0d18ea9500
+msgid "`CLOUDSTACK-1717 <https://issues.apache.org/jira/browse/CLOUDSTACK-1717>`_"
+msgstr ""
+
+#: ../../about.rst:789
+# 1a0044e05ad7401aa9b78b5a82a38192
+msgid "AWS Regions - Local region entry that gets added by default should not include \"..."
+msgstr ""
+
+#: ../../about.rst:790
+# e8cd251bcc6d4c379f0736aa46129bbe
+msgid "`CLOUDSTACK-1885 <https://issues.apache.org/jira/browse/CLOUDSTACK-1885>`_"
+msgstr ""
+
+#: ../../about.rst:790
+# 694628719d7145628aedbc499609a966
+msgid "Broken testcases in 4.1..."
+msgstr ""
+
+#: ../../about.rst:791
+# 7515997e2a7f413f80d330d8a0e0fa9e
+msgid "`CLOUDSTACK-1990 <https://issues.apache.org/jira/browse/CLOUDSTACK-1990>`_"
+msgstr ""
+
+#: ../../about.rst:791
+# cb1d24a891854529a3ec234b0d44e143
+msgid "Docs: Update \"Choosing a Hypervisor\" feature matrix with new info..."
+msgstr ""
+
+#: ../../about.rst:792
+# 0e015d29cbf1478fb5d4362bd9c9a49c
+msgid "`CLOUDSTACK-2004 <https://issues.apache.org/jira/browse/CLOUDSTACK-2004>`_"
+msgstr ""
+
+#: ../../about.rst:792
+# 8ead7e56bda24b15b373057319d52ec0
+msgid "IPV6 - UI - Router details page - NICs tab - Guest traffic type does not displa..."
+msgstr ""
+
+#: ../../about.rst:793
+# 182bad5646834f53a01d33b9a1024a67
+msgid "`CLOUDSTACK-2009 <https://issues.apache.org/jira/browse/CLOUDSTACK-2009>`_"
+msgstr ""
+
+#: ../../about.rst:793
+# d2bcbe2e6d66493aab159ea738344281
+msgid "IPV6 - listNetwork() command does not return ip6dns1 and ip6dns2 entries...."
+msgstr ""
+
+#: ../../about.rst:794
+# 8bdf10c82eb6496d8fbbd4e18f864519
+msgid "`CLOUDSTACK-2022 <https://issues.apache.org/jira/browse/CLOUDSTACK-2022>`_"
+msgstr ""
+
+#: ../../about.rst:794
+# 281659dd94f447ab89811c990e83746e
+msgid "IPV6 - ListRouter() should return guestip6address parameter similar to guestaddr..."
+msgstr ""
+
+#: ../../about.rst:795
+# 1e8b51b1d53a454a8ca390a0297a01dd
+msgid "`CLOUDSTACK-2023 <https://issues.apache.org/jira/browse/CLOUDSTACK-2023>`_"
+msgstr ""
+
+#: ../../about.rst:795
+# b10aa54c02b043838ee7d2c646017e85
+msgid "IPV6 - Dashboard View - System wide Capacity for Shared Network IPs does not inc..."
+msgstr ""
+
+#: ../../about.rst:796
+# 22f167a09c0c4e0f9f59b8a68f2ee654
+msgid "`CLOUDSTACK-2026 <https://issues.apache.org/jira/browse/CLOUDSTACK-2026>`_"
+msgstr ""
+
+#: ../../about.rst:796
+# 009ae683f400491fb6b1488a79994f26
+msgid "IPV6 - UI - Provide the ability to turn off all the IPV6 parameters by using a g..."
+msgstr ""
+
+#: ../../about.rst:797
+# cb6a5a34bfd341669546708c9119f3d5
+msgid "`CLOUDSTACK-2099 <https://issues.apache.org/jira/browse/CLOUDSTACK-2099>`_"
+msgstr ""
+
+#: ../../about.rst:797
+# 9f2cc504258748d182ed67ac3081057c
+msgid "Not able to add a host after a failed attempt to add the host to a wrong cluster..."
+msgstr ""
+
+#: ../../about.rst:798
+# 3f141bf7fe7445f19888de01c3aa6ba5
+msgid "`CLOUDSTACK-2112 <https://issues.apache.org/jira/browse/CLOUDSTACK-2112>`_"
+msgstr ""
+
+#: ../../about.rst:798
+# f6f310af0449450d87cdd0a210fdb0de
+msgid "VM went in stopped state after live migration failed while vmscaleup..."
+msgstr ""
+
+#: ../../about.rst:799
+# d3d65c8d21b84f9d8c30ff44d359665a
+msgid "`CLOUDSTACK-2191 <https://issues.apache.org/jira/browse/CLOUDSTACK-2191>`_"
+msgstr ""
+
+#: ../../about.rst:799
+# b718e77dad2d4d70b5ccdf6481a0f2e2
+msgid "sanity tests for \"EIP : Optional public IP\" changes ..."
+msgstr ""
+
+#: ../../about.rst:800
+# 0c16e6776c314ce19cb0b493768ee7da
+msgid "`CLOUDSTACK-2291 <https://issues.apache.org/jira/browse/CLOUDSTACK-2291>`_"
+msgstr ""
+
+#: ../../about.rst:800
+# 5369f4749beb456180f8567cc47c0a64
+msgid "[BasicZone-XenServer] NPE while trying DeleteNetworkCmd..."
+msgstr ""
+
+#: ../../about.rst:801
+# cfbcaf313e0040ada9c9ae72834c0456
+msgid "`CLOUDSTACK-2293 <https://issues.apache.org/jira/browse/CLOUDSTACK-2293>`_"
+msgstr ""
+
+#: ../../about.rst:801
+# fe6538720b324d7fa3bd6ee56bb415db
+msgid "[BasicZone-XenServer] DeletePhysicalNetworkCmd is not deleting the external devi..."
+msgstr ""
+
+#: ../../about.rst:802
+# 19ce524dca9b4b5fbebe8c77e6dc485d
+msgid "`CLOUDSTACK-2412 <https://issues.apache.org/jira/browse/CLOUDSTACK-2412>`_"
+msgstr ""
+
+#: ../../about.rst:802
+# e690d342afc54f69a90ab070bb65b3b1
+msgid "[UI]Disable CiscoVnmc provider for PF/SourceNat/StaticNAT/Firewall dropdown list..."
+msgstr ""
+
+#: ../../about.rst:803
+# ad9cf8f340b34dfe99003df89c673bde
+msgid "`CLOUDSTACK-2418 <https://issues.apache.org/jira/browse/CLOUDSTACK-2418>`_"
+msgstr ""
+
+#: ../../about.rst:803
+# a084e2d66028435e808e334df768f7b1
+msgid "[GSLB] NPE while removing the GSLB enabled Netscaler device..."
+msgstr ""
+
+#: ../../about.rst:804
+# a7edeaba8ea5402091f7ac2d5746244a
+msgid "`CLOUDSTACK-2471 <https://issues.apache.org/jira/browse/CLOUDSTACK-2471>`_"
+msgstr ""
+
+#: ../../about.rst:804
+# 55fe809fb167495bb2dff8be76b93a0a
+msgid "test_host_high_availability.py refers to non-existent library method wait_for_vm..."
+msgstr ""
+
+#: ../../about.rst:805
+# cc41be7d4b0a4b93a6e967d08c5828ab
+msgid "`CLOUDSTACK-2501 <https://issues.apache.org/jira/browse/CLOUDSTACK-2501>`_"
+msgstr ""
+
+#: ../../about.rst:805
+# fc6042d3a4124e0fb977723466b9b649
+msgid "Scalevm - Need to take care of upgraded vms..."
+msgstr ""
+
+#: ../../about.rst:806
+# fbf8b9d297254a44af85b4ad0842ed76
+msgid "`CLOUDSTACK-2790 <https://issues.apache.org/jira/browse/CLOUDSTACK-2790>`_"
+msgstr ""
+
+#: ../../about.rst:806
+# ff03767769eb44ecb3a56532519d227a
+msgid "AWSAPI: packaging includes all .class files bloating size of the RPM..."
+msgstr ""
+
+#: ../../about.rst:807
+# c19f028510d04cc28bfcc5b751d5e3d2
+msgid "`CLOUDSTACK-2795 <https://issues.apache.org/jira/browse/CLOUDSTACK-2795>`_"
+msgstr ""
+
+#: ../../about.rst:807
+# c6229aa4fa8e4d8eb9c3721fdd4ebefa
+msgid "Create template failed..."
+msgstr ""
+
+#: ../../about.rst:808
+# cf5c8f8d78d446059ec5f4f3fed761eb
+msgid "`CLOUDSTACK-2845 <https://issues.apache.org/jira/browse/CLOUDSTACK-2845>`_"
+msgstr ""
+
+#: ../../about.rst:808
+# 37593b03408f427aa7de5a29a3748a9f
+msgid "[DB upgrade] [ExternalLoadBalancer NetworkUsage] Duplicate entries in the databa..."
+msgstr ""
+
+#: ../../about.rst:809
+# c020d1432c6d4c4fb0e6f6b4e5cd1bc4
+msgid "`CLOUDSTACK-2853 <https://issues.apache.org/jira/browse/CLOUDSTACK-2853>`_"
+msgstr ""
+
+#: ../../about.rst:809
+# 4f1e62857eb24e02bcb12508a788902d
+msgid "Cloudstack copies xenserver scripts while adding host even the server is KVM hos..."
+msgstr ""
+
+#: ../../about.rst:810
+# 1f3a582d8a534e73bf6e5c5b2955fb42
+msgid "`CLOUDSTACK-2860 <https://issues.apache.org/jira/browse/CLOUDSTACK-2860>`_"
+msgstr ""
+
+#: ../../about.rst:810
+# d520cc0ec5e94254a5e872f670506b50
+msgid "Add new host into VMWare Cluster failed..."
+msgstr ""
+
+#: ../../about.rst:811
+# cf603d42174143a788458e386ef792e6
+msgid "`CLOUDSTACK-2910 <https://issues.apache.org/jira/browse/CLOUDSTACK-2910>`_"
+msgstr ""
+
+#: ../../about.rst:811
+# c4f453abc31c4760b0de34cd22a0a842
+msgid "SC: Ctrl combinated with >. is not working of SC IME..."
+msgstr ""
+
+#: ../../about.rst:812
+# 57433b88f491415d8a3b3a0557e62e90
+msgid "`CLOUDSTACK-2911 <https://issues.apache.org/jira/browse/CLOUDSTACK-2911>`_"
+msgstr ""
+
+#: ../../about.rst:812
+# c2891aaa96d045f59fdc65bf0ec4c6b6
+msgid "KO: Key translation fails for KO keyboard Right Alt, Han/Eng, Hanja keys..."
+msgstr ""
+
+#: ../../about.rst:813
+# 20c6aa92e5e64bfdbbba9b9873593e6a
+msgid "`CLOUDSTACK-2919 <https://issues.apache.org/jira/browse/CLOUDSTACK-2919>`_"
+msgstr ""
+
+#: ../../about.rst:813
+# 730d2192fd4c480a9ba6ae4dc725c6f7
+msgid "Snapshot cannot be saved to full Secondary Storage, but doesn't utilize other Se..."
+msgstr ""
+
+#: ../../about.rst:814
+# fd7d4be76aad4992a084ee3c9b87316a
+msgid "`CLOUDSTACK-3066 <https://issues.apache.org/jira/browse/CLOUDSTACK-3066>`_"
+msgstr ""
+
+#: ../../about.rst:814
+# a7da0f1a26c54809b0d5050d00edba7c
+msgid "No Error message is popped up on UI when a dedicated resource is dedicated to an..."
+msgstr ""
+
+#: ../../about.rst:815
+# 19fee5eea48c419591b66b59ff3ca932
+msgid "`CLOUDSTACK-3095 <https://issues.apache.org/jira/browse/CLOUDSTACK-3095>`_"
+msgstr ""
+
+#: ../../about.rst:815
+# ad934f739e5b48aaa189bb5006e06667
+msgid "[UI][API]Able to add multiple tier networks to a deployed VM using “Add network”..."
+msgstr ""
+
+#: ../../about.rst:816
+# 1685d66996f24e2c9ac9749ada0c337b
+msgid "`CLOUDSTACK-3111 <https://issues.apache.org/jira/browse/CLOUDSTACK-3111>`_"
+msgstr ""
+
+#: ../../about.rst:816
+# 90300713d7a94be9b4a53a3cbeaf9fb3
+msgid "[UI] Storage tab is not showing the Hypervisor column as 'KVM' if the (root/data..."
+msgstr ""
+
+#: ../../about.rst:817
+# ffd4f821bc2943d2930d9af2c49845de
+msgid "`CLOUDSTACK-3186 <https://issues.apache.org/jira/browse/CLOUDSTACK-3186>`_"
+msgstr ""
+
+#: ../../about.rst:817
+# 40c67476c65141a384d19d5e91ebe8e2
+msgid "Duplicate entries in /etc/hosts file on VR after reboot..."
+msgstr ""
+
+#: ../../about.rst:818
+# 86a63899c98d4540b236af83fc53bcd8
+msgid "`CLOUDSTACK-3195 <https://issues.apache.org/jira/browse/CLOUDSTACK-3195>`_"
+msgstr ""
+
+#: ../../about.rst:818
+# a5d3b451f9e74a57994918f6196c038d
+msgid "cannot view/delete forward rules if underlying/target VM is destroyed first..."
+msgstr ""
+
+#: ../../about.rst:819
+# 6316b885181e4a6db59dd7a61d848af6
+msgid "`CLOUDSTACK-3197 <https://issues.apache.org/jira/browse/CLOUDSTACK-3197>`_"
+msgstr ""
+
+#: ../../about.rst:819
+# 9a68d9f3dded4c1fb613689212157f70
+msgid "UI: NTier: User is required to scroll down every single time to \"Create Network\"..."
+msgstr ""
+
+#: ../../about.rst:820
+# 37f216e52aa64ea3b056df50d30772dd
+msgid "`CLOUDSTACK-3212 <https://issues.apache.org/jira/browse/CLOUDSTACK-3212>`_"
+msgstr ""
+
+#: ../../about.rst:820
+# a03c118709644f8a873dd08ae8d2ecab
+msgid "[Advanced_With_SG]View IP Address Range in Default Guest Network page does not s..."
+msgstr ""
+
+#: ../../about.rst:821
+# 91d455d686d74e8a84d45acd20e37a38
+msgid "`CLOUDSTACK-3272 <https://issues.apache.org/jira/browse/CLOUDSTACK-3272>`_"
+msgstr ""
+
+#: ../../about.rst:821
+# 7d38aaa3e47c41f48e72a98ff6af02ac
+msgid "EventBus: add global config parameters to specify which category of events are p..."
+msgstr ""
+
+#: ../../about.rst:822
+# 99ae405f44074d508e663c61adc5e2fe
+msgid "`CLOUDSTACK-3338 <https://issues.apache.org/jira/browse/CLOUDSTACK-3338>`_"
+msgstr ""
+
+#: ../../about.rst:822
+# 2d4b8aba24aa42c48845921942823f32
+msgid "Please provide an icon for \"assignVMs\" action in internal LB rule detailView..."
+msgstr ""
+
+#: ../../about.rst:823
+# 24213f8f87694830a5969b7396aba336
+msgid "`CLOUDSTACK-3518 <https://issues.apache.org/jira/browse/CLOUDSTACK-3518>`_"
+msgstr ""
+
+#: ../../about.rst:823
+# 345de226be3d4fbfbb1fdc2c36df5b57
+msgid "G11n: JA,SC: Un translation issue occurred on the strings of different UI Specif..."
+msgstr ""
+
+#: ../../about.rst:824
+# 0cad2b157e0643d4b095f8e42ede3653
+msgid "`CLOUDSTACK-3519 <https://issues.apache.org/jira/browse/CLOUDSTACK-3519>`_"
+msgstr ""
+
+#: ../../about.rst:824
+# 10b012d926f74eeaaaef9f5d4472b2e8
+msgid "G11n: JA,SC: Un translation issue occurred on the strings of different dropdown ..."
+msgstr ""
+
+#: ../../about.rst:825
+# 6e4117836bd54627983b90ccb4fd972e
+msgid "`CLOUDSTACK-3520 <https://issues.apache.org/jira/browse/CLOUDSTACK-3520>`_"
+msgstr ""
+
+#: ../../about.rst:825
+# 77e8bb8d4eeb46c8b7e8bbe4235146b3
+msgid "G11n: JA,SC: Un translation issue occurred on the strings of different error/war..."
+msgstr ""
+
+#: ../../about.rst:826
+# 69e17113af284510bbdfe40df0585a2d
+msgid "`CLOUDSTACK-3521 <https://issues.apache.org/jira/browse/CLOUDSTACK-3521>`_"
+msgstr ""
+
+#: ../../about.rst:826
+# 1e1fea07835f4dcebeefc56a4449f575
+msgid "G11n: JA,SC: Un translation issue occurred on the strings of different tooltips...."
+msgstr ""
+
+#: ../../about.rst:827
+# 1d2d8b90f2764934b1dd1cd1fce29339
+msgid "`CLOUDSTACK-3522 <https://issues.apache.org/jira/browse/CLOUDSTACK-3522>`_"
+msgstr ""
+
+#: ../../about.rst:827
+# ca84e356f6e84a6da02cb9d318143ad8
+msgid "G11n: JA,SC: Un translation issue occurred on the strings of different buttons. ..."
+msgstr ""
+
+#: ../../about.rst:828
+# 01b9bc53bfd24beca70b3526031dbff7
+msgid "`CLOUDSTACK-3523 <https://issues.apache.org/jira/browse/CLOUDSTACK-3523>`_"
+msgstr ""
+
+#: ../../about.rst:828
+# 283fcc12a9264505b50208d8bf7d2a49
+msgid "G11n: JA,SC: Un translation issue occurred on the strings of different popup mes..."
+msgstr ""
+
+#: ../../about.rst:829
+# d727ab1d9cdd4390830b55c9e82a72c5
+msgid "`CLOUDSTACK-3528 <https://issues.apache.org/jira/browse/CLOUDSTACK-3528>`_"
+msgstr ""
+
+#: ../../about.rst:829
+# 0ddbdc2d48364a249bb650bcaf5bbab4
+msgid "[UI]list calls are in the processing state forever with invalid name provided wi..."
+msgstr ""
+
+#: ../../about.rst:830
+# e37353944bf54b4a85b99168017481d7
+msgid "`CLOUDSTACK-3579 <https://issues.apache.org/jira/browse/CLOUDSTACK-3579>`_"
+msgstr ""
+
+#: ../../about.rst:830
+# 29097d5077f441acb224dc0abe0531f2
+msgid "[DOC]CLONE - Physical Netwok traffic label update requires Management Server res..."
+msgstr ""
+
+#: ../../about.rst:831
+# 8068a0f7fb314d09890588a269e6fbda
+msgid "`CLOUDSTACK-3607 <https://issues.apache.org/jira/browse/CLOUDSTACK-3607>`_"
+msgstr ""
+
+#: ../../about.rst:831
+# 0c66c8aa620d4276a766aabedf6d27ef
+msgid "\"guest_os_hypervisor\" table has values that are not registered in \"guest_os\" tab..."
+msgstr ""
+
+#: ../../about.rst:832
+# 9b30b8f208624d7fb47de5f9c27d766a
+msgid "`CLOUDSTACK-3608 <https://issues.apache.org/jira/browse/CLOUDSTACK-3608>`_"
+msgstr ""
+
+#: ../../about.rst:832
+# a9abe6215c9a4ffb9c2ad532d94f5af6
+msgid "\"guest_os_hypervisor\" table has repeated mappings of hypervisor and guest OS..."
+msgstr ""
+
+#: ../../about.rst:833
+# 91dda0b77dd7409dbfaee7af5bfd4735
+msgid "`CLOUDSTACK-3656 <https://issues.apache.org/jira/browse/CLOUDSTACK-3656>`_"
+msgstr ""
+
+#: ../../about.rst:833
+# 6fac99ff12f44703800ef69bbd326ade
+msgid "lots of cloud-management should be changed to cloudstack-management..."
+msgstr ""
+
+#: ../../about.rst:834
+# 3c5649e1ab4c47e98e0e3c1fb5c42f85
+msgid "`CLOUDSTACK-3788 <https://issues.apache.org/jira/browse/CLOUDSTACK-3788>`_"
+msgstr ""
+
+#: ../../about.rst:834
+# 23bcc323dd9f4499b4b990f6b60e23de
+msgid "[KVM] Weekly Snapshot got stuck in \"Allocated State\"..."
+msgstr ""
+
+#: ../../about.rst:835
+# bf66b9022ae745eeae6dd0d830e04e4b
+msgid "`CLOUDSTACK-3813 <https://issues.apache.org/jira/browse/CLOUDSTACK-3813>`_"
+msgstr ""
+
+#: ../../about.rst:835
+# 565bddce4d1a4e5c9989fc4713209422
+msgid "\"Service.provider.create\" event doesnt mention about the Service Provider in the..."
+msgstr ""
+
+#: ../../about.rst:836
+# 5909690d894e4af98b88348330eaf80c
+msgid "`CLOUDSTACK-3880 <https://issues.apache.org/jira/browse/CLOUDSTACK-3880>`_"
+msgstr ""
+
+#: ../../about.rst:836
+# 92f4394bbccc4d73a7abf4986b7aef09
+msgid "/sbin/poweroff et al or ACPID initiated shutdown does not stop cloudstack-[usage..."
+msgstr ""
+
+#: ../../about.rst:837
+# af5f6c67184c43d69be0f8a84c3da845
+msgid "`CLOUDSTACK-3952 <https://issues.apache.org/jira/browse/CLOUDSTACK-3952>`_"
+msgstr ""
+
+#: ../../about.rst:837
+# 8f858d9cad2f40c88d8d2f5af1e32c6b
+msgid "Persist VR nic details in DB for additional public ranges..."
+msgstr ""
+
+#: ../../about.rst:838
+# d476952f126c4e0da77c036b61493842
+msgid "`CLOUDSTACK-3973 <https://issues.apache.org/jira/browse/CLOUDSTACK-3973>`_"
+msgstr ""
+
+#: ../../about.rst:838
+# 7699c9364349442f9b4f367fe0cc5406
+msgid "[GSLB] [LOGS Message] Improving logs messages for GSLB rule configuration..."
+msgstr ""
+
+#: ../../about.rst:839
+# db8c9e75bf7148cc912ab4272aefb08e
+msgid "`CLOUDSTACK-4016 <https://issues.apache.org/jira/browse/CLOUDSTACK-4016>`_"
+msgstr ""
+
+#: ../../about.rst:839
+# cf07892fab0e409587c77f182580f130
+msgid "[PortableIP] [VPC] listPublicIpAddresses lists the portable IP that was already ..."
+msgstr ""
+
+#: ../../about.rst:840
+# 8b9b04e7723c4229a66a7451ee9149fa
+msgid "`CLOUDSTACK-4139 <https://issues.apache.org/jira/browse/CLOUDSTACK-4139>`_"
+msgstr ""
+
+#: ../../about.rst:840
+# abdf622f1de14176894c2458dd68a5a5
+msgid "[VMWARE]Failed to resize the volumes which are created from snapshot of root vol..."
+msgstr ""
+
+#: ../../about.rst:841
+# 13c094402d2b473b8748820532360c82
+msgid "`CLOUDSTACK-4475 <https://issues.apache.org/jira/browse/CLOUDSTACK-4475>`_"
+msgstr ""
+
+#: ../../about.rst:841
+# d75b21c14d854c718eb7baa5ae577e57
+msgid "[ZWPS] attaching an uploaded volume to a VM is always going to first primary sto..."
+msgstr ""
+
+#: ../../about.rst:842
+# 963c1f4a34fa48e482e68ecfaf50fb0f
+msgid "`CLOUDSTACK-4517 <https://issues.apache.org/jira/browse/CLOUDSTACK-4517>`_"
+msgstr ""
+
+#: ../../about.rst:842
+# 05f689495c3e468b9616d4a552b6041a
+msgid "[upgrade][Vmware]Deployment of VM using centos 6.2 template registered before up..."
+msgstr ""
+
+#: ../../about.rst:843
+# d79bc70df3164ff498dd037943a1c7d7
+msgid "`CLOUDSTACK-4536 <https://issues.apache.org/jira/browse/CLOUDSTACK-4536>`_"
+msgstr ""
+
+#: ../../about.rst:843
+# 2c3c317a8b7641d4b7411985a2d77a7b
+msgid "[object_store_refactor] Inconsistency in volume store location on secondary stor..."
+msgstr ""
+
+#: ../../about.rst:844
+# 4815b5eae689480abd0b6b7fe91ec576
+msgid "`CLOUDSTACK-4568 <https://issues.apache.org/jira/browse/CLOUDSTACK-4568>`_"
+msgstr ""
+
+#: ../../about.rst:844
+# 0d644eebf87f4ed3974a233caa1875e8
+msgid "Need to add this to the release note of 4.2..."
+msgstr ""
+
+#: ../../about.rst:845
+# 4ed6d4de0686413d897b5d5bc1e47bf4
+msgid "`CLOUDSTACK-4587 <https://issues.apache.org/jira/browse/CLOUDSTACK-4587>`_"
+msgstr ""
+
+#: ../../about.rst:845
+# c6d1314a3416461ca735639c482cff75
+msgid "VM is failing to deploy on a Legacy zone after adding zone wide primary storage ..."
+msgstr ""
+
+#: ../../about.rst:846
+# d8e2c85fe6084953b0cd57ca1432252a
+msgid "`CLOUDSTACK-4644 <https://issues.apache.org/jira/browse/CLOUDSTACK-4644>`_"
+msgstr ""
+
+#: ../../about.rst:846
+# 91e0978f03174df9a0ce716746467e3e
+msgid "Tool Tip information is not provided for the new fields which are added in 4.2 (..."
+msgstr ""
+
+#: ../../about.rst:847
+# e353f5b9bce741fe9283b7fdbc4deb2d
+msgid "`CLOUDSTACK-4789 <https://issues.apache.org/jira/browse/CLOUDSTACK-4789>`_"
+msgstr ""
+
+#: ../../about.rst:847
+# b50cb97705294024b308c11f9ae725dc
+msgid "Fix ResourceMetaDataManagerTest..."
+msgstr ""
+
+#: ../../about.rst:848
+# f59060ae188240b0a5d2f26715489d57
+msgid "`CLOUDSTACK-4906 <https://issues.apache.org/jira/browse/CLOUDSTACK-4906>`_"
+msgstr ""
+
+#: ../../about.rst:848
+# 3f4c63f3409141339cbbc807ce029e12
+msgid "add netaddr to marvin dependency list..."
+msgstr ""
+
+#: ../../about.rst:849
+# 3ae875a8bd9b4099955b237366e34a36
+msgid "`CLOUDSTACK-4918 <https://issues.apache.org/jira/browse/CLOUDSTACK-4918>`_"
+msgstr ""
+
+#: ../../about.rst:849
+# f2fabf4d452845cb95c65f6182800a84
+msgid "VR can not be LB service provider without requiring to be source nat service pro..."
+msgstr ""
+
+#: ../../about.rst:850
+# 9401d4a09ea74a9ab860bf262eb09b0f
+msgid "`CLOUDSTACK-4951 <https://issues.apache.org/jira/browse/CLOUDSTACK-4951>`_"
+msgstr ""
+
+#: ../../about.rst:850
+# 6551a1ac300749d59dcff44e00aa4916
+msgid "[event framework] Action events do not have UUID ..."
+msgstr ""
+
+#: ../../about.rst:851
+# a3fca57fd51343fa9ef3d4895f877e2a
+msgid "`CLOUDSTACK-4987 <https://issues.apache.org/jira/browse/CLOUDSTACK-4987>`_"
+msgstr ""
+
+#: ../../about.rst:851
+# 1b9b350d3957469c9a768c94875ac1ea
+msgid "Able to add isolated network belonging to an account to a virtual machine belong..."
+msgstr ""
+
+#: ../../about.rst:852
+# 90ae3294042f4d0597f0efdd0730c5ad
+msgid "`CLOUDSTACK-5043 <https://issues.apache.org/jira/browse/CLOUDSTACK-5043>`_"
+msgstr ""
+
+#: ../../about.rst:852
+# 5af46297d4384855b7abd846b9067ba0
+msgid "[DOC] Page number missing and words truncated in PDFs since 4.1.1..."
+msgstr ""
+
+#: ../../about.rst:853
+# ec7562dd46d849bca09658dc943e540e
+msgid "`CLOUDSTACK-5044 <https://issues.apache.org/jira/browse/CLOUDSTACK-5044>`_"
+msgstr ""
+
+#: ../../about.rst:853
+# bd1e5dee91b042c38ef5a4158faf96ad
+msgid "Configuration Framework Issue..."
+msgstr ""
+
+#: ../../about.rst:854
+# 538f943df0004e81a22d5df035e09d51
+msgid "`CLOUDSTACK-5090 <https://issues.apache.org/jira/browse/CLOUDSTACK-5090>`_"
+msgstr ""
+
+#: ../../about.rst:854
+# 59f356260ca64980873ea42bcd645f41
+msgid "Anti-Affinity: VM fails to start on a cluster belonging to a different pod...."
+msgstr ""
+
+#: ../../about.rst:855
+# b546e94e9dde4baeb145a43938a9cd10
+msgid "`CLOUDSTACK-5157 <https://issues.apache.org/jira/browse/CLOUDSTACK-5157>`_"
+msgstr ""
+
+#: ../../about.rst:855
+# 2646dfaae349447ca25494693e0462a8
+msgid "Loadbalancer Response should include stickiness, health check and ssl certs info..."
+msgstr ""
+
+#: ../../about.rst:856
+# 6a05087655c44bff937a2124f49369b1
+msgid "`CLOUDSTACK-5243 <https://issues.apache.org/jira/browse/CLOUDSTACK-5243>`_"
+msgstr ""
+
+#: ../../about.rst:856
+# 74a8e6f41c7f45e089dc569457615115
+msgid "SSVM responds with timestamp..."
+msgstr ""
+
+#: ../../about.rst:857
+# 912b281864744e47ad4f479d19241f4a
+msgid "`CLOUDSTACK-5251 <https://issues.apache.org/jira/browse/CLOUDSTACK-5251>`_"
+msgstr ""
+
+#: ../../about.rst:857
+# 37eb832c9bb74af4b0cdae2afcfda41f
+msgid "No Error message is displayed when nonexistent NFS secondary storage is added t..."
+msgstr ""
+
+#: ../../about.rst:858
+# d66f80edf66146fba90143a9e484d542
+msgid "`CLOUDSTACK-5296 <https://issues.apache.org/jira/browse/CLOUDSTACK-5296>`_"
+msgstr ""
+
+#: ../../about.rst:858
+# 384f8cbdf3654fa2a9eb680df54dd5db
+msgid "Add certificate chain support for NS..."
+msgstr ""
+
+#: ../../about.rst:859
+# 0d998bd399984a29862cb44b71fcbf96
+msgid "`CLOUDSTACK-5307 <https://issues.apache.org/jira/browse/CLOUDSTACK-5307>`_"
+msgstr ""
+
+#: ../../about.rst:859
+# c49d878f41984cd78db12c9fcf070c95
+msgid "Same router is listed twice in router view of project..."
+msgstr ""
+
+#: ../../about.rst:860
+# 71665a82fbc141a6b01d1195697bb70b
+msgid "`CLOUDSTACK-5324 <https://issues.apache.org/jira/browse/CLOUDSTACK-5324>`_"
+msgstr ""
+
+#: ../../about.rst:860
+# d69f8f89c7df449588dae87cd97d1db3
+msgid "error message not proper when start VM fails because router reuires upgrade..."
+msgstr ""
+
+#: ../../about.rst:861
+# 63e3490bdbfe48dbb9bdda4817820de1
+msgid "`CLOUDSTACK-5342 <https://issues.apache.org/jira/browse/CLOUDSTACK-5342>`_"
+msgstr ""
+
+#: ../../about.rst:861
+# f57d012692bb4c758f3c308260279825
+msgid "[Automation] Add NIC to virtual machine fails in KVM..."
+msgstr ""
+
+#: ../../about.rst:862
+# 854279263dcc4bedbcfdca929874c649
+msgid "`CLOUDSTACK-5359 <https://issues.apache.org/jira/browse/CLOUDSTACK-5359>`_"
+msgstr ""
+
+#: ../../about.rst:862
+# 647abcdf85a14baaba9aed0902868228
+msgid "Failed to add second VMWARE cluster on a standard vSwitch enabled zone when vCen..."
+msgstr ""
+
+#: ../../about.rst:863
+# 18efbd385eca4042bcef93617ac7cfe8
+msgid "`CLOUDSTACK-5373 <https://issues.apache.org/jira/browse/CLOUDSTACK-5373>`_"
+msgstr ""
+
+#: ../../about.rst:863
+# 9271346879e54d97be130f4728cbafeb
+msgid "Web UI (non-English) is corrupted by text expansion..."
+msgstr ""
+
+#: ../../about.rst:864
+# 780d56f9e92f4cc2ba1aa64bb09cbe83
+msgid "`CLOUDSTACK-5395 <https://issues.apache.org/jira/browse/CLOUDSTACK-5395>`_"
+msgstr ""
+
+#: ../../about.rst:864
+# ad882c1bb8f0458f99d80ce32f2583f1
+msgid "When backup snapshot fails becasue of backup.snapshot.wait time exceeding , the ..."
+msgstr ""
+
+#: ../../about.rst:865
+# c7aef46fb8da442d878cdfe4a257324e
+msgid "`CLOUDSTACK-5410 <https://issues.apache.org/jira/browse/CLOUDSTACK-5410>`_"
+msgstr ""
+
+#: ../../about.rst:865
+# ff02b9c29cdf4a668a0f907fe938d4a9
+msgid "Changes for tracking logs using jobid is missing in 4.3..."
+msgstr ""
+
+#: ../../about.rst:866
+# a4a3473f1ace4015b9339ba63e271bce
+msgid "`CLOUDSTACK-5445 <https://issues.apache.org/jira/browse/CLOUDSTACK-5445>`_"
+msgstr ""
+
+#: ../../about.rst:866
+# 186b08ec8c3540e7aacbbda556a2c2a0
+msgid "DeleteImageStoreCmd does not use storage plugins to delete storage..."
+msgstr ""
+
+#: ../../about.rst:867
+# 40a5c6bb376349dea617c8c68dd955b3
+msgid "`CLOUDSTACK-5446 <https://issues.apache.org/jira/browse/CLOUDSTACK-5446>`_"
+msgstr ""
+
+#: ../../about.rst:867
+# 3c0a1722a6cd4281918c4ef6acc1a6a2
+msgid "KVM-Secondary Store down-Even after secondary store is brought back up after bei..."
+msgstr ""
+
+#: ../../about.rst:868
+# 19936917d18f4c77aaaad9e27e2310d9
+msgid "`CLOUDSTACK-5463 <https://issues.apache.org/jira/browse/CLOUDSTACK-5463>`_"
+msgstr ""
+
+#: ../../about.rst:868
+# ba8cbe65e4594d899fe24e54ae8b5992
+msgid "Hyper-V does not report stopped VMs..."
+msgstr ""
+
+#: ../../about.rst:869
+# 27f903e78a1e4230b29219c4ec66fe0d
+msgid "`CLOUDSTACK-5474 <https://issues.apache.org/jira/browse/CLOUDSTACK-5474>`_"
+msgstr ""
+
+#: ../../about.rst:869
+# b91a29a477054ec79e256c6a0fbb1ec3
+msgid "EventBus: RabbitMQ provider expects password to be stored in plain text...."
+msgstr ""
+
+#: ../../about.rst:870
+# 6982699ba50f4148a796aa00770ec36d
+msgid "`CLOUDSTACK-5475 <https://issues.apache.org/jira/browse/CLOUDSTACK-5475>`_"
+msgstr ""
+
+#: ../../about.rst:870
+# ee289fc9554d4907a9b7f6db1c055723
+msgid "cluster.cpu/(memory).allocated.capacity.disablethreshold is getting displayed mu..."
+msgstr ""
+
+#: ../../about.rst:871
+# bca6052a6e7e4389acbc8d0733971f61
+msgid "`CLOUDSTACK-5479 <https://issues.apache.org/jira/browse/CLOUDSTACK-5479>`_"
+msgstr ""
+
+#: ../../about.rst:871
+# 3b3df00c077a4ff183fbb31913209048
+msgid "Upgrading service offering of stopped vm should release the reserved capacity of..."
+msgstr ""
+
+#: ../../about.rst:872
+# c2c37fd269c848c696fd09f301f8ddde
+msgid "`CLOUDSTACK-5482 <https://issues.apache.org/jira/browse/CLOUDSTACK-5482>`_"
+msgstr ""
+
+#: ../../about.rst:872
+# 664f6ca3453948a0a2563e0d533babe6
+msgid "Vmware - When nfs was down for about 1 hour , when snapshots were in progress , ..."
+msgstr ""
+
+#: ../../about.rst:873
+# f5034cfaedc848bdaca9750fe15dbd26
+msgid "`CLOUDSTACK-5488 <https://issues.apache.org/jira/browse/CLOUDSTACK-5488>`_"
+msgstr ""
+
+#: ../../about.rst:873
+# a7dec60810d14854b7976d8efbb9a90b
+msgid "KVM:agent is still in stopped state even after host recovered from sudddent powe..."
+msgstr ""
+
+#: ../../about.rst:874
+# 3bb93b7ac2de4fed9677b7368e741971
+msgid "`CLOUDSTACK-5504 <https://issues.apache.org/jira/browse/CLOUDSTACK-5504>`_"
+msgstr ""
+
+#: ../../about.rst:874
+# 557f1ef5197b4a9ebbfa0a10d2744ffb
+msgid "Vmware-Primary store unavailable for 10 mts - All snapshot tasks reported failur..."
+msgstr ""
+
+#: ../../about.rst:875
+# 5ae6f7889af34ae083506fa75e899a67
+msgid "`CLOUDSTACK-5512 <https://issues.apache.org/jira/browse/CLOUDSTACK-5512>`_"
+msgstr ""
+
+#: ../../about.rst:875
+# 185288f7676b451691fe79f60cabb4ea
+msgid "template format name checking is crude and doesn't work with advanced URLs..."
+msgstr ""
+
+#: ../../about.rst:876
+# 99d37e013d50405a8b7e8c3fbe6bd1b8
+msgid "`CLOUDSTACK-5536 <https://issues.apache.org/jira/browse/CLOUDSTACK-5536>`_"
+msgstr ""
+
+#: ../../about.rst:876
+# 3313cc51b9c54b3ea48d14ba8da7fd5a
+msgid "Restarting cloudstack service with template download in progress creates redunda..."
+msgstr ""
+
+#: ../../about.rst:877
+# 6fc2b9f9f0cd4244b6cae357df2648c1
+msgid "`CLOUDSTACK-5546 <https://issues.apache.org/jira/browse/CLOUDSTACK-5546>`_"
+msgstr ""
+
+#: ../../about.rst:877
+# ad995e32134d42538c1ea2e43b381f39
+msgid "Extra tab for adding rules displayed for non-elb networks..."
+msgstr ""
+
+#: ../../about.rst:878
+# a54dbaac63214de8a33c2afb52bdeb22
+msgid "`CLOUDSTACK-5550 <https://issues.apache.org/jira/browse/CLOUDSTACK-5550>`_"
+msgstr ""
+
+#: ../../about.rst:878
+# 88355285abd84916851924fca618a14f
+msgid "UI - Api key and secret key not fully visible in user detail view...."
+msgstr ""
+
+#: ../../about.rst:879
+# 115fded8d9b14ae888df6d309ed00928
+msgid "`CLOUDSTACK-5561 <https://issues.apache.org/jira/browse/CLOUDSTACK-5561>`_"
+msgstr ""
+
+#: ../../about.rst:879
+# 7d3829818296496e96133bb776f55ced
+msgid "support of multiple nics for VR running in HyperV..."
+msgstr ""
+
+#: ../../about.rst:880
+# 5d53268c0d8649dd8fd8451e90bb2bbe
+msgid "`CLOUDSTACK-5563 <https://issues.apache.org/jira/browse/CLOUDSTACK-5563>`_"
+msgstr ""
+
+#: ../../about.rst:880
+# ace3df46440647d5855140e8dd8dc0e4
+msgid "path field is set to null in volumes table ..."
+msgstr ""
+
+#: ../../about.rst:881
+# a4c069ad32674f6eaaabb01ca26e7113
+msgid "`CLOUDSTACK-5576 <https://issues.apache.org/jira/browse/CLOUDSTACK-5576>`_"
+msgstr ""
+
+#: ../../about.rst:881
+# 29da54590cab44809148bf8c2e05d3ff
+msgid "RemoteVPNonVPC : Label needs to be changed to \"Enable Remote Access VPN\"..."
+msgstr ""
+
+#: ../../about.rst:882
+# 1c6be0b1e1c545c8aab7cf4c395ee39a
+msgid "`CLOUDSTACK-5583 <https://issues.apache.org/jira/browse/CLOUDSTACK-5583>`_"
+msgstr ""
+
+#: ../../about.rst:882
+# e58f05d86e0a4f419ace651927d24418
+msgid "vmopsSnapshot plug-in (XenServer) does not return an error when it should..."
+msgstr ""
+
+#: ../../about.rst:883
+# cbed0572c6e7432a86db4deb1ac862a1
+msgid "`CLOUDSTACK-5600 <https://issues.apache.org/jira/browse/CLOUDSTACK-5600>`_"
+msgstr ""
+
+#: ../../about.rst:883
+# f1979a44524844f2be872644261781d8
+msgid "Xenserver - After HA , CPVM's disk is corrupted resulting in CPVM being stuck in..."
+msgstr ""
+
+#: ../../about.rst:884
+# 0ab0fd8ed1bb438794ce77987189a38d
+msgid "`CLOUDSTACK-5616 <https://issues.apache.org/jira/browse/CLOUDSTACK-5616>`_"
+msgstr ""
+
+#: ../../about.rst:884
+# 66ca2c3ae557455a8e0bd6fc1cf71461
+msgid "[DBHA]:There is no way to know to which DB is the CS writing in the case of DBHA..."
+msgstr ""
+
+#: ../../about.rst:885
+# d7afa33b29a9481b81da8e9979c9fe99
+msgid "`CLOUDSTACK-5632 <https://issues.apache.org/jira/browse/CLOUDSTACK-5632>`_"
+msgstr ""
+
+#: ../../about.rst:885
+# 1fb27092752e48ebae6b13be3236cc36
+msgid "[Automation] XenServer - Template deletion fails with error \"Please specify a te..."
+msgstr ""
+
+#: ../../about.rst:886
+# 8faf542b4f8d49268ad3f077a273d0ea
+msgid "`CLOUDSTACK-5645 <https://issues.apache.org/jira/browse/CLOUDSTACK-5645>`_"
+msgstr ""
+
+#: ../../about.rst:886
+# 50778e9a2d4a4bcbbc88640e9166df7b
+msgid "Agent manager doesn't need to be aware of vms and their relationship to resource..."
+msgstr ""
+
+#: ../../about.rst:887
+# 18b251fdf12941b08ae9f51e40ad63b5
+msgid "`CLOUDSTACK-5673 <https://issues.apache.org/jira/browse/CLOUDSTACK-5673>`_"
+msgstr ""
+
+#: ../../about.rst:887
+# 37828a256ee04f84bef64abc33e23445
+msgid "[Hyper-V] Default IP address never configured on eth0 with default CentOS templa..."
+msgstr ""
+
+#: ../../about.rst:888
+# a1a62c2a7c7140d893ac132834fa2ac3
+msgid "`CLOUDSTACK-5685 <https://issues.apache.org/jira/browse/CLOUDSTACK-5685>`_"
+msgstr ""
+
+#: ../../about.rst:888
+# ef5d0499d90b4aa1ac23c4c2ed84ad54
+msgid "[Vmsync] - When VR is rebooted outside of cloudstack , there is no change in sta..."
+msgstr ""
+
+#: ../../about.rst:889
+# 05dfaa9b48b74d5ea1cd1e1465e47a37
+msgid "`CLOUDSTACK-5700 <https://issues.apache.org/jira/browse/CLOUDSTACK-5700>`_"
+msgstr ""
+
+#: ../../about.rst:889
+# ae47fe867c8c4bebbf91f2089da3de2c
+msgid "[Vmsync] - kvm- \"paused\" state of Vm is not synced to CS...."
+msgstr ""
+
+#: ../../about.rst:890
+# f5f9d1b9f7eb44a8a12525d5876edaf6
+msgid "`CLOUDSTACK-5719 <https://issues.apache.org/jira/browse/CLOUDSTACK-5719>`_"
+msgstr ""
+
+#: ../../about.rst:890
+# f4a44a6bee7a4174904606768d1b5317
+msgid "[UI] Not listing shared network offerings tagged on second physical network..."
+msgstr ""
+
+#: ../../about.rst:891
+# 6ce899d61b7c48d7a5672becc9c54d4e
+msgid "`CLOUDSTACK-5724 <https://issues.apache.org/jira/browse/CLOUDSTACK-5724>`_"
+msgstr ""
+
+#: ../../about.rst:891
+# 700f101ab73145708d1ba9a04087c56d
+msgid "Console Proxy View - when using ctl c , errors seen on the console proxy view...."
+msgstr ""
+
+#: ../../about.rst:892
+# ff9918b62f6a4a64ba52cca3f79d88b4
+msgid "`CLOUDSTACK-5743 <https://issues.apache.org/jira/browse/CLOUDSTACK-5743>`_"
+msgstr ""
+
+#: ../../about.rst:892
+# 98cbe0a9a1e8430897abd0b9af2db194
+msgid "Download ROOT Volume when the VM is in stopped state is failing with \"Forbidden..."
+msgstr ""
+
+#: ../../about.rst:893
+# d0cf5147264a41baa87388c9783ee790
+msgid "`CLOUDSTACK-5744 <https://issues.apache.org/jira/browse/CLOUDSTACK-5744>`_"
+msgstr ""
+
+#: ../../about.rst:893
+# 0f713dfd8c3c4df69483c843804baab2
+msgid "[Hyper-v] White screen on console window when more than two console sessions are..."
+msgstr ""
+
+#: ../../about.rst:894
+# 5aafc3f652cf44d692c4e1645a8bf3d4
+msgid "`CLOUDSTACK-5753 <https://issues.apache.org/jira/browse/CLOUDSTACK-5753>`_"
+msgstr ""
+
+#: ../../about.rst:894
+# 42cd0b6e37ad4404bdb40e46486fed21
+msgid "[Hyper-v] ConsoleProxyLoadReportCommand does not honor the default value of cons..."
+msgstr ""
+
+#: ../../about.rst:895
+# 5b013ab075a44ee6a6b3e33a2bae8f61
+msgid "`CLOUDSTACK-5762 <https://issues.apache.org/jira/browse/CLOUDSTACK-5762>`_"
+msgstr ""
+
+#: ../../about.rst:895
+# b0cbc6e65abd4f33a804cd00a9b9c695
+msgid "[dynamic compute offerings]UI change required for select compute offerinngs in ..."
+msgstr ""
+
+#: ../../about.rst:896
+# a634cee299e04a14b89a67fd6a94125c
+msgid "`CLOUDSTACK-5785 <https://issues.apache.org/jira/browse/CLOUDSTACK-5785>`_"
+msgstr ""
+
+#: ../../about.rst:896
+# f250b3550ce9466a9b47ac297dcea0c4
+msgid "VM display name cell not updated upon detaching volume from VM..."
+msgstr ""
+
+#: ../../about.rst:897
+# 57ad55a4e61647a0882bc09169fd6817
+msgid "`CLOUDSTACK-5794 <https://issues.apache.org/jira/browse/CLOUDSTACK-5794>`_"
+msgstr ""
+
+#: ../../about.rst:897
+# 58ad5190ba254101aecd3d7a72a35438
+msgid "[Hyper-v] Specify username and domain name together in the username field while ..."
+msgstr ""
+
+#: ../../about.rst:898
+# ebd16484f41f49ae8baf3ae988aece7e
+msgid "`CLOUDSTACK-5798 <https://issues.apache.org/jira/browse/CLOUDSTACK-5798>`_"
+msgstr ""
+
+#: ../../about.rst:898
+# 7a0969b4f07a49f7b7c462a014c2c8af
+msgid "While attaching a disk to WIN2012 VM with xencenter tools installed got error as..."
+msgstr ""
+
+#: ../../about.rst:899
+# 8e0ee4b7c893491baa02e0e3e93e8e16
+msgid "`CLOUDSTACK-5800 <https://issues.apache.org/jira/browse/CLOUDSTACK-5800>`_"
+msgstr ""
+
+#: ../../about.rst:899
+# 0ed8e78455684cdc8a491ed802c6965f
+msgid "While creating a VM from template (which is created based on existing newly crea..."
+msgstr ""
+
+#: ../../about.rst:900
+# 12d7be57f3964c8ea7f8764a8b5542e1
+msgid "`CLOUDSTACK-5807 <https://issues.apache.org/jira/browse/CLOUDSTACK-5807>`_"
+msgstr ""
+
+#: ../../about.rst:900
+# 1250e3a50d13426193f19f2eb26d8234
+msgid "Problem with shared datastore in VMware cluster with only one host..."
+msgstr ""
+
+#: ../../about.rst:901
+# 69f827f9a93e490dbd9e6f2741f2cbc5
+msgid "`CLOUDSTACK-5809 <https://issues.apache.org/jira/browse/CLOUDSTACK-5809>`_"
+msgstr ""
+
+#: ../../about.rst:901
+# 9074e58f0309446e8db7614d7e5e5127
+msgid "Not able to deploy Vm becasue of crossing pool.storage.allocate d.capacity.disab..."
+msgstr ""
+
+#: ../../about.rst:902
+# 286bdc5b6ef849dd8db6b248ee7d6f60
+msgid "`CLOUDSTACK-5822 <https://issues.apache.org/jira/browse/CLOUDSTACK-5822>`_"
+msgstr ""
+
+#: ../../about.rst:902
+# d289cc546c5e4df4ad53f642e8874469
+msgid "ssh keypairs are removed after rebooting vm..."
+msgstr ""
+
+#: ../../about.rst:903
+# 664f265b4db244e3b0c56c3095902135
+msgid "`CLOUDSTACK-5834 <https://issues.apache.org/jira/browse/CLOUDSTACK-5834>`_"
+msgstr ""
+
+#: ../../about.rst:903
+# 667f15f64c964fa2bac4bba9015e4084
+msgid "[upgrade]Error while collecting disk stats from : You gave an invalid object ref..."
+msgstr ""
+
+#: ../../about.rst:904
+# 786d10393be74d629c641bc4b38faf42
+msgid "`CLOUDSTACK-5836 <https://issues.apache.org/jira/browse/CLOUDSTACK-5836>`_"
+msgstr ""
+
+#: ../../about.rst:904
+# 7bc6019b2e7848dea5578204eaa13518
+msgid "When tried to reverting back to (disk attached)quiesced vm snapshot, got error a..."
+msgstr ""
+
+#: ../../about.rst:905
+# d7f0463020c34e5e834a238760a0f9e4
+msgid "`CLOUDSTACK-5843 <https://issues.apache.org/jira/browse/CLOUDSTACK-5843>`_"
+msgstr ""
+
+#: ../../about.rst:905
+# af63ab512388436084ef9a5e5e26cdc8
+msgid "registering templates/isos should be either async or changed to non-blocking..."
+msgstr ""
+
+#: ../../about.rst:906
+# cb9d311cd97a46f0916d2556e653472d
+msgid "`CLOUDSTACK-5845 <https://issues.apache.org/jira/browse/CLOUDSTACK-5845>`_"
+msgstr ""
+
+#: ../../about.rst:906
+# 05f37dcc77404e77b8c79111c57c9d36
+msgid "[doc] Document Heterogeneous Secondary Storage Not Supported in Region..."
+msgstr ""
+
+#: ../../about.rst:907
+# c293d49d6ee14f3691333a1fcc1d9cae
+msgid "`CLOUDSTACK-5847 <https://issues.apache.org/jira/browse/CLOUDSTACK-5847>`_"
+msgstr ""
+
+#: ../../about.rst:907
+# 6c44f7c2f2f24344bd8bdfa3b418dd4c
+msgid "[Hyper-V] [doc] Document creation of external vswitch for Hyper-V 2012 R2 (unlik..."
+msgstr ""
+
+#: ../../about.rst:908
+# bb970630a4c340cfab239c5db76d5673
+msgid "`CLOUDSTACK-5855 <https://issues.apache.org/jira/browse/CLOUDSTACK-5855>`_"
+msgstr ""
+
+#: ../../about.rst:908
+# e13098ccaa854d3390abfce0d6b31ab9
+msgid "Contrail: Slave compute host restarts when the master compute host is changed to..."
+msgstr ""
+
+#: ../../about.rst:909
+# 928b3d2337e943518c6970f197a7d678
+msgid "`CLOUDSTACK-5862 <https://issues.apache.org/jira/browse/CLOUDSTACK-5862>`_"
+msgstr ""
+
+#: ../../about.rst:909
+# 53ef125446914ddb909aed2609ec7675
+msgid "Template life cycle needs to be changed based on references of existing VMs to t..."
+msgstr ""
+
+#: ../../about.rst:910
+# a799fb1c163f495bb4b930f6407dd4c0
+msgid "`CLOUDSTACK-5866 <https://issues.apache.org/jira/browse/CLOUDSTACK-5866>`_"
+msgstr ""
+
+#: ../../about.rst:910
+# 3c604dcccc1547b981102ad43574b2ea
+msgid "Remove maven profile used to configure zone..."
+msgstr ""
+
+#: ../../about.rst:911
+# 2f2b6f0b3b5b44dd85e12acc6c23ef50
+msgid "`CLOUDSTACK-5876 <https://issues.apache.org/jira/browse/CLOUDSTACK-5876>`_"
+msgstr ""
+
+#: ../../about.rst:911
+# 8b6ef5cbb54a4ce5b0467f0011c7c1f1
+msgid "Contrail: After vrouter restart agent doesnt have info about the Network..."
+msgstr ""
+
+#: ../../about.rst:912
+# 893995e98cc7440ea0dba88aaa379dd0
+msgid "`CLOUDSTACK-5879 <https://issues.apache.org/jira/browse/CLOUDSTACK-5879>`_"
+msgstr ""
+
+#: ../../about.rst:912
+# 6571f89c2aae4158bbd1b99c772c38f5
+msgid "Document on how to use RabbitMq event bus with spring modularisation done in 4.3..."
+msgstr ""
+
+#: ../../about.rst:913
+# cc8c7cf6a4d94119bf49f81944e920d0
+msgid "`CLOUDSTACK-5897 <https://issues.apache.org/jira/browse/CLOUDSTACK-5897>`_"
+msgstr ""
+
+#: ../../about.rst:913
+# 403d2f7b85104696a671c5b93e8ea8bb
+msgid "Remove OVM in add cluster drop down list..."
+msgstr ""
+
+#: ../../about.rst:914
+# 2c4e82e8705045c080699b97100bedb1
+msgid "`CLOUDSTACK-5907 <https://issues.apache.org/jira/browse/CLOUDSTACK-5907>`_"
+msgstr ""
+
+#: ../../about.rst:914
+# f034b4782a2b43f3bb70c3310b99162b
+msgid "KVM/CLVM volumes are shown as Ovm hypervisor..."
+msgstr ""
+
+#: ../../about.rst:915
+# 9334e89d22934a17943a95a1a6d5e76d
+msgid "`CLOUDSTACK-5908 <https://issues.apache.org/jira/browse/CLOUDSTACK-5908>`_"
+msgstr ""
+
+#: ../../about.rst:915
+# 534e0c90b9384a20978f7e71bdb28087
+msgid "Fail to add VXLAN network to instance..."
+msgstr ""
+
+#: ../../about.rst:916
+# 7abee3bb9e2f426d8c64026e38aead1a
+msgid "`CLOUDSTACK-5910 <https://issues.apache.org/jira/browse/CLOUDSTACK-5910>`_"
+msgstr ""
+
+#: ../../about.rst:916
+# 949aa883624c49ec947c8f6043726b82
+msgid "mark the LDAP user as imported from LDAP..."
+msgstr ""
+
+#: ../../about.rst:917
+# ddb914164d494cb389f441f8cdde6e6c
+msgid "`CLOUDSTACK-5920 <https://issues.apache.org/jira/browse/CLOUDSTACK-5920>`_"
+msgstr ""
+
+#: ../../about.rst:917
+# c7c78875c79c41b6a408653ff602283e
+msgid "CloudStack IAM Plugin feature..."
+msgstr ""
+
+#: ../../about.rst:918
+# 8e519430e75d485a994dae2492b983f0
+msgid "`CLOUDSTACK-5926 <https://issues.apache.org/jira/browse/CLOUDSTACK-5926>`_"
+msgstr ""
+
+#: ../../about.rst:918
+# f40042d45fa045c69feac8f0d56523e9
+msgid "[Doc] Create 4.3 Release Notes..."
+msgstr ""
+
+#: ../../about.rst:919
+# 01274b0e8eb0455488738fe326b2ca4a
+msgid "`CLOUDSTACK-5931 <https://issues.apache.org/jira/browse/CLOUDSTACK-5931>`_"
+msgstr ""
+
+#: ../../about.rst:919
+# 2ad43a29eb2446c19054d4f4de8a412d
+msgid "Hyper-V agent does not release logon handle..."
+msgstr ""
+
+#: ../../about.rst:920
+# 7574c7a322544be1b263bb3ec5592bf0
+msgid "`CLOUDSTACK-5932 <https://issues.apache.org/jira/browse/CLOUDSTACK-5932>`_"
+msgstr ""
+
+#: ../../about.rst:920
+# 8959ea6a86f14c44b75082b5cf4a5504
+msgid "SystemVM scripts: the iso download urls need updating as current ones are obsole..."
+msgstr ""
+
+#: ../../about.rst:921
+# 9ba0283e6f494ab9a79dd828a4f01f72
+msgid "`CLOUDSTACK-5933 <https://issues.apache.org/jira/browse/CLOUDSTACK-5933>`_"
+msgstr ""
+
+#: ../../about.rst:921
+#: ../../about.rst:922
+#: ../../about.rst:923
+# 4386f9854460410f99be0fbf30839be2
+# c01f1d82b0b34f4f8e65a923f537f52c
+# ee091b1541c5408892806e573ea04f96
+msgid "Problem with VMware snapshot when datastore has a space in its name..."
+msgstr ""
+
+#: ../../about.rst:922
+# 29f18f2027654c7195ad40575c511e42
+msgid "`CLOUDSTACK-5934 <https://issues.apache.org/jira/browse/CLOUDSTACK-5934>`_"
+msgstr ""
+
+#: ../../about.rst:923
+# 2803afd9715643d9993f1bc6d35b48ea
+msgid "`CLOUDSTACK-5935 <https://issues.apache.org/jira/browse/CLOUDSTACK-5935>`_"
+msgstr ""
+
+#: ../../about.rst:924
+# 16e9afd202824f61b74b88fcd119ac31
+msgid "`CLOUDSTACK-5947 <https://issues.apache.org/jira/browse/CLOUDSTACK-5947>`_"
+msgstr ""
+
+#: ../../about.rst:924
+# eaefc26ccb71465b9dd709c1363ce884
+msgid "Exception for getRootDir.. NFSStorage when running with Simulator..."
+msgstr ""
+
+#: ../../about.rst:925
+# 33be46514ef34269bf6bf799e7a0a600
+msgid "`CLOUDSTACK-5951 <https://issues.apache.org/jira/browse/CLOUDSTACK-5951>`_"
+msgstr ""
+
+#: ../../about.rst:925
+# 04ebebcb83874e32b89e4f558668fdfc
+msgid "Fix base.py for Dynamic compute offerings..."
+msgstr ""
+
+#: ../../about.rst:926
+# 3603844f426d4800b2674bcc3b9b0ecf
+msgid "`CLOUDSTACK-5954 <https://issues.apache.org/jira/browse/CLOUDSTACK-5954>`_"
+msgstr ""
+
+#: ../../about.rst:926
+# 2543950ffe334bd7af6428c70e2b0bc1
+msgid "update-ssl.png missing from docs..."
+msgstr ""
+
+#: ../../about.rst:927
+# fe22a557e4a54a8db459927cbb92059e
+msgid "`CLOUDSTACK-5955 <https://issues.apache.org/jira/browse/CLOUDSTACK-5955>`_"
+msgstr ""
+
+#: ../../about.rst:927
+# 45fbb0c1ae664a41be751b48dea38610
+msgid "vm stuck in migrating if mgmt server is restarted..."
+msgstr ""
+
+#: ../../about.rst:928
+# 8da42368a75849949db98ccf97555530
+msgid "`CLOUDSTACK-5962 <https://issues.apache.org/jira/browse/CLOUDSTACK-5962>`_"
+msgstr ""
+
+#: ../../about.rst:928
+# fc01cb9dba774bf89888043588232727
+msgid "Value of Global parameter \"custom.diskoffering.size.min\" is not reflected in UI ..."
+msgstr ""
+
+#: ../../about.rst:929
+# 4b6f466a4e8643b9860fa0ded9ccac27
+msgid "`CLOUDSTACK-5972 <https://issues.apache.org/jira/browse/CLOUDSTACK-5972>`_"
+msgstr ""
+
+#: ../../about.rst:929
+# ee4e8088a3294f549933b776bd47f7ca
+msgid "[DOC] Service monitoring enable/disable from global setting..."
+msgstr ""
+
+#: ../../about.rst:930
+# b7080df2863f4a02ada36a7669fcafb3
+msgid "`CLOUDSTACK-5976 <https://issues.apache.org/jira/browse/CLOUDSTACK-5976>`_"
+msgstr ""
+
+#: ../../about.rst:930
+# 28f272835ca8486f8c0891e5bcf8f2dd
+msgid "[upgrade]Typo in \"ssh_keypairs\" table's foreign key constraints on the Upgraded ..."
+msgstr ""
+
+#: ../../about.rst:931
+# 9714620e8faf422e9fa107751abe5e3b
+msgid "`CLOUDSTACK-5982 <https://issues.apache.org/jira/browse/CLOUDSTACK-5982>`_"
+msgstr ""
+
+#: ../../about.rst:931
+# 2fc8a368b6f6459d872d5d634ba665da
+msgid "Fix response name for assign and unassign cert from lb..."
+msgstr ""
+
+#: ../../about.rst:932
+# f4acaba44ed241d6a8074c671b3512bd
+msgid "`CLOUDSTACK-5984 <https://issues.apache.org/jira/browse/CLOUDSTACK-5984>`_"
+msgstr ""
+
+#: ../../about.rst:932
+# 7362786c6c33486ea7a8946e592e3ca6
+msgid "addvmwaredc API call is not documented ..."
+msgstr ""
+
+#: ../../about.rst:933
+# 2429317d3e594bd39f9a9fcb598d8c04
+msgid "`CLOUDSTACK-5990 <https://issues.apache.org/jira/browse/CLOUDSTACK-5990>`_"
+msgstr ""
+
+#: ../../about.rst:933
+# 0c384ea6026045b1978af48b16642089
+msgid "[UI]: search by username while importing ldap users..."
+msgstr ""
+
+#: ../../about.rst:934
+# 78e319ed865c4e0fa5dc3f7ed5de0d13
+msgid "`CLOUDSTACK-5991 <https://issues.apache.org/jira/browse/CLOUDSTACK-5991>`_"
+msgstr ""
+
+#: ../../about.rst:934
+# 6ff88586054e4c1d82b6e99db1f9ba80
+msgid "[UI]Infinite scrolling should be enabled to the Ldap user add page..."
+msgstr ""
+
+#: ../../about.rst:935
+# f96e43ac77f04ecfb3dc785d65882fd3
+msgid "`CLOUDSTACK-5992 <https://issues.apache.org/jira/browse/CLOUDSTACK-5992>`_"
+msgstr ""
+
+#: ../../about.rst:935
+# c14aa9269b9d441397bfe8e512f12311
+msgid "[Upgrade] default values of configuraiton parameters in configuration table are ..."
+msgstr ""
+
+#: ../../about.rst:936
+# 115e1a722aec40dea274c772d85f8282
+msgid "`CLOUDSTACK-6032 <https://issues.apache.org/jira/browse/CLOUDSTACK-6032>`_"
+msgstr ""
+
+#: ../../about.rst:936
+# 04d499a0e71b4bcfb0d6e3ac86c4dff9
+msgid "[VmScaleup]service offering id is not getting changed in usage_vm_instance table..."
+msgstr ""
+
+#: ../../about.rst:937
+# bfaa76d737784b5f95c018f977157aac
+msgid "`CLOUDSTACK-6043 <https://issues.apache.org/jira/browse/CLOUDSTACK-6043>`_"
+msgstr ""
+
+#: ../../about.rst:937
+# ccc1bf14d57044fcbb50a3ac110729a4
+msgid "VMware detaching volume fails if volume has snapshots..."
+msgstr ""
+
+#: ../../about.rst:938
+# 9aa2b12288f1420aaff1cfc0743f8da9
+msgid "`CLOUDSTACK-6053 <https://issues.apache.org/jira/browse/CLOUDSTACK-6053>`_"
+msgstr ""
+
+#: ../../about.rst:938
+# 0d09a8008b58494cb60ebe19ca52393a
+msgid "While adding smb as primary or secondary the password should be uri encoded..."
+msgstr ""
+
+#: ../../about.rst:939
+# ea7673542e854e8b8b711ff94908a370
+msgid "`CLOUDSTACK-6069 <https://issues.apache.org/jira/browse/CLOUDSTACK-6069>`_"
+msgstr ""
+
+#: ../../about.rst:939
+# 747f609fab1f4c7ab98cf17ac0fee78b
+msgid "can't create privatgateway with vlan in a mixed network env..."
+msgstr ""
+
+#: ../../about.rst:940
+# 326fdaf624be4f64bf070a7c3e06a679
+msgid "`CLOUDSTACK-6072 <https://issues.apache.org/jira/browse/CLOUDSTACK-6072>`_"
+msgstr ""
+
+#: ../../about.rst:940
+# 2d55d9b75a474be4a4b7d5e5211819c6
+msgid "vxlan networks not deallocating vnet ids..."
+msgstr ""
+
+#: ../../about.rst:941
+# ff1b141db0744c36a592d1d91ed693b4
+msgid "`CLOUDSTACK-6075 <https://issues.apache.org/jira/browse/CLOUDSTACK-6075>`_"
+msgstr ""
+
+#: ../../about.rst:941
+# 9275c6fbfa4144458d09a323ddb8bae2
+msgid "Increase the ram size for router service offering ..."
+msgstr ""
+
+#: ../../about.rst:942
+# 99d3af9b1e5e4a058a7ae118be123d1e
+msgid "`CLOUDSTACK-124 <https://issues.apache.org/jira/browse/CLOUDSTACK-124>`_"
+msgstr ""
+
+#: ../../about.rst:942
+# 8b32bfa08c0b46d6aef684e18497b33d
+msgid "NetworkGarbageCollector not cleaning up networks..."
+msgstr ""
+
+#: ../../about.rst:943
+# c7b26358582f4b899243737fd06f4f37
+msgid "`CLOUDSTACK-231 <https://issues.apache.org/jira/browse/CLOUDSTACK-231>`_"
+msgstr ""
+
+#: ../../about.rst:943
+# 7708223f4e4448b789b13ce1051e7600
+msgid "Tag creation using special charecters ..."
+msgstr ""
+
+#: ../../about.rst:944
+# b1bfdf6469a148aeb6acf9f7d59c9822
+msgid "`CLOUDSTACK-245 <https://issues.apache.org/jira/browse/CLOUDSTACK-245>`_"
+msgstr ""
+
+#: ../../about.rst:944
+# 9646ba76ef4042be82d7fa965b4b4d52
+msgid "VPC ACLs are not stored and programmed consistently..."
+msgstr ""
+
+#: ../../about.rst:945
+# b5967ba18bb7411284a3490e7441a8ac
+msgid "`CLOUDSTACK-270 <https://issues.apache.org/jira/browse/CLOUDSTACK-270>`_"
+msgstr ""
+
+#: ../../about.rst:945
+# cfbf880966d54900827f3b15c49cb007
+msgid "Ui should not ask for a vlan range if the physical network isolation type is not..."
+msgstr ""
+
+#: ../../about.rst:946
+# 8dd70cedd961486b891f7e9f84e26355
+msgid "`CLOUDSTACK-300 <https://issues.apache.org/jira/browse/CLOUDSTACK-300>`_"
+msgstr ""
+
+#: ../../about.rst:946
+# e9a0c1d5e2464610827b27e605893f3c
+msgid "Creation of compute offering allow combination of local storage + HA..."
+msgstr ""
+
+#: ../../about.rst:947
+# c314d5cd2be1492494cc4e4ea1154d0a
+msgid "`CLOUDSTACK-310 <https://issues.apache.org/jira/browse/CLOUDSTACK-310>`_"
+msgstr ""
+
+#: ../../about.rst:947
+# dc667412a14d4fc69fc4b8ed16fe2bab
+msgid "Failed to add host - Plugin error..."
+msgstr ""
+
+#: ../../about.rst:948
+# 48d31a39636440bea18cce416c33fbb1
+msgid "`CLOUDSTACK-315 <https://issues.apache.org/jira/browse/CLOUDSTACK-315>`_"
+msgstr ""
+
+#: ../../about.rst:948
+# ae220428d8694c7fb40b3a5761b7fa63
+msgid "Infrastructure view does not show capacity values..."
+msgstr ""
+
+#: ../../about.rst:949
+# 5ede82ec7e3d49d091dc2d17da781c46
+msgid "`CLOUDSTACK-338 <https://issues.apache.org/jira/browse/CLOUDSTACK-338>`_"
+msgstr ""
+
+#: ../../about.rst:949
+# 07a190ee55074d1d819ebabc319c3e68
+msgid "Unique Names of Disk and Service Offerings in the database are prefixed with \"Cl..."
+msgstr ""
+
+#: ../../about.rst:950
+# ae36f1b0f52d44399375157f009f074b
+msgid "`CLOUDSTACK-458 <https://issues.apache.org/jira/browse/CLOUDSTACK-458>`_"
+msgstr ""
+
+#: ../../about.rst:950
+# d2f66c59719448bfaa2ce410d66f8988
+msgid "xen:snapshots:Storage gc fail to clean the failed snapshot images from secondary..."
+msgstr ""
+
+#: ../../about.rst:951
+# 47ae8a9bb8f6481cbd5e3cf677f76b58
+msgid "`CLOUDSTACK-469 <https://issues.apache.org/jira/browse/CLOUDSTACK-469>`_"
+msgstr ""
+
+#: ../../about.rst:951
+# 75fd3eb386254a40a083e972fa4d9a6e
+msgid "CloudStack Documentation Landing Page has Alignment Issues..."
+msgstr ""
+
+#: ../../about.rst:952
+# 806acce787f84760abfb775a59d638ad
+msgid "`CLOUDSTACK-963 <https://issues.apache.org/jira/browse/CLOUDSTACK-963>`_"
+msgstr ""
+
+#: ../../about.rst:952
+# 12fff80d2a504c49bbbd22824bdace67
+msgid "[cloud.utils.AnnotationHelper] class java.lang.Stringdoes not have a Table anno..."
+msgstr ""
+
+#: ../../about.rst:953
+# de17f1a800814328b23a1e708d2b1d52
+msgid "`CLOUDSTACK-969 <https://issues.apache.org/jira/browse/CLOUDSTACK-969>`_"
+msgstr ""
+
+#: ../../about.rst:953
+# 2d464e8f68a74405b04341a4a2d4adb8
+msgid "api: zone response lists vlan in it as \"vlan range of zone\" but the vlan belongs..."
+msgstr ""
+
+#: ../../about.rst:954
+# f1c3403f8032419e829ccd4f66929b52
+msgid "`CLOUDSTACK-1306 <https://issues.apache.org/jira/browse/CLOUDSTACK-1306>`_"
+msgstr ""
+
+#: ../../about.rst:954
+# dfc0360381c84cfaa6bc712e47d656e3
+msgid "Better Error message when trying to deploy Vm by passing static Ipv4 addresses t..."
+msgstr ""
+
+#: ../../about.rst:955
+# dd3b26e637654719bb43bdc9c4951b4b
+msgid "`CLOUDSTACK-1432 <https://issues.apache.org/jira/browse/CLOUDSTACK-1432>`_"
+msgstr ""
+
+#: ../../about.rst:955
+# 121ae86f157948aca5c4968ee689fdff
+msgid "[UI] Inconsistent field names in \"Add Cluster\" dialog..."
+msgstr ""
+
+#: ../../about.rst:956
+# edb4df0f0696493b89d2bbb6cc1cb883
+msgid "`CLOUDSTACK-1471 <https://issues.apache.org/jira/browse/CLOUDSTACK-1471>`_"
+msgstr ""
+
+#: ../../about.rst:956
+# 675b3aabed6342f89a73e1b339e1307d
+msgid "Pop up window for host details/(host related operation) are not properly alligne..."
+msgstr ""
+
+#: ../../about.rst:957
+# 1cde4cfe8a714ee09c622f4f55535fb6
+msgid "`CLOUDSTACK-1524 <https://issues.apache.org/jira/browse/CLOUDSTACK-1524>`_"
+msgstr ""
+
+#: ../../about.rst:957
+# 53711da9789c471c9c4ccddec57bfd73
+msgid "\"White-box\" effect changes when changing value in combo box..."
+msgstr ""
+
+#: ../../about.rst:958
+# c8b98ae00ee74a8fb6482e1d34e1e202
+msgid "`CLOUDSTACK-1725 <https://issues.apache.org/jira/browse/CLOUDSTACK-1725>`_"
+msgstr ""
+
+#: ../../about.rst:958
+# 04d1ceedb4cf4fd587951c61447daadd
+msgid "publican update_pot might overwrite license headers ..."
+msgstr ""
+
+#: ../../about.rst:959
+# 8a851e230e3e42be884bc41ebca07328
+msgid "`CLOUDSTACK-1932 <https://issues.apache.org/jira/browse/CLOUDSTACK-1932>`_"
+msgstr ""
+
+#: ../../about.rst:959
+# e8da1950cdbf43ce91092026157cd9aa
+msgid "AutoScale UI documentation doesn't mention the option appears only for NetScaler..."
+msgstr ""
+
+#: ../../about.rst:960
+# f57d54cd7d08437ab637326258386606
+msgid "`CLOUDSTACK-2000 <https://issues.apache.org/jira/browse/CLOUDSTACK-2000>`_"
+msgstr ""
+
+#: ../../about.rst:960
+# a2971c5c19f245b2884b505f192fcf00
+msgid "CS4.1 Installation document - cloud-install-sys-tmplt command documented in wron..."
+msgstr ""
+
+#: ../../about.rst:961
+# ef26a2d622594a9f8ae10db60449a3a9
+msgid "`CLOUDSTACK-2213 <https://issues.apache.org/jira/browse/CLOUDSTACK-2213>`_"
+msgstr ""
+
+#: ../../about.rst:961
+# c6f808586258497dbb707d2e7e55cf79
+msgid "russian language select failure..."
+msgstr ""
+
+#: ../../about.rst:962
+# 5b524111ffd5492f878176c4e14f4372
+msgid "`CLOUDSTACK-2345 <https://issues.apache.org/jira/browse/CLOUDSTACK-2345>`_"
+msgstr ""
+
+#: ../../about.rst:962
+# 999211c7bc964a1583b5570055024ce2
+msgid "[GSLB] deleting GSLB rules is not cleaning server info from GSLB device..."
+msgstr ""
+
+#: ../../about.rst:963
+# d9b8c98f542a4b1981d8d347f6aa9590
+msgid "`CLOUDSTACK-2436 <https://issues.apache.org/jira/browse/CLOUDSTACK-2436>`_"
+msgstr ""
+
+#: ../../about.rst:963
+# d4e2678c414e41d0b481b115b9c0f6ad
+msgid "Message \"You do not have any affinity groups. Please continue to the next step.\"..."
+msgstr ""
+
+#: ../../about.rst:964
+# 5ae6ab9b375f4c7bb3589a8050f99194
+msgid "`CLOUDSTACK-2439 <https://issues.apache.org/jira/browse/CLOUDSTACK-2439>`_"
+msgstr ""
+
+#: ../../about.rst:964
+# 87c6a77f806e447ab440b72510b524d8
+msgid "\"Domain\" field under login page should be mandatory for the non root accounts...."
+msgstr ""
+
+#: ../../about.rst:965
+# 02b4ebd93f48469899a2d01cda5705c5
+msgid "`CLOUDSTACK-2449 <https://issues.apache.org/jira/browse/CLOUDSTACK-2449>`_"
+msgstr ""
+
+#: ../../about.rst:965
+# 23efd36a35834b908f1e7a70a28b1633
+msgid "Dropdown menu for action button scaleup System VM shows all service offering inc..."
+msgstr ""
+
+#: ../../about.rst:966
+# 94c82b371e014e7db572a651a1d5a824
+msgid "`CLOUDSTACK-2453 <https://issues.apache.org/jira/browse/CLOUDSTACK-2453>`_"
+msgstr ""
+
+#: ../../about.rst:966
+# 51034807cd4e4520ba084944db0e4554
+msgid "Select view dropdown under \"Network\" is listing the options in the absence of ad..."
+msgstr ""
+
+#: ../../about.rst:967
+# b0f18de078274cd285d7efe5a03e5a4b
+msgid "`CLOUDSTACK-2464 <https://issues.apache.org/jira/browse/CLOUDSTACK-2464>`_"
+msgstr ""
+
+#: ../../about.rst:967
+# 4bcccc8e991e484886d3f5fb30acc412
+msgid "[GSLB][UI] \"Add GSLB\" wizard doesn't prompt for \"PersistenceType\"..."
+msgstr ""
+
+#: ../../about.rst:968
+# 0433e6fc645d4d8fa034ce5b0bf63ce6
+msgid "`CLOUDSTACK-2533 <https://issues.apache.org/jira/browse/CLOUDSTACK-2533>`_"
+msgstr ""
+
+#: ../../about.rst:968
+# aa4c2b01e0c04f75863646c8609878f5
+msgid "Add Network to VM dialog should only show those network in the dropdown which ar..."
+msgstr ""
+
+#: ../../about.rst:969
+# 3cd97e91d6a1494eb443dd53eac4aa64
+msgid "`CLOUDSTACK-2535 <https://issues.apache.org/jira/browse/CLOUDSTACK-2535>`_"
+msgstr ""
+
+#: ../../about.rst:969
+# 0101c1f722244acaa1ba52f563626d08
+msgid "Cleanup port-profiles that gets created on Nexus switch as part of network clean..."
+msgstr ""
+
+#: ../../about.rst:970
+# 37c4a36817b449e9972b80ad060501e5
+msgid "`CLOUDSTACK-2559 <https://issues.apache.org/jira/browse/CLOUDSTACK-2559>`_"
+msgstr ""
+
+#: ../../about.rst:970
+# da49f93acbc0417eb9d4a91a39995de6
+msgid "[UI]Resource Name should not be present in UI as it is not available in listASA1..."
+msgstr ""
+
+#: ../../about.rst:971
+# 9126137d611b484eb865a2c06479b140
+msgid "`CLOUDSTACK-2605 <https://issues.apache.org/jira/browse/CLOUDSTACK-2605>`_"
+msgstr ""
+
+#: ../../about.rst:971
+# 20a378f44363495daf91c485585537ed
+msgid "Add Network to VM Command button should not be displayed for VMs belonging to B..."
+msgstr ""
+
+#: ../../about.rst:972
+# 71c4c344ffdc4e958ec6f5f7eb89de43
+msgid "`CLOUDSTACK-2697 <https://issues.apache.org/jira/browse/CLOUDSTACK-2697>`_"
+msgstr ""
+
+#: ../../about.rst:972
+# 087ec5baecbd46b8846e00bc1da9f9a8
+msgid "cluster id in alert message is null {alertType:: 1 // dataCenterId:: 1 // podId:..."
+msgstr ""
+
+#: ../../about.rst:973
+# 4e8a9f82abd7415f92b69d5f019956d9
+msgid "`CLOUDSTACK-2714 <https://issues.apache.org/jira/browse/CLOUDSTACK-2714>`_"
+msgstr ""
+
+#: ../../about.rst:973
+# b9a8751bb231427d85be7a486e346356
+msgid "Setting tab should not be visible for user accounts ..."
+msgstr ""
+
+#: ../../about.rst:974
+# 7b464c32172d4ed098b0ce969b998693
+msgid "`CLOUDSTACK-2951 <https://issues.apache.org/jira/browse/CLOUDSTACK-2951>`_"
+msgstr ""
+
+#: ../../about.rst:974
+# e98639016fea473b8b49ca4284a11d10
+msgid "[UI][Mixed-Zone-Management] during \"add Instance\" wizard, listTemplates API is n..."
+msgstr ""
+
+#: ../../about.rst:975
+# 4d48945fe87b49b6a8ae81013698783e
+msgid "`CLOUDSTACK-2993 <https://issues.apache.org/jira/browse/CLOUDSTACK-2993>`_"
+msgstr ""
+
+#: ../../about.rst:975
+# 8d80e722daef45178724195a133b6709
+msgid "[PortableIPRange] remove some of the unused columns if they are not required fro..."
+msgstr ""
+
+#: ../../about.rst:976
+# 54ac3fa8558842c398ccdc38f1ced838
+msgid "`CLOUDSTACK-3025 <https://issues.apache.org/jira/browse/CLOUDSTACK-3025>`_"
+msgstr ""
+
+#: ../../about.rst:976
+# b7b3e51f968948999a7c60937b897275
+msgid "The page and pagesize parameters are not working in ListCfgsByCmds with zoneid s..."
+msgstr ""
+
+#: ../../about.rst:977
+# dd940c1b0f9a409c8915a129da92f71f
+msgid "`CLOUDSTACK-3063 <https://issues.apache.org/jira/browse/CLOUDSTACK-3063>`_"
+msgstr ""
+
+#: ../../about.rst:977
+# 0bc901711ad14ab8833396c81147cca4
+msgid "[UI]Dedicating a host to non-root domain which has instances of other domain(ro..."
+msgstr ""
+
+#: ../../about.rst:978
+# ac414d5911ce41269d2fefab50309adc
+msgid "`CLOUDSTACK-3101 <https://issues.apache.org/jira/browse/CLOUDSTACK-3101>`_"
+msgstr ""
+
+#: ../../about.rst:978
+# 3eba9b21c31641a781a0c4ddb2bc01a5
+msgid "[DR] list* APIs are not working based on the display* flags ..."
+msgstr ""
+
+#: ../../about.rst:979
+# f7478719c1de492aa2cf09123878a13d
+msgid "`CLOUDSTACK-3225 <https://issues.apache.org/jira/browse/CLOUDSTACK-3225>`_"
+msgstr ""
+
+#: ../../about.rst:979
+# 5256cc0bd9364f87893c336a74f84eb7
+msgid "Multiple NPEs when cloudstack-management service is restarted with incomplete ta..."
+msgstr ""
+
+#: ../../about.rst:980
+# 5cfa9678dc1e43d59b38335ad8f91b4b
+msgid "`CLOUDSTACK-3265 <https://issues.apache.org/jira/browse/CLOUDSTACK-3265>`_"
+msgstr ""
+
+#: ../../about.rst:980
+# e9452d8251b643a4b03bce41674f4808
+msgid "[Health Check for NS LB]Failure to create a lb health check policy returns a API..."
+msgstr ""
+
+#: ../../about.rst:981
+# be48a8cbb5e349f89e66aadcaa541ef0
+msgid "`CLOUDSTACK-3325 <https://issues.apache.org/jira/browse/CLOUDSTACK-3325>`_"
+msgstr ""
+
+#: ../../about.rst:981
+# 230ac59306494ea39197506b81def3eb
+msgid "[UI] [GSLB]: add text box to specify weight for each load balancer participating..."
+msgstr ""
+
+#: ../../about.rst:982
+# 2705c0569cab4d6b90594a92ec65bf31
+msgid "`CLOUDSTACK-3406 <https://issues.apache.org/jira/browse/CLOUDSTACK-3406>`_"
+msgstr ""
+
+#: ../../about.rst:982
+# a8db221ce45a462aa6c2e05bc2d2eb7f
+msgid "UI: ZWPS: Zone wizard: Primary storage creation failed after \"fix error\" in \"add..."
+msgstr ""
+
+#: ../../about.rst:983
+# cf74cfd96dad473fb014d18a35250300
+msgid "`CLOUDSTACK-3477 <https://issues.apache.org/jira/browse/CLOUDSTACK-3477>`_"
+msgstr ""
+
+#: ../../about.rst:983
+# 0fefc1717380441c884cfaaf701079a9
+msgid "resizeDataVolume doesn't return proper error message when trying to shrink volum..."
+msgstr ""
+
+#: ../../about.rst:984
+# d45364bf4020433a913170368f609aab
+msgid "`CLOUDSTACK-3553 <https://issues.apache.org/jira/browse/CLOUDSTACK-3553>`_"
+msgstr ""
+
+#: ../../about.rst:984
+# 184036e307fd4f178ececf263bca2e80
+msgid "[UI]UI remains in the processing state forever when it failed to delete primary ..."
+msgstr ""
+
+#: ../../about.rst:985
+# c83f20fc84834a368caa9314832e54c2
+msgid "`CLOUDSTACK-3671 <https://issues.apache.org/jira/browse/CLOUDSTACK-3671>`_"
+msgstr ""
+
+#: ../../about.rst:985
+# 6c9eb98bd694461dba8f878670819297
+msgid "Set Host, Management Network and Storage Network Properly when there are multipl..."
+msgstr ""
+
+#: ../../about.rst:986
+# 8371c5905f8f4e5bac7ba985216659a3
+msgid "`CLOUDSTACK-3815 <https://issues.apache.org/jira/browse/CLOUDSTACK-3815>`_"
+msgstr ""
+
+#: ../../about.rst:986
+# f7cd0dc26cf648d3bdb020562cea6331
+msgid "\"SNAPSHOT.CREATE\" event's states are not registered on the events table ..."
+msgstr ""
+
+#: ../../about.rst:987
+# 8ed515eec0e24857853cbf89a631c552
+msgid "`CLOUDSTACK-3895 <https://issues.apache.org/jira/browse/CLOUDSTACK-3895>`_"
+msgstr ""
+
+#: ../../about.rst:987
+# ca4f125698734ec2a5122e644275964e
+msgid "VM Migration across VMWARE clusters which are added with different switches(Stan..."
+msgstr ""
+
+#: ../../about.rst:988
+# 85e8ff947d084dd7854ab375d940dd59
+msgid "`CLOUDSTACK-3896 <https://issues.apache.org/jira/browse/CLOUDSTACK-3896>`_"
+msgstr ""
+
+#: ../../about.rst:988
+# bb7ceed6e27445e4b714a9b97059137f
+msgid "[PrimaryStorage] deleteStoragePool is not kicking GC for the downloaded system v..."
+msgstr ""
+
+#: ../../about.rst:989
+# 80946f9e1d0e403980f58aa5f38cc72b
+msgid "`CLOUDSTACK-3994 <https://issues.apache.org/jira/browse/CLOUDSTACK-3994>`_"
+msgstr ""
+
+#: ../../about.rst:989
+# d2eb7ba4d45f47e5b811bf87a2265439
+msgid "Wrong error notification is generated when Primary storage (Cluster wide) is add..."
+msgstr ""
+
+#: ../../about.rst:990
+# 36ecfa62f5374e4997c2097a2e5fded0
+msgid "`CLOUDSTACK-3995 <https://issues.apache.org/jira/browse/CLOUDSTACK-3995>`_"
+msgstr ""
+
+#: ../../about.rst:990
+# bad0ef8ab93941b79b098112471e1747
+msgid "No error notification is generated when Primary storage (Zonelevel) is added wit..."
+msgstr ""
+
+#: ../../about.rst:991
+# 3a6ea2da46bf4583b7e963b661b54ae6
+msgid "`CLOUDSTACK-4071 <https://issues.apache.org/jira/browse/CLOUDSTACK-4071>`_"
+msgstr ""
+
+#: ../../about.rst:991
+# 1ce38dc6184444e086d00b9b1fd04f99
+msgid "[UI] - Word 'Default' is misspelled in descripiton of integration.api.port under..."
+msgstr ""
+
+#: ../../about.rst:992
+# c0007d2c93044bf99b095370c615cd21
+msgid "`CLOUDSTACK-4183 <https://issues.apache.org/jira/browse/CLOUDSTACK-4183>`_"
+msgstr ""
+
+#: ../../about.rst:992
+# 2ed3c6d02b474efdbb1ce654717060cd
+msgid "[Non-Contiguous VLAN] Typos Appear in an Error Message..."
+msgstr ""
+
+#: ../../about.rst:993
+# 9b70ea321e5b4f1686c2c85c6effa7f9
+msgid "`CLOUDSTACK-5033 <https://issues.apache.org/jira/browse/CLOUDSTACK-5033>`_"
+msgstr ""
+
+#: ../../about.rst:993
+# a4955022f36b4cf5b266a6b2375b9c00
+msgid "ipaddress in management-server.log and api.log are wrong if management servers i..."
+msgstr ""
+
+#: ../../about.rst:994
+# b206de9da37d4f21b9fdf71ea84ed410
+msgid "`CLOUDSTACK-5309 <https://issues.apache.org/jira/browse/CLOUDSTACK-5309>`_"
+msgstr ""
+
+#: ../../about.rst:994
+# 636eb801e14e4cb99089f40959d90aac
+msgid "version number and requires upgrade fields are not displayed for routers when na..."
+msgstr ""
+
+#: ../../about.rst:995
+# 1e0b3de7dabd42efb0f8e58b0fdfe23a
+msgid "`CLOUDSTACK-5383 <https://issues.apache.org/jira/browse/CLOUDSTACK-5383>`_"
+msgstr ""
+
+#: ../../about.rst:995
+# 73fcaca57140407c8792a19a593bf46a
+msgid "Multiselect actions are not reset when a multiselect action is performed..."
+msgstr ""
+
+#: ../../about.rst:996
+# e2c36d9ee109437787c7f790163e29fc
+msgid "`CLOUDSTACK-5524 <https://issues.apache.org/jira/browse/CLOUDSTACK-5524>`_"
+msgstr ""
+
+#: ../../about.rst:996
+# dd855f85311343258dc38de841f135a5
+msgid "[UI]\"root disk size\" field should be removed from the add instance wizard since ..."
+msgstr ""
+
+#: ../../about.rst:997
+# 73ee1275ea204ae79c6c82b8906c5bb5
+msgid "`CLOUDSTACK-5824 <https://issues.apache.org/jira/browse/CLOUDSTACK-5824>`_"
+msgstr ""
+
+#: ../../about.rst:997
+# 26bef1d1e89546788c6a884da12ce926
+msgid "Delete snapshot UI always success..."
+msgstr ""
+
+#: ../../about.rst:998
+# 056dbd72918245b09d116ea105d79278
+msgid "`CLOUDSTACK-5885 <https://issues.apache.org/jira/browse/CLOUDSTACK-5885>`_"
+msgstr ""
+
+#: ../../about.rst:998
+# e3f62bba080b450b9f164f5b0847f14c
+msgid "When process receives error, loading overlay on listView element does not disapp..."
+msgstr ""
+
+#: ../../about.rst:999
+# f7ca472d1e224ce79149f204a00048b8
+msgid "`CLOUDSTACK-5912 <https://issues.apache.org/jira/browse/CLOUDSTACK-5912>`_"
+msgstr ""
+
+#: ../../about.rst:999
+# 0f15765758da4cad8200f0decb588c1c
+msgid "WARN [c.c.h.v.m.HttpNfcLeaseMO] (Thread-28:null) Unexpected exception..."
+msgstr ""
+
+#: ../../about.rst:1000
+# c1f7f973391041c3b69f90eae30ce69d
+msgid "`CLOUDSTACK-5522 <https://issues.apache.org/jira/browse/CLOUDSTACK-5522>`_"
+msgstr ""
+
+#: ../../about.rst:1000
+# 5cd7fcc7c9ba4472afab041350028c5f
+msgid "Need of one more column i.e., \"Name\" at Home>Storage - Snapshots..."
+msgstr ""
+
+#: ../../about.rst:1001
+# ebdb64c792754bd795a01b47c7c04262
+msgid "`CLOUDSTACK-5904 <https://issues.apache.org/jira/browse/CLOUDSTACK-5904>`_"
+msgstr ""
+
+#: ../../about.rst:1001
+# 209d812fb98b48c8b9efb9602b2a75b8
+msgid "Small UI bug..."
+msgstr ""
+
diff --git a/source/upgrading/locale/pot/api-changes.pot b/source/upgrading/locale/pot/api-changes.pot
new file mode 100644
index 0000000..99b23aa
--- /dev/null
+++ b/source/upgrading/locale/pot/api-changes.pot
@@ -0,0 +1,264 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 10:50-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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-changes.rst:17
+# ba3c427d54514fcbb45333056ddac76e
+msgid "API Changes Introduced in 4.3"
+msgstr ""
+
+#: ../../api-changes.rst:20
+# ac0cebd35d5147bfa3289ae8831108dc
+msgid "Hyper-V"
+msgstr ""
+
+#: ../../api-changes.rst:23
+#: ../../api-changes.rst:34
+#: ../../api-changes.rst:46
+#: ../../api-changes.rst:61
+#: ../../api-changes.rst:85
+# 955a92c6c2ff437eaa1b01299be0a430
+# 3fb690a5662046aea3941f9782a3003f
+# 4133920bc75849b496db274486745470
+# f084afe1d38443bcad6f69b21bdc9a4e
+# 3793b324cc7446ecae1de674c9e36250
+msgid "API"
+msgstr ""
+
+#: ../../api-changes.rst:23
+#: ../../api-changes.rst:34
+#: ../../api-changes.rst:46
+#: ../../api-changes.rst:61
+#: ../../api-changes.rst:85
+# 21d5370f36d345bc894fc1200e4081f9
+# c623048b8bf94859b0b097f12ee74713
+# aa321543f351469aa8bf9f4c69570632
+# b4620725124f4ca39d0801d26ba75523
+# a69e132cf53544b792e5f1353e2c76bb
+msgid "Description"
+msgstr ""
+
+#: ../../api-changes.rst:25
+# f84c6a42fdca46cead1e193c01ea0f36
+msgid "addPrimaryStorage"
+msgstr ""
+
+#: ../../api-changes.rst:25
+#: ../../api-changes.rst:27
+# b7b1569caab44ee194d04cfa2f093cd7
+# d96dec8d2ed94fcfa19ee61b6bf47ea4
+msgid "To this existing API, the following field has been added: smb"
+msgstr ""
+
+#: ../../api-changes.rst:27
+# 7e113e5e8d4a433ba8e474ad294bf3a6
+msgid "addImageStore"
+msgstr ""
+
+#: ../../api-changes.rst:31
+# ea6f6b8d8bea4bfb8611e410aa23b03b
+msgid "Reporting CPU Sockets"
+msgstr ""
+
+#: ../../api-changes.rst:36
+# d4e484335c9a41bdb56d8b41199bea68
+msgid "listhost"
+msgstr ""
+
+#: ../../api-changes.rst:36
+# 969d419ca1104937baa79b79992ae9c3
+msgid "To this existing API, the following request parameter has been added: hypervisor."
+msgstr ""
+
+#: ../../api-changes.rst:39
+# 428ae0b866d7410894881bb74ea18644
+msgid "The new response parameter added is: cpusockets"
+msgstr ""
+
+#: ../../api-changes.rst:43
+# 7b4b0cd175c84154970c81e7cdc7b3a9
+msgid "Publishing Alerts Using the Web ROOT Admin API"
+msgstr ""
+
+#: ../../api-changes.rst:48
+# 8802e94706de4386a95d3cc54757287d
+msgid "generateAlert"
+msgstr ""
+
+#: ../../api-changes.rst:48
+# 7afd7ac1a4374ddfade68ae4b7145077
+msgid "A new API has been added to generate and publish alerts for usage services. The usage services can be installed on a different host or the same host where the Management Server is running. This API is available only to the Root Admin."
+msgstr ""
+
+#: ../../api-changes.rst:53
+# 688d56d7e36344789602041c66ee2eb9
+msgid "listAlerts"
+msgstr ""
+
+#: ../../api-changes.rst:53
+# 719e52a73f9c4c65b1307d517d862602
+msgid "To this existing API, a new response parameter has been added: name. An alert can be searched on the basis of alert name."
+msgstr ""
+
+#: ../../api-changes.rst:58
+# d77837111f134448a932b10f2311b330
+msgid "Dynamic Compute Offering"
+msgstr ""
+
+#: ../../api-changes.rst:63
+# ae3bac83e3ba4ab4955af55be5412bcf
+msgid "DeployVM"
+msgstr ""
+
+#: ../../api-changes.rst:63
+#: ../../api-changes.rst:66
+#: ../../api-changes.rst:69
+#: ../../api-changes.rst:73
+#: ../../api-changes.rst:76
+# 1ea304c847ba4faf98010b8982060897
+# 3e9cbab447274b4f8f7b16468d5b3154
+# cef25de8237949318623399efa3525ae
+# 991f9597f76140d09457d911571620f4
+# de469f85256d4cb1942213fdc0b7a0de
+msgid "To this existing API, the following request parameter has been added: details."
+msgstr ""
+
+#: ../../api-changes.rst:66
+# 895d5daaa7774843ad94df397c9249d3
+msgid "ScaleVM"
+msgstr ""
+
+#: ../../api-changes.rst:69
+# 763e4875a4704cb9aeae3c5ef36e62bf
+msgid "ScaleSystemVM"
+msgstr ""
+
+#: ../../api-changes.rst:73
+# aca413becd874b3e94e98dbfb5841368
+msgid "UpgradeVM"
+msgstr ""
+
+#: ../../api-changes.rst:76
+# b63a6cb0827644ec8d8ff4162f7eb843
+msgid "UpgradeSystemVM"
+msgstr ""
+
+#: ../../api-changes.rst:82
+# 04d15e5183ab475885ff23f884a7dbbe
+msgid "Enhanced Upgrade for Virtual Routers"
+msgstr ""
+
+#: ../../api-changes.rst:87
+# 9f3806d0d16c41699e0215c2c130abda
+msgid "upgradeRouterTemplate"
+msgstr ""
+
+#: ../../api-changes.rst:87
+# c6ec881a8a154d5ba133c8fd5f74d7da
+msgid "This is a new API which has been added in this release."
+msgstr ""
+
+#: ../../api-changes.rst:89
+# befa20db57a74be8a359230be1af24ce
+msgid "The following are the request parameters:"
+msgstr ""
+
+#: ../../api-changes.rst:91
+# 6f699977277045c79e59ec79cab3b502
+msgid "id: Upgrade the specified VR"
+msgstr ""
+
+#: ../../api-changes.rst:93
+# b74ed7f780cf4c22b3e53e23a5cb8e1f
+msgid "zone\\_id : Upgrade the VRs in the specified zone."
+msgstr ""
+
+#: ../../api-changes.rst:95
+# be1c0c2053f1482796bede31d6f34259
+msgid "pod\\_id : Upgrade the VRs in the specified pod."
+msgstr ""
+
+#: ../../api-changes.rst:97
+# 52429b1c63df4c6396485c3faacfaffc
+msgid "cluster\\_id : Upgrade the VRs in the specified cluster."
+msgstr ""
+
+#: ../../api-changes.rst:99
+# 3e38ba91cf38452fbfd372fd80ac1570
+msgid "domain\\_id : Upgrade the VRs belonging to the specified domain."
+msgstr ""
+
+#: ../../api-changes.rst:102
+# e963e6310c1f4c1ebf55d701b9ab3dc9
+msgid "account\\_id : Upgrade the VRs belonging to the specified account."
+msgstr ""
+
+#: ../../api-changes.rst:106
+# 5de6819e7d1e44b7ae295686d139ff4c
+msgid "listRouters"
+msgstr ""
+
+#: ../../api-changes.rst:106
+# 4adb9f6a1e194f599eb100d4630f6147
+msgid "For this existing API, the following request parameters has been added:"
+msgstr ""
+
+#: ../../api-changes.rst:109
+# 6777db6a54104f2487b901226f296040
+msgid "version: Lists routers by specified version."
+msgstr ""
+
+#: ../../api-changes.rst:111
+# b1f9333e4c6a4ab3adb13836ac2cc5a2
+msgid "zone\\_id : lists routers in specified zone."
+msgstr ""
+
+#: ../../api-changes.rst:113
+# f9966a08aeb440de936e8767c3f57049
+msgid "pod\\_id : Lists routers in the specified pod."
+msgstr ""
+
+#: ../../api-changes.rst:115
+# 63feeeb27fc746ebbb4b24247c3a6e90
+msgid "cluster\\_id : Lists routers in the specified cluster."
+msgstr ""
+
+#: ../../api-changes.rst:117
+# d0f7cd6a28ed4a90999cd86dea6f3c4f
+msgid "domain\\_id : Lists routers owned by specified domain."
+msgstr ""
+
+#: ../../api-changes.rst:119
+# 791fa005ad454dccbea24b78ba0f89d9
+msgid "account: Lists routers owned by specified account."
+msgstr ""
+
+#: ../../api-changes.rst:121
+# 83e77c83dc4d42f4b140f2b1f0a8e0b4
+msgid "The following response parameters has been added:"
+msgstr ""
+
+#: ../../api-changes.rst:123
+# 1172e9fa8e9c4d259cd76493bc7b6c79
+msgid "version : (String) The router version. For example, 4.3.0."
+msgstr ""
+
+#: ../../api-changes.rst:125
+# ae72e022d08344519e876a7f109ec5a0
+msgid "requiresupgrade: (Boolean) The flag to indicate if the router template requires an upgrade."
+msgstr ""
+
diff --git a/source/upgrading/locale/pot/compat.pot b/source/upgrading/locale/pot/compat.pot
new file mode 100644
index 0000000..e3e2037
--- /dev/null
+++ b/source/upgrading/locale/pot/compat.pot
@@ -0,0 +1,178 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 10:50-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../compat.rst:17
+# 7dcdc4217c22473a81ac668b21647b37
+msgid "Compatibility Matrix"
+msgstr ""
+
+#: ../../compat.rst:20
+# 8d4b52f9b66d448b9a69ab17165262a0
+msgid "Supported OS Versions for Management Server"
+msgstr ""
+
+#: ../../compat.rst:22
+# 0ae4756c5d53482ca9345cb559fd81ed
+msgid "This section lists the operating systems that are supported for running CloudStack Management Server. Note that specific versions of the operating systems are tested, so compatibility with CentOS 6.3 may not indicate compatibility with CentOS 6.2, 6.1 and so on."
+msgstr ""
+
+#: ../../compat.rst:29
+# 0ea47e988e0b4b05a09b11c13865f105
+msgid "RHEL versions 5.5, 6.2, 6.3, and 6.4"
+msgstr ""
+
+#: ../../compat.rst:33
+# c33bff6adc4341f5843ad17cd93ad74a
+msgid "CentOS versions 6.3, and 6.4"
+msgstr ""
+
+#: ../../compat.rst:37
+# e158c85352234b2b8fcb1348693fc4bd
+msgid "Ubuntu 12.04 LTS"
+msgstr ""
+
+#: ../../compat.rst:40
+# 9e37962eae2943649f2adb63d92cee5e
+msgid "Supported Hypervisor Versions"
+msgstr ""
+
+#: ../../compat.rst:42
+# 1816866bc94a42b485496d310764cfd1
+msgid "CloudStack supports three hypervisor families, XenServer with XAPI, KVM, and VMware with vSphere."
+msgstr ""
+
+#: ../../compat.rst:47
+# fca8daf72ca94ba6b5b9e318e7138d92
+msgid "Windows Server 2012 R2 (with Hyper-V Role enabled)"
+msgstr ""
+
+#: ../../compat.rst:51
+# 523e97bb92534e7a8ed52ad24b2fec3a
+msgid "Hyper-V 2012 R2"
+msgstr ""
+
+#: ../../compat.rst:55
+# 731596ff7ace498086168e86a25404f6
+msgid "CentOS 6.2 with KVM"
+msgstr ""
+
+#: ../../compat.rst:59
+# 960c87f799574ed89dfae43d8cf51363
+msgid "Red Hat Enterprise Linux 6.2 with KVM"
+msgstr ""
+
+#: ../../compat.rst:63
+# 8006ba4927364513ba27467d64f04930
+msgid "XenServer 6.0.2 (with Hotfix)"
+msgstr ""
+
+#: ../../compat.rst:67
+# 8ebbef6847bb4d5292b6fb06e7360d04
+msgid "XenServer versions 6.1 and 6.2 SPI with latest hotfixes"
+msgstr ""
+
+#: ../../compat.rst:71
+# 4f2624b282df44c6bc750bffab900897
+msgid "VMware versions 5.0, 5.1, and 5.5"
+msgstr ""
+
+#: ../../compat.rst:75
+# a569cbfdefd14cb59f8bc1300d03a55a
+msgid "Bare metal hosts are supported, which have no hypervisor. These hosts can run the following operating systems:"
+msgstr ""
+
+#: ../../compat.rst:80
+# 8a615763e58c42beaaa685396a01ec76
+msgid "RHEL or CentOS, v6.2 or 6.3"
+msgstr ""
+
+#: ../../compat.rst:82
+# 652796f466944c76bbb2d46ad1c8b9ba
+msgid "Use libvirt version 0.9.10 for CentOS 6.3"
+msgstr ""
+
+#: ../../compat.rst:86
+# eebaea9300d3459da093f63732a176f6
+msgid "Fedora 17"
+msgstr ""
+
+#: ../../compat.rst:90
+# 99834b9a6c884d93b63e0860fe563fee
+msgid "Ubuntu 12.04"
+msgstr ""
+
+#: ../../compat.rst:92
+# e2141af52dfb4b98875d035e5b1a3e73
+msgid "For more information, see the Hypervisor Compatibility Matrix in the CloudStack Installation Guide."
+msgstr ""
+
+#: ../../compat.rst:96
+# 5552b7e5a3af40029b60fb85a52f0502
+msgid "Supported External Devices"
+msgstr ""
+
+#: ../../compat.rst:100
+# eb219ee7b9f045b8bd8c22cec06e6263
+msgid "Netscaler VPX and MPX versions 9.3 and 10.e"
+msgstr ""
+
+#: ../../compat.rst:104
+# 718d33d0f5654995834a3216a78fed28
+msgid "Netscaler SDX version 9.3"
+msgstr ""
+
+#: ../../compat.rst:108
+# 3cfc8160c41c42fb81ff964f23558e77
+msgid "SRX (Model srx100b) versions 10.3 or higher"
+msgstr ""
+
+#: ../../compat.rst:112
+# 321b963dfd42471ea19cdde2c11d217d
+msgid "F5 10.1.0 (Build 3341.1084)"
+msgstr ""
+
+#: ../../compat.rst:115
+# abdd765edd9445d2ba6b0f20a180754e
+msgid "Supported Browsers"
+msgstr ""
+
+#: ../../compat.rst:117
+# f104084e36f7417e9f8acc08e5e266f6
+msgid "The CloudStack Web-based UI should be compatible with any modern browser, but it's possible that some browsers will not render portions of the UI reliably, depending on their support of Web standards. For best results, one of the following browsers recommended:"
+msgstr ""
+
+#: ../../compat.rst:124
+# fb3a357088db4d04994c6ac2257df6ac
+msgid "Internet Explorer versions 10 and 11"
+msgstr ""
+
+#: ../../compat.rst:128
+# 3a1e6ffa3b4e42a9ac6c5ac93ee69739
+msgid "Firefox version 26 or lower"
+msgstr ""
+
+#: ../../compat.rst:132
+# 2e628ae20f68407086f328f8b8f8d50f
+msgid "Google Chrome version 31"
+msgstr ""
+
+#: ../../compat.rst:136
+# 25919615c96d4fcdadc243cd8780eabd
+msgid "Safari 5"
+msgstr ""
+
diff --git a/source/upgrading/locale/pot/index.pot b/source/upgrading/locale/pot/index.pot
new file mode 100644
index 0000000..70c8e25
--- /dev/null
+++ b/source/upgrading/locale/pot/index.pot
@@ -0,0 +1,38 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 10:50-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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:22
+# 7d5bf8f1976649478c6426b1d3aef1d5
+msgid "Welcome to Apache CloudStack Release Notes"
+msgstr ""
+
+#: ../../index.rst:24
+# c1a368cd41964089b29311f960268dd8
+msgid "This section describes the operating systems, browsers, and hypervisors that have been newly tested and certified compatible with CloudStack 4.3. Most earlier OS and hypervisor versions are also still supported for use with 4.3 It might work well on other platforms, but the platforms listed below are the ones that are specifically tested against and are more likely to be able to help troubleshoot if you run into any issues."
+msgstr ""
+
+#: ../../index.rst:32
+# 598272357f4545e0a3698227daf4d4c5
+msgid "This document contains information specific to this release of CloudStack, including upgrade instructions from prior releases, new features added to CloudStack, API changes, and issues fixed in the release. For installation instructions, please see the `Installation Guide <http://cloudstack-installation.readthedocs.org/en/latest/>`__. For usage and administration instructions, please see the `CloudStack Administrator's Guide <http://cloudstack-administration.readthedocs.org/en/latest/>`__."
+msgstr ""
+
+#: ../../index.rst:38
+# 742b63f90051452a841b8b2bb2e0a8c6
+msgid "Contents:"
+msgstr ""
+
diff --git a/source/upgrading/locale/pot/rnotes.pot b/source/upgrading/locale/pot/rnotes.pot
new file mode 100644
index 0000000..e1f188b
--- /dev/null
+++ b/source/upgrading/locale/pot/rnotes.pot
@@ -0,0 +1,2328 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache CloudStack
+# This file is distributed under the same license as the Apache CloudStack Release Notes package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Release Notes 4.3\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 10:50-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@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"
+
+#: ../../rnotes.rst:18
+# 54c7454410d84e6594ce715ce80428db
+msgid "Upgrade Instructions for 4.3"
+msgstr ""
+
+#: ../../rnotes.rst:20
+# 57d91f3b7f514ea5b4ce6c7dc9fae484
+msgid "This section contains upgrade instructions from prior versions of CloudStack to Apache CloudStack 4.3. We include instructions on upgrading to Apache CloudStack from pre-Apache versions of Citrix CloudStack (last version prior to Apache is 3.0.2) and from the releases made while CloudStack was in the Apache Incubator."
+msgstr ""
+
+#: ../../rnotes.rst:26
+# 763e012b1cbb4dbfb8b2c1a5defd86e1
+msgid "If you run into any issues during upgrades, please feel free to ask questions on users@cloudstack.apache.org or dev@cloudstack.apache.org."
+msgstr ""
+
+#: ../../rnotes.rst:30
+# f592714fe95442b58f46cbd186ab8d6b
+msgid "Upgrade from 4.2.0 to 4.3"
+msgstr ""
+
+#: ../../rnotes.rst:32
+# 917061081ce244cfa8e2220092d88b74
+msgid "This section will guide you from CloudStack 4.2 to CloudStack 4.3."
+msgstr ""
+
+#: ../../rnotes.rst:34
+#: ../../rnotes.rst:663
+#: ../../rnotes.rst:1197
+# 839670a6c8404e6689c28e22e9beb7e9
+# eece6c1c6b404f65a19955ad53a17a69
+# fd68172c2b124becb308ed2d888b75ed
+msgid "Any steps that are hypervisor-specific will be called out with a note."
+msgstr ""
+
+#: ../../rnotes.rst:36
+#: ../../rnotes.rst:665
+#: ../../rnotes.rst:1201
+# 20506c6042314b5997698ca5ecdd32bc
+# ecf5f433d7864bbb85a84b2eb594e262
+# 94af5eeae7374a17bad1d4de092723a3
+msgid "We recommend reading through this section once or twice before beginning your upgrade procedure, and working through it on a test system before working on a production system."
+msgstr ""
+
+#: ../../rnotes.rst:40
+#: ../../rnotes.rst:678
+#: ../../rnotes.rst:1223
+#: ../../rnotes.rst:1641
+# 610f07ad15974e7196b2525a32b7b5cb
+# c073d7072a1d448c9fccf973192b0c97
+# 2fc30d45bf6e431caa140fc3a8b608bf
+# 7e7237f14b174ac09084ae1b9298408e
+msgid "The following upgrade instructions should be performed regardless of hypervisor type."
+msgstr ""
+
+#: ../../rnotes.rst:46
+# 1a94b234a76c4ec3b5c85c9c69a4c5a3
+msgid "While running the existing 4.2.0 system, log in to the UI as root administrator."
+msgstr ""
+
+#: ../../rnotes.rst:51
+#: ../../rnotes.rst:687
+#: ../../rnotes.rst:1232
+#: ../../rnotes.rst:1650
+#: ../../rnotes.rst:2475
+# 87a195264f014fafbcacf225ee49b60b
+# 9fed87b0bb5a4d09aae99a02c1846689
+# 26927a7715d34d0d953e701f900ea4d9
+# d9bc4a3467a74b24b867b1a0a1caa7b5
+# e0ec5d46b97d44609764fd49dfb9543b
+msgid "In the left navigation bar, click Templates."
+msgstr ""
+
+#: ../../rnotes.rst:55
+#: ../../rnotes.rst:691
+#: ../../rnotes.rst:1236
+#: ../../rnotes.rst:1654
+#: ../../rnotes.rst:2479
+# 1460b4b9bc9f4b49897d8176ba4c18ea
+# ef1a66d85b964c02aad6e5bd7c9ff223
+# 4dc49fa62d6d41fda5ed15c69fe7d8ce
+# bfbcb45f64c84379a00a8c3e2cd4c6d0
+# 52dfafc4d6154db8a3d96e9451d751ca
+msgid "In Select view, click Templates."
+msgstr ""
+
+#: ../../rnotes.rst:59
+#: ../../rnotes.rst:695
+#: ../../rnotes.rst:1240
+#: ../../rnotes.rst:1658
+#: ../../rnotes.rst:2483
+# 7422067820c0448cb4f6415687b58ac9
+# fe2c9ff7bfa8453988c921b9e9e682e0
+# 1343f352d25b4016aa3f66b7395fdaeb
+# 6c9273ba79ab4c6c8ac374c1672f97b2
+# c6f38fb928704fa2811d411adbc16c44
+msgid "Click Register template."
+msgstr ""
+
+#: ../../rnotes.rst:61
+#: ../../rnotes.rst:697
+#: ../../rnotes.rst:1242
+#: ../../rnotes.rst:1660
+#: ../../rnotes.rst:2485
+# a76ecceb7ec74ea4bfb386b62103e7c3
+# 2e43da4879e5413980b0cbb4d1f72f81
+# b2c82fcc5b3e4b53b9b5b10b1f4e7b66
+# 8e701b724e54456b8ca1bbde10ae0401
+# fb7761768b634b5c9769ccc234f069d9
+msgid "The Register template dialog box is displayed."
+msgstr ""
+
+#: ../../rnotes.rst:65
+#: ../../rnotes.rst:701
+#: ../../rnotes.rst:1246
+#: ../../rnotes.rst:1664
+# 70b55ffc5f74419793e312019de9e564
+# 48518d425e5541379999468368d93944
+# faf7207893bc422098f1acb0f300245a
+# ca10148af6ed40148fd770eb5e279113
+msgid "In the Register template dialog box, specify the following values (do not change these):"
+msgstr ""
+
+#: ../../rnotes.rst:69
+#: ../../rnotes.rst:705
+#: ../../rnotes.rst:1250
+#: ../../rnotes.rst:1668
+#: ../../rnotes.rst:2493
+# fabaedd3a17741db9feaeaa9c362fb37
+# 07cdc119bb174abb9a6ba0908f42d98f
+# f84be91d03154ebba60ac0c21f123a4a
+# 0819fc5670a64cf985899d81eb6a0567
+# 0e0ef055e40148309d6b33f6f508fa0f
+msgid "Hypervisor"
+msgstr ""
+
+#: ../../rnotes.rst:69
+#: ../../rnotes.rst:705
+#: ../../rnotes.rst:1250
+#: ../../rnotes.rst:1668
+#: ../../rnotes.rst:2493
+# eecd155317fc4913af9ae17e5402fe0c
+# 44d451689de54435904df3eaed15c6f0
+# 39b27bcf07f94071befcc1805711deff
+# cf9d17e8177c4e93b9b67992e280ebfb
+# 29e46943e1444141a1114eeb88507893
+msgid "Description"
+msgstr ""
+
+#: ../../rnotes.rst:71
+#: ../../rnotes.rst:707
+#: ../../rnotes.rst:1252
+#: ../../rnotes.rst:1670
+#: ../../rnotes.rst:2495
+# d6afb75336f342f8a534be42065089fb
+# 532f8ff8909f456498a09b740bc4a771
+# cd57f897975941b9a72908e8980d3609
+# 8f2eff0c8c144754a71c6873c05fba77
+# a8a2066ef613402c92453d5557b1dfa8
+msgid "XenServer"
+msgstr ""
+
+#: ../../rnotes.rst:71
+#: ../../rnotes.rst:707
+#: ../../rnotes.rst:1252
+#: ../../rnotes.rst:1670
+#: ../../rnotes.rst:2495
+# 66f56c4c29964dc49d7849ae35f3ab41
+# 7354275f76ea42ddbcbec977ce04e605
+# 0d818adb6a2348e2a937d92162fb0d0a
+# bcf8b47f0fcd4c6c8df2eafcfa8a21bb
+# 04ff051f045c499b8ea2548a36c479ec
+msgid "Name: systemvm-xenserver-4.3"
+msgstr ""
+
+#: ../../rnotes.rst:73
+#: ../../rnotes.rst:709
+#: ../../rnotes.rst:1254
+#: ../../rnotes.rst:1672
+#: ../../rnotes.rst:2497
+# e653b05ef987495caf72f468b9f54088
+# 3ca05005c9484802aecfc51a71bad016
+# 343199a366194ae78ed699ba83825f21
+# 294c5a83fc154fdbaf0d85b5abb030c5
+# 44946d65c4c04a47a814c55aa2a4b2bd
+msgid "Description: systemvm-xenserver-4.3"
+msgstr ""
+
+#: ../../rnotes.rst:75
+#: ../../rnotes.rst:711
+#: ../../rnotes.rst:1256
+#: ../../rnotes.rst:1674
+#: ../../rnotes.rst:2499
+# a609d90e7d4c4bddbcb80a207c11a286
+# 66757efe5c6d40e1bac66e579369d368
+# a8b209e329fc41ce94ec334acd8dc4d0
+# a26c20ade808412ab062e4a910efcde5
+# bfaf491e156c4f9ab1e381a756900595
+msgid "URL: http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2"
+msgstr ""
+
+#: ../../rnotes.rst:78
+#: ../../rnotes.rst:103
+#: ../../rnotes.rst:128
+#: ../../rnotes.rst:714
+#: ../../rnotes.rst:739
+#: ../../rnotes.rst:764
+#: ../../rnotes.rst:1259
+#: ../../rnotes.rst:1284
+#: ../../rnotes.rst:1309
+#: ../../rnotes.rst:2502
+#: ../../rnotes.rst:2527
+#: ../../rnotes.rst:2552
+# de0fafc107fc49c3b6fbc36f8269f090
+# 8bbba7f914b9462899eadab5fe99a500
+# 90b1c14925764bcbb4fc5e37088cd019
+# 884e767f38e24dbd999a0e83acfe468d
+# cbb58b1d17dc4f689b54373fa72b56e7
+# a24107e19f334b0da5cd948e622d448a
+# 996bbb0c2d144c38b152e314f7a23232
+# e671eff0f36044eba588d538993a548c
+# f0aaee12a6f44476868b96b6fdd3c531
+# 2ca4ffa3c1f84c688eae9e77e09776b0
+# 5fa3f47e5f6547f1b37eaee9850f64ab
+# 80c606b15f08401f8f6a8f6cc92f506b
+msgid "Zone: Choose the zone where this hypervisor is used"
+msgstr ""
+
+#: ../../rnotes.rst:80
+#: ../../rnotes.rst:716
+#: ../../rnotes.rst:1261
+#: ../../rnotes.rst:1680
+#: ../../rnotes.rst:2504
+# fe7c9476f0514b018ce17653e4dfaf14
+# c341ba5d6d934a4c992e1f6acd331f62
+# 5b42af014a774e8d8dd54fdb8c23b303
+# 24a87f94fef44351a659f98f77747f4b
+# a6d3e78bba8f4bfcb966bee2e13cca0e
+msgid "Hypervisor: XenServer"
+msgstr ""
+
+#: ../../rnotes.rst:82
+#: ../../rnotes.rst:718
+#: ../../rnotes.rst:1263
+#: ../../rnotes.rst:1682
+#: ../../rnotes.rst:2506
+# 5554e0e0df47402c8cd7f4755b3d4868
+# 320573028f954ab98f16747898be6dc8
+# 42f4d9b411d84a60adc6ce2dd653d983
+# 56f769b429e049d89ca64fcde83dc0be
+# 22416e0f3d004d2688284421f68774c8
+msgid "Format: VHD"
+msgstr ""
+
+#: ../../rnotes.rst:84
+#: ../../rnotes.rst:109
+#: ../../rnotes.rst:134
+#: ../../rnotes.rst:720
+#: ../../rnotes.rst:745
+#: ../../rnotes.rst:770
+#: ../../rnotes.rst:1265
+#: ../../rnotes.rst:1290
+#: ../../rnotes.rst:1315
+#: ../../rnotes.rst:1684
+#: ../../rnotes.rst:1710
+#: ../../rnotes.rst:1736
+#: ../../rnotes.rst:2508
+#: ../../rnotes.rst:2533
+#: ../../rnotes.rst:2558
+# d1a09ebff7224e33ac7d506a813c135f
+# abad9407f6e940e182e25fe5a5bcc559
+# 24176593f87f48f3b1063c0bf4757d1a
+# 846d087370894ec997db899976c581ec
+# 77363b11bf8f45b2860fed0d89aded2c
+# 87f8d2767140463aad639149799f4b10
+# 53567f0780b140fc863f010767a1dd88
+# 8a62a060568e47108413074103342e9e
+# 255ae8f7fc4c4621871ce7dcdce1d8b5
+# e8b04e914e324ca292e1b7becd10526b
+# c5bc63756ae84c8eb56cc8bdbca0d4de
+# 0c94f10a791340a5969ed518669ef764
+# b9db27fc2ea046e89a7224f72a43b9bf
+# c42e4c649a594537b29df5cd32e4a9c6
+# 9b64303f1ab940228ad6ffa21b4b3708
+msgid "OS Type: Debian GNU/Linux 7.0 (64-bit) (or the highest Debian release number available in the dropdown)"
+msgstr ""
+
+#: ../../rnotes.rst:88
+#: ../../rnotes.rst:113
+#: ../../rnotes.rst:138
+#: ../../rnotes.rst:724
+#: ../../rnotes.rst:749
+#: ../../rnotes.rst:774
+#: ../../rnotes.rst:1269
+#: ../../rnotes.rst:1294
+#: ../../rnotes.rst:1319
+#: ../../rnotes.rst:1688
+#: ../../rnotes.rst:1714
+#: ../../rnotes.rst:1740
+#: ../../rnotes.rst:2512
+#: ../../rnotes.rst:2537
+#: ../../rnotes.rst:2562
+# 479ec153cf7744a58bf6baa44fe1c619
+# 24b8f48035d84b72a8f4c47323576ccf
+# a84fcb89af764c63bb3a034947720e7d
+# d271b9fb4ffe43e59fc78422db066959
+# 5f82c03996db4438b51606755ef7bdc5
+# 46df05a15ea14b3392b3033307cbdb7d
+# 780997a25ad34ba7a2fe4891411d9670
+# 504456709066415990989c9449524e06
+# 5f1f75483716496e9c99153f6c86ebfb
+# 333f78edb2754dffa05428377545ba64
+# 18d2f94dabae4361a399160cdaf8672a
+# e40c9d0e1f9348ec9dd645bdeb26c737
+# 85b52cf2fc2d43ba8e09c8956fe779c7
+# dada2cde337c4f53aa3c90663118bf9a
+# ab2f69b4810d40329f27aa52562da282
+msgid "Extractable: no"
+msgstr ""
+
+#: ../../rnotes.rst:90
+#: ../../rnotes.rst:115
+#: ../../rnotes.rst:140
+#: ../../rnotes.rst:726
+#: ../../rnotes.rst:751
+#: ../../rnotes.rst:776
+#: ../../rnotes.rst:1271
+#: ../../rnotes.rst:1296
+#: ../../rnotes.rst:1321
+#: ../../rnotes.rst:1690
+#: ../../rnotes.rst:1716
+#: ../../rnotes.rst:1742
+#: ../../rnotes.rst:2514
+#: ../../rnotes.rst:2539
+#: ../../rnotes.rst:2564
+# 32ec5ca5289e4f129ed8b9aeeb8ee595
+# 73d0634d1dc64dd4b73bfa7bc87ddd56
+# 30bbf2f539ef468c84d4915726ea4201
+# 22ed7912f287421993ea7305350b7be2
+# d4173d6cf7194f87b55b66cf62bdd149
+# 995aba5ec4c842a59e7a614550ebbc5e
+# 248d5aa2dc504fa8a76b5d555bab3d04
+# c7b4241023184c6982c36aa1e36b2416
+# e5be91f0f616411eaa9f1867b25ebe84
+# 5512ab3950c04d088703fd29f2480061
+# 18d0087fe2ba4ca39d320698ff00ef8d
+# 42128b849be24efea31e76b92f424fb5
+# e5130ebea45a4a5e8e72f57854852840
+# 2212dca5cb964150966626b0d26163c6
+# c58f8deb9dbd4b6980e3f74dce83bf63
+msgid "Password Enabled: no"
+msgstr ""
+
+#: ../../rnotes.rst:92
+#: ../../rnotes.rst:117
+#: ../../rnotes.rst:142
+#: ../../rnotes.rst:728
+#: ../../rnotes.rst:753
+#: ../../rnotes.rst:778
+#: ../../rnotes.rst:1273
+#: ../../rnotes.rst:1298
+#: ../../rnotes.rst:1323
+#: ../../rnotes.rst:1692
+#: ../../rnotes.rst:1718
+#: ../../rnotes.rst:1744
+#: ../../rnotes.rst:2516
+#: ../../rnotes.rst:2541
+#: ../../rnotes.rst:2566
+# 2389803696f546b487bef7ed63fe9cf1
+# 031bd5b6d8fd4537a63882344d81462d
+# dd86b4c235cb4eb08ab8931433e394b6
+# 26c77b27863a499385e36d338318feff
+# 045ba7ada091465782397d1524eee5e7
+# a0dc2127e843432b87c88f649301c454
+# ff5b8fd2272d4dd192d2bb6574a6d457
+# 79921a08ae2e43b59d6807a4af32cfff
+# 418158fbc34b40d9861b178b0a409a2f
+# a7777a2783f142a8842bf36186dbf842
+# 86936dadb1ea48259f5872e8cc7bb683
+# 0807bf02f2ff4b0d9922ff2c24f40154
+# bab7722e44e14d88b3e1ebe4a534bf42
+# 0c66fa015dbc42b5b24b9bb46c721441
+# 76c1d0c642a449cf8e8c3c0a62833df4
+msgid "Public: no"
+msgstr ""
+
+#: ../../rnotes.rst:94
+#: ../../rnotes.rst:119
+#: ../../rnotes.rst:144
+#: ../../rnotes.rst:730
+#: ../../rnotes.rst:755
+#: ../../rnotes.rst:780
+#: ../../rnotes.rst:1275
+#: ../../rnotes.rst:1300
+#: ../../rnotes.rst:1325
+#: ../../rnotes.rst:1694
+#: ../../rnotes.rst:1720
+#: ../../rnotes.rst:1746
+#: ../../rnotes.rst:2518
+#: ../../rnotes.rst:2543
+#: ../../rnotes.rst:2568
+# 4c17b6e131e142cfaa3d305806fd7523
+# dbdd68d63a144465981a1b5d53bf2598
+# a6053a4500e043a39a12d95a50afc4e1
+# 9bf7ce3a64cf4686b21fa34bd30f2bf7
+# d568aaf2c5ff400e8d47fb031ee99220
+# 20f48bc71cb547d89b7bb0fcae240414
+# 47850a9184a347e488fceb137b451c7d
+# 9932a3d73a08419d98e74cdb5091123a
+# 340e155b466a4f9abcadd9018298d165
+# 6f33f6462cc44834b05ae27a00c57970
+# a8ab610725ec45be8a19282146c5f392
+# cb798e1bb4e74be2902a55efaa50560f
+# cf257a5fe2a347a9ba4dfdef870079de
+# 8de20e3c772c4faeb7e9fb6f046277c6
+# db6be797a2414885abe44cd6bbb78e6a
+msgid "Featured: no"
+msgstr ""
+
+#: ../../rnotes.rst:96
+#: ../../rnotes.rst:732
+#: ../../rnotes.rst:1277
+#: ../../rnotes.rst:1696
+#: ../../rnotes.rst:2520
+# db00d07c960741289aee5f8142d2e368
+# f5748f546a024355a3f198d2f629b90d
+# 5b2c304631934350a0ea7f67fe4416a5
+# 92273fee3e894b5fbe410ad5a579b1c6
+# 74e6eb6c9150498988fbc79ee254c3f0
+msgid "KVM"
+msgstr ""
+
+#: ../../rnotes.rst:96
+#: ../../rnotes.rst:732
+#: ../../rnotes.rst:1277
+#: ../../rnotes.rst:1696
+#: ../../rnotes.rst:2520
+# c37736f0a31b446fbc7a6841614cf71c
+# 0f316cbb0b5f470eb6de77a262ac6753
+# cd161a821ed644ae8ee5784e026676de
+# ac775fa72e52423c8c5598eb94481650
+# 9bc64751dd5740a0a32fd3a5ddc6a333
+msgid "Name: systemvm-kvm-4.3"
+msgstr ""
+
+#: ../../rnotes.rst:98
+#: ../../rnotes.rst:734
+#: ../../rnotes.rst:1279
+#: ../../rnotes.rst:1698
+#: ../../rnotes.rst:2522
+# a656549bdd5247f9afc62d5fc8274746
+# 2f025a6a9fb1499d988c0ce4cad3269d
+# 0735ca296d0b405fbd2edb3fde6e4dd9
+# 7982d040783d48eeb0f082ec3a964eec
+# b676371c6d9048558d21532594e0b739
+msgid "Description: systemvm-kvm-4.3"
+msgstr ""
+
+#: ../../rnotes.rst:100
+#: ../../rnotes.rst:736
+#: ../../rnotes.rst:1281
+#: ../../rnotes.rst:1700
+#: ../../rnotes.rst:2524
+# e34e7276eb9b415ea037b17c9551cad6
+# 1109b770c4fa4291afc17e19e29b9707
+# b11d6d74b8e340d2af1246f535bed9e1
+# 9ded492ee518410f88bfa49eab1e31b8
+# 3fb14024946f4d70b472ccc0fa7b876a
+msgid "URL: http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-kvm.qcow2.bz2"
+msgstr ""
+
+#: ../../rnotes.rst:105
+#: ../../rnotes.rst:741
+#: ../../rnotes.rst:1286
+#: ../../rnotes.rst:1706
+#: ../../rnotes.rst:2529
+# 62e429365b8f4214a44101104a4e2559
+# c2e845dfc5c94eb18daa21878999de42
+# 4bfbb7a1589642c09758deb322b60cfd
+# b877f732e57e45d2ae9d2ea7df035d6f
+# c9eb933ce083414a9edd3435e48eba2b
+msgid "Hypervisor: KVM"
+msgstr ""
+
+#: ../../rnotes.rst:107
+#: ../../rnotes.rst:743
+#: ../../rnotes.rst:1288
+#: ../../rnotes.rst:1708
+#: ../../rnotes.rst:2531
+# 069d369782c24899a2e100b375f13280
+# 77946a1996684db89326b05e56f5fe99
+# 828baee68962477484111e334b362b88
+# 30f5abf4b9154e52b8c19bb6939b7a83
+# 5a1a142d0a5d4b5cbcb82d8807818791
+msgid "Format: QCOW2"
+msgstr ""
+
+#: ../../rnotes.rst:121
+#: ../../rnotes.rst:757
+#: ../../rnotes.rst:1302
+#: ../../rnotes.rst:1722
+#: ../../rnotes.rst:2545
+# c2993bf4a5114311bed8d66a9c476908
+# cff8a056b7134da0a3029ebe635b0be9
+# 75461d4a82934e86b29790b58fd37d0e
+# 407967fd891d4b618ee98fffd9e0d946
+# 6ddde7782a414cc69f3738e33d31b902
+msgid "VMware"
+msgstr ""
+
+#: ../../rnotes.rst:121
+#: ../../rnotes.rst:757
+#: ../../rnotes.rst:1302
+#: ../../rnotes.rst:1722
+#: ../../rnotes.rst:2545
+# 4bc55164d5d741c7b5be740b658e0787
+# e3ed715b7f1346e9b612535f6dfaf40b
+# 6c2c442ff345425c8869b1d9d5d3acc0
+# 69588a28ba4347fcb68c87c646fb60ee
+# f661a12fd1cc426182904a4bc75345c8
+msgid "Name: systemvm-vmware-4.3"
+msgstr ""
+
+#: ../../rnotes.rst:123
+#: ../../rnotes.rst:759
+#: ../../rnotes.rst:1304
+#: ../../rnotes.rst:1724
+#: ../../rnotes.rst:2547
+# 4c8ebe8a548a4f9b9ccd79045e484d1f
+# 5564146be1f44426bb7ff011cd79da6b
+# 2bcaf70553fe41b49bfd3d520eb87cf2
+# 69cfec227db440c78ffebe965f718f51
+# 737c7f2c4bc14508a4c7f6ada8848b86
+msgid "Description: systemvm-vmware-4.3"
+msgstr ""
+
+#: ../../rnotes.rst:125
+#: ../../rnotes.rst:761
+#: ../../rnotes.rst:1306
+#: ../../rnotes.rst:1726
+#: ../../rnotes.rst:2549
+# 929b6fcb9fa04616afcefbd762fd270b
+# 45594193b7824f4faf2b49ed811292e1
+# c5214485e9114e2eb71127c7d7de6965
+# 0c755ceff7c547348ff3a27a613ef83a
+# a56695f39bb84f899e7915122a3c430a
+msgid "URL: http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-vmware.ova"
+msgstr ""
+
+#: ../../rnotes.rst:130
+#: ../../rnotes.rst:766
+#: ../../rnotes.rst:1311
+#: ../../rnotes.rst:1732
+#: ../../rnotes.rst:2554
+# fdce1fd6cf214aa1a80d576a2896b896
+# 16b1ece80c5b47d087926ef28030fa24
+# bf8ca53871274fa692c6d6d79c44e724
+# 01a8c28c4a0d4be19d066f6b1ca9bfb4
+# cdb023985a824671b495895401467244
+msgid "Hypervisor: VMware"
+msgstr ""
+
+#: ../../rnotes.rst:132
+#: ../../rnotes.rst:768
+#: ../../rnotes.rst:1313
+#: ../../rnotes.rst:1734
+#: ../../rnotes.rst:2556
+# f5ab7fa232ba4adb9aff39fe88823e75
+# 68828f3174144a2ba64fc023ce8c45f6
+# 84231abe4e084779850b6e0fd3b05ed5
+# e045e6e4e8f5494b8df360e658fdd16e
+# f8413cb707bd478ab0917c42fe20305a
+msgid "Format: OVA"
+msgstr ""
+
+#: ../../rnotes.rst:149
+#: ../../rnotes.rst:671
+#: ../../rnotes.rst:1207
+# 3d8594f701ce4339a128d828a3d45262
+# 5573cc224cad4c6083abb76bb0562de4
+# 37d7d78c63444bd5aff131eb3e13263e
+msgid "Most users of CloudStack manage the installation and upgrades of CloudStack with one of Linux's predominant package systems, RPM or APT. This guide assumes you'll be using RPM and Yum (for Red Hat Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu)."
+msgstr ""
+
+#: ../../rnotes.rst:156
+# 88aa12a47aa945f39be9bca36470030a
+msgid "Create RPM or Debian packages (as appropriate) and a repository from the 4.3 source, or check the Apache CloudStack downloads page at `http://cloudstack.apache.org/downloads.html <http://cloudstack.apache.org/downloads.html>`__ for package repositories supplied by community members. You will need them for step `9 <#upgrade-deb-packages-4.3>`__ or step `12 <#upgrade-rpm-packages-4.3>`__."
+msgstr ""
+
+#: ../../rnotes.rst:163
+#: ../../rnotes.rst:793
+#: ../../rnotes.rst:1219
+# fe1460adc2c44e3d80206f28f58cb501
+# 6010af120d70477ca3ad2427739f816f
+# be1c3c65497244fdaec1d9ffd92245f2
+msgid "Instructions for creating packages from the CloudStack source are in the `Installation Guide <http://cloudstack.apache.org/docs/en-US/index.html>`__."
+msgstr ""
+
+#: ../../rnotes.rst:169
+#: ../../rnotes.rst:799
+#: ../../rnotes.rst:1331
+# 9fb806b610304e06a27290e8b4e45d46
+# a62f49eead134ffaa2c3867d0392d355
+# 76b2f9c139b746f387ab004817e72ade
+msgid "Stop your management server or servers. Run this on all management server hosts:"
+msgstr ""
+
+#: ../../rnotes.rst:178
+#: ../../rnotes.rst:808
+#: ../../rnotes.rst:1340
+# 61ec24c202454102af5231204abf54e8
+# d94754cfaa1845009234f1fd07ad1abe
+# 5fe3320b47d3420e8284aecdc344ae98
+msgid "If you are running a usage server or usage servers, stop those as well:"
+msgstr ""
+
+#: ../../rnotes.rst:187
+#: ../../rnotes.rst:817
+#: ../../rnotes.rst:1349
+# 3dae9ac1b9544013bab74070b4aba392
+# 35aaf48e64de4120920294e0e644043b
+# 41167be41fe5441b9a775b581b54a6ea
+msgid "Make a backup of your MySQL database. If you run into any issues or need to roll back the upgrade, this will assist in debugging or restoring your existing environment. You'll be prompted for your password."
+msgstr ""
+
+#: ../../rnotes.rst:198
+# a832f169886e4d90a4bcc7546e99fb92
+msgid "Perform the following to verify the artifacts:"
+msgstr ""
+
+#: ../../rnotes.rst:202
+# 8fc29aba93244f9c85d92598c8895eec
+msgid "(optional) Install GPG keys if needed:"
+msgstr ""
+
+#: ../../rnotes.rst:210
+# 9c5cb5834dda446888da19f515871371
+msgid "Import the GPG keys stored in the source distribution's KEYS file"
+msgstr ""
+
+#: ../../rnotes.rst:216
+# 5e1c33e0d9b840f7baf9a010ce8ac584
+msgid "Alternatively, download the signing keys, the IDs found in the KEYS file, individually by using a keyserver."
+msgstr ""
+
+#: ../../rnotes.rst:219
+# 4ca3f7ea5fcf43d5b1ff77d4d2ca7344
+msgid "For example:"
+msgstr ""
+
+#: ../../rnotes.rst:227
+# 0d8d050411314507a7666a445ac8ee8c
+msgid "Verify signatures and hash files:"
+msgstr ""
+
+#: ../../rnotes.rst:235
+# b7794f596fe7409f861b2e3ae506bf12
+msgid "Each of these commands should return no output. Any output from them implies that there is a difference between the hash you generated locally and the hash that has been pulled from the server."
+msgstr ""
+
+#: ../../rnotes.rst:242
+# b33428839e5047f587d2980dab1d0400
+msgid "Get the commit hash from the VOTE email."
+msgstr ""
+
+#: ../../rnotes.rst:244
+# 6ca9e5088bcd4ff5b75cafd02e137b5b
+msgid "For example: ``4cd60f3d1683a3445c3248f48ae064fb573db2a1``. The value changes between releases."
+msgstr ""
+
+#: ../../rnotes.rst:249
+# 590a8aafe28348c298754e9256f72562
+msgid "Create two new temporary directories:"
+msgstr ""
+
+#: ../../rnotes.rst:258
+# fca2c85f4dd146a19014af8fb2337d08
+msgid "Check out the 4.3 branch:"
+msgstr ""
+
+#: ../../rnotes.rst:268
+# 497f648b84504e92a92ea26c04fb938c
+msgid "Unpack the release artifact:"
+msgstr ""
+
+#: ../../rnotes.rst:277
+# cfb84a84e1d846868e5e793d17e63295
+msgid "Compare the contents of the release artifact with the contents pulled from the repo:"
+msgstr ""
+
+#: ../../rnotes.rst:284
+# b74361dc65ff43d09fcbccab8fd8f22f
+msgid "Ensure that content is the same."
+msgstr ""
+
+#: ../../rnotes.rst:288
+# de5a514cdf5e45ec9e0c83602693f1a9
+msgid "Verify the Code License Headers:"
+msgstr ""
+
+#: ../../rnotes.rst:295
+# a08623e0592740adbefb044fffe43b80
+msgid "The build fails if any non-compliant files are present that are not specifically excluded from the ASF license header requirement. You can optionally review the target/rat.txt file after the run completes. Passing the build implies that RAT certifies that the files are compliant and this test is passed."
+msgstr ""
+
+#: ../../rnotes.rst:303
+#: ../../rnotes.rst:828
+# c05c67cb91ff4c4fb0830a15517c28e6
+# f879c0c2a45a42dfb0cbae8b0c6c723c
+msgid "(KVM Only) If primary storage of type local storage is in use, the path for this storage needs to be verified to ensure it passes new validation. Check local storage by querying the cloud.storage\\_pool table:"
+msgstr ""
+
+#: ../../rnotes.rst:312
+#: ../../rnotes.rst:837
+# f5faf75092944799abb54b8ff3a93aac
+# 0abfe7d9828549a4874a4d76bd74099b
+msgid "If local storage paths are found to have a trailing forward slash, remove it:"
+msgstr ""
+
+#: ../../rnotes.rst:321
+# 6b58c38ec36b43359f8df7a4e28d0ba8
+msgid "If you are using Ubuntu, follow this procedure to upgrade your packages. If not, skip to step `12 <#upgrade-rpm-packages-4.3>`__."
+msgstr ""
+
+#: ../../rnotes.rst:324
+#: ../../rnotes.rst:851
+#: ../../rnotes.rst:1408
+#: ../../rnotes.rst:1850
+#: ../../rnotes.rst:2680
+# a6b983d16c564e14a40c2219f254d185
+# 8192ffa8b36d4fe39ccf4a48ff19b805
+# cd79a60a33fa4a5099611ad000aa40a8
+# 808e6e5841394a90b82e39738f25e8ea
+# 16a5425eb3264f878d16075d65a84e75
+msgid "**Community Packages:** This section assumes you're using the community supplied packages for CloudStack. If you've created your own packages and APT repository, substitute your own URL for the ones used in these examples."
+msgstr ""
+
+#: ../../rnotes.rst:328
+#: ../../rnotes.rst:855
+#: ../../rnotes.rst:1412
+#: ../../rnotes.rst:1854
+#: ../../rnotes.rst:2684
+# e5511d82d7dd4a2086af894d4f3a66e7
+# f071f4d226434279935f3b2d3bbf0b94
+# b1de12ae7c1d4bcbbfd6751e7905c3fc
+# 5abb5d0722c14a99a381043de09e787c
+# c13e0c45e1ac477f93c1e509f8b7a3ed
+msgid "The first order of business will be to change the sources list for each system with CloudStack packages. This means all management servers, and any hosts that have the KVM agent. (No changes should be necessary for hosts that are running VMware or Xen.)"
+msgstr ""
+
+#: ../../rnotes.rst:333
+#: ../../rnotes.rst:860
+#: ../../rnotes.rst:1417
+#: ../../rnotes.rst:1859
+#: ../../rnotes.rst:2689
+# a958c2917bbf4e76bef951b82eaa948d
+# c6a2774a444d4731920dea30f603dab4
+# 5ba4911d0da74773afb9c2eddc851cd7
+# e319c10bde3c4c3081b19a676e612403
+# 74bc1bcada174e589a3decdfa5139e8e
+msgid "Start by opening ``/etc/apt/sources.list.d/cloudstack.list`` on any systems that have CloudStack packages installed."
+msgstr ""
+
+#: ../../rnotes.rst:336
+#: ../../rnotes.rst:863
+#: ../../rnotes.rst:1420
+#: ../../rnotes.rst:1862
+#: ../../rnotes.rst:2692
+# 52594ffb3e3b49dd973c9b71d574ed06
+# 15c32c5835094010913b0a0640ee2d45
+# b9c9af9596fd4c2b9859e01f5b7d7cb4
+# 5f46c399178e4ac79d7bdee13c360ef0
+# 4e99197def0348688a462fd4f6e4360b
+msgid "This file should have one line, which contains:"
+msgstr ""
+
+#: ../../rnotes.rst:342
+#: ../../rnotes.rst:869
+#: ../../rnotes.rst:1426
+#: ../../rnotes.rst:1868
+#: ../../rnotes.rst:2698
+# 06e5ec0807804d29a708de00c61b5777
+# ba0fc909e0cc4f6da0d20c7bbcf4056a
+# 4e99f6d067da4893997e3948525b964d
+# e8a04410ba684e0885652b5f0d4cf114
+# a1830e7e3f1c4716a2ecebf346b0b746
+msgid "We'll change it to point to the new package repository:"
+msgstr ""
+
+#: ../../rnotes.rst:348
+#: ../../rnotes.rst:561
+#: ../../rnotes.rst:875
+#: ../../rnotes.rst:1093
+#: ../../rnotes.rst:1547
+#: ../../rnotes.rst:1874
+#: ../../rnotes.rst:2819
+# fe91d09f17b048528bb381f857027531
+# d6a1773e0b28473fb2e55fcea1768f9e
+# 0bc0c855315f41ed857d4e617cd628e1
+# 9e8f2d39ef1a4bc9aa61655baf391a87
+# be264602baaa42a29744eed1658e59b3
+# adb92ccbe36d49a1aacce6228a0d89f7
+# b7dccba865e34824851ab5b3c19b64fd
+msgid "If you're using your own package repository, change this line to read as appropriate for your 4.3 repository."
+msgstr ""
+
+#: ../../rnotes.rst:353
+#: ../../rnotes.rst:880
+#: ../../rnotes.rst:1437
+#: ../../rnotes.rst:1879
+#: ../../rnotes.rst:2709
+# af318502921348f6a28ee215a56caa91
+# e907284d5a7a4629980c3d2c27945fe4
+# 8658aafa6489403f9951530d92103573
+# bdada53d85954149ab6b22c802022d21
+# a9e8b1b691c044a78ccc5cc7d1aa88a8
+msgid "Now update your apt package list:"
+msgstr ""
+
+#: ../../rnotes.rst:361
+#: ../../rnotes.rst:888
+#: ../../rnotes.rst:1445
+#: ../../rnotes.rst:1887
+#: ../../rnotes.rst:2717
+# b3e9469c25964af1846bada191e04ec4
+# 3b6338f090944644a9bc88994718d676
+# 84c3a21811cb4055b3f6a878e5e32ba1
+# c4bc202140ed4c2294ba47ef898cc33d
+# bced4ccb43214bc9944417aa960ad820
+msgid "Now that you have the repository configured, it's time to install the ``cloudstack-management`` package. This will pull in any other dependencies you need."
+msgstr ""
+
+#: ../../rnotes.rst:371
+#: ../../rnotes.rst:898
+#: ../../rnotes.rst:1455
+#: ../../rnotes.rst:1897
+# de1a9ec4bd5045c79dbdfc029370bea8
+# e6282c1fac50417387b20ba58a7886d5
+# d71ec2e87e9b48a6bc842c92910f623c
+# 29ab25bcc03343cf8436a1f7d2de0dd1
+msgid "You will need to manually install the ``cloudstack-agent`` package:"
+msgstr ""
+
+#: ../../rnotes.rst:378
+#: ../../rnotes.rst:905
+#: ../../rnotes.rst:1462
+#: ../../rnotes.rst:1904
+#: ../../rnotes.rst:2734
+# 7720a75dd93347c2b3881f7e34fc9ab4
+# 909dfb569c204270b7a4f4a229249de2
+# ebed114157c0496b86ebb471bd0df7fd
+# 53463349bedd4f09bad1425cae191821
+# 10cb1cfc5923438286b42a21e6b707aa
+msgid "During the installation of ``cloudstack-agent``, APT will copy your ``agent.properties``, ``log4j-cloud.xml``, and ``environment.properties`` from ``/etc/cloud/agent`` to ``/etc/cloudstack/agent``."
+msgstr ""
+
+#: ../../rnotes.rst:381
+#: ../../rnotes.rst:910
+#: ../../rnotes.rst:1467
+#: ../../rnotes.rst:1909
+#: ../../rnotes.rst:2739
+# 31c195a6e6aa49b199138992bfdc5c4c
+# 294c1b73507d4a138d0cffa807bc6aa5
+# e15fb33c81924d908ba2e5287be51de6
+# 450c72d1f9394fa18db5038e8bbccfcb
+# 8c9593f4a88d4016880d243cc85121bb
+msgid "When prompted whether you wish to keep your configuration, say Yes."
+msgstr ""
+
+#: ../../rnotes.rst:386
+#: ../../rnotes.rst:586
+#: ../../rnotes.rst:915
+#: ../../rnotes.rst:1118
+#: ../../rnotes.rst:1472
+#: ../../rnotes.rst:1577
+#: ../../rnotes.rst:1914
+#: ../../rnotes.rst:2019
+#: ../../rnotes.rst:2744
+#: ../../rnotes.rst:2849
+# 013b94409f95418e8897098e07a8d8bf
+# c7368db7d4a04ff1bc743c2f6184e685
+# 6c1a1db1129440a093d08072e24a883a
+# edefd647ee6947bfa9544f7ef98c6635
+# e82fc4a9717d40c6aec52f82d1d48c76
+# f99deecf9e7540f385fb4dfe580aeaa4
+# 5c0aa24881e7433da978c0519e7c5c12
+# c30d30b25c2a4524ae83838dffe52c60
+# f78700edcf7242e7866cd95f7f5d5255
+# e21ee87582d24075bfa8c7a8798e2193
+msgid "Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a line that reads:"
+msgstr ""
+
+#: ../../rnotes.rst:394
+#: ../../rnotes.rst:594
+#: ../../rnotes.rst:923
+#: ../../rnotes.rst:1126
+#: ../../rnotes.rst:1480
+#: ../../rnotes.rst:1585
+#: ../../rnotes.rst:1922
+#: ../../rnotes.rst:2027
+#: ../../rnotes.rst:2752
+#: ../../rnotes.rst:2857
+# 700f1c7b1a1049b8806f24a991406dee
+# 31ddbf40c7364e6d8622368dfead1a6c
+# b1c49dadf53e44db985e7def1c40f6f3
+# fb5ed344bc15491d9afbe48f3c54ab11
+# bd8c2be8aba142e39d3f763290b746b2
+# 9be24a50e7014e7ba502e5143445a584
+# 3158944a76d0492795f68eeb63f917e2
+# 246b5d6355294df0a4fc27ebc6e9ba8d
+# 62e1898bf0c2477fa6db149294f84efe
+# e0882954603e4da58c47686f7edb5096
+msgid "If not, add the line."
+msgstr ""
+
+#: ../../rnotes.rst:398
+#: ../../rnotes.rst:598
+#: ../../rnotes.rst:927
+#: ../../rnotes.rst:1130
+#: ../../rnotes.rst:1484
+#: ../../rnotes.rst:1589
+#: ../../rnotes.rst:1926
+#: ../../rnotes.rst:2031
+#: ../../rnotes.rst:2756
+#: ../../rnotes.rst:2861
+# 519de95f4a6f4f4593be8696649527a1
+# 23f0e056534c4ed6a418e70b8c95f99c
+# de193ddaadfc4c8e9dce765f2b72b674
+# 53ed305891e244388ab9a01cd353db41
+# a52346ad05fb49558efcac30a6ef4bab
+# 098daad3fe4b4b8a9442aab380db3c0f
+# ab71fb2b93b14fdfa86405bce6f128d5
+# c4fd879586a54a70a06dc06345db0220
+# 296868aa390e48b9833c5a07ddb80d9f
+# 583276a529844a7f8932e434c87e9c5f
+msgid "Restart the agent:"
+msgstr ""
+
+#: ../../rnotes.rst:408
+#: ../../rnotes.rst:937
+# 328d335035544cd1b6d5c1e32ddd2cd8
+# 631312e403e7449bbfe0ff961a939d20
+msgid "(VMware only) Additional steps are required for each VMware cluster. These steps will not affect running guests in the cloud. These steps are required only for clouds using VMware clusters:"
+msgstr ""
+
+#: ../../rnotes.rst:414
+#: ../../rnotes.rst:943
+# 3fd9107b9e704f9aa78462e82c53f962
+# f7622a76f2344e98ac49eb7b609ad6ec
+msgid "Stop the Management Server:"
+msgstr ""
+
+#: ../../rnotes.rst:422
+#: ../../rnotes.rst:951
+# f8ea8b67844c4d0b9d8d68da74958172
+# 78afdf4037214084a10ece106b4c493c
+msgid "Generate the encrypted equivalent of your vCenter password:"
+msgstr ""
+
+#: ../../rnotes.rst:428
+#: ../../rnotes.rst:957
+# ca82244cd0144fdf8e467c7b20afecaa
+# e4d65748d3144b70af2b8af91965c2b6
+msgid "Store the output from this step, we need to add this in cluster\\_details table and vmware\\_data\\_center tables in place of the plain text password"
+msgstr ""
+
+#: ../../rnotes.rst:434
+#: ../../rnotes.rst:963
+# 52ac28e16f264f0a979beb36d04b6ea8
+# 76c0eac4b9264ae1b3a6c07e0dd3b7ed
+msgid "Find the ID of the row of cluster\\_details table that you have to update:"
+msgstr ""
+
+#: ../../rnotes.rst:447
+#: ../../rnotes.rst:976
+# ab863aa53ec843caab4beb5e2f9c23d7
+# 438c5f0d709a407796e492d3e6a40587
+msgid "Update the plain text password with the encrypted one"
+msgstr ""
+
+#: ../../rnotes.rst:455
+#: ../../rnotes.rst:480
+#: ../../rnotes.rst:984
+#: ../../rnotes.rst:1009
+# 00b91c75cfdb47f2bddb79ad7570dc7e
+# 052499a889174eab91eb38879532eb57
+# d8740e201c9740148a64849ac8cd1a77
+# fa98627cf81343728fc22b61fbb1e82f
+msgid "Confirm that the table is updated:"
+msgstr ""
+
+#: ../../rnotes.rst:463
+#: ../../rnotes.rst:992
+# a3edd50f595c40bd82f3e3ba0acf8b6b
+# 2ea24676dae145bcbb18392065c3ba1a
+msgid "Find the ID of the correct row of vmware\\_data\\_center that you want to update"
+msgstr ""
+
+#: ../../rnotes.rst:472
+#: ../../rnotes.rst:1001
+# 4798580a87cf4186b0d95247bd67707c
+# 300ad8d0623b469ab95ad20e7577a2a2
+msgid "update the plain text password with the encrypted one:"
+msgstr ""
+
+#: ../../rnotes.rst:488
+#: ../../rnotes.rst:1017
+# 74ed75c564e94d359e17dd134a934edf
+# 54cc6717a8d74582b9f2383dfffb8c0b
+msgid "Start the CloudStack Management server"
+msgstr ""
+
+#: ../../rnotes.rst:496
+#: ../../rnotes.rst:1025
+# e5763429fd714c748dc111bd9d7498a4
+# f42087fb226f4fd1912cfcebda96844e
+msgid "(KVM only) Additional steps are required for each KVM host. These steps will not affect running guests in the cloud. These steps are required only for clouds using KVM as hosts and only on the KVM hosts."
+msgstr ""
+
+#: ../../rnotes.rst:503
+#: ../../rnotes.rst:1032
+# a9b1166d4fdc4f7bbaee34ed69d84685
+# 26df2ece28b0403e83734879189c0a28
+msgid "Configure the CloudStack yum repository as detailed above."
+msgstr ""
+
+#: ../../rnotes.rst:507
+#: ../../rnotes.rst:1036
+#: ../../rnotes.rst:2138
+#: ../../rnotes.rst:3053
+# 91fcb4e5d87a4758bb495df7a566eef9
+# d3b457f5c84b4d7fa94e18a2f094eec3
+# 6f6fbd8df62a470daf0529b8cbf7c575
+# 298db92eabbf4892b82b467d5946f9dd
+msgid "Stop the running agent."
+msgstr ""
+
+#: ../../rnotes.rst:515
+#: ../../rnotes.rst:1044
+# 761fcbfc3fb344d680081c493d38f542
+# 530303b4348245678bd1be14a384140e
+msgid "Update the agent software."
+msgstr ""
+
+#: ../../rnotes.rst:523
+#: ../../rnotes.rst:1052
+#: ../../rnotes.rst:2189
+#: ../../rnotes.rst:3111
+# 51aaef13bf80479e95adac061e600381
+# be13ad0cba844fd691c8141e07838472
+# f81edce8c2794070919839b648553619
+# fc468199e0df4362841e9d745cd875e4
+msgid "Start the agent."
+msgstr ""
+
+#: ../../rnotes.rst:531
+# 54e588c53c4a4a55823879f37ea6b7e9
+msgid "If you are using CentOS or RHEL, follow this procedure to upgrade your packages. If not, skip to step `14 <#restart-system-vms-4.3>`__."
+msgstr ""
+
+#: ../../rnotes.rst:534
+#: ../../rnotes.rst:1066
+#: ../../rnotes.rst:1521
+#: ../../rnotes.rst:1963
+#: ../../rnotes.rst:2793
+# ac689aa24a284a2185768cd88ff9c873
+# 09301068b69c43e985ae0e3134e12b3e
+# 70fe9e2a05b5402e9a10a00a46e61cad
+# 20b091f734b74c1386d19886179685e7
+# 4b2d56d79c4d42528cbdf98f3c70bac3
+msgid "**Community Packages:** This section assumes you're using the community supplied packages for CloudStack. If you've created your own packages and yum repository, substitute your own URL for the ones used in these examples."
+msgstr ""
+
+#: ../../rnotes.rst:538
+#: ../../rnotes.rst:1070
+# 4e7a8145ac1949d7909e5ea4abdf5325
+# 3f3368fc99844d03b8ee9b83e6f595c7
+msgid "The first order of business will be to change the yum repository for each system with CloudStack packages. This means all management servers, and any hosts that have the KVM agent."
+msgstr ""
+
+#: ../../rnotes.rst:542
+#: ../../rnotes.rst:1074
+# 313646a070e746c19f661db22c3b0595
+# 27ee7f6888fc4cf290d970b4e226dff7
+msgid "(No changes should be necessary for hosts that are running VMware or Xen.)"
+msgstr ""
+
+#: ../../rnotes.rst:545
+#: ../../rnotes.rst:1077
+#: ../../rnotes.rst:1531
+#: ../../rnotes.rst:1973
+#: ../../rnotes.rst:2803
+# ea83c71a4ec44c0d855b5228e4ae375a
+# 513cb1b4523644ffb91d714743211614
+# 0d4a968ce5da475c9c3ec65194a77d45
+# 2c09bae6e7d8426a9cb7e8e1e027cb77
+# c519b2cfa95d4d19af2c939c49a891ca
+msgid "Start by opening ``/etc/yum.repos.d/cloudstack.repo`` on any systems that have CloudStack packages installed."
+msgstr ""
+
+#: ../../rnotes.rst:548
+#: ../../rnotes.rst:1080
+#: ../../rnotes.rst:1534
+#: ../../rnotes.rst:1976
+#: ../../rnotes.rst:2806
+# 2bfac7c63bc04900acf82a034c5947cb
+# 96d47cf378704b7aa603e9a54ac7cbd2
+# 70431912242f430eaf34fa8177791654
+# 548512344fb04bb9b25b12f48dfb0dc2
+# f88bab91a8b74ec8b864ffc5be1f574d
+msgid "This file should have content similar to the following:"
+msgstr ""
+
+#: ../../rnotes.rst:558
+# bb244ec41ca44d3c9fa015bd5cf87c71
+msgid "If you are using the community provided package repository, change the base url to http://cloudstack.apt-get.eu/rhel/4.3/"
+msgstr ""
+
+#: ../../rnotes.rst:566
+#: ../../rnotes.rst:1098
+# 5ec2b4f2ba7e406eaa7106ed76e5cc27
+# 836f4777f360464fb8c1651f14a4d182
+msgid "Now that you have the repository configured, it's time to install the ``cloudstack-management`` package by upgrading the older ``cloudstack-management`` package."
+msgstr ""
+
+#: ../../rnotes.rst:576
+#: ../../rnotes.rst:1108
+#: ../../rnotes.rst:1562
+#: ../../rnotes.rst:2004
+#: ../../rnotes.rst:2834
+# 60e7d2e7d8ff489784980e8e2123403f
+# 06d70371a9ea4fcf99318f48a2328ba7
+# f3cf77bb966d470fb3f4e8002f9f3285
+# c7a6700f971b43ddaa177f83a72e4c2c
+# 2e5faaf8a299443e8d5fd3898dfe873d
+msgid "For KVM hosts, you will need to upgrade the ``cloud-agent`` package, similarly installing the new version as ``cloudstack-agent``."
+msgstr ""
+
+#: ../../rnotes.rst:608
+#: ../../rnotes.rst:1140
+# 32e28ad2e92d41d0994468f556882e5c
+# 6d17ed0451cc4413a12e072380279737
+msgid "Now it's time to restart the management server"
+msgstr ""
+
+#: ../../rnotes.rst:616
+#: ../../rnotes.rst:1148
+# ae37a02856d74de5b7e9566104f0bbe7
+# 17651c70cd9c47e2a30cc8b2bdd1b243
+msgid "Once you've upgraded the packages on your management servers, you'll need to restart the system VMs. Ensure that the admin port is set to 8096 by using the \"integration.api.port\" global parameter. This port is used by the cloud-sysvmadm script at the end of the upgrade procedure. For information about how to set this parameter, see \"Setting Global Configuration Parameters\" in the Installation Guide. Changing this parameter will require management server restart. Also make sure port 8096 is open in your local host firewall to do this."
+msgstr ""
+
+#: ../../rnotes.rst:625
+#: ../../rnotes.rst:1157
+#: ../../rnotes.rst:1603
+# 5d2b5c4a4596478eabaf1f2d0adde94a
+# b7c4ad22a18a4be2906e119ae2214bfa
+# 4e468a10b85547dc86a9e9651ceddce9
+msgid "There is a script that will do this for you, all you need to do is run the script and supply the IP address for your MySQL instance and your MySQL credentials:"
+msgstr ""
+
+#: ../../rnotes.rst:633
+#: ../../rnotes.rst:1165
+#: ../../rnotes.rst:1611
+# 4c1c9abb463849148162a0efe944f2d1
+# 6f9068ec81f044d290d07272beb3d974
+# 793af338a6664b6ba129266632045bd4
+msgid "You can monitor the log for progress. The process of restarting the system VMs can take an hour or more."
+msgstr ""
+
+#: ../../rnotes.rst:640
+#: ../../rnotes.rst:1172
+#: ../../rnotes.rst:1618
+# 1e8ce2c7d6af4bbe932f49718456417b
+# 7211600043044817bb217c8d55db6337
+# a99ea4e3fcaa4334a470dc2ecac3b0ed
+msgid "The output to ``sysvm.log`` will look something like this:"
+msgstr ""
+
+#: ../../rnotes.rst:653
+#: ../../rnotes.rst:1187
+# f602f2b3f15447aba0f04fba9caec6fe
+# 52598e6b74c64e3ca72fed00f69355f5
+msgid "**For Xen Hosts: Copy vhd-utils:** This step is only for CloudStack installs that are using Xen hosts."
+msgstr ""
+
+#: ../../rnotes.rst:655
+#: ../../rnotes.rst:1189
+#: ../../rnotes.rst:1631
+# b38a22207b6143bf9def98306932020c
+# 2b4d5dfa48c140d0a0e5f74c0688136b
+# bc97f715272e48a5a112bc3c400044f4
+msgid "Copy the file ``vhd-utils`` to ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``."
+msgstr ""
+
+#: ../../rnotes.rst:659
+# 6bc2e068727042f1b0825066b191470b
+msgid "Upgrade from 4.1.x to 4.3"
+msgstr ""
+
+#: ../../rnotes.rst:661
+# cd05670352b2496695cee82731e1ffd2
+msgid "This section will guide you from CloudStack 4.1.x versions to CloudStack 4.3."
+msgstr ""
+
+#: ../../rnotes.rst:682
+# fced6cae9fe646eb918bda5491f6f75e
+msgid "While running the existing 4.1.x system, log in to the UI as root administrator."
+msgstr ""
+
+#: ../../rnotes.rst:786
+# 1d425573a29d4265a26faeb32cdbd6e7
+msgid "Create RPM or Debian packages (as appropriate) and a repository from the 4.2.1 source, or check the Apache CloudStack downloads page at `http://cloudstack.apache.org/downloads.html <http://cloudstack.apache.org/downloads.html>`__ for package repositories supplied by community members. You will need them for step `8 <#upgrade-deb-packages-41to42>`__ or step `11 <#upgrade-rpm-packages-41to42>`__."
+msgstr ""
+
+#: ../../rnotes.rst:846
+# f4c7884a790a478eb3d9776f3f20e60e
+msgid "If you are using Ubuntu, follow this procedure to upgrade your packages. If not, skip to step `11 <#upgrade-rpm-packages-41to42>`__."
+msgstr ""
+
+#: ../../rnotes.rst:1060
+# 4d83b8a9f5c141e99d1236bb9173d405
+msgid "If you are using CentOS or RHEL, follow this procedure to upgrade your packages. If not, skip to step `13 <#restart-system-vms-41to42>`__."
+msgstr ""
+
+#: ../../rnotes.rst:1090
+# 310caf1a8fe84f8aa11b00f4fc748fa3
+msgid "If you are using the community provided package repository, change the base url to http://cloudstack.apt-get.eu/rhel/4.2/"
+msgstr ""
+
+#: ../../rnotes.rst:1193
+# 87865b78f90840bf81c79ad5693e44f1
+msgid "Upgrade from 4.0.x to 4.3"
+msgstr ""
+
+#: ../../rnotes.rst:1195
+# dcc03feb1c6343a481529d8e99584e31
+msgid "This section will guide you from CloudStack 4.0.x versions to CloudStack 4.3."
+msgstr ""
+
+#: ../../rnotes.rst:1199
+# b937d64b11fa482a8ef65369068951d7
+msgid "**Package Structure Changes:** The package structure for CloudStack has changed significantly since the 4.0.x releases. If you've compiled your own packages, you'll notice that the package names and the number of packages has changed. This is *not* a bug. However, this *does* mean that the procedure is not as simple as an ``apt-get upgrade`` or ``yum update``, so please follow this section carefully."
+msgstr ""
+
+#: ../../rnotes.rst:1212
+# 82a38fa66d5f405fb43868a559fd3be7
+msgid "Create RPM or Debian packages (as appropriate) and a repository from the 4.1.0 source, or check the Apache CloudStack downloads page at `http://cloudstack.apache.org/downloads.html <http://cloudstack.apache.org/downloads.html>`__ for package repositories supplied by community members. You will need them for step `9 <#upgrade-deb-packages-40to41>`__ or step `10 <#upgrade-rpm-packages-40to41>`__."
+msgstr ""
+
+#: ../../rnotes.rst:1227
+# b69cf695d3a547d5ae0b4c58c7fb38b0
+msgid "While running the existing 4.0.0 system, log in to the UI as root administrator."
+msgstr ""
+
+#: ../../rnotes.rst:1360
+# decdfc8d25a44aec8b0d7248429e30ee
+msgid "Whether you're upgrading a Red Hat/CentOS based system or Ubuntu based system, you're going to need to stop the CloudStack management server before proceeding."
+msgstr ""
+
+#: ../../rnotes.rst:1370
+# f2c485a660324ae4b21cda5e01d76f60
+msgid "If you have made changes to ``/etc/cloud/management/components.xml``, you'll need to carry these over manually to the new file, ``/etc/cloudstack/management/componentContext.xml``. This is not done automatically. (If you're unsure, we recommend making a backup of the original ``components.xml`` to be on the safe side."
+msgstr ""
+
+#: ../../rnotes.rst:1378
+#: ../../rnotes.rst:2078
+# a2d67a43640845bb9f9b4944a7771ddf
+# 3f90e26e9881440ca7016620bfe8826a
+msgid "After upgrading to 4.3, API clients are expected to send plain text passwords for login and user creation, instead of MD5 hash. Incase, api client changes are not acceptable, following changes are to be made for backward compatibility:"
+msgstr ""
+
+#: ../../rnotes.rst:1383
+# cfa3495575d648dba32738e703dfcb9a
+msgid "Modify componentsContext.xml, and make PlainTextUserAuthenticator as the default authenticator (1st entry in the userAuthenticators adapter list is default)"
+msgstr ""
+
+#: ../../rnotes.rst:1400
+# c3bc0360bcc44217a96b9982cb901933
+msgid "PlainTextUserAuthenticator works the same way MD5UserAuthenticator worked prior to 4.3."
+msgstr ""
+
+#: ../../rnotes.rst:1405
+# d5f1eac6893c4ffc8ac4742182e5eb3c
+msgid "If you are using Ubuntu, follow this procedure to upgrade your packages. If not, skip to step `10 <#upgrade-rpm-packages-40to41>`__."
+msgstr ""
+
+#: ../../rnotes.rst:1432
+# 5f17c031f249452a860b528ea147b261
+msgid "If you're using your own package repository, change this line to read as appropriate for your 4.1.0 repository."
+msgstr ""
+
+#: ../../rnotes.rst:1494
+#: ../../rnotes.rst:1936
+#: ../../rnotes.rst:2766
+# df2e794712da48a3b74b1e8ab3132d7c
+# 3e6d6d7a7d674b0590ecd5840b8f1de4
+# b3d517b1d8cd4d2d912c2522b608b33d
+msgid "During the upgrade, ``log4j-cloud.xml`` was simply copied over, so the logs will continue to be added to ``/var/log/cloud/agent/agent.log``. There's nothing *wrong* with this, but if you prefer to be consistent, you can change this by copying over the sample configuration file:"
+msgstr ""
+
+#: ../../rnotes.rst:1508
+#: ../../rnotes.rst:1950
+#: ../../rnotes.rst:2780
+# 1aa1fe091d6b44b6a502e4fa15fa5844
+# 6ac1e77aad1a4198b0461498be05c91c
+# 149a0aac879c4ff8999e9bbfcc9ce20e
+msgid "Once the agent is running, you can uninstall the old cloud-\\* packages from your system:"
+msgstr ""
+
+#: ../../rnotes.rst:1517
+# 7a0c9bd9683444ac90d759ed23c5e473
+msgid "If you are using CentOS or RHEL, follow this procedure to upgrade your packages. If not, skip to step `11 <#restart-system-vms-40to41>`__."
+msgstr ""
+
+#: ../../rnotes.rst:1525
+#: ../../rnotes.rst:1967
+#: ../../rnotes.rst:2797
+# 8f6623ff2c0c4f5386f112569ec959c1
+# 07168fbf9db442d1b8711818e63325d8
+# 9d0279dcf38241d49908aa63cae11f2d
+msgid "The first order of business will be to change the yum repository for each system with CloudStack packages. This means all management servers, and any hosts that have the KVM agent. (No changes should be necessary for hosts that are running VMware or Xen.)"
+msgstr ""
+
+#: ../../rnotes.rst:1544
+# 515ed73456d24d2789fbccf5ec679d68
+msgid "If you are using the community provided package repository, change the baseurl to http://cloudstack.apt-get.eu/rhel/4.1/"
+msgstr ""
+
+#: ../../rnotes.rst:1552
+#: ../../rnotes.rst:1994
+#: ../../rnotes.rst:2824
+# 5bfa9979f3a241219f9294919127e4a7
+# 641797aa883846e78664b464498cf0d7
+# f72fc5000d104f4f9d49c6217613f418
+msgid "Now that you have the repository configured, it's time to install the ``cloudstack-management`` package by upgrading the older ``cloud-client`` package."
+msgstr ""
+
+#: ../../rnotes.rst:1570
+#: ../../rnotes.rst:2012
+#: ../../rnotes.rst:2842
+# fd5be6d36cc14d59b7702c0ea4c6d4cb
+# 29d70a286063432d888332981c528fc8
+# 876b961c8f9d414daa75266fa0eceeae
+msgid "During the installation of ``cloudstack-agent``, the RPM will copy your ``agent.properties``, ``log4j-cloud.xml``, and ``environment.properties`` from ``/etc/cloud/agent`` to ``/etc/cloudstack/agent``."
+msgstr ""
+
+#: ../../rnotes.rst:1599
+# 55b9c7a21be24615986ce044cf855196
+msgid "Once you've upgraded the packages on your management servers, you'll need to restart the system VMs. Make sure port 8096 is open in your local host firewall to do this."
+msgstr ""
+
+#: ../../rnotes.rst:1629
+# 41d50bc3ff714f16b97527c2044e9291
+msgid "*For Xen Hosts: Copy vhd-utils:** This step is only for CloudStack installs that are using Xen hosts."
+msgstr ""
+
+#: ../../rnotes.rst:1635
+# 19db5d49a0c541a19aaba789a6ac0bb4
+msgid "Upgrade from 3.0.x to 4.3"
+msgstr ""
+
+#: ../../rnotes.rst:1637
+# f1069c86fe0b488e8833596e29166bc2
+msgid "This section will guide you from Citrix CloudStack 3.0.x to Apache CloudStack 4.3. Sections that are hypervisor-specific will be called out with a note."
+msgstr ""
+
+#: ../../rnotes.rst:1645
+# 07fa0747696746e89054a00dfefc0ee8
+msgid "While running the existing 3.0.x system, log in to the UI as root administrator."
+msgstr ""
+
+#: ../../rnotes.rst:1677
+#: ../../rnotes.rst:1703
+#: ../../rnotes.rst:1729
+# b935ab26de7c48c8b31fe129107e4dc9
+# fb1f274e485146dcbb4711cdbf24e0af
+# 1202a4283afc4b568d2af0d3fa8759ef
+msgid "Zone: Choose the zone where this hypervisor is used used"
+msgstr ""
+
+#: ../../rnotes.rst:1751
+# 0c6257995da4416a8fb34f633e5623bb
+msgid "Watch the screen to be sure that the template downloads successfully and enters the READY state. Do not proceed until this is successful."
+msgstr ""
+
+#: ../../rnotes.rst:1757
+#: ../../rnotes.rst:2587
+# 9636c195c8884db58b8daeb21f226604
+# 0f30cf93febd40afb5045d7d1c1c0e71
+msgid "(KVM on RHEL 6.0/6.1 only) If your existing CloudStack deployment includes one or more clusters of KVM hosts running RHEL 6.0 or RHEL 6.1, perform the following:"
+msgstr ""
+
+#: ../../rnotes.rst:1763
+#: ../../rnotes.rst:2593
+# 9aea9022e50d4058b2daef62655b4cae
+# 5d5aceb1eb87437491f476aadb526a3f
+msgid "Ensure that you upgrade the operating system version on those hosts before upgrading CloudStack"
+msgstr ""
+
+#: ../../rnotes.rst:1766
+#: ../../rnotes.rst:2596
+# a1780e7a08bd417e9fc82f515181b464
+# 9115728a006e40acac5a3878feaaa87f
+msgid "To do that, change the yum repository for each system with CloudStack packages, that implies that all the Management Servers and any hosts that have the KVM agent."
+msgstr ""
+
+#: ../../rnotes.rst:1772
+#: ../../rnotes.rst:2602
+# 507ef992b28f4439b57a0d6cb5a362a6
+# 3fc9066c3e1c421dbc2d25b8115c558d
+msgid "Open ``/etc/yum.repos.d/cloudstack.repo`` on any systems that have CloudStack packages installed."
+msgstr ""
+
+#: ../../rnotes.rst:1777
+#: ../../rnotes.rst:2607
+# 195a497b8a0a4ed98e65b5ad132ea523
+# 735cce9dcf334ce7a4e084171554bb7e
+msgid "Edit as follows:"
+msgstr ""
+
+#: ../../rnotes.rst:1792
+#: ../../rnotes.rst:2622
+# 643ae9711e784a95b11fe23e8f3bab60
+# 78a133fee9ae49499025cae7d85b8e91
+msgid "If you are using the community provided package repository, change the baseurl to http:// cloudstack.apt-get.eu/rhel/4.2/"
+msgstr ""
+
+#: ../../rnotes.rst:1795
+#: ../../rnotes.rst:2625
+# daba49b2374c43029a8ebf5c33c1d11a
+# 97fbb9d0ad194f5487c0b3177535f2cc
+msgid "If you are using your own package repository, change this line to read as appropriate for your 4.2.0 repository."
+msgstr ""
+
+#: ../../rnotes.rst:1800
+#: ../../rnotes.rst:2630
+# 748793b598834ac184e4bcb1c768233b
+# cb06d38747e04dbaa8e6a83ba343d50e
+msgid "Now that you have the repository configured, upgrade the host operating system from RHEL 6.0 to 6.3:"
+msgstr ""
+
+#: ../../rnotes.rst:1809
+#: ../../rnotes.rst:2639
+# 29c161c76fed483c872a009d255ac138
+# ff6b709a9dd64c64873f8cd8ef7ab770
+msgid "Stop all Usage Servers if running. Run this on all Usage Server hosts."
+msgstr ""
+
+#: ../../rnotes.rst:1818
+#: ../../rnotes.rst:2648
+# 79db674b90bc41aead755812aa5039c0
+# db5339d420e24d98a980fd13f28d8406
+msgid "Stop the Management Servers. Run this on all Management Server hosts."
+msgstr ""
+
+#: ../../rnotes.rst:1826
+#: ../../rnotes.rst:2656
+# bda05cf21e784a1cbc68f3bbef5bcf32
+# d35c3cd591f547888c10e4a335ab6d70
+msgid "On the MySQL master, take a backup of the MySQL databases. We recommend performing this step even in test upgrades. If there is an issue, this will assist with debugging."
+msgstr ""
+
+#: ../../rnotes.rst:1830
+#: ../../rnotes.rst:2660
+# 8e66828458b3471cb74246724863bdf9
+# 58c3902fdb1d4fae99f90cc451ff89c3
+msgid "In the following commands, it is assumed that you have set the root password on the database, which is a CloudStack recommended best practice. Substitute your own MySQL root password."
+msgstr ""
+
+#: ../../rnotes.rst:1841
+#: ../../rnotes.rst:2671
+# d44cad1eb8984acb9208854228e2a846
+# 18fd82555bdc4e5788c7c0d0436a7c9a
+msgid "Either build RPM/DEB packages as detailed in the Installation Guide, or use one of the community provided yum/apt repositories to gain access to the CloudStack binaries."
+msgstr ""
+
+#: ../../rnotes.rst:1847
+# f921fbc7667149a5a087a95fa26e9c1a
+msgid "If you are using Ubuntu, follow this procedure to upgrade your packages. If not, skip to step `8 <#upgrade-rpm-packages-302>`__."
+msgstr ""
+
+#: ../../rnotes.rst:1959
+# 76b5ee76c1f942b79bc51a4c4e3f6a49
+msgid "If you are using CentOS or RHEL, follow this procedure to upgrade your packages. If not, skip to step `9 <#correct-components-xml-302>`__."
+msgstr ""
+
+#: ../../rnotes.rst:1986
+#: ../../rnotes.rst:2816
+# 38fba8ece8fd4ad584f423e11488adc8
+# 0f2c08e6b61a46978a84509dff72ba7e
+msgid "If you are using the community provided package repository, change the baseurl to http://cloudstack.apt-get.eu/rhel/4.2/"
+msgstr ""
+
+#: ../../rnotes.rst:1989
+#: ../../rnotes.rst:2704
+# 3f607a6dcca84c09ae958564227b8a8a
+# 4876bde4e7ae4591ae6196a3341a8e26
+msgid "If you're using your own package repository, change this line to read as appropriate for your 4.2.0 repository."
+msgstr ""
+
+#: ../../rnotes.rst:2041
+# 3a925891334944b098b5d9075953d97f
+msgid "If you have made changes to your copy of ``/etc/cloud/management/components.xml`` the changes will be preserved in the upgrade. However, you need to do the following steps to place these changes in a new version of the file which is compatible with version 4.2.0."
+msgstr ""
+
+#: ../../rnotes.rst:2049
+# e8cff9d1c7e9444f9d63bcc404493f10
+msgid "Make a backup copy of ``/etc/cloud/management/components.xml``. For example:"
+msgstr ""
+
+#: ../../rnotes.rst:2058
+#: ../../rnotes.rst:2895
+# 8dffce70c30e4aa1b6f60d0738b4fc47
+# 3ed3e63d34724c40862cf7a7dda28c08
+msgid "Copy ``/etc/cloud/management/components.xml.rpmnew`` to create a new ``/etc/cloud/management/components.xml``:"
+msgstr ""
+
+#: ../../rnotes.rst:2067
+# 818ffe1a86194b00a953a20a7660f1ee
+msgid "Merge your changes from the backup file into the new ``components.xml``."
+msgstr ""
+
+#: ../../rnotes.rst:2074
+# 5136061e008944349c17c0a4812f59e0
+msgid "If you have more than one management server node, repeat the upgrade steps on each node."
+msgstr ""
+
+#: ../../rnotes.rst:2083
+#: ../../rnotes.rst:2918
+# 62b7e9bfa03b4cdf8bf6f606369e16a4
+# 540f75422d9346028fb00d354ad199f8
+msgid "Modify componentContext.xml, and make PlainTextUserAuthenticator as the default authenticator (1st entry in the userAuthenticators adapter list is default)"
+msgstr ""
+
+#: ../../rnotes.rst:2100
+# 4f45fbfb75af42e78c4433516c861913
+msgid "PlainTextUserAuthenticator works the same way MD5UserAuthenticator worked prior to 4.3"
+msgstr ""
+
+#: ../../rnotes.rst:2105
+#: ../../rnotes.rst:3017
+# f14640101f524df8b61c04c5802a0f90
+# 5b07020940544308aca9e8ead134c5de
+msgid "Start the first Management Server. Do not start any other Management Server nodes yet."
+msgstr ""
+
+#: ../../rnotes.rst:2112
+# 3130f813f1794a6688ab5f84a05c2eae
+msgid "Wait until the databases are upgraded. Ensure that the database upgrade is complete. After confirmation, start the other Management Servers one at a time by running the same command on each node."
+msgstr ""
+
+#: ../../rnotes.rst:2116
+# e6be4a6abd82409daa72e51bd5505d3b
+msgid "Failing to restart the Management Server indicates a problem in the upgrade. Having the Management Server restarted without any issues indicates that the upgrade is successfully completed."
+msgstr ""
+
+#: ../../rnotes.rst:2120
+#: ../../rnotes.rst:3031
+# b700cadf10414664ad30403b1d734a27
+# 0d68ecc612954ca98e26cd764e2c338b
+msgid "Start all Usage Servers (if they were running on your previous version). Perform this on each Usage Server host."
+msgstr ""
+
+#: ../../rnotes.rst:2123
+# 962f098bf0944d4e9506d9f8da308f11
+msgid "``# service cloudstack-usage start``"
+msgstr ""
+
+#: ../../rnotes.rst:2127
+# eba4690f9619425baa4d7585ce906dbf
+msgid "Additional steps are required for each KVM host. These steps will not affect running guests in the cloud. These steps are required only for clouds using KVM as hosts and only on the KVM hosts."
+msgstr ""
+
+#: ../../rnotes.rst:2133
+# 88374faf9f7242f6800c1497e39974d3
+msgid "Configure a yum or apt repository containing the CloudStack packages as outlined in the Installation Guide."
+msgstr ""
+
+#: ../../rnotes.rst:2140
+# 95e544424f9c4f2e9c0fe114340d1aca
+msgid "``# service cloud-agent stop``"
+msgstr ""
+
+#: ../../rnotes.rst:2144
+# 1532763bd0b844ef99f8b0a414832b62
+msgid "Update the agent software with one of the following command sets as appropriate for your environment."
+msgstr ""
+
+#: ../../rnotes.rst:2147
+# ef4b3ed3bffa49e8b3239246f44a472f
+msgid "``# yum update cloud-*``"
+msgstr ""
+
+#: ../../rnotes.rst:2149
+# 8827d2ee4e4c4a5691a358bbe2d44487
+msgid "``# apt-get update``"
+msgstr ""
+
+#: ../../rnotes.rst:2151
+# 4b3a2d9d972c4a4fbf3e3ac52b909d96
+msgid "``# apt-get upgrade cloud-*``"
+msgstr ""
+
+#: ../../rnotes.rst:2155
+# 2fc0c723022d4ec18381a57e629decbe
+msgid "Edit ``/etc/cloudstack/agent/agent.properties`` to change the resource parameter from \"com.cloud.agent.resource.computing.LibvirtComputingResource\" to \"com.cloud.hypervisor.kvm.resource.LibvirtComputingResource\"."
+msgstr ""
+
+#: ../../rnotes.rst:2162
+#: ../../rnotes.rst:3084
+# ecc4df90301c40bdba7ec9c7489bbf45
+# 086e6aa91006413ab8d5a95e39199f4d
+msgid "Upgrade all the existing bridge names to new bridge names by running this script:"
+msgstr ""
+
+#: ../../rnotes.rst:2171
+#: ../../rnotes.rst:3093
+# e9e301e2d3dc463494b6b6bad654fc8d
+# cf012cbefe924ffaa2dcd6e80eebeba9
+msgid "Install a libvirt hook with the following commands:"
+msgstr ""
+
+#: ../../rnotes.rst:2181
+#: ../../rnotes.rst:3103
+# 782564b3f86d43e8990c24382940cddd
+# faeab88588a949ba948729ad64112abf
+msgid "Restart libvirtd."
+msgstr ""
+
+#: ../../rnotes.rst:2197
+#: ../../rnotes.rst:3119
+# 8b96e3f8824d453691b596afcf04c1f1
+# cd1171e11a1b4a8783ff18d68e9150b4
+msgid "When the Management Server is up and running, log in to the CloudStack UI and restart the virtual router for proper functioning of all the features."
+msgstr ""
+
+#: ../../rnotes.rst:2203
+# 98cb545fbff346118931eaaa14fd6a4d
+msgid "Log in to the CloudStack UI as administrator, and check the status of the hosts. All hosts should come to Up state (except those that you know to be offline). You may need to wait 20 or 30 minutes, depending on the number of hosts."
+msgstr ""
+
+#: ../../rnotes.rst:2208
+# ea845784382c45babdbe93fc92a064cb
+msgid "Troubleshooting: If login fails, clear your browser cache and reload the page."
+msgstr ""
+
+#: ../../rnotes.rst:2210
+# a64cb15160f849f9aa8b559ddf1bd7ef
+msgid "Do not proceed to the next step until the hosts show in Up state."
+msgstr ""
+
+#: ../../rnotes.rst:2214
+# adb1c4abcc30453ebcbbca49a1e1b66b
+msgid "If you are upgrading from 3.0.x, perform the following:"
+msgstr ""
+
+#: ../../rnotes.rst:2218
+# e7b0f35d0e1c451f830784f6ae6c0cc7
+msgid "Ensure that the admin port is set to 8096 by using the \"integration.api.port\" global parameter."
+msgstr ""
+
+#: ../../rnotes.rst:2221
+# 408081aa0c764b198f931f4854ab35c0
+msgid "This port is used by the cloud-sysvmadm script at the end of the upgrade procedure. For information about how to set this parameter, see \"Setting Global Configuration Parameters\" in the Installation Guide."
+msgstr ""
+
+#: ../../rnotes.rst:2228
+# 25c5ff1ef6b9441097aa6b059f802f87
+msgid "Restart the Management Server."
+msgstr ""
+
+#: ../../rnotes.rst:2230
+# 1835094467c94d71a7a9aa3ddbffb17c
+msgid "If you don't want the admin port to remain open, you can set it to null after the upgrade is done and restart the management server."
+msgstr ""
+
+#: ../../rnotes.rst:2234
+# 799314b8a15a41b589f078b7daf5dc8c
+msgid "Run the ``cloudstack-sysvmadm`` script to stop, then start, all Secondary Storage VMs, Console Proxy VMs, and virtual routers. Run the script once on each management server. Substitute your own IP address of the MySQL instance, the MySQL user to connect as, and the password to use for that user. In addition to those parameters, provide the ``-c`` and ``-r`` arguments. For example:"
+msgstr ""
+
+#: ../../rnotes.rst:2241
+# 7a3141a8401a42a4872b988c04647e50
+msgid "``# nohup cloudstack-sysvmadm -d 192.168.1.5 -u cloud -p password -c -r > sysvm.log 2>&1 &``"
+msgstr ""
+
+#: ../../rnotes.rst:2243
+# 9807ea9a9d344fa0b0f21a1fce18d952
+msgid "``# tail -f sysvm.log``"
+msgstr ""
+
+#: ../../rnotes.rst:2245
+#: ../../rnotes.rst:3150
+# 34044aff323d44e69fdd811e5a344cf8
+# 292a8d8e24e74cddb150524a71d44997
+msgid "This might take up to an hour or more to run, depending on the number of accounts in the system."
+msgstr ""
+
+#: ../../rnotes.rst:2250
+# 04316862c59449639b26eb55d2c6c2fc
+msgid "If needed, upgrade all Citrix XenServer hypervisor hosts in your cloud to a version supported by CloudStack 4.3. The supported versions are XenServer 5.6 SP2 and 6.0.2. Instructions for upgrade can be found in the CloudStack 4.3 Installation Guide under \"Upgrading XenServer Versions.\""
+msgstr ""
+
+#: ../../rnotes.rst:2258
+# 38e445189b2c4853996d4b3f592a9693
+msgid "Now apply the XenServer hotfix XS602E003 (and any other needed hotfixes) to XenServer v6.0.2 hypervisor hosts."
+msgstr ""
+
+#: ../../rnotes.rst:2263
+#: ../../rnotes.rst:3236
+# 69583363c53344c9a5b461c1077a571c
+# 097ee691746942e0800bfc1cb07a7983
+msgid "Disconnect the XenServer cluster from CloudStack."
+msgstr ""
+
+#: ../../rnotes.rst:2265
+#: ../../rnotes.rst:3238
+# 767c1a5a8d144ba09defeffef7faeda6
+# fc75a38ab89842c0b4ac387dd92520b6
+msgid "In the left navigation bar of the CloudStack UI, select Infrastructure. Under Clusters, click View All. Select the XenServer cluster and click Actions - Unmanage."
+msgstr ""
+
+#: ../../rnotes.rst:2269
+#: ../../rnotes.rst:3242
+# 06d83535407e41f3be6839d7649e8966
+# 678a50801a10408b98fe76ae32cf8b4b
+msgid "This may fail if there are hosts not in one of the states Up, Down, Disconnected, or Alert. You may need to fix that before unmanaging this cluster."
+msgstr ""
+
+#: ../../rnotes.rst:2273
+#: ../../rnotes.rst:3246
+# 64997a1d38bb46c58c5365e1309412e7
+# b0be1ec3117c4e04825eb6d77a336554
+msgid "Wait until the status of the cluster has reached Unmanaged. Use the CloudStack UI to check on the status. When the cluster is in the unmanaged state, there is no connection to the hosts in the cluster."
+msgstr ""
+
+#: ../../rnotes.rst:2280
+#: ../../rnotes.rst:3253
+# 4832dc8f53df42cbb8aadca835cf4b04
+# 3200e9a4df5a4b66a0cd9031c101286e
+msgid "To clean up the VLAN, log in to one XenServer host and run:"
+msgstr ""
+
+#: ../../rnotes.rst:2282
+# 76e8c2612409448592919b545f0f0309
+msgid "``/opt/xensource/bin/cloud-clean-vlan.sh``"
+msgstr ""
+
+#: ../../rnotes.rst:2286
+# d99a958c8c534070bd10c4efacf38fd9
+msgid "Now prepare the upgrade by running the following on one XenServer host:"
+msgstr ""
+
+#: ../../rnotes.rst:2289
+# d38d1cef21254e62849dffb3bfb47867
+msgid "``/opt/xensource/bin/cloud-prepare-upgrade.sh``"
+msgstr ""
+
+#: ../../rnotes.rst:2291
+# 517e10dd9f56496cae62e554097f8cb6
+msgid "If you see a message like \"can't eject CD\", log in to the VM and unmount the CD, then run this script again."
+msgstr ""
+
+#: ../../rnotes.rst:2296
+# 1dbd633d13a444ca8b8afb25a559294a
+msgid "Upload the hotfix to the XenServer hosts. Always start with the Xen pool master, then the slaves. Using your favorite file copy utility (e.g. WinSCP), copy the hotfixes to the host. Place them in a temporary folder such as /tmp."
+msgstr ""
+
+#: ../../rnotes.rst:2301
+#: ../../rnotes.rst:3278
+# f754e93a062b45bb9fb2cca2c83db68a
+# 6ca0af40b8ed47a6a54b3d5da7418472
+msgid "On the Xen pool master, upload the hotfix with this command:"
+msgstr ""
+
+#: ../../rnotes.rst:2303
+# e3db416d75c14207b9cabf916d47957d
+msgid "``xe patch-upload file-name=XS602E003.xsupdate``"
+msgstr ""
+
+#: ../../rnotes.rst:2305
+#: ../../rnotes.rst:3284
+# b63d979455244643bb200351d2243333
+# a7ddaa8b75f84373babe61c17194cc6f
+msgid "Make a note of the output from this command, which is a UUID for the hotfix file. You'll need it in another step later."
+msgstr ""
+
+#: ../../rnotes.rst:2308
+#: ../../rnotes.rst:3287
+# f5f4b3681fee4ce0a5989f592c27f321
+# 4c0b4359005b4939b87bdf98f56ddfaf
+msgid "(Optional) If you are applying other hotfixes as well, you can repeat the commands in this section with the appropriate hotfix number. For example, XS602E004.xsupdate."
+msgstr ""
+
+#: ../../rnotes.rst:2312
+#: ../../rnotes.rst:3291
+# b9ec3718777d426d9db60baf9343700f
+# ffc6b344024e46b5865e67a6281f6822
+msgid "Manually live migrate all VMs on this host to another host. First, get a list of the VMs on this host:"
+msgstr ""
+
+#: ../../rnotes.rst:2315
+# 331d0088f2dc4f3aabf28db1387b68b9
+msgid "``# xe vm-list``"
+msgstr ""
+
+#: ../../rnotes.rst:2317
+#: ../../rnotes.rst:3298
+# bbe943847b1347e58edf0eab4a1d9d79
+# 162db05d17d2431d8468e31154318a22
+msgid "Then use this command to migrate each VM. Replace the example host name and VM name with your own:"
+msgstr ""
+
+#: ../../rnotes.rst:2320
+# d261a0ceae664341b94f5a2be6b9a1a0
+msgid "``# xe vm-migrate live=true host=host-name`` vm=\\ *``VM-name``*"
+msgstr ""
+
+#: ../../rnotes.rst:2322
+#: ../../rnotes.rst:3305
+# 5fbea663a35a4ec28956f372a83490e0
+# e7f75116ea124d079497ff44c73d5328
+msgid "**Troubleshooting:** If you see a message like \"You attempted an operation on a VM which requires PV drivers to be installed but the drivers were not detected,\" run: ``/opt/xensource/bin/make_migratable.sh b6cf79c8-02ee-050b-922f-49583d9f1a14``."
+msgstr ""
+
+#: ../../rnotes.rst:2326
+#: ../../rnotes.rst:3309
+# 0cc26f65fa1c45bfa75fe01f25a366c4
+# 5154615b30294fe28801002bae9295dc
+msgid "Apply the hotfix. First, get the UUID of this host:"
+msgstr ""
+
+#: ../../rnotes.rst:2332
+#: ../../rnotes.rst:3313
+# ec6c8fc14acc44939ce7fb3602c28bfa
+# 4139ce0f7c2344f19a5ea41635ea5d93
+msgid "Then use the following command to apply the hotfix. Replace the example host UUID with the current host ID, and replace the hotfix UUID with the output from the patch-upload command you ran on this machine earlier. You can also get the hotfix UUID by running xe patch-list."
+msgstr ""
+
+#: ../../rnotes.rst:2344
+#: ../../rnotes.rst:3323
+# 3568f9bafc8d4d8ab736796446df9797
+# fc8405849a8842a596c978e732b51cd7
+msgid "Copy the following files from the CloudStack Management Server to the host."
+msgstr ""
+
+#: ../../rnotes.rst:2349
+#: ../../rnotes.rst:3327
+# 43ca4b954df446c3848428042f956e5f
+# f71543bdc41c4196ab1e6d54f072f671
+msgid "Copy from here..."
+msgstr ""
+
+#: ../../rnotes.rst:2349
+#: ../../rnotes.rst:3327
+# 033a8945e6a64e9f87e885bfd3425e08
+# 5ebbadd0ed1c49c3b330fbe518b381e4
+msgid "...to here"
+msgstr ""
+
+#: ../../rnotes.rst:2351
+# 7d904ffbc0d9419fb938d82ba8615913
+msgid "/usr/lib64/cloud/common /scripts/vm/hypervisor/ xenserver/xenserver60/N FSSR.py"
+msgstr ""
+
+#: ../../rnotes.rst:2351
+# 1fa8227e1e834e688c46517f5ed648f7
+msgid "/opt/xensource/sm/NFSSR.py"
+msgstr ""
+
+#: ../../rnotes.rst:2356
+# 8b00a47eb29f4658b97ce82f6ef6b42c
+msgid "/usr/lib64/cloud/common /scripts/vm/hypervisor/ xenserver/setupxenserve r.sh"
+msgstr ""
+
+#: ../../rnotes.rst:2356
+# a304f18ed3fb4841829ce7d70a770e63
+msgid "/opt/xensource/bin/setupxenserver.sh"
+msgstr ""
+
+#: ../../rnotes.rst:2361
+# 7e8fdbf45336439f930a3ac144ca6cc3
+msgid "/usr/lib64/cloud/common /scripts/vm/hypervisor/ xenserver/make\\_migrata ble.sh"
+msgstr ""
+
+#: ../../rnotes.rst:2361
+# 1860fb18826648f1bf66769b659e1fdc
+msgid "/opt/xensource/bin/make\\_migratable.sh"
+msgstr ""
+
+#: ../../rnotes.rst:2370
+#: ../../rnotes.rst:3347
+# a3173d96b6f54aefbdb48752db9828ae
+# 9f01e46081614585a340d3eaaa18daf6
+msgid "(Only for hotfixes XS602E005 and XS602E007) You need to apply a new Cloud Support Pack."
+msgstr ""
+
+#: ../../rnotes.rst:2375
+#: ../../rnotes.rst:3352
+# 7993d80e1552436eb3aae46eb696927e
+# 265e07a4a0ea4b1c8dc01f70233bd936
+msgid "Download the CSP software onto the XenServer host from one of the following links:"
+msgstr ""
+
+#: ../../rnotes.rst:2378
+#: ../../rnotes.rst:3355
+# 8bf41b466c9c4f57b54840fd3ae80e77
+# 17b702c3fc5e40608ce8c6ec4ac6f975
+msgid "For hotfix XS602E005: `http://coltrane.eng.hq.xensource.com/release/XenServer-6.x/XS-6.0.2/hotfixes/XS602E005/56710/xe-phase-2/xenserver-cloud-supp.tgz <http://coltrane.eng.hq.xensource.com/release/XenServer-6.x/XS-6.0.2/hotfixes/XS602E005/56710/xe-phase-2/xenserver-cloud-supp.tgz>`__"
+msgstr ""
+
+#: ../../rnotes.rst:2381
+#: ../../rnotes.rst:3358
+# 6055011a1e474ae5a461738f114fd422
+# 9411b91bb9e44792bf8bb84138bdd2a6
+msgid "For hotfix XS602E007: `http://coltrane.eng.hq.xensource.com/release/XenServer-6.x/XS-6.0.2/hotfixes/XS602E007/57824/xe-phase-2/xenserver-cloud-supp.tgz <http://coltrane.eng.hq.xensource.com/release/XenServer-6.x/XS-6.0.2/hotfixes/XS602E007/57824/xe-phase-2/xenserver-cloud-supp.tgz>`__"
+msgstr ""
+
+#: ../../rnotes.rst:2386
+#: ../../rnotes.rst:3363
+# 0fadc25cecb44b32ad197b10f2eca0d8
+# cf407c2830ac47f492d64717d3501356
+msgid "Extract the file:"
+msgstr ""
+
+#: ../../rnotes.rst:2394
+#: ../../rnotes.rst:3369
+# 58c54753c0214293a8661dda5b2f0cba
+# 959bb01c0f3545008d2d84e4aa00a854
+msgid "Run the following script:"
+msgstr ""
+
+#: ../../rnotes.rst:2402
+#: ../../rnotes.rst:3375
+# 38f4aeff350a4fb4bd8d37e140dc694c
+# 9ea6d227be6742468d0ab1a68cc3f00a
+msgid "If the XenServer host is part of a zone that uses basic networking, disable Open vSwitch (OVS):"
+msgstr ""
+
+#: ../../rnotes.rst:2411
+#: ../../rnotes.rst:3382
+# aa7bb4ea4d0941bc8140111dbb8af091
+# a6640f09a1894e6597632d1dce45fed6
+msgid "Reboot this XenServer host."
+msgstr ""
+
+#: ../../rnotes.rst:2415
+#: ../../rnotes.rst:2425
+#: ../../rnotes.rst:3386
+#: ../../rnotes.rst:3394
+# baa1e6147c854b659e178a302e991f3b
+# 7dcf051dfcf74e2d993f7e3995bc7bec
+# f64177cb003044a1bbbb2a319e2f8b84
+# 1bc5465fb7384879a27b3c605f34b2bf
+msgid "Run the following:"
+msgstr ""
+
+#: ../../rnotes.rst:2421
+#: ../../rnotes.rst:3390
+# d236387f6cae4016885806bbf7abdf02
+# 87036bcab733448f95f0ba794ce12506
+msgid "If the message \"mv: cannot stat \\`/etc/cron.daily/logrotate': No such file or directory\" appears, you can safely ignore it."
+msgstr ""
+
+#: ../../rnotes.rst:2433
+#: ../../rnotes.rst:3402
+# 897e2e4a95984933b9a64f63be27747d
+# 83c27089bfe946598169ee4c6e34c066
+msgid "On each slave host in the Xen pool, repeat these steps, starting from \"manually live migrate VMs.\""
+msgstr ""
+
+#: ../../rnotes.rst:2436
+# 2d1ff5d4bbd641a99083f6f5761692c3
+msgid "**Troubleshooting Tip:** If passwords which you know to be valid appear not to work after upgrade, or other UI issues are seen, try clearing your browser cache and reloading the UI page."
+msgstr ""
+
+#: ../../rnotes.rst:2439
+# 82790ea01a2e453292fd3c0f5b3aeb5a
+msgid "Upgrade from 2.2.14 to 4.3"
+msgstr ""
+
+#: ../../rnotes.rst:2443
+# 6728458389e8472db11d804a01fef76e
+msgid "Ensure that you query your IPaddress usage records and process them; for example, issue invoices for any usage that you have not yet billed users for."
+msgstr ""
+
+#: ../../rnotes.rst:2447
+# 50e27594ab444c7b9abf820d92391cc4
+msgid "Starting in 3.0.2, the usage record format for IP addresses is the same as the rest of the usage types. Instead of a single record with the assignment and release dates, separate records are generated per aggregation period with start and end dates. After upgrading to 4.3, any existing IP address usage records in the old format will no longer be available."
+msgstr ""
+
+#: ../../rnotes.rst:2456
+# 0f112aff5e3a40229d261d3025697c2a
+msgid "If you are using version 2.2.0 - 2.2.13, first upgrade to 2.2.14 by using the instructions in the `2.2.14 Release Notes <http://download.cloud.com/releases/2.2.0/CloudStack2.2.14ReleaseNotes.pdf>`__."
+msgstr ""
+
+#: ../../rnotes.rst:2460
+# 36b91bca26364212b55e0431b9ef3c50
+msgid "**KVM Hosts:** If KVM hypervisor is used in your cloud, be sure you completed the step to insert a valid username and password into the host\\_details table on each KVM node as described in the 2.2.14 Release Notes. This step is critical, as the database will be encrypted after the upgrade to 4.3."
+msgstr ""
+
+#: ../../rnotes.rst:2464
+# e632bad81d304b5db94858d58117436e
+msgid "While running the 2.2.14 system, log in to the UI as root administrator."
+msgstr ""
+
+#: ../../rnotes.rst:2469
+# cfa10b7552cc46f5b525a62659daf633
+msgid "Using the UI, add a new System VM template for each hypervisor type that is used in your cloud. In each zone, add a system VM template for each hypervisor used in that zone"
+msgstr ""
+
+#: ../../rnotes.rst:2489
+# 7953d86b0a724e9dbdae1b45e20ee5f0
+msgid "In the Register template dialog box, specify the following values depending on the hypervisor type (do not change these):"
+msgstr ""
+
+#: ../../rnotes.rst:2575
+# e73c6f280a964e9ab53e8222dd07d15c
+msgid "Watch the screen to be sure that the template downloads successfully and enters the READY state. Do not proceed until this is successful"
+msgstr ""
+
+#: ../../rnotes.rst:2580
+# 043250aad638485091b1ad7d4904d976
+msgid "**WARNING**: If you use more than one type of hypervisor in your cloud, be sure you have repeated these steps to download the system VM template for each hypervisor type. Otherwise, the upgrade will fail."
+msgstr ""
+
+#: ../../rnotes.rst:2677
+# 9372e38792a84c4d9bfb8155f65bcc6f
+msgid "If you are using Ubuntu, follow this procedure to upgrade your packages. If not, skip to step `13 <#upgrade-rpm-packages-22>`__."
+msgstr ""
+
+#: ../../rnotes.rst:2727
+# 7f39a2e90aef41da83b417f972663e92
+msgid "On KVM hosts, you will need to manually install the ``cloudstack-agent`` package:"
+msgstr ""
+
+#: ../../rnotes.rst:2789
+# 13cfb58fe8ee46bb80e2f551a1135ed8
+msgid "If you are using CentOS or RHEL, follow this procedure to upgrade your packages. If not, skip to step `14 <#correct-components-xml-22>`__."
+msgstr ""
+
+#: ../../rnotes.rst:2871
+# 0432fc0914754107ac9754d391f54297
+msgid "If you have made changes to your existing copy of the file components.xml in your previous-version CloudStack installation, the changes will be preserved in the upgrade. However, you need to do the following steps to place these changes in a new version of the file which is compatible with version 4.0.0-incubating."
+msgstr ""
+
+#: ../../rnotes.rst:2877
+# 7ba721c652e94aadb385c5898dc894ed
+msgid "How will you know whether you need to do this? If the upgrade output in the previous step included a message like the following, then some custom content was found in your old components.xml, and you need to merge the two files:"
+msgstr ""
+
+#: ../../rnotes.rst:2886
+# 71dc951ca5664bf087d4f9212bc11e16
+msgid "Make a backup copy of your ``/etc/cloud/management/components.xml`` file. For example:"
+msgstr ""
+
+#: ../../rnotes.rst:2904
+# 5201132a543646bf84dc219e48173483
+msgid "Merge your changes from the backup file into the new components.xml file."
+msgstr ""
+
+#: ../../rnotes.rst:2913
+# ad4f895c83a84caf9ab707f7338c373e
+msgid "After upgrading to 4.3, API clients are expected to send plain text passwords for login and user creation, instead of MD5 hash. If API client changes are not acceptable, following changes are to be made for backward compatibility:"
+msgstr ""
+
+#: ../../rnotes.rst:2936
+# 1b3777b6ac2f49f0ae518824ae49679f
+msgid "PlainTextUserAuthenticator works the same way MD5UserAuthenticator worked prior to 4.2."
+msgstr ""
+
+#: ../../rnotes.rst:2941
+# 4221f77c756443ce9ab754de8ec65d66
+msgid "If you have made changes to your existing copy of the ``/etc/cloud/management/db.properties`` file in your previous-version CloudStack installation, the changes will be preserved in the upgrade. However, you need to do the following steps to place these changes in a new version of the file which is compatible with this version."
+msgstr ""
+
+#: ../../rnotes.rst:2950
+# b3daf8da6b434814840365b1fa239b76
+msgid "Make a backup copy of your file ``/etc/cloud/management/db.properties``. For example:"
+msgstr ""
+
+#: ../../rnotes.rst:2959
+# 50f2571bc6ae44eb9fa538ab20f55834
+msgid "Copy ``/etc/cloud/management/db.properties.rpmnew`` to create a new ``/etc/cloud/management/db.properties``:"
+msgstr ""
+
+#: ../../rnotes.rst:2968
+# 82dac835ce744fa2843e8fd4f00d725f
+msgid "Merge your changes from the backup file into the new db.properties file."
+msgstr ""
+
+#: ../../rnotes.rst:2977
+# 823c919ee94a4ea995fb5b6acb1789e2
+msgid "On the management server node, run the following command. It is recommended that you use the command-line flags to provide your own encryption keys. See Password and Key Encryption in the Installation Guide."
+msgstr ""
+
+#: ../../rnotes.rst:2986
+# 3183fd7f9fc64c1da805d400cef1a448
+msgid "When used without arguments, as in the following example, the default encryption type and keys will be used:"
+msgstr ""
+
+#: ../../rnotes.rst:2991
+# db7fda651fdf4edbbb55d79666f5de0a
+msgid "(Optional) For encryption\\_type, use file or web to indicate the technique used to pass in the database encryption password. Default: file."
+msgstr ""
+
+#: ../../rnotes.rst:2997
+# 1686fdd4b329427998f940269214b95e
+msgid "(Optional) For management\\_server\\_key, substitute the default key that is used to encrypt confidential parameters in the properties file. Default: password. It is highly recommended that you replace this with a more secure value"
+msgstr ""
+
+#: ../../rnotes.rst:3004
+# 53b58c1927814bafa5a8d851cf83f127
+msgid "(Optional) For database\\_key, substitute the default key that is used to encrypt confidential parameters in the CloudStack database. Default: password. It is highly recommended that you replace this with a more secure value."
+msgstr ""
+
+#: ../../rnotes.rst:3011
+# 62edafd0b35a480382433052c36a483a
+msgid "Repeat steps 10 - 14 on every management server node. If you provided your own encryption key in step 14, use the same key on all other management servers."
+msgstr ""
+
+#: ../../rnotes.rst:3024
+# ceadabc924b2492b89494d0e3665c19b
+msgid "Wait until the databases are upgraded. Ensure that the database upgrade is complete. You should see a message like \"Complete! Done.\" After confirmation, start the other Management Servers one at a time by running the same command on each node."
+msgstr ""
+
+#: ../../rnotes.rst:3040
+# 45eba2e4a54f4843b0e27e9c42f1dbf2
+msgid "(KVM only) Perform the following additional steps on each KVM host."
+msgstr ""
+
+#: ../../rnotes.rst:3042
+# dac62cccc4d74aa489a543c5660e35c9
+msgid "These steps will not affect running guests in the cloud. These steps are required only for clouds using KVM as hosts and only on the KVM hosts."
+msgstr ""
+
+#: ../../rnotes.rst:3048
+# c435bb7040ed46ed92c3d29c2fefc4ae
+msgid "Configure your CloudStack package repositories as outlined in the Installation Guide"
+msgstr ""
+
+#: ../../rnotes.rst:3061
+# b107265977d2498f8ef4131c0c86a1ed
+msgid "Update the agent software with one of the following command sets as appropriate."
+msgstr ""
+
+#: ../../rnotes.rst:3075
+# ae15ee20e0da4240a42ecb0ad283ba86
+msgid "Copy the contents of the ``agent.properties`` file to the new ``agent.properties`` file by using the following command"
+msgstr ""
+
+#: ../../rnotes.rst:3125
+# 8bb30e012222481888026129c2f7e555
+msgid "Log in to the CloudStack UI as admin, and check the status of the hosts. All hosts should come to Up state (except those that you know to be offline). You may need to wait 20 or 30 minutes, depending on the number of hosts."
+msgstr ""
+
+#: ../../rnotes.rst:3130
+# 9ee45f8da2654c7f88973bb87d6bb717
+msgid "Do not proceed to the next step until the hosts show in the Up state. If the hosts do not come to the Up state, contact support."
+msgstr ""
+
+#: ../../rnotes.rst:3135
+# fa850967858f47febfc91997ac25f725
+msgid "Run the following script to stop, then start, all Secondary Storage VMs, Console Proxy VMs, and virtual routers."
+msgstr ""
+
+#: ../../rnotes.rst:3140
+# 15eef6c66bb94d56b1109582896c36ec
+msgid "Run the command once on one management server. Substitute your own IP address of the MySQL instance, the MySQL user to connect as, and the password to use for that user. In addition to those parameters, provide the \"-c\" and \"-r\" arguments. For example:"
+msgstr ""
+
+#: ../../rnotes.rst:3155
+# d1283b650aa04aceac0fb1cc712af280
+msgid "After the script terminates, check the log to verify correct execution:"
+msgstr ""
+
+#: ../../rnotes.rst:3162
+# 9590559e0ef845399718b5b37e87d91a
+msgid "The content should be like the following:"
+msgstr ""
+
+#: ../../rnotes.rst:3175
+# 2ec40ea9c93549bb843191d9b8b2fce9
+msgid "If you would like additional confirmation that the new system VM templates were correctly applied when these system VMs were rebooted, SSH into the System VM and check the version."
+msgstr ""
+
+#: ../../rnotes.rst:3179
+# fd02ccf0a24145788a58ba23ef308968
+msgid "Use one of the following techniques, depending on the hypervisor."
+msgstr ""
+
+#: ../../rnotes.rst:3181
+# 2df764619b4b495981cb99842ea38f1a
+msgid "**XenServer or KVM:**"
+msgstr ""
+
+#: ../../rnotes.rst:3183
+# 68efcc3b46484b4b808e5a39b49d73a1
+msgid "SSH in by using the link local IP address of the system VM. For example, in the command below, substitute your own path to the private key used to log in to the system VM and your own link local IP."
+msgstr ""
+
+#: ../../rnotes.rst:3188
+# fd4b333286e5478d97c06160278544ca
+msgid "Run the following commands on the XenServer or KVM host on which the system VM is present:"
+msgstr ""
+
+#: ../../rnotes.rst:3196
+#: ../../rnotes.rst:3215
+# d020aa4087674068b0b854c5f95de59a
+# 9d87110c8bca44f28b610e5dd11c2b31
+msgid "The output should be like the following:"
+msgstr ""
+
+#: ../../rnotes.rst:3202
+# 253faad325424be09decb709919d5f28
+msgid "**ESXi:**"
+msgstr ""
+
+#: ../../rnotes.rst:3204
+# 7f9fa5dd30cb405bbb4e900045e4e9c4
+msgid "SSH in using the private IP address of the system VM. For example, in the command below, substitute your own path to the private key used to log in to the system VM and your own private IP."
+msgstr ""
+
+#: ../../rnotes.rst:3208
+# f71cc5b4b18f4b888cf90797987621fd
+msgid "Run the following commands on the Management Server:"
+msgstr ""
+
+#: ../../rnotes.rst:3223
+# 05d0ba7090a3476ca03dba20a21ba759
+msgid "If needed, upgrade all Citrix XenServer hypervisor hosts in your cloud to a version supported by CloudStack 4.0.0-incubating. The supported versions are XenServer 5.6 SP2 and 6.0.2. Instructions for upgrade can be found in the CloudStack 4.0.0-incubating Installation Guide."
+msgstr ""
+
+#: ../../rnotes.rst:3231
+# f40400badcaf4fcf9390c849d29a7800
+msgid "Apply the XenServer hotfix XS602E003 (and any other needed hotfixes) to XenServer v6.0.2 hypervisor hosts."
+msgstr ""
+
+#: ../../rnotes.rst:3261
+# 36cbfcfda1a2480e948ce702f432449e
+msgid "Prepare the upgrade by running the following on one XenServer host:"
+msgstr ""
+
+#: ../../rnotes.rst:3268
+# 3fd5250f54864755a9d4fb5274f1b731
+msgid "If you see a message like \"can't eject CD\", log in to the VM and umount the CD, then run this script again."
+msgstr ""
+
+#: ../../rnotes.rst:3273
+# d39f60ad6d3b479ca5f80e075fcb7336
+msgid "Upload the hotfix to the XenServer hosts. Always start with the Xen pool master, then the slaves. Using your favorite file copy utility (e.g. WinSCP), copy the hotfixes to the host. Place them in a temporary folder such as /root or /tmp."
+msgstr ""
+
+#: ../../rnotes.rst:3311
+# 2ea6ac411b414c97a5d700d01a73c88f
+msgid "``# xe host-list``"
+msgstr ""
+
+#: ../../rnotes.rst:3319
+# 8dd945f518ec4ae49e9d99c221aa8800
+msgid "``xe patch-apply host-uuid=host-uuid`` uuid=\\ *``hotfix-uuid``*"
+msgstr ""
+
+#: ../../rnotes.rst:3329
+# 774cb9a979354f4eb768e85ed3b33252
+msgid "``/usr/share/cloudstack -common/scripts/vm/hype rvisor/xenserver/xenser ver60/NFSSR.py``"
+msgstr ""
+
+#: ../../rnotes.rst:3329
+# eab01b95f0be46da97675955e962ee01
+msgid "``/opt/xensource/sm/NFSSR.py``"
+msgstr ""
+
+#: ../../rnotes.rst:3334
+# 9e059b42b8344fcfb27f1ba2f9d5e069
+msgid "``/usr/share/cloudstack -common/scripts/vm/hype rvisor/xenserver/setupx enserver.sh``"
+msgstr ""
+
+#: ../../rnotes.rst:3334
+#: ../../rnotes.rst:3388
+# 6a8dcdfe83e649fb80bcb75c4cdca85f
+# 1368764a6dec4fb49e23adb8fbda6b0d
+msgid "``/opt/xensource/bin/setupxenserver.sh``"
+msgstr ""
+
+#: ../../rnotes.rst:3339
+# 736582523a6b4710a62c8f0a03053ac6
+msgid "``/usr/lib64/cloudstack -common/scripts/vm/hype rvisor/xenserver/make_m igratable.sh``"
+msgstr ""
+
+#: ../../rnotes.rst:3339
+# c04d43d5d16d44c0a133aa8ebae5891f
+msgid "``/opt/xensource/bin/make_migratable.sh``"
+msgstr ""
+
+#: ../../rnotes.rst:3365
+# c25347962eed49c6a57d0832a0e9aec1
+msgid "``# tar xf xenserver-cloud-supp.tgz``"
+msgstr ""
+
+#: ../../rnotes.rst:3371
+# c5ac8fb53ab04e90957992eb9c5be8ac
+msgid "``# xe-install-supplemental-pack xenserver-cloud-supp.iso``"
+msgstr ""
+
+#: ../../rnotes.rst:3378
+# 2a0c09f664a44e9f866660c47094ab1a
+msgid "``# xe-switch-network-backend bridge``"
+msgstr ""
+
diff --git a/source/upgrading/upgrade/_java_8_ubuntu.rst b/source/upgrading/upgrade/_java_8_ubuntu.rst
new file mode 100644
index 0000000..1e0a57d
--- /dev/null
+++ b/source/upgrading/upgrade/_java_8_ubuntu.rst
@@ -0,0 +1,31 @@
+.. 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.
+
+.. sub-section included in upgrade notes.
+
+Java 8 JRE on Ubuntu
+--------------------
+
+CloudStack |version| requires installation of Java 8 JRE from an external PPA
+such as openjdk-r for Ubuntu distributions where the openjdk-8 packages are not
+available from the main repositories such as on Ubuntu 14.04. The PPA can be
+added before installation/upgrade:
+
+ .. parsed-literal::
+
+ $ sudo add-apt-repository ppa:openjdk-r/ppa
+ $ sudo apt-get update
+
+Users can also choose to install Java 8 distribution from Oracle, or `Xulu-8 <http://repos.azulsystems.com/>`_ OpenJDK distribution from Azul.
diff --git a/source/upgrading/upgrade/_mysql_connector.rst b/source/upgrading/upgrade/_mysql_connector.rst
new file mode 100644
index 0000000..a2afa31
--- /dev/null
+++ b/source/upgrading/upgrade/_mysql_connector.rst
@@ -0,0 +1,33 @@
+Install new MySQL connector
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Apache CloudStack |release| require an upgrade of the MySQL connector on CentOS.
+Starting with 4.9.0, cloudstack-management RPM's now depend on
+``mysql-connector-python`` package.
+
+
+MySQL connector RPM repository
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Add a new yum repo ``/etc/yum.repos.d/mysql.repo``:
+
+.. parsed-literal::
+
+ [mysql-community]
+ name=MySQL Community connectors
+ baseurl=http://repo.mysql.com/yum/mysql-connectors-community/el/$releasever/$basearch/
+ enabled=1
+ gpgcheck=1
+
+Import GPG public key from MySQL:
+
+.. parsed-literal::
+
+ rpm --import http://repo.mysql.com/RPM-GPG-KEY-mysql
+
+Install mysql-connector
+
+.. parsed-literal::
+
+ yum install mysql-connector-python
+
diff --git a/source/upgrading/upgrade/_no-sysvm_templates.rst b/source/upgrading/upgrade/_no-sysvm_templates.rst
new file mode 100644
index 0000000..dcfb81d
--- /dev/null
+++ b/source/upgrading/upgrade/_no-sysvm_templates.rst
@@ -0,0 +1,21 @@
+.. 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.
+
+.. sub-section included in upgrade notes.
+
+Update System-VM templates
+--------------------------
+
+Upgrade from |version_to_upgrade| to |version| does not require new systemvm-templates.
diff --git a/source/upgrading/upgrade/_sysvm_manual_hotfix.rst b/source/upgrading/upgrade/_sysvm_manual_hotfix.rst
new file mode 100644
index 0000000..90a7d56
--- /dev/null
+++ b/source/upgrading/upgrade/_sysvm_manual_hotfix.rst
@@ -0,0 +1,115 @@
+.. 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.
+
+.. sub-section optinaly included in upgrade notes.
+
+.. Add following to file when including this manual hotfix
+ .. _manual_hofix:
+
+ Manual hotfix for systemvm upgrade
+ ----------------------------------
+
+ .. include:: _sysvm_restart.rst
+.. End of include example
+
+Some manual steps are required to upgrade of SystemVMs and Virtual Routers.
+
+Following MySQL commands will update the template ID used by Console Proxy VMs (CPVM)
+and Secondary Storage VMs (SSVM). It will also change the default template for
+Virtual Router to *systemvm-<hypervisor>-4.4* templates.
+
+
+XenServer SystemVMs
+^^^^^^^^^^^^^^^^^^^
+
+ Execute following MySQL queries in MySQL.
+ Please note ``<ID FROM COMMAND #1>`` from the first command
+
+ #. Connect to the database:
+
+ .. code-block:: bash
+
+ mysql -h localhost -u root -p cloud
+
+ #. get the id of the new template:
+
+ .. code-block:: mysql
+
+ select id,name from vm_template where name = 'systemvm-xenserver-4.4';
+
+ #. Replace ``<ID FROM COMMAND #1>`` by the id from the previous command and execute following:
+
+ .. code-block:: mysql
+
+ update vm_template set type='SYSTEM' where id='<ID FROM COMMAND #1>';
+ update vm_instance set vm_template_id = '<ID FROM COMMAND #1>' where type='ConsoleProxy' and hypervisor_type = 'xenserver';
+ update vm_instance set vm_template_id = '<ID FROM COMMAND #1>' where type='SecondaryStorageVm' and hypervisor_type = 'xenserver';
+ update configuration set value = 'systemvm-xenserver-4.4' where name = 'router.template.xen';
+
+
+KVM SystemVMs
+^^^^^^^^^^^^^
+
+ Execute following MySQL queries in MySQL.
+ Please note ``<ID FROM COMMAND #1>`` from the first command
+
+ #. Connect to the database:
+
+ .. code-block:: bash
+
+ mysql -h localhost -u root -p cloud
+
+ #. get the id of the new template:
+
+ .. code-block:: mysql
+
+ select id,name from vm_template where name = 'systemvm-kvm-4.4';
+
+ #. Replace ``<ID FROM COMMAND #1>`` by the id from the previous command and execute following:
+
+ .. code-block:: mysql
+
+ update vm_template set type='SYSTEM' where id='<ID FROM COMMAND #1>';
+ update vm_instance set vm_template_id = '<ID FROM COMMAND #1>' where type='ConsoleProxy' and hypervisor_type = 'KVM';
+ update vm_instance set vm_template_id = '<ID FROM COMMAND #1>' where type='SecondaryStorageVm' and hypervisor_type = 'KVM';
+ update configuration set value = 'systemvm-kvm-4.4' where name = 'router.template.kvm';
+
+
+VMware SystemVMs
+^^^^^^^^^^^^^^^^
+
+ Execute following MySQL queries in MySQL.
+ Please note ``<ID FROM COMMAND #1>`` from the first command
+
+ #. Connect to the database:
+
+ .. code-block:: bash
+
+ mysql -h localhost -u root -p cloud
+
+ #. get the id of the new template:
+
+ .. code-block:: mysql
+
+ select id,name from vm_template where name = 'systemvm-vmware-4.4';
+
+ #. Replace ``<ID FROM COMMAND #1>`` by the id from the previous command and execute following:
+
+ .. code-block:: mysql
+
+ update vm_template set type='SYSTEM' where id='<ID FROM COMMAND #1>';
+ update vm_instance set vm_template_id = '<ID FROM COMMAND #1>' where type='ConsoleProxy' and hypervisor_type = 'vmware';
+ update vm_instance set vm_template_id = '<ID FROM COMMAND #1>' where type='SecondaryStorageVm' and hypervisor_type = 'vmware';
+ update configuration set value = 'systemvm-vmware-4.4' where name = 'router.template.vmware';
diff --git a/source/upgrading/upgrade/_sysvm_restart.rst b/source/upgrading/upgrade/_sysvm_restart.rst
new file mode 100644
index 0000000..7ab916a
--- /dev/null
+++ b/source/upgrading/upgrade/_sysvm_restart.rst
@@ -0,0 +1,52 @@
+.. 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.
+
+.. sub-section included in upgrade notes.
+
+Once you've upgraded the packages on your management servers, you'll
+need to restart the system VMs. Ensure that the admin port is set to
+8096 by using the "integration.api.port" global parameter. This port
+is used by the cloud-sysvmadm script at the end of the upgrade
+procedure. For information about how to set this parameter, see :ref:`configuration parameters <configuration-parameters>`
+Changing this parameter will require management server restart. Also
+make sure port 8096 is open in your local host firewall to do this.
+
+There is a script that will do this for you, all you need to do is
+run the script and supply the IP address for your MySQL instance and
+your MySQL credentials:
+
+.. parsed-literal::
+
+ # nohup cloudstack-sysvmadm -d IPaddress -u cloud -p password -a > sysvm.log 2>&1 &
+
+You can monitor the log for progress. The process of restarting the
+system VMs can take an hour or more.
+
+.. parsed-literal::
+
+ # tail -f sysvm.log
+
+The output to ``sysvm.log`` will look something like this:
+
+.. parsed-literal::
+
+ Stopping and starting 1 secondary storage vm(s)...
+ Done stopping and starting secondary storage vm(s)
+ Stopping and starting 1 console proxy vm(s)...
+ Done stopping and starting console proxy vm(s).
+ Stopping and starting 4 running routing vm(s)...
+ Done restarting router(s).
+
+.. sub-section included in upgrade notes.
diff --git a/source/upgrading/upgrade/_sysvm_templates.rst b/source/upgrading/upgrade/_sysvm_templates.rst
new file mode 100644
index 0000000..45bee8c
--- /dev/null
+++ b/source/upgrading/upgrade/_sysvm_templates.rst
@@ -0,0 +1,145 @@
+.. 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.
+
+.. sub-section included in upgrade notes.
+
+Update System-VM templates
+--------------------------
+
+#. While running the existing |version_to_upgrade| system, log in to the UI as
+ root administrator.
+
+#. In the left navigation bar, click Templates.
+
+#. In Select view, click Templates.
+
+#. Click Register template.
+
+ The Register template dialog box is displayed.
+
+#. In the Register template dialog box, specify the following values
+ (do not change these):
+
+ .. cssclass:: table-striped table-bordered table-hover
+
+ +------------+------------------------------------------------------------+
+ | Hypervisor | Description |
+ +============+============================================================+
+ | XenServer | Name: systemvm-xenserver-4.11.1 |
+ | | |
+ | | Description: systemvm-xenserver-4.11.1 |
+ | | |
+ | | URL: |sysvm64-url-xen| |
+ | | |
+ | | Zone: Choose the zone where this hypervisor is used |
+ | | |
+ | | Hypervisor: XenServer |
+ | | |
+ | | Format: VHD |
+ | | |
+ | | OS Type: Debian GNU/Linux 7.0 (64-bit) (or the |
+ | | highest Debian release number available in the |
+ | | dropdown) |
+ | | |
+ | | Extractable: no |
+ | | |
+ | | Password Enabled: no |
+ | | |
+ | | Public: no |
+ | | |
+ | | Featured: no |
+ | | |
+ | | Routing: no |
+ +------------+------------------------------------------------------------+
+ | KVM | Name: systemvm-kvm-4.11.1 |
+ | | |
+ | | Description: systemvm-kvm-4.11.1 |
+ | | |
+ | | URL: |sysvm64-url-kvm| |
+ | | |
+ | | Zone: Choose the zone where this hypervisor is used |
+ | | |
+ | | Hypervisor: KVM |
+ | | |
+ | | Format: QCOW2 |
+ | | |
+ | | OS Type: Debian GNU/Linux 7.0 (64-bit) (or the |
+ | | highest Debian release number available in the |
+ | | dropdown) |
+ | | |
+ | | Extractable: no |
+ | | |
+ | | Password Enabled: no |
+ | | |
+ | | Public: no |
+ | | |
+ | | Featured: no |
+ | | |
+ | | Routing: no |
+ +------------+------------------------------------------------------------+
+ | VMware | Name: systemvm-vmware-4.11.1 |
+ | | |
+ | | Description: systemvm-vmware-4.11.1 |
+ | | |
+ | | URL: |sysvm64-url-vmware| |
+ | | |
+ | | Zone: Choose the zone where this hypervisor is used |
+ | | |
+ | | Hypervisor: VMware |
+ | | |
+ | | Format: OVA |
+ | | |
+ | | OS Type: Other Linux 64-bit (or Debian 8.0 or 9.0 64-bit) |
+ | | |
+ | | Extractable: no |
+ | | |
+ | | Password Enabled: no |
+ | | |
+ | | Public: no |
+ | | |
+ | | Featured: no |
+ | | |
+ | | Routing: no |
+ +------------+------------------------------------------------------------+
+ | HyperV | Name: systemvm-hyperv-4.11.1 |
+ | | |
+ | | Description: systemvm-hyperv-4.11.1 |
+ | | |
+ | | URL: |sysvm64-url-hyperv| |
+ | | |
+ | | Zone: Choose the zone where this hypervisor is used |
+ | | |
+ | | Hypervisor: Hyper-V |
+ | | |
+ | | Format: VHD |
+ | | |
+ | | OS Type: Debian GNU/Linux 7.0 (64-bit) (or the |
+ | | highest Debian release number available in the |
+ | | dropdown) |
+ | | |
+ | | Extractable: no |
+ | | |
+ | | Password Enabled: no |
+ | | |
+ | | Public: no |
+ | | |
+ | | Featured: no |
+ | | |
+ | | Routing: no |
+ +------------+------------------------------------------------------------+
+
+#. Watch the screen to be sure that the template downloads successfully and
+ enters the **READY** state. Do not proceed until this is successful.
+
diff --git a/source/upgrading/upgrade/_sysvm_templates_pre45.rst b/source/upgrading/upgrade/_sysvm_templates_pre45.rst
new file mode 100644
index 0000000..8f3ddfc
--- /dev/null
+++ b/source/upgrading/upgrade/_sysvm_templates_pre45.rst
@@ -0,0 +1,219 @@
+.. 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.
+
+.. sub-section included in upgrade notes.
+
+Update System-VM templates
+--------------------------
+
+.. warning::
+ Upgrading from 4.4 or older to 4.6.0 require 2 systemvm templates to be
+ downloaded, for 4.5 and 4.6.
+
+#. While running the existing |version_to_upgrade| system, log in to the UI as
+ root administrator.
+
+#. In the left navigation bar, click Templates.
+
+#. In Select view, click Templates.
+
+#. Register 4.5 systemvm template:
+
+ #. Click Register template.
+
+ The Register template dialog box is displayed.
+
+ #. In the Register template dialog box, specify the following values
+ (do not change these):
+
+ .. cssclass:: table-striped table-bordered table-hover
+
+ +------------+------------------------------------------------------------+
+ | Hypervisor | Description |
+ +============+============================================================+
+ | XenServer | Name: systemvm-xenserver-4.5 |
+ | | |
+ | | Description: systemvm-xenserver-4.5 |
+ | | |
+ | | URL: |acs45-sysvm64-url-xen| |
+ | | |
+ | | Zone: Choose the zone where this hypervisor is used |
+ | | |
+ | | Hypervisor: XenServer |
+ | | |
+ | | Format: VHD |
+ | | |
+ | | OS Type: Debian GNU/Linux 7.0 (64-bit) (or the |
+ | | highest Debian release number available in the |
+ | | dropdown) |
+ | | |
+ | | Extractable: no |
+ | | |
+ | | Password Enabled: no |
+ | | |
+ | | Public: no |
+ | | |
+ | | Featured: no |
+ | | |
+ | | Routing: no |
+ +------------+------------------------------------------------------------+
+ | KVM | Name: systemvm-kvm-4.5 |
+ | | |
+ | | Description: systemvm-kvm-4.5 |
+ | | |
+ | | URL: |acs45-sysvm64-url-kvm| |
+ | | |
+ | | Zone: Choose the zone where this hypervisor is used |
+ | | |
+ | | Hypervisor: KVM |
+ | | |
+ | | Format: QCOW2 |
+ | | |
+ | | OS Type: Debian GNU/Linux 7.0 (64-bit) (or the |
+ | | highest Debian release number available in the |
+ | | dropdown) |
+ | | |
+ | | Extractable: no |
+ | | |
+ | | Password Enabled: no |
+ | | |
+ | | Public: no |
+ | | |
+ | | Featured: no |
+ | | |
+ | | Routing: no |
+ +------------+------------------------------------------------------------+
+ | VMware | Name: systemvm-vmware-4.5 |
+ | | |
+ | | Description: systemvm-vmware-4.5 |
+ | | |
+ | | URL: |acs45-sysvm64-url-vmware| |
+ | | |
+ | | Zone: Choose the zone where this hypervisor is used |
+ | | |
+ | | Hypervisor: VMware |
+ | | |
+ | | Format: OVA |
+ | | |
+ | | OS Type: Debian GNU/Linux 7.0 (64-bit) (or the |
+ | | highest Debian release number available in the |
+ | | dropdown) |
+ | | |
+ | | Extractable: no |
+ | | |
+ | | Password Enabled: no |
+ | | |
+ | | Public: no |
+ | | |
+ | | Featured: no |
+ | | |
+ | | Routing: no |
+ +------------+------------------------------------------------------------+
+
+#. Register |release| systemvm template:
+
+ #. Click Register template.
+
+ The Register template dialog box is displayed.
+
+ #. In the Register template dialog box, specify the following values
+ (do not change these):
+
+ .. cssclass:: table-striped table-bordered table-hover
+
+ +------------+------------------------------------------------------------+
+ | Hypervisor | Description |
+ +============+============================================================+
+ | XenServer | Name: systemvm-xenserver-4.6 |
+ | | |
+ | | Description: systemvm-xenserver-4.6 |
+ | | |
+ | | URL: |sysvm64-url-xen| |
+ | | |
+ | | Zone: Choose the zone where this hypervisor is used |
+ | | |
+ | | Hypervisor: XenServer |
+ | | |
+ | | Format: VHD |
+ | | |
+ | | OS Type: Debian GNU/Linux 7.0 (64-bit) (or the |
+ | | highest Debian release number available in the |
+ | | dropdown) |
+ | | |
+ | | Extractable: no |
+ | | |
+ | | Password Enabled: no |
+ | | |
+ | | Public: no |
+ | | |
+ | | Featured: no |
+ | | |
+ | | Routing: no |
+ +------------+------------------------------------------------------------+
+ | KVM | Name: systemvm-kvm-4.6 |
+ | | |
+ | | Description: systemvm-kvm-4.6 |
+ | | |
+ | | URL: |sysvm64-url-kvm| |
+ | | |
+ | | Zone: Choose the zone where this hypervisor is used |
+ | | |
+ | | Hypervisor: KVM |
+ | | |
+ | | Format: QCOW2 |
+ | | |
+ | | OS Type: Debian GNU/Linux 7.0 (64-bit) (or the |
+ | | highest Debian release number available in the |
+ | | dropdown) |
+ | | |
+ | | Extractable: no |
+ | | |
+ | | Password Enabled: no |
+ | | |
+ | | Public: no |
+ | | |
+ | | Featured: no |
+ | | |
+ | | Routing: no |
+ +------------+------------------------------------------------------------+
+ | VMware | Name: systemvm-vmware-4.6 |
+ | | |
+ | | Description: systemvm-vmware-4.6 |
+ | | |
+ | | URL: |sysvm64-url-vmware| |
+ | | |
+ | | Zone: Choose the zone where this hypervisor is used |
+ | | |
+ | | Hypervisor: VMware |
+ | | |
+ | | Format: OVA |
+ | | |
+ | | OS Type: Debian GNU/Linux 7.0 (64-bit) (or the |
+ | | highest Debian release number available in the |
+ | | dropdown) |
+ | | |
+ | | Extractable: no |
+ | | |
+ | | Password Enabled: no |
+ | | |
+ | | Public: no |
+ | | |
+ | | Featured: no |
+ | | |
+ | | Routing: no |
+ +------------+------------------------------------------------------------+
+
+#. Watch the screen to be sure that the template downloads successfully and
+ enters the **READY** state. Do not proceed until this is successful.
diff --git a/source/upgrading/upgrade/_upgrade_header.rst b/source/upgrading/upgrade/_upgrade_header.rst
new file mode 100644
index 0000000..adcba58
--- /dev/null
+++ b/source/upgrading/upgrade/_upgrade_header.rst
@@ -0,0 +1,37 @@
+.. 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.
+
+.. sub-section included in upgrade notes.
+
+If you run into any issues during upgrades, please feel free to ask
+questions on users@cloudstack.apache.org or dev@cloudstack.apache.org.
+
+.. warning::
+ Depreciation of realhostip.com DNS and SSL certificate
+
+ The realhostip.com dynamic DNS resolution service is being retired this
+ summer. In advance of that, CloudStack 4.3 and later no longer uses
+ realhostip.com DNS domains or SSL certificates to encrypt Console Proxy or
+ file copy communications.
+
+Any steps that are hypervisor-specific will be called out with a note.
+
+We recommend reading through this section once or twice before beginning
+your upgrade procedure, and working through it on a test system before
+working on a production system.
+
+.. note::
+ The following upgrade instructions should be performed regardless of
+ hypervisor type.
diff --git a/source/upgrading/upgrade/_xenserver_upg.rst b/source/upgrading/upgrade/_xenserver_upg.rst
new file mode 100644
index 0000000..0440cfb
--- /dev/null
+++ b/source/upgrading/upgrade/_xenserver_upg.rst
@@ -0,0 +1,57 @@
+.. 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.
+
+.. sub-section included in upgrade notes pre 4.4.
+
+XenServer HA
+^^^^^^^^^^^^
+
+As of Apache CloudStack 4.4, CloudStack is not responsible to promote a new pool
+master on a Citrix XenServer pool. In case of failure of the pool master host,
+the responsability of electing a new pool master as been delegated back to the
+HA feature of XenServer. CloudStack remain responsible to honored HA capability
+for Compute Offerings of instances. The XenServer HA feature must be enabled
+only for the pool master, not for virtual-machines.
+
+
+Make sure XenServer has enabled HA on the pool.
+
+To test if poolHA is currently turned on:
+
+.. parsed-literal::
+
+ xe pool-list params=all | grep -E "ha-enabled|ha-config"
+
+Output when poolHA is ON:
+
+.. parsed-literal::
+
+ ha-enabled ( RO): true
+ ha-configuration ( RO): timeout: 180
+
+Output when poolHA is OFF:
+
+.. parsed-literal::
+
+ ha-enabled ( RO): false
+ ha-configuration ( RO):
+
+To enable poolHA, use something like this:
+
+.. parsed-literal::
+
+ xe pool-enable-ha heartbeat-sr-uuids={SR-UUID} ha-config:timeout=180
+
+Please refer to the `XenServer documentation <http://docs.vmd.citrix.com/XenServer/>`_, as there are multiple ways of configuring it either on NFS, iSCSI or Fibre Channel. Be aware though, that the timeout setting is not documented. The default is 30 seconds so you may want to bump that towards 120-180 seconds.
diff --git a/source/upgrading/upgrade/upgrade-4.10.rst b/source/upgrading/upgrade/upgrade-4.10.rst
new file mode 100644
index 0000000..2c3572b
--- /dev/null
+++ b/source/upgrading/upgrade/upgrade-4.10.rst
@@ -0,0 +1,421 @@
+.. 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.
+
+
+.. |version_to_upgrade| replace:: 4.10.x
+
+Upgrade Instruction from |version_to_upgrade|
+=============================================
+
+This section will guide you from CloudStack |version_to_upgrade| to CloudStack
+|release|.
+
+Any steps that are hypervisor-specific will be called out with a note.
+
+We recommend reading through this section once or twice before beginning
+your upgrade procedure, and working through it on a test system before
+working on a production system.
+
+.. note::
+ The following upgrade instructions should be performed regardless of
+ hypervisor type.
+
+Upgrade Steps:
+
+#. Backup CloudStack database (MySQL)
+#. Add package repository for MySQL connector
+#. Upgrade CloudStack management server(s)
+#. Update hypervisors specific dependencies
+
+Apache CloudStack 4.10.0.0 users who are upgrading to 4.11.0.0 should read the
+following discussion and workaround for a db-upgrade issue:
+http://markmail.org/message/f42kqr3mx4r4hgih
+
+.. include:: _sysvm_templates.rst
+
+Packages repository
+-------------------
+
+Most users of CloudStack manage the installation and upgrades of
+CloudStack with one of Linux's predominant package systems, RPM or
+APT. This guide assumes you'll be using RPM and Yum (for Red Hat
+Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu).
+
+Create RPM or Debian packages (as appropriate) and a repository from
+the |release| source, or check the Apache CloudStack downloads page at
+http://cloudstack.apache.org/downloads.html
+for package repositories supplied by community members. You will need
+them for :ref:`ubuntu410` or :ref:`rhel410` and :ref:`kvm410` hosts upgrade.
+
+Instructions for creating packages from the CloudStack source are in the
+`CloudStack Installation Guide`_.
+
+
+Database Preparation
+--------------------
+
+Backup current database
+
+#. Stop your management server or servers. Run this on all management
+ server hosts:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. If you are running a usage server or usage servers, stop those as well:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage stop
+
+#. Make a backup of your MySQL database. If you run into any issues or
+ need to roll back the upgrade, this will assist in debugging or
+ restoring your existing environment. You'll be prompted for your
+ password.
+
+ .. parsed-literal::
+
+ $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql
+ $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql
+
+#. **(KVM Only)** If primary storage of type local storage is in use, the
+ path for this storage needs to be verified to ensure it passes new
+ validation. Check local storage by querying the cloud.storage\_pool
+ table:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'"
+
+ If local storage paths are found to have a trailing forward slash,
+ remove it:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"';
+
+
+.. _ubuntu410:
+
+Management Server on Ubuntu
+---------------------------
+
+If you are using Ubuntu, follow this procedure to upgrade your packages. If
+not, skip to step :ref:`rhel410`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ APT repository, substitute your own URL for the ones used in these examples.
+
+The first order of business will be to change the sources list for
+each system with CloudStack packages. This means all management
+servers, and any hosts that have the KVM agent. (No changes should
+be necessary for hosts that are running VMware or Xen.)
+
+
+.. _apt-repo410:
+
+.. include:: _java_8_ubuntu.rst
+
+CloudStack apt repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Start by opening ``/etc/apt/sources.list.d/cloudstack.list`` on
+any systems that have CloudStack packages installed.
+
+This file should have one line, which contains:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.10
+
+We'll change it to point to the new package repository:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise |version|
+
+Setup the public key for the above repository:
+
+.. parsed-literal::
+
+ wget -qO - http://download.cloudstack.org/release.asc | sudo apt-key add -
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Now update your apt package list:
+
+ .. parsed-literal::
+
+ $ sudo apt-get update
+
+#. Now that you have the repository configured, it's time to upgrade
+ the ``cloudstack-management`` package.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-usage
+
+
+.. _rhel410:
+
+Management Server on CentOS/RHEL
+--------------------------------
+
+If you are using CentOS or RHEL, follow this procedure to upgrade your
+packages. If not, skip to hypervisors section :ref:`upg_hyp_410`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ yum repository, substitute your own URL for the ones used in these examples.
+
+
+.. include:: _mysql_connector.rst
+
+
+.. _rpm-repo410:
+
+CloudStack RPM repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The first order of business will be to change the yum repository
+for each system with CloudStack packages. This means all
+management servers, and any hosts that have the KVM agent.
+
+(No changes should be necessary for hosts that are running VMware
+or Xen.)
+
+Start by opening ``/etc/yum.repos.d/cloudstack.repo`` on any
+systems that have CloudStack packages installed.
+
+This file should have content similar to the following:
+
+.. parsed-literal::
+
+ [apache-cloudstack]
+ name=Apache CloudStack
+ baseurl=http://download.cloudstack.org/centos/6/4.10/
+ enabled=1
+ gpgcheck=0
+
+If you are using the community provided package repository, change
+the base url to ``http://download.cloudstack.org/centos/$releasever/|version|/``.
+
+Setup the GPG public key if you wish to enable ``gpgcheck=1``:
+
+.. parsed-literal::
+
+ rpm --import http://download.cloudstack.org/RPM-GPG-KEY
+
+
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Now that you have the repository configured, it's time to upgrade the
+ ``cloudstack-management``.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-usage
+
+.. _upg_hyp_410:
+
+Hypervisor: XenServer
+---------------------
+
+**(XenServer only)** Copy vhd-utils file on CloudStack management servers.
+Copy the file `vhd-utils <http://download.cloudstack.org/tools/vhd-util>`_
+to ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``.
+
+.. parsed-literal::
+
+ wget -P /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver \
+ http://download.cloudstack.org/tools/vhd-util
+
+
+Hypervisor: VMware
+------------------
+
+.. warning::
+ For VMware hypervisor CloudStack management server packages must be
+ build using "noredist". Refer to :ref:`building-noredist`
+
+**(VMware only)** Additional steps are required for each VMware cluster.
+These steps will not affect running guests in the cloud. These steps
+are required only for clouds using VMware clusters:
+
+#. Stop the Management Server:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. Generate the encrypted equivalent of your vCenter password:
+
+ .. parsed-literal::
+
+ $ java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.2.jar org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh input="_your_vCenter_password_" password="`cat /etc/cloudstack/management/key`" verbose=false
+
+Store the output from this step, we need to add this in
+cluster\_details table and vmware\_data\_center tables in place of
+the plain text password
+
+#. Find the ID of the row of cluster\_details table that you have to
+ update:
+
+ .. parsed-literal::
+
+ $ mysql -u <username> -p<password>
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Update the plain text password with the encrypted one
+
+ .. parsed-literal::
+
+ update cloud.cluster_details set value = '_ciphertext_from_step_1_'
+ where id = _id_from_step_2_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Find the ID of the correct row of vmware\_data\_center that you
+ want to update
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+#. update the plain text password with the encrypted one:
+
+ .. parsed-literal::
+
+ update cloud.vmware_data_center set password = '_ciphertext_from_step_1_'
+ where id = _id_from_step_5_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+
+.. _kvm410:
+
+Hypervisor: KVM
+---------------
+
+KVM on Ubuntu
+^^^^^^^^^^^^^
+
+(KVM only) Additional steps are required for each KVM host. These
+steps will not affect running guests in the cloud. These steps are
+required only for clouds using KVM as hosts and only on the KVM
+hosts.
+
+#. Configure the :ref:`APT repo <apt-repo410>` as detailed above.
+
+#. Stop the running agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+
+#. Update the agent software.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Start the agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent start
+
+
+KVM on CentOS/RHEL
+^^^^^^^^^^^^^^^^^^
+For KVM hosts, upgrade the ``cloudstack-agent`` package
+
+#. Configure the :ref:`rpm-repo410` as detailed above.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Restart the agent:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+ $ sudo killall jsvc
+ $ sudo service cloudstack-agent start
+
+
+Restart management services
+---------------------------
+
+#. Now it's time to start the management server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management start
+
+#. If you use it, start the usage server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage start
diff --git a/source/upgrading/upgrade/upgrade-4.11.rst b/source/upgrading/upgrade/upgrade-4.11.rst
new file mode 100644
index 0000000..952d1cf
--- /dev/null
+++ b/source/upgrading/upgrade/upgrade-4.11.rst
@@ -0,0 +1,416 @@
+.. 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.
+
+
+.. |version_to_upgrade| replace:: 4.11.0.0
+
+Upgrade Instruction from |version_to_upgrade|
+=============================================
+
+This section will guide you from CloudStack |version_to_upgrade| to latest
+CloudStack |release|.
+
+Any steps that are hypervisor-specific will be called out with a note.
+
+We recommend reading through this section once or twice before beginning
+your upgrade procedure, and working through it on a test system before
+working on a production system.
+
+.. note::
+ The following upgrade instructions should be performed regardless of
+ hypervisor type.
+
+Upgrade Steps:
+
+#. Backup CloudStack database (MySQL)
+#. Add package repository for MySQL connector
+#. Upgrade CloudStack management server(s)
+#. Update hypervisors specific dependencies
+
+.. include:: _sysvm_templates.rst
+
+Packages repository
+-------------------
+
+Most users of CloudStack manage the installation and upgrades of
+CloudStack with one of Linux's predominant package systems, RPM or
+APT. This guide assumes you'll be using RPM and Yum (for Red Hat
+Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu).
+
+Create RPM or Debian packages (as appropriate) and a repository from
+the |release| source, or check the Apache CloudStack downloads page at
+http://cloudstack.apache.org/downloads.html
+for package repositories supplied by community members. You will need
+them for :ref:`ubuntu411` or :ref:`rhel411` and :ref:`kvm411` hosts upgrade.
+
+Instructions for creating packages from the CloudStack source are in the
+`CloudStack Installation Guide`_.
+
+Database Preparation
+--------------------
+
+Backup current database
+
+#. Stop your management server or servers. Run this on all management
+ server hosts:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. If you are running a usage server or usage servers, stop those as well:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage stop
+
+#. Make a backup of your MySQL database. If you run into any issues or
+ need to roll back the upgrade, this will assist in debugging or
+ restoring your existing environment. You'll be prompted for your
+ password.
+
+ .. parsed-literal::
+
+ $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql
+ $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql
+
+#. **(KVM Only)** If primary storage of type local storage is in use, the
+ path for this storage needs to be verified to ensure it passes new
+ validation. Check local storage by querying the cloud.storage\_pool
+ table:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'"
+
+ If local storage paths are found to have a trailing forward slash,
+ remove it:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"';
+
+
+.. _ubuntu411:
+
+Management Server on Ubuntu
+---------------------------
+
+If you are using Ubuntu, follow this procedure to upgrade your packages. If
+not, skip to step :ref:`rhel411`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ APT repository, substitute your own URL for the ones used in these examples.
+
+The first order of business will be to change the sources list for
+each system with CloudStack packages. This means all management
+servers, and any hosts that have the KVM agent. (No changes should
+be necessary for hosts that are running VMware or Xen.)
+
+
+.. include:: _java_8_ubuntu.rst
+
+.. _apt-repo411:
+
+CloudStack apt repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Start by opening ``/etc/apt/sources.list.d/cloudstack.list`` on
+any systems that have CloudStack packages installed.
+
+This file should have one line, which contains:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.10
+
+We'll change it to point to the new package repository:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise |version|
+
+Setup the public key for the above repository:
+
+.. parsed-literal::
+
+ wget -qO - http://download.cloudstack.org/release.asc | sudo apt-key add -
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Now update your apt package list:
+
+ .. parsed-literal::
+
+ $ sudo apt-get update
+
+#. Now that you have the repository configured, it's time to upgrade
+ the ``cloudstack-management`` package.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-usage
+
+
+.. _rhel411:
+
+Management Server on CentOS/RHEL
+--------------------------------
+
+If you are using CentOS or RHEL, follow this procedure to upgrade your
+packages. If not, skip to hypervisors section :ref:`upg_hyp_411`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ yum repository, substitute your own URL for the ones used in these examples.
+
+
+.. include:: _mysql_connector.rst
+
+
+.. _rpm-repo411:
+
+CloudStack RPM repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The first order of business will be to change the yum repository
+for each system with CloudStack packages. This means all
+management servers, and any hosts that have the KVM agent.
+
+(No changes should be necessary for hosts that are running VMware
+or Xen.)
+
+Start by opening ``/etc/yum.repos.d/cloudstack.repo`` on any
+systems that have CloudStack packages installed.
+
+This file should have content similar to the following:
+
+.. parsed-literal::
+
+ [apache-cloudstack]
+ name=Apache CloudStack
+ baseurl=http://download.cloudstack.org/centos/6/4.10/
+ enabled=1
+ gpgcheck=0
+
+If you are using the community provided package repository, change
+the base url to ``http://download.cloudstack.org/centos/$releasever/|version|/``.
+
+Setup the GPG public key if you wish to enable ``gpgcheck=1``:
+
+.. parsed-literal::
+
+ rpm --import http://download.cloudstack.org/RPM-GPG-KEY
+
+
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Now that you have the repository configured, it's time to upgrade the
+ ``cloudstack-management``.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-usage
+
+.. _upg_hyp_411:
+
+Hypervisor: XenServer
+---------------------
+
+**(XenServer only)** Copy vhd-utils file on CloudStack management servers.
+Copy the file `vhd-utils <http://download.cloudstack.org/tools/vhd-util>`_
+to ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``.
+
+.. parsed-literal::
+
+ wget -P /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver \
+ http://download.cloudstack.org/tools/vhd-util
+
+
+Hypervisor: VMware
+------------------
+
+.. warning::
+ For VMware hypervisor CloudStack management server packages must be
+ build using "noredist". Refer to :ref:`building-noredist`.
+
+**(VMware only)** Additional steps are required for each VMware cluster.
+These steps will not affect running guests in the cloud. These steps
+are required only for clouds using VMware clusters:
+
+#. Stop the Management Server:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. Generate the encrypted equivalent of your vCenter password:
+
+ .. parsed-literal::
+
+ $ java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.2.jar org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh input="_your_vCenter_password_" password="`cat /etc/cloudstack/management/key`" verbose=false
+
+Store the output from this step, we need to add this in
+cluster\_details table and vmware\_data\_center tables in place of
+the plain text password
+
+#. Find the ID of the row of cluster\_details table that you have to
+ update:
+
+ .. parsed-literal::
+
+ $ mysql -u <username> -p<password>
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Update the plain text password with the encrypted one
+
+ .. parsed-literal::
+
+ update cloud.cluster_details set value = '_ciphertext_from_step_1_'
+ where id = _id_from_step_2_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Find the ID of the correct row of vmware\_data\_center that you
+ want to update
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+#. update the plain text password with the encrypted one:
+
+ .. parsed-literal::
+
+ update cloud.vmware_data_center set password = '_ciphertext_from_step_1_'
+ where id = _id_from_step_5_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+
+.. _kvm411:
+
+Hypervisor: KVM
+---------------
+
+KVM on Ubuntu
+^^^^^^^^^^^^^
+
+(KVM only) Additional steps are required for each KVM host. These
+steps will not affect running guests in the cloud. These steps are
+required only for clouds using KVM as hosts and only on the KVM
+hosts.
+
+#. Configure the :ref:`APT repo <apt-repo411>` as detailed above.
+
+#. Stop the running agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+
+#. Update the agent software.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Start the agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent start
+
+
+KVM on CentOS/RHEL
+^^^^^^^^^^^^^^^^^^
+For KVM hosts, upgrade the ``cloudstack-agent`` package
+
+#. Configure the :ref:`rpm-repo411` as detailed above.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Restart the agent:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+ $ sudo killall jsvc
+ $ sudo service cloudstack-agent start
+
+
+Restart management services
+---------------------------
+
+#. Now it's time to start the management server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management start
+
+#. If you use it, start the usage server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage start
diff --git a/source/upgrading/upgrade/upgrade-4.2.rst b/source/upgrading/upgrade/upgrade-4.2.rst
new file mode 100644
index 0000000..cd782cc
--- /dev/null
+++ b/source/upgrading/upgrade/upgrade-4.2.rst
@@ -0,0 +1,441 @@
+.. 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.
+
+
+.. |version_to_upgrade| replace:: 4.2.x
+
+Upgrade Instruction from |version_to_upgrade|
+=============================================
+
+This section will guide you from CloudStack |version_to_upgrade| to CloudStack
+|release|.
+
+.. include:: _upgrade_header.rst
+
+Upgrade Steps:
+
+#. Install new System-VM templates
+
+#. Backup CloudStack database (MySQL)
+
+#. Upgrade CloudStack management server(s)
+
+#. Update hypervisors specific dependencies
+
+#. Restart System-VMs and Virtual-Routers
+
+
+Packages repository
+-------------------
+
+Most users of CloudStack manage the installation and upgrades of
+CloudStack with one of Linux's predominant package systems, RPM or
+APT. This guide assumes you'll be using RPM and Yum (for Red Hat
+Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu).
+
+Create RPM or Debian packages (as appropriate) and a repository from
+the |release| source, or check the Apache CloudStack downloads page at
+http://cloudstack.apache.org/downloads.html
+for package repositories supplied by community members. You will need
+them for :ref:`ubuntu42` or :ref:`rhel42` and :ref:`kvm42` hosts upgrade.
+
+Instructions for creating packages from the CloudStack source are in the
+`CloudStack Installation Guide`_.
+
+.. include:: _sysvm_templates.rst
+
+
+Database Preparation
+--------------------
+
+Backup current database
+
+#. Stop your management server or servers. Run this on all management
+ server hosts:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. If you are running a usage server or usage servers, stop those as well:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage stop
+
+#. Make a backup of your MySQL database. If you run into any issues or
+ need to roll back the upgrade, this will assist in debugging or
+ restoring your existing environment. You'll be prompted for your
+ password.
+
+ .. parsed-literal::
+
+ $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql
+ $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql
+
+
+#. **(KVM Only)** If primary storage of type local storage is in use, the
+ path for this storage needs to be verified to ensure it passes new
+ validation. Check local storage by querying the cloud.storage\_pool
+ table:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'"
+
+ If local storage paths are found to have a trailing forward slash,
+ remove it:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"';
+
+
+.. _ubuntu42:
+
+Management Server Ubuntu
+------------------------
+
+If you are using Ubuntu, follow this procedure to upgrade your packages. If
+not, skip to step :ref:`rhel42`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ APT repository, substitute your own URL for the ones used in these examples.
+
+The first order of business will be to change the sources list for
+each system with CloudStack packages. This means all management
+servers, and any hosts that have the KVM agent. (No changes should
+be necessary for hosts that are running VMware or Xen.)
+
+.. _apt-repo42:
+
+.. include:: _java_8_ubuntu.rst
+
+CloudStack apt repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Start by opening ``/etc/apt/sources.list.d/cloudstack.list`` on
+any systems that have CloudStack packages installed.
+
+This file should have one line, which contains:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.2
+
+We'll change it to point to the new package repository:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.8
+
+Setup the public key for the above repository:
+
+.. parsed-literal::
+
+ wget -qO - http://download.cloudstack.org/release.asc | sudo apt-key add -
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Now update your apt package list:
+
+ .. parsed-literal::
+
+ $ sudo apt-get update
+
+#. Now that you have the repository configured, it's time to upgrade
+ the ``cloudstack-management`` package.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-usage
+
+
+.. _rhel42:
+
+Management Server CentOS/RHEL
+-----------------------------
+
+If you are using CentOS or RHEL, follow this procedure to upgrade your
+packages. If not, skip to hypervisors section :ref:`upg_hyp_42`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ yum repository, substitute your own URL for the ones used in these examples.
+
+.. include:: _mysql_connector.rst
+
+
+.. _rpm-repo42:
+
+CloustStack RPM repository
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The first order of business will be to change the yum repository
+for each system with CloudStack packages. This means all
+management servers, and any hosts that have the KVM agent.
+
+(No changes should be necessary for hosts that are running VMware or Xen.)
+
+Start by opening ``/etc/yum.repos.d/cloudstack.repo`` on any
+systems that have CloudStack packages installed.
+
+This file should have content similar to the following:
+
+.. parsed-literal::
+
+ [apache-cloudstack]
+ name=Apache CloudStack
+ baseurl=http://download.cloudstack.org/rhel/4.2/
+ enabled=1
+ gpgcheck=0
+
+If you are using the community provided package repository, change
+the baseurl to ``http://download.cloudstack.org/centos/6/4.8/``.
+
+Setup the GPG public key if you wish to enable ``gpgcheck=1``:
+
+.. parsed-literal::
+
+ rpm --import http://download.cloudstack.org/RPM-GPG-KEY
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Remove the deprecated dependency for awsapi.
+
+ .. parsed-literal::
+
+ $ sudo rpm -e --nodeps cloudstack-awsapi
+
+#. Now that you have the repository configured, it's time to upgrade the
+ ``cloudstack-management``.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-usage
+
+.. _upg_hyp_42:
+
+Hypervisor: Xen/XenServer
+-------------------------
+
+**(XenServer only)** Copy vhd-utils file on CloudStack management servers.
+Copy the file `vhd-utils <http://download.cloudstack.org/tools/vhd-util>`_
+to ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``.
+
+.. parsed-literal::
+
+ wget -P /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver \
+ http://download.cloudstack.org/tools/vhd-util
+
+.. include:: _xenserver_upg.rst
+
+
+Hypervisor: VMware
+------------------
+
+.. warning::
+ For VMware hypervisor CloudStack management server packages must be
+ build using "noredist". Refer to :ref:`building-noredist`
+
+**(VMware only)** Additional steps are required for each VMware cluster.
+These steps will not affect running guests in the cloud. These steps
+are required only for clouds using VMware clusters:
+
+#. Stop the Management Server:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. Generate the encrypted equivalent of your vCenter password:
+
+ .. parsed-literal::
+
+ $ java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.2.jar org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh input="_your_vCenter_password_" password="`cat /etc/cloudstack/management/key`" verbose=false
+
+ Store the output from this step, we need to add this in
+ cluster\_details table and vmware\_data\_center tables in place of
+ the plain text password
+
+#. Find the ID of the row of cluster\_details table that you have to update:
+
+ .. parsed-literal::
+
+ $ mysql -u <username> -p<password>
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Update the plain text password with the encrypted one
+
+ .. parsed-literal::
+
+ update cloud.cluster_details set value = '_ciphertext_from_step_1_' where id = _id_from_step_2_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Find the ID of the correct row of vmware\_data\_center that you
+ want to update
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+#. Update the plain text password with the encrypted one:
+
+ .. parsed-literal::
+
+ update cloud.vmware_data_center set password = '_ciphertext_from_step_1_' where id = _id_from_step_5_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+
+.. _kvm42:
+
+Hypervisor: KVM
+---------------
+
+
+KVM on Ubuntu
+^^^^^^^^^^^^^
+
+(KVM only) Additional steps are required for each KVM host. These
+steps will not affect running guests in the cloud. These steps are
+required only for clouds using KVM as hosts and only on the KVM
+hosts.
+
+#. Configure the :ref:`APT repo <apt-repo42>` as detailed above.
+
+#. Stop the running agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+
+#. Update the agent software.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Start the agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent start
+
+
+KVM on CentOS/RHEL
+^^^^^^^^^^^^^^^^^^
+For KVM hosts, upgrade the ``cloudstack-agent`` package
+
+#. Configure the :ref:`rpm-repo42` as detailed above.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Restart the agent:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+ $ sudo killall jsvc
+ $ sudo service cloudstack-agent start
+
+
+Restart management services
+---------------------------
+
+#. Now it's time to start the management server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management start
+
+#. If you use it, start the usage server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage start
+
+
+Settings Changes
+----------------
+
+After upgrading to 4.2 and later, Settings ``mem.overporvisioning.factor`` and
+``cpu.overporvisioning.factor`` are now at the cluster level and be set to 1
+which is the default.
+
+If Global Settings ``mem.overporvisioning.factor`` and
+``cpu.overporvisioning.factor`` have been changed prior the upgrade to 4.2 and
+later, the upgrade process will be reset them to 1. Values can be changed by
+editing clusters settings.
+
+All clusters created after the upgrade will get created with the Global Settings
+values for ``mem.overporvisioning.factor`` and ``cpu.overporvisioning.factor``.
+
+
+.. _upg-sysvm42:
+
+System-VMs and Virtual-Routers
+------------------------------
+
+.. include:: _sysvm_restart.rst
diff --git a/source/upgrading/upgrade/upgrade-4.3.rst b/source/upgrading/upgrade/upgrade-4.3.rst
new file mode 100644
index 0000000..491cc19
--- /dev/null
+++ b/source/upgrading/upgrade/upgrade-4.3.rst
@@ -0,0 +1,430 @@
+.. 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.
+
+
+.. |version_to_upgrade| replace:: 4.3.x
+
+Upgrade Instruction from |version_to_upgrade|
+=============================================
+
+This section will guide you from CloudStack |version_to_upgrade| to CloudStack
+|release|.
+
+Any steps that are hypervisor-specific will be called out with a note.
+
+We recommend reading through this section once or twice before beginning
+your upgrade procedure, and working through it on a test system before
+working on a production system.
+
+.. note::
+ The following upgrade instructions should be performed regardless of
+ hypervisor type.
+
+Upgrade Steps:
+
+#. Backup CloudStack database (MySQL)
+#. Install new systemvm template
+#. Add package repository for MySQL connector
+#. Upgrade CloudStack management server(s)
+#. Update hypervisors specific dependencies
+
+
+Packages repository
+-------------------
+
+Most users of CloudStack manage the installation and upgrades of
+CloudStack with one of Linux's predominant package systems, RPM or
+APT. This guide assumes you'll be using RPM and Yum (for Red Hat
+Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu).
+
+Create RPM or Debian packages (as appropriate) and a repository from
+the |release| source, or check the Apache CloudStack downloads page at
+http://cloudstack.apache.org/downloads.html
+for package repositories supplied by community members. You will need
+them for :ref:`ubuntu43` or :ref:`rhel43` and :ref:`kvm43` hosts upgrade.
+
+Instructions for creating packages from the CloudStack source are in the
+`CloudStack Installation Guide`_.
+
+.. include:: _sysvm_templates.rst
+
+
+Database Preparation
+--------------------
+
+Backup current database
+
+#. Stop your management server or servers. Run this on all management
+ server hosts:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. If you are running a usage server or usage servers, stop those as well:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage stop
+
+#. Make a backup of your MySQL database. If you run into any issues or
+ need to roll back the upgrade, this will assist in debugging or
+ restoring your existing environment. You'll be prompted for your
+ password.
+
+ .. parsed-literal::
+
+ $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql
+ $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql
+
+#. **(KVM Only)** If primary storage of type local storage is in use, the
+ path for this storage needs to be verified to ensure it passes new
+ validation. Check local storage by querying the cloud.storage\_pool
+ table:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'"
+
+ If local storage paths are found to have a trailing forward slash,
+ remove it:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"';
+
+
+.. _ubuntu43:
+
+Management Server on Ubuntu
+---------------------------
+
+If you are using Ubuntu, follow this procedure to upgrade your packages. If
+not, skip to step :ref:`rhel43`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ APT repository, substitute your own URL for the ones used in these examples.
+
+The first order of business will be to change the sources list for
+each system with CloudStack packages. This means all management
+servers, and any hosts that have the KVM agent. (No changes should
+be necessary for hosts that are running VMware or Xen.)
+
+
+.. _apt-repo43:
+
+.. include:: _java_8_ubuntu.rst
+
+CloudStack apt repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Start by opening ``/etc/apt/sources.list.d/cloudstack.list`` on
+any systems that have CloudStack packages installed.
+
+This file should have one line, which contains:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.3
+
+We'll change it to point to the new package repository:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.9
+
+Setup the public key for the above repository:
+
+.. parsed-literal::
+
+ wget -qO - http://download.cloudstack.org/release.asc | sudo apt-key add -
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Now update your apt package list:
+
+ .. parsed-literal::
+
+ $ sudo apt-get update
+
+#. Now that you have the repository configured, it's time to upgrade
+ the ``cloudstack-management`` package.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-usage
+
+
+.. _rhel43:
+
+Management Server on CentOS/RHEL
+--------------------------------
+
+If you are using CentOS or RHEL, follow this procedure to upgrade your
+packages. If not, skip to hypervisors section :ref:`upg_hyp_43`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ yum repository, substitute your own URL for the ones used in these examples.
+
+.. include:: _mysql_connector.rst
+
+
+.. _rpm-repo43:
+
+CloudStack RPM repository
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The first order of business will be to change the yum repository
+for each system with CloudStack packages. This means all
+management servers, and any hosts that have the KVM agent.
+
+(No changes should be necessary for hosts that are running VMware or Xen.)
+
+Start by opening ``/etc/yum.repos.d/cloudstack.repo`` on any
+systems that have CloudStack packages installed.
+
+This file should have content similar to the following:
+
+.. parsed-literal::
+
+ [apache-cloudstack]
+ name=Apache CloudStack
+ baseurl=http://download.cloudstack.org/rhel/4.3/
+ enabled=1
+ gpgcheck=0
+
+If you are using the community provided package repository, change
+the base url to ``http://download.cloudstack.org/centos/$releasever/4.9/``.
+
+Setup the GPG public key if you wish to enable ``gpgcheck=1``:
+
+.. parsed-literal::
+
+ rpm --import http://download.cloudstack.org/RPM-GPG-KEY
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Remove the deprecated dependency for awsapi.
+
+ .. parsed-literal::
+
+ $ sudo rpm -e --nodeps cloudstack-awsapi
+
+#. Now that you have the repository configured, it's time to upgrade the
+ ``cloudstack-management``.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-usage
+
+.. _upg_hyp_43:
+
+Hypervisor: XenServer
+---------------------
+
+**(XenServer only)** Copy vhd-utils file on CloudStack management servers.
+Copy the file `vhd-utils <http://download.cloudstack.org/tools/vhd-util>`_
+to ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``.
+
+.. parsed-literal::
+
+ wget -P /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver \
+ http://download.cloudstack.org/tools/vhd-util
+
+.. include:: _xenserver_upg.rst
+
+
+Hypervisor: VMware
+------------------
+
+.. warning::
+ For VMware hypervisor CloudStack management server packages must be
+ build using "noredist". Refer to :ref:`building-noredist`
+
+**(VMware only)** Additional steps are required for each VMware cluster.
+These steps will not affect running guests in the cloud. These steps
+are required only for clouds using VMware clusters:
+
+#. Stop the Management Server:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. Generate the encrypted equivalent of your vCenter password:
+
+ .. parsed-literal::
+
+ $ java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.2.jar org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh input="_your_vCenter_password_" password="`cat /etc/cloudstack/management/key`" verbose=false
+
+ Store the output from this step, we need to add this in
+ cluster\_details table and vmware\_data\_center tables in place of
+ the plain text password
+
+#. Find the ID of the row of cluster\_details table that you have to
+ update:
+
+ .. parsed-literal::
+
+ $ mysql -u <username> -p<password>
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Update the plain text password with the encrypted one
+
+ .. parsed-literal::
+
+ update cloud.cluster_details set value = '_ciphertext_from_step_1_' where id = _id_from_step_2_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Find the ID of the correct row of vmware\_data\_center that you
+ want to update
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+#. update the plain text password with the encrypted one:
+
+ .. parsed-literal::
+
+ update cloud.vmware_data_center set password = '_ciphertext_from_step_1_' where id = _id_from_step_5_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+
+.. _kvm43:
+
+Hypervisor: KVM
+---------------
+
+KVM on Ubuntu
+^^^^^^^^^^^^^
+
+(KVM only) Additional steps are required for each KVM host. These
+steps will not affect running guests in the cloud. These steps are
+required only for clouds using KVM as hosts and only on the KVM
+hosts.
+
+#. Configure the :ref:`APT repo <apt-repo43>` as detailed above.
+
+#. Stop the running agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+
+#. Update the agent software.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Start the agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent start
+
+
+KVM on CentOS/RHEL
+^^^^^^^^^^^^^^^^^^
+
+For KVM hosts, upgrade the ``cloudstack-agent`` package
+
+#. Configure the :ref:`rpm-repo43` as detailed above.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Restart the agent:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+ $ sudo killall jsvc
+ $ sudo service cloudstack-agent start
+
+
+Restart management services
+---------------------------
+
+#. Now it's time to start the management server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management start
+
+#. If you use it, start the usage server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage start
+
+
+.. _upg-sysvm43:
+
+System-VMs and Virtual-Routers
+------------------------------
+
+.. include:: _sysvm_restart.rst
diff --git a/source/upgrading/upgrade/upgrade-4.4.rst b/source/upgrading/upgrade/upgrade-4.4.rst
new file mode 100644
index 0000000..67f1223
--- /dev/null
+++ b/source/upgrading/upgrade/upgrade-4.4.rst
@@ -0,0 +1,443 @@
+.. 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.
+
+
+.. |version_to_upgrade| replace:: 4.4.x
+
+Upgrade Instruction from |version_to_upgrade|
+=============================================
+
+This section will guide you from CloudStack |version_to_upgrade| to CloudStack
+|release|.
+
+Any steps that are hypervisor-specific will be called out with a note.
+
+We recommend reading through this section once or twice before beginning
+your upgrade procedure, and working through it on a test system before
+working on a production system.
+
+.. note::
+ The following upgrade instructions should be performed regardless of
+ hypervisor type.
+
+Upgrade Steps:
+
+#. Backup CloudStack database (MySQL)
+#. Install new systemvm template
+#. Add package repository for MySQL connector
+#. Upgrade CloudStack management server(s)
+#. Update hypervisors specific dependencies
+
+
+Packages repository
+-------------------
+
+Most users of CloudStack manage the installation and upgrades of
+CloudStack with one of Linux's predominant package systems, RPM or
+APT. This guide assumes you'll be using RPM and Yum (for Red Hat
+Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu).
+
+Create RPM or Debian packages (as appropriate) and a repository from
+the |release| source, or check the Apache CloudStack downloads page at
+http://cloudstack.apache.org/downloads.html
+for package repositories supplied by community members. You will need
+them for :ref:`ubuntu44` or :ref:`rhel44` and :ref:`kvm44` hosts upgrade.
+
+Instructions for creating packages from the CloudStack source are in the
+`CloudStack Installation Guide`_.
+
+.. include:: _sysvm_templates.rst
+
+
+Database Preparation
+--------------------
+
+Backup current database
+
+#. Stop your management server or servers. Run this on all management
+ server hosts:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. If you are running a usage server or usage servers, stop those as well:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage stop
+
+#. Make a backup of your MySQL database. If you run into any issues or
+ need to roll back the upgrade, this will assist in debugging or
+ restoring your existing environment. You'll be prompted for your
+ password.
+
+ .. parsed-literal::
+
+ $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql
+ $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql
+
+#. **(KVM Only)** If primary storage of type local storage is in use, the
+ path for this storage needs to be verified to ensure it passes new
+ validation. Check local storage by querying the cloud.storage\_pool
+ table:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'"
+
+ If local storage paths are found to have a trailing forward slash,
+ remove it:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"';
+
+
+.. _ubuntu44:
+
+Management Server on Ubuntu
+---------------------------
+
+If you are using Ubuntu, follow this procedure to upgrade your packages. If
+not, skip to step :ref:`rhel44`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ APT repository, substitute your own URL for the ones used in these examples.
+
+The first order of business will be to change the sources list for
+each system with CloudStack packages. This means all management
+servers, and any hosts that have the KVM agent. (No changes should
+be necessary for hosts that are running VMware or Xen.)
+
+
+.. _apt-repo44:
+
+.. include:: _java_8_ubuntu.rst
+
+CloudStack apt repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+ Start by opening ``/etc/apt/sources.list.d/cloudstack.list`` on
+ any systems that have CloudStack packages installed.
+
+ This file should have one line, which contains:
+
+ .. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.4
+
+ We'll change it to point to the new package repository:
+
+ .. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.9
+
+ Setup the public key for the above repository:
+
+ .. parsed-literal::
+
+ wget -qO - http://download.cloudstack.org/release.asc | sudo apt-key add -
+
+ If you're using your own package repository, change this line to
+ read as appropriate for your |version| repository.
+
+#. Now update your apt package list:
+
+ .. parsed-literal::
+
+ $ sudo apt-get update
+
+#. Now that you have the repository configured, it's time to upgrade
+ the ``cloudstack-management`` package.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-usage
+
+
+.. _rhel44:
+
+Management Server on CentOS/RHEL
+--------------------------------
+
+If you are using CentOS or RHEL, follow this procedure to upgrade your
+packages. If not, skip to hypervisors section :ref:`upg_hyp_44`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ yum repository, substitute your own URL for the ones used in these examples.
+
+.. include:: _mysql_connector.rst
+
+
+.. _rpm-repo44:
+
+CloudStack RPM repository
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The first order of business will be to change the yum repository
+for each system with CloudStack packages. This means all
+management servers, and any hosts that have the KVM agent.
+
+(No changes should be necessary for hosts that are running VMware
+or Xen.)
+
+Start by opening ``/etc/yum.repos.d/cloudstack.repo`` on any
+systems that have CloudStack packages installed.
+
+This file should have content similar to the following:
+
+.. parsed-literal::
+
+ [apache-cloudstack]
+ name=Apache CloudStack
+ baseurl=http://download.cloudstack.org/rhel/4.4/
+ enabled=1
+ gpgcheck=0
+
+If you are using the community provided package repository, change
+the base url to ``http://download.cloudstack.org/centos/$releasever/4.9/``.
+
+Setup the GPG public key if you wish to enable ``gpgcheck=1``:
+
+.. parsed-literal::
+
+ rpm --import http://download.cloudstack.org/RPM-GPG-KEY
+
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Remove the deprecated dependency for awsapi.
+
+ .. parsed-literal::
+
+ $ sudo rpm -e --nodeps cloudstack-awsapi
+
+#. Now that you have the repository configured, it's time to upgrade the
+ ``cloudstack-management``.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-usage
+
+.. _upg_hyp_44:
+
+Hypervisor: XenServer
+---------------------
+
+**(XenServer only)** Copy vhd-utils file on CloudStack management servers.
+Copy the file `vhd-utils <http://download.cloudstack.org/tools/vhd-util>`_
+to ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``.
+
+.. parsed-literal::
+
+ wget -P /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver \
+ http://download.cloudstack.org/tools/vhd-util
+
+.. include:: _xenserver_upg.rst
+
+
+Hypervisor: VMware
+------------------
+
+.. warning::
+ For VMware hypervisor CloudStack management server packages must be
+ build using "noredist". Refer to :ref:`building-noredist`
+
+**(VMware only)** Additional steps are required for each VMware cluster.
+These steps will not affect running guests in the cloud. These steps
+are required only for clouds using VMware clusters:
+
+#. Stop the Management Server:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. Generate the encrypted equivalent of your vCenter password:
+
+ .. parsed-literal::
+
+ $ java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.2.jar org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh input="_your_vCenter_password_" password="`cat /etc/cloudstack/management/key`" verbose=false
+
+ Store the output from this step, we need to add this in
+ cluster\_details table and vmware\_data\_center tables in place of
+ the plain text password
+
+#. Find the ID of the row of cluster\_details table that you have to
+ update:
+
+ .. parsed-literal::
+
+ $ mysql -u <username> -p<password>
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Update the plain text password with the encrypted one
+
+ .. parsed-literal::
+
+ update cloud.cluster_details set value = '_ciphertext_from_step_1_' where id = _id_from_step_2_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Find the ID of the correct row of vmware\_data\_center that you
+ want to update
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+#. update the plain text password with the encrypted one:
+
+ .. parsed-literal::
+
+ update cloud.vmware_data_center set password = '_ciphertext_from_step_1_'
+ where id = _id_from_step_5_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+
+.. _kvm44:
+
+Hypervisor: KVM
+---------------
+
+KVM on Ubuntu
+^^^^^^^^^^^^^
+
+(KVM only) Additional steps are required for each KVM host. These
+steps will not affect running guests in the cloud. These steps are
+required only for clouds using KVM as hosts and only on the KVM
+hosts.
+
+#. Configure the :ref:`APT repo <apt-repo44>` as detailed above.
+
+#. Stop the running agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+
+#. Update the agent software.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Start the agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent start
+
+
+KVM on CentOS/RHEL
+^^^^^^^^^^^^^^^^^^
+For KVM hosts, upgrade the ``cloudstack-agent`` package
+
+#. Configure the :ref:`rpm-repo44` as detailed above.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Restart the agent:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+ $ sudo killall jsvc
+ $ sudo service cloudstack-agent start
+
+
+Restart management services
+---------------------------
+#. If upgrading fresh installation of 4.4.0
+
+ If you are upgrading fresh installation of CloudStack 4.4.0, the following MySQL
+ command must be executed before restarting the management server. If the system
+ was running pre 4.4 and then upgraded to 4.4.0, the MySQL command is not required.
+ Refer to: `CLOUDSTACK-7813 <https://issues.apache.org/jira/browse/CLOUDSTACK-7813>`_
+
+ .. sourcecode:: mysql
+
+ use cloud;
+ ALTER TABLE `snapshot_policy` ADD `display` TINYINT( 1 ) NOT NULL DEFAULT '1';
+
+#. Now it's time to start the management server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management start
+
+#. If you use it, start the usage server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage start
+
+
+.. _upg-sysvm44:
+
+System-VMs and Virtual-Routers
+------------------------------
+
+.. include:: _sysvm_restart.rst
diff --git a/source/upgrading/upgrade/upgrade-4.5.rst b/source/upgrading/upgrade/upgrade-4.5.rst
new file mode 100644
index 0000000..4bde28c
--- /dev/null
+++ b/source/upgrading/upgrade/upgrade-4.5.rst
@@ -0,0 +1,434 @@
+.. 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.
+
+
+.. |version_to_upgrade| replace:: 4.5.x
+
+Upgrade Instruction from |version_to_upgrade|
+=============================================
+
+This section will guide you from CloudStack |version_to_upgrade| to CloudStack
+|release|.
+
+Any steps that are hypervisor-specific will be called out with a note.
+
+We recommend reading through this section once or twice before beginning
+your upgrade procedure, and working through it on a test system before
+working on a production system.
+
+.. note::
+ The following upgrade instructions should be performed regardless of
+ hypervisor type.
+
+Upgrade Steps:
+
+#. Backup CloudStack database (MySQL)
+#. Install new systemvm template
+#. Add package repository for MySQL connector
+#. Upgrade CloudStack management server(s)
+#. Update hypervisors specific dependencies
+
+
+Packages repository
+-------------------
+
+Most users of CloudStack manage the installation and upgrades of
+CloudStack with one of Linux's predominant package systems, RPM or
+APT. This guide assumes you'll be using RPM and Yum (for Red Hat
+Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu).
+
+Create RPM or Debian packages (as appropriate) and a repository from
+the |release| source, or check the Apache CloudStack downloads page at
+http://cloudstack.apache.org/downloads.html
+for package repositories supplied by community members. You will need
+them for :ref:`ubuntu45` or :ref:`rhel45` and :ref:`kvm45` hosts upgrade.
+
+Instructions for creating packages from the CloudStack source are in the
+`CloudStack Installation Guide`_.
+
+.. include:: _sysvm_templates.rst
+
+
+Database Preparation
+--------------------
+
+Backup current database
+
+#. Stop your management server or servers. Run this on all management
+ server hosts:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. If you are running a usage server or usage servers, stop those as well:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage stop
+
+#. Make a backup of your MySQL database. If you run into any issues or
+ need to roll back the upgrade, this will assist in debugging or
+ restoring your existing environment. You'll be prompted for your
+ password.
+
+ .. parsed-literal::
+
+ $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql
+ $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql
+
+#. **(KVM Only)** If primary storage of type local storage is in use, the
+ path for this storage needs to be verified to ensure it passes new
+ validation. Check local storage by querying the cloud.storage\_pool
+ table:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'"
+
+ If local storage paths are found to have a trailing forward slash,
+ remove it:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"';
+
+
+.. _ubuntu45:
+
+Management Server on Ubuntu
+---------------------------
+
+If you are using Ubuntu, follow this procedure to upgrade your packages. If
+not, skip to step :ref:`rhel45`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ APT repository, substitute your own URL for the ones used in these examples.
+
+The first order of business will be to change the sources list for
+each system with CloudStack packages. This means all management
+servers, and any hosts that have the KVM agent. (No changes should
+be necessary for hosts that are running VMware or Xen.)
+
+
+.. _apt-repo45:
+
+.. include:: _java_8_ubuntu.rst
+
+CloudStack apt repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Start by opening ``/etc/apt/sources.list.d/cloudstack.list`` on
+any systems that have CloudStack packages installed.
+
+This file should have one line, which contains:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.5
+
+We'll change it to point to the new package repository:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.9
+
+Setup the public key for the above repository:
+
+.. parsed-literal::
+
+ wget -qO - http://download.cloudstack.org/release.asc | sudo apt-key add -
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Now update your apt package list:
+
+ .. parsed-literal::
+
+ $ sudo apt-get update
+
+#. Now that you have the repository configured, it's time to upgrade
+ the ``cloudstack-management`` package.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-usage
+
+
+.. _rhel45:
+
+Management Server on CentOS/RHEL
+--------------------------------
+
+If you are using CentOS or RHEL, follow this procedure to upgrade your
+packages. If not, skip to hypervisors section :ref:`upg_hyp_45`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ yum repository, substitute your own URL for the ones used in these examples.
+
+.. include:: _mysql_connector.rst
+
+
+.. _rpm-repo45:
+
+CloudStack RPM repository
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The first order of business will be to change the yum repository
+for each system with CloudStack packages. This means all
+management servers, and any hosts that have the KVM agent.
+
+(No changes should be necessary for hosts that are running VMware
+or Xen.)
+
+Start by opening ``/etc/yum.repos.d/cloudstack.repo`` on any
+systems that have CloudStack packages installed.
+
+This file should have content similar to the following:
+
+.. parsed-literal::
+
+ [apache-cloudstack]
+ name=Apache CloudStack
+ baseurl=http://download.cloudstack.org/rhel/4.5/
+ enabled=1
+ gpgcheck=0
+
+If you are using the community provided package repository, change
+the base url to ``http://download.cloudstack.org/centos/$releasever/4.9/``.
+
+Setup the GPG public key if you wish to enable ``gpgcheck=1``:
+
+.. parsed-literal::
+
+ rpm --import http://download.cloudstack.org/RPM-GPG-KEY
+
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Remove the deprecated dependency for awsapi.
+
+ .. parsed-literal::
+
+ $ sudo rpm -e --nodeps cloudstack-awsapi
+
+#. Now that you have the repository configured, it's time to upgrade the
+ ``cloudstack-management``.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-usage
+
+.. _upg_hyp_45:
+
+Hypervisor: XenServer
+---------------------
+
+**(XenServer only)** Copy vhd-utils file on CloudStack management servers.
+Copy the file `vhd-utils <http://download.cloudstack.org/tools/vhd-util>`_
+to ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``.
+
+.. parsed-literal::
+
+ wget -P /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver \
+ http://download.cloudstack.org/tools/vhd-util
+
+
+Hypervisor: VMware
+------------------
+
+.. warning::
+ For VMware hypervisor CloudStack management server packages must be
+ build using "noredist". Refer to :ref:`building-noredist`
+
+**(VMware only)** Additional steps are required for each VMware cluster.
+These steps will not affect running guests in the cloud. These steps
+are required only for clouds using VMware clusters:
+
+#. Stop the Management Server:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. Generate the encrypted equivalent of your vCenter password:
+
+ .. parsed-literal::
+
+ $ java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.2.jar org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh input="_your_vCenter_password_" password="`cat /etc/cloudstack/management/key`" verbose=false
+
+Store the output from this step, we need to add this in
+cluster\_details table and vmware\_data\_center tables in place of
+the plain text password
+
+#. Find the ID of the row of cluster\_details table that you have to
+ update:
+
+ .. parsed-literal::
+
+ $ mysql -u <username> -p<password>
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Update the plain text password with the encrypted one
+
+ .. parsed-literal::
+
+ update cloud.cluster_details set value = '_ciphertext_from_step_1_'
+ where id = _id_from_step_2_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Find the ID of the correct row of vmware\_data\_center that you
+ want to update
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+#. update the plain text password with the encrypted one:
+
+ .. parsed-literal::
+
+ update cloud.vmware_data_center set password = '_ciphertext_from_step_1_'
+ where id = _id_from_step_5_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+
+.. _kvm45:
+
+Hypervisor: KVM
+---------------
+
+KVM on Ubuntu
+^^^^^^^^^^^^^
+
+(KVM only) Additional steps are required for each KVM host. These
+steps will not affect running guests in the cloud. These steps are
+required only for clouds using KVM as hosts and only on the KVM
+hosts.
+
+#. Configure the :ref:`APT repo <apt-repo45>` as detailed above.
+
+#. Stop the running agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+
+#. Update the agent software.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Start the agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent start
+
+
+KVM on CentOS/RHEL
+^^^^^^^^^^^^^^^^^^
+For KVM hosts, upgrade the ``cloudstack-agent`` package
+
+#. Configure the :ref:`rpm-repo45` as detailed above.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Restart the agent:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+ $ sudo killall jsvc
+ $ sudo service cloudstack-agent start
+
+
+Restart management services
+---------------------------
+
+#. Now it's time to start the management server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management start
+
+#. If you use it, start the usage server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage start
+
+
+.. _upg-sysvm45:
+
+System-VMs and Virtual-Routers
+------------------------------
+
+.. include:: _sysvm_restart.rst
+
+
+
diff --git a/source/upgrading/upgrade/upgrade-4.6.rst b/source/upgrading/upgrade/upgrade-4.6.rst
new file mode 100644
index 0000000..e308b04
--- /dev/null
+++ b/source/upgrading/upgrade/upgrade-4.6.rst
@@ -0,0 +1,424 @@
+.. 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.
+
+
+.. |version_to_upgrade| replace:: 4.6.x
+
+Upgrade Instruction from |version_to_upgrade|
+=============================================
+
+This section will guide you from CloudStack |version_to_upgrade| to CloudStack
+|release|.
+
+Any steps that are hypervisor-specific will be called out with a note.
+
+We recommend reading through this section once or twice before beginning
+your upgrade procedure, and working through it on a test system before
+working on a production system.
+
+.. note::
+ The following upgrade instructions should be performed regardless of
+ hypervisor type.
+
+Upgrade Steps:
+
+#. Backup CloudStack database (MySQL)
+#. Add package repository for MySQL connector
+#. Upgrade CloudStack management server(s)
+#. Update hypervisors specific dependencies
+
+
+Packages repository
+-------------------
+
+Most users of CloudStack manage the installation and upgrades of
+CloudStack with one of Linux's predominant package systems, RPM or
+APT. This guide assumes you'll be using RPM and Yum (for Red Hat
+Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu).
+
+Create RPM or Debian packages (as appropriate) and a repository from
+the |release| source, or check the Apache CloudStack downloads page at
+http://cloudstack.apache.org/downloads.html
+for package repositories supplied by community members. You will need
+them for :ref:`ubuntu46` or :ref:`rhel46` and :ref:`kvm46` hosts upgrade.
+
+Instructions for creating packages from the CloudStack source are in the
+`CloudStack Installation Guide`_.
+
+.. include:: _sysvm_templates.rst
+
+Database Preparation
+--------------------
+
+Backup current database
+
+#. Stop your management server or servers. Run this on all management
+ server hosts:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. If you are running a usage server or usage servers, stop those as well:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage stop
+
+#. Make a backup of your MySQL database. If you run into any issues or
+ need to roll back the upgrade, this will assist in debugging or
+ restoring your existing environment. You'll be prompted for your
+ password.
+
+ .. parsed-literal::
+
+ $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql
+ $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql
+
+#. **(KVM Only)** If primary storage of type local storage is in use, the
+ path for this storage needs to be verified to ensure it passes new
+ validation. Check local storage by querying the cloud.storage\_pool
+ table:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'"
+
+ If local storage paths are found to have a trailing forward slash,
+ remove it:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"';
+
+
+.. _ubuntu46:
+
+Management Server on Ubuntu
+---------------------------
+
+If you are using Ubuntu, follow this procedure to upgrade your packages. If
+not, skip to step :ref:`rhel46`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ APT repository, substitute your own URL for the ones used in these examples.
+
+The first order of business will be to change the sources list for
+each system with CloudStack packages. This means all management
+servers, and any hosts that have the KVM agent. (No changes should
+be necessary for hosts that are running VMware or Xen.)
+
+
+.. _apt-repo46:
+
+.. include:: _java_8_ubuntu.rst
+
+CloudStack apt repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Start by opening ``/etc/apt/sources.list.d/cloudstack.list`` on
+any systems that have CloudStack packages installed.
+
+This file should have one line, which contains:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.6
+
+We'll change it to point to the new package repository:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.9
+
+Setup the public key for the above repository:
+
+.. parsed-literal::
+
+ wget -qO - http://download.cloudstack.org/release.asc | sudo apt-key add -
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Now update your apt package list:
+
+ .. parsed-literal::
+
+ $ sudo apt-get update
+
+#. Now that you have the repository configured, it's time to upgrade
+ the ``cloudstack-management`` package.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-usage
+
+
+.. _rhel46:
+
+Management Server on CentOS/RHEL
+--------------------------------
+
+If you are using CentOS or RHEL, follow this procedure to upgrade your
+packages. If not, skip to hypervisors section :ref:`upg_hyp_46`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ yum repository, substitute your own URL for the ones used in these examples.
+
+.. include:: _mysql_connector.rst
+
+
+.. _rpm-repo46:
+
+CloudStack RPM repository
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The first order of business will be to change the yum repository
+for each system with CloudStack packages. This means all
+management servers, and any hosts that have the KVM agent.
+
+(No changes should be necessary for hosts that are running VMware
+or Xen.)
+
+Start by opening ``/etc/yum.repos.d/cloudstack.repo`` on any
+systems that have CloudStack packages installed.
+
+This file should have content similar to the following:
+
+.. parsed-literal::
+
+ [apache-cloudstack]
+ name=Apache CloudStack
+ baseurl=http://download.cloudstack.org/rhel/4.6/
+ enabled=1
+ gpgcheck=0
+
+If you are using the community provided package repository, change
+the base url to ``http://download.cloudstack.org/centos/$releasever/4.9/``.
+
+Setup the GPG public key if you wish to enable ``gpgcheck=1``:
+
+.. parsed-literal::
+
+ rpm --import http://download.cloudstack.org/RPM-GPG-KEY
+
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Remove the deprecated dependency for awsapi.
+
+ .. parsed-literal::
+
+ $ sudo rpm -e --nodeps cloudstack-awsapi
+
+#. Now that you have the repository configured, it's time to upgrade the
+ ``cloudstack-management``.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-usage
+
+.. _upg_hyp_46:
+
+Hypervisor: XenServer
+---------------------
+
+**(XenServer only)** Copy vhd-utils file on CloudStack management servers.
+Copy the file `vhd-utils <http://download.cloudstack.org/tools/vhd-util>`_
+to ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``.
+
+.. parsed-literal::
+
+ wget -P /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver \
+ http://download.cloudstack.org/tools/vhd-util
+
+
+Hypervisor: VMware
+------------------
+
+.. warning::
+ For VMware hypervisor CloudStack management server packages must be
+ build using "noredist". Refer to :ref:`building-noredist`
+
+**(VMware only)** Additional steps are required for each VMware cluster.
+These steps will not affect running guests in the cloud. These steps
+are required only for clouds using VMware clusters:
+
+#. Stop the Management Server:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. Generate the encrypted equivalent of your vCenter password:
+
+ .. parsed-literal::
+
+ $ java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.2.jar org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh input="_your_vCenter_password_" password="`cat /etc/cloudstack/management/key`" verbose=false
+
+Store the output from this step, we need to add this in
+cluster\_details table and vmware\_data\_center tables in place of
+the plain text password
+
+#. Find the ID of the row of cluster\_details table that you have to
+ update:
+
+ .. parsed-literal::
+
+ $ mysql -u <username> -p<password>
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Update the plain text password with the encrypted one
+
+ .. parsed-literal::
+
+ update cloud.cluster_details set value = '_ciphertext_from_step_1_'
+ where id = _id_from_step_2_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Find the ID of the correct row of vmware\_data\_center that you
+ want to update
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+#. update the plain text password with the encrypted one:
+
+ .. parsed-literal::
+
+ update cloud.vmware_data_center set password = '_ciphertext_from_step_1_'
+ where id = _id_from_step_5_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+
+.. _kvm46:
+
+Hypervisor: KVM
+---------------
+
+KVM on Ubuntu
+^^^^^^^^^^^^^
+
+(KVM only) Additional steps are required for each KVM host. These
+steps will not affect running guests in the cloud. These steps are
+required only for clouds using KVM as hosts and only on the KVM
+hosts.
+
+#. Configure the :ref:`APT repo <apt-repo46>` as detailed above.
+
+#. Stop the running agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+
+#. Update the agent software.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Start the agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent start
+
+
+KVM on CentOS/RHEL
+^^^^^^^^^^^^^^^^^^
+For KVM hosts, upgrade the ``cloudstack-agent`` package
+
+#. Configure the :ref:`rpm-repo46` as detailed above.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Restart the agent:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+ $ sudo killall jsvc
+ $ sudo service cloudstack-agent start
+
+
+Restart management services
+---------------------------
+
+#. Now it's time to start the management server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management start
+
+#. If you use it, start the usage server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage start
+
+
+
diff --git a/source/upgrading/upgrade/upgrade-4.7.rst b/source/upgrading/upgrade/upgrade-4.7.rst
new file mode 100644
index 0000000..e94f35f
--- /dev/null
+++ b/source/upgrading/upgrade/upgrade-4.7.rst
@@ -0,0 +1,417 @@
+.. 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.
+
+
+.. |version_to_upgrade| replace:: 4.7.x
+
+Upgrade Instruction from |version_to_upgrade|
+=============================================
+
+This section will guide you from CloudStack |version_to_upgrade| to CloudStack
+|release|.
+
+Any steps that are hypervisor-specific will be called out with a note.
+
+We recommend reading through this section once or twice before beginning
+your upgrade procedure, and working through it on a test system before
+working on a production system.
+
+.. note::
+ The following upgrade instructions should be performed regardless of
+ hypervisor type.
+
+Upgrade Steps:
+
+#. Backup CloudStack database (MySQL)
+#. Add package repository for MySQL connector
+#. Upgrade CloudStack management server(s)
+#. Update hypervisors specific dependencies
+
+Packages repository
+-------------------
+
+Most users of CloudStack manage the installation and upgrades of
+CloudStack with one of Linux's predominant package systems, RPM or
+APT. This guide assumes you'll be using RPM and Yum (for Red Hat
+Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu).
+
+Create RPM or Debian packages (as appropriate) and a repository from
+the |release| source, or check the Apache CloudStack downloads page at
+http://cloudstack.apache.org/downloads.html
+for package repositories supplied by community members. You will need
+them for :ref:`ubuntu47` or :ref:`rhel47` and :ref:`kvm47` hosts upgrade.
+
+Instructions for creating packages from the CloudStack source are in the
+`CloudStack Installation Guide`_.
+
+.. include:: _sysvm_templates.rst
+
+Database Preparation
+--------------------
+
+Backup current database
+
+#. Stop your management server or servers. Run this on all management
+ server hosts:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. If you are running a usage server or usage servers, stop those as well:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage stop
+
+#. Make a backup of your MySQL database. If you run into any issues or
+ need to roll back the upgrade, this will assist in debugging or
+ restoring your existing environment. You'll be prompted for your
+ password.
+
+ .. parsed-literal::
+
+ $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql
+ $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql
+
+#. **(KVM Only)** If primary storage of type local storage is in use, the
+ path for this storage needs to be verified to ensure it passes new
+ validation. Check local storage by querying the cloud.storage\_pool
+ table:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'"
+
+ If local storage paths are found to have a trailing forward slash,
+ remove it:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"';
+
+
+.. _ubuntu47:
+
+Management Server on Ubuntu
+---------------------------
+
+If you are using Ubuntu, follow this procedure to upgrade your packages. If
+not, skip to step :ref:`rhel47`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ APT repository, substitute your own URL for the ones used in these examples.
+
+The first order of business will be to change the sources list for
+each system with CloudStack packages. This means all management
+servers, and any hosts that have the KVM agent. (No changes should
+be necessary for hosts that are running VMware or Xen.)
+
+
+.. _apt-repo47:
+
+.. include:: _java_8_ubuntu.rst
+
+CloudStack apt repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Start by opening ``/etc/apt/sources.list.d/cloudstack.list`` on
+any systems that have CloudStack packages installed.
+
+This file should have one line, which contains:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.7
+
+We'll change it to point to the new package repository:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.9
+
+Setup the public key for the above repository:
+
+.. parsed-literal::
+
+ wget -qO - http://download.cloudstack.org/release.asc | sudo apt-key add -
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Now update your apt package list:
+
+ .. parsed-literal::
+
+ $ sudo apt-get update
+
+#. Now that you have the repository configured, it's time to upgrade
+ the ``cloudstack-management`` package.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-usage
+
+
+.. _rhel47:
+
+Management Server on CentOS/RHEL
+--------------------------------
+
+If you are using CentOS or RHEL, follow this procedure to upgrade your
+packages. If not, skip to hypervisors section :ref:`upg_hyp_47`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ yum repository, substitute your own URL for the ones used in these examples.
+
+.. include:: _mysql_connector.rst
+
+
+.. _rpm-repo47:
+
+CloudStack RPM repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The first order of business will be to change the yum repository
+for each system with CloudStack packages. This means all
+management servers, and any hosts that have the KVM agent.
+
+(No changes should be necessary for hosts that are running VMware
+or Xen.)
+
+Start by opening ``/etc/yum.repos.d/cloudstack.repo`` on any
+systems that have CloudStack packages installed.
+
+This file should have content similar to the following:
+
+.. parsed-literal::
+
+ [apache-cloudstack]
+ name=Apache CloudStack
+ baseurl=http://download.cloudstack.org/rhel/4.7/
+ enabled=1
+ gpgcheck=0
+
+If you are using the community provided package repository, change
+the base url to ``http://download.cloudstack.org/centos/$releasever/4.9/``.
+
+Setup the GPG public key if you wish to enable ``gpgcheck=1``:
+
+.. parsed-literal::
+
+ rpm --import http://download.cloudstack.org/RPM-GPG-KEY
+
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Now that you have the repository configured, it's time to upgrade the
+ ``cloudstack-management``.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-usage
+
+.. _upg_hyp_47:
+
+Hypervisor: XenServer
+---------------------
+
+**(XenServer only)** Copy vhd-utils file on CloudStack management servers.
+Copy the file `vhd-utils <http://download.cloudstack.org/tools/vhd-util>`_
+to ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``.
+
+.. parsed-literal::
+
+ wget -P /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver \
+ http://download.cloudstack.org/tools/vhd-util
+
+
+Hypervisor: VMware
+------------------
+
+.. warning::
+ For VMware hypervisor CloudStack management server packages must be
+ build using "noredist". Refer to :ref:`building-noredist`
+
+**(VMware only)** Additional steps are required for each VMware cluster.
+These steps will not affect running guests in the cloud. These steps
+are required only for clouds using VMware clusters:
+
+#. Stop the Management Server:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. Generate the encrypted equivalent of your vCenter password:
+
+ .. parsed-literal::
+
+ $ java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.2.jar org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh input="_your_vCenter_password_" password="`cat /etc/cloudstack/management/key`" verbose=false
+
+Store the output from this step, we need to add this in
+cluster\_details table and vmware\_data\_center tables in place of
+the plain text password
+
+#. Find the ID of the row of cluster\_details table that you have to
+ update:
+
+ .. parsed-literal::
+
+ $ mysql -u <username> -p<password>
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Update the plain text password with the encrypted one
+
+ .. parsed-literal::
+
+ update cloud.cluster_details set value = '_ciphertext_from_step_1_'
+ where id = _id_from_step_2_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Find the ID of the correct row of vmware\_data\_center that you
+ want to update
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+#. update the plain text password with the encrypted one:
+
+ .. parsed-literal::
+
+ update cloud.vmware_data_center set password = '_ciphertext_from_step_1_'
+ where id = _id_from_step_5_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+
+.. _kvm47:
+
+Hypervisor: KVM
+---------------
+
+KVM on Ubuntu
+^^^^^^^^^^^^^
+
+(KVM only) Additional steps are required for each KVM host. These
+steps will not affect running guests in the cloud. These steps are
+required only for clouds using KVM as hosts and only on the KVM
+hosts.
+
+#. Configure the :ref:`APT repo <apt-repo47>` as detailed above.
+
+#. Stop the running agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+
+#. Update the agent software.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Start the agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent start
+
+
+KVM on CentOS/RHEL
+^^^^^^^^^^^^^^^^^^
+For KVM hosts, upgrade the ``cloudstack-agent`` package
+
+#. Configure the :ref:`rpm-repo47` as detailed above.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Restart the agent:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+ $ sudo killall jsvc
+ $ sudo service cloudstack-agent start
+
+
+Restart management services
+---------------------------
+
+#. Now it's time to start the management server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management start
+
+#. If you use it, start the usage server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage start
+
+
+
diff --git a/source/upgrading/upgrade/upgrade-4.8.rst b/source/upgrading/upgrade/upgrade-4.8.rst
new file mode 100644
index 0000000..a0c929d
--- /dev/null
+++ b/source/upgrading/upgrade/upgrade-4.8.rst
@@ -0,0 +1,421 @@
+.. 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.
+
+
+.. |version_to_upgrade| replace:: 4.8.x
+
+Upgrade Instruction from |version_to_upgrade|
+=============================================
+
+This section will guide you from CloudStack |version_to_upgrade| to CloudStack
+|release|.
+
+Any steps that are hypervisor-specific will be called out with a note.
+
+We recommend reading through this section once or twice before beginning
+your upgrade procedure, and working through it on a test system before
+working on a production system.
+
+.. note::
+ The following upgrade instructions should be performed regardless of
+ hypervisor type.
+
+Upgrade Steps:
+
+#. Backup CloudStack database (MySQL)
+#. Add package repository for MySQL connector
+#. Upgrade CloudStack management server(s)
+#. Update hypervisors specific dependencies
+
+.. include:: _sysvm_templates.rst
+
+Packages repository
+-------------------
+
+Most users of CloudStack manage the installation and upgrades of
+CloudStack with one of Linux's predominant package systems, RPM or
+APT. This guide assumes you'll be using RPM and Yum (for Red Hat
+Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu).
+
+Create RPM or Debian packages (as appropriate) and a repository from
+the |release| source, or check the Apache CloudStack downloads page at
+http://cloudstack.apache.org/downloads.html
+for package repositories supplied by community members. You will need
+them for :ref:`ubuntu48` or :ref:`rhel48` and :ref:`kvm48` hosts upgrade.
+
+Instructions for creating packages from the CloudStack source are in the
+`CloudStack Installation Guide`_.
+
+
+Database Preparation
+--------------------
+
+Backup current database
+
+#. Stop your management server or servers. Run this on all management
+ server hosts:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. If you are running a usage server or usage servers, stop those as well:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage stop
+
+#. Make a backup of your MySQL database. If you run into any issues or
+ need to roll back the upgrade, this will assist in debugging or
+ restoring your existing environment. You'll be prompted for your
+ password.
+
+ .. parsed-literal::
+
+ $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql
+ $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql
+
+#. **(KVM Only)** If primary storage of type local storage is in use, the
+ path for this storage needs to be verified to ensure it passes new
+ validation. Check local storage by querying the cloud.storage\_pool
+ table:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'"
+
+ If local storage paths are found to have a trailing forward slash,
+ remove it:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"';
+
+
+.. _ubuntu48:
+
+Management Server on Ubuntu
+---------------------------
+
+If you are using Ubuntu, follow this procedure to upgrade your packages. If
+not, skip to step :ref:`rhel48`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ APT repository, substitute your own URL for the ones used in these examples.
+
+The first order of business will be to change the sources list for
+each system with CloudStack packages. This means all management
+servers, and any hosts that have the KVM agent. (No changes should
+be necessary for hosts that are running VMware or Xen.)
+
+
+.. _apt-repo48:
+
+.. include:: _java_8_ubuntu.rst
+
+CloudStack apt repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Start by opening ``/etc/apt/sources.list.d/cloudstack.list`` on
+any systems that have CloudStack packages installed.
+
+This file should have one line, which contains:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.8
+
+We'll change it to point to the new package repository:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.9
+
+Setup the public key for the above repository:
+
+.. parsed-literal::
+
+ wget -qO - http://download.cloudstack.org/release.asc | sudo apt-key add -
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Now update your apt package list:
+
+ .. parsed-literal::
+
+ $ sudo apt-get update
+
+#. Now that you have the repository configured, it's time to upgrade
+ the ``cloudstack-management`` package.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-usage
+
+
+.. _rhel48:
+
+Management Server on CentOS/RHEL
+--------------------------------
+
+If you are using CentOS or RHEL, follow this procedure to upgrade your
+packages. If not, skip to hypervisors section :ref:`upg_hyp_48`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ yum repository, substitute your own URL for the ones used in these examples.
+
+
+.. include:: _mysql_connector.rst
+
+
+.. _rpm-repo48:
+
+CloudStack RPM repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The first order of business will be to change the yum repository
+for each system with CloudStack packages. This means all
+management servers, and any hosts that have the KVM agent.
+
+(No changes should be necessary for hosts that are running VMware
+or Xen.)
+
+Start by opening ``/etc/yum.repos.d/cloudstack.repo`` on any
+systems that have CloudStack packages installed.
+
+This file should have content similar to the following:
+
+.. parsed-literal::
+
+ [apache-cloudstack]
+ name=Apache CloudStack
+ baseurl=http://download.cloudstack.org/centos/6/4.8/
+ enabled=1
+ gpgcheck=0
+
+If you are using the community provided package repository, change
+the base url to ``http://download.cloudstack.org/centos/$releasever/4.9/``.
+
+Setup the GPG public key if you wish to enable ``gpgcheck=1``:
+
+.. parsed-literal::
+
+ rpm --import http://download.cloudstack.org/RPM-GPG-KEY
+
+
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Now that you have the repository configured, it's time to upgrade the
+ ``cloudstack-management``.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-usage
+
+
+.. _upg_hyp_48:
+
+Hypervisor: XenServer
+---------------------
+
+**(XenServer only)** Copy vhd-utils file on CloudStack management servers.
+Copy the file `vhd-utils <http://download.cloudstack.org/tools/vhd-util>`_
+to ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``.
+
+.. parsed-literal::
+
+ wget -P /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver \
+ http://download.cloudstack.org/tools/vhd-util
+
+
+Hypervisor: VMware
+------------------
+
+.. warning::
+ For VMware hypervisor CloudStack management server packages must be
+ build using "noredist". Refer to :ref:`building-noredist`
+
+**(VMware only)** Additional steps are required for each VMware cluster.
+These steps will not affect running guests in the cloud. These steps
+are required only for clouds using VMware clusters:
+
+#. Stop the Management Server:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. Generate the encrypted equivalent of your vCenter password:
+
+ .. parsed-literal::
+
+ $ java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.2.jar org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh input="_your_vCenter_password_" password="`cat /etc/cloudstack/management/key`" verbose=false
+
+Store the output from this step, we need to add this in
+cluster\_details table and vmware\_data\_center tables in place of
+the plain text password
+
+#. Find the ID of the row of cluster\_details table that you have to
+ update:
+
+ .. parsed-literal::
+
+ $ mysql -u <username> -p<password>
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Update the plain text password with the encrypted one
+
+ .. parsed-literal::
+
+ update cloud.cluster_details set value = '_ciphertext_from_step_1_'
+ where id = _id_from_step_2_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Find the ID of the correct row of vmware\_data\_center that you
+ want to update
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+#. update the plain text password with the encrypted one:
+
+ .. parsed-literal::
+
+ update cloud.vmware_data_center set password = '_ciphertext_from_step_1_'
+ where id = _id_from_step_5_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+
+.. _kvm48:
+
+Hypervisor: KVM
+---------------
+
+KVM on Ubuntu
+^^^^^^^^^^^^^
+
+(KVM only) Additional steps are required for each KVM host. These
+steps will not affect running guests in the cloud. These steps are
+required only for clouds using KVM as hosts and only on the KVM
+hosts.
+
+#. Configure the :ref:`APT repo <apt-repo48>` as detailed above.
+
+#. Stop the running agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+
+#. Update the agent software.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Start the agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent start
+
+
+KVM on CentOS/RHEL
+^^^^^^^^^^^^^^^^^^
+For KVM hosts, upgrade the ``cloudstack-agent`` package
+
+#. Configure the :ref:`rpm-repo48` as detailed above.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Restart the agent:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+ $ sudo killall jsvc
+ $ sudo service cloudstack-agent start
+
+
+Restart management services
+---------------------------
+
+#. Now it's time to start the management server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management start
+
+#. If you use it, start the usage server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage start
+
+
+
diff --git a/source/upgrading/upgrade/upgrade-4.9.rst b/source/upgrading/upgrade/upgrade-4.9.rst
new file mode 100644
index 0000000..ab50563
--- /dev/null
+++ b/source/upgrading/upgrade/upgrade-4.9.rst
@@ -0,0 +1,420 @@
+.. 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.
+
+
+.. |version_to_upgrade| replace:: 4.9.x
+
+Upgrade Instruction from |version_to_upgrade|
+=============================================
+
+This section will guide you from CloudStack |version_to_upgrade| to CloudStack
+|release|.
+
+Any steps that are hypervisor-specific will be called out with a note.
+
+We recommend reading through this section once or twice before beginning
+your upgrade procedure, and working through it on a test system before
+working on a production system.
+
+.. note::
+ The following upgrade instructions should be performed regardless of
+ hypervisor type.
+
+Upgrade Steps:
+
+#. Backup CloudStack database (MySQL)
+#. Add package repository for MySQL connector
+#. Upgrade CloudStack management server(s)
+#. Update hypervisors specific dependencies
+
+.. include:: _sysvm_templates.rst
+
+Packages repository
+-------------------
+
+Most users of CloudStack manage the installation and upgrades of
+CloudStack with one of Linux's predominant package systems, RPM or
+APT. This guide assumes you'll be using RPM and Yum (for Red Hat
+Enterprise Linux or CentOS), or APT and Debian packages (for Ubuntu).
+
+Create RPM or Debian packages (as appropriate) and a repository from
+the |release| source, or check the Apache CloudStack downloads page at
+http://cloudstack.apache.org/downloads.html
+for package repositories supplied by community members. You will need
+them for :ref:`ubuntu49` or :ref:`rhel49` and :ref:`kvm49` hosts upgrade.
+
+Instructions for creating packages from the CloudStack source are in the
+`CloudStack Installation Guide`_.
+
+
+Database Preparation
+--------------------
+
+Backup current database
+
+#. Stop your management server or servers. Run this on all management
+ server hosts:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. If you are running a usage server or usage servers, stop those as well:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage stop
+
+#. Make a backup of your MySQL database. If you run into any issues or
+ need to roll back the upgrade, this will assist in debugging or
+ restoring your existing environment. You'll be prompted for your
+ password.
+
+ .. parsed-literal::
+
+ $ mysqldump -u root -p cloud > cloud-backup_`date '+%Y-%m-%d'`.sql
+ $ mysqldump -u root -p cloud_usage > cloud_usage-backup_`date '+%Y-%m-%d'`.sql
+
+#. **(KVM Only)** If primary storage of type local storage is in use, the
+ path for this storage needs to be verified to ensure it passes new
+ validation. Check local storage by querying the cloud.storage\_pool
+ table:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e "select id,name,path from cloud.storage_pool where pool_type='Filesystem'"
+
+ If local storage paths are found to have a trailing forward slash,
+ remove it:
+
+ .. parsed-literal::
+
+ $ mysql -u cloud -p -e 'update cloud.storage_pool set path="/var/lib/libvirt/images" where path="/var/lib/libvirt/images/"';
+
+
+.. _ubuntu49:
+
+Management Server on Ubuntu
+---------------------------
+
+If you are using Ubuntu, follow this procedure to upgrade your packages. If
+not, skip to step :ref:`rhel49`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ APT repository, substitute your own URL for the ones used in these examples.
+
+The first order of business will be to change the sources list for
+each system with CloudStack packages. This means all management
+servers, and any hosts that have the KVM agent. (No changes should
+be necessary for hosts that are running VMware or Xen.)
+
+
+.. _apt-repo49:
+
+.. include:: _java_8_ubuntu.rst
+
+CloudStack apt repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Start by opening ``/etc/apt/sources.list.d/cloudstack.list`` on
+any systems that have CloudStack packages installed.
+
+This file should have one line, which contains:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.8
+
+We'll change it to point to the new package repository:
+
+.. parsed-literal::
+
+ deb http://download.cloudstack.org/ubuntu precise 4.9
+
+Setup the public key for the above repository:
+
+.. parsed-literal::
+
+ wget -qO - http://download.cloudstack.org/release.asc | sudo apt-key add -
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Now update your apt package list:
+
+ .. parsed-literal::
+
+ $ sudo apt-get update
+
+#. Now that you have the repository configured, it's time to upgrade
+ the ``cloudstack-management`` package.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-usage
+
+
+.. _rhel49:
+
+Management Server on CentOS/RHEL
+--------------------------------
+
+If you are using CentOS or RHEL, follow this procedure to upgrade your
+packages. If not, skip to hypervisors section :ref:`upg_hyp_49`.
+
+.. note::
+ **Community Packages:** This section assumes you're using the community
+ supplied packages for CloudStack. If you've created your own packages and
+ yum repository, substitute your own URL for the ones used in these examples.
+
+
+.. include:: _mysql_connector.rst
+
+
+.. _rpm-repo49:
+
+CloudStack RPM repository
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The first order of business will be to change the yum repository
+for each system with CloudStack packages. This means all
+management servers, and any hosts that have the KVM agent.
+
+(No changes should be necessary for hosts that are running VMware
+or Xen.)
+
+Start by opening ``/etc/yum.repos.d/cloudstack.repo`` on any
+systems that have CloudStack packages installed.
+
+This file should have content similar to the following:
+
+.. parsed-literal::
+
+ [apache-cloudstack]
+ name=Apache CloudStack
+ baseurl=http://download.cloudstack.org/centos/6/4.8/
+ enabled=1
+ gpgcheck=0
+
+If you are using the community provided package repository, change
+the base url to ``http://download.cloudstack.org/centos/$releasever/4.9/``.
+
+Setup the GPG public key if you wish to enable ``gpgcheck=1``:
+
+.. parsed-literal::
+
+ rpm --import http://download.cloudstack.org/RPM-GPG-KEY
+
+
+
+If you're using your own package repository, change this line to
+read as appropriate for your |version| repository.
+
+#. Now that you have the repository configured, it's time to upgrade the
+ ``cloudstack-management``.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-management
+
+#. If you use CloudStack usage server
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-usage
+
+.. _upg_hyp_49:
+
+Hypervisor: XenServer
+---------------------
+
+**(XenServer only)** Copy vhd-utils file on CloudStack management servers.
+Copy the file `vhd-utils <http://download.cloudstack.org/tools/vhd-util>`_
+to ``/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver``.
+
+.. parsed-literal::
+
+ wget -P /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver \
+ http://download.cloudstack.org/tools/vhd-util
+
+
+Hypervisor: VMware
+------------------
+
+.. warning::
+ For VMware hypervisor CloudStack management server packages must be
+ build using "noredist". Refer to :ref:`building-noredist`
+
+**(VMware only)** Additional steps are required for each VMware cluster.
+These steps will not affect running guests in the cloud. These steps
+are required only for clouds using VMware clusters:
+
+#. Stop the Management Server:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management stop
+
+#. Generate the encrypted equivalent of your vCenter password:
+
+ .. parsed-literal::
+
+ $ java -classpath /usr/share/cloudstack-common/lib/jasypt-1.9.2.jar org.jasypt.intf.cli.JasyptPBEStringEncryptionCLI encrypt.sh input="_your_vCenter_password_" password="`cat /etc/cloudstack/management/key`" verbose=false
+
+Store the output from this step, we need to add this in
+cluster\_details table and vmware\_data\_center tables in place of
+the plain text password
+
+#. Find the ID of the row of cluster\_details table that you have to
+ update:
+
+ .. parsed-literal::
+
+ $ mysql -u <username> -p<password>
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Update the plain text password with the encrypted one
+
+ .. parsed-literal::
+
+ update cloud.cluster_details set value = '_ciphertext_from_step_1_'
+ where id = _id_from_step_2_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.cluster_details;
+
+#. Find the ID of the correct row of vmware\_data\_center that you
+ want to update
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+#. update the plain text password with the encrypted one:
+
+ .. parsed-literal::
+
+ update cloud.vmware_data_center set password = '_ciphertext_from_step_1_'
+ where id = _id_from_step_5_;
+
+#. Confirm that the table is updated:
+
+ .. parsed-literal::
+
+ select * from cloud.vmware_data_center;
+
+
+.. _kvm49:
+
+Hypervisor: KVM
+---------------
+
+KVM on Ubuntu
+^^^^^^^^^^^^^
+
+(KVM only) Additional steps are required for each KVM host. These
+steps will not affect running guests in the cloud. These steps are
+required only for clouds using KVM as hosts and only on the KVM
+hosts.
+
+#. Configure the :ref:`APT repo <apt-repo49>` as detailed above.
+
+#. Stop the running agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+
+#. Update the agent software.
+
+ .. parsed-literal::
+
+ $ sudo apt-get upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Start the agent.
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent start
+
+
+KVM on CentOS/RHEL
+^^^^^^^^^^^^^^^^^^
+For KVM hosts, upgrade the ``cloudstack-agent`` package
+
+#. Configure the :ref:`rpm-repo49` as detailed above.
+
+ .. parsed-literal::
+
+ $ sudo yum upgrade cloudstack-agent
+
+#. Verify that the file ``/etc/cloudstack/agent/environment.properties`` has a
+ line that reads:
+
+ .. parsed-literal::
+
+ paths.script=/usr/share/cloudstack-common
+
+ If not, add the line.
+
+#. Restart the agent:
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-agent stop
+ $ sudo killall jsvc
+ $ sudo service cloudstack-agent start
+
+
+Restart management services
+---------------------------
+
+#. Now it's time to start the management server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-management start
+
+#. If you use it, start the usage server
+
+ .. parsed-literal::
+
+ $ sudo service cloudstack-usage start
+
+
+
diff --git a/source/upgrading/upgrade/upgrade_notes.rst b/source/upgrading/upgrade/upgrade_notes.rst
new file mode 100644
index 0000000..713c5b1
--- /dev/null
+++ b/source/upgrading/upgrade/upgrade_notes.rst
@@ -0,0 +1,106 @@
+.. 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.
+
+
+General Upgrade Notes
+=====================
+
+
+Java version upgraded to Java 1.8
+---------------------------------
+
+As of Apache CloudStack 4.10, Java version required is 1.8 for the
+management-server, cloudstack-usage, KVM agent and system-VMs.
+
+
+.. include:: _java_8_ubuntu.rst
+
+
+Migrating to dynamic roles feature
+----------------------------------
+
+As of Apache CloudStack 4.9, dynamic roles feature can be enabled after an
+upgrade. Dyanamic roles feature is enabled by default on new installations.
+
+Please read more about :ref:`using-dynamics-roles`
+feature and process of migrating to using this after an upgrade.
+
+Agent and KVM Host Security
+---------------------------
+
+Starting 4.11, a new CA framework has been introduced that is used to secure
+agent and management server connections. Starting 4.11.1, KVM hosts in UP
+state that are not secured (i.e. the KVM host agent and libvirtd don't have
+CA framework provisioned X509 certificates) will show up as 'Unsecure'. A new
+button in the UI is available as well as an API to secure and onboard such
+hosts.
+
+Please read more about :ref:`host-security` and the process of migrating existing KVM hosts and agents to use the new security
+feature.
+
+OVS plug-in
+-----------
+
+OVS plug-in functionality is disrupted if ovsdaemon crashes
+
+A critical functionality issue came out with `CLOUDSTACK-6779 <https://issues.apache.org/jira/browse/CLOUDSTACK-6779>`_. On XenServer it
+is observed that on VIF unplug Ovs-Vswitchd is crashing resulting in loosing all
+the openflow rules added to the bridge. Ovs daemon gets started and creates a
+bridge but configure openflow rules are lost resulting in the disruption of
+connectivity for the VM's on the host.
+
+
+Active-Directory Authentication (LDAP)
+--------------------------------------
+
+If using Active-Directory (LDAP/LDAPs) as user authentication; Upgrading to
+4.3 and later require changes in Global Settings. After upgrading CloudStack
+to 4.3 or latest, following Global Settings must be change:
+
+.. cssclass:: table-striped table-bordered table-hover
+
+======================= ============== ==============
+Global Settings Default New
+======================= ============== ==============
+ldap.user.object inetOrgPerson user
+ldap.username.attribute uid sAMAccountName
+======================= ============== ==============
+
+
+SystemVM 32bit deprecated
+-------------------------
+
+32bit versions of systemvm templates are in the process of behing deprecated. Upgrade instructions from this Release Notes use 64bit templates.
+
+Explicit JDBC driver declaration
+--------------------------------
+
+While upgrading, on some environments the following may be required to be
+added in CloudStack's db.properties file:
+
+ # Add these to your db.properties file
+
+ db.cloud.driver=jdbc:mysql
+
+ db.usage.driver=jdbc:mysql
+
+
+Other Notes
+-----------
+
+If you are experiencing CloudStack UI issues, please consider upgrading your
+tomcat instance to version 6.0.43 (tested version, but earlier versions prior
+to 6.0.37 might work as well), to address the tomcat response issues caused by
+latency between the browser/client and CloudStack Management server.
diff --git a/source/upgrading/upgrade/valid_source.rst b/source/upgrading/upgrade/valid_source.rst
new file mode 100644
index 0000000..6436ee9
--- /dev/null
+++ b/source/upgrading/upgrade/valid_source.rst
@@ -0,0 +1,103 @@
+.. 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.
+
+
+Validate |release| source code tarball
+======================================
+
+#. Perform the following to verify the artifacts:
+
+ #. (optional) Install GPG keys if needed:
+
+ .. parsed-literal::
+
+ $ sudo apt-get install gpg
+
+ #. Import the GPG keys stored in the source distribution's KEYS file
+
+ .. parsed-literal::
+
+ $ gpg --import KEYS
+
+ Alternatively, download the signing keys, the IDs found in the
+ KEYS file, individually by using a keyserver.
+
+ For example:
+
+ .. parsed-literal::
+
+ $ gpg --recv-keys CC56CEA8
+
+ #. Verify signatures and hash files:
+
+ .. parsed-literal::
+
+ $ gpg --verify apache-cloudstack-|release|-src.tar.bz2.asc
+ $ gpg --print-md MD5 apache-cloudstack-|release|-src.tar.bz2 | diff - apache-cloudstack-|release|-src.tar.bz2.md5
+ $ gpg --print-md SHA512 apache-cloudstack-|release|-src.tar.bz2 | diff - apache-cloudstack-|release|-src.tar.bz2.sha
+
+ Each of these commands should return no output. Any output from
+ them implies that there is a difference between the hash you
+ generated locally and the hash that has been pulled from the
+ server.
+
+ #. Get the commit hash from the VOTE email.
+
+ For example: ``1b8a532ba52127f388847690df70e65c6b46f4d4``. The
+ value changes between releases.
+
+ #. Create two new temporary directories:
+
+ .. parsed-literal::
+
+ $ mkdir /tmp/cloudstack/git
+ $ mkdir /tmp/cloudstack/tree
+
+ #. Check out the |release| branch:
+
+ .. parsed-literal::
+
+ $ git clone https://git-wip-us.apache.org/repos/asf/cloudstack.git /tmp/cloudstack/git
+ $ cd /tmp/cloudstack/git
+ $ git archive --format=tar --prefix=/tmp/cloudstack/tree/ <commit-hash> | tar Pxf -
+
+ #. Unpack the release artifact:
+
+ .. parsed-literal::
+
+ $ cd /tmp/cloudstack
+ $ tar xvfj apache-cloudstack-|release|-src.tar.bz2
+
+ #. Compare the contents of the release artifact with the contents
+ pulled from the repo:
+
+ .. parsed-literal::
+
+ $ diff -r /tmp/cloudstack/apache-cloudstack-|release|-src /tmp/cloudstack/tree
+
+ Ensure that content is the same.
+
+ #. Verify the Code License Headers:
+
+ .. parsed-literal::
+
+ $ cd /tmp/cloudstack/apache-cloudstack-|release|-src
+ $ mvn --projects='org.apache.cloudstack:cloudstack' org.apache.rat:apache-rat-plugin:0.8:check
+
+ The build fails if any non-compliant files are present that are
+ not specifically excluded from the ASF license header requirement.
+ You can optionally review the target/rat.txt file after the run
+ completes. Passing the build implies that RAT certifies that the
+ files are compliant and this test is passed.
